Failed to run playbook

When I run playbook using
ansible-navigator run vmware_guest_info.yml

I am presented with

There is no error or warning.
artifact file contains -
{
    "version": "1.0.0",
    "plays": [],
    "stdout": [
        "\u001b[1;35m[WARNING]: No inventory was parsed, only implicit localhost is available\u
        "\u001b[1;35m[WARNING]: provided hosts list is empty, only localhost is available. Note
        "\u001b[1;35mthe implicit localhost does not match 'all'\u001b[0m",
        "\u001b[0;31mERROR! couldn't resolve module/action 'community.vmware.vmware_guest_info'
        "\u001b[0;31m\u001b[0m",
        "\u001b[0;31mThe error appears to be in '/home/vagrant/vmware/vmware_guest_info.yml': l
        "\u001b[0;31mbe elsewhere in the file depending on the exact syntax problem.\u001b[0m",
        "\u001b[0;31m\u001b[0m",
        "\u001b[0;31mThe offending line appears to be:\u001b[0m",
        "\u001b[0;31m\u001b[0m",
        "\u001b[0;31m  tasks:\u001b[0m",
        "\u001b[0;31m  - name: Get CentOS 7\u001b[0m",
        "\u001b[0;31m    ^ here\u001b[0m"
    ],
    "status": "failed",
    "status_color": 9
}

I agree that it is failing to find the module community.vmware.vmware_guest_info but TUI should show some meaningful error.

When you see the red FAILED indicator, try :stdout to see the error, LMK if it is there

I get
0 Error: unable to pull registry-proxy.engineering.redhat.com/rh-osbs/ansible-automation-platfo
r

If I manually pull image like
podman pull registry-proxy.engineering.redhat.com/rh-osbs/ansible-automation-platform-20-ee-supported-rhel8:latest --tls-verify=false

I get
Error: error pulling image "registry-proxy.engineering.redhat.com/rh-osbs/ansible-automation-platform-20-ee-supported-rhel8:latest": unable to pull registry-proxy.engineering.redhat.com/rh-osbs/ansible-automation-platform-20-ee-supported-rhel8:latest: unable to pull image: Error writing blob: error storing blob to file "/var/tmp/storage282544960/5": unexpected EOF

related to #175
We should also talk about a modal/pop-up that put the error in front of the user


Import CSV File into MariaDB - Tries to import the whole file at once

Description
With an older version of DBeaver, I was able to import a large (1 million row) CSV file successfully into MariaDB.
It would insert the rows into the database table as they loaded, not try to load them all at once.
Now it's trying to load the entire file at once and no rows are being inserted at all. Finally, there's a java heap exception because it runs out of memory.
No surprise since it's not properly flushing the data.
This seems like a bug - and it didn't exist as of one of the versions I had last year. (Just updated - not sure which version I had previously, but the new version has the error)
DBeaver Version
Community Edition <IP_ADDRESS>
Operating System
Windows 10
Database and driver

MariaDB (10.5.16-MariaDB)
MariaDB driver (mariadb-java-client-3.0.7.jar)

Steps to reproduce

I have a large CSV file (849 megabytes)
I try to insert this CSV file into MariaDB into an existing table with existing column mappings
No matter what settings I chose, it will run until it blows up, having inserted 0 records.

I know I can increase the memory size for the app, but wouldn't it be better to insert the records as it goes?
Additional context
No response

Hello @adexios
What settings do you have in the performance section? Are transactions enabled?

Please provide a screen of this page.
Also, did you try to use multi-insert?

Thanks for the fast reply!
I tried every combination of settings - transactions or no transactions.
Multi-insert, no multi insert. It refuses to insert records as it loads
them. I even tried switching to an earlier version of the Maria database
driver. Nothing seems to change the result. Any ideas?
Thanks!

Paul

On Thu, Mar 2, 2023 at 05:14 Anastasiya @.***> wrote:

Hello @adexios https://github.com/adexios
What settings do you have in the performance section? Are transactions
enabled?
[image: 2023-03-02 13_10_06-DBeaver Ultimate 23 0 0 - Sessions - MariaDB
10 6 1]
https://user-images.githubusercontent.com/45152336/222399122-b55be5fa-7515-478b-b663-17355c423966.png
Please provide a screen of this page.
Also, did you try to use multi-insert?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/19236#issuecomment-1451623503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQIUJVCB6ECA36XIB552U3W2BXHZANCNFSM6AAAAAAVMOX4EQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I just realized that this particular database was not migrated to MariaDB.
This is a MySQL database.  Version of the connector is 8.0.29. Still an
issue, just the wrong database in the title.
On Thu, Mar 2, 2023 at 14:31 Paul Wonderly @.***> wrote:

Thanks for the fast reply!
I tried every combination of settings - transactions or no transactions.
Multi-insert, no multi insert. It refuses to insert records as it loads
them. I even tried switching to an earlier version of the Maria database
driver. Nothing seems to change the result. Any ideas?
Thanks!

Paul

On Thu, Mar 2, 2023 at 05:14 Anastasiya @.***> wrote:

Hello @adexios https://github.com/adexios
What settings do you have in the performance section? Are transactions
enabled?
[image: 2023-03-02 13_10_06-DBeaver Ultimate 23 0 0 - Sessions - MariaDB
10 6 1]
https://user-images.githubusercontent.com/45152336/222399122-b55be5fa-7515-478b-b663-17355c423966.png
Please provide a screen of this page.
Also, did you try to use multi-insert?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/19236#issuecomment-1451623503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQIUJVCB6ECA36XIB552U3W2BXHZANCNFSM6AAAAAAVMOX4EQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I was not able to reproduce it. Can you specify which error stops the import and why do you think the file size matters?

It's been a while since no update here. Please let me know if the issue is still actual and provide additional information.


[WIP]: nodePackages: regenerate with node2nix 1.9.0

This reverts commit 3cd31450a13501ebb2c6851a59e81a60fdc38cab.

Motivation for this change
Second attempt update to node2nix 1.9.0.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I still need to investigate the problem case as described in https://github.com/NixOS/nixpkgs/pull/110545, most likely caused by zigbee2mqtt

I still need to investigate the problem case as described in https://github.com/NixOS/nixpkgs/pull/110545, most likely caused by zigbee2mqtt

Sorry dear bot @ofborg, I'm following this pull request with interest, but I am unfortunately not qualified to contribute a review.

Sorry dear bot @ofborg, I'm following this pull request with interest, but I am unfortunately not qualified to contribute a review.

I still need to investigate the problem case as described in #110545, most likely caused by zigbee2mqtt

It is definitely zigbee2mqtt because this exact same problem happened once before.

I still need to investigate the problem case as described in #110545, most likely caused by zigbee2mqtt

It is definitely zigbee2mqtt because this exact same problem happened once before.

hmm the weird thing is, I just have successfully built zigbee2mqtt locally.
Also, the following evaluation:
nix-env -f . -qaP --xml --out-path --show-trace

works for me.

hmm the weird thing is, I just have successfully built zigbee2mqtt locally.
Also, the following evaluation:
nix-env -f . -qaP --xml --out-path --show-trace

works for me.

You need to run nixpkgs-review pr 110813 --eval local otherwise the results by ofborg are used.

You need to run nixpkgs-review pr 110813 --eval local otherwise the results by ofborg are used.

@SuperSandro2000 yes I know.
This is weird situation. I think this problem is not caused by infinite recursion, but most likely by recursing too deeply. Maybe this condition is triggered when we evaluate all derivations on a cold cache, but not an individual package or a sub set.
What I think might contribute to this problem is the store derivations of NPM package deployments -- basically all dependencies including transitive dependencies in the entire closure become a direct dependency of the package to be deployed. Sadly, I see more and more NPM projects that use a substantial amount of dependencies (mostly micro-packages with only single functions).
For example, I see many packages in the closure of zigbee that are very small, such as the isarray package, which people probably should not use.
The only way to break out of this cycle, is probably a partial upgrade in which some packages are deployed with node2nix 1.9.0 and some still with 1.8.0. A binary cache probably contributes to the fact that not everything needs to be evaluated.
The real solution, of course, would be to change node2nix to not generate such large store derivations. It is already on my drawing board. This is obviously something that requires quite a bit of rework that will cost some time.

@SuperSandro2000 yes I know.
This is weird situation. I think this problem is not caused by infinite recursion, but most likely by recursing too deeply. Maybe this condition is triggered when we evaluate all derivations on a cold cache, but not an individual package or a sub set.
What I think might contribute to this problem is the store derivations of NPM package deployments -- basically all dependencies including transitive dependencies in the entire closure become a direct dependency of the package to be deployed. Sadly, I see more and more NPM projects that use a substantial amount of dependencies (mostly micro-packages with only single functions).
For example, I see many packages in the closure of zigbee that are very small, such as the isarray package, which people probably should not use.
The only way to break out of this cycle, is probably a partial upgrade in which some packages are deployed with node2nix 1.9.0 and some still with 1.8.0. A binary cache probably contributes to the fact that not everything needs to be evaluated.
The real solution, of course, would be to change node2nix to not generate such large store derivations. It is already on my drawing board. This is obviously something that requires quite a bit of rework that will cost some time.

I almost hate myself for saying that but I think maybe it doesn't make sense to block all of this work on one package. It's easy for me to say that since I don't depend on it and neither I knew the tool prior to this discussion but..... I think we should at least consider the option of just simply marking it as a broken.

I almost hate myself for saying that but I think maybe it doesn't make sense to block all of this work on one package. It's easy for me to say that since I don't depend on it and neither I knew the tool prior to this discussion but..... I think we should at least consider the option of just simply marking it as a broken.

We can keep zigbee2mqtt on an old version for now or worst case we mark it broken.

We can keep zigbee2mqtt on an old version for now or worst case we mark it broken.

I'll see if I can work out a gradual transition scenario

I'll see if I can work out a gradual transition scenario

@SuperSandro2000 I have regenerated the entire package set against a more recent version of the master branch.
Moreover, I have left zigbee2mqtt out of the generation process -- it is still deployable, but it uses node2nix 1.8.0's node-env.nix. When I run nixpkgs-review locally, I don't seem to run into this evaluation error that suggests infinite recursion.
@turboMaCk can you also take another look at this PR? Since this is an high impact change, I could use a second pair of eyes.

@raboof Maybe you can check as well, since previously you have noticed the issue.

I don't see it with this PR anymore, either!

So I've ran nixpkgs-review pr 110813 --eval local (and waited :D)
There seems to be few problems still.

elmPackages (maintained by me btw) fails to build due to breaking changes in upstream

/nix/store/gasb9j1ksfv21bv6y586lv9nljdyqz1m-node_elm-test-0.19.1-revision6.drv fails on patchBinwrap (elm specific thing) we do due to breaking change upstream
/nix/store/dlkl5yiam0cdg7ij5m8jl7zg6y0zhh7y-node_elm-review-2.4.0.drv fails due to the same reason
/nix/store/xs9jn1hvqd62s2k5sw58lpgvwy66gm7z-node_create-elm-app-5.22.0.dr also fails for the same reason

matrix-appservice-slack fails during npm run build
vscode-lldb fails because of dependecy build failing - likely unrelated
sage failed due to segfault in tests

$ git -c fetch.prune=false fetch --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/110813/head:refs/nixpkgs-review/1
$ git worktree add /home/marek/.cache/nixpkgs-review/pr-110813-2/nixpkgs fab6fcdceb2560a4ab943830a2b1632458c7a6ff
Preparing worktree (detached HEAD fab6fcdceb2)
Updating files: 100% (24290/24290), done.
HEAD is now at fab6fcdceb2 sbt-extras: 2020-12-26 → 2021-02-01
$ nix-env -f /home/marek/.cache/nixpkgs-review/pr-110813-2/nixpkgs -qaP --xml --out-path --show-trace
$ git merge --no-commit 8ba7dfad5cbd230f077e3205e572bacbe236c6ba
Removing pkgs/applications/networking/cluster/spacegun/package.json
Automatic merge went well; stopped before committing as requested
$ nix-env -f /home/marek/.cache/nixpkgs-review/pr-110813-2/nixpkgs -qaP --xml --out-path --show-trace --meta
136 packages updated:
airfield bat-extras-prettybat bitwarden-cli emojione EPGStation etcher imgbrd-grabber iosevka ldgallery lumo nixui node_base16-builder node_castnow node_create-cycle-app elmPackages.create-elm-app (5.21.0 → 5.22.0) node_cryptpad node_dat node_elm-analyse node_elm-coverage elmPackages.elm-doc-preview (5.0.3 → 5.0.5) node_elm-live node_elm-optimize-level elmPackages.elm-review (2.3.3 → 2.4.0) elmPackages.elm-test (0.19.1-revision4 → 0.19.1-revision6) node_elm-upgrade node_elm-verify-examples node_elm-xref node_fast-cli flood (4.3.1 → 4.4.0) node_fx node_gtop node_hueadm node_imapnotify node_joplin lessc (4.1.0 → 4.1.1) node_mastodon-bot node_matrix-appservice-slack node_mirakurun n8n (0.96.0 → 0.105.0) netlify-cli (3.4.3 → 3.4.6) newman (5.2.1 → 5.2.2) pm2 (4.5.1 → 4.5.4) node_postcss-cli node_pscid node_pulp node_purescript-psa redoc-cli (0.10.2 → 0.10.3) node_shout node_sloc node_spacegun node_thelounge node_triton node_whitebophir node_wring node_yaml-language-server node__at_antora_slash_cli elmPackages.elm-language-server (1.13.2 → 2.0.2) node__at_google_slash_clasp node__at_webassemblyjs_slash_cli node__at_webassemblyjs_slash_repl node__at_webassemblyjs_slash_wasm-strip node__at_webassemblyjs_slash_wasm-text-gen node__at_webassemblyjs_slash_wast-refmt parity-ui python3.7-batchspawner python3.7-dockerspawner python3.7-jupyterhub python3.7-jupyterhub-ldapauthenticator python3.7-jupyterhub-systemdspawner python3.7-jupyterhub-tmpauthenticator python3.7-oauthenticator python3.8-batchspawner python3.8-dockerspawner python3.8-jupyterhub python3.8-jupyterhub-ldapauthenticator python3.8-jupyterhub-systemdspawner python3.8-jupyterhub-tmpauthenticator python3.8-oauthenticator python3.9-batchspawner python3.9-dockerspawner python3.9-jupyterhub python3.9-jupyterhub-ldapauthenticator python3.9-jupyterhub-systemdspawner python3.9-jupyterhub-tmpauthenticator python3.9-oauthenticator remarkjs ripcord sage sage sage slack slack styx teleprompter twemoji-color-font uchiwa vimplugin-coc-css vimplugin-coc-diagnostic vimplugin-coc-emmet vimplugin-coc-eslint vimplugin-coc-git vimplugin-coc-go vimplugin-coc-highlight vimplugin-coc-html vimplugin-coc-imselect vimplugin-coc-java vimplugin-coc-jest vimplugin-coc-json vimplugin-coc-lists vimplugin-coc-markdownlint vimplugin-coc-metals vimplugin-coc-pairs vimplugin-coc-prettier vimplugin-coc-python vimplugin-coc-r-lsp vimplugin-coc-rls vimPlugins.coc-rust-analyzer (0.30.0 → 0.31.0) vimplugin-coc-smartf vimplugin-coc-snippets vimplugin-coc-solargraph vimplugin-coc-stylelint vimplugin-coc-tabnine vimplugin-coc-tslint vimplugin-coc-tslint-plugin vimplugin-coc-tsserver vimplugin-coc-vetur vimplugin-coc-vimlsp vimplugin-coc-vimtex vimplugin-coc-wxml vimplugin-coc-yaml vimplugin-coc-yank vimplugin-YouCompleteMe vscode-extension-MS-python-vscode-pylance vscode-extension-rust-analyzer-unstable vscode-extension-vscode-lldb ycmd

$ nix --experimental-features nix-command build --no-link --keep-going --option build-use-sandbox relaxed -f /home/marek/.cache/nixpkgs-review/pr-110813-2/build.nix
builder for '/nix/store/gasb9j1ksfv21bv6y586lv9nljdyqz1m-node_elm-test-0.19.1-revision6.drv' failed with exit code 1; last 10 log lines:
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/xml2js):
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/xml2js failed: cache mode is 'only-if-cached' but no cached response available.

  up to date in 0.844s

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

  linking elmi-to-json
  ln: failed to create symbolic link 'node_modules/elmi-to-json/bin/elmi-to-json': No such file or directory
builder for '/nix/store/dlkl5yiam0cdg7ij5m8jl7zg6y0zhh7y-node_elm-review-2.4.0.drv' failed with exit code 1; last 10 log lines:
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/xo):
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/xo failed: cache mode is 'only-if-cached' but no cached response available.

  up to date in 1.609s

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

  linking elm-json
  ln: failed to create symbolic link 'node_modules/elm-json/bin/elm-json': No such file or directory
builder for '/nix/store/qi2dc7n8345dzr4xpa1izarirsnjhinw-node_matrix-appservice-slack-1.4.0.drv' failed with exit code 2; last 10 log lines:
  npm ERR! errno 2
  npm ERR<EMAIL_ADDRESS>prepare: `npm run build`
  npm ERR! Exit status 2
  npm ERR!
  npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

  npm ERR! A complete log of this run can be found in:
  npm ERR!     /build/.npm/_logs/2021-02-02T17_01_14_195Z-debug.log

builder for '/nix/store/xs9jn1hvqd62s2k5sw58lpgvwy66gm7z-node_create-elm-app-5.22.0.drv' failed with exit code 1; last 10 log lines:
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/unexpected failed: cache mode is 'only-if-cached' but no cached response available.
  npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

  up to date in 12.872s

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

  linking elmi-to-json
  ln: failed to create symbolic link 'node_modules/elmi-to-json/bin/elmi-to-json': No such file or directory
builder for '/nix/store/nz24mhs18vadzw1q6ljzvxxhcd3lmhmi-vscode-lldb-adapter-1.5.3.drv' failed with exit code 101; last 10 log lines:
  For more information about this error, try `rustc --explain E0277`.
  The following warnings were emitted during compilation:

  warning: Could not find CMakeCache.txt

  error: could not compile `lldb`

  To learn more, run the command again with --verbose.
  warning: build failed, waiting for other jobs to finish...
  error: build failed
cannot build derivation '/nix/store/wlfk2q8q2l9kb56dyf955ygjbsckgmfh-vscode-lldb-1.5.3-vsix.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/x9wyv5bvg01zzybz8wfwpl5plx11pvx0-vscode-extension-vscode-lldb.drv': 1 dependencies couldn't be built
builder for '/nix/store/xm4x8gx5nzisig0ablf1a17hz7gka9p7-sage-tests-9.2.drv' failed with exit code 17; last 10 log lines:
  ----------------------------------------------------------------------t
  sage -t --long --random-seed=0 /nix/store/kc7cf6p4z8qm7hppw40kazlwyv54p2fr-sage-src-9.2/src/sage/interfaces/singular.py  # Killed due to segmentation fault
  sage -t --long --random-seed=0 /nix/store/kc7cf6p4z8qm7hppw40kazlwyv54p2fr-sage-src-9.2/src/sage/plot/plot3d/base.pyx  # 11 doctests failed
  sage -t --long --random-seed=0 /nix/store/kc7cf6p4z8qm7hppw40kazlwyv54p2fr-sage-src-9.2/src/sage/plot/animate.py  # 2 doctests failed
  sage -t --long --random-seed=0 /nix/store/kc7cf6p4z8qm7hppw40kazlwyv54p2fr-sage-src-9.2/src/sage/repl/rich_output/backend_ipython.py  # 1 doctest failed
  sage -t --long --random-seed=0 /nix/store/kc7cf6p4z8qm7hppw40kazlwyv54p2fr-sage-src-9.2/src/sage/repl/rich_output/display_manager.py  # 1 doctest failed
  ----------------------------------------------------------------------
  Total time for all tests: 2026.6 seconds
      cpu time: 17888.5 seconds
      cumulative wall time: 25844.6 seconds
cannot build derivation '/nix/store/nw6afad4d7nhwhrxrs4r23dwsm5h40p8-sage-9.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/x8079n1y6b9awabwiqafqirfaqkv879s-sage-9.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/m7mxch2vyklbiz5nxyfa7744pby97cwz-env.drv': 7 dependencies couldn't be built
error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------- nix
build of '/nix/store/m7mxch2vyklbiz5nxyfa7744pby97cwz-env.drv' failed

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/110813

3 packages marked as broken and skipped:
dat remarkjs vimPlugins.coc-imselect

7 packages failed to build:
elmPackages.create-elm-app elmPackages.elm-review elmPackages.elm-test matrix-appservice-slack sage sageWithDoc vscode-extensions.vadimcn.vscode-lldb

124 packages built:
airfield antora base16-builder bat-extras.prettybat bitwarden-cli castnow create-cycle-app cryptpad elmPackages.elm-analyse elmPackages.elm-coverage elmPackages.elm-doc-preview elmPackages.elm-language-server elmPackages.elm-live elmPackages.elm-optimize-level-2 elmPackages.elm-upgrade elmPackages.elm-verify-examples elmPackages.elm-xref emojione epgstation etcher fast-cli flood fx google-clasp gtop hueadm imapnotify imgbrd-grabber iosevka joplin ldgallery lessc lumo mastodon-bot mirakurun n8n netlify-cli newman nixui parity-ui pm2 postcss-cli pscid pulp purescript-psa python37Packages.batchspawner python37Packages.dockerspawner python37Packages.jupyterhub python37Packages.jupyterhub-ldapauthenticator python37Packages.jupyterhub-systemdspawner python37Packages.jupyterhub-tmpauthenticator python37Packages.oauthenticator python38Packages.batchspawner python38Packages.dockerspawner python38Packages.jupyterhub python38Packages.jupyterhub-ldapauthenticator python38Packages.jupyterhub-systemdspawner python38Packages.jupyterhub-tmpauthenticator python38Packages.oauthenticator python39Packages.batchspawner python39Packages.dockerspawner python39Packages.jupyterhub python39Packages.jupyterhub-ldapauthenticator python39Packages.jupyterhub-systemdspawner python39Packages.jupyterhub-tmpauthenticator python39Packages.oauthenticator redoc-cli ripcord shout slack sloc spacegun styx teleprompter thelounge triton twemoji-color-font uchiwa vimPlugins.YouCompleteMe vimPlugins.coc-css vimPlugins.coc-diagnostic vimPlugins.coc-emmet vimPlugins.coc-eslint vimPlugins.coc-git vimPlugins.coc-go vimPlugins.coc-highlight vimPlugins.coc-html vimPlugins.coc-java vimPlugins.coc-jest vimPlugins.coc-json vimPlugins.coc-lists vimPlugins.coc-markdownlint vimPlugins.coc-metals vimPlugins.coc-pairs vimPlugins.coc-prettier vimPlugins.coc-python vimPlugins.coc-r-lsp vimPlugins.coc-rls vimPlugins.coc-rust-analyzer vimPlugins.coc-smartf vimPlugins.coc-snippets vimPlugins.coc-solargraph vimPlugins.coc-stylelint vimPlugins.coc-tabnine vimPlugins.coc-tslint vimPlugins.coc-tslint-plugin vimPlugins.coc-tsserver vimPlugins.coc-vetur vimPlugins.coc-vimlsp vimPlugins.coc-vimtex vimPlugins.coc-wxml vimPlugins.coc-yaml vimPlugins.coc-yank vscode-extensions.matklad.rust-analyzer vscode-extensions.ms-python.vscode-pylance wasm-strip wasm-text-gen wast-refmt webassemblyjs-cli webassemblyjs-repl whitebophir wring yaml-language-server ycmd

error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------- nix
build log of '/nix/store/9rggvly206hpc9b9k4h3qp0xj18lfl7k-lumo-1.10.1.drv' is not available
error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------- nix
build log of '/nix/store/nw6afad4d7nhwhrxrs4r23dwsm5h40p8-sage-9.2.drv' is not available
error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------- nix
build log of '/nix/store/x8079n1y6b9awabwiqafqirfaqkv879s-sage-9.2.drv' is not available
error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------- nix
build log of '/nix/store/x9wyv5bvg01zzybz8wfwpl5plx11pvx0-vscode-extension-vscode-lldb.drv' is not available
$ nix-shell /home/marek/.cache/nixpkgs-review/pr-110813-2/shell.nix
these 4 paths will be fetched (0.51 MiB download, 2.47 MiB unpacked):
  /nix/store/7j4fadgmhydwa3k89zddqmk5sh8swfwz-bash-interactive-4.4-p23-man
  /nix/store/bgn5j1x94ynfs3kpi0wdhzd9xi45c8ab-bash-interactive-4.4-p23-info
  /nix/store/dx9ghdnwi1bpxjc250rkhpzzfs6y1nix-bash-interactive-4.4-p23-doc
  /nix/store/wa5xkjha3zxiqljnb2mp1ym9z4w07djp-bash-interactive-4.4-p23-dev
copying path '/nix/store/dx9ghdnwi1bpxjc250rkhpzzfs6y1nix-bash-interactive-4.4-p23-doc' from 'https://cache.nixos.org'...
copying path '/nix/store/bgn5j1x94ynfs3kpi0wdhzd9xi45c8ab-bash-interactive-4.4-p23-info' from 'https://cache.nixos.org'...
copying path '/nix/store/7j4fadgmhydwa3k89zddqmk5sh8swfwz-bash-interactive-4.4-p23-man' from 'https://cache.nixos.org'...
copying path '/nix/store/wa5xkjha3zxiqljnb2mp1ym9z4w07djp-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...

For elmPackages I'm aware of the breaking changes in upstream from https://github.com/NixOS/nixpkgs/pull/110845. I would suggest to reset/revert the changes - I'll take care of them in separate PR. I also need to sync with upstreams on a few things.
I'm not sure about the rest though. Let me know if I could help you with this further.

@turboMaCk I just fixed the matrix-appservice-slack package by using a different generation strategy. I'm still investigating the others.
About reverting changes -- do you mean reverting the changes that are related to the Elm packages?

@svanderburg yes just revert all changes in  pkgs/development/compilers/elm/ directory. It should just work once you do so as the previous version was independent of nodePackages. Once this PR is merged I'll open separate PR and unify node-env.nix there and ping you for the review.

Of course unless you want to solve the problem yourself. I think I even know how to do quick fix it. I just felt it might be better to take this off your shoulders since this is quite a big PR even excluding that. Just let me know what you prefer.
a) you can just discard these changes and I'll take care of it
b) you can try to just remove elmi-to-json from calls like patchBinwrap [elmi-to-json, elm-instrument] someDerivation
c) I can open PR targeting this during tomorrow so it can be merged together.
Personally I think a) makes most sense for you though as it minimizes surprises and delays and maximizes change of getting this merged soon.

@turboMaCk Ok, clear. I'll go for option a then: I'll just revert what's inside the elm directory.

@ofborg eval

hmm it closed all of a sudden :(

@turboMaCk I reverted the elm/ commits. I hope it evaluates now, there was a package named: galene that was still using the old deprecated stdenv.lib reference.

@svanderburg I've actually tested it locally before posting the reply and nix-build -A elmPackages just went through straight from the cache so :crossed_fingers:
I'll also let nixpkgs-review ran again (this time even my old macbook pro to see how this does on Darwin) probably over the night if it take too long. But I think this is :+1: from my side at least.

@turboMaCk I also briefly check the other two packages that did not build, but they fail because some tool (that has an NPM package as a dependency) in the build process fails, with a segfault.
Although I can't be 100% sure, I think it's very unlikely that it was caused by an NPM dependency upgrade.

@turboMaCk Thank you for all the assistance! I believe in the previous PR (that we reverted) we came to the same conclusion that the ldgallery/viewer package was already broken on Darwin.
I'll wait until tomorrow, so that people still have the opportunity to respond. Hopefully, nothing in the master branch will conflict in the meantime.
I also have to give node2nix some more thought on how to deal with these problematic packages, such as zigbee2mqtt. Sadly, the generation technique that I'm currently using has its limits, in particular on projects with 20K+ dependencies, and many levels of dependencies. This seems to become more common these days -- I think NPM can be considered a solution that automates code copy-and-pasting, that we used to do manually from Stackoverflow in the past.
Because NPM works so well, people are installing more and more package dependencies in projects (and those packages do the same) causing explosions of dependencies.
Probably in the near future, we may run into more weird limitations that the Nix package manager/Nix expression languages has difficulties coping with. That's why I think we have to be careful with adding new NPM projects to Nixpkgs, until I found a better to deal with these big/complex projects. This is still ongoing research.

@ofborg eval

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110813 run on x86_64-darwin 1

1 package marked as broken and skipped:

nixui

1 package failed to build and already failed to build on hydra master:

ldgallery: log was empty

1 package failed to build and are new build failure:

tests.writers: log was empty

28 packages built:

bat-extras.prettybat
python37Packages.batchspawner
python37Packages.dockerspawner
python37Packages.jupyterhub
python37Packages.jupyterhub-ldapauthenticator
python37Packages.jupyterhub-systemdspawner
python37Packages.jupyterhub-tmpauthenticator
python37Packages.oauthenticator
python38Packages.batchspawner
python38Packages.dockerspawner
python38Packages.jupyterhub
python38Packages.jupyterhub-ldapauthenticator
python38Packages.jupyterhub-systemdspawner
python38Packages.jupyterhub-tmpauthenticator
python38Packages.oauthenticator
python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator
styx
uchiwa
vimPlugins.YouCompleteMe
vscode-extensions.matklad.rust-analyzer
whitebophir
ycmd

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:
python37Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python37Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

python38Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python38Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

python39Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python39Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

ycmd:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern '/nix/store/nahdkr6gb1717grd0yqbnnas7z5wsfnn-ycmd-2020-02-22/lib/ycmd/ycmd/__main__.py' doesn't match anything in file '/nix/store/nahdkr6gb1717grd0yqbnnas7z5wsfnn-ycmd-2020-02-22/lib/ycmd/ycmd/__main__.py'

Please check the offending substituteInPlace for typos or changes in source.
warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/development/tools/misc/ycmd/default.nix:26:3:
   |
26 |   buildPhase = ''
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/missing-phase-hooks.md
warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/tools/misc/ycmd/default.nix:43:3:
   |
43 |   installPhase = ''
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/missing-phase-hooks.md
warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/tools/misc/ycmd/default.nix:96:5:
   |
96 |     license = licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

@SuperSandro2000 Looks like the output matches our expectation. The only exception is the failing writers test -- the fact that it fails with a log was empty error may have been caused by a problem with the build infrastructure. Not sure, if we can redo that build.
The rest (I believe) should not cause any problems.

I have blacklisted writers test in nixpkgs-review. The other things are expected.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110813 run on x86_64-linux 1

3 packages marked as broken and skipped:

image_optim
remarkjs
vimPlugins.coc-imselect

1 package blacklisted:

tests.writers

1 package failed to build and are new build failure:

vscode-extensions.vadimcn.vscode-lldb: log was empty

114 packages built:

airfield
antora
base16-builder
bat-extras.prettybat
bitwarden-cli
castnow
create-cycle-app
cryptpad
emojione
epgstation
etcher
fast-cli
flood
fx
google-clasp
gtop
hueadm
imapnotify
imgbrd-grabber
joplin
ldgallery
lessc
mastodon-bot
matrix-appservice-slack
mirakurun
n8n
netlify-cli
newman
nixui
parity-ui
pm2
postcss-cli
pscid
pulp
purescript-psa
python37Packages.batchspawner
python37Packages.dockerspawner
python37Packages.jupyterhub
python37Packages.jupyterhub-ldapauthenticator
python37Packages.jupyterhub-systemdspawner
python37Packages.jupyterhub-tmpauthenticator
python37Packages.oauthenticator
python38Packages.batchspawner
python38Packages.dockerspawner
python38Packages.jupyterhub
python38Packages.jupyterhub-ldapauthenticator
python38Packages.jupyterhub-systemdspawner
python38Packages.jupyterhub-tmpauthenticator
python38Packages.oauthenticator
python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator
redoc-cli
ripcord
shout
slack
sloc
spacegun
styx
teleprompter
thelounge
triton
twemoji-color-font
uchiwa
vimPlugins.YouCompleteMe
vimPlugins.coc-css
vimPlugins.coc-diagnostic
vimPlugins.coc-emmet
vimPlugins.coc-eslint
vimPlugins.coc-git
vimPlugins.coc-go
vimPlugins.coc-highlight
vimPlugins.coc-html
vimPlugins.coc-java
vimPlugins.coc-jest
vimPlugins.coc-json
vimPlugins.coc-lists
vimPlugins.coc-markdownlint
vimPlugins.coc-metals
vimPlugins.coc-pairs
vimPlugins.coc-prettier
vimPlugins.coc-python
vimPlugins.coc-r-lsp
vimPlugins.coc-rls
vimPlugins.coc-rust-analyzer
vimPlugins.coc-smartf
vimPlugins.coc-snippets
vimPlugins.coc-solargraph
vimPlugins.coc-stylelint
vimPlugins.coc-tabnine
vimPlugins.coc-tslint
vimPlugins.coc-tslint-plugin
vimPlugins.coc-tsserver
vimPlugins.coc-vetur
vimPlugins.coc-vimlsp
vimPlugins.coc-vimtex
vimPlugins.coc-wxml
vimPlugins.coc-yaml
vimPlugins.coc-yank
vscode-extensions.matklad.rust-analyzer
vscode-extensions.ms-python.vscode-pylance
wasm-strip
wasm-text-gen
wast-refmt
webassemblyjs-cli
webassemblyjs-repl
whitebophir
wring
yaml-language-server
ycmd

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:
python37Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

python37Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python38Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

python38Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python39Packages.jupyterhub:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern ''npm', 'run', 'lessc', '--'' doesn't match anything in file 'setup.py'

Please check the offending substituteInPlace for typos or changes in source.

python39Packages.jupyterhub-systemdspawner:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

ycmd:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern '/nix/store/p35vawy3d8ghgbqncksl9d8dqv47p5wk-ycmd-2020-02-22/lib/ycmd/ycmd/__main__.py' doesn't match anything in file '/nix/store/p35vawy3d8ghgbqncksl9d8dqv47p5wk-ycmd-2020-02-22/lib/ycmd/ycmd/__main__.py'

Please check the offending substituteInPlace for typos or changes in source.
warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/tools/misc/ycmd/default.nix:96:5:
   |
96 |     license = licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md
warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/development/tools/misc/ycmd/default.nix:26:3:
   |
26 |   buildPhase = ''
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/missing-phase-hooks.md
warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/tools/misc/ycmd/default.nix:43:3:
   |
43 |   installPhase = ''
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/missing-phase-hooks.md

@SuperSandro2000 I just reverted that change (I did an amend/force push to make sure it won't get into master in by accident).
We also briefly encountered that problem with the vscode-extensions.vadimcn.vscode-lldb package. It's indirectly caused by sage that segfaults in the build process of the plugin. A node package is an indirect dependency of it. Not sure, if there's a direct correlation between them.

Anyway, I think we have pretty much everything covered now. I'm now awaiting the new evaluation evaluation status.

@SuperSandro2000 @turboMaCk I think we're ready right? I intend to merge this very soon, or feel free to click on the merge button :+1:

Agree - :+1: merge

@timokau @omasanori I forgot to disable the intermittent segfaulting Sage test, which masked the fact that a three.js upgrade here broke another Sage test. Apologies for not taking action earlier, I will fix the three.js breakage and disable the other test today.

Thanks @collares. For reference: #113603


Simplify acquisition of grains of infinity.

Description
We've been discussing this a lot internally and had a good amount of feedback expressing frustration with the current means of acquiring grains of infinity (and coal dust). As such, this PR trivializes the process.

The manual crushing of deepslate and coal has been removed.
Dark Steel can now be crafted with 2 coal in place of 1 coal dust (coal dust option is still available) - this has already been merged
Grains of infinity can now be acquired by burning deepslate, this has a 35% chance to drop one grain for each block set on fire. This is intended as an early means of production - as well as deter users from using deepslate fire as automation.
Bedrock fire will now produce grains at an 80% rate, producing between 1-3 grains. This incentivizes a trip down to Y-32 and is a prime candidate for automation (especially once fire water is re-implemented).
A new SAG Mill recipe has been added for cobbled deepslate, turning it into cobblestone and a byproduct of grains of infinity at 30% chance (grinding ball modifiable). This is an alternative way to automate grains, fed by something like a quarry.

(In addition, the cobblestone recipe has been split into a normal cobblestone recipe, and a mossy variant that has a chance to produce a vine as a byproduct - this recipe is up for change still)

Breaking Changes
This changes the early game of Ender IO - but nothing that can be considered "breaking" as far as code goes.

Checklist

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
[x] I have made corresponding changes to the documentation.
[x] My changes are ready for review from a contributor.

30% for the SAG mill recipe feels a bit high. Deep slate isn't exactly rare, and throwing a stack or ten in to get more grains than you could ever use is so easy it invalidates any other method.
It's a bit evil, but assuming eio machines still capture their owner, the SAG mill could count how often a player has executed that recipe and use that to reduce the chance. Reducing the change by 33% (relative) for every 5 grains produced (0-4 30%, 5-9 20%, 10-14 14%, 15-20 9%, ...) could work.
Also, as blocks of deep slate are not infinite (indestructible), firecrafting should destroy them. (Or at least turn them into their cobble version, to prevent firemining. Mmmh, firemining could be interesting...maybe have a chance to mine the block with a chance to drop grains when the fire is extinguished by water? This is as close to real-life firemining as I can think of.)

30% for the SAG mill recipe feels a bit high. Deep slate isn't exactly rare, and throwing a stack or ten in to get more grains than you could ever use is so easy it invalidates any other method.

Yeah that is fair, I'll look to reduce it to something likely in the ballpark of 5-15%. I don't think the reduction by player is something I'd be keen to explore.

Also, as blocks of deep slate are not infinite (indestructible), firecrafting should destroy them. (Or at least turn them into their cobble version, to prevent firemining. Mmmh, firemining could be interesting...maybe have a chance to mine the block with a chance to drop grains when the fire is extinguished by water? This is as close to real-life firemining as I can think of.)

This is a great idea, I think transforming it into standard cobblestone afterwards provides consistency with the SAG Mill recipe grinding the void out of the stone. Firemining also sounds like a cool idea - but I'd probably defer that to another issue/PR for future evaluation :)
Thanks for the feedback!

The chance of obtaining grains of infinity from sag milling is lowered from 30% to 12% and burning deepslate will now convert the block below the fire to cobblestone afterwards.
We'll need a better way to show this in JEI, but I think in the interests of playtesting this - we can leave that for now.

This is unrelated to the PR, but for simplicity's sake:
I just had a look at the handler out of curiosity, and it looks a bit wasteful. (Also very much as I remember it, so this probably is my fault.)
I'd suggest a couple of changes:

Put https://github.com/Team-EnderIO/EnderIO/blob/65f3b09b23cb805049cf24b5016936ee06764319/enderio-base/src/main/java/com/enderio/base/common/handler/FireCraftingHandler.java#L70-L88 into a getMatchingRecipe() method
Put if (getMatchingRecipe() != null) { ...} return; inside if (isFire) {
Surround spawnInfinityDrops(...) with a if (getMatchingRecipe() instanceof FireCraftingRecipe matchingRecipe) { (or if ((FireCraftingRecipe matchingRecipe = getMatchingRecipe()) != null) {)
Move the // Grab useful fields. stuff inside the two if blocks just above where it's needed. Sadly this means duplicating it, but this is not an event to be picky---NeighborNotifyEvents are fired very often.
I think the if (FIRE_TRACKER.isEmpty() && !isFire) { now has no benefit anymore.

And then ignore the complicated description above and look at what I cobbled up in a text editor: https://gist.github.com/HenryLoenwind/e276c7f437120011f1c84175496c531d
I think this would greatly reduce the time spent in this event handler.

This is unrelated to the PR, but for simplicity's sake:
I just had a look at the handler out of curiosity, and it looks a bit wasteful. (Also very much as I remember it, so this probably is my fault.)
I'd suggest a couple of changes:
* Put https://github.com/Team-EnderIO/EnderIO/blob/65f3b09b23cb805049cf24b5016936ee06764319/enderio-base/src/main/java/com/enderio/base/common/handler/FireCraftingHandler.java#L70-L88
   into a getMatchingRecipe() method

* Put `if (getMatchingRecipe() != null) { ...} return;` inside `if (isFire) {`

* Surround `spawnInfinityDrops(...)` with a `if (getMatchingRecipe() instanceof FireCraftingRecipe matchingRecipe) {` (or `if ((FireCraftingRecipe matchingRecipe = getMatchingRecipe()) != null) {`)

* Move the `// Grab useful fields.` stuff inside the two if blocks just above where it's needed. Sadly this means duplicating it, but this is not an event to be picky---NeighborNotifyEvents are fired very often.

* I think the `if (FIRE_TRACKER.isEmpty() && !isFire) {` now has no benefit anymore.

And then ignore the complicated description above and look at what I cobbled up in a text editor: https://gist.github.com/HenryLoenwind/e276c7f437120011f1c84175496c531d
I think this would greatly reduce the time spent in this event handler.

Yeah I was thinking that when I was looking at the file again - I think I'll log this as an issue and we can handle this down the line. Thanks again!


Refactor SimpleProcessingService to leverage Jobs

Coverage decreased (-0.3%) to 24.549% when pulling af02af1352bc974a4d735343f610f81db70172a6 on sprint-sep18-b03663-processor-refactor into b23d50bbf3137878db56e76170e865871c9b6883 on sprint-sep18-b03663-implement_job.


refactor(api): merge signaling api context into control

What this PR changes/adds
Merge the signaling-api context into the control-api context
Why it does that
we should keep the context number consistent to the ones described in this decision record:
https://github.com/eclipse-edc/Connector/blob/main/docs/developer/decision-records/2022-11-09-api-refactoring/renaming.md
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #4175
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Attention: Patch coverage is 26.66667% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 75.01%. Comparing base (7f20ba5) to head (09d2eae).
Report is 255 commits behind head on main.

Files
Patch %
Lines

.../dataplane/api/DataPlaneSignalingApiExtension.java
0.00%
11 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4176      +/-   ##
==========================================
+ Coverage   71.74%   75.01%   +3.26%
==========================================
  Files         919     1012      +93
  Lines       18457    20561    +2104
  Branches     1037     1160     +123
==========================================
+ Hits        13242    15423    +2181
+ Misses       4756     4630     -126
- Partials      459      508      +49

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


feat(openssl): version upgrade to v0.10.48 in cactus-plugin-keychain-vault

fix: issue #2365

Thankyou!


update es_AR translation.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Translation

Great. Thanks!


Parts needed for a LibreMonitor are - broken battery link

The lipo link indicated is broken

I still use a 100 mAh lipo that I took out of a little model helicopter. It lasts a full day from early morning to late evening with the transfer interval set to two minutes. To my understanding any lipo with 110 mAh or more should do. If you want a longer time you could go higher, e.g. 200 mAh. A higher discharge rate is probably better and enables using a faster charger. I corrected the link in the readme for a lipo that should be appropriate.


Move version top strings to the Jinja template

Codecov Report

Merging #147 into master will decrease coverage by 0.93%.
The diff coverage is 67.74%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage   93.61%   92.68%   -0.94%
==========================================
  Files          16       15       -1
  Lines         658      629      -29
  Branches       66       68       +2
==========================================
- Hits          616      583      -33
- Misses         26       28       +2
- Partials       16       18       +2

Impacted Files
Coverage Δ

src/towncrier/test/test_cli.py
100% <ø> (ø)
:arrow_up:

src/towncrier/_settings.py
83.33% <100%> (+5.55%)
:arrow_up:

src/towncrier/check.py
94% <100%> (ø)
:arrow_up:

src/towncrier/_builder.py
100% <100%> (ø)
:arrow_up:

src/towncrier/test/test_check.py
100% <100%> (ø)
:arrow_up:

src/towncrier/test/test_write.py
100% <100%> (ø)
:arrow_up:

src/towncrier/test/test_format.py
100% <100%> (ø)
:arrow_up:

src/towncrier/__init__.py
84.05% <30%> (-6.86%)
:arrow_down:

src/towncrier/_writer.py
86.36% <33.33%> (-4.12%)
:arrow_down:

src/towncrier/_project.py
56.75% <66.66%> (ø)
:arrow_up:

... and 4 more

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 018a6d8...a3e4344. Read the comment docs.

This is nice, but seems backward incompatible if someone uses their own template file and the default string? I do not mind this, but there seems to options:

Note in the release notes that users who want the old behaviour need to to set the title_format manually now.
Use my version of forcing users who want to use this to set title_format = false?


doc: improve Python section

Motivation for this change
Avoid confusion as in https://github.com/NixOS/nixpkgs/pull/116325#discussion_r593946638.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@FRidh Is this okay?

ping @FRidh


multiple modifiers in chord's root not recognized

See for instance F##:dim7, Abb:maj7
similar to Issue #8
related to Issue #6

fixed in PR #5


CB-5660 Respect declared Role Config Groups in Data Hub template gene…

…ration

This simply removes the current cloning code for host groups.
This is an RFC only; will update with the proper unit test if this is a viable solution.
Tested by copying RCGs into different host templates in kafka-without-hdfs.bp.

Can one of the admins verify this patch?

Closing this, it is fixed by other commit.


Fix scout search

for some reason, in my setup scout search only return up to 20 result, thus causing the table pagination never get more than 1 page

engine: meilisearch:v1.1.0
Model->perPage should be laravel default 15
meilisearch index setting: "pagination":{"maxTotalHits":1000}"

Found the reason for 20 records, meilisearch default value https://www.meilisearch.com/docs/reference/api/search#number-of-results-per-page
this PR changes Model::search calls to pass in hitsPerPage option to return more result so that eloquent pagination can work properly

I'm not near a computer atm but the first thing that springs to mind, is hitsPerPage a Meilisearch specific parameter?

I'm not near a computer atm but the first thing that springs to mind, is hitsPerPage a Meilisearch specific parameter?

Algolia  have that too but I’m not able to test the before and after change
From scout source code it seems other engines are not using it so no effect on them
On algolia Doc  it mentions can set global settings for hitsPerPage to change the default: 20, but not meilisearch
so another approach I can think of is ::search(‘term’)->paginate(1000)->page(1)
So that the engine will handle their own perPage equivalent

I'm going to close this, as I don't think we should have driver-specific settings in the core. Feel free to continue to discuss this here and open another PR if we have a better approach.

@glennjacobs I think I found the root cause to this issue and a fix that is not driver specific
issue:
we are not using Scout's pagination but instead return scout result's IDs into eloquent whereIn and paginate on eloquent.
https://github.com/lunarphp/lunar/blob/0b54f4d269e15b60b4b4bd12ba9dfef86eb5d112/packages/admin/src/Tables/Builders/ProductsTableBuilder.php#L24-L45
the issue with this is we are always on the first page of the Scout search, and is subject to search engines default per page limit
suppose we should able to set the value on the engine but as mentioned earlier

On algolia Doc it mentions can set global settings for hitsPerPage to change the default: 20, but not meilisearch

also there is no such config in Scout.
a potential fix would be to rewrite the getData in table builder as seen in the above snippet to use scout's ->paginate($this->perPage), but I not sure how well it works with the additional filters and queryExtenders etc, and also the switch to Filament's table builder
for a driver agnostic approach and quick fix, would be similar to this current PR changes but instead of using the options() api, I would suggest to make use of scout's take() api and let it handle it
-$query->whereIn('id', Product::search($this->searchTerm)->keys());
+$query->whereIn('id', Product::search($this->searchTerm)
+                ->take(1000) // arbitrary large per page size
+                ->query(fn ($query) => $query->select('id')) // to limit the retrieval
+                ->keys());

let me know what do you think

@wychoong sounds reasonable, but does this work with Meilisearch and changing it's default response amount? If so, then great.

yes it works fine with Meilisearch, not tested with Algolia but the api is supported in Scout engines
this with Meilisearch
https://github.com/lunarphp/lunar/assets/67364036/b3b5fe73-81af-4bc4-9de8-a631885ed8d3


Fixed documentation urls on README.md

I am not following existing PR template because it's just very little update for fixing broken urls on README.

Thx for spotting this one.
Actually, we think that pointing to the documentation is the solution.
Could you please update your PR and point to URLs from the documentation, e.g.
https://docs.traefik.io/configuration/backends/docker/
instead of
docs/configuration/backends/docker.md
Thanks again for your help.

Hello Gérald, I've updated urls👌

Thank you :smile:


[l10n] zhTW refinement

We use 開 rather than 开 as 'open' in Traditional Chinese.
In Taiwan we usually use 載入中/讀取中 rather than 加載中. Even though languages do affect each other.

[x] I have followed (at least) the PR section of the contributing guide.

@shakatoday Much appreciated, thanks!


fzf works with Cygwin

[ ] I have read through the manual page (man fzf)
[ ] I have the latest version of fzf
[ ] I have searched through the existing issues

Info

OS

[ ] Linux
[ ] Mac OS X
[x] Windows
[ ] Etc.

Shell

[x] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
Not really an issue but information.
fzf works very nicely with Cygwin mintty and Windows Terminal (via ssh) if you use https://github.com/junegunn/fzf/issues/2798#issuecomment-1229376159
I suggest adding this information in https://github.com/junegunn/fzf/wiki/Cygwin

Thanks for letting me know. Anyone can edit the wiki page, so would you be willing to add the information to it?

Update the wiki


Cannot add user to group

When editing a group, I cannot add the first user of the list (regardless of the page number, or the filter condition) : the three-dotted button won't do anything.

Fixed by #234


Feature - Cloud Apps

Summary
Merge feature branch onto master.
This feature includes:

Binding fetching on channel switch
Handle binding refresh on websocket event
Bindings

Channel Header
Post option
Commands
Embedded bindings (in post)

Calls
Call response handling

OK
Error
Navigate To
Form

Modal Forms
Feature flag code guard (no code is executed if the feature flag is disabled)
Invalid binding filtering

@larkox / @catalintomai, can we work to break this long running feature branch into a series of smaller commits, clearly breaking apart distinct efforts around refactoring from the new functionality?

@lieut-data , we can definitely try to do that - do you see the QA effort splitting as well for the individual pieces? We'd like for QA to be able to test user scenarios, and doing QA on individual pieces (refactoring vs. additive code) might not work that well.

Thanks, @catalintomai! There will definitely be unavoidable QA effort on account of the multiple PRs. My hope, though, is that by breaking things up, it will allow for additional, focused testing on the refactored areas in addition to the key feature changes being made. Ultimately, I defer to the QA Guild's judgment though!

cc: @DHaussermann for the QA take on the issue.

Yes, as mentioned above, It would take more time to test because we would want another round of testing once all PRs have been merged. The other more difficult concern here would be with how testable the individual PRs become depending on how they are devided.

Closing in preference of https://github.com/mattermost/mattermost-webapp/pull/7773#pullrequestreview-628985779


Union types incompatible when it shouldn't

I'm trying to type an i18n file but I got a really strange bug.
This is what my i18n file looks like:
type ScreenTranslationType = {
  title: string,
};

type AppTranslationType = {
  dependents: ScreenTranslationType,
};

export const pt: AppTranslationType = {
  dependents: {
    title: 'Meus dependentes',
  },
};

I have to convert these nested object keys into dependents.title, so, I created a simple helper:
type InputType = {
  [key: string]: string | InputType,
};

type OutputType = {
  [key: string]: string,
};

const handleI18nKeys = (input: InputType, prevKey?: string): OutputType => {
  return Object.keys(input).reduce((accumulator, currentKey) => {
    const newKey = prevKey ? `${prevKey}.${currentKey}` : currentKey;
    const currentValue = input[currentKey];

    if (typeof currentValue === 'string') {
      return {
        ...accumulator,
        [newKey]: currentValue,
      };
    }

    return {
      ...accumulator,
      ...handleI18nKeys(currentValue, newKey),
    };
  }, {});
};

But if I use handleI18nKeys(pt), the following errors are thrown:

Cannot call handleI18nKeys with pt bound to input because ScreenTranslationType [1] is incompatible with string [2] in property dependents.
Cannot call handleI18nKeys with pt bound to input because string [1] is incompatible with InputType [2] in property dependents.title.
annot call handleI18nKeys with pt bound to input because string [1] is incompatible with InputType [2] in property title of property dependents.

Any tips what I could be doing wrong?

https://flow.org/try/#0PTAEAEDMBsHsHcBQAXAngBwKagMoGMAnTTAOwBUCBDEgZ2kuQEtZyNsBeUAb0VFCeTRMALlA1kBRiQDmAGkQBfANyIUbUAEF06CtToNmrLKE48+AE0xYSlkshqj8RUrtr0mLMm3nLVeFuKg6MiiWjpUbgae6qa8oJbWtvaiZnz8jIIioADkALKYAK408VakSZg02fJ8Cj4qiCCgABaY0FgEasYAkiToBchexrF8ANoA1pioouKSMgC60xJS0qAAPqA9fQPeivVoxgDy-VuDHNxx45OLs9ILYksydX4ByM3U5kJdAIwAHCQA0pNipwABRSLaiTb9U6yIJEABugNQAH5rssAJSiI7IE4xAB85z4RGQBQIJFABwARgArTB4ZAAOgmqBoYN6-XRDKI5gKeEwIJBlDweAKAFsCu5YARYSKCEQ7Ej0SYCak+P5aK8SJh4EiTHDMIjJqBkaAAAYAEi46ARSIUDMtsvlyFtptAokdpGdkxUaVA6sCHrsADVKNACmdwf0RoGvag5vVfYxIKAQftMLBkzGQ2GOOxONkZstskrVWliaTyaXfQya0KReLJdK4r7RlqdZM7lnQ+Hqi3fL6FKpfeWyYSWzWGXWxRKGFLe9Wa013p9fgCgSCuznYW3FfPQP397CuAp0SpfA0wEVloglzYV38kazgqegA

fix

It works! Thanks @apsavin


Feature request: Dark mode for live chat replay (from archived videos)

For some reason, live chat replay for archived videos has white background, which kind of sucks, especially when streams which are currently live do have a dark background for their chat.
It would be nice if a dark mode option could be addded.

This is fixed in upcoming release of the extension. Pending chrome store approval
https://github.com/HolodexNet/Holodex-Plus/blob/dev/CHANGELOG.md


Restruct get started

Restructure get started page to 'why mxnet' and 'installation'.

@zackchase @sandeep-krishnamurthy

The why mxnet part doesn't look very convincing. Also its making installation harder to access. Let's remove it for now.

@piiswrong disagree with you. We need to have solid high-level introduction to what MXNet is and what purpose it serves. Right now MXNet assumes the readers already knows what a deep learning acceleration library is, which is unacceptable. I agree that Installation needs to be as easy to reach as possible. One solution for is we can flip the order of the documents.

@piiswrong We will have a new home page that will point to each document, however they both need to live within the Getting Started section. Let's change the order and approve this quickly so we can get to work on the improved home page.

@kevinthesun Could you resize the images so that they are appropriate for the document?

In general yes. But this particular section is more like "why deep learning" than "why mxnet". It's probably better to call it "What's MXNet"

@piiswrong No it's not. I imagine you're mistaken because you're only reading the first paragraph (perhaps because the picture is too big). It's a full-page document.

Also this image is too long. A thinner banner like image would be better as it won't hide the content below.

BTW we don't put images in main repo. They should go in web-data.

@piiswrong Getting started is a section, not a page. It is not in the same page. They share a nav item. Nav item should point to categories, not pages (it should be somewhat balanced tree).
Yes the images need to be sized, we've already discussed this above.
Regarding the image repo, this seems like a horrible design decision. We shouldn't have dependencies among (as many as 3!) repos to make a single change to the site. It's fine to play by that for now. In the long run I think it's unacceptable.

Putting binaries in code repo will lead to extremely large repo size and clone can take a very long time.

@piiswrong still that doesn't mean we need to dump all the static files in another repo does it? what are the alternatives? S3?

Hosting it on another server is more or less the same thing. Doing it ourselves means we need to handle DNS/CDN  and all that madness.
An alternative would be to put the docs folder itself in another folder.

@piiswrong let's work out the long-term solution offline. In the short run - @kevinthesun can you please:

resize the images
commit them to the crazy image repo
flip the order of the documents so the Installation page appears first

Thanks!

Long term solution - We will have quick installation commands (similar to pytorch) on home page and a link from there to the installation page. This will cover use-case brought up @piiswrong
Also, I think in getting started page readers will see easily see Installation tab on the left which should serve the purpose.


fix: add label calico_ipv4_pool

fix for issue https://github.com/vexxhost/magnum-cluster-api/issues/70

cluster creation fails with error:
Cluster.cluster.x-k8s.io "test-rcr-afterpatch-7fvw3ma6en" is invalid: metadata.labels: Invalid value: "<IP_ADDRESS>/16": a valid label must be an empty string or consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9])?') |

@robincron so I think we don't want to change the default since we want to use the same old value as Magnum.
As you see from here:
https://opendev.org/openstack/magnum/src/branch/master/doc/source/user/index.rst#labels
The value used for service_cluster_ip_range is <IP_ADDRESS>/16 -- so we should default to that

added https://github.com/vexxhost/magnum-cluster-api/pull/71/commits/84f1fb3d3870ed8be5f5f436dc01f7ce8ff69ad9 according to https://github.com/vexxhost/magnum-cluster-api/pull/71#discussion_r1108607612 and https://github.com/kubernetes-sigs/cluster-api/blob/main/config/crd/bases/cluster.x-k8s.io_clusters.yaml
built image locally and tested, seems to do the job:
k get cm kubeadm-config -oyaml -n kube-system
apiVersion: v1
data:
  ClusterConfiguration: |
    apiServer:
      extraArgs:
        authorization-mode: Node,RBAC
        cloud-provider: external
        profiling: "false"
      timeoutForControlPlane: 4m0s
    apiVersion: kubeadm.k8s.io/v1beta3
    certificatesDir: /etc/kubernetes/pki
    clusterName: test-rcr-10-06-ggzsfdcx4a
    controlPlaneEndpoint: <IP_ADDRESS>:6443
    controllerManager:
      extraArgs:
        cloud-provider: external
        profiling: "false"
    dns: {}
    etcd:
      local:
        dataDir: /var/lib/etcd
    imageRepository: container-infra-registry.fieldtest.c3.cgm.ag/magnum
    kind: ClusterConfiguration
    kubernetesVersion: v1.23.13
    networking:
      dnsDomain: cluster.local
      podSubnet: <IP_ADDRESS>/16
      serviceSubnet: <IP_ADDRESS>/16
    scheduler:
      extraArgs:
        profiling: "false"
kind: ConfigMap
metadata:
  creationTimestamp: "2023-02-17T09:10:51Z"
  name: kubeadm-config
  namespace: kube-system
  resourceVersion: "354"
  uid: 657d3e9d-6388-4b31-bd83-8f7b59ea79ee


MentionAll Feature

I found this code around here to mention all members in the group,
    case 'mentionall':
        if (!isGroupMsg) return client.reply(from, 'Only For Groups', id)
        if (!isGroupAdmins) return client.reply(from, 'Only For Admin's Group', id)
        const groupMem = await client.getGroupMembers(groupId)
        let hehe = '╔══ 〘 Mention All 〙 ══\n'
        for (let i = 0; i < groupMem.length; i++) {
            hehe += '╠➥'
            hehe += `<EMAIL_ADDRESS>'')}\n`
        }
        hehe += '╚═〘 - Helllo World - 〙'
        await client.sendTextWithMentions(from, hehe)
        break

How I can make it works on Iris bot ?

el bot iris ya lo tiene

el bot iris ya lo tiene

Really ? , Iris have a lot of features , its hard to find exact one xD
So , What is the command ?

I found this code around here to mention all members in the group,
    case 'mentionall':
        if (!isGroupMsg) return client.reply(from, 'Only For Groups', id)
        if (!isGroupAdmins) return client.reply(from, 'Only For Admin's Group', id)
        const groupMem = await client.getGroupMembers(groupId)
        let hehe = '╔══ 〘 Mention All 〙 ══\n'
        for (let i = 0; i < groupMem.length; i++) {
            hehe += '╠➥'
            hehe += `<EMAIL_ADDRESS>'')}\n`
        }
        hehe += '╚═〘 - Helllo World - 〙'
        await client.sendTextWithMentions(from, hehe)
        break

How I can make it works on Iris bot ?

Iris don't need because she just have a similar command.
/everyone.
Please, ever read the command list.


Support for Pothos::Packet in source/sink blocks

SDRSink checks for Pothos::Packet  based messages and treats them as stream + labels.
SDRSource uses the SOAPY_SDR_ONE_PACKET flag to produce the buffer as a packet message and not into the stream.

https://github.com/pothosware/pothos-sdr/commit/cebdab9b98452e1b5a7a26a410f3be8213706d52


How to style appindicator menus?

It appears that menus in appindicators (nm-applet, blueman) inherit some of styling from waybar ie font family and font color, while background and highlight colors come from gtk theme. Since I'm using bright font color in waybar and bright gtk theme it results in unreadable menus. Is there any way to style those menus independently of the rest of waybar?

In case anyone's interested following worked for me:
menu label {
    color: @theme_text_color;
    font-family: DejaVu Sans;
}
menu label:disabled {
    color: @insensitive_fg_color;
}

Thanks for the snippet!


Return zero when input version is same as target

Coverage increased (+0.3%) to 62.69% when pulling b3d9ef2f42f8d63195f0f91336c49cd9158dd655 on reasonerjt:cfg-upgrade-fix into debcf7858a0d7b0764118ffebf1223742bffb279 on vmware:master.


Publishing

I have some trouble publishing this

What Issues?

It's okay now
On Fri, 17 Sept 2021 at 00:38, E - Coders (Aasheesh Agarwal) <
@.***> wrote:

What Issues?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/S-Vishwaja/Study_Space/issues/1#issuecomment-921099632,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVQ6WUBU2SRIIK6G5KOPOE3UCITQJANCNFSM5EBNERGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Cool!!


✨ better support for monorepos

Describe the solution you'd like

Properly handle init to create the .ccoco folder and the ccoco.config.json at git worktree's root. (Since it uses git for run, might as well lock .ccoco and ccoco.config.json to the root so it's like the .git folder)
Support non-root config files (files not at the git worktree's root)
Flat branch configs folder (Replace filepaths with hash, some simple encoding or encryption for easier navigation) Possibly <branchname>-<base62encodedfilepath> and add a .json file that serves as a reference to what file belongs to what config. Extendable with GUI/TUI, maybe?

Some resource/s that can be useful:

Finding the git directory https://github.com/go-git/go-git/issues/74#issuecomment-1811067459


Can't ignore devices

Hello, I'm trying to hide multiple switches on my TX3 devices, namely 2 SW0 switches and another SW1 and SW2. Neither one of the four are getting hidden, they all still show up on HomeKit. Here's my config.
    {
        "name": "eWeLink",
        "countryCode": xx,
        "username": "xxx",
        "password": "xxx",
        "mode": "auto",
        "ignoredDevices": "1000f4087cSW0, 1000f4087cSW1, 1000f4087cSW3, 1000f406c0SW0",
        "platform": "eWeLink"
    },

Wrote on the wrong section, had to use ignore switches, my bad

Wrote on the wrong section, had to use ignore switches, my bad


Clarify financial incentives (participarly in the lobby) LAS

Clarify financial incentives (participarly in the lobby) LAS
Lobby timeout - check that success - successful rerouting code
Add default currency translation note
Change to 10 min


Improve postgresql plugin tests

Coverage increased (+12.4%) to 95.643% when pulling 7f23ba7987d2e57d0b59ae72689fa93d6c391c74 on postgresql-plugins-test into d1a6358bd42f63fcb381ab5a952ccc09d1b57783 on master.


npx quartz sync deletes content folder, error -4075

Describe the bug
when I run npx quartz sync, the content folder is deleted, with error code -4075 listed. (errno: -4075, code: EEXIST)
To Reproduce

run npx quartz sync
check for content folder, yet it is missing

Expected behavior
the content folder should not be deleted, and instead should be pushed* to github. (*unsure if pushed is the proper term here)
Screenshots and Source

My quartz repo is here: https://github.com/richardphankins/richardhankins/tree/v4
Desktop (please complete the following information):

Quartz Version: v4.2.3
node Version: v20.11.1
npm version: v10.2.4
OS: Windows 11 pro
Terminal: Powershell

Additional context
After running npx quartz sync a second time, i get error -4058 (see above screenshot). I am only able to recover my vault as it is backed up in google drive. I downloaded the content folder again, and reran npx quartz sync, only for the folder to be deleted a second time.

Solved:

restarted my computer (sigh)
Deleted .npmrc files where I could find them according to here: https://docs.npmjs.com/cli/v10/configuring-npm/npmrc

closing - hope this helps someone else

Thanks, deleting my .npmrc seemed to work for me too 👍


Enhanced build system for OSAL

This ticket is for the OSAL portion of the enhanced build system pushed out under the corresponding cFS ticket:
[https://babelfish.arc.nasa.gov/trac/cfs_cfe/ticket/1]
The CMake script for OSAL can also be used to generate a standalone OSAL library for use with projects other than CFS

Imported from trac issue 2.  Created by jphickey on 2014-12-18T21:30:51, last modified: 2015-11-20T16:22:16

Trac comment by glimes on 2015-01-29 15:10:03:
Click [changeset:77d68dc here] to see the changeset.

Trac comment by jphickey on 2014-12-18 21:42:44:
Pushed commit [changeset:29fc38262] as the first step which implements posix/pc-linux

Trac comment by mlogan on 2015-01-30 18:15:55:
I ACCEPT these changes  as well.  Although the newer build system included with cFE is also quite nice.
I generally view CMake as providing excellent capability for unified builds across multiple environments.
OSAL, by its nature, already provides the multiple environments ability, making Cmake somewhat redundant.   I don't intend to use MAC/OSX, nor MS-Windows to build my cFS for a vxWorks target.   But other projects might do this.
Changes are harmless and everyone can choose their own style of building.

Trac comment by glimes on 2015-01-29 16:24:19:
I have reviewed [changeset:77d68dc changeset 77d68dc] and recommend ACCEPT.
I would not describe myself as a CMake Expert or even as a CMake Fan, but in my experience: these changes, combined with the corresponding changes to the other projects, significantly simplify and improve the build process.
That said, I think this could be improved by adding text to README.md or as a separate document, giving the short series of shell commands required to use cmake on a common build system to build the library and run the OSAL unit tests.
( Translation: I'm a cmake newbie. How do I build the OSAL library, and run unit tests, using cmake? )

Trac comment by dheater on 2015-02-03 18:34:37:
I'm not smart enough about cmake to judge one way or another.

Trac comment by jphickey on 2015-02-05 13:48:34:
FYI - along with the testing I was doing for various permutations of trac #1, I found that the scripts here were not actually defining "HAVE_STDINT" as they were supposed to.  This turned out to be a simple variable name issue.  I fixed this and the new commit is [changeset:c1a2036].
This simply changes "OSAL_C_DEFINES" to "OSAL_C_FLAGS" (the former being a remnant of a previous incarnation of this changeset).

Trac comment by glimes on 2015-02-05 16:56:00:
I've updated the Change Set link in the wiki page I'm using
to track this set of things to review, [wiki:ReviewMerge20150202].
I have reviewed Joe's updated edits and continue to recommend ACCEPT.

Trac comment by glimes on 2015-02-12 14:58:10:
Accepted by #18 for integration candidate.

Trac comment by glimes on 2015-02-12 14:36:24:
Commit was amended to [changeset:c5f8cc8]

Trac comment by glimes on 2015-03-04 15:00:39:
Confirmed that the fix from [changeset:c5f8cc8] is present in the
current development branch of OSAL, [changeset:5aae372].
https://babelfish.arc.nasa.gov/bamboo/browse/CFS-CFSOSAL
confirms that the Bamboo build has successfully shifted from
the classical build tree to the CMake based build as of
build 55 in that plan.


Add new sample with the implementation of the batch operations

Description
This PR adds the new sample bot-batch-operations that includes the uses of the Teams batch APIs.
Specific Changes

Created the bot-batch-operations sample in csharp.
Added the logic to use the new features in TeamsBatchOperationsBot.
Added the README guide to use the new bot.

Testing
The following images show some sample bot responses.

Also, once there is no more feedback, clean up the commit history

/promoted 888


Multiple items to trigger DHS effect

Having to use a DHS to trigger the DHS effect may "waste" critical slots and tonnage when the build only needs to dissipate 31-60 heat/turn. With the option to set multiple items to trigger the DHS effect a 1 slot/0 ton item could be added to the list which could then be used to trigger the DHS effect in cases where 31-60 heat/turn dissipation, provided by the engine equipped DHS, is needed (saving two crit slots and one ton).
An example of a mech which requires only ten double heat sinks is the HGN-732b; With the proposed change (add ability to specify multiple trigger items, concurrently) the 732b acquired through the campaign could be made into a true 732b, at least as far as heat dissipation is concerned, with out using too many critical slots. Also, 733's could be made into 732b's in this same fashion.

So in this example you would have normal DHS in addition to a new item I'll call ⚡. I equip one ⚡ and 3 DHS, and I get 30 base+30 doubled+18 DHS dissipation?

The new item wouldn't be required if there were normal double heat sinks in the build, but in cases where only the ten engine DHS are required you would use the new item in order to gain the +30
Sent from my Verizon 4G LTE Droid
On Jun 23, 2018 22:39, janxious<EMAIL_ADDRESS>wrote:
So in this example you would have normal DHS in addition to a new item I'll call ⚡. I equip one ⚡ and 3 DHS, and I get 30 base+30 doubled+18 DHS dissipation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/janxious/InternalHeaters/issues/3#issuecomment-399731112, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amp4-aK0spFd90dv26AHKgunKbuhyR48ks5t_yX5gaJpZM4U1B7m.

Hi!  I love this mod!
I am not sure if this should be a new topic/issue so I will just put it here.
The "Battletech Enhanced" mod I installed adds a DHS called "Gear_HeatSink_Generic_Double_EX".
How would I get that added to your mod.json?
Specifically the line in settings that says:
"doubleHeatSinksDoubleEngineHeatDissipationComponentId": "Gear_HeatSink_Generic_Double"
How do I get both to be recognized as double heat sinks?
Thanks in advance!

Yeah that sounds like what I was hoping for (an array where things like heat exchangers and heat banks could be added so they don't mess up the double engine heat sinks).
This is a wonderful mod I really love it!
Looking forward to that array. I will keep my eyes on this topic for further news.
Thanks janxious!

@Ruffyen @TiberDasher v1.0.0 includes the functionality you requested. Cheers!

Thanks Janxious, you da man.
Sent from my Verizon 4G LTE Droid
On Jul 18, 2018 17:12, janxious<EMAIL_ADDRESS>wrote:
@Ruffyenhttps://github.com/Ruffyen @TiberDasherhttps://github.com/TiberDasher v1.0.0https://github.com/janxious/InternalHeaters/releases/tag/v1.0.0 includes the functionality you requested. Cheers!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/janxious/InternalHeaters/issues/3#issuecomment-406112735, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amp4-RiXWuyDAa4mJjMOmOPeK_l-G_o5ks5uH87hgaJpZM4U1B7m.


ci: use macos-11

Not sure if this breaks things for older macOS versions. In that case we can revert to macos-10.15 which will still be supported.
closes #793
Checklist

[x] No CHANGELOG update needed

[ ] No new tests needed

[ ] No documentation update needed

Sticking to macos-10.15 for build (assume that's more portable).


Support for AWS ElasticSearch

Hey guys,
So correct me if I'm wrong, but I don't think you guys have any support for AWS' branded ElasticSearch. Is there any plans to support this? Have there been any pull requests that address this? Where should I look if I wanted to add this feature myself?

Hey @TuxOtaku
I'm not aware of any differences with AWS' Elasticsearch that would mean Wagtail wouldn't work with it. Their FAQ says that they use version 1.5.2, which is supported by Wagtail.
Have you come across any issues that meant Wagtail wouldn't work with AWS Elasticsearch?

Yeah I get an error from Elasticsearch saying
{"Message":"User: anonymous is not authorized to perform: es:ESHttpGet on resource: boxingoctopus"}

Thanks!
Just Googled that error message and came across this: http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-managedomains.html#es-managedomains-signing-service-requests
Looks like AWS needs Elasticsearch requests to be signed. It seems like the best way to do this is documented in the elasticsearch-py package https://elasticsearch-py.readthedocs.io/en/master/#running-on-aws-with-iam
I think this could be done entirely in settings as extra arguments passed into the WAGTAILSEARCH_BACKENDS entry are passed straight to the Elasticsearch constructor. This might work:
# settings.py

from elasticsearch import Elasticsearch, RequestsHttpConnection
from requests_aws4auth import AWS4Auth

WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
        'URLS': ['YOURHOST.us-east-1.es.amazonaws.com:443'],
        'http_auth': AWS4Auth(YOUR_ACCESS_KEY, YOUR_SECRET_KEY, REGION, 'es'),
        'use_ssl': True,
        'verify_certs': True,
        'connection_class': RequestsHttpConnection,
    }
}

@kaedroho Sorry man...no joy:
  File "/opt/apps/boxingoctopus/boxingoctopus/settings/base.py", line 121, in <module>     'http_auth': AWS4Auth('xxxxx','xxxxxxx', 'us-west', 'es'), NameError: name 'AWS4Auth' is not defined

@kaedroho pretty close. Here's what I ended up using to get things moving:
from elasticsearch import Elasticsearch, RequestsHttpConnection
from requests_aws4auth import AWS4Auth

WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
        'URLS': ['https://YOURCLUSTER.REGION.es.amazonaws.com'],
        'INDEX': 'wagtail',
        'TIMEOUT': 5,
        'http_auth': AWS4Auth('ACCESS_KEY','SECRET_KEY', 'REGION', 'es'),
        'use_ssl': True,
        'verify_certs': True,
        'connection_class': RequestsHttpConnection,
    }
}

Thanks for helping to point me in the right direction!

Glad you got it working @TuxOtaku! Adding a note for us to add this to the docs.

I've tried @TuxOtaku 's configuration suggestion and it does not work at all. It returns user anonymous cant perform, 443, etc.
The syntax doesn't seem to match the current configuration syntax (perhaps it's changed?)
This is what I have and it's almost working but the RequestsHttpConnection class doesn't seem to know how to handle the AWS4Auth. I'm getting "AttributeError: 'AWS4Auth' object has no attribute 'encode'".
WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
        'INDEX': 'wagtail',
        'TIMEOUT': 5,
        'HOSTS': [{
          'host': 'myserver.region.es.amazonaws.com',
          'port': 443,
          'use_ssl': True,
          'verify_certs': True,
          'http_auth': AWS4Auth('access_key_id', 'secret_key', 'region', 'es'),
          'connection_class': RequestsHttpConnection,
        }],
    }
}

This change seems to be working:
WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
        'INDEX': 'wagtail',
        'TIMEOUT': 5,
        'HOSTS': [{
          'host': 'myserver.region.es.amazonaws.com',
          'port': 443,
          'use_ssl': True,
          'verify_certs': True,
          'http_auth': AWS4Auth('access_key_id', 'secret_key', 'region', 'es'),
        }],
        'connection_class': RequestsHttpConnection,
    }
}

@justinoue this works but only if there are no special characters (é, ü, etc) otherwise getting the following error:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 17345: ordinal not in range(128)

which what's interesting happens here:
    msg += message_body```

Try with any of the `Page.title` set to `'C\xc3\xa9line'` (Céline)

Have added the configuration to the docs in #3345; Unicode issue to be covered separately in #3331.

I'm seeing the same AttributeError: 'AWS4Auth' object has no attribute 'encode' error as mentioned above in https://github.com/wagtail/wagtail/issues/2776#issuecomment-246393591 by @justinoue.
I'm using Python 3.5, wagtail==1.11.1, elasticsearch==2.4.1 and requests-aws4auth==0.9 and the following config as per 1.11.1 docs (note elasticsearch2 rather than elasticsearch):
WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch2',
        'INDEX': 'staging',
        'TIMEOUT': 5,
        'HOSTS': [{
            'host': 'SOMEID.REGION.es.amazonaws.com',
            'port': 443,
            'use_ssl': True,
            'verify_certs': True,
            'http_auth': AWS4Auth('ACCESS_KEY', 'SECRET_KEY', 'REGION', 'es'),
        }],
        'connection_class': RequestsHttpConnection,
    }
}

I found that connection_class needed to be inside OPTIONS, so looks like the docs should be:
WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch2',
        'INDEX': 'staging',
        'TIMEOUT': 5,
        'HOSTS': [{
            'host': 'SOMEID.REGION.es.amazonaws.com',
            'port': 443,
            'use_ssl': True,
            'verify_certs': True,
            'http_auth': AWS4Auth('ACCESS_KEY', 'SECRET_KEY', 'REGION', 'es'),
        }],
        'OPTIONS': {
            'connection_class': RequestsHttpConnection,
        },
    }
}

Here's the full traceback of error with the first config:
traceback.txt

I've also just tested with elasticsearch and elasticsearch5 backends and their equivalent "elasticsearch" Python package versions. Same error, so I think this is just a mistake in the docs.


Add analog of TypeTuple that does not auto-expand

public (@mihails-strasuns) reported this on 2013-10-12T14:23:58Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=11235
CC List

andrej.mitrovich (@AndrejMitrovic)
code (@MartinNowak)

Description
This topic pops up frequently in D.learn when one needs to pass several distinct TypeTuple's as template arguments. Auto-expansion behavior of existing TypeTuple does not make it possible because two will be merged into single argument list.

andrej.mitrovich (@AndrejMitrovic) commented on 2013-10-12T14:34:46Z
Isn't this what http://dlang.org/phobos/std_typecons.html#.Tuple is for?

public (@mihails-strasuns) commented on 2013-10-12T14:26:27Z
https://github.com/D-Programming-Language/phobos/pull/1633

public (@mihails-strasuns) commented on 2013-10-12T14:50:38Z
No, those are quite different. `std.typecons.Tuple` defines runtime tuple (struct). It can be CTFE'ed of course, but it can't contain types (in TypeTuple sense) or aliases (completely), only values and value meta-data.

Proposed `Group` acts exactly like `TypeTuple` but do not auto-expand.

code (@MartinNowak) commented on 2013-10-12T15:45:59Z
I wonder whether it is worth adding this as an officially supported kind of tuple, or if we should encourage making creative use of the current syntax to keep the complexity low: (untested, just typed it up to illustrate the principle of nesting templates)

---
template isEqual(T...) {
  template to(U...) {
    static if (T.length == U.length) {
      static if (T.length == 0) {
        enum to = true;
      } else {
        enum to = isSame!(T[0], U[0]) && isEqual!(T[1 .. $]).to!(U[1 .. $])
      }
    } else {
      enum to = false;
    }
  }
}

static assert(isEqual!(1, 2, 3).to!(1, 2, 3));
---

public (@mihails-strasuns) commented on 2013-10-13T03:48:30Z
Main problem with nesting is that it does not allow algorithms with variadic amount of tuples.

public (@mihails-strasuns) commented on 2013-10-12T15:05:25Z
It is not a 3d kind of tuple, it is just another syntax for existing TypeTuple. Considering outcome of last tuple discussion threads any changes in that domain won't come any time soon and this small addition allows to implement certain algorithms right here and now.

I personally don't mind keeping it in "stdx" part of my projects but it is mentioned quite frequently as a necessary feature [citation needed].

Also DIP32 addresses different issues and won't change the fact that both expanding and non-expanding tuples are needed in different places.

public (@mihails-strasuns) commented on 2013-10-12T14:52:15Z
If TypleTuple comparison would have been legal, one could say that `Group!(int, double, foo).expand == TypeTuple!(int, double, foo)`

andrej.mitrovich (@AndrejMitrovic) commented on 2013-10-12T14:55:06Z
(In reply to comment #3)
> No, those are quite different. `std.typecons.Tuple` defines runtime tuple
> (struct). It can be CTFE'ed of course, but it can't contain types (in TypeTuple
> sense) or aliases (completely), only values and value meta-data.
>
> Proposed `Group` acts exactly like `TypeTuple` but do not auto-expand.

Right.. well with Group you end up having a third tuple kind. I think it's best that we wait for a language implementation of tuple syntax (see http://wiki.dlang.org/DIP32).


amp_veltrack_onccN issue

Hi sfizz,
I just tried the amp_veltrack_onccN implementation that was done in here ;
https://github.com/sfztools/sfizz/issues/483
with this simple test :
<control>
set_cc31=127

<region>
sample=crash.wav
key=60
loop_mode=one_shot
amp_veltrack_oncc31=-100
amp_veltrack_curvecc31=2

Moving the CC via MIDI controller knob does work.
The issue is, the specified CC number not displayed on sfizz control panel.
That's what needed for user to adjust the value via UI knob to match personal taste.
Same for fil_veltrack_onccN and pitch_veltrack_onccN, no CC on UI.

Thanks for the catch! #1066 should solve this if you can try.

A quick test of #1066 , it's good so far, thank you Paul!


[s] fix bugs in data package view page

The fixes this commit will address are

Remove hard coded file name. The file name was hard coded as co2-mm-mlo
Remove hard coded file type. The file type was hard coded as csv.

Resolves - #275

@subhankarb where are the tests ;-) - i agree we don't want too much fragility but i think we start wanting tests. I wonder if there is anything like the snapshot testing in react?