Graphite - Dashboard failing to load and CLI submits being rejected ​*[Identified]*​ We are continuing to work on a fix for this incident. ​*Affected:*​ CLI, Dashboard View incident

Graphite - Dashboard failing to load and CLI submits being rejected ​*[Monitoring]*​ We implemented a fix and are currently monitoring the result. ​*Affected:*​ CLI, Dashboard View incident

We had a bad DB index migration - we’ve since rolled back the DB operation. One server pod is online, and the remainder are rebooting now. Apologies for the downtime folks!

Graphite - Dashboard failing to load and CLI submits being rejected ​*[Resolved]*​ This incident has been resolved. ​*Affected:*​ CLI, Dashboard View incident

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

On Windows (without WSL, in Git Bash), the generated completion script is broken. I'm not talking about

index.js

being used as mentioned in another thread here. But it also has

type_list=$(./C:\Users\redacted\AppData\Roaming\npm\node_modules\@withgraphite\graphite-cli\dist\src\index.js --get-yargs-completions "${args[@]}")

which cannot work properly. With

type_list=$(/C/Users/redacted/AppData/Roaming/npm/node_modules/@withgraphite/graphite-cli/dist/src/index.js --get-yargs-completions "${args[@]}")

it works. As well as with

type_list=$('C:\Users\bkautler\AppData\Roaming\npm\node_modules\@withgraphite\graphite-cli\dist\src\index.js' --get-yargs-completions "${args[@]}")

. As well as with simply

type_list=$(gt --get-yargs-completions "${args[@]}")

.

This message was deleted.

This message was deleted.

Typo on https://graphite.dev/docs/viewing-a-stack

commmit

->

commit

This message was deleted.

Typo on https://graphite.dev/docs/creating-and-submitting-pull-requests

make's

->

makes

This message was deleted.

Creating a lightweight git tag with the same name as the branch causes the Graphite to lose track of the branch and can't re-track it via

gt branch track

.

This message was deleted.

This message was deleted.

https://graphite.dev/docs/syncing-with-a-remote-repository leaves off with "part 3" being current and says next page continues. Next page, i.e. https://graphite.dev/docs/restacking-branches, also says it picks up from where last page left off. But it assumes we are at "part 2", doing

gt upstack restack

to restack parts 2 and 3.

Either doc or even code typo on https://graphite.dev/docs/updating-mid-stack-branches

continye

->

continue

Typo on https://graphite.dev/docs/merging-a-stack

Merging a stack via the Graphite dashboard

To merge a stack using the Graphite CLI, we recommend using the "Merge..." button in the Graphite dashboard,

->

Merging a stack via the Graphite dashboard

To merge a stack using the Graphite dashboard, we recommend using the "Merge..." button in the Graphite dashboard,

and for consistency

repo sync --restack

->

gt repo sync --restack

submit

->

gt stack submit

This message was deleted.

Typo on https://graphite.dev/docs/collaborating-on-a-stack

and use then use

->

and then use

and for consistency

downstack get

->

gt downstack get

repo sync

->

gt repo sync

https://graphite.dev/docs/command-shortcuts says

```## syncing & resolving conflicts

gt rs # gt repo sync```

But the

& resolving conflicts

is wrong as long as you do not add

--restack

, isn't it?

This message was deleted.

On https://graphite.dev/docs/faq for consistency

downstack get

->

gt downstack get

stack submit

->

gt stack submit

Typo on https://graphite.dev/docs/getting-started-with-the-dashboard

in. .

->

in.