Crashlytics Xcode 13 build regressions

#8436 introduces several build regressions for Xcode 13. See https://github.com/firebase/firebase-ios-sdk/pull/8665/checks?check_run_id=3634265019.
Please fix or revert before the Tuesday M105 code freeze.

This was fixed in #8679


Current Linux 64 release tar is missing the micro binary

du -h micro-linux64.tar.gz
4.0K	 micro-linux64.tar.gz

This seems to have been caused by my build script not liking the fact that a new dependency was added (diffmatchpatch). It should be fixed now (and for the future).


Add workflow for linting framework

Checklist:

[x] Securely signed commits

shoult pre-commit has it as well https://github.com/codeigniter4/CodeIgniter4/blob/develop/admin/pre-commit ?


Wiki fixes

Type: bug
The following has been addressed in the PR:

Move file wiki/iss-server.md to correct name wiki/iis-server.md plus fix the only one reference to that file
Fix a typo in README.md

there are some automatic whitespace cleanups/fixes that my text editor does on save. if they disturb you I could resave with the cleanup feature turned off

Thanks 👍


Confusion about tea magic.

Hi all,
I Installed tea with sh <(curl tea.xyz), I choose to install magic also. Its working magically ! (Its super) But In documents FAQ Section Its mention magic is removed.
How Is it possible ?

We released 1.0.0-alpha.1 three days ago where we changed how magic works. I think you discovered this project in this in between time where documentation is not fully migrated.
sh <(curl tea.xyz) installs v0 which still has magic. We haven't yet migrated the installer as there is a lot of infrastructure to move.
Sorry for the confusion.
tea is still “magical” but it requires an additional step, eg:
$ node
^^ tea can run that; type `tea`

$ tea
tea +node && node
Welcome to Node.js v20.1.2
>

Our blog post here explains in more details the justifications for our changes in v1.
https://tea.xyz/blog/tea-1-0-0-alpha-1/

How can I Install new version, because of I am using m2, brew is not working for me.

Interesting. Homebrew works find on my m2 air. Regardless, one of these options will work for you: https://docs.tea.xyz/run-anywhere/terminals

I tried again, Its working right now. I just deleted the ~/.tea directory to clean old version. Is it enough ?

Generally, should be sufficient. You can remove the (old) magic invocations from your .bashrc/.zshrc/etc files if you like, since you can manage that with the new cli.

The installer now works, though if tea is already installed it doesn't do anything. Or the one liner from the docs also now works so maybe do that:
curl -Ssf https://tea.xyz/$(uname)/$(uname -m).tgz | sudo tar xz -C /usr/local/bin


paketo community UBI builder 0.0.54 cannot build quarkus 3.9 as extender reports : Fatal error compiling: error: release version 21 not supported

Issue
Latest paketo community UBI image cannot build quarkus 3.9 no matter if we set BP_JVM_VERSION to use as value 17 or 21.
pack build ${REGISTRY_HOST}/quarkus-hello:1.0 \
     --builder paketocommunity/builder-ubi-base:0.0.54 \
     -e BP_NATIVE_IMAGE="false" \
     -e BP_JVM_VERSION="17" \
     -e BP_MAVEN_BUILT_ARTIFACT="target/quarkus-app/lib/ target/quarkus-app/*.jar target/quarkus-app/app/ target/quarkus-app/quarkus/" \
     -e BP_MAVEN_BUILD_ARGUMENTS="package -DskipTests=true -Dmaven.javadoc.skip=true -Dquarkus.package.type=fast-jar" \
     --volume $HOME/.m2:/home/cnb/.m2:rw \
     --path .
...
[extender (build)]       [INFO] ------------------------------------------------------------------------
[extender (build)]       [INFO] BUILD FAILURE
[extender (build)]       [INFO] ------------------------------------------------------------------------
[extender (build)]       [INFO] Total time:  18.781 s
[extender (build)]       [INFO] Finished at: 2024-04-11T10:51:00Z
[extender (build)]       [INFO] ------------------------------------------------------------------------
[extender (build)]       [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.1:compile (default-compile) on project quarkus-hello: Fatal error compiling: error: release version 21 not supported -> [Help 1]
[extender (build)]       [ERROR]
[extender (build)]       [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[extender (build)]       [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[extender (build)]       [ERROR]
[extender (build)]       [ERROR] For more information about the errors and possible solutions, please read the following articles:
[extender (build)]       [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[extender (build)] unable to invoke layer creator
[extender (build)] unable to contribute application layer
[extender (build)] error running build
[extender (build)] exit status 1
[extender (build)]       ERROR: failed to build: exit status 1

What should we do ? @BarDweller

The origin of the issue is because when we generate a quarkus project using maven, then it sets the maven compiler to 21 using Quarkus >= 3.8
To get rid of that, we can generate a project where we select the JDK like this
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.3:create \
  -DprojectGroupId=dev.snowdrop \
  -DprojectArtifactId=quarkus-hello \
  -DjavaVersion=17 \
  -DprojectVersion=1.0 \
  -DplatformVersion=3.8.3 \
  -Dextensions='resteasy-reactive,kubernetes,buildpack'

Question: Is there a way to figure out which JDK is packaged (11, 17, 21) by default within the paketo community UBI builder image (paketocommunity/builder-ubi-base:0.0.54) ? Can we override it part of the extension execution (using our own Dockerfile maybe) ?

Question: Is there a way to figure out which JDK is packaged (11, 17, 21) by default within the paketo community UBI builder image (paketocommunity/builder-ubi-base:0.0.54) ? Can we override it part of the extension execution (using our own Dockerfile maybe) ?

No JDKs are packaged within the paketo community UBI builder image. The JDK is installed into the builder image during the extend phase by microdnf, which obtains it from the UBI repository for the appropriate version of the runtime.
The version is resolved using libjvm (a paketo library for java buildpack related stuff), that lib will look at the version detected/requested by any maven/gradle etc build files, and will use BP_JVM_VERSION if set, and if all that fails, will fall back to the version defaulted in the extension.toml for the ubi java extension (currently 17 .. https://github.com/paketo-community/ubi-java-extension/blob/main/extension.toml )

Latest paketo community UBI image cannot build quarkus 3.9 no matter if we set BP_JVM_VERSION to use as value 17 or 21.
What should we do ? @BarDweller

Note that 21 is not a valid option for the paketocommunity UBI builder image, we have PRs pending to add it, and are working through them.

     -e BP_MAVEN_BUILT_ARTIFACT="target/quarkus-app/lib/ target/quarkus-app/*.jar target/quarkus-app/app/ target/quarkus-app/quarkus/" \
     -e BP_MAVEN_BUILD_ARGUMENTS="package -DskipTests=true -Dmaven.javadoc.skip=true -Dquarkus.package.type=fast-jar" \

Also, note that these should not be required when using the paketocommunity UBI builder image, as the image contains the paketo quarkus buildpack that will detect quarkus projects and handle this for you.

As JDK 21 is not yet available I will then use 17 which is available [extender (build)] Installing: java-17-openjdk-headless;1:<IP_ADDRESS>.7-2.el8;x86_64;ubi-8-appstream-rpms
and force maven to use it when the quarkus project is created
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.3:create \
  -DprojectGroupId=dev.snowdrop \
  -DprojectArtifactId=quarkus-hello \
  -DjavaVersion=17 \
  -DprojectVersion=1.0 \
  -DplatformVersion=3.8.3 \
  -Dextensions='resteasy-reactive,kubernetes,buildpack'

So running now this pack command works
REGISTRY_HOST="kind-registry.local:5000"
docker rmi ${REGISTRY_HOST}/quarkus-hello:1.0
pack build ${REGISTRY_HOST}/quarkus-hello:1.0 \
   --builder paketocommunity/builder-ubi-base:0.0.54 \
   -e BP_NATIVE_IMAGE="false" \
   -e BP_JVM_VERSION="17" \
   --volume $HOME/.m2:/home/cnb/.m2:rw \
   --path .
...
[extender (build)] Paketo Buildpack for Executable JAR 6.8.5
[extender (build)]   https://github.com/paketo-buildpacks/executable-jar
[extender (build)]
[extender (build)]   Process types:
[extender (build)]     executable-jar: java -jar /workspace/quarkus-run.jar (direct)
[extender (build)]     task:           java -jar /workspace/quarkus-run.jar (direct)
[extender (build)]     web:            java -jar /workspace/quarkus-run.jar (direct)
===> EXPORTING
[exporter] Adding layer 'paketo-community/ubi-java-buildpack:ajre'
[exporter] Adding layer 'paketo-community/ubi-java-buildpack:helper'
[exporter] Adding layer 'paketo-community/ubi-java-buildpack:java-security-properties'
[exporter] Adding layer 'paketo-buildpacks/ca-certificates:helper'
[exporter] Adding layer 'buildpacksio/lifecycle:launch.sbom'
[exporter] Adding 5/5 app layer(s)
[exporter] Adding layer 'buildpacksio/lifecycle:launcher'
[exporter] Adding layer 'buildpacksio/lifecycle:config'
[exporter] Adding layer 'buildpacksio/lifecycle:process-types'
[exporter] Adding label 'io.buildpacks.lifecycle.metadata'
[exporter] Adding label 'io.buildpacks.build.metadata'
[exporter] Adding label 'io.buildpacks.project.metadata'
[exporter] Setting default process type 'web'
[exporter] Saving kind-registry.local:5000/quarkus-hello:1.0...
[exporter] *** Images (f44f6ea63d6d):
[exporter]       kind-registry.local:5000/quarkus-hello:1.0
[exporter] Reusing cache layer 'paketo-buildpacks/syft:syft'
[exporter] Reusing cache layer 'paketo-buildpacks/maven:application'
[exporter] Reusing cache layer 'paketo-buildpacks/maven:cache'
[exporter] Reusing cache layer 'buildpacksio/lifecycle:cache.sbom'
Successfully built image kind-registry.local:5000/quarkus-hello:1.0


Enable subdirectory support for migrations

This commit implements the functionality to support subdirectories in Laravel migrations. The retrieveSubdirectories function is added, allowing the recursive retrieval of all subdirectories within the specified directory path(s), including child subdirectories.
This enhancement enables a more organized structure for migration files by enabling the creation of subdirectories within the migrations directory. The code handles both single path and array of paths, offering flexibility in defining the target directories.
The migration ordering continues to be based on the existing timestamp ordering, as you can see in the initial example.
See the discussion .
Initial example:

database

migrations

2023_06_22_000000_create_users_table.php

2023_06_22_000001_create_user_xs_table.php

2023_06_22_000002_create_user_ys_table.php

2023_06_22_000003_create_companies_table.php

2023_06_22_000004_create_company_zs_table.php

2023_06_22_000005_create_company_ts_table.php

Now, it can be converted to:

database

migrations

company_migrations

2023_06_22_000003_create_companies_table.php

2023_06_22_000004_create_company_zs_table.php

2023_06_22_000005_create_company_ts_table.php

user_migrations

2023_06_22_000000_create_users_table.php

2023_06_22_000001_create_user_xs_table.php

2023_06_22_000002_create_user_ys_table.php

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Use Kotlin DSL for Kotlin examples

I have a working build.gradle.kts written in Kotlin DSL for example-jdbc-kotlin. If you like, I can submit it in a PR.
Of course, if we switch from Groovy to Kotlin for this example, we should probably do it for all Kotlin examples across the Micronaut ecosystem. If you're interested in changing them, I can take a look at the others  and probably submit PRs for those as well.

See this branch: https://github.com/kensiprell/micronaut-predator/blob/kotlin-dsl/examples/example-jdbc-kotlin/build.gradle.kts

Sounds great. PRs welcome


Lra 605 lsa ride share add validation to all fields in vehicle report

Added validation to vehicle reports:

Mileage (start and end) allows for only numbers
Gas (start and end) allows for only numbers, numbers must be 0 - 100 (gas is a percentage of fuel available)

Includes previous validation:

End mileage cannot be lower than start mileage

@jocelynanderson

I think it would be nice to check mileage in the vehiclereport_controlle.js too. The same way as you did for gas.
gas_start and gas_end are floats in the database, so they are displayed like '20.0' in the form. Is that OK?  If they're percentages the fields should be integers, aren't they?

Thank you!

I have added validation for gas_start and gas_end in vehiclereport_controller.js.
gas_start and gas_end have been migrated to integers.

In regards to the validation for gas_start and gas_end, the model error pops up but not the controller warning. So I do not know if I did this 100% correct.

Oh, I did not read your comment. You didn't add mileage_error to the fors (a div to display the error). Check the Inspect
->console, you will see the error

Thanks! I forgot to add the target to controller - this is done and I moved tThe error message in the model. Message now shows in similar fashion to gas error.

I added clearing the error message to the js controller. To test try to add gas and mileage wrong numbers, then fix only one of them. See this commit 7262b40
If you agree please tel me know, and I'll merge the pull request.


Added ability to specify NS and SA for K8s pod

Signed-off-by: Yurii Shestakov<EMAIL_ADDRESS>

bot:retest

bot:retest

bot:retest

bot:retest

bot:retest

very cool! you need to retag "stable" to accomodate that commits
you can take script example for that at ~mdubman/bin/retag


Treeview in WinUI3 crashes on pressing the close button

What version of WinUI3 are you using? Are you able to make a minimum repro project for the issue?

What version of WinUI3 are you using? Are you able to make a minimum repro project for the issue?

I believe the latest stable version but how do I check and how do I create a minimum repo project for the issue?

Can you recreate the crash in a separate project that has the minimum required code to do so? Alternatively, could you provide the code you are using and the steps you take to cause the crash?


unit tests to reproduce issue #847

Do not merge this is just to show the issue.

close this test PR


Update dates for backup/restore example

On the Point-in-time restore for flexible server (https://docs.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-backup-restore#point-in-time-restore) there is an example about using the Aug 15th and Aug 14th restore points.... the following sentence accidentally refers to Aug 24th and 25th instead....
Current Paragraph:
For example, let us assume the backups are performed at 11pm every night. If the restore point is for August 15, 2020 at 10:00 am, the daily backup of August 14, 2020 is restored. The database will be recovered until 10am of August 25, 2020 using the transaction logs backup between August 24, 11pm until August 25, 10am.
Corrected Paragraph:
For example, let us assume the backups are performed at 11pm every night. If the restore point is for August 15, 2020 at 10:00 am, the daily backup of August 14, 2020 is restored. The database will be recovered until 10am of August 15, 2020 using the transaction logs backup between August 14, 11pm until August 15, 10am.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6e76b110-fa85-f3ba-51db-4e0ee2db3339
Version Independent ID: 4185869c-909d-65e8-8a18-6d96944847e1
Content: Backup and restore in Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/concepts-backup-restore.md
Service: postgresql
GitHub Login: @sr-msft
Microsoft Alias: srranga

@rosscouldrey, Thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you shortly.

@rosscouldrey Thanks for reporting this, we have made the changes through a PR which could take few days to go live.
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


support for "leases" for leader election

Is your feature request related to a problem? Please describe.
Kube audit logs show heavy use of configmaps resource; I believe this is for leader election. I'd like a simpler audit policy that ignores get/update verbs for "leases" (which seem to be the future for leader election locks anyway).
Describe the solution you'd like
I want a flag to let me pick the resource type used for leader election. The default should be backwards compat w/ today's implementation (configmaps) and should also allow me to choose "configmapsleases" or "leases", allowing me to gracefully upgrade cert-manager w/o fear of leader collisions.
This will likely require an upgrade of the controller-runtime dependency, since the new API provides a manager Options field for this setting.
Environment details (remove if not applicable):

cert-manager version: 1.x
Install method: static manifests

/kind feature

/good-first-issue
/help
/priority important-soon

As of cert-manager v1.4 the leader election will be using configmapsleases, see comments here.
We were planning to follow the migration flow of controller-runtime, i.e accept the default lock type.
Theoretically, in v1.5 we could have a flag to allow users to choose, but I guess since it probably makes sense for everyone to be eventually using leases as they're more performant, this flag would only make sense for a couple of releases to allow folks to start using leases sooner?

/remove-lifecycle stale
On Thu, Sep 16, 2021, 8:25 AM jetstack-bot @.***> wrote:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack https://github.com/jetstack.
/lifecycle stale
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/3766#issuecomment-920855889,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR5KLDUWZHQLO2W3BS43A3UCHO4LANCNFSM4ZDXJKOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/remove-lifecycle stale
On Wed, Dec 15, 2021, 6:19 PM jetstack-bot @.***> wrote:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack https://github.com/jetstack.
/lifecycle stale
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/3766#issuecomment-995291083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR5KLAGENS5OGQFYLJB67DUREO77ANCNFSM4ZDXJKOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I realize that we haven't gotten around to it.
@irbekrm it seems like controller-runtime will take forever to migrate from configmapsleases to leases, aka "we should be extremely conservative":
// Default resource lock to "configmapsleases". We must keep this default until we
// are sure all controller-runtime users have upgraded from the original default
// ConfigMap lock to a controller-runtime version that has this new default. Many
// users of controller-runtime skip versions, so we should be extremely conservative
// here.

Would it make sense to go ahead and have a flag for using the leases resource lock?

Looks like the default leader election mechanism in controller runtime might be Leases in the next release https://kubernetes.slack.com/archives/C02MRBMN00Z/p1639502526108900?thread_ts=1639494666.106900&cid=C02MRBMN00Z (I guess that would be v0.12, we're crurrently on v0.11).
We do explicitly  create ConfigMapsLeases instead of relying on controller-runtime defaults (see here).
I think that in cert-manager v1.8 we could also switch to Leases only for leaderlection in both cert-manager and cainjector. We would need to add a clear warning to users that they should not upgrade to v1.8 directly from v1.3 (which was the oldest release that still used ConfigMaps only for leaderelection).
As I understand Kubernetes too will only use Leases for leader election from v1.24 https://github.com/kubernetes/kubernetes/pull/106852
If we moved to Leases only, I think we could also remove all ConfigMap related permissions from cert-manager RBAC (which we couldn't do with a flag).
/milestone v1.8

Closing as it was implemented in #4935

🎉


Reproduce "test" accuracy

I'm having trouble reproducing the test accuracy that you quote in the Readme. In particular running your precise code for ResNet56 I get the best validation error rate of 7.36(16)%. This differs from your quoted value of 6.61% by 5 sigma. How exactly did you determine the quoted test accuracy of your model?

The pretrained models with reported errors are released along with the code. For example, here is the pretrained model for ResNet56, you can verify its accuracy is as reported.
The reported accuracies were obtained by running the training script, no bells and whistles. If during your training you have reached a different accuracy, I would suggest retraining, as the SGD is a stochastic algorithm, thus results can differ from run-to-run.

Thanks, I ran it 6 times and for each run I find the following best (top 1) errors:
7.4, 7.29, 7.4, 6.89, 8.42, 7.95
You can probably run it many times and find a lower test accuracy by statistical fluctuation, but I'm not sure how well that characterizes the model since it depends on the number of runs. I ask because in https://arxiv.org/pdf/2003.04887.pdf we're reporting an error of  7.37 +/- 0.06 % for this exact implementation to compare to our modification, so I wanted to understand the source of the discrepancy.

That is strange. I've had fluctuations above 7 but never so many. I'll re-run training to see what's happening. In meantime, can you share the training log? Also, are you running the training for 200 epochs?

Thanks! Let me know what you find. Here is a link to the log for three ResNet56 runs, training up to 200 epochs: https://www.dropbox.com/s/uuzmrfxtj0u64ha/log_resnet56.txt?dl=0

what is the weight decay? momentum? also, the pytorch version?

I'm using all your default parameters, i.e. batch_size = 128, momentum = 0.9, weight_decay = 1e-4.
I use Python 3.7.6 and PyTorch 1.4.0.

I'm running on PyTorch 1.2.0, but I don't think this is a problem. While I'm re-running the resnet56, I would suggest couple of things:

re-download the data(CIFAR10), might be some images got corrupted?
can you also makre sure that pre-trained resnet56 from the repo achives the reported error?

Thanks, I loaded the parameters from the model you provided online and successfully reproduced the accuracy of 6.61% that you quote, I guess this implies that my data is not corrupted.
Test: [0/79]	Time 0.270 (0.270)	Loss 0.2958 (0.2958)	Prec@1 96.094 (96.094)
Test: [50/79]	Time 0.027 (0.032)	Loss 0.2139 (0.3548)	Prec@1 96.094 (93.244)
 * Prec@1 93.390

The training finished with an error of 7.5% on PyTorch 1.2, so there is definitely something going on. Then I re-run on PyTorch 1.1 and got 6.7%. Currently, I'm not sure whether this is PyTorch's fault, or just variability of the training itself. However, I don't think I will look into this issue, so I would recommend using older PyTorch versions for now.
Note: I have not run multiple experiments to compute the mean and std of the error.

Ok, great, thanks for checking that out. At least now I know the source of the discrepancy and we'll report our PyTorch version along with the accuracy we find. Beautiful implementation by the way! You've made my life very easy.


Possible to edit implementation of RCTPicker.m in the ios folder?

Hi, I wanted to add some custom behavior to the underlying native IOS Picker and I was attempting to make changes to the RCTPicker.m file but I wasn't able to see the changes reflected in my app.
Is it possible to edit this implementation, and if so, do I have to make some sort of local patch or re-build in a certain way, etc?
Would appreciate any help or pointers

Realized that I handled appropriately ran pod install which was the reason the changes weren't reflected. However, now during the builds I'm getting duplicate symbols errors.

Realized that I was making edits to these files, but that my app was rendering the RCTPicker.m file that was contained in React Native node module (specifically node_modules/react-native/React/Views/RCTPicker.m).


only high vulns fixed

Codecov Report

Merging #1588 (2a6a6ba) into master (ce41093) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##           master    #1588   +/-   ##
=======================================
  Coverage   78.49%   78.49%
=======================================
  Files         280      280
  Lines        7906     7906
=======================================
  Hits         6206     6206
  Misses       1329     1329
  Partials      371      371


Do not cache pip

Pip has a 3.3GB cache of torch and friends. Do not keep this in the image. The vllm inference image should be around 6.7 GB after this. It's currently > 10 GB.
What does this PR do?
It removes the 3.3 GB cache of files that are downloaded.

cc @yanxi0830 just FYI


Split "Clip" and "Save" Buttons into Separate Options

Kinda hate clips button, but love to save videos

Hey there! Thank you for contributing @ilyadb !
I've already gone through this route in the past, but there's an issue regarding YouTube consistency. Here's the following screenshot, as an example:

With the elements you provided in the PR, I would be hiding "Donate" and Clip (in this order) if the view width was larger to fit those two buttons. It's an inconsistency on YouTube itself, and a more robust solution is required.


Remove NoiseAdaptiveLayout and CrosstalkAdaptiveSchedule

Summary
This commit removes two transpiler passes that are no longer useful in modern Qiskit. NoiseAdaptiveLayout has largely been superseded by VF2Layout and VF2PostLayout which takes noise into account for layout selection. The CrosstalkAdaptiveSchedule isn't usable anymore as it relies on custom fields being set to report cross talk in the BackendProperties payload for a BackendV1 instance. As most backends are using BackendV2 now and no current backends are reporting this custom field the pass can't be used.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.001%) to 87.555%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
2
92.93%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
59175

Relevant Lines:
67586

💛  - Coveralls


This /dev/null was extraneous and preventing push

Third times a charm? :wink:
Verified this one locally as well with my own token.

Wasn't the /dev/null there to prevent information leak?  https://medium.com/@nthgergo/publishing-gh-pages-with-travis-ci-53a8270e87db

Fixed. So glad you read through that. Thanks @blink1073

At least one of us is responsible.  :wink:

It worked!  http://jupyter.org/jupyter-js-services/

:beers:

:smile: :+1:
:beers:


Hello Microverse features

Modified
-README.md
-LICENSE.md
issue #1

As Suggested I have done changes as follows
-Removed .hintx file from .gitignore
-Added test.md with the text "This file should be ignored by git"
-I have tried to rename the branch but as I have noticed once I rename this branch it will automatically remove this pull request, so that's why I am leaving it as it is for now as "code-review".
as per your suggestion, I will always remember this tip to give meaningful branch names in my future projects.
Thank You for your support 🫡!


feat: action for labeling and closing stale PRs

Per discussion in the maintainer channel.
Uses a PR branch https://github.com/actions/stale/pull/1145 of actions/stale since it has a feature that will allow us to only consider PRs not sitting on the #queue.
There's still placeholder text for the comments, but this is intended to be merged with the debug-only flag until we have the kinks sorted out, so we could fill in that text in a later PR.

Thanks! Let's try this out.
bors delegate+

bors r+


DestinationRule not exported to all namespaces

Bug Description
DestinationRules in the istio-system namespace are correctly exported to all namespaces, but the same DestinationRules in other namespaces, do not appear to get exported to all namespaces.
We would like to put all our common istio configurations (serviceEntries, VirtualServices, destinationRules, and gateways) into one namespace for easy management. From our understanding, it should work, and it sorta does. For example, when we deploy all 4 to the istio-system namespace, every namespace correctly routes with the configs and everything works. But when we move the 4 configs to a new namespace that we’ve called istio-config, things break, and we a “NC” when trying to connect to the service. We’ve found in troubleshooting that we can move the ServiceEntry, VirtualService, and gateway to the istio-config namespace but leave just the “destinationRule” in the istio-system namespace, and everything continues to work. But when we move the destinationRule from istio-system to istio-config with the other configuration files, all other namespaces break. Here is our broken configuration:
---
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: agent-1
  namespace: istio-config
spec:
  hosts:
    - agent-1.example.com
  ports:
    - number: 22
      name: ssh
      protocol: TCP
  resolution: DNS
  exportTo:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: istio-egressgateway-agent-1
  namespace: istio-config
spec:
  selector:
    istio: egressgateway
  servers:
    - port:
        number: 22
        name: ssh
        protocol: TLS
      hosts:
        - "agent-1.example.com"
      tls:
        mode: ISTIO_MUTUAL
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: egressgateway-for-agent-1
  namespace: istio-config
spec:
  host: istio-egressgateway.istio-system.svc.cluster.local
  exportTo:
    - "*"
  subsets:
    - name: agent-1
      trafficPolicy:
        portLevelSettings:
          - port:
              number: 22
            tls:
              mode: ISTIO_MUTUAL
              sni: agent-1.example.com
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: agent-1
  namespace: istio-config
spec:
  exportTo:
    - "*"
  hosts:
    - "agent-1.example.com"
    - "agent-1"
  gateways:
    - mesh
    - istio-egressgateway-agent-1
  tcp:
    - match:
        - gateways:
            - mesh
          port: 22
      route:
        - destination:
            host: istio-egressgateway.istio-system.svc.cluster.local
            subset: agent-1
            port:
              number: 22
          weight: 100
    - match:
        - gateways:
            - istio-egressgateway-agent-1
          port: 22
      route:
        - destination:
            host: agent-1.example.com
            port:
              number: 22
          weight: 100

---

Again, the fix is to change the destination rule to:
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: egressgateway-for-agent-1
  namespace: istio-system
spec:

But the docs say we should be able to use any namespace when using the ExportTo: "*". Thanks for the help! =)
https://istio.io/latest/docs/reference/config/networking/destination-rule/#DestinationRule
Version
$ istioctl version
client version: 1.16.0
control plane version: 1.16.0
data plane version: 1.16.0 (10 proxies)
$ kubectl version --short
Client Version: v1.23.13
Server Version: v1.23.14+rke2r1

Additional Information
No response

DR can only impact hosts in their own namespace, or override hosts for proxies in their namespace. Allowing a completely unrelated ns to override settings for everyone else would be a security issue.

But the documentation:
https://istio.io/latest/docs/reference/config/networking/destination-rule/#DestinationRule
Says that you can use the exportTo on the DestinationRule to export it to any or all namespaces:
exportTo: A list of namespaces to which this destination rule is exported. The resolution of a destination rule to apply to a service occurs in the context of a hierarchy of namespaces. Exporting a destination rule allows it to be included in the resolution hierarchy for services in other namespaces. This feature provides a mechanism for service owners and mesh administrators to control the visibility of destination rules across namespace boundaries.

exportTo * is the default and follows the semantics I listed. Other
settings are for restricting that even further.
On Tue, Dec 27, 2022, 11:33 AM fluzzykitten @.***>
wrote:

But the documentation:
https://istio.io/latest/docs/reference/config/networking/destination-rule/#DestinationRule
Says that you can use the exportTo on the DestinationRule to export it to
any or all namespaces:
exportTo: A list of namespaces to which this destination rule is exported. The resolution of a destination rule to apply to a service occurs in the context of a hierarchy of namespaces. Exporting a destination rule allows it to be included in the resolution hierarchy for services in other namespaces. This feature provides a mechanism for service owners and mesh administrators to control the visibility of destination rules across namespace boundaries.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/42570#issuecomment-1366128767, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLSCFZY27BMTFPPWT3WPNABJANCNFSM6AAAAAATJ6BFHI
.
You are receiving this because you commented.Message ID:
@.***>

Right... so, you agree that there is a bug. It should work, since I'm explicitly saying the same as the default, which is to export to all namespaces.

It exports to all namespaces following the semantics I mentioned. All namespaces have access to it but chose not to do anything with it since it's not applicable.

I don't understand what you're saying. It sounds like you're saying it should be possible, which is also what the docs say, but you're not telling me what I'm doing wrong in the config.
Furthermore, this bug sometimes works and sometimes not work. As I mentioned in the post, a pod in namespace separate-namespace has access to the Destination rule with exportTo: "*" when it exists in the istio-system namespace, but with the same DestinationRule same settings, a pod in namespace separate-namespace does not have access to the same Destination rule when it exists in istio-config, or demo, or namespace2, or any other namespace, despite the DestinationRule being exported to all namespaces. Which is why this is a bug. Unless you see an error in my configuration, it should work the same in any namespaces, not just the namespace with the Istio Operator.

See https://istio.io/latest/docs/ops/best-practices/traffic-management/#cross-namespace-configuration. exportTo can further restrict that for values other than *. But it cannot widen it.

Thanks for sending that link. It would've been nice if at some point you actually said the problem, which was the lookup path, not a configuration problem. TL;DR for those who don't want to read through link attached, the reason global destination rules work in istio-system and not other namespaces is because:
You can avoid this problem by creating the destination rule in the same namespace as the corresponding service, default in this example. It would then get applied to requests from clients in any namespace. You can also move the destination rule to the istio-system namespace, the third namespace on the lookup path, although this isn’t recommended unless the destination rule is really a global configuration that is applicable in all namespaces, and it would require administrator authority.

https://istio.io/latest/docs/ops/best-practices/traffic-management/#cross-namespace-configuration


Intercept methods/setters globally using rules rather than explicit method/property names

Would it be possible to extend Post do AOP style method/property interception (including privates) using this approach? Or is there a reason (aside from it being outside of scope) why it wouldn't work?

I don't see a reason why it can't be done. But as you rightly mentioned, it's out of scope of this project


Segmentation fault in hsmm-possiblechangepoints-meanfield.py

I  run the HSMM meanfiled demo example, but a fault produces.

root@bd63:/home/exppy2/pyhsmm/examples# python hsmm-possiblechangepoints-meanfield.py
Segmentation fault

This fault occurs in line 38 of  script pyhsmm/examples/hsmm-possiblechangepoints-meanfield.py

truemodel.plot()

and in line 254 of pyhsmm/models.py

if draw: plt.draw()

I'm not planning to use that code in the near future so I can't say when or if I might fix this. If you want to debug it, you may want to recompile the C++ code with debug symbols and run the code with gdb to find where the segfault is happening. However, since it appears to happen in normal Python code, it's probably the case that the mean field message passing code for the 'possible changepoints' models is writing out of bounds.


Unable to make REST POST request using CRT and Key file

I have been trying to make rest calls using client certificate in my request but unable to do so due to this error message "javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
Below are the steps I have tried so far:

I was provided with mycompany.pem and cert.key private files

I have converted .pem and key file to Java mycompany.p12 file format

Added mycompany.p12 to java keyStore

Then I've executed following code
`      KeyStore keyStore = null;
SSLConfig config = null;
String password = "changeit";
 try {
     keyStore = KeyStore.getInstance("PKCS12");
     keyStore.load(
             new FileInputStream("/mypath/mycompany.p12"),
             password.toCharArray());

 } catch (Exception ex) {
     System.out.println("Error while loading keystore >>>>>>>>>");
     ex.printStackTrace();
 }

 if (keyStore != null) {

     org.apache.http.conn.ssl.SSLSocketFactory clientAuthFactory = new org.apache.http.conn.ssl.SSLSocketFactory(keyStore, password);

     // set the config in rest assured
     config = new SSLConfig().with().sslSocketFactory(clientAuthFactory).and().allowAllHostnames();
 }
 RestAssured.config = RestAssured.config().sslConfig(config);

 Response response = RestAssured.given().contentType(ContentType.JSON).body(MY_JSON_BODY).when().post("MY_URL").then().extract().response();

 System.out.println(response.statusCode());;`

When above code is executed, system throws this error message
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

When I've sent a request using relaxedHTTPSValidation then the system does not throw the exception from previous steps however response status code returned as 400 instead 201.

I have also tried disabling the SSLValidation using below code but it didn't work either

` public static void disable() {
try {
SSLContext sslc = SSLContext.getInstance("TLS");
TrustManager[] trustManagerArray = { new NullX509TrustManager() };
sslc.init(null, trustManagerArray, null);
HttpsURLConnection.setDefaultSSLSocketFactory(sslc.getSocketFactory());
HttpsURLConnection.setDefaultHostnameVerifier(new NullHostnameVerifier());
} catch(Exception e) {
e.printStackTrace();
}
}
private static class NullX509TrustManager implements X509TrustManager {
    public void checkClientTrusted(X509Certificate[] chain, String authType) throws CertificateException {
        System.out.println();
    }
    public void checkServerTrusted(X509Certificate[] chain, String authType) throws CertificateException {
        System.out.println();
    }
    public X509Certificate[] getAcceptedIssuers() {
        return new X509Certificate[0];
    }
}

private static class NullHostnameVerifier implements HostnameVerifier {
    public boolean verify(String hostname, SSLSession session) {
        return true;
    }
}

public static Boolean disableSSLValidation() throws Exception {
    final SSLContext sslContext = SSLContext.getInstance("TLS");

    sslContext.init(null, new TrustManager[]{new X509TrustManager() {
        @Override
        public void checkClientTrusted(X509Certificate[] x509Certificates, String s) throws CertificateException {
        }

        @Override
        public void checkServerTrusted(X509Certificate[] x509Certificates, String s) throws CertificateException {
        }

        @Override
        public X509Certificate[] getAcceptedIssuers() {
            return new X509Certificate[0];
        }
    }}, null);

    HttpsURLConnection.setDefaultSSLSocketFactory(sslContext.getSocketFactory());
    HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {
        public boolean verify(String hostname, SSLSession session) {
            return true;
        }
    });

    return true;
}`

I am able to make successful request using POSTMAN

Note: I have been trying to make this work for some time so any help would be highly appreciated
Thanks,

Check out this: https://github.com/rest-assured/rest-assured/issues/719
Maybe it help you

@pumano Thanks, did any of those approaches worked for you?

the above script worked, I had to add cer file to my keystore then it worked just fine.
thanks @pumano

@mmuntakim15 I am also getting an error
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Which cert file you added & to which keystore? can you please explain in detail?

I tried RestAssured.authentication= RestAssured.certificate("/Users/xxx/xx/cert.p12", “pwd");
still get javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Even after adding the certificate to Jdk cacert i still face the issue .
Desperately need help here .

package com.qa.setup;
import static io.restassured.RestAssured.given;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.security.KeyManagementException;
import java.security.KeyStore;
import java.security.KeyStoreException;
import java.security.NoSuchAlgorithmException;
import java.security.SecureRandom;
import java.security.UnrecoverableKeyException;
import java.security.cert.CertificateException;
import javax.net.ssl.KeyManager;
import javax.net.ssl.KeyManagerFactory;
import javax.net.ssl.SSLContext;
import javax.net.ssl.TrustManager;
import javax.net.ssl.TrustManagerFactory;
import io.restassured.RestAssured;
import io.restassured.config.RestAssuredConfig;
import io.restassured.config.SSLConfig;
import io.restassured.response.Response;
public class Certificates {
public static void main(String[] args) throws KeyManagementException, UnrecoverableKeyException, NoSuchAlgorithmException, KeyStoreException, CertificateException, FileNotFoundException, IOException {
	String clientPassword = "password"; // use Passphrase given by client/dev
	String clientCertificatePath ="cert_key.p12";
	String trustStorePath="C:\\Program Files\\jdk-8.0.1\\jre\\lib\\security\\cacerts";
	String trustStorePassword = "changeit";  // changeit is the default password
	KeyStore clientStore = KeyStore.getInstance("PKCS12");
	clientStore.load(new FileInputStream(clientCertificatePath), clientPassword.toCharArray());

	KeyManagerFactory kmf = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
	kmf.init(clientStore, clientPassword.toCharArray());
	KeyManager[] kms = kmf.getKeyManagers();

	KeyStore trustStore = KeyStore.getInstance("JKS");
	trustStore.load(new FileInputStream(trustStorePath), trustStorePassword.toCharArray());

	TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
	tmf.init(trustStore);
	TrustManager[] tms = tmf.getTrustManagers();

	SSLContext sslContext = null;
	sslContext = SSLContext.getInstance("TLS");
	sslContext.init(kms, tms, new SecureRandom());

	SSLSocketFactory lSchemeSocketFactory=null;

	lSchemeSocketFactory = new SSLSocketFactory(clientStore, clientPassword, trustStore);
	RestAssuredConfig reconfig = RestAssured.config().sslConfig(new SSLConfig().with().sslSocketFactory(lSchemeSocketFactory).and().allowAllHostnames());

	Response res=given().when().contentType("application/json").header("client_id", "123").header("client_secret", 456").config(reconfig).body("bodyString").post(url);
	System.out.println(res.asString());
}

}
This is working code . Pasting here , maybe it will help someone.
Downlaod openssl-0.9.8k_X64.zip ,  go in bin folder and run below command
openssl pkcs12 -export -inkey Key.pem  -in Cert.pem  -out cert_key.p12

@conngbha Thank you for posting the code above here. I'm trying to do the same thing described in this PR: Make REST POST request using .cert and key file. I did the following:

add the certificate to cacerts using the command: keytool -import -trustcacerts -alias mdecert -file /Users//IdeaProjects/restassured-cert-example/example.cert.pem -keystore -cacerts
convert the key.pem file to .p12 file format using the command: openssl pkcs12 -export -nocerts -inkey example.key.pem -out newformatexample.key.p12
then tried your code - please see the code below:

`      String clientPassword = "pass"; // use Passphrase given by client/dev
String clientCertificatePath ="localhost.example.com.key.p12";
    String trustStorePath=System.getProperty("java.home")+"/lib/security/cacerts";
    String trustStorePassword = "changeit";  // changeit is the default password

    //String trustStorePassword = "pass";  // changeit is the default password
    KeyStore clientStore = KeyStore.getInstance("PKCS12");
    clientStore.load(new FileInputStream(clientCertificatePath), clientPassword.toCharArray());

    KeyManagerFactory kmf = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
    kmf.init(clientStore, clientPassword.toCharArray());
    KeyManager[] kms = kmf.getKeyManagers();

    KeyStore trustStore = KeyStore.getInstance("PKCS12");
    trustStore.load(new FileInputStream(trustStorePath), trustStorePassword.toCharArray());

    TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
    tmf.init(trustStore);
    TrustManager[] tms = tmf.getTrustManagers();

    SSLContext sslContext = null;
    sslContext = SSLContext.getInstance("TLS");
    sslContext.init(kms, tms, new SecureRandom());

    SSLSocketFactory lSchemeSocketFactory=null;

    lSchemeSocketFactory = new SSLSocketFactory(clientStore, clientPassword, trustStore);
    RestAssuredConfig reconfig = RestAssured.config().sslConfig(new SSLConfig().with().sslSocketFactory(lSchemeSocketFactory).and().allowAllHostnames()
            .keyStore(clientCertificatePath, "pass").keystoreType("PKCS12")
            .trustStore(trustStorePath, trustStorePassword).trustStoreType("PKCS12"));

    Response res= given().when().contentType("application/json")
                    .config(reconfig).relaxedHTTPSValidation()
            .get("someendpointurl");

    System.out.println(res.asString());`

But it also didn't work.
Do you maybe have any idea what else I can try? Thanks in advance.


Application: Nova Budapest

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[x] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[ x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or Polkadot (USDC & USDT) address in the application).
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[ ] The software delivered for this grant will be released under an open-source license specified in the application.
[ ] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Hi @rivaratyr, thank you for the application and the effort you put into it, but the committee decided not to support it. Main reasons being that the project is EVM-focused, the deliverables are very specific to your project and mainly don't fit the program scope, and the price.
Best of luck!


Issues migrating dse 6.8.14 to apache 4.0.13

Hi!
We are planning to migrate some dse 6.8 cluster that are running into docker to apache cassandra 4.0 that will be running into k8s, for that we have created a new 4.0.13 image including your everywherestrategy patch.
Testing the image alone, seems to be working fine as it is able to create the keyspace with the everywherestrategy and it is able to insert rows there.
Problems begin when we try to connect the new cassandra 4.0 datacenter to the existing dse 6.8 cluster. Next errors appear when the first cassandra node tries to connect to dse:
Errors on DSE
ERROR [CoreThread-0] 2024-12-05 09:23:31,298  InboundHandshakeHandler.java:123 - Unexpected error while negotiating internode protocol handshake java.lang.NegativeArraySizeException: null         at org.apache.cassandra.net.CompactEndpointSerializationHelper.deserialize(CompactEndpointSerializationHelper.java:58)         at org.apache.cassandra.net.async.HandshakeProtocol$ThirdHandshakeMessage.maybeDecode(HandshakeProtocol.java:281)         at org.apache.cassandra.net.async.InboundHandshakeHandler.handleMessagingStartResponse(InboundHandshakeHandler.java:266)         at org.apache.cassandra.net.async.InboundHandshakeHandler.decode(InboundHandshakeHandler.java:107)         at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:520)         at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459)         at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:289)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)         at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)         at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)         at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)         at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800)         at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:529)         at org.apache.cassandra.concurrent.EpollTPCEventLoopGroup$SingleCoreEventLoop.processEpollEvents(EpollTPCEventLoopGroup.java:1020)         at org.apache.cassandra.concurrent.EpollTPCEventLoopGroup$SingleCoreEventLoop.processEvents(EpollTPCEventLoopGroup.java:988)         at org.apache.cassandra.concurrent.EpollTPCEventLoopGroup$SingleCoreEventLoop.run(EpollTPCEventLoopGroup.java:542)         at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)         at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)         at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)         at java.lang.Thread.run(Thread.java:750)         at org.apache.cassandra.utils.concurrent.InlinedThreadLocalThread.run(InlinedThreadLocalThread.java:251) Contraer
Errors on Apache Cassandra
ERROR [Messaging-EventLoop-3-1] 2024-12-05 09:23:29,343 NoSpamLogger.java:98 - /XXXXXXXX:7000->/XXXXXXXX:7000-URGENT_MESSAGES-[no-channel] failed to connect java.nio.channels.ClosedChannelException: null         at org.apache.cassandra.net.OutboundConnectionInitiator$Handler.channelInactive(OutboundConnectionInitiator.java:248)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)         at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)         at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)         at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)         at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)         at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:819)         at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)         at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)         at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)         at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)         at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)         at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)         at java.base/java.lang.Thread.run(Unknown Source)
We tried different tests (docker to docker , k8s to k8s, docker to k8s) with same result , so we assume that the issue should be something else...
Is it something else for this migration to be achieved needed?
Thanks in advance!

@smiklosovic maybe you could give some ideas here?
Thanks so much in advance.

@sinohC can you run your setup without this plugin? Can be even dse 6.8 and 4.0.13 in one cluster? I think this plugin is not hard requirement to do that. If it works without this plugin and the error happens with this plugin, then it it legit to deal with it.

@sinohC there is also test framework in test/ directory by which you can verify what combination of versions work and what not. Also, the plugin for Cassandra 4 is compiled against version 4.0.7 so it might differ in 4.0.13 somehow. Also I do not see this was tested against DSE 6.8, the tests were conducted on 5.x if you look into test results markdown ...
Please try to verify that you can use that against 4.0.7 first by executing the testing framework.

Your setup is also very specific because what you try to do is to have 1 dc on DSE and another dc on Apache Cassandra. So you are trying to have two separate datacenters. Maybe it would be worth to test what happens if you are joining Apache Cassandra node to the same DC all your DSE nodes are.

@sinohC can you run your setup without this plugin? Can be even dse 6.8 and 4.0.13 in one cluster? I think this plugin is not hard requirement to do that. If it works without this plugin and the error happens with this plugin, then it it legit to deal with it.

You mean that the desired migration should work without this plugin? Or you mean to try the connectivity just to test if the error changes? I mean, I never tested without the plugin as I assume it wont work and the purpose of the plugin is to fix the posible problems related to the everywherestrategy

Your setup is also very specific because what you try to do is to have 1 dc on DSE and another dc on Apache Cassandra. So you are trying to have two separate datacenters. Maybe it would be worth to test what happens if you are joining Apache Cassandra node to the same DC all your DSE nodes are.

We will test this option too.


Update serialization tests with PauliWord order updates

Context:
Pennylane #5301 updates PauliWord to reorder differently when using the @ operator.
Description of the Change:

Update tests in test_serialize.py to accommodate the change mentioned above.
~Also added tests for device_vjp=True with all interfaces. Not related to the above changes, but it's getting quite cumbersome to merge small changes multiple times.~ These were removed and will be added in a future PR.

Not to be merged until Pennylane #5301 is merged.
Benefits:
Possible Drawbacks:
Related GitHub Issues:

[sc-57962]

@mudit2812, I added do not merge label just in case.
Feel free to remove it as soon as https://github.com/PennyLaneAI/pennylane/pull/5301 is merged.

Since some CI overrides the requirements-dev.txt file and always uses pennylane from master, I've skipped CI for now until the PR needed for CI in this PR to pass are merged to pennylane. But I'd like to have approvals here before I merge that PR so that I can merge this PR as soon as possible after the merge as the changes will cause CI failures in other lightning PRs


Doubt regarding File Structure

I have a few doubts about the applications, hope they can be answered.
What is the difference between having a pages folder and a screens folder for the application ?
I might be confused here but there is a folder called services but most of the logic tends to be written in the UI files itself. Is there something about the architecture i am missing out on?
For example in the  settings_screen.dart file the code for deleting an account, logging out of an account and changing the password all are in the same file.
Usually i use the Stacked Architecture with clear UI and logic seperation, so just wanted to know the architecture the application is following. Would love to have a discussion with the moderators @cfsmp3 and @harchani-ritik  if using stacked architecture can be an option.

@AbdulMalikDev
So, the convention I used here was widgets in pages were placed horizontally with each other on the navigation stack and those in screens were placed vertically.
This stacked architecture looks good though, surely, the code can be refactored according to this, you can elaborate on the advantages of using this architecture in your proposal and yes, we surely have a discussion regarding this.

@AbdulMalikDev
So, the convention I used here was widgets in pages were placed horizontally with each other on the navigation stack and those in screens were placed vertically.
This stacked architecture looks good though, surely, the code can be refactored according to this, you can elaborate on the advantages of using this architecture in your proposal and yes, we surely have a discussion regarding this.

Thank you for replying. Now i understand the pages and screens folder.
Regarding the Stacked Architecture i would love to elaborate and take the responsibility of migrating the application, if it has been chosen.


Added StyleableToast.Builder class for builder pattern implementation

As requested via #1

@PDDStudio Sorry for the delay. I'm ready to merge your pull reqeuest now. But could you first pull the latest changes first.

@Muddz I've merged your latest changes into my fork and resolved the conflicts. You should be able to merge it without any conflicts now.

Finally done!
Its up and running in the new version 1.0.6 and is in the Readme
But I also made some changes on your request
I changed the withBoldText() to work without boolean argument: .withBoldText()
and the method isValidValue did not work with int colors as they also can have minus values.
Else everything is fine and works like charm


expose a function to return the readyState of the socket

It's useful to be able to tell whether the socket is active, opening, etc.
WebSocket exposes a readyState variable for this. It would be nice to expose it through the api

Or maybe just adding a way to get the websocket object underneath webstomp-client. This will avoid to add tons of abstraction just to mimic websocket API.

I'm realizing that I need to create subscribe/unsubscribes outside of the connect callback. So, either I need to tell whether the connection is open or not or, ideally, I could just call the connect method sa often if I wanted, with the socket knowing if it was open or not and immediately returning against the callback with the already open connection or, creating a new connection.

What I do in my app is maintening a list of subscription. If I'm already connected, I call the client subscribe method, if I'm not, I store the subscription for later.
Maybe that logic can be a part of the webstomp client.

Could you share some of that code as an example. How do you know if you're already connected?

Sorry I cannot. I just store a simple boolean flag that I switch to true once connected.

I think the websocket.readyState will provider the info
On Tue, Jul 5, 2016 at 6:22 PM Jérôme Steunou<EMAIL_ADDRESS>wrote:

Sorry I cannot. I just store a simple boolean flag that I switch to true
once connected.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JSteunou/webstomp-client/issues/17#issuecomment-230607223,
or mute the thread
https://github.com/notifications/unsubscribe/AAXfv0FqCxF1kffR3VGYP1LpQ13erB_Aks5qSsssgaJpZM4I8ylu
.

--
Kind regards,
Marc
M.Schipperheyn

Then why not use stomp.ws.readyState ?

yeah, ok. the ideal would be for calling CONNECT to be indemnipotent, so subscribes and sends could always run inside the safe context of the callback.

Pull request are welcome if you wanna share your idea 😉
Le 7 juil. 2016 00:53, "Marc Schipperheyn"<EMAIL_ADDRESS>a
écrit :

yeah, ok. the ideal would be for calling CONNECT to be indemnipotent, so
subscribes and sends could always run inside the safe context of the
callback.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JSteunou/webstomp-client/issues/17#issuecomment-230931813,
or mute the thread
https://github.com/notifications/unsubscribe/ACNyt3dBNsUj3lsMMjkgVMCSQJg6omp1ks5qTDH4gaJpZM4I8ylu
.

Well, what I ended up implementing is a buffering solution, backed by a reconnecting websocket. Not sure if it's a good idea. WDYT?
const socket = class Socket{

  constructor(){}

  createAndConnect(sessionToken, rememberMeToken, onConnectSuccess, onConnectFailure){
    this.createClient(sessionToken, rememberMeToken);
    this.connect(onConnectSuccess, onConnectFailure);
  }

  createClient(sessionToken, authToken){

    console.info(`Connecting to WebSocket: ${config.getWebsocketUrl()}`);

    this.sendBuffer = [];
    this.subscribeBuffer = [];
    this.unsubscribeBuffer = [];
    this.bufferSize = 10;

    let WS = new ReconnectingWebSocket(config.getWebsocketUrl(),{},this.getCookieHeader(sessionToken, authToken), (func) => {
      func();
    });

    WS.debug=config.debugWebsocket;

    this.ws = webstomp.over(
      WS,
      {
        debug:false
      }
    );
  }

  getCookieHeader(sessionToken, authToken){
    if(sessionToken || authToken)
      return {
        'Cookie': ATTR_SEND_SESSIONID + '=' + sessionToken + ';' + ATTR_SEND_REMEMBERME_TOKEN + '=' + authToken
      };

    return {};
  }

  getClient(){
    return this.ws? this.ws : new Error("No websocket present. Call createAndConnect first");
  }

  connect(onConnectSuccess, onConnectFailure){
    var that = this;

    this.headers = {};

    this.ws.connect(this.headers, function(frame){

      onConnectSuccess(frame);

      that.processBuffer.bind(that)();

    }, onConnectFailure);
  }

  disconnect(){
    this.ws.disconnect();
  }

  send(destination, body, bufferable = true){
    if(this.readyState() === WS_STATES.OPEN){
      this.ws.send(destination,body, this.headers);
      return;
    }

    if(bufferable && this.sendBuffer.length <= this.bufferSize){
      this.sendBuffer.push({
        destination,
        body
      });
    }else{
      throw new Error('Trying to send message on closed socket and no buffer available', destination, this.readyState());
    }
  }

  subscribe(destination, callback, bufferable = true){
    if(this.readyState() === WS_STATES.OPEN){
      this.ws.subscribe(destination, (message) => {

        message.ack();

        callback(message);

      }, this.headers);
      return;
    }

    if(bufferable && this.subscribeBuffer.length <= this.bufferSize){

      if(this.subscribeBuffer.filter((el) => el.destination === destination).length === 0)
        this.subscribeBuffer.push({
          destination,
          callback
        });
    }else{
      throw new Error(`Trying to subscribe on closed socket and no buffer available: ${destination}, readyState: ${this.readyState()}, buffer length: ${this.subscribeBuffer.length}`);
    }
  }

  unsubscribe(destination, bufferable = true){
    if(this.readyState() === WS_STATES.OPEN){
      this.ws.unsubscribe(destination);
      return;
    }

    if(bufferable && this.unsubscribeBuffer.length <= this.bufferSize){
      if(this.unsubscribeBuffer.filter((el) => el.destination === destination).length === 0)
        this.unsubscribeBuffer.push({
          destination
        });
    }else{
      throw new Error(`Trying to unsubscribe on closed socket and no buffer available: ${destination}, readyState: ${this.readyState()}, buffer length: ${this.unsubscribeBuffer.length}`);
    }
  }

  begin(transactionId){
    return this.ws.begin(transactionId);
  }

  commit(tx){
    tx.commit();
  }

  abort(tx){
    tx.abort();
  }

  sessionId(){
    return this.ws.sessionId;
  }

  readyState(){
    return this.ws.ws.readyState;
  }

  processBuffer(){
    console.log('Processing websocket buffer', this.sendBuffer.length);

    //Process unsubscribe first, in case a new subscribe came in for the to be unsubscribed endpoint
    for(let action of this.unsubscribeBuffer){
      this.unsubscribe(action.destination);
    }

    for(let action of this.subscribeBuffer){
      this.subscribe(action.destination, action.callback);
    }

    for(let action of this.sendBuffer){
      this.send(action.destination, action.body, false);
    }

    this.sendBuffer = [];
    this.subscribeBuffer = [];
    this.unsubscribeBuffer = [];
  }

}

export {
  socket as default
}

A PR with a clean diff is more readable

Well, this is just a suggestion.


ModelicaInternal_print to terminal not avilable if NO_FILE_SYSTEM is set

Reported by beutlich on 10 Jun 2014 13:51 UTC
ModelicaInternal_print has two cases:

Output to file or
output to terminal (by simply calling ModelicaFormatMessage) if given fileName is empty.
However the latter case is not available if NO_FILE_SYSTEM is set (e.g. on dSPACE DS1006). This should be improved.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1508

Modified by beutlich on 10 Jun 2014 14:10 UTC

Comment by beutlich on 10 Jun 2014 20:28 UTC
Resolved by b90623e80a0bd3582a493b648249c13d7fb042dd and 35bc6d2bf95376f4ca34fc63a39d2d4523df6e34.

Changelog modified by beutlich on 10 Jun 2014 20:28 UTC
Fixed ModelicaInternal_print (for Modelica.Utilities.Streams.print) to also output the string to terminal on platforms where a file system is not present (e.g. on dSPACE or xPC)


upload lsif to sourcegraph

https://github.com/flamego/flamego/blob/main/.github/workflows/lsif.yml
Don't they have a replacement for lsif?
Yes, they do; SCIP:
"The secret underground is pivoting from LSIF to SCIP, invisibly, as the new Sourcegraph backend."

https://about.sourcegraph.com/blog/introducing-steve-yegge

So maybe that's what we should use.

https://github.com/flamego/flamego/blob/main/.github/workflows/lsif.yml

https://github.com/sourcegraph/sourcegraph/blob/main/.github/workflows/lsif-go.yml


Send User-Agent header with commit hash

This PR adds a User-Agent header on the format node-indexer/<hash>. We try follow the convention described on Wikipedia.
This will be very useful when debugging!
We inject the Git hash using option 1 from Adam's excellent resource https://developers.redhat.com/articles/2022/11/14/3-ways-embed-commit-hash-go-programs#1__using__ldflags. I tried option 3 which should work, but somehow I didn't get any vcs info even when doing go build 🤔
Have verified this locally using Docker build.

Option 3 just missing -buildvcs i think

If you do end up getting runtime/debug ReadBuildInfo() to work then I think we'd probably be interested in the following when debugging on behalf of customers (in priority order if we don't want to squeeze them all in):

vcs.revision
GoVersion
GOARCH
GOOS
vcs.modified
vcs.time

Turns out buildvcs doesn't do it for us either 😕 Not when building by listing Go files directly, like we do with go build ... cmd/main.go https://github.com/golang/go/issues/51279#issuecomment-1048196896


Language badge production

Sporadic behavior noted, function isn't always entered based on console log of function. Even if it is part of the input array.
Transitioning badge strategies, commenting out code, but leaving to return to at a later time.

Decided to not go that route


Rendering performance optimizations, promote-layer mixin

These are some rendering optimizations while working on a custom theme based on Timber, but I figured I would let them bubble up to the framework.
Basically here we're promoting the drawers to their own compositor layers using will-change when it's supported (Firefox, Chrome) or the infamous translateZ hack (Safari).
Also, I fixed a bug on Chrome Mobile when scrolling inside the drawer when it's visible (screenshot).

cc @stevebosworth

Also, if you guys want me to actually put this on a Shopify dev account (let me know what the best way is to do that), I can demonstrate how this code actually does make an improvement to the frame rate of these animations.

Thanks @benknight!  If you want to put this up on a dev shop you can sign up for a partners account here: https://app.shopify.com/services/partners/auth/login
Here's a doc on creating dev stores once you have a partner's account:
https://docs.shopify.com/themes/theme-development/getting-started/development-environment

:+1:  Been using this for awhile and definitely a performance improvement.

Totally forgot to merge this. Great addition, and thanks for the :+1: @zackcote

Thanks for merging.  It had been pending my providing a demo store link but I was ultimately too lazy to bother.  Glad it worked out! :palm_tree: :palm_tree:


Add z-index to FormGroupContainer's remove button

This PR:

Renames .form-remove to .form-group-container-action-button
Gives a z-index to .form-group-container-action-button to prevent it from rendering below sibling elements

I can't actually force the remove button to render under its siblings without these changes, but this looks good to me in any case.

@mlunoe @jfurrow I've adjusted the class and var names as suggested.


HashScan should show the transaction hash in a usable form (Hedera 48-bytes & EVM 32-bytes)

Problem
Consider this transaction:

https://hashscan.io/mainnet/transaction/1685742901.591716003
https://hashscan.io/mainnet/tx/0x1000f86d0ea7169069022d573db69d8b20b586bbab93dd0161efb2c4f74c0c3f
https://mainnet-public.mirrornode.hedera.com/api/v1/contracts/results/0x1000f86d0ea7169069022d573db69d8b20b586bbab93dd0161efb2c4f74c0c3f

HashScan shows the Transaction Hash as:

This is because Hedera tx hashes are 48 bytes. However, EVM tx hashes are 32 bytes (as explained in this StackOverflow answer).
This 48-byte form of the hash, however, is not really usable by any other tool (EVM tools, Mirror REST API, or even HashScan itself - see all links above - they use the 32-byte hash).
We should make it easy for developers and non-developers to obtain the tx id AND a usable tx hash from HashScan - the change proposed below would support that.
Solution
Please consider:
- Renaming the existing field to Hedera Transaction Hash AND adding a field right below called EVM Transaction Hash
Hedera Transaction Hash:
0x1000f86d0ea7169069022d573db69d8b20b586bbab93dd0161efb2c4f74c0c3f132654d46f17cacc4b240d02022146cb
EVM Transaction Hash:
0x1000f86d0ea7169069022d573db69d8b20b586bbab93dd0161efb2c4f74c0c3f
As we onboard new developers, wallets, exchanges, and retail users, we should make it easy to find equivalent information between tools.
Alternatives
No response

Related: https://stackoverflow.com/q/76228588/194982


bug/ partition_pdf omits extractable text

partition_pdf() correctly detects the table, but it does not include within the element the numbers as text in the table. These numbers are indeed detected by the process_file_with_pdfminer() function.

This information dissapears with the clean_pdfminer_inner_elements() and clean_pdfminer_duplicate_image_elements() functions.
Element text:
'Affectations to houses and public buildings Quantity Houses affected Houses flooded Houses destroyed Other buildings affected Collapsed walls'
To Reproduce
elements = partition_pdf(filename=pdf_path,
include_page_breaks=True,
strategy="hi_res",
extract_image_block_types=['Image', 'Table'],
model_name="yolox",
infer_table_structure=False,
extract_image_block_to_payload=True)
Expected behavior
Output the table numbers in the unstructured element text.
18466.pdf

Addressed in https://github.com/Unstructured-IO/unstructured/pull/3618


Missing link to Chapter 2

The page at http://netty.io/wiki/user-guide-for-4.x.html has a paragraph stating:

If you prefer top-down approach in learning something, you might want to start from Chapter 2, Architectural Overview and get back here.

There is no link defined, I would add it myself but could not find that page

@normanmaurer not sure this can be fixed via source code on GitHub?

@normanmaurer @trustin This issues is duplicated with Netty 4.x User Guide - Architectural Overview missing? I think we should keep only one of them.

I think there is a link now. However, the page: https://netty.io/wiki/user-guide-for-4.x.html, which is the starter's guide for netty-4.x now refers to https://netty.io/3.8/guide/#architecture, which seems to be related with an older netty version.


[5.9] Allow all unicode characters in package-name input

Allow all unicode characters in package-name input
Error if the input is empty
Resolves rdar://104617274

cherrypicked from main https://github.com/apple/swift/pull/65111

@swift-ci test


chore: add test coverage report

What does this PR do?
Add test coverage report.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug: LexicalCharacterLimitPlugin CHARACTER_LIMIT - 5 (hardcoded) cant be changed

Lexical version:v0.7.5
Steps To Reproduce

try lexical playground and enable char limit from the options
CHARACTER_LIMIT is fixed to 5 and cant be changed

Link to code example:
https://github.com/facebook/lexical/blob/6e65c989c0d379dccfe28078a76ef49e4dc66443/packages/lexical-react/src/LexicalCharacterLimitPlugin.tsx#L15
The expected behavior
CHARACTER_LIMIT should be through the plugin props, similar to MaxLengthPlugin
reference to CharacterLimitPlugin -
https://github.com/facebook/lexical/blob/6e65c989c0d379dccfe28078a76ef49e4dc66443/packages/lexical-playground/src/Editor.tsx#L217
reference to MaxLengthPlugin -
https://github.com/facebook/lexical/blob/6e65c989c0d379dccfe28078a76ef49e4dc66443/packages/lexical-playground/src/Editor.tsx#L120

Fixed in https://github.com/facebook/lexical/pull/3649


Night CI 2023-09-04: Failed

action url: https://github.com/spidernet-io/egressgateway/actions/runs/6066461661

same with #727


Adds support for looping

Hey, thanks so much for open sourcing this. I made terminal animations many different ways while working on Surge.sh, and this is easily one of the most elegant solutions I’ve seen (presumably why you also ended up writing your own!)
While my old approach is still in place there, I actually ended up needing this for something else too, and adding in looping options in the process. To try it out:
# Install my branch
npm install kennethormandy/react-keyframes#ko-looping

import { render } from 'react-dom';
import { Keyframes, Frame } from 'react-keyframes';

render(
  <Keyframes loop> // Just added `loop` to the main example
    <Frame duration={500}>This</Frame>
    <Frame duration={500}>This is</Frame>
    <Frame duration={500}>This is animated.</Frame>
  </Keyframes>,
  document.getElementById('container')
);

You can also pass loop a number:
<Keyframes loop={2}>
  <Frame duration={100}>:)</Frame>
  <Frame duration={100}>;)</Frame>
</Keyframes>

If it’s possible to do this with onEnd already, I didn’t figure out how that should work. I don’t think my tests are thorough enough, but it’s a start.

Amazing, thanks!!!
btw, it's possible to set a new value to key props, so animation restarts.
Anyway this would be great for convenience.

published as v0.2.0

Thanks for merging, and for writing the docs!


When I build /targets/zephyr , it shows stdio.h: No such file or dictionary

As title .

cc: @sergioamr

Let me have a look, i also have to do some work on the default settings for the new zephyr since it changed a bit the api.

Which version of the zephyr-sdk are you using? I cannot reproduce this issue.

@sergioamr 1.5.0

@iamblue 1.5.0 is not the sdk. That is the Zephyr RTOS version.
If you are missing the stdio is probably because you don't have the SDK installed.
https://www.zephyrproject.org/doc/1.5.0/getting_started/getting_started.html
You have to follow the Development Environment Setup to install the SDK and the the toolchain.
This is where the SDK lives:
https://nexus.zephyrproject.org/content/repositories/releases/org/zephyrproject/zephyr-sdk/
You should have one of the latest ones. 0.8.2 for example in linux.
You can have more information about how to build zephyr here:
https://www.zephyrproject.org/

@LaszloLango This seems a problem of not having the toolchain installed.
Could we close this issue?

@sergioamr, sure. Thanks for your help.
@iamblue, feel free to reopen the issue, if you still have this problem.

@sergioamr  , I check my SDK version is 0.7.2 . I will try 0.8.2 version . Thx for your help~

@iamblue If you still have issues, please feel free to contact me on my email, or join the Freenode IRC chats.
We have a #jerryscript channel there and i am normally available for chat and help during working hours (UK time).

@iamblue
You can also try our recently released zephyr.js integration that gives support to different GPIOs, sensors, etc and helps your get the maximum of your Zephyr with JavaScript. And it is a very useful project to build upon.
https://github.com/01org/zephyr.js

@sergioamr  zephyr.js is awesome project!
My company has some IoT platform (ex 7687 (wifi + CM4) , 7697 (wifi + BT + CM4) ). I will porting Zephyr OS and zephyr.js to our platform.


Hide Vaccination "Valid to" from main screen of vaccination certificate and explain what it means in the details

Current Implementation
In contrast to CovPass, the CWA prominently shows the validity of the digital signature of the vaccination certificate

As most users of the CWA are not technicians, there is a potential of confusion between "Until when is my vaccination protecting me" and "technical validity of the signature".
Suggested Enhancement
At the location shown in the screenshot above, no "Valid to" shall be shown.
In the detail data of the vaccination (when you tap the "Vaccination x of y" field), the signature validity may be shown, but with an explanation text what it means (that this date has no medical meaning).
Expected Benefits
Avoid people deducing wrong conclusions ("Ah, I need a new vaccination after that date").
In the screenshot above, the fact that both dates are fully unrelated is already hinted by the fact that my vaccination was in a different month from the date when the certificate was technically created.

Hey @jkrwdf
Could you take a look at https://github.com/corona-warn-app/cwa-documentation/issues/645, please? I think this issue basically asks for the same, to clarify what the "valid to" means.
Thanks.

Hi @Ein-Tim ,
absolutely. Thanks for the hint.
Closing.


[FEATURE REQ] AppConfiguration ConfigurationClient is missing CreateIfNotExists API

Library or service name.
AppConfig
Is your feature request related to a problem? Please describe.
Scenario: I want an API that will only create a setting and set its value if it doesn't already exist.  If the setting exists, then the API does nothing. It does not update the value.

Add fails if it already exists
Get fails if it doesn’t exists
Set will overwrite the value if it exists

I ultimately put the “Add” call in a Try/Catch block to get this behavior.
Someone on the Python team mentioned that the Python Add method acts like CreateIfNotExists, meaning it won't throw exception if the item already exists.
azsdke2e

We did talk about having that behavior when we designed it and if I remember correctly, we went with the current design because it matches what a Dictionary type does in .NET, which is to throw if you try to add an existing key.

Sure, but I think we can support this scenario with a CreateIfNotExists method.

Following the logic of using Dictionary semantics, Dictionary has the ability to test if a key exists with ContainsKey.
My only way to get this behavior is with a try/catch block, which indicates a missing feature in the lib.
The other libs have CreateIfNotExists, i.e.
// App Config
            ConfigurationClient = new ConfigurationClient(new Uri(Env.GetString("AZURE_APP_CONFIG_ENDPOINT")), credential);

            // Blob
            BlobServiceClient = new BlobServiceClient(new Uri(Env.GetString("AZURE_STORAGE_BLOB_ENDPOINT")), credential);
            ContainerClient = BlobServiceClient.GetBlobContainerClient(Env.GetString("AZURE_STORAGE_BLOB_CONTAINER_NAME"));
            await ContainerClient.CreateIfNotExistsAsync(PublicAccessType.BlobContainer);

            // Queue
            QueueServiceClient = new QueueServiceClient(new Uri(Env.GetString("AZURE_STORAGE_QUEUE_ENDPOINT")), credential);
            QueueClient = QueueServiceClient.GetQueueClient(Env.GetString("AZURE_STORAGE_QUEUE_NAME"));
            await QueueClient.CreateIfNotExistsAsync();

            // Client Sync Queue
            ClientSyncQueueClient = QueueServiceClient.GetQueueClient(Env.GetString("AZURE_STORAGE_CLIENT_SYNC_QUEUE_NAME"));
            await ClientSyncQueueClient.CreateIfNotExistsAsync();

But for AppConfig I have to special case it and use a try/catch to get the behavior I want.  I would like the API surface to be consistent across the libs.

We should add this to the list of APIs that should not throw. /cc @annelo-msft

This is tracked under #25626 and will take a different form than discussed in this issue.   Closing this out.


Home page P1 edits

[x] Our Work: Please enable configurability of 'Learn More' buttons text in cards
[x]  Headers of all sections to be made configurable
[x]  Our Model: Please make the icons configurable
[x]  LinkedIn button: Please enable option to show/hide the text + button

Have merged all the four changes mentioned above, so closing the PR


Add /version endpoint

This endpoint should output some server side version information about the system. The data should be output in JSON. This information can be used to determine API compatibility with the CLI and other interfaces.

Do you have a specific set of information that would need to be displayed other than a version number?
I see some info in gateway, should some of these be displayed?

Hey there! I just put up a more centralized server handler that can be used to pass to make some of this easier:

On the NodeJS side of the world, we could set an arbitrary JSON block in package.json and read it from main.js. It would require some CI work, but nothing too complicated. Definitely willing to help on the Node side if needed.

I've updated the nodejs release process to add a meta object to the package.json file. Rendering an endpoint for NodeJS should be as easy as reading that file and writing out the meta block in json.

Hi, thanks a lot for clarifying and making things easier. I'll get started on this right away!

From what I understand from the Makefile. During the build (specfically install command) of each golang service, the variables are set (if the service has those variables).
gateway and tracker both use /internal/mux, so for them I have set variables version, commit, date. which are set by the goreleaser tool and used a Version struct to pass this info to internal/mux as part of the Config. but indexer and deps currently do not use /internal/mux. So no changes are required to deps and indexer?

Correct. Although, all of them should have a version subcommand for printing information (kinda like how deps works)


Ignore extra fields in ORM (fixes #190, option 1)

I'm not sure there's a valid use case for the ORM to fail when it gets a field it doesn't recognize. If someone has a use case in mind, we can always make this a configuration flag on Meta later, but I think it should be permissive by default.

Codecov Report

Merging #250 (997d876) into main (18903eb) will increase coverage by 0.48%.
The diff coverage is 100.00%.

:exclamation: Current head 997d876 differs from pull request most recent head 466e389. Consider uploading reports for the commit 466e389 to get more accurate results

@@            Coverage Diff             @@
##             main     #250      +/-   ##
==========================================
+ Coverage   87.50%   87.98%   +0.48%
==========================================
  Files          14       15       +1
  Lines         640      649       +9
==========================================
+ Hits          560      571      +11
+ Misses         80       78       -2

Impacted Files
Coverage Δ

pyairtable/orm/model.py
86.79% <100.00%> (+1.47%)
:arrow_up:

pyairtable/testing.py
100.00% <100.00%> (ø)


Close stream when module is hidden.

Hi again!
Because I'm using now 6 camera streams to my mirror (showing only when there is movements) there are lot's of bandwidth being wasted when the module is hidden. Would there be possible to "stop" the stream when the module gets hidden?
Thank you! :)

I believe this is fixed. :)


represent() uses base normalization by default which is almost always wrong

Before You Report a Bug, Please Confirm You Have Done The Following...

[X] I have updated to the latest version of the packages.
[X] I have searched for both existing issues and closed issues and found none that matched my issue.

DeepFace's version
0.0.94
Python version
3.10
Operating System
No response
Dependencies
n/a
Reproducible example
embedding_objs = DeepFace.represent(
  img_path = "img.jpg"
)

Relevant Log Output
No response
Expected Result
represent should default to appropriate normalization for the model in use
What happened instead?
represent uses "base" normalization by default which is image with its components divided by 255
instead it should default to the normalization required by the model in use
Additional Info
No response

Just to make sure I understand correctly: it is your position that using VGGFace normalization with VGGFace model is the wrong default?

if you use vggface normalization, then you will get lower results.

That is not what I observe.

then, you are free to use that normalization.


How to build

Hi,
can you please provide instructions for building it ourselves? I'm not familiar with this node thingy, but want to try this on Arch (so DEB and RPM is not ideal). Thanks!

hey @TamasBarta, sure, I'll write instructions in README.md to help contributors. I hope it will be useful for you as well.
Thanks a lot for your interest! Arch's  PKGBUILD will be super useful .


fix: Specify AWS_REGION to support cert-manager GovCloud.

This should be specified on the certificate issuer, but it didn't seem to take effect. Maybe we didn't test correctly and it would work with a clean test, but we don't actually know how to perform a clean test.

@josmo I need help diagnosing why commit signing isn't working.

Never mind. Sorted.


creating circle-progessBar-pag #5

Add description to the PR body.
Don't leave more than 1 empty in between the code blocks.


[Monitor] Fix duplicate attribute

Resolves https://github.com/Azure/azure-sdk-for-net/issues/38994
We have this attribute in core so just switching over to use to the version we have.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@rajkumar-rangaraj FYI

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


Enable NGINX Ingress Controller with TLS

I believe that the setup of the csi is not correct for the tutorial since it uses secrets but doesn't enable the secret syncing feature.
The correct install with helm would be the following:
helm install csi csi-secrets-store-provider-azure/csi-secrets-store-provider-azure --set secrets-store-csi-driver.syncSecret.enabled=true

I can create a pull request if this is correct

Hi @DavidMarquezF Thanks for reporting this. Your observation is right. We recently disabled synching secrets by default.
PR is always welcome 👍🏻


Missing "Solo" & "Soloend"?

Hey there, I was just wondering how I can add solo markers in Moonscraper. No matter which version of Moonscraper I download, I do not have the solo and soloend markers. When I type them in manually, they still don't work when playing my chart in Clone Hero. Please help? Thank you :)

These should already be implemented as part of the local events (red flag) tool. If these aren't present then you'll either need to do a complete uninstall and reinstall or edit your "local_events.txt" file located in the "Config" folder where you've installed MS to. These config files are not automatically updated between updates to prevent user specific configurations from being stomped, so it's possible you've upgraded from a version where the events didn't exist to one where they did and thus you didn't get the new event.


SIFT Installer error: unable to validate hashes for sift-saltstack | On Ubuntu server 20.04 and v2021.9.0

I have a basic installation of Ubuntu Server 20.04.3. I am following the instructions from Option 2A: SIFT Easy Installation on Native Ubuntu System
When I run sudo sift install --mode=server , I get the error below.
Does SIFT expect Ubuntu Desktop? Or am I running into some other (unexpected) issue?
==============
t805959@tsirtforensicswest:/var/tmp$ sudo sift install --mode=server

<EMAIL_ADDRESS>sift-version: notinstalled

mode: server
downloading v2021.9.0

downloading sift-saltstack-v2021.9.0.tar.gz.asc
downloading sift-saltstack-v2021.9.0.tar.gz.sha256
downloading sift-saltstack-v2021.9.0.tar.gz.sha256.asc
downloading sift-saltstack-v2021.9.0.tar.gz
validating file sift-saltstack-v2021.9.0.tar.gz

Hashes for sift-saltstack-v2021.9.0.tar.gz do not match. Expected: , Actual: bbb6b86d4269a9b6797496345b8f7cc852763ba2df1047b6a017e2abcc1c4606  /tmp/sift-saltstack-v2021.9.0.tar.gz
Error: Hashes for sift-saltstack-v2021.9.0.tar.gz do not match. Expected: , Actual: bbb6b86d4269a9b6797496345b8f7cc852763ba2df1047b6a017e2abcc1c4606  /tmp/sift-saltstack-v2021.9.0.tar.gz
at validateFile (/snapshot/sift-cli/sift-cli.js:401:11)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async downloadUpdate (/snapshot/sift-cli/sift-cli.js:468:3)
at async run (/snapshot/sift-cli/sift-cli.js:758:5)
at async main (/snapshot/sift-cli/sift-cli.js:781:5)

----- PLEASE READ ----------------------
A lot of failures are caused by the apt system being locked
or unhealthy.
Before opening an issue in GitHub, please check to see if
your apt system is healthy.
Try running 'apt-get update' then remove any packages that
aren't used by running 'apt-get autoremove'

Hi @AgnosticCrusader , it looks like there may not have been a download of the actual release file. This could happen if there was a network connectivity problem, or perhaps you might be behind a proxy. Could this be the case?

Hi @AgnosticCrusader , it looks like there may not have been a download of the actual release file. This could happen if there was a network connectivity problem, or perhaps you might be behind a proxy. Could this be the case?

I noticed that. I am indeed behind a proxy, but /etc/environment is correctly set:
http_proxy="http://###.###.##.25:8080/"
https_proxy="http://###.###.##.25:8080/"
HTTP_PROXY="http://###.###.##.25:8080/"
HTTPS_PROXY="http://###.###.##.25:8080/"
Having said that, some tools have their own config file for proxy declaration - they may not pick up on proxies defined in the environment variables. Is that the case here? Is there a magic config file where I need to declare my proxy?

Make sure those environment variables are in your current shell and you should be ok.

@AgnosticCrusader following up here.

None of the suggestions above worked. It looks like Saltstack has some issues with certain proxy types. I ended up deploying the SIFT appliance. I then tried to install REMnux on top of the SIFT appliance and ran into the same Saltstack issues.  Here is how I resolved those issues :
wget https://repo.saltproject.io/py3/ubuntu/20.04/amd64/latest/salt-archive-keyring.gpg
sudo mv salt-archive-keyring.gpg /usr/share/keyrings/
echo "deb [signed-by=/usr/share/keyrings/salt-archive-keyring.gpg arch=amd64] https://repo.saltproject.io/py3/ubuntu/20.04/amd64/latest focal main" | sudo tee /etc/apt/sources.list.d/salt.list
sudo apt-get update
sudo apt-get install salt-minion
sudo service salt-minion stop
sudo vi /etc/salt/minion
proxy_host:
proxy_port:
sudo apt-get install python3-tornado4
sudo apt-get install python3-pycurl
===
After that, Saltstack works fine through the proxy and I could install REMnux
===
sudo git clone https://github.com/REMnux/salt-states.git /srv/salt
clear;sudo salt-call -l info --local state.sls remnux.addon
===
My workaround also works with a semi-manual installation of SIFT on a clean Ubuntu behind my troublesome proxy.

You can just install salt-common via apt-get to get the salt-call command.
Nice note on the proxy_host and proxy_port variables, I can incorporate that into the updated CLI I'm working on.

Closed the issue since you have a work around for your proxy problems.


Fix Typo

https://github.com/GoogleCloudPlatform/forseti-security/blob/2.0-dev/rules/audit_logging_rules.yaml

Fixed Typo "exmption" to "exemption"