• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

valum-framework / valum
56%
master: 59%

Build:
Build:
LAST BUILD BRANCH: wip/build-on-windows
DEFAULT BRANCH: master
Repo Added 29 Mar 2015 03:31PM UTC
Files 47
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH 0.2/status-code-handler
branch: 0.2/status-code-handler
CHANGE BRANCH
x
Reset
  • 0.2/status-code-handler
  • 0.1/documentation-for-hacking
  • 0.1/improve-api-docs
  • 0.1/methods
  • 0.1/server-documentation
  • 0.2/converters
  • 0.2/end-in-a-continuation
  • 0.2/pollable-fastcgi-stream
  • 0.2/redesign-async-model
  • 0.2/redesigned-async-model
  • 0.2/update-documentation
  • 0.2/write-head-asynchronously
  • basepath-middleware
  • build-docs-with-waf
  • build-separate-libraries
  • cgi
  • codecov
  • coveralls-with-gcov
  • debug-flag-for-coverage
  • decode-middlewares
  • default-implementation-for-head
  • delegator-for-application
  • documentation-overhaul
  • explicit-leading-slash
  • filtering
  • fix-all-tests
  • fix-nullable-convert
  • flatten
  • generate-path-from-rule
  • genie-example
  • glib-application-integration
  • glib-parameter-for-request-params
  • improve-test-coverage
  • improve-vsgi-coverage
  • invert-routing
  • invoke-next-in-router
  • loader
  • master
  • master-with-c-sources
  • meson-build
  • middleware
  • multipart
  • negociation-middlewares
  • next
  • null-rule-catch-all
  • options-for-soup-server
  • replace-stack-with-context
  • return-in-application-callback
  • reuse-matcher-with-then
  • route-and-clause
  • route-flags
  • scgi
  • server-sent-events
  • stable
  • stacked-states
  • v0.1.0-alpha
  • v0.1.1-alpha
  • v0.1.3-alpha
  • v0.1.4-alpha
  • v0.2.0
  • v0.2.0-alpha
  • v0.2.1
  • v0.2.10
  • v0.2.11
  • v0.2.12
  • v0.2.13
  • v0.2.14
  • v0.2.15
  • v0.2.2
  • v0.2.3
  • v0.2.4
  • v0.2.5
  • v0.2.6
  • v0.2.7
  • v0.2.8
  • v0.2.9
  • valadoc
  • vsgi-convert
  • vsgi-response-expand
  • vsgi-rewrite-server-with-gmodule
  • wip/build-on-windows

pending completion
341

push

travis-ci

arteymix
Documents how to handle status code.

2520 of 4511 relevant lines covered (55.86%)

6.84 hits per line

Relevant lines Covered
Build:
Build:
4511 RELEVANT LINES 2520 COVERED LINES
6.84 HITS PER LINE
Source Files on 0.2/status-code-handler
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
341 0.2/status-code-handler Documents how to handle status code. push 30 May 2015 03:26AM UTC arteymix travis-ci pending completion  
340 0.2/status-code-handler Documents how to handle status code. push 30 May 2015 03:21AM UTC arteymix travis-ci pending completion  
332 0.2/status-code-handler Documents how to handle status code. push 30 May 2015 02:57AM UTC arteymix travis-ci pending completion  
315 0.2/status-code-handler Documents how to handle status code. push 29 May 2015 01:19AM UTC arteymix travis-ci pending completion  
308 0.2/status-code-handler Documents how to handle status code. push 28 May 2015 10:36PM UTC arteymix travis-ci pending completion  
306 0.2/status-code-handler Provide error code and message to the status handler. Keys 'code' and 'message' are setted in the request parameters so that the status handler can access that information. The request parameters are initialized if still null, which might happen... push 28 May 2015 04:56PM UTC arteymix travis-ci pending completion  
302 0.2/status-code-handler Status code handler. The status handler is invoked with perform_routing, so next can be used to jump to the next status handler for a given status. If nothing matches, the router handler is used. Status handler must set the status code in the re... push 28 May 2015 04:51PM UTC arteymix travis-ci pending completion  
287 0.2/status-code-handler Status code handler. The status handler is invoked with perform_routing, so next can be used to jump to the next status handler for a given status. If nothing matches, the router handler is used. It also captures generated NOT_FOUND and METHOD_N... push 28 May 2015 12:26PM UTC arteymix travis-ci pending completion  
285 0.2/status-code-handler Status code handler. The status handler is invoked with perform_routing, so next can be used to jump to the next status handler for a given status. If nothing matches, the router handler is used. push 28 May 2015 11:43AM UTC arteymix travis-ci pending completion  
See All Builds (764)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc