First user experiences #5955
Replies: 2 comments 1 reply
-
That's great! I really want to avoid manually setting node version via nvm when switching between the branches. @mwu-tow do you think the proposed solution is possible? @Procrat please create an issue for that.
We need to update our docs with clear instructions. Installing the correct
Tracked in #5505
Indeed. @jdunkerley is it a bug?
Fair point, but the decision to use Ctrl is deliberate. I think no actions are needed for now, although we can revisit it in the future.
I think this should be covered by a bunch of tasks for CB. Namely #5232 and #5356
What OS do you use? It is normal for Mac, but shouldn't happen otherwise.
Again, it's a deliberate decision, but we're aware that it might be suboptimal for some users.
Yeah, I would like it too. I think we will cover it with #5354, we had talked about it with @farmaazon
Please create an issue for every point you listed, if you can reproduce it. |
Beta Was this translation helpful? Give feedback.
-
Regarding some other backend issues - I would appreciate if you included full logs with stacktraces. Can't do much with oneliners. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Having had my first experience with the Enso product yesterday, I figured it would be good to share my first experiences in case it can help improve our product. I only accessed online resources (so mostly without asking for help) to adequately capture what other new users would encounter. I believe this is a product that's well on its way to being amazing, so don't take these points as criticism.
Building the IDE
fnm,nvm,nvs,n,nave,nodeenv,nodist, ...)I can make a PR with it, but the version number would be duplicated in
build-config.yaml, unless the build script were to look for the version number.conda. I guessed it tried to install flatbuffers/flatc, which is the only mention ofcondainCONTRIBUTING.md. (I hadn't installed it as it was marked as optional in the README.) However, after I installed flatc directly, it still failed with the same error. After digging through the logs, I saw a warning sayingFailed to find flatc in version == 1.12.0. Found version: 23.3.3.Ilya suggested building with a specific release of the engine, e.g.:
Running Enso
Data.fetchnode empty? Shouldn't it show the returned JSON?Table.from_rows, which after a second shows an error message "Methodfrom_rowsof Table.value could not be found." in a box that completely covers the input box, so that I'm unable to see what I type.On cloud.enso.org
Returning back to cloud.enso.org showed that the workspace had stopped, so that's probably what went wrong.
0.up_to 100 . to_vector . map .noiseexample. This was a particulary frustrating experience.Using the REPL
Table.readwas immediately available. In the REPL, I tried:Trying a book club challenge
Date.parsenode, I selected "Report Error", after which it completed toStandard.Base.Error.Problem_Behavior.Report_Errorbut then it saidDay_Of_Weekshowed[Object object].Table.from_objectsthrows an exception for anything that isn't a JS_Object, Number, Boolean, Text or Nothing, but the docs don't mention that.Syntax reference
Component reference
Data.read, but that didn't work.File_Format, which the documentation ofData.readmentions, but I couldn't find it. I also couldn't findDay_Of_Week.Beta Was this translation helpful? Give feedback.
All reactions