Add path to errors
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- deno, typescript
- 领域
- cli
调研方向
Start with lib/usePantry.ts and libexec/sort.ts for the missing-pantry error, then inspect the cellar failure path referenced through useCellar.ts. Trace how pantry and installation paths are selected; done means the relevant path is printed for both missing-package and cellar repair errors.
由索引模型根据 Issue 内容生成。
描述
One thing I've noticed about making packages is that when there are errors it's hard to know exactly where I should go hacking. The reason why is because I know pkg does some magic when you cd to the pantry repo directory. So I'm just confused about what exactly is going on when it can't find things.
Here's some examples.
> pkg build khronos.org/opencl-icd-loader
error: Uncaught Error: Not in pantry: khronos.org∕opencl-headers
https://github.com/teaxyz/pantry#contributing
throw new TeaError('not-found: pantry: package.yml', {project}, )
^
at https://deno.land/x/libtea@v0.6.2/src/hooks/usePantry.ts:49:13
at project (https://deno.land/x/libtea@v0.6.2/src/hooks/usePantry.ts:50:5)
at Object.getDeps (file:///opt/tea/tea.xyz/brewkit/v0.44.1/lib/usePantry.ts:30:21)
at file:///opt/tea/tea.xyz/brewkit/v0.44.1/libexec/sort.ts:24:29
at ascend (https://deno.land/x/libtea@v0.6.2/src/plumbing/hydrate.ts:62:31)
at ascend (https://deno.land/x/libtea@v0.6.2/src/plumbing/hydrate.ts:88:19)
at eventLoopTick (ext:core/01_core.js:183:11)
at async go (https://deno.land/x/libtea@v0.6.2/src/plumbing/hydrate.ts:93:5)
at async hydrate (https://deno.land/x/libtea@v0.6.2/src/plumbing/hydrate.ts:102:7)
at async file:///opt/tea/tea.xyz/brewkit/v0.44.1/libexec/sort.ts:23:13
I know why the above error is thrown. But it seems that sometimes if I build something locally that I don't get the error. It would be nice if the error told me the path of the pantry because I want to manually add the missing project so I can build the next one I'm working on.
Here's another example. I have no idea what this does, so I ran it to find out.
> pkg cellar -R
repairing: micro-editor.github.io
repairing: deno.land
repairing: deno.land
repairing: deno.land
repairing: deno.land
repairing: libpng.org
repairing: khronos.org/opencl-headers
repairing: zsh.sourceforge.io
repairing: pcre.org
repairing: pcre.org
error: Uncaught Error: not-found: pcre.org=2.0.0
throw new Error(`not-found: ${pkgutils.str(installation.pkg)}`)
^
at Object.resolve (https://deno.land/x/libtea@v0.6.2/src/hooks/useCellar.ts:78:13)
at eventLoopTick (ext:core/01_core.js:183:11)
at async link (https://deno.land/x/libtea@v0.6.2/src/plumbing/link.ts:9:24)
So something is broke with pcre.org. But I don't know which one, the main install or the repo. Well, I played with it and figured out it was the main install. But it would be nice if paths like this were printed.
- 主要语言
- TypeScript
- 星标
- 65
- 派生
- 16
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
pkgxdev/brewkit 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 3/5 1-2 天 新手友好度 52/100
-
难度 5/5 一周以上 新手友好度 25/100
-
难度 3/5 1-2 天 新手友好度 35/100
相似的 Issue
-
blocklist removal
难度 2/5 1-3 小时 新手友好度 65/100
MetaMask/eth-phishing-detect#296544 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
pastelsky/bundlephobia#1122 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100