Advanced converting data

Task has various of data types in response. We should translate it to objects

Reminders and Categories have separated issues, so only enum fields left


Cannot move window to space on macOS Sequoia (15.1)

Hi, I'm having an issue where I can't move my window to other space with this command: yabai -m window --space  3
If I execute this, yabai will just move the window lower, and it refuses to move that window to the workspace.
Any idea?
fwiw
$ yabai -v
yabai-v7.1.3

Also, if I give sudo yabai --load-sa a try, I get this error:

I have the same issue on Sequoia 15.0.

Same issue on Sequoia 15.0.

Well in theory 15.0 should be working just fine, have you guys tried installing from HEAD?

I have not, is there some information how that's done? I've installed, and are updating through brew.

Have a look: https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(from-HEAD)

I just update to sequoia 15.0 and yabai-v7.1.4 from HEAD.
However, it still cannot move windows to another space.

Have you disabled SIP according to the docs?

Not yet. Thank you for the instruction. I believe that is the reason!

@ZyberSE
Yes, macOS 15 requires partial SIP disabling.

@ZyberSE Yes, macOS 15 requires partial SIP disabling.

Is there any way around this?
Similar to @ZyberSE company policies do not allow me to disable SIP.

Yes, macOS 15 requires partial SIP disabling.

I'd like to know if this was mentioned somewhere. I tried searching the changelog, but couldn't find it.

There is this snippet in the changelog
[7.1.2] - 2024-08-10
Changed

Moving windows to other spaces requires SIP to be disabled on macOS Sequoia #2324 #2331

Same issue on macOS 15
SIP disabled and installed from HEAD did not help.
moving to another display causes other windows to resize as if  target window has moved but actually it stays in place
note: on displays detup  command works as long as space target space is active on another display

hey, you can try out yabai --load-sa, and make sure the Dock isn't restarted during the process.

I disabled SIP on macOS 15.01 and what do you know... it WORKS!! What a f-ing relief! Finally I can work again! 🤩
Didn't install from HEAD, just the same version that comes from brew.

Same here, the reason it was not working was that I didn't disable SIP. Thanks everyone for the help 🙏

Hi, I'm having an issue where I can't move my window to other space with this command: yabai -m window --space 3
If I execute this, yabai will just move the window lower, and it refuses to move that window to the workspace.
Any idea?
fwiw
$ yabai -v
yabai-v7.1.3

Also, if I give sudo yabai --load-sa a try, I get this error:

Maybe you forgot to update the hash in the sudoer file after updating yabai?

Same issue on macOS 15 SIP disabled and installed from HEAD did not help.
moving to another display causes other windows to resize as if target window has moved but actually it stays in place
note: on displays detup command works as long as space target space is active on another display

same here disabled sip partially according to the docs and still have the problem

@twilightty I updated it to the latest Yabai and am still experiencing this issue.
Yabai: yabai-v7.1.4
MacOS: 15.0.1
This command doesn't work
yabai -m window --space next
Do you know if I am missing something?

@twilightty I updated it to the latest Yabai and am still experiencing this issue.
Yabai: yabai-v7.1.4 MacOS: 15.0.1
This command doesn't work yabai -m window --space next
Do you know if I am missing something?

Try running sudo yabai --load-sa


refactor: use non-deprecated NSKeyedArchiver APIs

Refs https://chromium-review.googlesource.com/c/chromium/src/+/4628901
Several [NSKeyedArchiver](https://developer.apple.com/documentation/foundation/nskeyedarchiver) methods have been deprecated and replaced as of macOS 10.13:

unarchiveObjectWithData -> unarchivedObjectOfClass:fromData:error:
archivedDataWithRootObject -> archivedDataWithRootObject:requiringSecureCoding:error:

cc @MarshallOfSound

Another ref https://chromium-review.googlesource.com/c/chromium/src/+/3832503

See https://github.com/electron/electron/pull/40315


Support setting the version

This would be great if you support installing specific versions of gcc.

@HDembinski Sorry for the delay. I agree. I'll think about how best to implement it in a practical way.

@HDembinski There's now the version parameter, which will install the corresponding g++-VERSION package. The ubuntu-toolchain-r/test PPA is enabled for more GCC versions (although it had always been enabled on hosted runners). For a list of versions currently supported on Bionic & Focal, see README. A CI run that tests all the available versions for those distributions can be found here: https://github.com/egor-tensin/setup-gcc/actions/runs/993536290.


Highlight default?

Could you please specify how to highlight a default image (for selection)?

sorry. "defaultValue:" as usual is working fine


Unable to be logged-in on multiple server through the android app

Summary
It is impossible to add a new server while logged in to one server. Also when you have multiple servers configured, you can only be logged-in to one at a time. The error message is the same in both cases: "You are already connected to this server"
Environment Information

Device Name: Unihertz Titan Pocket
OS Version: Android 11
Mattermost App Version: 2.1.0 builds 6000461 & 600457
Mattermost Server Version: 7.8.0 (self-hosted)

Steps to reproduce

Log into a first server (self-hosted) as you normally would
go to the top left server icon
pick "+ Add a server"
enter (self-hosted) server address + name
click connect

You can have the same issue this way:

Log into a first
open browser and go to the url of another (self-hosted) server
from the landing-page, choose to open the app

Expected behavior
The client would connect to a second server
Observed behavior (that appears unintentional)
The client refuses to connect with "You are already connected to this server" although this is not the case

The error message is correct, you should reach put to your server(s) administratornand correct the problem.
Basically someone created a second server by copying the database of the first server, thus the diagnosticId which serves as the server identifier are the same on both servers.
If you want to use the same data on server A and B, the export/import method should be used instead of copying the databases.

I have the same issue. Samsung A52s, Android 13

Thanks, the process is slightly different (creating one vm and using it as a template to create multiple instances for setting up mattermost) but the diagnosticId is indeed the issue, thanks


train, test, valid csv appear empty

Thanks for wonderful contribution.
I am diligently following your provided read.me file. While running python create_dataset.py the train, test and validation files are successfully created but appears to be empty. Here is the illustration of my file navigator.

Here is my path specifications in case you need to help

Just for reference: I have mistakenly copied physionet.org data twice which appears as main folder name in some paths. So my main folder and sub folder has the data twice. please ignore this.
Thank you in advance

Hello!I have meet the same problem.How did you solve this problem?


Adds documentation uploading capabilities

I did this as part of hacky Friday.
It adds to the existing scripts to add document upload capability to this repo including file deletion. It existed in part previously, but required some manual steps.
Now that we have this capability we will be able to add a GitHub Action that ensures the files are updated on every update of the documentation in source.

Closing as we're organising the docs elsewhere


HLS trick mode support

We do not yet support trick mode in HLS.

It looks like there might not be enough information in iframe playlists generated by apple's tools to satisfy MediaSource.
I won't be able to work on this for a while. If anyone else wants to work on it, I have a WIP you can reference.

Without reconstructing a container for the I-frames, this is infeasible on top of MediaSource.  Closing this feature request.


Currently rebuilds all files on spec change

When a single spec is changed it currently results in rebuilding all specs, this needs to be resolved for DX

Cypress added a "just in time compile" for webpack and vite dev servers: https://github.com/cypress-io/cypress/commit/57f6110d29f0b234c969abc747f0fae29c0f4ead
However, I can't really see where the actual implementation is

Cypress added a "just in time compile" for webpack and vite dev servers: cypress-io/cypress@57f6110
However, I can't really see where the actual implementation is. Maybe the dev server doesn't actually need to be changed much.

Thanks, will look into it.

Cypress added a "just in time compile" for webpack and vite dev servers: cypress-io/cypress@57f6110
However, I can't really see where the actual implementation is. Maybe the dev server doesn't actually need to be changed much.

Hi, @Narretz a new version has been released, it would be compatible for the JIT compiler and also fix some bugs.

Amazing turnaround! I will use it once I have migrated to rspack and the latest Cypress versions


fix: take gitsigns config from inner module

Fixing regression after https://github.com/folke/zen-mode.nvim/commit/21ca264c6ae934ceac220cf719c0ed6c0216b057#diff-79fe7b2f00da5c112ea6be1547972b941947fc4444103e14bc9f9548de1f8875L5

This doesn't seem correct?
It should be require("gitsigns.config").config as it is right now. Am I missing something?

require("gitsigns").config does not exist, so would definitely fail

Nevermind 🤦♂
Thank you for fixing this :)

zen-mode w/ gitsigns still worked for me yesterday or so, much later than your last commit, I think gitsigns made changes

probably falsely accused regression on your side, sorry 😇

I totally misread your diff. I probably need to get some sleep 😅


Add Linode support

This quickly adds support for the Linode terraform provider, using existing keys and settings.
The only change required was to slightly re-order the keys in the resources. Linode uses both ip_address and private_ip - which was returning true by default. An extension to this may be to validate the correct key against a matching regex when returning, so that it only returns IPs.

Thanks very much! Looks good except for the note above.

Thank you!


getUserFollowers, getUserFollowing, getUserMedia doesn't return the correct user

Most of the functions like getUserFollowers, getUserFollowing, getUserMedia, etc. first searches for the specific username on the Instagram and then finds the first match and then returns it.
But the thing is, what happens if I have a commonly used username like "funny" where the search result doesn't bring the actual user with username "funny" but instead returns a different account?
This is an important issue that needs to be addressed. If you need further clarification, I can give full details.

Hello,
yes this problem reported before, the solution is to receive data by using userPk.
The person who reported this issue said he will pull a request very soon for this issue.
But if nothing happenes in a few next days, I'll push an update.

issue fixed in #32

Thanks!


qualia: init at 1.0.0

Motivation for this change
New package
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

It looks like the tests are broken upstream, so enabling custom testing would break the build. Would it be preferable if I close this PR for now and return later when it has been fixed, rather than adding the package with doCheck = false;?

No, adding doCheck = false; now is fine. Do you want to maintain this package? If so, you can add the maintainer field. Don't forget to squash the commits eventually.

Squashed, tests disabled and I've added myself as maintainer.


Radiant Crafting table's quick craft buttons consume "returned" items

When using the quick craft slots on a radiant crafting table, recipes do not return items when the recipe indicates they should.
Ex, quark's rusty iron plate (8x iron ingot + 1 bucket of water) consumes the bucket.  If you craft it normally you get the bucket back.
Blood magic recipes involving the orbs show the same issue.

The solution here is to limit the quick-crafting slots to IRecipes that are specifically instances of the Minecraft & Forge default recipes (ShapedOreRecipe, etc). Blood Magic orbs specifically, opening a separate issue about buckets.

Thanks for the report, I'm merging this into #29 as it'll cover both.


Custom hover status bar styles are messed up

I forgot how to get into that state in the first place :s

Oh right, configuring terminal.integrated.environmentChangesRelaunch helped.


(V5) Mismatched image and mask resolutions.

There appear to be several cases where the size of the original image and the size of a segmentation mask belonging to an object in the image are different.
For example, for training image 0cddfe521cf926bf, and mask 0cddfe521cf926bf_m0c9ph5_9ae6e629, the original image size is 768x1024, while the mask is 1200x1600. There are also cases where the image is larger than the mask, such as in the case of image 092e0c44f0bfe7e3 and mask 092e0c44f0bfe7e3_m01yrx_8db3ace7.
I have observed for a (not so) random sample of 1000 images (they were filtered by object classes first) that only about 6% of the images have masks with matching resolutions. I've also observed for this sample that one of the images seems to have a resolution that is a multiple of the other, i.e. the image was resized by a constant factor, preserving the aspect ratio.
Is this expected behavior or is there something wrong with my data? I've download the images from CVDF.
If this is expected behavior, what is the recommended approach to matching the size of the two images? While it seems relatively safe to simply reduce the size of the original image when it is the larger of the two, both upscaling the original image and downscaling the mask seem to be poor ideas for the case where the mask is the larger of the images.

Hello all.
Indeed the image masks do not match the released images.
It turns out the images available to download from https://g.co/dataset/open-images (via CVDF or Figure Eight) are a resized version of the original Flickr image.
"The images are rescaled to have at most 1024 pixels on their longest side" says https://github.com/cvdfoundation/open-images-dataset
However the annotations were done over a set of images with a different resizing rule ("at most 1600 pixels on the largest size"). The good news is that thus the annotations are actually higher resolution than the images (the ones available to download, the originals from Flickr might be even larger).
I am surprised that you found one case where it is the reverse, I would expect this to be rare.

what is the recommended approach to matching the size of the two images?
In any case, the aspect ratio of the binary mask images should be the same as the rgb images; thus resizing should be fine.
In general I would recommend to upscale instead of downscale (normally that would mean up-scaling the RGB image to match the masks), so that there is no information loss in the system.

It's true that many segmentations and images are mismatched, but also there are some images which have sizes much larger than 1024px, e.g. 6e4c43968cdada66.jpg and<PHONE_NUMBER>44a7ad.jpg.
I know that the issue is old, but I found it while looking for answers for my problems and maybe it will help someone else and save them some time. ;)


Update to tailwind v.1

Tailwind's config file got restructured in https://github.com/tailwindcss/tailwindcss/tree/v1.0.0-beta.1.
References need to be adjusted.
More info:
tailwindcss/tailwindcss#637

Thanks for MR Matiej! I published the v1 support under beta tag - https://www.npmjs.com/package/tailwind-bootstrap-grid/v/2.0.0
(Further changes will be done in https://github.com/buz-zard/tailwind-bootstrap-grid/pull/12)


[Suggestion] lightweight client without react email / axios

Hey guys,
Been loving experience around resend's sdk thus far and decided to swing by and leave a suggestion. After glancing at internals it seems like you could offer a more lightweight (additional?) client via dropping @react-email/render and axios and utalising node's native fetch client.
Such client could come handy for newer projects / not using react perhaps?

Commenting on this closed issue, so apologies, but I second this. Would be great to be able to send emails from Vercel's edge runtime. Right now it errors due to the dependencies on axios.


DPL-960 Research - RT #790511, 790785  Cancel or Fail plates on the LILYS-96 Stock and  LBSN-96 Lysate plate purposes

User story
As R&D (Abdul T/Scott T) we would like the ability to ‘fail’ samples on LILYS-96 Stock and  LBSN-96 Lysate plates within the BIOSCAN non-destructive extraction pipeline in order to identify when samples have been lost or contaminated.
Who are the primary contacts for this story
Scott T (R&D)
Abdul T (R&D)
Emma B (R&D)
Who is the nominated tester for UAT
Scott T (R&D)
Abdul T (R&D)
Emma B (R&D)
Acceptance criteria
To be considered successful the solution must allow:
From RT https://rt.sanger.ac.uk/Ticket/Display.html?id=790511
Allow the following actions to be carried out on the LILYS-96 Stock and  LBSN-96 Lysate plate purposes:

[ ] Cancel plate
Prevent further work on this labware only
E.g. plate was dropped, lost, or is no longer required.
[ ] Fail plate
Mark this labware as failed and fail the associated library requests
[ ] Fail individual samples
Mark one or more wells as failed and fail the associated library requests

From RT https://rt.sanger.ac.uk/Ticket/Display.html?id=790785

Clearly indicate to the user that the first action for a LILYS-96 Stock plate is Beckman LILYS-96 Stock Preparation
Ideally, only this option would be presented to the user, with the second robot step only being displayed in the UI after the LILYS 96 Stock Preparation step has been completed.
Remove the requirement for the robot barcode selected in Beckman LILYS-96 Stock => LBSN-96 Lysate to match Beckman LILYS-96 Stock Preparation.

Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

#<issue_no.>
sanger/#<issue_no.>

Additional context
From RT https://rt.sanger.ac.uk/Ticket/Display.html?id=790511
This is a high-priority feature request for the BIOSCAN faculty and R&D teams
In the BIOSCAN non-destructive extraction there are two robot steps at which samples can be lost or contaminated:
Beckman LILYS-96 Stock Preparation
Beckman LILYS-96 Stock => LBSN-96 Lysate
During these steps, there is a risk that the specimen will be lost (dropped, aspirated into the tip, stuck to outside of tip, etc.).
During the transfer step, the lysed material which has been transferred to the Lysate plate can proceed to library prep as normal (as it contains DNA), but as the insect specimen is no longer present in the LILYS plate, no further extraction is possible, so new child samples should be prevented from being created.
Definitions according to R&D’s understanding while writing this story:
Cancel will prevent further work from being performed on this labware only. It will not cancel the associated library requests. You will be able to return to an earlier plate in the process, and continue work.
Fail will mark this labware as failed and will fail the associated library requests. This decision is not reversible and will prevent any further work being carried out on parent plates. Note: This action will also remove all downstream aliquots unless there is a sequencing batch downstream already.
From RT https://rt.sanger.ac.uk/Ticket/Display.html?id=790785
Currently, both robot steps that are possible to perform on the LILYS-96 Stock plate in the BIOSCAN non-destructive extraction are presented to the user regardless of the state of that plate.
This has caused some confusion during training and has resulted in some errors. If possible, we would like to simplify the information presented on-screen to de-risk the process and reduce the number of issues that need to be resolved.
A detailed discussion of when this issue was first raised is recorded in Slack in the Bioscan channel in a thread started on Thursday 5 October.
It should be noted that the root cause for this particular issue was a typo, resulting in non-matching robot barcodes but the wider discussions are still largely relevant.

@andrewsparkes created the common Research story for https://rt.sanger.ac.uk/Ticket/Display.html?id=790785 and https://rt.sanger.ac.uk/Ticket/Display.html?id=790511.
I have not created the actual implementation story as I believe the research story may lead to multiple small stories.
Please could you help review and update the story as applicable.

To remove the connection that both bed verifications happen on the same robot: very small effort - change 'verify_robot' flag to 'require_robot' in bed verification Beckman LILYS-96 Stock => LBSN-96 Lysate
For ordering the two bed verifications it would be good if we could have the LILYS plate transition through 2 states, the first so we can show just the first bed verification, which transitions the plate to state 2, which is the start point for the second bed verification. The complication here is the LILYS plate is already in the 'passed' state at the beginning, there is no state to transition it into.
To try: can we create the LILYS plate in the 'pending' state, and transition it to the 'started' rather than 'passed' state on creation of the submission? what controls that?

@SujitDey2022 In the course of researching this story we've figured out the code solution so may as well treat this as the implementation story as well. Have linked the Sequencescape and Limber pull requests to this story and put forward to code review.
(solution developed with much help from Katy and Abdullah, thx to them)

From Scott T.
Faculty were happy to drop the request to fail individual samples on LILYS-96 Stock and LBSN-96 Lysate plates due to the low incidence. We have had 38 samples that have ‘failed’ at this stage out of approximately 160,000 samples. Faculty are happy to track this level of loss via other less reportable means.
The proposed implementation of removing sample information from the UMI file would have caused issues for certain analyses faculty use, as they are reliant on each plate having a consistent number of samples present.
Querying whether the remaining features to cancel and fail plates are required.

Further correspondence from Scott T:
Even though it hasn’t happened yet, we would like some mechanism to prevent the LILYS and Lysate plates from progressing any further due to a plate-level issue (e.g. the plate has been dropped).
I have removed the acceptance criteria for failing/cancelling on individual samples.

@TWJW-SANGER @andrewsparkes @KatyTaylor
Moving this to Done based on the above comments.


Revert "fix(deps): bump webpack from 4.46.0 to 5.71.0"

Reverts shadrqen/petshop#123

Broke nuxt peer dependency


Checklist for "big" release

As discussed on the Discord channel, we are looking to release a big version next week.
Here's the checklist we have agreed upon:

[x] Create a better project's documentation and "Getting Started" guide
[ ] Provide great changelog in a form of React article

Things that we should mention in the changelog:

[ ] All breaking changes and the upgrade path that happened after the last release. Provide reasoning behind them
[ ] The future of the project, including the "v2" that we have been prototyping
[ ] Explicitly mention Discord group and invite everyone once again for collaboration!
[ ] Announce core meetings and link to the last one we had together (where we discussed the future of Rebolt)

It's mainly writing/documentation at this stage. There are a few more things to do to make the timing perfect.

Cross-posting from another PR:

[ ] Fix status page and add proper links there
[ ] Improve homepage with things we removed from Readme

Work on status page is currently blocked by: https://github.com/ocaml/odoc/issues/200
Will submit a PR with the homepage, getting started and all other guides from Rebolt tomorrow.
Aiming for the release this Wednesday.

Home page is finished, via #255

The changelog discussion, via #256

Decided we will talk about the future in a separate thread / article, once the initial version is released.

Ok, this is now ready and published under v0.10.0-rc.0. Waiting for final review and making it public. Woo!


Layout methods fix/235

Fix for https://github.com/lotus/lotus/issues/235
With this fix the view is able to call methods that defined on the layout

@tomkadwill I've just merged it, thank you. :+1:


Apply ES5-compatible trailing commas

Reconfigures Prettier to only apply trailing commas where they are supported (pre-Node v8).
Also, this adds a simple test to verify that there are at least no syntax errors. Longer term, we may or may not want to introduce unit tests (e.g. via Jest).
Fixes https://github.com/nicoduj/homebridge-harmony/issues/12.

thanks ! Concerning unit tests, yes, I was thinking of that in the long term, as well as some travis integration if possible.


cancelButton component

Hello. Can we pass custom component for CancelButton in future?

Closed via https://github.com/valerybugakov/react-native-custom-actionsheet/pull/4 by @luigivieira


Null-Anti-Null: Don't assume postPageFunctions are Some.

When generating post-page JavaScript, we were assuming that because our first
access of the post-page functions was non-empty, all of them would be. This led
to occasional .get-related NullPointerExceptions. We now allow for later calls
to the post-page functions to be None, and simply assume we have no more
functions to fetch once we get a None for them.
Fixess #1689 .

Once this guy gets passing, I'm going to go ahead and merge 'im.

Success!


hackathon blog

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ New Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 👷 Example Application
[ ] 🧑💻 Code Snippet
[ ] 🎨 Design
[ ] 📖 Content
[ ] 🧪 Tests
[ ] 🔖 Release
[ ] 🚩 Other

Description

This PR [adds/removes/fixes/replaces] this [feature/bug/etc].
Related Tickets & Documents

Resolves #
Mobile & Desktop Screenshots/Recordings

Added code snippets?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

No tests? Add a note

Added to documentation?

[ ] 📜 readme
[ ] 📜 contributing.md
[ ] 📓 general documentation
[ ] 🙅 no documentation needed

No docs? Add a note

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

I've been waiting to get a list of names for each team but haven't heard back yet. We can probably just publish this and update it later if I get a response.


The scaling for ' set resolution ' is buggy and creates weird shadows on the character ( not sure what name . .

Godot version:
Godot 3.2.3, latest version . .
OS/device including version:
Windows 10, nVidia 1050 GTX Ti . .
Issue description:
I want my game to run in 1280x720p, by default, render it in that resolution, then scale it, using the settings in project settings, under ' visuals ', stretch mode, here are . .

However, when I do that, something weird happens, for the shadows, when the monitor is running at, 4K, ie. it scales the original render, from 1280x720, to 4K, weird shadow lines . . .

I'm not sure what happens, I set it to render game first, in 1920x1080, which is exactly HALF, of 4K, so I would assume the problem didn't occur, when I did that, ie. there would be no dithering, or interpolation, however the same lines occur . . I THINK there's a bug in the up-scaling method, that causes these things, it shouldn't happen when scaling from Full HD, to 4K, since it simply means, each pixel becomes 4 pixels, and should look the same, as the 1080p image . . It looks a bit weird, for my games, I was wondering if it was a bug, again not sure . . .
Steps to reproduce:
Make a 3D game, set resolution to 1280x720p, and play it with settings above, on a 4K monitor, same problem, for 1080p, where there is no scaling issues, ie. one simply needs to make 1 pixel, fit inside 4 pixels, for scaling to work, or so . . It looks a BIT ugly, so I hope it might be fixed, with a better scaling algorhitm <3
Minimal reproduction project:
Uhhmm, see images above, not sure how to upload it . .
Link, to exported example game, 30 mb . . .
https://1drv.ms/u/s!Ar-BMFbxklUbhEucwWBvon4dmi3E?e=t2rwGO

Add: Tried setting my monitor to resolution, of 720p, then playing game . . The same thing happens, the shadows look weird, or dithered, instead of smooth, when I look in the game engine window, before pressing ' run scene ', even at 4K, it looks like the shadows are made of ' small dots ', instead of a smooth curve, not sure . . . .

Use the 2d stretch mode if you don't want the viewport to be scaled.

Thanks . . <3


Fairyfloss for JetBrains Editor

Hello, have you ever thought about doing a FairyFlos Theme for JetBrains editors?
Would be awesome!

I've thought about it. I kind of got used to stuff that's darker like Calamity
https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/screenshots/calamity.png
https://github.com/Pustur/calamity-vscode


Use render function instead of template for compatibility with runtime-only build of Vue.

Right now, if you run vue-highcharts in the runtime-only build of Vue (which seems to be the default, at least in a vue-cli project) it raises an error saying that the template option is unsupported if you're using a build without the template compiler included.
Since the template just created a container <div>, I figured it would be easy enough to just swap it with a trivial render function. I've tried installing this build in my project, and it seems to work -- the tests also pass.

Thanks for your PR.

Oh, I just realized that Vue 1.x doesn't support render function.


[docs] Create "Debugging Release Builds" guide, consolidate existing pages

Replaces the symbolication and sourcemaps pages with a new "Debugging Release Builds" guide, now located under Debugging. This minimally describes how to enable source maps and symbolicate release builds. Code references have been updated.
/docs/sourcemaps and /docs/symbolication are redirected to the new page.

Thanks for updating the guides! 🙏 New content looks really nice, just have  one nit about redirect.
Currently we use the static, serve side redirects for most of the moved pages:

https://github.com/facebook/react-native-website/blob/8fc23770911514fc8bad2b99c2015e5cca28353b/website/static/_redirects#L3

If there is no strong reason why to use client side approach in those cases, we probably should stick to the solution above.

@Simek Thanks, was hoping we had something like that. Updated


Do not push updates to deployments-k8s if cmd-* has been not changed binary

Issue
cmd-* repos push updates into deployments-k8s repo even if they haven't changed binary.
Actual: NSMBot always update deployments-k8s repo
Expected: Do not update deployments-k8s repo if the change doesn't change behaviour of the application.
Solution
Compare the new version with the latest version from networkservicemeshci  on docker-push and do not push new version if there no binary changes.

This is very interesting... how would we do the comparison?


Refactor test settings files

After implementing #691 and #1168 there will most likely be no need for this anymore, since we should be able to run iRODS & Taskflow tests in CI without any issues.
It is still possible some different values are expected for local vs CI testing, so this has to be evaluated once #1168 is done.
Edit: Current plan is as follows. test.py should be the primary settings file for testing locally. IF alternate settings are needed for CI, add a separate test_ci.py file.

Done.


feat: add translate button to footer

Fixes #333
Translations doesn't work right now because we haven't integrated weblate.

@mariobehling


[bug] Door sensor has not value in payload

Version
Build/Run method

[x] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.2.3
Describe the bug
I have Vision Security Recessed Door Window Sensor (ZD2105) that has command class 113 with 26-113-0-Access Control-Door state and 26-113-0-Home Security-Cover status. The mqtt payload for both of these have no value field. Here's an example:
{
  "id": "26-113-0-Access Control-Door state",
  "nodeId": 26,
  "commandClass": 113,
  "commandClassName": "Notification",
  "endpoint": 0,
  "property": "Access Control",
  "propertyName": "Access Control",
  "propertyKey": "Door state",
  "type": "number",
  "readable": true,
  "writeable": false,
  "label": "Door state",
  "genre": "system",
  "min": 0,
  "max": 255,
  "list": true,
  "states": [
    {
      "text": "Window/door is open",
      "value": 22
    },
    {
      "text": "Window/door is closed",
      "value": 23
    }
  ],
  "lastUpdate":<PHONE_NUMBER>699
}

Without the value it won't report when the sensor is triggered.
Expected behavior
The payload should have a value key/field that reports a value from the states list field. So in this case the value of the value field would be either 0, 22, or 23.

@AlCalzone ?

@chilicheech Could you show us some logs

Can't say anything without logs.

Apologies, here's the log:
zwave-1.log
We're looking at Node 026.

I believe the config for this device is https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0109/zd2105.json
The OZW config file is: https://github.com/OpenZWave/open-zwave/blob/master/config/vision/zd2105us5.xml ... This config file is set to read the Basic CC.
That's all the debugging I could come up with 😄

I took a glance at the device manual - not much information in there. The device cannot be configured so it is not a configuration issue. Seems like it does send Basic CC instead. 🤷🏻♂

I think you're right. And I think that's why the ozw config file has a provision to make ozw look at the Basic CC instead: https://github.com/OpenZWave/open-zwave/blob/master/config/vision/zd2105us5.xml#L31

SetAsReport is used to treat BasicSet as BasicReport. Without this, the command would be ignored entirely. zwave-js does that automatically for BasicSets, or you wouldn't even get the value change.

ah, gotcha, thanks for the clarification 😄  .. what do you think we can do to make this device work with zjs?

Do you not see the values of the Basic CC? Since it supports no actuator CCs, you should.
@robertsLando or are you filtering out Basic CC in the dashboard?

Ok, I do see the Basic CC being reported in the dashboard as 26-32-0-currentValue. I'm finally starting to understand how to read the logs and values. I think the issue now is on the zjs2m side to get the hass discovery fixed for that device.
Thanks so much for your help 😄

Ok, I do see the Basic CC being reported in the dashboard as 26-32-0-currentValue. I'm finally starting to understand how to read the logs and values. I think the issue now is on the zjs2m side to get the hass discovery fixed for that device.

I don't provide an hass discovery for CC basic. You need to tell me how do you expect that to work

ok, I'm going to reopen this issue because I just tested with z2m/ozw and the sensor does report using the correct CCs:
Door Open:

Door Closed:

I'm gonna see what I can find in the logs.

@AlCalzone It could be that ozw reports basic CC values by using notification CC (by default) ?

Lokk at this: https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/command_classes/Basic.cpp#L230

Here are some z2m logs:
z2m      | 2020-12-03T16:35:14.692694168Z   z2m:Zwave zwave node 26: changed: 32-1-0:Basic:0 -> 255 +3s
z2m      | 2020-12-03T16:35:14.800588157Z   z2m:Zwave zwave node 26: changed: 113-1-6:Access Control:Door/Window Closed -> Door/Window Open +108ms
z2m      | 2020-12-03T16:35:19.818178057Z   z2m:Zwave zwave node 26: changed: 32-1-0:Basic:255 -> 0 +5s
z2m      | 2020-12-03T16:35:19.926573713Z   z2m:Zwave zwave node 26: changed: 113-1-6:Access Control:Door/Window Open -> Door/Window Closed +108ms

Essentially the label comes from: https://github.com/OpenZWave/open-zwave/blob/master/config/Localization.xml#L84

I wonder if OZW polls the Notification values when it receives a Basic CC report.

@chilicheech If you check the link on my previous comment seems it trigger a notification event, dunno then where it goes but seems that event will generete the notification you see there

Here's some more z2m with ozw logs:
Door Open:
z2m      | 2020-12-03T16:50:09.383442480Z 2020-12-03 08:50:09.380 Detail, Node026,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1a, 0x03, 0x20, 0x01, 0xff, 0x35
z2m      | 2020-12-03T16:50:09.383779304Z 2020-12-03 08:50:09.381 Detail,
z2m      | 2020-12-03T16:50:09.383922012Z 2020-12-03 08:50:09.381 Info, Node026, Received Basic set from node 26: level=255. Treating it as a Basic report.
z2m      | 2020-12-03T16:50:09.384041543Z 2020-12-03 08:50:09.381 Detail, Node026, Initial read of value
z2m      | 2020-12-03T16:50:09.384162220Z 2020-12-03 08:50:09.382 Detail, Node026, Notification: ValueChanged CC: COMMAND_CLASS_BASIC Instance: 1 Index: 0
z2m      | 2020-12-03T16:50:09.390081910Z   z2m:Zwave zwave node 26: changed: 32-1-0:Basic:0 -> 255 +8s
z2m      | 2020-12-03T16:50:09.491934972Z 2020-12-03 08:50:09.488 Detail, Node026,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1a, 0x0a, 0x71, 0x05, 0x06, 0xff, 0x00, 0xff, 0x06, 0x16, 0x00, 0x00, 0x99
z2m      | 2020-12-03T16:50:09.492243670Z 2020-12-03 08:50:09.488 Detail,
z2m      | 2020-12-03T16:50:09.492390962Z 2020-12-03 08:50:09.489 Info, Node026, Got a AlarmCmd_Report Message....
z2m      | 2020-12-03T16:50:09.492514920Z 2020-12-03 08:50:09.489 Info, Node026, Received Notification report (>v1): Type: Access Control (6) Event: Door/Window Open (22) Status: true, Param Length: 0
z2m      | 2020-12-03T16:50:09.493149191Z 2020-12-03 08:50:09.489 Detail, Node026, Initial read of value
z2m      | 2020-12-03T16:50:09.493408202Z 2020-12-03 08:50:09.490 Detail, Node026, Notification: ValueChanged CC: COMMAND_CLASS_NOTIFICATION Instance: 1 Index: 6
z2m      | 2020-12-03T16:50:09.498607579Z   z2m:Zwave zwave node 26: changed: 113-1-6:Access Control:Door/Window Closed -> Door/Window Open +108ms

Door Closed:
z2m      | 2020-12-03T16:50:13.220332198Z 2020-12-03 08:50:13.217 Detail, Node026,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1a, 0x03, 0x20, 0x01, 0x00, 0xca
z2m      | 2020-12-03T16:50:13.220652771Z 2020-12-03 08:50:13.218 Detail,
z2m      | 2020-12-03T16:50:13.220823917Z 2020-12-03 08:50:13.218 Info, Node026, Received Basic set from node 26: level=0. Treating it as a Basic report.
z2m      | 2020-12-03T16:50:13.221152042Z 2020-12-03 08:50:13.218 Detail, Node026, Value Updated: old value=255, new value=0, type=byte
z2m      | 2020-12-03T16:50:13.221307771Z 2020-12-03 08:50:13.219 Detail, Node026, Changes to this value are not verified
z2m      | 2020-12-03T16:50:13.221460636Z 2020-12-03 08:50:13.219 Detail, Node026, Notification: ValueChanged CC: COMMAND_CLASS_BASIC Instance: 1 Index: 0
z2m      | 2020-12-03T16:50:13.227106680Z   z2m:Zwave zwave node 26: changed: 32-1-0:Basic:255 -> 0 +3s
z2m      | 2020-12-03T16:50:13.328079325Z 2020-12-03 08:50:13.325 Detail, Node026,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1a, 0x0a, 0x71, 0x05, 0x06, 0x00, 0x00, 0xff, 0x06, 0x17, 0x00, 0x00, 0x67
z2m      | 2020-12-03T16:50:13.328318700Z 2020-12-03 08:50:13.325 Detail,
z2m      | 2020-12-03T16:50:13.328422606Z 2020-12-03 08:50:13.326 Info, Node026, Got a AlarmCmd_Report Message....
z2m      | 2020-12-03T16:50:13.328514325Z 2020-12-03 08:50:13.326 Info, Node026, Received Notification report (>v1): Type: Access Control (6) Event: Door/Window Closed (23) Status: true, Param Length: 0
z2m      | 2020-12-03T16:50:13.328609012Z 2020-12-03 08:50:13.326 Detail, Node026, Value Updated: old value=1, new value=2, type=list
z2m      | 2020-12-03T16:50:13.328710210Z 2020-12-03 08:50:13.326 Detail, Node026, Changes to this value are not verified
z2m      | 2020-12-03T16:50:13.328811304Z 2020-12-03 08:50:13.326 Detail, Node026, Notification: ValueChanged CC: COMMAND_CLASS_NOTIFICATION Instance: 1 Index: 6
z2m      | 2020-12-03T16:50:13.332925316Z   z2m:Zwave zwave node 26: changed: 113-1-6:Access Control:Door/Window Open -> Door/Window Closed +107ms

@chilicheech Yep seems ozw is mapping basic reports to notifications

If this helps, here's the mqtt payload for z2m's 26-113-1-6:
{
  "value_id": "26-113-1-6",
  "node_id": 26,
  "class_id": 113,
  "type": "list",
  "genre": "user",
  "instance": 1,
  "index": 6,
  "label": "Access Control",
  "units": "",
  "help": "Access Control Alerts",
  "read_only": true,
  "write_only": false,
  "min": 0,
  "max": 0,
  "is_polled": false,
  "values": [
    "Clear",
    "Door/Window Open",
    "Door/Window Closed"
  ],
  "value": "Door/Window Closed",
  "lastUpdate":<PHONE_NUMBER>332
}

As you can see it does have a value key in this case.

Look at this: https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/command_classes/Basic.cpp#L230

In the OZW world, Notification does not refer to the Notification CC (they still call it Alarm CC, how it was named in V1 and V2). Instead a "notification" is an event like ValueAdded.
I can't seem to find any code that triggers a Notification_Get after a Basic_Report is received. Nor does the config file contain any mapping.
Looking at the logs, it looks like the device actually does send notifications 🤷🏻♂ 100ms after the Basic Set seems a bit short for polling.

Something is off with the logs though. I can't see some things that should be in there.

@chilicheech can you upgrade to the current zwave-js master branch please? Just to exclude that we're hunting ghosts here.

Sure thing. I'll do that as soon as I can.

K, so I'm using zjs2m from master and zjs from master. I started everything up, waited until the interview completed, then opened and closed the door. Here's something interesting in the logs:
                      └─[BasicCCSet]
                          target value: 255
16:10:04.322 CNTRLR   [Node 026] treating BasicCC Set as a report
16:10:04.325 CNTRLR   [Node 026] [~] [Basic] currentValue: 0 => 255                     [Endpoint 0]
16:10:04.387 SERIAL « 0x01100004001a0a710506ff00ff0616000099                              (18 bytes)
16:10:04.395 SERIAL » [ACK]                                                                   (0x06)
16:10:04.401 DRIVER « [Node 026] [REQ] [ApplicationCommand]
                      └─[NotificationCCReport]
                          V1 alarm type:  6
                          V1 alarm level: 255
16:10:04.416 CNTRLR « [Node 026] received unsupported notification {
                          "nodeId": 26,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 6,
                          "alarmLevel": 255
                      }
16:10:09.075 SERIAL « 0x01090004001a03200100ca                                            (11 bytes)
16:10:09.079 SERIAL » [ACK]                                                                   (0x06)
16:10:09.083 DRIVER « [Node 026] [REQ] [ApplicationCommand]
                      └─[BasicCCSet]
                          target value: 0
16:10:09.091 CNTRLR   [Node 026] treating BasicCC Set as a report
16:10:09.094 CNTRLR   [Node 026] [~] [Basic] currentValue: 255 => 0                     [Endpoint 0]
16:10:09.183 SERIAL « 0x01100004001a0a7105060000ff0617000067                              (18 bytes)
16:10:09.187 SERIAL » [ACK]                                                                   (0x06)
16:10:09.193 DRIVER « [Node 026] [REQ] [ApplicationCommand]
                      └─[NotificationCCReport]
                          V1 alarm type:  6
                          V1 alarm level: 0
16:10:09.202 CNTRLR « [Node 026] received unsupported notification {
                          "nodeId": 26,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 6,
                          "alarmLevel": 0
                      }

It says received unsupported notification. I believe the notification with alarm type and alarm level might be an older version of the Notification CC or even an Alarm CC??

So, my multi sensor is doing the same thing. The air temperature, the humidity, and the illuminance get reported correctly. But the motion isn't reporting correctly and i'm seeing the same behavior as the door lock in the logs:
16:20:29.565 DRIVER « [Node 024] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[NotificationCCReport]
                            V1 alarm type:  7
                            V1 alarm level: 255
16:20:29.572 CNTRLR « [Node 024] received unsupported notification {
                          "nodeId": 24,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 7,
                          "alarmLevel": 255
                      }

And the same thing from my other multi sensor by a different manufacturer:
16:22:55.780 DRIVER « [Node 023] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[NotificationCCReport]
                            V1 alarm type:  7
                            V1 alarm level: 255
16:22:55.787 CNTRLR « [Node 023] received unsupported notification {
                          "nodeId": 23,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 7,
                          "alarmLevel": 255
                      }

Here's the full log if it helps:
zwave-1.log

Cool, that's something I can work with.

@AlCalzone Just for reference, could we create a more specific related issue for this? (or change the name of this issue based on the feat/bug to fix)


Add 'ddev composer' command, closes #1131

The Problem/Issue/Bug:
#1131
How this PR Solves The Problem:
Adds a ddev composer command, allowing for seamless use of composer within the context of the container. Specific support has been added for ddev composer create-project, installing the project into /tmp/composer and moving the resulting project into the app root when complete.
Manual Testing Instructions:

Execute composer commands with ddev composer
Create projects using ddev composer create-project
Test create-project args and flags: one argument should be interpreted as the package, two should be interpreted as the package and the installation directory, and three should be interpreted as the package, installation directory, and the version
Test something like ddev composer create-project --no-dev -v typo3/cms-base-distribution myproj ^8 and ensure it installs successfully to ${APP_ROOT}/myproj
Test other composer commands with and without flags, like: ddev composer require --quiet twitter/bootstrap and confirm that commands behave as if arguments are passed directly to composer

Note: ddev will make no effort to parse any flags provided to it, they will instead be passed to composer.
Automated Testing Overview:
composer_test.go has been added to test ddev composer and ddev composer create-project commands.
Related Issue Link(s):
#1131
Release/Deployment notes:

Taking this for a quick spin, reminded me of https://github.com/drud/ddev/issues/1027 - Shared composer cache. We may want to add that to this release.

I took this for a quick spin and things seemed to work out just fine! Haven't looked at the code at all but was just eager to take it for a spin.
mkdir junk
cd junk
ddev config --projecttype=php
ddev start
# This composer create-project is better example, builds in project dir, and v9
ddev composer create-project --no-dev -v typo3/cms-base-distribution . ^9

# composer require fails
ddev composer require typo3-ter/static-info-tables
Using version ^6.7 for typo3-ter/static-info-tables
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 74 installs, 0 updates, 0 removals

  [RuntimeException]
  /vendor does not exist and could not be created.

require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] [<packages>]...

The create-project went great, but the composer require apparently didn't execute in the expected directory (/var/www/html in this case)

Right, the example given was more to showcase version selection and that this now supported non-cwd installations. I'm having trouble recreating that issue you ran into given the commands you ran:
mkdir junk
cd junk
ddev start
ddev composer create-project --no-dev -v typo3/cms-base-distribution . ^9
ddev composer require typo3-ter/static-info-tables

Each of the above completed successfully. Can you confirm that after a ddev rm -a?
#1027 will bring a ton of efficiency and greatly speed things up, but I think that should be its own PR.

I can't recreate the ddev composer require failure with current, yay.
However, ddev composer update --dev fails. as does ddev composer update --no-dev and ddev composer require --no-dev monolog/monolog
I imagine that's because you haven't figured out how to get cobra to be gentle on flags it doesn't understand.

I believe this one's ready for review.
Spinoff issues that I'd like to add to improve this in the next release:

Improving the create-project flow to be less cumbersome and (maybe?) even handle some config interactivity if no config currently exists,
Sharing the composer cache between projects

There's a problem with our Drupal example.
ddev composer create-project drupal-composer/drupal-project:8.x-dev . --stability dev --no-interaction somehow gets the args moved around to Executing composer command: composer create-project --stability --no-interaction drupal-composer/drupal-project:8.x-dev /tmp/composer dev (see dev at end).
The result is
  [Symfony\Component\Console\Exception\RuntimeException]
  The "--stability" option requires a value.

Yikes, that's some complicated parsing, but I'll admit what's being done to intercept args and put them where they need to be is perhaps overly naive and trying to do too much. I see two ways of addressing this:

Lock down argument positions further, forcing flags to come before package/version and not allowing arbitrary directories,
Recreating Composer's flag parsing set to ensure all possible flags get put where they need to be

The second option would be preferable for a 1:1 recreation of the composer create-project user experience, but that's a lot to ask. The first option can be communicated through usage text and effective documentation, but will likely confuse users and prevent them from running commands how they're used to.

I would be in favor of using our own create, maybe renaming it to make it so it's clearly not transparent pass-through? And providing our own args/flags that work with it.  That way we're in control. And people who need to do something else can do it the old fashioned way.

Another anomaly that needs to be discussed and/or documented: "ddev composer xxx" seems to only work in the default working directory, whereas composer install and friends normally work in the current directory.

This has been rebased, doc updates made, and a quick fix to ddev composer to ensure we're working in the app root.

@cweagans we should have asked for your comment already on the minimal list of flags we're supporting for the ddev composer create command. Currently
Flags:
      --dev                Pass the --dev flag to composer create-project
  -h, --help               help for create
      --no-dev             Pass the --no-dev flag to composer create-projet
      --stability string   Pass the --stability <arg> option to composer create-project

but we'll add --no-interaction
Thoughts? We want to limit the flags we pass through to composer create-project for maintainability.

I would recommend allowing users to specify extra flags to pass (--extra-composer-args="" or something). People use Composer in all kinds of funky ways, and someone is inevitably going to want something that isn't provided there. Composer could also add a flag someday and we shouldn't make people wait to be able to use it IMO.

It looks like something is not quite copacetic with args. I guess the version spec must be optional?
$ ddev composer create drupal-composer/drupal-project:8.x-dev --stability dev --no-interaction
Error: accepts 2 arg(s), received 1
Usage:
  ddev composer create [flags] <package> <version>

Yup, ddev composer create drupal-composer/drupal-project:8.x-dev --stability dev --no-interaction ^8 works. So version spec must be optional.

The version argument is now optional, so usage will be:
ddev composer create [flags] <package> [<version>]
Tested with TYPO3 and D8 with and without version specifications, --no-interaction, and other flags.


fix: fail to update material source

Closed: #826

Codecov Report

Merging #921 (9f762e3) into release/1.3.1 (0e2a21c) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/1.3.1     #921   +/-   ##
==============================================
  Coverage          57.14%   57.14%
==============================================
  Files                  1        1
  Lines                 70       70
  Branches              15       15
==============================================
  Hits                  40       40
  Misses                30       30

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 0e2a21c...9f762e3. Read the comment docs.


MEDIA_ERR_SRC_NOT_SUPPORTED when updating source

Hello, I have an issue when updating source on initialized player object. Sample code
            window.player.src({
                type : type,
                src: val.src,
                keySystemOptions: [
                    {
                        name: 'com.widevine.alpha',
                        options: {
                            licenseUrl: widevine_la_url
                        }
                    },
                    {
                        name: 'com.microsoft.playready',
                        options: {
                            licenseUrl: playready_la_url
                        }
                    }
                ]
            });

This results in the following error:

VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) The media could not be loaded, either because the server or network failed or because the format is not supported

Plugin version 2.1.0

+1

This error should be fixed with 2.2.0 (released yesterday). I believe the issue stems from this plugin manually clearing the video element source between src() calls which is no longer needed with dash.js 2.0.

I have updated dash.js to v2.1.1 and videojs-dash to 2.2.0. I'm having the same issue. And there is another issue as well. Video plays for a while then stops. Chunks stop downloading. Stream is live, and I'm fetching it from Wowza version 4.4.1.

Do you have this issue when running the stream through the dash.js reference player? http://dashif.org/reference/players/javascript/v2.1.1/samples/dash-if-reference-player/index.html

It works with dash.js reference player, but it could mean that it works on older version. Also, I'm testing on the latest stable version of Chrome.

Would you be able to post a sample player for debugging?

I'll try to configure public example.

I've set up a public example with debug versions of videojs-dash, dash.js and video.js here http://cavar.pw/videojs/

I believe https://github.com/videojs/videojs-contrib-dash/pull/79 will fix this issue

Now released as version 2.3.0

Great, thank you. There is still an issue of not refreshing live source, but I'll create an another issue. Closing this one down.


Full restructure of ViewModel, implemented visualization of all algorithms, implemented Force-Directed Vizualisation algorithm

File restructure of view
Move common gui components like buttons to general functions
Full Restructure ViewModel: edges now belongs to VertexViewModel, not just general list of all edges
Implemented force-directed visualization algorithm
Add buttons and methods for visuzalization all existing algorithms
Fixed edges weights and edges drawing, change EdgeVM fields to getters
Add reset edges drawing button and method

Поиск циклов немного некорректно работает, добавил тест


Better Documentation on CLI command switches

No where is there a list of switches to use with commands.  please add this for somedeity's-sake!  I am trying to weed through the google searches to find how to use cli to send to multiple groups and also include release notes.  But I would like see what all the -commands and the --commands are I can use when I do something like
appcenter distribute release --debug --app $APP_NAME -r "Not sure if this is release notes as it fails" --group "Tag: our-qa" --file and so on
Its ridiculous that you want us to use this CLI since API is going south but you don't have proper documentation of all the little switch commands.

Hi @grndvl1!
There's built-in help command, could you point us to what is missing?
appcenter distribute release --help

Upload release binary and trigger distribution, at least one of --store or --group must be specified

Usage: appcenter distribute release -f|--file <arg> [--mandatory] [--silent] [-R|--release-notes-file <arg>]
         [-r|--release-notes <arg>] [-s|--store <arg>] [-g|--group <arg>] [-n|--build-number <arg>]
         [-b|--build-version <arg>] [-a|--app <arg>]

Options:
    -f|--file <arg>                           Path to binary file
       --mandatory                            Make the release mandatory for the testers (default is false)
       --silent                               Do not notify testers of this release
    -R|--release-notes-file <arg>             Path to release notes file
    -r|--release-notes <arg>                  Release notes text
    -s|--store <arg>                          Store name
    -g|--group <arg>                          Distribution group name
    -n|--build-number <arg>                   Build number parameter required for macOS .pkg and .dmg files
    -b|--build-version <arg>                  Build version parameter required for .zip, .msi, .pkg and .dmg files
    -a|--app <arg>                            Specify app in the <ownerName>/<appName> format

Common Options (works on all commands):
       --disable-telemetry             Disable telemetry for this command
    -v|--version                       Display appcenter version
       --quiet                         Auto-confirm any prompts without waiting for input
    -h|--help                          Display help for current command
       --env <arg>                     Environment when using API token
       --token <arg>                   API token
       --output <arg>                  Output format: json
       --debug                         Display extra output for debugging

Hi @grndvl1!
There's built-in help command, could you point us to what is missing?
appcenter distribute release --help

Upload release binary and trigger distribution, at least one of --store or --group must be specified

Usage: appcenter distribute release -f|--file <arg> [--mandatory] [--silent] [-R|--release-notes-file <arg>]
         [-r|--release-notes <arg>] [-s|--store <arg>] [-g|--group <arg>] [-n|--build-number <arg>]
         [-b|--build-version <arg>] [-a|--app <arg>]

Options:
    -f|--file <arg>                           Path to binary file
       --mandatory                            Make the release mandatory for the testers (default is false)
       --silent                               Do not notify testers of this release
    -R|--release-notes-file <arg>             Path to release notes file
    -r|--release-notes <arg>                  Release notes text
    -s|--store <arg>                          Store name
    -g|--group <arg>                          Distribution group name
    -n|--build-number <arg>                   Build number parameter required for macOS .pkg and .dmg files
    -b|--build-version <arg>                  Build version parameter required for .zip, .msi, .pkg and .dmg files
    -a|--app <arg>                            Specify app in the <ownerName>/<appName> format

Common Options (works on all commands):
       --disable-telemetry             Disable telemetry for this command
    -v|--version                       Display appcenter version
       --quiet                         Auto-confirm any prompts without waiting for input
    -h|--help                          Display help for current command
       --env <arg>                     Environment when using API token
       --token <arg>                   API token
       --output <arg>                  Output format: json
       --debug                         Display extra output for debugging


HOCS-4235 replace jsonb_agg use for 40% speedup

Before:
Planning Time: 2.517 ms
Execution Time: 322.106 ms
(43 rows)
After:
Planning Time: 1.062 ms
Execution Time: 197.900 ms
(43 rows)


Passwords in URL fail on certain characters

Using password auth, I noticed that a clone would fail with a password containing #.  Wherever the failure is, it truncated the URL from<EMAIL_ADDRESS>to https://myuser/....  The resulting message from this says Failed to clone repository: Get https://myuser/info/refs?service=git-upload-pack: dial tcp: lookup myuser: no such host.
This happens before anything ever gets to PathEscape() in plumbing/transport/common.go.  There are other failures with varying messages that happen if the password contains %, /, and ^.  Because % gives an error, I can't pass in a pre-escaped string.

@scooterhanson Are you specifying user and password with BasicAuth or are you adding it to the endpoint URL directly? If it is the later case, you should escape the # character, which is just not valid in that case.

Using escaped user and passwords in URLs seems to work correctly: https://github.com/src-d/go-git/pull/968
I'm closing the issue, since it is expected that using an unescaped # in a password directly in the URL has this behavior. Feel free to post more details if I closed this incorrectly. Thanks.


Terraform initialized in an empty directory! but directory is not empty

Hi I have a directory as follows

I cd into it and run the docker command provided, I get

The directory is not empty. there is an initialized  TF project, so what might be missing? Thanks

@eliassal Are you running the Docker command in the directory where your Terraform files are in?
Since this repo hasn't been active for a while, I also published my own fork: https://github.com/Ianyliu/blast-radius-fork
Feel free to try it!
Docker command
docker run --rm -it -p 5000:5000 \
  -v $(pwd):/data:ro \
  --security-opt apparmor:unconfined \
  --cap-add=SYS_ADMIN \
  ianyliu/blast-radius-fork

Thanks for your help. I did visit your fork and followed your instructions by running
blast-radius --serve "C:\Projects\...........\Terraform - Full Course\weatherapi"
it runs then I choose Firefox, I get a page with python code as follows (not sure what should I do to have the image insttead of code)


Refactor names and comments for readability

Looks like we need to get coding convention.

CI failed. you should fix and re-request
IRCPP/srcs/Server.cpp:152:30

LGTM

what means KQUEUE_FD mhKqueue;?
member h..... Kqueue

@bentraxgel That means a "Handle". Just another name for "File Descriptor".


JVM Crash on TransformOps with equal sized, but differently oriented parameters

While trying out the example code from https://github.com/deeplearning4j/nd4j/issues/958 I've made a mistake and didn't change the result shape. This resulted in a JVM crash.
BaseTransformOp already has a check to make sure that both arrays have the same length, but it doesn't check the orientation.
The following code produces reliably a crash with an error dump:
package com.example;

import org.nd4j.linalg.api.ndarray.INDArray;
import org.nd4j.linalg.api.ops.impl.transforms.SoftMax;
import org.nd4j.linalg.api.ops.impl.transforms.SoftMaxDerivative;
import org.nd4j.linalg.factory.Nd4j;

public class App {

    public static void main(String[] args) {
        INDArray input1 = Nd4j.create(1000).transpose();
        INDArray input2 = Nd4j.zerosLike(input1);
        Nd4j.copy(input1, input2);
        INDArray output1 = Nd4j.create(1, 1000);
        Nd4j.getExecutioner().exec(new SoftMax(input1, output1));
        System.out.println("Softmax = " + output1);
        INDArray output2 = Nd4j.create(1,1000);
        Nd4j.getExecutioner().exec(new SoftMaxDerivative(input2, output2));
        System.out.println("Softmax Derivative = " + output2);
    }
}

Does this affect softmax only?

With current master it looks like it only happens on SoftMaxDerivative

So softmax derivative still crashes on current master. Looking into it.

Is CUDA affected?

Haven't looked into cuda

Ok, i've checked it's not affected.
sumNumber returns 1.0 for both outputs.

@raver119 🎉
Let me hunt down what it is in cpu.

Closing. Merged and fixed in current master. Throws an exception instead of a crash in all such cases.


Flip X or Y For Lua Sprites?

What is your question?
Is There a way of flip the x or y of the lua sprites like animated ones or static graphics?

setProperty('tag.flipX', true)

setProperty('tag.flipX', true)

bro I managed to make the lua text opacity using this method thank you so much

ty


handbrake: fix Darwin build

Motivation for this change
The handbrake build had broken under Darwin. This PR fixes it by

Omitting the numactl dependency under Darwin.
Preventing the configure script from checking for xcodebuild. This check always failed (because xcodebuild isn't available in the build context) but xcodebuild isn't actually needed for the build, which uses --disable-xcode.
Using the Nix-provided libxml2 under Darwin like we already do under Linux.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc @Anton-Latukha @wmertens

Interesting.
I previously talked to upstream developers about that xcode check, I even opened a report for it, they said that that check is optional.
Well, it is at least good to disable the check if it is not needed.
Does the present in file:
if stdenv.isDarwin then "--disable-xcode" else ""

works, or manual patching is indeed needed?
We can add --force into it if we really want.

It is great that you commented on the patches.
And it is also good to keep packages without manual regex patches.
As it frequently happens, the are some flags that upstream forgot to put in ./configure --help, but they are in make/configure.py.
If the  "--force --disable-xcode" does not work - then we should remove it and patch.

I am OK with all the other changes.
Thank you for them.
It is just good for Nixpkgs to avoid patching when sources can change down the line.

@Anton-Latukha I tried adding --force to the configure options when building under Darwin, but unfortunately the configure script still stopped when it couldn’t find xcodebuild.

Ok. Thank you.
I approve the pull request.
Please, as you can - open a proper upstream bug report with according technical information.

HandBrake 1.3.3 is out, I would submit PR 1.3.(2->3), there is only ver/hash change, so PRs are independently mergeable. The release has minor changes, there are no changes related to this PR.

The reason there is no report about the issue the PR addresses - probably because their CI can just fail "optional" build, and they provide a set of prebuild packages, and for macOS also, we may be the only one package managemnet system that assembles and compiles the project on macOS, if in 8 month nobody except us noticed.

@Anton-Latukha It’s difficult for me to test a separate PR for the version bump because the package doesn’t build at all for me (on Darwin) without the changes in this current PR.

No, man, I just notified you that I opened parallel PR, and that they can merge in parallel.
Because I am quite aware of how parallel PRs can create all sorts of stuff. and so I inform you that there is parallel PR, and they would merge, no rebases needed.
I wish I could merge your PR myself.

Oh, I’m sorry, I misunderstood. I thought you were saying that I should open a new PR 🙂
Maybe I will mention this PR and #90302 on the NixOS Discourse to get some more visibility.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/170

I hope your PR gets merged faster. You somehow receive a huge timeouts on PRs merges.

@danieldk
I see you merged active recently.
Two package maintainers reviewed, it, changes were discussed and made, and PR approved by two maintainer. We wait for someone to come around and merge this for some time.
Pinging, we close the https://github.com/NixOS/nixpkgs/issues/99317 report.

@GrahamcOfBorg build handbrake

@GrahamcOfBorg build handbrake

This is (once again) ready to be merged.

Thank you!


PythonOperator not support snowflake dataset urn

Describe the bug
PythonOperator not support snowflake dataset urn when there is only outlets in conf
To Reproduce
Steps to reproduce the behavior:

This is my airflow dag:

from datetime import timedelta

from airflow import DAG
from airflow.utils.dates import days_ago

try:
    from airflow.operators.bash import BashOperator
except ModuleNotFoundError:
    from airflow.operators.bash_operator import BashOperator

from datahub_provider.entities import Dataset
# python op
from airflow.operators.python_operator import PythonOperator
default_args = {
    "owner": "airflow",
    "depends_on_past": False,
    "email"<EMAIL_ADDRESS>    "email_on_failure": False,
    "execution_timeout": timedelta(minutes=5),
}

def my_func():
   print('python done!')
with DAG(
    "datahub_test01",
    default_args=default_args,
    description="iiiiiiAn example DAG demonstrating the usage of DataHub's Airflow lineage backend.",
    schedule_interval=timedelta(days=1),
    start_date=days_ago(2),
    tags=["example_tag"],
    catchup=False,
) as dag:
    task_python = PythonOperator(
     task_id = 'first_python_task',
     python_callable=my_func,
     dag=dag,
     outlets={"datasets": [Dataset("snowflake", "mydb.schema.tableF")]},
     )
    task_python

2.After  I run my dag, the airflow log is:
[2022-06-29 11:05:57,717] {logging_mixin.py:109} INFO - Exception: Traceback (most recent call last):
File "/home/airflow/.local/lib/python3.8/site-packages/datahub_airflow_plugin/datahub_plugin.py", line 336, in custom_on_success_callback
datahub_on_success_callback(context)
File "/home/airflow/.local/lib/python3.8/site-packages/datahub_airflow_plugin/datahub_plugin.py", line 220, in datahub_on_success_callback
datajob.outlets.append(outlet.urn)
AttributeError: 'dict' object has no attribute 'urn'
Expected behavior
The meta info in datahub is empty.
Screenshots
None
Desktop (please complete the following information):

OS: Mac
Browser  chrome
Version 22

Additional context
Add any other context about the problem here.

same here with PythonOperator + outlets={"datasets": [Dataset("dbt", f"{database_name}.{schema_name}.{model_name}")]},

@gvillafanetapia @AprilJoy We need to update our docs because the correct way to set outlets is the following:
https://github.com/datahub-project/datahub/blob/ae577ddff24d6ac0db84fe6844590cd154c81f59/metadata-ingestion/examples/airflow/circuit_breaker/long_tail_companion/01-operation/ecommerce/01_snowflake_load.py#L35
Basically you don't need the datasets object and it should look like this:
     outlets=[Dataset("snowflake", "mydb.schema.tableF")],
     )

I update the examples in this pr -> https://github.com/datahub-project/datahub/pull/5696/files

The issue was because of an incorrect example provided. The example has been fixed now in the above PR. Closing.


Settings allowJs=true in tsconfigs will make debugger step in the javascript files instead of the typescript files.

Issue Type: Bug

Setup a typescript project
Set allowJS = true in the tsconfigs
Setup launch.json to debug typescript
Put a breakpoint in a typescript file
Run

The debugger will stop on the breakpoint, but not in the TypeScript file, it's gonna stop in the corresponding JavaScript file generated by the tsc command.
Please see this stackoverflow question for more details.
https://stackoverflow.com/questions/62763392/debugging-typescript-in-vs-code-steps-into-javascript-instead
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.18363

This behaviour does not occur in Webstorm.

I'm not able to repro this, can you collect a log file?
/jsDebugLogs

It's been a while, let me see if I can reproduce it.

Ok... got it to reproduce quite easily actually.

Here's the contents of the log file and a sample project in a zip file that makes the bug happen on my machine.
To run the project, first run npm install, then the tsc and finally, use the Launch Program config to debug is VS Code.
debugadapter-legacy.txt
vs-code-breakpoint-bug.zip
Version info:
Version: 1.46.1 (user setup)
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:13:20.174Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

Thanks for the followup! I noticed you're on an old version of VS Code; can you update to VS Code 1.47 or above? (Preferably to the latest 1.50). In 1.47 we switched to an entirely new debugger which may no longer have this issue.

Yes VS Code just updated itself. The is still happening in v1.50.1.
Do you want me to regenerate the logs from that version?
Version: 1.50.1 (user setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041

Please do 🙂

I see what's happening. A small handful people have run into this before. This is because of a behavior that, if you set your program to a non-.js file and we find valid sourcemaps referencing it in the outfiles, we'll actually execute the compiled version. This behavior is present because beginners often try to run their .ts files, and it's easy for us to fix that for them.
So we fix this, but keep the args. So although we're running dist/app.js, we still run it through ts-node. ts-node replaces the sourcemap in dist/app.js with a runtime/ephemeral sourcemap that maps its re-compiled version of app.js back to itself, replacing the correct sourcemap.
tl;dr you can do either of two things:

Set outFiles to an empty array so that sourcemaps are not discovered
Either drop ts-node and debug compiled files, or use ts-node without manually compiling them


Brain loading timing issue

Hi,
I was trying to add some user's information to the brain when hubot-xmpp receives presence messages. However, my setup uses redis-brain and there is a timming issue with the redis initial brain load.
The problem is that hubot-xmpp receives presence informations and stores that information into the brain before redis-brain load the initial brain content. When redis finally load the data, it "merges" the data into the brain. That actually override everything in the "users" key without further notice.
I looked at both redis-brain and hubot code and I don't see any easy way to solve that. It seems to me that the brain should be loaded before the adapters are started but I would like to fetch some advices before I attempt to patch/submit a pull request.
One possible solution would be to force brain implementation to extend the Brain class and add a switch to the hubot startup to specify the brain to use. This would be similar to the adapter. However, this seems pretty invasive and imply that you can't have two concurrent brain backend loaded at the same time (which is not necessarily a bad thing when you consider that loading data from two brain is not really supported anyway)
Any idea?

I'm having a similar issue with the hubot-slack adapter and redis-brain.
Basically, on server start, the hubot-slack adapter connects and fills robot.brain.data.users with data, but then that gets overwritten because redis-brain connects after the adapter.
I've attempted to purge redis of keys and it still overwrites the contents of robot.brain.data.users even if there is no data in redis.
Using a simple setTimeout I have logged robot.brain.usersForFuzzyName results before and after redis-brain has connected:
2015-07-28T16:28:17.395478+00:00 app[web.1]: { id: 'U022358134311496EY',
2015-07-28T16:28:17.395484+00:00 app[web.1]:   name: 'mshwery',
2015-07-28T16:28:17.395486+00:00 app[web.1]:   real_name: 'Matt Shwery' }
2015-07-28T16:28:17.657642+00:00 app[web.1]: [Tue Jul 28 2015 16:28:17 GMT+0000 (UTC)] INFO Successfully authenticated to Redis
2015-07-28T16:28:17.669665+00:00 app[web.1]: [Tue Jul 28 2015 16:28:17 GMT+0000 (UTC)] INFO Data for hubot brain retrieved from Redis
2015-07-28T16:28:18.402143+00:00 app[web.1]: [Tue Jul 28 2015 16:28:18 GMT+0000 (UTC)] ERROR TypeError: Cannot read property 'toLowerCase' of undefined
2015-07-28T16:28:18.402180+00:00 app[web.1]:   at Brain.usersForRawFuzzyName (/app/node_modules/hubot/src/brain.coffee:135:7, <js>:123:22)
2015-07-28T16:28:18.402183+00:00 app[web.1]:   at Brain.usersForFuzzyName (/app/node_modules/hubot/src/brain.coffee:144:20, <js>:132:27)
2015-07-28T16:28:18.402187+00:00 app[web.1]:   at Timer.listOnTimeout (timers.js:119:15)
2015-07-28T16:28:18.402188+00:00 app[web.1]:
2015-07-28T16:28:18.402185+00:00 app[web.1]:   at [object Object]._onTimeout (/app/scripts/voting.coffee:27:17, <js>:6:38)


[DOCFIX]docfix for common-configuration

Docfixs for common-configuration.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15690/
Test PASSed.


Server crashes when you commit suicide

When playing gungame on dm_boxy, dm_offblast or dm_warhead and you jump into the pit the server just shuts down.
This happens wether sourcemod is installed or not.
The server is running in a pterodactyl docker vm.

If you have yourself god mode and did that then this will happen. Please provide some form of evidence when opening the bug so we can reproduce the issue and try to fix it going forward.
Closing this for now as I'm 99% sure you had some form of god mode enabled as we're aware of that issue.


Tiny icons

These icons have gone tiny again - which I have fixed 2 or 3x now and it keeps being broken and regressing.
Width should be not defined at all, or set to auto - SVG icons are not all square
https://github.com/TryGhost/Ghost-Admin/blob/master/app/styles/components/power-select.css#L10
1.0-beta2

This was broken with the IE11 fixes and hasn't been resolved/fixed yet. It's on my list, I thought an issue had been opened but search is failing me.


[PE-D][Tester E] Duplicate person under an event when adding multiple groups

The app adds duplicate entries of the same person when adding multiple groups to an event, to which the same person is part of. While it could be good to show who belongs to which group in this way, It could make the UI cluttered with too many details when adding multiple groups to an event. Perhaps showing only the groups or avoiding duplicate persons can make this better :)

Labels: type.FeatureFlaw severity.Medium
original: zhengyup/ped#8

TODO:

Update the docs to inform users of this behaviour

Fix by @DistractedCat


startJVM fails without any message with Python 3.8 32bit and jre1.8.0_241 on Windows 10

It seems, that it fails in jp_exception.cpp (line 493):

There is no exception caught in the catch-Block at jp_env.cpp (line 184):

jpype1 was buildt with:

the result is:

What could be the reason?

Windows Event Viewer shows:
Name der fehlerhaften Anwendung: python.exe, Version: 3.8.2150.1013, Zeitstempel: 0x5e55a3ed
Name des fehlerhaften Moduls: _jpype.cp38-win32.pyd, Version: <IP_ADDRESS>, Zeitstempel: 0x5e8d6107
Exception Code: 0xc0000409
Error offset: 0x0001696d
ID des fehlerhaften Prozesses: 0x5694
Startzeit der fehlerhaften Anwendung: 0x01d60d69a19940cf
Pfad der fehlerhaften Anwendung: c:\DEVTOOLS\Python\38-32\python.exe
Pfad des fehlerhaften Moduls: c:\DEVTOOLS\Python\38-32\lib\site-packages\jpype1-0.7.2-py3.8-win32.egg_jpype.cp38-win32.pyd
Berichtskennung: e758c246-05c9-477c-9272-a4715b5a616a
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Regarding to the link below 0xc0000409 means STATUS_STACK_BUFFER_OVERRUN.
https://stackoverflow.com/questions/23409809/windows-7-exception-code-0xc0000409

Ouch that is a bad place to throw an error.   At that particular point we don't yet have a working set of resources to handle an exception.  But the fact that the exception isn't caught is a general indication that something happened during the JNI call.  So why would it not be caught?
Our current exception stack only captures exceptions that are produced by our handling calls except for the rethrow.  So lets walk down the exception handling.
Each frame catches and adds stack info to the exception (which could potentially go wrong, but it would require a serious problem.
#define JP_TRACE_OUT } catch (JPypeException &ex) { ex.from(JP_STACKINFO()); throw; }

But if it hit this code path,then it should have printed a message prior to getting to the catch.
void JPypeException::from(const JPStackInfo& info)
{
	JP_TRACE("EXCEPTION FROM: ", info.getFile(), info.getLine());  // <= if it were JPypeException this get printed
	m_Trace.push_back(info);
}

So it must be a different type of exception.  Falling back to the catch for Python, all exceptions are redirected to the exception master handler.
#define JP_PY_CATCH(...)  } catch(...) \
  { PyJPModule_rethrow(JP_STACKINFO()); } \
  return __VA_ARGS__

That will then transfer all exceptions that are uncaught to the handler.  But there is another alarm bell here.  In order to get transferred it must have printed a message that it is being rethrown.
void PyJPModule_rethrow(const JPStackInfo& info)
{
	JP_TRACE_IN("PyJPModule_rethrow");  //<= But this line has to be printed
	JP_TRACE(info.getFile(), info.getLine());
	try
	{
		throw;
	} catch (JPypeException& ex) // <= we only handle JPype exceptions
	{
		ex.from(info); // this likely wont be necessary, but for now we will add the entry point.
		ex.toPython();
		return;
	}
        // Nothing handles case of a fail other than JPype.
	JP_TRACE_OUT;  // But if we did get to here then we are now stuck in an endless loop,
}

So I do see one way that we could get a stack corruption here.   If we get an unexpected exception type, we will burn through the stack resulting in the error reported.
So how to address this.
First lets add a fatal error handling routine to PyJPModule_rethrow which will address part of the bug.  But the harder part is understanding how we could have gotten an exception from frame.FindClass("java/lang/Throwable").

I should mention that this error has occurred before, but I have never successfully replicated it locally.  My general opinion it is some corrupt build.  Pulling the latest Python 32 bit and running against Oracle 1.8 241 works fine on my system for what it is worth.
$ python
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 22:45:29) [MSC v.1916 32 bit (In
tel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import jpype
>>> print(jpype.getDefaultJVMPath())
C:\Program Files (x86)\Java\jre1.8.0_241\bin\client\jvm.dll
>>> jpype.startJVM(convertStrings=False)
>>>

Do you use Win 10 64bit?
I will reinstall Python and retry...

I use windows 10 and can successfully run under the following configurations.

Python amd64 between 3.5 and 3.8 with oracle and corretto 8 and 11  (installed from conda)
Python x86 3.8 with oracle 8 (installed from Python.com)
Python WSL 3.8 with openjdk 8 and 11 (installed ubuntu)

It appears my production machine is currently "Python 3.7 conda with open JDK 12" on Windows 10.
Python 3.7.3 (default, Mar 27 2019, 17:13:21) [MSC v.1915 64 bit (AMD64)] :: Anaconda, Inc. on win32

This Python interpreter is in a conda environment, but the environment has
not been activated.  Libraries may fail to load.  To activate this environment
please see https://conda.io/activation

Type "help", "copyright", "credits" or "license" for more information.
>>> import jpype
>>> print(jpype.getDefaultJVMPath())
C:\Program Files\Java\jdk-12.0.1\bin\server\jvm.dll
>>> jpype.startJVM(convertStrings=False)
>>>

So I am very sure there are working configurations.  I just have no clue what could be going wrong on your system.

See #673 for exception handling fix.

I reinstalled Python and jpype (using pip):
C:\DEVTOOLS\Python\38-32>python
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 22:45:29) [MSC v.1916 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import jpype
print(jpype.getDefaultJVMPath())
C:\Program Files (x86)\Java\jre1.8.0_241\bin\client\jvm.dll
jpype.startJVM(convertStrings=False)

C:\DEVTOOLS\Python\38-32>

Hmm.  Lets try a version with the C++ exception fix
 python -m pip install git+https://github.com/Thrameos/jpype.git@exception_bug

if you don't mind?

pip fails:

First I uninstalled jpype and then reinstalled it.
It seems that "JPypeClassLoader.java" is missing.

Darn a two-for-one.  I will have to think on this a bit as clearly we are getting very different outcomes.   Thank you for the bug report, hopefully I can get this resolved when I am back in.
$ mkdir ~/tmp
$ cd ~/tmp
$ python -m pip install git+https://github.com/Thrameos/jpype.git@exception_bug
Collecting git+https://github.com/Thrameos/jpype.git@exception_bug
  Cloning https://github.com/Thrameos/jpype.git (to revision exception_bug) to c
:\cygwin64\tmp\pip-req-build-l1o3eqwm
  Running command git clone -q https://github.com/Thrameos/jpype.git 'C:\cygwin6
4\tmp\pip-req-build-l1o3eqwm'
  Running command git checkout -b exception_bug --track origin/exception_bug
  Switched to a new branch 'exception_bug'
  Branch 'exception_bug' set up to track remote branch 'exception_bug' from 'ori
gin'.
Building wheels for collected packages: JPype1
  Building wheel for JPype1 (setup.py) ... done
  Created wheel for JPype1: filename=JPype1-0.7.2-cp38-cp38-win32.whl size=12533
55 sha256=7ca33c179478b4bd69caaa8e4d53cfe19774e49105afb3ca2d07070308be7f8b
  Stored in directory: C:\cygwin64\tmp\pip-ephem-wheel-cache-0a_g1gz5\wheels\a1\
f1\2f\93ce2498590216c151eeea9ccaeaea65ee38722f8dc5003037
Successfully built JPype1
Installing collected packages: JPype1
Successfully installed JPype1-0.7.2
(python-3.8-win32)
$

My German is not so great, but could that mean that "javac" is not found rather than "JPypeClassLoader.java"?  It would give a different error if it could not find the java file.
https://www.easeus.de/daten-wiederherstellen/das-system-kann-die-angegebene-datei-nicht-finden.html

Obviously your German is better than mine ;)
Adding java to %PATH% made it work.
The behavior is still the same though

No errors, no output, nada.  I am stumped.
At this point I would recommend trying to capture it under a debugger or using the trace with some printfs thrown in.   The debugger will be  a problem as the JVM uses segfault as a messaging system for the gc so first thing it does is create an error.  So I guess printf is your best bet.
I will be whatever assistance that I can be.

Thank you so far.
I will spend some time on it...

I got the master and building it with "--enable-tracing" fails, with compiler errors:

jp_class (343):  JP_TRACE("Python");//, JPPyObject::getTypeName(pyobj)); <- pyobj not defined
jp_exception.cpp(30): JP_TRACE("JAVA EXCEPTION THROWN:");//, msn); <- msn not defined
jp_exception.cpp(40): JP_TRACE("EXCEPTION THROWN:", error);//, msn); <- msn not defined
jp_proxy.cpp(47):
// JP_TRACE("Convert", i, type->getCanonicalName()); <- type not defined yet
jobject obj = frame.GetObjectArrayElement(args, i);
JPClass* type = frame.findClassForObject(obj);
JP_TRACE("Convert", i, type->getCanonicalName());  <- line moved
pyjp.h (40/41):
the macro JP_PY_CATCH_NONE is not defined, with JP_TRACING_ENABLE set
#endif
#define JP_PY_CATCH_NONE(...)  } catch(...) {} return __VA_ARGS__ <- switched both lines

I would suggest to continue when these errors are fixed.

Fixed in #675

Is it possible there is something wrong with JPJavaFrame?
These lines seem to work:

But the similar code fails:

Result:

@Karl:
is it possible to get your compiled pyd-files to try them on my machine?
Maybe the compiler makes a difference...?

Okay so we have it isolated to one statement.  We just need to break it down a bit further to see what happened.
jmethodID JPJavaFrame::GetMethodID(jclass a0, const char* a1, const char* a2)
{
JP_TRACE_IN("GetMethodID", this);
	JAVA_CALL("JPJavaFrame::GetMethodID");  // This is setting up exception handling.
JP_TRACE("env", m_Env);
JP_TRACE("a1", a1);
JP_TRACE("a2", a2);
try{
	jmethodID mid = m_Env->functions->GetMethodID(m_Env, a0, a1, a2);  // This is a native call the JVM DLL
JP_TRACE("GetMethodID success");
       return mid;
catch(std::exception &ex)
{
JP_TRACE("unexpected throw", ex.what());
}
catch(...)
{
JP_TRACE("unexpected throw");
}
JP_TRACE_OUT;
}

From here we need to see where that JAVA_CALL statement went.
#ifdef JP_INSTRUMENTATION
#define JAVA_CALL(X) \
	JPCall call(*this); \
	PyJPModuleFault_throw(compile_hash(X))
#else
#define JAVA_CALL(X) JPCall call(*this);
#endif
#define JAVA_CHECK(X)  call.check()

So here is the most dangerous part of this code path
/** Call a java jni function with error checking.
 *
 * This version should be used when the java call is a fixed length of time
 * to complete.
 */
class JPCall
{
	JNIEnv* _env;
	JPContext* _context;
public:

	JPCall(const JPJavaFrame& frame)
	{
// We are just setting up some variables for later.
		_env = frame.getEnv();
		_context = frame.getContext();
	}

	void check()
	{
		if (_env && _env->functions->ExceptionCheck(_env) == JNI_TRUE)
		{
			JPJavaFrame frame(_context, _env);
			jthrowable th = _env->functions->ExceptionOccurred(_env);
			_env->functions->ExceptionClear(_env);
			_env = 0;
			throw JPypeException(frame, th, JP_STACKINFO());
		}
	}

// This is a throw from a dtor.  Which is intended to make sure that we check for JNI errors....
// But if somehow we enter this from a C++ exception we would be in trouble.
	~JPCall() NO_EXCEPT_FALSE
	{
// So we need to instrument it
JP_TRACE_IN("~JPCall");
JP_TRACE("Check exception", _env);
		// This is a throw in destructor which is only allowed on an exception safe code pattern
		if (_env != NULL && _env->functions->ExceptionCheck(_env) == JNI_TRUE)
		{
JP_TRACE("Set up frame", _context, _env);
			JPJavaFrame frame(_context, _env);
JP_TRACE("Check exception");
			jthrowable th = _env->functions->ExceptionOccurred(_env);
JP_TRACE("Clear exception", th);
			_env->functions->ExceptionClear(_env);
			_env = 0;
JP_TRACE("Transfer control to throw"); // next line can abort if we have something already thrown
			throw JPypeException(frame, th, JP_STACKINFO());  // lgtm [cpp/throw-in-destructor]
		}
JP_TRACE_OUT;
	}
} ;

So the three likely problems we have to rule out

[ ] your JVM is not acting properly, (did it die in the native call?)
[ ] your compiler failed to respect the no-exception line and it barfing on the check and has compiled into invalid code.  (did it die in the exception check?)
[ ] is there some way to get another exception issues.

In addition we have another alternative approach, which is trying to determine if it is something special about the call to "getStackTrace".   In order to rule that out I would attempt to take some minor piece of code like getting the method for toString above the crash point.

Here the output:
>>> jpype.startJVM(convertStrings=False)
<B msg="PyJPModule_startup" >
  <B msg="JPPyUnicode::asStringUTF8" >
    <M>JPPyUnicode::asStringUTF8 : pyref new(claim) 026FDB60 1 bytes</M>
    <M>JPPyUnicode::asStringUTF8 : pyref dtor(dec) 026FDB60 1 bytes</M>
  </B> <!-- JPPyUnicode::asStringUTF8 -->
  <M>PyJPModule_startup : vmpath C:\Program Files (x86)\Java\jre1.8.0_241\bin\client\jvm.dll</M>
  <M>PyJPModule_startup : pyref new(inc) 00150028 3102 tuple</M>
  <M>PyJPModule_startup : pyref new(claim) 02743870 20 module</M>
  <M>PyJPModule_startup : pyref new(claim) 02767A48 4 list</M>
  <M>PyJPModule_startup : pyref new(claim) 0269FE88 3 builtin_function_or_method</M>
  <M>PyJPModule_startup : pyref dtor(dec) 0269FE88 4 builtin_function_or_method</M>
  <M>PyJPModule_startup : pyref dtor(dec) 02767A48 4 list</M>
  <M>PyJPModule_startup : pyref dtor(dec) 02743870 20 module</M>
  <B msg="JPContext::startJVM" >
    <B msg="JPException_init" >
      <B msg="~JPCall" >
        <M>~JPCall : Check exception 02EED140</M>
      </B> <!-- ~JPCall -->
      <B msg="GetMethodID" >

D:\jpype-master>

That is beyond strange.  There is nothing between the last print and the print of the args that could do anything.   It is just calling a ctor that copies two variables. Most likely the stack has been corrupted before this point.
I will put up a test PR after work to try to make this code a bit safer.

I attempted to address a potential problem in #679

I haven't heard back from you.  I did find one matching bug report indicating that on some systems it is necessary to place the java bin directory in the path to get the JVM to load.

I set PATH to
> PATH=C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86;C:\DEVTOOLS\Java\1.8-32\bin;...

>>> import jpype
>>> jpype.startJVM(convertStrings=False)

and got the same results.

@Matthias1975   I added a set of files to help you with debugging the start up issue in PR #729.
The instructions are in project/debug/windows/README.rst.  It researching the problem I found one bug with the error reporting path for JVM, but just prevented it from reporting a fairly meaningless message like "unable to load %1".   Windows simply does not produce any usable diagnostics information on LoadLibrary.
I ran through every possible test case local.  (Missing DLL, corrupt DLL, wrong Arch, missing JVM dependency) and recorded the outputs I got.   Hopefully it will help you find your issue.  The problem is clearly a site problem.  You have an improperly installed JVM, corrupt libraries, or paths pointing to libraries that don't belong to the JVM.  There is nothing further I can do.

As this is likely a site specific issue and not a general JPype bug I am going to close this one for now.  The debugging guide for this type of problem is posted.