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

Problem installing from scratch #137

Closed
lscheffler opened this issue Aug 6, 2023 · 11 comments
Closed

Problem installing from scratch #137

lscheffler opened this issue Aug 6, 2023 · 11 comments

Comments

@lscheffler
Copy link
Contributor

📝 Provide detailed reproduction steps (if any)

  1. pick empty folder
  2. install as documented in https://github.com/VFPX/Thor/blob/master/Docs/Thor_install.md
  3. start a plain VFP (no additional tools)
  4. run Thor.app from the folder above

✔️ Expected result

Should install

❌ Actual result

Complains about missing cthorlogforcfu property

If one ignores the error multiple times, Thor will sooner or later run.

@Jimrnelson
Copy link
Collaborator

Rats!

Does the error occur if you run it again?

@lscheffler
Copy link
Contributor Author

Only on first run on freshly downloaded Thor.

@Jimrnelson
Copy link
Collaborator

OK, thanks, that is very helpful

@Jimrnelson
Copy link
Collaborator

I have just released an update and the error does not recur for me.

Can you try again?

In the future, when getting a bug, can you include some of the debugger information? Code with the error, call stack, local variables are always helpful.

Thanks.

@lscheffler
Copy link
Contributor Author

It runs without error.

  • only it dates 2023/08/05

I really like to give better information about bugs. (Myself hates issues text like this) But this is Thor. It's all Execscript in Execsript, and all I see is the message that the debugger can not see the source code. There was even no pointer to the actual code line. I can try to sreenshot the debugger, but this one looked like it run into a secondary problem (error while logging an error). Would a screenshot be of help?

@Jimrnelson
Copy link
Collaborator

Odd that I got better information about the error when I reproduced it

The screen stack would have been helpful, actually, and locals, even if I could not see the code.

@lscheffler
Copy link
Contributor Author

ok, I try to remember it.

It would be a help if the template for the bug (.github/ISSUE_TEMPLATE/bug_report.md) hinting what you need.

@Jimrnelson
Copy link
Collaborator

I agree.

I think I would like a screenshot of the original error message, and also the trace,, call stack, and locals from the debugger:

@lscheffler
Copy link
Contributor Author

Right now, the failure of this issue? Ooops. I will look if I can get the old version of the zip ...

@Jimrnelson
Copy link
Collaborator

No, this issue is closed.

I was responding to your comment about the bug report template.

@lscheffler
Copy link
Contributor Author

see merge request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants