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

work item query -- too many 500 responses #207

Closed
clarkbreyman-yammer opened this issue Sep 8, 2018 · 2 comments
Closed

work item query -- too many 500 responses #207

clarkbreyman-yammer opened this issue Sep 8, 2018 · 2 comments
Assignees
Labels
bug done Code complete - will be released with the next major update to the CLI

Comments

@clarkbreyman-yammer
Copy link

bash-4.3# vsts work item query --instance https://REDACTED.visualstudio.com --project REDACTED --wiql 'select [System.ID], [System.Title] from workitems'

Generates the following error. Latest docker client.

Error occurred in request., RetryError: HTTPSConnectionPool(host='yammer.visualstudio.com', port=443): Max retries exceeded with url: /_apis/wit/workItems?ids=22%2C23%2C24%2C25%2C26%2C28%2C29%2C31%2C33%2C34%2C35%2C36%2C37%2C38%2C39%2C40%2C41%2C43%2C44%2C45%2C49%2C50%2C52%2C56%2C57%2C59%2C60%2C61%2C62%2C63%2C64%2C65%2C67%2C68%2C69%2C71%2C72%2C73%2C74%2C75%2C85%2C86%2C87%2C88%2C89%2C90%2C91%2C92%2C93%2C94%2C95%2C96%2C97%2C98%2C99%2C100%2C101%2C102%2C103%2C104%2C105%2C106%2C107%2C108%2C109%2C110%2C111%2C112%2C113%2C114%2C115%2C116%2C117%2C118%2C119%2C120%2C121%2C122%2C123%2C124%2C125%2C126%2C127%2C128%2C139%2C140%2C142%2C143%2C144%2C145%2C146%2C147%2C149%2C150%2C151%2C152%2C154%2C155%2C156%2C157%2C158%2C159%2C160%2C161%2C162%2C163%2C164%2C165%2C166%2C167%2C168%2C169%2C170%2C171%2C172%2C173%2C174%2C175%2C176%2C177%2C178%2C179%2C180%2C181%2C182%2C183%2C185%2C186%2C187%2C188%2C190%2C191%2C194%2C195%2C196%2C197%2C198%2C199%2C200%2C201%2C202%2C203%2C204%2C205%2C206%2C207%2C208%2C209%2C210%2C211%2C212%2C213%2C214%2C215%2C216%2C217%2C218%2C219%2C220%2C221%2C222%2C223%2C224%2C225%2C226%2C227%2C228%2C236%2C240%2C241%2C242%2C243%2C244%2C245%2C246%2C247%2C248%2C250%2C251%2C252%2C253%2C256%2C257%2C258%2C261%2C262%2C263%2C264%2C265%2C266%2C267%2C268%2C269%2C270%2C271%2C272%2C273%2C274%2C275%2C276%2C277%2C278%2C279%2C280%2C281%2C282%2C283%2C284%2C285%2C287%2C288%2C289%2C290%2C292%2C293%2C294%2C295%2C296%2C297%2C298%2C299%2C300%2C301%2C302%2C303%2C304%2C305%2C306%2C307%2C308%2C309%2C310%2C311%2C312%2C313%2C314%2C315%2C316%2C317%2C318%2C319%2C320%2C321%2C322%2C323%2C324%2C325%2C326%2C327%2C328%2C329%2C330%2C331%2C332%2C333%2C335%2C336%2C337%2C338%2C339%2C340%2C341%2C342%2C343%2C344%2C345%2C346%2C347%2C348%2C349%2C350%2C351%2C352%2C353%2C354%2C355%2C356%2C358%2C359%2C360%2C361%2C362%2C363%2C364%2C365%2C366%2C367%2C368%2C369%2C370%2C371%2C372%2C373%2C374%2C375%2C376%2C377%2C378%2C379%2C380%2C381%2C382%2C383%2C384%2C385%2C386%2C387%2C388%2C389%2C390%2C391%2C392&fields=System.Id%2CSystem.Title&asOf=2018-09-08T01%3A09%3A33.740Z (Caused by ResponseError('too many 500 error responses',))

@jetzerb
Copy link

jetzerb commented Sep 14, 2018

I'm getting the same error.
Works fine to get a full dump using "select *":
vsts work item query --wiql "select * from workitems"
But selecting specific attributes causes it to fail with the "too many 500 error responses" message:
vsts work item query --wiql "select [System.ID] from workitems"

On my system, it's related to the number of records returned. If my query returns up to 202 records, all is well. If it should return 203 or more, I get the "too many 500 error responses" message. And it doesn't matter how much content each returned record contains either. Both of these queries work fine (note that even though my cutoff is work item id 260, it's only returning 202 records):

$ vsts work item query --wiql "select [System.ID] from workitems where [System.ID] <= 260"
$ vsts work item query --wiql "select [System.ID],[System.Title],[System.AssignedTo],[System.WorkItemType] from workitems where [System.ID] <= 260"

I turned on logging

$ vsts configure --enable-log-file yes

and then ran "select [System.ID] from workitems where [System.ID] <= n" queries where n was 260 (works fine) and 261 (fails). I've attached the resulting log files.

vsts.log.fail.txt
vsts.log.success.txt

This is a fresh install of vsts-cli this morning in a Ubuntu-based Docker container

$ uname -a
Linux MyHostName 4.9.93-linuxkit-aufs #1 SMP Wed Aug 1 15:00:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ vsts --version
vsts-cli (0.1.3)

knack (0.4.1)
vsts (0.1.16)
vsts-cli-admin (0.1.3)
vsts-cli-admin-common (0.1.3)
vsts-cli-build (0.1.3)
vsts-cli-build-common (0.1.3)
vsts-cli-code (0.1.3)
vsts-cli-code-common (0.1.3)
vsts-cli-common (0.1.3)
vsts-cli-package (0.1.3)
vsts-cli-package-common (0.1.3)
vsts-cli-team (0.1.3)
vsts-cli-team-common (0.1.3)
vsts-cli-work (0.1.3)
vsts-cli-work-common (0.1.3)

Python (Linux) 3.6.5 (default, Apr  1 2018, 05:46:30)
[GCC 7.3.0]

Python location: /opt/vsts-cli/bin/python

Legal docs and information: https://aka.ms/vsts-cli-eula

@tedchamb tedchamb added the bug label Oct 12, 2018
@atbagga atbagga added the done Code complete - will be released with the next major update to the CLI label Nov 2, 2018
@atbagga
Copy link
Collaborator

atbagga commented Nov 29, 2018

Fixed in version 0.1.4.

@atbagga atbagga closed this as completed Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug done Code complete - will be released with the next major update to the CLI
Projects
None yet
Development

No branches or pull requests

5 participants