Skip to content

gh 1.4.0 gh_next() returns the same object  #181

@carlosparadis

Description

@carlosparadis

I came across this issue when re-executing source code in a new machine and noticing my

while(!is.null(res){
    res <- gh::gh_next(res)
}

were returning the same page instead of the next page on the new machine, but not in the older machine.

Older machine:

  • R 3.6.1
  • OS X 10.15.7
  • gh 1.2.0

New Machine (issue is here):

  • R 4.2.1
  • OS X 12.6.6
  • gh 1.4.0

After re-installing on the New Machine gh 1.2.0, it worked again.

Minimal Reproducible Example on New Machine

require(devtools)
devtools::install_version("gh", version = "1.4.0", repos = "http://cran.us.r-project.org")
require(gh)

res <- gh::gh("GET /repos/{owner}/{repo}/issues/events",
              owner="Copilot-Language",
              repo="copilot",
              type="IssuesEvent",
              page=1,
              per_page=100,
              .token=token)

res[[1]]$id # 9297015929

res <- gh::gh_next(res)

res[[1]]$id # 9297015929

devtools::install_version("gh", version = "1.2.0", repos = "http://cran.us.r-project.org")
require(gh)

res <- gh::gh("GET /repos/{owner}/{repo}/issues/events",
              owner="Copilot-Language",
              repo="copilot",
              type="IssuesEvent",
              page=1,
              per_page=100,
              .token=token)

res[[1]]$id # 9297015929

res <- gh::gh_next(res)

res[[1]]$id # 8860246024

I did not get any errors or warnings when executing the MRE.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugan unexpected problem or unintended behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions