Errors when accessing docs or metas with no cache
Closedopened 4 years ago by otherjoel · 7 comments
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
I am seeing some errors I did not expect when using
get-metason documents that aren't yet cached. Here are steps to recreate the problem:
pollen.rktconsisting of only one line,
example.html.pmconsisting of some token Pollen markup, e.g.:
sandbox.rktin the same folder. Save the file with these contents:
sandbox.rktfile, click Run, then at the REPL, enter
Upon doing this, I receive an error:
raco pollen render example.html, which should complete without problems.
raco pollen reset, then do step 5 above (clicking Run again to restart the REPL), I again get the error.
I should expect to be able to use
get-metasno matter what the state of the cache is, correct?
This is with Pollen version 2.0.2038.749 on Racket 6.12 on macOS 10.14.3.
Hmm, I can't reproduce this (on Racket 7.1). The msg is coming from
errortrace, which is weird. Have you tried doing
raco setup errortrace-lib?
raco setup errortrace? Sorry for the human experimentation. Usually the message "reference to a module that is not available" indicates out-of-date compiled files.
raco setup errortraceworked fine but did not affect the problem.
Then I went a little overboard and did
raco setup --cleanfollowed by
raco setup— still did not fix the problem.
Then I installed Racket 7.2, then installed pollen from within the 7.2 DrRacket (user scope). The problem does not occur with 7.2
Finally I deleted my 6.12 installation, downloaded and reinstalled 6.12 fresh from the Racket website, and reinstalled pollen (user scope). The problem does reoccur in this situation.
OK, thanks for the detail. I'll look into this shortly on 6.12.
I’ve installed Racket 6.12 (on OS X 10.14.1) and can't yet reproduce the issue. Another idea: does the issue still surface if you choose "No debugging or profiling" in the DrRacket Choose Language box?
Changing that setting does seem to fix the problem in 6.12 DrRacket.
Also, interestingly, I can no longer reproduce the problem in the CLI REPL for 6.12 (by just running
racketat the prompt). I did encounter it there too at least once, but that was in the context of my original project, before I created the MVE and opened this issue.
So given that you can't reproduce it, it seems likely the problem is/was on my end, and not a problem in Pollen at any rate.