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
We are noticing that with the version 2.30 extension where we encounter an unexplained undefined compile error:
It seems arbitrary and we are not able to isolate any code that specifically generates this.
We DO know that if we try to syntax check some code ( complexity does not seem to be a defnitive charictiristic ) we are seeing this issue consistently. However, when we try to break up the code and isolate the source - the error becomes elusive.
This is happening on multiple workstations and we have tried everything from reinstalling the full stack of VS code, extension and clienttools and the only solution that works for us is the downgrade to v2.29.0.
This is happening on Windows machine with client tools version 9.6.10-1.
I will reach out seperately with information regarding repository where this is occuring
The text was updated successfully, but these errors were encountered:
I repeated the syntax check after updating and I am now getting: Syntax check exception: Unicode replacement character detected, source encoding issues? (eclcc -syntax c:\Users\marcga01\git\PublicRecords7\Header\New_Header_Records.ecl)
We are noticing that with the version 2.30 extension where we encounter an unexplained undefined compile error:
It seems arbitrary and we are not able to isolate any code that specifically generates this.
We DO know that if we try to syntax check some code ( complexity does not seem to be a defnitive charictiristic ) we are seeing this issue consistently. However, when we try to break up the code and isolate the source - the error becomes elusive.
This is happening on multiple workstations and we have tried everything from reinstalling the full stack of VS code, extension and clienttools and the only solution that works for us is the downgrade to v2.29.0.
This is happening on Windows machine with client tools version 9.6.10-1.
I will reach out seperately with information regarding repository where this is occuring
The text was updated successfully, but these errors were encountered: