[BUG][MINOR] Fix scripts compatible with jdk8 & jdk11

What changes were proposed in this pull request?
Ignore unrecognized jvm options and use some gc options in jdk11 to replace that of jdk8
Why are the changes needed?
When use jdk11, the startup scripts will fail
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Just use jdk11 & jdk8 to startup the scripts without any failure

@summaryzb Thanks for your work. But is it possible to dispatch java program with different options based on the jvm version?
For example, in the startup script, check java version first, then start up java with different options?

Appreciate  your kind review and advise, maybe we'd better follow the common way to fix compatible problem of JDK version  just like SPARK community.
Offering different JDK version options which have the same effect  in the same command, and then ignore unrecognized options, It will be convenient to modify options just in one shoot in the future.

would you mind point the context how spark uses the different versions of Java options?
such as launcher/src/main/java/org/apache/spark/launcher/JavaModuleOptions.java project/SparkBuild.scala

The reason to suggest the change is that it's hard to add inline comments for bash's multiple comment. It would be clear and much easy to add comments for the above chanage.

follow the suggestion

Merged to master. Thanks all.


ModuleInterface: Avoid printing @_spi enum elements in public swiftinterfaces

The @_spi attribute was accepted on enum case declarations but the cases were still printed in public swiftinterfaces, leaking the SPI. The compiler now avoids printing enum cases in public swiftinterfaces when they are declared as @_spi by checking whether the enum case declaration contains any enum elements that are SPI (enum case declarations apparently do not themselves have a copy of the attributes they were written with). The compiler now also diagnoses @_spi on enum case declarations when the enum is @frozen since all the cases of a frozen enum must be known to the client so that the memory layout for the enum can be computed.
This PR also includes tests that show that the exportability of case statements is not checked. Unfortunately this gap is not simple to close since exportability is usually checked during availability checking but availability checking isn't appropriate for case statements and there isn't existing infrastructure to check exportability independently. A follow up PR will be needed to address this.
Resolves rdar://72873771

@swift-ci please test

@swift-ci please test


Replace exclusionary words whitelist and blacklist in the places that won't impact backwards compatibility

Description
Replacing the exclusionary words whitelist and blacklist that won't impact the compatibility. Changes just in code comments, internal variables, methods and class names.
Issues Resolved
This Pull request replaces Pull request https://github.com/opensearch-project/OpenSearch/pull/1970
Resolve #1484
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Signed-off-by: Andreas<EMAIL_ADDRESS>

Can we rebase and merge this?

@aponb Care to rebase and we'll merge? Thanks.

Hi @aponb, could you please resolve the conflicts, by either manually, or merge/rebase the upstream main branch to your feature branch? So that your code change can be merged. We would ship this change in version 1.3.0 release.

Hi @aponb, could you please resolve the conflicts, by either manually, or merge/rebase the upstream main branch to your feature branch? So that your code change can be merged. We would ship this change in version 1.3.0 release.

I merged the new changes. I pushed my branch, and tests are running now!

* What went wrong:
Execution failed for task ':qa:full-cluster-restart:v1.3.0#oldClusterTest'.
> There were failing tests. See the report at: file:///var/CITOOL/workflow/OpenSearch_CI/PR_Checks/Gradle_Check/search/qa/full-cluster-restart/build/reports/tests/v1.3.0%23oldClusterTest/index.html

https://github.com/opensearch-project/OpenSearch/issues/1793

start gradle check

In log 3002:

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testOperationBasedRecovery" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testOperationBasedRecovery FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://[::1]:46235], URI [/testoperationbasedrecovery], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testoperationbasedrecovery"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:83B9FB16A0D54E1F]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:952)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testOperationBasedRecovery(FullClusterRestartIT.java:1289)

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testSnapshotRestore" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testSnapshotRestore FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://[::1]:46235], URI [/testsnapshotrestore], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testsnapshotrestore"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:A1301DCA6CEEB317]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:952)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testSnapshotRestore(FullClusterRestartIT.java:810)

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testResize" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testResize FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://<IP_ADDRESS>:39569], URI [/testresize], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testresize"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:292AEDC7B9152E53]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testResize(FullClusterRestartIT.java:1387)

In log 3002:

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testOperationBasedRecovery" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testOperationBasedRecovery FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://[::1]:46235], URI [/testoperationbasedrecovery], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testoperationbasedrecovery"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:83B9FB16A0D54E1F]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:952)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testOperationBasedRecovery(FullClusterRestartIT.java:1289)

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testSnapshotRestore" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testSnapshotRestore FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://[::1]:46235], URI [/testsnapshotrestore], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testsnapshotrestore"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:A1301DCA6CEEB317]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:952)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testSnapshotRestore(FullClusterRestartIT.java:810)

REPRODUCE WITH: ./gradlew ':qa:full-cluster-restart:v1.3.0#oldClusterTest' --tests "org.opensearch.upgrades.FullClusterRestartIT.testResize" -Dtests.seed=9E55F733A653B468 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ar-DZ -Dtests.timezone=Australia/Perth -Druntime.java=17

org.opensearch.upgrades.FullClusterRestartIT > testResize FAILED
    org.opensearch.client.WarningFailureException: method [PUT], host [http://<IP_ADDRESS>:39569], URI [/testresize], status line [HTTP/1.1 200 OK]
    {"acknowledged":true,"shards_acknowledged":true,"index":"testresize"}
        at __randomizedtesting.SeedInfo.seed([9E55F733A653B468:292AEDC7B9152E53]:0)
        at app//org.opensearch.client.RestClient.convertResponse(RestClient.java:346)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:320)
        at app//org.opensearch.client.RestClient.performRequest(RestClient.java:295)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:976)
        at app//org.opensearch.test.rest.OpenSearchRestTestCase.createIndex(OpenSearchRestTestCase.java:956)
        at app//org.opensearch.upgrades.FullClusterRestartIT.testResize(FullClusterRestartIT.java:1387)

I also got this error first. By providing a JAVA11_HOME and a JAVA8_HOME on my local machine the test did pass. Strange, that the check is not working on the server.

@aponb that error is unrelated to this change and was fixed in #2334. You may need to rebase the latest changes to get the fix.

@aponb that error is unrelated to this change and was fixed in #2334. You may need to rebase the latest changes to get the fix.

thanks. Looks green now.

Thanks @aponb for your constant quick response! I will merge it today.

Thanks @aponb for your constant quick response! I will merge it today.

Thanks again to you and also the others for your help!

Hi @aponb , you are very welcome! 😄
The automatic backport workflow failed, maybe there are some conflicts with your commit and 1.x branch.
Would you mind create a PR manually to backport the change into 1.x? So that the change can be included in version 1.3.0 .
Even if you don't have enough time, we can help you create the backport PR.

Hi @aponb , you are very welcome! smile The automatic backport workflow failed, maybe there are some conflicts with your commit and 1.x branch. Would you mind create a PR manually to backport the change into 1.x? So that the change can be included in version 1.3.0 , the code freeze date is Mar.9th (PST) Even if you don't have enough time, we can help you create the backport PR.

ok. I created a backport of the changes. See #2365


Type narrowing on class members not considering changes made by function calls

TypeScript Version:  nightly (2.1.0-dev.20161025)
Description
When the type of a class member has been narrowed from a union type (e.g. '0|1|2') to a single type (e.g. '0'), calling a member function that modifies the class member to a different type or value does not 're-widen' the type again, resulting in a conflict between what the compiler thinks is true and what is actually true.
Code
// A *self-contained* demonstration of the problem follows...
class MyTestClass {
    private _myNumber: 0|1|2 = 0;

    public doThing(): void {
        // This narrows this._myNumber to 0
        if (this._myNumber === 0) {

            // This changes _myNumber to 1 outside of this method
            this.doChangeyThing();

            // Compile error - even though _myNumber is 1, the type was narrowed to 0!
            if (this._myNumber === 1) { // error TS2365: Operator '===' cannot be applied to types '0' and '1'.
                console.log("It's 1!");
            } else {
                console.log("It's not 1!");
            }
        }
    }

    private doChangeyThing(): void {
        this._myNumber = 1;
    }
}

const thing = new MyTestClass();
thing.doThing();

Expected behavior:
Example compiles without issue. When running, the message "It's 1" is printed to the console.
Calling this.doChangeyThing() should either widen the type of this._myNumber back to '0|1|2' (if it's impossible or difficult for the compiler to analyse what doChangeyThing might do), or '1' if it is.
Actual behavior:
Compiler returns the following error:

Test.ts(12,17): error TS2365: Operator '===' cannot be applied to types '0' and '1'.

Discussed at #9998 and other issues

@RyanCavanaugh So is this a bug?
enum E { One, Two }

class C {
  e: E;
  changeToTwo() {
    this.e = E.Two;
  }
}

function f(c: C) {
  if (c.e === E.One) {
    c.changeToTwo();
    assert(c.e === E.Two); // Compile error, flow analysis still thinks c.e is E.One
  }
}

@masaeedu not a bug in terms of a literal bug (e.g. we can't just "fix" it); rather a design limitation


Argument of type '{ fields: string[]; }' is not assignable to parameter of type '{ skip?: string[]; }'.

When method .validate is used on the instance with option { fields: ['...'] } application throw error
Argument of type '{ fields: string[]; }' is not assignable to parameter of type '{ skip?: string[]; }'.
Object literal may only specify known properties, and 'fields' does not exist in type '{ skip?: string[]; }'.

To work around this issue need manually write this line
entity.validate({ skip: _.difference(Object.keys(Entity.rawAttributes), ['foo']) })
Version
"sequelize": "^4.42.0",
"sequelize-typescript": "^0.6.6",

Steps to reproduce
import { Sequelize, Model, Column } from 'sequelize-typescript';

const sequelize =  new Sequelize({
  //configs
});

class Entity extends Model<Entity> {
    @Column
    foo: string

    @Column
    bar: string
}

sequelize.addModels([Entity]);

let entity = new Entity({ foo: 'FOO' });

entity.validate({ fields: ['foo'] }).then(v => {
    console.log(v);
});

@someApprentice thanks for reporting. Looks like the options typings are incomplete. As stated here besides fields, hooks is missing as well.


update naming for better MR structure

heads up @michaelthatsit - moved the datatypes and datamanagers out of core for better separation, updated the file names for entities and their classes, and cleaned up some includes
lmk if any questions

Looks good, but img still isn't loading properly on chrome/arc for some reason, it's fine in headset. I'm also running locally so I don't think it's a render thing. I can investigate separately.


Getting the error The domain/default pair of (/Library/Developer/CommandLineTools/../Info, DVTPlugInCompatibilityUUID) does not exist

Running on Mac OS X Yosemite. Cloned repo and ran make. Getting the following message
==> make
2016-01-16 03:40:58.107 defaults[99406:1108951]
The domain/default pair of (/Library/Developer/CommandLineTools/../Info, DVTPlugInCompatibilityUUID) does not exist

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29928668-getting-the-error-the-domain-default-pair-of-library-developer-commandlinetools-info-dvtplugincompatibilityuuid-does-not-exist?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github).

To make the 'makefile' work, xcode-select command must gives the proper Xcode path.
What xcode-select -p shows in you environemnt?

[I] ~
↪ xcode-select -p                                                     0@12:22:40
/Library/Developer/CommandLineTools

Sorry for late reply. Then try to do this.
  $ xcode-select -s [Your Xcode.app Path]/Contents/Developer
  (In my case, it is "xcode-select -s /Applications/Xcode.spp/Contents/Developer" )

Then run make

Actually, with the upgrade to OS X 10.11.4 and Xcode 7.3 final, make worked fine.


Add WSO2 to adopters list

Description:
Add WSO2 to adopters list

Relevant Issues:

Type of change:

Test Plan:

Changelog Message:

Additional documentation:

@pixie-labs-buildbot , test this please.

@aimichelle we need to edit the website url to https://wso2.com/choreo/ shall i send a update to this pr or send a new pr ?

@aimichelle could you please approve again ?

@tharinduwijewardane , would you mind signing your commit by following this guide? https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification Thank you!

@aimichelle Done. I force pushed a new verified commit with the change.


Remove workaround for final-state-schema

Cleanup after resolving https://github.com/Azure/autorest.csharp/issues/3546

API change check
API changes are not detected in this pull request.

Is there a preview PR?

Is there a preview PR?

The generated SDK remain the same during the CI, no preview PR needed.

Is there a preview PR?

Tried to check the output of autorest.core, there is no difference with or without this change.

Is there a preview PR?

Tried to check the output of autorest.core, there is no difference with or without this change.

Thanks


Migration to vitest, major dependency updates

This PR includes significant changes to the node dependencies:

Typescript v5

bundler module resolution
extending node18 and strictest base tsconfigs

Vitest instead of jest
Eslint v6
Prettier v3

It also includes a fresh run of prettier formatting and minor updates to these dependencies:

node18 and aws-lambda types
serverless and serverless step functions plugin
asl-validator

I haven't review this yet but I love this: Vitest instead of jest

@kai-nguyen-aligent I'm not yet sure if we should standardise ignoring lambda handlers. I might add an ignore comment on them here though.


Add temperature and humidity to xiaomi miio air quality monitor

Proposed change
added 2 new attributes in the HASS entity:

temperature
humidity

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ x] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

@fierland please update the docs so this can be merged, thanks ✌😊

I thought I had updated the docs but I will check if the push worked
Sincerely yours,
Frank van Ierland
06-21391053

From: springstan<EMAIL_ADDRESS>Sent: Saturday, February 1, 2020 11:46:41 AM
To: home-assistant/home-assistant<EMAIL_ADDRESS>Cc: Frank van Ierland<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [home-assistant/home-assistant] Add temperature and humidity to xiaomi miio air quality monitor (#31287)
@fierlandhttps://github.com/fierland please update the docs so this can be merged, thanks ✌😊
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/pull/31287?email_source=notifications&email_token=AINVD656Q3GRGRL7WCXGX2DRAVHJDA5CNFSM4KNLWBU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQZ7UI#issuecomment-581017553, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AINVD65U4COG3MVB3BGSS5TRAVHJDANCNFSM4KNLWBUQ.

You will need to create a separate PR in https://github.com/home-assistant/home-assistant.io and link it to this one :)

Mm what did i do wrong its pull request 6f43cd4  (https://github.com/home-assistant/home-assistant.io/commit/6f43cd45546fd4640b3b9858deb770f4e5df1030) and linked to this one.
Van: springstan<EMAIL_ADDRESS>Verzonden: zaterdag 1 februari 2020 13:12
Aan: home-assistant/home-assistant<EMAIL_ADDRESS>CC: Frank van Ierland<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Onderwerp: Re: [home-assistant/home-assistant] Add temperature and humidity to xiaomi miio air quality monitor (#31287)
You will need to create a separate PR in https://github.com/home-assistant/home-assistant.io and link it to this one :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/pull/31287?email_source=notifications&email_token=AINVD673W54PC6CGJULPNC3RAVRKBA5CNFSM4KNLWBU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQ3UXI#issuecomment-581024349, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AINVD67P2P6MOW4VMK7TKCLRAVRKBANCNFSM4KNLWBUQ.

Ok looks like its there now 😊
Van: springstan<EMAIL_ADDRESS>Verzonden: zaterdag 1 februari 2020 13:12
Aan: home-assistant/home-assistant<EMAIL_ADDRESS>CC: Frank van Ierland<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Onderwerp: Re: [home-assistant/home-assistant] Add temperature and humidity to xiaomi miio air quality monitor (#31287)
You will need to create a separate PR in https://github.com/home-assistant/home-assistant.io and link it to this one :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/pull/31287?email_source=notifications&email_token=AINVD673W54PC6CGJULPNC3RAVRKBA5CNFSM4KNLWBU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQ3UXI#issuecomment-581024349, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AINVD67P2P6MOW4VMK7TKCLRAVRKBANCNFSM4KNLWBUQ.

Great 👌

I realize that they should be a separate sensor although I see more entity’s with attributes that should be different. I’m new to coding for HASS so I started with this simple extension to make the data available. Have to digg into making a this integration with multiple entities . Are there any good examples for this ?
Sincerely yours,
Frank van Ierland
06-21391053

From: springstan<EMAIL_ADDRESS>Sent: Saturday, February 1, 2020 10:44:04 PM
To: home-assistant/home-assistant<EMAIL_ADDRESS>Cc: Frank van Ierland<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [home-assistant/home-assistant] Add temperature and humidity to xiaomi miio air quality monitor (#31287)
@springstan commented on this pull request.

In homeassistant/components/xiaomi_miio/air_quality.pyhttps://github.com/home-assistant/home-assistant/pull/31287#discussion_r373804104:

@@ -33,6 +35,8 @@
PROP_TO_ATTR = {
"carbon_dioxide_equivalent": ATTR_CO2E,
"total_volatile_organic_compounds": ATTR_TVOC,

"temperature": ATTR_TEMP,

Yeah you are completely right.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/pull/31287?email_source=notifications&email_token=AINVD647NAVDUM5MXJR4KKDRAXUKJA5CNFSM4KNLWBU2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCT42TKY#discussion_r373804104, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AINVD67HIU2QQBAK4JCWOKLRAXUKJANCNFSM4KNLWBUQ.

Currently each xiaomi miio platform configures its own devices. I don't know how the device library handles multiple connection instances for the same host device.
Usually we try to have a central device connection that spawns multiple platforms that shares the central device. That would mean a major code refactor here.
If it's ok to set up multiple device connections, then we may just need to add the collection of humidity and temperature measurements to the xiaomi_miio sensor platform.


Serial output is affected by telnet debug level

Describe the bug
By default serial only outputs the initial level (debug). When the debug level is changed through telnet the serial level is also changed.
To Reproduce
Steps to reproduce the behavior:

Upload a project with remote debug
Open serial console
Login via telnet and change debug level and see how the output on the serial console is affected

Expected behavior
The serial console should not be affected by the telnet debug level. It should output all levels by default and it should be possible to change the level for serial logging it in code.
Screenshots
If applicable, add screenshots to help explain your problem.
Arduino Information:

OS: Linux Mint 19.2
IDE Arduino IDE
IDE 1.8.10
Board ESP8266

Additional context
None.

This is a feature request not a bug, it is clearly described that serial output is a mirror, so this is expected behavior atm.


Document the Ontop process

what are the principles of Ontop
wht are the advantages on Ontop
what are the limitations of Ontop
how to edit a ontop binding (SQL-SPARQL) in Protegé or elsewere
how to contribute

It is now available at https://github.com/digital-botanical-gardens-initiative/earth_metabolome_ontology/blob/main/README.md


Design column addition

Column addition should be refined.
Ideas: Edit mode, hover with "+"-Button between columns, d&d, ...

Idea 1: When users are at the edge of the board, the nav buttons turn to a column addition button. Clicking this button adds a column to the left/right:

Idea 2: When hovering between column headers, a column addition button appears, which, when pressed, adds a column at that position:

Idea 3: A new option within the board settings dialog leads to a Edit Layout menu, where templates can be selected and columns can be added, deleted, renamed, moved, and made visible/hidden. In the future, it might be a good idea to save the current layout as a new template.

@Kraft16 the last pictures are showing a nice example of how we could do it for the template page when the user wants to create a new board.


feat: Add functions for calculation of min/max received trade amount

There are 2 another options, how these calculations could be implemented:

create one single function with parameter amountType which can have value max || min and regarding this value function will calculate min or max received value.
create one single function which will always calculate and return both max and min values (some extra calculations but less functions number)

This looks fine for me.


Fix Weighted panic

Please take a look.
https://github.com/gonum/gonum/issues/1866

Codecov Report
Patch coverage: 88.23% and project coverage change: -0.53 :warning:

Comparison is base (258a51e) 73.93% compared to head (891a633) 73.40%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1867      +/-   ##
==========================================
- Coverage   73.93%   73.40%   -0.53%
==========================================
  Files         526      510      -16
  Lines       63112    61651    -1461
==========================================
- Hits        46659    45257    -1402
+ Misses      13884    13844      -40
+ Partials     2569     2550      -19

Impacted Files
Coverage Δ

stat/sampleuv/weighted.go
88.46% <88.23%> (+5.48%)
:arrow_up:

... and 24 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I'll take a look on the weekend. From an initial look, I'd like more detail on the fix in the description and less code movement.

can I change the golang version for staticcheck to 1.18?

Where do you want to do this?

Where do you want to do this?

Here. I want to set it to v1 to use v1.3.0


Update timezones.py

Corrected IST

The right approach to this needs to be discussed in https://github.com/scrapinghub/dateparser/issues/683 first, and will probably not be as trivial as this. We might need a setting to allow choosing how to interpret some timezones.


Presentation 1 - Overview - What is MLops? -- Balaji

If you are done, close this issue when you get a chance


Add run command

Execute slash commands in Mattermost.

Can be merged once commander supports ... as a parameter name.

What’s the status of this PR? Can we add this to readme as well?

Yes, but it only supports Mattermost.

@niks3089  I've updated the docs.


CIV-10356 Pointing at civil service image under testing DO NOT MERGE

JIRA link
https://tools.hmcts.net/jira/browse/CIV-10356
Change description
Pointing at civil service image under testing
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Closing as it seems this is a test PR that wasnt closed off


Generic Types containing Array's Produce Invalid Schema Ids

When we use a generic class where it's declared type is an array, it'll produce an invalid Schema Id.
For instance
[ProducesRespons(200, typeof(ServiceResponse<Foo[]>))]
Will result in the schema id of Foo[]ServiceResponse, which is invalid per Swagger documentation because of the brackets. This issue is the result of the following method.
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/9abdbf99a271de5decb2bd93c5c614632e750b32/src/Swashbuckle.AspNetCore.SwaggerGen/SchemaGenerator/SchemaGeneratorOptions.cs#L38

Good catch 👍. Should be fixed by 7a29c9c2269bde2a624a2461818cb1a7d71ec7e3


Hash stored in map causes panick, type inconsistency between JS and Ruby

We are attempting to modify the same ydoc in the browser using yjs, and on our server using yrb. I have a pretty simple setup client side (this is simplified further for the sake of this report, but captures our use case fairly):
const ydoc = new Y.Doc();
const localBinder = bindImmerYjs(ydoc.getMap("data"));

localBinder.update((s) => {
  return {
    testString: "foo",
    testInt: 1,
    testFloat: 3.1415,
    testBool: false,
    testArray: [1, "two", true],
    testHash: { a: 1, b: "2", c: false }
  }
})

This ydoc is encoded as a uint8array, base64'd, then sent to the server where it's saved to a file store. In ruby, we load this content and try to access these values. This is mostly working. Roughly, this looks like:
ydata = Base64.decode64(stored_data)
ydoc = Y::Doc.new
ydoc.transact { |tx| tx.apply(ydata.bytes.to_a) }

ymap = ydoc.get_map("data")

All that is working, but this is where we run into problems:
# Works as expected
ymap[:testString] # => "foo"
ymap[:testBool] # => false
ymap[:testFloat] # => 3.1415

# Works close enough, but still wrong
ymap[:testInt] # => 1.0 (notice this is a Float now)

# Panick!
ymap[:testArray]
ymap[:testHash]

These Panicks are identical, producing:
thread '<unnamed>' panicked at /bundle/ruby/3.1.0/gems/y-rb-0.5.2/ext/yrb/.rb-sys/stable/cargo/registry/src/index.crates.io-6f17d22bba15001f/yrs-0.16.9/src/doc.rs:775:41:
called `Option::unwrap()` on a `None` value

There's an obvious workaround here where we can encode our hashes and arrays as a JSON string, but if we're going to do that, we might as well encode the whole map as a JSON string instead of as a map in the first place.
Note that this is not a problem when we decode these values on the client side.

@eliias should I open this as an issue upstream with yrs?

@eliias should I open this as an issue upstream with yrs?

@wkirby I am traveling atm. I can take a look next week. If it's really an upstream issue I'll move the issue.

@wkirby I recall having a discussion w/ the other yrs folks about support for nested “complex” data structures (like Array, and Object). I need to check if it's technically possible to do that as long as you know what you do (there will be no conflict-free replication for nested objects). Text editors usually utilize the XML-like structure to achieve proper replication with nested data-structures.

@wkirby I actually can't reproduce the panic, even using your example values. Could you provide me a value for ydata = Base64.decode64(stored_data) -> stored_data to allow me debug this further.

@eliias Just got back from some time off myself. I'll send over the encoded document we have and work on setting up a more concise repro. There's always the chance that the error is on the encoding end with y-immer.

@eliias attached is a file containing a Base64 string that presents the error. Here's how I reproduce with this data:
ydata = File.read('ydoc.base64.txt')
ydata = Base64.decode64(ydata)
ydoc = Y::Doc.new
ydoc.transact { |tx| tx.apply(ydata.bytes.to_a) }

ymap = ydoc.get_map("data")

ymap[:testInt] # => 1.0
ymap[:testFloat] # => 3.1415
ymap[:testString] # => "foo"
ymap[:testBool] # => false

ymap[:testArray] # => Panick!
ymap[:testHash] # => Panick!

Because this blob is pulled directly from our application, the Map at data also contains the following keys:
title
fields
fieldValues
agents
signatories

In addition, the ydoc includes an XML fragment at content which is serialized tiptap state. I don't believe either of these are causing the issue, as the same problem was present without these values in the ydoc.
Here are the relevant lines from my Gemfile.lock:
    y-rb (0.5.2)
      rake (~> 13.0)
      rb_sys (~> 0.9.71)
    y-rb (0.5.2-x86_64-linux)
      rake (~> 13.0)
      rb_sys (~> 0.9.71)

And from package.json:
"immer-yjs": "^1.1.0",
...
"yjs": "^13.6.7",

On the client side, the code (roughly) to serialize this data:
const useSyncedData = (doc) => {
  const ydoc = useMemo(() => new Y.Doc(), [doc.id]);
  const [binder, setBinder] = useState(undefined);

  useEffect(() => {
    const localBinder = bindImmerYjs(ydoc.getMap("data"));

    if (localBinder) {
      setBinder(localBinder);

      // optionally set initial data
      localBinder.update((s) => {
        return {
          testString: "foo",
          testInt: 1,
          testFloat: 3.1415,
          testBool: false,
          testArray: [1, "two", true],
          testHash: { a: 1, b: "2", c: false }
        };
      });
    }

    return () => {
      localBinder.unbind();
    };
  }, [ydoc, doc]);

  return ydoc;
}

const MyReactComponent = () => {
  const { doc } = useDoc();
  const ydoc = useSyncedData(doc);

  console.log(ydoc);

  return
Oh hey, a component

}

@eliias hope I'm not bugging you, but were the above resources enough to reproduce? If not I'm happy to schedule a call to work through this together. Just shoot me an email at<EMAIL_ADDRESS>if you'd like.

title

Yeah, I am able to reproduce this in a test case with your data. I think I also found the issue, but I do not have an immediate solution right now. The logic that converts the internal CRDT representation for a Map/Array requests a new read-only transaction on the CRDT store, which is usually fine, but as the Ruby library always maintains a read-write transaction, this call panics.

@eliias I'm not super versed in Rust, so I can't comment on the hackiness present here. I really appreciate your attention on this, and do let me know if there's any other way I can assist!

@wkirby I am going to release 0.5.3 later today that includes a fix.

@eliias sorry, we moved on in our project to other things, but are returning now. I will confirm within the next week or so whether your implementation fixes our issue. Thank you so much!

@eliias sorry for re-using same issue for my problem, but I have feeling that it's same or very close
$ grep y-rb Gemfile.lock
y-rb (0.5.3-x86_64-linux)
y-rb_actioncable (0.1.6)
y-rb (>= 0.4.5)
y-rb_actioncable (~> 0.1.6)

Then in the Rails log
MyChannel#receive {"update"=>"AAFKAQK/lKqpBgAHAQVhcnJheQEoAL+UqqkGABZ0ZXN0MC42NjkwOTk1MzkyNDY1NjUyAXcWdGVzdDAuNjY5MDk5NTM5MjQ2NTY1MgA="}
thread '' panicked at 'called Option::unwrap() on a None value', /home/runner/work/yrb/yrb/tmp/cargo-vendor/yrs/src/doc.rs:775:41
and when I'm trying to reproduce it in the console
irb(main):004> require 'y-rb'; update = Base64.decode64("AAFKAQK/lKqpBgAHAQVhcnJheQEoAL+UqqkGABZ0ZXN0MC42NjkwOTk1MzkyNDY1NjUyAXcWdGVzdDAuNjY5MDk5NTM5MjQ2NTY1MgA=").unpack('C*'); doc = Y::Doc.new; doc.sync(update[3..-1]); doc.get_array('array').to_a
thread '' panicked at 'called Option::unwrap() on a None value', /home/runner/work/yrb/yrb/tmp/cargo-vendor/yrs/src/doc.rs:775:41
/home/fedora/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/y-rb-0.5.3-x86_64-linux/lib/y/array.rb:269:in yarray_to_a': called Option::unwrap()on aNone` value (fatal)
(Why [3..-1] - because of the 1st byte is yrb-actioncable's message type, the 2nd byte is y-protocol message type and the 3rd byte is the length of the update)
If I put not an YMap into the array, but a primitive
const test = test${Math.random()}
const yMap = new Y.Map()
yArray.insert(0, [test])
provider.connect()
then it works like a charm
MyChannel#receive: {"update"=>"AAEpAQHs4JKHAgAIAQVhcnJheQF3FXRlc3QwLjU1NzkyODAyODMzNjEyMQA="}
MyChannel#receive synced: ["test0.557928028336121"]
and in the console
irb(main):005> require 'y-rb'; update = Base64.decode64("AAEpAQHs4JKHAgAIAQVhcnJheQF3FXRlc3QwLjU1NzkyODAyODMzNjEyMQA=").unpack('C*'); doc = Y::Doc.new; doc.sync(update[3..-1]); doc.get_array('array').to_a
=> ["test0.557928028336121"]
May be it's me doing something wrong?

@Phaengris It is possible that Maps in an Array aren't handled properly (still). I am going to add your case as a test and try to fix.

@Phaengris I identified the issue. Map/Array does not accept nested Y data-structures in yrb. It can be fixed, but it might take a while.

@eliias thank you for investigating this :)
No rush. If you can find time to fix it, it would make me happy, but if no - no worries.
For now I switched to use xml fragments / elements which also supports data nesting, in it's own way. May be a possible drawback is some performance hit, but I didn't do any benchmarks yet to see if it is actually a problem for my project.

@eliias came back to note that the most recent published version (0.5.4) is working roughly as expected. I do have a very similar issue to @Phaengris (same error message, different proximal cause), but with a clean workaround.
The structure of our Y:Map is (roughly):
{
  title: "string",
  order: 0,
  data: {},
  dataValues: []
}

I can access all these values individually:
ydoc = Y::Doc.new
ydata = get_file_from_s3()
ydoc.transact { |tx| tx.apply(ydata.bytes.to_a) }

ymap = ydoc.get_xml_map('data')

ymap.get('title') # => 'string'
ymap.get('order') # => 0.0
ymap.get('data') # => {}
ymap.get('dataValues') # => []

So far so good! The error arises from trying to get all the values:
ymap.to_h # => Panic!
ymap.to_json # => Panic!

Results in the same error as above:
thread '<unnamed>' panicked at /home/runner/work/yrb/yrb/tmp/cargo-vendor/yrs/src/doc.rs:775:41:
called `Option::unwrap()` on a `None` value

The workaround, though:
ymap.as_json.to_h # => { title: 'string', order: 0.0, data: {}, dataValues: [] }

Anyway, from my perspective this issue can be closed out. Appreciate all your hard work!

So it looks like nested maps don't work as the only way to create a Y::Map object it to use Y::Doc#get_map as the Y::Map constructor crashes.
In javascript I can create and assign Y.Map instances without errors.
I can work around this by changing how I'm modelling data but I'd love to be told I'm wrong here!


Add scan range usage to readme

https://github.com/slatedb/slatedb/issues/409

Looks good! Thanks :D


Board Review: Event Grid

Thank you for starting the process for approval of the client library for your Azure service.  Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
** Before submitting, ensure you adjust the title of the issue appropriately **
To ensure consistency, all Tier-1 languages (C#, TypeScript, Java, Python) will generally be reviewed together.  In expansive libraries, we will pair dynamic languages (Python, TypeScript) together, and strongly typed languages (C#, Java) together in separate meetings.
The Basics

Service team responsible for the client library: Event Grid team.
Link to documentation describing the service: https://docs.microsoft.com/en-us/azure/event-grid/ and https://docs.microsoft.com/en-us/azure/event-grid/edge/.
Contact email (if service team, provide PM and Dev Lead): PM<EMAIL_ADDRESS>Dev Lead<EMAIL_ADDRESS>Dev<EMAIL_ADDRESS>
About this client library

Name of the client library:  Event Grid
Languages for this review: .Net, Java, Python, Node.js, Go.
Link to the service REST APIs: swagger specs: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.EventGrid/stable/2018-01-01/EventGrid.json

Artifacts required (per language)
We use an API review tool (apiview) to support .NET and Java API reviews.  For Python and TypeScript, use the API extractor tool, then submit the output as a Draft PR to the relevant repository (azure-sdk-for-python or azure-sdk-for-js).
.NET

Upload DLL to apiview.  Link: https://www.nuget.org/packages/Microsoft.Azure.EventGrid/
There are 2 packages under the lib directory:
•	.Net .45.2: Microsoft.Azure.EventGrid.dll
•	Net Standard: Microsoft.Azure.EventGrid.dll

Link to samples for champion scenarios:
https://docs.microsoft.com/en-us/samples/azure-samples/event-grid-dotnet-publish-consume-events/event-grid-dotnet-publish-consume-events/
https://docs.microsoft.com/en-us/dotnet/api/overview/azure/eventgrid?view=azure-dotnet

Java

Upload JAR to apiview.  Link: https://mvnrepository.com/artifact/com.microsoft.azure/azure-eventgrid
Link to samples for champion scenarios: https://docs.microsoft.com/en-us/samples/azure-samples/event-grid-java-publish-consume-events/microsoft-azure-event-grid-java-sample/

Python

Upload the api as a Draft PR.  Link to PR:
Link to samples for champion scenarios: https://docs.microsoft.com/en-us/samples/azure-samples/event-grid-python-public-consume-events/event-grid-python-public-consume-events/

TypeScript

Upload output of api-extractor as a Draft PR.  Link to PR:
Link to samples for champion scenarios: https://docs.microsoft.com/en-us/samples/azure-samples/event-grid-node-publish-consume-events/event-grid-node-publish-consume-events/

Main customer requirements to be met

Cloud event support for publish/consume events.
Optional fields
Added new extension fields by customer
https://github.com/Azure/azure-sdk-for-net/issues/10684
Support consuming batch of events, not a single one only.
https://github.com/Azure/azure-sdk-for-net/issues/10137
More/update samples:
https://github.com/Azure-Samples/event-grid-dotnet-publish-consume-events/issues/20
Improve retry mechanisms for transient failures.
Leverage the dataplane SDK by 1st party service to publish events based on cert authentication rather than SAS key authentication and have their own http client.
From a scenario point of view, Event Grid delivers these events to a variety of targets Azure functions,  Event Hubs, Azure queues etc. It would be good to think through on how to leverage these client SDKs inside an azure function to parse http request body and also how this can be used to parse an Event hub event (which is holding a cloud event/grid event json bytes).

Champion Scenarios
A champion scenario is a use case that the consumer of the client library is commonly expected to perform.  Champion scenarios are used to ensure the developer experience is exemplary for the common cases.  You need to show the entire code sample (including error handling, as an example) for the champion scenarios.

Champion Scenario 1: Publish and consume events using (custom) topics.

Problem statement: How can I publish and/or consume events?

Description: This scenario covers the way a user meets a common integration requirement in which event needs to be sent by a publisher and being consumed by a client, which in this case is a Azure function.

Estimate the percentage of developers using the service who would use the champion scenario: 40%+

Link to the code sample: https://github.com/Azure-Samples/event-grid-dotnet-publish-consume-events. Note: this sample code shows a particular handler (function) of the many supported. Please consult supported handlers.

Champion Scenario 2: Publish and consume events using system topics.

Problem statement: How can I consume control-plane events generated by Azure services?

Description: This scenario enables end-users to consume events raised by ARM from services that have been integrated (onboarded) to Event Grid. Those services that have been onboarded feature a “Events” blade (bolt icon). An example of a service with this integration is Service Bus.

Estimate the percentage of developers using the service who would use the champion scenario: 20%+

Link to the code sample: Currently there are no samples that showcase the use of Event Grid SDKs to consume events from system topics, but the consumption model of event using system topics is basically the same as custom topic’s webhooks (a type of handler). There is documentation that can shed a light of the value that they provide but the example provided uses Azure Functions and Logic Apps to consume events (not our SDK).

Champion Scenario 3: Publish and consume events using domain topics.

Problem statements: How can I publish events to be consumed by a large number of consumers in simple way (one endpoint)? How can I publish events to many consumers who have different selection criteria for those events?

Description: This scenario enable event-driven architectures at a high-scale by using Event Grid domains which may include many topics that could be published to using a single endpoint: the endpoint of the Event Grid domain.

Estimate the percentage of developers using the service who would use the champion scenario: 20%+.

Link to the code sample: https://docs.microsoft.com/en-us/azure/event-grid/how-to-event-domains?tabs=azurecli#publish-events-to-an-event-grid-domain

Champion Scenario 4: Consume events using Cloud Events 1.0 schema.

Problem statement: How can I consume events using the Cloud Events 1.0 schema?

Description:  This scenario enable users who favor to use open standards (possibly to communize their implementation among all providers they may use) to consume events using the Cloud Events 1.0 schema.

Estimate the percentage of developers using the service who would use the champion scenario:

Link to the code sample: There are no samples yet as the current SDK is yet to support Cloud Events 1.0 schema.

Champion Scenario 5: Publish and consume events using partner topics.

Problem statement: How can I consume events from third-party SaaS providers using Cloud Events specification schema?

Description:  This scenario allows end-users to consume events generated by third-party publishers using Cloud Events schema 1.0.

Estimate the percentage of developers using the service who would use the champion scenario:

Link to the code sample: We do not have a specific example, but consuming events from partner topics is similar to consuming events for custom topics. Please see the following documentation that describe how to consume events from Auth0, which is a third-party service.

Champion Scenario 6: Handle Dead lettered events.

Problem statement: How can I process events that were not able to be sent to its destination (dead lettered)?

Description:  This scenario enables to implement the Dead letter Channel integration pattern.

Estimate the percentage of developers using the service who would use the champion scenario:

Link to the code sample: https://github.com/Azure-Samples/event-grid-dotnet-handle-deadlettered-events

Champion Scenario 7: Publish and consume events on the edge.

Problem statement: How can I integrate solutions/modules/services that are deployed in containers?

Description:  This scenario is used to showcase the way a user can meet requirements to integrate two IoT modules using Event Grid.

Estimate the percentage of developers using the service who would use the champion scenario: 20%+

Link to the code sample:  https://github.com/Azure-Samples/azure-iot-edge-event-grid-sample

Examples of good scenarios are technology agnostic (i.e. the customer can do the same thing in multiple ways), and are expected to be used by > 20% of users:

Upload a file
Update firmware on the device
Recognize faces in an uploaded image

Examples of bad scenarios:

Create a client (it's part of a scenario, and we'll see it often enough in true champion scenarios)
Send a batch of events (again, part of the scenario)
Create a page blob (it's not used by enough of the user base)

Agenda for the review
A board review is generally split into two parts, with additional meetings as required
Part 1 - Introducing the board to the service:

Review of the service (no more than 10 minutes).
Review of the champion scenarios.
Get feedback on the API patterns used in the champion scenarios.

After part 1, you may schedule additional meetings with architects to refine the API and work on implementation.
Part 2 - the "GA" meeting

Scheduled at least one week after the APIs have been uploaded for review.
Will go over controversial feedback from the line-by-line API review.
Exit meeting with concrete changes necessary to meet quality bar.

Thank you for your submission

By the way, we should include a section for Golang

As part of this introduction, we should try to close on what we believe the namespace will be for this code.  I believe that it will be Azure.Messaging.EventGrid (to follow our existing guidelines where we already have a messaging group) but it would be good to close on that so the teams can move forward implementing stuff without having to do a giant re-namspacing later.

In preparation for the today's meeting, I wrote up some of the champion scenarios with examples based on hypothetical designs for a Track 2 in .NET and TypeScript.
https://gist.github.com/ellismg/7e714a574443cdca3d7aa50f9ccfd300


added CMakeLists.txt file to support cmake

mkdir build
cd build; cmake ..
make
./lcvm  path/test.mp4 -o output.csv

great, thanks


Micropub token endpoint broken after Laravel 11 upgrade

The endpoint is now returning a HTTP 419 response.
Needs to be excluded from CSRF checking

The original URLs that need replicating
    /**
     * The URIs that should be excluded from CSRF verification.
     *
     * @var array<int, string>
     */
    protected $except = [
        'api/media',
        'api/post',
        'api/token',
        'micropub/places',
        'webmention',
    ];


Remove config show in favor of parent command

I'm wondering if we should keep the subcommand with a deprecation warning for a couple of versions.

@jimmykarily yup maybe that's the better approach, I'll change it. But we lack a deprecation process atm, so my guess is that, it will just stay with that message until who knows when. Whenever we add a deprecation warning, we should know that the deprecation is then planned for the upcoming N major/minor version 100% and have a ticket for it.

@jimmykarily yup maybe that's the better approach, I'll change it. But we lack a deprecation process atm, so my guess is that, it will just stay with that message until who knows when. Whenever we add a deprecation warning, we should know that the deprecation is then planned for the upcoming N major/minor version 100% and have a ticket for it.

Yes we lack a general deprecation policy. For now, just name a version (current +2 minors?) in the deprecation notice. Even if we loose the ticket, anyone looking at the message (or the code) will be able to tell if it can be removed or not. I think we've done something similar with some cli flags in the past.


/bin/sh: 1: lake: not found

When I run python scripts/trace_repos.py, this error always occures. I find it hard to locate the "lake" mentioned here.
2023-09-26 14:27:14.437 | INFO     | __main__:main:12 - Namespace(data_path='data')
2023-09-26 14:27:43.887 | INFO     | __main__:main:26 - Repos to trace: {LeanGitRepo(url='https://github.com/leanprover/std4', commit='dbffa8cb31b0c51b151453c4ff8f00ede2a84ed8'), LeanGitRepo(url='https://github.com/JLimperg/aesop', commit='d13a9666e6f430b940ef8d092f1219e964b52a09')}
2023-09-26 14:27:44.708 | INFO     | lean_dojo.data_extraction.trace:get_traced_repo_path:131 - Tracing LeanGitRepo(url='https://github.com/leanprover/std4', commit='dbffa8cb31b0c51b151453c4ff8f00ede2a84ed8')
2023-09-26 14:27:48.106 | INFO     | __main__:main:121 - Building std4
/bin/sh: 1: lake: not found
Traceback (most recent call last):
  File "/tmp/tmp0xhcp848/workspace/build_lean4_repo.py", line 165, in <module>
    main()
  File "/tmp/tmp0xhcp848/workspace/build_lean4_repo.py", line 147, in main
    run_cmd("lake build")
  File "/tmp/tmp0xhcp848/workspace/build_lean4_repo.py", line 27, in run_cmd
    res = subprocess.run(cmd, shell=True, capture_output=capture_output, check=True)
  File "/mnt/cache/luzimu/ReProver/reproverenv/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'lake build' returned non-zero exit status 127.

I an rather amateur and would really appreciate it if you guys could give me some suggestions as to why this error occured and how to solve it.

Hi,
Please set the environment variableVERBOSE=1 and include the logs here.

the logs are as below:
2023-09-27 10:42:19.807 | DEBUG    | lean_dojo.constants:<module>:70 - Using GitHub without authentication. Don't be surprised if you hit the API rate limit.
2023-09-27 10:42:21.031 | INFO     | __main__:main:12 - Namespace(data_path='data')
2023-09-27 10:42:44.973 | INFO     | __main__:main:26 - Repos to trace: {LeanGitRepo(url='https://github.com/JLimperg/aesop', commit='d13a9666e6f430b940ef8d092f1219e964b52a09'), LeanGitRepo(url='https://github.com/leanprover/std4', commit='dbffa8cb31b0c51b151453c4ff8f00ede2a84ed8'), LeanGitRepo(url='https://github.com/leanprover-community/mathlib4', commit='355541ae7a2455222f179dcf7f074aa2c45eb8aa')}
2023-09-27 10:42:44.973 | INFO     | lean_dojo.data_extraction.trace:get_traced_repo_path:131 - Tracing LeanGitRepo(url='https://github.com/JLimperg/aesop', commit='d13a9666e6f430b940ef8d092f1219e964b52a09')
2023-09-27 10:42:44.974 | DEBUG    | lean_dojo.data_extraction.trace:get_traced_repo_path:133 - Working in the temporary directory /tmp/tmpm9enmhba
2023-09-27 10:42:45.807 | DEBUG    | lean_dojo.data_extraction.lean:clone_and_checkout:441 - Cloning LeanGitRepo(url='https://github.com/JLimperg/aesop', commit='d13a9666e6f430b940ef8d092f1219e964b52a09')
2023-09-27 10:42:48.000 | DEBUG    | lean_dojo.data_extraction.trace:_trace_lean4:97 - Tracing LeanGitRepo(url='https://github.com/JLimperg/aesop', commit='d13a9666e6f430b940ef8d092f1219e964b52a09')
2023-09-27 10:42:48.041 | DEBUG    | lean_dojo.container:run:183 - NUM_PROCS=12 python3 build_lean4_repo.py aesop
2023-09-27 10:42:48.140 | INFO     | __main__:main:121 - Building aesop
/bin/sh: 1: lake: not found
Traceback (most recent call last):
  File "/tmp/tmpm9enmhba/workspace/build_lean4_repo.py", line 165, in <module>
    main()
  File "/tmp/tmpm9enmhba/workspace/build_lean4_repo.py", line 147, in main
    run_cmd("lake build")
  File "/tmp/tmpm9enmhba/workspace/build_lean4_repo.py", line 27, in run_cmd
    res = subprocess.run(cmd, shell=True, capture_output=capture_output, check=True)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'lake build' returned non-zero exit status 127.
Traceback (most recent call last):
  File "/home/SENSETIME/luzimu/theorm/ReProver/scripts/trace_repos.py", line 33, in <module>
    main()
  File "/home/SENSETIME/luzimu/theorm/ReProver/scripts/trace_repos.py", line 29, in main
    trace(repo)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/data_extraction/trace.py", line 162, in trace
    cached_path = get_traced_repo_path(repo)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/data_extraction/trace.py", line 134, in get_traced_repo_path
    _trace(repo)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/data_extraction/trace.py", line 66, in _trace
    _trace_lean4(repo)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/data_extraction/trace.py", line 104, in _trace_lean4
    container.run(
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/container.py", line 193, in run
    execute(cmd, capture_output=capture_output)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/utils.py", line 117, in execute
    raise ex
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/site-packages/lean_dojo/utils.py", line 112, in execute
    res = subprocess.run(cmd, shell=True, capture_output=capture_output, check=True)
  File "/home/SENSETIME/luzimu/theorm/ReProver/reproverenv/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'NUM_PROCS=12 python3 build_lean4_repo.py aesop' returned non-zero exit status 1.

From the logs, it looks like LeanDojo is running outside Docker. Did you set the environment variable CONTAINER?

If you want to run outside Docker, you'll have to install elan: https://github.com/leanprover/elan

The problems have been solved. Thank you very much!


TestResetFirstSequence sometimes seem to deadlock

https://travis-ci.org/zero-os/0-Disk/jobs/242714975
https://api.travis-ci.org/jobs/242714975/log.txt?deansi=true
goroutine 733 [chan receive, 4 minutes]:
github.com/zero-os/0-Disk/tlog/tlogserver/server.TestResetFirstSequence(0xc428fd1520)
	/home/travis/gopath/src/github.com/zero-os/0-Disk/tlog/tlogserver/server/reset_first_seq_test.go:69 +0x44e
testing.tRunner(0xc428fd1520, 0xd632a8)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/testing/testing.go:657 +0x96
created by testing.(*T).Run
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/testing/testing.go:697 +0x2ca

goroutine 786 [IO wait, 4 minutes]:
net.runtime_pollWait(0x2ab20c754378, 0x72, 0x11784e0)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/runtime/netpoll.go:164 +0x59
net.(*pollDesc).wait(0xc4200ef1e8, 0x72, 0x1173770, 0xc42000c780)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/fd_poll_runtime.go:75 +0x38
net.(*pollDesc).waitRead(0xc4200ef1e8, 0xffffffffffffffff, 0x0)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/fd_poll_runtime.go:80 +0x34
net.(*netFD).accept(0xc4200ef180, 0x0, 0x1176ca0, 0xc42000c780)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/fd_unix.go:430 +0x1e5
net.(*TCPListener).accept(0xc420091748, 0xc420725f30, 0xb7b076, 0x458080)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/tcpsock_posix.go:136 +0x2e
net.(*TCPListener).Accept(0xc420091748, 0xd63228, 0x1181060, 0xc42000ec90, 0xc42bda1540)
	/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/tcpsock.go:228 +0x49
github.com/zero-os/0-Disk/tlog/tlogserver/server.(*Server).Listen(0xc42bda1540)
	/home/travis/gopath/src/github.com/zero-os/0-Disk/tlog/tlogserver/server/server.go:85 +0x69
created by github.com/zero-os/0-Disk/tlog/tlogserver/server.TestResetFirstSequence
	/home/travis/gopath/src/github.com/zero-os/0-Disk/tlog/tlogserver/server/reset_first_seq_test.go:37 +0xf9

might related to #241

Only happen on travis, can't reproduce it

Seems suspicious that this issue is closed without a fix. Did this ever occur again on travis @iwanbk?

happens again today on travis, not sure if it worth to fix considering we will remove this feature anyway.
see #319

No for now that's fine I think, in case we decide later we don't remove this feature, than we do have to fix this. But for now it's OK.

This issue triggered again today a failure on travis. I'll be happy when this is gone...

Yeah, it needs #273, and not just the issue, but the test itself will be gone


Restrict outbound clipboard

This patch adds configuration option to xrdp-chansrv that turns copying from the session to clipboard.

Awesome! Good work!

Existing codes use environment variable to pass config parameter. For example, CHANSRV_LOG_PATH.
Of course environment variable is not the best way but consider using environment variable or let's discuss.

Should env be the only way of setting restriction on the clipboard or additional method? In my opinion config is less surprising.

One unacceptable point is chansrv is opening and reading sesman's config file sesman.ini. Please don't do that. Then you'll see how clipboard restriction flag should be passed sesman to chansrv.

Adding RestrictOutboundClipboard parameter to sesman.ini is OK. It's not surprising at all.  The parameter must be fetched by sesman because it is sesman.ini.

OK. Sesman gathers info from sesman.ini and then passes information about restriction to chansrv, right?

chnsrv is already reading sesman.ini here: https://github.com/neutrinolabs/xrdp/blob/devel/sesman/chansrv/chansrv.c#L1639
So it is config.c that shouldn't be used?

Indeed. That should be fixed but not at this time. I'll change it later.
I'm thinking of this. Similar thing is done as CHANSRV_LOG_LEVEL to set chansrv log level. The difference is setting environment variable directly or via config parameter.
sesman

sesman read if RestrictOutboundClipboard is on/off
sesman sets env var something like RESTRICT_OUTBOUND_CLIPBOARD to something like 1, yes, true
start chansrv with that env var

chansrv

read the env var at startup
if set to 1, restrict outbound clipboard

@metalefty Can I do something more to improve the code?

@jaroslaw-osmanski Give me some time to test.

I commented on some style & format issues but logic looks OK. After some test, I'll merge. I'd appreciate if you fix style & format before I merge.

@metalefty Fixed style and format

I'm testing this today and will be merged shortly. Sorry for the delay and thank you very much for your work!

Tested. Clipboard text/image/file LGTM.

Can I only pass text copy&paste and limit file transfer ?


Proposal: Extract main package logic into a dedicated function

In the use case for the company I work for, the krakend plugins are built in docker.
The final artifact used for deploying krakend is a docker image containing the krakend binary plus the custom plugins.
Also, it allows for greater flexibility when dealing with libraries.
As an example of how this could be useful, we have an internal library that we would like to use in our custom plugins. However, that library had defined OTEL version to 1.29, and we couldn't use it because krakend binary is fixed at 1.28.
We would probably have 2 options for this: either building krakend by ourselves, make it sure that the plugins and krakend share the exact same version, by building them together and putting them in the same go module or by downgrading the dependency specification at our internal library.
The second option imposes a challenge, because those are 2 different repos, so we reached for the first one (buildling both the plugins and krakend together).
To make this possible, all we had to do is copy/sync the contents of main.go. But this involves making it sure that our "main.go" version is always compatible with future versions of krakend.
By moving that logic into an importable function, this process is greatly simplified.

As a side note, I could recall other tooling that have a similar approach:

Caddy web server
Bramble Graphql Gateway


Question: get multiple markets in one call

is there a way to get all tickers (BTC, ETH, LTC...) in one call?
in most of the other exchanges, it's pretty straight forward.

There isn't a combined API call right now. We might want to add one in the future, for now every product needs to be queried separately.

Can you create this functionality?

any updates?


Add support for Candle

Candle is an EVM-compatible chain, L1.

Thank you for reaching out to us.
To add a new chain there has to be a bridge to that chain already. We can then aggregate that bridge and add the chain.
We are not planning to add Candle anytime soon, based on its explorer not a lot is happening on that chain: https://candleexplorer.com/txs
You can find a list of all chains we support and plan to support here:
https://docs.li.fi/products/supported-chains-bridges-and-exchanges

Thank you for reaching out to us.
To add a new chain there has to be a bridge to that chain already. We can then aggregate that bridge and add the chain.
We are not planning to add Candle anytime soon, based on its explorer not a lot is happening on that chain: https://candleexplorer.com/txs
You can find a list of all chains we support and plan to support here:
https://docs.li.fi/products/supported-chains-bridges-and-exchanges

Perceptions can be deceiving


Fi 1449 config messages

Adds a config view to show all config messages and improve current handling of error config messages.
Major changes:

Sidebar navigation tree item with icon to indicate the presence of errors/warnings
Config detail view with expandable alert items
Navigation to detail view from test suite detail view alert bars (and message truncation)

I don't understand why the config messages are shown in two places:

We also need to support markdown config messages.

I don't understand why the config messages are shown in two places:

We also need to support markdown config messages.

The error bars in the main page are for awareness while the config page is for full details.  I think long term, the config messages would benefit from having a short message field for the main error bars.  @arscan Thoughts?
FYI the main bars navigate to the config page anyway, I can come up with an alternative display if you’d like?

Codecov Report

Merging #152 (0e6b959) into main (3a282b5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0e6b959 differs from pull request most recent head 0a52511. Consider uploading reports for the commit 0a52511 to get more accurate results

@@           Coverage Diff           @@
##             main     #152   +/-   ##
=======================================
  Coverage   93.87%   93.87%
=======================================
  Files         109      109
  Lines        2744     2744
=======================================
  Hits         2576     2576
  Misses        168      168

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a282b5...0a52511. Read the comment docs.


Publishing not successful, error/reason why hidden due to column sizing

will update this issue with longer, better description -

Publish failed. No warning, no error, rocket menu has green checks for LUIS and QnA - no way to found out what happened.

Turns out this was due to the following error during provisioning: LUIS could not be provisioned due to insufficient quota
Expected: Error detail that includes this info in 'status' section of Publishing list/page.

Shiproom - @GeoffCoxMSFT can you look at this one, and once we have a root cause, we can assess if we'd take a fix for R13

@mareekuh - Could you tell me a little more about the repro steps.  What kind of project did you create? Are you using a MS or personal subscription? What options did you choose during provisioning?  What did the publishing log say?
The message in the UI is only the latest status, so it might be that something wrote an empty string last and that hides the error.

Shiproom - Per Geoff: Debugged Marieke's issue - it is a column sizing problem hiding the error when the window is narrow.  The error message is sent back and does appear when the window is wide enough (normal size).  Marieke agreed this is now a P1 for R14.

Should be fixed by reflow work


Support for darwin

@akzhan I added your binary, but I don't know if my crystalMain.ts is well configured to support this.
Can you confirm me that this extension work with the darwin binary?
The branch is https://github.com/faustinoaq/vscode-crystal-lang/tree/darwin-scry-support
BTW, thanks you!

I didnt install extensions by hands :) will do but later (2-24h).

@akzhan thanks you!
Please before do this:
git pull and recompile Scry, I added some fixes to formatting support in the tast commit, see https://github.com/faustinoaq/scry/commit/49012845ae63e74ec682bf698ff9170547aeaa24

Sorry for delay, just learned about extensions. Update package version to something high to turn off autoupdate and run extension.
Got
Error: No such module: icu
    at importPunycode (url.js:5:20)
    at url.js:11:21
    at url.js:960:3
    at NativeModule.compile (bootstrap_node.js:528:7)
    at NativeModule.require (bootstrap_node.js:468:18)
    at _http_client.js:5:13
    at _http_client.js:673:3
    at NativeModule.compile (bootstrap_node.js:528:7)
    at NativeModule.require (bootstrap_node.js:468:18

@akzhan that error is strange, I never seen Error: No such module: icu before.
Seems to be related to VSCode insiders version, see: https://github.com/Microsoft/vscode/issues/23639
Are you using VSCode Insider?
If yes, try to install VSCode latest stable version 1.13.0

Hi !
Now Scry server isn't distributed with this extension.
README message:

Scry server isn't distributed with this extension. You need to compile it from scry-vscode-crystal-lang and configure on settings.json

Please, see https://github.com/faustinoaq/vscode-crystal-lang/commit/cd116cecc31e17c717a6ee6c5c79eb417aa18dbc and https://github.com/kofno/scry/issues/3#issuecomment-312368919


setInterval RangeError: Maximum call stack

Using the preview here: https://github.com/angular/quickstart
Adding setInterval anywhere throws an error
es6-shim.js:29889 Uncaught RangeError: Maximum call stack size exceeded
es6-shim.js:29889 run
es6-shim.js:29866 zoneBoundFn
es6-shim.js:29940 fnNames.map.forEach.zone.(anonymous function).arguments.(anonymous function)
es6-shim.js:29873 (anonymous function)
es6-shim.js:29889 runes6-shim.js:29866 zoneBoundFn
es6-shim.js:29940 fnNames.map.forEach.zone.(anonymous function).arguments.(anonymous function)
es6-shim.js:29873 (anonymous function)
es6-shim.js:29889 run
es6-shim.js:29866 zoneBoundFn

The same issue:
RangeError: Maximum call stack size exceeded
STACKTRACE:
RangeError: Maximum call stack size exceeded
    at join (native)
    at VmTurnZone.$__export._onError (http://angular/quickstart/angular2/src/core/zone/vm_turn_zone.js:84:44)
    at Zone.errorHandling.onError (http://angular/quickstart/angular2/src/core/zone/vm_turn_zone.js:58:30)
    at Zone.run (http://angular/quickstart/dist/es6-shim.js:29892:14)
    at zoneBoundFn (http://angular/quickstart/dist/es6-shim.js:29866:19)
    at arguments.(anonymous function) (http://angular/quickstart/dist/es6-shim.js:29928:23)
    at Zone.run (http://angular/quickstart/dist/es6-shim.js:29889:19)
    at zoneBoundFn (http://angular/quickstart/dist/es6-shim.js:29866:19)
    at arguments.(anonymous function) (http://angular/quickstart/dist/es6-shim.js:29928:23)
    at Zone.run (http://angular/quickstart/dist/es6-shim.js:29889:19) ```

Same with setTimeout - interestingly enough, this only happens when zones are included before ng2 - when you push them after ng2 things seem to work as expected....

Actually, after some more testing, it doesn't seem to be linked to scripts inclusion order.

The issue is in the following line - https://github.com/angular/zone.js/blob/3a3dae4295657fb8e09f6025cabb984fed87a38f/zone.js#L129
In non-strict mode, modifying arguments[0] is actually reflected in the variable used as argument 0. see: http://plnkr.co/edit/IqsEew9ihO0oC2itrLo9

closed via #70


Set correct SANs when using cert-manager

This PR adds the Kubernetes Service DNS names to the DNS SANs of the Cert Manager generated Certificate.
Moreover, it removes the host name of the main Ingress rule when the ingress is disabled.
Finally, removes ambiguity in the variable names and adds documenting comments.
Fixes #262

Done @prometherion, thank you.


backup key window abort key missing

there is no possibility to leave this window!
I like the idea, but usability + setup is incredible bad!!
Btw. this looks like a part-time-one-day-a-week project of Google?

Problem is related to overlay.js:51 goog.dom.removeNode(goog.dom.getElementByClass('modal-dialog-title-close', elem)); which removes the close button from all Overlay dialogs.
Potential solution could be for RestoreKey to inherit directly from Dialog or to create a cancel button with this.setButtonSet(goog.ui.Dialog.ButtonSet.createOkCancel()); in decorateInternal.
I would submit a PR for this except that I can't build extension due to #264


deps: updates wazero to 1.0.0-pre.3

This updates wazero to 1.0.0-pre.3. This is the last release that will build with Go 1.17.
Notably, this improves performance and changes host function syntax.

@pkedy fyi nanobus PR is blocked on this one


Import from Solid Authentication Panel repository

This imports the Solid-OIDC text and associated artifacts from the solid/authentication-panel in their current state.
We may want to adjust the general layout -- the specification is in the base path and the primer is in a ./primer directory. I'm not committed to that structure.
I made the appropriate adjustments to the CI/CD workflows, but otherwise, everything is a direct copy over. Once this is merged, we'll want to adjust some of the details (repo location, etc)

Are PRs to main correctly gated with the build action and required review in the repo's settings?

I don't have access to that level of this repository. Given that this build action doesn't currently exist in the repo, I can only imagine that the answer is no.

Are direct pushes to main disabled?

Similar to the above. I haven't tried pushing directly to main. I suspect that direct pushes are not disabled
These are the sorts of repo setting details that will need to be sorted out, but I don't believe they need to block this current PR
cc @csarven


JQuery resource points to http:

This is a problem when serving an https website. There are two options here:

Use https://
Use //

The inconvenient of // is that it doesn't work when the website is served from file://.
On this topic @nbevans you said that // ensures the best possible compatibility; in what situations would https:// not be compatible?

The reason I suggested // instead of https:// is because not everyone is fully onboard with this "HTTPS all the things movement".
As far as I can see // only has drawback when the app is opened from a file:// link. Perhaps the implementation should auto-detect whether it is running from a file:// link and then use https:// instead.

Can you clarify - what disadvantages does using https:// have?

Establishing a SSL/TLS HTTPS session to a CDN is more expensive than a bare HTTP socket. It could also be blocked on some networks (hopefully not, but you never know) - so it is safer to operate using the exact same protocol as the W# app at all times.

Our rationale, admittedly a compromise, for choosing https:/ was to better enable local testing of SPAs and HTML+JS applications, which would be loaded from the file system.  Using https:// is otherwise desired for every client-server application and SPA with a server side, as these would all be running on HTTPS under sane circumstances. In the minority of the cases where this becomes an issue or during development, one can always manually override managed dependencies in web.config to use the desired protocol.
Leaving a note here: we should revisit this ticket for implementing auto-detection as suggested above.


Guard/Spork error in Simplecov 0.8.1 and up

The following issue seems to have been introduced for me in the changes to the at_exit block in PR #213. Previously the old code would assign @exit_status to nil if neither SimpleCov::ExitCodes::MINIMUM_COVERAGE or   SimpleCov::ExitCodes::MAXIMUM_COVERAGE_DROP were set. This meant that the exit call at the bottom would not be called.
Now since @exit_status is always set it will always call exit which is causing the below exception when run using guard/spork. No errors are thrown when run normally from the console
Im not sure wether this is a simplecov issue or one of the other gems but should simplecov call exit! instead at the end to terminate the process immediately or not call exit again if the status hasn't changed from the one passed in so the at_exit continues on with the original code.
A quick test locally of calling exit! prevents the error in guard/spork and still leaves all the tests passing, im just not sure if this would have any implications on other gems so iv put it out there for some smarter minds to weigh in on..
Gems
spork (1.0.0rc3)
guard-rspec (= 2.5.0)
guard-spork (= 1.5.0)
guard (2.2.3)
rspec (2.14.1)
Exception encountered: #<SystemExit: exit>
backtrace:
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/simplecov-0.8.1/lib/simplecov/defaults.rb:80:in `exit'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/simplecov-0.8.1/lib/simplecov/defaults.rb:80:in `block in <top (required)>'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork.rb:77:in `call'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork.rb:77:in `exec_after_each_run'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/run_strategy/forking.rb:14:in `block in run'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/forker.rb:21:in `block in initialize'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/forker.rb:18:in `fork'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/forker.rb:18:in `initialize'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/run_strategy/forking.rb:9:in `new'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/run_strategy/forking.rb:9:in `run'
/Users/jordan/.rvm/gems/ruby-2.0.0-p247@app/gems/spork-1.0.0rc3/lib/spork/server.rb:48:in `run'
/Users/jordan/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/drb/drb.rb:1588:in `perform_without_block'
/Users/jordan/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/drb/drb.rb:1548:in `perform'
/Users/jordan/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/drb/drb.rb:1626:in `block (2 levels) in main_loop'
/Users/jordan/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/drb/drb.rb:1622:in `loop'
/Users/jordan/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/drb/drb.rb:1622:in `block in main_loop'
Done.

Is this still an issue in the 0.9 series?  Please re-open with more info.


Code quotes are badly readable when using the dark theme

e.g. http://<IP_ADDRESS>:10010/language/quoting#index-entry-heredocs_:to-Heredocs:_:to

I believe it's closed with https://github.com/Altai-man/docs.raku.org/commit/53ead00803a59f1f8b991e90d04bd328d4562905


Go Spotify CLI release to Winget v1.0.65

Waiting for release to be approved
https://github.com/microsoft/winget-pkgs/pull/133916

approved


Add share-my-code extension

Description
This is an extension to easily share code snippets, links, texts between people by sharing a simple slug.
Taking advantage of the already existing service ShareMyCode, this extension simplifies the process by avoiding users to open their web browsers, fiddle with the url to get the correct content, etc...
It also tracks recently created  snippets and stores them. Any snippet can be also added to the recents list to be kept.

⚠ I am not the owner of ShareMyCode and am simply porting this service as an extension to Raycast.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi 👋
I just get this error when I test it, does it work for you?

Hi 👋
Sorry for the inconvenience, there indeed seems to be an error when using random slug :(
I am working on it to try and figure it out asap!
Should i convert this pr to draft for now while I investigate ? 😁
Thanks!

Let's convert it, let me know if you need any help

Hi again 👋
I finally found the cause of the bug !
It should work fine now with some small featured I added along the way :)
Let me know if I can/have to do anything 🙂

Thanks so much for the feedback !
Indeed hitting escape allows for modifications of the content which might be confusing and totally be an unexpected behavior 🥲
I think what lead me to this choice was that I thought it would be interesting to give the user a preview of what he just shared without him having to launch another command to check if everything went well!
I will implement your suggestions right-away but in the mean time I had a small concern about a choice I made and I would love to have your thoughts on it :
Is it ok to copy some content (here the link of the ShareMyCode he just created) to the user's clipboard without a mindful action from him (here it's triggered on form submission)?
Thanks 🙂

You could always make it a preference, this way the user can disable(or enable) if they want 🙂

Didn't even consider that, thanks!
Changes have been made now 🙂


server-sent events (SSE) support in GraphQLSubscriptions

Is there any existing solution or a plan to support server-sent events in graphql subscriptions yet? If not, I think it would be worth considering

We currently don't have any plans to support that. But feel free to open a PR.

Related info:

https://github.com/apollographql/graphql-subscriptions/issues/204
https://developers.facebook.com/docs/graph-api/server-sent-events/

With v4 we use gql_link so if someone wants this I'd say just make a 3rd party library or maybe PR a new link to https://github.com/gql-dart/gql


v10.2.2 switch back to Symfony 3.0.3

Current coverage is 95.45%

Merging #184 into master will not affect coverage as of edaa1f7

@@            master    #184   diff @@
======================================
  Files           26      26
  Stmts          374     374
  Branches         0       0
  Methods         83      83
======================================
  Hit            357     357
  Partial          0       0
  Missed          17      17

Review entire Coverage Diff as of edaa1f7

Powered by Codecov. Updated on successful CI builds.


Merge

Hello,
how far off are you from https://sourceforge.net/projects/ethernut/ HEAD? Any intention to  offer it?
Please note, I will be mostly offline until Sep.1

Hi Uwe, not far and far. It depends of point of view. This repository is publicly available, anyone can use it.
I made 2 major changes - PPP, which was not working reliably and I modified behavior, task sequencing (i.e. what is done in which context), added lcp echo to keep alive a connection. In other words ppp can now be invoked repeatedly.
2nd major change is in ifconfig.c, which is not comitted yet, but seems stable. It is about configuring routing tables, when ppp is active and a link is established on ethernet. In this case ppp routing can't be destroyed. I also added an ioctl for ethernet driver, which allows to start dhcp whenever a link is established.
We now have strange behavior with Windows10 v2004, where file upload works with a certain Nut and not working with another Nut version. This was not yet investigated enough.

We also tried to move to Zephyr, which has IPv6. We added file / socket coverage, SD driver for MK64 controller. But finally it was unreliable even with ARPs, so I left it and went back to Nut os and ported drivers for MK64, which are in this repo.
Any cooperation welcome, but we need some budget for this as we are very limited these days.

Hi Uwe,
just now, I finished ppp merge to Nut/OS trunk and ppp works. Once it is tested I will push it here.
Do you know someone, who can test it on ST platform?
No more changes in NutEnterCritical, but really many changes in LCP / IPCP automaton. I did it exactly to match the RFC 1661 transition table. Then some changes even in ifconfig.c (ppp must retain ethernet routing table) and udpout.c & ipout.c changes are usefull to allow broadcasting both to ethernet and ppp (requires to move IP address filling from udpout to ipout as each interface has different IP address). I also tuned interaction with hdlc thread to allow ppp to be opened again.
Here is a preliminary Youtube video of our new DIN rail based device animation with exchangable radio boards (GPRS / UMTS / NB-IoT - already OTS, LoRaWAN, WMBus - in development). Parameters are in a text below the video. More pictures can be found here. We are now working on exchangable functionality for 2 terminals - RS232 / RS485 / 2 opto isol. inputs (2DI) / 2DI isol. with DC/DC / RS485 with DC/DC / 2DO isol.

Hello Dusan,
Dusan Ferbas writes:

Hi Uwe,
just now, I finished ppp merge to Nut/OS trunk and ppp works. Once it is tested
I will push it here.
Do you know someone, who can test it on ST platform?

I have a lot of ST nuclo and disco boards, but my usage case is different:

Collect data from sensors and controll actuators
Provide controll and output via CAN or seriell

Networking is  hostile area for me...

No more changes in NutEnterCritical, but really many changes in LCP / IPCP
automaton. I did it exactly to match the RFC 1661 transition table. Then some
changes even in ifconfig.c (ppp must retain ethernet routing table) and
udpout.c & ipout.c changes are usefull to allow broadcasting both to ethernet
and ppp (requires to move IP address filling from udpout to ipout as each
interface has different IP address). I also tuned interaction with hdlc thread
to allow ppp to be opened again.
Here is a preliminary Youtube video of our new DIN rail based device animation
with exchangable radio boards (GPRS / UMTS / NB-IoT - already OTS, LoRaWAN,
WMBus - in development). Parameters are in a text below the video. More
pictures can be found here. We are now working on exchangable functionality for
2 terminals - RS232 / RS485 / 2 opto isol. inputs (2DI) / 2DI isol. with DC/DC
/ RS485 with DC/DC / 2DO isol.
SM3-LU-transparent-left
SM3-LU-transparent-mid
SM3-LU-transparent-right

I will try to look at the videos the next day.
With  NB-IoT/ LoRaWAN, this reminds me of a planned pet project:

Collect straingauge from a behive, e.g. by HX711
Transfer via BC66 via NB-IOT, with Quecopen or with a controlling STM32L4
Or use a STM32WL for Lora
Do this with lowest power consumption

Do your sample have some overlap with this requirements.
Bye
Uwe Bonnes<EMAIL_ADDRESS>Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

Hi Uwe,

interesting, I did not know about HX711, it requires only 1 MHz clock to output data in serial

our cpu NXP Kinetis MK60 has CAN, differential ADCs, but there is almost no space on the pcb to route additional things. If you are interested for a set of peripherals and the box suits you, we can think about a board variant or even the ST variant. The existing concept of exchangable radio boards can benefit from existing mechanical design, the used LMR36510/20 is promising for its conversion efficiency.
Do you plan to use STM32WL for LoRa (local radio net) or LoRaWAN to be able to send data to a cloud?

I already discussed with Quectel their open mcu (Quec open) for BG96 and they said yes, starting with 1k, better 10k pieces :-)

for LoRa, I thought about LJ elect (minyx.cz) , Hardwario or IMST. Hardwario uses the Murata CMWX1ZZABZ-078, which itself contains SX1276 + STM32L082, but their lead time is > 1y :-(. My current choice is the iM881A-XL, because they offer sniffer and bonding software tools.

our first intention was to made only 1 board with a possibility for different assembly either with LoRa or WMBus. However it was electrically feasible, we did not fit in our mechanical format. So there will be 2 boards.

I do not know if pictures are sent also to your email, but they are on github.

Hello Dusan,
just to exchange and document more notes:
Dusan Ferbas writes:

Hi Uwe,
• interesting, I did not know about HX711, it requires only 1 MHz clock to
output data in serial

It is low cost, other Sigma Delta will fit too. The HX711 resets with
high > 50 us.  That is a pitfall many people fell into when bitbanging
on a RPI while using complex network stacks.

• our cpu NXP Kinetis MK60 has CAN, differential ADCs, but there
is almost no
space on the pcb to route additional things. If you are interested for a
set of peripherals and the box suits you, we can think about a board
variant or even the ST variant. The existing concept of exchangable radio
boards can benefit from existing mechanical design, the used
LMR36510/20 is
promising for its conversion efficiency.
Do you plan to use STM32WL for LoRa (local radio net) or LoRaWAN
to be able
to send data to a cloud?

There was no TTN coverage in the deploy area, last time I looked. So a
Lora receiver would also be needed. And probably to reach the receiver
only small data rate with long transmission time is needed. This may
violate TTN rules (30 sec airtime/day) and increase current surge.
So either is not first choice. But I would plan to use STM32WL. For a better
solderable module, look at the Seeed Lora-E5 (WLe)

• I already discussed with Quectel their open mcu (Quec open) for BG96 and
they said yes, starting with 1k, better 10k pieces :-)

Find the parts at
https://www.soselectronic.de/gsm-umts-lte-5g-module/quectel for decent
pricing. Even Digikey/Mouser carries Quectel. Availability is however
low at the moment like many other things.
Problem is the API, only reverse engineered by Wiz-IO and
documentation could be improved.


session.subscribe(stream, elementId, properties) ignoring properties

Using the sample code in example/www, the video call works but the properties sent inside session.subscribe (in this case, subscribeToAudio: false) are not applied.
NOTE: Tested this on Android, not sure if the same happens on iOS.

+1
Still having this issue. I'm using the fork https://github.com/opentok/cordova-plugin-opentok tho. The properties when creating a publisher are ignored too (at least on Android, on iOS some of them are working, Web is mostly fine.). Especially the following properties are crucial for us: subscribeToVideo, videoSource and style.


[Feat] Add a precheck for tesseract image conversion

Issues have popped up in relation to the tesseract command not producing the txt file that contains the word #21, #40, #31

setup command checks this

Add check in bot just to double check