Test of standard Transcrypt install fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript, python
Research direction
Start in ../transcrypt/development/automated_tests/transcrypt/ and reproduce the installation test with the two transcrypt commands from the report. Inspect the generated autotest.html files and the browser error in div_issues.issue559.mylib.mylib.js, then run the webserver test again. Done means the standard installation test displays its table without the reported ReferenceError.
Written by the indexing model from the issue text.
Description
After installing transcrypt 3.7.16. I try to test the installation (as described in the doco):
In the directory ../transcrypt/development/automated_tests/transcrypt/ I run transcrypt -b -c -da autotest. This succeeds.
Then I run transcrypt -r -c autotest. This succeeds as well (but strangely I have afterwards two autotest html files: An old autoTest.html from install time, and a new autotest.html from the transcrypt run. (Note teh different capitalisation.)
Finally I start the webserver and go to http://localhost:8000/autotest.html. but I get an empty table and the browser console shows the following error log:
div_issues.issue559.mylib.mylib.js:4 Uncaught ReferenceError: __all__ is not defined
at div_issues.issue559.mylib.mylib.js:4
at div_issues.issue559.mylib.mylib.js:4
at Function.<anonymous> (org.transcrypt.__runtime__.js:3)
at run559 (div_issues.issue559.js:3)
at Object.run (div_issues.js:35)
at org.transcrypt.autotester.js:15
at Function.<anonymous> (org.transcrypt.__runtime__.js:3)
at autotest.js:18
My environment:
| Tool | Version |
|---|---|
| OS | Linux RHEL 7 |
| Python | Version 3.7.4 |
| Browser | Google Chrome 75.0.3770.142 |
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TranscryptOrg/Transcrypt
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
TranscryptOrg/Transcrypt#913 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TranscryptOrg/Transcrypt#911 · 2 comments ·
-
IS: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TranscryptOrg/Transcrypt#908 ·
-
SUB: documentation
Difficulty 1/5 Under an hour Newbie friendliness 62/100
TranscryptOrg/Transcrypt#656 · 7 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
TranscryptOrg/Transcrypt#914 ·
All issues in TranscryptOrg/Transcrypt
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100