added test goodfeaturetotrack.cpp

Added missed accuracy test for goodFeaturesToTrack functions from opencv_imgproc module

@AlexanderUsentsov, thank you for the PR. There are still failing tests: http://pullrequest.opencv.org

I am working on these issues.
Thank you.
Alexander
From: Vadim Pisarevsky<EMAIL_ADDRESS>Sent: Tuesday, January 20, 2015 4:04 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, thank you for the PR. There are still failing tests: http://pullrequest.opencv.org
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-70649859.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, any progress?

Hello, Ilya!
I have fixed all bugs in accuracy test from opencv_test_imgproc but can’t  fix issues in CV_FeatureDetectorTest::regressionTest() from opencv_test_features2d .
I see that result is compared with some test data from ..\opencv_extra-master\testdata/cv/features2d/feature_detectors/detector-harris.xml.gz files.  As I changed code of this function  I receive different results to compare with old code. To fix this issue I need to change detector-harris.xml.gz file.
Could you help me to generate new test data file?
Thank you,
Alexander
From: Ilya Lavrenov<EMAIL_ADDRESS>Sent: Saturday, February 21, 2015 12:47 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, any progress?
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-75364330.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, please, use this guide to update the performance data:
http://code.opencv.org/projects/opencv/wiki/HowToUsePerfTests#How-to-update-perf-data
the updated data should be contributed to opencv_extra from the branch with the same name ("good_feature" in this case)

Thank you.
I updated the performance data, contributed to opencv_extra from the "good_feature" branch and opened new pull request from this branch. Unfortunately I don’t see start of building and testing . Where am I wrong?
BR,
Alexander
From: Vadim Pisarevsky<EMAIL_ADDRESS>Sent: Monday, March 2, 2015 2:58 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, please, use this guide to update the performance data:
http://code.opencv.org/projects/opencv/wiki/HowToUsePerfTests#How-to-update-perf-data
the updated data should be contributed to opencv_extra from the branch with the same name ("good_feature" in this case)
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-76699991.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, I've restarted the builds.

I’ve updated test data. Will you restart the build or I need to do something for that?
BR,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Tuesday, March 17, 2015 4:40 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I've restarted the builds.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-82357117.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

opened new pull request from this branch

@AlexanderUsentsov, I don't see any PRs to opencv_extra from you. Can you take a look?
Although your branch is used during the build, you still need to create PR in case to merge it.

Hi!
I’ve analyzed result of testing and see that  Features2d_Detector_Harris.regression test fails because ../opencv_extra-master/testdata/cv/features2d/feature_detectors/detector-harris.xml.gz files has data for previous variant of goodFeaturesToTrack. Could you help me to generate new test data file for this test?
BR,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Tuesday, March 24, 2015 6:07 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
opened new pull request from this branch
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I don't see any PRs to opencv_extra from you. Can you take a look?
Although your branch is used during the build, you still need to create PR in case to merge it.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-85543552.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hi!
This is a friendly reminder.
BR,
Alexander
From: Usentsov, Alexander
Sent: Tuesday, April 7, 2015 7:21 PM
To: Itseez/opencv; Itseez/opencv
Subject: RE: [opencv] added test goodfeaturetotrack.cpp (#3540)
Hi!
I’ve analyzed result of testing and see that  Features2d_Detector_Harris.regression test fails because ../opencv_extra-master/testdata/cv/features2d/feature_detectors/detector-harris.xml.gz files has data for previous variant of goodFeaturesToTrack. Could you help me to generate new test data file for this test?
BR,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Tuesday, March 24, 2015 6:07 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
opened new pull request from this branch
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I don't see any PRs to opencv_extra from you. Can you take a look?
Although your branch is used during the build, you still need to create PR in case to merge it.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-85543552.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hi!
I’ve update  opencv_extra and sent PR.  Unfortunately testing is not start.
Could you describe the procedure how to start testing after update testdata?
BR,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Tuesday, March 24, 2015 6:07 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
opened new pull request from this branch
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I don't see any PRs to opencv_extra from you. Can you take a look?
Although your branch is used during the build, you still need to create PR in case to merge it.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-85543552.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, I still can not find your PR to opencv_extra: here. However, your branch is actually used for testing, please, see last build logs: linux-build-3044 -> merge opencv_extra test branch
As for generating test data, as I can see in the test, you need to remove old validation file and run corresponding regression test - it should create the new file in this case.

I have two branches with name good_feature : first one for  opencv, and second  for opencv_extra. When I submit code in opencv good_feature branch testing is started. You see this result for my commit on Friday.
I set new PR when I submitted new  open_extra data today but tests didn’t start.
About generating new test data for regression test.
I deleted  detector-harris.xml.gz file and ran opencv_test_features2dd.exe --gtest_filter=Features2d_Detector_Harris.regression
New file was created but it has size 1 KB instead of 3KB. And test cannot load data from it.
If I run opencv_test_features2dd.exe I have the same result.
Thank you,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Monday, April 20, 2015 5:52 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I still can not find your PR to opencv_extra: herehttps://github.com/Itseez/opencv_extra/pulls. However, your branch is actually used for testing, please, see last build logs: linux-build-3044http://pullrequest.opencv.org/buildbot/builders/precommit_linux64/builds/3044 -> merge opencv_extra test branchhttp://pullrequest.opencv.org/buildbot/builders/precommit_linux64/builds/3044/steps/Merge opencv_extra with test branch/logs/stdio
As for generating test data, as I can see in the testhttps://github.com/Itseez/opencv/blob/master/modules/features2d/test/test_detectors_regression.cpp#L211, you need to remove old validation file and run corresponding regression test - it should create the new file in this case.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-94473550.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, buildbot service does not check for changes in opencv_extra, thus it does not start new build when new commit arrives into this repository. You can force the build by rewriting the last commit in opencv repository.
I've started new build manually.

I have two branches with name good_feature

And you need to create two pull requests, one for opencv (this one), another for opencv_extra.
Also, as I can see, the latest commit in your opencv_extra/good_feature branch was created 27 days ago. Are you sure you've pushed it today?
Can you, please, check the contents of generated file, is it xml packed in gz? Does it have same structure as previous?

@AlexanderUsentsov, I was able to generate test data file without any problems. It does not have detector_params section because this method is not implemented in new GFTTDetector class, but keypoints information is there and the test (Harris.regression) passes.

I am able to generate test data for Harris.regression test now.
Thank you,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Tuesday, April 21, 2015 12:53 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov, I was able to generate test data file without any problems. It does not have detector_params section because this method is not implemented in new GFTTDetector class, but keypoints information is there and the test (Harris.regression) passes.
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-94724193.

Closed Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

@AlexanderUsentsov, there are some tests failures with new version:

On MacOSX: OCL_Imgproc/GoodFeaturesToTrack.EmptyCorners takes more than 180 seconds and gets killed by build service
OCL_GoodFeaturesToTrackFixture_GoodFeaturesToTrack.GoodFeaturesToTrack perf tests failed
OCL_PyrLKOpticalFlowFixture_PyrLKOpticalFlow.PyrLKOpticalFlow perf tests failed

@AlexanderUsentsov , I have two more comments:

remove or rename the good_feature branch from your opencv_extra fork, otherwise the CI system will not be able to merge this PR
squash all commits into one before merge

@mshabunin, are we ready to merge it?

@vpisarev , no, not yet.
@AlexanderUsentsov , looks like the test itself is missing now. I have a backup of the previous state if you need it: mshabunin/opencv:good_feature

I am sorry.
Test was really missed in last commit.
BR,
Alexander
From: Maksim Shabunin<EMAIL_ADDRESS>Sent: Monday, December 7, 2015 1:40 PM
To: Itseez/opencv
Cc: Usentsov, Alexander
Subject: Re: [opencv] added test goodfeaturetotrack.cpp (#3540)
@vpisarevhttps://github.com/vpisarev , no, not yet.
@AlexanderUsentsovhttps://github.com/AlexanderUsentsov , looks like the test itself is missing now. I have a backup of the previous state if you need it: mshabunin/opencv:good_featurehttps://github.com/Itseez/opencv/compare/master...mshabunin:good_feature
—
Reply to this email directly or view it on GitHubhttps://github.com/Itseez/opencv/pull/3540#issuecomment-162478626.

Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

:+1;


AntonyCourtney.Tad version 0.12.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@trenly: wingetcreate apparently did not detect that the architecture is x64 not x86 (again, as you corrected the PR for the last version). Can you tell if this due to some misconfiguration in the Tad installer or a bug in wingetcreate that should be filed there?

@Trenly: wingetcreate apparently did not detect that the architecture is x64 not x86 (again, as you corrected the PR for the last version). Can you tell if this due to some misconfiguration in the Tad installer or a bug in wingetcreate that should be filed there?
Maybe related to microsoft/winget-create#329?

Wingetcreate looks at the installer's architecture to try and determine which it is. In this case, the installer is compiled for x86, even though the application inside will only run on x64

https://github.com/microsoft/winget-create/issues/198

There are a few ways to work around this.

Manually update after manifest creation
The publisher can update the installer URL to include _x64
You can use the architecture override syntax


Wrong Password error on wifi connection

I've tried connecting to 2.4g wifi and get wrong Password error after entering correct password.  I've change the access point names and passwords and still get error.
(I really like this hardware.  Nice job!)

It may be a WIFI signal problem, you may be able to check whether your information is correct.


NTR peroxide sensor activity

NTR peroxide sensor activity
Interacting selectively and non-covalently with and responding, e.g. by conformational change, to changes in the cellular level of hydrogen peroxide (H2O2).
PMID:20919928
parent GO:0140299    small molecule sensor activity
reference PMID:20919928
Two-component mediated peroxide sensing and signal transduction in fission yeast.
(I want this mainly so that I can purge
"detection of oxidative stress" and standardize the F-P links in this area)

@pgaudet  can we discuss/add today?

@ValWood
Are you OK with the standard definition for this term, 'Binding to hydrogen peroxide (H2O2) and eliciting a change in the protein's activity in response to the intracellular level of that small molecule.'?

Absolutely


Missing type checking on component parameters

When you put a [Parameter] on a component, and then invoke it with <MyComponent param=@someValue>, it doesn't do static type checking at compile-time to make sure that value will actually work.  All of the necessary information to do so is present, but no type-checking is done until runtime, when it attempts to set the parameter value through Reflection, making it possible for this to blow up with an InvalidCastException.
This should not be the case.

This should be added to #1

Good suggestion.
@rynowak The implementation that occurs to me would be changing the AddAttribute codegen to insert a cast to whatever the target parameter type is. I know that means an extra runtime cast, at least for non-sealed parameter types. Maybe the compiler is smart enough to no-op the cast if the parameter type is sealed (which would be true for a large proportion of cases where people are passing int, string, etc.).
Alternatively we could create an AddAttribute<T> that requires you to pass a T, but that might make our current overload selection mechanism quite difficult to reason about.
What do you think?

This seems pretty straightforward. We'll want to try both and choose based on which provides the better error message.

Adding a thunk that the generated code calls through is pretty straightforward, and seems to fix the problem pretty nicely. We don't have super fine-grained control over what the error message looks like, but I think it's actually pretty decent.

Implemented in 4dee648ab8b3f5b350f3587c5748faee372224ac


ceph-mgr: create keys for MGRs

Add code in ceph-mgr for creating a keyring for manager in so that
managers can be deployed on a separate node too.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1552210
Signed-off-by: Rishabh Dave<EMAIL_ADDRESS>(cherry picked from commit 56bfec7c58407e269f6e6fa7b4c8a5928953dc6f)

jenkins test luminous-centos-non_container-update

jenkins test luminous-centos-container-collocation


feat: auto reset wrapper

What?
The jumanji auto reset wrapper has a small bug, this is a stop gap PR so that we have access to it until that on is merged: https://github.com/instadeepai/jumanji/pull/223

Looks good to me @sash-a! Super clean 💪 Is this what you used for your SAC systems?

Yup, hopefully will be in jumanji soon though


E2E scheduling of pods to GW/NonGW nodes

Before this patch, E2E didn't have any control of where pods
landed, this made the testing of different scenarios random.
With this patch we ensure the testing of the datapath when
traffic needs to transit from a worker node to a gateway node.
Cluster type has been converted to an enumeration as part of this
commit.

@sridhargaddam @mpeterson I posted a second commit with your requested changes, please re-review.

The order does not matter , all tests execute in random order always.
Enviado desde mi iPhone

El 16 sept 2019, a las 20:18, Sridhar Gaddam<EMAIL_ADDRESS>escribió:
@sridhargaddam requested changes on this pull request.
In test/e2e/dataplane/tcp_pod_to_service.go:

@@ -15,8 +15,8 @@ var _ = Describe("[dataplane] Basic Pod to Service tests across clusters without
testPod2ServiceTCP(f, framework.NonGatewayNode, framework.NonGatewayNode)
})

It("Should be able to perform a Pod to Service TCP connection and exchange data between different clusters NonGW to GW", func() {

testPod2ServiceTCP(f, framework.NonGatewayNode, framework.GatewayNode)

It("Should be able to perform a Pod to Service TCP connection and exchange data between different clusters GW to GW", func() {
Thanks for addressing the other comments.

Lets validate GW to GW use-case before nonGW to nonGW (i.e., move this to line before 14).
If GW to GW fails, then the second use-case is bound to fail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The order does not matter , all tests execute in random order always.

I see, thanks for clarifying. LGTM.
Enviado desde mi iPhone

…
El 16 sept 2019, a las 20:18, Sridhar Gaddam @.***> escribió: @sridhargaddam requested changes on this pull request. In test/e2e/dataplane/tcp_pod_to_service.go: > @@ -15,8 +15,8 @@ var _ = Describe("[dataplane] Basic Pod to Service tests across clusters without testPod2ServiceTCP(f, framework.NonGatewayNode, framework.NonGatewayNode) }) -	It("Should be able to perform a Pod to Service TCP connection and exchange data between different clusters NonGW to GW", func() { -	testPod2ServiceTCP(f, framework.NonGatewayNode, framework.GatewayNode) +	It("Should be able to perform a Pod to Service TCP connection and exchange data between different clusters GW to GW", func() { Thanks for addressing the other comments. Lets validate GW to GW use-case before nonGW to nonGW (i.e., move this to line before 14). If GW to GW fails, then the second use-case is bound to fail. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

I had to fix conflicts with the SRC IP preservation changes.
Excuse the repetition which I'm handling in PR#149 in a different way (by making the framework a bit smarter and cleaner).. automating some of the repetitive tasks.


Encountered a panic

I've ran into a panic on linux/gnu running cargo run --release:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/daniel/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_egui-0.17.1/src/egui_node.rs:332:79

The UI Code is pretty minimal in a fresh project:
fn ui_example(mut egui_context: ResMut<EguiContext>) {
    let gitlab_store = GitlabStore::fetch_updated();
    egui::Window::new("Event Counter")
        .resizable(true)
        .show(egui_context.ctx_mut(), |ui| {
            ui.label(format!("Builds: {}", gitlab_store.builds.len()));
            ui.label(format!("Deployments: {}", gitlab_store.deployments.len()));
            ui.label(format!("FeatureFlags: {}", gitlab_store.feature_flags.len()));
            ui.label(format!("Issues: {}", gitlab_store.issues.len()));
            ui.label(format!("MergeRequests: {}", gitlab_store.merge_requests.len()));
            ui.label(format!("Notes: {}", gitlab_store.notes.len()));
            ui.label(format!("Pipelines: {}", gitlab_store.pipelines.len()));
            ui.label(format!("Pushs: {}", gitlab_store.pushs.len()));
            ui.label(format!("Releases: {}", gitlab_store.releases.len()));
            ui.label(format!("WikiPages: {}", gitlab_store.wiki_pages.len()));
        });
}

The bevy version is "0.9" and bevy_egui is "0.17.1".
The crash happened after letting the application run for a few minutes and leaving it unattended.

I'm also facing the same issue, any news on it?
I'll be happy to provide logs etc. to help find out what's causing it.

I've been developing my application ever since and did not encounter this issue again.

Hi! Sorry, it took me long to respond. Yeah, I'd appreciate additional details on how to reproduce it. I left the ui example running for 5-10 mins but couldn't reproduce it.
What's the platform you tried running the examples on? Did you minimise the window or just "alt-tabbed"? Any chance you launched a 3d app that runs in real fullscreen mode? (I'm just making random guesses on how ExtractedWindow::swap_chain_texture could suddenly become None.)
I'll also ask around in Bevy's Discord, apparently, apps cannot assume that swapchain textures are always available.

I can't reproduce it.
I've been working on it daily for >2 weeks switching between Linux and Windows now and it worked stable ever since.
It happened while i was browsing the web browser and doing other stuff with the application opened on another monitor. The application ran in windowed mode. It must have been minutes after the application start when it suddenly closed. If i recall correctly i wasn't even touching the PC watching something on youtube.
I can surely say i did not have anything open in fullscreen mode.

The platform is Arch Linux using the x86_64-unknown-linux-gnu target.
The desktop environment is GNOME.
The display server is wayland.
The Backend used was vulkan and with the vulkan-tools package installed.
The GPU in use was an AMD Vega 64.

To me this error seems to either be extremely rare or a random hiccup on my end.
I don't know about the specific issue @zihadmahiuddin had however.
Are there any more specific details you'd like to have?

I also got the same error from the same line.
I'm on Endeavour OS (based on Arch Linux) and using the x86_64-unknown-linux-gnu target.
The desktop environment is KDE Plasma.
The display server is Xorg.
My GPU is AMD Radeon RX Vega 11 and I tried both the amdvlk and vulkan-amdgpu-pro packages for vulkan.
The weird thing is that everything was fine for 2-3 days and then this started appearing suddenly.
https://github.com/mvlabat/bevy_egui/blob/main/src/egui_node.rs#L332, this is the line btw.
I tried changing it to something like this but that only made the panic disappear but it doesn't function properly.
let Some(swap_chain_texture) = extracted_window.swap_chain_texture.as_ref() else {
  return Ok(());
};

I'm not using this crate directly but through this crate
I got the initial entities to show up in the inspector, but it doesn't update to show the newly added entities, so it only just got rid of the panic but doesn't fix anything, which is to be expected I guess.
By the way, another thing is that for me it was crashing at startup, I didn't have to leave it on for some time or anything like that.
Let me know if you need anything else from me.

Hi, I was trying out the bevy-inspector-egui - 0.15 and ran into this issue.
I'm on Arch Linux using an RX580 gpu on xorg. I'm using the window manager bspwm.
I used this code which I got from a tutorial
use bevy::prelude::*;
use bevy_inspector_egui::WorldInspectorPlugin;

pub const HEIGHT: f32 =  720.0;
pub const  WIDTH: f32 = 1280.0;

fn main() {
    App::new()
        .insert_resource(ClearColor(Color::BLACK))
        .add_startup_system(spawn_basic_scene)
        .add_startup_system(spawn_camera)
        .add_plugins(DefaultPlugins.set(WindowPlugin {
            window: WindowDescriptor {
                width: WIDTH,
                height: HEIGHT,
                title: "testing".to_string(),
                resizable: false,
                ..Default::default()
            },
            ..default()
        }))
        .add_plugin(WorldInspectorPlugin::new())
        .run();
}

fn spawn_basic_scene(
    mut commands: Commands,
    mut meshes: ResMut<Assets<Mesh>>,
    mut materials: ResMut<Assets<StandardMaterial>>,
) {
    commands.spawn(PbrBundle {
        mesh: meshes.add(Mesh::from(shape::Plane { size: 5.0 })),
        material: materials.add(Color::rgb(0.3, 0.5, 0.3).into()),
        ..default()
    });

    commands.spawn(PbrBundle {
        mesh: meshes.add(Mesh::from(shape::Cube { size: 1.0 })),
        material: materials.add(Color::rgb(0.67, 0.84, 0.92).into()),
        transform: Transform::from_xyz(0.0, 0.5, 0.0),
        ..default()
    });
}

fn spawn_camera(mut commands: Commands) {
    commands.spawn(Camera3dBundle {
        transform: Transform::from_xyz(-2.0, 2.5, 5.0).looking_at(Vec3::ZERO, Vec3::Y),
        ..default()
    });
}

Heres the stack trace:
hopalong_orbits_generator on  main [?] is 📦 v0.1.0 via 🦀 v1.66.0 took 3s
❯ RUST_BACKTRACE=1 cargo run
    Finished dev [optimized + debuginfo] target(s) in 0.17s
     Running `target/debug/hopalong_orbits_generator`
2022-12-25T18:28:21.422351Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1
2022-12-25T18:28:21.442944Z  INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 580 Series", vendor: 4098, device: 26591, device_type: DiscreteGpu, driver: "AMD open-source driver", driver_info: "2022.Q4.4 (LLPC)", backend: Vulkan }
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_egui-0.18.0/src/egui_node.rs:332:34
stack backtrace:
   0: rust_begin_unwind
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:65:14
   2: core::panicking::panic
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:115:5
   3: <bevy_egui::egui_node::EguiNode as bevy_render::render_graph::node::Node>::run
   4: bevy_render::renderer::graph_runner::RenderGraphRunner::run_graph
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_render-0.9.1/src/renderer/graph_runner.rs:188:21
   5: bevy_render::renderer::graph_runner::RenderGraphRunner::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_render-0.9.1/src/renderer/graph_runner.rs:68:9
   6: bevy_render::renderer::render_system
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_render-0.9.1/src/renderer/mod.rs:29:21
   7: core::ops::function::FnMut::call_mut
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:166:5
   8: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:297:13
   9: <Func as bevy_ecs::system::exclusive_function_system::ExclusiveSystemParamFunction<(),()>>::run::call_inner
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_ecs-0.9.1/src/system/exclusive_function_system.rs:193:21
  10: <Func as bevy_ecs::system::exclusive_function_system::ExclusiveSystemParamFunction<(),()>>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_ecs-0.9.1/src/system/exclusive_function_system.rs:196:17
  11: <bevy_ecs::system::exclusive_function_system::ExclusiveFunctionSystem<Param,Marker,F> as bevy_ecs::system::system::System>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_ecs-0.9.1/src/system/exclusive_function_system.rs:102:9
  12: <bevy_ecs::schedule::stage::SystemStage as bevy_ecs::schedule::stage::Stage>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_ecs-0.9.1/src/schedule/stage.rs:853:29
  13: <bevy_render::RenderPlugin as bevy_app::plugin::Plugin>::build::{{closure}}
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_render-0.9.1/src/lib.rs:300:21
  14: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/boxed.rs:2001:9
  15: bevy_app::app::App::update
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_app-0.9.1/src/app.rs:154:13
  16: bevy_winit::winit_runner_with::{{closure}}
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_winit-0.9.1/src/lib.rs:600:21
  17: winit::platform_impl::platform::sticky_exit_callback
  18: winit::platform_impl::platform::x11::EventLoop<T>::run_return::single_iteration
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/x11/mod.rs:363:17
  19: winit::platform_impl::platform::x11::EventLoop<T>::run_return
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/x11/mod.rs:488:27
  20: winit::platform_impl::platform::x11::EventLoop<T>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/x11/mod.rs:503:25
  21: winit::platform_impl::platform::EventLoop<T>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/mod.rs:755:56
  22: winit::event_loop::EventLoop<T>::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/event_loop.rs:278:9
  23: bevy_winit::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_winit-0.9.1/src/lib.rs:263:5
  24: bevy_winit::winit_runner_with
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_winit-0.9.1/src/lib.rs:645:9
  25: bevy_winit::winit_runner
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_winit-0.9.1/src/lib.rs:303:5
  26: core::ops::function::Fn::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:78:5
  27: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/boxed.rs:2001:9
  28: bevy_app::app::App::run
             at /home/aditeya/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_app-0.9.1/src/app.rs:168:9
  29: hopalong_orbits_generator::main
             at ./src/main.rs:8:5
  30: core::ops::function::FnOnce::call_once
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:251:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.


Mark opinionated styles

The font-family: sans-serif in the html [1] and margin: 0 in the body [2] are opinionated declarations, thus marked as such.
This closes #517 and #518.

+1


Dialog expands to 150 extra rows in length

Issue / opportunity
On Edge, copy-pasting 150 receipt codes, expanded the modal to be very long and scrollable with lots of white space.
Screenshot

Closing as a duplicate of #3639


Message order bug still exists

Just saw this in cli talk:
       talkbot+^ :: android port +1 -> +2                                   ~13.24.57
~taglux-nidsep+ +1 for android port                                         ~13.24.55
::
::  expanding talkbot's message:
::
? 5.202
  0vapmio.6qe94.8cvd6.7opjr.pk24h at ~2017.12.20..12.24.57..2634
  ~rivseb-biclus-bacnux-rocsum--liszod-sigsef-sabdex-hadref
  to + /urbit-meta
in reply to: ~taglux-nidsep:
+ +1 for android port
:: android port +1 -> +2

Currently can't be sure if this is just a rendering issue or not. I do believe I saw those two messages pop up at the same time though. Will have to investigate further.
Also see urbit/urbit#601.

For the record, it is not a CLI printing order bug.

(thanks @belisarius222, for the screencap)
Looking at urbit.org/stream to load in the messages from the place they were originally posted to (because _samzod are stream comets at the time of writing), we see they're ordered correctly:

If we then go and boot up a comet and ask ~samzod/urbit-meta (which pulls messages from stream) for messages 270-290, we see messages there are still in order.
~tamlud_samzod- there better be.                                       ~01.28.48
~tamlud_samzod- otherwise i'm just showing up at the urbit offices     ~01.29.00
~tamlud_samzod- demanding beer                                         ~01.29.05

Doing the same for ~zod, which ~samzod sends its urbit-meta messages to for relay, we see messages out of order again:
~tamlud_samzod+ demanding beer                                         ~01.29.05
~tamlud_samzod+ otherwise i'm just showing up at the urbit offices     ~01.29.00
~tamlud_samzod+ there better be.                                       ~01.28.48

Conclusion: problem seems to at least be in the way messages get sent to /report subscriptions. As of now, I think this bug has only been observed for federated channels, which would suggest the cause is somewhere in /report-specific logic.
If anyone ever sees this happening for a non-federated circle (ie, not urbit-meta), please report.

It seems not federation-related after all?
My moon printed this, incorrectly:
~palfun-foslup has no issue in the cli                                      ~01.34.32
~palfun-foslup+ lags that bad? huh                                          ~01.33.54

But my planet printed this, correctly:
~palfun-foslup+ lags that bad? huh                                          ~01.33.54
~palfun-foslup has no issue in the cli                                      ~01.34.32

Yikes.


Tl/add ninja build to BuildRequires

Summary of changes:
Add the ninja-build package to cilium.spec.envsubst (required for recent builds, verified on RHEL and Arch Linux)
Fix-up the VERSION variable.
Generate a RELEASE variable (previously hard-coded to 0).
Here is the current package information after building:
➜  rpm -qip output/cilium-1.2.90-0.git54ce03f.fc28.x86_64.rpm | head -3
Name        : cilium
Version     : 1.2.90
Release     : 0.git54ce03f.fc28

Here is the updated package information from this PR:
➜  rpm -qip output/cilium-1.2.0.rc3-1340.git562985b.fc28.x86_64.rpm | head -3
Name        : cilium
Version     : 1.2.0.rc3
Release     : 1340.git562985b.fc28

How to test (optional):
$ cd contrib/packaging/rpm && make

This change is

Thank you for the contributions @tonylambiris ! Can you please remove the "Merge" commit from your branch by rebasing, as well as sign off each commit per the contributing documentation ?

@tonylambiris Hey, I think it didn't quite work.
There's a guide on how to rebase here:
https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history
I usually do something similar to the section about "Interactive Rebase" and "Squash the commits together".
Then, to sign off, assuming you agree with the Contributing guidelines, you can do a git commit --amend -s and save the commit message.

@tonylambiris try git rebase -i ^HEAD~8 and replace pick with squash or s if you want to squash commits together or simply remove the lines for the commits that you want to make them disappear.
The do git fetch origin master and git rebase origin/master

@aanm did that work properly? if not im at a loss because I had rebased and squashed. running git rebase -i currently shows:

# Rebase 562985b8c..562985b8c onto 562985b8c (1 command)

let me know, i'll just redo the pull request. what exactly was the original issue anyway here (so I can avoid it in the future).
thanks.

@tonylambiris are you on cilium slack? I can help you quickly in there

@tonylambiris git rebase -i master, replace pick with squash except for first line, git commit --amend -s to sign the commit, git push -f

If we prefer saving tonylambiris the hassle, perhaps an admin can click the "Squash and merge" button? I think that will work correctly in this case (I'm not sure, though).

If we prefer saving tonylambiris the hassle, perhaps an admin can click the "Squash and merge" button? I think that will work correctly in this case (I'm not sure, though).

This might just work, but we still need sign-off from @tonylambiris.

Is it copisetic if I close this PR in favor of a new one, all refreshly rebased and such? Caught a one offs I need to add (ie: requirement of llvm installed due to llc and/or lld needed for pre-flight checks).
Thanks!

Is it copisetic if I close this PR in favor of a new one, all refreshly rebased and such? Caught a one offs I need to add (ie: requirement of llvm installed due to llc and/or lld needed for pre-flight checks).
Thanks!

Sure, go ahead

I'll get back to this shortly, thanks everyone for their input! 👍


Would like to add popular Fractional Knapsack problem solved using Greedy Approach

Please assign it to me

Hello, I would like to work on this issue. Can you assign it to me, please?

Hello , I would like to work on this issue. Please assign it to me

Please assign this issue to me


Youtube videos are not shown at all...

It just shows nothing when i add a youtube feed:

It gets the names of the shows, but no video..

Duplicate of #2538


"outputBy" configuration option results in an empty filename

When using "outputBy: Project" in the bridge.json file in version 1.13, the filename is empty, ie the output is ".js" and ".min.js" instead of "ProjectName.js" and "ProjectName.min.js" as it was in version 1.11.

Hi @johnwason,
Thank you for reporting the problem. We are investigating.
As a workaround, could you please use fileName configuration option in addition to outputBy setting:
"outputBy":  "Project",
"fileName":  "ProjectName.js"

Yes, that does work

Related to another forum thread:
http://forums.bridge.net/forum/bridge-net-pro/bugs/2295-bridge-1-13-combinescripts-error

Please see #1300 for a related problem.


Update known-issues-security.yml

The commands seems to have non-working param -cluster
         Update-AksHciClusterCertificates  -Name my-workload -cluster -fixKubeletCredentials

Learn Build status updates of commit cf9b3b0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AKS-Hybrid/known-issues-security.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@Iadwan Thank you for the contribution! This has been fixed in a separate PR and will be live today after 10 AM PST. #please-close


Consider removing/disabling Idle Detection API

Official Chromium now has a controversial feature called:
"Idle Detection API" (enabled by default).
You can check the internal page:
chrome://settings/content/idleDetection
Mozilla:
https://github.com/mozilla/standards-positions/issues/453#issuecomment-888225596 (@tantek from Mozilla)
Apple:
https://lists.webkit.org/pipermail/webkit-dev/2020-October/031565.html
Can this "feature" be removed from Ungoogled Chromium or at least be set to disabled by default?

I don't see why the feature should be removed from ungoogled-chromium. It appears to not be connected with any Google services and as such does not violate the objectives of this project. Privacy tweaks (as stated in the readme) are mainly available as opt in flags, the idle detection api can be disabled even easier by opening the settings.

I don't see why the feature should be removed from ungoogled-chromium. It appears to not be connected with any Google services and as such does not violate the objectives of this project.

You've got a point there.

Privacy tweaks (as stated in the readme) are mainly available as opt in flags, the idle detection api can be disabled even easier by opening the settings.

That's why I also suggested to disable this new "feature" by default, as it is clearly a privacy issue.

The idle detection api is permission-based like the others in the chrome://settings/content list, so it can't be used without the user's knowledge.
You can test it out on this site:  https://idle-detection.glitch.me/
Clicking the Ephemeral checkbox should show a bubble asking if you'd like to allow or deny the site's usage of the api.
It would be weird to have just that one permission disabled by default instead of, for example, access to USB devices, location, camera, and microphone as well.
Personally I'd never grant a site usage for the majority of the entries there but I like knowing what sites are requesting those permissions and when, so I leave the radio buttons on 'ask'.

Given the ability to set this setting in your profile, which should be preserved for you, there seems to be very little benefit of disabling it via ungoogled-chromium patches.

It should be removed but it SHOULD be disabled by default. The reason is that many people won't even be aware of the toggle existing, so will inadvertently leave it to enabled. Since it is a privacy issue it does not make sense to have the default setting at enabled.
Switching the default setting to disabled surely is no big deal programming-wise?

It should be removed but it SHOULD be disabled by default.

I think you mean:

It shouldn't be removed but it SHOULD be disabled by default.

Mozilla and Apple already decided that Firefox and Safari won't support the Idle Detection API, at least not in its current form because it has the potential for abuse.
Their engineers believe that the API may be abused for dark usage patterns or to run expensive computations when the device is idle (users tricked into clicking OK).

Users tricked into clicking ok

ungoogled-chromium users are not in this group of users.
There is no need for the browser to disable it by default, you can change it in the settings easily. I would even go as far as to say that changing this default would defeat the object to keep the ungoogled-chromium experience close to chromium.

@nicolaasjan thanks for pointing out the typo: yes it should read should not.

@networkException

you can change it in the settings easily

I am fully aware of that, but with that policy you ignore the fact, as I pointed out, that many people won't even be aware of the toggle existing, so will inadvertently leave it to enabled. Since it is a privacy issue it does not make sense to have the default setting at enabled.
Since Ungoogled Chromium was created precisely to improve privacy by blocking/taking away certain Google privacy invading features, I cannot marry that noble principle with letting unsuspecting users fall into this trap, when it is so easy to provide that togglable protection upfront.

ungoogled-chromium users are not in this group of users.

Most of them probably not, but not all of them, I'm afraid.

I would even go as far as to say that changing this default would defeat the object to keep the ungoogled-chromium experience close to chromium.

I get that, but IMO exceptions should be be considered when google makes controversial decisions like this.

@DutchPete As far as I can see, there is no enabled. It's either disabled or ask (per site), which most definitely isn't the same as enabled.
What remains is whether Ungoogled Chromium should disable this by default _by principle. I would be all for it, but as you can see by the extra privacy-related flags added to it, they're all disabled by default, so it's not the project's general approach.

they're all disabled by default

That being the case it makes even less sense to not disable this one too. After all, a site asking a browser user permission to know when they are using a device is highly unusual.
Moreover, “sites may convince users to give the permission”, something that is open to abuse. So, why not disable it, and if a user feels the need that certain sites may indeed “know”, that means the user is likely to have thought about it and to know what it means, in stark contrast to the unknowing user clicking “yes” to just keep browsing smoothly when a site asks.

I would even go as far as to say that changing this default would defeat the object to keep the ungoogled-chromium experience close to chromium.

In my view that statement does not make sense: considering all the privacy flags UC already has in place, you are arguing this single one destroys the Chromium experience? Come on.

they're all disabled by default

That being the case it makes even less sense to not disable this one too.

That's not how you should read it: these extra flags are patches on top of the Chromium codebase, optionally giving you extra privacy features. They're disabled by default, which would translate directly to leaving the Idle Detection feature from the Chromium codebase untouched, i.e. ask-per-site.

Moreover, “sites may convince users to give the permission”, something that is open to abuse.

I agree with you on that. In my previous post I was trying to say that enabled isn't a state for that setting, so you shouldn't make it seem like that, that's confusing, and I was trying to extrapolate the general approach to such stuff within the project.

In my view that statement does not make sense: considering all the privacy flags UC already has in place, you are arguing this single one destroys the Chromium experience? Come on.

In place, but not enabled.

So, why not disable it, and if a user feels the need that certain sites may indeed “know”, that means the user is likely to have thought about it and to know what it means, in stark contrast to the unknowing user clicking “yes” to just keep browsing smoothly when a site asks.

I would generally like to see this approach in Ungoogled-Chromium to be honest, but I'm not sure it will ever come.

I would generally like to see this approach in Ungoogled-Chromium to be honest, but I'm not sure it will ever come.

Sure, it is for the devs to decide whether they want to implement it or not. Hopefully they are open to good, valid arguments, but at the end of the day we'll have to defer to them.

I would generally like to see this approach in Ungoogled-Chromium to be honest, but I'm not sure it will ever come.

Sure, it is for the devs to decide whether they want to implement it or not. Hopefully they are open to good, valid arguments, but at the end of the day we'll have to defer to them.

A project that does have this philosophy is LibreWolf, based on Firefox, but inevitably this will break some sites. This is probably one of the reasons Ungoogled Chromium won't do it.

This is probably one of the reasons Ungoogled Chromium won't do it.

I doubt it because a number of other flags already in place also break sites.

The important difference is that all those are opt in

The important difference is that all those are opt in

So, disabling Idle Detection API would be right in line with that philosophy and make the feature also an opt-in. Or do I misunderstand?

FWIW, Brave disabled it.

I heard about this via r/privacy. In the thread, a commenter said "WTF ??? I trusted this browser until now ! From now on I will stop recommending to anyone." It currently stands at ~22 upvotes, so there are at least ~22 people who have not responded but feel similarly. Please reconsider.

For reference it is this comment: https://www.reddit.com/r/privacy/comments/pwkkbj/comment/hehr81w/?utm_source=share&utm_medium=web2x&context=3
I've already stated my reasoning why I personally don't see the need to disable this by default. The r/privacy community at least has a different opinion although I'm sure that if people would actually read the issue the outcry wouldn't be so loud.
I respect the community that has formed around this project and deeply believe in democracy for finding solutions. Even if I personally don't see the need for change as I already said I'm fine to approve such a change if other maintainers aggree


WIP-903-New ui

This is the design implementation. Opened PR for some help with CSS issues. Looking forward to get merged soon

Coverage decreased (-0.2%) to 98.982% when pulling ec06ea36f173ba7f39a067342ac4789a1b06058d on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.1%) to 99.077% when pulling 4cfd7215b8972dce52295af5796b13ff70855073 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.2%) to 98.982% when pulling 4cfd7215b8972dce52295af5796b13ff70855073 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.2%) to 98.982% when pulling 4cfd7215b8972dce52295af5796b13ff70855073 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.1%) to 99.077% when pulling 4cfd7215b8972dce52295af5796b13ff70855073 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.1%) to 99.127% when pulling 34ba65c6123007f50ecfef8cfef2b3e003d8eb0a on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.3%) to 98.931% when pulling 4638b6ebb66bb909128da43cc8edaa10dbd27c51 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.2%) to 98.982% when pulling d0a7760c3dddf3443b9c48c03afbde6f54bce26c on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.3%) to 98.931% when pulling<PHONE_NUMBER>be5889a0d4d670b362b01731ae4496 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.3%) to 98.931% when pulling d465e37d57092107c522517f5b35ef9985268155 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.3%) to 98.931% when pulling d465e37d57092107c522517f5b35ef9985268155 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Coverage decreased (-0.2%) to 98.982% when pulling d465e37d57092107c522517f5b35ef9985268155 on new-ui into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on master.

Closing this PR due to inactivity, although it appears that RSpec is working again after upgrades. Sorry for the radio silence on this one- I'm hoping to take a more active role in getting things merged in 2019. Please let me know if there is anything I can do to help- I realize it has been very quiet these days.


Share a list of items in date order

When sharing a selection of items to mail as URLs the date order of the links is not respected.
Would be good to have default share in date order please.

Looks like this has just landed in update, very pleased. not sure if you would want a pref but would be nice to be able to choose the reverse order ?


chore(Styleguide): Update AboutCell's to match new heirarchy.

Overview
Adds a new section for Layouts Specifically and makes the routing a bit simpler.
Note Labs link will be a bit strange.
PR Checklist

[ ] Related to Abstract designs:
[ ] Related to JIRA ticket: ABC-123
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

🚀 Styleguide deploy preview ready!https://5f0e0fdb029ca96934a5b358--codecademy-styleguide.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://5f0e21b98b07b301c2b8a4ee--codecademy-styleguide.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://5f0e27a3cff8a3019ce0467f--codecademy-styleguide.netlify.appDeploy Logs


Increase timeout for DEBUG bm_trickle

Fixes #13403
Kokoro logs show that that the passing instances of BM_PumpUnbalancedUnary_Trickle/1/16777216/67108864 take close to 300s. Anything over times out. Doubling timeout for those cases should fix this

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Basic Tests C++ Linux [dbg] (internal CI) has passed once. Re-running

Aha, looks like a bug in run_tests.py then. Benchmarks would always pick up the default timeout instead of trying to read from build.yaml

Fixed

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

This does not address the larger problem of timeouts being hard to change. We should treat build.yaml as the one source of truth, and anything that doesn't use it is a bug

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


Block serving a request for SCSB updates until the update file compression has completed

Backtrace
line 6 of [PROJECT_ROOT]/app/controllers/dump_files_controller.rb: show

View full backtrace and more info at honeybadger.io

I suspect that this is due to the fact that there is a parallel process generating the TAR-compressed archive file which has not completed before the Controller attempts to transmit the payload in the response:
ActionController::MissingFile: Cannot read file /data/marc_liberation_files/scsb_update_files/scsbupdate202001061815_1.xml.gz

[PROJECT_ROOT]/app/controllers/dump_files_controller.rb:6:in `show'
4
5   def show
6     send_file @dump_file.path, file_name: File.basename(@dump_file.path), type: 'application/x-gzip'
7   end


pub_to_p2wpkh_in_p2sh

Codecov Report

Merging #2 (5b579cd) into main (649e063) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##              main        #2   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            5        18   +13
=========================================
+ Hits             5        18   +13

Impacted Files
Coverage Δ

src/btcau.erl
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixes for swap errors

Changes:

Added retries for no quotes error
Showing better message for low amount error
Swap is now async

/workflows/benchmarks agents/token/test_swap.py 3


[Bug]: Share.shareXFiles is not working on my Android 11 device but Share.shareFiles is working

Platform
Android 11
Plugin
share_plus
Version
6.3.0
Flutter SDK
3.7.6
Steps to reproduce
I am calling :
 await Share.shareFiles([(filePath)], subject: "A nice subject");

And it's working fine, but this method is deprecated.
So i have tried to use :
await Share.shareXFiles([XFile(filePath)], subject: "A nice subject");

And here is the output : PlatformException(Share callback error, prior share-sheet did not call back, did you await it? Maybe use non-result variant, null, null)
With the exact same filePath
The only thing i have found on Google which was not helpful was : https://stackoverflow.com/questions/71855220/flutter-package-share-plus-unexpected-async-await-behaviour but this doesn't seem to match my behavior since it's working with the deprecated method.
Code Sample
call `await Share.shareXFiles([XFile(filePath)], subject: "A nice subject")` and see the error.

Logs
There is nothing helpful so i am attaching the only log i have got :

`PlatformException(Share callback error, prior share-sheet did not call back, did you await it? Maybe use non-result variant, null, null)`

Flutter Doctor
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-x64, locale fr-FR)
    • Flutter version 3.7.6 on channel stable at /Users/foxtom/Desktop/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12cb4eb7a0 (10 days ago), 2023-03-01 10:29:26 -0800
    • Engine revision ada363ee93
    • Dart version 2.19.3
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/foxtom/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.12.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.76.1)
    • VS Code at /Users/foxtom/Desktop/Visual Studio Code.app/Contents
    • Flutter extension version 3.46.0

[✓] Connected device (3 available)
    • moto g 8 power (mobile) • adb-ZY22BNDW2C-yyjDO7._adb-tls-connect._tcp. • android-arm64  • Android 11 (API 30)
    • macOS (desktop)         • macos                                        • darwin-x64     • macOS 13.2.1 22D68 darwin-x64
    • Chrome (web)            • chrome                                       • web-javascript • Google Chrome 110.0.5481.177

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Checklist before submitting a bug

[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

Try to write the file in File format first and then share. Somehow the XFile() or XFile.fromData() doesn't work as expected. So my workaround is:
final directoryPath = (await getApplicationDocumentsDirectory()).path;
final imagePath = '$directoryPath/some_image.png';

final imageFile = await File(imagePath).create(recursive: true);
imageFile.writeAsBytesSync(imageContent);

final file = XFile(imagePath);
await Share.shareXFiles([file], text: 'hello');

I've been using Share.shareXFiles for some time and it worked perfectly but when I upgraded flutter to version 3.7.6, I faced the same error as mentioned.

This is a regression because it was working with Share.shareXFiles on Android few months ago, i just can't remember which version and don't have time currently to test them one by one.

I am trying to reproduce the issue using example app and on Flutter 3.7.10. Sharing image works fine for me with Share button which uses shareXFiles(). Could you specify which types of files fail to share for you?

It seems to be working again using flutter 3.7.10 + on the same phone that had the issue, so this issue is possible to be happening only on Flutter 3.7.6 as mentioned by the other comments.

Thanks for the feedback.
@SheenaJacob @c-seeger Could you confirm that updating Flutter version helps with the issue?

Oh sorry i have not seen, but yes updating Flutter version solved this issue !
i am using flutter: 3.7.12

In my case, I was able to resolve the above issue by changing the share_plus version from 7.0.2 to 7.0.0.  Additionally, I am using Flutter SDK version 3.7.11.

I am having the same issue. share_plus 7.0.2 and flutter 3.10.2

Have you considered downgrading the share_plus version and using that version? This might help you to resolve the issue. Sometimes, compatibility issues can arise with different versions of packages. By downgrading to a previous version, you may be able to regain the share functionality.

i have the same problem

To solve the issue we need a reproducing instructions/reproducer project. I have already mentioned some months ago that currently can't reproduce. So till there is a proper reproducer provided we can't really help with this issue.

same issue when using version 7.1.0

same issue here

Same issue here.... @vbuberen to reproduce the issue try the steps listed here friend: https://github.com/fluttercommunity/plus_plugins/issues/1936

Share.shareFiles works fine, but the same issue occurs with Share.shareXfiles.

To solve the issue we need a reproducing instructions/reproducer project. I have already mentioned some months ago that currently can't reproduce. So till there is a proper reproducer provided we can't really help with this issue.

the reproducible steps are (Android):

have shareXFiles e.g. on some button click)

      await Share.shareXFiles(
        filesToShare, // e.g. 1 pdf
        text: 'Sharing something',
      );

In the share sheet, pick the same app as you are sharing from
Try to share again


Email verification on lbry.io instead of device

The Issue
Android side issue for: https://github.com/lbryio/lbry-desktop/issues/1299
System Configuration

Device:
Android version:

Anything Else

Screenshots

Internal Use
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

Done.


Add an export-clixml example.

In Microsoft support we ask customers to run this all the time to import into MRSExplorer.ps1 and analyse the migration batch / user, please add this example.
Get-MoveRequestStatistics<EMAIL_ADDRESS>-IncludeReport -DiagnosticInfo verbose | Export-CliXml MoveReport.xml

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

ID: 7b058d48-3c1e-bcb6-4070-00b144ddc03d
Version Independent ID: c37947e6-2308-0c18-34ba-25d82f71e2ec
Content: Get-MoveRequestStatistics (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@jprknight, I added your suggestion as example 6 in the Get-MoveRequestStatistics topic. Feel free to make any changes.
In the future, you too can make changes like this directly. Instructions are here.
Thanks for the feedback.
Closing


README.md typo

Fetures should be Features :)

什么意思？what is your mean？。。

README.md 有拼写错误 Fetures  应该是Features

wow，Thanks~


Store inbound connector errors

What do we need to do?
Connector runtime needs to store errors that happen in the following cases:

During inbound connector activation (i.e. in a synchronous call to activate() method)
During InboundConnectorExecutable lifecycle (i.e. when connector declares an error by calling the cancel() method of the InboundConnectorContext.

We also need to return this information from our status endpoint (GET /inboung) alongside running connectors.
Why do we need to do it?
To provide the user with debug information about errors that happened during inbound connector execution.

This issue was transferred to connectors-bundle repo.


Generate *.pb.go and *_grpc.pb.go separately for dapr proto

In what area(s)?

/area runtime
Describe the feature

We have used the old command to generate stub client from proto files.
https://github.com/dapr/dapr/tree/master/dapr#generate-go-clients
From 1.30.x gRPC, gRPC protoc generates *.pb.go and *_grpc.pb.go separately:

*.pb.go, which contains all the protocol buffer code to populate, serialize, and retrieve request and response message types.
*_grpc.pb.go, which contains the following:

An interface type (or stub) for clients to call with the methods defined in the service.
An interface type for servers to implement, also with the methods defined in the service.

Release Note

RELEASE NOTE: GENERATE _pb.go and _grpc.pb.go separately using newer gRPC protoc for Go.

@mchmarny I recall that go-sdk uses new way to generate pb files, doesn't it?
cc/ @yaron2 @artursouza

Ye, with libprotoc 3.13.0 you can just do this now (notice the : in path). No plugins necessary.
protoc \
  --proto_path=proto proto/v1/*.proto \
  --go_out=:pkg/api/v1 \
  --go-grpc_out=:pkg/api/v1

@mchmarny thanks for sharing the experience. @yaron2 I think we should generate go client with the latest protoc to conform with the latest version gRPC; we do not need proto file change. I suggest to mark this as P1.
cc/ @msfussell @artursouza

I still couldn't figure it out how to create file_grpc.pb.go


create doesn't work without insane genius

I've never been able to get the 'gh create' calls to work.  I tried all sorts of combinations and trying to specify the repo in different ways.  Nada.  So I decided to write up an issue...then I decided I'd better just look at the source.  And there is, some mysterious github token!  I didn't have one.  So I googled and discovered that I do have one and I need to set that in my global git config.
Could you please add a line saying that you need to do this step to the install?!  Unless I'm missing something how would any normal person know to do this?
Cheers,
Karl
PS A check that the token isn't empty would be good in the 'create' calls..or wherever it's needed.  Perhaps that would even be enough.
'You haven't configured your GitHub API key!  Please go to http://github.com/[github_user] and blah...'

I gave create an API token with all possible access rights, but it gives me the error:
gh create new-repo
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

There are no more access rights, and the repository doesn't exist – I'm trying to create it.

Also:
$ cd new-repo
$ git init .
$ gh create-from-local new-repo
 (JSON::ParserError)gems/2.1.0/gems/json_pure-1.5.5/lib/json/common.rb:148:in `parse': 757: unexpected token at '
<title>410 Gone</title>

410 Gone

nginx

'
	from /usr/local/lib/ruby/gems/2.1.0/gems/json_pure-1.5.5/lib/json/common.rb:148:in `parse'
	from /usr/local/lib/ruby/gems/2.1.0/gems/github-0.7.2/lib/commands/commands.rb:260:in `block in load'
	from /usr/local/lib/ruby/gems/2.1.0/gems/github-0.7.2/lib/github/command.rb:25:in `call'
	from /usr/local/lib/ruby/gems/2.1.0/gems/github-0.7.2/lib/github.rb:76:in `invoke'
	from /usr/local/lib/ruby/gems/2.1.0/gems/github-0.7.2/lib/github.rb:70:in `activate'
	from /usr/local/lib/ruby/gems/2.1.0/gems/github-0.7.2/bin/gh:8:in `<top (required)>'
	from /usr/local/bin/gh:23:in `load'
	from /usr/local/bin/gh:23:in `'


PythonPackages.taichi: init at 1.6.0

Description of changes
Homepage: https://www.taichi-lang.org/
Close #143181
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Hey @SaltyKitkat! Do you think this is good to go? I'd love to have Taichi in pythonPackages.

Sorry, I'm quiet busy these days and not working on this for a long time.
I'll close this pr.


teacher features icons/text when logged in as student

When logged into a student account, I saw this view of the Teacher Features page:

(does that work?)
The hexagons for setting assignments appear GREEN, when they should be grey (as they're not available until teacher status is granted).
Also, the text "Using isaac physics with your class" appears greyed out. The picture is correctly NOT greyed out, as this page IS accessible without teacher status, but the TEXT should also NOT be greyed out.

Didn't we note this down at the meeting in the CL the Friday before last? Is it a cache thing, or is it not fixed?


Updating a key resets it's expiry

https://github.com/dustin/gomemcached/blob/master/client/mc.go#L389
Why is this done? It appears to ignore the expiry value passed in and reset it to 0.
In our system, this leads to updated keys never expiring. The fix is easy, but wondering why this was done in the first place?

It's a bit unclear.  It seemed that every path was wrong, but that one probably looks more wrong than resetting it to the supplied value.


Discuss DPD angle computation outside of phase space

:construction: Problem :construction:
Description:
Due to numerical imprecisions and/or due to the behaviour of the kinematic fit some data points lie outside the allowed phase space for the reaction.
See:

Because of that, the Källén function within the DPD angle calculation can become negative leading to complex values in the acos() function.
See e.g. equation:

See Källén function:

The arcos() function in use is not defined for complex numbers. This leads to the data arrays of some events containing nan values. Currently the events containing nan values are just sorted out.
❓  Question ❓
Is there a way to treat the complex values within the acos() function? For example by redefining the function.

@mmikhasenko how do you usually deal with negative values of the Källén function?

I do not have a good way of dealing with it once they appear. I solved a similar problem by tracing where this points come from.
In my case, they were cost by the range of the angle that I said from -1 to 1. Solution for that was to shift the ranch by half a step and never touch the boundary

Just remembered, I have another thing before passing to the angle call. I check 'inphasespace' to reassure that all the lambda functions are computed.
See the last lines in
src/tbs_struct.jl

Oke thank you Misha. We are currently also sorting out the events which are not in phase space. However we have no control over the data points being in or out phase space at the boundaries as they came from some kinematic fit. So you mean that one can just redefine the domain of the arcosine function or just shift it slightly in x direction? But I think the problem comes from the squareroot containing a negative Källén function as it hands an imaginary number the arcosine?

After a discussion with @mmikhasenko: the problem is probably that the masses used for the kinematic fit are different from the masses in the amplitude model (which are used to compute $\zeta$, $\theta$, etc.).  Theoretically speaking the best solution, even though there may still be some points outside phase space, because the kinematic fit is coded with C++ and run on different architecture.
Compute the masses used in the kinematic fit by computing p1.m.mean() etc. Same as 1., this may still result in some floating-point imprecisions.
Compute $m_0, \dots, m_3$ per event (array-based) and insert them into your $\zeta$ functions. This is the most generic solution, that also works for decays where the initial energy is not fixed.

Seems solved. We could document this in the documentation, but users could still fint this issue if there are problems.


fix: add .venv to .gitignore

Description
In CONTRIBUTING.md, we recommend that the developer uses a python virtual env.
create a Python virtual environment (required for development builds), e.g. as described [here](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/)

However, .venv is not ignored in the .gitignore.
Related Issue(s)
Documentation

@gacharya you can use the make commands from the python directory to setup your venv


Added support for generating secrets for the Jaeger<->ES communication

Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

cc @knrc, @rcernich, @objectiser
This is a first draft, just to check if the direction is valid. Basically, this PR adds another preprocessObject hook for the Jaeger kind. When production-elasticsearch is used, it checks whether the required secrets exist. When they are absent, new certs are generated locally in the istio-operator process and set as fields that are then used by the new secret templates inside the tracing chart.
What's missing:

Changes to the existing templates (jaeger and ES)
Add the secrets to the list of templates to be processed
Testing (manual, as it seems there are no tests in this repo?)

What I don't know:

Whether the values that I set in the populateCertValues end up in the secret templates
If the general approach is valid and would be acceptable

Submitted #126 to show the alternative elasticsearch operator approach.

What is the use case that is driving these changes?  Why would we be doing this versus letting k8s generate the certs for us?

What is the use case that is driving these changes?

We had a few problems with the ES operator during the last week, to the point where we thought we might not be able to use it for GA. Most are sorted out already, but this PR brings a way to create an ES cluster based on templates instead of the operator, should we need to move away from the ES-operator.

Why would we be doing this versus letting k8s generate the certs for us?

I actually did consider generating the CSR's via Go and sending CertificateSigningRequest objects to Kubernetes for signing, but that's not how it's currently done by the Jaeger Operator nor ECL Operator. If we do decide to follow this approach, I'd be more than happy to consider moving away from this shell script for the next release.

I'm closing this, in favor of using the ES Operator. \o/


Hbase 25323 Fix potential NPE when the zookeeper path of RegionServerTracker does not exist when start

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 23s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 43s
master passed

+1 :green_heart:
checkstyle
1m 21s
master passed

+1 :green_heart:
spotbugs
2m 33s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 26s
the patch passed

-0 :warning:
checkstyle
1m  3s
hbase-server: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m 23s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
2m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 24s
The patch does not generate ASF License warnings.

42m 32s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2702

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 49d33c25cfe2 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1cd8f3cf94

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: hbase-zookeeper hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 28s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 23s
master passed

+1 :green_heart:
compile
1m 18s
master passed

+1 :green_heart:
shadedjars
7m 10s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  3s
the patch passed

+1 :green_heart:
compile
1m 28s
the patch passed

+1 :green_heart:
javac
1m 28s
the patch passed

+1 :green_heart:
shadedjars
7m 46s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 46s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
217m 34s
hbase-server in the patch passed.

250m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2702

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9d8e4ccf834f 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1cd8f3cf94

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/testReport/

Max. process+thread count
2942 (vs. ulimit of 30000)

modules
C: hbase-zookeeper hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 22s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 22s
master passed

+1 :green_heart:
checkstyle
1m 26s
master passed

+1 :green_heart:
spotbugs
2m 56s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  3s
the patch passed

-0 :warning:
checkstyle
1m 14s
hbase-server: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
20m  4s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
3m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 24s
The patch does not generate ASF License warnings.

49m  5s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2702

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 6182f0d58177 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4affae5938

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-zookeeper hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  8s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 25s
master passed

+1 :green_heart:
compile
1m 49s
master passed

+1 :green_heart:
shadedjars
8m 51s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 10s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 45s
the patch passed

+1 :green_heart:
compile
2m  1s
the patch passed

+1 :green_heart:
javac
2m  1s
the patch passed

+1 :green_heart:
shadedjars
9m 14s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 13s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 51s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
149m 48s
hbase-server in the patch passed.

191m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2702

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7f3131f754f4 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4affae5938

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/testReport/

Max. process+thread count
3870 (vs. ulimit of 30000)

modules
C: hbase-zookeeper hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 24s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  1s
master passed

+1 :green_heart:
compile
1m 15s
master passed

+1 :green_heart:
shadedjars
7m 11s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 53s
the patch passed

+1 :green_heart:
compile
1m 15s
the patch passed

+1 :green_heart:
javac
1m 15s
the patch passed

+1 :green_heart:
shadedjars
7m 12s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 42s
hbase-zookeeper in the patch passed.

-1 :x:
unit
220m 20s
hbase-server in the patch failed.

253m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2702

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 05f917a7b29a 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4affae5938

Default Java
AdoptOpenJDK-1.8.0_232-b09

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/testReport/

Max. process+thread count
3153 (vs. ulimit of 30000)

modules
C: hbase-zookeeper hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2702/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Hosts unreachable: Resolving timed out after 2000 milliseconds

Hi,
I´m running into this error with Laravel 5.1 when trying to index some data. Always get this error:
AlgoliaException in Client.php line 392:
Hosts unreachable: Resolving timed out after 2000 milliseconds,Resolving timed out after 2000 milliseconds,Resolving timed out after 4000 milliseconds,Resolving timed out after 4000 milliseconds
Found something similar on Twitter from 2013 but can´t figure out how to solve my problem.
Any Ideas on that ?
Thanks
Marc

Hi Marc,
could you provide us the whole stacktrace and tell us which call triggered that? Was it a big addObjects or a search ?

I tried both of them. I also switched the laravel package to the original algolia_php, but same issue.
Is there a problem with indexing html ?
Here´s the long part:

Ok. It seems this is related to your php installation. Can you try to reinstall php on your environment ?
Can you also give me a bit more details on your environment so that I can try to reproduce it ?
Is it running on Window, Unix, Mac ?
Are you using something like XAMP ?

It is running on a virtual machine:
Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-45-generic x86_64)

PHP 5.6.8-1+deb.sury.org~trusty+1

oooouuuuh. The vm is the problem ... I pushed it to production and it worked! But do you have any ideas why ?

There is two possible explanations:

Issue with the vm certificate (most probable)
You can check that you have certificates with this command ls /etc/ssl/certs | grep -i comodo. It should return something like 5 lines. It you do not have them it means you do not have the certicates
Issue with vm networking

I am closing this as it is not a extension related issue.


Experiment india/004 potential bug

I think there may have been a possible mistake in experiments/india/004_n_training_samples
The experiment states that the limit_train_batches option was used to limit the train batches and conduct the experiment. However, based on this discussion it suggests that that would just limit the number of batches shown on each training epoch. I think it means it shuffles all the batches and then limits them rather than limiting the batches and then shuffling them. This suggests the experiments with only 100 samples wouldn't be shown only 100 samples. Instead it sees a different 100 samples each epoch. The point of the experiment was to see if having more training examples was worth it, but if I'm right about the way lightning limits batches then the experiment doesn't address that

Yea I thought that might be the case. I did a quick check of this, by running an experiment with only 1 batch in an epoch, and printed out teh files names being used. From what I remember the same file names were used. SO i think this means the shuffling is only done once. We should find this out though

I do think this is fine actually


Add files via upload

Comment: PhD students at the MDC Berlin are also enrolled at Humboldt University, Technische Universität Berlin, or Freie Universität Berlin, and enjoy student privileges at one of those institutes, but maintain a primary MDC email address.
Details:
https://www.mdc-berlin.de/graduate-school
PhD program:
https://www.mdc-berlin.de/phd
Graduate school curriculum:
https://www.mdc-berlin.de/training/phd_program/Graduate-School/Curriculum
email address listed as PhD Student:
https://www.mdc-berlin.de/poulet#t-team

@ianerik merged, thank you. Please notice that free educational subscriptions are for students and teachers only.


Lists panel is not styled

The lists management panel is not currently styled by Tangerine UI.

Fixed in https://github.com/nileane/TangerineUI-for-Mastodon/commit/a7c80fb711a37238d4549bff942e4f6c33b34c99


WMS ID: 11184 - Updated lab with new screenshots up our updated UI removed conflicts and uppercase folders

Add here your WMS ID: 11184
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

Hi @yiby4n please resolve your conflicts


Bug if autocheck update off

if autocheck update is off, HA notify an update.

and the link is not correct https://github.com/rstrouse/ESPSomfy-RTS/releases/tag/

I'll have a look at the update entity I assume that is saying that the current installed version is v2.3.2 since there is no new version.  It should say up to date instead when it doesn't know what the current version is.

To reproduce:

HA v2.3.2
ESP v2.3.2

On ESP:

set autocheck update to off,
Reboot.

On HA:

Restart HA.

Then we have the message for a new version...
If autocheck update is on, no problem.

In v2.3.3 I will fix this issue.  It turns out that I have to make the update entity unknown if the checkbox is unchecked.

When the Auto check is turned off in ESPSomfy RTS then the entity will change to an unknown state and re-enable itself when you check it again.