-
Notifications
You must be signed in to change notification settings - Fork 3
feat: puya debugging support; improved source map management #37
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
Conversation
@daniel-makerx @neilcampbell , pushed latest tweak that filters out source maps to pass to DAP based on priority (only keep Puya if exists -> else Teal -> else Legacy teal prefixed with .tok). Other than that it still passes files however sourcemap registry file is now curated (only contains sourcemaps relevant for the executing trace -> after debug session is done it removes the file from users filesystem ). Also fixed e2e tests in CI pipeline, latest VSCode version seems to act and run slower than previous iterations (probably due to the fact that wdio is relying on a wdio related vscode plugin which prevents us from being able to upgrade to latest stable wdio version). |
5022812
to
4a395e9
Compare
@daniel-makerx added imports of the ProgramSourceEntryFile and ProgramSourceEntry from avm debugger instead of having the algokit extension replicate the interface |
868eecf
to
f569703
Compare
ef4ccc6
to
f446869
Compare
f446869
to
fee21cf
Compare
7d0407d
to
0efe5c4
Compare
0efe5c4
to
4f10f1a
Compare
Fixes the error thrown during npm package invocation: ERROR @types/vscode ^1.92.0 greater than engines.vscode ^1.80.0. Either upgrade engines.vscode or use an older @types/vscode version
Co-authored-by: Neil Campbell <neil.campbell@makerx.com.au>
...kspace/puya_third_parties/.fake-venv/lib/python3.12/site-packages/puya_bignumber/__init__.py
Outdated
Show resolved
Hide resolved
263ccf3
to
83c6032
Compare
83c6032
to
5e5729b
Compare
Proposed Changes
Further notes