initial commit

.flake8

@@ -0,0 +1,7 @@
+[flake8]
+max-line-length = 120
+per-file-ignores =
+    __init__.py:F401
+    evaluation/infinite_bench/create_huggingface_dataset.py:E501
+# E203, W503 - black-compatible config
+extend-ignore = E203, W503

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F41B Bug Report"
+about: Create a bug report
+title: "[BUG]"
+labels: type/bug
+assignees: ''
+---
+
+### 🐛 Bug
+
+<!-- A clear and concise description of what the bug is. Please include the full error stack trace, if applicable.-->
+
+### To Reproduce
+
+<!-- Steps to reproduce the behavior. Please include the code if possible. -->
+
+### Repository version
+<!-- Please provide the commit hash of the version you are using (running `git rev-parse HEAD`) in your report. -->

.github/ISSUE_TEMPLATE/code-improvement.md

@@ -0,0 +1,15 @@
+---
+name: "\U0001F527 Code improvement"
+about: Suggest a code improvement, e.g. refactoring, deprecation, etc.
+title: "[CODE IMPROVEMENT]"
+labels: area/core
+assignees: ''
+---
+
+### 🔧 Proposed code refactoring
+
+<!-- A clear and concise description of the code improvement -->
+
+### Motivation
+
+<!-- Please outline the motivation for the proposal. If this is related to another GitHub issue, please link here too -->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,15 @@
+---
+name: "\U0001F680 Feature Request"
+about: Submit a proposal/request for a new feature
+title: "[FEATURE]"
+labels: type/feature
+assignees: ''
+---
+
+### 🚀 Feature
+
+<!-- A clear and concise description of the feature proposal -->
+
+### Motivation
+
+<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

.github/ISSUE_TEMPLATE/new-press.md

@@ -0,0 +1,15 @@
+---
+name: "\U0001F680 New press Request"
+about: Submit a proposal/request for a new press
+title: "[NEW PRESS]"
+labels: type/feature
+assignees: ''
+---
+
+### 🆕 Press
+
+<!-- A clear and concise description of the new press, include any links to relevant papers or resources -->
+
+### Motivation
+
+<!-- Please outline the motivation for the proposal. Is your press different from existing ones? If so, how? -->

.github/workflows/python-publish.yml

@@ -0,0 +1,31 @@
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  deploy:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Set up Python
+      uses: actions/setup-python@v3
+      with:
+        python-version: 3.10.11
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build
+    - name: Build package
+      run: python -m build
+    - name: Publish package
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        user: __token__
+        password: ${{ secrets.PYPI_API_TOKEN }}

.github/workflows/style.yml

@@ -0,0 +1,24 @@
+name: Style
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+
+jobs:
+  style:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.10.11
+      - name: Install and configure Poetry
+        uses: snok/install-poetry@v1
+        with:
+          version: 1.8.2
+
+      - run: poetry install --with dev
+      - name: Run style checks
+        run: make style

.github/workflows/test.yml

@@ -0,0 +1,24 @@
+name: Test
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.10.11
+      - name: Install and configure Poetry
+        uses: snok/install-poetry@v1
+        with:
+          version: 1.8.2
+
+      - run: poetry install --with dev
+      - uses: actions/checkout@v3
+      - run: make test

.gitignore

@@ -0,0 +1,168 @@
+dev_notebooks/
+results/
+reports/
+.DS_Store
+poetry.lock
+*.parquet
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+*.pkl
+*.pickle
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+evaluation/loogle/results/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/