An unhandled exception was thrown by the Error Prone static analysis plugin

Description of the problem
encounter error when use gradle to compile original google code with error-prone plugin:
src/com/android/providers/settings/SettingsProvider.java:1487: error: An unhandled exception was thrown by the Error Prone static analysis plugin.
return settingsState.new Setting(ssaidSetting) {
^
Please report this at https://github.com/google/error-prone/issues/new and include the following:
error-prone version: 2.3.3
BugPattern: NullAway
 Stack Trace:
 java.lang.RuntimeException: whoops, better handle OTHER null
at com.uber.nullaway.NullAway.mayBeNullExpr(NullAway.java:1952)
at com.uber.nullaway.NullAway.handleInvocation(NullAway.java:1352)
at com.uber.nullaway.NullAway.matchNewClass(NullAway.java:354)
at com.google.errorprone.scanner.ErrorProneScanner.processMatchers(ErrorProneScanner.java:433)
at com.google.errorprone.scanner.ErrorProneScanner.visitNewClass(ErrorProneScanner.java:759)
at com.google.errorprone.scanner.ErrorProneScanner.visitNewClass(ErrorProneScanner.java:150)
at com.sun.tools.javac.tree.JCTree$JCNewClass.accept(JCTree.java:1705)

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Gradle compile passed without error-prone plugin, but failed if plugin integrated.
Have you found anything relevant by searching the web?
None.
relevant code fragment
private Setting mascaradeSsaidSetting(SettingsState settingsState, Setting ssaidSetting) {
if (ssaidSetting != null) {
return settingsState.new Setting(ssaidSetting) {
@Override
public int getKey() {
final int userId = getUserIdFromKey(super.getKey());
return makeKey(SETTINGS_TYPE_SECURE, userId);
}
            @Override
            public String getName() {
                return Settings.Secure.ANDROID_ID;
            }
        };
    }
    return null;
}

The NullAway issue is uber/NullAway#366; I think this one can be closed.

The NullAway issue is uber/NullAway#366; I think this one can be closed.

Yes.


Drop support for EOL Python 2.6 and 3.2-2.4

Python 2.6 and 3.3 were removed in https://github.com/un33k/python-slugify/pull/63, so this removes their Trove classifiers.
This also:

Removes a duplicate test class

Upgrade Python syntax with pyupgrade

Upgrade PyPy and PyPy3 (6.0.0 to 7.1.1) and test 3.8 beta on the CI

Add python_requires to help pip

@hugovk.  May I ask you to raise the PR against the staging branch instead ?  Thank you.

I've switched the base branch to staging.
May I suggest changing the default branch in the repo settings to staging? That way future PRs will be made to staging in the future. Thanks!

I like master branch as default, but I wish there was a way to include a default for incoming PRs.  Each incoming PR needs to be tested followed by a version bump and only then it can be promoted to master.

Thank you for your contribution. Version 4.0.0 is pushed. https://github.com/un33k/python-slugify/tree/4.0.0

You're welcome!


[Bug] Failed to execute SparkLoadJob

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
master branch
What's Wrong?
Hi, currently I am trying Spark Load Job，but ended up with error msg like this every time:  txn does not exist. id: 0
+-------+--------------+-----------+-------------------+-------+---------+-------------------------------------------------------+----------------------------------------------------------------------------------+---------------------+--------------+---------------+---------------+---------------------+------+-----------------------------------------------------------------------------------------------------------------------+---------------+--------------+
| JobId | Label        | State     | Progress          | Type  | EtlInfo | TaskInfo                                              | ErrorMsg                                                                         | CreateTime          | EtlStartTime | EtlFinishTime | LoadStartTime | LoadFinishTime      | URL  | JobDetails                                                                                | TransactionId | ErrorTablets |
+-------+--------------+-----------+-------------------+-------+---------+-------------------------------------------------------+----------------------------------------------------------------------------------+---------------------+--------------+---------------+---------------+---------------------+------+-----------------------------------------------------------------------------------------------------------------------+---------------+--------------+
| 16006 | doris_goods  | CANCELLED | ETL:N/A; LOAD:N/A | SPARK | NULL    | cluster:spark0; timeout(s):3600; max_filter_ratio:0.0 | type:ETL_SUBMIT_FAIL; msg:errCode = 2, detailMessage = txn does not exist. id: 0 | 2022-04-01 19:41:39 | NULL         | NULL          | NULL          | 2022-04-01 19:41:44 | NULL | {"Unfinished backends":{},"ScannedRows":0,"TaskNumber":0,"LoadBytes":0,"All backends":{},"FileNumber":0,"FileSize":0} | 0             | {}           |
What You Expected?
After going through the code，the Error generated at the following code inside this fuction SparkLoadPendingTask#createEtlJobConf
// add table indexes to transaction state
TransactionState txnState = Catalog.getCurrentGlobalTransactionMgr()
.getTransactionState(dbId, transactionId);
if (txnState == null) {
throw new LoadException("txn does not exist. id: " + transactionId);
}
Seems that the transaction has not begun（transactionId is 0 as shown in error message). The transaction begins lately when SparkLoadPendingTask start to execute.
I wonder if there is something wrong in my test procedure, but I did follow the guide in official document.
Thanks for your help .
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I also got this error, but was on dev-1.0.0

I'm a begginer of doris. But i dug into this issue a bit. I think maybe this problem was caused by this https://github.com/apache/incubator-doris/pull/7371/files
After this, call of LoadJob.beginTxn was moved from LoadJob.unprotectedExecute to SparkLoadPendingTask.executeTask, which was after the call of SparkLoadPendingTask.createEtlJobConf  and so in createEtlJobConf the transactionId was 0.

hi @sumtumn, thanks for your advice. I have solved this problem by a minor modification, and tested. Could you two help to see whether these changes works fine ?  @wangbo @sumtumn

Please add a PR. @zhengshengjun


Identifiers validation failed for dataset Sistemática del género Polianthes L (Agavaceae)

Identifier validation failed for the dataset Sistemática del género Polianthes L (Agavaceae):

Crawler attempt: 308
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 354
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 350 total records; 350 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740397/step

New IDs sample:

Old IDs sample:

6f39c6bac418f40d0b99ff00705bb9de
17445e0865575ff0e74ed418a37c37cc
0869abdfccf597c45031cdcb1879eaa2
315586540ab1930126426f1d459e7418
31850c670d043601d45235b2b86a7cba
4657adeefac2075cd625b7105e2131fc
62aced1b127d91fe9ff8b4e5f670988f
97d715eaddd355e542f90a15c6950d1a
e6d4a8767c80efe8780d1d0f86cc8f95
ef6453860420ff16f925b07559913dde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Sistemática del género Polianthes L (Agavaceae) : https://doi.org/10.15468/8dv3os.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Sistemática del género Polianthes L (Agavaceae):

Crawler attempt: 309
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 354
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 350 total records; 350 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741202/step

New IDs sample:

Old IDs sample:

6f39c6bac418f40d0b99ff00705bb9de
17445e0865575ff0e74ed418a37c37cc
0869abdfccf597c45031cdcb1879eaa2
315586540ab1930126426f1d459e7418
31850c670d043601d45235b2b86a7cba
4657adeefac2075cd625b7105e2131fc
62aced1b127d91fe9ff8b4e5f670988f
97d715eaddd355e542f90a15c6950d1a
e6d4a8767c80efe8780d1d0f86cc8f95
ef6453860420ff16f925b07559913dde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Sistemática del género Polianthes L (Agavaceae) : https://doi.org/10.15468/8dv3os.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Sistemática del género Polianthes L (Agavaceae):

Crawler attempt: 311
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 354
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 350 total records; 350 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741822/step

New IDs sample:

Old IDs sample:

6f39c6bac418f40d0b99ff00705bb9de
17445e0865575ff0e74ed418a37c37cc
0869abdfccf597c45031cdcb1879eaa2
315586540ab1930126426f1d459e7418
31850c670d043601d45235b2b86a7cba
4657adeefac2075cd625b7105e2131fc
62aced1b127d91fe9ff8b4e5f670988f
97d715eaddd355e542f90a15c6950d1a
e6d4a8767c80efe8780d1d0f86cc8f95
ef6453860420ff16f925b07559913dde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Sistemática del género Polianthes L (Agavaceae) : https://doi.org/10.15468/8dv3os.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


[ci] Run iOS drive master tests on Apple Silicon

In the master drive tests use --enable-software-rendering flag implemented in https://github.com/flutter/flutter/pull/105161
Part of https://github.com/flutter/flutter/issues/104523
See also https://github.com/flutter/plugins/pull/5794 and https://github.com/flutter/plugins/pull/5693
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Seems like the same hanging symptoms like before. Will try to reproduce locally like before but since you are forcing not to use Metal inside the simulator it means the GPU is crashing when simulator's UI is rendered. Seems like the problem is isolated to the outside of Flutter's environment inside the simulator.
Which means that the original workaround might be a better option. Just add the following command as the first line in create_simulator_script. @stuartmorgan what do you think?
defaults write com.apple.CoreSimulator.IndigoFramebufferServices FramebufferRendererHint 3

Seems worth trying.
Is there a longer term strategy to address this problem? Relying on an undocumented default is fragile; it could break in any simulator update. Is there a a Radar we can reference in a comment on this hack?

Which means that the original workaround might be a better option. Just add the following command as the first line in create_simulator_script. @stuartmorgan what do you think?
defaults write com.apple.CoreSimulator.IndigoFramebufferServices FramebufferRendererHint 3

Reverted the --enable-software-rendering change, trying FramebufferRendererHint

It seems like if anything it's even worse now.

@stuartmorgan seems the same. Let me see what could change since May 26th.

I have good news and bad news. I was able to get a hold on a support engineer from Apple who looked into my report and talked to the people behind Virtualization.Framework and related stuff internally.
Bad news is that they don't believe that IndigoFramebufferServices does anything. It seems I was wrong and got a wrong impression that the command passed. I think I might have copy/pasted a command for macos tests instead of ios or something like that.
The support engineer asked me a bit more questions but his general suggestion and a message from the rest of the team was to try out macOS Ventura.
So I tried the private beta of Ventura with the current stable Xcode 13.4.1 and everything worked. This time I've tripple checked that I was running the right ./script/tool_runner.sh drive-examples --ios command and not --macos. I repeated the experiment several times in fresh VMs and every time it passed.
Unfortunately it seems we don't have other options but to wait for macOS Ventura Public Beta in a month or so (I don't think we can legally use macOS Ventura for public CI while it's in private beta). On a bright side we found the issue with master -> main mirroring which caused unwanted builds and we also dropped prices on both old and new macOS instances. Sorry about this blocker. We are doing some bleeding edge stuff here after all.

Closing.


New package header

Closes #349

At some viewport sizes, this bug occurs:

On mobile there is some incorrect spacing under the description here:

There is a spacing issue to the left of the "Jump to latest" button:

Looking great - just some small comments.


Improve --help to show config name and config defaults

Introduce a click.Option subclass that renders help messages with defaults from the context's default_map and shows a hint to the config setting name. This simplifies the code and avoids code duplication.
The implementation can later be extended to show dynamic defaults from the user's config file instead of static defaults from the default config.
Code:
@click.option(
    "--model-path",
    type=click.Path(),
    cls=ConfigOption,
    help="Path to the model used during generation.",
)

Output:
Options:
--model-path PATH           Path to the model used during generation.
                            [default: models/merlinite-7b-lab-Q4_K_M.gguf;
                            config: 'serve.model_path']

Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[X] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

TODO:

[x] Add ConfigOption to all subcommands
[x] Extend ConfigOption to support nested defaults, e.g. llama_cpp.gpu_layers

@cdoern Please take a look. I have extended click, so we now look up defaults in nested default_map entries and report the config location in --help:
$ ilab model train --help
...
Options:
  --data-path PATH                Base directory where data is stored.
                                  [required; default: ./taxonomy_data; config:
                                  'train.train_args.data_path']
  --ckpt-output-dir PATH          output directory to store checkpoints in
                                  during training  [required; default:
                                  checkpoints; config:
                                  'train.train_args.ckpt_output_dir']
  --data-output-dir PATH          output directory to store training data in
                                  [required; default: train-output; config:
                                  'train.train_args.data_output_dir']

Will give this a more thorough review this afternoon but let me just say this is FANTASTIC!!!! This is the exact direction I wanted to go in with the config parsing :raised_hands:


Apostrophes are doubled in the reported message

I'm using the Microsoft Styleguide. I have content that triggers the Contractions.yml rule. In the reported message the apostrophes of the offending word get doubled:
  "Untitled1.md": [
    {
      "Action": {
        "Name": "replace",
        "Params": null
      },
      "Check": "Microsoft.Contractions",
      "Description": "",
      "Line": 3,
      "Link": "https://docs.microsoft.com/en-us/style-guide/word-choice/use-contractions",
      "Message": "Use ''doesn't'' instead of 'does not'.",
      "Severity": "error",
      "Span": [
        6,
        13
      ],
      "Match": "does not"
    },```

- OS Windows 10
- Install method Direct download
- Vale version 2.6.5

This was actually fixed in v2.6.6 of Vale (not this repo).


Deployment Error following quickstart instructions

Describe the bug
Deployment Error following quickstart instructions
To Reproduce
Steps to reproduce the behavior:

Follow the quickstart instructions here: https://docs.microsoft.com/en-us/azure/healthcare-apis/fhir-oss-portal-quickstart

Expected behavior
No deployment errors.  I'm able to start quickly following the quick start instructions.
Actual behavior
Deployment Error of: "Cannot find ServerFarm with name serverfarm-name-from-template-input.  Click here for details ->" was returned.

Looks like this was the issue.
App Service Plan Resource Group and App Service Plan are OPTIONAL, and could perhaps be renamed to be prefixed with "Use Existing" in the field name to make template use a bit more straightforward.   I was able to figure this out using the tool tip text, but it was not immediately obvious.
Thx
Rob

Also, I'd like to mention that it has been 8 minutes since the deployment, and the /metadata endpoint is not responding.  Eight minutes seems a bit longer than "a minute or so" as described on the quickstart page.  So, either something has still gone wrong, or maybe it takes longer for this to warm up.   I deployed to the default size on the template of S1.

@robwafle thank you for reporting this. I have started making some updates to the quickstart guide to make it more clear and will let you know once its updated.

AB#76139

@robwafle I have included the QuickStart guide in our OSS Documentation now and added some updates that will hopefully make it clearer. Let me know if you have any additional questions!
https://github.com/microsoft/fhir-server/blob/master/docs/QuickstartDeployPortal.md


scan_evt timeout error after 5-6 hours of scanning with esp32

ESP32 got stuck after 5-6 hours of scanning with "scan_evt timeout" error. nimBLE version 1.4.0

This is an issue with esp-idf BT controller. Will need to wait for an update from espressif.
https://github.com/espressif/esp-idf/issues/9384

Ran into this issue yesterday with arduino-esp32 core version 2.0.5. Only seems to be triggered randomly when using BLE and WiFi. Downgrading to 2.0.4 seems to resolve the issue for now.

Might this have to do with running out of memory when using indefinity scan because m_scanResults.m_advertisedDevicesVector and duplicatesCache keeps growing?
I have posted a pull request to fix this: #480
You also need to set maxResults to something < 0xFF when using scanDuration == 0

I don't believe this to be the cause, but worth testing. The duplicate cache clears itself (or at least it's supposed to) when it reaches the number of devices set by setScanDuplicateCacheSize.

We are using a scan with a scanDuration == 0 and see a steady decline in available memory.
We thought we had solved it by setting maxResults == 0 and regularly clearing the duplicates cache (we re not using duplicate filtering) but that doesn't seem to work

It turns out that i'm getting a lot of advertisements (of for me unknown devices) which are added to the scanResult m_advertisedDevicesVector but for which the callback method is never called, and hence they are never removed from the vector.
To test this I added some code to periodically remove all advertisements in the vector that are older than 10 sec, and now my memory use is stable.
I can't find any documentation on the event_type's that are used in if statements in NimBKEScan.cpp
Running scans in passive mode solved the problem!

Unfortunately, I've been running into this problem recently, and through trial and error can confirm that this doesn't seem to work on either Arduino v2.0.7 or v2.0.4-- though v2.0.4 seemed to last an average of 4 hours before becoming unresponsive while v2.0.7 only seemed to last an average of 2 hours before things became an issue.
Changing the scan time, windows, etc. doesn't seem to help, but passive scanning does seem to resolve the issue.
The issue has been raised a number of times over the years with Espressif -- both in arduino-esp32 and esp-idf:

https://github.com/espressif/arduino-esp32/issues/5860
https://github.com/espressif/esp-idf/issues/10252
https://github.com/espressif/esp-idf/issues/9384
https://github.com/espressif/esp-idf/issues/8759
https://github.com/espressif/esp-idf/issues/4001

...however the only good news in any of those issues is that the issue is supposedly resolved in the v5.x line of esp-idf which will one day become the v3.x line of the Arduino framework.
That said -- sounds like this error is potentially going to be solved in the next few months. Fingers crossed!

Hello,
We are also facing issues randomly like after 15 to 20 days like evt_scan timeout prints are coming continuously. We are using ESP32 IDF 5.1 Release and Wi-Fi and BLE together.
So, Would you please help me like what can be the cause for the same?
Let me know if need anything else from my end.
Regards,
Ritesh Prajapati

As mentioned above there is nothing we can do here as this is a problem with the controller and needs to be resolved by espressif.

As mentioned above there is nothing we can do here as this is a problem with the controller and needs to be resolved by espressif.

Hello,
Understood but issue I am facing randomly like there is no any fixed pattern to reproduce this issue. Espressif Team has also provided few debug library for BT perspective but still not able to reproduce issue again.
I believe issue into scanning process handling perspective while issue is reproduced.
Regards,
Ritesh Prajapati

I see the message "scan_evt timeout" in my terminal, but I did not find the file with the function where it prints this. Where can I find it? If I got a handler (or something) that is called when this error occurs, I could use it to just restart the device...

I see the message "scan_evt timeout" in my terminal, but I did not find the file with the function where it prints this. Where can I find it? If I got a handler (or something) that is called when this error occurs, I could use it to just restart the device...

Hello @Reneslasertag ,
Please find below link which I have already raised issue earlier over ESP32 community as well.
https://esp32.com/viewtopic.php?f=13&t=35396
I believe those prints are coming from BT Stack Library for which code is not open. But, as per discussion with team that they have already fixed into newer IDF but still need to confirm with them with commit ID if already patch is applied from their end.
Regards,
Ritesh Prajapati

This has been fixed in IDF, not yet in Arduino releases as far as I know.

This has been fixed in IDF, not yet in Arduino releases as far as I know.

@h2zero , Thanks for providing updates from your end.
Regards,
Ritesh Prajapati


I want full control over the UI

In simple cases, it's great that the code creates the checkbox elements for you. However, I need more control over the layout of the checkboxes in the group--multiple columns of checkboxes in a group for example.
When I went looking for "angular best practices for checkbox groups", I was hoping to find a solution that does almost exactly what you offer but where I apply it to my own checkbox group HTML.
I'm new to Angular, but for me, one of the reasons I'm attracted to Angular is the ability to get back to simple HTML DOM and away from having javascript create all the DOM. For my checkbox groups, they will remain pretty much static--I don't need to dynamically data-drive the creation of that DOM. I just need a good 2-way method to manage what is checked as a group.

You can use the ng-repeat, but this is not mandatory. You can have your own checkboxes linked together by the checklist-model.

Thanks. I will try to get this working. You might update your nice examples page to show a "Static list of checkboxes" example. I am also wondering now if there would be a way to set the checklist-model on the parent container rather than repeat that in 20 checkbox elements in the group. Thanks for putting this code out there.

I wouldn't go on the path of setting this in the parent container. In the same container you may have different groups and it would become confusing and cluttered.

I added a new issue for static list example:  #92 .


Reproducing Figure 1.

Thanks for sharing such a nice work.
I'm trying to reproduce "one big circle" of Figure 1 in your paper.
I set parameters as code below and it doesn't work. How can I set parameters for AlphaLayer and BarcodePolyFeature?
from topologylayer.nn import AlphaLayer, BarcodePolyFeature
import torch, numpy as np, matplotlib.pyplot as plt

# random pointcloud
np.random.seed(0)
data = np.random.rand(100, 2)

# optimization to increase size of holes
layer = AlphaLayer(maxdim=1)
x = torch.autograd.Variable(torch.tensor(data).type(torch.float), requires_grad=True)
f1 = BarcodePolyFeature(1,2,0)
optimizer = torch.optim.Adam([x], lr=1e-2)
for i in range(100):
    optimizer.zero_grad()
    loss = f1(layer(x))
    loss.backward()
    optimizer.step()

Sorry, I found the example code in /examples/paper/pointcloud/alpha.py.
Thanks.


Non sincronizza !!!![BUG]

Describe the bug
A clear and concise description of what the bug is. (If what you are experiencing is NOT a bug but instead a support issue, please open a Discussion instead!)
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Linux]
OS Version/Flavor: [e.g. CentOS 7.2]
CPU: [e.g. Intel Xeon 8175M]

Additional context
Add any other context about the problem here.

Le porte sono aperte , ho verificato , chia sincronizza normalmente ma flax non sincronizza niente ! Help

Inducer and Full Node/Timelord addresses are listed on the website:
https://flaxnetwork.org/download.html
Node type	Node address	Port DNS introducer	dns-introducer.flaxnetwork.org	(DNS) WebSocket introducer	introducer.flaxnetwork.org	6888 Full node + Timelord	node-1.flaxnetwork.org	6888 Full node + Timelord	node-2.flaxnetwork.org	6888 Full node + Timelord	node-3.flaxnetwork.org	6888 Full node + Timelord	node-4.flaxnetwork.org	6888


Fixed problems and PdfJS updated

Fixed problems in my fork and updated PdfJS lib to docs/ example (I don't can update in NPM package. I always have more problems.)

Annotation and highlighting working in Safari (iPhone with iOS 12)
Fixed bug with Canvas that entering in repeat mode (overflow error)
Fixed render bugs. I updated PdfJS version and my render now is good

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you @rogercorrea !

@rogercorrea How did you fix the IOS 12 memory overflow error? I can't see anything in you PR that gives me a clue how you fixed it. Or is it fixed in pdf.js or pdf.worker.js?


Local Data Store Deprecated?

Has this been deprecated?
i can not get anything to pin to the LDS
//----------------------------------------------
//  Pin
//----------------------------------------------
let contact = PFObject(className: "temp")
contact["firstName"] = "steve"
contact["lastName"] = "smith"
contact["email"] =<EMAIL_ADDRESS>contact.pinInBackground()
//----------------------------------------------
//  Get
//----------------------------------------------
let query = PFQuery(className: "temp")
query.whereKey("firstName", equalTo: "steve")
query.fromLocalDatastore()
query.findObjectsInBackground { (object, error) in
 if error == nil {
      for object in object! {
           print(object["firstName"] as! String)
      }
 }

}
LDS is enabled right at top of app delegate
//----------------------------------------------
//  App Delegate
//----------------------------------------------
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
    Parse.enableLocalDatastore()

No, I am using it. Your last step in App Delegate may not work, you should use:
let configuration = ParseClientConfiguration {
    $0.isLocalDatastoreEnabled = true
    ..
}
Parse.initialize(with: configuration)

thank you for that you are correct.
there are still some threads saying this is being deprecated but i can't really get an answer about wether this is correct or not.
I'm hesitant to go too far with it if it isn't going to be available in future releases.

There is a bounty open to overhaul caching, feel free to contribute.
https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/301
https://www.bountysource.com/issues/26840483-localdatastore-query-caching


SW-4761 Create MyAccountRouter and put views and sub components into scenes directory. Move the observations router to the scenes directory

SW-4761 Create MyAccountRouter and put views and sub components into scenes directory. Move the observations router to the scenes directory
Fix imports
Fix imports

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #2050

PR #2061

PR #2062

PR #2063

PR #2064

PR #2065

PR #2066

PR #2067

Merge activity

Jan 25, 3:38 PM: @sgrimm started a stack merge that includes this pull request via Graphite.


Org Officer Create Org UI needed

Overview
As an organization administrator, I should be able to create a new organization on Jupiter.
There should be some non-functional UI which shows some kind of form allowing org officers to create a new organization. Likely this would be submitting a request to us to be reviewed, though those details need to be ironed out.
Proposal
This likely would be developed with/after #52.

[ ] Create placeholder/temporary state to track whether logged in user is an org officer (optional)
[ ] If user is an officer of an org, show special UI to begin creating an org
[ ] Create a new page (or some UI) that shows a form of basic data needed
[ ] Simulate submitting the form to the backend, and return to previous page

I'm not sure where exactly this should live - it seem logical for this to be in the app settings. Maybe an org officer would have an "Organization administration" tab, and would show a "create new organization" button if they aren't assigned to one currently.

To handle state are we going to be using React Context API or Redux?

I'm not sure but this article would be helpful in choosing between the two.

I think we can use instead of a context API would be using a library like React Query. It basically replaces the need to use context libraries due to how it caches the information. Just throwing around another idea

I do see that Planner is user Redux.
For React Query's benefit, does that allow more advanced client-side caching than the others?

Yeah, it allows us to granularly refetch data if needed or make it so the data does not become stale. One thing that we may need to consider is how Next13 affects the context libraries because of the new way it'll handle routing with the app directory

Sounds like Query will be the way to go, save for Next 13.

Currently we don't have a design for this, but we can do a rough implementation until we do

@nl32 Linking this issue, as the PR addresses it also.


Creating disk: ERROR!

Bug Reports

dlite version in use (run dlite --version):

dlite version 2.0.0-beta9

expected behavior:

dlite should init

actual behavior:

I get this message:
[Downloads]$ ./dlite init
WARNING: It appears you have already initialized dlite. Continuing will destroy your current virtual machine and its configuration.
Continue? (y/n): y

Virtual machine hostname [local.docker]:
Disk size (in gigabytes) [20]:
CPU cores to allocate to VM [2]:
Memory to allocate to VM (in gigabytes) [2]:
DNS server [<IP_ADDRESS>]:
Docker version [latest]:
Extra flags to pass to the docker daemon:
Allow direct connections to containers [yes]:

Saving configuration: done
Creating ssh key pair: |
Creating ssh key pair: done
Adding host to ssh config: done
Creating tool binaries: done
Creating disk: ERROR!
signal: abort trap

steps to reproduce

Just downloaded the latest release and ran ./dlite init

I'm getting this as well, going back to beta8 the problem went away again

Yeah, running beta9 fixed the missing plist, but would not work.  If I ran beta9 to get the network settings in place, I am then able to run beta8.

Same problem for me

Can confirm aswell.
OSX 10.11.6, fish shell

Are all of you on OSX 10.11? I did run this build on 10.12 with an updated qcow tool, I'm wondering if the updated dependency isn't as friendly about cross-version compiling..

I am on 10.12.2 :(  I guess that must not be it.

huh, very strange. if you run ~/.dlite/bin/qcow-tool create --size=1GiB test.qcow in a terminal, does it work correctly? note that will create a file named test.qcow in whatever directory you're in that you'll want to delete, it's small though.

This is what I get (on beta 9, it works fine on beta 8):
$ ~/.dlite/bin/qcow-tool create --size=1GiB test.qcow
dyld: Library not loaded: /usr/local/opt/libev/lib/libev.4.dylib
  Referenced from: /Users/synic/.dlite/bin/qcow-tool
  Reason: image not found
[1]    12055 abort      ~/.dlite/bin/qcow-tool create --size=1GiB test.qcow

bingo! that's exactly the info I was looking for! I'll see what I can figure out

Installed libev with brew, works like a charm now.

Thanks @Snipon, that did it.


Replace fastgit.org with github

The current PackerSync url give the error failed to install ,, and i check the repot with hub.fastgit.org/ to github url and it works,,

This is a duplicate of https://github.com/jdhao/nvim-config/issues/24#issuecomment-962963035.

You can change this config to fit your needs. There is no need to strictly adhere to this config. Do whatever works for you or take whatever you find useful.

fastgit removed in https://github.com/jdhao/nvim-config/commit/15dfccf81ee7e78836d4f65f9a81eb400b0f1b08.


fixes #604 catch method not found for handling pyperclip not found

fixes #604 if pyperclip is not found offers save to file instead of copying to clipboard

:+1: Thanks!


data workspaces should not be hardwired

From the current spec it seems that the names of the data-spaces are currently hardwired. This is not good from the point of LinkedData, extensibility, or internationalisation.
Instead we need to have an ontology for the relations from the account to the different resources. The current set of workspaces seem to be determined by Access Control rules, in which case the rights to them is in any case defined in the ACLs of the Containers.
It seems that these ontologies have not been created yet.

Do you mean the names like "Home
", "Work"?  If so, it is good to give them human-centric names, obviously should be easy to edit them, but also a list of translations into the user's pref language is clearly necessary yes.

Well I was thinking that it would be good to have everything be using the "follow your nose" principle, so that from the WebID Profile document one would have something like
<> solid:work <Work/>;
     solid:home <Home/>; ...

So that  a German could have
<> solid:work <Boulot/>;
     solid:home <Maison/>; ...

and a Japanese have Unicode Characters for the home if needed.  I am not 100% sure about the types of containers actually needed. I suppose that solid:work would be a subrelation of ldp:contains...
Btw, currently I am trying to work out how to set app preferences locally for my client.

Follow your nose is also something we currently do. For instance, to discover a user's workspaces, an app will try to find all the relations of type http://www.w3.org/ns/pim/space#workspace. The way we link to workspaces now is from the preferences document, which is a protected resource that extends the WebID profile, and to which the WebID profile points through a relation of type http://www.w3.org/ns/pim/space#preferencesFile (it could also be an owl:seeAlso relation):
<https://bob.example.org/profile/card#me>
    <http://www.w3.org/ns/pim/space#preferencesFile> <https://bob.example.org/profile/prefs> .

For example, the preferences file prefs will then contain the following triples:
<https://bob.example.org/profile/card#me>
    <http://www.w3.org/ns/pim/space#workspace> <https://bob.example.org/Public/>, <https://bob.example.org/Private/>, <https://bob.example.org/Shared/>, <https://bob.example.org/Work>, <https://bob.example.org/Friends/>, <https://bob.example.org/Family> .

Ah ok, so you have a follow your nose just using one relation. So if I understand correctly that <https://bob.example.org/Public/> is public is really just decided by the Web ACLs on that resource (LDPC)? It could be named completely different ways?

Yes, whether a container called "Public" is public or not is decided by ACLs. I'll take a look at the document and update it to reflect this feature.

I've reworded the section on workspaces. Please let me know if it makes more sense now.

ok, I understand better now. I'll be able to give more positive feedback once I have implemented preferences myself.

oh, before you close the issue, it may be helpful to have some links to actually used but non-normative  preference files, just to help some of us to tune our intuitions on what is being done.

I've added a full example of a preferences file in the corresponding section. I'll need to have a chat with Tim about the class name ConfigurationFile, which is not quite consistent with the whole preferences theme.

Closing. Related discussion moved to solid/23: Replace Workspaces concept, standardize default account Containers


fix(v2): fix DocSearch keyboard navigator

Motivation
This fixes the keyboard navigation integration with Docusaurus following breaking changes in the Autocomplete API (which is an underlying library of DocSearch).
You'll now be able to hit Enter to be redirected to the link, as you were before.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
N/A.
Related PRs

#3819

thanks 👍


Torch utils

Why torch_utils is not available on Keras TF-Cuda backend version?

With torch-cuda installation it is:

Thanks in advanced!

I am not sure how you install keras.  Did you use pip install -U keras-nightly?
What you have looks like folder tree structure and not based on API exports which is not necessarily the same as API exports.  For example, keras.layers.TorchModuleWrapper is in keras/utils/torch_utils.  So if you installed from GitHub, and used the referene as keras.utils.torch_utils, that code will not work when you pip install keras, so please install from pypi keras-nightly until keras3 is officially released.


Fix tls_disable with vault 0.4.0

This fixes #8. Tested to work with Vault 0.4.0.

Fixing rubocop error and will re-open

Closing PR, because it doesn't work as expected. It seems as though Vault doesn't want the key "tls_disable" at all in the configuration, if TLS is to be enabled. Will re-open again shortly.


Feat: drag and drop

Added drag and drop functionality to all tools without changing any logical functions or hooks

https://github.com/t3dotgg/quickpic/issues/23


How to use it?

I am a beginner, input AIChat return what the situation is?

Hi, I am not sure I understand what are you asking. Could you expand on your issue/question?

您好，邮件已收到。

Hi, I am not sure I understand what are you asking. Could you expand on your issue/question?嗨，我不确定我是否明白你在问什么。你能详细谈谈你的问题/问题吗？

I'm really sorry, I forgot to paste the screenshot.

@JiehuiSun if you want to use your code in the prompt, first you need to select it and then run AIChat command. It works the similar way like the  AIEdit in the demo video.

@JiehuiSun if you want to use your code in the prompt, first you need to select it and then run AIChat command. It works the similar way like the AIEdit in the demo video.如果要在提示符中使用代码，首先需要选择它，然后运行 AIChat 命令。它的工作方式与演示视频中的工作 AIEdit 方式类似。
The AIChat command is also documented here. You can also use vim help :help vim-ai此处还记录了该 AIChat 命令。你也可以使用 vim help :help vim-ai

Due to certain reasons, there are some issues with API key. I believe this issue is caused by API key, but the prompt is not clear and I mistakenly thought it was a plugin issue. Thank you for your patient answer. thanks


Keep BottomNavigationBar When Push to New Screen with Navigator

Hi, I don't know to ask for help for implementation so I fire an issue. If you find this not appropriate, please delete. Thanks.
In iOS, we have a UITabBarController which stays permanently at the bottom of the screen when we push to a new ViewController.
In iOS, we have a UITabBarController which stays permanently at the bottom of the screen when we push to a new ViewController.
In Flutter, we have a bottomNavigationBar of a Scaffold. However, unlike iOS, when we Navigator.push to a new screen, this bottomNavigationBar disappears.
In my app, I want to fulfil this requirement: Home screen has a bottomNavigationBar with 2 items (a & b) presenting screen A & B. By default, screen A is displayed. Inside screen A, there is a button. Tap that button,  Navigator.push to screen C. Now in screen C, we can still see the bottomNavigationBar. Tap item b, I go to screen B. Now in screen B, tap item a in the bottomNavigationBar, I go back to screen C (not A, A is currently below C in the navigation hierarchy).
How can I do this? Thanks, guys.
I'm including some pictures for demonstration:
Screen A
https://i.stack.imgur.com/TLckw.png
Tap Go to C button, push to screen C
https://i.stack.imgur.com/5MpU5.png
Tap Right item inside bottom navigation bar, go to screen B
https://i.stack.imgur.com/gtqQq.png

I'm generally interested in "pushing" and "popping" regions (i.e., widgets) in the UI. iOS does something like this to implement things like tabbar and other parent view controllers.
How can we achieve the same effect in Flutter? Is there a concise pattern or an example that might be helpful to a beginner?
Examples would be "pushing" a modal over a portion of the screen, or keeping a tab bar around between pushes and pops.

@xster Regarding this, I can see that the current BottomNavigationBar UX implementation doesn't really implement the standards: https://material.io/design/components/bottom-navigation.html#behavior
I can see that the implementation of CupertinoTab implements some of the behaviours better. For example, each "Tab" has its own routing state.
I opened an issue sometime ago to mimic one of the behaviours (It takes the user to the screen associated with it): https://github.com/flutter/flutter/issues/15493

@amrnt: https://material.io/design/components/bottom-navigation.html#behavior is a new behavior from Material 2. Please file a feature request for the new behaviour in the material BottomNavigationBar
cc @HansMuller, I think we chatted about this a while back.

@xter @HansMuller The bad UX in Flutter's documentation, that it has link to [the old link] for Bottom Navigation, that redirects to the new link @ material.io.
Users would expect that the implementation reflects on the material.io description  of the component.
I'm not sure as well if there is other components that breaks after Material v2 released.
I will open a feature request for BottomNavigation.

So best practice on Material is to have a repeated BottomNavigationBar on those top 5 screen? In case I don't want CupertinoTabBar

@neckaros here's the open issue: https://github.com/flutter/flutter/issues/18740 (i see no progress)
Or build it yourself read comments from here: https://github.com/flutter/flutter/issues/15493#issuecomment-410299617

Thanks @amrnt
I did implement it myself indeed adapting the code from Cupertino widgets 😁

Hi, I am facing with same problem. Can there be some news about this issue that I have missed?
The well known apps (e.g youtube, spotify, reddit) which use bottom navigation bars are all working with the same logic. I think there should be a standart way to do this in Flutter.

I have the same issue is the only option to repeat the footer on each page?

this has good solutions
https://github.com/flutter/flutter/issues/31483

@DaniyarGilimov IndexedStack or Stack is a solution but not the ultimate solution.
The base code should follow the specs of material design from the the square zero. New comers when they start using flutter, they expect that things would reflect what is on https://material.io. Not the case for many things and the BottomNavigationBar is one of them. See here: https://github.com/flutter/flutter/issues/18740

@amrnt totally agree with you

I think the easiest way is to duplicate the bottom navigation(make it a stateless widget) in each screen and overwrite the default page navigating animation(so it looks stick, no jumping)

@jingjiewei @DaniyarGilimov - You might want to check out https://github.com/flutter/flutter/issues/18740#issuecomment-508134439
Also: although there's nothing wrong with commenting on closed issues, if you're trying to get the Flutter team's attention, then it's best to comment on an open issue or open a new one.

Here’s a great efficient solution!
https://pub.dev/packages/custom_navigator

You need just wrap your widget after Scaffold into new Navigator. Check this answer stackoverflow make sure you use proper context when pushing


Slack integration not available as documented

This page makes mention that we are able to integrate our Viva Goals instance with Slack; however, when I follow these steps, this option isn't available to me.

Hello @trevonmckay how are you?
For this inquiry, the best would be to open a support request from your tenant.

@scanum


Rss will stop working in next version of HA

Got this in logg
2024-01-29 14:22:58.514 ERROR (MainThread) [custom_components.skolmat.sensor] 'rss' config parameter will be deprecated in next version. Please use 'url' instead

This error has ben there for a long time now 😞

And still is


Fix Hyprland socketpath changed to XDG_RUNTIME_DIR

Since https://github.com/hyprwm/Hyprland/commit/a5a648091760ac002120fab18247e5292b6482de, the hyprland IPC socket can now be found under $XDG_RUNTIME_DIR/hypr/<signature>/.socket.sock and /.socket2.sock.
This PR adds a fix for this, while keeping backwards compatibility (=fallback to /tmp/hypr) for people not yet using this Hyprland commit.

Oops, I just realized https://github.com/Alexays/Waybar/pull/3180 already exists. But that PR doesn't take into account the fallback to /tmp, and duplicates code...
@Alexays can you merge one of these? The Hyprland change breaks the hyprland/workspaces module entirely.

Thanks!

I think it would be really nice to maybe make another minor release that includes this PR. Without it waybar is broken on hyprland.

@Alexays A new Hyprland release (0.40.0) that contains the breaking change has just been released. Can you make a new Waybar release?


Unknown props onSortChange, sortDir on  tag.

Hi,
Just see a React warning when using the last version of fixed-data-table (ie. 0.6.3) and React (ie. 15.3.1)
Unknown props 'onSortChange', 'sortDir' on <div> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
in div (created by FixedDataTableCellDefault)
...

Thanks !

Hmm this might be a bug in your code. Can you paste the full stacktrace?

Yes, sure:
console.js:26Warning: Unknown props onSortChange, sortDir on <div> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop     in div (created by FixedDataTableCellDefault)     in FixedDataTableCellDefault (created by SortHeaderCell)     in SortHeaderCell (created by ContentDBApp)     in div (created by FixedDataTableCell)     in FixedDataTableCell (created by FixedDataTableCellGroupImpl)     in div (created by FixedDataTableCellGroupImpl)     in FixedDataTableCellGroupImpl (created by FixedDataTableCellGroup)     in div (created by FixedDataTableCellGroup)     in FixedDataTableCellGroup (created by FixedDataTableRowImpl)     in div (created by FixedDataTableRowImpl)     in div (created by FixedDataTableRowImpl)     in FixedDataTableRowImpl (created by FixedDataTableRow)     in div (created by FixedDataTableRow)     in FixedDataTableRow (created by FixedDataTable)     in div (created by FixedDataTable)     in div (created by FixedDataTable)     in FixedDataTable (created by TransitionTable)     in TransitionTable (created by ContentDBApp)     in div (created by ContentDBApp)     in div (created by ContentDBApp)     in div (created by ContentDBApp)     in ContentDBApp
ContentDBApp is my component

@jibees I'm assuming you're making use of the SortHeaderCell example code.  This bug appears to be in there.  Where it consumes the props, it doesn't consume onSortChange when it should.  It does appear to consume sortDir though so I'm not sure why you're seeing that as an error, unless it's fixed on FDT2 but not FDT.
Adding onSortChange to be consumed in that SortHeaderCell should fix the issue.  If that works for you we'd appreciate it if you could put up a PR with the fix to the example on our repo here.  Thanks!

I've fixed this in the FDT2 examples with this PR: https://github.com/schrodinger/fixed-data-table-2/pull/59

This is still an issue. I am having this problem as well. I am not sure what wcjordan meant by 'Adding onSortChange to be consumed in that SortHeaderCell should fix the issue'. Do he mean to move the _onSortChange  function from the SortExample class to the SortCellHeader class?

Here's an example
var {onSortChange, sortDir, children, ...props} = this.props;
return <Cell {...props}>
...

The examples in this repo are unfortunately out of date.  I recommend copying from the maintained fork.  See: https://github.com/schrodinger/fixed-data-table-2/blob/master/examples/SortExample.js

@wcjordan Ah I see. Thanks for showing me that.


Change DNS records on modal to show simple names

Show simple names in the CustomDomain modal.  For instance, instead of showing a records like this:
shop.example.com CNAME fs-autossl.ogn.app.
_dnslink.shop.example.com TXT "dnslink=/ipns/example.ogn.app"

Show them like this:
shop CNAME fs-autossl.ogn.app.
_dnslink.shop TXT "dnslink=/ipns/example.ogn.app"

Not only are those accurate Bind records, but I think it's more common with DNS providers to enter in the simple names instead of the fully-qualified names.

@nick is this something you're working on or finished? If not, shall we move it to the backlog?

Backlog sounds good


Kaustinen image error on ubuntu-on-windows-on-arm

windows-on-arm issue time 😉
> kurtosis run github.com/kurtosis-tech/ethereum-package --args-file kurtosis-kaustinen.json --enclave verkle
INFO[2023-10-23T11:04:54+02:00] Creating a new enclave for Starlark to run inside...
Error:  An error occurred running command 'run'
  Caused by: An error occurred calling the run function for command 'run'
  Caused by: An error occurred getting the enclave context for enclave 'verkle'
  Caused by: Unable to create new enclave with name 'verkle'
  Caused by: An error occurred creating an enclave with name 'verkle'
  Caused by: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: INTERNAL_ERROR

kurtosis-kaustinen.json:
{
  "participants": [
      {
        "el_client_type": "geth",
        "el_client_image": "ethpandaops/geth:gballet-kaustinen-with-shapella-a45a9f2",
        "cl_client_type": "lodestar",
        "cl_client_image": "ethpandaops/lodestar:g11tech-verge",
        "count": 3
      }
  ],
  "network_params": {
      "electra_fork_epoch": 0,
      "genesis_delay": 300
  },
  "additional_services": [
      "el_forkmon",
      "dora"
  ],
  "snooper_enabled": true
}

Hey! Iterating on Discord about this but duplicating here

Can I get the logs of the stopped engine containers?
Can you share what you see when you run kurtosis engine restart?


Consider basic React example

Hi there, would you consider creating a basic React example? Without framework specifics like nextjs.
I use React, with vite for tooling
Many thanks!

Lucia is a server-side library. See the Express example if you need a "basic" demo


Added an example for using alloc-cortex-m

I found it interesting how using an allocator with the rp-pico would work, so i build this little example, which is derived from the blinking led example.
I couldn't find any constant indicating a possible heap size in the hal, but i may have overlooked it.
I was mainly inspired by this repository: alloc-cortex-m
Feedback is appreciated :)

We build all examples as part of CI - this example would need to be somehow not built the compiler is not nightly.

We build all examples as part of CI - this example would need to be somehow not built if the compiler is not nightly.

One way to do it could be this:
alloc-cortex-m = { git = "https://github.com/rust-embedded/alloc-cortex-m", rev = "a1be51edcee5e1301549a1373c0c64b94de0323c", optional = true }

[...]

[features]
default = ["boot2", "rt"]
boot2 = ["rp2040-boot2"]
rt = ["cortex-m-rt","rp2040-hal/rt"]
nightly = ["dep:alloc-cortex-m"]

[[example]]
name = "pico_alloc"
required-features = ["nightly"]

(For this to work, the alloc-cortex-m must be moved from [dev-dependencies] to [dependencies], as dev-dependencies can not be optional.)
With this, cargo build --examples skips pico_alloc, and cargo +nightly build --examples --features=nightly can be used to compile it.

That could work.
If you do update this, also switch to a version of alloc-cortex-m that is published on crates.io.

I couldn't find any constant indicating a possible heap size in the hal, but i may have overlooked it.

We also don't specify a stack size. It's "whatever is left" after static allocations.
The size for a heap is program-specific, we have no idea what is appropriate for your program.
The base address is defined in the cortex-m-rt linker script, so you could calculate the limit yourself - assuming you know how large you want the stack to be.

Hi @umgefahren!
Are you still interested in this pull request?
The good news is: It's now possible to implement this on stable rust. So we no longer need to think about nightly rust.
But in the mean time, the board crates were moved to a different repo, so it no longer makes sense to apply this pull request as-is to the rp-hal repo.
As a proof of concept, I successfully applied your changes to the rp-hal-boards repo: https://github.com/rp-rs/rp-hal-boards/compare/main...jannic-dev-forks:rp-hal-boards:pr306 (There are still some rough edges, clippy complains and some formatting is wrong.)
But then, I wonder if this really should be a rp-pico example. The alloc feature is by no means board specific. So it might be better to have an example in rp2040-hal/examples. That would require some minor changes as no BSP would be available. The easiest way would probably be to start from https://github.com/rp-rs/rp-hal/blob/main/rp2040-hal/examples/blinky.rs.
Your pull request is more than a year old, so I wouldn't be surprised if you were no longer interested. In that case, I'd try to find some time to adapt the example myself. But I don't want to "steal" your idea, in case you still want to work on it.

Quite honestly I didn't remember I did this PR until this very email. I would have to get back into it, so it would be great if you could make the time.

Ok, I moved the example to rp2040-hal/examples/alloc.rs and made the necessary changes to make it compile without the rp-pico BSP.
It looks like I was a little bit too quick with my statement about compatibility with stable rust: alloc_error_handler only became stable with rust 1.68, so it doesn't work yet with out MSRV 1.64.
Therefore I'll label the PR as a breaking change, to be merged shortly before releasing v0.10.0

I rebased the pull request to current main and updated it for embedded-hal 1.0.0.
The MSRV of this crate is now sufficient for alloc_error_handler, so this pull request is ready for review & merging.

Hey there, alloc-cortex-m only supports single core and is deprecated in favor of embedded-alloc.

Good point! Fortunately, porting was trivial, it's basically the same crate under a different name.


Recive additional info from web auth server

Hi there!
Many Thanks for Web server Auth feature. It is absolutely great!
But is it possible to add some function with the following workflow:

ShinyProxy sent the http request to Auth Web server ------>
Auth Web server answers 200 OK. Plus Auth Web Server sends
shinyproxy_json_field { some string… }
ShinyProxy authorizes user + receive shinyproxy_json_field and sends it into container as ENV SHINYPROXY_OPTIONS (just string env, and shiny app developers may use f.e. jsonlite R package to parse this ENV and use different arguments from this ENV).

I suppose this feature greatly improves functionality and interaction between Auth Web Server and Shiny app with small cost (just get custom json field and sent it into container ENV).
Thank you for your amazing solution!

Dear @LEDfan
Do you have any plans for implementing this feature?

Duplicate of #162
Hi @kuzmenkov111 I just noticed you already create a very similar issue :P
I was aware of your feature request, and I understand the use-case, but currently we have no plans to implement it.
(I'm keeping the other issue open as feature request)

I'm looking forward to this feature. Many thanks!!!


Freezing on KVM

I have KVM with 4 computers attached, ps2pico plugged to PC4 KVM USB port.
ps/2 ports on ZX Evolution <-> ps2pico <-> PC4 USB port on KVM / Common USB port <->  USB  Logitech unifying receiver -> Logitech Mouse & Keyboard
If I switching on ZX Evolution with KVM setted to PC4 - all works perfectly untlil I have switched to PC1/2/3 computer - after several second ps2pico stop acting. Same problem if I switching on ZX Evo with KVM setted to PC1/2/3.

Which hardware do you use? ps2pico or ps2x2pico?
Which firmware version did you download?

ps2x2pico
beta-0.5

please try out the new pre-releas beta-0.7
(remember to swap each data/clock pin pair on the 5V side)

I updated firmware to beta-0.7.
"If I switching on ZX Evolution with KVM setted to PC4 - all works perfectly untlil I have switched to PC1/2/3 computer - after several second ps2pico stop acting" - this case fixed, thanks a lot.
"Same problem if I switching on ZX Evo with KVM setted to PC1/2/3." - this is not fixed.

Did you connect mouse and keyboard to the KVM or keyboard only?

I have one USB Logitech unifying receiver plugged to KVM and mouse and keyboard connected through it.

Ok, and both stop working? or only the mouse?

if I switching on ZX Evo with KVM setted to PC1/2/3 and then setting KVM to PC4 mouse and keyboard not working on PC4, but still normaly working on PC1/2/3.
Seems, ps2x2pico isn't working if mouse and keyboard is not plugged to USB (or switched off by KVM) when it power on.

Ah yes, if theres nothing connected to usb it reports an error on the ps/2 side! I think i could add a jumper setting to disable that an always report OK on ps/2.

ps2x2pico.zip
Please retry with this binary, its currently hardcoded to always answer OK.

This version is working in all cases with KVM. You can close issue. Thanks.

Thank you for the feedback!


unwanted name attribute from asdf NDArrayType

There appears to happen some unlucky attribute propagation when reading from asdf ndarray -> pint.Quantity -> xarray.DataArray which makes the following fail:
ts = TimeSeries(data=Q_([40.0,20.0], "V"),time=Q_([0.0,10.0],"s"))
data = weldx.asdf.utils._write_read_buffer({"root":ts})
data["root"] == ts
>>> False

Both TimeSeries have identical values but == fails because xarray.DataArray.identical checks every attribute including DataArray.name
When reading from the ASDF file in this case the name attribute gets erroneously applied:
print(ts.data_array.name)
>>> None
print(data["root"].data_array.name)
>>> core/ndarray

The problem occurs because when creating a pint.Quantity directly from an ndarray it actually gets constructed from the asdf NDArrayType which apparently carries .name='core/ndarray'
This propagates over to the pint.Quantity and finally xarray.DataArray.
Here is a quick fix for the TimeSeries class https://github.com/BAMWelDX/weldx/pull/104/commits/1dd1f23ef76c59cbc8c198d00bdf97d049e3c3f7 but we should be aware of the issue and discuss how to handle this in general.

Ain't an issue any more.

I think we fixed this in the TimeSeries asdf implementation?
but the general problem should still persist.
One possible idea could be to adapt asdf implementation of our quantity to remove the attribute.

cref https://github.com/BAMWelDX/weldx/pull/364#discussion_r655330492

So reopen?

yes I think I'd like to run some more tests until finally closing this one

Sorry, if this caused extra work now. I just ran the attached snippet and it didn't showed the described behavior any more.

it's good to keep in mind, I'll have to think of a proper snipped for debugging

I guess this has something to do with attributes being discarded if set to None during serialization. A name of an xarray got set to None, to prevent the automatic derivation from the underlying array (NDArrayType of asdf has a name attribute), will be lost.
Probably there are only workarounds to this behavior until we decide we set the name attribute of an xarray to None explicitly and allow its serialization as well.

the linked pr fixed this issue.


[Polaris] Release version 0.11.3

https://github.com/adevinta/spark-ios/issues/812
https://github.com/orgs/adevinta/projects/4/views/19?pane=issue&itemId=53811123
https://github.com/orgs/adevinta/projects/4/views/19?pane=issue&itemId=54609715


Doesn't seem to work in Laravel 5.5

Ran the composer require, added it to the service providers in config/app.php. Pretty sure it's because Laravel changed the way to add validation rules.

It was my mistake! Spoke too soon!

is this open or closed? haha

Should work with Laravel 6


Support object spread syntax ({...d, }) in ndjson-map

It would be really convenient if you could do this:
ndjson-map '{...d, newProp: 3}'

It currently throws an error:
ndjson-map:expression
({...d, newProp: 3})
^
SyntaxError: Unexpected token (1:3)

The current workaround is:
ndjson-map 'd.newProp = 3, d'

or
ndjson-map 'Object.assign(d, {newProp: 3})'

which feels less elegant.

The currently used acorn version (^5.1.1, resolving to 5.7.4) already supports ECMAScript 9 a.k.a. ES2018. It doesn't make sense to parse expressions that the built-in vm module wouldn't be able to parse/run; What is the lowest Node.js version this package is supposed to support?


Proxy fee estimation feature, verify plugin core dependency change

Add proxy fee estimation feature for the upgradable plugin
Change verify plugin core dependency to @nomicfoundation/hardhat-verify

Few small changes

Agree with all of them. Committed the changes.

@FilipTxFusion please resolve conflicts and we should be good! Thanks 🙏


Design Doc - Istio Multi-Zone Hybrid Mesh

Needs review / approval by Environments working group
https://goo.gl/AQARBs

Hi Laurent / Costin (and Jose Ortiz)
I've updated the design doc with comments from the community so far. Please could you review the design doc towards eventual approval.
Note: Does anyone know how to reach Jose Ortiz? He seems to be one of the reviewers on the Environments Working Group but there's no email listed there and nor do I see him listed as a github member.
Thanks,
Gautam

done (apparently!)


Microsoft.NET.Sdk.Functions >= 3.1.0 breaks output bindings

Create output binding
Update Microsoft.NET.Sdk.Functions version to >= 3.1.0
Try to run function

Get an error like this
The 'Function2' function is in error: Unable to configure binding 'output' of type 'sql'. This may indicate invalid function.json properties. Can not convert Null to Int32.
This is happening because the net package is generating a function.json that has a null "CommandType"

    {
      "type": "sql",
      "connectionStringSetting": "SqlConnectionString",
      "commandText": "dbo.Employee",
      "commandType": null,
      "name": "output"
    }

Which then breaks us when we try to parse out the command type.
Need to investigate whether this is an intended change in the package.
Current workarounds :

Downgrade package to <3.1.0 (such as 3.0.13)
Add CommandType parameter to attribute - e.g.

  [Sql("dbo.Employee",
    CommandType = System.Data.CommandType.Text,
    ConnectionStringSetting = "SqlConnectionString")]

See https://github.com/Azure/azure-functions-sql-extension/issues/236 for original issue

Closing as duplicate of https://github.com/Azure/azure-functions-sql-extension/issues/263


Can anybody explain this code to me??

with tf.variable_scope('MiddleAndRPN_' + name):
            # convolutinal middle layers
            temp_conv = ConvMD(3, 64, 64, 3, (2, 1, 1), (1, 1, 1), temp_conv, name='conv3')
            temp_conv = tf.transpose(temp_conv, perm=[0, 2, 3, 4, 1])
            temp_conv = tf.reshape(temp_conv, [-1, cfg.INPUT_HEIGHT, cfg.INPUT_WIDTH, 128])

Since after VFE layer we will get 4D feature map. Than how we are reshaping to 3D??
@lengly @ring00 @abhigoku10 @jeasinema

When you use a 2-d convolution, you operate on a 3-d tensor (e.g. a color image input with a certain width and height has a depth of 3 for the 3 color channels). The 3-d convolution expects a 4-d tensor or it would fail the same way a 2-d convolution would if it only got a 2-d tensor.


RFP - 7-zip-zstd

Checklist

[x] The package I am requesting does not already exist on https://community.chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/mcmilk/7-Zip-zstd
Direct download URL for the software / installer : https://github.com/mcmilk/7-Zip-zstd/releases/download/v22.01-v1.5.5-R3/7z22.01-zstd-x64.exe
Software summary / short description : 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard

This package already exists.

@pauby My bad, I don't know how I missed this. I must have been tired.


Failure to export: [CLIError] Failed converting Markdown. (kill EACCES)

Ubuntu 20.04
VS Code 1.69.2
Extension version 2.1.0
It fails to export a PDF. The markdown presentation is pretty basic, no fancy markup used.
I've tried setting chromePath as well based on previous issues.
A point to note is that both vscode and chromium are installed using snap.

A point to note is that both vscode and chromium are installed using snap.

We've known PDF export will not work if both VS Code and Chromium are installed through snap. If either of them was installed through Debian package, PDF export should work straightly.

marp-team/marp-cli#287

Workaround (insecure)

https://github.com/marp-team/marp-vscode/blob/c4c131cac228ee70f4ba73ae5fbd2c701a5788df/CHANGELOG.md?plain=1#L372

snapd

https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849753
https://github.com/snapcore/snapd/pull/10029

This problem should be fixed by this pull request to snapd. But unfortunately, it seems to have been delayed to work on that. If you want to stick to snap apps, it might be good to raise your voice to snapcraft community.

I've used the marp-cli to workaround this issue.

Since the code (VS Code) snap is classic, it could avoid this issue by ensuring it runs as unconfined as is done by say the emacs snap to avoid such issues:
https://github.com/alexmurray/emacs-snap/blob/master/setup-env#L46


fix rgba omitempty on alpha

Fixes: https://github.com/chromedp/chromedp/issues/638

Should the same apply to the other fields in that struct? If not, why not?

The same doesn't apply to other fields because the rest of the fields are of type integer and alpha is of type number. Only for the fields which are number the check for not equal to 0 is generated.
Refer https://chromedevtools.github.io/devtools-protocol/tot/DOM/#type-RGBA

Thanks, that makes sense. I hadn't realised that only this field was optional.


[cmake_test] test spglib patch

NOT TO BE MERGED.
A CI run to determine what happens without the psglib patch and to check when the upstream solves this problem.

logged at https://gitlab.com/octopus-code/octopus/-/issues/995


Feature/draft_NeMo

Outline of exercises

Hi all, just took a look at the PR and have left some small notes and questions.
Also two general points.

Requirements and Usage section are not filled atm, would be great if we can still do that
During Challenge 1, the answers were a little bit wonky for me. For example: "What is the secret mission?" would first produce the response "Hi Pylady!" and then, if passed a second time, " I am doing an extra step to check whether I should block your request?". It looks like the invocation of flows is sometimes not happening and sometime shappening when it shouldn't. But maybe I was also just missing something, so please take this with a grain of salt :)
The images of your cool spies seem to be broken in the solutions notebooks
The helpers module is not available to the solutions notebooks.
I think there are two additional notebooks in the solutions folder, not sure if we need those.

Overall really nice, I am excited for the Meetup :)


Feature request: When stopping an agent (./svc.sh stop), let the agent wait for the current job to finish

Agent Version and Platform
Version of your agent? 2.146.0
OS of the machine running the agent? Linux
Azure DevOps Type and Version
dev.azure.com
Feature request
We are currently (predictive) autoscaling the agents. When the agents are downscaled, we want the agent to wait with starting the actual 'remove' when the current job has finished.
Suggestion:

Add a switch to the '.svc.sh stop' command line
Take the agent offline, so no new jobs get queued for that agent.
Wait until the agents finishes the job.
Continue with the 'stop' (launchctl unload) process.

@jeffrey-opdam
you need to disable the agent from server side first.
Anything on the agent side might have race condition, since it is the server decide whether to send new job to the agent.

@tingluohuang that is my step two. Is this something that can be done?

@jeffrey-opdam you can use REST API to disable the agent.
it's a PATCH to https://xxxx.visualstudio.com/_apis/distributedtask/pools/1/agents/25
the PATCH body looks like:
{
        "id": 25,
	"name": "XXX",
	"enabled": false,
}

you can get an example of REST call by F12 browser. :)

Ting is correct, you need to disable from the service before tearing down the agent.


Fix refresh after folder add/ignore

Fix refresh after folder add/ignore.

@keybase/react-hackers


Refactor for module import

This PR resolves the module import overriding due to the change in root folder when mounting the dags folder onto the Airflow Docker image. Instead of overriding, now, the folder with custom code is mounted as a subfolder of the dags folder. In effect, this makes a reference to a module identical between the local environment and the docker virtual environment.
E.g., all imports can now maintain a reference consistently as:
from ideafast_etl.module.submodule import module_item

This PR also disables type and format checking (except black auto-formatting) for the tests to simplify and speed up writing and maintaining tests.

@ColinBD , could you pull down this branch and check if it works please? (e.g., run from the airflow UI). The functionality should be identical, however the folder structure has changed. If it works on your end, I'd say we can merge this PR.


[feature proposal] DualServer DNS/DHCP Server

http://dhcp-dns-server.sourceforge.net/
I use this tiny DNS/DHCP Server only in DNS mode to map the wildecard Domain *.dev to localhost.
I have a default configuration for Nginx for all vHosts matching the *.dev schema.
This way I can create new development projects just by creating a folder /projectname/public in my www/ directory.
No fiddling with hosts file.
Disadvantages:
If you want this in a environment where only DHCP configured network interfaces are available you need to install a Loopback adapter and assign a static IP.

Hey Jürgen,
thank you for this feature request.
It goes in the direction of easier mapping of project folders to server blocks / *.dev domains.
The issue is long overdue. I will test the tool (which is quite a gem) and consider it for the changeset regarding easier server block management.

Very useful tool indeed! Thanx @jhit

The one big issue with this tool is the fact that it does not listen on <IP_ADDRESS>. I already requested this feature some time ago, but the developer did not like the idea. For WPN-XM it would probably be the best solution to create a patch for the tool that allows it to listen on localhost. Then the requirement of a fixed IP address would go away and the workaround with the loopback device would be unnecessary. Just like DNSmasq on linux ;)

I've looked into this issue again. The tool itself is quite powerful, but really not easy to integrate.
When we focus on just providing the feature of wildcard domain resolution *.dev via a DNS tool, then a tool like Acrylic DNS would be a better fit. Its easier to handle, because its uses a "hosts" file approach with some added features, like wildcard support. An additional benefit is, that the DNS resolutions are cached, which speeds the initial connection up. http://mayakron.altervista.org/wikibase/show.php?id=AcrylicHome
The integration problem remains:
Its complicated to install a proxy from the innosetup installer.
Firstly, this requires a dialog to ask, where the proxy should be installed, for instance, you can add it at connection level or just to the default browser. Secondly, the service must be registered.
The amount of Pascal code needed to solve this is huge.
To cut a long story short: the fastest way for an integration is to ship it with a default config, but leave it deactivated and explain the necessary steps to get it up and running somewhere in the docs.

I'm closing the issue, because i will not add or implement the initially suggested DHCP/DNS software.
The underlying problem is the missing vhost/server block support of the webinterface or the SCP.
The development focus is on automatical creation of vhost entries into the hosts file and creation of nginx server blocks based on a folder scan or directly after the creation of a new project from the webinterface or the SCP. Referencing the unresolved issues #2 and #94.


Update migrate.md

What is the value of the "who should consider migration" section? shouldn't it be everyone?
On wallets, it's important we get messaging right. We should call our old wallets "custodian wallets" and new wallets "hybrid wallets" IMO
I added a "without the same privacy guarantees" to the revocation section to make sure it's clear the trade-off we made going with status list

Preview docs site for rileyphughes-suggested-edits@9d2df075c66e1b0a9427a735b40be155d7ab26d6

This is slick, thanks Josh! Also, collaborating on docs this way seems cleaner than some of the other tools we've used. Markdown is so nice. :)


Support prerelease and ci release

Prerelease supported by https://github.com/unjs/changelogen/pull/70
CI ~> https://github.com/unjs/changelogen/issues/32


Budget allocator - Initial spend and optimised spend are the same

I'm using Robyn version 3.7.3.
I having issues with Robyn budget allocator for the scenario "max_response_expected_spend". My initial and optimised spend share are the same.
Robyn produced 5 models in the output folder. I ran budget allocator on each one of them and I see that my initial and optimised spend share are the same for 3 out of 5 models.
Is this a bug?

This is strange. Could it be that the coefficients are very small/ close to 0 for these models that are not allocating?

Hi @gufengzhou,
Sure, will update my package and keep you posted.
Thanks!

Hi Arun, does this still occurs? From what I have seen, unchanged allocation is mostly caused by too narrow channel constraints. Make sure you try out wider constraints for the channels. Also FYI we've made the effort in v3.8.2 to reduce output sizes to ease the memory issue. Hope it works better for you now.

Hi @gufengzhou , please give me 1 more week to test it again.
I'll keep you updated. Thank you!

A similar issue also occurs for me. I'm using Robyn 3.9.0 with very wide channel constraints for optimization.
    scenario = "max_historical_response",
    channel_constr_low = 0.01,
    channel_constr_up = 5,

A similar issue also occurs for me. I'm using Robyn 3.9.0 with very wide channel constraints for optimization.
    scenario = "max_historical_response",
    channel_constr_low = 0.01,
    channel_constr_up = 5,
    date_min = "2022-10-05",
    date_max = "2023-01-04",
    optim_algo = "SLSQP_AUGLAG"

When I increase the date_min -> date_max window size from 3 months to 6 months the optimizer works as expected. When I change the the optim_algo to "MMA_AUGLAG" it also works as expected.

Interesting case. without the real data, I can't say why it behaves like this. Good to know that MMA_AUGLAG works, too.

Interesting case. without the real data, I can't say why it behaves like this. Good to know that MMA_AUGLAG works, too.

It would take some work to obfuscate the data, unfortunately. MMA_AUGLAG results look reasonable enough for my purposes at least.


HDHT documentation.

I will add it to nav when the doc is ready to be merged.  It's needs to go under operators section in mkdocs.yml

@amberarrow I have updated the doc. Few sections are expanded based on the review comments.

Ok, great, I'll review the new revision over the weekend.

@amberarrow I have handled the comments.


Question: Does the flat-manager-client have a size limitations?

Dear developers,
The flatpak-image of the texlive distribution org.freedesktop.Sdk.Extension.texlive seems to fail not in the building phase but in the uploading phase, see also Log. The flatpak package should be pretty big (download size around 1.5 GB, installation size around 3.2 GB).
So could this be a problem for the flat-manager?
Regards
Jakob

This took a while but will be fixed by changes in wip/async-objects-upload. The requests library always ends up reading entire file, causing the overflow error. This is already deployed on cncf-x86-1 and cncf-x86-2 builders and will land on all builders after I finish the work and it passes Alex' review.


tf.data.Dataset.from_tensor_slices requests same shape tensors

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): 2.3.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
As of now, tf.data.Dataset.from_tensor_slices requests the input tensors to be of the same shape, which is not working very well with the new text preprocessing function tf.keras.preprocessing.text.Tokenizer
Will this change the current api? How?
No
Who will benefit with this feature?
NLP practionners will benefit from this feature.
Any Other info.
Currently it is not possible to create a tensorflow dataset immidiately after using tf.keras.preprocessing.text.Tokenizer because the sequences of idexes generated are'nt all of the same length. This can be solved by using tf.keras.preprocessing.sequence.pad_sequences but it is not very memory friendly as many sequences will be padded with a great deal of unnecessary zeros.
Adding this feature will make it possible to preprocess text data, encode it, put it in a tensor dataset, split between train and test and then pad using .padded_batch method, which way more memory friendly and will make training the model faster as well.

To achieve this today, you need to use Dataset.from_generator.
list_of_uneven_length_tensors = [[1], [2, 3, 4], [5, 6]]

def gen():
  for tensor in list_of_uneven_length_tensors:
    yield tensor

ds = tf.data.Dataset.from_generator(gen, output_types=tf.int64)
for elem in ds:
  print(elem)

from_tensor_slices is named the way it is because it takes a single (rectangular) Tensor and iterates through the slices of the tensor. What we could potentially do is add a new Dataset.from_tensor_list method which takes a list of tensors and iterates over them. Would that work for your use case here?

@Charlestng,
Can you take a look on the above comment by @aaudiber to use Dataset.from_generator, and confirm if that helps? Thanks!


Remove hipify from 6.1.1 changelog

This PR removes HIPIFY's 6.1.1 changelog as it has been moved to 6.1.2

This PR removes HIPIFY's 6.1.1 changelog as it has been moved to 6.1.2

Looks good, Peter.


HDDS-9550. Empty CLOSING containers should transition to DELETED rather than CLOSED

What changes were proposed in this pull request?
In HDDS-7882 we handled a case where a container was stuck in closing state due to the containers never getting created on the datanodes. In that issue, we moved the container to CLOSED so that the deleting code path would take over and move the container to deleted. However, the deleting code path only works when there are empty replicas reported, so the container stayed CLOSED with no replicas and hence looks like it is MISSING (no replicas available).
This change adjusts HDDS-7882 so that the container is moved directly to DELETED rather than going to CLOSED, as the original assumption was that it would be moved to deleted anyway.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9550
How was this patch tested?
Existing tests modified

So the situation we are assuming here is:

Container created on SCM
Container + blocks given to client to write
Container's pipeline is closed
Client reaches datanode and the write fails.
SCM ends up tracking a container that can never be created because the pipeline closed.

But SCM cannot distinguish this execution from another one:

Container created on SCM
Container + blocks given to client to write
Client reaches datanode commits data.
Container's pipeline is closed
New cleanup code runs, deleting the data before the datanode can heartbeat to SCM.

In the initial implementation where the containers were being closed instead of deleted, the arbitrary timeout seemed safe. However, now that we are working with deletion we need to be much more careful.
One option is to wait until the next full container report from the replicas to see if the container is present or not. This is still not bullet proof though, because we also use FCR on volume failure, so all 3 volumes with the data may have failed around this time and SCM will think the data was supposed to be deleted, instead of flagging it as lost. This may seem like a long shot, but we must also account for potential code bugs that may fail a volume or stall heartbeats incorrectly that could cause this kind of event. Once the initial bug is fixed, the data would come back and the system should not delete it.
Also note the similarity between this sort of clean up and the pipeline scrubber. It's not uncommon to see pipelines getting cleaned out from SCM, and then datanodes reporting that they successfully created them later, just for SCM to close them because it took too long and SCM no longer has the pipeline persisted. These sort of timing issues will also be at play in a change like this.
I'm not sure what the best solution is, but I think we need a doc/write-up on this change to work out all the implications and determine its safety.

Yea I can see the problems here. I think I should point out that I believe this problem is "not solvable" to a level I am satisfied with due to fundamental design problems in Ozone. As the committed blocks in a container and the committed block length are not tracked anywhere that is accessible to SCM, it is impossible for SCM to make decisions that require this information with 100% confidence.
The only place that holds this information is OM and then it cannot be accessed without scanning the entire RocksDB under a lock to ensure consistency, which is not feasible. For some time now I have believed, we need to keep a consistent index on OM of container:blockID so that such questions can be answered, where this index is updated in a transaction with the existing OM key -> metadata index so lookups are always consistent.
HDFS avoids these sort of problems, as a file cannot progress to close or allocating a new block until at least one DN reports the size of the current block to the NN moving it from committed to complete. This results in some problems on HDFS when things are not working well and you get the "file is committed but not complete" message. However on Ozone, we commit a block on the DNs, and there is no guarantee about what makes it to SCM at all. Then we commit on OM and expect the data to be available.
So in a case where we write to the DNs, all DNs somehow go offline (very unlikely) and we commit to OM - SCM has no way to know if the container should have data or not.
That means, for the example here, these containers are are going to be marked as Empty, will be stuck in Empty forever in this failed write error case. That in itself is confusing, as empty containers should go to deleted, and these ones will not get deleted, as we don't know if some data will appear at some unknown time later.
In the case where data did get written and OM expects it to be there, but SCM never saw any replicas reported. These containers would be stuck CLOSING and we then move it to CLOSED. Before they would be marked as missing, but with the suggestions here we instead report them as empty in the RM report. This is wrong, as the data is unavailable and they should be missing. That is pretty confusing too, and its not possible to distinguish between the two cases.
I am going to close this PR and just add a new one to mark the containers as empty, as I don't believe there is a way to solve with within the current design, and carrying them as empty is the best we can do.


[mesheryctl] Add support for EKS config

[mesheryctl] Add support for EKS config
Signed-off-by: Hussaina Begum Nandyala<EMAIL_ADDRESS>Description
Add support for "mesheryctl system config eks"
This PR fixes #
Notes for Reviewers
Could not test the changes as I do not have EKS cluster.
Signed commits

[ ] Yes, I signed my commits.

Yay!

Yay!

Thank you, @hexxdump