Color picker eyedropper creates a black rectangle on the editor viewport

Godot version
4.0.rc6
System information
Windows 10, Forward+, GTX 1070 driver 528.49
Issue description
As you can see on the screenshot, a black square appears with the message "Color Picking active" at the top.

The screenshot has been taken on my ultrawide monitor but it does the same on every monitor I have. Also, if I open up the eyedropper again, the black square takes the whole screen instead of a smaller part.
From there, pressing escape or clicking anywhere ON the rectangle closes the color picker and removes the black square and the selected color is black. If I click on the editor outside of the black rectangle, the color picker is closed but it doesn't select any color.
I've tested this issue on Windows with RC3, 4 5 and 6 and also with the three renderer available: Forward+, Compatibility and Mobile and the results are the same.
Someone else tried on Linux and had the same problem on the three renderer avaialble: Forward+, Compatibility and Mobile.
Linux config in case it's important:
Ubuntu 22.10 - KDE (X11)
3060 RTX mobile, driver: 525.78.01
I've seen this issue that seems somewhat related but they're not decribing the black square that I see.
Steps to reproduce
In an empty Godot 4 project, try to use the color picker eydropper tool to get a color on the screen
Minimal reproduction project
N/A

CC @bruvzg @KoBeWi

I can reproduce it on macOS as well (but black rect is covering the top quarter of the window).
I have never looked at the color picker code, but seems like color picker is trying to cover the parent window with a popup and draw copies of the other windows on it, which is a really strange way to do it and will never work (it at least should have a separate window for each screen).

I think #72764 last touched this functionality.
I can't reproduce this issue, for me it works without problems. Tested on Windows 10 on master.

I can't reproduce this issue, for me it works without problems. Tested on Windows 10 on master.

Try in on the second display or with non-maximized window. It only works if main window is at (0,0) position and on the display which is at (0,0).

Ah right 🤔
Although for me only the background is black, the Godot window is intact and picking is still working.
It's weird that everything becomes black, but at least it's functional, idk.
I think the problem is that the picking window does not fit the parent.

I get quick flashes of black on my screen. I tried to capture it on video but the recording program just blacked out until i stopped the color picking

What program did you use? I think OBS should be able to handle it.

I used obs yes

I managed to record it using the age old method of recording your screen with a phone camera
https://user-images.githubusercontent.com/80917990/221607771-2205809a-d12c-461b-bad2-fb70bc9b95a7.mp4

I'm the Linux user MrEliptik mentioned, and i tried it without external monitor connected : no black screen anymore, it works as intended.

I confirm that disconnecting all my other monitor to keep only one fixes the problem. I see a small rectangle with color being picked isntead of the big black rectangle

It's not only windows (as the tags would suggest). The behaviour is bad in a slightly different way on Mac, so I'm not quite sure that it qualifies as the same bug. Anyway - v4.0.stable. Color picking shifts the whole window area down
also related issue

#73935

https://user-images.githubusercontent.com/51323316/222938906-43dce778-c7c4-406a-854b-a90f5c086e5c.mov

I'd like to add that it's not very user friendly that you can't pick colors outside Godot's windows. Everything else turns black even on a single-monitor system, and it doesn't look very good.

@dame-ng color picking the whole monitor is a whole different beast that requires screen recording to be allowed afaik. Applications can not view outside their windows by design. You will notice The same behaviour in many other applications as well. As much as I would like it too, I think It would be best in a feature request

@Qubus0 I'm not sure about macOS, but I've done it on Windows without any problems.

I also use apps that allow to do it, and likely on macOS too (Clip Studio Paint, for example).

AFAIK there are some system-specific methods to allow that. GIMP supports it and it works very well, even taking the screen color calibration into account.

i just used powertoys and copied it from there.

Problem is still active and happening as of Godot 4.0.2

Can confirm for 4.0.2 stable
Win10 | AMD Ryzen 7 3700X | RTX 3060 Ti and 6600XT | Forward+

4.0.2 stable, under Debian 11, with dual monitors with the primary display set as the one on the right.
it's as if godot is momentarily calculating the 0,0 position from both screens, which is on 2nd monitor and is outside of the engine, which would explain why it turns all black? otherwise, if i have godot on that (left-most) screen, it works properly, as shown below:
Screencast 2023-05-17 18:04:19.webm

Experienced this on 4.0.3 and can confirm it's also not an issue for me if I use a different monitor. This also looks similar to my other issue: https://github.com/godotengine/godot/issues/76551


Give user information about increasing inotify watch count when needed

When watching for changes on Linux, the default limit of inotify handles is 8192. This runs out pretty quickly for medium sized projects. For example, running :snapshots:integTest on gradle/gradle wants to register 10K+ watches.
It is typically okay to increase this number substantially, though it requires superuser privileges. IntelliJ for example recommends 512K watchers. Some more info on memory consumption etc: https://unix.stackexchange.com/a/13757
If we hit the limit, and thus can't watch the file system, we should warn the user at the end of the build, pointing them to some resource describing how they could bump the watch count.

cc: @gradle/build-cache

The error number returned from inotify_add_watch is ENOSPC (28) when the user runs out of inotify watches:
       ENOSPC The user limit on the total number of inotify watches was
              reached or the kernel failed to allocate a needed resource.

These are the messages IDEA uses: https://github.com/JetBrains/intellij-community/blob/0e4772fc8c2e70019209d9bfb41fac6de131cf14/native/fsNotifier/linux/main.c
Note that there is the inotify instance limit and the inotify watches limit which may need to be increased.

Fixed via https://github.com/gradle/gradle/pull/13573


[fix] - filter operator does not exists

If an operator does not exists the api should return 400

#14


Move dependencies for rueidiscompat to go.mod

https://github.com/redis/rueidis/issues/466
Solves this issue

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

Comparison is base (5a8fa52) 95.65% compared to head (c5e57f3) 98.77%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #467      +/-   ##
==========================================
+ Coverage   95.65%   98.77%   +3.12%
==========================================
  Files          63       59       -4
  Lines       31765    26187    -5578
==========================================
- Hits        30384    25866    -4518
+ Misses       1185      310     -875
+ Partials      196       11     -185

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

Hi @DestroyerAlpha, these changes look great. Many thanks!
But the changes in the rueidiscompat/hscan_test.go seem to be unnecessary. Could you revert it?

Hey @rueian, Are you saying we do not need to replace global imports in hscan_test.go?

Hey @rueian, Are you saying we do not need to replace global imports in hscan_test.go?

Yes, can we just keep it untouched? Or will it be broken if we don’t replace global imports?

ginkgo moved to an indirect dependency, until I changed all imports to explicit imports.

ginkgo moved to an indirect dependency, until I changed all imports to explicit imports.

Hi @DestroyerAlpha, so what made you want to change them to explicit imports?

To remove ginkgo as a dependency from redis/rueidis altogether and not just present as an indirect dependency

@rueian Made changes. Not sure why it didn't work the first time around

Closed by https://github.com/redis/rueidis/pull/472#issuecomment-1952839914


bug: Error when performing a line break

Did you check docs and existing issues?

[X] I have read all the plugin docs
[X] I have searched the existing issues
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.0
Operating system/version
NixOS 24.11.20240712.7e7c39e (Vicuna) x86_64
Describe the bug
Hello, I have this error when skipping line in java, I get this error, I don't know if it's some nvim-java, lsp or lazyVim problem, I have a fresh installation of LazyVim and the only thing I've put has been the nvim-java plugin, I've tried changing jdk and the error is not solved.
The error occurs when I write in this class, in the others it does not always happen
Steps To Reproduce
1
https://github.com/user-attachments/assets/3bc7223f-1f86-4214-a4a6-4eccbe01fcd4
Expected Behavior
I was hoping that no annoying mistakes would happen

With vim.lsp.protocol.make_client_capabilities() inlay hint works fine. I'm also using LazyVim. I get no issue. Seems unrelated to nvim-java too

How strange, is it because of my distribution?

Don't think so. I'm also using Lazyvim as my personal configuration

I fixed this error by disabling the inlay hint

Am also getting this error with Neovim 0.10, not using a distribution.

Hey, I'm getting the same error with Neovim 0.10.0 and also after updating to 0.10.1. And I am getting it only with Java files. I am using a fresh copy of nvim-java/starter-lazyvim. Are there any updates on this issue?

Hi,
seems to be buggy for me too.
Describe the bug
When I use jdk-17 -> getting same error message.
When I use jdk-11 -> no error.

I also experience this bug on 0.10.2


WA-280 - Feature: improve safe creation flow

This PR fixes:

Bug found allowing to create infinite owners in a safe (and therefore problems when rendering a high number of components). Now it is limited to 50.

This PR tests:

When introducing a higher number of confirmations than owners a field level validation is run under the hood showing an error

This PR solves:

When creating a safe while the Tx is executed, if you leave the page (for example going to Safe List view), once the tx is executed the safe will be stored async.
See video: here

Travis automatic deployment:
https://staging-13-pr-gnosis-team-safe-gnosis.surge.sh
Storybook book automatic deployment:
https://storybook-staging-13-pr-gnosis-team-safe-gnosis.surge.sh

@germartinez Can you scroll? or is just the scrollbar is visible? Good catch, obviously in my environment that scroll does not appear.

Travis automatic deployment:
https://staging-13-pr-gnosis-team-safe-gnosis.surge.sh
Storybook book automatic deployment:
https://storybook-staging-13-pr-gnosis-team-safe-gnosis.surge.sh

Travis automatic deployment:
https://staging-13-pr-gnosis-team-safe-gnosis.surge.sh
Storybook book automatic deployment:
https://storybook-staging-13-pr-gnosis-team-safe-gnosis.surge.sh

Travis automatic deployment:
https://staging-13-pr-9-gnosis-team-safe-gnosis.surge.sh
Storybook book automatic deployment:
https://storybook-staging-13-pr-9-gnosis-team-safe-gnosis.surge.sh


Signed-out callback path coverage

Fixes #34378
cc: @damienbod if you want to take a look and provide feedback.
Notes

Updates to the Blazor+OIDC article.
Added to the Blazor+Entra article.
Added to the main doc set's RP+OIDC article.
I don't think that we carry an article/sample for RP or MVC and Entra, so there's nothing to update in that regard AFAIK.
Keeping the remarks about https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5783 for now, which were first placed by Halter back when he provided the first sample, the OIDC (BFF pattern) sample app, on https://github.com/dotnet/blazor-samples/pull/137. I'll use my version-tracking inline HTML comment notes to keep up with the remarks and mod as needed in all three articles and sample apps.
The RP+OIDC sample app mostly refers readers to the Blazor+OIDC article for app config guidance. However, I felt placing a section on this config for this one setting makes sense. If the consensus turns out to be to just let the Blazor+OIDC article with cross-link from the RP-OIDC article take care of it, I'll 🔪 the Signed-out callback path configuration section out of the RP+OIDC article. 👂

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/security/blazor-web-app-with-entra.md
aspnetcore/blazor/security/blazor-web-app-with-entra

aspnetcore/blazor/security/blazor-web-app-with-oidc.md
aspnetcore/blazor/security/blazor-web-app-with-oidc

aspnetcore/security/authentication/configure-oidc-web-authentication.md
aspnetcore/security/authentication/configure-oidc-web-authentication

UPDATE (12/18): I'm waiting to hear back from @halter73 if ...
https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-web-app-dotnet-core-sign-in
... is a suitable MSAL/MS Identity Web/Entra article to cross-link at the top of the RP+OIDC article.
Otherwise, I've made the relevant updates to 🔪 most of the Entra guidance from the two OIDC articles. However, I left a bit in a NOTE in those articles just in case someone uses the OIDC bits with Entra. I'd like to avoid unnecessary doc issues.
@damienbod ... Looks like your article wasn't edited by anyone before it was published. I only had a few minutes for a quick pass, but I fixed a few nits and bits here and there. It's all just minor grammar and style manual stuff, along with our 1,000 repo-specific (undocumented) conventions.

I found another sample link to include for External ID at ...
https://learn.microsoft.com/en-us/samples/azure-samples/ms-identity-ciam-dotnet-tutorial/ms-identity-ciam-dotnet-tutorial-1-sign-in-aspnet-core-mvc/
... so we'll see if that along with ...
https://learn.microsoft.com/en-us/entra/external-id/customers/sample-web-app-dotnet-sign-in
... are the ones Stephen is cool with.
That's it for today. I'll make a final pass on Thursday morning.

@halter73 ...

Cross reference not found: 'Microsoft.AspNetCore.Builder.OpenIdConnectOptions.SignedOutRedirectUri*'.

Did you mean Microsoft.AspNetCore.Builder.OpenIdConnectOptions.SignedOutCallbackPath ... but even if so, that appears to be 1.1-era bits.

That's it!

@halter73 ... I performed a few more passes to mop up the last few changes. I'll merge now. I'm clearing out as many work items and closing as many PRs as I can before taking off for the 🎄 holidays. If you have further updates, please open a new issue from the bottom of the article, and I'll either try to get them in quickly now or take care of them in January. Happy Holidays! ⛄

@meslubi2021 ... STOP COMMENTING! You've been reported to GitHub!


HTTP binding for the message.

Scope of this issue is to add the HTTP binding to the general protocol and new abstract interface https://github.com/CrowCpp/Crow. Crow has it is own vcpkg so it enough do a vcpkg install crow and it easy to use.

Closing, this should be in up-spec project

Yep. It is somet

Closing, this should be in up-spec project

Yep.


Fix versions numbers in changelog

This is a minor thing but the version numbers in the changelog were incorrect (e.g. 2.06 vs. 2.0.6).  This fixes them.

#141 includes this plus a tool to parse the changelogs into annotated git tags.  Closing.


[HDFS] Add configurable administrators

@loren:  Is this Elastic test failure due to slowness i.e. a flake or is this a real bug?  The PR doesn't touch Elastic.

It's a flake (that particular plugin install/uninstall test has been passing for months now). Looking at the logs, it looks like the call to marathon_update doesn't happen successfully for one reason or another. I'd expect to see evidence of this in the logs:
requests.put(marathon_api_url('apps/{}'.format(PACKAGE_NAME)), json=config, headers=REQUEST_HEADERS, verify=False)

Since the marathon config update doesn't go through, the plugin never gets installed, so the test spins and times out.

On Feb 19, 2017, at 6:53 PM, Gabriel Hartmann<EMAIL_ADDRESS>wrote:
@loren https://github.com/loren: Is this Elastic test failure due to slowness i.e. a flake or is this a real bug? The PR doesn't touch Elastic.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/mesosphere/dcos-commons/pull/586#issuecomment-280976111, or mute the thread https://github.com/notifications/unsubscribe-auth/AACnWFuDhnOl_keLGBk_KqnBRRDA7W4yks5reQAsgaJpZM4MEqIF.

retest this please


Raises 400 (bad request) error with django 1.6.+

Every call I make since upgrading from 1.5.5 to 1.6.2 gives this traceback :
    output = server.test("test")
  File "F:\Envs\smc_dev\lib\site-packages\jsonrpclib\jsonrpc.py", line 276, in __call__
    return self.__send(self.__name, args)
  File "F:\Envs\smc_dev\lib\site-packages\jsonrpclib\jsonrpc.py", line 224, in _request
    response = self._run_request(request)
  File "F:\Envs\smc_dev\lib\site-packages\jsonrpclib\jsonrpc.py", line 244, in _run_request
    verbose=self.__verbose
  File "F:\Bin\Python\2.7\Lib\xmlrpclib.py", line 1264, in request
    return self.single_request(host, handler, request_body, verbose)
  File "F:\Bin\Python\2.7\Lib\xmlrpclib.py", line 1313, in single_request
    response.msg,
xmlrpclib.ProtocolError: <ProtocolError for localhost:8000/smc/rpc/: 400 BAD REQUEST>

It seems like there is a patch here, but I did not test it :
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/185403
Solution for me was to stay with django 1.5.5

It's working with 1.6 now


Diffusion model benchmark

We have support diffusers in https://github.com/alibaba/BladeDISC/issues/867 . This issue tracks performance of all the diffuser pipelines. For the concern of performance, we use BlaDNN to tuning models during runtime.
The following pipelines would be tested:

[ ] StableDiffusionPipeline

[ ] runwayml/stable-diffusion-v1-5
[ ] stabilityai/stable-diffusion-2-1-base

[ ] StableDiffusionImg2ImgPipeline

[ ] runwayml/stable-diffusion-v1-5

[ ] StableDiffusionDepth2ImgPipeline

[ ] stabilityai/stable-diffusion-2-depth

[ ] StableDiffusionInpaintPipeline

[ ] runwayml/stable-diffusion-inpainting

[ ] AltDiffusionPipeline

[ ] BAAI/AltDiffusion

pipeine
model
img size
unet-pytorch
unet-disc
e2e-pytorch
e2e-disc

stableDiffusionPipeline
stabilityai/stable-diffusion-2-1
768*768
119.81ms
60.08ms
6.21s
3.14s

StableDiffusionImg2ImgPipeline
runwayml/stable-diffusion-v1-5
768*512
66.22ms
29.49ms
3.25s
1.30s

StableDiffusionDepth2ImgPipeline
stabilityai/stable-diffusion-2-depth
480*640
44.33ms
19.89ms
2.08s
0.89s

StableDiffusionInpaintPipeline
runwayml/stable-diffusion-inpainting
512*512
37.52ms
19.17ms
2.63s
1.10s

AltDiffusionPipeline
BAAI/AltDiffusion
512*512
37.93ms
18.74ms
2.65s
1.08s

How about the e2e latency run with TensorRT/AIT?

pipeine	model	img size	unet-pytorch	unet-disc	e2e-pytorch	e2e-disc
stableDiffusionPipeline	stabilityai/stable-diffusion-2-1	768768	119.81ms	60.08ms	6.21s	3.14s
StableDiffusionImg2ImgPipeline	runwayml/stable-diffusion-v1-5	768512	66.22ms	29.49ms	3.25s	1.30s
StableDiffusionDepth2ImgPipeline	stabilityai/stable-diffusion-2-depth	480640	44.33ms	19.89ms	2.08s	0.89s
StableDiffusionInpaintPipeline	runwayml/stable-diffusion-inpainting	512512	37.52ms	19.17ms	2.63s	1.10s
AltDiffusionPipeline	BAAI/AltDiffusion	512*512	37.93ms	18.74ms	2.65s	1.08s

Can you share the scripts to run these benchmarks?

@zzpmiracle Where I can find scripts to run this benchmarks? i've tried using it on the latest diffusers version, and it can't trace the components...

@zzpmiracle Where I can find scripts to run this benchmarks? i've tried using it on the latest diffusers version, and it can't trace the components...

maybe we can use docker images in this zhihu article https://zhuanlan.zhihu.com/p/631461489

@zzpmiracle Where I can find scripts to run this benchmarks? i've tried using it on the latest diffusers version, and it can't trace the components...

maybe we can use docker images in this zhihu article https://zhuanlan.zhihu.com/p/631461489

@zzpmiracle hi, do you have an example of Hires.fix ?


Don't let people inject evil code

I was actually learning, but my friend came up and said Why don't we try putting some code there?
so when the exercise looked roughly like this
val some = Some(123)

some.get shouldEqual _____    <- type something here

I put
{ while (true) {}; 123 }
Unfortunately server went down while testing 👯
Looks like the whole website is down on Application Error title and 404 page.
I'm sorry :)

It's because yesterday we replaced the problematic evaluation code with Twitter's eval and we are not respecting timeouts now, working to fix it. Thanks for reporting :blush:


[Config Packages] in devbox add, allow multiple --platform/--exclude-platform flag values

Summary
This PR enables calling --platform with multiple values with devbox add.
It gives the user an option to user either or both (1) comma-separated flag values (2) multiple flag invocations. Like:
--platform <platform>,<platform>...,<platform> --platform <platform> --platform <platform>
Ditto for --exclude-platform
How was it tested?
Augmented testscript unit test

Current dependencies on/for this PR:

main

PR #1357

PR #1360

PR #1358

PR #1363   👈

This comment was auto-generated by Graphite.


Can this be used in macos apps too?

Do you use SwiftUI or Cocoa for macOS development?

It can't be used right now, but if you 100% need it, let me know and I'll add this feature.


feat: Support sub-directory

By adding PUBLIC_URL to relative ., we can access casdoor's all web pages and static asserts under relative public url.
Closes #933
Signed-off-by: zzjin<EMAIL_ADDRESS>

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

@zzjin will this PR cause any bug for existing usage scenarios?

@zzjin will this PR cause any bug for existing usage scenarios?

As my local test, this will not affect any root domian deplyment.(https://test.com/./static===https://test.com/static)
I will test build full docker files, just need some more time.

@Resulte @leo220yuyaodog plz help test this PR to make sure it doesn't have any side effect


Add doc on assign app role managed identity cli.

Add documentation on assigning app role to managed identity using cli.

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

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

@CelesteDG Hi, I'm wondering if this might be a new article you were expecting and would want to have the contributor submit in the private repo? Or should we assign it to a member of the content team to move to the private repo for merge?
Thanks.

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

Hi @LizaShak. Per email with the content team, this pull request needs to be closed because it was opened in the public repository. The content needs to be created by using the private repository. A member of the content team will reach out to you to assist with doing that, OK? We'll close the PR. Thank you.
You can copy the contents on your files and save them in a Notepad file (or use some other process), so you don't lose the work.


Other display resolution

Hi, Im using your driver to setup a different display with the same chipset (ST7735S)

I followed the instructions and I get almost expected control on the screen but not really flawless like coordinates (0,0) for an square are like 5 pixels at left than really is it. I recorded a video of it, I hope it explains better than me (https://www.dailymotion.com/video/x7t5vh1).
I am using a raspberry 3b and the display in the picture (0.96 inch, 80x160)
My goals are

Set it up as a microDesktop screen but i have not luck yet (still looking for find it out)
Set it up on an OrangePi zero too, but i get random colored pixels.

I hope you can help me if I am doing something wrong.
Thx.

Hi,
I apologize for the response time.
I will try to help you as soon as possible.  First, I prepare Raspberry for me and I will make a short video for you.

On this address (https://www.youtube.com/watch?v=HY1hHUi0-1o) you can see how it looks like for me.

Look at the notes in the picture.
I marked the line numbers from main.c, where is the top and where is the first and last pixel on my display.
Note that the main function has constant coordinates for squares and lines. They are not prepared for your resolution, that's why lines are cropped at end. So don't worry about the lines and pay attention to the squares. They are at the very beginning.
Think of the display as a window of part of the driver's RAM.
Your pixel (0, 0) that is in the beginning of your window is in a different position in the RAM memory than (0, 0) address.
To fix this, you need to move the window accordingly. To such addresses from the RAM of your driver, on which what you draw will show on the display.
This is offset, which is relative to a (0, 0) point in RAM memory. The offset for width and height may be different.
Try this:
in this place:
/* The data type for one display */
typedef struct
{
	int cs, a0, rs;
	uint8 width, height;
	uint8 offset_width, offset_height;
} lcdst_t;

in this place (Note that I changed the resolution to yours.):
void lcdst_setOrientation(uint8 orientation)
{
	writeCommand(0x36); /* Memory Data Access Control */

	switch(orientation)
	{
		case 1:
			writeData(0x60); /* MX + MV */
			activeDisplay->width  = 160;
			activeDisplay->height = 80;
			activeDisplay->offset_width  = YOUR_VALUE_WRITE_HERE;
			activeDisplay->offset_height = YOUR_VALUE_WRITE_HERE;
			lcdst_setWindow(0, 0, 159, 79);
			break;

		case 2:
			writeData(0xC0); /* MY + MX */
			activeDisplay->width  = 80;
			activeDisplay->height = 160;
			activeDisplay->offset_width  = YOUR_VALUE_WRITE_HERE;
			activeDisplay->offset_height = YOUR_VALUE_WRITE_HERE;
			lcdst_setWindow(0, 0, 79, 159);
			break;

		case 3:
			writeData(0xA0); /* MY + MV */
			activeDisplay->width  = 160;
			activeDisplay->height = 80;
			activeDisplay->offset_width  = YOUR_VALUE_WRITE_HERE;
			activeDisplay->offset_height = YOUR_VALUE_WRITE_HERE;
			lcdst_setWindow(0, 0, 159, 79);
			break;

		default:
			writeData(0x00); /* None */
			activeDisplay->width  = 80;
			activeDisplay->height = 160;
			activeDisplay->offset_width  = YOUR_VALUE_WRITE_HERE;
			activeDisplay->offset_height = YOUR_VALUE_WRITE_HERE;
			lcdst_setWindow(0, 0, 79, 159);
			break;
	}
} /* lcdst_setOrientation */

in this place:
uint8 lcdst_setWindow(uint8 x1, uint8 y1, uint8 x2, uint8 y2)
{
	/* Accept: 0 <= x1 <= x2 < activeDisplay->width */
	if(x2 < x1) return 1;
	if(x2 >= activeDisplay->width) return 1;

	/* Accept: 0 <= y1 <= y2 < activeDisplay->height */
	if(y2 < y1) return 1;
	if(y2 >= activeDisplay->height) return 1;

	/* Set column address */
	writeCommand(0x2A);
	writeData(0); writeData(x1 + activeDisplay->offset_width);
	writeData(0); writeData(x2 + activeDisplay->offset_width);

	/* Set row address */
	writeCommand(0x2B);
	writeData(0); writeData(y1 + activeDisplay->offset_height);
	writeData(0); writeData(y2 + activeDisplay->offset_height);

	/* Activate RAW write */
	writeCommand(0x2C);

	return 0;
} /* lcdst_setWindow */

Here you must increase the offset until pixel (0, 0) appears on your display in the correct place.
There may be a problem when you start changing lcdst_setOrientation(). Because the offset will have to be adjusted to the orientation.
Try this code in main.c for test. Also check the height, because the pixel may not appear.
lcdst_setOrientation(0);
lcdst_drawScreen(0, 0, 0);
lcdst_drawPx(0, 0, 255, 255, 255);

I know this code is not perfect. The problem is that I don't have all the modules so that I can extend the code and run tests on them.

Have you changed the colors in main.c? I ask because they look different. If not, you may have other endianness or different number of colors does it.
I checked the specification of your module on the Internet. It looks like it has 65K different colors. Where this driver is prepared and tested for 262K and 4K colors.
262K mode should work OK, but you'll have big steps to change for another color. It would be necessary to analyze the documentation and correct bit operations for 65K mode. 4K mode should work correctly for you.

Feel free to write with any problem. I could have forgotten something in all this.

Hi, I made the changes and fixed the values of your answer and it fixed perfectly, also I modified to show four black lines as a frame from 1px from the border and there is no noisy lines.

(Ignore the tainted lines, it is from my camera)
About the colors I keep the original values of your code, it looks like it's casually working on YMC standard instead RGB. I guess an small hack coding of transformation between those standards could fix that issue.
About OrangePi, I will search about it, this is the first time I do something with SPI and my knowledge about it is still very limited. I will tell you about any important information I can get.
Thank you for your help, it was very usefull.

Hi, I've been working on Raspberry about colors and I realized the colors are not on YMC standard, there are working with cross red-blue channels and values are negative.
Well, if I want a value for rgb (100, 50, 255) I have to code it as follows
( 255-b, 255-g, 255-r) = (255-100, 255-50, 255-255) = (155, 205, 0).
As I said before, a bit of code for fix that is not really complex and I suppose the right place for it is on st7735s.h (I have to use my free time for it), but now...  how can I get a microDesktop display for Xwindows?
I have tried commands found on many pages but still doesnt work, no matters if colors are wrong for now. Any idea?

Your idea with this frame is great.

I used these specific colors because I liked them, nothing more. I must change them. Everything is in RGB standard.

63 page from the documentation v1.4 for 3-line SPI (without using MISO) (565 color mode):

To display one pixel you have to send two bytes. So you have to prepare these two bytes in one 'packet'. You have 5 bits for red. 6 bits for green. 5 bits for blue. Where green is partly in both bytes. If you prepare them, then you have to send first byte, then second byte. In this order. Then the cycle repeats for the next pixel. You don't need to subtract anything here, generally. I don't remember exactly anymore, but I didn't use these 'const 1 bit' and it worked. Probably with bug :/. I need to check it in my free time and improve it.
Unless I misunderstood and each of us thinks about something different.

Maybe try to use https://github.com/adafruit/Adafruit-ST7735-Library ? This library is more universal.

but now... how can I get a microDesktop display for Xwindows?

I have never used it. I really don't know. I always connect via SSH or HDMI cable.

Hi, thanks for your advice. I thought ST7731 and ST7731S was really different but those worked at first on Orange PI. I have the same issues (swaping of red and blue channels and one pixels line of random values at edge of screen) but I can deal with it.
Also I can get startX for desktop easily.
I'm not sure if that ends this topic but I suppose I will keep using that driver.
Thank you, again, very much for your help.


Sub-chart deleting order

Is there a way to control the sub chart deleting order?. For example lets' assume the chart A is a dependency for chart B. When we execute helm del <RELEASE_NAME>, instead of deleting both charts A and B at the same time, delete chart A before chart B.
Output of helm version:
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.5", GitCommit:"51dd616cdd25d6ee22c83a858773b607328a18ec", GitTreeState:"clean", BuildDate:"2019-01-16T18:24:45Z", GoVersion:"go1.10.7", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.8-gke.10", GitCommit:"f53039cc1e5295eed20969a4f10fb6ad99461e37", GitTreeState:"clean", BuildDate:"2019-06-19T20:48:40Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): GKE

There is not. There are other tools built on top of Helm that allow ordering to be controlled. For example, OpenStack needs ordering controlled and they use Armada that last I looked.
Kubernetes is declarative. In theory order should not matter. This is the case often argued. Some applications do require ordering and some tools have been created to help with that.

@mattfarina Thanks for the response. Although order doesn't matter In Kubernetes we can still control the order with Init containers. For example it is possible to wait until database getting ready before starting the main application. It would be better if we can have the similar approach for deleting the stack(delete database at last).

Closing this issue as answered. Please feel free to comment here and let us know if you have further questions. Thanks!

Is this still the case?

Yes. Kubernetes is a declarative system. When you need imperative processes, that's usually when you want to create an operator.


Firmware Changes to fix software shutdown timing and other improvements

Requested firmware for STM8S MCU to address firmware issues from Embest - no reponse to date.
Ideas:

Make software shutdown (OS initiated) as fast has button push - need to signal MCU to do the same as button press initiated shutdown
Support "press press" reboot to allow button initiated reboot

Note MCU is STM8S005CK part, 8-bit controller with 32Kb flash plus 128 bytes EEPROM, 2Kb RAM onboard pins are labeled for programming MCU.

I've been able to convince the Support team at Embest Technologies to provide sources rather than have me continue decompiling the code.  I've stopped that work now that I have the sources and have them building now.

Do you have any progress?
I guess you are not allowed to share the source code of the factory firmware, but I would be glad to help you.

While I have the firmware rewritten, I've decided not to publish/support it because RP4 is taking such a different direction, you can find the source code for the firmware in this repo:
https://github.com/hoopsurfer/mcu-power-control/tree/master/Pi_Desktop_iap_Stm8

Actually, I don't have RPi3 and PiDesktop anymore, I also went for RPi4.
Anyway, thank you for the support so far. Best wishes!


[WIP] feat: allow setting availability zones

This pull request introduce the "setAvailabilityZones" method which enables setting a list of availability zones for a given scope.
Usage:
Context.setAvailabilityZones(scope, ['us-east-1b', 'us-east-1c', 'us-east-1a']);

Why WIP:
setAvailabilityZones allows using the intrinsic getAZ via the intrinsic function Fn::Select:
Context.setAvailabilityZones(vpc, [
    cdk.Fn.select(1, cdk.Fn.getAZs()),
    cdk.Fn.select(2, cdk.Fn.getAZs())
]);

Due to the unstable nature of getAZ (order and size of the list can change) using it introduce some risks such as preventing deployment of a stack when the list changes.
If this is an acceptable behavior I will add a unit and integration test as well as a coding example of the  usage.
Pull Request Checklist

[x] Testing

Unit test added
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[x] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Is this what Elad told you to do?
I don't like the ordering dependency this creates, and it's also pretty non-discoverable.

ordering dependency

I mean, one must call Context.setAvailabilityZones() before constructing the VPC. If you do it afterwards, it will be too late, because the VPC will have determined its AZs in its constructor. I'm calling this an ordering dependency, because in this scenario:
// Case 1
Context.setAvailabilityZones(this, ...);
new Vpc(this, ...);

// Case 2
new Vpc(this, ...);
Context.setAvailabilityZones(this, ...);

The relative order of these 2 statements matters (one ordering will work, the other one won't), and more importantly:  there is no indication or forcing function to indicate that this is true.
The call to setAvailabilityZones() must be done on the VPC's parent before the VPC has been created. Given that the VPC is likely to be created in the constuctor of its containing Stack, in a realistic scenario the code must look like this:
interface MyStackProps {
  azs: string[];
}

class MyStack {
  constructor(..., props: MyStackProps) {
    super(...);

    Context.setAvailabilityZones(this, props.azs);  // <-- magic line here

    new ec2.Vpc(...);
  }
}

OBJECTION: But what if I don't want to parameterize my stack with the AZs? I just want to put a fixed value in there!
Sure, you're probably thinking of writing this:
class MyStack {
  constructor(...) {
    super(...);

    Context.setAvailabilityZones(this, [
      Fn.select(0, Fn.getAzs()),
      Fn.select(1, Fn.getAzs()),
      Fn.select(2, Fn.getAzs()),  // <-- should this line be here?
    ]);

    new ec2.Vpc(...);
  }
}

Your code still needs to be aware of whether the region you'll be deploying into has 2 or 3 availability zones. So for MyStack to work properly in any region, MyStackProps will still need to contain a threeAzs?: boolean property to decide between the two. In effect leading to:
interface MyStackProps {
  threeAzs: boolean;
}

class MyStack {
  constructor(...) {
    super(...);

    Context.setAvailabilityZones(this, [
      Fn.select(0, Fn.getAzs()),
      Fn.select(1, Fn.getAzs()),
      ...(props.threeAzs ? [Fn.select(2, Fn.getAzs())] : [])
    ]);
    new ec2.Vpc(...);
  }
}

Which is arguably worse than taking azs: string[] as a property and just passing it on.
The dirty secret is that stack-specific context as a method of configuration doesn't work very well, because you must set the context after the stack has been created, but before its constructor has completed. Which is to say, the only way to set that context is at the start of the constructor itself. So where will it get the context values that have to be configurable? Well, they have to come from the props anyway. So why isn't it props all the way down then?

Context.setAvailabilityZones(vpc, [

The given example, where setAvailabilityZones is called on the VPC context, will not work because the AZs will already have been determined at the time of executing vpc = new Vpc().
In my mind, the most pragmatic alternative is to just take Azs?: string[] as part of VpcProps.
Very clear no magic. Consumers can decide how to fill those props, either by making a MyGenericStack that does "something" or by adding azs: string[] to their own props.
I know this is not great, and context should have been the way to go, but it just doesn't work very well.
Plus, adding azs?: string[] as a property to VpcProps gives customers who want to a very clear way to control where their VPC is deployed, which will be helpful in cases such as in EKS where 1 of the 6 AZs in us-east-1 does NOT support EKS, and you must pick one of the other 5. (Or was it ECS? Anyway).
But please hold off on making the change according to my whims -- I supect @eladb  and I have a difference of opinion here, and I wouldn't want you to go back and forth while we battle it out.

there is no indication or forcing function to indicate that this is true.

Neta reminded me of the fact that we actually throw in the wrong case, which makes me feel better. At least the API won't be used incorrectly that easily.
Still don't like the hidden, roundabout way of passing props, and that nothing in the signatures of the methods involved forces the ordering, but at least it's not super broken.

I misbehaved in this thread before. I'm sorry.

Setting the AZs in the context mimics the behavior of setting it in the actual context file but  also enables the use of getAZ.
We don't want to only enable setting the AZ's in the VPC but also in other construct such as Network Load Balancer

We don't want to only enable setting the AZ's in the VPC but also in other construct such as Network Load Balancer

Aren't other constructs supposed to read the AZs from the VPC object?

It will be idle but not always possible, for example, after NLB is created it's not possible to update the AZs that were initially set

I am with @NetaNir here. The use case we are trying to address is not just to tell the VPC which AZs to use because there could be other potential constructs (either part of the AWS Construct Library or application-level constructs) that need the list of AZs for any reason. The AZ context provider is the CDK's way to allow implicit parameterization of exactly this kind, so to me, Context.setAvailabilityZones is the right layer to allow people to override this behavior, so the list of AZs will be consistent for everyone who queries it "the CDK way" (i.e. by using Context.getAvailabilityZones).
I don't see how we can achieve something like this without the context mechanism we have in the framework. Passing this information down from the top of your app all the way to any construct that will even need AZs is impractical. Context is akin to "thread local storage" or environment variables, and as much as it is "impure", it is a pragmatic approach, so long as it is not abused (which, granted, can happen).

I believe this is not required anymore, now that availabilityZones a property on Stack. To override the default behavior, users can extend Stack (which is a normative thing to do in the CDK) and override availabilityZones to return whatever they want. This is where all constructs within the stack (such as VPC, LBs, etc) will go in order to obtain the list of AZs, which will practically do the trick.


BI-760 (Notification handling improvements)

using the vuex store to hold the state of the notify-components

It's a little unclear to me from the jira card the exact behavior of notifications closing related to form updates. One example is I created a program and got a success notification. I then clicked edit on one of the table rows and then clicked cancel and the notification closed. technically this was a different form than the one that produced the notification. Not sure if that matters? @DebWeigand @timparsons

@nickpalladino I think if anything, any current notifications should be cleared when a new form is opened.  @shawnyarnes thoughts?


Pass async done function to clean tasks

Without passing this function, the clean task would exit before the system was able to delete the requested files.
Fixes #516 gulp clean does not erase files

Ya beat me to it, thanks Brendan :)


Implementation of Track Data Availability

Summary
Summarize the feature here.
Requirements
The more specific the better.

[ ]
[ ]

*Related tickets

Blocked on #95


Read back full screen state from window on macOS

Objective
I'm trying to display on a menu screen of my game the Windowed/Full screen state. However, on macOS it's possible for the user to trigger borderless fullscreen directly from the window controls, which results in a stale/wrong state displayed.
Solution

Add logic to read back full screen state and apply it to the window when the user directly makes it full screen via the window controls on macOS

Testing

Did you test these changes? If so, how? Yes, mostly on my game
Are there any parts that need more testing? I'm not sure if this has performance implications, as the call might be blocking on the UI thread. However, unscientifically I didn't notice any degradation.
How can other people (reviewers) test your changes? Is there anything specific they need to know? Adding log statements to the match branches should suffice.
If relevant, what platforms did you test these changes on, and are there any important ones you can't test? Just macOS

does winit sends a resolution changed event when the user changes the window controls? I think it would be better to add this when the window reacts to a corresponding event from winit

Should we be upstreaming this fix to winit instead?


dirPagination: Multiple filters with on of them being a date range.

I'm using jquery ui for the date picker, and I'm trying to make this tool work with it. So I saw the post with multiple filters, and have that working, but when I try and use my jquery ui field, it shows no results. I think the problem is that it is searching for items that exactly match the unix time stamp, and not ones that fall between the start date and end date. If you need code let me know.

Hi,
Sorry about the delay.
As far as I can tell, this is not an issue with my library, but rather a broader question about how to do a specific thing in Angular. Try StackOverflow, since I'm afraid I don't have time to help on this one.


Support cross-platform testing

Description of the new feature / enhancement
As contributor, I want to test DSC resources cross-platform through Azure Pipelines to ensure quality.
Proposed technical implementation details
Separate publish job and create test stage. Tests in Pester can be controlled by using the -Skip when declaring It blocks.

[Policy] Area Validation Pipelines


zwave.set_config_parameter throws error

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.46.1
Python release (python3 --version):
Python 3.5.3
Component/platform:
zwave
Description of problem:
When calling the zwave.set_config_parameter service I get the following error:
2017-06-09 18:14:54 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1967270896-5, service_data=parameter=3, node_id=12, value=1, service=set_config_parameter, domain=zwave>
2017-06-09 18:14:54 DEBUG (Thread-10) [libopenzwave] SetValueListSelection 1
2017-06-09 18:15:01 ERROR (Thread-1) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.5/dist-packages/homeassistant/core.py", line 1020, in execute_service
    service_handler.func(service_call)
  File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/zwave/__init__.py", line 429, in set_config_parameter
    value.data = selection
  File "/config/deps/openzwave/value.py", line 292, in data
    self._network.manager.setValue(self.value_id, value)
  File "src-lib/libopenzwave/libopenzwave.pyx", line 2867, in libopenzwave.PyManager.setValue (openzwave-embed/open-zwave-master/python-openzwave/src-lib/libopenzwave/libopenzwave.cpp:23786)
TypeError: Expected str, got int

This happens whether I pass it a string or an int.
Expected:
No error should be thrown and the setting should change on the zwave device.
Problem-relevant configuration.yaml entries and steps to reproduce:
script:
  test:
    alias: test
    sequence:
    - service: zwave.set_config_parameter
      data:
        node_id: 12
        parameter: 3
        value: 1

Run that script on the UI or go to the dev-service page, select the zwave domain, select the set_config_parameter service, type in {"node_id":12,"parameter":3,"value":1}, click the call service button.
Observe the error show up in the logs and the setting not get changed on the device.

Traceback (if applicable):
2017-06-09 18:14:54 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1967270896-5, service_data=parameter=3, node_id=12, value=1, service=set_config_parameter, domain=zwave>
2017-06-09 18:14:54 DEBUG (Thread-10) [libopenzwave] SetValueListSelection 1
2017-06-09 18:15:01 ERROR (Thread-1) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.5/dist-packages/homeassistant/core.py", line 1020, in execute_service
    service_handler.func(service_call)
  File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/zwave/__init__.py", line 429, in set_config_parameter
    value.data = selection
  File "/config/deps/openzwave/value.py", line 292, in data
    self._network.manager.setValue(self.value_id, value)
  File "src-lib/libopenzwave/libopenzwave.pyx", line 2867, in libopenzwave.PyManager.setValue (openzwave-embed/open-zwave-master/python-openzwave/src-lib/libopenzwave/libopenzwave.cpp:23786)
TypeError: Expected str, got int

Additional info:

This seems to work ok when I use the description of the value instead of its numeric id like so:
script:
  test:
    alias: test
    sequence:
    - service: zwave.set_config_parameter
      data:
        node_id: 12
        parameter: 3
        value: LED on when light on

Or when I give the following json to the service call:
{"node_id":12,"parameter":3,"value":"LED on when light on"}

I actually prefer using the description instead of the ID. We just need to document somewhere that this is how it works now.

Updated the documentation :+1:

For reference the documentation is here: https://home-assistant.io/docs/z-wave/#services


Update PeerManager and PeerMessagehandler

Codecov Report

Merging #23 into dev will increase coverage by 12.97%.
The diff coverage is 53.26%.

@@             Coverage Diff              @@
##                dev     #23       +/-   ##
============================================
+ Coverage     39.53%   52.5%   +12.97%
- Complexity      178     259       +81
============================================
  Files            64      69        +5
  Lines          1128    1295      +167
  Branches         57      74       +17
============================================
+ Hits            446     680      +234
+ Misses          663     574       -89
- Partials         19      41       +22

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/com/webank/wecross/core/SeqUtils.java
66.66% <ø> (ø)
1 <0> (ø)
:arrow_down:

...nk/wecross/p2p/peer/PeerRequestSeqMessageData.java
60% <ø> (+60%)
4 <0> (+4)
:arrow_up:

...main/java/com/webank/wecross/host/WeCrossHost.java
75% <0%> (ø)
5 <0> (ø)
:arrow_down:

...ecross/p2p/peer/PeerRequestSeqMessageCallback.java
50% <0%> (+50%)
1 <0> (+1)
:arrow_up:

...bank/wecross/restserver/p2p/RestfulP2PService.java
2.91% <0%> (-1.15%)
1 <0> (ø)

...webank/wecross/p2p/peer/PeerDoNothingCallback.java
0% <0%> (ø)
0 <0> (?)

...webank/wecross/host/SyncMessageHandlerFactory.java
100% <100%> (ø)
2 <2> (?)

...webank/wecross/restserver/p2p/P2PHttpResponse.java
100% <100%> (+100%)
12 <1> (+12)
:arrow_up:

...m/webank/wecross/p2p/peer/PeerInfoMessageData.java
64.7% <100%> (+64.7%)
5 <1> (+5)
:arrow_up:

...om/webank/wecross/host/SyncPeerMessageHandler.java
48.97% <27.27%> (+25.29%)
6 <4> (+4)
:arrow_up:

... and 22 more

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 60eaed7...c1496f8. Read the comment docs.


Question about WarGames and timeBeginPeriod(1);

I am writing a tool that attempts to convert the ddraw/Direct3D functions to Direct3D9.  As part of this work I ran into an issue with WarGames where it would hang for about 15 seconds or so right after the mission briefing and before starting the mission.
However, I discovered that it could be fixed by this line of code from DDrawCompat v0.3.2.  I am wondering why this line of code would prevent the game from hanging for 15 seconds, if you have any ideas.
Also, I see the timeBeginPeriod() called in DDrawCompat, but I cannot find the timeEndPeriod() call, which Microsoft's documentation says must exist:

You must match each call to timeBeginPeriod with a call to timeEndPeriod, specifying the same minimum resolution in both calls. An application can make multiple timeBeginPeriod calls as long as each call is matched with a call to timeEndPeriod.

This article probably explains what might be the problem better than I could:
https://randomascii.wordpress.com/2020/10/04/windows-timer-resolution-the-great-rule-change/

Also, I see the timeBeginPeriod() called in DDrawCompat, but I cannot find the timeEndPeriod() call, which Microsoft's documentation says must exist:

Pretty sure it's cleaned up on process exit anyway. (It would be pretty bad if it wasn't, since a crashing app can't clean up such things anyway). I think that note is mainly meant for apps that intend to continue running afterwards, when they don't need the increased timer granularity anymore, in which case this can save system resources.

I see.  Thanks for the article link!


Bug: Directory watch stream can't be cancelled.

Testing on Windows 11
Directory dir= Directory(Directory.current.path);
    dir.watch().listen((event) {
      print(event);
    });
    await dir.watch().listen((_) {}).cancel();

The above code still emits print events from the directory watch stream even after cancelling.
Secondarily, unless I'm approaching this wrong, which may be the case, directory streams are lack-lust at best and could really use some more helpers. Iterating changing lists of directories to watch for changes in order to trigger UI updates (as is the case in many desktop scenarios) is not the best. A cancel streams by path helper would be great. Iterating a list of directories to create watchers and then dispose of them is hard as each instance of a directory is unique despite paths being the same. I've mitigated this by managing a list of directory objects, yet can't find any way of cancelling them as per above bug. This creates a million watchers triggering a million events.

The way to cancel a Dart stream subscription requires you to remember the subscription object.
Here there are two subscriptions performed (two calls to listen), but only one of them is cancelled.
The other subscription keeps receiving events independently.
Try:
    Directory dir = Directory(Directory.current.path);
    var subscription = dir.watch().listen(print);
    await subscription.cancel();

Thank you Irhn. Closing issue.
FYI for future viewers - the stream object itself exists independently and needs to be tracked independent of the directory object. Calling directory.listen().watch() creates a new independent stream object and can't be used to control any other prior stream object. Makes sense retrospectively.

To be precise:
A Stream itself is an inert object which doesn't do anytning by itself. It shouldn't do anything, or start allocating any resources, until it's listened to.
When you listen to a stream, you create an active StreamSubscription, backed by code which can generate events, and the subscription stays active until the stream closes or the subscription is cancel'ed.
(Caveat: Some streams are backed by other resources from the start, like an HTTP request response body, and should be disposed of to release the underlying resource. Most streams should not be like that.)


#159170901-Readme file

Pull Request Test Coverage Report for Build 53

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

Totals

Change from base Build 49:
0.0%

Covered Lines:
15

Relevant Lines:
15

💛  - Coveralls


[SONARMSBRU-207] Amended targets to use the analyzer settings from th…

…e config file
Removed the obsolete SonarLintProvider code and tests
Fixed error in the Rsolyn profile name
Amended packaging code to ship NuGet.Core

LGTM


Add DockerFile

nowadays most developer community choose docker as platform more than vagrant, should we start to write DockerFile? I need suggestions.

Docker is not for a full development environment like this including the OS, compilers, web servers and all the various tools. Docker is much more suited for single-app things. There are plenty of PHP 7 Docker implementations out there.


Custom Actors

Created as per @sergmetelin . Will also insert into the Roadmap

This should be a continuation of https://github.com/hashgraph/guardian/issues/51

We just need confirmation from Serg / To Explain to Serg

Next step is for Serg to confirm this has been completed already and can be closed.


My first commit

Developer Checklist

[ ] Followed guidelines mentioned in the readme file.
[ ] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[ ] Starred ⭐ the Repo (Optional)

Summary
It is a Simon Says game using technologies HTML , CSS, JS
Screenshot

closes #1089


allow user to specify the security protocol of ssl/tls in azkaban.properties

allow user to specify the security protocol of ssl/tls in azkaban.properties manually,
by setting up "mail.security=tls" or "mail.security=ssl"

refers to: #1757


algorithm  has disconnected while in ready state, reason: 1000.

HKube micro-service
HKube 2.6.20 Worker pod
Describe the bug
During a 10 min run of sanity test i received multiple reports of the following:
Error:
algorithm  has disconnected while in ready state, reason: 1000.
Expected behavior
To Reproduce
Steps to reproduce the behavior:

Run "simple" sanity automated test.

Screenshots

This warning would apear if the algorithm container suddely disconnected, with out sending a failure indication to worker.


Wayland socket is missing when Systemd enabled

IMPORTANT
Please read README and Docs before creating the issue.
Please fill out the below information:
Describe the issue
When Systemd on my subsystem started working by accident, I found that all my GUI apps can only be opened via X11. Then I found that there was no wayland-0 in /run/user/1000. I do not know why the socket was gone, but it seems to be related to Systemd. Though I wrote a script as an alternative workaround, the problem has not been really solved. Wayland socket exists in Ubuntu WSL with Systemd running, so it does not seem to be an issue of WSL.
To Reproduce
Just try to make Systemd work
Expected behavior
Wayland socket exists, and GUI apps can use it.
Screenshots
If applicable, add screenshots to help explain your problem.
Enviroment:

Windows build number: 10.0.22631.3296
Security Software: Windows Defender
WSL version 1/2: WSL2
ArchWSL version: <IP_ADDRESS>
ArchWSL Installer type zip/appx/other clean/update: scoop/zip
Launcher version: 23072600

Additional context

To make Systemd work, first I tried to add something to %USERPROFILE%\.wslconfig according to #356 to disable cgroups v1, but it did not work. Then I found another article and modified .wslconfig according to it, and it worked. I renamed .wslconfig to .wslconfig1 without modifying it to enable cgroups v1, and Systemd was also working somehow. But when I tried to rename .wslconfig1 back without modifying it to disable cgroups v1, backup the origional ext4.vhdx, unregister ArchWSL, and then re-install it with a new ext4.vhdx, Systemd did not work. So I actually have no idea about how to make Systemd work.
Eventually, inspired by a post, I wrote a script, which links everything in /mnt/wslg to /run/user/$UID at startup, as an alternative workaround. Copy the content below and paste it to<EMAIL_ADDRESS>to "solve" the problem:[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* /run/user/"%i

@9numbernine9

Does wayland-0 exist in /run/user/$UID with version <IP_ADDRESS>? I found that wayland-0 is missing in version <IP_ADDRESS> when Systemd accidentally enabled, see [this issue]

No, it doesn't.

So Wayland does not work, right? If it works, what is $XDG_RUNTIME_DIR?

The command from https://github.com/microsoft/wslg/issues/1032#issuecomment-1502152914 solves the issue for me, and it seems it is fixed in mainline WSL
ln -s /mnt/wslg/runtime-dir/wayland-0* /run/user/1000/

The root cause is Arch mounts /tmp and /run/user/1000 as tmpfs after startup, make the existing /tmp/.X11-unit/X0 and /run/user/1000/wayland-0 unavailable.
Disable tmp.mount is one useful solution, but I recommend:
$ cat /etc/tmpfiles.d/wslg.conf
# See tmpfiles.d(5) for details
# link WSLg display files after system started

# Type Path              Mode UID  GID  Age Argument
L+     /tmp/.X11-unix/X0 -    -    -    -   /mnt/wslg/.X11-unix/X0

I have no idea how to disable mounting /run/user/1000 as tmpfs, so I recommend:
$ cat ~/.config/user-tmpfiles.d/wslg.conf
# Type Path              Mode UID  GID  Age Argument
L+     %t/wayland-0      -    -    -    -   /mnt/wslg/runtime-dir/wayland-0
L+     %t/wayland-0.lock -    -    -    -   /mnt/wslg/runtime-dir/wayland-0.lock
L+     %t/pulse/native   -    -    -    -   /mnt/wslg/runtime-dir/pulse/native
L+     %t/pulse/pid      -    -    -    -   /mnt/wslg/runtime-dir/pulse/pid
L+     %t/dbus-1         -    -    -    -   /mnt/wslg/runtime-dir/dbus-1

$ systemctl --user enable systemd-tmpfiles-setup.service systemd-tmpfiles-clean.timer

The root cause is Arch mounts /tmp and /run/user/1000 as tmpfs after startup, make the existing /tmp/.X11-unit/X0 and /run/user/1000/wayland-0 unavailable.
Disable tmp.mount is one useful solution, but I recommend:
$ cat /etc/tmpfiles.d/wslg.conf
# See tmpfiles.d(5) for details
# link WSLg display files after system started

# Type Path              Mode UID  GID  Age Argument
L+     /tmp/.X11-unix/X0 -    -    -    -   /mnt/wslg/.X11-unix/X0

I have no idea how to disable mounting /run/user/1000 as tmpfs, so I recommend:
$ cat ~/.config/user-tmpfiles.d/wslg.conf
# Type Path              Mode UID  GID  Age Argument
L+     %t/wayland-0      -    -    -    -   /mnt/wslg/runtime-dir/wayland-0
L+     %t/wayland-0.lock -    -    -    -   /mnt/wslg/runtime-dir/wayland-0.lock
L+     %t/pulse/native   -    -    -    -   /mnt/wslg/runtime-dir/pulse/native
L+     %t/pulse/pid      -    -    -    -   /mnt/wslg/runtime-dir/pulse/pid
L+     %t/dbus-1         -    -    -    -   /mnt/wslg/runtime-dir/dbus-1

$ systemctl --user enable systemd-tmpfiles-setup.service systemd-tmpfiles-clean.timer

The root cause is Arch mounts /tmp and /run/user/1000 as tmpfs after startup, make the existing /tmp/.X11-unit/X0 and /run/user/1000/wayland-0 unavailable.
 Also, I tried to add L+ /run/user/1000/wayland-0 - - - - /mnt/wslg/runtime-dir/wayland-0 to /etc/tmpfiles.d/wslg.conf, but it did not work, why?

system-tmpfiles.d and user-tmpfiles.d are different services, you cannot write conf in one file

/usr/lib/systemd/system/systemd-tmpfiles-setup.service
/usr/lib/systemd/user/systemd-tmpfiles-setup.service

Writing /run/user/1000/wayland-0 to /etc/tmpfiles.d/ is useless

file owner and group are wrong
/run/user/1000/ will be remounted as tmpfs later, clear the file

The only global conf location for user-tmpfiles.d is /usr/share/user-tmpfiles.d/*.conf
but user systemd-tmpfiles-setup is not enabled by default in arch, you have to enable it for each user.

this user service may works globally for each user(incomplete and untested):

$ cat /etc/systemd/user/wslg-user-runtime-dir.service
[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* /run/user/"%i

system-tmpfiles.d and user-tmpfiles.d are different services, you cannot write conf in one file

/usr/lib/systemd/system/systemd-tmpfiles-setup.service

/usr/lib/systemd/user/systemd-tmpfiles-setup.service

Writing /run/user/1000/wayland-0 to /etc/tmpfiles.d/ is useless

file owner and group are wrong

/run/user/1000/ will be remounted as tmpfs later, clear the file

The only global conf location for user-tmpfiles.d is /usr/share/user-tmpfiles.d/*.conf
but user systemd-tmpfiles-setup is not enabled by default in arch, you have to enable it for each user.

this user service may work globally for each user(incomplete and untested):

$ cat /etc/systemd/user/wslg-user-runtime-dir.service
[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* /run/user/"%i

Well, I think 4 should work, because my link.conf is completely same with your wslg-user-runtime-dir.service

We'd better use %t as XDG_RUNTIME_DIR
$ cat /etc/systemd/user/wslg-user-runtime-dir.service
[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t

We'd better use %t as XDG_RUNTIME_DIR
$ cat /etc/systemd/user/wslg-user-runtime-dir.service
[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t

I've tried this, but it did not work in my link.conf.

We'd better use %t as XDG_RUNTIME_DIR
$ cat /etc/systemd/user/wslg-user-runtime-dir.service
[Service]
ExecStart = sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t

I've tried this, but it did not work in my link.conf. Maybe I need to export "ln -fs /mnt/wslg/runtime-dir/* "%t to a file to find out why it didn't work

Well, I added sh -c "echo "%t" > /home/[username]/aaa.txt" in my link.conf, and found that %t is /run.
As for your systemd-tmpfiles-setup.service, I could not even start it. When I inputed sudo systemctl start /etc/systemd/user/wslg-user-runtime-dir.service in my terminal, it told me "Failed to start etc-systemd-user-wslg\x2duser\x2druntime\x2ddir.service.mount: Unit etc-systemd-user-wslg\x2duser\x2druntime\x2ddir.service.mount not found."; when I typed sudo systemctl start wslg-user-runtime-dir.service, it said "Failed to start wslg-user-runtime-dir.service: Unit wslg-user-runtime-dir.service not found." Please tell me how to start it. Thanks 😂

I guess that your<EMAIL_ADDRESS>is part of user init process, not a standalone user service.
User's XDG_RUNTIME_DIR is not done , when sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t executed.

Maybe. BTW, do you know how to start your wslg-user-runtime-dir.service?

$ cat /etc/systemd/user/wslg-runtime-dir.service
[Service]
Type=oneshot
ExecStart=sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t

[Install]
WantedBy=default.target

$ sudo systemctl --global enable wslg-runtime-dir
Created symlink /etc/systemd/user/default.target.wants/wslg-runtime-dir.service → /etc/systemd/user/wslg-runtime-dir.service.

It works! Thank you so much!

$ cat /etc/systemd/user/wslg-runtime-dir.service
[Service]
Type=oneshot
ExecStart=sh -c "ln -fs /mnt/wslg/runtime-dir/* "%t

[Install]
WantedBy=default.target

$ sudo systemctl --global enable wslg-runtime-dir
Created symlink /etc/systemd/user/default.target.wants/wslg-runtime-dir.service → /etc/systemd/user/wslg-runtime-dir.service.

tanks this worked, I would like to ask permission to create a gist script for this

tanks this worked, I would like to ask permission to create a gist script for this

Did you ever create a gist script for this? Thanks!


Hi ajrcampbell，will the complete code be release?

Hi @jukebox333 I will updating the repo with the code in the next few weeks. Thank-you for your interest!

Thanks a lot！

Hi @jukebox333 I will updating the repo with the code in the next few weeks. Thank-you for your interest!

Hi ajrcampbell, will this repo be updated recently


rock paper scissor

Fix to  Issue #
===============================

===============================
Checklist

[x] I read the contributing guidelines
[x] I structured my project as stated in the contributing guidelines
[ ] My project uses dependencies
[x] I starred the repo
[x] I had fun contributing!

Project reviewed and merged.
Thank you @sulavmhrzn
Feel free to add more projects.


Fix unpack multiple layers

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>If there are multiple layers, it will only unpack a layer and then return.
This pr fix this.

@runcom  @jonboulle  updated

LGTM

LGTM (IANAM)

LGTM


Selecting "Xpress (>= 8.3)" conflict with "Sensibilité" for Xpansion launch

Description
Provide a clear and concise description of the issue.
Steps to Reproduce
Steps to reproduce the behavior:

Start a new run
Select xpansion
Select Xpress (>= 8.3)
Select sensitivity
Select an output

Actual Behavior
Xpansion run starts but sensitivity option was not taken into account
Expected Behavior
When selecting "Sensitivité" it should works
Screenshots
If applicable, add screenshots to help explain your problem.
Possible Solution
Probably else/if management in LaunchAntares.sh
Environment

[ ] Production
[ x] Staging

Additional Information
Add any other context about the problem here.
7fb9e97f-88fa-4178-a29e-e5a431f20b11

After analysis, this issue is part of a bigger one. Antares-Launcher and the shell scripts do not support more than one option in other_options.

Une précision : dans la classe SlurmLauncher, on gère bien plusieurs options séparées par un espace.

Yes but we do not handle it when we give the command line to SLURM, see this code :
args.extend(
            shlex.quote(arg)
            for arg in [
                self.solver_script_path,
                script_params.input_zipfile_name,
                str(script_params.antares_version),
                _job_type,
                str(script_params.post_processing),
                script_params.other_options,
            ]
        )

This issue concerns the launchAntares.sh script which is part of antares-cd projet.
@JasonMarechal25 , can you open an issue on Jira or in Rte-s GitLab?


Request: --requirements-file to support setup.py

I think it would be useful if --requirements-file could support setup.py.  It seems that currently flake8-requirements assumes the requirements come from a requirements.txt.
Use case is a monorepo with:

setup.cfg containing known-modules in the directory where flake8 is being invoked
setup.py containing requirements in another directory

Thank you in advance for entertaining this request 😃

I am not sure why I opened this, but setup.py is supported: https://github.com/arkq/flake8-requirements/blob/v1.7.2/src/flake8_requirements/checker.py#L651


fix: respect patch policy merge options

Fixes https://github.com/crossplane-contrib/function-patch-and-transform/issues/90.
Almost identical to the upstream implementation.

Damn, I was really hoping we could avoid this and let SSA do all the merging etc. Obviously we can't do that in this context though, where we're just merging patches into the base template before even applying anything.
A few thoughts:

I'd like to fix the naming of these options, since moving to this function is a breaking change. See https://github.com/crossplane/crossplane/issues/2581.
The README says mergeOptions are no longer supported, which won't be true anymore.
It would be useful to make it clear that these options are only used to merge the patch into the base, not to merge the patch into the existing resource. Maybe just in the Godoc for the mergeOptions field?

I'd like to fix the naming of these options

Maybe something like:
      policy:
        fromFieldPath: Required
        toFieldPath: Merge

The options for toFieldPath would be:

Replace, the default behavior.
AppendArray - equivalent to mergeOptions.appendSlice
MergeObject - equivalent to mergeOptions.keepMapValues

I could imagine just Replace and Merge as options too. If it was an array we'd "merge" the two arrays by appending.

I do agree we could improve names, but changing them would mean a lot of confusion for users, we could start implementing them as they are, I think the number one goal for this function is a smooth transition path from native p&t. We could think of deprecating the field upstream and push people to the new toFieldPath policy first and handle it here too.

@phisco Please let's fix these names while we have the chance. We've already made breaking changes in this function (e.g. making fields that weren't required before required), and we have a migration tool we can update to handle the renaming.

we should at least properly validate the input against the crd to be sure we don't silently ignore it because a user is using the old name by mistake.

Yeah I was thinking the same. Silently accepting unknown fields makes this worse. A quick fix (easier than validating using the CRD) would be to use https://pkg.go.dev/encoding/json#Decoder.DisallowUnknownFields.

We should probably think about doing it upstream, but implementing it here will take less time. Wdyt?

You mean addressing https://github.com/crossplane/crossplane/issues/2581? Sure. If an API like the one I proposed works we could just mark mergeOptions deprecated and introduce the new toFieldPath.

You mean addressing crossplane/crossplane#2581? Sure. If an API like the one I proposed works we could just mark mergeOptions deprecated and introduce the new toFieldPath.

I meant validating against the CRD, but your option of strictly decoding is indeed easier. Regarding the API, yes, I think it looks good to me. Nothing against moving forward with that upstream.

opened https://github.com/crossplane/function-sdk-go/pull/121 to allow setting RejectUnknownMembers here.

Would be great if this could be merged. Readding mergeOptions would make migration from c/c much easier.

Note for a follow-up PR: If we stick with AppenSlice etc. we might want to add a PrependSlice option as well.

Ok, I switched to the suggested names, let me know if there is anything else, @negz 🙏


Fix markdown URL parsing

This PR fixes some URL parsing bugs in markdown render.

Close https://github.com/go-gitea/gitea/issues/17625
Add one-level sub-path support to anySHA1Pattern (hacky)
Fix wrong usage of setting.AppSubURL, rename const AppSubURL to const TestRepoURL

For test content reported in #17625 :
1. issue with line permalinks https://try.gitea.io/ktdkydkycoyf/ex/src/commit/a702ddb6e48b4b6a6cf002fe78b2a051b3c030f6/example.txt#L2:
2. issue with file permalinks https://try.gitea.io/ktdkydkycoyf/ex/src/commit/a702ddb6e48b4b6a6cf002fe78b2a051b3c030f6/example.txt:
3. issue when comparing two commits https://try.gitea.io/ktdkydkycoyf/ex/compare/e4787c3b4c8a4c301081c3f188d7fc73096a38b8...a702ddb6e48b4b6a6cf002fe78b2a051b3c030f6

Before

After

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a6f961f). Click here to learn what that means.
The diff coverage is 77.41%.

@@           Coverage Diff           @@
##             main   #17924   +/-   ##
=======================================
  Coverage        ?   45.35%
=======================================
  Files           ?      815
  Lines           ?    90752
  Branches        ?        0
=======================================
  Hits            ?    41162
  Misses          ?    43022
  Partials        ?     6568

Impacted Files
Coverage Δ

modules/markup/html.go
79.04% <77.41%> (ø)

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 a6f961f...d71fed9. Read the comment docs.

Hmm... This pr basically makes auto URLs only work if they're ASCII. This would prevent auto linking of things like: https://example.com/Verknüpfung/auf/Zeug
The main issue, apart from the compare URL, appears to be terminal punctuation - I wonder if we should just be checking if the final character is punctuation and if so just removing it like you've proposed for the terminal dot might just work instead.

Hmm... This pr basically makes auto URLs only work if they're ASCII. This would prevent auto linking of things like: https://example.com/Verknüpfung/auf/Zeug
The main issue, apart from the compare URL, appears to be terminal punctuation - I wonder if we should just be checking if the final character is punctuation and if so just removing it like you've proposed for the terminal dot might just work instead.

Yep, I made it only works for ASCII URL by purpose. Because due to RFC, the URL should be correctly encoded.
Especially for non-Latin family languages (eg: Korean/Japanese/Chinese), there is no space between URL and sentences. It's more difficult to guess and parse "这个https://xxx/描述了一个问题"

Oh, by the way, I only changed the anySHA1Pattern and comparePattern.
So if there is an external URL like https://example.com/Verknüpfung/auf/Zeug, the behavior is not changed. It should work as before.

🚀


xunit testcase name inconsistent and not inherited from casperjs

The JUnit XML report created by CasperJS+PhantomCSS is inconsistent in the naming of testcases.
The output of phantomCSS evaluation goes to the name of the testcase within the XML report.
<testcase name="No changes found for screenshot /Users/smsf/PhantomCSS/screenshots/open coffee machine button_0.png" classname="demo/testsuite" time="0.129"/>

If the same test fails, the testcase is named in other way:
<testcase name="Visual change found for screenshot /Users/smsf/PhantomCSS/screenshots/coffee machine dialog_1.png (10.72% mismatch)" classname="demo/testsuite" time="0.442"><failure type="fail"><![CDATA[Visual change found for screenshot /Users/smsf/PhantomCSS/screenshots/coffee machine dialog_1.png (10.72% mismatch)]]></failure></testcase>

The problem seems that PhantomCSS is not explicitly naming the testcases
function _onPass( test ) {
        console.log( 'PPPPPPPPPPPPPP\n' );
        console.log( JSON.stringify(test) );
        casper.test.pass( 'No changes found for screenshot ' + test.filename,  {name: test.name} );
}

function _onFail( test ) {
        console.log( 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\n' );
        console.log( test );
        casper.test.fail( 'Visual change found for screenshot ' + test.filename + ' (' + test.mismatch + '% mismatch)', {name: test.name});
}

function _onTimeout( test ) {
        console.log( '\n' );
        casper.test.info( 'Could not complete image comparison for ' + test.filename );
}

function _onNewImage( test ) {
        console.log( '\n' );
        casper.test.info( 'New screenshot at ' + test.filename );
}

As mentioned in CasperJS documentation (http://docs.casperjs.org/en/latest/testing.html), it's possible to name a testcase explicitly as seen bellow.
casper.test.fail('google search for "casperjs" retrieves 10 or more results', {name: 'result count is 10+'});

However, it seems that the "test" object received by the PhantomCSS callbacks don't have access to the casperJS message argument that can be passed to the assertions.
The testcases names should be consistent, and my suggestion which is the approach followed by casperjs, is to use the optional "message" argument to the assert statements as the name of the Xunit testcase.
This can easily be verified using PhantomCSS's sample demo and requesting the xunit XML report:
casperjs test demo/testsuite.js  --xunit=x.xml

It can't pass more context to the test, as the assertion happens after the actual test execution.  But I made the following change to ensure that the testname is always the same whilst preserving decent messaging on the command line.  You can of course override those callbacks for your own purposes.
function _onPass( test ) {
	console.log( '\n' );
	var name = 'Should look the same ' + test.filename;
	casper.test.pass(name, {name: name});
}

function _onFail( test ) {
	console.log('\n');
	var name = 'Should look the same ' + test.filename;
	casper.test.fail(name, {name:name, message: 'Looks different (' + test.mismatch + '% mismatch) ' + test.failFile });
}

Hi @jamescryer,
thanks for your feedback.
Your solution works and seems reasonable so I kindly ask you to consider it both for the v0 and master branches.
By the way, we here at "Xpand add-ons" will be referring PhantomCSS from a tutorial that we are going to provide for our test management tool for JIRA: Xray for JIRA.
Many thanks.

I don't have the time to maintain the v0 branch; I recommend everyone to update to v1/master.
Thanks

Ok but the v1/master branch is giving errors if you try to run the demo/testsuite :(


Large pause on loading a new project

Describe the bug
Program goes blank for nine seconds while loading a project from the 'open project' dialogue. Same delay happens regardless of project contents. Blank, new project with a single scene, large project. All seem to have the same delay.
To Reproduce
Steps to reproduce the behavior:

Open gb studio
see 'open projects' dialogue
Open a project
Wait
and wait
and wait
Project loads

Expected behavior
Loading with less lag (this lag is a new issue in 1.2)
Screenshots

Platform (please complete the following information):

OS: Win 8.1
App version 1.2

Need more computer specs than just OS.

laptop or desktop
Ram
Cpu
Solid state drive or hard disk
64bit or 32bit
Anything else.

You can find some of these by going to My Computer / This PC
Right clicking the blank background, and selecting properties.
Key words that hopefully show up when searching
Optimize Performance

Model
CZ CP Series (laptop)
Processor
Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz 2.50GHz
Installed memory (RAM)
16.0 GB (15.8 GB usable)
Graphics
NVIDIA GeForce GTX 860M
System type:
64-bit Operating System, x64-based processor
Drive type
SSD


Set Modal.openCount floor to 0

Fixes bug described in https://github.com/reactstrap/reactstrap/issues/1279 where Modal.openCount becomes negative after multiple .destroy() calls, preventing "modal-open" from being added to document.body.
Solution is prevent Modal.openCount from going below a minimum of 0, rejecting decrements that result in an erroneous negative value.

[x] Bug fix
[ ] New feature
[ ] Chore
[ ] Breaking change
[x] There is an open issue which this change addresses
[x] I have read the CONTRIBUTING document.
[x] My commits follow the Git Commit Guidelines
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

It doesn't actually fix it I think. You might have a few opened modal windows, so a few calls of destroy will lead to incorrect openCount value


refactor: small renaming

This change is

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

Project coverage is 77.84%. Comparing base (1631047) to head (3bc9f66).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1905   +/-   ##
=======================================
  Coverage   77.84%   77.84%
=======================================
  Files          61       61
  Lines        8744     8744
  Branches     8744     8744
=======================================
  Hits         6807     6807
  Misses       1497     1497
  Partials      440      440

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


EPERM: operation not permitted, lstat amplify-codegen-temp\temp-console-log.txt

Hi Team,
I am trying to do a amplify push and getting the below error:
EPERM: operation not permitted, lstat 'C:\Users\PK\Desktop\WORKSPACE\my-project\amplify-codegen-temp\temp-console-log.txt'
Since I am using windows, amplify is not recognized. Hence the actual command I am trying is below.
C:\Users\PK\AppData\Roaming\npm\amplify.cmd push --allow-destructive-graphql-schema-updates
But I get the above mentioned error. Seems like permission issue but I am not sure how/what/where to change the permissions.
Please suggest.

Hi @pavankumarn05, what version of the Amplify CLI were you using? I believe there was a bug in the version released as 11.0.4 and 11.0.5 which had to do with access to some local files, which has been resolved in the latest version.


Use correct SPDX license ident

Previous changes referenced the wrong SPDX

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Refactoring: have one file for docker image CI instead of two

⚠ Should be done once https://github.com/meilisearch/MeiliSearch/pull/1897 is merged
We should find a way to have only one file related to the docker image CI instead of two, for maintenance reasons.
Here are the current files:

https://github.com/meilisearch/MeiliSearch/blob/main/.github/workflows/publish-docker-latest.yml: publish the git tag as docker tag
https://github.com/meilisearch/MeiliSearch/blob/main/.github/workflows/publish-docker-tag.yml: publish the latest tag

-> The CI logic should be handled in one file only.

Is this issue still open or was it addressed in #1897 ?


Improve messaging when we can't find a package matching the constraint

When I run bin/pie download xdebug/xdebug:3.4.0alpha1, I see:
Unable to find an installable package xdebug/xdebug for version 3.4.0alpha1

It does not tell me why it can't find it, as there is certainly a release on packagist.

When you run bin/pie download xdebug/xdebug:3.4.0alpha1@alpha this works.
In this case, it is because the default stability flag is stable. This may be because we're missing something in version resolution in Composer, but either way, this could be improved with better messaging.

This also applies when the downstream dependency depends on an extension that is missing. For example, I built PHP 7.4 using --disable-json and tried to install mongodb/mongodb-extension:
$ bin/pie download --with-php-config=/home/james/workspace/oss/php-src-build/bin/php-config mongodb/mongodb-extension:v1.x-dev@dev
You are running PHP 8.3.10
Target PHP installation: 7.4.33 ts, on Linux/OSX/etc x86_64 (from /home/james/workspace/oss/php-src-build/bin/php)

In UnableToResolveRequirement.php line 16:

  Unable to find an installable package mongodb/mongodb-extension for version v1.x-dev@dev.

download [--with-php-config [WITH-PHP-CONFIG]] [--with-php-path [WITH-PHP-PATH]] [--] <requested-package-and-version>

Whilst it is correct, it is not particularly helpful in telling the user that the only thing preventing installation is that ext-json is missing... :sweat_smile:


Add 'count' textbox to Recent Favorite Statistics part of the main page of twitterapi project

the project was done, so this becomes unimportant, hence closed.


Don't see the buid directory

Hi,
I am new to swift development(and its build system) and I cannot find the .build/debug directory. It built successfully so it's obviously something I am missing.

You're going to have to give us a little more info.  How'd you get the code?  How'd you do a build?  etc.

I found the build folder after checking out the tagged branch. It was a confusion on my part.


change dotnet clustertask name

this change dotnet clustertask name s2i-dostnet3 to s2i-dotnet-3
to maintain the consistency among others

/approve
/lgtm


Is "Cherry Pick not supported" really very precise?

We use Release Flow and so we do hotfixes in feature branches off master, merged back then cherry pick that master commit into the last release branch
From the little I know of ADF source control, and the description in this article, I don't really understand why this wouldn't work.
By their nature hotfixes must be minor code changes otherwise they introduce significant risk with any programming language. We wouldn't be introducing new Datasets or Pipelines we would just be modifying the logic/properties inside these existing objects directly
Unless I am wrong on this due to my current inexperience with ADF, please clarify/refine this. This article is prescribing a specific approach to hotfixing which has its own tradeoffs - for example, your merge back to master may equally break your master ADF codebase - this should be indicated as an approach and that other approaches are available with the appropriate cautions.
It is also saying that an GIT function that I believe could work will not. I think it is better to be more explicit about the kinds of things that would actually cause the breakage (as is done partially) without that blanket "does not support" statement.

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

ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
Content: Continuous integration and delivery in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/continuous-integration-deployment.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@o-o00o-o Thanks for the feedback! We have assigned the issue to the content author to further review the feedback and provide an update as appropriate.

Hi @o-o00o-o,
Thanks for reaching out. ADF source control is just an implementation of DevOps source control. If you have a git process that works for you, I suggest you continue to use it.
This article is in the process of being updated and I will take your feedback into consideration. Our goal with the hot-fix section is to guide users to a pattern that will not break them.
Thanks,
Daniel

Thanks for clarifying Daniel, all understood. Glad we can continue to use release flow with ADF and it is useful that the article highlights the inter dependencies - most code has some interdependence so saying cherry pick isn't supported I think is a bit misleading
Get Outlook for Androidhttps://aka.ms/ghei36

From: Daniel Perlovsky<EMAIL_ADDRESS>Sent: Tuesday, April 21, 2020 8:37:57 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Brett Gerhardi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Is "Cherry Pick not supported" really very precise? (#52969)
Hi @o-o00o-ohttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fo-o00o-o&data=02|01||9881fd4ab5624c0ee71508d7e62b7edb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637230946788795161&sdata=hCfhWSudHVuhU3e%2Fw2OTMKNIIJoHTINfmK%2FH8JzsD9E%3D&reserved=0,
Thanks for reaching out. ADF source control is just an implementation of DevOps source control. If you have a git process that works for you, I suggest you continue to use it.
This article is in the process of being updated and I will take your feedback into consideration. Our goal with the hot-fix section is to guide users to a pattern that will not break them.
Thanks,
Daniel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F52969%23issuecomment-617371560&data=02|01||9881fd4ab5624c0ee71508d7e62b7edb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637230946788795161&sdata=u9L7Gz%2FasyXqELWAfX4m0u%2BKmZn36B1T5mY7PP8YPnY%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADIPBZ2R2M2EXX72H3VYIB3RNXYZLANCNFSM4MNQJURQ&data=02|01||9881fd4ab5624c0ee71508d7e62b7edb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637230946788805160&sdata=YpoPad0LrSSlhYAUjzPJdOVzdwM1IqUysJarbxiqHVY%3D&reserved=0.

Hey @o-o00o-o ,
Thanks for the feedback! Just updated the article so hopefully it is clearer. May take 24 hrs to go live. I'm going to go ahead and close this issue as it seems you are unblocked. If you have any more questions feel free to comment.
Thanks,
Daniel
#please-close


Blog: Gone Phishing

[] Foo
[] Bar

[ ] Fix title's
[ ]Add information about evilginx 2fa bypass
[ ]Add takeaways
[ ]Add how to defend
[ ] Fix virtual host information
[ ] Add photo's


[Lint] Fix autofixable lint errors

This PR cleans up auto fixable errors by running eslint --fix. A follow up PR will clean up those errors that are not auto fixable.
Then we can add lint to the buildkite pipeline.
Unsure how I officially accept the license agreement.

@feedmeapples done


aiStarter doesn't work in Raspberry Pi

After following the instructions on how to install aiStarter in Linux/Debian, still couldn't make it work, getting errors like.  "Error in the Exec format" - and when trying to run as a Sudo "Syntax error: work unexpected (Expecting ")");
We're using OS Raspbian (based in Linux/Debian) and the processor has an ARMHF architecture.
I'm not sure, but I think the some of the problems might be due to the architecture of the processor when installing in the .deb file.
Installed in ubuntu and Mint to te
st it and it worked fine, but I can't change the Raspberry to either of these OS.
I need to make the USB connection with the rapsberry pi and the mobile phone, Any idea what might be happening?

Your intuition is correct. The .deb file bundles only x86 binaries, it does not include arm binaries. A rough sketch of how you might be able to work around it:

sudo apt-get install adb to get adb installed
Download the aiStarter.py and bottle.py files from appinventor/misc/emulator-support
Create a directory to house your "aiStarter" installation (INSTALLDIR), and create a directory commands-for-Appinventor (COMMANDDIR)
Create a symlink to which adb in $COMMANDDIR
Modify aiStarter.py by changing PLATDIR from /usr/google/appinventor/ to INSTALLDIR
Run python aiStarter.py

This will run an interpreted version of aiStarter that makes use of the arm version of adb. You may need to do additional configuration in your system to make sure adb can talk to your Android device over USB. You should be able to test that is working by running adb shell to open a shell on your device.

Hey man, thanks for the help.
I tried doing what you said, it seem that i can connect my phone in the adb and run the aiStarter separately, but as soon as I connect my phone and try to Connect>USB in the website I'm getting some error like this (image below).

I might have screwed something thing up, any idea what this errors mean (my fault or still needs something to run properly)?
I didn't create the symlink but i did put the files in the the folder.
I'll try installing in a different Raspberry Pi to see if I get a different result.
Thanks

The problem is that you need the adb command to be the version that is compiled for arm. If you haven't replaced /usr/google/appinventor/adb, then you are still using the x86 version bundled in the deb. Remove the copy of adb there and replace it with a symlink to the one in /usr/bin (if installed using apt-get) and it should no longer give you the exec format error. Well, assuming that apt-get installs the arm version, that is.

Worked like a charm!
thanks a lot @ewpatton!


The issue with the test results.

I don't quite understand something. During training, I see that the I-AUC can reach an ideal value of 1.00 in mvtec_grid. However, when I only test the mvtec_grid, the instance_auroc and full_pixel_auroc are only 0.63 and 0.29, and the segmentation images are also disappointing.  respectively. Could you please explain why this is happening?Below, I will attach screenshots from the training, screenshots from the test, and segmentation result images to facilitate your analysis.!


fix: write snapshots to disk even if FS is mocked

Summary
We have a general problem in that when a user messes with globals, or requires node core modules, they get the same copy as we get. That means we have to make sure to work, even if users do global.Promise = undefined or fs.writeFileSync = () => {}.
We really should solve it generally (stick all globals and core modules on some Symbol known only to Jest?), but this solves it for the case of snapshots and FS mocking.
Fixes #5270. Without the changes in this PR, the snapshot would be reported as written, but not actually written to disk.

 I thought that was TS's thing...

Of course, we've had that issue for years, though. And I noted it in the OP. Ideas welcome! :D

Ah, good idea!

@mattphillips @thymikee updated