Graphite Community

When doing `gt ll` and then exiting the pager (`vim`) with `q`, I get
&gt; ```ERROR: Command failed with error exit code 141:
&gt; git log --graph --abbrev-commit --decorate --format=format:%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(white)%s%C(reset) %C(dim white)- %an%C(reset)%C(auto)%d%C(reset) --branches```
displayed.
If I first go to the end with `Shift+g` and then quit, the error is not displayed.

Typo on <https://graphite.dev/docs/updating-your-pull-requests>
`sequence of evens` -&gt; `sequence of events`

Bad shortcut on <https://graphite.dev/docs/reviewing-pull-reqeusts>
You might not agree that this is a bug, but imho it is.
Not everyone uses macOS.
Fewest developers I know actually do.
So mentioning only `CMD+J` is a bit unlucky.
On a normal keyboard you don't even have a `CMD` key or know what it is.

Formatting on <https://graphite.dev/docs/reviewing-pull-reqeusts>
"Click the # icon in the comment box" -&gt; "Click the `#` icon in the comment box"

<@U04K5N14V9B> Just in case you missed it and did not leave it in intentionally, the `gt stack fix` is still there.

<@U05447TKZKP> thank you for all of these bug reports! We really appreciate it. Continue to report any more that you see.

I'm through the docs, so for now, no more doc-bug reports :slightly_smiling_face:

Went ahead and made all your changes, <@U05447TKZKP>. Thanks for the feedback, and keep it coming!

Annoyingly, I uninstalled the package so I could upgrade other packages on my system, and now I can’t install an older version:
```brew install graphite@0.20.15
Warning: No available formula with the name "graphite@0.20.15". Did you mean graphite2?```

```% brew install withgraphite/tap/graphite@0.20.15
Warning: No available formula or cask with the name "withgraphite/tap/graphite@0.20.15". Did you mean withgraphite/tap/graphite?```

the npm install doesn’t work either:
```% npm install -g @withgraphite/graphite-cli
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*```

This may be because I use yarn generally, but I also can’t install with yarn:
```% yarn global add @withgraphite/graphite-cli
Usage Error: The 'yarn global' commands have been removed in 2.x - consider using 'yarn dlx' or a third-party plugin instead```

Of course I’m not going to add graphite to my package.json, so that method is out

Actually I tried that just to see, and it also doesn’t work:
```% yarn add @withgraphite/graphite-cli
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @withgraphite/gti-cli-shared-types@workspace:*: Workspace not found (@withgraphite/gti-cli-shared-types@workspace:*)```

I don’t see any hints or troubleshooting tips on <https://graphite.dev/docs/installing-the-cli>. Am I really the only one to hit all these issues?

Okay, I found <https://graphite-community.slack.com/archives/C02DRNRA9RA/p1682124810140379>. As suggested, `npm install -g @withgraphite/graphite-cli@0.20.15` works. I’d never have thought of that. So looks like the latest release is completely broken on homebrew and npm

Hey Brendan! Are you still having issues here?

I’m using the npm workaround, though I’d like to be able to upgrade :slightly_smiling_face:

Trying `npm upgrade -g` throws the same error still

I have the exact same issue upgrading via homebrew

Hi Sean! Are you still seeing this? which version is homebrew trying to install

We put out a fix earlier that should address

just tried again and `0.20.17` installed successfully, thanks

you’re running a compiled binary now :) 

Something was cached, so homebrew wouldn’t try to install .17, only .16. I had to untap and install fresh: `brew untap withgraphite/tap &amp;&amp; brew install withgraphite/tap/graphite`

I’m upgraded now though — thanks for the fix!

image.png

a fix for this issue is rolling out today!

Yep! Can confirm this is still happening. Getting an `unexpected server response 500` while submitting a stack. Any leads/updates Nicholas on how soon it could be fixed?

`gt bc -p` is not working with 0.20.15.
There are unstaged changes, but the command ends with
&gt; No staged changes; created a branch with no commit.
If there are already staged changes, it works, actually.

Graphite - Instability and failing merges due to GitHub API timeouts ​*[Resolved]*​ This incident has been resolved.
 ​*Affected:*​
Dashboard
 View incident button

0.20.17 also misses it here, 0.20.16 cannot be installed, 0.20.15 still has it, so if you downgrade to that you have it again

<@U02RREE9GKH>, any additional information on this. Was this removed on purpose?

No, not sure what happened here! We'll look into it

My guess would be, you wanted to copy `apps/cli/src/commands/branch-commands/edit.ts` to `apps/cli/src/commands/branch-commands/unbranch.ts` to create a new command but accidentally moved instead of copied in `097b5046c4e00b08cf168516e6067ce1367bfddc`. :slightly_smiling_face:

Following my guess I created a PR that reintroduces it at <https://github.com/withgraphite/graphite-cli/pull/1404> :slightly_smiling_face:

Oh my gosh. I was just noticing that `branch edit` was gone and was soooo close to just chucking the computer out the window

Just noticed this missing, pls we can get a release today reintroducing `branch edit`? Also, when looking for it I tried `gt changelog` and got this:

```ERROR: File '/**/graphite-cli/apps/cli/dist/.CHANGELOG.md' was not included into executable at compilation stage. Please recompile adding it as asset or script.```

:point_up_2::skin-tone-2: I second that :point_up_2::skin-tone-2: would love to upgrade from 0.20.15

If you are in a hurry, just pull my PR branch and do `yarn install &amp;&amp; yarn workspace @withgraphite/graphite-cli run dev` :slightly_smiling_face:

CleanShot 2023-04-28 at 13.59.41@2x.jpg

Thank you, I appreciate it. I'm not in a rush, but I'm a bit concerned about not having this bugfix. Probably unjustified.

ah - this bug only deletes empty branches

sorry for the scare! we will get a release out soon though 

Thank you for clarifying. That's good news! :pray::skin-tone-2:

Could you share the following (via DM) so I can look at logs?
1. Github username
2. PR number
3. PR org
4. PR repo

so this happened because one PR mid-stack was in a draft state. once i published it, things look good again

Hi! Yeah as an Arc user I've been experiencing this too - let me ask the team what would be helpful!

I just disabled the Refined GitHub extension and that _seems_ like it might have addressed the loading issue?

Another report that seems to be Arc related :disappointed:
<https://graphite-community.slack.com/archives/C02DRNRA9RA/p1682458129150139>

Getting a similar error :slightly_smiling_face:
```📨 Pushing to remote and creating/updating PRs...
ERROR: Unexpected server response (500).

Response: {
  "_response": {
    "size": 0,
    "timeout": 0
  }
}```

We're looking into it right now!! thanks for reporting :saluting_face:

We're experiencing occasional 500s when submitting PRs through the CLI and are looking into it - thanks for bearing with us! :saluting_face:
<https://status.graphite.dev/>

Hey! Thanks for reaching out — as a first step, I would recommend having them check their Github access settings at <https://app.graphite.dev/settings/github-access> — there are 3 different ways to authenticate, and it sounds like in this case they should be on GitHub app (as opposed to OAuth or Personal Access Token) — they might be on OAuth as that's what the app defaults to in certain cases.

Thanks <@U02RREE9GKH>, I’ll ask. In general, while signing up, what steps do we need to take to default to GitHub app?

Screenshot 2023-04-25 at 12.30.27.png

During sign-up, the user will see a screen that looks exactly like the settings page I linked — it will say either "Github app" or "Github OAuth" at the top — if they see the Github OAuth version, they should click the "GitHub app" link at the bottom of the page to switch.

Screenshot 2023-04-25 at 12.33.46.png

I think we managed to work but I believe there’s a snag.

Context:
• GitHub app has been configured to grant access to one particular repo
• The people who are onboarding do not have permissions to update/authorise the GitHub app
The issue:
• When they are going through the signup flow, Graphite asks them to “Configure” the GitHub app
• They get redirected to GitHub and GitHub shows that app is already installed on the repo and there is only one CTA: “Configure”
• Click on Configure errors out because they don’t permissions to update that app — at this point the signup flow is broken
• BUT if they go back to Graphite, and refresh the app
It’ll be tricky to onboard engineers with this snag — it is a little difficult to explain but I tried my best :slightly_smiling_face:

Got it - we can definitely do better here for orgs that have already been enabled with app! thanks for the detailed feedback

Hey <@U02RREE9GKH>, some people are still facing issues with the flow so I’d like to record the signup process (with this workaround) and share it with them. For that, I’ll need to delete my account. How can I do that?

Hey <@U02RREE9GKH> (or someone else from the Graphite team), can someone help me delete my account so that I can record the signup process for the wider team?

Hi all! We’ve just about resolved this incident, CLI pr submissions should stop listing a 500:
<https://graphite-community.slack.com/archives/C02DRNRA9RA/p1682436647243049>

Are you redirecting from the files changed tab?

It's a known issue that redirects are broken from the files changed tab, but work from the conversations tab

Is this using the chrome extension? How did you redirect

Sorry,  lost track of the conversation. It's happening when I am in conversations tab.

Are you on Arc or another browser? I use Arc exclusively and it is sometimes not a great experience in Graphite. 

Yep, I use Arc exclusively too :eyes: Huh, how is it a problem only on Arc?

CleanShot 2023-04-26 at 17.01.31@2x.png

Yeaaah, not sure. I am going to open a ticket internally to try and figure out more.

<@U055M3X2KS4> when you have this issue if you could record a trace in Arc using Help -&gt; Troubleshooting -&gt; Record a trace and mention "Graphite" in there that would be really helpful!

Same for you <@U02L3BRF5BK>!

Feel free to include `ask @amonshiz` also in the trace description message so that others know to ping me for context :slightly_smiling_face:

Thanks for helping us figure this out <@U02PSKGK4TS>!

<@U02PSKGK4TS> Uploading a trace right now (1 minute long). What's the length of the trace we should be submitting and should we be doing anything while the trace is recording? Not much to be done actually since the website is only loading :thinking_face:

1 minute is great! It should hopefully give us something to start with.

Added a trace as well! Thank you for looking into it

Screenshot 2023-04-26 at 11.40.52 AM.png

Oof thanks for the report! Looking into it

Hey <@U03H87EVAM6>! Sorry about that, are you still running into this?

Do you have any old tabs open with graphite? If so, can you try closing or refreshing those? I believe there might be an issue with tabs that are old enough can block new tabs from loading properly.

Sorry! Just got it resolved... Or rather it resolved itself. Logged into an incognito tab, that one worked, and when I went back to the original one on my browser, it was loading up fine :sweat_smile:
Not sure what it might have been but it looks temporary?

Thanks for reporting! This is a complex case and one we hope to make better with time.  Sorry that it resulted in unexpected behavior

Hey <@U02NH5WKTKL>! Are you still having this issue?

Oops! Solved. Sorry. A good lesson though, to always search. It wasn't the fault of graphite. It's just the git being weird. For those wondering, I switched from https to ssh &amp; set ssh repo uri as the remote url. My account is already setup with ssh. So, it was a ez fix. : )

Hey Ian, sorry about that! Will look into this

Thanks for looking into it. Notifications are still broken for me.

We've isolated the issue! Working on fixing it

Graphite - We are seeing issues with stacked merges failing. ​*[Investigating]*​ We are currently investigating this incident.
 ​*Affected:*​
Dashboard
 View incident button