Post ASgl8ybAkuwVTAMTEO by alex@gleasonator.com
(DIR) More posts by alex@gleasonator.com
(DIR) Post #ASgkFgR2aLyrD3FyVs by matty@nicecrew.digital
2023-02-15T01:37:39.935723Z
1 likes, 0 repeats
@alex @graf I’m trying to reset completely to the soapbox develop branch on a local test branch but it still has my commits. Is there a way to completely reset my test branch so that it is identical to the soapbox develop branch? I’m trying to diagnose the issue with clicking shit being broken when a new element is injected in to the feed.
(DIR) Post #ASgkQTm5zrKZ85FjiC by n3f_X@nicecrew.digital
2023-02-15T01:39:38.439524Z
1 likes, 0 repeats
no matty NO
(DIR) Post #ASgkUyIeRmYSxYcf3I by matty@nicecrew.digital
2023-02-15T01:40:18.245308Z
2 likes, 0 repeats
It's just for testing! I've learned my lesson and am maintaining a separate fork altogether so I don't break things again (yet)
(DIR) Post #ASgknNLG51bPq3cM1g by tyler@1611.social
2023-02-15T01:43:49.287570Z
1 likes, 0 repeats
(DIR) Post #ASgl8ybAkuwVTAMTEO by alex@gleasonator.com
2023-02-15T01:47:35.066291Z
0 likes, 0 repeats
@matty @graf git remote add upstream https://gitlab.com/soapbox-pub/soapbox.gitgit fetch upstreamgit reset --hard upstream/develop
(DIR) Post #ASglURaUAeFZSTHDRw by The_Almighty_Kek@nicecrew.digital
2023-02-15T01:51:23.062634Z
2 likes, 0 repeats
(DIR) Post #ASglaFc1bhO43UlWpU by matty@nicecrew.digital
2023-02-15T01:52:33.104870Z
0 likes, 0 repeats
Weird - it still happens even with a completely clean Soapbox clone. I wonder if it's because I'm in a VM or something. I'm a bit nervous about pushing it to production but I'm glad to know it's not something I've done.
(DIR) Post #ASglecsN3UUBMfUuQq by alex@gleasonator.com
2023-02-15T01:53:19.923773Z
0 likes, 0 repeats
@matty @graf Try git status and see if you’re in the middle of a rebase or something.
(DIR) Post #ASglmZ0BLJ4VfMw5ui by matty@nicecrew.digital
2023-02-15T01:54:50.094741Z
0 likes, 0 repeats
I don’t see anything out of the ordinary. This is on the completely clean clone of Soapbox.matty@virbun2:~/projects/soapbox-test$ git statusOn branch developChanges not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: package.json modified: yarn.lockno changes added to commit (use "git add" and/or "git commit -a")
(DIR) Post #ASgnSN2AKUoifHMYXw by smith@orwell.fun
2023-02-15T02:12:33.785887Z
0 likes, 0 repeats
if it's inside docker, maybe the volume got cached somehow
(DIR) Post #ASgnSNYQOYcaHKSJpQ by matty@nicecrew.digital
2023-02-15T02:13:31.333345Z
1 likes, 0 repeats
Nah I can't into docker. The `gleasonator` branch doesn't have this problem but I don't think he's on the latest commit. I should probably upload a video of the issue or something but I can't get OBS to work. It won't capture any graphics for some reason right now.
(DIR) Post #ASgrT0wAMzw4Et7RTM by matty@nicecrew.digital
2023-02-15T02:58:31.432699Z
0 likes, 0 repeats
This is what I was testing. I was able to replicate it with a clean clone of the develop branch, so I don't think it's a problem with my fork.https://gitlab.com/soapbox-pub/soapbox/-/issues/1371