WIP: runtime browser

.coveragerc

@@ -0,0 +1,7 @@
+[run]
+omit = 
+  ./nuclei/*
+  ./routers/*
+  ./setup.py
+  ./tests/*
+  ./env/*

.dockerignore

@@ -0,0 +1,21 @@
+**/data/
+**/*.log
+**/*.png
+**/*.pstats
+**/*.ipynb
+**/bittensor.egg-info/*
+**/lib/*
+**/build/*
+**/dist/*
+**/runs/*
+**/env/*
+**/venv/*
+**/tmp/*
+**/test_results/*
+**/__pycache__/*
+**/.circleci
+**/.git
+**/.github
+**/.hypothesis
+**/.vscode
+**/.gitignore

.flake8

@@ -0,0 +1,4 @@
+[flake8]
+max-line-length = 120
+exclude = .git,__pycache__, __init__.py, docs/source/conf.py,old,build,dist,venv,.venv,.tox
+select = E9,F63,F7,F82,F401

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,59 @@
+name: Bug report
+description: Create a report to help us improve
+labels: [bug]
+assignees: []
+
+body:
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: To Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Go to '...'
+        2. Run command '...'
+        3. Scroll down to '....'
+        4. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots to help explain your problem.
+    validations:
+      required: false
+
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: Please specify your OS and Distro, and Bittensor Version.
+      placeholder: "OS and Distro: [e.g. Linux Ubuntu, Linux Fedora, etc.], Bittensor Version [e.g. 22]"
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,38 @@
+name: Feature request
+description: Suggest an idea for this project
+labels: [feature]
+assignees: []
+
+body:
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is.
+      placeholder: "Ex. I'm always frustrated when [...]"
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE/bug_fix.md

@@ -0,0 +1,63 @@
+<!--
+
+### Requirements for Contributing a Bug Fix
+
+* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* The pull request must only fix an existing bug. To contribute other changes, you must use a different template.
+* The pull request must update the test suite to demonstrate the changed functionality.
+* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution.
+
+-->
+
+### Bug
+
+<!-- Link to the issue describing the bug that you're fixing. -->
+
+### Description of the Change
+
+<!--
+
+We must be able to understand the design of your change from this description.
+If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion.
+Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Alternate Designs
+
+<!-- Explain what other alternates were considered and why the proposed version was selected -->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification Process
+
+<!--
+
+What process did you follow to verify that the change has not introduced any regressions?
+Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
+
+-->
+
+### Release Notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in
+terms that a user can understand. This text will be used in release notes.
+
+If this change is not user-facing or notable enough to be included in release notes
+you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->
+
+
+### Branch Acknowledgement
+[ ] I am acknowledging that I am opening this branch against `staging`

.github/PULL_REQUEST_TEMPLATE/feature_change.md

@@ -0,0 +1,58 @@
+### Requirements for Adding, Changing, or Removing a Feature
+
+* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* The pull request must contribute a change that has been endorsed by the maintainer team. See details in the template below.
+* The pull request must update the test suite to exercise the updated functionality.
+* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution.
+
+### Description of the Change
+
+<!--
+
+We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Alternate Designs
+
+<!-- Explain what other alternates were considered and why the proposed version was selected -->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification Process
+
+<!--
+
+What process did you follow to verify that your change has the desired effects?
+
+- How did you verify that all new functionality works as expected?
+- How did you verify that all changed functionality works as expected?
+- How did you verify that the change has not introduced any regressions?
+
+Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
+
+-->
+
+### Release Notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in
+terms that a user can understand. This text will be used in release notes.
+
+If this change is not user-facing or notable enough to be included in release notes
+you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->
+
+
+### Branch Acknowledgement
+[ ] I am acknowledging that I am opening this branch against `staging`

.github/PULL_REQUEST_TEMPLATE/performance_improvement.md

@@ -0,0 +1,59 @@
+### Requirements for Contributing a Performance Improvement
+
+* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* The pull request must only affect performance of existing functionality
+* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution.
+
+### Description of the Change
+
+<!--
+
+We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Quantitative Performance Benefits
+
+<!--
+
+Describe the exact performance improvement observed (for example, reduced time to complete an operation, reduced memory use, etc.). Describe how you measured this change. Bonus points for including graphs that demonstrate the improvement or attached dumps from the built-in profiling tools.
+
+-->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification Process
+
+<!--
+
+What process did you follow to verify that the change has not introduced any regressions? Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
+
+-->
+
+### Applicable Issues
+
+<!-- Enter any applicable Issues here -->
+
+### Release Notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in
+terms that a user can understand.  This text will be used in release notes.
+
+If this change is not user-facing or notable enough to be included in release notes
+you may use the strings "Not applicable" or "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to add co-authors to commits.
+- Fixed an issue where multiple cursors did not work in a file with a single line.
+- Increased the performance of searching and replacing across a whole project.
+
+-->
+
+
+### Branch Acknowledgement
+[ ] I am acknowledging that I am opening this branch against `staging`

.github/auto_assign.yml

@@ -0,0 +1,7 @@
+addReviewers: true
+
+# A list of team slugs to add as assignees
+reviewers:
+  - opentensor/cortex
+
+numberOfReviewers: 0

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "daily"
+    open-pull-requests-limit: 0  # Only security updates will be opened as PRs

.github/pull_request_template.md

@@ -0,0 +1,10 @@
+Welcome!
+
+Due to [GitHub limitations](https://github.com/orgs/community/discussions/4620),
+please switch to **Preview** for links to render properly.
+
+Please choose the right template for your pull request:
+
+- 🐛 Are you fixing a bug? [Bug fix](?expand=1&template=bug_fix.md)
+- 📈 Are you improving performance? [Performance improvement](?expand=1&template=performance_improvement.md)
+- 💻 Are you changing functionality? [Feature change](?expand=1&template=feature_change.md)