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

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

There are many inactive PRs that have already been revised and with their APIs according to our addition criteria. These PRs are just waiting for some correction that was requested by one of the maintainers, and as they are inactive PRs, they will likely not be done.

Inactive PRs must be closed and their APIs added if they still meet our criteria.

Maintainers can add the APIs of these PRs in

Lite-xl doesn't remember how i left the zoom level,
I mean when i use it i zoom it a little bit for readability and when i quit and reopen it, that time it doesn't remember how i left it off that is the zoom level.

We need to correctly display that there was an issue when a redemption fails for some reason.

Description

I have a hardware abstraction layer interface, as well as a driver interface. I have multiple drivers utilizing the HAL interface, while implementing the driver interface. This plugin approach causes me to have identically named tests across multiple test files.

For example:

TEST_CASE("init() returns `E_HAL_INIT`, when HardwareAbstractionLayer::init() returns an er

GTest exports the following targets:

• GTest::gtest
• GTest::gtest_main
• GTest::gmock
• GTest::gmock_main

This targets should also be available when adding gtest with add_subdirectory (or FetchContent), because this should behave the same way as adding GTest with find_package. So somewhere, we should add the aliases to these targets, i.e.

add_library(GTest::gtest ALIAS