PR implements TailCallException handler
in the IdExecutionInstrument sending
correct value updates.
- implement onReturnExceptional of the
runtime instrument
- add onExceptionalCallback to the
runtime instrument
PR introduces the MetodCallsCache created per frame execution, meaning
that it is not persisted in between the runs. The cache tracks which
calls have been fired during the program execution (and sent as a
notification to the user). When the program finishes, we compute the set
of calls that have not been executed and send them to the user as well.
- add: MethodCallsCache temporary storage tracking the executed method
calls
- add: sendMethodCallUpdates flag enabling sending all the method calls
of the frame as a value updates
In the current workflow, at first, the default Unnamed project is
created, and the Suggestions database is populated with entries from the
Unnamed.* modules. When the user changes the name of the project, we
should update all modules in the Suggestion Database with the new
project name.
This PR implements module renaming in the Suggestions database and fixes
the initialization issues.
- add: search/invalidateSuggestionsDatabase JSON-RPC command that resets
the corrupted Suggestions database
- update: SuggestionsHandler to rename the modules in the
SuggestionsDatabase when the project is renamed
- fix: MainModule initialization
ExpressionValueUpdate notification contains information about the
executed object. To have the full information about this object, IDE
needs the id of the corresponding suggestion. PR updates the
notification adding the suggestion id of the executed object.
- update: public API for ExpressionValueUpdate notification
- update: ContextEventsListener groups ExpressionValueUpdates and sends
them in a batch
- update: ContextRegistry listens to the notifications from runtime and
routes them to the corresponding listener.
- test: add ContextEventsListenerSpec
1. Implements the `enso install distribution` command.
2. Implements a DistributionManager which is used for managing installation
layout in the launcher.
PR #1034Resolves#1010
1. This commit ensures that builds outside of repository don't file not being
able to fetch the git metadata for the version string but just report a
warning.
2. It also clarifies documentation on getting Enso artifacts from CI.
PR #1036
1. Our builds include a version check which for stability does not rely
on build.sbt but instead on querying enso --version. Building the
engine takes a lot of time, so to save that time on failed builds,
we ensure that the launcher is built first (which is much faster)
and only if its version check succeeds, the engine build is
attempted. This is achieved by making the `build-engine` job in
`release.yml` depend on `build-launcher`.
2. Enso version is bumped to `0.1.0`.
1. This commit adds an extensive library for parsing commandline
arguments and formatting output.
2. It implements the expected CLI for the launcher.
3. It turns off parallel execution on the CI in hopes of making it
more stable.
4. It implements plugin support in the launcher.
