b33->b34 causes Error Reading Workspace File too.
If it's not a bug and it's a reality when workspaces can be incompatible between builds (if something new is added or changed), I think we need something to prevent this, or to control this etc. As creating a workspace every time can be very time consuming (for Strategy Monitor if you have many strategies for example) and can cause data loss.
If it's not a bug and it's a reality when workspaces can be incompatible between builds (if something new is added or changed), I think we need something to prevent this, or to control this etc. As creating a workspace every time can be very time consuming (for Strategy Monitor if you have many strategies for example) and can cause data loss.
Rename
In general this shouldn't be an issue as workspaces support versioning. I can open workspaces saved in previous versions without a hitch. Some object may have disappeared (e.g. when you rebuilt the compiled strategy) but it's just an educated guess.
QUOTE:
Examples of a helpful bug report:
https://www.wealth-lab.com/Discussion/Build-26-Save-Workspace-exception-6904
https://www.wealth-lab.com/Discussion/Build-28-Strategies-don-t-load-in-workspace-6997
Once again: by the time I post a report I don't know whether it is just me who can see it or not. Example: yesterday Binance bugs are seen for everyone at any time. I'm not going to describe thousands of details for something that need zero details)).
But I think your instructions will be a good help for you or QA when reporting a bug).
OK we can close this topic as false positive then.😄
No problem)), I can stop reporting at all.
No need to stop reporting! I haven’t had any issues opening old Workspaces in B34 and there weren’t any changes around Workspace. So, is it just one problem WS or all of them? If you can see any common denominator let us know.
QUOTE:
No need to stop reporting! I haven’t had any issues opening old Workspaces in B34 and there weren’t any changes around Workspace. So, is it just one problem WS or all of them? If you can see any common denominator let us know.
Yep, this sounds much more constructive).
After a brief research. Of all my worspaces there is only one that genereates this error. A one with Strategy Monitor. With one strategy, settings attached. There is another WS (that works OK) on another server, the only differences I can see are:
- different server;
- Finam HDP provider connected to the dataset (instead of WealthData Dow30);
- Quik broker (instead of dummy).
Your Response
Post
Edit Post
Login is required