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

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

Build:
Build:
LAST BUILD BRANCH: realtime-update-v1-h-only-1
DEFAULT BRANCH: master
Ran 17 Jul 2015 04:10PM UTC
Files 74
Run time 5s
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

17 Jul 2015 04:07PM UTC coverage: 60.663% (+1.3%) from 59.387%
7033.1

push

travis-ci

seanh
Add NIPSA (Not In Public Site Areas) feature

This feature allows admin users to flag users as "nipsa'd", meaning that
these users' annotations will not appear in "public site areas".
Currently "public site areas" are defined as basically everywhere:
nipsa'd annotations are filtered out from the results returned by the
search API, so they won't appear in the stream or in the sidebar for
example.

- h/api/nipsa/ contains a new nipsa package with:
* nipsa table in db that records ids of nipsa'd users
* search functions for inserting nipsa-filtering commands into Es query
  dicts
* logic functions for using the nipsa feature, e.g. for nipsa'ing or
  unnipsa'ing a user. or asking whether a user is nipsa'd
* a worker function that adds the nipsa flag to or removes the nipsa
  flag from all of a user's past annotations

h/api/search.py: Now runs Es queries through the nipsa-filtering function

h/api/views.py: When creating a new annotation, if the user is nipsa'd
it now adds the nipsa flag to the annotation.

h/nipsa.py: A simple HTML page for admin users to nipsa and unnipsa
users.

Note on app/API separation: We don't want the app to read or write
database tables belonging to the API or vice-versa, nor do we want the
API to import modules defined in the app. The obvious place to put the
nipsa flag would be in a column on the user table (which belongs to the
app), but then when the user creates a new annotation the app would have
to communicate somehow to the API that the authorized user is nipsa'd
without the API reading from the user table or calling a function
defined in the app. Therefore the nipsa flag has been stored in a
separate nipsa table owned by the API instead.

1886 of 3109 relevant lines covered (60.66%)

0.61 hits per line

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