Fixed black precommit hook by upgrading to new version.

Reformatted all files.

Author: pgm

.pre-commit-config.yaml

@@ -1,8 +1,8 @@
 repos:
-  #  - repo: https://github.com/psf/black
-  #    rev: "19.3b0"
-  #    hooks:
-  #      - id: black
+  - repo: https://github.com/psf/black
+    rev: "26.1.0"
+    hooks:
+      - id: black
   - repo: https://github.com/pre-commit/mirrors-prettier
     rev: "v2.2.1"
     hooks:

arch.md

@@ -21,6 +21,7 @@ Taiga uses a hybrid storage approach:
 - **S3**: Stores the actual data files (raw files, converted files, etc.)
 
 The database schema is managed through SQLAlchemy ORM with Alembic for migrations. Key models include:
+
 - `User`: User accounts and authentication
 - `Entry`: Base class for all content (folders, datasets, etc.)
 - `Folder`: Directory-like containers for organizing content
@@ -30,9 +31,9 @@ The database schema is managed through SQLAlchemy ORM with Alembic for migration
 
 In other words the schema is like:
 
-* Dataset has many
-  * DataVersions has many
-     * DataFile
+- Dataset has many
+  - DataVersions has many
+    - DataFile
 
 Those all have a "ownership model" (meaning, if you delete a dataset, all the versions and files should also be deleted).
 
@@ -48,6 +49,7 @@ The backend is built with Flask and Connexion (for OpenAPI/Swagger integration):
 4. **File Processing**: Conversion between different file formats (CSV, HDF5, etc.)
 
 Key components:
+
 - `taiga2/controllers/endpoint.py`: API endpoint implementations
 - `taiga2/controllers/models_controller.py`: Database operations
 - `taiga2/conv/`: File conversion utilities
@@ -102,4 +104,3 @@ Taiga is deployed as a containerized application:
 1. **Authentication**: Token-based authentication
 2. **Authorization**: Group-based access control (This is not really fully implemented. If there is code about group-based access, I am willing to bet it is half-implement if at all)
 3. **Secure Storage**: Taiga will sign URLs for fetching data from S3 and give them to the client, so that the transfer of large data happens directly between client and S3.
-

autoapp.py

@@ -1,5 +1,6 @@
 # -*- coding: utf-8 -*-
 """Create an application instance."""
+
 import os
 
 from taiga2.api_app import create_app

migrations/versions/028f07e95137_.py

@@ -5,10 +5,10 @@
 Create Date: 2017-07-19 13:50:47.429002
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "028f07e95137"
 down_revision = "adb36ec6d16c"

migrations/versions/1cde9ea7a48f_.py

@@ -1,14 +1,14 @@
 """empty message
 
 Revision ID: 1cde9ea7a48f
-Revises: 
+Revises:
 Create Date: 2017-04-07 13:37:50.512285
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "1cde9ea7a48f"
 down_revision = None

migrations/versions/2af60fdf97d1_update_started_log.py

@@ -5,10 +5,10 @@
 Create Date: 2019-07-18 16:50:09.398289
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "2af60fdf97d1"
 down_revision = "c9d2700c78d4"
@@ -20,8 +20,7 @@ def upgrade():
     # ### commands auto generated by Alembic - please adjust! ###
     # ### end Alembic commands ###
     op.execute("delete from activities")
-    op.execute(
-        """
+    op.execute("""
         INSERT into activities (id, user_id, dataset_id, type, dataset_name, dataset_description, dataset_version, timestamp)
         SELECT uuid_in(md5(random()::text || clock_timestamp()::text)::cstring), u.id, v.dataset_id, 'started_log', de.name, ve.description, v.version, CURRENT_TIMESTAMP
         FROM dataset_versions v
@@ -30,8 +29,7 @@ def upgrade():
         JOIN entries de on de.id = d.id,
         users u
         WHERE u.name = 'admin'
-    """
-    )
+    """)
     op.execute("update entries set description = null where type = 'Dataset'")
 
 

migrations/versions/2d1729557360_replace_figshare_oauth_w_personal_token.py

@@ -5,10 +5,10 @@
 Create Date: 2021-01-05 11:39:13.077740
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "2d1729557360"
 down_revision = "b1e146e20467"

migrations/versions/3b8cc444f691_add_figshare_update_article.py

@@ -5,10 +5,10 @@
 Create Date: 2020-04-29 11:56:21.180582
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "3b8cc444f691"
 down_revision = "e04e7eb4fb16"

migrations/versions/42d37b47160c_.py

@@ -5,11 +5,11 @@
 Create Date: 2018-09-12 14:04:00.510194
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 from sqlalchemy.dialects import postgresql
 
-
 # revision identifiers, used by Alembic.
 revision = "42d37b47160c"
 down_revision = "9c0d7f0a89e8"

migrations/versions/6bf0d302380c_add_compressed_field.py

@@ -5,10 +5,10 @@
 Create Date: 2020-02-12 10:58:23.610440
 
 """
+
 from alembic import op
 import sqlalchemy as sa
 
-
 # revision identifiers, used by Alembic.
 revision = "6bf0d302380c"
 down_revision = "946c898fcded"