Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement scalability refactor for miner #94

Open
juanmanso opened this issue Jun 13, 2024 · 5 comments
Open

Implement scalability refactor for miner #94

juanmanso opened this issue Jun 13, 2024 · 5 comments
Labels

Comments

@juanmanso
Copy link
Contributor

juanmanso commented Jun 13, 2024

Description

After masa-finance/bt-refactor-spike#1, we are now able to put this refactor into action on the masa-bittensor repo.

TL;DR for planning:

  • use self.axon.attach() for miner instead of what we have now
  • define a way to generate synapses for each task
  • follow the folder structure suggested

Use as reference the draft PR which spikes the implementation

Acceptance criteria

@juanmanso
Copy link
Contributor Author

Blocked by masa-finance/bt-refactor-spike#1

@juanmanso juanmanso changed the title Implement scalability refactor Implement scalability refactor for miner Jun 24, 2024
@juanmanso
Copy link
Contributor Author

juanmanso commented Jun 24, 2024

Unblocked by masa-finance/bt-refactor-spike#1

@juanmanso juanmanso removed the blocked label Jun 24, 2024
@mudler mudler added triage and removed task labels Jun 24, 2024
@juanmanso
Copy link
Contributor Author

juanmanso commented Jul 1, 2024

I think this is ready for development

EDIT: I think that triage here means that it might not be well defined. What I meant with the previous text is that I think this is defined enough so we can remove the triage label and as a team select it for ready either above or below the waterline

@juanmanso
Copy link
Contributor Author

I think this is ready for development

EDIT: I think that triage here means that it might not be well defined. What I meant with the previous text is that I think this is defined enough so we can remove the triage label and as a team select it for ready either above or below the waterline

+1

@juanmanso
Copy link
Contributor Author

I think this is ready for development
EDIT: I think that triage here means that it might not be well defined. What I meant with the previous text is that I think this is defined enough so we can remove the triage label and as a team select it for ready either above or below the waterline

+1

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants