-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialization issue on big job definition #92
Comments
Can confirm that |
I still believe the runner should filter out these unnecessary values from the job report. |
Actually, this is a problem with UI5 objects detection that does not work in OPA with iFrames (because the base class are not the same between the OPA window and the application window). Used a safer method based on UI5 object known members ( |
Closing the incident as the initial problem is solved. Being able to generate a bigger JSON could be interesting but would cause other problems (such as the report generator that must be able to load the serialized the JSON). |
Qualification : the job's JSON is too big to be serialized with
JSON.stringify
Alternatives :
json-stream-stringify
seems to be capable of saving very big JSONs in a stream. That would solve the issue on save but to be able to generate the reports, it would need to be able to read it again…Opa5.assert.ok(ui5Control)
) and the runner keeps track of everything…The text was updated successfully, but these errors were encountered: