Skip to content

Can't find reader macros #320

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

Closed
caioaao opened this issue Mar 31, 2016 · 5 comments
Closed

Can't find reader macros #320

caioaao opened this issue Mar 31, 2016 · 5 comments

Comments

@caioaao
Copy link

caioaao commented Mar 31, 2016

Refactors that need to run the project fail with the following error (full stack trace here - file paths were removed):

error in process filter: cljr--get-error-value: Error in nrepl-refactor: java.util.concurrent.ExecutionException: clojure.lang.ExceptionInfo: No reader function for tag time {:type :reader-exception, :line 31, :column 30, :file "..."}

I've printed the value from *data-readers* in CIDER repl and the macros are being declared correctly. Everything else works fine (running tests, loading code to CIDER, etc).
Idk if it's related or not, but the macros are declared in other projects. I've tried copying the data_readers.clj file from those project to the one I'm working, but it didn't work either.
Versions used:

  • cider: 20160216.440
  • clj-refactor: 20160329.331
  • cider-nrepl: 0.11.0-SNAPSHOT
  • refactor-nrepl: 2.2.0-SNAPSHOT
@benedekfazekas
Copy link
Member

pls upgrade to latest snapshots (cider 0.12.0-SNAPSHOT and clj-refactor 2.3.0-SNAPSHOT) just to rule out that this is related to this mranderson issue: benedekfazekas/mranderson#12

@expez
Copy link
Member

expez commented Apr 1, 2016

Also, is this with leiningen?

@caioaao
Copy link
Author

caioaao commented Apr 5, 2016

@benedekfazekas looks like that issue was fixed in 2.2.0. Anyway, I tested it with the versions you said and the error is the same.

@expez yes, I'm using leiningen here

@caioaao
Copy link
Author

caioaao commented Apr 7, 2016

Looks like the error was fixed, but another one appeared:
stacktrace
As this is related to refactor-nrepl, should I reopen the issue there instead of here?

@expez
Copy link
Member

expez commented Apr 8, 2016

Looks like the error was fixed

I published the latest snapshot after you posted this message so I'm not sure you actually ran a new version.

but another one appeared:
stacktrace_readerm.txt

In the future, could you please link to a gist, so I don't have to download a file to view stacktraces?

As this is related to refactor-nrepl, should I reopen the issue there instead of here?

Yes, that would be great!

Thanks for taking the time to report issues!

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

No branches or pull requests

3 participants