[1] Added script to make it easier to update secrets

What this PR does / why we need it:
I had this scrip laying around so I thought I would add it here.
Makes it easier to generate secrets for a new deployment (Or to update existing ones)
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

Maybe we could name the script generate-passwords, "generate-secrets", or similar?
I kind of got the association with update-passwords that it would update passwords that are already deloyed :)


worker_1  | 2021-01-06T17:15:20.940Z pid=1 tid=gnfn59299 WARN: {"context":"Job raised exception","job":{"retry":true,"queue":"default","class":"ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper","wrapped":"RunnerJob","args":[{"job_class":"RunnerJob","job_id":"f9cc5fca-775b-468e-8d28-645896b08009","provider_job_id":null,"queue_name":"default","priority":null,"arguments":[],"executions":0,"exception_executions":{},"locale":"en","timezone":"UTC","enqueued_at":"2021-01-06T17:15:11Z"}],"jid":"09a4194258480d49751e7fc2","created_at":1609953311.2627673,"enqueued_at":1609953311.2628284},"jobstr":"{\"retry\":true,\"queue\":\"default\",\"class\":\"ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper\",\"wrapped\":\"RunnerJob\",\"args\":[{\"job_class\":\"RunnerJob\",\"job_id\":\"f9cc5fca-775b-468e-8d28-645896b08009\",\"provider_job_id\":null,\"queue_name\":\"default\",\"priority\":null,\"arguments\":[],\"executions\":0,\"exception_executions\":{},\"locale\":\"en\",\"timezone\":\"UTC\",\"enqueued_at\":\"2021-01-06T17:15:11Z\"}],\"jid\":\"09a4194258480d49751e7fc2\",\"created_at\":1609953311.2627673,\"enqueued_at\":1609953311.2628284}"}
worker_1  | 2021-01-06T17:15:20.940Z pid=1 tid=gnfn59299 WARN: NameError: uninitialized constant AWSLoader::EMR
worker_1  | 2021-01-06T17:15:20.941Z pid=1 tid=gnfn59299 WARN: /app/app/jobs/lib/loader/asset/loaders/aws_loader/_resource_loader.rb:21:in `const_get'
worker_1  | /app/app/jobs/lib/loader/asset/loaders/aws_loader/_resource_loader.rb:21:in `load'
worker_1  | /app/app/jobs/lib/loader/asset/loaders/aws_loader/_resource_loader.rb:8:in `initialize'
worker_1  | /app/app/jobs/lib/loader/asset/asset_router.rb:49:in `new'
worker_1  | /app/app/jobs/lib/loader/asset/asset_router.rb:49:in `aws_load'
worker_1  | /app/app/jobs/lib/loader/asset/asset_router.rb:29:in `route'
worker_1  | /app/app/jobs/lib/loader/asset/asset_router.rb:24:in `initialize'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:49:in `new'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:49:in `block (3 levels) in loop_over_asset_lines'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:509:in `call_with_index'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:477:in `process_incoming_jobs'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:459:in `block in worker'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:450:in `fork'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:450:in `worker'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:441:in `block in create_workers'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:440:in `each'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:440:in `each_with_index'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:440:in `create_workers'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:380:in `work_in_processes'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:283:in `map'
worker_1  | /gems/gems/parallel-1.20.1/lib/parallel.rb:232:in `each'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:46:in `block (2 levels) in loop_over_asset_lines'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:45:in `each_slice'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:45:in `block in loop_over_asset_lines'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:44:in `open'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:44:in `loop_over_asset_lines'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:35:in `block in loop_over_files'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:34:in `each'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:34:in `loop_over_files'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:27:in `load'
worker_1  | /app/app/jobs/lib/loader/file_loader.rb:23:in `initialize'
worker_1  | /app/app/jobs/lib/batch_importer.rb:26:in `new'
worker_1  | /app/app/jobs/lib/batch_importer.rb:26:in `import'
worker_1  | /app/app/jobs/loader_job.rb:25:in `perform'
worker_1  | /app/app/jobs/runner_job.rb:32:in `perform'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:40:in `block in perform_now'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:112:in `block in run_callbacks'
worker_1  | /gems/gems/i18n-1.8.7/lib/i18n.rb:313:in `with_locale'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/translation.rb:9:in `block (2 levels) in <module:Translation>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `instance_exec'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/time/zones.rb:66:in `use_zone'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/timezones.rb:9:in `block (2 levels) in <module:Timezones>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `instance_exec'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:25:in `block (4 levels) in <module:Logging>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:180:in `block in instrument'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:180:in `instrument'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:24:in `block (3 levels) in <module:Logging>'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:45:in `block in tag_logger'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:80:in `block in tagged'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:28:in `tagged'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:80:in `tagged'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:45:in `tag_logger'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:21:in `block (2 levels) in <module:Logging>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `instance_exec'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:139:in `run_callbacks'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:39:in `perform_now'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:25:in `block in execute'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:112:in `block in run_callbacks'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/railtie.rb:43:in `block (4 levels) in <class:Railtie>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:88:in `wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:72:in `block in wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:84:in `wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:71:in `wrap'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/railtie.rb:42:in `block (3 levels) in <class:Railtie>'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `instance_exec'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:139:in `run_callbacks'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:23:in `execute'
worker_1  | /gems/gems/activejob-<IP_ADDRESS>/lib/active_job/queue_adapters/sidekiq_adapter.rb:42:in `perform'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:196:in `execute_job'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:164:in `block (2 levels) in process'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/middleware/chain.rb:133:in `invoke'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:163:in `block in process'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/job_retry.rb:111:in `local'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/rails.rb:14:in `block in call'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:88:in `wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:72:in `block in wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:88:in `wrap'
worker_1  | /gems/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:71:in `wrap'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/rails.rb:13:in `call'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:257:in `stats'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/job_logger.rb:13:in `call'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/job_retry.rb:78:in `global'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:124:in `block in dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/logger.rb:10:in `with'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/job_logger.rb:33:in `prepare'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:123:in `dispatch'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:162:in `process'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:78:in `process_one'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/processor.rb:68:in `run'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/util.rb:15:in `watchdog'
worker_1  | /gems/gems/sidekiq-6.1.2/lib/sidekiq/util.rb:24:in `block in safe_thread'
worker_1  | 2021-01-06T17:15:46.677Z pid=1 tid=ouhq6p8q9 class=RunnerJob jid=09a4194258480d49751e7fc2 INFO: start

sed '/Transfer/d' output.json.bak  | sed '/EMR/d' | sed '/ServiceQuotas/d' | sed '/XRay/d' > output.json

👌

sed '/Transfer/d' output.json.bak  | sed '/EMR/d' | sed '/ServiceQuotas/d' | sed '/XRay/d' > output.json

👌

@Techbrunch we've recently added loaders for all of the missing services above. I'm going to close this for now, but go ahead and re-open if you're still having issues.


css file

@.***
On Mon, 9 Jan 2023 at 13:26, Vaibhav Jain @.***> wrote:

Merged #1 https://github.com/Aditya10CR7/Hotel/pull/1 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/Aditya10CR7/Hotel/pull/1#event-8179054886, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVMUN3JRHMQF2OV42CVSUK3WRPADPANCNFSM6AAAAAATVD2ZJA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Stopped VM with local storage and data disk created/attached fails if created on a different host

This is where all disks are local storage. Create a VM with root disk on host A, stop the VM and create a disk and attach it to the VM and chances are sometimes it gets created on host B (local storage); however on attach it fails with error as data disk is on local storage of host B.
ISSUE TYPE

Bug Report

COMPONENT NAME

Local storage, VM/volume

CLOUDSTACK VERSION

4.18

CONFIGURATION

Adv zone

@rohityadavcloud
what's the hypervisor and OS ?

Fixed in https://github.com/apache/cloudstack/pull/7886


Create a new cart when the cart->order is placed and add tests for To…

Hi @theimerj,
With this adjustment I am adding support for creating a new cart when the current cart->order is placed.
And I have added a fix for #59

@tdwesten thank you very much!


[PackageLoading] Diagnose bad executable products

rdar://problem/42138100 Incorrect product reference in Package.swift caused failed build on linux, succeeded on macOS

@swift-ci please smoke test


Cherrypick #298 to release-1.4

(cherry picked from commit aa49f10779c3c774770bbe71b10616adabec39c1)

/lgtm
/approve


[Feture Request] data serialization, contract origination, contract invoke

Supporting contract origination and invoke is very necessary. And I think there are some utils method at this repo but they are not exported. Such as base58 encode and decode, pack bigNum to string. For convenience, these method should be exported. And in conseilJS, there are many methods to support serialize various data to byte array, and these methods are very useful and helpful. So I wish go-tezos could provide the same feature as conseilJS.
Thanks!

Bear with me, contract interaction is on the roadmap for Q2-Q3. I'm going to have to unfortunately disagree on exporting the crypto functions. It's not idiomatic go to expose functions that aren't strictly related to the library. I would consider moving the crypto library into it's own repository with it's own version.


Breaks for some icons.

Some icons such as the ones below don't display correctly.
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/account_circle.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/content_copy.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/history.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/settings.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/google_color.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/location_on.icon
https://chromium.googlesource.com/chromium/src/+/main/components/vector_icons/passkey.icon

I managed to fix this and opened pull request #2  to get it integrated basically the methods QUADRATIC_TO, R_QUADRATIC_TO, QUADRATIC_TO_SHORTHAND were missing/unimplemented and it looks like most round icons were using these methods.

@dragonloverlord Thanks! Merged the request.
Curious, how did you find out about this extension, and what do you use it for. Are you a chromium dev?

Not a Chromium dev but I have help with Chrome OS patches a few years back in a unofficial context. I also make chrome extensions for private use on a case by case basis for individuals with specific usage needs so I have a good bit of familiarity with chrome extension and there inner workings. As for this extension I found it on the thorium wiki and thought it was a rather interesting way to render text based image formats via SVG conversion which I have played around with before when making various mods for games like Starbound, Stardew Valley, and Skyrim to list a few. Personally I was more curious about the underlying technology in use by the extension than the extension its self but in the process of tinkering with it I managed to fix the bug in question and figured the least I could do was share my discovery.
I was actually just checking for updates on thorium when I ran across the extension so kind of luck really. Also I got to say thorium AVX2 is really useful for power users like me who could have multiple tabs open all well running a resource intensive process such as a game in 4K on the side so keep up the good work and glad I could help even if it was just a simple fix I stumbled across in this extension.

 I'm not sure how I initially found this extension but I was looking for some way to convert the icons to an SVG for one of my projects. I can't exactly remember what project it was for but it was either to make an operating system in the browser styled like Chrome OS or for a Chrome styled web proxy. Neither of those really went anywhere but I have since been working on a similar project meant to look like Firefox (cohenerickson/Velocity).


Address minor comments on #626

#626 was merged in with a few outstanding comments, here and here. This issue is a placeholder to track that work.

Not sure why i'm not able to assign this to you, so tagging you instead, @slaloggia.

I think I have to have interacted with the issue before you can assign, so try now!
I have an interview this afternoon that I'm preparing for, but will start working on these tomorrow.

I think I have to have interacted with the issue before you can assign, so try now!

Working now. Also noticed you hadn't actually been added as a collaborator to the project! (Maybe that's why you were forking!?). I added you so you should see an invite in email. Of course feel free to keep using your fork if you prefer.

I have an interview this afternoon that I'm preparing for, but will start working on these tomorrow.

Good luck!!


fix: revert prod flag

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Re-enable superfluid asset proposal CLI cmds

Closes: #XXX
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #910 (b728669) into main (2cefa2d) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #910      +/-   ##
==========================================
- Coverage   20.33%   20.33%   -0.01%
==========================================
  Files         192      192
  Lines       24919    24921       +2
==========================================
  Hits         5067     5067
- Misses      18924    18926       +2
  Partials      928      928

Impacted Files
Coverage Δ

x/superfluid/client/cli/tx.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Corrects CVE-2023-20863 by forcing spring-expression version

Description
Corrects CVE-2023-20863 by forcing spring-expression up to a corrected version.
Check List

[ ] ~New functionality includes testing~
[ ] ~New functionality has been documented~
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@RyanL1997 and @DarshitChanpura would you mind reviewing this CVE bump when you get a chance?


[Bug]: Logwaiting strategy not working in Windows with Podman

Module
RabbitMQ
Testcontainers version
1.17.2
Using the latest Testcontainers version?

I am trying to use Podman (version 4.2)  instead of Docker to run the tests with Testcontainers.
I am trying to start the RabbitMQ containers with following code
static {
        rabbitMQContainer = new RabbitMQContainer("rabbitmq:3.10.6-management-alpine")
                .withStartupTimeout(Duration.of(100, SECONDS));
        rabbitMQContainer.start();

    }

Testcontainer is recognizing the Podman as docker environment but failing to recognize the container strartup based on the log messages.
org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*Server startup complete.*'
If I switch to HostPortWaitStrategy everything works fine.
.testcontainer.properties
docker.client.strategy=org.testcontainers.dockerclient.NpipeSocketClientProviderStrategy
DOCKER_HOST = npipe:////./pipe/podman-machine-default
Relevant log output
07:16:15.735 [docker-java-stream--2056062630] DEBUG com.github.dockerjava.zerodep.shaded.org.apache.hc.client5.http.wire - http-outgoing-0 << "{"cause":"using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported","message":"failed to obtain logs for Container '38555297088f5eb766b2c81e22637bb0b4581456b02422ee1cd59deb30674fdc': using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported","response":500}[\n]"

....
07:17:55.731 [main] DEBUG 🐳 [rabbitmq:3.10.6-management-alpine] - Wait strategy threw an exception
org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*Server startup complete.*'

Additional Information
No response

Thanks for raising this issue @sureshgadupu and providing the debug output that helps look into this. Looking at this response from the /containers/{id}/logs Docker API endpoint (which podman-service tries to provide, and which Testcontainers accesses using docker-java)
using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported","message":"failed to obtain logs for Container '38555297088f5eb766b2c81e22637bb0b4581456b02422ee1cd59deb30674fdc': using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported","response":500

, it seems the logging subsystem of your podman installation is not correctly set up. The Docker documentation explains the following constraints for usage of the logs API:

Note: This endpoint works only for containers with the json-file or journald logging driver.

I would suggest asking the podman community how to correctly configure the log driver to allow usage of /containers/{id}/logs, I don't think there is anything Testcontainers can do here and it expects to interact with a Docker-compatible API.

Thanks for providing the explanation @kiview .
I will check with Podman community

I was able to resolve the issue after watching the youtube video .
After setting events-backend to k8s-file in /usr/share/containers/container.conf file in virtual machine my tests are running fine.
If you are using Podman version 4.2, no need to change cgroup-manager option


fix(node/store): fix memory leak, reduce memory consumption and improve cache hit rate

TODO:

[ ] Split it out other miscellaneous PRs
[ ] Test sync on BN
[ ] Submit a minor bug fix to libp2p(peerstoreds cyclicBatch)

Codecov Report
Attention: 18 lines in your changes are missing coverage. Please review.

Comparison is base (dd3b8e1) 50.98% compared to head (d82de9c) 50.98%.

Files
Patch %
Lines

nodebuilder/store.go
85.71%
4 Missing and 2 partials :warning:

share/eds/inverted_index.go
53.84%
4 Missing and 2 partials :warning:

nodebuilder/header/config.go
62.50%
3 Missing :warning:

nodebuilder/settings.go
0.00%
2 Missing :warning:

nodebuilder/das/config.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2960      +/-   ##
==========================================
- Coverage   50.98%   50.98%   -0.01%
==========================================
  Files         168      168
  Lines       10937    10994      +57
==========================================
+ Hits         5576     5605      +29
- Misses       4865     4886      +21
- Partials      496      503       +7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I will be posting further findings on badger configuration here. For some unknown reason, compression brings lots of RAM overhead, but not for the compression process itself, but for the internal caching. I don't have any ideas why, but will try syncing again with a reduced cache side to confirm that overhead is coming from the cache. Potentially badger caches more things to avoid decompression.

Also, before merging, we should test if its breaking. My understanding that it's not, but we need to triple check


Summa Explorer problem report

A problem has been reported with the page located at: http://ift.tt/1k0TE1I

I don't see the problem here.


Modify interface for CSP options

Is your feature request related to a problem? Please describe.

Currently, the options to set up CSP headers in Nuxt Security are found in different places

in the headers: contentSecurityPolicy header, with optionally a 'nonce-{{nonce}}' placeholder
in the nonce: boolean option for SSR
in the ssg: hashScripts option for SSG

Our users can sometimes get confused on how to setup CSP properly, depending on whether they are trying to use CSP-strict mode and whether they are using SSR or SSG modes.
Describe the solution you'd like

1- eliminate the 'nonce-{{nonce}}' placeholder from headers
2- regroup CSP setup under a new option:
{ // Better naming possible...
  cspNonceOrHashes: {
    addToScriptSrc: boolean; // default true
    addToStyleSrc: boolean; // default false
  }
}

Rationale for the Proposal
1- On the suppression of the 'nonce-{{nonce}}' placeholder: this parameter can conflict with the current nonce option. If 'nonce-{{nonce}}' is used but nonce is set to false, it blocks the page. The opposite is also true. In addition, nonce: true is ignored with SSG. Finally, our users sometimes use 'nonce-{{nonce}}' on non-nonceable elements, leading to questions as to why the page blocks.
2- On the introduction of the cspNonceOrHashes option: this parameter makes it clear that we are dealing with both SSR and SSG at the same time. There is no more need to think about the differences between SSR (nonce option) and SSG (ssg option), Nuxt Security will use nonces for SSR and hashes for SSG automatically. In addition, it makes it clear where the nonce or hash will be included, and what sensible defaults should be used.
Implementation Guidelines
The implementation SHOULD follow the following logic:

if cspNonceorHashes.addToScriptSrc is true:

if rendering mode is SSR:

parse all inline scripts, add nonce attribute to HTML
parse all external scripts (including in links), add nonce attribute to HTML
add nonce to script-src policy

if rendering mode is SSG:

parse all inline scripts, hash content, add SHA to script-src policy
parse all external scripts (including in links), find integrity attribute, add SHA to script-src policy.
If 'strict-dynamic' is used and at least one external script does not have an integrity attribute, send a warning to the user that this script will be blocked because of 'strict-dynamic' (consider alternative:  disable 'strict-dynamic' and warn the user that we are removing the keyword)

else:

return

if cspNonceorHashes.addToStyleSrc is true:

if rendering mode is SSR:

parse all inline styles, add nonce attribute to HTML
parse all external styles (including in links), add nonce attribute to HTML
add nonce to style-src policy

if rendering mode is SSG:

parse all inline styles, hash content, add SHA to style-src policy
parse all external styles (including in links), find integrity attribute, add SHA to style-src policy

else:

return

The old ModuleOptions syntax MAY be marked as deprecated but SHOULD continue to be supported in future versions.
Describe alternatives you've considered

A first alternative would be to use a more generic term such as {{nonceOrHash}} placeholders in headers: contentSecurityPolicy. This would make it clear that the nonce or hash will be included in the corresponding section of the CSP header. It's a clean alternative, that eliminates the need for both the nonce option and the ssg option. However it does not prevent users from including this placeholder on non-nonceable elements, nor does it make clear that we can only process

Hey @vejja
Thanks for this extensive research and description! I really like the idea of making things simpler.
I am totally into getting rid of nonce in the headers if it is possible. This would make working with CSP and nonce much smoother.
However, for your proposed change about merging nonce and ssg options, I think this is not a good idea.
The module is aimed for SSR apps mainly (due to the usage of server middleware). What the user gets while using this module in SSG is the CSP delivered as http-equiv, remove console loggers, and some smaller utils. That is why, I think that additional configuration option for ssg is fine.
For the nonce however, it would be useful to have is as a part of security.headers.contentSecurityPolicy but the current interface (that is also generic for other headers) is that inside security.headers.contentSecurityPolicy you would just get the HTTP directives. And nonce is a special case of CSP that you may want to use but you dont have to. It is an additional layer of protection.
So in summary,

I think that getting rid of nonce placeholder in headers is a good idea (if we can deliver it to the users without requiring them to write additional code or refactor existing solution because of breaking changes)
I am against merging nonce and ssg. I think they are in the right places :)

Let me know what you think about it :)

Ok, it makes sense and agree it will work for our users.
The thing I'm trying to scratch my head around is the following

In SSR mode, setting script-src: 'self' 'unsafe-inline' 'strict-dynamic' and style-src 'self' https: 'unsafe-inline' should be the reasonable default. It will work in all cases and ensure a strict CSP.
In SSG mode, this will work also in the majority of cases, but it will break sites that include an external script (think Google Analytics, Bootstrap, etc.), if an integrity hash is not included on that external resource.

At the end of the day, we are constrained by how CSP works, and it should be the responsibility of the user to include integrity tags manually to comply with CSP if they want to enable CSP.
Maybe I can try to clarify this in the docs, WDYT?

I think the docs should do the trick. We don't have to deliver everything to the user. It would be awesome but as you know, security is not easy ;)
So giving users right tools is also a fine approach IMO. Let's give them tools and instructions on how they can solve their issues :)

Ok then I'll update the docs
Before that, can you confirm I understand correctly

We will keep the nonce-{{nonce}} placeholders. This is necessary to make sure that in SSR mode, the user can elect to disable nonces in either style-src or script-src, while keeping nonces in the other one. In SSG mode, these placeholders will be ignored.
We will keep the nonce option. This somewhat conflicts with the previous placeholders in SSR mode, but is nonetheless a handy switch to disable all nonces in one place. In SSG mode, this option will be ignored.
We will keep the ssg option, with sub-properties hashScripts and hashStyles. This is necessary to make sure that in SSG mode, the user can elect to disable hashes in either style-src or script-src, while keeping hashes in the other one. In SSR mode, this option will be ignored.

Can you also confirm that

In SSR mode, all external scripts and styles will have nonces, except if the nonce option is set to false. This is really where the nonce option will be useful :  if nonce is set to true, and there is no nonce-{{nonce}} placeholder, we will still insert the nonce for external resources
In SSG mode, all external scripts and styles will be looked up for integrity attributes, and the corresponding hashes will be inserted in script-src (if hashScripts is true) and style-src (if hashStyle is true)

In summary:
In SSR mode, nonce insertion is governed via placeholders for inline elements, and by nonce option for external elements
In SSG mode, hash insertion is governed via ssg option, both for inline and external elements

One wuick note here. Keep in mind that hashStyles have not yet been merged. The commit was but along with the one that reverted it. I mentioned it in the PR that for some reason GitHub decided to merge the PR with hashStyles.
Could you please create a new pr with this proposed change?

Yes, I think this approach should be safe. It could be better of course but this will lead to breaking changes that I wont to avoid now :)
Thanks for doing the summary!
Maybe we could add a note in the documentation about usage of the module in SSR vs SSG? With the summary of what user get by using certain approach
What do you think about it?

I am clarifying the docs section right now + adding a brand new section in 'Advanced' on CSP to cover edge cases
I will submit via PR but I think you will want to do some editing to ensure it looks good to you

Awesome, let me know once it is ready. I will do my best to help.
Thanks for everything. I really appreciate it!

🚀 PR #282
Will close this issue now


Add a warning if the target "element" can't be found in the original source code

With version 0.8.0, if the # Raincoat comment points to an invalid element, there is no warning nor output.
For instance, with the following code:
from django.conf import settings
from django.db.backends.oracle import base

class DatabaseOperations(base.DatabaseOperations):  # pylint: disable=abstract-method

    def _convert_field_to_tz(self, field_name, tzname):
        # Raincoat: pypi package: Django==1.8.4 path: django/db/backends/oracle/operations.py element: _convert_field_to_tz

Running raincoat leads to the following output:
% raincoat
Collecting Django==1.8.4
  Using cached [....]/Django-1.8.4-py2.py3-none-any.whl
  Saved /tmp/tmpzrv6fd7r/Django-1.8.4-py2.py3-none-any.whl
Successfully downloaded Django

When I fix this to element: DatabaseOperations._convert_field_to_tz, I receive the proper output:
% raincoat
Collecting Django==1.8.4
  Using cached https://.../Django-1.8.4-py2.py3-none-any.whl
  Saved /tmp/tmpxpg868d7/Django-1.8.4-py2.py3-none-any.whl
Successfully downloaded Django
Django == 1.8.4 vs 1.10.7 @ django/db/backends/oracle/operations.py:DatabaseOperations._convert_field_to_tz (from blusers/core/optiservice/oracle_optiservice/base.py:11)
Code is different:
--- django/db/backends/oracle/operations.py
+++ django/db/backends/oracle/operations.py
@@ -1,13 +1,14 @@
def _convert_field_to_tz(self, field_name, tzname):
-        if not self._tzname_re.match(tzname):
-            raise ValueError("Invalid time zone name: %s" % tzname)
-        # Convert from UTC to local time, returning TIMESTAMP WITH TIME ZONE.
-        result = "(FROM_TZ(%s, '0:00') AT TIME ZONE '%s')" % (field_name, tzname)
+        if settings.USE_TZ:
+            if not self._tzname_re.match(tzname):
+                raise ValueError("Invalid time zone name: %s" % tzname)
+            # Convert from UTC to local time, returning TIMESTAMP WITH TIME ZONE.
+            field_name = "(FROM_TZ(%s, '0:00') AT TIME ZONE '%s')" % (field_name, tzname)
# Extracting from a TIMESTAMP WITH TIME ZONE ignore the time zone.
# Convert to a DATETIME, which is called DATE by Oracle. There's no
# built-in function to do that; the easiest is to go through a string.
-        result = "TO_CHAR(%s, 'YYYY-MM-DD HH24:MI:SS')" % result
-        result = "TO_DATE(%s, 'YYYY-MM-DD HH24:MI:SS')" % result
+        field_name = "TO_CHAR(%s, 'YYYY-MM-DD HH24:MI:SS')" % field_name
+        field_name = "TO_DATE(%s, 'YYYY-MM-DD HH24:MI:SS')" % field_name
# Re-convert to a TIMESTAMP because EXTRACT only handles the date part
# on DATE values, even though they actually store the time part.
-        return "CAST(%s AS TIMESTAMP)" % result
+        return "CAST(%s AS TIMESTAMP)" % field_name

Hmm, that's an interesting one :) According to the code, an appropriate error should be displayed ! I'll add a test for that and fix it !
Thank you a lot for your report and I'm really glad to know there are people out there who use Raincoat !

The root cause was that Raincoat saw the object did not exist both in the old code and the new code, and said, because it was identical, it was not worth reporting. Fixing it :)

Fixed in 0.8.2, released on PyPI. Tell me if it works better for you !


Login - No possibility to highlight the entire entered code and delete it with the Delete key

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to URL https://staging.new.expensify.com/
In the email field, enter an email address
Press continue
Enter a few digits of the magic code, then try to highlight it, and delete it with the Enter key

Expected Result:
Digits can be selected altogether and deleted using the Delete key.
Digits can be deleted one at a time with the Delete key first to the end and the backspace key from the end to the beginning.
Actual Result:
It is not possible to highlight the entire entered code and delete it with the delete key, the digits are only deleted one by one with backspace from end to beginning and in no other way.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: New feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/235905889-f3f83fea-d2df-48fa-92ab-76a9ed86bef8.mp4
https://user-images.githubusercontent.com/93399543/235905907-87455897-086d-4e68-b60b-6203610607a6.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @conorpendergrast (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync


[Lesson 01] Excerise 3

Hi there,
I am trying to solve the 3rd exercise for lession 01 on  a Raspberry Pi 4B. So far I could manage
to adapt all the code for the 4 with the help of the hints in the issues. But I do not manage to
get all the cores running, just the processor 0.

I even built the other user solutions without any success.
UPDATE: With uart_2ndstage=1

What am I missing? Thanks for you help!

These documents led me to the solution:

These documents led me to the solution:

Found a solution.

Found a solution.


%w{...]...} is wrongly formatted to %w[...]...]

Ruby version: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
Rubyfmt git sha: 3f3653ccc6210a37eab2954ad534c901d63604a4

Input file
%w{...]...}

Rubyfmt's output
%w[...]...]

This breaks because
The delimiters of %w{} is changed to brackets, and the contents include a closed bracket which unintentionally terminates the %w literal. I have no good idea how to fix, though.

hi @penelopezone i'd like to look into this one if it's ok?


Profile morphology from ellipticities

Hi @SampsonML , @pmelchior ,
I think I found the issue with generating ProfileMorphology from ellipticities.
The coordinate transformation matrix
$ \dfrac{1}{\sqrt{1-g²}} \begin{pmatrix} 1+g_1 & g_2 \\ g_2 & 1-g_1 \end{pmatrix}$ (the covariance matrix is the inverse of this one),
is defined with respect to $g$ which is the reduced definition of the ellipticity. However, the input parameters of the profile are $e_1$ and $e_2$ which are the distortion definition (see here for definitions and how to convert one from the other).
I am fine working with $e_1$ and $e_2$ and this is what is computed using the moments in Melchior et al. (2010) eq. 2:
$\epsilon = [G_{20} - G_{02} + 2iG_{11}] / [G_{20} + G_{02}]$.
I am not familiar with the formula in #47 using an additional term in the denominator, and everything is consistent with the definition above.
Therefore, I think the moments method in measure.py is correct, we just need to make a conversion when using distortion ellipticities in morphology.py (hence this PR). For later, we may want to have the flexibility to take as input either distortion or reduced ellipticities, let me know if you want me to add these options.
Here is a notebook which compares the two definitions (for ellipticity computation) and where the profile is generated using the conversion from distortion to reduced ellipticities.

Nice,  from the notebook the size however is still overestimating by a bit bigger than a factor of root 2?

OK, great. So, the take-aways:

The elliptical profile definition is identical between ProfileMorphology and galsim's profiles. I might have looked at the galsim code when I created it years ago, not sure anymore..
Both use the simpler definition (which in Bartelmann & Schneider is called $\chi$ instead of $\epsilon$).
Both give moment sizes $T=47$ when we set it with a size of $\sigma=30$.

3 is a result of 1, but nonetheless weird. One culprit can be the factor $1/\sqrt{1-e^2}$, which both we and galsim use in the profile definition. I tried setting $e=0$ and got a factor of $\sqrt{2}$ up to uncertainties from the pixel sizes, so this is still wrong. I wonder if this definition is meant to preserve flux or surface brightness or something else. Can one of you dig through the galsim docs to see if they mention it anywhere.

OK, I found it. The correct form of the size given the flux-normalized 2nd moments of the profile is $det(Q)^{1/4}$, i.e.
(g[(0,2)] * g[(2,0)] - (g[(1,1)])**2)**(1/4)

Matt tried this earlier, but using only the exponent 1/2 instead of 1/4.


[#516] Add UTxO Generators to CHAIN State Machine Tests

The amount of tests run is quite low at the moment, because of the performance of the generators, but hopefully we'll see some improvements after input-output-hk/cardano-ledger-specs#518
Closes #516

Zen!

bors r+


Fix: ledger no request keys context

Building Leather at commit 8096b8a

Fixes #4682 and #4786 by using location state for chain name in ledger connect error, as it sometimes doesn't have access to LedgerRequestKeysContext
Fixes #4863, refactored a good chunk of code into useLedgerSignTx hook and TxSigningFlow provider.

Here's some testing of different scenarios:
https://github.com/leather-wallet/extension/assets/22010816/773cb55d-b17e-45b7-b981-5bb806917872

@314159265359879 , please, let me know if there are any other scenarios worth testing on this branch.

@314159265359879 , please, let me know if there are any other scenarios worth testing on this branch.

I believe you covered them, very nice!


tidb_query: fix cast string to real inconsistent with TiDB

Signed-off-by: Lonng<EMAIL_ADDRESS>
What have you changed?
Fix cast string to real inconsistent with TiDB, the former implementation does not handle the case in which the input parameter is binary string.
What is the type of the changes?

Bugfix (a change which fixes an issue)

How is the PR tested?

Unit test

/run-all-tests


Ensure we're compatible with node 12

The latest node LTS is 14, and we're still on 10. We should at least try to be compatible with 12...

Pull Request Test Coverage Report for Build 917

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 80.054%

Totals

Change from base Build 915:
0.04%

Covered Lines:
8408

Relevant Lines:
10104

💛  - Coveralls


Save wont overwrite opened files

if you have saved a file, when you have opened 2 opened files (same ones) then its saved on first file, but not in the second one

A better solution would be:

checking if this file is open. If it is, then just go to the tab with that file
Each time you focus on the tab, it is checking if the file was changed. If it was, then overwrite


tendermint::consensus::State serde impls

We serialize tendermint::consensus::State to JSON in TMKMS for double signing prevention.
It looks like the Serialize and Deserialize impls were removed recently. Can we get them back?

Sure!


CP HUD going higher than the max

I believe there is a console command that is causing a CP to get more health than it should. Investigate.

Fixed


[Refactor] Remove limitation of groovy script (#31500)(cherry-pick)

backport #31500

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


add interceptors grpc

closes #
I think it might be necessary to use grpc interceptors for the channel and I have created a method to be able to add interceptors. It could be used for example to create an interceptor to send traces with Opentelemetry.

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

This PR is out dated and the CLA haven't been signed since the beginning so closing this.


How can we obtain the tokenizer

Hi Thanks for sharing the code. I wonder how can we obtain the tokenizer. Is it also from GPT-2: https://huggingface.co/openai-community/gpt2/tree/main?
From https://github.com/yaochenzhu/LLM4Rec/blob/main/src/training.py#L145-L148, it looks for a file "vocab_file.json", but I couldn't find it in the GPT-2 repo. Also the tokenizer is sitting under a "tokenizer" folder, which seems not consistent with the one in GPT-2 repo.
Another question, what does "lambda_V" mean and how can I set it?
Thanks!

Hi Claire,
Thanks for reaching out!
I'm sorry for the confusion. vocab_file.json is just the vocab.json. I'll modify the codes to avoid the confusion.
In addition, for lambda_V, as you can find in our paper, we have two sets of token embeddings for user and items, i.e., collaborative embeddings encoding the interaction information and content embedding encoding the content information. lambda_V denotes the "coupleness" between the user/item collaborative and content embeddings. If lambda_V is large, then the couples is tight, where user/item collaborative/content token embeddings are constrained to be more similar (risking introducing unnecessary content information). If lambda_V is small, then the coupleness is loss, where we may risk introducing insufficient content information to support collaborative filtering. Empirically, we find in our paper that lambda_V = 1 serves as a good starting point.
Best,
Yaochen

Thanks for the quick reply.
One more question, should I run both training.py and finetuning.py as instructed in the run.sh script?

Yup. They correspond to the pretrain and finetune steps mentioned in the paper.


type->lqueries

Given a type for an XSD, generate lqueries to find all elements of that type. For help with numerous validations to come, and for future retrofitting of validations gone by.

Buildkite doesn't like > in branch names.


Storage Subsystem should take type system as optional

This way, one can verify the schema to apply before reading or writing. How it would work needs to be investigated.

Here is an ongoing PR.
https://github.com/nmondal/cowj/pull/100

This is done now!


React-Swipy on Mobile creates a vertical scroll on the whole page

Reopening #2 - Still can't figure out why react-swipy works fine on desktop, however on Mobile it will create an awkward vertical scroll on the page.
Examples (Open these on a mobile phone and on desktop to see issue replicated):

https://5x53pnrn3x.codesandbox.io/ (@goncy 's example implementation)
https://plug.af/75ca67 (my Implementation)

@goncy last mentioned "lock this behaviour disabling the overflows on the container or removing it's pointer events i guess" but I am unable to figure out how this helps

add overflow:hidden to the div with class card-container-god

@goncy I tried these changes and it didn't solve the issue. You can see that the issue persists even on the implementation you provided.
I plan to fork the repo to fix this issue, but I would love to have a brief chat with you when you are free to discuss if possible.
thank you!

This might be a reference to the issue at hand : https://stackoverflow.com/questions/16348031/disable-scrolling-when-touch-moving-certain-element


[New Rule] freedreno-builder

Library filename / 库文件名
libvulkan_freedreno.so
Library label / 库的文字标签
vulkan-freedreno
Library team / 库的开发团队
PojavLauncherTeam
Files & Comment / 同组文件 & 备注
No response
In Apps / 出现于
Fold Craft Launcher 1.1.0、PojavLauncher
Library icon / 库图标
No response
Library description / 库描述
A script for building turnip driver as a magisk module from mesa repository, scheduled releases per 2 week via github actions.
Library relative URL / 相关链接
https://github.com/PojavLauncherTeam/freedreno-builder

This code repository seems to only have script files, but not the source code for this native library


working tests inc, dec, shift, pop, push, prepend with ttl

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/7736/

Tests blue except known issue: https://github.com/arangodb/release-3.6/issues/15

@kvahed do we have the same PR for devel?


Trigger error from failing Collection.create with wait:true

This fixes #4262.
The bug arose because the transaction with the backend is mediated through model.save and the 'error' event is initially triggered by the model. Normally, the collection will forward all events from the model, but with wait: true, the model is not yet added to the collection when the event triggers, so the collection is not listening, either. I addressed this by special-casing the 'error' event in this particular scenario.
I determined that a similar fix is not required for the 'sync' event on successful create. In that case, the model is still added to the collection before the event triggers.
I foresee two possible criticisms on the solution:

One could argue that a similar fix is still needed for the 'request' event. However, since the timing of this event is fully predictable (i.e., just before the end of the call to create), users do not need to listen for it in order to match the timing of a callback. Adding special case code for the 'request' event as well would further inflate the code size.
It is theoretically possible that a user would call collection.create with a model that is already in the collection. In that case, with wait: true, I expect that the collection will forward the 'error' event twice. If this scenario is considered problematic enough, I am willing to address it.

On the other hand, someone might also argue that this issue does not need fixing at all. The old behavior, while surprising, could be argued to be consistent, since the collection cannot be expected to forward events from a model it does not yet contain.
Reviews and discussion welcome!
CC @paulfalgout @ogonkov @alanhamlett @recursivk

It is theoretically possible that a user would call collection.create with a model that is already in the collection. In that case, with wait: true, I expect that the collection will forward the 'error' event twice. If this scenario is considered problematic enough, I am willing to address it.

I think it's better to get an error message rendered twice rather than not at all.

Thanks, both!
I realized something after submitting the PR. Even in the old situation, create would return the new model so you could listen on that for the error event. It can even be a oneliner if you don't need a lasting handle to the model:
someCollection.create({...props}, {wait: true}).on('error', ...);

In other words, listening for the event is already possible, just not on the collection.
With that in mind, do you still consider the change worthwhile?

Also what about view.listenTo(collection, 'error', callback)? Does that already work or also not firing?

With that in mind, do you still consider the change worthwhile?

I think it's worthwhile to make sure the error event triggers as expected, because error cases are often not as tested as success cases so someone might not notice the error even never fires in their code.

Also what about view.listenTo(collection, 'error', callback)? Does that already work or also not firing?

Not firing. That depends on the collection forwarding the event again.

2. It is theoretically possible that a user would call collection.create with a model that is already in the collection. In that case, with wait: true, I expect that the collection will forward the 'error' event twice. If this scenario is considered problematic enough, I am willing to address it.

Imho, sending the error event twice should be considered a bug. If it's not that much of a hassle, I think I would opt to go the extra mile to make sure it only fires once.
If it turns out it will actually be a significat hassle to make sure it only fires once, perhaps that's a sign the status quo is actually more correct than the fix.
Rephrasing the question slightly, if I would have to choose which is less wrong:

A collection not forwarding an event for a model that technically isn't part of the collection yet anyway
A collection that broadcasts the same error twice

I'd say the first option 1 seems significantly less wrong to me.

I can see why you would be hesitant to introduce the this.has(model) check, especially if it becomes significantly slower the more models are in the collection... 🤔 Does the _.noop version negate the this.has(model) check?
If de-duplicating the event is going to be expensive no matter what, perhaps that's a sign that the status quo is a sensible default behavior. I think the argument could be made that having a collection forward events for a model it doesn't actually own is a nice-to-have rather than a must.
If it's an expensive nice-to-have, would it be so terrible to hide this type of event-forwarding behind a feature flag? The 'unexpectedness' of the default behavior could simply be documented.
For someone who are already being mindful about performance due to working with large datasets, this is probably just fine:
someCollection.create({...props}, {wait: true}).on('error', callback);

The view.listenTo(collection, 'error', callback) equivalent equally doesn't strike me as completely horrible for someone who's already being very particular for the sake of performance:
view.listenToOnce(someCollection.create({...props}, {wait: true}), 'error', callback);

I can see why you would be hesitant to introduce the this.has(model) check, especially if it becomes significantly slower the more models are in the collection... 🤔

This is not the case. has is implemented using get, which in turn uses the internal _byId hash table. There is no loop, although it might make a constant number of nested function calls:
https://github.com/jashkenas/backbone/blob/3b37e6aaccbdb8d661487b7cef63e8c930b6f182/backbone.js#L996-L1003

Does the _.noop version negate the this.has(model) check?

No. It only prevents worse bugs. It is cheap, though.

If de-duplicating the event is going to be expensive no matter what, perhaps that's a sign that the status quo is a sensible default behavior. I think the argument could be made that having a collection forward events for a model it doesn't actually own is a nice-to-have rather than a must.

Agreed.

If it's an expensive nice-to-have, would it be so terrible to hide this type of event-forwarding behind a feature flag? The 'unexpectedness' of the default behavior could simply be documented.

I'm open to either documenting the unexpected behavior or silently fixing it (like this PR attempts to do) (although it should be mentioned in the change log). In my opinion, adding features would be too much honor for a corner case like this.

The get code doesn't look that bad to me and people probably shouldn't be adding models in bulk this way anyways if they really care about speed? If you'd really like to silently fix this, I would vote to include the this.has(model) fix to avoid double events as well.
If you really don't want to add the this.has(model) check, I'd say double events mean you'd just be replacing one unexpected behavior with another arguably more obscure one. In that case documenting the current behavior would be the better alternative in my opinion.

I don't have a strong opinion on the this.has(model) check. In order to have one, I would need solid performance measurements, but getting those is a hassle. That would probably not be worth the time.
@alanhamlett have your thoughts on the matter evolved?

TBH the wait kind of makes it less likely that we can know at the point of adding the error if we should attach the listener.. ie: we might not know what the id is to check against until the server returns it.


I have a I/O error

Hello. I am adding a Gmail account to SMS Backup+ using the IMAP way. I meet a I/O error and cannot sync messages. What's I/O error and how to fix it?
The IMAP setting on Gmail is on. I see the app password of Google is in using. The IMAP address is imap.gmail.com:993. Everything looks good. What's the problem?

Thanks for the report.
"IO Error" simply means that the program received an unexpected response from Android when it asked to send or receive data, either from a local file or over the network.
"Unable to connect" and "end of stream reached" indicate that a network connection rather than a local file was a fault, but don't really help to narrow the problem down any further.
Does this happen every time, some of the time, or just once?
Was your WiFi working correctly at the time?
Does your device have a recent release of Android?

That definitely could cause those symptoms.
I'm afraid I'm not entirely sure how an in-phone VPN normally works.
Perhaps the VPN only diverts HTTPS & DNS traffic, which would miss the IMAP connections.
Is there anything in the configuration of the VPN about choosing "ports" or  "traffic types" or "protocols?

A properly-working VPN should not require any changes to client programs.
The majority of apps only need web access, if anything, but SMS Backup+ uses IMAP, which is a separate protocol, not part of HTTP or HTTPS.
So "only this one has an error" is not proof that it's at fault.
We also need to consider:

the VPN client may not be diverting email ports such as IMAP
the VPN client may be blocking email ports such as IMAP
the VPN server may be blocking email ports such as IMAP
the IMAP server (Gmail, if that's what you're using) may have blacklisted the exit address of your VPN provider

Although we are looking for "blocking IMAP", this might be phrased as "blocking TCP ports 143 and/or 993", or "blocking email", or "blocking everything except" (some list of other ports or services). Please confirm that you've checked what the "default settings" for your VPN actually provide, at this level of detail. If you find it difficult to confirm these, can you at least say which VPN client you're using (and its version)?
Have you confirmed that your VPN provider isn't blocking "email"? You might need to email them and ask them to unblock email. (Such blocking is commonly done to prevent blacklisting, since their customers' devices get compromised by spammers.)
Personally I would test end-to-end functionality by installing a telnet client and trying to connect to imap.gmail.com:143; if it fails to connect then at least the error message will be a little more informative.
Even the timing of the response will be informative: if it takes less than 0.01 seconds that indicates that the problem is almost certainly on your device; if it takes longer than 0.1 seconds, then it's being blocked out on the internet somewhere. (Visually that's the difference between "apparently simultaneous" and "the tiniest perceptible delay".)


Support for Views without Headers

Since there are no HeaderViews or FooterViews in RecyclerView, we should support views not having headers, so they can be used as header and footer views.
I think a decent approach will be to return a header id < 0 to indicate the view shouldn't have a header.

Hiding all headers with an id < 0 makes this harder to use for me. My headers are (more or less) arbitrary strings so I can't just go by the initial letter the header id must be based on the whole string for me.
header.hashCode() is a very convenient way of generating an id based on the whole string. However this returns negative values for many strings meaning I don't get any headers.

Feel free to submit a PR that overrides the default behavior.  Or use
Math.abs() :)
On Sun, Jan 11, 2015 at 4:02 PM, Niklas Barsk<EMAIL_ADDRESS>wrote:

Hiding all headers with an id < 0 makes this harder to use for me. My
headers are (more or less) arbitrary strings so I can't just go by the
initial letter the header id must be based on the whole string for me.
header.hashCode() is a very convenient way of generating an id based on
the whole string. However this returns negative values for many strings
meaning I don't get any headers.
—
Reply to this email directly or view it on GitHub
https://github.com/timehop/sticky-headers-recyclerview/issues/10#issuecomment-69513821
.

I ended up using Math.abs(), it doesn't feel right to mess with the return value of hashCode(), but I think it should be safe to do in my case.


[Feature requst] Allow snippets in code action edits

Currently, a language server can send text edits in code actions, but the edits cannot be interpreted as snippets. This is different in completion items, where the item can also be a snippet.
This is useful for example when the edited text still contains some holes that must be filled by a user to get a valid piece of code.

Dups https://github.com/microsoft/language-server-protocol/issues/592


Random events rewards recorded as kc

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10 x64
Bug description
Because the client uses regex to match game messages like "Your Corporeal Beast killcount is: 12" to record kc, it catches events such as "Your reward is: Coins x 120" that are commonly seen from random rewards (the mystery box from Quiz Master, for example). This leads to !kc reward reporting a "Reward kill count", that is of course a meaningless number because it's just the most recent reward you got.
Screenshots or videos

RuneLite version
RuneLite version: <IP_ADDRESS>
Launcher version: 2.4.2
Logs
No response

Funny timing, we found this via other channels and committed a fix for this mere hours ago. Fixed in 50af007e944570de1138ce99f52e16bd2d8faee2


Fixes #5838

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Approach

Commands to test

Screenshots

Learning

thank you so much, @cviorel !


Use new analyzer APIs.

It makes the example a bit slower, because we use API that is more general than the example needs. But I think that it might be OK for examples.

Hm... I cannot make checks of Travis work. It seem that sdk: '>=1.24.0 <2.0.0' is not compatible with SDK requirements for analyzer 0.32.0 that provides new APIs.
I don't know what are requirements for package:graphs, or why package:analyzer requires sdk: '>=2.0.0-dev.48.0 <2.0.0'. Please advise if we can raise minimal SDK version for package:graphs.
Alternatively we could make it stop using package:analyzer at all, and use instead less sophisticated  ways for searching imports, e.g. regular expressions.

Totally fine to stop testing stable on Travis


Inference Images should be different than training

The Learning Path points people to the same set of images for both Training the Custom Vision Service and using the app afterwards in production. This is incorrect, a different set of images must be used. Also the folder structure of the training set would overwrite half the images if used for inference because they have the same name. It also misses the 0.jpg described in the path. This is a set of creative commons use images to be referred to in the Unit 4. I will update the docs shortly to refer to it.

inference set.zip


PDF_417 format not being read on iOS

Issue
I'm using this plugin to read the barcode on US drivers' licenses and extract some information, for android it worked like a charm, the problem is when you try to use it on iOS, it doesn't read the barcode, seems like it doesn't recognize the format. According to PR-431 (https://github.com/phonegap/phonegap-plugin-barcodescanner/pull/431) this problem was resolved, still it doesn't work on iOS.
Platform and Version
iOS 10.3.1
Android 6.2.3
Cordova CLI version and cordova platform version
cordova --version 7.0.1
cordova platforms android 6.2.3 && ios 4.4.0

Plugin version
cordova plugin version 6.0.8

Sample Code that illustrates the problem
cordova.plugins.barcodeScanner.scan(
    scanSuccess,
    scanError,
    {
      formats: 'PDF_417,CODE_128'
    }
  );
}

function scanSuccess (result) {
    console.log(result.format, result.text);
}

According to the documentation, I don't think they support PDF_417 format on iOS yet. We could ask them if they plan to support it soon.

Please comment on #478 and give me an example image.

Despite the documentation , PDF_417 works fine on ios for me , but never did the same on android, I've tried with some phonegap-plugin-barcodescanner plugins's version like 6.0.6 and 7.1.0 , didn't works for me on android.

So frustrating, I can't find some post that really fix it.


Title and header links are horizontally unaligned

Before 2.0.0:

Alignment should be fixed now.


[Bug]: ts-protoc-gen package isn't generating a package_json.bzl even though it looks like it should

What happened?
While working on a patch file to get rules_proto_grpc to be compatible with rules_js, I was needing to change the rule for the ts-protoc-gen library (I am using ts-protoc-gen: 0.15.0).
It seems that rules_js registers that it is a binary. For example, the hasBin attribute in my pnpm-lock file is true. Likewise, I can see that the @npm external repository has the package ts-protoc-gen and that @npm//ts-protoc-gen/package_json.bzl does exist. The problem is that the non-syntactic-sugar ts-protoc-gen external repository (AKA @npm__ts-protoc-gen__0.15.0 does not generate it's own package_json file. So I can't get or execute the bin object.
If I try to load("@npm//:ts-protoc-gen/package_json.bzl", ts_bin = "bin"), it will complain with an error like the following
Skipping 'components/ui/proto:proto_grpc_web': error loading package 'components/ui/proto': at /root/.cache/bazel/_bazel_root/cbb1cba52c589b25ddeaba98ec308a80/external/rules_proto_grpc/js/defs.bzl:11:6: at /root/.cache/bazel/_bazel_root/cbb1cba52c589b25ddeaba98ec308a80/external/npm/ts-protoc-gen/package_json.bzl:1:6: cannot load '@npm__ts-protoc-gen__0.15.0//:package_json.bzl': no such file

Version
Development (host) and target OS/architectures:
I am running docker inside of windows. My host and target are the same.
Architecture: x86_64
Host OS: Windows 10
Docker OS: Ubuntu 20
Output of bazel --version:
Bazel 6.3.0
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
rules_js-1.31.0
rules_proto_grpc-4.4.0
Npm package - ts-protoc-gen: 0.15.0
Language(s) and/or frameworks involved:
rules_js
rules_proto_grpc (which in turn, needs uses the npm package ts-protoc-gen)
How to reproduce
I think a good starting point would be to include ts-protoc-gen in your package.json file. Run something like `link_all_node_modules`. Then check the external repository `npm__ts-protoc-gen__0.15.0` and the external repository `npm`.

If `npm` has a package_json.bzl file, but `npm__ts-protoc-gen__0.15.0` doesn't. Then you have reproduced my issue.

Any other information?
No response

I haven't been able to complete confirm it, because I'm fighting with getting the pnpm patching feature to work through bazel, but it seems more and more likely that the issue is because there is a windows .cmd file in the ts-protoc-gen bin directory

it's been hard to confirm this because it's been difficult to make a patch file that removes a .cmd file due to #1132

Thanks for the clue about .cmd in the package...


Fix Broken Link - UWP - Input Primer

Corrected Input Primer UWP - broken link
Old Link: https://msdn.microsoft.com/windows/uwp/input/input-primer
New Link (proposed): https://docs.microsoft.com/windows/uwp/design/input/input-primer

@TylerMSFT : PR passed review checklist. Please evaluate the proposed changes further. URL change looks good, but note that link text ("Input primer") no longer matches target topic title ("Interaction primer"); fix that with this PR?


Add branching commands

branch
checkout

git branch summed up in 230b6e7347ce0434f64af2300fb09988b2b4e955

@voloda can you check this if it's ok?

Overall looks good +1. Comments:

ls -l should be dir in checkout
Using notepad instead of echo might be easier
I think that next step should a lab where you will play with these
Also it might be easier to review on pull request :)

ls -l should be dir in checkout

I changed it into something that works under powershell

Using notepad instead of echo might be easier

tbh I don't see why.. why spawn notepad when the same thing can be accomplished with echo without leaving command line?

I think that next step should a lab where you will play with these

for playing you would need marge imho. so lab for playing with it maybe after all the core commands?

Also it might be easier to review on pull request :)

agree, trying that now


Download Notifications Language

When a download is started app uses the user's selected language without problems. But when the app gets restarted (gets killed) the app switches to English notifications regardless of the user's language choice.
Tested on both Android 11 A50 (physical) and Bluestacks emulator.
Screenshots:

what the notification is

what it should be in

What are the steps to reproduce this behaviour?
I tried:

killing the app from the device settings, but if you do so the OS will clear all the notification of the app
closing the app by going always back, but then the download will continue normally without change in language
terminating the app from the multitasking, the notification remains but without progress since it is terminated and on app restart you have to restart the download and it will be in the right language

killing the app from the device settings, but if you do so the OS will clear all the notification of the app

Start a download (Correct language)
Before download finishes kill the app from device settings (All notifications gets cleared)
Open the app and continue the download (Notifications are now in English)

Unfortunately I wasn't able to reproduce this behaviour, so I tried to fix this by forcing the language switch as the first instruction the app executes at startup, so now it should be more cosistent

It's working now!
closing this issue


Query bind params using operator format with MSSQL

What steps will reproduce the problem?
$count->where(['between', 'field', ':start',':end' ])
       ->addParams([':start' => $x, ':end' => $y]);

What is the expected result?
The query not to to fail
What do you get instead?
Invalid parameter number: parameter was not defined
BUT, if I change the clause to: where('field BETWEEN :start AND :end' )->addParams([':start' => $x, ':end' => $y]);
Query succeeds, is this expected behavior?
Additional info

Q
A

Yii version
2.0.10.?

PHP version
5.6

Operating system
Windows 7

No, it's not. What is the query generated by query builder in case of error?

SELECT * FROM (SELECT *, SUM(CASE WHEN type IS NULL THEN 1 ELSE 0 END) OVER (PARTITION BY id) AS sorter FROM "reg" ) t WHERE digit BETWEEN :startRange AND :endRange ORDER BY "sorter" DESC, "id", "type"

is the query if I don't use the operator format. When I change to operator format it returns:

SQLSTATE[HY093]: Invalid parameter number: parameter was not defined
Failed to prepare SQL

SELECT * FROM (SELECT *, SUM(CASE WHEN type IS NULL THEN 1 ELSE 0 END) OVER (PARTITION BY id) AS sorter FROM "reg" ) t WHERE [digit] BETWEEN :qp2 AND :qp3 ORDER BY [sorter] DESC, [id], [type]

OK. That's definitely a bug. If you want it fixed in 2.0.11 you may work on a pull request. Otherwise, will get back to in after 2.0.11 release.

Ok thanks, i'll have a look into it :+1:

['between', 'field', ':start',':end' ]

array syntax does automatic quoting so params will not work inside of the parameters unless you use Expression.


Update repositories.txt

First released

@suratin27 the problem reported by the bot still exists:

A problem was found with your submission https://github.com/suratin27/ESP32_Control_Lite
❌ ERROR: Unable to load submission URL. Is the repository public?

Please check the repository settings of https://github.com/suratin27/ESP32_Control_Lite to make sure that you have set the "repository visibility" setting to "public".
You can learn how to do that by following these instructions:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility#changing-a-repositorys-visibility

@ArduinoBot please check it again.


Azure Percept and View device stream in Azure

Hello all!
We've received our Azure Percept DK yesterday. What we are trying to do is, to just view the device stream and telemetry. We have sucessuflly conected the device to our internal WLAN network. After that we've created Azure IoT Hub and add new edge iot device. Everything looks OK, but we cannot click on "View stream" on Azure portal section, to see the actual video output from the device. Can someone please help us and tell where the problem is. The button is somehow "grayed out" / "without a link".
Screenshot: https://ibb.co/g4WBDFw
The device is showing with "Connected status" in the Azure Percept Studio.
Thank you for your helop!

Hello @nacestruc,
I'm glad you got an Azure Percept DK to try out. About the "view stream" issue, could you follow the instruction below to check and resolve the status of your azureyemodule?
https://docs.microsoft.com/en-us/azure/azure-percept/vision-solution-troubleshooting#check-the-runtime-status-of-azureeyemodule
Let me know how it goes. Thanks!

Hello @nkhuyent,
first of all, thank you for your response. In my Azure Portal control panel i don't have the following option. So based on the instructions on the webpage, i don't have the following option avaiable:
2. Select the Modules tab to see the runtime status of all installed modules.
3. If the runtime status of azureeyemodule isn't listed as running, select Set modules > azureeyemodule.
Please see the following screenshots:
https://ibb.co/K6sGsBY
https://ibb.co/kMtbGYY
So at the current state, we haven't resolve the issues with establishing connection to eyemodule.


Web - Can't react emoji in the thread message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any chat
Send new message
Go to thread of this message
Send a message in the thread
Hover on the parent message and click on any emoji

Expected Result:
User can react emoji in the thread message
Actual Result:
Can't react emoji in the thread message
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.41-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/ac9f0e64-1cdf-4932-83db-1cf54a019101
https://github.com/Expensify/App/assets/93399543/f6bffeb0-589f-4b04-b84c-2ac27c58f1d5
Expensify/Expensify Issue URL:
Issue reported by: requested
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689413343768979
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - Can't react emoji in the thread message
What is the root cause of that problem?
The issue is that ReportActionItem is always passing the reportID to toggleEmojiReaction as props.report.reportID, and the problem with that is when the message is being handled by ReportActionItemParentAction, the reportActionID that will be passed to ReportActionItem will be coming from parentReportAction which will not be matching within the allReportActions in ReportActionsUtils.getReportAction as the reportID will be the thread child while the reportActionID will be an ID that would be present inside the parent report.
https://github.com/Expensify/App/blob/b9508b616f3a7229365c8bd7280fd1e34cfd2f9b/src/pages/home/report/ReportActionItemParentAction.js#L64-L66
What changes do you think we should make in order to solve the problem?
We can start by passing isParentReportAction from ReportActionItemParentAction so that we have a way of knowing if the message is being passed a reportActionID coming from the report itself or it's parent.
After that, we can add a check and pass either props.report.reportID or props.report.parentReportID depending if isParentReportAction is true or not, we would need to do the check in showPopover, toggleReaction and when passing reportID to MiniReportActionContextMenu.
props.isParentReportAction? props.report.parentReportID.toString() : props.report.reportID

Result
https://github.com/Expensify/App/assets/74202751/4d8100c5-0d32-4610-881d-d1bd76116df1


HDFS-17024. Potential data race introduced by HDFS-15865

Description of PR
This PR fixes HDFS-17024.
How was this patch tested?
I cannot test against this issue due to the nature of the data race. This is the reason why I did not include the new test. Also, I ran mvn clean install -Pdist -Dtar -Ptest-patch. However, it seems that some tests fail even without this patch in my environment.
Additional notes
There is another WiP patch to fix HDFS-17024. However, it seems to be abandoned.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
13m 11s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m 27s

trunk passed

+1 :green_heart:
compile
1m  3s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 57s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 37s

trunk passed

+1 :green_heart:
mvnsite
1m  3s

trunk passed

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 46s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 35s

trunk passed

+1 :green_heart:
shadedclient
35m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
0m 54s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 54s

the patch passed

+1 :green_heart:
compile
0m 47s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 23s

the patch passed

+1 :green_heart:
mvnsite
0m 50s

the patch passed

+1 :green_heart:
javadoc
0m 35s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 35s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 33s

the patch passed

+1 :green_heart:
shadedclient
35m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 24s

hadoop-hdfs-client in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

152m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6223/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6223

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 412a1778b200 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 75244661d0ff418daaa1ac5cce401e5913a08c86

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6223/1/testReport/

Max. process+thread count
559 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6223/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@jojochuang Could you take a look?

Thank you @jojochuang!


Create .pre-commit-config.yaml

A pre-commit config file has been added.

i dont think enforcing black formatting is needed in this PR. but it is ok. can you check the build failures please?

I think Black auto reformatting will just make our lives easier, especially for newcomers who don't know about pre-commit but need to lint.


Send the project ID with each request

Is your feature request related to a problem? Please describe.
Each app belongs to a single project. The currently used graphql backend endpoints do not resemble that situation, were deprecated in #508 and only work for bayern.ehrenamtskarte.app.
Describe the solution you'd like
The project id will be available in dart using the build config made available in #513. The currently used deprecated graphql endpoints are replace with project specific ones by sending that project id as param in the request.
Describe alternatives you've considered
None
Additional context
None

Closed by #556


Cannot route to internet through transit gateway

Attempting to setup a multaccount transit network where the spoke account can route through the transit gateway and get to the internet. Created two new fresh aws accounts to apply this terraform and let it setup all of the attachments, route tables, subnets,etc. but I can't seem to get to the internet from the spoke. The instance sitting in the spoke  can ping things in the network account but can't get to the internet.
                  - Core Network Account -                                                              - Spoke Account -
<igw>--<publicsubnet>--<natgw>--<privatesubnet>--<tgw_attachment>--<tgw>--<tgw_attachment>--<privatesubnet>--<instance>

main.tf
resource "aws_ec2_transit_gateway" "network_tgw" {
  provider                       = aws.core_prod_network
  amazon_side_asn                = 65412
  auto_accept_shared_attachments = "enable"
  dns_support                    = "enable"
  description                    = "Core Prod Network Transit Gateway"
}

resource "aws_ram_resource_share" "core_prod_network" {
  provider                  = aws.core_prod_network
  name                      = "Transit Gateway Resource Share"
  allow_external_principals = true
  tags = {
    Name = "core-prod-network-tgw-resource-share"
  }
}

# Share the transit gateway...
resource "aws_ram_resource_association" "core_prod_network" {
  provider           = aws.core_prod_network
  resource_arn       = aws_ec2_transit_gateway.network_tgw.arn
  resource_share_arn = aws_ram_resource_share.core_prod_network.id
}

#### For every Spoke Account, add this to attach tgw
## ..with the core_prod_devops account
resource "aws_ram_principal_association" "core_prod_devops" {
  provider           = aws.core_prod_network
  principal          = var.vega_accounts.core_prod_devops.id
  resource_share_arn = aws_ram_resource_share.core_prod_network.id
}

## core_prod_network
module "core_prod_network_vpc" {
  providers = {
    aws   = aws.core_prod_network
    awscc = awscc.core_prod_network
  }
  source     = "aws-ia/vpc/aws"
  name       = "core-prod-network-vpc"
  cidr_block = "<IP_ADDRESS>/16"
  az_count   = 2

  subnets = {
    public = {
      name_prefix               = "core-prod-network-public"
      netmask                   = 24
      nat_gateway_configuration = "all_azs"
      route_to_transit_gateway  = ["<IP_ADDRESS>/8"]
    }

    private = {
      name_prefix              = "core-prod-network-private"
      netmask                  = 24
      route_to_nat             = true
      route_to_transit_gateway = ["<IP_ADDRESS>/8"]
    }

    transit_gateway = {
      name_prefix                                     = "core-prod-network-transit"
      netmask                                         = 28
      transit_gateway_id                              = aws_ec2_transit_gateway.network_tgw.id
      route_to_nat                                    = false
      transit_gateway_default_route_table_association = true
      transit_gateway_default_route_table_propagation = true
    }
  }
}

### Output Block we need after every VPC creation
output "core_prod_network_vpc_id" {
  value = module.core_prod_network_vpc.vpc_attributes.id
}

output "core_prod_network_vpc_info" {
  value = module.core_prod_network_vpc
}

## core_prod_devops
module "core_prod_devops_vpc" {
  providers = {
    aws   = aws.core_prod_devops
    awscc = awscc.core_prod_devops
  }
  source     = "aws-ia/vpc/aws"
  name       = "core-prod-devops-vpc"
  cidr_block = "<IP_ADDRESS>/16"
  az_count   = 2

  subnets = {
    private = {
      name_prefix              = "core-prod-devops-private"
      netmask                  = 24
      route_to_nat             = false
      route_to_transit_gateway = ["<IP_ADDRESS>/0"]
    }

    transit_gateway = {
      name_prefix                                     = "core-prod-devops-transit"
      netmask                                         = 28
      transit_gateway_id                              = aws_ec2_transit_gateway.network_tgw.id
      route_to_nat                                    = false
      transit_gateway_default_route_table_association = true
      transit_gateway_default_route_table_propagation = true
    }
  }
}

I don't know if this is something that you guys have to add to the routing tables in the terraform to account for this use case but something is missing from routing.

Thanks for reporting this issue. I'll investigate today and get back to you

Much appreciated.

Closing for now - if this is still a problem for you please let me know and I can re-open!


Maximum Idle timeout for NAT GAteway

In this article it is mentioned that idle timeout can go from 4 to 10 mins. But the actual maximum value for the timeout is 2 hours (120 mins)

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

ID: ba948130-9ae2-4e15-398e-3573c46d5392
Version Independent ID: f2bed927-309d-d106-c126-b07d357b880e
Content: Tutorial: Create and test a NAT Gateway - Azure portal
Content Source: articles/virtual-network/tutorial-create-validate-nat-gateway-portal.md
Service: virtual-network
Sub-service: nat
GitHub Login: @asudbring
Microsoft Alias: allensu

@aralvar, Thanks for reaching out. We will investigate and update this thread.

@aralvar, Appreciate your feedback. We will update the doc accordingly.

@aralvar, the doc has been edited accordingly and it would take some time for the changes to get reflect over the doc.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

The article is a tutorial and uses a scenario where the idle timeout is changed from 4 minute default to 10 minutes.  The article is correct as written and the section refers to what is covered in the tutorial.  Yes, the maximum allowed value is 120 minutes, but that's not what this article is about.  Please refer to https://docs.microsoft.com/azure/virtual-network/nat-gateway-resource for what is available for this resource.

@asudbring fyi

#please-close


Cannot Install Jupyter Extension in Remote SSH Server

Applies To

[ ] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I am trying to install the jupyter extension in a remote ssh but every time I get an error that says jupyter cannot be installed because it is not compatible with the current version of VSCode. I have tried installing many different versions of vscode and the jupyter extension (including the pre-release) but keep getting the same error. The jupyter extension installs without an issue on my local machine and other extensions like Python have installed fine on the remote ssh.
VS Code Version
1.88.0
Jupyter Extension Version
v2024.3.0
Jupyter logs
2024-04-09 13:37:05.318 [error] Can't install 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code (version 1.88.0).: Incompatible: Can't install 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code (version 1.88.0).
    at x.N (/home/ubuntu/.vscode-server/cli/servers/Stable-5c3e652f63e798a5ac2f31ffd0d863669328dc4c/server/out/vs/server/node/server.main.js:173:32008)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /home/ubuntu/.vscode-server/cli/servers/Stable-5c3e652f63e798a5ac2f31ffd0d863669328dc4c/server/out/vs/server/node/server.main.js:173:23109
    at async Promise.allSettled (index 0)
    at async x.installGalleryExtensions (/home/ubuntu/.vscode-server/cli/servers/Stable-5c3e652f63e798a5ac2f31ffd0d863669328dc4c/server/out/vs/server/node/server.main.js:173:23033)
    at async x.installFromGallery (/home/ubuntu/.vscode-server/cli/servers/Stable-5c3e652f63e798a5ac2f31ffd0d863669328dc4c/server/out/vs/server/node/server.main.js:173:22584)

Coding Language and Runtime Version
Python v3.9
Language Extension Version (if applicable)
v2024.4.0
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote

I just tried it again today and it worked (not sure what changed).


Linker error: undefined reference to `bind'

Hello,
thanks for making this project :)
I faced an issue while trying to compile this on MacOS.
Error: Linker /Users/pyaillet/.platformio/packages/toolchain-xtensa32/bin/xtensa-esp32-elf-gcc failed: exit status: 1
          STDERR OUTPUT:
          /Users/pyaillet/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /Users/pyaillet/Projets/esp32/rust-esp32-std-demo/target/xtensa-esp32-espidf/debug/deps/libstd-8790520575118186.rlib(std-8790520575118186.std.638b6fe2-cgu.7.rcgu.o):(.literal._ZN3std10sys_common3net11TcpListener4bind17hddb23264c2c7f006E+0x8): undefined reference to `bind'
          collect2: error: ld returned 1 exit status

I could not say if it comes from my setup or another problem though :
I installed the toolchain by following instructions provided here.
❯ rustc -V
rustc 1.56.0-dev

Do you know what could be the cause ?

I was able to reproduce the error with the docker image provided by the project https://github.com/esp-rs/rust-build
  = note: Running ldproxy
          Error: Linker /root/.platformio/packages/toolchain-xtensa32/bin/xtensa-esp32-elf-gcc failed: exit status: 1
          STDERR OUTPUT:
          /root/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /opt/app/target/xtensa-esp32-espidf/debug/deps/libstd-16436e5ba6bf7e8a.rlib(std-16436e5ba6bf7e8a.std.1umsku00-cgu.7.rcgu.o):(.literal._ZN3std10sys_common3net11TcpListener4bind17h3475a5f8b9c24e36E+0x8): undefined reference to `bind'
          collect2: error: ld returned 1 exit status

root@001aa6451039:/opt/app# rustc -V
rustc 1.54.0-dev

Nervermind, I was able to fix the error.
For the record, here is what I did:

I deleted my esp toolchain and reinstalled it following these instructions
I did setup the LIBCLANG_PATH according to the previous instructions (I suspect this is what I previously did wrong)
cargo install bindgen, cargo clean and then cargo build went OK


create a page that displays rocket information

create a page similar to the homepage that displays information on the first ten rockets returned from the request
add a link to this page on the homepage

Interested ,please assign

@Cerchie  Can you share the url of home page and screenshot as well?

@gagandeepp
I'll be answering questions once October begins. In the meantime, please see the README.

@Cerchie  I am using this endpoint and it is only listing 4 rockets https://api.spacex.land/graphql/
Schema:
{
rockets {
id
name
wikipedia
}
}

Following is the result set
{
"data": {
"rockets": [
{
"id": "falcon1",
"name": "Falcon 1",
"wikipedia": "https://en.wikipedia.org/wiki/Falcon_1"
},
{
"id": "falcon9",
"name": "Falcon 9",
"wikipedia": "https://en.wikipedia.org/wiki/Falcon_9"
},
{
"id": "falconheavy",
"name": "Falcon Heavy",
"wikipedia": "https://en.wikipedia.org/wiki/Falcon_Heavy"
},
{
"id": "starship",
"name": "Starship",
"wikipedia": "https://en.wikipedia.org/wiki/SpaceX_Starship"
}
]
}
}

https://github.com/stepzen-samples/stepzen-spacex-graphql/pull/19


[#165633078] Mitigate USN-3947-1, USN-3885-2, USN-3943-1

What
This mitigates USN-3947-1, USN-3885-2 and USN-3943-1 by upgrading versions in line with triaging done in this comment: https://www.pivotaltracker.com/story/show/165633078/comments/202039197.
How to review

🐝 Wait for Miki to try this in their dev environment; 🐝
Review alongside https://github.com/alphagov/paas-cf/pull/1867;
Review the choice of versions;
Code review.

Who can review
Not @46bit

I have run this down my dev environment just fine
LGTM


Websocket HandleOnUpgrade and autentication...

Is your feature request related to a problem? Please describe.
My question is related with authentication when using websockets...
Describe the solution you'd like
Sorry if I am wrong but usually we used to authenticate (basic auth or query param, etc.) in the Upgrade websocket handler when we still have access to the HTTP request but in Drogon I can not find this handler. Does Drogon provides any other sort of authentication for websockets?
Thank you
Alex

    // This function is called after a new connection of WebSocket is
    // established.
    virtual void handleNewConnection(const HttpRequestPtr &,
                                     const WebSocketConnectionPtr &) = 0;

The first parameter of the handler is thre upgrade request.

Thanks!


Feature | Use token to access KBS resources

Now after the handshake of the RCAR protocol, KBS will response a token to the requester. This token should have access to the KBS' resources. (This avoids to re-establish a RCAR session again after the former session breaks in the timeout of the token)

duplicated issue https://github.com/confidential-containers/kbs/issues/129. mistake by GH network error.