If a metric is removed from a datasource the single metric widget is inoperable if saved slice or URL references the previously defined metric. Note this isn't a problem for visualization types which support multiple metrics.

Expected results

The metric widget to render correctly.

Actual results

The metric widget in inoperable (see attached screenshot).

Screenshots

<

Is your feature request related to a problem? Please describe.
Problem: I'd like to dynamically import scripts as <script> tags.

Describe the solution you'd like
Proposal:

const useScript = ({ url, id, type = 'text/javascript', async = true }) => {
    const [ready, setReady] = React.useState(false);
    const [failed, setFailed] = React.useState(false);

    R

To improve the quality of our end-to-end testing code, we want to create lint checks for common bad practices. If you would like to help with this issue, please leave a comment on this issue with the task you want to work on.

How to Write E2E Lint Checks

1. First think about how you can identify the bad practice based solely on the text of the code. Imagine you get a code file as a string

To allow a higher api request volume, we should use Binance's websocket APIs instead of the current implementation.

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.

The tutorial for using Messaging https://firebase.flutter.dev/docs/messaging/overview lacks an important part, it does not talk about the required extra service worker for Web (see my SO question about the matter)

Importing the following scripts in index.html:

Willingness to contribute

The MLflow Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature (either as an MLflow Plugin or an enhancement to the MLflow code base)?

• Yes. I can contribute this feature independently.
• Yes. I would be willing to contribute this feature with guidance

What problem does this solve or what need does it fill?

Selecting particular camera types is frustrating, relying on checking the name field within a system.

What solution would you like?

Add a simple marker components for UiCamera and GameplayCamera.

What alternative(s) have you considered?

Users can add their own marker components manually.

Only tag UiCamera and