Prepare Release 1.11 branches

Modified version of https://github.com/istio/istio/issues/31627 (from 1.10)

This issue aims to track all steps needed to prepare the release 1.11 branches/builds.
This issue was created early to help document the steps using some new automation (I hope) as well as any ordering changes, etc. Please update/add additional steps taken here so we can document for future releases.
See https://github.com/istio/istio/issues/24473 for steps used for the release 1.7 branch cutting; (note: 1.8 will be more relevant, see https://github.com/istio/istio/issues/27993). Note that was before automation, but does have pointers to PRs to see what some of the steps did. Note that the actual coding steps done by the automation steps are left in this issue for reference only. You only need to run the automated steps, and not the individual instructions. Also note that the reference steps may be INCOMPLETE as the automation is updated, not necessarily the reference steps.
For now, the code to run is in https://github.com/istio/release-builder master branch. From within that branch, one can do a make shell and then within the shell run REPO_ORG=myorg STEP=x ./release/branch.sh (you can update the STEP in the trigger-branch file and not set it manually). This generates the changes for review (trygit status or git diff).  Adding DRY_RUN=false will cause the PRs to be created in the REPO_ORG.
Note that the automated steps 3 and on require the new release's branch in the various repos which are created by automated step 2.

[x] Set up release manager team - Make sure the new team has write access to the repositories. (done here and here)

[x] Send an announcement on Discuss pre-announcing branch cut (adding, but are branch cut notifications needed and where?)

[ ] Send an announcement on Discuss announcing the start of branch cut and to stop merging of PRs (adding, but are branch cut notifications needed and where?)

[x] Build new base images: 1.12-dev.0. Run tools/build-base-images.sh. You may also update the 1.11-dev image to fix existing CVEs, although new code should create these automatically when you try the first 1..11 build. (reach out to @howardjohn or possibly @brian-avery)

[x] (Automation step=1) Update dependencies. This must be done before branching so that PRs can be easily backported later.

Check if github.com/envoyproxy/go-control-plane dependency needs to be updated (to master?). Ask Kuat.

https://github.com/istio/istio/pull/33976

Run the following command in istio/istio UPDATE_BRANCH=master ./bin/update_deps.sh; make gen

https://github.com/istio/istio/pull/33974

[x] Merge PR in istio/istio. Wait for it to complete.

[x]  (Automation step=2)  (new step because we are waiting on prior change to master before branching) Create a release-1.11 branch in every Istio repo - run commands export org=xyz ; export repo=xyz ; (git clone git@github.com:${org}/${repo}.git && cd $repo && git checkout -b release-1.11 && git push --set-upstream origin release-1.11).

[x] istio/istio
[x] istio/pkg
[x] istio/api
[x] istio/proxy
[ ] istio/envoy Not needed - we are using upstream envoyproxy/envoy
[x] istio/client-go
[x] istio/tools
[x] istio/common-files
[x] istio/gogo-genproto
[x] istio/release-builder
[x] istio/enhancements
Explicitly skipped: istio-releases/pipeline, istio/tests, istio/istio.io, istio/test-infra
[x] No PRs to merge as the new branches were created by automation

[x] Set up branch protection. Modify prow/config.yaml in test-infra to add release manages as owners for a branch.

https://github.com/istio/test-infra/pull/3430

[ ] (not automated) Adjust istio/proxy to correct version of istio/envoy. Requires istio/envoy to be set up for new release. We point to envoyproxy directly now?, so this step may be a little different. I don't think envoy has cut their new version yet, so maybe point at their main branch. Not needed - we are using upstream envoyproxy/envoy

[x] (Automation step=3) (doesn't work locally, appears to need credential to add a tag to an existing build-tools image)(new step because this might need to be done separately) Set up prow on release branches go run generate.go branch 1.11 (Note: Needed to run postsubmit in next step) (Contact Googler or ping in #test-and-release slack channel for help).

https://github.com/istio/test-infra/pull/3442

[x] (Automation step=4) (new step since we want the automation from prior step to actually create the image after PR merges)

[x] Updates istio/tools to build new release-1.11 build image (update BRANCH in docker/build-tools/build-and-push.sh. PR postsubmit will create new container images whose name will be used in the next step)  eg: https://github.com/istio/tools/pull/1397
Update common-files in new release. You first have to manually update the common/Makefile.common.mk update-common target to point to the new release  (but not in common-files). The next step will cause the prow automation to actually call make update-common in these repos to do the actual make update-common against the new common-files release branch

[x] istio/common-files - skipped. Covered in next step
[x] istio/istio
[x] istio/pkg
[x] istio/api
[ ] istio/envoy Not needed, we didn't branch envoy for 1.11
[x] istio/client-go
[x] istio/gogo-genproto
[x] istio/proxy
[x] istio/release-builder
[x] istio/tools

Update CODEOWNERS to contain only the release managers for this release. Command: export org=xyz ; export repo=xyz ; (git clone git@github.com:${org}/${repo}.git && cd $repo && git checkout release-1.11 && git checkout -b release-1.11-codeowners && echo '* @istio/release-managers-1-11' > CODEOWNERS && git add CODEOWNERS && git commit -m 'Set release managers as CODEOWNERS for release-1.11' && git push --set-upstream origin release-1.11-codeowners).

[x] istio/istio
[x] istio/pkg
[x] istio/api
[ ] istio/envoy Not needed, we didn't branch envoy for 1.11
[x] istio/proxy
[x] istio/client-go
[x] istio/tools
[x] istio/common-files
[x] istio/gogo-genproto
[x] istio/release-builder
[x] istio/enhancements

[x] Stop publishing latest tags
Update istio/release-builder branch changes from master to new release in build.sh, publish.sh and manifests.

https://github.com/istio/release-builder/pull/710

[x] Merge PRs from STEP 4. Wait for the new build images to be created at https://gcr.io/istio-testing/build-tools.

[x] (Automation step=5) (new step since we need image from prior step) Update istio/common-files to set release-1.11 build image (Update the UPDATE_BRANCH in files/common/Makefile.common.mk to be the new release name, and IMAGE_VERSION in files/common/scripts/setup_env.sh  to be the new build image from prior step (found at https://gcr.io/istio-testing/build-tools)

https://github.com/istio/common-files/pull/453

[x] Merge PR from STEP 5. Wait until step 5 PR merges and all the postsubmit generated PRs (to update common files in repos) merge.

Additional steps that still need automation (if possible)

[x] Add new label: cherrypick/release-1.11: https://github.com/istio/bots/pull/386

[x] Create a 1.12 milestone: https://github.com/istio/bots/pull/387

[x] Bump master to version 1.12

[x] Update Istio: 1.11.0 to 1.12.0, 1.11-dev to 1.12-dev, etc: https://github.com/istio/istio/pull/34052

[ ] Send an announcement on Discuss announcing branch cut complete and PRs can be merged again (adding, but are branch cut notifications needed and where?)

[ ] Add release lock for release 1.11 in master branch of API repo. See https://github.com/istio/api/blob/master/scripts/check-release-locks.md

[x] Publish a beta release (from https://docs.google.com/document/d/1ilwz-HGSeiRDCFwP5rm-5d_UY6OOYL_nflx7bNggek0/edit#heading=h.qex63c29z2to, builds on release branch are labeled beta. Updating below names to reflect that.

[x] Trigger a 1.11 beta.0 build
[x] Some verification to verify build is good
[x] Publish a 1.11 beta.0 release

[x] Send an announcement on Discuss announcing availability of beta. May wait and add something about starting the first round of community testing. (Done in Slack)

[x] Ask istio.io team to run job to update to use the 1.11 branch (probably @ericvn)

https://github.com/istio/istio.io/pull/10082

[x] Run the long-running tests on the dev builds (I asked Xinnan Wen on Slack)

The release has been cut, closing this out.


Merge Spring Cloud Azure 5.1.0 to feature/spring-boot-3

Description
As title.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

azp run java - spring - tests

/azp run java - spring - tests

API change check
API changes are not detected in this pull request.

/azp run java - spring - tests

/azp run java - spring - tests


add link to jsnark snark compiler

I'm going to fix some build issues https://github.com/akosba/jsnark/issues/7 and then merge this.


Fix #229 - Remove underscore dependency

This fixes #229 and should enable #190. I refactored all the instances of underscore with the es6 equivalent or by adding it to a new util.js module. The unit testing in this library is excellent, I don't think this would have been as straightforward without the them.
The process of refactoring went something like this:

Remove all the unused underscore imports; they were everywhere.
Replace monolithic import with es module imports
Replace functions with equivalents if it was easy

Arrow functions remove most of the bind usage
includes and some other array functions were straightforward

Replace uniqueId with the implementation straight out of underscore
Replace escape with the set of maps from underscore, with some tests to validate behavior.

Here are a bunch of links that I referenced:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes
https://stackoverflow.com/a/51399754
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/at
https://developer.mozilla.org/en-US/docs/Glossary/Shallow_copy
https://underscorejs.org/docs/modules/uniqueId.html
https://underscorejs.org/docs/modules/escape.html
https://stackoverflow.com/questions/6234773/can-i-escape-html-special-chars-in-javascript

I'm very happy to have one less library to depend on. Thank you @acmiyaguchi (and @vidjuheffex #261)!


Bring 4Minitz to Docker for a simple demo server experience

What we need

[x] Create docker hub account
[x] Put Dockerfile into .docker
[x] Put BUILD.sh into .docker
[x] Put 4minitz.sh launcher into .docker
[x] Deploy develop/ images to docker hub
[x] Introduce docker image on project README.md

Done with d0410262777777b6f0e9be02ba1971aaf69c2278


Arduino Drone

Is your proposal related to a problem? Please describe.
Build a Drone setup with Arduino.
Add any other context or screenshots about the proposal request here.
Issue made under GSSoC'22 contributions.

`int hello
int bye
void setup()
{
Bye
}
`

Amogus


[FEATURE] package specific no-op logging

Requirements
To improve performance we should be able to disable logging packages within flagd, such as disabling the logging for the service while preserving those from runtime and sync, this no-op logging implementation should also bypass the setting of fields on the logger, bypassing the sync.Map and further improving the performance
This can be done through arguments such for example --disable-service-logging or --logger-args=disable-service-logging

Yep, I think this is needed. Any opinions on if this no-op logging should be the default with the operator?

Yep, I think this is needed. Any opinions on if this no-op logging should be the default with the operator?

This is now the default behaviour as this feature is controlled via the --debug


Access Denied Error When Using uploadprovider.s3 Instead of SeaweedFS

As mentioned in the documentation:
This chart deploys SeaweedFS S3 as an upload provider. You can use AWS S3 or any other external S3-compatible storage as an upload provider. Just set seaweedfs.enabled to false and configure the external S3 provider in ctfd.uploadprovider.s3.
I assume this also applies to the GCP storage buckets and have followed all the steps outlined above, and while the upload screen is displaying, the logs indicate an error: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: Access denied.

This SA<EMAIL_ADDRESS>has Storage Admin Role
Here are the relevant configuration details:

uploadprovider:
  s3:
    # AWS S3 bucket name
    bucket: "ctf-storage"  # external bucket (please disable SeaweedFS as mentioned)
    # AWS S3 bucket region
    endpoint_url: "https://storage.googleapis.com/"  # Consider changing to the correct URL
    # AWS S3 bucket access key
    secret_access_key: |
      {
        "type": "service_account",
        "project_id": "utility-lock-434506-m6",
        "private_key_id": "f2e1013b1e20f31d8da5ba3b527",
        "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDBVXh2rTOX5G8Y\nVPvhQ/dc2LuajaOpOjFpRjnzt4qTU7tvKpBHTZFPCcL3VezfH39TYcoKCoiQzX7V\n/PoZxfn/QuJGngZ2GmHhjr5art7lhL8zLpE+KpswVxQv3603TumMllUEexu8tgbn\nyBO5MrYCkHvOFY2vtn2/hUdwWhnpNj4GRkaV/0TvLhw62plixb3hosDlaFpUQcbn\nY1OVyKwQyKh/heu8gxME0llvtCznQdDCbOMBiw7JMT8LXllkS7KP3M3YNIVWOjfl\nOG/ZVefHfUnplhE+s8eJFtdTWAgO1g5lRoTBd6rl6hUOF7LZ7z7WS5EvxLS2XRr+MF\nik4cyQBnAk/NHubnsyHqVDQ=\n-----END PRIVATE KEY-----\n",
        "client_email"<EMAIL_ADDRESS>        "client_id": "1082257212450547",
        "auth_uri": "https://accounts.google.com/o/oauth2/auth",
        "token_uri": "https://oauth2.googleapis.com/token",
        "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
        "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/ctf-storage%40lock-434506.gserviceaccount.com",
        "universe_domain": "googleapis.com"
      }
    # AWS S3 bucket secret key id
    access_key_id<EMAIL_ADDRESS>

P.S. Please note that the provided JSON key is invalid. Additionally, for testing purposes I'm using the JSON key directly in the values.yaml.
@ScribblerCoder  Any assistance with this error would be greatly appreciated!
Error:
ERROR [CTFd] Exception on /api/v1/files [POST]
Traceback (most recent call last):
  File "/opt/venv/lib/python3.11/site-packages/flask/app.py", line 1516, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/flask/app.py", line 1502, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/flask_restx/api.py", line 404, in wrapper
    resp = resource(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/flask/views.py", line 84, in view
    return current_app.ensure_sync(self.dispatch_request)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/flask_restx/resource.py", line 46, in dispatch_request
    resp = meth(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/CTFd/CTFd/utils/decorators/__init__.py", line 136, in admins_only_wrapper
    return f(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/opt/CTFd/CTFd/api/v1/files.py", line 106, in post
    obj = uploads.upload_file(file=f, **request.form.to_dict())
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/CTFd/CTFd/utils/uploads/__init__.py", line 51, in upload_file
    location = uploader.upload(file_obj=file_obj, filename=filename, path=parent)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/CTFd/CTFd/utils/uploads/uploaders.py", line 180, in upload
    self.s3.upload_fileobj(file_obj, self.bucket, s3_dst)
  File "/opt/venv/lib/python3.11/site-packages/boto3/s3/inject.py", line 642, in upload_fileobj
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/s3transfer/futures.py", line 103, in result
    return self._coordinator.result()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/s3transfer/futures.py", line 266, in result
    raise self._exception
  File "/opt/venv/lib/python3.11/site-packages/s3transfer/tasks.py", line 139, in __call__
    return self._execute_main(kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/s3transfer/tasks.py", line 162, in _execute_main
    return_value = self._main(**kwargs)
                   ^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/s3transfer/upload.py", line 764, in _main
    client.put_object(Bucket=bucket, Key=key, Body=body, **extra_args)
  File "/opt/venv/lib/python3.11/site-packages/botocore/client.py", line 553, in _api_call
    return self._make_api_call(operation_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/botocore/client.py", line 1009, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: Access denied.
<IP_ADDRESS> - - [09/Oct/2024:14:23:11 +0000] "POST /api/v1/files HTTP/1.1" 500 37 "https://ctf.securable.ai/admin/challenges/1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

> Any assistance with this error would be greatly appreciated!

I don't think GCP's  serviceaccount json key is supported. Use "User account HMAC" instead. This is exact same way that AWS S3 API  use. Where the key_id is not a serviceaccount email and the secret_key is definitely NOT a json key. Check with CTFd's maintainers, they probably won't add support to it because they're sticking with AWS.

Noted. So, you've tried setting this up by creating an HMAC key for a service account and it worked? I'll try with the User account HMAC then.
Thanks @ScribblerCoder !


Content messed up in the textLayer div

Attach (recommended) or Link to PDF file here:
problem.pdf
Configuration:

Web browser and its version: Firefox Developer Edition 60.0b11 (64-bit)
Operating system and its version: Windows 10 Pro 1709
PDF.js version: Built-in version inside the Firefox browser.
Is a browser extension: Built-in PDF.js inside the firefox browser.

Steps to reproduce the problem:

Right click on the PDF file, and select Open With
Select Firefox Developer Edition.
Try to select text and find it is not possible.
Press F12 to open the Inspector, and locate the textLayer div.
Found that the font-size for each div is abnormal, and the text content for each div is somehow messed up and has nothing to do with the text content which we see on the PDF.

What is the expected behavior? (add screenshot)
We should be able to select the text displayed, and the text content inside the textLayer div should match with what we see.

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
None

After tracing on the source code line by line, finally found out the reason:
The differences table of the PDF file looks like below, which is a hex number after a letter "C":

In the evaluator.js, I don't know why but the logic is:
case 'c':
    if (glyphName.length >=3 ) {
        code = + glyphName.substr(1);
    }

I changed it to:
case 'c':
    if (glyphName.length >=3 ) {
        code = parseInt(glyphName.substr(1), 16);
    }

And this could fix the messed up content, which means I could get the correct content from the textLayer, see the screenshot below:

But still, the text cannot be selected due to the strange font-size, or maybe the strange scaleX, I haven't found out why.

BTW, can anyone provide some explanations about the Gxx glyph, g00xx glyph and the Cddd glyph? I tried to google them but found nothing helpful.


Add Polyfuses

Add Polyfuse symbol and component
CHECKLIST

[x] I have read and followed the library conventions¹.
[ ] I already used the new library elements in a design and verified their correctness (optional).
[x] I'm the copyright owner of the added content (i.e. the changes are made by myself, not copied/imported from somewhere else).
[x] I agree to publish all my changes under the CC0 Public Domain License³, allowing everyone to use and modify the content without any restrictions.

One thing I should add: the polyfuse pin numbers appear on the schematic editor, but they don't show for regular fuses, I don't know why that is or how to change it. It would be better if they did not appear for polyfuses either I think.

Thanks! I allowed myself to make some modifications, I hope that's fine for you.

Remove line through the symbol body (AFAIK polyfuses usually don't contain that line, please correct me if I'm wrong)
Add US version of symbol
Remove category, moving to "Resistors" category instead (A category "Fuses" within the "Passive" category somehow feels wrong, as most fuses are not passive components - but polyfuses are actually resistors, so using that category should be fine)
Hide symbol pin names in schematics

Of course that's fine.
I saw in KiCad they have a line through it but you might be right that it's more common to not put the line.
Looks good to me ty.


Display the time not in fractions of an hour, but in the usual format

For example, it's 30 minutes now, displayed as «0,5».
It will be much more convenient if 30 minutes is displayed everywhere as 0:30.
For example in these places:

https://yadi.sk/i/4BerZe3XoI4yMw
https://yadi.sk/i/2psHxL7LeCHfcQ

It is also possible to make a choice in the settings in which form to display the time as "0.5 (fractions)" or as "0:30 (usually)".
Each user will choose what is more convenient for him.
However, I think the "0:30 (usually)" format is the best choice.

Thank you for your idea.
I added the feature you requested. Now you can choose your preferred format.

It will be available in the new version (v1.15.0)


Update unicode-programming-summary.md

There's no output page. Entry Point is in the Advanced page of the Linker of the project's property dialog in VS2017.

@corob-msft:  Please confirm that this PR is ready for merge. Thank you.


Training Lora for SD 1.5 is slower now than in release v0.6.5

Each epoch while training plain lora is slower now than when it was on release v0.6.5. There is some change in configuration of training process which is affecting this.
I observed that the GPU utilization is much lower in current release and it goes to 0 in between some epochs and takes some time to resume the training.
@kohya-ss
GPU: Nvidia L4
Total steps: 1000
Same params across both training run.
Current release(2a23713f71628b2d1b88a51035b3e4ee2b5dbe46): 38 mins
v0.6.5 release: 10 mins

Trying this out.

@kohya-ss
Update:
I tried adding --persistent_data_loader_workers, the training process still takes a lot of time than the previous release version.
Training config:
{
  "data": {
    "repeat": 1,
    "training_preset": "person",
    "flags": {
      "network_alpha": "128",
      "network_dim": "128",
      "train_batch_size": "1",
      "enable_bucket": "true",
      "resolution": "512",
      "min_bucket_reso": "320",
      "max_bucket_reso": "768",
      "seed": "420",
      "flip_aug": "true",
      "color_aug": "true",
      "face_crop_aug_range": "2.0,4.0",
      "max_token_length": "225",
      "clip_skip": "1",
      "gradient_accumulation_steps": "1",
      "max_train_steps": "1000",
      "optimizer_type": "AdamW8bit",
      "lr_scheduler": "polynomial",
      "unet_lr": "1e-4",
      "text_encoder_lr": "5e-5",
      "learning_rate": "1e-4",
      "pretrained_model_name_or_path": "runwayml/stable-diffusion-v1-5",
      "persistent_data_loader_workers": "true"
    }
  },
}


Update partitionoperator.md

improve partition operator docs + one more example

@ziham1531991 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@shsagir
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

New PR opened for light edits
#please-close


volcanosv-vc-large-indel.py fails

Hi,
I ran volcanosv-vc-large-indel.py, but the results of chr* did not have volcano_variant_chr*vcf file.
log:
Traceback (most recent call last):
  File "/home/xgc/variant/sv/volcanosv/VolcanoSV/bin/VolcanoSV-vc/Large_INDEL//extract_contig_signature_Hifi.py", line 740, in <module>
    ref_seq = dc_ref[chr_name]
KeyError: 'chr1'
cat: large_indel_output_tumor/chr1/volcano_variant_chr*vcf: 没有那个文件或目录

script:
path_to_volcanosv='../VolcanoSV'
for i in {1..22}
do
echo "***********************large-indel for chr${i}*******************"
python3 ${path_to_volcanosv}/bin/VolcanoSV-vc/Large_INDEL/volcanosv-vc-large-indel.py \
-i volcanosv_asm_output_tumor \
-bam hifi_tumor.bam \
-o large_indel_output_tumor \
-ref genome.fa \
-t 20 \
-chr ${i} \
-dtype Hifi \
-px hifi_tumor
done

Best regards.

What is your reference file like? Does the contig have name in a format like chr1 chr2 etc?

Yes, genome is T2T-CHM13, the format is chr1, chr2...

Your error is a new one to me. Is it possible to send me a small BAM file (like chr22) and the contig for that chromosome as well? So I can reproduce the error in my end and try to debug.

Does your reference file have some descriptive fields after the chromosome name? For example
>chr1          xxxxxxx
format like that.

Yes, after I simplied chr id, volcanosv-vc-large-indel.py works well.
But ValueError: too many values to unpack (expected 2) in volcanosv-vc-small-indel.py is still exist.
The small BAM file (like chr22) size is huge, ~1.16G, how can I send to you?

Is it possible to upload to a cloud drive (google drive or anything similar) and share the link to me please?
I need the BAM, contig and reference file to test. Thanks!

Hi, I have uploaded bam file and contig to google drive(https://drive.google.com/drive/folders/1w6pn5bIiiNIWmafqqLCwgqod06h3jZjM?usp=drive_link).
Thanks in advance.

Thanks! I also need the assembled contig file generated by VolcanoSV-asm, which should be under volcanosv-asm_output/chr22/final_contigs/_final_contigs.fa. Could you also provide that please?

Hi,
I uploaded the contig file now in the same link. Please have a check.

Hi @DayTimeMouse I was able to generate a VCF with ~1600 variants. I had to manually modify some scripts since you gave me a single chromosome reference file.
I think the problem might be the reference splitting. Can you check if you have a file in large_indel_output_tumor/chr1/ref_by_chr/chr1.fa ? And how big it is ?

Hi volcano1998,
I'm so sorry for that. Now I uploaded the full reference file (https://drive.google.com/drive/folders/1w6pn5bIiiNIWmafqqLCwgqod06h3jZjM?usp=drive_link).
large_indel_output_tumor/ref_by_chr/chr1.fa size is 239.74 MB, and large_indel_output_tumor/ref_by_chr/chr22.fa size is 49.56MB.

Thank you! I used your wgs reference file and was able to get the VCF without changing my code. I ran it on chr22 and got a VCF of size 3.1M in 3 mins.
I also notice that your file structure is the older version of VolcanoSV. I suggest you to try git pull and run it on chr22 again.


[FEATURE] Diets

Is there an existing issue for this?

[X] I have searched the existing issues

Information
Select if you are on a specific diet and give you a set of options if you are, also have an option to open an issue to request a new diet.
How will this improve our application
As a pescatarian I would use this feature, you can just run it over and over but this is a little easier.
Anything else?
No response
Code of Conduct

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

@SoupDevHub Please specify some examples, I will try to work on it ASAP.

@electron271 pescatarian, vegetarian, vegan, keto, low fat, low carb, etc.

Vegetarian and vegan will make it in for now, the others might be added eventually.


Update IFF_RUNNING flag by netdev_carrier_on and netdev_carrier_off

Summary

sim/netdev: Update IFF_RUNNING flag by netdev_carrier_on and netdev_carrier_off
net/loopback: Update IFF_RUNNING flag by netdev_carrier_on and netdev_carrier_off
net/tun: Update IFF_RUNNING flag by netdev_carrier_on and netdev_carrier_off
net/slip: Update IFF_RUNNING flag by netdev_carrier_on and netdev_carrier_off

Impact
running flag reflect the carrier state correctly for the pseudo netdev.
Testing
Pass CI

How about the other net drivers? It seems this fix could also be extended to them.
At least we should create an issue for not losing track of it.

How about the other net drivers? It seems this fix could also be extended to them.

Yes, the real driver need monitor the carrier change interrupt and report the real state correctly, but since it 's hardware dependent, I can't skimpily modify directly.

At least we should create an issue for not losing track of it.

It's here: https://github.com/apache/incubator-nuttx/issues/5059


Images_to_samples: Create binary labels from multi-class label data

Problem
To train class-specific models, GDL cannot currently create samples with single-class labels if label data provided is multi-class.
Solution
Two approaches seem feasible to implement this missing feature. First let's look at necessary developements, common to both approaches, that would let user control this feature seemlessly:

a parameter "hide_classes" would be added to the "global" section of the config yaml
validate_num_classes function would be adapted to take into account the ignored classes, since "num_classes" would most likely be smaller that the number of classes found in the geopackage.

1. Online approach
Description
Dynamically zero out (i.e. set as "background") irrelevant class values during training without modifying hdf5 files.
Advantages

Single class vs multi-class trainings can be performed with a single set of hdf5s, making it less prone to errors if user wants to directly compare performances of single-class vs multi-class models.

Disadvantages

For certain classes, like road or vegetation extraction, the online approach combined with the way GDL uses pre-rasterized samples saved as HDF5s during training may limit the ability of models to extract features of one class under features of another class. For example, a waterbody covered by vegetation would not be extracted if the HDF5s initially discarded the presence of this waterbody in the process of rasterizing the geopackages;
Though zeroing out irrelevant class values is possible, GDL is not currently developped to dynamically (i.e. during training) exclude samples that have no pixels of relevant class in their label. An quick implementation of online appoach would therefore be inadequate if user wishes to exclude samples in which class of interest is not represented (i.e. containing no pixels of that class in label). **Update: Random Weighted Sampler is about to be added to GDL and could help balance out an umbalanced dataset using the online approach;
May add some overhead during training

Implementation
The get_item method of data loader would be in charge of zeroing out irrelevant values, returning a binary label.
2. Offline approach
Description
In images_to_samples.py, once geopackage is read and rasterized, create hdf5 samples with binary values (i.e. "class of interest" and "non class of interest"). All irrelevant class values are then zeroed out to match the value of "non class of interest" class. Training continues as usual
Advantages

User can resort to already implemented features (i.e. "class proportion" parameter) to filter out samples for which the label contains no values of "class of interest"

Disadavantages

This approach calls for a separate set of hdf5 files. This will require more disk space and cause some duplication if a single-class vs multi-class comparison is desired for the same dataset.

Implementation
After having filtering out undesired samples (i.e. those that do not meet the class_prop threshold and min annotated percent), irrelevant class values are zeroed out before final samples is written to hdf5, in add_to_dataset function
Dev effort estimate
Necessary effort to implement either approaches ranges from 1 to 2 workdays. This dev seems fairly simple at a first glance.
Useful resources and articles
Buildings extraction

Zorvi et al., 2020, "Machine-learned_ Regularization and Polygonization
of Building Segmentation Masks"
http://cs231n.stanford.edu/reports/2017/pdfs/550.pdf

Road extraction

Ding & Bruzzonne, 2020, "DiResNet: Direction-aware Residual Network for
Road Extraction in VHR Remote Sensing Images"

Personally I prefer the first one.

I would call approaches dynamic/static rather than online/offline.  In an ideal world, that is when we can fetch training samples through the web, there could be an opportunity for us not to bother anymore with duplicating our data into HDF5 files.  In that respect, I would prefer the dynamic approach (#1).

This feature should apply to any subset of classes as was done with the parameter target_ids. In previous implementations, the offline approach was chosen. The disadvantages of this approach can be dealt with by a sampling to plain .tifs and .geojson rather than HDF5s.
This feature was broken with PR #208.

A solution is proposed in my 215-solaris-tiling branch. The vector ground truth is first tiled to vector chips (as geojson) alongside the imagery. The desired attribute values for a particular attribute field are then burned to raster. The advantage of this approach is that the geojson chips contain all initial attribute information and only to be created once. The burning of specific values can be requested multiple times and store to different copies as raster chips.

This issue will be solve with the merge of the branch 222-stac-item-input and the change made at line 471 in train_segmentation.py. This change make the reading of the gt binary if only one class is specify at attribute_values in the dataset yaml.


PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

This issue has been moved from a ticket on Developer Community.

[severity:It bothers me. A fix would be nice]
在此处描述你的问题
===DO NOT EDIT BELOW THIS LINE===
PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

Original Comments
Feedback Bot on 11/13/2022, 07:55 PM:
(private comment, text removed)

Original Solutions
(no solutions)

duplicate of https://github.com/microsoft/PTVS/issues/7238


Fixes for k8s ingress

Tested with 2 namespaces, both ingress writeback and forwarding seem to work now.
Since in 1.2 we may drop legacy k8s ingress - I think it's better to keep it local here, and move
the code to a separate controller when we start removing k8s deps from pilot.

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
00f98bb9b0fadef2454aeef4d31f4b9296230278
link
/test e2e-mixer-no_auth

prow/istio-integ-k8s-tests.sh
00f98bb9b0fadef2454aeef4d31f4b9296230278
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
00f98bb9b0fadef2454aeef4d31f4b9296230278
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c9d77eef76607641db62a905b4765e60acb54c48
link
/test istio_auth_sds_e2e

prow/istio-unit-tests.sh
b3822fc818f9ffadf9685823fc87fd2a81d595e6
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS [costinm]
pilot/OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
41ab74fbeb467c67c1a93ed0ab3f63383268b23d
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
41ab74fbeb467c67c1a93ed0ab3f63383268b23d
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
41ab74fbeb467c67c1a93ed0ab3f63383268b23d
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-integ-k8s-tests
/test istio-pilot-multicluster-e2e

/test racetest

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
41ab74fbeb467c67c1a93ed0ab3f63383268b23d
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-multicluster-e2e

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
41ab74fbeb467c67c1a93ed0ab3f63383268b23d
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wenchenglu  - can you merge this ? Has been tested (including stress test ), low risk, users waiting.


Proxy based on 0 TTL

I have a bit of a funky use case - I'm using https://github.com/Janik-Haag/NixOS-DNS to generate my octodns configuration, and it works by generating a ZoneFile which octodns consumes (https://github.com/Janik-Haag/NixOS-DNS/blob/main/utils/zonefiles.nix). Unfortunately because of this we can't set the proxied status of a domain.
My pitch is the ability to set the TTL to 0 and this provider sees that as a request to proxy the domain, since the TTL of 0 doesn't make sense in other use cases.
Alternatively, I might look at the ZoneFileSource and retain the octodns.* configuration options as comments, which might be better long term?

There's already a special ttl value, defined by Cloudflare not octodns-cloudflare, that enables proxied.
https://github.com/octodns/octodns-cloudflare/blob/59de7e37905605f8126bd7d1b391e55000474c89/octodns_cloudflare/__init__.py#L441
So if it sees a ttl of 1 it'll enable proxied.
If the source can't use make them 1 the other option would be to use a custom processor, defining a process_source_zone that looks for the 0, or whatever you want to drive it off of, and sets record._octodns['cloudflare']['proxied'] = true or whatever you'd like to do.

Oh, neat! Was digging through the code and must have missed this - thanks :)

Oh, right, I remember why this didn't occur to me
https://github.com/octodns/octodns-cloudflare/blob/v0.0.4/octodns_cloudflare/__init__.py#L188-L189
From what I'm reading, this effectively overrides the ttl of 1 every time? From my testing the TTL of 1 doesn't get used and proxying never gets added. I am going to look at the processor route but curious if this is intentional behaviour.


Update Hera/Jet/Cheyenne site configs

Summary
Addressing checklist items from #765 for hera, jet, and cheyenne.
since cheyenne is on a shared filesystem w/ casper & derecho, we will need to re-build the 3rdparty libraries and modules in the machine-specific subdirs under /glade/work/epicufsrt/contrib/spack-stack.
Testing
Describe the testing done for this PR.
Applications affected
probably any that use spack-stack 1.5.0
Systems affected
hera/jet/cheyenne
Dependencies
none
Issue(s) addressed
#765
Checklist

[ ] This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
[ ] These changes have been tested on the affected systems and applications.
[ ] All dependency PRs/issues have been resolved and this PR can be merged.

hera / jet installations did not go well.
on jet there were<EMAIL_ADDRESS>and<EMAIL_ADDRESS>issues:
==> Installing scotch-7.0.4-4avzhnbk2ocm7vkfgvv2hocnjeelr5nx
==> No binary for scotch-7.0.4-4avzhnbk2ocm7vkfgvv2hocnjeelr5nx found: installing from source
==> Cannot find version 7.0.4 in url_list
==> Error: FetchError: All fetchers failed for spack-stage-scotch-7.0.4-4avzhnbk2ocm7vkfgvv2hocnjeelr5nx
==> Installing libxau-1.0.8-3mroavg7o5fhr7yupniyc7rhvwaoff3i
==> No binary for libxau-1.0.8-3mroavg7o5fhr7yupniyc7rhvwaoff3i found: installing from source
==> Warning: Skipping build of ufs-weather-model-env-1.0.0-qdc3zfrlyef4hjvzb52w76avtiqzngut since scotch-7.0.4-4avzhnbk2ocm7vkfgvv2hocnjeelr5nx failed

==> No binary for proj-8.1.0-6g5mn2usqoioqtcfaqoy5vvfhiqcqeoa found: installing from source
==> Fetching file:///mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/source-cache/_source-cache/archive/22/22c5cdc5aa0832077b16c95ebeec748a0942811c1c3438c33d43c8d2ead59f48.tar.gz
==> Fetching file:///mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/source-cache/proj/proj-data-8.1.0.tar.gz
==> Error: ChecksumError: sha256 checksum failed for /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/resource-proj-data-6g5mn2usqoioqtcfaqoy5vvfhiqcqeoa/proj-data-1.13.tar.gz
    Expected f1e5e42ba15426d01d1970be727af77ac9b88c472215497a5a433d0a16dd105b but got 76960d34d635aa127058ce654d89ea0eff91e2e4f2036482e677af5a88669b08. File size = 581536964 bytes. Contents = b'\x1f\x8b\x08\x00\xe3D\xef_\x00\x03\xd4\xb9c\x94&M...\x9f\xff\xfc\xe7\xff\xaf\xff\x016{\xd4+\x00V\xfa"'

on hera, issues with intel<EMAIL_ADDRESS>and, again,proj-8.1.0 checksum errors (both compilers).
for netcdf, the error looks like:
libtool: warning: library '/apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.la' was moved.
libtool: link: ar cr .libs/libnetcdf4_nf_interfaces.a .libs/module_netcdf4_nf_interfaces.o
libtool: link: ranlib .libs/libnetcdf4_f03.a
libtool: warning: library '/apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.la' was moved.
ifort: command line warning #10434: option '-nofor_main' use with underscore is deprecated; use '-nofor-main' instead
ifort: command line warning #10006: ignoring unknown option '-mismatch_all'
ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(attr.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(putget.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(error.o): relocation R_X86_64_32 against `unknown' can not be used when making a shared object; recompile with -fPIC
ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(nc.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
ld: final link failed: Nonrepresentable section on output
make[2]: *** [libnetcdff.la] Error 1
make[1]: *** [all] Error 2
make[1]: Leaving directory `/scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/spack-stage-netcdf-fortran-4.6.0-z5pu7eld2j7cftvrdo6vp2mudy5poabq/spack-src/fortran'
make: *** [all-recursive] Error 1
==> Error: ProcessError: Command exited with status 2:
    'make' '-j6' 'V=1'

4 errors found in build log:
     532    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(nc.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shar
            ed object; recompile with -fPIC
     533    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(string.o): relocation R_X86_64_32 against `.rodata.str1.4' can not be used when mak
            ing a shared object; recompile with -fPIC
     534    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(v1hpg.o): relocation R_X86_64_32 against `.rodata.str1.4' can not be used when maki
            ng a shared object; recompile with -fPIC
     535    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(var.o): relocation R_X86_64_32 against `.rodata.str1.4' can not be used when making
             a shared object; recompile with -fPIC
     536    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(utf8proc.o): relocation R_X86_64_32S against symbol `utf8proc_utf8class' can not be
             used when making a shared object; recompile with -fPIC
     537    ld: /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a(posixio.o): relocation R_X86_64_32 against `.rodata.str1.4' can not be used when ma
            king a shared object; recompile with -fPIC
  >> 538    ld: final link failed: Nonrepresentable section on output
  >> 539    make[2]: *** [libnetcdff.la] Error 1
     540    make[2]: Leaving directory `/scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/spack-stage-netcdf-fortran-4.6
            .0-z5pu7eld2j7cftvrdo6vp2mudy5poabq/spack-src/fortran'
  >> 541    make[1]: *** [all] Error 2
     542    make[1]: Leaving directory `/scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/spack-stage-netcdf-fortran-4.6
            .0-z5pu7eld2j7cftvrdo6vp2mudy5poabq/spack-src/fortran'
  >> 543    make: *** [all-recursive] Error 1

See build log for details:
  /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/spack-stage-netcdf-fortran-4.6.0-z5pu7eld2j7cftvrdo6vp2mudy5poabq/spack-build-out.txt

@AlexanderRichert-NOAA do you have any clue about any of these failures?

scotch 7.0.4 error: Are you sure you're using the right branch for the submodule? See https://github.com/JCSDA/spack/blob/release/1.5.0/var/spack/repos/builtin/packages/scotch/package.py
proj error: I did a sha256sum for a fresh copy of that file, and it matched what's in the recipe, so the cached tarball needs to be deleted.
netcdf error: Why is it using /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a?

I can take a look tomorrow if needed

scotch 7.0.4 error: Are you sure you're using the right branch for the submodule? See https://github.com/JCSDA/spack/blob/release/1.5.0/var/spack/repos/builtin/packages/scotch/package.py

pretty sure it is the correct branch:
[role.epic@Hera:/scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/spack]# git branch
* (HEAD detached at 610a6c4fee)

and 7.0.4 is in the scotch package.py
[role.epic@Hera:/scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/spack]# cat var/spack/repos/builtin/packages/scotch/package.py
# Copyright 2013-2023 Lawrence Livermore National Security, LLC and other
# Spack Project Developers. See the top-level COPYRIGHT file for details.
#
# SPDX-License-Identifier: (Apache-2.0 OR MIT)

import spack.build_systems.cmake
import spack.build_systems.makefile
from spack.package import *

class Scotch(CMakePackage, MakefilePackage):
    """Scotch is a software package for graph and mesh/hypergraph
    partitioning, graph clustering, and sparse matrix ordering.
    """

    homepage = "https://gitlab.inria.fr/scotch/scotch"
    git = "https://gitlab.inria.fr/scotch/scotch.git"
    url = "https://gitlab.inria.fr/scotch/scotch/-/archive/v7.0.1/scotch-v7.0.1.tar.gz"
    list_url = "https://gforge.inria.fr/frs/?group_id=248"

    maintainers("pghysels")

    version("7.0.4", sha256="8ef4719d6a3356e9c4ca7fefd7e2ac40deb69779a5c116f44da75d13b3d2c2c3")

proj error: I did a sha256sum for a fresh copy of that file, and it matched what's in the recipe, so the cached tarball needs to be deleted.

10-4. i will delete the cached tarballs.

netcdf error: Why is it using /apps/wgrib2/2.0.8/intel/<IP_ADDRESS>/lib/libnetcdf.a?

this i have no clue about.

removing the proj cache worked on jet, but not on hera:
==> Installing proj-8.1.0-wk2drtykj5qtjyyiruscorefx72lpucy
==> No binary for proj-8.1.0-wk2drtykj5qtjyyiruscorefx72lpucy found: installing from source
==> Fetching https://mirror.spack.io/_source-cache/archive/22/22c5cdc5aa0832077b16c95ebeec748a0942811c1c3438c33d43c8d2ead59f48.tar.gz
==> Fetching file:///scratch1/NCEPDEV/nems/role.epic/spack-stack/source-cache/proj/proj-data-8.1.0.tar.gz
==> Error: ChecksumError: sha256 checksum failed for /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.0/cache/build_stage/resource-proj-data-wk2drtykj5qtjyyiruscorefx72lpucy/proj-data-1.13.tar.gz
    Expected f1e5e42ba15426d01d1970be727af77ac9b88c472215497a5a433d0a16dd105b but got 76960d34d635aa127058ce654d89ea0eff91e2e4f2036482e677af5a88669b08. File size = 581536964 bytes. Contents = b'\x1f\x8b\x08\x00\xe3D\xef_\x00\x03\xd4\xb9c\x94&M...\x9f\xff\xfc\xe7\xff\xaf\xff\x016{\xd4+\x00V\xfa"'

@climbfuji @AlexanderRichert-NOAA is this single scotch checksum failure something we need to create a mirror using another machine for?

On jet I can't even wget the scotch package (though I can ping the server where it lives). So I'm assuming it needs to be downloaded separately and pulled in (or ask the system admins what gives).

On jet I can't even wget the scotch package (though I can ping the server where it lives). So I'm assuming it needs to be downloaded separately and pulled in (or ask the system admins what gives).

weird. i just used jet's spack.lock to make a mirror on orion. i decided to just rsync the scotch/7.0.4 tarball from the mirror on orion to /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/source-cache, but spack still won't install scotch/7.0.4.

Assuming the cache file is in the same location with the same name-- what happens if you run 'spack fetch scotch'? Does it pick up on the cached copy?

all issues on hera and jet were resolved. both of these installations are now completed and the jet/hera sections of the docs. have been updated.


[Feature Suggestion] Option to "Tell Us Why" -> "I don't like the video" with one click

Hi. Thank you very much for this great extension.
I'm not sure if it has any real effect, but I usually follow the "Not Interested" click with "Tell Us Why" -> "I don't like the video" to make it extra clear to youtube algorithms that I'm really really really not interested in such kind of videos.
So my personal procedure of not-interesting a video before this extension consisted of 5 clicks (triple-dot button, "Not Interested", "Tell Us Why", "I don't like the video", "Submit").
This extension currently reduces the number of clicks I have to do to 4 (which is great!), but it would be really neat if this number could be reduced further.
Maybe something like a setting in the extension to automatically send the "Tell Us Why" -> "I don't like the video" commands when you are not-interesting the video with the extension's button, or maybe some follow-up button alongside the "Tell Us Why" button to "I don't like the video" in one click.
Just dropping this idea in case you'll find it a logical continuation of this extension's development.

Got it, thank you, I will try.

Already published as version 0.0.5

Wow, thank you so much!
It appears to be working on my side ^_^
Wish you all the besties!


Increment version

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/75690
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.8 -m "<description of version>" ae7fa32987fa3ee58e25725aa8159f695955637d
git push origin v0.10.8

Registration pull request created: JuliaRegistries/General/75756
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.9 -m "<description of version>" fd4d2b73f4a0fed4790b209656bf23bfbc87c2bc
git push origin v0.10.9

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/81149
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.10 -m "<description of version>" 2e4f1839a7ff411cfc7dd8fdf5c80e22c8b29370
git push origin v0.10.10

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/82934
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.11 -m "<description of version>" 27304a5f7d92d28d2b6be750c9813bbb8029810a
git push origin v0.10.11

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/83807
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.0 -m "<description of version>" d439a3b852c0bdbf65d8e2d6718e7eb478737f61
git push origin v0.11.0

Error while trying to register: "Tag with name v0.11.0 already exists and points to a different commit"

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/83823
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.1 -m "<description of version>" 573b7ba6e36f57d04b5c43cd8fd92dd6c6bd1379
git push origin v0.11.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/84803
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.2 -m "<description of version>" 4e6296beea3d936e529b9f56e542143db7df7e09
git push origin v0.11.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/85565
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.0 -m "<description of version>" 4942107b49d51d97cf658c7e8d5cd7d881250eed
git push origin v0.12.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/85723
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.1 -m "<description of version>" 778e6d502360bcee00036777a107403408494ecb
git push origin v0.12.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/86028
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.3 -m "<description of version>" 02efde93c38ce7b4efe50a8b972ef55bb707868a
git push origin v0.12.3

Also, note the warning: Version 0.12.3 skips over 0.12.2
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/86031
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.2 -m "<description of version>" 0c4dad43c61411da5ab0f6a752823581c9af306a
git push origin v0.12.2


feat: drop requirement for release tag to exist

Stop relying of an existing tag for the release to publish. The assumption are:

that package.json holds the version to release;
that previous release tag exist locally.

The new process is as follow:

release gets the version from ./package.json;
find a tag for the version:

use the tag if it exists;
use HEAD if it doesn't exist;

find the tag for the previous release.

fix #41 #44

This was the first try on the plugin. But then @rauchg came around and told me that if we stop relying on the package.json file, we could support other projects as well (not just the node ones).
We have a lot of non-node projects in @zeit, so I found it great to support them as well.


Can't use multiple domains with entity roles or groups

Rasa Open Source version
2.8.22 - also happens with 3.0.5
Python version
3.8
What operating system are you using?
OSX
What happened?
You can reproduce by cloning https://github.com/melindaloubser1/moodbot/tree/entity_roles_multidomain and running rasa train --domain domains
I have a split domain setup like this:
├── domains
│   ├── domain.yml
│   ├── entities.yml
│   └── intents.yml

In entities.yml, I have an entity with roles:
version: '2.0'
entities:
   - city:
       roles:
       - from
       - to

When I try to train a model with these domains, it fails with the error below i.e. it cannot combine the sections because it is expecting a list, but roles are a dictionary.
The same error does not occur when I have no roles for my entity.
Command / Request
rasa train --domain domains

Relevant log output
Traceback (most recent call last):
  File "/Users/melinda/.pyenv/versions/rasa2/bin/rasa", line 8, in <module>
    sys.exit(main())
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/__main__.py", line 118, in main
    cmdline_arguments.func(cmdline_arguments)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/cli/train.py", line 59, in <lambda>
    train_parser.set_defaults(func=lambda args: run_training(args, can_exit=True))
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/cli/train.py", line 91, in run_training
    training_result = train_all(
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/api.py", line 109, in train
    return rasa.utils.common.run_in_loop(
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/utils/common.py", line 296, in run_in_loop
    result = loop.run_until_complete(f)
  File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/model_training.py", line 100, in train_async
    domain = await file_importer.get_domain()
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/utils/common.py", line 141, in decorated
    return await cache.cached_result()
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/importer.py", line 448, in get_domain
    original, e2e_domain = await asyncio.gather(
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/importer.py", line 455, in _get_domain_with_e2e_actions
    stories = await self.get_stories()
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/importer.py", line 490, in get_stories
    return await self.importer.get_stories(
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/importer.py", line 399, in get_stories
    return await self._importer.get_stories(
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/utils/common.py", line 141, in decorated
    return await cache.cached_result()
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/importer.py", line 272, in get_stories
    stories = await asyncio.gather(*stories)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/rasa.py", line 55, in get_stories
    await self.get_domain(),
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/importers/rasa.py", line 79, in get_domain
    domain = Domain.load(self._domain_path)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/core/domain.py", line 143, in load
    other = cls.from_path(path)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/core/domain.py", line 155, in from_path
    domain = cls.from_directory(path)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/core/domain.py", line 239, in from_directory
    domain = other.merge(domain)
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/core/domain.py", line 305, in merge
    combined[key] = merge_lists(combined[key], domain_dict[key])
  File "/Users/melinda/.pyenv/versions/rasa2/lib/python3.8/site-packages/rasa/shared/core/domain.py", line 275, in merge_lists
    return sorted(list(set(list1 + list2)))
TypeError: unhashable type: 'dict'

Hi I was wondering what release this bugfix was going to target? Our team is essentially blocked without it.

This will be fixed when 3.1 is released


Accessing to the scripts for generating these datasets

@hichamjanati  @agramfort
Could you please let me know how did you generate the following ave and bem files?
@stefanhaufe
https://github.com/hichamjanati/Cam-CAN-preprocessing/blob/8f747263c85544d5973f2470f92782d1f1ce0d94/config.py#L91
https://github.com/hichamjanati/Cam-CAN-preprocessing/blob/8f747263c85544d5973f2470f92782d1f1ce0d94/config.py#L65

see my PR https://github.com/hichamjanati/Cam-CAN-preprocessing/pull/9


fix: set pending status on single-commit PRs with a solitary unsemantic commit

Normally when a GitHub pull request is squashed, the title of the pull request is used in the result squash commit message.
☝ However! ☝if that PR contains only one single solitary commit, that commit's message will be used for the squash message, rather than the PR title.
In cases where the PR title is semantic and the single commit is not, this bot was previously giving the green light to merge. This PR changes the behavior, instead setting a pending status and the following message:

Squashing a PR with only one commit will use that commit’s message. Please push an empty semantic commit.

Resolves #17

I think the condition check in this PR is wrong.
https://github.com/probot/semantic-pull-requests/blob/fadfa5d16495da335306d7157cbf8a7d060fee8f/lib/handle-pull-request-change.js#L47
In my private repository, it falls to the else block above (in other words, vanilaConfig is true), and
https://github.com/probot/semantic-pull-requests/blob/fadfa5d16495da335306d7157cbf8a7d060fee8f/lib/handle-pull-request-change.js#L53
isSemantic is always false for single-commit PRs even though the title and the only commit message of it are semantic.

@alanhchoi oops thanks for pointing this out. I opened a PR to revert this: https://github.com/probot/semantic-pull-requests/pull/59 -- will give this another shot in a followup PR.


Remove unnecessary output that the certificates repo was encrypted

          1 Warning

:warning:
Please provide a changelog summary in the Pull Request description @ohayon

  Generated by :no_entry_sign: Danger


JKali revised and fixed

Hi @khaes-kth
Ready to merge?

Hi @martinezmatias
Yes, READY.

Merged, thanks!

Thanks @martinezmatias


otel: check attribute for all calls: trace_id

If you click on any event here , you'll see a trace_id field under Info > otel. Our friendly customer team needs to use trace_id to trace verb-to-verb calls.
The existing trace_id that gets logged by default is probably the one described here.
Separately, our request headers contain a trace_id that can definitely be used to track verb-to-verb calls.
We do not know if the default trace_id field provided by otel (i.e. what we have now in Datadog) is actually correctly instrumented such that it can be used to trace verb-to-verb calls. We also do not know if otel's trace_id is the same as our request headers' trace_id.
The task here is to:

Find answers to these 2 unknowns.
If the existing trace_id does not enable tracing of verb-to-verb calls, then:

we need to either:

Fix it so that the spans we send to otel correctly cover the full call stack
OR, start logging our request headers' trace_id as a new attribute

Cross reference with https://github.com/TBD54566975/ftl/issues/2022 to make sure the users are seeing the same thing as us. Or if they don't realize it's broken and we do, we should give them a heads up (so they're aware until we've fixed it)

Separately, we should check if any request header data (including trace_id) is persisted by default. We should also take a quick pass over to make sure we aren't exporting any sensitive data (e.g. auth tokens).

Fixed in #2144


[Feature] [SR SQL Planner Summer Camp] add showSnapshot analyzer

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #7951
Problem Summary(Required) ：

add showSnapshot analyzer

[FE PR Coverage Check]
:heart_eyes: pass : 62 / 72 (86.11%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[443]

:large_blue_circle:
com/starrocks/sql/analyzer/ShowSnapshotAnalyzer.java
48
56
85.71%
[19, 38, 62, 63, 75, 77, 111, 117]

:large_blue_circle:
com/starrocks/analysis/ShowSnapshotStmt.java
6
7
85.71%
[172]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
6
6
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 62 / 72 (86.11%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[456]

:large_blue_circle:
com/starrocks/sql/analyzer/ShowSnapshotAnalyzer.java
48
56
85.71%
[19, 38, 62, 63, 75, 77, 111, 117]

:large_blue_circle:
com/starrocks/analysis/ShowSnapshotStmt.java
6
7
85.71%
[172]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
6
6
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 62 / 72 (86.11%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[422]

:large_blue_circle:
com/starrocks/sql/analyzer/ShowSnapshotAnalyzer.java
48
56
85.71%
[19, 37, 61, 62, 74, 76, 110, 116]

:large_blue_circle:
com/starrocks/analysis/ShowSnapshotStmt.java
6
7
85.71%
[172]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
6
6
100.00%
[]

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 62 / 72 (86.11%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[480]

:large_blue_circle:
com/starrocks/sql/analyzer/ShowSnapshotAnalyzer.java
48
56
85.71%
[19, 37, 60, 61, 73, 75, 109, 115]

:large_blue_circle:
com/starrocks/analysis/ShowSnapshotStmt.java
6
7
85.71%
[172]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
6
6
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 62 / 72 (86.11%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[492]

:large_blue_circle:
com/starrocks/sql/analyzer/ShowSnapshotAnalyzer.java
48
56
85.71%
[19, 37, 60, 61, 73, 75, 109, 115]

:large_blue_circle:
com/starrocks/analysis/ShowSnapshotStmt.java
6
7
85.71%
[172]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
6
6
100.00%
[]


haskell-modules: add callCabal2nixWithOptions.

Fixes #44377.
Motivation for this change
haskellSrc2nix supports calling cabal2nix with extra options, but there is no way to do this via callCabal2nix. This adds a new function, callCabal2nixWithOptions, which supports those extra options.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Looks related to https://github.com/NixOS/nixpkgs/pull/42658 (I’m not in the position to judge whether it’s better or worse than that).

Bumping for review, please.

@peti @ryantm @roberth like @cocreature mentions this is indeed an alternative to #42658.
Advantages of #42658 compared to this PR:

#42658 doesn't introduce a new function.

Disadvantages  #42658 compared to this PR:

#42658 convolutes the attribute set for overriding the callPackage arguments with the extraCabal2nixOptions. It's a nifty idea but a bit magical and harder to discover than callCabal2nixWithOptions. However this can be solved by adding some documentation to #42658.

I would go for #42658 if it introduces some documentation. What do you think?

It's fine with me, as long as one of them gets merged soon :)

I have no preference.

I prefer this one, becuase it seems the least path of resistance to actually get moving with this, and this has already sat for quite a while. :smiley:

@dhess @basvandijk I think we should bite the bullet on this, but also rewrite the function to take an argset instead of multiple arguments, such that next time, we can hide the addition of some field from the user without introducing YetAnotherCallCabal2nixWithFeatureX

@srhb I agree we should bite the bullet and I also think we should backport this to release-18.09.
With regards to your point about the argset argument, do you mean something like:
callCabal2nixWithOptions = name: src: { extraCabal2nixOptions ? "" }: args: ...

@basvandijk I was actually considering
callCabal2nixWithOptions = { name, src, args, extraCabal2nixOptions ? "" }: ...

This way it becomes a uniform invocation no matter what we add in the future. But if it's too radical a change, I don't feel strongly about it. I just thought it could help future-proof a bit.

@srhb I think all callSomething functions in Nix use multiple arguments instead of taking a set. I don't want to be inconsistent here. I've bitten the bullet and merged this.


Java toolbox: Java 11 adoptions

Turns out that the currency format for different locales has changed in
newer versions of java. Most significantly, non breaking space and
unicode "minus sign" is sometimes used instead of horizontal space and
hyphen.
We choose to live with this change, as we don't want to add custom
configuration that's costly to maintain. Also, given that other repos already use this artifact, they are already unknowingly formatting in the new way if they're running on java11.
But, as a consequence of this, the parser cannot parse strings with
normal space or hyphen, should those be the characters preferred by the
formatter. So, to not make this too dangerous, logic has been changed in
the parser method, so that normal space and hyphen won't cause a
problem.
ping @minisu and @xiaodong-izettle
Unfortunately, the entire repo doesn't build under my java11 installation, as some dependency in izettle-cassandra-datastax seems to break under java11. Any idea on how to solve that?

@minisu or @xiaodong-izettle : any thoughts on this?

Thanks @minisu ! Still have to solve the build failure though...

Great! I still get:
[ERROR] useConfiguredValues(com.izettle.cassandra.CassandraSessionFactoryTest)  Time elapsed: 0.001 s  <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.apache.cassandra.io.util.FileUtils
        at com.izettle.cassandra.CassandraSessionFactoryTest.before(CassandraSessionFactoryTest.java:29)

but it seems our build server is happy anyway.

Thank you for help with this @xiaodong-izettle !


E2E tests failing due to unschedulable nodes

What steps did you take and what happened:
I have the same problem as bug #1091 but when I attempt to use the solution, the e2e pod still reports those nodes as unschedulable and loops until the timeout.
What did you expect to happen:
I expected the --non-blocking-taints passed via the e2e args to make the e2e pod ignore the nodes with those taints.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Sonobuoy version: 0.50.0
Kubernetes version: (use kubectl version): 1.18.16
Kubernetes installer & version:
Cloud provider or hardware configuration: AWS EC2 instances
OS (e.g. from /etc/os-release):
Sonobuoy tarball (which contains * below) sonobuoy_0.50.0_darwin_amd64.tar.gz

Can you attach the logs from the run so I can help you diagnose the issue?
The test starup logic is very finicky and I wouldn't be surprised if there were a legitimate bug  in some part of it. It can also be easily misconfigured. The logs from sonobuoy will help us see 1) what you ran 2) what the nodes were tainted as 3) the logs from the run and hopefully which nodes were giving it the problem.

Thank you - we tried a couple of ways, here are a couple of runs (ec2 ip address host names removed to protect the innocent/comply with security disclosure requirements):
kubectl logs sonobuoy-e2e-job-834000a6ba2d4138 e2e -n sonobuoy

/gorunner
sep is " " args are "“--non-blocking-taints=kaim-server,stable”"split [“--non-blocking-taints=kaim-server,stable”]
2021/05/14 18:01:06 Running command:
Command env: []
Run from directory:
Executable path: /usr/local/bin/ginkgo
Args (comma-delimited): /usr/local/bin/ginkgo,--focus=Pods should be submitted and removed,--skip=,--noColor=true,/usr/local/bin/e2e.test,--,--disable-log-dump,--repo-root=/kubernetes,--provider=local,--report-dir=/tmp/results,--kubeconfig=,“--non-blocking-taints=kaim-server,stable”
2021/05/14 18:01:06 Now listening for interrupts
I0514 18:01:07.591413      25 test_context.go:410] Using a temporary kubeconfig file from in-cluster config : /tmp/kubeconfig-464088907
I0514 18:01:07.591428      25 test_context.go:423] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
I0514 18:01:07.591506      25 e2e.go:124] Starting e2e run "04ceced8-2609-4f86-802a-4c7253b4cca5" on Ginkgo node 1
{"msg":"Test Suite starting","total":1,"completed":0,"skipped":0,"failed":0}
Running Suite: Kubernetes e2e suite
===================================
Random Seed:<PHONE_NUMBER> - Will randomize all specs
Will run 1 of 4994 specs

May 14 18:01:07.602: INFO: >>> kubeConfig: /tmp/kubeconfig-464088907
May 14 18:01:07.604: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
May 14 18:01:07.638: INFO: Unschedulable nodes:
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:01:07.638: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
Run 2: trying to isolate the taint list to see if we could get at least one to go:
kubectl logs sonobuoy-e2e-job-4045ceb3efa04cef e2e -n sonobuoy

/gorunner
sep is " " args are "“--non-blocking-taints=dedicated monitoring NoSchedule”"split [“--non-blocking-taints=dedicated monitoring NoSchedule”]
2021/05/14 18:22:31 Running command:
Command env: []
Run from directory:
Executable path: /usr/local/bin/ginkgo
Args (comma-delimited): /usr/local/bin/ginkgo,--focus=Pods should be submitted and removed,--skip=,--noColor=true,/usr/local/bin/e2e.test,--,--disable-log-dump,--repo-root=/kubernetes,--provider=local,--report-dir=/tmp/results,--kubeconfig=,“--non-blocking-taints=dedicated,monitoring,NoSchedule”
2021/05/14 18:22:31 Now listening for interrupts
I0514 18:22:31.937800      24 test_context.go:410] Using a temporary kubeconfig file from in-cluster config : /tmp/kubeconfig-104645444
I0514 18:22:31.937818      24 test_context.go:423] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
I0514 18:22:31.937895      24 e2e.go:124] Starting e2e run "f651bda6-7207-4ee8-aa88-ce6f4fc4811d" on Ginkgo node 1
{"msg":"Test Suite starting","total":1,"completed":0,"skipped":0,"failed":0}
Running Suite: Kubernetes e2e suite
===================================
Random Seed:<PHONE_NUMBER> - Will randomize all specs
Will run 1 of 4994 specs

May 14 18:22:31.949: INFO: >>> kubeConfig: /tmp/kubeconfig-104645444
May 14 18:22:31.951: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
May 14 18:22:31.981: INFO: Unschedulable nodes:
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated monitoring NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated kiam-server NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master
May 14 18:22:31.981: INFO: -> ec2.internal Ready=true Network=false Taints=[{dedicated stable NoSchedule }] NonblockingTaints:node-role.kubernetes.io/master

Something does seem off with the quoting/etc of the non-blocking taints.
In the logs you can see it just lists the master taint as the only non-blocking taint despite you trying to do it above.

Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready

It is unintuitive how to write the line since we're via the sonobuoy CLI we're telling the plugin to set an environment variable which changes the CLI values for ginkgo.
However, a tiny example I just ran on my own kind cluster:

Tolerating taints "foo,bar" when considering if nodes are ready

To get that I provided:
sonobuoy run --plugin-env=e2e.E2E_EXTRA_ARGS=--non-blocking-taints=foo,bar

You need to make the list of taints a comma-separated list:
... --plugin-env=e2e.E2E_EXTRA_ARGS=--non-blocking-taints=dedicated,stable,NoSchedule
Thats the way it looks in your logs; that they are separate taints. As you wrote it (dedicated=stable:NoSchedule) it thinks that is one value (since there are no commas).
That should fix you up; going to close but reopen if this doesn't resolve the issue.

that did it!  thanks much!


Mark certain bindings as experimental

From @yochay on December 15, 2016 0:8
Binding like Twilio and SandGrid needs to be marked as experimental.
Copied from original issue: projectkudu/AzureFunctionsPortal#847

From @lindydonna on January 4, 2017 19:13
This is because we want to make breaking changes to the bindings once we create binding extensibility.

Once we support 3rd party binding extensibility, these bindings will not ship "in the box". You'll need to add them to your function app. In this world, the promises we make about core bindings vs 3rd party bindings are very different e.g. 3rd party bindings are as-is, we can't guarantee that they always work, you might need to accept a license agreement to use them, etc. There is a difference in customer expectations. I think @yochay wants to communicate that now, ahead of time, by moving these to the experimental category (please correct me if I'm wrong).

From @mathewc on December 15, 2016 0:33
Why? These bindings are solid - what's the problem with them?

From @fabiocav on January 4, 2017 20:1
What bindings do we expect to break? Why would that be impacted by the extensibility work?

From @yochay on January 4, 2017 22:52
Marking these experimental allows us to handle future updates and not ship them 'in the box'. We also want the partners (eco-system) to start picking such bindings on their own. Furthermore, what happens if tomorrow either of  these providers release a security fix. Are we on the hook to take the updates and then when and how...

Proposal is to add (experimental) in the binding name in bindings.json and in the templates (if it isn't there already).

As per chat with donna
Will be updating the titles of the following binding  as experimental

Sendgrid
Twilio
External file
External table

Per chat with @soninaren, my previous guidance was incorrect. Should do the following instead:

Sendgrid (preview)
Twilio (preview)
External file (preview)
External table (experimental)

Apologies for the churn!

Fixed here https://github.com/Azure/azure-webjobs-sdk-templates/pull/399


Add suffisticated test sequence for three roll passes

We should add the pass sequences of @sagkalibreur as well as @grplan as tests for the pyroll-basic meta package.

If added the test of sag kalibreur.
@RichardPfr please add the pass sequence of grplan.

Done


Github CI: Bump test timeout to 90 minutes

Codecov Report

Merging #581 (398fcbb) into main (abc86cb) will decrease coverage by 0.1%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            main    #581     +/-   ##
=======================================
- Coverage   12.0%   11.9%   -0.1%
=======================================
  Files         34      34
  Lines      10642   10732     +90
=======================================
+ Hits        1277    1282      +5
- Misses      9365    9450     +85

Impacted Files
Coverage Δ

src/cli/command.rs
19.8% <0.0%> (-2.4%)
:arrow_down:

src/cli/opts.rs
39.0% <0.0%> (-0.3%)
:arrow_down:

src/walletd/runtime.rs
0.0% <0.0%> (ø)

src/farcasterd/runtime.rs
0.0% <0.0%> (ø)

src/syncerd/syncer_state.rs
83.6% <0.0%> (+0.1%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update abc86cb...398fcbb. Read the comment docs.


Extract common PlatformView functionality: Gesture and PointerEvent

Description
PlatformViewSurface handling gesture and pointer events
Related Issues
#36779
Tests
I added the following tests:

PlatformViewSurface view can lose gesture arenas
PlatformViewSurface gesture recognizers dispatch events
PlatformViewSurface can claim gesture after all pointers are up
PlatformViewSurface rebuilt during gesture
PlatformViewSurface with eager gesture recognizer
PlatformViewRenderBox reconstructed with same gestureRecognizers
PlatformViewSurface rebuilt with same gestureRecognizers

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

Updated with comments. Ready for another review.

Updated.
Note: With the mixin, we are going to move the hitTestBehavior to the mixin out from the RenderAndroidView.
Do we consider this kind of change a breaking change?


Fix editor gizmos - entity

Fixes #136
Fixes #133
Fixes #132

Such a problem still in Godot 4.0 RC3 in Windows 10.


Add partial implementation of data retention policies part of #175

I think I may need some more understanding about the last two:
# Keep deltas for an additional month (1 whole quarter)
# Keep deleted record information for 6 months after it is removed

This also adds a default value for the default column on streams so that we don't have the true, nil, false situation.

We don't have deltas yet, so there's nothing to be done yet.
For "deleted record information", I think things like our MarcRecord instances qualify (I'm not sure if Rails is going to remove them automatically on us (and we'll have to do something to stop it) or if we need to sweep them up ourselves too)

@cbeer I've confirmed the fact that our MarcRecord are gone on stream deletion. Have you put much thought in to how the reaping might work? It seems like we might have some UI consistancy issues.
Two alternatives I've thought of:

I wonder if a stream could be "archived" which might put it into a state where data cleanup is more explicitly understood
Or the easy thing might just be change streams to 6 months to sync w/ our MarcRecord needs and call it a day.

options 1 or 2 sound fine to me. Option 1 might be easy enough (flag it, purge the files)?


code quality: apply dart lint rules, format and remove unused imports

Hello everyone !
Really glad that tflite for flutter is moving forward with the little love needed for the old community plugin !
Here's some small fixes to avoid the 51 linter's warns in order to (start) improving code quality :

moving to UpperCamelCase style
remove unused imports
unnecessary cast
dart format everywhere

This is a partial copy of a personal fork of the old repo I currently use for few projects  ( https://github.com/am15h/tflite_flutter_plugin/pull/235 )
Happy to discuss about it 🎉

LGTM. Can you also send up a PR adding your name under the AUTHORS file in the project root? Thanks!


Add a string methods cop

This change adds a cop that can be configured to add an offense when a
string method is used when another equivalent method is preferred. It
adds a default to prefer to_sym over intern. It is modeled after the
CollectionMethods cop which checks for preferred methods on Enumerable.
/cc @jrafanie @Fryguy

concat over <<

Something like this will likely yield many false positives.

@bbatsov I'll scrub this from my commit message. TBH I was struggling to find another example for String but felt obliged to create a StringMethods after CollectionMethods. What I'd really like is more room to expand upon preferred methods in general....but can start here if you think that's OK?

@jonas054 @rrosenblum just updated to incorporate your comments/suggestions. Can you rereview?

:+1: Looks good to me.

:+1:

Damn. I should have actually read the PR - 4 commits, instead of 1 and no changelog entry. Guess I'll do the unthinkable and rewrite the history.

@bbatsov apologies on missing the changelog. anything I can do to help? I'll make sure to squash next time prior to merging. Thanks for your assistance in getting this merged
:heart:

anything I can do to help?

Guess you can add it in another PR. I've combined the 4 commits and force-pushed to master. Once again I realize it's a bad idea to review code when I'm that tired. :-)

@bbatsov thanks! I'll take care of that part


change folder name #22

@kunal232i  close this bro !  this issue is assigned  for @tanya-gupta25
Hope to see more contribution from your side . :smile:
Thank u

ok, no problem.


[P2] failed running soletta/src/test-fbp/bitwise-int.fbp in Minnowboard

soletta sha1: 69f00c94f6ea36807022bc1dd715429644709ee6
Plattform: Minnowboard
FAILED running /home/root/soletta/src/test-fbp/javascript.fbp
output returned:
Output:
WRN:sol-flow ./src/lib/flow/sol-flow-resolver-conffile.c:189 _resolver_conffile_get_module() failed to get rootdir for module test
bitwise-byte.fbp:43:32 Couldn't resolve type 'test/result' of node 'test_byte_bitwise_and'
Thank you.

OK, in fact this is not a test error. The minnow image is being generated with Soletta without JS support (duktape is not being built).
I'm rebuilding the image, adding the step needed to include duktape.
cc: @brunobottazzini

Issue retested with duktape support enabled and everything worked.