jiebi/CodeConvo huggingface dataset:
Change:
pushd dist # See https://peps.python.org/pep-0491/#escaping-and-unicode <del> local -r pkg_name="${pname//[^[:alnum:].]/_}-$version" </del> <ins> local -r pkg_name="${pname//[^[:alnum:].]/_}" </ins> local -r unpack_dir="unpacked" <del> local -r metadata_file="$unpack_dir/$pkg_name/$pkg_name.dist-info/METADATA" </del> <ins> local -r metadata_file="$unpack_dir/$pkg_name*/$pkg_name*.dist-info/METADATA" </ins> # We generally shouldn't have multiple wheel files, but let's be safer here for wheel in "$pkg_name"*".whl"; do @pythonInterpreter@ -m wheel unpack --dest "$unpack_dir" "$wheel" rm -rf "$wheel" <del> _pythonRelaxDeps "$metadata_file" _pythonRemoveDeps "$metadata_file" </del> <ins> # Using no quotes on purpose since we need to expand the glob from `$metadata_file` _pythonRelaxDeps $metadata_file _pythonRemoveDeps $metadata_file </ins> if (( "${NIX_DEBUG:-0}" >= 1 )); then echo "pythonRelaxDepsHook: resulting METADATA for '$wheel':" <del> cat "$unpack_dir/$pkg_name/$pkg_name.dist-info/METADATA" </del> <ins> cat $metadata_file </ins> fi <del> @pythonInterpreter@ -m wheel pack "$unpack_dir/$pkg_name" </del> <ins> @pythonInterpreter@ -m wheel pack "$unpack_dir/$pkg_name"* </ins> done # Remove the folder since it will otherwise be in the dist output.

Discussion:
is failing to remove requirements as requested by the setting of . Attempt to build Upon building: Tested on . to remove the dependencies as specifies. n/a n/a Latest committers to python-relax-deps- <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Some debugging: I'm fairly certain this is due to a naming issue with the whl. pkg_name () is set to based on some print-statement debugging. But the actual wheel that is produced is . Why are these names different? Why isn't the wheel named ?
Probably because the wheel name is based on the package metadata. Maybe we should just ignore the version during the matching?
Yes, we should.
Created a PR:
Closing now that has been merged.
Change:
<ins> { lib , buildPythonPackage , pythonOlder , fetchFromGitHub , fetchpatch , setuptools , cmdstanpy , numpy , matplotlib , pandas , lunarcalendar , convertdate , holidays , python-dateutil , tqdm , importlib-resources , pytestCheckHook }: buildPythonPackage rec { pname = "prophet"; version = "1.1.4"; format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "facebook"; repo = "prophet"; rev = "refs/tags/v${version}"; hash = "sha256-pbJ0xL5wDZ+rKgtQQTJPsB1Mu2QXo3S9MMpiYkURsz0="; }; patches = [ # TODO: remove when bumping version from 1.1.4 (fetchpatch { name = "fix-stan-file-temp-dest.patch"; url = "https://github.com/facebook/prophet/commit/374676500795aec9d5cbc7fe5f7a96bf00489809.patch"; hash = "sha256-sfiQ2V3ZEF0WM9oM1FkL/fhZesQJ1i2EUPYJMdDA2UM="; relative = "python"; }) ]; sourceRoot = "source/python"; env.PROPHET_REPACKAGE_CMDSTAN = "false"; nativeBuildInputs = [ setuptools ]; # TODO: update when bumping version from 1.1.4 propagatedBuildInputs = [ cmdstanpy numpy matplotlib pandas lunarcalendar convertdate holidays python-dateutil tqdm importlib-resources ]; preCheck = '' # the generated stan_model directory only exists in build/lib* cd build/lib* ''; nativeCheckInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "prophet" ]; meta = { homepage = "https://facebook.github.io/prophet/"; description = "A tool for producing high quality forecasts for time series data that has multiple seasonality with linear or non-linear growth"; changelog = "https://github.com/facebook/prophet/releases/tag/v${version}"; license = lib.licenses.mit; platforms = lib.platforms.linux; maintainers = with lib.maintainers; [ tomasajt ]; }; } </ins>

Discussion:
Project description Tool for producing high quality forecasts for time series data that has multiple seasonality with linear or non-linear growth. Metadata PyPI: homepage URL: source URL: license: mit platforms: x86_64-linux
Change:
--replace 'date -u' "date -d @$SOURCE_DATE_EPOCH '+%Y-%m-%d %H:%M:%S'" ''; <del> preConfigure = '' configureFlagsArray+=("--extra-cflags=-DXBOX=1 -Wno-error=redundant-decls") '' + # When the data below can't be obtained through git, the build process tries # to run `XEMU_COMMIT=$(cat XEMU_COMMIT)` (and similar) '' echo '${finalAttrs.version}' > XEMU_VERSION ''; </del> <ins> preConfigure = '' configureFlagsArray+=("--extra-cflags=-DXBOX=1 -Wno-error=redundant-decls") '' + # When the data below can't be obtained through git, the build process tries # to run `XEMU_COMMIT=$(cat XEMU_COMMIT)` (and similar) '' echo '${finalAttrs.version}' > XEMU_VERSION ''; </ins> preBuild = '' cd build substituteInPlace ./build.ninja --replace /usr/bin/env $(which env) ''; <del> installPhase = let installIcon = resolution: '' install -Dm644 -T ../ui/icons/xemu_${resolution}.png  $out/share/icons/hicolor/${resolution}/apps/xemu.png </del> <ins> installPhase = let installIcon = resolution: '' install -Dm644 -T ../ui/icons/xemu_${resolution}.png  $out/share/icons/hicolor/${resolution}/apps/xemu.png ''; in '' runHook preInstall install -Dm755 -T qemu-system-i386 $out/bin/xemu '' + (lib.concatMapStringsSep "n" installIcon [ "16x16" "24x24" "32x32" "48x48" "128x128" "256x256" "512x512" ]) + "n" + '' install -Dm644 -T ../ui/xemu.desktop $out/share/applications/xemu.desktop runHook postInstall </ins> ''; <del> in '' runHook preInstall install -Dm755 -T qemu-system-i386 $out/bin/xemu '' + (lib.concatMapStringsSep "n" installIcon [ "16x16" "24x24" "32x32" "48x48" "128x128" "256x256" "512x512" ]) + "n" + '' runHook postInstall ''; </del> meta = { homepage = "https://xemu.app/";

Discussion:
Generated desktop file for package is missing categories. It can be easily solved by adding to and deleting list. I tested it, it works. But perhaps it would be better to patch desktop file to use /nix/store path as I saw other people do. It would be better to use provided desktop file, or at least recreate it. It is not a bug, but rather improvement request. I need categories set for my desktop, and it would be nice to have them out of the box. And I think it is better to use provided desktop file instead of creating a new one if possible. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
sha256FileURL: (newVersion) => `https://github.com/pulsar-edit/pulsar/releases/download/v${newVersion}/SHA256SUMS.txt`, x86_64FileName: (newVersion) => `Linux.pulsar-${newVersion}.tar.gz`, aarch64FileName: (newVersion) => `ARM.Linux.pulsar-${newVersion}-arm64.tar.gz`, <del> targetFile: new URL("default.nix", import.meta.url).pathname, </del> <ins> targetFile: new URL("package.nix", import.meta.url).pathname, </ins> }; async function utf16ToUtf8(blob) {

Discussion:
Package name: pulsar Latest released version: 1.118.0 Current version on the unstable channel: 1.117.0 Current version on the stable/release channel: 1.117.0 Notify maintainers
Sorry I'm super busy these days... I'll try to get back to this as soon as possible. In the meantime, please try the of this package if you can, and see if the resulting package build fine. Thank you!
i am not familiar with updateScript and not really urgently need the latest Pulsar version, but i think update request is a good way to keep actual nixpkgs's packages version.
Change:
githubId = 757752; name = "Jonas Heinrich"; }; <ins> ony = { name = "Mykola Orliuk"; email = "virkony@gmail.com"; github = "ony"; githubId = 11265; }; </ins> OPNA2608 = { email = "christoph.neidahl@gmail.com"; github = "OPNA2608";

Discussion:
Looks like there has been a new release this year: maintainer: cc it adds XDG portal support, which might be necessary for screen sharing on phosh and other Wayland clients.
PR:
I marked this as stale due to inactivity. &rarr;
Change:
index d5a67d2..19b7ffc 100644 --- a/shapely/geos.py +++ b/shapely/geos.py <del> @@ -61,127 +61,10 @@ def load_dll(libname, fallbacks=None, mode=DEFAULT_MODE): </del> <ins> @@ -61,127 +61,17 @@ def load_dll(libname, fallbacks=None, mode=DEFAULT_MODE): </ins> "Could not find lib {} or load any of its variants {}.".format( libname, fallbacks or []))

Discussion:
Describe the bug python38Packages.shapely does not build for me on darwin. It looks like the previous release, 1.7.0, did build on hydra (). I'm not sure if this is a difference depending on the version of shapely or on the version of macosx. To Reproduce Failure It looks like this store path is specifically being by a nixpkgs patch, but that the patch refers to a file that doesn't exist. Additional context The're no here: Notify maintainers Metadata
Ah, it's broken on hydra too, so it's not just me:
I think it's possible that the regression is related to how interact with
Change:
appgate-sdp = callPackage ../applications/networking/appgate-sdp { }; <del> apostrophe = callPackage ../applications/editors/apostrophe { pythonPackages = python3Packages; }; </del> ardour = callPackage ../applications/audio/ardour { }; ardour_7 = callPackage ../applications/audio/ardour/7.nix { };

Discussion:
Package name: apostrophe Latest released version: 3.0 <!-- Search your package here: --- Current version on the unstable channel: 2.6.3 Current version on the stable/release channel: 2.6.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
buildInputs = [ alsa-lib gtk3 libXScrnSaver libXtst mesa nss ]; <del> dontBuild = true; dontConfigure = true; unpackPhase = '' dpkg-deb -x ${src} ./ </del> <ins> unpackCmd = '' # If unpacking using -x option, there is a permission error dpkg-deb --fsys-tarfile $src | tar -x --no-same-permissions --no-same-owner; </ins> ''; installPhase = '' runHook preInstall <del> mv usr $out mv opt $out mv "$out/opt/Pocket Casts" $out/opt/pocket-casts mv $out/share/icons/hicolor/0x0 $out/share/icons/hicolor/256x256 </del> <ins> mkdir -p $out mv bin $out mv lib $out mv share $out cp $out/lib/pocket-casts/resources/app/icon.png $out/share/pixmaps/pocket-casts.png </ins> runHook postInstall ''; postFixup = '' substituteInPlace $out/share/applications/pocket-casts.desktop  <del> --replace '"/opt/Pocket Casts/pocket-casts"' $out/bin/pocket-casts  --replace '/usr/share/icons/hicolor/0x0/apps/pocket-casts.png' "pocket-casts" </del> <ins> --replace Name=pocket-casts "Name=Pocket Casts"  --replace GenericName=pocket-casts "GenericName=Podcasts App"  --replace Exec=pocket-casts Exec=$out/bin/pocket-casts </ins> makeWrapper ${electron}/bin/electron  $out/bin/pocket-casts  <del> --add-flags $out/opt/pocket-casts/resources/app.asar </del> <ins> --add-flags $out/lib/pocket-casts/resources/app/main.js </ins> ''; meta = with lib; {

Discussion:
Pocket casts was previously building but now fails since the electron version is insecure. The for the project however has "^17.0.0". Please run and paste the result.
The problem is that we are picking the AppImages, and the latest release is 0.5.0. The best thing to do would be asking the devs to publish a new release.
The author has 0.6.0 bumping the electron version!
working on this. Right now I have found some issues with this new version (problems unpacking the deb, no and probably need to create the file), but I hope to get them solved at least this week.
do you want to test it? . As there were some considerable changes and the latest version of Electron is working fine, I want to ensure the functionality hasn't been affected.
Yes let me give it a try!
I was able to build and run your branch. Login, playback etc all work. The only thing I noticed is it uses the default electron logo: ! Its been a while since I was able to run 0.5.0 but I believe it used the application logo.
Got it. I had to edit the to reflect the new changes, and it contained some edits to the desktop file. So it makes sense the default logo is being used here. Luckily the complicated part is fixed. EDIT: Never mind, it is working as intended. The file at contains the exact icon, as shown below: ! This is more of a package not including the original Pocket Casts icon on the dir. I will replace it with the original icon that is on the resources.
Just posted the PR on nixpkgs. Feel free to check the final changes and if everything looks fine, throw an approval.
Change:
</varlistentry> <varlistentry> <del> <term><option>--install-grub</option></term> </del> <ins> <term><option>--install-bootloader</option></term> </ins> <listitem> <del> <para>Causes the GRUB boot loader to be (re)installed on the device specified by the <varname>boot.loader.grub.device</varname> configuration option.</para> </del> <ins> <para>Causes the boot loader to be (re)installed on the device specified by the relevant configuration options. </para> </ins> </listitem> </varlistentry>

Discussion:
I was using gummiboot and struggling to figure out how to reinstall it. This option should be aliased and deprecated in favor of "--install-bootloader" or the like, and the manpage updated to be agnostic of the bootloader selected in , since the correct behavior is already in place (--install-grub reinstalls gummiboot properly).
Change:
scudcloud = callPackage ../applications/networking/instant-messengers/scudcloud { }; <del> shotcut = libsForQt514.callPackage ../applications/video/shotcut { libmlt = mlt; }; </del> <ins> shotcut = libsForQt5.callPackage ../applications/video/shotcut { }; </ins> shogun = callPackage ../applications/science/machine-learning/shogun { stdenv = gcc8Stdenv;

Discussion:
Shotcut in theory supports LADSPA plugins. However, LADSPA plugins are not found by Shotcut on NixOS version Install a bunch of LADSPA plugins (by listing them in ) Open Shotcut Add effects to a track Look for audio effects: no LADSPA plugins are shown Please run and paste the results.
cc maintainers
I tried to build shotcut and mlt with ladspa-sdk and set LADSPA_PATH, but did not manage to get the ladspa plugins working yet. ,-(
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
found out why: configure is using , which is not available, and therefore does disable ladspa. Preparing a PR.
Change:
stdenv.mkDerivation rec { pname = "openocd"; <del> version = "0.11.0"; </del> <ins> version = "0.12.0"; </ins> src = fetchurl { url = "mirror://sourceforge/project/${pname}/${pname}/${version}/${pname}-${version}.tar.bz2"; <del> sha256 = "0z8y7mmv0mhn2l5gs3vz6l7cnwak7agklyc7ml33f7gz99rwx8s3"; </del> <ins> sha256 = "sha256-ryVHiL6Yhh8r2RA/5uYKd07Jaow3R0Tu+Rl/YEMHWvo="; </ins> }; nativeBuildInputs = [ pkg-config ];

Discussion:
v0.11.0 of OpenOCD is over a year old, does anyone have time to update or add an unstable branch?
v0.11.0 seems to be the latest release (). I suggest asking upstream for a new release.
We don't update to unstable unless there is a good reason to do so. Do you have any?
Yes - there is no sign of a 0.12.0 release that I can see, and the software has been actively developed since the 0.11.0 release. There is currently open to update ElmerFEM for similar purposes. I’m not convinced that it should be on users or maintainers to ask upstream for a release number in cases like this.
That's a different case, since the person opening the PR indicated there is something they need from the unreleased version of the software. So let me repeat and rephrase my question: Do you have any reason why you want us to update OpenOCD to unstable? Any bug fixes, any features you are missing from the latest stable release?
Now that v0.12.0 is out, would you take action to update this? I want to see if any of the changes related to allow me to flash an atsamc21g18 that drives it’s SWD pins from a rpi.
Can you test
Change:
]; sha256 = (if cudaSupport then { <del> x86_64-linux = "sha256-TgIH7r1IXNkbOFSXvaKVbU9kL+TuQqxVrBge7iv2ykQ="; </del> <ins> x86_64-linux = "sha256-Vwl4hWGlFjk53M1ZkWY92x1vkSgzOvx8pBuw9BTVZSM="; </ins> } else { <del> x86_64-linux = "sha256-on14CAolJ3mvJmKxX2PE21BsYOJJFUSQuUOnOuVR2GQ="; aarch64-linux = "sha256-2tcIiQlMUKMc+juCy+dt37s+lFqr2pcVizCyYkkQtOM="; </del> <ins> x86_64-linux = "sha256-bGMqx7HnjQsIDJUcQMA5TridAAG5LfWKH3fQ+lKti7A="; aarch64-linux = "sha256-h7bFAXmvucuM0wwld50LpmVudeaPBzXdvI0rfcuZw/M="; </ins> }).${stdenv.system} or (throw "jaxlib: unsupported system: ${stdenv.system}"); };

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: -
Bisected to
Since then, updating both (currently v1.60 on ) and (to ) has not made any difference on this matter.
See
Change:
<ins> From fa3c39331d4ef56a13019f45d811bde1fc755c21 Mon Sep 17 00:00:00 2001 From: Bobby Rong <rjl931189261@126.com> Date: Sat, 25 Sep 2021 23:21:01 +0800 Subject: [PATCH] Fix session crash when taking screenshots with mutter 3.38 --- src/ScreenshotManager.vala | 5 ++--- vapi/mutter-clutter.vapi   | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/ScreenshotManager.vala b/src/ScreenshotManager.vala index 3ffb0123..388fee1a 100644 --- a/src/ScreenshotManager.vala +++ b/src/ScreenshotManager.vala @@ -354,12 +354,11 @@ namespace Gala { paint_flags |= Clutter.PaintFlag.FORCE_CURSORS; } -            unowned var data = image.get_data (); if (GLib.ByteOrder.HOST == GLib.ByteOrder.LITTLE_ENDIAN) { wm.stage.paint_to_buffer ( {x, y, width, height}, scale, -                    ref data, +                    image.get_data (), image.get_stride (), Cogl.PixelFormat.BGRA_8888_PRE, paint_flags @@ -368,7 +367,7 @@ namespace Gala { wm.stage.paint_to_buffer ( {x, y, width, height}, scale, -                    ref data, +                    image.get_data (), image.get_stride (), Cogl.PixelFormat.ARGB_8888_PRE, paint_flags diff --git a/vapi/mutter-clutter.vapi b/vapi/mutter-clutter.vapi index 5b778cb2..95de24be 100644 --- a/vapi/mutter-clutter.vapi +++ b/vapi/mutter-clutter.vapi @@ -7336,7 +7336,7 @@ namespace Clutter { [Version (since = "1.2")] public bool get_use_alpha (); #if HAS_MUTTER338 -		public bool paint_to_buffer (Cairo.RectangleInt rect, float scale, [CCode (array_length = false)] ref unowned uint8[] data, int stride, Cogl.PixelFormat format, Clutter.PaintFlag paint_flags) throws GLib.Error; +		public bool paint_to_buffer (Cairo.RectangleInt rect, float scale, [CCode (array_length = false, type = "uint8_t*")] uint8[] data, int stride, Cogl.PixelFormat format, Clutter.PaintFlag paint_flags) throws GLib.Error; public void paint_to_framebuffer (Cogl.Framebuffer framebuffer, Cairo.RectangleInt rect, float scale, Clutter.PaintFlag paint_flags); #else [Version (since = "0.4")] </ins>

Discussion:
When i try to take a screenshot of an area (STRG + PRINT), i hear the bell notification sound (that also comes when the disk is full) and nothing more happens (no screenshot). The third time i tried, the whole session crashed! I actually have a video of it: Steps to reproduce the behavior: screenshot with STRG + PRINT (not tested other methods) ??? crash actually taking screenshot that's the issue ;) Issue appeared after can you reproduce or should i get a log? system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
The issue is introduced in (though we are using Mutter 3.38). I will try to patch gala if possible, . Can confirm that the issue can be reproduced and by reverting the change the issue can be fixed. I will submit a PR in 48 hours.
Change:
environment.etc."pre-built-paths".source = writeText "pre-built-paths" ( builtins.toJSON [hello figlet stdenvNoCC] ); <ins> environment.variables = { SAMPLE = invokeSamples ./test/sample.nix; REFERENCES = invokeSamples ./test/invoke-writeReferencesToFile.nix; DIRECT_REFS = invokeSamples ./test/invoke-writeDirectReferencesToFile.nix; }; </ins> }; testScript = '' machine.succeed(""" <del> cd ${lib.cleanSource path} ./pkgs/build-support/trivial-builders/test.sh 2>/dev/console </del> <ins> ${./test.sh} 2>/dev/console </ins> """) ''; <ins> meta = { license = lib.licenses.mit; # nixpkgs license maintainers = with lib.maintainers; [ roberth ]; description = "Run the Nixpkgs trivial builders tests"; }; </ins> }

Discussion:
There is an issue in the test by . This line introduces a dependency on the contents of nixpkgs, making every change evaluate with a different hash. cc
Steps to reproduce:
You're absolutely right, but I don't think I see the impact of this fact. It's not recursed into (no /) and it's not even built by ofborg. The test needs to compare results, but perhaps the actual evaluation can be removed from it; injected as store paths by the test runner instead. It won't make the test easier to read :(
This currently impacts every ofborg evaluation. For example:
I have no idea how to solve this. Why would ofborg have a different hash for multiple evaluations? Cause it puts stuff in the nixpkgs path?
is the whole Nixpkgs source tree, which kinda always changes. Here's a solution . Not pretty but still quick to run outside the sandbox and solves this issue.
Still an issue ?
Ofborg doesn't rebase PRs so if the PR is based on a master that's of the wrong age, you'll still see this happen. Please check that the PR includes the improved test.
I did, and it's been more than 12 hours since the commit landed. At the same time my original repro doesn't see the issue:
It's a broader issue that applies to all NixOS tests, , but it went under the radar.
This seems to be fixed now. Thanks for looking into this!
Change:
<ins> #!/usr/bin/env nix-shell #! nix-shell -i bash -p jq nodePackages.node2nix # Get latest release tag tag="$(curl -s https://api.github.com/repos/jean-emmanuel/open-stage-control/releases/latest | jq -r .tag_name)" # Download package.json from the latest release curl -s https://raw.githubusercontent.com/jean-emmanuel/open-stage-control/"$tag"/package.json | grep -v '"electron"|"electron-installer-debian"|"electron-packager"|"electron-packager-plugin-non-proprietary-codecs-ffmpeg"' >package.json # Lock dependencies with node2nix node2nix  --node-env ../../../development/node-packages/node-env.nix  --nodejs-16  --input package.json  --output node-packages.nix  --composition node-composition.nix rm -f package.json </ins>

Discussion:
Project description Libre and modular OSC / MIDI controller Metadata homepage URL: source URL: license: GPLv3 platforms: electron
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Still would be cool.
I marked this as stale due to inactivity. &rarr;
still relevant
I marked this as stale due to inactivity. &rarr;
Still relevant
I've opened a PR to add this package! See