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

hypothesis / h / 7067 / 1
63%
master: 97%

Build:
Build:
LAST BUILD BRANCH: realtime-update-v1-h-only-1
DEFAULT BRANCH: master
Ran 20 Jul 2015 12:02PM UTC
Files 74
Run time 6s
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

20 Jul 2015 11:57AM UTC coverage: 60.431% (-0.2%) from 60.663%
7067.1

push

travis-ci

seanh
Enable nipsa'ing users who don't exist

I don't think it's a good idea to restrict nipsa to users who we have a
row for in the users table. The model (nipsa'd user IDs in a separate
table with no relation to the user table) allows us to be more flexible
and nipsa any userid. Taking advantage of that avoids potential future
problems such as:

- Nipsa'ing users whose accounts have been deleted (if in the future we
  enable deleting accounts and it removes the row from the users table)
- Nipsa'ing users from third-party account providers (if in the future
  we enable external accounts and it's implemented in such a way that
  the users have no row in our users table)

So nipsa is just a simple list of userids. Each id may or may not exist
in our users table as well, it doesn't matter. And any annotations
created by these ids are hidden.

1877 of 3106 relevant lines covered (60.43%)

0.6 hits per line

Source Files on job 7067.1
  • Tree
  • List 0
  • Changed 10
  • Source Changed 10
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 7067
  • Travis Job 7067.1
  • 89f62556 on github
  • Prev Job for on nipsa (#7033.1)
  • Next Job for on nipsa (#7074.1)
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

© 2026 Coveralls, Inc