jiebi/CodeConvo huggingface dataset:
I started grafana-agent in flow mode, and tried to access the http API at http://localhost:. Unfortunately, instead of providing a web interface to debug the current list of components, I get a "404 page not found". Steps to reproduce the behavior: grafana-agent in flow mode. port via HTTP I'd expect grafana-agent to ship with the web interface. Please run and paste the result.
It looks like is what's building the frontend. Unfortunately, the web interface seems managed by yarn (and has a ), so we'd need to first provide a . I tried to have resolve the dependency, but it seems it's not able to:
I manually patched things in to bump to a more recent version, compatible with the react version that's mentioned in , but ugh, I'm not really sure why it's that way. I'll ask upstream.
yeah, sorry, I don't use flow mode (yet?) and the nixos module does not support it either, as far as I am aware. I can try looking into it as well, first, before you raise an issue upstream. While the nixos module might lack support for it (for now?), I believe we should try fix it nonetheless :)
Yeah, we should probably have a second NixOS module for flow mode, it's very different and the existing config structure doesn't make much sense - for now I just did ship my own custom systemd unit for it: But yeah, without the web ui it's quite annoying to debug, so we should probably get that sorted out first, before providing a module and getting more people to use it.
fyi
I tried to move it over, but still seems to be terribly slow when trying to resolve deps and not being able to, so I guess we should stay with yarn.
We should prefer yarn simply due to upstream having an instead of a :) ^
The packages and are outdated () and have been replaced by the package (). To update a derivation just replace those two packages by as a build input. The following packages depend on and/or : [x] openmpi (fixed in ) [x] (does not find librdmacm in the configure phase when compiled against rdma-core) [x] (infiniband support seems to be defunct. configure does not check for IB libs and it is not linked against any of the required libs, libibverbs or librdmacm) [x] (RDMA support was removed from )
Steps to reproduce the behavior: localstack (from unstable) (version 3.2.0) localstack 2.3.0 works and so does (tagged because you bumped the version) (the channel is slightly messed up. I am using 23.11 but with flakes) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The new version requires too many dependencies to package up in a reasonable time frame and even includes circular ones. contains a revert to 3.0.0 which builds for me and shows the usage. Can you take a look if that works for you?
Sorry for the delay! Yes, the revert works well for me! Thank you!
Package name: mongodb-compass Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 1.43.0 Current version on the stable/release channel: 1.43.2 <!-- 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]:
Describe the bug For some reason neither of nix-env, nix-build or nix-shell compile Lean standard library, i.e. there are no .olean files. This results in abysmal performance even on trivial code, because every time it needs to recompile entire library in memory. Also, there is no leanstatic.a installed. To Reproduce Steps to reproduce the behavior: Expected behavior There should be compiled .olean files. Additional context Building Lean manually using compiles standard_library by default without issues. Also, there was no such issue on older NixOS. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Turned out that compiling standard_lib was included in tests. Adding should fix the issue.
Except that 39 tests have failed :disappointed:
This patch fixes all remaining issues, which proves that in NixOS 20.09 expression for Lean is broken:
Describe the bug I'm unsure what the error is, but it seems to relate to ulauncher being unable to find the project path, whatever that may be. To Reproduce Steps to reproduce the behavior: Expected behavior For Ulauncher to start normally Additional context This is the error message I get: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(miyuki): nixpkgs: Maintainer information:
See the PR linked above. The issue is that the ulauncher package must be installed via , , , or something similar. Using does not work (for reasons explained in the patch). The PR both updates ulauncher and adds a note to explain what's going on to Nix users trying out the package. I think it would be a good idea to create a NixOS module for Ulauncher. I might be able to do this after I finish exams in a couple weeks.
Alright guys, the real solution here is to just use rofi. With a little work you can make it look pretty good and with a little extra work one could easily make it look similar to ulauncher. Here is my config I tried to fix this issue up but it seemed to work for maintainers thus it was the end of that story
Hello ulauncher package maintainer here. This definitely shouldn't be the end of the story. I do want to get these issues fixed. The problem is that ulauncher wants to store paths to its assets in a config file within . Typically we'd just let it use paths for everything, but that would cause ulauncher to break if we update the derivation then garbage-collect the old paths in . I also use Rofi right now, and it works. But I really want the plugin ecosystem of Ulauncher, so I'm motivated to fix this situation. Perhaps we could modify the current package to allow decoratively specifying the file contents (like ), which would allow the package to be used without messing with system state? Maybe we could even create something like and a NixOS module?
Perhaps this is a good fit for a home-manager module?
Buck as installed via nix reports with an older release version than the one listed in its nixpkgs My guess is that is probably the correct version. The issue here is that IIRC buck Expected behavior 's output should match the version rerefenced in the build file. Notify maintainers
I did try to investigate by bumping buck to its latest release that should be Python3 compatible but didn't get very far as I am unfamiliar with the build system. But maybe the patch helps With this I encountered a failure at the end of the build
buck now generates a hash for build outputs
This tracks the conversion of from DocBook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.
This tracks the conversion of from Docbook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.
I opened a PR for and : PTAL, thanks in advance for reviewing :-)
Project description Ente's 2FA app. An end-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups. Works offline. You can even use it without signing up for an account if you don't want the cloud backups or multi-device sync. Metadata homepage URL: source URL: license: AGPL-3.0 license platforms: linux, windows, android, ios, apple silicon macOS, web Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Describe the bug has , preventing it from being used on other platforms, particularly Darwin in my case. To Reproduce nix-shell to get this error: error: Package ‘postgis-2.5.2’ in is not supported on ‘x8664-darwin’, refusing to evaluate. Expected behavior Produce a postgresql-and-plugins package with postgis available. Additional context Simply allowing doesn't work immediately because PostGIS' build system is quirky. There was some relevant-looking discussion on . Metadata system: host os: multi-user?: sandbox: version: channels(lukeworth): nixpkgs:
Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:
It looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).
Yes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.
I see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3
Exim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix.
Project description As discussed in is now EOL and the dev's have moved their effort to . As per the in order for it to work specific need to be set up. We can probably do something similar to what we do for the expression: Metadata homepage URL: source URL: license: GPL3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For people who subscribed to this issue: I opened to add streamcontroller
Yes. We have a package which is what I tried, but since it’s a thin wrapper around it’s possible that it’s still not built with the right options. Also I’ve noticed these messages from : does not show the extension, and GLX applications fail to start. Originally posted by in I probably merged , too early. I'm not totally sure this is working properly.
This is pretty much a help wanted because I lack the depth of knowledge and hardware to help anymore with Nvidia things. My goal with finishing was that it could be possible and improved upon. i.e packages are built with the capability etc.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
The last few evenings, I have tinkered around a bit. I was not successful so far. Here are my findings: I have set the following options: This page says that there is no acceleration support for xwayland and nvidia yet but glxgears fails to start, so I think this is another issue There are multiple versions of : One from the egl-wayland package, the other from nvidia-x11 package. As the one in is loaded, I tried to replace it with the one from egl-wayland. Though, the result is the same with both. When starting an application, which would use acceleration, I can observe this line in the kernel log: Using , I can see that is accessed, though one of the calls fails: one more thing: looking at , gnome-shell is listed. Maybe it has working acceleration? Edit: Got a bit further: Found a reference to an additional directory, which is used to look up libraries: Creating a file in there: with the file in /run/opengl-driver/lib/libnvidia-egl- being replaced by the one from egl-wayland package. Now the error in xwayland is just a warning: I can run a wayland native terminal, but still fails If you have any suggestions, what to try next, I would be glad to give it a try.
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 .
I'm trying to get this working as well. However I can't even get the session chooser in GDM in 20.09. Is it only working in unstable? Any tips? Here's my config
With this overlay and the 470.42.01 driver, nvidia is usable with xwayland. :tada: , unigene-valley and so far every game I started on Steam. Only issues I have so far are that chrome does not start properly Workaround is to start it with some options: and in CSGO there is noticeable input delay.
I've updated to the latest nixos-unstable () which includes updated & , but I'm still facing issues. While it's generally working I have problems with some apps. : : : Additionally in my system logs I can see: & are both working. My relevant config: I also tried using an overlay to apply the new meson flags from overlay: Is there anything else I need to set up?
also fails with
I have a very similar setup as and am experiencing precisely the same errors. I'm not sure whether it's an issue with gnome, my particular config, or what. Things work fine when running in an X session.
:thinking: I don't see anything missing with your config . I have updated my config to and removed the overlay. and are producing the same errors, and chrome won't function properly unless started with and are working for me, as well as and and . Note: Seam is installed via but this should only be relevant for running games inside steam, not steam itself.
I came here because I'm experiencing the same as and Can't launch Steam or Kitty under Wayland: nvidia: 470.42.01 xwayland: 21.1.2 Config is virtually identical to
I found this issue because I had the same problem as After reading , I tried to create a different file (listed in the end). And that solved my problem. With this file, I can open steam. However, alacritty still has an error. Maybe that relates to another . The cause of this problem is that even though both and packages provide , cannot be found without a json file. The says: So, maybe we should add a json file /usr/share/egl/eglexternalplatform.d /xxx.jsonnvidia-x11egl-waylandlibnvidia-egl-wayland.solibnvidia-egl-, gnome setting says my video card is "Unknown". In the end, I will post my related config:
I filed this issue to see if we can patch to look in the right place: If we can't get it to look in then we should probably just add the etc symlink in the nixos module so that this works correctly for end users out of the box. I'll send an initial PR shortly and will update it in that egl-wayland issue gets a useful answer (or if there's another way to patch a closed source SO that I'm not thinking of).
BTW, I can confirm the different results. When I override nvidia's with our "upstream" one, I get more info in , but I'm not sure if there are other functional differences. Not sure what I would've expected, but it nags me that there's a difference.
PR:
Interesting, there IS a way to override the egl_externaplatform search path(s):
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
would this still be an issue after ?
I think it needs and
I am taking over as I've been using that setup as a daily driver and have a rough working understanding of the pieces fitting together. And to confirm, the general problem here, that is addressed in , is EGLStreams working in Wayland environment with the NVIDIA driver (aka, it doesn't now because we don't "wire up" NVIDIA's egl driver per egl-wayland's expectations).
That is pretty tangential to NVIDIA having a driver that supports GBM allocation and "wiring it up" (an extra piece included in ), and it being discoverable (whatever I send to replace ). Hope that helps.
Also, to reiterate, is good to merge independently on it's own and will resolve this issue. Separately, a replacement for will be necessary for the ideal Sway scenario without users having to set an extra env var.
I thought the point of the new Nvidia driver was to finally move away from EGLStreams? Is EGLStreams used by the new stable driver at all?
I don't know? It doesn't really matter, we should still fix it? Like, the fundamental issue is that we're simply not installing the Nvidia driver correctly for NixOS when it comes to these important configuration JSON files. Plus, it's not like everything is going to immediately switch to GBM, drop EGL, know about the env var, on and on. That, and the wiring for GBM is in that PR and I'm not splitting them apart at the current merge rate.
Describe the bug Build fails when trying to install . I get: To Reproduce Expected behavior The package should install without error. Metadata Maintainer information:
cc
Related to
Tried the following: It doesn't even bother about the C-core Version 6 that I asked: What am I doing wrong ?
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 . 3. Ask on the on .
Refreshed. My PR will fix this issue. Thanks for your patience.
Describe the bug is currently in nixpkgs master. It was released in July 2018. was released in October 2019. It contains a few improvements and may also contains fix for some vulnerabilities: Is there a reason to keep the old version in nixpkgs, other than a lack of manpower? I'd be happy to do this work, but I just want to be sure that I was not starting a long, difficult and redundant work. I already tried a "naive" bump of the and but it does not work, mostly because most of the patchs are not valid anymore.
This was solved by cc.
Thank you for continuing this work!
Project description ET: Legacy is an open source project based on the code of Wolfenstein: Enemy Territory which was released in 2010 under the terms of the GPLv3 license. Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin
I got a derivation to work: This is for the 32-bit build, client only. Run and use the binary. Planning to properly package it and contribute to nixpkgs, but since it's my first package it'll require some more time. Also planning to get the server and omnibot working.
I marked this as stale due to inactivity. &rarr;
Still interested.
My version of derivation gist doesn't seem to work now that I've upgraded to NixOS 22.05. Haven't had time to investigate too much yet. Whether I try to join an online game server or host a game, I get the below error:
This adaptation of gist is working for me. It's currently for the 32-bit Linux version only, so produces a package . There is an option to use the mod libs built by the ET Legacy project (CI pipeline) or compile them locally.
Hi guys Based on gist I did compiled using NixOS VM Machine it runs fine but there a small quirks there Date is not set correctly it is set to beginning of the time :D Also does ignores manually set env variables ?
Added those 2 in etlegacy*.nix files ` Those 2 should fix issue with correct compile date and naming scheme to build non package But it does not Am I doing something wrong ? :D
Package created and pull request created. Just waiting on PR to be approved so the package can be to nixpkgs.
Is it normal I cannot find the package in the unstable channel?
I think there may be some delay as it migrates to the unstable channel, and then into 23.05.
it seems to be in unstable now.
fails to install on . It worked before the recent update. It fails early on in the check phase. I'm guessing the fact that I have to build it from source at all is because it also fails everywhere else, so there's no cached build to download. Try to install on system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Hmm, the tests worked just fine for me on
Do they work for you now? What's kinda weird is that I never get an error message or anything. You see in the output I posted above, there's just loads of dots. It kind of sits there printing dots for a while and then it looks like it just times out or something.
For what it's worth if I put in the derivation, the resulting player is perfectly functional at least for my purposes. Haven't tested every feature or anything though.
I think it crashes during the test. I will try bisecting.
Bisecting was inconclusive because I ran out of resources when building webkitgtk.
What commands did you run? I have a server with plenty of resources that's just sitting idle at the moment, I could try run it on that.
but I guess it might make more sense to skip the builds where dependencies failed by running something like:
Cool, I've been running this for a while, for what it's worth it's currently narrowed it down to between and .
I'll let you know in the morning when it's finished.
The original bisect command I ran didn't take into account the case where dependencies failed to build, so I had to run it again with a script like the one you suggested. Here's the output of :
FWIW I managed to build it by setting in an overlay. Works for me, but I wouldn't suggest that this is done in the Hydra build of course!
Yeah, we should probably add in the expression if this still occurs.
I get quite a bit further, attempting to build rather than . The entire test suite finishes, then reports three test failures related to icons and GTK / GDK.
Seems like the tests are failing again
I marked this as stale due to inactivity. &rarr;
EDIT: Kindly ignore this comment, didn't notice that I was using the deprecated repository. Hi, I'm encountering the same errors as reported previously. In case anyone else is experiencing the same, I was able to fix them using:
The ssmtp program is dead/unmaintained. The commonly suggested substitute is msmtp. While [home-manager has a module for msmtp][1], NixOS lacks one. [1]: Let's: [x] Done in We should probably also: [x] Remove the ssmtp NixOS module and add migration instructions to the release notes () [x] Remove the ssmtp package ()
I marked this as stale due to inactivity. &rarr;
The module works really well. Thanks for the module