SBOX_FATAL_MEMORY_EXCEEDED when send pressesed

When large files are selected and send button is pressed, chrome gives this error. This is because peerjs has to send large file. Upon commenting the send line, error disappears.

possible solution: slice the files into smaller chunks and then send. Also free up memory wherever possible, like deleting file array elements that are no longer useful/sent

Also, ask users to zip large files before uploading

Also, ask users to zip large files before uploading

Done.

Also, the error seems to not appear after removing JSZip. Hence, closing.


Mutual Information Sensitivity

Checklist

[ ] Appropriate tests were added
[ ] Any code changes were done in a way that does not break public API
[ ] All documentation related to code changes were updated
[ ] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[ ] Any new documentation only uses public API

Additional context
I attempted an initial implementation of #175 and it seems to work, but it should be checked for correctness.

Don't know why the documenter can't find the version of ComplexityMeasures you want to use here?


Add position data + README Improvements

Hello there.
This pr adds position data to the module. This can be gotten via Player.position which accounts for time since the last update.
This also improves the example in the readme. The readme example had the wrong arguments for send (it's the second arg and not an option). This also doesn't set the value to connect because connect returns a Promise so you don't want to store it. I also await connect. I also include the raw VOICE_STATE_UPDATE and VOICE_SERVER_UPDATE because these are needed for it to work but not documented anywhere which I spent way too much time trying to figure out.  Thanks

Pull Request Test Coverage Report for Build 695849239

9 of 20 (45.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 75.05%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/core/Player.ts
9
20
45.0%

Files with Coverage Reduction
New Missed Lines
%

src/core/Player.ts
1
37.86%

Totals

Change from base Build 695068402:
-0.3%

Covered Lines:
1508

Relevant Lines:
2011

💛  - Coveralls


added play store data scrapper

Description
added an application developed using streamlit which can scrap the data in csv format of the reviews of any app from play store simpley jsut by entering app name, app id , number of reviews using data scrapping.
Fixes #676
Type of change

[X] Added a new machine learning frameworks, libraries or software.
[ ] Documentation update

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

@sanjay-kv please merge this Pr along with the level and label of gssoc'24


update codec variable to remove mb

It seems that the application is already appending mb to the numerical value specified in the APPSMITH_CODEC_SIZE variable so setting the value to the existing 500MB results in startup errors.
Description
Provide a concise summary of the changes made in this pull request
Pull request type
Check the appropriate box:

[ ] Review Fixes
[ ] Documentation Overhaul
[ ] Feature/Story

Link one or more Engineering Tickets
*

[ ] A-Force
[x] Error in documentation
[ ] Maintenance

Documentation tickets
Link to one or more documentation tickets:
Checklist
From the below options, select the ones that are applicable:

[ ] Checked for Grammarly suggestions.
[ ] Adhered to the writing checklist.
[ ] Adhered to the media checklist.
[ ] Verified and updated cross-references or added redirect rules.
[ ] Tested the redirect rules on deploy preview.
[x] Validated the modifications made to the content on the deploy preview.
[ ] Validated the CSS modifications on different screen sizes.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Outputs svd.in.m

Seems like a leftover from debugging, but should be removed (or optional, with the default not outputting it): hmatrix-svdlibc-0.5.0/svdlibc/las2.c:  svdWriteSparseMatrix(A, "svd.in.m", SVD_F_DT);. I don't see it on github, but it's on the version uploaded to hackage.

Is there any way I can help with this issue? It just might need to be reuploaded with the version on github.

Whoops. Thanks for pointing this out. Indeed it looks like my tree was dirty when I cut the release.

Fixed in <IP_ADDRESS>.


Is it possible to use chrome-devtools over safari's on mac?🧐

https://github.com/tauri-apps/tauri/issues/981#issuecomment-694014485
If possible, how?🧐

Not possible.
The only thing you can do, if your frontend can run outside of a tauri window, is opening your frontend in a chromium based browser for development...


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2024-06-23T14:15:31+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
6c337186804ab73eb9add7dfe0f6ae69e2a13aa3
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
9ed1259c81bbb0f02dbe28fdf8c9fb5190215427
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
9ed1259c81bbb0f02dbe28fdf8c9fb5190215427
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
1397c9f79d08831d76914c79237142306d51cd91
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
e68908a512a38a18b5baf481b723dc6393e3465c
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
5f3860ebe00cccb6676b9e0dd460afff20b8bfdb
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
2d7b02c76660e196e651fd861d8e091237c4e92c
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
915ffc5e0d60add0405634b7ff3ff0e6660644dd
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
e155fab9e210b58bad3b97444a171fbab8c5b581
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
89f4692be721e5b3fc786377018a0d5612b8216b
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.22
4ec73e95a485bff21056b50b9e33097133cf7a3e
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest


🆕 Software Suggestion | Passbolt

Basic Information
Name: Passbolt
Category: Password Managers
URL: https://www.passbolt.com
Description
Passbolt is a password manager for teams. It is open source and uses OpenPGP.
In browser, it requires a browser extension to ensure security, as it uses OpenPGP.js.
Why I am making the suggestion
I was surprised to see pass listed but not Passbolt. I couldn't find an existing thread, so figured it'd be worth suggesting at least.
My connection with the software
I once set up the self-hosted version for an organisation I was the sysadmin for at the time.

[x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.

Already suggested in prism-break but no reply https://gitlab.com/prism-break/prism-break/-/issues/2184
In the same category you have:

psono https://gitlab.com/prism-break/prism-break/-/issues/2186 - Already in the worth mentioning list
https://passit.io/
And bitwarden already included.

I used passbolt and bitwarden in a small team a few moths ago. Personal opinion Passbolt is better in the technical/security side that bitwarden at least at that time.
Bitwarden it seems more like a cloud service for personal use. It the technical/management side my personal opinion is a mess, I used the official documentation to do all the installation and config. The version I used had layers of microsoft stuff in a linux environment.
Passbolt the version I used was very good, fast that bitwarden, all tech/library used is open source with good license, the team are very aware of security and privacy, and do security audit frequently. The main issues, old data remains in the DB and user administration is lacking, for a personal use, self-hosted I think is wide better. From security perspective it seems good, I remember even the databases all data was encrypted, I remember even the admin don't have the power to see the passwords of user, admin user just do some admin tasks. But the same old gpg mechanics problem if you are familiar with that. All the issue mentioned was already known and already in the roadmap, maybe they are already fixed.
You can run in a docker container in you own machine and used as "Local" password manager, is lightweight. The free version of passbolt lack some feature that have the free version of bitwarden. But perfectly fine for use it with a small team/family or even personal.
Passit.io is still in development lack features.
Psono in development, more advanced in features that passIT, in my opinion what I used at that time.
In my opinion I would said:

Passbolt Cloud/Self-host/Team/Personal Use
Bitwarden Cloud/Personal use
Go for KeePassXC - Local

From my personal experience with Passbolt (as a user, not administrator), it seems to be pretty lackluster (no offense to whoever is developing it):

unable to change masterpassword without exporting PGP key, changing the pasphrase and then doing an "Account Recovery" with the new key
seems like only the passwords itself are actually encrypted, all other data seems to be not fully encrypted
doesn't support multiple urls per login
manual backup of PGP is mandatory if you want to use it across devices, or if you lose your device
no TOTP support as far as I can tell

unable to change masterpassword without exporting PGP key, changing the pasphrase and then doing an "Account Recovery" with the new key

PGP mechanics unfortunately. You own the key.

manual backup of PGP is mandatory if you want to use it across devices, or if you lose your device

Yeah well that's a good thing, you own the key. I remember even the admin can't do anything, except recreate the account.

no TOTP support as far as I can tell

Is supported, only for the pro version I'm afraid. Anyway take as example the recently twitter hack, it seems all the accounts use 2fa, what is matter if all data is encrypted. If is local self-hosted doesn't matter, if you use a public vps, you should use a vpn
Overall, I think people first need to be familiar with PGP, PGP have its own quirk, and install Passbolt, use it and be familiar with all they documentation they provided.

PGP mechanics unfortunately. You own the key.

Except that's not a PGP limitation, the key is available to the browser extension, the browser extension should be able to regenerate a key for you with a new passphrase the same way a desktop app like the gnome keyring can.

@lynn-stephenson Would you have a time to scan over this? Seems like a nice addition for companies. I wonder how it holds up against something like bitwarden.

@blacklight447-ptio I'll look into it. :)

GPG is a hard to use tool, and it's generally easy to shoot yourself in the foot. This does adopt some good practices, but I see no reason to recommend a harder to use tool that is also partially/is behind a paywall when there are other better existing solutions.

Passbolt from installation to use is quite easy, they provide docker, just run it and start use it. Is not behind a paywall 😕 except the "PRO features", if you want ldap, audit log or business support. The Community is totally functional even for a small team like 20 people (when I used it). Is a good self host alternative.

I still think passbolt is not quite user-friendly for the end user though, at least not even close to something like Bitwarden.
For me, these 3 points remain dealbreakers:

unable to change masterpassword without exporting PGP key, changing the pasphrase and then doing an "Account Recovery" with the new key
seems like only the passwords itself are actually encrypted, all other data seems to be unencrypted
doesn't support multiple urls per login

As we are most likely going to be removing Gnu Privacy Guard as a recommendation, and in addition to other password managers having better cryptography designs and under more scrutiny, this does not seem recommendable.


prepare release 3.1.2: update CHANGELOG for kic 3.1.2

What this PR does / why we need it:

Update CHANGELOG for KIC 3.1.2 release.
Which issue this PR fixes:

part of #5693.
Special notes for your reviewer:

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

The Changelog is missing the link at the top and the diff with 3.1.1 at the bottom

Updated in the new commit: https://github.com/Kong/kubernetes-ingress-controller/pull/5694/commits/ce683bd659dfd4b58f9b595b117cc4f1cfeb2942


Fix incorrect spelling of CocoaPods

This pull request fixes the incorrect spelling of CocoaPods in the README.

The GitHub description also has the typo, but can't PR a fix for that.

:+1: :+1: Fixing the description


Make swift-application plugin support the configuration cache

This issue is about making the swift-application core Gradle plugin support the configuration cache.
Upon completion, all configuration and tasks provided by the swift-application plugin are compatible with the configuration cache.

Duplicated by https://github.com/gradle/gradle/issues/13515


Missing procedure entry point "GetDpiForWindow" in DLL gw2addon_gw2radial.dll

Just installed v1.4.2 of GW2 Addon Manager fresh after removing all addon directories, selected only GW2Radial, hit update, then ran the game. Once through the GW2 game launcher, the missing DLL entry point error dialog pops up. Hitting OK allows the game to start, but GW2 Radial does not appear to be loaded. Shift-Alt-M doesn't do anything (but bring up the in-game map, as I would expect if the hotkeychord isn't being trapped by GW2Radial).
To Reproduce
Steps to reproduce the behavior:

Install GW2_UOAOM_1.4.2 clean.
Run it.
Select ONLY GW2 Radial, then click "Update"
It installs Addon Loader and GW2 Radial, then says it is done.
Close the addon manager.
Launch the game.
See the error dialog after logging in and clicking "Play". Click OK.
Game starts normally, but without GW2 Radial functioning.

Expected behavior
No error, and the addon present and working.
Screenshots
If applicable, add screenshots to help explain your problem.
System configuration (please fill in):

OS: Windows 8.1 Pro
GPU: Radeon R9 390X
Chainloading, if any: Only whatever GW2 UOAOM and GW2Radial does in the latest version.

Not sure, but I think that is a Windows 10+ winuser function which isn't available in Win 8.1, so maybe it is not finding it in the loaded system DLLs, and is defaulting to the referencing DLL?

Yeah. It's recommended to use GetDpiForMonitor for Win 8.1, and GetDeviceCaps for older systems.
https://mariusbancila.ro/blog/2021/05/19/how-to-build-high-dpi-aware-native-desktop-applications/
If that helps any.

While I can't release a new build right away for just this bug, I can at least provide you with a fixed version:
gw2addon_gw2radial.zip.
This should resolve the issue and the next patch release will include it. Let me know if it helps!

It works, but had a very strange error crop up after I opened the config menu with Shift-Alt-M, and then switched to my second monitor where this web page is to type this message.
GW2Radial Fatal Error
Fatal Error: shader compilation failed! Error code was 0x88760B59. Please report..(etc)
Probably a different issue.

Now it always happens when launching the game and getting to character select screen, but before the characters are loaded.
I should also point out that I have D3DCompiler_43.dll in bin64 instead of D3DCompiler_47.dll as mentioned in your other issue on core dependencies. Curious. Not finding any good info on the version differences.

Looks like 43 is for Windows 8.1 and 47 is for Windows 10.

Was able to launch the game and get fully in-world before it popped up this time. Seems to be inconsistent when it happens.
0x88760B59 is D3DXERR_INVALIDDATA - Guess it will give more info in the trace window if you're debugging, but it might be one of "those" errors one user sees that doesn't show up in testing. Just to be on the safe side, I am going to restart the system. Never know if a driver has gone off the deep end from corrupted internal state and makes for monsters that go bump in the night.

OK. After a full restart, still getting the error after logging in and getting in-world. I removed GW2 Radial by renaming the DLL, and logged back in. The game runs fine now, so it does appear to be something GW2 Radial is doing. Going to leave it out until you have a chance to get back to me. I know you're extra busy atm with GW2 addon updates as well, so no rush. Thank you for your time! :)

It looks like applications are expected to distribute the correct updated d3dcompiler_47.dll, so here's what we'll do. Here's the DLL: d3dcompiler_47.zip
I don't know where it'll get picked up by the game, so could you please try placing it in bin64 and, if that doesn't work, in the root directory of the game? I'll make sure the new Addon Manager installs this.

OK. So I put the _47.dll into the bin64 dir, renaming the _43 one to .tmp. Started the game. It gave the same shader error again.
I went back into the bin64 directory, and there was a new _43.dll file there. Looks like something is re-creating it if missing. I deleted the new one and copied the _47.dll to the main dir then restarted. Back in game now for a few mins, got into the Radial options, reset my hotkeys and ran through the mounts, testing. No problems. (I like the new dismount when clicking the button a second time! :D) It also still recreated a copy of the _43.dll in the bin64 dir, but it apparently is using the _47 one in the main dir, according to Process Explorer, so I think that fixed it.
I'll keep playing for a while and if I have any other issues, I'll update here this evening.
Thanks again for the speedy fixes and support! :)

Looks like this is all fixed now. Had a nice session without any more crashes or other errors. Gonna close this out now, and will open a new issue if something crops back up later.


Dependabot

Pull Request Test Coverage Report for Build 360

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 355:
0.0%

Covered Lines:
29

Relevant Lines:
29

💛  - Coveralls


Update database again

Sponsors gave another new dataset. I missed a new column.

Realized that I had missed a column in the new dataset provided to us which screwed up the county search from working properly. Fixed this issue. Had to reimport the new data a couple of times so because of this it took some time.
{t:60}


Factor folder structure to follow gradle guidelines

@aleffert  Please update readme and if any other documentation.
I have moved contents of android/source folder to the root of the repo.
I have verified gitignore to not include any unwanted contents. Also, I have updated Travis scripts to have correct references of the app folders.
We will not merge this PR until we have all other PRs merged and no PR is pending, so as to avoid conflicts.
cc @nasthagiri @shahidtamboli

@rohan-dhamal-clarice Looks good. I pushed a commit with some minor README changes - just updating path references.
Be careful merging, you don't want to lose the changes from the outstanding PRs.

It's okay if those PRs have to be recreated. It should be easy to use git diff to figure out what they changed and then you can use
patch -p3 < {patchfile} to apply them. (I think it's going to be a '3', but I might be off by one).

I merge this as we just have two small PRs pending. Shouldn't cause any problem.


Why do website examples of DOM use 'attributes

The 1st example on http://cycle.js.org/ and others use 'attributes in the attribute' object. This appears to be redundant and I have seen no other examples using this. Is it purely historical?

input('.field', {attributes: {type: 'text'}}),

Apparently with snabbdom you have to use attrs or props, you can’t just pass the attributes directly as the second argument.

Property is that can be set on the DOM element itself input.value = 1. attribute is that should be set with input.setAttribute('type', 'text'). In snabbdom there was mad clear distinction, API is a little bit verbose. I had an issue on that https://github.com/paldepind/snabbdom/issues/83

So here is not always a 1 to one properties to attributes? We thought so but unable to find a clear list of the differences. Thanks

some props maybe set on elements and they do not set any attributes for example el.innerHTML = 'xxx' does not set any attributed, but does something else. And attributes are attrubtes el.setAttrubte("data-sectect", 'xxx')will setdata-secret` attribute on the element.

Though I think your data-secret example would normally be accessed as el.dataset.secret?

Thanks for the answer. I'll close as now understand better.

Though I think your data-secret example would normally be accessed as el.dataset.secret?
It seems not in IE prior 11)

Wow, yes. This isn't new. More concerning is not Opera Mini.

For completeness this article is a good explanation

You should use attributes in only two cases:

A custom HTML attribute, because it is not synced to DOM property.
To access a built-in HTML attribute, which is not synced from the property, and you are sure you need the attribute.
For example, value in INPUT.


Checking do_not_track_routes after start session

You call session_start() that sends Cache-control: no-cache headers before checking do_not_track_routes. So it is inpossible to set http cache.

Yes, this is a problem.


PyPy 3.10 Wheels

Hey, I'm wondering if you could add pypy3.10 wheels for watchfiles? Currently the following minimal dockerfile will fail:
FROM pypy:3.10-7.3.12-bullseye
RUN pip install watchfiles

Of course you can fix by installing the rust toolchain and compiling from source, but it would be nice to have wheels in pypi.

Can do, but waiting for https://github.com/PyO3/maturin-action/issues/166.

fixed in #248.

Thanks!


Hollow History UI has hardcoded time zone

https://github.com/Netflix/hollow/blob/f0126b04575a897b3e7ceefa07baa0f354b79683/hollow-diff-ui/src/main/java/com/netflix/hollow/history/ui/VersionTimestampConverter.java#L27
For the sake of international users please consider changing this to use the JVM's default time zone as provided by the host.

I don't think using JVM's default time zone would be ideal specially if you deploy the history UI using UTC (as a lot of people do).
With that said, I just opened a pull request that adds a new TimeZone parameter to the HollowHistoryUI  and HollowHistoryUIServer so users can specify it
https://github.com/Netflix/hollow/pull/261

Thanks, I'm happy with this solution.


Pairing with Alexa not working

Log file attached.
alexa.txt

Can you try if you can pair with the branch containing the iOs fixes?
"support-ios"
I was able to pair with iOs with this branch but most of the fixes in it are too hacky to be able to merge them as is

Log from from the iOS branch. In the app, it takes quite a while before I finally fails up with: "Is this device set up for control with another assistant or app?"
Log File attached
alexa1.txt

The commissioning seems to have been successful per node-matter logs:
GeneralCommissioningClusterHandler Commissioning completed on fabric #43153954716076642 as node #009E91B49E9051D0.
iOs actually does multiple commissioning in a row, so maybe this is what is failing.
The last action seems to read the features of the NetworkCommissioningCluster to check which connectivity is supported on the device.
Not implemented yet in the main branch, I will send a MR shortly to fix this.

Created https://github.com/mfucci/node-matter/pull/162
Can you try with this branch "define-network-cluster"?
Now the last read of attribute 0/49/65532 should return the correct value.
I don't have an Alexa device on my side so I will rely on you for the testing. Hopefully I will be able to debug all the issues in 3 / 4 rounds of fixing.

Here's a run from the  "define-network-cluster" branch.  I'm still getting the same failure message from the app.
If it would help, I'd be glad to send you an Alexa "Dot" as thanks for your work. Just send me your info.
alexa2.txt

Thanks for offering to send me a "Dot"!
Let me merge down all the fixes I did to support iOs and there is some chance that it will work as well for Alexa.
I will let you know when pairing with an iPhone is working in master, probably in a couple of days.

I remember that I was stuck at the same step you are now with Alexa when debugging iOs...
And Android / iOs / Alexa are all using the same codebase to implement the controller so behave in a similar way.

Nice work! I just cloned add-android-support and Alexa now works! Very cool to saw "Alexa, turn on light" and have it reply "ok" and see node-matter respond appropriately.
I do see an error in the log (attached) and I would guess persistence is not there yet? i.e. I have to delete the Alexa device and re-commission every time I start the node-matter server. If I don't, I see messages like the following:
2023-0-4 7:42:3.619 INFO Device<EMAIL_ADDRESS>2023-0-4 7:42:3.698 INFO Device Listening
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ ██▀▄▀▄█ ▄▄▄▄▄ █
█ █   █ █▄▀▄▀▄█ █   █ █
█ █▄▄▄█ ██ ▀▀▄█ █▄▄▄█ █
█▄▄▄▄▄▄▄█ █ ▀▄█▄▄▄▄▄▄▄█
█▄ ▄█▄ ▄▄ ▀ █  ▄▀██ █▀█
██ █▀▀ ▄▄█ █ ▀▄▄██ ▀█▀█
█▄▄████▄▄▄▀▄▀ ▀██▄▄▀▄▀█
█ ▄▄▄▄▄ █  ▄█▄█▄▄█▄ █ █
█ █   █ █▄▀▀█▄ ▄▀▀▄ ▀██
█ █▄▄▄█ █  ▀█▄█ ▀█  ▀ █
█▄▄▄▄▄▄▄█▄█▄█▄██▄██▄█▄█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
QR Code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT:Y.K90AFN00KA0648G00
Manual pairing code:<PHONE_NUMBER>2
2023-0-4 7:42:3.919 ERROR ExchangeManager Error: Cannot find a session for ID 55274
2023-0-4 7:42:5.412 DEBUG MessageExchange onMessageReceived id:0/54877/205441394 t:0/48 reqAck:true payload: 15300120a999c1636e2e6fe11c50a11e93cb79461048b590671d8d2c8d9c596eb4e8f2ee2502a5d8300320d9fb5c54de33a95e712719af9b6626a4835691cc16d81a6fa8b09fc1e5c51bdf300441047a593180860c4037c83c12749845c8ee1424dd297fadcb895e358255d2c7d2b2a8ca25580f2626fe579062ff1b99ff91c24a0da06fb32b5be20148c9249f565030061013fccb420c8fa77b3fcc3065e5f4e43c300710c62512664d0c3821b5d48539b0d94ad218
2023-0-4 7:42:5.418 INFO CaseServer Case server: Received pairing request from udp://<IP_ADDRESS>:5541
2023-0-4 7:42:5.427 ERROR CaseServer An error occured during the commissioning Error: Fabric cannot be found from destinationId
2023-0-4 7:42:5.433 DEBUG ExchangeManager sending id:0/54877/3773895937 t:0/64 acked:205441394 reqAck:true payload:<PHONE_NUMBER>000200
2023-0-4 7:42:5.487 DEBUG MessageExchange onMessageReceived id:0/54877/205441395 t:0/16 acked:3773895937 reqAck:false payload:
....
alexa3.txt

woo ... awesome!

@JimBuzbee : correct, persistence is not implemented yet...
I will close as fixed then.
Is there a screenshot of some interface showing node-matter paired that you can take and attach here? Just to prove to non-believer that it indeed works :-)

Here's an Android Alexa screenshot after node-matter has been added.

Thanks!

@JimBuzbee Is it the "normal" Alexa App on Android? which version exactly is that? Maybe I can also try if my "one alexa device in the whole house" can install that one? ;-)

@Apollon77 Yes, that is the normal Alexa app, version 2022.21. It is also the only Alexia device i have in the house for me as I typically use Google Home.
I'm not clear on the Matter infrastructure. Does anyone know if we'll be able to control a node-matter "device" from both the Alexa app and Google home app? And what is the vision for commissioning multiple virtual devices through node-matter? Multiple QR codes?

Cool. I really appreciate the work you guys are doing. It fits my needs well to think of node-matter (or uses of it) as a bridged device like a Hue bridge etc. I have lots of older devices such as Wemo, Govee, etc. that will never see official Matter support and I also have a lot of custom IOT devices. All of which I can control locally via custom code, so they should be easy to integrate to node-matter in some fashion.  It would be great to unify everything. I might even dig up some old X10 devices fo kicks. Wouldn't it be funny to integrate 1970s technology into Matter :-)

My alexa on my Tablet shows version 2.2.490414.0 from 7.12.  .... android 8 and older.

@JimBuzbee my goal is to integrate it as Bridge and controller into iobroker as plugins. So then all iobroker devices and stuff is available as bridged devices and it can also pair other matter compatible devices. Let's see how all that goes ;-)

@Apollon77 - Here's a screenshot of the "about" screen on my Alexa app, running on Android 13.

Then the same cool. So I can also try my wall Tablet to pair. ;-))

Verified it :-) Cooool

When you pair, are you using the  manual code<PHONE_NUMBER>2 (alternatively visible QrCode) or 20202021?
Do you have to have an Alexa device in the network, e.g. Echo?

Thanks!

I used the QR code. The only Alexa device I have on the network is an Echo Dot, 3rd gen.

Gotcha. Thanks. Think I need to get a Alexa device in my network to be able pair, it appears. Appreciate all updates in this thread.

@JimBuzbee, forgot to ask, are you running node-matter on a Raspberry Pi, MacBook or ? Thanks.

@javierbarellano4v - I've been switching back and forth a bit between a Raspberry Pi and a Macbook. I think when I was doing the Alexa testing, I was using the Pi. Most recently I've been only using a MacBook with Google Home, not Alexa.

@JimBuzbee  Thanks.
In terms of Alexa, when you added a Matter device with Alexa App on Android, did you add it as a "Other" device and then selecting 'Matter' as  the connection type which then prompts "Does your device have a Matter logo?"

Yes - That is the path I took. Selected "Yes" then "Scan Qr Code", then scan code.

In fact the  "longer" manual pairing code<PHONE_NUMBER>2 from above) is in the QR code too, so use this one

@JimBuzbee @Apollon77 Successfully paired (used QrCode) node-matter running on MacBook in my home environment once I setup my Alexa Echo Dot. Upon success, Alexa Echo Dot audibly confirmed adding a "light bulb.."
Initially, had trouble but the Alexa app on my Android table, recommended to "reconnect" my matter-enabled device so I relaunched node-matter and bingo! It discovered it, paired it. Able to instruct Alexa Echo Dot to turn off and on the "light bulb"
Very cool!
node-matter/MacBook
Alexa app/Android tablet
Alexa hub/Echo Dot

@JimBuzbee Hey, I tested today again with Alexa and was surprised because pairing was no longer possible ... It stops when handling the certificate signing ... It seems to me they blocked self-signed (aka Development) devices which would be really bad ...
From what I can see is that some days ago I updated to a new Alexa App on my Tablet ... If you have time it would be awesome if you could also check it and verify that ...
@mfucci @turon FYI

Playing with it now - not having much luck. The app itself seems to hang up. I see lots of "odd" messages from  "adb logcat | grep -i amazon"  :
02-03 17:01:04.434  7413  7515 E Metrics:NonVolatileBoun: remove - Unable to delete the file./data/user/0/com.amazon.dee.app/app_NORMAL_ANONYMOUS/1675468157553: open failed: ENOENT (No such file or directory);
02-03 17:01:04.434  7413  7515 E Metrics:BatchTransmitte: QueuePusher.sendBatches - Unable to send  NORMAL_ANONYMOUS queue batchesjava.io.FileNotFoundException: /data/user/0/com.amazon.dee.app/app_NORMAL_ANONYMOUS/1675468157553: open failed: ENOENT (No such file or directory);
02-03 17:01:07.523  7413  7951 W .amazon.dee.app: Cleared Reference was only reachable from finalizer (only reported once)
02-03 17:01:07.577  7413  7951 I .amazon.dee.app: Explicit concurrent copying GC freed 535979(26MB) AllocSpace objects, 310(9120KB) LOS objects, 50% free, 27MB/55MB, paused 242us,725us total 448.424ms
02-03 17:01:07.756  7413  7427 W SQLiteConnectionPool: A SQLiteConnection object for database '/data/user/0/com.amazon.dee.app/databases/AlertRecords.db' was leaked!  Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
02-03 17:01:07.822  7413  7951 I .amazon.dee.app: Explicit concurrent copying GC freed 1469(117KB) AllocSpace objects, 0(0B) LOS objects, 50% free, 27MB/55MB, paused 155us,252us total 234.344ms
02-03 17:01:07.984  7413  7951 I AlarmAuthTokenManager: Cancelling alarm with actioncom.amazon.comms.ringservice.ACTION_AUTH_TOKEN_ALARM

Got it to try, but failed. "adb logcat | grep -i matter" showed a bunch of messages like so (I modded session id with XXX):
02-03 17:13:29.184 17230 17474 I [ELEMENTS]: [matter-provisioning] making network request for: {"path":"https://alexa.amazon.com/api/gordonservice/v1/sessions/XXXXXXX/checkPairingStatus","queryParameters":{"commissionSessionID":"XXXXXXXX"}}
02-03 17:13:29.329 17230 17474 I MobilyticsMetricsServic: react.lmnt.smart-home.matter.pairingStatus.responseTime.mobilytics-operational latency 0.136 seconds
02-03 17:13:29.330 17230 17474 I [ELEMENTS]: [matter-provisioning] ALPHA DEBUG: pairingStatusHelper: rawResponse: {"endpointId":null,"failureReason":"COMMISSIONER_FAILURE_INTERNAL_ERROR","pairingStateInfo":{"detailedState":"PASE_SESSION_FAILED","userInputInfo":null},"pairingStatus":"FAILED"}
02-03 17:13:29.330 17230 17474 I [ELEMENTS]: [matter-provisioning] ALPHA DEBUG: PairingStatus response: {"endpointId":null,"failureReason":"COMMISSIONER_FAILURE_INTERNAL_ERROR","pairingStateInfo":{"detailedState":"PASE_SESSION_FAILED","userInputInfo":null},"pairingStatus":"FAILED"}
02-03 17:13:29.330 17230 17474 E [ELEMENTS]: [matter-provisioning] pollPairingStatus: pairing failed with failureReason: COMMISSIONER_FAILURE_INTERNAL_ERROR
02-03 17:13:29.332 17230 17474 I [ELEMENTS]: [matter-provisioning] updateManagerStateAndPublish is called with state SETUP_ERROR
02-03 17:13:29.338 17230 17474 I [ELEMENTS]: [matter-provisioning] publishToEventBus: chipProvisioning publishing event: Matter:GD:StatusUpdate
02-03 17:13:29.348 17230 17474 I [ELEMENTS]: [guided-discovery] Recieved matter state change event with message: {"uuid":"aacf922c-8326-4110-8367-de07e707ddd9","source":"Local","eventType":"Matter:GD:StatusUpdate","date":null,"ttl":0,"payload":"{"message":"chipManager state is updated"}"}

Finally got a coherent response from Alexa. Something has definitely changed. Here's the logcat error followed by the Alexa screenshot
02-03 17:53:06.396 30894  3599 I [ELEMENTS]: [matter-provisioning] ALPHA DEBUG: pairingStatusHelper: rawResponse: {"endpointId":null,"failureReason":"COMMISSIONER_FAILURE_UNSUPPORTED_DEVICE","pairingStateInfo":{"detailedState":"PASE_SESSION_ESTABLISHED","userInputInfo":null},"pairingStatus":"FAILED"}
02-03 17:53:06.396 30894  3599 I [ELEMENTS]: [matter-provisioning] ALPHA DEBUG: PairingStatus response: {"endpointId":null,"failureReason":"COMMISSIONER_FAILURE_UNSUPPORTED_DEVICE","pairingStateInfo":{"detailedState":"PASE_SESSION_ESTABLISHED","userInputInfo":null},"pairingStatus":"FAILED"}
02-03 17:53:06.396 30894  3599 E [ELEMENTS]: [matter-provisioning] pollPairingStatus: pairing failed with failureReason: COMMISSIONER_FAILURE_UNSUPPORTED_DEVICE
02-03 17:53:06.397 30894  3599 I [ELEMENTS]: [matter-provisioning] updateManagerStateAndPublish is called with state MATTER_DEVICE_NOT_SUPPORTED
02-03 17:53:06.397 30894  3599 I [ELEMENTS]: [matter-provisioning] publishToEventBus: chipProvisioning publishing event: Matter:GD:StatusUpdate

COMMISSIONER_FAILURE_UNSUPPORTED_DEVICE looks like that :-(

Can you try to go back to the Alexa App version  we had beginning january? I think was one of the december ones?

I uninstalled the Alexa app and went to the Google Play store to re-install. Now it works again. There was an option on the play store Alexa page to allow automatic updates, so I unchecked that - hope it wasn't for all apps and hope Alexa can't bypass. We'll see. Screenshot of Alexa version

Interesting ... i have the same version of the app ... but ok ... I will try again now ... too

Mine started failing again. Uninstalled and reinstalled twice without success.

:-( COuld you try the version of alexa app  from end december

PS: Are you on discord? Please send me your Username

I'm curious about the Alexa devices you have. When I try, the requests don't come from the Android app but from my Fire TV. Could it be possible that it's linked to the version of the Alexa devices?

This could also be the case ... then it would be not the App but a "Firmware" and we have no chance to workaround it ... Honestly never did look at the IP :-)

@s-hadinger - The only Alexa device I have on my network is an Echo Dot.
@Apollon77  - I went back to version 2022.21 and still failed The "adb logcat" file looks the same or similar during an attempt. I see a call to "checkPairingStatus" on https://alexa.amazon.com/api/... followed by a debug message of failureReason":"COMMISSIONER_FAILURE_UNSUPPORTED_DEVICE" - Leads me to believe the significant change was on the Amazon server side - wonder if they started using a similar "developer" setup to Google where you need to register your development "device"
discord - have not used it.

I would more asume a "Firware update of the Echo devices" ... but yes :-( Difficult ... I did not heared of any dev dloper account things so far.
Discord more like a "chat tool"

FYI - I successfully paired "Device.js" with Alexa using main as of Feb 7 - Not sure what to make of the inconsistencies.

Alexa app version 2023.3 build 2.2.495391.0

Thanks for reporting this good news. I can't test this week, but I'm eager to see what changed. Could you also report the version of your echo device?

Thanks. Mine is still at<PHONE_NUMBER>

I will check tomorrow ...

Ok, fort me he used the oldest device I had an Echo dot ... with<PHONE_NUMBER> as FW and it did not worked

I kind of expected it to fail this morning, but I was able to pair and control a node-matter "light".
I still can't pair "sensor" devices, but I think the message has been updated. It now says "This device can't connect to Alexa. We're working on ways to connect this device to Alexa, but right now it's not compatible"

Ok, why not sensor is clear, please check the Alexa Infos in Readme ... they only have OnOff and Light implemented so far!

Good news, I updated the Alexa Android App, and I can now pass the CSR Request and have the device fully commissioned.

hhuui .... which version? then I check later (again) too ;-) Was it now asking if you want to add a inofficial device?

The App asked to update as soon as I selected the Matter button.
Now the app version is:

Client version: 1.24.208499.0
Build version: 2.2.495949.0
App version: 2023.3

I verified it ... also works again for me


Add SNP Protocol

First of all, thanks for this outstanding project. I have SNP networking partially implemented now, so here's a draft PR in case anyone tries to work on it before I'm done.
There's still a fair amount left (wrapper methods, documentation, test cases, final cleanup), but feedback is always welcome!

Thanks for the contribution @cilki! I've taken a quick look over your PR and left some comments/ideas on what I've observed. Let us know when you think the feature is ready for a final review.

@GabrielMajeri Thanks for the early feedback!
I'm currently blocked on the test code. For some reason Transmit works fine, but Receive never actually gets a packet. I've messed with the receive filters and tried on physical hardware to no avail. I can't imagine it being a driver bug, so there must be something I'm missing.
Anyway, once I can figure that one out, I'll be able to finish the rest of this. Any debugging tips? Like maybe there's a way to run the driver under a debugger or get debug log output? Thanks!

Any debugging tips? Like maybe there's a way to run the driver under a debugger or get debug log output? Thanks!

There's been some discussion towards how uefi-rs apps can be debugged on https://github.com/rust-osdev/uefi-rs/issues/289
There are some issues currently, but maybe the ideas in that thread can be of help 😅

@cilki I've noticed you're making some changes to this PR. When you're finished, please remove the Draft label and feel free to ping me for a final review 😁

My use case for this fell through, so I'm not finding time to finish the testing. Hopefully someone can pick it back up someday.

@cilki Understood. I'm closing this PR for now and opening #431 to track future implementation of the SNP.


docs: fix readme error

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


need the output of the namespace in log-metric-filter submodule to reuse in metric-alarm submodules and potentially others

Is your request related to a problem? Please describe.
When I want to create an alarm from a metrics I set for exemple with the submodule metric-filter
module "metric_test" {
  source = "myrepo.com/modules/log-metric-filter"
  version = "5.4.0"

  log_group_name                      = aws_cloudwatch_log_group.dummy.name
  pattern                             = "PATTERN"
  name                                = "dummy"
  metric_transformation_default_value = 0
  metric_transformation_unit          = "Count"
  metric_transformation_namespace     = "DummyNameSpace"
  metric_transformation_name          = "Dummy_Name"
  metric_transformation_value         = 1
}

in my other module I would like to get the namespace directly from metric_test module
module "alarm_test" {
  source = "myrepo.com/modules/metric-alarm"
  version = "5.4.0"

  create_metric_alarm = var.create_metric_alarm
  actions_enabled     = true
  alarm_name          = "dummy"
  alarm_description   = "Alarm for the dummy lambda"
  alarm_actions       = [data.aws_sns_topic.topic.arn]
  metric_name         = module.log_metric_filter_dummy.cloudwatch_log_metric_filter_id
  comparison_operator = "GreaterThanThreshold"
  datapoints_to_alarm = 1
  evaluation_periods  = 1
  threshold           = 0
  treat_missing_data  = "notBreaching"
  namespace           = module.metric_test.cloudwatch_log_metric_filter_namespace
}

Describe the solution you'd like.
add an output in log-metric-filter with something like that:
output "cloudwatch_log_metric_filter_namespace" {
  description = "The namespace of the metric filter"
  value       = try(aws_cloudwatch_log_metric_filter.this[0].metric_transformation.metric_transformation_namespace, "")
}

Thanks for your consideration !

I close the issue as my change will not be so useful using local variable

bad choice in the closing


Improve usage of table filters

What is currently missing?
Currently, syncing table filters into search parameters are done on component level, like this:
function StatusFilter() {
  const [searchParams, setSearchParams] = useSearchParams();
  const status =
    (searchParams.get("status") as RequestStatus | null) ?? "CREATED";

  const handleChangeStatus = (nextStatus: RequestStatus) => {
    searchParams.set("status", nextStatus);
    searchParams.set("page", "1");
    setSearchParams(searchParams);
  };

...

}

The syncing responsibility is encapsulated in to each filter component.
If i want to get the status filter value in other context, i'll do:
const [searchParams, setSearchParams] = useSearchParams();
searchParams.get('status');

How could this be improved?
While the current solution works, the experience could possibly be improved.
We could move the responsibility of setting and getting each table filter into own hook.
The hook would expose the current value and a setter function.
The usage would look something like this:
const [status, setStatus] = useStatusFilter('CREATED');	// set get status search param

<StatusFilter
  value={status}
  onChange={(status) => setStatus(status)}
/>

This way, we'll decouple the logic and add a concise way to set / get the table filters in other contexts as well.
Also, this will help with testing since we are extracting responsibilities into smaller pieces.
Is this a feature you would work on yourself?

[x] I plan to open a pull request for this feature

Refers to: https://github.com/aiven/klaw/pull/781#pullrequestreview-1328171167


Broken link

MSAL Python links go to a 404: https://learn.microsoft.com/en-us/python/api/msal/overview-msal

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

ID: b90331e5-cca5-b157-eaa1-6f8f90003b32
Version Independent ID: 4b1b803d-e30d-10b2-90a1-3f0ccd8d7d44
Content: Code samples for Microsoft identity platform authentication and authorization - Microsoft Entra
Content Source: articles/active-directory/develop/sample-v2-code.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

#please-close

@msftvito Thank you for your valuable contribution - we have now updates as required!


addinput host and port in args for demo

Thanks for your contribution. I have merged this PR into the main branch.


Add Wixlar WIX Logo

Token Name: Wixlar
Token Symbol: WIX
Decimals: 2
Contract Address: 0x7ba19b7f7d106a9a1e0985397b94f38eee0b555e
Website: https://wixlar.com
Wixlar is the only Digital Currency offering 12 Services to the public, 5 International Physical Offices https://wixlar.com/offices , Sponsoring Major Blockchain, Charity, Sports and Fashion Events, as well as its own TV Broadcasting Channel 24/7.

it was } and we already removed it.
But still showing old test !!
Would you please help us to figure it out if the issue is still there !


⚠ T:Riza Docs has degraded performance

In 0466e06, T:Riza Docs (https://docs.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 9263 ms

Resolved: T:Riza Docs performance has improved in 0702842.


Set up OWNERS for get.submariner.io repo

We use OWNERS files to manage permissions in all other submariner.io repos. Add that feature and the CI to auto-gen/validate from OWNERS.in to the get.submariner.io repo.

Add that feature and the CI to auto-gen/validate from OWNERS.in to the get.submariner.io repo.

We can't add this part since we don't have Shipyard for the make CODEOWNERS target.


Adding nullability

Cleans up #2706 and #2566 and adds nullability to all of the header files.

Thanks again @franklsf95

You're welcome! Glad I can be of help!


Categorical Wombling

Add functionality for categorical wombling

I've had a look at Odin and friends (1993) and this is my sort of the high level interpretation thereof. I really like how they approach the candidate boundaries thing in here


User & Project page styling

Make buttons & spacing similar
Add search to users
Fixes #240, works towards #102

looks good

how do we want to address #102? I think having it inline without seeing the tech would be confusing

We can add a button?


Tanka should explicitly warn when deleting a Namespace object

A library may have something like this, pretty innocent:
local k = import 'k.libsonnet';
{
  namespace:  k.core.v1.namespace.new('default'),
}

If tanka uses the prune labels, it will happily label the namespace object as part of the environment, even though the object exists. Now, tk prune will pick up that object, just like any other and offer it to kubectl to delete it.
I'd like to propose a BIG FAT warning right before confirming for any namespace deletions, as deleting them might turn out really disastrous.

What about aborting deleting a ns if a namespace contains things we don't own?

Sounds like a good combination, have both a warning (to make sure the action was intended) and abort (because conflict of ownership). The abort might come at a performance penalty, I don't know the implementation details.

Now that we also have tk delete, Tanka should generally not delete namespaces.
I see three ways here:

Never doing it. Users need to clean up namespaces themselves.
Having a flag to allow it, this will also have dangerous in it
Trying to be clever and deleting it if we own all resources, otherwise aborting

I favor option 2 and we should also have the delete message print a warning that we delete a namespace and how many objects are still in there

I don't see why tk delete can't delete namespaces. I can see many valid use cases.
Do you mean warning before confirmation? As in, tk prune or tk delete will show a diff result and at the end we say:
<diff here>

If you continue, this will also delete these namespaces:
 * metrictank
 * default
 * kube-system
Are you sure? [yes/No]

You could go one step further and say 'Type namespace default to delete:'.
An argument could exist --delete-namespace=metrictank which would allow to answer that in automation or something.
Personally I'm not a fan of the 'dangerous' keyword, most commands I know use --force to express that.

Actually thinking about this, if we deleted everything else before namespaces (happens like this anyways), we could then check whether it is empty. If it is, no worries, delete it.
If it is not, abort and let the user know. No need for warnings or more manual approval. wdyt?

Yes, that nails it, I'd say.

Sounds very unix-y: rmdir doesn't continue either if the dir ain't empty.

In our multi-tenant environment, we have an out of band process to create and delete namespaces (to allow setting credentials for the namepace default serviceaccount and other policies.
I would not want tanka to delete the namespace even if empty because it is hard for the tenant to recreate it.

If the namespace is not created using Tanka, it's doesn't consider it owned (no label) and not in Jsonnet, so it'll never delete it.
This is only about namespaces created as part of the environment.
You need to make sure to not actually include the namespace as an object in your Jsonnet though

I'd definitely vote for an option to include/exclude the namespace in the deletion. Then also require --force for the non empty namespace scenario.

I tried to address not deleting namespaces in #477 but I think we have too jump way too many hoops and if not that there are a bunch of caveats that we don't yet see.
How do we feel about just warning before the apply? Then this issue becomes low hanging fruit with little impact on how Tanka works.
Applying to namespace 'default' of cluster 'cluster_name' at 'https://<IP_ADDRESS>' using context 'cluster_name'.
WARNING: This will delete these namespaces and all resources in them:
- <namespace>
- <namespace>
Please type 'yes' to confirm:

Ha, seems like I already propose that structure. ^^ :facepalm:


Better/safer printout

Sometimes I accidentally type print(t) in a script and then have to kill my terminal tab as millions of rows flood into stdout.
We get a nice compact representation with the "default repr" in the REPL
julia> p
 Row │ nMuon   Muon_pt
     │ UInt32  SubArray{Float3
─────┼─────────────────────────
 1   │ 0       []
 2   │ 2       [19.9, 15.3]
 3   │ 0       []
 4   │ 0       []
 5   │ 0       []
 6   │ 0       []
 7   │ 2       [22.2, 4.43]
 8   │ 0       []
 9   │ 0       []
 10  │ 0       []
  ⋮  │   ⋮            ⋮
                90 rows omitted

which you can reproduce with display(p) or println(repr(p, context=:limit=>true)), the former of which is unintuitive for a newcomer and the latter unintuitive unless you spend 10 mins tracing through show/display/repr in Base.
I think pandas has a sane approach here:
>>> import pandas as pd
>>> df = pd.DataFrame(range(1000))
>>> df
       0
0      0
1      1
2      2
3      3
4      4
..   ...
995  995
996  996
997  997
998  998
999  999

[1000 rows x 1 columns]
>>> print(df)
       0
0      0
1      1
2      2
3      3
4      4
..   ...
995  995
996  996
997  997
998  998
999  999

[1000 rows x 1 columns]

so, I propose that we match this behavior (always give compact output).

OK, I have mixed feelings about it 😅 I was always a bit annoyed that pandas skips rows when I do print because I usually would assume that print prints everything (in the old-sense of printing something on a physical printer, where you expect the whole thing and not skipping the middle part).
On the other hand, numpy does the same, so I understand the consistency issue. Maybe they started it and other devs just adopted it? Also, we don't have much fine-graded options for the "printer" like "from page 4-10", so my argument above is lacking a good foundation 😆

assume that print prints everything

I agree.

for the "printer" like "from page 4-10"

I say we add this and other issues and one more for https://github.com/ronisbr/TerminalPager.jl as hacktoberfest 2021 ;)

@tamasgal at the least we should always have some way of printing the full table. As a lifelong Python fan 😉, I'm a bit biased since numpy/pandas elide with all the main print methods (in a script and on the REPL) and then make it (only slightly harder) to show the full representation, since it's more common to summarize a table's structure than inspect all its values. Maybe this is even more so the case for julia because of its superior abilities for laziness :).
numpy
a = np.arange(10000).
a/print(a) -- short output
print(a.tolist()) -- full output
pandas
df = pd.DataFrame(np.arange(1000))
df/print(df) -- short output
print(df.to_string()), df.style (notebook) -- full output
julia
t/display(t)/println(repr(p, context=:limit=>true)) -- short output
show(t), println(t), repr(t) -- full output
So I think it would be nice to swap the behavior of the two rows in julia so that we retain an easy way of fully dumping a table. But then that feels like a literal anti-pattern.

@Moelf yeah, a scan(t) (or better word that doesn't give ROOT trauma) that shows a pager like less, and then making print elided by default, would solve this (for me at least)!

We still need to think of a way to print a full table, print(string(tree)) feels not Julia.

Oh, I would've thought print(string(tree)) makes sense (since there a step (string()) that explicitly materializes the full tree).
I can't say I like the DataFrame printout behavior either :(.

so if we were like DataFrames.jl we should use show() and have a compact printout in the REPL and a script alike.

LazyTree
REPL
script

t
short
N/A

show
full
full

println
full
full

display
short
full

DataFrame
REPL
script

df
short
N/A

show
short
short

println
full
full

display
short
full

To summarize, the PR made our printing behavior consistent with DataFrames, so we now can and should be using show/@show in scripts to get compact printouts and println for the full printout.

Thanks! 🙃


Notification Template - filter is not working correctly

Describe the bug

when we add some space in before or after search text it does not filter correctly

https://www.berrycast.com/conversations/b6bb6045-7da8-508c-989c-99fda92b3d84


Stiebel Eltron Integration

HI there,
I have a Stiebel Eltron LWZ170E which looks identical to the Brink system.
My system also has ebus, and I have connected an ebus <-> wifi dongle. I wonder if this integration could be updated or modified to work with the Stiebel Eltron system. Stiebel Eltron does not have the api / website login, so I wondered if it would be possible to connect using just the ip address and port of the ebus signal?

Hey,
Sorry for such a late response. But this integration currently are written fully by the rest api from the app of the brink-home, so if this device is controlled differently then it will not work through this integration


function GROUP_CONCAT() doesn't work

alasql('SELECT Type,GROUP_CONCAT(Name) AS Names FROM ? GROUP BY Type',[[{Type:'PT',Name:'Steve'},{Type:'PT',Name:'Dan'}]]);

returns

Uncaught SyntaxError: Unexpected token ;

should be

[{Name: "Steve,Dan", Type: "PT"}]

or, even better, unless "separator" was defined

[{Name: ["Steve","Dan"], Type: "PT"}]

Thank you!
Could you try ARRAY() aggregator:
    var res = alasql('SELECT Type,ARRAY(Name) AS Names FROM ? GROUP BY Type',[[{Type:'PT',Name:'Steve'},{Type:'PT',Name:'Dan'}]]);

it gives [{"Type":"PT","Names":["Steve","Dan"]}]
Or you can implement GROUP_CONCAT user-defined aggragator function:
    alasql.aggr.GROUP_CONCAT = function(v,s){
        if(typeof s == "undefined") return v; else return s+','+v;
    };

Here v - is a value, and s - is an accumulator.
It gives [{"Type":"PT","Names":"Steve,Dan"}]
This is an example in jsFiddle

Now GROUP_CONCAT() is in Alasql.

Here is an update to the GROUP_CONCAT function. I was getting "undefined" results through out  the string:
    alasql.aggr.GROUP_CONCAT = function(v,s){         if(typeof v === "undefined" && typeof s === 'undefined') return '';         else if(typeof v === "undefined" && typeof s !== 'undefined') return s;         else if(typeof v !== "undefined" && typeof s === 'undefined') return v;         else return s+','+v;     };


Feature request: Negative value for Grid export limit

Hi, will it be possible to add the capability to make the export limit a negative value.
On the new firmware for my GW6000ES20 inverter there is a constant 100W export from batteries when there is no PV Power and then a constant 100W import from the grid when there is PV Power. I have lodged the call with Goodwe and they have acknowledged as a bug but have not given any indication to when it will be fixed. The work around they have provided is to change the export limit to -100 through the SolarGo application. As it stand now I have to change the limit in the morning to 0 when there is PV power and to -100 if there is no PV power. I would like to automate this but the integration does not allow negative values.
I have changed the minimum value for export limit number in the number.py to -100 but this alone does not seems to work.

Thank you for the assistance.

Does anyone know if there was ever a version of the firmware that didn't do this?

On the new firmware for my GW6000ES20 inverter there is a constant 100W export from batteries when there is no PV Power and then a constant 100W import from the grid when there is PV Power.

On the same model I get 100W export to grid when discharging batteries or when producing PV and 125W import to batteries if my DoD does not match up with my battery SoC. Unless I change the export limit to -100W in the apps

I know my problems with the batteries exporting to the grid started with version 07.7202.  However, going through my history, I suspect that it was still importing +- 100W constantly from the grid during battery discharge. Sorry I do not remember what version I had before 07.7202.
Testing with 08.8808 now and early results seems like it works as one would expect if you set the export limit to -100W.
Goodwe support is just not what it used to be as I am not getting any response from them on this issue.

The new DSP firmware seem to be working for me too. Down to less than 0.1kWh exported per day with the export limit set to -100W in the app. The integration shows the the export limit selector at 10000 when hovering over on a Windows browser and 65,436W on mobile browser.


⚠ HDBits has degraded performance

In 96adea0, HDBits ($HDB) experienced degraded performance:

HTTP code: 200
Response time: 4401 ms

Resolved: HDBits performance has improved in dbd5718 after 28 minutes.


Remove version: NewBreedSoftware.TuxPaint version 0.9.33

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

URL: https://sourceforge.net/projects/tuxpaint/files/tuxpaint/0.9.33/tuxpaint-0.9.33-windows-x86_64-installer.exe/download
Status Code: 200
(Automated message - build 897)

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


need to make sure our contributors list is up to date

https://mondo.monarchinitiative.org/pages/contributors/

add Sanjeeta
add Deanne Taylor
Add Daniel Olson (Vineyardintern)
Add Emily Hartley (ehartley)
go through GitHub and try to make sure everyone is listed on the website as a contributor

website editing instructions are here:
https://mondo.readthedocs.io/en/latest/editors-guide/mondo-website-editing/

I am working on this

this is done


Add method to listener interface, which will notify about variable change during test execution

It will be nice for debugging propose, if Robot Framework(RF) Listener API, will be extend to get notification about variable(s) change during test execution. The solution could base on getting at the very begin of test, before any suite will start - all available variables and after test will start just get update about: new variable available, change value of variable and remove variable from test execution.
Currently to do such pretty nice feature, we need to send on every start and end function from RF Listener API all available variables and filter changes on our listening RF test debug server. It could be very helpful if this update, will contains any information about scope of variable (GLOBAL, TEST_SUITE, TEST_CASE) also.

Sounds reasonable. Have you thought how the API should look in more detail? Are you interested in implementing this enhancement yourself?
Notice that if your listener is implemented in Python, you can pretty easily access current variables using BuiltIn library as the API. You should be able to get started with just
from robot.libraries.BuiltIn import BuiltIn
variables = BuiltIn().get_variables()

and there are also other variable related keywords/methods that may be useful.

I will come back soon with some proposal, with our implementation of this feature we go step further by  implementing dynamic variable change during test execution by user. The only problem which we have been met is that from
variables = BuiltIn().get_variables()

we can not get scope of currently changed variable, so we are blind in see if we should use
BuiltIn().set_global_variable(name, *values)
BuiltIn().set_suite_variable(name, *values)
BuiltIn().set_test_variable(name, *values)

. Is any possibility to get such knowledge? I think use set_global_variable can introduce only mess, because according to our experience user can get wrong feeling that variable with such value exists also in other parts of test. Our current conclusion is that only possible solution is that we will have to create own test execution context to register any variables, which we will get and set it scope by own.

Unfortunately scope information isn't easily available. To be honest, the whole scope implementation is pretty bad. Our plan is to rewrite it in RF 2.9. See variable related issues in milestone 2.9 for more details.

Any activity with this issue?

Hello,
Currently as I see is many ongoing changes releated to how Robot Framework is internally handle variables. Therefore I have been postponed a little bit providing any kind of solution. If all activities releated to variables in Robot Framework 2.9 is finished I can check and put solution here.

Have you had a change to look at this?

Ooops, pressed wrong button. Reopening.

Unfortunatelly no, but I will provide some idea tomorrow.

Sorry I will do the update today for ensure - what do you prefer poll request with some source code or just concept of API?

It would be good to start from the concept.

Ok, so I just think about method like this:

Method
Arguments
Attributes / Explanation

variables_updated
collection_of_attributes
Where collection_of_attributes is collection of attribute dictionaries (list of maps).
Single list with attributes map contains:

time: time of the first change of variable
name: variable name
type: type of variable: SCALAR, LIST, DICTIONARY - in case of SCALAR as list (many values - deprecated from RF 2.7.6) the type should be LIST
value:  map of key-value pair, in case of type:

SCALAR key is none and value
LIST key is index of changed element and after just value
DICTIONARY key from map and value

variable_declaration_source an absolute path to variable declaring source
variable_scope: GLOBAL, TEST_SUITE, TEST_CASE, LOCAL/TEST

I guess the method name should be variable_updated and I'm not sure is all information you want to include available or relevant. Another issue is that the proposal doesn't yet explain how listeners would get the initial list of variables.
I'm afraid implementing this will be pretty complicated because variables can be set in so many ways. I obviously have nothing against you trying, but want to remind that acceptable end result should not be overly complicated to maintain in the future. If you could explain your underlying needs better, we could also think are there easier ways to meet them.

You are right about method name, I made typo - sorry for that.
About information I think the most important and currently used by RED are attributes name and value from my table. In case getting index of changed element in list variable could be hard to do - listener can get even whole collection - without any information what was changed.
The initial list of variables should be send after the first start_suite or better where listener agent is initialized by Robot Framework - in our case execution of Python method:  __init__.
In RF 2.8.7 I made some proof of concept, where I put my source close to, where variables are stored, so every update of variable call listener as logger to notify external application server about changes.
Thanks for you patient and understanding.

Could you clarify the use case a little more? Is there a reason why getting variables from Robot itself wouldn't work?

We want to implement in RED - variable watch debugging feature, which gives ability to stop test execution when variable was changed in RF model. Currently we are getting update of variables only on start_suite, start_test, start_keyword it is required to every start_* send and check currrent state of variables.

Is there a strong demand on such functionality? Do normal debuggers support something like that? I'd be more interested to be able to inspect current variables at a certain breakpoint.

This feature is common used by developers ("Toggle Watchpoint" - Field Access), when basically you are only interesting on see possible when variable on which your code demand is changing. Change of variable is not take away possibility to see all variables, which are available.
The example is when you have in test variable X and you are want to stop executing test case, when it will have value 5 or anytime variable is changing - to do this you need to see what current value of variable and meet this requirements you need to get it updated when it was changed.

So this is something normal debuggers support, right? I don't have much experience with them but I assume it is useful in some cases. Is adding this functionality to RED a concrete requirement from existing users or just something you'd like to implement to have same features as other debuggers?

To be honest I do not imaginate debugger without this nice feature ;) For users the minimum is to get all variables, but get it each time start_* methods is invoked create some overhead, if you think that this new method will create some trouble for RF, then we can just leave this as exists. Currently we are using Eclipse difference check functionality included in platform to show user which variable was changed by each test step.
About RED - it is currently is in development phase in NSN, You can ask Jussi Malinen since we met one or two weeks ago when he was in Wroclaw.

You should notice that RF isn't same as normal programming language and thus debugger needs are not same either. Personally I have never needed such a functionality and I don't remember any RF user requesting anything similar either. Debuggers are discussed quite often, but I guess just being able to set break points would cover most needs. I don't think any Robot editor currently has any real debugger support, and I'm surprised you see that so high priority in RED. I would try to get the first version to real users ASAP and see what they like and don't like about it. Otherwise there's a big risk that you are spending time with features nobody or very few will use.
Notice that the above doesn't mean we couldn't add support for notification about variables into RF. I would be happy to merge a pull request as long as it isn't too complicated and is adequately tested and documented.

Ok Pekka, I undestand that RF isn't real programming language and for me is quite ok if  BuiltIn().get_variables() is fully allowed and You accept such solution as is currently implemented - without this line debugger feature will be just partly made - you can set break point but you couldn't see what kind of values you have in your test case - and I think you understand that.
About debugger itself as I know some person from NSN China using it currently with RED, so it will be not just another feature without any users.

BuiltIn.get_variables() is OK to use in libraries and listeners. What do you mean with "such solution as is currently implemented"? Great to hear RED has already has users. Didn't know about that. And I agree debuggers in general can be useful also with RF.

I wanted to say that BuiltIn.get_variables() was added to our own listener to get variables from RF.
About users I will say that they use part of RED, but I hope soon we will deliver more valuable parts.

Is this still relevant? I'm afraid the implementation would be terribly complicated and likely not worth the benefits.

Hello @pekkaklarck,
The first sorry for late answer.
I discussed with RED team this issue and seems that it will be nice to have it to finally finish some part of debugger (currently we do not have watch variables feature). As You probably seen users are interested in Debug part of RED, so if will be possible to implement breakpoints when variable is changed - for RF users no extra work will be required to get as close as possible to problem. I reviewed previous spec and what is really need to get as much knowledge as is required to create valuable part on RF and I think it should be like below:

Method
Arguments
Attributes / Explanation

variable_updated
collection_of_attributes
Where collection_of_attributes is collection of attribute dictionaries (list of maps).
Single list with attributes map contains:

time: time of the first change of variable
name: variable name
value:  map of key-value pair, in case of type:

SCALAR key is none and value
LIST key is index of changed element and after just value
DICTIONARY key from map and value

About code snippet I will try to provide is as kind of console print out if is acceptable for You.

If you think this is important, please try implementing it and provide a pull request. I'm afraid implementation is very complicated and that the resulting code may be hard to maintain in the future. I cannot thus promise that a pull request would be approved even if this could be made to work.

@pekkaklarck I have time to check it a little bit more and I think You are right. In case of collections fully work implementation will required to have some kind of proxy object over normal object to get each update on them. So I think current BuiltIn.get_variables() is enough mostly because Eclipse debugger API contains possibilities to find what was changed.


Run a Registry as a pull-through cache for microsoft registry mcr.microsoft.com

Hi Team:
We are trying to set up registry as pull-through cache for our users for microsoft based images from mcr.microsoft.com
There are some issues (4 years older) that suggests that this isnt possible, https://github.com/microsoft/containerregistry/issues/9
Do we have any latest changes there?

Closing. This is the wrong repo to ask this question. Please ask in https://github.com/distribution/distribution


Cache most frequently executed functions in reporting

Cache summarize and charge functions in order to speed up the processing a bit.
According to a profiler ~60% of the CPU time is spent in vm/vm2 C++ ticks for organizations with a lot of consumers and plans.

Coverage increased (+0.09%) to 90.728% when pulling 44a399549374672e50148c8bfc005b3072e5ac8d on SAP:cache-in-reporting into 680fc9ce2b64247a7f99533939c0990938102906 on cloudfoundry-incubator:master.

Coverage increased (+0.09%) to 90.728% when pulling 44a399549374672e50148c8bfc005b3072e5ac8d on SAP:cache-in-reporting into 680fc9ce2b64247a7f99533939c0990938102906 on cloudfoundry-incubator:master.

Coverage increased (+0.09%) to 90.728% when pulling 44a399549374672e50148c8bfc005b3072e5ac8d on SAP:cache-in-reporting into 680fc9ce2b64247a7f99533939c0990938102906 on cloudfoundry-incubator:master.

Coverage increased (+0.09%) to 90.728% when pulling 44a399549374672e50148c8bfc005b3072e5ac8d on SAP:cache-in-reporting into 680fc9ce2b64247a7f99533939c0990938102906 on cloudfoundry-incubator:master.


[IncrementalParseTransition] Simplify implementation of IncrementalParseTransition

Now that getting the position offset from the node is 'cost-free' there's no need to keep track of the offset separately.

@swift-ci Please test


Reproducible builds

@Carreau :
[takluyver@tk2e15 flit]$ flit wheel
[takluyver@tk2e15 flit]$ md5sum dist/flit-0.7.2-py3-none-any.whl
104fa2df7ba06b4c1369299761dc9866  dist/flit-0.7.2-py3-none-any.whl
[takluyver@tk2e15 flit]$ flit wheel
[takluyver@tk2e15 flit]$ md5sum dist/flit-0.7.2-py3-none-any.whl
104fa2df7ba06b4c1369299761dc9866  dist/flit-0.7.2-py3-none-any.whl

There's two levels to this. If you run flit wheel twice on the same source tree locally, you should get the same results. But timestamps in the zip file reflect the time when you last pulled changes from git (git doesn't store mtimes), so someone else can't immediately reproduce the build from another clone. To make a properly reproducible build, set SOURCE_DATE_EPOCH. Try this (on this branch) and see if you get the same result:
[takluyver@tk2e15 flit]$ export SOURCE_DATE_EPOCH=1451922369
[takluyver@tk2e15 flit]$ flit wheel
Zip timestamps will be from SOURCE_DATE_EPOCH: 2016-01-04 15:46:09  I-flit.wheel
[takluyver@tk2e15 flit]$ md5sum dist/flit-0.7.2-py3-none-any.whl
8a49f357088a0596810566989a428b82  dist/flit-0.7.2-py3-none-any.whl

For some reason we're creating an invalid zip file under Python 3.5, though it's fine under 3.4. I'm looking into what's changed in the zipfile module.

Sweet ! (just drove 6h almost non stop, but will look at that later)

OK, got the zipfile stuff working with Python 3.5. Of course that means that the md5sum of a build from this branch has changed:
[takluyver@tk2e15 flit]$ echo $SOURCE_DATE_EPOCH
1451922369
[takluyver@tk2e15 flit]$ flit wheel
Zip timestamps will be from SOURCE_DATE_EPOCH: 2016-01-04 15:46:09  I-flit.wheel
[takluyver@tk2e15 flit]$ md5sum dist/flit-0.7.2-py3-none-any.whl
472b266d8efa0724da385797fe0228f7  dist/flit-0.7.2-py3-none-any.whl

Awesome !
What do you think (independently) of having a ZipFile that can built in-memory zips?

What do you think (independently) of having a ZipFile that can built in-memory zips?

Precision: not the final zip file in memory, but something that make what we are doing here easier. Basicaly having ZipFile.write take a "Fake file" with os.stats info and so on... instead of a file name ?

I'm working on a patch for zipfile to add more flexibility along those
lines. Currently, it's a new method that takes a file like object and a
ZipInfo object.

Will be happy to review it. (and looking forward CPython being on GitHub)
On Tue, Jan 5, 2016 at 2:55 PM, Thomas Kluyver<EMAIL_ADDRESS>wrote:

I'm working on a patch for zipfile to add more flexibility along those
lines. Currently, it's a new method that takes a file like object and a
ZipInfo object.
—
Reply to this email directly or view it on GitHub
https://github.com/takluyver/flit/pull/64#issuecomment-169007760.

Python issue for making zipfile more flexible: http://bugs.python.org/issue26039
I've included a patch, but it's more a starting point to work out the API than a definite proposal.

Ping so you don't forget to have a look at this, @Carreau :wink:
I'm sure it's a good way to hold sleep off as you adjust time zones.

I was able to produce bit-for-bit identical wheels on different machines using this branch and setting $SOURCE_DATE_EPOCH. However, as it stores file permissions, it is sensitive to the umask on the machine where you checked out the repository - this initially caused me some trouble, because Debian and Fedora have different default umasks. In the future, I may look into normalising permission bits, but I think it's good enough for now.
@Carreau I'll merge this soon unless you want to look at it any more.

Go ahead and merge.

Good luck. You should approach it as a data science problem - use machine learning to pick where you're going to live. Live in many places for a few days each and rate them to train the model.


Enhance some attributes in the text SR writer

This pull request intends to merge some changes made during the IHE Connectathon IAIP testing.

Update the series selection operator to support matching DICOM instance level metadata
Updated the liver tumor segmentation example to include simple filtering rules
Updated the text SR writer to add time zone offset from UTC, while keep content date time local
Updated the text SR writer to use content sequence for sections of text
Updated the text SR writer storage SOP class to that of basic text SR

Everything looks good to me.

Thanks for adding Media Storage SOP Class UID, that was really helpful @MMelQin

The Storage SOP Class UID attributed was changed from Comprehensive 3D to the more representative Basic Text SR in the PR.
Also, I need to reopen this to merge the PR.


Debugging C++ on macOS is stuck on loading variables

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.77.3
OS Version: macOS 13.0.1 (22A400)

Steps to Reproduce:

Use the following launch.json and tasks.json and Run Start Debugging.

Notes:

Xcode debugging works fine.
Same issue on stackoverflow: https://stackoverflow.com/questions/69443991/visual-studio-code-stucks-in-the-beginning-when-debug-c-code-on-mac

launch.json:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(lldb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/debug/bin/opencv_test_dnn",
            "args": [
                "--gtest_filter=Test_ONNX_layers.FAIR_SAM/0",
            ],
            "stopAtEntry": false,
            "cwd": "${fileDirname}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "lldb",
            "preLaunchTask": "build opencv",
        }

    ]
}

tasks.json
{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "shell",
			"label": "build opencv",
			"command": "cmake",
			"args": [
				"--build",
				"build/debug",
				"--target",
				"opencv_test_dnn",
				"-j4"
			],
			"group": "build",
			"problemMatcher": [],
			"detail": "CMake template build task"
		}
	]
}

/extC++

It looks like this is caused by the C++ extension. Please file the issue to the C++ extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


x/sys/unix: file type information from dirents inaccessible

golang.org/x/sys/unix.ReadDirent reads a Dirent that includes the filename and the file type. golang.org/x/sys/unix.ParseDirent parses out the filename.
Linux and OSX include the file type in the Dirent. Go should make this information accessible. This info would let programs skip stat'ing files of the wrong type.
It would not be feasible to change ParseDirent to do so because it would require a type signature change.
If we can agree on a plan, I can (try to) make the code change.
Here's my proposal, but I've never made a change to Go so it may be off-base.
The package unix could offer a func like "ParseDirentFully" that returned a struct or interface that offered all dirent members available. ParseDirent could call ParseDirentFully to return just the name. (The naming could be better, e.g. ParseDirent and ParseNameFromDirent, but that would break existing code) The code in syscall_*.go already casts to the dirent type from the underlying FS, so it could access another member.
(I am using go 1.5.1 on darwin/amd64. I have inspected code on tip and believe this issue still applies)

Note that ParseDirent is only part of answer to parsing dirents,
you also need to use type Dirent.
It's only used to handle the variable length field Name in type
Dirent, so to parse all Dirents, you can do this:
// assume b is the byte slice containing dirents
names := make([]string, 0, 1)
dirent := (*Dirent)unsafe.Pointer(&b[0])
l, _, names := unix.ParseDirent(b, 1, names)
b = b[l:]
// now you have dirent and names[0]
The details are a little more complicated, as you need to remember
to fill in the buffer when necessary, please see (*os.File).readdirnames
for details:
https://golang.org/src/os/dir_unix.go?s=300:362#L8


KYLIN-4817 Refine CubeMigrationCLI for kylin4

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Test Evidence

src kylin instance url: ADMIN:KYLIN@<IP_ADDRESS>:7070
target Kylin instance url: ADMIN:KYLIN@<IP_ADDRESS>:7072
migrate cube: kylin_sales_cube
src project: learn_kylin
target project: test_migration_kylin

cmd

bin/kylin.sh org.apache.kylin.tool.CubeMigrationCLI ADMIN:KYLIN@<IP_ADDRESS>:7070 ADMIN:KYLIN@<IP_ADDRESS>:7072 kylin_sales_cube test_migration_kylin true false true true true

Result: kylin_sales_cube be migrated to project test_migration_kylin of <IP_ADDRESS>:7072, and the related hdfs resource(dict、snapshot、parquet file) be copied to target kylin instance HDFS working dir.
Migrate log

Migrated can be queried

Codecov Report

:exclamation: No coverage uploaded for pull request base (kylin-on-parquet-v2@c7e08d6). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##             kylin-on-parquet-v2    #1496   +/-   ##
======================================================
  Coverage                       ?   24.12%
  Complexity                     ?     4611
======================================================
  Files                          ?     1136
  Lines                          ?    64388
  Branches                       ?     9501
======================================================
  Hits                           ?    15536
  Misses                         ?    47240
  Partials                       ?     1612

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 c7e08d6...e0cfed8. Read the comment docs.


Start-Stop-Automation - PathToSAPControl

Starting and/or stopping of a SAP System does not work if PathToSAPControl variable contains space.
This is typically the one within saphostagent installation (C:\Program Files\SAP\hostctrl...), so that one can't be used (as of now)

Do you try to use the path where you have the usr folder?
like e:/usr/xxxxxx

Do you try to use the path where you have the usr folder?
like e:/usr/xxxxxx

Yes, that works fine.
However, I was trying to use the one from saphostagent installation to have the same tag value on all of the servers

hi folks,
is there any special reason to use Host Agent path for SAP control path?

hi folks,
is there any special reason to use Host Agent path for SAP control path?

Not really, just for convenience

closing due to no activity


Show ability activation when it causes an immunity

Originally this was regarding the following attack:

The opposing Lapras used Confuse Ray!
Lickitung doesn't become confused!
But it failed!

The "But it failed" should not appear, since we already have the confusion immunity message. Additionally while looking into this I noticed that not only do most Ability immunities also simply cause the attack to fail, they don't even activate. I have therefore tried to add immunity activations for all of them. (This is untested as yet though.)

I should probably revert the Overcoat change as that's a more complex one (like Levitate).

I've limited this to the easy ones for now: Immunity, Insomnia, Limber, Own Tempo (including skill swapping Own Tempo onto a confused Pokémon), Vital Spirit and Water Veil.
Leaf Guard and Oblivious looks as if they should activate in more cases, but I'll double-check first.

TryHit can't be used for this because the Abilities don't activate if the attack misses or fails for some other reason. Here's the general flow of checks the game does in this area:

Check for Dry Skin / Flash Fire / Soundproof / Telepathy / Wonder Guard / etc
Check for accuracy
Check for substitute
Check for status / powder immunity due to typing
Check for status / powder immunity due to Ability (Limber / Water Veil / Overcoat / Flower Veil / etc)

This order is somewhat different prior to Gen 5 since back then stuff like Hydro Pump could miss against Water Absorb, but that's a separate issue.

Would that make it wrong for Oblivious to activate against Captivate when the user has a Substitute? (And why doesn't it activate against Attract? Also, I'm glad I had a backup plan.)

Oblivious can use TryHit because it's checked at the same level as Dry Skin in the list I posted above. Interestingly though, Attract and Captivate check for failure due to gender before that, so Oblivious doesn't even activate if it wouldn't have worked normally.
Attract and Captivate failure is checked at such a high level that even Protect and Magic Bounce happen after them. I edited my other comment to add the top of the list. I imagine Attract/Captivate would land above Wide Guard/Quick Guard, but I can't really test that with an AI opponent.

@urkerab You may have forgotten to check for Cute Charm.

Fair enough, but one last question, and that is where does "already has status" come on the list of checks?

Added that step to the list, @urkerab.

onSetStatus seems to work well: Leaf Guard already uses it, although without an Ability activation; perhaps both its onSetStatus and onTryHit should add -immune and return null?

I'd previously asked someone to test the effects of Glare on a Limber Pokémon, and they said that when they tried on the cart they found that Limber does activate behind a Substitute, but not if the Pokémon is already statused.

That looks like a great solution! :+1: Leaf Guard can probably follow suit, but I'll have to check its Rest and Yawn interaction again. The only issue left then would be making Synchronize play nicely with these. Currently it's implemented out of order so these Abilities activate first. Perhaps something like this would do?
onAfterSetStatus: function (status, target, source, effect) {
	if (!source || source === target) return;
	if (effect && effect.id === 'toxicspikes') return;
	if (status.id === 'slp' || status.id === 'frz') return;
	this.add('-activate', this.effectData.target, 'ability: Synchronize');
	source.trySetStatus(status, target);
},

A check for Synchronize would need to be added to each immunity Ability too so they activate when it attempts to status them. Something I haven't considered is where to defer the immunity message for Synchronize failure on natural immunities.
Re: Glare + Limber, that's exactly the result I would expect from Infiltrator Seviper.

Would if (source.runImmunity(status, true)) source.trySetStatus(status, target); work?

runStatusImmunity, but yeah that seems to work perfectly along with a move.id === 'synchronize' check in each status immunity Ability.

Added Leaf Guard activations and Synchronize, assuming that the Yawn interaction doesn't need to be changed.

Nicely done! Leaf Guard looks good too. :+1:
Last thing is Synchronize currently sends no message when attempting to status a Pokemon with an existing status. Maybe repurposing the code from scripts would work well for it? I can't really see a better solution to that at the moment.
if (source.status) {
	if (source.status === status.id) {
		this.add('-fail', source, source.status);
	} else {
		this.add('-fail', source);
	}
	return;
}

Ah, so Synchronise actually thinks it's a move that sets status? Maybe it would be better if trySetStatus performed the messaging if a directly statusing effect was passed.

Oh, yeah combining that idea with your previous suggestion of simply if (source.runImmunity(status, true)) source.trySetStatus(status, target); would probably be a good solution and may even be useful later on.

Now that I've improved trySetStatus, I can just call it directly from Synchronize; if the target already has the same status it will fail with "Already [status]"; if it has a different status it will display "Failed"; if it has no status but it is immune by typing it will display "Immune", if it has no status and it is not immune by typing but it is immune by ability then the ability will activate.
Enhancing trySetStatus also allowed me to simplify moveHit in data/scripts.js and also in mods/gen2/scripts.js (I didn't want to touch mods/gen1/scripts.js but I don't think it should be affected.)
The changes to mods/gen*/abilities.js is because some of the statusing abilities were passing the move, and I'm not sure that's desired (although right now it's always a contact move so it will never be a status-setting move).

Very nice work; I think you made all the right decisions. Thanks! :+1:

Now, all I have to do is to fix the Abilities that block volatile status...


Various improvements to README.txt

Just a small fixes to the README file:

.js ➡ .ts to prevent dead links
typo
added goTo values to the config table

This is not a functional implementation. No new release is needed.

No idea why the checks fail…

here we go