[eWeLink] WebSocket was closed. Reason [1006]

Hey guys,
This seems to have just started happening recently.
Whenever Homebridge is sending a command to eWeLink devices, the request seems to always timeout. Below is what the log reads and it keeps repeating on and on without resolve:
[2018-4-18 08:19:52] [eWeLink] Setting power state to [on] for device [Hall and Porch CH 1]

WebSocketClient: error { '0':

   { Error: getaddrinfo ENOTFOUND us-long.coolkit.cc us-long.coolkit.cc:8080

    at errnoException (dns.js:50:10)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

     code: 'ENOTFOUND',

     errno: 'ENOTFOUND',

     syscall: 'getaddrinfo',

     hostname: 'us-long.coolkit.cc',

     host: 'us-long.coolkit.cc',

     port: '8080' } }

[2018-4-18 08:20:10] [eWeLink] WebSocket was closed. Reason [1006]

WebSocketClient: reconnecting...

My suspicion is that the individual Sonoff devices aren't connected to the internet (perhaps a Wi-Fi issue?) which is leading to this message.
If anyone has any insights on how to fix this, that would be greatly appreciated!

Tagging @MrTomAsh for visibility :)

Also like to point out that it doesn't seem to be an Auth-token/Header issue, since it seems to have picked up my device name just fine (i.e. Hall and Porch CH 1)

I have the same problem with Sonoff Basic.
It seems that the webservice server is changed

I'm seeing the same issue too.

Same problem as discussed in this other topic: https://github.com/gbro115/homebridge-ewelink/issues/17
The problem isn't with the switches, because mine work with eWeLink-software. I suspect that the three chinese notifications on eWeLink iOS-app that were sent this morning had something to do with this.

Does anyone have any screenshots of these notifications? I can read and speak Chinese so I may be able to help decipher if there is any relevance.

Hi. I’m having a similar issue. I updated the server as per the other issue people were having. My eWeLink app still works and it is the correct auth token so not sure why it won’t work.
[2018-4-22 04:00:42] [eWeLink] WebSocket was closed. Reason [1006]
WebSocketClient: retry in 5000ms 1006
[2018-4-22 03:58:02] [eWeLink] WebSocket messge received:  {"error":0,"apikey":"83df1414-1be9-4d70-aefb-8e2039a852af","config":{"hb":1,"hbInterval":145},"sequence":"1524333482153"}
[2018-4-22 03:58:02] [eWeLink] Sending login request [{"action":"userOnline","userAgent":"app","version":6,"nonce":"152433348215300","apkVesrion":"1.8","os":"ios","at":"removed auth key","apikey":"83df1414-1be9-4d70-aefb-8e2039a852af","ts":"1524333482","model":"iPhone10,6","romVersion":"11.1.2","sequence":1524333482153}]

Please try to update your config.json file as follow:
"webSocketApi" : "eu-pconnect3.coolkit.cc"

Using the US version worked for me too.
us-pconnect3.coolkit.cc

Thanks @MrTomAsh and @jwhits!
Using us-pconnect3.coolkit.cc worked for me also.

I am getting the same error but using the Asia version - "as-api.coolkit.cc:8080" as the apiHost, any idea what would the webSocketApi would be ?

I am getting the same error but using the Asia version - "as-api.coolkit.cc:8080" as the apiHost, any idea what would the webSocketApi would be ?

I have got the error "WebSocket was closed. Reason[1006].
below is my config.json setting. What is the issue?
{
"platform": "eWeLink",
"name": "太郎",
"countryCode": "81",
"email": "<EMAIL_ADDRESS>"password": "************",
"imei": "C91CDC73-EC7B-4AC8-B5BA-9B084CE48411"
}

@deng-san
your config is for homebridge-ewelink-max, this plugin is homebridge-ewelink that’s why it isn’t working

Hi,Ben
thank you for your mail.
I have settled the issue.
best regards
Z. S. Deng

8/11/2020 午後4:38、Ben<EMAIL_ADDRESS>
@deng-san
your config is for homebridge-ewelink-max, this plugin is homebridge-ewelink that’s why it isn’t working
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please try to update your config.json file as follow:
"webSocketApi" : "eu-pconnect3.coolkit.cc"

Hi Tom,  I'm new to programming and trying to get my Sonoff kit to work.  When you state 'add this ("webSocketApi" : "eu-pconnect3.coolkit.cc") to the config file'. does it matter where I add it?    I can't get it to work, I'm in UK so tried eu and us variants but no dice.  Can you help at all?

Please try to update your config.json file as follow:
"webSocketApi" : "eu-pconnect3.coolkit.cc"

Hi Tom,  I'm new to programming and trying to get my Sonoff kit to work.  When you state 'add this ("webSocketApi" : "eu-pconnect3.coolkit.cc") to the config file'. does it matter where I add it?    I can't get it to work, I'm in UK so tried eu and us variants but no dice.  Can you help at all?

In fact can anyone help please?  The sonoffs are recognised in Homebridge and on my iPhone in Apple Home but I can't control them from either.  They all work fine using ewe link..
Config is:
{
    "bridge": {
        "name": "Homebridge XXXX",
        "username": "0E:73:32:47:82:36",
        "port": 51839,
        "pin": "472-76-xxxx"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "name": "eWeLink",
            "countryCode": 44,
            "email": "xxxx.com",
            "password": "xxxxx",
            "imei": "xxxxxxxxxxxxxxxxxxxxx",
            "groups": [
                {
                    "type": "blind",
                    "handle_api_changes": true
                }
            ],
            "webSocketApi": "us-pconnect3.coolkit.cc",
            "platform": "eWeLink"
        }
    ]
}

In fact can anyone help please?  The sonoffs are recognised in Homebridge and on my iPhone in Apple Home but I can't control them from either.  They all work fine using ewe link..
Config is:
{
    "bridge": {
        "name": "Homebridge XXXX",
        "username": "0E:73:32:47:82:36",
        "port": 51839,
        "pin": "472-76-xxxx"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "name": "eWeLink",
            "countryCode": 44,
            "email": "xxxx.com",
            "password": "xxxxx",
            "imei": "xxxxxxxxxxxxxxxxxxxxx",
            "groups": [
                {
                    "type": "blind",
                    "handle_api_changes": true
                }
            ],
            "webSocketApi": "us-pconnect3.coolkit.cc",
            "platform": "eWeLink"
        }
    ]
}

@markkibble
The plugin has had a lot of updates since, and some of the configuration options you have added are not necessary.
Please refer to
https://github.com/bwp91/homebridge-ewelink/wiki/Configuration
for the most up to date configuration fields.
Thanks

@markkibble
The plugin has had a lot of updates since, and some of the configuration options you have added are not necessary.
Please refer to
https://github.com/bwp91/homebridge-ewelink/wiki/Configuration
for the most up to date configuration fields.
Thanks

Ben
Thanks so much for this!  I uninstalled the older version I had and installed homebridge-ewelink v3.18.1
It all works fine now (so far).  I have lost the ‘Accessories’ tab in Homebridge webpage but otherwise it works from my iphone with Apple Home.
Plan to now have a stab at integrating my Arduino next – I think I need to add a homebridge http plugin –
I’m new to all this webby stuff, I’m a retired electrical engineer and having a stab at home automation for my place - so really appreciate your advice as I learn.
I do a lot of amateur theatre lighting controlled with DMX and have got loads of old dimmers and switches that control bits of my house – so working towards linking all that into the project. eBay is full of all this high-end kit which gets ripped out of nightclubs and pubs when they are refurbished and they are just waiting to be repurposed! Much better to control things properly via hardwired OEM kit than dodgey little relays and wifi if possible!
Thanks again for the link and help
Mark. (Oxford UK)
From: Ben<EMAIL_ADDRESS>Reply-To: bwp91/homebridge-ewelink<EMAIL_ADDRESS>Date: Friday, 1 January 2021 at 19:10
To: bwp91/homebridge-ewelink<EMAIL_ADDRESS>Cc: Mark Kibble<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [bwp91/homebridge-ewelink] [eWeLink] WebSocket was closed. Reason [1006] (#16)
@markkibble
The plugin has had a lot of updates since, and some of the configuration options you have added are not necessary.
Please refer to
https://github.com/bwp91/homebridge-ewelink/wiki/Configuration
for the most up to date configuration fields.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ben
Thanks so much for this!  I uninstalled the older version I had and installed homebridge-ewelink v3.18.1
It all works fine now (so far).  I have lost the ‘Accessories’ tab in Homebridge webpage but otherwise it works from my iphone with Apple Home.
Plan to now have a stab at integrating my Arduino next – I think I need to add a homebridge http plugin –
I’m new to all this webby stuff, I’m a retired electrical engineer and having a stab at home automation for my place - so really appreciate your advice as I learn.
I do a lot of amateur theatre lighting controlled with DMX and have got loads of old dimmers and switches that control bits of my house – so working towards linking all that into the project. eBay is full of all this high-end kit which gets ripped out of nightclubs and pubs when they are refurbished and they are just waiting to be repurposed! Much better to control things properly via hardwired OEM kit than dodgey little relays and wifi if possible!
Thanks again for the link and help
Mark. (Oxford UK)
From: Ben<EMAIL_ADDRESS>Reply-To: bwp91/homebridge-ewelink<EMAIL_ADDRESS>Date: Friday, 1 January 2021 at 19:10
To: bwp91/homebridge-ewelink<EMAIL_ADDRESS>Cc: Mark Kibble<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [bwp91/homebridge-ewelink] [eWeLink] WebSocket was closed. Reason [1006] (#16)
@markkibble
The plugin has had a lot of updates since, and some of the configuration options you have added are not necessary.
Please refer to
https://github.com/bwp91/homebridge-ewelink/wiki/Configuration
for the most up to date configuration fields.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


ARCore with React Native?

Curious to know if it's possible to use the ARCore trackable feature for an android application in react native.

Hello Viro,
Would we like to know if the new ViroReact Version 2.14.0 was include ARCore trackable feature for an android ??

Hi, Viro React v2.15.0 has been upgraded to support ARCore 1.10.0 w/ the continuous image tracking.
https://docs.viromedia.com/docs/releases


So, this is not applicable to tenants that do not have an EA with MS? If you are a small tenant with commercial terms licenses without an EA or on a CSP with layers of middle people without an EA?

So, this is not applicable to tenants that do not have an EA with MS? If you are a small tenant with commercial terms licenses without an EA or on a CSP with layers of middle people without an EA?

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

ID: c61c960c-f5c3-76f7-ac18-dfeaf30230e4
Version Independent ID: 3dc607b2-869e-976f-80da-d73cfb1210e5
Content: Cross-tenant mailbox migration - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/cross-tenant-mailbox-migration.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@spahbedsuren Thank you for your feedback. Yes, as of now, it is available only for EA customers and will be available for the commercial licenses soon.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @spahbedsuren Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Warnings and error "There was no ChunkGraph assigned to the Module for backward-compat" when using with default test in vue 2 project with webpack 5

I'm using the following versions

@vue/cli 5.0.0-alpha.3
@vue/test-utils 2.0.0-rc.0
vue 2.6.12
webpack 5.19.0

and I tried to execute the default example unit test:
import { expect } from 'chai'
import { shallowMount } from '@vue/test-utils'
import HelloWorld from<EMAIL_ADDRESS>
describe('HelloWorld.vue', () => {
  it('renders props.msg when passed', () => {
    const msg = 'new message'
    const wrapper = shallowMount(HelloWorld, {
      propsData: { msg }
    })
    expect(wrapper.text()).to.include(msg)
  })
})

Unfortunately, it gives me the following warnings and error when executing vue-cli-service test:unit:
> vue-cli-service test:unit

  [                         ] 0% () WEBPACK  Compiling...

  [=======================  ] 92% (sealing)(node:22544) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
        Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
        Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
  [=========================] 98% (emitting)

 WARNING  Compiled with 11 warnings

 warning  in<EMAIL_ADDRESS>
export 'nextTick' (imported as 'nextTick') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'setDevtoolsHook' (imported as 'setDevtoolsHook') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'getCurrentInstance' (imported as 'getCurrentInstance') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'transformVNodeArgs' (imported as 'transformVNodeArgs') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'Transition' (imported as 'Transition') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'TransitionGroup' (imported as 'TransitionGroup') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'reactive' (imported as 'reactive') was not found in 'vue' (possible exports: default)

 warning  in<EMAIL_ADDRESS>
export 'createApp' (imported as 'createApp') was not found in 'vue' (possible exports: default)

 warning  in ./node_modules/mochapack/lib/entry.js

Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
Invalid dependencies may lead to broken watching and caching.
As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
Globs: They are not supported. Pass absolute path to the directory as context dependencies.
The following invalid values have been reported:
 * "\"../../../tests/unit/example.spec.ts\""

  [=========================] 99% (done) WEBPACK  Compiled with 23 warning(s)

Warning in<EMAIL_ADDRESS>
  export 'nextTick' (imported as 'nextTick') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'setDevtoolsHook' (imported as 'setDevtoolsHook') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'nextTick' (imported as 'nextTick') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'nextTick' (imported as 'nextTick') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'getCurrentInstance' (imported as 'getCurrentInstance') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'getCurrentInstance' (imported as 'getCurrentInstance') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'transformVNodeArgs' (imported as 'transformVNodeArgs') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'Transition' (imported as 'Transition') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'TransitionGroup' (imported as 'TransitionGroup') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'reactive' (imported as 'reactive') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'createApp' (imported as 'createApp') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'defineComponent' (imported as 'defineComponent') was not found in 'vue' (possible exports: default)

Warning in<EMAIL_ADDRESS>
  export 'h' (imported as 'h') was not found in 'vue' (possible exports: default)

Warning in ./node_modules/mochapack/lib/entry.js

  Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
  Invalid dependencies may lead to broken watching and caching.
  As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
  Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
  Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
  Globs: They are not supported. Pass absolute path to the directory as context dependencies.
  The following invalid values have been reported:
   * "\"../../../tests/unit/example.spec.ts\""

  [=========================] 100% (completed)

(node:22544) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: Compilation.modules was changed from Array to Set (using Array method 'reduce' is deprecated)
(node:22544) [DEP_WEBPACK_MODULE_ID] DeprecationWarning: Module.id: Use new ChunkGraph API
Error: Module.id: There was no ChunkGraph assigned to the Module for backward-compat (Use the new API)
    at C:\tmp\unittestbugrep\node_modules\webpack\lib\ChunkGraph.js:1474:12
    at deprecated (internal/util.js:89:15)
    at Function.getChunkGraphForModule (C:\tmp\unittestbugrep\node_modules\webpack\lib\ChunkGraph.js:1465:18)
    at MakeNamespaceObjectRuntimeModule.get id [as id] (C:\tmp\unittestbugrep\node_modules\webpack\lib\Module.js:169:21)
    at C:\tmp\unittestbugrep\node_modules\mochapack\src\webpack\util\getAffectedModuleIds.ts:43:51
    at Array.reduce (<anonymous>)
    at Set.set.<computed> [as reduce] (C:\tmp\unittestbugrep\node_modules\webpack\lib\util\deprecation.js:87:35)
    at buildModuleMap (C:\tmp\unittestbugrep\node_modules\mochapack\src\webpack\util\getAffectedModuleIds.ts:42:29)
    at Object.getAffectedModuleIds [as default] (C:\tmp\unittestbugrep\node_modules\mochapack\src\webpack\util\getAffectedModuleIds.ts:144:32)
    at Object.getBuildStats [as default] (C:\tmp\unittestbugrep\node_modules\mochapack\src\webpack\util\getBuildStats.ts:20:47)
    at TestRunner.prepareMocha (C:\tmp\unittestbugrep\node_modules\mochapack\src\runner\TestRunner.ts:76:49)
    at C:\tmp\unittestbugrep\node_modules\mochapack\src\runner\TestRunner.ts:116:34
    at C:\tmp\unittestbugrep\node_modules\mochapack\src\webpack\compiler\registerReadyCallback.ts:15:7
    at Hook.eval [as callAsync] (eval at create (C:\tmp\unittestbugrep\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:60:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\tmp\unittestbugrep\node_modules\tapable\lib\Hook.js:18:14)
    at C:\tmp\unittestbugrep\node_modules\webpack\lib\Compiler.js:447:23
 ERROR  Error: mochapack exited with code 1.
Error: mochapack exited with code 1.
    at ChildProcess.<anonymous> (C:\tmp\unittestbugrep\node_modules\@vue\cli-plugin-unit-mocha\index.js:84:18)
    at ChildProcess.emit (events.js:326:22)
    at ChildProcess.cp.emit (C:\tmp\unittestbugrep\node_modules\cross-spawn\lib\enoent.js:34:29)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)

I am not really sure whether this really fits here, though. Sorry if it does not.
When using webpack@4, it works.

Hi there!
Vue Test Utils v2 is to be used with Vue 3, and does not work with Vue 2.
Please use VTU v1 if you work with Vue 2 ;)


Do not merge! Testing a color change on visual regression.

Yes, now the visual regression tests work as intended. Closing this PR.


OPS-3261 skip interactive prompt in automation

if gets return nil, it means stdin is closed or its source ended (if we were piping from another process or file). This means we are probably in an automated environment, so we pause like we do with "--no-prompt" switch

lgtm


Stencil/Mustache parsing

Implement https://github.com/kylef/Stencil or other Mustache-like parsing for Views.

This seems like a great place to bring up middleware support for vapor.
Some thoughts I have had on the subject
Would we want support for adding middleware to:
- All requests
- A single route
- A group of routes
The Bootstrap class seems to be the place where middleware will hook into request and response to process what it needs to then pass it on.  The problem I see is that in order to add support for multiple layers of middleware we would also need access to the next middleware in line inside both methods of Bootstrap.  Also how middleware is ordered as it comes in from the request versus going out in the response should be decided.
Some links to where my thoughts/ideas are coming from:
SlimPHP's middleware docs
Lumen's middleware docs

I'm working on an update that replaces Bootstrap and adds a protocol called Middleware.
This will be in release 0.1.7.
The protocol looks like this
public protocol Middleware {
    func handle(handler: Request -> Response) -> (Request -> Response)
}

Stencil parsing added in 0.1.8

@tannernelson  vapor had stopped support for stencil template?

@yudun1989 the efforts required to run stencil on Linux were insurmountable for a long time w/o maintaining multiple forks in the dependency chain of Stencil. I'm not sure the current Linux status, but if it's improved, making a 3rd party stencil provider shouldn't be too difficult.
Unfortunately, these 3rd party renderers were requiring too much dev time internally, so it's very unlikely that we'll open up official support any time soon.
Hopefully this answers your question, and happy to open a discussion further if you'd like 👍


Add pyproject.toml for Custom Node Registry

We are building a global registry for custom nodes (similar to PyPI). The registry makes using custom nodes more reliable by reserving globally unique names for each custom node, and supporting semantic versioning.
Here’s some more information on the registry.
Action Required:

[ ] Go to the registry. Login and create a publisher id. Comment it here and we will update the PR (or just merge it and change it yourself).
[ ] Write a short the description.
[ ] Merge the separate Github Actions PR and run the workflow.
If you want to publish the node manually, install the cli and run comfy node publish

Please message me on Discord if you have any questions!

hey @meap158, wanted to send a small nudge and ask if you had any questions!

@meap158, wondering if there's any way we can support you on this PR!


AsOf blog post fixes

@hawkfish I made a few changes to the AsOf blog post: The first three are cosmetic changes / nits, the fourth commit 0ace45db81f6d05691ffbd3d0b879307fecf5d31 fixes issue #1204.

thanks


fix: powerbi-docs/report-server/quickstart-embed.md

Add code fence language

@nschonni : Thanks for your contribution! The author, @markingmyname, has been notified to review your proposed change.

@mgblythe : Thanks for your contribution! The author, @markingmyname, has been notified to review your proposed change.


Error bootstrapping toolkit on cluster with HelmRelease CRD v1

Trying to use the toolkit against a brand new K8s cluster
$ tk check --pre
► checking prerequisites
✔ kubectl 1.18.2 >=1.18.0
✔ Kubernetes 1.16.11 >=1.14.0
✔ prerequisites checks passed

But the bootstrap fails:
$ tk bootstrap github \
>  --owner=$GITHUB_USER \
>  --repository=gotk-example \
>  --path=gitops-runtime \
>  --personal
► connecting to github.com
✔ repository created
✔ repository cloned
✚ generating manifests
✔ components manifests pushed
► installing components in gitops-system namespace
namespace/gitops-system created
customresourcedefinition.apiextensions.k8s.io/alerts.notification.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/gitrepositories.source.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/helmcharts.source.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/helmrepositories.source.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/kustomizations.kustomize.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/providers.notification.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/receivers.notification.fluxcd.io created
role.rbac.authorization.k8s.io/crd-controller-gitops-system created
rolebinding.rbac.authorization.k8s.io/crd-controller-gitops-system created
clusterrolebinding.rbac.authorization.k8s.io/cluster-reconciler-gitops-system created
service/notification-controller created
service/source-controller created
service/webhook-receiver created
deployment.apps/helm-controller created
deployment.apps/kustomize-controller created
deployment.apps/notification-controller created
deployment.apps/source-controller created
networkpolicy.networking.k8s.io/deny-ingress created
The CustomResourceDefinition "helmreleases.helm.fluxcd.io" is invalid: status.storedVersions[0]: Invalid value: "v1": must appear in spec.versions
✗ install failed

I just realized that this is probably because I am installing on a fresh WKP cluster - it already has a helmrelease CRD installed. Version conflict it seems.

Version conflict it seems.

Yes it's not possible to use helm-controller on WKP as helm-controller and helm-operator can't run on the same cluster. Even if you delete the helm-operator deployment and the HelmRelease v1 CRD, WKP's Flux will reapply them. The HelmRelease v2 is not backwards compatible with v1, so upgrading in-place is not an option, we need to write a v1-to-v2 convertor in tk cc @hiddeco

Is there a way to allow helm-controller and helm-operator to co-exist, maybe use a new crd name for helm-controller and have a migration tool that coverts existing helmrelease custom resources to the new format/name.
My client is using helm-operator widely and wants to use GitOps toolkit source controller and kustomize-controller but is not yet convinced about replacing helm-operator with helm-controller.

At this stage I guess I could use tk install --export and remove helm-controller objects so I can deploy the bits of GitOps toolkit they want right now?

@paulcarlton-ww we will definitely investigate options at a later time but at the moment I am waiting for the various API design questions to be answered before committing to a migration tool.

@paulcarlton-ww expect for source-controller all the others are optional components, if you want to bootstrap or install without helm-controller you can use the components arg like so:
tk install/bootstrap --components=source-controller,kustomize-controller,notification-controller

Great, would it be possible to add --components option to install too?

@paulcarlton-ww check out the help command:
tk install -h
The install command deploys the toolkit components in the specified namespace.
If a previous version is installed, then an in-place upgrade will be performed.

Usage:
  tk install [flags]

Examples:
  # Install the latest version in the gitops-systems namespace
  tk install --version=latest --namespace=gitops-systems

  # Dry-run install for a specific version and a series of components
  tk install --dry-run --version=v0.0.7 --components="source-controller,kustomize-controller"

  # Dry-run install with manifests preview
  tk install --dry-run --verbose

  # Write install manifests to file
  tk install --export > gitops-system.yaml

Flags:
      --components strings   list of components, accepts comma-separated values (default [source-controller,kustomize-controller,helm-controller,notification-controller])
      --dry-run              only print the object that would be applied
      --export               write the install manifests to stdout and exit
  -h, --help                 help for install
      --manifests string     path to the manifest directory, dev only
  -v, --version string       toolkit version (default "latest")

I think there are two use cases:

Automated migration of HelmRelease v1 to v2.
Being able to consume both HelmRelease v1 and v2 in same cluster, during a migration period.

I would say 1. is a nice to have, but 2. is vital if you are consuming many HelmRelease documents, potentially from distributed sources, and cannot migrate them all at once.

They are still closely related.
The error as described in the issue is about storedVersions, once we have settled on a stable API we should declare v2 as the storedVersion (as described in https://book.kubebuilder.io/multiversion-tutorial/api-changes.html) and write a converter for v1 -> v2 as described in https://book.kubebuilder.io/multiversion-tutorial/conversion.html.

I see, so there could be two approaches:

A migration tool which does a one-time conversion of source (e.g. stored in git) HelmReleases. And then using the strategy mentioned by @paulcarlton-ww of running the helm-operator (consuming v1) and helm-controller (consuming v2) in the same cluster.
A single controller which can convert v1 to v2 on the fly and thus consume both as mentioned by @hiddeco

They are not really in conflict with one another, but no need to double the effort.

They are not really in conflict with one another, but no need to double the effort.

If we still want to offer both approaches, I think the converter logic of option 2 can be re-used in the utility made available for option. Which would greatly reduce the amount of work required to be able to offer both options to users.

Another reason for requiring option 1 is the fact that we will drop the support for values from external sources.
With an utility we would be able to fetch this external source and write the contents to a ConfigMap or Secret entry, while creating a ValuesReference in the HelmRelease to this resource. With the conversion happening automatically within the controller, this will be a harder task and likely impossible to pull off in a way that the contents are stored in Git.

This has been fixed in the toolkit v0.0.13 release.
Now you can run both helm-operator and helm-controller in parallel and migrate from HelmRelease v1 to HelmRelease v2 gradually. The toolkit CRDs no longer conflict with Flux v1 as the group changed to helm.toolkit.fluxcd.io.


useChain() is returning stale wallet address

I'm experiencing an issue where after switching accounts in wallet the change is not reflected in the useChain() response. I have a reproduction example here: https://github.com/lukasz-jercinski-vc/cosmos-kit-issue-reproduction
Steps to reproduce the issue:

connect wallet
select different account in the wallet

useChain() returns address for the initially connected wallet

Hi, @lukasz-jercinski-vc
i did some test. could you try to use “page router” mode in nextjs to see if this is work?

hi @lukasz-jercinski-vc please try on latest version. we push some fix for app route in nextjs

Hey! The latest version seems to be working well with app router, thanks!

Okay, Nice. Enjoy!


Add KeyedDecodingContainer extensions

This PR adds KeyedDecodingContainer extensions as required by this issue #743
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 610 tests, with 0 failures (0 unexpected) in 12.288 (15.066) seconds

:book:
tvOS: Executed 584 tests, with 0 failures (0 unexpected) in 5.654 (7.174) seconds

:book:
macOS: Executed 438 tests, with 0 failures (0 unexpected) in 1.063 (1.401) seconds

SwiftLint found issues
Warnings

File
Line
Reason

KeyedDecodingContainer.swift
28
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
79
Variable name should be between 3 and 40 characters long: 'isPlayingAsIntAndIsFullScreenTypeMismatch' (identifier_name)

KeyedDecodingContainerTests.swift
16
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
21
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
31
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
35
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
43
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
52
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
61
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
70
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
78
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
87
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
88
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
91
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
100
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
103
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
112
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
115
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
124
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
127
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
135
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
139
Lines should not have trailing whitespace. (trailing_whitespace)

KeyedDecodingContainerTests.swift
88
Limit vertical whitespace to a single empty line. Currently 2. (vertical_whitespace)

  Generated by :no_entry_sign: Danger

I just noticed a major issue with your implementation: It requires Foundation because you're casting the values to NSNumber and NSString. You either need an alternative or cover the whole thing with #if canImport(Foundation).

@guykogus I'll take a detailed look as soon as possible, but for this one specifically, I would like to have the review from @omaralbeik :))


Add a shell message for flock-file-locks experiment

Related to https://github.com/buildkite/agent/pull/1624
This adds a comment similar to the mirrors experiment when flock-file-locks is used. We're trying to troubleshoot lock failures, so this helps us be certain the experiment is enabled!

Hi @lox, thanks for adding this. Are you seeing the locking issue with this experiment turned on? I just opened https://github.com/buildkite/agent/pull/1685 which might be explained by the locking not working as expected in updateGitMirror but it's only happened twice since turning on the experiment in April and its typically worked well.


automatically emit formData upon save

besides newData and oldData I should also emit formData

The payload @save  already looks like { newData, oldData, formData }. I guess this has already been implemented?


Bitstamp missing bitcoin withdrawal method

Using ccxt==1.9.41.
I can't seem to find private api endpoints for withdrawing bitcoin on bitstamp v2. Comparing it to version 1, these methods are missing:
https://www.bitstamp.net/api/bitcoin_deposit_address/
https://www.bitstamp.net/api/unconfirmed_btc/
https://www.bitstamp.net/api/bitcoin_withdrawal/

Hi, I added those missing endpoints, thank you very much for pointing that out! They should be available as of version 1.9.42+ in 5 minutes. Let us know if you have any difficulties with them. Cheers!

I am also having problems fetching ltc address in python asyncio for bitstamp.
bitstamp = ccxt.bitstamp({
    "apiKey": "my_api_key",
    "secret": "my_secret",
    "uid" : "my_uid"

})
loop.run_until_complete(bitstamp.private_post_ltc_address())

It returns 400 error code:
ExchangeNotAvailable: bitstamp POST https://www.bitstamp.net/api/v2/ltc_address 400

@davidpodrebarac and the others are working?

Sorry, I haven't had the time to check it yesterday, but it seems to be working now. Thanks :slightly_smiling_face:

@davidpodrebarac awesome! ) Good to know that! Thx, really appreciate your report!

 Methods for xrp, eth and ltc work like a charm.
Thanks!

Can you post verbose output of it?
bitstamp_ccxt = ccxt.bitstamp({
    "apiKey": "<<api_key>>",
    "secret": "<<secret>>",
    "uid" : "<<uid>>",
    "verbose": True,
})
loop.run_until_complete(bitstamp_ccxt.private_post_bitcoin_deposit_address())

?

Nope, never mind. The reason is: you should use bitstamp1 (v1) for BTC deposit and withdrawal. Looks like their v2 does not support that. I'll remove those endpoints.

Actually, I think I'll add them to v2 but they will call v1 under the hood. Just to make it more convenient to those who want v2.

Great, thank you! That is just what I wanted to ask you.

Ok, I added them properly now, but because those methods use v1-endpoints inside, you should call them like so:
loop.run_until_complete(bitstamp_ccxt.v1_post_bitcoin_deposit_address()) # "private_" → "v1_"

Please update to version 1.9.91+ and try the above ↑ example now )
Let us know if it helped you or not.
Thx!

It works great now.


filer: refactor fullpath to handle invalid path

I refactored fullpath.go.
It supports:

Directory literal (ends with /) switch and detect. (no need to detect, add, remove / suffix directly anymore)
Replace invalid UTF-8 characters with ?.
Handle . .. and // in path.

Then refactored some codes related with fullpath.

The pr is too big. Need to split into smaller ones.


Should we pin to master when Github advises pinning to full git SHA?

https://github.com/aquasecurity/trivy-action/blob/cb606dfdb0d2b3698ace62192088ef4f5360b24f/README.md?plain=1#L70
See https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions

Fair enough - you can pin to a full SHA as you mentioned. The documentation is simply a suggestion and not a requirement.


[Guides] kpt pkg update is misleading

kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge

After the above command, the image tag will not change from 0.1.0 to v0.3.0.

I suspect there is a mismatch between tag and commit hash.

I think this might be an actual bug. I see that if do
kpt pkg get<EMAIL_ADDRESS>helloworld
kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge

I end up with the image tag 0.1.0.
But if I do
kpt pkg get<EMAIL_ADDRESS>helloworld

I do get the expected image tag 0.3.0

Yes, it seems a change in comment does not trigger resource-merge.

@mortent @gosharplite
Here are the steps I followed
kpt pkg get<EMAIL_ADDRESS>helloworld
deploy.yaml is same as here
https://github.com/GoogleContainerTools/kpt/blob/package-examples/helloworld-set/v0.3.0/package-examples/helloworld-set/deploy.yaml
kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge
deploy.yaml is same as here
https://github.com/GoogleContainerTools/kpt/blob/package-examples/helloworld-set/v0.5.0/package-examples/helloworld-set/deploy.yaml
If you observe there are two types of tags in repo:
v0.3.0 and package-examples/helloworld-set/v0.3.0
v0.5.0 and package-examples/helloworld-set/v0.5.0
That might be leading to this confusion?

@phanimarupaka @mortent
Yes, it could be a tag mismatch issue.
At the end, the Kptfile changed to below hash.
commit: 3f173ad974081896b47f6929b2c3cb595d71af94

The image tag v0.3.0 is associated this hash. (subdirectory<EMAIL_ADDRESS>https://github.com/GoogleContainerTools/kpt/blob/3f173ad974081896b47f6929b2c3cb595d71af94/package-examples/helloworld-set/deploy.yaml

But it seems the image tag 0.1.0 of repo<EMAIL_ADDRESS>is used instead.
https://github.com/GoogleContainerTools/kpt/blob/v0.5.0/package-examples/helloworld-set/deploy.yaml

So I agree this might be caused by the different tags. But it seems pretty clear to me that the result we want from running:
kpt pkg get<EMAIL_ADDRESS>helloworld
kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge

is that my local state should reflect that of the tag package-examples/helloworld-set/v0.5.0. And the value of the image tag should be v0.3.0.
@phanimarupaka Are you getting a different result or do you expect a different result?

@mortent If I run these commands
kpt pkg get<EMAIL_ADDRESS>helloworld
kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge
My local state reflects this v0.3.0.
So it is as expected for me. Did you try with the latest kpt release?

@mortent @gosharplite The issue is due to Kptfiles not being merged in a 3 way fashion. If you observe, even Kptfile setter value is not being changed to v0.3.0. I am working on fixing it.

@phanimarupaka You observation is correct.
After
kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge
The Kptfile setter value has not been changed  to v0.3.0.
apiVersion: kpt.dev/v1alpha1
kind: Kptfile
metadata:
    name: hello-world-set
upstream:
    type: git
    git:
        commit: 3f173ad974081896b47f6929b2c3cb595d71af94
        repo: https://github.com/GoogleContainerTools/kpt
        directory: /package-examples/helloworld-set
        ref: v0.5.0
.
.
        io.k8s.cli.setters.image-tag:
            description: hello-world image tag
            x-k8s-cli:
                setter:
                    name: image-tag
                    setBy: package-default
                    value: 0.1.0

@gosharplite @mortent FYI https://github.com/GoogleContainerTools/kpt/pull/530

@mortent @phanimarupaka @pwittrock
PR #530 gives expected results as shown below.
This issue has been resolved. Thank you!
$ kpt pkg update<EMAIL_ADDRESS>--strategy=resource-merge
updating package helloworld to v0.5.0

$ git diff
diff --git a/helloworld/Kptfile b/helloworld/Kptfile
index 5a30f3b..fb20489 100644
--- a/helloworld/Kptfile
+++ b/helloworld/Kptfile
@@ -5,10 +5,10 @@ metadata:
 upstream:
     type: git
     git:
-        commit: 3d721bafd701deb06aeb43c5ea5afda3134cfdd6
+        commit: 3f173ad974081896b47f6929b2c3cb595d71af94
         repo: https://github.com/GoogleContainerTools/kpt
         directory: /package-examples/helloworld-set
-        ref: v0.3.0
+        ref: v0.5.0
 openAPI:
     definitions:
         io.k8s.cli.setters.http-port:
@@ -24,7 +24,7 @@ openAPI:
                 setter:
                     name: image-tag
                     setBy: package-default
-                    value: 0.1.0
+                    value: v0.3.0
         io.k8s.cli.setters.replicas:
             description: helloworld replicas
             x-k8s-cli:
diff --git a/helloworld/deploy.yaml b/helloworld/deploy.yaml
index b94d058..4f05d0a 100644
--- a/helloworld/deploy.yaml
+++ b/helloworld/deploy.yaml
@@ -31,7 +31,7 @@ spec:
     spec:
       containers:
       - name: helloworld-gke
-        image: gcr.io/kpt-dev/helloworld-gke:0.1.0 # {"$ref":"#/definitions/io.k8s.cli.substitutions.image-tag"}
+        image: gcr.io/kpt-dev/helloworld-gke:v0.3.0 # {"$ref":"#/definitions/io.k8s.cli.substitutions.image-tag"}
         ports:
         - name: http
           containerPort: 80 # {"$ref":"#/definitions/io.k8s.cli.setters.http-port"}
diff --git a/helloworld/service.yaml b/helloworld/service.yaml
index 0853ee1..c938fde 100644
--- a/helloworld/service.yaml
+++ b/helloworld/service.yaml
@@ -22,7 +22,7 @@ metadata:
   labels:
     app: hello
 spec:
-  type: LoadBalancer
+  type: NodePort
   selector:
     app: hello
   ports:


Allow use of custom menu with native titlebar (on Linux and Windows)

This is my attempt to find a suitable workaround to #224515, given that we will probably not see a proper resolution to that bug for a long time if ever. I have implemented a proof-of-concept and intend to submit a PR for this shortly.
Add a "Force Custom Menu Style" option - boolean, default false.

If false, behavior is unchanged. If true, and "Title Bar Style" is "native", and we're running on Linux or Windows (notably: not Mac*, not web), then we display the OS native title bar, but we display the custom menu bar below it, taking care not to repeat the window title. Of course, it affects context menus as well as the main menu bar. The result: a pleasant user experience while using the native title bar.

Debian 12, MATE
Compare with the screenshots from my comment here - unfortunately I can't show the same menu, since I understand it's not possible (not allowed) to use the Marketplace from an unofficial build of VS Code, but hopefully it should still illustrate the point.
By default, you'll also get the "Command Center" and "Layout Controls" showing up next to the menu, since this menu bar is really just the custom title bar, forced to be displayed. The above screenshot, showing the classic "separate title bar and menu bar, with no additional clutter" layout, was accomplished by just using the existing settings to hide these items.
(*I have assumed that this isn't applicable on Mac, based on basic knowledge of the Mac interface and various comments in the VS Code source, but I don't use Mac myself, so I have no way to test this. If someone else finds a reason why it'd be useful to have this feature on Mac as well, then feel free to enable it there.)

I too was thinking this would be a decent compromise during this past week, missing the native title bar.

*I have assumed that this isn't applicable on Mac, based on basic knowledge of the Mac interface and various comments in the VS Code source, but I don't use Mac myself, so I have no way to test this.

You're spot on. 👍🏼  Under macOS 11 (obsolete, very old), I can confirm that VS Code 1.96 / Electron 32 does use the native menus, both for the menu bar (global/system) and context menus. No visual discrepancies across programs there.
I'm hoping the Electron docs can be updated to clarify the so-called "native" menu:

https://github.com/electron/electron/pull/45033


Added Docker support

This PR introduces the generation of a Docker image for the project and a docker-compose definition about how to run it.
It adds the following features:

Automated Docker image creation when creating a new release / tag
Automated push to GHCR (Github Container Registry), in this case ghcr.io/krausefx/auxcord.org:latest
Will also generate the corresponding tags (latest, vX.X.X, etc)

Note: No additional secrets are required since it is using Github Action's builtin token and variables

Beautiful, thank you. Also, I added you to the repo 😊


sig#789 - Update ServiceReleaseProcess Form

Precondition

https://github.com/eclipse-tractusx/portal-frontend/issues/1078

Description
in the https://portal.int.catena-x.net/serviceReleaseProcess/form & https://portal.int.catena-x.net/appReleaseProcess/form
Adjust the description to have the same design as the one from
https://portal.int.catena-x.net/technicalUserManagement

as soon as i click both internal and external accounts i want to see an info:
Be aware that this configuration will cause the system to generate multiple Technical User Accounts"
design should be aligned with https://github.com/eclipse-tractusx/portal-frontend/issues/1126
Acceptance Criteria
Alignment with Technical User Management Design:

[ ] The description in the https://portal.int.catena-x.net/serviceReleaseProcess/form should have the same design as the one from https://portal.int.catena-x.net/technicalUserManagement.

[ ] The description in the https://portal.int.catena-x.net/sappReleaseProcess/form should have the same design as the one from https://portal.int.catena-x.net/technicalUserManagement.

[ ] This includes the use of the same font, font size, and color scheme.

[ ] The layout and structure of the description should also be aligned.

Clicking Internal and External Accounts:

[ ] When the user checks both types of accounts (internal + external) , an informational message should be displayed.
[ ] The message should read: "Be aware that this configuration will cause the system to generate multiple Technical User Accounts".
[ ] The design of the informational message should be aligned with the design specified in this GitHub issue.

Responsiveness and Accessibility:

[ ] The updated description and informational message should be responsive and accessible, ensuring a good user experience across different devices and screen sizes.

Consistency with Platform Design:

[ ] The overall design and implementation should be consistent with the existing design and user experience of the Catena-X platform.

Functionality Validation:

[ ] Ensure that the updated description and informational message function correctly and do not introduce any regressions or issues in the existing functionality.

Documentation and Testing:

[ ] Update the documentation accordingly https://github.com/eclipse-tractusx/portal-assets/tree/main/docs/user/05. Service(s)

Test Cases
Test Case 1: Verify Form Design Matches "Technical User Management" Form
Steps:
Navigate to https://portal.int.catena-x.net/serviceReleaseProcess/form.
Inspect the design and layout of the form, including the placement and styling of form elements, headers, and labels.
Verify that the design and layout match the "Technical User Management" form on https://portal.int.catena-x.net/technicalUserManagement.
Expected Result: The design and layout of the "Service Release Process" form should match the "Technical User Management" form, including the placement and styling of form elements, headers, and labels.
Test Case 2: Verify Informational Message When Both "Internal Accounts" and "External Accounts" are Selected
Steps:
Navigate to https://portal.int.catena-x.net/serviceReleaseProcess/form.
Select the "Internal Accounts" checkbox.
Select the "External Accounts" checkbox.
Observe the informational message displayed.
Expected Result: When both the "Internal Accounts" and "External Accounts" checkboxes are selected, an informational message should be displayed, stating: "Be aware that this configuration will cause the system to generate multiple Technical User Accounts"

@MaximilianHauer Hope this implementation is fine


Resolve non-type free variables in return type restrictions

Resolves #6543.
The free variables are already there, only that the return type lookup skipped over them.

Is this also related to https://github.com/crystal-lang/crystal/issues/11859 ?

Looks like this causes some recursive aliases to be resolved earlier than they should...?

No and no.


installation error

Hi, I am installing ModDotplot in ubuntu and I have an error:
Collecting tk
Downloading tk-0.1.0-py3-none-any.whl (3.9 kB)
ERROR: Could not find a version that satisfies the requirement PIL (from moddotplot) (from versions: none)
ERROR: No matching distribution found for PIL
My comands to install were:
python3.10 -m venv venv
source venv/bin/activate
python3.10 -m pip install .
The complete output:
Processing /home/ggreif/ModDotPlot
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting numpy
Downloading numpy-2.1.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (16.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 16.3/16.3 MB 10.5 MB/s eta 0:00:00
Collecting pandas
Downloading pandas-2.2.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.0/13.0 MB 10.7 MB/s eta 0:00:00
Collecting setproctitle
Downloading setproctitle-1.3.3-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (30 kB)
Collecting plotly
Downloading plotly-5.24.1-py3-none-any.whl (19.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 19.1/19.1 MB 8.9 MB/s eta 0:00:00
Collecting patchworklib
Downloading patchworklib-0.6.4-py3-none-any.whl (48 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 48.5/48.5 KB 6.8 MB/s eta 0:00:00
Collecting mmh3
Downloading mmh3-5.0.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (88 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 88.9/88.9 KB 9.4 MB/s eta 0:00:00
Collecting plotnine==0.12.4
Downloading plotnine-0.12.4-py3-none-any.whl (1.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 10.1 MB/s eta 0:00:00
Collecting pysam
Downloading pysam-0.22.1-cp310-cp310-manylinux_2_28_x86_64.whl (22.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 22.0/22.0 MB 4.8 MB/s eta 0:00:00
Collecting dash
Downloading dash-2.18.1-py3-none-any.whl (7.5 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.5/7.5 MB 10.4 MB/s eta 0:00:00
Collecting tk
Downloading tk-0.1.0-py3-none-any.whl (3.9 kB)
ERROR: Could not find a version that satisfies the requirement PIL (from moddotplot) (from versions: none)
ERROR: No matching distribution found for PIL

Hi @Gon1976,
This error was caused by a dependency conflict with PIL, and has now been patched. Please pull the latest version of ModDotPlot and try again, or simply replace PIL with pillow in the pyproject.toml file.
Thanks,
Alex

thanks it's work fine now


can you provide a example about send btc transaction?

can you provide a example about send btc transaction?

Hi @YDJSZY , here you are https://github.com/anicdh/bitcoin_flutter/blob/master/test/integration/transactions_test.dart#L7

Closing. Feel free to open if you have any issues, Thanks!

Thanks!


Add loading indicators

Testing out Skeleton content loader components.

The Skeleton component is a named export alongside the Component. It's a react component, but there's no reason why we can't make it a data structure that describes the shape, and is invoked by our own Query component.

Love it! This is really nice.

@mojombo This has changed a bit since last you saw it, I've added a queryProps static object to the Post component. These are {...spread} into the Query component and can contain anything from the query to the skeleton definition.


fix: replace en dashes

Fixes #1
Checklist

[x] I have ensured my pull request is not behind the main or master branch of the original repository.
[x] I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first.
[x] I have written a commit message that passes commitlint linting.
[x] I have ensured that my code changes pass linting tests.
[ ] I have ensured that my code changes pass unit tests.
[x] I have described my pull request and the reasons for code changes along with context if necessary.

@titanism thanks for clarification


[doc] Hardware Designs Dashboard text unreadable unless in dark mode

https://docs.opentitan.org/doc/project/hw_dashboard/
The table contents are all in white, and only visible if switching to dark mode.

I don't find this document linked from https://docs.opentitan.org/doc/project/ either, so maybe it's an old page? The linked one is at https://docs.opentitan.org/hw/ and works just fine.

Ah, the bug is likely that this old page is hanging around then. It's the first or second result on Google for opentitan dashboard.

@towoe or @gkelly might know more

Interesting find. I do not see this page on a local instance. So might this be a deployment relic?

Yeah, that appears to be https://docs.opentitan.org/doc/project/hw_dashboard/ which should have been deprecated. I can remove that with a PR

Yeah, that appears to be https://docs.opentitan.org/doc/project/hw_dashboard/ which should have been deprecated. I can remove that with a PR

ooh I see, it is removed from our GH repo, yet it lingers in docs. @gkelly any idea what is going on there? Does hugo need a scrub before rendering?

The way the docs push works is that it generates locally and then gsutil rsyncs the tree over to the hosting bucket. When I first wrote the scripts I was worried that a bad generation run would potentially wipe the current documentation set out if the output directory was empty, so I didn't pass --delete to the rsync. Let me check the logs to see if it's ever happened, and if not I can just add --delete so that it takes old pages out of the serving bucket.


Fix parsing directories

throw a runtime error if we pass a directory to parse_file (fixes #1113)
add test to make sure it works

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.60%. Comparing base (347f786) to head (c71ecbf).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1203      +/-   ##
==========================================
+ Coverage   86.58%   86.60%   +0.01%
==========================================
  Files         175      175
  Lines       13006    13009       +3
==========================================
+ Hits        11261    11266       +5
+ Misses       1745     1743       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Is it posible to get the description of a file?

Files on Google Drive can be completed with a description on the details section. Is it possible to get this description with the terminal command?
I was expecting to see the description with the "drive stat file".

Hello there @marcoblancas thanks for reporting this issue and welcome to drive!
You are right, this should be reported -- good catch. Am spinning up a PR asap.
Thanks!

Addressed by PR https://github.com/odeke-em/drive/pull/413. Please get the latest from master.

Perfect... it works. Thank you.

Awesome glad to know it works. Thanks again for reporting it!


Add calculating correlations with p-value as in scipy.stats.pearsonr

Is your feature request related to a problem? Please describe.
It is similar to existing library
Describe the solution you'd like
Add a method that returns correlation matrix and p-value matrix
Describe alternatives you've considered
Using scipy.stats.pearsonr, but it is not NaN, inf friendly

Done


Refactor and optimize

I took the liberty of refactoring/simplifying/optimizing the current FRFuel code. This is totally up to you guys if you want to take this, or parts of it.
Work done:

Fuel Consumption no longer tied to FPS
Config file is now JSON

Added fuel tank capacity option
Added manual refill option
Added speed fuel impact modifier

Simplified GasStations loading
Made Config and GasStations static instances
Simplified blip creation
Simplified and optimized Jerry can spawning for efficiency

In this version, jerry cans no longer despawn when you are not near. Instead, they spawn at all gas stations and only respawn as needed every 10 minutes.

Optimized fuel consumption method
Optimized refueling check method
Separated fuel consumption from refueling. Refuel check still runs every tick
Cleaned up HUD code and static instanced
More thorough gitignore
General code cleanup (Reduction of ~400 lines of code)

Code is not extremely thoroughly tested. I attempted to keep all Mod functionality the same unless there were major efficiency gains (ie. Jerry cans)

Hey @thers,
Thanks for taking a look at the PR. I appreciate the feedback and in your shoes, would probably make the same decision. This is just too large of a change and needs more testing. The benefit I saw from presenting it was hopefully showing you new practices or ideas that you could take advantage of in smaller increments.


Update master from v0.4b release

Codecov Report

Merging #105 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #105   +/-   ##
=======================================
  Coverage   92.73%   92.73%
=======================================
  Files          21       21
  Lines        1142     1142
  Branches      141      141
=======================================
  Hits         1059     1059
  Misses         55       55
  Partials       28       28

Impacted Files
Coverage Δ

azure_monitor/src/azure_monitor/version.py
100.00% <100.00%> (ø)

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 e9e669f...dd69ab4. Read the comment docs.


Feature Request: High-level commands instead of just directions

nallaj on the Battlesnake Discord shared an interesting idea:

Have you thought of using higher level commands instead of directions? Coords was the first to come to mind, but I feel like stratagies could be the good, eg !feed, !attack, !wait.

My own thoughts on this:

Could be really fun
Probably less annoying when there's a delay, because the command could take multiple moves to carry out anyway
How would voting work with multi-turn commands, and how would you keep it fair?

Might help with https://github.com/xtagon/chatsnek/issues/9
Similar to https://github.com/xtagon/chatsnek/issues/3


License?

What license is this under? I would recommend adding a license file if you want people to know what limitations there are on using and forking your repository.

Thank you for the reminder! I have completely neglected this until now, but just added the MIT license.


After upgrading to 1.93.1 source control inside SSH tunnel is broken

Does this issue occur when all extensions are disabled? Yes
Using Microsoft SSH extensions:

Remote explorer: v0.4.3
Remote - SSH: v0.114.3

VS Code Version: 1.93.1
OS Version: Windows_NTx64 10.0.19045

Steps to Reproduce:

Upgrade to 1.93.1
SSH to an Ubuntu machine with git in a repo
Make changes to some files in the repo
Not seeing any source control details at all

I can re-raise this on https://github.com/microsoft/vscode-remote-release if you feel it needs to be there instead.

@WibblyGhost, based on the screenshot it seems that the vscode.git-base and/or vscode.git extensions are not running. Could you please open the "Extensions" viewlet and search for both git-base and git extensions. Are they running? Are you seeing any warnings in the "Extensions" viewlet for these two extensions?

When using RDP'ing onto my Ubuntu box the Git features all work correctly, however only when SSH'ing from my Windows box, the Git doesn't show. It seems the add-ons are enabled correctly.
Extension Host (Remote) Log:
2024-09-16 23:36:22.678 [info] Extension host with pid 10894 started
2024-09-16 23:36:22.723 [info] Lock '/home/taitnet/.vscode-server/data/User/workspaceStorage/_____/vscode.lock': Lock acquired.
2024-09-16 23:36:23.195 [info] ExtensionService#_doActivateExtension alexkrechik.cucumberautocomplete, startup: false, activationEvent: 'onLanguage:feature'
2024-09-16 23:36:23.197 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: '*'
2024-09-16 23:36:23.198 [info] ExtensionService#_doActivateExtension albert.TabOut, startup: false, activationEvent: '*'
2024-09-16 23:36:23.198 [info] ExtensionService#_doActivateExtension balmacefa.linehighlightbookmarkvscode, startup: false, activationEvent: '*'
2024-09-16 23:36:23.199 [info] ExtensionService#_doActivateExtension christian-kohler.path-intellisense, startup: false, activationEvent: '*'
2024-09-16 23:36:23.199 [info] ExtensionService#_doActivateExtension mhutchie.git-graph, startup: false, activationEvent: '*'
2024-09-16 23:36:23.199 [info] ExtensionService#_doActivateExtension outofsync42.select-compare-tabs, startup: false, activationEvent: '*'
2024-09-16 23:36:24.719 [info] ExtensionService#_doActivateExtension vscode.tunnel-forwarding, startup: false, activationEvent: 'onTunnel'
2024-09-16 23:36:24.725 [info] ExtensionService#_doActivateExtension ms-python.python, startup: true, activationEvent: 'workspaceContains:pyproject.toml', root cause: ms-python.black-formatter
2024-09-16 23:36:25.025 [info] ExtensionService#_doActivateExtension vscode.github, startup: false, activationEvent: '*'
2024-09-16 23:36:25.642 [info] ExtensionService#_doActivateExtension ms-python.black-formatter, startup: true, activationEvent: 'workspaceContains:pyproject.toml'
2024-09-16 23:36:25.884 [info] Eager extensions activated
2024-09-16 23:36:25.884 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-09-16 23:36:25.884 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-09-16 23:36:25.914 [info] ExtensionService#_doActivateExtension ms-python.debugpy, startup: false, activationEvent: 'api', root cause: ms-python.python
2024-09-16 23:36:26.107 [info] ExtensionService#_doActivateExtension ms-python.vscode-pylance, startup: false, activationEvent: 'api', root cause: ms-python.python

Both vscode.git-base and vscode.git extension need to be running in the remote extension host. It looks like the vscode.git extension is not installed there as indicated by the "Warning" shown in the hover. Could you please click on the "Gear" icon and install the extension in the remote extension host? Thanks!

There is not installation options here due to it being a builtin plugin.

Also on a different machine with an old version of VSCode the Git seems to be working correctly.

@sandy081, any idea what is going on there? Why can't the vscode.git extension be installed on the remote? Thanks!

Built in extensions are supposed to be loaded correctly on the correct extension host. This should not happen for any built in extension unless there is an issue with the set up. It seems the vscode.git-base extension is not available on the remote, it could be an issue with installation or some other reason which I am not aware of.
@WibblyGhost Can you please enable log level to trace  F1 > Developer: Set Log Level... > Trace , reload the window and share the Server log F1 > Open View... > Server ?

I don't see any immediate problems in the server logs, this is the only line that looks suspicious.
(error: Error: ENOENT: no such file or directory, stat '/home/taitnet/Programming/integration-tests/.vscode/extensions')
remoteagent.log
remoteexthost.log
ptyhost.log

@WibblyGhost I do not see git extension getting scanned on the remote server. Can you please check if the git folder exists in the server extensions folder here - /home/taitnet/.vscode-server/cli/servers/Stable-38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40/server/extensions/

I do not see git extension listed here. It explains why the extension is not loaded in the remote. I believe the installation is not complete or corrupt. Can you please re-install and try?

Yep just deleted the entire .vscode-server folder and it seems to have fixed the issue. 👍


Remove version: AgileBits.1Password version 8.4.1

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

URL: https://downloads.1password.com/win/1PasswordSetup-8.4.1.exe
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 910)


Tracking issue: performance

Nothing much to track yet, and not quite a priority, but we need to do some performance work at some point. Even moderate sized crates take quite some time to format, if we want to be run regularly on large projects, we need to make some improvements and ensure we do not do worse as we get better at formatting.
todo list:

some kind of benchmarking to make sure we don't regress (need to know time difference for optimised vs debug too)
profile a long-ish run to see where we're spending our time
[ ] #385 incremental reformatting
[ ] benchmarking
[ ] profiling

0.1.9-nightly () is an order of magnitude slower than the last time I benchmarked (cc #1599).
I have not investigated further since currently the performance is not high priority.
Just leaving it as a comment here since I think it is worth sharing.

Some concrete steps I think would be good to do:

[ ] identify some 'typical' medium to large sized projects and measure the formatting time. Keep track of these large benchmarks
[ ] profile the above to identify where we're spending time
[ ] add some smaller benchmarks to the test suite
[ ] some form of incremental reformatting (based on timestamps or diffs or something like that)
[ ] investigate using a rope or other data structure rather than string concatenation
[ ] investigate more pre-allocation of memory (probably requires the above first)
[ ] look out for any > O(n) behaviour - we've had some nasty blow-ups in the past

I don't know if this is the right place for this, but these are the top 25 function calls I found using callgrind.
--------------------------------------------------------------------------------
         Ir  file:function
--------------------------------------------------------------------------------
103,139,410  ???:<alloc::vec::Vec<T>>::extend_with [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 94,217,847  ???:<rustfmt_nightly::comment::CharClasses<T> as core::iter::iterator::Iterator>::next [/home/marcus/rustfmt/target/release/rustfmt]
 68,762,712  ???:syntax::codemap::CodeMap::lookup_filemap_idx [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 45,885,887  ???:rustfmt_nightly::format_lines [/home/marcus/rustfmt/target/release/rustfmt]
 42,856,475  ???:syntax::parse::lexer::StringReader::bump [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 38,002,028<EMAIL_ADDRESS>[/usr/lib64/libc-2.25.so]
 33,136,711  /checkout/src/libcore/fmt/mod.rs:core::fmt::write [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]
 30,705,361  ???:<rustfmt_nightly::comment::UngroupedCommentCodeSlices<'a> as core::iter::iterator::Iterator>::next [/home/marcus/rustfmt/target/release/rustfmt]
 28,438,225  ???:syntax::codemap::CodeMap::span_to_snippet [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 24,381,665  ???:_ZN6syntax5parse5lexer12StringReader13advance_token17h3765cf14d7e01289E.llvm.3E1208B2 [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 23,491,170  /checkout/src/liballoc_jemalloc/../jemalloc/src/jemalloc.c:mallocx [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]
 22,470,635  ???:_ZN4core3ptr13drop_in_place17hdbe8add465ba12a0E.llvm.A0C0D04A [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 21,306,647  ???:rustfmt_nightly::comment::combine_strs_with_missing_comments [/home/marcus/rustfmt/target/release/rustfmt]
 21,207,596  ???:alloc::str::<impl str>::contains [/home/marcus/rustfmt/target/release/rustfmt]
 20,497,162  ???:syntax::codemap::CodeMap::bytepos_to_file_charpos [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 20,359,629  /checkout/src/liballoc_jemalloc/../jemalloc/src/jemalloc.c:sdallocx [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]
 19,626,552  ???:syntax::codemap::CodeMap::lookup_byte_offset [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 18,100,492  ???:<strings::string_buffer::Chars<'a> as core::iter::iterator::Iterator>::next [/home/marcus/rustfmt/target/release/rustfmt]
 18,009,897  /checkout/src/liballoc_jemalloc/lib.rs:__rde_alloc [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]
 17,218,912  ???:syntax_pos::span_encoding::Span::data [/home/marcus/rustfmt/target/release/rustfmt]
 17,014,640  ???:syntax_pos::FileMap::lookup_line [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax_pos-a42779b429274f57.so]
 15,312,800  ???:<rustfmt_nightly::file_lines::FileLines as core::clone::Clone>::clone [/home/marcus/rustfmt/target/release/rustfmt]
 15,118,140  /checkout/src/liballoc/vec.rs:<alloc::vec::Vec<T>>::reserve [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]
 14,648,403  ???:_ZN6syntax5parse6parser11TokenCursor4next17h0eae928732eb485aE.llvm.DFCFA51F [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libsyntax-5fbd27a1f9bceeec.so]
 14,597,952  /checkout/src/libcore/fmt/mod.rs:<core::fmt::Write::write_fmt::Adapter<'a, T> as core::fmt::Write>::write_str [/home/marcus/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/libstd-5d73bd20dd205fcf.so]

Some stats are to be expected, such as the many calls to the CodeMap and FileMap functions. The things that stand out to me are the many calls in the comment module, calls related to String (de)allocation and concatenation and format_lines. Note: these are the functions with the most calls, which is not per se the ones where the most time is spent, but they should still give some leads as to where performance could be improved.

In order to properly wrap lines even with unicode chars, it is necessary to use unicode_width::UnicodeWidthStr to compute the length of a line instead of String::len. However, it's computationaly more expensive as noted in https://github.com/rust-lang/rustfmt/pull/3618#issuecomment-501232266


Often Show Xcode warning

Description
The project runs normally, but the following warning often appears when opening files：External macro implementation type 'PerceptionMacros.PerceptibleMacro' could not be found for macro 'Perceptible()'

Checklist

[X] I have determined that this bug is not reproducible using Swift's observation tools. If the bug is reproducible using the @Observable macro or another tool from the Observation framework, please file it directly with Apple.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Perception version information
1.3.5
Destination operating system
No response
Xcode version information
Xcode 15.4.0 and 16.0.0
Swift Compiler version information
No response

Hi @yoodu, do you have custom build configurations in your project other than the default "Debug" and "Release"? If so, this is a known issue in Xcode. We highly recommend to not use custom build configurations as it leads to lots of problems, including this one.
Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!


Service Bus Queue Subscriptions

I have a question regarding Service Bus queue subscriptions. Is it possible to specify a connection string, as opposed to selecting the subscription/resource group of the Service Bus queue? I am asking because I am trying to connect to a queue that lives in a subscription that is not accessible by my logged-in account in the Azure portal.

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

ID: aac7f75f-c324-8dab-76bb-ebedddd6f357
Version Independent ID: 87467881-a215-78e8-b406-e83d558a7172
Content: Azure Event Grid event handlers
Content Source: articles/event-grid/event-handlers.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

@sophiedasinger Thank you for your feedback! We will review and update as appropriate.

@sophiedasinger Sorry for the late reply. You can create an HTTP-triggered Function app from your logged-in account and register its HTTP endpoint as a Webhook event handler in an Event Grid under another subscription.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


zero in stringsdict is not supported for English language

When trying to upload a source English stringsdict resource with zero plural rule property, transifex client fails with:
<...> - upload of resource '<...>' failed - parse_error: Invalid plural types for string: <...> Language supports: ['one', 'other'], but found: ['zero', 'one', 'other'] instead.
Note that even though for English zero does not provide different from other pluralization rule, it is still supported by Xcode for the purpose of differentiation for cases like this:

Rule
Example

zero
no trees

one
one tree

other
two trees

Now, since we are using Transifex for our project we are forced to use if else 😬 to implement different string resource for zero and non zero cases.
In Apple's documentation we can see that zero is listed as non language dependent rule (i.e. available in all languages).

As a side note - if the rule is not used by language, it is simply ignored so it can't harm. The incorrect check done by transifex client does harm by blocking translation syncing and subsequently a workaround for it harms code quality.

Hey @andris-zalitis,
Thank you for bringing this to our attention. This is not an issue with the client. The client is not capable of looking inside .stringsdict files, neither in any other file format. This error is raised by Transifex itself. You can verify this by uploading the same source file via the UI.
Unfortunately, this is a very hard issue to solve. The way the database internals interpret plurals, each language is configured with specific rules that are dictated by the Unicode CLDR Project.
Feel free to contact our support so that issue can be in consideration by our product team.

This is not an issue with the client. The client is not capable of looking inside .stringsdict files, neither in any other file format. This error is raised by Transifex itself. You can verify this by uploading the same source file via the UI.

👍

The way the database internals interpret plurals, each language is configured with specific rules that are dictated by the Unicode CLDR Project.

Yup, but .zero should be also included additionally to language specific pluralization rules.

Feel free to contact our support so that issue can be in consideration by our product team.

That does not sound promising 😟


Scanner is off the screen when holding phone horizontally

The real solution will require React so as to rerender and recopute aspect ratios on phone reorientation

Resolved as part of https://github.com/josephrkramer/batuu-scanner2/issues/45


Fixed postgres tests.

Fixed that tests are executed on all node.
Added some logic to sort nodes to make sure the primary node is first, regardless of the order in the inventory we run against.

/azp run

/azp run


The regularization parameter optimization is not working on self-measured data

Hi,
When computing on an experimental data
drt_check.csv, the regularization optimization methods provided can not be optimized.
I mean, selecting LC method, for example, the exported DRT results show lambda of the input value in the panel.
It seems that the regularization parameter can only be optimized by customized value in the current version.
Thank you very much for checking this issue!
This tool is really useful for my current work, I will cite all related work. Thanks again for making it open-sourced!

Hello,
The regularization parameter selection method can automatically choose the reg. parameter optimally, or you can manually select the reg. parameter as you prefer. It's essential to note that the reg. parameter selection methods adapt its choice based on the data. In certain data situations, the selected lambda values (for each method) might be close to each other, resulting in less noticeable changes in the DRT curve compared to when parameters are selected arbitrarily. For instance, you could choose lambda values like 0.1, 0.01, 0.15, 0.025, etc. On the other hand, the parameter selection methods might choose values like 0.01, 0.011, 0.012, 0.05, and this might not exhibit significant changes in the DRT curve.
Therefore, regularization parameter methods aim to find a balance between over-smoothing and under-smoothing, a consideration that might be overlooked when manually selecting your own reg. parameter (lambda).

Thank you very much for the explanation.
I think there is a misunderstanding about this issue.
From my side, I just want to use the regularization parameter optimization function to present the optimized lambda, as you said it  is better than manually chosen. But, for my data, I fail to obtain the optimized lambda.
I suspect there is a bug in regularization parameter optimization in the current version.
You try some trails on the data I provide, you will see:

For instance, choose LC method, input 0.001 for 'Regularization Method', then in the exported DRT data, you will see the lambda exactly equals to 0.001. I tried several runs with different input values on the same data, the obtained (lambda) values are always exactly the same as the input ones.

I totally agree with what you have explained. But in my experiments, every time the results are exactly the same as the input ones, this seems strange.

I am also experiencing this issue where the lambda parameter is not being optimized. For example: I select the GCV method and I do not change the regularization parameter. I perform a simple run and the DRT gives me the optimized regularization parameter of 0.001, which just so happens to be the default value. I then change the regularization parameter to 1E-6 and I rerun the simple GCV. This time the optimized regularization parameter is 1E-6, the value that I unput therefore there is no optimization happening. Any help in fixing this issue would be greatly appreciative as we plan on using this tool for publications. Thank you.

drt_check.csv
Hello Mr. Edward,
Using the latest version of pyDRTtools I shared with you, I just analyzed this data shared by Jianzuo. You can try to reproduce this yourself, while I am still waiting for your data. For L-curve (LC),  0.04853899 is optimally selected. Please check the following screenshots:

For the GCV, 0.04978707 is optimally selected.

Now if I select custom and set the insert your own reg. parameter of "0.001". This is the DRT plots, and your arbitrary value will be returned as the optimal. This can only happen if you select "custom". What custom does is to tell pyDRTtools to allow users to decide on their own reg. parameter (as they like), and the value arbitrarily chosen will be returned as shown in the screenshotted anaconda shell below

To investigate your claim above, I use arbitrary reg. value of 1E-6 and I selected GCV. I got optimal regularization parameter "0.04978707 " (in contrary to your claim that pyDRTtools returned the same value of 1E-6 as the optimal). If pyDRTtool should return 1E-6 as the optimal, there should be under-regularization and the DRT curve should overfit.

This is the case where pyDRTtools use the arbitrary value of "1E-6" inserted when using "custom" (as this can only work by first selecting "custom").

We affirm that the latest code shared with you via mail works properly and has resolved the issue with optimal parameter selection or user-defined (custom) reg. parameter. In case all the illustrations above are not so clear, I will appreciate if you could share your data, like the user (Jianzuo) who shared his data with us here. Thank you so much for your interest in pyDRTtools and for getting in touch.

Hello Mr. Francesco
Thank you for your detailed response. Unfortunately I have not received a new version from you or Maradresa, so I have not been able to test the new version. Maybe it didn't get sent or I didn't receive it for some reason. Please send it again and I will test it as soon as possible. I sent Maradresa an email with one of our data files for you to test on, but I think with the new version of pyDRTtools, the results will be as you have them here. Thank you so much for your time.

Hello Mr. Edward,
Please see the screenshot below so that you can locate the day the latest version was sent your mail. I just tested with your data every works fine, and the reg. parameter is selected optimally.  You can locate the latest version which was sent to you via mail on the 29/05/2024. Thank you so much for your interest in pyDRTtools, and for getting in touch.

With your data, I selected L-curve and optimal reg. value of 0.01630123 was obtained.

For the GCV, an optimal value of "0.04978707" was obtained.

Hmmm, I have searched through my emails and cannot find an email sent on the 29th with the attachment. I have attached a screenshot of my conversation with Maradesa. If you could send it again I'd be greatly appreciative. Thank you.

SENT

@ciuccislab , So the latest version of pyDRTtools is not open-sourced?
Apparently, the results you are demonstrating to Edward can not be obtained with the
version in GitHub as shown in my previous reply.
Thanks for verifying this!

Hello Jianzuo,
We need to incorporate some new functionalities, such as displaying the optimal regularization parameter on the GUI. This will make it easier for users to locate, rather than searching for it in the Anaconda shell/prompt. We are currently working on this.
We should be able to update GitHub and PyPI by next week. If you need the latest version, please drop your email here, and I will send it to you.

@ciuccislab Thanks for the explanation!
Do not bother, I will follow the next update.

Hi @ciuccislab , thanks again for your excellent work. Has this GitHub been updated with the optimal parameter selection issue resolved? I ask because I pulled from the repo yesterday, but have found that lambda is rarely changed from its initial value. From my brief experimentation, LC sometimes slightly modifies lambda around the initial value given (with the optimiser terminating with a few evaluations), but GCV doesn't change it at all (few evaluations reported in the optimiser). I have found that if I change the algorithm in optimal_lambda from 'SLSQP' to 'Powell', then GCV becomes much more responsive (90 + function evaluations), although admittedly it seems to consistently tend to the lower end of the bounds provided, so I have just started using 1e-7 as my lambda. Before I spend any time looking further, were the parameter selection changes uploaded? If the answer is yes, perhaps there is an issue with compute_GCV or some quirks in the sensitivity to individual datasets - I am happy to send you my data if you're interested.

Thanks for raising this issue. We will look into it and let you know. Could you kindly send me your data for checking?


Fix uv__to_stat function on Nuttx with newer gcc

With a newer arm gcc (5.0+) the _DEFAULT_SOURCE macro
gets defined when the unix/fs.c file is built thus
trying to access a set of stat struct members which
are not defined on Nuttx.
By adding an extra check to see if the build is for
Nuttx we can correctly select the stat conversion
code path.
libtuv-DCO-1.0-Signed-off-by: Peter Gal<EMAIL_ADDRESS>

Related issue: https://github.com/Samsung/iotjs/issues/1313

LGTM


Threads sometimes don't render in correct order

Describe the bug
In this screenshot, the selected note is a response to my note below it, but it's being shown as a response to the note at the top.

The order of the tags in the debug json look correct
{
  "content": "Oh, cool",
  "created_at":<PHONE_NUMBER>,
  "id": "5fad2ba5080627514e12e890d0ec14f7b4a0942694041837656f8a5a1778866a",
  "kind": 1,
  "pubkey": "69074169ed68fa74c37d3926359f4100635c37eea5cfece064ed022ed06f792b",
  "sig": "34523391eeb7bcc6ea3c26cd05ff122d32da7c897ce35706533b71364c16ce195bb653e901b3fe5f966c5665af612f09b73c4d8f81020684c82c4877e022bc42",
  "tags": [
    [
      "e",
      "bca08e633fd7319e134fc8112646268eaa76c3453ecf242cdf40d342eee80f4d"
    ],
    [
      "e",
      "e29a06d29922f7f3e051429ce83b948bdcd9ed5cac15571a85361365b749c155"
    ],
    [
      "e",
      "ed3bf80b3905dea7468f292e45ef55a3e056a9d97f95f88cffe2661d145b09f0"
    ],
    [
      "p",
      "69074169ed68fa74c37d3926359f4100635c37eea5cfece064ed022ed06f792b"
    ],
    [
      "p",
      "63fe6318dc58583cfe16810f86dd09e18bfd76aabc24a0081ce2856f330504ed"
    ],
    [
      "p",
      "604e96e099936a104883958b040b47672e0f048c98ac793f37ffe4c720279eb2"
    ]
  ],
  "relays": [
    "wss://filter.nostr.wine/npub1vp8fdcyejd4pqjyrjk9sgz68vuhq7pyvnzk8j0ehlljvwgp8n6eqsrnpsw"
  ]
}

To Reproduce
Steps to reproduce the behavior:

Go to https://snort.social/e/note1t7kjhfggqcn4znsjazgdpmq57762p9pxjszpsdm9d79959mcse4qk0846t

This issue is very consistently experienced here, too. All the time. Bounty anybody?


Fix Cargo manifests

A couple fixes to the Cargo manifests of our public crates:

vulkano had both a macros and vulkano-macros feature, the latter of which is completely useless and can't be used. Now there's only macros so it's a bit less confusing hopefully.
Each crate's manifest links to its subdirectory in the repo, instead of the repo as a whole.
Each crate's manifest links to its own docs page, rather than vulkano's.
Each crate now has the readme linked.
Other miscellaneous improvements.

The new repository URLs are all deadlinks, so I think something went wrong there.


flow() not connecting the dots

Hi, there is another glitch when flowing only one of two XY lines at a time. In this case, it won't render the lines between the dots:
http://jsfiddle.net/muf8voq9/
Also, this fiddle places dots wrong since it's not a timeseries, which is #423.
My use case is a live updated timeseries, so I could do this by keeping the data somewhere else and calling load(), but then I run into issue #906, which makes it look odd.

hi
set connectNull. This should work in your case
   line: {
      connectNull: true
    }

Thanks, that helps for the lines that flow in from the right. The issue is now that the lines on the left side go missing. I've updated the jsfiddle:
http://jsfiddle.net/muf8voq9/3/

i think, that you should use the "to"-option in the flow call. with this option you can handle the movement in the flow. see

If to is given, the lower x edge will move to that point. If not given, the lower x edge will move by the number of given data points.

http://c3js.org/reference.html#api-flow

But then again, I have to keep all my data points somewhere else (probably for all columns) and always flow to the leftmost point in a certain row. Which feels a bit unnecessary and has costs in performance. In this scenario I might just as well call load().

If i get you right, it works with the to-option set to 0:
see http://jsfiddle.net/1e22junt/

Well okay, but then the old points are never removed...

see http://c3js.org/reference.html#api-flow
you can use the parameter "length" to remove old points from the chart
i am sorry. Maybe i am not understanding your problem. If this length-option is not helping you, maybe you could create another fiddle to make your issue clearer.

I think my first fiddle shows pretty good, how it stops connecting the new dots. In case it's an OS/browser related issue, here is the screenshot:

lets summarize:
if you add
    line: {
      connectNull: true
    }

then all your points will be connected,
if you want some of your point to be removed, then you could use the to-option
    chart.flow({
        columns: [
            ['data1-x', 7],
            ['data1', 200],
        ],
        to: 0
    });

Actually I am still not sure what you want to accomplish?

If you do, then you could try to initialize your chart using null-values
something like
        columns: [
            ['data1-x', 0,0,0,0,0,0,0,0,0,0],
            ['data2-x', 0,0,0,0,0,0,0,0,0,0],
            ['data1', null,null,null,null,null,null,null,null,null,null],
            ['data2', null,null,null,null,null,null,null,null,null,null]
        ]

and then start dropping your data into it (with chart.flow without using the to-option).


Project completion

Hi,
Your project is visually beautiful and also responsive, but it seems that the project is not yet finished and its logic has not been defined?
When will the project end?

I think you can use this photo as well

Thank you for your patience and your opinion the project is not clear when it will end, but I will try to finish faster.


Proxy Credentials

Can you upgrade the application, use Proxy authentication by username - password and save them?

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.


if onlyTestTsNext is set to true only install the "next" typescript

At the moment if you supply --onlyTestTsNext it still installs all the typescript packages when it only needs to install the next one.
This fixes this.
Can we merge this in ASAP please 👍

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: joshstevens19 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Can you please look at this @sandersn It's making our build time a lot longer then it needs to be due to installing all the ts packages.
Thanks

What does dtslint do as part of your build? It seems like overkill unless you are building definitely typed.

Sorted them out thanks.
In ethereum/web3 we have created all type support for our all our packages. We have chose to put this within our lib like moment and redux so we can manage it ourselves. We can then bring in contribution guidelines with maintaining types etc things we could not control much if it was outside the lib. This solves a lot of issues for our TS community but we wanted some tests written out for them just to be sure they match up, hence we used dtslint for this 👍
Cheers

@sandersn When are you planning a new NPM deployment of this?

It's deployed! Thanks for the reminder -- Definitely Typed just pulls the package from the production branch on github, so npm deployment isn't a required step for me.


I have added html.com

I have added html.com to the websites. Please approve my PR. Thank you:)

Thanks @chryzcodez for checking my PR 🙂


Prevent that people misunderstand the purpose of the …/models/design/ folder

It's meant as the storage for UML design model (german "Entwurfsmodelle") and exported diagram images, not for GUI or layout related things.

It appears there is already a readme in the design/ folder… closing this.