Skip to content
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

Merge remote-tracking branch 'NixOS/master' into lazy-trees #4

Draft
wants to merge 1 commit into
base: lazy-trees
Choose a base branch
from

Conversation

bb010g
Copy link

@bb010g bb010g commented Jan 11, 2023

figured i'd share this; think I got the merge correct? this merge includes the new error throwing code.

@bb010g bb010g requested a review from edolstra as a code owner January 11, 2023 08:38
@bb010g
Copy link
Author

bb010g commented Jan 11, 2023

This is way less relevant now, but from reviewing git diff bb010g/lazy-trees..edolstra/lazy-trees, there are a few places I think you missed with regards to errors (e.g. src/nix/flake.cc). I'd recommend comparing the behavior of this PR's src/libexpr/primops/patch.cc in particular; I think switching over to state.error gives better diagnostics. (General thing I noticed: Primops are currently called with noPos, so including that in traces will cause an unknown location to be reported. The primop call site is automatically added to any trace, so primops only need to worry about including other positions in their error traces.) src/libcmd/installables.cc line 428 caught my eye also; this line was specifically changed in 1123c42 in response to code review, but your merge reverted that. Anyways, the majority of our changes were the same, which is neat. Feel free to close this whenever you like.

@Artturin
Copy link

@bb010g Eelco has been keeping the branch very up to date recently so this can be closed

I checked that the merge revert has been fixed.

@bb010g
Copy link
Author

bb010g commented Sep 23, 2023

@bb010g Eelco has been keeping the branch very up to date recently so this can be closed

I checked that the merge revert has been fixed.

I'll close this after checking the thoroughness of the current lazy-trees error handling (I remember Eelco's merge being a bit less through than mine when diffing); thanks for the reminder. That'll be in a separate PR anyhow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants