fdb-joshua | FoundationDB Correctness service

by FoundationDB Python Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | fdb-joshua Summary

fdb-joshua is a Python library. fdb-joshua has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

joshua is a tool designed to coordinate ephemeral tests of the foundationdb. the architecture is essentially as follows:. at the moment, joshua agent has been designed to "die on failure" rather than deal with failures more elegantly. this is because the environment will just reschedule an agent after its task ends, so it is cheaper and easier to simply have an agent die if it sees something it can’t deal with and allow its environment to be reset rather than to deal with it more elegantly. by design, the current package does not include two dependencies that it will need if one wants to run the agent, namely childsubreaper and subprocess32. the

Support

Quality

Security

License

Reuse

Support

fdb-joshua has a low active ecosystem.

It has 19 star(s) with 22 fork(s). There are 22 watchers for this library.

It had no major release in the last 6 months.

There are 15 open issues and 4 have been closed. On average issues are closed in 42 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of fdb-joshua is current.

Quality

fdb-joshua has 0 bugs and 0 code smells.

Security

fdb-joshua has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fdb-joshua code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fdb-joshua is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

fdb-joshua releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 3255 lines of code, 175 functions and 27 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed fdb-joshua and discovered the below as its top functions. This is intended to give you an instant insight into fdb-joshua implemented functionality, and help decide if they suit your requirements.

Runs an agent
Log the message to the console
Sanitize a file name
Return the path of ensemble files
Open the database
Get the last results of a test ensemble
Get properties for an ensemble
Return the last results of an ensemble
Read results from the ensemble
Run a command
Test if all processes are running
Remove all jobs from the job queue
Print the number of active ensemble sizes
Retrieves the child processes
Kill all children
Set child s children
Redirect a single job
Run an ensemble
Upload a job
Start an ensemble
Upload an ensemble
Create Flask application
Return whether the agent should run
Show the list of failed agents
Download an ensemble
Open database
Delete all runs in a given range

Get all kandi verified functions for this library.

fdb-joshua Key Features

No Key Features are available at this moment for fdb-joshua.

fdb-joshua Examples and Code Snippets

No Code Snippets are available at this moment for fdb-joshua.

Community Discussions

No Community Discussions are available at this moment for fdb-joshua.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fdb-joshua

To run Joshua agent processes, we provide a Docker image that can spawn multiple agent processes. This docker image created by build.sh script, which uses Dockerfile. Note restarting tests need old fdbserver binaries and TLS libraries, which should be saved in Docker/old_binary and Docker/old_tls_library directories, respectively. To start agents, run. The -v parameter is to pass the cluster file /home/centos/joshua/fdb.cluster for the docker to use. Change this parameter path to where the cluster file is stored. By default, agents run under /tmp/joshua_agent/XX/, where XX is the agent ID number. Each agent also produces a log file at /tmp/joshua_agent/XX.log. If an agent died, its working directory is renamed as /tmp/joshua_agent/XX.failed and a new agent with a different ID number will be spawned. Agent spawning events are logged in log file /tmp/joshua_agent/start_agent.log.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: