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

Error : INPUT is not valid #3

Open
mdzakirhussain opened this issue Nov 29, 2019 · 7 comments
Open

Error : INPUT is not valid #3

mdzakirhussain opened this issue Nov 29, 2019 · 7 comments
Assignees
Labels

Comments

@mdzakirhussain
Copy link

I had followed all steps given in Installation Procedure, but then I am getting the following error

zakir@zakir-virtual-machine:~$ atalanta c17.bench
INPUT is not valid
Fatal error: Error in circuit file

@mdzakirhussain
Copy link
Author

I had followed all steps given in Installation Procedure, but then I am getting the following error

zakir@zakir-virtual-machine:~$ atalanta c17.bench
INPUT is not valid
Fatal error: Error in circuit file

I am still waiting for the reply

@hsluoyz
Copy link
Owner

hsluoyz commented Jan 15, 2020

It's open source. Please debug the code to find where outputs INPUT is not valid

@hsluoyz hsluoyz self-assigned this Jan 15, 2020
@edrichv
Copy link

edrichv commented Feb 15, 2021

I have found that if you use CRLF as your line endings, this error appears. Try using LF instead?

@hsluoyz
Copy link
Owner

hsluoyz commented Feb 15, 2021

@EdrichVeburg can you make a PR to fix it?

@edrichv
Copy link

edrichv commented Feb 15, 2021

A quick and easy fix for the user is to just remove all CR characters from their .bench files. Instead of using CRLF, they only need LF. Do you want to add support for CR in the tool? Otherwise you just need to add a note to the readme so that users use LF instead of CRLF

@edrichv
Copy link

edrichv commented Feb 15, 2021

A quick and easy fix for the user is to just remove all CR characters from their .bench files. Instead of using CRLF, they only need LF. Do you want to add support for CR in the tool? Otherwise you just need to add a note to the readme so that users use LF instead of CRLF

This - of course - is if this even fixes @mdzakirhussain 's issue.

@hsluoyz
Copy link
Owner

hsluoyz commented Feb 15, 2021

@mdzakirhussain is this the case?

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

No branches or pull requests

3 participants