I think it would help users to have some clear information directly accessible about:

• What version of WebAssembly is currently supported and if there is any feature that is not supported (right now it is quite straightforward but better having it displayed clearly)
• Which of the WebAssembly proposals are supported (from https://github.com/WebAssembly/proposals)
• Which WASI snapshop is sup

MDN docs: clientWidth, clientHeight

These properties are useful for getting the actual width and height of an element as it is displayed on the webpage, and it is the [recommended way](https://webglfundamentals.org/webgl/lessons/webgl-anti-patt

breadcrumbs.ts:155 Error importing index.js: TypeError: Cannot set property 'style' of undefined
at resize (index.js?ee1c:114)
at eval (index.js?ee1c:117)
at Module../js/index.js (1.e22692a2f01f3cf7e8df.js:343)
at webpack_require (main.92fa4d75296f0cce142e.js:84)

![image](https://user-images.githubusercontent.com/18341555/75841081-d0422800-5e07-11ea-9603-f4f98a1db782.p

• There seems to be a bug when navigating to the catch_all route but not contributors, ex. localhost:7878/test. The current implementation panics using both rocket and actix as server.
• Rocket currently has 404 for unknown routes and this should be added to the actix example as well.

I'm having trouble groking how to get data out of the fetch::Request::fetch() method.

Sorry this is more of a support request than an issue.

emscripten-core/emscripten#10148 is a report from a cargo-web user whose Emscripten installation is managed by cargo-web but is invalid. I took a look at the cargo-web source, and noticed a few issues:

1. The help messages with instructions for installing Emscripten should probably recommend using emsdk regardless of the platform, since that's the only distribution met

Add a short "Guide"/"How to play" section describing UI, basic game mechanics, agent types, effects, and abilities.

Use images and GIFs.

Check WarbitsManual.pdf as an example of a good guide.

Related to #420 ("Clarify how movement limits work")

Add a bootnode config validation. account_id cannot be Some("34.89.175.66 :24567") and address must be defined.

[2019-11-06T11:06:42Z WARN near_network::peer_manager] Trying to connect to peer with no public address: PeerInfo { id: ed25519:FF7ttcBjsyNtXh6fBw5q85o2HYgtPxnC36Xhvt3HYb8X, addr: None, account_id: Some("34.89.175.66 :24567") }

error: proc-macro derive panicked
  --> src/lib.rs:14:10
   |
14 | #[derive(GraphQLQuery)]
   |          ^^^^^^^^^^^^
   |
   = help: message: Extracting query path.
           The graphql attribute is missing

error: proc-macro derive panicked
  --> src/lib.rs:14:10
   |
14 | #[derive(GraphQLQuery)]
   |          ^^^^^^^^^^^^
   |
   = help: message: Extracting schem

It took me a bit to figure this out and I think the documentation doesn't really cover it and I had to piece things together from the code so I want to leave a snippet here that may help others.

This is a pretty nifty test which illustrates compiling identical modules from wat with wat2wasm in the wabt crate and the parity-wasm module builder api.

#[cfg(test)]
mod tests {
  

The contract! macro is part of the API provided to the contract developer. It should therefore be documented. Currently, there is no easy way to know that there is a env parameter to this macro that allows specifying an own EnvTypes impl.

@torch2424 ran into an issue with source being a relative path that started with ../.. and was outside the manifest directory. The error message they got was vague enough that there's no chance someone not familiar with the code would be able to spot the error.

Right now, going to sandbox.edit.io (or a locally running edit-text instance) will open up the document that corresponds to the requester's IP address, e.g. /welcome-127-0-0-1. This code lives in edit-server.rs:

https://github.com/tcr/edit-text/blob/8bcb38a7f0ac1002b04c9b1b74495927ede2b2ae/edit-server/src/bin/edit-server.rs#L251-L301

We want to add another check just before this which

Using the middleware functionality available in the host, we should provide a crate that contains an OpenTracing middleware implementation. This should perform, at a minimum, the following:

• Initiate a new span when appropriate:
  • When a capability invokes an actor without an existing span
  • When the host performs a manual invocation on an actor (which will not have an existing span)

Currently user needs to kill the process to terminate nes-rust in standalone mode. We should add a proper way to stop.