timing issue with KMS auth policy

 2024/09/09 10:03:41 Terraform apply | Error: [ERROR] Error when creating resource instance: Please contact the Service Provider for this error. [422, Unprocessable Entity] The Secrets Manager instance failed to access the selected root key. Verify that the key exists in the selected key management service instance. with resp code: {
 2024/09/09 10:03:41 Terraform apply |     "StatusCode": 422,
 2024/09/09 10:03:41 Terraform apply |     "Headers": {
 2024/09/09 10:03:41 Terraform apply |         "Cache-Control": [
 2024/09/09 10:03:41 Terraform apply |             "max-age=0, no-cache, no-store"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Content-Length": [
 2024/09/09 10:03:41 Terraform apply |             "547"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Content-Type": [
 2024/09/09 10:03:41 Terraform apply |             "application/json; charset=utf-8"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Date": [
 2024/09/09 10:03:41 Terraform apply |             "Mon, 09 Sep 2024 10:03:29 GMT"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Expires": [
 2024/09/09 10:03:41 Terraform apply |             "Mon, 09 Sep 2024 10:03:29 GMT"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Pragma": [
 2024/09/09 10:03:41 Terraform apply |             "no-cache"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Request-Id": [
 2024/09/09 10:03:41 Terraform apply |             "bss-0e9320aaca0df6a1"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Retry-After": [
 2024/09/09 10:03:41 Terraform apply |             "0"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Server": [
 2024/09/09 10:03:41 Terraform apply |             "istio-envoy"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Strict-Transport-Security": [
 2024/09/09 10:03:41 Terraform apply |             "max-age=31536000;includeSubDomains"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "Transaction-Id": [
 2024/09/09 10:03:41 Terraform apply |             "bss-e2189442ce987368"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Content-Type-Options": [
 2024/09/09 10:03:41 Terraform apply |             "nosniff"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Correlation-Id": [
 2024/09/09 10:03:41 Terraform apply |             "bss-e2189442ce987368"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Envoy-Upstream-Service-Time": [
 2024/09/09 10:03:41 Terraform apply |             "17209"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Op-Completion-Time": [
 2024/09/09 10:03:41 Terraform apply |             ""
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Ratelimit-Limit": [
 2024/09/09 10:03:41 Terraform apply |             "100"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Ratelimit-Remaining": [
 2024/09/09 10:03:41 Terraform apply |             "99"
 2024/09/09 10:03:41 Terraform apply |         ],
 2024/09/09 10:03:41 Terraform apply |         "X-Ratelimit-Reset": [
 2024/09/09 10:03:41 Terraform apply |             "0"
 2024/09/09 10:03:41 Terraform apply |         ]
 2024/09/09 10:03:41 Terraform apply |     },
 2024/09/09 10:03:41 Terraform apply |     "Result": {
 2024/09/09 10:03:41 Terraform apply |         "details": "{\"error\":\"Bad Request\",\"description\":\"The Secrets Manager instance failed to access the selected root key. Verify that the key exists in the selected key management service instance.\"}",
 2024/09/09 10:03:41 Terraform apply |         "error_code": "RC-ServiceBrokerErrorResponse",
 2024/09/09 10:03:41 Terraform apply |         "message": "Please contact the Service Provider for this error. [422, Unprocessable Entity] The Secrets Manager instance failed to access the selected root key. Verify that the key exists in the selected key management service instance.",
 2024/09/09 10:03:41 Terraform apply |         "status_code": 422,
 2024/09/09 10:03:41 Terraform apply |         "transaction_id": "bss-e2189442ce987368"
 2024/09/09 10:03:41 Terraform apply |     },
 2024/09/09 10:03:41 Terraform apply |     "RawResult": null
 2024/09/09 10:03:41 Terraform apply | }
 2024/09/09 10:03:41 Terraform apply |
 2024/09/09 10:03:41 Terraform apply |
 2024/09/09 10:03:41 Terraform apply |   with module.secrets_manager.ibm_resource_instance.secrets_manager_instance[0],
 2024/09/09 10:03:41 Terraform apply |   on ../../main.tf line 35, in resource "ibm_resource_instance" "secrets_manager_instance":
 2024/09/09 10:03:41 Terraform apply |   35: resource "ibm_resource_instance" "secrets_manager_instance" {
 2024/09/09 10:03:41 Terraform apply |

Looks like the depends_on id wrong here: https://github.com/terraform-ibm-modules/terraform-ibm-secrets-manager/blob/dd819a8c62bc4c6b135b0e4ee1ed396848bbc6da/main.tf#L37
It should depends on the time sleep (as a workaround for https://github.com/IBM-Cloud/terraform-provider-ibm/issues/4478). The time sleep already exists but want being used in the SM instance creation block

Even with the correct time sleep in place, the issue is still seen.
Summary from logs:

2024/09/09 11:45:32:  key created successfully
2024/09/09 11:46:09: KMS s2s auth policy created successfully
 2024/09/09 11:46:39: Start of SM instance creation
 2024/09/09 11:46:56: Error occurs: [422, Unprocessable Entity] The Secrets Manager instance failed to access the selected root key. Verify that the key exists in the selected key management service instance.

So you can see that the 30 second sleep is in place between the time the auth policy was created and the time SM provisioning started.
On re-run it passed, so its still a backend timing issue here, as opposed to any bug in our logic. I don't really want to increase the sleep past 30 seconds, as this is usually more than enough time.
I'm going to close this, and keep an eye on the frequency of occurrences here. Hoping this is a once off backend slowness issue.


Remove version: SillyKoalaHugs.IdleEucalytus version 1.1.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sillykoala.eu.org/?smd_process_download=1&download_id=86
OK
(Automated message - build 908)

URL: https://sillykoala.eu.org/?smd_process_download=1&download_id=86
OK
(Automated message - build 908)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 885.)

URL: https://sillykoala.eu.org/?smd_process_download=1&download_id=86
Status Code: 200
(Automated message - build 886)

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Edit: Package still available.


return with error from _log_request_list() in case of failed allocation

In case of failed allocation of LogListHelper, the next lines can cause hardfault.
This didn't happen to me, but still its good practice to protect from that.
As more widen question, why LogListHelper is a class at all? why its not part of MavlinkLogHandler?
I think that removing as much as possible dynamic allocations is good practice.
My only thought is to save some RAM, and try to allocate it only if and when Log need to be download. LogListHelper is about 150 bytes.

I think your criticism is fair. Please feel free to send a follow-up PR that allocates the class at compile time.

Great, thanks!


iOS + SQLCipher = SQLite.SQLiteException: not an error

Hello everyone,
I'm having an issue when trying to enable SQLCipher in iOS (Android seems to be working fine).
Probably I'm missing some obvious step.
Steps to reproduce:

Create a new Xamarin project with Visual Studio 2019 Enterprise (latest version)
Add reference to both sqlite-net-pcl and sqlite-net-sqlcipher (1.7.335) on both .net standard common project and iOS project
Add the following in App.xaml.cs (.net standard common project)

        protected override void OnStart()
        {
            try
            {
                var databasePath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData), "dh-test.db3");
                File.Delete(databasePath);
                //var options = new SQLiteConnectionString(databasePath, true);
                var options = new SQLiteConnectionString(databasePath, true, key: "password");
                //var options = new SQLiteConnectionString(databasePath, true, key: "password", postKeyAction: c => { c.Execute("PRAGMA cipher_compatibility = 3"); });

                var encryptedDb = new SQLiteConnection(options);

                encryptedDb.Execute("create table Stock(Symbol varchar(100) not null)");
            }
            catch (Exception ex)
            {
                Debug.WriteLine(ex.ToString());
            }
        }

Run on iPhone 12 Pro (iOS 14.4.2) with Hot restart
Stare at the brilliant "not an error" exception threw by SQLiteConnection

SQLite.SQLiteException: not an error
  at SQLite.SQLiteCommand.ExecuteNonQuery () <0x103847570 + 0x00142> in <b7f631d5fc1944c0bd63336596c11967>:0
  at SQLite.SQLiteConnection.Execute (System.String query, System.Object[] args) <0x103830280 + 0x0006c> in <b7f631d5fc1944c0bd63336596c11967>:0
  at SQLite.SQLiteConnection.SetKey (System.String key) <0x10382fb38 + 0x0003c> in <b7f631d5fc1944c0bd63336596c11967>:0
  at SQLite.SQLiteConnection..ctor (SQLite.SQLiteConnectionString connectionString) <0x103840d08 + 0x001e2> in <b7f631d5fc1944c0bd63336596c11967>:0
  at SqlCipher.App.OnStart () [0x0002b] in C:\Users\EugenioFavalli\source\repos\SqlCipher\SqlCipher\SqlCipher\App.xaml.cs:33 }

Any help is appreciated, I can share the project source if needed.
Thanks in advance

@praeclarum or @sjlombardo any hint on this issue?

Hello @elvenprogrammer:

you should not add both sqlite-net-pcl and sqlite-net-sqlcipher, use one or the other.
Capture the result of PRAGMA cipher_version. If it returns 0 rows, you are not using SQLCipher (see https://github.com/praeclarum/sqlite-net/issues/986#issuecomment-697967001)
If it returns the expected result and you have a dependency on SQLitePCL.raw 2.0.5, use this patch https://github.com/praeclarum/sqlite-net/pull/1026

Hi @sjlombardo thanks for the precise answer.

you should not add both sqlite-net-pcl and sqlite-net-sqlcipher, use one or the other.

Makes sense, I just kept slite-net-sqlcipher

Capture the result of PRAGMA cipher_version. If it returns 0 rows, you are not using SQLCipher

Not sure, but I tried:
    var opt = new SQLiteConnectionString(databasePath, true, key: "password");   var db = new SQLiteConnection(opt);   var version = db.ExecuteScalar<string>("PRAGMA cipher_version");
which again throws the not an error error. If I remove the key than I get a null which I think is to be expected?

If it returns the expected result and you have a dependency on SQLitePCL.raw 2.0.5, use this patch

Not sure again, as far as I can understand it seems to me slite-net-sqlcipher is bringing in SQLitePCL.raw.bundle_e_sqlcipher 2.0.3

I don't know if it makes sense but I tried to isolate more the problem by including the packages only in the iOS project.
I tried with both sqlite-net-sqlcipher and SQLitePCL.raw.bundle_e_sqlcipher, or adding them alone one at a time.
Tested quite a lot of combinations inside FinishedLaunching, without success, I think I'm doing something really stupid, but I can't figure out what.
Any example or better a quickstart example would be really appreciated.
public override bool FinishedLaunching(UIApplication app, NSDictionary options)
        {
            SQLitePCL.Batteries_V2.Init();

            try
            {
                var databasePath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData), "dh-test.db3");
                if (File.Exists(databasePath))
                    File.Delete(databasePath);
                //var opt = new SQLiteConnectionString(databasePath, true);
                var opt = new SQLiteConnectionString(databasePath, true, key: "password");
                //var opt = new SQLiteConnectionString(databasePath, true, key: "password", postKeyAction: c => { c.Execute("PRAGMA cipher_compatibility = 3"); });

                var db = new SQLiteConnection(opt);

                //db.Execute("create table Stock(Symbol varchar(100) not null)");
                var version = db.ExecuteScalar<string>("PRAGMA cipher_version");
            }
            catch (Exception ex)
            {
                Debug.WriteLine(ex.ToString());
            }

            global::Xamarin.Forms.Forms.Init();
            LoadApplication(new App());

            return base.FinishedLaunching(app, options);
        }

Hello @elvenprogrammer

If I remove the key than I get a null which I think is to be expected?

That is actually not expected. Regardless of whether a key is provided, if the SQLCipher is properly linked and loaded at runtime then PRAGMA cipher_version will return a version string. The fact that it is not indicates that SQLCipher is not properly linked in your app.
I don't think your code is at fault, rather there is likely something in your project introducing another non-SQLCipher SQLite library (the system libsqlite). Are you using any other nuget packages that could be introducing a transitive dependency on sqlite-net-pcl?

Hi @sjlombardo
this is all I get:

And the repro project attached for you convenience.
SqlCipher.zip


Use dhcp and ovn agent images from OpenstackVersion

Related-Issue: OSPRH-6639
Resolves: OSPRH-6747
Depends-On: https://github.com/openstack-k8s-operators/openstack-operator/pull/818

/appove

/approve

Marked as draft as would require updating go.mod once depends-on pr merges

Marked as draft as would require updating go.mod once depends-on pr merges

updated


🚀 Feature: support http proxy

🔖 Feature description
in some companies, application need use http proxy to visit Internet site. but backstage does not support proxy which configured in env variable.
🎤 Context
those situations need proxy:

import template from github
run 'yarn backstage-cli version:bump' to upgrade backstage

✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Indeed, thanks for linking. I'll close this for now. The article has a little bit of rationale; the way proxying works in node is a bit special.


Feat/4010 pass primitive features

@PipKat : I've added **kwargs as an argument when primitives are created thereby making it possible to set a property when the primitive is instantiated.  This will simplify syntax and improve consistency as some methods use explicit keyword arguments that have inconsistent naming. For example non_model=True which is used to set the property model to False. There is, however, a conflict between PEP and IronPython syntax.
   **kwargs,
   )

is allowed for PEP but causes the IronPython unit test to fail.

Allow primitive properties to be set on instantiation by passing named arguments.


fix: log flickering on clear screen

Instead clearing the screen when requested, we just store the message (usually the RERUN XXX message) and then on first log/error received we check if we have the pending log/error and log to the console the pending log/error and the message at once.
https://streamable.com/92bizj
EDIT: only tested on IntelliJ on windows, we should check it also on macos and linux and also on VSCode. We also need to check it on multiple tests changes.
@dominikg can you check this on linux on IntelliJ/WebStorm (sorry to ping you direclty)

We should also change the message on clearScreen to required string

we can add ansi-escapes and use it to clear the screen: https://github.com/sindresorhus/ansi-escapes

with ansi-escapes equivalent, the flickering is still there, appears less (check the _clearScreen method): https://streamable.com/kjgduo

It does reduce the "flicker" on linux too.
However i have 2 concerns with this

it complicates the clearscreen api by requiring to pass a message to it
the effect on ux feels contraproductive: The "flicker" is a visual indicator that a rerun happens. Without it slight changes (like the expectation change in the video) appear mostly static which may be misunderstood as "test was not rerun". vitest may be a victim of it's speed here :see_no_evil:

The feedback issue is interesting. It is expected in a web app HMR but here it may be surprising as you suggest. I think it could still lead to a better DX, but we may need to give feedback somehow. Maybe a color flash for the error? But it starts to get more complex... IMO this is still good, but it isnt straightforward at the end

@dominikg about the first entry, it is internal and used only when rerun tests on changes or when deleting tests
@patak-dev maybe we can randomize the RERUN color, currently using blue
On Vite we have a plugin to delay the dev server startup, also a plugin to notify HMR updates on dev, maybe we can add here a system notification (joking) :joy:

Changing the color of RERUN is interesting, but it may also be confusing to users. Maybe we could add a char next to rerun that changes from one run to the next?
Something like a spinner that is rotating as you do changes?
There seem to be some good ones:
2 steps:
◩ -> ◪ -> ◩ -> ◪

◒ -> ◓ -> ◒ -> ◓

4 steps:
◑ -> ◒ -> ◐ -> ◓

Changing the color of RERUN is interesting

Maybe we can add a number of reruns to RERUN? Like RERUN (3)

Something like a spinner that is rotating as you do changes?

https://streamable.com/6ipv4b

Changing the color of RERUN is interesting

Maybe we can add a number of reruns to RERUN? Like RERUN (3)

The problem it is global, we should one per test: the RERUN log is anbout the current test, not the global, and also what happens when pressing a?

So, what's up with this PR? 👁 👁

@sheremet-va: with the latest tests I did, it seems that we need to change the way we send the messages to the console, the flicker can't be removed as we do now (IIRC, the command to clean and to run the tests is produce from different modules and in an asynchronous way), I need to review it (I'll try to pick it up on my vacation): anyway, the PR is in draft, you can close it, but don't delete the branch (a few weeks ago I cleaned my laptop and I don't know if I have it locally)

https://user-images.githubusercontent.com/11247099/178035018-3a769a96-f1e2-4688-92b9-febf77fcfb90.mp4
Made it like this

I love how stable it is, and I understand the idea but at least to me it feels strange that the console will keep constantly updating. It could be distracting while looking at the results. If you go this way, I would prefer a single "Updated" is shown and then it disappears. When updating too quickly, the Updated may not disappear between updates but it is fine since the last time it goes away is enough feedback. Maybe it could be full bright first, and then go with a low-key color, then disappear, kind of like an opacity animation.

https://user-images.githubusercontent.com/11247099/178042178-c926672f-0ede-4c1d-b64d-0aed3bfd0694.mp4
🫠

on windows also looks good, there is no flickering, the force=false do the trick.

Merging this for now and we can iterates if later we have better idea of presenting the updates


Button clicking doesn't work sometimes

Summary
When trying to click a button, it sometimes doesn't click
Reproduction Steps
It happens way too randomly, but the way it happens with me is when I try to click a button, it doesnt click, and then returns an error like asyncio timeout error. And no it's not an index error
Code
# both vars are int, defined, and are within the correct index of the message
await response.components[components_num].children[children_num].click()

Expected Results
I guess the buttons should always click
Actual Results
Sometimes it doesn't click, sometimes it does. but most of the time it doesnt
System Information

Python v3.10.3-final
discord.py-self v2.0.0-alpha

discord.py-self pkg_resources: v2.0.0a2

aiohttp v3.8.1
system info: Windows 10 10.0.22000

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
No response

Try adding a ms delay before clicking

It always works when running a "small" number of instances/accounts and/or executing lesser button clicks.
This usually occurs (for me) only when I run too many accounts through the lib, clicking too many buttons at the same time.

Not related to the bug or anything, but i can't seem to find out how to get the components from a slash command (discord.Slashcommand). Mind explaining me how you managed to find information on it?

Duplicate of #380

Pretty sure this is not a duplicate and still remains a bug. Your explanation stated in #380

gateway closing at an inopportune time
does not explain the REPEATED behaviour- I get it if it errors once in a thousand times, but it errors almost once in every 10 times
@Sxvxgee can confirm as we have tested this alot and everything produces the same result


[test] Adjust IRGen tests to be ptr size agnostic

This is a preparation to enable executable tests against WebAssembly, which is 32-bit platform.
Resolves part of rdar://116488131

@swift-ci Please smoke test


Latest release doesn't provide Firefox addon (.xpi)

Latest release (1.4.7) includes source code archives only. Please consider adding ready-to-use add-on (.xpi) for the Firefox browser.

I've addressed this in another issue thread https://github.com/gabrielecirulli/hn-special/issues/33#issuecomment-239920928. I know it's been awhile, because the work needed to remove dependencies on innerHTML is frustrating. There is no obvious replacement for our small, well-scoped use of it from what I can find.
I'll count this thread as another vote for the short-term workaround (self-signed xpi) and close it for now. Thanks for taking the time to post, I appreciate hearing that others want to use the Firefox version too. :)


Fix numerous issues with Use Before Declaration

Fixes #505 and VSO 5425942
Emit() needs to visit all AST nodes so that various algorithms can
collect data and set info on symbols and such, assign locations etc.
In our implementation of the let/const lexical variable Use Before
Declaration error, we had a call to EmitUseBeforeDeclaration() at the
beginning of Emit() and would exit early if it decided to emit the error
into the bytecode.  This would prevent visitation of subtrees in certain
cases, like e.g. issue #505.  It would do this for assignments, i.e.
stores.  Detection for Use Before Declaration for loads (and typeof)
are done in EmitPropLoad and EmitPropTypeof.
This fix pushes Use Before Declaration detection for stores down into
EmitPropStore and fixes up where we clear the needsDeclaration flag on
symbols that we weren't doing exactly right for EmitPropStore to work
this way.
Summary of changes

Tweak parse tree tracing to note deferred funcs
Change EmitPropStore to emit static UseBeforeDecl
Consolidate Emit() of knop[Var|Let|Const]Decl
Reduce code duplication in TrackMemberNodesInObjectForIntConstants
Add missing EmitUseBeforeDeclaration in EmitReference for knopCall
Remove EmitUseBeforeDeclaration for knopVarDecl case in Emit()
Remove redundant parameter fLoadUndef from
EmitUseBeforeDeclarationRuntimeError().  Use the presence of the
location parameter to indicate that a LdUndef is needed instead.
Remove fAcquire param from EmitUseBeforeDeclaration
Remove pnodeNeedUndef parameter from EmitUseBeforeDeclaration
Remove always true fAssignRegs parameter from EmitApplyCall.
Removed call to EmitUseBeforeDeclaration in
EmitCallTargetNoEvalComponents.  This was the only remaining call
that used pnodeNeedUndef, hence ability to remove that parameter
from EmitUseBeforeDeclaration.
Added three test cases to unittests

@pleath @Microsoft/chakra-es please review

I like it already. (But I’ll look in detail tomorrow.)
--Paul
From: Ian Halliday<EMAIL_ADDRESS>Sent: Thursday, May 5, 2016 6:45 PM
To: Microsoft/ChakraCore<EMAIL_ADDRESS>Cc: Paul Leathers<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/ChakraCore] Fix numerous issues with Use Before Declaration (#936)
@pleathhttps://github.com/pleath @Microsoft/chakra-eshttps://github.com/orgs/Microsoft/teams/chakra-es please review
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/ChakraCore/pull/936#issuecomment-217328395

I forgot to note that I ran test262 with and without my changes.  No new failures were introduced by my change.

Very nice cleanup. Ship it.

Otherwise LGTM

Appreciate the cleanup effort. Looks good.

Looks good to me as well.


3d tileset could not be loaded in electron environment after cesium was packaged, but it worked perfectly when imported through cdn url

cesiumWorkerBootstrapper.js:30 Uncaught Error: importScripts failed for app://ThirdParty/Workers/draco_decoder_nodejs.js at app://ThirdParty/Workers/draco_decoder_nodejs.js
http://requirejs.org/docs/errors.html#importscripts
at makeError (cesiumWorkerBootstrapper.js:30)
at Function.req.load (cesiumWorkerBootstrapper.js:30)
at Object.load (cesiumWorkerBootstrapper.js:30)
at r.load (cesiumWorkerBootstrapper.js:30)
at r.fetch (cesiumWorkerBootstrapper.js:30)
at r.check (cesiumWorkerBootstrapper.js:30)
at r.enable (cesiumWorkerBootstrapper.js:30)
at Object.enable (cesiumWorkerBootstrapper.js:30)
at r. (cesiumWorkerBootstrapper.js:30)
at cesiumWorkerBootstrapper.js:30
makeError @ cesiumWorkerBootstrapper.js:30
req.load @ cesiumWorkerBootstrapper.js:30
load @ cesiumWorkerBootstrapper.js:30
load @ cesiumWorkerBootstrapper.js:30
fetch @ cesiumWorkerBootstrapper.js:30
check @ cesiumWorkerBootstrapper.js:30
enable @ cesiumWorkerBootstrapper.js:30
enable @ cesiumWorkerBootstrapper.js:30
(anonymous) @ cesiumWorkerBootstrapper.js:30
(anonymous) @ cesiumWorkerBootstrapper.js:30
each @ cesiumWorkerBootstrapper.js:30
enable @ cesiumWorkerBootstrapper.js:30
init @ cesiumWorkerBootstrapper.js:30
(anonymous) @ cesiumWorkerBootstrapper.js:30
setTimeout @ cesiumWorkerBootstrapper.js:25
req.nextTick @ cesiumWorkerBootstrapper.js:30
o @ cesiumWorkerBootstrapper.js:30
requirejs @ cesiumWorkerBootstrapper.js:30
(anonymous) @ decodeDraco.js:1

Hi do you have any information on how your app was built or served? You'll likely need to host the static files, including the ThirdParty directory.

Thank you. I built the project with vue-cli5.0+electron, and all functions work normally after packing it into the desktop. Only part of the 3d tileset gave an error, which should be that the draco_decoder_nodejs.js path could not be found

Thanks @xiaobaiQJ. You should make sure you are  somehow statically serving the SourceThirdParty directory along with your app. For example, this is how we recommend serving the static files using webpack.


Implementing Hill Cipher in Go

💥 Proposal
Implementing Hill Cipher in Go.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


[Orleans] Add support for Orleans serialization.

We need to modify Result and Status to be something like this...
[GenerateSerializer]
[Alias("OperationResult.Result`2")]
public class Result<TResult, TError>
{
    [Id(0)]
    public readonly TResult Value;

    [Id(1)]
    public readonly TError Error;

    [Id(2)]
    public bool IsSuccess { get; set; }

    [Id(3)]
    public bool IsError { get; set; }

   // .. omitted
}

This feature was added in this PR


Start updating location type CSV to contain LocationType.id

A start at remodelling some of the location stuff to add filters.

Closing as these won't actually be used.
See #857


Dynamic Width

Is there any way to achieve dynamic width using setPreferredSize() instead of using Percentage Layout?

You can write your own layout. It is not a big deal. If you  give me few tips regarding the rules UI components have to be ordered, I can try to help you with a code or snippet.


Not Resolving. Again!

Hello;
The new version, as i described for older version, after restart, sleep or shutdown, can't resolve.
we must go to the windows services and 'restart' both dnscrypt services manually to back them again.
I got this problem before, in my windows 10, but i now use windows 7.i'm sure this is your fault.

Well, maybe the dnscrypt-proxy services doesn't start automatically, which were disabled or disturbed by some software you installed and used.
I have not meet this issues, which I use it for a long time on several computers (including Windows 10/8.1/7 x64). However, I have tested that VMWare Bridge Protocol is considered as a incompatible reason: Connection issuse with VMWare Bridge Protocol enabled my be it can be helpful for you.


JS_CONTROLLER_STOPPED

Gerade mal aufs "geradewohl" ein manuelles update von github gestartet, nun startet der Adapter nicht mehr.

host.raspberrypi
2022-12-19 09:16:54.378
error
instance system.adapter.bluelink.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

host.raspberrypi
2022-12-19 09:16:54.378
error
Caught by controller[0]:     at node:internal/main/run_main_module:22:47

host.raspberrypi
2022-12-19 09:16:54.378
error
Caught by controller[0]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)

host.raspberrypi
2022-12-19 09:16:54.378
error
Caught by controller[0]:     at Function.Module._load (node:internal/modules/cjs/loader:868:12)

host.raspberrypi
2022-12-19 09:16:54.378
error
Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1033:32)

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1119:27)

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]:     at wrapSafe (node:internal/modules/cjs/loader:1084:15)

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]:     at Object.compileFunction (node:vm:360:18)

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]: SyntaxError: Invalid or unexpected token

host.raspberrypi
2022-12-19 09:16:54.377
error
Caught by controller[0]:

host.raspberrypi
2022-12-19 09:16:54.376
error
Caught by controller[0]:                     let airTempF = (airTempC.val × 9/5) + 32;

host.raspberrypi
2022-12-19 09:16:54.376
error
Caught by controller[0]: /opt/iobroker/node_modules/iobroker.bluelink/main.js:99

Hab´s orginal mit ioBroker auf die 2.2.6. upgedated und nun tut es wieder :-)


Descriptor:user_data_segment() does not have Flags::LONG_MODE set

The doc-comment of the function states Creates a segment descriptor for a long mode ring 3 data segment.
I have not made a pull request to change this as i'm unsure if Flags::LONG_MODE is deliberately not set. My knowledge of the intricacies of x86_64 is sorely lacking.

This is intentional. For more information see section 4.8 of the AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.
Basically, in Long mode (which includes 64-bit mode and compatibility mode) Data segments are almost completely ignored. From the manual:

Segment-limit checking is not performed on any data segments in 64-bit mode, and both the segment-limit field and granularity (G) bit are ignored. The D/B bit is unused in 64-bit mode.
The expand-down (E), writable (W), and accessed (A) type-field attributes are ignored.
A data-segment-descriptor DPL field is ignored in 64-bit mode, and segment-privilege checks are not
performed on data segments. System software can use the page-protection mechanisms to isolate and
protect data from unauthorized access.

In practice this means that a Data Segment (for either the user or the kernel) only needs to set Flags::USER_SEGMENT  and Flags::PRESENT, and not set Flags::EXECUTABLE, every other flag is ignored.
We actually  set Flags::WRITABLE and Flags::DPL_RING_3 unnecessarily which probably confuses things.

#181 clarifies some of the documentation here, but I think this can be closed.

Thanks for looking into this @josephlr!


Detected blocking call error

During startup of HASS OS on a Respberry Pi 5, I can see an error message containing a stack trace which contains a message to report the information here.
Note: I reported the first 3 lines from the log shown below on Home Assistants github page but included these here just in case they are the cause of the error shown after the 3 lines.
2024-12-10 13:33:42.867 WARNING (MainThread) [hass_nabucasa.remote] Invalid certificate found for: ([***REDACTED***].ui.nabu.casa)
2024-12-10 13:34:03.017 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: automation, lovelace, mqtt.button, met, frigate, http, todo, google_assistant.button, mqtt.switch, input_number, sonoff.number, mqtt, google_generative_ai_conversation.conversation, image_upload, input_select, recorder, onboarding, radio_browser, config, mobile_app.binary_sensor, persistent_notification, hacs.switch, energy, image, smartthings.sensor, cast, dhcp, diagnostics, rpi_power.binary_sensor, homeassistant.scene, sonoff.remote, blueprint, system_health, google_cloud.tts, hardware, ffmpeg, number, device_tracker, webhook, hassio.sensor, shopping_list.todo, auth, met.weather, mqtt.light, hassio, logbook, cloud.stt, light, input_button, application_credentials, smartthings.light, mobile_app, smartthings.scene, frontend, cast.media_player, mobile_app.notify, hacs, mqtt.lock, smartthings.binary_sensor, my, input_datetime, homeassistant_alerts, fan, google_translate, tag, hacs.update, analytics, history, mobile_app.sensor, cloud.binary_sensor, assist_pipeline, default_config, energy.sensor, mqtt.binary_sensor, smartthings.fan, device_automation, soundtouch, weather, stream, timer, bluetooth, shopping_list, smartthings.climate, select, hassio.binary_sensor, media_source, mqtt.update, repairs, input_boolean, camera, frigate.camera, binary_sensor, api, homeassistant, sensor, zone, sonoff.button, frigate.switch, cloud, schedule, hassio.update, frigate.binary_sensor, raspberry_pi, frigate.number, sonoff.climate, script, stt, google_generative_ai_conversation, sonoff.sensor, counter, sonoff.light, sonoff, intent, smartthings.switch, google_cloud, button, google_translate.tts, tts, command_line.sensor, system_log, frigate.sensor, scene, ssdp, wake_word, group, rpi_power, google_cloud.stt, smartthings.cover, cloud.tts, switch, command_line, lock, mobile_app.device_tracker, smartthings, search, person, mqtt.number, frigate.update, cover, websocket_api, remote, sonoff.binary_sensor, sonoff.fan, group.light, notify, logger, sonoff.cover, smartthings.lock, network, usb, conversation, sonoff.switch, climate, zeroconf, trace, mqtt.select, soundtouch.media_player, update, media_player, go2rtc, input_text, frigate.image, sun, file_upload, backup, google_assistant, mqtt.sensor, sun.sensor The system is waiting for tasks: {<Task pending name='Task-295' coro=<AbstractConfig.async_initialize.<locals>.sync_google() running at /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2024-12-10 13:34:16.558 WARNING (MainThread) [hass_nabucasa.cloud_api] Fetched https://remotestate.nabucasa.com/request_sync (404)
2024-12-10 13:35:50.404 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args ('/usr/local/lib/python3.13/site-packages/pytz/zoneinfo/Africa/Abidjan', 'rb') inside the event loop by custom integration 'frigate' at custom_components/frigate/media_source.py, line 464: ) - (dt.datetime.now(pytz.timezone(timezone)).utcoffset() or dt.timedelta()) (offender: /usr/local/lib/python3.13/site-packages/pytz/__init__.py, line 108: return open(filename, 'rb')), please create a bug report at https://github.com/blakeblackshear/frigate-hass-integration/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 708, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 679, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2027, in _run_once
    handle._run()
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 480, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_app.py", line 569, in _handle
    return await handler(request)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/http.py", line 57, in get
    return await WebSocketHandler(request.app[KEY_HASS], request).async_handle()
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/http.py", line 343, in async_handle
    await self._async_websocket_command_phase(connection)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/http.py", line 494, in _async_websocket_command_phase
    async_handle_str(command_msg_data)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/connection.py", line 237, in async_handle
    handler(self.hass, self, schema(msg))
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 47, in schedule_handler
    hass.async_create_background_task(
  File "/usr/src/homeassistant/homeassistant/core.py", line 873, in async_create_background_task
    task = create_eager_task(target, name=name, loop=self.loop)
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task
    return Task(coro, loop=loop, name=name, eager_start=True)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/media_source/__init__.py", line 207, in websocket_resolve_media
    media = await async_resolve_media(hass, msg["media_content_id"], None)
  File "/usr/src/homeassistant/homeassistant/components/media_source/__init__.py", line 170, in async_resolve_media
    return await item.async_resolve()
  File "/usr/src/homeassistant/homeassistant/components/media_source/models.py", line 84, in async_resolve
    return await self.async_media_source().async_resolve_media(self)
  File "/config/custom_components/frigate/media_source.py", line 568, in async_resolve_media
    server_path = identifier.get_integration_proxy_path(
  File "/config/custom_components/frigate/media_source.py", line 464, in get_integration_proxy_path
    ) - (dt.datetime.now(pytz.timezone(timezone)).utcoffset() or dt.timedelta())

2024-12-10 13:36:05.500 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 380, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "aiohttp/_http_parser.pyx", line 558, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadHttpMessage: 400, message:
  Data after `Connection: close`:

    b'HELP'
       ^

this is a duplicate of https://github.com/blakeblackshear/frigate-hass-integration/issues/688


[ Indy ] Documentation determining the success of BAF Indy network deployment

Changelog

Update Indy Network Verification steps

Reviewed by
@sownak
Linked issue
#885

No more a valid PR; please create new PR for the closure of the issue


Collapse plugin not finding trigger when targeting a class or multiple ids

Potential fix: PR  #19779
When a collapse panel is targeting either a class or a comma separated list of ids, the trigger's class and aria attributes are not updated.
Use case 1, "class":

item

item

item

item

item

item

<button type="button" data-toggle="collapse" data-target=".mylist">show/hide</button>

Use case 2, "multliple ids":

item

item

item

item

item

item

<button type="button" data-toggle="collapse" data-target="#mylist1,#mylist2">show/hide all</button>

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


Doctrine\ODM\MongoDB\LockException when using versioning, a custom name for the version field and embedMany

I have a versioned document, with a version field, using a custom name.
"version" is the field name I use in the PHP object and "_version" is the name I use in the underlying document.
I have added an embedMany field and can no longer update my document.
A Doctrine\ODM\MongoDB\LockException is thrown.
It seems that the problem comes from the CollectionPersister, that adds the version field name to the query, when it should instead use the related field mapping name.

Thanks @bmichalski! Hopefully it'll be one last place of infamous name vs fieldName issue, but frankly I hope so every time I see such PR :)

Ah, just noticed before pushing merge button, @bmichalski could you please retarget your PR for 1.x branch? That may require an additional rebase for your commit to be the only one.

I cherry-picked the commit and changed the base branch to doctrine:1.1.x, is this ok?

That'll do, thanks @bmichalski! Offhand there's neat rebase --onto if you'd ever need to do such thing again and had more than 1 commit to move :)

@malarzm thank you for the advice :)
I'm not familiar with the lifecycle of this project: will there be a 1.1.5 tag soon now that the fix has been merged?

Usually we waited a bit if no more issues would arise, but I can tag new version somewhen this week if it's needed. Also you can always depend on 1.1.x branch

I'm a bit behind on my OSS work due to paid work issues, but I'll tag 1.1.5 and 1.2.0 within the next few days. It's long overdue anyways.

Release tagged - we haven't tagged a release in a couple of months, so it's ok to tag for just one fix.


Invalid HTTP Request

Describe the bug
Logs are producing "WARNING: Invalid HTTP request received."
To Reproduce
docker run -it -v <path>/config:/config -e ECOWITT2MQTT_CONFIG=/config/config.yaml -p 8080:8080 bachya/ecowitt2mqtt:2023.07.0
My config file is:
---
endpoint: /data/report
input_unit_system: imperial
mqtt_broker: emqx.<fqdn>
mqtt_port: 1883
mqtt_username: EW2MQTT
mqtt_password: # no password required for my emqx
mqtt_topic: ew2mqtt
output_unit_system: imperial
port: 8080
raw_data: false
verbose: true # changed this to try to get better errors without success
diagnostics: true # ditto

My hub settings are:

Expected behavior
A working ecowitt2mqtt install, however at the moment I'd just like to understand the problem.
Additional context
I am assuming I've misconfigured something, however I think this is still a valid bug report as I'm stuck debugging because of the vague log warning.

Please provide the entire log—since you've set verbose, we may get a clue there.

I changed the mqtt_broker below (and above) since I didn't want to share my insecure mqtt broker.
We renamed asyncio-mqtt to aiomqtt and released a version 1.0.0 in the process. This is the last release under the asyncio-mqtt name. You can find the new repository at https://github.com/sbtinstruments/aiomqtt
2023-07-14 14:37:52,196 | DEBUG | Input CLI options/environment variables: {'config': '/config/config.yaml'}
2023-07-14 14:37:52,196 | DEBUG | Configs loaded: <Configs _configs={'default': {'config': '/config/config.yaml', 'endpoint': '/data/report', 'input_unit_system': 'imperial', 'mqtt_broker': 'emqx.<path>', 'mqtt_port': 1883, 'mqtt_username': 'EW2MQTT', 'mqtt_password': None, 'mqtt_topic': 'ew2mqtt', 'output_unit_system': 'imperial', 'port': 8080, 'raw_data': False, 'verbose': True, 'diagnostics': True, 'mqtt_retain': False, 'input_data_format': <InputDataFormat.ECOWITT: 'ecowitt'>, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>, 'battery_override': {}, 'disable_calculated_data': False, 'mqtt_tls': False}}
2023-07-14 14:37:52,202 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
2023-07-14 14:37:52,202 | DEBUG | Starting runtime
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
WARNING:  Invalid HTTP request received.
2023-07-14 14:38:14,393 | DEBUG | Stopping runtime
2023-07-14 14:38:14,394 | DEBUG | Runtime shutdown complete

It's the third line from the bottom. --> WARNING:  Invalid HTTP request received.
After I got the warning, I shut the container down. Before I filed the bug report, it had been running for at least a half-hour (hoping it might just fix itself) which had just resulted in one of those messages every 20s.

Ah, sorry, I missed that. What specific weather station/gateway do you have?

Ambient WS-5000-IP. The hub is running version 'OBSERVERIP2_V2.2.3'.

Thanks! I think you're seeing this error because, by default, ecowitt2mqtt expects the ecowitt data format; since you have an Ambient Weather–branded station, you'll need to use the ambient_weather format (more info here. Add input_data_format: ambient_weather to your config file and restart the app.
(As an aside, although I can't directly detect this scenario—there are a few reasons why ecowitt2mqtt might receive an invalid HTTP request—I'll see if I can add a log message reminding the user to check their input data format.)

Same error; I've attached new logs (removing my domain as before):
We renamed asyncio-mqtt to aiomqtt and released a version 1.0.0 in the process. This is the last release under the asyncio-mqtt name. You can find the new repository at https://github.com/sbtinstruments/aiomqtt
2023-07-15 16:25:23,082 | DEBUG | Input CLI options/environment variables: {'config': '/config/config.yaml'}
2023-07-15 16:25:23,082 | DEBUG | Configs loaded: <Configs _configs={'default': {'config': '/config/config.yaml', 'endpoint': '/data/report', 'input_data_format': <InputDataFormat.AMBIENT_WEATHER: 'ambient_weather'>, 'input_unit_system': 'imperial', 'mqtt_broker': 'emqx.impetuo.us', 'mqtt_port': 1883, 'mqtt_username': 'EW2MQTT', 'mqtt_password': None, 'mqtt_topic': 'ew2mqtt', 'output_unit_system': 'imperial', 'port': 8080, 'raw_data': False, 'verbose': True, 'diagnostics': True, 'disable_calculated_data': False, 'mqtt_tls': False, 'battery_override': {}, 'mqtt_retain': False, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>}}
2023-07-15 16:25:23,086 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
2023-07-15 16:25:23,086 | DEBUG | Starting runtime
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
WARNING:  Invalid HTTP request received.
WARNING:  Invalid HTTP request received.
WARNING:  Invalid HTTP request received.
2023-07-15 16:26:09,529 | DEBUG | Stopping runtime
2023-07-15 16:26:09,529 | DEBUG | Runtime shutdown complete

Thanks for trying. I'm going to put together a Docker image with some more debug info; I'll send to you when it's ready.

Give this image a try. Let's remove diagnostics and just keep verbose in your config—let things run for a bit (i.e., try to grab a few instances of this bad request), then post the logs back here. Thanks!

I commented out verbose and am running docker run -it -v <path>/config:/config -e ECOWITT2MQTT_CONFIG=/config/config.yaml -p 8080:8080 bachya/ecowitt2mqtt:pr-636, and I'm getting the same log output:
We renamed asyncio-mqtt to aiomqtt and released a version 1.0.0 in the process. This is the last release under the asyncio-mqtt name. You can find the new repository at https://github.com/sbtinstruments/aiomqtt
2023-07-16 00:15:06,959 | DEBUG | Input CLI options/environment variables: {'config': '/config/config.yaml'}
2023-07-16 00:15:06,960 | DEBUG | Configs loaded: <Configs _configs={'default': {'config': '/config/config.yaml', 'endpoint': '/data/report', 'input_data_format': <InputDataFormat.AMBIENT_WEATHER: 'ambient_weather'>, 'input_unit_system': 'imperial', 'mqtt_broker': 'emqx.<fqdn>', 'mqtt_port': 1883, 'mqtt_username': 'EW2MQTT', 'mqtt_password': None, 'mqtt_topic': 'ew2mqtt', 'output_unit_system': 'imperial', 'port': 8080, 'raw_data': False, 'verbose': True, 'disable_calculated_data': False, 'mqtt_retain': False, 'diagnostics': False, 'mqtt_tls': False, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>, 'battery_override': {}}}
2023-07-16 00:15:06,963 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
2023-07-16 00:15:06,963 | DEBUG | Starting runtime
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
WARNING:  Invalid HTTP request received.
WARNING:  Invalid HTTP request received.
WARNING:  Invalid HTTP request received.
2023-07-16 00:16:10,824 | DEBUG | Stopping runtime
2023-07-16 00:16:10,824 | DEBUG | Runtime shutdown complete

However, it still says version 2023.07.0 (which could be correct if you didn't change the version). Is there somewhere else the log is being saved or did I do something wrong? I had thought you were more verbosity. On the other hand, I can also just let it run? Let me know.

That image has the same version, so don't worry about that. I was definitely expecting more verbosity, especially around what the invalid HTTP request actually was. I'll investigate and get back to you.

I can only reproduce the Invalid HTTP request received log line by sending a request to https://IP:PORT/data/report (notice https). Can you confirm that you're not attempting to upload to HTTPS at that endpoint?

I apologize, I don't know how to confirm that. I don't have a proxy or anything that is redirecting the http request, and I haven't made any changes to the hub/gateway since my screenshot above (which just uses the host IP of the linux box using to test the docker container on).
Is there a way to set up an open API that will accept any http request on port 8080 at /data/report (likely via a different container entirely, maybe even one that exists) so I can give you the raw http post that's creating the issue? I don't know enough about web APIs, etc, to know how to do that, so it may be a simple idea with a complicated execution.

I just ran netcat (nc -l -p 8080) on the host and grabbed one of the http posts:
GET /data/reportMAC=94:3C:C6:44:B2:FB
&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-16+01:41:32&tempf=82.04&humidity=83&windspeedmph=3.58&windgustmph=9.17&maxdailygust=23.26&winddir=175&winddir_avg10m=144&uv=0&solarradiation=0.00&hourlyrainin=0.000&eventrainin=0.000&dailyrainin=0.000&weeklyrainin=0.898&monthlyrainin=1.803&yearlyrainin=1.803&totalrainin=1.803&battout=1&battrain=1&tempinf=79.52&humidityin=58&baromrelin=29.988&baromabsin=29.849&battin=1&lightning_day=5&lightning_time=1689458285&lightning_distance=34&batt_lightning=0 HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: OBSERVERIP2

I don't know if that is a complete post or not, but is that what (or part of what) you're expecting?

Yes, that's what I was looking for. With that raw payload, I can at least reproduce the Invalid HTTP request received. Will follow up.

Please pull this image (same tag, so you may need to do a docker pull) and try again—with this one, your example payload published fine on my side.

Okay, so it's still not working, but I decided to try something on my end to see if I can help troubleshoot:
First, the docker logs haven't changed (even after pulling the latest pr-636).
2023-07-16 23:30:09,064 | DEBUG | Input CLI options/environment variables: {'config': '/config/config.yaml'}
2023-07-16 23:30:09,065 | DEBUG | Configs loaded: <Configs _configs={'default': {'config': '/config/config.yaml', 'endpoint': '/data/report', 'input_data_format': <InputDataFormat.AMBIENT_WEATHER: 'ambient_weather'>, 'input_unit_system': 'imperial', 'mqtt_broker': 'emqx.<fqdn>', 'mqtt_port': 1883, 'mqtt_username': 'EW2MQTT', 'mqtt_password': None, 'mqtt_topic': 'ew2mqtt', 'output_unit_system': 'imperial', 'port': 8080, 'raw_data': False, 'verbose': True, 'disable_calculated_data': False, 'battery_override': {}, 'mqtt_retain': False, 'diagnostics': False, 'mqtt_tls': False, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>}}
2023-07-16 23:30:09,068 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
2023-07-16 23:30:09,068 | DEBUG | Starting runtime
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
WARNING:  Invalid HTTP request received.
WARNING:  Invalid HTTP request received.
2023-07-16 23:30:34,397 | DEBUG | Stopping runtime
2023-07-16 23:30:34,398 | DEBUG | Runtime shutdown complete

So I grabbed another netcat:
GET /data/reportMAC=94:3C:C6:44:B2:FB
&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-16+23:31:35&tempf=80.06&humidity=84&windspeedmph=3.36&windgustmph=4.03&maxdailygust=16.55&winddir=200&winddir_avg10m=212&uv=0&solarradiation=88.48&hourlyrainin=0.000&eventrainin=1.559&dailyrainin=1.559&weeklyrainin=1.559&monthlyrainin=3.362&yearlyrainin=3.362&totalrainin=3.362&battout=1&battrain=1&tempinf=79.52&humidityin=60&baromrelin=29.914&baromabsin=29.775&battin=1&lightning_day=9&lightning_time=1689520556&lightning_distance=14&batt_lightning=0 HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: OBSERVERIP2

After restarting the new container, I submitted (a version) of that request:
curl '<IP_ADDRESS>:8080/data/reportMAC=94:3C:C6:44:B2:FB&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-16+23:31:35&tempf=80.06&humidity=84&windspeedmph=3.36&windgustmph=4.03&maxdailygust=16.55&winddir=200&winddir_avg10m=212&uv=0&solarradiation=88.48&hourlyrainin=0.000&eventrainin=1.559&dailyrainin=1.559&weeklyrainin=1.559&monthlyrainin=3.362&yearlyrainin=3.362&totalrainin=3.362&battout=1&battrain=1&tempinf=79.52&humidityin=60&baromrelin=29.914&baromabsin=29.775&battin=1&lightning_day=9&lightning_time=1689520556&lightning_distance=14&batt_lightning=0'

and the docker container/pr-636 got the following log output (e.g. worked):
2023-07-16 23:33:04,220 | DEBUG | Input CLI options/environment variables: {'config': '/config/config.yaml'}
2023-07-16 23:33:04,221 | DEBUG | Configs loaded: <Configs _configs={'default': {'config': '/config/config.yaml', 'endpoint': '/data/report', 'input_data_format': <InputDataFormat.AMBIENT_WEATHER: 'ambient_weather'>, 'input_unit_system': 'imperial', 'mqtt_broker': 'emqx.<fqdn>', 'mqtt_port': 1883, 'mqtt_username': 'EW2MQTT', 'mqtt_password': None, 'mqtt_topic': 'ew2mqtt', 'output_unit_system': 'imperial', 'port': 8080, 'raw_data': False, 'verbose': True, 'mqtt_tls': False, 'mqtt_retain': False, 'diagnostics': False, 'battery_override': {}, 'disable_calculated_data': False, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>}}
2023-07-16 23:33:04,224 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
2023-07-16 23:33:04,224 | DEBUG | Starting runtime
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
2023-07-16 23:33:06,327 | DEBUG | Received data payload: {'MAC': '94:3C:C6:44:B2:FB', 'stationtype': 'OBSERVERIP2_V2.2.3', 'dateutc': '2023-07-16 23:31:35', 'tempf': '80.06', 'humidity': '84', 'windspeedmph': '3.36', 'windgustmph': '4.03', 'maxdailygust': '16.55', 'winddir': '200', 'winddir_avg10m': '212', 'uv': '0', 'solarradiation': '88.48', 'hourlyrainin': '0.000', 'eventrainin': '1.559', 'dailyrainin': '1.559', 'weeklyrainin': '1.559', 'monthlyrainin': '3.362', 'yearlyrainin': '3.362', 'totalrainin': '3.362', 'battout': '1', 'battrain': '1', 'tempinf': '79.52', 'humidityin': '60', 'baromrelin': '29.914', 'baromabsin': '29.775', 'battin': '1', 'lightning_day': '9', 'lightning_time': '1689520556', 'lightning_distance': '14', 'batt_lightning': '0', 'PASSKEY': '943CC644B2FB'}
2023-07-16 23:33:06,328 | DEBUG | Creating MQTT loop: 3fb513e11ccb401d8dce1d27290de4f0
INFO:     <IP_ADDRESS>:50790 - "GET /data/reportMAC%3D94%3A3C%3AC6%3A44%3AB2%3AFB%26stationtype%3DOBSERVERIP2_V2.2.3%26dateutc%3D2023-07-16%2B23%3A31%3A35%26tempf%3D80.06%26humidity%3D84%26windspeedmph%3D3.36%26windgustmph%3D4.03%26maxdailygust%3D16.55%26winddir%3D200%26winddir_avg10m%3D212%26uv%3D0%26solarradiation%3D88.48%26hourlyrainin%3D0.000%26eventrainin%3D1.559%26dailyrainin%3D1.559%26weeklyrainin%3D1.559%26monthlyrainin%3D3.362%26yearlyrainin%3D3.362%26totalrainin%3D3.362%26battout%3D1%26battrain%3D1%26tempinf%3D79.52%26humidityin%3D60%26baromrelin%3D29.914%26baromabsin%3D29.775%26battin%3D1%26lightning_day%3D9%26lightning_time%3D1689520556%26lightning_distance%3D14%26batt_lightning%3D0 HTTP/1.1" 204 No Content
2023-07-16 23:33:06,338 | DEBUG | Sending CONNECT (u1, p0, wr0, wq0, wf0, c1, k60) client_id=b''
2023-07-16 23:33:06,343 | DEBUG | Received CONNACK (0, 0)
2023-07-16 23:33:06,343 | DEBUG | Publishing payload: {'MAC': '94:3C:C6:44:B2:FB', 'stationtype': 'OBSERVERIP2_V2.2.3', 'dateutc': '2023-07-16 23:31:35', 'tempf': '80.06', 'humidity': '84', 'windspeedmph': '3.36', 'windgustmph': '4.03', 'maxdailygust': '16.55', 'winddir': '200', 'winddir_avg10m': '212', 'uv': '0', 'solarradiation': '88.48', 'hourlyrainin': '0.000', 'eventrainin': '1.559', 'dailyrainin': '1.559', 'weeklyrainin': '1.559', 'monthlyrainin': '3.362', 'yearlyrainin': '3.362', 'totalrainin': '3.362', 'battout': '1', 'battrain': '1', 'tempinf': '79.52', 'humidityin': '60', 'baromrelin': '29.914', 'baromabsin': '29.775', 'battin': '1', 'lightning_day': '9', 'lightning_time': '1689520556', 'lightning_distance': '14', 'batt_lightning': '0', 'PASSKEY': '943CC644B2FB'}
2023-07-16 23:33:06,345 | DEBUG | No calculator found for MAC
2023-07-16 23:33:06,346 | DEBUG | Calculator found for temp: <ecowitt2mqtt.helpers.calculator.temperature.TemperatureCalculator object at 0x7f7846038550> (key: temp, value: 80.06)
2023-07-16 23:33:06,346 | DEBUG | Calculator found for humidity: <ecowitt2mqtt.helpers.calculator.humidity.RelativeHumidityCalculator object at 0x7f7846038580> (key: humidity, value: 84.0)
2023-07-16 23:33:06,347 | DEBUG | Calculator found for windspeed: <ecowitt2mqtt.helpers.calculator.wind.WindSpeedCalculator object at 0x7f7846038370> (key: windspeed, value: 3.36)
2023-07-16 23:33:06,347 | DEBUG | Calculator found for windgust: <ecowitt2mqtt.helpers.calculator.wind.WindSpeedCalculator object at 0x7f78460383d0> (key: windgust, value: 4.03)
2023-07-16 23:33:06,348 | DEBUG | Calculator found for maxdailygust: <ecowitt2mqtt.helpers.calculator.wind.WindSpeedCalculator object at 0x7f78460515e0> (key: maxdailygust, value: 16.55)
2023-07-16 23:33:06,348 | DEBUG | Calculator found for winddir: <ecowitt2mqtt.helpers.calculator.wind.WindDirCalculator object at 0x7f7846051580> (key: winddir, value: 200.0)
2023-07-16 23:33:06,348 | DEBUG | Calculator found for winddir_avg10m: <ecowitt2mqtt.helpers.calculator.wind.WindDirCalculator object at 0x7f7846051700> (key: winddir_avg10m, value: 212.0)
2023-07-16 23:33:06,349 | DEBUG | Calculator found for uv: <ecowitt2mqtt.helpers.calculator.uv.UVIndexCalculator object at 0x7f7846051760> (key: uv, value: 0.0)
2023-07-16 23:33:06,350 | DEBUG | Calculator found for solarradiation: <ecowitt2mqtt.helpers.calculator.illuminance.IlluminanceCalculator object at 0x7f78460517c0> (key: solarradiation, value: 88.48)
2023-07-16 23:33:06,350 | DEBUG | Calculator found for hourlyrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f7846051820> (key: hourlyrain, value: 0.0)
2023-07-16 23:33:06,351 | DEBUG | Calculator found for eventrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f7846051880> (key: eventrain, value: 1.559)
2023-07-16 23:33:06,351 | DEBUG | Calculator found for dailyrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f78460518e0> (key: dailyrain, value: 1.559)
2023-07-16 23:33:06,352 | DEBUG | Calculator found for weeklyrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f7846051940> (key: weeklyrain, value: 1.559)
2023-07-16 23:33:06,352 | DEBUG | Calculator found for monthlyrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f78460519a0> (key: monthlyrain, value: 3.362)
2023-07-16 23:33:06,353 | DEBUG | Calculator found for yearlyrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f7846051a00> (key: yearlyrain, value: 3.362)
2023-07-16 23:33:06,354 | DEBUG | Calculator found for totalrain: <ecowitt2mqtt.helpers.calculator.precipitation.AccumulatedPrecipitationCalculator object at 0x7f7846051a60> (key: totalrain, value: 3.362)
2023-07-16 23:33:06,354 | DEBUG | Calculator found for battout: <ecowitt2mqtt.helpers.calculator.battery.BatteryCalculator object at 0x7f7846051ac0> (key: battout, value: 1.0)
2023-07-16 23:33:06,355 | DEBUG | Calculator found for battrain: <ecowitt2mqtt.helpers.calculator.battery.BatteryCalculator object at 0x7f7846051b20> (key: battrain, value: 1.0)
2023-07-16 23:33:06,355 | DEBUG | Calculator found for tempin: <ecowitt2mqtt.helpers.calculator.temperature.TemperatureCalculator object at 0x7f7846051b80> (key: tempin, value: 79.52)
2023-07-16 23:33:06,356 | DEBUG | Calculator found for humidityin: <ecowitt2mqtt.helpers.calculator.humidity.RelativeHumidityCalculator object at 0x7f7846051b20> (key: humidityin, value: 60.0)
2023-07-16 23:33:06,357 | DEBUG | Calculator found for baromrel: <ecowitt2mqtt.helpers.calculator.pressure.PressureCalculator object at 0x7f7846051c40> (key: baromrel, value: 29.914)
2023-07-16 23:33:06,357 | DEBUG | Calculator found for baromabs: <ecowitt2mqtt.helpers.calculator.pressure.PressureCalculator object at 0x7f7846051be0> (key: baromabs, value: 29.775)
2023-07-16 23:33:06,358 | DEBUG | Calculator found for battin: <ecowitt2mqtt.helpers.calculator.battery.BatteryCalculator object at 0x7f7846051d00> (key: battin, value: 1.0)
2023-07-16 23:33:06,358 | DEBUG | Calculator found for lightning_day: <ecowitt2mqtt.helpers.calculator.lightning.LightningStrikeDistanceCalculator object at 0x7f7846051d60> (key: lightning_day, value: 9.0)
2023-07-16 23:33:06,359 | DEBUG | Calculator found for lightning_time: <ecowitt2mqtt.helpers.calculator.time.EpochCalculator object at 0x7f7846051dc0> (key: lightning_time, value:<PHONE_NUMBER>.0)
2023-07-16 23:33:06,360 | DEBUG | Calculator found for lightning_distance: <ecowitt2mqtt.helpers.calculator.lightning.LightningStrikeDistanceCalculator object at 0x7f7846051eb0> (key: lightning_distance, value: 14.0)
2023-07-16 23:33:06,360 | DEBUG | Calculator found for batt_lightning: <ecowitt2mqtt.helpers.calculator.lightning.LightningStrikeDistanceCalculator object at 0x7f7846051e80> (key: batt_lightning, value: 0.0)
2023-07-16 23:33:06,362 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,363 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,363 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,364 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,364 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,365 | DEBUG | Safe exposure only valid for non-zero UV indices (current: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': 1.0, 'battrain': 1.0, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': 1.0, 'lightning_day': 9.0, 'lightning_time':<PHONE_NUMBER>.0, 'lightning_distance': 14.0, 'batt_lightning': 0.0})
2023-07-16 23:33:06,366 | DEBUG | Wind Chill Temperature is only defined for temperatures at or below 50 F and wind speeds above 3 mph. (current temperature: 80.06, current wind speed: 3.36)
2023-07-16 23:33:06,367 | DEBUG | Sending PUBLISH (d0, q0, r0, m1), 'b'ew2mqtt'', ... (1433 bytes)
2023-07-16 23:33:06,368 | INFO | Published to ew2mqtt
2023-07-16 23:33:06,369 | DEBUG | Published data: {'MAC': '94:3C:C6:44:B2:FB', 'temp': 80.06, 'humidity': 84.0, 'windspeed': 3.36, 'windgust': 4.03, 'maxdailygust': 16.55, 'winddir': 200.0, 'winddir_avg10m': 212.0, 'uv': 0.0, 'solarradiation': 88.48, 'hourlyrain': 0.0, 'eventrain': 1.559, 'dailyrain': 1.559, 'weeklyrain': 1.559, 'monthlyrain': 3.362, 'yearlyrain': 3.362, 'totalrain': 3.362, 'battout': <BooleanBatteryState.ON: 'ON'>, 'battrain': <BooleanBatteryState.ON: 'ON'>, 'tempin': 79.52, 'humidityin': 60.0, 'baromrel': 29.914, 'baromabs': 29.775, 'battin': <BooleanBatteryState.ON: 'ON'>, 'lightning_day': 5.592340730136006, 'lightning_time': datetime.datetime(2023, 7, 16, 15, 15, 56, tzinfo=datetime.timezone.utc), 'lightning_distance': 8.699196691322676, 'batt_lightning': 0.0, 'beaufortscale': 1, 'dewpoint': 74.78352612466718, 'feelslike': 84.92080283220405, 'frostpoint': 68.07790238150552, 'frostrisk': <FrostRisk.NO_RISK: 'No risk'>, 'heatindex': 84.92080283220405, 'humidex': 38, 'humidex_perception': <HumidexPerception.SOME_DISCOMFORT: 'Some discomfort'>, 'humidityabs': 0.0013279654774776928, 'humidityabsin': 0.0013279654774776928, 'relative_strain_index': 0.2, 'relative_strain_index_perception': <RsiPerception.SLIGHT_DISCOMFORT: 'Slight discomfort'>, 'safe_exposure_time_skin_type_1': None, 'safe_exposure_time_skin_type_2': None, 'safe_exposure_time_skin_type_3': None, 'safe_exposure_time_skin_type_4': None, 'safe_exposure_time_skin_type_5': None, 'safe_exposure_time_skin_type_6': None, 'simmerindex': 97.84506559999998, 'simmerzone': <SimmerZone.INCREASED_DISCOMFORT: 'Increased discomfort'>, 'solarradiation_perceived': 80.98436045340364, 'thermalperception': <ThermalPerception.QUITE_UNCOMFORTABLE: 'Quite uncomfortable'>, 'windchill': None}
2023-07-16 23:33:07,864 | DEBUG | Stopping runtime
2023-07-16 23:33:07,865 | DEBUG | Runtime shutdown complete
2023-07-16 23:33:07,866 | DEBUG | Sending DISCONNECT

I also confirmed my broker got a mqtt message from the container. However, I'm at a bit of a loss, because I don't understand what is wrong with my configuration here, but based on what you said earlier the only way you get the Invalid HTTP request received warning is if it's https? So theoretically, something somewhere is upgrading my lan http requests to https? (That's something that wouldn't surprise me on my Kubernetes cluster running traefik, but here is just the gateway and a bare linux laptop).

Thanks for doing that! Very helpful.
I'd expect to see the second, longer log set when ecowitt2mqtt is working. So, something is different between the request made by the Ambient station and your cURL example.
One question I have when comparing your Netcat capture:
/data/reportMAC=94:3C:C6:44:B2:FB
&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-16+23:31:35&tempf=80.06&humidity=84&windspeedmph=3.36&windgustmph=4.03&maxdailygust=16.55&winddir=200&winddir_avg10m=212&uv=0&solarradiation=88.48&hourlyrainin=0.000&eventrainin=1.559&dailyrainin=1.559&weeklyrainin=1.559&monthlyrainin=3.362&yearlyrainin=3.362&totalrainin=3.362&battout=1&battrain=1&tempinf=79.52&humidityin=60&baromrelin=29.914&baromabsin=29.775&battin=1&lightning_day=9&lightning_time=1689520556&lightning_distance=14&batt_lightning=0 HTTP/1.1

...against your cURL command:
curl '<IP_ADDRESS>:8080/data/reportMAC=94:3C:C6:44:B2:FB&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-16+23:31:35&tempf=80.06&humidity=84&windspeedmph=3.36&windgustmph=4.03&maxdailygust=16.55&winddir=200&winddir_avg10m=212&uv=0&solarradiation=88.48&hourlyrainin=0.000&eventrainin=1.559&dailyrainin=1.559&weeklyrainin=1.559&monthlyrainin=3.362&yearlyrainin=3.362&totalrainin=3.362&battout=1&battrain=1&tempinf=79.52&humidityin=60&baromrelin=29.914&baromabsin=29.775&battin=1&lightning_day=9&lightning_time=1689520556&lightning_distance=14&batt_lightning=0'

...is whether the Netcat capture has a literal newline between the MAC address and the &stationtype...? If so, what happens if you put that same literal newline in your cURL command?

but based on what you said earlier the only way you get the Invalid HTTP request received warning is if it's https?

Not necessarily—that's merely the only way I could locally reproduce the Invalid HTTP request received message. There may be others that I'm not aware of.

FYI, we are beyond my actual knowledge and ability right now. I learned about netcat from a search, so I'm not particularly versed in it. I did redirect the netcat output to a file and there is a definitely a line break after the MAC in the output as below:
GET /data/reportMAC=94:3C:C6:44:B2:FB
&stationtype=OBSERVERIP2_V2.2.3&dateutc=2023-07-17+15:25:41&tempf=87.08&humidity=46&windspeedmph=2.68&windgustmph=5.14&maxdailygust=10.96&winddir=285&winddir_avg10m=310&uv=5&solarradiation=608.52&hourlyrainin=0.000&eventrainin=1.559&dailyrainin=0.000&weeklyrainin=1.559&monthlyrainin=3.362&yearlyrainin=3.362&totalrainin=3.362&battout=1&battrain=1&tempinf=79.52&humidityin=59&baromrelin=30.070&baromabsin=29.932&battin=1&lightning_day=0&lightning_time=1689551524&lightning_distance=14&batt_lightning=0 HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: OBSERVERIP2

I tried to introduce the line break into curl to test the command, but I'm not sure if it's sending. If I enclose the command with '' (on the cli, to allow the command to span two lines) I get a curl: (3) URL using bad/illegal format or missing URL (and it doesn't send). I also tried to introduce a '\n' which resulted in a successful capture at the docker container. If you know how to properly send that get request, I'll be happy to try.

No worries. I'm not sure a newline would do anything; that's just the one difference I notice.
Any other details you can give about your environment? I'm not seeing anything glaring that would explain why this is happening.

Thanks! Unfortunately, I don't have any further testing avenues at the moment; I'll keep you posted if I come across anything.

No worries--I really appreciate you trying to help debug this. I just confirmed that I'm still having the same problem when I'm on the same VLAN, so I don't think my network setup is effecting this problem.
If you'd like to close this issue, feel free; it may be one of those ephemeral things that happens only to one person under slightly different gravity or whatever.

Let's leave it open for now; I really would love to figure out what's going on and help you get unstuck.

So I have more information for you, I just don't know what it means. Using fastapi/uvicorn, I put together a basic script:
from fastapi import FastAPI

app = FastAPI()

@app.get("/")
async def get_weather_report(params: str):
    pass

I spun it using uvicorn --host <IP_ADDRESS> and directed my ambient weather station to it, which immediately starting getting the warnings. So this is a uvicorn problem -- maybe related to those extra line breaks? On a lark, I switched it to Wunderground format, and that is showing up in the uvicorn output.
I wonder if this isn't an Ambient Weather problem with their V2.2.3 firmware. I would be willing to write a support request but I want to make sure that it's actually a malformed GET before I do so?

Great find! Glad to hear that it wasn't necessarily something we had control over. Let me know if you hear from Ambient. FWIW, I've had luck emailing<EMAIL_ADDRESS>in the past.

So the only thought I had in the meantime was if you could accommodate the "wunderground" format? This is a netcat capture of that:
GET /report/ID=MCKEAN&PASSWORD=1909&tempf=89.42&humidity=54&dewptf=70.70&windchillf=89.42&winddir=269&windspeedmph=0.00&windgustmph=9.17&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.476&monthlyrainin=4.831&yearlyrainin=4.831&solarradiation=732.04&UV=6&indoortempf=79.34&indoorhumidity=55&baromin=30.135&lowbatt=0&dateutc=now&softwaretype=OBSERVERIP2_V2.2.3&action=updateraw&realtime=1&rtfreq=5 HTTP/1.0
Accept: */*
Host: <IP_ADDRESS>
Connection: Close

It looks like the (relevant) parameters it sends are the same, with the primary difference being that it opens with an ID & PASSWORD (which could safely be ignored). I looked at forking your code and doing it myself, but to be honest I can't figure out how you're separating the parameters since it sends (from what I understand is) a non-standard query. I'm only just learning about python APIs through this ticket, so again--well beyond my knowledge and ability.
I literally have no idea how much work this would be to accomplish, so if it's too much, please ignore the thought entirely.

That's a great idea and doesn't look horrible. I'll check it out and get back to you.

I've created #648 to track the addition of the WUnderground format. Since the remainder of this issue is with the Ambient gateway parser, I will close this issue—feel free to post back if you hear from them!


Handlebars lexer mishandles spinal-case identifiers

(Original issue 1034 created by dan-freeman on 2014-09-25T15:32:17.716594+00:00)
The Handlebars lexer handles spinal-case identifiers for plain variable references (e.g. {{my-var-name}}), but not in the case of named parameters and block helpers. For instance, the following is valid Handlebars:
{{#my-helper param-name=foo}}Bar{{/my-helper}}

For my-helper and param-name, though, it will only treat the characters up to the first - as part of name.

(Original comment by birkenfeld on 2014-10-07T09:21:14.117735+00:00)
Closes #1034: allow "-" in names for handlebars lexer
→ <>


refactor(#51): switch from @discordx/koa to routing-controllers

switch from @discordx/koa to routing-controllers
add SwaggerUi on /docs thanks to routing-controllers-openapi
fix error is not a SQLite database when using better-sqlite

Todo

[ ] Replace the use of KoaMetadataStorage in https://github.com/barthofu/tscord/blob/main/src/services/Logger.ts#L320
[ ] Safe delete legacy deps

[ ] @discordx/koa
[ ] koa-*


doc: ...

Hello Kaskada team,
There is a spelling mistake in README.md file. I am opening an issue for that, will rectify the spelling mistake, create a pull request.
Thank you.

[] #383


Warnings for policy components

Policy components are not part of the standard flow and thus the module generates warnings in logs for each execution.

when will that be fixed

The Problem is now not fixed ? Policies are not supported ?


Feature request: scaling_offset

There's an option for scaling_factor which increases the size of dots through multiplication (I think?), but if the value is 0 (or np.nan), it will not be visible on the map.
For instance, here is a map of stations with size_index set to the precipitation column.

Somewhere in Alaska gets a lot of rain!  I think this is addressed by https://github.com/ioam/holoviews/pull/2152 , which I hope can be resurrected and merged someday soon!

I've made a good bit of progress on https://github.com/ioam/holoviews/pull/2152 and it should be able to land in 1.11.

I'll close this since it's covered by the op proposal.


Failed to load Notion posts

Hey, I just found that the notion blog posts became empty. The site https://notion-blog.vercel.app/blog shows nothing. Could it be that the Notion's API is not accessible anymore? or they changed the response structure or something else. I have tried to use the latest notion token and it doesn't work either.

Same problem.
Notion API has probably changed.
With reference to this issue, it seems that the maximum value of the pagination limit has changed.

I solved this problem with change limit from 999 to 100.
https://github.com/ijjk/notion-blog/blob/7b39503232b98a6644f09daae61abf47533b5720/src/lib/notion/getBlogIndex.ts#L26

I solved this problem by changing limit from 999 to 100.
https://github.com/ijjk/notion-blog/blob/7b39503232b98a6644f09daae61abf47533b5720/src/lib/notion/getBlogIndex.ts#L26

Yeah, it works! Thank you.

Worked for me as well.

OK then I'll make a pull request from @skmatz patch file of https://github.com/skmatz/vml-blog/pull/2 .


Explore CI/CD using Docker machines with Jenkins

Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST

What happened:
For some linux distributions getting a vagrant variant might be difficult as some of them have moved to doing it more in the docker way. It makes sense if the CI/CD setup had an integration with docker machines too the same way it has for vagrant.
What you expected to happen:
If a viable vagrant option for a particular linux distribution then we can have a docker machine implementation to run the CI.
How to reproduce it (as minimally and precisely as possible):
This is a feature request.
Anything else we need to know?:
Environment:

kubectl get nodes
kubectl get pods --all-namespaces
kubectl get services
kubectl get sc
kubectl get pv
kubectl get pvc
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

We could use the argo project's CI-CD workflow and notes as reference for this : https://blog.argoproj.io/argo-workflow-demo-at-the-kubernetes-community-meeting-c428c3c93f9d

Moving this to openebs/e2e-infra project.


Fix too-wide clickbox on chat name

Also fix too-large clickbox on chat avatar.

r? @keybase/react-hackers

PTAL


Release/1.31.0

What
Describe what you have changed and why.
How to review
Describe the steps required to test the changes.
Who can review
Describe who worked on the changes, so that other people can review.

No idea why my changes had merge conflicts, but I've resolved them.


Fix vulnerabilities

I'm not sure if we will be safe.

What does that mean?

It means I'm not sure if doing that breaks things or not.

No one knows this until we try, that's why I'm suggesting to give it a shot :)
If it does break, we will see it. Then we can revert and report the bug etc

@KnorpelSenf Vulnerabilities can't be fixed if we upgrade the dependencies.

Why not?

Try it yourself.

@KnorpelSenf This is not a draft, you're trying to change its goal.

That's a vuln in the deps. Usually updating deps helps, and we need to do this anyway again, so why not do it now? The goal is to be up to date so that we avoid vulns.
Draft because there are pending discussions that need to be resolved, so this isn't ready to merge.

Pending discussions could be in a different PR that does the dependency upgrades. I thought you were just meaning to remove the vulnerability alerts at first.

I was, but in the most future-proof way, which would be not to rely on months-old beta versions. Do you feel like this needs to be merged fast?

Well, that's a thing, too. The warning can be nothing.

Drafting it again

@KnorpelSenf Vulnerabilities can't be fixed if we upgrade the dependencies.

I do not understand what you mean. It seems to me like all vulnerabilities are fixed if VuePress is updated to the most recent version. In addition, some bugs are fixed. For example, the production site does not remove the header anchor from the URL when scrolling to the top.

$ npm audit
found 0 vulnerabilities


Cannot read property 'length' of undefined

After recently updating the API, I started receiving this error...  Looks like it happens when the last DJ leaves the waitlist.
C:\bot\node_modules\plugapi\lib\room.js:195
        for (let i = 0; i < ids.length; i++) {
                               ^
TypeError: Cannot read property 'length' of undefined

Known bug and fixed by https://github.com/plugCubed/plugAPI/pull/140. ATM I am trying to figure out the playlist functionality as well as fixing auto reconnect before I release a new version of v5. Sorry you're getting the bug, I had to rush the release for v5 due to the role updates and did not have the proper amount of time to bug test things

Got it... I read that but didn't realize that doing an npm update wouldn't pick up that fix.

Issue should be resolved with the latest release v5.1.0, please let me know if it is not.


Move ACL-specific code from nefertari-* projects

I'm done reviewing for now. In summary I think that the two biggest issues are:

storing default acls in the db
where default item acls are defined. I don't like how they are passed back and forth between acl and model instance.


logSearch with compliance drop down - harden architecture and UI flow

FULL ISSUE DESCRIPTION PENDING
This viz is currently in MVP state for the Japan demo.
Rework the flow of data through the system as follows:
initial page load
viz and table reflect lookback selector and complete set of severity filters
refresh reached
viz and table reflect same lookback, but refreshed time span
changing lookback
viz and table reflect new time span
select/deselect filter on viz
viz and table reflect filtered results
double clicking on viz
viz zooms
table reflects subset (time and filtering) of zoomed chart
typing query in table search box
viz unchanged
table results reflect query
compliance defined_search dropdown
viz and table reflect selected query
... more details to follow regarding filtering/zoom/pagination

Moving to more recent ticket that duplicated the intent.


Password protection

Hi, thanks for your work!
Is it possible to protect the stream via password without just using basic auth?
Thanks!

Hi Martin, not right now, but I think @boerniee did this on an installation of photo-stream, not sure how though. Maybe he can chime in on this topic.

Hello 🙂
I did it with basic auth via htaccess. Sorry 🤷♂
But if you are using docker and a reverse proxy, maybe you can use Authalia or something similar.

Maybe "Keycloak" is an option.

Thanks for your suggestions :)


sudo error on resolving hostname

sudo reboot
sudo: unable to resolve host lamp

possible solution:

Error message when I run sudo: unable to resolve host (none)

solution:
$ sudo cat /etc/hosts

<IP_ADDRESS>	localhost lamp.local
::1		localhost ip6-localhost ip6-loopback
ff02::1		ip6-allnodes
ff02::2		ip6-allrouters

<IP_ADDRESS>	lamp


Add initial version of FAQ document

This PR is meant to add an initial version of our FAQ document, so we can start having this information accessible to members of the community.
Often some of these questions have to be answered over and over again, this will help mitigate some confusion. I don't plan this to be a full complete version, but the beginning in which we can add later.
Fixes #4
These are some of the questions that were gathered in this google document. Check issue #4 to see all the members who contributed to it

@vj-codes your suggestions were so spot on! 🎉 👏 💪 Thank you so much for doing this review! I addressed your comments, let me know if you see something else that can be improved ;)

@vj-codes your suggestions were so spot on! 🎉 👏 💪 Thank you so much for doing this review! I addressed your comments, let me know if you see something else that can be improved ;)

@aditmehta9 @vj-codes could you please review this PR again?

@aditmehta9 @vj-codes could you please review this PR again?

done with the changes @vj-codes @aditmehta9 💪

done with the changes @vj-codes @aditmehta9 💪

@isabelcosta VMS, portal and mentorship ios, flutter should be removed from active projects , only this change otherwise the doc looks great 🚀

@isabelcosta VMS, portal and mentorship ios, flutter should be removed from active projects , only this change otherwise the doc looks great 🚀

@vj-codes can you take a look again please?

@vj-codes can you take a look again please?

Thank you so much for your thorough reviews @vj-codes @aditmehta9 🎉

Thank you so much for your thorough reviews @vj-codes @aditmehta9 🎉


CML matrix multiplication is terribly inefficient

CML matrix multiplication is based on naive algorithm which does not take into account any cache memory optimizations. As the result matrix multiplications becomes bottleneck in any real-world applications using CML. It would be nice to implement at least some memory optimizations (https://gist.github.com/nadavrot/5b35d44e8ba3dd718e595e40184d03f0). Also it would be great to use SIMD intrinsics (https://codereview.stackexchange.com/questions/101144/simd-matrix-multiplication) if not too hard to implement in template code.

Sincere apologies for not responding to this. For some reason, I do not receive new issue notifications.
Have you observed slowdown in a real application? If so, by how much and for what size matrices?
In general, CML is targeted at small, often-changing matrices. Please correct me if I am wrong, but as I recall, cache-conscious matrix product won't make much difference unless the matrices are larger than the L1 and/or L2 cache. Consequently, I'd imagine that one of the cache-optimized BLAS implementations would be more appropriate outside of typical CML use cases.
Similarly for SIMD, if you've observed a slowdown in a real application, I'd be very interested. I haven't verified recently, but for small, fixed-size vectors and matrices, loops should be compiler-unrolled automatically. Moreover, on Intel x64, SSE is required for floating-point arithmetic, and later Visual Studio releases should auto-parallelize the loops (this may require a special command-line argument, I don't recall at the moment). I can verify this and make sure I'm not doing anything to get in the compiler's way.
Finally, I'm very much interested in these sorts of optimizations, so if you have performance data and/or code that supports your request, that would be fantastic and most welcome. (Of course, pull requests with supporting performance tests would also be welcome.)
Thank you! Demian

Hello Demian,
I've found this performance issue during optimization of the graphics sample demonstrating parallel rendering, which is a part of Methane Kit project. Methane Kit is a modern graphics API abstraction library and it is using CML as a base vector math library.
Asteroids sample demonstrates parallel rendering up to 50000 asteroids in realtime with animation updates on each frame. It was found that sample is CPU-bound because of animation updates are too slow even with multi-threaded execution. AsteroidsArray::Update function updates parameters of 50000 asteroids on each frame, including calculation of model and model-view-projection matrices, which are produced as the result of 4 multiplications of matrix44f_r for each asteroid. This results in 200000 matrix multiplications per AsteroidsArray::Update call on each frame executed in parallel 16 threads on my Intel Core i7-7820X in 16.2 ms, which is obviously to much for 60 FPS frame budget, if you want to do some render comands encoding besides calculating animations (sample was running at 40 FPS). Program was compiled on Windows 10 1909 with VS2019 MSVC 14.26 using standard CMake Release configuration flags.
To fix this I've implemented SSE-optimized template specialization of the matrix product for matrix44f_r - see modified version of cml/matrix/matrix_product.tpp. With optimized implementation in place the same AsteroidsArray::Update now takes 4.3 ms, having almost 4x performance boost on this function call. As the result sample is now running at 85 FPS with 50000 asteroids. I believe that it is possible to accelerate vector/matrix calculations on CPU even further in case of using fully SEE-optimized math library like hlslpp, but it lacks some functionality available in CML, so it is still on hold.
I think that CML is great C++ vector math library with extensive functionality, but it lacks crtically needed SSE optimizations to be used in high-performance and realtime applications. Hope that you could add these optimizations in future!

With Best Regards,
Evgeny.

Evgeny, thank you very much for the details. I will definitely look into it.
Just out of curiosity, was the slowdown in the 32-bit or 64-bit build of the Asteroids sample (or both)?
Thanks again!
Demian


Rename Denoising in Report Generated

Hi,
I noticed an issue in the report generated:
This needs to be changed from MP-PCA denoising to "Denoising". For instance, if I use Patch2Self, it still shows MP-PCA denoising:
https://github.com/PennLINC/qsiprep/blob/cd6a9605691d0c66e746b0c36d1e9020ee0bf66d/qsiprep/viz/config.json#L80
I can make a quick PR for this @mattcieslak !

Thanks, this is definitely a bug


🏃 Change manager image tag to follow release-0.3 branch

What this PR does / why we need it:
This PR changes the image used to be the release-0.3 branch

wrong branch


[9.x] Fix/db commands

@jbrooksuk @joedixon
model:show command needs this mapping too

Thanks for addressing this @joedixon ! I opened a PR at #43645 for the same issue, so I guess it can be closed.
There are two things to consider concerning your implementation:

the issue with enum types only seems to exist on MySQL databases, so we probably might want register the type mapping only on MySQL platforms.
the issue also exists for point types, so a mapping for these should probably also be added.

Hey @lupinitylabs - thanks for bringing the additional missing mapping to my attention. I've gone ahead and added some more that we were missing support for.
I'm not sure it's worth conditionally checking the database type as if it's only an issue with, for instance, MySQL, the other database types won't be impacted anyway.

Yes, I guess since we are just reading the structure anyways, just mapping it all to string might be fine.