Create a packer configuration to build an Ubuntu Server AMI

Create a packer configuration to build an Ubuntu Server AMI
🗣 Description
Create a packer configuration to build out a new Ubuntu Server AMI to use in the COOL and CEIL
💭 Motivation and context
Currently, the CEIL is using Red Hat as the OS platform for its User Services. This OS is reaching EOL and we need to rebuild these servers using IaC. Ubuntu is preferred, as it has a larger default package repo and more up-to-date packages.
🧪 Testing
Created a packer role based off the existing Debian Packer role. Modified it to pull and set up the latest Ubuntu server image (22.04 Jammy).
Built the AMI and deployed in COOL Staging to test functionality.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

@bra1ncramp or @jsf9k Do you know what's going on with this error?

@bra1ncramp or @jsf9k Do you know what's going on with this error?

It looks like a temporary lack of sanity.  I kicked off a re-run.

@bra1ncramp or @jsf9k Do you know what's going on with this error?

It looks like a temporary lack of sanity. I kicked off a re-run.

Success!

@bra1ncramp or @jsf9k Do you know what's going on with this error?

It looks like a temporary lack of sanity. I kicked off a re-run.

It sometimes does that. It's not nearly as bad as the Aptitude error which often persists. But I do have that from time to time - so far it's resolved after a single re-run

@mcdonnnj please re-review and hopefully approve as soon as you can so that we can get the PR out the door.


Support Library 23.2.0, "No resource found that matches the given name"

There is an issue with <IP_ADDRESS> with Support Library 23.2.0. Also I can't get compile <IP_ADDRESS> with 23.2.0 on my side, following error occured:
"Error:(3, 5) No resource found that matches the given name (at 'android:actionModeCloseDrawable' with value '@drawable/abc_ic_ab_back_mtrl_am_alpha')."

Same here

Already reported, guys: https://github.com/jitpack/jitpack.io/issues/444

How much can this take ?

Use Support Library 23.1.1 and <IP_ADDRESS> until Jitpack update its support library.

Affected by the same issue. Subscribing.

Already fixed: https://github.com/jitpack/jitpack.io/issues/444#issuecomment-188675840

Closed.

@AzureusSme :+1:

this seems to be back on v24.2.1

@carloxavier yeah, back again!

Same problem here c:

This issue here is specifically for Support 23.2.0, which is not supported.


Switch to safe_yaml fork

Partially resolves #272
Full fix: wait for https://github.com/lostisland/faraday_middleware/pull/157 to be merged

Coverage remained the same at 98.006% when pulling 067ef3055bf9658f458e3dcd6ac1bf155c87b03e on switch_to_safeyaml_faraday_middleware into d214ec08cd4b4b90ab1a913bb209cfbde97a9914 on master.

Coverage remained the same at 98.006% when pulling 067ef3055bf9658f458e3dcd6ac1bf155c87b03e on switch_to_safeyaml_faraday_middleware into d214ec08cd4b4b90ab1a913bb209cfbde97a9914 on master.


docs: add some badges in README.md

Add some badges in README.md to improve project maintainability.
Signed-off-by: Qinqi Qu<EMAIL_ADDRESS>

Codecov Report
Base: 30.50% // Head: 30.50% // No change to project coverage :thumbsup:

Coverage data is based on head (d10f016) compared to base (7e6afdb).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #318   +/-   ##
=======================================
  Coverage   30.50%   30.50%
=======================================
  Files          37       37
  Lines        3800     3800
=======================================
  Hits         1159     1159
  Misses       2520     2520
  Partials      121      121

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[IDEA] Context Menu

Hello guys.
What do you think about the idea on the context menu of the operation for the rows (delete, edit, move up/down, etc.). It can be a substitute for select/multiselect actions (better UI impletmetace).
A similar solution uses tables in Redmine system and the solution I like.

What do you think about it @paveljanda ?

I don't like context menus on websites. Feels unnatural and also is not that great for mobiles.

I also don't think is netural. Otherwise all other UI components would use it.


Allow empty scope authorization

Registries may allow using token authorization without explicitly setting the scope. This may cover use cases where no scope is required for an endpoint or the registry is only covering authentication using the token. This aligns with the oauth2 spec which specifies the scope as optional.

Any known registry service that had hit the issue?

LGTM

@AkihiroSuda see the conversation that back-referenced this. I don't think any registry is legitimately using this feature, however, we don't have a good reason to deviate from the oauth spec on this. This is more to help ensure that if a registry has a bug around setting the scope, the bug is manifesting itself during authorizing a token, rather than validating the WWW-Authenticate header.

Codecov Report

Merging #3889 into master will decrease coverage by 4.49%.
The diff coverage is 71.42%.

@@            Coverage Diff            @@
##           master    #3889     +/-   ##
=========================================
- Coverage   42.32%   37.82%   -4.5%
=========================================
  Files         130       88     -42
  Lines       14678    12313   -2365
=========================================
- Hits         6212     4658   -1554
+ Misses       7540     7004    -536
+ Partials      926      651    -275

Flag
Coverage Δ

#linux
?

#windows
37.82% <71.42%> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

remotes/docker/authorizer.go
71.67% <71.42%> (+1.15%)
:arrow_up:

archive/tar_opts.go
11.76% <0%> (-47.06%)
:arrow_down:

cio/io.go
1.4% <0%> (-45.08%)
:arrow_down:

snapshots/native/native.go
1.73% <0%> (-40.7%)
:arrow_down:

archive/tar.go
18.95% <0%> (-29.24%)
:arrow_down:

metadata/snapshot.go
34.25% <0%> (-14.23%)
:arrow_down:

metadata/adaptors.go
39.04% <0%> (-9.53%)
:arrow_down:

oci/spec_opts.go
32.91% <0%> (-2.28%)
:arrow_down:

gc/scheduler/scheduler.go
66.34% <0%> (-0.97%)
:arrow_down:

content/local/writer.go
57.69% <0%> (-0.97%)
:arrow_down:

... and 42 more

Continue to review full report at Codecov.

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

Will this be on a milestone before 1.4, like a patch release for 1.3.3? just wondering as I can only see a old milestone 1.3.1 and the next release 1.4 which doesn't contain this PR
btw I'm asking as suggested here https://github.com/containerd/containerd/blob/master/RELEASES.md#next-release 🤓


fix(reactivity): readonly object should not track on 'has' and 'ownKeys'

Good catch! Although in this case, we can simply remove the has and ownKeys traps for readonly proxies (see 691a4b95)


Settings-Archive-Admin-App Sprint 1

Description:

Build the Screen to match the Figma design.
Integrate Screen with the Backend

hello @Honeyloveet , I'll like to work on this. kindly assign it to me. thank you


bitbucket: Use display_name/nickname when username is not available

I trusted our unit tests on this, which are pretty extensive, and the changes here are pretty straightforward.

My main goal here is to stop the Sentry errors for now, without changing too many things.  #16377 suggests a more aggressive removal of username.

Does this method (and its callsites) need to get swapped out as well?
def get_user_display_name(payload: Dict[str, Any]) -> str:
    return payload['actor']['display_name']

So d0066c37ff7dc5c69028fdf85d6ca273b2c01a5a was the original commit, and we had both functions:
+def get_user_display_name(payload):
+    # type: (Dict[str, Any]) -> str
+    return payload['actor']['display_name']
+
+def get_user_username(payload):
+    # type: (Dict[str, Any]) -> str
+    return payload['actor']['username']

Ah, and here's why:
User {display_name}(login: {username})

Ugh, I'll discuss on chat.  The commit daea9a543b2842c547ca2fb537a51052a46c3bdd from Eeshan probably should have chose nickname before display_name, although I'm not sure.
Given the GDPR changes, we might need to account for cases where display_name is the only field.

Hold off on merging this.  I have some ideas on how to proceed here, but I want to think it through a bit.

Why did we originally show both display_name and username for folks forking a repository, but then we only showed username for folks changing/updating repos or changing commits?  That seemed arbitrary.
When we made our GDPR patches, which seems a bit haphazard, why did we put display_name ahead of nickname in get_user_username, when we already had a get_user_display_name function?

I think the solution here is to do this:

always show the user name the same way (don't make exceptions for the "fork" case)
make the helper flexible for various combos of username, nickname, and display_name

Merged, thanks @showell!


Contributing?

Hi @whoisryosuke!
I really love what you have put together here so far.
Yesterday I was working on packaging up a theme for my organization to use with mdx-deck and I was surprisingly frustrated trying to get some of the theming to work. Many changes required killing build processes and starting them over again. I think this has to do with the caching in Gatsby... which comes with its own issues (all of the install warnings with dependencies, etc). There are a lot of things that feel like they should get updated with mdx-deck to make theming and configuration easier. I got to thinking that it would potentially be easier to build a better solution with Next instead. Which is how I found your project this morning. 👍🏽
Are you interested in having contributions to this project? If so, we should add a CONTRIBUTING.md to the project and define some vision and direction. If you prefer this to be a personal project only, that is okay too.
I did make a fork and tested out a few things in terms of starting to centralize configuration. I think it would be great if the project was self contained and you could just point it at an MDX file and have a slide spin up. That way this could eventually be published as a package. If all it needed was a deck.config.js, deck.mdx, and possibly a deckTheme.js, that would be awesome.
Let me know what you think. I'd be happy to share some ideas in terms of abstracting out some of the implementation details into config the way you already started.

Hey @brianespinosa 👋🏼
Thank you for the kind words and interest! 🔥🤘🏼
Always down for contributions 👍🏼 I can add a CONTRIBUTING.MD to help start this process.
Not sure if there's a particular vision for the project, I have a roadmap I initially outlined for features, but it's definitely not concrete. You can see it here under v2.. It's basically smaller features to reach parity with mdx-deck and a couple quality of life improvements.
I like the idea of CLI-izing the project to make it easier to consume as an end user, really helps encapsulate all the Next logic. And like you said, would allow for more simpler config based setup. This seems fairly achievable, especially looking at the mdx-deck CLI.
Feel free to throw in a PR if you have any suggestions, always open to feedback and refactors. As long as the app works and gets better for everyone, it's all good 😁 If you'd prefer to put in a more conceptual PR, that's also cool too!
I'm personally paused on this project for a little bit, my focus is on a couple other things right now, but I'll be circling back to this soon when I start recording some talks again 🎙✅
If you have any questions about anything feel free to hit me up or create a new issue 👍🏼

@brianespinosa Created a branch for the CLI. Feel free to test it out 👍
Should be able to clone the branch, npm link it to a project, and run the CLI (using the new README).
I'm going to stress test it locally then consider a v1 release. Gotta pick up a user's deck.config.js to replace the slide layout data and whatnot, but the core functionality should be good to go.

Hey there! I'm evaluating code-based presentation tools to build my future presentations in. I checked out Marp and RevealJS, but was ultimately drawn towards using MDX to build slides.
First I found mdx-deck, but then I also found this cool project. I'm actually tempted to start using this one, but the one thing that is really missing, is a good CLI to make it super easy to get started. Are you planning to merge and publish your CLI branch @whoisryosuke ?


Added a few more fixes for PBIRS Oct 2020 release

There are a few fixes missing from the list. Some customers have asked about them and they should be added publicly.

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

closing, redoing in private repo merging to master in https://github.com/MicrosoftDocs/powerbi-docs-pr/pull/4941


fix should do read lock on table being insert when analyze

picked from master
PR: #25619
commit id: 3ffc6f08354ca10a796d880aa762dee7a2f3be00
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Topic/native

So this works, but unfortunately the unit tests will only run on Linux. I couldn't find a way to call GCC from JUnit to compile the native library.

[Current coverage][cc-pull] is 89.06%

Merging [#5][cc-pull] into [master][cc-base-branch] will increase coverage by 0.12%

@@             master         #5   diff @@
==========================================
  Files            57         58     +1
  Lines          1323       1353    +30
  Methods           0          0
  Messages          0          0
  Branches        153        159     +6
==========================================
+ Hits           1176       1205    +29
  Misses          111        111
- Partials         36         37     +1

Powered by Codecov. Last updated by [d746b90...88ad538][cc-compare]
[cc-base-branch]: https://codecov.io/gh/aj-michael/minijavac/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/aj-michael/minijavac/compare/d746b902f8847cd1a5353d567909b63dc2aaff1a...88ad538b8eb667a847f2dade7186c5332f5f3b85
[cc-pull]: https://codecov.io/gh/aj-michael/minijavac/pull/5?src=pr

Also, we are no longer Java compliant (although technically neither was Thread#join). Normally, you have to call System.loadLibrary("MyLibrary"). But since we don't have support for strings, I made it a compiler flag. So if you want to compile code that uses the native keyword, you specify the name of the library with minijavac generate Main.java -l MyLibrary.


False exports detections

I don't know if its wrong for this lexer to pick up none valid module exports but this code should not report y as an export.
I guess it's because it's un aware of scopes and variable declarations.
function fake(module){
    module.exports.y = 1
}
fake({exports: {}});

Yes, as described in https://github.com/guybedford/cjs-module-lexer#named-exports-parsing the lexer will overclassify.
If you have a specific example you think is a bad overclassification happy to discuss further, but otherwise this is by design yes.


Different Color Priority for Space Parameters

The first 2 colors that show up when linking Space Parameters are gray and purple, but they're sort of hard to tell apart for me, so I was wondering if the priority could be changed, so it starts with blue & orange, or maybe make the colors a bit different to tell?
Thanks in advance!

One factor is that the opacity was at 0.5 for the colors. I bumped it up to 0.9 so maybe that helps? I'm not opposed to changing the color order necessarily but I just wonder if the opacity was the primary issue.


Fix redpanda tests

It seems^1 that redpanda will now throw errors if the advertised address is set to <IP_ADDRESS>.

Most tests run (and pass now) but still one error to figure out.

Tests are green now! 🥳

Tests are green now! 🥳

Awesome work!!


Report seems to be a bit off

Describe the bug
When running the report to see what should I improve, all the messages seem to be cutting the first 3 characters.
Config options
Default
To Reproduce
Steps to reproduce the behavior:

run :Hardtime report

Expected behavior
The report should display correctly the suggestions.
Screenshots

Additional context
I am using LazyVim if matters.

Could you provide your ~/.cache/nvim/hardtime.nvim.log? It's where the report messages are stored.

Absolutely:
[INFO  Mon Aug 21 10:54:11 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 10:54:16 2023] Use cw instead of dwi
[INFO  Mon Aug 21 10:54:24 2023] Use cw instead of dwi
[INFO  Mon Aug 21 10:57:57 2023] Use "_db instead of vb"_d
[INFO  Mon Aug 21 11:00:25 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 11:00:46 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 11:00:59 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:01:03 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:01:14 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:01:27 2023] Use db instead of vbd
[INFO  Mon Aug 21 11:01:54 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 11:04:13 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 11:05:46 2023] Use O instead of ko
[INFO  Mon Aug 21 11:07:14 2023] Use a instead of li
[INFO  Mon Aug 21 11:07:42 2023] Use a instead of li
[INFO  Mon Aug 21 11:07:49 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 11:07:51 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 11:08:28 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:09:47 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:10:39 2023] Use O instead of ko
[INFO  Mon Aug 21 11:11:07 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:11:54 2023] Use O instead of ko
[INFO  Mon Aug 21 11:12:06 2023] Use cw instead of dwi
[INFO  Mon Aug 21 11:15:31 2023] Use cit instead of diti
[INFO  Mon Aug 21 11:15:33 2023] Use a instead of li
[INFO  Mon Aug 21 11:56:49 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 11:57:10 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 11:58:48 2023] Use O instead of ko
[INFO  Mon Aug 21 11:58:53 2023] Use O instead of ko
[INFO  Mon Aug 21 12:06:11 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:06:13 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:06:14 2023] Use O instead of ko
[INFO  Mon Aug 21 12:06:24 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:06:56 2023] Use O instead of ko
[INFO  Mon Aug 21 12:07:14 2023] Use db instead of vbd
[INFO  Mon Aug 21 12:07:26 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:07:28 2023] Use cw instead of dwi
[INFO  Mon Aug 21 12:07:34 2023] Use O instead of ko
[INFO  Mon Aug 21 12:13:00 2023] Use O instead of ko
[INFO  Mon Aug 21 12:13:09 2023] Use O instead of ko
[INFO  Mon Aug 21 12:17:33 2023] Use d3j instead of V3jd
[INFO  Mon Aug 21 12:18:28 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:18:31 2023] Use cw instead of dwi
[INFO  Mon Aug 21 12:19:09 2023] Use cw instead of dwi
[INFO  Mon Aug 21 12:23:01 2023] Use O instead of ko
[INFO  Mon Aug 21 12:25:41 2023] Use a instead of li
[INFO  Mon Aug 21 12:26:02 2023] Use a instead of li
[INFO  Mon Aug 21 12:29:18 2023] Use db instead of vbd
[INFO  Mon Aug 21 12:45:54 2023] Use cw instead of dwi
[INFO  Mon Aug 21 12:47:36 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 12:47:39 2023] You pressed the h key too soon!
[INFO  Mon Aug 21 12:47:47 2023] You pressed the l key too soon!
[INFO  Mon Aug 21 13:06:53 2023] Use cw instead of dwi
[INFO  Mon Aug 21 13:07:11 2023] Use O instead of ko

Just hit this, thanks for resolving it in the update @m4xshen :)


Add printf-style support for messages

I recently ran into the situation, that I wanted to export some parametrized and localized messages to JavaScript. Imagine a text box that only allows a limited amount of characters. A hint like '23 characters left' would be shown, but this should be localized. So I'd add a message 'charactersLeft' to the culture's info like this:
Globalize.addCultureInfo("en", {
	messages: {
		"characterLeft": "%0n characters left"
	}
});
Globalize.addCultureInfo("de", {
	messages: {
		"characterLeft": "verbliebene Zeichen: %0n"
	}
});

Note that the format is similar to the Globalize.format function, but the precision and conversion are switched to be closer to the printf style. I could then do this to obtain the localized message:
var localized = Globalize.localize("charactersLeft", [23]);
// en: "23 character left"
// de: "verbliebene Zeichen: 23"

Nice and simple, isn't it?
I added the example 'formatter' witch contains a universal String formatter that behaves similar to C's printf or java.util.Formatter. The replacing happens in a concurrent manner, which means that replacing a specifier with another one won't do any harm. The specifiers support ordinary and argument indexing, precision and conversion (like Globalize.format), but no flags. Its localization is handled by pluging in a so-called Localizer. I added one that uses Globalize to format Dates, Numbers and Strings. The demo page shows the capabilities of the formatter. I've overwritten Globalize.localize in the example to directly integrate the formatter.
I've tested the formatter with jasmine (https://github.com/pivotal/jasmine), the localizer itself and the overwritten Globalize.localize are not tested yet.
Anybody interested in seeing this in Globalize? I'd give you the tests then (they kind of didn't fit into an example folder, so I left them away) or could do other stuff to get this thing merged.

An interesting idea. Some quick comments:
Starting numbering from 0 is natural to a programmer, less natural to (normal) human beings. It would be more natural if %1 stood for the first parameter and not for the second.
As translated strings will normally be written by translators - people who know human languages, not usually programming that much -, I wonder how well it would work to tell them to translate "%0n characters left". They areprobably used to working with "%1 characters left", but both the numbering and a format specifier like "b" would complicate things. Perhaps not too much, but they would need to know exactly which constructs are to be kept intact.
Translating patterns like "%1 characters" is tough. Very tough. Even for English, you get a grammatically wrong expression "1 characters" when the value is 1. For, say, Russian, it gets much worse: the form of the noun depends on the number in a relatively complicated manner (41 requires singular nominative, 42 requires singular genitive, for example), and constructing the form requires algorithms of its own, with a fairly large set of rules.
Such issues can be avoided, at the cost of clumsiness of expression, by rewording the entire statement, as in your example "verbliebene Zeichen: %0n" (which probably should have verbleibende, not verbliebene). But without extra logic that handles at least the special case of 1, this would be the right move even for English!
So I think it's better to suggest that the design of texts to be generated tries to avoid the issue of generating things like "n characters" with variable n, by trying to "factorize" sentences so that numeric data appears as standalone, outside sentence context - until we can address the issue of translating such expressions properly.


fix docker rm name issue

Addresses https://github.com/docker/docker/issues/12308
This is a workaround, I didn't find the root cause. This issue is strange,  docker rm /db won't even trigger router handler function. But the leading slash won't affect other commands. So this workaround just make the behavior the same as other commands.
Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

yep, docker rm /db will be DELETE /containers//db which seems not to match DELETE /containers/{name:.*} in mux. Much like if /db isn't allowed in .*

LGTM

@runcom We have GET /containers/{name:.*}/logs and docker logs /db works, so I tried to change rm API to DELETE /containers/{name:.*}/rm, but docker rm /db still not work, any thoughts on this? I still trying to figure out the root cause.

@hqhq wow.. didn't try that but I suspect it's something related to DELETE method perhaps if it's like you say, I'll have a look at gorilla mux source tomorrow btw


Update all internal imports relative. Update all external imports abs…

Update all internal imports relative. Update all external imports absolute. This is needed to work as an apworld.

Thanks to @Silvris for helping with file io and pkgutil.

New commit fixes Reaching goal early (fxpak) and the goal at the end. Thanks to @Silvris for proper event bit.


Multiple "Fetching search index..." notifications in github.dev

In my case I have switched to Insiders version of github.dev and as well as enabled search index couple of weeks ago.
When I opened github.dev again today I had Find in Files view active and started to type. Not sure if there were 3 notifications when page started loading, but when I finished I saw 3 similar notifications.
(I think there were two at some point and third appeared when I finished, but can't tell for sure as there were other notification for some time)

Version: 1.63.0-insider
Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4714.0 Safari/537.36 Edg/98.0.1089.1
Embedder: github.dev

Also saw this. Maybe related to anycode also triggering an index fetch?

Logic has since been updated quite a lot, this should not longer occur.


Allowing command module authors to inject formatter class.

@scobb,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

What is the intent behind exposing this functionality?

Our specific use case is that we need to allow users to specify argument values that begin with a hyphen. The only way to accomplish this is to use the equal version of argument specification:
--in=--some-user-value
We want the help messages to guide users to this--can get some of the functionality using metavar, but to force the equal to appear, we have to override the help parser.
Current help message without overriding HelpFormatter (notice no '=' after the first '--in')
usage: az ml service create batch [-h] [--output {json,tsv,table,jsonc}]
[--in <input_name>:[<default_value>]
[--in=...]]
Our desired help message is (notice the '=' after first '--in'):
usage: az ml service create batch [-h] [--output {json,tsv,table,jsonc}]
[--in=<input_name>:[<default_value>]
[--in=...]]

Codecov Report

Merging #2622 into master will decrease coverage by 0.65%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #2622      +/-   ##
=========================================
- Coverage   72.45%   71.8%   -0.66%
=========================================
  Files         374     375       +1
  Lines       20410   20691     +281
  Branches     2991    3035      +44
=========================================
+ Hits        14789   14858      +69
- Misses       4697    4901     +204
- Partials      924     932       +8

Impacted Files
Coverage Δ

src/azure-cli-core/azure/cli/core/parser.py
80% <100%> (+0.21%)
:arrow_up:

...azure-cli-core/azure/cli/core/commands/__init__.py
79.75% <100%> (+0.06%)
:arrow_up:

...cli-vm/azure/cli/command_modules/vm/_validators.py
68.5% <0%> (-3.67%)
:arrow_down:

.../azure/cli/command_modules/vm/_template_builder.py
77.71% <0%> (-3.24%)
:arrow_down:

...li-batch/azure/cli/command_modules/batch/custom.py
81.86% <0%> (-0.91%)
:arrow_down:

...zure-cli-vm/azure/cli/command_modules/vm/custom.py
72.94% <0%> (-0.89%)
:arrow_down:

...h/azure/cli/command_modules/batch/_command_type.py
94.39% <0%> (-0.71%)
:arrow_down:

...-batch/azure/cli/command_modules/batch/commands.py
100% <0%> (ø)
:arrow_up:

...i-batch/azure/cli/command_modules/batch/_format.py
13.79% <0%> (ø)

...ure-cli-vm/azure/cli/command_modules/vm/_params.py
96.09% <0%> (+0.03%)
: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 c0c9116...061a492. Read the comment docs.

The change itself looks fine to me. @johanste you opinion?

The changes look good - my only concern is that we are bypassing the formatter for some of the general help output. But as long as the help provided when providing --help to the command looks good, I'm fine with this change!


Tooltip not show style

Hello, i have problem about tooltip. It's not show style follow the example

This is my html code

When i find data-toggle="tooltip"  in boostrap.min.js. It's not found. Is it possible to be a reason?
Pls help me
Thank.

for help/how-to questions, please use stackoverflow or similar - see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker


Debug clock skew on macos workers

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Needed to debug kokoro macos flakes, merging.


cant inject "failed to find pattern #22"

whenever I try to inject I get this error message accompanied by csgo crashing

i think pattern 22 is for fake prime, it would make sense that it doesnt work anymore because of the last update

i think pattern 22 is for fake prime, it would make sense that it doesnt work anymore because of the last update

oh thats why

i think pattern 22 is for fake prime, it would make sense that it doesnt work anymore because of the last update

what about #26?


when i changing the animation to animation (by code) it doesn't work

Godot version:
Godot_v3.2.1-stable_win64
OS/device including version:
Windows 10
Issue description:
i think this is bug if not i am sorry so i have two animationPlayer in one scene but i cannot change animation to another animation
i mean i want when a texture button (screen) pressed the want to be changed to another animation
here is my code,
`extends TextureButton
onready var anim = get_node("AnimationPlayer")
##i connected to button node (presssed)##
func _on_TextureButton_pressed():
anim.play("starting")`
If you don't understand sorry i am very poor at explanation.if you have a question tell me
Steps to reproduce:

Unpack the archive
Open the project.
Minimal reproduction project:
The bob.zip

Cant run your project, but at first glance, you 'get_node("AnimationPlayer")' but you want get_node("../AnimationPlayer") (AnimationPlayer is sibling to your node with attached script, not his child)
Please, next time, try godotengine questions and answers first.


Not yet meeting all ETD requirements

According to USF ETD, this sample is not quite in line with ETD requirements.

Title Page

The spaces above and below "by" should both be the same length. The space above "by" is wider than the space below it.
Space between Committee and Date of Approval should be equal to 2 single-spaced lines or approx. 24pt. It should be the same size as the space between University of Florida and the first major professor line.
Space between date of approval and Keywords should be equal to 3 single-spaced lines or approx. 36pt. It should be the same size as the space between "by" and "author name"

Table of Contents

The second line of a long heading should be indented an additional 0.25" from where the first line starts

List of Figures/Tables

"Figure" and "Table" should start against the left margin
There should be a single line of space between each figure/table entry
Possibly also indent on long captions like in Table of Contents?

Figures/Tables

Figures/Tables should start against the top margin if they begin on a new page


[Feature Request]: Validate User input for Data Science Pipelines Database Connections

Feature description
In it's current implementation, Data Science Pipelines only supports Mysql-compliant databases.  This means that connection metadata (database name, username, and password) must conform to mysql specifications, and these have Regular Expressions associated with them (see related issue: opendatahub-io/data-science-pipelines-operator#207[1]).  Due to this stipulation, ODH Dashboard should also block users from providing invalid connection metadata
[1] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/207
Describe alternatives you've considered
Alternatively we rely on DSPO/DSPA updating it's CRD to reject improper metadata, but this is fragile and adding UI validation would be an extra added layer of confidence that only proper metadata is allowed.
Anything else?
No response

Migrated to https://issues.redhat.com/browse/RHOAIRFE-19


[ansible] build backend and doc, v2.3.2

Coverage remained the same at 89.114% when pulling 95eaa88359fb5d076b441c6941c2fffc0172e575 on bug-ansible-build-backend-doc into d1f5e3b3885ab74e95049d65e9aa396d00989f0d on master.


cordova-light support for android

Added support for cordova light apps
ping @aliok

@odra code looks good, but I would like to test it locally.

How I tested:
cd digger-build-cli
source activate digger
python setup.py install

cd /tmp
git clone https://github.com/feedhenry-templates/Push-Hello-World-Cordova-Light-Client
cd Push-Hello-World-Cordova-Light-Client
# checkout an old commit. after that commit, this template is converted to a full Cordova app
git checkout fe1b62bf976519158545b6b833a77c7ec6eeb7d5
abcd build --path=/tmp/Push-Hello-World-Cordova-Light-Client

> BUILD SUCCESSFUL
> Total time: 7.43 secs

If I just do abcd build --path=., I receive following:
  File "/Users/ali/miniconda3/envs/digger/lib/python3.5/site-packages/AeroGear_build_cli_for_Digger-0.3.1-py3.5.egg/digger/builds/cordova_android.py", line 80, in add_plugins
    with open('%s/www/config.json' % self.tmp_path) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/._tmp/www/config.json'

--path needs an absolute path for now

LGTM


The implementation of DiceLoss

Thanks for your share. When I run this version (40ae1aa) code and I get the following error:
`/userfolder/relaynet_pytorch/relaynet_pytorch/net_api/losses.py in forward(self, output, target, weights, ignore_index)
60             encoded_target[mask] = 0
61         else:
---> 62             encoded_target.scatter_(1, target.unsqueeze(1), 1)
63
64         if weights is None:
RuntimeError: invalid argument 3: Index tensor must have same dimensions as output tensor at /pytorch/aten/src/THC/generic/THCTensorScatterGather.cu:289
`
And the input data's size is [NumData, 1, rows, cols], the corresponding label's size is [NumData, 1，rows, cols]. The target of our is to segment 10 class.
I read the code and don't understand these code:
`
relaynet_pytorch/relaynet_pytorch/net_api/losses.py
lin51：output = output.exp()
lin52：encoded_target = output.detach() * 0
line61：encoded_target.scatter_(1, target.unsqueeze(1), 1)
`
In the older versions, the implementation of DiceLoss is different from this version code. And the older vision as follows:
`
class DiceLoss(_Loss):
def forward(self, input, target):

    return 1 - dice_coeff(input, target)

`
So which is better ? or which is the right version for the "ReLayNet" paper ?
Thanks a lot!

Hello,
The previous version of the code required passing of the binarized (one-hot encoded) ground truth for the Dice Loss, whereas the new version takes in the Ground Truth as [1,..,NumClass-1], and one-hot encode them within the function. This saves some RAM space when dealing with large number of classes. Functionally, both should perform the same.
Best
Abhijit

Thanks very a lot !
I will check these possible error result from the changes in the new version code.

Hi @Atomwh and @abhi4ssj ,
im getting the same error
RuntimeError: invalid argument 3: Index tensor must have same dimensions as output tensor at /pytorch/aten/src/THC/generic/THCTensorScatterGather.cu:289
The shape of my data is:
Tr_Dat = np.zeros((16, 1, 512, 512), dtype="float32");
Tr_Label = np.zeros((16, 1, 512, 512), dtype="uint8");
Tr_weights = np.zeros((16, 1, 512, 512), dtype="float32");
train_data = ImdbData(Tr_Dat, Tr_Label, Tr_weights);
test_data = ImdbData(Tr_Dat, Tr_Label, Tr_weights);
Which pytorch version should I use? And what is the solution to the error above?
Thanks


app.json runtime issue, not able to publish

Describe the bug
The minimum runtime version for using NavigationPageId and Multiplicity in api pages changed the last month. According to app.json documentation the runtime for 17.3 is 6.3 and for 17.4 it is 6.4. So when developing the above api pages, I am targeting 17.3 and 17.4 with their respective runtimes 6.3 or 6.4.
However, when publishing from VSCode, the following error occurs:
[2021-03-04 08:03:32.80] Sending request to https://bc173de:7049/BC/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default
[2021-03-04 08:03:33.04] The request for path /BC/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: The runtime version of the extension package is currently set to '6.3'. The runtime version must be set to '6.2' or earlier in the app.json file in order to install the extension package on this server.
To Reproduce

Install docker container with onprem:17.3.20469.20605-de
Create a new app with runtime set to 6.3 (to support NavigationPageId)
Add a dependency to "id": "10cb69d9-bc8a-4d27-970a-9e110e9db2a5", "name": "Exclude_APIV2", "publisher": "Microsoft", "version": "<IP_ADDRESS>"
Create an api page for Items, add id, no, description
Add field unitOfMeasureId with TableRelation = "Unit of Measure".SystemId;, NavigationPageId = "APIV2 - Units of Measure";
Publish

ERROR: The request for path /BC/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: The runtime version of the extension package is currently set to '6.3'. The runtime version must be set to '6.2' or earlier in the app.json file in order to install the extension package on this server.
Expected behavior
Successful publishing and correct runtime checking
Screenshots
5. Versions:
Using onprem:17.3.20469.20605-de
Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 6.6.425415
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.

Excuse me!? What is this, if not to "Report a bug in the latest AL compiler / Developer Tools"?
We are blocked to develop/publish apps from VSCode with this issue. So please reopen it!

Re-opening the issue, sorry for the confusion, we are looking into it.

@MODUSCarstenScholling thank you for reporting this issue. It appears indeed that the backward compatibility check done in the server for versions 17.2, 17.3, 17.4 and 17.5 is not correct, leading to some issues deploying extensions or using some features with are available for specific versions (as mentioned here).
We are working on a HF for it in SaaS and it will be available in docker images too.

This issue should now be fixed and should be deployed soon.
Here are the minimum server/platform versions containing the fix:

17.2: 17.0.19353.22854
17.3: 17.0.20458.22852
17.4: 17.0.21485.22862
17.5: 17.0.22463.22853

Do you know when will we able to create docker containers with this hotfix?
I cannot get artifact with mentioned versions for 17.4 and 17.5

The versions mentioned above are the platform versions. You should be able to see the version of the platform in the Help & Support page.


improves error handling for argument mismatch

fixes NPE when Intl definition did contain no arguments while ARB did provide some
skip the code generation for a message if argument mismatch has been detected instead of aborting the process / code generation.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

Googlers: Go here for more info.

@googlebot I signed it!

I don't know how relevant this PR might be today (after close to two years). Also the commit e6642485a5bb8d1fe5ddbb3cd8f3999bfaa6683c did not only migrate the project to dart null-safety but also did refactor a lot of architecture making a rebase impossible.
Any strong opinions on this other than closing the PR?

I am also fine with closing it, as it does not address a high-priority issue. But thanks for contributing, and sorry for the long wait!


Anyone Having Issues with Outlook 365?

I took a look through the issues board, and didn't see anything, so I figured I'd add a question.
I've rebuilt a profile now several different times, and THIS time, keeping track of what I add or Change before I have an inevitable breakdown of MS Outlook refusing to connect to anything, and I find that it's following my setting BrowserPicker as my default browser.
I enable the "always ask" option, as I have several links for different apps that I prefer to have open in different browsers for reasons, but is seems like within a day of enabling "always ask" my Outlook will hang up on "trying to connect", and balks on even letting me add a new profile.
My gut tells me that the BrowserPicker is somehow getting in the way of Outlook's Modern Authentication, but I can't prove that.
Anyone else seen anything like this? suggest a good workaround?

As I unfortunately have no way of debugging this myself, anything I could come up with would be pure conjecture.
Maybe try adding a default browser for the url that outlook opens?

With the new options for default browsers in 2.0, you may want to give this another go


Excel Cannot Open Generated File

Description
Anytime I generate a new xlsx file, Excel is not able to open it.  I am using Go Modules version github.com/xuri/excelize/v2.
I did some digging and the generated sheet1.xml file file has xmlns="" added to the dimension, sheetViews, sheetFormatPr, and sheetData tags.  Through experimentation I was able to determine that if I remove the xmlns="" property from the sheetData tag (or all tags), the workbook will open normally.
Steps to reproduce the issue:

var xlsx = excelize.NewFile()
xlsx.SaveAs([filepath_and_name])
Attempt to open the generated file with Excel and it will report "We found a problem with some content in [filename].  Do you want us to try to recover as much as we can?"

Describe the results you received:
Attempting to open a generated file with Excel produces the message: "We found a problem with some content in [filename].  Do you want us to try to recover as much as we can?"
Describe the results you expected:
The file to open correctly.
Output of go version:
go version go1.21.0 windows/amd64

Excelize version or commit ID:
<EMAIL_ADDRESS>
Environment details (OS, Microsoft Excel™ version, physical, etc.):
Windows 10, Excel 2016
sheet1.txt

This was duplicated with issue #1465, #1595, #1603 and #1619. I suggest using the previous Go version or waiting for the next minor releases.


Resource exhaustion in engine.io   CVE-2020-36048

Version
6.0.12
Browser and OS info
win10/node14.17.0
Steps to reproduce
npm init -f
npm install --save-dev  @vue/devtools
npm audit

What is expected?
no vulnerabilities found
What is actually happening?
High            Resource exhaustion in engine.io
Package         engine.io
Patched in      >=4.0.0
Dependency of   @vue/devtools [dev]
Path            @vue/devtools > socket.io > engine.io
More info       https://github.com/advisories/GHSA-j4f2-536g-r55m
found 1 high severity vulnerability in 186 scanned packages

https://overreacted.io/npm-audit-broken-by-design/


Extend standard Exception class by response code.

Description
Generated exceptions are catche by src/Controller/App.php line 16. There I would like to get HTTP response code from exception object. It should be named like getHttpStatusCode without parametter. Response code should be provided in constructor, or by setter. Code should be in src/Lib/Exception/Exception.php and namespace App\Exception. Also create unit tests! Check your code by PHPStan and CS.
Links

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
https://www.php.net/manual/en/language.exceptions.extending.php

List

[ ] Extended class

[ ] Pass PHPStan and CS

[ ] Cover code by unit test and it should pass

Steps to solve

Clone repository https://github.com/Stacha-dev/back-end to your sandbox
Follow install instructions in README.MD, before install.sh call git checkout develop in project root (there is some changes).
Checkout to develop branch and create your branch by git checkout -b dev_exceptions
Write your code, commit every finished step, push it to remote
Test by PHPStan calling composer phpstan and fix reported problems
Fix CS by composer cs:fix
Make pull request wait for code review


Add import and export functions

This would enable someone to export his database in a JSON format, well-formated for the viewer for example.
This file could be imported back in the manager too.

This would be a nice feature to have! Currently running my first tournament using your libraries, and I just ran into a small problem: I pushed a small fix during the tournament (luckily just before final match) and the deployment cleared the bracket database, so my Discord bot stopped working since it didn't find any participants or matches anymore 😄 I have the bracket structure stored elsewhere, so I could technically load the database based on that structure. However, it is currently not so straight-forward to do so.

Is this urgent? Have you managed to do it on your own?

Just to be sure: you have some JSON that can be used for the viewer (same data model) somewhere and you'd like to import it back in your deployed database thanks to the manager, right?
(that's the idea of this issue)

Just to be sure: you have some JSON that can be used for the viewer (same data model) somewhere and you'd like to import it back in your deployed database thanks to the manager, right?
(that's the idea of this issue)

Yes, exactly this. It's not urgent.
I can do some workarounds in my code and this "data loss" won't happen unless I do a new production deployment during the tournament, which I'm now going to avoid 😄 This only occurred because one of the players disconnected during their match (connection problems) and the game's API recorded that match to have been played, even though it had just started. If the match wasn't recorded as a played match, this wouldn't have been a problem.
The match was a best of three series where the first game was finished normally, second game resulted in connection loss and needed to be replayed. Since my code is getting X previous matches (in this case, 3), the one with the disconnection would have been included. I though that maybe if I filter out the match ID from the previous matches data, I could get around the problem. But then my deployment cleared the local data. Expected as it's using Docker images, but just hadn't occurred in my mind that this might happen 😄
I tried looking into node-json-db if it would be possible to use an existing structure, however I didn't come across a quick way to do it in the middle of the tournament. Some other person has asked for the same feature, but decided to close it without explanation...

Okay. I'll be busy this week so I don't think I will do it before next week or so.
But you definitely ranked this issue's priority up 😁

Define import() and export() in manager.ts, which only use CrudInterface methods behind the scene.

Fixed by https://github.com/Drarig29/brackets-manager.js/commit/ef639f1d41886fa13534c6814063785a10c335a7 and https://github.com/Drarig29/brackets-manager.js/commit/9da58698d3eb22c9705e37aa8258f5c095ababe6


update for pytorch 1.9.0, add zero_gradients function

close #59
Please review my code and merge this pull request.

Hi,
thanks for letting me know about this! I haven't tested the attacks with the PyTorch 1.9.0. I'll have a quick look, then merge.

Great, thanks!


Code is inserted at the top of file, not at cursor

I'm hoping that this extension will insert the interface implementation at the current cursor position, when invoked from the right-click context menu. It chooses to search from the top of the file for some condition, and inserts the code where it thinks it belongs. Obviously where it's inserting is incorrect. I'm guessing your code doesn't recognize multi-line use blocks.
Example from top of code file:

/** @package PROJECT */

namespace MAIN\Framework;

use MAINU\Enums\State;
use MAIN\Framework\BaseController;
use MAIN\Modules\ModuleManager;

use MAIN\Hooks\{
        // <<<<<<<<< functions inserted here
	IHandleHooks,
	InitHooks,
};
use MAIN\Init\{
	Activate,
	Deactivate,
};

Thanks.

@TonyGravagno yes, i didn't make a use blocks recognition as i didn't really use it because of IDE's auto imports :) I'll add it soon.
Code insertion at cursor as a good idea, i'll see what i can do about it.
Thanks for your feedback!


#5328: sliding window indices tensor need to be page size aligned

I left @shwetankTT's branch intact for now to separate the ttnn test port + other failure signatures from the test list, i.e. cases that are using an invalid sharding strategy.


Add orchestrator claimed rewards exporter

Is your feature request related to a problem? Please describe.
Introducing an exporter that fetches and exposes the LivePeer rewards claimed by the orchestrator would be beneficial.
Describe the solution you'd like
I examined the https://github.com/stronk-dev/LivepeerEvents/wiki/API-Call:-getAllRewardEvents endpoint for this purpose. However, I'm still looking for an endpoint specifically tailored to include only the rewards claimed by the orchestrator. This optimization would reduce fetch size and thereby decrease network traffic.
Describe alternatives you've considered
Alternatively, we can only fetch the rewards once every 6 hours.
Additional context
No response

Implemented in https://github.com/rickstaa/livepeer-exporter/releases/tag/v1.1.0.


Can IINA players be supported

The IINA player experience is quite good on Mac and is also open source

That's amazing. I tried changing it to a URL Scheme to open IINA, which also works
iina://weblink?url={{url}}

For now, in order to trigger IINA, we must go through a terminal session. I've opened a GitHub issue in order to change this behavior to match the same UX as with VLC - see here

This is now fix with v2.0.1. 😄


Allow exported variables in .env

Being able to export variables in a .env file allows one to be able to source the file in bash scripts, which can be immensely helpful.  I've updated the regex to also check for an optional unmatched group export\s+.
I also added a bit of regex to remove quotes for android - I'm sure that regex could be better, but I needed something like it and it worked for me.
Lastly I updated the regex101 link in ios/ReactNativeConfig/BuildDotenvConfig.ruby

Nice! I didn't realize people even exported vars from .env, thank you :+1:

Hi, I just found this when searching how to use .env variables in XCode scripts. Does this work just by prefixing .env variables with export  - is that right? I'd make an PR for documentation, but I'm not completely sure of the usage..


"Value of type "Callable[[], Any]" is not indexable" for pd.MultiIndex.levels

bug.py
import pandas as pd

def fun(foo: str, bar: pd.MultiIndex) -> None:
    print(foo in bar.levels[0])

fun("foo", pd.MultiIndex.from_product([["foo"], ["bar"]]))

$ mypy bug.py
itrade/cnn/bug.py:5: error: Value of type "Callable[[], Any]" is not indexable  [index]
Found 1 error in 1 file (checked 1 source file)
$ python bug.py
True
$ pip list | grep pandas
pandas                       1.4.1
pandas-stubs                 <IP_ADDRESS>
$ mypy --version
mypy 0.941

Interestingly, mypy is fine with this one:
import pandas as pd
print("foo" in pd.MultiIndex.from_product([["foo"], ["bar"]]).levels[0])

Hi @bersbersbers. Sorry for taking my time to have a look at this.
I've prepared a fix. Once the CI passes I'll merge it: https://github.com/VirtusLab/pandas-stubs/pull/158

Version <IP_ADDRESS> includes the fix. Please reopen the issue if you re-encounter this problem.

Thanks a lot, that was superquick :)


Update clair : image scanning not working

Description
Devtron is using old version of clair, i.e. quay.io/coreos/clair:v2.1.7. Clair has released multiple updates after this version and they contain breaking changes that are causing issues with scanning images. In the old version, clair used to get vulnerabilities from database which has been changed in the latest versions. This is causing some specific images(for ex:- with base images like centos, ubuntu etc.) to fail in scanning process. This issue can be fixed if clair is updated to one of the latest versions which contain the breaking changes different from the current version of clair devtron is using.
Logs
{"Event":"fetching vulnerability updates","Level":"info","Location":"updater.go:239","Time":"2022-01-24 13:12:58.240588"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"ubuntu.go:85","Time":"2022-01-24 13:12:58.240626","package":"Ubuntu"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"amzn.go:84","Time":"2022-01-24 13:12:58.240665","package":"Amazon Linux 2"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"alpine.go:176","Time":"2022-01-24 13:12:58.240710","package":"Alpine"}
{"Event":"Getting vulnerability data...","Level":"debug","Location":"alpine.go:136","Time":"2022-01-24 13:12:58.240800","package":"alpine"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"amzn.go:84","Time":"2022-01-24 13:12:58.240823","package":"Amazon Linux 2018.03"}

updated estimated time with inclusion of - setup problem exploration and fix time


How to read configuration in the workflow/decider

Does the SideEffect feature not address this? (https://github.com/uber-go/cadence-client/blob/master/workflow.go#L525)

The side effect should help here, this task was filed way before we designed side effect. Either we can close this and open a new one (or) use this to provide a sample of reading configuration.

Closing this.


validate that spec.memStorage.size does not surpass spec.resources

this is a followup ticket to #9
description
add validation to ensure that spec.memStorage.size does not surpass the spec.resources.
acceptance

[ ] CRs with memStorage.Size > resources.limits.memory are rejected.

hints
You can find some instructions for defaulting and validation here.

Blocked until its supported by k8s!

[ ] https://github.com/kubernetes-sigs/controller-tools/issues/827

/remove-lifecycle stale


Update examples.md

I think I've written this method a few times now, and keep having to scratch my head each time :-)...
So here it is - no pressure to merge if it isn't idiomatic :-).

Actually I've needed this several times as well, thank you! :P. I like the pipe approach more personally.
I would like the examples to be a bit more "hey why you would do it and this is how" style, so I would phrase it more like this:
## Writing data to a CSV file

If you want to save a list of a case class into a CSV file, you could do the following:
@:select(scala-version)

@:choice(scala-3)

\```scala mdoc:reset:silent
import fs2.*
import fs2.data.csv.*
import fs2.io.file.Path

// create an encoder for your case class, by creating a `CsvRowEncoder[YourCaseClass, String]`
given CsvRowEncoder[YourCaseClass, String] = deriveCsvRowEncoder

def writeCaseClassToCsv[A](path: Path)(using CsvRowEncoder[A, String]): Pipe[IO, A, Nothing] =
    _.through(encodeUsingFirstHeaders(fullRows = true))
      .through(text.utf8Encode)
      .through(Files[IO].writeAll(path))
      .drain
\```

@:choice(scala-2)

\```scala mdoc:reset:silent
import fs2._
import fs2.data.csv._
import fs2.io.file.Path

// create an encoder for your case class, by creating a `CsvRowEncoder[YourCaseClass, String]`
implicit val csvRowEncoder: CsvRowEncoder[YourCaseClass, String] = deriveCsvRowEncoder

def writeCaseClassToCsv[A](path: Path)(using CsvRowEncoder[A, String]): Pipe[IO, A, Nothing] =
    _.through(encodeUsingFirstHeaders(fullRows = true))
      .through(text.utf8Encode)
      .through(Files[IO].writeAll(path))
      .drain

\```

With the benefit of hinsight, my original PR was rushed, and perhaps a little sloppy. Will tidy with the suggestions above - thanks for feedback - agreed on all points. Will revise in the next days when I have a few mins at keyboard to devote to it!

Thanks for all the feedback - incorporated and hopefully mergable now :-)

@zetashift  I thought I already approved and committed them? Ah... I fear however, that I did not press the "resolve conversation" button ... gonna do that right now.

@zetashift  Oh dear, I honestly thought I'd done them. I've had another go.

I might be asking a silly question, but where is the evaluation happening in these scripts?
They appear to be more similar to code examples than auto-runnable scripts, no?
Or are they meant to be used as scala worksheets (and in that case, where's the Stream evaluation)?
I would add, like in other examples the usual IOApp.Simple and .compile.drain, or add a brief explanation on how to use them as worksheets.

Here's a runnable example:
//> using toolkit typelevel:latest
//> using scala 3.3.1
import fs2.io.file.Files

import fs2.data.csv.*
import fs2.data.csv.generic.semiauto.*
import fs2.io.file.Path
import cats.effect.{IO, IOApp}
import fs2.{Pipe, Stream}
import java.time.LocalDate

/** Define your case class and derive an encoder for it */
case class YourCaseClass(n: String, i: Int)
given CsvRowEncoder[YourCaseClass, String] = deriveCsvRowEncoder

def writeCaseClassToCsv[A](
    path: Path
)(using CsvRowEncoder[A, String]): Pipe[IO, A, Nothing] =
  _.through(encodeUsingFirstHeaders(fullRows = true))
    .through(fs2.text.utf8.encode)
    .through(Files[IO].writeAll(path))
    .drain

/** Example Let's imagine we have a `Book` case class we would like to write to
  * a .csv file.
  */
object WriteBooksToCsv extends IOApp.Simple:
  case class Book(id: Long, name: String, isbn: String)
  given CsvRowEncoder[Book, String] =
    deriveCsvRowEncoder // Don't forget to define an Encoder for your case class!

  val input = Seq(
    Book(1, "Programming in Scala", "9780997148008"),
    Book(2, "Hands-on Scala Programming", "9798387677205"),
    Book(3, "Functional Programming in Scala", "9781617299582")
  )

  def run: IO[Unit] =
    Stream
      .emits(input)
      .through(writeCaseClassToCsv(Path("books.csv")))
      .compile
      .drain

@Quafadas if you don't have time to update the PR, is it okay if I add this in?

Continued here: https://github.com/typelevel/toolkit/pull/120 because completing this PR through Quafadas fork is getting too slow. Still @Quafadas thank you!!


fix: code allows sitemapOutFile to be null but type is wrong

Fix #2872
What is it?

[ ] Feature / enhancement
[x] Bug
[ ] Docs / tests

Description
See #2872
Use cases and why

One use case

Another use case

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

makes a lot of sense! i would love to merge this!
the CI is failing because there is a change in types, so it's needed to run pnpm build.full to update them

makes a lot of sense! i would love to merge this!
the CI is failing because there is a change in types, so it's needed to run pnpm build.full to update them

thanks, I forgot that.
done!


Add post for SWIFT private preview

Add wiki for SWIFT private preview
Add issue templates

@microsoft-github-policy-service agree


helidon-standalone-quickstart-mp does not support GraalVM native-image

Environment Details

Helidon Version: 2.0.0-RC1
Helidon MP
JDK version: GraalVM Version 20.1.0 (Java Version 11.0.7)
OS: Ubuntu 16.04 LTS
Docker version (if applicable):

Problem Description
profile for native image is not applicable for helidon-standalone-quickstart-mp. Native image generation fails if it is used. If it is not required to support GraalVM native image for this quick start, its description shall be removed from README.md in the same module. By default profile is not set, so the only thing which does not corresponds is README.md. But otherwise native-image shall be fixed.
Steps to reproduce
mvn package -Pnative-image

stack trace:
[INFO] --- helidon-maven-plugin:1.1.1:native-image (default) @ helidon-standalone-quickstart-mp ---
[INFO] Building native image :/home/mavines/git/helidon/examples/quickstarts/helidon-standalone-quickstart-mp/target/helidon-standalone-quickstart-mp
[INFO] [helidon-standalone-quickstart-mp:13083]    classlist:  18,297.09 ms,  0.94 GB
[INFO] [helidon-standalone-quickstart-mp:13083]        (cap):   4,673.44 ms,  0.94 GB
[INFO] [helidon-standalone-quickstart-mp:13083]        setup:  12,190.19 ms,  0.94 GB
[INFO] 2020.06.11 14:10:56 INFO io.helidon.microprofile.cdi.LogConfig Thread[ForkJoinPool-2-worker-5,5,main]: Logging at initialization configured using classpath: /logging.properties
[INFO] 2020.06.11 14:10:56 INFO org.jboss.weld.Version Thread[ForkJoinPool-2-worker-5,5,main]: WELD-000900: 3.1.3 (Final)
[INFO] 2020.06.11 14:10:59 INFO org.jboss.weld.Bootstrap Thread[ForkJoinPool-2-worker-5,5,main]: WELD-ENV-000020: Using jandex for bean discovery
[INFO] 2020.06.11 14:10:59 INFO org.jboss.weld.Bootstrap Thread[ForkJoinPool-2-worker-5,5,main]: WELD-000101: Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
[INFO] 2020.06.11 14:10:59 INFO org.jboss.weld.Event Thread[ForkJoinPool-2-worker-5,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] private io.helidon.microprofile.openapi.OpenApiCdiExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
[INFO] 2020.06.11 14:10:59 INFO org.jboss.weld.Event Thread[ForkJoinPool-2-worker-5,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] public org.glassfish.jersey.ext.cdi1x.internal.ProcessAllAnnotatedTypes.processAnnotatedType(@Observes ProcessAnnotatedType<?>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
[INFO] 2020.06.11 14:12:37 WARNING com.netflix.config.sources.URLConfigurationSource Thread[ForkJoinPool-2-worker-5,5,main]: No URLs will be polled as dynamic configuration sources.
[INFO] 2020.06.11 14:12:37 INFO com.netflix.config.sources.URLConfigurationSource Thread[ForkJoinPool-2-worker-5,5,main]: To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
[INFO] Warning: RecomputeFieldValue.ArrayIndexScale automatic substitution failed. The automatic substitution registration was attempted because a call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) was detected in the static initializer of rx.internal.util.unsafe.ConcurrentCircularArrayQueue. Detailed failure reason(s): Could not determine the field where the value produced by the call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) for the array index scale computation is stored. The call is not directly followed by a field store or by a sign extend node followed directly by a field store.
[INFO] Warning: RecomputeFieldValue.ArrayBaseOffset automatic substitution failed. The automatic substitution registration was attempted because a call to jdk.internal.misc.Unsafe.arrayBaseOffset(Class) was detected in the static initializer of rx.internal.util.unsafe.ConcurrentCircularArrayQueue. Detailed failure reason(s): Could not determine the field where the value produced by the call to jdk.internal.misc.Unsafe.arrayBaseOffset(Class) for the array base offset computation is stored. The call is not directly followed by a field store or by a sign extend node followed directly by a field store.
[INFO] Warning: RecomputeFieldValue.ArrayIndexScale automatic substitution failed. The automatic substitution registration was attempted because a call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) was detected in the static initializer of rx.internal.util.unsafe.SpscUnboundedArrayQueue. Detailed failure reason(s): Could not determine the field where the value produced by the call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) for the array index scale computation is stored. The call is not directly followed by a field store or by a sign extend node followed directly by a field store.
[INFO] Warning: RecomputeFieldValue.ArrayIndexScale automatic substitution failed. The automatic substitution registration was attempted because a call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) was detected in the static initializer of rx.internal.util.unsafe.ConcurrentSequencedCircularArrayQueue. Detailed failure reason(s): Could not determine the field where the value produced by the call to jdk.internal.misc.Unsafe.arrayIndexScale(Class) for the array index scale computation is stored. The call is not directly followed by a field store or by a sign extend node followed directly by a field store.
[INFO] Warning: RecomputeFieldValue.ArrayBaseOffset automatic substitution failed. The automatic substitution registration was attempted because a call to jdk.internal.misc.Unsafe.arrayBaseOffset(Class) was detected in the static initializer of rx.internal.util.unsafe.ConcurrentSequencedCircularArrayQueue. Detailed failure reason(s): Could not determine the field where the value produced by the call to jdk.internal.misc.Unsafe.arrayBaseOffset(Class) for the array base offset computation is stored. The call is not directly followed by a field store or by a sign extend node followed directly by a field store.
[INFO] WARNING GR-10238: VarHandle for static field is currently not fully supported. Static field private static volatile java.lang.System$Logger jdk.internal.event.EventHelper.securityLogger is not properly marked for Unsafe access!
[INFO] [helidon-standalone-quickstart-mp:13083]     (clinit):   1,733.70 ms,  5.17 GB
[INFO] [helidon-standalone-quickstart-mp:13083]   (typeflow): 287,044.42 ms,  5.17 GB
[INFO] [helidon-standalone-quickstart-mp:13083]    (objects): 109,558.26 ms,  5.17 GB
[INFO] [helidon-standalone-quickstart-mp:13083]   (features):   5,873.99 ms,  5.17 GB
[INFO] [helidon-standalone-quickstart-mp:13083]     analysis: 411,785.34 ms,  5.17 GB
[WARNING] Error: Unsupported features in 2 methods
[WARNING] Detailed message:
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor$Worker.thread of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor$Worker@540ef7af reached by
[WARNING] 	reading field java.util.HashMap$Node.key of
[WARNING] 		constant java.util.HashMap$Node@ed3977f reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@233e4dd9 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@6b8d0779 reached by
[WARNING] 	reading field java.util.HashSet.map of
[WARNING] 		constant java.util.HashSet@c15667a9 reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workers of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$Node.thread of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$Node@58dde31b reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.lastWaiter of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7aee5a22 reached by
[WARNING] 	reading field java.util.concurrent.LinkedBlockingQueue.notEmpty of
[WARNING] 		constant java.util.concurrent.LinkedBlockingQueue@41a502e reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workQueue of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING]
[WARNING] com.oracle.svm.core.util.UserError$UserException: Unsupported features in 2 methods
[WARNING] Detailed message:
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor$Worker.thread of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor$Worker@540ef7af reached by
[WARNING] 	reading field java.util.HashMap$Node.key of
[WARNING] 		constant java.util.HashMap$Node@ed3977f reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@233e4dd9 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@6b8d0779 reached by
[WARNING] 	reading field java.util.HashSet.map of
[WARNING] 		constant java.util.HashSet@c15667a9 reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workers of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$Node.thread of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$Node@58dde31b reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.lastWaiter of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7aee5a22 reached by
[WARNING] 	reading field java.util.concurrent.LinkedBlockingQueue.notEmpty of
[WARNING] 		constant java.util.concurrent.LinkedBlockingQueue@41a502e reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workQueue of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING]
[WARNING] 	at com.oracle.svm.core.util.UserError.abort(UserError.java:79)
[WARNING] 	at com.oracle.svm.hosted.FallbackFeature.reportAsFallback(FallbackFeature.java:217)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:753)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGenerator.doRun(NativeImageGenerator.java:538)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGenerator.lambda$run$0(NativeImageGenerator.java:451)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1407)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
[WARNING] 	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)
[WARNING] Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Unsupported features in 2 methods
[WARNING] Detailed message:
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor$Worker.thread of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor$Worker@540ef7af reached by
[WARNING] 	reading field java.util.HashMap$Node.key of
[WARNING] 		constant java.util.HashMap$Node@ed3977f reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@233e4dd9 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@6b8d0779 reached by
[WARNING] 	reading field java.util.HashSet.map of
[WARNING] 		constant java.util.HashSet@c15667a9 reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workers of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING] Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image run time.  To see how this object got instantiated use -H:+TraceClassInitialization. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image run time by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
[WARNING] Trace: Object was reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$Node.thread of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$Node@58dde31b reached by
[WARNING] 	reading field java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.lastWaiter of
[WARNING] 		constant java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7aee5a22 reached by
[WARNING] 	reading field java.util.concurrent.LinkedBlockingQueue.notEmpty of
[WARNING] 		constant java.util.concurrent.LinkedBlockingQueue@41a502e reached by
[WARNING] 	reading field java.util.concurrent.ThreadPoolExecutor.workQueue of
[WARNING] 		constant java.util.concurrent.ThreadPoolExecutor@443e804b reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader.executor of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEventPreloader@6eab666 reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.preloader of
[WARNING] 		constant org.jboss.weld.bootstrap.events.ContainerLifecycleEvents@1b99c891 reached by
[WARNING] 	reading field java.util.HashMap$Node.value of
[WARNING] 		constant java.util.HashMap$Node@438e8a63 reached by
[WARNING] 	indexing into array
[WARNING] 		constant java.util.HashMap$Node[]@c4260b6 reached by
[WARNING] 	reading field java.util.HashMap.table of
[WARNING] 		constant java.util.HashMap@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry.services of
[WARNING] 		constant org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry@1abdeacc reached by
[WARNING] 	reading field org.jboss.weld.environment.deployment.AbstractWeldDeployment.serviceRegistry of
[WARNING] 		constant org.jboss.weld.environment.deployment.WeldDeployment@7d5cc359 reached by
[WARNING] 	reading field io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi.deployment of
[WARNING] 		constant io.helidon.microprofile.cdi.HelidonContainerImpl$HelidonCdi@15c47aae reached by
[WARNING] 	reading field java.util.concurrent.atomic.AtomicReference.value of
[WARNING] 		constant java.util.concurrent.atomic.AtomicReference@7f5f1b39 reached by
[WARNING] 	scanning method io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] Call path from entry point to io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI():
[WARNING] 	at io.helidon.microprofile.cdi.HelidonCdiProvider.getCDI(HelidonCdiProvider.java:29)
[WARNING] 	at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
[WARNING] 	at com.oracle.svm.reflect.CDI_current_4f3ca7f3b2c81296f8ef411f769b23ecb5f90faf_1839.invoke(Unknown Source)
[WARNING] 	at java.lang.reflect.Method.invoke(Method.java:566)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:345)
[WARNING] 	at javax.xml.transform.TransformerException.printStackTrace(TransformerException.java:285)
[WARNING] 	at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:761)
[WARNING] 	at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)
[WARNING]
[WARNING] 	at com.oracle.graal.pointsto.constraints.UnsupportedFeatures.report(UnsupportedFeatures.java:129)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:750)
[WARNING] 	... 8 more
[WARNING] Error: Image build request failed with exit status 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  08:05 min
[INFO] Finished at: 2020-06-11T14:17:47+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.helidon.build-tools:helidon-maven-plugin:1.1.1:native-image (default) on project helidon-standalone-quickstart-mp: Image generation failed, exit code: 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/dis

This is fixed in master. Will require Helidon build tools 2.1.1 to fix this on non-Windows environments

Cannot reproduce on current master. Found a different problem (quoted path) that is resolved by new build tools. Closing this issue.

Workaround until we release the fix:
Please update version of the helidon plugin to 2.1.1, usually there is a property:
<version.plugin.helidon>2.1.1</version.plugin.helidon>


Improve performance with clang builtin type pack element

__type_pack_element source
I don't know if you already use this, but I wanted to share it

Here is some additional info on compiletime performance of  different parameter pack indexing methods https://ldionne.com/2015/11/29/efficient-parameter-pack-indexing/


Dockerfile support for add --chown is missing.

We have it for the buildah copy command, but the syntax checker for Docker file fails.
cat Dockerfile
from fedora
copy --chown 3267:3267 dan.tar

 buildah bud -f Dockerfile .
STEP 1: FROM fedora
STEP 2: copy --chown 3267:3267 dan.tar
error building: error building at step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin DISTTAG=f27container FGC=f27 FBR=f27] Command:copy Args:[3267:3267 dan.tar] Flags:[--chown] Attrs:map[] Message:COPY --chown 3267:3267 dan.tar Original:copy --chown 3267:3267 dan.tar}: no files found matching "/root/3267:3267": no such file or directory

Closing as we've created a Trello card to track tihis at: https://trello.com/c/O2IMRqDB

@ripcurld @TomSweeneyRedHat Any movement on imagebuilder with this support?

Tom we are still missing this functionality.  Could you take a look at this, I think this needs work in imagebuilder.

https://github.com/openshift/imagebuilder/issues/77

Stil not resolved in imagebuilder.

Yeah this bubbled down below my radar.  I'll try to pop it back up and look into it again.

We now have support.  Thanks @TomSweeneyRedHat


Add metrics and log for txn

as title says

PTAL @zhangjingpeng1987 @AndreMouche

Is it really necessary to rename "snapshot" to "txn_snapshot"?
I think there is no other "snapshot" concept in the "txn" module.

@huachaohuang yes, but there is in raftstore

I have the same question here, for the metrics, we already have the sub-namespace so we can distinguish txn and raftstore.
I guess you here just want to let the Grafana show clearly, maybe you should update Grafana only.

any update?

@siddontang agree with you, I will take a look at granfana.

LGTM