git ssb

Clicking "view sorce"-gears switches to an open git repo tab

When having a git repo open in one tab and I click a "show source" gear in another tab, patchbay switches to the git repo.

can you give me a link to a message which behaves like this plz @keks ?

%t1en5fS... ;)

I think its any message for me...

for me right now, clicking "view source"-gears switches me to the /network tab that i have open.

for me right now, clicking "view source"-gears switches me to the /network tab that i have open.

That is not happening here o.O

I'm on 6.7.4 / 5840ace3e723ac68ca995db5a3598cb2ac264c83

I'm having a hard time replicating this D:

:( Do you have the same listeners?

not at all ! This is what I see in electron .. in 6.9.2

have you run npm upgrade ?

oh I mean this are the listeners for the gear <a>.

I'm currently on patchbay 6.7.4. I have the git repo cloned and do a git pull && npm i every now and then. I'll try upgrading now, hang on

Just updated, I'm on master. The problem remains. I just removed all the event listeners on the gear and it keeps happening (the source doesn't show anymore though, so it worked). I made screenshots of the listeners before and after opening a git repo, and there are differences!

before:

after:

still no success replicating this.

to be clear, the steps I follow are:

1. open the /git-ssb tab, select %catstack (a git repo page)
2. got to /public tab, click on a gear on any message

And I expect to be taken back to %catstack ?

I am still not seeing the same event listeners as you, though with logging can confirm the listeners are being attached, and the gear click is triggering the keyscroll.js onActivateChildbut does not run selectChild

@mikey do you have any recommendations for debugging this? @keks to try something desperate can you scrap your node_modules and npm i afresh?

:/

to be clear, the steps I follow are:

1. open the /git-ssb tab, select %catstack (a git repo page)
2. got to /public tab, click on a gear on any message

And I expect to be taken back to %catstack ?

Exactly.

@keks to try something desperate can you scrap your node_modules and npm i afresh?

I'll do that, but not now...