@coinsgaga first of all, kindly thank you for your report. Each and every such report helps us improve rigidness of the system.
The issue turned out to have higher impact than previously anticipated. We’ve investigated this down to improper handling of Decentralized Chat Messages within GRIDNET OS.
Oh yes, GRIDNET OS does include a decentralized anonymous messaging sub-system and some of you seem to be playing around with it on daily basis.
In any case, the issue you’ve reported is being investigated on YouTube LIVE.
If we take a close look at the code snipper below:
We may see that in some cases the messages were taken from the messages’ stack but these were not actually removed from the processing loop which in turn freezed the main processing loop of one of the major system components (the Network Manager) which had significant implications.
A hot fix ha been already introduced at a single public test-net (orion.gridnet.org) which is currently rebooting and pending validation.
No, in regards to your question whether you can continue with the rest of the tutorials.
The short answer is yes, we haven’t noticed this issue to affect the processing of code throughout the network.
Yet still, we advise to wait for an hour or two once thing settle as we will be investigating this further and dispatching an update throughout the network soon.
If you tried to commit any code, most likely the processable code bundle would be compiled by the full-node you’ve been accessing and broadcasted away to the current leader (a GPU enabled node) for processing. So the process is expected to succeed.
Do notice that the log-me-in functionality is used mostly for personalization of your command line/ UI environment. (once you log-in, the system autonomously takes you to your home directory be it through SSH or UI, the Wallet UI dApp automatically refreshes the status of your account’s balance, the ‘start-menu’ displays your login-name as present within your Identity token if registered with your State Domain, the Decentralized Messaging sub-system automatically assumes your friendly identifier for the messages you write etc.)
but with that said it is not needed to log-in to affect the system or to read data. Authentication with the mobile app would be always required whenever you are ready to commit.
The implications of log-me-in go way further, for instance if you log-in the commands you execute within the terminal would simulate your identity not the identity of the owner of the current directory - yet another convenience. But yet again - it is a convenience functionality, it allows to better ‘simulate’ the actual processing results once user decides to ‘commit’ yet again - whether user logs on or not would not affect the final processing results as that involves validation of a secure ECC signature.
It can be further explained that the log-me-in mechanism causes a dynamic Security Access Token to be generated and associated with the user’s session. The token is validated and taken account for during processing of any further instructions. All the active user-mode UI dApps are notified about it as well, they can then react accordingly.
