Assertion error on  import of CVAT 1.1 annotation file with tracks

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Steps to Reproduce (for bugs)

Upload valid annotations file in CVAT 1.1 format (since annotation files on which the issue reproducible is a part of internal datasets, please contact me by email in profile to share them for reproducing).
Tracks has no duplicated entries and all shapes are sequential by frame id
Wait for "Error: Request failed with status code 500. "AssertionError\n".."
Operating System and version: Ubuntu 20.04  (MacOS 13.1 in case of dev environment)
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
issue introduced by 279f01b53bb50bd7ac64e32ed09705f96e224d34
Not reproducible on previous commit dde9f610df5e57ead2208b62a7799a2cecaa4bfa (if to remove checks for zip archive in cvat-core/src/annotations.ts)
cvat_worker_default log:

Traceback (most recent call last):
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/.env/lib/python3.9/site-packages/rq/worker.py", line 936, in perform_job
    rv = job.perform()
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/.env/lib/python3.9/site-packages/rq/job.py", line 684, in perform
    self._result = self._execute()
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/.env/lib/python3.9/site-packages/rq/job.py", line 690, in _execute
    return self.func(*self.args, **self.kwargs)
  File "/Users/mikhailtreskin/.pyenv/versions/3.9.0/lib/python3.9/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/task.py", line 784, in import_task_annotations
    task.import_annotations(f, importer, conv_mask_to_poly=conv_mask_to_poly)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/task.py", line 669, in import_annotations
    self.create(task_data.data.serialize())
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/task.py", line 626, in create
    self._patch_data(data, PatchAction.CREATE)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/task.py", line 616, in _patch_data
    self._merge_data(_data, jobs[jid]["start"], self.db_task.overlap)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/task.py", line 620, in _merge_data
    annotation_manager.merge(data, start_frame, overlap)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/annotation.py", line 158, in merge
    tracks.merge(data.tracks, start_frame, overlap)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/annotation.py", line 241, in merge
    cost_matrix[i][j] = 1 - self._calc_objects_similarity(
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/annotation.py", line 413, in _calc_objects_similarity
    obj0_shapes = TrackManager.get_interpolated_shapes(obj0, start_frame, end_frame)
  File "/Users/mikhailtreskin/repos/ml2providence/thirdparty/cvat/cvat/apps/dataset_manager/annotation.py", line 751, in get_interpolated_shapes
    assert shape["frame"] > prev_shape["frame"]
AssertionError

Same issue here! Hope it gets resolved soon.

I was able to reproduce this error by uploading COCO formatted labels (no tracks) and running the openvino Person re-ID function on it.

We've hit that multiple times.

Related: https://github.com/cvat-ai/cvat/issues/6779


use pinned SHA of GitHub Actions instead of branch name or version

Description
In GitHub Actions (GA) there is a security consideration related to 3rd party GA, so, GitHub recommends using Pinned SHA of the 3rd party GA instead of using branch name or version of GA.
There are already side projects that ensure that like the following:

https://michaelheap.com/ensure-github-actions-pinned-sha
https://michaelheap.com/improve-your-github-actions-security/

This is done.


Working Group admin

Description
These are the follow up actions to the Sep 23 working group meeitng
DOD

[x] Molly to create a shared space where working group team members can populate an agenda
[ ] Add Karla's replacement to attendance list
[x] Matt to schedule 30 min recurring monthly meeting until Dec 2021, share link to agenda with invitation for members to drive future agendas with topics they wish to cover. If barriers to technology, email Molly with agenda ideas.

cc: @arielleandrews @lmullane

I have created blank agendas in miro @m-prodan https://miro.com/app/board/o9J_lwDMCMs=/

Thanks for tracking this , @mpilchar

Meetings have been scheduled for third thursday of a given month at 3PM until the end of the year. I've included the link to the Miro board, but I also advised that we would send out a reminder ahead of time. I'll set calendar reminders for myself for the Monday of our WG meeting week.

Also updated our membership list on the WG TOR - is there a separate space for an attendance list somewhere, or can we consider this one closed @mpilchar?


Add Command Line Support

Add Command Line Support
Similar as https://github.com/Clever/csvlint

@kwent, the library csvlint.rb already shops with a command line utility (see the bin directory). It is installed for you when you follow the installation directions in README.md. Is that what you are looking for?

@adamc00 Oh nice i did not see that ! Well maybe you should complete the README and indicate this. With the --help. Params and an example how to use it ?

Hi @kwent, I'm not actually a maintainer of this project just a fellow user. Why not fork this project, update README.md, and submit a pull request to include your documentation improvement? The project team here have applied my own pull requests so I'm sure they'd appreciate one from you.

Oh, yes, a section on command-line use would be great! We'll add it to our list, but if anyone fancies sending in a PR, that would be great. We're not getting much time on this at the moment.

I'll have a go at this now


DO NOT MERGE: Test PHP MacOS build failure

Test reverting #18115 in order to fix #18423

The real fix is in #18438 now


Update Chrome style in user guide; Support dark mode

Close enough. Part of https://github.com/fregante/webext-permission-toggle/issues/62

Full page


Jar file won't open

I try opening the jar file but it doesn't do anything.

@CoffeeTheProto Have you tried running it from a command line?

I'm getting this bug also. What's a command line?

Disclaimer:
Only run these commands with code you trust, you might end up installing a virus if it's random code you found on the internet.
Assuming you downloaded this to your Downloads folder
You can open your terminal and type
cd Downloads
java -jar cmpdl-2.3.0.jar

Change the Downloads and cmpdl-2.3.0.jar as needed if if it's in another directory or the version changes.

I tried it and it did not work, it says: Error: Could not find or load main class com.github.franckyi.cmpdl.CMPDL

@peterodavies27atgmailcom Which version of Java are you using? CMPDL is only compatible with Java 8.

openjdk version "1.8.0_272"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_272-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.272-b10, mixed mode)

AdoptOpenJDK doesn't include JavaFX, which CMPDL uses for the UI. You have to install OpenJFX (or build it if it's not available for your system). See https://stackoverflow.com/questions/18547362/javafx-and-openjdk

gluonhq.com/products/javafx
Do I install JavaFX Windows SDK or JavaFX Windows jmods or something else?

Gluon only distributes JavaFX starting from version 11, and you need version 8 to run CMPDL.
Honestly, since you're using Windows, I think the easiest way to fix your issue would be to use the Oracle JRE instead of AdoptOpenJDK.
You can download it here https://java.com/en/download/manual.jsp

ok

Acctually you can also use newer versions of Java (AdoptOpenJDK is fine if you also install openjfx (https://openjfx.io/)) and with it JavaFX .
The command you need to run it from command line would be:
java --module-path "%JAVAFX_HOME%\lib" --add-modules javafx.controls,javafx.fxml -jar cmpdl-2.3.0.jar
You have to replace %JAVAFX_HOME% with the file path to where you have JavaFX installed to. For example: C:\Program Files\Java\JavaFX\javafx-sdk-15.0.1
Or more advanced: Create a environment variable with that name and the file path.

Hello, it seems like i have something similar happening.
Error: Could not find or load main class com.github.franckyi.cmpdl.CMPDL
Caused by: java.lang.NoClassDefFoundError: javafx/application/Application
is there a way to fix this?

I've tried what you said but i'm getting the error "Error occurred during initialization of boot layer
java.lang.LayerInstantiationException: Package jdk.internal.jimage in both module jrt.fs and module java.base"

This application is only compatible with Java 8

Changed my default jre version to java-8-openjdk/jre and still get Error: Could not find or load main class com.github.franckyi.cmpdl.CMPDL as an error, before it was
Error occurred during initialization of boot layer java.lang.LayerInstantiationException: Package jdk.internal.jimage in both module jrt.fs and module java.base

I've tried what you said but i'm getting the error "Error occurred during initialization of boot layer java.lang.LayerInstantiationException: Package jdk.internal.jimage in both module jrt.fs and module java.base"

Okay for me this works even with java 20 (@skyecodes).
To diagnose this we need more info about your system.
We need:

OS (Windows 10/11, Linux (what distro), ...)
Architecture (x86, x86_64, arm64, ...)
Java Version (with install path)
JavaFX Version (with install path)
A screenshot of the window telling you about the error


chore: refine README.kr.md

Summary
Refine Korean README Translation.

Update some sections that differ from the README.md.
Refine some slightly awkward sentences in the Korean README.md.
Update the Japanese link to the default link.

Tickets

closes #3889

Test Plan

I’ll suggest a native Korean speaker as a reviewer, if that’s okay with you.

I’ll suggest a native Korean speaker as a reviewer, if that’s okay with you.

Yeah. Please :)

@StationSoen can you apply the suggestions?

@ematipico Sorry for the delay. I’ve applied all the feedback since it was very helpful.


test coverage

this is a placeholder issue for all of our future testing needs 🌈 ⭐
We should make stories for:

[x] installing cypress for e2e tests [#325]
[x] writing e2e tests [#326]
[x] circle ci integration [#296]
[ ] unit tests???

this has been split up into smaller issues:

#296
#325
#326

unit testing can be considered after the refactor :)


Property name "location" not allow by the schema arm-template (schema)

This page contains a recommendation to use a location parameter with a default value of "[resourceGroup().location]". However in visual studio code, when I include this in a template using the schema version 2019-04-01, I get a warning for the location parameter "Property name is not allowed by the schema arm-template (schema)". I could change the name, but if this is a genuine restriction of the arm-template schema, then this page should be updated. Or I might have it wrong and perhaps it's a problem with the VS Code addin for arm-templates that I'm using, though with other schema versions the location parameter isn't a problem. Thanks.

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

ID: c1558fc8-7d7b-6d02-113d-650a87295de6
Version Independent ID: cfb3afb4-bbfc-05da-3faa-02266c8ea270
Content: Best practices for templates - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/template-best-practices.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Apologies, I missed something and the error I was seeing wasn't that the location wasn't an allowed parameter name. Sorry.


[bfgroup-lyra] Update to 1.3

Fix related issue https://github.com/microsoft/vcpkg/issues/10435
Update bfgroup-lyra to latest release revision 1.3
bfgroup-lyra doesn't contain any features need test locally.

/azp run

/azp run

/azp run

/azp run


Eigen trunk appears broken

Eigen trunk seems to be broken for this minimal example:
#include <Eigen/Dense>

You can check this by switching from stable to trunk.  Adding the path listed here in the compiler command line doesn't help either.
Thanks for the tool!

Hi! Thanks for noticing this. Something went wrong and we added trunk to the UI but not to the backend! I'll fix this right now. :)

Rockstar - thanks!

This should now be fixed. 👍


URL build

https://github.com/deannabosschert/web-app-from-scratch-1920/blob/2440c2af26dd613ec443be412ecfd4b8493c3a3a/docs/js/app.js#L13
You could try constructing this api with template literals and even a URL object instance.
This would improve readability and usability

Had it already fixed in the branch I was working in back then hahaha, but it's in template literals on the master branch aswell now. I'll ask you about the URL object instance next week  👀


Added bower support

Added support for bower. Since I am not the owner of this project there is a step that you need to do @axel-zarate because i don't want to maintain this project and have to keep it up to date in bower as well.
Take a look at this page for further information on pushing to bower. Basically these are the steps you'll need to do:

$ npm install -g bower
$ bower register js-custom-select git@github.com:axel-zarate/js-custom-select.git <-- This just points at master but you'll want to start tagging your code and then push the tags.

This looks great, can we get this merged?


IGNIETFERRO-2059: Fix use-after-free error in the TDqExecuter

Changelog entry
Fix use-after-free error caused by constructing an input stream over a temporary string object
Changelog category

Bugfix

@vitstn please, take a look


aquery action attrs should be strongly typed

When using aquery from bxl, and trying to get the command line args for a cxx_compile action, it’s a value like [cl.exe, -c, foo.cpp, @argsfile, -o, foo.obj].  Unfortunately, it’s quite literally a string, so to get it as a Starlark list you have to do the very awkward
cmd = cmd.strip(“[]”).split(“,”)
cmd = list(map(lambda x: x.strip(), cmd))

which is sure to break at the worst possible time.  Is it possible to make the action_attr binding support more types than just raw strings?

Yup, aquery attrs are all strings currently, both in BXL and CLI. I can work on strongly typing (most of) them, but it may be a week or two

Great!  No rush on my end as the above hack works for all of the use cases I've tested so far.  Just writing stuff down as soon as I come across them so i don't lose track of them.  Thanks :)


[Request] Ukraine NFT

I searched DuckDuckGo "ukraine nft" because I was sure someone had done something but surprisingly as much as I was expecting NFTs about the Ukraine attack I was much more surprised to find people using NFTs to raise money to help Ukraine. Looks like Lana Rhoades is back at it again by saying people cannot discuss her NFT scam while Ukraine thing is going on https://www.tweaktown.com/news/84780/famous-porn-star-compares-her-nft-scam-to-russia-invading-ukraine/index.html
PS Also will there be a new way to discuss additions for web3isgoinggreat? GitHub is a coding website and I would prefer for my issues here to be software related, thanks.

Yeah, should probably add some. While there seem to be some NFT projects and DAO fundraisers that are genuinely sending some proceeds to Ukraine, it also seems like a wave of scammers have come in as well.
Regarding off-GH discussions, I hadn't really thought about it. Is there another system you had in mind as being particularly well-suited?

@molly Personally, I would just add a forum board to web3isgoinggreat.com but I think most people are looking for some type of social media platform. guilded.gg is an up and coming alternative to Discord, could try that out?

I've added an entry on Ukraine-related grifts to https://web3isgoinggreat.com/?id=2022-02-26-0
As for the discussion thing, I'll think on it. I definitely do not plan to add a forum or commenting to W3IGG—I don't have the time, energy, or desire to moderate such a thing.


Pressing Esc in REPL wipes call stack

In particular, this means that using traceback() after an error doesn't work.
Expected behaviour:
> lm(y ~ x, foo)
Error in is.data.frame(data) : object 'foo' not found
> traceback()
6: is.data.frame(data)
5: model.frame.default(formula = y ~ x, data = foo, drop.unused.levels = TRUE)
4: stats::model.frame(formula = y ~ x, data = foo, drop.unused.levels = TRUE)
3: eval(expr, envir, enclos)
2: eval(mf, parent.frame())
1: lm(y ~ x, foo)

Actual behaviour:
> lm(y ~ x, foo)
Error in is.data.frame(data) : object 'foo' not found

   ** press Esc here **

> traceback()
No traceback available

This is side effect of fixing #1066 as ESC now means 'Cancel all`.


[AI-4451] Add Milvus integration

What does this PR do?

Motivation

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Already done in https://github.com/DataDog/dd-analytics/pull/37568

Created Jira card for Docs Team editorial review.


labelFontSize doesn't work

labelFontSize isn't working.
Example 1: labelFontSize 7
        <RNChart style={styles.chart}
          chartData={chartData}
          verticalGridStep={5}
          xLabels={xLabels}
          labelFontSize={7}>
        </RNChart>

Example 2: labelFontSize 12
        <RNChart style={styles.chart}
          chartData={chartData}
          verticalGridStep={5}
          xLabels={xLabels}
          labelFontSize={12}>
        </RNChart>

Regardless of the labelFontSize setting, the font size remains the same.

@johnnyoshika, did you ever find a workaround for this?

@nickmaxwell10, unfortunately, no.

Will be looking into this.

@johnnyoshika can you send me the chart data and styles so I can easily test this?

@tomauty: this was from 4 months ago, so I'm not sure if I still have it, but I'll see if I can dig it up.  :-)
Thanks for following up though.

Hah, yeah, thought it'd be worth a shot ;)

the same issue, any idea now?

Should have a fix this week

v0.1.7 :+1:


Installing from pypi does not work

Summary
pip install github from pypi does not work
Reproduction Steps
Just installing the package form pypi will not work.
I am using python 3.10.5
pip install github

Minimal Reproducible Code
pip install github

### Expected Results

I expected the pip install not to fail.

### Actual Results

pip install github
Collecting github
Using cached github-1.2.4.tar.gz (14 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [18 lines of output]
Traceback (most recent call last):
File "/home/andrej/.pyenv/versions/3.10.5/envs/curated/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in
main()
File "/home/andrej/.pyenv/versions/3.10.5/envs/curated/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/andrej/.pyenv/versions/3.10.5/envs/curated/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-825ng7yu/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel
return self._get_build_requires(
File "/tmp/pip-build-env-825ng7yu/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 159, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-825ng7yu/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 281, in run_setup
super(_BuildMetaLegacyBackend,
File "/tmp/pip-build-env-825ng7yu/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 174, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 5, in
with open('requirements.txt') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

### Checklist

- [X] I have searched the open issues for duplicates.
- [X] I have shown the entire traceback, if possible.
- [X] I have removed my token from display, if visible.

### Additional Context

_No response_

Hello. Sorry for the issue.
I'll try to figure it out as soon as possible. You can install the package using
py -m pip install -U git+https://github.com/VarMonke/Github-Api-Wrapper if Windows
python3 -m pip install -U git+https://github.com/VarMonke/Github-Api-Wrapper OR python3.x -m pip install -U git+https://github.com/VarMonke/Github-Api-Wrapper (x being the minor python version) if Linux/Unix

No worries.
I have helped myself by adding the package with the git format to my requirements.txt file:
git+https://github.com/VarMonke/Github-Api-Wrapper@72df28268493ac03fb221f2e84e6ca752d3027f2

No blocker there. Just thought you want to know.

Yep, Thank you!


Issues encountered in scaling recent DCR on Piz Daint

This list is mostly for myself, to document issues encountered on recent scaling runs on Piz Daint. I will follow up separately for specific issues but hopefully this will help jog my memory so I know what to reproduce and how.
Note that these are symptoms, not every symptom is necessarily a separate runtime bug (or a runtime bug at all; there could be issues in different parts of the system).

[x] ~stencil/circuit/pennant: nodcr_noidx crashes with bad_alloc https://github.com/StanfordLegion/legion/issues/1049~
[x] ~stencil/circuit: dcr_noidx freezes at >= 512 nodes (note: not fixed by -lg:window)~
[x] ~stencil: dcr_idx gets wrong answer with >= 2 nodes unless you run with -lg:no_fence_elision~
[x] ~circuit: dcr_noidx gets (non-deterministic?) uninitialized read-only field error with >= 4 nodes (worked around by blanket fill on top-level regions)~
[ ] pennant: dcr_noidx is 10x slower than dcr_idx (probably an application or mapper issue)
[x] ~soleil: dcr_noidx freezes at 2 nodes when -lg:sched -1 is used (maybe Legion should assert if this value is passed?)~
[x] ~soleil: dcr_noidx freezes at 16 nodes unless -lg:window (with a sufficiently large value) is used~
[ ] soleil: I've been seeing a number of distinct symptoms, depending on configuration and node count:

[ ] hit_dom in base configuration freezes at 1 (?) node (or at least 2)
[ ] hit_dom in stag-200 with 1020/204 freezes at 16 nodes (at start of run)
[x] ~hit_dom in stag-200 with 780/156 has a variety of symptoms:~

[x] ~non-deterministic crashes (related to distributed collectables)~
[x] ~non-deterministic freezes (sometimes at start, sometimes after iterations 199 or 399 (i.e., immediately before DOM))~
[x] ~deterministic shutdown hang starting at 16 nodes~

[ ] REALM_NETWORKS=gasnetex crash: https://github.com/StanfordLegion/legion/issues/1040
[ ] LLVM 6 performance regression: https://github.com/StanfordLegion/legion/issues/1041

There has been a fix applied to a hang in the future all reduce collective now, so all the tests that hung before need to be rerun.

stencil: dcr_idx gets wrong answer with >= 2 nodes unless you run with -lg:no_fence_elision

Please provide a debug binary and command line to reproduce this one on sapling.

There has been a fix applied to a hang in the future all reduce collective now, so all the tests that hung before need to be rerun.

This has fixed the stencil/circuit freeze at 512 nodes.

I have not been able to reproduce any of the Soleil symptoms at the 780/156 problem size. I'm running some more tests now to rule out the distributed collectable issue, but the shutdown hang was quite deterministic before, so I'm going to consider that gone.
I am still seeing freezes at the 1020/204 problem size. It may be that this genuinely is a memory issue. I'll need to investigate more to be sure.

stencil: dcr_idx gets wrong answer with >= 2 nodes

This is fixed

I am still seeing freezes at the 1020/204 problem size. It may be that this genuinely is a memory issue

Why do you think a memory issue would  produce a hang?

stencil: dcr_idx gets wrong answer with >= 2 nodes

This is fixed

Confirmed.

I am still seeing freezes at the 1020/204 problem size. It may be that this genuinely is a memory issue

Why do you think a memory issue would produce a hang?

No real reason except that the hang is problem size dependent and behavior can get finicky as you approach the node's memory limit, even if swap is disabled.

You also owe me a reproducer for the program that was giving you a read-only uninitialized error for sub-operations inside of a virtually mapped task in a control-replicated context.

No real reason except that the hang is problem size dependent and behavior can get finicky as you approach the node's memory limit, even if swap is disabled.

Ok, yes, this does make sense if the runtime grinds to halt because malloc/free operations that it needs start going into swap space. Would be good to confirm that is occurring.

Also the std::bad_alloc is a duplicate of #1049 when assertions are off for release mode.

Binary and command line to replicate the uninitialized data issue:
/scratch2/eslaught/regent-index-launch-sc21/language/circuit.run1_debug_uninit

mpirun -n 2 -npernode 1 -bind-to none -x LD_LIBRARY_PATH=$PWD ./circuit.noidx -npp 500 -wpp 2000 -l 50 -p $(( 3 * 10 )) -pps 10 -prune 10 -hl:sched 1024 -ll:gpu 1 -ll:util 2 -ll:bgwork 2 -ll:csize 15000 -ll:fsize 15000 -ll:zsize 2048 -ll:rsize 512 -ll:gsize 0 -dm:replicate 1 -dm:same_address_space

Should be compatible with any recent control_replication.

@elliottslaughter Pull the most recent control replication. The uninitialized read-only error should be gone. You actually found the very first bug anyone has ever reported with replicated equivalence sets.
What hangs are still reproducible at this point?

There's the issue with -lg:sched -1, which I'm not sure is a valid option in the first place. We might solve that one by just disallowing values <= 0 on that command line flag (unless you've changed your mind about this being a valid value).
There are also the DOM freezes with the larger problem size, where I'm not sure if they're "real" or related to memory pressure.

Let me try again to see if I can get direct access to Piz Daint nodes. Their user guide claims that it's still possible, so maybe I just am not doing something right. If I can, I'll watch during a run and see if it's actually running close to the memory limit on the machine.

Ok, I think we should try -lg:sched -1 and see if it reproduces after the other hang fix. Let me know if you find anything else that seems suspicious.

I don't seem to be seeing a freeze related to the presence of -lg:sched -1. I am still seeing a freeze if I fail to increase the -lg:window parameter. Was that something you wanted to address? I can add it if you want.

I am still seeing a freeze if I fail to increase the -lg:window parameter. Was that something you wanted to address? I can add it if you want.

Yes, I still want to address it, but you don't need to look into it. I understand it. It should go away if you run with -lg:no_physical_tracing. Knowing how to reproduce it for when I push a fix would be good so we can test that it has been fixed.

I don't think so, and the important (Realm/Regent) bugs are in separate issues. I'll go ahead and close this.


启动报错

[Singleton] An instance of NetCore is needed in the scene, so '(singleton) NetCore (UnityEngine.GameObject)' was created with DontDestroyOnLoad.
UnityEngine.Debug:Log(Object)
NetProto.Singleton`1:get_Instance() (at Assets/Scripts/NetLib/Singleton.cs:51)
Sample.Main:Start() (at Assets/Scripts/NetLib/Sample/Main.cs:18)
System.Net.Sockets.SocketException: 使用了与请求的协议不兼容的地址。
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP, Boolean requireSocketPolicy) [0x00000] in :0
at System.Net.Sockets.Socket+Worker.Connect () [0x00000] in :0
UnityEngine.Debug:Log(Object)
NetCore:ConnectCallback(IAsyncResult) (at Assets/Scripts/NetLib/NetCore.cs:180)
System.Net.Sockets.Worker:Connect()

https://github.com/en/libunity/blob/master/Sample/Main.cs#L10


Decide on Message Scoping

Decide to have either have an explicit scoping of messages to belong to an organization or to implicit inheriting the belonging by the request

explicitly scoped with #1966


Why you don't use just npm install -g yarn ?

Hi @pahaz,
npm install -g yarn might be an easier way for someone.
For me, This guide just one option. 😂
The ways to config npm, yarn are hackable.
So this the ways Config via Homebrew


Bad News

I found your awesome repo today and decided I was going to whip up a FUSE adapter for it but then I saw this: https://9to5google.com/2020/11/11/google-docs-storage/
too bad :(
Maybe some other google service exists that will not be affected.

looks like google keep and google sites are not affected


Loggly Error (403): Forbidden

Getting this error at yarn start, is there any suggestions?
Error: Loggly Error (403): Forbidden
at Request._callback (/opt/ak/node_modules/node-loggly-bulk/lib/loggly/common.js:203:31)
at Request.self.callback (/opt/ak/node_modules/request/request.js:185:22)
at Request.emit (events.js:315:20)
at Request.EventEmitter.emit (domain.js:485:12)
at Request. (/opt/ak/node_modules/request/request.js:1154:10)
at Request.emit (events.js:315:20)
at Request.EventEmitter.emit (domain.js:485:12)
at IncomingMessage. (/opt/ak/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)

If you do not set the variable LOGGLY_KEY, it will skip this section of the code.


nixos/swap: fix creation on BTRFS and refactor assertions

Description of changes

Fixes #156829

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

.rw------- 8.6G root 30 Nov 08:23 /swapfile

Filename				Type		Size		Used		Priority
/swapfile                               file		8388604		0		-2

Works on my machine, Thank you.

@ofborg build nixosTests.swap-file-btrfs

@ofborg build nixosTests.swap-partition

It seems like it's in a good shape, anything left over before merging? Maybe having a backward compat release note in 23.05 ?

@RaitoBezarius

It seems like it's in a good shape, anything left over before merging? Maybe having a backward compat release note in 23.05 ?

The related code would only be trigger when the swapfile size is different than the size specified in config.

If user uses BTRFS, the service fails on master, but succeeds after this PR.
If user uses non-COW filesystems like EXT4, the service succeeds on master, and still succeeds after this PR, just with an extra chattr, whose result is ignored.

I consider this a fix rather than a breaking change.

@RaitoBezarius

It seems like it's in a good shape, anything left over before merging? Maybe having a backward compat release note in 23.05 ?

The related code would only be triggered when the swapfile size is different than the size specified in the config.

If user uses BTRFS, the service fails on master, but succeeds after this PR.
If user uses non-COW filesystems like EXT4, the service succeeds on master, and still succeeds after this PR, just with an extra chattr, whose result is ignored.

I consider this a fix rather than a breaking change.

You convinced me!

@Artturin are you okay with merging this?

Rebased and added maintainers for the new test.

gives me swapon: /swapfile: skipping - it appears to have holes. on zfs but it's not a regression

@ofborg test swap-file-btrfs

gives me swapon: /swapfile: skipping - it appears to have holes. on zfs but it's not a regression

AFAIK, ZFS doesn't support swapfile, but swap volume could be used instead. https://wiki.archlinux.org/title/ZFS#Swap_volume


AR & dependencies

Description
Added AR into project, no links to page yet, just an app named ARentry.dart to run the AR models in assets/chicken something
pls check if it works first
Jira Ticket

https://garrysjh.atlassian.net/browse/DIP-[your ticket number]

TODO:
Add button for productID = 13 that links to AR page
Cleanup AR page

Sounds done, test please for item (waterbottle)
ATM only web retrieving of AR object works, not sure if local does


Provide both asynchronous and synchronous @DBStore functions.

@DBStore should be both synchronous and asynchronous (eg via an additional parameter (sync) which would be by default false and could be set to true)

Resolved via https://github.com/panossot/jboss-automated-metrics/commit/9b1a9ee8f778a7b68343efe492d76e1a10539dd2 .
Addition of parameter sync : @DBStore(sync=true)
Closing this issue ...


[Feature]: insertHtml command

I'm submitting a

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Enhancement
[x] Feature request
[x] Documentation issue or request

Description
Is it possible to add a command that allow us to insert some content as HTML ?
If not, is it possible to have some documentation to write this new command ?
Version Information
ngx-editor: 8.0.0-beta.7
angular: 9.1.13

Browser

All browsers

Like HTML snippet as code block or could you elaborate a little?

For example I want to add via a button the character Ψ. So I used insertText("Ψ") but insertText insert directly the text.

The editor uses ProseMirror underneath for content editing. ProseMirror documents are not HTML. So It is not possible to insert random HTML in it.
You can try inserting unicode in your case may be
this.editor.commands.insertText("\u03A8").exec() // will insert `Ψ`

Else you might need to create custom schema and implement nodeviews for specific needs.

You can do this to insertHTML.
import { DOMParser } from "prosemirror-model";

const { state, dispatch } = this.editor.view;
const { selection, schema, tr } = state;

const element = document.createElement("div");
element.innerHTML = html;
const slice = DOMParser.fromSchema(schema).parseSlice(element);

const transaction = tr.insert(selection.anchor, slice.content);
dispatch(transaction);

but for the above requirement It will always insert the parsed value. Ψ will be a text inside the doc.

Added in v8.


position relative and position absolute

Describe the Features
It is necessary to add a component that will allow elements to be superimposed on each other.

For example: Add text on top of the picture, and the text can be moved using standard CSS properties.

All CSS are already supported for standard components, including "position"


AngularLocalizaionAspNetCore Solution does not build in VS2017 Enterprise . Can you help me?

Severity	Code	Description	Project	File	Line	Suppression State
Error	TS2688	Build:Cannot find type definition file for 'node'.	AngularLocalizationAspNetCore	C:\Users\pjlay\Documents\Visual Studio 2017\Projects\Angular2LocalizationAspNetCore-master\src\AngularLocalizationAspNetCore\tsc	1

You might need to install nodejs. The nodejs deployed with VS2017 is an old one. You need to configure VS to use the nodejs installed on the path
Then try from the commnad line to see if VS is configured correctly or if your missing something.

npm install
npm run build-production
dotnet restore
dotnet build

Greetings Damien


How to structure b7a code guide mention non-existant -s flag

Description:
How to structure Ballerina code guide mention -s flag for run (ballerina run -s file.bal) that's not there in Ballerina 0.970.1
$ ballerina run -s hello_service.bal
ballerina: unknown flag '-s'
Run 'ballerina help' for usage.

The "-s" flag is removed from How to Structure Ballerina Code, hence closing this issue


[release 9.0.1xx] VerifyVersionFile Failing Due to Mismatched Version

Regression caused by https://github.com/dotnet/sdk/pull/44289
The SourceBuiltArtifactsTests.VerifyVersionFile is failing in all 9.0.1xx builds because the test expects the SDK version to be 9.0.100-rtm.24517.1 but it is 9.0.100.
The expected version is pulled from the source-built SDK, and the actual version is pulled from the private-source-built artifacts. This means that the SDK version is still 9.0.100-rtm.24517.1.
cc @marcpopMSFT

The expected SDK version is being pulled as the unique, non-stable version.
I think that to fix this we can either 1) adjust the DetermineSourceBuildSdkVersion to be the non-stable version (this would lead to a mismatch in artifact versions between the source-built SDK and the Private.SourceBuilt.Artifacts), 2) adjust the test to use the stable version if we are using an rtm version for the non-stable SDK version, or 3) something I'm not thinking of.
cc @dotnet/source-build

The issue is with version in PSB archive, it is 9.0.100


Adds configuration to ignore revs in blame

There have been a couple commits that touched most of the files in the
repository, especially when applying the Black formatter. The
.git-blame-rev-ignore file tells git blame to ignore those commits when
computing the blame for a file.
I'm not sure if there are other commits that should be added to this file as well. I ran into a few cases where I was trying to understand context for a change and had to step through the Black formatting commits, so I hope this will be more broadly useful.
According to GitHub's documentation, this file should also work in the GitHub Web UI for blames.

Sure thing @jrbourbeau happy to add those extra commits!

@jrbourbeau I looked through all the commits back to 2017 that changed more than 10 files, I think I got the big ones here.


merge from arlac77/template-cli-app,arlac77/template-github

package.json

chore(package): add ^2.3.1 remove ^2.3.0 (devDependencies.rollup)
chore(package): add ^11.0.2 (devDependencies.@rollup/plugin-commonjs)

rollup.config.mjs

chore(rollup): copy from template

:tada: This PR is included in version 2.1.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


I can understand attributes 'root' and 'depth',but how to calculate 'lft' and 'rgt'? thx

You do not, the extension does it for you, this is the benefit of using the extension.


Handle Browser Back and Forward Buttons with Custom Page Transition

I have a hook to handle link button clicks. When a link button is clicked, a page transition is shown and animated. After the animation completes, the location is set to the target address.
However, I have a question regarding handling the browser's back and forward buttons. When the back button is clicked, I want to:
Prevent the default event that navigates to the previous page.
Set the target address.
Animate the page transition.
After the animation completes, set the location to the target address.
Could you please provide an solution for this?

Could you please share how you're implementing delayed transitions? Are you using Suspense?


bump go-diskfs

Fixes cdrom provider leaving block devices opened, see https://github.com/diskfs/go-diskfs/pull/166 for more info

cc @davidcassany

Thanks much! Probably I should try to make a PR with the providers package refactor upstream. Have not done it as this code is based on top of the azure PR and requires some love to remove it again 😒 . I guess azure support won't ever be merged at this stage.

Thanks much! Probably I should try to make a PR with the providers package refactor upstream. Have not done it as this code is based on top of the azure PR and requires some love to remove it again unamused . I guess azure support won't ever be merged at this stage.

This branch is [15 commits ahead](https://github.com/davidcassany/linuxkit/compare/linuxkit:linuxkit:master...master), [323 commits behind](https://github.com/davidcassany/linuxkit/compare/master...linuxkit:linuxkit:master) linuxkit:master.
Yeah...difficult :D


Navigating to http://localhost// causes a security exception

When react router attempts to load a route beginning with two slashes, you will receive a security exception similar to the following:
Uncaught SecurityError: Failed to execute 'replaceState' on 'History': A history state object with URL 'http:' cannot be created in a document with origin 'http://localhost'.
This is because react router attempts to push // onto the history, which is interpreted as a scheme-relative URL.
I was expecting a 404 and the corresponding not found route to load.

Can you file this against mjackson/history? It's not an RR bug per se.

Sure


User Profile Page Redesign 🤩

The User profile page currently looks a bit weird.
You can share a Figma file for the design you want to implement.
Make sure the design must be responsive too.
Screenshot Also works

The above issue will require multiple PRs
So the points are based on a number of PRs and functionalities!

https://www.figma.com/file/4ZBjMLeBVffO4fAz3k55Hh/Untitled?type=design&mode=design&t=6kwami1aiBcNCuaK-1
@Spyware007 check it out 😹

Hello @Spyware007 Can I work on this issue?

🎉 The GSSOC'23 program has reached its conclusion, prompting us to officially close all pull requests (PRs) and issues. We extend a heartfelt thank you for your amazing contributions! 🙌 Keep the coding spirit alive with the same enthusiasm, and may luck 🍀 favor you in all your future coding adventures!

https://github.com/FMC-Weekend/fmc24-client.git

Please assign this issue to me

Please assign this issue to me
i had already worked on assignments such as building a profile page


CUDA implementation of BiasAddGrad op is non-determinstic

I'm running TensorFlow 1.5.0 on a K80 GPU on Python 2.7
Failing test case:
from __future__ import print_function
import hashlib
import numpy as np
import tensorflow as tf

np.random.randn(2018)
tf.set_random_seed(2018)

X = np.random.randn(1024, 50).astype(np.float32)
b = tf.get_variable('bias', [50])
z = tf.nn.bias_add(X, b)

grad = tf.gradients(z*z, b)[0]

init_op = tf.global_variables_initializer()

with tf.Session() as sess:
    sess.run(init_op)

    run1 = sess.run(grad)
    run2 = sess.run(grad)

    print(np.all(run1 == run2))
    print(np.max(np.abs(run1 - run2)))

    dohash = lambda X: hashlib.md5(X.tostring()).hexdigest()
    print(dohash(run1))
    print(dohash(run2))

Outputs
False
6.10352e-05
b489a1d659518b2ae9213f5a21e35df2
187a57d563468e59ba5f9d9cf51ca5cb

This bug still exists in master, because the code in master uses the unsafe CUDA atomic floating point add in several places. See https://github.com/tensorflow/tensorflow/blob/abc55107eb7a03fe3d83f95fd5e1b8e4def90826/tensorflow/core/kernels/bias_op_gpu.cu.cc
If TensorFlow will be ever be fully determinstic, atomic floating point add should never be used (it is inherently non-determinstic due to non-associativity of floating point).
Notably, Keras's Dense layer uses bias_add, so all networks that use this layer are non-reproducible. This is relevant to https://github.com/keras-team/keras/issues/2280 .
This can currently be avoided by using tf.add instead of tf.nn.bias_add at a slightly performance hit. The correct fix would be refactor the BiasAddGrad op to use a (deterministic) reduction tree.
edit with issue template fields:
Have I written custom code: Python test case, see above
OS Platform and Distribution: RHEL 7.5 (Linux)
TensorFlow installed from: source
TensorFlow version: 1.5.0
Bazel version: unknown
CUDA/cuDNN version: CUDA 8.0.61, cuDNN v6
GPU model and memory: Nvidia K80, 12GB memory
Exact command to reproduce: run the above script
Mobile device: NA

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

@eamartin A small amount of non-determinstism in TensorFlow computations is expected on GPU. Ongoing efforts are put forth and FR is in place. 18096 Latest developments from algorithms and hardware architecture perspectives reaped success where challenges remain.
Please resort to workarounds, e.g. tf.add for now until more concrete solutions come forth.

Closing this issue for now, will use FR to track progress.

@wt-huang This issue is completely separate from https://github.com/tensorflow/tensorflow/issues/18096 as it has nothing to do with cuDNN. The non-determinism here is in the TensorFlow source itself, not a 3rd party library.

@eamartin This problem is a subset of the non-determinism issue resides in cuDNN. When the feature request is completed and the solution implemented will be transferred to tf.nn.bias_add

This problem is a non-determinism issue, but is separate from non-determinism issues with cuDNN.
The solution to cuDNN non-determinism is to pass the correct flags into the library specifying which algorithm to use. See https://docs.nvidia.com/deeplearning/sdk/cudnn-developer-guide/index.html#reproducibility
The solution of "set the right cudDNN flags" cannot be transferred to non-cuDNN issues such as this. Resolving this issue involves modifying CUDA kernels in the TF source. Resolving https://github.com/tensorflow/tensorflow/issues/18096 probably does not.
Additionally, this issue affects more users than https://github.com/tensorflow/tensorflow/issues/18096 as bias_add is used for fully connected layers (including through Keras) while cuDNN primarily affects CNNs.
An appropriate "remove non-deterministic behavior" parent issue should not be solely about cuDNN in my opinion. It should include mention of removing all uses of atomic floating point instructions in the TF source.

https://github.com/tensorflow/tensorflow/issues/2732 is a more relevant issue than https://github.com/tensorflow/tensorflow/issues/18096

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

@eamartin Yes, atomic floating point addition is one of the primary triggers of non-determinism, which happens to be prevalent in CUDA regime.
We are very well aware of this issue and progress is underway.

@wt-huang Has this issue been solved? Why has it been closed?

@eamartin We are aware of this issue, fix is in the progress.

Can this issue remain open until the fix is merged?

@eamartin, this issue was resolved, in Oct 2019, with PR 31465. In TensorFlow version 2.1 and onwards, you can enable the solution by setting the environment variable TF_DETERMINISTIC_OPS to "1" or "true".
For more information, see [github.com/NVIDIA/tensorflow-determinism].

@duncanriach thank you very much for that fix as well as all of your other work on TensorFlow determinism!

You're welcome, @eamartin. Thank you for the appreciation.


[Discussion] Do we need to open up all the security ports for AWS?

Priority
Undecided
OS type
Ubuntu
Hardware type
Xeon-SPR
Installation method

[X] Pull docker images from hub.docker.com
[ ] Build docker images from source

Deploy method

[X] Docker compose
[ ] Docker
[ ] Kubernetes
[ ] Helm

Running nodes
Single Node
What's the version?
0.9
Description
I'm trying to follow the instructions at https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/docker/xeon.
Why do we need to open up all these ports in the EC2 Security Group? These services should be talking to each other within the VPC only.
Reproduce steps
Curious about the need to open up the ports before I start implementing this.
Raw log
No response

@arun-gupta The architecture design is to open up gateway port only.
Let me try to get a AWS platform first. Then we can get to know the networks settings on AWS, and we can try and verify the port setting for the GenAIExamples.

I've been playing with the setup on AWS. I logged into the EC2 instance and could run a couple of tests locally without opening any ports.
It seems like the ports only needs to be opened up if you do curl from the local machine. The instructions already mention that but it is easy to miss.  Can we remove the instructions to open up the port otherwise someone would accidentally do that in production?
Here are my evolving instructions: https://gist.github.com/arun-gupta/7e9f080feff664fbab878b26d13d83d7

@arun-gupta
Do you have AWS platform shared with us so I can investigate this issue?
We have no AWS platform.

@xiguiw sure, send me an internal Teams message and lets set up offline time to work through this.

I update the guide for AWS user to fix this issue.
Please refer to PR: https://github.com/opea-project/GenAIExamples/pull/849

Hi Arun
we fixed the problem by PR: https://github.com/opea-project/GenAIExamples/pull/849
close now, please feel free to reopen it if any issues.
Thank you!


Add FTPS support (#33)

Title
Support for reading and writing files directly to/from ftps (ftp with tls)
Motivation
I have previously added support ftp servers (without tls encryption). Now, to add more complete ftp functionality, I have added support for ftp+tls servers.
from smart_open import open
with open('ftps://user:password@host:port/dir1/dir2/file') as fin:
     for line in fin:
          print(line)

Tests
I have edited the ftp integration tests to run an ftp and ftps server on different ports and then test reading, writing, and appending to each of them. (specific integration test here, pull up ftp and ftps servers here).

Thanks for the quick resolution @RachitSharma2001.
@mpenkov can you please review?

Thank you for your work @RachitSharma2001 !


psiTurk now supports python 3

should update!

https://github.com/NYUCCL/psiTurk/releases/tag/2.3.2

Resolved in f0041e6


Seeing lots of "Error Packet Recieved" messages in the logs

Hundreds of them. Seems like the device is working and showing in my overview dashboard on HA, but the ammount of times this is being logged is concerning:
`This error originated from a custom integration.
Logger: msmart.base_device
Source: custom_components/midea_ac/climate.py:179
Integration: Midea Smart AC (documentation, issues)
First occurred: September 3, 2023 at 11:35:36 PM (600 occurrences)
Last logged: 10:06:56 PM
Network error <IP_ADDRESS>:6444: Error packet received.
Network error <IP_ADDRESS>:6444: Protocol has not been authenticated.
Network error <IP_ADDRESS>:6444: Transport is closing or closed.
Network timeout <IP_ADDRESS>:6444: No response from host.
No response from <IP_ADDRESS>:6444 in 6.010000 seconds.`

Sorry for the trouble. Were you a user of mac-zhou's original version? Can you supply the full logs? Not just the summary.

Don't be sorry! Thank you for the quick reply. I was a user of the zhou version, but have removed it and switched over to yours since the other one seems out of date. Here are the full logs:
home-assistant_2023-09-05T05-32-09.906Z.log

Wait, that might not be all the logs, give me a moment and I'll grab them

Sorry I originally sent the wrong logs: here are the correct ones!
home-assistant_2023-09-05T06-03-02.444Z.log

@mill1000 yes that is similar to what I see. I don't see an "error packet received" - it just straight up times out.
It also happens every 4 minutes exactly (screenshot below). Once or twice now, it has timed out and stayed offline and wouldn't come back until I restarted the integration (however at this time I didn't have the debug enabled so I can't tell you what the logs said).

Startup of integration (following re-load of HASS via the developer console following putting the debug lines in)

2023-09-06 11:02:00.828 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444
2023-09-06 11:02:00.841 DEBUG (MainThread) [msmart.lan] Connected to <IP_ADDRESS>:6444.
2023-09-06 11:02:00.842 INFO (MainThread) [msmart.lan] Authenticating with <IP_ADDRESS>:6444.
2023-09-06 11:02:00.843 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444:<PHONE_NUMBER>000000d00ecbeccce8ea489ac43452264d7401b4e1ef72fc1b45a75d1362bcea1cac670bc6d6940620c25ef03413144e7e0ddd5c61ed22d657097c1e7fa0a62f504070
2023-09-06 11:02:01.420 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444:<PHONE_NUMBER>0100003b3fac3695300e779c73afa536a8e4181dabac917b868c23b431c4d79f43ecc45366ab101bfe83016ef2ae40e1abbe60c178a77d04dcd2876ca32396328ff842
2023-09-06 11:02:02.034 INFO (MainThread) [msmart.lan] Authentication successful. Local key: 5b320fcbad1c6e010b45f081e1dae902941efeddb7c8e421b91031549f9043bd
2023-09-06 11:02:03.036 INFO (MainThread) [custom_components.midea_ac] Querying device capabilities.
2023-09-06 11:02:03.036 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa0faca3000000000003b5011101cd0a
2023-09-06 11:02:03.037 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01115800200000000000030302170509171428fa0000001c0000000000000000000000000000587b6ef1789c550a4ef57108e708a5d2915c618b02ed2747fad73f2ffa0db1d300a978b08a76f82669395ead3aa3d186
2023-09-06 11:02:03.037 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370007e2066ab58aa9818bcf4cdfa8b73a3fc1eeaaa8cdbe2a24774980288090cf231370ac51f77d81eba2305324c69550ef66c365b48fbf0001d9711ab6d3d14dbb32591089d78879badf527018a58437d82d33e68424f5086a02d1057f79df5a6ae5b64d71d1d10ddfcc6f519cfd2ae2b29fe3e2374ad072b07a0d53b3f580169fa8409a6
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e20636d3bd6be210dfd03e0ae29342930c5e84cd9e7360cf078d00f6fd9c0de3642729f93d9790a79a1eb36386a0be327b174716466fb92bce4e5c6c7be4237f72c31008a79f577064a46e9525853523a7cee4285452454ef3643d68f39adf24955072d26dd8f9bee5b57f59b5d5ec6afa7a3d82f09cc05460cac489547b0c25f11c3054178880b2aeb3c232664c16aec15ce
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a01116800208000000000000000000000000028fa0000001c00000000000000000000000000002ed30f7318deb2150985a069e6df704fc6c5350d624b48edff5254e941e2aad1eb8d98ade0f90bb5f67d9331fb42c16db69be03904c2b18ee1b8eca66cfc0da0
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa29ac00000000000303b5071202010113020101140201011502010116020101170201001a020101dedb
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.610000 seconds.
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.device.AC.command] Capabilities response payload: b5071202010113020101140201011502010116020101170201001a020101
2023-09-06 11:02:03.648 DEBUG (MainThread) [msmart.device.AC.command] Supported capabilities: {'eco_mode': True, 'eco_mode_2': False, 'freeze_protection': True, 'heat_mode': True, 'cool_mode': True, 'dry_mode': True, 'auto_mode': True, 'swing_horizontal': True, 'swing_vertical': True, 'power_cal': False, 'power_cal_setting': False, 'nest_check': False, 'nest_need_change': False, 'turbo_heat': True, 'turbo_cool': True}
2023-09-06 11:02:03.653 INFO (MainThread) [custom_components.midea_ac.climate] Setting up climate platform.
2023-09-06 11:02:03.654 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac8d000000000003418100ff03ff000200000000000000000000000003028b4e
2023-09-06 11:02:03.654 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000410302170509171428fa0000001c0000000000000000000000000000b8436dd15e84d5a4fc6fbf77d2b1248672946460bceafc6eae86e4200896522a734e1faa37ce959a047497632b36c8a865fd30f251eff5ee97df66f9259f05b4
2023-09-06 11:02:03.654 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e2066add9f67c8b0e98950cb8f86abb0ce5aa0847459f2981037a37626ec066837b4f72ce92786f4f4ec10b44a48e0977d14185d55be386e0c73e7ad35c92e5885ec87af54d0b22af8e4472e01ea37af7d7394440d7f53dff4897d2768489c8bada7c48467e7794c26a907bc9fe14e7cc7bb6925345cf5d1abe683d4310def747669fd35769fc703246d314cb59705a87c095
2023-09-06 11:02:03.655 INFO (MainThread) [custom_components.midea_ac.sensor] Setting up sensor platform.
2023-09-06 11:02:03.655 INFO (MainThread) [custom_components.midea_ac.binary_sensor] Setting up binary sensor platform.
2023-09-06 11:02:03.655 INFO (MainThread) [custom_components.midea_ac.switch] Setting up switch platform.
2023-09-06 11:02:04.375 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e2063ad6b22cf29abe048e8096b10620b6b6873dcf720d11259888d6aedca4f2e3f42a08b0107b0384f00f4e0951a5a4b75151115c286d9e1df16d849571f4610e8658f42f2e4cc4b1af8dc53cf54c5e219d0829c95ca959fd58f15476c8943bb8ef48fc002a43f3bab3dfa34a61502c0b14ee8265ebfeb8b4746625fc20e2f5c075ccf9c5a0878cac3fda777bae919f28671
2023-09-06 11:02:04.375 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a01116800208000000000000000000000000028fa0000001c0000000000000000000000000000e57ffebd2033eb931d73fbf6e7234b52926f5fac7422549d4ba996e6b262c20c644f1c1a0aebe50d39b5bf1c5285d2d7b684d409b2a0101f22a0383db152f0c4
2023-09-06 11:02:04.376 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c000a5667f7f00300000005a510000000000000000008b3ebf
2023-09-06 11:02:04.376 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.720000 seconds.
2023-09-06 11:02:04.376 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c000a5667f7f00300000005a510000000000000000008b

When the device goes offline (I suspect the first 12 lines here are not relevant, but I have included them in case there's some info there that you'd need)
2023-09-06 11:06:04.389 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac8d000000000003418100ff03ff0002000000000000000000000000031216b3
2023-09-06 11:06:04.390 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000270406170509171428fa0000001c0000000000000000000000000000b8436dd15e84d5a4fc6fbf77d2b12486e1022a09a865fb1d6ddec45619b7ce4b1e89ae4ea71e445916df99626ed88195724676278f2b0a9219317e16a57ac7b1
2023-09-06 11:06:04.390 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e206637b0ffee53265edaeee7ea38bb98f342d77accaa488625d4a92379dde5bd5da8a7a700038892d98806f1314d263a0d76cc27bf0bd48fc0d9c4b8dad66c6e317243230a376727afa0b2c47ec0bb6b5d10d15c08fdcee76105a871a5038e868cf787e33029e05a465c6a1c672701171ddcbcb8a753f88af3cf0330dac692226e0f7caaeffbd7aeb9171890c3f578051143
2023-09-06 11:06:05.103 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e2063a53b18d82b1bb9099bd4865c16be339e264e4b0267cf5bc914d9c8b9a39fa04ba7b6e76ed9ec22b4101a3a05861900b57e871b939146e990fc4e0cde920e379588a3ab9e0af2c36ee98f726328e51eb759df4a55f63e7f9c57981ea16253c3b1d86efbef4a0af0a6148afa8a80136b92896e43a79c54feb31a797c55afff380bd1bd76b38ec37c8566a130c0112d1aff
2023-09-06 11:06:05.104 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a01116800208000000000000000000000000028fa0000001c0000000000000000000000000000e57ffebd2033eb931d73fbf6e7234b525b2d7362ba4fc5204636ed5913983384814c20d0376c2a8f770b95b0b2e70e6fee171a31098bd10672b9745d9c59a7e8
2023-09-06 11:06:05.104 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c000a5667f7f00300000005b5100000000000000000016bab7
2023-09-06 11:06:05.104 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.710000 seconds.
2023-09-06 11:06:05.104 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c000a5667f7f00300000005b5100000000000000000016
2023-09-06 11:06:19.390 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac8d000000000003418100ff03ff000200000000000000000000000003134880
2023-09-06 11:06:19.390 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000271306170509171428fa0000001c0000000000000000000000000000b8436dd15e84d5a4fc6fbf77d2b12486565485cade4a7e9857564f5d9d7b68bb9b0651f2ae768de690e0717b0b29b231b306d8ddccf9640453acaf1ac8a854ad
2023-09-06 11:06:19.390 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e20662883d43dd6984b55d01f045e685891c84ee299b85b678e8a9f758785985d226ecac3ca661445db1c462cdfe4a9e3b992f7d7c41c420cfd72c4175d2e0a9e97419f646492e015131497a738669bb80e3c4085fa6c4340ece997a9830195988396b3eccfa499a6f408aafdb51b3bbd2f0bb3f620600bbfeca9026aa33475b9d6c91fd3f39dee275c3d4657deb10ec440ad
2023-09-06 11:06:21.391 DEBUG (MainThread) [msmart.lan] Request timeout. Resending.
2023-09-06 11:06:21.391 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000271306170509171428fa0000001c0000000000000000000000000000b8436dd15e84d5a4fc6fbf77d2b12486565485cade4a7e9857564f5d9d7b68bb9b0651f2ae768de690e0717b0b29b231b306d8ddccf9640453acaf1ac8a854ad
2023-09-06 11:06:21.391 ERROR (MainThread) [msmart.base_device] Network error <IP_ADDRESS>:6444: Transport is closing or closed.
2023-09-06 11:06:34.391 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac8d000000000003418100ff03ff00020000000000000000000000000314cbfc
2023-09-06 11:06:34.391 DEBUG (MainThread) [msmart.lan] Disconnecting from <IP_ADDRESS>:6444.
2023-09-06 11:06:34.391 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444
2023-09-06 11:06:34.395 DEBUG (MainThread) [msmart.lan] Connected to <IP_ADDRESS>:6444.
2023-09-06 11:06:34.395 INFO (MainThread) [msmart.lan] Authenticating with <IP_ADDRESS>:6444.
2023-09-06 11:06:34.395 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444:<PHONE_NUMBER>000000d00ecbeccce8ea489ac43452264d7401b4e1ef72fc1b45a75d1362bcea1cac670bc6d6940620c25ef03413144e7e0ddd5c61ed22d657097c1e7fa0a62f504070
2023-09-06 11:06:34.838 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444:<PHONE_NUMBER>0100008a05d88e1688575df51a157f4401ad86afc3e0139386dd8241ceb227d21f65e6da63f768753546dfa61b8fccced2687dc89dfadc163b092c0c594fa1869e5adc
2023-09-06 11:06:34.838 INFO (MainThread) [msmart.lan] Authentication successful. Local key: 19fc716a407b97b6cff58f3572fe95b51311016b1b4d9a961f00cee3ac053c0a
2023-09-06 11:06:35.839 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000532306170509171428fa0000001c0000000000000000000000000000b8436dd15e84d5a4fc6fbf77d2b12486348dd9a0c1701b19f4c95446839559aebc87dab37210444c7065964f319aa816bffa05984fa5fca05e80d5f359f73586
2023-09-06 11:06:35.839 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e2066861396107d1b321950e03f294a0b71b66fae9d7a36fc0c640b31b71d49377806e9a52b0e4b6b49bc8729f0ecc5eeb3cb9080840a7ce543c87a97e8e58ccd692caf8700adbcc613a08a328b8e6362dce3053c2662d41250dfc48179409a429a556a7c735a33f9fc8781d03493eb6ac392b54b968c607a8e3c89af60d07cca8efeecaffba15211c290926f838f6c8795d0
2023-09-06 11:06:36.553 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e206340b5e8f5ccff4bc3d899ebeb89ffb887eeeb2c5bf4986d7220f4bec86fda0f34fc8a0fdc4b0104a05cf1c838808fd9ed9a0f264210825b0e266c14457b6b9e092073ae2f7e3499ded115d224dc78dc42031e41c4fe45c1b9d218fe61af0c8a8214ea372776cf6e30c443034a091bcd856c7eea891595510901bd9d3d676237ffd2318312de1b556d125e4baabe804b90
2023-09-06 11:06:36.554 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a01116800208000000000000000000000000028fa0000001c0000000000000000000000000000e57ffebd2033eb931d73fbf6e7234b525b2d7362ba4fc5204636ed59139833843437697aec014f6ed40edb58704245d743c89804f02f347cef73b4337a1d18a5
2023-09-06 11:06:36.554 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c000a5667f7f00300000005b51000000000000000000cb10ac
2023-09-06 11:06:36.554 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 2.160000 seconds.
2023-09-06 11:06:36.554 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c000a5667f7f00300000005b51000000000000000000cb

@amit-nz  Thanks for the very detailed response.

@mill1000 yes that is similar to what I see. I don't see an "error packet received" - it just straight up times out.
It also happens every 4 minutes exactly (screenshot below). Once or twice now, it has timed out and stayed offline and wouldn't come back until I restarted the integration (however at this time I didn't have the debug enabled so I can't tell you what the logs said).

Let me know if this happens again with debug logging. Obviously all these warnings are no good, but it's even worse if it doesn't come back up.

If it matters, my Midea Aircon is on my IoT subnet which cannot talk to my main "LAN Trusted" subnet. HASS has a LAN interface on both my LAN subnet and my IoT subnet as well, so it's on the same L3 segment. I ran a ping to it anyways while the issue was happening (Timeout) and here's what it turned up - no packet loss or excessive latency/jitter as expected.

I don't think this would be a problem.
If you're feeling ambitious would you be able to capture a timeout/re-connection with Wireshark or tcpdump?
I'm making an assumption that these disconnects are being triggered from the device's side, not the HA side. At the time I'm wondering if one of the following might help:

Closing/re-opening the connection for each message. 2-4 minutes hardly seems like a "long-living" connection but perhaps the device is super aggressive about dropping "old" connections.
Enabling TCP keepalives.Although I'm not sure if these connections are up long enough for keepalives to be sent.

Just an anecdote, there is a configuration option that was inherited from mac-zhou called "Keep Last Known State" that I'm guessing was introduced to mask this issue by not declaring the device offline when it fails to receive data. Instead it just returned stale data to HA.

@mill1000 sure I can packet capture, is it OK if I do a packet capture on port 6444 only (i.e. traffic between HASS and my aircon on TCP 6444 filtered by MAC of my ac unit) - otherwise there is a ton of noise coming up.

What you've suggested sounds fine to me.

@adamrgolf, @amit-nz, Do either of you have the device blocked from accessing the internet? Either via DNS or some router access control?

It's been almost a day now and there are now 3400+ logs!
home-assistant_2023-09-10T05-33-15.380Z.log

Based on your first log the device disconnects every two minutes, almost to a tee.
A possible fix might be to close the connection after every message, but I'll have to see if the overhead would be unreasonable.
Something different, and more fatal, happened in your second log. I'll have to look closer later, but it appears at some point your device rejected the authentication message after which I believe the device probably went offline to HA.
Were you a user of mac-zhou's integration before?

I was a user of the zhou version, but have removed it and switched over to yours since the other one seems out of date. Seemed to have the same issues with that version.

Well thanks for trying this one out! Hopefully we can find a solution for your setup.
Ok, that's what I expected. The network code was rewritten (to be async) but fundamentally works the same.
What model & name is your device?
Do you know the model of your WiFi dongle? Should be something like OSK105.

So, this is the one I currently have installed in my Carrier minisplit.
However, I know I also have this one, which I can try out the next time I'm at the property.
Do you happen to know if there is a difference between osk102/103/105?

Do you happen to know if there is a difference between osk102/103/105?

Not exactly. I have both an OSK103 and OSK105. My 103 uses the V2 protocol and my 105 uses the V3 protocol. Neither of my devices show the problem yours has.
Your device is using the V3 protocol. It would be interesting to see if the other dongle behaves differently.

Also, here is a log with a few more messages, not sure if they were in the other logs or not:

Thanks, at this point I don't think any more logs are necessary.

Updating midea_ac climate took longer than the scheduled update interval 0:00:15 September 10, 2023 at 8:36:15 PM – (WARNING) Climate - message first occurred at September 10, 2023 at 9:28:11 AM and shows up 3 times
Update of climate.midea_ac_32985348836922 is taking over 10 seconds September 10, 2023 at 8:36:10 PM – (WARNING) helpers/entity.py - message first occurred at September 10, 2023 at 9:28:06 AM and shows up 2 times
Update for climate.midea_ac_32985348836922 fails September 10, 2023 at 9:35:45 AM – (ERROR) Midea Smart AC (custom integration) - message first occurred at September 10, 2023 at 9:28:31 AM and shows up 30 times

I think there are a few things happening with these messages.

The device appears to have dropped off the WiFi briefly
The connect calls take too long to timeout, so we get warnings about taking over 10 seconds to update. This should be addressed in the next release of msmart-ng: https://github.com/mill1000/midea-msmart/pull/56
Eventually the OS knows it can't reach that device so it throws OSError 113 (no route to host). I created an issue here to address that more gracefully: https://github.com/mill1000/midea-msmart/issues/62

home-assistant_2023-09-11T09-40-16.575Z.log

@adamrgolf @amit-nz
If you're willing, I have a hack I'd like you to test. This branch will reconnect every time it sends a command.
You can install it with pip like so.
pip install git+https://github.com/mill1000/midea-msmart@issue/hack_always_reconnect

OK. I have installed that hack :) I'll let you know in a day or so how it looks and post the new logs.
Thanks for your efforts!

It looks like the branch wasn't installed.
From your logs
2023-09-12 02:42:11.019 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py. Using msmart version 2023.9.2.

I would expected the version to be: msmart-ng-2023.9.2.post1.dev13+ga6738bc.
Did you restart HA after installing the branch?

I did restart, does it revert back after a restart?

I ran it from here:

should I try something different?

That's a good add-on, but it's not putting you into the docker container where you need to run pip.
Check this link: https://community.home-assistant.io/t/execute-in-home-assistant-container-context/415031/4

Got it! Sorry for the trouble, doing the command properly now:

I'll test it out for a bit and report back. Cheers!

No problem. You should only need to run for about 10-20 minutes to get good logs.

So I'm still a bit confused. I issued the command to install the hack, but still wasn't seeing anything similiar to "msmart-ng-2023.9.2.post1.dev13+ga6738bc", just "msmart version 2023.9.2". I then saw that there was an update for this package to 9.3, so I updated to that and rebooted HA. Should I still attempt to install the hack you provided? I'm happy to try what I can to help! As of now it still looks like the AC drops off HA quite often:

Thanks again!

Ok, I've updated the branch to be based of the latest release.
After installing you should see version: msmart-ng-2023.9.4.dev1+g39fd011.

OK, I've installed the hack again :) I'm rebooting and will keep a close eye on things

Great. If you can send logs after about 10 minutes, I should be able to get an idea of if this will work

Let me know if this is enough:
home-assistant_2023-09-15T14-33-06.249Z.log

This is looking pretty good so far. No errors in the first 10 minutes.
Can you follow up with your impression (and logs) after a few hours?

No problemo, I'll set a reminder for a couple hours, and if by chance I miss it due to sleep, I'll post an update later this eve/tonight.
So far so good though, no drop offs for almost 2 hours:

Cheers!

Good morning :) It looks a little better today, but I do still see a decent amount of drop offs in HA:

Here are the logs since yesterday:
home-assistant_2023-09-16T11-11-59.726Z.log
Hopefully there's something helpful in here. Thank you!

Overall this is still looking to be much better! There was about 15 dropped connections, most which occurred in a burst between 3:21 to 3:30.
I've updated the branch again. Can you install and test? You should see version 2023.9.4.dev14+g0eb25b4.
You may get a notice from HACS about an update being available. You can ignore that for now.

No problem, installing the updated branch now and will ignore the HACS update for msmart.

I'll let you know after while too how things are looking!

Here's the status after an hour, looking good to me so far:
home-assistant_2023-09-17T21-42-50.189Z.log

Re-opening cause I preemptively closed this.
Great! I suspect it will never be perfect (my system has the occasional hiccup too) but a handful of warnings is better than thousands.

I completely agree! So far i've only seen one reconnect in HA overview:

And only a couple errors in the log:
home-assistant_2023-09-18T03-50-17.349Z.log
Thank you very much again for your work. Is there any length of time you'd like me to keep monitoring via the hack branch, or should I update the version though HACs at some point?

I'll review those logs tomorrow. Use the branch for now, I'll make a new release soon and you can update to that

I've released this feature in 2023.9.5.
@adamrgolf You can set the connection lifetime in the integration options, a value of 90 will match what you've been testing

Awesome! I'll update to 9.5 and change the option you mentioned to 90! Thanks again!

Gentlemen, can anyone help me with similar problem? I had been using original midea-ac-py without any issue but decided to switch to this one because HACS kept saying to me about its' obsolete state.
Now I see these messages in the logs:
2024-01-29 23:07:16.610 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.
2024-01-29 23:09:16.617 ERROR (MainThread) [msmart.base_device] Network error <IP_ADDRESS>:6444: Transport is closing or closed.
2024-01-29 23:09:29.318 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.
2024-01-29 23:11:31.326 ERROR (MainThread) [msmart.base_device] Network error <IP_ADDRESS>:6444: Transport is closing or closed.
2024-01-29 23:11:45.610 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.
2024-01-29 23:13:46.618 ERROR (MainThread) [msmart.base_device] Network error <IP_ADDRESS>:6444: Transport is closing or closed.
2024-01-29 23:14:01.611 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.
2024-01-29 23:16:01.630 ERROR (MainThread) [msmart.base_device] Network error <IP_ADDRESS>:6444: Transport is closing or closed.
2024-01-29 23:16:16.610 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.

and some screenshot:

I changed 'maximum connection lifetime' to 130 but looks like that didn't help to me. Should I increase that value more? Or any else ideas?
Thanks in advance!

Your disconnects appear to be happening about 2 minutes apart. You should be setting the Maximum Connection Lifetime to less than 120 s.

LESS! Thanks! that worked!


[#20097] Add replacement for "dds" modules and -no-dependencies option to fastddsgen

Make fastddsgen add “eprosima” and “fastdds” when “dds” modules are found in IDLs.
Add a -no-dependencies option to avoid generating files for dependencies.

CI: https://github.com/eProsima/Fast-DDS-Gen/actions/runs/7165951726

CI: https://github.com/eProsima/Fast-DDS-Gen/actions/runs/7169867608


Exported mp3 file sampling rate problem

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.09.08. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.09.08

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--no-playlist', '--default-search', 'ytsearch', '--format', 'bestaudio[ext=m4a]', '--extract-audio', '--audio-format', 'mp3', '--add-metadata', '-o', '13471849318416175427.mp3', 'https://www.youtube.com/watch?v=nksfBbEfOD0']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.09.08
[debug] Python version 3.6.6 (CPython) - Linux-4.4.0-1027-aws-x86_64-with-debian-stretch-sid
[debug] exe versions: ffmpeg 4.0.2-static, ffprobe 4.0.2-static
[debug] Proxy map: {}
ERROR:     Last message repeated 1 times
 Traceback (most recent call last):
   File "/app/.heroku/python/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 2047, in post_process
     files_to_delete, info = pp.run(info)
   File "/app/.heroku/python/lib/python3.6/site-packages/youtube_dl/postprocessor/ffmpeg.py", line 465, in run
     self.run_ffmpeg_multiple_files(in_filenames, temp_filename, options)
   File "/app/.heroku/python/lib/python3.6/site-packages/youtube_dl/postprocessor/ffmpeg.py", line 204, in run_ffmpeg_multiple_files
     raise FFmpegPostProcessorError(msg)
 youtube_dl.postprocessor.ffmpeg.FFmpegPostProcessorError:     Last message repeated 1 times
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
I have been trying to add bitrate, sample rate and length to the extracted audio files as otherwise the mp3 file does not play well with audacity which seems to think the audio file is only a few seconds long.  So I am using the --add-metadata however it throws this error. I am wondering if I am doing something wrong as no matter what I try the mp3 won't work well with audacity or google play music.

https://transfer.sh/4xtVx/13471849318416175427.mp3
Heres an example. It plays fine on the transfer.sh and groove music

however trying to use it with audacity will result in

and uploading to google play music

.
I'm not sure what i am doing wrong.

Do not hardcode extension in output template.

Thank you soo much. For some reason I didn't think that would be the problem! Also thanks for the quick reply!


【bug】Game Crashes on Startup.

It crashes when I start the game, I added more than 50 modules, and the error report I uploaded below.
debug.log

Fixed with v0.1.1.


Fix python3.7 Compatibility

Compatibility with Python 3.7+ an Pytorch 1.12.0+:

Changed src/transformers/adapters/utils.py so that it remains compatible
Adapted the python and pytorch versions in the CI/CD pipeline workflows

Fixes #509

This looks good. But we should consider, whether we want to continue to support python 3.7. The adapter-transformers version 3.2 we released does not. So "going back" in the supported python version might be confusing. Additionally, python 3.7 is only supported till June this year. It might make more sense to update our documentation and only support version 3.8 or higher.


msbuild: init at 15.8

(recreation of #43680 because I broke my repo)
Motivation for this change
xbuild, which is part of Mono, is deprecated, in favor of the recently open-source MSBuild used on Windows. MSBuild has an incredibly complicated build system, which appears to fail silently on non-FHS systems. Thus, I used the official Ubuntu binaries. These require relatively little patching, as .NET is a bytecode language, so patchelf is not necessary. I don't have a Mac to test, but it may work on MacOS as well for this reason. This is definitely a stopgap; however, MSBuild's custom build system will require extensive work to be used, or even emulated, on NixOS. Since #43680, I've updated it to 15.8, cleaned up the build script, and shrunk the package by about 100MB.
Things done

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

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

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

Wait, I accidentally reverted the update.

Does it impossible to build it from source?

It uses a custom build process which automatically downloads pre-compiled Mono binaries.

I bit back I was looking at your original pr and applied some of @samueldr feedback.
Almost died in a stash but here it is :smile:
diff --git a/pkgs/development/tools/build-managers/msbuild/default.nix b/pkgs/development/tools/build-managers/msbuild/default.nix
index 781f5b1c524..93d19fb047c 100644
--- a/pkgs/development/tools/build-managers/msbuild/default.nix
+++ b/pkgs/development/tools/build-managers/msbuild/default.nix
@@ -14,15 +14,21 @@ stdenv.mkDerivation rec {
   dontConfigure = true;
   dontBuild = true;

-  unpackPhase = "dpkg-deb -x $src .";
-  installPhase = ''
-    substituteInPlace usr/bin/msbuild --replace /usr/bin/mono ${mono}/bin/mono --replace /usr/lib/mono/msbuild/15.0/bin/MSBuild.dll '$(dirname $0)/../usr/lib/mono/msbuild/15.0/bin/MSBuild.dll'
+  unpackPhase = "dpkg-deb -x $src build";
+  installPhase = "
+    (
+    cd build
     mv usr/bin .
-    mkdir -p $out
-    cp -r ./bin ./usr $out
-    cp -rs ${mono}/lib/mono/msbuild/15.0/bin/Roslyn $out/usr/lib/mono/msbuild/15.0/bin/Roslyn
-    cp -rs ${mono}/lib/mono/4.5 $out/usr/lib/mono/4.5
-  '';
+    mv usr/lib .
+    rm -rf usr
+    )
+    cp -r build/ $out
+
+    substituteInPlace $out/bin/msbuild --replace /usr/bin/mono ${mono}/bin/mono --replace /usr/lib/mono/msbuild/15.0/bin/MSBuild.dll $out/lib/mono/msbuild/15.0/bin/MSBuild.dll
+
+    ln -s ${mono}/lib/mono/msbuild/15.0/bin/Roslyn $out/lib/mono/msbuild/15.0/bin/Roslyn
+    ln -s ${mono}/lib/mono/4.5 $out/lib/mono/4.5
+  ";

   meta = with stdenv.lib; {
     description = "The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio";

Main things addressed if I recall correctly were:

Symlink instead of copying stuff from mono
No usr in $out
Bring in the env-vars file

Also didn't include anything from share/doc/ because it didn't look useful.

Nice GitHub bug 😛 I'll create a new PR again, I guess.

@leo60228

I don't have a good build machine. Could you see if it still runs without it?

I was actually able to reproduce what @jdanekrh mentioned in the older pr without this change.

I think I've encountered the same error also. When compiling a project, the compilation would fail with
  Microsoft.Common.CurrentVersion.targets(3446, 5): [MSB3491] Could not write lines to file "/Debug/ClientLib.csproj.CoreCompileInputs.cache". Could not find a part of the path "/Debug/ClientLib.csproj.CoreCompileInputs.cache".
  Microsoft.Common.CurrentVersion.targets(5101, 5): [MSB3191] Unable to create directory "/Debug/". Access to the path "/Debug/" is denied.

(it attempts to write to the filesystem root, because a prefix is not set correctly).
I resolved the same thing by 1) downloading msbuild and unpacking msbuild, 2) setting it in jetbrains.rider in GUI in Use custom MSBuild version to
/home/jdanek/Downloads/msbuild/MSBuild.dll

and 3) adding to my .bashrc the following
export MSBuildExtensionsPath=/home/jdanek/Downloads/msbuild/Extensions

It went away when I applied it IIRC.
I'll test your new pr, with the latest msbuild, and see if I can reproduce it again.

@leo60228 Have you opened your new PR already? If not, can you link to https://github.com/NixOS/nixpkgs/issues/29817 from it when you do it (preferably with some keyword like Closes #29817), so that it can close the issue automatically once it's merged? :)

:confused: I am a bit confused, what is the state of msbuild? I can't find anything in master.

I'm not sure, @leo60228 do you still have the expression?
If you don't have enough time for it, it could still be there for someone to pick up.
It would improve the situation for getting source builds for applications that need msbuild dramatically, because we'd actually have it.

I still have it, but I don't have time for it. I'll try and push it later.

@leo60228 any progress or any chance of sharing that expressions so someone else can pick it up.
i too have the requirement for msbuild ;)

@leo60228 I would love to get msbuild in too. That way I can use NixOS for work projects.

@billksun Just BTW, there is MSBuild 16 available in dotnet core. I have it at /nix/store/klwr9h00b25ws7g7wj2iasnvl3b63xa3-dotnet-sdk-2.2.203/sdk/2.2.203/MSBuild.dll and the Rider IDE is able to detect it and use it, My only issue regarding C# on NixOS is #55435, and that has a reasonable workaround.


Is there anyway to check keyboard states, i.e. up arrow is currently pressed.

-Self-explanatory, would like to add a listener of some kind if possible.

For now you can listen to the keyboard from your App.vue and use Vue events to pass info to your overlays. I'll think about adding it as an API.

I think pushing the 'right arrow' for moving the canvas 1 candle to the right is good.
Maybe shift+right arrow should move it 10 candles to the right

I think pushing the 'right arrow' for moving the canvas 1 candle to the right is good.
Maybe shift+right arrow should move it 10 candles to the right

I assume that this particular behavior should be implemented on the application side (imagine that someone is already using arrows, and this will come as a surprise). However, It will be useful to be able to access keyboard events through the overlay API.
I'm still thinking how to implement this in the possible best way.

https://github.com/C451/trading-vue-js/commit/ead0e8ab4a7775ba8d50e95ed41586145a3a676d


Expose the Node3D.scale() method

Expose Node3D.scale() to the editor side.
Also changed the description of "rotate" to clarify that the rotation happens around the axis of the parent node.
Regarding "translate" and "translate_object_local" they seem to behave the same.

This isn't valid, you can't expose scale because there's already the scale property

Can this be exposed under another name?

Sure, unsure what name would be appropriate though
Also unsure if we should have a whole three different scaling methods, we already have global_scale and scale_object_local

If I haven't tested it wrong, this method scales along the local axes of the parent node so it's different from the other two.

Here's the difference:

I know it's different, I'm saying it'll be confusing with three different ones

It'd pair with rotation methods as there are 3 different types rotate_object_local, rotate and global_rotate.
In the end this is just a shortcut for transform.basis = transform.basis.scaled(Vector3(x, y, z))

Sorry I'm confused. Should I close this PR or change the exposed name?

Go ahead and change it and we'll see what name is agreed on

Commit & PR could use a better title since the name has changed

Such as "Expose Node3D.scale() as scale_object()" ?

Yes, correct


1.12.2 - Crash on opening gui of newly placed machines.

It seems that getDisplayName in the tiles is called before blockType is set, this results in the following crash if you try to access the gui of a very freshly placed machine:
https://gist.github.com/Thutmose/b8c38dfdeeec54088786b15788d08d85

Yes, discovered this a few weeks ago - will be a simple fix :)

Fixed!


Fixes #22 change SMTPServerIPAddress_RemoteHosts to accept hostnames

@Klaas- Thanks for this fix, LGTM. We are looking into this. will update soon

Thank you for merging this, it was getting close to the 1 year anniversary of the PR :)


Missing v2.2.3 tag and release in this repository

Hello,
dependabot detected https://pypi.org/project/kafka-python-ng/2.2.3/ but there is no v2.2.3 tag nor GitHub release for it.
It looks like contents of .tar.gz on pypi match 9bee9fc599c473437ebec8d90dd22ae7ed7a9bc8
Thank you for keeping this project alive!

Sorry about that. There was a mistake that occurred while doing the release! I'll re-tag.

👍
https://github.com/wbarnha/kafka-python-ng/releases/tag/v2.2.3


module 'tvm.relay' has no attribute 'Module'

tvm: 0.8
error reproduce: mod = relay.Module({})

The Module has been moved to ir.Module. Please open new discussion thread on https://discuss.tvm.apache.org/ for further related questions

The Module has been moved to ir.Module. Please open new discussion thread on https://discuss.tvm.apache.org/ for further related questions


[enhance][elasticsearchapi] - use three way merge to diff elasticsearch objects

Like, k8s-objectmatcher, use a generic function to implement three way merge. We can use metadata to store the original.

It's ok


chore: bump griffe to >=0.33, <=0.38

BREAKING CHANGE: This commit may break renderers implemented by
downstream users if they use the griffe.expressions module.
Over the past 8 months (and about 10 releases), griffe has had
2 releases that have broken quartodoc. So the griffe requirement
is set to include only the current known working versions.

griffe has moved quite along and has had some nice improvements. e.g. v0.36 fixed the issue of inherited parameters.

Thanks so much for looking into this, and submitting the PR. I'm going to try migrating py-shiny's custom renderer quickly, to get a feel for griffe's new expression API, and then will merge!

I hope it's okay--I removed the upper bound on griffe. If they release any more breaking changes, happy to pin an upper bound (and also open to rethinking my approach to upper bounds 😅)