Skip to content

issues Search Results · repo:ncss/boomerang language:Python

Filter by

13 results
 (55 ms)

13 results

inncss/boomerang (press backspace or delete to remove)

When we switch to DO, it d be nice to use a managed database rather than SQLite -- but we must keep SQLite support for students.
  • cyphar
  • Opened 
    on Jan 11, 2021
  • #16

  • cyphar
  • Opened 
    on Jan 11, 2021
  • #15

I don t know why it does this, but for example attempting to fetch or post to the key abc/def in the Swagger API explorer will actually fetch or post to abc%2Fdef, the URL-encoded version of the path. ...
  • joelgibson
  • Opened 
    on Jan 11, 2020
  • #12

When using the try it out docs the request is made, but the supplied JSON is never sent with the request.
  • kennib
  • 2
  • Opened 
    on Dec 19, 2019
  • #10

The model claims that GET /key will return a Value JSON blob like: { key : group1/users/georgina , value : { food : marzipan , name : georgina } } But in fact, it will return blobs ...
  • cyphar
  • 2
  • Opened 
    on Dec 18, 2019
  • #9

If a key does not exist, DELETE /key will still return 204. While this isn t necessarily bad, we probably should return a 404 if the key is not known. The main issue is that there is no obvious way to ...
  • cyphar
  • 3
  • Opened 
    on Dec 10, 2019
  • #8

As discussed in tutor training, we need to add limits so people don t end up posting gigabytes of payload and causing issues for other students. Ideally we d have a user API with limits for each user, ...
  • cyphar
  • Opened 
    on Dec 10, 2019
  • #7

Not a major issue, but it is a bit strange for a JSON-only API to be returning non-JSON errors.
  • cyphar
  • Opened 
    on Dec 10, 2019
  • #6

As far as I can tell, it will always be true (db_store always returns True except when it panics) but more generally I don t understand why it s included -- if there s an error storing the key we really ...
  • cyphar
  • Opened 
    on Dec 10, 2019
  • #5

Arguably, POST /key is not an entirely correct use of POST -- since the insertion operation (after #1 gets fixed) is idempotent arguably it should be PUT. However, I m not sure whether this will confuse ...
  • cyphar
  • 1
  • Opened 
    on Dec 10, 2019
  • #4
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub