OnVisible not OnSelect 2522723

Step 17 says "Select the OnSelect" property. Should be OnVisible. Look as the screenshot "ble" shows.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 006ea3e1-916f-fd30-90f1-7787c1459c37
Version Independent ID: e09165f1-60a8-c746-a0de-3a9d0c6ea0bb
Content: Add hierarchy to inspection location - Power Apps
Content Source: powerapps-docs/teams/inspections-hierarchy-locations.md
Service: powerapps
Sub-service: teams
GitHub Login: @sbahl10
Microsoft Alias: namarwah

Thank you for your feedback. Documentation has been fixed and will reflect the changes soon.


Field "Manufacturer" in the input is renamed to "manf" in input, but not in spreadsheet

Specifically: if I have a field called "Manufacturer", it gets renamed to "manf" by the mapping in 'tools.py:97'. However, if I use the option '--fields Manufacturer', both a field called 'manf' and 'Manufacturer' appear in the output spreadsheet, with the 'Manufacturer' column being empty.
The renaming should be done consistently everywhere, or alternatively should be disabled for fields passed as arguments to '--field', under the assumption that the user really wants to keep the name they're using.

Linked with #333

The renaming will need a code refacture of parts of KiCost. I will add an assert not not allow the user to rename this.

If you want to use "Manufacturer" as a user field remove from the internal dictionary using --translate_field Manufacturer, command just used to solve #333, so it can be used as personal field now.


Do something about audit logs

Version channel
Nightly
Loader version
Nightly
What part of Adonis is this related to?
Other
What happened?
There are so many problems with Audit logs.

They just errors and lags in studio.
They don't respect any datastore saving settings
They cause massive datastore spam due to every command that uses audit logs always saving to a datastore.
Code is very error prone
The implementation inappropriately shares code between different Adonis modules
Dublicates functionality of oldlogs
The code doesn't use proper Adonis datastore mechanisms
Numerous other issues

Something should be done, either about the issues or about auditlogs.
Steps to reproduce
N/A
Device
Windows
Relevant log output
No response

Related #1588

Once something is done about audit logs I can release v260. You're welcome to submit a PR to either remove them or fix them and I'll merge either

Once something is done about audit logs I can release v260

Its not. There ae  numerous problems (including breaking bugs) and pulls to be merged to fix them

Fixed by #1698


Self-hosted etcd pod restartPolicy should be OnFailure

Currently it is Always. After a member was removed, if operator failed to remove its pod, then the member could restart again. If it exited 0, we should let it go. We need to cleanup completed pod though.

How will k8s treat a restarted node's pods that are set to OnFailure?

Stopping a node in a short time won't change its pods statuses.

After some research, I don't think kubelet provides good guarantees on node restart. Docker daemon could return exit code=0 for all containers on restart.


Configmap updates not auto-refreshed

Describe the bug
Viewing configmaps with lens I noticed two problems:
While newly created configmaps automatically show up in lens, updates to existing configmaps don't seems to reach lens.
For a test I created the (of course) test configmap with random content:
kubectl --context dev -n default create configmap test --dry-run=client --from-literal=data=$(head -c32 /dev/urandom | base64) -o yaml | kubectl --context dev apply -f -

On the first invocation the new confimap properly shows up in the configmaps view.
Subsequent invocations do work and change the configmap (checked via kubectl) but the new content does not show up in lens until I hit an explicit reload.
De- and re-selecting the configmap doesn't have any effect either.
Editing the configmap will load the proper up to date version of the configmap though - leading to a weirdly inconsistent screenshot as below.
To Reproduce
Steps to reproduce the behavior:

Go to configmaps view
Select an existing configmap
Change the configmap via kubectl or else

Expected behavior
I would expect the updated content to show up in lens.
Screenshots

Environment (please complete the following information):

Lens Version:

OS: macOS 13.2.1
Installation method: An earlier release from https://github.com/MuhammedKalkan/OpenLens/releases - auto updates since then
Kubernetes: This is on an azure kubernetes service cluster:

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Honestly didn't figure out how to run the installed app with console logs 🤦♂
Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
your kubeconfig here

Additional context
Add any other context about the problem here.

I think this problem is more general that auto-refreshing when updated.  I have seen with the most recent version that switching namespace filters will show the wrong configmap values if both namespaces have a configmap with the same name.  It simply doesn't seem to refresh values at all.  So it shows the right namespace in the slide-out panel but values from the configmap in the other namespace.
For example we have a "default" namespace and a "nur-int-interventions" namespace in our cluster.  First I had viewed the configmap in nur-int-interventions".  Then I switched to "default" and attempted to view the same configmap in that namespace.  I received this view:

This was proven to be 100% false information by looking at Rancher:

Restarting OpenLens and then going directly to the "default" namespace showed the right info:

There appears to be a (potentially) dangerous bug here in configmap value refresh.

It almost cost us monetarily. I caught the discrepancy at the last minute and luckily didn't save the changes.  This is a dangerous bug just waiting to cause pain.

I have a similar issue where config files don't show up-to-date information. Find myself reloading Lens a lot lately :(
I'm using:
Lens: 2023.5.120950-latest
Extension API: 6.4.15
Electron: 19.1.9
Chrome: 102.0.5005.167
Node: 16.14.2

Similar issue, spent a whole day diagnosing a non-existent problem with a new application.

Same for me here. Took me quite a while to realize that's a refresh problem. I then immediately found this issue here.


Incorrect rendering of annotations

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome Version 95.0.4612.0 (Official Build) canary (64-bit)
Operating system and its version: Windows 10 Home 20H2 19042.1165
PDF.js version: 2.9.147
Is a browser extension: Yes

Steps to reproduce the problem:

Create a pdf with box annotation with formatting s.a. italics, bold, etc

What is the expected behavior? (add screenshot)
1.Date and time should be set
2.Formatting should be respected (e.g., bold, italics, subscript, superscript)
mouse-over:

clicked:

What went wrong? (add screenshot)
1.Date and time aren't displayed properly
2.Formatting not respected

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Attach (recommended) or Link to PDF file here:

This part of the ISSUE_TEMPLATE is required in order for this (or any) issue to be actionable/valid.

PDF.js version: 2.9.147

That's not an official release; please please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

Date and time should be set

That'd suggest a custom implementation of the viewer, where localization isn't handled correctly (since otherwise that cannot happen).

Formatting not respected

Given that PopupAnnotations are handled separately from the general page rendering (in the PDF.js viewer), there may be some smaller formatting discrepancies between e.g. Adobe Reader and the PDF.js demo viewer.

In version 2.3.164 (Official Chrome release) the result is the same.
(Chrome Version 94.0.4606.12 (Official Build) dev (64-bit))
From what I can see, pdf.js does NOT respect ANY formatting in annotations (italics, bold, subscript, superscript).

Duplicate of #2966


Metadata may be missing for the manually constructed pages

The following pages have no metadata:

[x] https://main--moleculardevices--hlxsites.hlx.live/applications
[x] https://main--moleculardevices--hlxsites.hlx.live/lab-notes/blog
[x] https://main--moleculardevices--hlxsites.hlx.live/lab-notes
[x] https://main--moleculardevices--hlxsites.hlx.live/products
[x] https://main--moleculardevices--hlxsites.hlx.live/products/accessories-consumables
[x] https://main--moleculardevices--hlxsites.hlx.live/products/assay-kits
[x] https://main--moleculardevices--hlxsites.hlx.live/products/additional-products
[x] https://main--moleculardevices--hlxsites.hlx.live/technology
[x] https://main--moleculardevices--hlxsites.hlx.live/products/culture-media-reagents

All missing metadata has been added


File input: inherit padding to avoid duplicating it for sizes

While backporting it to Boosted, I noticed we duplicate padding for ::file-selector-button but it would benefit from inheriting it from its parent input since we wouldn't have to duplicate it for sizes variant.

Did this at first, but removed this because incorrect inheriting with validation backgrounds: https://deploy-preview-32060--twbs-bootstrap.netlify.app/docs/5.0/forms/validation/#supported-elements

Thanks, didn't spotted that!


fix bug when hyps result is empty

@pkufool

@manbaaaa  Thanks!  I did not notice this PR, sorry!


DOC: Make it clear that stitch only supports python 3.5+

Oh, but just like IPython 6.x+ you can still run python2 kernels.

Closed by https://github.com/pystitch/stitch/commit/d9114cd5c5dbd0b4ec0bcb9f0a0b559908ff0538


fix: MD035/hr-style

Horizontal rule style

@nschonni : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@chbain : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@nschonni Thanks for your contribution. We are moving this PR to the private repo for staging and verification.

@chbain no problem, feel free to close when it's moved

Move commits to public repo: https://github.com/MicrosoftDocs/azure-docs-pr/pull/79845


Comment Highlight always starts from now?

When viewing the comments on a post, it says "Highlighting new comments since [...]".  This always seems to show today at the current time even if you have not visited the page before.  Shouldn't this be based on when you actually last looked at the page?

Covered by #231


Pocket Editions Skins

Mojang is adding customs skins to Minecraft: Pocket Edition, and should be providing API support for them. We should probably add support for these at some point down the road. We'll need to figure out if these skins differ from Minecraft's skins, and the possibility that there is a different endpoint for them.
Here

Does the pocket edition use different accounts?
If not, I'd think they just use your account's skin.

I'm not really sure about that, as I don't have that version. Waiting to see if I can find out more about how accounts are connected.

Not sure about this right now...will look into whether or not it's actually relevant at some point when we have more info on the pocket edition skins.


[XLA][WIP] Add support for Polyhedral compilation through Polly

Added Bazel build files for compiling Polly with LLVM to enable Polyhedral compilation, as discussed in #8100

Can one of the admins verify this patch?

cc @BrianRetford @meinersbur @tobig

@googlebot I signed it!

cc @hawkinsp
Could you please look into this?

Seems that there is also a recent effort to mainline Polly in LLVM /cc @hfinkel

@annanay25 any chance to pull rebase and address comments? Thank you.

@drpngx, yes, will do it shortly.

@annanay25 any update?

@sanjoy did the new commits resolve your comments?

@annanay25 @arpith-jacob could you resolve the conflicts?

@annanay25 any luck with addressing the comments? Could you pull rebase and push again?

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jpienaar: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jpienaar: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Can @tensorflowbutler count real days? This second one was probably 28 days so it doesn't make sense to count bot only posts.

Good point. @av8ramit how hard would it be to ignore bot posts for the purposes of counting days only (the 2 weeks interval in nagging is still good).

Sure I'll add this to our upcoming feature set. Thanks @bhack


Destructuring assignment for object

Currently there is no way to destruct object on assignment.
my (:$key, :$value) = a => 1; # not what you think
# $key is :a(1)
# $value is (Any)

This is weird, since destructing array works both in block signature and in assignment.

But how is ths not binding?
my ($a, $b) = 1, 2

But how is ths usable?
my ($a, $b) = 1, 2

That's list assignment. I suggest looking up some docs on assignment vs binding; Raku offers both, and they are quite different in nature.

The official docs (docs.raku.org) only has example for single-value binding (my $a = $b). Now I understand it better.


"Playback Resumed" Erroneous Message

Seems to be an issue with /leave not triggering status change events, since the "Left voice channel due to inactivity" message still occurs in the image above.

Fixed in V3


Error after edit process.env in code

[ x] Asked question in discussions
[ v] Tried the troubleshooting Wiki
[ v] Followed the migration Wiki
[ v] Installed library as devDependency not production dependency

code in index.jsx:
process.env.ABC = 123;

error:
Property left of AssignmentExpression expected node to be of a type ["LVal","OptionalMemberExpression"] but instead got "StringLiteral"

warning: the transform cache was reset.
debug Checking for a newer version of React Native
debug Current version: 0.74.1
debug Cached release version: 0.74.1
debug Checking for newer releases on GitHub
                Welcome to Metro v0.80.9
              Fast - Scalable - Integrated

adebug Latest release: 0.74.1 (undefined)

...

> Task :app:installDebug
Installing APK 'app-debug.apk' on 'Pixel_7_Pro_API_34(AVD) - 14' for :app:debug
Installed on 1 device.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 7s
242 actionable tasks: 31 executed, 211 up-to-date
info Connecting to the development server...
info Starting the app on "emulator-5554"...
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.jjassistant/.MainActivity }
 BUNDLE  ./index.js

error: App/index.jsx: .../App/index.jsx: Property left of AssignmentExpression expected node to be of a type ["LVal","OptionalMemberExpression"] but instead got "StringLiteral"

Desktop (please complete the following information):

MacOS 14.3.1

Smartphone (please complete the following information):

Simulator: Pixel_7_Pro_API_34(AVD) - 14

not working react-native 0.74.1

any solution?

not working react-native 0.74.1 Install react-native-dotenv, and I have react-native 0.74.1, follow all the steps, restart the computer. I applied cache reset and nothing. any solution?
any solution?


[BUG] test

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Samsung Galaxy S22]
OS: [e.g. OneUI]
Version [e.g. v3.4.0]

Additional info
Add any other context about the problem here.

@no-response


color_threshold gives incorrect coloring when fill_raw is 'null' (or unspecified) and data is missing,

Checklist

[x] I updated the card to the latest version available
[x] I cleared the cache of my browser
[x] I verified that I'm really running the latest version in my browser console
[x] I checked if there is another issue opened with the same problem. possible dupe of #202 and #305

Describe the bug
If there is a gap in the data and fill_raw is missing or set to null color_threshold paints incorrect colors.
Version of the card
Version: 2.0.1
To Reproduce
This is the configuration I used:
  - type: custom:apexcharts-card
    graph_span: 24h
    update_interval: 1min
    apex_config:
      chart:
        height: 200px
      grid:
        show: false
      xaxis:
        axisBorder:
          show: false
        axisTicks:
          show: false
        spanGaps: false
    experimental:
      color_threshold: true
    header:
      show: true
      show_states: true
      colorize_states: true
    series:
      - entity: sensor.yuba_crest_temp
        color: grey
        opacity: 1
        stroke_width: 3
        name: Outside
        type: line
        show:
          legend_value: false
          in_chart: true
          header_color_threshold: true
          extremas: true
        yaxis_id: Temperature
        color_threshold:
          - value: 0
            color: rgb(224,123,222)
          - value: 20
            color: rgb(187, 116, 212)
          - value: 30
            color: rgb(116, 92, 219)
          - value: 40
            color: rgb(23, 210, 227)
          - value: 50
            color: rgb(0,215,144)
          - value: 60
            color: rgb(94,210,48)
          - value: 70
            color: rgb(255,255,101)
          - value: 80
            color: rgb(250,130,46)
          - value: 90
            color: rgb(180,35,17)
          - value: 100
            color: rgb(175,0,0)
    yaxis:
      - id: Temperature
        show: true
        align_to: 5
        decimals: 0

Screenshots
Screenshot with no fill_raw or fill_raw: 'null'

Screenshot with fill_raw: 'last'

Expected behavior
Expected chart to colorize correctly and leave. gap where data was null
Desktop (please complete the following information):

Browser Chrome
Version  105.0.5195.125

Smartphone (please complete the following information):
N/A - not tested
Additional context
Add any other context about the problem here.
Console errors:

I know it may be a duplicate of #202 and #305 hoping the console log data may shed more light on what's going wrong.

I also had the problem of incorrect coloring with fill_raw: last, but with missing data. I found a workaround by averaging the data for any time period. for example:
group_by:       func: avg       duration: 10m
You can change the duration to any amount of time. Can also be the same as the update interval of the sensor.


Cattle: 502 Bad Gateway on conversion.

Tried converting a csv file with Cattle, received a 502 Bad Gateway, reduced the file-size by taking out rows and converted without issue.
File that timed-out was 200kb with 3222 rows and 9 columns.
File that worked was 44kb with 749 rows and 9 columns.

This is being addressed now by the improved error reporting and the druid connection, so I'm closing the issue


Does Proof Assistant verify $d now?

Under "prove" we have:

Note:  In the present version of
Metamath\index{Metamath!limitations of version 0.07.30}, the Proof
Assistant does not verify that \texttt{$d}\index{\texttt{$d}
statement} restrictions are met as a proof is being built.  After you
have completed a proof, you should type \texttt{save new{\char`_}proof}
followed by \texttt{verify proof} {\em label} (where {\em label} is the
statement you are proving with the \texttt{prove} command) to verify the
\texttt{$d} restrictions.

@nmegill - Is this still true? I think it is, but if it's obsolete we should remove it.

Unfortunately $d's are still not handled in MM-PA.  This is an item on my to-do list but is a somewhat big project.  So the book's comment stands.

Ok! Closing out


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

4c049a1a1: - Adds onClick and other props to IconLinkVertical;

Allows TriggerButton component to render when pager duty key is missing;

Refactors TriggerButton and PagerDutyCard not to have shared state;

Removes the action prop of the IconLinkVertical component while adding onClick.
Instead of having an action including a button with onClick, now the whole component can be clickable making it easier to implement and having a better UX.
Before:
const myLink: IconLinkVerticalProps = {
  label: 'Click me',
  action: <Button onClick={myAction} />,
  icon: <MyIcon onClick={myAction} />,
};

After:
const myLink: IconLinkVerticalProps = {
  label: 'Click me',
  onClick: myAction,
  icon: <MyIcon />,
};

Patch Changes

40c0fdbaa: Added support for optional external route references. By setting optional: true when creating an ExternalRouteRef it is no longer a requirement to bind the route in the app. If the app isn't bound useRouteRef will return undefined.
2a271d89e: Internal refactor of how component data is access to avoid polluting components and make it possible to bridge across versions.
bece09057: Improve rendering of multiple support item links in the SupportButton
169f48deb: Added the color prop to TrendLine from the Sparklines props types to be able to have custom colors.
8a1566719: Added a new useSupportConfig hook that reads a new app.support config key. Also updated the SupportButton and ErrorPage components to use the new config.
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Minor Changes

8106c9528: The scaffolder has been updated to support the new v1beta2 template schema which allows for custom template actions!
See documentation for more information how to create and register new template actions.
Breaking changes
The backend scaffolder plugin now needs a UrlReader which can be pulled from the PluginEnvironment.
The following change is required in backend/src/plugins/scaffolder.ts
 export default async function createPlugin({
   logger,
   config,
   database,
+  reader,
 }: PluginEnvironment): Promise<Router> {

  // omitted code

  return await createRouter({
    preparers,
    templaters,
    publishers,
    logger,
    config,
    dockerClient,
    database,
    catalogClient,
+   reader,
  });

Patch Changes

12d8f27a6: Move logic for constructing the template form to the backend, using a new ./parameter-schema endpoint that returns the form schema for a given template.
bc327dc42: Tweak the template cards to be even more compliant with MUI examples, and a little bit more dense.
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Minor Changes

8106c9528: The scaffolder has been updated to support the new v1beta2 template schema which allows for custom template actions!
See documentation for more information how to create and register new template actions.
Breaking changes
The backend scaffolder plugin now needs a UrlReader which can be pulled from the PluginEnvironment.
The following change is required in backend/src/plugins/scaffolder.ts
 export default async function createPlugin({
   logger,
   config,
   database,
+  reader,
 }: PluginEnvironment): Promise<Router> {

  // omitted code

  return await createRouter({
    preparers,
    templaters,
    publishers,
    logger,
    config,
    dockerClient,
    database,
    catalogClient,
+   reader,
  });

96ccc8f69: Removed support for deprecated publisher auth configuration within the scaffolder configuration block, such as scaffolder.github.token. Access should instead be configured through integrations configuration.
For example, replace the following configuration in app-config.yaml
scaffolder:
  github:
    token: my-token

with
integrations:
  github:
    - host: github.com
      token: my-token

Patch Changes

12d8f27a6: Move logic for constructing the template form to the backend, using a new ./parameter-schema endpoint that returns the form schema for a given template.
12d8f27a6: Add version backstage.io/v1beta2 schema for Template entities.
f31b76b44: Consider both authentication methods for both onprem and cloud BitBucket
f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
d0ed25196: Fixed file path resolution for templates with a file location
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Minor Changes

813c6a4f2: Add authorization header on techdocs api requests. Breaking change as clients now needs the Identity API.

Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [f43192207]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]
Updated dependencies [61299519f]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

497859088: Add optional logClientErrors to errorHandler to log 4XX errors
8adb48df4: Change debug log format to print as color grey

<EMAIL_ADDRESS>Patch Changes

12d8f27a6: Add version backstage.io/v1beta2 schema for Template entities.

<EMAIL_ADDRESS>Patch Changes

507513fed: Bump @svgr/webpack from 5.4.x to 5.5.x.
e37d2de99: Bump @testing-library/react in the plugin template from ^10.4.1 to ^11.2.5. To apply this to an existing plugin, update the dependency in your package.json.
11c6208fe: Fixed an issue where the backend:dev command would get stuck executing the backend process multiple times, causing port conflict issues.
d4f0a1406: New config command to export the configuration schema. When running backstage-cli with yarn, consider using yarn --silent backstage-cli config:schema to get a clean output on stdout.

<EMAIL_ADDRESS>Patch Changes

40c0fdbaa: Added support for optional external route references. By setting optional: true when creating an ExternalRouteRef it is no longer a requirement to bind the route in the app. If the app isn't bound useRouteRef will return undefined.
2a271d89e: Internal refactor of how component data is access to avoid polluting components and make it possible to bridge across versions.

<EMAIL_ADDRESS>Patch Changes

f71589800: The api-docs plugin has been migrated to use an external route reference to dynamically link to the create component page.
If you want to have a button that links to the scaffolder plugin from the API explorer, apply the following changes to packages/app/src/App.tsx:
+ import { apiDocsPlugin } from '@backstage/plugin-api-docs';
  import { scaffolderPlugin } from '@backstage/plugin-scaffolder';

  const app = createApp({
    // ...
    bindRoutes({ bind }) {
+     bind(apiDocsPlugin.externalRoutes, {
+       createComponent: scaffolderPlugin.routes.root,
+     });
    },
  });

If you choose to not bind the routes, the button to create new APIs is not displayed.

7a1b2ba0e: Migrated away from using deprecated routes and router components at top-level in the app, and instead use routable extension pages.
To apply this change to an existing app, make the following changes to packages/app/src/App.tsx:
Update imports and remove the usage of the deprecated app.getRoutes().
-import { Router as DocsRouter } from '@backstage/plugin-techdocs';
+import { TechdocsPage } from '@backstage/plugin-techdocs';
 import { CatalogImportPage } from '@backstage/plugin-catalog-import';
-import { Router as TechRadarRouter } from '@backstage/plugin-tech-radar';
-import { SearchPage as SearchRouter } from '@backstage/plugin-search';
-import { Router as SettingsRouter } from '@backstage/plugin-user-settings';
+import { TechRadarPage } from '@backstage/plugin-tech-radar';
+import { SearchPage } from '@backstage/plugin-search';
+import { UserSettingsPage } from '@backstage/plugin-user-settings';
+import { ApiExplorerPage } from '@backstage/plugin-api-docs';
 import { EntityPage } from './components/catalog/EntityPage';
 import { scaffolderPlugin, ScaffolderPage } from '@backstage/plugin-scaffolder';

const AppProvider = app.getProvider();
const AppRouter = app.getRouter();
-const deprecatedAppRoutes = app.getRoutes();

As well as update or add the following routes:

```diff
   <Route path="/create" element={<ScaffolderPage />} />
-  <Route path="/docs" element={<DocsRouter />} />
+  <Route path="/docs" element={<TechdocsPage />} />
+  <Route path="/api-docs" element={<ApiExplorerPage />} />
   <Route
     path="/tech-radar"
-    element={<TechRadarRouter width={1500} height={800} />}
+    element={<TechRadarPage width={1500} height={800} />}
   />
   <Route path="/catalog-import" element={<CatalogImportPage />} />
-  <Route
-    path="/search"
-    element={<SearchRouter/>}
-  />
-  <Route path="/settings" element={<SettingsRouter />} />
-  {deprecatedAppRoutes}
+  <Route path="/search" element={<SearchPage />} />
+  <Route path="/settings" element={<UserSettingsPage />} />

If you have added additional plugins with registered routes or are using Router components from other plugins, these should be migrated to use the *Page components as well. See this commit for more examples of how to migrate.
For more information and the background to this change, see the composability system migration docs.

Updated dependencies [b2a5320a4]
Updated dependencies [12d8f27a6]
Updated dependencies [507513fed]
Updated dependencies [52b5bc3e2]
Updated dependencies [ecdd407b1]
Updated dependencies [32a003973]
Updated dependencies [40c0fdbaa]
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [1987c9341]
Updated dependencies [f31b76b44]
Updated dependencies [15eee03bc]
Updated dependencies [f43192207]
Updated dependencies [8adb48df4]
Updated dependencies [bc327dc42]
Updated dependencies [2386de1d3]
Updated dependencies [9ce68b677]
Updated dependencies [10362e9eb]
Updated dependencies [e37d2de99]
Updated dependencies [813c6a4f2]
Updated dependencies [11c6208fe]
Updated dependencies [8106c9528]
Updated dependencies [05183f202]
Updated dependencies [40c0fdbaa]
Updated dependencies [f71589800]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [d4f0a1406]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [d0ed25196]
Updated dependencies [4c049a1a1]
Updated dependencies [96ccc8f69]
Updated dependencies [3af994c81]
Updated dependencies [b33e553b2]
Updated dependencies [04667f571]
Updated dependencies [dbea11072]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
61299519f: Remove read-store-upload loop when uploading S3 objects for TechDocs
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

32a003973: Update messaging when no entities are in a table.

2386de1d3: Add organization name to the API Explorer page title

f71589800: The api-docs plugin has been migrated to use an external route reference to dynamically link to the create component page. This means you need to migrate the api docs plugin to use the new extension components, as well as bind the external route.
To bind the external route from the api docs plugin to the scaffolder template index page, make sure you have the appropriate imports and add the following to the createApp call:
import { apiDocsPlugin } from '@backstage/plugin-api-docs';
import { scaffolderPlugin } from '@backstage/plugin-scaffolder';

const app = createApp({
  // ...
  bindRoutes({ bind }) {
    bind(apiDocsPlugin.externalRoutes, {
      createComponent: scaffolderPlugin.routes.root,
    });
  },
});

If you choose to not bind the routes, the button to create new APIs is not displayed.

Updated dependencies [12d8f27a6]

Updated dependencies [40c0fdbaa]

Updated dependencies [2a271d89e]

Updated dependencies [bece09057]

Updated dependencies [169f48deb]

Updated dependencies [8a1566719]

Updated dependencies [4c049a1a1]

Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
3af994c81: Expose a configuration option for the oidc scope
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

32a003973: Update messaging when no entities are in a table.
40c0fdbaa: Make the external createComponent route optional, hiding the "Create Component" button if it isn't bound.
10362e9eb: Use entity relation for the owner of an entity in the catalog entity page header.
b33e553b2: Removed fullScreen property from UnregisterEntity Dialog modal.
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

ecdd407b1: GithubDiscoveryProcessor outputs locations as optional to avoid outputting errors for missing locations (see https://github.com/backstage/backstage/issues/4730).
12d8f27a6: Add version backstage.io/v1beta2 schema for Template entities.
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

05183f202: Bump react-hook-form version constraint to "^6.15.4"
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

02816ecd7: Fixed EntityProvider setting 'loading' bool erroneously to true
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

b2a5320a4: Use Breadcrumbs from @backstage/core rather than material-ui
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

b2a5320a4: Use Breadcrumbs from @backstage/core rather than material-ui
d21058c34: Change terminology for cloudbuild
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

b2a5320a4: Use Breadcrumbs from @backstage/core rather than material-ui
04667f571: Use Breadcrumbs from @backstage/core
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

0452ba238: - Add Jenkins logo to project page.

Move to new Backstage breadcrumb component.
Change references of deprecated "Job" terminology to "Project" per Jenkins Glossary.

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

ba21797ca: k8s plugin now surfaces k8s components with only label selector query annotation.
Previously backstage.io/kubernetes-label-selector catalog entity annotation would only work if you also included backstage.io/kubernetes-id.
But backstage.io/kubernetes-id value was ignored
42c8ebb79: Support AWS auth provider on kubernetes FE plugin
Updated dependencies [12d8f27a6]
Updated dependencies [f43192207]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
Updated dependencies [12d8f27a6]
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

dbea11072: Change setup wording of intro card to latest
Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

4c049a1a1: - Adds onClick and other props to IconLinkVertical;

Allows TriggerButton component to render when pager duty key is missing;

Refactors TriggerButton and PagerDutyCard not to have shared state;

Removes the action prop of the IconLinkVertical component while adding onClick.
Instead of having an action including a button with onClick, now the whole component can be clickable making it easier to implement and having a better UX.
Before:
const myLink: IconLinkVerticalProps = {
  label: 'Click me',
  action: <Button onClick={myAction} />,
  icon: <MyIcon onClick={myAction} />,
};

After:
const myLink: IconLinkVerticalProps = {
  label: 'Click me',
  onClick: myAction,
  icon: <MyIcon />,
};

Updated dependencies [12d8f27a6]

Updated dependencies [40c0fdbaa]

Updated dependencies [2a271d89e]

Updated dependencies [bece09057]

Updated dependencies [169f48deb]

Updated dependencies [8a1566719]

Updated dependencies [4c049a1a1]

Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

1987c9341: Added a verification for well formed URLs when processing proxy targets. Otherwise users gets a cryptic error message thrown from Express which makes it hard to debug.
9ce68b677: Fix for proxy-backend plugin when global-agent is enabled
Updated dependencies [497859088]
Updated dependencies [8adb48df4]

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [12d8f27a6]
Updated dependencies [40c0fdbaa]
Updated dependencies [2a271d89e]
Updated dependencies [bece09057]
Updated dependencies [169f48deb]
Updated dependencies [8a1566719]
Updated dependencies [4c049a1a1]
Updated dependencies [02816ecd7]

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

410550388: Collect all available metric types if the number exceeds the default page size of 100.
a4c575802: Display '-' instead of 'undefined' if no code coverage is reported.

Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf

Tugboat has finished building the preview for this pull request!
Link:

https://pr4659-kvj3lkfnw0ngirwfdrjrn4hecfod3ioi.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6034fe3cfcb22d35555d44bf


Backend operator repository

Story
Description
Define where the extension's backend code resides. For now we can use rancher-turtles but, is it the long-term choice?
Other extensions are split into two repositories, e.g. Kubewarden:

UI - kubewarden/ui
Backend - kubewarden/kubewarden-controller

After some discussion today we decided to use this repo for all backend and a separate one for the UI, closing this issue as done


unexpected behaviour plots.series_per_group

The plots.series_per_group function gives an unexpected behaviour.
https://github.com/ArtesiaWater/hydropandas/blob/2426022ead74875a5f5abf6830c405d07533e78c/hydropandas/extensions/plots.py#L740C20-L740C52
When only one column provided as by
When groupname is a string, than the filename is spoiled with - symbols, e.g. series_by_monitoring_well_group_P-B-4.png
When groupname is a float or int, the function fails.
My solution is to exclude this line.
When a list is provided as by
You expect something as the join function. Therefore 2 lines up, include: groupname = '-'.join(str(x) for x in groupname)
Maybe I missed something in the function logic. Otherwise, I will fix this issue.

I think it is good to remove the line. I would think that groupname is never a collection and always a string, int or float. Maybe it is a good idea to add a test or an example for this function in one of the notebooks.

groupname can actually be a collection. In the case you're grouping on (x, y) locations it is a tuple of the x and y coordinates of that group.
The issue is that it if it is not a collection but a string the join call will put hyphens between each letter. A simple fix is to check whether groupname is string, and if it is, skip the join call, I think. I'll submit a quick fix.

Ah that makes sense, thanks for the fix


Add integration tests that utilize a local v2 registry instance.

We should be able to test integration to a registry locally, without hammering Docker Hub and alike.

This should be similar to what was done for crashvb/docker-registry-client-async#2


Crashlytics command line upload-symbols finishes successfully but Firebase console still shows missing DSYM

Description
I'm using upload-symbols command line to upload symbols after a successful build, but for some reason the crashes in Firebase are still not symbolicated and says that DSYM is missing. If I upload exactly the same package via Firebase Console UI, the crashes become symbolicated and the warning disappeared. Reproduced consistently with each release.
Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios mycoolapp.dSYMs.zip

In response I'm getting the following output
Successfully submitted symbols for architecture arm64 with UUID xxx in dSYM: /var/folders/xxx.dSYMs.zip.unzipped/xxx.framework.dSYM
Successfully submitted symbols for architecture arm64 with UUID xxx in dSYM: /var/folders/yyy.dSYMs.zip.unzipped/yyy.framework.dSYM
....
Successfully uploaded Crashlytics symbols

The DSYM package is valid because when I upload it via UI, it works.
The plist metadata is valid, freshly downloaded from the Firebase console.
Reproducing the issue
No response
Firebase SDK Version
9.3.0
Xcode Version
14.2
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Crashlytics, Messaging, Remote Config
Targeted Platforms
iOS
Relevant Log Output
> Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios mycoolapp.dSYMs.zip

Successfully submitted symbols for architecture arm64 with UUID xxx in dSYM: /var/folders/xxx.dSYMs.zip.unzipped/xxx.framework.dSYM
Successfully submitted symbols for architecture arm64 with UUID xxx in dSYM: /var/folders/yyy.dSYMs.zip.unzipped/yyy.framework.dSYM
....
Successfully uploaded Crashlytics symbols

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

  - FirebaseCrashlytics (9.3.0):
    - FirebaseCore (~> 9.0)
    - FirebaseInstallations (~> 9.0)
    - GoogleDataTransport (< 10.0.0, >= 9.1.4)
    - GoogleUtilities/Environment (~> 7.7)
    - nanopb (< 2.30910.0, >= 2.30908.0)
    - PromisesObjC (~> 2.1)

  FirebaseCrashlytics: 65a5b349e664e986e6c7486b0a9b5ed8c11d0491

We noticed the same issue with our first upload on Xcode 14.2 🤔

Hi @alexeystrakh, based on your logs, the dSYMs were successfully uploaded but still missing in the console. With this, you may try the troubleshooting steps on our docs and see if it fixes the issue. Otherwise, please file a ticket via our support channel so the team can investigate your project and check your configurations. I'll now be closing this issue.


googleapis/python-storage/issues/324 is fixed

Codecov Report

Merging #127 (c84061a) into main (d1eebc9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #127   +/-   ##
=======================================
  Coverage   87.42%   87.42%
=======================================
  Files           7        7
  Lines         851      851
  Branches      117      112    -5
=======================================
  Hits          744      744
  Misses         80       80
  Partials       27       27

Flag
Coverage Δ

unittests
87.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1eebc9...c84061a. Read the comment docs.


DEV: adds support for chat composer buttons API

A video is a file, so presumably, the user could also upload it via "Attach a file". Is it not going to get the Mux treatment if uploaded that way?

I don't know enough about the plugin to answer this, it was a request from Sam to have support for this so I imagined it was different than simple upload?

@oblakeerickson maybe you can help on this please? (penar's question)

From the plugin README it seems pretty clear upload video is different than regular upload. It uploads on MUX and let you stream it after. Maybe the button title should be clearer? Not sure what though.

I will merge this, but feel free to answer when you are available @oblakeerickson please


Roll Packages from 6698b2d67999 to 701d60a08941 (6 revisions)

https://github.com/flutter/packages/compare/6698b2d67999...701d60a08941
2024-04-16<EMAIL_ADDRESS>[CupertinoIcons] fix broken icons and vertical alignment, bump the version to 1.08 (flutter/packages#6520)
2024-04-16<EMAIL_ADDRESS>[video_player] Calls onDestroy instead of initialize in onDetachedFromEngine (flutter/packages#6501)
2024-04-15<EMAIL_ADDRESS>[image_picker] Adopt code excerpts in README (flutter/packages#5523)
2024-04-15<EMAIL_ADDRESS>[url_launcher][web] Link should work when triggered by keyboard (flutter/packages#6505)
2024-04-15<EMAIL_ADDRESS>Manual roll Flutter from 53cba24de3a0 to 2e748e8598b3 (19 revisions) (flutter/packages#6541)
2024-04-15<EMAIL_ADDRESS>Update local_auth_android minSdkVersion to 19 (flutter/packages#6537)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


expand RV grid & fit Gaussian to CCF

per Didier Queloz comments: we should be getting a cross-correlation function across a wider RV grid with the binary mask method and extracting an RV based on a Gaussian fit to the full thing, rather than interpolating locally at the minimum

Okay this is not a hard change. Can we plan to make this change on Monday?

Added in the infrastructure to do this. Let's discuss tomorrow!


Authorization in an already existing JWT protected API with a secret key

I've been looking for info regarding this but haven't found any so I open this "issue" which is more a "question". I have an API in Symfony 3.4 working with LexikJWTAuthenticationBundle. We use Angular 2+ to work with it and everything is fine. Now we want to create a WordPress plug-in that will communicate with this existing API (not with Angular 2+ but that's not the problem). We don't want to ask for or store (in the WordPress space) the user and password of our users so I would like to use a pre-generated secret string given from our application to the user and then the user should paste that secret in the configuration of our plug-in in WordPress. That secret should be used to generate a JWT token.
Is there a way I can get a valid JWT token from this secret string with an already existing secure approach? Or should I just create an end-point to exchange the secret for a JWT token? I'm not sure how to deal with the secure exchange of the secret and the JWT token. Does anybody know a better approach for this?
Thanks.

The solution to this was to create a custom authenticator class and use multiple guard authenticators in the same path.

Sorry for the lack of feedback though! And thank you for sharing your solution


Feat/entrega 1

Codecov Report

Merging #2 (02af70a) into master (59c212a) will increase coverage by 9.77%.
The diff coverage is 89.47%.

@@             Coverage Diff              @@
##             master       #2      +/-   ##
============================================
+ Coverage     83.87%   93.65%   +9.77%
- Complexity       21       28       +7
============================================
  Files             8        9       +1
  Lines            62       63       +1
  Branches          6        3       -3
============================================
+ Hits             52       59       +7
+ Misses            8        3       -5
+ Partials          2        1       -1

Impacted Files
Coverage Δ

src/main/java/edu/fiuba/algo3/modelo/Auto.java
66.66% <33.33%> (+4.16%)
:arrow_up:

src/main/java/edu/fiuba/algo3/modelo/Piquete.java
75.00% <60.00%> (+17.85%)
:arrow_up:

src/main/java/edu/fiuba/algo3/modelo/Auto4x4.java
100.00% <100.00%> (ø)

src/main/java/edu/fiuba/algo3/modelo/Grilla.java
100.00% <100.00%> (ø)

...va/edu/fiuba/algo3/modelo/HayPiqueteException.java
100.00% <100.00%> (ø)

src/main/java/edu/fiuba/algo3/modelo/Moto.java
100.00% <100.00%> (ø)

...rc/main/java/edu/fiuba/algo3/modelo/Obstaculo.java
100.00% <100.00%> (ø)

src/main/java/edu/fiuba/algo3/modelo/Pozo.java
100.00% <100.00%> (+42.85%)
:arrow_up:

src/main/java/edu/fiuba/algo3/modelo/Vehiculo.java
100.00% <100.00%> (+11.11%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


(Discussion) Bridge representation

Motivation
To make creating new levels easier, we should think about how to make it modular, e.g. we should be able to just drag-and-drop all required parts, without thinking about scripts, groups, or anything functional. In essence, someone not knowing the code should be able to build a level.
Considerations

water functionality should become its own scene
same for goal menu-related things, we should only have one node for it
hazards should be a general object and be able to adjust via a variable in the inspector
only one grid sprite
spawn buttons will be completely reworked into an inventory, which should require just one node
shore dropzones should be generic as well, customized via a variable in the inspector

Was discussed and decided.


Change YPR guidance

Currently, we advise users to use camera yaw, pitch, roll pose (YPR) values of
[0, 0, 0]       #[yaw, pitch, roll]
if the parameters are unknown. This can either be set in the camera environment txt file, or as a variable in a driver script. However, this causes problems in the optimisation routine - if the yaw parameter is 0 then the optimisation routine may not be able to resolve the camera environment from the ground control points. It should be advised to use an estimate of the yaw parameter in order to give the optimisation routine a starting point e.g.
[90, 0, 0]      #i.e. camera pointing east

This has now been changed in the example camera environment files to suggest that the yaw should be guessed if YPR is unknown:
Yaw_pitch_roll #Yaw, pitch, roll of camera (estimate yaw viewing angle if YPR is unknown e.g. [180 0 0])


Add load balancer description for keepalived and ephemeral cluster

@Jaakko-Os
@mikkosest

for keepalived yes as soon as I have a bit of time to test it, for the second one, it depends on the configmap reloading in the LB and CAPBM needs to be heavily modified.


ssl_verify_client_exception: fixed segfault of referring null pointer

import bugfix of nginx core phase from this nginx commit:
commit 57dde2ab37708423d97333be19830437732b3f4f
Author: Sergey Kandaurov<EMAIL_ADDRESS>Date:   Tue Jan 30 17:46:31 2018 +0300

    SSL: using default server context in session remove (closes #1464).

    This fixes segfault in configurations with multiple virtual servers sharing
    the same port, where a non-default virtual server block misses certificate.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.笑臣 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.笑臣 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Miden Assembly Linter?

Feature description
I was wondering if there is a linter/code formatter for miden assembly files. There is probably some standard code formatter for assembly that could be adapted to miden assembly.
Why is this feature needed?
Improves readability and standardization of Miden Assembly files.

There is a rustfmt like API available in miden-core, via the PrettyPrint trait. This is implemented for both MASM and MAST textual formats. A formatter tool simply needs to parse a module, then write it back to disk like write!(&mut file, "{module}")?;
We don't have a linter though, that would be nice!


trace output for CMD

CMD does not output any trace (unlike e.g. CP, which is using -v unless -q is specified).
$ cat base/Bastillefile
CMD /bin/ln -sf /usr/share/zoneinfo/Europe/Prague /etc/localtime

CP etc /
CP root /

$ rocinante template base # notice [CMD] trace is completely missing, only exit code 0 gets printed
[TEMPLATE]:
Applying template: base...

0

[CP]:
base/etc -> /etc
base/etc/ttys -> /etc/ttys

[CP]:
base/root -> /root
base/root/.hushlogin -> /root/.hushlogin

the [CMD] should be shown
ideally sh -x would print the command being executed, unless -q

Thank you for contributing this feature. Changes are available in the 0.1.20220714 release.


[Feature] DATA-4844: Sink both Key and Value 4.0.0

[JIRA] What Jira tickets does this PR Address?
https://jira.wishabi.com/browse/DATA-4844
[SUMMARY] What's this PR do?

[x] - Customized S3 connector to enable sinking both key and value
[x] - Add a config s3.sink.key to control if you want to sink the key or not
[x] - Add test cases for primitive types and nested types
[x] - Currently, it supports the following types

Schema.Type.INT8,
Schema.Type.INT16,
Schema.Type.INT32,
Schema.Type.INT64,
Schema.Type.FLOAT32,
Schema.Type.FLOAT64,
Schema.Type.BOOLEAN,
Schema.Type.STRING,
Schema.Type.STRUCT

[TEST CASES] How should this be tested?

[x] - Run mvn test to make sure all test cases pass

[USAGE] How should this be used?

Run mvn install to generate the jar on local

Replace /usr/share/java/kafka-connect-s3/kafka-connect-s3-4.0.0.jar with /usr/share/java/kafka-connect-s3/kafka-connect-s3-flipp-4.0.0.jar

In s3 connector config file, add the following lines to sink both key and value:

connector.class=io.confluent.connect.s3.S3SinkKeyValueConnector
s3.sink.key=true

@johnnycaol
Is this basically just a simple port of your code from 3.3 to 4.0 ?

@bellemare That's correct.

If it's just a port, it builds and passes all the tests, then I say ship it!

Note: You could also achieve this with a transform.
https://github.com/jcustenborder/kafka-connect-transform-archive


Wonky Sound

added sounds
moved javascript into a dedicated folder
added sound.js for sounds
html: added test link, button and input to see the effect
should have sound when clicking link/button and pressing keys
random and somehow chaotic
again sry if I did anything wrong, and thanks for the opportunity ^-^

From the next time:
mention the issue you have worked on by writing
Closes: #10
or if its a fix for already closed issue then write Fixes: #issueNumber
This helps the PA look into your issue and verify if you did the assigned task correctly or not and also autocloses the issue making it simpler for the PA
Keep up the chaos 😵💫
Happy Coding 🚀
Show you love and ⭐ the repository!


Release nbconvert constraint

Summary
Releases constraint in the nbconvert version due to https://github.com/jupyter/nbconvert/issues/2092, which nbconvert v7.16.4 may have fixed.
Details and comments
Closes https://github.com/qiskit-community/qiskit-machine-learning/issues/735
Closes https://github.com/OkuyanBoga/hc-qiskit-machine-learning/issues/51

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.681%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
4640

Relevant Lines:
5061

💛  - Coveralls

Before merging, I just wanted to check how Nbconvert might behave as soon as we re-instate the stable tutorials in
https://github.com/qiskit-community/qiskit-machine-learning/blob/2bc61a3968e2fbdaecfed87d518947b65424ae06/.github/workflows/main.yml#L232-L261
These were commented out temporarily when Algorithms were merged (https://github.com/qiskit-community/qiskit-machine-learning/pull/817) because of the removed dependency. What do you think @woodsp-ibm?

This was done to make sure that when we went from version to version there were no breaking changes - at least as far as testing with the tutorials from the last (stable) minor version was concerned. The nbconvert change you did here does revert what was done earlier. I am not sure with things in this case - to some degree its a breaking change here since now we would expect users to use the parts that did come from algorithms from ML here now instead - so if you don't install qiskit-algorithms, since ML not longer depends/needs it then those stable tutorials are not going to work right. It would seem once a release was done with this self-contained ML, ie the next version, then that would be a point after which perhaps re-enabling that would make more sense?

Indeed, we should reinstate the stable tutorials after 0.8 is released. I was wondering if the nbconvert>7.14 install could give errors on the stable tutorials as soon as they are reactivated, but I don't see issues with the tutorials running in this round of checks. So, stable tutorials in 0.8 should also run with nbconvert>7.14 successfully.
I'll merge this for now, and we can revisit this after the 0.8 release if nbconvert breaks the stable tutorials.


Spawner exact copy

It would be great if powered spawner support exact copy,because wither skeleton spawning(now when i spawn wither skeletons it simply spawn normal skeletons) I request this because I not want to put MFR just for this to my pack

EnderIO has an option to replace wither skeletons with it's own version - which can then be spawned. As an alternative you can put a skeleton spawner in the nether.

Exact copy is very abusable, even though MFR provides a blacklist, there are still ways to abuse it in almost any pack out there. I don't want to open that can of worms. Do what @MatthiasMann said and spawn them in the nether.


fix: flake on TestSSHAuthSockPathHandling test

Closes #8571
When testing the TestSSHAuthSockPathHandling, Alex encountered rightfully a flake on this test, leading to this error:
Error: module at source dir "" doesn't exist or is invalid

It turns out that the error comes from the tests being run in parallel whilst relying on the same client
More context here. After the change, no flake after 30 runs on my side

Still a bit surprised that in a nested environment, when interacting with the host, the same client cannot be used in parallel. Is it my test / setup that is wrong or is it by-design / expected ?

The very reason that it sometimes work would be that one of the test sets the nested SESSION's env vars prior the second one's erasing the HOME var, or before ?

The error message you were getting here is very weird, poked around and realized that if you look in the engine logs you actually can see:
[buildkit] [client=2zpsohynpqyijy61a4upbhlt6] #3 git://gitlab.com/dagger-modules/private/test/more/dagger-test-modules-private.git
[buildkit] [client=2zpsohynpqyijy61a4upbhlt6] #3 ERROR: NotFound: rpc error: code = NotFound desc = socket xxh3:f9b3115dbb65e64e not found

So I think this is actually related to https://github.com/dagger/dagger/issues/8385
The reason the error message ends up being module at source dir "" doesn't exist or is invalid is not 100% clear to me yet, didn't dig in that deeply yet, but it has something to do with the fact that this line is saying the Git module source config file doesn't exist yet.

I'm guessing that it doesn't exist because of the error that showed up in the logs above? But would have liked this to fail more cleanly
Also the error message itself is extra confusing because it is assuming the module was local, not git (hence the source dir "" part of the message). This should probably be improved separately.

I'll keep poking at this for a few in parallel with you since it turns out to be one the good flakes that are actually reproducible locally 🎉

If it comes down to it, I'm totally fine merging this PR as is to avoid the flakes. These nested exec setups are not anything close to what real world users would do, so it's not a huge loss of test coverage if we just avoid whatever this problem is by giving each test case its own client. Worth a little bit of effort to dig into though in case it reveals any problems that are user-facing after all though.

After some println debugging, the problem appears to be that when concurrent requests are made by the clients, sometimes only one of the Query.git calls actually executes between them? At least, when I add a log to this line and the tests fail, only one of the clients actually prints anything from it. I can however see both clients are hitting the git source implementation in buildkit, which is where the socket is requested and fails in one of them (the one with the missing Query.git call).
So that all adds up: a client never executes Query.git, which is where the socket is registered in its store, and then when buildkit goes to the store to ask for the socket, it's not there.
You can also see this by running the tests with -parallel=1 and without the change in this PR: that also avoids the flake for me.
I think the reason only one of the clients actually executes Query.git is dagql caching: that API is not marked impure and so it gets deduped based on its dagql ID, which is identical for the two clients.
The last thing I don't understand is the fact that when I marked Query.git as impure (which technically would be more correct since it can end up implicitly accessing+registering these host dependent sockets), I still get the same behavior as before.

I'll poke at this for a little bit longer, but consider it separate from all this.

Overall, I don't think it's really productive for us to care about any of this. These requirements for making some API calls impure because there could technically be multiple nested clients in the same session using the same paths for different resources is something that exists only inside our test framework, not the real world. So we are honestly better off ignoring things like this for now IMO rather than going down unnecessary rabbit holes (we have plenty of necessary rabbit holes first).
@grouville tl;dr lets go with just giving each test case its own client, as you did in this PR. It might be worth a minute of your time to check if any of the other SSH socket related tests are sharing a dagger client and make the same change to this ones.
cc @vito (related to impurity, caching and all that fun stuff if you're in the mood)

Ohhh @sipsma could it be because the socket access only actually occurs in tree? We wouldn't want to mark Query.git as impure, we'd want to mark Git.tree and Git.tags.
Still seems good to me though, but also... confused. I feel like this only started appearing yesterday, about when I merged https://github.com/dagger/dagger/pull/8318. But really really unsure as to why this would have any effect at all.


Fix DispatchDataloader

This PR fixes the dispatch dataloader which was a bit broken by the recent refactors. It's untested (since it requires a multiGPU setup) but will be in the new evaluation testing @muellerzr will add soon.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Adding story and secondary button

I added a secondary button to indicate an action that is secondary.
You can check here how it looks and how I like to use it
Checklist:

[x] Test added / Snapshots updated
[x] Documentation added / updated

Usage like this:

@dan-lee this screenshots might be confusing because it shows Anna Keller twice. Actually, the second entry would be some other user.

Guck mal @mosch So ist es gerade in den Settings, wenn man die Zugriffsrechte einer externen Micro-App widerrufen möchte :)

I added a resolution because building storybook failed with

TypeError: Cannot read property 'minify' of undefined

@dan-lee @fivenp can we get this in?

So only secondary prop is really new? Rest is docs noise and refactoring?

as we added a hover effect to the button lately we should keep this in mind here too

as we added a hover effect to the button lately we should keep this in mind here too

I did and I think I made everything work together nicely.


Chrome 53.0.2785.143 m - No longer works with drag and drop lists

Firefox and IE appear to be ok, chrome is broken. Even the samples on this website do not work, unable to drag anything around.

Closing, This is fixed in chrome 55 (tested with chromium)

@Deklin
drag and drop doesn't work with chrome 58.0.3  on CentOS 7.2 again.
will you fix it?

Last time it was a browser defect with html5 drag and drop, not an issue with this library.

@Deklin
your angular-drag-and-drop-lists lib is based on AngularJS 1.
does it support Angular 2 or 4?  I haven't test it.
if not, do you have any plan to update it?

@uptonking this is not my library or module, I was just someone who wanted to contribute. @marceljuenemann owns this repository.