You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue with the format of the time data stored in the json file.
The problem is that sorting the messages with the stored data is not possible when more than one comment is added within one minute (In my case sorting put the entered message not in the first line, but inserted it into 2nd respective 3rd aso line. Reason is that messages have identical "timestamp" and therefore chronological sorting is impossible)
The issue could be simply ignored when sorting is not applied at all just the messages would be inserted into the lists at index [0]. This can be done because the processing is synchronous and thus blocks until the requests are finnished.
Though, generally, when doing data analysis tasks during handling of requests at the server
it might be also worth thinking about asynchronous processing.
Especially if handling requests involves heavy number crunching this would block other users to submit to the server or deny processing them until the request handling of the previous submitted task is finnished.
(Also, kind of good to be aware of when programming web servers that implement data analysis tasks)
There is an issue with the format of the time data stored in the json file.
The problem is that sorting the messages with the stored data is not possible when more than one comment is added within one minute (In my case sorting put the entered message not in the first line, but inserted it into 2nd respective 3rd aso line. Reason is that messages have identical "timestamp" and therefore chronological sorting is impossible)
The issue could be simply ignored when sorting is not applied at all just the messages would be inserted into the lists at index [0]. This can be done because the processing is synchronous and thus blocks until the requests are finnished.
Though, generally, when doing data analysis tasks during handling of requests at the server
it might be also worth thinking about asynchronous processing.
Especially if handling requests involves heavy number crunching this would block other users to submit to the server or deny processing them until the request handling of the previous submitted task is finnished.
(Also, kind of good to be aware of when programming web servers that implement data analysis tasks)
https://realpython.com/python-async-features/
The text was updated successfully, but these errors were encountered: