Merge 7.45.1.dev0 into Bootstrap 5 update branch. Made a first pass at reconciling differences.

 - Legacy-Id: 19945

Author: jennifer-richards

.devcontainer/devcontainer.json

@@ -58,18 +58,19 @@
 
     // Add the IDs of extensions you want installed when the container is created.
     "extensions": [
-        "ms-python.python",
-        "ms-python.vscode-pylance",
-        "ms-azuretools.vscode-docker",
-        "editorconfig.editorconfig",
-        "redhat.vscode-yaml",
-        "visualstudioexptteam.vscodeintellicode",
-        "batisteo.vscode-django",
-        "mutantdino.resourcemonitor",
-        "spmeesseman.vscode-taskexplorer",
-        "mtxr.sqltools",
-        "mtxr.sqltools-driver-mysql"
-    ],
+		"ms-python.python",
+		"ms-python.vscode-pylance",
+		"ms-azuretools.vscode-docker",
+		"editorconfig.editorconfig",
+		"redhat.vscode-yaml",
+		"visualstudioexptteam.vscodeintellicode",
+		"batisteo.vscode-django",
+		"mutantdino.resourcemonitor",
+		"spmeesseman.vscode-taskexplorer",
+		"mtxr.sqltools",
+		"mtxr.sqltools-driver-mysql",
+		"mrmlnc.vscode-duplicate"
+	],
 
     // Use 'forwardPorts' to make a list of ports inside the container available locally.
     "forwardPorts": [8000, 3306],

.devcontainer/docker-compose.extend.yml

@@ -4,7 +4,8 @@ services:
     app:
         environment:
             EDITOR_VSCODE: 1
+            DJANGO_SETTINGS_MODULE: settings_local_sqlitetest
         volumes:
-            - ..:/root/src:cached
+            - ..:/root/src
         # Runs app on the same network as the database container, allows "forwardPorts" in devcontainer.json function.
         network_mode: service:db

.editorconfig

@@ -5,6 +5,8 @@
 root = true
 
 # Settings for IETF datatracker
+# ---------------------------------------------------------
+# PEP8 Style
 
 [*]
 indent_style = space
@@ -14,3 +16,39 @@ charset = utf-8
 # to avoid tripping Henrik's commit hook:
 trim_trailing_whitespace = false
 insert_final_newline = false
+
+# Settings for .github folder
+# ---------------------------------------------------------
+# GitHub Markdown Style
+
+[.github/**]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = false
+insert_final_newline = true
+
+# Settings for client-side JS / Vue files
+# ---------------------------------------------------------
+# StandardJS Style
+
+[client/**]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+# Settings for cypress tests
+# ---------------------------------------------------------
+# StandardJS Style
+
+[cypress/**]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.github/workflows/dev-db-nightly.yml

@@ -0,0 +1,43 @@
+# GITHUB ACTIONS - WORKFLOW
+
+# Build the database dev docker image with the latest database dump every night
+# so that developers don't have to manually build it themselves.
+
+name: Nightly Dev DB Image
+
+# Controls when the workflow will run
+on:
+  schedule:
+    - cron: '0 0 * * *'
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+  
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: datatracker-db
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: ${{ github.ref == 'refs/heads/main' }}
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+          
+      - name: Get Current Date as Tag
+        id: date
+        run: echo "::set-output name=date::$(date +'%Y%m%d')"
+          
+      - name: Docker Build & Push Action
+        uses: mr-smithers-excellent/docker-build-push@v5.6
+        with:
+          image: ${{ env.IMAGE_NAME }}
+          tags: nightly-${{ steps.date.outputs.date }}, latest
+          registry: ${{ env.REGISTRY }}
+          dockerfile: docker/db.Dockerfile
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -54,3 +54,4 @@
 /unix.tag
 *.pyc
 __pycache__
+node_modules

.vscode/tasks.json

@@ -43,7 +43,7 @@
             "problemMatcher": []
         },
         {
-            "label": "Run JS Tests",
+            "label": "Run JS Tests (python)",
             "type": "shell",
             "command": "/usr/local/bin/python",
             "args": [
@@ -117,7 +117,7 @@
             "type": "shell",
             "command": "/bin/bash",
             "args": [
-                "${workspaceFolder}/docker/app-win32-timezone-fix.sh"
+                "${workspaceFolder}/docker/scripts/app-win32-timezone-fix.sh"
             ],
             "presentation": {
                 "echo": true,
@@ -128,6 +128,24 @@
                 "clear": false
             },
             "problemMatcher": []
+        },
+        {
+            "label": "Run JS Tests (cypress)",
+            "type": "shell",
+            "command": "/bin/bash",
+            "args": [
+                "${workspaceFolder}/docker/scripts/app-cypress.sh"
+            ],
+            "group": "test",
+            "presentation": {
+                "echo": true,
+                "reveal": "always",
+                "focus": true,
+                "panel": "new",
+                "showReuseMessage": false,
+                "clear": false
+            },
+            "problemMatcher": []
         }
     ]
 }

CODE_OF_CONDUCT.md

@@ -0,0 +1,33 @@
+# Code of Conduct
+
+This is a reminder of IETF policies in effect on various topics such as patents
+or code of conduct. It is only meant to point you in the right direction.
+Exceptions may apply. The IETF's patent policy and the definition of an IETF
+"contribution" and "participation" are set forth in
+[BCP 79](https://www.rfc-editor.org/info/bcp79); please read it carefully.
+
+As a reminder:
+ * By participating in the IETF, you agree to follow IETF processes and
+policies.
+ * If you are aware that any IETF contribution is covered by patents or patent
+applications that are owned or controlled by you or your sponsor, you must
+disclose that fact, or not participate in the discussion.
+ * As a participant in or attendee to any IETF activity you acknowledge that
+written, audio, video, and photographic records of meetings may be made public.
+ * Personal information that you provide to IETF will be handled in accordance
+with the IETF Privacy Statement.
+ * As a participant or attendee, you agree to work respectfully with other
+participants; please contact the
+[ombudsteam](https://www.ietf.org/contact/ombudsteam/) if you have questions
+or concerns about this.
+
+Definitive information is in the documents listed below and other IETF BCPs.
+For advice, please talk to WG chairs or ADs:
+
+* [BCP 9 (Internet Standards Process)](https://www.rfc-editor.org/info/bcp9)
+* [BCP 25 (Working Group processes)](https://www.rfc-editor.org/info/bcp25)
+* [BCP 25 (Anti-Harassment Procedures)](https://www.rfc-editor.org/info/bcp25)
+* [BCP 54 (Code of Conduct)](https://www.rfc-editor.org/info/bcp54)
+* [BCP 78 (Copyright)](https://www.rfc-editor.org/info/bcp78)
+* [BCP 79 (Patents, Participation)](https://www.rfc-editor.org/info/bcp79)
+* [Privacy Policy](https://www.ietf.org/privacy-policy/)