Added missing items to overridableComponents

Hey, I just made a Pull Request!
Added missing items to overridableComponents. Have a feeling this is a breaking change but want feedback on the naming before I get too deep into that.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

This should fix https://github.com/backstage/backstage/issues/25615

@CodiumAI-Agent /describe

@CodiumAI-Agent /improve

PR Code Suggestions ✨

CategorySuggestion                                                                                ScoreBest practice

Simplify makeStyles usage by removing unnecessary options

It's recommended to use makeStyles directly without the { name: '...' } option unless you have a specific reason for needing a custom name. This simplifies the code and follows common practices.
plugins/catalog-react/src/components/EntityOwnerPicker/EntityOwnerPicker.tsx [58-61]
-const useStyles = makeStyles(
-  _theme => ({
-    root: {
-      overflow: 'hidden',
-    },
-  }),
-  { name: 'CatalogReactEntityOwnerPicker' },
-);
+const useStyles = makeStyles(_theme => ({
+  root: {
+    overflow: 'hidden',
+  },
+}));

Suggestion importance[1-10]: 8
Why: Removing the unnecessary { name: 'CatalogReactEntityOwnerPicker' } option simplifies the code and follows common practices, improving readability without losing functionality.
8

Add type safety to ensure that only valid keys are used in style overrides

To ensure that the overrides are correctly applied and avoid runtime errors, add explicit type checks or runtime validations for the keys in CatalogReactComponentsNameToClassKey.
plugins/org/src/overridableComponents.ts [29-31]
-[Name in keyof CatalogReactComponentsNameToClassKey]?: Partial<
+[Name in keyof CatalogReactComponentsNameToClassKey as Name extends keyof StyleRules ? Name : never]?: Partial<
   StyleRules<CatalogReactComponentsNameToClassKey[Name]>
 >

Suggestion importance[1-10]: 5
Why: Adding explicit type checks can prevent runtime errors, but the suggested change is complex and might not be necessary if the current implementation is already working correctly. It's a good practice but not critical.
5

Add explicit types to the interface for better type safety

Consider adding explicit types for the BackstageComponentsNameToClassKey interface to ensure type safety and better maintainability. This will help in catching potential type mismatches during compile time.
packages/core-components/src/overridableComponents.ts [100-176]
 type BackstageComponentsNameToClassKey = {
-  ...
+  [key: string]: string;
 };

Suggestion importance[1-10]: 2
Why: While adding explicit types can improve type safety, the suggested change oversimplifies the type definition and does not align with the existing complex structure of BackstageComponentsNameToClassKey. This could lead to loss of type information.
2
Enhancement

Enhance the visual distinction of highlighted text in search results

Add specific styling rules to the highlight class in useStyles to visually differentiate highlighted text, such as a background color or font style change.
plugins/search-react/src/components/HighlightedSearchResultText/HighlightedSearchResultText.tsx [25]
-highlight: {}
+highlight: {
+  backgroundColor: 'yellow',
+  fontWeight: 'bold'
+}

Suggestion importance[1-10]: 8
Why: Adding specific styling rules to the highlight class improves the user experience by making highlighted text more visually distinct, addressing a potential usability issue.
8

Improve type safety by using Required instead of Partial for style rules

Consider using a more specific type than Partial for the style rules in BackstageOverrides. This will ensure that the overrides are strictly typed, providing better compile-time checks and potentially catching errors early.
plugins/home/src/overridableComponents.ts [28-30]
-[Name in keyof CatalogReactComponentsNameToClassKey]?: Partial<
+[Name in keyof CatalogReactComponentsNameToClassKey]?: Required<
   StyleRules<CatalogReactComponentsNameToClassKey[Name]>
 >

Suggestion importance[1-10]: 4
Why: While using Required instead of Partial can improve type safety, it may not be appropriate here as it would require all style rules to be defined, which might not be necessary. The suggestion is correct but not crucial.
4
Maintainability

Use scalable units and theme-based calculations for CSS grid properties

Replace the hard-coded pixel value in gridTemplateColumns with a calculation based on the theme's spacing function to maintain consistency and scalability with theme changes.
plugins/org/src/components/Cards/Group/MembersList/MembersListCard.tsx [137-139]
-gridTemplateColumns: `repeat(auto-fit, minmax(auto, ${theme.spacing(34)}px))`
+gridTemplateColumns: `repeat(auto-fit, minmax(auto, ${theme.spacing(8.5)}em))`

Suggestion importance[1-10]: 7
Why: This suggestion improves maintainability and scalability by using theme-based calculations, which is a good practice for consistent styling.
7

Improve the descriptive naming of makeStyles for better style traceability

Replace the custom name in makeStyles with a more descriptive one that reflects the component's functionality, improving the traceability and debuggability of the styles.
plugins/catalog/src/components/CatalogTable/CatalogTableToolbar.tsx [25-40]
 const useToolbarStyles = makeStyles(
   theme => ({
     root: {
       display: 'flex',
       justifyContent: 'space-between',
     },
     text: {
       flex: '1 1 100%',
       padding: theme.spacing(1, 0),
       color: theme.palette.text.primary,
       overflow: 'hidden',
     },
   }),
-  { name: 'PluginCatalogTableToolbar' },
+  { name: 'CatalogTableToolbarStyles' },
 );

Suggestion importance[1-10]: 6
Why: The suggestion to use a more descriptive name for makeStyles is valid and improves traceability, but the improvement is minor and does not address any critical issues.
6

Standardize the naming convention for export types to improve readability and maintainability

To avoid potential future errors and improve code readability, consider using consistent naming conventions for export types. For example, use Props suffix for all props types.
plugins/catalog-graph/src/components/CatalogGraphPage/index.ts [17-21]
-export type { CatalogGraphPageClassKey } from './CatalogGraphPage';
-export type { MaxDepthFilterClassKey } from './MaxDepthFilter';
-export type { SelectedKindsFilterClassKey } from './SelectedKindsFilter';
-export type { SelectedRelationsFilterClassKey } from './SelectedRelationsFilter';
-export type { SwitchFilterClassKey } from './SwitchFilter';
+export type { CatalogGraphPageProps, CatalogGraphPageClassKey } from './CatalogGraphPage';
+export type { MaxDepthFilterProps, MaxDepthFilterClassKey } from './MaxDepthFilter';
+export type { SelectedKindsFilterProps, SelectedKindsFilterClassKey } from './SelectedKindsFilter';
+export type { SelectedRelationsFilterProps, SelectedRelationsFilterClassKey } from './SelectedRelationsFilter';
+export type { SwitchFilterProps, SwitchFilterClassKey } from './SwitchFilter';

Suggestion importance[1-10]: 5
Why: The suggestion to standardize naming conventions is good for readability and maintainability, but it introduces new types that are not defined in the existing code, making it incomplete and potentially confusing.
5

Hi @mlkmhd, if you'd like to review this PR feel free but would it be possible for use tools in a way that doesn't just add noise to the PR? 👍

@awanlin Any update when this PR will be merged

Hi @gayatrisamant18, this fell off my radar as I didn't want to get it merged before the 1.30.0 release, I'll try and pick it up again on Friday if I have time.

@awanlin  One more question I had on this theme related styling changes.Lets say, I have added a new MUI component, then how to add that styling in custom_theme.ts. The new MUI component wont be availble in BackstageComponentKeyToClass. How to set theme for newly added MUI components?

@gayatrisamant18, if you need help then I would post your question on the Backstage Discord Server or log an issue in this repo. Sorry, just want to make sure things here are focused on the PR itself. 👍


Separate into Maven multi-module project

Same as https://github.com/USCDataScience/hadoop-pot/issues/12


Screenshot delay

Closes #80

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
4
❗

❗ storybook/components-popover--default__[w1440px]:

Before
After

❗ storybook/components-popover--default__[w1920px]:

Before
After

❗ storybook/components-popover--default__[w390px]:

Before
After

❗ storybook/components-popover--default__[w900px]:

Before
After

Shot Type
Count
Status

Added
4
🟡

Deleted
4
❌

Regression
8
❗

🟡 custom/widgets-navbar-opened__[w1440px]:

Image

🟡 custom/widgets-navbar-opened__[w1920px]:

Image

🟡 custom/widgets-navbar-opened__[w390px]:

Image

🟡 custom/widgets-navbar-opened__[w900px]:

Image

❌ custom/widgets-navbar--mobile-opened__[w1440px]:

Image

❌ custom/widgets-navbar--mobile-opened__[w1920px]:

Image

❌ custom/widgets-navbar--mobile-opened__[w390px]:

Image

❌ custom/widgets-navbar--mobile-opened__[w900px]:

Image

❗ custom/widgets-heart-rate--hint-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w1920px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w390px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w900px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w900px] (click to expand)

Before
After

❗ storybook/widgets-meal-nutrients--default__[w900px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w390px] (click to expand)

Before
After

Shot Type
Count
Status

Added
2
🟡

Deleted
0
❌

Regression
4
❗

🟡 custom/widgets-navbar-opened__[w1920px]:

Image

🟡 custom/widgets-navbar-opened__[w900px]:

Image

❗ custom/widgets-heart-rate--hint-opened__[w1920px]:

Before
After

❗ custom/widgets-navbar-opened__[w1440px]:

Before
After

❗ custom/widgets-navbar-opened__[w390px]:

Before
After

❗ storybook/widgets-heart-rate--default__[w900px]:

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
2
❗

❗ storybook/utility-responsive-image--responsive-image__[w1440px]:

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px]:

Before
After

Shot Type
Count
Status

Added
1
🟡

Deleted
0
❌

Regression
4
❗

🟡 custom/widgets-navbar-opened__[w900px]:

Image

❗ custom/widgets-heart-rate--hint-opened__[w900px]:

Before
After

❗ custom/widgets-navbar-opened__[w1920px]:

Before
After

❗ custom/widgets-navbar-opened__[w390px]:

Before
After

❗ storybook/widgets-progress-info--default__[w390px]:

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
0
❗

Shot Type
Count
Status

Added
1
🟡

Deleted
0
❌

Regression
4
❗

🟡 custom/widgets-navbar-opened__[w900px]:

Image

❗ custom/widgets-navbar-opened__[w1440px]:

Before
After

❗ custom/widgets-navbar-opened__[w390px]:

Before
After

❗ storybook/widgets-heart-rate--default__[w1920px]:

Before
After

❗ storybook/widgets-progress-info--default__[w390px]:

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
16
❗

❗ storybook/components-card--item-card__[w1440px] (click to expand)

Before
After

❗ storybook/components-card--item-card__[w1920px] (click to expand)

Before
After

❗ storybook/components-card--item-card__[w390px] (click to expand)

Before
After

❗ storybook/components-card--item-card__[w900px] (click to expand)

Before
After

❗ storybook/components-card--item-card-action__[w1440px] (click to expand)

Before
After

❗ storybook/components-card--item-card-action__[w1920px] (click to expand)

Before
After

❗ storybook/components-card--item-card-action__[w390px] (click to expand)

Before
After

❗ storybook/components-card--item-card-action__[w900px] (click to expand)

Before
After

❗ storybook/components-card--item-card-avatar__[w1440px] (click to expand)

Before
After

❗ storybook/components-card--item-card-avatar__[w1920px] (click to expand)

Before
After

❗ storybook/components-card--item-card-avatar__[w390px] (click to expand)

Before
After

❗ storybook/components-card--item-card-avatar__[w900px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1440px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w390px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w900px] (click to expand)

Before
After

Shot Type
Count
Status

Added
13
🟡

Deleted
0
❌

Regression
11
❗

🟡 custom/widgets-meal-nutrients--hint-opened__dropdown__[w1440px] (click to expand)

Image

🟡 custom/widgets-meal-nutrients--hint-opened__dropdown__[w1920px] (click to expand)

Image

🟡 custom/widgets-meal-nutrients--hint-opened__dropdown__[w390px] (click to expand)

Image

🟡 custom/widgets-meal-nutrients--hint-opened__dropdown__[w900px] (click to expand)

Image

🟡 custom/widgets-navbar-opened__[w900px] (click to expand)

Image

🟡 custom/widgets-progressInfo__[w1440px] (click to expand)

Image

🟡 custom/widgets-progressInfo__[w1920px] (click to expand)

Image

🟡 custom/widgets-progressInfo__[w390px] (click to expand)

Image

🟡 custom/widgets-progressInfo__[w900px] (click to expand)

Image

🟡 custom/widgets-progressInfo__dropdown__[w1440px] (click to expand)

Image

🟡 custom/widgets-progressInfo__dropdown__[w1920px] (click to expand)

Image

🟡 custom/widgets-progressInfo__dropdown__[w390px] (click to expand)

Image

🟡 custom/widgets-progressInfo__dropdown__[w900px] (click to expand)

Image

❗ custom/widgets-heart-rate--hint-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w1920px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w390px] (click to expand)

Before
After

❗ custom/widgets-heart-rate--hint-opened__[w900px] (click to expand)

Before
After

❗ custom/widgets-meal-nutrients--hint-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-navbar-opened__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w390px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w1440px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w390px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w900px] (click to expand)

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
2
❗

❗ storybook/utility-responsive-image--responsive-image__[w1440px]:

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px]:

Before
After

Shot Type
Count
Status

Added
12
🟡

Deleted
0
❌

Regression
8
❗

🟡 storybook/components-indicator--default__[w1440px] (click to expand)

Image

🟡 storybook/components-indicator--default__[w1920px] (click to expand)

Image

🟡 storybook/components-indicator--default__[w390px] (click to expand)

Image

🟡 storybook/components-indicator--default__[w900px] (click to expand)

Image

🟡 storybook/components-indicator--right-side__[w1440px] (click to expand)

Image

🟡 storybook/components-indicator--right-side__[w1920px] (click to expand)

Image

🟡 storybook/components-indicator--right-side__[w390px] (click to expand)

Image

🟡 storybook/components-indicator--right-side__[w900px] (click to expand)

Image

🟡 storybook/components-indicator--with-content__[w1440px] (click to expand)

Image

🟡 storybook/components-indicator--with-content__[w1920px] (click to expand)

Image

🟡 storybook/components-indicator--with-content__[w390px] (click to expand)

Image

🟡 storybook/components-indicator--with-content__[w900px] (click to expand)

Image

❗ storybook/components-button--all-states__[w1440px] (click to expand)

Before
After

❗ storybook/components-button--all-states__[w1920px] (click to expand)

Before
After

❗ storybook/components-button--all-states__[w390px] (click to expand)

Before
After

❗ storybook/components-button--all-states__[w900px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1440px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w390px] (click to expand)

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w900px] (click to expand)

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
8
❗

❗ custom/widgets-meal-nutrients--hint-opened__[w900px] (click to expand)

Before
After

❗ custom/widgets-navbar-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-navbar-opened__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w390px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w1440px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w390px] (click to expand)

Before
After

❗ storybook/widgets-progress-info--default__[w900px] (click to expand)

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
2
❗

❗ storybook/components-indicator--with-content__[w900px]:

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px]:

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
6
❗

❗ custom/widgets-meal-nutrients--hint-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-meal-nutrients--hint-opened__[w900px] (click to expand)

Before
After

❗ custom/widgets-navbar-opened__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w1440px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w1920px] (click to expand)

Before
After

❗ storybook/widgets-steps-counter--default__[w1920px] (click to expand)

Before
After

This is not a 100% solution because we need to use only screenshots from (e2e tests) Playwright to get the solution we want.
But it's enough to close #71 and #80 for now.


Screens look bad on desktop

@RenatBuga we still think that it would be good to improve the view for the desktop web users.
Could you sketch how it could we rearrange components to make them more user friendly?
Something like http://web.trafi.com/


Use build-in xml package

Prefer the built in xml package over the nonstandard lxml package.

@dave3d Why was lxml used of xml?


[Help] Watermark and spec list font

Hello, so im making my own paste with osiris and i want to change the font of the watermark and the spectator list.
I tried some things but still not works.
I would appreciate if someone helps me :))

interfaces->surface->setTextFont(number);

interfaces->surface->setTextFont(number);
Still not working, with 1 its very small, and with 2 its not the font i want.

What I like to do is make the number a variable in the config and put an inputint in the gui and then you can look through every font and pick the one that suits you the best

hi,
can you send me the code for this?
i'm a beginner.


Question: MPPnet

What is the inference time for MPPnet?

The inference time (not including IO ) is about 200ms for 4-frame and 16frame's latency is about 50ms longer than 4frame ( resuing feature stored in a memory bank and running on V100).

About the performance of MPPNet, are you aligned with the paper. Is there anything else that needs to be changed.

Following the guideline, this implementation can achieve similar performance to the paper.
Note: You need to generate multi-frame pkl first, and then train centerpoint_4frame as instructed. If the results of centerpoint_4frame are similar to the paper, you can get the reported performance of MPPNet，employing centerpoint_4frame as RPN.

Following the guideline, this implementation can achieve similar performance to the paper. Note: You need to generate multi-frame pkl first, and then train centerpoint_4frame as instructed. If the results of centerpoint_4frame are similar to the paper, you can get the reported performance of MPPNet，employing centerpoint_4frame as RPN.

I have been based on the guideline to generate multi-frame pkl first. The details are shown in link https://github.com/open-mmlab/OpenPCDet/issues/1111. But I could not get the results of centerpoint_4frame are similar to the paper. How do I align the first phase of MPPNet performance.

Close this since it has been discussed in https://github.com/open-mmlab/OpenPCDet/issues/1111.


Type hints TypeError

def load_txt2img_custom_tracked_component_ids() -> list[str]: TypeError: 'type' object is not subscriptable
i can't create a pull request.
from typing import List and change list[str] to List[str]

What version of Python are you loading with Stable Diffusion?
I'm on 3.10.6 and no errors here.

I'm still on Python 3.8.10 for A1111. the extension still works. But I'm always getting this error at startup.

That's the issue. The minimum recommended Python version is 3.10.6, so I won't make code changes to address your error.


Update version to 2.1.1 and update release notes

@yamt, @loganek I am planning to create a new release since there are lots of commits after version 2.1.0 was created, and as the commits are mainly related to bug fixings and some enhancements, few new features were added except exporting some new APIs, I think 2.1.1 should be good. Wondering whether it is good to you? Thanks.

i'm not aware of any release-blocking problems. thank you.

Sounds good to me, thanks for making the release.

Welcome, FYI, WAMR-2.1.1 was created:
https://github.com/bytecodealliance/wasm-micro-runtime/releases/tag/WAMR-2.1.1


Align Right in Table Breaks Cell

Describe the bug
After typing text into a cell of a table, when I select 'Align right', the individual cell squeezes to the right which looks odd.
Steps To Reproduce

Create a table (tested with 4x4)
Enter some text in some cells
Click a cell(s)
Click the 'Align right' button

Expected behavior
The table shape and size remains unchanged while aligning the text in the selected cell to the right side.
Screenshots

Your Configuration:

Exact BookStack Version (Found in settings): v0.25.1
PHP Version: 7.2.14
Hosting Method (Nginx/Apache/Docker): Apache

Additional context
Freshly installed yesterday.

@cwmke Thanks for reporting, this definitely is not right, can see what's going wrong though so should be fairly quick to fix. Have assigned to the next bugfix release.
Surprised how long this must have gone unreported

Fix applied, Will be in the next patch release.

4 month I want to add this issue... @ssddanbrown I dont see a patch to resolve this little bug. Is it really applied ?

@jeromequintard it should be. If you're experiencing issues please confirm your BookStack version and the exact issue you are coming across.


syntax error on line 12

if anyone can help me pls do

Did you try to replace this here

with this?

The method you use is kinda old and the other one is more recommended.

@Andre601 thanks... im trying to make a discord API in nocode, this will really help

@Andre601 Finished! https://github.com/Saini14/discord.nocode/blob/master/README.md

I think I need to get my eyes checked.

Did you try to replace this here

with this?

The method you use is kinda old and the other one is more recommended.

Definitely right, I am a big fan of nocode, and I also imported it into all my projects, it works well in this way.

I really thought there was something wrong with my computer

I really thought there was something wrong with my computer

haha, nah mate... im writing a book on how to code in NoCode!


ERR_INVALID_ARG_TYPE

error error in hook onWatched from @vuepress-plume/plugin-notes-data
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
按照文档的快速上手启动就报错

已修复该问题


add clear of APP_VERSION

when using serviceworkers it seems to be necessary to clean the APP_VERSION in localstorage too.
window.localstorage.setItem("APP_VERSION", ""); does the job.

For your use case, you can manually remove ite.


Allow users to customise number of recent presets

At the moment, iD shows the four most recently used preset at the top of the list.
However sometimes this means recently used presets drop off the list if you are editing an area which needs a variety of presets. Add a car park, a building, some trees, a pitch and then you're having to type in "car" again to add another car park.
It would be useful if this could be increased - the preferences panel would be a good places to have a box with an up/down selector.

Given the wide variety of things I work on in a single edit set day after day e.g farmland, farmyard, buildings, track, orchard, meadow, grassland tree, tree rows as a typical group, certainly many times thought of this. 8-10 last used  would be great and persistent, groups of these one can save to the user profile would be the ultimate so they can be recalled at the next session.
Big Bump.

Here’s what currently controls the number of remembered recent presets:
https://github.com/openstreetmap/iD/blob/aee82585706e97850e5b14190516c72632fcae98/modules/presets/index.js#L392
Here’s what determines the contents of the Preferences pane:
https://github.com/openstreetmap/iD/blob/3bf8d52ca9a8d371f31e6d25243c12bf31a7b94f/modules/ui/panes/preferences.js#L13-L15
Here’s what a section definition looks like:
https://github.com/openstreetmap/iD/blob/3bf8d52ca9a8d371f31e6d25243c12bf31a7b94f/modules/ui/sections/privacy.js#L7-L68


tf.math.add runs successfully Documentation Unsupported type: uint16

Click to expand!
Issue Type
Documentation Bug
Source
source
Tensorflow Version
TF 2.10
Custom Code
Yes
OS Platform and Distribution
windows 11
Mobile device
No response
Python version
3.8.15
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
CUDA: 11.3       cuDNN cuDNN 8.6.0
GPU model and memory
RTX3060
Current Behaviour?
According to the TensorFlow2.10 documentation, tf.math.add(x, y, name=None), the types of x and y must be A Tensor. types: bfloat16, half, float32, float64, uint8, int8, int16, int32, int64 , complex64, complex128, string.
But when the type of my x and y is input as uint16, I found that the program can run successfully, so I suggest that the document can be modified.

Standalone code to reproduce the issue
from tensorflow import int64
    from tensorflow import uint16
    import tensorflow as tf
    with tf.device('/CPU'):
        x = tf.saturate_cast(tf.random.uniform([1, 2, 1, 3], minval=0, maxval=257, dtype=tf.int64), dtype=tf.uint16)
        y = tf.saturate_cast(tf.random.uniform([2, 1, 3, 1], minval=0, maxval=257, dtype=tf.int64), dtype=tf.uint16)
        res = tf.math.add(x, y)
    print(res)

Relevant log output
Test code result:
tf.Tensor(
  [[[[350 277 296]
   [259 186 205]
   [183 110 129]]

  [[376 204 403]
   [285 113 312]
   [209  37 236]]]

 [[[189 116 135]
   [244 171 190]
   [178 105 124]]

  [[215  43 242]
   [270  98 297]
   [204  32 231]]]], shape=(2, 2, 3, 3), dtype=uint16)

tf.math.cumsum also has such a situation, the official type of the parameter x must be float32, float64, int64, int32, uint8, uint16, int16, int8, complex64, complex128, qint8, quint8, qint32, half, but uint32, etc. can run the code successfully.
code:
x = tf.cast(tf.random.uniform([2, 4], minval=0, maxval=2, dtype=tf.int32), dtype=tf.uint32)
axis = 1
results["res_cpu"] = tf.math.cumsum(x,axis=axis)

tf.math.floor also has such a situation,  the official type of the parameter x must be  bfloat16, half, float32, float64, etc. can run the code successfully.
code:
import tensorflow as tf
with tf.device('/CPU'):
x = tf.random.uniform([6, 1], minval=-256, maxval=257, dtype=tf.float16)
res = tf.floor(x)
print(res)

I like to solve this bug  I am  new to open source can anyone guide me?

@triumph-wangyuyang
There is internal PR created. Once the PR merged issue will close.
Thank you


Add Support to grab a Secret which requires comments

Add Support to grab a Secret which requires comments
"Get-Secret : Secret server returned error The requested Secret requires a comment when viewed."
Add support to parse a comment to the Secrets, which require them and retrieve the comment.

Second... had written my own version of Get-Secret before I knew about this one, and came to look for this exact scenario.  In the meantime, I will make a version of the secret that doesn't require the check-out comment, but IAM may not like it.  :D


Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Duplicate of https://github.com/biomejs/biome/issues/2475 ?

@ematipico Yes, you're right. I missed that issue. I'll close this one


Expose missing Quaternion operators.

Scripts can now evaluate the following cases:

(quat * real) and (quat / real)
(quat + quat) and (quat - quat)

Can't it be declared the same way as for Vector3, using DEFAULT_OP_LOCALMEM(+,QUAT,Quat);?

Right, rebased.

Mhh, CI failed on the android build, but it doesn't look like it was the code's fault ^^

Restarted android build


CSS support

I'm trying to add support to CSS files with the @apply directive
Example :
body {
    @apply container p-10;
}

Tree Sitter playground give me this :
rule_set [0, 0] - [2, 1]
  selectors [0, 0] - [0, 4]
    tag_name [0, 0] - [0, 4]
  block [0, 5] - [2, 1]
    postcss_statement [1, 4] - [1, 26]
      at_keyword [1, 4] - [1, 10]
      plain_value [1, 11] - [1, 20]
      plain_value [1, 21] - [1, 25]

First, I tried to query the plain_value but, I can only select them independently → not a good option
(postcss_statement
    .(at_keyword) @_keyword (#eq? @_keyword "@apply")
    ((plain_value).(plain_value)*.) @tailwind
)

Then I wrote this :
(
    (postcss_statement
        .(at_keyword) @_keyword (#eq? @_keyword "@apply")
        ((plain_value).(plain_value)*.)
    ) @_apply
    (#offset! @_apply 0 7 0 -1)
) @tailwind

And I'm almost there, the only remaining problem is : the semicolon at the end is being moved when the sort is applied.
Even with my offset of -1 end column

What grammar/treesitter parser is this?
Because I get this with the css parser and that css snippet of yours:
(rule_set ; [1:1 - 3:1]
  (selectors ; [1:1 - 4]
    (tag_name)) ; [1:1 - 4]
  (block ; [1:6 - 3:1]
    (at_rule ; [2:3 - 24]
      (at_keyword) ; [2:3 - 8]
      (keyword_query) ; [2:10 - 18]
      (ERROR ; [2:20 - 23]
        (ERROR))))) ; [2:20 - 20]

I think, TreeSitter CSS add support for @apply recently : b21ec1d
@laytan so maybe update your TreeSitter and you will be able to have it

Ah you are correct, it is not an error anymore now. Additionally I got the query working like this:
(
  (postcss_statement
    .(at_keyword) @_keyword (#eq? @_keyword "@apply")
    ((plain_value).(plain_value)*.)
  ) @tailwind
  (#offset! @tailwind 0 8 0 -2)
)

Would you like to make a pull request?

Thanks, works like a charm 🤩
I made a PR,
and I made a second one for Go Templ support 👍


Erroneous highlighting of best 5K score on multicore

Rust is crowned the winner despite being >1ms slower than C# w/ AoT

fixed: https://github.com/jinyus/related_post_gen/commit/1bb7efb420983c26f9212bf3ccca9f2789603cf9


Add Sajal24

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Hey, I just added my name and github link here.
Do I need to change anything else?


Bug when using token reference syntax in border's composite value

Description
Hello guys, I have a problem with a token usage :
export const borderWidths = defineTokens.borderWidths({
  thin: { value: '1px' },
  thick: { value: '2px' },
})

export const borders = defineTokens.borders({
  brand: { value: { width: '{borderWidths.thick}', color: '#fff', style: 'solid' } },
})

The output is "--borders-brand: var(--border-widths-thick) px solid #fff;"
Which is equal "2px px solid #fff"
Note the "2px px" which cause the CSS to not apply.
Link to Reproduction
https://play.panda-css.com/1736HE8uZB
Steps to reproduce

Open console
Check the element with the "bd_brand" class
See the value of the border ? It's "2px px solid #fff"

JS Framework
No response
Panda CSS Version
0.47.0
Browser
No response
Operating System

[x] macOS
[x] Windows
[x] Linux

Additional Information
No response

I just pushed a fix for this. We'll release an update shortly.
If the issue persists after upgrading, I'll re-open it.


Not working with graphql subscriptions

I was able to set this up and get it to work for queries, but it doesn't work for subscriptions.

This issue was probably meant for tada 😅 this is the lsp repo

Ok thanks @JoviDeCroock. Any reasons why it's not working for subscriptions?


Please add support for SEA802 and SEA801 Thermostats

Device description
Thermostat device
Zigbee2mqtt page
https://www.zigbee2mqtt.io/devices/SEA801-Zigbee.html
MQTT message with device information
PUT here the device data you receive when publish message with topic
zigbee2mqtt/bridge/config/devices, as example
{"dateCode":"","description":"Thermostatic radiator valve","friendly_name":"Hobbykamer","hardwareVersion":1,"ieeeAddr":"0x5c0272fffec3c9af","lastSeen":1606738836307,"manufacturerID":4098,"manufacturerName":"_TZE200_c88teujp","model":"SEA802-zigbee","modelID":"TS0601","networkAddress":49532,"powerSource":"Battery","type":"EndDevice","vendor":"Saswell"}

info  2020-11-30 13:19:29: MQTT publish: topic 'homeassistant/sensor/0x5c0272fffec3c9af/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x5c0272fffec3c9af"],"manufacturer":"Saswell","model":"Thermostatic radiator valve (SEA802-Zigbee)","name":"Hobbykamer","sw_version":"Zigbee2MQTT 1.16.1-dev"},"icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/Hobbykamer","name":"Hobbykamer_linkquality","state_topic":"zigbee2mqtt/Hobbykamer","unique_id":"0x5c0272fffec3c9af_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'

info  2020-11-30 13:19:29: MQTT publish: topic 'homeassistant/climate/0x5c0272fffec3c9af/climate/config', payload '{"action_template":"{% set values = {'idle':'off','heat':'heating','cool':'cooling','fan only':'fan'} %}{{ values[value_json.running_state] }}","action_topic":"zigbee2mqtt/Hobbykamer","availability":[{"topic":"zigbee2mqtt/bridge/state"}],"away_mode_command_topic":"zigbee2mqtt/Hobbykamer/set/away_mode","away_mode_state_template":"{{ value_json.away_mode }}","away_mode_state_topic":"zigbee2mqtt/Hobbykamer","current_temperature_template":"{{ value_json.local_temperature }}","current_temperature_topic":"zigbee2mqtt/Hobbykamer","device":{"identifiers":["zigbee2mqtt_0x5c0272fffec3c9af"],"manufacturer":"Saswell","model":"Thermostatic radiator valve (SEA802-Zigbee)","name":"Hobbykamer","sw_version":"Zigbee2MQTT 1.16.1-dev"},"hold_command_topic":"zigbee2mqtt/Hobbykamer/set/preset","hold_modes":["Schedule"],"hold_state_template":"{{ value_json.preset }}","hold_state_topic":"zigbee2mqtt/Hobbykamer","json_attributes_topic":"zigbee2mqtt/Hobbykamer","max_temp":"30","min_temp":"5","mode_command_topic":"zigbee2mqtt/Hobbykamer/set/system_mode","mode_state_template":"{{ value_json.system_mode }}","mode_state_topic":"zigbee2mqtt/Hobbykamer","modes":["off","heat"],"name":"Hobbykamer","temp_step":0.5,"temperature_command_topic":"zigbee2mqtt/Hobbykamer/set/current_heating_setpoint","temperature_state_template":"{{ value_json.current_heating_setpoint }}","temperature_state_topic":"zigbee2mqtt/Hobbykamer","temperature_unit":"C","unique_id":"0x5c0272fffec3c9af_climate_zigbee2mqtt"}'

info  2020-11-30 13:19:29: MQTT publish: topic 'homeassistant/binary_sensor/0x5c0272fffec3c9af/battery_low/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x5c0272fffec3c9af"],"manufacturer":"Saswell","model":"Thermostatic radiator valve (SEA802-Zigbee)","name":"Hobbykamer","sw_version":"Zigbee2MQTT 1.16.1-dev"},"device_class":"battery","json_attributes_topic":"zigbee2mqtt/Hobbykamer","name":"Hobbykamer_battery_low","payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/Hobbykamer","unique_id":"0x5c0272fffec3c9af_battery_low_zigbee2mqtt","value_template":"{{ value_json.battery_low }}"}'

info  2020-11-30 13:19:29: MQTT publish: topic 'homeassistant/switch/0x5c0272fffec3c9af/window_detection/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/Hobbykamer/set/window_detection","device":{"identifiers":["zigbee2mqtt_0x5c0272fffec3c9af"],"manufacturer":"Saswell","model":"Thermostatic radiator valve (SEA802-Zigbee)","name":"Hobbykamer","sw_version":"Zigbee2MQTT 1.16.1-dev"},"icon":"mdi:window-open-variant","json_attributes_topic":"zigbee2mqtt/Hobbykamer","name":"Hobbykamer_window_detection","payload_off":"OFF","payload_on":"ON","state_off":"OFF","state_on":"ON","state_topic":"zigbee2mqtt/Hobbykamer","unique_id":"0x5c0272fffec3c9af_window_detection_zigbee2mqtt","value_template":"{{ value_json.window_detection }}"}'

info  2020-11-30 13:19:29: MQTT publish: topic 'homeassistant/lock/0x5c0272fffec3c9af/child_lock/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/Hobbykamer/set/child_lock","device":{"identifiers":["zigbee2mqtt_0x5c0272fffec3c9af"],"manufacturer":"Saswell","model":"Thermostatic radiator valve (SEA802-Zigbee)","name":"Hobbykamer","sw_version":"Zigbee2MQTT 1.16.1-dev"},"json_attributes_topic":"zigbee2mqtt/Hobbykamer","name":"Hobbykamer_child_lock","payload_lock":"LOCK","payload_unlock":"UNLOCK","state_locked":"LOCKED","state_topic":"zigbee2mqtt/Hobbykamer","state_unlocked":"UNLOCKED","unique_id":"0x5c0272fffec3c9af_child_lock_zigbee2mqtt","value_template":"{{ value_json.child_lock }}"}'

MQTT messages from device
Put here examples of MQTT messages with different states you've received from device, as example
info  2020-11-30 13:36:49: MQTT publish: topic 'zigbee2mqtt/Hobbykamer', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":"false","child_lock":"LOCKED","current_heating_setpoint":"16.0","frost_detection":"ON","last_seen":"2020-11-30T13:36:49+01:00","linkquality":111,"local_temperature":"21.8","local_temperature_calibration":0,"preset_mode":"Schedule","system_mode":"heat","window_detection":"ON"}'

MQTT state change commands
If device supports state change put MQTT topics + payload examples to change device state here

@SargonofAssyria, could you please check what is supported by the latest plugin version and report here what's missing.

@SargonofAssyria, could you please check what is supported by the latest plugin version and report here what's missing.

I checked, and the only thing that is missing is:
2021-01-18 09:49:42.390 Error: (Zigbee) Hobbykamer: can not process numeric item "local_temperature_calibration"

It is not mentioned here: https://www.zigbee2mqtt.io/devices/SEA801-Zigbee_SEA802-Zigbee.html#saswell-sea801-zigbee%252Fsea802-zigbee
Log:
info  2021-01-18 09:49:41: MQTT publish: topic 'zigbee2mqtt/Hobbykamer', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":"19.0","frost_detection":"ON","last_seen":"2021-01-18T09:44:00+01:00","local_temperature":"17.7","local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"ON"}'

I checked, and the only thing that is missing is:
2021-01-18 09:49:42.390 Error: (Zigbee) Hobbykamer: can not process numeric item "local_temperature_calibration"

It is not mentioned here: https://www.zigbee2mqtt.io/devices/SEA801-Zigbee_SEA802-Zigbee.html#saswell-sea801-zigbee%252Fsea802-zigbee
Log:
info  2021-01-18 09:49:41: MQTT publish: topic 'zigbee2mqtt/Hobbykamer', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":"19.0","frost_detection":"ON","last_seen":"2021-01-18T09:44:00+01:00","local_temperature":"17.7","local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"ON"}'

Awesome, we already have a ticket for that #541, so closing this one

Awesome, we already have a ticket for that #541, so closing this one


Update wgpu example to wgpu 0.7

Our current WGPU example uses 0.6 and the 0.7 release of WGPU has some breaking changes that require non-trivial updates to our example. It would nice to upgrade to it though.

I'm going to look into this, ark work is currently turning my head into a concrete mixer, and I could use some relatively boring upgrade work to clear my head


Use clang as default compiler

With android ndk 11, gcc is deprecated and clang is recommended.
Sidenotes:
These notes are not directly related to clang but to an update of the toolchain.

Qt 5.7 requires C++11 features, which must be enabled within cmake
Qt 5.6 seems to require gcc-4.8 which is only shipped up to ndk 10. If gcc-4.8 is not present qscintilla will fail to compile.

Keep an eye on these toolchains:
https://github.com/OSVR/android-cmake/tree/libcxx

Hello,
for qscintilla under Qt5.6, you can force ANDROID_NDK_TOOLCHAIN_VERSION variable to match TOOLCHAIN_VERSION. This seems to work for Qt5.6.1 and NDK 13 (at least, it does compile qscintilla): qmake use 4.9 toolchain directory instead of default 4.8.


Update Alabama legislators for 2019

Committee assignments aren't up yet, so this only updates the legislator information.
Part of #38.

Pull Request Test Coverage Report for Build 150

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 67.913%

Totals

Change from base Build 143:
0.0%

Covered Lines:
908

Relevant Lines:
1337

💛  - Coveralls


Update tensorflow-core-api to 0.3.2

Updates org.tensorflow:tensorflow-core-api from 0.3.1 to 0.3.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.tensorflow", artifactId = "tensorflow-core-api" } ]

labels: library-update, semver-patch

Codecov Report

Merging #166 (298c160) into main (d32d2c0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #166   +/-   ##
=======================================
  Coverage   70.00%   70.00%
=======================================
  Files           4        4
  Lines          80       80
  Branches        4        4
=======================================
  Hits           56       56
  Misses         24       24

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 d32d2c0...298c160. Read the comment docs.


Query tab: extranous line after service restart

I have pgweb constantly running in the background (as user-service managed by systemd), and the browser tab is pinned in Firefox. Recently I've upgraded from 0.10.0 (or 0.11.0) to the latestest 0.11.6 version. I've noticed that the query tab sometimes has an extra line or two the textarea:

(reenactment, the original query had about 40 lines)
I'm pretty sure, I left the last query to be just select 1. Today I've found fragments of another query appended to that (I've pasted the when clause yesterday sometime prior to creating the select 1 query).
This doesn't always happen though, and I cannot reproduce it if I want to. Clearing the browser cache and storage did not help either (after deleting the local storage, it didn't happen for some days, now it's back). The FF DevTools don't show anything interesting...
Any chance you've encountered this before?

I've come closer to a reproduction:

Start pgweb.
Point Firefox to https://localhost:8081 (or whatever you specified with --bind and --listen). I'm using 89.0.1
Enter a multiline query into the query editor, likewith numbers as (select generate_series(1, 5) as n)
select *
from numbers
where n > 2

Mark the last line (where n > 2).
Hit Ctrl+c, then Ctrl+v to replace the line with itself.
Close and reopen the browser.
Observe the content of the query editor:with numbers as (select generate_series(1, 5) as n)
select *
from numbers
where n > 2where n > 2

or, depending on whether you copied/pasted the line with line break:with numbers as (select generate_series(1, 5) as n)
select *
from numbers
where n > 2
where n > 2

This suggest something funny with the pgweb_query storage mechanism for LocalStorage.

Im sorry this took so long, but i'll try to repro this issue. Im pretty sure i haven't seen anything like it before. Which OS was this issue on?

This is reproducible on my Debian 10 workstation. IIRC, I've seen this on a Windows 10 VM as well.

I was trying to reproduce this on OSX (my main dev os) with Chrome and Firefox - no luck.

Hm, I'll dig into this a bit more next week, when I'm back at work.


🌐 Add Chinese translation for docs/async.md

as title

📝 Docs preview for commit 99fac02a2d2c9d87a2ad45d6711330b62888f01a at: https://649a2380c3bf901b5aa9e53c--fastapi.netlify.app

Thank you! It seems this one was handled in another PR, so I'll pass on this one, but feel free to add new PRs updating the current version if you think that's needed!
Thanks! ☕ 🍰


questions about developer setup, improvements

Hi @thomasdkelly,
First I would like to take a moment to appreciate your effort here. Great initiative to create a FOSS AquaCrop implementation!
I am a freelance GIS developer, looking at spending substantial amount of time using your aquacrop module this year. (See more explanation in the bottom 👇)
Do you welcome PRs and ideas about fixes/improvements (performance, code architecture)?
If yes what would be the 'right' developer setup as of now? Before the holidays I did a dev. setup on my machine (via nbdev) , but as I understand from #16 you are moving away from it now?
I got hired for a project within the context of analysis ready GIS/EO data for the CEE region.
As part of a 'showcase', we would build a crop modelling solution that takes EO/GIS derived inputs from a data platform of ESA, and run the model. The goal is to make the process of model setup quicker and easier, but also to provide some optimization features. If you are interested in more detail, you can mail me at<EMAIL_ADDRESS>

Great, thanks!


[BUG]

when using SelectWeekDays in a dialog, close the diolog and enter it again the selected days remain selected unless I leave the page and come back again, I need to somehow reset the selectedDays list

Hey @AbnerRibeirodaSilva  thanks for opening the issue and sorry for the late reply. Would you like to work on it?

@AbnerRibeirodaSilva this is fixed in #15


FAILURE: Build failed with an exception.

Hi,
I use RN 47.0 and html-to-pdf 0.5.0
FIRST, I tried the library in a new RN application and it worked.
SECOND, I added this library to my existing project and the app coudlnt run because of this error :
FAILURE: Build failed with an exception.

What went wrong:
Could not read path 'C:\Users....\node_modules\react-native-html-to-pdf\android\build\generated\source\buildConfig\debug\com\parkerdan\htmltopdf'.

C:\Users...\node_modules\react-native-html-to-pdf\android\build\generated\source\buildConfig\debug\com\parkerdan\htmltopdf

Then, I rerun the code in case some software error (which I believe it is and therefore this is not an issue, I guess) and then I got the following which is more important:
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex

it looks similar to #46 and I tried to solve it with gradlew clean build, still no help.. I tried many other ways but still no solution. Any ideas related to this error?

sorry to add this issue here, because this is unrelated to html-to-pdf library. This is regarding and DEX issue and the solution is here


Alternate Skip Identification Method

Add another method of identifying the skip button. Identification fails with different text sometimes.

actually just reducing the confidence fixes it


ESLINT_DISABLED breaks webpack

Description
If you disable eslint using the ESLINT_DISABLED ENV variable, webpack breaks with No Loader specified.
Because the resulting rule is:
      {
            test: /\.m?js$/,
            exclude: /(node_modules|bower_components|vendors)/,
            use: [
                {
                    loader: 'babel-loader',
                    options: babelrc,
                },
                {},
            ],
        },

An empty object is not allowed here.
Possible Solution
Refactoring necessary.
Additional context

Hi Hans and thank you for reporting this issue.
You are right this looks really misconfigured. Not just because it breaks the config but because it can disable lint for non development environments, too.
We already scheduled the issue. You can track the progress at:
https://issues.shopware.com/issues/NEXT-5970

Its fixed in the meanwhile. Tested working on master


 Since INSDC master records are entries to group contigs and they themselves do not have sequence data, they should be distinguished from the other INSDC entries.
On webpages of the Assembly database, master records are referred in the "WGS Project" attribute.
e.g. https://www.ncbi.nlm.nih.gov/assembly/GCA_000001765.3
Thus I have renamed the namespace to insdc_master_record and have set Project as the category of it.

note:
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3245039/#sec-19title
WGS sequences appear in GenBank as groups of sequence-overlap contigs collected under a master WGS record. Each master record represents a WGS project and has an accession number in the Nucleotide database consisting of a four-letter prefix followed by eight zeroes and a version suffix as found in standard GenBank records.


My Phone is DEAD and there is no way to find a Cable nearby!!

  Leave the project and go home ????????????
It only has text or call for authentication.

@dilanthaonline Thank you for reaching out. However, we need more information on what you are trying to achieve. Could you please provide the document link which you are following?

Its Microsoft Two factor Authentication on Azure servers.

@dilanthaonline Apologies for your inconvenience. We use GitHub for documentation improvement as opposed to troubleshooting issues. We would request you to post any issues related to azure and Microsoft 365 products which might require troubleshooting, on our new forum Microsoft QnA . We have a vibrant community there who can provide you better guidance for such issues.
Coming to your issue, we can understand that it might have been frustrating to go though this situation. I hope you have been able to access the server properly after charging the phone by this time . However in these situations you will need to contact your internal IT whoever can manage and disable the MFA on your account temporarily . They can make changes at MFA management page if you are global admin of your azure AD tenant. If you do not have global admin access , I would suggest to contact your internal IT who manages your azure active directory where your account belongs to.  If you have been allowed to change the MFA settings by your organization then you can modify your account's security info by going to https://mysignins.microsoft.com/security-info and trying to add a new method in the security info as shown below.

You can add an alternate number additional to your primary one temporarily for getting through this kind of situation in future . Microsoft cannot make changes to customer tenants in such cases. Hence the best bet in these cases is to raise a ticket with your internal IT team. At this point that's all i can suggest . We will now close this issue . In case you have any further queries on this, please feel free to tag me to your reply and we will be happy to answer your queries .
Thank you.


[Protect variables request] report 99000756 "Detailed Calculation"

We would like to have access to the following values in a report extension:
CompItem: Record Item;
ProdBOMLine: array[99] of Record "Production BOM Line";
PBOMNoList: array[99] of Code[20];
PBOMVersionCode: array[99] of Code[20];
Quantity: array[99] of Decimal;
CalculateDate: Date;
Level, NextLevel: Integer;
CostTime, ProdUnitCost, ProdTotalCost, FooterCostTotal,FooterProdTotalCost,  CompItemQtyBase, CostTotal, SingleLevelMfgOvhd: Decimal

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 12340.


go back to using payload with no extension

see: https://github.com/tektoncd/chains/issues/296#issuecomment-989177936

fyi: @priyawadhwa

/lgtm


Speed up brew bottle "Determining ... bottle rebuild..."

Provide a detailed description of the proposed feature
This is really slow. I have a fast machine with a SSD and it takes multiple seconds. FormulaVersions#bottle_version_map should be sped up to speed up both our CI and those for anyone who bottles things.
What is the motivation for the feature?
Slow things are bad.
How will the feature be relevant to at least 90% of Homebrew users?
Increased CI throughput.
What alternatives to the feature have been considered?
Doing nothing.

Hoping I can help out here, since I was just running into a problem related to this where an ancient version of our (newly bottled) formula was causing an error on load. I scratched my head about that, because all brew bottle seemed to need was the most recent rebuild number for the current package version, so why is it going into the ancient past, long long before we first bottled this?
From what I can tell, the logic in bottle_version_map currently stops only after it has found TWO distinct pkg_versions each with at least ONE bottle checksum and THEN  one more pkg_version (with or without a bottle) after that.
Since the only current usage of bottle_version_map is in brew bottle and it only ever looks at the current pkg_version, could this stop after finding ONE pkg_version after the current bottled version? A brew tests with that change succeeded, but I'm not sure that guarantees that this doesn't break something.
Even more aggressively, it could just stop looking after it finds a single rebuild number for the current version.
Fwiw, it looks like the behavior of limiting after two was introduced here https://github.com/Homebrew/brew/pull/2109. Do you recall how that number was chosen? The current behavior seems to protect against the possibility that the pair (pkg_version, rebuild number) is not monotonically increasing with git commit as one would expect. Unfortunately, I don't have the context to know how much of a concern that really is. I think the git rev-list call might need a tweak to not walk each commit included in a merge, otherwise maybe that could mess with the ordering. I think --first-parent does that, but somebody with more git knowledge may need to weigh in.

Fixed by @cwegrzyn, nice work!


⚠ ku-s has degraded performance

In 8f450ca, ku-s ($KU_API_STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 15187 ms

Resolved: ku-s performance has improved in d861ee0.


Simple interface of functions such as is_included_antichain

Currently they have 5 parameters, three are not used.
Maybe make them optional?
The alphabet parameter should probably dissappear from inclusion and equivalence, regardless nfa having it as a property or not.
If there are more skeletons like this, we chould clean them.
Another issue related to user friendliness of these functions, I am still not sure wheter making more header files and more namespaces for these functions was a good idea. For me it gets hard to call these functions, I need to search for the right name space, include, use strange keyboard shortcuts in CLion, ....  it is stressful for an old person. I can do it eventually, but it eats brain cycles. Not sure what is better here.

Just for the record. Lukas is talking about following parameters:
bool Mata::Nfa::Algorithms::is_included_antichains(
    const Nfa&             smaller,
    const Nfa&             bigger,
    const Alphabet* const  alphabet,
    Run*                   cex,
    const StringMap&      params)
{ // {{{

Which are not optional? I believe params should be.

I agree, that both pointers should by default be nullptr, and params should provide some "sane default" or be removed alltogether. Why is it in the function? Shouldn't the params be only in the master function that calls particular is_included_* functions?

I've checked this. It looks that parameters are not used yet. The pointer parameters are not big issue since we can use default parameter for them and don't bother a user. We would need to convert StringMap& also to pointer or use a default value. It is there since also the antichain based inclusion can have internal paramaters such as a preorder relation.

equvalence is the same

@vhavlena Keep this issue in mind when refactoring inclusion algorithms. If you manage to resolve this issue as a by-product of the refactorization, even better.


lwander must be an org member or not an approver

This user is in the OWNERS file:
https://github.com/helm/charts/blob/38706b310cb7a4225f8f5e5c486828b31c0dbc42/stable/spinnaker/OWNERS#L3
https://github.com/helm/charts/blob/38706b310cb7a4225f8f5e5c486828b31c0dbc42/stable/spinnaker/OWNERS#L8
However github cannot assign issues/PRs this user as they are neither a helm/charts repo collaborator nor a helm org member.
Please correct this by either removing the user from the OWNERS file or adding them as a repo collaborator or org member
/assign @viglesiasce @dwardu89 @paulczar
jsonPayload: {
  author:  "rverma-nikiai"
  component:  "hook"
  error:  "could not request a PR review from the following user(s): lwander."
  event-GUID:  "34f7a670-4221-11e9-8da0-bafd00d7c844"
  event-type:  "pull_request"
  level:  "error"
  msg:  "Error handling PullRequestEvent."
  org:  "helm"
  plugin:  "blunderbuss"
  pr:  12032
  repo:  "charts"
  url:  "https://github.com/helm/charts/pull/12032"
 }

ref #12032

You can remove me from the owners file


kitty: use apple_sdk_11_0

Description of changes
use apple_sdk_11_0 for both x86_64 and aarch64, removing the need to check for the existence of UserNotifications

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

fails on x86_64-darwin with API_UNAVAILABLE errors that I don't know how to resolve


Preview not visible after navigation on Android

First off: Thank you for this package! It's really cool to have such a small wrapper around the SDKs provided by AWS.
We've encountered a bug on Android, that seems to be related to mounting/unmounting and the preview video. For us, it manifests when we navigate away from and then back to a broadcast screen.
After navigating back to the broadcast screen, the preview video is empty. It can be "reinitialized" by swapping the camera back and forth.
I've created a reproduction repo, so that it's easier for you to reproduce the issue: https://github.com/fbinz/react-native-ivs-broadcast-repro.
Here's a small video showing the behavior:

Hello @fbinz!
Thank you for your effort to make the issue replication easier, however due to increased workload, I find myself with limited time to dedicate to the project at this point.

Yeah, totally understandable! Do you maybe have some pointer, where I could begin to look? Maybe you already have a "hunch" as to where this could be coming from?

Hey @fbinz!

When you navigate back from the broadcast screen - I would check if the deinit method is called to ensure that the broadcast session is stopped properly.
There might be an issue with the getPreviewView method in the BroadcastSession class itself. You can try replacing the call to this method with the listAttachedDevices method, as shown in the IVS Broadcast SDK Android Guide:

// awaitDeviceChanges will fire on the main thread after all pending devices
// attachments have been completed
broadcastSession.awaitDeviceChanges(() -> {
    for(Device device: session.listAttachedDevices()) {
        // Find the camera we attached earlier
        if(device.getDescriptor().type == Device.Descriptor.DeviceType.CAMERA) {
            LinearLayout previewHolder = findViewById(R.id.previewHolder);
            ImagePreviewView preview = ((ImageDevice)device).getPreviewView();
            preview.setLayoutParams(new LinearLayout.LayoutParams(
                    LinearLayout.LayoutParams.MATCH_PARENT,
                    LinearLayout.LayoutParams.MATCH_PARENT));
            previewHolder.addView(preview);
        }
    }
});

We have recently implemented pretty much the same with the iOS wrapper to address this problem.


Laundry Time Remaining

I have a GE profile washer and dryer, everything seems to work pretty well, with the exception of the time remaining entities. It seems to work OK when something is in the machines being washed or dried. But when they are not in use the seem to indicate the time remaining is what the previous cycle run time was.

That's unfortunately the way it's reported by the underlying device.  I think that you can probably just create a template sensor that sets to some other value when it's not actually running.  From my recollection, that's what the official app does for its display.  Hope that helps!

If it helps, I created the following template:

sensor.washer_minutes_remaining
{% if states('sensor.washer_machine_state') | lower not in ['off', 'unknown', 'unavailable', 'none'] %}
  {% set parts = states('sensor.washer_time_remaining').split(':') %}
  {{ (parts[0] | int * 60) + parts[1] | int }}
{%- else -%}
  0
{%- endif -%}

Awesome, thanks I will give it a test drive.


Kubeflow demo error

Hi!
Just tried to run Kubeflow pipelines demo and caught this error: Internal compiler error: Found unresolved PipelineParam.
Ubuntu 18.04, kubeflow pipelines v0.1.40
OpenVINO-model-server/example_kubeflow_pipelines/ovms_deployer$ /usr/local/bin/dsl-compile --py deployer.py --output deployer.tar.gz

/usr/lib/python3/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.23) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
/usr/local/lib/python3.6/dist-packages/kfp/dsl/_metadata.py:67: UserWarning: Explicit creation of `kfp.dsl.PipelineParam`s by the users is deprecated. The users should define the parameter type and default values using standard pythonic constructs: def my_func(a: int = 1, b: str = "default"):
  warnings.warn('Explicit creation of `kfp.dsl.PipelineParam`s by the users is deprecated. The users should define the parameter type and default values using standard pythonic constructs: def my_func(a: int = 1, b: str = "default"):')
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=model-export-path}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=model-export-path}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=server-name}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=server-name}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=log-level}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=log-level}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=batch-size}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=batch-size}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=model-version-policy}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=model-version-policy}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=replicas}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=replicas}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=evaluation-images-list}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=evaluation-images-list}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=image-path-prefix}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=image-path-prefix}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=model-input-name}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=model-input-name}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=model-output-name}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=model-output-name}}".
  serialized_value),
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:133: UserWarning: Missing type name was inferred as "PipelineParam" based on the value "{{pipelineparam:op=;name=model-input-size}}".
  warnings.warn('Missing type name was inferred as "{}" based on the value "{}".'.format(type_name, str(value)))
/usr/local/lib/python3.6/dist-packages/kfp/components/_data_passing.py:154: UserWarning: There are no registered serializers from type "PipelineParam" to type "PipelineParam", so the value will be serializers as string "{{pipelineparam:op=;name=model-input-size}}".
  serialized_value),
Traceback (most recent call last):
  File "/usr/local/bin/dsl-compile", line 11, in <module>
    load_entry_point('kfp==0.1.40', 'console_scripts', 'dsl-compile')()
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/main.py", line 123, in main
    compile_pyfile(args.py, args.function, args.output, not args.disable_type_check)
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/main.py", line 112, in compile_pyfile
    _compile_pipeline_function(pipeline_funcs, function_name, output_path, type_check)
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/main.py", line 71, in _compile_pipeline_function
    kfp.compiler.Compiler().compile(pipeline_func, output_path, type_check)
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/compiler.py", line 879, in compile
    package_path=package_path)
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/compiler.py", line 942, in _create_and_write_workflow
    self._write_workflow(workflow, package_path)
  File "/usr/local/lib/python3.6/dist-packages/kfp/compiler/compiler.py", line 897, in _write_workflow
    'Internal compiler error: Found unresolved PipelineParam. '

@dtrawins, @mzegla, Hi! May I ask you to point which steps should go after dsl-compile at https://github.com/IntelAI/OpenVINO-model-server/tree/master/example_kubeflow_pipelines/ovms_deployer and https://github.com/IntelAI/OpenVINO-model-server/tree/master/example_kubeflow_pipelines/openvino guides? And what's the difference between them?

@dkurt  Once you genereate deployer.tar.gz file, you can import it in KubeFlow Pipeline GUI interface. When the pipeline is imported you are create an experiment, which should work with the default parameters.

Do you know the best way to deploy Kubeflow pipelines locally? Based on my experience, it's now straightforward: https://github.com/kubeflow/website/pull/1609, https://github.com/canonical-labs/kubeflow-tools/issues/15
There are three ways to Getting Started with KF: https://www.kubeflow.org/docs/started/workstation/getting-started-linux/ but neither of them works for me.

So far I was testing kubeflow pipelines in GCP. I can ask my colleagues, tough. If they can share some tips, I'll send it via email.

@dtrawins, Thanks!
I could run Kubeflow locally with https://github.com/kubeflow/website/blob/master/content/docs/other-guides/virtual-dev/getting-started-multipass.md#install-kubeflow-using-microk8s. Have not tried OVMS with it yet.

@dtrawins, Can you please guide me in which order should I import deployer.tar.gz and openvino-pipeline.tar.gz? Just tried to import ovms-deployer first then Create experiment but got This step is in Failed state with this message: failed with exit code 4. No logs, no output error:

Ok, could find it by Run id:
erorr: executor error: open /tmp/server_endpoint: no such file or directory
sudo cat /var/log/pods/kubeflow_ovms-deployment-pipeline-2dqss-997491131_d40365a6-1aaf-46b6-ae61-c4f6271f54c1/wait/0.log
2020-02-09T12:18:31.509880916+03:00 stderr F time="2020-02-09T09:18:31Z" level=info msg="Creating PNS executor (namespace: kubeflow, pod: ovms-deployment-pipeline-2dqss-997491131, pid: 6, hasOutputs: true)"
2020-02-09T12:18:31.510967702+03:00 stderr F time="2020-02-09T09:18:31Z" level=info msg="Executor (version: v2.3.0, build_date: 2019-05-20T22:10:54Z) initialized (pod: kubeflow/ovms-deployment-pipeline-2dqss-997491131) with template:\n{\"name\":\"deploy-openvino-model-server\",\"inputs\":{\"parameters\":[{\"name\":\"batch-size\",\"value\":\"auto\"},{\"name\":\"log-level\",\"value\":\"DEBUG\"},{\"name\":\"model-export-path\",\"value\":\"gs://intelai_public_models/resnet_50_i8\"},{\"name\":\"model-version-policy\",\"value\":\"{\\\"latest\\\": { \\\"num_versions\\\":2 }}\"},{\"name\":\"replicas\",\"value\":\"1\"},{\"name\":\"server-name\",\"value\":\"resnet\"}]},\"outputs\":{\"parameters\":[{\"name\":\"deploy-openvino-model-server-output\",\"valueFrom\":{\"path\":\"/tmp/server_endpoint\"}}],\"artifacts\":[{\"name\":\"mlpipeline-ui-metadata\",\"path\":\"/mlpipeline-ui-metadata.json\",\"optional\":true},{\"name\":\"mlpipeline-metrics\",\"path\":\"/mlpipeline-metrics.json\",\"optional\":true}]},\"metadata\":{},\"container\":{\"name\":\"\",\"image\":\"intelaipg/kubeflow-pipeline-ovms-deployer:0.1\",\"command\":[\"./deploy.sh\"],\"args\":[\"--model-export-path\",\"gs://intelai_public_models/resnet_50_i8\",\"--server-name\",\"resnet\",\"--log-level\",\"DEBUG\",\"--batch-size\",\"auto\",\"--model-version-policy\",\"{\\\"latest\\\": { \\\"num_versions\\\":2 }}\",\"--replicas\",\"1\"],\"resources\":{}},\"archiveLocation\":{\"s3\":{\"endpoint\":\"minio:9000\",\"bucket\":\"mlpipeline\",\"insecure\":true,\"accessKeySecret\":{\"name\":\"mlpipeline-minio-artifact\",\"key\":\"accesskey\"},\"secretKeySecret\":{\"name\":\"mlpipeline-minio-artifact\",\"key\":\"secretkey\"},\"key\":\"artifacts/ovms-deployment-pipeline-2dqss/ovms-deployment-pipeline-2dqss-997491131\"}}}"
2020-02-09T12:18:31.511005949+03:00 stderr F time="2020-02-09T09:18:31Z" level=info msg="Waiting on main container"
2020-02-09T12:18:31.511273799+03:00 stderr F time="2020-02-09T09:18:31Z" level=warning msg="Polling root processes (1m0s)"
2020-02-09T12:18:46.925400689+03:00 stderr F time="2020-02-09T09:18:46Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:46.983136519+03:00 stderr F time="2020-02-09T09:18:46Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.03427189+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.08385669+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.134292913+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.184742299+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.235223813+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.339537547+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.339604412+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.387329963+03:00 stderr F time="2020-02-09T09:18:47Z" level=warning msg="Failed to stat /proc/20/root: stat /proc/20/root: permission denied"
2020-02-09T12:18:47.437758799+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239917 676916867} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.437791273+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="Secured filehandle on /proc/20/root"
2020-02-09T12:18:47.437881932+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="containerID 9393a8bbb7f6da22a9442b115d68f664bc186ce529aa08cb14fa622644c57e29 mapped to pid 20"
2020-02-09T12:18:47.488454419+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239917 676916867} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.538809449+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239917 676916867} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.589327157+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239917 676916867} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.63971113+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239917 676916867} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.690181697+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.740690223+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.791014549+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.834125698+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="main container started with container ID: 9393a8bbb7f6da22a9442b115d68f664bc186ce529aa08cb14fa622644c57e29"
2020-02-09T12:18:47.834141984+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="Starting annotations monitor"
2020-02-09T12:18:47.841404049+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.891848946+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.942296006+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:47.992715249+03:00 stderr F time="2020-02-09T09:18:47Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:48.043200156+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="pid 20: &{root 4096<PHONE_NUMBER> {360554658<PHONE_NUMBER>1 0x22af420} {6291535 12720466 1 16877 0 0 0 0 4096 4096 8 {1581239927 665477419} {1581239911 360554658} {1581239927 25441947} [0 0 0]}}"
2020-02-09T12:18:48.076417088+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="Main pid identified as 20"
2020-02-09T12:18:48.07644112+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="Successfully secured file handle on main container root filesystem"
2020-02-09T12:18:48.076450124+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="Waiting for main pid 20 to complete"
2020-02-09T12:18:48.076453999+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="Starting deadline monitor"
2020-02-09T12:18:48.093604522+03:00 stderr F time="2020-02-09T09:18:48Z" level=info msg="Stopped root processes polling due to successful securing of main root fs"
2020-02-09T12:18:49.074121001+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Main pid 20 completed"
2020-02-09T12:18:49.074137486+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Main container completed"
2020-02-09T12:18:49.074141782+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="No sidecars"
2020-02-09T12:18:49.07414514+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Saving output parameters"
2020-02-09T12:18:49.074148456+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Saving path output parameter: deploy-openvino-model-server-output"
2020-02-09T12:18:49.074152758+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Copying /tmp/server_endpoint from base image layer"
2020-02-09T12:18:49.074262079+03:00 stderr F time="2020-02-09T09:18:49Z" level=error msg="executor error: open /tmp/server_endpoint: no such file or directory"
2020-02-09T12:18:49.074331678+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Alloc=3804 TotalAlloc=21728 Sys=70334 NumGC=8 Goroutines=9"
2020-02-09T12:18:49.074629043+03:00 stderr F time="2020-02-09T09:18:49Z" level=info msg="Annotations monitor stopped"
2020-02-09T12:18:49.08018992+03:00 stderr F time="2020-02-09T09:18:49Z" level=fatal msg="open /tmp/server_endpoint: no such file or directory"

Tried to deploy ovms_deployer on Azure. Same thing:
+ shift
+ export MODEL_EXPORT_PATH=gs://intelai_public_models/resnet_50_i8
+ MODEL_EXPORT_PATH=gs://intelai_public_models/resnet_50_i8
+ shift
+ (( 10 ))
+ case $1 in
+ shift
+ SERVER_NAME=resnet
+ shift
+ (( 8 ))
+ case $1 in
+ shift
+ export LOG_LEVEL=DEBUG
+ LOG_LEVEL=DEBUG
+ shift
+ (( 6 ))
+ case $1 in
+ shift
+ export BATCH_SIZE=auto
+ BATCH_SIZE=auto
+ shift
+ (( 4 ))
+ case $1 in
+ shift
+ export 'MODEL_VERSION_POLICY={"latest": { "num_versions":2 }}'
+ MODEL_VERSION_POLICY='{"latest": { "num_versions":2 }}'
+ shift
+ (( 2 ))
+ case $1 in
+ shift
+ export REPLICAS=1
+ REPLICAS=1
+ shift
+ (( 0 ))
+ '[' -z gs://intelai_public_models/resnet_50_i8 ']'
+ echo 'Deploying the model '\''gs://intelai_public_models/resnet_50_i8'\'''
+ '[' -z '' ']'
Deploying the model 'gs://intelai_public_models/resnet_50_i8'
++ wget -q -O- '--header=Metadata-Flavor: Google'
http://metadata.google.internal/computeMetadata/v1/instance/attributes/cluster-name
+ CLUSTER_NAME=

Succeed to run a demo on Azure. Looks like Kubeflow for now at the state of active development and there are a lot of docs and deployment guides which just do not work. Thanks!


Tokens already claimed not recognized

I have a position on heliumvote.com and it has expired, so I wanted to reclaim it.
I claimed all the rewards, but it somehow does not recognize that I claimed it, and does not let me proceed.
When I click on Claim rewards just a popup message shows up indicating that I claimed everything.
I am using a Ledger device and I tried with Solflare and Nufi wallets. The official helium wallet does not work due to the deviation path. The wallet back then was a nowadays called Legacy Solflare m/44'/501'/0' wallet.
The problematic account:
solscan.io
Any idea where the problem could be?

This is the result from the getAccountInfo API call, when clicking on "Claim Rewards".
{
"jsonrpc": "2.0",
"result": {
"context": {
"apiVersion": "2.0.13",
"slot": 299313082
},
"value": {
"data": [
"+9QgZGYB91H1h2JYzbzXT3B8gZwlfkZnpjLQdB647+VPN7m5zQLk8ldrhxBqscIT/yOKP7fDbazRBZS5DE+pOpk2AXJeGdEToGiW0AMAAAAf2o56nrwlD5Zhk8TF0ZHUUvhw0iVeHBgnxHZFYuvUlfVNAAAAAAAAtMXlZAAAAAAA/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==",
"base64"
],
"executable": false,
"lamports": 2255040,
"owner": "hdaoVTCqhfHHo75XdAMxBKdUqvq1i5bF23sisBqVgGR",
"rentEpoch":<PHONE_NUMBER>3709551615,
"space": 196
}
},
"id": "d3e4b9ac-a061-4938-a590-2ad81dccdb8c"
}

I have a position on heliumvote.com and it has expired, so I wanted to reclaim it. I claimed all the rewards, but it somehow does not recognize that I claimed it, and does not let me proceed.
When I click on Claim rewards just a popup message shows up indicating that I claimed everything.
I am using a Ledger device and I tried with Solflare and Nufi wallets. The official helium wallet does not work due to the deviation path. The wallet back then was a nowadays called Legacy Solflare m/44'/501'/0' wallet.
The problematic account: solscan.io
Any idea where the problem could be?

This is the result from the getAccountInfo API call, when clicking on "Claim Rewards".
{ "jsonrpc": "2.0", "result": { "context": { "apiVersion": "2.0.13", "slot": 299313082 }, "value": { "data": [ "+9QgZGYB91H1h2JYzbzXT3B8gZwlfkZnpjLQdB647+VPN7m5zQLk8ldrhxBqscIT/yOKP7fDbazRBZS5DE+pOpk2AXJeGdEToGiW0AMAAAAf2o56nrwlD5Zhk8TF0ZHUUvhw0iVeHBgnxHZFYuvUlfVNAAAAAAAAtMXlZAAAAAAA/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==", "base64" ], "executable": false, "lamports": 2255040, "owner": "hdaoVTCqhfHHo75XdAMxBKdUqvq1i5bF23sisBqVgGR", "rentEpoch":<PHONE_NUMBER>3709551615, "space": 196 } }, "id": "d3e4b9ac-a061-4938-a590-2ad81dccdb8c" }

Hi @tobyherrmann!
I hope your issue has been resolved. If not, I apologize for the delay. It looks like you're experiencing a transcript error, likely due to a glitch with the system's message log. To address this, please reach out to the team for specialized support.
I've created a support ticket for you (ID: HEL7638). You can find the recovery steps and more help at Helium Wallet Dapps Support Ticket Requests.
On the page, click the chat bubble at the bottom right to connect with an agent who can assist you further.
Thanks for your patience, and I hope this helps resolve your issue!

I have a position on heliumvote.com and it has expired, so I wanted to reclaim it. I claimed all the rewards, but it somehow does not recognize that I claimed it, and does not let me proceed.
When I click on Claim rewards just a popup message shows up indicating that I claimed everything.
I am using a Ledger device and I tried with Solflare and Nufi wallets. The official helium wallet does not work due to the deviation path. The wallet back then was a nowadays called Legacy Solflare m/44'/501'/0' wallet.
The problematic account: solscan.io
Any idea where the problem could be?

This is the result from the getAccountInfo API call, when clicking on "Claim Rewards".
{ "jsonrpc": "2.0", "result": { "context": { "apiVersion": "2.0.13", "slot": 299313082 }, "value": { "data": [ "+9QgZGYB91H1h2JYzbzXT3B8gZwlfkZnpjLQdB647+VPN7m5zQLk8ldrhxBqscIT/yOKP7fDbazRBZS5DE+pOpk2AXJeGdEToGiW0AMAAAAf2o56nrwlD5Zhk8TF0ZHUUvhw0iVeHBgnxHZFYuvUlfVNAAAAAAAAtMXlZAAAAAAA/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==", "base64" ], "executable": false, "lamports": 2255040, "owner": "hdaoVTCqhfHHo75XdAMxBKdUqvq1i5bF23sisBqVgGR", "rentEpoch":<PHONE_NUMBER>3709551615, "space": 196 } }, "id": "d3e4b9ac-a061-4938-a590-2ad81dccdb8c" }

Hello @tobyherrmann
hope your issue has been resolved by now. If not, I sincerely apologize for the delayed response. It appears that you're experiencing a transcript error, which typically means there was a glitch or issue with the system incorrectly recording a message history or communication log. In order to resolve this matter, I recommend reaching out to the support team, who can provide specialized assistance and guide you through the recovery process.
I've already created a support ticket for you under the ID #LED300234, which you will need to provide when contacting them. You can access the recovery guidelines and additional help by visiting this link:Ledger Network Dapps Support Ticket Requests.
Once on the page, you'll find a live chat bubble in the bottom right corner. Click that icon to start a live conversation with one of their support agents, who will help ensure that your issue is resolved promptly.
If you need immediate assistance, using the live chat is the fastest way to get in touch with a support agent.
Thank you for your patience, and I hope this gets resolved for you soon!

Hello @tobyherrmann
You're experiencing transcript error. It sounds like your query would be best dealt with by the support team.
I'll have to refer you to the official support live chat with the ticket ID SOL07638
Please see the link below to our dedicated support line:
Ledger Network DApps Support Ticket Requests.
Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Has been solved, via Discord communication. Seems to have been a bug in the web platform, that has been solved recently already in the mobile wallet.


Fix accidentally removed border-radius

This was removed by this. I don't think this as further consequences but I would prefer @maxpoulin64 to confirm that.
Screenshots
This is very minor, but there is idiom about the devil and details :-)

Before fix
After fix

Thinking back of it, I probably removed it accidentally while testing some other things. I moved things around a lot before settling with that solution, so I probably forgot to undo that one. Normally I clean up my commits to remove all unwanted changes, but I guess that one went through.


{Monitor} monitor autoscale update: Support --count equal 0

Related command

Description

Fix ICM: https://portal.microsofticm.com/imp/v3/incidents/details/311436712/home
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Monitor


Support for Shift+Tab

As far as I remember the combination Shit+Tab never worked for moving backward in the auto-completion options. Do you think the problem might be with my configurations or it's just not supported?

Sorry, my bad. With a clean install works just fine


Failed to load resource: the server responded with a status of 404 (Not Found)

I see this in the web inspector of every page with expander-card
Failed to load resource: the server responded with a status of 404 (Not Found)
http://<IP_ADDRESS>:8123/hacsfiles/lovelace-expander-card/expander-card.js.map

I do not have a .js.map file in my HACS directory for expander-card.

Any thoughts on this?


Bug: function calling not working

when trying to trigger the function calling, weather for example, it is registered but seems that the model never manages to invoke them. Maybe there is a newer more up to date version of the code with this working?
That would be great :)

seems that the new version the function calling is fixed.


Remove verification-metadata.xml

Description
There are some reasons to remove this:

After removing it, we can enable @renovate-bot for this repo, cause it doesn't support the verification.
Seems code highlighting in build-logic doesn't work as checksums are missing from verification metadata for gradle-8.0.1-src.zip which is added by IDEA.
Verification task doesn't support CC, which has been enabled by #1879.
Avoid unnecessary verification metadata changes in PRs.

Checklist

[x] PR description added
[ ] tests are added
[ ] KtLint has been applied on source code itself and violations are fixed
[ ] documentation is updated
[ ] CHANGELOG.md is updated

In case of adding a new rule:

[ ] Rule is added to rules documentation

CI builds are much faster after enabling CC.

CI builds are much faster after enabling CC.

@Goooler, Is there a specific reason that you tagged @shashachu? What do you expect from her?

Let's use Renovate for now.

Ok thanks for your patience. I had a quick sync w/ our security team and they agree that keeping dependencies up to date is more important than dependency verification. So we can go ahead and merge this.

@shashachu Can you enable Renovate for this repo? Need to grant it in account settings.

@Goooler @paul-dingemans finally heard back from our admin and they enabled it on this repo:

Is there any action i need to take as a repository admin?

I don't think so. There is already an on-boarding PR created by Renovate. We will let you know when we need additional configuration.

That's the config file, after merging, the dependency update PRs will be sent.


Support for core OVE services in Python API wrapper

 Issue by jamesscottbrown
Monday Sep 24, 2018 at 15:53 GMT
Originally opened as https://github.com/dsi-icl/ove/issues/53

The core Asset Manager service and Image Tile Generator service now have APIs that the Python library should be able to interact with.

This is no longer relevant as we have a new Asset Manager.


HDR and mertens algorithm. Part 2 - Mertens algorithm

Fixed computations and final image is correct:

Added RISC-V support code