We badly started implementing some props mutation.
There are usually two cases:

1. The props are injected via root component propsData
2. The props are used inside a vue app

Solution 1

Migrate the propsData (usually initial-states) to the root .vue file away from the .js entry point

Solution 2

Use a sync modifier and change the data flow according to vue documentations

Right now any StyleSheet has a list of functions without a default implementation. Implementing a StyleSheet is really annoying, because you have to override all of the functions and not just the thing you want to change.

I recently wanted to just change the border_radius of a text_input and I had to write the following code.

impl StyleSheet for Styles {
    fn active(&self) ->

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

TBH these white splashes are quite painful.

This usercss helps:

.tox .tox-dialog-wrap__backdrop {
background-color: #303030 !important;
}

Though I think that should work out of the box. Could you fix that?

Thanks

<img width="1533" alt="Screenshot 2021-08-14 at 16 01 35" src="https://user-images.githubusercontent.com/295225/129450537-77840706-6909-446a-8aaa-d8c0cee81b1

go-ethereum is the official Go implementation of the Ethereum protocol. In affected versions a consensus-vulnerability in go-ethereum (Geth) could cause a chain split, where vulnerable versions refuse to accept the canonical chain. Further details about the vulnerability will be disclosed at a later date. A patch is included in the upcoming v1.10.8 release. No workaround are available.

h

⚠️ Should be done once meilisearch/milli#330 (comment) is merged and released

We need to use reset_sortable_fields instead of the current set_sortable_fields.

There is no impact on the usage, only on the code base consistency 🙂

The new GrpcDataRuntime (https://github.com/jina-ai/jina/blob/master/jina/peapods/runtimes/grpc/__init__.py) does not support sharding at the moment. Thus a Flow should not specify this runtime and a sharded pod at the same time.

Right now this will not raise any error, but silently produce unexpected behavior. This is undesirable and the Flow should rather check this condition and raise an app