[bug] npm migrate can't migrate plugins pulled from v1 branch

Describe the bug
Following the commands on the RC blog post, I ran npm run tauri migrate after installing @tauri-apps/cli@next.
NPM deps were upgraded to ^2.0.0-rc.0 including @tauri-apps/plugins-*
Encountered the error:

the package webkit2gtk-sys links to the native library web_kit2, but it conflicts with a previous package which links to web_kit2 as well:
package webkit2gtk-sys v2.0.1

Reproduction
From a 1.6.0 app using the following cargo deps:
tauri = { version = "2.0.0-rc", features = [] }
tauri-plugin-dialog = "2.0.0-rc.0"
tauri-plugin-shell = "2.0.0-rc.0"
tauri-plugin-store = { branch = "v1", git = "https://github.com/tauri-apps/plugins-workspace" }
tauri-plugin-window-state = { branch = "v1", git = "https://github.com/tauri-apps/plugins-workspace" }

npm install @tauri-apps/cli@next
npm run tauri migrate

Expected behavior
migrate without encountering errors. Full error encountered:
> set RUST_BACKTRACE=full& tauri migrate

    Info Installing NPM dependencies "<EMAIL_ADDRESS>"@tauri-apps/plugin-dialog", <EMAIL_ADDRESS>
added 2 packages, changed 1 package, and audited 350 packages in 5s

118 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
    Info Installing Cargo dependencies "tauri-plugin-dialog", "tauri-plugin-shell"...
    Updating crates.io index
      Adding tauri-plugin-dialog v2.0.0-rc.0 to dependencies
      Adding tauri-plugin-shell v2.0.0-rc.0 to dependencies
    Updating crates.io index
error: failed to select a version for `webkit2gtk-sys`.
    ... required by package `wry v0.18.3`
    ... required by package `wry v0.18.3`
    ... which satisfies dependency `wry = "^0.18.3"` of package `tauri-runtime-wry v0.9.0`
    ... which satisfies dependency `tauri-runtime-wry = "^0.9.0"` of package `tauri v1.0.0`
    ... which satisfies dependency `tauri = "^1"` of package `tauri-plugin-store v0.0.0 (https://github.com/tauri-apps/plugins-workspace?branch=v1#5e3900e6)`
    ... which satisfies git dependency `tauri-plugin-store` (locked to 0.0.0) of package `app v1.0.0 (C:\Apps91\Mapestry\src-tauri)`
versions that meet the requirements `^0.18` are: 0.18.0

the package `webkit2gtk-sys` links to the native library `web_kit2`, but it conflicts with a previous package which links to `web_kit2` as well:
package `webkit2gtk-sys v2.0.1`
    ... which satisfies dependency `ffi = "^2.0.1"` of package `webkit2gtk v2.0.1`
    ... which satisfies dependency `webkit2gtk = "=2.0.1"` of package `tauri v2.0.0-rc.0`
    ... which satisfies dependency `tauri = "^2.0.0-rc"` of package `app v1.0.0 (C:\Apps91\Mapestry\src-tauri)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "web_kit2"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `webkit2gtk-sys` which could resolve this conflict
    Error failed to migrate from v1: Error installing new Cargo packages: Failed to install Cargo dependencies

Full tauri info output
$ npm run tauri info

[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 127.0.2651.105
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.10.0
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.8
    - @tauri-apps/api [NPM]: 2.0.0-rc.0
    - @tauri-apps/cli [NPM]: 2.0.0-rc.3

[-] App
    - build-type: bundle
    - CSP: default-src 'self' data: blob:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; connect-src ipc: http://ipc.localhost
    - frontendDist: ../dist
    - devUrl: http://localhost:3055/
    - framework: React
    - bundler: Rollup

Stack trace
Updating crates.io index
error: failed to select a version for `webkit2gtk-sys`.
    ... required by package `wry v0.18.3`
    ... required by package `wry v0.18.3`
    ... which satisfies dependency `wry = "^0.18.3"` of package `tauri-runtime-wry v0.9.0`
    ... which satisfies dependency `tauri-runtime-wry = "^0.9.0"` of package `tauri v1.0.0`
    ... which satisfies dependency `tauri = "^1"` of package `tauri-plugin-store v0.0.0 (https://github.com/tauri-apps/plugins-workspace?branch=v1#5e3900e6)`
    ... which satisfies git dependency `tauri-plugin-store` (locked to 0.0.0) of package `app v1.0.0 (C:\Apps91\Mapestry\src-tauri)`
versions that meet the requirements `^0.18` are: 0.18.0

the package `webkit2gtk-sys` links to the native library `web_kit2`, but it conflicts with a previous package which links to `web_kit2` as well:
package `webkit2gtk-sys v2.0.1`
    ... which satisfies dependency `ffi = "^2.0.1"` of package `webkit2gtk v2.0.1`
    ... which satisfies dependency `webkit2gtk = "=2.0.1"` of package `tauri v2.0.0-rc.0`
    ... which satisfies dependency `tauri = "^2.0.0-rc"` of package `app v1.0.0 (C:\Apps91\Mapestry\src-tauri)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "web_kit2"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `webkit2gtk-sys` which could resolve this conflict
    Error failed to migrate from v1: Error installing new Cargo packages: Failed to install Cargo dependencies

Additional context
Ran npm commands from gitbash terminal.

Change the store and window-state plugin to use the v2 branch. I think the migrate command currently can't handle git dependencies, which i guess it should considering that v1 plugins never got released...

Change the store and window-state plugin to use the v2 branch. I think the migrate command currently can't handle git dependencies, which i guess it should considering that v1 plugins never got released...

I figured this might need changing - once updated, do I re-run migrate or another command?
Updated deps to:
tauri-plugin-store = { branch = "v2", git = "https://github.com/tauri-apps/plugins-workspace" }
tauri-plugin-window-state = { branch = "v2", git = "https://github.com/tauri-apps/plugins-workspace" }

once updated, do I re-run migrate or another command?

Hmm, probably re-run it. I'm not sure how well the migrate command handles failures like this right now so maybeee you have to reset the project to v1 again (assuming you have version control set up), change the plugins deps and run it again 🤔

I've re-organised main.rs and lib.rs per the migration docs. Looks like the migration worked through my tauri.conf.json and extracted the allowlist perms into capabilities/migrated.json.
I'm just updating shell plugin code. I'll raise a separate issue if I run into trouble there. I'll leave this open until I get a running app stood up. Thanks for the help.

It appears the migration script did duplicate a permission from my v1 allow list:
  "permissions": [
    "core:default",
    {
      "identifier": "fs:scope",
      "allow": [
        "$APP/*",
        "$DESKTOP/*",
        "$RESOURCE/*"
      ]
    },
    "core:window:allow-set-title",
    "shell:allow-execute",
    "shell:allow-open",
    "shell:allow-open", // dupe
    "dialog:allow-open",
    "dialog:allow-save",
    {
      "identifier": "http:default",
      "allow": [{ "url": "file:///" }]
    }
  ]

During npm start I'm seeing:
Permission fs:scope not found, expected one of core:app:default, ...
It's as if it can't see the fs:scope object in capabilities/migrated.json
   Compiling tauri-plugin-shell v2.0.0-rc.0
error: failed to run custom build command for `app v1.0.0 (C:\yyy\src-tauri)`

Caused by:
  process didn't exit successfully: `C:\yyy\src-tauri\target\debug\build\app-d15e51f6b2c8c9a8\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-check-cfg=cfg(desktop)
  cargo:rustc-cfg=desktop
  cargo:rustc-check-cfg=cfg(mobile)
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_APP_NAME=yyy
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_PREFIX=yyy
  cargo:rustc-check-cfg=cfg(dev)
  cargo:rustc-cfg=dev
  cargo:PERMISSION_FILES_PATH=C:\yyy\src-tauri\target\debug\build\app-9ea48d623f55e621\out\app-manifest\__app__-permission-files
  cargo:rerun-if-changed=capabilities
  Permission fs:scope not found, expected one of core:app:default,

During npm start I'm seeing:
Permission fs:scope not found, expected one of core:app:default, ...
It's as if it can't see the fs:scope object in capabilities/migrated.json
   Compiling tauri-plugin-shell v2.0.0-rc.0
error: failed to run custom build command for `app v1.0.0 (C:\yyy\src-tauri)`

Caused by:
  process didn't exit successfully: `C:\yyy\src-tauri\target\debug\build\app-d15e51f6b2c8c9a8\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-check-cfg=cfg(desktop)
  cargo:rustc-cfg=desktop
  cargo:rustc-check-cfg=cfg(mobile)
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_APP_NAME=yyy
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_PREFIX=yyy
  cargo:rustc-check-cfg=cfg(dev)
  cargo:rustc-cfg=dev
  cargo:PERMISSION_FILES_PATH=C:\yyy\src-tauri\target\debug\build\app-9ea48d623f55e621\out\app-manifest\__app__-permission-files
  cargo:rerun-if-changed=capabilities
  Permission fs:scope not found, expected one of core:app:default,

The V2 docs state the variables I've used (see previous post) are still valid in V2.

I think the migration added the FS scope but not the FS plugin. I'll run through the list of changes needed here today.

During npm start I'm seeing:
Permission fs:scope not found, expected one of core:app:default, ...
It's as if it can't see the fs:scope object in capabilities/migrated.json
   Compiling tauri-plugin-shell v2.0.0-rc.0
error: failed to run custom build command for `app v1.0.0 (C:\yyy\src-tauri)`

Caused by:
  process didn't exit successfully: `C:\yyy\src-tauri\target\debug\build\app-d15e51f6b2c8c9a8\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-check-cfg=cfg(desktop)
  cargo:rustc-cfg=desktop
  cargo:rustc-check-cfg=cfg(mobile)
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_APP_NAME=yyy
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_NAME_PREFIX=yyy
  cargo:rustc-check-cfg=cfg(dev)
  cargo:rustc-cfg=dev
  cargo:PERMISSION_FILES_PATH=C:\yyy\src-tauri\target\debug\build\app-9ea48d623f55e621\out\app-manifest\__app__-permission-files
  cargo:rerun-if-changed=capabilities
  Permission fs:scope not found, expected one of core:app:default,

The V2 docs state the variables I've used (see previous post) are still valid in V2.

I think the migration added the FS scope but not the FS plugin. I'll run through the list of changes needed here today.

from my test it does add the FS plugin, maybe it's because yours failed?

My migration did fail, how do I add the FS plugin - add it to my Cargo.toml dependencies?
My current deps:
[dependencies]
base64 = "0.22.0"
minifier = "0.3.0"
minify-html = "0.15.0"
scraper = "0.19.1"
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
tauri = { version = "2.0.0-rc", features = [] }
tauri-plugin-dialog = "2.0.0-rc.0"
tauri-plugin-shell = "2.0.0-rc.0"
tauri-plugin-store = { branch = "v2", git = "https://github.com/tauri-apps/plugins-workspace" }
tauri-plugin-window-state = { branch = "v2", git = "https://github.com/tauri-apps/plugins-workspace" }
thiserror = "1.0"

Should the migration script add the src-tauri/gen directory to .gitignore if the ignore file exists?

No, currently the suggestion is to commit the gen folder too. without gen/schemas though (which is what the default gitignore file does).


[dvsim] Introduce a compile-time randomization mechanism using a randomly picked seed

The first commit makes a minor enhancement to dvsim, introducing seed to CompileSim and CompileOneShot classes. This seed value is picked randomly, or set via command line using the --build-seed switch.
This seed value can thus be referenced in build_opts in the simulation configuration hjson file using the special substvar {seed}.
The second commit test-drives this approach in RV_DM testbench, where the JTAG IDCODE is one such design constant that can be mutated without any side-effects. It sets a global pre-processor macro BUILD_SEED which can be used in any Verilog source as the source compile-time randomness.
If different seed values are sought at compile-time, the BUILD_SEED macro can be mutated further (PRNG?), to derive secondary random constants. This will make the compilation deterministically reproducible.

One slight wrinkle is that this is going to add another step for someone trying to reproduce a failing test. Have you had any thoughts about how we report the build seed in the output logs?
(Also, I'm pretty unconvinced this is worth doing at all, but we talked through that in the RV_DM meeting already and I think I lost the argument!)

Yes - the build seed should show up front and center in the final report. I will fix that. This is worth doing because it is better than running tests day after day, with the same set of device constants. The IDCODE is just a start - the real change that will come once this lands is to modify ALL rand const packages before nightly regressions are run (it would only apply to nightlies). Nuvoton will tape out the chip with a completely different set of device constants than what exists in the open repo, so IMO this is worth doing.
Also, this should largely have no impact on reproducing test failures themselves - if the device constant values are having side effects, then we either did something disastrously wrong in the design, or our verification is not robust enough - both of these are worth uncovering. I see no reason to have to pass the build seed to reliably reproduce a failure (for the most part). Sure, some randomized values may look different, but I think that is ok.

In my latest force-push, the build seed is now indicated in the final report. It is also made 'static', i.e. constant across ALL builds across all DUTs.


tabs vs spaces?

Is there a strong preference for the tabs over spaces? PEP8 prefers spaces. I guess most people's editors default to spaces.  Am I alone in preferring a switch over to spaces?

I actually prefer tabs to spaces, seems faster and easier..
Also, considering that my editor allows for easy manipulations with both and an easy conversion from one to the other, I can work with both easily.. Let's just say I got used to it?
I also have the tendency to use the 4-spaces tab not the 2-spaces.. Sorry for the trouble :)


High level rules inside Arrays don't return the index on the error message

Ex:
{:should_have_investment_rate_only=>["must be filled", "must be filled", "must be filled", "cannot be defined"], 2=>{:minimum_investment=>["is missing"]}}
The rule :should_have_investment_rate_only return an array of error messages, but it's not possible to know if it was on item 1,2 or 42. It would be better if it worked like the other rules.
The schema was something like:
BATCH_SCHEMA = Dry::Validation.JSON do
  each do
    schema(OTHER_SCHEMA)
  end
end

OTHER_SCHEMA = Dry::Validation.JSON do
  required(:minimum_investment) #blah blah

  rule(:should_have_investment_rate_only) do
    # the rule
  end
end

I'm gonna close this one since it's actually about high-level rules which are gone here.


Enhancements create event

WHAT DOES THIS PR DO?

[x] adding SKIP and also csv format util logic
[x] input validation for the format field
[x] introducing csv format in responses
[x] Gzip compressing to decrease the size of the response body and increase the speed

WHAT ISSUES ARE RELATED TO THIS PR?

Jira cards

PLAT-1197

HOW DO I TEST OUT THIS PR?
cd src/device-registry
npm install
npm run stage-mac

check the README for OS specific instructions for running the microservice.
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:

[x] GET Events V2

merging since changes are just hotfixes. @123MwanjeMike and @NoahNsimbe


Bug - Useful but currently unusable - constant DOM Exceptions and causes Obsidian to run out of memory

Please see the attached

Ping

Hi @ozntel
Could you please review this issue?
Thanks

Hi @ozntel
Any hope for a fix?
Thanks

I now consider this plugin to be dead, and I'm closing the issue


Proposal: Agent healthcheck endpoint to advance production-readiness of deployed agents

Is your feature request related to a problem? Please describe.
As it stands, there is currently no universal standard in the spec for liveness/readiness of an Agent running in the context of a system. Until I receive an vendor-Agent/model/custom-Agent bad response to a task-related request, I don't know there are problems with my Agent (within the context of the spec).
At a high level, I believe an open protocol capably applied across all Agent implementations should treat an Agent as any other service within a stack and consider things like integrating observability, events/metrics, shutdown, etc, but this proposal is limited in scope to a binary health/unhealth discovery implementation.
Describe the solution you'd like
Kubernetes actually has a great solution in the form of two health check probes, liveness and readiness. In such context, the liveness healthcheck returns either a 200 or unhealthy HTTP status like 400/500 and indicates that the service is alive, and the readiness healthcheck does the same but ensures all dependencies are also alive (such as connection to a database).
An Agent that depends on connection to a single model is arguably not dependent upon any external resources as it could be considered unalive/not healthy if there is no connection to its single LLM, but I think we could easily see a future where a single orchestrator Agent is facilitating Agent interactions between multiple models, and a truly universally applied spec needs to consider such circumstances.
An endpoint /ap/v1/agent/health_check would be a good place to capture health-related inquiries and I'd love to hear more discussion from there about:

Whether liveness_and_ readiness are both requirements
Whether it needs to be a concern of the spec beyond providing a dedicated endpoint to query health and can be left as an Agent-implementation concern from there

I think an implementation that lacks the ability to decipher if a non-200 response is due to a failure of my Agent to start or a bug in my implementation is a poor developer experience, so Agent-implementations will solve for this on their own and will undoubtedly differ in their implementations without a protocol-driven spec.
Describe alternatives you've considered
The alternative is mostly just not providing a way to query an Agent's healthy state, which is the current status of the Agent Protocol. Agent health is the responsibility of the Agent-specific implementation and not of the protocol, which leads to a lack of consistency and will promote vendor lock-in should Agents evolve to 3rd party SaaS tooling.
Additional context
It could be worthwhile discussion to extend this conversation to things like Agent deployment versioning /ap/v1/agent/version and other deployment state/service context discovery as well, but again, this proposal is limited in scope to solely a health check.

I'm curious what your thoughts are on the info endpoint, I posted a potential schema for it here in Issue #39.
It didn't go over a health check for readiness and liveliness, but I think that it could be added there technically. Or some other type of standardized status message.
The schema we were considering does include a version for both the Agent Protocol and the Agent itself, which would be useful for clients.

That's an interesin

I'm curious what your thoughts are on the info endpoint, I posted a potential schema for it here in Issue #39.
It didn't go over a health check for readiness and liveliness, but I think that it could be added there technically. Or some other type of standardized status message.
The schema we were considering does include a version for both the Agent Protocol and the Agent itself, which would be useful for clients.

That's an interesting proposal @jzanecook. I have some thoughts about that info proposal that are distinctly different form this one, but I believe they are and should be separate concerns. I think it's worthwhile deciding earlier rather than later how prescriptive the agent protocol needs to be. For what it's worth, I prefer open/extensible protocols rather than restrictive ones, and I also believe a mechanism in the protocol for Agent metadata is valuable but is a separate concern from liveness or readiness.
I would find a lot of value in being able to GET liveness with a 200 response as good enough to detect liveness of an Agent. I think the readiness check is distinctly different because it indicates that dependent resources are also alive and responsive. Agent metadata is also valuable but a GET for info/metadata should be different than a GET for a factor of health. My preference in RESTful architectures (since this protocol appears to assume HTTP so far) is always to keep separate endpoints for separate resources.


Adding Email Validation To Form

This Pull Request Closes #69
Adds Email Validation to Event Creation Form using the email_address crate, I also added another check of a . in the domain to make sure that the email isn't just a@a as that was originally passing using just the crate, as visible in the image below.

Final version is visible below.

Could possibly add a mailbox existance checker later on.

Great work! 🥳


🐛 fix i18n not working in production issue

Why need this change? / Root cause:

i18n not working in production

Changes made:

Test Scope / Change impact:

Issue

Close #291

✅ Knip Scan Result for https://github.com/Game-as-a-Service/Game-Lobby-Web/pull/297/commits/a1a9c112764e01951b81ebd390252a9354c40355

Unused files (10)

Unused files (10)

.bundlewatch.config.js

components/shared/Chat/ChatContent.tsx

components/shared/Chat/ChatMessage.tsx

components/shared/Chat/index.tsx

components/shared/Icon/group/news.tsx

configs/i18nConfigs.ts

lighthouserc.js

reset.d.ts

scripts/knipScanReporter.js

scripts/lhciScanReporter.js

Unused dependencies (2)

Unused dependencies (2)

@svgr/webpack  package.json

sharp          package.json

Unused devDependencies (5)

Unused devDependencies (5)

@actions/github             package.json

@octokit/core               package.json

@storybook/blocks           package.json

@storybook/testing-library  package.json

@total-typescript/ts-reset  package.json

Configuration issues (1)

Configuration issues (1)

Unused item in ignoreDependencies: @next/bundle-analyzer


feat(seat-upgrades): auto upgrades seats if applicable or block till plan upgrade

TODO:

[ ] Update Front end to alert anyone on Scale Up or above that they will be charged!
[ ] Fix E2E tests

@kyle-ssg - please check the requirements here! https://github.com/Flagsmith/flagsmith/issues/298
Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?

Changes
This will add a new seat to the user subscription if the plan supports it(AUTO_SEAT_UPGRADE_PLANS)
Else This will not allow user the user to join the organisation until plan upgrades
Adds an e2e test endpoint /api/v1/e2etests/update-seats/ that takes an optional parameter named seats(default value 3)
How did you test this code?

Manually test the Chargebee code on staging test site
Adds unit test cases

Adds an e2e test endpoint /api/v1/e2etests/update-seats/ that takes an optional parameter named seats(default value 3)


Custom menu bar

Windows native menu bar is enough for MVP. Will eventually add a custom menu bar after Tandem matures a bit.


Add this Website!

URL: https://matthewhoelter.com/
Moving the mouse around on the homepage leaves a trail of colorful confetti!

love it! I'll add it in the next update.


Use new iree_py_binary macro so that legacy_create_init gets set prop…

…erly.
Fixes #2405 (for now)

cc @phoenix-meadowlark (https://github.com/google/iree/commit/0dc2f4f95fc24a7500b95406de5dee0851afa788 added these)
Maybe we should bazel run these or other targets on CI? Or just remember to test the open source builds as part of such changes. There are some functional differences between the internal and external builds.
Context: before this commit, bazel run //integrations/tensorflow/e2e:math_test_manual -- --target_backends=iree_vmla fails while bazel test //integrations/tensorflow/e2e:e2e_tests_math_test__tf__iree_vmla passes.
Here's the error:
    from pyiree.tf.support import tf_test_utils
ModuleNotFoundError: No module named 'pyiree.tf'

cc @phoenix-meadowlark (0dc2f4f added these)
Maybe we should bazel run these or other targets on CI? Or just remember to test the open source builds as part of such changes. There are some functional differences between the internal and external builds.
Context: before this commit, bazel run //integrations/tensorflow/e2e:math_test_manual -- --target_backends=iree_vmla fails while bazel test //integrations/tensorflow/e2e:e2e_tests_math_test__tf__iree_vmla passes.
Here's the error:
    from pyiree.tf.support import tf_test_utils
ModuleNotFoundError: No module named 'pyiree.tf'

I don't know how much we want to put in to trying to test weird combinations of bazel feature flags. The rule that would cover most of this now would be: never have a py_binary/py_test in the IREE tree: use iree_py_binary and iree_py_test


Feat(penumbra) add support

replaced by https://github.com/strangelove-ventures/cosmos-operator/pull/423


Unhandled error conditions in worker.py

indexer/worker.py has two places with "# XXX fatal error?" comments.  I think the first was the cause of the hung tqfetcher process (Pika thread exited, but all the other threads continued running, cut off from Pika communication) last week.
I don't think there's much value to a traceback (ie; throwing an Exception), because the error likely happened elsewhere, so I'm leaning towards adding sys.exit(1), which I've checked propagates an exception up thru all with context handlers, and exits with less noise...

Two different problems seen.  The above description may be a conflation of them:
On 6/15 tqfetcher (using base class MultiThreadStoryWorker) lost rabbitmq connection, Pika thread exited, sending kisses of death to worker threads.  Main thread exited with status zero, so the container was not (and could not be) restarted.
On 6/9 the csv-queuer (using base class Queuer) lost rabbitmq connection, and continued to run (outputting error messages, and marking the work file successfully queued).  This could be addressed at several different levels (long inheritance path): QApp, Producer, StoryProducer, Queuer...

While testing a fix for the above two problems (by doing docker service scale ...._rabbitmq=0 and back to 1), I found a third problem:
In an ordinary Worker (parser and importer), the main thread blocks on _message_queue and doesn't see that the Pika thread has exited.


Allow rendering meshes without UV coordinate data.

Objective
Bevy requires meshes to include UV coordinates, even if the material does not use any textures, and will fail with an error ERROR bevy_pbr::material: Mesh is missing requested attribute: Vertex_Uv (MeshVertexAttributeId(2), pipeline type: Some("bevy_pbr::material::MaterialPipeline<bevy_pbr::pbr_material::StandardMaterial>")) otherwise. The objective of this PR is to permit this.
Solution
This PR follows the design of #4528, which added support for per-vertex colours. It adds a shader define called VERTEX_UVS which indicates the presence of UV coordinates to the shader.

This relates to #5147 but it only solves the problem with UV. The same problem will still happens with Position and Normal.

bors r+


500 Internal Server Error - Invalid JSON data

When I send an PATCH request with invalid JSON data to the server, I get the following as a response:
500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong.
and in the log file the following:
App 32245 stderr: Error during failsafe response: 784: unexpected token at '{
App 32245 stderr:   "data": {
App 32245 stderr:     "id": 2
App 32245 stderr:     "type": "users",
App 32245 stderr:     "attributes": {
App 32245 stderr:       "first-name": "M.C.",
App 32245 stderr:       "last-name": "McMaster"
App 32245 stderr:     }
App 32245 stderr:   }
App 32245 stderr: }'

I know, there is a comma missing but it probably should not return 500 Internal Server Error.
I haven't tried other requests than PATCH yet but I wanted to open an issue before I forget it.
I am using the latest stable jsonapi-resources (v0.8.1) together with Rails 5.0.0 and Ruby 2.3.1.

I believe returning a 500 Internal Server Error follows the standard as stated at jsonapi. What response are you expecting it to be?
Since it is malformed data that is just trying to be processed by the server it is allowed to return a 500 response error.
Unless you whitelist the specific exception that is occurring you won't be able to handle it yourself. In README.md.

I am sorry, I think I missed this part of the documentation. Thank you for clearing things up @Petesta

The problem is, we don't get a rendered json error response but instead the default rails 500.html. This is the bug I am talking about @Petesta

@Ybrin Ahh, that's a little more specific now. Mentioning the Rails 500.html page. I thought you were just receiving a 500 Internal Server Error JSON response.
But you're right, I got the same response. Here's mine.
JSON::ParserError at /endpoint
==============================

> 743: unexpected token at '{"data":{"type",:"foo"}'

json (2.0.2) lib/json/common.rb, line 156
-----------------------------------------

  151     #   additions even if a matching class and create_id was found. This option
  152     #   defaults to false.
  153     # * *object_class*: Defaults to Hash
  154     # * *array_class*: Defaults to Array
  155     def parse(source, opts = {})
> 156       Parser.new(source, opts).parse
  157     end
  158
  159     # Parse the JSON document _source_ into a Ruby data structure and return it.
  160     # The bang version of the parse method defaults to the more dangerous values
  161     # for the _opts_ hash, so be sure only to parse trusted _source_ documents.

App backtrace
-------------

Full backtrace
--------------

 - json (2.0.2) lib/json/common.rb:156:in `parse'
 - jsonapi-resources (0.8.0.beta2) lib/jsonapi/mime_types.rb:22:in `block in parser'
 - actionpack (5.0.0) lib/action_dispatch/http/parameters.rb:66:in `parse_formatted_parameters'
 - actionpack (5.0.0) lib/action_dispatch/http/request.rb:366:in `block in POST'
 - rack (2.0.1) lib/rack/request.rb:57:in `fetch_header'
 - actionpack (5.0.0) lib/action_dispatch/http/request.rb:365:in `POST'
 - actionpack (5.0.0) lib/action_dispatch/http/parameters.rb:35:in `parameters'
 - actionpack (5.0.0) lib/action_dispatch/http/filter_parameters.rb:41:in `filtered_parameters'
 - actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:21:in `process_action'
 - actionpack (5.0.0) lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
 - activerecord (5.0.0) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
 - actionpack (5.0.0) lib/abstract_controller/base.rb:126:in `process'
 - actionpack (5.0.0) lib/action_controller/metal.rb:190:in `dispatch'
 - actionpack (5.0.0) lib/action_controller/metal.rb:262:in `dispatch'
 - actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
 - actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:32:in `serve'
 - actionpack (5.0.0) lib/action_dispatch/journey/router.rb:39:in `block in serve'
 - actionpack (5.0.0) lib/action_dispatch/journey/router.rb:26:in `serve'
 - actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:725:in `call'
 - bullet (5.2.0) lib/bullet/rack.rb:10:in `call'
 - rack (2.0.1) lib/rack/etag.rb:25:in `call'
 - rack (2.0.1) lib/rack/conditional_get.rb:38:in `call'
 - rack (2.0.1) lib/rack/head.rb:12:in `call'
 - activerecord (5.0.0) lib/active_record/migration.rb:552:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
 - activesupport (5.0.0) lib/active_support/callbacks.rb:97:in `__run_callbacks__'
 - activesupport (5.0.0) lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
 - activesupport (5.0.0) lib/active_support/callbacks.rb:90:in `run_callbacks'
 - actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:36:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
 - better_errors (2.1.1) lib/better_errors/middleware.rb:84:in `protected_app_call'
 - better_errors (2.1.1) lib/better_errors/middleware.rb:79:in `better_errors_call'
 - better_errors (2.1.1) lib/better_errors/middleware.rb:57:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
 - railties (5.0.0) lib/rails/rack/logger.rb:36:in `call_app'
 - railties (5.0.0) lib/rails/rack/logger.rb:24:in `block in call'
 - activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in `block in tagged'
 - activesupport (5.0.0) lib/active_support/tagged_logging.rb:26:in `tagged'
 - activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in `tagged'
 - railties (5.0.0) lib/rails/rack/logger.rb:24:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/request_id.rb:24:in `call'
 - rack (2.0.1) lib/rack/runtime.rb:22:in `call'
 - activesupport (5.0.0) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in `call'
 - actionpack (5.0.0) lib/action_dispatch/middleware/static.rb:136:in `call'
 - rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
 - rack-cors (0.4.0) lib/rack/cors.rb:80:in `call'
 - sentry-raven (2.0.2) lib/raven/integrations/rack.rb:50:in `call'
 - rack-mini-profiler (0.10.1) lib/mini_profiler/profiler.rb:278:in `call'
 - railties (5.0.0) lib/rails/engine.rb:522:in `call'
 - puma (3.6.0) lib/puma/configuration.rb:225:in `call'
 - puma (3.6.0) lib/puma/server.rb:578:in `handle_request'
 - puma (3.6.0) lib/puma/server.rb:415:in `process_client'
 - puma (3.6.0) lib/puma/server.rb:275:in `block in run'
 - puma (3.6.0) lib/puma/thread_pool.rb:116:in `block in spawn_thread'

I've submitted a PR for this but not sure if there's a better way to handle it.

https://github.com/cerebris/jsonapi-resources/pull/895

I can see how that would happen. I'll try to get a fix soon.

@lgebhardt Ahh, no worries. Yea, I created a PR to help resolve this issue.


⚠ SceneTime has degraded performance

In 41ed2ab, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3094 ms

Resolved: SceneTime performance has improved in 139e3a2 after 9 minutes.


Add space to SSH command to fix error when using -i option

Using the -i option to supply a SSH key fails with the error 'Safety check failed - the destination does not appear to be a backup folder or drive (marker file not found).' This seems to be because of a missing space in the SSH parsing code which means that the key address and the SSH address get munged together. This pull request simply adds a space between them.

Thanks a lot @wragge!
I made a tiny change to make the tests pass (not adding a double space when not needed).

Just released https://github.com/basnijholt/rsync-time-machine.py/releases/tag/v1.3.1.


Update to gotch 0.9.0

Would be great to update transformer to work with https://github.com/sugarme/gotch/tree/v0.9.0
For example in /transformer/util/activation.go, the MustGelu method signature changed to accept a string and a bool:
func (g GeluActivation) Fwd(x *ts.Tensor) (retVal *ts.Tensor) {
	return x.MustGelu("???", false)
                           ^^^
}

Hitting the same issue, lets get this fixed

func (g GeluActivation) Fwd(x *ts.Tensor) (retVal *ts.Tensor) {
	return x.MustGelu("none", false)
}

you can replace with "none" or "tanh"
according to libtorch docs


Understanding Closures in Ruby

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
This fixes #2523.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[X] Does your article follow any of the suggested structure formats? - see example formats
[X] Is your article properly formatted in Markdown? - see Github Markdown guide
[X] Have you used the correct folder and file structure? - see Contribution Guidelines
[X] Is your article over 750 words? - Tool: Wordcounter.net
[X] Have you used our preferred heading structure? - H3 (###) and up
[X] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[X] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[X] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[X] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[X] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[X] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[X] Have you checked your article for readability? - Tool: Hemmingway
[X] Have you added sources for quotes and images that aren't yours?

Technical checks

[X] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines

@Njunu-sk
Good afternoon and thank you for submitting your article for publishing. It has been entered into our queue and should be reviewed (and published pending any changes) as soon as a peer reviewer is finished with the ones in the queue before it. 🚀

Understanding Closures in Ruby #2755.pdf
@Njunu-sk
There appear to be many sentences in this article that are taken verbatim from third-party sources. We can't publish any content that is not original or properly cited/referenced. There are many free online tools where you can check this (such as quetext.com, and if you're uncertain about the definitions around plagiarism, this is a good resource to reference

Can you run another plagiarism check please? @hectorkambow

plagiarism check completed - all good
2120420-dd961f3ca325953134fd-1626876066834.pdf

Hey @Njunu-sk 👋
Your local branch doesn't have your author folder for some reason - I don't know how it was deleted on your end.
Please sync your forked repo and branch with "master", which should bring back your author profile since it is available on our repo.

Great article - good work @Njunu-sk @WanjaMIKE


Formatting is broken

The formatting of the section documenting the fields in this structure is broken.  I've tried wtih Edge, Internet Explorer, Chrome and Firefox.  On all, it shows the html source instead of being formatted for reading.
This isn't the only NDIS structure documentation page that is similarly broken.

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

ID: d88ac221-7a6b-4460-fc07-52eecb039e7b
Version Independent ID: 1bcd65e9-9bb5-ed36-47fb-061b67ff706b
Content: _NDIS_MINIPORT_INIT_PARAMETERS (ndis.h) - Windows drivers
Content Source: wdk-ddi-src/content/ndis/ns-ndis-_ndis_miniport_init_parameters.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @duncanmacmichael
Microsoft Alias: dumacmic

Thanks so much @DyessGG for this.
It turned out that this was a system-wide build issue. We've made the fix and all topics should be rendering correctly now.
Eliot


typo: Double word "has"

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/libraries/standard/data-structures.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove WLR_DRM_NO_ATOMIC_GAMMA workaround

This is fixed on amdgpu, so we don't need this any more.

Thanks!


disable function action

This PR updates the release workflow to disable the batch and send functions before a deployment, and re-enable them when the deployment has completed (even if deployment failure)
Test Steps:

Run a deployment and check if functions are disabled in the function app during.

Changes

Update release workflow to include function disable/re-enable
Update documentation to reference disable function usage

Checklist
Testing

[x] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Fixes

Closes #3385

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Time to review
Total comments

cwinters-usds
27
2h 9m
17

carlosfelix2
12
2h 23m
41

MauriceReeves-usds
11
19h 40m
7

TomNUSDS
11
1h 27m
29

jeremy-page
8
6m
0

jimduff-usds
8
2h 30m
13

jbiskie
8
1h 27m
0

brick-green-agile6
7
10h 4m
2

TurkeyFried
6
1h 2m
1

JosiahSiegel
6
4m
0

sethdarragile6
6
40m
0

snesm
6
41m
7

bgantick
5
25m
1

kevinhaube
5
12m
0

oslynn
4
2d 23h 3m
1

clediggins-usds
4
4h 26m
4

jh765
4
1h 26m
4

ahay-agile6
3
22m
0

acoushawk
2
4m
0

jorg3lopez
2
4d 11h 2m
0

RickHawesUSDS
1
3d 8h 47m
2

rhood23699
1
15m
0

No longer needed.

Carlos Felix
Note that on of the primary reasons was to disable it due to the problems we get when deploying schema changes, but that has been fixed.  Not sure what other use cases this has right now.

If needs to be re-created, action JosiahSiegel/disable-azure-function is available.


Doubt about warnings by lua_ls

I had a doubt about why these warnings appear:

I have to clarify that the functionality works perfectly but since I am learning lua by tweaking neovim I wanted ask so that someone with more lua knowledge could share the know-how on the reason these warnings appear.

It's a lua LSP issue. Don't worry about it. Both get and has are valid fields.

Why do you open an issue for this? Sigh

Thanks @b0ae989c for the clarification.
Sorry @folke, at that time I didn't know discussions section was a thing.


Un wanted multi select

I have

and formtastic forces a multi select. How do I stop that?

Ok, have reproduced this bug with a test. Looking into it, sorry for the lag in responding.

Actually, I have a test that "proves" it should work:
  describe 'for a has_and_belongs_to_many association' do
    it 'should allow non-multi select with the :input_html option' do
      output_buffer.replace ''
      concat(semantic_form_for(@freds_post) do |builder|
        concat(builder.input(:authors, :as => :select, :input_html => { :multiple => false }))
      end)
      output_buffer.should_not have_tag('form li select[@multiple="multiple"]')
    end
  end

The logic was a bit smelly, and there weren't any tests for this case:
<%= f.input :pages, :as => :select, :multiple => false, :collection => pages.flatten %>

... so I've added two tests and some code changes to hopefully resolve this. I've committed them in a branch "GH-745", so please bundle in Formtastic from master with the `:git` option and use the branch name as the `:ref` option.

@cgunnels Please report back and confirm that this has resolved your problem, then I'll merge it into master.

This worked:
<%= f.input :pages, :as => :select, :input_html => { :size => 1 }, :multiple => false, :collection => pages.flatten %>

Ok, closing then.


View opportunity api changes done (#228)

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixed #228
Type of change
Please check options that are relevant to your PR.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] I have pulled the latest changes in the repository
[x] I have squashed my commits
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Good work @akshitakanojia. There are few minor changes -

There's another field opportunityOrganisation in JOBS and INTERNSHIP. Please use that for company name. You can use this Swagger Doc to verify fields for all opportunities.
Display date in this format: YYYY-MM-DD or DD-MM-YYYY

@vaishali614  I'm not able to access the link for swagger doc . Can you please check and tell the correct link.

Good work @akshitakanojia. There are few minor changes -

There's another field opportunityOrganisation in JOBS and INTERNSHIP. Please use that for company name. You can use this Swagger Doc to verify fields for all opportunities.
Display date in this format: YYYY-MM-DD or DD-MM-YYYY

@vaishali614 I'm not able to access the link for swagger doc . Can you please check and tell the correct link.

Please use this link: https://opportunity-calendar.herokuapp.com/playground/#/default/get_opportunity


Return API body as byte[]

To be honest I have no clue whether this helps or not - I am not a Spring guy, sorry


Add GNMT

Description
Reaches BLEU=25.80 after 8 epochs using beam_size=4. In tensorflow/nmt, the BLEU score is 26.1 using beam_size=10.
Checklist
Essentials

[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Hello, it seems that there is no reference about the paper in this page. Is it possible that you could add a reference so that it is easier for me to write the catalog page?
Thanks!
#1184

@StrayBird-ATSH https://arxiv.org/abs/1609.08144

Thanks a lot!
Do you want me to create a pull request for adding reference information to the website https://gluon-nlp.mxnet.io/model_zoo/machine_translation/index.html ?


Tabs inside Modal not highlighting entire Tab button

I have a <Tabs /> component inside a <Modal /> with 2 <Tab /> inside it. While all other components are loaded correctly, the <Tabs /> bar doesn't highlight all the bottom of the active <Tab /> button. See image below.

The component loaded inside each tab is part of a form implemented using react-native-ui-form-validator. I made little tests removing the <FormValidator />, but it didn't fix the problem.

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The highlight should be covering all tab button bottom line.
Current Behavior

The highlight doesn't cover all tab button bottom line, just getting part of it.
Your Environment

Tech
Version

Material-UI
v1.0.0-beta.45

React
16.3.2

browser
Chrome

Your issue has been closed because it does not conform to our issue requirements.
Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

Still happen to me.
Is there any workaround?

Duplicate of #9337


Normalize Table

Is your feature request related to a problem?
Normalization mean to shift and squeeze the data into the interval [0, 1]. More generally, we can do that for any interval [minimum, maximum].
Desired solution

Add a class RangeScaler in safeds.data.tabular.transformation that wraps the MinMaxScaler of scikit-learn
Make it a subclass of InvertibleTableTransformer
Add two parameters to the __init__ method to set the minimum (float, default 0.0) and maximum (float, default 1.0).
Raise a value error if minimum >= maximum.

:tada: This issue has been resolved in version 0.13.0 :tada:
The release is available on:

v0.13.0
GitHub release

Your semantic-release bot :package::rocket:


i18n(zh-cn): Update wordpress.mdx

Description (required)
Update wordpress.mdx

Related issues & labels (optional)

#7886

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/zh-cn/guides/cms/wordpress.mdx
Localization changed, will be marked as complete.
zh-cn

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


no libSDL2_image.a in the prebuilt SDL package.

I'm trying to use zsdl2_image module.
But the prebuilt SDL archive does not contain the library.
libSDL2.a and libSDL2_ttf.a are there but no libSDL2_image.a, which leads to link failure.

Sorry, my mistake. Added here: https://github.com/zig-gamedev/SDL2-prebuilt/commit/01ed17a8a2c85943be82fd9638212a1f1ab6f2b9

monorepo dependencies updated here: https://github.com/zig-gamedev/zig-gamedev/commit/2eec4b4b4bcbfe260e3bb367981a1151a73f7539


Instance should be latent if config isn't set

Until initial config is set, the system should consider instances LATENT

Fixed by pull/issue 6


VS Code Dark Mode - Designer Data/Expression Colors Very Poor Contrast

Describe the Bug with repro steps
When using a VS Code theme that is using a dark background, the color chosen to display the UI makes it impossible to see UI elements without moving the cursor over the element
What type of Logic App Is this happening in?
Standard (VSCode)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Not relevant

Screenshots or Videos

Browser
Edge
Additional context
Accessibility standard issue ?

@ccastrotrejo can you take a look?


feat(words): add datasheet and velarray

Use in https://github.com/autowarefoundation/autoware.universe/pull/1623

I'll fix check-deprecated-file-change. Close...


convertto-json command returns the wrong value in some cases

Steps to reproduce
file a.json
{
    "a": {
        "b": [
            {
                "c1": "str",
                "c2": []
            }
        ]
    }
}

get-content d:\a.json | ConvertFrom-Json |ConvertTo-Json
file b.json same problem.
{
    "a": {
        "b": [
            {
                "c1": "str",
                "c2": "abc"
            }
        ]
    }
}

Actual behavior
file a.json return is:
{
    "a":  {
              "b":  [
                        "@{c1=str; c2=System.Object[]}"
                    ]
          }
}

Expected behavior
remove "a",then return normal.
c.json
{
    "b": [
        {
            "c1": "str",
            "c2": []
        }
    ]
}

get-content d:\c.json | ConvertFrom-Json |ConvertTo-Json
return is:
{
  "b": [
    {
      "c1": "str",
      "c2": ""
    }
  ]
}

Environment data
win10 + powershell 5.1.14393.1066   tested,have this problem
win10 + powershell 5.1.15063.138    tested,have this problem
cenos 7.x + v6.0.0-alpha.18         tested,have this problem
Name                           Value

PSVersion                      6.0.0-alpha
PSEdition                      Core
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   <IP_ADDRESS>
GitCommitId                    v6.0.0-alpha.18
CLRVersion
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
reporter
By the chinese powershell study & research group. QQ group No. is 183173532
in 'vscode' or other open source project,in version release notes,bug reporter should be thank.
So I left a group name.

-Depth
Specifies how many levels of contained objects are included in the JSON representation. The default value is 2.
Increase the value of the default value,problem solved


feat(catalog): Add tile counters

Currently, when looking for a saga component, we see a Saga component, but there's also a Saga pattern and there's no visual feedback that it exists until we click on the Pattern toggle.
This PR adds counters to each toggle, so we can monitor the occurrences in other groups as well.
In addition to that, the lookup is debounced until the user stops writing, in a 500ms window. This helps when writing the first letters of the search term, it doesn't get stuck until the UI renders.
Screencast
https://github.com/KaotoIO/kaoto-next/assets/16512618/e10b5349-a301-436a-9358-f859398dd47d
fix: https://github.com/KaotoIO/kaoto-next/issues/745

Hi @lordrip, looking at the e2e failures, it seems there is an issue introduced by this PR. It's making it not possible to use filtering using tags:
https://github.com/KaotoIO/kaoto-next/assets/4180208/acc60cba-0c9c-41fd-abbc-0121f2438cab

Hi @lordrip, looking at the e2e failures, it seems there is an issue introduced by this PR. It's making it not possible to use filtering using tags:
vokoscreenNG-2024-02-27_08-50-52.mp4

It looks like just the first tag is honored, I'll check it out

cy.get('.pf-v5-c-text-input-group__text-input').should('have.value', '');

Thanks @tplevko, I've updated it according to your suggestion 💪


Clarification to Quickstart guide

For others that need things spelled out as much as I do :)

Thanks! 👍


Data Missing and crash

@TiagoMaiaL we are facing on issue, it would be great if you can help in same.

Habit selected dates data is missing on edit screen.
Another issue is getting crash while editing same habit multiple times.(reason: '*** Collection <__NSCFSet: 0x600003446ac0> was mutated while being enumerated.')

Kindly have a look on video
https://www.dropbox.com/s/awv5awdel0hm1et/Habit Calendar Issues.mov?dl=0

@TiagoMaiaL It would be great if you can have a look.

Hello,
I have plans to continue adding support and new features to this app, but unfortunately, I currently don't have enough time.
You guys are more than welcome to propose new features and solve these kinds of bugs if you wish. Just create a new PR with the description of the bug and issue you are solving and I'll carefully review it.
Thank you for your interest.
If you have any questions, don't hesitate in asking.

Hello,
I have plans to continue adding support and new features to this app, but unfortunately, I currently don't have enough time.
You guys are more than welcome to propose new features and solve these kinds of bugs if you wish. Just create a new PR with the description of the bug and issue you are solving and I'll carefully review it.
Thank you for your interest.
If you have any questions, don't hesitate in asking.

Just remember that in the case of a new feature, it's a good idea to propose and discuss it, before actually working on it.


Support for fasthttp.Client

Background
fasthttp is an alternative to Go's native net/http network library. It is written to be significantly more performant at scale; in some cases, it is ~10x faster than the standard library. It is used widely and is well-maintained.
Moreover, this project already have support for fasthttp handlers: issue & merged pull request.
The Ask
Therefore, it'd be helpful if aws-xray-sdk-go could work out-of-the-box with fasthttp client as well.
The client implementation is different enough to make it not trivial to use as-is.
Links
fasthttp
net/http-->fasthttp request adaptor

Hi @joanlopez - thanks for the feedback! We'd be happy to take a look at a PR for a new client instrumentation, however at this time we will not be able to add new instrumentations on our roadmap. We would recommend you check out the AWS Distro for OpenTelemetry Go, which provides first-class fasthttp support and support for the X-Ray backend! https://aws-otel.github.io/docs/getting-started/go-sdk

Alternatively, we would recommend you check out the AWS Distro for OpenTelemetry Go, which provides first-class fasthttp support and support for the X-Ray backend! https://aws-otel.github.io/docs/getting-started/go-sdk

Sure, sounds like a great alternative! :) Could you please point out to any code example / documentation page with examples or information about how to instrumentate the SDK with the fasthtt, please? Thanks!


Microsoft.CodeAnalysis in 5.0.100 source-built Razor SDK is newer than Microsoft-built copy

Microsoft.CodeAnalysis is also shipped with the Microsoft-built SDK:
$ tar tf ~/downloads/dotnet-sdk-5.0.100-linux-x64.tar.gz | grep Microsoft.CodeAnalysis.dll
./sdk/5.0.100/Sdks/Microsoft.NET.Sdk.Razor/tools/Microsoft.CodeAnalysis.dll
./sdk/5.0.100/Roslyn/bincore/Microsoft.CodeAnalysis.dll

I can't see the version of the bincore dll, but the Razor/tools version seems to be 3.7.0 (instead of 3.8.0) :disappointed:
$ exiftool ./sdk/5.0.100/Sdks/Microsoft.NET.Sdk.Razor/tools/Microsoft.CodeAnalysis.dll | grep -i version
ExifTool Version Number         : 12.00
Linker Version                  : 48.0
OS Version                      : 4.0
Image Version                   : 0.0
Subsystem Version               : 4.0
File Version Number             : 3.700.20.37502
Product Version Number          : <IP_ADDRESS>
File Version                    : 3.700.20.37502
Product Version                 : 3.7.0-6.20375.2+34202cc2f3e869fd70a26d8237f4552cf9e192cf
Assembly Version                : <IP_ADDRESS>

Originally posted by @omajid in https://github.com/dotnet/source-build/pull/1849#issuecomment-724068355

(In the source-built SDK, Roslyn is 3.8.0 including in Sdks/Microsoft.NET.Sdk.Razor/tools.)

Assuming we're building 3.8.0 for some valid reason, this could mean the Microsoft SDK is incoherent. It might be fine for us to replace 3.7.0 with 3.8.0 in this case. But maybe we don't have a valid reason for 3.8.0?

Actually, directly inspecting all Microsoft.CodeAnalysis.dll files present shows that the SDK has incoherent versions:
#> find . -iname 'Microsoft.CodeAnalysis.dll' -exec pwsh -c 'echo {}; [System.Reflection.AssemblyName]::GetAssemblyName("{}").Version.ToString()' \;
./sdk/5.0.100/Sdks/Microsoft.NET.Sdk.Razor/tools/Microsoft.CodeAnalysis.dll
<IP_ADDRESS>
./sdk/5.0.100/Roslyn/bincore/Microsoft.CodeAnalysis.dll
<IP_ADDRESS>

@JunTaoLuo, do you know if it's ok for source-build to use a 3.8.0 version at ./sdk/5.0.100/Sdks/Microsoft.NET.Sdk.Razor/tools/Microsoft.CodeAnalysis.dll rather than 3.7.0? Is the incoherency in Microsoft.NET.Sdk.Razor expected?
Is this something that should be fixed in 5.0 servicing in the Microsoft build to make it more coherent?

#> find . -iname 'Microsoft.CodeAnalysis.dll' -exec pwsh -c 'echo {}; [System.Reflection.AssemblyName]::GetAssemblyName("{}").Version.ToString()' \;
./sdk/5.0.100/Sdks/Microsoft.NET.Sdk.Razor/tools/Microsoft.CodeAnalysis.dll
<IP_ADDRESS>
./sdk/5.0.100/Roslyn/bincore/Microsoft.CodeAnalysis.dll
<IP_ADDRESS>

@mmitche, maybe you have some broader context over whether that incoherency is expected in the 5.0 SDK, if it's ok for source-build to use 3.8.0 in both cases?

Triage: @JunTaoLuo, @mmitche, any thoughts on this?

Filed https://github.com/dotnet/aspnetcore/issues/28096 to figure out what the next steps are.

In https://github.com/dotnet/aspnetcore/issues/28096 it's confirmed that using 3.8.0 in both places is fine. Closing.
There's a PR proposed for 5.0.1 to update the Microsoft build to use 3.8.0 in both places there, too.
In the future, when we start building multiple SDK bands, we may get incoherent again due to the nature of building an SDK tool inside a Runtime repo like aspnetcore. More details: https://github.com/dotnet/aspnetcore/issues/28096#issuecomment-733218190


cclient: added logger.

This PR fixed #222
Test Plan:
CI must pass

the compiler will tell you if it has overlap. before this modification, we don't know where it is.


UX Discovery Sessions - Andrew & Jamie

Title of ticket: UX Discovery Sessions - Andrew & Jamie
Description
Two sessions, with Andrew & Jamie to watch current process for creating reports and get feedback on what they think is required info to share vs not
Dependencies
Are there any dependencies?
DOD

[x] Book Session with Andrew & Jamie - @arielleandrews
[x] Session with Andrew
[x] Create User Flows based off of Andrew's Process and current Pain Points
[x] Session with Jamie
[x] Create User Flow based on Jamie's Process and current Pain Points

@arielleandrews Added booking in the two sessions with Andrew and Jamie into the DOD of this ticket. In thinking that Dec 1st is also the big IAO meeting - would it be a bad idea to take more hours on the day to have Andrew walk me through things? Not sure just wanted to ask here in knowing that they are both very busy

Sessions booked as follows:

Andrew - Wednesday December 1st 1PM-3PM PST
Jamie - Friday December 3rd 11AM-12PM PST

Session 1 Recording
https://bcgov.sharepoint.com/:v:/r/teams/03521/Shared Documents/General/User Research/1 - Sprint 14 - Recordings/Session 1 - Andrew Bonneau - Process Walk-though Reporting.mp4?csf=1&web=1&e=vT94sJ

Session 2 Recording
https://bcgov.sharepoint.com/:v:/r/teams/03521/Shared Documents/General/User Research/1 - Sprint 14 - Recordings/Session 2 - Jamie Onciul - Pain Points %26 Feedback.mp4?csf=1&web=1&e=id0TsD

All sessions are complete


Enabling spellcheck GitHub Action

Hi,
This is a first shot at a configuration.
I corrected a few spelling mistakes. You should review the candidates in the local dictionary if there are more.
The configuration has been tested locally, but not the action, it will be tested via this PR.
Let me know if there are any challenges or questions to the PR.
Closes #2

Any chance of the getting reviewed?

I will be removing the Docker image for version 0.24.0 from DockerHub soon, so please consider getting this merged or your action updated.
Do note version 0.32.0 was a recommended security update.
REF:

https://github.com/rojopolis/spellcheck-github-actions/blob/master/CHANGELOG.md#0320-2023-05-18-security-patch-release-update-recommended


[Enhancement]: Contributors guideline needs some update

Do you want to have the enhancement of existing game ? 😀 Describe yourself..

At present new games gets added to the project but not to website .
some contributors don't add things to dedicated folders , and many don't follow naming conventions

Describe the solution you'd like

I would like to update contributors guideline so that new game contributors add their games to website and also add more precise details so that contributors add things properly and follow proper naming conventions

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @mohitgedar !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @mohitgedar ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


action: enable gofmt lint; fix dupword.go formatting

The PR fixes formatting in dupword.go by running go fmt ./.... Additionally, enables gofmt linter to prevent formatting issues in the future.

Thanks @alexandear


Destination branch for pull requests?

What about updating the PULL_REQUEST_TEMPLATE file, adding instructions about which branch the pull requests should be created against?

Sounds intriguing. We'd probably have to keep updating though – unless we just wanted to make it generic

I think the way git flow is supposed to work is we keep all 0.0.X patch changes on the develop branch. If we have larger changes that aren't meant for a patch release we use a feature branch and only merge that in when develop is reflecting 0.X.0 changes.
If develop is reflecting 0.X.0 and we need to make an 0.0.X patch release, we check out the tag that we want and create a new release branch.
Ideally we should only have release branches when we are preparing to release. Once the release goes out we delete the branch and continue working out of dev or the appropriate feature branch.
This might be a good opportunity to revisit how we're using gitflow and adjust so that we're closer to what's intended now that we have some working experience with it.


cargo generate command does nothing, maybe related to zlib1.dll?

Describe the bug
When I ran a cargo generate command on Windows PowerShell, it exited immediately with no console or file output.
Similarly, cargo help generate or cargo generate --version also terminated without any output.
make sure you

[x] I'm on the latest rust version rustup update
[x] I'm on the latest cargo-generate version cargo install cargo-generate

To Reproduce
Steps to reproduce the behavior:

cargo generate --git https://github.com/esp-rs/esp-idf-template cargo
output it generated.. : nothing
See error

Expected behavior
I expected it asks project name, settings, etc. and create a directory containing a new Rust project.
Screenshots

Desktop (please complete the following information):

OS: Windows 11 Home
Version: 21H2
Build tools: msvc
Shell: powerShell
rustc --version: rustc 1.65.0 (897e37553 2022-11-02)
cargo generate --version: Nothing was displayed. Version was v0.17.3.

Additional context
For your information, when I checked DLL dependencies of cargo-generate.exe binary with Dependencies (Windows equivalent of ldd), zlib1.dll, which cargo-generate.exe depends, was not found in the system.
Double-clicking the exe file on the Explorer showed an error that zlib1.dll was not found.
As a workaround, building zlib and putting the resultant DLL along with cargo-generate.exe as zlib1.dll fixes the problem. However, it seems weird.

@tana this seems to be an old known and also fixed cargo issue rust-lang/cargo/issues/3415
Maybe you can try a rustup update?
Could you also fire a cargo --version to see if that at least would work (without the .ddl placement in the same folder)

Thank you for your reply. I didn't thought it was a problem of Cargo.
I ran rustup update but cargo-generate --version still displays nothing (without DLL workaround).
cargo --version succeeded even before rustup update.
It displayed cargo 1.66.0 (d65d197ad 2022-11-15). I think this is quite recent version.

I meet the same error, check the dependencies and found that it's missing zlib1.dll.
I just copy a zlib1.dll with version <IP_ADDRESS> from my vcpkg folder, then the generate could work.

I suspect this is a duplicate of #984
The solution that worked there was:

I resolved the issue. After re-installing the zlib library and add them into the path, I also did a restart of my mac. Now the library is linked and cargo generate does not have issue anymore.


[Toolkit feature]: Add Github Actions to toolkit-remix

Contact Details (Optional)
No response
What is the context of the feature/improvement?
This would allow us to easily test the new toolkit versions and report back on new features or report bugs.
Currently most users are not equipped to build the toolkit on their own PC.
Please describe the feature/improvement?
Update the build-windows.yml workflow file in the toolkit-remix repository to allow building the toolkit.
What would be your solution? (optional)
I have put together a (very janky) build workflow here:
https://github.com/Kim2091/toolkit-remix/blob/main/.github/workflows/build-windows.yml
Currently it fails on building code related to the GPU, as GitHub's actions VMs do not have CUDA supported GPUs.
Removing this code allows it to progress, but of course breaks it: https://github.com/Kim2091/toolkit-remix/commit/6d63919384c4189c61e386d03651252ec9943bfb
Version
202x.x.x
Media
No response

REMIX-3651 for tracking


Streams jerking with WebRTC and HLS

In my tests I found that MSE works very well. Unfortunately, I can't say the same for WebRTC and HLS, the streams stop every few seconds. Are there any tweaks that can be applied here? For example, higher buffer etc.?

This is very strange, but is there any error in the logs? Perhaps the player is not sending a keep-alive request?

This is very strange, but is there any error in the logs? Perhaps the player is not sending a keep-alive request?

I get the following error messages in debug mode for an encoder:
2021/02/11 09:59:30 [Unsuported Intervaled data packet 1 [8 24 97 32 128 32 82 35 0 0 48 201 0 238 49 130 129 202 0 9 55 88 197 191 1 29 86 117 83 116 114 101 97 109 49 53 48 45 48 50 58 48 54 58 48 53 58 49 100 58 48 48 58 50 50 0]]
2021/02/11 09:59:30 [Unsupported NAL Type 6]
Do you have any idea what the problem is?

no problem, disable debug
nal -> 6 | Supplemental enhancement information (SEI)sei_rbsp( ) | 5 | non-VCL | non-VCL | non-VCL
no need for play


NPM install 404 error

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'i',
1 verbose cli   '@recogito/annotorious'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose npm-session a855050a092fed1a
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 404 https://registry.npmjs.org/@recogito%2fannotorious 731ms
8 http fetch GET 404 https://registry.npmjs.org/@recogito%2fannotorious 140ms
9 silly fetchPackageMetaData error for @recogito/annotorious@latest 404 Not Found - GET https://registry.npmjs.org/@recogito%2fannotorious - Not found
10 timing stage:rollbackFailedOptional Completed in 1ms
11 timing stage:runTopLevelLifecycles Completed in 19512ms
12 verbose stack Error: 404 Not Found - GET https://registry.npmjs.org/@recogito%2fannotorious - Not found
12 verbose stack     at C:\nvm\v12.0.0\node_modules\npm\node_modules\npm-registry-fetch\check-response.js:104:15
12 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:88:5)
13 verbose statusCode 404
14 verbose pkgid @recogito/annotorious@latest
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "@recogito/annotorious"
18 verbose node v12.0.0
19 verbose npm  v6.9.0
20 error code E404
21 error 404 Not Found - GET https://registry.npmjs.org/@recogito%2fannotorious - Not found
22 error 404
23 error 404 '@recogito/annotorious@latest' is not in the npm registry.
24 error 404 You should bug the author to publish it (or use the name yourself!)
25 error 404 Note that you can also install from a
26 error 404 tarball, folder, http url, or git url.
27 verbose exit [ 1, true ]

Hi,
hm - that's weird. Might be a temporary problem with the NPM registry. I'll check back later and see if the problem persists. If it does, I'll try publishing a new version... thanks for letting me know!

Hi again,
I tried again just now and it worked for me this time. Can you check once more?

still the same
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@recogito%2fannotorious - Not found
npm ERR! 404
npm ERR! 404  '@recogito/annotorious@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@recogito%2fannotorious - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

Can you post the OS and node/npm versions you are using?

I just got this working on Linux (Ubuntu), using node v14.5.0 and npm 6.14.5
$ npm install --save @recogito/annotorious
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>updated 1 package and audited 43 packages in 5.156s
found 0 vulnerabilities

simonr@N3IM1806L:~/foo$ npm install --save @recogito/annotorious
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>updated 1 package and audited 43 packages in 2.935s
found 0 vulnerabilities

^^
could be registry issue?
Node: v12.0.0
NPM: 6.9.0
Windows 10

Ok, those node/npm versions definitely look ok. Weird - I can open http://registry.npmjs.org/@recogito/annotorious on my end of the world (Austria) just fine.
Puzzled... I can only guess that it might indeed be some temporary network problems on the side of the registry and its mirrors.

Seems so it's working now :)


The isolate scope prevents the directive from correctly reading the options from the scope

Hi,
Sorry about the long title, but creating an isolated scope prevents scope.$eval() from getting the options from the controller scope. You can safely remove the isolated scope.

Sorry for the delay, I was busy on other projects.
Can you post an example to check it? I tested on the example.html file and worked correctly.

No worries :)
          datetimepickerOptions: '@'
}```

This means that inside the HTML you MUST interpolate the object `datetimepicker-options="{{ myScopeOptions }}"` and serialize it inside the DOM attribute.

I think it's better to have it evaluated as an expression (&) inside the isolated scope, bidirectionally bound (=) if you try to change the options after the datepicker has been initialized, or even remove the isolated scope altogether since it's not needed right now.

This is more of a design preference, not an issue :) I realized how the directive works after looking through the code. I was simply using `datetimepicker-options="myScopeOptions"` and that didn't work with `scope.$eval`.


Documentation

This should provide documentation and a readthedocs page, but I think that we might still need a few things before this is complete:

Code review, obviously.
A certified dask domain (e.g., dask-mpi.dask.org? or mpi.dask.org?) which will require some help from the Dask team (@mrocklin?)

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   93.49%   93.49%
=======================================
  Files           4        4
  Lines         123      123
=======================================
  Hits          115      115
  Misses          8        8

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 ede7b41...2389d7e. Read the comment docs.

Lets get this up smoothly on dask-mpi.readthedocs.io first, and then we'll ask NumFOCUS to reroute things accordingly.  Also, I encourage you to use the Dask Sphinx theme.  See instructions in the README here: https://github.com/dask/dask-sphinx-theme

@mrocklin Sounds good.  It's currently building the docs for master (failing, because this PR hasn't gone in, yet) and the documentation branch, which is passing.  So, I'm going to merge this in.

Closes #8


Fix dropped ingress packets in azure

[!warning]
This is a public repository, ensure not to disclose:

[ ] personal data beyond what is necessary for interacting with this pull request, nor
[ ] business confidential information, such as customer names.

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[x] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

This PR fixes the problem with dropped ingress packets to the ingress nginx on azure, it also enables preserving the source IP of incoming traffic.

Fixes https://github.com/elastisys/ck8s-issue-tracker/issues/250

Information to reviewers

Checklist

[ ] Proper commit message prefix on all commits

Change checks:

[ ] The change is transparent
[ ] The change is disruptive
[ ] The change requires no migration steps
[ ] The change requires migration steps
[ ] The change upgrades CRDs

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packets in the NetworkPolicy Dashboard

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Bug checks:

[ ] The bug fix is covered by regression tests

Config checks:

[ ] The schema was updated

For whitelist-source-range it was there in the common-config by default, i don't have a clear idea if it is needed or not.
The network policies that does look very weird, did that happen after you did the init? i don't remember touching anything there to make it behave like that. running a diff doesn't show that.
allocateLoadBalancerNodePorts to use direct routing from load balancer and fix the NetworkPolicies issue, which gave the opportunity to run externalTrafficPolicy and preserve the source IP

allocateLoadBalancerNodePorts to use direct routing from load balancer and fix the NetworkPolicies issue

Are you sure this is supported by Azure? I think it uses node ports for the health probes.

Note that disabling node port allocation does not also automatically remove the node ports: https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-nodeport-allocation
This means that even though you set it to false and applies it on an existing cluster it will not take effect.

allocateLoadBalancerNodePorts to use direct routing from load balancer and fix the NetworkPolicies issue

Are you sure this is supported by Azure? I think it uses node ports for the health probes.

It creates a specific port for health checks.

Note that disabling node port allocation does not also automatically remove the node ports: https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-nodeport-allocation
This means that even though you set it to false and applies it on an existing cluster it will not take effect.

Yeah, i completely removed and then reapplied ingress-nginx so that the new load balancers get created without them.


feat: support session persistence in HTTPRouteRule

What type of PR is this?

What this PR does / why we need it:
support session persistence in HTTPRouteRule.
Which issue(s) this PR fixes:

Fixes #3315
Ref https://github.com/envoyproxy/gateway/issues/2624#issuecomment-2047564216
GEP: https://gateway-api.sigs.k8s.io/geps/gep-1619/

Done. Addressed the points from @zhaohuabing and added the e2e test.

/retest

I just rebased to resolve the conflict.
Who should I ask the second review path?

I just rebased to resolve the conflict.
Who should I ask the second review path?

that will be me 🙈 , sorry for the delay, will review this today

No worries, just wanted to ensure it's not missed.
Thanks!

@arkodg I updated based on your suggestions.

thanks @sanposhiho, one comment on naming the session, else LGTM !

@arkodg Addressed your point + rebased for a conflict.

/retest

@zirain Updated based on your points.


Deploy

This is an automatically generated release PR!

I know that there were some chatter with Force's test suite, so going to re-assign to @damassi who will probably have more context on whether Force is deployable.


Only set Vol AttachmentState if not set by driver

@akutz Since another RC is in the works for 0.3.3, I wonder if you'd consider this patch. Per our previous conversations, types.VolumeAttachmentStateUnknown is available to drivers in order to indicate that a volume's state is truly unknown or cannot be determined. This is a feature I am using. But I noticed today that if an AttachmentState is set by the driver, it is always overriden by the framework. I don't think that's what we wanted. So this patch wraps that bit of code in an if statement to only figure one out if AttachmentState is 0, meaning that it hasn't been set by a driver. Let me know what you think.

The framework can automatically set a volume's attachment state, but
a driver can also explicitly set it to "unknown" -- something that
only a driver can determine. That driver-set value was always
being overriden by the framework.

This patch makes it so that the framework only determines attachment
state if a driver has not already set a value.

@akutz That is indeed much cleaner. I've pushed the change. Thanks!


Update thingtalk dependency

When you edit package.json you also need to run npm install to update package-lock.json, and commit that too, otherwise the change won't have any effect.


faster-whisper vs whisper.cpp with CoreML

@guillaumekln Hello! I am developing a real-time ASR running on both Mac OS and Windows, is faster-whisper faster than whisper.cpp with CoreML support on Mac OS?

different hardware, no comparison. I am using faster-whipser on a 1070ti. about 500ms for large-v2 for a  everyday sentence, very nice for me.

Hi,
I don’t have access to a Mac at this time so hopefully someone else can share some insights.
If someone runs a comparison, make sure to compare with equivalent options.
Here are the options to match the default values in<EMAIL_ADDRESS>model.transcribe(
    audio,
    language="en",
    beam_size=1,
    best_of=2,
    temperature=[0.0, 0.4, 0.8],
    suppress_tokens=None,
)

I measured it with whiper.cpp sample audio, gb1.wav (198.7 sec)
Tested on M2 air 8GB, measured twice pick smaller.

type
tiny
base
small
medium
large-v2

faster-whisper fp32
3.80
7.38
20.53
59.42
245.96

faster-whisper int8
3.78
7.00
20.05
63.17
113.03

whisper.cpp CPU
2.73
4.68
14.69
42.86
78.62

whisper.cpp ANE
1.79
3.18
8.53
23.88
51.01

Thank you for these results!
It might also be interesting to get some numbers for a larger beam size (the Whisper paper recommends 5).
One thing we should improve in Apple Silicon builds is multi threading. For example the fp32 run is always using a single core at the moment.
See this issue https://github.com/OpenNMT/CTranslate2/issues/1137 where some users tried to compile CTranslate2 with OpenMP on macOS ARM64.
I will update this thread if we have something new.

I just released ctranslate2==3.13.0 which includes some multithreading improvements on Apple Silicon.
@neurostar Could you renew the benchmark when you have some time? I also suggest to disable the "temperature fallback" to prevent any irregular transcription time.
./main --file gb1.wav --language en --threads 8 --no-fallback --beam-size 1

import faster_whisper

model = faster_whisper.WhisperModel(..., device="cpu", cpu_threads=8, compute_type="float32")

segments, _ = model.transcribe(
    "gb1.wav",
    language="en",
    beam_size=1,
    temperature=0,
    suppress_tokens=None,
)
segments = list(segments)

Would be cool to also get the results for a beam size of 5.
Thanks!

The same gb1.wav used as previously.
These are --no-fallback --beam-size 1 and --beam-size 5
Since M2 Air 8G was swapping memory for large fp32 (~6.4GB, short peak at 11.3GB),  I did not include fp32 large.
I used 4 threads, the regular M2 have only 4 P cores, 8 threads is not performing well.
There is one faster-whisper 0.51 int8 bs5 t8 with 8 thread for reference.
There seem to be better performance of 0.51 with bs1 but worse with bs5.
The previous measures on faster-whisper did not include model loading time.
This include model loading time for all.
whisper.cpp ANE ran twice because some kind of caching happen when model is loaded first time which increase model loading time significantly. The subsequent loading of same model have normal model loading time.
whisper.cpp ANE only encoder part is running in ANE due to decoder is slower in ANE, so the bs5 setting significantly increase total time. faster-whisper 0.51 int8 bs5 is faster than whisper.cpp ANE bs5.

type
tiny
base
small
medium
large-v2

faster-whisper 0.41 fp32 bs1
4.10
7.93
21.25
61.12
x

faster-whisper 0.51 fp32 bs1
4.59
8.30
22.30
59.32
x

faster-whisper 0.41 int8 bs1
4.08
7.61
21.99
62.61
118.52

faster-whisper 0.51 int8 bs1
4.03
7.07
19.89
57.32
105.56

faster-whisper 0.41 fp32 bs5
7.21
16.20
43.40
125.47
x

faster-whisper 0.51 fp32 bs5
10.68
24.63
63.81
137.22
x

faster-whisper 0.41 int8 bs5
5.23
10.38
27.07
78.70
177.39

faster-whisper 0.51 int8 bs5
6.81
13.16
31.74
86.75
175.17

faster-whisper 0.51 int8 bs5 t8
9.11
15.16
36.43
98.19
205.31

whisper.cpp CPU bs1
2.68
4.73
15.18
50.11
90.34

whisper.cpp ANE bs1
1.74
2.80
8.09
22.81
57.28

whisper.cpp CPU bs5
7.19
12.42
39.26
108.66
217.79

whisper.cpp ANE bs5
6.19
10.51
29.49
78.37
179.60

Thanks for all these numbers.
The next step for us is to explore FP16 execution on the CPU which could improve performance on ARM CPUs: https://github.com/OpenNMT/CTranslate2/issues/1153


consider pie for plugins

see https://github.com/natefinch/pie
Instead of compiling-in plugins, you could use pie to run executable plugins using RPC over stdin/stdout of the plugin executable.  Far more flexible than making people compile things in, they could just be dropped in place, and they can be written in any language.

Thanks for the link. I'll investigate when I get the chance.
But it's not clear to me: how would using pie be different from the current  behaviour of invoking selected text with os.exec/Command on middle click and inserting it into the buffer?

I think the main reason neovim switched to this sort of plugin arch is to allow more metadata to be passed to the plugin along with merely selected-text-as-stdin, and more structured responses than stderr & stdout.
The canonical argument against the naive plugins is what inspired jwz's famous:

Some people, when confronted with a problem, think “I know, I'll use regular expressions.” Now they have two problems.

I don't have anything particularly against pie to achieve this, but I'd rather work to support something like acme's fs api (or the neovim nvimfs inspired by it). Or investigate the msgpack rpc that neovim is developing so we can reuse their plugins. Of course for all I know, just swapping the gob codec for msgpack would let us use nvim plugins.
Regardless, I'd like not to use the gob codec at all, because then it'll be unnecessarily tedious to write plugins in anything than go. And if you're writing the plugin in go, it's hard to argue that there's any reason not to compile it in.

Note that pie supports whatever codec you want for RPC.  You just use the *Codec function (such as StartProviderCodec) and pass in the function that creates the codec, so like here:
client, err := pie.StartProviderCodec(jsonrpc.NewClientCodec, os.Stderr, path)

StartproviderCodec takes in a func(conn io.ReadWriteCloser) rpc.ClientCodec so in theory you can use whatever encoding you like.  There's an example python plugin doing json rpc here: https://github.com/natefinch/pie/blob/master/examples/python-plugin/plugin.py

Okay, I've finally had a chance to look into this a little more now that the basic functionality of de is getting closer to having everything I need.
My concern with this has always been that from my understanding using pie for plugins would require:

Designing an RPC mechanism for plugins and doing a good enough job of it that it would be stable and not constantly breaking other plugins with changes
Documenting it well enough that third parties can use it without too much difficulty.
Implementing it.

Step 3 was never a problem for me, I was concerned about the significant work of steps 1 and 2 for only the theoretical advantage of it being a better architecture where plugins would still be tied to de.
Now that I've looked into it, I think those concerns can be sidestepped by using pie to implement support for the neovim plugin architecture, which would neatly sidestep my first issue and have the significant benefit of increasing the number of plugins that are available instantly.
Since I'm not sure if this plan will work and the neovim plugin plugin is probably going to be fairly complex and experimental at first, I might try it in another repo, but that's my current plan.
If anyone has any neovim plugin examples (preferably simple ones) that they'd like me to try, let me know.

go 1.8 officially supports plugins:
https://golang.org/pkg/plugin/

See my second comment in #40 for the problem with using the go 1.8 plugins. The fact that they're Linux-only is a fairly major stumbling block for me.
Since I've obviously been slacking off on this front, if anyone wants to look into adding Go 1.8 style plugins they may want to start by looking into github.com/sbinet/plugs as a method to build/load them.


Saving java.util.Date Date does not work properly

Saving java.util.Date Date does not work properly.
I tried setting a new Date in my Date variable:
@PropertyDescription(initial = true)
private Date case_startDate;
public void setCase_startDate(Date case_startDate) {
        this.case_startDate = case_startDate;
}
setCase_startDate(new Date());
After several nodes i tried using it via pool:
NumberCreatePool pool = getContext().getPool();
pool.getCase_startDate();
and that is null.
Can you please verify this error and try to fix it. thx :)
+++ Current workaround is to safe the date in a String variable an use it with:
MDate.toDate(pool.getCase_startDateStr(), new Date())

Fixed! Also fixed ENUM values (must have exact spelling, e.g. in upper case)


[staging & production] Public User Profile name obscured on mobile site

When viewing public user profiles on mobile devices the top line of information is cut off.

Occurs for iphone 5 and 4
Also, the 'edit profile' link is obscured using Nexus 4 mimicking, if you have a longer last name with descenders.

This occurs on the full site as well, if you put a long enough name.

Reopening the issue: Fixed in Mobile but not in full site. @ticklemepierce ? Want to carry over that fix? Thanks.

@jinluyuan @lbanner Should be fixed from https://github.com/CenterForOpenScience/osf.io/pull/2806

Alright -- looks like #2806 forecast release w/0.39.0 today -- We'll test on Production post release, @jinluyuan

@ticklemepierce Looks good

Fixed in #2806


Update style.js for FAQ

A small change in UI for the FAQItem

Hey! Thank you for the PR but this provides no significant benefit for the webpage. + and - do the job of conveying the message clearly and let's keep it that way since this new update doesn't look too aesthetically pleasing as well.


NPM WARN Unsupported platform for<EMAIL_ADDRESS> ?

Versions
<!--
Output from: `ng v1.5.2`.
 output from: `node v8.9.1` and  `npm v5.5.1`.
  Windows 7
-->

Repro steps

Step 1 : npm install -g @angular/cli
Step 2 : NPM WARN Unsupported platform for<EMAIL_ADDRESS>Step 3

Observed behavior
<!--
<img width="726" alt="capture" src="https://user-images.githubusercontent.com/25393048/33001076-4524761c-cdde-11e7-96c3-868dc979ac46.PNG">
 -->

Desired behavior

Mention any other details that might be useful (optional)

You can ignore this warning. fs-events is required on macOS

Closing as answered by @danielsogl, thanks!

adding this to package.json solved the problem for me
 "optionalDependencies": {
    "fsevents": "*"
  }

not acceptable for me. See how yarn handle this:
yarn install v1.15.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.


Typo on p5.dom.js reference page

Hi,
Just found a small typo on the p5.dom.js reference page (extra square bracket).

Cheers.

thanks! the fix has been made to the documentation source code that this page is generated from. the corrected version will appear as soon as an updated version of the docs is pushed to the site.


Error installing Empress

Hello
I am trying to install empress into qiime2 2021.11 on Windows 10 WSL (Ubuntu 20.04.3 LTS (GNU/Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)), versions attached. I have attached a copy of the full error below. The rest of Qiime2 works fine for me.
Any help is appreciated.
Oliver
Empress Error.txt
Versions.txt

Hi @OliverAshton1,
Thanks for the detailed report. I just checked, and was able to install Empress using pip into a new QIIME 2 2021.11 environment (with the same software versions as you've listed in Versions.txt) on a Linux computer. This, together with the exact error message you got, implies that things are going wrong when installing the iow library into your system.
The origin of the installation error seems to occur when trying to build one of iow's dependencies (line 81 of your error message file):
  ar -csru libbitarr.a bit_array.o
  make: ar: No such file or directory
  make: *** [Makefile:25: libbitarr.a] Error 127

From what I can tell, the reason you're running into this problem is that the ar command (which creates / extracts certain types of archives) is not installed on your system (and it looks like it is installed on my Linux system already, so this would explain why I don't encounter this problem when installing Empress).
It seems like ar is part of the binutils package, so I think that installing binutils should then allow you to install Empress. Long story short, could you please try installing binutils? I'm not very familiar with WSL, but from some googling I think something like
sudo apt-get install binutils

should do the trick.
Let us know if this works out!

Hi @fedarko
As you recommended I used:
conda activate qiime2-2021.11
sudo apt-get install binutils
pip install empress
qiime dev refresh-cache
qiime empress --help

Empress then installed first time, on both my PCs that showed the error.
Many thanks for your quick reply!
Oliver

Fantastic, thanks @OliverAshton1! Glad that worked.
I just created a new issue (#553): we'll add this information to EMPress' documentation to help other people who run into this problem in the future, since I imagine that other WSL users may also encounter this.