Updated coach mark tokens for both desktop and mobile

Updated coach mark tokens by creating new and deprecated old Title, Body, Pagination body font size tokens.

Added the word "font" in the font size token naming.

n/a

n/a

 [ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [x] Minor (add a new token, changing a value; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)
Checklist:

 [x] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [x] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-pagination-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-title-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-title-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-title-font-size

SPECTRUM SYNC SUMMARY
NEW TOKENS: (23) in-field-button-edge-to-fill-small/desktop, in-field-button-edge-to-fill-extra-large/desktop, in-field-progress-circle-edge-to-fill/desktop, in-field-progress-circle-size-75/desktop, in-field-progress-circle-size-100/desktop, in-field-progress-circle-size-200/desktop, in-field-progress-circle-size-300/desktop, in-field-button-edge-to-fill-small/mobile, in-field-button-edge-to-fill-extra-large/mobile, in-field-progress-circle-edge-to-fill/mobile, in-field-progress-circle-size-75/mobile, in-field-progress-circle-size-100/mobile, in-field-progress-circle-size-200/mobile, in-field-progress-circle-size-300/mobile, combo-box-visual-to-field-button, in-field-button-edge-to-fill-medium, in-field-button-edge-to-fill-large, coach-mark-body-font-size/desktop, coach-mark-body-font-size/mobile, coach-mark-pagination-body-font-size/desktop, coach-mark-pagination-body-font-size/mobile, coach-mark-title-font-size/desktop, coach-mark-title-font-size/mobile
MODIFIED TOKENS: (7) coach-mark-body-size, coach-mark-pagination-body-size, coach-mark-title-size, combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-small
DEPRECATED TOKENS: (19) combo-box-quiet-minimum-width-multiplier, combo-box-visual-to-field-button-small/desktop, combo-box-visual-to-field-button-small/mobile, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-medium/mobile, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-large/mobile, combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-extra-large/mobile, combo-box-visual-to-field-button-quiet, coach-mark-title-size/desktop, coach-mark-title-size/mobile, coach-mark-body-size/desktop, coach-mark-body-size/mobile, coach-mark-pagination-body-size/desktop, coach-mark-pagination-body-size/mobile, in-field-button-edge-to-fill, drop-shadow-y, drop-shadow-blur
CHANGED VALUES: (8) combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small/desktop, coach-mark-body-size/desktop, coach-mark-pagination-body-size/desktop, coach-mark-title-size/desktop
CHANGED SCHEMAS: (5) combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small

TEST COMPLETE

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-pagination-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-title-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-title-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-title-font-size

SPECTRUM SYNC SUMMARY
NEW TOKENS: (23) in-field-button-edge-to-fill-small/desktop, in-field-button-edge-to-fill-extra-large/desktop, in-field-progress-circle-edge-to-fill/desktop, in-field-progress-circle-size-75/desktop, in-field-progress-circle-size-100/desktop, in-field-progress-circle-size-200/desktop, in-field-progress-circle-size-300/desktop, in-field-button-edge-to-fill-small/mobile, in-field-button-edge-to-fill-extra-large/mobile, in-field-progress-circle-edge-to-fill/mobile, in-field-progress-circle-size-75/mobile, in-field-progress-circle-size-100/mobile, in-field-progress-circle-size-200/mobile, in-field-progress-circle-size-300/mobile, combo-box-visual-to-field-button, in-field-button-edge-to-fill-medium, in-field-button-edge-to-fill-large, coach-mark-body-font-size/desktop, coach-mark-body-font-size/mobile, coach-mark-pagination-body-font-size/desktop, coach-mark-pagination-body-font-size/mobile, coach-mark-title-font-size/desktop, coach-mark-title-font-size/mobile
MODIFIED TOKENS: (7) coach-mark-body-size, coach-mark-pagination-body-size, coach-mark-title-size, combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-small
DEPRECATED TOKENS: (19) combo-box-quiet-minimum-width-multiplier, combo-box-visual-to-field-button-small/desktop, combo-box-visual-to-field-button-small/mobile, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-medium/mobile, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-large/mobile, combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-extra-large/mobile, combo-box-visual-to-field-button-quiet, coach-mark-title-size/desktop, coach-mark-title-size/mobile, coach-mark-body-size/desktop, coach-mark-body-size/mobile, coach-mark-pagination-body-size/desktop, coach-mark-pagination-body-size/mobile, in-field-button-edge-to-fill, drop-shadow-y, drop-shadow-blur
CHANGED VALUES: (8) combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small/desktop, coach-mark-body-size/desktop, coach-mark-pagination-body-size/desktop, coach-mark-title-size/desktop
CHANGED SCHEMAS: (5) combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small

TEST COMPLETE

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-pagination-body-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.🚫 coach-mark-title-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-pagination-body-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.coach-mark-title-font-size
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.coach-mark-title-font-size

SPECTRUM SYNC SUMMARY
NEW TOKENS: (23) in-field-button-edge-to-fill-small/desktop, in-field-button-edge-to-fill-extra-large/desktop, in-field-progress-circle-edge-to-fill/desktop, in-field-progress-circle-size-75/desktop, in-field-progress-circle-size-100/desktop, in-field-progress-circle-size-200/desktop, in-field-progress-circle-size-300/desktop, in-field-button-edge-to-fill-small/mobile, in-field-button-edge-to-fill-extra-large/mobile, in-field-progress-circle-edge-to-fill/mobile, in-field-progress-circle-size-75/mobile, in-field-progress-circle-size-100/mobile, in-field-progress-circle-size-200/mobile, in-field-progress-circle-size-300/mobile, combo-box-visual-to-field-button, in-field-button-edge-to-fill-medium, in-field-button-edge-to-fill-large, coach-mark-body-font-size/desktop, coach-mark-body-font-size/mobile, coach-mark-pagination-body-font-size/desktop, coach-mark-pagination-body-font-size/mobile, coach-mark-title-font-size/desktop, coach-mark-title-font-size/mobile
MODIFIED TOKENS: (7) coach-mark-body-size, coach-mark-pagination-body-size, coach-mark-title-size, combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-small
DEPRECATED TOKENS: (21) color-loupe-drop-shadow-y, color-loupe-drop-shadow-blur, combo-box-quiet-minimum-width-multiplier, combo-box-visual-to-field-button-small/desktop, combo-box-visual-to-field-button-small/mobile, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-medium/mobile, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-large/mobile, combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-extra-large/mobile, combo-box-visual-to-field-button-quiet, coach-mark-title-size/desktop, coach-mark-title-size/mobile, coach-mark-body-size/desktop, coach-mark-body-size/mobile, coach-mark-pagination-body-size/desktop, coach-mark-pagination-body-size/mobile, in-field-button-edge-to-fill, drop-shadow-y, drop-shadow-blur
CHANGED VALUES: (10) color-loupe-drop-shadow-blur, color-loupe-drop-shadow-y, combo-box-visual-to-field-button-extra-large/desktop, combo-box-visual-to-field-button-large/desktop, combo-box-visual-to-field-button-medium/desktop, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small/desktop, coach-mark-body-size/desktop, coach-mark-pagination-body-size/desktop, coach-mark-title-size/desktop
CHANGED SCHEMAS: (7) color-loupe-drop-shadow-blur, color-loupe-drop-shadow-y, combo-box-visual-to-field-button-extra-large, combo-box-visual-to-field-button-large, combo-box-visual-to-field-button-medium, combo-box-visual-to-field-button-quiet, combo-box-visual-to-field-button-small

TEST COMPLETE

@lynnhao @KayiuCarlson Just FYI: This is how the tokens appear with the type "fontSizes".

@GarthDB This is ready to merge. 👍


Replace organisation->organization

References
There isn't a specific issue for this PR
Description
From a missing translation, we noticed that some fields were written with a different schema:

organisation.address.addressCountry

organisation.address.addressLocality

organisation.foundingDate

I personally don't have any strong preference on the way it's written (en_EN or en_US), but I think we should use one and stick to it. Currently the schema is organization with the Z and not with the S, so, we need to change the one that were specified with the S

I will do this today, thank you @tdonohue!


Vectors as Vispy Lines (rather than meshes)

Description
As mentioned in this zulip conversation, depicting vectors as meshes was a choice made a while back based on a few issues that might not exist anymore (see #215, #214). This PR reverts that change; please check it out (especially with OSX) and see if any weird artifacts occur.
If everythign is fine, this PR drastically simplifies the housekeeping work that napari needs to do, as well as making vector visualization more consistent (no changes based on point-of-view).
Antialiasing could be activated, but is currently disabled due to the transparency issues in vispy.
If this gets approved, I would wait to first merge #3333 and fix conflicts here.
Type of change

[x] Change of backed visual (non-breaking change)

References

#214
#215

How has this been tested?

[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality

@brisvag would you mind showing some before/after screenshots here?

I notice now that there are a few significant differences with this method:

line width is in screen space (so inconsistent in data space)
and can only be changed by integers (rounded up)

As far as I can tell, this are intrinsic limitations of GL lines. They might be solvable using the agg method, but that's currently unable of doing segments, and might be significantly worse in performance.
I think these changes are significant enough that this can't replace the current mode. However, I can see this being an alternative depiction mode. Maybe we could think about this :)
Here's a screen capture (left is main, right is this PR):
https://user-images.githubusercontent.com/23482191/135226381-62a847cc-6f11-4920-bd1c-8d4689d914dd.mp4

@brisvag so one question is whether we could tie the vector size to the camera distance, ie do the screen->data scaling manually and updating the visuals as the camera zoom level changes, and whether that would still be simpler/more performant than the current vector/mesh approach. What do you think?
Personally I don't have a strong opinion here, but I do think that vector width scaling in data (world) coordinates is a valuable thing to have and should be the default.

Not sure on the first one... Zooming happens all on the vispy canvas, not sure how hackable that would be, nor how performant.
Actually, i have a half-implemented cylinder impostor visual thst might work for this and do what we need, though not sure on the performance.

Just getting caught up, but a couple of thoughts that may or may not be useful...

Not sure on the first one... Zooming happens all on the vispy canvas, not sure how hackable that would be, nor how performant.

I think this is probably not super useful because it doesn't work with perspective, but this is how the vispy Markers visual used to get the scaling:
https://github.com/vispy/vispy/blob/d901f6430784416bacb028e1ff450a3640400e44/vispy/visuals/markers.py#L614-L628
Can you calculate the width in data units by transforming a vector of known length from data to canvas coordinates (the same technique for setting the point width as you implemented in Markers)?

Can you calculate the width in data units by transforming a vector of known length from data to canvas coordinates (the same technique for setting the point width as you implemented in Markers)?

Yes, that's exactly what I did in my cylinder impostor approach. That won't work with opengl lines, cause the size is a gl "global" variable (https://github.com/vispy/vispy/blob/545abddf3cf5d7e672cb48fe8e68779fc338cc2d/vispy/visuals/line/line.py#L345)

I don't think it's the better approach at this point. In might be worth introducing an "alternative visual" for layers, but this would need some more architerctural changes. I think we can maybe close this PR for now, but keep it in mind for the future.
To summarise:

PROS:

screen-space width: this is often better, as vector width is more often than not just a visualization parameter than data.
no POV-dependant visualization: these meshes look weird as you rotate them, since they are made of flat planes.
faster (in theory, I have not tested)

CONS:

no way to maintain data-space width, in those cases where this is what a user wants
width limited to integer pixels, which limits options

Alternatives:

expand the agg drawing method of Linevisual to work with segments (might be bad on performance, but looks good)
use a custom made visual (I have some prototype, but it needs polishing and might not solve all the issues).


inventory from industrial facilities

There are instances where generation is reported  under NAICS code 22 in EIA form 923 and the generator is at an industrial facility. When electricity uses StEWI to pull other reported emissions, there is currently no way to see whether those emissions are reported for the rest of the industrial facility vs just the electricity generation. In cases where the emissions are for an industrial facility this can produce inaccurate inventories. For example, there is solar generation at an Intel facility in Arizona. The NEI inventory for this facility is actually for semiconductor manufacturing as indicated by its NAICS code (or general electronics) and reports very high SF6 emissions, which makes sense for this type of facility, but it makes no sense for solar generation.
To avoid this issue, we need to pull in facility NAICS information as done here in flowsa and filter non-electricity-generation flows out.

opening up a branch to give this a shot. See also Discussion #191.


[BUG] If "viewIsInsideTabBar" is false, set keyboardSpace set as 0

Even though "viewIsInsideTabBar" value is false, "ScrollView" has marine as tab-bar on the bottom.
Set "keyboardSpace" as 0 if "viewIsInsideTabBar" prop is {false}
It's fine after focused once. so, this commit fixed bottom margin when it's rendered first place.

please declined this PR if it's not acceptable.

Hello @JosephDev!
It shouldn't be necessary, take a look here https://github.com/JosephDev/react-native-keyboard-aware-scroll-view/blob/c218ce89c6c6b037f438dbed8819c1bef2a10a85/lib/KeyboardAwareMixin.js#L45 and here https://github.com/JosephDev/react-native-keyboard-aware-scroll-view/blob/c218ce89c6c6b037f438dbed8819c1bef2a10a85/lib/KeyboardAwareMixin.js#L64
The TabBar is handled in reset and update keyboard space methods.
Please fill a bug if you find anything related to this.
Thanks!


Change airgap method and validate pulling non cached images does not work

The current method is not optimal as dropping the default route has negative effects on the Kind cluster. The new method uses iptables to block non RFC1918 CIDR traffic. A new check has been added to make sure that images cant be pulled from the internet.

As far as I know the interface will always be eth0. Good comment about using reject instead.


Snapshot

Summary
new snapshot version updated

Pull Request Test Coverage Report for Build 84

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

Totals

Change from base Build 79:
0.0%

Covered Lines:
338

Relevant Lines:
343

💛  - Coveralls


bug(chat): external resource inclusion

STR:

go to chat
send this

![External Image](http://malicious-site.com/image.jpg)

display like this

not sure what behavior do we prefer here
discord displays like this

macOS, m1

same as #1745

i only meant this


Track approval steps of a dossier

As a group master, when forwarding, returning, or rejecting a dossier, I want the history of my actions to be viewable and displayed to any other reviewer.
[Story Points: 5]
[Priority: Medium]
[Risk: Medium]
Tasks:

[x] #369
[x] #378
[x] #379

Demo steps:
Given I’m a group master reviewing a dossier
When I send a request to forward a dossier
The dossier is successfully forwarded.
Then, on the review page, I can see a record of when and by who this dossier was forwarded.

All work is complete for this story


⚠ Bofrost.lu has degraded performance

In 5e798fe, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1625 ms

Resolved: Bofrost.lu performance has improved in d60ca8d after 39 minutes.


[InAppMessaging] Fix SPM warnings

[ ] Need to check SPM warnings in CI when it's done

#no-changelog

SG! I'll open a new PR with the approach.


RFC: Add per component and per BOM key/value pairs

There are times when adopters and implementors of CycloneDX need to specify data that falls outside of what the spec provides. Vendor specific schema extensions are one way to accomplish that, however, it also leads to vendor lock-in.
Therefore, it is desirable to support per component and per bom key/value stores.
For example:
<component type="library">
    <name>Acme Component</name>
    <version>1.0.0</version>
    <properties>
        <property name="myprop" value="myvalue"/>
    </properties>
</component>

This allows a certain degree of customization without having to use vendor-specific extensions. Support for properties inside of other objects (e.g. supplier and license) may also be desirable.

I really like this addition.
It supports use cases like internal (semi-)automated workflows. I propose this is also included at the BOM level.

@wrgoff This is still being designed. Once complete, if the RFC is approved, then it will be incorporated into the next version of the CycloneDX specification (v1.3). Historically, there has been a new release of CycloneDX in Q1/Q2 every year for the past three years.

I'm +1 to this addition as well.

Reopening. For XML, I think it makes sense to implement the value as a child element rather than an attribute.
The original proposal specified:
<properties>
    <property name="myprop" value="myvalue"/>
</properties>

However, I think it might be better to support it like this:
<properties>
    <property name="myprop">myvalue</property>
</properties>

By doing it this way, adopters could specify CDATA in value to minimize escaping.
Thoughts? Does it matter?
The way its implemented in JSON would remain the same.

I think the second option is better.
There's also inconsistency between the JSON and XML schema. name for XML and key for JSON.
<properties>
    <property name="myprop">myvalue</property>
</properties>

"properties": [
  {
    "key": "Foo",
    "value": "Bar"
  }
]

Actually, I much prefer name. When I hear key value I think the key would be unique.

You bring up a good point @coderpatros. While implementing support for this I originally started with a hashmap, then realized it would not work since duplicates are allowed in the spec. I'll change it to name/value for both and ensure the value in XML is an element rather than an attribute.

Ok, the changes have been made. The following syntax is now used:
XML
<properties>
    <property name="Foo">Bar</property>
    <property name="Foo">You</property>
    <property name="Foo">Two</property>
    <property name="Bar">Foo</property>
</properties>

JSON
"properties": [
      {
        "name": "Foo",
        "value": "Bar"
      },
      {
        "name": "Foo",
        "value": "You"
      },
      {
        "name": "Foo",
        "value": "Two"
      },
      {
        "name": "Bar",
        "value": "Foo"
      }
    ]


Added automation tests for android

[x] All speced functionally is implemented and is working
[x] Unit tests for all functions and modules
[x] Integration tests for all use cases
[ ] Comment documentation for all modules, functions and types
[x] Ready for code review

Please add instructions on how to test for android to readme.me

That's true.


OSB Release Calendar

Motivation
To adhere to the OpenSearch release schedule, OpenSearch Benchmark (OSB) releases will be done on a 6-week cadence. For more details, see this discussion #579.
Schedule
The following tables shows upcoming release dates for OSB, their associated release managers (maintainers), and their tracking issues.

OSB Version
Date
Release Manager
Tracking Issue

1.9.0
8/22
Govind
#610

1.10.0
10/3
Vijayan

1.11.0
11/14
Ian

2.0.0
TBD
TBD

I think we'll have the version 1 branch being released for a few more versions, so it would be good to have additional entries in that series for folks to sign up.  Also, adding entries to indicate the release managers for the last 3 or 4 releases will help us round-robin better.


Use custom url for self-hosted

I suggest to replace the ntfy.sh url suggested in the code blocks to match the real url, to allow an easier copy-pasting if we selfhost.
This replacement has been tested with a custom port (first screenshot) and a classic port (80/443 for http/https) (second screenshot).

On main page
On event page

Also, thanks for this "It just works" software, which looks good and works fine!

Awesome thank you.


0.13.2 Crash Issue

I'm on a Rooted Amazon Fire HD 7 Fire OS 5.0.1 Every Time I install a mod, or 2 texture packs. BlockLauncher repeatedly crashes, even in safe mode. And even when I uninstall the mods/texture packs/addons it still crashes! What do I do? Thanks.

I sometimes get this on my SHIELD tablet. Generally it breaks after a crash.


Remove ServerAddress in 3.0

https://github.com/aspnet/KestrelHttpServer/pull/2987/commits/e9eea50966ff8bd8bcae304c107f90c9022e9e57
It was obsoleted in 2.2 and now it should be removed in 3.0.

Most certainly not just a task! This is an API change.


Create Non-singer-esque language for common extract and load operations

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2664
Originally created by @tayloramurphy on 2021-03-22 15:31:30

From our Vision discussion:
Straightforward non-singer-esque language for common EL operations: "backfill", "incremental", "full replace", etc.

Awareness around append-only targets
No remaining shortcomings around singer spec

View 3 previous comments from the original issue on GitLab


ObjectID error

Hello,
I had been using the modbus read node successfully until an update a little while ago. What's happening now is that when I pass the output to a dashboard template node, I get "Error: invalid ObjectId, ObjectId.id must be either a string or a Buffer, but is [{"_placeholder":true,"num":1}]". I cannot seem to track this down to any other source of input into the template node, only seems to happen when the modbus read node is connected. Any help is much appreciated.

Hello,
some logs or stacktrace to see what happens?

Thanks for your time!
3 Apr 05:50:03 - [error] [ui_template:valve message] Error: invalid ObjectId, ObjectId.id must be either a string or a Buffer, but is [{"_placeholder":true,"num":1}]     at ObjectID.toHexString (/home/[user]/.node-red/node_modules/bson/lib/bson/objectid.js:88:11)     at ObjectID.toJSON (/home/[user]/.node-red/node_modules/bson/lib/bson/objectid.js:196:15)     at Object.stringify (<anonymous>)     at encodeAsString (/home/[user]/.node-red/node_modules/socket.io-parser/index.js:178:17)     at writeEncoding (/home/[user]/.node-red/node_modules/socket.io-parser/index.js:199:16)     at Object.exports.removeBlobs (/home/[user]/.node-red/node_modules/socket.io-parser/binary.js:139:5)     at encodeAsBinary (/home/[user]/.node-red/node_modules/socket.io-parser/index.js:206:10)     at Encoder.encode (/home/[user]/.node-red/node_modules/socket.io-parser/index.js:130:5)     at Adapter.broadcast (/home/[user]/.node-red/node_modules/socket.io-adapter/index.js:121:16)     at Namespace.emit (/home/[user]/.node-red/node_modules/socket.io/lib/namespace.js:222:18)     at Server.(anonymous function) [as emit] (/home/[user]/.node-red/node_modules/socket.io/lib/index.js:425:29)     at TemplateNode.<anonymous> (/home/[user]/.node-red/node_modules/node-red-dashboard/ui.js:242:16)     at TemplateNode.emit (events.js:127:13)     at TemplateNode.Node.receive (/usr/local/lib/node_modules/node-red/red/runtime/nodes/Node.js:215:14)     at FunctionNode.Node.send (/usr/local/lib/node_modules/node-red/red/runtime/nodes/Node.js:202:14)     at sendResults (/usr/local/lib/node_modules/node-red/nodes/core/core/80-function.js:52:18)

Hello, just a follow up, I was able to solve this issue with the dashboard template node by deleting either msg.input or msg.responseBuffer from the message generated out of the ModbusRead node.


global search function is broken

Describe
Global search doesn't work, unless opened as a local file.
Reproduce

visit https://tilde.xvvvyz.xyz/.
type "duck" and hit return.
will enter the address "https://tilde.xvvvyz.xyz/?q=duck", instead of "https://duckduckgo.com/?q=duck".

Replace follow:
      const [baseUrl, rest] = Search.#splitUrl(CONFIG.defaultSearchTemplate);
      const url = Search.#formatSearchUrl(baseUrl, rest, query);
      return { query, search: query, url };

with:
      const url = this.#hasProtocol(query) ? query : `https://duckduckgo.com/?q=${query}`;
      return { query, search: query, url };

I hope it helps. Love your work.

Good catch, thank you for opening this. Fixed in https://github.com/xvvvyz/tilde/commit/68b64d190af8f8fb0456561bf3e4e2eb42e47215.


Change meeting frequency to every 2 to every 4 weeks?

Problem description
We do not have a lot to discuss for this API.
What about change meeting frequency to every 2 to every 4 weeks?
Of course use of git for issue & discussion is more than welcome to keep the chanel alive
Expected action
Additional context

THis is done


Laravel/Configure cronjobs

Laravel Version: #.#.#
PHP Version:
Database Driver & Version:

Description:I am trying to setup task every hour.
I executed command : vagrant@vagrant-ubuntu-trusty-64:/var/www/html/shop$ 30 * * * * php /var/www/html/shop/artisan aimeos:jobs "customer/email/watch order/cleanup/unfinished order/service/async order/service/payment"
I got this result: 30: command not found
Please help. Thanks
Steps To Reproduce:

You are pasting the cron schedule in your shell, and so the command "30" does not exist. Setup "30 * * * * php /var/www/html/shop/artisan aimeos:jobs customer/email/watch order/cleanup/unfinished" in your cronjob. Learn more about that here.

Thanks a lot, much appriciated.


[BugFix] ParallelEnv handling of done flag

Description
This PR addresses issue #776.
It does two things:

The ParallelEnv workers will not try to test the "done" flag coming out of a wrapped environment. This worked only when the done flag was without a batch_size. Now, on the other hand, the workers reports the step result as is (the done message was not even used anyway)
Very important issue. The workers now call env.reset() instead of env._reset(). this is because some environments do not return the done key in the tensordict returned by _reset(). Since later the worker calls if _td.get("done").any(): this call fails if the environment does not return the done key in the tensordict returned by _reset(). reset() on the other hand wraps _reset() and automatically adds the defaulte done value, solving the issue.

Very important issue. The workers now call env.reset() instead of env._reset(). this is because some environments do not return the done key in the tensordict returned by _reset(). Since later the worker calls if _td.get("done").any(): this call fails if the environment does not return the done key in the tensordict returned by _reset(). reset() on the other hand wraps _reset() and automatically adds the defaulte done value, solving the issue.

I'm curious: can't we use default?
As of now default can't be a callable, so we could do
done = _td.get("done", None)
if done is None:
    done = torch.zeros(_td.shape, dtype=torch.bool, device=device)

Some tests are failing, I suspect that it's because of the _reset to reset change.
Can we try with the False default?

Yes your options definitely work! I thought that that defaulting was all that reset() deos plus simple checks, but maybe was wrong. Will fix

Apparently just seeting the default in the if is not enough as later the done is checked again in
 while self.shared_tensordict_parent.get("done").any():
            if check_count == 4:
                raise RuntimeError("Envs have just been reset but some are still done")

Thus i now tried as it is done in reset() to set the default.
In any case, I plan to propose some bigger modifications to this type of checking of the done with any(). Because with vectorize enironments it doesn't make sense. So I thing theseparts might be changed in the near future.


[Other] How to undo the changes done to the amfi and system.

Additional Information
No response

See README.md

Enable SIP in recovery mode with csrutil enable and reboot.
Remove boot argument by sudo nvram -d boot-args


.walk() should respect "detail=True"

This PR addresses two issues: passing detail as a kwarg to
.walk() fails because it internally calls .ls()
with both detail=True and whatever kwargs were passed
originally, causing detail to be specified twice.
The second is that .walk() does not respect detail=True
and always returns bare file names. My fix here is to just
shove the dict from .ls() into the return list unmodified --
this feels slightly incongruous with the non-detail version
which strips prefixes from paths, but this feels like the
right thing to do?
Anywhoo, this is a bit messy so I'm happy to clean it up
if you have any suggestions. It could also use some tests:
is there any particular way you'd like it tested? A test in
test_local?

As I said elsewhere, I believe it may make sense to add this to find(), but not for walk().


Segmentation fault (core dumped)

Hi,
I just update a few minutes ago the libraries cunn & cutorch using "luarocks install cunn.. cutorch" and after the update when i try to run a program with cuda does not work.
I was wondering if is a problem of the update or something, because before that i had not any problem.
Best Regards

I'm not aware of any issues. Can you give us a bit more detail on how it crashes? Maybe you can post some code that reproduces the error?

Sorry but I not sure the problem is, but it appears when i try to move data:
for i = t,math.min(t+opt.batchSize-1,#inset) do
-- load new sample
local input = inset[i]--[pos[i]]
local target = outset[i]--[pos[i]]
if opt.gpuid >= 0 then
--cutorch.synchronize()
input = input:cuda()
target = target:cuda()
--TensorType = 'torch.CudaTensor'
end
table.insert(inputs, input)
table.insert(targets, target)
end

It is working, i just updated cunn and cutorch, and the problem doent not appears.
However i was wondering why using a cutorch.sync() into a for loop, locating data into the gpu stocks the memory and didnt release the memory, that leave the gpu out of memory, anyway, i'm trying to avoid the use of sync into for and the computing speed is really fast.


Animating AudioStreamPlayer volume db property does not work in game, only in editor

Tested versions
Reproducible in 4.2.1
System information
Windows 11
Issue description
When I animate the volume on an audio stream player it only works in the editor, does not work when the game is launched.
Steps to reproduce
Create a scene
Add an AudioStream3d node
Add an AnimationPlayer node
Add a Camera3d node
Add an audio stream to the player node and set to autoplay.
Create a new animation with 2 keyframes attenuating the volume from 0db to -80db.
Set the animation to autostart or play it from script.
Test in Editor:
Set the streamplayer to "playing" and scrub the timeline.  The volume does change.  Disable "playing"
Test in Game:
Launch the scene.  The volume does not go down.  In the remote scene tree the volume property has changed, but the actual volume coming out of the speakers does not change.
EDIT: Actually, doing more testing, it seems the volume property does not work in game at all, animated or not.  If I set a stream to just be at -80 db and start the scene with no animation, it still plays at full volume.
Minimal reproduction project (MRP)
test.zip

Add an AudioStream3d node
Add an AnimationPlayer node
Add a Camera3d node
Add an audio stream to the player node and set to autoplay.
Create a new animation with 2 keyframes attenuating the volume from 0db to -80db.
Set the animation to autostart or play it from script.

I followed these steps but can't reproduce your issue using ogg or wav sound files. (Win 10. Godot 4.2.1 stable)

Yes that worked.  Thank you.
Not sure I ever would have figured that out on my own.


Get a list of APIs based on Tags

User story
Tags are widely used to group APIs based on different criteria and helps searching them in API Manager or API Portal.
It would be great if APIs could be identified by Tags as well in the APIM CLI (API GET command) for display or export purpose, similar to the handling described in the Axway docs:
https://docs.axway.com/bundle/axway-open-docs/page/docs/central/connect-api-manager/filtering-apis-to-be-discovered/index.html

Thanks for adding this enhancement. Implement this as an additional filter option. Part of the next release 1.2.3


Can't built osgjs plugin:  no member named ‘setForceReIndex’

Hi,
I am using osgjs plugin 3.1.0 and osg 3.0.1 according to this entry http://osgjs.org/2011/02/working-with-openscenegraph/
cmake . && make
OpenSceneGraph-3.0.1/src/osgPlugins/osgjs/GeometryOperation.cpp: In member function ‘osg::Geometry* GeometryIndexSplitVisitor::doSplit(osg::Geometry&, unsigned int)’:
OpenSceneGraph-3.0.1/src/osgPlugins/osgjs/GeometryOperation.cpp:598:61: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
OpenSceneGraph-3.0.1/src/osgPlugins/osgjs/GeometryOperation.cpp: In member function ‘virtual void OpenGLESGeometryOptimizerVisitor::apply(osg::Geode&)’:
OpenSceneGraph-3.0.1/src/osgPlugins/osgjs/GeometryOperation.cpp:877:25: error: ‘class osgUtil::IndexMeshVisitor’ has no member named ‘setForceReIndex’
make[2]: *** [src/osgPlugins/osgjs/CMakeFiles/osgdb_osgjs.dir/GeometryOperation.o] Error 1
make[1]: *** [src/osgPlugins/osgjs/CMakeFiles/osgdb_osgjs.dir/all] Error 2
make: *** [all] Error 2

Thanks for help

It's because I added a method but it's in my repository of osg not in the trunk. You can try to get my repository https://github.com/cedricpinson/osg but clearly I need to report the code into the plugin repository

Now it works. Thanks:)


Only include debug info for binary deployed to TileDB Cloud

Background:

The debug info was included in the binary starting in 0.6.0 (https://github.com/TileDB-Inc/TileDB-Vector-Search/pull/424). My understanding is that the motivation for this was for easier debugging in TileDB Cloud
Including the debug info greatly increases the size of the binary, and thus the conda binary uploaded to anaconda.org
We are running out of space on anaconda.org

Proposal:
I have attempted to use the scikit-build-core configuration to override the settings in pyproject.toml. The goal is to only include the debug info for the binary that is installed for TileDB Cloud (linux-64 and python 3.9).
Status:
Unfortunately it isn't currently working. Despite passing -C skbuild.cmake.build_type="Release"  and --config-settings=install.strip=true , CMake still reports -- Install configuration: "RelWithDebInfo", and the binary _tiledbvspy.cpython-310-x86_64-linux-gnu.so is still huge.
Can anyone see how I need to edit the pip install command to properly override the default settings?

As expected from the builds on my fork, the linux-64 python 3.9 build used the correct script: command, built the binary in "RelWithDebInfo" mode, and created a large binary. The other builds, eg linux-64 python 3.10, used the correct script: with -C skbuild.cmake.build_type="Release" and --config-settings=install.strip=true, but still built the binary in "RelWithDebInfo" mode, and created a large binary.
In other words, the jinja2 preprocessing selectors are working as expected, but the command-line options I am passing to pip install are not having any effect on scikit-build-core.
@dudoslav any ideas?

@jdblischak Looking at the scikit-build-core documentation it seems that the correct option should be:
pip install . --config-settings=cmake.build-type="Debug"

https://scikit-build-core.readthedocs.io/en/latest/configuration.html#configuring-cmake-arguments-and-defines
So perhaps I gave you an incorrect option to set, sorry for that.

@dudoslav thanks! Trying that now

Success! The binary for linux-64 python 3.10 was reduced from 123,872,008 to 4,978,832

@NikolaosPapailiou @ihnorton is it ok if only the conda binary that is deployed to TileDB Cloud includes the debug info? This will drastically reduce the storage requirements of future releases of tiledb-vector-search on anaconda.org

While not as drastic of a size decrease as the linux-64 binaries, the size of the osx-64 binary _tiledbvspy.cpython-39-darwin.so was still halved from 9,135,816 in the most recent osx-64 python 3.9 build on main to 4,498,128 in the osx-64 python 3.9 build for this PR


Build 8.20210621 alldep version

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

uff -- running over two hours... the log with webui says that it is at "Solving environment:" for "Testing downstream package: datalad=0.14.3" -- we have 0.14.7 -- will update now, might be a bit lighter in some environments (windows) on dependents ;) ... oh -- it finished before I finished typing this, and green!  I cannot miss the opportunity to have it merged as is.  Will boost to later datalad later, may be in a PR to also try to boost the nodep one (to replace #122 ?)

oops -- subject was wrong ;-)


Switch from our custom datastore cache(s) to ndb's with custom policies?

Would be nice to ditch our own code for this! https://cloud.google.com/appengine/docs/legacy/standard/python/ndb/cache , https://googleapis.dev/python/python-ndb/latest/context.html#google.cloud.ndb.context.Context.set_cache_policy
It has a bug/weird behavior that we'd probably need to work around though, https://github.com/snarfed/bridgy-fed/issues/558 . More: https://github.com/snarfed/bridgy-fed/issues/558#issuecomment-1603253691

Done! We're now using a memcache instance. Results were surprisingly not as big as I'd hoped, but we are doing it. 🤷♂


Oops; flutter has exited unexpectedly.

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter build ios --release --no-codesign --no-simulator --verbose
exception
ArgumentError: Invalid argument(s)
#0      _StringBase._interpolate (dart:core-patch/string_patch.dart:846:9)
#1      BuildIOSCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:83:62)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
#3      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#4      _rootRunUnary (dart:async/zone.dart:1132:38)
#5      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#9      Future._complete (dart:async/future_impl.dart:473:7)
#10     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#11     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async-patch/async_patch.dart:33:20)
#12     _rootRun (dart:async/zone.dart:1124:13)
#13     _CustomZone.run (dart:async/zone.dart:1021:19)
#14     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#15     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#16     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#17     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
#18     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)

flutter doctor
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Mac OS X 10.14.4 18E226, locale zh-Hans-CN)
    • Flutter version 1.5.4-hotfix.2 at /Users/spt/.flutterHome
    • Framework revision 7a4c33425d (2 周前), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/spt/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.0

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (1 available)
    • XR • 00008020-0001408E1112002E • ios • iOS 12.0.1

• No issues found!

@intspt is it still an issue? Please provide a code example to reproduce the error, also your flutter doctor -v output.

Duplicate of https://github.com/flutter/flutter/issues/28895.


RuntimeError  yolov3

I run the detect.py in the example given by the official can succeed, but if the real-time screenshot inference will occur errors, the test read a local picture will not report an error,
error code,[libprotobuf FATAL D:\a_work\1\s\pytorch-directml\caffe2\dml\dml_operator.cc:116] CHECK failed: ((((HRESULT)((backend_->dml_device->CreateOperator(&op_desc_, uuidof(**(&op)), IID_PPV_ARGS_Helper(&op))))) >= 0)) == (true):
Traceback (most recent call last):
File "D:/yolov3/zimiao/main.py", line 37, in
det[:, :4] = scale_coords(img.shape[2:], det[:, :4], img0.shape).round()
File "D:\yolov3\utils\general.py", line 404, in scale_coords
coords[:, [0, 2]] -= pad[0]  # x padding
RuntimeError: CHECK failed: ((((HRESULT)((backend->dml_device->CreateOperator(&op_desc, __uuidof(**(&op)), IID_PPV_ARGS_Helper(&op))))) >= 0)) == (true):

Hi @meyll, Can you print out the dtype and shape of coords and pad so we could try to repro it?

Hi @meyll, this could be due to #306 as an out-of-memory error. Closing this as a stale issue, but feel free to reopen if you can repro on the latest version of torch-directml-0.1.13.dev221216.


fix #312 - no initial page load on Android

Summary
fix #312 with workaround solution from @KusStar (see https://github.com/callstack/react-native-pager-view/issues/312#issuecomment-807846238)

Checklist

[X] I have tested this on a device and a simulator

@Lukas-Heiligenbrunner @troZee this doesn't really fix the issue. Now you can first see the first page before it skips to the initialPage.

Yes, I'm facing the same issue, I can see 0 index first before jumping to initialPage index.

@danilobuerger @sajorahasan could you try this PR ?
https://github.com/callstack/react-native-pager-view/pull/368

@Lukas-Heiligenbrunner @troZee this doesn't really fix the issue. Now you can first see the first page before it skips to the initialPage.

Same

@troZee I just tested #368 and looks like the issue is fixed for android.
Step: yarn remove react-native-pager-view && yarn add callstack/react-native-pager-view#368/head && ENVFILE=.env.development npx react-native run-android


Update scodec-bits to 1.1.24

Updates org.scodec:scodec-bits from 1.1.18 to 1.1.24.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: library-update, semver-patch

Superseded by #149.


Intel MKL DNN: Adding support of fusing Pad and Conv2D Operators in MKL DNN

Idea of fusing Pad and Conv2d:
A = input(such as image), B = input(paddings), C= Pad = input of conv2D,
D=input(filter), E = Conv2D, Z = Zeta
C=Pad(A,B); E=Conv2D(C,D); Z=Zeta(E,Y)
After layout pass (merge), the new Op will be the following:
_MklPadWithConv2D(A, D, B, DMT/_0, DMT/_1, DMT/_2)
Here, DMT/_X are the mkl layout inputs, corresponding to A, D and B.
Explanation of the Pad + Conv2D Fusion with Example:
Input = y
x = pad(y, paddings) ; for example: x = pad ( y, {(0,0), (2=top,5=bottom), (6=left,9=right), (0,0)}
paddings = { (0,0) (2,5) (6,9) (0,0)}
Eigen version of conv2D:
Z = conv2D(x, filter, stride, dilation, "padding") // size of z depends on x, filter, stride, dilation, “Padding”, paddings
MKL version of conv2D :
Y = MKL_Conv2d(input, filter, padding_left, padding_right, output)
// padding_left = (2,6), padding_right =(5,9)
Padding in conv2D = "VALID", or “SAME"
Restriction:
Pad op changes the size of input. Then, in the conv2d, if "SAME" padding is assigned, then additional padding are applied. We calculate the output size based on the Padding. Currently this "Pad and Conv2D fusion" implementation does not support SAME padding.
MKL DNN conv2D API only can accept two arrays for padding. They are: pad_left(top, left) and pad_write(bottom, right). There will be one value of each of the padding, such as top, left, bottom and right.
Y = MKL_DNN_Conv2d(input, filter, padding_left, padding_right, output)
How we handle the pad+conv fusion:
Changes in Layout pass:
We check, if pad and conv2D are in correct pattern, if yes, we merge them
We check if VALID padding option is selected in the conv2d op, if yes, then only we merge. We primarily support pad+conv2D fusion for “VALID” type of conv2D padding. This is the usual use cases, such as found in Yolo v2. If needed later, fusion with SAME padding will be supported.
We replace the merged dummy fused op by the correct fused op.
Changes in Conv2d op:
The tensor format of padding in Pad operator is different than the format of padding to pass to the MKL DNN fused conv2D operator. Needed to convert the format so that proper format is passed to the MKL DNN conv2D op.
If VALID padding option in the conv2D op is passed, then there will be no padding requested from the Conv2D op. Then, when we fuse Pad and conv2D, then we calculate proper format of pad (such as the right, left, top, bottom padding). Then pass them to the MKL DNN op and execute in mkl_conv2d_ops.cc file. We calculate proper Conv2D output size based on the padding from the Pad op in mkl_conv2d_ops.h file.
Y = MKL_DNN_Conv2d(input, filter, padding_left, padding_right, output)
Unit tests:
Merge test: Two tests are written to make sure, 1) the Pad and Conv2D are merged within constrain and 2) Pad and Conv2D dont merge if the constrain does not meet
Producing correct output: Two tests are written to make sure they produce correct output, 1) NHWC format and 2) NCHW format.

@penpornk Would you mind taking a look at this?

Thank you so much for the detailed and very helpful reviews. I tried my best to address the issues. Please let me know any issues.

Thank for the suggestion of removing the duplicate edge.
I took the 1st suggestion.
I think with small change we can achieve this. We can have the following :
for (const Edge* e : pred->in_edges()) {
if (e->IsControlEdge()) {
//Don't allow duplicate edge
(*g)->AddControlEdge(e->src(), new_node, false);
}
}
Here, if duplicate edge is found, then it will return nullptr, otherwise it will add the edge.
The addControlEdge is in :
tensorflow/tensorflow/core/graph/graph.cc
Line 454 in 0126748
const Edge* Graph::AddControlEdge(Node* source, Node* dest,
And the AddEdge is in :
tensorflow/tensorflow/core/graph/graph.cc
Line 403 in 425b62a
const Edge* Graph::AddEdge(Node* source, int x, Node* dest, int y) {
Please let me know if this looks ok or not.

Could you please add a test case (some node pointing to Pad and Conv2D and some node that both Pad and Conv2D both point to) for this as well?

Sure, I have added actually two test cases, which seemed required. As you have suggested,
a) one test for one node pointing to Pad and conv2d. The test name is : TEST_F(MklLayoutPassTest, NodeMerge_PadWithConv2D_Common_InOutput)
b) The other test is common input for pad and conv2d and output from both pad and conv2d go to one node (Output2).  In this case pad and conv2d were not fused correctly, as checked and explained in https://github.com/Intel-tensorflow/tensorflow/blob/f6c9e054a042bf0f518a740380f3f96a28e8c5be/tensorflow/core/graph/mkl_layout_pass.cc#L4144. In short, if pad output is going to another node other than conv2d, then if we merge, we lost that pad output. the unit test successfully test this scenario.

Currently, there are conflicts of two files with the master, because, other PRs merged recently. I will resolve this conflict soon.

Thank you so much for the changes! I believe we are getting close.
I originally meant testing for the same incoming/outgoing control edges, but having the test for same input/output is also nice. Could you please also check for the control edges? For example, add a node X where X:control->Pad:control and X:control->Conv2D:control, and check for the output that we only have X:control->_MklConv2D:control appeared once. The same goes for outgoing control edges.

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

For example, add a node X where X:control->Pad:control and X:control->Conv2D:control, and check for the output that we only have X:control->_MklConv2D:control appeared once. The same goes for outgoing control edges.

Sorry for the delay. There are some conflicts with master, which needed to resolve.
I have added two unit tests as you have suggested above. One is to test if control edges are added as input to pad and conv2d from one common op, then control edges are not duplicated on the merged node (MklPadWithConv2d) from the common op. This test name is Input_ControlEdge_PadWithConv2D_Positive. The other test will be for output control edge from both pad and conv2d to a common op. That test name is : Output_ControlEdge_PadWithConv2D_Positive.
Needed to do some smaller edit/add code in mkl_layout_pass.cc and mkl_layout_pass_test.cc file to support these two test.
There are minor conflict in the (mkl_conv_ops.cc file) for the name of the signature of the kernel (mkl_conv_ops) between this branch and the master due to adding padding types and if pad+conv2d fusion is enabled. However, the conflict can be resolved easily when merging with master.

Thanks, it was great to work with you!

Thanks for approving the PR. Just wondering, is there anything needed to merge the branch with master?

I was waiting for the check results. Not sure why we still have some checks not completed yet. Just force-rerun it.

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

Sorry for the delay. Will look into it.

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

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@penpornk  We fixed the build errors, merge conflict and clang format errors. Thanks

There is a small issue with master which failing other testing. We are fixing those, and, then the tests will pass. So, we need wait until the fix is done in the master.

With this new commit from agramesh1, the issues should be fixed.

One test failed in Ubuntu contrib test is probably not related to this PR.
We cannot see the details on Ubuntu Python2 issue. Not sure, what is failing there.

I agree it's probably not from this PR. The tests aren't even built with --config=mkl to begin with. We are just having troubles pulling your additional changes in and I'm not sure why. Will figure this out soon.


Fallback to default_locale when locale was not specified

As today, i18n has this behavior:
I18n.locale
I18n.default_locale = :pt
I18n.locale #=> :en
I think that if the locale was not specified, #locale should return the default locale, do you agree?
For example, in a Rails application the default locale is specified the the config/application.rb file. Before loading this code, Rails loads the engines and one of the engines (rails_admin) executes I18n.locale, so the current default locale is cached to @locale and after overriding the default locale, #locale keeps returning the previous default locale, :en in this case.
What do you think?

This exact change was merged to master a few days ago: c54be4e61fe01288d4f6c0ce7067928399a2364f. See also #320 and #269.


[18.03] openmw: update hash missed in update to 0.43.0

Fixes #39712
(cherry picked from commit a8f3b1ad752c6552245f42e7428319642d7ca627)
Motivation for this change

https://logs.nix.samueldr.com/nixos/2018-08-01#1533094570-1533094336;

As discussed on IRC, there was a bungled up update to openmw, it was fixed in unstable, but not backported.
Things done

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

✔ NixOS
⬜ macOS
⬜ other Linux distributions

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

cc @dtzWill

@GrahamcOfBorg build openmw

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openmw
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openmw
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: openmw
Partial log (click to expand)
shrinking /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin/bsatool
shrinking /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin/openmw-wizard
shrinking /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin/openmw-launcher
/nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0
shrinking /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin/esmtool
shrinking /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin/openmw-iniimporter
strip is /nix/store/k8b9hqv58dd1z0j4ikak24ykndcm91s6-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0/bin
patching script interpreter paths in /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0
checking for references to /build in /nix/store/803f8h7zy88hvsxa7i1acvxmvnavl87i-openmw-0.43.0...

Failure on aarch64-linux (full log)
Attempted: openmw
Partial log (click to expand)
/build/hdf-4.2.12/hdf/src/bitvect.h:375:11: error: unknown type name 'intn'
 HDFLIBAPI intn bv_clear(bv_ptr b, bv_bool value);
           ^~~~
/build/hdf-4.2.12/hdf/src/hfile.h:559:15: error: unknown type name 'int32'
     HDFLIBAPI int32 HXPread
building of '/nix/store/ljqj8pf9p6yf3a4fmcvi24kdla99xawm-hdf-4.2.12.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/7fnagf971q7r4i4f4k1hxnky6286nnhp-gdal-2.2.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/3z6psf0kzp4ymxi7vsgxs0183z02c7ny-openscenegraph-3.4.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/chr33i9f0962ihr9yisbz3s3pc221wxs-openmw-0.43.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/chr33i9f0962ihr9yisbz3s3pc221wxs-openmw-0.43.0.drv' failed

Failure on aarch64-linux (full log)
Attempted: openmw
Partial log (click to expand)
 typedef intn (*HULsearch_func_t)(const VOIDP obj, const VOIDP key);
               ^
/build/hdf-4.2.12/hdf/src/hfile.h:479:15: error: unknown type name 'int32'
     HDFLIBAPI int32 HPgetdiskblock
               ^~~~~
building of '/nix/store/ljqj8pf9p6yf3a4fmcvi24kdla99xawm-hdf-4.2.12.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/7fnagf971q7r4i4f4k1hxnky6286nnhp-gdal-2.2.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/3z6psf0kzp4ymxi7vsgxs0183z02c7ny-openscenegraph-3.4.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/chr33i9f0962ihr9yisbz3s3pc221wxs-openmw-0.43.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/chr33i9f0962ihr9yisbz3s3pc221wxs-openmw-0.43.0.drv' failed


(PUP-5525) Fix pseudo variable assignment that happens too late

The pseudo variable for calling_module was assigned too late when
a resource was evaluated which resulted in that a hiera interpolation
used when finding default values didn't interpolate the value
correctly.
This commit ensures that the value is assigned before the external
values are resolved which means that hiera will find the right
values.
I suggest the addition of an acceptance test to verify this behavior.

Reviewed: looks good to merge. Ping @kylog


Add Institution to the account

Account has an attribute of "fiName". It would be neato if that was included on the exported data. In my particular case I have 2 accounts that are named exactly the same thing. So this would help to distinguish which account this account really is.
https://github.com/monarchmoney/mint-export-extension/blob/1aa8ffc64a584950cba70e68008bed90d74ba8e3/src/shared/lib/accounts.ts#L259 (Right around here is where the change would need to be made)
Another small observation. Maybe Monarch is using this data but the "Account Name" column in the mint-balances csv files, could probably go away. It's repetitive data that just makes the csv files larger. And the file name of the csv is the account name already.
Thanks for building this. I have around 15 years of data in mint that would be really sad to lose. So I appreciate you guys!

I believe this issue can be closed, given that the PR for it has been merged.


Bluetooth: mesh: Node Identity Advertising issue

I read in the spec (<IP_ADDRESS>.3) that Advertising with Node Identity shall be started if Mesh Proxy Service is supported and provisioning is completed using PB-GATT.
Now, Zephyr is starting Advertising with Node Identity even if provisioning was done using PB-ADV.
I was about to report an issue to the PTS that they end the tests too early to see advertisements with Network ID, but now I have doubts.
Could you please verify the implementation?
Affected TC:
MESH/NODE/CFG/GPXY/BV-02-C
When I changed Node Identity timeout, test is passing for me
CONFIG_BT_MESH_NODE_ID_TIMEOUT=5
BT_MESH_NODE_ID_TIMEOUT is set to 60 seconds by default.
In this test case (MESH/NODE/CFG/GPXY/BV-02-C), PTS is scanning about 10 seconds waiting for Network ID advertisements on two subnets only.

I've uploaded a fix candidate for this in #6962
@MariuszSkamra could you please test it? Also verify that it doesn't break any other provisioning or GATT proxy test cases.

@jhedberg Sure.
MESH/NODE/CFG/GPXY/BV-02-C is passing now, I will check the rest test mesh cases


docs(APITextInputComponent): correct label max characters

Please describe the changes this PR makes and why it should be merged:
APITextInputComponent shows max 80 characters but it's actually 45 characters according to Text Input Structure
If applicable, please reference Discord API Docs PRs or commits that influenced this PR:

Can you update the non-deno files too?


support --harmony

Adding --harmony_async_iteration in the mocha.opts has no effect on mocha-typescript-watch but work for mocha
./node_modules/.bin/mocha-typescript-watch --opts ./mocha.opts
SyntaxError: Unexpected token *

./node_modules/.bin/mocha  --opts ./mocha.opts 2>&1 >/dev/null && echo "succeed"
succeed

The #49 has been merged and released in<EMAIL_ADDRESS>


Resources of the ASM MCP Multi Clusters Workshop

Make the resources of the ASM MCP Multi Clusters Workshop publicly available for students, customers and Googlers.

Took as-is the terraform and instructions folder from the Qwiklabs repo
Created the README.md which may need a review
Places these resources under demos (not docs)
Didn't add the copyright header for the resources in the terraform folder yet, something to do later if possible/needed

sweet - we should add a reminder to add the workshop link once it works


bug: cmdheight=0 causes inconsistent behavior between : and ; with whichkey mapping

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.5 Build type: Release LuaJIT 2.1.1702233742
Operating system/version
Linux mechrevo 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35 +0000 x86_64 GNU/Linux
Describe the bug
When mapping ; to : with whichkey and setting cmdheight=0, pressing ; once won't show cmdline but pressing : once will.
Steps To Reproduce

Use the repro.lua
press : once, statusline disappears. press esc to go back to normal mode.
press ; once, statusline won't disappear, but keep typing it will disappeaer.

Expected Behavior
The behavior of ; is the same as : when mapped against it.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/which-key.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.o.cmdheight = 0
local wk = require('which-key')

wk.register({
  [';'] = {':', 'Enter command mode', opts = {  }},
}, {})

Trying to remap : acts strange for me regardless of the cmdheight setting.


OCM-7079 | feat: select security groups interactive - filtering

Checking if the security group has a cluster tag, and filter accordingly.
Improve UX by preventing an error returned from the backend, for the same validation.

/lgtm


Linking errors when enabling 'Minimal mDNS' tests

Problem
After we pulled changes from upstream repository, we can't link with some of MinimalMdns function.
Proposed Solution

List all MinimalMdns functions which causes that problem.
Check upstream repository for possible fix
Fix it!

GN scripts fixed and changes commited to test-unittests branch. All Minimal DNS tests are passed.


Native Notebooks - Latex rendered strangely

VS Code Version: 1.58.2
OS Version: Windows

Steps to Reproduce:

Open notebook
Run $ \ne $ in markdown cell

Expected Output:

Actual Output:

Duplicate of #128490
Should be fixed in the first 1.60 insiders builds


Default Profile/Custom Profile setup ?

Empire Version
2.3
OS Information (Linux flavor, Python version)
Ubuntu 16.04.3
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
I'm trying to setup a custom profile however i can't no longer see the configuration setup in setup_database.py . Where do you set the profile  and how do you change the index.jsp, index.php, index.jsp ?
Thanks,
Screenshot of error, embedded text output, or Pastebin link to the error
Any additional information

You shouldn't need to do anything to setup_database.py. When you are setting up your listener within Empire you can do the following to change those things:
listeners
uselistener http
set DefaultProfile url/one.php;urltwo.html;/content/url/three.jsp|Some User Agent|CustomHeader1:Value1|CustomHeader2:Value2

Above sets three custom pages, modifies the user agent to "Some User Agent", and adds on two Custom HTTP Request headers.

Thanks for your help.
Regards,


[FEATURE REQUEST] Allow management and report status of "PERI" alarm

First of all thanks for this great job!
One thing I miss in the Securitas Direct integration in HA is that I cannot check the status of the perimeter alarm or activate/deactivate it.
I know it was exposed by the earlier API because the component Cebeerre developed by supported it.
Is it anything you could do for adding this feature?

Thanks for this.  I am a total noob to HA, Python etc. so I have a lot to learn.  I DID get it working, so am really thrilled.  +1 for any feature requests - Annex (secondary) alarm would be great, and I can't see how to set Partial Day/Night...  I will keep exploring.

Thanks @bvis for the feature request. How I write the api was by opening the https://customers.securitasdirect.es/owa-static/login web application and logging calls to the /owa-api/graphql with the json payload.
If you need help let me know and we can work on getting those logs.

Hi, now I have had some time for doing this. It was so easy because all the calls are as you said between the browser and the backend:
First request:
{
   "operationName":"xSArmPanel",
   "variables":{
      "request":"PERI1",
      "numinst":"XXXX",
      "panel":"SDVFAST",
      "currentStatus":"D"
   },
   "query":"mutation xSArmPanel($numinst: String!, $request: ArmCodeRequest!, $panel: String!, $pin: String, $currentStatus: String) {\n  xSArmPanel(numinst: $numinst, request: $request, panel: $panel, pin: $pin, currentStatus: $currentStatus) {\n    res\n    msg\n    referenceId\n  }\n}\n"
}

First response:
{
   "data":{
      "xSArmPanel":{
         "res":"OK",
         "msg":"Su solicitud ha sido enviada",
         "referenceId":"XXXX"
      }
   }
}

Polling request:
{
   "operationName":"ArmStatus",
   "variables":{
      "request":"PERI1",
      "numinst":"XXXX",
      "panel":"SDVFAST",
      "currentStatus":"D",
      "referenceId":"YYYY",
      "counter":1
   },
   "query":"query ArmStatus($numinst: String!, $request: ArmCodeRequest, $panel: String!, $referenceId: String!, $counter: Int!) {\n  xSArmStatus(numinst: $numinst, panel: $panel, referenceId: $referenceId, counter: $counter, request: $request) {\n    res\n    msg\n    status\n    protomResponse\n    protomResponseDate\n    numinst\n    requestId\n    error {\n      code\n      type\n      allowForcing\n      exceptionsNumber\n      referenceId\n    }\n  }\n}\n"
}

Polling first response:
{
   "data":{
      "xSArmStatus":{
         "res":"WAIT",
         "msg":"Petición en proceso",
         "status":null,
         "protomResponse":null,
         "protomResponseDate":null,
         "numinst":null,
         "requestId":"_pollingStatus_56613",
         "error":null
      }
   }
}

Final response:
{
   "data":{
      "xSArmStatus":{
         "res":"OK",
         "msg":"La zona exterior ha sido conectada",
         "status":"3",
         "protomResponse":"E",
         "protomResponseDate":"2022-01-07 22:38:22.306",
         "numinst":"XXXX",
         "requestId":"_pollingStatus_57119",
         "error":null
      }
   }
}

When only the perimetral alarm is activated the request/answer is like this:
{
   "operationName":"CheckAlarmStatus",
   "variables":{
      "numinst":"XXXXX",
      "panel":"SDVFAST",
      "referenceId":"XXXX",
      "idService":"11",
      "counter":3
   },
   "query":"query CheckAlarmStatus($numinst: String!, $idService: String!, $panel: String!, $referenceId: String!) {\n  xSCheckAlarmStatus(numinst: $numinst, idService: $idService, panel: $panel, referenceId: $referenceId) {\n    res\n    msg\n    status\n    numinst\n    protomResponse\n    protomResponseDate\n  }\n}\n"
}

After some WAITS, the final answer:
{
   "data":{
      "xSCheckAlarmStatus":{
         "res":"OK",
         "msg":"Tu Alarma está conectada en el exterior",
         "status":"3",
         "numinst":"XXXX",
         "protomResponse":"E",
         "protomResponseDate":"2022-01-07 22:56:47.126"
      }
   }
}

Other statuses are:
{
   "operationName":"CheckAlarmStatus",
   "variables":{
      "numinst":"XXXXX",
      "panel":"SDVFAST",
      "referenceId":"YYYYY",
      "idService":"11",
      "counter":3
   },
   "query":"query CheckAlarmStatus($numinst: String!, $idService: String!, $panel: String!, $referenceId: String!) {\n  xSCheckAlarmStatus(numinst: $numinst, idService: $idService, panel: $panel, referenceId: $referenceId) {\n    res\n    msg\n    status\n    numinst\n    protomResponse\n    protomResponseDate\n  }\n}\n"
}

{
   "data":{
      "xSCheckAlarmStatus":{
         "res":"OK",
         "msg":"Tu Alarma está conectada en modo Parcial Día y en el exterior",
         "status":"B",
         "numinst":"XXXXX",
         "protomResponse":"B",
         "protomResponseDate":"2022-01-07 23:01:45.716"
      }
   }
}

{
   "data":{
      "xSArmStatus":{
         "res":"OK",
         "msg":"Tu Alarma está conectada en modo Parcial Noche y en el exterior",
         "status":"C",
         "protomResponse":"C",
         "protomResponseDate":"2022-01-07 23:05:29.380",
         "numinst":"XXXXX",
         "requestId":"_pollingStatus_238933",
         "error":null
      }
   }
}

Awesome! Let me work on that tomorrow!

I added the support for the PERI1 type of alarm in this commit, can you download and test it and tell me if it works?

I’ll do it asap, tonight when I’m at home

When I pressed the CUSTOM BYPASS it has activated the "PERI" alarm! Nice!
But it's incorrectly seen in the panel:

In fact the current status is this one:

It seems it's displaying the different statuses wrongly.
When I press the ARMAR EN CASA button the status shown in the panel is this one:

And the real status is:

And when I press the button of ARMAR AUSENTE the other is activated, why seem to be switched by mistake, could it be?

On other hand it would be very useful, I don't know if it's possible, to have a "button" or activator to do a call to the remote system and update the status of the sensor. This way I could check the current status of the alarm in case I want to program an scenario or script, as it's very usual to change the status via the control panel we have in home.

Thanks for the update on the perimeter alarm. I see what you mean when you said that is reporting the incorrect status.
Home Assistant define a set of possible status for the alarm, defined here.
The original code for the integration of the alarm used that custom state STATE_ALARM_ARMED_CUSTOM_BYPASS for the perimeter alarm. I don't know how to set a custom state for the panel.

On other hand it would be very useful, I don't know if it's possible, to have a "button" or activator to do a call to the remote system and update the status of the sensor. This way I could check the current status of the alarm in case I want to program an scenario or script, as it's very usual to change the status via the control panel we have in home.

This is happening in the background automatically. I push a new changed in the alarm_control_panel.py file, please update and tell me if it fix the issue.

After this update now it's reported like this:

This is how it's seen:

AFAIK it should be in the state armes_cusom_bypass, as I see in the possible status list:
https://developers.home-assistant.io/docs/core/entity/alarm-control-panel/#states

Now I realized that there are three new states for when the perimeter is active,
"protomResponse":"C", Tu Alarma está conectada en modo Parcial Noche y en el exterior
"protomResponse":"B", Tu Alarma está conectada en modo Parcial Día y en el exterior
"protomResponse":"E", Tu Alarma está conectada en el exterior
So I pushed new changes to group all those changes into the CUSOM_BYPASS.

Here is the commit
Tell me how it looks like right now.

Hi and thanks again for this, you are so responsive!

As you may see it right now show the "correct", based in the current limitations the alarm control panel card has. Thanks a lot for this!
One improvement which I think shouldn't be hard to do is to add an attribute to the current sensor with the obtained message, it contains the exact sentence like in my example: `"msg":"Tu Alarma está conectada en modo Parcial Noche y en el exterior".
It could be something like this, it would be very helpful because I could show the message below the alarm card to give me more information.
state: armed_custom_bypass
code_format: number
changed_by: null # I always see this as null, maybe it's a bug, IDK
code_arm_required: false
friendly_name: CASA
supported_features: 23
message: Tu Alarma está conectada en modo Parcial Noche y en el exterior

On other hand I suspect there's another protomResponse to add that I didn't add in my examples, when it's completely activated (AWAY+PERI).
This is answer I obtain when it's in this status:
{
   "data":{
      "xSArmStatus":{
         "res":"OK",
         "msg":"Tu Alarma está conectada en modo Total y en el exterior",
         "status":"4",
         "protomResponse":"A",
         "protomResponseDate":"2022-01-09 01:40:23.536",
         "numinst":"XXXXXXXX",
         "requestId":"_pollingStatus_244486",
         "error":null
      }
   }
}

Related to this I've created this PR: https://github.com/guerrerotook/securitas-direct-new-api/pull/16

Yeah, I'm looking forward in how to add custom attributes to an entity so I can add more information. I'm going to investigate this.

Hi,
Thanks for this work!
I can activate the exterior perimeter with arm_custombypass but I cannot disarm it... Even when I set with node red, alarm_arm_home and then alarm_arm_custombypass and after when I disarm with alarm_disarm, only the mode Home (or away) is disarmed and not the exterior perimeter. It stays armed.
What do I need to do to disarm the custombypass and not only the arm_away or arm_home ?
Thanks a lot!

#71 It is the same that this issue.

I think this is solved with latest releases.


Is There An Option For Input

If this is not triggered by queue but still need to pop or peek a message from the queue, is there an option to dequeue a message with an input binding?

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

ID: 5063120f-d48e-6a76-8e6d-208ead92d187
Version Independent ID: 72bb8ecc-6dec-079a-a9d4-52205466a8c6
Content: Azure Queue storage bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-queue.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for the question! We are investigating and will update you shortly.

Hi @IndreamLuo Not sure if I'm understanding your question clearly but here are my thoughts:

Are you asking how to dequeue messages in a scenario where your Function app is triggered by a different event? If so, input binding will only carry payload specific to the trigger you've used. If you still need to interact with queue operations in same context, you may have use Queue SDK and implement those operation right in your Function app.
Alternatively, if you're curious about what happens to messages after they've been processed in your Function App successfully or not, this documentation and followed by this SO post should help you. In a nutshell, Functions runtime will attempt to retries, if unsuccessful, and it'll ultimately send the message to poison queue for processing later.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


A new plugin for oh-my-zsh: Complete other zsh sessions directories

This plugin allows the user to complete other zsh session pathes by hitting 'CTRL+v'.

Works for me on Ubuntu 15.10, also it complete zsh session in tmux.

Thank you for testing


Misleading error message with child injector

If you have a child injector and ask the parent injector a value for a binding defined in the child, you get an "It was already configured on one or more child injectors" error.
It would be better to say "No implementation for ... was bound, although it is configured in a child injector".
Here's a sample code:
import com.google.inject.AbstractModule;
import com.google.inject.Guice;
import com.google.inject.Injector;

public class GuiceBug {

    public static void main(String[] args) {
        Injector i1 = Guice.createInjector();
        Injector i2 = i1.createChildInjector(
                new AbstractModule() {
                        @Override
                        protected void configure() {
                            bind(IStuff.class).to(Stuff.class);
                        }
                    });
        i1.getInstance(IStuff.class);
    }

    static interface IStuff {}

    static class Stuff implements IStuff {}
}

Exception in thread "main" com.google.inject.ConfigurationException: Guice configuration errors:

1) Unable to create binding for org.enercoop.test.GuiceBug$IStuff. It was already configured on one or more child injectors or private modules
    bound at org.enercoop.test.GuiceBug$1.configure(GuiceBug.java:15)
  If it was in a PrivateModule, did you forget to expose the binding?
  while locating org.enercoop.test.GuiceBug$IStuff

1 error
    at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1004)
    at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:961)
    at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
    at GuiceBug.main(GuiceBug.java:18)

I can't help but think @laurentmartelli was right about this error.

With my bind call, I get this error
If I comment out my bind call, I get "No implementation for ... was bound"

How can I have too many bindings, then remove one binding, and then not have enough?

fyi I also found this extremely confusing.

NB child injectors are extremely confusing. We try hard to avoid using them internally.

Yeah the error message is confusing. However now googling the error will give this discussion and allow people to resolve it despite the wording. Thanks @laurentmartelli!

1 on this

It was confusing for me as well, googling this discussion turned out the fastest way to find the actual cause, so the message could just as well have a link to this discussion.

The message is indeed misleading, spent a lot of time scratching my head about how the hell parent injector has bindings from child modules until dtumbled on this issue.

Yep, it is confusing. I was trying to find a second place where my class is bound in a way which conflict with a binding which was "already" made in another place. The error message is doubly confusing, when seen in this light, because it lists only one binding. FWIW, I'm not a native speaker - I think you should take into account that not everyone may understand a word to be used in its secondary or tertiary meaning.


Consistent default objectives

I already built in default objectives in the R package and they are not the same as those recently added to the API in the Java lib (see bb0ac38be423bc1cf654c43942d2001b215a8782, 01b8289ddaf9491d4b71660d6fd0f956324167e0 and b6aa10dc9e9c6e89c7135ff00e12c2d1ab7f4503). I suggest the following defaults (in this order):

E-NE with Modified Roger's distance (genotypes)
E-NE with Gower's distance (phenotypes)
E-NE with precomputed distances

The API now uses A-NE as default distance aggregation and prefers phenotypes over genotypes which I would swap.
@daveneti do you agree that I make these changes?

@daveneti Do you plan to enable just one objective by default in the GUI or one per data type (genotypes/phenotypes/distances) as part of a weighted index? Whatever we prefer, we should make sure it the GUI and R interface do the same.

I have added a methods in API on the release\gui-dev branch that provide the default objectives. These are just guesses that the monent. I will align with you decision when i merge back to develop

Ok I have currently implemented the defaults from above, in that order of preference when multiple types of data are included. I guess it is better though to default to a weighted index in the latter case (with equal weights) so I will change that.

Hi @hdbeukel, where did you change the defaults? I did not see the changes. In the GUI I use the
public static final List<CoreHunterObjective> createDefaultObjectives(CoreHunterData coreHunterData) method to create the default objectives. This creates one default objective for each available type of data. At the moment I am not sure what to do about the weights. I think it does not matter if the sum of the weights is not 1. So dividing by the number of objectives is not important. However, in the interface I think that the weights should be added as an integer summing up to 100. I.e. a percentage, I think this is more easy to understand and edit.

I implemented those in the R package which does not (yet) use the new API methods that you added for creating default objectives. I will align both interfaces soon. You are right that the weights do not need to sum to 1. I am ok with your suggestion of summing to 100 in the GUI.

Thanks, my current plan is to keep working on the gui release branch to make minor adaptations needed for the gui, merge this into develop on a regular basis and merge in any of your changes from develop.

I pulled in your changes to my branch and updated the default objectives. The tests are now running and then I will merge my branch into develop.


Ignore F403 errors in preludes.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

@jaheba let’s always have description in PRs, however short. Some context is always useful. Also labels: does this need to be backported?

Added description. I think we can backport this, but there is no rush since this doesn't just anything functional but makes the CI pass on the ruff check.


CM-25728 - Fix relative paths; fix validations of paths

before

after

plus fix of relative paths


Don't serialize empty collections and dummy objects

Hey,
how could change serialization of empty lists? My classes often uses (Observable)Collections for storing objects in properties. For avoiding NullReferenceExceptions accessing the list it will be preinitialized in Constructor. Therefore the property have a value which will be serialized. But it contains no useful information. Therefore I would avoid property tag in XML.
How could I configure Serializer (v2) don't serializing properties which are only an empty list?
Another use case is creation of dummy objects which have Id = 0. Could I conditionial check in serialization process for an property value (like an Id) and avoid serializing this object in case of specific value?
Thx Thomas

Hi @thomasjoscht thank you for your questions here.
To start with the empty lists, if the property is writable, we need to signify in some way that an object is required (or expected) upon deserialization.  It would be possible to make it always force a create, even if there is none, but that might be a little more work.
We do support read-only collection properties.
So you could do something like this:
public class Subject
{
		public ObservableCollection<ObjectType> Counts { get; } = new ObservableCollection<ObjectType>();
}

And it will serialize for you as it does now with a writable-property.
Unfortunately, currently this is emitted even if there are not any items.  I agree with you and think that we should reduce the amount of emitted data where possible.  Currently we only emit values that are "assigned" (not-null or not default).  In the case of read-only lists we should do the equivalent and only emit when there are items.
Sound good to you?
As for the dummy serialization, this is also a good question. :)
We do have the ability to ignore and include members, and also to do so based on specification (conditions).  Unfortunately they were not wired up.  I took some time to do so, and you can now see how this is done here:
https://github.com/wojtpl2/ExtendedXmlSerializer/blob/001b9f1d1b3cef726d01748406ef04d1c1e31f31/test/ExtendedXmlSerializer.Tests/ReportedIssues/Issue128Tests.cs
Unfortunately, we do not have a way of saying "when you see this type, emit it based on this specification".  It might not be so difficult to do, however.  So I will see what you think of the above changes before working on that.

Hi @Mike-EEE,
thanks a lot for your answers.  This is awesome!
Most part of my code could be changed to readonly collection properties. So your approach will work. Sometimes it could be that read-only is not possible in special circumstances, f.e. the collection property itself has some setter behaviour like NotifyPropertyChanged or the class is used by other libraries requiring setter like EF. But this is not really a problem in my case. Thx
Secondly for my dummy objects your approach also works fine. The solution to specify the condition for each member is passable in my app because dummy objects only necessary in special cases. A broader way specifing conditions for types instead of members could pe perfect, but I think the approach potentially willl not work in all ways (special exclusions). For me it is not necessary. Therefore Thx again!
A soon nuget publish will be nice ;-)
Regards, Thomas

Cool, @thomasjoscht!  Glad things will work for you as-is.  However, I do think having the ability to emit-per-type would be valuable.  It is actually something that was part of the original vision of this v2 work, so I should probably add it.  Shouldn't take more than today.  Then @wojtpl2 should be able to get a NuGet Alpha 7 push out for you. :)
In the meantime, you can always try cloning the project locally and reference it as a .csproj in your working SLN, if that makes sense.  I can provide further instruction if necessary.

This issue should be resolved now.  Please feel free to add a comment if not and we will take it from there.

Unfortunately, we do not have a way of saying "when you see this type, emit it based on this specification". It might not be so difficult to do, however. So I will see what you think of the above changes before working on that.

I would like to ask to revisit this issue. I have a project with a large amount of objects containing ICollections. These are defaulted, when the objects are constructed, to new List(), which makes me unable to use the EmitBehaviors that are included. Potentially I could setup configuration for each and every member, using .EmitWhen, but that would make for a large amount of configuration. Fortunately, all of these objects inherit from a common abstract class Entity. What I would be hoping to do would be something like:
new ConfigurationContainer().ConfigureType<ICollection<Entity>>().EmitWhen(e => e.Count != 0) or possibly
new ConfigurationContainer().ConfigureType<ICollection<Entity>>().Emit(EmitBehaviors.NotEmpty)
Is this already possible in some way that I have missed, or would this have to be added?

Cool @frjonsen thanks for  pinging back regarding this.  We're ramping up for 2.1 in the near future.  I think this is possible to do for this release.  I've added it to our list as a new issue:
https://github.com/wojtpl2/ExtendedXmlSerializer/issues/145
Please feel free to add additional feedback there. :)


Nested structure methods can not be found

type String string

func (self String) String() string {
	return string(self)
}

type Second struct {
	Name String
}
type Person struct {
	SecondName Second
	Age        int
}

func main() {
	const test = `
	print(user.SecondName.Name.String())
`

	L := luar.Init()
	defer L.Close()

	user := &Person{SecondName: Second{"lion"}, Age: 46}

	luar.Register(L, "", luar.Map{
		"user": user,
	})

	err := L.DoString(test)
	if err != nil {
		fmt.Println(err)
	}
}

run this , It show error:
[string "..."]:2: attempt to call field 'String' (a nil value)

Thank you for the catch. The bug comes from an unanswered design issue. Let me break it down:
When calling GoToLuaProxy() over a struct, the struct is (usually) not
addressable and a Lua table is created. This table has no method.
When calling GoToLuaProxy() over a pointer to a struct, a proxy is created and the struct methods are callable.
The flaw shows when a direct struct is inside the struct proxy, as in your example: &Person{SecondName: Second{"lion"}, Age: 46}.
SecondName is not a pointer and thus it will be returned as a Lua table without methods.
In that case however, the inner struct is addressable, so it would be possible to proxify it.
I could change the code so that proxy array/struct members are always proxified.
The would change the inner representation of the proxy value and I wonder if this would have any undesirable side effects. Any comment on that?
I've pushed the changes on the #proxy-nesting branch. Let me know what you think.

Same thing for slices and the fix is the same.
However, the values of struct-maps and plain structs are not addressable.
The solution would be to allocate a new struct each time.
This indulges a significant performance cost however.
Proxies serve two purposes:

Allow direct modification of the Go value from Lua code.

Call methods.

In the case of unaddressable values, proxies are only useful for calling methods.
I suggest the following implementation instead of checking if struct/arrays are addressable:

If the input to GoToLuaProxy() is a pointer to a struct/array, then proxify.

If not a pointer and no method, then convert to a Lua table.

If not a pointer but has methods, then allocate a new object and return a proxy to it: modifying the proxy will have no effect, but at least the methods can be called.

Thank you! It worked. I can continue to work down, thanks again. I will read your code and I do not know if I can make useful suggestions.

Hey, I wasn't done with it! :p
In fact my aforementioned solution is badly designed, I have been experimenting and I think I came up with a right approach for structs and arrays. Stay tuned.

very sorry. I will continue to be concerned. ths

I have pushed some commits on the #proxy-nesting2 branch.
Here are the updated, better specified rules for converting from Go to Lua:
// Proxies have several uses:
//
// - Type checking in Go function calls, so variable of user-defined type are
// always profixied.
//
// - Reflexive modification of the Go data straight from the Lua code. We only
// allow this for compound types.
//
// - Call methods of user-defined types.
//
// Predeclared scalar types are never proxified as they have no methods and we
// only allow compound types to be set reflexively.
//
// Structs are always proxified since their type is always user-defined. If they
// they are not settable (e.g. not nested, not passed by reference, value of a
// map), then a copy is passed as a proxy (otherwise setting the fields from Lua
// would panic). This will not impact the corresponding Go value.
//
// Arrays are only proxified if they are settable (so that the user can set the
// Go value from the Lua side) or if they are of a user-defined type (method
// calls or function parameters). If the type user-defined but the array is not
// settable, then a proxy of a copy is made, just as for structs.
//
// Lua cannot dereference pointers and Go can only call methods over one level
// of indirection at maximum. Thus proxies wrap around values dereferenced up to
// the last pointer.
//
// Go functions can be passed to Lua. If the parameters require several levels
// of indirections, the arguments will be converted automatically. Since proxies
// can only wrap around one level of indirection, functions modifying the value
// of the pointers after one level of indirection will have no effect.

Please let me know if that works for you and I will merge.

@liyonglion Any feedback?

I have merged the change into master.


Can't update graphenelib

Why is graphenelib forced to use version 0.6.6 or lower in the python-bitshares requirements. I would need to update this to get rid of deprecation warning caused by graphenelib.
"CryptographyDeprecationWarning: signer and verifier have been deprecated. Please use sign and verify instead."

Sorry about that, but the most recent version of pygraphene brings breaking changes.
I expect the release of a new pybitshares version to happen shortly.
In the meantime, you can always install from the repo's develop branch with something like this:
pip3 install -e git://github.com/bitshares/python-bitshares@develop#egg=bitshares

Thank you for your response.


Any possibilities to add account section for customer?

To track order history, personalized coupon and stuff.

@diboune

@zahidul-islam-selise this starter didn't use the Customer module but there's other starters that use it here's an example

Thanks, I really like this starter. So it would be easy to integrate to this one right?

yes very simple code and very good docs and examples