KDE not showing any window borders in 18.03

Issue description
I just updated to 18.03 and KDE is broken. I can't close or resize windows anymore as window decorations are not displayed
Steps to reproduce
Upgrade to 18.03
Technical details
I can't as I can't open a browser on the machine

Sorry for the terse description but I can't open a web browser on the machine. Or at least. I can't make the window focus..

Can't reproduce. It may be due to the configuration in your home directory. If you move that out (~/.kde, and a number of files in ~/.config), does the issue persist? Are there any other details about your computer?

Runs successfully for me without issue.

When I'm home I'll investigate further :)
On Sat, Apr 14, 2018, 09:17 Bastian Köcher<EMAIL_ADDRESS>wrote:

Yeah, @arianvp https://github.com/arianvp should try that. If for you
everything works, I did not expect anything else ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/38870#issuecomment-381309697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmWo5JwwFNeiHFzfd8WrWjuqYLkaal4ks5toaKmgaJpZM4TSekx
.

Possible dup of #38752

After running 18.03 for a day, this suddenly started happening for me, as well. I rolled back to 17.09 and rebuild 18.03 just to be certain, and it still happens. I'll try the step bkchr mentioned above.

$ nix-info
system: "x86_64-linux", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(root): "nixos-18.03.132083.06c576b0525", channels(b): "unstable-18.09pre135256.6c064e6b1f3", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

This does look like a dupe of #38752, though I'm not sure how that helps me :)

nix-info from the broken 18.03:

system: "x86_64-linux"
host os: Linux 4.14.35, NixOS, 18.03.132083.06c576b0525 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0
channels(root): "nixos-18.03.132083.06c576b0525"
channels(b): "unstable-18.09pre135256.6c064e6b1f3"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Maybe it's time to switch away from KDE.

@chreekat did it fix your installation to delete the config folder?

I will try that and let you know.
On Apr 22, 2018 15:36, "Bastian Köcher"<EMAIL_ADDRESS>wrote:
@chreekat https://github.com/chreekat did it fix your installation to
delete the config folder?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/38870#issuecomment-383406631, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAg3qg7P1kXZrDcEhwcIsWxj8XNA6Myzks5trNu4gaJpZM4TSekx
.

@chreekat which GPU are you using?
I found a similar bug report for gnome: https://bugzilla.redhat.com/show_bug.cgi?id=1462507
Do you also use wayland?

I am using X11. I have some integrated graphics, probably Intel. NixOS doesn't seem to have lspci, and I'm not sure what else to use to look up the info. lshw doesn't give anything useful.
Ah, the GNOME 'about' pages says, "Intel® Haswell Mobile".

NixOS doesn't seem to have lspci

nix-shell -p pciutils --run lspci or nix-env -f '<nixpkgs>' -iA pciutils then try again.

Thanks,
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)

I said "seems to not have" because I got no prompt to install a particular package, as I sometimes do with missing utilities, and I am not sure how to map particular utilities to particular packages. Except for grepping the sources, I suppose, which I could have done...

I'm now getting the issue, with the same error as chreekat (kwin_x11[1364]: segfault at 4 ip 00007f414ff1ca98 sp 00007ffd5e041820 error 4 in libxkbcommon.so.0.0.0[7f414ff00000+3e000]). Similarly affecting old generations. Have cleared out ~/.config, ~/.kde /var, /tmp
Have attempted to clear out most qt-using packages from user-env. Currently the only version from 5.10.1 is the phonon backend using 5.6
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Device 9d1b (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev ff)
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)```

My error was likely related to qt versions. Fixed by removing version of spectacle  which was more recent than expected for the release I was on (spectacle was version 18.04 from unstable, expected version was 17.12 or earlier).

Got same problem when I installed qt5 app (telegram client) from nixpkgs-unstable. It got fixed once I removed it from user profile.

Considering the lack of recent comments, this issue was probably fixed a while ago.


[INLONG-706] Add 0.9.0 version release modification to CHANGES.md

Codecov Report

Merging #549 (b163491) into master (3c18efd) will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #549      +/-   ##
===========================================
+ Coverage      7.67%   7.72%   +0.04%
- Complexity      561     563       +2
===========================================
  Files           355     355
  Lines         31081   31081
  Branches       4972    4972
===========================================
+ Hits           2387    2400      +13
+ Misses        28212   28191      -21
- Partials        482     490       +8

Impacted Files
Coverage Δ

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
43.98% <0.00%> (+1.46%)
:arrow_up:

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (+2.22%)
:arrow_up:

...nlong/tubemq/corebase/policies/FlowCtrlResult.java
60.00% <0.00%> (+60.00%)
:arrow_up:

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 3c18efd...b163491. Read the comment docs.


[Info] Sokol luajit direct use version

Last weekend I put together a luajit sokol that uses ffi and linked sokol dll's
Currently only tested on Win. But should work on MacOS and Linux (will check this weekend).
This is just an issue if people are interested.
https://github.com/dlannan/sokol-luajit
Want to thank @floooh  for making Sokol. Its been a very interesting framework to use and quite a bit more powerful than I expected :)
The fork for luajit is slightly tampered with, but I hope to get the luajit header generation working nicely and some auto patching as well - cimgui being a bit of a pain with luajit (not being really C).
Again thanks for Sokol, I also hope to contrib if possible as I progress with this.

Woah, very cool!
Are you planning to integrate this with the automatic binding generation scripts in the sokol repo (https://github.com/floooh/sokol/tree/master/bindgen)?
...then a separate CI job in the sokol-luajit repo could rebuild and commit the precompiled DLLs.
The only thing that would need to be updated manually is then probably fixing the examples from time to time in case of breaking changes.
Also the shader compiler integration is impressive :D Would it make sense to add an official Lua code generator to sokol-shdc? I'm very surprised how little code this is:
https://github.com/dlannan/sokol-luajit/blob/10c6ecb417448d3abf2a564b25e875d969a0013c/tools/shc_compile.lua#L44-L126
...significantly less than a sokol-shdc code generator...
Btw... bug (the win32 path)?
https://github.com/dlannan/sokol-luajit/blob/10c6ecb417448d3abf2a564b25e875d969a0013c/tools/shc_compile.lua#L39
Can Lua detect x86 vs ARM Macs? In that case you could add both the x86 and ARM macOS exes.
Anyway, great stuff! :)
Cheers :)

Hi, thanks, and really you did all the hard work :) (Im just leeching :) ).
I looked at trying to setup some binding, but there are some complilcations I want to figure out first before going that route - ie, what does each target need - currently android and wasm are not happy for various reasons. Wasm is complicated because building luajit using something like emscriptem wont work because of its dynasm system - it might be possible to make a luajit dynasm wasm target, which would be awesome, but theres a couple of other ways around I wanna try first.
The android problem is issues with shared libs, so Im looking at a more integrated approach - luajit + sokol + some libs to provide a 'good enough' runtime, but that needs investigation too.
So yes. Will get to generation one day.. but as you prob know.. sw dev goes slow at the best of times :)
I dunno how stable/friendly the shader compiler is. Its rudimentary ( I really want runtime adjustable data sets, and shaders are one of those). I'll spend more time on it, since Im looking at making a Defold shader import to be included in it (probably as a param setting), because I have a tun of Defold shaders I'd like to try out :)
The pathing. yes... this is just wonderous. And I will definitely be making an agnostic path manager (have built a few before for lua) which will make paths across systems a little more consistent. This is kinda tricky to get right though, so once I have that in a better state can be a bit more confident in its use.
Yes lua can detect diff platforms. However, this is only with luajits ffiu module. You can use the properties ffi.os and  ffi.arch. Extremely useful for handling the platform issues. But should go in a single lua defines or something to handle it more appropriately.
Thanks again, really enjoying playing around with sokol. Hooked it up to luasocket and copas and made a little http server running in the sokol game loop. Really nice api you built so I greatly appreciate what you (and Im sure others) have done.

@floooh - I hope you dont mind, I added a Discord server for sokol-luajit. I couldnt see one for sokol. So I hope its ok?
https://discord.gg/KMDeFebk

Sure it's fine! :)


Update logic-apps-enterprise-integration-overview.md

@MSFTMan Hello, another article with the same link flagged.

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

@msebolt Hi Matthew, thanks for your feedback! Did you mean to include a different article? This issue looks the same as this GitHub issue:
https://github.com/MicrosoftDocs/azure-docs/pull/13339

@ecfan  Yes, sorry about that.  I think another article references the same content.


"Eth-Consensus-Version" header absent in eth/v2/debug/beacon/states/{state_id} response

Describe the bug
curl -H "Accept: application/octet-stream;q=1,application/json;q=0.9" -Ssv "http://consensus:5052/eth/v2/debug/beacon/states/finalized" > /dev/null
*   Trying <IP_ADDRESS>:5052...
* Connected to consensus (<IP_ADDRESS>) port 5052
> GET /eth/v2/debug/beacon/states/finalized HTTP/1.1
> Host: consensus:5052
> User-Agent: curl/8.4.0
> Accept: application/octet-stream;q=1,application/json;q=0.9
>
< HTTP/1.1 200 OK
< vary: Origin
< access-control-allow-origin: *
< content-type: application/octet-stream
< content-length: 213503710
< Date: Thu, 23 Nov 2023 04:46:56 GMT
< Connection: keep-alive
< Keep-Alive: timeout=72
<
{ [14263 bytes data]
* Connection #0 to host consensus left intact

Expected behavior
Eth-Consensus-Version header should be set, as required by https://ethereum.github.io/beacon-APIs/#/Debug/getStateV2

Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.12.0

Did you face issues with that after updating the go http client? Same issue happens with the latest checkpointz version which also expects the Eth-Consensus-Version header to be set (https://github.com/ChainSafe/lodestar/issues/6124).
We are not following the spec here, this will be addressed by API rework done in https://github.com/ChainSafe/lodestar/pull/6080

Well, I was hitting this error, then I upgraded the attestantio http client so I could toggle the EnforceJson switch which sets Accept to exclude ssz, and then I hit the Invalid string length one.
I switched my holesky test environment to nimbus for now. Only 3300 validators were down while i migrated :laughing:


Create package failed

Describe the bug
Create package failed when dependent package version is in format 'X.X.X.NEXT'
To Reproduce
Set dependent package version in format 'X.X.X.NEXT'
Expected behavior
Package created
Screenshots

-----------------------------------------
Package Creation Failed for email-spam-filtering
sfpowerscripts--log
Package Directory  :  "packages/email-spam-filtering"
Fetching Package Type Info from DevHub
-------------------------
Package  :  "email-spam-filtering"
IsOrgDependent  :  "No"
Package Id  :  "0Ho4a00000000BnCAI"
-------------------------
Resolving project dependencies
Command failed: sfdx sfpowerkit:package:dependencies:list -p packages/email-spam-filtering -v devhub -w --usedependencyvalidatedpackages
ERROR running sfpowerkit:package:dependencies:list:
PatchVersion=17 and BuildNumber=NEXT ORDER BY BuildNumber DESC
                               ^
ERROR at Row:1:Column:254
Bind variables only allowed in Apex code

Platform Details (please complete the following information):

OS:
Version [e.g. CLI Version  eg: 1.6.6]
Salesforce Version:
CI Platform:

Additional context
Add any other context about the problem here.

@ashokkumar14   We will not be allowing for package creation to go ahead. Rather we would try to validate the schema to disallow .NEXT packages in dependencies as its not allowed by sfdx


ENG-11206: Replace POST by PUT in access rule creation

Description of the change
Due to a backend inconsistency that leaves an empty access rule set behind, the following error could happen:

User creates access rules through Terraform;
User removes same access rules using the UI;
User try to re-create the very same access rules using Terraform and faces a 409 error.
The error is due to the empty access rule set that is left behind by our API. This is going to be fixed and the set will be completely removed, but in order to avoid customers from having this error and not being able to recover, we opted to switch the POST to a PUT in the access rules creation.
We could use the POST back after all customers are migrated to a release that contains the fix informed in the associated Jira ticket.

Type of change

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklists
Development

[ ] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[x] All tests related to the changed code pass in development

Code review

[ ] This pull request has a descriptive title and information useful to a reviewer.
This obviously leads to mismatch between the CP state and the TF state for the resource. In these cases, how does the TF user reconcile the state? I'm asking the more general question where the resource is edited using the UI (e.g., editing of a specific rule) and not deleted altogether.


Update avs-tutorial-failback.md

Corrected VMware product names.

@rvandenbedem : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@rvandenbedem - the author for this doc has changed. Request you to resolve the conflict before we can merge.
CC: @v-pgaddala as she is the doc owner

@rvandenbedem : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@rvandenbedem : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @Harsha-CS

Hi @Harsha-CS
Could you please sign off the PR as I'm unable to do the same. Thank you.

Hi,
Received confirmation from the PM that the updates are good and the sign off can be done. As the assignee (who can sign off this PR) is no longer part of this service, request you to Sign off.
Thank you!

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.


New linker scripts, cproject config, and gitignore update

Verified updated LPC15x9 linker script.
Others haven't been tested but are trivial changes
Build config for mbed now renamed LPC15xx since it works with all of the board
Project files are in a zip file and now ignored by git for this static library project. Users will need to unzip the project files when they first clone the repo
gitignore is updated to ignore project files and build artifacts from new build config

Closes #1 #2 and #3

@wei2gao fixing the .gitignore conflict dismissed your approval ...


[stable/presto] Prestosql version bump to 337

What this PR does / why we need it:
prestosql is now on version 337 that have interesting improvements. Unfortunately, bumping up the version in he chart is not enough since healthchecks and readiness/livenessprobe will fail due to some changes in the official image behaviors.
This issues are fixed in this PR.
Special notes for your reviewer:
@bivas nothing in particular, hopefully this PR will be good enough to be merged, ty.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

@valeriano-manassero The error from CI is pointing out that the resource type is no longer supported by Kubernetes for Deployments. It's an old and now deprecated API version. It's not part of your change but is affecting your PR. There are two options, either fix it here or it needs to be fixed in another PR and then this one be rebased from that change.

@valeriano-manassero The error from CI is pointing out that the resource type is no longer supported by Kubernetes for Deployments. It's an old and now deprecated API version. It's not part of your change but is affecting your PR. There are two options, either fix it here or it needs to be fixed in another PR and then this one be rebased from that change.

@mattfarina I updated this PR and now CI looks good so I think we should be ok, let me know. Ty!

dain  1 hour ago
/v1/status should be used for liveness checks on coordinator and workers

Maybe you want to update the check endpoints as well. Since the 340 is released, Can you bump the version as well

/v1/status are used already for probes in this PR.
About version bump, I'm not sure it should be included in this PR.
Maybe a specific PR after merging this one (if not will be approved) is a better solution?

Since this will not probably merged and I had other improvements to be made, I created a new chart and added it to ArtifactHub on https://artifacthub.io/packages/helm/valeriano-manassero/presto
Closing this one, ty for feedbacks.


confidence unit: p-value

How come there's not a single unit for confidence ?  Can we please add, for starters,  p-value ?
or is there some other CV to use ?  other than that, definition for parameter unit should not refer
to kinetic constant units because,  eg  'kelvin', (btw. any physicist reading kelvin definition will
cringe :o/  I'd just write kelvin is SI unit of thermodynamic temperature, in order to  to bypass
intricacies and history of its definition) can be used in a context different than kinetic measurements;
sadly, specific reference to kinetic constant makes underlying terms not applicable in other contexts :o/
it might also make sense to make, both, 'parameter unit' and 'confidence unit' children of 'unit'.
Note, that 'confidence unit' should refer to generic measurement confidence,  without referring
to interaction and/or participant identification. In general, every cv term definition should be
made as generic as possible.

Interaction confidence and parameter unit are treated as very different things in the CV. Both are children of the root term directly and operate in different ways. Confidence works as a set of categrized free-text annotations and the parameter units are fixed terms that need to be associated to a numeric field.
My suspicion is that confidence was set up this way because there is a huge range of ways people use to determine confidence, many of which do not use a quantitative output, but a qualitative one, so defining units for something that is going to need an annotation to describe how it was defined anyway was likely viewed as pointless. I pretty much agree with this and would advocate to leave confidence as an annotation. Also, I would heavily advise against using 'p-value' as a unit, which is not. p-values shoudl be reported with summary statistics about the test they refer to, not as a meaningless unit. I think p-values are over-interpreted and over-used in science in general, so I do not think we should contribute to the problem.
Regarding definitions, I have altered the definition of 'kelvin' to the latest SI redefinition, which is the following: "The kelvin (K) is the SI unit of thermodynamic temperature. It is defined by taking the fixed numerical value of the Boltzmann constant k to be 1.380649×10-23 when expressed in the unit J·K-1, which is equal to kg·m2·s-2·K-1, where the kilogram, metre and second are defined in terms of h, c and caesium frequency. It is equivalent to -273.15°C / -459.67°F."


prefixing all options with micm_

To prevent name conflicts with other packages and to make it explicit when using micm from other packages, all micm cmake options are prefixed with MICM_
closes #412

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

Comparison is base (9416a2f) 94.66% compared to head (7afa87f) 94.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #413   +/-   ##
=======================================
  Coverage   94.66%   94.66%
=======================================
  Files          38       38
  Lines        3057     3057
=======================================
  Hits         2894     2894
  Misses        163      163

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


⚠ Bofrost.be has degraded performance

In f17d8f5, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1120 ms

Resolved: Bofrost.be performance has improved in 916b00f after 9 minutes.


[setup] installation with MS Configuration Manager fails

Environment
Windows build number: 10.0.18363.900
PowerToys version: 0.19.0
PowerToy module for which you are reporting the bug (if applicable): installer

Steps to reproduce
using MS Config Manager to install as application model, elevated, allow user interaction. msiexec /i PowerToysSetup-0.19.0-x64.msi /qb!
CfgMgr runs the installer in system context.
Expected behavior
Should just show the msiexec progress bar with no cancel button
Actual behavior
shows msiexec progress, but stops and shows popup "unable to create scheduled task...". when you click ok to dismiss the scheduiled task popup, it says 1 second remaining, but hangs for at least 20 seconds, then exits w/ error 0 - app is listed in Apps control panel, but not in start menu or systray. CfgMgr throws an error because the product code isn't detected in the registry uninstall key after msiexec is done.
troubleshooting
added CREATESCHEDULEDTASK=0 property to command line - this eliminates the popup about scheduled task, but still doesn't fully install (exit 0, not in start or tray, CfgMgr doesn't see the product code in registry)
running manually as an admin user allows the installation to complete normally, even without using the CREATESCHEDULEDTASK property.
But I must ask - why use a scheduled task? Wouldn't it be easier to just put the launcher in the RUN key of the registry? Seems a tool like this is intended to always be running so putting itself in the run key during install would be expected behavior. If you want to give users a choice, then put it in HKCU run instead of HKLM.

Hi @Gibson99
we haven't tried to reproduce the problem yet, but I wanted to give you an answer for:

why use a scheduled task?

Because it's the only why to auto start a program with elevated privileges without showing the UAC prompt.

Because it's the only why to auto start a program with elevated privileges without showing the UAC prompt.

Just like CCleaner does, right? 💡

@enricogior this will still happen i'm assuming with the exe installer since that does some wrapping

@crutkas
yes.

@Gibson99
just checking if you have tried with the recent installer, not that we made specific fixes for this issue, but want to verify. Thanks.

@Gibson99
just checking if you have tried with the recent installer, not that we made specific fixes for this issue, but want to verify. Thanks.

Yes, I extracted the msi, imported it into config mgr, and it installed
just fine using msiexec /I <filename.msi>/q
When I tried /qb! in order to have a visible progress bar, it threw an
error about not being able to create a scheduled task or something like
that (can't remember exactly). Since I don't NEED the progress bar, /q
solved that.
Note that I have not yet tried this on the very latest bugfix release,
that came out a couple days ago, but I will try it on Monday.
On Sun, Jan 3, 2021, 3:19 PM Enrico Giordani<EMAIL_ADDRESS>wrote:

@Gibson99 https://github.com/Gibson99
just checking if you have tried with the recent installer, not that we
made specific fixes for this issue, but want to verify. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4668#issuecomment-753677809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIJDWAP6BWUL7S6FJDZJNDSYDNPFANCNFSM4ON7G3GA
.

Yes, I extracted the msi, imported it into config mgr, and it installed
just fine using msiexec /I <filename.msi>/q
When I tried /qb! in order to have a visible progress bar, it threw an
error about not being able to create a scheduled task or something like
that (can't remember exactly). Since I don't NEED the progress bar, /q
solved that.
Note that I have not yet tried this on the very latest bugfix release,
that came out a couple days ago, but I will try it on Monday.
On Sun, Jan 3, 2021, 3:19 PM Enrico Giordani<EMAIL_ADDRESS>wrote:

@Gibson99 https://github.com/Gibson99
just checking if you have tried with the recent installer, not that we
made specific fixes for this issue, but want to verify. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4668#issuecomment-753677809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIJDWAP6BWUL7S6FJDZJNDSYDNPFANCNFSM4ON7G3GA
.

@Gibson99

I extracted the msi

did you use the  --extract_msi flag for the .exe installer? https://github.com/microsoft/PowerToys/wiki/Installer-arguments-for-exe
Since you got it to work, I'll close the issue, but please reopen it if you run into a problem with the latest build.

@Gibson99

I extracted the msi

did you use the  --extract_msi flag for the .exe installer? https://github.com/microsoft/PowerToys/wiki/Installer-arguments-for-exe
Since you got it to work, I'll close the issue, but please reopen it if you run into a problem with the latest build.

Yes that's where I got the msi since it's not available to download
separately. Thank you for making msi an option again!
On Sun, Jan 3, 2021, 5:13 PM Enrico Giordani<EMAIL_ADDRESS>wrote:

@Gibson99 https://github.com/Gibson99
I extracted the msi
did you use the --extract_msi flag for the .exe installer?
https://github.com/microsoft/PowerToys/wiki/Installer-arguments-for-exe
Since you got it to work, I'll close the issue, but please reopen it if
you run into a problem with the latest build.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4668#issuecomment-753690236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIJDWHQQIFNQ7CWVFF2UPTSYD2Y5ANCNFSM4ON7G3GA
.

Yes that's where I got the msi since it's not available to download
separately. Thank you for making msi an option again!
On Sun, Jan 3, 2021, 5:13 PM Enrico Giordani<EMAIL_ADDRESS>wrote:

@Gibson99 https://github.com/Gibson99
I extracted the msi
did you use the --extract_msi flag for the .exe installer?
https://github.com/microsoft/PowerToys/wiki/Installer-arguments-for-exe
Since you got it to work, I'll close the issue, but please reopen it if
you run into a problem with the latest build.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4668#issuecomment-753690236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIJDWHQQIFNQ7CWVFF2UPTSYD2Y5ANCNFSM4ON7G3GA
.

I am also having trouble with this. I had Powertoys 0.17.xx running and I saw there were some updates. I downloaded the 0.29.3.exe from here, and when I installed I got the same task scheduler error. I also tried downloading the the previous few releases all with the same error.
I tried --extract_msi as mentioned above and attempted the /q install which didn't give me any errors but also didn't give me any powertoys LOL. my C:\Program Files\Power Toys folder is empty.
I also thought I would try redownloading version 0.17.0 again but that installer told me I had a newer version installed and 0.18.0's installer gave me the same task scheduler error as the latest releases but also gave an "error code 2753" which may not be related....
I did try rebooting a few times through this but that didn't improve my results either.
WinVer 1909 (my employers AD Domain has us halted on this version for the time being)

I am also having trouble with this. I had Powertoys 0.17.xx running and I saw there were some updates. I downloaded the 0.29.3.exe from here, and when I installed I got the same task scheduler error. I also tried downloading the the previous few releases all with the same error.
I tried --extract_msi as mentioned above and attempted the /q install which didn't give me any errors but also didn't give me any powertoys LOL. my C:\Program Files\Power Toys folder is empty.
I also thought I would try redownloading version 0.17.0 again but that installer told me I had a newer version installed and 0.18.0's installer gave me the same task scheduler error as the latest releases but also gave an "error code 2753" which may not be related....
I did try rebooting a few times through this but that didn't improve my results either.
WinVer 1909 (my employers AD Domain has us halted on this version for the time being)

@GsynthChris
please open a new issue.

@GsynthChris
please open a new issue.


Regular failures when trying to fetch PR's

For the past week, we have been seeing a very non-descriptive error popup when trying to generate a changelog.
We get an Error: Server Error at the point it's trying to execute a getBetweenDates API call.
🚀 Load pull requests
  ℹ Comparing org/repo - 'env-date-time-sha...env-date-time-sha2'
  ℹ Found 2 commits from the GitHub API for org/repo
  ℹ Fetching PRs between dates 2024-04-10T14:06.000Z to 2024-04-10T14:41:53.000Z for org/repo
  ℹ Retrieved 2 release commits for org/repo
  Error: Server Error

(obscured some details)
The action is set up as follows:
      - name: Generate Changelog
        id: generate_changelog
        uses<EMAIL_ADDRESS>        with:
          configuration: workflows/.github/generate-changelog-configuration.json
          token: ${{ steps.get_workflow_token.outputs.token }}
          fromTag: ${{ env.PREVIOUS_RELEASE_TAG }}
          toTag: ${{ env.RELEASE_TAG }}

I am not sure where to look for this one, Has anyone seen this happening? Is this possible that the maxPullRequests setting is needed here? How can we get more info besides this non-descriptive error?
Often a re-run fixes the issue. We use an application token for authentication but would expect a different error in case auth would be the issue.
Sorry if I'm at the wrong location but had to start somewhere, why not with people having Github API experience?

Thank you for the ticket @YorickH
Based on the logs it would appear that the most likely place is from Octokit pulling the diff:
https://github.com/mikepenz/release-changelog-builder-action/blob/release/4.x/src/repositories/GithubRepository.ts#L99
Given we would have a log line after it gets the diff:
https://github.com/mikepenz/release-changelog-builder-action/blob/94250de0148ccfb426e53db5dc1ab62e03e49cf7/src/pr-collector/pullRequests.ts#L152
Which then propagates the error up to here:

https://github.com/mikepenz/release-changelog-builder-action/blob/94250de0148ccfb426e53db5dc1ab62e03e49cf7/src/main.ts#L113

Unfortunately the error if it is thrown in octokit is beyond what I can tell about, it could be some server errors from GitHub API, or it might be fixed by updating to the latest release of the 4.x version of the action (from today) with the latest octokit updates.
We might be able to improve the error by logging the whole object, instead of just the message of the error though.

Hi @mikepenz,
Thanks for the input, I doubt the change in octokit will be of much value as it's only a minor security change in the release flow, anyhow still good to keep up with things.
The search continues, maybe switching to use fetchViaCommits might fix some things. We do notice these issues only on a rather large and active repository so there might be just too much to fetch.
Thanks for confirming my suspicion on being an API (or maybe network) issue, might go back to github support as they were locked into the fact we are using ARC instead of the github supported Auto Scaling Runner Set and wouldn't give support (although I doubt it would make any difference). Now I have some specific API requests I can pass.

Let me maybe also make a change to the error log when it fails. so it has the full error object printed. that could perhaps include additional details.

Created v4.2.2 which will log the whole error object. I hope that includes more information on what's happening


make a method to store data in a file for appending between sessions.

At present the files are being overwritten when the arraylist is empty in the main class. Implement a method so that new data is appended to the existing files.

File saving is completed for the application.


Add Picular & Remove.bg

Checklist

[x] I made something good today 💐.
[x] I put links in the correct format: [Tool](link) — description.
[x] My description starts with the lower-case letter and ends with the full stop.
[x] I put the tool in the alphabetical order.

Optional

[x] I added the appropriate labels: free, open-source or mac.
[x] I put the tool only to one category.
[x] I followed Contribution Guidelines.

@xiaoluoboding thanks for adding great tools!


Bug when formatting huge numbers

Hi,
numeral(1e21).format('0.[0]')  throws an error in version 1.5.6 and returns NaN in 2.0.6
thanks

duplicate with many others (eg #629)


Not getting the aligned depth map when using the D435i

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
4.15

Platform
PC

SDK Version
2.19.1

Language
Python 3

Segment
Robot

Issue Description
Cannot grab the aligned depth frame from the D435i. I have tested the same code with a D435 and it works perfectly.

Figure 1: Output generated with a D435i

Figure 2: Output generated with a D435
Source code:
## License: Apache 2.0. See LICENSE file in root directory.
## Copyright(c) 2017 Intel Corporation. All Rights Reserved.

#####################################################
##              Align Depth to Color               ##
#####################################################

# First import the library
import pyrealsense2 as rs
# Import Numpy for easy array manipulation
import numpy as np
# Import OpenCV for easy image rendering
import cv2

# Create a pipeline
pipeline = rs.pipeline()

# Create a config and configure the pipeline to stream
#  different resolutions of color and depth streams
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 360, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)

# Start streaming
profile = pipeline.start(config)

# Getting the depth sensor's depth scale (see rs-align example for explanation)
depth_sensor = profile.get_device().first_depth_sensor()
depth_scale = depth_sensor.get_depth_scale()
print("Depth Scale is: ", depth_scale)

# We will be removing the background of objects more than
#  clipping_distance_in_meters meters away
clipping_distance_in_meters = 3  # 1 meter
clipping_distance = clipping_distance_in_meters / depth_scale

# Create an align object
# rs.align allows us to perform alignment of depth frames to others frames
# The "align_to" is the stream type to which we plan to align depth frames.
align_to = rs.stream.color
align = rs.align(align_to)

# Streaming loop
try:
    while True:
        # Get frameset of color and depth
        frames = pipeline.wait_for_frames()

        # frames.get_depth_frame() is a 640x360 depth image

        # Align the depth frame to color frame
        aligned_frames = align.process(frames)
        # Get aligned frames
        aligned_depth_frame = aligned_frames.get_depth_frame().as_depth_frame()  # aligned_depth_frame is a 640x480 depth image
        color_frame = aligned_frames.get_color_frame()

        depth_frame1 = frames.get_depth_frame()
        color_frame1 = frames.get_color_frame()

        # Validate that both frames are valid
        if not aligned_depth_frame or not color_frame or not depth_frame1 or not color_frame1:
            continue

        depth_image = np.asanyarray(aligned_depth_frame.get_data())
        color_image = np.asanyarray(color_frame.get_data())
        depth_image1 = np.asanyarray(depth_frame1.get_data())
        color_image1 = np.asanyarray(color_frame1.get_data())
        # Apply colormap on depth image (image must be converted to 8-bit per pixel first)

        # Remove background - Set pixels further than clipping_distance to grey
        grey_color = 153
        depth_image_3d = np.dstack((depth_image, depth_image, depth_image))  # depth image is 1 channel, color is 3 channels
        depth_image_3d1 = np.dstack((depth_image1, depth_image1, depth_image1))  # depth image is 1 channel, color is 3 channels
        bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0), grey_color, color_image)
        # Render images
        depth_colormap = cv2.applyColorMap(cv2.convertScaleAbs(depth_image, alpha=0.03), cv2.COLORMAP_JET)
        depth_colormap1 = cv2.applyColorMap(cv2.convertScaleAbs(depth_image1, alpha=0.03), cv2.COLORMAP_JET)
        images = np.hstack((color_image, bg_removed))
        cv2.namedWindow('Align Example', cv2.WINDOW_AUTOSIZE)
        cv2.imshow('Align Example', images)
        cv2.imshow('Example RGB', color_image1)
        cv2.imshow('Example depth', depth_colormap1)
        key = cv2.waitKey(1)
        # Press esc or 'q' to close the image window
        if key & 0xFF == ord('q') or key == 27:
            cv2.destroyAllWindows()
            break
finally:
    pipeline.stop()

Hi @dorodnic ,
Does this situation also happen in C/C++?

This is a similar issue with #3201. How about running "rs-enumerate-devices -c" to see the calibration data there?

Hi @pedrombmachado,
As #3201, I suspect probably the extrinsic calibration data has something wrong. You can consider to have a replacement or have a try of the dynamic calibration tool.

Hi @RealSense-Customer-Engineering ,
I tried to get the calibration tool but I am getting the following error:

Can you please advise on what to do next?

Hi @pedrombmachado,
The calibration table has the compatibility issue. A factory calibration is required to recover from this status. Please have a replacement.

Hi @pedrombmachado,
Before the replacemnt of the camera, can you also install and try the dynamic calibration tool to dump the raw active calibration tables?
In Win10, the Intel.Realsense.CustomRW.exe tool in DC package under C:\CalibrationToolAPI<version>\bin. (now, the version is <IP_ADDRESS>)
In Ubuntu, the Intel.Realsense.CustomRW tool ins in /usr/bin.
Try to read raw calibration table from device and save into a binary file, supported table id 19, 1F, and 20, for example,
Intel.Realsense.CustomRW -r -raw 19 -f mytable-19.bin
Intel.Realsense.CustomRW -r -raw 1F -f mytable-1F.bin
Intel.Realsense.CustomRW -r -raw 20 -f mytable-20.bin

Hi @RealSense-Customer-Engineering
My only problem is that I do not have windows machines near me. All the computers in the Robotics lab run Linux. Is there an updated version of the calibration tool for Linux?

Hi @RealSense-Customer-Engineering
I
Please download the 3 files from here
However I thinkt the problem are not the calibration tables because I can see the depth map when I run the realsense-viewer. Please check Figure 1

Figure1: Screenshot of the realsense-viewer
Please advise.
BW
Pedro

Thanks for the files, @pedrombmachado. Will further analyze since the mismatched table info shows in the dynamic calibration tool with D435i.
If any update, will let you know ASAP.

Hi @RealSense-Customer-Engineering ,
I forgot to mention that I am getting the depth map. I am not getting any image from the aligned_frames. Please check below.

The problem is only with the aligned frames.

@pedrombmachado, to add on @RealSenseCustomerSupport response - this is how you can check  Depth<->RGB extrinsic in less than 3 min:

The fastest way is to run rs-pointcloud or realsense-viewers 3D view with RGB as texture source and to see that the RGB fits the Depth nicely.
It is also useful to examine rs-enumerate-devices -c:

The rotation matrix should be ~roughly~ diagonal identity matrix
The translation vector norm should be ~15mm .

You can also post the result of rs-enumerate.. for review

Hi @ev-mp and @RealSense-Customer-Engineering ,
Please find below the output of the rs-pointcloud

The output of rs-enumerate-devices -c is listed below:

Device info:
Name                          : 	Intel RealSense D435I
Serial Number                 :<PHONE_NUMBER>91
Firmware Version              : 	<IP_ADDRESS>
<IP_ADDRESS>
Recommended Firmware Version  : 	<IP_ADDRESS>
Physical Port                 : 	/sys/devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/video4linux/video1
Debug Op Code                 : 	15
Advanced Mode                 : 	YES
Product Id                    : 	0B3A
Usb Type Descriptor           : 	3.2
Stream Profiles supported by Stereo Module
Supported modes:
stream       resolution      fps       format
Infrared 1	  1280x800	@ 30Hz	   Y8
Infrared 2	  1280x800	@ 30Hz	   Y8
Infrared 1	  1280x800	@ 25Hz	   Y16
Infrared 2	  1280x800	@ 25Hz	   Y16
Infrared 1	  1280x800	@ 15Hz	   Y16
Infrared 2	  1280x800	@ 15Hz	   Y16
Infrared 2	  1280x800	@ 15Hz	   Y8
Infrared 1	  1280x800	@ 15Hz	   Y8
Infrared 1	  1280x720	@ 30Hz	   Y8
Infrared 2	  1280x720	@ 30Hz	   Y8
Infrared 1	  1280x720	@ 15Hz	   Y8
Infrared 2	  1280x720	@ 15Hz	   Y8
Infrared 1	  1280x720	@ 6Hz	   Y8
Infrared 2	  1280x720	@ 6Hz	   Y8
Infrared 1	  848x480	@ 90Hz	   Y8
Infrared 2	  848x480	@ 90Hz	   Y8
Infrared 1	  848x480	@ 60Hz	   Y8
Infrared 2	  848x480	@ 60Hz	   Y8
Infrared 2	  848x480	@ 30Hz	   Y8
Infrared 1	  848x480	@ 30Hz	   Y8
Infrared 2	  848x480	@ 15Hz	   Y8
Infrared 1	  848x480	@ 15Hz	   Y8
Infrared 1	  848x480	@ 6Hz	   Y8
Infrared 2	  848x480	@ 6Hz	   Y8
Infrared 1	  640x480	@ 90Hz	   Y8
Infrared 2	  640x480	@ 90Hz	   Y8
Infrared 2	  640x480	@ 60Hz	   Y8
Infrared 1	  640x480	@ 60Hz	   Y8
Infrared 2	  640x480	@ 30Hz	   Y8
Infrared 1	  640x480	@ 30Hz	   Y8
Infrared 2	  640x480	@ 15Hz	   Y8
Infrared 1	  640x480	@ 15Hz	   Y8
Infrared 2	  640x480	@ 6Hz	   Y8
Infrared 1	  640x480	@ 6Hz	   Y8
Infrared 2	  640x400	@ 25Hz	   Y16
Infrared 1	  640x400	@ 25Hz	   Y16
Infrared 1	  640x400	@ 15Hz	   Y16
Infrared 2	  640x400	@ 15Hz	   Y16
Infrared 2	  640x360	@ 90Hz	   Y8
Infrared 1	  640x360	@ 90Hz	   Y8
Infrared 2	  640x360	@ 60Hz	   Y8
Infrared 1	  640x360	@ 60Hz	   Y8
Infrared 2	  640x360	@ 30Hz	   Y8
Infrared 1	  640x360	@ 30Hz	   Y8
Infrared 2	  640x360	@ 15Hz	   Y8
Infrared 1	  640x360	@ 15Hz	   Y8
Infrared 2	  640x360	@ 6Hz	   Y8
Infrared 1	  640x360	@ 6Hz	   Y8
Infrared 2	  480x270	@ 90Hz	   Y8
Infrared 1	  480x270	@ 90Hz	   Y8
Infrared 2	  480x270	@ 60Hz	   Y8
Infrared 1	  480x270	@ 60Hz	   Y8
Infrared 2	  480x270	@ 30Hz	   Y8
Infrared 1	  480x270	@ 30Hz	   Y8
Infrared 2	  480x270	@ 15Hz	   Y8
Infrared 1	  480x270	@ 15Hz	   Y8
Infrared 1	  480x270	@ 6Hz	   Y8
Infrared 2	  480x270	@ 6Hz	   Y8
Infrared 1	  424x240	@ 90Hz	   Y8
Infrared 2	  424x240	@ 90Hz	   Y8
Infrared 2	  424x240	@ 60Hz	   Y8
Infrared 1	  424x240	@ 60Hz	   Y8
Infrared 2	  424x240	@ 30Hz	   Y8
Infrared 1	  424x240	@ 30Hz	   Y8
Infrared 2	  424x240	@ 15Hz	   Y8
Infrared 1	  424x240	@ 15Hz	   Y8
Infrared 1	  424x240	@ 6Hz	   Y8
Infrared 2	  424x240	@ 6Hz	   Y8
Depth	  1280x720	@ 30Hz	   Z16
Depth	  1280x720	@ 15Hz	   Z16
Depth	  1280x720	@ 6Hz	   Z16
Depth	  848x480	@ 90Hz	   Z16
Depth	  848x480	@ 60Hz	   Z16
Depth	  848x480	@ 30Hz	   Z16
Depth	  848x480	@ 15Hz	   Z16
Depth	  848x480	@ 6Hz	   Z16
Depth	  640x480	@ 90Hz	   Z16
Depth	  640x480	@ 60Hz	   Z16
Depth	  640x480	@ 30Hz	   Z16
Depth	  640x480	@ 15Hz	   Z16
Depth	  640x480	@ 6Hz	   Z16
Depth	  640x360	@ 90Hz	   Z16
Depth	  640x360	@ 60Hz	   Z16
Depth	  640x360	@ 30Hz	   Z16
Depth	  640x360	@ 15Hz	   Z16
Depth	  640x360	@ 6Hz	   Z16
Depth	  480x270	@ 90Hz	   Z16
Depth	  480x270	@ 60Hz	   Z16
Depth	  480x270	@ 30Hz	   Z16
Depth	  480x270	@ 15Hz	   Z16
Depth	  480x270	@ 6Hz	   Z16
Depth	  424x240	@ 90Hz	   Z16
Depth	  424x240	@ 60Hz	   Z16
Depth	  424x240	@ 30Hz	   Z16
Depth	  424x240	@ 15Hz	   Z16
Depth	  424x240	@ 6Hz	   Z16
Stream Profiles supported by RGB Camera
Supported modes:
stream       resolution      fps       format
Color	  1920x1080	@ 30Hz	   RGB8
Color	  1920x1080	@ 30Hz	   RAW16
Color	  1920x1080	@ 30Hz	   Y16
Color	  1920x1080	@ 30Hz	   BGRA8
Color	  1920x1080	@ 30Hz	   RGBA8
Color	  1920x1080	@ 30Hz	   BGR8
Color	  1920x1080	@ 30Hz	   YUYV
Color	  1920x1080	@ 15Hz	   RGB8
Color	  1920x1080	@ 15Hz	   Y16
Color	  1920x1080	@ 15Hz	   BGRA8
Color	  1920x1080	@ 15Hz	   RGBA8
Color	  1920x1080	@ 15Hz	   BGR8
Color	  1920x1080	@ 15Hz	   YUYV
Color	  1920x1080	@ 6Hz	   RGB8
Color	  1920x1080	@ 6Hz	   Y16
Color	  1920x1080	@ 6Hz	   BGRA8
Color	  1920x1080	@ 6Hz	   RGBA8
Color	  1920x1080	@ 6Hz	   BGR8
Color	  1920x1080	@ 6Hz	   YUYV
Color	  1280x720	@ 30Hz	   RGB8
Color	  1280x720	@ 30Hz	   Y16
Color	  1280x720	@ 30Hz	   BGRA8
Color	  1280x720	@ 30Hz	   RGBA8
Color	  1280x720	@ 30Hz	   BGR8
Color	  1280x720	@ 30Hz	   YUYV
Color	  1280x720	@ 15Hz	   RGB8
Color	  1280x720	@ 15Hz	   Y16
Color	  1280x720	@ 15Hz	   BGRA8
Color	  1280x720	@ 15Hz	   RGBA8
Color	  1280x720	@ 15Hz	   BGR8
Color	  1280x720	@ 15Hz	   YUYV
Color	  1280x720	@ 6Hz	   RGB8
Color	  1280x720	@ 6Hz	   Y16
Color	  1280x720	@ 6Hz	   BGRA8
Color	  1280x720	@ 6Hz	   RGBA8
Color	  1280x720	@ 6Hz	   BGR8
Color	  1280x720	@ 6Hz	   YUYV
Color	  960x540	@ 60Hz	   RGB8
Color	  960x540	@ 60Hz	   Y16
Color	  960x540	@ 60Hz	   BGRA8
Color	  960x540	@ 60Hz	   RGBA8
Color	  960x540	@ 60Hz	   BGR8
Color	  960x540	@ 60Hz	   YUYV
Color	  960x540	@ 30Hz	   RGB8
Color	  960x540	@ 30Hz	   Y16
Color	  960x540	@ 30Hz	   BGRA8
Color	  960x540	@ 30Hz	   RGBA8
Color	  960x540	@ 30Hz	   BGR8
Color	  960x540	@ 30Hz	   YUYV
Color	  960x540	@ 15Hz	   RGB8
Color	  960x540	@ 15Hz	   Y16
Color	  960x540	@ 15Hz	   BGRA8
Color	  960x540	@ 15Hz	   RGBA8
Color	  960x540	@ 15Hz	   BGR8
Color	  960x540	@ 15Hz	   YUYV
Color	  960x540	@ 6Hz	   RGB8
Color	  960x540	@ 6Hz	   Y16
Color	  960x540	@ 6Hz	   BGRA8
Color	  960x540	@ 6Hz	   RGBA8
Color	  960x540	@ 6Hz	   BGR8
Color	  960x540	@ 6Hz	   YUYV
Color	  848x480	@ 60Hz	   RGB8
Color	  848x480	@ 60Hz	   Y16
Color	  848x480	@ 60Hz	   BGRA8
Color	  848x480	@ 60Hz	   RGBA8
Color	  848x480	@ 60Hz	   BGR8
Color	  848x480	@ 60Hz	   YUYV
Color	  848x480	@ 30Hz	   RGB8
Color	  848x480	@ 30Hz	   Y16
Color	  848x480	@ 30Hz	   BGRA8
Color	  848x480	@ 30Hz	   RGBA8
Color	  848x480	@ 30Hz	   BGR8
Color	  848x480	@ 30Hz	   YUYV
Color	  848x480	@ 15Hz	   RGB8
Color	  848x480	@ 15Hz	   Y16
Color	  848x480	@ 15Hz	   BGRA8
Color	  848x480	@ 15Hz	   RGBA8
Color	  848x480	@ 15Hz	   BGR8
Color	  848x480	@ 15Hz	   YUYV
Color	  848x480	@ 6Hz	   RGB8
Color	  848x480	@ 6Hz	   Y16
Color	  848x480	@ 6Hz	   BGRA8
Color	  848x480	@ 6Hz	   RGBA8
Color	  848x480	@ 6Hz	   BGR8
Color	  848x480	@ 6Hz	   YUYV
Color	  640x480	@ 60Hz	   RGB8
Color	  640x480	@ 60Hz	   Y16
Color	  640x480	@ 60Hz	   BGRA8
Color	  640x480	@ 60Hz	   RGBA8
Color	  640x480	@ 60Hz	   BGR8
Color	  640x480	@ 60Hz	   YUYV
Color	  640x480	@ 30Hz	   RGB8
Color	  640x480	@ 30Hz	   Y16
Color	  640x480	@ 30Hz	   BGRA8
Color	  640x480	@ 30Hz	   RGBA8
Color	  640x480	@ 30Hz	   BGR8
Color	  640x480	@ 30Hz	   YUYV
Color	  640x480	@ 15Hz	   RGB8
Color	  640x480	@ 15Hz	   Y16
Color	  640x480	@ 15Hz	   BGRA8
Color	  640x480	@ 15Hz	   RGBA8
Color	  640x480	@ 15Hz	   BGR8
Color	  640x480	@ 15Hz	   YUYV
Color	  640x480	@ 6Hz	   RGB8
Color	  640x480	@ 6Hz	   Y16
Color	  640x480	@ 6Hz	   BGRA8
Color	  640x480	@ 6Hz	   RGBA8
Color	  640x480	@ 6Hz	   BGR8
Color	  640x480	@ 6Hz	   YUYV
Color	  640x360	@ 60Hz	   RGB8
Color	  640x360	@ 60Hz	   Y16
Color	  640x360	@ 60Hz	   BGRA8
Color	  640x360	@ 60Hz	   RGBA8
Color	  640x360	@ 60Hz	   BGR8
Color	  640x360	@ 60Hz	   YUYV
Color	  640x360	@ 30Hz	   RGB8
Color	  640x360	@ 30Hz	   Y16
Color	  640x360	@ 30Hz	   BGRA8
Color	  640x360	@ 30Hz	   RGBA8
Color	  640x360	@ 30Hz	   BGR8
Color	  640x360	@ 30Hz	   YUYV
Color	  640x360	@ 15Hz	   RGB8
Color	  640x360	@ 15Hz	   Y16
Color	  640x360	@ 15Hz	   BGRA8
Color	  640x360	@ 15Hz	   RGBA8
Color	  640x360	@ 15Hz	   BGR8
Color	  640x360	@ 15Hz	   YUYV
Color	  640x360	@ 6Hz	   RGB8
Color	  640x360	@ 6Hz	   Y16
Color	  640x360	@ 6Hz	   BGRA8
Color	  640x360	@ 6Hz	   RGBA8
Color	  640x360	@ 6Hz	   BGR8
Color	  640x360	@ 6Hz	   YUYV
Color	  424x240	@ 60Hz	   RGB8
Color	  424x240	@ 60Hz	   Y16
Color	  424x240	@ 60Hz	   BGRA8
Color	  424x240	@ 60Hz	   RGBA8
Color	  424x240	@ 60Hz	   BGR8
Color	  424x240	@ 60Hz	   YUYV
Color	  424x240	@ 30Hz	   RGB8
Color	  424x240	@ 30Hz	   Y16
Color	  424x240	@ 30Hz	   BGRA8
Color	  424x240	@ 30Hz	   RGBA8
Color	  424x240	@ 30Hz	   BGR8
Color	  424x240	@ 30Hz	   YUYV
Color	  424x240	@ 15Hz	   RGB8
Color	  424x240	@ 15Hz	   Y16
Color	  424x240	@ 15Hz	   BGRA8
Color	  424x240	@ 15Hz	   RGBA8
Color	  424x240	@ 15Hz	   BGR8
Color	  424x240	@ 15Hz	   YUYV
Color	  424x240	@ 6Hz	   RGB8
Color	  424x240	@ 6Hz	   Y16
Color	  424x240	@ 6Hz	   BGRA8
Color	  424x240	@ 6Hz	   RGBA8
Color	  424x240	@ 6Hz	   BGR8
Color	  424x240	@ 6Hz	   YUYV
Color	  320x240	@ 60Hz	   RGB8
Color	  320x240	@ 60Hz	   Y16
Color	  320x240	@ 60Hz	   BGRA8
Color	  320x240	@ 60Hz	   RGBA8
Color	  320x240	@ 60Hz	   BGR8
Color	  320x240	@ 60Hz	   YUYV
Color	  320x240	@ 30Hz	   RGB8
Color	  320x240	@ 30Hz	   Y16
Color	  320x240	@ 30Hz	   BGRA8
Color	  320x240	@ 30Hz	   RGBA8
Color	  320x240	@ 30Hz	   BGR8
Color	  320x240	@ 30Hz	   YUYV
Color	  320x240	@ 6Hz	   RGB8
Color	  320x240	@ 6Hz	   Y16
Color	  320x240	@ 6Hz	   BGRA8
Color	  320x240	@ 6Hz	   RGBA8
Color	  320x240	@ 6Hz	   BGR8
Color	  320x240	@ 6Hz	   YUYV
Color	  320x180	@ 60Hz	   RGB8
Color	  320x180	@ 60Hz	   Y16
Color	  320x180	@ 60Hz	   BGRA8
Color	  320x180	@ 60Hz	   RGBA8
Color	  320x180	@ 60Hz	   BGR8
Color	  320x180	@ 60Hz	   YUYV
Color	  320x180	@ 30Hz	   RGB8
Color	  320x180	@ 30Hz	   Y16
Color	  320x180	@ 30Hz	   BGRA8
Color	  320x180	@ 30Hz	   RGBA8
Color	  320x180	@ 30Hz	   BGR8
Color	  320x180	@ 30Hz	   YUYV
Color	  320x180	@ 6Hz	   RGB8
Color	  320x180	@ 6Hz	   Y16
Color	  320x180	@ 6Hz	   BGRA8
Color	  320x180	@ 6Hz	   RGBA8
Color	  320x180	@ 6Hz	   BGR8
Color	  320x180	@ 6Hz	   YUYV
Stream Profiles supported by Motion Module
Supported modes:
stream       resolution      fps       format
Accel	 N/A		@ 63Hz	   MOTION_XYZ32F
Accel	 N/A		@ 250Hz	   MOTION_XYZ32F
Gyro	 N/A		@ 200Hz	   MOTION_XYZ32F
Gyro	 N/A		@ 400Hz	   MOTION_XYZ32F
Provided Intrinsic:
Intrinsic of "Depth" / 424x240 / {Z16}
Width:      	424
Height:     	240
PPX:<PHONE_NUMBER>04688
PPY:<PHONE_NUMBER>08691
Fx:<PHONE_NUMBER>07031
Fy:<PHONE_NUMBER>07031
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Depth" / 480x270 / {Z16}
Width:      	480
Height:     	270
PPX:<PHONE_NUMBER>9043
PPY:<PHONE_NUMBER>81445
Fx:<PHONE_NUMBER>02734
Fy:<PHONE_NUMBER>02734
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Depth" / 640x360 / {Z16}
Width:      	640
Height:     	360
PPX:<PHONE_NUMBER>48047
PPY:<PHONE_NUMBER>61523
Fx:<PHONE_NUMBER>58594
Fy:<PHONE_NUMBER>58594
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Depth" / 640x480 / {Z16}
Width:      	640
Height:     	480
PPX:<PHONE_NUMBER>01172
PPY:<PHONE_NUMBER>77344
Fx:<PHONE_NUMBER>77344
Fy:<PHONE_NUMBER>77344
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Depth" / 848x480 / {Z16}
Width:      	848
Height:     	480
PPX:<PHONE_NUMBER>09375
PPY:<PHONE_NUMBER>17383
Fx:<PHONE_NUMBER>14062
Fy:<PHONE_NUMBER>14062
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Depth" / 1280x720 / {Z16}
Width:      	1280
Height:     	720
PPX:<PHONE_NUMBER>96094
PPY:<PHONE_NUMBER>23047
Fx:<PHONE_NUMBER>17188
Fy:<PHONE_NUMBER>17188
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 320x180 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	320
Height:     	180
PPX:<PHONE_NUMBER>16406
PPY:        	89.1665802001953
Fx:<PHONE_NUMBER>56641
Fy:<PHONE_NUMBER>15234
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 320x240 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	320
Height:     	240
PPX:<PHONE_NUMBER>21875
PPY:<PHONE_NUMBER>86523
Fx:<PHONE_NUMBER>36328
Fy:<PHONE_NUMBER>20312
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 424x240 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	424
Height:     	240
PPX:<PHONE_NUMBER>21875
PPY:<PHONE_NUMBER>86523
Fx:<PHONE_NUMBER>36328
Fy:<PHONE_NUMBER>20312
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 640x360 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	640
Height:     	360
PPX:<PHONE_NUMBER>32812
PPY:<PHONE_NUMBER>00391
Fx:<PHONE_NUMBER>13281
Fy:<PHONE_NUMBER>30469
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 640x480 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	640
Height:     	480
PPX:<PHONE_NUMBER>4375
PPY:<PHONE_NUMBER>73047
Fx:<PHONE_NUMBER>72656
Fy:<PHONE_NUMBER>40625
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 848x480 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	848
Height:     	480
PPX:<PHONE_NUMBER>4375
PPY:<PHONE_NUMBER>73047
Fx:<PHONE_NUMBER>72656
Fy:<PHONE_NUMBER>40625
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 960x540 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	960
Height:     	540
PPX:<PHONE_NUMBER>66797
PPY:<PHONE_NUMBER>59375
Fx:<PHONE_NUMBER>52344
Fy:<PHONE_NUMBER>28125
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 1280x720 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16}
Width:      	1280
Height:     	720
PPX:<PHONE_NUMBER>65625
PPY:<PHONE_NUMBER>00781
Fx:<PHONE_NUMBER>26562
Fy:<PHONE_NUMBER>60938
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Color" / 1920x1080 / {YUYV/RGB8/BGR8/RGBA8/BGRA8/Y16/RAW16}
Width:      	1920
Height:     	1080
PPX:<PHONE_NUMBER>33594
PPY:<PHONE_NUMBER>1875
Fx:         	1377.91198730469
Fy:         	1373.95947265625
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 424x240 / {Y8}
Width:      	424
Height:     	240
PPX:<PHONE_NUMBER>04688
PPY:<PHONE_NUMBER>08691
Fx:<PHONE_NUMBER>07031
Fy:<PHONE_NUMBER>07031
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 480x270 / {Y8}
Width:      	480
Height:     	270
PPX:<PHONE_NUMBER>9043
PPY:<PHONE_NUMBER>81445
Fx:<PHONE_NUMBER>02734
Fy:<PHONE_NUMBER>02734
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 640x360 / {Y8}
Width:      	640
Height:     	360
PPX:<PHONE_NUMBER>48047
PPY:<PHONE_NUMBER>61523
Fx:<PHONE_NUMBER>58594
Fy:<PHONE_NUMBER>58594
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 640x480 / {Y8}
Width:      	640
Height:     	480
PPX:<PHONE_NUMBER>01172
PPY:<PHONE_NUMBER>77344
Fx:<PHONE_NUMBER>77344
Fy:<PHONE_NUMBER>77344
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 848x480 / {Y8}
Width:      	848
Height:     	480
PPX:<PHONE_NUMBER>09375
PPY:<PHONE_NUMBER>17383
Fx:<PHONE_NUMBER>14062
Fy:<PHONE_NUMBER>14062
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 1280x720 / {Y8}
Width:      	1280
Height:     	720
PPX:<PHONE_NUMBER>96094
PPY:<PHONE_NUMBER>23047
Fx:<PHONE_NUMBER>17188
Fy:<PHONE_NUMBER>17188
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 1" / 1280x800 / {Y8}
Width:      	1280
Height:     	800
PPX:<PHONE_NUMBER>96094
PPY:<PHONE_NUMBER>23047
Fx:<PHONE_NUMBER>17188
Fy:<PHONE_NUMBER>17188
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 424x240 / {Y8}
Width:      	424
Height:     	240
PPX:<PHONE_NUMBER>04688
PPY:<PHONE_NUMBER>08691
Fx:<PHONE_NUMBER>07031
Fy:<PHONE_NUMBER>07031
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 480x270 / {Y8}
Width:      	480
Height:     	270
PPX:<PHONE_NUMBER>9043
PPY:<PHONE_NUMBER>81445
Fx:<PHONE_NUMBER>02734
Fy:<PHONE_NUMBER>02734
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 640x360 / {Y8}
Width:      	640
Height:     	360
PPX:<PHONE_NUMBER>48047
PPY:<PHONE_NUMBER>61523
Fx:<PHONE_NUMBER>58594
Fy:<PHONE_NUMBER>58594
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 640x480 / {Y8}
Width:      	640
Height:     	480
PPX:<PHONE_NUMBER>01172
PPY:<PHONE_NUMBER>77344
Fx:<PHONE_NUMBER>77344
Fy:<PHONE_NUMBER>77344
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 848x480 / {Y8}
Width:      	848
Height:     	480
PPX:<PHONE_NUMBER>09375
PPY:<PHONE_NUMBER>17383
Fx:<PHONE_NUMBER>14062
Fy:<PHONE_NUMBER>14062
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 1280x720 / {Y8}
Width:      	1280
Height:     	720
PPX:<PHONE_NUMBER>96094
PPY:<PHONE_NUMBER>23047
Fx:<PHONE_NUMBER>17188
Fy:<PHONE_NUMBER>17188
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Intrinsic of "Infrared 2" / 1280x800 / {Y8}
Width:      	1280
Height:     	800
PPX:<PHONE_NUMBER>96094
PPY:<PHONE_NUMBER>23047
Fx:<PHONE_NUMBER>17188
Fy:<PHONE_NUMBER>17188
Distortion: 	Brown Conrady
Coeffs:     	0  	0  	0  	0  	0
Provided Motion Intrinsic:
Provided Extrinsic:
Extrinsic from "Depth"	  To	  "Depth" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Depth"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Depth"	  To	  "Infrared 1" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Depth"	  To	  "Infrared 2" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.0499882847070694  0  0
Extrinsic from "Depth"	  To	  "Gyro" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.00552000012248755  -0.00510000018402934  -0.011739999987185
Extrinsic from "Depth"	  To	  "Accel" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.00552000012248755  -0.00510000018402934  -0.011739999987185
Extrinsic from "Color"	  To	  "Depth" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Color"	  To	  "Color" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Color"	  To	  "Infrared 1" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Color"	  To	  "Infrared 2" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Color"	  To	  "Gyro" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Color"	  To	  "Accel" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Infrared 1"	  To	  "Depth" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Infrared 1"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0  0  0
Extrinsic from "Infrared 1"	  To	  "Infrared 1" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Infrared 1"	  To	  "Infrared 2" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.0499882847070694  0  0
Extrinsic from "Infrared 1"	  To	  "Gyro" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.00552000012248755  -0.00510000018402934  -0.011739999987185
Extrinsic from "Infrared 1"	  To	  "Accel" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.00552000012248755  -0.00510000018402934  -0.011739999987185
Extrinsic from "Infrared 2"	  To	  "Depth" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.0499882847070694  0  0
Extrinsic from "Infrared 2"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: 0.0499882847070694  0  0
Extrinsic from "Infrared 2"	  To	  "Infrared 1" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.0499882847070694  0  0
Extrinsic from "Infrared 2"	  To	  "Infrared 2" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Infrared 2"	  To	  "Gyro" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.0555082857608795  -0.00510000018402934  -0.011739999987185
Extrinsic from "Infrared 2"	  To	  "Accel" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0.0555082857608795  -0.00510000018402934  -0.011739999987185
Extrinsic from "Gyro"	  To	  "Depth" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Gyro"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Gyro"	  To	  "Infrared 1" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Gyro"	  To	  "Infrared 2" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.0555082857608795  0.00510000018402934  0.011739999987185
Extrinsic from "Gyro"	  To	  "Gyro" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Gyro"	  To	  "Accel" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Accel"	  To	  "Depth" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Accel"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Accel"	  To	  "Infrared 1" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.00552000012248755  0.00510000018402934  0.011739999987185
Extrinsic from "Accel"	  To	  "Infrared 2" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: -0.0555082857608795  0.00510000018402934  0.011739999987185
Extrinsic from "Accel"	  To	  "Gyro" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0
Extrinsic from "Accel"	  To	  "Accel" :
Rotation Matrix:
1   0   0
0   1   0
0   0   1
Translation Vector: 0  0  0

Hello @pedrombmachado ,
Unfortunately ( but also anticipated) the depth-color extrinsic is not valid indeed:

Extrinsic from "Color"	To	"Depth" :
Rotation Matrix:
0 0 0
0 0 0
0 0 0
Translation Vector: 0 0 0

You can also see that the texture mapping in 3D view is broken.
Did you try to use the dynamic calibration tool to recalculate the extrinsic or flash with factory reset ?

@ev-mp
The dynamic calibration doesn't work (check the error above). I will flash it (again) and then come back to you.
Thanks for the tips.
Bw
Pedro

@ev-mp
Did the firmware upgrade and I am still getting the same issue. Could this an issue be caused by the firmware version? Because, this is exactly same version of firmware that I had running on the D435i.

Extrinsic from "Depth"	  To	  "Color" :
Rotation Matrix:
0   0   0
0   0   0
0   0   0

Problem solved. The solution was to replace the camera.

@pedrombmachado hello,
A brief update - even though it could be less relevant now  -
at least in some cases downgrading the firmware  results in compatibility issue with the firmware being not able to access the calibration data properly. Since the actual data is not impaired, the situation seem to be reverse-able by re-burning the new/latest FW version.
Follow #3788 for updates

It's simple. Change the color and depth frame rate to 30 and the 435i will work as well.


Problem Nav menu on mobile click, opera mini v4.x

i use opera mini (v4.x )mobile for android and click nav menu the page reload for opening the dropdown menu..
close the dropdown menu the page reload again.

Website link: themes.dadesain.com

Opera Mini (and similar thin client browsers) are not officially supported by Bootstrap I'm afraid. Suggest asking for workaround on Stackoverflow or similar. https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker

Uhh... that's how Opera Mini works - it processes JS on the server and returns it to the client. The same happens for every other website.

...and what @techdavid said (I thought the original issue was about the menu not opening/closing after the reload)


Remove details from mesh expansion.

The example in https://preliminary.istio.io/docs/guides/integrating-vms/
actually do not have details running in VM.
/cc @costinm @geeknoid @linsun @sdake

Could we add details service in the diagram to be consistent with the other bookinfo diagram?   I assume it is in k8s?

@linsun done, thanks.


Inconsistent result into leaf.x containing list of None and ERROR

With the same problem that is actually feasible, MIOSQP give inconsistent result, where sometimes it is feasible and give a good result and sometimes stuck into leaf.x containing list of None that make numpy round error.
See: https://github.com/osqp/miosqp/blob/ac672338b0593d865dd15b7a76434f25e24244a9/miosqp/workspace.py#L254
Can you fix this guys?

Please review https://github.com/osqp/miosqp/pull/16


How to do when I want to update my alert rule frequently from different users?

I know that if I want to add or modify an alert rule, I can modify the 'alerts.yml'.
Such as:
- alert: example
expr: >-
ceph_pool_stats_write_bytes_sec{name="service-1"} >  70000000.0
for: 3m
labels:
route: "email"
severity: "warning"
service: "example-1"
annotations:
description: "This is an example."
summary: "This is an example."
But a case is when the alert rules would be modified by different users, I do not think it is a good strategy that modifying a single 'alert.yml' file. Any other strategy can be offered?

Thanks for your report. It looks as if this is actually a question about usage and not development.
To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list.
Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future.


Bid collateral of new purchase price

Per discussion here, the collateral needed for a bid should be the new purchase price. The collateral is redeemed upon acceptance or rejection of the bid.

Completed with https://github.com/Geo-Web-Project/core-contracts/pull/61


tests: kernel: workq: work_queue: kernel.workqueue fails

Describe the bug
The tests/kernel/workq/work_queue/kernel.workqueue fails
Observed for

nrf9160dk_nrf9160
nrf5340dk_nrf5340_cpuapp
nrf5340dk_nrf5340_cpunet
nrf9160dk_nrf9160_ns
nrf5340dk_nrf5340_cpuapp_ns

To Reproduce
Steps to reproduce the behavior:

have nrf9160dk connected
go to your zephyr dir
call ./scripts/twister -T tests/kernel/workq/work_queue -p nrf9160dk_nrf9160 --device-testing --device-serial /dev/ttyACM0 -v --inline-logs
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
[2022-08-11T20:42:48.969Z] ERROR   - *** Booting Zephyr OS build zephyr-v3.1.0-3361-gb076aa373a63  ***
[2022-08-11T20:42:48.969Z] Running TESTSUITE workqueue
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_sequence
[2022-08-11T20:42:48.969Z] - Initializing test items
[2022-08-11T20:42:48.969Z] - Submitting test items
[2022-08-11T20:42:48.969Z] - Submitting work 1 from preempt thread
[2022-08-11T20:42:48.969Z] - Running test item 1
[2022-08-11T20:42:48.969Z] - Submitting work 2 from coop thread
[2022-08-11T20:42:48.969Z] - Submitting work 3 from preempt thread
[2022-08-11T20:42:48.969Z] - Submitting work 4 from coop thread
[2022-08-11T20:42:48.969Z] - Running test item 2
[2022-08-11T20:42:48.969Z] - Submitting work 5 from preempt thread
[2022-08-11T20:42:48.969Z] - Submitting work 6 from coop thread
[2022-08-11T20:42:48.969Z] - Waiting for work to finish
[2022-08-11T20:42:48.969Z] - Running test item 3
[2022-08-11T20:42:48.969Z] - Running test item 4
[2022-08-11T20:42:48.969Z] - Running test item 5
[2022-08-11T20:42:48.969Z] - Running test item 6
[2022-08-11T20:42:48.969Z] PASS - test_sequence in 0.929 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_resubmit
[2022-08-11T20:42:48.969Z] Starting resubmit test
[2022-08-11T20:42:48.969Z] - Submitting work
[2022-08-11T20:42:48.969Z] - Waiting for work to finish
[2022-08-11T20:42:48.969Z] - Resubmitting work
[2022-08-11T20:42:48.969Z] - Resubmitting work
[2022-08-11T20:42:48.969Z] - Resubmitting work
[2022-08-11T20:42:48.969Z] - Resubmitting work
[2022-08-11T20:42:48.969Z] - Resubmitting work
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_resubmit in 0.729 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_delayed
[2022-08-11T20:42:48.969Z] Starting delayed test
[2022-08-11T20:42:48.969Z] - Initializing delayed test items
[2022-08-11T20:42:48.969Z] - Submitting delayed test items
[2022-08-11T20:42:48.969Z] - Submitting delayed work 1 from preempt thread
[2022-08-11T20:42:48.969Z] - Submitting delayed work 3 from preempt thread
[2022-08-11T20:42:48.969Z] - Submitting delayed work 5 from preempt thread
[2022-08-11T20:42:48.969Z] - Waiting for delayed work to finish
[2022-08-11T20:42:48.969Z] - Submitting delayed work 2 from coop thread
[2022-08-11T20:42:48.969Z] - Submitting delayed work 4 from coop thread
[2022-08-11T20:42:48.969Z] - Submitting delayed work 6 from coop thread
[2022-08-11T20:42:48.969Z] - Running delayed test item 1
[2022-08-11T20:42:48.969Z] - Running delayed test item 2
[2022-08-11T20:42:48.969Z] - Running delayed test item 3
[2022-08-11T20:42:48.969Z] - Running delayed test item 4
[2022-08-11T20:42:48.969Z] - Running delayed test item 5
[2022-08-11T20:42:48.969Z] - Running delayed test item 6
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_delayed in 0.817 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_delayed_cancel
[2022-08-11T20:42:48.969Z] Starting delayed cancel test
[2022-08-11T20:42:48.969Z] - Cancel delayed work from preempt thread
[2022-08-11T20:42:48.969Z] - Waiting for work to finish
[2022-08-11T20:42:48.969Z] - Cancel delayed work from coop thread
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_delayed_cancel in 0.141 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_delayed_pending
[2022-08-11T20:42:48.969Z] Starting delayed pending test
[2022-08-11T20:42:48.969Z] - Check pending delayed work when in workqueue
[2022-08-11T20:42:48.969Z] - Running delayed test item 1
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] - Check pending delayed work with timeout
[2022-08-11T20:42:48.969Z] - Running delayed test item 1
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_delayed_pending in 0.180 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_triggered
[2022-08-11T20:42:48.969Z] Starting triggered test
[2022-08-11T20:42:48.969Z] - Initializing triggered test items
[2022-08-11T20:42:48.969Z] - Submitting triggered test items
[2022-08-11T20:42:48.969Z] - Submitting triggered work 1
[2022-08-11T20:42:48.969Z] - Submitting triggered work 2
[2022-08-11T20:42:48.969Z] - Submitting triggered work 3
[2022-08-11T20:42:48.969Z] - Submitting triggered work 4
[2022-08-11T20:42:48.969Z] - Submitting triggered work 5
[2022-08-11T20:42:48.969Z] - Submitting triggered work 6
[2022-08-11T20:42:48.969Z] - Triggering test items execution
[2022-08-11T20:42:48.969Z] - Triggering work 1
[2022-08-11T20:42:48.969Z] - Triggering work 2
[2022-08-11T20:42:48.969Z] - Triggering work 3
[2022-08-11T20:42:48.969Z] - Triggering work 4
[2022-08-11T20:42:48.969Z] - Triggering work 5
[2022-08-11T20:42:48.969Z] - Triggering work 6
[2022-08-11T20:42:48.969Z] - Running triggered test item 1
[2022-08-11T20:42:48.969Z] - Running triggered test item 2
[2022-08-11T20:42:48.969Z] - Running triggered test item 3
[2022-08-11T20:42:48.969Z] - Running triggered test item 4
[2022-08-11T20:42:48.969Z] - Running triggered test item 5
[2022-08-11T20:42:48.969Z] - Running triggered test item 6
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_triggered in 0.282 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_already_triggered
[2022-08-11T20:42:48.969Z] Starting triggered test
[2022-08-11T20:42:48.969Z] - Initializing triggered test items
[2022-08-11T20:42:48.969Z] - Triggering test items execution
[2022-08-11T20:42:48.969Z] - Triggering work 1
[2022-08-11T20:42:48.969Z] - Triggering work 2
[2022-08-11T20:42:48.969Z] - Triggering work 3
[2022-08-11T20:42:48.969Z] - Triggering work 4
[2022-08-11T20:42:48.969Z] - Triggering work 5
[2022-08-11T20:42:48.969Z] - Triggering work 6
[2022-08-11T20:42:48.969Z] - Submitting triggered test items
[2022-08-11T20:42:48.969Z] - Submitting triggered work 1
[2022-08-11T20:42:48.969Z] - Submitting triggered work 2
[2022-08-11T20:42:48.969Z] - Submitting triggered work 3
[2022-08-11T20:42:48.969Z] - Submitting triggered work 4
[2022-08-11T20:42:48.969Z] - Submitting triggered work 5
[2022-08-11T20:42:48.969Z] - Submitting triggered work 6
[2022-08-11T20:42:48.969Z] - Running triggered test item 1
[2022-08-11T20:42:48.969Z] - Running triggered test item 2
[2022-08-11T20:42:48.969Z] - Running triggered test item 3
[2022-08-11T20:42:48.969Z] - Running triggered test item 4
[2022-08-11T20:42:48.969Z] - Running triggered test item 5
[2022-08-11T20:42:48.969Z] - Running triggered test item 6
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_already_triggered in 0.282 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_triggered_resubmit
[2022-08-11T20:42:48.969Z] Starting triggered resubmit test
[2022-08-11T20:42:48.969Z] - Submitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 1)
[2022-08-11T20:42:48.969Z] - Resubmitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 2)
[2022-08-11T20:42:48.969Z] - Resubmitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 3)
[2022-08-11T20:42:48.969Z] - Resubmitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 4)
[2022-08-11T20:42:48.969Z] - Resubmitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 5)
[2022-08-11T20:42:48.969Z] - Resubmitting triggered work
[2022-08-11T20:42:48.969Z] - Triggering test item execution (iteration: 6)
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_triggered_resubmit in 0.714 seconds
[2022-08-11T20:42:48.969Z] ===================================================================
[2022-08-11T20:42:48.969Z] START - test_triggered_no_wait
[2022-08-11T20:42:48.969Z] Starting triggered test
[2022-08-11T20:42:48.969Z] - Initializing triggered test items
[2022-08-11T20:42:48.969Z] - Triggering test items execution
[2022-08-11T20:42:48.969Z] - Triggering work 1
[2022-08-11T20:42:48.969Z] - Triggering work 2
[2022-08-11T20:42:48.969Z] - Triggering work 3
[2022-08-11T20:42:48.969Z] - Triggering work 4
[2022-08-11T20:42:48.969Z] - Triggering work 5
[2022-08-11T20:42:48.969Z] - Triggering work 6
[2022-08-11T20:42:48.969Z] - Submitting triggered test items
[2022-08-11T20:42:48.969Z] - Submitting triggered work 1
[2022-08-11T20:42:48.969Z] - Submitting triggered work 2
[2022-08-11T20:42:48.969Z] - Submitting triggered work 3
[2022-08-11T20:42:48.969Z] - Submitting triggered work 4
[2022-08-11T20:42:48.969Z] - Submitting triggered work 5
[2022-08-11T20:42:48.969Z] - Submitting triggered work 6
[2022-08-11T20:42:48.969Z] - Running triggered test item 1
[2022-08-11T20:42:48.969Z] - Running triggered test item 2
[2022-08-11T20:42:48.969Z] - Running triggered test item 3
[2022-08-11T20:42:48.969Z] - Running triggered test item 4
[2022-08-11T20:42:48.969Z] - Running triggered test item 5
[2022-08-11T20:42:48.969Z] - Running triggered test item 6
[2022-08-11T20:42:48.969Z] - Checking results
[2022-08-11T20:42:48.969Z] PASS - test_triggered_no_wait in 0.282 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_triggered_no_wait_expired
[2022-08-11T20:42:48.970Z] Starting triggered test
[2022-08-11T20:42:48.970Z] - Initializing triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered work 1
[2022-08-11T20:42:48.970Z] - Submitting triggered work 2
[2022-08-11T20:42:48.970Z] - Submitting triggered work 3
[2022-08-11T20:42:48.970Z] - Submitting triggered work 4
[2022-08-11T20:42:48.970Z] - Submitting triggered work 5
[2022-08-11T20:42:48.970Z] - Submitting triggered work 6
[2022-08-11T20:42:48.970Z] - Running triggered test item 1
[2022-08-11T20:42:48.970Z] - Running triggered test item 2
[2022-08-11T20:42:48.970Z] - Running triggered test item 3
[2022-08-11T20:42:48.970Z] - Running triggered test item 4
[2022-08-11T20:42:48.970Z] - Running triggered test item 5
[2022-08-11T20:42:48.970Z] - Running triggered test item 6
[2022-08-11T20:42:48.970Z] - Checking results
[2022-08-11T20:42:48.970Z] PASS - test_triggered_no_wait_expired in 0.218 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_triggered_wait
[2022-08-11T20:42:48.970Z] Starting triggered test
[2022-08-11T20:42:48.970Z] - Initializing triggered test items
[2022-08-11T20:42:48.970Z] - Triggering test items execution
[2022-08-11T20:42:48.970Z] - Triggering work 1
[2022-08-11T20:42:48.970Z] - Triggering work 2
[2022-08-11T20:42:48.970Z] - Triggering work 3
[2022-08-11T20:42:48.970Z] - Triggering work 4
[2022-08-11T20:42:48.970Z] - Triggering work 5
[2022-08-11T20:42:48.970Z] - Triggering work 6
[2022-08-11T20:42:48.970Z] - Submitting triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered work 1
[2022-08-11T20:42:48.970Z] - Submitting triggered work 2
[2022-08-11T20:42:48.970Z] - Submitting triggered work 3
[2022-08-11T20:42:48.970Z] - Submitting triggered work 4
[2022-08-11T20:42:48.970Z] - Submitting triggered work 5
[2022-08-11T20:42:48.970Z] - Submitting triggered work 6
[2022-08-11T20:42:48.970Z] - Running triggered test item 1
[2022-08-11T20:42:48.970Z] - Running triggered test item 2
[2022-08-11T20:42:48.970Z] - Running triggered test item 3
[2022-08-11T20:42:48.970Z] - Running triggered test item 4
[2022-08-11T20:42:48.970Z] - Checking results
[2022-08-11T20:42:48.970Z] Assertion failed at ../../../../../../../../../zephyr/zephyr/tests/kernel/workq/work_queue/src/main.c:164: check_results: (num_results not equal to num_tests)
[2022-08-11T20:42:48.970Z] *** work items finished: 4 (expected: 6)
[2022-08-11T20:42:48.970Z] - Running triggered test item 5
[2022-08-11T20:42:48.970Z] - Running triggered test item 6
[2022-08-11T20:42:48.970Z] FAIL - test_triggered_wait in 0.348 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_triggered_wait_expired
[2022-08-11T20:42:48.970Z] Starting triggered test
[2022-08-11T20:42:48.970Z] - Initializing triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered work 1
[2022-08-11T20:42:48.970Z] - Submitting triggered work 2
[2022-08-11T20:42:48.970Z] - Submitting triggered work 3
[2022-08-11T20:42:48.970Z] - Submitting triggered work 4
[2022-08-11T20:42:48.970Z] - Submitting triggered work 5
[2022-08-11T20:42:48.970Z] - Submitting triggered work 6
[2022-08-11T20:42:48.970Z] - Running triggered test item 1
[2022-08-11T20:42:48.970Z] - Checking results (before timeout)
[2022-08-11T20:42:48.970Z] Assertion failed at ../../../../../../../../../zephyr/zephyr/tests/kernel/workq/work_queue/src/main.c:164: check_results: (num_results not equal to num_tests)
[2022-08-11T20:42:48.970Z] *** work items finished: 7 (expected: 0)
[2022-08-11T20:42:48.970Z] - Running triggered test item 2
[2022-08-11T20:42:48.970Z] - Running triggered test item 3
[2022-08-11T20:42:48.970Z] - Running triggered test item 4
[2022-08-11T20:42:48.970Z] - Running triggered test item 5
[2022-08-11T20:42:48.970Z] - Running triggered test item 6
[2022-08-11T20:42:48.970Z] FAIL - test_triggered_wait_expired in 0.321 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_triggered_from_msgq
[2022-08-11T20:42:48.970Z] Starting triggered from msgq test
[2022-08-11T20:42:48.970Z] - Initializing kernel objects
[2022-08-11T20:42:48.970Z] - Starting the thread
[2022-08-11T20:42:48.970Z] PASS - test_triggered_from_msgq in 0.38 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_delayed_work_define
[2022-08-11T20:42:48.970Z] PASS - test_delayed_work_define in 0.1 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] START - test_triggered_cancel
[2022-08-11T20:42:48.970Z] Starting triggered test
[2022-08-11T20:42:48.970Z] - Initializing triggered test items
[2022-08-11T20:42:48.970Z] - Submitting triggered work 1
[2022-08-11T20:42:48.970Z] - Submitting triggered work 2
[2022-08-11T20:42:48.970Z] - Submitting triggered work 3
[2022-08-11T20:42:48.970Z] - Submitting triggered work 4
[2022-08-11T20:42:48.970Z] - Submitting triggered work 5
[2022-08-11T20:42:48.970Z] - Submitting triggered work 6
[2022-08-11T20:42:48.970Z] PASS - test_triggered_cancel in 0.103 seconds
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] TESTSUITE workqueue failed.
[2022-08-11T20:42:48.970Z] ===================================================================
[2022-08-11T20:42:48.970Z] RunID: c6acca80a0d1bab16717d48934738f63
[2022-08-11T20:42:48.970Z] PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.14.1
Commit SHA or Version used: zephyr-v3.1.0-3361-gb076aa373a63

This has already been fixed by #48876.


[Batch] Knack conversion

Merge pending review from @matthchr and @xingwu1

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

View a preview at https://prompt.ws/r/Azure/azure-cli/4990
This is an experimental preview for @microsoft.com users.
(It may take a minute or two for your instance to be ready)
Email feedback to 'azfeedback' with subject 'Prompt Feedback'.

PR for Batch Knack Conversion - #4924

Also PR #5021 was updated which moves and renames the _CommandGroup and _ParametersContext objects, so you'll want to update this accordingly :D

@tjprescott - I've chatted to the Batch team and they have signed-off :)
The only test currently failing for me locally is the account test that depends on KeyVault, however more failures may be exposed once CI is running.

@annatisch sounds good. I'm gonna merge and we can do a follow-up PR later to re-enable CI once KeyVault is in place.


how to import LargeVis, when run the LargeVis_run.py,ModuleNotFoundError: No module named LargeVis

This may be because you work the program not in the correct folder, you should run it under Linux folder.
So you can just change part of main.cpp so that you can run the program just by ./Linux rather than use python file.

python setup.py install
This may be useful.
Note the compatibility issues between python2 and python3

C:\work_space\LargeVis-master\Windows>python setup.py install
running install
running build
running build_ext
building 'LargeVis' extension
error: Unable to find vcvarsall.bat
Why doesn't it work properly?


improve type promotion in strong mode

There are some cases where type promotion won't work. Found while investigating the state of https://github.com/dart-lang/dev_compiler/issues/31.
It roughly falls into a few buckets:

[x] if the original type of T of v was dynamic, the test v is SomeType won't promote. This leads to some suboptimal codegen in SDK (see https://github.com/dart-lang/sdk/issues/25486)
[ ] if the tested type S is not a subtype of T, the test won't promote. You'd have to track a union type.
[ ] the type promotion is only valid in the body/else clause of that if statement. There's no analysis of the rest of the method, meaning patterns like if (v is! S) return; don't affect the type of v in the rest of the method body.
[ ] from Sky, we've heard they would like to do assert(v is S); and have v be treated as S for the rest of the method. Sort of like an unchecked (in production mode) cast, similar to S v2 = v but not requiring a second variable name to be introduced.
[ ] from package:yaml, assignment to the variable in a closure will disable all promotion, this is true even if that closure hasn't been defined yet (and therefore, cannot possibly mutate the variable).
[x] Constrained generic parameter like T extends Event, not promoting to a subtype of Event like InputEvent, see #327
[ ] If the variable is mutated, it won't promote. This is the case even if the mutation doesn't affect the type.
[ ] If the type test wants to allow null, like if (v == null || v is T), it should promote to nullable-T

Moved from https://github.com/dart-lang/dev_compiler/issues/274.

I'd like to propose that v == null promote V. I don't know the type theory well enough to say what— maybe dynamic?—but this would support the following pattern:
void fn(T v) {
  // ...
}

void fnTakesObject(Object v) {
  if (v != null && v is! T) return;
  fn(v);
}

This comes up when implementing collections, since they have a number of methods that take Objects but need more specialized behavior for values of the collection's type.

ah, good example. So right now that won't promote because of flow analysis (issue 3 above) but it'd be equivalent to this:
void fnTakesObject(Object v) {
  if (v == null || v is T) {
    fn(v);
  }
}

Doing || generally would take union types, but we could definitely special case null, since that works for any T.

To add to the list (unless this is being split into smaller issues?):

[ ] Promote in ternary: x is SomeType ? x.someField : 'something' should have an understanding that x has a someField field after the ?.

@srawlins ternary operators already work:
class C {
  var greeting = 'hello';
}
main() {
  Object c = new C();
  print(c is C ? c.greeting : 'world');
}

What you are likely seeing is one of the other problems above. With more info I can help you figure it out.

Is this still happening? Will the analyzer and front_end both do the right thing?

Maybe @leafpetersen knows where the language is heading on this?

@bwilkerson Had a very nice proposal that covered a fair bit of this.  It didn't make the cut for Dart 2 just because of time, but I hope we can find a good way to roll it out post 2.

if the tested type S is not a subtype of T, the test won't promote. You'd have to track a union type.

I think this is https://github.com/dart-lang/sdk/issues/33932
Some of the others are covered by https://github.com/dart-lang/sdk/pull/29624

It looks like this is the canonical request for improved promotion, which is a topic that has been discussed for a long time (no proposal made it into Dart 2, but surely we'll get there at some point).
I think it would be nice to use this issue as a focal point for that proposal. So here's a list of issues on this topic which contains the issues that I know about (you're welcome to extend the list if you know about a relevant issue that I overlooked):

https://github.com/dart-lang/sdk/issues/17281: 'Allow promotion using the raw type'.
https://github.com/dart-lang/sdk/issues/18921: 'Make type rules more flow sensitive'.
https://github.com/dart-lang/sdk/issues/21530: '"is" operator inconsistent with type coercion for member variables'.
https://github.com/dart-lang/sdk/issues/25260: '"this is Foo ? this : null" => "Type check failed: ... is not of type Foo"' (closed, but refers to some properties that may call for enhancements).
https://github.com/dart-lang/sdk/issues/27725: 'type promotion of upper bound does not work inside closures'.
https://github.com/dart-lang/sdk/issues/27813: 'Analyzer does not infer type of dynamic class fields after typecheck'.
https://github.com/dart-lang/sdk/issues/28483: 'analyzer doesn't narrow the type after an is-check when you're reassigning' (closed, but raises the issue of allowing some assignments).
https://github.com/dart-lang/sdk/issues/28586: 'analyzer doesn't trust the "is" operator enough' (closed, but essentially requests intersection types, which has been part of the promotion discussion for a long time).
https://github.com/dart-lang/sdk/issues/33932: 'promote locals without an upcast first' (raises the same concern that usually gives rise to a request for intersection types ;-).
https://github.com/dart-lang/sdk/issues/34483: 'Type promotion could be even better if it analyzed more of the control flow' (this one brings up a more subtle idea: an if that doesn't throw/return may provide a guarantee by assigning to the scrutinee variable).

Moreover, here's a PR that includes an overview of the ideas on the table at the given time:

https://github.com/dart-lang/sdk/pull/29624: "Enhanced Type Promotion" informal proposal.

@jmesserly, I've added a comment at the top of the original text of this issue and adjusted the labels to make this issue "the place to go" for discussions on promotion. I believe it does not fit so well as an 'area-analyzer' issue because the language design needs to be settled first, so I made it an 'area-language' issue; similarly, I removed 'analyzer-strong-mode' because it's now a Dart 2 effort (or 2.x, for some finite x), and the priority.

@eernstg -- that sounds perfect. Yeah feel free to edit my old description to whatever is most is helpful. It's great to have a canonical issue for type promotion work!

Putting check marks on a couple of cases in the initial comment:

if the original type of T of v was dynamic, the test v is SomeType won't promote. This leads to some suboptimal codegen in SDK (see https://github.com/dart-lang/sdk/issues/25486)

In current Dart, it is possible to promote a local variable whose type is dynamic.

if the tested type S is not a subtype of T, the test won't promote. You'd have to track a union type.

Also true today.

the type promotion is only valid in the body/else clause of that if statement. There's no analysis of the rest of the method, meaning patterns like if (v is! S) return; don't affect the type of v in the rest of the method body.

Today we have a rather complex flow analysis, and there are many ways in which the type of v can be affected by the promotion machinery outside the true-continuation of that test.

from Sky, we've heard they would like to do assert(v is S); and have v be treated as S for the rest of the method. Sort of like an unchecked (in production mode) cast, similar to S v2 = v but not requiring a second variable name to be introduced.

We don't do that (because production code cannot be affected by assert statements since they aren't executed), but it can be done using v as S. Flow analysis will then know that this type cast must have succeeded at every location in the code which is reached after having executed the type cast (modulo try/cast and other complex stuff -- but it works! ;-).

from package:yaml, assignment to the variable in a closure will disable all promotion, this is true even if that closure hasn't been defined yet (and therefore, cannot possibly mutate the variable).

Kept this one active, the flow analysis basically doesn't try to keep track of which locations in the code are such that the function object definitely hasn't been invoked. So we're still disabling promotion a bit more than we'd like.

Constrained generic parameter like T extends Event, not promoting to a subtype of Event like InputEvent, see https://github.com/dart-lang/sdk/issues/327

In current Dart we do this: There is a kind of type which is known as an intersection type (it's not a general intersection type, just a special case, and only a compile-time phenomenon). This kind of type supports a few special cases, presumably including the case about Event and InputEvent which is mentioned here. So I added the check mark here, too.

If the variable is mutated, it won't promote. This is the case even if the mutation doesn't affect the type.

Today there are lots of mutations of local variables which are compatible with promotion. We also have a notion of 'demotion' in the case where a promoted variable v gets assigned the value of an expression whose static type isn't assignable to the promoted type of v, but it is assignable to the declared type of v.

If the type test wants to allow null, like if (v == null || v is T), it should promote to nullable-T

I put a check mark here, too, because we can use if (v is T?) and get that promotion.
This seems to indicate that only the part about function objects with potential side effects on local variables isn't yet covered.


Maid 966 test

Reviewed files:

src/beacon.rs @ r1

Comments from the review on Reviewable.io


Inconsistent line references between diagnostic section and sidebar

Describe the bug
The line numbering in the bottom panel is incorrect.
Version
1.3.1-nightly.219396.61c944a
To Reproduce
Steps to reproduce the behavior:

Introduce an LG error in a dialog somewhere
Open the bottom panel
Note the inconsistent line numbers

Expected behavior
Line numbers should be the same when pointing to the same error.
Screenshots

This is actually by design, because the inline error is trying to point to the "relative offset" and the global diagnostic bar is trying to show the "absolute offset" in the file.
Close this for now, free feel to re-open if you think this is still an issue.


[MAINT] Replace Sphinx Gallery dev by stable

Follow-up on https://github.com/skrub-data/skrub/pull/703 since the bug seems to have been addressed.

Related: can we set up the sphinx-gallery recommender system please?
Talk to Arturo if you need help / advice.

In this PR or in a next one?

In this PR or in a next one?

Whatever you feel is best

In this PR or in a next one?

let's do it in another one as it seems a bit orthogonal