A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

🙋 feature request

https://github.com/parcel-bundler/parcel/blob/d24e09a9797af41a9d2c6c733b1c6cf6671d60c7/packages/core/workers/src/Profiler.js#L2

The inspector module not always available, it depends on build param --without-inspector

🤔 Expected Behavior

Compatible with --without-inspector mode.

😯 Current Behavior

Direct import

💁 Possible Solution

Not pretty

Was provided this repo: https://github.com/y-a-v-a/lighthouse-async

run it async to see the error:

  lighthouse-async Error: no known mark: lh:gather:afterPass:OptimizedImages
  lighthouse-async     at Object.exports.stop (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/marky/lib/marky.cjs.js:76:13)
  lighthouse-async     at Function.timeEnd (/Users/cjamcl/src/tmp/lighthouse-async

This isn't as much a bug as it is a question/suggestion.
Button material setup and ripple code needs updating.

Should the [Getting Started Guide][1] linked as the first link of the README Important Links be a part of automated testing and quality control to ensure that this 'seemingly simple' first introduction to material-components-web will yield the results that are intended?

I ask

Describe the bug
Say we have a route with the trailing slash and strict_slashes=True:
@app.route('/endpoint/', strict_slashes=True)
this way, url_for() will always trim the trailing slash, returning a non-working URL.

Code snippet

from sanic import Sanic
from sanic.response import html

app = Sanic()

# @app.route('/endpoint', strict_slashes=True)
@app.route('/endpo

Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

Description

I'm submitting a feature request (I intend to work on this myself if I can find the time).

While Option<Callback> works as expected (the prop takes a closure and defaults to None), that doesn't really apply to other Option<T> properties, leading to a small amount of boilerplate (which might accumulate quickly).

For example: If I have a property of type `Option<S

The documentation of FromDataSimple doesn't mention that it's only for debugging. This is only mentioned at documentation of FromData.

Based on several closed issued about this and recent message at #beginners, this causes enough confusion that documentation of FromDataSimple should also mention this.

Need a doc cover how to use A11Y universally in Expo

• How to debug A11Y for iOS, Android, Web
• Best practices
• Using System font sizes
• Dark mode
• Localization