Standardize how LLM output is stored in a ProviderResponse output object

ProviderResponse has an output field that is documented to be either a string or an object.
If it's a string, then the Web UI shows a nice diff between the LLM outputs when comparing two prompts or providers.
However, if it's an object, the serialized object is shown and you lose the nice diff output.
Can a convention be established about what goes into the object, specifically if a field with a specific key exists, then that represents the LLM output? (And any other fields can be visible in the Web UI if you click on the magnifying glass).

This seems reasonable.  What do you think we should call the displayed field?  content, display, text?

This seems reasonable. What do you think we should call the displayed field? content, display, text?

I prefer text or content.

Added a frontend configuration for this in #893


Scroll bars

Constantly losing scroll bars. They also need to be wider. Currently difficult to grab

ok, np.

or what do you mean by 'losing' ?

now a little bigger, reopen if you need it bigger


ai quotes generation

Issue: #21
Add functionality to generate quotes randomly through gemini api.
When running on local machine do following

npm install
node server.js or nodemon server.js if available
check if server is running on localhost:3000
Then open index.html with live server
choose category and click AI_Quotes button which redirects to ai.html with quotes and functionality to copy text.

Also, don't forget to star the repo. Thank you!


Set the secure attribute of the token cookies.

Describe the feature
I would appreciate it if there is a possibility to set the Secure attribute on both token and refresh cookies. Thus resulting in the cookies only being sent through HTTPS.
I will link the PR where I already made changes which worked in both relevant playgrounds. For now, the secureCookieAttribute defaults to false, even though I am open for discussions about a more secure default by switching it to true if not defined otherwise.
How would you implement this?
How about adding a new attribute in nuxt.config.ts in both ProviderLocal and ProviderRefresh? Nonetheless, open for other ways on how to implement the Secure attribute of the token and refresh cookies.
Additional information

[X] Would you be willing to help implement this feature?

Provider

[ ] AuthJS
[X] Local
[X] Refresh
[ ] New Provider

I think not, you can configure it with auth js instead.

Closed via #729


test: build unit test & integration test

is the scope of this PR to have 100% of coverage on both: unit test and integrations test?


Support sending log data to Activity Tracker service

The code app.js currently simply drop the data that comes from the audit log webhook on stdout - assuming that there is a logging agent that will pick up the container output and forward to the logging service.
The IBM Cloud Activity Tracker with LogDNA service is the audit service provided by IBM Cloud. User actions against cloud resources are automatically sent to the service providing an audit trail.
There is some debate if kube audit logs should be stored in the Activity Tracker (AT) service or not. Currently audit-events that are sent to AT are generated exclusively by IBM services operating on resources on behalf of a customer action. The IKS master is run/managed by IBM, but the audit events are more kube-centric than IBM Cloud centric.
In any case - this entire project is a work-around to get the data out of the IKS master API server and get it into the customers hands. It is reasonable to allow the customer to send that data where they want.

There is one line of code that is responsible for emitting the audit log data
console.log(JSON.stringify(data.items[i]));

The AT service is built on top of LogDNA. Audit logs are 'just log data' and can easily be stored in a LogDNA account. The IBM Cloud is capturing all of the audit data from IBM services and sharing it wth customers via a LogDNA instance that is isolated for audit data.
We can make use of the Node.js library to forward data. This should be a relatively simple change to app.js.
When visiting the IBM Cloud web interface for AT the ingestion token is not shown to the user.

However, if we visit the LogDNA user interface and manage the API keys, then the ingestion key is visible to us.

Thus we have all the parts we need to send data from this webhook target to Activity Tracker.


Install-WindowsUpdate bombing on high number of updates - add "BatchSize" parameter?

I have a machine that needs 135 updates - but keeps bombing on one of the downloads and can't move forward.  When i do them manually, batching usually helps fix many situations.
It would be great if I could tell Install-WindowsUpdate to only download and install 10-20 updates at a time.
Would be even better if it could skip ones it bombed on the previous run - but that seems like it could complex.

Or maybe just have it ignore errors. Report them but dont fail the run.
Another thing to look at is using the -criteria argument. Boxstarter uses:
IsHidden=0 and IsInstalled=0 and Type='Software'

If none is given. I'm not very familiar with the syntax but if you research the win update API it might allow you to filter based on KB or string.


feat: ability to copy freight id and alias

Closes https://github.com/akuity/kargo/issues/1197

Is there a way to see the freight ID without copying it? Sometimes I just want to visually see the ID (e.g. mentally map it to a CR i see from kubectl get freight).


Allow Custom Table names

DynamoDB does not has any namespace concept, except account.
This patch allows to override hard-coded table dynamo table names.

Hi, thanks for the PR. We also identified that very same issue.
However we decided to take a different approach and allow the definition of an optional table name prefix, that gets added to all the table names (if defined). I.e. the table name prefix applies to all the tables in the same plugin and cannot be defined individually for each table.
We think this solves the namespace issue, with a simpler configuration model.
The changes were introduced by this commit (https://github.com/curityio/dynamodb-data-access-provider/commit/97b62235203f4bb192acd67eda9fc0b0570e824d) and are already available in master.


Add deploy-setup-k8s-dev-mode Makefile target

Since deploy-setup-k8s disables webhook,
adding deploy-setup-k8s-dev-mode make target which does
exactly the same but respects previous
ENABLE_ADMISSION_CONTROLLER value.
This allows to run k8s deploy with webhooks, straight forward.
Signed-off-by: Or Shoval<EMAIL_ADDRESS>

/cc @zshi-redhat

/cc @zshi-redhat

@oshoval does current operator webhook work in vanilla k8s environment? how the certificate is handled?

/cc @zshi-redhat

@oshoval does current operator webhook work in vanilla k8s environment? how the certificate is handled?

The default make target deploy-setup-k8s disables the webhook, so no need to use certificates,
we do want to use webhooks and when we use them we self sign the cert, and inject it manually (there is other issue on the reconcile of it).
This PR only introduce a new make target which will not disable the webhook in case the user set them to be enabled,
as the current make target  deploy-setup-k8s disregard the exported value of ENABLE_ADMISSION_CONTROLLER and sets it to false hard-coded.

/cc @zshi-redhat

@oshoval does current operator webhook work in vanilla k8s environment? how the certificate is handled?

The default make target deploy-setup-k8s disables the webhook, so no need to use certificates,
we do want to use webhooks and when we use them we self sign the cert, and inject it manually (there is other issue on the reconcile of it #3).

ok, so once #3 is resolved, we would remove the hardcoded ENABLE_ADMISSION_CONTROLLER=false no longer need this dev-mode, correct?

/cc @zshi-redhat

@oshoval does current operator webhook work in vanilla k8s environment? how the certificate is handled?

The default make target deploy-setup-k8s disables the webhook, so no need to use certificates,
we do want to use webhooks and when we use them we self sign the cert, and inject it manually (there is other issue on the reconcile of it #3).

ok, so once #3 is resolved, we would remove the hardcoded ENABLE_ADMISSION_CONTROLLER=false no longer need this dev-mode, correct?

I don't think so, the reason of ENABLE_ADMISSION_CONTROLLER=false is the unsupported nics.

/cc @zshi-redhat

@oshoval does current operator webhook work in vanilla k8s environment? how the certificate is handled?

The default make target deploy-setup-k8s disables the webhook, so no need to use certificates,
we do want to use webhooks and when we use them we self sign the cert, and inject it manually (there is other issue on the reconcile of it #3).

ok, so once #3 is resolved, we would remove the hardcoded ENABLE_ADMISSION_CONTROLLER=false no longer need this dev-mode, correct?

I don't think so, the reason of ENABLE_ADMISSION_CONTROLLER=false is the unsupported nics webhook validation.
once #3 will be solved the new target will be able to use webhooks and inject self signed certs,
while the previous target will stay with webhooks disabled i think.

I was thinking once #3 is resolved, then we can enable the admission controler webhook by default for vanilla k8s deployment.
The admission controller webhook can validate both unsupported NICs ID and other validation/mutating functions that's already supported by existing webhooks.
User who wants to disable it can export the ENABLE_ADMISSION_CONTROLLER env var to false manually or in their automatic script, no need to maintain two different entries in Makefile for changing admission controller mode. wdyt?

I was thinking once #3 is resolved, then we can enable the admission controler webhook by default for vanilla k8s deployment.
The admission controller webhook can validate both unsupported NICs ID and other validation/mutating functions that's already supported by existing webhooks.
User who wants to disable it can export the ENABLE_ADMISSION_CONTROLLER env var to false manually or in their automatic script, no need to maintain two different entries in Makefile for changing admission controller mode. wdyt?

Yep, Its a possibility, but https://github.com/k8snetworkplumbingwg/sriov-network-operator/issues/10 should be fixed as well (i am on it),
and documentation should reflect ENABLE_ADMISSION_CONTROLLER and configmap of unsupported nics,
I will do that in case needed once we are done with all the changes we described.
Meanwhile should / can we merge this PR?

I was thinking once #3 is resolved, then we can enable the admission controler webhook by default for vanilla k8s deployment.
The admission controller webhook can validate both unsupported NICs ID and other validation/mutating functions that's already supported by existing webhooks.
User who wants to disable it can export the ENABLE_ADMISSION_CONTROLLER env var to false manually or in their automatic script, no need to maintain two different entries in Makefile for changing admission controller mode. wdyt?

Yep, Its a possibility, but #10 should be fixed as well (i am on it),
and documentation should emphasize imo ENABLE_ADMISSION_CONTROLLER=falsein case using unsupported nics
and how to use configmap in order to support them, as alternative.
I will do that in case needed once we are done with all the changes we described.
Meanwhile should / can we merge this PR?
The reason is that it allows to use k8s with webhooks with just one make target command, in respect to operator deployment.

@oshoval if this is just about having a way for running admission controllers on vanilla k8s, I think you probably can first deploy with make deploy-setup-k8s on vanilla k8s, then patch the default SriovOperatorConfig custom resource to enable both EnableInjector and EnableOperatorWebhook. Is it acceptable for your testing?

I was thinking once #3 is resolved, then we can enable the admission controler webhook by default for vanilla k8s deployment.
The admission controller webhook can validate both unsupported NICs ID and other validation/mutating functions that's already supported by existing webhooks.
User who wants to disable it can export the ENABLE_ADMISSION_CONTROLLER env var to false manually or in their automatic script, no need to maintain two different entries in Makefile for changing admission controller mode. wdyt?

Yep, Its a possibility, but #10 should be fixed as well (i am on it),
and documentation should emphasize imo ENABLE_ADMISSION_CONTROLLER=falsein case using unsupported nics
and how to use configmap in order to support them, as alternative.
I will do that in case needed once we are done with all the changes we described.
Meanwhile should / can we merge this PR?
The reason is that it allows to use k8s with webhooks with just one make target command, in respect to operator deployment.

@oshoval if this is just about having a way for running admission controllers on vanilla k8s, I think you probably can first deploy with make deploy-setup-k8s on vanilla k8s, then patch the default SriovOperatorConfig custom resource to enable both EnableInjector and EnableOperatorWebhook. Is it acceptable for your testing?

Yes, i am doing it little different,
https://github.com/kubevirt/kubevirtci/pull/500/files#diff-499cff045d8a875e8b39f4a9fd59354eb99e8f8d91a95ebc70fbf42d2d5b5beaR190
just thought its better in one liner, until we fix all the issues.
Closing thanks.


Defining the 'publish' task conflicts with the built in maven-publish task

[https://docs.gradle.org/nightly/userguide/publishing_maven.html](maven-publish plugin) defines publish already.
I figure we should call it publishService instead

Hrm, I need to ponder this some more. The existing publish task that I've added to the plugin (unreleased) relies on the maven plugin for uploading. If I were using maven-publish for uploading, I would need a different set of requirements
(Thinking aloud) I wonder if what will be needed is support for both plugins, for example, if you have the maven plugin we define the serviceArchives configuration and ensure the right artifacts are thereIf we use the maven-publish plugin, we add the appropriatepublications` for that.

According to @ysb33r, who I ask for all Gradle-related questions, like, nobody uses maven-publish.
I think I'll remove the squatting on the publish task name and call it a day

According to @ysb33r, who I ask for all Gradle-related questions, like, nobody uses maven-publish.

I think I said something like, no-one I know likes the new maven-publish DSL. Even-though it solves problems of the old maven plugin, it has lost the simplicity of the DSL.

@ysb33r heh, sorry to put words in your mouth. In my research around GitHub I actually couldn't find any real examples of people using it


[bump] client: 2.0.0-internal.8.0.0 => 2.0.0-rc.1.0.0 (exact)

Bumped client from 2.0.0-internal.8.0.0 to 2.0.0-rc.1.0.0.
flub bump client --exact 2.0.0-rc.1.0.0

/azp run Build - client packages


Coordinate system anchoring and error calculation in evaluation

Thank you for the work. I've been reviewing the codebase, specifically looking for the implementation details related to anchoring the coordinate system to the canonical one of the largest pieces in the experiment. Additionally, I'm interested in understanding how errors are calculated on other pieces during the evaluation process.
Could you kindly guide me on where in the codebase these functionalities are implemented? Any pointers or specific files related to these aspects would be greatly appreciated.
Thank you.

After last update, the global transformation estimation is in utils/estimate_transform.py. There is a function for aligning pieces to a given pivot align_to_pivot.
For calculating the metrics, a calc_metric function is in the matching_base_model where you can calculate the metrics based on gt and estimated transformations.

Hi and thank you very much for the nice work and for sharing the code.
According to the paper (Section 3.4)

we anchor the coordinate system to the canonical one of the largest pieces in our experiment and measure the errors over all other pieces of the fractured object

However, from the metrics detailed in your comment above I could see no such a thing as the exclusion of the largest piece from the calculation of the metric. From my understanding of the code, the error is calculated over all the pieces.
Hope you can clarify this!

Since the largest piece is anchored, it will contribute 0 error in rotation and translation, which means the accumulated error only comes from other pieces.

@Nes-tle exactly.
However by averaging over all pieces, zero-error piece is actually contributing to the metrics.
This affect accuracy a lot, especially in puzzle with few pieces. In the extreme case of a 2-piece puzzle, base accuracy will be 50%.
Also, RMSD error is affected a lot, since the zero error piece is accounted for in the average.

@Jiaxin-Lu @Nes-tle I want to clarify that I am not saying that the evaluation is unfair.
However, what is written in the paper my be misleading, since one may think that metrics are calculated by excluding the largest pieace.

@pmorerio Yes. We are taking the largest piece into account. As you can see, the current implementation of global alignment will bring some benefits in PA, but lose optimality in rotation and translation averaging. This project is still far from solving the assembly problem, and I would suggest taking PA as a minor standard.

Well, @Nes-tle @Jiaxin-Lu  thank you very much for the fruitful discussion, that clarifies everything :smiley:


calling builtins.mapAttributes on a loaOf shifts list order

I was experiencing this in the ssh module, but it might be relevant elsewhere too.
Apparently the list is re-sorted alphabetically, which leads to this behaviour:
[ "unnamed-1.1" "unnamed-1.10" "unnamed-1.11" "unnamed-1.12" "unnamed-1.13" "unnamed-1.14" "unnamed-1.15" "unnamed-1.2" "unnamed-1.3" "unnamed-1.4" "unnamed-1.5" "unnamed-1.6" "unnamed-1.7" "unnamed-1.8" "unnamed-1.9" ]

if someone needs a workaround for this:
my current workaround is preprending the list with 9 dummy hosts - I don't care where those get sorted in. but if you have more than 90 hosts this might not be feasible.
{ host = "dummy-1"; }
                { host = "dummy-2"; }
                { host = "dummy-3"; }
                { host = "dummy-4"; }
                { host = "dummy-5"; }
                { host = "dummy-6"; }
                { host = "dummy-7"; }
                { host = "dummy-8"; }
                { host = "dummy-9"; }

Took quite a while but the upstream fix just got in the stable NixOS channel so I'll close this. The workaround should no longer be necessary 🙂

Cool, thanks again :)


Account Dropdown on Sidebar

Currently, when a user opens the sidebar, he can see a small thumbnail of the account avatar and a dropdown, but it needs to be clarified witch account is selected.
The following design adds the account name and address to the current design, making it easier for the user to know what info is there.

This will be handled on a new redesign of the main wallet page.


Function request, export as svg, png, or pdf

When visualizing a tree, exporting an image format would be ideal.

@aglucaci -- The Observable pages should provide the functionality. Do you still want it on phylotree.hyphy.org?

Yes

Implemented SVG export.


It is better to add the ignore unhandled critical extensions flag when use Openssl crypto library

By default any unhandled critical extensions in certificates or (if checked) CRLs result in a fatal error.
But the actual cert may have the customized critical extension.
It is better to add the flag to ignore unhandled critical extensions when the user want to ignore.
https://github.com/DMTF/libspdm/blob/ab6e3436413e23cd2339e7d053a91c7b0ae423ae/os_stub/openssllib/openssl_gen/openssl/x509_vfy.h#L425-L426

From RFC 5280:

The X.509 v3 certificate format also allows communities to define private extensions to carry information unique to those communities.  Each extension in a certificate is designated as either critical or non-critical.  A certificate-using system MUST reject the certificate if it encounters a critical extension it does not recognize or a critical extension that contains information that it cannot process.  A non-critical extension MAY be ignored if it is not recognized, but MUST be processed if it is recognized.

From OpenSSL:

Normally if an unhandled critical extension is present that is not supported by OpenSSL the certificate is rejected (as required by RFC5280).

So for the cryptography libraries that libspdm supports, I think it's fine if this check is on by default, and that it can be disabled explicitly. Note that, while this issue is currently for OpenSSL, presumably the same disablement also applies to MbedTLS. I'll rename the issue.
https://github.com/DMTF/libspdm/blob/ab6e3436413e23cd2339e7d053a91c7b0ae423ae/os_stub/mbedtlslib/include/mbedtls/config.h#L2206-L2213


Speed up matching CSS selectors and other tasks which use elementSiblingIndex()

Matching css selectors can be slow because finding elementSiblingIndex() is relatively slow.
I have created a pull request https://github.com/jhy/jsoup/pull/862 which provides a way to cache the sibling index for all siblings which results in speeding up subsequent calls to elementSiblingIndex(). It would be possible to speed up other calls which effectively want to know the elementSiblingIndex() but do not call that method. I didn't make too many changes I would like to know if such a change to Jsoup would be acceptable or if plans already exist for speeding up CSS selectors.

@jhy um am i going about this the wrong way? I tried to use the google group https://groups.google.com/forum/#!forum/jsoup but my posts are just sent for review and I never see them or here anything back.

Apologies for the late replies on this @LukeButtersFunnelback. You are/were going about it the right way, I just haven't been able to keep up with the project for a while until now. Really appreciate your contribution.


Pagination with AngularJS 1.3

I am having a strange issue where the model that is being used is not being updated.
<pagination ng-if="totalItems > limit" total-items="totalItems" items-per-page="limit" ng-model="currentPage" ng-change="pageChanged()"></pagination>

$scope.currentPage = 1;
$scope.limit = 1;

$scope.pageChanged = function() {
	var start = ($scope.currentPage * $scope.limit) - 1,
		end = start + $scope.limit;
        $scope.newslist = $scope.origList.slice(start, end);
};

after removing the ng-if in the element it worked again.


Bootstrap in agent 3 does not inherit agent configuration on "ssh fingerprint verification"

SSH fingerprint verification (a misnamed feature as explained here: #649) configured at the agent level does not get inherited by the default settings to the new go based bootstrap.
You can currently workaroudn this via setting buildkite-agent bootstrap --ssh-fingerprint-verification=false.
If this is expected behavior I expect to change the expectation ;) Took me a while of head scratching till I finally convinced myself to read the source.

Hmm, I rememeber finding that the ENV var had changed. In the v3 Agent it is BUILDKITE_AUTO_SSH_FINGERPRINT_VERIFICATION, but seems to still be passing in BUILDKITE_SSH_FINGERPRINT_VERIFICATION to the bootstrap. We will get this fixed, thank you for the report.

Closed in #671


FFMPEG ERROR

Description
Newbie here, how to bypass this one
Reproduction Steps
HA logs
Expected behavior
Want to stream via HA
If applicable, add error logs.
-----LOGS-----
2024-05-08 14:08:06.330 ERROR (MainThread) [homeassistant.components.camera] Error while setting up ffmpeg platform for camera
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\HassWP_2024.4.3\python-3.12.3.amd64\Lib\site-packages\homeassistant\helpers\entity_platform.py", line 356, in _async_setup_platform
await asyncio.shield(awaitable)
File "C:\Users\Jordan\Desktop\HassWP_2024.4.3\python-3.12.3.amd64\Lib\site-packages\homeassistant\components\ffmpeg\camera.py", line 47, in async_setup_platform
async_add_entities([FFmpegCamera(hass, config)])
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\HassWP_2024.4.3\python-3.12.3.amd64\Lib\site-packages\homeassistant\components\ffmpeg\camera.py", line 59, in init
self._manager: FFmpegManager = hass.data[DATA_FFMPEG]
~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'ffmpeg'
Device Firmware
latest build
Integration Version
latest version
Using stream component
Yes
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Home Assistant Windows 10 OS
Search for similar issues
Yes
Additional information
No response

Not an integration isssue.

You are probably missing ffmpeg and are running unsupported install method for ha.

How to fix this problem?
Should I need to install the HA os on raspberry pi. As of now I am using HA
on windows 10
On Wed, May 8, 2024, 3:46 PM Juraj Nyíri @.***> wrote:

You are probably missing ffmpeg and are running unsupported install method
for ha.
—
Reply to this email directly, view it on GitHub
https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues/566#issuecomment-2099958751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYNKTKDQRGVIJIXH7E4I7EDZBHJ7DAVCNFSM6AAAAABHMKE4HWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZHE2TQNZVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Using supported installation method will fix it automatically, like the proper install of HA OS.
Or just install ffmpeg, but you need to be able to google and find solutions to your issues if you are using unsupported HA install.


Document printf-style-formatting behaviour of ignoring single-variables

This: https://github.com/astral-sh/ruff/issues/3549#issuecomment-1477242022 should probably be documented here: https://docs.astral.sh/ruff/rules/printf-string-formatting/

Thanks, good call.


Fix tiny typo: andD -> and

Fixed tiny typo to match the next item.

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


Fixed the link to "extra addons" in the plugins README

Fix for issue #646 changed the link in the README to point to https://github.com/impress/impress-extras

Thanks!


How to create configuration property of type Duration

Hi, I was looking for some documentation on how to use java.time.Duration as a configuration property but couldn't find any. I have the following configuration:
@Valid @JsonProperty("operationTimeout")
private final Duration operationTimeout;

And in my YML file I have:
operationTimeout: 20s

but when I try to read this, I get an error:
Incorrect type of value at: requestOptions.operationTimeout; is of type: String, expected: Duration

What is the correct way to specify a Duration in the yml file? Thanks for your help!

Does using a ISO8601 duration format work?
operationTimeout: PT20S

@mattnelson yes! That works, thanks so much.

For more readable durations in your configuration files, you can also use io.dropwizard.util.Duration.

Thanks @joschi, this is perfect.


upgrade tensorflow workload to v2.13

For Bazel
Please follow the README

[ ] add pthread support
[ ] add sgx support

For Cmake (Deprecated)

apply the patch
involve Emscripten toolchain during configration

CC=/usr/lib/llvm-15/bin/clang CXX=/usr/lib/llvm-15/bin/clang++ \
cmake -S ./tensorflow/lite -B tflite_wasm_build \
  -DCMAKE_TOOLCHAIN_FILE=/opt/emsdk/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake \
  -DTFLITE_ENABLE_NNAPI=OFF \
  -DTFLITE_ENABLE_XNNPACK=OFF \
  -DTFLITE_ENABLE_EXTERNAL_DELEGATE=OFF \
  -DCMAKE_VERBOSE_MAKEFILE=On

build

cmake --build tflite_wasm_build --target benchmark_model

Hello @lum1n0us, have you dropped the upgrade of TFlite?


Update TOC for correct URL

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

security-docs/TOC.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add Overview page for Ordinals API

This item adds an Overview page for Ordinals API, similar to the other product Overview pages.

Reach out to @chresko for more info.

https://github.com/hirosystems/ordinals-api/pull/157

https://github.com/hirosystems/docs/pull/415. Pushed docs PR to add to the side bar. Hence marking this as done.


Some Qubino 2-relay ZMNHBD devices (depending on firmware version) do not send instant status reports

Checklist:

[X] I am not using HomeAssistant. Or: a developer has told me to come here.
[X] I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
Some Qubino 2-relay ZMNHBD devices that do not send "instant status" reports to zwavejs2mqtt
when they are  operated manually. They are all firmare version 1.1. However other ones, versioned 1.2 and 5.0 work perfectly. All these devices worked ok in the ancient zwave 1.4.
Forcing "Refresh values" to affected nodes results in correct value updates.
Device information
Which device(s) is/are affected (make/model)?   QUBINO ZMNHBD Flush 2 relay (firmware 1.1)
What are the node IDs?   21, 22, 28, 36, 37, 38, 50, 56
Did you change anything?

[ ] Yes: (please describe)
[X] No

Did this use to work before?

[ ] Don't know, this is a new device
[ ] No, it never worked anywhere
[X] Yes, in: (Zwave 1.4)

How are you using node-zwave-js

[x] zwavejs2mqtt (latest) docker image 2.1.1
[ ] zwavejs2mqtt (dev) docker image
[ ] zwavejs2mqtt Manual Docker build

node-zwave-js branch:
zwavejs2mqtt branch:

[ ] ioBroker.zwave2 adapter
[ ] HomeAssistant version XYZ
[ ] Pkg
[ ] Manual Docker build

node-zwave-js branch:
zwavejs2mqtt branch:

[ ] Manually built (as described in the docs)
[ ] Other:

To Reproduce
Steps to reproduce the behavior:

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

NA
Additional context
Nodes with issue: 21, 22, 28, 36, 37, 38, 50, 56 (Firmware 1.1)
Nodes with no issue: 39 (Firmware 1.2)
Logs include manual switching on, then off for nodes 37 and 39, both endpoints (may be more than once).
Logfile:
zwavejs_1.log
Part of zwave2mqtt.log file for node 37. Switched on then off, both endpoints
Part of zwave2mqtt.log file for node 39. Switched on then off, both endpoints

:( you didn't read the issue template - especially the part where it tells you which logfile to select.

Working in it.... I need to setup a Node.js environment first. May be a couple of days....

Do you know https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/docker_custom_builds ?

No I didn't. Thanks! It has been better -and faster- option, once solved silly issues with a hanging rpi3 and the lack of credentials for the docker build.
Here you are the logs. I operated the two switches in node 037, via HA and pushing the buttons.
zwavejs_1.log

Hmm... I think I was blind earlier. The config file for your device is this one, which sets the compat option preserveRootApplicationCCValueIDs (I got this info from Qubino that it is necessary).
This prevents the value from being mapped to endpoints.
You could ask the Qubino support if there is something you can do to make the device report values for each endpoint.
For me, the remaining question is now: do you see the value for endpoint 0 change in zwavejs2mqtt?

Regarding the last question. Each capture is with one of the endpoints switched on.

I'm looking at 37-37-0-currentValue - my guess this shows if any of the endpoints are on, so you won't see anything in a screenshot. Can you turn off both and see if that value changes?

Yes. I omitted that picture because I thought it was obvious.

Ok so the reporting for the root endpoint works. We won't get further here without Qubino's answer what to do about the single endpoints.
Worst case you'll need an automation that polls both endpoints when the combined channel is updated (not necessarily changed).

I will ask Qubino, although I guess they will offer a firmware upgrade https://support.qubino.com/support/solutions/articles/44001936790-do-qubino-devices-support-ota-can-i-update-the-firmware-ota-, a process that is expected to be slow, long-term and (maybe) expensive.
Is it possible to poll just one device?

It is possible to poll just one value (and the associated ones):
https://zwave-js.github.io/zwavejs2mqtt/#/usage/setup?id=poll-values

As I understand, one can poll just one value for ALL devices of the same type. I had tried this but the z-network becomes laggy. I have also tried automations, as you suggested:

But they do not work as expected, since it only triggers when root value changes, not when it updates, what would. be the desired behavior (HA switch devices created have no attributes). May be I misunderstood your suggestion for the automations.

I don't know how HA operates in this regard - best if you ask in the HA channels for support. You need to be able to react to a value update, even it if is not a change. If that is not possible with HA, that should definitely be added.
zwave-js offers a method to poll a single value ID once and zwavejs2mqtt also offers this API via MQTT AFAIK.

As I understand, one can poll just one value for ALL devices of the same type. I had tried this but the z-network becomes laggy. I have also tried automations, as you suggested:

But they do not work as expected, since it only triggers when root value changes, not when it updates, what would. be the desired behavior (HA switch devices created have no attributes). May be I misunderstood your suggestion for the automations.

You should be able to refresh just one value from an automation.
SERVICE ZWAVE_JS.REFRESH_VALUE
This service will refresh the value(s) for an entity. This service will generate extra traffic on your Z-Wave network and should be used sparingly. Updates from devices on battery may take some time to be received.
Service Data Attribute	Required	Description
entity_id	yes	Entity or list of entities to refresh values for.
refresh_all_values	no	Whether all values should be refreshed. If false, only the primary value will be refreshed. If true, all watched values will be refreshed.
https://www.home-assistant.io/integrations/zwave_js/

You should be able to refresh just one value from an automation, or all of them.
SERVICE ZWAVE_JS.REFRESH_VALUE
refresh_all_values no Whether all values should be refreshed. If false, only the primary value will be refreshed. If true, all watched values will be refreshed.
https://www.home-assistant.io/integrations/zwave_js/
There is a last updated attribute I believe it just doesn't show in the list. If you go to developer tools it does list a last updated time down towards the bottom. Can you access that through a jinja template? It should be triggering on updates anyway, though, if you don't have from/to.
https://community.home-assistant.io/t/how-to-trigger-on-changes-to-last-updated/230354

Thank you for four comment.
May be my post was confusing. The first statement about polling any value for all devices of the same type referred to the zwavejs2mqtt control panel. However, the statement below pointed in the same direction than yours. The problem is that the HA zwave2js integration does not pass any atribute, such as the last_updated, what would make -I hope- the rules using the service  ZWAVE_JS.REFRESH_VALUE. Part of my "developer tools" shows as follows. All the switches shown have been set up by the zwavejs integration: No atribute, except for the state value.

You should be able to refresh just one value from an automation, or all of them.
SERVICE ZWAVE_JS.REFRESH_VALUE
refresh_all_values no Whether all values should be refreshed. If false, only the primary value will be refreshed. If true, all watched values will be refreshed.
https://www.home-assistant.io/integrations/zwave_js/
There is a last updated attribute I believe it just doesn't show in the list. If you go to developer tools it does list a last updated time down towards the bottom. Can you access that through a jinja template? It should be triggering on updates anyway, though, if you don't have from/to.
https://community.home-assistant.io/t/how-to-trigger-on-changes-to-last-updated/230354

Thank you for four comment.
May be my post was confusing. The first statement about polling any value for all devices of the same type referred to the zwavejs2mqtt control panel. However, the statement below pointed in the same direction than yours. The problem is that the HA zwave2js integration does not pass any atribute, such as the last_updated, what would make work -I hope- the rules using the service  ZWAVE_JS.REFRESH_VALUE. Part of my "developer tools" shows as follows. All the switches shown have been set up by the zwavejs integration: No atribute, except for the state value.

@AlCalzone  is right.The integration should pass further information to HA from zwavejs than the raw state value. I will also follow his suggestion.

I have been able to solve the issue enabling MQTT in zwavejs2mqtt and using automations to catch the value updates (wether changing state or not) to endpoint 0., forcing the polling to endpoints 1 and 2. This way:

It seems to work fine (I have to watch performance). Thank you for your help, @AlCalzone. I also forwarded the issue to Qubino support. Waiting for answer....

What Qubino says about the issue follows:

The Flush 2 Relay device is an older device, that doesn't have an endpoint1, which would have the same functionality as the root endpoint. Usually, the same values are reported from the root endpoint and endpoint1, but the Flush 2 Relay has cumulative values on the root endpoint, relay1/channel1 values on endpoint1 and relay2/channel2 values on endpoint2.

The unsolicited reports (state reports, sent from the device automatically, without it being polled), that are sent from the device, depends on the configured Lifeline association;:
i) If an ordinary association is configured, using ASSOCIATION_SET(groupId=1, nodeId=1), the Flush 2 Relay will only send the cumulative values for the root endpoint (W and kWh values) and will not send separate channel values.
ii) if a multi channel lifeline is configured, using MULTI_CHANNEL_ASSOCIATION_SET(groupId=1, multichannelnodeid=1, endpoint=0), the device will send separate channel values, but will not send cumulative (root endpoint) values.

It seems like zwavejs configured an ordinary lifeline for this older version of the device OR configuring the multi channel Lifeline failed, so you'll have to configure the lifeline association manually, by first issuing an ASSOCIATION_SET(groupId=1, nodeId=1) and then sending MULTI_CHANNEL_ASSOCIATION_SET(groupId=1, multichannelnodeid=1, endpoint=0). Since you are using the zwavejs2mqtt, you should have access to the control panel, which should have a section for configuring associations. Another option is to use Silicon Lab's PC Controller, which will enable you to send the same commands. This is shown in the attached gifs (you should follow the PCControllerSettingMCLifeline1). The tool can be downloaded from here.

If the device reported everything in ozw_1.4, we should be able to configure it to report everything also for zwavejs.

I am not sure on what they say about (MULTI_CHANNEL)_ASOCIATION_SET. My devices seemed to be configured to endpoint 1, but changing  --with difficulty-- to endpoint 0 seems not to work.
In any case, the management of associations is difficult with the interface. If I try to delete associations to lifeline, I get the old associations. In addition to that, if I get an association for a node, the same association appears in other nodes that are opened in the interface. I hardly could change endpoint 1 to endpoint 0 in one of my devices.
Is there an issue with association management in the interface?

Can you share a screenshot of the association settings in the interface?

To start fresh and figure out where things go wrong, I suggest the following procedure:

Enable zwave-js logging (if not already)
Remove all associations of that device via the interface
Do a re-interview and share:

a log of that
another screenshot of the associations after the interview
the cache files (like above)

Screenshots for step 1 (zwavejs2mqtt recently restarted).
Lifeline for Node 37:

After that, screenshot for getting lifeline for Node 36, leaving open the data for Node 37. Please, note that its data has changed:

Step 2 along the afternoon....

Hi,
I just want chime in to this discussion as I believe have seen this issue on an other platform (SmartThings) with Qubino, Fibaro and some other multi endpoint devices.
Here is a summary of what was going wrong with a firmware update there, it was written by one of the developers:
https://community.smartthings.com/t/z-wave-issues-with-firmware-update-30-3/192759/123

@enredador Best if you also make a log where you delete the lifeline. Not sure if that's the device messing up or the UI.
@GSzabados zwave-js does not care for the destination endpoint. The problem here is that the reports aren't getting sent at all.

@AlCalzone, sorry for the misunderstanding.
I've looked at the Device Handler which was written for the Qubino 2 Relay for SmartThings. (Eric Maycock, who wrote it, is the CTO of Inovelli)
https://github.com/erocm123/SmartThingsPublic/blob/master/devicetypes/erocm123/qubino-flush-2-relays.src/qubino-flush-2-relays.groovy
If you look at it, it is full of get commands for endpoint 1 and 2. The behaviour must have been known before.

Step 2 along the afternoon....

Here it is finally.

Remove all associations of that device via the interface

Done.  I tried both the red trash icon near the association info, and then the button "remove all"

Do a re-interview and share:
a log of that

zwavejs_1.log - Log for all the process from restart

another screenshot of the associations after the interview

the cache files (like above)

e22379bc.values.jsonl.txt
e22379bc.json.txt

That's during your re-interview, so the multi channel association seems to be set up correctly.
14:30:34.948 CNTRLR « [Node 037] received information for multi channel association group #1:
                      maximum # of nodes:           1
                      currently assigned nodes:
                      currently assigned endpoints: 1:0

Which reports does your device send now, or rather on which endpoints do you receive updates now?

i) If an ordinary association is configured, using ASSOCIATION_SET(groupId=1, nodeId=1), the Flush 2 Relay will only send the cumulative values for the root endpoint (W and kWh values) and will not send separate channel values.
ii) if a multi channel lifeline is configured, using MULTI_CHANNEL_ASSOCIATION_SET(groupId=1, multichannelnodeid=1, endpoint=0), the device will send separate channel values, but will not send cumulative (root endpoint) values.

This could be a problem if it is really required to have both. Currently, zwave-js removes the node association if it needs to set an endpoint association.

Ok. I deleted all the associations of these type of nodes and reinterviewed all of them. They all are associated to 1:0 as desired.
FW 1.1 nodes do not report instant status, as usual, when the zwave2mqtt catching updates rules are disabled.
Power consumption (Watt) reports are got aggregated on (I guess) endpoint 0, BUT energy consumption (kWh) are received in different reports, and also accumulate  (There are at least values, but LED lightning do not update this frequently).
Screenshots for one light, the other and both:

The only FW1.2 node report instant status, and separate power consumption values (endpoints 1, 2) and no aggregated values on endpoint 0 (reports are always 0W). Energy reports are got in endpoints 0 and 1, but due to the big difference I am not sure of their meaning (may be one of the lights and aggregated? separated lights?)

FW 1.1:
With status do you mean switch status (...-1-currentValue and ...-2-currentValue)? Does ...-0-currentValue still get updated?
FW 1.2: Do you get cumulative updates if you add an association to Node 1 (no endpoint)?

FW 1.1: With status do you mean switch status (...-1-currentValue and ...-2-currentValue)? Does ...-0-currentValue still get updated?

Oh! I meant that only 0-currentValue is updated, as before. I think that is shown in the screen capture. If I force refresh values, then 1-currentValue or 2-currentValue is also updated.

FW 1.2: Do you get cumulative updates if you add an association to Node 1 (no endpoint)?

The behavior changes: I get cumulative updates for power (endpoint 0) and separated values for energy for both endpoints !!

In any case, the "forced" association to Node 1 (no endpoint)  is lost as soon as a new node interview is done!

In any case, the "forced" association to Node 1 (no endpoint) is lost as soon as a new node interview is done!

That's zwave-js removing an association it considers wrong. I can think about removing that - is the behavior with both associations what you'd consider correct?

Oh! I meant that only 0-currentValue is updated, as before. I think that is shown in the screen capture.

Hard to see changes in a static image ;) I guess they don't update either if you also add the node association in Firmware 1.1?
In that case, it sounds like it is not behaving as the support said it should.

Hard to see changes in a static image ;) I guess they don't update either if you also add the node association in Firmware 1.1?
In that case, it sounds like it is not behaving as the support said it should.

No, they don't update neither with the lifeline association to Node 1 (No endpoint) nor with association to Node 1 (endpoint 0) in FW 1.1. I think this association group do not accept more than one association.
I agree, the observed behavior is not as support said.

That's zwave-js removing an association it considers wrong. I can think about removing that - is the behavior with both associations what you'd consider correct?

I am not sure which association -to node or to node+endpoint- is correct (regarding W and kWh reports). I think maybe neither is correct at all.  I am not very interested in kWh reports, but I am in report status, that do not work in any case as they should.

Hm :( Guess you'll have to do another round with the support.

Anything new?

Not yet. Qubino support people want to access a computer running the Silabs PCcontroller with this device included to have a look (they say that do not have any module with so old FW). I am still preparing how to, since I do not have any Windows system and I want to test if that program runs under emulation on a Mac. I will be also out for 10 days....
I haven't given it up .....

Hello. I have some news about this.
This morning, some people from Qubino support team have been make some tests directly on my zwave network using the SIlabs PCController. They have report this two texts:

I am not sure whether this is different from what they suggested before or not. I am a little bit dizzy with all these dances with endpoints. The point is that, after connecting the dongle newly to the machine that runs zwavejs2mqtt+Homeassistant, and reinterview the node (it was excluded, and included with the PC Controller) the device reports perfectly!
I have tried to mimic these associations for a different node with no success. But I think that the problem is that the associations are not made.For instance, trying to set the following association:
Node: 36 - Group: Q1 switch binary - Target: NodeID_1 - Endpoint: 1
The log says:

Calling api addAssociations with args: [ 36, 3, [ { nodeId: 1, endpoint: 1 }, [length]: 1 ], [length]: 3 ]
Error while adding associations to 36: The endpoint 1 was not found on node 1!

Instead, If I try:
Node: 36 - Group: Q1 switch binary - Target: NodeID_1 - Endpoint: 0
The log says:

Calling api addAssociations with args: [ 36, 3, [ { nodeId: 1, endpoint: 0 }, [length]: 1 ], [length]: 3 ]
Assocaitions: Adding Node 1 to Group 3 of  Node 36
Success zwave api call addAssociations { success: true, message: 'Success zwave api call', result: undefined }
Calling api getAssociations with args: [ 36, 3, [length]: 2 ]
Success zwave api call getAssociations {
success: true,
message: 'Success zwave api call',
result: [ { nodeId: 0, endpoint: 0 }, [length]: 1 ]

nodeid 0???. The fact is that in the UI "no associations" is shown when requested, but the log shows:

result: [ { nodeId: 0, endpoint: 0 }, [length]: 1 ]

I have also updated my zwavejs2mqtt to docker :latest (7.1.1) and I observe the same behavior.
Am I missing something when working with the associations in zwavejs? May be the multichannel lifeline setup needs something else?

Some pics from PC Controller screen show how the associations were configured:

The endpoint 1 was not found on node 1!

Z-Wave JS checks if the association you're trying to make is valid and doesn't like that you're trying to set an association to endpoint 1. I think it would be okay to omit this check for the controller itself.

No, they didn't. Just that this is a very old firmware.
BUT, I have a FW1.2 that reports status with no issues. So may be you can act only in FW1.1 or older ones.

Associations to Node 1 with a different endpoint than 1 are now possible with #2347.
As for setting up the associations, I'll have to revisit this after #2286 is solved.

Hello. I just updated to zwavejs 7.2.4 / zwavejs2mqtt 3.5.0. Associations can be configured now to get all unsolicited reports for old Qubino 2 relay devices, including independent power consumption reports for endpoints.
Very nice job, @AlCalzone. Thank you very much.

Huh, I didn't release the association changes yet 👀

Then, how did I?

Ahh, right. That part was released

Hi!
I’ve got similar issues with old Qubino Flush 1 Relays ZMNHAA (Z-Wave chip firmware versions 1.12, Z-Wave protocol version 3.28). I’m not receiving any unsolicited updates e.g. energy reports or status updates when manually operating a switch.
Currently running zwavejs2mqtt version 5.10.1 (Z-wave JS 8.6.1).
I migrated from Fibaro Home Center 2 (where all Qubino devices worked just fine) to running Home Assistant on a NUC with an AEON Labs Gen5 USB Z‐Stick Controller.
How should I proceed, should I open a separate issue? But I’m not sure which logs you want and how to get them...

How should I proceed, should I open a separate issue? But I’m not sure which logs you want and how to get them...

Yes please. The issue template will tell you what's required and where to find it

Maybe not the correct place to add a comment, but i'm having the same issue here where the manual light switch presses are not sent towards the controller.
I've been struggling quite a bit but not been able to add the correct associations, and i was wondering if someone can help.
I have two of these Relay's and it seems that some part of it did work on my side, when target endpoint was set to 1. But for testing i removed these accociations, to see this was making it work, but i'm not able to re-add them again, as i can only select "no endpoint" or "endpoint 0" in the drop down. Is there an easy way to also be able to add "1" as target endpoint?
I'm running:
zwave-js-ui: 8.5.1.ad42de0
zwave-js: 10.3.1
home id:<PHONE_NUMBER>
home hex: 0xed89557b
firmware of both my relay's is FW1.1

It might help you, but I struggled with a single relay module on v1.1.
And it requires to set the Endpoints I2 Notification Type and Event and Endpoints I3 Notification Type and Event to Home Security (default). It is under Configuration.
If those were set to Disabled  it just did not report the physical switch changes.

Note that you need to exclude and re-include Qubino devices after changing the endpoint configuration.

It might help you, but I struggled with a single relay module on v1.1.
And it requires to set the Endpoints I2 Notification Type and Event and Endpoints I3 Notification Type and Event to Home Security (default). It is under Configuration. If those were set to Disabled it just did not report the physical switch changes.

Thanks for the remark, but these properties are not available for the 2 replay versions. I did check my other 2 single qubino modules and they both have this set to disabled, but i have never had a problem with those. They always report manual switch changes correctly.

I managed to get it working again using some chrome hacking aswell!
As the UI does not allow me to set target endpoint to "1", i changed some chrome element settings to disable readonly on the drop down for setting the target endpoint and managed to set up them with "1".

Now it looks like this and it's working as expected. For me it's not needed to have power consumption and i'm only interested in push button status update.


TransactionId and OrderId

How can we correlate the orderId/TransactionId in this report to the Subscription(https://docs.microsoft.com/en-gb/windows/uwp/monetize/get-subscriptions-for-a-user) fetched for a user which has an "id" field(subscription id). Secondly is there an API to download this payout summary on a server? We basically want to associate price info with subscriptions

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

ID: 65a40199-aaff-a750-b2df-cc8533606f0a
Version Independent ID: 76160f31-f715-009a-e73e-202f8ed27006
Content: Payout summary - Windows UWP applications
Content Source: windows-apps-src/publish/payout-summary.md
Product: uwp
Technology: publish
GitHub Login: @hickeys
Microsoft Alias: hickeys

Thanks for reaching out with your feedback. Issues opened on the docs GitHub are meant for documentation feedback, and unfortunately we cannot provide technical support. For community assistance with development questions I recommend that you ask on our forums or StackOverflow. For other support options, check out the developer support page. If you get assistance through these other resources and believe a documentation change is required, please come back and let us know.
Thanks,
Shawn

Hello, I have a question in my partner center, reach the threshold and only raw data for a year, how do I process it?


Utilities: Introduce an option to generate more display utility

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
For example, I want to display a div as flex only when it is sm or less than sm and not change its name at other times (that is, it is defaulted to block). The current method is to add d-flex and d-md-block to it.
I hope that the above effect can be achieved by adding only one class, that is, adding d-sm-max-flex
Similarly, there are also people who want to add classes such as d-sm-lg-between as helpers.
I believe I only need to modify mixins/_utilities.scss to achieve it, but I don't know where to start. The code inside is a bit complicated for me. Please give me some guidance. Thank you.
Motivation and context
I think some users have also encountered this problem. Although this will increase the size of scss, I think it can be an option for users to decide for themselves.

Hey there,
First of all, we don't recommand to introduce classes that could be mimic in another way and as you said, it's quite easy to mimic this behavior atm. Furthermore, we try as much as possible to have a mobile first approach.
Since we don't remove unused CSS, we try to limit the number of classes we introduce.
In a second time, I'd consider to introduce those classes manually.
That said, you don't need to change anything in our mixin. Here is a two step process to get what you need.
I just tried this (naming might be reworked and code might be optimized):
Inside scss/utilities/_api.scss
@each $breakpoint1 in map-keys($grid-breakpoints) {
  @each $breakpoint2 in map-keys($grid-breakpoints) {
    $i1: index(map-keys($grid-breakpoints), $breakpoint1);
    $i2: index(map-keys($grid-breakpoints), $breakpoint2);

    @if $i1 < $i2 {
      @include media-breakpoint-between($breakpoint1, $breakpoint2) {
        $infix: #{breakpoint-infix($breakpoint1, $grid-breakpoints) + breakpoint-infix($breakpoint2, $grid-breakpoints) + "-between"};

        // Loop over each utility property
        @each $key, $utility in $utilities {
          @if type-of($utility) == "map" and (map-get($utility, between-responsive) or $infix == "") {
            @include generate-utility($utility, $infix);
          }
        }
      }
    }
  }
}

Inside scss/_utilities.scss
    "display": (
      responsive: true,
      between-responsive: true, // Only new line
      print: true,
      property: display,
      class: d,
      values: inline inline-block block grid inline-grid table table-row table-cell flex inline-flex none
    ),

And here are the results (only few)
@media (max-width: 479.98px) {
  .d-sm-between-inline {
    display: inline !important;
  }
  .d-sm-between-inline-block {
    display: inline-block !important;
  }
  ...
}
@media (max-width: 767.98px) {
  .d-md-between-inline {
    display: inline !important;
  }
  .d-md-between-inline-block {
    display: inline-block !important;
  }
  ...
}
...
@media (max-width: 1439.98px) {
  .d-xxl-between-inline {
    display: inline !important;
  }
  .d-xxl-between-inline-block {
    display: inline-block !important;
  }
  ...
}
@media (min-width: 480px) and (max-width: 767.98px) {
  .d-sm-md-between-inline {
    display: inline !important;
  }
  .d-sm-md-between-inline-block {
    display: inline-block !important;
  }
  ...
}
...
@media (min-width: 1280px) and (max-width: 1439.98px) {
  .d-xl-xxl-between-inline {
    display: inline !important;
  }
  .d-xl-xxl-between-inline-block {
    display: inline-block !important;
  }
  ...
}

This code generates .75kB of CSS.
Once more, prefer using another approach and if you use this, please make sure to clean all unused CSS with any tool like PurgeCSS.


JsonDeserializationFailed on negative numbers

Describe the bug
Passing REQ event that contains negative numbers results in error
To Reproduce
Send client message:
[
    "REQ",
    "some_id",
    {
        "authors": [
            "3235036bd0957dfb27ccda02d452d7c763be40c91a1ac082ba6983b25238388y"
        ],
        "kinds": [
            0,
            3
        ],
        "limit": 200000,
        "since": -50123406
    }
]

Expected behavior
Parsed ClientMessage::Req structure
Build environment

Library: nostr
Tag/commit: v0.18.1, v0.19
OS+version: macOS 13.2.1
Rust/Cargo version: v1.66.0

Additional context
nostr_console sends negative values for timestamps

A negative unix timestamp means a date before 1970/01/01, so I think that the bug is on their side.
However, I'll change timestamp type from u64 to i64 to avoid deserialization issue.


Miscellaneous E2 player additions

Additions:

number entity:accountID() - returns the player's account ID.
number entity:userID() - returns the player's user ID. This is different from entity index.
entity player(index) - returns a player entity from the user ID.
array teamMembers(index) - returns an array with the members of a team.
number teamMemberCount(index) - returns the number of players on a team.

Changes:

Deprecated number teamPlayers(index) (misleading, should be replaced by teamMembers)
Simplified some function returns
Added exceptions to certain functions where they seemed appropriate
Small E2 Description change for consistency

Removals:

Removed check for Player.LocalEyeAngles() existing
Removed unused local variables

Let me know if the lints are okay. Didn't know if anyone wanted to keep them around for future reference.
Test code
Fixes #2660

Don't leave commented code; just deleted it

Think of all the keystrokes that guy in 15 years will save.


feat: Improve the cards in Authors section

Description
UI changes:

It would be better if we could make the cards in the Author section horizontal.
This would make the UI more appealing.

Would like to take this issue under Hacktoberfest2023 🚀 @oyepriyansh
Screenshots

Ready to Work?

[X] I want to work on this issue

assigned to you.


Remove "unspecified" entities in favor of partial-evaluation unknowns

Category
Internal refactors/changes
Describe the feature you'd like to request
Cedar's API allows you to leave the principal, action, or resource of a request unspecified, indicating that the principal, action, or resource "shouldn't matter" for any policy evaluation.  The semantics of this are somewhat complicated.  WLOG let's consider the principal case.  If the principal is unspecified, but some policy actually checks whether the principal is == some UID (or expression that evaluates to a UID), the == is false -- unspecified entities are defined to not be equal to any entity in the hierarchy.  Likewise for in -- unspecified entities are defined to not be in any entity in the hierarchy.  But if a policy tries to access an attribute of principal and principal is unspecified, this is reported as an error (EvaluationError::UnspecifiedEntityAccess) because the caller who does not specify a principal, is implicitly guaranteeing that principal does not matter to the authorization outcome (e.g., because no policies check principal).
Cedar has a separate feature called partial evaluation, which allows partially evaluating a policy or request in the presence of unknowns.  Partial evaluation may return a "residual", that is, an expression involving the input unknowns, if it cannot determine a fully concrete answer from the inputs that were actually concretely provided.
The semantics of unspecified entities are complicated, not always intuitive, and have to be special-cased frequently in the validator.  Furthermore, the distinction between unspecified entities and partial-evaluation unknowns is subtle and confusing, and it feels bad to have to handle both "unspecified" and "unknown" separately.
We propose replacing unspecified entities with partial-evaluation unknowns, which have a (arguably) more intuitive semantics.  This replacement is safe because of the implicit contract the is_authorized() caller is making -- that the principal (or whichever request element is omitted) does not matter to the authorization outcome.  This issue proposes that if the caller does not specify principal, then we use partial-evaluation with principal unknown, and if the resulting answer is not-concrete -- that is, if we get a residual involving principal -- then we return an error akin to the existing UnspecifiedEntityAccess, because the caller "promised" that the principal would not matter, but actually it did.  This semantics is technically slightly different than the existing semantics for unspecified entities (which, e.g., allows == on an unspecified entity, returning false), but I claim that this partial-evaluation semantics is "more correct" and is what the unspecified entity semantics arguably should have been in the first place.  At any rate, I think it's easy to explain the new semantics to callers based on the implicit-contract described above.
It's unclear to me whether the slight change in semantics warrants calling this a breaking change, or whether this can be considered a purely internal refactor that will just result in slightly different error messages in some cases.
Describe alternatives you've considered
None
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

Note: design may change based on work on #209. Revisit once we start work on that issue.


feat: fixing next-css for webpack 5

Beyond the repo be way out of date with what's on NPM. You're using a really old version of mini-css.
This PR works fine with webpack 4 but also enables css processing in webpack 5

Hey! We're deprecating this repository hence why this PR hasn't been merged. I just updated the readme. The built-in CSS support is fully compatible with webpack 5 and being used in production.


Azure Powershell task gets INPUT_SCRIPTARGUMENTS wrong in log, if one is an azure portal URL

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzurePowershell
Environment

Server - Azure Pipelines or TFS on-premises?

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

tribalgroup, EdgePlatform, pipeline 1705

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name: windows-latest

Issue Description
When parameters are passed into a script run by the AzurePowershell task running in debug mode, these parameters are logged as INPUT_SCRIPTARGUMENTS. This works fine normally, but if one of the parameters contains an azure portal URL then the logging goes wrong:

one or more of the parameters goes missing entirely
part of the azure portal URL is not printed; it is replaced by asterisks *** as if the value were a secret (which it is not)

Task logs
Sample task for reproducing the problem:
  - task: AzurePowerShell@5
    displayName: 'Reproducing Script Parameter Problem'
    inputs:
      azureSubscription: redacted
      scriptType: inlineScript
      ScriptArguments: >
        -parameterA "https://url-parameter-A.example.com"
        -parameterB "https://url-parameter-B.example.com"
        -parameterC<EMAIL_ADDRESS>        -parameterD "https://url-parameter-D.example.com"
      inline: |
        Write-Host "If this were a separate script with params, it would get the correct values for all 4 parameters, I assure you"
        # param ($parameterA, $parameterB, $parameterC, $parameterD)
        # Write-Host "parameterA is: $parameterA"
        # Write-Host "parameterB is: $parameterB"
        # Write-Host "parameterC is: $parameterC"
        # Write-Host "parameterD is: $parameterD"
      azurePowerShellVersion: LatestVersion
      FailOnStandardError: true

(of course normally ScriptArguments would be used with a powershell script file, not an inline script; however to make it easy for you to reproduce I have used an inline script task here)

##[debug]INPUT_SCRIPTARGUMENTS: '-parameterA "https://url-parameter-A.example.com" -parameterB<EMAIL_ADDRESS>-parameterD "https://url-parameter-D.example.com"'

Note the mistakes in that output:

the value for parameterB is missing
the name for parameterC is missing
the value for parameterC is not correct; the part at the start "https://portal.azure.com/#@" is mostly missing; the forward-slashes, the domain, and the hash character # are all replaced with a set of three asterisks.

@vincebowdren Could you please confirm whether the issue is only present on writing logs and not on task ?

@vincebowdren Could you please confirm whether the issue is only present on writing logs and not on task ?

Yes, that's right. The task receives and processes the parameters correctly, with the correct values.
It's only the logging which goes wrong.


Add Euler angles to the IMU

change of the Operating Mode to enabele the IMU tu provide euler angles and save these

noticed a mistake in the code while testing, working on a fix


fixed copying to clipboard

Thanks @yoaddb for fixing https://github.com/PalashBansal/Collision/issues/26


Use with in examples, remove close in json()

Update the examples to use with request.method as response: and removed the close in the Response.json() as it doesn't match CPython
Tested the wifi standard and advanced and the rocketlive in advanced
fixes #186

Wow, thank you.  Saved me from all these changes. 🙏


ChatGPT display is cropped in windows 11

Image cropped in windows 11

Same here, it's a bit cropped

Maybe devs can add option to drag the window?

I have the same problem

Still met this (2023-05-03), seems that we might solve it by ourselves...
Then no need to open a new issue for the following:
As the prompts get longer than the original width, viewing the entire conversation would become cumbersome.
You could see this from the position of "bbbb" strings. I have to move mouse cursor in the prompt window to see the whole contents. And when I tried to change the window size, the windows closed directly.

+1

+1, I have to add items to the system tray to move the screen over and not get cropped


glint integration

it will be cool if we able to add glint here and fix found typings issues

linking some issues: https://github.com/typed-ember/glint/issues/519


chore(scripts): setup auto release

@jcarbo @layershifter Hey, this is pretty important:
This PR  adds a script to automatically release commits on the master branch.  Version bumps are determined by the commit message type (ie chore, feat, etc).  This accounts for pre v1 bumps vs v1 bumps as promised in our README.md.
Before merging PRs, the titles must follow our commit guidelines.  This is on me so I'll work to ensure they are correct.
I've added breaking(scope): message as a type to signify breaking changes. All PRs must follow this convention moving forward.
If anything goes wrong, the script will fail and CI will not release.

Sounds good 👍


Document how next/router works

Feature request
Is your feature request related to a problem? Please describe.
There's quite a bit of confusion on how Next.js handles routing as is slightly different from most routing frameworks out there. The reason for this is that Next.js by design has a constraint that we won't ship a routes manifest of every possible route in the application.
Describe the solution you'd like
I've written a pretty complete comment about how <Link> works with custom parameters etc. It can be found here: https://github.com/zeit/next.js/issues/2833#issuecomment-414919347
Most of that comment can be used in the docs.

@paulina-grunwald definitely! You can add the docs in the readme in this repository and we automatically sync them to the docs on the website etc.

I would love to contribute to this as well!


[BUG] Playwright executions in jenkins throws Internal error

Playwright executions in jenkins throws Internal error:

Playwright Version: [1.18.0]
Operating System: [Jenkins server in Linux]
Node.js version: [Java 11]
Browser: [Chromium]
Extra: [The execution is fine in local machines. But it is failing only in jenkins execution]

Code Snippet
page.locator(".xn-arclabel-value-text").isVisible(new Locator.IsVisibleOptions().setTimeout(60000)

isVisible throws Internal error only in jenkins
com.microsoft.playwright.PlaywrightException: Internal error
at com.microsoft.playwright.impl.Utils.convertType(Utils.java:55)
at com.microsoft.playwright.impl.LocatorImpl.isVisible(LocatorImpl.java:266)

What is the full stack trace including the error message?

Hi @yury-s This is the full stack trace we have
com.microsoft.playwright.PlaywrightException: Internal error
at com.microsoft.playwright.impl.Utils.convertType(Utils.java:55)
at com.microsoft.playwright.impl.LocatorImpl.isEnabled(LocatorImpl.java:250)
at com.sample.test.AbstractChartsCommon.waitForEnabledInChartContext(AbstractChartsCommon.java:194)

There should be  caused by below that which may contain some useful information, otherwise it's hard to tell what's going on there, probably some reflection calls are not working as intended.

@yury-s We can close this issue. Its already been discussed in https://servicenow.cloud.mattermost.com/main/pl/n9pemzggz3gum8orfz3n3mr78o
https://bytemeta.vip/repo/microsoft/playwright-java/issues/802


Update chip tool Darwin to use mRequest

Problem
chip-tool-darwin needs to be updated to use mRequest for CLI parameters and then converted to objective-c objects.

Fixes #18287

Change overview

Updates chip-tool-darwin command zap file to use mRequest as CLI params
Updates chip-tool-darwin to parse mRequest and convert to objective object for all params.

Testing

Generated code
compiled code
Tested complex command
Tested basic command

Fast-tracking Darwin-only test-only change.


Can't get shaka player to fetch more then the first chunk on live stream

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
2.5.12
Please ask your question
Hi,
I'm trying to create a live stream of mpeg-dash with ffmpeg(version 3.4) and shaka-player
I'm streaming the frames to ffmpeg with python through pipe and this is the ffmpeg command I use:
ffmpeg -re -f rawvideo -pix_fmt bgr24 -video_size 640x360 -i - -vcodec libx264 -preset ultrafast -tune zerolatency -f dash -window_size 10 -use_template 1 -use_timeline 0 -live 1 /srv/http/dash/stream.mpd
Currently I'm using nginx as a server and I've created a simple index.html with the example from the Basic Usage section in the docs.
The problem I have with this is that I couldn't get it to load and play more then the first chunk. (checked with dev-tools in chrome in the network tab, it only asks for the mpd file, init-stream.m4s and chunk-stream0-00001.m4s)
I've tried to play with the configuration of shaka and the parameters of ffmpeg but could get it to work.
I've also tried using shaka player 3.0.0 and 3.0.1 but both of them don't request any chunk (with no errors in console)
The mpd file ffmpeg created while streaming looks like this:

<?xml version="1.0" encoding="utf-8"?> <MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="urn:mpeg:DASH:schema:MPD:2011 http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG-DASH_schema_files/DASH-MPD.xsd" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="dynamic" minimumUpdatePeriod="PT500S" suggestedPresentationDelay="PT10S" availabilityStartTime="2020-06-30T05:09:49Z" publishTime="2020-06-30T05:19:39Z" timeShiftBufferDepth="PT1M40.0S" minBufferTime="PT20.0S"> <ProgramInformation> </ProgramInformation> <UTCTiming schemeIdUri="urn:mpeg:dash:utc:http-xsdate:2014" value="https://time.akamai.com/?iso"/> <Period id="0" start="PT0.0S"> <AdaptationSet id="0" contentType="video" segmentAlignment="true" bitstreamSwitching="true" frameRate="25/1"> <Representation id="0" mimeType="video/mp4" codecs="avc1.f4001e" bandwidth="57572937" width="640" height="360" frameRate="25/1"> <SegmentTemplate timescale="1000000" duration="10000000" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startNumber="1"> </SegmentTemplate> </Representation> </AdaptationSet> </Period> </MPD>

Am I missing something with the way I use ffmpeg or shaka-player?
Thanks in advance!

Hello @OF1re ,
Would you please validate your content via https://conformance.dashif.org/ ?
If the content is valid, would you please send us the URL (on Github or email<EMAIL_ADDRESS>), so that we can reproduce the issue?
Thanks!

Hi @michellezhuogg ,
Sorry for the delay, sadly the site for the validation didn't work for some time due to disk space issues and there are some open github issues about it (https://github.com/Dash-Industry-Forum/DASH-IF-Conformance/issues/515 and https://github.com/Dash-Industry-Forum/DASH-IF-Conformance/issues/516).
It works now and I run the validator with the additional tests of 'Segment Validation'  and 'DASH-IF' tests and I get no warning or errors on the manifest file.
Here are the full steps I've done:

My machine is Ubuntu 14.04.5 LTS, I'm using python 3.6.5 and ffmpeg 4.3 and nginx 1.4.6 (i guess any other server would work)
I've created a simple http server with nginx at /srv/http/dash/
I've created a simple python script which read frames from a stream, manipulate the frame and sends the new frame to ffmpeg.
Here is a close enough code to what I do without any manipulation of the frame.

import numpy as np
import sys
import cv2
import subprocess as sp
import shlex

command = "ffmpeg -re -f rawvideo -pix_fmt bgr24 -video_size 640x360 -i - -vcodec libx264 -preset \
ultrafast -tune zerolatency -f dash -window_size 10 -use_template 1 -use_timeline 0 -live 1 -utc_timing_url https://time.akamai.com/?iso \
-minimum_update_period 1 -time_shift_buffer_depth 10 /srv/http/dash/stream.mpd"
command = shlex.split(command)

stream_path = '/home/user/dash/example.mp4'

def resize_frame(frame, size):
    return cv2.resize(frame, size, interpolation=cv2.INTER_CUBIC)

def process_frame(frame):
    return frame

def main():
    proc = sp.Popen(command, stdin=sp.PIPE,shell=False)

    while True:
        cap = cv2.VideoCapture(stream_path)
        while(cap.isOpened()):
            ret, frame = cap.read()
            if ret:
                new_frame = process_frame(frame)
                new_frame = resize_frame(new_frame, (640, 360))
                proc.stdin.write(new_frame.tostring())
            else:
                break

if __name__ == "__main__":
    main()

Change 'stream_path' value to a path to any media file you have on your machine

This is my index file at /srv/http/dash/index.html

<!DOCTYPE html>
<html>
	<head>
		<!-- Shaka Player compiled library: -->
		<script src="https://cdnjs.cloudflare.com/ajax/libs/shaka-player/2.5.12/shaka-player.compiled.js"></script>
		<script>
			var manifestUri = 'stream.mpd';

			function initApp() {
				// Install built-in polyfills to patch browser incompatibilities.
				shaka.polyfill.installAll();
				// Check to see if the browser supports the basic APIs Shaka needs.
				if (shaka.Player.isBrowserSupported()) {
				// Everything looks good!
					initPlayer();
				} else {
				// This browser does not have the minimum set of APIs we need.
					console.error('Browser not supported!');
				}
			}

			function initPlayer() {
				// Create a Player instance.
				var video = document.getElementById('video');
				var player = new shaka.Player(video);
				// Attach player to the window to make it easy to access in the JS console.
				window.player = player;
				// Listen for error events.
				player.addEventListener('error', onErrorEvent);
				// Try to load a manifest.
				// This is an asynchronous process.
				player.load(manifestUri).then(function() {
					// This runs if the asynchronous load is successful.
					console.log('The video has now been loaded!');
				}).catch(onError);  // onError is executed if the asynchronous load fails.
			}

			function onErrorEvent(event) {
				// Extract the shaka.util.Error object from the event.
				onError(event.detail);
			}

			function onError(error) {
				// Log the error.
				console.error('Error code', error.code, 'object', error);
			}

			document.addEventListener('DOMContentLoaded', initApp);
		</script>
		<style>
			video {
				width: 640px;
				height: 480px;
			}
		</style>
	</head>
	<body>
	<video id="video" width="640" controls autoplay></video>
	<div>
	</div>

	</body>
</html>

Run the python file and go to the index.html in chrome, you are supposed to get the same results I had, only the first chunk is being loaded and after a while when ffmpeg deletes old chunks it not loading anything when you refresh. (if you'll change player to the latest version, even the first chunk won't be loaded)

Whenever you kill the python process you'll see that you are now able to play the stream (ffmpeg edits the manifest from dynamic to static) but you couldn't play more than the first chunk when it's live streaming. (I've run the validator for both the dynamic and static manifests and they both pass with no errors or warning)

Thanks!

Hi, I've managed to get my intended behavior by adding the flag '-single_file 1' to the ffmpeg command.
I've also changed version to 3.0.1 and it works there too.
I'm not really sure if mpeg-dash protocol wanted live streams to be presented as single file or not, so I don't know if it's cosidered a bug or not.
Also, 3.0.1 and 2.5.12 behave differently in live streaming with the current example I gave but with the flag 'single_file' for ffmpeg.
When looking at the network tab in chrome devtools, 2.5.12 asks the server only for the needed chunks and the status code of the mp4 request is always 206(Partial Content).
In 3.0.1 it seems to do that while asking for the full mp4 file at the same time, which means there is a lot of wasted traffic when using version 3.0.1.

If this is still an issue for you, please post a playable manifest URL.  Just using the manifest text or a command-line isn't enough for us to debug this; we'd need to see the whole content to be able to debug this.  You can send it privately to<EMAIL_ADDRESS>if you prefer.


Toggle Button added

What is the change?
Added toggle button.
Related issue?
closes: #292
How was it tested?
Tested on VS code.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x] I'm HSOC22 contributor.
[x] I have commented my code, particularly in hard-to-understand areas.

GIF/video of the working of component you created:
https://user-images.githubusercontent.com/98695632/182649670-9c9d6d54-12ca-4947-af3c-d81cc0f366dc.mp4

Add your component to the general readme

Already added mam

No you havent

No you havent

But it's visible from my side.

You haven't committed it ig

You haven't committed it ig

Done


Vignesh/stable diffusion ttnn basic transformer block fix

This PR contains the fix for low PCC issue in BasicTransformerBlock. For all test cases we are getting PCC >0.98.

Passing CI:
[post-commit] Run all post-commit workflows  : Link


Add an option to disable default mappings

This PR add an option mappings_enabled to setup section.
This is needed for users who want to map the keys themselves.
The basic behavior does not change due to the fact that the setting is enabled by default.
Also, I've added a configuration for stylua, with defaults appropriate for project c:

Thanks for your PR.


Allow potentially unused import

Replaces #2860

@Dirbaio I saw your "?" mark in the channel, just to clarify - when I had vendored a fork of Embassy, I saw
warning: the item `AtomicWaker` is imported redundantly
 --> vendor/embassy/embassy-stm32/src/usart/buffered.rs:5:5
  |
5 | use embassy_sync::waitqueue::AtomicWaker;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6 |
7 | use super::*;
  |     -------- the item `AtomicWaker` is already imported here
  |
  = note: `#[warn(unused_imports)]` on by default

but I also saw once CI ran that tests would import this separately without a dependency on super::* - so it's needed.
This is just to silence the above warning.

under which condition is it unused? afaict it's used unconditionally in State.
If it's redundant due to the use super::*; maybe we should remove that instead, replacing it with use super::{list, of, things};

done in #2872

under which condition is it unused? afaict it's used unconditionally in State.
If it's redundant due to the use super::*; maybe we should remove that instead, replacing it with use super::{list, of, things};

Thanks for the suggestion!!


Failed job, incorrectly updated JIRA tickets with passed test results.

Failed job, incorrectly updated JIRA tickets with passed test results.
The following is a test that fails on pod creation, and doesn't run the set of tests:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-knative-serverless-operator-main-ocp4.15-lp-interop-operator-e2e-interop-aws-ocp415/1759589706720350208/artifacts/operator-e2e-interop-aws-ocp415/firewatch-report-issues/build-log.txt
Prow correctly marks the job as failed. However, firewatch incorrectly reports this job as a success (https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-knative-serverless-operator-main-ocp4.15-lp-interop-operator-e2e-interop-aws-ocp415/1759589706720350208/artifacts/operator-e2e-interop-aws-ocp415/firewatch-report-issues/build-log.txt) updating Jira tickets with passing job notifications and job labels to other linked Jira tickets.

After some investigation, I have found the issue... It seems like the pod that failed operator-e2e didn't come up, but the finished.json file was not updated with the failure until after the firewatch execution occurred. This seems to be the way OpenShift CI or Prow operates. Unfortunately, in its current state I'm not sure this sort of error can be caught by firewatch, and it is hard to test this as it is an edge case. It seems the order of operation here follows something like this:

Container fails to come up
Prow writes the finished.json file as a success in the operator-e2e step
Prow starts the "post" steps which contains firewatch-report-issues (ref that executes firewatch)
Prow updates the finished.json file to reflect a failure after firewatch has already run

firewatch executed and finished at 16:56:32

operator-e2e files (finished.json) updated at 17:22:23

With the files updated, I can run firewatch and create the correct bug in stage: https://issues.stage.redhat.com/browse/LPTOCPCI-1145
My current thoughts on this are - I don't think we can resolve this without running firewatch as a service outside of OpenShift CI. Would appreciate some ideas to resolve this behavior.

Bug filed against DPTP, adding for reference: https://issues.redhat.com/browse/DPTP-3902


Replication Network Traffic

Does the replication network traffic travel over the internet or does it use Azure's internal networks?

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

ID: 2476aace-c2ac-4084-93d5-8bd4edbc0ea0
Version Independent ID: fa098bb4-5c9e-0f58-cfc7-5d40eb1ce89b
Content: Failover groups and active geo-replication - Azure SQL Database
Content Source: articles/sql-database/sql-database-geo-replication-overview.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

@kringen We are checking and will get back to you soon.

@kringen In the case of SQL Server Always On replication, the replication traffic travels across the Microsoft backbone network. The following reference architecture indicates SQL Server Always On functionality being synched via the Microsoft backbone: Run Windows VMs in multiple regions for high availability.
Inaddition, any Azure VNet that is peered with a VNet from another Azure region, the traffic is also across the Microsoft backbone network. Virtual network peering
Please let me know if you have additional questions, or require additional information.
Regards,
Mike


TAC meeting notes 2020-07-29

TAC meeting notes 2020-07-29
Signed-off-by: Jean-Francois Panisset<EMAIL_ADDRESS>

Thanks JF!


iOS Flutter 2.10.3 got crash because of EXC_BAD_ACCESS KERN_INVALID_ADDRESS

Steps to Reproduce

100% of the users crashed when the app is in foreground.
75% of the users crashed on iOS 15. 25% of the users crashed on iOS 14.
The crash got reported to Firebase console.
I haven't found a way to reproduce it.

Expected results:
Actual results:
Crashed: DartWorker
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000031
Crashed: DartWorker
0  Runner                         0x4be5c signal_handler_callback + 221 (PLCrashReporter.m:221)
1  Runner                         0x483ec internal_callback_iterator(int, __siginfo*, __darwin_ucontext*, void*) + 1023 (atomic:1023)
2  Runner                         0x48340 plcrash_signal_handler + 201 (PLCrashSignalHandler.mm:201)
3  Runner                         0x2afc74 SEASignalHandler + 111 (SEAExceptionManager.m:111)
4  libsystem_platform.dylib       0x6d90 _sigtramp + 52
5  libsystem_pthread.dylib        0x99e8 pthread_kill + 212
6  libsystem_c.dylib              0x738f4 abort + 100
7  libsystem_malloc.dylib         0x1d030 _malloc_put + 554
8  libsystem_malloc.dylib         0x1d2a4 malloc_zone_error + 100
9  libsystem_malloc.dylib         0xbfcc free_list_checksum_botch + 36
10 libsystem_malloc.dylib         0x93fc small_free_list_remove_ptr_no_clear + 1228
11 libsystem_malloc.dylib         0xa244 free_small + 592
12 Flutter                        0x4c4708 (missing UUID be105c8b7c053a8ba51f83e291732357)
13 Flutter                        0x615c40 (missing UUID be105c8b7c053a8ba51f83e291732357)
14 Flutter                        0x6170a0 (missing UUID be105c8b7c053a8ba51f83e291732357)
15 Flutter                        0x6175ac (missing UUID be105c8b7c053a8ba51f83e291732357)
16 Flutter                        0x60d76c (missing UUID be105c8b7c053a8ba51f83e291732357)
17 Flutter                        0x5c5afc (missing UUID be105c8b7c053a8ba51f83e291732357)
18 libsystem_pthread.dylib        0x8c9c _pthread_start + 288
19 libsystem_pthread.dylib        0xd880 thread_start + 8

Code sample

Logs

Crashed: DartWorker
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000031
Crashed: DartWorker
0  Runner                         0x4be5c signal_handler_callback + 221 (PLCrashReporter.m:221)
1  Runner                         0x483ec internal_callback_iterator(int, __siginfo*, __darwin_ucontext*, void*) + 1023 (atomic:1023)
2  Runner                         0x48340 plcrash_signal_handler + 201 (PLCrashSignalHandler.mm:201)
3  Runner                         0x2afc74 SEASignalHandler + 111 (SEAExceptionManager.m:111)
4  libsystem_platform.dylib       0x6d90 _sigtramp + 52
5  libsystem_pthread.dylib        0x99e8 pthread_kill + 212
6  libsystem_c.dylib              0x738f4 abort + 100
7  libsystem_malloc.dylib         0x1d030 _malloc_put + 554
8  libsystem_malloc.dylib         0x1d2a4 malloc_zone_error + 100
9  libsystem_malloc.dylib         0xbfcc free_list_checksum_botch + 36
10 libsystem_malloc.dylib         0x93fc small_free_list_remove_ptr_no_clear + 1228
11 libsystem_malloc.dylib         0xa244 free_small + 592
12 Flutter                        0x4c4708 (missing UUID be105c8b7c053a8ba51f83e291732357)
13 Flutter                        0x615c40 (missing UUID be105c8b7c053a8ba51f83e291732357)
14 Flutter                        0x6170a0 (missing UUID be105c8b7c053a8ba51f83e291732357)
15 Flutter                        0x6175ac (missing UUID be105c8b7c053a8ba51f83e291732357)
16 Flutter                        0x60d76c (missing UUID be105c8b7c053a8ba51f83e291732357)
17 Flutter                        0x5c5afc (missing UUID be105c8b7c053a8ba51f83e291732357)
18 libsystem_pthread.dylib        0x8c9c _pthread_start + 288
19 libsystem_pthread.dylib        0xd880 thread_start + 8

[✓] Flutter (Channel stable, 2.10.3, on macOS 11.6 20G165 darwin-arm, locale
    zh-Hans-CN)
    • Flutter version 2.10.3 at /Users/Shared/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (5 weeks ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/blake/Library/Android/sdk
    • Platform android-32, build-tools 32.0.0
    • ANDROID_HOME = /Users/blake/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.63.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.36.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 100.0.4896.75

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/101491#issue-1195748363 force flutter#v2.10.3 ios release arm64

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/101491#issue-1195748363 force flutter#v2.10.3 ios release arm64

Labeling for further investigation

Unfortunately, I don't think there's enough information to go on here. All we can tell from the backtraces is that some form of heap corruption is causing deallocation to fail when a Paragraph object is GC's. This could either be because there is some problem with the lifetime of the Paragraph object, or Paragraph could simply be a casualty of some other issue.

This is happening for us, very frequently and we are able to reproduce it every time with the same error log

Hi, @pruthvi-itribe, can you share a reproducible sample?

We haven't been able to figure out  which code is causing this. Because it's happening randomly on different screens. And mostly it happens when app comes from background to foreground and pull to refresh a place


Unable to use '~' in virtualenvs-path from v1.2.0

Hello!
We recently updated to v1.2.0 and found that our virtualenvs were being put in the wrong place; instead of ~/.cache/virtualenvs they were being put into <project-dir>/~/.cache/virtualenvs.
Our action looked like this:
      - name: Install and configure poetry
        uses<EMAIL_ADDRESS>        with:
          virtualenvs-in-project: false
          virtualenvs-path: ~/.cache/virtualenvs

I did a bit of investigation and I think this is due to the github input being directly quoted: https://github.com/snok/install-poetry/blob/main/action.yml#L62, whereas previously it was not quoted before being passed to the script: https://github.com/snok/install-poetry/blob/v1.1.8/action.yml#L40, which allowed the shell to expand it.
I can of course hardcode the home directory instead of using ~ but this seems like a common case, so would it be worth changing this to allow expansion again?

Thanks for reporting this @JaimeLennox 👏
Yes I agree we should fix this. Would you be interested in trying to create a PR with a fix? Think we would need a test-case in the test workflow and an appropriate change in logic and that should be it 🙂
If you don't have time, I'll most likely fix this over the weekend!

Thanks for the quick response! I'll probably not have time today but might be able to take a look next week if you haven't got to it by then already 😄

I'll take a look at it then 👍  Looks like the problem is probably what you said, re https://github.com/koalaman/shellcheck/wiki/SC2088

I released a new version now @JaimeLennox. If you get time, please let me know whether it resolved your issue 🙂

Yep, looks good! Working perfectly, thanks 😄


Load mod-defined resources earlier

Mod Menu has an API for mods, which, among other things contains translatable descriptions and summaries.
A year ago I discovered that most mods actually don't use the summaries, which gave me a creative idea - what if I made a resource pack for my modpack to make all summaries consistent? So I did, people liked it and contributed translations to it.
However, recently some modders and translators have discovered the feature, and due to the way Mod Menu loads these strings later than the resource packs, the resource pack string becomes useless for those mods.
So here is my suggestion: what if you loaded mod-defined descriptions and summaries earlier than the resource packs? It would then work similarly to how resource packs can change a mod's textures.
Related to #401

Prospector and haykam helped me fix this - my resource pack used Mod Menu's namespace but

by using modmenu's namespace, you can only replace things that Mod Menu has jurisdiction over

so using a custom namespace fixed the issue. Language files apparently don't work the same as texture files and can be referenced from any namespace.

I'm having this issue again.
My resource pack provides a string for Iris' summary and Iris itself does too, somehow Iris' prevails in some languages.
Why does mine not take precedence if it is applied above "Fabric Mods" in resource packs list?
In Iris:
  "modmenu.summaryTranslation.iris":"Современный графический мод для загрузки существующих наборов шейдеров Optifine.",
  "modmenu.descriptionTranslation.iris": "Современный графический мод для Minecraft, предназначенный для загрузки существующих наборов шейдеров формата Optifine."

in my pack:
    "modmenu.summaryTranslation.iris": "Шейдеры OptiFine'а\n§9✎§8 Отключение мода, выбор шейдеров, ...",

Note: not all languages have those strings in Iris, not even English does.


⚠ Bofrost.at has degraded performance

In ed15cd0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2628 ms

Resolved: Bofrost.at performance has improved in 3222aac after 311 days, 17 hours, 8 minutes.


left arrow icon is smaller than all others

I am really impressed by this amazing plugin and would like to express my gratitude to all the developers involved in its creation. Your hard work is truly appreciated!
I have a small request, which isn't exactly an issue, but I hope it can be addressed. It appears that the icon for the left arrow is smaller than the other arrow icons. If possible, could this be adjusted to ensure consistency across all arrow icons?
Thank you for considering my request!
The correct one is:
      ▲
    ◀   ▶
      ▼

instead the one you provided:
◄ ▼ ▲ ►

notice the difference in size of the left arrow

Thank you for opening an issue.
I think this comes down to subjectivity. Indeed the arrows used are slightly narrower instead of using the "triangle" version of it which is wider. This is what I take as a reference: triangle, pointer.
It's already possible to override these if you prefer the others. See here.
To change it for everybody, I think it makes sense only if there is a general agreement.

Thank you for your insightful comments. I completely agree with your suggestions and will proceed with my own customization using the link you provided. I am now closing this issue. Thank you once again for your guidance, and please keep up the excellent work.