Roman
Roman
Since e2e tests take a lot of time to investigate, it was decided to do this in the next PR, after the merger. Related PR https://github.com/opentensor/bittensor/pull/2084
Merge staging in merge-async is required to keep the code base up to date.
### The current task will cover 2 goals: 1. Avoiding multiple code duplication 2. Maintaining strict class architectures for creating command classes. ### AC: - [ ] The classes of...
### Is your feature request related to a problem? Please describe. As a next step after `bittensor/subtensor.py` migrated to async the `bittensor/extrinsic` sub-package have to be next one. ### Describe...
### Is your feature request related to a problem? Please describe. The feature related with following issues: - [subtensor: UI and python client get the error types and error docs...
### Is your feature request related to a problem? Please describe. It comes from here https://discord.com/channels/799672011265015819/1176889593136693339/1243454643569299477 ### Describe the solution you'd like Since creating a network (for test purposes) costs...
### Is your feature request related to a problem? Please describe. As part of [Refactoring of the Bittensor codebase](https://github.com/opentensor/bittensor/issues/1882) ### Describe the solution you'd like - [ ] Style refactoring...
## Is your feature request related to a problem? Please describe. The current Bittensor package lacks consistent coding standards across its various modules, which сan led to maintainability issues. This...
### Is your feature request related to a problem? Please describe. As a part of https://github.com/opentensor/bittensor/issues/1882 ### Describe the solution you'd like - [x] Style refactoring - [x] Сode refactoring...
### Is your feature request related to a problem? Please describe. Create/describe, obtain approval, and implement into the process the documentation of the general Bittensor development standard for the Cortex...