You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing a problem with the CircleCI JSON check where it fails to load status for one branch but is able to load the status for another branch. Using the CircleCI status only check works for this branch. I tried running the curl requests directly and saw that the sizes of the results differed dramatically (125KB for working check vs 263KB for the broken one). I don't see any error messages when I run Checkman in the terminal so that I can see its output (all I see is periodic FSChangesNotifier - didNoticeChangeToPath: /Users/username). If the size is the source of the problem, possibly limiting the count of pulled builds would solve the problem (the JSON endpoint supports a limit=10 parameter).
The text was updated successfully, but these errors were encountered:
I am seeing a problem with the CircleCI JSON check where it fails to load status for one branch but is able to load the status for another branch. Using the CircleCI status only check works for this branch. I tried running the curl requests directly and saw that the sizes of the results differed dramatically (125KB for working check vs 263KB for the broken one). I don't see any error messages when I run Checkman in the terminal so that I can see its output (all I see is periodic
FSChangesNotifier - didNoticeChangeToPath: /Users/username
). If the size is the source of the problem, possibly limiting the count of pulled builds would solve the problem (the JSON endpoint supports alimit=10
parameter).The text was updated successfully, but these errors were encountered: