-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
package fetching: elide errors from unpacking that relate to excluded file paths #17460
Copy link
Copy link
Closed
Labels
bugObserved behavior contradicts documented or intended behaviorObserved behavior contradicts documented or intended behaviorcontributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig build systemstd.Build, the build runner, `zig build` subcommand, package managementstd.Build, the build runner, `zig build` subcommand, package management
Milestone
Metadata
Metadata
Assignees
Labels
bugObserved behavior contradicts documented or intended behaviorObserved behavior contradicts documented or intended behaviorcontributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig build systemstd.Build, the build runner, `zig build` subcommand, package managementstd.Build, the build runner, `zig build` subcommand, package management
Type
Fields
Give feedbackNo fields configured for issues without a type.
Extracted from #17392.
If any of the file paths associated with these errors:
zig/src/Package/Fetch.zig
Lines 1080 to 1100 in f7bc55c
would be excluded by this filter:
zig/src/Package/Fetch.zig
Lines 1500 to 1518 in f7bc55c
then don't report those errors.
Above, I linked to the code related to tarball unpacking, but the same needs to be done for the other kinds of unpacking too: