Is there a plan to add a CONTRIBUTING.md? This could include template to do a PR, guidelines to add tests, coding standards, etc.

I'm currently learning Rust and am very interested in contributing on this project somehow. Thanks!

As part of clarifying what is part of the open source offering and what is examples or private code, we should signal these differences using package names/namespaces.

Suggested solution:

• Let all public, published packages retain their @backstage namespace.
• Change all private packages in the open source project (plugins/home-page, plugins/welcome) to be under an @internal names

package.json's main field seems to be aimed directly at npm, not browsers. So perhaps if there are no jsdelivr or browser fields, then the /dist folder should be the next highest priority when looking for the default file?

Example:
spectacle: main (so jsdelivr's default) = [/lib/index.js](https://cdn.jsdelivr.net/npm/spectacle@4.3.

Is there a method for setting a timeout period for an observer? For example, say the observer is a SQL database, and that database becomes inaccessible for a few minutes. Right now, the experiment simply fails. Is there an argument somewhere to avoid such a situation? Particularly for multi-day experiments.

When I'm using doctl as part of a CI/CD process, I want to be able to set a custom expiration time when calling kubernetes cluster kubeconfig {save,show} so that I can feel secure and not have long lived API tokens that need to be manually cleaned up.

This is supported in the API and in godo:

https://developers.digitalocean.com/documentation/v2/#retrieve-the-kubeconfig-for-a-kubernetes-c

(I will compile a list and hopefully open a PR if needed)

Describe the bug
This behavior is present in a plethora of catalyst's callbacks and losses. It's consistent, but it's definitely confusing for many new users.

To Reproduce
Steps to reproduce the behavior:
Use these functions/classes:
Callbacks

• [MeterMetricsCallback](https://github.com/catalyst-team/catalyst/blob/mas

Issue type

• Bug Report

Build number

master branch

Configuration

Deployed as a Stack Set, with a CloudWatch Rule triggering the function

Summary

Can't confirm completely, but I believe the logger which is created from main.go 's setupLogging function does not get created, and therefore

The AWS walkthrough states the only required policies are AmazonEC2FullAccess, AutoscalingFullAccess & AmazonVPCFull Access.
However, the AWS Walkthrough fails with the following message:

2019-06-24T02:46:13+05:30 [✖]  Error during apply of atomic reconciler, attempting clawback: AccessDenied: User: arn:aws:iam::406569211866:user/k

We've tried for feature parity, but there are certain things that are still specific to one of the proxies. It would be helpful to have some sort of documentation tag for these features.

Hi,

In the documentation, it says that Mitogen can be used with Fabric:

the goal is to provide a robust and efficient low-level API on which tools like Salt, Ansible, or Fabric can be built, and while the API is quite friendly and comparable to Fabric, ultimately it is not intended for direct use by consumer software. """

I am having a hard time to find an example of example of Fabric

I can see some basic support in Sceptre for AWS SAM although there don't appear to be any code examples or blog posts and it's unclear to me how you would actually do SAM in Sceptre, especially after SAM's guided deploy mode became the standard.

In the mean time, can anyone suggest the high level approach- would I create a Python wrapper to call the SAM CLI to do sam build and sam package a

https://www.usenix.org/conference/opml19/program

Prepare to read papers

** Question : **

I arrived here and am interested in leveraging this platform in addition to and as a compliment terratest, but I don't want to start from scratch in writing features and I can't find any reference at all in the readme to a sample library or folder of already-existing tests/features. I could copy-paste all the examples from the .md example files but that seems like more work

In the CI automated generated docs of the control repo, we can add documentation generated automatically showing classes usage in different nodes.

# fc29
dnf install -y docker docker-compose

# docker-1.13.1-62.git9cb56fd.fc29.src.rpm
# docker-compose-1.22.0-2.fc29.src.rpm

What's a good way to make this (only installing from a limited set of package repos) optional?

I'm not very experienced with Caddy, because for now, I've always resorted to simply using Nginx, however I'm finding some difficulties when setting up Caddy and Vigil.

To check that it wasn't Caddy's fault, I have also tried to reverse proxy other webpages, and everything seemed to work perfectly fine.

And to be perfectly clear, serving Vigil over port 8080 (HTTP only) also works perfectly