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.

Sign up for GitHub

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

Jump to bottom

ViVeTool-GUI Feature scanner write access failure of final step #37

Closed
Zantetsukens-cut opened this issue Nov 5, 2022 · 6 comments
Closed

ViVeTool-GUI Feature scanner write access failure of final step #37

Zantetsukens-cut opened this issue Nov 5, 2022 · 6 comments
Assignees
@PeterStrick
Labels
Bug 🐛 Something isn't working Version 1.7 To do/In-Progress in Version 1.7

Comments

@Zantetsukens-cut
Copy link

I have an issue with the feature scanner failing at the final step of creating/ transferring final result log after a very long scan session ( that ran flawlessly by the way) I can't give you the actual error code because that would take 12 hours to retrieve that. but it says "write access error" and I scoured my hard drive looking for that document it was nowhere

P.S. I noticed if you run the scan as trusted installer it was successful at scanning items it had failed at using my admin profile.
@PeterStrick PeterStrick added the Bug 🐛 Something isn't working label Nov 6, 2022
@PeterStrick
Copy link
Owner

The Version of the Feature Scanner in v1.7-Testing currently saves the Feature List to a Text File within the Folder that you specified to download the Debug Symbols into.

After that, it tries to copy that Text File to your Desktop, which seems to fail.

For Example, if you selected C:\New folder as the Debug Symbol Path and your current Build that you are scanning one would be 25231 then the Text File should be at C:\New folder\25231.txt

The Logic for the Scanning using mach2 can be found here https://github.com/PeterStrick/ViVeTool-GUI/blob/v1.7-Testing/ViVeTool-GUI.FeatureScanner/ScannerUI.vb#L367

The latest version of the Feature Scanner from the v1.7-Testing Branch can be found here https://github.com/PeterStrick/ViVeTool-GUI/releases/tag/v1.6.999.1_v1.7-Branch_FeatureScanner

After that, it tries to copy that Text File to your Desktop, which seems to fail.

An alternative to this that I have considered would be to ask the User where the Feature List should be saved, and re-open that same Dialog if any Error or Exceptions occurs until the File was saved.

@Zantetsukens-cut
Copy link
Author

Zantetsukens-cut commented Nov 14, 2022 via email

@Zantetsukens-cut
Copy link
Author

Zantetsukens-cut commented Nov 15, 2022 via email

@Zantetsukens-cut
Copy link
Author

Zantetsukens-cut commented Nov 19, 2022 via email

@PeterStrick
Copy link
Owner

So on the fourth time it actually worked

Nice to see that the Feature List was finally scanned and created. The Feature Scanner is going to get a revamp in the entire "Saving the Feature List" aspect hopefully soon/tomorrow, by actually asking you where to save the Results

But then I went to the Mach 2 repository and tried to upload the file and it told me that uploads are disabled.

Hmmm, so I guess the Feature Scanner will be sorta for personal use only then

and then I tried to load this into the Vivetool GUI and part way through loading all the feature information it has a copy error.

As for the ViVeTool GUI Copy Error, could you send a Exception Message/Screenshot if you still have it? The results file seems to be cut off or Github is not displaying the entirety of it

Also Sorry for the delayed Response, was dealing with Family Issues and School Exams so didn't really have time at all to work on ViVeTool GUI, luckily my Exams are all finished, Family Issues kinda over and my Winter Holiday for School and Work is gonna start from 22th December to New Years Eve which means plenty of more time to work on ViVeTool GUI

@PeterStrick PeterStrick mentioned this issue Dec 17, 2022
Closed
@PeterStrick PeterStrick added the Version 1.7 To do/In-Progress in Version 1.7 label Dec 17, 2022
@PeterStrick
Copy link
Owner

For now fixed in the Emergency Bugfix Release 1.6.999.3

Will be properly bug tested until Version 1.7 releases to the public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PeterStrick PeterStrick

Labels
Bug 🐛 Something isn't working Version 1.7 To do/In-Progress in Version 1.7
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PeterStrick @Zantetsukens-cut