MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
_global_index_store/v5/units/empty.swift.o-3NQIJGOI98742': No such file or directory
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
failed to read unit file /private/var/tmp/_bazel_jiangchao/11a172fb0b7bb90e1ea6fdb4f5a93109/rules_xcodeproj.noindex/build_output_base/execroot/main/bazel-out/_global_index_store/v5/units/RaiseToListen.swift.o-2QLMTAJ88Y73J -- Failed opening '/private/var/tmp/_bazel_jiangchao/11a172fb0b7bb90e1ea6fdb4f5a93109/rules_xcodeproj.noindex/build_output_base/execroot/main/bazel-out/_global_index_store/v5/units/RaiseToListen.swift.o-2QLMTAJ88Y73J': No such file or directory
Thanks & Regards
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the reported failure to read Swift unit files under Bazel's bazel-out/_global_index_store/v5/units path, including RaiseToListen.swift.o-2QLMTAJ88Y73J and empty.swift.o-3NQIJGOI98742. Reproduce the missing-file error and determine the conditions under which the generated unit file is absent; done means the reported unit-file read failure no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100