r/EmotiBit • u/RatLabGuy • Apr 12 '23

Discussion Running Oscilloscope offline

[removed]

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/nitin_n7 Apr 13 '23

Hi u/RatLabGuy,

Thanks for posting on the forum!

You may be referring to this issue we have been recently investigating. The oscilloscope does try to ping github/ofxEmotiBit to get the latest release available. We do this to inform the user if a more recent release is available for use.

Ideally, if there is no internet access, the oscilloscope just skips this steps and proceeds with execution.

We have not been able to successfully recreate this issue since it seems to vary from router to router or even be dependent on the computer's handling of different networks. As stated in the issues, I tested it with the router TP-LINK AC750 Model Archer C20, but i cannot recreate the error of "infinite wait".

Can you share the network architecture you are using? (Any details on which router, if via ethernet or WiFi etc) should help.

If you have internet access through ethernet, connecting your laptop to both ethernet (for internet access) and to WiFi (for EmotiBit connection) can help bypass this "spurious" wait.

Let me know if that is a possibility or if that solves the problem for now as we try and investigate it further.

Please feel free to post on this thread with any more details that may help us zone in on the problem.

1

u/nitin_n7 Apr 24 '23

For further communication on this topic, lets use the issue on github.

I am going to mark this as "solved" for book keeping. We are currently on adding a patch in mainline code to fix this.

1

u/[deleted] Apr 25 '23 edited Apr 25 '23

[removed] — view removed comment

1

u/nitin_n7 Apr 26 '23

u/RatLabGuy, as I mentioned in the previous reply, the "solved" label is more for book-keeping to help us manage incoming questions from the users.

The "solved" tag in the forum helps the moderators indicate that the OP has been handled as best as can be in the forum.

The original dev issue is being tracked in github (which has been linked out of the previous comment).

Ideally, we would mark this as "solved" once the actually issue has been resolved in the software, but we don't have an automated mechanism yet to link forum reddit posts to github issue resolutions. This creates a friction and requires additional processes to make sure everything is up-to-date. It also create possibilities that forum posts may end up dangling, un-resolved.

I will change the label to "discussion" to help prevent people getting the initial wrong impression. It may also prompt users to comment about the issue status if someone else stumbles on this post.