Saravanan666/pypi-org huggingface dataset:
Package: chaostoolkit-k6
# Chaos Toolkit Extension for k6.[![Python versions](https://img.shields.io/pypi/pyversions/chaostoolkit-k6.svg)](https://www.python.org/)This project is a collection of [actions][] and [probes][], gathered as an
extension to the [Chaos Toolkit][chaostoolkit].[actions]:http://chaostoolkit.org/reference/api/experiment/#action[probes]:http://chaostoolkit.org/reference/api/experiment/#probe[chaostoolkit]:http://chaostoolkit.org## InstallThis package requires Python 3.5+To be used from your experiment, this package must be installed in the Python
environment where [chaostoolkit][] already lives.` $ pip install-Uchaostoolkit-k6`## UsagePlease explore the code to see existing probes and actions.
## Configuration## ContributeIf you wish to contribute more functions to this package, you are more than
welcome to do so. Please, fork this project, make your changes following the
usual [PEP 8][pep8] code style, sprinkling with tests and submit a PR for
review.[pep8]:https://pycodestyle.readthedocs.io/en/latest/The Chaos Toolkit projects require all contributors must sign a
[Developer Certificate of Origin][dco] on each commit they would like to merge
into the master branch of the repository. Please, make sure you can abide by
the rules of the DCO before submitting a PR.[dco]:https://github.com/probot/dco#how-it-works### DevelopIf you wish to develop on this project, make sure to install the development
dependencies. But first, [create a virtual environment][venv] and then install
those dependencies.[venv]:http://chaostoolkit.org/reference/usage/install/#create-a-virtual-environment`console $ pip install-rrequirements-dev.txt-rrequirements.txt `Then, point your environment to this directory:`console $ pip install-e. `Now, you can edit the files and they will be automatically be seen by your
environment, even when running from thechaoscommand locally.### TestTo run the tests for the project execute the following:` $ pytest `
Package: chaostoolkit-oci
# Chaos Toolkit Extension for OCI[![Build Status](https://travis-ci.org/chaostoolkit-incubator/chaostoolkit-oci.svg?branch=master)](https://travis-ci.org/chaostoolkit-incubator/chaostoolkit-oci)
[![Python versions](https://img.shields.io/pypi/pyversions/chaostoolkit-oci.svg)](https://www.python.org/)This project is a collection of [actions][] and [probes][], gathered as an
extension to the [Chaos Toolkit][chaostoolkit].[actions]:http://chaostoolkit.org/reference/api/experiment/#action[changelog]: ./CHANGELOG.md
[chaostoolkit]:http://chaostoolkit.org[contributing]: ./docs/dev/contribute.md
[experiments]: ./docs/use/experiments.md
[install chaostoolkit-oci]: ./docs/setup/chaostoolkit.md
[keys and ocids]:https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm[oci]: ./docs/setup/oci.md
[oci config]:https://docs.cloud.oracle.com/en-us/iaas/Content/API/Concepts/sdkconfig.htm[probes]:http://chaostoolkit.org/reference/api/experiment/#probe[python]: ./docs/setup/python.md
[virtualenv]: ./docs/setup/venv.md## Setup environment[Install Python and pip][python][Install and create a virtual environment][virtualenv][Install chaostoolkit, chaostoolkit-oci][install chaostoolkit-oci]Configure your [signing keys and obtain your OCIDs][keys and ocids].Create your [OCI Configuration file][oci config].## Using chaostoolkit-oci
[Creating and running chaos experiments][experiments].## Contributing[Contributing to chaostoolkit-oci][contributing].## ChangelogView the [CHANGELOG][changelog].## AcknowledgementChaos installation: [chaostoolkit.org][chaostoolkit]Python, pip installation and virtualenv documentation:https://docs.python-guide.org/### License
Package: chaostoolkit-openstack
chaostoolkit-openstackChaostoolkit driver for OpenstackFree software: BSD licenseFeaturesA minimal chaostoolkit driver for Openstack compute resources.SecretsThe driver probes/actions depends on configuration parameters stored as secrets. An
“openstack” key in the “secrets” experiment section should be present.
The following keys should be defined in it:“region”“auth_url”“project_name”“username”“password”Then in each action/probe used the “openstack” secret should be added as param.ProbesThe driver provides the following probes:# returns 1 if server name exists or 0 othewise
check_server_name(name)ActionsThe driver provides the following actions:# starts a server
start_server(server_name)

# stops a server
stop_server(server_name)

# suspend a server
suspend_server(server_name)

# resume a server
resume_server(server_name)

# pause a server
pause_server(server_name)

# unpause a server
unpause_server(server_name)CreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2019-04-02)First release on PyPI.
Package: chaostoolkit-prometheus
Prometheus extension for the Chaos ToolkitPrometheussupport for theChaos Toolkit.InstallTo be used from your experiment, this package must be installed in the Python
environment wherechaostoolkitalready lives.$ pip install chaostoolkit-prometheusUsageTo use this package, you must create have access to a Prometheus instance via
HTTP and be allowed to connect to it.By default, the Prometheus instance athttp://localhost:9090will be queried.
To override, you need to set up the instance details using theprometheus_base_urlconfiguration property:"configuration":{"prometheus_base_url":"http://my.prometheus.server/"}This package only exports probes to query for some aspects of your system as
monitored by Prometheus.Here is an example of querying Prometheus at a given moment{"type":"probe","name":"fetch-cpu-just-2mn-ago","provider":{"type":"python","module":"chaosprometheus.probes","func":"query","arguments":{"query":"process_cpu_seconds_total{job='websvc'}","when":"2 minutes ago"}}}You can also ask for an interval as follows:{"type":"probe","name":"fetch-cpu-over-interval","provider":{"type":"python","module":"chaosprometheus.probes","func":"query_interval","arguments":{"query":"process_cpu_seconds_total{job='websvc'}","start":"2 minutes ago","end":"now","step":5}}}In both cases, the probe returns theJSON payload as-isfrom Prometheus
or raises an exception when an error is met.The result is not further process and should be found in the generated report
of the experiment run.You can also send metrics to a pushgateway service via a control:{"controls":[{"name":"prometheus","provider":{"type":"python","module":"chaosprometheus.metrics","arguments":{"pushgateway_url":"http://someip:9091","job":"chaostoolkit"}}}]}You can also set three more arguments:grouping_key: A mapping of strings to uniquely aggregate multiple runs
in the Prometheus backendtrace_id: This must be a string which will identify this run uniquely in
your metrics. If none is a provided, a random string is generated.experiment_ref: Sometimes it's useful to identify a particular experiment,
not just its run, throughout many runs. This is the string to do that. If
none is provided, a hash of the experiment is performed and used. The hash
is not stable across changes of the experiment of course.These are particularly useful when you couple this extension with others like
Loki where you want to cross-reference between logs and metrics.ContributeIf you wish to contribute more functions to this package, you are more than
welcome to do so. Please, fork this project, make your changes following the
usualPEP 8code style, sprinkling with tests and submit a PR for
review.
Package: chaostoolkit-reporting
A general purpose reporting generator for Chaos ToolkitThe Chaos Toolkit reporting extension library.PurposeThe purpose of this library is to provide reporting support to theChaos Toolkitexperiment results.FeaturesThe library takes the journal generated by thechaos runcommand
and transforms into a human friendly report. The report can be a standalone
PDF or HTML document.InstallInstall this package as any other Python packages:$pipinstall-Uchaostoolkit-reportingNotice that this draws a fewdependencies:Some of them are LGPL v3 licensed.You will also need toinstall some additional dependenciesthat thechaos reportcommand relies upon.UsageOnce installed, a newreportsubcommand will be made available to thechaoscommand, use it as follows:$chaosreport--export-format=html5journal.jsonreport.htmlor, for a PDF document:$chaosreport--export-format=pdfjournal.jsonreport.pdfYou can also generate a single report from many journals at once:$chaosreport--export-format=pdfjournal-1.jsonjournal-2journal-3report.pdfOr more succinctly:$chaosreport--export-format=pdfjournal-*.jsonreport.pdfDownload a Docker ImageAs the dependencies for this plugin can be difficult to get right, we also
provide a docker image - note that this image is rather big with 1.4Gb to
pull. You can installDockerfrom theDocker Hub.$dockerpullchaostoolkit/reportingUse a Docker containerTo generate a PDF report using the Docker image you must first ensure that you are running the command from where thejournal.jsonfile, generated during an experiment run, can be found. To check for this you can run:$lsAnd you should see thejournal.jsonfile:journal.jsonNow you can run the docker command:$dockerrun\--user`id-u`\-v`pwd`:/tmp/result\-it\chaostoolkit/reportingThis will createchaostoolkit.logandreport.pdffiles in this directory.$lschaostoolkit.log   journal.json   report.pdfThereport.jsonfile will be owned by the user id returned by the commandid -u, it should
be your user. The reason we specify a user is that, by default, the container
runs as root and the image doesn't make a guess about which user will run
the container. If you don't have theidcommand you can set the value
manually as follows instead:--user 1000:1000assuming both your user and
group ids are1000.The default command of the image is equivalent to running this without a
container:$chaosreport--export-format=pdfjournal.jsonreport.pdfIf you wish to override that command, pass thechaos reportparameters as
follows:$dockerrun\--user`id-u`\-v`pwd`:/tmp/result\-it\chaostoolkit/reporting--report--export-format=html5journal.jsonreport.htmlAnd the same files will be created:$lschaostoolkit.log   journal.json   report.pdfContributeContributors to this project are welcome as this is an open-source effort that
seeksdiscussionsand continuous improvement.From a code perspective, if you wish to contribute, you will need to run a
Python 3.7+ environment. Then, fork this repository and submit a PR. The
project cares for code readability and checks the code style to match best
practices defined inPEP8. Please also make sure you provide tests
whenever you submit a PR so we keep the code reliable.
Package: chaostoolkit-slack
Chaos Toolkit Extension for SlackThis project is an extension for the Chaos Toolkit to targetSlack.InstallThis package requires Python 3.7+To be used from your experiment, this package must be installed in the Python
environment wherechaostoolkitalready lives.$ pip install -U chaostoolkit-slackSlack AppTo use this extension, you need to create a Slack app in your workspace.
Please follow the Slack documentation to create a basic app:https://api.slack.com/apps?new_app=1https://api.slack.com/tutorialsYou can start from this manifest if you want:display_information:name:Chaos Toolkit eventslong_description:Get live feedback information of all your Chaos Engineeringexperiments executed from Chaos Toolkit. See which experiments deviated andinvestigate their logs directly from a Slack thread.description:Chaos Engineering experiments live events from Chaos Toolkit.background_color:"#ffffff"settings:org_deploy_enabled:falsesocket_mode_enabled:falseis_hosted:falsetoken_rotation_enabled:falsefeatures:bot_user:display_name:chaostoolkitoauth_config:scopes:bot:-channels:read-chat:write-files:writeOnce your application is created, you may want to set the Chaos Toolkitlogoto clarify to your users where these messages come from.Slack TokenPlease follow the procedure on Slack to create a token suitable for
API calls made using the Python client. The token should start withxoxb-.
You can find the token in your app settings under theOAuth & Permissionspage.The token should have at least the following scopes:channels:read,chat:writeandfiles:writeInstall your Slack appOnce created, you need to install the app in your workspace and invite it in
any channel you wish to send events to. This channel will also have to be part
specified as a controls argument (see below).Now you should be good to go!UsageCurrently, this extension only provides a control to send Chaos
Toolkit events to Slack channels.To use this extension, add the following to your experiment (or settings):"secrets":{"slack":{"token":"xoxb-..."}},"controls":[{"name":"slack","provider":{"type":"python","module":"chaosslack.control","secrets":["slack"],"arguments":{"channel":"general"}}}]ContributeIf you wish to contribute more functions to this package, you are more than
welcome to do so. Please fork this project, make your changes following the
usualPEP 8code style, add appropriate tests and submit a PR for
review.The Chaos Toolkit projects require all contributors must sign aDeveloper Certificate of Originon each commit they would like to merge
into the master branch of the repository. Please, make sure you can abide by
the rules of the DCO before submitting a PR.DevelopIf you wish to develop on this project, make sure to install the development
dependencies. But first,create a virtual environmentand then install
those dependencies.$pipinstall-rrequirements-dev.txt-rrequirements.txtThen, point your environment to this directory:$pipinstall-e.Now, you can edit the files and they will be automatically be seen by your
environment, even when running from thechaoscommand locally.To run the tests for the project execute the following:$ pytest
Package: chaostoolkit-storeevent
chaostoolkit-storeeventA chaostoolkit control to store events on different data stores/monitoring platfomsFree software: BSD licenseDocumentation:https://chaostoolkit-storeevent.readthedocs.io.FeaturesTODOCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.0.9 (2019-03-08)First release on PyPI.
Package: chaostoolkit-utils
A ChaosToolkit package that lists some useful utility actions/probes/controlsProbescheck_site_contentThis probe can be used to check if the content from a http get request matches a pattern.Usage{
    "type": "probe",
    "name": "Check there are no errors...",
    "provider": {
      "arguments": {
        "url": "...",
        "pattern": "any pattern accepted by re...",
        "timeout": x # timeout in seconds, not mandatory...
      },
      "func": "check_site_content",
      "module": "chaostoolkit_utils.probes",
      "type": "python"
    },
Package: chapa
ChapaUnofficial Python SDK forChapa API.InstructionsThis is a Python SDK for Chapa API. It is not official and is not supported by Chapa. It is provided as-is. Anyone can contribute to this project.Installationpip install chapaUsagefromchapaimportChapadata={'email':'abebe@bikila.com','amount':1000,'first_name':'Abebe','last_name':'Bikila','tx_ref':'<your-unique-transaction-id>',# optional'callback_url':'https://www.your-site.com/callback','customization':{'title':'<Your-Company>','description':'Payment for your services',}}chapa=Chapa('<your_api_key>')response=chapa.initialize(**data)print(response['data']['checkout_url'])# Another Implementationchapa=Chapa('<your_api_key>',response_format='obj')response=chapa.initialize(**data)# notice how the response is an objectprint(response.data.checkout_url)# How to verify a transactionresponse=chapa.verify('<your-unique-transaction-id>')ContributingPull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. After that free to contribute to this project. Please read theCONTRIBUTING.mdfile for more information.Please make sure to update tests as appropriate.API ReferenceCreate new TransactionBase endpointhttps://api.chapa.co/v1POST /transaction/initializeParameterTypeDescriptionkeystringRequired. This will be your public key from Chapa. When on test mode use the test key, and when on live mode use the live key.emailstringRequired. A customer’s email. addressamountintegerRequired. The amount you will be charging your customer.first_namestringRequired. Your API keylast_namestringRequired. A customer’s last name.tx_refstringRequired. A unique reference given to each transaction.currencystringRequired. The currency in which all the charges are made. Currency allowed is ETB.callback_urlstringThe URL to redirect the customer to after payment is done.customization[title]stringThe customizations field (optional) allows you to customize the look and feel of the payment modal. You can set a logo, the store name to be displayed (title), and a description for the payment.HEADER KeyValueAuthorizationBearer <YOUR-API-KEY>Verify TransactionGET /transaction/verify/${tx_ref}ParameterTypeDescriptiontx_refstringRequired. A unique reference given to each transactionFAQNo Available Questions!Run LocallyClone the projectgitclonehttps://github.com/chapimenge3/chapa.gitGo to the project directorycdchapaInstall dependenciespipinstall-rrequirements.txtLicenseMITAuthorTemkin Mengistu
Package: chap-backend-replay
chap-backend-replayA proof-of-concept backend plug-in for chap.InstallationIf you installed chap with pip, then runpip install chap-backend-replay.If you installed chap with pipx, then runpipx inject chap chap-backend-replay.Usechap --backend replay -B session:/full/path/to/existing-chap-session.json tuiThere are additional back-end parameters, usechap --backend replay --helpto list them.
Package: chaperone
Chaperone is a lean, full-featured top-level system manager, similar to init, systemd, and others,
but designed for lean container environments like Docker.  It is a single, small program which provides
process clean-up, rudimentary logging, and service management without the overhead of additional
complex configuration.Documentationhttp://garywiz.github.io/chaperonechaperone Sourcehttp://github.com/garywiz/chaperonepypi linkhttp://pypi.python.org/pypi/chaperone
Package: chapicha
ChapichaA semi-automated image editing toolInstallationInstall chapicha from source usingPoetrygitclonehttps://github.com/julius383/chapichacdchapichapoetryinstallInstall using pippipinstallchapichaUsage/ExamplesUsage: chapicha [OPTIONS] COMMAND [ARGS]...

Options:
  --version       Show the version and exit.
  --verbose TEXT
  --help          Show this message and exit.

Commands:
  color  Find the most dominant colors in image
  crop   Crop images to given dimensions
  ocr    Try and recognize text present in an image
  scale  Scale down an image by a given factorLicenseMIT
Package: chapisha
Chapisha: docx to standards-compliant epub3 conversionWhat is it?Chapishaprovides an intuitive method for converting a well-formatted Microsoft Word.docxfile into a
standards-compliant EPUB3 ebook.There are only a small number of steps required to create your.epub, andChapishawill provide an appropriate
stylesheet and take care of document structure:Set the working directory where you want to create your.epub,Define and validate the metadata required for the creative work,Import thedocxfile,Import the cover image,Define and add any contributors, such as cover artist,Define your creative work's publication rights,Add in an optional dedication,Build your creative work as an EPUB3 standards-compliant ebook.Read the docsWhy use it?Chapishais easy-to-use, quick, and fits into your workflow.There are a multitude of.epubconversion tools but few that support the day-to-day workflow and tools used by most
jobbing writers: Microsoft Word.Chapishadraws onPandocfor document conversion and ebook creation, adding a
simple, stateless Python frame around it, which means you can also include it in a web application.Installation and dependenciesYou'll need at least Python 3.9, then:pip install chapishaYou will also need to installPandocandJava:sudo apt install pandoc default-jreChangelogThe version history can be found in thechangelog.BackgroundChapishawas created to serve my needs as both a formally, and self-published, author. I have written two
novels -Lament for the fallenandOur memory like dust- and a number ofshort stories. These works are available to read online, and to download
as an ebook.Chapishais theSwahiliword for 'publish' or 'post'.LicenceBSD 3Other licenced elements:Samara logois copyrightWhythawkandQwyre.Cover photois copyright Rodd Halstead, licenced under commercial terms to Whythawk, and used here for test purposes.Usan Abasi's Lamentis copyright Gavin Chait, licencedCC BY-NC-SA 4.0and used here for test purposes.
Package: chappie-ai
Chappie.aiDescriptionThe following is framework for developing reinforcement learning (rl) agents. This bot has been designed as a general framework for performing a multitude of tasks with minimal teaching.Installation Instructionspip install --upgrade chappie_aiImport InstructionsimportchappieWrite UpTo get a better understanding of why the code is written this way check out my detailed write up:https://medium.com/@bellerb/playing-chess-with-a-generalized-ai-b83d64ac71fehttps://medium.com/@bellerb/playing-chess-with-offline-reinforcement-learning-411edc5efd5fhttps://medium.com/@bellerb/retrieval-transformer-enhanced-reinforcement-learning-24509e97c4c6
Package: chapsnap
ChapSnapResync Chapters by snapping them to Scene Changes.UsageUsage: chapsnap [OPTIONS] VIDEO [CHAPTERS]

  Snap Chapters to Scene Changes.

  VIDEO       The video file to snap chapters to scene changes. All video formats are
              supported. You may alternatively provide a directory path to process
              video files in batch.
  [CHAPTERS]  Optional chapters file if you want to use chapters from a file
              rather than ones already muxed with the video.

Options:
  -t, --threshold FLOAT  Threshold on Scene Change probability scores. The
                         lower the value, the more unlikely the frame is to be
                         a Scene Change. Range: 0.0 (Impossible) - 1.0
                         (Definite).
  -o, --offset FLOAT     Offset to apply to each Chapter. A negative offset
                         may result in fewer Chapters.
  --trim INTEGER         Remove n Chapters from the start of the Video. A
                         negative value will remove n Chapters from the end of
                         the Video. Timestamps will be offset respectively.
  -nf, --no-forward      Do not try to resync Chapters forward in time.
  -nb, --no-backward     Do not try to resync Chapters backward in time.
  -k, --keyframes        Only sync to Scene Changes on Keyframes (I-frames).
  -0, --zero             Force the first chapter to be at `00:00:00.000`, even
                         after offsets and trims.
  -c, --chain            Chain sync adjustments from one Chapter to the next.
                         E.g., Chapter 1 had -2, so Chapter 2 will begin with
                         an offset of -2. Chapter 2 with -2 has a change of
                         -1, so Chapter 3 will begin with an offset of -3 and
                         so on.
  --overwrite            Apply new Chapters to the input video file in-place,
                         without making a duplicate.
  --help                 Show this message and exit.ContributorsLicense© 2023 rlaphoenix —GNU General Public License, Version 3.0