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

setting .future as defaultRegistery

Open
#25 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
r

Research direction

Start by reading the future.batchtools API around registry handling and compare it with batchtools::setDefaultRegistry() and batchtools::getStatus(). The requested behavior is a wrapper that targets the .future subdirectory and makes getStatus() usable; completion should be defined by that workflow working as described.

Written by the indexing model from the issue text.

Description

feature request

is there a wrapper in future.batchtools to setdefaultRegister() the .future subdirectory. this would open up the possibility of using getStatus.

the analogues in batchtools are

batchtools::setDefaultRegistry(tmp)
batchtools::getStatus()
Dominant language
R
Stars
87
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 futureverse/future.batchtools

All issues in futureverse/future.batchtools

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.