Modeling tool research

Pam had provided a listing of modeling tools that might be relevant for ASKEM program

Simulink: https://www.mathworks.com/products/simulink.html
GleamViz: http://www.gleamviz.org/

ABMs:

Netlogo http://www.netlogoweb.org/launch#http://www.netlogoweb.org/assets/modelslib/Curricular Models/epiDEM/epiDEM Travel and Control.nlogo
GAMA: https://gama-platform.org/
MESA: https://mesa.readthedocs.io/en/main/tutorials/adv_tutorial.html#adding-visualization

Misc

EPI Grass: https://www.youtube.com/watch?v=UwZ-KWV0oGU

Marking as completed. Our notes can be found here:
https://docs.google.com/document/d/1xxJ7LGLi_yp600zMNzlNZC_pP8exhhyyD3p--r6CJRA/edit#


Filter menu and field name with dot

When field name contains dot (nested objects), filter menu only show "(Blanks)".
Is that supposed to work, or am I missing something? Let me know if you need more info.
Thank you

dots in field name not supported. if you need 'embedded' fields, then use valueGetter and expressions.

ok, thank you

What if you do not have 'embedded' fields but rather just column names with dots in them like (Parent.Name)? It still is showing blanks even though row data has "Parent.Name" property with values.

@goodies4uall user property suppressFieldDotNotation use the dots as part of the name

@goodies4uall user property suppressFieldDotNotation use the dots as part of the name

Thanks a lot


CMS wizard leaks session data

Summary
Create newsblog app config A and B
Create newsblog article via wizard inside app config B targeting app A
Press on the wizard create button before toolbar loads
Create newsblog article targetting app A
Expected behaviour
There should be no TypeError at /en/cms_wizard/create/

I would expect the issue to still be there, but would be nice to confirm with the latest CMS version.


Automated cherry pick of #266: 修复选择endpoint

Cherry pick of #266 on release/2.6.0.
#266: 修复选择endpoint

/approve
/lgtm


Compiling usbd.h with C++ compiler fails

Hi,
Compiling a Zephyr project with a C++ compiler (CONFIG_CPP=y) leads to a build error, when zephyr/include/zephyr/usb/usbd.h gets included.
/opt/zephyrproject/zephyr/include/zephyr/usb/usbd.h:507:9: error: designator order for field 'usbd_desc_node::<anonymous>' does not match declaration order in 'usbd_desc_node'
  507 |         }

/opt/zephyrproject/zephyr/include/zephyr/usb/usbd.h:530:9: error: designator order for field 'usbd_desc_node::ptr' does not match declaration order in 'usbd_desc_node'
  530 |         }

Putting the members of the struct in the correct order in those macros fixes the problem.

I had the same problem with zbus when CONFIG_RUNTIME_OBSERVERS=y (or whatever it's called) is set. Are there any means to tell the C compiler to act like C++ in this regard?

Take a look at https://github.com/zephyrproject-rtos/zephyr/commit/d3a1ce879186eebdb604bc48c23987dce9b1d2d8 and #70403

@MSeesko  can you please provide information about which Zephyr version/sha you are using?

I am using Zephyr 3.7.0-rc3


chore: change codecov reporter to nyc

BREAKING CHANGE: required node 7.6.0 to run this. New options for logger named trace, defaults to false and contrary to previous versions does not create ringBuffer by default

Codecov Report

Merging #212 into master will increase coverage by 2.82%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #212      +/-   ##
=========================================
+ Coverage   90.28%   93.1%   +2.82%
=========================================
  Files          41       1      -40
  Lines         988      87     -901
=========================================
- Hits          892      81     -811
+ Misses         96       6      -90

Impacted Files
Coverage Δ

src/index.js
93.1% <0%> (ø)
:white_check_mark:

src/plugins/http/handlers/express/router/attach.js

src/plugins/router/modules/allowed.js

src/plugins/router/modules/response.js

src/plugins/http/handlers/hapi/index.js

src/plugins/router/extensions/index.js

src/plugins/redis/migrate.js

src/plugins/socketIO.js

src/plugins/router/modules/auth.js

src/plugins/router/modules/handler.js

... and 31 more

Continue to review full report at Codecov.

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


Remove meaningless judgments in DDFileLogger

New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[x] I have added the required tests to prove the fix/feature I am adding

[x] I have updated the documentation (if necessary)

[x] I have run the tests and they pass

[x] I have run the lint and it passes (pod lib lint)

This merge request fixes / refers to the following issues: ...
Pull Request Description
https://github.com/CocoaLumberjack/CocoaLumberjack/pull/1042/files#diff-c8a9bcf29dc1c5256c046b115400ea8ac3327f7200552637f62f8a49ae6f4109R1039
This refactor had check if the log file is archived. Just return NO to create new log file. So in lt_shouldLogFileBeArchived method to check archived is meaningless.
I guess the refactoring forgot to delete this judgment.
In other words, If the file has been archived, it's need to create new log file. this place should also return YES instead of NO.

/run_checks


Build a functional e2e tests framework for the project

We could use something like https://github.com/DATA-DOG/godog for this.
The minishift folks use this too.
This is how their tests look for e.g.
@basic
Feature: Basic
  As a user I can perform basic operations of Minishift and OpenShift

  Scenario: User can install default add-ons
    When executing "minishift addons install --defaults" succeeds
    Then stdout should contain
     """
     Default add-ons 'anyuid, admin-user, xpaas, registry-route' installed
     """

  Scenario: User can enable the anyuid add-on
    When executing "minishift addons enable anyuid" succeeds
    Then stdout should contain
     """
     Add-on 'anyuid' enabled
     """

from - https://github.com/minishift/minishift/blob/master/test/integration/features/basic.feature

Another option is ginkgo - https://onsi.github.io/ginkgo/

@kadel @ashetty1 can we close this?

Did you guys decide any test frame work ? or go with your decided one ?

@containscafeine sure.
@amitkrout we zeroed in on ginkgo.

Fair enough, i will recommend to play around with those BDD framework. You will love BDD style.

Closing this since we already have a framework in place, feel free to re-open if someone thinks otherwise


[Feature Request]: Integration with Charger Card

The feature
https://github.com/tmjo/charger-card/tree/master
Charger Card looks pretty interesting.

Additional information
No response

Way ahead of you https://github.com/tmjo/charger-card/issues/22

I've ended up trying to mimic some OpenEVSE ui on HA UI for this and feel it much better on daily use.

very slick

I've ended up trying to mimic some OpenEVSE ui on HA UI for this and feel it much better on daily use.

@KipK - Is this published to anywhere, or downloadable as a script?

Those are just dashboard cards.

Right. It has been on my to do to create better looking dashboards for charging. I was hoping KipK would share the yaml for that buildup of cards instead of having to duplicate that work also.

Hopefully he'll share at some point :slightly_smiling_face:

Right. It has been on my to do to create better looking dashboards for charging. I was hoping KipK would share the yaml for that buildup of cards instead of having to duplicate that work also.

Sure here is the EVSE part yaml:
`
type: grid
cards:

type: heading
icon: mdi:ev-station
heading: OpenEVSE
heading_style: subtitle
type: entities
entities:

type: custom:hui-element
card_type: horizontal-stack
cards:

type: horizontal-stack
cards:

type: heading
icon: ""
heading_style: title
type: custom:button-card
entity: input_text.openevse_override_state
aspect_ratio: 2
color_type: card
show_label: true
show_name: false
icon: fas:bolt
name: Auto
tap_action:
action: call-service
service: openevse.set_override
target:
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
data:
state: active
state:

value: active
color: rgb(24.71% 82.35% 56.47%)
styles:
icon:
- color: >-
[[[ if
(states['sensor.openevse_charging_status'].state ===
'charging') return 'yellow';  else return 'white';
]]]
operator: default
color: rgba(0, 0, 0, 0.0)
styles:
icon:
- color: rgba(24.71% 82.35% 56.47% 1)
styles:
card:

border-radius: 10%

type: custom:button-card
entity: input_text.openevse_override_state
aspect_ratio: 2
color_type: card
show_label: true
show_name: false
icon: fas:robot
name: Auto
tap_action:
action: call-service
service: openevse.clear_override
target:
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
state:

value: auto
color: rgb(19.61% 70.2% 83.14%)
styles:
icon:
- color: >-
[[[ if
(states['sensor.openevse_charging_status'].state ===
'charging') return 'yellow';  else return 'white';
]]]
operator: default
color: rgba(0,0,0,0.0)
styles:
icon:
- color: rgba(19.61% 70.2% 83.14% 1)
styles:
card:

border-radius: 10%

type: custom:button-card
entity: input_text.openevse_override_state
aspect_ratio: 2
color_type: card
show_label: true
show_name: false
icon: fas:ban
name: Auto
tap_action:
action: call-service
service: openevse.set_override
target:
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
data:
state: disabled
state:

value: disabled
color: rgb(6.67% 41.57% 53.33%)
styles:
icon:
- color: white
operator: default
color: rgba(0,0,0,0.0)
styles:
icon:
- color: white
styles:
card:

border-radius: 10%

type: heading
icon: ""
heading_style: title

type: custom:hui-element
card_type: custom:mushroom-chips-card
chips:

type: entity
entity: sensor.openevse_station_status
card_mod:
style: |
ha-card {
{% if states("sensor.openevse_station_status") == 'active' %}
--chip-background: rgb(24.71% 82.35% 56.47%);
{% elif states("sensor.openevse_station_status") == 'disabled' %}
--chip-background: rgb(6.67% 41.57% 53.33%);
{% endif %}
border-radius: 10% !important;
}
type: entity
entity: sensor.openevse_charging_status
card_mod:
style: |
ha-card {
{% if states("sensor.openevse_charging_status") == 'connected'%}
--chip-background: rgb(24.71% 82.35% 56.47%);
{% elif states("sensor.openevse_charging_status") == 'charging'%}
--chip-background: rgb(19.61% 70.2% 83.14%);
{% elif states("sensor.openevse_charging_status") == 'not connected' or states("sensor.openevse_charging_status") == 'sleeping' %}
--chip-background:  rgb(6.67% 41.57% 53.33%);
{% endif %}
border-radius: 10% !important;
}
type: entity
entity: binary_sensor.openevse_vehicle_connected_2
card_mod:
style: |
ha-card {
{% if states("binary_sensor.openevse_vehicle_connected_2") == 'on' %}
--chip-background: rgb(24.71% 82.35% 56.47%);
{% elif states("binary_sensor.openevse_vehicle_connected_2") == 'off' %}
--chip-background: rgb(6.67% 41.57% 53.33%);
{% endif %}
border-radius: 10% !important;
}
alignment: center

show_name: true
show_icon: true
show_state: true
type: glance
entities:

entity: sensor.openevse_charge_time_elapsed
name: Temps écoulé
entity: sensor.openevse_time_left
name: Temps réstant
icon: mdi:timer-sand
entity: sensor.openevse_usage_this_session
name: Session
icon: mdi:ev-station
columns: 3

type: horizontal-stack
cards:

type: horizontal-stack
cards:

type: gauge
entity: number.openevse_charge_rate
name: Consigne
max: 32
type: gauge
entity: sensor.ioniq_5_ev_battery_level
name: SOC
max: 100
unit: "%"
min: 1
type: entities
entities:

entity: sensor.openevse_current_power_usage
name: " "
secondary_info: none
entity: sensor.openevse_charging_current
name: "  "
show_header_toggle: true
state_color: false

type: custom:mushroom-number-card
entity: number.openevse_charge_rate
name: Courant
icon_color: blue
fill_container: true
grid_options:
columns: 12
rows: 2
type: entities
entities:

entity: sensor.openevse_current_power_usage
name: Puissance
secondary_info: none
entity: sensor.openevse_charging_current
name: Courant
entity: sensor.openevse_ambient_temperature
name: Température

square: true
type: grid
cards:

show_name: false
show_icon: true
type: button
tap_action:
action: url
url_path: https://openevse.local/#/configuration/firmware
entity: binary_sensor.openevse_ota_update
name: Maj
icon: mdi:update
show_state: true
show_name: false
show_icon: true
type: button
tap_action:
action: perform-action
perform_action: homeassistant.reload_config_entry
target:
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
data: {}
name: Restart
icon: mdi:restart
show_state: false
columns: 6
column_span: 1
`

It needs input_text.openevse_override_state  helper
And this automation to set it correctly :
`
alias: Update OpenEVSE State
description: Update OpenEVSE 3 buttons state
triggers:

entity_id: binary_sensor.openevse_manual_override
trigger: state
type: changed_states
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
entity_id: 2af9afd2bfe57f61f9d4a3127015f562
domain: switch
trigger: device
trigger: state
entity_id:

sensor.openevse_charging_status
conditions: []
actions:

response_variable: openevse_response
action: openevse.list_overrides
data: {}
target:
device_id: 1a8619b7019b8e42ea0f560a0c008fc0
variables:
override_state: "{{ openevse_response['state'] }}"
choose:

conditions:

condition: template
value_template: "{{ override_state == 'disabled' }}"
sequence:
data:
entity_id: input_text.openevse_override_state
value: disabled
action: input_text.set_value

conditions:

condition: template
value_template: "{{ override_state == 'active' }}"
sequence:
data:
entity_id: input_text.openevse_override_state
value: active
action: input_text.set_value
default:

data:
entity_id: input_text.openevse_override_state
value: auto
action: input_text.set_value
mode: queued
max: 10
`


Remaining errors in HA logs in ha-tahoma V2.7.1

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
Remaining errors in HA log with ha-tahoma V2.7.1
2021-09-07 17:43:19 INFO (MainThread) [homeassistant.setup] Setting up tahoma
2021-09-07 17:43:19 INFO (MainThread) [homeassistant.setup] Setup of domain tahoma took 0.0 seconds
2021-09-07 17:43:20 WARNING (MainThread) [homeassistant.components.sensor] custom_components.tahoma.sensor is setting 'unit_of_measurement' on an instance of SensorEntityDescription, this is not valid and will be unsupported from Home Assistant 2021.11. Please report it to the custom component author.
2021-09-07 17:43:20 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.tahoma
2021-09-07 17:43:20 WARNING (MainThread) [custom_components.tahoma.climate_devices.atlantic_pass_apc_heating_and_cooling_zone] Temperature sensor could not be found for entity Zone 1
2021-09-07 17:43:20 ERROR (MainThread) [homeassistant.components.switch] Error while setting up tahoma platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tahoma/switch.py", line 50, in async_setup_entry
[
TypeError: 'NoneType' object is not iterable`

What version of this integration (ha-tahoma) has the issue?
2.7.1
What version of Home Assistant Core has the issue?
Core-2021.9.4
Which gateway / hub do you use?
Cozytouch
Device model
R002412300 by Atlantic Group Firmware: C667208
Device type
Atlantic Firmware: 2021.3.4
Additional information
In addition the temperature is not displayed anymore for heat chart

Relevant log output
2021-09-07 17:43:19 INFO (MainThread) [homeassistant.setup] Setting up tahoma
2021-09-07 17:43:19 INFO (MainThread) [homeassistant.setup] Setup of domain tahoma took 0.0 seconds
2021-09-07 17:43:20 WARNING (MainThread) [homeassistant.components.sensor] custom_components.tahoma.sensor is setting 'unit_of_measurement' on an instance of SensorEntityDescription, this is not valid and will be unsupported from Home Assistant 2021.11. Please report it to the custom component author.
2021-09-07 17:43:20 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.tahoma
2021-09-07 17:43:20 WARNING (MainThread) [custom_components.tahoma.climate_devices.atlantic_pass_apc_heating_and_cooling_zone] Temperature sensor could not be found for entity Zone 1
2021-09-07 17:43:20 ERROR (MainThread) [homeassistant.components.switch] Error while setting up tahoma platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tahoma/switch.py", line 50, in async_setup_entry
[
TypeError: 'NoneType' object is not iterable

Thx for this report. I guess you haven’t any covers? About the warning, this one has been fixed with https://github.com/iMicknl/ha-tahoma/pull/553 and I have now fixed your error with.
Both fixes will be available with the next release.

Thanks for your quick fix.
No i have not cover
Télécharger BlueMail pour Android
Le 8 sept. 2021 à 08:51, à 08:51, Thibaut @.***> a écrit:

Thx for this report. I guess you haven’t any covers? About the warning,
this one has been fixed with
https://github.com/iMicknl/ha-tahoma/pull/553 and I have now fixed your
error with.
Both fixes will be available with the next release.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/iMicknl/ha-tahoma/issues/554#issuecomment-914968520


🐛 [firebase_messaging] Disable default notification

Hello,
First thanks for this fantastic plugin! You do an awesome work!
I come here to ask if its possible to disable default firebase notification, i was unable to achieve that, i have my own notification service on my app and want to use it instead of default firebase notification. backgroundHandler automatically fires a default notification, is this possible ?  Thanks.

Hi @menezes85, how are you sending the notifications and what is the payload that you send?

The background handler does not by default post a notification. If you wish to have a silent message (i.e. no notification), do not send a notification in the message payload: https://github.com/firebase/flutterfire/blob/master/packages/firebase_messaging/firebase_messaging/example/scripts/send-message.js#L25C1-L28


XNatalie for Xcode7

XNatalie plugin need update to Xcode 7 on branch Swift20 cc @phimage

I can't install for the moment Xcode7 on my computer
I test on Xcode 7 beta 1 on friend computed, I don't see any issues except adding the UUID of current XCode
But new beta could have break the plugin

I tested it on some later beta and it crashed.

I see you have updated code and add UUID for beta 3 763b97aae5e9aa4fd6c293fc329bd03f6513c895
So I tested with beta 3
I have no problem (on OSX 10.10.3)
But I do some project configuration change to test it :

Edit Scheme > Run > Info (tab)
Change Executable to Xcode-beta.app

But when Xcode7 will be the main Xcode, this change will be no more necessary
So I don't know If it is necessary to commit this change (to remove it later)


Multiple Commands Build Error

Showing Recent Messages
:-1: Multiple commands produce '/Users/karanshah/Library/Developer/Xcode/DerivedData/tflite_photos_example-hdnywmlpwpmthuekrlxjakvnxhzq/Build/Products/Debug-iphonesimulator/tflite_photos_example.app/Info.plist':

Target 'tflite_photos_example' (project 'tflite_photos_example') has copy command from '/Users/karanshah/tensorflow-for-poets-2/ios/tflite/Info.plist' to '/Users/karanshah/Library/Developer/Xcode/DerivedData/tflite_photos_example-hdnywmlpwpmthuekrlxjakvnxhzq/Build/Products/Debug-iphonesimulator/tflite_photos_example.app/Info.plist'
Target 'tflite_photos_example' (project 'tflite_photos_example') has process command with output '/Users/karanshah/Library/Developer/Xcode/DerivedData/tflite_photos_example-hdnywmlpwpmthuekrlxjakvnxhzq/Build/Products/Debug-iphonesimulator/tflite_photos_example.app/Info.plist'

Xcode Workspace settings > Change to Legacy Build System, it worked for me after that

Instruction by @iDuckDark seems to have done the trick. Here's some more background from Apple:
File > Workspace/Project Settings > Build System > Legacy Build System

@iDuckDark and @ml-illustrated you guys are correct. It worked for me thanks.


Fix add service reference in wcf folder

Change "Add Service Reference" to "Add > Service Reference" where applicable.
Whitespace changes (diff with hide whitespace on).

I am OOF next week but this is ready to go from my POV.


Switch to "main" branch

Remove usage of "master" term and update repository and confluent documentation as required

In progress


Low resolution image

Source information
Manganato 1.4.7
Source language
English
Steps to reproduce
k
Expected behavior
The reader should be HD
Actual behavior
The reader is blurry ang low resolution
Mihon/Tachiyomi version
Mihon 0.16.5
Android version
Android 14
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Still blur, but on web view its fine, it's only in the app that it's low res

App version: 0.16.5 (standard, 2a01a2a, 6, 2024-04-09T09:58:14Z)
Android version: 14 (SDK 34; build UKQ1.231207.002 release-keys)
Device brand: POCO
Device manufacturer: Xiaomi
Device name: munch (munch_eea)
Device model: 22021211RG
WebView: Android System WebView 125.0.6422.83

come to our discord for further help. this kind of issue can happen if you are using a custom rom

Okay


Feature 9 release

Expected Differences

[x] Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:

Pull Request Testing

[x] Describe testing already performed for these changes:

Reviewed changes with addition of NSF NCAR on the following pages based on the Sundog guidance:

https://fasteddy-model.readthedocs.io/en/feature_9_release/index.html
https://fasteddy-model.readthedocs.io/en/feature_9_release/Tutorial/getting_started.html

Reviewed the release notes:

https://fasteddy-model.readthedocs.io/en/feature_9_release/release_notes.html

Reviewed the zenodo additions:

https://fasteddy-model.readthedocs.io/en/feature_9_release/Tutorial/cases.html

https://fasteddy-model.readthedocs.io/en/feature_9_release/Tutorial/cases/MBL.html

[x] Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:

Please review the new menu structure with the addition of the Release Notes and review the Release Notes themselves.  I welcome any suggestions for modifications.

[x] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

[x] Do these changes include sufficient testing updates? [N/A]

[x] Will this PR result in changes to the test suite? [N/A]
If yes, describe the new output and/or changes to the existing output:

[x] Please complete this pull request review by [20240419].

Pull Request Checklist

[x] Complete the PR definition above.
[x] Ensure the PR title matches the feature or bugfix branch name.
[x] Select: Reviewer(s)
[x] After submitting the PR, select the :gear: icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
[ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
[ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

Could we please adjust the last paragraph of the Release notes intro text to read as
In addition to the initial code, this release includes a patch for building the system in the current NSF NCAR high performance computing environment on the Casper and Derecho platforms, along with other changes as detailed below:

Hi @jsauer-NCAR. Thank you for your attention to detail.    I pushed the release date forward to Monday to give you more time to review and to give me more time to focus on the release next week.

I have changed the language to be as you indicated. Thank you for your work on rephrasing that text.

In addition to the initial code, this release includes a patch for building the system in the current NSF NCAR high performance computing environment on the Casper and Derecho platforms, along with other changes as detailed below:

Great catch on the link https://github.com/NCAR/FastEddy-model/tutorials not working.  Navigating to that page in the repo it looks like it should actually be https://github.com/NCAR/FastEddy-model/tree/main/tutorials, however, I like your suggested change better anyway.  However, I did make one adjustment, which is instead of listing the link itself, I specified the text in the following way (also modifying the Zenodo reference as well).

Required tutorial resources including python utilities and Jupyter Notebooks are provided in the tutorials directory of the FastEddy-model GitHub repository with required data for the moist dynamics example available at this Zenodo record.

I thought it looked more professional to have the text instead of the link, but please let me know if you do not prefer it and/or would like me to change the wording.

Great catch on the 'no-title' reference and thank you for the screenshot, which was very helpful.  It looks like in order to fix that I needed to change the menu and get rid of the nice 'TUTORIAL' caption or have redundancy and list a "Tutorial" menu underneath the 'TUTORIAL' caption.  I was going to replace the 'TUTORIAL' caption with something else, but I couldn't really come up with anything worthwhile, so I just removed it.  Please be sure to take a look at the menu and navigate through to make sure it looks ok to you.

I'll request a re-review through GitHub and will plan to get back to this on Monday after you've had a chance to look it over and suggest any other changes.  Again, many thanks for your careful attention to ensuring everything is in good shape.

@jprestop Thanks for the adjustments and I like the use of text with hyperlink rather than URL in the documentation.  I went ahead and added the same formatting to the Zenodo record in the MBL.rst. via branch commit to feature_9_release.  PR with changes approved.


Cannot connect to Xdebug port inside Podman container

Version
Microsoft Windows [Version 10.0.19042.1348]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu 20.04 LTS
Other Software
Podman version 3.3.1
IntelliJ 2021.2.3 (Community Edition)
Repro Steps

Setup WSL2 setting to be able to build image for old CentOS version, create %USERPROFILE%/.wslconfig with the below config

[wsl2]
kernelCommandLine=vsyscall=emulate

Restart computer, inside Ubuntu check if vsyscall=emulate is in output
cat /proc/cmdline
-> initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=4 vsyscall=emulate

Inside Ubuntu install Podman, set shortname to quay.io (/etc/containers/registries.conf.d/000-shortnames.conf)

[aliases]
  # centos
  "centos" = "quay.io/centos/centos"

Run a CentOS 6 base instance with port mapping 8080 and 8000

podman run -td --name centos -p 8080:8080 -p 8000:8000 centos:6.10 bash -l

Install Java 1.8 and Tomcat 7

Setup Catalina option in /usr/share/tomcat/conf/tomcat.conf with the below option

CATALINA_OPTS="-Dlog.host=`hostname -s` -Xms256m -Xmx256m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+UseG1GC -Djava.security.egd=file:/dev/./urandom -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"

Start tomcat service using service tomcat start
On Windows host, run IntelliJ, setup remote JVM debug to Attach to remote JVM to localhost:8000
Run the above debug configuration

Expected Behavior
IntelliJ debugger can connect to port 8000
Actual Behavior
Unable to open debugger port (Connection refused: connect)
Diagnostic Logs
I use the same recipe for Docker with WSL2 backend, IntelliJ can connect to debug port, but not Podman running inside WSL2, so maybe there is some problem with forwarding TCP port.
Both Docker and Podman containers port 8080 (HTTP) can be accessed by using localhost:8080.
Here is netstat output for Docker and Podman port (I run them at the same time, so setting Docker on 8000 and Podman on 8001).
PS C:\Users\christopher.vo> netstat -a | findstr :8000
  TCP    <IP_ADDRESS>:8000           P50442:0               LISTENING
  TCP    [::]:8000              P50442:0               LISTENING
  TCP    [::1]:8000             P50442:0               LISTENING
PS C:\Users\christopher.vo> netstat -a | findstr :8001
  TCP    [::1]:8001             P50442:0               LISTENING

This works!
Thanks a lot for the suggestion, it still would be better to be accessed from localhost though...

Looks like it's the same problem as here: https://github.com/microsoft/WSL/issues/4851, and due to a difference in the way Podman and Docker bind their listening sockets you run into this.


1 test openalex api

Description
Began investigating the OpenAlex API and clustering the data. Run steps 1-3 to check the process; skip straight to steps 4-6 if you just want to see the analysis.
Main analysis steps:

pipeline/openalex_metaflow.py - this came from the AI genomics project, but with concepts relevant to child development added (of course)
notebooks/00_preprocess_openalex.py - this notebook (needs to be refactored and put in pipeline/ cleans the data resulting from step (1)
pipeline/embed_openalex.py - this creates embeddings for the titles and abstracts and stores them on s3
notebooks/01_openalex_clustering.py performs some initial clustering on the embeddings created at step (3)
notebooks/02_explore_concepts.py explores the unique concepts that appeared in the OpenAlex data. Not necessarily useful in future...
notebooks/concepts_per_text.py tries creating embeddings from the concepts that were attached to each abstract, and clustering the abstracts based on those embeddings.

Additional files:

openalex_search_by_title.py - this was used when cherrypicking titles to be exemplars for this project. math_augmented_reality.py is related - there happened to be a lot of papers about using augmented reality to teach mathematics
openalex_utils.py - currently this just contains a function for turning an inverted index back to normal text (this function was also stolen from AI Genomics!)

Fixes # (issue)
Instructions for Reviewer
In order to test the code in this PR you need to ...

Create a conda environment and install the libraries from both requirements_dev.txt and requirements.txt
See if you can run the notebooks described above

Please pay special attention to ...

Whether all the requirements are recorded
Whether the notebooks are OK: is there too little explanation; are they formatted OK (eg with regard to jupytext)

Checklist:

[ ] I have refactored my code out from notebooks/
[x] I have checked the code runs
[ ] I have tested the code
[x] I have run pre-commit and addressed any issues not automatically fixed
[ ] I have merged any new changes from dev
[x] I have documented the code

[x] Major functions have docstrings
[x] Appropriate information has been added to READMEs

[x] I have explained this PR above
[x] I have requested a code review

Hey @beingkk , I think most things are now done. Do you want to resolve the comments or do you want me to do that (if you trust I have resolved them!)?
I still need to move the concepts to the google doc but I think that can be a separate issue.


CAlphaOnly not working when loading pdb from rcsb

This might be me not understanding what's possible, but using this adjusted codepen of Alex's, I've loaded the same protein 3 times, showing from left to right: 1. from a data:// source (in red), 2. from a data:// source with cAlphaOnly:true (in yellow), and 3. from a rcsb:// source with cAlphaOnly:true (in cyan)
https://codepen.io/anon/pen/WPqgpv
I expected the last two to be the same, but loading with rcsb:// seems to ignore the cAlphaOnly setting. Have I just got something in the wrong place, is it a bug or is it something that's not doable?

looks like a bug, a workaround is the following
stage.loadFile( "rcsb://1crn.bb.mmtf", {cAlphaOnly:true}).then( function( o ){
    var p = new NGL.Vector3( -50, 0, 0 );
    o.setPosition( p );
    o.addRepresentation( "backbone", {color: "cyan"});
    stage.autoView();
} );


Enable --build-sil-debugging-stdlib for all of swift/stdlib/public

Previously it was enable only for swift/stdlib/public/core

@swift-ci smoke test


Add PRIMARY_DOMAIN support in urienv

Coverage decreased (-0.2%) to 90.42% when pulling 085f45107320be6abc6759589a3d3fc66d1c8f61 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage decreased (-0.2%) to 90.42% when pulling 085f45107320be6abc6759589a3d3fc66d1c8f61 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage decreased (-0.2%) to 90.42% when pulling 085f45107320be6abc6759589a3d3fc66d1c8f61 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage increased (+0.04%) to 90.651% when pulling fb3286d11467764f40980200f81489a9819fc598 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage increased (+0.04%) to 90.651% when pulling fb3286d11467764f40980200f81489a9819fc598 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage increased (+0.04%) to 90.651% when pulling fb3286d11467764f40980200f81489a9819fc598 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.

Coverage increased (+0.04%) to 90.651% when pulling fb3286d11467764f40980200f81489a9819fc598 on SAP:primary_domain into 8146c312c6f2ad0a21c940b3988c1f4bd4fb9bc6 on cloudfoundry-incubator:master.


Improve documentation around supported falco fields

/area documentation
What would you like to be added:
Expand and improve https://falco.org/docs/reference/rules/supported-fields/:
We could add full schemas for each syscall that are accessible via evt.arg.*  or at least refer to the source code file https://github.com/falcosecurity/libs/blob/master/driver/event_table.c.
Current mention is not explicit enough, I still don't know what valid field names are as typical end user (unless I am very familiar with the source code and each Linux syscall man page or deduct them from existing Falco rules):

"Event fields applicable to syscall events. Note that for most events you can access the individual arguments/parameters of each syscall via evt.arg, e.g. evt.arg.filename."

Related to https://github.com/falcosecurity/libs/issues/1134

Many users are also unfamiliar with the evt.arg.* fields and their meaning. Enhancing our documentation can address these issues by providing clear explanations and references to the concept of files in Linux.

On that note mesos can be removed as it is deprecated and I am not sure what span and fdlist classes actually represent and how you would use them in Falco. Can this be documented as well?
Why is this needed:
Improve UX for effective use of Falco.

We could add full schemas for each syscall that are accessible via evt.arg.* or at least refer to the source code file https://github.com/falcosecurity/libs/blob/master/driver/event_table.c.

Available evt.arg.* are listed in https://falco.org/docs/reference/rules/supported-events/ (now including the full list of flags, thanks to https://github.com/falcosecurity/falco-website/pull/1068).
We may cross link them for reference. Would it be enough? :thinking:

On that note mesos can be removed as it is deprecated and I am not sure what span and fdlist classes actually represent and how you would use them in Falco. Can this be documented as well?

mesos already removed
span is legacy stuff, but if we want to remove it we need a separate deprecation plan (that's out of the scope of this discussion, IMO)
fdlist is about monitoring multiple file descriptors during a poll()

The doc says Poll event related fields.. May it not be clear enough? :thinking:
In such a case, this should be addressed in libs https://github.com/falcosecurity/libs/blob/4d91fa1b8954bc3b8f95daa5496e998c15269f98/userspace/libsinsp/filterchecks.cpp#L8488

I added an explicit link (plus fixed a couple minor things). While the two pages are next to each other in the table of contents an extra link wouldn't hurt and will make the content easier to consume.


Use github actions to enforce prettier

Linting already runs in the Node.ci command. Just need prettier to get integrated.
https://github.com/bahmutov/gh-action-with-prettier
https://glebbahmutov.com/blog/trying-github-actions/

I was able to get prettier to run but the action to commit the changes failed complaining that master didn't exist.

Never gonna happen.


Cannot load DLL

Hi there,
We are using CouachDB Lite which has SQLitePCL as dependency.  Everything works perfectly locally on my development machine (windows 7).  However, when our CI Server (MS Server 2008 box) builds the .net MVC web project and deploy it to our Web Server (MS Server 2012 box), we getting an exception says:
The type initializer for 'Couchbase.Lite.Store.SqliteCouchStore' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'sqlite3': The specified module could not be found.
So I downloaded the latest version of 32bits sqlite3.dll from sqlite.org and dropped it into the folder overriding the one generated at build time, everything works...  I don't have much knowledge of PCL libraries but it looks like this might be similar to issue 44?  Just wondering if you could shed some light on how to solve this issue? Would referencing VC++ extension SDK in my project solve this issue?

The one from sqlite.org works because it is statically linked to the C runtime, and because you're on a desktop OS, where such static linking is allowed.
I'm in the process of overhauling the mechanism by which SQLitePCL.raw interacts with the native code, so this is all getting a fresh look as part of that effort.  I should probably just bundle sqlite3.dll's which have the C runtime lib statically linked when possible, since this is such a common case.  I would just have to think through the inconsistency of sometimes having the C runtime statically linked and sometimes not.

(responding to your second question)
Which two versions do you mean?  The 32bit and the 64 bit?

Ericsink,
Thanks for your prompt reply. Please ignore my second question. I figured it out :).  So for us, before the new version of SQLitePCL is released, I need to stop SQLitePCL from emitting sqlite3.dll and then bundle the one I downloaded in my project?  How do I stop SQLitePCL from creating sqlite3.dll?

Try setting the msbuild property UseSQLiteFrom to the value elsewhere
I'm not sure if that setting is supported in your situation, but it's the first thing to try.
How this works:
There is a .targets file in the nuget package which is used to copy the sqlite3.dll over to your build directory.  The UseSQLiteFrom property can be used to control whether that copy happens or not.
Anyway, if you don't want that sqlite3.dll copied over, you need to prevent that targets file from doing its thing.
Like I said, this will all be different (read: "better") in 0.9.

Thank you Eric. Looking forward to the new release!


Refactor StakePreview proposal

Description
Removes redundant variable and sets currentShares as a static property.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?

[ ] Test stake preview works as expected.

Visual context
n/a
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

@alter-eggo sorry Anastas, I think you were right about keeping it static. It's not ideal that this is the case, but it works for this component. I think it's important that the value doesn't update once the transaction goes through and that's why it was originally set as a ref rather than a computed property.


Fix Profile Project Card for Admin

Description
Fix the width of the project card in Profile Admin View so that it looks nice.
Screenshots

Additional information
No response

Use this layout for fixing it which is in visitor view of the profile

I will like to work on it. Please assign it to me.

@RajKanani1206 assigned you

hey, if this issue is still pending I can work on it?

Nope, I'm working on it and will be done by today.


Input is missed if the underlying ButtonInput only lasts for a single frame

Relevant system information

Bevy version 0.13.2
Leafwing-input-manager: 0.13.3
macOS 12.5.1 (on an early 2015 MacBook Air)

Description
Using leafwing-input-manager for mouse click input, a significant fraction of my trackpad taps get ignored. I.e. the just_pressed() function seems to never return true for some clicks. This does not happen when I physically click the touchpad.
I believe this is due to the fact that the tap creates a press and release event simultaneously, ie just_pressed and just_released of bevy_input are true in the same frame, as the following logs show. Therefore I assume you clear the pressed state again before any schedule has time to read it. For the sake of the user experience I think it would be nicer if the pressed state would be forced to last for at least one frame/update.
Additional information / logs
I ran the following system:

fn log_clicks(
    frame: Res<bevy::core::FrameCount>,
    leafwing: Res<ActionState<Action>>,
    bevy: Res<ButtonInput<MouseButton>>,
) {
    if leafwing.just_pressed(&Action::Build) {
        debug!("{frame:?} leafwing click");
    }
    if leafwing.just_released(&Action::Build) {
        debug!("{frame:?} leafwing release");
    }
    if bevy.just_pressed(MouseButton::Left) {
        debug!("{frame:?} bevy click");
    }
    if bevy.just_released(MouseButton::Left) {
        debug!("{frame:?} bevy release");
    }
}

with the Action::Build being mapped to (Self::Build, Single(Mouse(MouseButton::Left)))
And got the following (shortened) output:
// those are 3 normal clicks
..:43.767761Z: Res(FrameCount(486)) leafwing click
..:43.767798Z: Res(FrameCount(486)) bevy click
..:44.019270Z: Res(FrameCount(501)) leafwing release
..:44.019294Z: Res(FrameCount(501)) bevy release
..:50.605571Z: Res(FrameCount(835)) leafwing click
..:50.605597Z: Res(FrameCount(835)) bevy click
..:50.885160Z: Res(FrameCount(852)) leafwing release
..:50.885212Z: Res(FrameCount(852)) bevy release
..:54.312468Z: Res(FrameCount(1057)) leafwing click
..:54.312493Z: Res(FrameCount(1057)) bevy click
..:54.649199Z: Res(FrameCount(1077)) leafwing release
..:54.649222Z: Res(FrameCount(1077)) bevy release
// here I switched to tapping
..:00.345182Z: Res(FrameCount(1418)) bevy click
..:00.345213Z: Res(FrameCount(1418)) bevy release
..:02.616926Z: Res(FrameCount(1554)) leafwing click
..:02.617046Z: Res(FrameCount(1554)) bevy click
..:02.634939Z: Res(FrameCount(1555)) leafwing release
..:02.634971Z: Res(FrameCount(1555)) bevy release
..:05.693888Z: Res(FrameCount(1738)) bevy click
..:05.693927Z: Res(FrameCount(1738)) bevy release
..:08.082196Z: Res(FrameCount(1881)) bevy click
..:08.082226Z: Res(FrameCount(1881)) bevy release
..:10.588752Z: Res(FrameCount(2031)) bevy click
..:10.588776Z: Res(FrameCount(2031)) bevy release
..:12.744516Z: Res(FrameCount(2160)) leafwing click
..:12.744539Z: Res(FrameCount(2160)) bevy click
..:12.762709Z: Res(FrameCount(2161)) leafwing release
..:12.762734Z: Res(FrameCount(2161)) bevy release
..:15.436291Z: Res(FrameCount(2321)) bevy click
..:15.436315Z: Res(FrameCount(2321)) bevy release
..:17.875363Z: Res(FrameCount(2467)) leafwing click
..:17.875386Z: Res(FrameCount(2467)) bevy click
..:17.893768Z: Res(FrameCount(2468)) leafwing release
..:17.893796Z: Res(FrameCount(2468)) bevy release

Even more information
I have also run the pump_events example of winit, which logs all events every 16ms and got interesting results:
Sometimes when I tap, no Update or RedrawRequested event are logged between the pressed and released:
RedrawRequested
Update()
RedrawRequested
Update()
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>236328 } }
MouseInput { device_id: DeviceId(DeviceId), state: Pressed, button: Left }
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>6484375 } }
MouseInput { device_id: DeviceId(DeviceId), state: Released, button: Left }
RedrawRequested
Update()
RedrawRequested
Update()

Sometimes there is a single update between the two tap events:
Update()
RedrawRequested
Update()
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>236328 } }
MouseInput { device_id: DeviceId(DeviceId), state: Pressed, button: Left }
RedrawRequested
Update()
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>6484375 } }
MouseInput { device_id: DeviceId(DeviceId), state: Released, button: Left }
RedrawRequested

And for comparison, here is how it looks when I casually press the touchpad instead of tapping.
Update()
RedrawRequested
Update()
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>236328 } }
MouseInput { device_id: DeviceId(DeviceId), state: Pressed, button: Left }
RedrawRequested
Update()
RedrawRequested
Update()
RedrawRequested
Update()
RedrawRequested
Update()
RedrawRequested
Update()
RedrawRequested
Update()
RedrawRequested
Update()
CursorMoved { device_id: DeviceId(DeviceId), position: PhysicalPosition { x:<PHONE_NUMBER>0859375, y:<PHONE_NUMBER>6484375 } }
MouseInput { device_id: DeviceId(DeviceId), state: Released, button: Left }
RedrawRequested
Update()
RedrawRequested

Agreed, I think this should be considered a bug.


Expose metrics through spring boot actuator

The module allows exposing metrics through the Spring Boot actuator in a Spring Boot project.
To make the configuration works you just need to add @EnableVictoriaMetricsEndpoint annotation in your project configuration and add "victoriametrics" to the list of endpoints exposure like:
management.endpoints.web.exposure.include=victoriametrics, health in the application.properties or application.yml

Awesome, thank you. Do you know any places we should let people know that we now have the SpringBoot integration (springboot forums / talks)?

I am going to write an article how to use it.


[Audio player] update design spec

As a [user role below]:

developer

I need to:

have the audio player design specs

so that I can:

correctly change the audio player component to meet accessibility requirements
Additional Information

See the epic Audio player #9256 for the overarching descriptions of the work.

Acceptance Criteria

[ ] A Figma file is created or updated with the Audio  design and specs
[ ] Create a Box folder for the ?component name? (if not already there)
[ ] The design specs and pdf version are added to the Box folder
[ ] Add Box folder link to the website content if it exists

[https://app.zenhub.com/files/193129061/8fc4e33b-b56b-4b24-b330-d1a8624cd1f9/download](Sample Component page with callouts)

Hi!
I just thought it would be nice to add some context and background on this task about the specs that were used to create the current audio-player.
In #4083 - specifically here - there is a link to a box folder called "References and inspirations" and under it there is this sketch file that contains studies for a podcast-page or micro-site page containing an audio-player.
After some calls with Shi Xie and our stakeholders around those ideas - everyone agreed with the "Desktop Version" without the download transcript button - being the best experience.
I'm not sure if it may help around upgrading / migrating from sketch to figma, but again, thought it would be nice to at least have some backstory around this 😃

Hi @tweenn!
In order to upgrade the Audio player from experimental to production, we had our accessibility team review and test the component. They found a few accessibility issues and have logged them on our github board, you can see them all under the Epic Audio player upgrade to production #9256
This design task is specifically addressing the accessibility issues and creating/updating the specs for things that were not documented in the original spec sheet.
I hope that context helps! @kennylam and I will be scheduling some time to review the requirements with you and your team as soon as I wrap up the spec updates

@tweenn Here is a link to the specs in Figma you should be able to view them there!
I will also add a PDF of the specs to the Box folder


[WIP] Added tests for utils/analytics

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew tests with your changes locally?

Please review, @mistydemeo
Thanks!

A test failure:
Failures:
  1) Utils::Analytics::os_prefix_ci when anonymous_os_prefix_ci is not set returns OS_VERSION and prefix when HOMEBREW_PREFIX is not /usr/local
     Failure/Error: expect(described_class.os_prefix_ci).to include("#{OS_VERSION}, non-/usr/local")
       expected "macOS 10.12.5, CI" to include "macOS 10.12.5, non-/usr/local"
     # ./test/utils/analytics_spec.rb:7:in `block (4 levels) in <top (required)>'
     # ./test/spec_helper.rb:91:in `block (2 levels) in <top (required)>'
     # ./vendor/bundle/ruby/2.0.0/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
Finished in 7 minutes 20 seconds (files took 4.54 seconds to load)
971 examples, 1 failure
Failed examples:
rspec ./test/utils/analytics_spec.rb:6 # Utils::Analytics::os_prefix_ci when anonymous_os_prefix_ci is not set returns OS_VERSION and prefix when HOMEBREW_PREFIX is not /usr/local

@MikeMcQuaid please review. Thanks!
Also, here is it alright to add a remove cache method for @anonymous_os_prefix?

Also, here is it alright to add a remove cache method for @anonymous_os_prefix?

Yes, thanks.

Thanks!

Well done again @mansimarkaur 😍


Fix PostCSS condition for Review app “pseudo-classes” plugin

This PR restores the postcss-pseudo-classes PostCSS plugin for review app stylesheets
We use the plugin to generate classes (see below) for the following:
:link
:visited
:hover
:active
:focus

Unfortunately our config hasn't matched minified stylesheets (such as app.min.css) since merging:

https://github.com/alphagov/govuk-frontend/pull/3050

This PR includes:

Fix PostCSS condition for Review app “pseudo-classes” plugin
We can match all '**/app/assets/scss' child stylesheets regardless of name or extension

Adjust Sass task to run PostCSS first before renaming
For some Gulp streams we were renaming/moving files before PostCSS could check the path

Move PostCSS cssnano to default plugins
We minify our CSS by default so can simplify our tests

Unfortunately it doesn't seem to be transforming all selectors as expected. (The :focus examples in your screenshot aren't styled correctly, for example.)
Complex selectors seem to only be getting partially transformed — in the below case,:hover is getting transformed but :focus isn't.
/* Before */
.govuk-radios--small .govuk-radios__item:hover .govuk-radios__input:focus + .govuk-radios__label:before {}

/* After (other selector output omitted for brevity) */
.govuk-radios--small .govuk-radios__item.\:hover .govuk-radios__input:focus + .govuk-radios__label:before {}

I think this may be a bug with postcss-pseudo-classes' restrictTo option. Removing that part of the PostCSS configuration generates the expected selectors in the above example, but also results in the janked :not selectors that the old configuration warned about.
Simply swapping out for the old configuration doesn't seem to work in all cases either, as the :not selector jankiness seems to remain. Here the :not(:disabled) pseudo-selector shouldn't be transformed, as we've blacklisted it, but it's being transformed anyway.
/* Before */
.govuk-radios--small .govuk-radios__item:hover .govuk-radios__input:not(:disabled) + .govuk-radios__label:before {}

/* After (other selector output omitted for brevity) */
.govuk-radios--small .govuk-radios__item.\:hover .govuk-radios__input.\:not\(.\:disabled\) + .govuk-radios__label:before {}

This happens with both the previous config (blacklist: [':not(', ':disabled)']) and with a more specific, targeted version (blacklist: [':not(:disabled)']).
I'm not sure why the messed up :not selectors keep happening despite being blacklisted, nor am I sure whether this was an existing issue or is a regression, but either way it's probably not the highest priority given this is code specific to the review app and not something end users are using.
I'm going to try and make reduced test cases for each to see if they're bugs inherent in postcss-pseudo-classes and will report them if so.

Thanks @querkmachine, great spot—another bug!
Looks like we need to tread very carefully with these legacy PostCSS plugins
I've fixed it by letting them run before we minify 🙌
(The consolidated selectors that CSSNANO outputs must be too complex for postcss-pseudo-classes)


Added the Jekyll Friday Theme to the directory.

Here's a pull request for my submission to the themes directory, for my  own them 'Friday Theme', which I created for my personal web site at http://www.freytag.org.uk. I published the theme to GitHub and it has been sued by a few people since then, so I think it is reliable enough to be shared more widely. I look forward to your thoughts!

Thanks!


feat: add inbox icon

TDESKAPP-558
Description
Add inbox icon
How to test
Open http://localhost:9001/?path=/story/components-icons--icons and search for inbox icon.
Screenshots

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

[x] codemod is created and showcased in the changeset
[x] test alpha package of Picasso in StaffPortal

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

I checked the Happo screenshot and it's looking fine.
There's only a small change that we need to fix on the changeset and we good to go!
Thanks for your contribution @tiagoporto! :+1:
We appreciate it!


change ft and meoh capacity max according to bus1

Before asking for a review for this PR make sure to complete the following checklist:

[x] Workflow with target rule ariadne_all completes without errors
[x] The logic of export_ariadne_variables has been adapted to the changes
[ ] One or several figures that validate the changes in the PR have been posted as a comment
[ ] A brief description of the changes has been added to Changelog.md
[x] The latest main has been merged into the PR
[ ] The config has a new prefix of the format YYYYMMDDdescriptive_title

This implementation:

with min and max constraints:
unconstrained:

2020:

model builds total of 131 MW methanolisation
DE0 2 methanolisation-2020     11.0
DE0 3 methanolisation-2020    100.0
DE0 4 methanolisation-2020     18.0
DE0 5 methanolisation-2020      1.0

2025:

model builds no more methanolisation and all components with p_nom < 10 are not taken into next investment period according to snakemake.params.threshold_capacity (in add_brownfield)
remaining capacity: 130 MW
DE0 2 methanolisation-2020     11.4168
DE0 3 methanolisation-2020    100.4576
DE0 4 methanolisation-2020     18.2657

2030:

first year with active constraint of <= 5700
model builds no more capacity: shadow value of constraint = -2.411570e-08

2035:
model builds up until the constraint limit 5699 and wants to build more: shadow value of constraint = 	-3414.1
DE0 0 methanolisation-2035     438.0
DE0 4 methanolisation-2035    3017.0
DE0 7 methanolisation-2035    2115.0
DE0 2 methanolisation-2020      11.0
DE0 3 methanolisation-2020     100.0
DE0 4 methanolisation-2020      18.0
2040:

capacity build in 2020 is at end of lifetime
model could build 131 more but sees no strong need to do so? -> shadow value of constraint = -0.084
capacity: 5700 - 131 = 5569
DE0 0 methanolisation-2035     438.0
DE0 4 methanolisation-2035    3017.0
DE0 7 methanolisation-2035    2115.0

2045:

model stll sees no need to build up the remaining 131 MW again
shadow value of constraint: -0.008
capacity same as in 2040

-> constraint seems to work fine

FT is also fine:
2020
meoh capacity (bus1) : 115.38 GW
meoh capacity (bus0) : 131.31 GW
ft capacity (bus1) : 0.00829432587329681 GW
ft capacity (bus0) : 0.010380883445928423 GW
2025
meoh capacity (bus1) : 114.38 GW
meoh capacity (bus0) : 130.17 GW
ft capacity (bus1) : 0.0052032704984440546 GW
ft capacity (bus0) : 0.006512228408565775 GW
2030
meoh capacity (bus1) : 114.35 GW
meoh capacity (bus0) : 130.14 GW
mu value of max costraint : -2.4115696635667474e-08
ft capacity (bus1) : 1.9693473919195225e-06 GW
ft capacity (bus0) : 2.4647651963948966e-06 GW
mu value of max costraint : -5.9584081071868524e-08
2035
meoh capacity (bus1) : 5008.59 GW
meoh capacity (bus0) : 5700.0 GW
mu value of max costraint : -3414.162795625043
ft capacity (bus1) : 1997.499906730292 GW
ft capacity (bus0) : 2499.9998832669485 GW
mu value of max costraint : -9557.476697961874
2040
meoh capacity (bus1) : 4894.12 GW
meoh capacity (bus0) : 5569.72 GW
mu value of max costraint : -0.08426526053332607
ft capacity (bus1) : 1997.49982239351 GW
ft capacity (bus0) : 2499.9997777140297 GW
mu value of max costraint : -27544.85509900011
2045
meoh capacity (bus1) : 4894.11 GW
meoh capacity (bus0) : 5569.71 GW
mu value of max costraint : -0.008418827120426268
ft capacity (bus1) : 1997.4892921854039 GW
ft capacity (bus0) : 2499.986598479855 GW
mu value of max costraint : -188.76359809320329


An error in documentation

I ran into an error when I tried to implement a default model as shown in the documentation.
inference.posterior = posterior_alr_to_clr(inference.posterior)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_1733275/737458355.py in <module>
      1 #convert your BIRDMAn fit into this data structure.
----> 2 inference.posterior = posterior_alr_to_clr(inference.posterior)

TypeError: posterior_alr_to_clr() missing 3 required positional arguments: 'alr_params', 'dim_replacement', and 'new_labels'

It turns out the documentation is out of date, and this worked for me:
inference.posterior = posterior_alr_to_clr(
    inference.posterior,
    alr_params=["beta"],  # the default NB model has only beta in ALR coordinates
    dim_replacement={"feature_alr": "feature"},  # the default NB model assigns 'feature_alr' as the dimension name
    new_labels=nb.feature_names  # replace the old labels (all the feature names except the first) with all the feature names
)

Thanks Gibs!

I ran into an error from jindongmin's suggestion above.
inference.posterior = posterior_alr_to_clr(
    inference.posterior,
    alr_params=["beta"],
    dim_replacement={"feature_alr": "feature"},
    new_labels=nb.feature_names
)

Traceback (most recent call last):
  File "<stdin>", line 5, in <module>
NameError: name 'nb' is not defined. Did you mean: 'np'?

nb should be nb_lme
inference.posterior = posterior_alr_to_clr(
    inference.posterior,
    alr_params=["beta"],
    dim_replacement={"feature_alr": "feature"},
    new_labels=nb_lme.feature_names
)


[feat] add a common method search list to chose

such as:

ObjectInputStream readObject
Runtiume exec
...

After thinking, this function seems unnecessary


STOR-1038: Reconcile Storage and ClusterCSIDrivers in the guest clusters

What this PR does / why we need it:
Overwrite any user changes in Storage and ClusterCSIDriver CRs that are managed by CPO and other operators in the hosted control plane.
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm
/cherry-pick release-4.12

/approve

/cherry-pick release-4.12
It should be clean after https://github.com/openshift/hypershift/pull/1932


[select-star] Adding optional schema to view

This PR updates a couple of aspects of the select-star logic including:

Adding an optional schema to the /select_star route.
Making the /select_star route return a JSON response as opposed to HTML.
Ensured that the /select_star route includes a partition (if appropriate).
Ensured that the /table route includes a partition (if appropriate)†.
Added a where_latest_partition for Presto.
Changed the default Hive where_latest_partition behavior to return the first partition if the table is multi-partitioned. Previous it would return False is the table was partitioned but contained more than one partition key.

† Note this improves the performance of the SQL Lab preview by including a partition predicate even though there is additional overhead of finding the latest partition. At Airbnb for a large daily partitioned table with several years of data this reduced the query time from ~ 75 seconds to ~ 3 seconds. This also helps to ensure that the data preview is associated with the partition (guaranteed for the single partitioned case) shown in the UI.

to: @graceguo-supercat @kristw @michellethomas @mistercrunch @timifasubaa @williaster

Codecov Report

Merging #6051 into master will increase coverage by 0.1%.
The diff coverage is 46.66%.

@@            Coverage Diff            @@
##           master    #6051     +/-   ##
=========================================
+ Coverage   77.74%   77.84%   +0.1%
=========================================
  Files          46       46
  Lines        9400     9412     +12
=========================================
+ Hits         7308     7327     +19
+ Misses       2092     2085      -7

Impacted Files
Coverage Δ

superset/views/core.py
73.92% <100%> (+0.18%)
:arrow_up:

superset/db_engine_specs.py
55.61% <27.27%> (+0.79%)
:arrow_up:

superset/connectors/sqla/models.py
81.2% <0%> (+0.75%)
:arrow_up:

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 93fe453...99c7819. Read the comment docs.

LGTM


[Bug]: Avoid reducing paddings in a background-free zone when at least one zone in a section has a background on

Is there an existing issue for this?

[X] I have searched the existing issues

Description
With conditional paddings depending on visual separation it might make sense to reintroduce another constraint: we don’t reduce/remove paddings in a background-free zone as long as at least one zone in a section has background on. This will prevent situations when a content of bordering zones is misaligned.
Steps To Reproduce

add multiple zones to a section
Turn off the background on one of the zones and observe the shift in the UI

Public Sample App
No response
Environment
Deploy Preview
Severity
Low (Inconsistent UI/UX)
Issue video log
https://theappsmith.slack.com/files/U03JBF3Q8JE/F06RQK11TNY/cleanshot_2024-03-27_at_20.46.02.mp4
Version
cloud

related to #32924

an additional side-effect of this: distribution handles appear closer to widgets on a background-free zone

@riodeuno are you picking this up?
This has been moving through sprint but still have not closed.


qt-creator: Add version 6.0.1

Latest versions of qt creator do not support x86 so removed the autoupdate

Closes #7548

I'm not sure if this is the way to go, please let me know if I need to change anything.

Please remove the 32bit version

/verify


Pull Authorizers out of Roles into its own class, and add authorizers…

… to admin controller methods.
Description
Authorizers cannot just be an enum because annotations require values to be constants and a toString() method on the enum class doesn't work.
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Is this too much? Could we just use a list of static strings in an Authorizers class (public static final String UAT_ADMIN = "uatadmin";)?


Severe cache bug during submission on deposit

Describe the bug
When a new submission that contains a relationship issue is created a severe cache bug occurs which doesn't allow to deposit the item.
Essentialy if all the changes in the submission have been saved, before to deposit the application try to retrieve the submission object again to check if the item can be deposited (it happens here). In the case the changes of the submission are not yet saved before to add a new relationship field they are saved when the relationship is added. This probably cause a cache problem and when the user try to deposit the item the application can't retrieve the updated submission object (it happens here) because it gets a remote data with status error stale and this leads to an endless loop of request to REST server.
To Reproduce
It can be reproduced in the sandbox environment also

as submitter try to create a new publication in the collection Publication 2 which have a relationship field
start to fill out the form following this order and without clicking on save:

accept the license
add the titlke and the date that are mandatory
add an author
upload a file

click on deposit
the submission is hanging forever and in the network endless requests are sent

https://github.com/DSpace/dspace-angular/assets/2486489/a1f132d9-798f-4677-b038-cb2fe933056f
Untitled_ Oct 26, 2023 9_46 AM.webm
Expected behavior
The submission should be deposited
Related work
It's important to retrieve every time a fresh submission object because of the bug already resolved https://github.com/DSpace/dspace-angular/issues/1502

@atarix83 The problem seems to be caused by the reRequestOnStale feature, if you set that to false, in the call you mentioned, the problem goes away.
Since the submission always manually re-retrieves the submission objects it shouldn't be necessary anyway so disabling it shouldn't affect the functionality.
However I do think there's still a bug in that reRequestOnStale feature, in a complicated case like this. If i log the number of calls to the findByID method for that same submission object, I count 6.  Some with reRequestOnStale true, others false. Then we also manually re-retrieve the object in the effect (by setting useCachedIfAvailable to false). I suspect this causes an edge case where the request that one of these subscriptions makes gets immediately set to stale by one of the others, causing the reRequestOnStale to trigger, which sets it to stale again, causing an infinite loop
So I'd try the workaround of disabling reRequestOnStale in the effect, see if it doesn't break anything, and if it doesn't merge that now. But leave the issue open to look into in more detail later

thanks @artlowel  for your analysis. i can confirm your solution works.
I've also find out that if i change the request by including the item and collection embeds it works as well even with reRequestOnStale as true.
I've tried it becuase i notice that there are two requests done endlessly one just the submission id and one with also item and collection embed

Maybe it can help to better understand the bug.
In the end i agree to temporary fix the issue in one of the two way and then to try to find out the problem in this edge case

I'm positive, that this is related to #1924. I observed the same pattern of endlessly re-requesting on stale


Are encoded big integers allowed to have leading zeroes?

I do realise I'm asking alot of questions about MTProto but this seems to be the place where everyone who knows anything is.
Just wondering if I can leave leading zeroes in for optimization's sake.

Where do you want to keep leading zeros? If you want to properly calculate RSA fingerprint, then there should be no leading zeros in numbers, otherwise the fingerprint will be completely different.

For example when I send the values pq, p and q for SendReqDhParams

I don't think that leading zeroes are allowed there.

Could you expand on why that might be the case? Just so I can have a better understanding

Because it works so. There is no reason to accept numbers with leading zeros in req_DH_params as there is no reason to accept numbers in binary, octal or hexadecimal form there.


Poke the new usage stat file

This helps give the ChromeOS team a vague view of the approximate number of active crouton machines (who have opted into ChromeOS stats reporting).  This single-bit stat is not associated with users, machines, or the actual usage of crouton.  If this terrifies you, you can block the stat by setting CROUTON_DISABLE_STATS in your environment (the variable is plural but there are no other stats).
https://crbug.com/989219 for reference

CR+2


Problems converting Java.ArrayList to NDArray in scala.

Issue Description
I'm trying to convert a Java.util.List<java.Float> into a NDArray:
I have the following scala code:
val vector: util.List[Float] = model.getVector("word")
val scalaArray = vector.asScala.toArray

Then if i try to convert it, with scalaArray.toNDArray() i with the implicit function it doesn't find the implicit conversion:
Then i tried then i tells me that it cannot convert java.Float to an NDArray, since this is a java object But scala has no real way to convert it explicitly to an:
floatArray2INDArray(scalaArray).toNDArray()

and even this:
floatArray2INDArray(scalaArray.map(_.toFloat)).toNDArray()

Eventually i just solved it in java code like this:
    public INDArray getWordVector(String word){
        float[] buffer = new float[model.getDim()];
        List<Float> vector = model.getVector(word);
        for(int i = 0;i < model.getDim() ;i++){
            buffer[i] = vector.get(i);
        }
        return Nd4j.create(buffer);
    }

a scala oneliner solution is where to option allows you to unbox the Float object into a primitive float:
    val scalaArray = vector.asScala.toArray.flatMap(float => Option(float).map(_.toFloat)).toNDArray

expected behavior
Direct conversion functions between Seq/ List containers To NDArrays. Since most java/ scala code operate on List/Seq and not the Array.

encountered behavior

It is hard to convert from a boxed java.Float to a scala.Float in scala.
There are no functions in java to from a java.List to Float[] without manually copying.
I understand that this is a problem on Scala its side because opaque boxing and unboxing of a Float.
On the java side it is the missing functions to convert between Java List to Array and functions to go from java Float[] to float[]
Version Information
Please indicate relevant versions, including, if relevant:

Deeplearning4j version
ND4j 0.8.0
ND4s 0.8.0

Contributing
If you'd like to help us fix the issue by contributing some code, but would
like guidance or help in doing so, please mention it!
Since i could write convenience code to do the conversions from the scala types and the java list. But these probably have to be documented that they are rather inefficient because of the way they work.

That's a general limitation in Java as well. Since we need to copy the values from arrays anyway, the equivalent with List wouldn't be that inefficient. Additional factory methods are welcome! Please send your pull request. :)

I will be right on it and try to implement it into a rather generic way. :) So if i see it correctly the right way will be to copy the values from the list directly into an NDArray without creating an intermedian array.

@borissmidt you can have that just be zero if you want. I'm more inclined to treat this similarly to a float array in java.

@agibsonccc I see 2 problems for which i will have to find a solution,
The first one is Type erasure, so i'm unable to overload the function for a List and List since the jvm will be unable to see the difference after compilation.
Another problem is that these functions will have to be implemented in the abstract factory but also in the BaseNdArrayFactory and its childeren.
To solve the second problem, i could just copy the List to an array and then delegate the call to the usual functions.

I already created a pull request that solves this problem for scala. But i still have to tackle the java case.

@agibsonccc, I'm still interested to implement these conversion functions, But i have to give them different names to avoid type erasure of the java.util.List.  Is this a reasonable solution or do you have a better idea to do this?
My proposed solution would be to just copy it to a primitive array and then use the existing functions. Since this would only cause in a small change.

Yeah that would be fine.

In Scala, you can just:

scala> import scala.collection.breakOut
import scala.collection.breakOut
scala> import scala.collection.JavaConverters._
import scala.collection.JavaConverters._
scala> def f(l: java.util.List[java.lang.Float]): Array[java.lang.Float] = l.asScala.map(identity) (breakOut)
f: (l: java.util.List[Float])Array[Float]

Unboxing should not be needed if you avoid boxing, but if you don't there is an unsafe Float.box you can use in cases you are certain you boxed.

That's not the issue, AFAIU. We need a float[], but we're getting a Float[] or something. Unboxing all elements isn't very efficient.

The original problem is just that most of the java works use the default collections like List. But java its collections can only contain elements of type object, But the primitives are not objects. Thus you cannot go from List to a primitive array. While List is used by many java libraries but float[] isn't.
Thus it would be useful for the library to have convenience functions to convert from List to NDFloatArray.

So, rather than speaking besides the point I'd rather equip you with tools to make things happen.
In Scala, Java Arrays are Scala ones too:
scala> import java.util.Arrays
import java.util.Arrays
scala> var m = scala.Array(8,7,6,5,4,3)
m: Array[Int] = Array(8, 7, 6, 5, 4, 3)
scala> Arrays.sort(m)
scala> m
res2: Array[Int] = Array(3, 4, 5, 6, 7, 8)

in Scala, scala.Float, a primitive value type, is convertible to a java.lang.Float through an implicit conversion in Predef (everybody gets these implicits):
https://github.com/scala/scala/blob/2.12.x/src/library/scala/Predef.scala#L455
Boxed java.lang.Float objects are auto-convertible to a scala.Float:
https://github.com/scala/scala/blob/2.12.x/src/library/scala/Predef.scala#L472
And breakout lets you implicitly invoke the basic collection construction for translating without adding one more traversal to your collection construction (as long as there's one).
So, in scala, as this issue started out with, you get:
scala> def f(l: List[java.lang.Float]): Array[Float] = l.map((x)=>x:Float) (breakOut)
f: (l: List[Float])Array[Float]

(which implicitly applies Float2float)
And coming from a java list:
scala> import scala.collection.JavaConverters
import scala.collection.JavaConverters

scala> def f(l: java.util.List[java.lang.Float]): Array[Float] = l.asScala.map((x)=>x:Float) (breakOut)
f: (l: java.util.List[Float])Array[Float]

(the map is here because it's still applying Float2float)
If you want to do this in Java, you'll need to unbox the java.lang.Float elements while filling your float[], because, well, that's all you have. I wasn't saying anything more controversial that : unbox if all you have is boxed objects, and take the primitive elements otherwise.

So should i add the convenience functions to the library? But  i'm still confused on how to handle the null pointer.
Is it a yes i would like to have a null replaced by 0. Or is an exception tolerable since the scala implementation would just throw the exception?

You should add those convenience functions. My opinion is you should throw on null, both in Java and Scala. The functions I have above will throw on null, but will have tremendously better performance than ones which null-check with Option (the object creation alone is intractable at the data volumes we're envisioning).
In Scala, your implementation can look like the above, in Java, it should look like the similar convenience function from Guava https://github.com/google/guava/blob/master/guava/src/com/google/common/primitives/Floats.java#L414
(in fact, if you look around, you'll see we have Guava in dependencies, and you can use just that).

Sir @raver119
I tired in Jython to create a double array:
myArray = jarray.array(vector, java.lang.Double),  where vector is  <type 'java.util.ArrayList'>. the type of myArray is <type 'array.array'>. So when i pass it to the create function like that nd = Nd4j.create(myArray)`, i get the following exception:
nd = Nd4j.create(myArray)
TypeError: create(): 1st arg can't be coerced to int[], float[], double[][], float[][], org.nd4j.linalg.api.buffer.DataBuffer, int, double[]

Fixed with merge of #2043


Can't simultaneously add multiple tconsts that resolve to same name

Describe the bug
Fargo the movie and Fargo the TV series have different tconst IDs.
tt0116282	movie	Fargo
tt2802850	tvSeries	Fargo
If both are put in one .tconst file they get disambiguated into Fargo (1996) and Fargo (2014) when building a local database.
Since they have different tconst IDs it seems you should be able to feed them both to any script that takes tconst IDs and it would process both. It doesn't, forcing you to pick one.
To Reproduce
./createTconstFile.sh tt0116282 tt2802850 or ./createTconstFile.sh tt0116282 Fargo
Expected behavior
Both tconst IDs should be processed and disambiguated.
Additional context
This is unlikely to happen in normal use, most searches are for the show title, not a tconst.

This is easily resolved by running the command twice, once with each tconst ID. There are no ill effects other than having to type two commands.
Making this work as expected would overcomplicate too many scripts.

This is easily resolved by running the command twice, once with each tconst ID. There are no ill effects other than having to type two commands.
Making this work as expected would overcomplicate too many scripts.


Finished LED code v1

Adds LED Functionality,
Can Set Leds using SetState from LED class to set LED strip.
made first set of colors to represent Shooter and intake state.
Resolves #64

/format


All The TestCases are done

verifyDragAndDrop assertion is not correct. Also, instead of writing same BeforeMethod and AfterMethod in each test class, those methods could be in TestBase to reduce some code. Please fix these issues in your next commit.


Java.Util.Random

10/06

Discuss about current status of native
Implement all functions inside Random and create test case also
Discuss about mobile's architecture


2.4 backport

Essentially a fast forward without 2.5 version change

Side effect is usage of incorrect tags, however those will be corrected by the build process anyway so I'm gonna skip fixing all affected commits

@jcechace Applied, thanks. COuld you please check if all the Jiras referred in commits have 2.4.1.Final fix version set and set it if not? Thanks

Will do.

@jpechane done


🔌 Plugin: Argo - part 1

Goals

Evaluate existing community plugin to find issues and opportunities for improvement & enhancement
This epic aims to provide additional capabilities to the existing Roadie Argo plugin

Identify issues that we want to address with existing upstream plugin

Issue with passing token
When there are issues with Argo, include error messages
Provide a link to the Argo UI
Update the ArgoCD history card to include the following 5 columns (see image below of deployment history view from OpenShift Console Environments page - we want the same display, but omit Environment):

Deployment status (need to confirm proper design pattern here, green/red dot maybe?)
Deployment time
Message
Author
Revision SHA

Issues in Epic

[x] https://github.com/janus-idp/backstage-plugins/issues/84
[x] https://github.com/janus-idp/backstage-plugins/issues/110

Link to upstream

https://github.com/RoadieHQ/roadie-backstage-plugins/issues/881

Provides a deployment history view
I

Issue: https://github.com/RoadieHQ/roadie-backstage-plugins/issues/881 has been done.


Vite: works locally, but does not work in production

I got

Uncaught ReferenceError: document is not defined

on production, but everything is ok locally
vite.config.ts
import eslintPlugin from "@nabla/vite-plugin-eslint";
import react from "@vitejs/plugin-react";
import autoprefixer from "autoprefixer";
import dns from "dns";
import postcssLogical from "postcss-logical";
import { defineConfig } from "vite";
import svgr from "vite-plugin-svgr";

dns.setDefaultResultOrder("verbatim");

export default defineConfig({
  assetsInclude: ["**/*.glb", "**/*.gltf", "**/*.hdr", "**/*.riv"],
  server: {
    host: "localhost",
    port: 3000,
  },
  plugins: [react({ fastRefresh: false }), svgr(), eslintPlugin()],
  worker: { plugins: [react()] },
  esbuild: { jsx: "automatic" },
  css: {
    postcss: {
      plugins: [autoprefixer, postcssLogical],
    },
  },
});

also not working with @vitejs/plugin-react-swc

The problem occurs because I use the Html component
After building, styles are still inserted by injecting

Also, it doesn't work if something uses raf


[Snyk] Upgrade puppeteer from 23.4.0 to 23.4.1

Snyk has created this PR to upgrade puppeteer from 23.4.0 to 23.4.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released on 21 days ago.

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

We already have this PR to to upgrade puppeteer to 23.5.3, so this one is not needed.


Catch and pass along errors in ok callback

This patch wraps _isResponseOk in a try/catch block and passes along the caught error. The client version of superagent already appears to be doing this properly.
Fixes #1247

That's very useful. Thank you.


Module API require with dynamic load module causes variable  not defined

bug?
Is the module context error?
In the code, why throw error 'Uncaught ReferenceError'.

index.js
import data from './data';
import dynamic from './dynamic';

const _dynamic = {
  dynamic: 'dynamic',
};

console.log('data', data);
console.log('dynamic', dynamic);

console.log('require', require('./dynamic.js').default);
console.log('require _dynamic', require(`./${_dynamic.dynamic}.js`).default);
console.log('require dynamic', require(`./${data.dynamic}.js`).default); // throw Error Uncaught ReferenceError: data is not defined

data.js
export default {
  dynamic: 'dynamic',
};

dynamic.js
export default {
  key: 'value',
};

Chrome console

If use the babel module, it will not report the error.
Chrome 59
Node.js 6.10.1
webpack 2.6.1

yep, it's a bug. Workaround should be easy. Fix is difficult. Don't expect that a fix to appear soon...

You can stick with CommonJS imports as a workaround until it's fixed. It's not even that dirty 🙂.
// import data from './data'
const data = require('./data').default;

console.log('require dynamic', require(`./${data.dynamic}.js`).default); // this works

It works because a CommonJS module is treated like a regular object and its fields don't get renamed by webpack.

Could you try it with webpack@next?

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!


Fix #1689, Add time arithmetic functional tests

Describe the contribution
A clear and concise description of what the contribution is.

Fixes #1689
Adds functional tests for

CFE_TIME_Add
CFE_TIME_Subtract
CFE_TIME_Compare

Testing performed
Steps taken to test the contribution:

Build CFE and run all functional tests

Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.

No impact to behavior

System(s) tested on

Hardware: PC
OS: Ubuntu 20.04

Contributor Info - All information REQUIRED for consideration of pull request
Niall Mullane - GSFC 582 Intern

@nmullane check format. Might want to enable actions on your fork to catch these

CCB:2021-07-28 APPROVED


Remove this useless assignment to local variable "strideDistance"

Describe the technical debt
This issue displays unnecessary assignment to a local variable, "strideDistance," which serves no functional purpose and adds to the complexity and verbosity of the code. Technical debt refers to suboptimal or inefficient code that might work but can lead to maintenance difficulties, reduced code quality, or increased complexity in the future.

Proposed solution
Remove the useless assignment to the local variable "strideDistance" to improve code quality and reduce technical debt.
Technical information
Device: Pixel 7 Pro
OS: Android 11
OpenTracks version: v4.8.3

Closed


Added ability to hide the nav bar

Merged. Thanks!

No problem. Have also noticed that the pch file contains the uikit and foundation imports, not sure it is practical for someone who merges your project. Last few months, was not the case and this time, I struggled (not that much...) to figure it out. I would place the imports in the file if I were you, just a suggestion.
Thanks again for the project, it is great!
Sent from my iPhone

On Jan 25, 2015, at 08:49, Andrea Mazzini<EMAIL_ADDRESS>wrote:
Merged. Thanks!
—
Reply to this email directly or view it on GitHub.

Those imports in the prefix header was a common practice a while ago (the project template itself did that). Anyway, the prefix header belongs to the demo project alone, that shouldn't really be used besides demonstrating the control use.


Policy fix mapstate owners

When an identity is deleted, the agent processes the incremental policy
map changes against previously saved policy state with owners and
dependents of the identity key to decide if an identity can be marked for
deletion. In some cases, the owners field for the identity entry was
nil (due to them being redacted when returned by ConsumeMapChanges()
previously), and the deleteKeyWithChanges would return early without
tracking the identity for deletion. As a result, when this information is
consumed later to delete the identity from the BPF maps, the identity was
being leaked in those cases.
Callers of ConsumeMapChanges() and AddVisibilityKeys() depend on the
returned added and deleted keys to perform datapath policy map updates
without iterating whole policy maps. Moreover, the "realized" version of
endpoint's policy map used to be updated solely based on these returned
entries.
Make this less fragile and error prone by only returning the added and
deleted map keys (no values). AddVisibilityKeys() supports reverting the
changes, so it still needs to return the full MapState (keys and values)
for any changed entries.
Now that ConsumeMapChanges() and AddVisibilityKeys() return the keys of
added entries, the caller needs to find the value to be inserted from the
desired policy map using the given key.
Fixes: #18581
Fixes: 0d585f110846237eb3611e88d0992ba26a162f72
Fixes: https://github.com/cilium/cilium/issues/19003
Co-authored-by: Aditi Ghag<EMAIL_ADDRESS>Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>Fixed a bug where deleted identities would remain in BPF policy maps.

policy: Keep internal state in added and deleted mapstate entries

🚀 As discussed on the issue and offline, I originally found this to be the right fix as I was unable to reproduce the issue. Remote debugging also confirmed the same. You'll need to fix the unit tests, see failures in this temporary PR I had created - https://github.com/cilium/cilium/pull/18805.
Change Signed-off-by to Co-authored-by.
Also, can you add "Fixes: https://github.com/aditighag/cilium/commit/0d585f110846237eb3611e88d0992ba26a162f72" to this commit to record the history.

I would also suggest adding more description to the commit around how the identities were leaked. Something along the lines of -
When an identity is deleted, the agent processes the incremental policy
map changes against previously saved policy state with owners
and dependents of the identity key to decide if an identity can be marked for
deletion in the `deletes` map. In some cases, the `owners` field for the identity
entry was nil, and the deleteKeyWithChanges would return early without tracking
the identity for deletion. As a result, when this information is consumed
later to delete the identity from the BPF maps, the identity was being leaked
in those cases.

@aditighag Working on the unit tests I noticed that an added entry misses any changes made to owners and dependents due to other entries being added afterwards, as it takes a copy of the entry at the time. Trying to make the returned copy always be the latest one basically would mean reading it from the policy map before returning. Since the caller also has access to the (desired) policy map it is better not to return the map values at all. Instead just return the added and deleted keys and let the caller worry about coping the entry with that key from desired to realised policy map. This makes the code more robust and simplifies the unit tests as well.

@aditighag Working on the unit tests I noticed that an added entry misses any changes made to owners and dependents due to other entries being added afterwards, as it takes a copy of the entry at the time. Trying to make the returned copy always be the latest one basically would mean reading it from the policy map before returning.

I'm not sure I understand this - Take an example of deleteKeyWithChanges (or add), the desired keys that need to be added or deleted are already fixed, no? Share a link if you are referring to some other code path?

Since the caller also has access to the (desired) policy map it is better not to return the map values at all. Instead just return the added and deleted keys and let the caller worry about coping the entry with that key from desired to realised policy map. This makes the code more robust and simplifies the unit tests as well.

I suppose this could could work as long as the desired keys are in sync with the realized ones. What happens when there were sync-up errors?
Can you also share the unit test that's failing?

I was looking at this example - http://github.com/cilium/cilium/blob/a66538b31e206bb7f4470daeacd879e858177a4d/pkg/endpoint/bpf.go#L1211-L1211. We'll need to read the entries before and after the AddVisibilityKeys calls if we avoid populating the entries in the adds/deletes map? But since we can't track all the calls to the entries, how can be sure that the entries weren't modified outside of the current processing path?
One solution could be adding per entry lock?

I was looking at this example - http://github.com/cilium/cilium/blob/a66538b31e206bb7f4470daeacd879e858177a4d/pkg/endpoint/bpf.go#L1211-L1211. We'll need to read the entries before and after the AddVisibilityKeys calls if we avoid populating the entries in the adds/deletes map? But since we can't track all the calls to the entries, how can be sure that the entries weren't modified outside of the current processing path? One solution could be adding per entry lock?

I think this should happen as the (policy) regeneration logic runs at most once in parallel for each endpoint and all policy map updates are done within this logic. I added a new warning log if the entry for an added key can not be found to make sure we learn about any unexpected behaviour here.

Sorry, I'm really not familiar enough with this part of the code or functionality to be able to give more than a rubber-stamp review.

@joe An attempt for a big-picture explanation with the weekends separation from this work:

As part of an endpoint regeneration, incremental policy map updates are retrieved via ConsumeMapChanges()

As part of this call the collected changes are applied into Endpoint's desired policy 'mapstate'

Endpoint regeneration logic can then use the returned maps to

update the bpf policy map of the endpoint by inserting and removing map entries
update the endpoint's realized policy MapState so that after all updates it becomes the same as the endpoint's desired MapState

Prior to this PR the map updates were made with keys and values returned by ConsumeMapChanges(), but the returned values missed the owners and dependents fields, causing the realized MapState to deviate from the desired MapState

ultimately when the identity is GC'd this lead to the entry to not be deleted as it missed the owner field.

This PR changes the above so that ConsumeMapChanges() only returns the added and deleted keys, and the caller uses the Endpoint's desired policy map to retrieve the map entry. This fixes the GC bug by not losing the owners and dependents fields when applying incremental policy updates.
The simpler approach of just copying also the owners and dependents fields when returning them from ConsumeMapChanges() would become more complex due to the need to copy the final values of the map entries as the entry's dependents field is modified when a dependent entry (with a different key) is added. It is more robust to just return the keys and have the caller copy the entry from desired to relalized map.

/test

/test

Renamed the 2nd commit to match the contents.

/test

net next provisioning had failed, triggering the test again.

test-1.23-net-next

/test-1.23-net-next

Thanks Jarno for https://github.com/cilium/cilium/pull/19005#issuecomment-1060771478. This made sense to me.


[Adaptive cards]: Ensures role attribute has an appropriate value for the element.

Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
OS version: 22H2 (Build 25252.1010)110.0.1543.0
Browser: Edge Dev (110.0.1543.0)
URL: https://adaptivecards.io/
Tool: Accessibility Insights for Web
Repro Steps:

Open the above URL in edge dev browser.
Turn on the fast pass of accessibility insights for web.
Observe the issue.

Actual Result:
Ensures role attribute has an appropriate value for the element.
Expected Result:
Ensures role attribute has an appropriate value for the element.
User Impact:
Screen reader user will get impacted if incorrect role is defined due to which user will not be able to understand the purpose of the content easily.
MAS Reference link:
https://microsoft.sharepoint.com/:w:/s/accessibility/EXdDUZzldv5MgwDaMHnTzcMBcT8opKGncYjU-gCJ4uqQdg?e=9nuVmt
“Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com) “
Screenshots

![image](https://user-images.githubusercontent.com/104483005/208441073-8ebf18e2-c6c7-42c4-875d-c81f3d1beb8a.png)
Card JSON
NA

Sample Code Language
No response
Sample Code
No response

This issue is not repro, hence closing this issue.