-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
YAML ParseError #187
Comments
your config file is wrong, you can try again by delete your old config and edit it again. |
Thank you. What is the changes that I need to do on that config file? Is this the error from node.js install? Can I re-install the node.js? What would you need from me? |
Are you referring to 'config.yml' file? |
Yes it is the config.yml file. You might mess up the structure of the file. So the best way in my opinion is just delete the config file and use the example config to do it again |
Thank you very much, I really appreciate it |
I got this error now. I used the Dev tools -> Network to get the APIKey and replaced it in authToken 01/11/2025 12:08:27] ERROR: Config file is not valid |
i just pushed new version with some changes. try delete the codespace and create a new one. Updated guide here https://github.com/phamleduy04/texas-dps-scheduler/wiki/Captcha-(Auth-Token) |
Thank you sir, I'll check this |
When I try to npm run start I'm getting the below error
/workspaces/texas-dps-scheduler/node_modules/yaml/dist/compose/composer.js:70
this.errors.push(new errors.YAMLParseError(pos, code, message));
^
YAMLParseError: All mapping items must start at the same column at line 44, column 1:
startDate: 01/10/2024
^
code: 'BAD_INDENT',
pos: [ 2030, 2031 ],
linePos: [ { line: 44, col: 1 }, { line: 44, col: 2 } ]
}
The text was updated successfully, but these errors were encountered: