Skip to content
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.

Truffle: Debug Transaction source file's cannot be correctly matched #219

Open
pupudaye opened this issue Sep 5, 2022 · 8 comments
Open
Assignees

Comments

@pupudaye
Copy link

pupudaye commented Sep 5, 2022

ctrl + shift + p

=> pop-up command list
=> select ”Truffle: Debug Transaction“

issues: Transaction list selection not triggered

ganache is started!

@acuarica
Copy link
Contributor

Hi @pupudaye, thanks for sending this.

Does the ganache instance have some transactions to select from? In other words, did you first deploy any contract to that instance? If so, can you specify the version of the extension you are running?

@pupudaye
Copy link
Author

Thanks, I have solved this problem! But I have a new problem, the source file cannot be correctly matched when debugging. What is the reason?

@acuarica
Copy link
Contributor

Glad to hear you solved the first issue. As for the second one, to help us troubleshoot, will you be able to provide some steps to reproduce the issue or a corresponding repo (if it's a public project)?

@acuarica acuarica changed the title ”Truffle: Debug Transaction“ Transaction list selection not triggered Truffle: Debug Transaction source file's cannot be correctly matched Sep 13, 2022
@pupudaye
Copy link
Author

pupudaye commented Sep 14, 2022

The truffle development case "metacoin" can be debugged normally, but it can't be debugged properly when switching to complex projects that rely on contracts.

The steps are not easy to express clearly, or can you give me some advice, how should I configure vscode setting.json and launch.json .

Is it because of relying on third-party libraries, such as: openzeppelin?

@acuarica
Copy link
Contributor

My best guess is that it's related to #54. We are experiencing some issues while debugging non-trivial Truffle projects.

We are investigating the root cause of this issue.

@kevinbluer
Copy link
Member

Hey @pupudaye, quick heads up that we've identified the issue and have a fix coming shortly (cc @xhulz) 👍

@pupudaye
Copy link
Author

Hey @pupudaye, quick heads up that we've identified the issue and have a fix coming shortly (cc @xhulz) 👍

OK thks!

@kevinbluer
Copy link
Member

Hey @pupudaye, apologies for the slight delay in follow-up to this one. However, good news in that the fix for this should hopefully now be in place (as of v2.6.0). Feel free to give it a try and let us know how you get on it 🤞

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

4 participants