Get Relevant Machine Info for Setting CPU Affinities

Problem Description
Currently, we are just getting the total number of CPUs, as shown in the snippet below:
https://github.com/AdoptOpenJDK/TKG/blob/84b082615e8cf443f3ce07e2eea9a334dbd8f52e/src/org/openj9/envInfo/MachineInfo.java#L32
In order to set affinities, we need the following info:

Number of Logical Cores
Number of Physical Cores
Number of Numa Nodes
Threads Per Core

Besides number of physical cores, we can directly get everything from lscpu. We have multiple ways of calculating number of physical cores. One of them can be: CPU(s)/ Thread(s) per core.
For example, looking at the CPU info for a Power machine which has SMT-8:

Number of Logical Cores = 160
Number of Physical Cores = 160/8 = 20
Number of Numa Nodes = 2
Threads Per Core = 8

lscpu
Architecture:          ppc64le
Byte Order:            Little Endian
CPU(s):                160
On-line CPU(s) list:   0-159
Thread(s) per core:    8
Core(s) per socket:    10
Socket(s):             2
NUMA node(s):          2
Model:                 1.0 (pvr 004c 0100)
Model name:            POWER8NVL (raw), altivec supported
CPU max MHz:           4023.0000
CPU min MHz:           2061.0000
L1d cache:             64K
L1i cache:             32K
L2 cache:              512K
L3 cache:              8192K
NUMA node0 CPU(s):     0-79
NUMA node1 CPU(s):     80-159

Other Relevant Snippet
https://github.com/AdoptOpenJDK/TKG/blob/84b082615e8cf443f3ce07e2eea9a334dbd8f52e/src/org/openj9/envInfo/EnvDetector.java#L75-L84
Proposed Changes
Add the support to fetch that info in https://github.com/AdoptOpenJDK/TKG/blob/master/src/org/openj9/envInfo/
Related Issues

Ability to Set CPU Affinities for Benchmarking (https://github.com/AdoptOpenJDK/openjdk-tests/issues/1587)

Added support for this in https://github.com/AdoptOpenJDK/openjdk-tests/pull/1917.


STS Media Inc

Leading Commercial real Estate promoters

Leading Commercial real Estate promoters

This author doesn't seem to be updating this component, but you can look at similar components that implement SSR PROMISE asynchronous loading，github address ：https://github.com/qq281113270/react-lazy-router-dom


Load SVG files with esbuild's api.LoaderText with in js.Build

On my site I've got a custom color theme selector, and I've got a Preact element where I'd like to inline an SVG so I can apply styles to it, and make it responsive to CSS custom properties. This is currently achieved using a custom Figure component:
// Figure.tsx

import { FunctionComponent } from "preact";

export const Figure: FunctionComponent<{ svg: string }> = ({ svg }) => {
  // This "color-responsive-svg" class adds a number of selectors for the paths, etc within the svg to
  // make them response to various css custom properties, and then the actual SVG file gets inlined
  // here as a child element.
  return (
    <figure class="color-responsive-svg" dangerouslySetInnerHTML={{ __html: svg }} />
  );
};

Below, using the component like so doesn't work. You'll get something akin to JSBUILD: failed to transform "ts/index.tsx" (text/tsx): "my-icon.svg:1:0": Unexpected "<"
// NavModal.tsx

import { Figure } from "./Figure";
import myIcon from "./my-icon.svg";

export const NavModal: FunctionComponent = () => {
  return (
    <Figure svg={myIcon} />
  );
};

If you switch the file extension to .txt, you can import the file and render it as expected. This looks like it's because ".svg" is currently not supported in the extensions array: https://github.com/gohugoio/hugo/blob/master/resources/resource_transformers/js/options.go#L134
It looks like loading SVG as text is the documented approach for using this in ESBuild, and that seems like a nice default to me.

Has this been fixed?

From what I understand @zmsy the solution to this is to add ".svg":  api.LoaderText here:
https://github.com/gohugoio/hugo/blob/master/resources/resource_transformers/js/options.go#L134
Note that any JavaScript ESBuild plugins you find on the interweb is not relevant for Hugo.

@bep  I think I may have missed some few pointer in the contributing guidelines. I wish to correct them and make subsequent adequate changes that fixes this issue.

@bep Have you had time to go through my edited commit? It seems I have passed all the checks to make a successful commit/PR.


RAT-390 migrate exclusion config - (Harmonize Part 6)

Fixes for RAT-390, RAT-416, RAT-417, RAT-418
Moved exclusion calculations from plugin to core which involved refactoring and reimplementing to better fit into the design.
Largest changes are:

Code in apache-rat-plugin that dealt with inclusion and exclusion of files to process was moved into the core o.a.r.config.exclusion package and its sub packages.  All of the inclusion and exclusion processing is handled by the ExclusionProcessor.   The exclusion package is the largest change in the codebase as it is both in core (where things are added) and plugin (where things are removed).
A DocumentNameMatcher interface is defined in the o.a.r.document.impl package.  implementations of this class are used in the filtering process.
A DocumentName class has been created in o.a.r.document.impl package.  The name is associated with all Documents.  The document name tracks both the fully qualified path to the file on the file system as well as the base directory that the file was referenced from.  This class is where filenames are localized to the directory where rat starts it's scan.  A lot of the churn in this PR is to push the DocumentName into the Document across the codebase.
The Plexus code that we use to match file patterns has be copied into o.a.r.config.exclusion.plexus .  These files have been modified from their original.
An o.a.r.utils.iterator package has been added.  It contains extended iterator code from Apache Jena that is slightly modified to fit our needs.  This code allows us to use iterators in ways similar to streams but without the overhead.
Added more tests.

The changes seem to have induced test irregularities .... not sure if you spot the cause, @Claudenw ?
https://github.com/Claudenw/creadur-rat/actions/runs/11262029997/job/31316786387
The changes are really great (still reviewing/reading) :)

@Claudenw kudos for this great work! Let us see how downstream users benefit from this new and enhanced functionality.


REQUEST: deploy prow for Docs SIG

GitHub Repo Name
@pingcap/docs, @pingcap/docs-cn, @pingcap/docs-tidb-operator, @pingcap/docs-dm
Which plugins do you want to deploy
We want to deploy all plugins except ti-community-blunderbuss. (please don't auto-assign reviewers)
We also want to customize a plugin:

require-matching-label: require a translation/xxx label for each PR.

Requirements

[x] I have carefully read the instructions for the plugin I want to use.
[x] I agree to leave the plugin configuration to be maintained by sig-ti-community-infra.

TODO

[ ] @ti-community-infra/sig-community-infra  Add the requested plugin configuration
[ ] @ti-community-infra/sig-community-infra  Add repository admin to Robots
[ ] @ti-community-infra/sig-community-infra  Turn off the old robot function

I'll be working on this next week.

@hi-rustin Any update on this?

@hi-rustin Any update on this?

I'm really sorry, I was really busy last week, I will help you deploy it by tomorrow at the latest.


Add test cases for NacosMetadataReport

What is the purpose of the change
Add test case for NacosMetadataReport
Brief changelog

Add test cases for  "doSaveMetadata","removeServiceMetadata","doGetExportedURLs","doSaveSubscriberData"
Modify codes in NacosMetadataReportTest

Verifying this change

All test cases pass for NacosMetadataReportTest

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #5776 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #5776      +/-   ##
============================================
+ Coverage     61.17%   61.29%   +0.11%
- Complexity      471      496      +25
============================================
  Files           926      979      +53
  Lines         37843    38823     +980
  Branches       5461     5569     +108
============================================
+ Hits          23152    23798     +646
- Misses        12179    12401     +222
- Partials       2512     2624     +112

Impacted Files
Coverage Δ
Complexity Δ

...g/context/properties/DefaultDubboConfigBinder.java
0% <0%> (-100%)
0% <0%> (ø)

...t/annotation/DubboLifecycleComponentRegistrar.java
0% <0%> (-100%)
0% <0%> (ø)

...ache/dubbo/rpc/cluster/support/ForkingCluster.java
0% <0%> (-100%)
0% <0%> (ø)

.../context/properties/AbstractDubboConfigBinder.java
0% <0%> (-92.31%)
0% <0%> (ø)

...ring/context/config/DubboConfigBeanCustomizer.java
0% <0%> (-66.67%)
0% <0%> (ø)

...che/dubbo/rpc/cluster/support/FailfastCluster.java
50% <0%> (-50%)
0% <0%> (ø)

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
0% <0%> (-38.47%)
0% <0%> (ø)

...ache/dubbo/remoting/transport/AbstractChannel.java
37.5% <0%> (-37.5%)
0% <0%> (ø)

...ava/org/apache/dubbo/common/utils/MethodUtils.java
54.16% <0%> (-17.27%)
0% <0%> (ø)

.../org/apache/dubbo/rpc/model/ServiceRepository.java
63.63% <0%> (-14.42%)
0% <0%> (ø)

... and 176 more

Continue to review full report at Codecov.

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


Links to Data Releases broken?

From the public site I was not able to get the Data Releases URLs to work:
https://civic.genome.wustl.edu/#/releases
e.g.
https://civic.genome.wustl.edu:3000/downloads/nightly/GeneSummaries.tsv
https://civic.genome.wustl.edu:3000/downloads/01-May-2015/GeneSummaries.tsv

I think this is a dupe of #97


Knative install instructions use default namespace

Please describe your use case / problem.
I want to use Ambassador with Knative with system components (e.g. Ambassador) separated from user components.
Describe the solution you'd like
Ambassador components live in a separate namespace (e.g. ambassador)
Describe alternatives you've considered
ambassador-system 😉
Additional context
https://knative.dev/development/install/knative-with-ambassador/

Fix at https://github.com/knative/docs/pull/1893

Fix not merged yet

Fixed


nixos manual: segment into pages

At the moment we have one unnavigable large page.
This pull request puts each chapter into a separate file.
The idea solution would be to have a navigation side-bar were only
first-level chapters are shown (or even a page search like sphinx).
However docbook seems to be too inflexible to do that.
Is there a way to get nicer looking templates like the guix manual has?
https://www.gnu.org/software/guix/manual/guix.html
Update the template used on the website would be already enough.

Splitting into separate pages will also help the google indexation as large pages get ranked down

There was a discussion about this earlier when the switch was made to a single page https://github.com/NixOS/nixpkgs/issues/7607.

Most projects offer single page and multi page for good reason as well as multiple formats (PDF/HTML)

I'd definitely prefer both single-page and multi-page versions being available (as was mentioned above), as an arbitrary example: https://www.gnu.org/software/bison/manual/

Having two version would increase the build time twice. I would like avoid that, because I have to build the manual, whenever service options are changed.


ERROR Not enough space on volume 1 to backup @docker -- "Free: 0 GB"

I was trying to move my Container Manager package over from my existing volume1 to my new nvme volume2 tonight, and keep running into this issue.
It appears that it's trying to call du with volume1 instead of /volume1 when called from the backup_extras method... You can see below that the call to check_space from process_packages is passing in /volume2, where the call from backup_extras is passing in volume1 without the leading forward slash.
I confirmed that attempting to run df --output=avail "volume1" fails, while running df --output=avail "/volume1" succeeds.
jeff@synology01:/$ sudo -s /volume1/scripts/Synology_app_mover-3.0.39/syno_app_mover.sh -t
Password:
Synology_app_mover v3.0.39
DS920+ DSM 7.2.1-69057-3

Running from: /volume1/scripts/Synology_app_mover-3.0.39/syno_app_mover.sh

1) Move
2) Backup
3) Restore
Select the mode: 1
You selected Move

cdir called from main
skip_dev_tools called from main
...
skip_dev_tools called from main
[Installed package list]
 1) /volume1  Advanced Media Extensions
 2) /volume1  Container Manager
 3) /volume1  Hyper Backup
 4) /volume1  Log Center
 5) /volume1  Node.js v14
 6) /volume1  Node.js v16
 7) /volume1  Node.js v18
 8) /volume1  PHP 7.4
 9) /volume1  PHP 8.0
10) /volume1  PHP 8.2
11) /volume1  Plex Media Server
12) /volume1  Storage Analyzer
13) /volume1  Synology Application Service
14) /volume1  Synology Drive Server
15) /volume1  Synology Office
16) /volume1  Synology Photos
17) /volume1  Tailscale
18) /volume1  Universal Viewer
Select the package to move: 2
You selected Container Manager in /volume1

Destination volume is /volume2

Ready to Move Container Manager to /volume2? [y/n]
y

stop_packages called from main
package_status called from stop_packages
process_packages called from main
check_space called from process_packages
$1: /volume1/@docker
$2: /volume2
folder_size called from check_space
vol_free_space called from check_space
vol_free_space parm: /volume2
vol_free_space free:<PHONE_NUMBER>
Do you want to backup the @docker folder on volume1? [y/n]
y
check_space called from backup_extras
$1: /volume1/@docker
$2: volume1
folder_size called from check_space
vol_free_space called from check_space
vol_free_space parm: volume1
WARNING Not enough space to move  /volume1/@docker to /volume2
Free: 0 GB  Needed: 109 GB

ding called from backup_extras
ERROR Not enough space on volume1 to backup @docker!
Do you want to continue moving Container Manager? [y/n]
n

Thanks. I've releases a new version that fixes that bug.
https://github.com/007revad/Synology_app_mover/releases/tag/v3.0.40
I'm impressed that you found and used the -t option.

Updated to 3.0.40 and was able to move Container Manager successfully to the new volume.
I'm having a follow up issue with running the Update available updater from the Image tab, but I can open a separate issue for that.


Publish package on dart pub

Seems https://pub.dev/packages/kollections available.

Okokok! Will do it ASAP, thanks for pushing me :D

The package is published. Thanks again!


How to check if a channel is closed?

In Go, I can check if a channel is closed by doing this.
ch := make(chan bool)
close(ch)
v, ok := <- ch
if !ok { // channel is closed
}

When I do a similar think in anko, I get an error: undefined symbol 'v'.
ch = make(chan bool)
close(ch)
v, ok = <- ch // error: undefined symbol 'v'

Is there a way to check if a channel is closed in anko?

Sorry, this works as expected.


LIO-SAM Coordinate definition

Coordinate definition in LIO-SAM

As shown in VLP Lidar user manual, its coordinate is x-right, y-forward, z-up. The coordinate used in LIO_SAM is x-forward, y-left, z-upward.
Do we need to perform some axis switch operation to unify the coordinate?

In function. projectPointCloud(); I find that the laserCloudIn’s coordinates (x,y,z) is directly given to thisPoint.
thisPoint.x = laserCloudIn->points[i].x;
thisPoint.y = laserCloudIn->points[i].y;
thisPoint.z = laserCloudIn->points[i].z;

Do we need to do some declaration to let the ROS system know that the coordinate used in code is REP-105?

When call the function pcl::getTransformation() to derive the rotation matrix, does the rotation matrix denote the transformation between (forward-left-upward) and North-West-Up? A little confused that we can have various coordinate definitions which lead to different rotation matrix, do we need to let the PCL lib or ROS system know the coordinate definition ahead?

As per discussed in website https://www.ros.org/reps/rep-0103.html
REP-103 describes the relationship between axes. i.e.,
In relation to a body the standard is:
x forward
y left
z up
Is it a typo in the document of REP-105 which should be REP-103??

@ygfwqqz please read  README.md file carefully.

@ygfwqqz please read README.md file carefully.

I do not think you understand my question carefully or understand the coordinate definition carefully.


Use the setup script for venv setup

Update readme.md

LGTM, but nit: can we add transformers as well for miniLM and other HF models?

done


NOT an issue but...

can I use this library with standard arduino and other servos?
I am experiencing some jittering on the servos too, when using WIRE...etc on the Mega.
I can't find info about the using of timers and interrupts on the servo standard library.
Nice boards btw on your site!

i found this library and seems working fine: http://arduiniana.org/libraries/pwmservo/


knex.js - non-basic subtract operation on select clause

Hello all,
I am trying to make next to execute the following query:
select "NAME", "COUNT(*) - COUNT(NULLIF('STATUS', 'ERROR'))" as "countFailed", ...
The main issue is about the subtract operation in the select clause
I haven't found anything in the guides concerning how can it be done

I am familiar with the option to use count, however, it seems that it supports only very basic plain column as a parameter.
I'd like to refrain from using raw (Yeah - I know it's an option)

Does anyone have a clue?

Without raw this is currently not possible.
knex.select(['NAME', knex.raw("COUNT(*) - COUNT(NULLIF('Status', 'ERROR')) as \"countFailed\"").wrap('(', ')')]).toString();
//select "NAME", (COUNT(*) - COUNT(NULLIF('Status', 'ERROR')) as "countFailed")
```

.query(function (query) {
query.select(knex.raw(` (SELECT available_leave_days from leave_trackers)`)) -
(knex.raw(`SELECT ((DATEDIFF(${end_date}, ${start_date}) + 1) -
(WEEK(${end_date}) - WEEK(${start_date})) -
(case when weekday(${end_date}) = 6 then 1 else 0 end) -
(SELECT IFNULL(sum(total), 0)
from
(
SELECT count(holidays.date) as total
FROM holidays, leave_applications
WHERE holidays.date between ${start_date} and ${end_date}
GROUP BY holiday_id) as holiday_leave
)
) as available_days
FROM leave_applications
group by leave_apply_id
)) AS total_available_leave_days`)))

I want to do this query in knex and its not working fine for me as I guess '-' in between queries is problem, can someone help me to convert this properly?, thanks!

query.column(knex.raw('((select leave_trackers.available_leave_days from leave_trackers) - (select ((DATEDIFF(?, ?) + 1) - (WEEK(?) - WEEK(?)) - (case when weekday(?) = 6 then 1 else 0 end) - (SELECT IFNULL(sum(total), 0) from (select count(holidays.date) as total FROM holidays WHERE holidays.date between ? and ? && holidays.location_id = ?) as holiday_leave )) AS total_available_days)) AS total_available_leave_days',
                                            [saveLeave.attributes.end_date, saveLeave.attributes.start_date, saveLeave.attributes.end_date,
                                            saveLeave.attributes.start_date, saveLeave.attributes.end_date, saveLeave.attributes.start_date, saveLeave.attributes.end_date, locId]
                                        ))

Solved it, thanks! 👍


[ADD] add to show result of imported but not declared in requirements

The option '--diff' will only show the modules declared in requirements but not imported in code, sometimes we also may need to check the modules has imported but not declared.

Coverage decreased (-1.7%) to 70.0% when pulling 1e448f9b203b80081c1b9b21550fca04a7563ade on spenly:master into 5707a39df693ddd243ddd7c47ff35ce66d25a6c6 on bndr:master.

Coverage decreased (-1.7%) to 70.0% when pulling 1e448f9b203b80081c1b9b21550fca04a7563ade on spenly:master into 5707a39df693ddd243ddd7c47ff35ce66d25a6c6 on bndr:master.

Coverage decreased (-1.7%) to 70.0% when pulling 1e448f9b203b80081c1b9b21550fca04a7563ade on spenly:master into 5707a39df693ddd243ddd7c47ff35ce66d25a6c6 on bndr:master.

Coverage decreased (-1.7%) to 70.0% when pulling 1e448f9b203b80081c1b9b21550fca04a7563ade on spenly:master into 5707a39df693ddd243ddd7c47ff35ce66d25a6c6 on bndr:master.


Not displaying red badge for unread messages in Office 365 Outlook Web App

When receiving new unread mails/messages in my configured Office 365 Outlook Web App service, NO red badge icon is displayed for this service. The service properly detects incoming mails and displays corresponding system notification, but NO red badge icon is displayed.
I'm using Franz in my Desktop with following configuration:

OS: Ubuntu 18.04
Browser: Chrome  72.0.3626.81 (Official Build) (64-bit)

+1 to this. When switched to "New Outlook" notifications aren't working and the calendar opens in a new window.

I have the same issue. But when I go back to the old ui, It also don't work.
No more notification for outlook 365

I went back to the "Old Outlook" UI and my Franz notifications came back. (OSX)

What about the desktop's notifications? I can't manage to see them.

I'm not getting the badge or any notifications with the new outlook.

There is no such option to switch to the old Outlook, making notifications definitely not working :(

I looked at how Franz actually looks for the number of unread messages, and I hacked a way to fix it. I'm no javascript expert so I know that it's not the best (I get the text of a div and split it around), but heh, it works.
First, open .config/Ferdi/recipes/office365-owa/webview.js
Then change the const unreadMail for the following atrocity:
   const unreadMail = parseInt(jQuery("div[title*='Inbox']").first().text().split("Inbox")[1].split("unread")[0], 10);

Not sure if it's any better, but I took a kick at the can after seeing your comment:
const unreadMail = parseInt(jQuery("div[title*='Inbox'] > span > span").first().contents().first().text(), 10);

@strigona-worksight it looks better, thanks! I never used jQuery before trying to fix this ;-)

I'm far from a jQuery expert. I tracked down the repo for this recipe and there's an outstanding PR to get this fixed: https://github.com/adambirds/recipe-office365-owa/pull/10

Yeah pretty sure the author isn't updating it since my PR there is almost a year old. Maybe this is due for a takeover.  I see your note on my PR there @strigona-worksight - I'll apply your fix to my PR at least. 🤷♂

Latest commit 254f289 on Oct 23, 2017

Yeah....

Ahh I have spread the conversation all over the place.. sorry. I have submitted an updated fork to Franz: https://github.com/meetfranz/plugins/issues/435

try this...
https://acompli.helpshift.com/a/outlook-mac/?s=troubleshooting&f=i-am-not-getting-new-email-notifications-after-upgrading-to-macos-catalina

I have the same problem with Windows 10 OS


Find the plugin's main class regardless of the package

Description
Ensure that the tool can find the plugin's main class regardless of the Android package name.
Related Issues
Fixes https://github.com/flutter/flutter/issues/42661
Tests
I added the following tests: Unit test in plugin_test.dart
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

Adding @amirh for plugin/platform changes

I don't think the tool should look for the plugin's class in any other package than the one specified. If there's a mismatch in the spec it's a plugin bug and the tool should fail.


Feature/start date warning

This fix for #352 seems like a good candidate to go straight to acceptation. It doesn't touch anything critical, but the wording could use a good look-over by @djhcapel.
Current state: Intended start date warning is always shown in the form. When input is actually within two weeks of today, the warning turns red. On the submission page the warning is only shown when relevant, with a link back to the first page.

Did you use a formatter tool? And is that tool set to use 2 spaces instead of 4?
Sorry if I'm nagging, but we use 4 spaces everywhere and the reformat now adds 2 spaced indentation everywhere...

Yes the two spaces are intentional. IMO four spaces is too much for HTML.

IMO I think two spaces are hard to read. So we disagree on that point.
I'm very willing to discuss switching indentation project wide, but I don't think it's a good idea to just switch one file in an indentation-unrelated PR. (Especially as my editor will just switch back to four spaces the next time I edit that file, causing more commit-gore).
That discussion aside, was the removal of indentation around Django tags (if/with/blocktrans/etc) intentional as well?


fix(): macaddress.one() should return a Promise

The implementation of Promise support was incorrect. I recommend adding unit tests because this PR:

broke the TypeScript support (fixed here)
was incorrectly implemented
the app will break for previous versions of node, because Promise does not exist

.one() should return a Promise
.one('eth0), should return a Promise
.one(callback) should return void and use the callback
.one('eth0', callback) should return void and use the callback

Thank you for the pull request! Gonna release as 0.4.2

Released as https://github.com/scravy/node-macaddress/releases/tag/0.4.2


Make validation options more flexible

(valid) = true implies (required) = true.
We need to make it possible to override this behavior with (required) = false. This includes the case when (valid) = true is implied (e.g. via (when), (max), etc.).

Currently, (valid) = true does not imply (required) = true. Also, no validation options imply (valid) = true.


Babylon JS Version 6.0.0 Typescript Declarations Fail

When compiling using TSC 4.9.5 i am getting an error with the new Babylon.d.ts:

@MackeyK24 can you confirm if our next release is all good with you ? and reopen if not ?


Bridging not working in Kata running in ACRN VM

Description of problem
a) Install ACRN v1.6.1 (acrn-2020w18.4-140000p) on Ubuntu 18.04.4 as documented in this tutorial.
b) Set up Kata containers on ACRN by following this tutorial.
c) The kata-manager installs version 1.11.0-rc0 as of writing.
d) Run a Kata container using ACRN VM, for example sudo docker run -ti --runtime=kata-runtime busybox sh, and check the networking inside the container is working?
Expected result
The networking of the Kata container should be bridged to the host.
Actual result

Show kata-collect-data.sh details

Meta details
Running kata-collect-data.sh version 1.11.0-rc0 (commit ) at 2020-06-11.09:41:50.152514120+0800.

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

[Runtime]
  Debug = false
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  SandboxCgroupOnly = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    OCI = "1.0.1-dev"
    [Runtime.Version.Version]
      Semver = "1.11.0-rc0"
      Major = 1
      Minor = 11
      Patch = 0
      Commit = ""
  [Runtime.Config]
    Path = "/etc/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = ""
  Version = "DM version is: 1.6-2020w18.4.140000p_284 (daily tag:acrn-2020w18.4.140000p), build by mockbuild@2020-04-30 02:27:43"
  Path = "/usr/bin/acrn-dm"
  BlockDeviceDriver = "virtio-blk"
  EntropySource = "/dev/urandom"
  SharedFS = ""
  VirtioFSDaemon = ""
  Msize9p = 0
  MemorySlots = 10
  PCIeRootPort = 0
  HotplugVFIOOnRootBus = false
  Debug = false
  UseVSock = false

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.11.0-rc0_agent_d4df5d96ba.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-<IP_ADDRESS>-47.container"
  Parameters = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = false
  [Proxy.Version]
    Semver = "1.11.0-rc0-a6f5534"
    Major = 1
    Minor = 11
    Patch = 0
    Commit = "a6f5534"

[Shim]
  Type = "kataShim"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = false
  [Shim.Version]
    Semver = "1.11.0-rc0-ad49288"
    Major = 1
    Minor = 11
    Patch = 0
    Commit = "ad49288"

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

[Host]
  Kernel = "5.4.28-PKT-200203T060100Z-00002-gd7da1d772f85"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "Ubuntu"
    Version = "18.04"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz"

[Netmon]
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = false
  Enable = false
  [Netmon.Version]
    Semver = "1.11.0-rc0"
    Major = 1
    Minor = 11
    Patch = 0
    Commit = "<<unknown>>"

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

Runtime config file contents
Output of "cat "/etc/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-acrn.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.acrn]
path = "/usr/bin/acrn-dm"
ctlpath = "/usr/bin/acrnctl"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/share/kata-containers/kata-containers.img"

# 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 acrn uses the default firmware leave this option empty
firmware = ""

# 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 = 1

# 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

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. ACRN only supports virtio-blk.
block_device_driver = "virtio-blk"

# 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

# 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

# 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"

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

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

[shim.kata]
path = "/usr/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 = "/usr/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 (Deprecated)
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#     ***NOTE: This feature has been deprecated with plans to remove this
#     feature in the future. Please use other network models listed below.
#
#
#   - 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="macvtap"

# 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

# if enabled, the runtime will add all the kata processes inside one dedicated cgroup.
# The container cgroups in the host are not created, just one single cgroup per sandbox.
# The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox.
# The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation.
# The sandbox cgroup is constrained if there is no container type annotation.
# See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType
sandbox_cgroup_only=false

# 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:
# (default: [])
experimental=[]

Output of "cat "/usr/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 = "/usr/bin/qemu-vanilla-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/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

# Specifies virtio-mem will be enabled or not.
# Please note that this option should be used with the command
# "echo 1 > /proc/sys/vm/overcommit_memory".
# Default false
#enable_virtio_mem = true

# 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 = "/usr/bin/virtiofsd"

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

# Extra args for virtiofsd daemon
#
# Format example:
#   ["-o", "arg1=xxx,arg2", "-o", "hello world", "--arg3=yyy"]
#
# see `virtiofsd -h` for possible options.
virtio_fs_extra_args = []

# 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 vhost-user storage device, default false
# Enabling this will result in some Linux reserved block type
# major range 240-254 being chosen to represent vhost-user devices.
enable_vhost_user_store = false

# The base directory specifically used for vhost-user devices.
# Its sub-path "block" is used for block devices; "block/sockets" is
# where we expect vhost-user sockets to live; "block/devices" is where
# simulated block device nodes for vhost-user devices to live.
vhost_user_store_path = "/var/run/kata-containers/vhost-user"

# 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

# If false and nvdimm is supported, use nvdimm device to plug guest image.
# Otherwise virtio-block device is used.
# Default is false
#disable_image_nvdimm = 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

# Before hot plugging a PCIe device, you need to add a pcie_root_port device.
# Use this parameter when using some large PCI bar devices, such as Nvidia GPU
# The value means the number of pcie_root_port
# This value is valid when hotplug_vfio_on_root_bus is true and machine_type is "q35"
# Default 0
#pcie_root_port = 2

# If vhost-net backend for virtio-net is not desired, set to true. Default is false, which trades off
# security (vhost-net runs ring0) for network I/O performance.
#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 = "/usr/libexec/kata-containers/kata-proxy"

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

[shim.kata]
path = "/usr/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"

# Comma separated list of kernel modules and their parameters.
# These modules will be loaded in the guest kernel using modprobe(8).
# The following example can be used to load two kernel modules with parameters
#  - kernel_modules=["e1000e InterruptThrottleRate=3000,3000,3000 EEE=1", "i915 enable_ppgtt=0"]
# The first word is considered as the module name and the rest as its parameters.
# Container will not be started when:
#  * A kernel module is specified and the modprobe command is not installed in the guest
#    or it fails loading the module.
#  * The module is not available in the guest or it doesn't met the guest kernel
#    requirements, like architecture and version.
#
kernel_modules=[]

[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 = "/usr/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:
#
#   - 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=tcfilter` 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

# if enabled, the runtime will add all the kata processes inside one dedicated cgroup.
# The container cgroups in the host are not created, just one single cgroup per sandbox.
# The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox.
# The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation.
# The sandbox cgroup is constrained if there is no container type annotation.
# See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType
sandbox_cgroup_only=false

# 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:
# (default: [])
experimental=[]

KSM throttler
version
Output of "/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version":
kata-ksm-throttler version 1.11.0-rc0-ae0fdd0

systemd service
Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2020-04-20T16:06:11.186926495+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "32870"
  packages:
    default:
      - "chrony"
      - "iptables-bin"
      - "kmod-bin"
      - "libudev0-shim"
      - "systemd"
      - "util-linux-bin"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.11.0-rc0-d4df5d96ba10ced41d2d614a35ad6d535be045ba"
  agent-is-init-daemon: "no"

Initrd details
No initrd

Logfiles
Runtime logs
Recent runtime problems found in system journal:
time="2020-06-10T13:36:37.534725328+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T13:36:37.534931909+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.70254939+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/config.json: no such file or directory" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 name=kata-runtime pid=3882 source=virtcontainers
time="2020-06-10T14:01:12.704269156+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.704496981+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.79450014+08:00" level=warning msg="no such file or directory: /run/kata-containers/shared/sandboxes/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/rootfs"
time="2020-06-10T14:01:12.795557342+08:00" level=warning msg="Could not remove container share dir" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 error="no such file or directory" name=kata-runtime pid=3882 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 share-dir=/run/kata-containers/shared/sandboxes/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=virtcontainers subsystem=container
time="2020-06-10T14:01:12.80120647+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/config.json: no such file or directory" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 name=kata-runtime pid=3882 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=virtcontainers
time="2020-06-10T14:01:12.80197238+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.802217092+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.803793736+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/config.json: no such file or directory" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 name=kata-runtime pid=3882 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=virtcontainers
time="2020-06-10T14:01:12.804526223+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:12.80469411+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:13.536699276+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/config.json: no such file or directory" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 name=kata-runtime pid=3882 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=virtcontainers
time="2020-06-10T14:01:13.540063723+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:13.545239263+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:13.557783906+08:00" level=warning msg="sandbox cgroups path is empty" arch=amd64 command=delete container=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 name=kata-runtime pid=3882 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=virtcontainers subsystem=sandbox
time="2020-06-10T14:01:35.214764312+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:45.382030613+08:00" level=warning msg="sandbox's cgroup won't be updated: cgroup path is empty" arch=amd64 command=create container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4052 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers subsystem=sandbox
time="2020-06-10T14:01:45.422000031+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=start container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4283 source=virtcontainers
time="2020-06-10T14:01:45.423379095+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:45.423569863+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:45.425313174+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=start container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4283 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers
time="2020-06-10T14:01:45.425923857+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:01:45.426071584+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.669156255+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4752 source=virtcontainers
time="2020-06-10T14:14:58.670869147+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.671148966+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.763401356+08:00" level=warning msg="no such file or directory: /run/kata-containers/shared/sandboxes/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/rootfs"
time="2020-06-10T14:14:58.764459351+08:00" level=warning msg="Could not remove container share dir" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 error="no such file or directory" name=kata-runtime pid=4752 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 share-dir=/run/kata-containers/shared/sandboxes/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers subsystem=container
time="2020-06-10T14:14:58.770127779+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4752 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers
time="2020-06-10T14:14:58.770859174+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.77102566+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.772619748+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4752 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers
time="2020-06-10T14:14:58.77333799+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:58.773510169+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:59.517025844+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/config.json: no such file or directory" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4752 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers
time="2020-06-10T14:14:59.520103794+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:59.520400481+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-10T14:14:59.537999421+08:00" level=warning msg="sandbox cgroups path is empty" arch=amd64 command=delete container=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 name=kata-runtime pid=4752 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=virtcontainers subsystem=sandbox
time="2020-06-11T09:39:14.05319558+08:00" level=error msg="failed to open file for reading" driver=fs error="open /run/vc/uuid/uuid.json: no such file or directory" file=/run/vc/uuid/uuid.json source=virtcontainers/persist/fs subsystem=persist
time="2020-06-11T09:39:14.053329115+08:00" level=info msg="Load UUID store failed" arch=amd64 command=create container=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc name=kata-runtime pid=2432 source=virtcontainers subsystem=acrn
time="2020-06-11T09:39:14.053925789+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-11T09:39:24.42284489+08:00" level=warning msg="sandbox's cgroup won't be updated: cgroup path is empty" arch=amd64 command=create container=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc name=kata-runtime pid=2432 sandbox=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc source=virtcontainers subsystem=sandbox
time="2020-06-11T09:39:24.474670357+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc/config.json: no such file or directory" arch=amd64 command=start container=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc name=kata-runtime pid=2531 source=virtcontainers
time="2020-06-11T09:39:24.476164168+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-11T09:39:24.476229109+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups
time="2020-06-11T09:39:24.477706298+08:00" level=warning msg="failed to get sandbox config from old store: open /var/lib/vc/sbs/3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc/config.json: no such file or directory" arch=amd64 command=start container=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc name=kata-runtime pid=2531 sandbox=3b0a074ee051c66075130d9a8e7ed99a101ba19aa8ac4f269c99df3c53b9eedc source=virtcontainers
time="2020-06-11T09:39:24.478314772+08:00" level=warning msg="Could not get device information" device=/dev/kvm error="no such file or directory" source=virtcontainers/pkg/cgroups
time="2020-06-11T09:39:24.478386175+08:00" level=warning msg="cgroups have not been created and cgroup path is empty" source=virtcontainers/pkg/cgroups

Proxy logs
Recent proxy problems found in system journal:
time="2020-06-09T17:52:38.046760855+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/227ff69b6eeb37431b7a51d550c16c5c6c45c6cc637a9a25af9df7aeab50298c/kata.sock: use of closed network connection" name=kata-proxy pid=2952 sandbox=227ff69b6eeb37431b7a51d550c16c5c6c45c6cc637a9a25af9df7aeab50298c source=proxy
time="2020-06-09T17:58:21.450558808+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/cafd67234a96b5e91be1143e826a01a199ceefeb5810fbe05f2c7db5a215ba60/proxy.sock: use of closed network connection" name=kata-proxy pid=3023 sandbox=cafd67234a96b5e91be1143e826a01a199ceefeb5810fbe05f2c7db5a215ba60 source=proxy
time="2020-06-09T18:05:49.669961829+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/09f753a4e16d06b8e0e3ef6dffbb858df82f5583609d7ed51a9bf3fc757c10f0/kata.sock: use of closed network connection" name=kata-proxy pid=2623 sandbox=09f753a4e16d06b8e0e3ef6dffbb858df82f5583609d7ed51a9bf3fc757c10f0 source=proxy
time="2020-06-09T19:18:30.425982134+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/30279f5bc7d5e788ace93837bf1e1bf08dee9abdf0fe8d4b3b3269936269b487/kata.sock: use of closed network connection" name=kata-proxy pid=2423 sandbox=30279f5bc7d5e788ace93837bf1e1bf08dee9abdf0fe8d4b3b3269936269b487 source=proxy
time="2020-06-09T19:54:42.289342993+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/24b13519456c77f747a880067a2f5f1d6a82a42cb57208ead3b900c3acbde89e/proxy.sock: use of closed network connection" name=kata-proxy pid=3765 sandbox=24b13519456c77f747a880067a2f5f1d6a82a42cb57208ead3b900c3acbde89e source=proxy
time="2020-06-09T19:59:52.909781215+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b797f10ef242c291a0d3ada811646e124ee9c3fe9d68ba85b98704215ba52197/proxy.sock: use of closed network connection" name=kata-proxy pid=4206 sandbox=b797f10ef242c291a0d3ada811646e124ee9c3fe9d68ba85b98704215ba52197 source=proxy
time="2020-06-09T20:17:14.719499252+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a1415e6bd11052e51966e334cc195a3ebc170535a381dca08bfef5a9d13e124e/kata.sock: use of closed network connection" name=kata-proxy pid=4861 sandbox=a1415e6bd11052e51966e334cc195a3ebc170535a381dca08bfef5a9d13e124e source=proxy
time="2020-06-09T20:33:36.553575386+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/7769df7d75c99569564cd1510039306ab94541d36acba89e3c1724bba11ebb51/kata.sock: use of closed network connection" name=kata-proxy pid=2452 sandbox=7769df7d75c99569564cd1510039306ab94541d36acba89e3c1724bba11ebb51 source=proxy
time="2020-06-09T20:40:50.415250836+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a0362469f529e338731ecff8bde03f3ceb5aba2032ec1174b3619d4ab48582e7/kata.sock: use of closed network connection" name=kata-proxy pid=2445 sandbox=a0362469f529e338731ecff8bde03f3ceb5aba2032ec1174b3619d4ab48582e7 source=proxy
time="2020-06-09T21:23:19.138054453+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/f93345d4c0ded08e44794329e559629159e16d85710e0b520f02efeedfa1deb9/proxy.sock: use of closed network connection" name=kata-proxy pid=2473 sandbox=f93345d4c0ded08e44794329e559629159e16d85710e0b520f02efeedfa1deb9 source=proxy
time="2020-06-09T21:24:07.523641951+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/e7fda5c33c55741630e8f7346b31ea50f5f9fcbea98202f9acd6024234bb4669/proxy.sock: use of closed network connection" name=kata-proxy pid=3025 sandbox=e7fda5c33c55741630e8f7346b31ea50f5f9fcbea98202f9acd6024234bb4669 source=proxy
time="2020-06-09T21:25:35.826589333+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/22ad7f31b888e1254bae0e0c276a89a66387fba3ed224a64d918bc4f341c74c2/kata.sock: use of closed network connection" name=kata-proxy pid=3347 sandbox=22ad7f31b888e1254bae0e0c276a89a66387fba3ed224a64d918bc4f341c74c2 source=proxy
time="2020-06-09T21:26:19.349662821+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/f97f19875e437dfd3c77ca3d7b49f460c3e01354f618475b5f7428c4f2db7fb3/kata.sock: use of closed network connection" name=kata-proxy pid=3659 sandbox=f97f19875e437dfd3c77ca3d7b49f460c3e01354f618475b5f7428c4f2db7fb3 source=proxy
time="2020-06-09T23:38:53.939196597+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/86e19c544aef276bd325e8a1fc97edad2765da09169852df89c8a2a4e673c87c/kata.sock: use of closed network connection" name=kata-proxy pid=3071 sandbox=86e19c544aef276bd325e8a1fc97edad2765da09169852df89c8a2a4e673c87c source=proxy
time="2020-06-10T14:01:12.808301245+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0/kata.sock: use of closed network connection" name=kata-proxy pid=2485 sandbox=159a53a0e66b4028a40b4fe5ce034b226235d09ea0f36efe0464254c74d867c0 source=proxy
time="2020-06-10T14:14:58.77686887+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5/kata.sock: use of closed network connection" name=kata-proxy pid=4247 sandbox=ce57bc35101f67aa9921bfc209d87514e0f5ce66db1d35ab6f41acf8e47cf9f5 source=proxy

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:
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        369ce74a3c
 Built:             Fri Feb 28 23:45:43 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.6
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       369ce74a3c
  Built:            Wed Feb 19 01:06:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.3.3-0ubuntu1~18.04.2
  GitCommit:
 docker-init:
  Version:          0.18.0
  GitCommit:

Output of "docker info":
Client:
 Debug Mode: false

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 3
 Server Version: 19.03.6
 Storage Driver: devicemapper
  Pool Name: docker-8:2-2236520-pool
  Pool Blocksize: 65.54kB
  Base Device Size: 10.74GB
  Backing Filesystem: ext4
  Udev Sync Supported: true
  Data file: /dev/loop8
  Metadata file: /dev/loop9
  Data loop file: /var/lib/docker/devicemapper/devicemapper/data
  Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
  Data Space Used: 512.8MB
  Data Space Total: 107.4GB
  Data Space Available: 46.75GB
  Metadata Space Used: 17.81MB
  Metadata Space Total: 2.147GB
  Metadata Space Available: 2.13GB
  Thin Pool Minimum Free Space: 10.74GB
  Deferred Removal Enabled: true
  Deferred Deletion Enabled: true
  Deferred Deleted Device Count: 0
  Library Version: 1.02.145 (2017-11-03)
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: kata-runtime runc
 Default Runtime: kata-runtime
 Init Binary: docker-init
 containerd version:
 runc version: N/A
 init version:
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.4.28-PKT-200203T060100Z-00002-gd7da1d772f85
 Operating System: Ubuntu 18.04.4 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 14.73GiB
 Name: nuc7i5bnh
 ID: ZEVE:R64C:HPUN:GKOZ:KW2J:YLNS:GRXP:63SI:BRTG:LZUF:V2SN:6DEO
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: the devicemapper storage-driver is deprecated, and will be removed in a future release.
WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
         Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.

No rpm

thanks @ttzeng for raising this, @vijaydhanraj do you have any idea about this ?

yes working with @amshinde on this debug.

Thanks @vijaydhanraj , I confirm this commit solves the issue. Thanks for the fix.


A bit (~5%) faster Rust

------- assembly (nasm) ---------
NASM version 2.16.01 compiled on Mar 18 2023
602489
2289
---- c native (opt-level=3) -----
gcc (GCC) 12.2.1 20230201
602489
2617ms
--- c++ native (opt-level=3) ----
g++ (GCC) 12.2.1 20230201
602489
2297ms
--- rust native (opt-level=3) ---
rustc 1.69.0 (84c898d65 2023-04-16)
Finished release [optimized] target(s) in 0.00s
602489
2375ms
-------------- go ---------------
go version go1.20.3 linux/amd64
602489
2630ms

Too match complexity for 5%.
All other languages handles with single source code file without any other config files and stuff.
What do you thing? should I merge it?


[Bug] (file cache) IOContext should not be saved in class CachedRemoteFileReader

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
master
What's Wrong?
Query id, ReaderType, FileCacheStatistics and so on are saved in IOContext，CachedRemoteFileReader save the IOContext in  class.  The call stack for creating CachedRemoteFileReader is as follows：
#7  0x00007f9ad9e29d89 in doris::io::RemoteFileSystem::open_file_impl (this=0x7f9946225000, path=..., reader_options=..., reader=0x7f98a7f855a0, io_ctx=0x0)
    at /home/disk2/doris/be/src/io/fs/remote_file_system.cpp:60
#8  0x00007f9ad9e29658 in doris::io::RemoteFileSystem::open_file (this=0x7f9946225000, path=..., reader_options=..., reader=0x7f98a7f855a0, io_ctx=0x0)
    at /home/disk2/doris/be/src/io/fs/remote_file_system.cpp:32
#9  0x00007f9ada7c9ac4 in doris::segment_v2::Segment::open (fs=..., path=..., segment_id=0, rowset_id=..., tablet_schema=..., reader_options=..., output=0x7f98a7f856d0)
    at /home/disk2/doris/be/src/olap/rowset/segment_v2/segment.cpp:53
#10 0x00007f9adacdecf7 in doris::BetaRowset::load_segments (this=0x7f99e4343b80, seg_id_begin=0, seg_id_end=1, segments=0x7f98a7f85890)
    at /home/disk2/doris/be/src/olap/rowset/beta_rowset.cpp:146
#11 0x00007f9adacde54e in doris::BetaRowset::load_segments (this=0x7f99e4343b80, segments=0x7f98a7f85890) at /home/disk2/doris/be/src/olap/rowset/beta_rowset.cpp:127
#12 0x00007f9adac6e545 in doris::SegmentLoader::load_segments (this=0x7f9b1e1a5be0 <doris::SegmentLoader::create_global_instance(unsigned long)::instance>, rowset=...,
    cache_handle=0x7f9a65e6cc20, use_cache=true) at /home/disk2/doris/be/src/olap/segment_loader.cpp:76

This cause if use segment cache in memory, may be multi query use the same CachedRemoteFileReader, and IOContext may be not true, may be multi query calculate cache statistic base on the same FileCacheStatistics object. So I don't think we need to save IOContext in class CachedRemoteFileReader.
What You Expected?
Remove IOContext in class CachedRemoteFileReader, and pass IOContext when calling the function CachedRemoteFileReader::read_at().
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This problem will be solved in #17586, close this issue.


etcd on the master should only be accessible from localhost

Forked from #129.
Right now it binds to <IP_ADDRESS>.

@roberthbailey Is the goal to run a single etcd instance private to the Kubernetes API server?

Kelsey - Yeah, that's the goal. (This obviously might differ on Core
setups, but you still could imagine having a separate etcd just for
separation of concerns between fleet / k8s.)
On Mar 27, 2015 7:12 AM, "Kelsey Hightower"<EMAIL_ADDRESS>wrote:

@roberthbailey https://github.com/roberthbailey Is the goal to run a
single etcd instance private to the Kubernetes API server?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5962#issuecomment-86952174
.

@zmerlynn The more I think about it, I think that is the right thing to do out of the box. If users really want to share etcd clusters, they can make the configuration changes.

@ArtfulCoder was this fixed by #6417?

yes, PR #6422


189 break up counterfactualsfunctionsjl into several files

Broke up counterfactuals/functions.jl into:
convergence.jl
core_struct.jl
encodings.jl
info_extraction.jl
initialisation.jl
latent_space_mappings.jl
path_tracking.jl
search.jl
utils.jl

Deleted counterfactuals/functions.jl.
Included all the new files in Counterfactuals.jl where all the "using" calls are now housed.
The package where a method is being called from is always specified now in these files.

Codecov Report

Merging #221 (8c928e8) into development (17ea311) will decrease coverage by 0.38%.
The diff coverage is 76.82%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@               Coverage Diff               @@
##           development     #221      +/-   ##
===============================================
- Coverage        77.73%   77.36%   -0.38%
===============================================
  Files               38       46       +8
  Lines             1334     1334
===============================================
- Hits              1037     1032       -5
- Misses             297      302       +5

Impacted Files
Coverage Δ

src/counterfactuals/plotting.jl
83.33% <50.00%> (-3.34%)
:arrow_down:

src/counterfactuals/utils.jl
60.00% <60.00%> (ø)

src/counterfactuals/core_struct.jl
61.76% <61.76%> (ø)

src/counterfactuals/info_extraction.jl
75.75% <75.75%> (ø)

src/counterfactuals/encodings.jl
76.92% <76.92%> (ø)

src/counterfactuals/latent_space_mappings.jl
78.26% <78.26%> (ø)

src/counterfactuals/path_tracking.jl
80.95% <80.95%> (ø)

src/counterfactuals/search.jl
86.20% <86.20%> (ø)

src/counterfactuals/initialisation.jl
92.30% <92.30%> (ø)

src/counterfactuals/convergence.jl
92.59% <92.59%> (ø)

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Annotation constants such as cr, cs, etc not defined

Happy to chip in with a PR if you are OK.

Hi @aliostad,
Why would you need such constants ? Isn't trace.Record(Annotations.ClientRecv()) enough ?
Can you explain your use case ?

Ah, I see. Yes, that suffice.

Ah... is this correct?
I am trying to add an annotation but there is a type mismatch?
span.Annotations.Add(Annotations.ServerRecv());

cannot convert from 'Criteo.Profiling.Tracing.Annotation.IAnnotation' to 'Criteo.Profiling.Tracing.Tracers.Zipkin.ZipkinAnnotation'

If you are trying to add an existing annotation to the span, the correct way to do it is trace.Record(Annotations.ServerRecv()).
If you're trying to add a custom annotation, then we'll need to discuss which one and how to do it.

Frankly I do not understand the role of Trace here. I have a span, it has a public interface allowing me to add an annotation. The crux of the problem seem to be that the list has been defined as a list of ZipkinAnnotation and not IAnnotation.
In the part of code that I am trying to do this I have a span, not a trace.
Again, I am a user of the library and I am trying to clear out things, I am happy to go along with the canonical suggestions of how to use the library. On the other hand, I have been a library developer for sometime and I can happily share some views on how to let consumers fall into the pit of success, if it is welcomed.
All in all, none of this is a criticism towards all the work that has been done here.

We definitely need to better document the role of Trace.cs as it is the cornerstone component when tracing your application. Usually  you don't manipulate directly with Spans, their lifecycle is managed by ZipkinTracer.
It's interesting that your use case lead you to manipulate Spans directly, could you detail it ?
Also don't hesitate to share anything that you find confusing with the library, like you said the more instinctive the library is the better.
For examples on how to use Trace, you can look at ClientTrace and ServerTrace.

@aliostad Can we close this issue ?

Sure, I guess another needed in terms of docs or approach.


event.body for handler

Is there any change from the base aws images that could affect this? as after creating my own image and attempt o use this everything goes well but i cannot send any parameters to the tests it always return a message event.body undefined if i inject the event paramenter to the handler

Most likely smth related to your code, as it still works fine for us, no changes made. Maybe if you paste some of your code somebody will be able to help.

This is my handler code
`const { convertFileToPDF } = require("./logic");
module.exports.handler = async (event, context, cb) => {
if(! event || ! event.body) {
console.log('[Empty request body]')
return  cb(null, {
headers: {
"Access-Control-Allow-Origin": ""
},
body: JSON.stringify({ message: 'Invalid body provided' })
});
}
console.log(event)
const { filename, base64File } = JSON.parse(event.body);
const pdfFileURL = await convertFileToPDF(base64File, filename).catch(cb);
return cb(null, {
headers: {
"Access-Control-Allow-Origin": ""
},
body: JSON.stringify({ pdfFileURL })
});
};`
it just goes directly into the empty event.body condition and im inserting data through the lambda test interface


Feat: Add Logout Button to Webpage

Describe the feature
Upon logout from the webpage, there is no button or relevant option for logging out; instead, a prompt for logging out appears when clicking on the login/sign-up button after already being logged in.
Add ScreenShots

Record

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

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


chore(FDS-342): Add input month field

*** Merge after https://github.com/Espressive/cascara/pull/261/files -- Input image module
The input month type is adding to our module list.
This PR includes:

Module DataMonth.
Fixture
Unit test

Snapshots
A new fixture for the DataMonth field is created.
New Component Checklist

[x] Includes unit tests for ALL required FDS use cases
[x] Does not mute any top level API props in React
[x] Includes an explanation for any changes to Jest snapshots (should be a PR tag automatically added if this happens)
[-] Component uses React.forwardRef() when a single DOM node is returned, AND it makes React-sense to access that DOM node

Warnings

:warning:
Please assign someone to merge this PR, and optionally include people who should review.

  Generated by :no_entry_sign: dangerJS against 7893d29e39772356672be10e6c69c3ddea437df4

Messages

:book:

packages/cascara/src/modules/DataImage/DataImage.fixture.js: This fixture has been changed.

:book:

packages/cascara/src/modules/DataMonth/DataMonth.fixture.js: This fixture has been changed.

  Generated by :no_entry_sign: dangerJS against e7ad7767b605b2e229c4f57adabdb8ab656f27f1


Prevent Channels from allowing the creation of CableCar identifier

I'm pretty sure that if someone declared a channel with...
stream_from "CableCar"
... it would blow up https://github.com/stimulusreflex/cable_ready/blob/master/lib/cable_ready/cable_car.rb
I think that it would be best to raise an exception just before https://github.com/stimulusreflex/cable_ready/blob/d809ad348eb649e37a9e547a79c3986494166b05/lib/cable_ready/channels.rb#L17

Nope.


fix: improve st-delete-digit test

One more test case to ensure that solution doesn't simply remove the smallest digit.

This is a great idea, I will merge this after deadline


Deploy-Diagnostics-LogAnalytics: non compliant

Describe the bug
The Deploy-Diagnostics-LogAnalytics policy is non-compliant, although a deployment finishes.
This is due to logs[*].enabled being [True,false] != True.
I made the policy compliant by enabling the Summary Logs manually. I'm happy to contribute the changes to the policy. As the policy just got one parameter to enable logs or not, I would suggest to just enable the other Log category as well.
We could also enable the log categrory groups instead of single log categories (currently exactly the same). But when MS adds a new category to a group, that shouldn't break the policy anymore.
What do you think?
Steps to reproduce

Create LAW in RG
Assign Policy to RG with LAW as target
See non-compliant as expected
Create RemediationTask
Check that diagnostic settings are deployed
LAW still non compliant

Hi @QBY-ThimoLimpert thanks for reporting. We're in the process of deprecating all the ALZ Diagnostic Settings policies and transitioning to new category based policies over the next few weeks. I'll keep this open to ensure we've covered Diag for LAW.

@Springstone @QBY-ThimoLimpert The same issue applies to most of these policies if not all of them. New log categories cause the following policies to be non-compliant at our side:
Deploy Diagnostic Settings for Service Bus to Log Analytics workspace
Deploy Diagnostic Settings for AVD Host Pools to Log Analytics workspace
Deploy Diagnostic Settings for Azure Function App to Log Analytics workspace
Deploy Diagnostic Settings for Data Factory to Log Analytics workspace
Deploy Diagnostic Settings for Databricks to Log Analytics workspace

Closing this as we've deprecated all our diagnostic settings policies and shifted to the PG owned initiative to do the same. Please review  https://aka.ms/alz/whatsnew for details.
If you find gaps in diagnostic settings coverage, please add the missing services to this discussion: #1644 as this is where we will track this going forward.
The new Diag Settings v2 initiative is based on categories and we default to "allLogs" which should cover all categories that may have been missed before. For this particular resource this is the new built-in: https://www.azadvertizer.net/azpolicyadvertizer/818719e5-1338-4776-9a9d-3c31e4df5986.html


Http Cache isn't cleared

I've run into an issue where cache-control is breaking some tests. Looks like page.clearMemoryCache() between runs

After doing a bit more looking into this. It appears that this isn't going to be very straightforward. It looks like ghostdriver doesn't have a clearMemoryCache() endpoint since it's a newer feature.

Sorry about that @smdern. Can you explain what the specific problem was?

@keathley I'm running a series of tests that require some seed data to exist in the DB. I insert the models as part of each test setup, but the endpoint that returns the list of models adds a cache-control header. The problem is that the id that is presented is different depending on which test ran first and causes subsequent tests (which tries to insert a model that associates to those ids) to fail.
It seems like the most straightforward way to handle this is to disable cache-control in the test environment, but ideally there could be a way to clear the cache between tests. It looks like phantomjs v2+ has such a feature which has clearMemoryCache(). After creating this issue I thought I'd try to open a PR but it looks like ghostdriver (which implements the wire protocol for phantomjs giving us the REST interface) hasn't been touched much since phantom 1.9.

scenario would be
test 1

inserts model(uniqueName=foo returns ID=1)
controller returns cache-control response with model id

test 2

inserts model(unqiueName=foo) (returns ID=2)
doesn't hit controller for list of ids because of cache-control
tries to create model with association to the model but w/ ID=1 because of cached response
insert fails because entry with ID=1 doesn't exist


Update MD file on new branch 2017-12-10_23-40-07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.