Build failure: cargo-pgrx

I was attempting to build pgvecto-rs 0.2.1 which relies on cargo-pgrx, and hit a build failure on https://github.com/NixOS/nixpkgs/commit/e9ee548d90ff586a6471b4ae80ae9cfcbceb3420 (nixos-unstable via flakes). I add pgvecto-rs to my system flake in this line.
Steps To Reproduce
Steps to reproduce the behavior:

build pgvectors-0.2.1
Run into a rust compilation failure of the std_detect crate while building cargo-pgrx, which pgvectors-0.2.1 relies on.

Build log

Click to view logs
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/2jd1xa3isz1d74pq6if0zmh7lsi3zbx5-source
source root is source
Executing cargoSetupPostUnpackHook
Finished cargoSetupPostUnpackHook
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
applying patch /nix/store/l31pik55kdjixyfs7dad61hqgsqqmvj1-0001-read-clang-flags-from-environment.diff
patching file crates/c/build.rs
Hunk #1 succeeded at 1 with fuzz 1.
Executing cargoSetupPostPatchHook
Validating consistency between /build/source/Cargo.lock and /build/cargo-vendor-dir/Cargo.lock
Finished cargoSetupPostPatchHook
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
@nix { "action": "setPhase", "phase": "buildPhase" }
Running phase: buildPhase
Executing cargo-pgrx buildPhase
   Validating /nix/store/7wy8v3sjqiqy6bw75rymgshrsp8cllqs-postgresql-14.12/bin/pg_config
 Initializing data directory at /build/tmp.poc6yAMXrY/data-14
waiting for server to start....2024-06-15 20:13:27.382 GMT [74] LOG:  starting PostgreSQL 14.12 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 13.3.0, 64-bit
2024-06-15 20:13:27.382 GMT [74] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2024-06-15 20:13:27.383 GMT [74] LOG:  listening on Unix socket "/build/tmp.S6BpGEK97x/.s.PGSQL.5432"
2024-06-15 20:13:27.385 GMT [75] LOG:  database system was shut down at 2024-06-15 20:13:27 GMT
2024-06-15 20:13:27.387 GMT [74] LOG:  database system is ready to accept connections
 done
server started
2024-06-15 20:13:27.482 GMT [83] ERROR:  role "nixbld" already exists
2024-06-15 20:13:27.482 GMT [83] STATEMENT:  CREATE ROLE nixbld SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;
createuser: error: creation of new role failed: ERROR:  role "nixbld" already exists
waiting for server to shut down....2024-06-15 20:13:27.483 GMT [74] LOG:  received fast shutdown request
2024-06-15 20:13:27.486 GMT [74] LOG:  aborting any active transactions
2024-06-15 20:13:27.487 GMT [74] LOG:  background worker "logical replication launcher" (PID 81) exited with exit code 1
2024-06-15 20:13:27.487 GMT [76] LOG:  shutting down
2024-06-15 20:13:27.497 GMT [74] LOG:  database system is shut down
 done
server stopped
warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
       Using PgConfig("pg14") and `pg_config` from /nix/store/7wy8v3sjqiqy6bw75rymgshrsp8cllqs-postgresql-14.12/bin/pg_config
    Building extension with features  pg14
     Running command "/nix/store/qyw7qc22j2ngf9wip8sxagaxb0387gnq-cargo-1.78.0/bin/.cargo-wrapped" "build" "--release" "--features" " pg14" "--no-default-features" "--message-format=json-render-diagnostics" "--frozen" "-j" "8"
warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
   Compiling proc-macro2 v1.0.71
   Compiling unicode-ident v1.0.12
   Compiling libc v0.2.151
   Compiling cfg-if v1.0.0
   Compiling serde v1.0.193
   Compiling autocfg v1.1.0
   Compiling memchr v2.7.1
   Compiling syn v1.0.109
   Compiling thiserror v1.0.52
   Compiling scopeguard v1.2.0
   Compiling serde_json v1.0.108
   Compiling hashbrown v0.14.3
   Compiling lock_api v0.4.11
   Compiling eyre v0.6.11
   Compiling equivalent v1.0.1
   Compiling regex-syntax v0.8.2
   Compiling aho-corasick v1.1.2
   Compiling crossbeam-utils v0.8.18
   Compiling quote v1.0.33
   Compiling cc v1.0.83
   Compiling syn v2.0.43
   Compiling getrandom v0.2.11
   Compiling indexmap v2.1.0
   Compiling version_check v0.9.4
   Compiling tinyvec_macros v0.1.1
   Compiling glob v0.3.1
   Compiling tinyvec v1.6.0
   Compiling clang-sys v1.6.1
   Compiling regex-automata v0.4.3
   Compiling ring v0.17.7
   Compiling spin v0.9.8
   Compiling lazy_static v1.4.0
   Compiling ucd-trie v0.1.6
   Compiling once_cell v1.19.0
   Compiling winnow v0.5.31
   Compiling indenter v0.3.3
   Compiling anyhow v1.0.77
   Compiling unicode-normalization v0.1.22
   Compiling unicode-bidi v0.3.14
   Compiling minimal-lexical v0.2.1
   Compiling regex v1.10.2
   Compiling option-ext v0.2.0
   Compiling target-features v0.1.5
   Compiling percent-encoding v2.3.1
   Compiling semver v1.0.20
   Compiling libloading v0.7.4
   Compiling form_urlencoded v1.2.1
   Compiling idna v0.5.0
   Compiling dirs-sys v0.4.1
   Compiling nom v7.1.3
   Compiling proc-macro-error-attr v1.0.4
   Compiling bitflags v2.4.1
   Compiling crc32fast v1.3.2
   Compiling itoa v1.0.10
   Compiling ryu v1.0.16
   Compiling untrusted v0.9.0
   Compiling rustix v0.38.28
   Compiling serde_derive v1.0.193
   Compiling thiserror-impl v1.0.52
   Compiling bindgen v0.68.1
   Compiling cexpr v0.6.0
   Compiling pathsearch v0.2.0
   Compiling url v2.5.0
   Compiling dirs v5.0.1
   Compiling pest v2.7.5
   Compiling crossbeam-epoch v0.9.17
   Compiling proc-macro-error v1.0.4
   Compiling memoffset v0.9.0
   Compiling linux-raw-sys v0.4.12
   Compiling semver-parser v0.10.2
   Compiling semver v0.11.0
   Compiling lazycell v1.3.0
   Compiling fixedbitset v0.4.2
   Compiling unicode-segmentation v1.10.1
   Compiling owo-colors v3.5.0
   Compiling libm v0.2.8
   Compiling shlex v1.2.0
   Compiling peeking_take_while v0.1.2
   Compiling same-file v1.0.6
   Compiling parking_lot_core v0.9.9
   Compiling log v0.4.20
   Compiling rustc-hash v1.1.0
   Compiling walkdir v2.4.0
   Compiling serde_spanned v0.6.5
   Compiling toml_datetime v0.6.5
   Compiling toml_edit v0.21.0
   Compiling convert_case v0.6.0
   Compiling toml v0.8.8
   Compiling cargo_toml v0.16.3
   Compiling petgraph v0.6.4
   Compiling rustc_version v0.3.3
   Compiling pgrx-pg-config v0.11.2
   Compiling crossbeam-deque v0.8.4
   Compiling rustc_version v0.4.0
   Compiling rand_core v0.6.4
   Compiling num-traits v0.2.17
   Compiling rustls v0.21.10
   Compiling rayon-core v1.12.0
   Compiling unescape v0.1.0
   Compiling ppv-lite86 v0.2.17
   Compiling adler v1.0.2
   Compiling smallvec v1.11.2
   Compiling byteorder v1.5.0
   Compiling radium v0.7.0
   Compiling pgrx-pg-sys v0.11.2
   Compiling rand_chacha v0.3.1
   Compiling miniz_oxide v0.7.1
   Compiling pgrx-sql-entity-graph v0.11.2
   Compiling heapless v0.7.17
   Compiling atomic-traits v0.3.0
   Compiling rustls-webpki v0.101.7
   Compiling sct v0.7.1
   Compiling bytemuck_derive v1.5.0
   Compiling validator_types v0.16.0
   Compiling c v0.0.0 (/build/source/crates/c)
   Compiling if_chain v1.0.2
   Compiling tap v1.0.1
   Compiling wyz v0.5.1
   Compiling validator_derive v0.16.0
   Compiling bytemuck v1.14.0
   Compiling multiversion-macros v0.7.3
   Compiling flate2 v1.0.28
   Compiling pgrx-macros v0.11.2
   Compiling rand v0.8.5
   Compiling hash32 v0.2.1
   Compiling uuid v1.6.1
   Compiling enum-map-derive v0.17.0
   Compiling ctor v0.2.6
   Compiling idna v0.4.0
   Compiling crossbeam-channel v0.5.10
   Compiling crossbeam-queue v0.3.10
   Compiling std_detect v0.1.5 (https://github.com/tensorchord/stdarch.git?branch=avx512fp16#db0cdbc9)
error[E0658]: use of unstable library feature 'stdarch_x86_has_cpuid'
  --> /build/cargo-vendor-dir/std_detect-0.1.5/src/detect/os/x86.rs:33:9
   |
33 |     if !has_cpuid() {
   |         ^^^^^^^^^
   |
   = note: see issue #60123 <https://github.com/rust-lang/rust/issues/60123> for more information
   = help: add `#![feature(stdarch_x86_has_cpuid)]` to the crate attributes to enable
   = note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date

For more information about this error, try `rustc --explain E0658`.
error: could not compile `std_detect` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...

Additional context
I was able to build pgvecto-rs 0.2.1 successfully in the past, and there hasn't been an update to pgvecto-rs or cargo-pgrx recently, so I'm not sure why this is failing now. Perhaps I was relying on the build cache's copy of cargo-pgrx, and now I'm not?
The error looks to be due to using an unstable rust library feature (stdarch_x86_has_cpuid) while not using a nightly rust compiler. Did the default rust compiler used to build packages change recently?
Notify maintainers
cargo-pgrx maintainers:

@happysalada

pgvecto-rs maintainers:

@diogotcorreia
@esclear

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.32, NixOS, 24.11 (Vicuna), 24.11.20240613.e9ee548`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/qqwr649pc0qprc9lw2fmdsi1km6p7q2h-source`

Add a :+1: reaction to issues you find important.

Its most likely a version issue.
Cargo pgrx is very version sensitive. Every minor upgrade is breaking. Ive been waiting for 1.0 to try to make the upgrade in nixpkgs otherwise we have to add and maitain every minor version.
You cam try with a different version is you want and that might solve your problem.
Sorry for not having a better solution than this unfortunately.

This seems to have been caused by an upgrade of rustc to 1.78 (from 1.77.2). I'll see if it can be patched in pgvecto.rs (or pgrx if that's the case).
nixpkgs on nixos-24.05
❯ nix repl
Welcome to Nix 2.18.2. Type :? for help.

nix-repl> :l .
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
Added 21484 variables.

nix-repl> pkgs.rustPlatform.rust.rustc.version
"1.77.2"

nix-repl> pkgs.rustc.version
"1.77.2"

nixpkgs on nixos-unstable
❯ nix repl
Welcome to Nix 2.18.2. Type :? for help.

nix-repl> :l .
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
Added 21680 variables.

nix-repl> pkgs.rustPlatform.rust.rustc.version
"1.78.0"

nix-repl> pkgs.rustc.version
"1.78.0"

Some more information I found:

pgvecto-rs uses a fork of rust's std_detect crate (under the stdarch repo), which only has a single commit (https://github.com/tensorchord/stdarch/tree/avx512fp16): https://github.com/tensorchord/pgvecto.rs/blob/v0.2.1/crates/detect/Cargo.toml#L7
This commit has since been merged upstream https://github.com/rust-lang/stdarch/commit/fb7df64264cefdebdcaeab4f269a529bc992819b
The build is failing because of https://github.com/rust-lang/stdarch/pull/1486 (you can see the devs trying to fix all the build failures in the commit history https://github.com/rust-lang/stdarch/commits/master/crates/std_detect/src/lib.rs)

I think the easiest fix here would be to patch pgvecto-rs to use Rust's crate instead of the fork, which should work fine. I'll still have to investigate whether there were any other changes to the std_detect crate that could cause problems, but it seems to be a fairly small crate, so fingers crossed it doesn't.

@anoadragon453 Can you try my branch in PR https://github.com/NixOS/nixpkgs/pull/320302?
It's based on commit https://github.com/NixOS/nixpkgs/commit/e9ee548d90ff586a6471b4ae80ae9cfcbceb3420, so it should be a drop-in replacement for nixos-unstable.
Let me know on the PR if it works fine with Immich (perhaps backup first, but I don't think it should have problems).


Automatic error report

OS: windows 10 64bit

Click Tools->Preferences->Syntax coloring
Select Scheme: Spyder Dark and click apply button
Then, Spyder internal error occurs

Thanks for reporting. This is a duplicate of issue #6519, which will be fixed in our next version.


You show a sctip to Install but how about Uninstall?

You have the install script:
install-wireguard.bash
would be beneficial to have an equivalent for "uninstall" that would
clean-up (reverse) and changed made.

Also, maybe you should turn-on your Github Repo's "Wiki" function so Q&A can be done & it also would make it easy to find answers by new people using this.
just an idea.

Wiki opened up to everyone (I think, let me know if it doesn't work).
Agreed, an uninstall script would be very beneficial. Not sure when I could get around to this, but it should just involve deleting the configs, stopping wg-quick@wg0, disabling the auto-start, then (optionally) removing the wireguard packages.
If anyone wants to take this on, PRs will absolutely be accepted.


Cannot set mode to OFF

If I set the mode to OFF (using the web ui, homeassistant or direct POST), the charging stops but the mode does not turn to OFF anymore, after a few seconds, charging starts again.
I did some debugging, write_settings() was added at some places, this calls validate_settings(), and in there is this check:
if (RFIDReader == 2) Access_bit = 0;
    // Enable access if no access switch used
    else if (Switch != 1 && Switch != 2) Access_bit = 1;

the else if flips the Access_bit to 1 again on my setup. I am not entirely sure what needs to be done to fix it in the current flow.

Thanks for noticing Dan, I have no RFID reader attached so I didn't notice this behaviour; it forced me to release v1.6.4 early, that has a bugfix in it for this problem. Please confirm if it tests ok @ your setup?

i don't have an RFID reader attached either (it actually hits it if RFIDReader != 2).. it does this if Switch !=1 or 2.. which both are activation switche types (i have my switch configured as smart/solar switcher).

Aha ok it should still be fixed since those lines will no longer be hit when changing modes....


ARM Arch support

Hi! congrats for the app!
I would love to know if the docker container has ARM support? because when a try to install it via docker-compose got this log messages on my raspi:

thanks!

Hi, that's a good point! I'll see about creating a multi-arch Docker image today.


Add getitem and setitem to wrapped methods

This allows for using the subredis[key] format instead of only subredis.get(key) and subredis.set(key).  Tested on 3.4.3 and 2.7.5.

Sorry it's nearly a year later, but this PR looks great. Merging...

Released an v0.2.0


Flutter 1.21.0-9.2.pre cherry picks

Description
I accidentally closed https://github.com/flutter/flutter/pull/64680 and cannot re-open, so I'm recreating the PR with this one.
Additional cherry picks to fix tests:

https://github.com/flutter/flutter/pull/63806
https://github.com/flutter/flutter/pull/63796

Related Issues
Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR. There should be at least one issue listed here.
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behavior with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

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

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

@a14n would you mind letting the CLA bot know it's ok to cherry pick your commit?

@googlebot I consent

@a14n thanks!


Bug in select2 wrapper component example (on options changed)

I found when using this - if the options change after rendering, the new set gets appended to the existing set rather than replacing them. Adding the empty() call in the options watch solved this.
I'm not sure how to update the jsfiddle so I linked to my fork of it, happy to change as needed!

Thanks! I just forked your fork, as we like to keep the fiddles under member accounts for security reasons. 🙂

This approach ends up throwing out any additional options that are passed in via the <slot>, unfortunately.


Make stdout accessible for console components

This is another feature request. When using components in a web controller we can access Yii::trace(), Yii::debug() and so forth statically from within the component. However, when using application components in a console environment, we can't use the stdout() function from within the component, because it's not accessible statically. I'm looking for a consistent way of outputting messages in a console application that makes use of components. Any suggestions?

Q
A

Yii version
2.0.10

See:
https://github.com/yiisoft/yii2/issues/12163#issuecomment-240046093

Thanks for the hint! I also just found out that anything (public) defined in the controller can be accessed through Yii::$app->controller. Hence, anything logging related can be accessed that way also from a component. So no worries there!


Ftrack: Use client query functions

Brief description
Ftrack module is using query functions from PR instead of direct use of mongo queries.
Description
Replaced queries using AvalonMongoDB with using function queries from openpype.client. Function get_versions can accept version names (versions as integers) in filter args. Added new function get_archived_assets, it is questionable if it can be merged into get_assets with more specific arguments.
Testing notes:

[x] Run any application
[x] Run prepare project action on new project
[ ] Auto-sync from ftrack should work (event server must be running)
[x] Run sync to avalon action (doesn't matter if local of server)
[x] Download thumbnails from ftrack to openpype
[ ] Run delivery action
[ ] Run delete old versions action
[ ] Run delete asset/subset action (it would be good to try both variants)
[ ] Integration of hierarchy to ftrack during editorial publishing
[ ] Action to fill workfile attribute (this requires some more settings)

Optional testing
Not sure if these features were working:

Event user assignment
RV action

Also, if I select any asset/shot and chose Delete Asset/Subset action, it is ignoring the context where it is started from and behaving like I am in Project context. It is listing all available Asset objects within the project.


[BUG] Bright colors use the same sequences as regular colors on Command Prompt

Describe the bug
On Command Prompt, bright colors use the same escape sequences as regular colors (e.g. \x1b[30m) rather than the ones for bright colors (e.g. \x1b[90m).
I would expect bright colors to either use the bold escape sequence or just use the regular bright color sequence, either works the same in Command Prompt so it doesn't really matter which of these would be used.
To Reproduce
import rich

def show_color(x):
    c.print(f"[color({x})]TEXT[/]    [color({x+8})]TEXT[/]    [color({x}) bold]TEXT[/]")

c = rich.get_console()

c.print("normal  bright  bold\n")
for x in range(8):
    show_color(x)

c.print("\nnormal                 bright                 bold\n")
with c.capture() as capture:
    for x in range(8):
        show_color(x)
print(capture.get().replace("\x1b", "\\x1b"))

Command Prompt:

Windows Terminal for comparison:

Platform
Windows with Command Prompt and for comparison Windows with Windows Terminal.
Diagnose
Command Prompt:

Windows Terminal for comparison:

Running Rich 9.8.2 on both.

From what I gathered, changing few methods in Color to support 16 rather than 8 colors would be enough to fix it on Windows 10, but I've got no clue if that won't break on older Windows versions that don't support ANSI escape sequences.
So if that were problematic, it could be better to instead use the standard color system on Windows versions that support ANSI escape sequences, but I don't really know whether that would be easy to accomplish.

From what I gathered, changing few methods in Color to support 16 rather than 8 colors would be enough to fix it on Windows 10, but I've got no clue if that won't break on older Windows versions that don't support ANSI escape sequences.
So if that were problematic, it could be better to instead use the standard color system on Windows versions that support ANSI escape sequences, but I don't really know whether that would be easy to accomplish.

The problem with bright colors on Windows is bold would have no effect, i.e. "bold bright_red" renders the same as "bright_red" - since true bold isn't supported. That and the fact that the default color choices for Windows is terrible. Some of the "bright" versions are barely distinguishable from the regular versions.
That was my thinking at the time. I'm not a windows user myself. If you think that it is better to explicitly expose all 16 colors I'm happy to make the change.

The problem with bright colors on Windows is bold would have no effect, i.e. "bold bright_red" renders the same as "bright_red" - since true bold isn't supported. That and the fact that the default color choices for Windows is terrible. Some of the "bright" versions are barely distinguishable from the regular versions.
That was my thinking at the time. I'm not a windows user myself. If you think that it is better to explicitly expose all 16 colors I'm happy to make the change.

You're right that bold has the same effect as using the bright color and that "bolded" bright color and not "bolded" will be the same on Windows. But even with that said, I think it's easier to make a multiplatform application if you can still differ between bright color and bold color on platforms that do support it. This way, you can at least still expect the "bright" colors to be "bright" on all platforms, rather than use bold just so that it can also appear "bright" on Windows.
So to summarize, I think that exposing all 16 colors on Windows would indeed work better.

You're right that bold has the same effect as using the bright color and that "bolded" bright color and not "bolded" will be the same on Windows. But even with that said, I think it's easier to make a multiplatform application if you can still differ between bright color and bold color on platforms that do support it. This way, you can at least still expect the "bright" colors to be "bright" on all platforms, rather than use bold just so that it can also appear "bright" on Windows.
So to summarize, I think that exposing all 16 colors on Windows would indeed work better.

v9.9.0 exposes all 16 colors.

v9.9.0 exposes all 16 colors.


[🙏] - Protect main branch

Describe the request
Protect main branch, so no one can direct push to main branch.
Steps:

Go to Settings > Rules > Rulesets

Fill the inputs

Ruleset Name: main
Enforcement status: select Active
SKIP Bypass list

In the Target branches.

Click Add target > Select Include default branch

In the Branch Rules, select:

Restrict deletions (it's already checked by default in many cases)
Require a pull request before merging

Required approvals, select to 1
Select Dismiss stale pull request approvals when new commits are pushed
Select Require conversation resolution before merging
Allowed merge methods only Squash

Require status checks to pass

Check Require branches to be up to date before merging
Click + Add checks

Find GitHub Actions: smoke and ci
Find Vercel Deployment

please review the settings mas @mazipan 🙇🏻

i'm not sure for the Status checks that are required section.
is it correct?

This is trial and error actually.
Let just ship it first, if something wrong then we can revisit the settings.
By enabling this setting, you (as an owner) also need to start to not "coding in the main branch". Consider to create separate branch then create pull request even though you can approve it by your self.


[Bug]: Why the aspect_rules_js can not find the package?

What happened?
I have installed all package in my modules package.json. but it sill failed.
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+core<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>3:0-54
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>1:0-37
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-46
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-70
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>1:0-45
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>1:0-75
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-71
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>2:0-48
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@deck.gl+mesh-layers<EMAIL_ADDRESS>3:0-54
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@deck.gl+mesh-layers<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+gltf<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@loaders.gl+schema<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@math.gl+polygon<EMAIL_ADDRESS>1:0-72
Module not found: Error: Can't resolve '@babel/runtime/helpers/esm/defineProperty' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@math.gl+polygon<EMAIL_ADDRESS>
ERROR in ../../../../node_modules/.aspect_rules_js/@turf+dissolve<EMAIL_ADDRESS>4:0-36
Module not found: Error: Can't resolve '@turf/flatten' in '/autra/.cache/bazel/cb92cb09597ef463226f6e13f5e110cf/execroot/autra/bazel-out/k8-fastbuild/bin/node_modules/.aspect_rules_js/@turf+dissolve@6.5.0/node_modules/@turf/dissolve/dist/es'

Version
Development (host) and target OS/architectures:
Output of bazel --version:
bazel 5.5.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
.aspect_rules_js
1.20.0
Language(s) and/or frameworks involved:
How to reproduce
{
  "version": "5.5.0",
  "description": "Visualization of the Autra.",
  "main": "app.js",
  "license": "Apache-2.0",
  "packageManager"<EMAIL_ADDRESS>  "engines": {
    "npm": ">=8",
    "node": ">=16"
  },
  "dependencies": {
    "@ant-design/icons": "^4.7.0",
    "@babel/runtime": "^7.14.0",
<EMAIL_ADDRESS>"8.7.12",
<EMAIL_ADDRESS>"8.7.12",
<EMAIL_ADDRESS>"8.7.12",
<EMAIL_ADDRESS>"8.7.12",
    "@emotion/core": "^10.0.22",
    "@emotion/styled": "10.0.27",
<EMAIL_ADDRESS>"^3.2.0",
<EMAIL_ADDRESS>"^3.2.0",
<EMAIL_ADDRESS>"^3.2.0",
<EMAIL_ADDRESS>"^3.2.0",
<EMAIL_ADDRESS>"^8.4.0",
<EMAIL_ADDRESS>"^8.4.0",
<EMAIL_ADDRESS>"^8.4.0",
<EMAIL_ADDRESS>"^8.4.0",
<EMAIL_ADDRESS>"^8.4.0",
    "@turf/turf": "^6.5.0",
    "antd": "4.20.5",
    "base64-js": "^1.3.0",
    "baseui": "^8.5.1",
    "chart.js": "^2.7.0",
    "chncrs": "^0.1.6",
    "classnames": "^2.2.5",
    "color": "^3.0.0",
    "comlink": "^4.3.1",
    "compute-polynomial": "^1.1.0",
    "d3-array": "3.2.0",
    "d3-scale": "4.0.2",
    "debounce": "^1.1.0",
    "deck.gl": "8.7.12",
    "fast-text-encoding": "^1.0.3",
    "font-awesome": "^4.7.0",
    "gl-matrix": "^3.4.0",
    "i18next": "^21.6.16",
    "imports-loader": "0.6.5",
    "lodash": "^4.17.14",
    "lodash.merge": "^4.6.1",
    "lru-cache": "^7.13.2",
    "math.gl": "^3.0.0",
    "mobx": "^5.15.2",
    "mobx-react": "^6.1.5",
    "mobx-utils": "^5.5.7",
    "moment": "2.29.4",
    "object-hash": "^3.0.0",
    "object-sizeof": "^1.6.3",
    "popper.js": "^1.11.1",
    "probe.gl": "^3.1.0",
    "proj4": "^2.4.4",
    "promise-retry": "^1.1.1",
    "prop-types": "^15.6.2",
    "protobufjs": "^6.8.4",
    "rc-slider": "^9.7.2",
    "react": "^16.14.0",
    "react-dom": "^16.14.0",
    "react-error-boundary": "^3.1.4",
    "react-i18next": "^11.16.7",
    "react-jss": "^10.4.0",
    "react-loadable": "^5.3.1",
    "react-map-gl": "~5.2.0",
    "react-router": "^5.2.0",
    "react-router-dom": "^5.2.0",
    "react-split-pane": "^0.1.66",
    "react-tabs": "^3.1.1",
    "react-tooltip": "^4.2.7",
    "react-virtualized": "9.22.3",
    "react-vis": "^1.11.2",
    "recorder-js": "^1.0.7",
    "reselect": "^3.0.0",
    "stats.js": "^0.17.0",
    "styled-components": "^4.1.3",
    "styletron-engine-atomic": "^1.4.0",
    "styletron-react": "^5.2.0",
    "three": "0.104.0",
    "three-line-2d": "^1.1.6",
    "viewport-mercator-project": "^6.1.0"
  },
  "devDependencies": {
    "@babel/core": "^7.14.0",
    "@babel/eslint-parser": "^7.12.1",
    "@babel/plugin-proposal-class-properties": "^7.18.6",
    "@babel/plugin-proposal-decorators": "^7.14.2",
    "@babel/plugin-proposal-optional-chaining": "^7.20.7",
    "@babel/plugin-syntax-export-default-from": "^7.18.6",
    "@babel/plugin-transform-runtime": "^7.19.6",
    "@babel/plugin-syntax-flow": "^7.14.5",
    "@babel/plugin-transform-react-jsx": "^7.14.9",
    "@babel/preset-env": "^7.20.2",
    "@babel/preset-react": "^7.16.0",
    "@babel/preset-stage-0": "^7.0.0",
    "@babel/preset-typescript": "^7.17.12",
    "@babel/plugin-proposal-object-rest-spread": "^7.20.7",
    "@danmarshall/deckgl-typings": "^4.9.0",
    "@harmony-dev/protobufjs": "^6.10.0",
    "@harmony-dev/protobufjs-cli": "^1.0.1",
    "@svgr/webpack": "5.5.0",
    "@testing-library/dom": "^7.26.5",
    "@testing-library/jest-dom": "^5.14.0",
    "@testing-library/react": "^11.0.0",
    "@types/debounce": "^1.2.1",
    "@types/lodash": "^4.14.191",
    "@types/prop-types": "^15.7.5",
    "@types/react": "^16.14.0",
    "@types/react-dom": "^16.9.16",
    "@types/react-router-dom": "^5.1.2",
    "@types/react-virtualized": "^9.21.21",
    "@types/viewport-mercator-project": "^6.1.2",
    "@typescript-eslint/parser": "^5.42.0",
    "babel-loader": "^8.3.0",
    "babel-polyfill": "^6.26.0",
    "copy-webpack-plugin": "^4.2.0",
    "css-loader": "^0.28.2",
    "eslint": "^8.1.0",
    "eslint-config-airbnb": "^19.0.4",
    "eslint-config-airbnb-base": "^15.0.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-import-resolver-alias": "^1.1.2",
    "eslint-plugin-import": "^2.23.2",
    "eslint-plugin-jsx-a11y": "^6.4.1",
    "eslint-plugin-prettier": "^3.4.0",
    "eslint-plugin-react": "^7.24.0",
    "eslint-plugin-react-hooks": "^4.2.0",
    "eslint-webpack-plugin": "2.6.0",
    "fast-sass-loader": "^2.0.1",
    "file-loader": "^6.2.0",
    "html-webpack-plugin": "5.5.0",
    "image-webpack-loader": "^7.0.1",
    "jest": "^27.0.4",
    "json-loader": "^0.5.4",
    "less": "4.1.2",
    "less-loader": "^7.3.0",
    "prettier": "^2.5.1",
    "sass": "^1.50.0",
    "style-loader": "^0.18.1",
    "tslint": "^4.0.0",
    "tslint-webpack-plugin": "2.1.1",
    "typescript": "^4.6.4",
    "url-loader": "4.0.0",
    "webpack": "~5.75.0",
    "webpack-bundle-analyzer": "^3.3.2",
    "webpack-cli": "^5.0.1",
    "webpack-dev-server": "^4.8.0",
    "webpack-permissions-plugin": "^1.0.8",
    "webpackbar": "5.0.2",
    "worker-loader": "^3.0.6",
    "yaml-loader": "^0.4.0",
    "ts-loader": "^8.0.4"
  }
}

No response
Any other information?
load("@npm//modules/dreamview/frontend:webpack-cli/package_json.bzl", "bin")
load("@npm//:defs.bzl", "npm_link_all_packages")
load("@aspect_rules_js//js:defs.bzl", "js_library")
load("//buildtools/install:install.bzl", "install_files")

npm_link_all_packages(name = "node_modules")

package(default_visibility = ["//visibility:public"])

filegroup(
    name = "frontend_src",
    srcs = glob([
        "src/**/*",
        "proto_bundle/*.json",
        "assets/**/*",
        "autra_modules_wasm/*",
    ]),
)

filegroup(
    name = "frontend_config",
    srcs = [
        ".babelrc",
        ".eslintrc",
        ".prettierignore",
        ".prettierrc.js",
        "global.d.ts",
        "tsconfig.json",
        "webpack.config.js",
    ],
)

js_library(
    name = "frontend_lib",
    srcs = [
        ":frontend_src",
    ],
    deps = [
        ":node_modules",
    ],
)

bin.webpack_cli(
    name = "webpack_bundle",
    srcs = [
        ":frontend_config",
        ":frontend_lib",
    ],
    args = [
        "--progress",
        "--config",
        "webpack.config.js",
        "--mode=production",
        "--stats=minimal",
        "--output-path",
        "webpack_dist",
    ],
    chdir = package_name(),
    log_level = "debug",
    out_dirs = [
        "webpack_dist",
    ],
)

genrule(
    name = "bundle_dist",
    srcs = [
        ":webpack_bundle",
    ],
    outs = [
        "dist",
    ],
    cmd = """
        chmod -R 755 $(SRCS) &&
        cp -rp $(SRCS) $(OUTS) &&
        rm -rf $(SRCS)
     """,
)

# install the dist

install_files(
    name = "install",
    dest = "modules/dreamview/frontend",
    files = [
        ":bundle_dist",
    ],
)

Fund our work

[ ] Sponsor our open source work by donating a bug bounty

This looks like an issue with how https://loaders.gl/ is resolving npm packages and not a rules_js issue. I recommend trying this with pnpm outside of Bazel with hoist=false in your .npmrc. We do provide paid support at https://aspect.dev if you would like us to dig deeper into this. The community on the #javascript channel on https://slack.bazel.build/ is also very helpful.

This looks like an issue with how https://loaders.gl/ is resolving npm packages and not a rules_js issue. I recommend trying this with pnpm outside of Bazel with hoist=false in your .npmrc. We do provide paid support at https://aspect.dev if you would like us to dig deeper into this. The community on the #javascript channel on https://slack.bazel.build/ is also very helpful.

Thanks, it is weird that I can build it with webpack cli, but failed with rule_js.

I have fixed the issue by adding<EMAIL_ADDRESS>path.resolve(__dirname<EMAIL_ADDRESS>to resolve.alias in webpack_config.


improvementoptimize select stmt with limit 0

Proposed changes
In some scenarios of automatic report generation platform, field and type information is frequently obtained through select followed by limit 0
select * from .. limit 0
Doris has two problems in processing
1、Limit 0 SQL will also be sent to the be node for meaningless queries
2、When there are multiple nested scenes, it will lead to some strange cores
Some optimizations have been made for this purpose. The sql of limit 0 is not sent to be any more. It is returned directly after carrying the meta information on the fe side
在一些自动化报表生成平台场景会频繁通过select 接一个limit 0的方式来获取字段和类型的信息
select * from ..  limit 0

doris在处理时存在两个问题
1、limit 0 的sql也会发到be节点，做无意义的查询
2、在里面有多层嵌套场景下，会导致be一些奇怪的core
为此做了一些优化，limit 0 的sql不在发送到be，在fe侧携带meta信息后直接返回
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.84 seconds
load time: 508 seconds
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221209062627_clickbench_pr_60766.html

hi @chenlinzhong , please add some regression test for this case


Make it works

What error are you seeing where this line is not working?     What OS / PHP version?

PHP 5.6
OS: debain, ubuntu.
I didn't see errors, just hanging protoc command.


feat(tutorial): complete step 5 - Boeblingen

Closes #
{{short description}}
Changelog
New
Bluemix URL: https://carbon-tutorial-lakeside76.mybluemix.net/#/

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@lakeside76 Looks spectacular 💯! I've recorded your completion of step 5.

@ZrianinaMariia Thank you for your prompt review & approval!!

@lakeside76 Feel free to stop your running application on IBM Cloud to avoid the possibility of incurring any charges.


tgsen uses an output argument for computing a default argument

tgsen uses lwork=max(2*m*(n-m),1) as default argument (for the complex case) where integer intent(out) :: m. I assume this means that lwork will always be 1, which is usually insufficient. m is the amount of eigenpairs that will be selected (which may be larger than the amount of nonzeros in the select array in the non-complex case).
Note that the same issue exists for the non-complex case, but this is less visible, since the default is set to lwork=max(MAX(4*n+16,2*m*(n-m)),1), so this includes 4*n+16.
Reproducing code example:
@pytest.mark.parametrize('dtype', DTYPES)
def test_gges_tgsen(dtype):
    seed(1234)
    atol = np.finfo(dtype).eps*100

    n = 10
    a = generate_random_dtype_array([n, n], dtype=dtype)
    b = generate_random_dtype_array([n, n], dtype=dtype)

    gges, tgsen = get_lapack_funcs(('gges', 'tgsen'), dtype=dtype)

    result = gges(lambda x: None, a, b, overwrite_a=False, overwrite_b=False)
    assert_equal(result[-1], 0)

    s = result[0]
    t = result[1]
    q = result[-4]
    z = result[-3]

    if dtype in COMPLEX_DTYPES:
        assert_allclose(s, np.triu(s), rtol=0, atol=atol)
        assert_allclose(t, np.triu(t), rtol=0, atol=atol)

    assert_allclose(q @ s @ z.conj().T, a, rtol=0, atol=atol)
    assert_allclose(q @ t @ z.conj().T, b, rtol=0, atol=atol)

    result = tgsen(select, s, t, q, z)
    assert_equal(result[-1], 0)

    s = result[0]
    t = result[1]
    q = result[-9]
    z = result[-8]

    if dtype in COMPLEX_DTYPES:
        assert_allclose(s, np.triu(s), rtol=0, atol=atol)
        assert_allclose(t, np.triu(t), rtol=0, atol=atol)

    assert_allclose(q @ s @ z.conj().T, a, rtol=0, atol=atol)
    assert_allclose(q @ t @ z.conj().T, b, rtol=0, atol=atol)

Error message:
 ** On entry to CTGSEN parameter number 21 had an illegal value
 ** On entry to ZTGSEN parameter number 21 had an illegal value

Scipy/Numpy/Python version information:
Scipy commit 55cf5c301e58f24092639c01e48c2bd139807906
Numpy 1.19.4
Python 3.8.5

Also, it needs to be +1 the actual default value. See also
https://github.com/scipy/scipy/blob/6e15c52a40370d629dfa4951eb58e7f2b267ed61/scipy/linalg/_decomp_qz.py#L373

Well indeed we clearly made a mistake in that wrapper.

Correction: I am surprised that it is actually working. Most settings should have lead to segfaults. I'll fix this

Well apparently, I've opened a can of worms since when I touched these wrappers, linalg.qz and linalg.ordqz stopped working. So it will get a bit complicated as a fix.
However, there is basically no way to get a straightforward formula to get the minimal lwork and liwork values hence there will be an additional ?tgsen_lwork functions wrapped to get the right values. Then the regular ?tgsen call can be requested.


Add support for presence detection using GPIO polling

Can one of the admins verify this patch?

add to approvelist

jenkins run tests please

jenkins run tests please


Add proper Don/Ka types to clusters of notes

This should match most fumens. Some exceptional cases I've seen:

[x] ~In official fumens, even-numbered clusters of 4 notes will sometimes be ドドドド or カカカカ. Right now, my converter will always use ドドドドン or カカカカッ, since I don't really understand the rules behind it.~ Fixed: Now, all 16th notes and above in groups of 4 will no longer use the don/kat ending character.
[X] ~In official fumens, sometimes isolated notes will be grouped together, but sometimes they will be treated as single clusters of 1. Right now, my converter will always try to cluster isolated notes.~ Fixed: Only 4th/8th/16th/etc. notes will be clustered. Whole/half notes will not be clustered.
[x] ~Right now, my logic always treats big notes as their own cluster. But, sometimes you get a cluster like ddddD, and right now my converter treats this as (ドドドドン) + big DON instead of do-ko-do-ko-DON.~ Fixed: Now big notes are included in clusters.
[x] ~For high-level Oni songs with complex groups of dense notes (e.g. (12th/16th/24th) notes mixed with (16th/34th/32nd) notes), official fumens seem to group them together even though they technically have different timings. Right now, my converter will group the 32nd notes, but treat the 16th notes as their own separate group.~ Fixed: Now anything above an 8th note will be clustered together.
[X] Songs with BPM gimmicks. e.g. the TJA has low base BPM, but then everything is doubled/tripled except for one section. I can't remember which songs have this? Something like RNG Cinderella?

Maybe solved by https://github.com/vivaria/tja2fumen/pull/64/commits/1f640c1aa1fb436fe6edf421e077fdb2a41aaf00?

Fixes #41.

From Discord, Yin has requested what is basically a bin2bin refresher -- basically, an option to read in an old .bin file (converted with an old version of tja2bin/tja2fumen) then update the senote types.
I think this should be pretty easy to implement as part of this PR, since:

I already have a read_fumen function that can parse the old tja2bin-converted .bins
The read_fumen function outputs my custom FumenCourse class, which is the exact same output as the TJA->Fumen process. So, I should be able to re-use the exact same code on both old bins and converted TJAs. :D
I could probably make the new note type code modular, so that it can be run

sakurada and yin have been helping test lots, and they've given the 👍 on this PR working as they expect 🎉


Unable to host my asp.net wep apis to azure app service

Description
[Enter feedback here]
I have been trying to deploy my asp.net Apis to azure app service from visual studio to no gain. I have tried all the resources I could find but no gain. The far I could go is to successfully publish the apis but when i go to get them I cannot just getting 404 error
Page URL
https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-api-management-using-vs?view=aspnetcore-7.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/tutorials/publish-to-azure-api-management-using-vs.md
Document ID
19c98d91-e5fe-5832-6c75-23e677e469a3
Article author
codemillmatt

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

Potential bugs in the ASP.NET Core framework and product feedback can be reported at dotnet/aspnetcore issues (include full repro steps and cross-link to a repro project in GH when appropriate). For Visual Studio, use the Report a Problem gesture or Suggest a Feature gesture within VS, which open internal issues for the VS team. For Visual Studio Code, you can open an issue at microsoft/vscode issues.


Drop skip option and improve 'plan' and 'run' UI

Drop skip option and use "Continue(y/N)" instead
For application level upgrade, group all of its substeps and prompt
only once.
For functionless steps (except ApplicationUpgradeStep) and UpgradeSubSteps
(including its child classes), automatically proceed without prompting
Add progress indicator for eligible steps

fixes: #76
fixes: #82
fixes: #84
fixes: #128
fixes: #162
(To be merged after #163 )

Unit tests to be added after getting approval for on the approach.

Can we convert this to draft, it do not make sense to review it before #163.

There is one ongoing discussion about UX, but other than that it's LGTM.


test: add new proxy controller tests

:tada: This PR is included in version 0.16.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug] Broker gets block while creating topic using IsolatedBookieEnsemblePlacement in missing cache

Search before asking

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

Version
2.11.0
Minimal reproduce step
1、create namespace and set bookie affinity group
2、create topic under that namespace
3、broker will appear log "ZooKeeper session reconnection timeout. Notifying session is lost."
What did you expect to see?
create topic success
What did you see instead?
topic creating is block
Anything else?
`2023-04-19T21:53:11,365+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 4.166 seconds
2023-04-19T21:53:11,366+0800 [metadata-store-zk-session-watcher-11-1] INFO  org.apache.pulsar.broker.PulsarService - Received metadata service session event: ConnectionLost
2023-04-19T21:53:11,367+0800 [metadata-store-zk-session-watcher-11-1] INFO  org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl - Received MetadataStore session event: ConnectionLost
2023-04-19T21:53:11,369+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 88,3  replyHeader:: 88,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:11,701+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 3.83 seconds
2023-04-19T21:53:11,702+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 89,3  replyHeader:: 89,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:12,035+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 3.496 seconds
2023-04-19T21:53:12,036+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 90,3  replyHeader:: 90,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:12,368+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 3.163 seconds
2023-04-19T21:53:12,369+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 91,3  replyHeader:: 91,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:12,702+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 2.83 seconds
2023-04-19T21:53:12,703+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 92,3  replyHeader:: 92,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:13,035+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 2.496 seconds
2023-04-19T21:53:13,036+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 93,3  replyHeader:: 93,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:13,369+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 2.163 seconds
2023-04-19T21:53:13,371+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 94,3  replyHeader:: 94,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:13,702+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 1.829 seconds
2023-04-19T21:53:13,703+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 95,3  replyHeader:: 95,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:14,035+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 1.496 seconds
2023-04-19T21:53:14,037+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 96,3  replyHeader:: 96,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:14,369+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 1.162 seconds
2023-04-19T21:53:14,370+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 97,3  replyHeader:: 97,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:14,702+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 0.829 seconds
2023-04-19T21:53:14,703+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 98,3  replyHeader:: 98,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:15,036+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 0.495 seconds
2023-04-19T21:53:15,037+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply session id: 0x24109391046d001e, packet:: clientPath:/ serverPath:/ finished:false header:: 99,3  replyHeader:: 99,4294969298,0  request:: '/,F  response:: s{0,0,0,0,0,9,0,0,0,11,4294967580}
2023-04-19T21:53:15,176+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Got notification session id: 0x24109391046d001e
2023-04-19T21:53:15,176+0800 [main-SendThread(<IP_ADDRESS>:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Got WatchedEvent state:SyncConnected type:NodeDataChanged path:/loadbalance/brokers/<IP_ADDRESS>:8080 for session id 0x24109391046d001e
2023-04-19T21:53:15,369+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.metadata.impl.ZKSessionWatcher - ZooKeeper client is disconnected. Waiting to reconnect, time remaining = 0.162 seconds
2023-04-19T21:53:15,703+0800 [metadata-store-zk-session-watcher-11-1] INFO  org.apache.pulsar.broker.PulsarService - Received metadata service session event: SessionLost
2023-04-19T21:53:15,978+0800 [metadata-store-zk-session-watcher-11-1] WARN  org.apache.pulsar.broker.PulsarService - The session with metadata service was lost. Shutting down.
"main-EventThread" #19 daemon prio=5 os_prio=0 cpu=363.30ms elapsed=12.86s tid=0x00007fcd19a3b480 nid=0x3296 waiting on condition  [0x00007fcaf02e5000]
java.lang.Thread.State: WAITING (parking)
at<EMAIL_ADDRESS>Method)
- parking to wait for  <0x0000100015adbd50> (a java.util.concurrent.CompletableFuture$Signaller)
at java.util.concurrent.locks.LockSupport.park(java.base@17.0.5/LockSupport.java:211)
at java.util.concurrent.CompletableFuture$Signaller.block(java.base@17.0.5/CompletableFuture.java:1864)
at java.util.concurrent.ForkJoinPool.unmanagedBlock(java.base@17.0.5/ForkJoinPool.java:3463)
at java.util.concurrent.ForkJoinPool.managedBlock(java.base@17.0.5/ForkJoinPool.java:3434)
at java.util.concurrent.CompletableFuture.waitingGet(java.base@17.0.5/CompletableFuture.java:1898)
at java.util.concurrent.CompletableFuture.join(java.base@17.0.5/CompletableFuture.java:2117)
at org.apache.pulsar.bookie.rackawareness.IsolatedBookieEnsemblePlacementPolicy.initialize(IsolatedBookieEnsemblePlacementPolicy.java:91)
at org.apache.pulsar.bookie.rackawareness.IsolatedBookieEnsemblePlacementPolicy.initialize(IsolatedBookieEnsemblePlacementPolicy.java:51)
at org.apache.bookkeeper.client.BookKeeper.initializeEnsemblePlacementPolicy(BookKeeper.java:583)
at org.apache.bookkeeper.client.BookKeeper.(BookKeeper.java:507)
at org.apache.bookkeeper.client.BookKeeper$Builder.build(BookKeeper.java:307)
at org.apache.pulsar.broker.BookKeeperClientFactoryImpl.create(BookKeeperClientFactoryImpl.java:83)
at org.apache.pulsar.broker.ManagedLedgerClientFactory.lambda$initialize$0(ManagedLedgerClientFactory.java:97)
at org.apache.pulsar.broker.ManagedLedgerClientFactory$$Lambda$715/0x0000000801192fb8.apply(Unknown Source)
at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(java.base@17.0.5/ConcurrentHashMap.java:1708)
- locked <0x0000100015aa9f60> (a java.util.concurrent.ConcurrentHashMap$ReservationNode)
at org.apache.pulsar.broker.ManagedLedgerClientFactory.lambda$initialize$1(ManagedLedgerClientFactory.java:95)
at org.apache.pulsar.broker.ManagedLedgerClientFactory$$Lambda$187/0x0000000800edc080.get(Unknown Source)
at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.lambda$asyncOpen$6(ManagedLedgerFactoryImpl.java:373)
at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl$$Lambda$709/0x0000000801186698.apply(Unknown Source)
at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(java.base@17.0.5/ConcurrentHashMap.java:1708)
- locked <0x0000100014f25a88> (a java.util.concurrent.ConcurrentHashMap$ReservationNode)
at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.asyncOpen(ManagedLedgerFactoryImpl.java:369)
at org.apache.pulsar.broker.service.BrokerService.lambda$createPersistentTopic$54(BrokerService.java:1429)
at org.apache.pulsar.broker.service.BrokerService$$Lambda$707/0x000000080117f898.accept(Unknown Source)
at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@17.0.5/CompletableFuture.java:757)
at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@17.0.5/CompletableFuture.java:735)
at java.util.concurrent.CompletableFuture.thenAccept(java.base@17.0.5/CompletableFuture.java:2182)
at org.apache.pulsar.broker.service.BrokerService.createPersistentTopic(BrokerService.java:1407)
at org.apache.pulsar.broker.service.BrokerService.lambda$checkOwnershipAndCreatePersistentTopic$49(BrokerService.java:1375)
at org.apache.pulsar.broker.service.BrokerService$$Lambda$698/0x000000080117a5c0.accept(Unknown Source)
at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@17.0.5/CompletableFuture.java:757)
at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@17.0.5/CompletableFuture.java:735)
at java.util.concurrent.CompletableFuture.thenAccept(java.base@17.0.5/CompletableFuture.java:2182)
at org.apache.pulsar.broker.service.BrokerService.checkOwnershipAndCreatePersistentTopic(BrokerService.java:1377)
at org.apache.pulsar.broker.service.BrokerService.lambda$loadOrCreatePersistentTopic$46(BrokerService.java:1350)
at org.apache.pulsar.broker.service.BrokerService$$Lambda$708/0x00000008011af880.run(Unknown Source)
at java.util.concurrent.CompletableFuture.uniRunNow(java.base@17.0.5/CompletableFuture.java:819)
at java.util.concurrent.CompletableFuture.uniRunStage(java.base@17.0.5/CompletableFuture.java:803)
at java.util.concurrent.CompletableFuture.thenRun(java.base@17.0.5/CompletableFuture.java:2195)
at org.apache.pulsar.broker.service.BrokerService.loadOrCreatePersistentTopic(BrokerService.java:1346)
at org.apache.pulsar.broker.service.BrokerService.lambda$getTopic$23(BrokerService.java:991)
at org.apache.pulsar.broker.service.BrokerService$$Lambda$701/0x00000008011ae8e8.apply(Unknown Source)
at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap$Section.put(ConcurrentOpenHashMap.java:404)
at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap.computeIfAbsent(ConcurrentOpenHashMap.java:238)
at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:990)
at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:952)
at org.apache.pulsar.broker.service.BrokerService.getTopicIfExists(BrokerService.java:944)
at org.apache.pulsar.broker.admin.impl.PersistentTopicsBase.lambda$internalCreateNonPartitionedTopicAsync$49(PersistentTopicsBase.java:530)
at org.apache.pulsar.broker.admin.impl.PersistentTopicsBase$$Lambda$616/0x000000080113d660.apply(Unknown Source)
at java.util.concurrent.CompletableFuture$UniCompose.tryFire(java.base@17.0.5/CompletableFuture.java:1150)
at java.util.concurrent.CompletableFuture.postComplete(java.base@17.0.5/CompletableFuture.java:510)
at java.util.concurrent.CompletableFuture.complete(java.base@17.0.5/CompletableFuture.java:2147)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleGetResult(ZKMetadataStore.java:262)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$8(ZKMetadataStore.java:212)
at org.apache.pulsar.metadata.impl.ZKMetadataStore$$Lambda$162/0x0000000800e8a448.processResult(Unknown Source)
at org.apache.pulsar.metadata.impl.PulsarZooKeeperClient$3$1.processResult(PulsarZooKeeperClient.java:489)
at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:712)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:553)
Locked ownable synchronizers:
- None
`
in the broker log above, we can see zk client has replied request, but ZKMetadataStore still disconnect. In the stack of zk EventThread, we know that EventThread got block in IsolatedBookieEnsemblePlacementPolicy.initialize(IsolatedBookieEnsemblePlacementPolicy.java:91) .

in source code, we can see creating bookie client must wait until getting the node "/bookies" succeed from the cache. if  node "/bookies" is not in cache, ZKMetadataStore will get it from zk. However, creating bookie client is running in the zk EventThread, and waiting for getting node  "/bookies" complete, and the callback getting node "/bookies" from zk must run in EventThread。it will appear deadlock in this situation
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

https://github.com/apache/pulsar/pull/20303 handles a related issue that is possibly solve this one also.
cc @poorbarcode

https://github.com/apache/pulsar/pull/20303 handles a related issue that is possibly solving this one also.

No, the PR https://github.com/apache/pulsar/pull/20303 is not helpful for this issue. I'll take note of the issue and will try to fix it later.

https://github.com/apache/pulsar/pull/21096 has fixed this issue


Update dns-ownership documentation.

Adapter has been updated: Passing type as TXT is no longer needed.
Ethereum job cost changed from 1 LINK to 2 LINK.

hello @1marcghannam
thanks so much for the PR. Indeed I'm able to get a response using the fixes that you suggested.
Just for my understanding: How do you map an IP address to an Ethereum address ?
This is the response I get from https://dns.google/resolve?name=www5.infernos.io:
{
  "Status": 0,
  "TC": false,
  "RD": true,
  "RA": true,
  "AD": false,
  "CD": false,
  "Question": [
    {
      "name": "www5.infernos.io.",
      "type": 1
    }
  ],
  "Answer": [
    {
      "name": "www5.infernos.io.",
      "type": 1,
      "TTL": 300,
      "data": "<IP_ADDRESS>"
    },
    {
      "name": "www5.infernos.io.",
      "type": 1,
      "TTL": 300,
      "data": "<IP_ADDRESS>"
    }
  ],
  "Comment": "Response from <IP_ADDRESS>."
}

Additional info: similar PR still in review https://github.com/smartcontractkit/external-adapters-js/pull/1658

Hello @aelmanaa ,
I appreciate the review. Your query is missing type parameter which is always set to TXT.
The correct query should be https://dns.google/resolve?name=www5.infernos.io&type=TXT with response:
{
    "Status": 0,
    "TC": false,
    "RD": true,
    "RA": true,
    "AD": false,
    "CD": false,
    "Question": [
        {
            "name": "www5.infernos.io.",
            "type": 16
        }
    ],
    "Answer": [
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x2ffb3d72fa6af12af5d378df0697a2bf9f45652e"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x4d3407ddfdeb3feb4e8a167484701aced7056826"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xeb9abc589734ce8051f089cf3498e230456a85dd"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xf75519f611776c22275474151a04183665b7feDe"
        }
    ],
    "Comment": "Response from <IP_ADDRESS>."
}

Hello @aelmanaa ,
I appreciate the review. Your query is missing type parameter which is always set to TXT. The correct query should be https://dns.google/resolve?name=www5.infernos.io&type=TXT with response:
{
    "Status": 0,
    "TC": false,
    "RD": true,
    "RA": true,
    "AD": false,
    "CD": false,
    "Question": [
        {
            "name": "www5.infernos.io.",
            "type": 16
        }
    ],
    "Answer": [
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x2ffb3d72fa6af12af5d378df0697a2bf9f45652e"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x4d3407ddfdeb3feb4e8a167484701aced7056826"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xeb9abc589734ce8051f089cf3498e230456a85dd"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xf75519f611776c22275474151a04183665b7feDe"
        }
    ],
    "Comment": "Response from <IP_ADDRESS>."
}

Thanks for the info @1marcghannam !
Just made a few updates:

Update the solidity contract accordingly
Write a guide so it is easy for users to test in one-click
Fixed some broken links

Is your node still using V1? The Tasks section mentions V1 (e.g.: https://docs.chain.link/docs/core-adapters/#copy). If you are node operates on V2 then we should update the section accordingly, mentioning the right V2 tasks.

Hello @aelmanaa ,
I appreciate the review. Your query is missing type parameter which is always set to TXT. The correct query should be https://dns.google/resolve?name=www5.infernos.io&type=TXT with response:
{
    "Status": 0,
    "TC": false,
    "RD": true,
    "RA": true,
    "AD": false,
    "CD": false,
    "Question": [
        {
            "name": "www5.infernos.io.",
            "type": 16
        }
    ],
    "Answer": [
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x2ffb3d72fa6af12af5d378df0697a2bf9f45652e"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0x4d3407ddfdeb3feb4e8a167484701aced7056826"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xeb9abc589734ce8051f089cf3498e230456a85dd"
        },
        {
            "name": "www5.infernos.io.",
            "type": 16,
            "TTL": 300,
            "data": "0xf75519f611776c22275474151a04183665b7feDe"
        }
    ],
    "Comment": "Response from <IP_ADDRESS>."
}

Thanks for the info @1marcghannam ! Just made a few updates:

Updated the solidity contract accordingly
Wrote a guide so it is easy for users to test in one-click
Fixed some broken links

Is your node still using V1? The Tasks section mentions V1 (e.g.: https://docs.chain.link/docs/core-adapters/#copy). If you are node operates on V2 then we should update the section accordingly, mentioning the right V2 tasks.

Thank you for the updates @aelmanaa ,
We are using V2 tasks in the updated jobs.
type = "directrequest"
schemaVersion = 1
contractAddress = "0x0000000000000000000000000000000000000000"
maxTaskDuration = "0s"
observationSource = """
    decode_log          [type=ethabidecodelog
                         abi="OracleRequest(bytes32 indexed specId, address requester, bytes32 requestId, uint256 payment, address callbackAddr, bytes4 callbackFunctionId, uint256 cancelExpiration, uint256 dataVersion, bytes data)"
                         data="$(jobRun.logData)"
                         topics="$(jobRun.logTopics)"]

    decode_cbor         [type=cborparse data="$(decode_log.data)"]

    dnsproof            [type=bridge
                         name="dnsproof"
                         requestData="{\\"data\\": {\\"endpoint\\": \\"dnsProof\\", \\"name\\": $(decode_cbor.name), \\"record\\": $(decode_cbor.record)}}"]

    result_parse        [type=jsonparse data="$(dnsproof)" path="result"]

    encode_data         [type=ethabiencode
                         abi="(bool _result)"
                         data="{\\"_requestId\\": $(decode_log.requestId),\\"_result\\": $(result_parse)}"]

    encode_tx           [type=ethabiencode
                         abi="fulfillOracleRequest(bytes32 requestId, uint256 payment, address callbackAddress, bytes4 callbackFunctionId, uint256 expiration, bytes32 data)"
                         data="{\\"requestId\\": $(decode_log.requestId),\\"payment\\": $(decode_log.payment),\\"callbackAddress\\": $(decode_log.callbackAddr),\\"callbackFunctionId\\": $(decode_log.callbackFunctionId),\\"expiration\\": $(decode_log.cancelExpiration),\\"data\\": $(encode_data)}"]

    submit_tx           [type=ethtx to="0x0000000000000000000000000000000000000000" data="$(encode_tx)" minConfirmations="2"]

    decode_log -> decode_cbor -> dnsproof -> result_parse -> encode_data -> encode_tx -> submit_tx
"""

@1marcghannam  you can check the new page here:
https://documentation-git-fork-1marcghannam-patch-1-chainlinklabs.vercel.app/docs/dns-ownership-oracle#dns-ownership-contract
Are you happy with the result? If yes then will merge so it is live


feat (RingTheory/PowerSeries) add formal derivative operation

Give a commutative semiring R, define the formal derivative R[[X]] \to R[[X]] and prove some basic properties.
This is a part of PR 7271.

FYI you can link other PRs and issues with #7271 -> #7271

Looking at polynomial we call the derivative as derivation Polynomial.derivative'. The ' is an artifact of the fact that we have the unprimed version, but I think you should follow the same convention (i.e. remove the f from the name). I will have a closer look later today, but thanks!

bors r+


[SMALLFIX] Correctly clean up aborted writes

Since the control path is tied to the channel, we cannot close the channel (commit blocks) until the entire file is ready.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15158/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15156/
Test PASSed.

LGTM


Maximum number of results in drop down list

In case of using Select2 for tagging, there should be an option to limit numbers of results in drop down list.
I've made up my own solution for this issue, hope somebody can improve it
populateResults: function(container, results, query) {
    ...
    // get maxResults from user defined parameters
    var maxResults = this.opts.maxResults;
    ...
    populate = function(results, container, depth, maxResults) {
        // maximum number of loop iteration must be smaller than (or equal to) actual number of results
        maxResults = (maxResults === null) ? results.length : Math.min(results.length, maxResults);

        var i, l, result, selectable, compound, node, label, innerContainer, formatted;
        for (i = 0, l = results.length; i < maxResults; i = i + 1) {
            ...
        }
    };
    populate(results, container, 0, maxResults);
}

Chosen has such an option called max_shown_results. It is quite useful if you have a lot of options and don't use AJAX. Can this option be reconsidered for inclusion?

Found this issue when loading 2000+ items via JSON (without AJAX).  It's more efficient to load the data one time, minified into the JS of the page, because I have various fields with the same data.  However, the performance is crushed because select2 renders all the items each time the select menu appears.
As @siccovansas suggests, an option to limit the number of shown results would be the solution, so +1 to that.

This is especially problematic when using an image in the templateResult. If you have 200 items, 200 images try to load at the same time.

FYI I found this to work better:
                if (data.results.length > opts.maximumResultsForSearch) {
                      render("
Please enter more characters
");
                      if (initial && this.showSearch) this.showSearch(true);
                      return;
                }
//just before this existing code
                if (data.results.length === 0 && checkFormatter(opts.formatNoMatches, "formatNoMatches")) {
                    render("
" + opts.formatNoMatches(search.val()) + "
");
                    return;
                }

hi bro
how i can use this code?


remove invalid version test for GET_VERSION

Fix: https://github.com/DMTF/SPDM-Responder-Validator/issues/124

The fix for emu is at https://github.com/DMTF/spdm-emu/pull/340


Search or Filter of breadcrumb disappears when nothing matches

It provides a yellow warning with "No Elements Found"

Create example.js file.
Enter something simple, like const a = 'b';.
Open breadcrumbs list.
Hit Ctrl(Cmd)+F.
Enable filter (that's the only useful mode for this list).
Start typing qqq.

Well, now… you're in limbo. Your editor stopped responding to keyboard and you are not quite sure, how to get control back. Esc doesn't work.

Originally posted by @AnrDaemon in https://github.com/microsoft/vscode/issues/157986#issuecomment-1222473783

This also happens if step 5 is omitted and Search mode is used.
The problem seems to be that to put the 'No elements found.' warning message under the find-in-list's input widget a ContextView is created immediately below it. But when find is occurring in a breadcrumb list, that list is itself in a ContextView which gets hidden and cleared immediately before the one for the warning message is shown. The warning message appears in the top left of the VS Code window in a very narrow column. See below, where I open keybindings.json, click on the filename in the breadcrumb to get a list of sibling filenames, then type "z" which isn't present in any of the filenames.


Fix for #3992: Add check for custom command in redhat service provider

Fixing https://github.com/chef/chef/issues/3992
Instead of just checking for the missing service, check if a custom command was provided for the action as well. If neither is provided throw Chef::Exceptions::Service pointing at a missing init.d script or custom command for action.

Seems reasonable. :+1:

fwiw, I tested this locally and it works for our case, as I expected it would.

@lamont-granquist, @jkeiser, can you take a look?

LGTM :+1:
@chef/client-core could use review.

LGTM :+1:


Offline Error

Hello, i runned this script on W10.
But everytime getting offline. When i check on chrome typing link.  I seen the streamer is online. How is that possible?

This is your account status.


Better Web Interface Design

Description
When I wrote the web interface, I only aimed to get it up and running. The code could definitely use some cleaning up and beautification from someone with a good amount of design and frontend experience.
Code is here on the repo
Requirements

Add CSS to the web interface
Improve the overall look of the interface
Clean up existing code if necessary

Closed with #91


How can i install? I ran pod 'ChromaColorPicker' and put the files on there, but i can't import ChromaColorPicker

Could you provide a little more detail
Which installation method did you use?
Did you add the framework to your target?

Closing this issue. If there are continued problems, please open another ticket with more details.


Default Dashboard: Google Ads Clickthrough Rate (CTR)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1735
Originally created by @dmor on 2020-02-13 21:00:46

Definition of "Clickthrough Rate (CTR)":

The percentage of time people saw your ads and performed an inline link click.

Label: CTR (Link Click-Through)
Calculation: Inline Link Clicks divided by Impressions, bounded by some time period
MVC Scope: This will only be at the account level.
https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#ctr

View 5 previous comments from the original issue on GitLab


Added Curve

please add the screenshot of space running status

please add the screenshot of space running status

Added


removeFilter

If a song has quotation marks, the removeFilter function break because it will not be able to perform JSON.parse(). To replicate the bug, type in idol in the inputbox.

possible solution:
we use str.indexOf() to find every instance of quotation marks
we can identify the quotation marks that are a part of the json by checking the nearby charcters
for example "seconds":
it would find the first qutations mark then we could check to see if the next few characters is seconds":
same thing can be done for "lyrics":"
for the ending quotation mark for lyrics "}
we can just check for the bracket to the right of it


Update quickstart-onboard-aws.md

Fixing typo

Docs Build status updates of commit 9d9fc55:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/defender-for-cloud/quickstart-onboard-aws.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@TomJanetscheck - thanks!


Image scale is incorrect for large image if it is loaded directly

Visit demo page http://getcontenttools.com/demo
Insert an image tag to editable content in preview mode, for example , this image has size 1900x1200.
Enter edit mode and then exit edit mode, it is found that width="1900" and height="488" is added to the output img tag.
Furthermore, if you try to resize the image in edit mode, part of the image is trimmed.

Hi @Hoiy, I believe this is simply the CSS on the demo website which limits images to 780px in width, it's not a limitation of ContentTools but the design I put in place.

@anthonyjb I am not sure if it is a correct behaviour for an input img tag  (of size 1920x1200) to become  after changing to edit mode and then back to preview mode.
Moreover, the user really has no chance to see the original picture once they resized it in edit mode, only the trimmed one.

Hi @Hoiy,
Width and Height attributes
We store the width and height of the image as attributes when the image is made editable so that we can determine the aspect ratio (which is used when resizing the image), if no width/height attributes are set against the image when we make it editable we extract them from the image itself using natural/clientWidth/Height.
We set the width and height as attributes against the image on html output by default because;

this is good HTML practise (I believe) as it helps in the initial page render by indicating how much space needs to be reserved for said image (less content jumping),
and it's often useful in allowing devs to review the HTML on save for changes in image sizes that once identified are enacted as changes to the physical image, e.g for us:

we review the HTML
find images that have changed in size
generate new versions of those images at their new sizes
update the image src within the HTML to point to the newly resized images
We don't change the image on the fly purely for efficiency and simply rely on the browser scaling the image until the page changes are saved.

I'm not saying it's the correct behaviour, or even the best solution in all cases, but for our set up it works well and hence has become the default behaviour.
Having said that if this behaviour is causing an issue for your project it is possible to change it, either by patching the html method for image elements to exclude the width/height attributes on output or you could also patch the fromDOMElement method to flag whether or not the width/height was set or extracted and then have the html only output a new width/height attribute if one was originally set. If you need to do this let me know and I can provide an example of how.
Trimming
I'm not really sure what you mean by trimming the image, as per my previous comment the trimming you've highlighted in your image on the demo page only occurs because that's how the CSS is set up, it's to do with CSS nothing to do with CT.


Updated EntityDescriptions

Added support for post 1.18.2 active effects
Some fixes for active effects

Your new active effects code version checks without checking the edition type. Please review your code.

Sick


Added profile to hackbook

@Aditi22Bansal  In the "data" folder create a folder for your GitHub username and place your details in a 'username.md' file within that folder.


mbedtls-prepare-build: support generated files

Run make generated_files if necessary. This makes it easier to work with 3.x.
Also an unrelated feature I had in the pipeline: support for e.g. make tests/test_suite_cipher.run to run all the test_suite_cipher.*.exe.

@AndrzejKurek You should have write access now.


small typo in configuring-private-vulnerability-reporting-for-a-repository

Why:
typo fix

What's being changed (if available, include any code snippets, screenshots, or gifs):
creat -> create
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@psmoros Thanks for catching this and opening a PR! We actually have another PR with this fix that is just about to merge ⚡
So I'm going to go ahead and close this one as a duplicate. Thank you for your passion and interest in improving GitHub Docs! :sparkling_heart:


Update LaunchControl to 1.25.1

Thank you for the contribution. It was merged directly as e06f29b278a7d0860d26da4277c354703a8f4844 to keep commit history cleaner. Your contribution is still credited to you.


Text Field Alignment Issues?

We are having an issue where we are using this class in a tableview cell. During text entry, the vertical spacing is different from the field when it is not being edited.
As shown in the screen shot, you can see a difference when editing the text and not.

Thanks in advance.

@CMoebius have you tried setting the keepBaseline property?

Yes, and all that did was drop the text field to the bottom of the table view cell when editing.

I think that's what you would want to do in order to make sure that editing vs. not editing are at the same position. Then, you can use other means to pad around the text field so that it is positioned how you'd like.


Update documentation to use new runner configurations

Update documentation for Axual Runner
Fix final examples

Merged because the missing documentation was needed


CSS is included in SSR builds

Describe the bug
CSS is included in SSR builds, which is unexpected: CSS is useless on the server-side. (You can actually see that the CSS included in the SSR build is unused.)
Reproduction
https://github.com/brillout/vite-bug-css-included-in-ssr-build
System Info
System:
    OS: Linux 5.10 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (2) x64 Intel(R) Celeron(R) N4020 CPU @ 1.10GHz
    Memory: 413.73 MB / 2.71 GB
    Container: Yes
    Shell: 5.0.3 - /bin/bash
  Binaries:
    Node: 18.0.0 - ~/.config/nvm/versions/node/v18.0.0/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.6.0 - ~/.config/nvm/versions/node/v18.0.0/bin/npm
  Browsers:
    Firefox: 97.0.1

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is more important than I initially thought.
Because it considerably increases the bundle size of server-side builds, which is critical for edge platforms such as Cloudflare Workers.
A workaround would be to use a code pruning tool that removes unused variables: AFAICT that should do the trick to remove the CSS form the server build.
@benmccann I think SvelteKit may want to know about this.

@sapphi-red I tagged you in a thread in discord started by @bluwy, that also found memory issues possibly related to #8278. I think we should revert v2, yes, PR welcome if you can.
And for v3, I don't know about the implications of forcing minification. Maybe we should revert it too and then test with more time for v3.1
Also, I wonder if we could bail out of CSS a lot sooner in SSR so we don't need to process them (in the same lines of https://github.com/vitejs/vite/pull/8454)

memory issues

That may explain https://github.com/vitejs/vite/issues/8715.
(My guess was that there was a problem with too much memory consumption. Note that it happened with the Vite 3 alphas but not with the Vite 3 betas, I don't know why.)

Also, I wonder if we could bail out of CSS a lot sooner in SSR so we don't need to process them (in the same lines of https://github.com/vitejs/vite/pull/8454)

👍

Closing as it is fixed by https://github.com/vitejs/vite/pull/8874 (v2) and https://github.com/vitejs/vite/pull/8896 (v3).


Search

Probably lunr.js?

After some research, there are lots of options. Of all the options, these were the standouts for this project:

Lunr - relatively simple to setup and use; not relatively fast or efficient
Elasticlunr - some extra options and a bit faster without much difference to Lunr's API
FlexSearch - billed as the fastest of the JS search libraries, has a much broader feature set over and above Lunr or Elasticlunr (including the option for workers, server-side indexing etc); but with all of that comes further complexity of course. Perhaps good to flag for further down the road/larger docs projects.

However all of these have one thing in common - we plan to use them client-side. This means, one way or another, downloading the entire site index to the client every time they load a page with a search box. I have some ideas to minimise this (autocomplete on most pages uses a separate, limited index, then full text search on dedicated page only), but it is not ideal for sites with 100+ pages to index.
An alternative to all of this is Algolia's DocSearch service - extremely simple to setup, they look after the indexing (re-indexed once every 24hrs) and entirely free for open source projects. It does require an "approval" process of sorts and each clone of this starter would be it's own site (risking it not being approved for whatever reason), but definitely worth keeping as an option.
I will talk through all of this with you in more detail, including how we might go about building an index for use with those client-side libraries.

FlexSearch :-)

Noting for future reference: https://healeycodes.com/webassembly-search-tools-for-static-websites/
WASM looks like it offer advantages, BUT:

Stork still loads a large index
Causes additional dependencies (Rust, probably) which greatly complicate the initial experience

So I'm swinging back to lunr I think. Making some notes because I won't remember this tomorrow:

Generate a JSON file of all the site content
Generate a lunr.js serialised index https://lunrjs.com/guides/index_prebuilding.html
Create a frontent (probably not trivial)

Example of how to generate initial JSON: https://github.com/philhawksworth/eleventyone/blob/master/src/site/search.njk