azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
<d1b2> <johnsel> YouUser had a space in it in this case, so the instructions should include instructions to escape the path as needed
<d1b2> <johnsel> It’s actually windows generally that doesn’t like spaces in folder paths
<azonenberg> @johnsel so are updates to the docs required to handle this?
<d1b2> <johnsel> I’m going off the information @tetrikitty gave us, but do have questions about where that space character got inserted specifically. I know you can have your home folder defined in several ways which could be the source of this problem
<d1b2> <johnsel> It is definitely something worth testing/replicating
<azonenberg> Yeah. I mean, at this point ngscopeclient is done-enough that i dont think a ton of new feature dev is needed before a v0.1 release
<azonenberg> it's finding all of these rough edges and fixing them as best we can
<azonenberg> i expect more work to be in packaging, processes, and documentation than code, by far
<azonenberg> (although there are definitely still some bugs i want to track down)
<d1b2> <johnsel> But if it is a non-std mingw64 (which I think is a possibility) then we will have to see
<d1b2> <johnsel> Yeah we can do an official feature freeze and only work on what you stated
<azonenberg> I'm not looking for a freeze necessarily for a while because i am not too worried about new features introducing regressions
<azonenberg> it's more finding and squishing the existing bugs
<azonenberg> we can worry about potential regressions just before cutting the release
<d1b2> <johnsel> I understand what you mean but I’d still apply it in the context of ci then. I have some ideas there but will table them then to get the basic ci running
<d1b2> <johnsel> And work on markdown conversation if still necessary/desirable
<azonenberg> I think figuring out how to polish the docs in general would be good to have
<azonenberg> functional CI is higher priority
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
Darius has quit [Server closed connection]
Darius has joined #scopehal
tnt has quit [Server closed connection]
tnt has joined #scopehal
Abhishek_ has quit [Server closed connection]
Abhishek_ has joined #scopehal
<azonenberg> also i'm seeing a weird issue with channel drag and drop that i need to troubleshoot
<azonenberg> never seen it before but its happening all the time with one session
sgstair has quit [Server closed connection]
sgstair has joined #scopehal
Fridtjof has quit [Server closed connection]
Fridtjof has joined #scopehal
juri__ has joined #scopehal
juri_ has quit [Ping timeout: 246 seconds]
juri__ has quit [Ping timeout: 268 seconds]
juri_ has joined #scopehal
octorian has quit [Server closed connection]
octorian has joined #scopehal
<_whitenotifier-f> [scopehal-apps] qduff starred scopehal-apps - https://github.com/qduff
<azonenberg> Hmmmmmm very very interesting
<azonenberg> when i turn on averaging in the lecroy channel config
<azonenberg> it seems to do something funky with the timestamps
<azonenberg> and i lose sub-second granularity
<azonenberg> unsure if parsing bug or something funky in the headers or what
<_whitenotifier-f> [scopehal] azonenberg opened issue #813: LeCroy: waveform timestamps lose sub-second granularity when averaging is enabled - https://github.com/ngscopeclient/scopehal/issues/813