Remove master.mesos polling

Codecov Report

Merging #33 into master will decrease coverage by 0.33%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   85.26%   84.93%   -0.34%
==========================================
  Files          33       33
  Lines        2118     2118
==========================================
- Hits         1806     1799       -7
- Misses        312      319       +7

Impacted Files
Coverage Δ

src/lashup_hyparview_membership.erl
83.91% <87.5%> (-0.66%)
:arrow_down:

src/lashup_hyparview_ping_handler.erl
79.71% <0%> (-5.8%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24b1841...e01e580. Read the comment docs.

https://github.com/mesosphere/dcos-net/pull/1/files#diff-a292656825829d512e3c73e530f1daf1R1


Proposal: Enable control plane node exclusivity through built-in well-known tolerations

We anticipate the need for users to dedicate nodes to control planes for various reasons (e.g. https://github.com/openshift/hypershift/issues/237 regarding noisy neighbors, resource requirements, etc.). One way we expect users to achieve node exclusivity is through the use of taints and tolerations.
This proposal is to bake in some default tolerations to each control plane component which define well-known/predictable values which can be leveraged by users to add corresponding taints to their nodes to achieve node exclusivity for any set of hosted control planes.
Each control plane component would have a default toleration set like:
tolerations:
- key: "hypershift.openshift.io/control-plane"
  operator: "Equal"
  value: "true"
  effect: NoSchedule
- key: "hypershift.openshift.io/$cluster-id"
  operator: "Equal"
  value: "true"
  effect: NoSchedule

The idea being that the end user could taint nodes in such a way that the nodes are dedicated to hosted clusters generally, or any subset (1 or many) of hosted clusters based on their ID.
TODO: Decide what is the right value to use for the unique cluster ID (e.g. hostedcluster UUID, namespace+name tuple, etc.)
TODO: Define the exhaustive list of control plane components which to which these defaults will be applied.

This is always something I feel the need to remember whenever the topic of taints/tolerations comes up.
A pod tolerating a taint means the pod can be scheduled to the tainted node, not that it will be.  In order to confine the scheduling to a set of nodes, nodeSelector and Node labels must be used.  The taint just prevents pods with no nodeSelector from scheduling onto the dedicated nodes.

This is always something I feel the need to remember whenever the topic of taints/tolerations comes up.
A pod tolerating a taint means the pod can be scheduled to the tainted node, not that it will be. In order to confine the scheduling to a set of nodes, nodeSelector and Node labels must be used. The taint just prevents pods with no nodeSelector from scheduling onto the dedicated nodes.

Great points. I guess the implicit assumption in the requirements as they've been discussed is that there's no explicit confinement via node selectors in this use case, only exclusionary methods.
However, we also have https://github.com/openshift/hypershift/issues/370 which will induce node colocation by default. Does that change the calculus here? Otherwise, what do you propose? Another thought is we could do a soft node affinity for nodes labelled specific to the cluster.
Seems like we should be able to describe in terms of test scenario data (hostedcluster, node state, etc) what the expectations are to see whether we can satisfy them...
cc @relyt0925 @csrwng

So what I mean here is, if we had both a default hosted-cluster-scoped toleration and soft node affinity rule, these would be benign out of the box, but if the admin wants to make a node exclusive to the hosted cluster, they could label the node with the well-known label matching the default affinity rule (to get the pods in right place) and taint the node with the well-known key for that cluster to prevent other clusters from being scheduled.

I am fine doing a soft node affinity rule as well to prefer the isolated nodes by default. I think it's a good addition.

also fine with names.

Every component that supports a master should tolerate these tolerations
catalog-operator                 0/1     0            0           52m
certified-operators-catalog      1/1     1            1           52m
cloud-controller-manager         3/3     3            3           50m
cluster-api                      1/1     1            1           52m
cluster-autoscaler               1/1     1            1           52m
cluster-policy-controller        3/3     3            3           52m
cluster-version-operator         1/1     1            1           52m
community-operators-catalog      1/1     1            1           52m
control-plane-operator           1/1     1            1           52m
hosted-cluster-config-operator   1/1     1            1           51m
ignition-server                  1/1     1            1           52m
konnectivity-agent               1/1     1            1           52m
konnectivity-server              1/1     1            1           52m
kube-apiserver                   3/3     3            3           52m
kube-controller-manager          3/3     3            3           52m
kube-scheduler                   3/3     3            3           52m
oauth-openshift                  3/3     3            3           52m
olm-operator                     1/1     1            1           51m
openshift-apiserver              3/3     3            3           52m
openshift-controller-manager     3/3     3            3           52m
openshift-oauth-apiserver        3/3     3            3           52m
packageserver                    2/2     2            2           52m
redhat-marketplace-catalog       1/1     1            1           52m
redhat-operators-catalog         1/1     1            1           52m

In addition the manifest-bootstrapper pod and any one time creation pods (machine config server, image lookup if it doesn't go away) should tolerate as well

/assign @csrwng

Tracked in https://issues.redhat.com/browse/HOSTEDCP-193


Compiling error when export WAMR to Cortex-M4 board

When I try to export the WAMR to Cortex-M4 board I came across these errors:
../wamr/core/iwasm/common/arch/invokeNative_arm.s: Assembler messages:
../wamr/core/iwasm/common/arch/invokeNative_arm.s:19: Error: lo register required -- `stmfd sp!,{r4,r5,r6,r7,lr}'
../wamr/core/iwasm/common/arch/invokeNative_arm.s:29: Error: Thumb does not support this addressing mode -- `ldr r0,[r4],#4'
../wamr/core/iwasm/common/arch/invokeNative_arm.s:33: Error: Thumb does not support this addressing mode -- `ldr r1,[r4],#4'
../wamr/core/iwasm/common/arch/invokeNative_arm.s:37: Error: Thumb does not support this addressing mode -- `ldr r2,[r4],#4'
../wamr/core/iwasm/common/arch/invokeNative_arm.s:41: Error: Thumb does not support this addressing mode -- `ldr r3,[r4],#4'

And I solved this by adding .syntax unified in invokeNative_arm.s to let the assembler know I am using the unified assembly. With this modification, I am able to run WAMR on cortex-m4 board. I think this is not the best way to solve this issue and I hope someone could give out a better solution.

The Cortex-M4 processor implements the ARMv7-M Thumb instruction set while invokeNative_arm.s is for ARM but not for Thumb. So you should use invokeNative_thumb.s instead. And if the board has FPU(and has been enabled) which means VFP registers s0-s15 (d0-d7, q0-q3) are used for passing arguments or returning results in standard procedure-call variants, you should use invokeNative_thumb_vfp.s instead.
If you build WAMR with CMake, just set the CMake variable -DWAMR_BUILD_TARGET=THUMBV7 or  -DWAMR_BUILD_TARGET=THUMBV7_VFP.
I hope it helps.

Thanks, I will take a try


bug: OT2 camera not responding

Overview
I tried the /camera/picture endpoint and recieved.
{
"message": "Error 1000 COMMUNICATION_ERROR (CameraException): Failed to communicate with camera",
"errorCode": "4000"
}
running ffmpeg -y -f video4linux2 -s 640x480 -i /dev/video0 -ss 0:0:1 -frames 1 /data/user_storage/image.jpg gives ```[video4linux2,v4l2 @ 0x12af290] Cannot open video device /dev/video0: No such file or directory
/dev/video0: No such file or directory
errors

### Steps to reproduce

_No response_

### Current behavior

_No response_

### Expected behavior

_No response_

### Operating system

None

### System and robot setup or anything else?

_No response_

@ChrisTwig
sorry for the inconvenience to you. Software team is working on this issue.
The fix version will be released as 7.2.2.

7.2.2 has been released. please try that.
https://github.com/Opentrons/opentrons/releases/tag/v7.2.2


Show histogram / change color of overlay based on proportion of viewers who watched

Also change view cutoffs?


Windows, Linux: verify that copy/cut/paste, undo/redo, close-window keyboard shortcuts work without menu items

See:
https://github.com/readium/readium-desktop/issues/390
We should also check CTRL+W ALT+F4 for closing windows and/or application.
FYI:
https://electronjs.org/docs/tutorial/keyboard-shortcuts
https://electronjs.org/docs/api/global-shortcut

I tested copy/cut/paste and undo/redo on Windows, it works normally.

Related issue: https://github.com/readium/readium-desktop/issues/454

can we close this ?

Checklist to close this issue (both Windows and Linux, both dev and release modes):

Undo CTRL+Z / Redo SHIFT+CTRL+Z (or CTRL+Y) => test with the search box / text input field.
Cut CTRL+X / Copy CTRL+C / Paste CTRL+V => also test with the search box / text input field.
Close window ALT+F4 and/or CTRL+W => test with library and reader windows, and with the web inspectors in debug mode.

Undo CTRL+Z / Redo SHIFT+CTRL+Z (or CTRL+Y) => test with the search box / text input field. -> OK
Cut CTRL+X / Copy CTRL+C / Paste CTRL+V => also test with the search box / text input field. -> OK
Close window ALT+F4 and/or CTRL+W => test with library and reader windows, and with the web inspectors in debug mode. -> OK with ALT-F4
on windows

Thanks Pierre! Closing.


CRD object status is not being updated after reconciliation

Summary
Controller reconciliation for Temporal namespace are not patching/applying the object status.conditions updates on first reconciliation of a new Temporal namespace object.
Steps to Reproduce

Add a new TemporalNamespace to the cluster
Reconciliation is successful
TemporalNamespace.status.conditions are still empty.
Update the TemporalNamespace object
Reconciliation now correctly patches the object's status.conditions

Expected Results
The controller should patch/apply the status.conditions updates to the object on every reconciliation run.
Actual Results
The status.conditions updates are not patched/applied after initial reconciliation. The updates are, however, applied after a secondary reconciliation is run.

Hi @AdamSendible !
Thanks for reporting this issue. It may be related to an issue in https://github.com/alexandrevilain/controller-tools/tree/main/pkg/patch where I'm having issues to upgrade the Kubernetes client.
I'll take a look as soon as possible.

Ok I found the issue, it will be fixed in https://github.com/alexandrevilain/controller-tools/pull/111 once I ci is fixed :)


Setup Project Structure in Flutter

Description:

Set up the basic folder structure for the Flutter project, including separate folders for front-end UI components, API services, and shared utilities.
Ensure that both developers can work within the structure without conflicting paths.

Acceptance Criteria:

A folder structure with directories for lib/components, lib/services, lib/screens, and lib/utils.
Basic Flutter project setup committed to the repository with main.dart included.
README updated with instructions on setting up the Flutter environment.
Ensure all dependencies are installed and the app builds without errors.
"""

Completed with previous task


Bump vendir to 0.40.0

What this PR does / why we need it:
This PR updates vendir to the latest v0.40. Since they renamed the module name to carvel.dev/vendir  (see their go.mod), people using kapp-ctrl as a dependency won't be able to upgrade their vendir dep because a module name mismatch (for example, we in Kubeapps).
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?

NONE

Additional Notes for your reviewer:
I'm not familiar with this repo; I mostly run a bulk rename, run go mod tidy, run go mod vendor and finally run ./hack/gen.sh, so please let me know if I'm missing something to ensure everything continues to work as expected.
Review Checklist:

[X] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[X] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

Hey @antgamdia Thanks for creating the PR. We have an open PR  #1495 by @joaopapereira, which is also bumping vendir to v0.40.0 (plus some additional changes). Right now the tests are failing on that, so we need to look into it. Just curious how urgent this change is for y’all.

Thanks for the quick reply! I looked for other ongoing PRs bumping it up but didn't notice that one.
No rush at all. I simply was reviewing our deps to keep them up to date and simply bumped into this incompatibility with vendir latest version. But there is no urgency at all.
Happy to close this PR and defer the upgrade to the one you mentioned. As you prefer :)


'#21' - Add Identity-based idempotency support

This fixes #21.
Note:
Due to this reverse() https://github.com/zeit/next.js/blob/master/lib/head.js#L24 the last key is used instead of the first. I don't know if this is an issue.
Usage:
<Head>
  <link rel="stylesheet" href="/abc.css" key="test" />
  <link rel="stylesheet" href="/def.css" key="test" />
</Head>

Will only render <link rel="stylesheet" href="/def.css" key="test" />. When rendering new pages it checks if the key was already set. If so it will not remove the current key="test" and discard the new key="test". key is used by React for the same kind of functionality. So it seems the best possible prop to use. Though I'm open to changing it to id

@rauchg Can you review this ?

Needs documenting in README section of <Head>
Does the usage of Set imply a polyfill?

If so, are we using Set elsewhere, so we've already paid its price?

@rauchg On the second point:
It's used in quite a few places.
https://github.com/zeit/next.js/search?utf8=✓&q=new+Set
it says here babel-polyfill is needed:
https://babeljs.io/learn-es2015/#ecmascript-2015-features-map-set-weak-map-weak-set
We include https://babeljs.io/docs/plugins/transform-runtime/ in next.js. So It should be fine 👍

Just came across this issue: would it also be possible to use JSON.stringify(type, props) as the key?
My concern is that in cases where there are a lot of meta tags (think social media directives), this could lead to errors which are difficult to trace / catch (duplicate keys used when they should not etc).
There is of course a performance penalty to be paid, not sure how large that is though.

The purpose of the key usage is for things that are meant to be deduped. For example, you could ensure certain components only inject some global <style> only once by specifying a key on it.

In other words: the vast majority of users will never specify a key on their <Head> children.

I actually haven't needed this in a while 🤔 Let's hold off on this until we feel the need again

@rauchg this is surely needed by people who use non-css-in-js solution for components styling.
For now, we forced to explicitly import every css file in one place, say, layout component or _document.js file.
With this PR landed, I would place style content injection in component itself only.
Also, we can use simple wrapper to reduce boilerplate code:
const InjectStylesheet = ({ id, value }) => (
  <Header>
    <style key={id} dangerouslySetInnerHTML={{ __html: value }} />
  </Header>
)

and in someComponent.js:
 <div>
    <InjectStyleSheet id="someComponent" value={stylesheet} />
...

Obviously, for now this approach ends up with duplicate style tag injection every time the component is being used.

Running into the exact same issue described above by @code4aman.
I ended up having to maintain a list of injected styles to kill the duplication.

this would indeed be very useful, especially for managing meta tags


Support encryption of root and ebs volumes

@JamesGally - I've taken care of this functionality via this PR https://github.com/glg-public/terraform-aws-ec2-basic/pull/3. I'll be closing this ticket out now. You can leverage this functionality in your terraform by setting the source of your module like so:
source = "git::https://github.com/glg-public/terraform-aws-ec2-basic.git?ref=v1.0.3"


 Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
Fetching gem metadata from https://rubygems.org/........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Unable to use the platform-specific (universal-darwin) version of facter (2.5.0) because it has different dependencies from the ruby version. To use the platform-specific version of the gem, run `bundle config specific_platform true` and install again.
Unable to use the platform-specific (universal-darwin) version of puppet (5.0.1) because it has different dependencies from the ruby version. To use the platform-specific version of the gem, run `bundle config specific_platform true` and install again.

mac:repo root# bundle config specific_platform true
mac:repo root# bundle install
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
Fetching gem metadata from https://rubygems.org/........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies...
Using rake 12.0.0
Fetching CFPropertyList 2.3.5
Installing CFPropertyList 2.3.5
Using public_suffix 2.0.5
Using bundler 1.15.3
Using diff-lcs 1.3
Using multipart-post 2.0.0
Using fast_gettext 1.1.0
Using locale 2.1.2
Using text 1.3.1
Using hiera 3.4.0
Using thor 0.19.4
Using minitar 0.6.1
Using rsync 1.0.9
Using metaclass 0.0.4
Using userinput 1.0.2
Using puppet-lint 2.3.0
Using rspec-support 3.6.0
Using puppet-syntax 2.4.1
Fetching facter 2.5.0 (universal-darwin)
Installing facter 2.5.0 (universal-darwin)
Using addressable 2.5.1
Using faraday 0.9.2
Using gettext 3.2.3
Using librarianp 0.6.3
Using mocha 1.2.1
Using rspec-core 3.6.0
Using rspec-expectations 3.6.0
Using rspec-mocks 3.6.0
Using faraday_middleware 0.10.1
Using sawyer 0.8.1
Using gettext-setup 0.26
Using rspec 3.6.0
Using octokit 4.7.0
Using semantic_puppet 1.0.1
Fetching puppet 5.0.1 (universal-darwin)
Installing puppet 5.0.1 (universal-darwin)
Using rspec-puppet 2.6.4
Using octoauth 1.4.8
Using puppet_forge 2.2.7
Using puppetlabs_spec_helper 2.3.1
Using librarian-puppet 2.2.3
Bundle complete! 5 Gemfile dependencies, 39 gems now installed.
 Do you have pre-existing ruby/facter/bundler? The current way this works on Macs should use the magic puppet bundle w/ its ruby, bypassing any custom cruft.

Actually, more relevantly: why/how are you running bundle install in the above? THis script should custom-run the bundler in the magic puppet dir.

Shit, so, I think it was because the script (which was puppet-run I thought) was bailing without much info so I ran it by hand. Of course, I did the above change and it started working so I'm not sure if we can repro the issue easily now...

Gonna close this for now, feel free to re-open if it happens again


Tags lost order after exporting and importing

Issue Summary
Exporting Data and Importing Data lost the tag sequence. Most of the time the sequence doesn't matter for tags. But I am using a first tag as category and from second, normal tags. So that makes it all fuzzy after exporting and importing it.
Note: Tags re-ordering works fine if you don't export-import.
Steps to Reproduce

Export all data from http://websitename.com/ghost/settings/labs/
Delete all content from the same page
Import it again from the same page

Technical details:

Ghost Version: 0.8
Node Version: 4.3.0
Browser/OS: Chrome v51
Database: SQLite

Hi @kirtan403, thanks for the bug report! I think we missed updating the importer after tag ordering was added. Our importer probably needs a bit of TLC.

It was just 20 posts for me. So I was able to do it again. But may take good amount time on large blog.
Hope to see the fix soon.

Just to confirm - this is fixed in 1.0.0 but not in LTS?

@ErisDS
Yeah exactly. I left some importer bugs open, in case the community wants to pick them up. But they didn't get any attention.
I am going to close this issue, because we've overhauled the importer in Ghost 1.0. If you experience this problem, i would suggest to migrate to 1.0 👍 😬
Alternatively, feel free to re-open and provide a quick fix for the LTS branch.


Superposing generated structures

Hello again.
I was curious if you had any thoughts regarding superpositioning of the model's generated structures relative to the corresponding input (i.e., native) PDB structures for structural loss scoring. For example, in the structure prediction (not necessarily generation) community, one's predicted structures are usually superposed onto the corresponding native structure for the sake of calculating structural losses such that the model only needs to optimize the predicted structure up to a 3D rotation and translation (which will be handled e.g., by the Kabsch structural alignment algorithm).
I understand that this diffusion process is formally defined on a translation-invariant subspace, so 3D translations are likely already addressed (w.r.t. the generated structures). Moreover, since the model uses SE(3)-equivariant network layers to learn its structural distribution, the distribution it learns should be SE(3)-invariant. However, 3D rotations of the generated structures do not appear (to me) to be aligned with the input PDB structures when it comes to the calculation of the backbone atom loss, so this loss function appears (to me) to break the assumption that the final distribution the model learns should be rotation-invariant. Unless, by chance, these backbone atom loss terms are being computed from a residue-local perspective and not at a structure-global level?
I'd be curious to get your thoughts on this.
Best,
Alex

Hi Alex,
Thanks for the question.  This is an interesting idea.  We haven't seriously considered within the SE(3)^N diffusion framework for the primary, score-matching loss.  But it's possible that additional auxiliary losses involving an alignment step of this sort could improve performance.
I'm not sure what you mean by "this diffusion process is formally defined on a translation-invariant subspace".   Can you elaborate?  This is not how I think about our procedure.
Best,
Brian

@blt2114, I see. When I mentioned translation-invariant subspace, I was borrowing the language used by other equivariant diffusion models like EDM that subtract the center of mass from all their input point clouds prior to model training. This appears to be the case in this repository's dataloader as well (i.e., zero-centering each training example).

Closing due to inactivity.


Add entry point for convoy test suite

Coverage remained the same at 79.348% when pulling d6192c78d67fae75956ea57b5bf024cfeb8abaa1 on Scandie:a444872261902739_run_tests_plugin into 9145918f44a21770511942197f4c00f1300de253 on openprocurement:master.


Fix Add member payload

I have removed roomId from Add Member request payload according to
https://www.hipchat.com/docs/apiv2/method/add_member
In addition, userId can be now an email or mention name too.

Hi @rjimgal! Thanks for your help in our hipchat-api project. We'll review your code and then continue with this pull request.

Hi @rjimgal i will close this pull request because your change has already been fix in our new release candidate.


Enable windows test with Github actions

This enables windows testing for Github actions.
It is just a reference to what is fixed by #19
So don't merge this :)

Sorry. I think I had a yml syntax error which caused the workflow file to be invalid.

Pytest reports the following for windows:
= 113 failed, 23 passed, 11 skipped, 2 xfailed, 11 warnings in 171.39 seconds =

With the failing test, might there be a linebreak issue?

With the failing test, might there be a linebreak issue?

@johanneskoester Yes. Line ending issues contributes a significant portion of the errors. So in #19 I modified the tests machinery so it can compare expected outputs while ignoring line endings on windows.
https://github.com/snakemake/snakemake/pull/19/files#diff-61d51a325171d97c8a56e59ea525339bL30-R38

@johanneskoester I have updated the pull request that fixes the windows test suite with the original description from bitbucket which explains what the PR does:
https://github.com/snakemake/snakemake/pull/19#issue-326685340

I am closing this. It was just a reference to what was fixed by #19


Improved my implementation

Check List:

[x] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[x] All formatting changes by the build are committed
[x] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable
[x] Output matches that of calculate_average_baseline.sh

Execution time: 8s (Apple M2, 8-core, 8GB)
Execution time of reference implementation: 3m

00:10.553 now, nice. Thx for participating!


Fixed bug in udmx plugin CMake

#1408
https://github.com/mcallegari/qlcplus/issues/1408#issuecomment-1793679159

@mcallegari
I made a stupid mistake.
2 files were totally missing from source list in CMake file of udmx.

ah, sorry!
We made the fix in parallel!
See 5ba3e34543ea8f57f181eb3e994f0de88223e4a7

coverage: 28.067%. remained the same
when pulling 7e50586dced24886e59900c697272b427e0f5a82 on Itay-Lifshitz:master
into 76fff86bd693f573b8b96b0e728b717d3877c821 on mcallegari:master.


Implement Prim's Algorithm  in Java

Issue Description

Need the Java implementation of Prim's algorithm. A non-optimised version will do. You may use an array for the priority queue.
Corresponding post on website
Permitted languages - Java

Guidelines

Your code will be live on a tutorial website, so code readability and understandability will be given paramount importance.
Please follow coding conventions listed in CONVENTIONS.md
The directory structure of the project is pretty obvious, but take a moment to go through STRUCTURE.md if you are confused where to place your code.
Please add a few sample input output test case files too. Minimum 1. The more the merrier!

@VamsiSangam I will work on this.

Sure! Go ahead @ranesr :smile:


Please add SGE and RPR job selections

All jobs but SGE and RPR present. Would be nice to be able to specify the new jobs.

Yup.


Add a global FreezeFS setting and a volume FreezeFS field

Which issue(s) this PR fixes:
longhorn/longhorn#2187
What this PR does / why we need it:

Depending on the global and volume-specific setting, either pass freezeFS == true or freezeFS == false in the proxy snapshot request to the engine.
Make the settings configurable via the REST API.

Depends on:

https://github.com/longhorn/types/pull/8
https://github.com/longhorn/longhorn-engine/pull/1083
https://github.com/longhorn/longhorn-instance-manager/pull/477
https://github.com/longhorn/longhorn/pull/8447

Need to resolve imports before merging.

I ran out of time to retest this now that the dependencies are resolved and coming from the lower-level merged PRs, but I don't anticipate any change in functionality. It is ready for review (and I will retest the full stack before merge).

I retested the full stack and everything is looking good. Please review when you can.


feat(congregation): update user details after congregation info update

:tada: This PR is included in version 2.11.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix transaction snark profiler

This fixes a bug in the transaction SNARK profiler. It was not providing the correct coinbase state.

I think you need to update the CI config files.


Cherry pick - Import aap hint 2.6

related issue: https://github.com/stolostron/backlog/issues/25028
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

/lgtm


853 recreate boxes view

This is part 1 of the implementation of the boxes view in the new frontend. Follow ups to do already identified (there might be more):

adding tests
as soon as the feature "base selector for the current session" is implemented: change the currently hard coded baseId (1) to the selected baseId (@spaudanjo)
write an ADR proposal statement for using chakra-ui and react-table (@spaudanjo)
optimise for mobile screens

Contributes to https://trello.com/c/BGjslF4u/853-recreate-boxes-list-view-in-new-fe

Thanks @vahidbazzaz :)
@flisowna will merge in a few hours as soon as she is back


Select multiple resource into custom action

It looks like if you setup a custom action with a form then it submits that form for each resource that was selected. I'd like the ability to setup an action that only works with multiple resources selected that submits it as 1 request to the backend.
For example, say I have Users (username, email, twitter_url) and I want to merge the duplicated records. It feels like I should be able to create a custom form that has a reference to User with the multiple option selected. Then when I create a custom action that goes to this form, all of the Users would be pre-populated into this field. Maybe something like this submitted to the backend as the post data:
user_ids: [1,2,3]

The request this form hit would have to be setup to figure out how to merge the resources into a single resource and I'd probably setup some extra fields to help that orchestration.

@curtis741 in this case the only way is to use custom form with User reference fields with multi selector to send multiple user_ids to the API.
Using custom resource actions on multiple selected rows is too complex/specific and i think it would be better to avoid adding it as long as the same scenario works with regular custom forms.

Okay. Thanks for the responses @omohokcoj. We've been really enjoying how this project works.


Fix for #870

Closes #870.
Edit: Ah nevermind, I've found devices this doesn't work on.

Ping @D0nPiano because I'm not really a style expert.
Did it work fine on small screens, e.g. mobile phone?

@searchingfor thanks for taking care of #870
I think it would be best for it to not have a specific width (always annoying when it comes to mobile), therefore I would propose something like giving the Search component 100% width (and maybe removing the div around it?), and adding something like:
  width: 100%
  min-width: 200px
  max-width: 400px

to the .searchbar class
I think it would solve the problem (didn't test it yet), and the search bar would still be bigger on desktop than on mobile.
If that doesn't work, than your approach seems better than the current solution though.


dropup class doesn't function correctly

I have a problem getting dropup to work. (demo doesn't display dropup working, which isn't helpful)
https://silviomoreto.github.io/bootstrap-select/examples/#dropup-menu
tried the solution in this issue, and it didn't work:
https://github.com/silviomoreto/bootstrap-select/issues/1050
I also tried with JQuery, and dropup still doesn't take effect:
$('#selections').data("dropupAuto",false).addClass('dropup');

Believe that the documentation is wrong on this, the dropup class should be on the parent/container, not the  itself.

Using data-dropup-auto="false" in conjunction with applying the dropup class on the select element is working for me. If you you can provide an example proving otherwise, I'll reopen.

@caseyjhol Yes this works for me too. Thanks a lot :)

It's not working for 1.13.14. because Popper is autopositioning the menu (regardless of dropup settings). Setting data-display="static" on your select element (in addition to data-dropup-auto="false") should prevent this from happening.


list_snapshots error

I am unable to use https://cloud.ibm.com/apidocs/vpc?code=python#list-snapshots
Is this a defect ?
response = service.list_snapshots()
AttributeError: 'VpcV1' object has no attribute 'list_snapshots'
I have installed pip3 install --upgrade "ibm-vpc>=0.6.0"

From Astha:
Astha Jain
Yes. There were some delays. But this release is going out next week which has snapshots.

:tada: This issue has been resolved in version 0.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


'RuntimeError: No rendezvous handler for env://' with multi-gpu

🐛 Bug
I get an error
'RuntimeError: No rendezvous handler for env://'
when I run my model with multiple GPU.
Below the code and the traceback:
trainer = pl.Trainer(gpus = -1,
                     accelerator='ddp',
                     check_val_every_n_epoch=10,
                    # precision=16,
                    # auto_scale_batch_size='binsearch',
                     callbacks=[checkpoint_callback],
                     max_epochs = 1)

GPU available: True, used: True
TPU available: None, using: 0 TPU cores
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0,1]

trainer.fit(model)

initializing ddp: GLOBAL_RANK: 0, MEMBER: 1/2
Traceback (most recent call last):
File "", line 1, in
trainer.fit(model)
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\pytorch_lightning\trainer\trainer.py", line 470, in fit
results = self.accelerator_backend.train()
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\pytorch_lightning\accelerators\ddp_accelerator.py", line 152, in train
results = self.ddp_train(process_idx=self.task_idx, model=model)
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\pytorch_lightning\accelerators\ddp_accelerator.py", line 252, in ddp_train
self.init_ddp_connection(
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\pytorch_lightning\accelerators\accelerator.py", line 153, in init_ddp_connection
self.ddp_plugin.init_ddp_connection(
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\pytorch_lightning\plugins\ddp_plugin.py", line 90, in init_ddp_connection
torch_distrib.init_process_group(
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\torch\distributed\distributed_c10d.py", line 433, in init_process_group
rendezvous_iterator = rendezvous(
File "C:\Users\45027900\Anaconda3\envs\PyTorch\lib\site-packages\torch\distributed\rendezvous.py", line 82, in rendezvous
raise RuntimeError("No rendezvous handler for {}://".format(result.scheme))
RuntimeError: No rendezvous handler for env://

The error is not present if I set
gpus = 1
Expected behavior

Environment

PyTorch Version (e.g., 1.0): 1.7.1
OS (e.g., Linux): Windows 10
How you installed PyTorch (conda, pip, source): conda
Build command you used (if compiling from source): conda install pytorch torchvision torchaudio cudatoolkit=11.0 -c pytorch
Python version: 3.8.5
CUDA/cuDNN version: 11.0
GPU models and configuration: 2 * Quadro RTX 6000
Any other relevant information:

Also, I don't know if it is related, but when I check the GPU performance during training (with the flag GPU = 1) using windows task manager, I can see only 1-2% used in the GPU, and 45-50% in the CPU. Is this a normal behaviour?

Also, I don't know if it is related, but when I check the GPU performance during training (with the flag GPU = 1) using windows task manager, I can see only 1-2% used in the GPU, and 45-50% in the CPU. Is this a normal behaviour?

@costantinoai mind share what PL version are you using? also, do you have and full example to reproduce?

@costantinoai mind share what PL version are you using? also, do you have and full example to reproduce?

PL version is 1.1.2.
I do have an example, but I would rather not post it publicly. I'll send it to your inbox?

PL version is 1.1.2.
I do have an example, but I would rather not post it publicly. I'll send it to your inbox?

Hi, you can ping me on slack if you want. It's probably an issue with passing the argument gpus=-1 to the script. I bet if you set gpus=n where n is the number of gpus, it will work. We just have to support -1 for ddp.

Hi, you can ping me on slack if you want. It's probably an issue with passing the argument gpus=-1 to the script. I bet if you set gpus=n where n is the number of gpus, it will work. We just have to support -1 for ddp.

Ok, thanks. I’ll try setting n and see what happens. I’ll send you the Colab link on slack if I still have issues.
Really appreciated!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Adrian Wälchli<EMAIL_ADDRESS>Sent: Thursday, January 7, 2021 11:37:33 AM
To: PyTorchLightning/pytorch-lightning<EMAIL_ADDRESS>Cc: Andrea Costantino<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [PyTorchLightning/pytorch-lightning] 'RuntimeError: No rendezvous handler for env://' with multi-gpu (#5358)
Hi, you can ping me on slack if you want. It's probably an issue with passing the argument gpus=-1 to the script. I bet if you set gpus=n where n is the number of gpus, it will work. We just have to support -1 for ddp.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PyTorchLightning/pytorch-lightning/issues/5358#issuecomment-755797802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOCXNCMM3CA3OQJSM2ZAP5DSYT643ANCNFSM4VU7DUZQ.

Ok, thanks. I’ll try setting n and see what happens. I’ll send you the Colab link on slack if I still have issues.
Really appreciated!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Adrian Wälchli<EMAIL_ADDRESS>Sent: Thursday, January 7, 2021 11:37:33 AM
To: PyTorchLightning/pytorch-lightning<EMAIL_ADDRESS>Cc: Andrea Costantino<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [PyTorchLightning/pytorch-lightning] 'RuntimeError: No rendezvous handler for env://' with multi-gpu (#5358)
Hi, you can ping me on slack if you want. It's probably an issue with passing the argument gpus=-1 to the script. I bet if you set gpus=n where n is the number of gpus, it will work. We just have to support -1 for ddp.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PyTorchLightning/pytorch-lightning/issues/5358#issuecomment-755797802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOCXNCMM3CA3OQJSM2ZAP5DSYT643ANCNFSM4VU7DUZQ.

@awaelchli still got the same problem after setting gpus = 2. I reached you on twitter (I don't have a slack account).
Thanks!

@awaelchli still got the same problem after setting gpus = 2. I reached you on twitter (I don't have a slack account).
Thanks!

In summary after private conversation with @costantinoai

ddp not supported on windows platform (yet)
script needs guard around entry point (if __name__ == "__main__")

if these requirements are not met, we see the No rendezvous handler for env://' or similar exceptions.

In summary after private conversation with @costantinoai

ddp not supported on windows platform (yet)
script needs guard around entry point (if __name__ == "__main__")

if these requirements are not met, we see the No rendezvous handler for env://' or similar exceptions.

Hi,  I also get this error when adding the second gpu to machine:
RuntimeError: No rendezvous handler for env://
please advise how to fix and/or work around?
Thx!

Hi,  I also get this error when adding the second gpu to machine:
RuntimeError: No rendezvous handler for env://
please advise how to fix and/or work around?
Thx!

RuntimeError: No rendezvous handler for env://
That's not much information, but one possibility is because you are on Windows.
accelerator=ddp will not work on windows, you have to choose dp.

RuntimeError: No rendezvous handler for env://
That's not much information, but one possibility is because you are on Windows.
accelerator=ddp will not work on windows, you have to choose dp.

I am on windows and saw this error. change accelerator to 'dp' works.

I am on windows and saw this error. change accelerator to 'dp' works.

Windows 10 user here.. this worked for me

I am on Pytorch-Lightning 1.2.1. and it seems I still run into the issue on Windows if I set accelerator to "dp". I am training on 1 GPU.
I encounter this issue when I use DeepSpeed plugin.

@carlomarxdk is deepspeed supported on windows? I can't find any mention of it, so probably not.


Feat/314 gridsystem

@vrwebdesign please delete storybook files

@vrwebdesign

Delete storybook files
Delete old grid files
It is preferred to change the files to Grid and GridItem.svelte (we may discuss about this)
Change SCSS file names to be matched with component names (ie: col.scss should be griditem.scss)
Add col-sm, col-xs, etc. properties and css

@vrwebdesign we may talk more about this


Update rest-text-to-speech.md

brazil is confirmed to be removed. (to be supported after //build)

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

#please-close
We will address in azure-docs-pr. @qiliao123 please submit your PRs against azure-docs-pr in the future, especially for Build deliverables.


fix is_empty and read_file op api_doc

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

Can one of the admins verify this patch?


EVP_PKEY_CTX_get_ecdh_kdf_md doesn't work when using the FIPS provider

If you run the following test case using both the default provider and the FIPS provider, you will notice that EVP_PKEY_CTX_get_ecdh_kdf_md incorrectly returns NULL when using the FIPS provider:
#include <openssl/core_names.h>
#include <openssl/decoder.h>
#include <openssl/ec.h>
#include <openssl/err.h>
#include <openssl/evp.h>
#include <openssl/params.h>
#include <openssl/provider.h>
#include <stdio.h>

static const unsigned char kExampleECKeyDER[] = {
    0x30, 0x77, 0x02, 0x01, 0x01, 0x04, 0x20, 0x71, 0x11, 0x11, 0x37, 0x68,
    0x6f, 0x3b, 0xe4, 0xc5, 0x20, 0x62, 0x77, 0xfc, 0x9e, 0x14, 0x35, 0x7a,
    0x90, 0x75, 0x2b, 0x84, 0x59, 0x14, 0xd6, 0x81, 0x3c, 0xfb, 0x97, 0x13,
    0x0f, 0x3e, 0x43, 0xa0, 0x0a, 0x06, 0x08, 0x2a, 0x86, 0x48, 0xce, 0x3d,
    0x03, 0x01, 0x07, 0xa1, 0x44, 0x03, 0x42, 0x00, 0x04, 0x01, 0x72, 0xdf,
    0x6b, 0x4c, 0xe2, 0x3a, 0x17, 0xd7, 0x6b, 0x41, 0xf7, 0x24, 0x33, 0xdd,
    0x62, 0xab, 0x6b, 0xd3, 0xaf, 0xbd, 0x1b, 0xdd, 0xc2, 0x5c, 0x94, 0x03,
    0xab, 0xe4, 0x05, 0x23, 0x38, 0x95, 0xc2, 0x33, 0x70, 0x35, 0xfe, 0xce,
    0x04, 0x3c, 0xc9, 0x06, 0x1d, 0x00, 0xba, 0x1f, 0x9b, 0xec, 0x95, 0x3c,
    0x63, 0x3d, 0x13, 0x53, 0x78, 0x6c, 0x14, 0x3e, 0xbd, 0x80, 0xdd, 0x98,
    0x51
};

int main(int argc, char **argv)
{
    const unsigned char *key = kExampleECKeyDER;
    size_t keylen = sizeof(kExampleECKeyDER);
    int libno = ERR_get_next_error_library();
    OSSL_DECODER_CTX *dctx = NULL;
    EVP_PKEY *pkey = NULL;
    EVP_PKEY_CTX *pctx = NULL;
    const EVP_MD *md;
    int ok = 0;

    if (argc != 2) {
        fprintf(stderr, "usage: %s <provider>\n", argv[0]);
        return 1;
    }

    if (OSSL_PROVIDER_load(NULL, argv[1]) == NULL) {
        fprintf(stderr, "cannot load %s provider\n", argv[1]);
        goto done;
    }
    if (OSSL_PROVIDER_load(NULL, "base") == NULL) {
        fprintf(stderr, "cannot load base provider\n");
        goto done;
    }

    if ((dctx = OSSL_DECODER_CTX_new_for_pkey(&pkey, NULL, NULL, NULL,
                                              OSSL_KEYMGMT_SELECT_ALL, NULL,
                                              NULL)) == NULL) {
        fprintf(stderr, "err: OSSL_DECODER_CTX_new_for_key\n");
        goto done;
    }
    if (!OSSL_DECODER_from_data(dctx, &key, &keylen)) {
        fprintf(stderr, "err: OSSL_DECODER_from_data\n");
        goto done;
    }
    if ((pctx = EVP_PKEY_CTX_new_from_pkey(NULL, pkey, NULL)) == NULL) {
        fprintf(stderr, "err: EVP_PKEY_CTX_new_from_pkey\n");
        goto done;
    }
    if (!EVP_PKEY_derive_init(pctx)) {
        fprintf(stderr, "err: EVP_PKEY_derive_init\n");
        goto done;
    }
    if (!EVP_PKEY_CTX_set_ecdh_kdf_md(pctx, EVP_sha256())) {
        fprintf(stderr, "err: EVP_PKEY_CTX_set_ecdh_kdf_md\n");
        goto done;
    }
    if (!EVP_PKEY_CTX_get_ecdh_kdf_md(pctx, &md)) {
        fprintf(stderr, "err: EVP_PKEY_CTX_get_ecdh_kdf_md\n");
        goto done;
    }
    if (md != EVP_sha256())
        fprintf(stderr, "unexpected md (%p)\n", md);
    else
        printf("success!\n");

    ok = 1;

 done:
    EVP_PKEY_CTX_free(pctx);
    OSSL_DECODER_CTX_free(dctx);
    EVP_PKEY_free(pkey);

    if (!ok)
        ERR_print_errors_fp(stderr);

    return ok ? 0 : 1;
}

The output gives:
$ ./test default
success!
$ ./test fips
unexpected md ((nil))

The issue is that when evp_pkey_ctx_ctrl_to_param queries the digest from the ecdh EVP_KEYEXCH implementation that is on the FIPS provider side, the digest name that is returned is "SHA2-256" - this is the name that the EVP_MD is initialized with because it's the first name of the underlying algorithm. evp_pkey_ctx_ctrl_to_param then tries to map this name to a legacy EVP_MD in fix_md, using evp_get_digestbyname_ex. Because evp_get_digestbyname_ex looks up the names on the application's library context, the lookup fails because the application's library context hasn't loaded any digests yet. The application's library context only contains a mapping with the name "SHA256", which was created during the call to OPENSSL_init_crypto.
This has implications at least for openssl-cms, which currently ignores the -keyopt ecdh_kdf_md:sha256 argument when using the FIPS provider and just uses SHA1 for the key agreement, because of this code here: https://github.com/openssl/openssl/blob/8c7d847e2e6ac6bfded210c19fd8461254bb2be3/crypto/cms/cms_ec.c#L309
(Tested with 8c7d847e2e6ac6bfded210c19fd8461254bb2be3)

marking as inactive, will be closed at the end of the 3.4 dev cycle barring further input

This is very interesting corner case bug that we should IMO investigate fix for.

It seems that my report #24004 is duplicated with this one.
Should I close mine?

Changing the above code to
    cmd = EVP_MD_fetch(NULL, "SHA256", NULL);
    if (!EVP_PKEY_CTX_set_ecdh_kdf_md(pctx, cmd)) {
        fprintf(stderr, "err: EVP_PKEY_CTX_set_ecdh_kdf_md\n");
        goto done;
    }
    if (!EVP_PKEY_CTX_get_ecdh_kdf_md(pctx, &md)) {
        fprintf(stderr, "err: EVP_PKEY_CTX_get_ecdh_kdf_md\n");
        goto done;
    }

fixes the failure

The call to EVP_PKEY_CTX_set_ecdh_kdf_md(pctx, EVP_sha256())) works correctly (i.e. it does a fetch inside ecdh_ecxh.c)
So it is the getter that the issue (especially if it has code in cms that sets the value to SHA1 if the get returns NIL)

It doesnt matter what I pass to the set..
calling EVP_MD_fetch(NULL, "SHA256", NULL); anywhere populates the namemap otherwise it doesnt.
The name returned from the ecdh_exch is "SHA2-256" for both cases
fix_cipher_md() calls get_algo_by_name() which calls get_md_by_name() which calls evp_get_digestbyname_ex().
    dp = (const EVP_MD *)OBJ_NAME_get(name, OBJ_NAME_TYPE_MD_METH);

    if (dp != NULL)
        return dp;

    namemap = ossl_namemap_stored(libctx);
    id = ossl_namemap_name2num(namemap, name);
    if (id == 0)
        return NULL;

dp is NULL since there is no alias for "SHA2-256"
And without the call to EVP_MD_fetch() id returns 0.

@t8m @nhorman @levitte any thought on this?

Yeah, our "on-demand" fetching has consequences.  Like @slontis says, a workaround is indeed to fetch something known (preferably from the intended provider, see suitable properties) to get the proverbial ball rolling...

Fix in #24940


System wide switch?

Is it possible to have a system wide effect? If not, can we have one?
Pretty pritty pleeeeeeeeeze!
Below is from an installation as regular user:

(Ignore that the editor is not switched -- that's a different wish.)

I think generally you shouldnt start kate as root user. If you want to edit system files, you can open them as you would normally. On save, you will be prompted to enter your password.

Absolutely! This was only a demo to show that Y-Y does not effect changes for root (here, the toolbar).

A theoretical workaround:
Install Y-Y as root, for all users. The latter ~/.config/yin_yang/yin_yang.json would be links to /root/.config/yin_yang/yin_yang.json that has to allow read access.


Restarting dev server resets build version

Hello,
First of all, thank you for making this useful plugin!
I've just started to use it and I noticed that if I stop the server and start it again, it will generate v1.0.0-build.2 again which is usually older than the version I had before and I have to reinstall the script manually (by clicking "Downgrade").
Is there a way to remember build number to make development easier? Or maybe just use current time: Date.now() as build version, that way it will always generate bigger number.
 Thanks for the feedback.

@Juraj-Masiar It actually can be achieved in the current version with using HeaderProvider.
HeaderProvider will be called after each compilation.
In the webpack.config.js, construct the plugin instance with the following options,
new WebpackUserscript({
  headers ({ version }) {
    const buildTime = Date.now()
    return {
      version: `${version}-build.${buildTime}`
    }
  }
})

Instead of changing the current buildNo, I think a new variable buildTime can be provided as well in the future version, then you can use it in the template string instead of using HeaderProvider function.

Nice! It works perfect!
Good thinking :)
Feel free to close this, but I do like the idea with the buildTime variable, I'm sure other would appreciate it as well.
Thanks again for fast fix!

Closed by #18


CI: K8sAgentChaosTest Connectivity demo application Endpoint can still connect while Cilium is not running

Test Name
K8sAgentChaosTest Connectivity demo application Endpoint can still connect while Cilium is not running

Failure Output
The following controller was failing consistently in `cilium status`:

	   sync-to-k8s-ciliumendpoint (2705)             never          6s ago       3       endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"

Stack Trace
/home/jenkins/workspace/Cilium-PR-K8s-1.22-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:453
cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc0015bbfc0>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: controllers are failing: cilium-agent 'cilium-r4x8x': controller sync-to-k8s-ciliumendpoint (2705) is failing: Exitcode: 0 \nStdout:\n \t KVStore:                Ok   Disabled\n\t Kubernetes:             Ok   1.22 (v1.22.13) [linux/amd64]\n\t Kubernetes APIs:        [\"cilium/v2::CiliumClusterwideNetworkPolicy\", \"cilium/v2::CiliumNetworkPolicy\", \"cilium/v2::CiliumNode\", \"cilium/v2alpha1::CiliumEndpointSlice\", \"core/v1::Namespace\", \"core/v1::Node\", \"core/v1::Pods\", \"core/v1::Service\", \"discovery/v1::EndpointSlice\", \"networking.k8s.io/v1::NetworkPolicy\"]\n\t KubeProxyReplacement:   Disabled   \n\t Host firewall:          Disabled\n\t CNI Chaining:           none\n\t CNI Config file:        CNI configuration file management disabled\n\t Cilium:                 Ok   1.13.0-rc4 (v1.13.0-rc4-bcbf9284)\n\t NodeMonitor:            Listening for events on 3 CPUs with 64x4096 of shared memory\n\t Cilium health daemon:   Ok   \n\t IPAM:                   IPv4: 4/254 allocated from <IP_ADDRESS>/24, IPv6: 4/254 allocated from fd02::100/120\n\t IPv6 BIG TCP:           Disabled\n\t BandwidthManager:       Disabled\n\t Host Routing:           Legacy\n\t Masquerading:           IPTables [IPv4: Enabled, IPv6: Enabled]\n\t Controller Status:      28/29 healthy\n\t   Name                                          Last success   Last error   Count   Message\n\t   bpf-map-sync-cilium_lxc                       5s ago         never        0       no error                                                                                \n\t   cilium-health-ep                              44s ago        never        0       no error                                                                                \n\t   dns-garbage-collector-job                     48s ago        never        0       no error                                                                                \n\t   endpoint-1143-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-2249-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-2705-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-516-regeneration-recovery            never          never        0       no error                                                                                \n\t   endpoint-gc                                   3m48s ago      never        0       no error                                                                                \n\t   ipcache-inject-labels                         3m39s ago      3m46s ago    0       no error                                                          ...

Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.22-kernel-4.9/src/github.com/cilium/cilium/test/k8s/assertion_helpers.go:107

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
⚠  Number of "level=warning" in logs: 27
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 2 errors/warnings:
could not take ownership of existing ciliumendpoint
Unable to restore endpoint, ignoring
Cilium pods: [cilium-r4x8x cilium-tkxgn]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                           Ingress   Egress
coredns-69b675786c-pzrjv      false     false
grafana-5747bcc8f9-g6vk9      false     false
prometheus-655fb888d7-qqkqf   false     false
⚠  Cilium agent 'cilium-r4x8x': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 29 Failed 1
Failed controllers:
 controller sync-to-k8s-ciliumendpoint (2705) failure 'endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"'
Cilium agent 'cilium-tkxgn': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 24 Failed 0
Failed controllers:
 controller sync-to-k8s-ciliumendpoint (2705) failure 'endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"'

Standard Error
19:29:55 STEP: Running BeforeAll block for EntireTestsuite K8sAgentChaosTest
19:29:55 STEP: Ensuring the namespace kube-system exists
19:29:55 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
19:29:55 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
19:29:55 STEP: Installing Cilium
19:29:56 STEP: Waiting for Cilium to become ready
19:30:07 STEP: Validating if Kubernetes DNS is deployed
19:30:07 STEP: Checking if deployment is ready
19:30:07 STEP: Checking if kube-dns service is plumbed correctly
19:30:07 STEP: Checking if pods have identity
19:30:07 STEP: Checking if DNS can resolve
19:30:11 STEP: Kubernetes DNS is up and operational
19:30:11 STEP: Validating Cilium Installation
19:30:11 STEP: Performing Cilium controllers preflight check
19:30:11 STEP: Performing Cilium status preflight check
19:30:11 STEP: Performing Cilium health check
19:30:11 STEP: Checking whether host EP regenerated
19:30:19 STEP: Performing Cilium service preflight check
19:30:19 STEP: Performing K8s service preflight check
19:30:25 STEP: Cilium is not ready yet: controllers are failing: cilium-agent 'cilium-r4x8x': controller sync-to-k8s-ciliumendpoint (2705) is failing: Exitcode: 0
Stdout:
 	 KVStore:                Ok   Disabled
	 Kubernetes:             Ok   1.22 (v1.22.13) [linux/amd64]
	 Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumEndpointSlice", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
	 KubeProxyReplacement:   Disabled
	 Host firewall:          Disabled
	 CNI Chaining:           none
	 CNI Config file:        CNI configuration file management disabled
	 Cilium:                 Ok   1.13.0-rc4 (v1.13.0-rc4-bcbf9284)
	 NodeMonitor:            Listening for events on 3 CPUs with 64x4096 of shared memory
	 IPAM:                   IPv4: 4/254 allocated from <IP_ADDRESS>/24, IPv6: 4/254 allocated from fd02::100/120
	 IPv6 BIG TCP:           Disabled
	 BandwidthManager:       Disabled
	 Host Routing:           Legacy
	 Masquerading:           IPTables [IPv4: Enabled, IPv6: Enabled]
	 Controller Status:      26/28 healthy
	   Name                                          Last success   Last error   Count   Message
	   bpf-map-sync-cilium_lxc                       9s ago         never        0       no error
	   cilium-health-ep                              8s ago         never        0       no error
	   dns-garbage-collector-job                     12s ago        never        0       no error
	   endpoint-1143-regeneration-recovery           never          never        0       no error
	   endpoint-2249-regeneration-recovery           never          never        0       no error
	   endpoint-2705-regeneration-recovery           never          never        0       no error
	   endpoint-516-regeneration-recovery            never          never        0       no error
	   endpoint-gc                                   12s ago        never        0       no error
	   ipcache-inject-labels                         never          10s ago      7       k8s cache not fully synced
	   k8s-heartbeat                                 12s ago        never        0       no error
	   link-cache                                    9s ago         never        0       no error
	   metricsmap-bpf-prom-sync                      7s ago         never        0       no error
	   resolve-identity-2249                         8s ago         never        0       no error
	   restoring-ep-identity (1143)                  10s ago        never        0       no error
	   restoring-ep-identity (2705)                  10s ago        never        0       no error
	   restoring-ep-identity (516)                   10s ago        never        0       no error
	   sync-endpoints-and-host-ips                   10s ago        never        0       no error
	   sync-lb-maps-with-k8s-services                9s ago         never        0       no error
	   sync-policymap-1143                           8s ago         never        0       no error
	   sync-policymap-2705                           5s ago         never        0       no error
	   sync-policymap-516                            5s ago         never        0       no error
	   sync-to-k8s-ciliumendpoint (1143)             10s ago        never        0       no error
	   sync-to-k8s-ciliumendpoint (2249)             8s ago         never        0       no error
	   sync-to-k8s-ciliumendpoint (2705)             never          6s ago       3       endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"
	   sync-to-k8s-ciliumendpoint (516)              10s ago        never        0       no error
	   template-dir-watcher                          never          never        0       no error
	   waiting-initial-global-identities-ep (2705)   10s ago        never        0       no error
	   waiting-initial-global-identities-ep (516)    10s ago        never        0       no error
	 Proxy Status:            OK, ip <IP_ADDRESS>, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok   Current/Max Flows: 60/65535 (0.09%), Flows/s: 11.01   Metrics: Disabled
	 Encryption:              Disabled
	 Cluster health:          2/2 reachable   (2023-01-23T19:30:14Z)

Stderr:
 	 Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init)

...
FAIL: cilium pre-flight checks failed
Expected
    <*errors.errorString | 0xc0015bbfc0>: {
        s: "Cilium validation failed: 4m0s timeout expired: Last polled error: controllers are failing: cilium-agent 'cilium-r4x8x': controller sync-to-k8s-ciliumendpoint (2705) is failing: Exitcode: 0 \nStdout:\n \t KVStore:                Ok   Disabled\n\t Kubernetes:             Ok   1.22 (v1.22.13) [linux/amd64]\n\t Kubernetes APIs:        [\"cilium/v2::CiliumClusterwideNetworkPolicy\", \"cilium/v2::CiliumNetworkPolicy\", \"cilium/v2::CiliumNode\", \"cilium/v2alpha1::CiliumEndpointSlice\", \"core/v1::Namespace\", \"core/v1::Node\", \"core/v1::Pods\", \"core/v1::Service\", \"discovery/v1::EndpointSlice\", \"networking.k8s.io/v1::NetworkPolicy\"]\n\t KubeProxyReplacement:   Disabled   \n\t Host firewall:          Disabled\n\t CNI Chaining:           none\n\t CNI Config file:        CNI configuration file management disabled\n\t Cilium:                 Ok   1.13.0-rc4 (v1.13.0-rc4-bcbf9284)\n\t NodeMonitor:            Listening for events on 3 CPUs with 64x4096 of shared memory\n\t Cilium health daemon:   Ok   \n\t IPAM:                   IPv4: 4/254 allocated from <IP_ADDRESS>/24, IPv6: 4/254 allocated from fd02::100/120\n\t IPv6 BIG TCP:           Disabled\n\t BandwidthManager:       Disabled\n\t Host Routing:           Legacy\n\t Masquerading:           IPTables [IPv4: Enabled, IPv6: Enabled]\n\t Controller Status:      28/29 healthy\n\t   Name                                          Last success   Last error   Count   Message\n\t   bpf-map-sync-cilium_lxc                       5s ago         never        0       no error                                                                                \n\t   cilium-health-ep                              44s ago        never        0       no error                                                                                \n\t   dns-garbage-collector-job                     48s ago        never        0       no error                                                                                \n\t   endpoint-1143-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-2249-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-2705-regeneration-recovery           never          never        0       no error                                                                                \n\t   endpoint-516-regeneration-recovery            never          never        0       no error                                                                                \n\t   endpoint-gc                                   3m48s ago      never        0       no error                                                                                \n\t   ipcache-inject-labels                         3m39s ago      3m46s ago    0       no error                                                          ...

Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

to be nil
19:34:11 STEP: Running JustAfterEach block for EntireTestsuite K8sAgentChaosTest
===================== TEST FAILED =====================
19:34:12 STEP: Running AfterFailed block for EntireTestsuite K8sAgentChaosTest
19:34:14 STEP: Cilium is not ready yet: controllers are failing: cilium-agent 'cilium-r4x8x': controller sync-to-k8s-ciliumendpoint (2705) is failing: Exitcode: 0
Stdout:
 	 KVStore:                Ok   Disabled
	 Kubernetes:             Ok   1.22 (v1.22.13) [linux/amd64]
	 Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "cilium/v2alpha1::CiliumEndpointSlice", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
	 KubeProxyReplacement:   Disabled
	 Host firewall:          Disabled
	 CNI Chaining:           none
	 CNI Config file:        CNI configuration file management disabled
	 Cilium:                 Ok   1.13.0-rc4 (v1.13.0-rc4-bcbf9284)
	 NodeMonitor:            Listening for events on 3 CPUs with 64x4096 of shared memory
	 Cilium health daemon:   Ok
	 IPAM:                   IPv4: 4/254 allocated from <IP_ADDRESS>/24, IPv6: 4/254 allocated from fd02::100/120
	 IPv6 BIG TCP:           Disabled
	 BandwidthManager:       Disabled
	 Host Routing:           Legacy
	 Masquerading:           IPTables [IPv4: Enabled, IPv6: Enabled]
	 Controller Status:      28/29 healthy
	   Name                                          Last success   Last error   Count   Message
	   bpf-map-sync-cilium_lxc                       9s ago         never        0       no error
	   cilium-health-ep                              58s ago        never        0       no error
	   dns-garbage-collector-job                     1m2s ago       never        0       no error
	   endpoint-1143-regeneration-recovery           never          never        0       no error
	   endpoint-2249-regeneration-recovery           never          never        0       no error
	   endpoint-2705-regeneration-recovery           never          never        0       no error
	   endpoint-516-regeneration-recovery            never          never        0       no error
	   endpoint-gc                                   4m2s ago       never        0       no error
	   ipcache-inject-labels                         3m53s ago      4m0s ago     0       no error
	   k8s-heartbeat                                 32s ago        never        0       no error
	   link-cache                                    14s ago        never        0       no error
	   metricsmap-bpf-prom-sync                      6s ago         never        0       no error
	   resolve-identity-2249                         3m58s ago      never        0       no error
	   restoring-ep-identity (1143)                  3m59s ago      never        0       no error
	   restoring-ep-identity (2705)                  3m59s ago      never        0       no error
	   restoring-ep-identity (516)                   3m59s ago      never        0       no error
	   sync-endpoints-and-host-ips                   59s ago        never        0       no error
	   sync-lb-maps-with-k8s-services                3m59s ago      never        0       no error
	   sync-policymap-1143                           58s ago        never        0       no error
	   sync-policymap-2249                           54s ago        never        0       no error
	   sync-policymap-2705                           54s ago        never        0       no error
	   sync-policymap-516                            54s ago        never        0       no error
	   sync-to-k8s-ciliumendpoint (1143)             9s ago         never        0       no error
	   sync-to-k8s-ciliumendpoint (2249)             8s ago         never        0       no error
	   sync-to-k8s-ciliumendpoint (2705)             never          8s ago       22      endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"
	   sync-to-k8s-ciliumendpoint (516)              9s ago         never        0       no error
	   template-dir-watcher                          never          never        0       no error
	   waiting-initial-global-identities-ep (2705)   3m59s ago      never        0       no error
	   waiting-initial-global-identities-ep (516)    3m59s ago      never        0       no error
	 Proxy Status:            OK, ip <IP_ADDRESS>, 0 redirects active on ports 10000-20000
	 Global Identity Range:   min 256, max 65535
	 Hubble:                  Ok   Current/Max Flows: 2928/65535 (4.47%), Flows/s: 12.27   Metrics: Disabled
	 Encryption:              Disabled
	 Cluster health:          2/2 reachable   (2023-01-23T19:34:03Z)

Stderr:
 	 Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init)

cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                               READY   STATUS    RESTARTS      AGE     IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-5747bcc8f9-g6vk9           1/1     Running   0             29m     <IP_ADDRESS>      k8s1   <none>           <none>
	 cilium-monitoring   prometheus-655fb888d7-qqkqf        1/1     Running   0             29m     <IP_ADDRESS>       k8s1   <none>           <none>
	 kube-system         cilium-operator-56ff6b46dc-6tpnz   1/1     Running   0             4m21s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-operator-56ff6b46dc-g7rgr   1/1     Running   0             4m21s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-r4x8x                       1/1     Running   0             4m21s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-tkxgn                       1/1     Running   0             4m21s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         coredns-69b675786c-pzrjv           1/1     Running   0             7m47s   <IP_ADDRESS>      k8s2   <none>           <none>
	 kube-system         etcd-k8s1                          1/1     Running   0             34m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running   0             34m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running   3 (29m ago)   34m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-kwd5k                   1/1     Running   0             30m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         kube-proxy-xvgjv                   1/1     Running   0             31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running   3 (29m ago)   34m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-4cltc                 1/1     Running   0             29m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-ntdvp                 1/1     Running   0             29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         registry-adder-h8ggm               1/1     Running   0             30m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-tdndg               1/1     Running   0             30m     <IP_ADDRESS>   k8s2   <none>           <none>

Stderr:

Fetching command output from pods [cilium-r4x8x cilium-tkxgn]
cmd: kubectl exec -n kube-system cilium-r4x8x -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443 (active)
	 2    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53 (active)
	 3    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153 (active)
	 4    <IP_ADDRESS>:3000   ClusterIP      1 => <IP_ADDRESS>:3000 (active)
	 5    <IP_ADDRESS>:9090     ClusterIP      1 => <IP_ADDRESS>:9090 (active)
	 6    <IP_ADDRESS>:443      ClusterIP      1 => <IP_ADDRESS>:4244 (active)

Stderr:

cmd: kubectl exec -n kube-system cilium-r4x8x -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                        IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 516        Disabled           Disabled          10864      k8s:app=prometheus                                                                 fd02::1e0   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=cilium-monitoring
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=prometheus-k8s
	                                                            k8s:io.kubernetes.pod.namespace=cilium-monitoring
	 1143       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                                                ready
	                                                            k8s:node-role.kubernetes.io/control-plane
	                                                            k8s:node-role.kubernetes.io/master
	                                                            k8s:node.kubernetes.io/exclude-from-external-load-balancers
	                                                            reserved:host
	 2249       Disabled           Disabled          4          reserved:health                                                                    fd02::1cc   <IP_ADDRESS>   ready
	 2705       Disabled           Disabled          64571      k8s:app=grafana                                                                    fd02::165   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=cilium-monitoring
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=cilium-monitoring

Stderr:

cmd: kubectl exec -n kube-system cilium-tkxgn -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:3000   ClusterIP      1 => <IP_ADDRESS>:3000 (active)
	 2    <IP_ADDRESS>:9090     ClusterIP      1 => <IP_ADDRESS>:9090 (active)
	 4    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443 (active)
	 5    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53 (active)
	 6    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153 (active)
	 7    <IP_ADDRESS>:443      ClusterIP      1 => <IP_ADDRESS>:4244 (active)

Stderr:

cmd: kubectl exec -n kube-system cilium-tkxgn -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                  IPv6       IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 1158       Disabled           Disabled          4          reserved:health                                                              fd02::8    <IP_ADDRESS>    ready
	 1332       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                                           ready
	                                                            reserved:host
	 1515       Disabled           Disabled          4099       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system   fd02::5d   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns

Stderr:

Resources

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.22-kernel-4.9/392/testReport/junit/Suite-k8s-1/22/K8sAgentChaosTest_Connectivity_demo_application_Endpoint_can_still_connect_while_Cilium_is_not_running/
ZIP file(s):
566295da_K8sAgentChaosTest_Connectivity_demo_application_Endpoint_can_still_connect_while_Cilium_is_not_running.zip

Anything else?
Related: a1c33d8c4e752 (https://github.com/cilium/cilium/pull/21768) cc @tom-hadlaw-hs

This can cause many subsequent tests to fail during the "BeforeAll" stage.

Hi,
The following controller was failing consistently in `cilium status`:

	   sync-to-k8s-ciliumendpoint (2705)             never          6s ago       3       endpoint sync could not take ownership of CEP "cilium-monitoring/grafana-5747bcc8f9-g6vk9", endpoint UID ("80d05f47-52b3-47b2-89f1-84c77a6e7c38") did not match CEP UID: "fa3d16e5-1dcd-450c-9a74-89522a85508e"

We also see this issue on v1.12.  Do we have a RCA for this?


Store nginx files path in .env

Repeating the path so many times is tedious and error prone. Now, one can specify it once in an .env file.

Nice, thanks!


Registry types in const

Hi, I would want to use core cosmos registry types in some consts/enums, but couldn't find them, are they exist?
I did this PR, but realized that this should be done in Cosmos libs, not by devs in theirs projects.
Or how to do it correct?

Created thread in Cosmos discord - https://discord.com/channels/669268347736686612/1195340710333911050/1195340710333911050


[Investigate] Use on the invoice the same customer details as the ones on the proforma

What is to investigate here?

When a proforma is issued the details of the customer should be copied into archived_customer
If a proforma is paid and the provider's flow is proforma, when creating the invoice automatically, it should copy the archived details of the customer and use those instead of retrieving the details from the related customer object. The details might have changed and we should keep the ones from the proforma.

These 2 aspects should be investigated as they are related and 2) does not work without 1).

and 2) are already happening.

A new one:
3) When the document entries are generated we need to make sure the generator uses the frozen details (such as sales_tax_percent and sales_tax_name) and not the ones from the related customer object.


[ja] Localize virtualization for Japanese

Describe your changes
Localize virtualization for Japanese.
不自然にならないよう元の文章を複数に分けていたりします。
元の文意が失われてないかも確認いただけたら嬉しいです。
Related issue number or link (ex: resolves #issue-number)
#2444
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@yuichi-nakamura
Thank you for your comments!
I completely agree with your feedback and have fixed the contents.
Would you please check again?


Wagtail 1.4.x breaks image conversion

Hi, I've been diving into the source code for wagtail trying to figure out why code we had written to create circle-cropped image renditions no longer works in wagtail 1.4.x when it worked fine in 1.3.x and earlier. There is definitely some re-work on our part that needs to be done, but I think I've got a good handle on most of that now.
The piece that is missing can be found here: https://github.com/torchbox/wagtail/blob/stable/1.3.x/wagtail/wagtailimages/models.py
vs.
https://github.com/torchbox/wagtail/blob/stable/1.4.x/wagtail/wagtailimages/models.py
Around line 388; in the run of the Filter, in wagtail 1.3.x the output format of the image rendition was determined AFTER all the operations on it had been performed, which allowed us to apply an alpha layer and save any image as a PNG, simply by changing the original_format.
In wagtail 1.4.x however, the original image format is stored BEFORE any operations are performed and then used to save the image. So it doesn't matter what our custom operations tell wagtail the file should be saved as, any image rendition will always be saved as in the same format as the original image.

Hi @miscellainiac Before 1.4 the internal image operations/willow APIs were considered "unstable", so I wouldn't consider this a bug (but as of Wagtail 1.4 and Willow 0.3 they are stable and will no longer be changed without our standard deprecation process).
The fact that the original_format could be used to change the output format was just a side-effect of how the code was implemented. But I'd like to implement an official way of doing this by adding a get_properties method to image operations (see https://github.com/torchbox/wagtail/pull/1847#issuecomment-157857150).


Create proper support for Upstream proxy supporting username, passwor…

…d, and ssl fixes

Add support for passing a function to figure out a per request based proxy

Now we can support authentication if a func is passed in for both http and https requets.  Supports basic authentication

@ilushka85 Good work. Can you fix merge conflicts please. I don't want to merge this to master. Lets do a beta release by committing to release branch.

Just merged in release and fixed the conflicts.  Also added some more params to SessionEventArgs


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.452

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.452


[Feature Request] API Enhancement for Fetching Bookmarks/Tags that have been Modified or Created after Date

Would it be possible to add a feature to the api to only retrieve objects that have been updated or created after a certain date? This would prevent having to re-fetch all after the initial download.

That should be possible, each bookmark has a creation and update timestamp.


DOC: there is no issue only updated the document UI

What's wrong with the existing documentation
There is no issue only update the document UI. Change in navbar, footer, and some content on the webpage.
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[x] I want to work on this issue

there is no issue only update the document UI. Change in navbar, footer, and some content on the webpage


Minor fixups in log handling

I've been looking at the log handling code in preparation to send that data via the network.
Microsoft Reviewers: Open in CodeFlow

/azp run


Update UG

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@53fe5f4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #23   +/-   ##
=========================================
  Coverage          ?   72.15%
  Complexity        ?      399
=========================================
  Files             ?       70
  Lines             ?     1232
  Branches          ?      125
=========================================
  Hits              ?      889
  Misses            ?      311
  Partials          ?       32

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53fe5f4...94dc61e. Read the comment docs.


Throwing exception when checker fails to run

Scalastyle checker silently swallows exceptions, e.g. Scalastyle runs fine with the following configuration file reporting no errors:
<scalastyle>
  <name>Scalastyle configuration</name>
  <check level="error" class="this.does.not.Exist!" enabled="true"/>
</scalastyle>

It's error-prone. A project can keep thinking its configuration is right, while it's a simple typo in class name.
The downside of the solution is that it reports an error for each checked file. I believe it's strictly better than the current swallowing though.

Codecov Report

Merging #297 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff          @@
##           master   #297   +/-   ##
=====================================
  Coverage       0%     0%
=====================================
  Files          59     59
  Lines        1464   1464
  Branches      147    147
=====================================
  Misses       1464   1464

Impacted Files
Coverage Δ

src/main/scala/org/scalastyle/Checker.scala
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 54198e2...d37967e. Read the comment docs.

Thanks for thie PR. I need to think about this, and I'll get back to you.


HTTPS Proxy setup issues (OPENSSL_internal:HTTPS_PROXY_REQUEST)

I'm trying to setup a swift-nio/swift-nio-ssl based server that is capable of acting as a https proxy server.
When adding the SSLServerHandler I'm constantly getting
handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: 268435611 error:1000009b:SSL routines:OPENSSL_internal:HTTPS_PROXY_REQUEST]))
Errors. Any help is highly appreciated :-)
Thanks,
Philipp

In general when a HTTP proxy is interposed between a client and a server and that client is aware of the proxy, the client will issue a HTTP CONNECT request to establish the connection. This will establish an opaque TCP tunnel through the proxy to the remote peer, at which point TLS will be negotiated over that reverse proxy. This means the proxy itself never terminates the TLS, and so SSLServerHandler should not be necessary.
So my question is: when you say "a https proxy server", what specific behaviour do you want to achieve?

Thanks for your quick reply. I'm trying to intercept http/https calls made on a device by setting up a http/https proxy that handles all the requests coming in. I'm not an expert in this area so my terminology might be wrong ....
My https proxy server should be able pretend to be the receiver of the https request and act as the original target of the request.

My https proxy server should be able pretend to be the receiver of the https request and act as the original target of the request.

This is a complex thing to do unless the target turns off its certificate validation.
What you're asking to do is similar to what mitmproxy and Charles proxy to do, which is to inject yourself as a man-in-the-middle. If you want to do this in the same way that those two entities do, you need to write code to build an automated certificate authority that can issue new certificates in response to inbound TCP connections. This is quite a lot of code to write, and it's definitely beyond what I can reasonably help you with in a GitHub issue. Suffice to say that this project only provides tools for the TLS: the generation and signing of certificates is outside the scope of this project.
If you're willing to disable certificate validation on the clients, then it gets easier: you can just present a self-signed certificate. What you have to do here is deal with the fact that the client is going to send a CONNECT request to you before it attempts to start speaking TLS. In your case this is easy enough to deal with: just respond to the CONNECT request before you add your TLS handler.
Essentially, you want a channel handler that listens for an inbound CONNECT request, adds the SSLHandler behind it, responds with a 200 OK message and then removes itself from the pipeline. Then you should be good to go.

Of course, if you are interested in just seeing the data more than building the tool, I recommend using mitmproxy or Charles, as they'll work out-of-the-box to achieve what you want to achieve.

I think using self-signed certificate would work for me. Thanks for pointing me in the right direction. Is there any example code that is also dynamically adding and removing handlers that I can take as a starting point?

There should be plenty, but looking at things like NIO's HTTPServerUpgradeHandler shows some example of that code.

Awesome, thanks for your support!


Page load time number in Firefox 92.0 is cut

The latest version of Firefox probably limits overflow on icons in toolbar so now it is partially hidden as seen on the above screenshot.

Unfortunately I cannot control that. Probably for FF I will use one less char so it will be one digit after decimal point in most cases.

Thanks!


feat: add payload option to GET subscriber feed api

closes #23
changes

SubscriberNotificationFeedOptions struct to support payload query
GetNotificationFeed to convert the payload to base64 and send
noticed wrong type for CTA.Action.Buttons, changed type to Array

@sumitsaurabh927  @unicodeveloper  can review plz?

@jainpawan21  @unicodeveloper  i was checking here https://github.com/novuhq/docs , but i dont see any go sdk docs added yet, so seems like documentation can be a separate issue? or am i looking at the wrong place?

@mahendraHegde Never mind.


[Mutator] ManHack

According to the readme, the author's name is  Johannes '[A|K]Leviathan' Sievert

URL: https://unrealarchive.org/mutators/unreal-tournament-2004/M/manhack_1fdbb40d.html
Hash: 1fdbb40dcbe56ca1298c54f51eea2cad874ef0ec
Current name: ManHack

updated


Test changing test data

FOR CONTRIBUTOR:

[ ] - I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
[ ] - License permits unrestricted use (educational + commercial)
[ ] - This PR adds a new tool or tool collection
[ ] - This PR updates an existing tool or tool collection
[ ] - This PR does something else (explain below)

/update-test-data

Hmm.. Seems that the bot can't push to your branch: remote: Permission to simonbray/tools-iuc.git denied to github-actions[bot].
This might be solvable for the autoupdate mechanism, but I have no idea how to deal with this in general ...

/update-test-data

@simonbray just invidet you as collaborator to this project. lets see if you can start update of test data

/update-test-data

Still
remote: Permission to simonbray/tools-iuc.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/simonbray/tools-iuc/': The requested URL returned error: 403

/update-test-data

Same

Maybe its possible to trigger the workflow on your branch .. have to think about this

@bernt-matthias is it possible that I grant the bot access to my fork? I know how to do this for github users, but no idea for actions.
An alternative could be that if the bot cannot push to a branch, to make a pull request instead? Maybe also posting a comment requesting access.

By the way, where is the code for the update-test-data slash command?

@bernt-matthias is it possible that I grant the bot access to my fork? I know how to do this for github users, but no idea for actions.

Don't know.

An alternative could be that if the bot cannot push to a branch, to make a pull request instead? Maybe also posting a comment requesting access.

Good idea. I guess we can manage for the autoupdates to push directly. But in general a PR should be a good fallback.

/update-test-data

@bernt-matthias could you accept my collaboration invite? We didn't try this yet and to me it makes sense (your action is making a change to my fork).

@bernt-matthias could you accept my collaboration invite? We didn't try this yet and to me it makes sense (your action is making a change to my fork).

Done


Start next download in queue earlier

There seems to be these 4 states for a download:

Downloading
Merging files
Converting video
Done

Currently, the next item in the queue is only started once the current one reaches Done.
But neither Merging files nor Converting video uses any network bandwidth (I assume), so it would be great if the next item in the queue could start downloading as soon as the current one is done Downloading instead.

#458


Test bug

The test output before the fix was:
Running test/handler/fee_change.test.mo
 ✖
 FAIL src/TokenHandler/AccountManager.mo:325:13: execution error, arithmetic overflow
   ...
   324	|             debit(p, deposit - prevFee);
-> 325	|             queuedFunds -= deposit;
   326	|           };
   ...

Before the fix, there were these problems:

debit(p, deposit - fee_);
This command would run twice. Once in consolidate and then again inside recalculateDepositRegistry, resulting in an under-credit for p.

queuedFunds -= deposit
This is not supposed to run for the p for which consolidation just failed. Because deposit was already moved from queuedFunds to underwayFunds. So this causes an underflow which makes the test fail.

ignore updateDeposit(p, 0);
This would also run twice but has no negative effect because it is idempotent.


USER->VIEW CART: minus button cannot reach to zero; when it reached zero it is good as deleted

not an issue, already fixed in live

@jenadrianne akong pasabot kay murag naay 2 options sa pag delete, 1st is to click the "delete button" 2nd is when the user keeps on clicking the minus button until mo reach siya ug 0.

kasabot ko sa imo pasabot @duenaser  ako ni gifix
commit id: 325b8155b079f8e5eb2738218166506e7450f182


#157720609 Fix UI bugs

What does this PR do?
It fixes most of the UI bugs that exist in the application.
Description of Task to be completed?
Fix UI bugs.
The current user interface has bugs that would make it difficult for Users to enjoy the value that this platform has to offer. This Pull Request is meant to fix all the major bugs that are identified.
How should this be manually tested?

clone the app and change into the project directory
setup the app(instructions in the readme)
run the tests to ensure that nothing is failing/breaking
visit the app in a browser
explore the various functionalities of the app, everything should still be working fine but with a better User Interface

Any background context you want to provide?
None
What are the relevant pivotal tracker stories?
#157720609
Questions:
None

Coverage increased (+0.06%) to 92.807% when pulling d5a58ecc1be2609b82a10755f39f3dc48f1cd263 on bg-fix-UI-bugs-157720609 into a1f6600a5bd302de1d83acbfd642583d17f4fd67 on develop.


Make options.limit configurable

Feature request: make options.limit configurable

This feature is added in version 0.10.0

Thanks.
Unfortunately it seems the commit broke path were image lives
https://github.com/arefaslani/next-images/commit/cca3ee0fa65cb4f6e408a157e3fd158d8423b11d
-              publicPath: `${assetPrefix}/_next/static/images/`,
+              publicPath: `${assetPrefix}/_next/`,

When I take a look inside my .next I see the image lives in .next/static/images.

Oh sorry! I will correct this now.


Arrow Color

How to change the arrow color ?

Hi @lamer547
ngx-gallery /deep/ .ngx-gallery-icon {
    color: red;
}