Cycle 4, stage 4, day 17:
if there is something that can happen, it will happen.
Few days ago, I have addressed a very exceptional asset balance management issue. By its exceptional nature, having the opportunity to try out the fix was not immediate. It did turn out that there was a regression bug in the fix and it manifested itself yesterday morning.
It took me the whole day yesterday to find it. I was doing insomnia due to my obsession to understand the issue... That has been a hard nut to crack. I had few hypothesis to explain my observation but the logs were not supporting them.
It is funny how when you focus on a certain part of a system, you keep discovering imperfections... I have cleaned and polished few minor things but not the one that I hunting down... I was about to make insomnia despite being tired last night. I could not sleep, so I went back to my computer to keep looking for the cause of my issue and I have finally found it... It was one of the hypothesis that I have imagined... I had modified the code to address the theoretical issue but I was not sure that it was the one... I have finally stumbled into a log trace confirming that my suspicion was correct.
I was too tired to fix it right away but it has been an immense relief to know that the mystery was resolved. I have completed the fix few minutes ago... I am not 100% satisfied of the result as it is kinda complex and not as elegant as I like but this is the best that I can think of to manage a complex race condition... I have left plenty of documentation in case that this issue would reappear down the road...
So, I am ready to close the current issues and glitches chapter and hurry up the implementation of my latest idea that might be the game changer feature that I am working to find...
Update:
A new problem did appear... Hopefully, it is going to be easy to fix. I think it will...
if there is something that can happen, it will happen.
Few days ago, I have addressed a very exceptional asset balance management issue. By its exceptional nature, having the opportunity to try out the fix was not immediate. It did turn out that there was a regression bug in the fix and it manifested itself yesterday morning.
It took me the whole day yesterday to find it. I was doing insomnia due to my obsession to understand the issue... That has been a hard nut to crack. I had few hypothesis to explain my observation but the logs were not supporting them.
It is funny how when you focus on a certain part of a system, you keep discovering imperfections... I have cleaned and polished few minor things but not the one that I hunting down... I was about to make insomnia despite being tired last night. I could not sleep, so I went back to my computer to keep looking for the cause of my issue and I have finally found it... It was one of the hypothesis that I have imagined... I had modified the code to address the theoretical issue but I was not sure that it was the one... I have finally stumbled into a log trace confirming that my suspicion was correct.
I was too tired to fix it right away but it has been an immense relief to know that the mystery was resolved. I have completed the fix few minutes ago... I am not 100% satisfied of the result as it is kinda complex and not as elegant as I like but this is the best that I can think of to manage a complex race condition... I have left plenty of documentation in case that this issue would reappear down the road...
So, I am ready to close the current issues and glitches chapter and hurry up the implementation of my latest idea that might be the game changer feature that I am working to find...
Update:
A new problem did appear... Hopefully, it is going to be easy to fix. I think it will...
