Closed edclark59 closed 2 weeks ago
@edclark59 Did this just start happening recently, or have you always observed this behavior?
I just experienced it in the last month or so, but before that I was still mostly using studio
On Jul 1, 2024, at 12:58, Brett Saviano @.***> wrote:
@edclark59 https://github.com/edclark59 Did this just start happening recently, or have you always observed this behavior?
— Reply to this email directly, view it on GitHub https://github.com/intersystems-community/vscode-objectscript/issues/1391#issuecomment-2200629899, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANU6W5CS4JXVQDE3Q4NACQDZKGDCNAVCNFSM6AAAAABKF54FBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGYZDSOBZHE. You are receiving this because you were mentioned.
Thanks. I was able to reproduce this and need to investigate further.
This is caused by a server-side Dynamic Objects bug. I will update this issue when there's a resolution.
Closing because this is an IRIS bug that is being tracked internally.
For example, setting an array with
s p={"value1":{"value2":{"value3":{"x":1}}}}
, in the variables window you can expand p to shown value1, but expanding value1 hangs.If you expand p one level to show value1, then type p in the debug console, you get an error: `p %Library.DynamicObject