PHPStan Cache Not Utilized in v3.0.1 on Mac with PHP 8.3

First of all: Thanks for the great plugin!
I've encountered an issue with PHPStan cache not being utilized while running version 3.0.1 on a Mac with PHP 8.3. It seems that every file is rechecked upon saving, leading to significant cpu spikes. This behavior is also seen at the progress bar, which indicates that all files undergo checking on each save.
When executing vendor/bin/phpstan directly from the terminal, the cache is recognized and used, resulting in a much faster process.
Could you advise on any additional information or logs that would be helpful for diagnosing this issue?
Thanks for your help.

Hey thanks for the report. Could you do the following for me?

Share the logs of the extension when the issue occurs. They're shown in the Output panel under PHPStan Client. Ideally running it a couple of times.
Look for the line "Spawning PHPStan with the following configuration" and run the shown command in your terminal. Can you check whether the issue then still occurs, or if some warning of some sort is outputted?

Thanks!

I've got the same problem (but with PHP 8.1 on a M2 mac). The log:
[check:42] Check started for project
[status-bar] Showing status bar
[file-watcher] Document changed, triggering
[check:43] Check started for project
[fixer-manager] No file changes, not checking
[check:42] Check completed for project, errors= {"fileSpecificErrors":{},"notFileSpecificErrors":[]}
[check:43] Spawning PHPStan with the following configuration:  {"binStr":"/[redacted]/vendor/bin/phpstan","args":["analyse","-c","/[redacted]/phpstan.neon","--error-format=json","--no-interaction","--memory-limit=1G","-a","/[redacted]/.vscode/extensions/sanderronde.phpstan-vscode-3.0.3/_config/autoload.php","-c","/[redacted]/.vscode/extensions/sanderronde.phpstan-vscode-3.0.3/_config/config.neon"]}
[process-spawner] Spawning process 86896 with timeout 900000

The output:
$ vendor/bin/phpstan analyse -c /[redacted]/phpstan.neon --error-format=json --no-interaction --memory-limit=1G -a /[redacted]/.vscode/extensions/sanderronde.phpstan-vscode-3.0.3/_config/autoload.php -c /[redacted]/.vscode/extensions/sanderronde.phpstan-vscode-3.0.3/_config/config.neon
 396/396 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

{"totals":{"errors":1,"file_errors":0},"files":[],"errors":["<error>Child process error</error> (exit code 1): Error: Unable to encode JSON: Recursion detected\n"]}%

PHPStan version: 1.10.60
PHP version: 8.1.23
Extension version: 3.0.3
VS Code version: 1.87.1
OS: macOS 13.6.3 (M2 MacBook Air)

Could you try disabling the phpstan.enableLanguageServer setting. Does it still occur then?

Without phpstan.enableLanguageServer enabled, everything is fast and quick.

Ah good to know. Then I guess my recommendation is to disable that option. It only provides on-hover information and is not actually needed for type-checking.
Going further I've disabled that option by default in the pre-release version of the extension so it'll be opt-in instead.
I'll close this issue for now, maybe I'll spend more time getting the hover-provider feature to work without busting the cache on macs but that'll be kind of hard. So for now just "disable that setting" will do.


Add ability to save state in app

The app currently does not save any information on the selections made during a session, meaning that it will reset if the tab is reloaded or the user is disconnected. A button could be added to save the current selections made to a .rds file that can be loaded at startup, after which all inputs with selections will be updated to match the selections saved in the file.

Ana asked for this feature recently.

It might be better to have a save/load function that would download YAML files with browser state information. In addition to this being able to work regardless if Shiny server being used, a user could save multiple files for different analyses. The users could also send these files to us for bug reporting.


Generic keynames in Pagination

Description of issue:

In Pagination, item here is often a number.
App developers often have numbers as keynames (they shouldn't, but it's a common mistake).  I think it's best to rename this just to get out their way.

Component in question (if applicable):

pagination

Metronome Link (if applicable):

Metronome

Figma Link (if applicable):

Figma

Closing as dup of UX-234

Closing as dup of UX-234


Update UiSettings in ui-core to correct release tag

/azp run

@calebmshafer why don't the build jobs run? What does "Expected — Waiting for status to be reported" mean?

/azp run

/azp run

@kabentley they don't run by default for Draft PRs. Right now, /azp run doesn't queue the regular builds either, it starts the public build instead.


Build error with cargo prove build-toolchain

I followed the building-from-source document to install SP1, I get an error when doing cargo prove build-toolchain.
Here is the OS context:
% sw_vers
ProductName:		macOS
ProductVersion:		14.3
BuildVersion:		23D56

% uname -m
x86_64

Here are the logs:

niu@Spartucus cli % cargo prove build-toolchain
No SP1_BUILD_DIR detected, cloning rust.
No GITHUB_ACCESS_TOKEN detected. If you get throttled by Github, set it to bypass the rate limit.
Cloning into 'rust'...
remote: Enumerating objects: 2425039, done.
remote: Counting objects: 100% (7778/7778), done.
remote: Compressing objects: 100% (93/93), done.
remote: Total 2425039 (delta 7736), reused 7694 (delta 7685), pack-reused 2417261
Receiving objects: 100% (2425039/2425039), 1.14 GiB | 5.66 MiB/s, done.
Resolving deltas: 100% (1901494/1901494), done.
Updating files: 100% (44291/44291), done.
Already on 'rustc-1.75'
Your branch is up to date with 'origin/rustc-1.75'.
HEAD is now at 99671f9ea25 rename curta to succinct
Submodule 'library/backtrace' (https://github.com/rust-lang/backtrace-rs.git) registered for path 'library/backtrace'
Submodule 'library/stdarch' (https://github.com/rust-lang/stdarch.git) registered for path 'library/stdarch'
Submodule 'src/doc/book' (https://github.com/rust-lang/book.git) registered for path 'src/doc/book'
Submodule 'src/doc/edition-guide' (https://github.com/rust-lang/edition-guide.git) registered for path 'src/doc/edition-guide'
Submodule 'src/doc/embedded-book' (https://github.com/rust-embedded/book.git) registered for path 'src/doc/embedded-book'
Submodule 'src/doc/nomicon' (https://github.com/rust-lang/nomicon.git) registered for path 'src/doc/nomicon'
Submodule 'src/doc/reference' (https://github.com/rust-lang/reference.git) registered for path 'src/doc/reference'
Submodule 'src/doc/rust-by-example' (https://github.com/rust-lang/rust-by-example.git) registered for path 'src/doc/rust-by-example'
Submodule 'src/doc/rustc-dev-guide' (https://github.com/rust-lang/rustc-dev-guide.git) registered for path 'src/doc/rustc-dev-guide'
Submodule 'src/llvm-project' (https://github.com/rust-lang/llvm-project.git) registered for path 'src/llvm-project'
Submodule 'src/tools/cargo' (https://github.com/rust-lang/cargo.git) registered for path 'src/tools/cargo'
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/library/backtrace'...
remote: Enumerating objects: 149, done.
remote: Counting objects: 100% (149/149), done.
remote: Compressing objects: 100% (113/113), done.
remote: Total 149 (delta 6), reused 99 (delta 5), pack-reused 0
Receiving objects: 100% (149/149), 113.86 KiB | 588.00 KiB/s, done.
Resolving deltas: 100% (6/6), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/library/stdarch'...
remote: Enumerating objects: 312, done.
remote: Counting objects: 100% (312/312), done.
remote: Compressing objects: 100% (258/258), done.
remote: Total 312 (delta 50), reused 134 (delta 21), pack-reused 0
Receiving objects: 100% (312/312), 1.18 MiB | 3.23 MiB/s, done.
Resolving deltas: 100% (50/50), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/book'...
remote: Enumerating objects: 2475, done.
remote: Counting objects: 100% (2475/2475), done.
remote: Compressing objects: 100% (1399/1399), done.
remote: Total 2475 (delta 617), reused 2139 (delta 591), pack-reused 0
Receiving objects: 100% (2475/2475), 3.52 MiB | 7.44 MiB/s, done.
Resolving deltas: 100% (617/617), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/edition-guide'...
remote: Enumerating objects: 48, done.
remote: Counting objects: 100% (48/48), done.
remote: Compressing objects: 100% (38/38), done.
remote: Total 48 (delta 5), reused 19 (delta 5), pack-reused 0
Receiving objects: 100% (48/48), 44.83 KiB | 483.00 KiB/s, done.
Resolving deltas: 100% (5/5), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/embedded-book'...
fatal: unable to access 'https://github.com/rust-embedded/book.git/': LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
fatal: clone of 'https://github.com/rust-embedded/book.git' into submodule path '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/embedded-book' failed
Failed to clone 'src/doc/embedded-book'. Retry scheduled
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/nomicon'...
remote: Enumerating objects: 81, done.
remote: Counting objects: 100% (81/81), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 81 (delta 0), reused 27 (delta 0), pack-reused 0
Receiving objects: 100% (81/81), 146.97 KiB | 723.00 KiB/s, done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/reference'...
remote: Enumerating objects: 145, done.
remote: Counting objects: 100% (145/145), done.
remote: Compressing objects: 100% (136/136), done.
remote: Total 145 (delta 0), reused 42 (delta 0), pack-reused 0
Receiving objects: 100% (145/145), 271.02 KiB | 1.06 MiB/s, done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/rust-by-example'...
remote: Enumerating objects: 265, done.
remote: Counting objects: 100% (265/265), done.
remote: Compressing objects: 100% (252/252), done.
remote: Total 265 (delta 0), reused 108 (delta 0), pack-reused 0
Receiving objects: 100% (265/265), 185.03 KiB | 1.11 MiB/s, done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/rustc-dev-guide'...
remote: Enumerating objects: 244, done.
remote: Counting objects: 100% (244/244), done.
remote: Compressing objects: 100% (233/233), done.
remote: Total 244 (delta 3), reused 104 (delta 3), pack-reused 0
Receiving objects: 100% (244/244), 2.21 MiB | 4.44 MiB/s, done.
Resolving deltas: 100% (3/3), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/llvm-project'...
remote: Enumerating objects: 3, done.
remote: Counting objects: 100% (3/3), done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 3 (delta 0), reused 2 (delta 0), pack-reused 0
Receiving objects: 100% (3/3), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/tools/cargo'...
remote: Enumerating objects: 2309, done.
remote: Counting objects: 100% (2309/2309), done.
remote: Compressing objects: 100% (1564/1564), done.
remote: Total 2309 (delta 615), reused 1602 (delta 508), pack-reused 0
Receiving objects: 100% (2309/2309), 4.01 MiB | 4.02 MiB/s, done.
Resolving deltas: 100% (615/615), done.
Cloning into '/Users/niu/work/code/zkvm/sp1/cli/rust/src/doc/embedded-book'...
remote: Enumerating objects: 85, done.
remote: Counting objects: 100% (85/85), done.
remote: Compressing objects: 100% (75/75), done.
remote: Total 85 (delta 0), reused 30 (delta 0), pack-reused 0
Receiving objects: 100% (85/85), 655.52 KiB | 1.59 MiB/s, done.
remote: Enumerating objects: 4649, done.
remote: Counting objects: 100% (4649/4649), done.
remote: Compressing objects: 100% (1408/1408), done.
remote: Total 4543 (delta 3005), reused 4408 (delta 2942), pack-reused 0
Receiving objects: 100% (4543/4543), 1.16 MiB | 4.28 MiB/s, done.
Resolving deltas: 100% (3005/3005), completed with 69 local objects.
From https://github.com/rust-lang/backtrace-rs
 * branch            6145fe6bac65c38375f1216a565a6cc7deb89a2d -> FETCH_HEAD
Submodule path 'library/backtrace': checked out '6145fe6bac65c38375f1216a565a6cc7deb89a2d'
remote: Enumerating objects: 16795, done.
remote: Counting objects: 100% (16794/16794), done.
remote: Compressing objects: 100% (3952/3952), done.
remote: Total 16533 (delta 12354), reused 16120 (delta 12011), pack-reused 0
Receiving objects: 100% (16533/16533), 11.26 MiB | 18.10 MiB/s, done.
Resolving deltas: 100% (12354/12354), completed with 181 local objects.
From https://github.com/rust-lang/stdarch
 * branch              f4528dd6e85d97bb802240d7cd048b6e1bf72540 -> FETCH_HEAD
Submodule path 'library/stdarch': checked out 'f4528dd6e85d97bb802240d7cd048b6e1bf72540'
remote: Enumerating objects: 31753, done.
remote: Counting objects: 100% (31744/31744), done.
remote: Compressing objects: 100% (9574/9574), done.
remote: Total 30418 (delta 20709), reused 29718 (delta 20028), pack-reused 0
Receiving objects: 100% (30418/30418), 32.75 MiB | 16.67 MiB/s, done.
Resolving deltas: 100% (20709/20709), completed with 485 local objects.
From https://github.com/rust-lang/book
 * branch              5b6c1ceaa62ecbd6caef08df39b33b3938e99deb -> FETCH_HEAD
Submodule path 'src/doc/book': checked out '5b6c1ceaa62ecbd6caef08df39b33b3938e99deb'
remote: Enumerating objects: 2668, done.
remote: Counting objects: 100% (2668/2668), done.
remote: Compressing objects: 100% (898/898), done.
remote: Total 2638 (delta 1724), reused 2566 (delta 1692), pack-reused 0
Receiving objects: 100% (2638/2638), 474.28 KiB | 1.44 MiB/s, done.
Resolving deltas: 100% (1724/1724), completed with 22 local objects.
From https://github.com/rust-lang/edition-guide
 * branch            34fca48ed284525b2f124bf93c51af36d6685492 -> FETCH_HEAD
Submodule path 'src/doc/edition-guide': checked out '34fca48ed284525b2f124bf93c51af36d6685492'
remote: Enumerating objects: 2372, done.
remote: Counting objects: 100% (2372/2372), done.
remote: Compressing objects: 100% (781/781), done.
remote: Total 2310 (delta 1499), reused 2220 (delta 1426), pack-reused 0
Receiving objects: 100% (2310/2310), 615.25 KiB | 1.65 MiB/s, done.
Resolving deltas: 100% (1499/1499), completed with 48 local objects.
From https://github.com/rust-embedded/book
 * branch            22bca3d0f6e9b9b556689b54ce96f25b46ecd1b3 -> FETCH_HEAD
Submodule path 'src/doc/embedded-book': checked out '22bca3d0f6e9b9b556689b54ce96f25b46ecd1b3'
remote: Enumerating objects: 2726, done.
remote: Counting objects: 100% (2726/2726), done.
remote: Compressing objects: 100% (887/887), done.
remote: Total 2661 (delta 1889), reused 2504 (delta 1753), pack-reused 0
Receiving objects: 100% (2661/2661), 1.14 MiB | 3.85 MiB/s, done.
Resolving deltas: 100% (1889/1889), completed with 54 local objects.
From https://github.com/rust-lang/nomicon
 * branch<PHONE_NUMBER>919fa62e81bdecd5e8f95be2839dbb -> FETCH_HEAD
Submodule path 'src/doc/nomicon': checked out '1842257814919fa62e81bdecd5e8f95be2839dbb'
remote: Enumerating objects: 11362, done.
remote: Counting objects: 100% (11362/11362), done.
remote: Compressing objects: 100% (3222/3222), done.
remote: Total 11233 (delta 8260), reused 10841 (delta 7980), pack-reused 0
Receiving objects: 100% (11233/11233), 3.71 MiB | 9.25 MiB/s, done.
Resolving deltas: 100% (8260/8260), completed with 113 local objects.
From https://github.com/rust-lang/reference
 * branch            cd8193e972f61b92117095fc73b67af767b4d6bc -> FETCH_HEAD
Submodule path 'src/doc/reference': checked out 'cd8193e972f61b92117095fc73b67af767b4d6bc'
remote: Enumerating objects: 14471, done.
remote: Counting objects: 100% (14471/14471), done.
remote: Compressing objects: 100% (6205/6205), done.
remote: Total 14228 (delta 8138), reused 13867 (delta 7802), pack-reused 0
Receiving objects: 100% (14228/14228), 3.21 MiB | 7.85 MiB/s, done.
Resolving deltas: 100% (8138/8138), completed with 195 local objects.
From https://github.com/rust-lang/rust-by-example
 * branch            311b84962016b28c75525c86e7b3f49fd9101a39 -> FETCH_HEAD
Submodule path 'src/doc/rust-by-example': checked out '311b84962016b28c75525c86e7b3f49fd9101a39'
remote: Enumerating objects: 11460, done.
remote: Counting objects: 100% (11460/11460), done.
remote: Compressing objects: 100% (2833/2833), done.
remote: Total 11261 (delta 8543), reused 11022 (delta 8324), pack-reused 0
Receiving objects: 100% (11261/11261), 3.12 MiB | 4.33 MiB/s, done.
Resolving deltas: 100% (8543/8543), completed with 172 local objects.
From https://github.com/rust-lang/rustc-dev-guide
 * branch            77dbe5782b2488af3bb489ad702eaff438f465bf -> FETCH_HEAD
Submodule path 'src/doc/rustc-dev-guide': checked out '77dbe5782b2488af3bb489ad702eaff438f465bf'
remote: Enumerating objects: 5462408, done.
remote: Counting objects: 100% (5462408/5462408), done.
remote: Compressing objects: 100% (925157/925157), done.
remote: Total 5462406 (delta 4455758), reused 5462387 (delta 4455751), pack-reused 0
Receiving objects: 100% (5462406/5462406), 1.74 GiB | 16.32 MiB/s, done.
Resolving deltas: 100% (4455758/4455758), done.
From https://github.com/rust-lang/llvm-project
 * branch                      2c4de6c2492d5530de3f19f41d8f88ba984c2fe2 -> FETCH_HEAD
Submodule path 'src/llvm-project': checked out '2c4de6c2492d5530de3f19f41d8f88ba984c2fe2'
remote: Enumerating objects: 120572, done.
remote: Counting objects: 100% (120565/120565), done.
remote: Compressing objects: 100% (31574/31574), done.
remote: Total 119281 (delta 86169), reused 118279 (delta 85327), pack-reused 0
Receiving objects: 100% (119281/119281), 36.32 MiB | 15.36 MiB/s, done.
Resolving deltas: 100% (86169/86169), completed with 668 local objects.
From https://github.com/rust-lang/cargo
 * branch                1d8b05cdd1287c64467306cf3ca2c8ac60c11eb0 -> FETCH_HEAD
Submodule path 'src/tools/cargo': checked out '1d8b05cdd1287c64467306cf3ca2c8ac60c11eb0'
Submodule path 'src/doc/embedded-book': checked out '22bca3d0f6e9b9b556689b54ce96f25b46ecd1b3'
downloading https://static.rust-lang.org/dist/2023-11-16/rust-std-1.74.0-x86_64-apple-darwin.tar.xz
######################################################################################################################################### 100.0%
downloading https://static.rust-lang.org/dist/2023-11-16/rustc-1.74.0-x86_64-apple-darwin.tar.xz
######################################################################################################################################### 100.0%
downloading https://static.rust-lang.org/dist/2023-11-16/cargo-1.74.0-x86_64-apple-darwin.tar.xz
######################################################################################################################################### 100.0%
extracting /Users/niu/work/code/zkvm/sp1/cli/rust/build/cache/2023-11-16/rustc-1.74.0-x86_64-apple-darwin.tar.xz
extracting /Users/niu/work/code/zkvm/sp1/cli/rust/build/cache/2023-11-16/rust-std-1.74.0-x86_64-apple-darwin.tar.xz
extracting /Users/niu/work/code/zkvm/sp1/cli/rust/build/cache/2023-11-16/cargo-1.74.0-x86_64-apple-darwin.tar.xz
Building bootstrap
error: current package believes it's in a workspace when it's not:
current:   /Users/niu/work/code/zkvm/sp1/cli/rust/src/bootstrap/Cargo.toml
workspace: /Users/niu/work/code/zkvm/sp1/Cargo.toml

this may be fixable by adding `cli/rust/src/bootstrap` to the `workspace.members` array of the manifest located at: /Users/niu/work/code/zkvm/sp1/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.
failed to run: /Users/niu/work/code/zkvm/sp1/cli/rust/build/x86_64-apple-darwin/stage0/bin/cargo build --manifest-path /Users/niu/work/code/zkvm/sp1/cli/rust/src/bootstrap/Cargo.toml
Build completed unsuccessfully in 0:00:16
Building bootstrap
error: current package believes it's in a workspace when it's not:
current:   /Users/niu/work/code/zkvm/sp1/cli/rust/src/bootstrap/Cargo.toml
workspace: /Users/niu/work/code/zkvm/sp1/Cargo.toml

this may be fixable by adding `cli/rust/src/bootstrap` to the `workspace.members` array of the manifest located at: /Users/niu/work/code/zkvm/sp1/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.
failed to run: /Users/niu/work/code/zkvm/sp1/cli/rust/build/x86_64-apple-darwin/stage0/bin/cargo build --manifest-path /Users/niu/work/code/zkvm/sp1/cli/rust/src/bootstrap/Cargo.toml
Build completed unsuccessfully in 0:00:00
info: no toolchain installed for 'succinct'
Succesfully removed existing toolchain.
thread 'main' panicked at cli/src/commands/build_toolchain.rs:98:43:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

same here ...

same here ...

Do cd ~ before cargo prove build-toolchain, see https://github.com/succinctlabs/sp1/pull/258.


*** Assertion failure in +[FAKIonIcons registerIconFontWithURL:],

I get the following error and I have made no changes to my code (from when this was working without error). Now I receive the following:
*** Assertion failure in +[FAKIonIcons registerIconFontWithURL:], /Applications/MAMP/htdocs/blaclist/node_modules/react-native-icons/ios/ReactNativeIcons/Libraries/FontAwesomeKit/FAKIcon.m:14
2016-02-16 01:59:22.298 blaclist[74426:56845999] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Font file doesn't exist'

I highly recommend using https://github.com/oblador/react-native-vector-icons instead as its more fully featured, I've added a warning to the Readme about this as well.


REQUIRE_THROWS_AS doesn't seem to work under certain MSVC

Description

REQUIRE_THROWS_AS() doesn't seem to catch the exception properly.
Steps to reproduce

Following test case:
auto dummy1 = 0, dummy2 = 0;

constrained_type<int*, constraints::non_null, throwing_verifier> a(&dummy1);
std::cerr << "1\n";
REQUIRE_NOTHROW((a = &dummy2, true));
std::cerr << "2\n";
REQUIRE_THROWS_AS(a = static_cast<int*>(nullptr), constrain_error);
std::cerr << "3\n";

(Taken from my type_safe library)
Results in this output on Appveyor: https://ci.appveyor.com/project/foonathan/type-safe/build/230
(very bottom, 1 is printed, 2 is printed, then abort()).

My bad, still happens after a try-catch so could be an issue on my side.

Okay, my fault, sorry about the noise.

lol - np. Glad you got it sorted (or did you?)

Yes, I did. It was a conditional noexcept that wasn't working.


Halve Hold/Roll/CPHold image size

Height of Hold/Roll/CPHold image can be halved and it may helps implement quantized hold #15.

Before and after.

Oops... image size for quantized hold will still exceed Stepmania's texture limit. (512x3072, >2048px)

or rearrange hold image layout?

How did you know 2048 is the highest that can be supproted

Graphics/Sound Options -> Texture Resolution.

I have a noteskin that is 2304 x 1152 (5.0 noteskin and the image still works)


[Doc] Convert Toolbars to use the new standard.

@oliviertassinari I had to make some modifications to your PropTypeDescription to support multiple components per page. Also I did some improvements to fix some bugs, added className to ToolbarTitle to ensure consistency and migrated from menu to menus. Please review.
One last thing to note. seems like the new menus cannot be corretly positioned in a Toolbar the IconButton is not in the right place. But that doesn't have anything to do with this PR. merge if it's alright with you.

@oliviertassinari Please check again. Is this better?

You must have seen that react/jsx-boolean-value: [2, always] is enforced.
That probably opinionated, I feel like it's better to be explicit.
I have tested the branch, it's fine for me :+1:.
Remarque regarding the documentation.

We could add a max height to the doc example block and a button to expand it,
Increasing the marginTop of the MardownElement will probably improve readability.

@oliviertassinari Thanks for the review. I will fix them asap.

@oliviertassinari Please review again. I think coding styles must be kept consistent, I did some aggressive changes :smiling_imp:

That's pretty agressive indeed.
I think that we should keep the function that return the style.
That's good for separation of concern, readability and will probably help for react-native style abstraction.

@oliviertassinari Please check again

@subjectix Thanks

Thanks :tada: :tada:


NIFI-6400 Better options, consistent ids for ShellUserGroupProvider.

Description of PR
The code in this change-set provides the following:

consistent user and group identifiers from named UUIDs
two additional regular expression properties for excluding groups and users
new and updated integration tests for the above

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@natural Thanks for the update! We should be able to leverage the methods in User.Builder and Group.Builder to remove the private method for getNameBasedUUID. There is admittedly one scenario where the Group that is being created is only needed temporarily but I think this would use the APIs for as the were expected. I've typed up an example here [1]. Happy to discuss it and work through it more.
[1] https://github.com/mcgilman/nifi/commit/c423a016cc00816436191962a4eda9445f7abe17

Thanks @natural! This has been merged to master.


Fix typos in optwin.vim

@brammool Sorry if you have already included this.
I have already reported this at https://github.com/vim/vim/commit/cb80aa2d53e56d3aba3b3c439fb467f29a750c5e#r43601749, but I create this PR not to forget the changes.

I'll include it, thanks.


Creating a footer for all the pages

Every webpage will be using the same footer
footers usually have:

copyright
logo
terms
social media
contact form
etc.

I added a footer tho the bottom of each page. But i'm gonna keep this issue open so that it can be added to future pages


Update options

Fixes #18
Change option names:

license is now ccLicense
licensePrompt is now ccLicensePrompt
work is now ccWork

Fix incorrect main in package.json.

Coverage remained the same at 100.0% when pulling 0af23cfec7eb78dbc636bc2804330a18e6d28d2b on update-options into d5cf6b5f462db9d577ec261c826d998d1e04e6f1 on master.

Coverage remained the same at 100.0% when pulling 0af23cfec7eb78dbc636bc2804330a18e6d28d2b on update-options into d5cf6b5f462db9d577ec261c826d998d1e04e6f1 on master.

Coverage remained the same at 100.0% when pulling 0af23cfec7eb78dbc636bc2804330a18e6d28d2b on update-options into d5cf6b5f462db9d577ec261c826d998d1e04e6f1 on master.


Disk label is yellow by default

Description
By default, the label for info disk is yellow:
print_info() {
    ...
    info memory
    info disk
    ...
}

Neofetch version
3.0 on OSX 10.12.3
Screenshot

Verbose log
https://gist.github.com/anonymous/c2ef68eafb09e48c8aa3719844e7faa9

Can you send me your config file? I can't reproduce this at all.

I'm curious, is this the expected output (since you deleted the subtitle)?
2294MB / 16384MB
58G / 279G

I've fixed the issue. #641
I won't merge this until @konimex's question is answered so we can figure out the expected output. The PR currently prints it like the comment above.

I agree with @konimex. Totally missed the label added.

Will merge the fix now :+1:

@dylanaraps Not too sure what you would do in the case of multiple disks though...

We can append the disk name to the end of the string:
58G / 279G (21%) [/]
58G / 279G (21%) [/mnt/Local Disk]

Actually, I'd prefer it at the beginning hierarchy-wise. Thoughts?

Like this?
Also which brackets (if any)?
[/] 58G / 279G (21%)
[/mnt/Local Disk] 58G / 279G (21%)

(/) 58G / 279G (21%)
(/mnt/Local Disk) 58G / 279G (21%)

Yes. As far as formatting goes I would remove the brackets. Just like how the OS Xdiskutil list command does:
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:          Apple_CoreStorage Macintosh HD            300.3 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                199.0 GB   disk0s4

/dev/disk1 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Macintosh HD           +300.0 GB   disk1

Just to confirm, you'd prefer this?:
/: 58G / 279G (21%)
/mnt/Local Disk: 58G / 279G (21%)

Also what color would you expect the output to be?
This is what it currently looks like:

Yes, but that's just my opinion. It's think it's arbitrary and can be changed later if needed/wanted.
I would expect the color to be the color of the title if it's considered as part of the title:
Disk /: 58G / 279G (21%)
Disk /mnt/Local Disk: 58G / 279G (21%)

Otherwise I'd expect it to be the same color of the value:
Disk:
    /: 58G / 279G (21%)
    /mnt/Local Disk: 58G / 279G (21%)

Done!
Thanks for your input. :)


How can I make a deploy from a php script

Im traing use PHPSeclib and SSH2 for run dep deploy command
But i get error permission denied. If I run the command from putty, then everything is fine.
This is a output from php script:
➤ Executing task deploy:unlock\n
\n
In Client.php line 103:\n
                                                               \n
  The command "rm -f /var/www/front/.dep/deploy.lock" failed.  \n
                                                               \n
  Exit Code: -1 (Unknown error)                                \n
                                                               \n
  Host Name: domain.net                                      \n
                                                               \n
  ================                                             \n
  Permission denied, please try again.                         \n
  Permission denied, please try again.                         \n
<EMAIL_ADDRESS>Permission denied (publickey,password).`

Closing this issue as inactive. If you still have this problem, please open a new issue.


How can one specify the API version?

Nothing in the documentation regarding this. I'd like to use the API version before the latest release.

Never mind, forked it and figured it out...


403 Forbidden

When I use the demo to access "https://query1.finance.yahoo.com/v8/finance/chart/eth-usd?&period1=0&period2=9999999999&interval=1d" on my home WIFI it works fine. When I try the exact same thing on LTE it returns a 403 forbidden error.
Any help?

Have you seen the pinned issue, #301 ?

Thanks for the response this seems to be the issue :(
Do you know any easy way to migrate from cors-anywhere to be able to simply extract the data from the above URL?

301 lists several options including easy alternatives. Self-hosting is the most reliable solution.


Add an autest testcase for HTTP3

This extends autest a little and adds a test case for active timeout on HTTP/3.
This works on my env (curl built with ngtcp2 and nghttp3) but still WIP.

Running this autest on CI box would be tricky. We'd need special curl built with a QUIC library and the QUIC version the library supports has to match with the one ATS supports. Currently, 9.0.x and master supports 27 and quic-latest supports 29.

Updated the test condition to check if ATS is built with QUIC enabled, in addition to the check for HTTP/3 support of curl. The check for QUIC depends on #7074.

[approve ci docs]

@zwoop Do you have any concern on this? Running this on CI may be tricky, but I think this addition itself should not harm anything.


xiphos: code refactor

Now with my (current) personal tastes.

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Great to see that this is still maintained! However, I must inform you that this package is marked for removal because it depends on both Python 2 and Gtk2, which are end of life. Unless you see a way around it, this will be removed as part of my libglade removal.


Not raise ProxyError when I use proxy https://...:8080

Code:
proxies = {'https': u'https://...:8080'} # or {'HTTP':'http://:80' }
r = requests.head(u'http://example.com', proxies=proxies, timeout=10)
r.status_code
>>> 200

The proxy is broken, seems requests do not use this proxy and make request directly,
it should raise ProxyError('Cannot connect to proxy.' here.

That proxy is not broken. We are using the configuration you set. If you set the scheme {'https': u'https://...:8080'}, and make a request to a URL beginning with http://, you have not set any proxy for us to use: as a result, we don't use it.
The mere presence of a proxy dictionary does not indicate that the user wants every request they issue to be proxied.


how to set image height and width ?

I pass the height and width for generation, but the result is quite bizarre.
import torch
from diffusers import StableDiffusionPipeline, StableDiffusionImg2ImgPipeline, StableDiffusionInpaintPipelineLegacy, DDIMScheduler, AutoencoderKL
from PIL import Image
base_model_path = "SG161222/Realistic_Vision_V4.0_noVAE"
vae_model_path = "stabilityai/sd-vae-ft-mse"
image_encoder_path = "IP-Adapter/models/image_encoder"
ip_ckpt = "IP-Adapter/models/ip-adapter-plus_sd15.bin"
device = "cuda"
noise_scheduler = DDIMScheduler(
    num_train_timesteps=1000,
    beta_start=0.00085,
    beta_end=0.012,
    beta_schedule="scaled_linear",
    clip_sample=False,
    set_alpha_to_one=False,
    steps_offset=1,
)
vae = AutoencoderKL.from_pretrained(vae_model_path).to(dtype=torch.float16)
pipe = StableDiffusionPipeline.from_pretrained(
    base_model_path,
    torch_dtype=torch.float16,
    scheduler=noise_scheduler,
    vae=vae,
    feature_extractor=None,
    safety_checker=None
)
from ip_adapter import IPAdapterPlus
image = Image.open("boy.png")
image.resize((512, 512)) # is this necessary
print(image.size)

ip_model = IPAdapterPlus(pipe, image_encoder_path, ip_ckpt, device, num_tokens=16)
only image prompt
images = ip_model.generate(pil_image=image, num_samples=1, num_inference_steps=10, seed=42,
                           height = 1024, width = 1024)
images[0]

The input image

The generated image

It seems that the input image is duplicated.
My questions are :

is it necessary to resize the input image ?
what's the optimal height and width for generation ? It seems that 512 * 512 is the only one stable.

try with object image of (1600, 1600)

generation height set to 512, and width 1024

@PansaLegrand since the ip-adapter is trained with 512x512, generation with 512x512 is stable. If you want to generate higher resolution images, you can firstly generate 512x512 images and then use Hires. fix (image to image).

@PansaLegrand since the ip-adapter is trained with 512x512, generation with 512x512 is stable. If you want to generate higher resolution images, you can firstly generate 512x512 images and then use Hires. fix (image to image).

Thank you for the reply. I will stick to 512 * 512 then.


Binary search

Added recursive & iterative implementation of binary search.

Awesome, man!
Thank you for being its first contributor :)

@parkjs814 no problem mate, great work with the whole project 👊😀

Thanks, @nem035! Tell me whenever you want to be a collaborator.


Add a wiki: Fate/Grand Order Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://fategrandorder.fandom.com
Link to destination (independent) wiki: https://grandorder.wiki

Need to take a closer look; Fandom has 10,825 articles vs indie's 6,691. Indie is also very outdated on MediaWiki 1.27.


Update adding-typescript.md

Command line typo fix.

This is not a typo. yarn create is a valid command.


Add Enrichment Method Facet

┆Issue Number: HCAB-183

Not in current Mini Schema/Accessor Library

Obsolete


Maybe not setting right resolution?

I have been using MonitorSwapAutomation successfully for a while.  Now no longer have access to my physical monitor Problem with ResolutionAutomation maybe?  The logs for monitorswap claim it set the monitor back to the physical monitor.  The problem though ResolutionAutomation shows this and I'm not currently connected:
Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
--     ----            -------------   -----         -----------     --------             -------
1      ResolutionMa... BackgroundJob   Running       True            localhost            ...
3      ResolutionMa... BackgroundJob   Running       True            localhost            ...
Waiting for the next event to be called... (for starting/ending stream)
Processing event: Start
Setting screen resolution to 1920 x 1080 x 60
Resolution changed successfully.
Request to terminate has been processed, script will now revert resolution.
Setting screen resolution to 3840 x 2160 x 60
Resolution changed successfully.
**********************
Windows PowerShell transcript end
End time:<PHONE_NUMBER>4152

Problem I'm having is the monitor attached to the computer is a older 17" LCD 1U rack mount KVM monitor.  Looks like the last resolution change was to 4k which would be the dummy dongle.  Is it possible ResolutionAutomation is setting the wrong resolution and that's why the monitor isn't displaying?   Not even sure if ResolutionAutomation touches the primary display resolution.
MonitorSwap claims it set the monitor back to active but no clue how to tell:
Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
--     ----            -------------   -----         -----------     --------             -------
1      MonitorSwapp... BackgroundJob   Running       True            localhost            ...
3      MonitorSwapp... BackgroundJob   Running       True            localhost            ...
Waiting for the next event to be called... (for starting/ending stream)
Processing event: Start
Dummy plug activated
Request to terminate has been processed, script will now revert monitor configuration.
Attempting to set primary screen, some displays may not activate until you return to the computer
Monitor(s) have been successfully restored.
Dummy Plug has been successfully deactivated!
**********************
Windows PowerShell transcript end
End time:<PHONE_NUMBER>4154

Yes, the resolution swap changes the primary monitors resolution. You need to make sure the monitor swap happens first, if it changes it too quickly you can adjust the sleep timers in the script to wait a little longer before it does it.
As for when it reverts, it does it backward. So it will first revert the resolution, then swap back to main monitor (provided you have the swap happening before the resolution change like mentioned earlier)


transport Content-Length header issue

I called a grpc service which is not written by micro framework。the Content-Length header will be transformed by micro grpc client。and then my grpc server will use this header to handle request。but the Content-Length  is not the actual one。 so my server throw the below exception。
Less data received than specified in the Content-Length header

Whether it is should be transport this header or not? same issue with Connection header.
My grpc service is written by .net core.

Old stale issue. Is unclear to us whether this is still an issue.


Implement End-to-End Smoke Testing Suite

User Story:
As a tester, I want to implement an end-to-end smoke testing suite, so that I can quickly verify the basic functionality of the web application.
A/C:

Given there is no test suite configured; When the test suite is set up; Then the testing environment should be as similar as possible to the production environment.
Given the test suite is configured; When the tester develops the tests; Then the test suite must at least visit the most important web pages and find a source of truth.
Given the web application is in a development enviornment; When the tester executes the test suite; Then all tests should pass indicating basic functionality is working.
Given the tests have been executes; When the tests are complete; Then the results must be saved in a report so failures can be properly addressed.

Moved from iteration 5 -> 6 and downgraded to Priority P2. It may not make it in the first release.

Moved from iteration 6 -> 7. May continue to be kicked down the line...


Wiki mirror upstream address keep old when change mirror repository address

Gitea version (or commit ref):1.9.4
Git version:2.22.0
Operating system: Docker
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[Y] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
when change mirror repository's upstream address, its wiki mirror upstream address does not synchronized with changes and kept old one.

I think this has been resolved, I cannot reproduce it in v1.20


Update SQL .NET SDK tests to get location from environment variable

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

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

Testing Guidelines

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

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@dnayantara

There are some ".json.swp" files added, not sure what they are but please delete

@azuresdkci test this please

@mihymel FYI, added a simple retry to SqlTestUtilities that I'm calling from the failing TDE test


Angular Elements support

Angular Elements is in the process of being merged in the Angular master branch.
Will angular-cli provide some kind of support to this feature?

I've seen ng add @angular/elements somewhere which also should add needed polyfills. It seams that there already is some kind of "support" for this feature.
From my point of view the post important thing that should be supported, is some kind of "registration" of elements in angular-cli.json so they will be build and exported on ng build.
I don't really know what kind of additional support is needed for angular elements.

By looking into the not very well documented eco system around angular cli I guess what is missing is a @angular-devkit/build-angular:webcomponent that allows specifying a main that points to a module that contains the webcomponents that should be exported. Additionaly there should be a alternative polyfill file that contains webcomponent polyfills. Something like this:
"build": {
          "builder": "@angular-devkit/build-angular:webcomponent",
          "options": {
            "outputPath": "dist/webcomponents",
            "main": "src/app/webcomponent.module.ts",
            "polyfills": "src/webcomponent.polyfills.ts",
          }
}

The webcomponent.module.ts would look like this
import { Injector, NgModule } from '@angular/core';
import { ButtonComponent } from './button.component';
import { createCustomElement } from '@angular/elements';

@NgModule({
  declarations: [ButtonComponent],
  exports: [ButtonComponent],
  entryComponents: [ButtonComponent]
})
export class ButtonModule {
  constructor(private injector: Injector) {
    const customButton = createCustomElement(ButtonComponent, { injector });
    customElements.define('custom-button', customButton);
  }
}

Hopefully @angular/core is not that big that it carries to much unneeded code into the bundle.
Is this the way to go? Is there anything on the roadmap to support this? I really would like to get small reusable webcomponent bundles from my project. It would be really awesome if there was any documentation on how to get this done.

Let's close this in favor of https://github.com/angular/angular-cli/issues/19164 since there is more discussion happening over there.
Thanks.


Kafka consumers started twice on Host.Run

Hello,
I'm noticing unexpected behavior when using SlimMessageBus.Host.Kafka with .NET Generic Host.
When I run this code
using Microsoft.Extensions.Hosting;
using SlimMessageBus.Host;
using SlimMessageBus.Host.Kafka;

namespace SlimMessageBusTest
{
    class Program
    {
        static void Main(string[] args)
        {
            Host.CreateDefaultBuilder(args)
                .ConfigureServices((_, services) =>
                {
                    services.AddSlimMessageBus(mbb =>
                    {
                        mbb.WithProviderKafka(cfg => cfg.BrokerList = "localhost:9092");
                    });
                })
                .Build()
                .Run();
        }
    }
}

I get this output on Console
info: SlimMessageBus.Host.Kafka.KafkaMessageBus[0]
      Creating producers
info: SlimMessageBus.Host.MessageBusBase[0]
      Starting consumers for Main bus...
info: SlimMessageBus.Host.MessageBusBase[0]
      Starting consumers for Main bus...
info: SlimMessageBus.Host.MessageBusBase[0]
      Creating consumers
info: SlimMessageBus.Host.MessageBusBase[0]
      Creating consumers
info: SlimMessageBus.Host.MessageBusBase[0]
      Started consumers for Main bus
info: SlimMessageBus.Host.MessageBusBase[0]
      Started consumers for Main bus
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production

It seems that the consumers are started twice.
I don't know if this is normal/managed behavior or if I should use a different configuration.
This is my csproj:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0</TargetFramework>
    <Nullable>enable</Nullable>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.Extensions.Hosting.WindowsServices" Version="6.0.2" />
    <PackageReference Include="SlimMessageBus.Host.Kafka" Version="2.2.2" />
  </ItemGroup>
</Project>

I also noticed that when updating Microsoft.Extensions.Hosting.WindowsServices to version 8.0.0 this behavior does not occur and the consumers are started only once.

Thanks for raising. Sounds like this is a bug. Let me try to replicate and look into this.

hey @mib85 please check version 2.2.3 - it should be resolved. Please let me know if any issues. Thanks!

Hi @zarusz. I did some tests and everything seems fine. Thank you very much!


ci(release): Increase the timeout for creating the staging repository

Creating the Sonatype staging repository occasionally fails with a timeout, therefore increase it from the default 1 minute 1 to 5 minutes.

Merging this despite the unrelated funTtest-docker failure.


[New Issue]: google home page ui

Description
Description of the project here - i'll be adding google homepage UI
Code of Conduct

[X] I follow Contributing Guidelines of this project.

@RAHULBAWA777 google clone is already here, so make something unique, before making Issue Plz check it, If it has existed on the repo or not at this time I'm closing this issue


My new branch

Summary
Provide an overview...
Details
Add more context to describe the changes..
References
Example
Checks

[ ] Tested Changes
[ ] Stakeholder Approval

Looks good

Looks good


Cloning  a service that has health check enabled and creating it  fails with "Validation failed: secondaryLaunchConfigs" error.

Build from master - jun/10
Steps to reproduce the problem:
Create a service with scale 3 with health check enabled ( by providing port).
Activate service.
Clone this service , change the name of the service and clck on "create".
I get this error message - "Validation failed: secondaryLaunchConfigs" error.
I noticed that port field on the " health check" panel is missing.

Healthcheck is irrelevant.. secondaryLaunchConfigs is just null in the existing service so that is cloned, but the field isn't allowed to be null in the schema so the API rejects it on create.

Build from master - June 11th (morning)
Verified fixed - Can clone Service and Container with Health Check info in it.  Entered separate bug for Port field missing in cloned container.


Expose flakeModule from flake for use with flake-parts

Is there any interest in providing a flake-parts module? @roberth had a WIP solution here: https://github.com/numtide/devshell/compare/master...hercules-ci:devshell:flake-modules
I'm happy to resume/update this if there is any interest.
Matrix discussion
My intention is to use devshell's MOTD feature but without having to create devshell.toml and the like (ie., configure everything in flake.nix, and use with an existing language dev shell). To begin with, I'd use this to replace all the scripts in https://github.com/srid/haskell-template/tree/master/bin

I like it. Especially if it can get the same treatment as with treefmt-nix.

This would be really nice, now writing abstractions on top of shells using config from flake-parts is a bit tricky.

This would be really nice, now writing abstractions on top of shells using config from flake-parts is a bit tricky.

In the meantime here's a simple way that been bringing in devshell, might be useful:
{
  inputs,
  lib,
  ...
}: let
  importDevshellModule = name: {
    perSystem = import (inputs.devshell + "/modules/${name}");
  };
in {
  imports = [
    (importDevshellModule "env.nix") # allows us to define env variables
    (importDevshellModule "commands.nix") # allows us to define shell commands
    (importDevshellModule "devshell.nix") # the glue that binds
  ];

  config.perSystem = {
    pkgs,
    config,
    ...
  }: let
    # capture the devshell config generated for us by the devshell modules
    cfg = config.devshell;
  in {
    config = {
      # we need to create the data dir as this is typically done with devshells mkShell which we aren't using
      devshell.startup.create-datadir.text = ''
        mkdir -p $PRJ_DATA_DIR
      '';

      # define some useful env variables
      env = [
 		...
      ];

      # add some common commands
      commands = [
        ...
      ];

      # set our devshell
      devShells.default = cfg.shell;
    };
  };
}

In the next week or so I'm going to port this to a proper flake module for devshell.

Thank you, won't this put the env.nix and commands.nix options in the top level namespace? I wanted a more isolated solution and had a look at the currently proposed devenv integration. Based on this and also having tested it could look like this:
{
  lib,
  flake-parts-lib,
  ...
}: let
  inherit (flake-parts-lib) mkPerSystemOption;
  inherit (lib) mkOption types;
in {
  options = {
    perSystem = mkPerSystemOption ({
      config,
      pkgs,
      ...
    }: let
      devshellType =
        (lib.evalModules {
          modules = import ./modules/modules.nix {
            inherit lib pkgs;
          };
        })
        .type;
    in {
      options.devshell.shells = mkOption {
        type = types.lazyAttrsOf devshellType;
        default = {};
      };
      config.devShells = lib.mapAttrs (_name: devshell: devshell.devshell.shell) config.devshell.shells;
    });
  };
}

Yeah I didn't really mind about polluting the globacl namespace, just getting something working. I like the proposal above


Cilium thinks some endpoints for ClusterIP service is (terminating) when they are not

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
On some nodes, cilium shows endpoints of certain service as (terminating) when they are not. The service is accessible from such nodes.
Here is an example
spec:
    backendaddresses:
        - ip: <IP_ADDRESS>
          nodename: gw3.alpha
          port: 8446
          preferred: false
          state: terminating
          weight: 100
        - ip: <IP_ADDRESS>
          nodename: gw1.alpha
          port: 8446
          preferred: false
          state: terminating
          weight: 100
        - ip: <IP_ADDRESS>
          nodename: gw2.alpha
          port: 8446
          preferred: false
          state: terminating
          weight: 100
    flags:
        cluster: ""
        exttrafficpolicy: Cluster
        healthchecknodeport: 0
        inttrafficpolicy: Cluster
        name: ingress-nginx-external-controller-admission
        namespace: ingress-nginx
        natpolicy: ""
        trafficpolicy: Cluster
        type: ClusterIP
    frontendaddress:
        ip: <IP_ADDRESS>
        port: 443
        protocol: ""
        scope: external
    id: 21
    updateservices: false
status:
    realized:
        backendaddresses:
            - ip: <IP_ADDRESS>
              nodename: gw3.alpha
              port: 8446
              preferred: false
              state: terminating
              weight: 100
            - ip: <IP_ADDRESS>
              nodename: gw1.alpha
              port: 8446
              preferred: false
              state: terminating
              weight: 100
            - ip: <IP_ADDRESS>
              nodename: gw2.alpha
              port: 8446
              preferred: false
              state: terminating
              weight: 100
        flags:
            cluster: ""
            exttrafficpolicy: Cluster
            healthchecknodeport: 0
            inttrafficpolicy: Cluster
            name: ingress-nginx-external-controller-admission
            namespace: ingress-nginx
            natpolicy: ""
            trafficpolicy: Cluster
            type: ClusterIP
        frontendaddress:
            ip: <IP_ADDRESS>
            port: 443
            protocol: ""
            scope: external
        id: 21
        updateservices: false

Cilium Version
Client: 1.14.2 a6748946 2023-09-09T20:59:33+00:00 go version go1.20.8 linux/amd64
Daemon: 1.14.2 a6748946 2023-09-09T20:59:33+00:00 go version go1.20.8 linux/amd64
Kernel Version
6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"28", GitVersion:"v1.28.2", GitCommit:"89a4ea3e1e4ddd7f7572286090359983e0387b2f", GitTreeState:"clean", BuildDate:"2023-09-13T09:29:07Z", GoVersion:"go1.20.8", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
Even limited to 6h, it has 140MB - is there something in particular you would like to see?
Relevant log output
No response
Anything else?
Here is the Service:
apiVersion: v1
kind: Service
metadata:
  annotations:
    meta.helm.sh/release-name: ingress-nginx-external
    meta.helm.sh/release-namespace: ingress-nginx
  creationTimestamp: "2023-09-20T21:18:53Z"
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx-external
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.9.0
    helm.sh/chart: ingress-nginx-4.8.0
    helm.toolkit.fluxcd.io/name: ingress-nginx-external
    helm.toolkit.fluxcd.io/namespace: ingress-nginx
  name: ingress-nginx-external-controller-admission
  namespace: ingress-nginx
  resourceVersion: "6117688"
  uid: cbe1b303-fd34-41b8-a88f-2e995a5107a8
spec:
  clusterIP: <IP_ADDRESS>
  clusterIPs:
  - <IP_ADDRESS>
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - appProtocol: https
    name: https-webhook
    port: 443
    protocol: TCP
    targetPort: webhook
  selector:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx-external
    app.kubernetes.io/name: ingress-nginx
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Endpoint:
apiVersion: v1
kind: Endpoints
metadata:
  annotations:
    endpoints.kubernetes.io/last-change-trigger-time: "2023-10-09T23:17:15Z"
  creationTimestamp: "2023-09-20T21:18:53Z"
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx-external
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.9.0
    helm.sh/chart: ingress-nginx-4.8.0
    helm.toolkit.fluxcd.io/name: ingress-nginx-external
    helm.toolkit.fluxcd.io/namespace: ingress-nginx
  name: ingress-nginx-external-controller-admission
  namespace: ingress-nginx
  resourceVersion: "13527851"
  uid: b7a4e2f2-463e-4ef8-a4f6-ac07f8556bfc
subsets:
- addresses:
  - ip: <IP_ADDRESS>
    nodeName: gw1.alpha
    targetRef:
      kind: Pod
      name: ingress-nginx-external-controller-2gbk2
      namespace: ingress-nginx
      uid: 24c61871-7245-4613-99be-b94f2fbc0d94
  - ip: <IP_ADDRESS>
    nodeName: gw2.alpha
    targetRef:
      kind: Pod
      name: ingress-nginx-external-controller-b2kz8
      namespace: ingress-nginx
      uid: ad974373-1ac6-430e-91f8-ef09ea588b48
  - ip: <IP_ADDRESS>
    nodeName: gw3.alpha
    targetRef:
      kind: Pod
      name: ingress-nginx-external-controller-zvspk
      namespace: ingress-nginx
      uid: 404d2023-ca5e-43a8-8d85-757dd5dd3d16
  ports:
  - appProtocol: https
    name: https-webhook
    port: 8446
    protocol: TCP

and EndpointSlice:
addressType: IPv4
apiVersion: discovery.k8s.io/v1
endpoints:
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: true
    serving: true
    terminating: false
  nodeName: gw2.alpha
  targetRef:
    kind: Pod
    name: ingress-nginx-external-controller-b2kz8
    namespace: ingress-nginx
    uid: ad974373-1ac6-430e-91f8-ef09ea588b48
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: true
    serving: true
    terminating: false
  nodeName: gw3.alpha
  targetRef:
    kind: Pod
    name: ingress-nginx-external-controller-zvspk
    namespace: ingress-nginx
    uid: 404d2023-ca5e-43a8-8d85-757dd5dd3d16
- addresses:
  - <IP_ADDRESS>
  conditions:
    ready: true
    serving: true
    terminating: false
  nodeName: gw1.alpha
  targetRef:
    kind: Pod
    name: ingress-nginx-external-controller-2gbk2
    namespace: ingress-nginx
    uid: 24c61871-7245-4613-99be-b94f2fbc0d94
kind: EndpointSlice
metadata:
  annotations:
    endpoints.kubernetes.io/last-change-trigger-time: "2023-10-09T23:17:15Z"
  creationTimestamp: "2023-09-20T21:18:53Z"
  generateName: ingress-nginx-external-controller-admission-
  generation: 141
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx-external
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.9.0
    endpointslice.kubernetes.io/managed-by: endpointslice-controller.k8s.io
    helm.sh/chart: ingress-nginx-4.8.0
    helm.toolkit.fluxcd.io/name: ingress-nginx-external
    helm.toolkit.fluxcd.io/namespace: ingress-nginx
    kubernetes.io/service-name: ingress-nginx-external-controller-admission
  name: ingress-nginx-external-controller-admission-hvz2b
  namespace: ingress-nginx
  ownerReferences:
  - apiVersion: v1
    blockOwnerDeletion: true
    controller: true
    kind: Service
    name: ingress-nginx-external-controller-admission
    uid: cbe1b303-fd34-41b8-a88f-2e995a5107a8
  resourceVersion: "13527852"
  uid: cf3b852a-a2dd-429c-a789-577be8308be8
ports:
- appProtocol: https
  name: https-webhook
  port: 8446
  protocol: TCP

Also, on the nodes, that has the service in (terminating), the logs are flooded with:
level=error msg=k8sError error="github.com/cilium/cilium/pkg/k8s/resource/resource.go:304: Failed to watch *v1.EndpointSlice: unable to sync list result: cache.DeletedFinalStateUnknown not a known endpoint or endpoint slice object" subsys=k8s

messages
Code of Conduct

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

oops! We must be processing the EndpointSlices incorrectly. At least, I hope that's what it is :grimacing:

@pavels how often does this occur? Can you easily reproduce it? Would it be possible to get a sysdump / bugtool of a node exhibiting this issue?

I will try to replicate this in lab environment - this is happening now on production system and even if i isolate sysdump to single node, it contains a lot of stuff i can't post publicly.

It now happens for this single service only - also the problem persists if i restart the cilium-agent pod on a node - just the log messages disappear

I can't reproduce it anymore - looks like it disappeared after upgrade to 1.14.3
May be related to https://github.com/cilium/cilium/pull/27340


Support disconnected network environments

This PR adds support for installing the operator in disconnected network environments. To build with image-digests set USE_IMAGE_DIGESTS=true before running make bundle.
For Prow jobs we are enabling this via .prow-ci.env
This drops the old logic from create_bundle.sh which has been broken with operator-sdk's make bundle for some time.
Also, bumps to operator-sdk-1.31 since this operator has artifacts from registry.redhat.io that require auth to work to obtain the sha's
(NOTE: this currently requires a secure registry)
Jira: OSP-26486

/retest

/recheck

recheck

recheck

recheck

recheck

recheck


TCVP-2005 Added methods to retrieve PartId from idirUsername

Description
This PR includes the following proposed change(s):
TCVP-2005
Created 2 helper methods to aid in retrieving the part_id attribute from a user in KeyCloak with the given idir_username attribute.
ICollection<UserRepresentation> UsersByIdir(string idirUsername)
ICollection<string> TryGetPartIds(UserRepresentation userRepresentation)

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[ ] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

Isn't the part id available in the user's token? Is there a requirement to access other people's part id? ie for assigning files to others?

No, unfortunately, part_id not part of the token (jwt).
I don't know if it's a requirement or not to get part_id for a different user's idir account.

Isn't the part id available in the user's token? Is there a requirement to access other people's part id? ie for assigning files to others?

Staff will be hitting button in the staff portal to update court appearance information in JUSTIN including the judicial justice who adjudicated the hearing.  TCO will record the judicial justice IDIR in the TCO COURT APPEARANCE table but JUSTIN needs the part id for the judicial justice and the staff member, though only the staff member is logged into the staff portal.


HotFix: Formatter moves all comments in flattened namespace to the top

fix https://github.com/microsoft/typespec/issues/2060
Issue was that when parsing
namespace Foo.Bar {}

both node for the namespace Foo and Bar would have the exact same pos and end. This caused issue with prettier thinking the comment would belong to Foo instead of under Bar.
The change makes it that the the Foo namespace keeps the same pos end end but the Bar pos has been updated to start at the beginning of the Bar indentifier.
This is the same the typescript compiler does for namespace/modules(despite not being something you should use) https://github.com/microsoft/TypeScript/blob/d79ec186d6a4e39f57af6143761d453466a32e0c/src/compiler/parser.ts#L8086

I believe we may have done it this way before and there was an issue here when the namespace is decorated.
@foo
namespace Foo.Bar {
}
Now the decorator node is a child of the Foo.Bar node, but not within its pos<= x && x < end range. This will break getNodeAtPosition.
If I am remembering correctly, I believe there is a test that should be failing here.


Added ability to set board in Monte Carlo Game

The ability to set the board allows users to run Monte Carlo Game simulations on specific game scenarios after the flop. This allows this crate to be used in development of game solvers.

This should all be merged. I went ahead and changed the nits on rebase myself, but left your commit. Thank you!


[QUESTION] Using avy-* instead of evil-avy-*

Is there a reason for using avy-goto-char-timer instead of evil-avy-goto-char-timer at https://github.com/hlissner/doom-emacs/blob/c54509f99c6dfeb5f0aee1c76c719c2086cf4457/modules/config/default/%2Bevil-bindings.el#L165?
The evil variant seems to work better with evil-jump.

No reason. I think evil-avy-goto-char-timer didn't exist when the keybind was first introduced. I've changed it to use it in 18cefa0. Thanks for bringing it to my attention!


e2e jobs for prod-preview rescheduled

@jmelis @kbsingh @riuvshin could you please review it? it only reschedules two jobs


Documentation request: add version buttons of Helm Chart versions

I would like to request similar style helm chart version numbers that Kyverno repo project does on this repo so that version numbers are viewable at a glance as illustrated in this image:

hey, thanks for your request. I will have a look on it.

I added the badges but the Helm Chart is already prepared for the next release, so they currently not reflect the latest currently release.

Available with the latest release infos (v<IP_ADDRESS>)


feat: add mechanism for detecting top-level TMs

Codecov Report

Merging #48 (314cf02) into main (38228c1) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #48   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines          965       978   +13
  Branches       173       178    +5
=========================================
+ Hits           965       978   +13

Impacted Files
Coverage Δ

sdf_wot_converter/converters/wot_to_sdf.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


merge psrewrite into master

Merge of branch psrewrite with updated styling and compatibility.
The rewrite updates the styling to an Object oriented approach which is beneficial to future expansion of the logic surrounding errors and restarting the script.

A new branch will be created when the RTC functionality is added.


Productslider empty!

Description: With Dynamic Productgroup the Productslider is empty/white
Environment: sw6.6.2 new clean install
Steps to reproduce: every time, with different Browser
Expected result: should show products like in the Categoriepage
Actual result: no clue

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-36102
[created from NEXT-36102, comment 501920]


cant open doors

lock our unlock I cant open the doors
any of them

Check your mod. Something cause conflict

lock our unlock I cant open the doors
any of them

Hi @Tirus89,
I have the same door issue, as well as the pilot and copilot not disappearing when viewed from their positions or when I change the weights to below 100 lbs.
To resolve this I changed the mods folder name to "zz-aircraft-tbm930-improvement" so it loads into MSFS 2020 as the last mod.
Of course, this may make other mods in the community folder stop working correctly too.
So, @mixMugz is right ti identify that the issue is a conflict with another mod.

Conflict with another mod


APEXCORE-790 Enforce dependency analysis for CVE in CI builds

Jenkins retest this please

Jenkins retest this please

We need to resolve before we can proceed
<EMAIL_ADDRESS>

It is not clear what needs to be resolved there.

If this check can be avoided for PRs and done only for release builds and on demand.

It needs to run in the CI, otherwise it has no purpose. I would suggest we give this a try and if there are real problems then we revisit.

@PramodSSImmaneni That was discussed on dev@apex and private@apex and it is not a general preference. The entire goal of the PR is

preventing a new dependency with a severe CVE being introduced
notifying the community of a new severe CVE in existing dependencies

Like I mentioned many times in dev@apex, I have a strong reservation for failing PRs because of unrelated CVEs. If the situation is different and it doesn't do that please let me know. There is already enough resistance on the PRs and I don't want to try this and make it worse. A significant number of PRs weren't pursued by contributors after back and forth with committers and were closed due to inactivity.
There are many projects that run periodic builds (like nightlies) and those builds would be the right place to activate these checks. I have no issue if this can be tailored to fail PRs that are introducing dependency changes with CVEs.

@PramodSSImmaneni I would suggest to address the perceived problem if and when it actually occurs. I had proposed another solution as well: If a CVE is detected and it is not related to the PR, create a ticket and whitelist it until it gets fixed.

@tweise I already see a problem with PRs getting approved and merged. I don't want to add one more to the process and then create workarounds when it can be easily be achieved in alternate ways like a separate build. Why don't we look into that option? If it is not feasible then we can consider this approach.

No, check for new dependencies with CVE can't be achieved in alternate ways and there is no separate build for Apex.
I am more concerned with the quality of contribution for those PRs that were closed due to inactivity.

As the change can be easily reverted back (it does not affect the platform functionality) if it affects a large number of PRs, I'd prefer to move forward and merge it.

I'll merge it in a day.

Like I said, let's exercise restraint and do it in a way that doesn't require to add workarounds or to pull it back.

@PramodSSImmaneni As I mentioned, there is no a separate CI build and should it even exists, the goal of the PR is to prevent an introduction of new dependencies with CVE, so I don't see how to do it in a way you want. If you have a concrete proposal, please open a PR or post it to dev@apex. Without the concrete proposal, I plan to merge the PR in a day.

@vrozov I would be ok if we did the following.

Make this check the last thing in the PR build process, so we know whether the rest of the steps (unit tests etc) succeeded or not.
If it is a CVE that isn't related to the PR then a committer can merge it.
If it is due to a dependency added by the PR then the committer would ask the contributor to address it. If there are no good alternatives, then a discussion would need to happen in dev whether to allow it.
In both the cases above, we need to discuss what the remedy for the dependency is going forward, can someone look into it and make the necessary changes to upgrade the dependency, do we whitelist the dependency etc. We need to add these to the contribution guidelines.
We need the plugin to honor a whitelist. If I am not mistaken I didn't see this in the change.

Without these I am -1 on the PR.

@PramodSSImmaneni addressed items 1 and 5. 2 & 3 were already discussed and there is a general agreement on both items (some details may need to be flushed out). I can't address item 4 in the PR.

Jenkins retest this please

Check the build once.

Please clarify or merge the PR if it is good to go on your side.

Do you know why the jenkins build failed. It wasn't clear.

No, I don't know why it fails, except that it looks unrelated to this PR. I am OK to put this PR on hold until the Jenkins build failure RCA is done, but only in the case it becomes a generic policy.

Jenkins retest this please

Another trial failed with message after 20mins. Is there an overall timeout for the build.
Finished: ABORTED

Jenkins retest this please

Yes, there is 20 min timeout.

Jenkins retest this please

@PramodSSImmaneni I guess the plan is to move forward with the policy to put PR on hold till CI build failure RCA is done. I am +1 on such approach.

@vrozov I am fine with the RCA approach. In this case I too think the change is not related to the error and am partial to merging it. I did some checking and looks like a StramMiniCluster test which checks shutdown behavior is failing. I ran an alternative build on jenkins and I think this is an issue in master as well.  I am partial to merging it and will do it later today unless someone has objections. Do send the email to dev on that thread that further resolution happened in the JIRA.

@PramodSSImmaneni Please check PR #589. StramMiniClusterTest fails as all (the only one) nodes in the Yarn mini cluster are not usable (likely due to check for free disk space). It may be better to merge the other PR first.

@PramodSSImmaneni Please update JIRA


Bot not recognizing valid token

Promise {
  <rejected> Error [TokenInvalid]: An invalid token was provided.
      at Client.login (/home/runner/VerifyBot/node_modules/discord.js/src/client/Client.js:216:52)
      at file:///home/runner/VerifyBot/dist/index.js:85:8
      at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
      at async Promise.all (index 0)
      at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
      at async loadESM (node:internal/process/esm_loader:91:5)
      at async handleMainPromise (node:internal/modules/run_main:65:12) {
    code: 'TokenInvalid'
  }
}
✅ [Firebase] Successfully Connected to firebase!```

I've resetted the token 5 times and nothing...

This has to do with you and isn't an issue with the bot. Please verify that you attached the token inside of the .env file.

This has to do with you and isn't an issue with the bot. Please verify that you attached the token inside of the .env file.

Yes it was, And I even changed the client.login to be only the token and it didn't work.

The bot doesn't use client.login.
Please create a file called .env and use this format:
TOKEN=token

The bot doesn't use client.login.
Please create a file called .env and use this format:
TOKEN=token

Oh, ok, I wonder what I changed...
Question, do I need to run npm run build before every change?

The bot doesn't use client.login.
Please create a file called .env and use this format:
TOKEN=token

Oh, ok, I wonder what I changed...
Question, do I need to run npm run build before every change?

I believe so.
npm run build to build
then
npm run start to start bot or update to new build


String management Ruby 1.9.3 version

Hi,
I'm sending you the file bm_str_chars.rb with a benchmark that show the big difference between the ruby 1.9.3 to the other ones about the management of strings.

looks good to me


How to install dependencies on centos7, download rpm does not work

It not work on centos7 by running springboot project
·Linux localhost.localdomain 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux·

please help me ,thanks.

The names of these packages are different for RPM (the package names we list are for apt).
try:

libc6 -> glibc
libx11 -> libX11
libxext -> libXext
libxrender -> libXrender
libssl1.0 -> openssl


missing Exploration.from_config

As w/ all my newbie PRs, feel free to scrap mine & use your own if y'all have a correct solution. Defining exploration in the config gave "Exploration doesn't have from_config()" (ish).

Thanks! The from_config is not necessary, instead in other parts it should rightly be called via from_spec. Will fix that.


feat: relative last activity based eviction

Adds a new disk usage based eviction option, EvictionOrder, which selects whether to use the current AbsoluteAccessed or this new proposed but not yet tested RelativeAccessed. Additionally a fudge factor was noticed while implementing this, which might help sparing smaller tenants at the expense of targeting larger tenants.
Cc: #5304

I also confirm that the patch should be safe to run in staging/production. there is floating point ops now which are unconditional, and it would be a bit safer if relative_last_activity were an Option instead of using ZERO, but that is only a tiny bit of safety that we'd be gaining.


Does this bot work on Windows?

No, MSGPACK causes problems for the most people. We work on a version that will support Windows.

Update: now it should work on windows since we rermoved MSGPACK


server is slow af.

Any chance you can run on a faster server/ bigger instance? Let me know if I can help. I use this daily and would love to contribute.

Most URL types seem to be responding reasonably. Its the user scoped requests for random image that are taking too long.
If there are other URL patterns that you think are unusually slow, please add them to this issue. I'll poke around to see what's slowing them down.
$ httpstat http://lgtm.in/i/CfqdWAW9q -H "Accept: application/json"
Connected to <IP_ADDRESS>:80 from <IP_ADDRESS>:60615

HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: JSESSIONID=VSPsES1uqI9r1EpNaR7UHQ;Path=/
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET
Access-Control-Allow-Credentials: true
X-Cloud-Trace-Context: 3da145f85c2b054c288442e33a618683;o=1
Date: Fri, 18 Aug 2017 05:42:44 GMT
Server: Google Frontend
Content-Length: 690
Cache-Control: private

Body stored in: /var/folders/36/x8ynjcxx4533f_v44b6dxzmm0000gn/T/tmpVisjQ2

  DNS Lookup   TCP Connection   Server Processing   Content Transfer
[     8ms    |      47ms      |       198ms       |        1ms       ]
             |                |                   |                  |
    namelookup:8ms            |                   |                  |
                        connect:55ms              |                  |
                                      starttransfer:253ms            |
                                                                 total:254ms

$ httpstat http://lgtm.in/g -H "Accept: application/json"
Connected to <IP_ADDRESS>:80 from <IP_ADDRESS>:60617

HTTP/1.1 302 Found
Content-Type: text/html; charset=utf-8
Location: http://lgtm.in/i/cYtYqlh3q
X-Cloud-Trace-Context: 40512bce676ab1311a893c1a1f10c81e
Date: Fri, 18 Aug 2017 05:42:47 GMT
Server: Google Frontend
Content-Length: 0

Body stored in: /var/folders/36/x8ynjcxx4533f_v44b6dxzmm0000gn/T/tmpKXLfLR

  DNS Lookup   TCP Connection   Server Processing   Content Transfer
[     5ms    |      46ms      |       336ms       |        1ms       ]
             |                |                   |                  |
    namelookup:5ms            |                   |                  |
                        connect:51ms              |                  |
                                      starttransfer:387ms            |
                                                                 total:388ms

$ httpstat http://lgtm.in/g/rahulsom -H "Accept: application/json"
Connected to <IP_ADDRESS>:80 from <IP_ADDRESS>:60618

HTTP/1.1 302 Found
Content-Type: text/html; charset=utf-8
Location: http://lgtm.in/i/wYcwHPnws
X-Cloud-Trace-Context: bb65abe5e8d298ea7c05006507ad25fa
Date: Fri, 18 Aug 2017 05:42:58 GMT
Server: Google Frontend
Content-Length: 0

Body stored in: /var/folders/36/x8ynjcxx4533f_v44b6dxzmm0000gn/T/tmpJZMTK1

  DNS Lookup   TCP Connection   Server Processing   Content Transfer
[     4ms    |      45ms      |      7642ms       |        1ms       ]
             |                |                   |                  |
    namelookup:4ms            |                   |                  |
                        connect:49ms              |                  |
                                      starttransfer:7691ms           |
                                                                 total:7692ms

The user scoped random requests have been sped up by this commit - https://github.com/rahulsom/lgtmin/commit/5b9c6c786b89c30cedd1cff883771b25a15444d6
Please let me know if this has improved performance for you.
$ httpstat http://lgtm.in/g/rahulsom -H "Accept: application/json"
Connected to <IP_ADDRESS>:80 from <IP_ADDRESS>:62176

HTTP/1.1 302 Found
Content-Type: text/html; charset=utf-8
Location: http://lgtm.in/i/UqJiuVcfq
X-Cloud-Trace-Context: 16ad0c4edf0e8c7575ee025211a99592;o=1
Date: Fri, 18 Aug 2017 07:12:03 GMT
Server: Google Frontend
Content-Length: 0

Body stored in: /var/folders/36/x8ynjcxx4533f_v44b6dxzmm0000gn/T/tmpvqBCBJ

  DNS Lookup   TCP Connection   Server Processing   Content Transfer
[     4ms    |      47ms      |       313ms       |        0ms       ]
             |                |                   |                  |
    namelookup:4ms            |                   |                  |
                        connect:51ms              |                  |
                                      starttransfer:364ms            |
                                                                 total:364ms


Create waardex

Adding a new HB bidder description - WaardeX

I don't see existing code or a PR in Prebid.js for this bidder. While the doc looks ok, it won't be merged without code - please link this to the relevant code PR. Thanks.

Hi, thew bidder was added to the release 2.38.0, but this description was not added to the website, please add

Sorry - it sometimes takes a day or two for me to catch up with PBJS releases.


python3Packages.yark: fix build by relaxing some deps

Description of changes
Fixes: #288426

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build python3Packages.yark

Result of nixpkgs-review pr 288496 run on x86_64-linux 1

2 packages marked as broken and skipped:

python312Packages.yark
python312Packages.yark.dist

2 packages built:

python311Packages.yark
python311Packages.yark.dist


Add get hash step

Codecov Report

Merging #12 (11ae476) into main (df8d6ae) will decrease coverage by 0.13%.
The diff coverage is 33.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
- Coverage   55.28%   55.16%   -0.13%
==========================================
  Files          17       17
  Lines         454      455       +1
  Branches       73       73
==========================================
  Hits          251      251
- Misses        199      200       +1
  Partials        4        4

Impacted Files
Coverage Δ

transpire/types.py
47.57% <33.33%> (-0.47%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Shapeless regression in 2.12.x

at https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/317/consoleFull we see:
[shapeless] [info] Compiling 1 Scala source to /home/jenkins/workspace/scala-2.12.x-integrate-community-build/target-0.9.5/project-builds/shapeless-1679f8516c3340bf735655bf1552c1628bc52b69/core/jvm/target/scala-2.12.0-dbuildx0fb517827cb71cfe78f1d5b24cd78dccaabefe46/classes...
[shapeless] [info] Compiling 43 Scala sources to /home/jenkins/workspace/scala-2.12.x-integrate-community-build/target-0.9.5/project-builds/shapeless-1679f8516c3340bf735655bf1552c1628bc52b69/core/jvm/target/scala-2.12.0-dbuildx0fb517827cb71cfe78f1d5b24cd78dccaabefe46/test-classes...
[shapeless] [error] /home/jenkins/workspace/scala-2.12.x-integrate-community-build/target-0.9.5/project-builds/shapeless-1679f8516c3340bf735655bf1552c1628bc52b69/core/src/test/scala/shapeless/hmap.scala:134: ambiguous implicit values:
[shapeless] [error]  both method idKeyWitness in object ~?> of type [V[_], T](implicit rel: shapeless.~?>[shapeless.Id,V])rel.λ[T,V[T]]
[shapeless] [error]  and method witness in object ~?> of type [K[_], V[_], T](implicit rel: shapeless.~?>[K,V])rel.λ[K[T],V[T]]
[shapeless] [error]  match expected type shapeless.~?>[shapeless.Id,Option]#λ[Int,V]
[shapeless] [error]     val o2 = nt.get(23)
[shapeless] [error]                    ^
[shapeless] [error] one error found
[shapeless] [error] (coreJVM/test:compileIncremental) Compilation failed

fyi @milessabin. @scala/core anyone know of a recent 2.12 change that might be involved here?

Could you point me at a compiler artefact that I could test this with? It looks likely that tweaking the priorities of those instances will fix the problem here. I'm aiming for a 2.3.0 RC today so it would be super helpful to get this resolved ASAP.

@milessabin this is the latest revision in 2.12.x:
resolvers += "Scala PR Validation Snapshots" at "https://scala-ci.typesafe.com/artifactory/scala-pr-validation-snapshots/"

scalaVersion := "2.12.0-363bad3-SNAPSHOT"

This change in shapeless fixes the problem,
diff --git a/core/src/main/scala/shapeless/hmap.scala b/core/src/main/scala/shapeless/hmap.scala
index 7edb785..e1687d1 100644
--- a/core/src/main/scala/shapeless/hmap.scala
+++ b/core/src/main/scala/shapeless/hmap.scala
@@ -52,12 +52,13 @@ class ~?>[K[_], V[_]] extends Serializable {
   class λ[K, V] extends Serializable
 }

-object ~?> {
+object ~?> extends NatTRel0 {
   implicit def rel[K[_], V[_]] : K ~?> V = new (K ~?> V)
-
-  implicit def witness[K[_], V[_], T](implicit rel : K ~?> V) : rel.λ[K[T], V[T]] = new rel.λ[K[T], V[T]]

   implicit def idKeyWitness[V[_], T](implicit rel : Id ~?> V) : rel.λ[T, V[T]] = new rel.λ[Id[T], V[T]]
   implicit def idValueWitness[K[_], T](implicit rel : K ~?> Id) : rel.λ[K[T], T] = new rel.λ[K[T], Id[T]]
 }

+trait NatTRel0 {
+  implicit def witness[K[_], V[_], T](implicit rel : K ~?> V) : rel.λ[K[T], V[T]] = new rel.λ[K[T], V[T]]
+}

I see @retronym is doing a test run at https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/319/consoleFull

FYI I have also pushed the fix above: https://github.com/milessabin/shapeless/commit/22cb6def0692d7694672fc8fd576b8fab0248213.

Just happened in the area and Jenkins run https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/321/consoleFull proves that Miles' 22cb6de change fixes the failure.


geometry shader extension (gl_ext_geometry_shader4) not available

On a windows 10 x64-bit machine ... Don't know what to do

i will look into this very very soon, because it seems to concern many people!

please do it!

i'm quite sure i fixed it today, but i haven't tested on windows yet. binary will be out sat or sunday (not sure if i have time tomorrow)

Ok. I'm waiting for a response  Saturday, 10 December 2016, 04:23AM +00:00 from hansi raber<EMAIL_ADDRESS>:

i'm quite sure i fixed it today, but i haven't tested on windows yet. binary will be out sat or sunday (not sure if i have time tomorrow)
—
You are receiving this because you commented.
Reply to this email directly,  view it on GitHub , or  mute the thread .

can you try this and please let me know? https://asdfg.me/up/Oscilloscope-1.0.6-win32-pre.zip

doesn't open on my windows 10 x64-bit

can you describe a bit more in detail?
do you get any kind of error or other message?

I run the .exe file, then it loads a litte but doesn't show anything

is it still open if you look for oscilloscope.exe in the task manager?

in the task manager the oscilloscope.exe shows for some seconds then disappear

I will attach a screenshot of the error.

💃 it works on my machine (WIN 10 pro, Build 10586) thanks a lot  .. it's a little buggy though, anything that refreshes the display causes the sound to crackle .. and attempting to minimize the exe makes it stop working

Windows 7 32 bits. "geometry shader extension (gl_ext_geometry_shader4) not available".

@FelipeTesta yes, that's an old version. can you test this please: https://asdfg.me/up/Oscilloscope-1.0.6-win32-pre.zip

Nice! That's working.

@FelipeTesta great. can you please test:

minimizing the app
dragging a lot of different files into it (wav, mp3, mp4, avi, ... whatever you can find).

does it crash doing any of that?

Minimizing and fullscreen mode is working.
I don't have all this types of archive right now, but I'll soon. When I get these I'll try.

geometry shader seems fixed.


Removing encodeURIComponent from already added option check

Using an encodeURIComponent in the option selection will fail for any options that use encodable characters such as spaces. This results in duplicate option tags getting generated for any value containing spaces.

:+1: for merging this pull request! This bug bit me today, and I just submitted a detailed issue #294 before finding this waiting here.
@jviletto, you might consider modifying this to always encode option attribute values safely. This requires a few more modifications as described in #294, but would then support tags with quotes, angle brackets, etc. safely.

I'll have a look at this locally a little later on tonight guys and try and get it merged then or tomorrow.
Thanks for the work you guys put in!

@lucknerjb Can you please review this?


Auto-generated state results in a very large response header

After making a copy of a project because of domain related deployment restrictions, my new deployment is making oauth2 calls that appear to result in extremely large response headers on the Oauth2 server. If I manually update the state in authUri to something smaller, there appears to be no issue when tested in browser.
Although the behavior of an external Oauth2 server such as Keycloak is outside the scope of this project, if the length of the state variable could be modified within Oauth2 client, it'd be nice to avoid an otherwise unnecessary configuration to increase allowed header size on the oauth2 server.
Currently, the ScriptApp.newStateToken() appears to be a blackbox. The most documentation available appears to only explain usage, but not how it internally sets the state to be used later in usercallback. I was hoping a custom state (say, Utilities.getUUID()) could be accepted as a param to ScriptApp.newStateToken() to give more flexibility to users.
Does that sounds like it could make sense to let users customize state or otherwise configure the length?

Unfortunately there isn't anything I can do in this library to influence the size of the state tokens. As you mentioned, they are generated by ScriptApp.newStateToken() which is part of the Apps Script platform and is not code I can directly control. The OAuth2 spec doesn't specify a maximum size for the state parameter, and the current size works well for a wide array of OAuth2 providers, so I don't think the Apps Script team will see a large motivation to adjust their output.
The state tokens are only required when using the /usercallback endpoint, which were designed specifically for this purpose. However some developers have used the Apps Script web app endpoints instead to work around various issues. Those endpoint don't require a state token, but also don't provide the cross-site request forgery (CSRF) protections that the state tokens provide. You could implement that kind of protection on your own, but it's part of the reason why the state tokens are as long as they are.

Thanks for the quick response Eric, and the suggested alternate solution of using the web app end point.
It turns out that it wasn't the long state [alone] that caused the large header, as the issue only happened when the user was already logged in. Appears that Oauth2 server logs an invalid_token error on grant refresh_token, and sends a large response header which I thought was due to the extraordinarily long state [alone]. Temporarily, I've put prompt=login to avoid the refresh_token call altogether while I figure why.
Separately, I wish ScriptApp.newStateToken() wasn't a blackbox, but then again it isn't a part of this repo. Thanks for your help.


Converted the actionHelper and waitHelper helper classes to typescrip…

…t classes. #5

Completed and Merged.


Feature/google cast support

Barebones needed to add Cast support to the project and simple Http server that will serve the content.

Q: how big is the .apk getting after including the casting framework and the nano httpd server?

10 529 KB -> 11 647 KB
rougly 1MB (10%) increase


ltHelper & gtHelper keep misbehaving

After writing some tricky tests I realized that those functions keep failing with some corner cases. For example, gtHelper should return true when called with 0, 0, true, but it returns undefined instead.
Let me finish the specs, @obeliskos and then we'll discuss how to manage this.

Oh, sorry, that is actually a brainfart. I was testing $gt as if was $gte.


gen2-deeplabv3_depth missing a file, "background.jpeg"

Hi,
I just tried to launch the experiment gen2-deeplabv3_depth from the master branch and had the issue:
  File "main.py", line 88, in <module>
    colorBackground = cv2.resize(crop_to_square(cv2.imread('background.jpeg')), (400,400))
  File "main.py", line 82, in crop_to_square
    height = frame.shape[0]
AttributeError: 'NoneType' object has no attribute 'shape'

Guessing "background.jpeg" hasn't been comitted?
Adding a black 400x400px jpeg file (attached) seems to fix this.

Just a bit odd because one of the last commits was: https://github.com/luxonis/depthai-experiments/commit/fb6fde1ac9a46fc68843bcabd1ccd39340ebbe85 - "Updated & tested all experiments" would suggest to me a fault in the testing process assuming I haven't made a mistake.
Would it be possible to confirm the issue independently?

Sorry about that @John-Dean , I have just merged https://github.com/luxonis/depthai-experiments/pull/258 PR that fixes that issue.

That's working great, thanks @Erol444 !