Follow first link on suggestion selection.

It would be nice if we could have an option to follow the first link of a suggestion on click and suggestion selection.
Is suppose this feature is re-implemented in nearly every usage of the lib.
WDYT?

Not sure I got your point. To follow the link of a clicked/selected suggestion I'm used to do:
.on('autocomplete:selected', function(dataset, suggestion) {
  location.href = suggestion.myUrlAttribute;
});

Yes I got the same piece of code, so that's why I thought we could integrate it into the lib somehow.
We could rely on the dom of the currentTarget like:
window.location.href = $(e.currentTarget).find('a:first').attr('href');

And we could instantiate the autocomplete like:
searchInput.autocomplete(
            {
                followLinks: true
            },
            sources
        );

In my opinion it is not a huge feature, but at the same time this is used on every implementation, so very handy.

Might be a bit tricky if you don't render any <a> element (I remember rendering suggestions with <div> only) but I understand your point.
Maybe we could also do something like:
searchInput.autocomplete({
    locationKey: 'myurlattribute'
  },
  sources
);

To keep compliant with the displayKey option and not rely on DOM parsing.

Yes for the way where the user has an href property in his record and we follow it if he provided so in the options of autocomplete.js.
We should no try to dig inside the suggestion rendered DOM indeed, you could have multiple <a> for various usages.

You both made your points about not basing the feature on the DOM.
Your suggestion about giving a key available in the suggestion looks great!

Your suggestion about giving a key available in the suggestion looks great!

I'm not sold by the locationKey yet, maybe hrefKey or urlKey or linkKey ?

In other projects like instantsearch.js, when talking about objects, we then talk about attributes (meaning properties of the object)

Yeah, here we're already talking about key so I think I'll keep that.

Hard choice indeed, I personally prefer locationKey or urlKey.

urlKey seems good

Autocomplete v0 has been in low maintenance mode for a few years and we just released Autocomplete v1 so I'm closing this.
This is now supported with getItemUrl.
Resources

Getting Started
Populating Autocomplete with Sources
getItemUrl
Integrating Keyboard Navigation


Admonitions in partials outside the docs directory are rendered as plain text

🐛 Bug Report
Prerequisites

[x ] I'm using the latest version of Docusaurus. I'm using the canary release 0.0.0-3914 because it support adding partials from outside the docs plugin directory.

Description
When including a partial from a file outside the doc plugin directory, if the partial contains admonitions then the admonitions are rendered as plain text.
Have you read the Contributing Guidelines on issues?
Yes.
Steps to reproduce

Create a new project from the template with npx @docusaurus/init@latest init my-website classic

Update Docusaurus version to a canary release that supports including partials from outside the docs plugin directory, currently 2.0.0-beta.4 does not support it. I've used 0.0.0-3914.

Create a new file /docs/test-doc.mdx and a directory and partial file /_shared/test-partial.mdx:

/docs/test-doc.mdx---
id: test-doc
---
import TabItem from '@theme/TabItem';
import Tabs from '@theme/Tabs'
import Partial from<EMAIL_ADDRESS>
# Test Doc #

Some paragraph.

:::info

This is an info panel outside a partial.

:::

<Partial />

/_shared/test-partial.mdximport Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

:::info

This is an info panel inside a partial.

:::

<Tabs
defaultValue="apple"
values={[
    {label: 'Apple', value: 'apple'},
    {label: 'Orange', value: 'orange'},
    {label: 'Banana', value: 'banana'},
]}>
<TabItem value="apple">This is an apple 🍎</TabItem>
<TabItem value="orange">This is an orange 🍊</TabItem>
<TabItem value="banana">This is a banana 🍌</TabItem>
</Tabs>

```bash title="source.sh"
# Source is ok
$ ls -l .
\```

Run npx docusaurus start and navigate to http://localhost:3000/docs/test-doc.

Expected behavior
The admonition from the partial file /_shared/test-partial.mdx (This is an info panel inside a partial.) should be rendered with admonition style instead of plain text.
Actual behavior

There are no errors on npx docusaurus start.
Your environment

Public source code: https://codesandbox.io/s/youthful-architecture-w2xcy?file=/docs/test-doc.mdx
Public site URL: https://w2xcy.sse.codesandbox.io/docs/test-doc
Docusaurus version used: 0.0.0-3914
Environment name and version: Chrome 92.0.4515.131, Node.js 16.4.0
Operating system and version: Ubuntu 20.04.2 LTS

Reproducible demo
https://codesandbox.io/s/youthful-architecture-w2xcy?file=/docs/test-doc.mdx
Visit the page https://w2xcy.sse.codesandbox.io/docs/test-doc to see the issue live.

agree, the issue is the extra space

Sorry, indeed I made a syntax issue mistake while creating the initial sandbox environment.
Nevertheless, after fixing the syntax issue and creating a proper setup where the partial is a file outside /docs, I could reproduce the potential bug.

Right, can reproduce the issue 👍 will get this fixed

fixed in https://github.com/facebook/docusaurus/pull/5339


Add changelog

Because it’s important.

@sokra genuinely doesn't care about informing people of what he's doing with webpack.  You'll be waiting a long time for this.

@d3viant0ne I guess this will be solved once we get this project to follow the standard structure, right?

yep standard version generates a CHANGELOG.md following git tags and extract them based on the angular commit convention, so at mininum commits starting from the last (current)  tag must be reworded to follow the convention

@michael-ciniawsky Is it possible to lint PRs against the commit convention? I think that would help a lot.

@bebraw https://github.com/marionebl/conventional-changelog-lint [+ https://gitcop.com/]

@michael-ciniawsky 👍 Thanks.

We have a standard setup for this, i'll PR it in shortly. See webpack/webpack#4104

Already fixed changelog


Added support for listenPort in airMobile convention (adt -listen flag)

It was impossible to set -listen flag for adt. Added listenPort property of airMobile, which sets this flag.

Thanks for the PR! Looks good!
I've changed the base to the 'develop' branch, since that's the one containing all the latest development code.


Journal count on profile page doesn't go down when journal entries are deleted

From: https://forum.inaturalist.org/t/my-list-of-people-i-follow-shows-journal-entries-but-when-i-click-on-view-journal-no-entries-appear-for-that-person/16314/6
For example, @bouteloua's test account zeet had three journal posts, but two were deleted weeks ago. However, the profile page for zeet still shows 3 journal entries: https://www.inaturalist.org/people/zeet

I'll take a look.


Upgrading Golang to 1.12.8

What does this PR do?
Upgrading Golang to 1.12.8.

Hi @hush-hush
they just announced 1.12.9, maybe it is worth to migrate to this latest version.

@clamoriniere indeed I just saw this ... Closing this PR and opening another one


add --startup-size option to yamitranscode and yamvpp

same as the #67 .
Because @xuguangxin is busy on other thing, I help to fix the review issues.

please help to review, thanks a lot.

Hi @wudping
Why you close this branch?

sorry, @xuguangxin, It's a accident.
I cleaned my repository and branches with script yesterday.
I will reopen it.

Please fix compile issues (rebase?):
14:52:19,038 INFO  - ../tests/vppoutputencode.cpp: In function 'void setEncodeParam(const std::shared_ptr<YamiMediaCodec::IVideoEncoder>&, int, int, const EncodeParams*, const char*, uint32_t)':
14:52:19,038 INFO  - ../tests/vppoutputencode.cpp:124:36: error: 'VideoRateControlParams {aka struct VideoRateControlParams}' has no member named 'layerBitRate'; did you mean 'bitRate'?
14:52:19,039 INFO  - memcpy(encVideoParams.rcParams.layerBitRate, encParam->layerBitRate,
14:52:19,039 INFO  - ^~~~~~~~~~~~
14:52:19,039 INFO  - ../tests/vppoutputencode.cpp:169:27: error: 'VideoParamsAVC {aka struct VideoParamsAVC}' has no member named 'temporalLayerNum'
14:52:19,039 INFO  - encVideoParamsAVC.temporalLayerNum = encParam->temporalLayerNum;
14:52:19,039 INFO  - ^~~~~~~~~~~~~~~~

updated, Thanks @uartie .

@xuguangxin @wudping is this ready to be merged?

Closing... No activity or response from submitter or reviewers for over 30 days.


Why do log e and log 10 charts look identical?

Discovered during https://github.com/phetsims/bamboo/issues/27, why do log e and log 10 charts look identical?  Note that this problem predated changes in #27.

This is to be expected, since we are using the same chart area and gridlines, and since changing base only changes the scale (but the scale is fixed, as I mentioned).  Closing.


datetime fixes

Changes
Fixes to datetime issues including:

all datetime creations are TZ aware
standardize on UTC across the application
no use of today (is naive, use now)

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#169  👈
#168
#167
#166
#165
#164
#163
#162
#161
#160
#159
#158
#157
#156
#155
#154
master

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

Join @chrisaddy and the rest of your teammates on  Graphite


application always get  ' unfortunately app has stopped '

its always get that annoying error
i tried different apks from different sites !
and always get this ?
any help ?

i tried many apk files from different sources I got the same problem. any idea on what's causing it  ?

@maklmakl @winner91 Can you guys share some details of your environments? Is this Kali rolling? Are you using Metasploit that is included with Kali? Any other additional information you think might be useful.
In the meantime, I'll update my instance of Kali and test for similar issues.

Closing as duplicate of issue: #54


[pt-br] Update docs/concepts/storage/volumes.md

Fixes #41502
This PR aims to update the Portuguese version of the volumes page, by marking the deprecated volume types.

/cc
/uncc @saad-ali @thockin
/retitle [pt-br] Update docs/concepts/storage/volumes.md

Thanks!
/approve


Support null-coalescing operator and Xor operator

I noticed that these operators are not supported.

Released in 0.10.0


Few broken URLs in the code and docs

Loving the work on Ponzu, keep it up!
Seems a few links broken however:
addons.ponzu-cms.org - Dead, referenced in docs and plugins.
https://www.bosssauce.it/ - On admin footer, broken too.

Hey there, I think the first of these is a known issue that just hasn't been addressed yet. Re the second, please would you clarify - the link in the ponzu server application's /admin footer is ok for me so you probably have spotted something else?  If you're able to, and have the time, a fix for these via PR would be great.  The main dev behind Ponzu is pretty busy ATM, so community contributions to the Ponzu project are especially welcome.

@benduncan @olliephillips -
thanks for pointing these out! As Ollie mentioned, the first is indeed a known issue. I'd love to follow through with the "Addon Marketplace" I had initially set out to build... however, the second link should now resolve just fine -- I had accidentally reverted some DNS records in a registrar migration and the broken link was a sad side effect.
I'm going to close this issue, as it is (half) resolved... Appreciate the heads up!


How to  filter or search the editColumn ?

@yajra ,
Can I ask some help please, How can I filter or search in my editColumn
here is my code
     $model = Po::select(['id','vendor_id','amount']);

    return Datatables::of($model)
            ->editColumn('vendor_id',function( $m ){
                return Vendor::find($m->vendor_id)->name;
            })

         ->filterColumn('vendor_id', function($query, $keyword) {
                $sql = "like ?"; //here I have no idea what to do.
                $query->whereRaw($sql, ["%{$keyword}%"]);
            })
         ->make(true);

Thank you in advance.

Try using eager loading?
     $model = Po::with('vendor')->select(['id','vendor_id','amount']);

    return Datatables::of($model)->make(true);

On you scripts:
columns: [
    {data: 'id'},
    {data: 'vendor.name'},
    {data: 'amount'}
]

Some demo for ref:
http://dt54.yajrabox.com/eloquent/has-one
https://datatables.yajrabox.com/relation/belongs-to

Thank you so much @yajra

can we don't do with
->filterColumn('vendor_id', function($query, $keyword) {
$sql = "like ?"; //here I have no idea what to do.
$query->whereRaw($sql, ["%{$keyword}%"]);
})
?  i want to done with this only , please any solution


Embedded dependencies crash on 1.20.1

Dependencies bundled with the mod (Polymer and Server Translations API) use versions incompatible with 1.20.1, causing a crash (which is hidden unless you extract the dependencies' JARs).
While for Polymer this can be worked around, by simply downloading a compatible version off of Modrinth and editing this mod's json to not reference the invalid version stored within, I was unable to find such a version for the translations API.
The mod seems to work fine without the latter, at least in a singleplayer setting, so it's not that big of a deal, but I hope this gets fixed.

Thanks for letting me know. I appreciate your thorough investigation and troubleshooting. I've uploaded versions on both Modrinth and Github that have the appropriate dependencies and versioning for 1.20.1. This is a band aid fix, but I'm not proficient enough nor do I really have the motivation to set up the proper subprojects to support a high number of Minecraft versions. This means as of right now the mod only supports 1.20.1 and 1.20.4, which to my knowledge are two of the most commonly modded modern Minecraft versions.
This fix should at the very least stop you from having to download a separate version of Polymer. Please let me know if there are still issues. Have a fine day.


Add support for optional numbers

Fixes #624.

Thanks for this!
It looks like the in-memory representation of optional types is a u32 indicating whether it's Some or None and then the payload itself? That seems plausible to me!
@fitzgen was experimenting using the "global stack" as well for the payload and/or discriminant, as this I believe would enable a blanket implementation for all Option<T> rather than needing a per-type solution (like we need today)
Another option I was thinking of is that if we want to go the super-specialized route we could support Option<T> for all T that aren't f64 or u64 by using f64 as the ABI value, choosing an out-of-range sentinel for None for each type (e.g. None::<u32> becomes NaN, None::<f32> becomes Some(f64::max_value()), etc)
I'm not sure what the best option is here, but I'm curious what @fitzgen thinks of this too!

Other approaches are possible, yes. But implementing manually means that it's possible to do it better, more compact (like I do with optional i8, u8, i16 and u16 types, using a single u32 argument/return type everywhere). And we don't have too many primitives.
Is passing (and converting) float significantly cheaper than passing 2 integers / integer and 32-bit float?

True yeah! I personally like the idea of using more compact representations as well, and I think using u32 where possible is a great example of that.
In terms of cost I'm not actually sure, but I'd imagine that it's pretty negligible for wasm-bindgen's purposes

I don't have any concrete work in progress, so don't block this on me!
Regarding blanket vs targeted impls: I also doubt that there is observable overhead to putting a discriminant on the global stack. But targeted impls mean that we have to write many impls instead of a single one. I suspect that we will want to move to a blanket impl eventually. But it is also an implementation detail that can be changed at a later date.

I think it's now implemented for all of the primitive types.

Thanks so much @afdw!


Statistics: Separate chart name and chart in course statistics to fix wrong line break issue

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I followed the coding and design guidelines.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Motivation and Context

This is a PR to solve issue #6192
Description

The issue stems from the fact that on some screen sizes the chart name takes up less space than a word in width. Reducing font size doesn't make much sense(screenshot 2) but separating chart name and chart is a straightforward way(screenshot 3).
Steps for Testing

Prerequisites:

1 Instructor

Log in to Artemis
Navigate to Course Statistics
Check the chart names and charts are responsive

Review Progress

Performance Review

[x] I confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[x] Test 1
[ ] Test 2

Screenshots

issue:

reduce the font size:

separate:

Looks good on ts5


Remove emojis from core?

Currently djot includes a giant table of emoji aliases so it can do substitutions for :smile:.
While this is undoubtedly useful for some purposes, I wonder if it would be better implemented as an optional filter.
It should be relatively easy to create an emoji filter -- performance would have to be tested.

Another problem with emojis is that their set changes over time. So, there's (theoretical) forward compatibility hazard with :emoji_which_will_exist_in_2025:
To clarify, is this about removing just the emoji table (so, the user still can write :smile:, it's just that it doesn't get replaced) or about remoting the :ident: syntax from djot?

Thinking about this a bit more, a case could be made for redesignating the emoji element as something more general-purpose, which could be resolved to emojis but could be put to another use.  E.g. special.
We have extensible containers for blocks, inlines, verbatim block, verbatim inline.  But we don't have an extensible leaf node -- this could be it.

This is a good idea but please note my comment at https://github.com/jgm/djot/issues/44#issuecomment-1215075532 that {:some text:} should probably also be supported, and that a decimal or hexadecimal number should be allowed between the colons as probably being the best way of representing arbitrary characters by codepoint.

https://github.com/kitsunies/emoji.lua seems to be a nice emoji library.
We could remove our djot.emoji module and instead either

handle emojis using a filter that uses this rock, or
make emoji support optional in the HTML renderer and depend on this rock if it is selected

The tests would no longer contain resolved emojis.  Either way, we could compile the support into the web playground (amalg.lua will include the module if it's installed and you ask it to).

Let me copy my thoughts about emoji notation from #175 here.
I don't think emoji notation is not necessary because

If we want to write emoji characters, it is possible to write them in the document. For example, if I want to write a dog emoji, I can write 🐶 instead of :dog: directly in the text.
Emoji notation requires readers to map symbols to the actual emoji on their memory when they read the document in plain text. But it is not easy because there are so many emoji characters these days.
For parsers, it is not easy to parse emoji symbols. As djot parser does, a parser must maintain the list of emoji symbols. However, they need to be updated constantly (e.g. new Unicode version bump).
It is actually not possible to map all emoji characters to simple emoji symbols. (e.g. emoji modifiers like skin tone 👍🏻, compound emojis like 👪)
Some emoji symbols are confusing. For example, according to Emojipedia 🚶🏼♂ is :walking_man: on GitHub and :man-walking: on Slack. It's not easy to remember which one is correct for users so parsers need to support the both patterns. But supporting both patterns makes the emoji symbols list bigger and messy.
Adding dedicated notation increases the language's complexity. If removing the notation, : character will be free and a parser will get simpler.

@rhysd's excellent points boils down to: 😉 for all intents and purposes is plain text just like a, b and c.


Requests aggregation for heatmaps.

@skenmy Do you mind having s5 (request aggregation) infra part of the s3 module? Fine by me, we can refactor later on easily.


add Task#TimeoutSeconds{,Path}

Overview:
When there is an issue with the resource name, kubernetes runs forever.
I added timeout support to handle these issues
Highlights:

Runner#output,status uses cached value after the container stops running.
Runner#mark_status lets Task override the status
add Task#TimeoutSeconds
add Task#TimeoutSecondsPath

update:

fixed syntax error in timeoutpath section (refactoring FTW)

update:

fixed hashrocket

@agrare Could you verify the first 2 commits.

Is it true that we only want to ask for the output after the task is complete?
If this is not true, then we need another way to change the runner context to state that there is an error / cause.
Even if that was true, do we want to set those values in the context, or do you feel setting the Error, Cause in the context are better
Does it make sense to have context more consistent with a tristate success (true, false, nil), Error, Cause, and Output column?

Due to the stubbing, it is a little tricky to test these values

WIP: want to discuss the first bullet "caching" before merging
Other than that, I'm happy with these changes

I rebased.
WIP: need to validate this on all 3 runtimes
WIP: need to determine where timeout lives (in runtime or task)
WIP: if it does belong in Task, need to determine the best way to override the runtime.


Address missing options for running commands on computes

Refactor the code to remove repeated sections.

LGTM. Be nice to use run_compute_cmd to run geopmread and geopmwrite rather than:
https://github.com/geopm/geopm/blob/95f1b9959eefe2000dbba6576c0d254c60f00c5f/integration/experiment/util.py#L96-L132

Yeah, I'm still looking, but there's no easy way to do this.
run_compute_cmd() requires a launcher to be created before it can be called.  Switching those util functions for read/write around to use run_compute_cmd() is still going to involve some hoop jumping like what's in allocation_node_test() to create the right launcher (SLURM vs. APRUN...) via injecting things into the argv that's passed along.
The only line I see changing after all of that is the launcher.run(...) line (changing to run_compute_cmd()) and that doesn't really buy us anything.


Implement .well-known/core option for the coap server node

I actually think this is a crucial feature (which is also very relevant for my own intended use-cases). I will to implement this.

Gotcha. Just didn't want to leave my backlog for you. But if you think it's useful then sure.
Feb 1, 2021, 21:03 by<EMAIL_ADDRESS>
I actually think this is a crucial feature (which is also very relevant for my own intended use-cases). I will to implement this.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, > view it on GitHub https://github.com/JKRhb/node-red-contrib-coap/issues/2#issuecomment-770841037> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AAYLVWCRZ7HVCEAUJQKQHN3S42RBDANCNFSM4AURIP6A> .

Gotcha. Just didn't want to leave my backlog for you. But if you think it's useful then sure.

Ah, I see! Thank you for this and for your support in general :)


atlauncher: init at <IP_ADDRESS>

Description of changes
This is an alternative launcher for Minecraft; similar to a bunch of others like PrismLauncher.
Homepage: https://atlauncher.com/
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

I am unsure how do I add a desktop icon for this package. I'm using KDE Plasma and do not see this package on my app menu. I have referred to this thread to no avail.

I am unsure how do I add a desktop icon for this package. I'm using KDE Plasma and do not see this package on my app menu. I have referred to this thread to no avail.

makeDesktopItem + copyDesktopItems
there are many examples over nixpkgs

BTW in nixpkgs we prefer to package from source code if possible, if not me someone else would say this

makeDesktopItem + copyDesktopItems
there are many examples over nixpkgs

I've added a few lines for the same but the icon still does not load. I am assuming I'm doing something blatantly wrong?

BTW in nixpkgs we prefer to package from source code if possible, if not me someone else would say this

I started off with building from source at first; switched to the jar solely because of errors. I will try again as a refactor after this PR, if that works.

The icon doesn't load because it's not found. You can copy a PNG to a specific folder (ex: [1]) or reference an icon downloaded from the Internet by using fetchurl for example.
The first approach is better because in the future an icon pack can override the default icon.
If the project has no icon, you can try using a generic one such as java or another default [2].
[1] https://github.com/NixOS/nixpkgs/blob/6e56adb22679971dfe9343f713786f9cb89b83da/pkgs/applications/office/trilium/desktop.nix#L62
[2] https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html

Noted for the future. For now, I'm using fetchurl.

Only one thing left in this PR, it's that I need to default the running of this package with steam-run. Working on it!

Hey, drupol. Thanks for considering the binary build; I'll make sure I send another refactor PR building from source in some time.

Awesome, thanks ! Looking forward to review it!


Alpine

After Listen.moe and Tohru, Commando is also getting Alpine-ifyed :)
On image disk size :
Old: 1010 MB
New: 230 MB
Reduction: 780 MB saved
Tested it with my Discord server and it seems to work the way it should, still have not received my SoundCloud API key so can not test every feature.

You are on 🔥 man. Such dedication.

hehe, I am done for today ^-^


Add price/volume sentiment feature

Description
Actual trading flow can be used to determine external/market sentiment towards individual tickers.

Specifics

[ ] research price/volume-based sentiment analysis strategies
[ ] build sentiment calculator (potentially an in-memory algorithm/function not a hosted service)
[ ] add get_market_sentiment method to feature package (likely utilizing above algorithm)
[ ] add sentiment generator to feature generation script/update storage logic
[ ] manually test small scale feature/signal performance
[ ] retrain/redeploy model with updated features

Hey, @forstmeier - here's a feature to review!

Closing in favor of moving to ad hoc Google Doc


Publish on Modrinth newer versions

The modrinth project need to update.
The CurseMaven only holding id on files instead of version number that isn't readable.

The uptake of Lootr on Modrinth is extremely minimal compared with CurseForge and, until I get uploads working alongside CurseForge, manual updates will take a while.
That said, you can simply view the available files on CurseForge, select the one you want and then copy the file ID from that page for CurseMaven.

There are 388K on Modrinth. Hmm

and, until I get uploads working alongside CurseForge, manual updates will take a while.

Make sense

There are 388K on Modrinth. Hmm

For comparison, the previous single version for Fabric for 1.20 available on CurseForge had almost 300k downloads from mid-February until now, versus 388k total on Modrinth.

As of 1.21's Architectury-based multiproject, builds are now being published on both CurseForge and Modrinth.


[WFLY-13086] Upgrade gson from 2.8.2 to 2.8.5

Issue: https://issues.redhat.com/browse/WFLY-13086
Downstream dependency to align with Runtimes versions
Changes: https://github.com/google/gson/compare/gson-parent-2.8.2...gson-parent-2.8.5

@ehsavoie could you review please?

Jaeger client is on 2.8.6. Why not going all the way to 2.8.6 ?

@ehsavoie I was going by downstream version, if it's OK to go to most recent version I can update the PR

@spyrkob Please go to 2.8.6. The only use of this lib is Jaeger and the pom of the 0.34.3 version we use specifies 2.8.6 so WF should match.


Fix webhook conflict that occurs when reinstalling after the default installation has failed

Please provide a description of this PR:
This is a supplement to https://github.com/istio/istio/pull/48700, covering the last missing case regarding webhook conflict. This fix is to ignore the in-cluster istio-sidecar-injector webhook in webhook analysis if the installation is a default one, as it will be deactivated upon successful installation. Otherwise if that webhook is activated due to failed installation before, which applied the webhook manifest and didn't do ProcessDefaultWebhook, the installation can still be conflict.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
91e0360c01c066436c0d211cbd1d8c7affd92d52
link
true
/test release-notes

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

/test release-notes

@istio/wg-networking-maintainers PTAL, thanks

In response to a cherrypick label: new pull request created: #49478


samples: sensor: qdec: Run sample on nrf54h20

Add overlay file that enables sample on nrf54h20 Application core.

FYI: @nika-nordic @anangl @kl-cruz @nordic-piks


Generate CI config for openshift-knative/serverless-operator

Fixes https://issues.redhat.com/browse/SRVCOM-2846
Should be merged after https://github.com/openshift-knative/serverless-operator/pull/2380
Features:

Invividual tests can specify the following:

onDemand execution
ignoreError - this equals to "optional" in the final Prow job (tests don't have to pass before merging PR)
whether to generate Cron job for the test or not
runIfChanged pattern

The repository can specify patterns for Dockerfiles instead of the default openshift/ci-operator/knative-images.* and openshift/ci-operator/knative-test-images.*. The serverless-operator repo has Dockerfiles in different locations.
Individual OpenShift versions under branch can specify their own Cron pattern (previously it was for the whole branch)
OnDemand jobs can also be enforced for all jobs related to given OpenShift versions (for s-o we want that because all jobs for older OpenShift version are on demand, we don't run them for every PR)
It is possible to specify image promotion namespace in the config yaml

Example CI configs generated by the code from this branch can be found in https://github.com/openshift/release/pull/45448 (the tests won't pass until https://github.com/openshift-knative/serverless-operator/pull/2380 is merged but I previously executed the tests against my own branch in https://github.com/openshift/release/pull/45380)

https://github.com/openshift-knative/hack/actions/runs/6850738345/job/18625506091?pr=84
other than that, good for me now :)

@ReToCode Fixed. Thanks


API request: Set relative zoom level of webview

Currently, all webviews use the same zoom level as all VSCode views. Sometimes this is not ideal, it can make the content in the webview look comically large. This API request would hopefully make things look less comical.
The ask is an API to let webviews set a relative scaling factor. If VScode is zoomed to 125%, I want an API that would let me specify that my content should only be at 100% zoom. This would be a scaling factor of 0.8
100 / 0.8 = 1.25 = 125%

One might argue that you can accomplish something similar using the CSS scale transform. However using a transform negatively impacts font rendering. The only way to scale content without affecting font rendering is to use electron's native zoom API

Zoom is currently designed to zoom the entire editor. I don't think allowing webviews to override this is a good idea as some users may need webview content to be displayed at a larger size


Added contacttracing.app

Read the contribution guidelines please.

If you want to contribute, note that you should only update data/*.json.


called Option::unwrap() on a None value

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (a44aa13 2023-01-09T00:04:40.069116Z)
What command(s) is the bug in?
forge test --contracts ./src/test/Optimism_exp.sol -vvv
Operating System
macOS (Intel)
Describe the bug
To reproduce please execute forge test --contracts ./src/test/Optimism_exp.sol -vvv at https://github.com/SunWeb3Sec/DeFiHackLabs
Thanks.
Here the bug log:
2023-01-09T13:16:15.412630Z ERROR sharedbackend: Failed to send/recv basic err=GetAccount(0x0000000000000000000000000000000000000000,
(code: -32000, message: missing trie node af4866f7567d0d82a7d63fbfcf799b080f096055229690edfddbde3ddf3bfb65 (path ), data: None)) address=0x0000000000000000000000000000000000000000
The application panicked (crashed).
Message:  called Option::unwrap() on a None value
Location: /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/revm-2.3.1/src/evm_impl.rs:285
This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: __mh_execute_header
at :
2: __mh_execute_header
at :

missing trie node af4866f7567d0d82a7d63fbfcf799b080f096055229690edfddbde3ddf3bfb65

this is likely an issue with the RPC that failed to return the data

closing as this is

missing trie node

which means the endpoint you're using lacks the requested data


Doesn't transition to type: "content" on close

Actually does it on open
https://github.com/onet-team/onet/blob/4a9b0a41d004e3b7adea80a7529d0e40051e216b/src/histore/__init__.py#L160-L162

Changes to content regardless if any content written


Maintained?

@maxcountryman  First, Thank you for the excellent plugin.
I was planning to use this extension instead of rolling out my own but I noticed numerous open PRs and open issues. Is this repo still maintained?

Hi, the plugin is maintained although I haven’t had the time to merge in many PRs lately. If you need a release we can arrange that otherwise you can always pin a git sha.

No worries, I'll use it instead of writing my own then! Thank you for the quick response


show-selection-container is not Customizable [ Feature Request ]

There should be option for customizing the show-selection-container, the only customization which I have seen is to show selected items below search placeholder or above that. But there should be option either to hide that 'show-selection-container' part or to change the css completely.

Hi @puneet24 ,
to hide the selection container you may simply use CSS:
.sol-selection-container {
   display: none;
}

All SOL elements have CSS classes defined which allow you to customize them to your needs. Or am I missing your point? Please let me know which concrete customizations you need.
Cheers
Patrick

Simply hiding that part is not good solution, it is not cost effective
There should be options kind of parameter in sol object for this type of
configuration and apart from that it should take more parameters for
customizing the complete css of select Box
On Mar 3, 2016 4:33 PM, "pbauerochse"<EMAIL_ADDRESS>wrote:

Hi @puneet24 https://github.com/puneet24 ,
to hide the selection container you may simply use CSS:
.sol-selection-container {
display: none;
}
All SOL elements have CSS classes defined which allow you to customize
them to your needs. Or am I missing your point? Please let me know which
concrete customizations you need.
Cheers
Patrick
—
Reply to this email directly or view it on GitHub
https://github.com/pbauerochse/searchable-option-list/issues/26#issuecomment-191708711
.


How to change the LSTMCell weight format from tensorflow to tf.keras

I I have some old code from tensorflow that I want to make work for tensorflow2/tf.keras. I would like to keep the same LSTM weights, but cannot figure out how to convert the format.
I have the old weights saved in a checkpoint file, and also have them saved in csv files.
My old code looks something like this:
input_placeholder = tf.placeholder(tf.float32, [None, None, input_units])
lstm_layers = [tf.nn.rnn_cell.LSTMCell(layer_size), tf.nn.rnn_cell.LSTMCell(layer_size)]
stacked = tf.contrib.rnn.MultiRNNCell(lstm_layers)
features, state = tf.nn.dynamic_rnn(stacked, input_placeholder, dtype=tf.float32)

And my new code looks something like this:
input_placeholder = tf.placeholder(tf.float32, [None, None, input_units])
lstm_layers = [tf.keras.layers.LSTMCell(layer_size),tf.keras.layers.LSTMCell(layer_size)]
stacked = tf.keras.layers.StackedRNNCells(lstm_layers)
features = stacked(input_placeholder)
... #later in the code
features.set_weights(previous_weights)

The old bias seems to match the new bias. The old kernel seems to be the concatenation of the kernel and recurrent kernel. I am able to load the previous_weights into the model (have explicitly checked the weights loaded correctly), however tests I have fail to produce the same result. Digging into the source code, the kernels seem to have a different format under the hood.
Is it possible to calculate the kernel and recurrent_kernel (tf.keras) using these old saved kernel weights?
Links if they're helpful:
https://github.com/tensorflow/tensorflow/blob/r1.13/tensorflow/python/ops/rnn_cell_impl.py
https://github.com/tensorflow/tensorflow/blob/r1.13/tensorflow/python/keras/layers/recurrent.py

@5M7k0R5tTe Please fill the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Along with the template, please provide as many details as possible to find the root cause of the issue. Thanks!

@5M7k0R5tTe, the tf lstm cell has two weights: kernel, bias. and keras cell has 3 weights: kernel, recurrent_kernel, bias. The tf kernel should be the concat of keras kernel and recurrent kernel.
Format wise, tf lstm cell was using IFCO (input, forget, carry, output) gate order, and Keras cell was using ICFO (input, carry, forget, output). So to convert the weights, assume each gates has size U, it will be:
i, f, c, o = np.split(tf_weights, 4, axis=1)
keras_weights = np.concatenate([i, c, f, o], axis=1)

@qlzh727 , thanks for the clarification. However, it almost looks like TF LSTMCell uses icfo, and keras LSTM uses ifco, as opposite to what you described?
The source is: current tf2onnx handles TF LSTMCell (see code here) and the lstm rewriter assumes that the weights and bias are in icfo, prior to conversion to ONNX format, which is iofc.
Please correct me if wrong. I am confused after reading tf2onnx code and this thread. Thanks.

oh, yes. Thanks for spotting the error in my previous message. The keras weight format is IFCO, and TF format was ICFO.
You can find the keras logic for weights in https://github.com/keras-team/keras/blob/353cb10af7c0c7d435b31129c5970fcabe3fc961/keras/layers/recurrent.py#L2468

@qlzh727 , thanks for the clarification. However, it almost looks like TF LSTMCell uses icfo, and keras LSTM uses ifco, as opposite to what you described?
The source is: current tf2onnx handles TF LSTMCell (see code here) but not keras LSTM as of now. Under this case, the lstm rewriter treats that the weights and bias as in icfo format. Only then, it's converted to ONNX format which is iofc.
Therefore, my understanding on default gate order is: TF LSTM: ICFO keras LSTM: IFCO ONNX LSTM: IOFC
Please correct me if wrong. I am confused after reading tf2onnx code and this thread. Thanks.


feat: port CategoryTheory.Equivalence

This is missing slice_lhs which is only used in two proofs though.
Update: slice_lhs (and other slice tactics) have now been ported

[x] depends on: #2109

In my understanding, by obviously should be replaced by by aesop_cat.

Okay I pushed the port as far as I could now. There is still a couple of issues remaining of course:

the slice_lhs tactic is missing so some lemmas are not proven
the symm calls in the file dont work for some reason despite operating on equality if I am seeing that correctly
some simp calls don't work either, this might be because some other lemmata in the file are still not proven or other reasons I'm not sure.
towards the end of the file there is a bunch of slightly confusing stuff with instances that I'd like to take a look at when the above things are fixed.

Current status:

now depends on slice PR #2109
aesop_cat looking good so far
slice_lhs now sliceLHS and working
added a Trans Iso Iso Iso to use calc for a lemma
@[refl] complaining and one proof that seems actual thought

All green now.

This PR/issue depends on:

leanprover-community/mathlib4#2109
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#2109
By Dependent Issues (🤖). Happy coding!

@semorrison So we can merge this now I guess right?

Thanks :tada:
bors merge


Document hoisting semantics

Right now, this example prints 106:
z = 3
f = x -> x + y + z
y = 5
z = 100

println (f 1)  --  106

z is marked as resolved and f captures its reference, so it later evaluates to 100 when f is called. y is properly hoisted such that it evaluates to 5 in the closure.
Instead, this should be a compile time failure since z is marked as immutable by f's capture.
Discord thread: https://discordapp.com/channels/651996477333438474/730624907607539722/904815689154564227

Thanks for taking the time to put this in! Aside from hoisting, we need to document the semantics of mutability and immutability in Passerine, especially the concept of 'local mutability.' Maybe now would be a good time to start building out the Codex?
Here's a brief rundown of what should happen:

Variables are mutable in the scope in which they are defined, i.e. while on the stack.-- this is valid
x = 5
x = 4

Function calls are pass-by-value. Mutating a function parameter makes a copy[^1] and does not effect the original value:f = x -> { x = 2; x }
y = 7
f y -- is 2
y -- is 7

Closures are capture-by-value. Mutating a captured value (inside or outside the closure) is a compile-time error:-- compile-time error:
x = 7
f = () -> { x = 2; x }
-- also:
x = 7
f = () -> x
x = 2

Variables may be shadowed:x = 7
f = x -> { x = 2; x } -- shadowed
f 7 -- is 2
x -- is 7

This is just a brief overview, I think we should provide more examples in the documentation. I'd like to include a method for closures to capture by reference in trivial cases, i.e. closures that do not escape the scope in which they are defined. I'd also like a way to introduce variables guaranteed to be immutable, through something like let x = ....
[1]: Pass-by-value does not always cause an actual copy to occur because of FBiP due to Vaporization. In the case of last-use, the original value is passed and may be mutated:
mutate_first = list -> { list[0] = 0; list }

big_list = [ ... ]
big_list = mutate_first big_list -- last use of big_list
print big_list -- no copies have been made


VM stops when using virtio-fs and cache=none

Description of problem
When running certain commands in a Kata container that uses virtio-fs and virtio_fs_cache = "none", the virtiofsd process quits and the VM/sandbox is recreated.
I've experienced this when running the following commands:

apt-get update
apt-get install <any package>
(there may be more, but I can reliably get this to happen with the above commands).

Expected result
For commands to complete successfully when running inside a Kata container using virtio-fs and virtio_fs_cache = "none".
Actual result
The following pod spec can be used to replicate:
apiVersion: v1
kind: Pod
metadata:
  name: test
  namespace: default
  annotations:
    io.kubernetes.cri.untrusted-workload: "true"
spec:
  containers:
    - image: ubuntu:18.04
      imagePullPolicy: Always
      name: test
      command:
        - sleep
        - "3600"

Once the pod is running, exec in and run the command:
$ kubectl exec -it test bash
# apt-get update
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
# the console output freezes at this point and the pod is restarted

Listing pods we can see the pod has restarted
NAME          READY   STATUS    RESTARTS   AGE
test   1/1     Running   1          25m

With enable_debug=true, we can see the following logs in containerd/kata:
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757017446Z" level=debug msg="fv_queue_thread: elem 0: with 2 out desc of length 80" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757033995Z" level=debug msg="unique: 14652, opcode: READ (15), nodeid: 76, insize: 80, pid: 147" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757050997Z" level=debug msg="lo_read(ino=76, size=4096, off=0)" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757066919Z" level=debug msg="virtio_send_data_iov: count=1 len=4096 iov_len=16 " ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757083091Z" level=debug msg="virtio_send_data_iov: elem 0: with 3 in desc of length 4112" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757100029Z" level=debug msg="virtio_send_data_iov: after skip skip_size=0 in_sg_cpy_count=2 in_sg_left=4096" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757122993Z" level=debug msg="virtio_send_data_iov: preadv_res=4096 len=4096" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757139553Z" level=debug msg="fv_queue_thread: Waiting for Queue 1 event" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757156210Z" level=debug msg="fv_queue_thread: Got queue event on Queue 1" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757172521Z" level=debug msg="fv_queue_thread: Queue 1 gave evalue: 1 available: in: 24 out: 94" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757191212Z" level=debug msg="fv_queue_thread: elem 0: with 3 out desc of length 94" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757207621Z" level=debug msg="fv_queue_thread: Write special case" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757223526Z" level=debug msg="unique: 14653, opcode: WRITE (16), nodeid: 83, insize: 80, pid: 147" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757267104Z" level=debug msg="lo_write(ino=83, size=14, off=0)" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757283379Z" level=debug msg="   unique: 14653, success, outsize: 24" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757300097Z" level=debug msg="virtio_send_msg: elem 0: with 2 in desc of length 24" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757317520Z" level=debug msg="fv_queue_thread: Waiting for Queue 1 event" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757336008Z" level=debug msg="fv_queue_thread: Got queue event on Queue 1" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757353054Z" level=debug msg="fv_queue_thread: Queue 1 gave evalue: 1 available: in: 24 out: 81" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757370543Z" level=debug msg="fv_panic: libvhost-user: virtio: invalid address for buffers" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtiofsd subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757389818Z" level=info msg="virtiofsd quits" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtcontainers subsystem=qemu
Jul 24 06:54:53 ip-10-149-77-57.us-west-2.compute.internal containerd[23267]: time="2019-07-24T06:54:53.757411504Z" level=info msg="Stopping Sandbox" ID=dd71d7f25480beae21e0eee6a4e4b766c7d4783db752c6bbd865b494a93d3e84 source=virtcontainers subsystem=qemu

It looks like virtiofsd has quit, and kata has stopped the sandbox. Virtiofsd seems to have paniced - fv_panic: libvhost-user: virtio: invalid address for buffers

Show kata-collect-data.sh details

Meta details
Running kata-collect-data.sh version 1.8.0 (commit 31b8cb3fbc7b1de9c94201aed7c54ddb73e97587) at 2019-07-24.07:22:06.769436156+0000.

Runtime is /opt/kata/bin/kata-runtime.
kata-env
Output of "/opt/kata/bin/kata-runtime kata-env":
[Meta]
  Version = "1.0.23"

[Runtime]
  Debug = true
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  Path = "/opt/kata/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.8.0"
    Commit = "31b8cb3fbc7b1de9c94201aed7c54ddb73e97587"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/etc/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "virt"
  Version = "NEMU (like QEMU) version 4.0.0 (kata-static)\nCopyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers"
  Path = "/opt/kata/bin/nemu-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false
  SharedFS = "virtio-fs"

[Image]
  Path = "/opt/kata/share/kata-containers/kata-containers-ubuntu-console-1.8.0-9e0a061.img"

[Kernel]
  Path = "/opt/kata/share/kata-containers/vmlinuz-4.19.52-45"
  Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket agent.log=debug agent.log=debug"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.8.0-7cd620094df16486c19b2c20300f9847a94c23af"
  Path = "/opt/kata/libexec/kata-containers/kata-proxy"
  Debug = true

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.8.0-bc65ea8385a09611054d95b5dbc8f858f87c3d7a"
  Path = "/opt/kata/libexec/kata-containers/kata-shim"
  Debug = true

[Agent]
  Type = "kata"
  Debug = true
  Trace = false
  TraceMode = ""
  TraceType = ""

[Host]
  Kernel = "4.19.50-coreos-r1"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Container Linux by CoreOS"
    Version = "2135.4.0"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz"

[Netmon]
  Version = "kata-netmon version 1.8.0"
  Path = "/opt/kata/libexec/kata-containers/kata-netmon"
  Debug = true
  Enable = false

Runtime config files
Runtime default config files
/etc/kata-containers/configuration.toml
/opt/kata/share/defaults/kata-containers/configuration.toml

Runtime config file contents
Output of "cat "/etc/kata-containers/configuration.toml"":
# Copyright (c) 2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration-nemu.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

# nemu utilizes the 'qemu' hypervisor template type, since it closely matches qemu
[hypervisor.qemu]
path = "/opt/kata/bin/nemu-system-x86_64"
kernel = "/opt/kata/share/kata-containers/vmlinuz.container"
image = "/opt/kata/share/kata-containers/kata-containers.img"
machine_type = "virt"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = "agent.log=debug"

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = "/opt/kata/share/kata-nemu/OVMF.fd"

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Shared file system type:
#   - virtio-fs (default)
#   - virtio-9p
shared_fs = "virtio-fs"

# Path to vhost-user-fs daemon.
virtio_fs_daemon = "/opt/kata/bin/virtiofsd-x86_64"

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "none"

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
enable_hugepages = false

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent (no proxy is started).
# Default true
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# Default false
#enable_template = true

# Specifies the path of template.
#
# Default "/run/vc/vm/template"
#template_path = "/run/vc/vm/template"

# The number of caches of VMCache:
# unspecified or == 0   --> VMCache is disabled
# > 0                   --> will be set to the specified number
#
# VMCache is a function that creates VMs as caches before using it.
# It helps speed up new container creation.
# The function consists of a server and some clients communicating
# through Unix socket.  The protocol is gRPC in protocols/cache/cache.proto.
# The VMCache server will create some VMs and cache them by factory cache.
# It will convert the VM to gRPC format and transport it when gets
# requestion from clients.
# Factory grpccache is the VMCache client.  It will request gRPC format
# VM and convert it back to a VM.  If VMCache function is enabled,
# kata-runtime will request VM from factory grpccache when it creates
# a new sandbox.
#
# Default 0
#vm_cache_number = 0

# Specify the address of the Unix socket that is used by VMCache.
#
# Default /var/run/kata-containers/cache.sock
#vm_cache_endpoint = "/var/run/kata-containers/cache.sock"

[proxy.kata]
path = "/opt/kata/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
enable_debug = true

[shim.kata]
path = "/opt/kata/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = true

[agent.kata]
# If enabled, make the agent display debug-level messages.
# (default: disabled)
enable_debug = true

# Enable agent tracing.
#
# If enabled, the default trace mode is "dynamic" and the
# default trace type is "isolated". The trace mode and type are set
# explicity with the `trace_type=` and `trace_mode=` options.
#
# Notes:
#
# - Tracing is ONLY enabled when `enable_tracing` is set: explicitly
#   setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing`
#   will NOT activate agent tracing.
#
# - See https://github.com/kata-containers/agent/blob/master/TRACING.md for
#   full details.
#
# (default: disabled)
#enable_tracing = true
#
#trace_mode = "dynamic"
#trace_type = "isolated"

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/opt/kata/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="tcfilter"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

# Enabled experimental feature list, format: ["a", "b"].
# Experimental features are features not stable enough for production,
# They may break compatibility, and are prepared for a big version bump.
# Supported experimental features:
# 1. "newstore": new persist storage driver which breaks backward compatibility,
#				expected to move out of experimental in 2.0.0.
# (default: [])
experimental=[]

Output of "cat "/opt/kata/share/defaults/kata-containers/configuration.toml"":
# Copyright (c) 2017-2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration-qemu.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/opt/kata/bin/qemu-system-x86_64"
kernel = "/opt/kata/share/kata-containers/vmlinuz.container"
image = "/opt/kata/share/kata-containers/kata-containers.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = ""

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Shared file system type:
#   - virtio-9p (default)
#   - virtio-fs
shared_fs = "virtio-9p"

# Path to vhost-user-fs daemon.
virtio_fs_daemon = "/opt/kata/bin/virtiofsd-x86_64"

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "always"

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
#enable_hugepages = true

# Enable file based guest memory support. The default is an empty string which
# will disable this feature. In the case of virtio-fs, this is enabled
# automatically and '/dev/shm' is used as the backing folder.
# This option will be ignored if VM templating is enabled.
#file_mem_backend = ""

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
#enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# Default false
#enable_template = true

# Specifies the path of template.
#
# Default "/run/vc/vm/template"
#template_path = "/run/vc/vm/template"

# The number of caches of VMCache:
# unspecified or == 0   --> VMCache is disabled
# > 0                   --> will be set to the specified number
#
# VMCache is a function that creates VMs as caches before using it.
# It helps speed up new container creation.
# The function consists of a server and some clients communicating
# through Unix socket.  The protocol is gRPC in protocols/cache/cache.proto.
# The VMCache server will create some VMs and cache them by factory cache.
# It will convert the VM to gRPC format and transport it when gets
# requestion from clients.
# Factory grpccache is the VMCache client.  It will request gRPC format
# VM and convert it back to a VM.  If VMCache function is enabled,
# kata-runtime will request VM from factory grpccache when it creates
# a new sandbox.
#
# Default 0
#vm_cache_number = 0

# Specify the address of the Unix socket that is used by VMCache.
#
# Default /var/run/kata-containers/cache.sock
#vm_cache_endpoint = "/var/run/kata-containers/cache.sock"

[proxy.kata]
path = "/opt/kata/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[shim.kata]
path = "/opt/kata/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
#enable_debug = true

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = true

[agent.kata]
# If enabled, make the agent display debug-level messages.
# (default: disabled)
#enable_debug = true

# Enable agent tracing.
#
# If enabled, the default trace mode is "dynamic" and the
# default trace type is "isolated". The trace mode and type are set
# explicity with the `trace_type=` and `trace_mode=` options.
#
# Notes:
#
# - Tracing is ONLY enabled when `enable_tracing` is set: explicitly
#   setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing`
#   will NOT activate agent tracing.
#
# - See https://github.com/kata-containers/agent/blob/master/TRACING.md for
#   full details.
#
# (default: disabled)
#enable_tracing = true
#
#trace_mode = "dynamic"
#trace_type = "isolated"

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/opt/kata/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
#enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="tcfilter"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

# Enabled experimental feature list, format: ["a", "b"].
# Experimental features are features not stable enough for production,
# They may break compatibility, and are prepared for a big version bump.
# Supported experimental features:
# 1. "newstore": new persist storage driver which breaks backward compatibility,
#				expected to move out of experimental in 2.0.0.
# (default: [])
experimental=[]

Config file /usr/share/defaults/kata-containers/configuration.toml not found

KSM throttler
version
Output of " --version":
./kata-collect-data.sh: line 178: --version: command not found

systemd service
Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-07-22T00:55:25.248493513+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "bionic"
  version: "18.04"
  packages:
    default:
      - "systemd,iptables,init,chrony,fuse,bash"
    extra:
      - "bash"
      - "fuse"
agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.8.0-3195c3e48c50dc835ab84d6b4ced397659369fb8"
  agent-is-init-daemon: "no"

Initrd details
No initrd

Logfiles
Runtime logs
No recent runtime problems found in system journal.
Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.
Throttler logs
No recent throttler problems found in system journal.

Container manager details
Have docker
Docker
Output of "docker version":
Client: Docker Engine - Community
 Version:           18.09.7
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        2d0083d
 Built:             Thu Jun 27 17:54:15 2019
 OS/Arch:           linux/amd64
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Output of "docker info":
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
CollectMode=inactive

No kubectl
No crio
Have containerd
containerd
Output of "containerd --version":
containerd github.com/containerd/containerd v1.2.0-575-gb99a66c2 b99a66c267d04740628634d7d038f9ce1753b339

Output of "systemctl show containerd":
Type=simple
Restart=always
NotifyAccess=none
RestartUSec=5s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=23267
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Wed 2019-07-24 06:20:50 UTC
ExecMainStartTimestampMonotonic=4687037607
ExecMainExitTimestampMonotonic=0
ExecMainPID=23267
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStartPre={ path=/opt/bin/containerd-init.sh ; argv[]=/opt/bin/containerd-init.sh ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStart={ path=/opt/containerd/bin/containerd ; argv[]=/opt/containerd/bin/containerd --log-level=debug --config=/etc/containerd/config.toml ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=2700111872
CPUUsageNSec=[not set]
TasksCurrent=262
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=73727
IPAccounting=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=2063281
LimitSIGPENDINGSoft=2063281
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=-999
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=containerd.service
Names=containerd.service
Requires=sysinit.target system.slice
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=multi-user.target shutdown.target
After=kata-init.service systemd-journald.socket containerd-devicemapper-init.service sysinit.target basic.target system.slice
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/etc/systemd/system/containerd.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Wed 2019-07-24 06:20:50 UTC
StateChangeTimestampMonotonic=4687037656
InactiveExitTimestamp=Wed 2019-07-24 06:20:48 UTC
InactiveExitTimestampMonotonic=4684555132
ActiveEnterTimestamp=Wed 2019-07-24 06:20:50 UTC
ActiveEnterTimestampMonotonic=4687037656
ActiveExitTimestamp=Wed 2019-07-24 06:20:48 UTC
ActiveExitTimestampMonotonic=4684545051
InactiveEnterTimestamp=Wed 2019-07-24 06:20:48 UTC
InactiveEnterTimestampMonotonic=4684552864
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2019-07-24 06:20:48 UTC
ConditionTimestampMonotonic=4684553489
AssertTimestamp=Wed 2019-07-24 06:20:48 UTC
AssertTimestampMonotonic=4684553489
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=4c91603e75244e8daaad521179e42ec8
CollectMode=inactive

Output of "cat /etc/containerd/config.toml":
[grpc]
address = "/run/containerd/containerd.sock"
uid = 0
gid = 0

[plugins]
  [plugins.cri.containerd]
    snapshotter = "overlayfs"
    [plugins.cri.containerd.default_runtime]
      runtime_type = "io.containerd.runtime.v1.linux"
      runtime_engine = "/usr/bin/runc"
      runtime_root = ""
    [plugins.cri.containerd.untrusted_workload_runtime]
      runtime_type = "io.containerd.kata.v2"

[plugins.cri]
  max_container_log_line_size = 262144

[plugins.linux]
  shim = "/opt/containerd/bin/containerd-shim"
  runtime = "runc"

[plugins.cri.registry]
  [plugins.cri.registry.mirrors]
    [plugins.cri.registry.mirrors."docker.io"]
       endpoint = []

Packages
No dpkg
No rpm

i tested this last night and any amount of disk IO on a virtio-fs backed folder works just fine. writing a 1G file or reading bits of random files in rootfs. apt update though triggers an error and I was unable to get a solid trace. Any thoughts @stefanha? Guessing the version of virtio-fs needs to be caught up.

Nice find @ganeshmaharaj with the dax setting!


Improved , Save Preset and Load Preset Buttons with animation And also Improve the FeedBack Form

Description
I have Improve  the Save Preset and Load Preset Buttons with Cool and Funky Aniamtions and Also Updated the old FeedBack Form to new Elegant Animated Form , I hope You will review my PR and assign this issue to me under GSSOC24.
Video
https://github.com/sk66641/Random-Disco-Light-Simulator/assets/114290748/bbc936f3-36df-483a-80e5-fb87eeae1666
Images
BEFORE

AFTER

@sk66641

@sk66641 please checkout this PR

@sk66641 please checkout this PR

@AbheetHacker4278
Read #guidelines!

@AbheetHacker4278
Read #guidelines!

Please mention the problem , so i can fix it

@sk66641 okay  , now i understand , so do i wait for my issue is been reviewed or delete this PR

@sk66641 i want to do PR under GSSOC24

@AbheetHacker4278
Keep the changes for the new feedback form & remove the changes for Save preset and Load preset button
And there is an issue in your feedback form, clicking on the submit button without filling any info makes it invisible

@AbheetHacker4278
Keep the changes for the new feedback form & remove the changes for Save preset and Load preset button
And there is an issue in your feedback form, clicking on the submit button without filling any info makes it invisible

Okay,  till tommorow i will fix this issue and i acknowledge your review very serious,  thanks for this review 😊

@sk66641 please check the feedback form , i have done necessary changes

@AbheetHacker4278
The background gets change after submitting the feedback form, i have attached a video for the reference
...
https://github.com/sk66641/Random-Disco-Light-Simulator/assets/145834771/d28bde97-074f-402c-8626-226c2eae3b4e

https://github.com/sk66641/Random-Disco-Light-Simulator/assets/114290748/4580bede-5f67-4903-ab5c-8e0d5fdfaca4

@AbheetHacker4278
It's good practice to link the PR to the issue. It was #289.


get_brep_part_properties doesnt exist

The function get_brep_part_properties doesn't exist anymore. If you would like the same print out as the readme file example it requires the function  get_part_properties_from_file.

Thanks for reporting. I thought I had fixed this bug, can I check which version you are using

could you run conda list and let me know the output please

brep_part_finder          0.5.2

That is great, you have the latest version there.
There are a few other packages that I would be keen to konw the version number of
paramak
cad_to_dagmc
brep_to_h5m

paramak  0.8.7
cad_to_dagmc  0.1.3
brep_to_h5m  0.4.2
Also thanks for the quick response

latest versions all around. Thanks for that.
I have updated the readme now. The function name got changed to get_part_properties_from_file
If you are happy this issue is resolved could you close this issue