How to modify the retention period of Recycle for deleted workitems

In the Azure devops:- What is the default retention period of deleted work items in Recycle bin? Can we change this limit.

@manvendrautralia Thank you for the question.
With no explicit statements made, it would be assumed that items are kept indefinitely until explicitly deleted, see Remove delete work items.
I'll assign the author for further confirmation.
For new feature requests, please see Azure DevOps community for feedback from the product team.

@manvendrautralia Thank you for the question.
With no explicit statements made, it would be assumed that items are kept indefinitely until explicitly deleted, see Remove delete work items.
I'll assign the author for further confirmation.
For new feature requests, please see Azure DevOps community for feedback from the product team.

@msebolt Thanks for your inputs. Please help to get it verified, as we will have to plan our production workloads accordingly.

@manvendrautralia: The items stay in the Recycle bin until someone permanently deletes them. So there is no explicit limit on the Retention Period and no way to change the limit. I'll update the article accordingly.


Issue with Rendering Multiple Geometry Instances Together vs. Separately

When trying to render multiple geometry instances within a single GroundPrimitive, I encounter a rendering issue that doesn't appear when rendering each instance in its own separate GroundPrimitive.
Sandcastle example: URL
Browser: Chrome
Operating System: Windows
Details:

Combined Rendering:
In this approach, I tried to combine multiple geometry instances and pass them to a single GroundPrimitive. This resulted in unexpected rendering or display issues.

Separate Rendering:
Contrarily, when rendering each geometry instance in its own separate GroundPrimitive, the issue does not manifest, and the display is as expected.

I would appreciate insights into why this behavior occurs and how to resolve it.

Thanks for the report @criyson.
Because of the rendering techniques used, geometry instances batched together must be the same color. This is alluded to in the example listed in the GroundPrimitive API reference doc.
I'm closing this as this behavior is not a bug per-say.
However, could you provide more info about why the combined rendering approach is preferable here? Is it for the sake of performance?


keycloak-realm-operator image not available

Describe the bug
When following deployment instructions, an image quay.io/keycloak/keycloak-realm-operator:latest is requested by the Realm Operator deployment. This image is not available, the repository is empty.
Version
20.x
Expected behavior
Deployment succeeds, having pulled quay.io/keycloak/keycloak-realm-operator:latest successfully.
Actual behavior
Image pull fails, deployment fails.
How to Reproduce?

Observe image name in https://raw.githubusercontent.com/keycloak/keycloak-realm-operator/main/deploy/operator.yaml, which is recommended by the docs.
Try pulling quay.io/keycloak/keycloak-realm-operator:latest
Observe pull errors due to missing image.

Anything else?
No response

Thanks for the report. The image should be available now.


Link to the actual tool

I feel humble to have my own tool featured here, but I'd appreciate if the link targets the actual tool and not the old Codeplex repository.

Hi @sebagomez, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@seguler Please review these proposed changes. Thanks.

Hi @sebagomez ,
Would it be better to link to your github repository ? That would give users a chance to evaluate before they submit their account and key to your website.
Thanks!
Sercan

I answered by email but I guess it didn't make it here.
I prefer straight to the site for search engine purposes, there's also a link at the site to the GitHub repo so people can go check it out if they want.

Hey @sebagomez , I don't agree putting a direct link to the website. I'd like users to evaluate the code on github, or codeplex before sharing their account key with the Storage explorer application.

If you agree, will close this PR.

Hi @seguler - Please add an appropriate comment so that automation can take appropriate action. Thanks

@sebagomez Please change this to link to the GitHub repository rather than your site. We won't link to a site that requires the customer to register, it's like giving it our implicit approval.

@GitHubber17 Let's see if the contributor changes the link. I should be on the notifications for this, so if Sercan is still buried, I'll take a look in another week or so and act accordingly.

I still believe you're being unfair to me, other tools are linked directly. But I'll take the link to github.
Thanks

@sebagomez I'm guessing it's because your link goes to your website, which requires the user to register before you even let him into your website, before he knows anything about your tool, and none of the others do. Are you going to change the link in the document?

I already have PR #2412
Thanks

#please-close
PR Mergers -- Apparently the contributor created a new PR for this instead of just updating this PR. So go ahead and close this PR. Thanks. (The new one is here: https://github.com/MicrosoftDocs/azure-docs/pull/2412)


Getting this error while pushing ...@hzoo
ERROR: Permission to babel/babel.github.io.git denied to getonlineamit.

@getonlineamit Fork this repository first and then you need to work on it.

@xtuc i have already forked this repository.

looks like you are trying to push from the wrong branch?
getonlineamit  wants to merge 1 commit into master from kaicataldo-patch-1


The find widget fails to scroll to the next match

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[ ] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
When using Monaco Editor find widget to search for a specific word and clicking on the next match, the editor does not scroll to the next match.
After reviewing the source code, I found that my editor instance sets an adaptive height (refer to this link: can editor stretch to fit its content), which causes the line of the next match to always be within the viewport of the editor(even not in the viewport of document).
If I want to keep the adaptive height of the editor, how can I implement scrolling to the line of the next match when a user clicks on the next/previous match?
Is there an API that can listen for events when a user clicks on the next/previous match and manually implement scrolling to the line of the next match to the viewport of current document?
Monaco Editor Playground Link

Monaco Editor Playground Code
const value = /* set from `myEditor.getModel()`: */ `function searchWorld() {
	alert('Hello world!');

	alert('end: hello,world')
}`;

const width = 300;
const container = document.getElementById('container');
container.style.border = '1px solid #f00';
const editor = monaco.editor.create(container, {
	value,
	language: "javascript",
    scrollBeyondLastLine: false,
    wordWrap: 'on',
    wrappingStrategy: 'advanced',
    minimap: {
        enabled: false
    },
    overviewRulerLanes: 0
});
let ignoreEvent = false;
const updateHeight = () => {
	const contentHeight = Math.min(1000, editor.getContentHeight());
	container.style.width = `${width}px`;
	container.style.height = `${contentHeight}px`;
	try {
		ignoreEvent = true;
		editor.layout({ width, height: contentHeight });
	} finally {
		ignoreEvent = false;
	}
};
editor.onDidContentSizeChange(updateHeight);
updateHeight();

```html

### Reproduction Steps

1. use cmd+f keyboard shortcut to search text "world"
2. click on next match arrow

### Actual (Problematic) Behavior

The line of next matched "world" does not scroll into the viewport of current document

### Expected Behavior

The line of next matched "world" scroll into the viewport of current document

### Additional Context

_No response_

Works for me:

Thank you for your response. I must not have described the issue clearly. Please refer to the video below. There are two instances of 'hello, world' in the editor: one is within the visible area, and the other is outside of it. If I type 'hello' and search for it, only the first 'hello' is matched. When I click to match the next instance, the second 'hello' which is outside the visible area does not get matched and does not scroll into view. My expectation is that all matching characters would be able to scroll into the visible area.
https://github.com/microsoft/monaco-editor/assets/24250131/49d3c252-4716-4989-93b8-36cad419fb2e

ok, thanks.

Ahh, I understand. This is because it only scrolls the monaco editor, not any parent containers!
You can try to get the line top value and scroll the parent container yourself. Afaik there is even some dom API.

ok, thanks


yanglint errors when submitted a YANG model draft

Describe the issue
I got the following errors when submitting a draft with YANG data model. I tried a couple of different drafts and got the same errors.
yanglint SO 1.9.2: yanglint --verbose -p {tmplib} -p {rfclib} -p {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
err : Encountered invalid character sequence "
rt
".
err : Module "iana-bfd-types" parsing failed.
err : Importing "iana-bfd-types" module into "ietf-bfd-types" failed.
err : Module "ietf-bfd-types" parsing failed.
err : Importing "ietf-bfd-types" module into "ietf-isis" failed.
err : Module "ietf-isis" parsing failed.
err : Importing "ietf-isis" module into "ietf-isis-remaining-lifetime" failed.
err : Module "ietf-isis-remaining-lifetime" parsing failed.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

@Yingzhen-ietf - changes were made at yangcatalog that should clear this up. It might be tomorrow before these changes propogate to the datatracker though.

Hi Robert,
Thanks for the update and fixing the issue. I'll try uploading drafts
tomorrow.
Thanks,
Yingzhen
On Fri, Mar 1, 2024 at 2:46 PM Robert Sparks @.***>
wrote:

@Yingzhen-ietf https://github.com/Yingzhen-ietf - changes were made at
yangcatalog that should clear this up. It might be tomorrow before these
changes propogate to the datatracker though.
—
Reply to this email directly, view it on GitHub
https://github.com/ietf-tools/datatracker/issues/7122#issuecomment-1974035485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AURDC47JGIMEHUERMBPDT6DYWEAN5AVCNFSM6AAAAABEAQQRJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUGAZTKNBYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing this as OBE


refactor(barchart): reduce some calculations

Calculating label_offset is unnecessary, if we just render the group label after rendering the bars. We can just reuse bar_y.
this commit is getting rid of let label_offset = bars.len() as u16 * (self.bar_width + self.bar_gap) - self.bar_gap;

I am suspecting that the codecov is reduced, because we have one line less in total. If I add somewhere an empty line, I think the codecov will be happy again.
Please write, if I have to add an Empty line.

Thanks for the PR


Improve threading

Improve thread lifecycle

Catch some edge cases in thread lifecycle to avoid starting it twice

Improve tests

Use in_memory_cache for testing to avoid destroying real cache data

Codecov Report

Merging #15 (0cb89ef) into master (0590d82) will decrease coverage by 0.60%.
The diff coverage is 67.92%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   95.58%   94.97%   -0.61%
==========================================
  Files          55       55
  Lines        3761     3784      +23
==========================================
- Hits         3595     3594       -1
- Misses        166      190      +24

Flag
Coverage Δ

unittests
94.97% <67.92%> (-0.61%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

calculate_anything/currency/cache.py
67.85% <58.33%> (-14.09%)
:arrow_down:

calculate_anything/currency/service.py
85.34% <70.73%> (-4.66%)
: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 0590d82...0cb89ef. Read the comment docs.


Measurement gaps result in non-uniform datetime grid and result in interpolation issue with plotting

Need to think of a good way of indicating gaps in data with the xarray plotting. Could either just plot a mask over it and avoid the skipped dates. The issue is that typical data sets would have a regularly gridded timeseries and NaNs or zeros for missing values. Our dataset on the other hand pulls the date values from each measurement, so our missing values also have missing dates, resulting in this lack of a uniform grid. This makes it a bit trickier to define the gaps and properly illustrate them. Below is an example of what happens:

Here, the black dots indicate the timestamps of all the measurements made in the winter season. We see some pretty substantial data gaps, but it's not immediately obvious when plotting the entire profiles which sections are a result of these gaps.

I think the best approach is to identify the gaps by highlighting the irregular spacing in the datetime grid and use that to create a mask. Then we interpolate the data onto a regular grid, and then set the values in the mask to NaN.


[Windows] Switch from Windows 8+ futex to std::mutex.

Restores Windows 7 support.
New Windows 8+ futex implementation was added recently, but seems like it is mostly used by ANGLE over Vulkan backend (which we do not include), it's also disabled in ANGLE builds used by Chromium.

Thanks!


DFCM Lease Locations

Benefit
App created to help DFCM view lease and parcel locations. Short term: list of locations are to be geocoded and displayed in web app, long term: ongoing updates to lease locations and addition of DFCM parcels if they decide to continue with the app.
Acceptance Criteria

[x] Geocode locations and create simple web app.
~- [ ] Pull updates from internal DFCM database with Palletjack.~

Notes
No response
Risks
Geocoding issues with bad source addresses, possible difficult feedback loop.
Issue Reference
refs #

App sent for review. Based on feedback filters will be added for agency, department, lease, and city. Fixed popup will be used instead of sidebar.
Update of app data will be done manually every 3 to 6 months. Palletjack will not be needed at this time.


Builds on docs.rs are broken

Open tasks

[x] A PR for 0.5 (relm4 and relm4-components) https://github.com/Relm4/Relm4/pull/316
[x] A backport to the stable branch for 0.4 https://github.com/Relm4/Relm4/pull/293
[x] A new release for 0.4 (I can take care of that)
[ ] The stable docs generated by relm4-docs should show a deprecation warning (I think nightly docs are still kinda nice to have)
[x] We should move some of the pre-proccessed doc headers into the source code (especially the link collection is pretty useful I think). https://github.com/Relm4/Relm4/pull/338
[ ] Update the links on the website and in the README (and everywhere else, probably some links in the book too)

Why is this important?
Whenever a crate is published on crates.io, its documentation is automatically built and linked. Since you added a documentation attribute to the Cargo.toml files, the default link to docs.rs is replaced by that link. I am sure you had some reasons to do that but I am not a fan of it. I know that all gtk crates do that too, so maybe that was the idea. The downside of this is that the documentation is only available in the current version. If I use an older version, I can't have a look at its documentation (or it is not obvious how to do that). Luckily it is always possible to just go to docs.rs/crate/CrateName and view the documentation there. On docs.rs it is possible to look at all previous versions. This is why there is value in having working builds on docs.rs.
What is the issue?
Unfortunately the build of the current version is broken. I had a similar problem with one of my crates and I believe the reason is that the dependencies are not available. This should be possible to be fixed by adding something along the lines of
[package.metadata.docs.rs]
features = ["dox"]

[features]
dox = ["gtk/dox", "adw/dox"]

to the Cargo.toml file. The same also applies to relm-components. relm-macros builds fine.
It is possible to test the build locally by following this guide:
https://github.com/rust-lang/docs.rs/blob/master/README.md#build-subcommand
Explanation of the proposed solution
Here is my understanding of how this fixes the error:
[package.metadata.docs.rs]
features = ["dox"]

This tells docs.rs to activate the feature dox.
[features]
dox = ["gtk/dox", "adw/dox"]

If the feature dox is active, it activates it in the crates gtk4 and libadwaita too. This features allows building the docs without the dependencies.

I love the new 0.5 version by the way. Feels so much easier :+1:  :1st_place_medal:

I would be very happy to have this resolved and the custom build jobs removed. Honestly, maintain the build jobs has been quite a bit of work.
A PR that addresses this should consider adding more doc examples to compensate the loss of the scrape examples feature.

I did not know about the scrape examples feature before. Very interesting. On the page you linked, it says:
To enable this feature on docs.rs, add this to your Cargo.toml:
[package.metadata.docs.rs]
cargo-args = ["-Zunstable-options", "-Zrustdoc-scrape-examples=examples"]

It looks like you could just add that and then there would be no need to make other changes to the documentation.

Nice, I've overlooked that. In this case, we need the following steps

[ ] A PR for 0.5 (relm4 and relm4-components)
[ ] A backport to the stable branch for 0.4
[ ] A new release for 0.4 (I can take care of that)
[ ] The stable docs generated by relm4-docs should show a deprecation warning (I think nightly docs are still kinda nice to have)
[ ] We should move some of the pre-proccessed doc headers into the source code (especially the link collection is pretty useful I think).
[ ] Update the links on the website and in the README (and everywhere else, probably some links in the book too)

Okay, I can work on that. I'll start with the backport since that is the easiest way to see if it actually fixes the builds

Regarding the nightly docs, my suggestion would be to get rid of them too and publish prerelease versions of the crates instead. They will be ignored when running cargo update, but the docs will be built on docs.rs and the version will be visible when clicking on "versions" on crates.io. When searching for a crate, only the most recent stable version will be displayed, so there should not be any danger of users accidentally using unstable versions. An example for a crate that does this is https://crates.io/crates/wayland-server. The way prerelease versions are published seems to be to add something like -beta.2 to the version field in Cargo.toml and running cargo publish. Since you already append these strings to beta versions, all you'd need to do is publish them.
Benefits

you can completely get rid of your custom build jobs
users can use crates.io for unstable versions if they opt-in
users can freely switch between unstable and stable versions

Ah, that's unfortunately true.
I noticed that you removed the documentation field in the Cargo.toml. I think it would be better to keep it and link to docs.rs. The reason for this is some odd behavior on crates.io. When you search for a crate and it does not have the documentation link set, in the search results there will no link to the docs. You will need to click on the crate and on that page, you can click on the documentation. It's just a minor nuisance though, so it's not that important.
You can see this behavior when you search for base64id (just a random crate I quickly found) on crates.io for example.
This for example should work and then the documentation can be opened from the search results without going through the details page:
documentation = "https://docs.rs/relm4/"

Feel free to ping me once a new version is released, then I'll do the changes for 0.5

I think the new version you published will not build. I believe there are some errors with the doc when the tokio-rt feature is active.
:( Sorry about that

Mhh, that's not good but also not that bad either. We can fix it and follow it up by another version.

You probably noticed already, but apparently libadwaita doesn't pass the "dox" feature flag to its dependencies, not even the sys crate which causes the actual problem. The build script that causes the error would work otherwise.

Yes, I created a Gitlab account and will create a PR today. After that is accepted, I can do the same thing for libpanel and then we should be good.
It might be the case that we can only do this for the 0.5 version though. Not sure if they will publish a new patch version for previous minor versions.

Here is the MR for libadwaita: https://gitlab.gnome.org/World/Rust/libadwaita-rs/-/merge_requests/50

I opened two more PRs to get it working:
https://github.com/gtk-rs/gtk-rs-core/pull/778
https://github.com/gtk-rs/gtk4-rs/pull/1135
Once those are merged, I'll do it for libpanel too and then we should be good to go

I wonder if it makes sense to back port the changes to Relm4 0.4. This would require a back port for gir, gtk-rs-core, gtk4-rs, libadwaita-rs and libpanel-rs. And quite a few new releases as well of course. It is certainly possible, but I wonder if it's worth the effort. What do you think @pentamassiv ?

Agreed, it's unlikely to happen. I think we would also get a problem with semantic versioning. People using the --all-features config would have their builds fails since all of the sudden, the libraries would not be linked.

Is there any progress on this issue? Do you need help with implementing the necessary changes in gir?
It would be great to merge this soon so all gtk-rs crates pick up the changes in time for their next release.

Yes, there is some progress on it. My draft was reviewed today and changes were suggested. It is not ready to be merged yet, but I am positive it can cross the finishing line soon
https://github.com/gtk-rs/gir/pull/1382

Awesome :+1:

Gir now automatically activates the dox feature in sys crates for the dependencies where it is available. gtk-rs-core, gtk3 and gtk4 were also fixed. Libadwaita was fixed a few days ago. The only remaining upstream crate that is missing seems to be libpanel.
I create an issue for it: https://gitlab.gnome.org/World/Rust/libpanel-rs/-/issues/3
Next step I guess would be to fix it for relm4 0.5.

Apparently libpanel will be fixed in the 1.0.0 release.

Yes I think it's already on crates.io, however due to an oversight while re-enabling libpanel, 0.5.0-beta.4 still failed on docs.rs. So I'd like to release beta.5 or even rc1 soon.

Btw. builds on docs.rs look great, so we can now move on with the remaining steps to complete the transition :)

Okay, great. I will have a look at it the next days :)

I read through the issue again and I there seems to be very little left to do. Here is what I would suggest:

[ ] Change the documentation field in the Cargo.toml files to the docs.rs link (https://github.com/Relm4/Relm4/pull/383)
[ ] Change the link on the website to point to docs.rs too but keep the old documentation at https://relm4.org/docs/stable/relm4/ (https://github.com/Relm4/website/pull/5)
[ ] Wait two months or so to give people time to move the 0.5 release
[ ] Remove the old documentation

@AaronErhardt , I remember you changed your mind about keeping the "next" docs but I think your wrote that is some other thread that I can't find anymore. Do you want to keep the next docs or get rid of them?

As soon as we release 0.5 as stable we should discontinue the docs and redirect to docs.rs. But we might consider reviving the custom docs builds for "nightly" docs to keep the main branch documented between releases but everything else should be on docs.rs.

I think we're mostly done with this, right? I think we could even disable the Relm4/docs repo since the 0.4 docs are still available.


does the gem support v2 of the Javascript library?

Not harping. Just curious as I think this is pretty new. https://www.filepicker.com/documentation/
Any plans on supporting this or is there a way I can update it to support v2?
thx

looks like it does


how to include our own model in the model list

Hello, Can someone share the process/steps to include our own like yolov3, yolov5, or faster rcnn model into the Model list for automatic/ semi automatic annotation. I wanna add my own model which i have trained on my own dataset.

@Ironman1508 , we are working on the tutorial. For now you have to look at examples inside the repository:  https://github.com/openvinotoolkit/cvat/tree/develop/serverless

@Ironman1508 , we are working on the tutorial. For now you have to look at examples inside the repository: https://github.com/openvinotoolkit/cvat/tree/develop/serverless

Hi @nmanovic, I did replace the files needed for "yolo-v3 tf" with my custom model (IR files) and have no change to the code except for the number of classes is now only 1 for my custom class.
My custom yolov3 tf model  built from darknet and convert to Openvino (IR) but the CVAT default yolo-v3 tf seems to built from Keras. Could this be the reason ?

Is it added in the tutorial ? I haven't found it anywhere


ReactXP & Redux

This PR attempts to do the following:

[x] Make the Hello World demo app use ReactXP components so it can work on both Web and Native
[x] Make all necessary changes to the code base to make it universal
[x] Add Redux!
[ ] Document mechanism to customize redux

@umairfarooq44 can you review the failing tests?

There will be no further development on this PR. We'll just focus on documenting changes and fixing tests. @umairfarooq44 @haris-ramzan


AttributeError: AWS::EC2::NatGateway object does not support attribute Tags

Im attempting to create a nat gateway, the code works if I remove the Tags portion.  When adding the tags portion like the following, It throws an error.
            t.add_resource(
                ec2.NatGateway(
                    gateway_name,
                    AllocationId=GetAtt(eip_name, 'AllocationId'),
                    SubnetId=Ref(subnet_name),
                    Tags=Tags(
                        Customer=variables["Customer"],
                        Environment=variables["Environment"],
                        Name=Join("-", ["ngw", variables["Customer"], gateway_name, variables["Environment"]]),
                    ),
                )
            )

Traceback (most recent call last):
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/bin/stacker", line 9, in
args.run(args)
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/commands/stacker/diff.py", line 32, in run
action.execute()
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/actions/base.py", line 127, in execute
self.run(*args, **kwargs)
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/actions/diff.py", line 249, in run
plan.execute()
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/plan.py", line 267, in execute
if not self._single_run():
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/plan.py", line 227, in _single_run
status = step.run()
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/plan.py", line 74, in run
return self._run_func(self.stack, status=self.status)
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/actions/diff.py", line 214, in _diff_stack
new_template = stack.blueprint.rendered
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/blueprints/base.py", line 485, in rendered
self._version, self._rendered = self.render_template()
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/stacker/blueprints/base.py", line 459, in render_template
self.create_template()
File "./blueprints/vpc.py", line 386, in create_template
self.create_network()
File "./blueprints/vpc.py", line 220, in create_network
self.create_nat_instance(i, subnet_name)
File "./blueprints/vpc.py", line 318, in create_nat_instance
Name=Join("-", ["ngw", variables["Customer"], gateway_name, variables["Environment"]]),
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/troposphere/init.py", line 123, in init
self.setattr(k, v)
File "/home/justin/Documents/cloudformation/AWS-CloudFormation/projects/stacker/local/lib/python2.7/site-packages/troposphere/init.py", line 211, in setattr
(type_name, name))
AttributeError: AWS::EC2::NatGateway object does not support attribute Tags

The cloudformation documentation makes it appear that this should work.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-natgateway.html
{
  "Type" : "AWS::EC2::NatGateway",
  "Properties" : {
    "AllocationId" : String,
    "SubnetId" : String,
    "Tags" : [ Resource Tag, ... ]
  }
}

That was fixed in #835 and isn't yet released.  It was released in the CF spec late last week: https://github.com/cloudtools/troposphere/issues/826
You can always point at the github version/sha to get that feature if you need it before the release is done (probably in the next week or so.)


travis.yml: update xcode to 9.4

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Some weird Travis RVM stuff here.

Ok, if that's the only option begrudging (to Travis not you) 👍. Can you update the homebrew-test-bot repo similarly? Thanks!

@commitay Looks like this broke code coverage uploading. Mind either taking a look or reverting? Thanks 🙇

https://github.com/Homebrew/homebrew-test-bot/pull/167


Ignore replaced resources when creating moved blocks

We found another issue when using tfautomv.
The following shows automatically created moved blocks for 2 replaced "aws_route" resources.
Which were cross-moved one to the other.
...
┌─ Summary
│ tfautomv made 177 comparisons and found 16 moves
│
│ 16 moves within current directory
│ ├─
│ │ from aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"]
│ │ to   aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"]
│ ├─
│ │ from aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"]
│ │ to   aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"]
│ ├─
...

Resulting in this error:
...
┌─ Error
│ failed to get plan for workdir ".": failed to compute Terraform plan: exit status 1
│
│ Error: Moved object still exists
│
│   on moves.tf line 1:
│    1: moved {
│
│ This statement declares a move from
│ aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"], but
│ that resource instance is still declared at tgw-attachment.tf:123,14.
│
│ Change your configuration so that this instance will be declared as
│ aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"] instead.
│
│ Error: Moved object still exists
│
│   on moves.tf line 5:
│    5: moved {
│
│ This statement declares a move from
│ aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"], but
│ that resource instance is still declared at tgw-attachment.tf:123,14.
│
│ Change your configuration so that this instance will be declared as
│ aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"]
│ instead.
│
└─
...

The following is an original terraform plan output log when NOT using tfautomv which clearly proves that
terraform already realized that the resource address has not changed.
We believe that tfautomv should never act on replaced resources.
  # aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"] must be replaced
-/+ resource "aws_route" "dynamic" {
      ~ id                     = "r-rtb-06b06996b02bf5fd11080289494" -> (known after apply)
      + instance_id            = (known after apply)
      + instance_owner_id      = (known after apply)
      + network_interface_id   = (known after apply)
      ~ origin                 = "CreateRoute" -> (known after apply)
      ~ route_table_id         = "rtb-06b06996b02bf5fd1" -> (known after apply) # forces replacement
      ~ state                  = "active" -> (known after apply)
        # (2 unchanged attributes hidden)
    }

  # aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"] must be replaced
-/+ resource "aws_route" "dynamic" {
      ~ id                     = "r-rtb-089a8c6633ab16d9a1080289494" -> (known after apply)
      + instance_id            = (known after apply)
      + instance_owner_id      = (known after apply)
      + network_interface_id   = (known after apply)
      ~ origin                 = "CreateRoute" -> (known after apply)
      ~ route_table_id         = "rtb-089a8c6633ab16d9a" -> (known after apply) # forces replacement
      ~ state                  = "active" -> (known after apply)
        # (2 unchanged attributes hidden)
    }

In pkg/engine/plan.go in the SummarizeJSONPlan function we wanted to identify the involved change actions.
The "replace" results from the following delete and create actions in combination, which we simply printed out.
fmt.Printf("Change Action: %s for resource address: %s\n", rc.Change.Actions, rc.Address)

Because tfautomv acts on each delete and create individually it tries to find an unnecessary "move partner" resource
and only the other replaced one is available.
...
Change Action: [no-op] for resource address: aws_iam_policy.vpc_flow_log_cloudwatch[0]
Change Action: [no-op] for resource address: aws_iam_role.vpc_flow_log_cloudwatch[0]
Change Action: [no-op] for resource address: aws_iam_role_policy_attachment.vpc_flow_log_cloudwatch[0]
Change Action: [delete create] for resource address: aws_route.dynamic["vpc-shared-services-tgw-next-prod_intra_<IP_ADDRESS>/0"]
Change Action: [delete create] for resource address: aws_route.dynamic["vpc-shared-services-tgw-next-prod_web_<IP_ADDRESS>/0"]
Change Action: [no-op] for resource address: aws_route53_resolver_query_log_config.this[0]
Change Action: [no-op] for resource address: aws_route53_resolver_query_log_config_association.this[0]
Change Action: [no-op] for resource address: aws_route53_resolver_rule.system
...

Hi Arthur,
first, sorry for the late reply (we were very busy with a big (state) migration - very successful thanks to tfautomv 😃), and thanks a lot for the detailed answer.
After we looked at your examples above, we believe that there are cases where the generation of moved blocks for replace actions is meaningful. But since tfautomv is currently not able to reliably create these moved blocks in the correct order, we believe that the default should be to not act on terraform replace action.
Instead, we propose to add a parameter/flag e.g. --force-replace to allow generation of moved blocks as it is currently implemented in latest version of tfautomv, but without this parameter/flag no moved blocks should be created for replace actions.
What do you think about this proposal?


Bug 1837043: Mount the cluster's certificate authority bundle in the auth-proxy sidecar container.

This CA bundle already gets mounted in the reporting-operator container when the cluster-wide proxy is enabled, but not in the sidecar container.

/lgtm

Want to reproduce the user's cluster/MeteringConfig setup before merging.
/hold

/hold cancel


Add rustsec workflow

At the moment, there are a few crates in Cargo.lock that have RustSec advisories, so I thought that it would be a good idea to check for advisories automatically. This PR adds a workflow that checks for relevant RustSec advisories and automatically opens issues for them.

Why not


Unable to checkout '19fb89416f3fdc2d6668f3738f444885575285bc' in submodule path 'third_party/protobuf'

What version of gRPC and what language are you using?
1.36.4
What operating system (Linux, Windows,...) and version?
CentOS 8.0
What runtime / compiler are you using (e.g. python version or version of gcc)
devtoolset-7
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
git clone -b v1.30.0 https://github.com/grpc/grpc
cd grpc
git submodule update --init
What did you expect to see?
No errors
What did you see instead?
fatal: reference is not a tree: 19fb89416f3fdc2d6668f3738f444885575285bc
Cloning into 'third_party/protoc-gen-validate'...
remote: Enumerating objects: 9461, done.
remote: Counting objects: 100% (241/241), done.
remote: Compressing objects: 100% (171/171), done.
remote: Total 9461 (delta 92), reused 170 (delta 58), pack-reused 9220
Receiving objects: 100% (9461/9461), 13.96 MiB | 14.62 MiB/s, done.
Resolving deltas: 100% (4479/4479), done.
Submodule path 'third_party/protoc-gen-validate': checked out '872b28c457822ed9c2a5405da3c33f386ac0e86f'
Cloning into 'third_party/re2'...
remote: Enumerating objects: 6471, done.
remote: Counting objects: 100% (92/92), done.
remote: Compressing objects: 100% (71/71), done.
remote: Total 6471 (delta 47), reused 50 (delta 21), pack-reused 6379
Receiving objects: 100% (6471/6471), 3.11 MiB | 0 bytes/s, done.
Resolving deltas: 100% (4942/4942), done.
Submodule path 'third_party/re2': checked out 'aecba11114cf1fac5497aeb844b6966106de3eb6'
Cloning into 'third_party/udpa'...
remote: Enumerating objects: 406, done.
remote: Counting objects: 100% (76/76), done.
remote: Compressing objects: 100% (51/51), done.
remote: Total 406 (delta 32), reused 41 (delta 18), pack-reused 330
Receiving objects: 100% (406/406), 124.96 KiB | 0 bytes/s, done.
Resolving deltas: 100% (152/152), done.
Submodule path 'third_party/udpa': checked out 'cc1b757b3eddccaaaf0743cbb107742bb7e3ee4f'
Cloning into 'third_party/zlib'...
remote: Enumerating objects: 5150, done.
remote: Total 5150 (delta 0), reused 0 (delta 0), pack-reused 5150
Receiving objects: 100% (5150/5150), 3.66 MiB | 0 bytes/s, done.
Resolving deltas: 100% (3612/3612), done.
Submodule path 'third_party/zlib': checked out 'cacf7f1d4e3d44d871b605da3b647f07d718623f'
Unable to checkout '19fb89416f3fdc2d6668f3738f444885575285bc' in submodule path 'third_party/protobuf'
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?

1.36.3 suffers from the same issue. BTW.

This issue seems to have appeared sometime yesterday. I was able to clone and fetch submodules for these releases 2 days ago.

I still get the issue on a clean git clone.
If I click on the commit you list above, I see warning at the top of the page: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository."

That v1.30.0 in the reproduction steps was a typo. Should have been 1.36.4. V1.30.0 seems fine.

It was a typo in the reproduction step. Should be 1.36.4

That warning is now gone for that commit, and everything is working again. If it is something you did, thanks! If not, well thanks to whoever fixed things on the protobuf repo side.
I guess  the issue can be closed.

Resolved


Add nyc and coveralls.

Fixes #127
Currently I've only included the lib files.

So, apparently this requires Node.js >= 6 too. We should merge #125 first.

Thanks for your efforts. I really don't want to spend any time on this project these days; please ask other collaborators for reviews. I've added Nick recently...
I'd also be happy to move the project to another accounr or organization.

No problem, I'll do what I think it's best then :)
Maybe we could move this repo under the validator org, @sideshowbarker ?

Maybe we could move this repo under the validator org, @sideshowbarker ?

Sure, would be very happy to have it there

@jzaefferer: please get in touch with @sideshowbarker to make the move :)
I can talk with Michael on IRC if any issues arise.

@sideshowbarker looks like you'd have to give me (temporary) access to create repositories on the validator organization. That seems to be the only option here: https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/
In the dialog itself it says that it may take a while for the new owner to approve the transfer, but when I try it anyway, I get this error: "You don’t have the permission to create repositories on validator"

Shouldn't you use the Settings -> Transfer repo option?

That's what I tried. Its called 'Transfer ownership' though

Ah, OK. Then @sideshowbarker needs to enable the option to allow creation of repositories in the validator org.

@sideshowbarker looks like you'd have to give me (temporary) access to create repositories on the validator organization

OK, you should have an invite waiting

@sideshowbarker needs to enable the option to allow creation of repositories in the validator org

Yup, just now flipped that on

Done! For the remaining tasks I've filed #131.


tag v1.5.2

Please tag commit 9aeb3cf with v1.5.2. It simplify the lib usage with go mod and unlocks the latest.

Are you maintaining the library?


Add missing bbox bounds to vizjson used in tests

:point_up:
The cartodb.js dependency in package.json needs to be updated once https://github.com/CartoDB/cartodb.js/pull/1082 is merged

ditto https://github.com/CartoDB/cartodb.js/pull/1082#issuecomment-183240331
@alonsogarciapablo could you take care of merging these ones? :bow:


Bad MAAS behavior when installing hardware

What version (commit) do you encounter this issue on?
RPC11.1 and up
What type of issue is this (bug, feature, documentation, regression)?
Bug
What is the expected behavior?
We have changed the defaults of installing hardware monitoring checks to not installing any because
dell_check and hp_check is set to false.
I would much rather prefer to enable both checks and add a dependency on ansible_system_vendor to install either the dell or hp checks
What is actually happening?
No hardware checks are rolled out
How can we reproduce this issue?
Just install MAAS checks on a bare metal machine
How can we verify your issue is addressed?
It installs dell or HP checks depending on machine vendor
If this is a large issue, what can be done immediately to alleviate the issue while working on a longer-term solution?
High prio
What is your evaluation on the importance of this issue, and why?
All kilo installation have no hardware monitoring
What branches / milestones do you believe this issue should target?
The list below is what is currently supported for backports
Remove branches (lines) you do not wish to target.

[ ] Master
[ ] liberty-12.2
[ ] liberty-12.1
[ ] kilo

could be similar to #931

to summarize the issue, this is a request that we selectively enable either the dell or hp checks based on inspecting system info

@prometheanfire @BjoernT @git-harry IMHO, this is neither a bug nor a prio 1. it is a prio 3 feature enhancement at best. I personally don't believe that it is at all onerous for the deployer to decide whether they have HP hardware or Dell hardware and run the appropriate playbook.

@mancdaz I'm fine with reclassifying it, it's not like we don't have enough meetings where this can be brought up.

@promethanfire yes indeed, though I can't always make the meetings so wanted to note my thoughts here

@mancdaz yes I would agree here. The deployer needs to set a single var to get the appropriate monitoring and it should be simple enough to add this as part of a deployment.

@git-harry  I disagree as usually, especially in the prio. This is came up after changing a default behavior and the playbooks still don't support mixed cluster with dell and hp hardware within the same control plane.

@BjoernT there has never been any automatic hardware detection. In Juno there were separate playbooks for Dell and HP and the deployer was required to run the appropriate one. The rpc-openstack commit 4059eb63 is the first one I can find using dell_check and that was created more than a year ago. The lack of appropriate monitoring is easily addressed by setting the appropriate var.
We have never been made aware of a requirement to support mixed hardware environments. That said you are able to set vars against individual hosts and so that requirement can be met by the current mechanism.

I agree with @BjoernT on this. It seems like something that would be simple to solve for since ansible can detect the hardware and would automate an otherwise manual step that can easily be missed by the deployments team. Open Compute hardware is coming as well so there will be 3 vendors.

+1 Can we get this bumped as a priority?
I don't see why we would want to leave this up to the deployer to set a manual variable when ansible is collecting the system vendor in ansible facts and can use this to deploy the correct hardware checks based on that.
OpenCompute hardware checks are a new feature request (https://github.com/rcbops/u-suk-dev/issues/241), adding even more complexity to this manual setting in a mixed vendor environment.

@shane-c @wesmattson the weekly triage meetings, held on Mondays, are where we approve the issues the engineering team will work on next. If you wish to see this issue addressed sooner, please attend or speak with your representatives, so that it is considered at the next meeting.

You can now use host_check: true to automatically detect whether to install Dell or HP checks going foward in Newton:
https://github.com/rcbops/rpc-openstack/pull/1727


Switch microservices to use AlertManager

Fixes ##10341
Status
Not tested
Description
This PR switches alerts sent from microservices (ms-output, ms-transferor, ms-rulecleaner) from email to AlertManager
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
Requires this PR to be merged as well: #10308
External dependencies / deployment changes
Each MS service configuration in k8s (services_config) needs to have the alertmanager URL added to the config
Also need CMSWEB team to set up proper routes for the alert labels we use

Erik, I think unit tests are failing strangely because we have not yet merged https://github.com/dmwm/WMCore/pull/10308
Merging that one now.

test this please

test this please


Add Force Remove Vesting for Vesting Pallet

This is an issue for @nzt48
There is already a function inside the Vesting Pallet:
	/// Remove a vesting schedule for a given account.
	fn remove_vesting_schedule(who: &T::AccountId, schedule_index: u32) -> DispatchResult {
		let schedules = Self::vesting(who).ok_or(Error::<T>::NotVesting)?;
		let remove_action = VestingAction::Remove { index: schedule_index as usize };

		let (schedules, locked_now) = Self::exec_action(schedules.to_vec(), remove_action)?;

		Self::write_vesting(who, schedules)?;
		Self::write_lock(who, locked_now);
		Ok(())
	}

This should be exposed through a ROOT call, so that developers and governance can have access to such things.
Steps:

[ ] Create a new extrinsic force_remove_vesting_schedule which checks for the root user, and then calls this already implemented function.
[ ] Add a test which verifies the function works.

Test verifies only root can call
Test verifies that vesting schedule is removed (and all the appropriate storage is cleaned up)
Test verifies that trying to remove a schedule when it doesnt exist errors
(probably all can be done in one unit test)

[ ] Add a benchmark which benchmarks this new call.
[ ] Create companion PRs for Polkadot (and Cumulus?)

Would love to work on it shawn

@MrishoLukamba please read the issue, this is assigned to @NTZ48

Thanks @shawntabrizi, I have already started working on it

Hey, is anyone still working on this? Looking forward to this feature being merged!

@Bart200c There is a (somewhat stale) MR for it https://github.com/paritytech/substrate/pull/11910

I will try to address all the open questions and update MR in the next two weeks, thanks for reopening it


Support PKCS#8 private keys.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: myidpt
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [myidpt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: lei-tang, myidpt
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [myidpt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@myidpt: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
440b634daba52c317366e40af86de8a5ad23ce65
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@myidpt: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
440b634daba52c317366e40af86de8a5ad23ce65
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
440b634daba52c317366e40af86de8a5ad23ce65
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@myidpt: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
7a613b50f904ac94f6b7285d6ee48b0e3462eb92
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Fix link in config map

Description
Fixed a link in the pods details view.
Related issue(s)
Fixes #734

/test pre-busola-integration-test-k3s

/test pre-busola-integration-test-k3s


Instructions indicate user should click on "Profile" when they should really click on "Notifications"

This page has an image that indicates user's should click on their Settings button and then their Profile button.  The image following confirms this.  However, The next section assumes that the user has clicked on the Notifications button

From your home page, select  Settings, and then select Profile.

followed by

The notifications you're subscribed to are indicated with the the blue toggle under State.

But clicking on the profile doesn't automatically take the user to their notifications.

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

ID: e3fac729-92a7-0f85-3e28-3a2515b77fca
Version Independent ID: 3038ace1-8e10-9d2f-5e8b-2d883d4dd718
Content: View subscribed notifications - Azure DevOps
Content Source: docs/organizations/notifications/unsubscribe-default-notification.md
Service: azure-devops
Sub-service: azure-devops-notifications
GitHub Login: @chcomley
Microsoft Alias: chcomley

Thanks for your feedback, @MattRuwe, I'll get this article updated! Once live, this issue will automatically close. Thanks again!


camel-json-path extension

I will have a try with this one. If anybody is already working on it, please report.

@aldettinger do you have any update on this extension ?

yep, still on it. I think I will have time for this in the coming days.

Follow up on #610 and #611. Closing this ticket.


API docs: OnInit has inlined code and no longer links to Lifecycle docs

@matan: The APIs to some of the lifecycle hook interfaces were updated in this commit https://github.com/dart-lang/angular/commit/0f1abe5b9e2abfd537956271eead6ee6786c1b3c#diff-d9e2200e3226057f249e806a7e95d1adL76.
Consider OnInit as an example. Under 3.x, the OnInit documentation has an "Example" section with

A(n auto-updatable) code excerpt of (CI tested) code from the AngularDart doc examples
A link to the AngularDart docs "Lifecycle Hooks" page.

In the 4.x OnInit API page, this has been replaced by inlined code block. Admittedly, the old example wasn't as good as it could be, but better ones can be found.
My question is: do we still want to stick to the old format of API docs along the lines of (the current 3.x docs):

Examples
Try the live example from the Some docs page:
<?code-excerpt "docs/lifecycle-hooks/lib/spy_directive.dart (spy-directive)"?>
[auto-updated codeblock]

cc @kwalrath

Oops, this should be @matanlurey, not that other Matan...

Oops indeed. Thanks for noticing!


Support for NCNN\MNN\OpenVINO inference framework.

/kind feature
NCNN and MNN inference framework is widely use in arm, Openvino inference framework is widely use in x86 platform. For speed up inference, we will not use origin inference part of tensorflow or onnx etc.Can we consider the candidate  as additional feature in the next release? 😊
Link on NCNN : https://github.com/Tencent/ncnn
Link on MNN: https://github.com/alibaba/MNN
Link on OpenVINO: https://github.com/opencv/dldt

It seems that support of the inference protocol has improved a lot. Here is an example with Triton client. Maybe something to consider adding to docs?


How to Sanity-Check Slack Plugin Configuration via Jenkins Configuration as Code

I'm having trouble with this configuration, and I'd like to know what the simplest way of knowing whether my CasC is working for this plugin.
unclassified:
  slackNotifier:
    room: "#bot_notifications"
    teamDomain: "${SLACK_TEAM_DOMAIN}"
    tokenCredentialId: slack_integration_token

Is there, say, somewhere I can go in the Jenkins GUI to see that these items have been correctly populated? Otherwise, what's the simplest way?

We wrote a groovy test to confirm our configuration. That way we don't have to look at UI :)

FWIW, I don't need to confirm the configuration on a repeated basis, or in an automated way, I just need to confirm CasC is doing what I expect (once). The thing is, I don't exactly know what the above CasC snippet is supposed to accomplish.

the above piece of YAML will be visible inside Jenkins -> Configure -> Configure System.
Like most plugin have their configuration in Configure system.


PLAT-73229: Update Header to match latest designs

Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[x] This is an API breaking change

Issue Resolved / Feature Added
Header's got some new visuals and features.
Resolution

Updated Header's sizing and positioning
Accounted for light/dark themes, LTR/RTL, noCloseButton/no controls, compact/standard types.
Panels is now smarter about & when to apply the (newly renamed) .hasControls class.
Dropped the casing prop, but did not update the samples or tests, and don't plan to until we get confirmation that it should be gone for good.
Added Measurable HOC and Hook
Panels now supports a <controls> slot, which is intended to have app-level IconButton controls in it which remain stationary and are accessible from any panel.

Additional Considerations
Also updated the font names to match the current version.
Uppercase has been removed from Header, but the tests have not been updated. They should be updated before merging. Left in place until we get verification that the feature is going away. If the feature is retained, this PR will no longer be considered a "breaking" change.

Proposed change looks good! :clap: :clap: @Djspaceg
In addition to what we discussed earlier, I noticed a couple differences from the specs.

The padding-right on the header components <nav> element is leaving some unusable space for long titles

Appears to be missing the 60px margin between the children controls and the text

I think I addressed each of the issues we discussed "in person" and above.
I noticed a rendering issue that occurs during first load of Storybook samples. The header title is "blank" because the padding is set too large, and it pushes the text off screen. It must be measuring something too soon in the render cycle and not updating after render. Every other after initial Storybook load seems fine, just that first one seems messed up. This will require further investigation, however, I did not notice this in sample apps.

Made a small doc commit to fix up Measurable. The storybook rendering issue seems to be caused by measurement occurring before the CSS has been applied. Also seems unique to serve so I think we can defer the fix from this ticket.
I would like to add some unit tests for Measurable and fix up the failed tests before moving forward.
Good work, @Djspaceg!


Cannot export PDF when SwaggerViewer is installed

Hello.
This issue was resolved and I'm not stuck, but I'll share the info for someone else.
When I tried to export the PDF, I got the following error.
[error] [Extension Host] TypeError: Cannot read properties of undefined (reading 'encrypted')
I opened "window" from the list of outputs to see the error message and it seems to conflict with the Swagger Viewer.
at IncomingMessage.protocol (/Users/xxxxxx/.vscode/extensions/arjun.swagger-viewer-3.1.2/node_modules/express/lib/request.js:307:31)
After uninstalling SwaggerViewer, I can export the PDF.

Related: marp-team/marp#391
Seeing these cases, probably express looks like doing a something prank. Marp for VS Code is using express that is bundled to the extension, and usually it should never be affected from express library in other extensions. However, express or its internal may depend on some shared value or method globally by a some reason.

This does not apply to my Issue because I have neither of the conflicting extensions listed here installed.
Stack Trace:
[Extension Host] TypeError: Cannot read properties of undefined (reading 'encrypted')
at IncomingMessage.protocol (c:\Users\thevi.vscode-insiders\extensions\shyykoserhiy.vscode-spotify-3.2.1\node_modules\express\lib\request.js:307:31)
at Function.values ()
at qe.findClassPath (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:1:41653)
at qe.resolvePackage (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:1:41390)
at Function.resolve (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:1:40772)
at Function.resolveDefaultEngine (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:1:40887)
at fromArguments (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:44:64909)
at Jl (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\node_modules@marp-team\marp-cli\lib\marp-cli-48291805.js:44:125649)
at runMarpCli (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\lib\extension.js:3841:919586)
at doExport (c:\Users\thevi.vscode-insiders\extensions\marp-team.marp-vscode-2.4.1\lib\extension.js:3841:922459) (at console. (c:\Program Files\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:138842))
T @ workbench.desktop.main.js:sourcemap:90
$logExtensionHostMessage @ workbench.desktop.main.js:sourcemap:1573
N @ workbench.desktop.main.js:sourcemap:1573
M @ workbench.desktop.main.js:sourcemap:1573
H @ workbench.desktop.main.js:sourcemap:1573
G @ workbench.desktop.main.js:sourcemap:1573
(anonymous) @ workbench.desktop.main.js:sourcemap:1573
invoke @ workbench.desktop.main.js:sourcemap:86
deliver @ workbench.desktop.main.js:sourcemap:86
fire @ workbench.desktop.main.js:sourcemap:86
fire @ workbench.desktop.main.js:sourcemap:553
se.onmessage @ workbench.desktop.main.js:sourcemap:1671
workbench.desktop.main.js:sourcemap:747 Failure to export: [TypeError] Cannot read properties of undefined (reading 'encrypted')

Following the Stack Trace, vscode-spotify seemed to be the issue.
Getting rid of the extension resolved my issue.
Please add the extension to your list of known conflicting extensions.

Added ➕
Thanks for sharing the full stack trace too. I could not have reproduced this problem yet so it is going to be helpful to find a root issue.

The latest release of Marp CLI v2.4.0 has no longer inspected the detail of express module while exporting. I've confirmed #408 actually mitigate errors brought by conflicted extensions.


ReferenceError: self is not defined

Describe the bug
i was trying to use pouchdb in the main thread i.e node . while i import pouchdb it throws error.
if i remove pouchdb, error disapeared and app works fine.

Electron-Vite Version
^1.0.17
Electron Version
^21.3.3
Vite Version
^4.0.4
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Enable externalizePlugin and install punchDB to deps. Do not need to bundle punchDB. PunchDB support browser and nodejs.  More detail: https://evite.netlify.app/guide/dev.html#dependencies-vs-devdependencies

Enable externalizePlugin and install punchDB to deps. Do not need to bundle punchDB. PunchDB support browser and nodejs. More detail: https://evite.netlify.app/guide/dev.html#dependencies-vs-devdependencies

Many many thanks.
after dodifying like below,it works. is it ok?

There is no need to configure the rollup external option, the externalizeplugin will auto to externalize modules which install in deps

Not working, same error persist....

Pouchdb installed as Dev dependency

should be dep not devdep

https://evite.netlify.app/guide/dev.html#dependencies-vs-devdependencies

just only
 main: {
    plugins: [externalizeDepsPlugin()]
 },

should be dep not devdep

pouchdb installed as dep and modified the electron.vite.config.ts file as you describe
but error persist...

only works when i use pouchdb without any plugin i.e pouchdb-find
settings --->

import * as PouchDB from 'pouchdb'
const Pouch = PouchDB.default.defaults({
    prefix: getPath('userData'),
    auto_compaction: true
})

const db = Pouch("kittens")
db.info().then(console.log).catch(console.error)

works fine.
but fails on
  import * as PouchDB from 'pouchdb'
  import pouchdbFind from 'pouchdb-find'
  PouchDB.default.plugin(pouchdbFind)

  const Pouch = PouchDB.default.defaults({
      prefix: getPath('userData'),
      auto_compaction: true
  })

  const db = Pouch("kittens")
  db.info().then(console.log).catch(console.error)

except pouch-find, other 3 plugins works without error

Your pouchDB is latest?
In my project, it works fine.

Your pouchDB is latest?
In my project, it works fine.

aftrer few try, it works.
Many many thanks for your support. <3


Updating Run After not updating tokens

Describe the Bug with repro steps
1.Create a standard logic app
2.Add a request trigger and some actions in it.
3. Add a parallel branch to any of the action in workflow.
4. Select last action of the workflow either Response or any action.
5.  Click on select actions option, add the actions that are in parallel branches.
7. Come back to parameters tab.
8. Try and select the tokens from parallel branches actions.
Expected: Tokens from parallel branches actions also should be visible without saving and refreshing the workflow.
Actual: Tokens from parallel branches actions are visible after saving the workflow and refreshing the workflow.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Edge
Additional context
Version : 2.30710.1.4
AB#24574939

Issue repro in latest request
VS Code extension - vscode-azurelogicapps-2.55.1.vsix
NuGet package: https://artprodeussu2.artifacts.visualstudio.com/A41bf5486-7392-4b7a-a7e3-a735c767e3b3/b32aa71e-8ed2-41b2-9d77-5bc261222004/_apis/artifact/cGlwZWxpbmVhcnRpZmFjdDovL21zYXp1cmUvcHJvamVjdElkL2IzMmFhNzFlLThlZDItNDFiMi05ZDc3LTViYzI2MTIyMjAwNC9idWlsZElkLzc3MzU3NDkxL2FydGlmYWN0TmFtZS9kcm9wX2J1aWxkX0J1aWxkQXJ0aWZhY3RzX1dpbmRvd3M1/content?format=file&subPath=%2FMicrosoft.Azure.Workflows.WebJobs.Extension.1.33.6.nupkg
Extension Bundle (CDN URL): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting
Extension Bundle (Direct Download): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.33.6/Microsoft.Azure.Functions.ExtensionBundle.Workflows.1.33.6_any-any.zip
https://github.com/Azure/LogicAppsUX/assets/113517384/19842428-1bd9-4355-8e37-50fabd227ced

Issue repro in the latest request.
1.VS Code extension - vscode-azurelogicapps-2.55.1.vsix
2. NuGet package: https://artprodeussu2.artifacts.visualstudio.com/A41bf5486-7392-4b7a-a7e3-a735c767e3b3/b32aa71e-8ed2-41b2-9d77-5bc261222004/_apis/artifact/cGlwZWxpbmVhcnRpZmFjdDovL21zYXp1cmUvcHJvamVjdElkL2IzMmFhNzFlLThlZDItNDFiMi05ZDc3LTViYzI2MTIyMjAwNC9idWlsZElkLzc3NTc3MjAwL2FydGlmYWN0TmFtZS9kcm9wX2J1aWxkX0J1aWxkQXJ0aWZhY3RzX1dpbmRvd3M1/content?format=file&subPath=%2FMicrosoft.Azure.Workflows.WebJobs.Extension.1.33.12.nupkg
3. Extension Bundle (CDN URL): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting
4. Extension Bundle (Direct Download): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.33.12/Microsoft.Azure.Functions.ExtensionBundle.Workflows.1.33.12_any-any.zip

Issue not repro in the latest portal request.
Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30731.1.4
https://github.com/Azure/LogicAppsUX/assets/113517384/2d510bdf-6cf3-40c6-8c75-a19b0634de5f


Removing the operator first, should it automatically  remove the driver?

Describe the bug
Not really  a bug, but just wanted to log this  for completeness.. will also open a issue in driver ...
After running for some time, I was planning to remove the driver first, then operator (in a good flow) but accidentally  removed the operator first.
[root@c943f4n01-pvt csi-operator-ansible]# ./operator-helper.sh get_pods
+ oc get pods -n ibm-spectrum-scale-csi-driver
NAME                                               READY   STATUS    RESTARTS   AGE
ibm-spectrum-scale-csi-attacher-0                  1/1     Running   0          42h
ibm-spectrum-scale-csi-operator-6ff9cf6979-k2gpd   2/2     Running   0          42h
ibm-spectrum-scale-csi-provisioner-0               1/1     Running   0          42h
ibm-spectrum-scale-csi-vk7kr                       2/2     Running   0          41m
ibm-spectrum-scale-csi-vpz6v                       2/2     Running   0          41m
ibm-spectrum-scale-csi-ww78g                       2/2     Running   0          41m
+ set +x
[root@c943f4n01-pvt csi-operator-ansible]# ./operator-helper.sh removeOP
Removing secret before namespace
secret "spectrum-scale-gui-secret" deleted
NAME                                               READY   STATUS    RESTARTS   AGE
ibm-spectrum-scale-csi-attacher-0                  1/1     Running   0          42h
ibm-spectrum-scale-csi-operator-6ff9cf6979-k2gpd   2/2     Running   0          42h
ibm-spectrum-scale-csi-provisioner-0               1/1     Running   0          42h
ibm-spectrum-scale-csi-vk7kr                       2/2     Running   0          43m
ibm-spectrum-scale-csi-vpz6v                       2/2     Running   0          43m
ibm-spectrum-scale-csi-ww78g                       2/2     Running   0          43m
deployment.apps "ibm-spectrum-scale-csi-operator" deleted
serviceaccount "ibm-spectrum-scale-csi-operator" deleted
serviceaccount "ibm-spectrum-scale-csi-attacher" deleted
serviceaccount "ibm-spectrum-scale-csi-node" deleted
serviceaccount "ibm-spectrum-scale-csi-provisioner" deleted
role.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-operator" deleted
clusterrole.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-operator" deleted
clusterrole.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-node" deleted
clusterrole.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-attacher" deleted
clusterrole.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-provisioner" deleted
rolebinding.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-operator" deleted
clusterrolebinding.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-operator" deleted
clusterrolebinding.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-node" deleted
clusterrolebinding.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-provisioner" deleted
clusterrolebinding.rbac.authorization.k8s.io "ibm-spectrum-scale-csi-attacher" deleted
customresourcedefinition.apiextensions.k8s.io "csiscaleoperators.scale.ibm.com" deleted

Whoops, noticed this when I only saw operator terminating...
[root@c943f4n01-pvt csi-operator-ansible]# ./operator-helper.sh get_pods
+ oc get pods -n ibm-spectrum-scale-csi-driver
NAME                                               READY   STATUS        RESTARTS   AGE
ibm-spectrum-scale-csi-attacher-0                  1/1     Running       0          42h
ibm-spectrum-scale-csi-operator-6ff9cf6979-k2gpd   2/2     Terminating   0          42h
ibm-spectrum-scale-csi-provisioner-0               1/1     Running       0          42h
ibm-spectrum-scale-csi-vk7kr                       2/2     Running       0          43m
ibm-spectrum-scale-csi-vpz6v                       2/2     Running       0          43m
ibm-spectrum-scale-csi-ww78g                       2/2     Running       0          43m
+ set +x

Then decided oh crap, let me remove the driver...
[root@c943f4n01-pvt csi-operator-ansible]# ./operator-helper.sh removeDR
csiscaleoperator.scale.ibm.com "ibm-spectrum-scale-csi" deleted

Operator then removes fine, but driver is left running...
[root@c943f4n01-pvt csi-operator-ansible]# ./operator-helper.sh get_pods
+ oc get pods -n ibm-spectrum-scale-csi-driver
NAME                                   READY   STATUS    RESTARTS   AGE
ibm-spectrum-scale-csi-attacher-0      1/1     Running   0          42h
ibm-spectrum-scale-csi-provisioner-0   1/1     Running   0          42h
ibm-spectrum-scale-csi-vk7kr           2/2     Running   0          46m
ibm-spectrum-scale-csi-vpz6v           2/2     Running   0          46m
ibm-spectrum-scale-csi-ww78g           2/2     Running   0          46m
+ set +x

More of  a  question about  whether operator terminating should remove the driver as well.
To Reproduce
Not sure....  will see if i can...
Expected behavior
Unknown, looking for some answers with this issue
Environment
--- POD: ibm-spectrum-scale-csi-attacher-0 ---
  ibm-spectrum-scale-csi-attacher:
    Container ID:  cri-o://6798f2aad5ddc2968368080b52e6d173e4ab6155e4a82b9da133d23c3774dee6
    Image:         quay.io/k8scsi/csi-attacher:v1.0.0
    Image ID:      quay.io/k8scsi/csi-attacher@sha256:e57bb6abf0d78e638f70d38bdb07ee30ffe42d423a14fb2f910c11afab3a5e01
--- POD: ibm-spectrum-scale-csi-provisioner-0 ---
  csi-provisioner:
    Container ID:  cri-o://5334023271ac883db03e032ecf46439c9f98c992272a31a41df4c7edd6caef60
    Image:         quay.io/k8scsi/csi-provisioner:v1.0.0
    Image ID:      quay.io/k8scsi/csi-provisioner@sha256:cd0df00950e7b50154e83e29010eb2f2bfe0b661fb7fdd65c6621e8a49cd2bc0
--- POD: ibm-spectrum-scale-csi-vk7kr ---
  driver-registrar:
    Container ID:  cri-o://39e209f1237d2a3f6344905c3eb79b35b7674349d40872d992ca90f8d23770d7
    Image:         quay.io/k8scsi/csi-node-driver-registrar:v1.0.1
    Image ID:      quay.io/k8scsi/csi-node-driver-registrar@sha256:5ad51d40e6de6762ae9bf2acbcf7117d46c87bc50048a337ce5a5cd6697498b4
--
  ibm-spectrum-scale-csi:
    Container ID:  cri-o://5773bf605f616207c5f8e5674d191ffb1b2fa50ced709dc1e2bd3424adab1893
    Image:         quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver:v0.9.1
    Image ID:      quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver@sha256:e5926978bd4f4a553df18fc79ac532037c4e31e3a2cdaa6a5c06014fba02c808
--- POD: ibm-spectrum-scale-csi-vpz6v ---
  driver-registrar:
    Container ID:  cri-o://d71f2b8b96edd5e48cb56ec60843471675ac9efcc7b7615c9fa20baa34810e0e
    Image:         quay.io/k8scsi/csi-node-driver-registrar:v1.0.1
    Image ID:      quay.io/k8scsi/csi-node-driver-registrar@sha256:5ad51d40e6de6762ae9bf2acbcf7117d46c87bc50048a337ce5a5cd6697498b4
--
  ibm-spectrum-scale-csi:
    Container ID:  cri-o://bded886e5b2e3aedc0b008bda5499c6572ee6e51681659c9ceb05d3cd2579432
    Image:         quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver:v0.9.1
    Image ID:      quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver@sha256:e5926978bd4f4a553df18fc79ac532037c4e31e3a2cdaa6a5c06014fba02c808
--- POD: ibm-spectrum-scale-csi-ww78g ---
  driver-registrar:
    Container ID:  cri-o://e59f0ad8029ae46b4023e28e76226446335fefaccfa8a4cbf2b3265a7409f3a3
    Image:         quay.io/k8scsi/csi-node-driver-registrar:v1.0.1
    Image ID:      quay.io/k8scsi/csi-node-driver-registrar@sha256:5ad51d40e6de6762ae9bf2acbcf7117d46c87bc50048a337ce5a5cd6697498b4
--
  ibm-spectrum-scale-csi:
    Container ID:  cri-o://bce2077dbcca30c17c782b1bb991b2bdef1d6cec645dc91c849eb6554008c689
    Image:         quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver:v0.9.1
    Image ID:      quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver@sha256:e5926978bd4f4a553df18fc79ac532037c4e31e3a2cdaa6a5c06014fba02c808

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

This is currently working as designed. Please reopen if disagree


Feature/persistance pub sub

Added data persistance to pub and sub and beacons repositories.

I've merged current develop to the feature branch making changes more visible.

Great job for the persistance !


[WebExt] General API tasks, Fx 73

Trello
https://trello.com/c/hNQnoIAW/114-general-api-enhancements-fx-73
Acceptance criteria

[x] Webextension UUID leak via Fetch requests

@rebloor this one has just had its patch backed out due to problems, so will no longer be landing in Fx73. So no need to worry about this one for now ;-)


Fix for bug #12115

Description
Fix for bug #12115
https://github.com/filamentphp/filament/assets/4639175/d482d4fa-c7a3-4e8f-b7f9-a24498847797
Before proposed fix
https://github.com/filamentphp/filament/assets/4639175/547ce979-892f-4af6-b134-9599f383e44f
Visual changes
Nope
Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

Thanks!


Add FDK.dll to gitignore

必要ないと思うのでgitの管理対象から外しました。

It's normally necessary to run the game, but since it's generated while compiling it shouldn't be an issue for latest commit players


CRTLibraryImportTest

Help find missing exports.

This should wait for https://github.com/dolphinsmalltalk/DolphinVM/pull/67 before it is merged.

@jgfoster, I've committed your change to the DolphinVM repo and pushed a new tag, so version 7.0.11 is ready to consume for this submission once the test is fixed as described above.

Thanks, I'll work on the suggested change...


Payment Initiation model version 3.1.4 missed fields (Refund)

Description
It has been detected that the objects generated from swagger file version 3.1.4 (payment initiation) was wrong and the object Refund doesn't exist defined in the generated model when was generated at 2020-05-19.

The OBIE spec was wrong defined and miss fields, will be necessary generate again the model to fix the missed fields.

swagger file correction
v3.1.4 Payment initiation swagger file
tasks

[x] Generate the model with the correct payment initiation swagger file
[ ] Compare the model generated with the current model on openbanking-uk-datamodel to detect issues or fields missed.
[ ] Overwrite the model on openbanking-uk-datamodel

Command used to generate the model
java -jar ../../swagger-codegen-cli-2.4.17.jar generate \
-i https://raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/v3.1.4/dist/swagger/payment-initiation-swagger.json \
-DuseBeanValidation=true \
-Dmodels \
--model-package uk.org.openbanking.datamodel.payment \
--group-id com.forgerock.openbanking \
--artifact-id openbanking-sdk \
-l spring \
--library spring-boot \
-o generated-spring

Swagger file used

v3.1.4 payment-initiation-swagger.json

Changes in openbanking-uk-datamodel

uk.org.openbanking.datamodel.payment

OBWriteInternationalResponse4Data

Added refund property OBWriteInternationalResponse4DataRefund
OBWriteInternationalResponse4DataRefund: new class
OBWriteInternationalResponse4DataRefundAgent: new class
OBWriteInternationalResponse4DataRefundCreditor: new class

OBWriteInternationalScheduledResponse5Data

OBWriteInternationalRefundResponse1DataRefund changed to OBWriteInternationalResponse4DataRefund

OBWriteInternationalStandingOrderResponse6Data

OBWriteInternationalRefundResponse1DataRefund changed to OBWriteInternationalResponse4DataRefund


Let Gc::cast and Gc::from_ptr work for ?Sized types

ptr::byte_offset requires rust 1.75, so this is a MSRV change.


add @types/minimist so that build step passes

when running the install command in packages/xstate-compiled it fails with:
error TS7016: Could not find a declaration file for module 'minimist'.
adding @types/minimist fixes the problem.

#9

@redappleorigin Looks good, thanks!


Stabilizing: Add retry on docker container removal

Retry one additional time to remove docker if it fails.  Warn if retry required and error if retry fails.
PPG 415 passed.

Rebased and merged as 90846a3.


move lib files into src subfolder

Summary
Test Plan

Please consider the impact of your changes on the other developers.

#37  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Silver-Sword and the rest of your teammates on  Graphite


No code for BCNet on Faster/Mask RCNN

Hi, I realise that BCNet implementation in Mask RCNN is also not given in this repo. Will you be able to provide them for purpose of results reproduction? Thank you!

hi, sorry for the late reply, please refer to the code implementation by other github users here.


Use SGVector instead of raw pointers in dense_dot

This is part of getting rid of raw pointers in Features. I renamed dense_dot to dot, and now it uses SGVector. Currently dense_dot just calls dot so as not to break current algorithms. If this is ok, I will change the rest of the code to use this instead of the one with raw pointers.

This is getting ugly, I will split stuff to other PRs

All uses of this variant of dense_dot is replaced, except for some cases which will be uglier in the gpl code.

Let's rebase (fix the submodule conflict) and then merge ....

One good extension of this topic would be (not in this PR though).
Quite often, we do iterative dot products in loops over all feature vectors. This could be done via a matrix multiplication for dense features. And that would be faster. So I think it would be cool to identify such opportunities and implement and API for that case. In a first step, the API would just call the existing one-by-one dot products, a second step would be to check whether a matrix-multiple batched version is possible (e.g. dense feats, no subsets), and then check whether we get speed improvements

this is ready


Add a "Default Unchecked" Omit Page Numbering Checkbox

This would do what it suggests; it would effectively ignore the page number field entirely:

        $options = request()->get('options');
        $numbering = false;
        if (is_array($options) && in_array('omit-numbering', $options)) {
            $numbering = false;
        } else {
            if (request()->has('numbering') && !is_null(request()->get('numbering'))) {
                $numbering = !!request()->get('numbering');
            }
        }```

This implements it by the way in (`app/Http/Controllers/Controller.php`) on  bf2001988b90bbb4cec40865292bf5d040f7ee5b.

Yes, I know - and the problem there is that there's NOTHING that shows
you can do that.
On 2022-06-29 4:43 pm, Josh Reisner wrote:

you can actually omit page numbering by making the |Start #| field blank
—
Reply to this email directly, view it on GitHub
https://github.com/code4recovery/pdf/issues/26#issuecomment-1170475203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI6YBDLCKA2ROFKOH7LDMLVRSYPVANCNFSM52GBGHZA.
You are receiving this because you authored the thread.Message ID:
@.***>


Validate JoinSplit proofs

Motivation
We need to validate JoinSplit Groth16 proofs from post-Sapling Sprout transactions. (Pre-Sapling use BCTV14 proofs, but since we checkpoint on Canopy, we don't need to validate them.)
Specifications
JoinSplit descriptions are described in https://zips.z.cash/protocol/protocol.pdf#joinsplitdesc
The primary input encoding is not documented yet; see https://github.com/zcash/librustzcash/blob/0ec7f97c976d55e1a194a37b27f247e8887fca1d/zcash_proofs/src/sprout.rs#L152-L166 for the reference implementation.
Designs

Solution

Add support for encoding JoinSplits in order to verify them
Add test to make sure verification works
Rename spend_prepared_verifying_key to joinsplit_prepared_verifying_key which is more appropriate
This does not add batch verification since it will required some changes to zcash_proofs, will be done in https://github.com/ZcashFoundation/zebra/issues/3127
Does not actually make Zebra validate the proofs, that will be done in https://github.com/ZcashFoundation/zebra/issues/1835

Closes https://github.com/ZcashFoundation/zebra/issues/322
Review
@dconnolly and/or @upbqdn can review this.
Reviewer Checklist

[x] Code implements Specs and Designs
[x] Tests for Expected Behaviour
[x] Tests for Errors

Follow Up Work
Actually using this to validate proofs will be done in https://github.com/ZcashFoundation/zebra/issues/1835
Adding support for batch verification is https://github.com/ZcashFoundation/zebra/issues/3127

Some rustdoc improvements and a merge conflict to resolve but functionally ✅

Some rustdoc improvements and a merge conflict to resolve but functionally white_check_mark

:+1: Conflicts solved


change message event to confirm with recent changes

change the event to match the current spec
https://w3c.github.io/ServiceWorker/#extendablemessage-event-data

Looks great! Thanks for the submission!

Shouldn't this be considered as a breaking change since it completely changes how to trigger events?
self.trigger('message', Object.assign(new Event(), { data: 'skipWaiting' }));

No longer works and instead needs to be
self.trigger('message', 'skipWaiting');

This should not affect how the event was triggered. Previously, the second argument for MessageEvent was completely unused, so the first example did not actually do anything previously.

Are you sure?
Previously it was:
constructor(type, args) {
  super()
  Object.assign(this, args);
}

Which would run Object.assign(this, Object.assign(new Event(), { data: 'skipWaiting' }) with my example. And the result should've been that this.data had value skipWaiting?
Anyway, not a big deal. Thanks for a great module to make it easier write tests.

Oh gosh, thank you! This pull request is actually wrong according to: MessageEvent. The init object should contain data not be the data. I'm going to revert.

Reverted and updated to be more explicit according to the spec. Live in 1.10.1


move 3.x MongoDB to 4.x

I have been running Bitfinex backfill for some time. Is it possible or useful to dump zenbot 3.x mongodb and restore it to zenbot 4.x mongodb?

I think we would have to support bitfinex in 4.x first, and even then I'd advise just to run a new backfill instead of going through the problem of migrating..

Obsolete as zenbot 3 data backfiller is offline. No need to migrate.


HDDS-4476. Improve the ZH translation of the HA.md in doc.

What changes were proposed in this pull request?
Fix the parent tag in ZH translation of the HA.md doc.  At the same time, modify the link of interface/_index.md to point to its Chinese translation version
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4476
How was this patch tested?
Run the /hadoop-hdds/docs/dev-support/bin/generate-site.sh and Passed all unit tests.

PR Merged. Thanks @yuyang733 for the contribution.


Class extends value undefined is not a constructor or null

After change 45021, these tests fail in dartdevk:
language_2/regress_22666_test:
Uncaught TypeError: Class extends value undefined is not a constructor or null

language_2/mixin_regress_13688_test:
Uncaught TypeError: Class extends value undefined is not a constructor or null

merging into #32428


Before the animation screen jump

i have noticed that before the animation there is a small drop . is there any solution for this ?

Hey @Denaindra - Assuming you mean iOS? Yes, there is a "feature" on Xamarin.Forms on iOS where the OnAppearing actually renders after the page appears. I have created a PR where a fix for this is implemented.
I wanted to take the time to update the NuGets but currently on macOS.


Strange ModuleLoadException due to a WPF dependency

I have been using the .NET C# kernel in JupyterLab and it has been working quite fantastically. Except when I ran some code that has a dependency on System.Windows.Media.DisableDpiAwarenessAttribute class from assembly WindowsBase, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
Here's the error stack trace:
System.TypeInitializationException: The type initializer for '<Module>' threw an exception.
 ---> <CrtImplementationDetails>.ModuleLoadException: The C++ module failed to load during appdomain initialization.

 ---> System.TypeLoadException: Could not load type 'System.Windows.Media.DisableDpiAwarenessAttribute' from assembly 'WindowsBase, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at CModuleInitialize.IsProcessDpiAware(CModuleInitialize* )
   at CModuleInitialize.{ctor}(CModuleInitialize* , IntPtr cleaningUpFunc)
   at ?A0x52b3a002.InitCmiStartupRunner()
   at ?A0x52b3a002.??__E?A0x52b3a002@unused@@YMXXZ()
   at _initterm_m((fnptr)* pfbegin, (fnptr)* pfend)
   at <CrtImplementationDetails>.LanguageSupport.InitializePerAppDomain(LanguageSupport* )
   at <CrtImplementationDetails>.LanguageSupport._Initialize(LanguageSupport* )
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   --- End of inner exception stack trace ---
   at <CrtImplementationDetails>.ThrowModuleLoadException(String errorMessage, Exception innerException)
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   at .cctor()
   --- End of inner exception stack trace ---
<<<< omitting stack trace of code that depends upon this library >>>>

Note that I have included the assembly using #r ""C:\Windows\Microsoft.NET\assembly\GAC_MSIL\WindowsBase\v4.0_<IP_ADDRESS>__31bf3856ad364e35\WindowsBase.dll" and there was no error while loading the dependency. I have also been able to run code that depends upon other random DLLs, so I don't think DLL loading in general is a problem. Apart from that, I'm not really sure what's going on. Am I loading incorrect DLL? There were multiple WindowsBase.dll, but this seemed to match the version. I did try some other DLLs and it didn't seem to help.
Which version of .NET Interactive are you using?
Version: 1.0.155302+ea10eecdeb2eb5f0ccbac5d7eec8b97a99453388
Build date: 2021-01-19T13:09:34.6320576Z

OS: Windows 10
Browser: Chrome
Frontend: Jupyter Lab

Interestingly, this error does not happen with C# interactive console in Visual Studio.

@thakkarparth007 , could you provide the code that demonstrates this crash, that would help with diagnosing the broken dependency.

@KevinRansom , pinged you internally on Teams.

@thakkarparth007 ,
c# interactive doesn't automagically probe for missing 'dlls.  So your list of depencies may not be complete.  It also doesn't know how to automagically resolve native dependencies.  The best solution is to create nuget packages containing the dependencies you are trying to load and reference them in notebooks using #r "nuget:PackageName, version#".


Plugin for FresshRSS using Google Reeders API: How to create or create a officially one

Hello I read the documentation. It would be nice to have a plugin for FreshRSS to get all RSS feed from the self hosted instance and also automatically update the reading status on FreshRSS. A lot of RSS Readers implement it using the Google Reeder api. For example Reeder5, which i want to replace with your great App Tapestry.
But it seems currently the API does not provide a way to do so, or i oversee something. How i could authenticate using an username and API Password instead of Oauth. Also is it possbile to mark different Categories with different colors and have a different Title instead of just "Blog". How to achieve that?
Or how i would get all unread, not yet fetched entries to display in tapestry instead of a fixed amount of entries.
I think a lot of user would benefit from that so they could continue to use FreshRSS or similar Tool and not need to enter all RSS Feeds manually and have a cross platform solution.
Here are some links maybe helping implemneting it:

FreshRSS Github Repo: https://github.com/FreshRSS/FreshRSS
Documentation of FreshRSS about the Google Reeders API, with links to more detailed manuals: https://freshrss.github.io/FreshRSS/en/developers/06_GoogleReader_API.html

It sounds like you should use the extraHeaders parameter in sendRequest(). You can collect the username and password using variables in ui-config.json. Then create a dictionary value for "Authorization" that matches the service's needs.
https://github.com/TheIconfactory/Tapestry/blob/main/Documentation/API.md#sendrequesturl-method-parameters-extraheaders--promise
A far as coloring items - the user will eventually have control over coloring an individual feed (the connector will suggest a default). If you want something instead of "Blog", change the service_name in plugin-config.json.

In freshrss the Feeds Are seperated in different Categories. So setting service_name won't be suitable. Due I want for each category another name. Also how I could create a function to Mark a Feed entry as Read in freshrss if I scroll over the entry or click on it. On 16 Aug 2024, at 19:12, Craig Hockenberry @.***> wrote:
It sounds like you should use the extraHeaders parameter in sendRequest(). You can collect the username and password using variables in ui-config.json. Then create a dictionary value for "Authorization" that matches the service's needs.
https://github.com/TheIconfactory/Tapestry/blob/main/Documentation/API.md#sendrequesturl-method-parameters-extraheaders--promise
A far as coloring items - the user will eventually have control over coloring an individual feed (the connector will suggest a default). If you want something instead of "Blog", change the service_name in plugin-config.json.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Fix for rendering problem in data-factory.md

Ah, you should probably merge the changes into main in your repo, not gh-pages


Fix duplicate folder name when use downloadFiles options

fixed #282

Using the following command to test
crank --config .\samples\local\local.benchmarks.yml --scenario hello --profile local --application.options.downloadFiles App_Data/logs/*.*

Before modification

After modification

Would you mind trying to add a unit test? I added one recently related to downloading files, so you should be able to copy it and update the conditions.


chore: clean and optimise ui

Also, the failing ci seems like is cause by the breaking change in the Gotrue-dart where GotrueError was renamed to GotrueException.


Support "$ref": "{{model:MyModel}}"

Dynamically inserts references to the model.

Codecov Report

Merging #58 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #58   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      5    +1
  Lines         247    276   +29
  Branches       31     37    +6
=====================================
+ Hits          247    276   +29

Impacted Files
Coverage Δ

src/models.spec.js
100% <100%> (ø)

src/models.js
100% <100%> (ø)
: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 b0f280d...ee375db. Read the comment docs.

Awesome!

Any idea when this might be released?

@ShaunEgan I wanted to do something for this on the weekend. There is another ticket I want to include into 1.0. But if I couldn't get to that point I would release it already.

Great, thanks

So this doesn't work when doing validation using ajv - do you have a suggested solution?

I don't have experience with ajv, but I looked at its docs quickly. It does support $ref, which is part of the standard, but I can see why it would get confused by the unprocessed references.
I can't really think of a great solution. We could change this feature so that instead of $ref we use a different keyword ('awsref'?), and then at least things which are expecting a real reference won't get confused. But I don't think that really solves your problem, which is that you want to do validation using composition of the unprocessed model definitions. I think you're going to have to pick one way of doing it or the other. I am holding out hope that AWS adds support for enabling validation via CloudFormation soon.

Could you please publish a new version on npm?

Yes, will do this today

@vilius-rugaitis Released with version 1.0 :)

Somehow, I cannot update the package over npm. Or does npm have some kind of update review processes?

@vilius-rugaitis Oh, my bad. thought this package had an automated publishing process in travis ci.
Have published it manually now :)


Help with packit run: /usr/bin/make: No such file or directory

Hi all, I hope this is the right place to report this, if not, please let me know the right place.
We are having an issue on a PR that might be related to packit.
https://github.com/avocado-framework/avocado/pull/4604
Can some good soul help us here?

@beraldoleal thanks for reporting this, but this is not a packit issue AFAICT.
The PR was sent to Avocado's LTS, which is still using make for the man page generation, but make is not on Fedora 34's build root.  Something like this should be backported to LTS too.
Packit folks, I think it's safe to close this issue.
Thanks!

Thank you @clebergnu for checking. Closing then.


Has anyone been able to fix the callback URI issue?

We updated the OHIF viewer version to latest and this is fixed

You will need to deploy the latest version from this repi


Handler for Spring 5.1 Servlet Exceptions

Closes #29
Signed-off-by: Ali Dehghani<EMAIL_ADDRESS>

Codecov Report

Merging #31 into master will decrease coverage by 0.07%.
The diff coverage is 93.33%.

@@             Coverage Diff              @@
##             master      #31      +/-   ##
============================================
- Coverage     94.91%   94.83%   -0.08%
- Complexity      147      156       +9
============================================
  Files            14       15       +1
  Lines           295      310      +15
  Branches         32       35       +3
============================================
+ Hits            280      294      +14
  Misses            7        7
- Partials          8        9       +1

Impacted Files
Coverage Δ
Complexity Δ

.../me/alidg/errors/conf/ErrorsAutoConfiguration.java
89.47% <100%> (+0.58%)
9 <1> (+1)
:arrow_up:

...dlers/MissingRequestParametersWebErrorHandler.java
92.85% <92.85%> (ø)
8 <8> (?)

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 c5c1f54...f6f6cec. Read the comment docs.