text:
acpid: 2.0.29 -> 2.0.30

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/acpid/versions.
meta.description for acpid is: '"A daemon for delivering ACPI events to userspace programs"'.

Checks done (click to expand)

built on NixOS
/nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin/acpi_listen passed the binary check.
/nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin/acpid passed the binary check.
Warning: no invocation of /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin/kacpimon had a zero exit code or showed the expected version
2 of 3 passed binary check by having a zero exit code.
2 of 3 passed binary check by having the new version present in output.
found 2.0.30 with grep in /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30
directory tree listing: https://gist.github.com/9a6064536f0d2a1dc0f6bebe16b24a2a
du listing: https://gist.github.com/d0165f4766121872a87cb61128c50a58

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 7225c2acd063709c85a9a5e9924a5ddea6cc4b65 && nix-shell --pure -I nixpkgs=. -p acpid

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: acpid
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: acpid
Partial log (click to expand)
shrinking /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin/acpi_listen
shrinking /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/sbin/acpid
shrinking /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/sbin/kacpimon
gzipping man pages under /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/share/man/
strip is /nix/store/90vmpr41dzsx350k5argycaf693hnl1l-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin  /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/sbin
patching script interpreter paths in /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30
checking for references to /build in /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30...
moving /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/sbin/* to /nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30/bin
/nix/store/jjl60m8jhn884bxg60nxpzihry13sq63-acpid-2.0.30

Success on aarch64-linux (full log)
Attempted: acpid
Partial log (click to expand)
shrinking /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/bin/acpi_listen
shrinking /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/sbin/acpid
shrinking /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/sbin/kacpimon
gzipping man pages under /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/share/man/
strip is /nix/store/7iyn7gn33i7xxjgmwf25k20246y6nd9d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/bin  /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/sbin
patching script interpreter paths in /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30
checking for references to /build in /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30...
moving /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/sbin/* to /nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30/bin
/nix/store/wsspggaakysr4r9nfwjylsqizf3j7gxd-acpid-2.0.30

authors: GrahamcOfBorg r-ryantm


text:
gnupg22: 2.2.10 -> 2.2.11

Motivation for this change
See http://lists.gnu.org/archive/html/info-gnu/2018-11/msg00003.html for
release information
Once merged, I’ll backport this to staging-18.09 and staging-18.03 since this is a maintenance release.
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 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 x86_64-linux (full log)
Attempted: gnupg22
Partial log (click to expand)
shrinking /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/bin/gpg
shrinking /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/bin/gpgsm
gzipping man pages under /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/share/man/
strip is /nix/store/rpbg8gmqxhz8g61p1plz5d2srs84pvmv-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/lib  /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/libexec  /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/bin  /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/sbin
patching script interpreter paths in /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11
/nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/sbin/addgnupghome: interpreter directive changed from "/bin/sh" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/sh"
/nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/sbin/applygnupgdefaults: interpreter directive changed from "/bin/sh" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11...
moving /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/sbin/* to /nix/store/ipglbqjp2p3k1yfzaggfgy1dgc7546dh-gnupg-2.2.11/bin

cherry-picked to staging-18.09: cff4cb689f6

I actually did push it to 18.09 along side with other cherry-picks this morning… (76a06b02ecf87e3057bccc47061c113e08f9e931) Should I revert this backport to release-18.09 and wait for staging-18.09 to be merged ? (sorry if I went to a too fast integration into the release branch…)

oh, whoops. Given the amount of rebuilds I think this should only go to staging? I'm not sure though.

Yes, I guess I should have gone for that approach, but hydra seems to have done a good job at the moment: https://hydra.nixos.org/eval/1489936 (less than 200 jobs to go at the moment). And I actually said in the PR message that I would backport those to staging-18.09, not release-18.09… This is definitely my mistake.
But since it is done, and hydra already did most of the job, I think we should leave it there.

source: gharchive/pull-request

authors: GrahamcOfBorg lheckemann lsix

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
xpra: Mark as broken

Motivation for this change
https://github.com/NixOS/nixpkgs/pull/48872#issuecomment-433559636
Things done

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

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: xpra
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: xpra
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: xpra
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

authors: GrahamcOfBorg Infinisil


text:
dockerTools.buildImage.runAsRoot: preserve layers ordering at image unpacking

This patch preserves the ordering of layers of a parent image when the
image is unpacked.
Fixes #55290
Motivation for this change
Things done

[ ] 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 nox --run "nox-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.

Backported to 19.03 (8002a7f1e41b290d307a1dbec819898c0c522d21)


text:
networkmanager_strongswan: 1.4.4 -> 1.4.5

Motivation for this change
TODO:

[ ] Confirm working on appropriate setup(s).
[ ] check release notes's mentions of compat or issues

Things done

[ ] 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.

News had one change
- Enables the IPv6 tab in the connection dialog

Should be very safe.

authors: dtzWill worldofpeace


text:
Reorganize GNOME tests, re-enable LightDM for release-combined

Motivation for this change
Other than the name changes ~all the GNOME3 tests use GDM and~ we re-enabled the LightDM test.
Things done
quick hack, haven't tested anything yet

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

Notify maintainers
cc @

Thoughts for followup improvement

write an actual GDM test
do we need standalone DM tests?
test GDM in all the GNOME tests

For some reason I couldn't get the gnome-xorg test to work at all with gdm. And I made sure wayland was disabled. Guess I'll save that for later.

@GrahamcOfBorg test gnome-xorg

@GrahamcOfBorg test gnome3 lightdm

@GrahamcOfBorg build gnome3.gnome-software

@GrahamcOfBorg test gnome3

I've tested that everything succeeds on aarch64.


text:
Remove newline in PS1

Motivation for this change

The current behaviour is opinionated and it shouldn't be up to distributions to decide this. Distributions should use the "default" which users expect.
It fills the terminal for no reason.
There is no reason to have it.
People often leave it because they don't know how to remove it. https://stackoverflow.com/questions/51560300/unwanted-bash-newline-nixos

This newline has been present as far back as git allowed me to go in PS1 (7c93a71468e7d5) (2008 more than 10 years ago).
Things done

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

-1, though it's a purely personal preference so I won't insist if this is widely supported.

there is a reason to have it, which is that commands that don't terminate their output with a newline don't mess up the prompt.

While messing up all other commands.
The thing is that this is non standard. NixOS (from what I know) is the only distro that does this. Also I'm pretty sure that in Ubuntu commands that finish without newlines aren't messed up, how do they do it?

While messing up all other commands.
The thing is that this is non standard. NixOS (from what I know) is the only distro that does this. Also I'm pretty sure that in Ubuntu, commands that finish without newlines aren't messed up, how do they do it?

zsh fixes that on its own, maybe bash also have an option for that?

While messing up all other commands.

It doesn't mess anything up at all, just looks different.

there is a reason to have it, which is that commands that don't terminate their output with a newline don't mess up the prompt.

It doesn't mess anything up at all, just looks different.

Applies to both

A non-newline-terminated command does mess up the prompt if the prompt doesn't start with a newline. To see what I mean, try printf " %.0s" $(seq $((COLUMNS - 5 ))), and compare behaviour afterwards with a newline in the prompt and without.

A non-newline-terminated command does mess up the prompt if the prompt doesn't start with a newline. To see what I mean, try printf " %.0s" $(seq $((COLUMNS - 5 ))), and compare behaviour afterwards with a newline in the prompt and without.

I think i would be nice to do it similarly to Ubuntu (if they actually have a way and I'm not just making things up) but the same applies:

It doesn't mess anything up at all, just looks different.

This is just a choice but I believe it is better to do what is "expected".

Maybe you could mention it on Discourse and ask for people's opinions.
I don't really care either way, since I use fish and it does this:
$ echo "Foo"
Foo
$ echo -n "foo"
foo⏎                                                                                $

However when I use bash on other distros I'm sometimes confused where my PS1 indicator has gone when it's just at the end of a long line without \n.
So I concur with @lheckemann that I don't want my prompt messed up.
As you mentioned it has been like this for >10 years so I wouldn't change it willy nilly.

Indeed it has been this way since the start and I don't see a strong reason to change it. I prefer it this way since I think it makes bash a bit more readable by clearly separating command invocations. Obviously not everybody will agree but that's true for any default.

authors: JohnAZoidberg Mic92 NilsIrl edolstra lheckemann


text:
firectl: init at 0.1.0

Motivation for this change
firectl is a command-line tool to run Firecracker microVMs.

https://github.com/firecracker-microvm/firectl

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

Notify maintainers
cc @

@GrahamcOfBorg build firectl

@jonringer Thank you!

authors: jonringer xrelkd


text:
buildStackProject: Set __noChroot to make it fail without sandbox

Motivation for this change
Currently buildStackProject doesn't have any indication that it needs the sandbox to be disabled, leading to a hard-to-decipher error, see https://github.com/NixOS/nixpkgs/issues/32005
With this change, doing a buildStackProject will result in
error: derivation '/nix/store/nk4wms3hk4mp9lc86k30vc8w44fcq0rj-foo.drv' has
  '__noChroot' set, but that's not allowed when 'sandbox' is 'true'

when attempting to build it without --option sandbox false
Fixes #32005
Things done

[x] Made sure this error happens without disabling the sandbox

@Infinisil Thanks for this change.  I was actually thinking of doing this myself.
I think this is okay as-is, if you'd like to go ahead and merge it.
However, if possible, I think it would be nice to add a little more documentation.  For example, either linking to the nix manual where it talks about __noChroot, or alternatively just adding a small example of running nix-build with sandbox set to relaxed.
As a new user, at one point I came across __noChroot and had no idea what it meant or where I could find more information about it.

Added a bit more comment and docs

Thanks! Looks really good!

authors: Infinisil cdepillabout


text:
Atari800: no more ROM install

Now, the expression will not install ROM files anymore. It is easier the
final user install them locally by himself, in a local directory.

(The Travis failure is due to ide.o being omitted from the final link step. It's weird, and I can't reproduce it anywhere, but it's nothing to do with this commit.)
Tested & merged. Thanks!

authors: AndersonTorres nckx


text:
Port NixOS tests to python

Motivation for this change
#72828
Things done

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

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

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

Notify maintainers
cc @tfc

@GrahamcOfBorg test systemd-timesyncd
@GrahamcOfBorg test switch-test
@GrahamcOfBorg test sonarr
@GrahamcOfBorg test quagga
@GrahamcOfBorg test postgis
@GrahamcOfBorg test php-pcre
@GrahamcOfBorg test pgmanage
@GrahamcOfBorg test peerflix
@GrahamcOfBorg test pdns-recursor
@GrahamcOfBorg test paperless

@GrahamcOfBorg test switchTest

@veprbl @tfc Thanks for reviewing :+1:

authors: kampka veprbl


text:
libwebsockets: propagate openssl and libuv

Motivation for this change
Resolves #76714.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[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
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

according to the libwebsockets.pc, this is intended behavior:
prefix="/nix/store/0xdhyq4hj6ypa0lrsqnasz5cnjcjxr61-libwebsockets-3.2.0"
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

Name: libwebsockets
Description: Websockets server and client library
Version: 3.2.0

Libs: -L${libdir} -lwebsockets
Cflags: -I${includedir}

However, this doesn't mean that the package has an incorrect .pc, which it likely does.
Personally, I'm against propagating libraries because it adds the dev closure (and transitively the dev closure of all dependencies) to package's runtime closure, see https://github.com/NixOS/nixpkgs/pull/71553 for an example bloat

But practical use of libwebsockets requires these dependencies, no?
The added closure size seems marginal to me:
nix path-info -Sh ./result # after
/nix/store/10wc552m2xacsaqfab5vac65ihp8gjsz-libwebsockets-3.2.0	 188.5M

nix path-info -Sh ./result # before
/nix/store/0xdhyq4hj6ypa0lrsqnasz5cnjcjxr61-libwebsockets-3.2.0	 186.4M

If this is an issue we should take upstream, this could just be a stopgap... :man_shrugging:

They are optional

Seeing as this has been inactive for 6 months, and it's likely not intended behavior from upstream, im going to close

authors: furrycatherder jonringer volth


text:
python3Packages.annoy: add missing h5py dependency

Motivation for this change
noticed it was broken reviewing another package
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.

Notify maintainers
cc @

@GrahamcOfBorg build python3Packages.annoy

@GrahamcOfBorg build python3.pkgs.rl-coach

tensorflow build is broken right now, so rl-coach will fail anyway

authors: filalex77 jonringer timokau


text:
Itk: 5.0.1 -> 5.1.0

Motivation for this change
Things done

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

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

[NA] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] 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.

@GrahamcOfBorg build elastix ezminc simpleitk vtk itk4

@GrahamcOfBorg build elastix ezminc simpleitk vtk itk4

@GrahamcOfBorg build elastix ezminc simpleitk vtk itk4

@jonringer -- pkgconfig now propagated.

@jonringer -- pkgconfig now propagated.

Hm. This means it will only be available to all nix-builds depending on it, but not at runtime when using nix run nixpkgs.itk. If we want the latter we probably will need to add the pkg-config PATH to the makeWrapperArgs, right?

@knedlsepp -- h5cc and h5c++ are compiler wrappers so most likely they would be used by other derivations, although it's a bit unseemly to have them fail at runtime.  Not sure what the best solution is here -- these are somewhat incidental programs built by the ITKHDF5 module which aren't needed to compile most programs using ITK (including all reverse deps in the Nixpkgs tree such as ANTs).  Is it worth it to create a wrapper for them?

I've wrapped h5c++ with pkgconfig.

@GrahamcOfBorg build elastix ezminc simpleitk vtk itk4

@GrahamcOfBorg build vtk itk elastix ezminc simpleitk

@GrahamcOfBorg build elastix ezminc simpleitk vtk itk4

authors: bcdarwin knedlsepp veprbl


text:
[20.03] jool: 4.0.5 -> 4.0.9

(cherry picked from commit a8ee561b0f2f9d5676a83dfe274985b052343907)

Motivation for this change
Fixes build error, as https://github.com/NixOS/nixpkgs/pull/89754 does.
Things done

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

[x] NixOS

tested with Kernel 5.4.44 and 5.6.16 (boot.kernelPackages = pkgs.linuxPackages_latest;)
Test environment is a nixos-container which did ping and mtr to 64:ff9b::8.8.8.8
Only the NAT64 mode was tested.

[ ] 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.

@GrahamcOfBorg build linuxPackagesv_latest.jool


text:
spago: 0.15.1 -> 0.15.3

Motivation for this change
Bumps spago to 0.15.3 (and gets building with LTS-16).
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.

@GrahamcOfBorg build spago

Looks like it is successfully building at least on x86_64-linux.


text:
sndio: 1.6.0 -> 1.7.0

Motivation for this change
Updates sndio to the latest version.
Things done

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

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

Fails to build on macos (10.14):
mkdir -p /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/bin /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/share/man/man1
  cp midicat /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/bin
  cp midicat.1 /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/share/man/man1
  make[1]: Leaving directory '/private/tmp/nix-build-sndio-1.7.0.drv-0/sndio-1.7.0/midicat'
  post-installation fixup
  gzipping man pages under /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/share/man/
  strip is /nix/store/gmhd52yac3w4zk8xqsgh97makjh8gi7l-cctools-binutils-darwin-927.0.2/bin/strip
  stripping (with command strip and flags -S) in /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/lib  /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/bin
  patching script interpreter paths in /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0
  error: install_name_tool: can't open file: /nix/store/mq3gi0vq1jarrzhk9qg8pn4pvhiyjnv5-sndio-1.7.0/lib/libsndio.7.0.dylib (No such file or directory)

Rather than chasing the exact .dylib name in a postFixup all the time, it does seem to work if you simply add fixDarwinDylibNames to the build inputs if stdenv.isDarwin.
Also, obviously, could do with a rebase.

WFM, macos 10.14, non-nixos linux x86_64.

authors: S-NA risicle


text:
使用iTransformer遇到问题

What happened + What you expected to happen
Traceback (most recent call last):
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 541, in _run_script
exec(code, module.dict)
File "/sdc/jky/llm_demo/pages/1_Training.py", line 90, in
Y_hat_insample = nf.predict_insample(step_size=pred_len)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/neuralforecast/core.py", line 1175, in predict_insample
fcsts[:, col_idx : (col_idx + output_length)] = model_fcsts
ValueError: could not broadcast input array from shape (1404,1) into shape (1440,1)
在进行样本内预测时发生了报错，但是书写代码并没有发现问题
Versions / Dependencies
python=3.8
neuralforecast=1.7.2
Reproduction script
nf = NeuralForecast(
models=[model],
freq=freq
)
    nf.fit(df=train_df, val_size=pred_len)

    if not os.path.exists(save_path):
        os.makedirs(save_path)

    nf.save(path=save_path,
            model_index=None,
            overwrite=True,
            save_dataset=True)

    Y_hat_insample = nf.predict_insample(step_size=pred_len)
    print('Y_hat_insample' ,Y_hat_insample.head(),Y_hat_insample.shape)
    Y_hat_insample = pd.DataFrame(Y_hat_insample)

Issue Severity
None

Hi, thanks for using neuralforecast.
Can you include a fully reproducible example of code (a piece of code that I can copy-paste and run standalone on my machine), demonstrating the error? Otherwise it's very difficult for me to help.

您好，感谢您使用神经预测。
您能否提供一个完全可重现的代码示例（一段我可以复制粘贴并在我的计算机上独立运行的代码）来演示该错误？不然我很难帮忙。

您好，这是完整的代码，麻烦你了
train_df = pd.read_csv('/sdc/jky/llm_demo/coin_BinanceCoin.csv',encoding='utf-8')
print('etth1', train_df.head())
model = iTransformer(h=12,
input_size=36,
n_series=8,
hidden_size=128,
n_heads=8,
e_layers=2,
d_layers=1,
d_ff=4,
factor=1,
dropout=0.1,
use_norm=True,
loss=MSE(),
valid_loss=MSE(),
early_stop_patience_steps=3,
batch_size=24,
max_steps=5)
nf = NeuralForecast(
models=[model],
freq='D'
)
nf.fit(df=train_df, val_size=12)
nf.save(path=save_path,
model_index=None,
overwrite=True,
save_dataset=True)
print('模型保存完成')
Y_hat_insample = nf.predict_insample(step_size=pred_len)
print('Y_hat_insample' ,Y_hat_insample.head(),Y_hat_insample.shape)
Y_hat_insample = pd.DataFrame(Y_hat_insample)
Y_hat_insample['unique_id'] = Y_hat_insample.index
mae = mae(Y_hat_insample,models=['iTransformer'],id_col='unique_id')
mse = mse(Y_hat_insample,models=['iTransformer'],id_col='unique_id')
validation_df = pd.DataFrame(data={'MAE': mae['iTransformer'], 'MSE': mse['iTransformer']})

不好意思，我又遇到一个新的问题，在进行iTransformer预测时发现torch版本不能低于2.1.0，如果低于会有如下报错
Traceback (most recent call last):
File "/data/anaconda3/envs/time_py/lib/python3.9/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 600, in _run_script
exec(code, module.dict)
File "/sdc/jky/llm_demo/pages/2_Forecast.py", line 40, in
nf2 = NeuralForecast.load(path=load_path)
File "/data/anaconda3/envs/time_py/lib/python3.9/site-packages/neuralforecast/core.py", line 1357, in load
loaded_model = MODEL_FILENAME_DICT[model_class_name].load(
File "/data/anaconda3/envs/time_py/lib/python3.9/site-packages/neuralforecast/common/_base_model.py", line 351, in load
model.load_state_dict(content["state_dict"], strict=True, assign=True)
TypeError: load_state_dict() got an unexpected keyword argument 'assign'
但是如果我把版本更新到torch=2.1.0，又不能进行iTransformer的训练，也就是训练要求版本不能高于torch=2.0.1，如果高于会有如下报错
Traceback (most recent call last):
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 600, in _run_script
exec(code, module.dict)
File "/sdc/jky/llm_demo/pages/1_Training.py", line 80, in
nf.fit(df=train_df, val_size=pred_len)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/neuralforecast/core.py", line 462, in fit
self.models[i] = model.fit(
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/neuralforecast/common/_base_multivariate.py", line 537, in fit
return self._fit(
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/neuralforecast/common/_base_model.py", line 219, in _fit
trainer.fit(model, datamodule=datamodule)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 544, in fit
call._call_and_handle_interrupt(
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/call.py", line 44, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 580, in _fit_impl
self._run(model, ckpt_path=ckpt_path)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 987, in _run
results = self._run_stage()
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1033, in _run_stage
self.fit_loop.run()
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 205, in run
self.advance()
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 363, in advance
self.epoch_loop.run(self._data_fetcher)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 140, in run
self.advance(data_fetcher)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 250, in advance
batch_output = self.automatic_optimization.run(trainer.optimizers[0], batch_idx, kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 190, in run
self._optimizer_step(batch_idx, closure)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 268, in _optimizer_step
call._call_lightning_module_hook(
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/call.py", line 157, in _call_lightning_module_hook
output = fn(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/core/module.py", line 1303, in optimizer_step
optimizer.step(closure=optimizer_closure)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/core/optimizer.py", line 152, in step
step_output = self._strategy.optimizer_step(self._optimizer, closure, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/strategies/strategy.py", line 239, in optimizer_step
return self.precision_plugin.optimizer_step(optimizer, model=model, closure=closure, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/precision.py", line 122, in optimizer_step
return optimizer.step(closure=closure, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/optim/lr_scheduler.py", line 68, in wrapper
return wrapped(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/optim/optimizer.py", line 373, in wrapper
out = func(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/optim/optimizer.py", line 76, in _use_grad
ret = func(self, *args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/optim/adam.py", line 143, in step
loss = closure()
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/precision.py", line 108, in _wrap_closure
closure_result = closure()
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 144, in call
self._result = self.closure(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 138, in closure
self._backward_fn(step_output.closure_loss)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 239, in backward_fn
call._call_strategy_hook(self.trainer, "backward", loss, optimizer)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/trainer/call.py", line 309, in _call_strategy_hook
output = fn(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/strategies/strategy.py", line 213, in backward
self.precision_plugin.backward(closure_loss, self.lightning_module, optimizer, *args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/precision.py", line 72, in backward
model.backward(tensor, *args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/pytorch_lightning/core/module.py", line 1090, in backward
loss.backward(*args, **kwargs)
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/_tensor.py", line 492, in backward
torch.autograd.backward(
File "/data/anaconda3/envs/time_py/lib/python3.8/site-packages/torch/autograd/init.py", line 251, in backward
Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: GET was unable to find an engine to execute this computation

Can you upgrade your Pytorch version to the latest version?

你能将你的 Pytorch 版本升级到最新版本吗？我认为你可能使用的是 PyTorch 2.0.0，而且该版本的代码似乎存在问题。因此升级到 2.1+ 应该可以解决问题。

1、您好，您说的我都已经试过了，如果版本更新到2.1+以上，则无法训练，报错信息我已经粘贴在上述问题中
2、关于第一个问题，我依旧无法进行样本内预测

I am currently running torch==2.3.1+cu121 and neuralforecast 1.7.2 and am also experiencing this issue. JKYtydt's reproducible example didn't reproduce the error for me.
I have created a reproduction of the error below. The dataset can be accessed here
`import numpy as np
import pandas as pd
import torch
from neuralforecast.core import NeuralForecast
from neuralforecast.auto import AutoNHITS
from neuralforecast.losses.pytorch import MQLoss
import os
torch.cuda.is_available()
horizon = 14
input_size = 28
num_samples = 1
ts_df = pd.read_parquet(os.path.join('data', 'ts_cleaned_dataset.parquet'))
ts_df = ts_df.rename(columns={'date': 'ds', 'Rt': 'y', 'cases_key': 'unique_id'})
auto_model = AutoNHITS(h=horizon, loss=MQLoss(), num_samples=num_samples, config=dict(input_size=input_size))
nf = NeuralForecast(models=[auto_model], freq='D')
nf.fit(df=ts_df)
insample_pred_df = nf.predict_insample()`
The final line results in the error:
`core.py:1176) # Append predictions in memory placeholder
core.py:1177) output_length = len(model.loss.output_names)
core.py:1178) fcsts[:, col_idx : (col_idx + output_length)] = model_fcsts
core.py:1179) col_idx += output_length
core.py:1180) model.set_test_size(test_size=test_size)  # Set original test_size
ValueError: could not broadcast input array from shape (39393900,5) into shape (28724780,5)`

@eye4got 您好，非常感谢您提供的建议，您方便告诉一下具体的解决办法么

@JKYtydt you need to make every unique_id have the same number of time steps. So you can either: 1) cut all the timeseries down to the same length and/or not include some shorter timeseries, so that they are all say 100 days long; 2) use some kind of interpolation or imputation method to fill missing data so they are all the same length. I honestly switched to using the darts package when I found out that neuralforecast doesn't support multivariate forecasting for TFT models. It is much more flexible when it comes to restrictions like this

@eye4got 您好，我的这个数据集unique_id是唯一的，也没有缺失值，但是它仍然存在这个报错，且发现这个形状的差别刚好是输入的序列长度，这有什么关联么
test.py 68 <module>
Y_hat_insample = nf.predict_insample(step_size=12)

core.py 1175 predict_insample
fcsts[:, col_idx : (col_idx + output_length)] = model_fcsts

ValueError:
could not broadcast input array from shape (1416,1) into shape (1440,1)

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://github.com/Jostino/RimWorld-it/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

source: gharchive/issue

authors: FoioMikael JKYtydt KrissV2 elephaint enricozao eye4got louseee rajnikyadav

repo: Nixtla/neuralforecast


text:
How predict_rolled works

Could you please explain how predict_rolled would work if I pass n_windows and step_size to predict multiple steps ahead? Lets say my data is hourly and the model predicts for the next day. If I want to get predictions for the next 30 days I could use predict_rolled(df, window_size=30*24, step_size=24) to get the predictions. My question is will the model use measured data of the previous window to predict the next samples or use its predictions to predict the next window? I know that for the first sequence it will definitely use measured data but for predicting next sequences does it use its previous predictions or measured data as input?
Thanks.

Hi @tinased95,
We are working on an updated version of the predict_rolled method.
We will deprecate it soon in favor of a predict_insample method that generates the rolling predictions of dimensions
[n_series, n_time, horizon] or when you send step_size [n_series, n_time//step_size, horizon] in flattened format.
This is the PR https://github.com/Nixtla/neuralforecast/pull/528.

Thanks for your response. My question is regarding rolling predictions; Does the model use measured data each time moving forward in time or use its previous predictions as the input to predict the next sequence?

Currently, all our models employ a multi-step forecast strategy, which involves generating a forecast in multiple steps or stages. This approach allows us to create a forecast in a single forward pass, resulting in faster predictions, compared to the recurrent version.
The strategy is depicted here:
https://nixtla.github.io/neuralforecast/models.dilated_rnn.html

Thanks. Based on the paper you shared, which strategy are you using for multi-step forecasting in predict_rolled method?

Most networks use an MLP decoder that creates the whole forecast horizon in a single pass.

I apologize for any confusion, but I'm still unclear on the name of the strategy being used in predict_rolled. Would it be possible for you to kindly share that information with me? Thank you.

Hi @tinased95! If you want to make several historical predictions, you can use the cross_validation function. To make daily forecasts for one month, you can set the following hyperparameters of the function: n_windows=30 and step_size=24.
Here is an explanation: the first prediction will be made at the timestamp T-3024 hours (where T is the length of your data), and it will use all the information before that point to forecast. It will then "move" to T-2924 and produce the forecast again with the latest available data. Note that this function only works for historical data. We do not yet have a function to iteratively forecast longer horizons (than h) and concatenate the forecast. I hope this helps.

Thank you so much for your response.

authors: cchallu kdgutier tinased95


text:
how to use grid in positioning

Here we learned how to use grid and in the css and linking them to html.

Thank you


text:
경기도 에러

실례하지만

계속 경기도만 "unable to verify the first certificate"이라고 뜹니다.
혹시 Rest API라 사용 가능하게 하실 수 있나요? 지금은 Node 파일로만 있지만 API로 만들면 좋을 것 갍습니다.
직접 빌릴 수 있는 링크를 삽입할 수 있나요?

감사합니다!

문제는 확인했는데 제가 지금 코로나에 걸려서 빠른 시일내에 고치긴 어려울것 같습니다
2, 3. 말을 좀 이해하지 못했는데 자세히 설명 가능할까요

조금 더 확인해보니 수도권 지역만 되네요.. 지역마다 리퀘스트 규칙이 다 다른가봅니다

Firebase처럼 Rest API를 배포할 수 있나요?
제가 잘 모르는 부분이어서 그런데 혹시 학교 도서관으로 직접 들어가서 빌릴 수 있게 만들 수 있나요? 예를 들면, 한 책에 대한 정보를 가지고 오고 링크가 따라와서 누르면 바로 빌릴 수 있게.

현재 고치고 있긴한데 axios 모듈의 문제인지 정확한 이유는 모르겠지만 울산, 세종, 강원만 안되네요.
조금 더 시도하볼거지만 계속해서 안되면 그냥 세 지역만 빼고 커밋하겠습니다...

RestAPI로 배포하는건 좀 힐들것 같고, YSC대회에서 node.js를 사용하신다면 express, app 관련 다 빼고 searchBookFromSchoolName(localName, bookName, schoolName)을 사용하시면 됩니다.
학교 도서관으로 바로 리다이렉트 해주는 링크는 독서교육종합지원시스템에서 딱히 나와있지 않아 추가하지 않았습니다.

제 깃허브 fork에서 https://littlechildwriter-school.onrender.com로 @NoBrain0917 님의 코드를 수정해서 배포했습니다


text:
🛑 rimgo rimgo.whateveritworks.org is down

In 5eb7d37, rimgo rimgo.whateveritworks.org (https://rimgo.whateveritworks.org) was down:

HTTP code: 502
Response time: 338 ms

Resolved: rimgo rimgo.whateveritworks.org is back up in 1b51e89.

repo: NoPlagiarism/services-personal-upptime


text:
🛑 libreddit libreddit.spike.codes is down

In a375679, libreddit libreddit.spike.codes (https://libreddit.spike.codes) was down:

HTTP code: 502
Response time: 21653 ms

Resolved: libreddit libreddit.spike.codes is back up in 45653f8.


text:
🛑 librarian (discontinued) lbry.vern.cc is down

In 8c6048f, librarian (discontinued) lbry.vern.cc (https://lbry.vern.cc) was down:

HTTP code: 0
Response time: 0 ms

Resolved: librarian (discontinued) lbry.vern.cc is back up in cc4fc7c after 9 days, 2 hours, 46 minutes.


text:
🛑 rimgo rimgo.in.projectsegfau.lt is down

In b7ad32e, rimgo rimgo.in.projectsegfau.lt (https://rimgo.in.projectsegfau.lt) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rimgo rimgo.in.projectsegfau.lt is back up in a6652fc.


text:
🛑 ProxiTok proxitok.privacydev.net is down

In 4eb7a37, ProxiTok proxitok.privacydev.net (https://proxitok.privacydev.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ProxiTok proxitok.privacydev.net is back up in ebe3b38 after 1 hour, 17 minutes.


text:
🛑 librarian (discontinued) lbry.projectsegfau.lt is down

In 173af48, librarian (discontinued) lbry.projectsegfau.lt (https://lbry.projectsegfau.lt) was down:

HTTP code: 0
Response time: 0 ms

Resolved: librarian (discontinued) lbry.projectsegfau.lt is back up in 97e6df6.


text:
🛑 GotHub gothub.dev.projectsegfau.lt is down

In 9281fee, GotHub gothub.dev.projectsegfau.lt (https://gothub.dev.projectsegfau.lt) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GotHub gothub.dev.projectsegfau.lt is back up in 328be56 after 9 minutes.


text:
🛑 libreddit libreddit.privacydev.net is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 AnonymousOverflow overflow.ducks.party is down

In 61d11c1, AnonymousOverflow overflow.ducks.party (https://overflow.ducks.party) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnonymousOverflow overflow.ducks.party is back up in b64c549 after 11 minutes.


text:
lib/sorcery/initializers/initializer.rb  not found

Looking forward to using the gem, but didn't get past the 'bootstrap' step:
No such file or directory: ... /lib/sorcery/initializers/initializer.rb

It's now rails g sorcery:install.
See README.
On Sun, Oct 30, 2011 at 3:35 AM, Kyle Passarelli <
reply@reply.github.com>wrote:

Looking forward to using the gem, but didn't get past the 'bootstrap' step:
No such file or directory: ... /lib/sorcery/initializers/initializer.rb
--
Reply to this email directly or view it on GitHub:
https://github.com/NoamB/sorcery/issues/123

repo: NoamB/sorcery

license: mit

license_source: bigquery


text:
Hash Key appears to have expired

[2017-06-26 18:44:18][   ERROR][worker-15] 5T6A0V4S1X... appears to have expired.
Then it closes, but the hash key is fine and starting again works, is this an issue with bossland or the app?
Also the program should try again instead of quitting entirely.
5T6A0V4S1X... appears to have expired.
Exiting, please wait until all tasks finish
Finishing tasks...
Dumping pickles...ve, 0 DB items pending
Closing pipes, sessions, and event loop...
Done.
ubuntu@ubuntu-01:~/Monocle$
And thanks for the effort of making this app.

This is a bosslands problem sadly.
Verstuurd vanaf mijn iPhone

Op 26 jun. 2017 om 19:19 heeft Karlos007 notifications@github.com het volgende geschreven:
[2017-06-26 18:44:18][ ERROR][worker-15] 5T6A0V4S1X... appears to have expired.
Then it closes, but the hash key is fine and starting again works, is this an issue with bossland or the app?
Also the program should try again instead of quitting entirely.
And thanks for the effort of making this app.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I got this problem quit often as well. Sometimes it stops after a very short period of time, which is quite annoying. I am trying to comment out exit() in line 713 of workers.py and it should be able to retry.

I'm also trying this command to auto exec after crash
while true; do python3 scan.py; done

bossland issue, nothing we can do sadly

Didn't see this post and wrote #311 . The error details seems a bit different in windows.

repo: Noctem/Monocle


text:
Question: Do I need to put client.xreadgroup into a loop in order to get consumer group data?

Intuitively it seems that I shouldn't need to, but it's the only way I can get retrieval to work
Here's the code I came up with. But maybe you can correct me.
const redis = require('redis');
const client = redis.createClient();
const uuidv4 = require('uuid/v4');
const consumerId = uuidv4();

const streamName = process.env.BOMBARDIER_STREAM_NAME || 'BOMBARDIER';
const streamGroup = process.env.BOMBARDIER_CONSUMER_GROUP || 'BOMBARDIER_GROUP';

console.log(`Spinning up consumer ${consumerId} for stream ${streamName}`);

const timeout = setInterval(function () {
    client.xreadgroup('GROUP', streamGroup, consumerId, 'BLOCK', 1000, 'COUNT', 1, 'NOACK',
        'STREAMS', streamName, '>', function (err, stream) {
            if (err) {
                return console.error(err);
            }
            console.log(JSON.stringify({consumerId, stream}));
        });

}, 1000);

I use the same approach, not sure it is the best but it does the job.

Thank you, tgrall

@reselbob The interval is a weird solution (and error prone - JS timers / intervals are not precise - GC pauses and all). I tend to use async.js forever and just pass next in the callback.

Something like this I guess: (thanks @stockholmux for the hint)
async.forever(
    function(next) {
       redisClient.xreadgroup('GROUP', APPLICATION_ID,  CONSUMER_ID , 'BLOCK', 1000, 'COUNT', 10, 'NOACK', 'STREAMS', STREAMS_KEY, '>', function (err, stream) {
            if (err) {
                console.error(err);
                next();
            }
            console.log(JSON.stringify({ CONSUMER_ID : stream}));
            next();
        });

    },
    function(err) {
        // if next is called with a value in its first parameter, it will appear
        // in here as 'err', and execution will stop.
    }
);

@tgrall Correct, with a tweak. To get the error handling correct you'll need to do something like if (err) { next(err); } which will push it down to the second callback and break out of forever loop.

I'm going to go ahead and close this issue since it's not a problem with the module itself, but please proceed to work out the solution in the closed issue.

Thank you all.

authors: reselbob stockholmux tgrall


text:
Difference between two payloads (new API)

Hello 👋
The goal of the feature is to compare two scanner payloads (one older and one recent) and get informations and delta between them. A feature like this could be very useful in a tool like CI.
For example, to find out if new licences have appeared in between. But we can apply this principle to several other elements:

New maintainers (or some has been removed since).
New dependencies added

To date I do not know what would be the ideal approach to develop this feature. Do not hesitate to give ideas!

Pretty interesting. However,  do I get the old payload to compare with the new I requested?

@tekeuange23 payload are basically just JSON

@fraxken it is assumed that the new api we're creating (I've called it between) has to take two packageName as entries
But since the between is between two versions of the same package, shouldn't we take in two version entries instead

Looking into it

authors: fraxken jean-michelet tekeuange23

repo: NodeSecure/scanner


text:
Question: Is this compatible with Gatsby JS?

I'm trying to use it with Gatsby JS ?

But I have encountered an error.

@drailanjohngss Brother, I don't know because I'm not familiar with gatsby :(

authors: NomanGul drailanjohngss

repo: NomanGul/react-page-progress


text:
Version 4.5.1 is still unable to adapt to swift 5.1

I've upgraded from Carthage to version 4.5.1, but I still can't run swift 5.1 to warn of errors.

I've upgraded from Carthage to version 4.5.1, but I still can't run swift 5.1 to warn of errors.

We'll update dfu library soon.

Hey Philips,
Any ETA on the iOS DFU library update ?
Thanks.

Isn't Carthage compiled on your machine? Shouldn't you just call carthage update command and drag new binaries from Carthage/Build/?
See: https://github.com/Carthage/Carthage

Have a look at: https://stackoverflow.com/a/58621404

@DevAndArtist, could you help here? The version 4.5.1 works for you with Carthage.

I don't exactly know what's wrong here, you could check if you use correct Xcode in case if you have multiple versions. The error messages seems to indicate that you compile with an older version of Xcode.
https://stackoverflow.com/a/37868983
Also which Carthage version do you use? (Update it if it's outdated.)

Thanks! @haiztao @had23j you may also check out the first comment on the link above: https://stackoverflow.com/questions/37867753/change-carthage-swift-version/37868983#comment78202856_37868983 (this is if you don't want to play with console).

Thanks! @haiztao @had23j you may also check out the first comment on the link above: https://stackoverflow.com/questions/37867753/change-carthage-swift-version/37868983#comment78202856_37868983 (this is if you don't want to play with console).

@philips77 Hi philips77 Have you tried to update to Xcode 11 and swift 5.1.See if it fits

Yes, I'm using Xcode 11 and Swift 5.1.

I just released 4.6.0, which is developed in Xcode 11 with Swift 5.1.


text:
Missing

Heyo!
Can you add this to the documentation please?
Over API 30, you need to add this to your <manifest> in case you want it to work.
<queries>
	<package android:name="no.nordicsemi.android.log" />
</queries>

It would save time for others possibly!
Thanks!
David

@ #

</queries

<package android:name="no.nordicsemi.android.log" />

``

¡Oye!
¿Puedes agregar esto a la documentación, por favor? A través de API 30, debes agregar esto a tu <manifest>en caso de que quieras que funcione.
<queries>
	<package android:name="no.nordicsemi.android.log" />
</queries>

¡Posiblemente ahorraría tiempo a otros! ¡Gracias! David

Listo :)

Hola yo no entiendo nada de programacion alguienme hackea ymwdesordenatodo mi cell programativo mehacenver mal que extoyencontra la ley amanera queel govierno vea que yo extoyfaltando las letes de ezte pais y yonose nadade eso como hacerlo si me edadoc7enta quelos certicados de acceso al neyworka sido borrado y muchas cosas mad queyonos4como ponerlasb8em     On Wednesday, November 22, 2023 at 01:14:47 a.m. MST, David Azamar @.***> wrote:
¡Oye!
¿Puedes agregar esto a la documentación, por favor? A través de API 30, debes agregar esto a tu en caso de que quieras que funcione.

¡Posiblemente ahorraría tiempo a otros! ¡Gracias! David
Listo :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

repo: NordicSemiconductor/nRF-Logger-API


text:
关于访问其他请求返回500错误的问题

样例客户端在samples文件夹下，直接启动，浏览器配置文件下的http://127.0.0.1:8082/foo/bar，进入登录页，输入用户名user和密码user即可 这一步是没问题的
但是如果请求其他请求，例如 http://127.0.0.1:8082/ 进入登录界面，输入用户名密码 就会跳转到500错误页面

@ebdmn  请详细描述你的流程

这个重定向uri 其实是有逻辑处理的是吧？不仅仅是简单的一个重定向，而是授权成功的一个逻辑处理

@ebdmn http://127.0.0.1:8082/ 并不是合法的重定向uri ，参考项目中的dml.sql。非法的重定向uri参与的授权是不被接受的，不知道这样说你明白了没有？

这个重定向uri 其实是有逻辑处理的是吧？不仅仅是简单的一个重定向，而是授权成功的一个逻辑处理

@ebdmn http://127.0.0.1:8082/ 并不是合法的重定向uri ，参考项目中的dml.sql。非法的重定向uri参与的授权是不被接受的，不知道这样说你明白了没有？

这个重定向uri 其实是有逻辑处理的是吧？不仅仅是简单的一个重定向，而是授权成功的一个逻辑处理

localhost 不是合法的oauth2 host和逻辑无关，相关说明在rfc6749，这个问题没有继续深究的价值


text:
Color is not changing

Hello,
The project is not working since today 16-Feb-2023
I have been using this from a long ago.
I have refreshed the token, restarted the script ...
But it's not working.
There isn't any error in the logs.

Can you help ?
Regards,
Lionel

Hello, what you noticed was a planned outage on twitch's part.
Twitch will be permanently shutting down the IRC chat commands by 24 February 2023 (5 days from now). What this means is that this script will stop working. They announced this back in September 2022.
This script won't work after 24 Feb 2023, because twitch.

I personally don't have any reason to update this script to the new APIs and I will feel that would probably be a hassle. I will put a clear warning on the project page that the script no longer works.
Read more about twitch's decision to remove these chat commands here: https://discuss.dev.twitch.tv/t/deprecation-of-chat-commands-through-irc/40486
I'll be leaving this issue open for anyone to find it, because I won't be fixing this issue. It seems all those rainbow chatters i see sometimes in forsens chat won't be rainbow anymore :P too bad i guess.

My take on it is the same as the comment by Mm2pl from September when this was announced:

This is outrageous. It breaks basically
ALL
apps dealing with IRC, the migration path is suck up the rate limits and use helix? It also removes the only sensible way for (at least some) 3p users to whisper: /w. The requirements to even use this feature are outright stupid. I’ll be honest: I find it suspicious how Twitch suddenly pushed phone number verification, just like there is something to earn there, I do not trust this company. A whole 163 days to rewrite any functionality dealing with this shit or just delete your app and have it be over with. Open a new connection, wait for tls, send a json and then decode one back instead of using the already existing long-running connection? And what for? Just messing with third party developers because you can? Someone abusing IRC commands, executing hundreds and hundreds of /mods, /vips or what ever? Those people will be the first to abuse your first party graphql or just use fuck ton of selenium browsers to do the same and probably have better rate limits than helix.
Developing for this platform is for masochists. Oops now your app that relied on behavior that existed for YEARS AND YEARS and has been documented is broken, suck it up. Like how fucking stupid is that.

repo: NotNotQuinn/twitch-chat-colorchanger


text:
[BUG] Example for React project not current for 4.0.0 for createFragmentContainer syntax.

Describe the bug
Using BabelPluginRelay, introspectionQuery.tsx yields the error:
Error: babel-plugin-relay/macro: BabelPluginRelay: Expected exactly one definition per graphql tag. Learn more: https://www.npmjs.com/package/babel-plugin-relay
    at Array.forEach (<anonymous>)
    at Array.forEach (<anonymous>)

introspectionQuery.tsx
Maybe update to implement createFragmentContainer() syntax for fragments.
To Reproduce
Use declared introspection query with babel-plugin-relay/macro.
Encounter above error.
Expected behavior
Not encountering above error.
Package
react
Additional context
See:
BabelPluginRelay Error in 4.0
and
Breaking change
Caveat
I'm just getting my feet wet with React, and it is entirely possible I'm completely misunderstanding what's going on here. ::cha-grin:: If that's the case, please gently slap me and move on with your day. :)

I've worked around this issue by doing the following (this'll be long, apologies in advance):
const IntrospectionQuery = graphql`
  query IntrospectionQuery {
      __schema {
      queryType {
        name
      }
      mutationType {
        name
      }
      subscriptionType {
        name
      }
      types {
        kind
        name
        description
        fields(includeDeprecated: true) {
          name
          description
          args {
            name
            description
            type {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                        ofType {
                          kind
                          name
                          ofType {
                            kind
                            name
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
            defaultValue
          }
          type {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                        ofType {
                          kind
                          name
                        }
                      }
                    }
                  }
                }
              }
            }
          }
          isDeprecated
          deprecationReason
        }
        inputFields {
          name
          description
          type {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                        ofType {
                          kind
                          name
                        }
                      }
                    }
                  }
                }
              }
            }
          }
          defaultValue
        }
        interfaces {
          kind
          name
          ofType {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                      }
                    }
                  }
                }
              }
            }
          }
        }
        enumValues(includeDeprecated: true) {
          name
          description
          isDeprecated
          deprecationReason
        }
        possibleTypes {
          kind
          name
          ofType {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
      directives {
        name
        description
        locations
        args {
          name
          description
          type {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                        ofType {
                          kind
                          name
                        }
                      }
                    }
                  }
                }
              }
            }
          }
          defaultValue
        }
      }
    }
  }
`

But yeah, Yay fragments!

Hey @changeling,
Is this issue resolved for you now or is additional work necessary?
Thanks!

Hey, @rohit-ravikoti,
Has something changed in the code? I was able to work around it, as mentioned above, by explicitly stating the entire introspectionQuery, sans fragments, but would love to see it working as presented in https://github.com/Novvum/graphql-birdseye/blob/master/example/src/utils/introspectionQuery.tsx.
The last commit I see shows as 21 days ago, so I haven't tried. Is there something changed that I'm missing?

Hey @changeling,
No, there haven't been any changes since that last commit. That's really strange.

I used the entire query as a JSON import, which works fine, bypassing the  use of introspectionQuery.tsx. Is there something you'd like me to try to figure this out, or just let it go?

Please reopen if this becomes an issue.

authors: changeling rohit-ravikoti

repo: Novvum/graphql-birdseye


text:
1.21?

Is 1.21.x planned? Would love to use this mod on my survival server.

Sorry for the late response, but a 1.21 version is planned. As of now I'm focusing on updating other mods though. And with the new data-driven enchantment change it's a lot harder to implement some features

I'll keep an eye out for it then, thank you.

repo: Now-this-is-crazy/TridentFix


text:
NuGet.org allows all images, including badges, from the following trusted domains to be rendered (but doesn't)

this page indicates that the following domains are allowed including travis-ci, except the travis-ci domain listed on that pages is api.travis-ci.<org/com> but the images used for the build status badges are not api.travis-ci.com but simply travis-ci.com which means nuget blocks the badge on any documentation package readme's (including mine as shown below).
Image from github readme.md

image on nuget which should be pulling from github readme.md but has travis-ci build image blocked

@nullfx Thank you for providing more information. api.travis-ci.<org/com> are supported early with badge.
Example:
Thanks for pointing out that they also support travis-ci.com.  We will update to travis-ci.org/com to support more scenarios.

has this been pushed to production yet? guessing not since nuget.org still not showing the build status for travis-ci.org while trying to update documentation pointing to readme with https://travis-ci.org as the badge source for "build status" which also doesn't show up on the main website:

It would work. please let me know if you have further questions.

brilliant. it wasn't showing up earlier. that was when i went to try and update the documentation (and saw what I just posted) but its showing now. thanks.

authors: lyndaidaii nullfx

repo: NuGet/NuGetGallery


text:
[Organizations] Link empty Manage Organizations page to the Transform flow

https://github.com/NuGet/NuGetGallery/issues/5691
Also some small UI fixes to the transform page
Manage organizations page:

Transform page:

@anangaur let me know what you think would look better on the page

First of all. Not related to this but the breadcrumb looks weird. Too big. The arrow needs to change from the > to another icon.
As for the transform option, we need 3 things:

The transform option should not be a button but a linked button:

There needs to be a confirm dialog as this is an irreversible process:

There needs to a small fix on the transform page:

@anangaur what is the change on 3? I don't see anything different

@anangaur regarding 2, I'm also concerned that the text you have provided will scare users into thinking that the "transform this account into an organization" button actually performs the transformation. I think the text you're proposing would be better off on the transform form page itself.

Looks like I added wrong picture for 3. Will add the right one soon.
For 2, I am fine with your suggestion. Can you make this a warning banner on the transform page at the top itself?

@anangaur I have updated this PR and the screenshots. Any thoughts?

@anangaur see updated screenshot

Some fixes required:

Left align the breadcrumb
Remove the account name
Increase the spacing/padding between the warning and the rest of the contents.

The warning seems too big but i do not have any better suggestion as of now. Lets see if people have better inputs in tomorrow' bugbash.

@anangaur see updated screenshot

per @anangaur feedback to apply before merging: increase margin between breadcrumb and image in empty page

authors: anangaur scottbommarito


text:
Added the missing command line options.

follows #324

ReportMode is probably going to be reworked entirely as an output format. But we can keep it for now.

authors: AnthonySteele skolima

repo: NuKeeperDotNet/NuKeeper


text:
GLIBC 2.32 ISSUE

./BB.dist/BB: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./BB.dist/BB)
nuitka3 --standalone --onfile BB.py, copied .dist to another PC and ran

@Maxwell175 python3 -m nuitka --version
0.8.4
Commercial: None
Python: 3.10.4 (main, Mar 24 2022, 13:07:27) [GCC 11.2.0]
Flavor: Debian Python
Executable: /usr/bin/python3
OS: Linux
Arch: x86_64
Distribution: Kali (based on Debian) 2022.2

actually gcc is 12.0
gcc --version
gcc (Debian 12.1.0-2) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

How can i install glibc 2.32 in my computer then compile bb then move to another computer to run that program

@Maxwell175 @kayhayen

Standalone does not allow you to run new Linux software on old Linux, only the other way around. In Nuitka commercial there is a container build, not advertised well, but still, that can produce on new Linux binaries that do work on things as old as Fedora 19, but you either do this yourself or go here:
https://nuitka.net/doc/commercial.html

authors: kayhayen machineydv

repo: Nuitka/Nuitka


text:
Server Migration / Portability Question. Not related to Script

@Nyr - Now that you’ve helped me create 50+ OpenVPN clients for employees in a jiffy (THANKS!), I want to take our installation one step further and ensure that the need to re-create and more importantly, re-distribute, clients is not faced anytime soon.
Currently our OpenVPN setup works off udp/1194 on a physical server with a static public IP, and it’s in daily use by employees to connect back to the office network to access a secure database. Superb speed, instant access, highly secure, and with no passwords to remember. Everyone loves it.
Ideally, I’d like to setup and keep in reserve a second server with a different IP but identical certs/keys/clients, so that if the physical server was to ever go down (power, bad drive), I could simply bring the virtual server online, change the NAT to point to it, install available updates, and we’re back in business in literally minutes without needing to notify and email a new VPN client again to 50 different folks.
This would be easier if we were running VSphere, so I could simply restore a backup of the primary virtual server to another host via Veeam if disaster struck, but budgets are tight.
Is that even doable without cloning (using Acronis or clonezilla)? Many thanks for any/all advise.

Please, avoid opening further issues seeking general support. I suggest the OpenVPN forums for that, this is not the right place.
That said, in your case it is way easier than you think:

You can configure clients for failover with multiple server IP addresses. That way you could have zero downtime if required.
Alternatively, and if the secondary server needs to have a different, unknown at this time, IP address, you should use domain name(s).
Once you have that done, just backup the server configuration from /etc/openvpn. That will include all the needed certificate stuff. When setting up a new server, you can just restore the backed up configuration and certificates.

Understood. Apologies for posting this query under Issues.
Will try out your suggestion on restoring /etc/openvpn on another server.

authors: Nyr wicknet

repo: Nyr/openvpn-install


text:
A few tiny fixes

Thanks for continuing work on this again.
I'm not experienced with Github and PR flow so I'm sorry for not making feedback earlier.
Glad to see some of my fixes has merged in master. I reorganize my local commits and rebase them on the new upstream, and there are a few tiny fixes on this that are reasonable in my view.

There're some contents not fully merged in file project.pbxproj.

On macOS 'KB' means kilobyte(10^3) while 'KiB' means kibibyte(2^10, short for kilo binary byte). Similar for MiB and GiB.

On resolution display, FAR (proportion of number of pixels) is needed, and when the pixel is not square (SAR≠1:1), it should be noted, in my opinion.

Judging pixel bit depth doesn't depend on profile any more.

It's my first PR. If some other info or commit are needed just let me know plz. Thanks.

Thanks


text:
Show info, warn, error by default

Show info, warn, and error logs by default

This looks like a great start, but there are still a lot of console.log calls left.

There are so many console.log calls. I could not fix them all

Can we do a massive sed to replace all console.log -> trace, console.error -> error, etc?

We could do that, but I would probably replace them manually because console.log sometimes makes more sense than info or trace, e.g., when printing usage info.

I agree sometimes you do want console calls but I don't think we want any in our oada services. none of them print use info or anything. I like @abalmos idea, except everyone only used console.log even for errors and warnings which we would not want to just stick in trace.

I have replaced most of console.log calls in da12f6c

This looks good and would be useful to have. There is more that needs to be done, but merging this effort.

Thanks

authors: abalmos awlayton tomohiroarakawa

repo: OADA/oada-srvc-docker


text:
[WIP] Metadata handling

Add frontmatter and config file handling  …

Move ResultSet and ResultFormatter subclass mappings to global config
Allow backend database to be specified in frontmatter, config, or envar
ResultSet classes take a Query class that holds query body and metadata attributes
Handle ResultSet dispatching in QueryBroker class (renamed from former Query class to use that name for actual Query instances)
Parse out frontmatter from query files in QueryBroker, and add to Query object
Pass through frontmatter metadata to formatter classes

Currently no formatter uses frontmatter yet
Will support arbitrary key-value metadata to describe results to clients
Can use frontmatter to specify database backend per query file in this release

Codecov Report

Merging #34 into master will decrease coverage by 4.92%.
The diff coverage is 76.92%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
- Coverage   89.42%   84.49%   -4.93%
==========================================
  Files          10       11       +1
  Lines         208      258      +50
==========================================
+ Hits          186      218      +32
- Misses         22       40      +18

Impacted Files
Coverage Δ

nerium/contrib/formatter/csv.py
100% <100%> (ø)
:arrow_up:

nerium/contrib/formatter/affix.py
100% <100%> (ø)
:arrow_up:

nerium/contrib/formatter/sum.py
100% <100%> (ø)
:arrow_up:

nerium/contrib/formatter/compact.py
100% <100%> (ø)
:arrow_up:

nerium/utils.py
55.55% <55.55%> (ø)

nerium/main.py
77.87% <72.72%> (-11.52%)
:arrow_down:

nerium/contrib/resultset/sql.py
86.66% <88.88%> (-2.81%)
:arrow_down:

nerium/app.py
81.63% <92.85%> (+7.12%)
:arrow_up:

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 53740ea...4a87aa2. Read the comment docs.

I updated some stuff for jinjasql to make it conform to the new style, and then it ran for the first time after updating that and making sure the test config was setup correctly. Next push after that the tests failed again. 😕

authors: codecov-io henryrizzi tym-oao

repo: OAODEV/nerium


text:
Table Selection Should Initiate Radio Button on Method Selection for Save

When selecting a method in the save dialog, if a user selects a method from the table of existing methods, this should cause the associated radio button to be selected.

Before merging to master, please make sure that the connection is good to MSSQL- it is not working in this branch.
This is addressed. Closing issue and merging pull request.


text:
glibc / libc6 version conflict with jetpack 4.4 image

Describe the bug, or it's more like a problem I have
I'm using a customized Xavier board which is based on jetpack 4.4 and some private BSP for Canbus ports.
Since the private BSP is not open sources, I'm using Yocto and meta-tegra to build a complete rootfs/image but I don't use it as a whole. On the contrary, I manually copy the deploy *.deb files to my board and install them, at least it's my current plan.
I built an app.deb, during the sudo apt install, I found it depends on libc6.
Depends: libc6 (>= 2.31+git0+df31c7ca92) but 2.27-3ubuntu1 is to be installed

From this message, it says libc6 2.27 is the current version as in Jetpack 4.4, bud in my Yocto and meta-tegra (dunfell-r32.4.3 branch), it builds libc6_2.31.
At first, I didn't hesitate but forced to install the deployed libc_2.31.deb file, the result were many warnings and actually an error in the end.
Then I read something and thought I'd better not to upgrade libc.
Here is my question:
In my app, I don't write specific code to use libc 2.31 and I think it should work with libc 2.27, how can I remove this version requirement?
I can also copy the recipe of glibc 2.27 (https://layers.openembedded.org/layerindex/recipe/80771/) and set PREFERRED_VERSION_glibc = 2.27, then in my meta-tegra image, it use libc 2.27 anywhere.
Which way should I go?
Thanks.

I did some test but failed, it seems that I need to use gcc 7.3 (which is same as in default jetpack 4.4), but gcc 7.3 only exists in yocto sumo branch.
Maybe I have gone too far in the wrong direction?

Hey @fei4xu ,
related to the GCC part please check the wiki page am I right you wanna build the app and some tools with the YOCTO layer but run them on the Nvidia L4T Ubuntu based image?


text:
ConfigPoint theme doesn't respect PUBLIC_URL

theme.json5 doesn't respect PUBLIC_URL
Bug description
Theme url is hardcoded and doesn't reflect PUBLIC_URL change
Repro

Set PUBLIC_URL environment variable and run yarn build
Load the viewer
Observe everything works except for the theme.json5 load since it is hardcoded to /theme/theme/json5

ConfigPoint.load(defaultTheme, '/theme', 'theme');

config point is removed from the application. Please re-try again on master and re-open the issue if necessary

repo: OHIF/Viewers


text:
Add orthanc in docker compose

app.json of docker-compose anyway is orthanc specific. Might as well include orthanc in docker compose. Also added instructions to run the viewer using docker compose in readme.

https://docs.ohif.org/deployment/recipes/nginx--image-archive.html
Our latest, version 2.x, has docker support for use with Orthanc locally (with appropriate CORS headers), or alongside a container that has our WebApp in it.

authors: chsasank dannyrb


text:
Quadratic equation example prints NaNs

Should I treat it as no solution?
Inform a: 3
Inform b: -5
Inform c: 8
Calculating x' and x''
x' NaN, x'' NaN

Yes, there's an error in the Vaca code. I'm calculating
#(delta (brt (- (* b b) (* 4 (* a c) )) 2))

Which is wrong, the square root should only be calculated after checking if the inner expression is positive
It's the first Vaca logic error rather than in the interpreter
But this remainds me of adding some NaN treatment
I'll fix the example in a latter update

I think taking a square root of a negative number should be a runtime error.

ATM i added a value NaN, but i may turn it into an Error

authors: OJarrisonn vtereshkov

repo: OJarrisonn/vaca


text:
How to refactor source code via IR？

Hello, author
I want to know how to perform inorder traversal on the IR program to reconstruct the original source program? Where is the corresponding code？

https://github.com/OMH4ck/PolyGlot/blob/7162dbc78f24ee3cc6ed019ef42a0cd913815e47/srcs/internal/srcs/ir.cpp#L119

您好，您的文件我已收到！

authors: Changochen HopeDevote


text:
Remove expects from middle of tests

What is the context of this PR?
Remove interim expects from middle of functional tests which serve no purpose. Currently one such expect is unnecessarily testing an age.
How to review
Check the tests continue to pass.

 Bug: Functional test failure due to date based test

repo: ONSdigital/eq-questionnaire-runner


text:
Ability to have question definitions

What is the context of this PR?
Implements question definitions.
Card for context. To match Will's design, you need to update runner to pattern lib v1.4.1
How to review

Ensure definitions look and behave as expected.

Also, master needs to be merged into this branch

@nealedj That's because I've raised this PR on v1.2.0 as #1624 has not gone in yet. If you change it to v1.4.1 you should get the orange outline.

https://github.com/ONSdigital/eq-schema-validator/pull/58 PR needs to go in first before this can be merged.

authors: MebinAbraham insacuri

repo: ONSdigital/eq-survey-runner


text:
Removed repeated survey path from manual outlier and manual trimming …

Parts of the path were repeated. Removed the repetition.
Insert detailed bullet points about your changes here!
Insert any instructions to help the reviewer, e.g. "install new requirements from requirements.txt"
*Let the reviewer know what data files are needed (and if applicable, where they are to be found)
Closes or fixes

Detail the ticket(s) you are closing with this PR
Closes #

Code

[ ] Code runs The code runs on my machine and/or CDSW
[ ] Conflicts resolved There are no conflicts (I have performed a rebase if necessary)
[ ] Requirements My/our code functions according to the requirements of the ticket
[ ] Dependencies I have updated the environment yaml so it includes any new libraries I have used
[ ] Configuration file updated any high level parameters that the user may interact with have been put into the config file (and imported to the script)
[ ] Clean Code

[ ] Code is as PEP 8 compliant as I can humanly make it
[ ] Code passess flake8 linting check
[ ] Code adheres to DRY

[ ] Type hints All new functions have type hints

Documentation
Any new code includes all the following forms of documentation:

[ ] Function Documentation Docstrings within the function(s')/methods have been created

[ ] Includes Args and returns for all major functions
[ ] The docstring details data types

[ ] Updated Documentation: User and/or developer working doc has been updated

Data

[ ] All data needed to run this script is available in Dev/Test
[ ] All data is excluded from this pull request
[ ] Secrets checker pre-commit passes

Testing

[ ] Unit tests Unit tests have been created and are passing or a new ticket to create tests has been created

Peer Review Section

[ ] All requirements install from (updated) requirements.txt
[ ] Documentation has been created and is clear - check the working document
[ ] Doctrings (Google format) have been created and accurately describe the function's functionality
[ ] Unit tests pass, or if not present a new ticket to create tests has been created
[ ] Code runs The code runs on reviewer's machine and/or CDSW

Final approval (post-review)
The author has responded to my review and made changes to my satisfaction.

[ ] I recommend merging this request.

Review comments
Insert detailed comments here!
These might include, but not exclusively:

bugs that need fixing (does it work as expected? and does it work with other code
that it is likely to interact with?)
alternative methods (could it be written more efficiently or with more clarity?)
documentation improvements (does the documentation reflect how the code actually works?)
additional tests that should be implemented (do the tests effectively assure that it
works correctly?)
code style improvements (could the code be written more clearly?)
Do the changes represent a change in functionality so the version number should increase? Start a discussion if so.
As a review you can generates the same outputs from running the code

Your suggestions should be tailored to the code that you are reviewing.
Be critical and clear, but not mean. Ask questions and set actions.

Hi @zorge69 - this isn't showing any changes now?

These changes weren't needed - the error in the Prod environment would be that the full paths instead of reduced paths were included.

authors: AnneONS JenCheshire zorge69

repo: ONSdigital/research-and-development


text:
Us102 create collection exercise

This PR allows for a user to create a new collection exercise with validation to ensure that a period cannot be entered if it already exists for a collection exercise for that survey.
Also added in missing validation for editing a collection exercise so that a user cannot change the period to one that already exists
BACKSTAGE coming for this code too

 US102: INT User to Create a CE - After R17/18 (M)

Codecov Report

Merging #140 into master will increase coverage by 0.17%.
The diff coverage is 96%.

@@            Coverage Diff             @@
##           master     #140      +/-   ##
==========================================
+ Coverage   95.21%   95.38%   +0.17%
==========================================
  Files          34       34
  Lines        1254     1323      +69
==========================================
+ Hits         1194     1262      +68
- Misses         60       61       +1

Impacted Files
Coverage Δ

response_operations_ui/forms.py
100% <100%> (+1.75%)
:arrow_up:

...esponse_operations_ui/views/collection_exercise.py
97% <100%> (+0.43%)
:arrow_up:

response_operations_ui/views/surveys.py
100% <100%> (+4.87%)
:arrow_up:

..._ui/controllers/collection_exercise_controllers.py
81.03% <85%> (-0.55%)
:arrow_down:

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 0e2b966...356f1a8. Read the comment docs.

authors: codecov-io emilioward

repo: ONSdigital/response-operations-ui


text:
test PR with Github API

Please pull this in!

Docs Build status updates of commit 4ec2d36:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

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

Docs Build status updates of commit bf5c76a:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

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

Docs Build status updates of commit 73b930b:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

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


text:
DocsArchive-1.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_67380bef-e41e-47c1-8513-ad925d67f320/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_67380bef-e41e-47c1-8513-ad925d67f320.git

Docs Build status updates of commit c4918b6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-07-16-00-45 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-11-07-16-00-45

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

authors: VSC-Service-Account v-alji


text:
DocsArchive-1.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_a50c38bd-fe77-41c1-b26b-dc35b3607171/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_a50c38bd-fe77-41c1-b26b-dc35b3607171.git

Docs Build status updates of commit 0e4ab08:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-29-13-14-56 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-29-13-14-56

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


text:
DocsArchive-15.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/362 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit d423923:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

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


text:
Clean up

Rename BBox to Box and add ETI to details. Should we rename all the files in details as DTK_DetailsXXX?

Codecov Report

Merging #220 into master will not change coverage.
The diff coverage is 96.66%.

@@           Coverage Diff           @@
##           master     #220   +/-   ##
=======================================
  Coverage   97.34%   97.34%
=======================================
  Files          42       42
  Lines        1960     1960
=======================================
  Hits         1908     1908
  Misses         52       52

Impacted Files
Coverage Δ

packages/Search/src/DTK_LinearBVH_decl.hpp
100% <ø> (ø)
:arrow_up:

packages/Search/src/details/DTK_Node.hpp
100% <ø> (ø)

...s/Search/src/details/DTK_TreeConstruction_decl.hpp
100% <ø> (ø)

packages/Search/src/details/DTK_Point.hpp
100% <ø> (ø)

...es/Search/src/details/DTK_TreeConstruction_def.hpp
98.23% <ø> (ø)

packages/Search/test/tstDetailsAlgorithms.cpp
100% <100%> (ø)
:arrow_up:

...kages/Search/src/details/DTK_DetailsAlgorithms.cpp
100% <100%> (ø)
:arrow_up:

packages/Search/src/DTK_LinearBVH_def.hpp
100% <100%> (ø)
:arrow_up:

packages/Search/src/details/DTK_Box.hpp
84.21% <100%> (ø)

...ackages/Search/test/tstDetailsTreeConstruction.cpp
100% <100%> (ø)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

A lot of the redundancy that we have in the files is actually required by Tribits. I have removed everything that is not necessary in the cmake.

Should DTK_ETI_SC_LO_GO_NT.tmpl and the corresponding CMake code be removed? We don't template anything on LO and GO anyway.

yes I think we should remove that file

OK done

Related to #217.

authors: Rombur aprokop codecov-io sslattery

repo: ORNL-CEES/DataTransferKit


text:
[WIP] Add compactly supported radial basis functions

Addressing #282

Codecov Report

Merging #290 into master will increase coverage by 0.06%.
The diff coverage is 98.33%.

@@            Coverage Diff             @@
##           master     #290      +/-   ##
==========================================
+ Coverage   95.05%   95.11%   +0.06%
==========================================
  Files          55       58       +3
  Lines        3071     3131      +60
==========================================
+ Hits         2919     2978      +59
- Misses        152      153       +1

Impacted Files
Coverage Δ

packages/Operators/test/unit_test_main.cpp
100% <100%> (ø)

...src/DTK_CompactlySupportedRadialBasisFunctions.hpp
100% <100%> (ø)

packages/Operators/test/tstInterpolation.cpp
96.96% <96.96%> (ø)

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 1c47f02...ae2c243. Read the comment docs.

I rebased onto master and moved everything to the new "Meshfree" package.
I think it is ready for merge.


text:
Look/install saamge

We should look/try to install saamge since it is the only mpi implementation of spectral amge. Hypre contains a serial implementation of spectral amge.

The easiest way to install would probably be to create a Spack package.

authors: Rombur aprokop

repo: ORNL-CEES/mfmg


text:
AlgorithmGenerator to IRGenerator, and specify input parameters

AlgorithmGenerator maybe should take as input an AcceleratorBuffer and a vector of InstructionParameters

This issue was moved to eclipse/xacc#7

repo: ORNL-QCI/xacc


text:
Segmentation fault 11

After compiling the latest version I ran and got this output:
"[OSVR Server] Using config file 'Test.json'
[OSVR Server] Constructing server as configured...
[OSVR Server] Loading auto-loadable plugins...
Segmentation fault: 11"
EDIT: I'm on a mac

Sorry, without additional details this is hard to diagnose. What platform is this on (Mac? Linux? What distribution? What processor architecture? Etc)? Try rebuilding in RelWithDebInfo mode and getting a back trace with symbols if it crashes (run in gdb, command bt after segfault) and posting that here as well, since that will hopefully pinpoint what exactly is segfaulting - the messages shown don't narrow it down much right now.

Ah, on a Mac, this is likely to be a dupe of #321 if you aren't using homebrew to build.

repo: OSVR/OSVR-Core


text:
systemd config need a new variable for --queue

Recommend:
--queue name
project-role-environment-worker|admin

closed by commit 8cf00ad

authors: jsnshrmn mbstacy

repo: OULibraries/ansible-role-celery-worker