-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update nix configuration #8452
Update nix configuration #8452
Conversation
I've figured out why those two tests are failing, they seem to rely on the fact that the variables are captured and in parallel. Is this expected? |
@angaz I clearly missed this, so sorry it's been sitting for so long. I'll try to take a look today. |
It's been such a long time. Fixing the tests was done already, so that's not relevant anymore. Should I update the branch again? |
1c00f99
to
bcf2b55
Compare
I'm running the tests locally because the CI is quite slow on GH and I see there are tests failing trying to find addresses for all the interfaces, which is interesting. I'm not sure what to do about it, but it seems like the test is possibly wrong.
|
It looks like this is also happening in the CI. I think everything else is good. I don't know what to do about the tests. |
if you wouldn't mind, it looks pretty much good to go from my perspective, so just a matter of getting the tests to pass |
I do not understand this code or these tests. Is the code wrong or are the tests wrong? I have no idea. So I can't say if I know how they need to be fixed. Are they just broken for the nix-run tests or are they also broken for everyone else? |
I understand the code and the failure, but not how to fix it Loki uses your local network interface to find your IP when setting up memberlist communication with the other processes. This normally works fine as there's a default set of interface names that covers the standard nic naming strategies across most OSes. I'm assuming in whatever sandbox nix is building in there is no networking interface, or it's named something totally different, I'm just not sure how to discover that? |
ddc4dcb
to
4eb813f
Compare
@angaz sorry for the long delay on this. I'm going to look into this a bit today. FYI I've force pushed to your branch to rebase these changes on the latest in |
Yeah, cool, sounds good. No problem. You can take over if you need to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for helping fix this! It's easy for this nix stuff to get neglected as it has a smaller user base. I would love continuing help in the future keeping it up to date!
aedda49
to
25ea572
Compare
The main reason for this is when running logcli or promtail, I don't want to wait for loki to compile as well. * This also refactors the folder structure under the nix folder to better organize packages and overlays. * This also create new apps using the now top level packages.
25ea572
to
cedd715
Compare
Fix nix configuration (mainly failing test), and break up various binaries (ie. logcli, promtail, loki, etc.) into their own pakcages. --------- Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>
Fix nix configuration (mainly failing test), and break up various binaries (ie. logcli, promtail, loki, etc.) into their own pakcages. --------- Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>
Hi.
I found the nix configuration here to be a bit broken, it looks like it hasn't been updated in a while, so I had a look at fixing some of the issues. It creates a workable dev environment now. I also fixed the linter errors I came accross.
One problem I have run into is that some of the tests are failing, so I can't actually build the packages with this setup. I tried it without running the tests, and it does build, but the default is to run the tests. We can disable that if we don't want to run the tests at build time.
Checklist
CONTRIBUTING.md
guide (required)CHANGELOG.md
updateddocs/sources/upgrading/_index.md