Allison Rapoport
04/15/2024, 6:16 PMInstatus
04/15/2024, 8:08 PMHoàng Xuân An (Inta)
04/16/2024, 8:17 AMgt ss
doesn't like my project on Windows. If I do gt ss
via WSL2, it works fine, though git commands on WSL2 don't like my on-Windows project. Here's the gt ss
logthiago damasceno
04/16/2024, 1:37 PM📨 Pushing to remote and creating/updating PRs...
ERROR: Unexpected server response (400).
Headers:
x-graphite-request-id: 981f9cb0-c72e-47b1-b17c-ab94d3f89cb8
Response: {}
Sean Wilson
04/17/2024, 5:51 AM龙逸楠
04/17/2024, 6:19 AMAnders Ha
04/17/2024, 9:40 AMInstatus
04/17/2024, 10:12 AMInstatus
04/17/2024, 10:50 AMBen Jaffe
04/17/2024, 2:04 PMLuka Salević
04/17/2024, 2:13 PMuseSettingsOrg
being the culprit)Walker Hildebrand
04/17/2024, 10:49 PMForest Anderson
04/18/2024, 2:42 AMsdks/** linguist-generated=true
to our .gitattributes
, and it works great for most files (image 1), but for some it doesn't (image 2). Sidenote, it seems that the Files view doesn't respect this file and auto-collapse the regions (image 3).tremy
04/18/2024, 11:07 AMElla Rohm-Ensing
04/18/2024, 3:38 PM> gt submit -d
:pancakes: Validating that this Graphite stack is ready to submit...
The following upstack branches have open PRs:
▸ ella/rm-filebasedfinalstatecursor (#37021)
▸ ella/rmfinalstatecursor (#37022)
▸ ella/remove-sync-mode-use (#36999)
✔ Would you like to submit these branches as well? … yes
In the future you can use gt submit --stack --update-only to update all open PRs in your current stack.
ERROR: You are trying to submit at least one branch that has not been restacked on its parent.
To resolve this, check out ella/rm-filebasedfinalstatecursor and run gt restack.
Ryan Gray
04/18/2024, 8:52 PMgt init --reset
, but the issue persists after that.
This is preventing me from starting/submitting new branches in the interactive view. I can still do it through the cli, though.Vampire
04/18/2024, 10:03 PMPing
04/19/2024, 1:02 AMBradley Turek
04/19/2024, 8:12 PMVampire
04/19/2024, 11:26 PM$ gt --version
1.3.2
$ gt sync --debug
[...]
🌲 Pulling master from remote...
Spawning fetchRemoteTrackingBranch: git fetch upstream master
Finished getRemoteUrl: git remote get-url upstream --push
{
"code": 0,
"signal": null,
"stdout": "git@github.com:spockframework/spock.git\n",
"stderr": ""
}
Finished getRemoteUrl: git remote get-url upstream --push
{
"code": 0,
"signal": null,
"stdout": "git@github.com:spockframework/spock.git\n",
"stderr": ""
}
Requesting: {
"route": {
"method": "POST",
"url": "/graphite/pull-requests",
"params": {},
"response": {}
},
"params": {
"repoOwner": "spockframework",
"repoName": "spock",
"prNumbers": [
1630,
1298,
1610,
1696,
1629,
1927
],
"prHeadRefNames": [],
"trunkBranchNames": [
"master"
]
}
}
UNCAUGHT EXCEPTION: fetch failed
UNCAUGHT EXCEPTION: TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11457:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.request (C:\Users\bkautler\AppData\Roaming\npm\node_modules\@withgraphite\graphite-cli\graphite.js:3:1303363)
at async i (C:\Users\bkautler\AppData\Roaming\npm\node_modules\@withgraphite\graphite-cli\graphite.js:3:1302781)
at async a (C:\Users\bkautler\AppData\Roaming\npm\node_modules\@withgraphite\graphite-cli\graphite.js:3:1131032)
Flushing trace...
Sent trace to child...
😿
Same happening with stable version, thus moved here from https://graphite-community.slack.com/archives/C0604H4AM97/p1713562862702039Vampire
04/20/2024, 6:41 PMSasha Bratyshkin
04/23/2024, 8:44 AMAlex Wayne
04/23/2024, 4:56 PMTyler Nieman
04/23/2024, 8:33 PMgt get branch-name
no longer checks out the specified branch.
Was this an intentional change?Peter Griess
04/23/2024, 8:52 PMelliott
04/23/2024, 11:17 PMJoshua Punshon
04/24/2024, 2:22 AMgt submit --stack ...
if branches have been deleted. If I try to do the automatic option, it deletes the branches but then fails to restack and the command fails. So i have to either cancel and then run gt sync
or run gt sync
and often gt restack
to try fix the weird state it gets to and then resubmitJoongi Kim
04/24/2024, 3:59 AMForest Anderson
04/24/2024, 6:49 PMgt absorb
commands, I keep getting this error. How can I get around this?Farah Uraizee
04/25/2024, 12:27 AMmain
/ whatever the ancestor's actually living now
2. Ideally, do the correct behavior and do what the user expects. I know of exactly 0 times where I expect clicking the "merge" button on the UI to not merge into the main branch and rather into the old version of the parent PR.
Apologies for the frustrated tone. We've lost a lot of time this week working backwards on what's going on and not having the right combination of CLI commands each time feels like a bad UX. I expect that some of the updates around submit or merge this past week in the changelog may have caused the regression. Unsure, but our team would really appreciate a fix on this asap, or at least a better UX guiding folks to the right experience.