Skip to content
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

Missing Refresh entry points action - SEP doesn't get triggered after program is recompiled #2426

Open
sebjulliand opened this issue Dec 18, 2024 · 5 comments
Labels
bug A confirmed issue when something isn't working as intended debug Debug client issue (IBM)

Comments

@sebjulliand
Copy link
Collaborator

sebjulliand commented Dec 18, 2024

Debug extension: 2.0.2
Debug service: 2.0.1

Setting an SEP on a program works fine until the program gets recompiled. After that, it's not possible to get the SEP to be triggered again. Removing and adding the SEP doesn't work either. Only restarting the Debug Service will make it work again...until the program gets recompiled.

RDi doesn't suffer from this because it includes an action to refresh the SEPs; this action must be run after a program is recompiled, and it works fine:
image

This action seems to be missing from the VS Code Debug Extension and should be added, IMHO.

@sebjulliand sebjulliand added bug A confirmed issue when something isn't working as intended debug Debug client issue (IBM) labels Dec 18, 2024
@heymchri
Copy link

@sebjulliand I was so glad to see this issue - we have been running into it as well, and we couldn't figure out what was going on. It's puzzling though that removing and adding the SEP doesn't fix this either.

@mkwan01
Copy link

mkwan01 commented Jan 8, 2025

@sebjulliand This is a known missing feature. There is some amount of work to implement this feature in the debug service. We will try to add this feature in the next debug service update.

@sebjulliand
Copy link
Collaborator Author

Lovely; thanks for the heads up @mkwan01 (and happy new year)!

@heymchri
Copy link

heymchri commented Jan 8, 2025

@mkwan01 Thanks for the update - this is a critical issue for our development team that prevents them from fully adopting VS Code for their IBM i work.

@mkwan01
Copy link

mkwan01 commented Jan 8, 2025

@heymchri Thanks for the comment. We will try to give this one a higher priority when planning for the next phase features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A confirmed issue when something isn't working as intended debug Debug client issue (IBM)
Projects
None yet
Development

No branches or pull requests

3 participants