In the solution for the pastebin/bitly system design, the write to cache flow is missing in the second diagram which refers to the scaling aspect. The cache has only a read arrow but not a write arrow. The diagram will be more intuitive if a write-through/write-back cache mechanism was indicated.

🙋 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

Provide the steps to reproduce

1. Run LH on https://qwww.americanexpress.com

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
The default port for a Sanic app is 8000, which by HTTP standards is a custom port. This port can also be set during calls to app.run().

When using app.url_for('handler.name', _external=True), the resultant URL does not contain the port without manual intervention.

This line is the final step before the application returns the URL. The URL is build using `urlunp

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.

Glide is used in UIManagerModuleWrapper#loadImageForManipulationFromURL which is used by expo-image-manipulator. The dependency could probably be moved somewhere else to avoid having to include it in all apps using unimodules.

Discussed this on slack with @sjchmiela