accessibility-insights-web icon indicating copy to clipboard operation
accessibility-insights-web copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Issue filling fails with "Query String too long" error

Open Shobhit1 opened this issue 5 years ago • 3 comments

Describe the bug

When I tried to use "File Issue" feature on the Issue dialog popup, the process fails with following errors:

  1. Azure boards: "Query string too long"
  2. Github: 2FA fails with 500 error.

To Reproduce Steps to reproduce the behavior: Prerequisite: You should not be logged in Azure devops or github before this

  1. Go to "any target page'
  2. Click on Accessibility Insights popup windows and press settings to configure Issue filling.

Part 1:

  1. Choose Github as the option and put in a url for your repo.
  2. Fast Pass the target page
  3. Turn on the visualizations for accessibility issues found
  4. Click on the red exclamation mark to open Issue dialog
  5. Click on the File Issue button and try to login

Part 2:

  1. Choose Azure board as the option and put in a url for your repo.
  2. Fast Pass the target page
  3. Turn on the visualizations for accessibility issues found
  4. Click on the red exclamation mark to open Issue dialog
  5. Click on the File Issue button and try to login

Expected behavior

It should successfully file an issue or create an issue after logging you in for the specific service provider (github or azure boards)

If applicable, add screenshots to help explain your problem.

Extension (please complete the following information)

  • OS: Windows 10
  • Version: 10.0.17763 Build 17763
  • Chrome Version: 74.0.3729.108 (Official Build) beta (64-bit)

Are you willing to submit a PR?

Yes

Did you search for similar existing issues?

Yes

Did you search for similar issues in our github issues or on stackoverflow

Yes

Shobhit1 avatar Apr 23 '19 20:04 Shobhit1

This issue has been marked as requiring additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, please update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

msft-github-bot avatar Apr 23 '19 21:04 msft-github-bot

I have reached out to GitHub support to get their thoughts on the GitHub length. For me a URL of 1938 characters leads to the 500 server error if the user is logged out. This link is an example. When the user is logged in, we can add many more characters.

karanbirsingh avatar Jun 11 '19 18:06 karanbirsingh

I got a response - the team has acknowledged the issue and will follow up with me when they have more info. No ETA.

karanbirsingh avatar Jun 26 '19 19:06 karanbirsingh