Missing interface for Eval/Trampoline in effect hierarchy

There's no interface in monix-eval for types that capture synchronous, trampolined evaluation without errors. Examples include Eval in cats, Trampoline in scalaz, and util.TailCalls in the stdlib. Deferrable[F] almost fits except for the Recoverable[F, Throwable] supertype.

@edmundnoble those types are experimental and thus far meant to fit the types exposed by Monix. Monix thus far doesn't expose more because it would end up duplicating Cats and Scala.
It is also incredibly hard to design type classes. Therefore in the interest of having usable integration with Cats and Scalaz, the types are now just the shims necessary for what Cats and Scalaz already provide.
This means that Deferable and Recoverable are gone for the moment. Upgrade to the latest version and you'll see. I am interested in providing more than the shims of Cats, so these types might be back, but the priority is releasing a stable 2.0 release that people can rely on.
That said I'm interested in your use-case. Are you looking for an abstraction over all these types?
Also, are you interested in helping with the design of these type classes? The timeline would be September 1st for the release of 2.0 (could happen right now, but waiting for people to come back from vacation), than possible improvements to those types could happen for 2.1.

@alexandru I would be interested in contributing to the design of these typeclasses. Unfortunately I'm away from my development machine at the moment, but I think typeclasses entirely for abstracting over evaluation would have very little overlap with Scalaz and cats, though they'd still need shims. They might even be useful enough to be worth their own (small) library.
My use case is abstracting over trampolined functions so that I can add trampolined and partially trampolined (a la http://blog.higher-order.com/blog/2015/06/18/easy-performance-wins-with-scalaz/) recursion schemes to matryoshka, for a compiler I am writing. I'm also open to creating a monix-matryoshka integration which would (for example) allow emitting partial results of a recursion scheme to an observable, or using the monix-eval hierarchy to express asynchronous or potentially error-throwing recursions generically.

@edmundnoble cool. Sorry, I've been away on vacation.
I already had a design in Evaluable and Deferrable.
We can bring those back, but it's not so easy. Like I'd like some laws to accompany these type-classes.
Another problem is how do you describe a type-class for something that produces a single result? This is the reason for the Recoverable super type, because you can then at least have materialize.  And because these types will live in monix-types, we can't have the conversion to Task either.
So again, how do you describe something that eventually produces a single result (Eval, Coeval, Task) and not something that can produce a whole stream (e.g. Observable)?

@edmundnoble FYI there's a new branch where I'm bringing back some of my previous work: https://github.com/monixio/monix/tree/wip-eval-streams
In particular, there's a new Enumerator type that can use both Task and Coeval as the underlying mechanism for doing evaluation.
So there's now the Deferrable type-class and it no longer inherits from any Recoverable and it could be applied to Cats Eval.
Let me know what you think.

This is no longer relevant, we dropped monix-types and moved on to cats-core and cats-effect. Closing.


black jack game

Describe the Feature you want to end

Expected behavior

Screenshots (optional)

Additional context (optional )

@MohitGupta121 , @TusharKesarwani please assign it to me i want to add my this game


License

Hi there! I recently came across this project and it is really cool! I am curious what the intent of this project and if others (including me) can use it or its code? Without a license (open-source or otherwise) in the repository, the allowed usage is unclear. See this Stack Exchange question for context.
Please consider adding a license such as MIT, Apache 2, or GPL, etc (if it fits the intent of your project).

Oh sorry, I decided with MIT and forgot to apply it)


when selecting 3 grade nodes and creating an OUTPUT label, it doesn't return anything, it should give an warning msg

i don't know which node you want to create an output for.
please select only 1 node if you want to create an output for it.

implemented this feature with:
selected_node_classes.append(node.Class())
if self.nodeClass not in selected_node_classes and self.validateLabelFormat(input):
self.warningLabel.setText("I DON'T KNOW WHICH NODE YOU WANT TO CREATE AN OUTPUT FOR.\nPLEASE HAVE ONLY ONE NODE SELECTED!")
self.reset_labeller_state()
return False


Checkout: on iPhone with 'Display Zoom' setting enabled: Payment fields 'cut off' / inaccessible

Expected behavior
Payment fields would be accessible on iPhone regardless of whether user has Display Zoom enabled in Settings
Actual behavior
When a user on iPhone has Display Zoom enabled, payment fields are "cut off" on the right side of the screen and not accessible

It appears that this prevents any user with Display Zoom enabled, from completing a purchase on our site
Steps to reproduce behavior
Using a physical iPhone, go to settings -> display + brightness -> Display Zoom -> select Larger Text
iPhone will restart, after which Display Zoom will be enabled
Navigate to checkout page -> payment information
Note: this issue appears (and the above screenshot was taken ) when vanilla Cornerstone (with no customizations) is the theme on our site

Thanks for reporting the bug. We''ll triage it.

Hello, closing this ticket because I tested it on my end, the issue is not there any more.
The problem should have been resolved by this PR, https://github.com/bigcommerce/checkout-js/pull/1128.


Fix image sizing logic for auto and stretch

Fix background container color being applied when it shouldn't

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


Misleading Redeem Output

I ended up in some odd state where my redeem preview did not add up to anywhere close to the amount that I was selling. I'm unable to reproduce this and I didn't submit the transaction, so I don't know whether it was a DApp issue or if the contract was returning the wrong amount. I suspect that it's a DApp-only concern and might be related to the comma in my number since the output nearly equals 110 instead of my 1,100.

Seen a second time with no comma 😕 I think maybe it had something to do with typing a 9 and then pausing before typing the rest.

Fixed via: https://github.com/OriginProtocol/origin-dollar/pull/344


"Git not supported on Windows" Warnings (Fix #540)

Rather than a Dockerfile approach to fixing #540, let's just check if we're on Windows or not, and if not just don't import the sh library and for any git. calls preempt the calls by checking the platform instead; if we're on Windows, it'll just fail out and never reach a git function, and also never reach the from sh import git functions either if Windows is the platform we're on.
(Inspired by an approach I made to my lxc-bootstrap script for an LXC container automated bootstrapping approach, where I tested if we're on Linux and if not return "NotImplementedError").

In testing this, we can properly run the test code.  We cannot, however, launch Smokey in a way that works with Windows.  Testing on Win7 and Win10, I got the same issue about not being able to get the usr cookie.  That suggests some Windows incompatibility, so I've added a "quit" condition early in ws.py that will exit if you try and actually run SmokeDetector in a Windows environment.  This does not, however, affect the test suites, so all is good.

Tested on four separate Windows instances, this prevents the sh import problems.  Note remaining issues such as that in #555.


Pc/fbprophet

Description
Please include a summary of the changes and the related issue.
Related to: (ClickUp/JIRA task link)

❔ This change

[x] adds a new feature
[ ] fixes breaking code
[ ] is cosmetic (refactoring/reformatting)

✔ Pre-merge checklist
Mark which items have been completed:

[x] Refactored code (sourcery)
[x] Tested code locally
[x] Added code to GitHub tests (notebooks, scripts)
[x] Updated GitHub README

🪝 Run the following to both pre-commit hooks and JupyterLab (turn on format on save)

[x] Stripped outputs from notebooks - (nbstripout)
[x] Sorted imports - (isort)
[x] Formatted code - (back)

📄 Updated documentation
Share the link of the documentation branch with changes: (link)

[ ] Updated content in the docs
[ ] Documentation all relevant docs index pages (e.g., Examples, Integrations intro, Model training index)

🧪 Test Configuration

OS: macOS Monterey v12.4
Python version: 3.8.13
Neptune version: 0.16.2
Affected libraries with version:

✔ Post-merge checklist
These tasks should be done after the code is merged to main. Please create a subtask under the main ClickUp task to have these on your radar and share the subtask here.
Post-merge subtask: (ClickUp/JIRA task link)

[x] Update relevant blogs with impacted code/functionality (ClickUp task name: Update prophet articles assigned to @SiddhantSadangi )
[ ] Add functionality under the Neptune column of the competitor comparison sheet (Coordinate with @SiddhantSadangi)
[ ] Work with marketing team to share updates on Social Media (Contact @Patrycja-J/@jakubczakon)

@Blaizzy lets hold merging this until neptune-prophet==1.0.0 is released.
Meanwhile, can you check the failing tests if anything looks out of the ordinary, and add more details to the PR checklist?

@Blaizzy lets hold merging this until neptune-prophet==1.0.0 is released. Meanwhile, can you check the failing tests if anything looks out of the ordinary, and add more details to the PR checklist?

It was a mistake during release they put 1.0.0 while it's supposed to be 0.1.0.
We can proceed.

@SiddhantSadangi tests are passing but some other tests are failing for something not very clear to me.

src/checkdep_freetype2.c(5): fatal error C1189: #error:  "FreeType version 2.3 or higher is required. You may set the MPLLOCALFREETYPE environment variable to 1 to let Matplotlib download it."
...
RuntimeError: main thread is not in main loop
Tcl_AsyncDelete: async handler deleted by the wrong thread

The PR is ready for review.
@normandy7 and @SiddhantSadangi  I pass it over to you guys.
Let me know if there are any further changes needed 👍

I tried out the example notebook in Colab, but I get an error when running the following:
import neptune.new.integrations.prophet as npt_utils

run["prophet_summary"] = npt_utils.create_summary(model=model, df=df, fcst=forecast)

AttributeError: 'Line2D' object has no property 'auto_ylims'

Could you verify that it works on your end?

@normandy7, that is weird.
It works normally on my local machine, but in colab, it indeed throws an error

@normandy7  found the issue.
Colab, by default, is not on the latest statsmodels v0.13.2 library, which causes the error.
It can be fixed by updating it:
!pip install -U statsmodels

@Blaizzy @normandy7 Prophet dependencies were updated and it was released. It should work for now, but for Conda, we might need to wait longer till it catches up.

Great to hear, thanks @twolodzko !

Back to you @SiddhantSadangi 👍🏾


Can't use custom config file with v0.0.29 and newer

Short description of the problem:
I use a custom config file for PouchDB compatibility. It works in 0.0.27 and 0.0.28. When in 0.0.29 or newer this error is printed :

Config file "/Users/******/Documents/IonicProjects/Metho/config/rollup.config.js" not found. Using defaults instead.
(replace the * with my username)
But the config file is there as it's working for older versions.

What behavior are you expecting?
The config file to be used
Steps to reproduce:

Provide a config file to<EMAIL_ADDRESS>ionic serve

Which @ionic/app-scripts version are you using?
0.0.28 (working), newer (broken)

Hello, thanks for opening an issue with us! You should be getting a warning message in the output that tells you the small change that 0.0.29 and up requires to custom rollup.config files. The entry property of the rollup.config file should now be 'src/app/main.dev.ts'. Can you give that change a try and see if it fixes it for you? Thanks!

I got the same error. The change in entry was not enough, so I restarted with a fresh  file from<EMAIL_ADDRESS>(as proposed in the docs) and just inserted the PouchDB namedExports:
My rollup.config.js:
`var nodeResolve = require('rollup-plugin-node-resolve');
var commonjs = require('rollup-plugin-commonjs');
var globals = require('rollup-plugin-node-globals');
var builtins = require('rollup-plugin-node-builtins');
var json = require('rollup-plugin-json');
var rollupConfig = {
entry: 'src/app/main.dev.ts',
sourceMap: true,
format: 'iife',
dest: 'main.js',
plugins: [
builtins(),
commonjs({
namedExports: {
// pouchdb
'node_modules/js-extend/extend.js': ['extend'],
}
}),
nodeResolve({
module: true,
jsnext: true,
main: true,
browser: true,
extensions: ['.js']
}),
globals(),
json()
]
};
if (process.env.IONIC_ENV == 'prod') {
// production mode
rollupConfig.entry = '{{TMP}}/app/main.prod.ts';
rollupConfig.sourceMap = false;
}
module.exports = rollupConfig;`

That error is somewhat misleading, but rollup treats any syntax errors triggered by attempting to evaluate the config file as if the file was not found, so look up for earlier root causes.

@jgw96 I found the cause. My Rollup script was importing ngTemplate and it isn't available in 0.0.29 and newer. Once I fixed that issue, it prompted me with the error saying to use src/app/main.dev.ts


Matrix Builds / Sub-Builds / Parallel Builds

I'm wondering how would a .drone.yml would look if you'd want to test with multiple versions of Python, like for example, using Tox?

We couldn't wait and rolled another solution.  It's based on Integrity and leverages CoreOS for parallelism.  We're elastically scaling workers into AWS to supplement the workers we have on site.

Did anybody step up to the plate yet? Just asking to prevent duplicate work? If not I will put this on my plate round about 2 weeks.

@drahnr thanks!
Just to clarify, are you referring to the matrix style referenced in https://github.com/drone/drone/issues/6#issuecomment-36059400 ? Because that is definitely the direction we want to go after speaking with some large open source projects and collecting feedback.
This change is going to be pretty involved and touch a lot of files, so it would be very helpful to break this up into smaller, focused pull requests (similar to what we are doing with #749) instead of one massive pull request. For example, the first pull request could modify the database, the second pull request could add rest endpoints, the third could modify the user interface, the fourth could alter the queue, etc ...
The first implementation of matrix builds doesn't need to be perfect, however, we need to be confident that it will (at some point) be able to address the following issues:

which build (in the matrix) should handle the deployment / publish steps?
should we publish / deploy only if all other builds in the matrix pass? If yes, how does this work?
how does this work with the cache feature in the yaml? If multiple matrix builds are trying to access the cache it could lead to race conditions

Pretty much as comment https://github.com/drone/drone/issues/6#issuecomment-36059400 though I'd prefer the {{ var }} version since it is more recognizable, but that is just an implementation detail.
The idea was to run k (configurable) docker containers based on the matrix elements concurrently. When the matrix container queue empty converge the results and if all builds succeeded, deployment is triggered (this will be the first implementation round, exceptions or allowed failure will be added later on).
I did not look into the caching features yet.
As said, I am currently pretty busy thus the delayed plating.

it would be awesome if you would provide the folks with information on this asap. we hardly wait for this and would be happy to test early stuff and provide feedback. :sparkling_heart:

Pretty much as comment #6 (comment) though I'd prefer the {{ var }} version since it is more recognizable, but that is just an implementation detail.

We ditched the {{ var }} syntax in the last release in favor of the $$ notation, so we would probably keep this for consistency.

When the matrix container queue gets empty, the results should be converged and if all builds succeeded, deployment is triggered

The implementation is going to be a bit tricky, but it is possible. The .drone.yml is converted into a shell script that gets injected into the container and executed. This script includes the build and test commands (ie the script section) and the publish and deployment commands. So basically it is one giant script.
This means we need to stop the container before the publish and deploy commands are executed. Then we need to re-start the container and skip directly to the publish and deploy commands.
When we first run the container we do something like docker run ./build.sh. When we restart the container we cannot change the entrypoint command. This means the build script will be executed twice. It will need to know when to run the build and test commands vs the publish and deploy commands.
Perhaps something like this:
if [ -f /tmp/.skiptests ]  // checks to see if some file was written indicating our tests were executed
then

  // create some sort of file indicating we've run
  // our tests before.
  touch /tmp/.skiptests

  // my build and test commands here

else

  // my publish and deploy commands here

fi

Some of these changes may be contingent upon, or at least easier, when #749 is ready

I did not look into the caching features yet.

No worries, this is probably the easiest of the 3 to solve. I haven't put much thought into it myself, but we would likely have a cache for each axis in the matrix. It is the safest (and easiest) path forward and we can always fine tune the implementation in a follow-up release.

As said, I am currently pretty busy thus the delayed plating.

I completely understand. I'm happy to help when you're ready to start

I will to split the changes up as far as it makes sense.

When you're ready to start coding let's come up with a plan to chunk up the work

$$var it is, didn't know about the drop of {{ var }} so far.
What means of inter-docker container communication can I take as granted? That is the most difficult point and depends on the fact if all containers run on the same machine (hint: dbus)
or not (hint: TCP/IP)
I will setup a testing repo for x86_64 Fedora 21, but be patient, that won't happen until the end of next week - at least.

This is a (barely) functioning proof of concept illustrating a matrix build from the Drone CLI:
https://github.com/drone/drone-cli/blob/matrix/runner/run/run.go
There isn't much to see, but wanted to post an update so that people could follow progress on this branch. The plan is to get matrix builds working from the command line utility first, and then integrating into Drone.

We are updating the .drone.yml file format and have a few different options described in https://github.com/drone/drone/issues/902
I would love to get some feedback on the existing proposals at the above link. The formats are un-related to matrix builds, however, it is a blocking prerequisite. I want to be sure we get it right. The quicker we get feedback the quicker we get matrix builds :)

i would like to be able to use
image:
  - ubuntu:14.04
  - ubuntu:12.04

instead of
image: ubuntu:$$ubuntu_version
[...]
matrix:
  ubuntu_version:
    - 14.04
    - 12.04

for just parallel builds. so we could use ubuntu and debian or centos if we don't use apt for example.

My use case comes down to building multiple variants of the same code using the very same image. Effectively this comes down to threading the configuration settings through whatever syntax you guys design:

Eg: invoking distinct scripts:
matrix:
debug:
script: ./scripts/ci-debug
opt:
script: ./scripts/ci-opt
opt-asan:
script: ./scripts/ci-opt-asan

Eg: setting environment variables:
script: ./scripts/ci
matrix:
debug: VARIANT=debug
opt: VARIANT=opt
opt-asan: VARIANT=opt INSTRUMENTATION=asan

It would also be nice to keep track of the individual rows within the matrix. Eg: the "opt" variant may start failing.

@davidak there are no restrictions as to how or where matrix parameters get injected into the yaml file. You could test multiple distros by doing something like this:
image: $$docker_image
[...]
matrix:
  docker_image:
    - ubuntu:14.04
    - ubunut:12.04
    - centos:latest
    - debian:wheezy

The ability to inject parameters with $$ is quite flexible

@os12 you will be able to invoke distinct scripts using the following notations:
build:
  image: go
  commands:
     - ./scripts/$$script
matrix:
    script:
      - ci-debug
      - ci-opt
      - ci-opt-asan

and you could inject environment variables like this:
build:
  image: go
  commands:
     - export $$env
matrix:
    env:
      - VARIANT=debug
      - VARIANT=opt
      - VARIANT=opt INSTRUMENTATION=asan

I'm pretty confident that all use cases are supported

Both look good. Thanks Brad!

quick screencast of Drone running matrix builds from the command line: https://twitter.com/droneio/status/577496429242912769

@bradrydzewski that's great to see, great work!

Any update on when this is going to land?

yes, I expect to have a working 0.4 distribution available around May 22nd (sourced from the bolt branch). It will then take between 2 and 4 weeks before it is merged into master, depending on how quickly we are able to test and backport existing plugins to the new plugin model, document changes, etc.

@bradrydzewski Will this pull request also allow for dependant builds (i.e. project b should be built after  project a)? I think this is a bit different than a matrix build if I understand correctly.

@stevenpall we are launching a new plugin model (included with the matrix feature) that would allow you to augment builds. I think this dependant builds could probably be added as a plugin.

+1 Refreshing approach to the build matrix. It's nice to see that they can be include in the configuration file and injected into the build environment.

@bradrydzewski, any plan for release of this feature ?

@romani the 0.4 branch includes matrix builds, but it is still a bit too unstable and undocumented for people to start using. The 0.4 release, however, is still planned for this month

:+1:

+1

just wanted to give a quick update here.... I gave an implementation overview and live demo in last week's Rancher meetup of upcoming matrix build functionality:
https://youtu.be/86u8pVESbPQ?t=4586

WOW. This looks pretty cool (not only the matrix build, everything). Can't wait for the release :)

@bradrydzewski I haven't had the chance to watch the video but is there a doc specifying a build env/commands to build and try 0.4? Once I get that far I'll be able to help as much as possible but figuring it out on my own is too much time for me.

@mjschultz as far as I know the only documentation is in this issue

Merged into master. Note that this is the initial implementation of matrix builds. Now everyone can start following the open issue for parallal matrix builds (#1254) targeted for the 0.4.1 release :smile:
You can find the matrix documentation here:
http://readme.drone.io/build/matrix.html
Enjoy!

Is this still a feature? The URL above is broken and I'm struggling to find docs about build matrices


Issue while bundle install

What did you do?
I ran the command /Users/fluvip/.rvm/gems/ruby-2.3.1@project/bin/bundle install

What did you expect to happen?
I expected Bundler to install gems from Gemfile to specific gemset

What happened instead?
Instead, what actually happened was this error appeared.

Error details
Errno::EIO: Input/output error @ io_fread - /Users/fluvip/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/info/capistrano3-unicorn
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:77:in `read'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:77:in `checksum_for_file'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:70:in `update_info'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:43:in `block in dependencies'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/fetcher/compact_index.rb:88:in `block (3 levels) in compact_index_client'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/worker.rb:65:in `apply_func'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/worker.rb:60:in `block in process_queue'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/worker.rb:57:in `loop'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/worker.rb:57:in `process_queue'
  /Users/fluvip/.rvm/gems/ruby-2.3.1@project/gems/bundler-1.12.5/lib/bundler/worker.rb:29:in `block (2 levels) in initialize'

Environment
Bundler   1.12.5
Rubygems  2.5.1
Ruby      2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin14]
GEM_HOME  /Users/fluvip/.rvm/gems/ruby-2.3.1@project
GEM_PATH  /Users/fluvip/.rvm/gems/ruby-2.3.1@project:/Users/fluvip/.rvm/gems/ruby-2.3.1@global
RVM       1.27.0 (latest)
Git       2.8.1
  Bundler settings

orig_path
Set via BUNDLE_ORIG_PATH: "/Users/fluvip/.rvm/gems/ruby-2.3.1@project/bin:/Users/fluvip/.rvm/gems/ruby-2.3.1@global/bin:/Users/fluvip/.rvm/rubies/ruby-2.3.1/bin:/Users/fluvip/.rvm/bin:/opt/local/lib/postgresql94/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/MacGPG2/bin:/usr/local/ec2/ec2-api-tools-<IP_ADDRESS>/bin"
orig_gem_path
Set via BUNDLE_ORIG_GEM_PATH: "/Users/fluvip/.rvm/gems/ruby-2.3.1@project:/Users/fluvip/.rvm/gems/ruby-2.3.1@global"

This has a friendlier error message in 1.14 -- in the meantime, perhaps deleting that file and trying to bundle install again will fix things.


Split validation workflow

As mentioned in https://github.com/nodejs/bluesky/pull/5#issuecomment-2510283183

...apparently the secrets are not passed into workflow runs triggered by PRs from forks. So I guess that means we should split the validation into two parts:

If it's triggered by a PR from a branch in this repo (which means it must be from someone who already has write access here), it can invoke additional validation to check the URLs are reachable and valid (which requires access to bluesky secrets).
Otherwise, only local validations are run on the JSON files.

This means:

Split everything below https://github.com/nodejs/bluesky/blob/dbdab8983a9b3ee52c2f18dd5e33674629687a26/actions/login-and-validate.js#L21 to a separate file
Splitting https://github.com/nodejs/bluesky/blob/main/.github/workflows/validate.yml into two workflows, one local and one remote. PRs started from a branch in this repo get both run for them, and PRs from forks just run the one that's without the login.

Hi joyeecheung,
Can I work on this issue?

Sure, go ahead please!


File Missing

I have got Fatal error for in checkout lib
Fatal error: Class 'CheckoutApi_Api' not found in com/checkout/helpers/ApiHttpClient.php on line 17
Need Solution for this  one

Hello there,
Try to clone the library with the submodule by using the below command:
git clone --recursive https://github.com/CKOTech/checkout-php-library.git

I have the same issue.
I did install CheckOutAPI using composer (require "checkout/checkout-php-api:dev-master") and don't want to split my libs outside composer.
@dhiraj-gangoosirdar-cko could you please upgrade the checkout-php-library dependancies ?
Thanks.

+1

Please try the below to remove the mater branch library and install the updated one from our release/v1.2 branch:
composer remove checkout/checkout-php-api --update-with-dependencies
composer require "checkout/checkout-php-api:dev-release/v1.2"
Don't forget to include autoload.php file when you want to use the Checkout.com library:
If you're using Laravel:
include DIR.'/../vendor/checkout/checkout-php-api/autoload.php';

That did the trick, thanks!


API Validation: Check ValueType vs Value from the response

As discussed in Test Engine Developer Group Meeting (21.08.2024), it should be checked in the received response, if the valueType & corresponding value match each other. For instance, if the valueType is bool, then the server should not allow value of some random string. Also, the valuesTypes should be from the valid data types defined in the specs.

Fixed


git module seems to break stderr

Description
When enabling the git module, the stderr output occasionally breaks and nothing is printed on the terminal.
Expected behavior
When writing to stderr, it should be printed into the terminal.
Steps to Reproduce
It's quite hard to reproduce this bug.
I tried to disable the git module and I could not reproduce the issue.
Versions

Prezto commit: 0a405494cae54e208ff550c1ba83380ed115410a
ZSH version: zsh 5.8
OS information: Archlinux (kernel 5.9.1-arch1-1)

@gnuletik I'm not sure what is causing this issue but I know a fix for this. nano is the default editor for git. You should update your $EDITOR to either vim or emacs to fix this issues or just update global git config to specific a different EDITOR.

Hi @srijanshetty
Thanks for the answer !
The $EDITOR variable was already set but setting the $VISUAL variable fixed the default editor for git.
However, the issue still appears when spamming other commands.
zsh: command not found: CD
~/c/i/f/s/d/a/www ❯❯❯ S                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: S
~/c/i/f/s/d/a/www ❯❯❯ A                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: A
~/c/i/f/s/d/a/www ❯❯❯ A                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: A
~/c/i/f/s/d/a/www ❯❯❯ A                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: A
~/c/i/f/s/d/a/www ❯❯❯                                                                                ✘ 127 dev ✭ ◼
~/c/i/f/s/d/a/www ❯❯❯ a                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: a
~/c/i/f/s/d/a/www ❯❯❯ a                                                                                ✘ 127 dev ✭ ◼
zsh: command not found: a

# and now stderr is broken

~/c/i/f/s/d/a/www ❯❯❯ a                                                                                ✘ 127 dev ✭ ◼
~/c/i/f/s/d/a/www ❯❯❯                                                                                ✘ 127 dev ✭ ◼
~/c/i/f/s/d/a/www ❯❯❯                                                                                ✘ 127 dev ✭ ◼

~/c/i/f/s/d/a/www ❯❯❯ a                                                                                ✘ 127 dev ✭ ◼
~/c/i/f/s/d/a/www ❯❯❯ echo test 1>&2                                                                                ✘ 130 dev ✭ ◼
~/c/i/f/s/d/a/www ❯❯❯ echo test                                                                                dev ✭ ◼
test

# stdout still works

My current guess is that something in our git-info function or the external zsh-async are using stderr redirection with a command stored in a variable and that var is somehow unset sometimes.
I think we've had similar issues with people holding down Control C...
Does this seem correlated to how quickly you rerun the command, or is that not a factor?

Hi @belak,
Thanks for the answer.
Holding Ctrl-C do not reproduce the problem.
I tried this test

cd into git repo
press 'a'
Wait half a second
press enter
Wait half a second
Go back to the "press 'a'" step

The issue occurred after 40 occurrences.
I repeated the tests faster multiple times, sometimes it occurs after 5 occurrences, sometimes after 40.
So, it does not seems correlated to how quickly I rerun the command.
Thanks!

Just updated async to 1.8.5 via #1926. This was in my backlog for a while.
Let's keep an eye on how this goes. We can roll back if we find a regression.

Closing, assuming #1926 fixed this. @gnuletik, please feel free to reopen if you still continue to face this.


Sort by any field in cms

This adds the ability to sort in the CMS
closes #2774

Sweet!! This one's going to be so helpful.
Small thing @spbyrne (and don't think it needs to hold this PR up) but the loading state flash is a bit jarring:
https://www.loom.com/share/72947a36c6d44874a04f899250113369

Instead of "No Selection" should it say Default maybe (which is the filename sort)?

Instead of "No Selection" should it say Default maybe (which is the filename sort)?

I may be wrong on this, but I thought someone said recently the default sort was the isTitle field (if it's set)

Instead of "No Selection" should it say Default maybe (which is the filename sort)?

I may be wrong on this, but I thought someone said recently the default sort was the isTitle field (if it's set)

yeah, I think if isTitle is set then that field is the default, otherwise it is the filename. Either way, a "default" sort is applied - "No selection" seems to be saying that there is no sort.

Sweet!! This one's going to be so helpful.
Small thing @spbyrne (and don't think it needs to hold this PR up) but the loading state flash is a bit jarring: https://www.loom.com/share/72947a36c6d44874a04f899250113369

@jamespohalloran Do you have a suggestion of how to fix this? In production the loading will take a bit longer and the loading message will be very helpful and feel better.

Instead of "No Selection" should it say Default maybe (which is the filename sort)?

I may be wrong on this, but I thought someone said recently the default sort was the isTitle field (if it's set)

yeah, I think if isTitle is set then that field is the default, otherwise it is the filename. Either way, a "default" sort is applied - "No selection" seems to be saying that there is no sort.

@jamespohalloran @kldavis4
The default is the 'IsTitle" field if there is no isTitle field then it will be the file name.
I can change is to "Default" instead of the "No selection"

@logan-anderson Here's how Linear does it: https://www.loom.com/share/021159a491b744ca8f6a9fb0cd608cdc
It just looks a bit smoother without the global loading state flicker.


Responsiveness in mobile view

I would like to work on this issue.

I also want to work on this project to make it more interactive, can you assign me?

This project seems interesting to me, can I contribute?


Session persistence (opened tabs and split screen configs)

It would be great if the window size & position, tabs and split screen configs are preserved and then restored on Terminus reopen. Preserving the CWD of each tab & split screen and last commands of it, would make it awesome!

Personally for me the lack of that feature is becoming more and more an issue. I'll probably give it a try to implement if I find some time soon.

This has been implemented a while ago


Support no-label mode

This improved version supports no-label mode. Set LabelText to empty so that no labels are displayed. In addition, the arguments-options syntax was introduced to set name-value parameters more clearly and concisely.

Merged into master. Thanks!


Page number not shown on document template.

The document template does not add page numbers. This makes following the index more difficult (and everybody expects page numbers so why not have them).

Fixed on last commit.


The word several is repeated in step 11

In step 11 of the build a personal portfolio zipline, the word
“several” is repeated.  See issue 3884.

@tdugger thanks for the PR! Please, add to the description something line "Closes 3884" or "Fix 3884" to automatically close the issue when this PR is merged. And next time follow instructions from Guidelines for Contributing, thanks.

@tdugger Thanks for fixing this!


Devicemapper device leak with container restart of a crashed pod

Description of problem
ENV: k8s-1.13.4+containerd-1.3.0beta2+kata-1.7.4 (devicemapper as snap)
Recently I noticed thousands of unused dm thinpool on k8s node, meanwhile one or more crashed pods stay on it.
I tried to reproduce it successfully.  while a pod  in CrashLoopBackOff state, creation or deletion of runc dm are as expected, but dm thinpools of kata become greater in number.
Number showed by: dmsetup ls|wc -l
I could clean unused thinpools by: dmsetup remove_all
Expected result
Devicemapper thinpool deleted as expected.
Actual result
leak

Hi @clarklee92 - please can you run sudo kata-collect-data.sh as requested in the template to provide further details.
Also, you are referring to Kata 1.7.4 - have you tried testing with a 1.8 release or master?

Show kata-collect-data.sh details

Meta details
Running kata-collect-data.sh version 1.7.4 (commit 984f7bbaa7a26ebcec29ef9911a63aaef601c62d) at 2019-09-05.11:09:23.866573913+0000.

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

[Runtime]
  Debug = false
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.7.4"
    Commit = "984f7bbaa7a26ebcec29ef9911a63aaef601c62d"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/opt/kata/share/defaults/kata-containers/configuration-qemu.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version <IP_ADDRESS> (2019-08-05_15:35:32@szwg-inf-bce2.szwg01.baidu.com@e567da5)\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/libexec/qemu-kvm"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = false
  UseVSock = false
  SharedFS = "virtio-9p"

[Image]
  Path = "/opt/kata/share/kata-containers/kata-containers-image_clearlinux_1.7.4_agent_6a96cd0906.img"

[Kernel]
  Path = "/opt/kata/share/kata-containers/vmlinux-4.19.52-45"
  Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket systemd.mask=systemd-journald.service systemd.mask=systemd-journald.socket systemd.mask=systemd-journal-flush.service systemd.mask=systemd-journald-dev-log.socket systemd.mask=systemd-udevd.service systemd.mask=systemd-udevd.socket systemd.mask=systemd-udev-trigger.service systemd.mask=systemd-udevd-kernel.socket systemd.mask=systemd-udevd-control.socket systemd.mask=systemd-timesyncd.service systemd.mask=systemd-update-utmp.service systemd.mask=systemd-tmpfiles-setup.service systemd.mask=systemd-tmpfiles-cleanup.service systemd.mask=systemd-tmpfiles-cleanup.timer systemd.mask=tmp.mount systemd.mask=systemd-random-seed.service<EMAIL_ADDRESS>init=/usr/bin/kata-agent"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.7.4-494d9a35e330b002de547a5473c167a3482eb1ca"
  Path = "/opt/kata/libexec/kata-containers/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.7.4-238a235f13436282bdb198d4e3ae6ea60202e3d3"
  Path = "/opt/kata/libexec/kata-containers/kata-shim"
  Debug = false

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

[Host]
  Kernel = "4.19.12-1.el7.elrepo.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "CentOS Linux"
    Version = "7"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz"

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

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

Runtime config file contents
Output of "cat "/etc/kata-containers/configuration.toml"":
[hypervisor.qemu]
path = "/usr/libexec/qemu-kvm"
kernel = "/opt/kata/share/kata-containers/vmlinux.container"
image = "/opt/kata/share/kata-containers/kata-containers.img"
machine_type = "pc"

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

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

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

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

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

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

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

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

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

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

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Output of "cat "/opt/kata/share/defaults/kata-containers/configuration.toml"":
[hypervisor.qemu]
path = "/usr/libexec/qemu-kvm"
kernel = "/opt/kata/share/kata-containers/vmlinux.container"
image = "/opt/kata/share/kata-containers/kata-containers.img"
machine_type = "pc"

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

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

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

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

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

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

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

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

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

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

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

systemd service
Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-07-20T18:43:02.600522601+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "30450"
  packages:
    default:
      - "chrony"
      - "iptables-bin"
      - "libudev0-shim"
      - "systemd"
      - "util-linux-bin"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.7.4-6a96cd09061ce3babdfcdd1b06d809aeec5037be"
  agent-is-init-daemon: "no"

Initrd details
No initrd

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

Container manager details
No docker
Have kubectl
Kubernetes
Output of "kubectl version":
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:37:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Output of "kubectl config view":
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: https://<IP_ADDRESS>:6443
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: kubernetes-admin
  name: kubernetes-admin@kubernetes
current-context: kubernetes-admin@kubernetes
kind: Config
preferences: {}
users:
- name: kubernetes-admin
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED

Output of "systemctl show kubelet":
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestampMonotonic=0
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=0
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=0
ExecMainCode=0
ExecMainStatus=0
MemoryCurrent=18446744073709551615
TasksCurrent=18446744073709551615
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=65536
LimitAS=18446744073709551615
LimitNPROC=767759
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=767759
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=inherit
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=kubelet.service
Names=kubelet.service
Description=kubelet.service
LoadState=not-found
ActiveState=inactive
SubState=dead
InactiveExitTimestampMonotonic=0
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=no
AssertResult=no
ConditionTimestampMonotonic=0
AssertTimestampMonotonic=0
LoadError=org.freedesktop.DBus.Error.FileNotFound "No such file or directory"
Transient=no

No crio
Have containerd
containerd
Output of "containerd --version":
containerd github.com/containerd/containerd v1.3.0-beta.2 640860a042b93c26c0a33081ee02230def486f81

Output of "systemctl show containerd":
Type=simple
Restart=always
NotifyAccess=none
RestartUSec=5s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=Thu 2019-09-05 08:00:09 GMT
WatchdogTimestampMonotonic=31348684
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=9159
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Thu 2019-09-05 08:00:09 GMT
ExecMainStartTimestampMonotonic=31348626
ExecMainExitTimestampMonotonic=0
ExecMainPID=9159
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStart={ path=/usr/local/bin/containerd ; argv[]=/usr/local/bin/containerd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=266981376
TasksCurrent=241
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1048576
LimitAS=18446744073709551615
LimitNPROC=18446744073709551615
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=767759
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=-999
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=containerd.service
Names=containerd.service
Requires=basic.target
Wants=system.slice
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=multi-user.target shutdown.target
After=network.target systemd-journald.socket system.slice basic.target
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/etc/systemd/system/containerd.service
UnitFileState=enabled
UnitFilePreset=disabled
InactiveExitTimestamp=Thu 2019-09-05 08:00:09 GMT
InactiveExitTimestampMonotonic=31343610
ActiveEnterTimestamp=Thu 2019-09-05 08:00:09 GMT
ActiveEnterTimestampMonotonic=31348719
ActiveExitTimestamp=Thu 2019-09-05 08:00:09 GMT
ActiveExitTimestampMonotonic=31288886
InactiveEnterTimestamp=Thu 2019-09-05 08:00:09 GMT
InactiveEnterTimestampMonotonic=31339383
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Thu 2019-09-05 08:00:09 GMT
ConditionTimestampMonotonic=31341334
AssertTimestamp=Thu 2019-09-05 08:00:09 GMT
AssertTimestampMonotonic=31341335
Transient=no

Output of "cat /etc/containerd/config.toml":
root = "/data/lib/containerd"
state = "/data/run/containerd"
[plugins]
  [plugins.cri]
    sandbox_image = "***/pause:3.1"
    [plugins.cri.containerd]
      no_pivot = false
      snapshotter = "devmapper"
      [plugins.cri.containerd.runtimes]
        [plugins.cri.containerd.runtimes.untrusted]
          runtime_type = "io.containerd.kata.v2"
          privileged_without_host_devices = true
  [plugins.devmapper]
    pool_name = "containerd-thinpool"
    base_image_size = "20480MB"

Packages
No dpkg
Have rpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"":
qemu-kvm-1.5.3-160.el7_6.3.x86_64
qemu-kvm-common-1.5.3-160.el7_6.3.x86_64
qemu-img-1.5.3-160.el7_6.3.x86_64
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch


Latest cisco MIB has been in netdisco-mibs for a year but are missing in the latest containerized builds

Expected Behavior

Latest docker image should include latest MIBs.
The latest Cisco MIB has been in netdisco-mibs for more than a year:
https://github.com/netdisco/netdisco-mibs/blob/master/cisco/CISCO-PRODUCTS-MIB.my
(last modified september 2019).
However the bundled file in the latest docker-backend image is dated from 2018 and stops at "ciscoProducts 2705" :
318.9K Dec 30  2018 CISCO-PRODUCTS-MIB.my
Current Behavior

Older version of the file is bundled.
Possible Solution

Steps to Reproduce (for bugs)

Docker pull/run -latest (2.46.5 at the time of this writing)
docker exec -t  sh -c "ls -alh /home/netdisco/netdisco-mibs/cisco/CISCO-PRODUCTS*"
-rw-rw-r--    1 netdisco netdisco  318.9K Dec 30  2018 /home/netdisco/netdisco-mibs/cisco/CISCO-PRODUCTS-MIB.my
Note that the file is not the latest

Context

Wrong products displayed with latest Cisco devices.
Your Environment

netdisco container versions: 2.46.5

netdisco-postgresql: 2.46.5
netdisco-backend: 2.46.5
netdisco-web: 2.46.5

docker engine version:  irrelevant
docker-compose version:  irrelevant
host operating system: rhel

Config info (deployment.yml and docker env settings)

irrelevant
Device information

i thought i saw this issue before. netdisco-mibs get tagged x.xxx.
for some reason however we once released 4.13 instead of 4.013 and the logic used thinks 4.13 is greater than the recently release 4.019
https://github.com/netdisco/netdisco-docker/blob/75ed4476deb8004d1da30709be2123c41f88c17d/netdisco-backend/Dockerfile#L17-L20
i've alrdy renamed netdisco-mibs 4.13 to 4.013, but it seems the git tag might be still around....

oh, it seems github has a handy feature to remove tags now, so removed the incorrect 4.13 tag, can you try again?
before deleting the tag i got this:
curl -sL https://api.github.com/repos/netdisco/netdisco-mibs/tags | jq '.[]|.tarball_url|select(test("tarball/\\d+\\.\\d+$"))' | sort -rg | head -n1
"https://api.github.com/repos/netdisco/netdisco-mibs/tarball/4.13"

after deleting the tag i get the latest version:
curl -sL https://api.github.com/repos/netdisco/netdisco-mibs/tags | jq '.[]|.tarball_url|select(test("tarball/\\d+\\.\\d+$"))' | sort -rg | head -n1
"https://api.github.com/repos/netdisco/netdisco-mibs/tarball/4.019"

i'm no git expert, perhaps the tag was readded by accident when someone merged their tree. we'll need to keep an eye on this.

pull request #35 hopefully solves this issue forever.

Thanks, I'll try with the next container build

I can confirm that my cisco.Product.XXXX have now become 9500FixedSwitchStack in the inventory, confirming that the MIBs have been upgraded !
Thanks for the fix !


Windows DDLs being built without exported functions

Replaces #120 with new information from cjlarose/argon2-ffi#20.
DLLs built on Windows (sometimes?) have no exported functions. This can be confirmed with the command dumpbin /exports built.dll. Results can be seen here. A normal result would look like this. This causes the win32 error 127, could not load the specified procedure. That is because the specified procedure (function) is not in the DLL.
This binding.gyp can replicate it, although there is nothing too special in there.

I think we've found the root problem in that thread:

It looks like the problem is that for VS you have to put __declspec(dllexport) before any function you want to export when building a DLL. That's why our built DLLs have no functions.
There's no way to automatically export all functions (that's built into VS at least), so it looks like it won't easily work unless argon2 adds specific support for Visual Studio.

Could node-ffi handle this automatically? It would be hard to automatically instert __declspec into the code, but VS provides another way. A module definition file could specify functions that need exported. However, you first have to determine which functions need exported and then put them in a file. Anybody have a good idea on how to do this? I know CMake handles this somehow.

While in this case the issue was easily fixable thanks to already having ARGON2_PUBLIC which can be adjusted to __declspec(dllexport), many projects are not that planned. A more general automated solution would be very nice.

I think what you're looking for is the ModuleDefinitionFile in gyp. See node-ogg for an example: https://github.com/TooTallNate/node-ogg/blob/b7fa35df9ed859901eb6d0316bf6e147b6bb13b1/binding.gyp#L30-L36

@TooTallNate I see, that's very useful. I've not seen that in a node-ffi project before. Complete automation like CMake would be nice, but I think that's out of the scope of this project. Therefore, I'm closing this issue. If anyone has a good idea on how to automate this (with a library or such) I can reopen this.


Update DocDB models and inject SourceRegion

This updates the DocDB model and injects the SourceRegion argument for
the CopyDBClusterSnapshot operation.

Codecov Report

Merging #2087 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #2087   +/-   ##
========================================
  Coverage    93.11%   93.11%
========================================
  Files           60       60
  Lines        11096    11096
========================================
  Hits         10332    10332
  Misses         764      764

Impacted Files
Coverage Δ

botocore/handlers.py
96.35% <ø> (ø)

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 9ba31db...65dc18c. Read the comment docs.


Mismatch in released rspec and rspec-core versions

Hi,
As part of our build process, we have a few different gems that install rspec and rspec-core (both at the latest versions). We are now running in to an issue as a new version of rspec-core was released earlier today (which in itself is fine) but due to the runtime dependencies of rspec (defined here), we are no longer able to run any builds.
As rspec v3.8.0 (currently the latest) depends on rspec-core, rspec-expectations and rspec-mocks v3.8.0 (which are no longer the latest).
I do see a commit in rspec to push to v3.9.0 here; would it be possible to publish the new version of the gem? If not, please advise of a way we can work around this dependency issue.
Thanks!

@vishuvig yes the release was in progress, I'm a bit confused as to how this broke your build though, if you use gem 'rspec', '~> 3.8' it would have just worked for example.

@vishuvig yes the release was in progress, I'm a bit confused as to how this broke your build though, if you use gem 'rspec', '~> 3.8' it would have just worked for example.

I had the same problem - and the problem was with serverspec and busser-serverspec - it doesn't specify the version so gem install serverspec installed 3.9 (as it didn't include metapackage, just rspec-core) and busser-serverspec installed metapackage rspec with 3.8

Bundler should have worked that out, sounds like there could be an issue with its resolution


Add user defined cohort injection logic into raiwidgets

Description
This change proposes the injection of user defined cohorts defined in SDK into the ResponsibleAIDashboard. The user defined cohorts are added into the dashboard_input as cohortData (which in python world is a list of Cohort class objects.). The injection logic is tested in the test_responsibleai_dashboard.py.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[x] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[ ] No new tests required.
[x] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #1237 (3dd8d16) into main (9578d5a) will decrease coverage by 72.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #1237       +/-   ##
==========================================
- Coverage   75.58%   3.48%   -72.10%
==========================================
  Files          10      10
  Lines         258     258
==========================================
- Hits          195       9      -186
- Misses         63     249      +186

Flag
Coverage Δ

unittests
3.48% <ø> (-72.10%)
:arrow_down:

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

Impacted Files
Coverage Δ

...core_flask/rai_core_flask/environments/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

..._flask/environments/credentialed_vm_environment.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...i_core_flask/environments/public_vm_environment.py
0.00% <0.00%> (-88.89%)
:arrow_down:

...re_flask/environments/local_ipython_environment.py
0.00% <0.00%> (-88.89%)
:arrow_down:

rai_core_flask/rai_core_flask/flask_helper.py
10.76% <0.00%> (-81.54%)
:arrow_down:

...ai_core_flask/environments/azure_nb_environment.py
0.00% <0.00%> (-73.53%)
:arrow_down:

...sk/rai_core_flask/environments/base_environment.py
0.00% <0.00%> (-57.15%)
:arrow_down:

..._core_flask/environments/databricks_environment.py
0.00% <0.00%> (-56.25%)
:arrow_down:

..._core_flask/rai_core_flask/environment_detector.py
0.00% <0.00%> (-53.34%)
:arrow_down:

rai_core_flask/rai_core_flask/__init__.py
66.66% <0.00%> (-33.34%)
:arrow_down:

Continue to review full report at Codecov.

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


Enable HSTS policy on taproot.watch

We will never serve content on HTTP, so to improve security it makes sense to enable HSTS.
Serving via HTTPS is currently out of scope of fork-explorer, so this has to be done on a reverse proxy (Nginx, Apache, Caddy, etc). taproot.watch uses Caddy, so I'll take a look there.

This added to the site block for Caddy should do:
header {
	 Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
}

This sets the HSTS policy and also enables the site to be preloaded within browsers.
Preloading form, after the header is set: https://hstspreload.org/