Closed oldlore closed 1 year ago
I think this is fixed in the develop branch, but not in master yet
You're right. I didn't catch this similar report under the closed issue #1070 . I updated the 2 relevant files from develop branch and the process ran successfully. Thanks for your help and I'll try to remember to check the closed issues before opening new ones to avoid clutter!
Has the fix been merged into master ?
It has not but I fixed it locally by updating: ib_client.py csv_contract_position_data.py from develop. Hopefully that didn't break anything else :)
At the moment there seems to be two critical fixes in develop and not in master - the logging fix and the backup process fix.
As a general practice, it would be better implement critical fixes in master first, and then merge the fix into develop.
I know we have recently decided to have two branches master and develop, but thinking little more, the best practice could be instead of having a develop branch, each new big feature or critical bug fix which require substantial code change is developed in a new branch (out of master) and then merged into master. Small safe fixes can directly be done in master. Perhaps food for thought for the future.
Anyhow, I hope there will be a merge from develop into master soon and things are stable.
Yes, @emretezel. That is exactly how it should work. But...
No one else but you is responsible for your system.
If all you can do in this situation is wait for Rob to do a merge, you're likely to be in for a bad time down the road.
*Neither of those bugs is truly critical. Both are highly annoying, though, and should be fixed in master as soon as possible.
I noticed today that run_backups has been crashing since 4/3. Error is posted below. I updated to the master branch this past weekend. Run_backups completed successfully on 3/31 (before upgrade). I don't know if it matters, but the instrument order is different each day, i.e. it doesn't seem to be crashing on one specific instrument.