[Core][Bug] Unbalanced base predictions fail to reshape forreconciler_args

Currently, HierarchicalForecast methods require the base predictions to be "balanced", i.e., all the predictions must be available for all the series and forecast creation dates.
If the base forecast inputs are not balanced, the following reshapes fail:
y_hat = Y_hat_df[model_name].values.reshape(len(S_df), -1).astype(np.float32)

y_insample = Y_df['y'].values.reshape(len(S_df), -1).astype(np.float32)

The is_balanced parameter is already available, but a Raise.Exception to check the input characteristics can help.

I've seen this issue too - this also ties in to #290 - it seems the checks / required data should be method-specific.


AYS API: GetServiceByName returns service if you filter on incorrect parent

Installation information

jumpscale version:
8.2
operating system:
Ubuntu

Detailed description
If you try to get service by name from ays and give it an incorrect parent in the query params, it returns the service and ignores the incorrect filtering instead of 404.
Steps to reproduce
GET http://<IP_ADDRESS>:5000/ays/repository/objstor/service/gateway/mygw?parent=node.g8os!5254003456
Where node '5254003456' doesn't exist but mygw exists and has another parent node. The api returns the mygw service normally.
Relevant stacktraces

I don't see parent as query param in getServiceByName, but It's there is listServicesByRole https://github.com/Jumpscale/ays9/blob/master/JumpScale9AYS/ays/server/apidocs/api.raml#L537


feat(protocol-designer): define liquids banner to assign liquids toolbox

closes AUTH-1002
Overview
Add define liquids banner when there are no liquids defined

Test Plan and Hands on Testing
Create a protocol and go to add a liquid to a labware when there is no liquid defined. Then see that the banner renders correctly when selecting wells. click on the button in the banner and it should open the define liquids modal
Changelog

add define liquids banner
add disabled state to dropdownMenu
render defineLiquids modal if the button is clicked in the banner

Risk assessment
low

thread about Banner's padding
https://opentrons.slack.com/archives/C07E9T2NAQK/p1730316440382139

thread about Banner's padding https://opentrons.slack.com/archives/C07E9T2NAQK/p1730316440382139

is there something i should change about the banner in the PR @koji ?

thread about Banner's padding https://opentrons.slack.com/archives/C07E9T2NAQK/p1730316440382139

is there something i should change about the banner in the PR @koji ?

Banner's padding is 8px but the design uses 12px for the space between icon and the outline. So, need to add  iconMarginLeft={SPACING.spacing4}


Add encoding argument for directives

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 22 (81.82%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-18.3%) to 81.684%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mkdocs_include_markdown_plugin/event.py
17
21
80.95%

Totals

Change from base Build<PHONE_NUMBER>:
-18.3%

Covered Lines:
611

Relevant Lines:
748

💛  - Coveralls


UI Layer needs collision flags

UI layer needs its own collision flags or some kind of way to track interaction. Maybe remove the flag from all UI and just do rect collision?

This will not be added, all collision on the UI layer should be done by hand.


fix: Handle missing fetch implementation

There is a lake of information in replicate documentation regarding nodejs integration:
https://replicate.com/docs/get-started/nodejs
This fix will help to solve "ReferenceError: fetch is not defined" by giving user a way to provide fetch implementation in options object.

Thanks, @plustokens. This matches the documented behavior, where the initializer has a configurable fetch option.

A quick work that worked for me is to use node v18. ie. nvm install 18.

A quick work around that worked for me is to use node v18. ie. nvm install 18.

There are other reasons that someone might want to configure which fetch to use. Testing is one example. Another is to wrap fetch and add custom headers / caching / retry behavior.


GTK3 and GTK4 applications fail to display Noto CJK fonts.

Describe the bug
Noto CJK fonts show up as either hollow or filled squares in GTK applications, and cause Gnome Font Viewer to segfault when selected.
Steps To Reproduce
Steps to reproduce the behavior:

Activate a system configuration with fonts.fonts including noto-fonts-cjk-sans.
Open gnome-font-viewer
Select Noto Sans CJK JP

Expected behavior
The font displays normally. Gnome Font Viewer does not segfault.
Screenshots

Noto Sans displays properly,

Noto Sans CJK fonts do not.
Additional context

Log from `gnome-font-viewer`:
(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.435: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Bold 9.9990234375'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.435: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.435: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.436: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Bold 9.9990234375'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.436: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.436: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 9.9990234375'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 9.9990234375'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.437: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.542: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.542: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.542: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.543: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.543: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.543: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.548: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.548: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.548: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.549: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.549: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.549: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.551: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.551: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.551: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.552: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.552: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:47.552: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.159: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.161: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.163: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.165: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.167: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.169: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.169: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.169: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.170: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.170: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.170: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.171: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.171: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.172: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.172: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK HK Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.172: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.172: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.175: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.175: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.175: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.176: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.176: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.176: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.406: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.408: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.410: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.412: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.414: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.416: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.417: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.417: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.417: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.418: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.418: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.418: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.419: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.419: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.419: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.420: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.420: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.420: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.421: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.421: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.421: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.421: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.421: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.422: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK KR Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.423: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.425: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.427: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.429: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.430: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.430: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.430: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.431: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.431: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.431: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.432: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.432: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.432: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.432: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.433: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.433: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.434: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK SC Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.436: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.437: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.437: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.437: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.438: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.438: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.438: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Bold 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.439: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Heavy 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.441: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.443: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Medium 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.445: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Semi-Light 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.447: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK TC Thin 96'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:18:52.449: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 8.3330078125'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: scaled_font status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans CJK JP 8.3330078125'

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: font_face status is: file not found

(gnome-font-viewer:3025619): Pango-WARNING **: 13:20:08.814: scaled_font status is: file not found

(gnome-font-viewer:3025619): GLib-GObject-CRITICAL **: 13:20:17.774: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
Segmentation fault (core dumped)

Notify maintainers
Gnome: @bobby285271 @hedning @dasj19 @maxeaubrey + @7c6f434c
Noto Fonts CJK Sans: @Mathnerd314 @emilazy
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.8, NixOS, 22.11 (Raccoon), 22.11.20221130.596a8e8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - nixpkgs: `/nix/store/qwgw2b19ga8dr7c6wfpd6p87bdjyrnha-source`

We have a test for this: nixosTests.noto-fonts, would you mind building the test to see if it reproduce?

The output on 596a8e8 is shown below:

We have a test for this: nixosTests.noto-fonts, would you mind building the test to see if it reproduce?

Apologies, I can't seem to figure out how to do that! I ran the Reproduce locally command from Hydra, and it seems to have just output a nix store path. Inside is nix-support/hydra-{aggregate-constituents,build-products}.

nix-build '<nixos>' -A nixosTests.noto-fonts (or <nixpkgs> depending on the name of your channel), the test runs gedit, a gtk application to see if noto fonts correctly renders, this would help us isolating the problem.

Just ran that command (without fetching the exact same image you posted from hydra) and the build failed due to a test suite from python-aiohttp:
error: builder for '/nix/store/i4hbjzgswmxq89nvaycajqxs4a2jf76v-python3.10-aiohttp-3.8.3.drv' failed with exit code 1;
       last 10 log lines:
       > XFAIL test_web_server.py::test_unsupported_upgrade[pyloop]
       >   The behavior of C-extensions differs from pure-Python: https://github.com/aio-libs/aiohttp/issues/6446
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urldecoded_route]
       >   Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urldecoded_route_with_regex]
       >   Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urlencoded_route]
       >   Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > ERROR test_web_sendfile_functional.py::test_static_file_if_none_match[no_sendfile-pyloop-additional_etags1-]
       > = 2550 passed, 17 skipped, 6 deselected, 10 xfailed, 1 error in 234.52s (0:03:54) =
       For full logs, run 'nix log /nix/store/i4hbjzgswmxq89nvaycajqxs4a2jf76v-python3.10-aiohttp-3.8.3.drv'.

Sorry that this is being difficult.

That looks like a flaky test, have you tried updating your channel?

The test works fine.

Then double check if your gnome-font-viewer comes from the same channel, maybe it's installed by nix-env and is outdated.

It does. And the problem is not just with gnome-font-viewer, it's my entire computer. GNOME panel, GNOME shell, GNOME text editor, GNOME terminal, wxWidgets applications, everything GTK has this issue.

I have no idea with this now, but as the tests do work, I would not blame this to gtk. Could it be offending fontconfig settings or else?

The fonts section of my system configuration:
  fonts = {
    fonts = with pkgs; [ noto-fonts noto-fonts-cjk-sans twemoji-color-font ];

    fontconfig.defaultFonts = {

      monospace = [ "Noto Sans Mono CJK JP" ];

      sansSerif = [ "Noto Sans CJK JP" ];

    };

    fontDir.enable = true;
  };

Everything has worked fine in the past before upgrading to 22.11.

Do you have the environment variable $LD_LIBRARY_PATH set? It could cause applications to load wrong libraries.

The only thing in $LD_LIBRARY_PATH is pipewire's jack library; I'm not overriding anything.

You mentioned that nix run nixos#<packageName> fails, would you mind trying nix run github:NixOS/nixos-22.11#gnome.gnome-font-viewer.

Yes, nix run github:NixOS/nixpkgs/nixos-22.11#gnome.gnome-font-viewer also fails.

What about LC_ALL=en_US.UTF-8 nix run github:NixOS/nixpkgs/nixos-22.11#gnome.gnome-font-viewer, I'm genuinely confused by what I'm seeing.

(to get around having to use --impure I entered a shell first)
❯ nix shell github:NixOS/nixpkgs/nixos-22.11#gnome.gnome-font-viewer
❯ LC_ALL=en_US.UTF-8 gnome-font-viewer

Exhibits the same behaviour.

Can you post you full configuration or at least the relevant parts? I currently have no way to reproduce this issue and the back and forth attempts are obviously deficient.

https://github.com/Prism019/prism.home.arpa contains my NixOS configuration.
I check it out with nixos-rebuild test --flake .#ristaccia

nit pick: release-22.11 is the equivalent of master for 22.11, you should use nixos-22.11 instead.
give me some time to look into it.

Found nothing suspicious, could it be leftover gtk configurations from old installations, normally these kind of issues can be isolated by testing with freshly created users.

Clearing ~/.cache/fontconfig fixed it. I'm a bit confused as to why that didn't happen automatically at some point through the several system rebuilds I've done over the past few days. Either way, good that it's finally working now.


Upgrade to newer kerberos libraries

What is the feature request? What problem does it solve?
At the moment we use extremely old libraries for kerberous auth.
https://mvnrepository.com/artifact/org.springframework.security.kerberos/spring-security-kerberos-web/1.0.1.RELEASE
It hasn't been update in 8 years.
It depends on classes in the JDK that aren't easily accessible in JDK 17 onwards.
People online say that we should migrate to apache kirby: https://stackoverflow.com/a/69479644/6401281
Suggested solution
Migrate to apache Kirby or a similar framework (https://github.com/bedrin/kerb4j)

It does seem we have 2 optoins
A) Either adopt the latest version of spring security kerberos web by compiling and releasing it ourselves.
B) Adopt https://github.com/bedrin/kerb4j . It does have spring integration and although there are not updates in last year . It's still more recently updated than the spring web and also the maintainer has stated that there are not major issues.
So I'd recommend going with kerb4j. I haven't tried it out yet to see how seamless and easy the integration is (hopefully just renaming a few packages and upgrade gradle manifest). But at worst case we. should be able to do it in 2 or 3 days even if we hit some issues.

Triaged. Closed as being already resolved.


CocoaPods versio 2.2.1

When install sugar record 2.2.1 to iOS application, cocoapods return error.
The platform of the target xxxx (iOS 8.0) is not compatible with SugarRecord/CoreData (2.2.1), which does not support ios.

True, I get this also:
[!] The platform of the target XXXXX (iOS 8.3) is not compatible with SugarRecord/CoreData (2.2.1), which does not support ios.
On a side note, if I drop to 2.1.9, it works, but Realm frameworks are still present - is this expected?

Are you using Carthage?

No, not at all, pods only.
platform :ios, '8.3'
use_frameworks!

target 'XXXXX' do

pod 'SugarRecord/CoreData', '2.2.1'

end

@VladislavJevremovic &@Koranda , it should be solved in 2.2.2
https://github.com/pepibumur/SugarRecord/pull/203

Thanks a bunch, works like a charm now! Cheers!

Thanks, it works greate

Nice, thanks for reporting :)


[Request] Heavy Traffic find alternate path. + Desenate Main roads

These two kind of go hand in hand.
One issue I see a lot in every city I've made thus far, is I can have many a means for traffic to get from point A to point B, but even with all these extra options, most traffic ends up focusing on a single road. This becomes an issue when that single road ends up being a two way one lane, or a two lane road.
Case in point, my last city I had a small residential area with a two way one lane road cutting through it and split off into other areas that went from a main 3 lane road, and on the other side a 2 lane. Beside it just a little ways ahead there is a 'main' 2 lane road. But because that road was further down the road a.k.a the next intersection, the 'shortest' travel time from the 2 lane, to the 3 lane ended up being my single lane road, causing a huge traffic jam that could only be fixed by deleting one end of the road so the whole area became dead-end streets.
It would be nice if the AI took road size as a priority to travel along to get from point a to point b, and only if the traffic starts getting backed up, start using the smaller side roads to find alternate clear paths even if said paths may take them a little out of the way.
This may help clear up a lot of the common road jams I see and fix the need to rely on a lot of these 'tricks' I see in city fixer videos with all these cars piling up on a single road ignoring all the other roads available unless its the end destination.
Because I don't know about you, but if I see traffic at a near standstill and there's a perfectly good road to my side that I know will still get me where I'm going I'm not going to sit and wait for traffic to maybe start moving, I'm taking that side road.

We could potentially achieve this by adding a penalty based on road category:

Small roads: 10 points
Medium roads: 5 points
Large roads: 2 points
Highways: 0 points

That way traffic would have added incentive to use bigger roads.

That would be great, but also just a means to aid against traffic jams, if away if cars start backing up that new ones pick a different path?  like maybe a check that cars have been in a section of road for X time, find the next shortest path.
It's just annoying having all these roads to offer several means to get to places but they mostly all go ignored due to the ai always picking the shortest path to an area.

TMPE already includes that sort of thing, I think it's part of the Advanced Vehicle AI. checks...
Yup, see: https://tmpe.viathinksoft.com/wiki/index.php?title=Advanced_Vehicle_AI#Road_usage_optimization
Thing is the pathfinder will still generally want to find the fastest route, and if that's a small road that provides a shortcut then traffic will use it like IRL unless you encourage it otherwise by refactoring your road design or even just ensuring faster speed limit on the bypass road.
That being said, I do think TM:PE could add some improvements in this respect (like the aforementioned road-category penalties). Also there needs to be a clearer distinction between traffic density vs. traffic congestion. You could have high density of traffic that's still moving normally (little or no disruption to traffic flow), vs. low density traffic that's causing congestion (long wait times).

One other thing we could do - add a de-pentalty buff to "priority routes". That would give user direct way to say "I want traffic using this road".

BTW, you can also use district policies to keep heavy traffic out - Heavy Traffic Ban in particular.

The problem is that paths are pre-calculated. Advanced Vehicle AI takes the current traffic situation into account but the statistics used to find the fastest route might be already outdated when a vehicle finally reaches a critical point. At that time it is not possible for a vehicle to deviate from its route (except for DLS, which is able to select a faster lane, but not a different segment).
Because paths are pre-calculated we can only use traffic statistics which are accumulated and averaged over a large time span (~5 minutes). If we dialed the time resolution up (say for example, to 1 minute) we would start seeing feedback effects where either one or the other road would either be jammed or completely empty.
In that sense, your idea to add a priorization system for roads would have exactly the opposite effect that you would like to achieve. It would essentially force all traffic to ultimately prefer large roads which would cause massive traffic problems.
Since we are unable to use statistics with a high time resolution, we can only count on heavy randomization which comes with a certain drawback, namely that cars sometimes take routes that seem unlogical from an external point of view.

Sorry to say, but for me that's a "wontfix".

If vehicles do not use your main road this for sure has a reason:

Try to set the TrafficCostFactor (in TMPE_GlobalConfig.xml) to a higher value. Wait a few minutes. Are cars using the main road now?
If not: Check lane connections, lane arrows pointing to the main road and on the main road itself. Are vehicles able to enter and exit the main road as you intend?
If yes: Count the number of intersections vehicles have to pass in order to reach the main road and get back to their destination. Try to remove as much junctions as possible. Does that help?
If no: Did you set appropriate speed limits on the main road and on the side roads? Usually, you should set a higher speed limit on the main road. Does it help?
If no: Check if any vehicle restrictions apply or if you need to set up new restrictions. Does it help?
If no: Check for global vehicle restrictions, like the old town policy. It heavily affects every road such that vehicles won't perform detours at all. Try to deactivate it.
If nothing helps: Some other mods are incompatible with TMPE and prevent TMPE from collecting traffic statistics. Without those statistics it's impossible for TMPE to improve path-finding.

TODO: Add above comment to an FAQ page somewhere.


Save package without Modelica library

The actual version a0b05eb contains parts of the Modelica standard library. This effect may have been caused by saving the package by "Save Total" in Dymola. In order to remove Modelica the following steps shall be performed:

Open Dymola
Open Modelica Standard Library (double click)
Load your package DistrictHeating
Use "Save As" to re-store your package

Fixed with new version 5d5420ce25b2ae32b7c8846628eb3d930f1436b0


SCRIPT element should provide :text() behaviors

The SCRIPT element is valid HTML, the content of which should be accessible via text() method. Similarly, Element::select("script:contains(somethinguseful)") is expected to work. Finally, remember script type attribute could be application/text. You do NOT have to "parse" the content of the script tag, simply treat it as cdata and expose it to the Element API so we can do simple and important work without having to require a JS parsing lib.

hope fix  script:contains(some-js-here) !  the code in Evaluator.java, ContainsText,ContainsOwnText,Matches,MatchesOwn  matches method like this:
@Override
public boolean matches(Element root, Element element) {
        return (("script".equalsIgnoreCase(element.tagName()) ? element.html() : element.ownText()).toLowerCase().contains(searchText));
    }

I fixed the :contains behaviour for the <script> tag by looking at both data and text. Can you please merge this? @jhy
https://github.com/lakshmirajagopalan/jsoup/commit/86162fcaecab7c4eda82cca27f86ec5862151af7

I added :containsData() to support this usecase.


Refactor Blob Service API

Refactor Blob Service API
This PR refactors the blob service API to be oriented around blob descriptors. Identified by digests, blobs become an abstract entity that can be read and written using a descriptor as a handle. This allows blobs to take many forms, such as a ReadSeekCloser or a simple byte buffer, allowing blob oriented operations to better integrate with blob agnostic APIs (such as the io package). The errors definitions are now better organized to reflect conditions that can only be seen when interacting with the blob API.
The main benefit of this is to separate the much smaller metadata from large file storage. Many benefits also follow from this. Reading and writing has been separated into discrete services. Backend implementation is also simplified, by reducing the amount of metadata that needs to be picked up to simply serve a read. This also improves cacheability.
"Opening" a blob simply consists of an access check (Stat) and a path calculation. Caching is greatly simplified and we've made the mapping of provisional to canonical hashes a first-class concept. BlobDescriptorService and BlobReadService can be combined in different ways to achieve varying effects.
Recommend Review Approach
This is a very large patch. While apologies are in order, we are getting a considerable amount of refactoring. Most changes follow from the changes to the root package (distribution), so start there. From there, the main changes are in storage. Looking at (*repository).Blobs will help to understand the how the linkedBlobStore is wired. One can explore the internals within and also branch out into understanding the changes to the caching layer. Following the descriptions below will also help to guide you.
To reduce the chances for regressions, it was critical that major changes to unit tests were avoided. Where possible, they are left untouched and where not, the spirit is hopefully captured. Pay particular attention to where behavior may have changed.
Storage
The primary changes to the storage package, other than the interface updates, were to merge the layerstore and blobstore. Blob access is now layered even further. The first layer, blobStore, exposes a global BlobDescriptorService and BlobReadService. Operations here provide a fast path for most read operations that don't take access control into account. The linkedBlobStore layers on top of the blobStore, providing a repository- scoped blob link management in the backend. The linkedBlobStore implements the full BlobService suite, providing access-controlled, repository-local blob writers. The abstraction between the two is slightly broken in that linkedBlobStore is the only channel under which one can write into the global blob store. The linkedBlobStore also provides flexibility in that it can act over different link sets depending on configuration. This allows us to use the same code for signature links, manifest links and blob links. Eventually, we will fully consolidate this storage.
The improved cache flow comes from the linkedBlobDescriptorStore component of linkedBlobStore. Using a cachedBlobDescriptorStore, these combine together to provide a simple cache hierarchy that should streamline access checks on read and write operations, or at least provide a single path to optimize. The metrics have been changed in a slightly incompatible way since the former operations, Fetch and Exists, are no longer relevant.
The fileWriter and fileReader have been slightly modified to support the rest of the changes. The most interesting is the removal of the Stat call from newFileReader. This was the source of unnecessary round trips that were only present to look up the size of the resulting reader. Now, one must simply pass in the size, requiring the caller to decide whether or not the Stat call is appropriate. In several cases, it turned out the caller already had the size already. The WriterAt implementation has been removed from fileWriter, since it is no longer required for BlobWriter, reducing the number of paths which writes may take.
Cache
Unfortunately, the cache package required a near full rewrite. It was pretty mechanical in that the cache is oriented around the BlobDescriptorService slightly modified to include the ability to set the values for individual digests. While the implementation is oriented towards caching, it can act as a primary store. Provisions are in place to have repository local metadata, in addition to global metadata. Fallback is implemented as a part of the storage package to maintain this flexibility.
One unfortunate side-effect is that caching is now repository-scoped, rather than global. This should have little effect on performance but may increase memory usage.
Handlers
The handlers package has been updated to leverage the new API. For the most part, the changes are superficial or mechanical based on the API changes. This did expose a bug in the handling of provisional vs canonical digests that was fixed in the unit tests.
Configuration
One user-facing change has been made to the configuration and is updated in the associated documentation. The layerinfo cache parameter has been deprecated by the blobdescriptor cache parameter. Both are equivalent and configuration files should be backward compatible.
Notifications
Changes the notification package are simply to support the interface changes.
Context
A small change has been made to the tracing log-level. Traces have been moved from "info" to "debug" level to reduce output when not needed.

This is solid work.
Indeed a big changeset - calling @noxiouz @ahmetalpbalkan @ncdc @RichardScothern to the rescue for additional reviews - we should merge this ASAP and avoid it to linger for too long so additional work can move forward on top of this.

I'm out of the office and can take a look next week. Cc @vbatts
On Wed, May 13, 2015 at 1:38 AM Olivier Gambier<EMAIL_ADDRESS>wrote:

This is solid work.
Indeed a big changeset - calling @noxiouz https://github.com/noxiouz
@ahmetalpbalkan https://github.com/ahmetalpbalkan @ncdc
https://github.com/ncdc @RichardScothern
https://github.com/RichardScothern to the rescue for additional reviews

we should merge this ASAP and avoid it to linger for too long so
additional work can move forward on top of this.

—
Reply to this email directly or view it on GitHub
https://github.com/docker/distribution/pull/519#issuecomment-101519515.

@dmp42 thank you for calling me. I'm going to look at it a couple hours later.

The changes look good and someone has to be first to drop it, but let me preface...
Having to pass along such a powerful interface such as a repository to every object is an unfortunate pattern that this changes makes steps to breaking.  repository.Name() occurs many times and often only the name is needed.  There were a few cases were it was confusing whether repository.ctx or .ctx should be used directly.  These mixups will always occur when direct access is allowed to a powerful parent object.  This change is progress though!
Also a few nits to address, but...
LGTM

Apart from name bikesheddings and splitting BlobReadService into BlobReadService and BlobServer, the interface looks solid and super well thought-out. Like I told @stevvooe, it would be super helpful to have in a later document somewhere, detailed explanations on why this design was chosen, mentioning different scenarios as well as how/where optimizations can happen.
Design LGTM

@dmcgowan I agree about the issue with having to pass Repository around. Really, it should represent the data structure Repository throughout the application, but it does carry baggage. Part of this comes from the original intent of the code, which avoided using the repository name as a string field. The other half comes from the lack of type safety we have for repository names.
I'll see if I can simplify this aspect slightly.

Updates:

Using errors.New where it makes sense
Writer is now Create and Rollback is now Cancel. The bikeshed is now painted.
Made blob oriented service definitions more granular. We now have BlobServer, BlobService and BlobStore.
Clarified godocs in blobs.go.
Removed descriptors from Open and ServeBlob by leveraging better separation with BlobStatter.
Cache control max-age moved to a constant and increased to one year

LGTM


FR: Can we achieve the semi folding effect shown in the figure below

Yes, I think, this would be possible. I was considering adding a feature something like this. Although, I am not yet sure, if the uncollapse button at the bottom, should be added or not? If the button is added then it could be confusing that normally the header controls folding, but in this case the lower button. Maybe it could be an option. I think it through, but generally it is a good idea. It will be available in a future release.

I have seen this semi folding effect in other tools, and it feels good. It would be a surprise if the plugin can achieve this effect.
I have a little question:in some tools, it can be set to automatically render such a semi folding effect when the number of lines in a code block exceeds a certain number of lines. I want to know whether this is achievable.

It definitely is. I am already working on it, just have to make a little smoother, so the difference in opacity between the lines is not visible. This what I have now:

You can set the number of visible lines. If you fold a code block, and it contains the previously set number + 4 lines (for the fade effect), then it will semi-fold.

Available in release 1.2.1 :) I hope you like it. Please give a feedback, if it's ok, or I should change something. I am closing the issue.


Use dependsOn list for a service to add more ExtraHosts definitions

Since we moved to using the service-router in all environment options for endpoints, services running in docker have been unable to communicated via nginx. This is due to .service.local.tescloud.com resolving inside a container to localhost.
This change adds the depended upon services to the hosts list with the host machine ip.

Coverage remained the same at 77.348% when pulling 5bb48e828b427560febcb44535f9fb02b62f2d22 on improve-local-domain-injection into c4d0cb57c6f8ada47f1e108bcbd0fc25852b3b13 on master.

lgtm


fix(FileDetails/FileDetailsLabel): Adjust chip width

We were relying on the default PatternFly label behavior for long titles. Mark raised a concern that this will cause problems in the future when we enable multiple file uploads. This PR adjusts the chip so it has text truncation and a max width. The loading state should also look a little more consistent when titles are long.

Modals use the same text treatment, meaning that they will have truncation.
Short title:

Long title:

Preview: https://virtual-assistant-pr-virtual-assistant-261.surge.sh

@rebeccaalpert needs rebase

Should be all set @nicolethoen!


feat: add tda and update outdated tests

implement ENG-3351

add tda
add consent config node
update outdated tests
add tests

More tests to come in next pr


haskellPackages.zeromq4-haskell_0_8_0: unbreak

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Tested with nix-build -A haskellPackages.zeromq4-haskell_0_8_0.

@GrahamcOfBorg build haskellPackages.zeromq4-haskell_0_8_0


Update testregistry.textproto

correcting TR-6.2 test title

Pull Request Functional Test Report for #2400 / 1d4627dee080a69afb594ff06648d0cd7b6d6de5
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1541

Relevant Lines:
3164

💛  - Coveralls


NioTest fails on fresh install of Fedora due to RSA key size < 2048

On a fresh installation of Fedora 31, running the NioTest will fail. This is due to Fedora using 2048 as the minimum allowed size for a RSA key and cloudstack generates a 1024 size key.
An upgrade has to be made to the certificate key size Cloudstack uses for the test as 2048 is the recommended size for RSA keys at the moment and other operating systems will likely make this a requirement as well.
I have verified the key size requirement in the following files:
/usr/share/crypto-policies/DEFAULT/java.txt
/usr/share/crypto-policies/FIPS/java.txt
/usr/share/crypto-policies/NEXT/java.txt
The NioTest passes when changing the RSA keySize to < 1024, but this doesn't address the issue of Cloudstack generating a less secure certificate.
ISSUE TYPE

Improvement Request

COMPONENT NAME

NioTest

CLOUDSTACK VERSION

Tested on <IP_ADDRESS>

CONFIGURATION

OS / ENVIRONMENT

Fedora 31
Cloudstack 4.13 branch
Java 1.8
Python 2.7
STEPS TO REPRODUCE

Do a fresh install of Fedora,
Install Java 8
Install python2.7
Install git
Install maven

Clone Cloudstack 4.13 branch

Run mvn install -Pdeveloper,systemvm

EXPECTED RESULTS

Tests pass

ACTUAL RESULTS

Tests fail

I think @shwstppr has addressed this in his PR #4068 ?

@Spaceman1984 here https://github.com/apache/cloudstack/pull/4068/files#diff-a24703d95ef24543c23939815013558a cc @rhtyd
I used a 2048-bit key. Do we need to use even higher for future-proofing?

@shwstppr I think 2048 is fine for now, I don't think the recommended size will change very soon. This issue may be closed once your PR is merged.

Addressed in https://github.com/apache/cloudstack/pull/4068/files#diff-a24703d95ef24543c23939815013558a


[9.x] Update Cache.php

Added missing docblock methods in Cache.php
These are public methods from:
\Illuminate\Cache\CacheManager
\Illuminate\Cache\Repository

@taylorotwell It is possible, I tested it rn:
Cache::put('key', 1);

Cache::offsetGet('key'); // 1


Plugin not working with Flutter View - Flutter Module on Android existing app!

i have flutter module use file-picker plugin, on flutter app it work fine but when add flutter module to existing android when picked a file or picture it not return anything. i created a flutter view to add module to android app
i found this code on file-picker it's mean that it can not return file to flutter View only work with FlutterActivity
public static void registerWith(PluginRegistry.Registrar registrar) {
if (registrar.activity() == null) {
// If a background flutter view tries to register the plugin, there will be no activity from the registrar,
// we stop the registering process immediately because the ImagePicker requires an activity.
return;
}
How can i fix it to work with Flutter View?

Hi @da140110, have you tried to load your FlutterView inside another Android Activity?

Due to no response for a while, I'm assuming you might have found a solution for this. Feel free to reopen otherwise.


enumSum?

I just noticed that enumSum didn't make it - is there a reason for leaving it out, or is it fine to port here?

No good reason for it to be missing that I can think of, I'm not sure why I didn't carry it over!


.Net: Extract semantic functions from Kernel.Core

Motivation and Context

Why is this change required? This is part of the work to extract functionality from Semantic Kernel core prior to 1.0 release.
What problem does it solve? Isolates the semantic function implementation from the Semantic Kernel core.
What scenario does it contribute to? Contributes to the goal of reducing the Semantic Kernel core to focus on AI orchestration.
If it fixes an open issue, please link to the issue here. https://github.com/microsoft/semantic-kernel/issues/2563

Description

Move classes from abstractions SemanticFunctions folder to skills core
Move classes from core SemanticFunctions and SkillDefinition folders to skills core
Fix up all unit tests

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Will create a new PR once Skill -> Plugin rename work is complete. Will follow the pattern in this ADR https://github.com/microsoft/semantic-kernel/pull/2668


Add the HLAPI Batch Installer (may need admin privileges)

This is a utility for Windows users to install HLAPI Community DLLs when compiled from source code into their Unity Editor installation. As long as they follow the script's directions when they run it, there will be no drama - all they need to do is enter the path of their Unity Editor installation.
If in doubt, you can inspect the batch file for any malicious behaviour, but I can assure you that this is non-destructive and has been tested extensively. Some problems may occur if Windows Batch Files are blocked due to security policy or other things on the target machine but that cannot be tested because my machine is standalone and not used in such an environment where batch files are blocked.

Codecov Report

Merging #7 into improvements will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           improvements      #7   +/-   ##
============================================
  Coverage          3.78%   3.78%
============================================
  Files                30      30
  Lines              7152    7152
  Branches           1207    1207
============================================
  Hits                271     271
  Misses             6875    6875
  Partials              6       6

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 d7cf9dc...ddb7ec1. Read the comment docs.

Sorry for never merging this. Mirror drop-in won't require this anymore


Add support for mysql 'SHOW CREATE VIEW' statement

Support for show create view.
This may be useful for https://github.com/apache/arrow-datafusion/issues/2857.

Thanks @mrob95

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 4 (75.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 89.884%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser.rs
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
8876

Relevant Lines:
9875

💛  - Coveralls

Thanks @mrob95 !


[DiagnoseUnreachable] Ignore dead_end destroys.

Such destroys mark the lifetime end of their operands along their availability boundary.  They are currently inserted in this test case by the ClosureLifetimeFixup pass, but in the fullness of time they will be present for every value which is not explicitly destroyed (that's what complete OSSA lifetimes is mostly about).
Currently, such destroys are diagnosed by DiagnoseUnreachable.  Fix the diagnostic pass not to diagnose these valid instructions.
rdar://137960229

@swift-ci please test

@swift-ci please test

@swift-ci please smoke test macos platform


version up to upload maven repository

What is the necessity of this update? What is updated?
version up to upload maven repository
How did you do the test? (Not required for updating documents)
uploaded to maven repository

LGTM

Merge is complete but there is a conflict.

This branch has conflicts that must be resolved

I used this procedure as a guide, but there seems to be no difference.
-step 1
git checkout -b yohto-verup master
git pull https://github.com/yohto/yosegi.git verup

-step 2
git checkout master
git merge --no-ff yohto-verup
git push origin master

@yohto
Check if the merge is complete, can you close it if there is no problem?

Thank you. I checked the conflict locally, but I couldn't find.
And, I used the command line to merge.


Install Boto for SQS capabilties?

I understand that it's not a core feature, but, in order to use SQS w/this image, I need boto installed in addition to Celery.  Thanks!

Have you tried something like the following?
FROM celery
USER root
RUN pip install boto
USER user


any plan support xcode 9 ?

got some errors when build project

Try setting your project to build using the Swift 3.2 compiler until the project is updated.

yes but i got this an error https://imgur.com/a/gp8wq

After running pod update I have this too. @MaTriXy's fork works with Swift 4, change your podfile to
pod 'paper-onboarding', :git => 'git@github.com:MaTriXy/paper-onboarding'

until the PRs are added here.

thanks @francisjervis it's help me a lot

I changed my podfile to this but still get this error? :/

what is your erro @ZenunVee r ?


u2f-local.php not working

I get "Unknown or missing requestId in response." when running u2f-local.php and clicking on Register.
Chrome Version 68.0.3440.84 (Official Build) (64-bit)
PHP Version 7.2.2

Looking at the https://demo.yubico.com/u2f shows it has a different version of u2f-api.js and the functions take different parameters.  For example u2f.register
this code: function(registerRequests, signRequests,callback, opt_timeoutSeconds)
demo site: function(appId, registerRequests, registeredKeys, callback, opt_timeoutSeconds)
So could it be this code is not compatible with the latest versions of chrome?


Add subscribeRequestProperties in secure erase job

During @ytjohn secure erase test, we found

Existing secure erase job doesn't have subscribeRequestProperties action, this works since secure_erase.py have no real rendering action. More important, current secure erase workflow used bootstrap-ubuntu triggerGroup, and bootstrap-ubuntu subscribeRequestProperties will take effective.
However if we remove tirggerGroup, secure erase job will fail without subscribeRequestProperties

This PR is to add subscribeRequestProperties in secure erase job.

@keedya @iceiilin @lanchongyizu @sunnyqianzhang


Suggestion: add toy data set to streamlit app

Cool work!
I recommend adding an example dataset to the streamlit app so that it's easier to explore. Maybe having a few (small) datasets in the repo could work too.
I get an error when I try to add my own data, but I'm not sure if that's a bug or me not properly formatting the data.

Hi James! Thank you for the suggestion, definitely valuable. Will address this issue ASAP

@JamesHWade  A "test run" option is now added to the streamlit app. You can download this toy dataset after the run along with test outputs.
Closing this issue for now. Thank you for your suggestion!


query watcher returning type CastList instead of List

Steps to Reproduce
create a query watcher like contacts.where().findAll().watch() and listen to it
Code sample
Stream stream = contacts.where().findAll().watch();

stream.listen((event) {
  print(event.runtimeType);
 //CastList<Contact, Contact>

});

casting the result to type List works, but casting it to List<Object> returns CastList<Contact, Contact> is not a subtype of List<Conatct>
Version

Platform: Android
Flutter version: 3.1.0-0.0.pre.1309
Isar version: 3.0.0-dev.5
Isar Generator version: 3.0.0-dev.5

Use .toList().cast()

thanks, this worked

Sorry for commenting on a closed issue, but I'm having the same issue when building a query like contacts.where().build() and then trying to execute findAll() on the query.
Already tried the solution above but the error continues the same. Also tried to cast using (await query.findAll()) as List<Contact> but not worked.
Any help would be appreciated, also, if it's best to create another issue I can do that.


Handling promise resolution

Sorry if this should go in the forums or chat, but I was a little confused about this section in the docs: https://vue-test-utils.vuejs.org/en/guides/getting-started.html#what-about-nexttick
It states

To simplify usage, vue-test-utils applies all updates synchronously so you don't need to use Vue.nextTick in your tests.

This is true if you are only doing DOM manipulation, but as soon as you are waiting for Promise resolution, I do not believe the statement holds.
I have what I think is a pretty common pattern in a component that I am trying to test, where it loads data from an API when it is created, and presents it in a list. Simply calling wrapper.update(), as far as I can tell, only re-renders the DOM, but does not push forward the event loop like Vue.$nextTick() does.
Explicitly calling wrapper.vm.$nextTick() does still push the event loop forward, and I get my data rendered in the DOM.
Is that the expected way to handle things in vue-test-utils? If so, I think it might be helpful to amend the What about nextTick section to clarify that nextTick is still needed for things like resolving asynchronous data retrieval.

Thanks for the issue 🙂
You're right, update only re renders the DOM. It doesn't affect async functions, like promises.
I think this should be added to the docs. Would you like to make a PR clarifying that update does not do this?

I'd be happy to, I'll try to get something up tonight.

You can handle wrapper.vm.$nextTick by using your test runner's done/end functions.
for instance with Ava you would write a test:
// use 'test.cb' instead of just 'test' as it tells Ava to wait for a callback
test.cb('A $nextTick test that will pass', t => {
  const wrapper = shallow(MyComponent);
  wrapper.vm.$nextTick(() => {
    t.pass(); // passes the test - you can have any assertion here
    t.end(); // ends the test
  });
});

And other test runners also must have similar methods for testing async JS.

Sorry, forgot to close this after merging #86.
Also thanks @fartek for the example, I've actually been a fan of using async/await in my tests, so I don't have to wrap anything in a callback:
it('should await synchronously', async () => {
  const wrapper = mount(MyComponent)

  await wrapper.vm.$nextTick()

  // assert things like data loading properly
}

Sorry for posting this here, but I'm having trouble with this exact case. I am writing a test for a component that loads data from an API and displays that data in a form. I'm mocking the data access layer and resolving the promise right away. With the code above, the value is never there yet and my test fails.
Here's the test:
// ...imports

describe('Profile page', () => {
  const localVue = createLocalVue()
  localVue.use(Vuex)

  // mock api data
  jest.mock('@/data/PersonData', () => {
    return {
      getOwnerData () {
        return Promise.resolve({ email<EMAIL_ADDRESS>})
      }
    }
  })

  test('data is loaded and rendered', async () => {
    const store = createNamespacedStore('@/store/modules/Profile', 'Profile')
    const wrapper = mount(Profile, {
      store,
      localVue,
      mocks: {
        $t: jest.fn()
      }
    })

    await wrapper.vm.$nextTick()
    // this fails:
    expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>    // this passes:
    setTimeout(() => {
      expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>    }, 10)
  })
})

Any help on this?

Use flush-promises:
npm install --save-dev flush-promises

import flushPromises from 'flush-promises'

  test('data is loaded and rendered', async () => {
    const store = createNamespacedStore('@/store/modules/Profile', 'Profile')
    const wrapper = mount(Profile, {
      store,
      localVue,
      mocks: {
        $t: jest.fn()
      }
    })
    await flushPromises()
    expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>  })
})

Thanks @eddyerburgh. Unfortunately, it still doesn't work. I have the await flushPromises() right before the expect. Again, if I put the expect into the setTimeout block, even with 1ms, the test passes.
It may be relevant to note that the component I'm testing calls the mocked function getOwnerData() in it's beforeMount hook. So it's being invoked automatically. All the examples I'm seeing with jest are invoking the async methods themselves, like:
expect(wrapper.load()).resolves.toBe(...)

Try calling flushPromises twice.
Here's an example test for a component that runs an async function in beforeMount—https://github.com/eddyerburgh/vue-hackernews-chapter-6/blob/master/src/views/__tests__/ItemList.spec.js#L65

Doesn't work either::
await flushPromises()
await flushPromises()
expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>

I can +1 on @chlab’s use–case, works for me as a thenable, unfortunately doesn’t with await. 🤔

@mixn  What test runner/ browser environment are you using?

I've just been dealing with a similar problem and didn't want to hack around it using timeout's (nextTick also didn't work). I fixed this by exposing the promise in my components data and referencing it in my test.
// form.js?
  data () {
    return {
      submitPromise: true
    }
  },

  methods: {
    submit () {
      this.submitPromise = this.$validator
        .validateAll()
        .then(() => {
          if (!this.credentialsIncorrect && !this.errors.items.length) {
            this.$emit('onCredentialsCorrect', this.activationForm)
          } else {
            this.$emit('onCredentialsIncorrect', this.errors.items)
          }
          return Promise.resolve()
        })
      return this.submitPromise
    }
  },

// form.test.js
  it('will run test after promise is resolved', () => {
    form.trigger('submit')
    return wrapper.vm.submitPromise
      .then(()=>{
        expect(wrapper.emitted('onCredentialsCorrect')).toBeTruthy()
      })
  })

+1 for then() working but async/await not

Instead of:

wondering if including import 'babel-polyfill'; would help in @chlab 's case. 🤔

Doesn't work either:
await flushPromises()
await flushPromises()
expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>
edit: huh, this works though:
flushPromises().then(() => {
  expect(wrapper.find({ ref: 'emailField'<EMAIL_ADDRESS>})

Any idea why the async/await version wouldn't work (I'm using async/await everywhere else in my code)?

Thanks @chlab . I had a same issue and this worked well.


Add optional display name for HomeAssistant discovery

Documents activation of HomeAssistant MQTT discovery
Adds the option to set a human readable name  per input/output pin, or sensor. This allows for example to use spaces and german umlauts.

Thanks so much for your work on this! However, I won't merge this PR because it's been extended already by #172 , and it'll need transferring over to the new version of the software on feature/asyncio. I'm sorry that you won't get your merge credit, but your work will be incorporated one way or another, so thank you!


Add support for the Null Array response

Currently, the library does not yet support Null Array replies ( "*-1\r\n" ), as described here: https://redis.io/topics/protocol#resp-arrays
This is due parser_array_len not expecting '-' as the first character, and no follow up code existing if this is indeed the case.
This PR looks to fix this, and seems to work in my use case (Try for example executing:
WATCH a
MULTI
SET a a
EXEC

while setting a over e different connection somewhere between the WATCH and the EXEC. This would originally result in the library hanging indefinitely, while now it comes back with a null response as specified by the Redis documentation.

You should look at if the code is structured as you would like it to be, and if indeed all use cases are implemented.

Second commit is to fix a possible ambiguity: A null array would respond with res.size == 1, making it indistinguishable from an array which (correctly) return a nil response.
Quick fix is to force the result length to be zero, as in the commit. However, correct would be to return an rrt_array_value with length 0, or in a normal commit return an rrt_array_value containing its children. This is currently blocked by #4.

Sorry for response so late.
I design '-' as result for error message, so at least have one element in array, which type is rrt_error_info.
In case result have many error message, it has a clean interface to use.

What do you mean by this exactly? Because the null array is different from an error, so should this not have a different message?

If result have many error in result, it must store in an array.


[haskell-updates] haskellPackages.hnix: Fix build

Add override as explained in the comment
This addresses https://github.com/haskell-nix/hnix/issues/676 and #93103.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build haskellPackages.hnix


Design PR - Prototype ClaimsTransformation (non automatic flow)

Addresses https://github.com/aspnet/Security/issues/48 second part:
Also hook any calls to HttpContext.AuthenticateAsync to apply transformation before returning the resultant identity
This is a bit messy/fragile as currently each AuthMiddleware has to manually call ApplyClaimsTransformation, thoughts on how best to force this to happen?  If the ClaimsTransformation options were moved up into Http.Authentication, HttpContext could do it as the last step before returning any results from Authenticate instead of relying on the implementations of the handler to remember to apply the xform...
cc @Praburaj @Tratcher @loudej @brentschmaltz

@davidfowl suggested swapping in a claims transformation decorated HttpAuthenticationFeature, I will try that next

Updated with feedback from @lodejard
Transformation now done via ClaimsTransformation IAuthenticationHandler.
There's an issue where Automatic authentication schemes like Cookies will apply the transformation twice (once on the automatic authenticate, and once when the Xform middleware runs)

cc @brentschmaltz

Merged 14d1b467c69dd6f836f5683b6e1545b7f3f859ee


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.places

[ ] [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.places"

Thanks,
your automatic adapter checker.

Thanks, that all bugs have been fixed.


bootfiles: allow i2c-gpio overlay

Hi all,
this is a RFC to be able to add i2c-gpio overlays.
Defining I2C_GPIO_CONFIG = "bus=7,i2c_gpio_sda=6,i2c_gpio_scl=5"
Will configure i2c-7 bus to use gpio 6 as SDA and gpio 5 as SCL
This way of configuration has the drawback to not be able to define more then one bus. Should we define an array? I saw some other defines using _X so we could use e.g
I2C_GPIO_CONFIG_X = "i2c_gpio_sda=6,i2c_gpio_scl=5" to define bus X and check a fix list of such variables?
I'm also not sure if we should abstract the command line even further?
I2C_GPIO_CONFIG_X_SCL=6
I2C_GPIO_CONFIG_X_SDA=5
Or something like that?

It feels to me that we are splitting this a bit too much. I would say let's just keep the dtb installed and enable the configuration with the general extra config vairable.

Hi,
thanks for the review and the imput. I changed the pull request as suggested.

Thanks again for the review :) I updated the pull request as suggested.


Modified example in separable_conv2d

Example code has changed by modifying existing code

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.34%. Comparing base (e12ae46) to head (65791db).

:exclamation:  There is a different number of reports uploaded between BASE (e12ae46) and HEAD (65791db). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (e12ae46)
HEAD (65791db)

keras
4
1

keras-tensorflow
1
0

keras-torch
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20629       +/-   ##
===========================================
- Coverage   82.37%   60.34%   -22.04%
===========================================
  Files         517      517
  Lines       48517    48517
  Branches     7570     7570
===========================================
- Hits        39968    29276    -10692
- Misses       6729    17468    +10739
+ Partials     1820     1773       -47

Flag
Coverage Δ

keras
60.34% <ø> (-21.88%)
:arrow_down:

keras-jax
?

keras-numpy
60.34% <ø> (ø)

keras-tensorflow
?

keras-torch
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Unable to install with Laravel 9/PHP 8.1/Nova 4

When running composer require naoray/blueprint-nova-addon I get the following error
_Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires naoray/blueprint-nova-addon ^2.0 -> satisfiable by naoray/blueprint-nova-addon[v2.0.0].
- naoray/blueprint-nova-addon v2.0.0 requires illuminate/pipeline ^6.0 || ^7.0 || ^8.0 -> found illuminate/pipeline[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require naoray/blueprint-nova-addon:*" to figure out if any version is installable, or "composer require naoray/blueprint-nova-addon:^2.1" if you know which you need._
I'm guessing this is related to new PHP, Laravel, Or Nova. Do you have any plans to update the code?

Any news regarding nova 4 support?

@Naoray If you can update the package for Laravel 9. I can check the compatibility for Nova 4.

Any news regarding nova 4 support?

is there a demand? I plan to support

It looks like these two forks support Nova 4
https://github.com/neilgilmour/blueprint-nova-addon
https://github.com/osubeaver808/blueprint-nova-addon


Consider grouping font options in the json into an object

Is it time for us to move from fontFace to font{ face, weight, ... } or font{ family, weight ... }?
Originally posted by @DHowett in https://github.com/microsoft/terminal/pull/6048#issuecomment-631635543

link: #1790

triage: 1.x


Documentation for GCP Trigger Spec

Moved documentation to new scaler folder

You might want to get a clean fork 😅
Relates to #301


Revert "Conditionally pass musttail checking flag to frontend."

This reverts commit 0acbbbd001887bf8be842065928df037b457f88c.
Using this flag caused breakage when trying to use upstream LLVM
as well as Clang/LLVM from Xcode 12.5. See SR-14714.

@swift-ci test


Six package dependencies incompatible with awsebcli

Hello
I'm trying to use awsebcli to deploy my web application to AWS. When I try to install awsebcli I get next error:
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Could not find a version that matches six<1.12.0,<2,>=1.10.0,>=1.11.0,>=1.12,>=1.3.0,>=1.4.0,>=1.5,>=1.9.0
Tried: 0.9.0, 0.9.1, 0.9.2, 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.4.1, 1.5.0, 1.5.0, 1.5.1, 1.5.1, 1.5.2, 1.5.2, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.7.3, 1.7.3, 1.8.0, 1.8.0, 1.9.0, 1.9.0, 1.10.0, 1.10.0, 1.11.0, 1.11.0, 1.12.0, 1.12.0, 1.13.0, 1.13.0, 1.14.0, 1.14.0, 1.15.0, 1.15.0
Skipped pre-versions: 1.0b1
There are incompatible versions in the resolved dependencies.
I'm using pipenv. graphql-relay-py requires six>=1.12 and awsebcli requires >=1.11.0,<1.12.0
is there any way to resolve this dependency?

The current vresion of graphql-relay-py does not require six any more.


could not make search-guard works with elasticsearch head

Search Guard and Elasticsearch version
Both are 5.1.1
JVM version and operating system version
JDK 1.8, AWS linux
Number of nodes in your cluster
3
the Key, certficates are generated by the example.sh,  the elasticsearch head tried to talk with https which is not work. Even just curl with username and password not working:
[root@ip-10-8-8-246 elasticsearch-head]# curl https://admin:admin@<IP_ADDRESS>:9200/
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: https://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
...
the elasticsearch configuration is:
[root@ip-10-8-8-246 elasticsearch-head]# cat /etc/elasticsearch/elasticsearch.yml
cluster.name: ELK-TUHAO
path.data: /data
node.name: usg-elk-a
network.host: <IP_ADDRESS>
action.destructive_requires_name: true
bootstrap.memory_lock: true
discovery.zen.minimum_master_nodes: 2
discovery.zen.ping.unicast.hosts: ['<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>']
searchguard.ssl.transport.keystore_filepath: usg-elk-a-keystore.jks
searchguard.ssl.transport.keystore_password: changeit
searchguard.ssl.transport.truststore_filepath: truststore.jks
searchguard.ssl.transport.truststore_password: changeit
searchguard.ssl.transport.enforce_hostname_verification: false
#searchguard.ssl.transport.http.enforce_clientauth: false
searchguard.authcz.admin_dn:

CN=kirk, OU=client, O=client, L=Test, C=DE

#enable REST API with https:
searchguard.ssl.http.enabled: true
searchguard.ssl.http.keystore_filepath: usg-elk-a-keystore.jks
searchguard.ssl.http.keystore_password: changeit
searchguard.ssl.http.truststore_filepath: truststore.jks
searchguard.ssl.http.truststore_password: changeit

do you think this is a bug?

do you mean that we can not connect to head after installing search guard？thank you for reply   @floragunncom

Yes, head not able to connect to the cluster.

Does curl -k https://admin:admin@<IP_ADDRESS>:9200/work?
Regarding head plugin: Pls look into the JS developer console of your browser to get details why the connection is fails and make sure you have enabled CORS support and you can open https://admin:admin@<IP_ADDRESS>:9200 directly in the browser.
Regarding CORS pls read the head docs: https://github.com/mobz/elasticsearch-head and if its still not working i suggest you open a head issue.

ping

thanks,  curl -k works:
[root@ip-10-8-8-246 ec2-user]# curl -k https://admin:admin@<IP_ADDRESS>:9200/
{
"name" : "usg-elk-a",
"cluster_name" : "ELK-TUHAO",
"cluster_uuid" : "P5VnvOw-T7eN2G5YC2Dyfw",
"version" : {
"number" : "5.1.1",
"build_hash" : "5395e21",
"build_date" : "2016-12-06T12:36:15.409Z",
"build_snapshot" : false,
"lucene_version" : "6.3.0"
},
"tagline" : "You Know, for Search"
}

Hi robertchen:
Have you  connected to the cluste by elasticsearch-head?

yes, should be ok.

Can you tell me how to connect with elasticsearch-head when we use search-guard ? Thank you anyway

@xiaoyuxiaoyu

Before connecting ES with Elasticsearch-head, you need to browse to either ES node (https://es-node01:9200/) and let your browser accept the self-signed certificate while it warns you of the unsecured/untrusted connection.
Then browse to Elasticsearch-head: http://es-head:9100/?base_uri=https://es-node01:9200&auth_user=admin&auth_password=admin_password
Finally, press the "Connect" button in Elasticsearch-head and the cluster health info will appear.


disable Circle e2e tests

Motivation is that Circle e2e tests have been broken for a few days, it appears to be flaky and an ongoing problem. @AaaChiuuu & Andrew Chen are taking a look, but for now let's turn this off so that Circle can be useful for other things.

Let's make sure this actually fixes Circle before merging

Ok but this is still quite bad because we also have instrumentation tests disabled


[FIXED JENKINS-45478] Add UTM query parameter support

See JENKINS-45478
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Change from p6doc to rakudoc

Our installed doc tool should probably be called rakudoc and no longer p6doc.

I believe this can be closed, as I understand the current plan it's to use the tool in raku/rakudoc.

Got it. Will close it when it's totally eliminated from here (and created a
new release)

It's been removed, and is now called rakudoc at http://github.com/raku/rakudoc


Add 'title' attribute support

Current Behavior
There is no support for title prop so that the rendered iframe have a title attribute. This causes the accessibility score to drop
Expected Behavior
Allow a prop title to add title in rendered iframe

ReactPlayer has very little control over the iframes that each player API produces. If the API supports a title attribute, then it can probably be configured in the config prop. If not, there's not much that this library can do to help.


LOSes & Links are not shown in the map view

When viewing a LOS or link in the map view, the installs on either side of the link are not shown in the admin map view, it is blank

Same with devices, aps and sectors