semvec/pypi-packages huggingface dataset:
headerfiles 0.4
Header files inference for C/C++ projects
Requires Python: >=3.7

# headerfiles
Header file inference tool for LLM-based fuzz driver generation to OSS-Fuzz projects

# API

There are two APIs:

```
headerfiles.api

- is_supported_proj
  - Usage: Check if a projection is supported by the API.
  - Return value: True if the projection is supported, False otherwise.

- get_proj_headers
  - Usage: Get the inferred headers for a specific project.
  - Return value: A list of inferred headers for the project, their orders also matter.

```

# Support List (68 projects till now)

- [x] avahi
- [x] bind9
- [x] bluez
- [x] brotli
- [x] capstone
- [x] coturn
- [x] croaring
- [x] dovecot
- [x] igraph
- [x] inchi
- [x] kamailio
- [x] krb5
- [x] lcms
- [x] libarchive
- [x] libbpf
- [x] libcbor
- [x] libcoap
- [x] libdwarf
- [x] libevent
- [x] libexif
- [x] libfido2
- [x] libfuse
- [x] libgd
- [x] libical
- [x] libjpeg-turbo
- [x] libpcap
- [x] librdkafka
- [x] libredwg
- [x] libressl
- [x] libsndfile
- [x] libsodium
- [x] libsrtp
- [x] libssh
- [x] libssh2
- [x] libtasn1
- [x] libtpms
- [x] libusb
- [x] libvips
- [x] libvnc
- [x] libwebsockets
- [x] libxls
- [x] libyang
- [x] lua
- [x] lwan
- [x] mbedtls
- [x] mdbtools
- [x] minizip
- [x] ndpi
- [x] netcdf
- [x] njs
- [x] oniguruma
- [x] openexr
- [x] opusfile
- [x] ostree
- [x] picotls
- [x] pidgin
- [x] pjsip
- [x] proftpd
- [x] pupnp
- [x] sleuthkit
- [x] tidy-html5
- [x] unicorn
- [x] unit
- [x] utf8proc
- [x] vlc
- [x] w3m
- [x] wasm3
- [x] zydis

# Test

```bash
python3 -m tests.test_api
```
robottrace 0.1.0
A tool to generate slack alerts for robot errors.

# Robot Trace

## Overview
**Robot Trace** is a tool designed to monitor Hamilton VENUS robot log folder
for errors and send notifications via Slack. It is based on python Watchdog
and slack webhook API with a simple http request.

## Getting Started
Follow these instructions to set up the project on your local machine for
development and testing purposes.

### Prerequisites
You will need:

- Python 3.x
- pip
- Virtualenv (optional, but recommended for environment management)

### Installation
Clone the repository and set up the environment:
```bash
git clone https://github.com/gorefbitim/robottrace.git
cd robottrace
```

Create and activate a virtual environment:
```bash
python -m venv venv
source venv/bin/activate  # On Windows use `venv\Scripts\activate`
```

Install the required packages:
```bash
pip install -r requirements.txt
```

## Configuring Slack Notifications
To enable Slack notifications, you need to create a Slack App for webhook
integration or bot functionality.

### Creating a Slack App
1. Go to [Your Apps](https://api.slack.com/apps) on the Slack API website.
2. Click **Create New App**, select **From scratch**.
3. Name your app (e.g., "Robot Monitor") and select your workspace.
4. Click **Create App**.

### Configuring Incoming Webhooks (for simple notifications)
1. Select **Incoming Webhooks** from the app settings.
2. Turn on incoming webhooks.
3. Click **Add New Webhook to Workspace**.
4. Choose a channel for the app to post to and authorize it.
5. Copy the webhook URL. Use this URL in Robot Monitor to send messages to
   Slack.

### Setting Bot Token (for interactive features)
1. Go to **OAuth & Permissions** in the app settings.
2. Add bot token scopes such as `chat:write` and `channels:read`.
3. Install the app in your workspace to obtain your Bot User OAuth Access
   Token.

### Usage
Ensure your webhook URL or bot token is set correctly in your project
configuration.

## Running the Application
Run the application with:
```bash
python robottrace.py
```

## Contributing
We welcome contributions! Please see `CONTRIBUTING.md` for how to submit
changes and our code of conduct.

## License
This project is licensed under the GNU General Public License v3.0 - see the
[LICENSE.md](LICENSE) file for more details.

## Acknowledgments
- Thanks to all contributors who help improve this project.
status-check-runner 0.2.0
Status check runner
Requires Python: <4.0,>=3.12

# Status Check Runner

Configure this tool with the `[tool.status-check-runner]` table in your `pyproject.toml`.

```toml
# pyproject.toml

[tool.status-check-runner.python]
paths = ["src", "tests"]

# or, equivalently

[tool.status-check-runner]
python = { paths = ["src", "tests"] }
```
traduire-cli 0.0.5
Traduire CLI
Requires Python: >=3.12

# Traduire CLI interface

First, install the client program. The `trd` program is contained in the
`traduire-cli` package. I recommend using [pipx](https://pipx.pypa.io/stable/)
or something comparable:

    pipx install traduire-cli

You need a configuration file, `~/.config/traduire.toml` which contains one or
more records of the following form:

    [[project]]
    name = "Project name"
    token = "asdf...-1"
    url = "https://traduire.example.com/api/pofile/project-name/"
    path = "..."

The name, token, and URL are taken from your Traduire installation. The path is
the folder where your local checkout of the project resides. The `trd` client
uses the configured path to automatically find the correct settings. Right now
there's no support forspecifying the necessary token and URL parameters
directly. (Contributions would be very welcome for this!)

Then, assuming you have your gettext `.po` files inside `project/locale` you
you should first ensure that they are up-to-date:

    python manage.py makemigrations -a

Next, you can upload the pofiles to the Traduire server. All `trd` invocations
automatically find all `*.po` files in the provided folder and act on all of
them.

    trd submit project/locale

After translating everything you can fetch all updates from the server:

    trd get project/locale

You probably want to compile the catalogs now:

    python manage.py compilemessages

Submitting pofiles only uses the `msgid` values except on the first submit.
Also, it doesn't delete obsolete strings. If you know what you're doing you can
replace the `.po` files on the server:

    trd replace project/locale

The CLI currently doesn't support deleting translation catalogs, that's
restricted to the administration interface.
pygameMax 1.2.0
please email for any issues. Thanks :/
Requires Python: >=3.8

version: 1.0.1
    --Please note that to gain acsess to the main 'Pygame' modle please use the following:

        -import pygameMax
        -import pygameMax.scr
        -pygameMax.scr.pygameMax
        -[varible] = pygameMax.scr.pygameMax.pac.Pygame([WIDTH], [HEIGHT], [COLOR (siting or rgb value)])
________________________________________

This is the second consumer ready version of the pygameMax modle. Please note that their may be bugs and / or issues.


For more info, please reach the pygameMax docs using:

    [varible] = pygameMax.scr.pygameMax.pac.dataSheets.()
    [varible].overview()


Thanks, have fun using this modle!
oarepo-model-builder-ui 4.0.10
Model builder plugin for oarepo-ui

<!--
 Copyright (c) 2022 CESNET

 This software is released under the MIT License.
 https://opensource.org/licenses/MIT
-->

# UI model builder plugin

An [OARepo Model Builder](https://github.com/oarepo/oarepo-model-builder) plugin to generate
user interface layout from model specification.

## Installation

```bash
pip install oarepo-model-builder-ui
```

## Usage

The plugin adds support for UI annotation of the model file:

```yaml
title:
  type: keyword
  label.key: title.label
  label.cs: Název
  label.en: Title
  help.key: title.help
  hint.key: title.hint
  ui:
    detail: <detail component name>
    edit: <edit component name>
    // any other property here - not validated
```

The following files are generated:

```text
<package>
  +- model
    +- ui.json 
  +- templates
    +- <langcode>
      +- LC_MESSAGES
        +- messages.po
        +- messages.mo
```

### i18n

The `po` and `mo` files are standard gettext po files. The translation keys 
are taken from the `*.key` properties. If keys are not specified, they are
generated from the property path (for example, metadata.creator.firstName.label ).

### UI layout

The UI layout is generated as a convenience for other tools, for example for `oarepo-cli`.
It contains simplified layout of the model. Example:

```json
{
  "children": {
    "title": {
      "detail": "fulltext",
      "input": "fulltext",
      "help": "title.help",
      "label": "title.label",
      "hint": "title.hint"
    },
    "providers": {
      "detail": "array",
      "input": "array",
      "help": "providers.help",
      "label": "providers.label",
      "hint": "providers.hint",
      "child": {
        "detail": "provider",
        "input": "provider",
        "children": {
          "name": {
            "detail": "keyword",
            "input": "keyword",
            "help": "providers/name.help",
            "label": "providers/name.label",
            "hint": "providers/name.hint"
          }
        }
      }
    }
  }
}
```

Fields:
 * detail: component used for rendering the detail page
 * input: component used for rendering input
 * help/label/hint: keys to gettext message catalogues