text:
vokoscreen-ng: 4.0.0 -> 4.2.0

Description of changes
Feature and Bugfix-Release 4.2.0 from Jul 01, 2024
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Could you update this to 4.3.0?

Perhaps we should merge as it is, it's been a while it has been made

Thanks! Let's work on the bump now.

Thanks! Let's work on the bump now.

https://github.com/NixOS/nixpkgs/pull/360742 ^^

authors: Scrumplex dietmarw drupol


text:
Python package updates

Motivation for this change
Things done

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

[ ] NixOS
[ ] 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/)
[ ] Fits CONTRIBUTING.md.

https://hydra.nixos.org/jobset/nixpkgs/python-unstable

Please add https://github.com/dotlambda/nixpkgs/commit/130542eb860c274d6402bfb2279853f5df7d905c

I also updated typing: dotlambda/nixpkgs@fd753e1f107a58ce18c8827124417f2317482b41
I however had to disable tests for Python 3.6. I must say I can't really follow https://github.com/python/typing/pull/280 but typing should have any effect for Python 3.5 or later anyway.
Is there a way to add typing to buildInputs only for Python 3.4 and below? For example by making it null otherwise? This could however lead to unsatisfied requirements.

Is there a way to add typing to buildInputs only for Python 3.4 and below? For example by making it null otherwise? This could however lead to unsatisfied requirements.

buildInputs = [ ] ++ optionals pythonOlder "3.5" [ typing ];

Other solution we use mostly for backports:
typing = if pythonAtLeast "3.5" then null else buildPythonPackage rec { ... };

Wouldn't it make sense to remove all names in the updated derivations?

Feel free to create a commit that removes all of them. These updates are generated automatically.

I had already tried the second solution but that would cause packages requiring typing in their setup.py to fail to build. So I guess it is best left as is.

Don't you want to include the typing update?

@GrahamcOfBorg eval

(@grahamc vs @GrahamcOfBorg :laughing:  )

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘spyder-3.2.6’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/applications/science/spyder/default.nix:47 is not supported on ‘x86_64-darwin’, refusing to evaluate.

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.

Failure on x86_64-linux (full log)
Partial log (click to expand)
Requirement already satisfied: pylint in /nix/store/hg7z39d2ifi0i83njd4j4xswbsfdfkjf-python2.7-pylint-1.8.2/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: jedi>=0.9.0 in /nix/store/mzaj8hm6x9szwskh1z6gmm4vcl4bz3ik-python2.7-jedi-0.11.1/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: pycodestyle in /nix/store/47fniyjczd3nacnym72mya9i4w8kinkz-python2.7-pycodestyle-2.3.1/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: psutil in /nix/store/96ral8lnx118a1qccink2z2bhsmyg7ar-python2.7-psutil-5.4.3/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: nbconvert in /nix/store/18mqml1f4gb9ya5w2plxvkf56bds2hh1-python2.7-nbconvert-5.3.1/lib/python2.7/site-packages (from spyder==3.2.6)
Collecting pyopengl; platform_system == "Linux" (from spyder==3.2.6)
  Could not find a version that satisfies the requirement pyopengl; platform_system == "Linux" (from spyder==3.2.6) (from versions: )
No matching distribution found for pyopengl; platform_system == "Linux" (from spyder==3.2.6)
builder for ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’ failed with exit code 1
error: build of ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’ failed

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘spyder-3.2.6’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/applications/science/spyder/default.nix:47 is not supported on ‘x86_64-darwin’, refusing to evaluate.

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.

Failure on x86_64-linux (full log)
Partial log (click to expand)
Requirement already satisfied: pylint in /nix/store/hg7z39d2ifi0i83njd4j4xswbsfdfkjf-python2.7-pylint-1.8.2/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: jedi>=0.9.0 in /nix/store/mzaj8hm6x9szwskh1z6gmm4vcl4bz3ik-python2.7-jedi-0.11.1/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: pycodestyle in /nix/store/47fniyjczd3nacnym72mya9i4w8kinkz-python2.7-pycodestyle-2.3.1/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: psutil in /nix/store/96ral8lnx118a1qccink2z2bhsmyg7ar-python2.7-psutil-5.4.3/lib/python2.7/site-packages (from spyder==3.2.6)
Requirement already satisfied: nbconvert in /nix/store/18mqml1f4gb9ya5w2plxvkf56bds2hh1-python2.7-nbconvert-5.3.1/lib/python2.7/site-packages (from spyder==3.2.6)
Collecting pyopengl; platform_system == "Linux" (from spyder==3.2.6)
  Could not find a version that satisfies the requirement pyopengl; platform_system == "Linux" (from spyder==3.2.6) (from versions: )
No matching distribution found for pyopengl; platform_system == "Linux" (from spyder==3.2.6)
builder for ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’ failed with exit code 1
error: build of ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’ failed

Failure on x86_64-linux (full log)
Partial log (click to expand)
                         yyParenDepth--;
                         ^~~~~~~~~~~~
g++ -c -pipe -O2 -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DPy_LIMITED_API=0x03040000 -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_PLUGIN -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem /nix/store/w81d7rbysi0rmf9c47njqbxjnllqv9cq-python-2.7.14/include/python2.7 -I../qpy/pylupdate -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtXml -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtCore -I. -I/nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/mkspecs/linux-g++ -o metatranslator.o ../qpy/pylupdate/metatranslator.cpp
g++ -c -pipe -O2 -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DPy_LIMITED_API=0x03040000 -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_PLUGIN -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem /nix/store/w81d7rbysi0rmf9c47njqbxjnllqv9cq-python-2.7.14/include/python2.7 -I../qpy/pylupdate -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtXml -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtCore -I. -I/nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/mkspecs/linux-g++ -o numberh.o ../qpy/pylupdate/numberh.cpp
g++ -c -pipe -O2 -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DPy_LIMITED_API=0x03040000 -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_PLUGIN -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem /nix/store/w81d7rbysi0rmf9c47njqbxjnllqv9cq-python-2.7.14/include/python2.7 -I../qpy/pylupdate -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtXml -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtCore -I. -I/nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/mkspecs/linux-g++ -o proparser.o ../qpy/pylupdate/proparser.cpp
g++ -c -pipe -O2 -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DPy_LIMITED_API=0x03040000 -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_PLUGIN -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem /nix/store/w81d7rbysi0rmf9c47njqbxjnllqv9cq-python-2.7.14/include/python2.7 -I../qpy/pylupdate -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtXml -isystem /nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/include/QtCore -I. -I/nix/store/ibfm5z49nv2jvdcv4wk0p5d4pp8czk4f-qtbase-5.10.0-dev/mkspecs/linux-g++ -o sametexth.o ../qpy/pylupdate/sametexth.cpp
building of ‘/nix/store/nqg1b3h2dmvp7gr9zw1mf58il85flhrc-python2.7-PyQt-5.10.drv’ timed out after 1800 seconds
cannot build derivation ‘/nix/store/lr138a8lj9x8ajhxsvd0m3z3lghniac4-python2.7-qtconsole-4.3.1.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/xqwzwxz29ipxvf081sxd44qpxk4bfqgs-spyder-3.2.6.drv’ failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
[2967/21250] CXX obj/services/service_manager/public/cpp/cpp/service_runner.o
[2968/21250] ACTION //third_party/WebKit/Source/bindings/core/v8:generate_bindings_core_v8_interfaces(/build/qtwebengine-everywhere-src-5.10.0/src/toolchain:target)
[2969/21250] CXX obj/services/service_manager/public/cpp/cpp/service.o
[2970/21250] ACTION //third_party/WebKit/Source/bindings/core/v8:bindings_core_conditional_features(/build/qtwebengine-everywhere-src-5.10.0/src/toolchain:target)
[2971/21250] CXX obj/services/service_manager/public/cpp/standalone_service/standalone_service/linux_sandbox.o
building of '/nix/store/k1zx0cqlwfyqpap7igla25vvryfq6af3-qtwebengine-5.10.0.drv' timed out after 3200 seconds
cannot build derivation '/nix/store/c9a3yajs6qidn9xv32wf539bfx673nxf-python2.7-PyQt-5.10.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/71fzqc715hcfjilnlpw8fcpjdn5fkhkb-python2.7-qtconsole-4.3.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv': 9 dependencies couldn't be built
error: build of '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
[4934/21250] CXX obj/third_party/icu/bundled_icui18n/regeximp.o
[4935/21250] CC obj/third_party/libvpx/bundled_libvpx/idct32x32_34_add_neon.o
[4936/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/rdft.o
[4937/21250] CXX obj/third_party/libwebm/libwebm/mkvmuxer.o
[4938/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavformat_options.o
building of '/nix/store/k1zx0cqlwfyqpap7igla25vvryfq6af3-qtwebengine-5.10.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/c9a3yajs6qidn9xv32wf539bfx673nxf-python2.7-PyQt-5.10.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/71fzqc715hcfjilnlpw8fcpjdn5fkhkb-python2.7-qtconsole-4.3.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv': 9 dependencies couldn't be built
error: build of '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
[4930/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/flacdec.o
[4931/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/id3v1.o
[4932/21250] CXX obj/third_party/icu/bundled_icuuc/uhash_us.o
[4933/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/options.o
[4934/21250] CC obj/third_party/ffmpeg/ffmpeg_internal/rmsipr.o
building of '/nix/store/k1zx0cqlwfyqpap7igla25vvryfq6af3-qtwebengine-5.10.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/c9a3yajs6qidn9xv32wf539bfx673nxf-python2.7-PyQt-5.10.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/71fzqc715hcfjilnlpw8fcpjdn5fkhkb-python2.7-qtconsole-4.3.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv': 9 dependencies couldn't be built
error: build of '/nix/store/41fcq1sk2g0ppsvq13jls3jm5i4sqjam-spyder-3.2.6.drv' failed

source: gharchive/pull-request

authors: FRidh GrahamcOfBorg dotlambda grahamc

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
vimPlugins.focus-nvim: init at 2024-10-20

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 349981

x86_64-linux

:white_check_mark: 2 packages built:

vimPlugins.focus-nvim
vimPluginsUpdater

aarch64-linux

:white_check_mark: 2 packages built:

vimPlugins.focus-nvim
vimPluginsUpdater

x86_64-darwin

:white_check_mark: 2 packages built:

vimPlugins.focus-nvim
vimPluginsUpdater

aarch64-darwin

:white_check_mark: 2 packages built:

vimPlugins.focus-nvim
vimPluginsUpdater


text:
unifi8: 8.5.6 -> 8.6.9

Closes https://github.com/NixOS/nixpkgs/issues/355028
https://community.ui.com/releases/r/network/8.6.9

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 355029

x86_64-linux

:white_check_mark: 1 package built:

unifi

authors: devusb qubitnano


text:
t-rex: mark broken

t-rex: mark broken
Tracking issue: https://github.com/NixOS/nixpkgs/issues/355705
CC @NixOS/geospatial

Review @paparodeo ?

Would be good to mention that the breakage is due to Rust 1.80

You just said it. What is there to say?

Closing because a fix is known.


text:
python312Packages.homematicip: 1.1.3 -> 1.1.4

Diff: https://github.com/hahn-th/homematicip-rest-api/compare/refs/tags/1.1.3...1.1.4
Changelog: https://github.com/hahn-th/homematicip-rest-api/releases/tag/1.1.4

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362729

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.homematicip_cloud
python311Packages.homematicip
python311Packages.homematicip.dist
python312Packages.homematicip
python312Packages.homematicip.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362729

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.homematicip_cloud
python311Packages.homematicip
python311Packages.homematicip.dist
python312Packages.homematicip
python312Packages.homematicip.dist

authors: NickCao fabaff


text:
redocly: 1.25.11 -> 1.26.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/redocly/versions.
meta.description for redocly is: Makes OpenAPI easy. Lint/validate to any standard, generate beautiful docs, and more
meta.homepage for redocly is: https://github.com/Redocly/redocly-cli
meta.changelog for redocly is: https://redocly.com/docs/cli/changelog/
Updates performed

NPM version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.26.0 with grep in /nix/store/gmzv9mkcq5g8j729d75iqaz0makxhcxk-redocly-1.26.0
found 1.26.0 in filename of file in /nix/store/gmzv9mkcq5g8j729d75iqaz0makxhcxk-redocly-1.26.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

redocly

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/0ef1b4172ae75f15ed25483c35416a40dae57fcd#redocly

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

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

x86_64-linux

:white_check_mark: 1 package built:

redocly

Maintainer pings
cc @szlend for testing.

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

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

1 package built:
redocly
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365672

aarch64-darwin

:white_check_mark: 1 package built:

redocly

authors: r-ryantm szlend


text:
pony-stable: 0.1.1 -> 0.1.2

Motivation for this change
Version bump.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg  build pony-stable

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: pony-stable
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.

Failure on x86_64-linux (full log)
Attempted: pony-stable
Partial log (click to expand)
/build/source/stable/main.pony:85:63: can't reference a method without calling it
          ["env"; "PONYPATH=" + ponypath] .> append(rest), env.exitcode)?
                                                              ^
Error:
/build/source/stable/main.pony:85:60: argument not a subtype of parameter
          ["env"; "PONYPATH=" + ponypath] .> append(rest), env.exitcode)?
                                                           ^
make: *** [Makefile:41: build/release/stable] Error 255
builder for '/nix/store/k47cksmn41yipn9vsp8g53cmavzr8igs-pony-stable-0.1.2.drv' failed with exit code 2
error: build of '/nix/store/k47cksmn41yipn9vsp8g53cmavzr8igs-pony-stable-0.1.2.drv' failed

Failure on x86_64-darwin (full log)
Attempted: pony-stable
Partial log (click to expand)
/private/tmp/nix-build-pony-stable-0.1.2.drv-0/source/stable/main.pony:85:63: can't reference a method without calling it
          ["env"; "PONYPATH=" + ponypath] .> append(rest), env.exitcode)?
                                                              ^
Error:
/private/tmp/nix-build-pony-stable-0.1.2.drv-0/source/stable/main.pony:85:60: argument not a subtype of parameter
          ["env"; "PONYPATH=" + ponypath] .> append(rest), env.exitcode)?
                                                           ^
make: *** [Makefile:41: build/release/stable] Error 255
builder for '/nix/store/p942b1sp0gvzhw2crm5s4189a8fyshqr-pony-stable-0.1.2.drv' failed with exit code 2
error: build of '/nix/store/p942b1sp0gvzhw2crm5s4189a8fyshqr-pony-stable-0.1.2.drv' failed

Let's try again now that #41234 is merged.
@GrahamcOfBorg build pony-stable

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: pony-stable
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-darwin (full log)
Attempted: pony-stable
Partial log (click to expand)
Writing build/release/stable.o
Linking build/release/stable
installing
mkdir -p /nix/store/2qj2491fdwxjngqp1na26xfzr58swh1p-pony-stable-0.1.2/bin
cp build/release/stable /nix/store/2qj2491fdwxjngqp1na26xfzr58swh1p-pony-stable-0.1.2/bin
post-installation fixup
strip is /nix/store/r5mcn9vqq80v5pfqp45d7290cis7dwp4-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/2qj2491fdwxjngqp1na26xfzr58swh1p-pony-stable-0.1.2/bin
patching script interpreter paths in /nix/store/2qj2491fdwxjngqp1na26xfzr58swh1p-pony-stable-0.1.2
/nix/store/2qj2491fdwxjngqp1na26xfzr58swh1p-pony-stable-0.1.2

Success on x86_64-linux (full log)
Attempted: pony-stable
Partial log (click to expand)
mkdir -p /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2/bin
cp build/release/stable /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2/bin
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2
shrinking /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2/bin/stable
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2/bin
patching script interpreter paths in /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2
checking for references to /build in /nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2...
/nix/store/8sisv3vb67k1bxnmhdif3vqpmjvqyfka-pony-stable-0.1.2

authors: GrahamcOfBorg patternspandemic xeji


text:
streamlink: 0.12.1 -> 0.13.0

Motivation for this change
Update
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.

cc @dezgeg @zraexy

@GrahamcOfBorg  build streamlink

Failure on x86_64-linux (full log)
Attempted: streamlink
Partial log (click to expand)
TypeError: freeze_time() expected None, a string, date instance, or datetime instance, but got type <class 'function'>.

----------------------------------------------------------------------
Ran 517 tests in 10.710s

FAILED (errors=1, skipped=20)
Test failed: <unittest.runner.TextTestResult run=517 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=517 errors=1 failures=0>
builder for '/nix/store/fr0ly6d31vhapk646ryr6kyyddqqm223-streamlink-0.13.0.drv' failed with exit code 1
error: build of '/nix/store/fr0ly6d31vhapk646ryr6kyyddqqm223-streamlink-0.13.0.drv' failed

Failure on aarch64-linux (full log)
Attempted: streamlink
Partial log (click to expand)
TypeError: freeze_time() expected None, a string, date instance, or datetime instance, but got type <class 'function'>.

----------------------------------------------------------------------
Ran 517 tests in 37.284s

FAILED (errors=1, skipped=20)
Test failed: <unittest.runner.TextTestResult run=517 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=517 errors=1 failures=0>
builder for '/nix/store/354il86la0anipfswldfpkx0422dbniy-streamlink-0.13.0.drv' failed with exit code 1
error: build of '/nix/store/354il86la0anipfswldfpkx0422dbniy-streamlink-0.13.0.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: streamlink
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 aarch64-linux (full log)
Attempted: streamlink
Partial log (click to expand)
test_stream_open_video_audio (tests.streams.test_dash.TestDASHStream) ... ok
test_stream_open_video_only (tests.streams.test_dash.TestDASHStream) ... ok
test_dynamic_reload (tests.streams.test_dash.TestDASHStreamWorker) ... ok
test_static (tests.streams.test_dash.TestDASHStreamWorker) ... ok

----------------------------------------------------------------------
Ran 517 tests in 36.719s

OK (skipped=20)
/nix/store/i8slsbrss3kfy2awlciqhx7wzh2vi4vy-streamlink-0.13.0

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: streamlink
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.

I have sandboxing enabled. I mereley managed to somehow let this commit slip away …

Thanks. Why does this cause a mass rebuild of pretty much all haskell things now? If this is necessary, you will need to rebase this PR on the staging branch.

Haskell? With nox-review I am seeing primarily Python packages. This is probably caused by the update of freezegun which is a test dependency and thus indirectly used by those packages.

Can you get the streamlink update to work without updating freezegun?

Yes! I have applied a patch from upstream which was commited twelve days ago specifically to make it work with older versions of freezegun.

Thank you!

authors: GrahamcOfBorg jfrankenau xeji


text:
almonds: use python3

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/18185
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.

cc @Infinisil

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

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

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

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

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

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

authors: GrahamcOfBorg dotlambda


text:
Fix firefox sync-server

Motivation for this change
The nixos syncserver module was broken, this PR fixes it by rolling back a dependency. serversyncstorage requires cornice v0.17 and does not work with any later version.
Based on https://github.com/NixOS/nixpkgs/pull/52654.
I have tested it in production and it seems to work well.
Fixes https://github.com/NixOS/nixpkgs/issues/38830.
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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is digging up quite an old PR, but could we not simply set
  disabled = !(isPy27 && cornice.version == "0.17");

to stop this appearing to be a "broken" package?

authors: Nadrieril risicle


text:
la-capitaine-icon-theme: init at 0.6.1

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)

[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"
[ ] 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
[x] Fits CONTRIBUTING.md.

I don't use nixos for a while and i don't like to be notified anymore. Please don't mention me!


text:
bazel: 0.24.0 -> 0.26.0

Motivation for this change
A few new versions of Bazel have been released. This bumps to 0.26.0 to stay recent.
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
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p 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)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@grahamcofborg build bazel

Please give it another try @matthewbauer
I still can't get it building on Darwin, but I enabled sandbox to get past the Skydoc error, so I think it may get a bit further on Linux.
My Darwin error is:
In file included from src/main/cpp/blaze_util_darwin.cc:24:
/nix/store/mffyf74zc4h2wic5lwx0kyx7gvwif0c5-Libsystem-osx-10.12.6/include/pthread/spawn.h:65:34: error: unknown type name 'qos_class_t'; did you mean 'au_class_t'?
                                 qos_class_t __qos_class);
                                 ^
/nix/store/mffyf74zc4h2wic5lwx0kyx7gvwif0c5-Libsystem-osx-10.12.6/include/bsm/audit.h:176:19: note: 'au_class_t' declared here
typedef u_int32_t       au_class_t;
                        ^
In file included from src/main/cpp/blaze_util_darwin.cc:24:
/nix/store/mffyf74zc4h2wic5lwx0kyx7gvwif0c5-Libsystem-osx-10.12.6/include/pthread/spawn.h:88:34: error: unknown type name 'qos_class_t'; did you mean 'au_class_t'?
                                 qos_class_t * __restrict __qos_class);
                                 ^
/nix/store/mffyf74zc4h2wic5lwx0kyx7gvwif0c5-Libsystem-osx-10.12.6/include/bsm/audit.h:176:19: note: 'au_class_t' declared here
typedef u_int32_t       au_class_t;
                        ^
2 errors generated.

Build succeeds on Linux, but tests are failing with:
src/main/tools/process-wrapper-legacy.cc:58: "execvp(external/remote_java_tools_linux/java_tools/ijar/ijar, ...)": No such file or directory

Here's a fix for the Darwin issue:
diff --git a/pkgs/development/tools/build-managers/bazel/default.nix b/pkgs/development/tools/build-managers/bazel/default.nix
index 3b23ca395e8..3a880541228 100644
--- a/pkgs/development/tools/build-managers/bazel/default.nix
+++ b/pkgs/development/tools/build-managers/bazel/default.nix
@@ -160,6 +160,9 @@ stdenv.mkDerivation rec {
         src/tools/xcode/realpath/BUILD \
         src/tools/xcode/stdredirect/BUILD \
         tools/osx/BUILD
+
+      # nixpkgs's libSystem cannot user pthread headers directly, must import GCD headers instead
+      sed -i -e "/#include <pthread\/spawn.h>/i #include <dispatch/dispatch.h>" src/main/cpp/blaze_util_darwin.cc

       # clang installed from Xcode has a compatibility wrapper that forwards
       # invocations of gcc to clang, but vanilla clang doesn't

Legend! Thanks @uri-canva I'll kick off a local test now. I think I'll have to fetch the java_tools_javac10_darwin-v3.1.zip as well.
I think I understand what is happening during the installCheckPhase. I've got it working if I build on Linux without Nix. Bazel downloads java_tools_javac10_linux-v3.1.zip when building the interface jars for junit4 used in the tests.
This is failing under Nix. I'm not 100% clear on how or if this should be fixed. I wonder if the whole approach to these tests may fail, given that Bazel can fetch rules remotely.

@GrahamcOfBorg build bazel

Success on Darwin, failure on Linux. Must be a first! 😂
I'm looking into the Linux errors. I didn't have sandbox enabled locally, so I'll do that for Linux which will hopefully help track down errors.

@uri-canva Thanks! Opened this issue to track what's going on: https://github.com/NixOS/nixpkgs/issues/62555

@matthewbauer Any chance you can kick off another build. Linux only. I'm unable to run sandboxed builds in a Docker container at the moment. I've fixed the previous error with rules_sass in https://github.com/NixOS/nixpkgs/pull/62336/commits/f1a511a86a02295e2385da96180e3481d68b26d5

I suspect the Bazel tests fail on Linux because of the network sandboxing. The way the building of the tests should be done to account for that is the same way buildBazelPackage does it: first run bazel fetch as a fixed output derivation with networking enabled, then run bazel test with networking disabled.
We could rewrite the whole derivation to split it in two: first build the bootstrap bazel, then use boostrap bazel with buildBazelPackage to build and test Bazel. That also mirrors what compile.sh does.
It's a lot of work though, we might want to skip testing java on Linux in the meantime.

@Profpatsch This is now ready for review. Please kick off a build to confirm.
I expect it to pass on Darwin. Fail on Linux. I'm able to reproduce the Linux failure on my local VM.

We could rewrite the whole derivation to split it in two: first build the bootstrap bazel, then use boostrap bazel with buildBazelPackage to build and test Bazel. That also mirrors what compile.sh does.

Yes, I think given the way Bazel works, this is the only sensible solution. I think I understand what is necessary. Will that second inside buildBazelPackage be cached in the Nix store?

Yes, the deps derivation is separate from the build derivation and they get cached separately.

So we’re skipping 0.25 alltogether? https://github.com/NixOS/nixpkgs/pull/61097

So we’re skipping 0.25 alltogether? #61097

The Bazel release cycle is too frequent to do 1:1 Nix releases. I certainly don't have time to do it. The functionality I want is in 0.26. In a week or 2 there will 0.27....

@GrahamcOfBorg build bazel.tests

The linux test fails.

The linux test fails.

@Profpatsch Yes, thanks, it is expected. We just wanted to confirm if it fails on CI with the same error as we get locally. It does, so that's great, we can hopefully fix it.
The failure is due to the sandbox blocking network access during the tests. Bazel isn't very good to test in this way, as rules can go and download other rules at runtime. What are your thoughts to fixing it?

What are your thoughts to fixing it?

By now I’m tempted to disable the checkPhase (doCheck = false;) and rely on the manual tests we run afterwards. We can’t keep up with their (shitty) WORKSPACE stuff, they don’t really care about other build systems.

The problem now is that the fetch arbitrary binaries (external/remote_java_tools_linux/java_tools/ijar/ijar) and try to execute them, we must patch those first or add their dependencies to the test environment.

The java tools currently live here: https://github.com/bazelbuild/bazel/tree/master/src/java_tools, but they'll move them to https://github.com/bazelbuild/java_tools eventually. We can build them from source in the nix derivation using the bootstrap bazel that should be possible to build without network access.

Sorry I'm just commenting and not helping much on the PR this time, I don't have enough time to dedicate to it at the moment.

We can also patch out some of the remote files as long as we delete the references to them: I cannot believe the rules_sass and rules_nodejs are needed for building Bazel itself, they're probably used to render the documentation.

@Profpatsch

By now I’m tempted to disable the checkPhase (doCheck = false;) and rely on the manual tests we run afterwards.

I agree that this is the best course of action for now. PR updated to reflect this. Passing locally on my Linux VM.
I'll try to find some time to submit an additional PR to change the approach of the Bazel derivation as @uri-canva is suggesting.

@GrahamcOfBorg build bazel

@GrahamcOfBorg build bazel bazel.tests

Why the heck is the builtin rule py_binary downloading external libraries.

I opened an upstream issue https://github.com/bazelbuild/bazel/issues/8575

@GrahamcOfBorg build bazel.tests

@GrahamcOfBorg build bazel.tests

@GrahamcOfBorg build bazel.tests

@GrahamcOfBorg build bazel.tests

@GrahamcOfBorg build bazel.tests

I very much appreciate the help here @Profpatsch
0.26.1 has been released. If you are able to get 0.26.0 working, it might be worth giving one shot to the 0.26.1 since we're in the trenches anyway. I'm happy to help and / or prepare it. I can dig up all the hashes etc. Equally, I'd totally understand if you'd rather not. I get fed up with Bazel shenanigans too.

Sure, but tomorrow. I think it’s building now (I’m pretty sure caching the bazel extraction for tests was not worth the effort lol).

@GrahamcOfBorg build bazel.tests

Great! Seems to have passed. I'll try a quick bump to 0.26.1 sometime today.

The build works locally for me on Darwin (no sandbox) and a NixOS VM (sandbox = true).
I'll update the title, description and squash the commits.

Is it okay if we leave the commits as-is? I’d only squash in the fixup commits (git rebase --autosquash).

Is it okay if we leave the commits as-is? I’d only squash in the fixup commits (git rebase --autosquash).

Apologies, I think I'm too late and I've squashed it all down. In some of my other nixpkgs contributions, the reviewer was particular that I squashed everything down into a single commit with a particular commit message. Maybe that's not standard across the whole repo or is more nuanced and can be more than a single commit.

Normally multiple commits for separate changes are not a problem. I’ll force-push the split commits.

Okay, I rebased to master & autosquashed the fixup commits. Will merge once it’s green again.

Ah, I’m sorry, I didn’t see the bump to 0.26.1.

I'm putting a quick PR together for 0.26.1.

Thanks @Profpatsch @kalbasit

I just noticed that this changed the hash of the fetch phase of dm-sonnet. We probably have to be more careful with bazel updates in the future if we're using it in fixed output derivations.

I just noticed that this changed the hash of the fetch phase of dm-sonnet. We probably have to be more careful with bazel updates in the future if we're using it in fixed output derivations.

Uuuuuuuuuuuuuuugh, I suggest we just don’t.
@timokau But for the while being, can you add a tests.downstreamPackages = { inherit <list of packages that use fetchbazel>; }?

Don't do what? Don't be careful seems like a bad idea to me ;) And we're already using it in fixed output derivations, I don't see how we could avoid that when building bazel packages.
Would that actually help? Since they're fixed output, they will just be fetched from the binary cache and therefore pass the tests even though they're broken.

@timokau you can probably override one of the phases of the fetcher to invalidate it's input, and force it to compile. Something like echo ${version} should do.

Interesting idea! I feel like there is a bit of a "just because you can doesn't mean that you should" going on here, but here we go: https://github.com/NixOS/nixpkgs/pull/63645
I have created a separate attribute for the derivation instead of a list, because a list wouldn't get built with nix-build -A bazel.test.

Don't do what? Don't be careful seems like a bad idea to me ;) And we're already using it in fixed output derivations, I don't see how we could avoid that when building bazel packages.

Don’t ever use fixed output derivations.

How else should we fetch bazel dependencies?
I'd expect the fetch output to become deterministic between releases once bazel is stable. If it still isn't, we can look into how they differ between releases and clean up the fetch result accordingly (similar to what we do with fetchpatch).

How else should we fetch bazel dependencies?

We do it like with all other (well-behaved) package managers and generate nix expressions for WORKSPACE dependencies. I already wrote a mockup hack for updating bazel proper: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/build-managers/bazel/update-srcDeps.py
But really, bazel devs should pull the stick out of their asses, provide a reasonable interface and become a nice player in the open source world.

Yeah Bazel is really really biased towards monorepos with full vendoring.
I think something good integration-wise can be done with resolved workspaces and provided external repositories, but both mechanisms are very much in their infancy and it's unclear how well supported they are:
https://blog.bazel.build/2018/07/09/bazel-sync-and-resolved-file.html
https://github.com/bazelbuild/bazel/issues/5252

Ah, yes, that’s the better way tbh. It’s a skylark file, so we should be able to cheat our way by evaling it in a python interpreter.

authors: Lassulus Profpatsch groodt kalbasit matthewbauer timokau uri-canva


text:
qt5.12 base: Add patch to fix QTBUG-73459

Motivation for this change
QT 5.12 introduced a regression, where a QT program wouldn't show its
tray icon, if there was no tray bar during program startup.
It got fixed already in Qt 5.12.4, but according to #57042 and its
sibling issues/PRs it doesn't seem to get fixed in near future for
nixpkgs.
The bug on the qt bugtracker: https://bugreports.qt.io/browse/QTBUG-73459
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"
[ ] 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] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Is there a reason to backport this particular patch?

It's a super annoying bug. Other distros have backported it before release of 5.12.4 (see Arch) too.
I don't know yet the exact policies of NixOS backporting and I don't know, whether Qt 5.12.4 would get backported onto 19.03. But nevertheless after reading through the threads regarding the update of Qt 5.12, I guess it won't happen because of the required labor.

I don't know yet the exact policies of NixOS backporting and I don't know, whether Qt 5.12.4 would get backported onto 19.03. But nevertheless after reading through the threads regarding the update of Qt 5.12, I guess it won't happen because of the required labor.

I expect Qt 5.12.4 to be backported into NixOS 19.03, but I don't know when it will be in master so that it can be backported. So, I would support including this patch.
The workflow for this kind of change is: This change should go into staging (instead of release-19.03). Once it is merged, it should be backported to release-19.03 in a separate pull request using git cherry-pick -x. The changes to staging will eventually make it into master (it's also needed there for now). The rationale for this is that we would prefer that the release branch not diverge from master: the master branch has changes not in the release branch, but not vice versa.

I'm currently working on Qt 5.12.4, but something serious changed in the build system... I'm already debugging it to find the cause, but can still take some time.

@bkchr I'm about to open a pull request into staging with Qt 5.12.3 based on #60119, would that address some of the build system problems for you?

I'm not sure. I got a little bit further. Qtbase is compiling and some stuff building on it. Now I'm at qtwayland

@bkchr ping (status?)

@aanderse sorry, did not any time to look into it :(

@petabyteboy Thank you for fixing this in all relevant branches!

authors: aanderse bebehei bkchr ttuegel


text:
[staging-next] gtk3: don't multiout demos

Motivation for this change
Noticed that pantheon.elementary-gsettings-schemas was failing on staging-next.
After checking the copy commands it was doing I noticed there was no gsettings
in gtk3.out!
moveToOutput share/gsettings-schemas "$dev" was doing this.
After reflection I found this approach on multioutputs to be flimsy.
Perhaps a patch would be better to use in the future.
this needs to be merged to staging-next to avoid that aforementioned regression
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"
[ ] 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.

Darwin problem is at stdenv level

:+1: the difference in disk usage is negligible (160k addition to 36M of .out).

authors: 7c6f434c vcunat worldofpeace


text:
nodePackages.postcss-cli: init at 7.1.0

Motivation for this change
postcss-cli is a very handy way for using postcss outside node projects (like personal userstyles).
Things done

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

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

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

Rebased to master

@ryan4729 Rebased to master, apologies for the delay

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Rebased to master

Thank you!


text:
cargo-deps: init at 1.1.1

Motivation for this change
Describes itself as "an improvement on the unmaintained and buggy cargo-graph," which is in nixpkgs.
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
[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 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
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Thanks!

authors: arcnmx marsam


text:
python3Packages.tensorflow-build: enable on darwin

Motivation for this change
This should be a way to fix tensorflow on darwin. The tensorflow-bin is broken (#73703).
Things done

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

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

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

@GrahamcOfBorg build python3Packages.tensorflow

Hydra doesn't seem to be able to build it:
https://hydra.nixos.org/job/nixpkgs/trunk/python37Packages.tensorflow.x86_64-darwin
I don't understand why in https://hydra.nixos.org/build/108086001 we got
Neither 'python3' nor 'python' were found on the target platform's PATH, which is:

when I can do
# nix-store -r /nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env
# ls /nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python*
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python-config
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3-config
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3.7
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3.7-config
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3.7m
/nix/store/b2nfnj6m9m3ibbm9gwb54c39xh3x86wf-python3-3.7.5-env/bin/python3.7m-config

authors: jonringer veprbl


text:
firecracker: 0.19.0 -> 0.20.0

https://github.com/firecracker-microvm/firecracker/blob/v0.20.0/CHANGELOG.md#0200

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)

[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
[x] Fits CONTRIBUTING.md.

Thanks!

authors: marsam zowoq


text:
gegl: enable umfpack support

Fixes #79836, thus adding one more awesome feature to gimp !

Motivation for this change
umfpack supports enable using a better foreground select tool in gimp
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)
[x] 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.

Wow, did not even know this existed. Levin indeed looks much better

than the global method

I am especially impressed by how it handled the bouquet.
(Image source)

Thanks.

authors: jtojnar multun


text:
[backport-20.03] nixos/haproxy: Revive the haproxy user and group

Running haproxy with "DynamicUser = true" doesn't really work, since
it prohibits specifying a TLS certificate bundle with limited
permissions. This revives the haproxy user and group, but makes them
dynamically allocated by NixOS, rather than statically allocated. It
also adds options to specify which user and group haproxy runs as.
(cherry picked from commit bb7ad853fbcbd158ff32c12d2d93941343418715)

Motivation for this change
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.

backport of https://github.com/NixOS/nixpkgs/pull/82350

@GrahamcOfBorg test haproxy


text:
nixos/octoprint: improve example

Motivation for this change
noticed in https://www.reddit.com/r/NixOS/comments/ifmg55/octoprint_plugins/ that the example will actually cause an error. Fixed the example.
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/)
[ ] 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.

also changed it to show m33-fio as m3d-fio i guess is deprecated


text:
HyperX Alloy FPS Mechanical Gaming Keyboard not working

I mentioned it in my pull request. My HyperX Alloy FPS Mechanical Gaming Keyboard is behaving strangely.
Symptoms:
It is register correctly:
HID(2,3,KEYBOARD) mounted
 ID: 0951:16b7
 Manufacturer: Kingston
 Product:      HyperX Alloy FPS Mechanical Gaming Keyboard

But when a key is pressed all the events are recognized as mouse events although they come from the dev_addr/instance that was identified as KEYBOARD (i.e. dev_addr=2, instance=3 in the above example). The mouse cursor jumps wildly across the screen and ps2x2pico hangs eventually.
Investigation
I did some investigation and found out that the events identified as mouse events are actually keyboard events, but not from the simplified boot protocol that tinyusb uses but with a real HID event descriptor. They are 16 bytes long, not 8 and they have different but correct format. I wrote some code to decode them and could reliably identify all keypresses, except the EUROPE_1 and EUROPE_2 keys (these are the keys that are not present on US american keyboards, but on many european ones). The latter two keys were send in the 8 byte long boot protocol, but with the modifier bit field always 0.
So my assumption is that the keyboard in question does not support the old boot protocol but only the full featured HID protocol. Tinyusb is not able to cope with this. The tinyusb function tuh_hid_interface_protocol(dev_addr, instance) to identify the protocol of the event (i.e. if it is mouse or keyboard) is not compatible with the full protocol mode and falsely claims that it is a mouse event.
The lock up of ps2x2pico is probably due to concurrency issues. Could be due to calling the ms_usb_receive(report) function while the previous call is not finished or maybe due to a tinyusb problem where they are overrun by the events and ps2x2pico is not consuming them fast enough.
This little project here really ignited my interest and I want to dive deeper into this USB stuff. So I will continue to work on this. So maybe there will be another pull request in the future for this.

Hu ha sounds complicated, but boot mode won't cut it in the long run I guess.
Would also solve this on the mouse side: https://github.com/No0ne/ps2x2pico/issues/35
Thanks for future PRs!

I have the feeling that tinyusb is quite incomplete in this regard (USB host and boot mode vs. full), and I"m not sure this is a priority for them. They wrote somewhere in the comments that they switch each mouse and keyboard into boot mode when connecting. But I need to read more of the USB docs and tinyusb code before deciding what to do. I also plan to contact them and ask them about their plans. But only after I know enough to ask them educated questions... ;-)

Did you find out anything new on this issue?
I'm nearly finished with the ps2 input feature, please pull as some files a renamed now.

I investigated this some time ago and then traveled for a few weeks. I found out how to configure tinyusb to set report protocol instead of boot protocol when configuring a hid device:
tuh_hid_set_default_protocol(HID_PROTOCOL_REPORT);
tusb_init();

I implemented a rough parsing of the report that the keyboard is sending (just hardcoded, without actually parsing the report descriptor).
But I noticed that this keyboard is not sending europe_1 and europe_2 keys when I do this. And since I live in Germany I need them. I think the keyboard has weird bugs, that might be triggered when the report protocol is explicitly requested. I traced the USB communication of this kb and a few others I have on Linux to have something to compare to and Linux never sets the protocol explicitly. It just requests the report descriptors and then the keyboard sense also the events for the europe keys happily...
Anyway this is the only kb that is not working for me, which is not a big issue to me. I'm a bit fed up with the topic at the moment. ;) I suggest to leave this issue open since it is not fixed and I will come back when I have time and you haven't fixed it yourself yet by implementing proper report descriptor parsing and setting of the mode.

Have you ever noticed that there is a full hid report parser just in raspcerry pi pico-sdk?
https://github.com/bluekitchen/btstack/blob/72ef1732c954d938091467961e41f4aa9b976b34/src/btstack_hid_parser.c

No, I indeed have never noticed this parser. :D But this still doesn't solve the fundamental problem of the seemingly very buggy firmware of this keyboard. There are 2 bugs I did identify:

In boot protocol mode (which it supports according to its descriptors)  it sends the report not in boot format but in its own report format.
If report protocol mode is set it sends the event in its report format but omits the europe_1 and europe_2 keys. (deal breaker for me)

It seems to work fine if the protocol mode is not set explicitly though. This is what I saw when I traced the communication in Linux using Wireshark.
To solve this I would need to patch tinyusb to never set the protocol mode and issue a PR for it. I simply do not want to do this just for one buggy keyboard. (I simply don"t use it here. I have too many keyboards anyway...) But if there are more keyboards that have similar bugs it might be worth the effort.
Another question is if we would start to use the HIDs in report mode and drop the boot protocol mode. This indeed is something to consider. But I think this decision is up to NoOne as the maintainer of this project. I suggest to open a new issue for this.
My day job is currently consuming most of my time so I can't work on this during the next few months. Still I would do this when I have more time to burn.

Yeah, there are quite a lot of HID devices not following the standard HID specification. Many of them just never had a boot mode, even though they claimed to support it in their descriptor. However, I'm very surprised that Linux and Windows' HID drivers always make the right choice on whether to set the device into report mode. I cannot see any reason from the USB traffic; maybe it needs digging into the kernel source to understand.

As I said my assumption is that at least Linux is not setting the mode and it just uses the device as is (i.e. in report protocol mode). In Linux it is quite easy to capture the USB traffic with Wireshark. Don't know about Windows. Haven't looked at this yet.
Though I'm 100% sure all manufactures test their devices with Windows and most of them with Linux. So it would be best to copy Windows or at least Linux. I also started digging into the Linux kernel sources already. I think Linux is the best source to copy you can get.
So yes in my eyes there is definitely a case to move away from boot proctol mode for this project.

Yes totally agree, this would also help/fix #3 #23 and #35, but it is also too difficult for me right now.
Thanks for the research, I'll close this for now and open it when its relevant again.

I'll soon get rid of boot mode. @bstrobel if you are still interested and would like to test your keyboard when I'm done this would be nice.

Please test the latest pre-release: https://github.com/No0ne/ps2x2pico/releases/tag/pre-1.3

There is a new 2.0 pre-release, it fixed #64.

Please also try this: https://github.com/No0ne/ps2x2pico/issues/66#issuecomment-2538518448

source: gharchive/issue


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

In 429873a, 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 b412a31 after 1 hour, 27 minutes.

repo: NoPlagiarism/services-personal-upptime


text:
🛑 WikiLess wikiless.whateveritworks.org is down

In 8559999, WikiLess wikiless.whateveritworks.org (https://wikiless.whateveritworks.org) was down:

HTTP code: 500
Response time: 669 ms

Resolved: WikiLess wikiless.whateveritworks.org is back up in 64fe39d after 6 minutes.


text:
🛑 WikiLess wiki.privacytools.io is down

In 4d529a9, WikiLess wiki.privacytools.io (https://wiki.privacytools.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WikiLess wiki.privacytools.io is back up in 7065151 after 45 minutes.


text:
🛑 WikiLess wikiless.esmailelbob.xyz is down

In 364b07f, WikiLess wikiless.esmailelbob.xyz (https://wikiless.esmailelbob.xyz) was down:

HTTP code: 500
Response time: 869 ms

Resolved: WikiLess wikiless.esmailelbob.xyz is back up in 9a85fad.


text:
🛑 BreezeWiki bw.projectsegfau.lt is down

In 78f8041, BreezeWiki bw.projectsegfau.lt (https://bw.projectsegfau.lt) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BreezeWiki bw.projectsegfau.lt is back up in a1ff104 after 22 minutes.


text:
Kicked from server when mod is interacted with

Load in is fine and can do everything else however when anyone interacts with the mod ie picks up an item or spawns in one they get kicked from the server. Works fine in singleplayer so no issue there.
Disconnect error is "Internal Exception: io.netty.handler.codec.DecoderException: Failed to decode packet 'serverbound/minecraft:set_creative_mode_slot'
Other mods work fine all dependencies are installed as said in Modrinth description.
Using version 1.21 Alpha4
Apologies if this is a simple fix or something that you guys cannot recommend a fix for, thank you.

Could you provide some more info surrounding how you re-created the issue? Mainly if you providing a log, as it would be very helpful as it contains a lot of info regarding Mythic Metals, Fabric, and the dependencies you are using when the disconnect occurs

I am not able to reproduce this issue. I am using latest Alloy Forgery (2.2.1), and the next alpha of Mythic Metals which fixes #252. Alloy Forgery is released, and for Mythic Metals you can test out the alpha from the Action: https://github.com/Noaaan/MythicMetals/actions/runs/9869137397/artifacts/1685165128

Are you still experiencing this issue?

Closing this due to lack of information. Feel free to re-open it should it still be a problem

authors: Mewey-y Noaaan

repo: Noaaan/MythicMetals


text:
Designate a filename for the "best" model

It would be nice if there were a programmatic way to identify the best-performing model, as measured by validation error.  I am thinking that in addition to outputting checkpoints with names like epoch=4-step=450000.ckpt we could output a copy (or symlink) to the one with the best validation error using a name like "final.ckpt".

Unfortunately looking at the PyLightning documentation this isn't supported by the ModelCheckpoint class natively. However, it would be possible to define a custom callback which would own a reference to the validation ModelCheckpoint, and whenever the validation ModelCheckpoint fires the custom callback would save a symlink to the validation checkpoint with the best validation loss with a name like best.ckpt. Thoughts on this approach would be appreciated.

I like the name best.ckpt better than my suggestion (final.ckpt) because it's more accurate.  Using a symlink rather than a copy is also better.  I will let others comment on the best way to implement this.

Simply saving the best model is already supported by setting save_top_k to 1 in the config, no code changes required.

Yes, but my point is that the user has no way in advance of knowing exactly what that model will be called. And if save_top_k is >1, then it's hard to tell which is the best.

Then I see two low-code options to address that:

Provide a config option to set the name of the output file, optionally removing the epoch and step information.
Add an additionall ModelCheckpoint that only saves the best model with a fixed name, in addition to the currently saved best 5 and last model.

Addressing the second low-code approach, I'm not terribly familiar with the PyLightning API but wouldn't this create a copy of the best performing weights rather than a symlink? I'm not sure how concerned we are about disk usage.

Yes, it would be a copy of the weights. I don't think that's a real concern though (weights will be smaller than training data or even a run for sequencing anyway).

I tried introducing another model checkpoint that monitors the valid_CELoss but has k set to one. However, it turns out you can't have to ModelCheckpoints monitoring the same quantity in the same mode (in this case valid_CELoss and min). I'm looking into a workaround atm.

After investigating some potential workarounds I found a workable low(ish) code solution. By adding this to model_runner.py (tentatively, let me know if it should be moved):
class SaveBestModelCheckpoint(ModelCheckpoint):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)

    def on_validation_end(self, trainer, pl_module):
        super().on_validation_end(trainer, pl_module)
        target_path = Path(self.best_model_path)
        simlink_path = Path(self.dirpath) / "best.ckpt"
        simlink_path.unlink()
        simlink_path.symlink_to(target_path)

and replacing
if config.save_top_k is not None:
  self.callbacks.append(
      ModelCheckpoint(
          dirpath=config.model_save_folder_path,
          monitor="valid_CELoss",
          mode="min",
          save_top_k=config.save_top_k,
      )
  )

with
if config.save_top_k is not None:
  self.callbacks.append(
      ModelCheckpoint(
          dirpath=config.model_save_folder_path,
          monitor="valid_CELoss",
          mode="min",
          save_top_k=config.save_top_k,
      )
  )

We can essentially create a thin wrapper around ModelCheckpoint that creates a simlink to the best model. I've done some preliminary testing and this solution appears to work. The only problem thus far is (on windows at least) creating a simlink requires admin level privileges, so maybe SaveBestModelCheckpoint can simply copy the best file instead of creating a simlink.

However, it turns out you can't have to ModelCheckpoints monitoring the same quantity in the same mode

So the conflict is between saving the top k models and only the best one? We've discussed this a bit before already, but I'm not sure what the benefit is of saving the best 5 models. Why would you want to use models ranked 2–5? 🤷♂
Alternatively, we could change it to save all checkpoints, which is default Lightning behavior and doesn't require a ModelCheckpoint callback, and then use the callback for just the best model.

I agree that the utility of saving the top 5 is not clear to me.  I'm fine with saving all models, as long as there is a way to disable that behavior to save disk space.

authors: Lilferrit bittremieux wsnoble

repo: Noble-Lab/casanovo


text:
Update Favicon

index.html in dapp/public

done in commit 0efb854f746e4019e7f036249749de8367dc978e

repo: NonFungibleTeam/cell


text:
Date separators not appearing at the right time

See https://www.evernote.com/l/ABYc9VtmgzlBEpJLs2LRo_crRmiptPrEK24A

This is fixed in one-point-oh, since it is rendered on client side:
https://github.com/Nordaaker/convos/blob/one-point-oh/assets/js/core/dialog.js#L38

authors: jhthorsen marcusramberg

repo: Nordaaker/convos


text:
Modify the integration test env variables

Use the CAPI_VERSION variable and only override the variables for the
tested patchset

please do not merge

/test-integration

/test-centos-integration

/test-integration

/test-centos-integration

Looks good for me

/test-v1a1-integration

/test-v1a1-centos-integration

/test-v1a1-centos-integration

/test-v1a1-integration

authors: fmuyassarov maelk

repo: Nordix/airship-dev-tools


text:
assistant/chatgpt: Add jackMort/ChatGPT.nvim

Redoes #242 with a minimal diff.
CC @ksonj for review.

looks good to me, thanks!

authors: NotAShelf ksonj

repo: NotAShelf/neovim-flake


text:
fix :批量转账到零钱:微信明细单号查询明细单API,商家明细单号查询明细单API 参数错误

请尝试目前最新的版本 1.0.10

不好意思忘了加版本号，PR使用的是最新的1.0.10版本


text:
Update Franchisee SILK History

Purpose:
This issue aims to provide a comprehensive overview of the franchise's rich history, highlighting its journey, global impact, and significant milestones. By delving into the franchise's history, we can showcase its evolution, values, and the legacy it has built over time.
Importance:
Understanding the history of the SILK franchise is crucial for both internal stakeholders and prospective franchisees. It instills a sense of pride among existing members and serves as an inspiring narrative for those considering joining the franchise. It also demonstrates the franchise's commitment to transparency and integrity.
Approach:

Global Legacy: Explore the global reach and influence of the franchise. Highlight how SILK has left a positive imprint on diverse communities worldwide, fostering well-being and social impact.

Milestones of Success: Chronicle the franchise's key achievements and milestones, emphasizing its growth, innovation, and contributions to the wellness industry.

Building on Success: Showcase how the franchise's history has paved the way for its current success and how it continues to build upon this foundation to create a brighter future.

Outcome:
This issue will result in a comprehensive and engaging portrayal of the franchise's history, emphasizing its global legacy and milestones of success. It will serve as an invaluable resource for franchisees, partners, and anyone interested in the franchise's journey toward a brighter, more inclusive future.

You can use Envato Elements or Flickr to find high-quality photos.
You can use Pixlr to resize the image.

Note:

All images should be saved inside this folder: SILK Images
Be organized on how you're naming your images.

I'm going to work on this issue#273. Firstly I am going to find a suitable image for my project and resize it in addition I'm going to change the source of the image.

@SuzyQuant
Asset 1: Link
Asset 2: Link

Asset:1 Link
@Aini-Bashir  please download this image for Global legacy.

@rahmatzeb, please work on this issue again as already created one PR has mistakes. Images are already in the SILK images folder but if you still want to choose something else then share the Envato link and also mention me I'll download it for you.
Let me know if you have any quesries.
Thanks

@rahmatzeb, please be careful while choosing the narration of the source and image. Narration means by which name you save and upload the image and the name which you update in the html file.

Don't use any capital alphabet
Don't put space in wording (i.e. "silk yoga" this is wrong)
You can use "_" under scroll or just write without any symbol. (i.e. silkyoga this is correct)

Ok. @Aini-Bashir . I am going to work on this issue. Will let you know if I had any issues.

@rahmatzeb, this issue has three subparts:

Global Legacy
Building on Success
Milestone of success
Work is done on Global legacy and Milestones of success so you need to work only on building on success.

Ok. I was about to ask this... Thanks

@rahmatzeb, please share the link from the search bar

Okay, lemme do it again. I was on break.

@Aini-Bashir I am gonna used te saved picture. I find one suitable. Will let you know once I am done with it

Okay. I also downloaded the one you shared above.

Ok. Let me check

authors: Aini-Bashir Alisha-Rashid rahmatzeb

repo: NoteHive/Silk-Corp-Guide


text:
Initial project setup

Code formatting rules
Pull and build dependencies
Build dummy gtest

Draft until github actions can be added

TODO:

[ ] Build library
[ ] Build and run tests in pipeline
[ ] Code coverage
[ ] Badges
[ ] Doxygen
[ ] GitHub pages for doxygen?

Longer term:

[ ] Benchmarks
[ ] Test data!

authors: Ipiano Notgnoshi

repo: Notgnoshi/shpxx


text:
Quality Change

Hello,
Would it be possible to let users choose the quality without breaking the p2p structure?
I'm using this one with notmal HLS streaming. But Its not compatible with your p2p script.

Video.js integration is implemented using videojs-contrib-hlsjs plugin. It can be not compatible with videojs-resolution-switcher.
In this case, I recommend using another player, that has working quality selector support: Clappr, Flowplayer, JWPlayer.
We are going investigate the ability to implement P2P for built into Video.js 7 HLS support in next few months.

authors: defrinex mrlika


text:
Building as a dependency to other CMake project

I would like to build this as a dependancy to my project but your CMakeLists refers to the root project all the time.
Changes needed:
Replace CMAKE_SOURCE_DIR with PROJECT_SOURCE_DIR,
CMAKE_BINARY_DIR with PROJECT_BINARY_DIR.
This makes all your paths relative to your project and not the top level project (which are the same if you just build VK2D but different if my project has VK2D as a dependency).
I can make a pull request if that would be easier for you.

Hey, sorry for the long wait. Yeah that sounds good. I could grab from your branch if that's okay?

This https://github.com/exuvo/Vulkan2DRenderer/tree/20925688b3b11d385858f66675fd486b818d7016 tree should be good for just the changes to build this as a nested project.
We also did some reformatting of includes to be relative to the Source and Include directories instead of having to use ../../ all the time. That can be found in this tree https://github.com/exuvo/Vulkan2DRenderer/tree/302e62c7d97f8c65e9f935af3c29e9e52ec0abeb . My IDE eclipse handles this just fine but maybe check if yours does too.
A note about your usage of M_PI, many c libs already define it in math.h so we on linux were getting errors where you declare it yourself as a variable (ie it becomes double 3.14 = 3.14; error identifier expected). Doing it as a ifndef define should work better but we just commented it out for now when we tested. If you are okay with using c++20 they have added it there under std::numbers::pi (took them long enough).
The tests seems to work well on linux btw.

I looked over the differences and I like most of those changes, I'll update my branch sometime soon and see what I could pull from your branch.
There's vk2d::PI (I'll move it to a better location soon), forgot to remove the M_PI.
I want to conform to C++17 for the time being, but yeah, I agree it took them long enough. XD
The API is still changing a bit from time to time, just so that you're aware, I haven't locked anything down yet. I'll rewrite the tests whenever I have a better picture of how the final API will look like but it's good to know they pass on Linux as well. 👍

Thats nice to hear.
I'm fine with API changes, my game rendering is mostly solitary white pixels and some circles so it should be easy to adapt.

I reviewed and applied most changes from your fork to mine. If you have time, could you test the "dev" branch and let me know if it works before I merge it to master?

Gcc requires a parentheses around unsigned intin glfw_gamma_ramp.size = unsigned int( glfw_ramp_node_count ); in Window.cpp:4273, other than that it builds and runs fine.
It seems my reasoning about the CMake sources was slightly flawed, it is enough with add_custom_command with output and depends for me. The if(MSVC) in CMakeLists:129 can be removed and leave just the version that includes FILES_SHADERS for add_library.

authors: Noxagonal exuvo


text:
Admin/Support Request pages do not have the new site design

The admin, SR pages and maybe more do not have the new site redesign. I am not sure if this is expected. Filling a bug to get clarity.

Duplicate of this: https://github.com/NuGet/NuGetGallery/issues/4120

repo: NuGet/NuGetGallery


text:
build failed

by default powershell uses SSL3 and TLS1 in [Net.ServicePointManager]::SecurityProtocol
recently api.github.com removed support for TLS1 (only TLS1.2 left), so build fails with
Downloading files from https://api.github.com/repos/NuGet/ServerCommon/contents/build?ref=37ff6e758c38b3f513af39f881399ce85f4ff20b
VERBOSE: GET https://api.github.com/repos/NuGet/ServerCommon/contents/build?ref=37ff6e758c38b3f513af39f881399ce85f4ff20b with 0-byte
payload
BUILD FAILED: The underlying connection was closed: An unexpected error occurred on a send.
ERROR DETAILS:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
   --- End of inner exception stack trace ---
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()

after I added
[Net.ServicePointManager]::SecurityProtocol += [Net.SecurityProtocolType]::Tls12

to build.ps1 - build is fixed
should we add it permanently ? or there's better solution ?

The same fix is in the dev branch and will be merged to master soon. #5551

Thanks @edyoung. Yup, this is a duplicate of https://github.com/NuGet/NuGetGallery/issues/5551.

Workaround is to run this on your machine:
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

authors: chipitsine edyoung joelverhagen


text:
Store PackageTypes in Database

This PR is a preliminary look at adding package types to the database and includes the following:

Updates database to have a packageTypes table.

adds a new PackageTypeEntity for this.

Updates reference to NuGet.Packaging to rc1
Fixes tests.

@maartenba @skofman1 @xavierdecoster @joelverhagen

Hi @ryuyu, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Looking good :smile:

Wondering about package type name length: would be better if we could allow it to be indexed, so not sure what use case will require nvarchar(4000).
Otherwise LGTM!

Looks good.

:shipit: (perhaps check if we need to surface this in the V2 feed as well?)

Let's have a discussion about that with @harikmenon and i'll put in a new PR if we want to add it.

authors: dnfclas maartenba ryuyu shishirx34 xavierdecoster


text:
Using Enchantments through Polymer API removing level at the end (1.19)

When using Server Translations API for enchantments through Polymer, the enchantment tooltip on items removes the level at the end.
Example:

Without Server Translations: enchantment.enchanted_expanded.frost_aspect II
With Server Translations: Frost Aspect (II is missing)

Here's a link to the repo I used to test this, using Polymer and Server Translation API: https://github.com/firenh/enchanted_expanded

Hey! Could you try updating to latest version, as it should fix some issues!

yeah that fixed it, thank you!!!

authors: Patbox firenh

repo: NucleoidMC/Server-Translations


text:
Benchmark Dashboard

Updated by GitHub Action automatically
Summary 2023-01-13

base64-simd is the fastest base64 crate.
hex-simd is the fastest hex crate.

test

Moved to https://github.com/Nugine/simd-benches

repo: Nugine/simd


text:
FATAL: Error, 'depends.exe' failed to produce expected output. using tobix/pywine Docker container

Using simplest possible hello world program, print('Hello World!'), fails using wine python -m nuitka --standalone test.py with FATAL: Error, 'depends.exe' failed to produce expected output.. Without the standalone option it works fine and the output binary prints correctly, but of course no dependencies are included.
I am currently using the tobix/pywine container (run with docker run --rm -it --entrypoint /bin/sh tobix/pywine).
Trying to execute depends.exe manually with /opt/wineprefix/drive_c/users/root/AppData/Local/Nuitka/Nuitka/Cache/downloads/depends/x86_64/depends.exe results in no output with an exit code of 53. Not sure what that means but wine is definitely set as the interpreter so the problem isn't that it's being run without wine.

Nuitka version, full Python version, flavor, OS, etc.

# wine python -m nuitka --version
1.5.6
Commercial: None
Python: 3.11.3 (tags/v3.11.3:f3909b8, Apr  4 2023, 23:49:59) [MSC v.1934 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Python310\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: ~\AppData\Local\Nuitka\Nuitka\Cache\downloads\gcc\x86_64\11.3.0-14.0.3-10.0.0-msvcrt-r3\mingw64\bin\gcc.exe (gcc).

How did you install Nuitka and Python

Python installer is wget and run in wine, details in the dockerfile (https://github.com/webcomics/pywine/blob/main/Dockerfile). Nuitka installed with wine pip install nuitka.
I understand this may not be a supported usecase but I'm not seeing any immediately obvious reason it shouldn't work...

If you cannot get depends.exe to work, you are lost. My suspect would be that wine libraries are not all proper PE files, and wouldn't run on Windows anyway. Things could probably be hacked in such a fashion to circumvent that issue, but I do not care enough to even try.

Not sure if the 32 and 64 bit versions can do everything the other version can. I didn't expect them to be able to look at 64 bit binaries, but if that's wrong, we could detect wine probably somehow and special case that indeed.

repo: Nuitka/Nuitka


text:
A 1.7 version for the new update

Hi guys there isn't a new 1.7 version of the update but just for 1.8 and 1.9 I guess. I tried installing but it doesn't show any command so it is not working. Can someone give me a link for it?

New build was pushed to release page.
Note that 1.7.x branch is no longer under active maintenance so we cannot guarantee it will work properly. Remember to backup.
Also, please consider updating your server.

authors: OkappaAN RecursiveG

repo: NyaaCat/RPGitems-reloaded

license: mit

license_source: bigquery


text:
Maskot to cookie

Added the maskot hiding to the cookie as well, leaving none of the configuration up to JS.

Isn't {{call $.T "mascot_select"}} redundant? Since there's {{call $.T "mascot"}} already.

Yes it is, I'll remove it.

authors: mitki steindornatorinn

repo: NyaaPantsu/nyaa


text:
Install not working on Ubuntu  18.04

when I use the commandline as stated to download and install I get the following error at the end.

Saving to: 'openvpn-install.sh'
openvpn-install.sh              100%[====================================================>]  17.21K  --.-KB/s    in 0.01s
2020-01-17 15:42:11 (1.29 MB/s) - 'openvpn-install.sh' saved [17619/17619]
Unable to initialize the iptables/netfilter NAT table, setup can't continue.
Make sure that your system has iptables/netfilter available.
If using OpenVZ, ask your provider to enable full netfilter support.

I have now installed https://github.com/angristan/openvpn-install package without any issue or additional packages to be added, but your own script wont install.
I am not sure whats missing since its a new minimal build from yesterday.  I've used your script previously with Debian without any issues.

Sorry for the late (too late) response but I completely missed this issue.
Who is your server provider? What virtualization are they using?
Would be useful if you can provide the output of the following command in your system:
iptables -t nat -nL
This error message is shown by the script as a safeguard and can be removed, but it's there for good reason because if the NAT table can't be initialized, routing problems will arise.

Who is your server provider?

MCS Mail.ru

What virtualization are they using?

KVM

@zettend try running sudo openvpn-install.sh even if you are already root and report the results, please.

@Nyr
sudo: unable to resolve host debian-basic-1-2-10gb: Name or service not known Unable to initialize the iptables/netfilter NAT table, setup can't continue. Make sure that your system has iptables/netfilter available. If using OpenVZ, ask your provider to enable full netfilter support.

@zettend the message is self explanatory:

Make sure that your system has iptables/netfilter available

Run apt-get install iptables and it will work. The Mail.ru image doesn't have the iptables package installed by default.

authors: Nyr conligwx zettend

repo: Nyr/openvpn-install


text:
Blog updates

[ ] Title bigger on landing page
[ ] Split the landing page for the blog. 9/12 blog, 3/13 twitter feed?
[x] Ensure all blogs have an excerpt (@chealsye)
[ ] Increase font size on the blog, make the width narrower (to increase readability). E.g https://medium.com/art-marketing/meet-the-men-keeping-the-typewriter-alive-in-india-6c8191963aaf#.a9ihnrb0v

Excerpts added to all blogs now

I can make the remaining changes here pretty easily on the generated pages, but I need a bit more info about the website/app generator. I asked about this on #140 and will probably get a response there, but just noting for this particular issue that I need to know which files and templates are used to generate the blog page.

@GrantRVD can you update here too?

authors: GrantRVD JosephMcArthur chealsye

repo: OAButton/backend


text:
Add OP fuzzy matching to utilities

I created a utilities folder and added Mike's phonetics matching to use for the sectors and org types - I think this can develop as more countries are added and necessitate fuzzy matching.  The three countries we have now are so clean it's hard to really tell how deep we'll have to get into this.

Pull Request Test Coverage Report for Build 6510270517

15 of 22 (68.18%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.3%) to 94.6%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hapi/pipelines/utilities/text_parsing.py
11
18
61.11%

Totals

Change from base Build 6500576500:
-1.3%

Covered Lines:
473

Relevant Lines:
500

💛  - Coveralls

I'm pulling these changes into HAPI-252, so will close and create a new one for that branch!

authors: b-j-mills coveralls

repo: OCHA-DAP/hapi-pipelines


text:
Spectroscopy and asl post processing tools

ASL (ARTERIAL spin labelling) and Spectroscopy is important for neuroimaging and other areas
community: it wil make ohif viewer stand alone one stop solution for neuroimaging and other advance imaging and would make the imaging less vendor dependant.

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

@sedghi Sorry about delay. How many cases you would want? I can share them as anonymised cases through email.

Anything would be helpful

authors: DrAkshaykumar sedghi

repo: OHIF/Viewers


text:
Feat 1441 [WIP] Adding support for viewport groups and mapping loaded studies to viewport groups

PR Checklist

[x] Brief description of changes
[ ] Links to any relevant issues
[ ] Required status checks are passing
[ ] User cases if changes impact the user's experience
[ ] @mention a maintainer to request a review

Changes

Adding module to support representing viewport layouts using standard DICOM notation (and thus introduce support for advanced viewport layouts)
Adapting redux viewport storage to support advanced layouts (instead of only grid layouts) with minimal API change impact;
Adapting viewer initialization logic to:

Support predefined layouts and viewport groups;
Support loading of multiple studies (fix of study load issue);
Support mapping loaded studies to predefined viewport groups;

Links
Please try the following link on your local environment:

http://localhost:3000/longitudinal-viewer/1.3.6.1.4.1.25403.345050719074.3824.20170126083429.2;1.3.6.1.4.1.25403.345050719074.3824.20170126082902.1
Note that two studies are loaded and the most recent (2015) in on the two left panes while the older one (2014) on the other two right panes;

Notes

This is a WIP;
In order to render the new advanced layouts UI changes are still required. For now, the UI only understands standard grid layouts (mostly HTML and CSS changes needed to make use of the new layout data available from redux storage);
Some unit tests are still to be updated;

Closing because we won't get to this in this version

authors: emfol swederik


text:
Sanity check prepending '.' on extension list.

A small annoyance.

Ah! I see the story here! So you do html,htm,php instead of .html,.htm,.php.
Roger that. Thanks for the PR. I'll probably tweak this a little so that the prepending happens outside of the loop. Micro-optimisations for the win! But every bit I can take out of the loop, I will :)

Hi there. In future can you please PR from feature branches? Thanks.

Hi again,
Please see https://github.com/OJ/gobuster/compare/add-dots?expand=1 for an adjusted implementation. Instead of your approach it does the following:

Checks for the . using a char compare instead of a string prefix check.
Prepends the . during the startup rather than doing it every time a word in the wordlist is attempted.

Please take a look at let me know if this works for you. Thanks!

I've added the fix to master.
Closing.

repo: OJ/gobuster


text:
Automatisierte Tests

Routinen für das Testen der Website auf mögliche Fehler schreiben.

Betrifft nicht unbedingt nur die Homepage sondern auch Bundles von OKTO/RS.


text:
Phrase Check

mnemonic check before finishing the new account would be great to avoid false copied phrases and later problems with restoring the wallet

Covered on https://github.com/OLSF/carpe/issues/23
Thanks!

authors: McErebos soaresa

repo: OLSF/carpe


text:
🛑 Africa Mobile Site is down

In 17ad472, Africa Mobile Site (https://m.one.org/us) was down:

HTTP code: 403
Response time: 75 ms

Resolved: Africa Mobile Site is back up in ee4e50c.