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

Can't find miner.conf when installed on a path with Unicode characters #19

Closed
quetzalcoatl opened this issue Jun 10, 2020 · 0 comments
Closed

Can't find miner.conf when installed on a path with Unicode characters #19

quetzalcoatl opened this issue Jun 10, 2020 · 0 comments
Assignees
@quetzalcoatl
Labels
bug Something isn't working
Projects
temp board

Comments

@quetzalcoatl
Copy link
Owner

Describe the bug
Blagominer doesn't start and reports it can't find miner.conf file.
Works fine when moved to a directory with a simpler path.

To Reproduce
Steps to reproduce the behavior:

  1. Get any recent blago, unpack to any folder.
  2. Rename the folder so it has non-ascii characters. For example, on Windows 10, just copy the folder so it gets automatic suffix of — copy. Note the long dash.
  3. Run blago from within that folder.
  4. See error

Expected behavior
Blago doesn't care about what path it is installed to.

Desktop (please complete the following information):

  • OS: Windows 10, and probably any OS that handles non-ASCII characters in file path
  • Version 2.300004.0 and probably all earlier
@quetzalcoatl quetzalcoatl added the bug Something isn't working label Jun 10, 2020
@quetzalcoatl quetzalcoatl self-assigned this Jun 10, 2020
@quetzalcoatl quetzalcoatl added this to To do in temp board Jun 10, 2020
@quetzalcoatl quetzalcoatl moved this from To do to In progress in temp board Jun 11, 2020
@quetzalcoatl quetzalcoatl moved this from In progress to To do in temp board Jun 11, 2020
@quetzalcoatl quetzalcoatl moved this from To do to In progress in temp board Jun 11, 2020
quetzalcoatl added a commit that referenced this issue Nov 29, 2020
@quetzalcoatl
[GH-19] got rid of: narrow-char file paths
b5760c8
quetzalcoatl added a commit that referenced this issue Nov 29, 2020
@quetzalcoatl
[GH-19] got rid of: narrow-char file paths, mostly
2a7976c
quetzalcoatl added a commit that referenced this issue Nov 29, 2020
@quetzalcoatl
[GH-19] oh god paths d'oh
0ab5b64
quetzalcoatl added a commit that referenced this issue Nov 29, 2020
@quetzalcoatl
[GH-19] swapped rapidjson's default UTF8 document to UTF16/wchar_t; p…
647e4d8 
…lus tons of other string->wstring updates
temp board automation moved this from In progress to Done Nov 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@quetzalcoatl quetzalcoatl

Labels
bug Something isn't working
Projects
temp board
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@quetzalcoatl