text:
chamber: 3.1.0 -> 3.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/segmentio/chamber/releases.
meta.description for chamber is: A tool for managing secrets by storing them in AWS SSM Parameter Store
meta.homepage for chamber is: https://github.com/segmentio/chamber
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.1 with grep in /nix/store/0gzc7k1f76rgaxxikpw133vm5vcqij9v-chamber-3.1.1
found 3.1.1 in filename of file in /nix/store/0gzc7k1f76rgaxxikpw133vm5vcqij9v-chamber-3.1.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

chamber

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0gzc7k1f76rgaxxikpw133vm5vcqij9v-chamber-3.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A chamber https://github.com/r-ryantm/nixpkgs/archive/d9b23fc6772117dfb477ec64e2684c2fbbde8a01.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d9b23fc6772117dfb477ec64e2684c2fbbde8a01#chamber

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0gzc7k1f76rgaxxikpw133vm5vcqij9v-chamber-3.1.1
ls -la /nix/store/0gzc7k1f76rgaxxikpw133vm5vcqij9v-chamber-3.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

chamber

Maintainer pings
cc @kalekseev for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge

authors: kalekseev r-ryantm


text:
tfproviderdocs: init at 0.12.1

Things done
tfproviderdocs is a tool to validate if the documentation of a terraform resource is up to date. This inits the package at version 0.12.1. You can check the project here: https://github.com/bflad/tfproviderdocs

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4979

source: gharchive/pull-request

authors: nixos-discourse tembleking

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
kubernetes: 1.9.1 -> 1.9.7

Motivation for this change
Update Kubernetes to the latest 1.9.x release while we wait for #38445.
Things done

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

[ ] NixOS
[x] 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 nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: kubernetes
Partial log (click to expand)
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/g80532irzxv9blr1fyw3ykp0bxlayh5h-kubernetes-1.9.7-man
checking for references to /build in /nix/store/g80532irzxv9blr1fyw3ykp0bxlayh5h-kubernetes-1.9.7-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/ph3nq71k77y4j2zi58mw2m7rb9b5fcry-kubernetes-1.9.7-pause
shrinking /nix/store/ph3nq71k77y4j2zi58mw2m7rb9b5fcry-kubernetes-1.9.7-pause/bin/pause
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ph3nq71k77y4j2zi58mw2m7rb9b5fcry-kubernetes-1.9.7-pause/bin
patching script interpreter paths in /nix/store/ph3nq71k77y4j2zi58mw2m7rb9b5fcry-kubernetes-1.9.7-pause
checking for references to /build in /nix/store/ph3nq71k77y4j2zi58mw2m7rb9b5fcry-kubernetes-1.9.7-pause...
/nix/store/sw0liaqgdaw6c89ws99pcq1ra5bs4pyp-kubernetes-1.9.7

Success on x86_64-darwin (full log)
Attempted: kubernetes
Partial log (click to expand)
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/xv43nfpa0hd5faxsg0z096bcs4adrpsl-kubernetes-1.9.7/bin
patching script interpreter paths in /nix/store/xv43nfpa0hd5faxsg0z096bcs4adrpsl-kubernetes-1.9.7
gzipping man pages under /nix/store/00sqd1iham82a1y8x0yk5fddww748g7c-kubernetes-1.9.7-man/share/man/
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/00sqd1iham82a1y8x0yk5fddww748g7c-kubernetes-1.9.7-man
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/k0v2qcymbh70dnfh9yhxwi8r39jhw9nq-kubernetes-1.9.7-pause/bin
patching script interpreter paths in /nix/store/k0v2qcymbh70dnfh9yhxwi8r39jhw9nq-kubernetes-1.9.7-pause
/nix/store/xv43nfpa0hd5faxsg0z096bcs4adrpsl-kubernetes-1.9.7

Success on aarch64-linux (full log)
Attempted: kubernetes
Partial log (click to expand)
strip is /nix/store/jk6j4lh9v5mvjdbdc35sj0zffhhf6s56-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/9fdasgpanb6xm83d58vff1370lvrl8j0-kubernetes-1.9.7-man
checking for references to /build in /nix/store/9fdasgpanb6xm83d58vff1370lvrl8j0-kubernetes-1.9.7-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/gxrzczrj5k46l8w5bp8kzppkryymfsxn-kubernetes-1.9.7-pause
shrinking /nix/store/gxrzczrj5k46l8w5bp8kzppkryymfsxn-kubernetes-1.9.7-pause/bin/pause
strip is /nix/store/jk6j4lh9v5mvjdbdc35sj0zffhhf6s56-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/gxrzczrj5k46l8w5bp8kzppkryymfsxn-kubernetes-1.9.7-pause/bin
patching script interpreter paths in /nix/store/gxrzczrj5k46l8w5bp8kzppkryymfsxn-kubernetes-1.9.7-pause
checking for references to /build in /nix/store/gxrzczrj5k46l8w5bp8kzppkryymfsxn-kubernetes-1.9.7-pause...
/nix/store/3fd95vx60x56x2grwhh0cy99ky7qk1pf-kubernetes-1.9.7

authors: GrahamcOfBorg yurrriq


text:
silver-searcher: 2.1.0 -> 2.2.0

Things done

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

[x] 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 nox --run "nox-review wip"
[x] 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)
[x] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: silver-searcher
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0
shrinking /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0/bin/ag
gzipping man pages under /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0/share/man/
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0/bin
patching script interpreter paths in /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0
checking for references to /build in /nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0...
/nix/store/v2fvkf5d7zzj06c97acnwldg4k6kgvgp-silver-searcher-2.2.0

Success on x86_64-linux (full log)
Attempted: silver-searcher
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0
shrinking /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0/bin/ag
gzipping man pages under /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0/share/man/
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0/bin
patching script interpreter paths in /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0
checking for references to /build in /nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0...
/nix/store/62bgqnzcn9hzli16smr40drinixah8i6-silver-searcher-2.2.0


text:
networkmanager: sed from gnused, not coreutils! fix bad path

Motivation for this change
Eep!
Not sure how likely this is to be causing folks problems
but definitely should be fixed!
Don't we check udev rules for valid paths?
Maybe we can add a check for this sort of thing,
although TBH really hope there are no other instances.. !
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Don't we check udev rules for valid paths?
Maybe we can add a check for this sort of thing,

This is particularly difficult one since the invalid path is inside a string.
I actually prefer passing the full path to substituteAll, that could be more conducive to linters.

Considering the change was made in December, this means this issue is in 19.03. Unless this fix would further break something, this will need to be backported I think. Right?

Yes, this seems good to backport-- depending on build impact, maybe to the appropriate -staging?

authors: dtzWill jtojnar samueldr


text:
epiphany: 3.32.2 -> 3.32.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/epiphany/versions.
meta.description for epiphany is: '"WebKit based web browser for GNOME"'.
meta.homepage for epiphany is: '"https://wiki.gnome.org/Apps/Epiphany"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 3.32.3 with grep in /nix/store/7716dhi07m8zkfd8jgb6hpw8kyk0hpqn-epiphany-3.32.3
directory tree listing: https://gist.github.com/08a5f6a06f93a6b5ddcb462df8b22307
du listing: https://gist.github.com/738fc2b43aa98525135b66d675630d99

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
epiphany
gnome3.epiphany
pantheon.elementary-gsettings-schemas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7716dhi07m8zkfd8jgb6hpw8kyk0hpqn-epiphany-3.32.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A epiphany https://github.com/r-ryantm/nixpkgs/archive/fc78e57467601928b907c67e45888ead4d1a933a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7716dhi07m8zkfd8jgb6hpw8kyk0hpqn-epiphany-3.32.3
ls -la /nix/store/7716dhi07m8zkfd8jgb6hpw8kyk0hpqn-epiphany-3.32.3/bin

cc @lethalman @jtojnar @hedning @worldofpeace for testing.

Seems to work.

authors: jtojnar r-ryantm


text:
dovecot: 2.3.6 -> 2.3.7

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dovecot/versions.
meta.description for dovecot is: '"Open source IMAP and POP3 email server written with security primarily in mind"'.
meta.homepage for dovecot is: '"https://dovecot.org/"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.3.7 with grep in /nix/store/8vni5ylzg535dyaa2f6i213220nwsjla-dovecot-2.3.7
directory tree listing: https://gist.github.com/c5de0cf89bd2e7a32fd964142dd20e94
du listing: https://gist.github.com/5cff5fb1b01c5a4e83747042b8472c01

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
dovecot
dovecot_pigeonhole

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8vni5ylzg535dyaa2f6i213220nwsjla-dovecot-2.3.7 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A dovecot https://github.com/r-ryantm/nixpkgs/archive/5eb574010e8984c9c766ee845d6ea86704e1c55f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8vni5ylzg535dyaa2f6i213220nwsjla-dovecot-2.3.7
ls -la /nix/store/8vni5ylzg535dyaa2f6i213220nwsjla-dovecot-2.3.7/bin

cc @peti @rickynils @fpletz for testing.

Review per https://nixos.org/nixpkgs/manual/#sec-reviewing-contributions and top comment in https://raw.githubusercontent.com/NixOS/nixpkgs/master/.github/PULL_REQUEST_TEMPLATE.md .
Reviewed points

[x] package name fits guidelines
[x] package version fits guidelines
[x] package build on x86_64-linux
[ ] executables tested on x86_64-linux: only dovecot
[x] all depending packages build: exim (with enableAuthDovecot set)

Comments

The test in nixos/tests/dovecot.nix succeeds.
Tested with a small custom configuration and Thunderbird: Mails are delivered flawlessly via POP3, stored and delivered flawlessly via IMAP.
All tests described here were performed after rebasing the pull request onto current nixos-unstable channel.  To test from an unprivileged account, the module_dir patch was skipped.


text:
i3lock-fancy: Bugfix, make scrot overwrite file

Motivation for this change
After commit  https://github.com/resurrecting-open-source-projects/scrot/commit/489e3229045962be2f63535ecd70cd15e6e2414d scrot will no longer overwrite files unless the -o option is given. This commit makes the i3lock-fancy use scrot -z -o instead of just scrot -z.
Things done

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

[x] 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 nix-review --run "nix-review wip"
[x] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @garbas , @vcunat , @NeQuissimus , @rail , @jokogr

just noticed a mistake in the commit message, i won't rebase & force push in order to preserve the reviewer state but whoever merges this probably wants to fix:

... This commit makes the i3lock-fancy use scrot -z -o instead of just scrot -o.

to

... This commit makes the i3lock-fancy use scrot -z -o instead of just scrot -z.

@NeQuissimus you are welcome. Yes this bug is somewhat annoying since screen locking is now broken on my machine :)

@NeQuissimus what else can I do so that this PR gets merged?
Not having a lock screen is quite annoying :)

My bad, I had wanted to try it out first.

yay, thank you for merging this. @NeQuissimus

authors: Enteee NeQuissimus


text:
nixos/nixos-enter: Create /tmp

/tmp is normally created by the systemd-tmpfiles-setup systemd service
at startup.
Fixes #39140
Motivation for this change
Working towards being able to run 'nixos-enter -- nix-build ...`.  This is the first thing that breaks.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

(I plan to add this test for nixos-enter -- nixos-build ... when I get it working.)

[ ] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @edolstra whether systemd-tmpfiles is fine to run in nixos-enter

:+1: I need this too, otherwise I cannot nixos-rebuild switch in the nixos-enter to fix a server's GRUB.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/313

I'm merging this now as it looks correct, works for me +3 others, and from https://github.com/NixOS/nixpkgs/issues/39140#issuecomment-589905207 this is the same

like switch-to-configuration.pl

in https://github.com/NixOS/nixpkgs/blob/ff97a25fc6da512edf8fb32cf27f001e0d7382c0/nixos/modules/system/activation/switch-to-configuration.pl#L419.

authors: chkno danbst nh2 nixos-discourse


text:
glib.setupHook: run glibPreFixupPhase before gappsWrapperArgsHook

Motivation for this change
Since we split wrapGAppsHook and move its variable initialization to preFixupPhases in #81475, it was getting run before glibPreFixupPhase which sets GSETTINGS_SCHEMAS_PATH variable gappsWrapperArgsHook depends on. Let's introduce this ugly hack to ensure glibPreFixupPhase will run before gappsWrapperArgsHook.
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
[x] Fits CONTRIBUTING.md.

backported to 20.03 in e544e03110063eee62ca1f1b407c4f7e0739c432

authors: jtojnar worldofpeace


text:
chromium: 83.0.4103.116 -> 84.0.4147.89

https://chromereleases.googleblog.com/2020/07/stable-channel-update-for-desktop.html
This update includes 38 security fixes.
CVEs:
CVE-2020-6510 CVE-2020-6511 CVE-2020-6512 CVE-2020-6513 CVE-2020-6514
CVE-2020-6515 CVE-2020-6516 CVE-2020-6517 CVE-2020-6518 CVE-2020-6519
CVE-2020-6520 CVE-2020-6521 CVE-2020-6522 CVE-2020-6523 CVE-2020-6524
CVE-2020-6525 CVE-2020-6526 CVE-2020-6527 CVE-2020-6528 CVE-2020-6529
CVE-2020-6530 CVE-2020-6531 CVE-2020-6533 CVE-2020-6534 CVE-2020-6535
CVE-2020-6536

Testing status

platform
attribute
status
tester

x86_64
chromium
:heavy_check_mark:
@danielfullmer

x86_64
nixosTests.chromium
:heavy_check_mark:
@danielfullmer

x86_64
google-chrome
:heavy_check_mark:
@primeos

aarch64
chromium
:heavy_check_mark:
@thefloweringash

Let's hope the M84 build didn't break again since my last test and the browser still works at runtime.
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.

Sorry, I opened the PR a bit to early (I always ensure that at least everything before the build phase works). Unfortunately enable-vdpau-support-for-nvidia.patch originally contained an old workaround that broke in the meantime. I updated the patch and everything up to the configuration phase works now.

Built chromium and nix-build nixos/tests/chromium.nix -A stable successfully but did not test interactively. LGTM.

Awesome :) I'm relieved to hear that it does still work as the M84 build already broke twice and was a bit annoying to fix IIRC.
Thanks for testing! :heart:

authors: primeos thefloweringash


text:
python3Packages.*: bump packages I maintain

Motivation for this change
bump some packages I maintain
Things done

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

[x] 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/)
[x] 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.

failures are broken on master as well:
https://github.com/NixOS/nixpkgs/pull/99102
3 packages marked as broken and skipped:
bareos pepper sabnzbd

55 packages built:
ceph ceph-client errbot fava flexget libceph mnemosyne nix-prefetch-github pypi2nix python37Packages.WSME python37Packages.backports_functools_lru_cache python37Packages.cheroot python37Packages.cherrypy python37Packages.elementpath python37Packages.fints python37Packages.heudiconv python37Packages.irc python37Packages.jaraco_collections python37Packages.jaraco_functools python37Packages.jaraco_logging python37Packages.jaraco_text python37Packages.nipype python37Packages.nix-prefetch-github python37Packages.portend python37Packages.pyalgotrade python37Packages.pybids python37Packages.pytest-black python37Packages.sepaxml python37Packages.tempora python37Packages.ws4py python37Packages.xmlschema python37Packages.zerobin python38Packages.WSME python38Packages.backports_functools_lru_cache python38Packages.cheroot python38Packages.cherrypy python38Packages.elementpath python38Packages.fints python38Packages.irc python38Packages.jaraco_collections python38Packages.jaraco_functools python38Packages.jaraco_logging python38Packages.jaraco_text python38Packages.nipype python38Packages.portend python38Packages.pyalgotrade python38Packages.pybids python38Packages.pytest-black python38Packages.sepaxml python38Packages.tempora python38Packages.ws4py python38Packages.xmlschema python38Packages.zerobin samba4Full tribler


text:
Transparency report 2024-06-30

For context, the project's state is in limbo, with the foundation understaffed and the assembly still working on a new governance structure. Things will eventually stabilize, and hopefully, new governance structures will clarify these interactions. Until then, I am doing my best to keep things going in my own way by unblocking people when they need things in the GitHub org.

On Thursday morning, a community member contacted me in DM and asked if we should consider removing commit access from people who left the project. Given that I had helped Samueldr move their nixos-mobile repo to https://github.com/mobile-nixos/mobile-nixos the same week and knew about Linus' departure, I didn't think more of it. I assumed that if you leave, you don't care about the commit access.
Then I removed the following members from the nixpkgs committers team:

amaxine
delroth
lheckemann
marsam
samueldr

Later that day, Samueldr posted a toot (since removed) that raised some concerns. I contacted him in private and clarified the situation with him. I learned about the existence of RFC55 and RFC71, which then led me to re-add the members to the https://github.com/orgs/NixOS/teams/retired-nixpkgs-contributors team (except delroth because they blocked the org, or me, not sure).
In retrospect, all of this lacked transparency and caused some confusion, so I am publishing this report. This wasn't my intention, and I hope this clears things out.
In the future, I will only act on tickets posted to this repo in full transparency until the new governance structure takes place.

Clarification: for maintainer removal, the best is to report to https://github.com/NixOS/nixpkgs/issues/88867

source: gharchive/issue

repo: NixOS/org


text:
GPU type and OOM

Hi, Thank you for your great work!
In this code, batch_size is set to 4. But I encountered Out of Memory error. I couldn't find the hardware configuration for the experiment in the paper either. How many GPUs do you use to train for batch_size = 4? (I noticed that there is distributed training such as SLURM in the code) What type of GPU and how much memory they have?
Thank you.

I meet the same question, by changing the batch size to 2 on each GPU, it costs about 15.5G memory. I think a 32G GPU (v100) or 48G GPU (RTX 8000) is needed when using bs=4 or higher.

authors: Hanqer Jiankai-Sun


text:
local vs global optimal path

Hi,
Thank you for the nice package!
I have some problems related to the pathfind function. Does it first find the global optimal path, then cut high dissimilarity out?

In my case, I changed my gene list of interested GO term slightly: 150 gene in the beginning, then add 60 more genes in. The heatmap of dissimilarity looks almost the same, but the path changed a lot!

result of 150 genes:

result of 210 genes:

the path it identified seems not the optimal ones.
the gray path is the one identified by pathfind.
but by eyes, the red line make more biological sense, also seems better if consider it locally.

Do you have any suggestions to get more stable and optimal result? Many thanks!

Hi there!
Thanks for showing an interest.
There is two ways that TrAGEDy cuts out high dissimilarity. The first is before the global optimal path is calculated (see the top half of supplementary figure 2 of the TrAGEDy paper) and the second (see the bottom half of supplementary figure 2 of the TrAGEDy paper) does it after the global path is identified.
In terms of adding the 60 genes, you're right the paths have changed, and this might be an area where TrAGEDy might not be suited. TrAGEDy assumes that their is a continious alignment path between your two datasets, but you can see your dissimilarity matrix is quite 'spiky' (i.e. areas of high and low dissimilarity occuring right next to each other).
These 'spiky' regions can sometimes be caused by your pseudotime values not being accurate. What packages and code are you using to generate them
Another thing i've noticed is that your plot dissimilarity scores don't start from 0. In the latest version of TrAGEDy on github, the plot dissimilarity score legend should always start from 0, otherwise very dissimilar regions can have a blue colour (e.g. the last plot you've posted) and make it seem like there is an alignment where there is none.
Hope this is helpful!
-Ross

Thanks for the quick reply!
Could you give an example to show how to cut out high dissimilarity before the global optimal path? In the tutorial, it showed how to cut out after global optimal path if I understand correct?
In my dataset, our hypothesis is the start points of the two lineage is quite different, but after the treatment their end points should converged. So that it might not be always continuous through the trajectory.  Do you think TrAGEDy suited in this case?
I used Slingshot to generate the pseudotime value. I subset the cells on the interested branch for following analysis. I checked the dynamic of some known markers and the temporally changes are consistent with literature. I also have a question related to that. The maximum value of the two trajectory are quite different, one is around 3 the other is around 6. In this case, do you think I should normalise the maximum to 1 to make them more comparable?
There is a batch effect between my two datasets. I don't know which normalised value as input matrix is better: logNormalize, or scaleData, or scaleData regress out cell cycle. Have you ever tested these normalised value to see which has a better performance?
I modify the code a bit, change the score legend from 0 to minimum value.
Do you have any suggestions for my second question? The optimal path by eyes (the red line) is quite different from the one picked by dtw (the grey line).
Best regards,
Menghan

Hi Menghan,
It would be difficult to remove high dissimiilarity regions before global optimal path as we use the global path alignment as a model to set thresholds for removing high dissimilarity regions.
In the scenario described, TrAGEDy could work in your scenario but you would have to change the cut_type parameter in the pathfind from "minimum" to "none". I say this because if we have the following scenario:

Because we have no alignment at the beginning, it tries to find the optimal start point and instead picks a region which (probably due to noise) has slightly lower dissimilarity. This means it cuts some optimal alignment parts from your final alignment, because it ocurred before the 'optimal' point of initial alignment. By setting cut_type to none, it takes the very start and very end as the points of initial and end alignment, and we'd capture the section properly.

In future versions of TrAGEDy we will add a parameter which will ask whether the users want to cut: the start, the end, both or none of the dissimilarity matrix, which will deal with this problem a lot more elegantly.
In terms of differences in pseudotime values, none of the tests we've done have been on datasets with the same pseudotime scales, however we've not dealt with anything as extreme as pseudotime scales that are half of the other dataset in the comparison. I've just ran the alignment code for our start_shared simulated alignment (Fig 2A in the paper) where I made the pseudotime of the WT dataset half that of the KO (WT max pseudotime = 10.53, KO max pseudotime = 21.07) and it the alignments looked very similar:

In terms of batch effects all our results are done on the normalized data. Because we use Spearman's correlation for alignment, it doesn't matter whether the expression values are scaled or not. The T cell dataset in the TrAGEDy paper seemed to have a pretty substantial cell cycle batch effect. We controlled for this in terms of pseudotime by regressing out cell cycle genes when we scaled the data and we used the normalised data for dissimilarity estimation.
In terms of the grey vs your red line path I'd say there should be no alignment between the two datasets (at least on the genes you've chosen). If you kept the scale as it is originally, it would probably be all red; the lowest dissimilarity you have is 0.8 which is a spearmans correlation of 0.2, which is quite low.
I will say that TrAGEDy is not the ultimate authority on alignments, we could get it wrong. We've tested it on quite a few datasets and it's been able to return (what we think) are biological accurate alignments but we could always be wrong with other ones. Does the data integrate together with harmony or Seurat?
Also how are you choosing the genes that define the alignment?
Best wishes,
Ross

Hi Ross,
Thank you very much for the nice illustration!
I'm using Seurat integrateData to minimise batch effect. But it a bit overfitting here, as the dissimilarity score is quite low. So I just used LogNormalize data from UMI for the analysis.
The gene list I used is from a specific GO term.
Will definitely try out the parameters you suggested. : )
Best,
Menghan

We've only tested TrAGEDy on capturing a whole biological process (i.e. T brucei differentiation and T cell development) we've not tested whether it will work on just one GO term so that might be the issue.
If you have time, I would try on some marker genes of your two dataset clusters and then see if you can identify any of the genes in the GO term as being differentially expressed across the alignment.
Let me know how changing the parameters goes and good luck.
Best wishes,
Ross


text:
🛑 AnonymousOverflow overflow.adminforge.de is down

In 79ac3c8, AnonymousOverflow overflow.adminforge.de (https://overflow.adminforge.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnonymousOverflow overflow.adminforge.de is back up in 8c908e3.

repo: NoPlagiarism/services-personal-upptime


text:
🛑 libreddit libreddit.privacydev.net is down

In 6ad7554, libreddit libreddit.privacydev.net (https://libreddit.privacydev.net) was down:

HTTP code: 502
Response time: 749 ms

Resolved: libreddit libreddit.privacydev.net is back up in daf8269.


text:
🛑 ProxiTok tok.habedieeh.re is down

In a6fb5c3, ProxiTok tok.habedieeh.re (https://tok.habedieeh.re) was down:

HTTP code: 502
Response time: 396 ms

Resolved: ProxiTok tok.habedieeh.re is back up in d9600df after 16 days, 11 hours, 53 minutes.


text:
add link to medium post

it's a nice writeup, adding a link in your readme will allow more people to learn from you
https://medium.com/myheritage-engineering/how-controllable-react-components-maximize-reusability-86e3d233fa8e

I put the wrong link in "what is controllable?"
Thank you very much! 😀

authors: NoamELB ssured

repo: NoamELB/make-controllable


text:
Adding mention or emoji inline (:name) switches text direction

To reproduce, switch to RTL, and add an emoji by typing : and selecting one from the dialog selection box. The direction will switch to LTR and the line will be aligned to the left.

Turns out this is an old issue I reported earlier with textcomplete and mention.
The following pull fixed markdown, but not mention:
https://github.com/julianlam/nodebb-plugin-markdown/pull/107
We should reopen the issue: https://github.com/NodeBB/NodeBB/issues/7457
To recap, mention returns a string @ + userslug, and that confuses the editor. It should return html with direction / alignment attributes.

Update:
I removed HTML support from textcomplete.contenteditable that I had earlier to solve RTL issues with Redactor. Now mention and inline emoji work well.
As for textcomplete.contenteditable:
The command that was making quill reset the direction is "range.deleteContents();". That command stems from a PR for providing HTML support. See here: (https://github.com/yuku/textcomplete.contenteditable/pull/3)
Since HTML insertion is not supported by composer, and since we are dropping Redactor, going back to text is the best solution.
I did however keep the changes from the mentioned PR that allow textcomplete to work with Safari.
@julianlam I do believe Safari related support should be integrated to the core, for the benefit of all other users.
Feel free to close this issue once read.

repo: NodeBB/nodebb-plugin-composer-quill


text:
if statement fix

Pull Request check-list
Please make sure to review and check all of these items:

[x] Does npm test pass with this change (including linting)?
[X] Is the new or changed code fully tested?
[X] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Sometimes command_obj is null and causes node to spit-up an Error with  'TypeError: Cannot read property 'callback' of undefined'. This change fixes that. This problem might be windows specific.

@gstringfellow what version do you use and what commands? There should always be a command_obj, otherwise there's a error somewhere else.
Do you have a reproducible test case? Otherwise please also activate the debug_mode to make it easier to spot the error.

This is a blocker for me to release v.2.6. Could you provide some more details for me? This would be very helpful!

I am running windows 8 with redis 2.8.24 running on my local machine; connecting to an external redis instance (on aws) runs fine. I ran node_redis with debug_mode but the output did'nt reveal anything to me. The Throw happens during initialization of node_redis before I run any commands with it. What follows is the output and the stacktrace.
`Stream connected 127.0.0.1:6379 id 0
Checking server ready state...
Send 127.0.0.1:6379 id 0: *1
$4
info
Stream connected 127.0.0.1:6379 id 1
Checking server ready state...
Send 127.0.0.1:6379 id 1: *1
$4
info
Stream connected 127.0.0.1:6379 id 2
Checking server ready state...
Send 127.0.0.1:6379 id 2: *1
$4
info
Net read 127.0.0.1:6379 id 0
Redis server ready.
on_ready called 127.0.0.1:6379 id 0
Net read 127.0.0.1:6379 id 1
Redis server ready.
on_ready called 127.0.0.1:6379 id 1
Net read 127.0.0.1:6379 id 2
Redis server ready.
on_ready called 127.0.0.1:6379 id 2
Sending offline command: monitor
Send 127.0.0.1:6379 id 2: *1
$7
monitor
Net read 127.0.0.1:6379 id 2
redis:main [8488] RedisClient entering monitoring mode. +20ms
c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\index.js:616
if ( typeof command_obj.callback === 'function') {
^
TypeError: Cannot read property 'callback' of undefined
at normal_reply (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\index.js:616:28)
at RedisClient.return_reply (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\index.js:719:9)
at JavascriptReplyParser.self.reply_parser.returnReply (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\lib\individualCommands.js:63:22)
at JavascriptReplyParser.run (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\node_modules\redis-parser\lib\javascript.js:137:18)
at JavascriptReplyParser.execute (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\node_modules\redis-parser\lib\javascript.js:112:10)
at Socket. (c:\Users\gstringfellow\Code\SVO\poc-server\node_modules\redis\index.js:240:27)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Socket.Readable.push (_stream_readable.js:110:10)
at TCP.onread (net.js:523:20)
`

The output looks like it has something to do with the monitor command. You open three clients and fire monitor with one of them. As soon as it's connected and the monitor command is called, it throws... Would you be so kind and show the code that reproduces the error? And are you able to trigger the error in a local test?
As far as I see it this might be a race condition. To verify that you could add this.monitoring = true; in the individual commands line 63. That might solve the issue.

redisClient.monitor(function (err, res) { debug("RedisClient entering monitoring mode."); });
The above is the offending set of lines. I added the statement and removed the null check,but no change it still threw.
There are at least 2 connections to redis one in the main process and then one for each processor (we use clustering with socket.io-redis).

Would you be so kind and try to find a way to reduce your code to the absolute minimal to reproducible this as a standalone program? Or would there be any other way to have a closer look at what is happening?
The current information is not enough for me to see the error.

@gstringfellow would you be so kind and check if #1074 fixes your issue?

authors: BridgeAR gstringfellow


text:
use in Java - error: reference to getMetadata is ambiguous

public static void main(String[] args) {
        String rpcUrl = "wss://127.0.0.1:9944";
        var provider = new SubstrateProvider(rpcUrl);
        var meta = provider.getMetadata().blockingGet();

}

build and get error
 % gradle build

> Task :compileJava FAILED
bcd-java/src/main/java/UsingSubstrateClientKotlin.java:10: error: reference to getMetadata is ambiguous
        var meta = provider.getMetadata().blockingGet();
                           ^
  both method getMetadata() in SubstrateProvider and method getMetadata() in SubstrateProvider match
bcd-java/src/main/java/UsingSubstrateClientKotlin.java:10: error: cannot find symbol
        var meta = provider.getMetadata().blockingGet();
                                         ^
  symbol:   method blockingGet()
  location: class RuntimeMetadata
2 errors

FAILURE: Build failed with an exception.

For sure this should be "call Kotlin from Java" issue, however I have no clue how to solve

I guess related docs are https://kotlinlang.org/spec/overload-resolution.html
But I have not found any generation recommendation for dealing with in Java.

repo: NodleCode/substrate-client-kotlin


text:
🛑 KReady is down

In cead00c, KReady (https://prod.kready.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KReady is back up in 5bc7f69.

repo: NoincCTE/CAS-StatusPage


text:
added work in tech

added work in Tech to the orgs variable

nice.
So we still need Work In Tech's linktree?

repo: Nola-Devs/Nola-Dev-Site


text:
Switch gitlab imports to github imports in nolus-core Github

Switch gitlab imports to github imports in nolus-core Github

[x] Upgrade the project to the latest stable go version 1.19

Done

authors: Lockwarr kostovster

repo: Nolus-Protocol/nolus-core


text:
Export data after Filtering it.

Is there any way to export the data after filtering the data in the client side.

Current export example does export the filtered out data only.
If you want to export it without hitting the back end, you can only export current page.

Ohh  Yes. I just figured it out. So to download all data after column filtering I need to remove the RowsPerPage. Am I right?

For all the data you need remove paging when constructing the grid for the export.

Ok. Thanks a lot. By the way a very nice product you have build.

license: mit

license_source: bigquery


text:
Prevent renaming the class of ui.hotbar

Also: foundry.js should not be a part of the repository. I'm not even sure if you're allowed to publish it publicly like this.

Also: change the latest automated release to only trigger on commits on master.
Then you can safely add a alpha/beta tag to a different branch and release that version separately.

Thanks, all changes look necessary

authors: Norc janssen-io

repo: Norc/foundry-custom-hotbar


text:
FEATURE REQUEST: Invoke from CloudWatch Rule

Is your feature request related to a problem? Please describe.
I would like to run load tests against several different services at scheduled times. Specifically, I would like to setup a CloudWatch Rule to invoke the load generator lambda with a particular config (script.yml) at a particular time.
I don't see how to do this currently because the only invocation method I see is to run slsart invoke --stage <whatever> from a command line. It would be good if the documentation articulated how to invoke the load generator lambda with a raw payload.
Describe the solution you'd like
It would be good if the documentation articulated how to invoke the load generator lambda with a raw payload. I assume that slsart invoke is just an alias for this very thing.
Describe alternatives you've considered
I imported your source code into a CloudFormation setting with some luck. However, things broke down when trying to use the artillery-plugin-cloudwatch, so I am back at hacking on the original Serverless implementation.
Additional context
From the README, it seems like this performance-testing stack is intended to be ephemeral; that is, built during the deploy, run test, and spin down.
My team intends to keep it up semi-permanently in order to run cron-job performance tests. If that sounds like a terrible idea, I'd be curious to know.

I think that I've answered my own question. Once you run slsart configure and pop the serverless.yml, you can manually add any number of extra schedule events, e.g.
...
events:
      - schedule:
          name: "${self:service}-${opt:stage, self:provider.stage}-monitoring"
          description: The scheduled event for running the function in monitoring mode
          rate: rate(1 minute)
          enabled: false
          input:
            ">>": script.yml
            mode: monitoring
      - schedule:
          name: "my-service-monitoring" # CHANGE THIS TO WHATEVER
          description: The scheduled event for running the function in monitoring mode
          rate: rate(1 hour) # CHOOSE YOUR RATE
          enabled: true
          input:
            ">>": scripts/my-service-script.yml # CHANGE THIS TO WHATEVER
            mode: monitoring

repo: Nordstrom/serverless-artillery


text:
Add to Hyprland website

The spinning logo would be a cool addition to the main website.
The news section still needs some artwork for the header and this would also fit contextually.
Do you like the idea?

sure, sounds good

Added. See it here https://hyprland.org/news/

authors: NotAShelf Visual-Dawg

repo: NotAShelf/hyprascii


text:
delete this

in favor of #23

Thanks for staying active on this important issue

thank you for your great work, matmen

Bumping this, please merge

@NotSoSuper any updates on this? this has been open for over a year and you haven't even replied. sad!

fix

@NotSoSuper the original issue has been open for 2 years, 5 months and 7 days, pls fix.

Hey, i just saw this on my front page again, @NotSoSuper could you please fix this issue?

can't believe it's almost been 3 years

is repo owner even alive?

ah right, i think he did the not so super. too bad.

authors: Fogapod Kefta empt1xo matmen ozzt y21

repo: NotSoSuper/NotSoBot


text:
In-line/refreshable templates (data-view v1)

someone could embed template code like this:
```Template
some template code here
```
and then when NP sees that code block, it executes it (and refreshes it on demand). Whatever the return value is gets rendered by NotePlan in-line

I was thinking that it would trigger a re-draw on:

note load
code block edit
refresh button/menu press (initially could be on note ... overflow menu, but at some point a circular refresh arrow on the block itself would be nice)

Note: @mikeerickson said: Another FYI, any time you execute a template to render, any JavaScript code you have between tags will be executed.
You will have access to any:

NotePlan API command
Any methods defined in globals.js
Any methods you have supplied to in your own plugins located in methods object or variables located in data object

So, basically using any template you can do d LOT LOT LOT LOT more than existing templates

If it's gonna display the word "Template" maybe that's not the right word.
Maybe ```Data

Instead I suggest this is a further use case for #187 (the first trigger).

I am gonna let @mikeerickson respond to your comments, because he knows what Templates does and doesn't do. But in case I wasn't clear, I am talking about using np.Templates here inside of a code block. I suggested using ```Template or ```data to specifically delineate from standard JS code blocks, which by definition are just formatted display, not executed.

authors: dwertheimer jgclark

repo: NotePlan/plugins


text:
Notificare failed to launch for Moshi initialization error on Android Gradle Plugin 8.0.2 on minifyEnabled

With minifyEnabled set to true and com.android.tools.build:gradle version 8.0.2, Notificare launch fails because of a initialization error for the Internal Moshi instance; this is the stacktrace:
Failed to launch Notificare.
     re.notifica.internal.network.NetworkException$ParsingException: Unable to parse JSON.
     	at re.notifica.internal.network.request.NotificareRequest$responseDecodable$2.invokeSuspend(NotificareRequest.kt:98)
     	at re.notifica.internal.network.request.NotificareRequest$responseDecodable$2.invoke(NotificareRequest.kt:0)
     	at re.notifica.internal.network.request.NotificareRequest$responseDecodable$2.invoke(NotificareRequest.kt:0)
     	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:89)
     	at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:169)
     	at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:1)
     	at re.notifica.internal.network.request.NotificareRequest.responseDecodable(NotificareRequest.kt:90)
     	at re.notifica.internal.network.request.NotificareRequest$responseDecodable$1.invokeSuspend(NotificareRequest.kt:0)
     	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
     	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
     	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
     	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
     	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
     Caused by: java.lang.IllegalArgumentException: Unexpected signature for public final org.json.JSONObject re.notifica.internal.moshi.JSONObjectAdapter.fromJson(com.squareup.moshi.JsonReader,com.squareup.moshi.JsonAdapter).
     @FromJson method signatures may have one of the following structures:
         <any access modifier> R fromJson(JsonReader jsonReader) throws <any>;
         <any access modifier> R fromJson(JsonReader jsonReader, JsonAdapter<any> delegate, <any more delegates>) throws <any>;
         <any access modifier> R fromJson(T value) throws <any>;

     	at com.squareup.moshi.AdapterMethodsFactory.fromAdapter(AdapterMethodsFactory.java:301)
     	at com.squareup.moshi.AdapterMethodsFactory.get(AdapterMethodsFactory.java:135)
     	at com.squareup.moshi.Moshi$Builder.add(Moshi.java:224)
     	at re.notifica.internal.MoshiKt$moshi$2.invoke(Moshi.kt:22)
     	at re.notifica.internal.MoshiKt$moshi$2.invoke(Moshi.kt:15)
     	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
     	at re.notifica.internal.MoshiKt.getMoshi(Moshi.kt:15)
     	at re.notifica.internal.network.request.NotificareRequest$responseDecodable$2.invokeSuspend(NotificareRequest.kt:92)
     	... 15 more

A workaround is downgrading AGP to version 7.4.2, changing gradle version doesn't seem to affect the issue.
I created a minimal GitHub project that reproduces the issue.

Hi @OvoMaS,
There is a known issue with Moshi where it fails to keep the JsonAdapter classes when the application is built with R8 enabled. This is now enabled by default with Gradle 8.0.
You can refer to this Moshi issue for a suggested workaround.
In short, you can temporarily add the following Proguard rule to your app.
-keep,allowobfuscation,allowshrinking class com.squareup.moshi.JsonAdapter

Hi @hpinhal,
Thanks for the quick reply and for the Moshi issue reference/fix!
May I suggest updating the troubleshoot section of the integration guide with this information? It would have saved me a few hours of debugging.

authors: OvoMaS hpinhal

repo: Notificare/notificare-sdk-android


text:
Unable to load codelists

Good morning,
I am trying to load codelists in ontobrowser. it runs on port 8080 for me. I could not find an example of how to achieve this. Currently, I am trying this:
$ curl -s -S -H "Content-Type: application/obo;charset=utf-8" -X PUT --data-binary "@send_codelist_terms.txt" -u SYSTEM "http://localhost:8080/ontobrowser/ontologies/sendcodelist"
here my codelist is called send_codelist_terms.txt. Is it a correct way of achieving this?
Thank you,
Nikhita Jatain
Erasmus MC

Hi @nikhitajatain - @carloravagli appears to be the only contributor to this repo (and I don't know anything about this project). I'm tagging him here to see if he can help, but it doesn't seem like he's been much active on GitHub recently.

Hi @nikhitajatain,
Currently OntoBrowser does not support loading flat code lists via the REST service i.e. only ontologies in OBO format can be loaded via REST.
In the past we imported flat code lists (such as CDISC's controlled terminology) using standard ETL tools to populate the required tables i.e. ONTOLOGY, TERM, TERM_XREF and TERM_SYNONYM (optional) e.g. for Oracle we used SQL Loader. If you are using MySQL then you can use the LOAD DATA INFILE functionality.
I would encourage you to add support to be able to load flat code lists via the REST endpoint.
Cheers,
Carlo

Many thanks Carlo,
This idea worked. However, after uploading codelist as ontology, I had to manually set the is_codelist flag as TRUE in the database. is there a way to set it to true via the REST service?
Best,
Nikhita

Many Thanks Carlo,
Thank you very much for your suggestion. I am able to upload the obo file format of codelist into ontobrowser.
Best,
Nikhita

authors: carloravagli nikhitajatain zbarry

repo: Novartis/ontobrowser


text:
Update sbt to 1.7.1

Updates org.scala-sbt:sbt from 1.5.8 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #117.

repo: NthPortal/life-vest


text:
Move some fetch code so we can call fetch logic independetly of compo…

Move some fetch code so we can call fetch logic independetly of componentDidMount. Useful for filtering.
Naming could be improved but I think this is a small, easy win.

duplicate

repo: NuCivic/react-dashboard


text:
Support request emails accidentally remove underscores from package links

We got an email today which I imagine should have linked to
https://www.nuget.org/packages/JQueryFileUpload_Demo_with_Backload/
but it actually linked to
http://www.nuget.org/packages/JQueryFileUploadDemowithBackload/
and
http://www.nuget.org/packages/JQueryFileUploadDemowith_Backload/1.9.2.4
which didn't work

This still happens.

repo: NuGet/NuGetGallery


text:
Move to a new version of anglicangeek.markdownmailer

Gallery references the old unlisted version from 2011. There is a newer version (which is not unlisted) from 2013. We should use that one: https://www.nuget.org/packages/MarkdownMailer/

@joelverhagen @skofman1 It appears this newer version has been removed. Shall we close this issue?

Yes, I think we'd only update if we had a compelling reason. I don't recall a compelling reason since this issue was filed.

authors: drewgillies joelverhagen skofman1


text:
Windows Server hangs after opening http://serveraddress/nuget/Packages

I have very strange problem with Nuget.Server (3.1.2.0) which is deployed on Windows Server 2016. Every time when someone is opening address http://myserveraddress/nuget/Packages (in the web browser or Visual Studio Packages Manager) server hangs.  Resource Monitor on the serwer doesn't show any unusual vales but it's hard to connect with Remove Desktop. After connecting (tens of seconds) it's hard to do anything. Problem disappears after restarting W3SVC service. I've 66 packages (18 MB, ~1300 file and ~530 folders).

Random thoughts: such hangs may happen when there are issues with the disk. Can you run error checking on all disks on your server to make sure there are no errors? It's also might be worth checking the system event log for other issues that might affect the performance.

@agr event log was clean and disks are OK. Problem has disappeared after moving nuget server to the default IIS 'wwwroot' folder.

Could you please provide some details about your initial setup, so we could try to reproduce the behavior?

Nuget.Server and Packages folders were on one of our server (Windows Server 2016) drives in the same parent folder (eg. d:\WebApplications). IUSR, IIS_IUSRS and DefaultAppPool users had full access to the folders. There were no problems with the same configuration on my local machine (Windows 10) and our old server (Windows Server 2008).

authors: PiterGoCompany agr


text:
improve error message when pushing a snupkg without a parent nupkg

Today we say Response status code does not indicate success: 404 (Not Found). That is not very helpful.
C:\Users\karann\source\repos\LicenseTest\PackageA\bin\Debug>nuget push BasicMathNew2.0.0.1.snupkg -Source https://api.nuget.org/v3/index.json -apikey ~~~redacted~~~
Pushing BasicMathNew2.0.0.1.snupkg to 'https://www.nuget.org/api/v2/symbolpackage'...
  PUT https://www.nuget.org/api/v2/symbolpackage/
  NotFound https://www.nuget.org/api/v2/symbolpackage/ 1076ms
Response status code does not indicate success: 404 (Not Found).

I think server returns an appropriate message here. It is likely the nuget client version isn't showing the message correctly.

I opened a client issue : https://github.com/NuGet/Home/issues/7498. Close this issue.

authors: cristinamanum karann-msft shishirx34


text:
[NuGet.org Bug]: The generated link for owner request is broken.

Impact
It's more difficult to complete my work
Describe the bug
The link in the email doesn't point to www.nuget.org.
Repro Steps
Add a package owner and check the generated link in the email.
Expected Behavior
The link should be workable. What about other scenarios?
Screenshots
No response
Additional Context and logs
No response

We may need an additional config used on the admin panel (in addition to the existing SiteUrl) used for email links.

The generated link used for API key revocation is also broken.

authors: joelverhagen zhhyu


text:
use separate variables for package source and package path

this is a quick fix for #650
Now the PackageSource in the PackageViewModel is always the package path. Which means that if a package is opened from a feed, the feed name is no longer shown in the package view but instead the temp path to the package.
If we want to preserve the previous behavior we also have to use separate variables for package source and package path in the PackageViewModel which would require more changes.

I think we should use separate variables for the package source and path in the view model too so we hide the underlying details from the UI.

authors: campersau onovotny


text:
Show 2 FileUploads

With this one it show this

Try Updating The package.

authors: Nuhel davidtim

repo: Nuhel/filament-cropper


text:
Windows CI

Has there been an attempt to add Windows CI?
Travis CI for Windows is quite good, and there is a reasonable support base able to help at https://travis-ci.community/c/environments/windows
I was able to make it almost like AppVeyor for the coala-bears CI; see e.g. Windows icon on https://travis-ci.org/coala/coala-bears/builds/581997859 for a 30min job setting up lots of chocolatey packages.
Azure also has Linux, macOS and Windows , so switching to that is also an option.

ping @kayhayen , do you have any preference for how I proceed with this?

Sorry for the late reply, @jayvdb things are busy for me privately. However, I have lots of response to this, and didn't take the time yet.
I had started to use AppVeyor for Nuitka, but noticed early on, they were not giving too many cycles to build jobs. However, their offering is of course attractive. What I preferred Travis for is deep integration with Github that was fully automatic. I never got that to work with AppVeyor, which is why I recently disabled that one job I had, where it produces the MSI files. I am not even sure, how useful those even are, and I never managed to automate the download of the MSI artifacts from the webhooks.
Basically all lack of time. We have a Linux only public CI of our own, nightshift.nuitka.net, that has fallen into disrepair, since Buildbot failed to work with Apache and only Nginx, but that works less well with the SSL certificate renewal. I will turn to that this weekend I hope. There we can burn as many cycles as we want. But it's ugly since it's not automatically adding branches, i.e. PRs do not get built. But for many, that is also far from needed to run the whole suite of compilations.
If you want to take this on, very well. I also mean to invite you to the Nuitka organisation, if you are interested, which I hope. Esp. if you are interested in that 3.8 work with test suites, and other stuff, you are more than welcome.
Again sorry for the late reply.
Yours,
Kay

Ok, I'll make a start on Travis CI, and let you know how I go.
I have had fairly deep integration with AppVeyor, including artifacts.
AppVeyor provides more variation of Windows environments - different images, but I havent used the non-default ones much.
We can have both operational in order to spread the load, if needed.
Yes I am interested in joining the org.

Feel free to have your own branch in the central repository. That way I will see it easier. I added you to the pushers as part of the invite.
I indeed had very good experience with AppVeyor, but I didn't use the .yml file in their instance, that's actually pretty annoying to try out things that way, isn't it. But it also is the only way to share stuff.
They have VMs with all Python's installed, etc. and it seems even WSL was added recently. I think AppVeyour still has access to Nuitka, if you want to go there as well. I think starting with Travis is a good idea. I can lookup what is still on AppVeyor, I might have deleted it 2 months ago though, when it failed to build MSIs and I noticed it still existed and only wasted energy.

I recommend using Github actions for this (which should be available for everyone sometime in November, or you can sign up to get early access)

Deep integration with GitHub, obviously
Has Windows, Mac and Linux VMs

We've created a build for our project that runs on all OSes and it's been fantastic. Here's a slimmed down example that would belong in .github/workflows/test_nuitka.yml
name: Nuitka tests

on:
  pull_request: {}
  push:
    branches: master
    tags: '*'

jobs:
  linux:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1

    - name: Use Python 3.7.4
      uses: actions/setup-python@v1
      with:
        python-version: 3.7.4

    - name: Install dependencies
      run: |
        pip install nuitka

    - name: Build with nuitka
      run: python -m nuitka

    - name: Run tests
      run: ...

  mac:
    runs-on: macOS-latest
    steps:
    - uses: actions/checkout@v1

    - name: Install Python 3.7.4 using Conda
      run: |
        sudo chown -R $USER $CONDA
        $CONDA/bin/conda install python=3.7.4

    - name: Install dependencies
      run: |
        pip install nuitka

    - name: Build with nuitka
      run: python -m nuitka

    - name: Run tests
      run: ...

  windows:
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@v1

    - name: Use Python 3.7.4
      uses: actions/setup-python@v1
      with:
        python-version: 3.7.4

    - name: Install MinGW using Conda
      shell: bash
      run: $CONDA/Scripts/conda install m2w64-gcc libpython

    - name: Install dependencies with pipenv
      shell: bash
      run: |
        pip install nuitka

    - name: Build with nuitka
      shell: bash
      run: CC=$CONDA/Library/mingw-w64/bin/gcc.exe pipenv run build

    - name: Run tests
      shell: bash
      run: ...

@jayvdb @brendanator any news on this, I really would want to use Github actions, is there anything I need to do to enable it?

@kayhayen All you need to do to enable it is create a .yml file in the .github/workflows/ directory. The template that I've included above runs 3 jobs on each os and installs the dependencies. You just need to fill in the ...s with whatever you want to run.
The property on which is at the top means that the jobs will be run on each PR, commit to master and tag.
Here's the main docs: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions

Since macOS is currently broken, I will give it a shot myself now.
All public CI is limited in what it can do for us. Nuitka wants too much CPU to be tested, that is for sure, but the basics, they should be covered reliably. These public CIs are going to better integrated on any given day.

I managed to get things up and running for only Python 3.7, and on factory branch right now. I need to figure out the matrix next up.
The use of Anaconda on macOS doesn't fit into setup-python, so it's more manual. Also there was a problem executing the installed scons from Nuitka, which I think i will react to by making the inline copy of scons the default. It has optimizations for faster startup and often is newer than installed stuff anyway, and means better control over what is actually going on. I think the PYTHONHOME, PYTHONPATH is wrong for scons, but that worry should go away. Nuitka deletes those variables when it executes scons, hoping for them to not be necessary, as they often proved to be counter productive. But there is no right or wrong here.
For Windows, I had to whitelist a few paths from PATH, which precede system DLLs, but that wasn't so big.
For Linux, all went relatively smooth.
So this is poised to remove the need for Travis almost entirely. It seems more flexible, and I might figure out how to actually use secrets. With that happening, I might be able to move release jobs from my private CI to this public one, which will be great. Maybe Travis was/is also capable of that, maybe I won't do it immediately, but e.g. putting the MSI build and deployment or OBS upload on Github actions seems like a relief, and it allows for others to enhance on it.
That way, my private CI can focus on CPU heavy stuff. I doubt we can run massive test suites on Github actions, but this looks very promising as it stands. The final switch is probably something I will do, once I got working cron jobs on Nuitka master too.
But first the matrix, and maybe in a way that it uses variables so the macOS which needs to give the concrete binary version to use, python3.7 rather than just python will work fine. Before adding 3.8, I need to fixup a missing 3.8 feature still.
I hope to resolve this issue over the week.

Ah, for Windows, the --assume-yes-for-downloads needed to be added to the main test runner, so it can forward it, to download depends.exe.
Which reminds me that we ought to make sure we got good caching going on for this one as well, because it would be a shame to not preserve the ccache or the nuitka cache files for CPython outputs here too.

So, the inline scons is now the default, and on Windows, we use short filenames for robustness. This should avoid regressions with unicode paths like we had issues with in the past.

Windows and macOS CI are operational. I think I need to do something to make it work on normal PRs too. But I will close this is it's solved.

authors: brendanator jayvdb kayhayen

repo: Nuitka/Nuitka


text:
Added option to use PGO on Nuitka-generated code.

Thank your for contributing to Nuitka!
!! Please check that you select the develop branch (details see below link) !!
Before submitting a PR, please review the guidelines:
Contributing Guidelines
What does this PR do?
Performs PGO on the Nuitka-generated code.
Why was it initiated? Any relevant Issues?
Greatly improved performance.
PR Checklist

[x] Correct base branch selected? Should be develop branch.
[ ] All tests still pass. Check the developer manual about Running the Tests.
There are Github Actions tests that cover the most important
things however, and you are welcome to rely on those, but they might not
cover enough.
[ ] Ideally new features or fixed regressions ought to be covered via new tests.
[ ] Ideally new or changed features have documentation updates.

Things that are not yet solved. I think this is only for non-Windows, and it won't work well for standalone mode at all, as I think data files won't be there yet, or post processing of the file done, and I don't really like that it's not possible to re-use existing profiling information. I am going to add stuff to disallow using it for modes that won't work and/or hide it from the options help temporarily.

I am also making --lto an option that defaults to auto, and is implied with --pgo when given as auto, this way I am more sure it's used properly. Also allows to disable the LTO for MSVC, which sort of was missing. That was a TODO in my mind for a long time now. It will also enable Nuitka to hint at using --lto=yes or --lto=no dependent on your setup needs.
Still need to figure out, how to detect if LTO is going to work in advance, with different gcc versions bytecode versions, not sure how to detect them from files. But much like with --static-libpython it might be good enough to inform the user is missing out on something.


text:
Unable to sign in

No matter which Google Account I use it gives Auth Error and says to sign in with another account.

same issue for me !!

The DB was down for a few hours this morning but things should be working now! Can you all check now and let me know if it's working please? @codemobii @paradisebuster44 @saurishmonga

The DB was down for a few hours this morning but things should be working now! Can you all check now and let me know if it's working please? @codemobii @paradisebuster44 @saurishmonga

Still seems down. I was able to sign in but image generation doesn't happen and a page refresh signs out again

@paradisebuster44 should be good now! Mind trying one more time?

@paradisebuster44 should be good now! Mind trying one more time?

thanks for a quick turnaround! Login seems to be working smoothly now but it says I don't have generations anymore. Will refresh in 6 hours. I guess it still recorded the past failed attempts.

hi
cant login , geting an error message
There is a problem with the server configuration.
Check the server logs for more information.

Hey there.. just tried logging into RoomGPT and not sure why now whenever I log out of Gmail, I can't seem to press anything on the screen. Has anyone encountered similar problem?

use www.roomgpt.io/  website , Oauth only works on registered domain

Great.. tqvm for the reply.. will try it out..
On Sun, Mar 19, 2023, 12:39 AM Harikrushna @.***> wrote:

use www.roomgpt.io/ website , Oauth only works on registered domain
—
Reply to this email directly, view it on GitHub
https://github.com/Nutlope/roomGPT/issues/30#issuecomment-1474903998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6OUCRNM56ND2JLZHVPL2I3W4XQN3ANCNFSM6AAAAAAVWPJX6Q
.
You are receiving this because you commented.Message ID:
@.***>

Same problem here

Hi
When I want to download the rendered image, the download button does not work and the image is not downloaded.
Recently, it does not display the rendering image either

repo: Nutlope/roomGPT


text:
Status sort on Submission table does not sort as expected

Log in as nih-user, go to Submissions page, click the Status header, the column does not sort as expected.

This could be anywhere from 5 minutes to 6 hours, depending on the issue. Will provide a better estimate after some investigation.

This isn't so much a bug as it is an improper implementation - ember-model-tables handles sorting by alphabetically sorting the propertyName value of each column, in this case aggregatedDepositStatus. In order to get the sorting to work properly, all of the status computation would have to take place not in the cell but in a computed value on the model, so it would be accessible as the column/cell's propertyName.

This was fixed when status display was updated

authors: cameronblandford karenhanson

repo: OA-PASS/pass-ember


text:
Add action buttons where appropriate on the /submissions/ table

Now that there are a variety of Submission statuses that may require the user to act upon a Submission (review submission, edit submission, attention required, etc.), when looking at the /submissions/ list it can be ambiguous which submissions you need to do something with and which you are waiting for someone else to act on.  The Action column in the /submissions/ list should be customized to display buttons for any submission that can be acted on by the user.

closed by #763


text:
[WIP] Consolidate submission details

Original:

First draft


text:
cannot describe a typical XML-based REST API in OpenAPI/Swagger

I cannot describe a XML request/response that has different elements typed by the same complex type. That should be possible, as it is common practice in XML modeling (typically using XSD schemas).
Simple example: a customer has a billing address (element name: billing-address) and a residential address (residential-address).
Reasons:

in order to reuse a complex type, in OpenAPI I must create a definition object, and refer to this definition in the $ref field in the body of request/response
in order to declare the name, namespace, prefix and other XML-specific metadata in OpenAPI, I must declare a XMLobject (via a "xml" field)
however, as per the spec, whenever you use $ref, other values are ignored, IOW, I cannot define the name/namespace/prefix of the XML element

See swagger-api/swagger-ui#3469 and #556.

I'm not sure this limitation is specific to XML based payloads.  Whenever you reference a "reusable" resource you cannot modify or add to that reusable component.  That is a limitation of the $ref construct that we borrowed from JSON Schema.  The JSON Schema folks are working on alternative mechanisms but currently there is no ability to do this.
You are limited to defining the xml field in the reused definition.  Is there a reason this does not work for you?

@darrelmiller This is the key requirement: "different elements typed by the same complex type" - they would all be deemed to have the same element name. The linked swagger-ui issue includes an example.

@abstratt Ah, I understand.  Yes that is a limitation, however  I would argue that doing that in XML isn't a particularly wise thing. Elements usually have a different structure. If you just want a descriptive difference between elements then create a name attribute on the element.  I realize that is probably not possible to change the XML in your case.
From a longer term perspective, I would like to see the addition of XSD support to OpenAPI rather than trying to fix the Xml annotations.

Thanks for the idea @darrelmiller, but I hope we agree that is a workaround, and with some serious limitations. A customer may have two addresses (not three or more), a residential one, and a billing one. The latter is optional. That is trivial to model with XSD. It should be possible to model with Swagger as well.  But it is not, actually not even if you  use JSON (because you cannot reuse complex types, but only entire property definitions, including things like descriptions, 'requiredness', etc - please correct me if that statement is incorrect, as I see it as the root cause for the present issue, and a major design issue with OpenAPI/Swagger).

@abstratt JSON Schema doesn't make a distinction between complex types and schemas.  Unfortunately you are trying to do something that JSON Schema was designed to do.  Currently OpenAPI is somewhat constrained by the limitations of JSON Schema when it comes to description of payloads.  Hopefully that won't always be the case.

@darrelmiller Thanks. Here's hoping that changes soon. That is a serious drawback in JSON Schema, one which Swagger/OpenAPI should not be inheriting, as it limits the description of JSON-based APIs, and prevents description of many XML-based APIs.

I think that draft-07 (which should be published by November 20th) and draft-08 will help with this sort of thing.  And the relevant ideas in draft-07 don't technically require an implementation change.
draft-07 classifies keywords as data model, assertions, or annotations, and is more formal about how annotations are applied to instance data.  xml is an annotation keyword: it adds information to the instance that is used by other tools.  Note that this is not a change from draft-05, it's just giving names to things that were not called out clearly before.
Based on how we define annotations and the concept of applicability in draft-07, I would expect this to work:
propA:
  allOf:
    - $ref: '#/definitions/MyType2'
    - xml:
        name: prop-a

I assume that it does not in current OpenAPI implementations?
As for draft-08, it will focus on re-usability, including several issues around how things with allOf and/or $ref function.  There is a draft-08 milestone if you want to keep an eye on that.

This may seem off the wall, but JSON schema definition seems to be in the same state that XML was about a millenia ago at version 0.5 or some such.  My 2 cents worth is that OpenApi should not tie itself to an emergent standard that could well take many years to become operable.  By comparison, XML, XSLT, XSD family of technologies could well have resolved most of the issues being found with OpenAPI 3 et al had they been adopted as the underlaying schema definition.  Not suggesting it changes, just saying it's all been done before.

Wow, a good old XML vs JSON discussion. Just wanted to bring back https://blog.jclark.com/2010/11/xml-vs-web_24.html in the discussion. Coming from XML (maybe even from SGML) this post has changed my relationship with JSON almost 9 years ago. BTW, James is back after (also) almost 9 years of Blog silence to talk about Ballerina ;-)
Disclaimer: I still enjoy writing parsers for X12 and EDIFACT ;-)

@chippyash The alternate schema work that is ongoing will ensure that no-one is tied to any particular schema language.  Despite it's "draft" status, JSON Schema is far from emergent.  I would argue it has more real world traction than XML Schema ever did.
XML Schema has a fundamentally different world view than JSON Schema.  The XML Schema "closed world" principle does not fit nearly as well with the loosely coupled web.
I am and always will be a fan of XML and XSLT.  Less so of XML Schema, but XML tech just isn't the best tool for the job when describing payloads for HTTP APIs.

This issue is not really a contest between JSON or XML, but about a relevant gap in OpenAPI spec in which it does not allow a fairly common modeling pattern (multiple child objects of the same base type with different roles/under different names) for XML-based APIs, ironically due to a limitation in JSON Schema.
Hopefully OpenAPI can loosen this restriction soon, as many well designed XML based APIs out there cannot be modeled with OpenAPI, as it stands now.

@chippyash @patricekrakow @abstratt @darrelmiller Please note that we finally, after over a year of work, released the 2019-09 draft of JSON Schema yesterday.
In IETF terms, this consists of several draft-handrews-*-02 documents (there is a giant table of all of the versions and identifiers on json-schema.org now, explaining IETF vs meta-schema and why we're using dates now).
Of particular interest may be the hypothetical code generation example in Appendix E of the Core spec.  This is intended to illustrate some techniques related to how JSON Schema 2019-09 could be extended for code generation.
@darrelmiller and the rest of the OpenAPI TSC have been working with @philsturgeon and myself on the JSON Schema side to ensure that JSON Schema is a better platform for the needs of OAS.  Between proposals for improving compatibility of the Schema Object in OAS 3.1, and the alternate-schema work that @darrelmiller mentioned, I am optimistic about future functionality and alignment.

Oops. @patricekrakow I have to grin. I read James' blog about Ballerina too.  Kinda how I ended up here. Was very interested in it's OpenApi (although limited) capability, started to play, delved deeper into the standard and started to find some fundamental issues particularly in the nesting and multiple child arenas that @abstratt refers to.  I'm going to use OpenApi, but instruct my devs to use copious examples to get around the limitation in the definition itself. Just means we'll have to hand code those bits in our implementations. Anyone remember the processors you could inject in an XSLT definition to get round local difficulties?  ;-) Still going to use XML for my DI container definitions though! And @handrews, thanks for all the good work you and your colleagues are doing to even try and establish a standard for API definitions.

@chippyash 🙏
For XML definitely the alternate-schema work will be more helpful for you!  While the flexibility we've put into JSON Schema 2019-09 should eventually make it more possible to describe other things, having the ability to use XML Schema for XML payloads is something that I very much support.

@handrews I wasn't really saying I want to have the ability to specify XML schema, although having to support clients that use XML and JSON (and a few other strange things that I can't remember the names of) would most certainly be useful. It was more about applying the pain that was gone through in XMLs birth to the construction of a JSON schema definition. I've shied away from using JSON as a reliable data transport mechanism simply because I couldn't validate it reliably and have built whole libraries around doing just that. I welcome a standardised mechanism to do that validation whole heartedly. Sure XSDs can be a PITA to design and implement, but at least there is only one way to do it, (barring a few processor 'flavours'!).  I guess my observation was kind of asking does the JSON schema group have old buggers with that pain involved in bringing a new standard into the world? I don't know but I guess I kinda hope so.

I think it sounds like you have feedback on how JSON Schema works, or used to work, or need support on a certain use case, or something. This doesn't seem like a "XML in OpenAPI" conversation anymore though, so lets close this one down?
If JSON Schema cannot do what you want, and the XML Object is not good enough, then XML Schema in Alternative Schema is going to solve your problems when it gets done. So its a solved problem however you spin it.

Can we please have a link to the document describing how to model XML APIs in OpenAPI using the a "Alternative Schema" approach (which I confess I know nothing about) which avoids the limitation reported here?
If that is doable with a new approach (and the new approach is already available even if in beta form etc), yup, closing this issue makes sense.

Alternative Schema is a draft feature still being worked on, but it will allow XSD as @chippyash is requesting. People who want alternative Schema can join in various conversations about alternative Schema. #1993
The main “doing this in JSON Schema + xml keyword” issue is solved by OpenAPI raising support for JSON Schema Draft 2019-09 in #1977
So anyone interested in those two topics can track progress there. This issue is now superfluous, confusingly named, and sinking in slightly in accurate person opinions about JSON and JSON Schema in general, which will probably not lead anywhere constructive.

@philsturgeon i didn't start this thread. Far be it from me to close it down. It does however leave some unanswered questions, however uncomfortable they are. By all means close it down, but how about raising issue tickets to resolve the the open questions (many here in this thread alone) that have been identified.  This is OpenAPI. The JSON schema issue aside, OpenAPI is not dealing with some of the real world use cases identified in this thread alone.

The TSC have done work to bring the Alternative Schema proposal to the community as a draft feature.  This will allow XML based APIs to be described accurately.  The next step in the draft feature process is for people building tools to implement the draft feature and provide feedback on its feasibility.  If we get multiple implementations then we will incorporate the feature into the specification.
The OpenAPI TSC has done what it can at this point to support this feature.  If you need proper support for XML, then please encourage the people building the tools you use to implement the alternative schema draft feature and provide us with real world implementation experience.
There doesn't need to be any further discussion on this thread.

authors: abstratt chippyash darrelmiller handrews patricekrakow philsturgeon

repo: OAI/OpenAPI-Specification


text:
[FEATURE REQUEST] Create a function, allowing direct terminal reload (a.k.a ally reload)

Is your feature request related to a problem? Please describe.
Somewhat. When Ally finishes a command, it will output:
To make these settings take effect for this terminal session,

And then cuts off. We ideally want to have ally reload the terminal automatically.
Describe the solution you'd like
The ally command should be set into a zsh function, allowing source to be run after normal command finishes. Otherwise, we can change it to outputting
source $HOME/.ally

Describe alternatives you've considered
A function or asking the user to run source, but that requires further user action. Since it is ally's goal to mimic the alias command, we ideally want it to add it to the local session like alias does.

This is TOP PRIORITY because it is how the user will reload the terminal. Failure to accomplish this issue means that the ally command DOES NOT WORK like the ZSH alias command.

repo: OCA-Creations/Ally


text:
Maluspunten opnieuw maken

Is foei lelijk lol

#173


text:
Add a relish push line to continuous integration

adding a relish push to continuous integration would mean that features published to Relish would always be up to date
gem install relish
relish push <path>

may not be needed after #496 tested

no longer needed - using Cucumber Pro

repo: ODIQueensland/data-curator


text:
[Documentation on DockerHub] Add statement on Eclipse version to use with the plugin

In the "Rule Designer development environment for ODM developers:" section  of the DockerHub page we read that we have to use Eclipse v4.7.3. but we don't know if this is the only version of Eclipse that works and/is supported.
What if I use another version?

See the different branches:
https://github.com/ODMDev/ruledesigner
I believe each version of ODM has a plugin for a specific version of eclipse.  Other versions of eclipse are supported with different versions of ODM, but you'll loose functionality.
It is still unclear to me if ODM v8.10.2 supports say Eclipse v3.7, but I've always found it best practice to keep different versions totally separate and downloading exact versions of software.

repo: ODMDev/odm-ondocker


text:
NullPointerException bei der Erstellung einer neuen Task

(ArrayAsList Branch)

wurde gefixt

authors: OGNylux Tobree


text:
Problem with cookie-cipher-secret-key

Im trying to add authentication to Spark using this filter. Im using:

Keycloak
Spark 3.5.1

Im identifying that there is something strange in terms of the cookie-cipher-secret-key. Im seeing this message (already logged in)

To generate the key Im using the comand that is in the documentation: openssl enc -aes-128-cbc -k <PASS PHRASE> -P -md sha1 -pbkdf2. The output is this:

Im putting the key value as the value of cookie-cipher-secret-key
It seams that there is an issue encoding and decoding but I don't seem to find the problem. ¿Is it possible that this is due to a wrong key cookie-key definition?

No, we have not hitted this issue before.
To help reproduce the issue from my side, what is the java base image and version you use to build your spark image?
Alternatively,  can you try with this image: ?

quay.io/okdp/spark:spark-3.5.1-scala-2.13-java-17 or
quay.io/okdp/spark:spark-3.5.1-scala-2.12-java-17

Im currently using this Spark image: bitnami/spark:3.5.1. I would like to try the images that you mention, ¿is it possible that you can provide me with a configuration example for docker-compose.yml with those images?

There is an issue, related to base64 encoding/decoding logic in the filter, with the bitnami jdk which does not happen in other JDKs distributions tested until now.
I have pushed a fix as a pre-release here: https://github.com/OKDP/okdp-spark-auth-filter/releases/tag/v1.2.2
Can you please, test with the jar okdp-spark-auth-filter-1.2.2.jar also included in the Assets

Hi @idirze ,
We have tested the change in 1.2.2 with bitnami/spark images (3.5.1 exactly) and it works correctly. We appreciate that you have taken the time to make the changes.

I close the issue. Fixed by v1.2.2.

I close the issue. Fixed by v1.2.2.

I close the issue. Fixed by v1.2.2.

authors: idirze luiscinfo

repo: OKDP/okdp-spark-auth-filter


text:
Added ability to add theme settings and a census output

Main features:

Created a census.scss manifest file.
Webpack outputs a census.css file.
Created 'settings/_census.scss' for any Census related styles.
Added !default to variables and typography in existing files.
Renamed responsive.scss to main.scss.

Looks good, only suggestion I have is to put everything but settings into one file (maybe something like _core.scss, and then have main.scss import the default settings and _core.scss, and then census.scss to import the census settings and _core.scss... keeps it dry and means if anything else is changed or added its only done in one file.

Oh also, if you could search for anywhere where responsive.css was referenced and change that to main.css, because I think you might have missed some templates.

Looks good, I think you still need to change the responsive.css reference in  src/styles/page-template/_template.njk

authors: bameyrick boxadesign

repo: ONSdigital/design-system


text:
Do not store unanswered questions in the answer store

Merge only after #1925 has gone in. (I have merged that branch into this one).
What is the context of this PR?
Trello.
Currently, the data we store in the answer store for unanswered questions is quite varied (see Andrew's investigation in trello). This PR normalises that by ensuring we never store anything in the answer store for unanswered questions.
Since version 3 of the questionnaire store didn't involve an answer store upgrade, I had to modify the upgrade method to allow for skipped versions. The difficulties around this system of versioning / upgrades have been noted in a trello card, we likely need to refactor this. I have not gone very far in this PR.
How to review
The /dump/answers endpoint should prove useful. Run through some live surveys.
Ensure unanswered questions do not appear in the store. Test each of the question types.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Haven't tested everything in SDX but it seems to work as expected.

authors: MebinAbraham bitdivision

repo: ONSdigital/eq-survey-runner


text:
Update api.md

Update api.md to reflect current endpoints and bring in line with other services. Added missing endpoint to find sample unit by id and added samples blueprint to urls.

 Update Api.md for java services

repo: ONSdigital/rm-sample-service


text:
Feature/sdx sequence on cloud foundry

What? and Why?

Removed redundant config.ini
Added vcap_example.json to enable testing
Refactored settings to make them more testable
Added more tests

Codecov Report

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

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   71.55%   71.55%
=======================================
  Files           1        1
  Lines         109      109
=======================================
  Hits           78       78
  Misses         31       31

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 eac96d5...c0b6ee5. Read the comment docs.

 2nd 1/2 SDX into Cloudfoundry (5)

authors: AndrewTorrance codecov-io

repo: ONSdigital/sdx-sequence


text:
fixup: only use mpi rank in name if greater than one rank

Mistake in #5

@gknapp1 this is the mistake you noted


text:
Kinetics Options - Default Parameters

Suggest adding in default fuels/reactors to the kinetics options. Perhaps 4 options like: 235-U, 233-U, 239-Pu, and custom. This could also be implemented by allowing the user to select from several predefined options and then make modification, thus negating the custom option.
The current implementation loads defaults from a variety of sources (the beta and lambda info is 235-U). I would suggest, in general, that a consistent set of defaults be made available (perhaps PWR for now). Can also draw some of this info from publicly available FSAR/DCD.

Well I'm no fuels expert, but I understand the beta_i and lambda_i stuff to be characteristic of the primary fissile isotope. So what you have for 235-U is likely acceptable. Still might be useful to protect some of these from the user as 235-U, 233-U, etc. Like I said, I'm not the fuels guys here but we should ask one to see what actually does change from reactor to reactor, core to core, cycle to cycle, etc.
The reactivity coefficients, however, could be made slightly more consistent by using a common source such as AP1000 DCD (I mention this as this is what I am familiar with, not because it it the most useful. As NHES has been interested IRIS, maybe it makes sense to use that as default, but I digress). For AP1000, you could use the material in Ch 4.3, specifically Table 4.3-2. (https://www.nrc.gov/docs/ML1117/ML11171A445.pdf)
The challenge here is that many parameters are expressed as a functions of temperature and/or boron concentration. This implies the use of a separate module outside of PK (or perhaps inside a larger kinetic module) to calculate the effective temperature/parameter and then some sort of look-up table or spline function.
So the rabbit hole is quite deep here.

repo: ORNL-TRANSFORM/TRANSFORM-Library


text:
Error about port key in the settings dictionary

I installed zambeze from the dev-cleanup branch and tried to run the imagemagick_files.py example. I get the key error shown below:
Traceback (most recent call last):
  File "~/FlowceptZambeze/zambeze/examples/imagemagick_files.py", line 60, in <module>
    main()
  File "~/FlowceptZambeze/zambeze/examples/imagemagick_files.py", line 56, in main
    campaign.dispatch()
  File "~/FlowceptZambeze/zambeze/zambeze/campaign/campaign.py", line 90, in dispatch
    zmq_port = settings.settings["zmq"]["port"]
KeyError: 'port'

It looks like the ZambezeSettings class needs a config file. Do I need to provide a config file to run this example? If so, what type of file does this config need to be and what do I put in the file?

The config file is located at ~/.zambeze/agent.yaml after running zambeze agent start.

repo: ORNL/Zambeze


text:
Remove/replace mentions of LLNL

You might want to grep from LLNL
The https://ornl.github.io/software-catalog/about/ page mentions LLNL 10x.  Only the headers and the first sentence were ported.

Should be gone now, thanks.

repo: ORNL/software-catalog


text:
Support Sorting and Top Count on results

Something like right click to sort and "show top n" type of functionality would be immensely useful for ad-hoc analysis

+1000
and calculated columns!

+1!

+1

authors: adphillips jsotresr pablo9044 seocam

repo: OSBI/saiku