[GR-32720] Fix links

PullRequest: graal/9966

Author: eregon

docs/examples/examples.md

@@ -20,5 +20,5 @@ Here you can also find an even more sophisticated example of polyglot native exe
 
 The [Java/Kotlin Native Image Example](java-kotlin-aot.md) demonstrates how to compile a Java and Kotlin application ahead-of-time, and illustrates the performance gain.
 
-The [Oracle Database Example](examples/mle-oracle.md) contains instructions on how to run the Oracle Database Multilingual Engine (MLE) which is the integration of GraalVM in the Oracle
+The [Oracle Database Example](mle-oracle.md) contains instructions on how to run the Oracle Database Multilingual Engine (MLE) which is the integration of GraalVM in the Oracle
 Database 21c.

docs/reference-manual/java/README.md

@@ -33,5 +33,5 @@ This mode allows you to [debug the GraalVM compiler with a Java debugger](Operat
 
 ## Interoperability
 
-In addition to running JVM-based languages on GraalVM, you can also call any other language implemented with the [Truffle language implementation framework](../truffle-framework/README.md) directly from Java.
-See the [Polyglot Programming](../polyglot-programming.md) and [Embedding Languages](../embed-languages.md) guides for more information about interoperability with other programming languages.
+In addition to running JVM-based languages on GraalVM, you can also call any other language implemented with the [Truffle language implementation framework](../../../truffle/docs/README.md) directly from Java.
+See the [Polyglot Programming](../polyglot-programming.md) and [Embedding Languages](../embedding/embed-languages.md) guides for more information about interoperability with other programming languages.

docs/reference-manual/languages.md

@@ -13,9 +13,9 @@ GraalVM's polyglot capabilities make it possible to mix multiple programming lan
 If you are mostly interested in GraalVM's support for a specific language, here you can find the most extensive documentation:
 * [Java](java/README.md)
 * [Java on Truffle](java-on-truffle/README.md)
-* [JavaScript and Node.js](js/README.md)
+* [JavaScript and Node.js](https://github.com/oracle/graaljs/blob/master/docs/user/README.md)
 * [LLVM Languages](llvm/README.md)
-* [Python](python/README.md)
-* [R](r/README.md)
-* [Ruby](ruby/README.md)
+* [Python](https://github.com/oracle/graalpython/blob/master/docs/user/README.md)
+* [R](https://github.com/oracle/fastr/blob/master/documentation/user/README.md)
+* [Ruby](https://github.com/oracle/truffleruby/blob/master/doc/user/README.md)
 * [WebAssembly](wasm/README.md)

docs/tools/graalvm-insight.md

@@ -146,7 +146,7 @@ Hello from GraalVM Ruby!
 It is necessary to start the Ruby launcher with the `--polyglot` parameter, as the _source-tracing.js_ script remains written in JavaScript.
 
 A user can instrument any language on top of GraalVM, but also the Insight scripts can be
-written in any of the GraalVM supported languages (implemented with the [Truffle language implementation framework](../graalvm-as-a-platform/truffle-framework/README.md)).
+written in any of the GraalVM supported languages (implemented with the [Truffle language implementation framework](../../truffle/docs/README.md)).
 
 1. Create the _source-tracing.rb_ Ruby file:
 ```ruby

docs/tools/vscode/micronaut/README.md

@@ -112,8 +112,6 @@ For more details, continue reading to the [Micronaut documentation](https://guid
 The Micronaut support in VSCode also allows to build and deploy Docker image to a Docker Registry.
 Use action View > Command Palette > Micronaut: Deploy... and select **dockerPush** to deploy dockerized Micronaut application or **dockerPushNative** to build and push docker with a native executable of Micronaut application.
 
-![Micronaut Deploy Commands](images/micronaut-deploy-commands.png)
-
 Besides that, you can also push a Micronaut application or a native executable to a Docker Registry from the VS Code terminal window. A particular Docker Registry can be configured in the build, see the [Micronaut Deploying Application](https://micronaut-projects.github.io/micronaut-maven-plugin/latest/examples/deploy.html) documentation.
 
 ### Feedback

truffle/README.md

@@ -17,7 +17,7 @@ Software of the Johannes Kepler University Linz.
 
 ## Using Truffle
 
-If you are looking for documentation on how to use Truffle, please consult the documentation [here](../docs/truffle-framework/README.md) or [on the website](https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/).
+If you are looking for documentation on how to use Truffle, please consult the documentation [here](docs/README.md) or [on the website](https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/).
 
 ## Hacking Truffle
 

truffle/docs/Exit.md

@@ -1,13 +1,20 @@
+---
+layout: docs
+toc_group: truffle
+link_title: Context Exit
+permalink: /graalvm-as-a-platform/language-implementation-framework/Exit/
+---
+
 # Context Exit
 
 Different Truffle (guest) languages may use different mechanisms for exiting. This is not optimal as a Truffle language has no way to detect and handle an exit triggered by a different language.
 
-As of 22.0 Truffle has support for polyglot context hard explicit exit triggered by guest languages using [TruffleContext.closeExited(Node,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleContext.html#closeExited-com.oracle.truffle.api.nodes.Node-int-). 
+As of 22.0 Truffle has support for polyglot context hard explicit exit triggered by guest languages using [TruffleContext.closeExited(Node,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleContext.html#closeExited-com.oracle.truffle.api.nodes.Node-int-).
 It provides a unified way for languages to trigger the exit of the underlying polyglot context. When triggered, all initialized
 guest languages are first notified using [TruffleLanguage.exitContext(C,ExitMode,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleLanguage.html#exitContext-C-com.oracle.truffle.api.TruffleLanguage.ExitMode-int), then all context threads are stopped, and finally, the context is closed.
-The hard explicit exit is simply referred to as "hard exit". 
+The hard explicit exit is simply referred to as "hard exit".
 
-The hard exit is only one of the three types of exit in Truffle. There are the following types of exit. 
+The hard exit is only one of the three types of exit in Truffle. There are the following types of exit.
 
 * The new hard exit introduced above
   * Hard exit notifications are executed with `ExitMode.HARD` as the second parameter of `TruffleLanguage.exitContext(C,ExitMode,int)`.
@@ -19,9 +26,9 @@ The hard exit is only one of the three types of exit in Truffle. There are the f
   * Explicit exit triggered by throwing a Truffle exception of the exception type `ExceptionType.EXIT`.
   * The exception is not automatically thrown in other threads by Truffle and it does not trigger exit notifications or context close on its own.
   * The context is still fully usable after a soft exit and the soft exit can be followed by either the natural or the hard exit.
-  
+
 For completeness, a polyglot context can be also closed by cancelling it using `Context.close(true)`, `TruffleContext.closeCancelled(Node,String)`, or `TruffleContext.closeResourceExhausted(Node,String)`.
-The cancel operation leads to immediate stopping of all context threads and closing the context without any exit notifications. 
+The cancel operation leads to immediate stopping of all context threads and closing the context without any exit notifications.
 
 ## Soft exit
 
@@ -44,7 +51,7 @@ The natural exit occurs during a normal context close triggered by `Context.clos
 3. All initialized languages are finalized.
    * `TruffleLanguage.finalizeContext(C)` is called for all initalized languages.
    * Guest code runs normally during finalization.
-   
+
 4. All languages are disposed.
    * `TruffleLanguage.disposeContext(C)` is called for all languages.
 
@@ -66,42 +73,42 @@ a special `ThreadDeath` cancel exception depending on whether the hard exit or t
 2. Exit notifications for all initialized languages are executed - [TruffleLanguage.exitContext(C,ExitMode,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleLanguage.html#exitContext-C-com.oracle.truffle.api.TruffleLanguage.ExitMode-int), where `ExitMode.HARD` is used as the `ExitMode` parameter.
    * Guest code runs normally during exit notifications.
    * If the context is not cancelled during exit notifications (during step 2a) and reaches step 2b, the exit process proceeds with the next step. Otherwise, the exit notifications are interrupted and the context is immediately cancelled.
-  
+
 3. All context threads are forced to stop by throwing a special `ThreadDeath` exit exception from Truffle safepoints.
    * To exit threads reliably, languages need to ensure that `ThreadDeath` is always immediately rethrown and guest language exception handlers and finally blocks are not run.
    * The embedder threads eventually throw a `PolyglotException` to the host with `PolyglotException.isExit() == true` and `PolyglotException.getExitStatus()`
      being equal to the exit code originally specified as the second parameter to the first call to`TruffleContext.closeExited(Node,int)`.
    * Note that from step 3 the exit process is similar to the cancelling process as indicated by the figure, but the cancelling process uses a special `ThreadDeath` cancel exception
-     and the `PolyglotException` thrown to the host has `PolyglotException.isCancelled() == true` instead of `PolyglotException.isExit() == true`. 
+     and the `PolyglotException` thrown to the host has `PolyglotException.isCancelled() == true` instead of `PolyglotException.isExit() == true`.
 
 4. All initialized languages are finalized.
    * `TruffleLanguage.finalizeContext(C)` is called for all initalized languages.
    * Running any guest code in `TruffleLanguage.finalizeContext(C)` will throw the special `ThreadDeath` exit exception from the first Truffle safepoint.
    * Languages should skip any finalization that would require running guest code. A language can find out if it can run guest code in `TruffleLanguage.finalizeContext(C)` by checking if `TruffleLanguage.exitContext(C,ExitMode,int)` was previously called with ExitMode.NATURAL,
    or by checking that `TruffleContext.isClosed()` returns `false`.
 
-   
+
 5. All languages are disposed.
    * `TruffleLanguage.disposeContext(C)` is called for all languages.
-   
+
 6. The context is closed.
 
 ### Behavior if useSystemExit is enabled
 
 1. The exit is triggered by [TruffleContext.closeExited(Node,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleContext.html#closeExited-com.oracle.truffle.api.nodes.Node-int-).
    * Same as with system exit disabled.
-   
+
 2. Exit notifications for all initialized languages are executed - [TruffleLanguage.exitContext(C,ExitMode,int)](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/TruffleLanguage.html#exitContext-C-com.oracle.truffle.api.TruffleLanguage.ExitMode-int), where `ExitMode.HARD` is used as the `ExitMode` parameter.
    * Same as with system exit disabled.
-   
+
 3. `System.exit(int)` is called to terminate the whole host application providing the fastest exit possible.
    * The exit code passed to `System.exit(int)`
-     is the one originally specified as the second parameter to the first call to`TruffleContext.closeExited(Node,int)`. 
+     is the one originally specified as the second parameter to the first call to`TruffleContext.closeExited(Node,int)`.
 
 ## Example Usage
 
 The [SimpleLanguage](https://github.com/graalvm/simplelanguage) demonstrates the usage of the hard context exit. The following aspects are demonstrated.
 
 * [SLExitBuiltin](https://github.com/graalvm/simplelanguage/blob/master/language/src/main/java/com/oracle/truffle/sl/builtins/SLExitBuiltin.java) demonstrates triggering the context exit.
 * [SLRegisterShutdownHookBuiltin](https://github.com/graalvm/simplelanguage/blob/master/language/src/main/java/com/oracle/truffle/sl/builtins/SLRegisterShutdownHookBuiltin.java) demonstrates registration of shutdown hooks that are executed during the exit notification defined in [SLLanguage](https://github.com/graalvm/simplelanguage/blob/master/language/src/main/java/com/oracle/truffle/sl/SLLanguage.java).
-* [SLExitTest](https://github.com/graalvm/simplelanguage/blob/master/language/src/test/java/com/oracle/truffle/sl/test/SLExitTest.java) demonstrates the usage of the builtins defined above.
+* [SLExitTest](https://github.com/graalvm/simplelanguage/blob/master/language/src/test/java/com/oracle/truffle/sl/test/SLExitTest.java) demonstrates the usage of the builtins defined above.