This message was deleted.
# report-bugs
s
This message was deleted.
s
any idea of how to debug?
ah, some additional helpful context: node version is 20.3.1, npm version is 9.6.7, normal git operations still work (git pull/fetch etc.), and passthrough from graphite to git seems to work fine (gt push, etc.)
p
Thanks for the info! @Jacob Gold might know what's going on here
s
hi, using graphite
0.20.21
this is still happening for me ๐Ÿ˜ž
p
Hey @Sidharth Menon! Sorry about that - we'll take a look and get back to you!
s
hello. on graphite latest and this is still happening to me ๐Ÿ˜ž. really unfortunate experience here - is
gt repo sync
not a recommended workflow?
although the latest stacktrace seems to be more helpful:
Copy code
โฏ gt rs --debug
2023-07-13T17:08:27.790Z: Reading cache seed data...
2023-07-13T17:08:27.809Z: Loading cache...
2023-07-13T17:08:27.809Z: Building cache from disk...
2023-07-13T17:08:27.822Z: Validating branches...
2023-07-13T17:08:27.822Z: trunk: develop
2023-07-13T17:08:27.834Z: validated: sm/remove-cluster-meta
2023-07-13T17:08:27.840Z: validated: sm/helm-migration
๐ŸŒฒ Pulling develop from remote...
develop is up to date.
2023-07-13T17:08:29.382Z: Clearing persisted cache...
2023-07-13T17:08:29.394Z: Failed to persist Graphite cache
ERROR: fetch failed
2023-07-13T17:08:29.412Z: TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async getPrInfoForBranches (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/lib/api/pr_info.js:20:22)
    at async syncPrInfo (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/actions/sync_pr_info.js:10:24)
    at async syncAction (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/actions/sync/sync.js:22:5)
    at async Object.run (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/commands/repo-commands/repo_sync.js:49:9)
    at async graphiteHelper (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/lib/runner.js:97:9)
    at async /opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/lib/runner.js:72:20
    at async Tracer.span (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/lib/utils/tracer.js:91:22)
    at async graphiteInternal (/opt/homebrew/lib/node_modules/@withgraphite/graphite-cli/dist/src/lib/runner.js:55:9)
fwiw Iโ€™m not a user of the graphite UI in this context, just the CLI
f
Hi there! Still having this issue?
s
yup
let me upgrade graphite again and double-check ๐Ÿ™‚
still happening
0.36.0-alpha.1
hmm, still happening ๐Ÿ˜ž
Copy code
๐ŸŒฒ Pulling develop from remote...
develop is up to date.
2023-07-19T14:37:53.362Z: Clearing persisted cache...
2023-07-19T14:37:53.369Z: Failed to persist Graphite cache
ERROR: fetch failed
2023-07-19T14:37:53.379Z: TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
although the debug output is more helpful this time - something abt bad parents? although this happens on all of my repos though, so idk if itโ€™s just a repo-specific problem
๐Ÿ‘€ 1
p
Weird, thanks for the flag! @Nicholas Yan anything you touched with the CLI recently?
s
Copy code
2023-07-19T14:37:48.232Z: bad parent name: sm/no-op-fix
	missing
2023-07-19T14:37:48.241Z: validated: sm/v2-read
2023-07-19T14:37:48.241Z: invalid parent: sm/write-v2
2023-07-19T14:37:48.247Z: validated: sm/v2-write
๐ŸŒฒ Pulling develop from remote...
develop is up to date.
2023-07-19T14:37:53.362Z: Clearing persisted cache...
2023-07-19T14:37:53.369Z: Failed to persist Graphite cache
ERROR: fetch failed
2023-07-19T14:37:53.379Z: TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
n
Hmm I havenโ€™t. I think @Jacob Gold would be the right person for the job here!