Update 3.0.0 manifest to use JDK-20

Description
Finally, https://github.com/opensearch-project/OpenSearch/pull/7344 is merged, we could use JDK-20 to build and run OpenSearch 3.x
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-build/issues/3425
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@peterzhuamazon here we are :)


Add Support for UI Toolkit

Hi there,
I am a developer using a combination of UniRX and UI Toolkit to do a pseudo-MVVM. UI Toolkit (Formerly UI Elements) is a preview package provided by Unity that provides a UI that is of industry Standard Design, as opposed to Unity's more simplistic hierarchical design. UI Toolkit allows for building out UI using a single-source declarative language. UniRX offers support for Bindings with the standard Unity UI (things like Buttons and Labels). UI Toolkits features alternative versions of such Buttons and Labels. I would appreciate the creation of support for Bindings with UI Toolkit's respective Visual Elements as either an add-on package or integrated into the main repo.
(Note: I viewed the UniRX tag before writing, but only looked at the first page and in searches, I could not find an add-on for UI Toolkit that already exists; It may well already be developed and I missed it. Please inform me as it would be incredibly helpful within my project)

Hey @crazyjackel,
I've developed a quite a collection of extension methods for binding observables to VisualElements.
It's nothing fancy, but it does the job well in my opinion. Would you be interested in my code?

Hello @scho  !
I would personally be really interested to see your code if possible, I'm also working with UITK and UniRX !

Hello @scho !
I would personally be really interested to see your code if possible, I'm also working with UITK and UniRX !

public static IDisposable BindVisualElementCallback<TEventType>(this VisualElement element, ReactiveCommand<TEventType> command, TrickleDown trickleDown = TrickleDown.NoTrickleDown) where TEventType : EventBase<TEventType>         {             var callback = new EventCallback<TEventType>((ev) => command.Execute(ev));             element.RegisterCallback(callback, trickleDown);             return Disposable.Create(() => { element.UnregisterCallback(callback, trickleDown); });         }
I am trying with something like this for right now. The Idea is that I can bind to Reactive Commands.
https://github.com/crazyjackel/redmoon-reactiveKit
I am still working on this and there is a little bit of testing, but it works with Unity's Package Manager, so that's nice. (Though, Unity's Package Manager really needs some work, can't even update git packages (planned for 2021.2))

Thank you very much, I'm going to test it right now !
At the moment I'm trying to extend the already existing element, for exemple the Button click and be able to Subscribe to it just like in UniRX with the current UGUI

@Kaiymu:
Sorry for answering back so late.
I finally managed to extracted my binding extensions and put them into a gist:
https://gist.github.com/scho/6ec3f30653119b3856b1a9edfd5b0b7b

No problem at all ! And thank you for that, I'm looking into your implementation right now ;).
Maybe you can do a merge request ?

@Kaiymu: Sorry for answering back so late. I finally managed to extracted my binding extensions and put them into a gist: https://gist.github.com/scho/6ec3f30653119b3856b1a9edfd5b0b7b

I like some of these, but I have some general critiques on impl.
Bind Display should have IObservable over IObservable to support future DisplayStyles, such as Grid being added. Also saves on a calculation.
I think ClickEvents should pass the event in as an action to implement.
Seeing someone else's implementation suggests some better ways to do mine.

@crazyjackel: Sure, the implementation could be improved. It's written to fit out project best and it does not claim to be a general solution for everyone.
Regarding the click events: We never need the actual event and it allows us to do the following:
_confirmButton.Bind(viewModel.Confirm).AddTo(this);

Regarding BindDisplay: Sure, this is not future proof. Maybe just naming it BindDisplayFlex would make it clear, that it's either Flex or None.
@Kaiymu: I'm not sure if it's wort to do a pull request. The last release of UniRx is from July 2019. If this changes, I can create a pull request.

I am updating my implementation package for Unity with some of the concepts that you provided. I think having this as a separate package would be good instead of further bloating out this package. That is one thing I dislike about UniRX is that it is rather bloated.

@crazyjackel: Sounds like a sensible decision to have a dedicated packe for the extensions. Do you plan to publish it on the asset store or here on Github?

https://github.com/crazyjackel/redmoon-reactiveKit
I have been developing this, I have updated the development branch recently. Provided is a Sample. Feel free to try it out and submit issues.  (Besides the Extensions, I also am including a MVVM-type system and a dependency (thought, I might make it a soft-dependency) for my Dependency Injection Package)

@crazyjackel: The MVVM looks interesting, it's a bit similar to what we use, but our's is rather basic (see https://gist.github.com/scho/d737ec33aa3b5b1e7fc8e04990d866d2).
Any reason why not using Zenject for DI?

It’s less of dependency injection and more of a way for a class to get references to enabling and disabling managers classes. Probably main reason is that I was not aware of it or how to use it.
I like how simple your view is, but I like to keep the view and the functionality of the view model separate (also as a way to have separate loading times). The code mostly comes from when I did some WPF work with ReactiveUI (copy what seems to work to a new system.)


⚠ AtmoVantage Homepage has degraded performance

In a7a1d70, AtmoVantage Homepage (https://atmovantage.com) experienced degraded performance:

HTTP code: 200
Response time: 8047 ms

Resolved: AtmoVantage Homepage performance has improved in 519d996.


Clean up: Change getByBlockNumber to be getByBlockHeader

Following https://github.com/hyperledger/besu/pull/4743
We should update all the usages we can to be getByBlockHeader and phase out getByBlockNumber.
getByBlockNumber can cause issues in a post-shanghai (TimestampSchedule-enabled) chain.
This has been intentionally separated out of #4743 so it doesn't make the PR huge, see this spike for an idea of what the changes might look like: https://github.com/hyperledger/besu/pull/4687
Another related item for clean-up:
https://github.com/hyperledger/besu/pull/4743#discussion_r1045390099

Partial work of the trivial replaces done here: https://github.com/gfukushima/besu/tree/replace-getByBlockNumber-by-getByBlockHeader

Bug found during goerli sync: https://github.com/hyperledger/besu/issues/5064


Modify Streaming Ozone Emissions Endpoint for CBS Intergration

Context
Modify Streaming Ozone Emissions Endpoint  for CBS Intergration  (see below for requirements)
Required Parameters:  facilityId and Year
Required Data Elements:  NOX MASS, OP_YEAR, SO2 MASS, Unit ID
If the location is not specified, then the system shall filter by the oris code and all of the locations for the oris code  are returned.
If loction and oris code are specified then the system shall filter by the location

The endpoint is returning the data below:
{
"stateCode":"AL",
"facilityName":"Barry",
"facilityId":3,
"unitId":"1",
"unit_id":1,
"associatedStacks":"CS0AAN",
"year":2020,
"countOpTime":0,
"sumOpTime":0,
"grossLoad":null,
"steamLoad":null,
"so2Mass":null,
"so2Rate":null,
"co2Mass":null,
"co2Rate":null,
"noxMass":null,
"noxRate":null,
"heatInput":null,
"primaryFuelInfo":"Pipeline Natural Gas",
"secondaryFuelInfo":null,
"unitType":"Tangentially-fired",
"so2ControlInfo":null,
"noxControlInfo":"Low NOx Burner Technology w/ Closed-coupled OFA,Selective Non-catalytic Reduction",
"pmControlInfo":null,
"hgControlInfo":null,
"programCodeInfo":"ARP, CSNOX, CSOSG2, CSSO2G2"
},
The system is working as expected


[HOLD for payment 2023-11-07] [$500] Request Money - Amount input getting displaced if there is an error

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696005319999269
Action Performed:

Login to new.expensify.com
Click on FAB > Request Money > Request

Expected Result:
An error message is shown and input doesn't move
Actual Result:
Amount input is getting displaced and error message is shown
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/93399543/3607ed54-5cf0-4b31-9406-5767e3092c69

Android: mWeb Chrome

https://github.com/Expensify/App/assets/93399543/aa688d30-ae44-4795-b37c-ad9a06f57bb7

iOS: Native

https://github.com/Expensify/App/assets/93399543/00ea7bb8-d669-4165-b43b-1d49109f73c2

iOS: mWeb Safari

https://github.com/Expensify/App/assets/93399543/381a076c-b53c-43bf-96f5-9698d3d8d584

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/2593aba3-5732-4dac-8496-f3c09314f67f

MacOS: Desktop

https://github.com/Expensify/App/assets/93399543/9266cb3d-7296-4be9-830d-99ebe35528ee

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0189b47702ed5e01e9
Upwork Job ID:<PHONE_NUMBER>907104768
Last Price Increase: 2023-10-17
Automatic offers:

situchan | Reviewer | 27350803
aman-atg | Contributor | 27350805
aman-atg | Reporter | 27350806

Proposal
Please re-state the problem that we are trying to solve in this issue.
Amount input getting displaced if there is an error
What is the root cause of that problem?
When the error message appears, it takes up additional vertical space within its container, causing the layout to shift.
What changes do you think we should make in order to solve the problem?

We can use a parent View for the FormHelpMessage and assign it a fixed height here, ensuring its presence at all times.
And when the conditions are met, the error message will occupy this space.
We might need to made some adjustments for BigNumberPad as it will also have an effect when BigNumberPad is visible for smaller screens (mWeb)
What alternative solutions did you explore? (Optional)
We can implement relative positioning by placing both the Amount Input's container and the FormHelpMessage within a parent View and then aligning the FormHelpMessage at the bottom.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~017cdcbaaecd47d62c

Proposal
Please re-state the problem that we are trying to solve in this issue.
Amount box displaces on error state changes
What is the root cause of that problem?
We are using flex1 to render all content on the screen to take the available width. At the time of error the height of the amount part will be reduced which causes the jump/displace in the screen.
What changes do you think we should make in order to solve the problem?
We can move the error part with the TextInputWithCurrencySymbol View and set its position to absolute, bcoz the amount input isn't multiline so it won't get overlapped and allows the amount part to be in the centered.
https://github.com/Expensify/App/blob/f79fbc14c0e10bc020e57f7d6e882617b19c3e64/src/pages/iou/steps/MoneyRequestAmountForm.js#L262-L271
          />
          {!_.isEmpty(formError) && (
              <FormHelpMessage
                  style={[styles.pAbsolute, styles.b0, styles.ph5, styles.w100]}
                  isError
                  message={translate(formError)}
              />
          )}
      </View>

Result
https://github.com/Expensify/App/assets/14358475/e4059dd7-3219-4eba-9a28-ed5f2c9f4bf2
https://github.com/Expensify/App/assets/14358475/f0271d3b-d09d-427b-a6c7-6de77e60cc03

Proposal
Please re-state the problem that we are trying to solve in this issue.
Amount input getting displaced if there is an error
What is the root cause of that problem?
Because we show FormHelpMessage that has height when when only has error.
What changes do you think we should make in order to solve the problem?

We need to update all FormHelpMessage usage.
From:

 {!_.isEmpty(formError) && (
          <FormHelpMessage
                    style={[styles.ph5]}
                    isError
                    message={translate(formError)}
          />
 )}

To:
<FormHelpMessage
           style={[styles.ph5]}
           isError
           message={!_.isEmpty(formError)? translate(formError) : ''}
 />

We need to return fixed height view instead of null

return (
            <View style={[styles.flexRow, styles.alignItemsCenter, styles.mt2, styles.mb1, ...props.style]}>
                    <View style={{height: 20}} />
            </View>
)

https://github.com/Expensify/App/blob/562f9d8ff66d1e90285df088fa785c9638aa3861/src/components/FormHelpMessage.js#L36
What alternative solutions did you explore? (Optional)
We can wrap with fixed height View like this.
            <View style={{height: 30}}>
                {!_.isEmpty(formError) && (
                    <FormHelpMessage
                        style={[styles.ph5]}
                        isError
                        message={translate(formError)}
                    />
                )}
            </View>

https://github.com/Expensify/App/blob/562f9d8ff66d1e90285df088fa785c9638aa3861/src/pages/iou/steps/MoneyRequestAmountForm.js#L265-L271

Proposal
Please re-state the problem that we are trying to solve in this issue.
Amount box displaces on error state changes
What is the root cause of that problem?
Input container height is changed because of error message
What changes do you think we should make in order to solve the problem?
We can show error message on position: absolute
https://github.com/Expensify/App/blob/f79fbc14c0e10bc020e57f7d6e882617b19c3e64/src/pages/iou/steps/MoneyRequestAmountForm.js#L265-L271
{!_.isEmpty(formError) && (
    <FormHelpMessage
            style={[styles.pAbsolute, styles.b0, styles.ph5]}
            isError
            message={translate(formError)}
    />
)}

What alternative solutions did you explore? (Optional)

reviewing proposals

Thanks for the proposals. Please share screenshot on iPhone SE safari

https://github.com/Expensify/App/assets/14358475/1f1bd35b-128e-4030-869d-bfe20b58a2b1

@aman-atg's proposal looks good to me.
I think alternative solution (absolute position) is better than main solution (fixed height). The only difference is vertical center align of amount input.
We should also make sure that error message is not overlapped with amount input on very small device (even smaller than iPhone SE)
🎀 👀 🎀 C+ reviewed

Everyone is paid

This is eligible for bonus

[x] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/23712
[x] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/23712/files#r1388117046
[x] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] Determine if we should create a regression test for this bug.
[x] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

This is minor style issue and doesn't affect money request flow so I propose no regression test

Looks like the PR was created before the announcement so just confirming the urgency bonus request @muttmuure.
Agreed no regression test necessary.

Urgency bonuses given


Linux pip install gives "Proj executable not found. Please set PROJ_DIR variable."

Installation method/steps
pip install pyproj

Environment Information

pyproj version you are attempting to install: 2.4.1 (this is not an issue for 2.4.0)
Tested with 3.5 and 3.6
Tested with Linux Mint 18 and Ubuntu Xenial

Error
 Running setup.py (path:/tmp/pip-install-qfelb_w6/pyproj/setup.py) egg_info for package pyproj
    Running command python setup.py egg_info
    Proj executable not found. Please set PROJ_DIR variable.

Since 2.4.1 release pip install won't work unless you have a more recent version of pip.
pip 18.1 for example will fail because it refuses to download the wheel packages and then will try to compile the sources.
Skipping link https://files.pythonhosted.org/packages/a5/b3/a3e00996681ef6e2e19cf367ff57e5e83ad8357f398b0cb71dab5cc8b756/pyproj-2.4.1-cp35-cp35m-manylinux2010_x86_64.whl#sha256=a1422da59673ca5bf56d89cf8e2a3cb2c9868bea27bbee6600ae603d322316a8
 (from https://pypi.org/simple/pyproj/) (requires-python:>=3.5); it is not compatible with this Python

Fix
The solution is to upgrade pip to a later version (pip install --upgrade pip)
You can close this issue if you think this is not a bug worth fixing. I created it mostly so users with the same issue may hopefully find this.

This is likely related to using manylinux2010 wheels with 2.4.1

@snowman2 I suppose it's possible with multibuild to still build both manylinux1 and manylinux2010 wheels and upload both?

According to: https://github.com/pypa/manylinux/issues/179#issue-314290405
It seems it should work with pip 10.x. I don't think that is too unreasonable of a minimum version of pip to use to install pyproj. Or are there reasons why that would be problematic?

Hmm, that's not very true. Need pip~=19.0.0 for it to work.

Apart from the pip version, there will also just be OSes that are too old for manylinux2010 (but don't know the exact requirements, not sure if the "2010" is a proper indicator)

Apart from the pip version, there will also just be OSes that are too old for manylinux2010 (but don't know the exact requirements, not sure if the "2010" is a proper indicator)

According to: https://github.com/pypa/manylinux/issues/179#issuecomment-541891168, "most of linux flavors that came out before 2010 are now EOL". So, if their maintainers aren't supporting them, then I am not sure if we should be supporting them either.

I had this issue on travis by the way. Default distro is Xenial there. And default pip 18.1.

I had this issue on travis by the way. Default distro is Xenial there. And default pip 18.1.

Yes, you will need pip>=19.0.0

I suppose it's possible with multibuild to still build both manylinux1 and manylinux2010 wheels and upload both?

I guess this is likely the best path forward if it works.

Yes, the old distros is probably as you quoted not really a problem. Old pip versions seems more annoying (AFAIK there is no good way to message to the users of "hey you should upgrade pip to ensure to install pyproj wheels").

Old pip versions seems more annoying (AFAIK there is no good way to message to the users of "hey you should upgrade pip to ensure to install pyproj wheels").

I guess I could add a message in the setup.py that says if you want manylinux2010 wheels, update to `pip>=19.0' if the install fails and they are on Linux.
Current plan:

Update docs to say if you want manylinux2010 update to pip 19+
Update setup.py
Upload manylinux1 for 2.4.1

hey @snowman2 i'm so happy i found this issue as i started running into this - this week - with our travis build. I'm noticing it works on python 3.5, 3.6 but fails again on 3.7 . essentially i added pip >=19.0 as a dep to my envt setup.
pr here:  https://github.com/earthlab/earthpy/pull/452/files
travis error: https://travis-ci.org/earthlab/earthpy/jobs/608881106#L1172
is there anything else that i can test for python 3.7 or is my fix or forcing pip>19.0 incomplete?
many thanks.

@lwasser it seems that fixed your pyproj issues. The build seems to be failing for a different reason now.

Ubuntu Bionic is certainly not EOL nor is it using Pip > 9.0, and upgrading to a newer pip brings its own problems. Is it necessary to have a breaking change for a minor point release?
https://packages.ubuntu.com/bionic/python3-pip

hey @snowman2  ok thank you!! i figured it out. it was a pyproj error associated with tox needing the pip dependency too!! for anyone else running into this - the fix is as easy as this:
https://github.com/earthlab/earthpy/pull/452/files#diff-b91f3d5bd63fcd17221b267e851608e8R21
essentially specifying pip>=19.0 as a dep in the tox envt as well as the deps file (if things are setup the way we have them setup for you that is!!).
thank you again for this issue! it helped me resolve things!!


how to reduce size of kubevirt component images?

Is this a BUG REPORT or FEATURE REQUEST?:
/kind enhancement
What happened:
The size of kubevirt component images is so large:
virt-operator 425M
virt-api 387M
virt-controller 388M
virt-handler 780M
virt-launcher 745M
cirros-registry-disk-demo 202M
there are two problems:
(1) where is the dockerfile of every component, I only find a dockerfile in hack/builder.
(2) how to reduce the size of images?
What you expected to happen:
Reduce size of every image to less than 100M.
How to reproduce it (as minimally and precisely as possible):
Docker pull from dockerhub.
Anything else we need to know?:
no.
Environment:

KubeVirt version (use virtctl version): v0.33.0
Kubernetes version (use kubectl version):1.17.9
VM or VMI specifications:no
Cloud provider or hardware configuration:no
OS (e.g. from /etc/os-release):centos
Kernel (e.g. uname -a):3.10.0
Install tools:no
Others:no

KubeVirt uses bazel to build the images. So you won't find any Dockerfiles, except the Dockerfile for the builder image.

look at the BUILD.bazel  files for each component. For example, virt-handler's is ````cmd/virt-handler/BUILD.bazel```. the container_image section in there defines how the containers are built with bazel


Automatically stage Release Candidates to gMaven

The current procedure is:

Push a commit to the stable branch updating the release candidate number
Cut the release on GitHub, wait for the m2repo build action to finish
Download the finished artifact, stage on x20
Run the gmaven_publish command to stage it.

This can all be done automatically via Kokoro

Pending internal review for Google backend components, moving out to 0.22.


Alarm entity arming itself.

Hello,
I'm facing issue with self arming alarm entity. Not a single error in log file and action log just says that alarm has been armed, there is no trigger mention. When I'm disarming then it correctly says that it has been disarmed by user x. No automations seted up, no automations or other actions in MiHome as well and Gateway is working in ZHA mode without any child devices except M2 mesh lights, Mi flora and temp sensor (all bluetooth).

And some logs:
2021-02-05 00:01:22 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=alarm_control_panel.0xbc33acfffe514b02_alarm, old_state=<state alarm_control_panel.0xbc33acfffe514b02_alarm=disarmed; code_format=None, changed_by=None, code_arm_required=False, friendly_name=Xiaomi Gateway 3 Alarm, icon=mdi:shield-home, supported_features=7 @ 2021-02-05T00:00:22.388879+01:00>, new_state=<state alarm_control_panel.0xbc33acfffe514b02_alarm=armed_home; code_format=None, changed_by=None, code_arm_required=False, friendly_name=Xiaomi Gateway 3 Alarm, icon=mdi:shield-home, supported_features=7 @ 2021-02-05T00:01:22.033335+01:00>> 2021-02-05 00:01:22 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547131661856] Sending {"id": 275, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "old_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "disarmed", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:00:22.388879+00:00", "last_updated": "2021-02-04T23:00:22.388879+00:00", "context": {"id": "f46519094920a5d208ec47c71cd02d24", "parent_id": null, "user_id": "238b30160b00496bbfd60ab1a0215297"}}, "new_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "armed_home", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:01:22.033335+00:00", "last_updated": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}} 2021-02-05 00:01:22 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547128817168] Sending {"id": 2, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "old_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "disarmed", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:00:22.388879+00:00", "last_updated": "2021-02-04T23:00:22.388879+00:00", "context": {"id": "f46519094920a5d208ec47c71cd02d24", "parent_id": null, "user_id": "238b30160b00496bbfd60ab1a0215297"}}, "new_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "armed_home", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:01:22.033335+00:00", "last_updated": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}} 2021-02-05 00:01:22 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547131542880] Sending {"id": 2, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "old_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "disarmed", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:00:22.388879+00:00", "last_updated": "2021-02-04T23:00:22.388879+00:00", "context": {"id": "f46519094920a5d208ec47c71cd02d24", "parent_id": null, "user_id": "238b30160b00496bbfd60ab1a0215297"}}, "new_state": {"entity_id": "alarm_control_panel.0xbc33acfffe514b02_alarm", "state": "armed_home", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "Xiaomi Gateway 3 Alarm", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-04T23:01:22.033335+00:00", "last_updated": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-02-04T23:01:22.033335+00:00", "context": {"id": "7c16dc078cc174d5f7c279e49bfa6185", "parent_id": null, "user_id": null}}}

I think alarm is useless in ZHA mode because it trigger on mihome Zigbee devices

Moving back to MiHome mode should fix it?

I am using Mihome mode.And I have the same problem.

You can enable integration debug logs and check what happened there

2021-02-09 08:48:43 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=alarm_control_panel.0x588e81fffee17498_alarm, old_state=None, new_state=<state alarm_control_panel.0x588e81fffee17498_alarm=disarmed; code_format=None, changed_by=None, code_arm_required=False, friendly_name=三楼网关, icon=mdi:shield-home, supported_features=7 @ 2021-02-09T08:48:43.417208+08:00>>
2021-02-09 08:48:43 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=alarm_control_panel.0x588e81fffedc322e_alarm, old_state=None, new_state=<state alarm_control_panel.0x588e81fffedc322e_alarm=disarmed; code_format=None, changed_by=None, code_arm_required=False, friendly_name=客厅网关, icon=mdi:shield-home, supported_features=7 @ 2021-02-09T08:48:43.418187+08:00>>
2021-02-09 08:48:43 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [140320650306656] Sending {"id": 2, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "alarm_control_panel.0x588e81fffee17498_alarm", "old_state": null, "new_state": {"entity_id": "alarm_control_panel.0x588e81fffee17498_alarm", "state": "disarmed", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "\u4e09\u697c\u7f51\u5173", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-09T00:48:43.417208+00:00", "last_updated": "2021-02-09T00:48:43.417208+00:00", "context": {"id": "1e845f38a70477f2b08f5b0fdcc2a3a6", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-02-09T00:48:43.417208+00:00", "context": {"id": "1e845f38a70477f2b08f5b0fdcc2a3a6", "parent_id": null, "user_id": null}}}
2021-02-09 08:48:43 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [140320650306656] Sending {"id": 2, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "alarm_control_panel.0x588e81fffedc322e_alarm", "old_state": null, "new_state": {"entity_id": "alarm_control_panel.0x588e81fffedc322e_alarm", "state": "disarmed", "attributes": {"code_format": null, "changed_by": null, "code_arm_required": false, "friendly_name": "\u5ba2\u5385\u7f51\u5173", "icon": "mdi:shield-home", "supported_features": 7}, "last_changed": "2021-02-09T00:48:43.418187+00:00", "last_updated": "2021-02-09T00:48:43.418187+00:00", "context": {"id": "f6977b2d2ba5dc4d0b93cdf016ceb4e6", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-02-09T00:48:43.418187+00:00", "context": {"id": "f6977b2d2ba5dc4d0b93cdf016ceb4e6", "parent_id": null, "user_id": null}}}
It seemed nothing wrong,but it did changed again and again.

You showing global Hass log. But interesting to investigate integration log.

021-02-09 21:00:00  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:03:59:59.803 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226040} length:55 bytes 2021-02-09 21:00:00  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:03:59:59.803 [I] internal: handle_local_msg_state:{"id":226040,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:03  DEBUG    mini_miio     Send get_properties 128B, recv 448B in 0.0 sec and 1 try 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.922 [D] otu: {"id":901083061,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]}. 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.993 [D] miio_client_func: method_local_broadcast_msg(), {"id":901083061,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]} 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.993 [D] miio_client_func: 9, msg: {"id":901083061,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]},  len:91 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.001 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":901083061,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} length:84 bytes 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.001 [D] miio_client_func: handle_command_ack_msg: {"id":901083061,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} 2021-02-09 21:00:03  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:02.102 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":901083061,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}],"exe_time":110}, len: 99 2021-02-09 21:00:10  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:09.073 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226041} length:55 bytes 2021-02-09 21:00:10  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:09.073 [I] internal: handle_local_msg_state:{"id":226041,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:15  DEBUG    mini_miio     Send set_properties 144B, recv 448B in 0.0 sec and 1 try 2021-02-09 21:00:15  DEBUG    mini_miio     Send get_properties 128B, recv 144B in 0.0 sec and 1 try 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.692 [D] otu: {"id":558469433,"method":"set_properties","params":[{"did":"374684771","siid":3,"piid":1,"value":0}]}. 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.802 [D] otu: {"id":471832989,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]}. 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.803 [D] miio_client_func: method_local_broadcast_msg(), {"id":558469433,"method":"set_properties","params":[{"did":"374684771","siid":3,"piid":1,"value":0}]} 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.803 [D] miio_client_func: 9, msg: {"id":558469433,"method":"set_properties","params":[{"did":"374684771","siid":3,"piid":1,"value":0}]},  len:101 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.811 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":558469433,"result":[{"code":0,"did":"374684771","piid":1,"siid":3}]} length:74 bytes 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.811 [D] miio_client_func: handle_command_ack_msg: {"id":558469433,"result":[{"code":0,"did":"374684771","piid":1,"siid":3}]} 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.873 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":558469433,"result":[{"code":0,"did":"374684771","piid":1,"siid":3}],"exe_time":110}, len: 89 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.922 [D] miio_client_func: method_local_broadcast_msg(), {"id":471832989,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]} 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.922 [D] miio_client_func: 9, msg: {"id":471832989,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]},  len:91 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.929 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":471832989,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} length:84 bytes 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.929 [D] miio_client_func: handle_command_ack_msg: {"id":471832989,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} 2021-02-09 21:00:15  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:14.982 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":471832989,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}],"exe_time":110}, len: 99 2021-02-09 21:00:16  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:15.773 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":null,"id":226042} length:57 bytes 2021-02-09 21:00:16  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:15.774 [I] internal: handle_local_msg_state:{"id":226042,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:17  DEBUG    mini_miio     Send get_properties 336B, recv 128B in 0.0 sec and 1 try 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | Pull Mesh [{'code': 0, 'did': '374684771', 'piid': 1, 'siid': 3}] 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.497 [D] otu: {"id":294709315,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]}. 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.542 [D] miio_client_func: method_local_broadcast_msg(), {"id":294709315,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]} 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.542 [D] miio_client_func: 9, msg: {"id":294709315,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]},  len:287 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.551 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":294709315,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}]} length:396 bytes 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.551 [D] miio_client_func: handle_command_ack_msg: {"id":294709315,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}]} 2021-02-09 21:00:17  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:16.632 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":294709315,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}],"exe_time":110}, len: 411 2021-02-09 21:00:20  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:19.583 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226043} length:55 bytes 2021-02-09 21:00:20  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:19.583 [I] internal: handle_local_msg_state:{"id":226043,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:24  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:24.143 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"_sync.ble_mesh_keep_alive","uptype":2,"params":[{"did":"1042016013","rssi":-66,"hops":0,"ts":1612900821},{"did":"1042079783","rssi":-72,"hops":0,"ts":1612900823},{"did":"1042086761","rssi":-65,"hops":0,"ts":1612900822},{"did":"1042079500","rssi":-56,"hops":0,"ts":1612900819},{"did":"1042079488","rssi":-59,"hops":0,"ts":1612900823},{"did":"1042001282","rssi":-59,"hops":0,"ts":1612900822}],"id":226044} length:414 bytes 2021-02-09 21:00:24  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:24.144 [D] miio_client_rpc: call={"method":"_sync.ble_mesh_keep_alive","uptype":2,"params":[{"did":"1042016013","rssi":-66,"hops":0,"ts":1612900821},{"did":"1042079783","rssi":-72,"hops":0,"ts":1612900823},{"did":"1042086761","rssi":-65,"hops":0,"ts":1612900822},{"did":"1042079500","rssi":-56,"hops":0,"ts":1612900819},{"did":"1042079488","rssi":-59,"hops":0,"ts":1612900823},{"did":"1042001282","rssi":-59,"hops":0,"ts":1612900822}],"id":226044} 2021-02-09 21:00:24  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:24.222 [D] ots: ots_up_rpc_delegate_out_cb(), 289, {"method":"_sync.ble_mesh_keep_alive","uptype":2,"params":[{"did":"1042016013","rssi":-66,"hops":0,"ts":1612900821},{"did":"1042079783","rssi":-72,"hops":0,"ts":1612900823},{"did":"1042086761","rssi":-65,"hops":0,"ts":1612900822},{"did":"1042079500","rssi":-56,"hops":0,"ts":1612900819},{"did":"1042079488","rssi":-59,"hops":0,"ts":1612900823},{"did":"1042001282","rssi":-59,"hops":0,"ts":1612900822}],"id":226044} 2021-02-09 21:00:25  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:24.372 [D] ots: {"id":226044,"result":{"report_interval":180,"delta":120,"filter":[]}}. 2021-02-09 21:00:25  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:24.442 [D] miio_client_func: ot_agent_send_ack id 226044: {"id":226044,"result":{"report_interval":180,"delta":120,"filter":[]}} len=70 2021-02-09 21:00:30  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:29.492 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226045} length:55 bytes 2021-02-09 21:00:30  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:29.493 [I] internal: handle_local_msg_state:{"id":226045,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:30.352 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.4.14ivvur44gc00","mac":"C4:7C:8D:6B:B0:FA","pdid":152},"evt":[{"eid":4105,"edata":"bf00"}],"frmCnt":228,"gwts":1612900829},"id":226046} length:192 bytes 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | Process BLE {'dev': {'did': 'blt.4.14ivvur44gc00', 'mac': 'C4:7C:8D:6B:B0:FA', 'pdid': 152}, 'evt': [{'eid': 4105, 'edata': 'bf00'}], 'frmCnt': 228, 'gwts':<PHONE_NUMBER>} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:30.353 [D] miio_client_rpc: call={"method":"_async.ble_event","params":{"dev":{"did":"blt.4.14ivvur44gc00","mac":"C4:7C:8D:6B:B0:FA","pdid":152},"evt":[{"eid":4105,"edata":"bf00"}],"frmCnt":228,"gwts":1612900829},"id":226046} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | Process BLE {'dev': {'did': 'blt.4.14ivvur44gc00', 'mac': 'C4:7C:8D:6B:B0:FA', 'pdid': 152}, 'evt': [{'eid': 4105, 'edata': 'bf00'}], 'frmCnt': 228, 'gwts':<PHONE_NUMBER>} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:30.382 [D] ots: ots_up_rpc_delegate_out_cb(), 289, {"method":"_async.ble_event","params":{"dev":{"did":"blt.4.14ivvur44gc00","mac":"C4:7C:8D:6B:B0:FA","pdid":152},"evt":[{"eid":4105,"edata":"bf00"}],"frmCnt":228,"gwts":1612900829},"id":226046} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | Process BLE {'dev': {'did': 'blt.4.14ivvur44gc00', 'mac': 'C4:7C:8D:6B:B0:FA', 'pdid': 152}, 'evt': [{'eid': 4105, 'edata': 'bf00'}], 'frmCnt': 228, 'gwts':<PHONE_NUMBER>} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] ble/blt.4.14ivvur44gc00 {"conductivity":191,"temperature":23.5,"illuminance":68,"moisture":4} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] ble/blt.4.14ivvur44gc00 {"conductivity":191,"temperature":23.5,"illuminance":68,"moisture":4} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] ble/blt.4.14ivvur44gc00 {"conductivity":191,"temperature":23.5,"illuminance":68,"moisture":4} 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:30.422 [D] ots: {"id":226046,"result":"ok"}. 2021-02-09 21:00:31  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:30.492 [D] miio_client_func: ot_agent_send_ack id 226046: {"id":226046,"result":"ok"} len=27 2021-02-09 21:00:33  DEBUG    mini_miio     Send get_properties 128B, recv 144B in 0.0 sec and 1 try 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.892 [D] otu: {"id":713495853,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]}. 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.992 [D] miio_client_func: method_local_broadcast_msg(), {"id":713495853,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]} 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.992 [D] miio_client_func: 9, msg: {"id":713495853,"method":"get_properties","params":[{"did":"374684771","siid":3,"piid":1}]},  len:91 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.999 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":713495853,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} length:84 bytes 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.000 [D] miio_client_func: handle_command_ack_msg: {"id":713495853,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}]} 2021-02-09 21:00:33  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:32.023 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":713495853,"result":[{"code":0,"did":"374684771","piid":1,"siid":3,"value":0}],"exe_time":111}, len: 99 2021-02-09 21:00:40  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:39.072 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226047} length:55 bytes 2021-02-09 21:00:40  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:39.073 [I] internal: handle_local_msg_state:{"id":226047,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:46  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:45.783 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":null,"id":226048} length:57 bytes 2021-02-09 21:00:46  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:45.784 [I] internal: handle_local_msg_state:{"id":226048,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:00:47  DEBUG    mini_miio     Send get_properties 336B, recv 448B in 0.0 sec and 1 try 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.553 [D] ots: ots_up_rpc_delegate_out_cb(), 289, {"id":40190599,"method":"_otc.pull_ip_list","params":{}} 2021-02-09 21:00:47  DEBUG    mini_miio     Send get_properties 336B, recv 144B in 0.0 sec and 1 try 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Pull Mesh [{'did': '1042016013', 'siid': 2, 'piid': 1, 'value': True, 'code': 0}, {'did': '1042079783', 'siid': 2, 'piid': 1, 'value': True, 'code': 0}, {'did': '1042086761', 'siid': 2, 'piid': 1, 'value': True, 'code': 0}, {'did': '1042079500', 'siid': 2, 'piid': 1, 'value': False, 'code': 0}, {'did': '1042079488', 'siid': 2, 'piid': 1, 'value': False, 'code': 0}, {'did': '1042001282', 'siid': 2, 'piid': 1, 'value': False, 'code': 0}, {'code': 0, 'did': '374684771', 'piid': 1, 'siid': 3, 'value': 0}] 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': True} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': True} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': True} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': False} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': False} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | Process Mesh Data for<PHONE_NUMBER>: {'light': False} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.642 [D] otu: {"id":952465334,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]}. 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.663 [D] miio_client_func: method_local_broadcast_msg(), {"id":952465334,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.663 [D] miio_client_func: 9, msg: {"id":952465334,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":1},{"did":"1042079783","siid":2,"piid":1},{"did":"1042086761","siid":2,"piid":1},{"did":"1042079500","siid":2,"piid":1},{"did":"1042079488","siid":2,"piid":1},{"did":"1042001282","siid":2,"piid":1}]},  len:287 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.670 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":952465334,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}]} length:396 bytes 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.670 [D] miio_client_func: handle_command_ack_msg: {"id":952465334,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}]} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.702 [D] ots: {"id":40190599,"result":{"svr_list":[{"ip":"<IP_ADDRESS>","port":443},{"ip":"<IP_ADDRESS>","port":443}],"interval":1800, "firstprobe":511}}. 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.752 [D] otu: {"id":149144328,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":2},{"did":"1042016013","siid":2,"piid":3},{"did":"1042079783","siid":2,"piid":2},{"did":"1042079783","siid":2,"piid":3},{"did":"1042086761","siid":2,"piid":2},{"did":"1042086761","siid":2,"piid":3}]}. 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.772 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":952465334,"result":[{"did":"1042016013","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079783","siid":2,"piid":1,"value":true,"code":0},{"did":"1042086761","siid":2,"piid":1,"value":true,"code":0},{"did":"1042079500","siid":2,"piid":1,"value":false,"code":0},{"did":"1042079488","siid":2,"piid":1,"value":false,"code":0},{"did":"1042001282","siid":2,"piid":1,"value":false,"code":0}],"exe_time":110}, len: 411 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.782 [D] miio_client_func: method_local_broadcast_msg(), {"id":149144328,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":2},{"did":"1042016013","siid":2,"piid":3},{"did":"1042079783","siid":2,"piid":2},{"did":"1042079783","siid":2,"piid":3},{"did":"1042086761","siid":2,"piid":2},{"did":"1042086761","siid":2,"piid":3}]} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.782 [D] miio_client_func: 9, msg: {"id":149144328,"method":"get_properties","params":[{"did":"1042016013","siid":2,"piid":2},{"did":"1042016013","siid":2,"piid":3},{"did":"1042079783","siid":2,"piid":2},{"did":"1042079783","siid":2,"piid":3},{"did":"1042086761","siid":2,"piid":2},{"did":"1042086761","siid":2,"piid":3}]},  len:287 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.789 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"id":149144328,"result":[{"did":"1042016013","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042016013","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042079783","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042079783","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042086761","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042086761","siid":2,"piid":3,"value":3460,"code":0}]} length:396 bytes 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.789 [D] miio_client_func: handle_command_ack_msg: {"id":149144328,"result":[{"did":"1042016013","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042016013","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042079783","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042079783","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042086761","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042086761","siid":2,"piid":3,"value":3460,"code":0}]} 2021-02-09 21:00:47  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:46.882 [D] otu: otu_down_rpc_delegate_ack(), 324, ack: {"id":149144328,"result":[{"did":"1042016013","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042016013","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042079783","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042079783","siid":2,"piid":3,"value":3460,"code":0},{"did":"1042086761","siid":2,"piid":2,"value":32125,"code":0},{"did":"1042086761","siid":2,"piid":3,"value":3460,"code":0}],"exe_time":108}, len: 411 2021-02-09 21:00:51  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:50.833 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226049} length:55 bytes 2021-02-09 21:00:51  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:00:50.833 [I] internal: handle_local_msg_state:{"id":226049,"method":"local.status","params":"cloud_connected"} 2021-02-09 21:01:01  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:01:00.932 [D] miio_client_func: ot_agent_recv_handler_one(): fd:9, msg:{"method":"local.query_status","params":"","id":226050} length:55 bytes 2021-02-09 21:01:01  DEBUG    gateway3      <IP_ADDRESS> | [MQ] log/miio 2021:02:10:04:01:00.933 [I] internal: handle_local_msg_state:{"id":226050,"method":"local.status","params":"cloud_connected"}
These are my logs. Hope you can read something about alarm here as I couldn't ;)

Yes I can. Alarm was in off state all the time. And additionally you send command to turn off it.

@AlexxIT The same problem here.
My gateway is running in Mi Home mode. It only happens when I am using a Xiaomi Button (the round one). When the state in HASS became "Armed Home"(I was notified by HomeKit bridged by HASS), The actual state was disarmed, the same as it reads via miio. The gateway doesn't beep like it changes arming mode as usual. The state in HASS keeps until next time the problem happened again, which was not long after I used the Xiaomi Button.

(This comment is the same as the one above)
针对楼主的回复： @broda1125 @mikeinblue
我发现这个问题只有在操作过“小米无线开关”后才会出现，而操作Aqara六键开关时不会出现（我的两个无线开关都是这样；我只有这些设备了）。如果连续操作开关，就可能导致警戒状态变化，如果警戒状态变化后立即停止操作，警戒状态会停留在错误的状态。你们的也是这样吗？

(This comment is the same as the one above)
针对楼主的回复： @broda1125 @mikeinblue
我发现这个问题只有在操作过“小米无线开关”后才会出现，而操作Aqara六键开关时不会出现（我的两个无线开关都是这样；我只有这些设备了）。如果连续操作开关，就可能导致警戒状态变化，如果警戒状态变化后立即停止操作，警戒状态会停留在错误的状态。你们的也是这样吗？
我是定时开启夜间警戒，然后hass里的状态就一直来回变化，实体的网关其实并没有变化。

I also have a issue with the gateway alarm randomly going off. Only recently came about I'm not sure which HA upgrade has caused the issue. I only have one automation to arm the alarm and it was not triggered before the alarm going off.

Please reopen the issue if it is still relevant


Build a Random Quote Machine: As user I can share current quote with tumblr

Acceptance criteria: tumblr button should be consistence with APP.
Sub-tasks:

find in tumblr way to create a button
provide custom tumblr icon


Evaluate: tiiuae/falcon-11B

Check upon issue creation:

[ ] The model has not been evaluated yet and doesn't show up on the CoT Leaderboard.
[ ] There is no evaluation request issue for the model in the repo.
[ ] The parameters below have been adapted and shall be used.

Parameters:
NEXT_MODEL_PATH=tiiuae/falcon-11B
NEXT_MODEL_REVISION=main
NEXT_MODEL_PRECISION=bfloat16
MAX_LENGTH=2048
GPU_MEMORY_UTILIZATION=0.8
VLLM_SWAP_SPACE=4

ToDos:

[ ] Run cot-eval pipeline
[ ] Merge pull requests for cot-eval results datats (> @ggbetz)
[ ] Create eval request record to update metadata on leaderboard (> @ggbetz)

possible issue with VLLM and transformers: 2024-06-09T00:56:34.809027540Z (RayWorkerVllm pid=10931) INFO 06-09 00:55:41 pynccl_utils.py:45] vLLM is using nccl==2.18.1 [repeated 2x across cluster] 2024-06-09T00:56:34.810614509Z Traceback (most recent call last): 2024-06-09T00:56:34.810640753Z   File "/usr/local/bin/cot-eval", line 8, in <module> 2024-06-09T00:56:34.810670576Z     sys.exit(main()) 2024-06-09T00:56:34.810676624Z   File "/workspace/cot-eval/src/cot_eval/__main__.py", line 149, in main 2024-06-09T00:56:34.810719213Z     llm = VLLM( 2024-06-09T00:56:34.810737842Z   File "/usr/local/lib/python3.10/dist-packages/langchain_core/load/serializable.py", line 120, in __init__ 2024-06-09T00:56:34.810753544Z     super().__init__(**kwargs) 2024-06-09T00:56:34.810762650Z   File "/usr/local/lib/python3.10/dist-packages/pydantic/v1/main.py", line 339, in __init__ 2024-06-09T00:56:34.810825823Z     values, fields_set, validation_error = validate_model(__pydantic_self__.__class__, data) 2024-06-09T00:56:34.810833903Z   File "/usr/local/lib/python3.10/dist-packages/pydantic/v1/main.py", line 1102, in validate_model 2024-06-09T00:56:34.810972709Z     values = validator(cls_, values) 2024-06-09T00:56:34.810989335Z   File "/usr/local/lib/python3.10/dist-packages/langchain_community/llms/vllm.py", line 88, in validate_environment 2024-06-09T00:56:34.810996428Z     values["client"] = VLLModel( 2024-06-09T00:56:34.810998644Z   File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/llm.py", line 112, in __init__ 2024-06-09T00:56:34.811023086Z     self.llm_engine = LLMEngine.from_engine_args( 2024-06-09T00:56:34.811028309Z   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/llm_engine.py", line 196, in from_engine_args 2024-06-09T00:56:34.811084375Z     engine = cls( 2024-06-09T00:56:34.811087001Z   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/llm_engine.py", line 110, in __init__ 2024-06-09T00:56:34.811088759Z     self.model_executor = executor_class(model_config, cache_config, 2024-06-09T00:56:34.811091133Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/ray_gpu_executor.py", line 62, in __init__ 2024-06-09T00:56:34.811126708Z     self._init_workers_ray(placement_group) 2024-06-09T00:56:34.811132405Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/ray_gpu_executor.py", line 192, in _init_workers_ray 2024-06-09T00:56:34.811168916Z     self._run_workers( 2024-06-09T00:56:34.811174082Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/ray_gpu_executor.py", line 324, in _run_workers 2024-06-09T00:56:34.811209017Z     driver_worker_output = getattr(self.driver_worker, 2024-06-09T00:56:34.811214567Z   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/worker.py", line 107, in load_model 2024-06-09T00:56:34.811242529Z     self.model_runner.load_model() 2024-06-09T00:56:34.811247480Z   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/model_runner.py", line 95, in load_model 2024-06-09T00:56:34.811256892Z     self.model = get_model( 2024-06-09T00:56:34.811258664Z   File "/usr/local/lib/python3.10/dist-packages/vllm/model_executor/model_loader.py", line 101, in get_model 2024-06-09T00:56:34.811294265Z     model.load_weights(model_config.model, model_config.download_dir, 2024-06-09T00:56:34.811301734Z   File "/usr/local/lib/python3.10/dist-packages/vllm/model_executor/models/falcon.py", line 425, in load_weights 2024-06-09T00:56:34.811364589Z     param = params_dict[name] 2024-06-09T00:56:34.811377353Z KeyError: 'transformer.h.26.input_layernorm.weight' 2024-06-09T00:56:36.929909774Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44] Error executing method load_model. This might cause deadlock in distributed execution. 2024-06-09T00:56:36.929931343Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44] Traceback (most recent call last): 2024-06-09T00:56:36.929933284Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/ray_utils.py", line 37, in execute_method 2024-06-09T00:56:36.929935669Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]     return executor(*args, **kwargs) 2024-06-09T00:56:36.929937002Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/worker.py", line 107, in load_model 2024-06-09T00:56:36.929938537Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]     self.model_runner.load_model() 2024-06-09T00:56:36.929939834Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/model_runner.py", line 95, in load_model 2024-06-09T00:56:36.929941274Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]     self.model = get_model( 2024-06-09T00:56:36.929942571Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]   File "/usr/local/lib/python3.10/dist-packages/vllm/model_executor/model_loader.py", line 101, in get_model 2024-06-09T00:56:36.929944200Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]     model.load_weights(model_config.model, model_config.download_dir, 2024-06-09T00:56:36.929945603Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]   File "/usr/local/lib/python3.10/dist-packages/vllm/model_executor/models/falcon.py", line 425, in load_weights 2024-06-09T00:56:36.929947310Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44]     param = params_dict[name] 2024-06-09T00:56:36.929948607Z (RayWorkerVllm pid=10701) ERROR 06-09 00:56:34 ray_utils.py:44] KeyError: 'transformer.h.26.input_layernorm.weight' 2024-06-09T00:56:36.929950064Z (RayWorkerVllm pid=10931) INFO 06-09 00:56:03 weight_utils.py:177] Using model weights format ['*.safetensors'] [repeated 2x across cluster] 2024-06-09T00:56:36.929952403Z (RayWorkerVllm pid=10931) ERROR 06-09 00:56:35 ray_utils.py:44] Error executing method load_model.


update: added strapi provider example to readme

Added a Strapi provider example
Added Application-Side useFetch nitro call with session cookie headers
Added Server-Side getToken JWT retrieval
Checks:

[#] Closes subitem Strapi example documentation addition, issue 30.

That would be so nice, I'm working with Strapi and Nuxt3 right now and I was looking for a solution. Thanks for this one !

You can follow this for Strapi v4 and Nuxt3.
https://darweb.nl/foundry/article/nuxt3-sidebase-strapi-user-auth

Hey @BracketJohn, wanna take a look at my commits whenever you get the chance


Bot not respon a request from mattermost

hi,
i'm trying to configure the bot to make chatops
i build hubot matteruser on docker container
but i'm got some error, when call the bot to respon my order in mattermost don't show any respon
but in hubot logs, i got some error like this

any one please can help me, with this problem
thanks

Hi @centen , looks like something is going wrong with loading the profiles. I have not tested the bot with Mattermost 5.2.0 yet though. you might have luck with an older version of the Mattermost server. I will try to look into in the next couple of days.

I am also experiencing the same issue. Running Mattermost v4.10.1

Hello, me too.
But I haven't the issue when I don't run it in container.
Version: 4.8.0 of Mettermost

@thomasbellois if I may know,
that you don't run in a container, it mattermost or the hubot?
Thanks

@centen the goal is to run all on Docker.
Mattermost is already on.
I tested hubot with matteruser without "containerizing" it. The result was OK.
I tryed on Docker but I have the error. However, I use the same connection parameters for the bot.

Same issue here.  Mattermost 4.9, running hubot with docker-compose.

Ah, I responded in another issue but I am having the same problem myself: https://cl.ly/340J1S3x0k1h

Not working out of the box, 4.10.1. I suspect (due to matteruser.coffee:201:36 in the exception) this is caused by an old version of the client being loaded in the Docker script.

generator-hubot uses the latest published version of the adapter. And the latest version of hubot-matteruser has the .coffee script instead of the newer .js variant. So all what we need is a new release

@codeart1st is right.
Npm package, which is used by yo generator, use v 4.4.0, which has old .coffee file.
If you change (old) matteruser.coffee by (new, available here in Github repo) matteruser.js all works as expected in the newer Matttermost versions.
@loafoe could you please take a look on adding a new release? 😃

I tried to replace the matteruser file by doing this
RUN echo no | yo hubot --adapter=matteruser --name="${hubot_name}" --owner="${hubot_owner}" --description="${hubot_description}"
RUN rm /usr/src/${hubot_name}/node_modules/hubot-matteruser/src/matteruser.coffee
RUN wget https://github.com/loafoe/hubot-matteruser/blob/master/src/matteruser.js -P /usr/src/${hubot_name}/node_modules/hubot-matteruser/src/

but I get this error:
body-parser deprecated undefined extended: provide extended option node_modules/hubot/src/robot.js:445:21
[Tue Sep 11 2018 12:47:40 GMT+0000 (UTC)] ERROR Cannot load adapter matteruser - SyntaxError: Unexpected token <

Confirmed this is working.  I updated my Dockerfile to remove the .coffee and shove a copy of the .js file in the right place.

@loafoe what about the new release?
This repo is not usable for now without manual changes...
Last commit was 3 months ago, is someone supporting/taking care of this repo?

@centen @rgomez90 @mechanicjay @loleg @thomasbellois @bmaynard there ia new major release available which should fix the issue. As the new release is ES6 there might be some incompatibilities with some existing scripts. Please try the new release and report any issues. And apologies for the delay.


Multiple Accounts Breaks Integration

When I add multiple integrations it breaks with the error below. We have 2 charge points across 2 accounts.
Looking at the logs it looks like it could be as simple as the integration not generating a unique ID. It seems to work properly with a single account. I appreciate I'm using a beta version.
Happy to help with debugging if required.
Version of the custom_component
v0.3.0-beta2
Configuration
N/A
Describe the bug
When adding a second integration on a different account Home Assistant throws an error about duplicate sensors.
Debug log

2022-04-12 16:39:10 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform pod_point does not generate unique IDs. ID pod_point_8377_PSL-118776 already exists - ignoring binary_sensor.cable_status
2022-04-12 16:39:10 ERROR (MainThread) [homeassistant.components.sensor] Platform pod_point does not generate unique IDs. ID pod_point_8377_PSL-118776 already exists - ignoring sensor.pod_status
2022-04-12 16:39:10 ERROR (MainThread) [homeassistant.components.sensor] Platform pod_point does not generate unique IDs. ID pod_point_8377_PSL-118776_total_energy already exists - ignoring sensor.psl_118776_total_energy
2022-04-12 16:39:10 ERROR (MainThread) [homeassistant.components.sensor] Platform pod_point does not generate unique IDs. ID pod_point_8377_PSL-118776_total_energy_current_charge_energy already exists - ignoring sensor.psl_118776_current_energy
2022-04-12 16:39:10 ERROR (MainThread) [homeassistant.components.switch] Platform pod_point does not generate unique IDs. ID pod_point_8377_PSL-118776 already exists - ignoring switch.charging_allowed
2022-04-12 16:39:17 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.psl_118776_total_energy_2 (<class 'custom_components.pod_point.sensor.PodPointTotalEnergySensor'>) with state_class total_increasing has set last_reset. Setting last_reset for entities with state_class other than 'total' is not supported. Please update your configuration if state_class is manually configured, otherwise report it to the custom component author.
2022-04-12 16:39:17 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.psl_118776_current_energy_2 (<class 'custom_components.pod_point.sensor.PodPointCurrentEnergySensor'>) with state_class total_increasing has set last_reset. Setting last_reset for entities with state_class other than 'total' is not supported. Please update your configuration if state_class is manually configured, otherwise report it to the custom component author.

@adamlc I'll take a look into this over the coming days, it should be relatively easy to 'fix' multiple accounts. I did really concentrate much on it at the start as I only have one account

@adamlc I've just pushed 0.3.0-beta5 which should fix this for you. Are you able to update and let me know how you get on?


Update sap-solution-deploy-alternate.md

Improved title suggestion

@YoavDaniely - for SEO purposes, we're required to include "Azure Sentinel" in the title metadata.
What about:
Azure Sentinel SAP data connector expert configuration options, on-premises deployment and SAPControl log sources
Also a reminder that as a PM you can make changes directly to the internal repo :). Install the SpineEdit extension to make this simpler - https://chrome.google.com/webstore/detail/spineedit/llhlgkbkfdfcbjbfnnakfpgmemopbbnf
Feel free to ping me offline for help.

Ok with me 😊
From: Batami Gold @.>
Sent: Wednesday, July 14, 2021 12:25 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Yoav Daniely @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update sap-solution-deploy-alternate.md (#77885)
@YoavDanielyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYoavDaniely&data=04|01|yoav.daniely%40microsoft.com|e02b28f21fb0499abde508d946a94353|72f988bf86f141af91ab2d7cd011db47|1|0|637618515071302964|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=NBFxXBz4vqwVzi3K0fJoSg0eX6Wz%2FdD1zfOFcvx225Y%3D&reserved=0 - for SEO purposes, we're required to include "Azure Sentinel" in the title metadata.
What about:
Azure Sentinel SAP data connector expert configuration options, on-premises deployment and SAPControl log sources
Also a reminder that as a PM you can make changes directly to the internal repo :). Install the SpineEdit extension to make this simpler - https://chrome.google.com/webstore/detail/spineedit/llhlgkbkfdfcbjbfnnakfpgmemopbbnfhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Fspineedit%2Fllhlgkbkfdfcbjbfnnakfpgmemopbbnf&data=04|01|yoav.daniely%40microsoft.com|e02b28f21fb0499abde508d946a94353|72f988bf86f141af91ab2d7cd011db47|1|0|637618515071302964|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2FWdPj8dtz19CXr1tPd6cTKOKbwZXH0jDcnOnz9fb0%2Fc%3D&reserved=0
Feel free to ping me offline for help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F77885%23issuecomment-879739801&data=04|01|yoav.daniely%40microsoft.com|e02b28f21fb0499abde508d946a94353|72f988bf86f141af91ab2d7cd011db47|1|0|637618515071312959|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=NkmALKXEpldhBD1nuh%2B4mpWN%2FSwu%2FeKSqWHLwOSy4xA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPFDHWBBGW7IDW2XJIITYFTTXVJW7ANCNFSM472URUOQ&data=04|01|yoav.daniely%40microsoft.com|e02b28f21fb0499abde508d946a94353|72f988bf86f141af91ab2d7cd011db47|1|0|637618515071312959|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8nBZOiMpGYW36HdhXgu0%2FUS6geYzm5JiyfnIfATnVjE%3D&reserved=0.

@YoavDaniely - for SEO purposes, we're required to include "Azure Sentinel" in the title metadata.
What about:
Azure Sentinel SAP data connector expert configuration options, on-premises deployment and SAPControl log sources
Also a reminder that as a PM you can make changes directly to the internal repo :). Install the SpineEdit extension to make this simpler - https://chrome.google.com/webstore/detail/spineedit/llhlgkbkfdfcbjbfnnakfpgmemopbbnf
Feel free to ping me offline for help. The private repo means that you can sign off on your own PRs, getting the content out quicker.

to speed up the process, i merged this change in using a separate PR on the private repo. we can close this one.
#please-close

Can we please apply this? The title is still only about on-premises
From: Batami Gold @.>
Sent: Wednesday, July 14, 2021 12:32 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Yoav Daniely @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update sap-solution-deploy-alternate.md (#77885)
@YoavDanielyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYoavDaniely&data=04|01|yoav.daniely%40microsoft.com|5b3fc9bec1a54ea9988108d946aa2edd|72f988bf86f141af91ab2d7cd011db47|1|0|637618519015770643|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=GxPGU08amU%2FbEfzdxnFtw5nNp1nAGecDgU5%2FzJvFZTg%3D&reserved=0 - for SEO purposes, we're required to include "Azure Sentinel" in the title metadata.
What about:
Azure Sentinel SAP data connector expert configuration options, on-premises deployment and SAPControl log sources
Also a reminder that as a PM you can make changes directly to the internal repo :). Install the SpineEdit extension to make this simpler - https://chrome.google.com/webstore/detail/spineedit/llhlgkbkfdfcbjbfnnakfpgmemopbbnfhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Fspineedit%2Fllhlgkbkfdfcbjbfnnakfpgmemopbbnf&data=04|01|yoav.daniely%40microsoft.com|5b3fc9bec1a54ea9988108d946aa2edd|72f988bf86f141af91ab2d7cd011db47|1|0|637618519015780643|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eJK9npbyXDxpzuDOnT42ILdAuqLaovPrHFV9gAkBlUA%3D&reserved=0
Feel free to ping me offline for help. The private repo means that you can sign off on your own PRs, getting the content out quicker.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F77885%23issuecomment-879743854&data=04|01|yoav.daniely%40microsoft.com|5b3fc9bec1a54ea9988108d946aa2edd|72f988bf86f141af91ab2d7cd011db47|1|0|637618519015780643|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=GlRL6mbLHQonlHOSS%2B%2BcwroFftbGpGhWkcHgF4PAqg4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPFDHWA2HI6HIVA7UIACWLDTXVKPXANCNFSM472URUOQ&data=04|01|yoav.daniely%40microsoft.com|5b3fc9bec1a54ea9988108d946aa2edd|72f988bf86f141af91ab2d7cd011db47|1|0|637618519015790632|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=t3LWfi3zPW4vaztbDbw23ggEopthiSSp98uacATiQkc%3D&reserved=0.


Feature/proc refactor

Refactor code to allow for user-defined experiments, shorthand abbreviations, and concatenated time windows.
To-Do:

[ ] modify CMakeLists.txt to move *Proc/*Plot scripts to build directory.
[ ] in building, make *Plot scripts directly callable.

The other comment I will make is that it seems that grdstats.py cannot figure out on its own where to find gritas.x ... in order words it requires the user to place the path of gritas in the PATH ... perhaps this can be changed to do something like, if gritas,x is not in the path look for it in the same location as grdstats.py is ...

The other comment I will make is that it seems that grdstats.py cannot figure out on its own where to find gritas.x ... in order words it requires the user to place the path of gritas in the PATH ... perhaps this can be changed to do something like, if gritas,x is not in the path look for it in the same location as grdstats.py is ...

Path to gritas.x is now set via CMakeLists.txt by substituting for CMAKE_INSTALL_PREFIX in grit_util.py.in - see here.

When comparing two experiments, confidence intervals are now shown as filled regions rather than individual errors bars. See here.


TypeError: undefined is not an object (evaluating 'e.width')

I am trying to implement this plugin into my application. First of all thank you so much for providing this library, this is great!
However, while playing around I ran into the following issue:

export default function LocationOverviewMap () {
    const locations = [ {
        id: 1,
        lat: 48,
        lon: 9,
        title: 'Test 1 48 9',
    },
    {
        id: 2,
        lat: 49,
        lon: 9,
        title: 'Test 2 49 9',
    },
    {
        id: 3,
        lat: 48,
        lon: 10,
        title: 'Test 3 48 10',
    } ];

    const [ selectedLocation, setSelectedLocation ] = useState();

    return (
        <>

                <Map
                    token="my token ..."
                    isRotationEnabled={false}
                    isZoomEnabled={true}
                    showsCompass={0}
                    showsMapTypeControl={true}
                    showsUserLocation={true}
                    showsUserLocationControl={true}
                    showsPointsOfInterest={false}
                    mapType={0}
                >
                    {locations.map(location=> (<React.Fragment key={location.id}>
                        <Marker
                            latitude={location.lat}
                            longitude={location.lon}
                            color='#333'
                            glyphImage={{ 1: 'https://externalimageurl.com' }}
                            onSelect={()=> setSelectedLocation(location.id)}
                        />
                        <Annotation
                            latitude={location.lat}
                            longitude={location.lon}
                            title={location.title}
                            selected={selectedLocation === location.id}
                        />
                    </React.Fragment>))}
                </Map>

</>
    );
}

The error happens whenever I click on one of the markers and an Annotation is visible. Not sure if I am doing the implementation wrong or what is the issue here.
Also when playing around with the Storybook I often after some time get an error like this, not sure if this is similar to the first error in my error log and has something to do with this error:

For the sourcemap console.log it looks like the issue is described here: https://developer.apple.com/forums/thread/724005
Unfortunately I cannot upvote or comment as login to the forum is buggy for me. However, this does not look like it has anything to do with the error described.

Thank you for the bug report! The source map warning you have is caused by MapKit JS. I opened a bug report on Apple’s bug tracker ([FB13112020](https://openradar.appspot.com/radar?id=5598272181764096)). For the last bug you reported, I’m not sure what’s going on, and I opened a new issue (#43) to track it.
I could not reproduce the bug you are experiencing with your example. I tried to run the code in Storybook, but I don’t see errors when clicking on the annotations.

Are there some specific steps I need to follow to reproduce the bug?
The use of <Annotation> with no child looks suspicious. Have you tried to use a fragment instead, or a zero-size div instead?

Hi @Nicolapps,
thank you so much for your investigation. This was my very first implementation and currently I am using another implementation not facing this issue. Also honestly I agree that this implementation did not make so much sense.
Main reason to use the implementation like this was the fact that I wanted the default marker but with a callout, so as the marker doesn't have a callout I used the one of the annotation. As soon as we will allow custom Callouts, this will be obsolete anyhow.
In addition I tried to reproduce my own bug and for some reason wasn't able to do so. So I think we can close this ticket and keep #43 :)

Okay, thank you for the update!


DEX-208 add annotation to Encounter linkage plus patching of annotation from one encounter to another

Title says it all
Pull Request Overview
Annotation to Encounter linkage and patching added

Database Updates [OPTIONAL]
Annotation to encounter many to one mapping added
REST API Updates [OPTIONAL]
Annotation creation now requires an encounter_guid as well as an asset guid
Patch of Annotation added to change encounter
Pull Request Checklist

[x] Ensure that the PR is properly formatted

Example: All lint checks are passing

[x] Ensure that the PR is properly rebased

Example: The PR is rebased on develop (commit: <insert develop commit hash>)

[x] Ensure that the PR uses a consolidated database migration

Example: One database migration is proposed (revision <insert develop revision> -> <insert new revision>)

[x] Ensure that the PR is properly tested

Example: All automated tests are passing

[x] Ensure that the PR is properly covered

Example: The percentage of the code covered by tests has not decreased

[x] Ensure that the PR is properly sanitized

Example: No sensitive data or large content was added to this PR

[ ] Ensure that the PR is properly reviewed

/rebase


After upgrading to minitest 5.22.0 I get error status even if all test pass

Hello!
After upgrading to minitest 5.22.0 we are getting a failed status from bundle exec rake knapsack_pro:queue:minitest even if all test cases pass.
The failing jobs has the output Nothing ran for filter:  and the passing jobs does not.
My guess is that this change for empty_run! will generate a warning where it previously did not:
https://github.com/minitest/minitest/compare/v5.21.2...v5.22.0#diff-b43f1192f616004aa819abdb67ebe90528572c49ec805b9ad66ce45e1afce97bR177

I reproduced the error.
Minitest shows the Nothing ran for filter: error and exits with 1 as exit code (error exit code) when test files returned from the Queue API include pending tests or an empty test file with no test cases.
I use the knapsack_pro gem 6.0.4.
I prepared PRs to reproduce the problem for our team:

https://github.com/KnapsackPro/knapsack_pro-ruby/pull/241
https://github.com/KnapsackPro/rails-app-with-knapsack_pro/pull/57

The output:
➜  rails-app-with-knapsack_pro git:(debug-minitest-5.22.0) bin/knapsack_pro_queue_minitest
==================================================
Tests (mocked API response):
["test/minitest_spec_rails/shared_examples_test.rb"]
==================================================
D, [2024-02-06T19:06:10.015472 #90231] DEBUG -- : [knapsack_pro] Test suite time execution queue recording enabled.
Run options: --verbose --seed 50180

# Running:

Nothing ran for filter:
----------After Subset Queue Hook - run after subset of test suite----------==================================================
Tests (mocked API response):
["test/controllers/pending_controller_test.rb"]
==================================================
Run options: --verbose --seed 49280

# Running:

Nothing ran for filter:
----------After Subset Queue Hook - run after subset of test suite----------==================================================
Tests (mocked API response):
[]
==================================================
----------After Queue Hook - run after test suite----------W, [2024-02-06T19:06:10.056715 #90231]  WARN -- : [knapsack_pro] 2 test files were executed on this CI node but the recorded time was lost due to:
W, [2024-02-06T19:06:10.056732 #90231]  WARN -- : [knapsack_pro] 1. Please ensure you do not remove the contents of the .knapsack_pro directory between tests run.
W, [2024-02-06T19:06:10.056740 #90231]  WARN -- : [knapsack_pro] 2. Ensure you've added Knapsack::Adapters::RSpecAdapter.bind in your rails_helper.rb or spec_helper.rb. Please follow the installation guide again: https://knapsackpro.com/perma/ruby/installation-guide
W, [2024-02-06T19:06:10.056745 #90231]  WARN -- : [knapsack_pro] 3. Another potential reason for this warning is that all your tests are empty test files, pending tests, or they have syntax errors, and the time execution was not recorded for them.
D, [2024-02-06T19:06:10.143137 #90231] DEBUG -- : [knapsack_pro] POST http://api.knapsackpro.test:3000/v1/build_subsets
D, [2024-02-06T19:06:10.143159 #90231] DEBUG -- : [knapsack_pro] API request UUID: e055db31-5cde-4800-b6f5-1926cddbbcfd
D, [2024-02-06T19:06:10.143168 #90231] DEBUG -- : [knapsack_pro] API response:
D, [2024-02-06T19:06:10.143177 #90231] DEBUG -- : [knapsack_pro]
D, [2024-02-06T19:06:10.143190 #90231] DEBUG -- : [knapsack_pro] Saved time execution report on Knapsack Pro API server.
Coverage report generated for Unit Tests to /Users/artur/Documents/github/knapsack-pro/rails-app-with-knapsack_pro/coverage. 2 / 2 LOC (100.0%) covered.
SimpleCov failed with exit 1%
➜  rails-app-with-knapsack_pro git:(debug-minitest-5.22.0) echo $?
1

@davidwessman Could you use the old Minitest version until this is solved? Thanks.

I reported an issue in Minitest:

https://github.com/minitest/minitest/issues/985

The problem exists also for Knapsack Pro Regular Mode. API returns a pending test then 1 is set as an exit code.
Failing CI build: https://app.circleci.com/pipelines/github/KnapsackPro/knapsack_pro-ruby/1229/workflows/e15db5b4-01b3-4468-a9c4-63a1ca8d05ef/jobs/7496

https://github.com/minitest/minitest/compare/v5.22.0...v5.22.1
They seem to have fixed it in 5.22.1!

The issue was partially solved. More details here:  https://github.com/minitest/minitest/issues/985#issuecomment-1932480740

I confirm. The Minitest 5.22.2 version fixed the issue.


encode svg data into base64 to prevent some browsers to add html enti…

When we add the svg data to img.src, Firefox convert it to replace some characters with html entities and after it can load the image correctly !
Simple poc here : http://jsfiddle.net/3PfcC/
the solution is to convert svg into base64 string and ff can load it without error !
http://jsfiddle.net/0L6mrcqq/

Use base64 for binary data, for SVG try use encodeURIComponent.


Remove "beta" designation of opensearch-java

What do you want to do?

[ X ] Request a change to existing documentation

Tell us about your request. Provide a summary of the request and all versions that are affected.
The documentation here (https://opensearch.org/docs/1.2/clients/java/) suggests that opensearch-java is "beta."  In fact it is not in beta and it is the recommended client. the verbiage is misleading. This verbiage is written on a prior version page, but that doesn't change the fact that it is incorrect.
This is a request to remove that warning wherever it exists.

Hi @wbeckler: The beta designation is removed from OpenSearch 1.3 up: https://opensearch.org/docs/1.3/clients/java/.
Do you still need us to update the OpenSearch 1.2 documentation?

Yes, for all versions. The status of the client isn't dependent on the
server version , so every "beta" reference linked from old versions is
confusing and incorrect.
On Tue, Nov 22, 2022, 2:41 PM Naarcha-AWS @.***> wrote:

Hi @wbeckler https://github.com/wbeckler: The beta designation is
removed from OpenSearch 1.3 up:
https://opensearch.org/docs/1.3/clients/java/.
Do you still need us to update the OpenSearch 1.2 documentation?
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/documentation-website/issues/2011#issuecomment-1324156670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5PRLTH6OSHYMWUCY7CKB3WJUOXHANCNFSM6AAAAAASHLHPCI
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

@Naarcha-AWS - Can we resolve this by backporting the 1.3 version of this to 1.2-1.0? Thanks!


Implement dart class models instead using dynamic types and Maps

This is a breaking change that introduces Dart Class models to this package.
Using dynamic types are prone to bug and its easier to use Dart class models instead of Maps
I have done my best to refactor the required changes for this feature.
There aren't changes internally that would change the behavior of this package.
Please let me know if there are any changes required.
Thanks

Thanks!! @icodelifee
I've always wanted to make the same change.

Great PR, can we get this merged @hiennguyen92 ?

Would love to see this in the next version. @hiennguyen92

@hiennguyen92 please, do something or grant access to another contributor if you don't work on this package

@hiennguyen92 please, do something or grant access to another contributor if you don't work on this package

You always can fork the package and work on it yourself. What's the point to spam here?

thanks you.


YAML support

Hi, most people seem to prefer YAML for manually writing swagger specs. Would be nice if you could add support, so a lot more examples etc. can be invoked directly, without converting it manually to JSON etc :-)

This support is trivial by integrating a yaml parser. The only overhead for me is that an additional dependency would be required.
This request is added to TODO, thanks for asking.

I just finished the support of YAML, this issue is closed, reopen it once you found something wrong.


Confusing versioning

I've just installed app using link for .dmg from this page:

I expect it to be 0.2.0 version. When I check version in the app itself I see this version:

Taking into account message for 87a26a commit I expect to see column sizes preserved between app relaunches. But it seems not working.. On each launch they are default one. Maybe it's expected..

 I've even put it down to the README. Updates are now awful, sorry about that.
There are several disturbing issues:

webapp should be refreshed twice after release
desktop app (which consists of two parts: launcher script and webpage) can update only webpage
updates cannot be turned off on desktop
desktop app actually doesn't have any content and first install cannot be completed without Internet as it just loads the app page into launcher
the user has no notification on updates

Taken into account all of these issues, I'm working on updater module which will allow to install updates smoothly or allow to turn them off. This is not so easy because electron (desktop app wrapper which launches this app) doesn't provide built-in auto-update feature.
I expect the updater to be complete by this weekend.
Regarding column sizes: I've implemented saving but this will be in the next version, I haven't built the release with it yet.

Auto-update has landed so far. All issues I've mentioned have been resolved.
Please note: updates are downloaded as patches, so About box will always show the app version you have downloaded, and I don't know how to resolve this, because version shown in About box is stored in Info.plist file which is inaccessible to change by security settings. So to change it, we should re-download the app (which of course is not an option). I'll be think how to fix this in future but I consider it to be a minor issue. Correct running version is in Settings/Help section.

Thats nice! Thanks :+1:
About automatic updates.. Is it possible to disable them? When we are talking about security I don't want something critical to be updated at the background. It is the right place to inject malicious code.

Of course, there's a checkbox to disable.
Hm, having notifications with disabled updates makes sense. I'll replace this checkbox with select having 3 options:

auto check and install (will be default option)
don't check for updates at all
check but don't install

Sorry, I see a check box!

Yes, that make sense to see changes without automatic updates. A bit more secure in my opinion :)
P. S. I see also width is being saved properly now :+1:

Thanks, I've added this feature to new release schedule.


Bug with delete

Hi. I think that there is a bug with the library. The "Delete" checkbox column it isn't shown. Am I doing something wrong?

There's a default set on TabularInlinePaginated for can_delete=False. You can override that:
class YourTabularInline(TabularInlinePaginated):
    model = YourModel
    per_page = 25
    can_delete = True

Thanks! Didn't see in docs


Label issues

I came up with a technical issue and wanted to browse whether it was raised before, so as to avoid duplicance. However, the issue tracker is filled with "comments", "humor", and "到此一游" topics.
May I recommend the maintainer to kindly classify issues by "technical", "miscellaneous" etc. for the convenience of contributors?

Disclaimer: I understand that GitHub is used very differently in Chinese community. We should not blame some "not so GitHub" usages, if GitHub is the only place to do so.
Nevertheless, I still believe that many discussions in this repo fit way better elsewhere. This might be common for "popular overnight among beginners" projects. Hopefully there'll be some solution.

Totally agreed. Code of conduct and issue templates may also help people better contribute to this project. I would love to do this if @LingDong- feels good about it 😄

@liyishuai  Okay! I just spent some time to give every issue a tag :)
@antfu, sounds like a great idea! Thanks for your help!


chore: add extentions for suggest in composer.json

Description

add extentions for suggest

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

ext-xml is not listed in composer.json, but it is checked in CodeIgniter.php
I'm not sure xml is really needed.
CodeIgniter4/CodeIgniter.php at develop · codeigniter4/CodeIgniter4
https://github.com/codeigniter4/CodeIgniter4/blob/a1a635814eb5c254b5a31cbfde054ff54f0b30a3/system/CodeIgniter.php#L214-L220

I'm not sure xml is really needed.

Sorry, missed this comment before review.

what is "required" versus "suggested".

I think curl is suggested. It is needed only if you use CURLRequest.


Vagrant does not support Virtualbox 5.2+

Hi all, looks like this PR https://github.com/caskroom/homebrew-cask/pull/39790 breaks compatibility with the latest version of Vagrant.
https://www.vagrantup.com/docs/virtualbox/

The VirtualBox provider is compatible with VirtualBox versions 4.0.x, 4.1.x, 4.2.x, 4.3.x, 5.0.x, and 5.1.x.

Repro steps:
brew cask install vagrant
brew cask install virtualbox
vagrant up --provider=virtualbox

Note the compatibility error message. Reinstalling the last 5.1.x available fixes the issue.
brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/e8816187ae43f52b598f15f45b3453e22727ac99/Casks/virtualbox.rb

I'll leave this open for now so we don't get duplicate reports.
A new version of vagrant with support for virtualbox 5.2.0+ should be released next week.

https://github.com/caskroom/homebrew-cask/pull/40295