Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • backend backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • subugoesubugoe
  • ahiqarahiqar
  • backendbackend
  • Merge requests
  • !19

Bugfix/#23 api

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Michelle Weidling requested to merge bugfix/#23-api into develop Jun 10, 2020
  • Overview 0
  • Commits 8
  • Pipelines 3
  • Changes 4

Bug fix

Related Tickets

#23 (closed)

Summary

The problem stemmed from the way cURL works:

[(23) Failed writing body] happens when a piped program (e.g. grep) closes the read pipe before the previous program is finished writing the whole page.

(https://stackoverflow.com/questions/16703647/why-does-curl-return-error-23-failed-writing-body)

By adding the -N option (no buffering) this shouldn't happen again. But it did, for reasons unclear to me. Thus I separated the cURL result from further information extraction.

This MR also includes:

  • minor linting
  • enabling curl --head by adding HTTP HEAD to the RESTXQ annotations

Changelog

  • I added a statement to the CHANGELOG.

/cc Mathias Göbel, Frank Schneider, Michelle Weidling

Edited Jun 10, 2020 by Michelle Weidling
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: bugfix/#23-api