Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Gaps in testing (local Python --> local GDrive --> Colab)

Open
  • Is something wrong?
#9,411 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
testing-qa

Research direction

No repository files or tests are named. Reproduce the data-owner and data-scientist workflows across local Python, local GDrive, and Colab, starting with do_client.approve_peer_request(ds_email) and the dataset-creation users parameter. Done means the differences are reproduced and the expected behavior is established for each environment.

Written by the indexing model from the issue text.

Description

Type: Testing :test_tube:

Description

In minimizing the gap between local testing and Colab testing, few differences I found.

  1. I have to explicitly approve the peer request at the data owner side: do_client.approve_peer_request(ds_email)
  2. In dataset creation for DS to view the DO's datasets, users parameter is optional in local python and local GDrive but in necessary in Colab.
Image
Dominant language
Python
Stars
10k
Forks
2k
Avg merge
23h 19m
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenMined/PySyft

All issues in OpenMined/PySyft

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.