[Bug][Asana] Story, subtask and tag collectors stop at 100 per task; task and user collectors restart on a full last page

Aberta
  • Algo errado?
#9,365 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 2 dias

@ShivamSharma43 já está trabalhando nisso.

Desde 10/11/2026.

  • #9366 de @ShivamSharma43 — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

Search before asking
  • I had searched in the issues and found no similar issues.
What happened

The Asana collectors don't page through list endpoints correctly.

  1. collectStory, collectSubtask and collectTag (plugins/asana/tasks/{story,subtask,tag}_collector.go) send limit=100 but have no PageSize and no GetNextPageCustomData, so the ApiCollector makes one request per task and never sends offset. Only the first 100 stories, subtasks and tags of each task are collected. Stories include system events (assignments, section moves, due date changes), so busy tasks go past 100.

  2. collectTask and collectUser do page with offset, but their GetNextPageCustomData returns nil, nil when next_page is null:

if resp.NextPage != nil && resp.NextPage.Offset != "" {
	return resp.NextPage.Offset, nil
}
return nil, nil

nil, nil doesn't end the collection. The collector sets CustomData to nil and requests the next page, and the query then has no offset, so it asks for page 1 again. When the last page is full (100 items) and Asana returns "next_page": null, the collector keeps re-collecting the project from the start and saving the same raw rows again.

From the Asana docs (https://developers.asana.com/docs/pagination): limit must be between 1 and 100, and "If there are no more pages available, next_page will be null and no offset will be provided."

What do you expect to happen

All five collectors follow next_page.offset and stop when next_page is null.

How to reproduce
  • Stories: collect a project with a task that has more than 100 stories. _raw_asana_stories has 100 rows for that task.
  • Tasks: the GetNextPageCustomData above returns nil, nil for a full page with "next_page": null, and fetchPagesSequentially in helpers/pluginhelper/api/api_collector.go only stops on a short page or ErrFinishCollect.
Anything else

Proposed fix (I have a PR ready): a shared getNextAsanaPageOffset that returns api.ErrFinishCollect when next_page is null, and a setAsanaPageQuery that sets limit and offset, used by the task, user, story, subtask and tag collectors.

Version

main

Are you willing to submit PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Linguagem predominante
Go
Estrelas
3.2k
Forks
840
Merge médio
1d 21h
PRs com merge (30d)
104

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/devlake

Todas as issues de apache/devlake

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.