Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Parse Error: Encountered "<EOF>" at line 0, column 0 and token - Regression in InJarFilenameToStream

See original GitHub issue

@pfeodrippe Commit 00cd5641d5d07b79818a7096fc1cbcc02388070c introduces a regression with model.InJarFilenameToStream

markus@avocado:~/src/TLA/tla((no branch, bisect started on master))$ java -jar tlatools/org.lamport.tlatools/dist/tla2tools.jar 
@!@!@STARTMSG 2262:0 @!@!@
TLC2 Version 2.15 of Day Month 20?? (rev: ${git.shortRevision})
@!@!@ENDMSG 2262 @!@!@
@!@!@STARTMSG 2187:0 @!@!@
Running breadth-first search Model-Checking with fp 80 and seed -5197081046360030598 with 1 worker on 4 cores with 5952MB heap and 64MB offheap memory [pid: 104041] (Linux 5.4.0-66-generic amd64, Ubuntu 11.0.10 x86_64, MSBDiskFPSet, DiskStateQueue).
@!@!@ENDMSG 2187 @!@!@
@!@!@STARTMSG 2220:0 @!@!@
Starting SANY...
@!@!@ENDMSG 2220 @!@!@
Parsing file /tmp/MC.tla
Parsing file /tmp/EWD840.tla (/tmp/MC.tla)
***Parse Error***
Was expecting "---- MODULE (beginning of module)"
Encountered "<EOF>" at line 0, column 0 and token "" 

Residual stack trace follows:
Begin module starting at line 0, column 0.
Module definition starting at line 0, column 0.

a
Fatal errors while parsing TLA+ spec in file MC

tla2sany.semantic.AbortException
@!@!@STARTMSG 2219:0 @!@!@
SANY finished.
@!@!@ENDMSG 2219 @!@!@
@!@!@STARTMSG 2185:0 @!@!@
Starting... (2021-03-14 20:22:16)
@!@!@ENDMSG 2185 @!@!@
@!@!@STARTMSG 3002:1 @!@!@
Parsing or semantic analysis failed.
@!@!@ENDMSG 3002 @!@!@
@!@!@STARTMSG 2186:0 @!@!@
Finished in 355ms at (2021-03-14 20:22:16)
@!@!@ENDMSG 2186 @!@!@

Reproduce by copying a spec and model to src/model, followed by ant -f customBuild.xml clean compile dist, and running java -jar dist/tla2tools.jar.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

lemmycommented, Mar 15, 2021

Please make sure to add a test case.

1reaction

pfeodrippecommented, Mar 15, 2021

😮 I will check it today, thanks for the report, Markus.

Top Results From Across the Web

Cannot parse 'XX*': Encountered "<EOF>" · Issue #632 - GitHub

Today, we have encountered a random error, that could not be reproduced: Cannot parse 'Bl*': Encountered "<EOF>" at line 1, column 18.

How to fix `Encountered <EOF> at line 1 ...` issues

1 Answer 1 · Yeah, I fixed this and the syntax error is gone but it gives this error Exception at execAction:dataHandler23505 :...

ParseException line 1:X missing EOF at '-' near 'keyword'" in ...

When I run an MSCK REPAIR TABLE or SHOW CREATE TABLE statement in Amazon Athena, I get an error similar to the following:...

Lexical error (syntax error) when parsing valid Solr query - IBM

TokenMgrError : Lexical error at line 1, column 2. Encountered: "\"" (34), after : "\"" at org.apache.solr.parser.QueryParserTokenManager.getNextToken(Quer ...

cannot parse __indextypecontent encountered eof error using

When we make the calls initially it pulls the data down correctly after that however it starts throwing this error: Cannot parse '__IndexType: ......