Bug when npm run test #405
Comments
|
Hello, We apologize that you are having difficulties. The current version of CODAP is built on the Sproutcore development environment, which is old and unsupported. We limp along as best we can until our newer version is available. It is not clear what are wanting to do with the development version of CODAP and a bit unclear what went wrong, so I am going to make three suggestions. I hope one or more of them is helpful.
I hope these suggestions help. If not, please respond with more details about what you are trying to accomplish. Jonathan Sandoe |
|
Does `DG` in the url work? I thought it had to be `dg`.
Kirk
… On May 10, 2022, at 9:32 AM, Jonathan Sandoe ***@***.***> wrote:
Hello,
We apologize that you are having difficulties. The current version of CODAP is built on the Sproutcore development environment, which is old and unsupported. We limp along as best we can until our newer version is available.
It is not clear what are wanting to do with the development version of CODAP and a bit unclear what went wrong, so I am going to make three suggestions. I hope one or more of them is helpful.
You may not need a full development environment. If you are not intending to actually modify CODAP itself it may be sufficient to have a local version of CODAP. If so, you can get a zipped copy of the current version of CODAP's current build from https://codap.concord.org/releases/zips/latest.zip <https://codap.concord.org/releases/zips/latest.zip>. Just download it to your local machine, unzip it, and place it in the filesystem of a web server.
The development server takes some time to run the first time. Your version may, in fact, have run properly. It takes some time, sometimes five or more minutes, to deliver the initial view of CODAP. If you see a blank screen when you access http://0.0.0.0/DG <http://0.0.0.0/DG>, then this may be the problem. This is because, as I said, the development environment is comparatively ancient. It has to perform some conversions on the source and it is not very efficient. Once the server is running it will deliver pages quite a bit faster, though it can hang.
There may be Ruby incompatibilities with Sproutcore. If you see other errors in the browser when you access http://0.0.0.0/DG <http://0.0.0.0/DG>, this may be the problem. When the Sproutcore development environment was last under support, it recommended a the latest 1.x version of Ruby. We are able to run CODAP with Ruby 2.4.x.
I hope these suggestions help. If not, please respond with more details about what you are trying to accomplish.
Jonathan Sandoe
—
Reply to this email directly, view it on GitHub <#405 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABZNYQVY3D467YRVYINUFLVJKFRRANCNFSM5VQEWITQ>.
You are receiving this because you are subscribed to this thread.
|
|
Kirk, I stand corrected. Should by |
|
Hello, thank you for your detailed reply!The first suggestion is helpful. Actually, we have no plan to modify CODAP, so we have built the current version of CODAP. And it worked successfully.
But since i have put a lot of effort into the development version, I still wanted to figure out what the wrong was. We didn't use /DG in the url, so it might not the problem. Based on the error message, I guess the problem appeared in the core.js. It showed "TypeError: undefined is not a function (evaluating 'Object.assign')" in line 116. Then, all the lines which appears "DG." didn't work, and showed "ReferenceError: Can't find variable: DG". Is there any solution to fix this problem? Or it was caused by the environment, such as ruby version or nodejs version? In our server, we runned CODAP with Ruby 2.7 and node 10.14.1. I tried Ruby 2.4, But when npm start, something went wrong.
…------------------ 原始邮件 ------------------
发件人: "concord-consortium/codap" ***@***.***>;
发送时间: 2022年5月11日(星期三) 凌晨0:32
***@***.***>;
***@***.******@***.***>;
主题: Re: [concord-consortium/codap] Bug when npm run test (Issue #405)
Hello,
We apologize that you are having difficulties. The current version of CODAP is built on the Sproutcore development environment, which is old and unsupported. We limp along as best we can until our newer version is available.
It is not clear what are wanting to do with the development version of CODAP and a bit unclear what went wrong, so I am going to make three suggestions. I hope one or more of them is helpful.
You may not need a full development environment. If you are not intending to actually modify CODAP itself it may be sufficient to have a local version of CODAP. If so, you can get a zipped copy of the current version of CODAP's current build from https://codap.concord.org/releases/zips/latest.zip. Just download it to your local machine, unzip it, and place it in the filesystem of a web server.
The development server takes some time to run the first time. Your version may, in fact, have run properly. It takes some time, sometimes five or more minutes, to deliver the initial view of CODAP. If you see a blank screen when you access http://0.0.0.0/DG, then this may be the problem. This is because, as I said, the development environment is comparatively ancient. It has to perform some conversions on the source and it is not very efficient. Once the server is running it will deliver pages quite a bit faster, though it can hang.
There may be Ruby incompatibilities with Sproutcore. If you see other errors in the browser when you access http://0.0.0.0/DG, this may be the problem. When the Sproutcore development environment was last under support, it recommended a the latest 1.x version of Ruby. We are able to run CODAP with Ruby 2.4.x.
I hope these suggestions help. If not, please respond with more details about what you are trying to accomplish.
Jonathan Sandoe
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hello,
It is hard to say what went wrong. I suspect the culprit would be the
version of Ruby. I am glad you have a working environment, though. Jonathan
…On Tue, May 10, 2022 at 7:56 PM q707132127 ***@***.***> wrote:
Hello, thank you for your detailed reply!The first suggestion is helpful.
Actually, we have no plan to modify CODAP, so we have built the current
version of CODAP. And it worked successfully.
But since i have put a lot of effort into the development version, I still
wanted to figure out what the wrong was. We didn't use /DG in the url, so
it might not the problem. Based on the error message, I guess the problem
appeared in the core.js. It showed "TypeError: undefined is not a function
(evaluating 'Object.assign')" in line 116. Then, all the lines which
appears "DG." didn't work, and showed "ReferenceError: Can't find variable:
DG". Is there any solution to fix this problem? Or it was caused by the
environment, such as ruby version or nodejs version? In our server, we
runned CODAP with Ruby 2.7 and node 10.14.1. I tried Ruby 2.4, But when npm
start, something went wrong.
------------------ 原始邮件 ------------------
发件人: "concord-consortium/codap" ***@***.***>;
发送时间: 2022年5月11日(星期三) 凌晨0:32
***@***.***>;
***@***.******@***.***>;
主题: Re: [concord-consortium/codap] Bug when npm run test (Issue #405)
Hello,
We apologize that you are having difficulties. The current version of
CODAP is built on the Sproutcore development environment, which is old and
unsupported. We limp along as best we can until our newer version is
available.
It is not clear what are wanting to do with the development version of
CODAP and a bit unclear what went wrong, so I am going to make three
suggestions. I hope one or more of them is helpful.
You may not need a full development environment. If you are not intending
to actually modify CODAP itself it may be sufficient to have a local
version of CODAP. If so, you can get a zipped copy of the current version
of CODAP's current build from
https://codap.concord.org/releases/zips/latest.zip. Just download it to
your local machine, unzip it, and place it in the filesystem of a web
server.
The development server takes some time to run the first time. Your version
may, in fact, have run properly. It takes some time, sometimes five or more
minutes, to deliver the initial view of CODAP. If you see a blank screen
when you access http://0.0.0.0/DG, then this may be the problem. This is
because, as I said, the development environment is comparatively ancient.
It has to perform some conversions on the source and it is not very
efficient. Once the server is running it will deliver pages quite a bit
faster, though it can hang.
There may be Ruby incompatibilities with Sproutcore. If you see other
errors in the browser when you access http://0.0.0.0/DG, this may be the
problem. When the Sproutcore development environment was last under
support, it recommended a the latest 1.x version of Ruby. We are able to
run CODAP with Ruby 2.4.x.
I hope these suggestions help. If not, please respond with more details
about what you are trying to accomplish.
Jonathan Sandoe
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#405 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKBDOFX3P4QJZSCSZUYF3VJMOVXANCNFSM5VQEWITQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hello! I met a new problem on CODAP. When I tried to input Chinese in the text box, it failed. After entered “enter”, I got the result as follows. I have tried in Chrome, Safari and Microsoft Edge and met the same problem. Firefox was an exception, but text can't be deleted after inputed. Is there any solution to fix this problem?
…------------------ 原始邮件 ------------------
发件人: "concord-consortium/codap" ***@***.***>;
发送时间: 2022年5月15日(星期天) 凌晨0:54
***@***.***>;
***@***.******@***.***>;
主题: Re: [concord-consortium/codap] Bug when npm run test (Issue #405)
Hello,
It is hard to say what went wrong. I suspect the culprit would be the
version of Ruby. I am glad you have a working environment, though. Jonathan
On Tue, May 10, 2022 at 7:56 PM q707132127 ***@***.***> wrote:
> Hello, thank you for your detailed reply!The first suggestion is helpful.
> Actually, we have no plan to modify CODAP, so we have built the current
> version of CODAP. And it worked successfully.
>
>
> But since i have put a lot of effort into the development version, I still
> wanted to figure out what the wrong was. We didn't use /DG in the url, so
> it might not the problem. Based on the error message, I guess the problem
> appeared in the core.js. It showed "TypeError: undefined is not a function
> (evaluating 'Object.assign')" in line 116. Then, all the lines which
> appears "DG." didn't work, and showed "ReferenceError: Can't find variable:
> DG". Is there any solution to fix this problem? Or it was caused by the
> environment, such as ruby version or nodejs version? In our server, we
> runned CODAP with Ruby 2.7 and node 10.14.1. I tried Ruby 2.4, But when npm
> start, something went wrong.
>
>
>
>
> ------------------&nbsp;原始邮件&nbsp;------------------
> 发件人: "concord-consortium/codap" ***@***.***&gt;;
> 发送时间:&nbsp;2022年5月11日(星期三) 凌晨0:32
> ***@***.***&gt;;
> ***@***.******@***.***&gt;;
> 主题:&nbsp;Re: [concord-consortium/codap] Bug when npm run test (Issue #405)
>
>
>
>
>
>
> Hello,
>
> We apologize that you are having difficulties. The current version of
> CODAP is built on the Sproutcore development environment, which is old and
> unsupported. We limp along as best we can until our newer version is
> available.
>
> It is not clear what are wanting to do with the development version of
> CODAP and a bit unclear what went wrong, so I am going to make three
> suggestions. I hope one or more of them is helpful.
>
> You may not need a full development environment. If you are not intending
> to actually modify CODAP itself it may be sufficient to have a local
> version of CODAP. If so, you can get a zipped copy of the current version
> of CODAP's current build from
> https://codap.concord.org/releases/zips/latest.zip. Just download it to
> your local machine, unzip it, and place it in the filesystem of a web
> server.
>
> The development server takes some time to run the first time. Your version
> may, in fact, have run properly. It takes some time, sometimes five or more
> minutes, to deliver the initial view of CODAP. If you see a blank screen
> when you access http://0.0.0.0/DG, then this may be the problem. This is
> because, as I said, the development environment is comparatively ancient.
> It has to perform some conversions on the source and it is not very
> efficient. Once the server is running it will deliver pages quite a bit
> faster, though it can hang.
>
> There may be Ruby incompatibilities with Sproutcore. If you see other
> errors in the browser when you access http://0.0.0.0/DG, this may be the
> problem. When the Sproutcore development environment was last under
> support, it recommended a the latest 1.x version of Ruby. We are able to
> run CODAP with Ruby 2.4.x.
>
> I hope these suggestions help. If not, please respond with more details
> about what you are trying to accomplish.
>
> Jonathan Sandoe
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID:
> ***@***.***&gt;
>
> —
> Reply to this email directly, view it on GitHub
> <#405 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABLKBDOFX3P4QJZSCSZUYF3VJMOVXANCNFSM5VQEWITQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hello,
I am sorry you encountered this issue. We had a similar sounding issue with
the Text Component a while ago. It is described here:
https://www.pivotaltracker.com/story/show/173260782. The problem was in a
third party library we use in the Text Component. Perhaps there is a new
issue or variant. If you could tell us a little more about the problem, we
may be able to resolve it. For example, what type of computer and what
operating system, and keyboard. Are there settings in the operating system
for text entry, and if so, how are they configured? If you are able to send
us screenshots or video screen captures, this would also be helpful.
Thank you,
Jonathan Sandoe
…On Tue, May 17, 2022 at 5:01 AM q707132127 ***@***.***> wrote:
Hello! I met a new problem on CODAP. When I tried to input Chinese in the
text box, it failed. After entered “enter”, I got the result as
follows. I have tried in Chrome, Safari and Microsoft Edge and met the same
problem. Firefox was an exception, but text can't be deleted after inputed.
Is there any solution to fix this problem?
------------------ 原始邮件 ------------------
发件人: "concord-consortium/codap" ***@***.***>;
发送时间: 2022年5月15日(星期天) 凌晨0:54
***@***.***>;
***@***.******@***.***>;
主题: Re: [concord-consortium/codap] Bug when npm run test (Issue #405)
Hello,
It is hard to say what went wrong. I suspect the culprit would be the
version of Ruby. I am glad you have a working environment, though.
Jonathan
On Tue, May 10, 2022 at 7:56 PM q707132127 ***@***.***> wrote:
> Hello, thank you for your detailed reply!The first suggestion is
helpful.
> Actually, we have no plan to modify CODAP, so we have built the
current
> version of CODAP. And it worked successfully.
>
>
> But since i have put a lot of effort into the development version, I
still
> wanted to figure out what the wrong was. We didn't use /DG in the
url, so
> it might not the problem. Based on the error message, I guess the
problem
> appeared in the core.js. It showed "TypeError: undefined is not a
function
> (evaluating 'Object.assign')" in line 116. Then, all the lines which
> appears "DG." didn't work, and showed "ReferenceError: Can't find
variable:
> DG". Is there any solution to fix this problem? Or it was caused by
the
> environment, such as ruby version or nodejs version? In our server,
we
> runned CODAP with Ruby 2.7 and node 10.14.1. I tried Ruby 2.4, But
when npm
> start, something went wrong.
>
>
>
>
> ------------------&nbsp;原始邮件&nbsp;------------------
> 发件人: "concord-consortium/codap" ***@***.***&gt;;
> 发送时间:&nbsp;2022年5月11日(星期三) 凌晨0:32
> ***@***.***&gt;;
> ***@***.******@***.***&gt;;
> 主题:&nbsp;Re: [concord-consortium/codap] Bug when npm run test
(Issue #405)
>
>
>
>
>
>
> Hello,
>
> We apologize that you are having difficulties. The current version of
> CODAP is built on the Sproutcore development environment, which is
old and
> unsupported. We limp along as best we can until our newer version is
> available.
>
> It is not clear what are wanting to do with the development version
of
> CODAP and a bit unclear what went wrong, so I am going to make three
> suggestions. I hope one or more of them is helpful.
>
> You may not need a full development environment. If you are not
intending
> to actually modify CODAP itself it may be sufficient to have a local
> version of CODAP. If so, you can get a zipped copy of the current
version
> of CODAP's current build from
> https://codap.concord.org/releases/zips/latest.zip. Just download it
to
> your local machine, unzip it, and place it in the filesystem of a web
> server.
>
> The development server takes some time to run the first time. Your
version
> may, in fact, have run properly. It takes some time, sometimes five
or more
> minutes, to deliver the initial view of CODAP. If you see a blank
screen
> when you access http://0.0.0.0/DG, then this may be the problem.
This is
> because, as I said, the development environment is comparatively
ancient.
> It has to perform some conversions on the source and it is not very
> efficient. Once the server is running it will deliver pages quite a
bit
> faster, though it can hang.
>
> There may be Ruby incompatibilities with Sproutcore. If you see other
> errors in the browser when you access http://0.0.0.0/DG, this may be
the
> problem. When the Sproutcore development environment was last under
> support, it recommended a the latest 1.x version of Ruby. We are able
to
> run CODAP with Ruby 2.4.x.
>
> I hope these suggestions help. If not, please respond with more
details
> about what you are trying to accomplish.
>
> Jonathan Sandoe
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID:
> ***@***.***&gt;
>
> —
> Reply to this email directly, view it on GitHub
> <
#405 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ABLKBDOFX3P4QJZSCSZUYF3VJMOVXANCNFSM5VQEWITQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#405 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKBDPNF4XFQ7RT5H445QDVKODARANCNFSM5VQEWITQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm trying to build a codap application on my server.
According to the instruction, after run "npm start", I got output like this. But the web page didn't work successfully.
Then I runned "http-server -p 4020", port 4020 can be accessed normally, indicating that it should not be a problem with the network environment. After that, I runned "npm run test", got the following information:
I don't know how to fix this and get the site to start properly. But it doesn't seem to be a problem with the configuration of the environment, but rather a procedural problem. Hope we can get your help. Thanks a lot!
The text was updated successfully, but these errors were encountered: