aboutsummaryrefslogtreecommitdiffstats
path: root/rust/src
Commit message (Collapse)AuthorAgeFilesLines
* rust: bump macaroon crate to v0.3.0 (upstream)Bryan Newbold2022-10-211-17/+9
|
* Merge branch 'bnewbold-fix-editing-4xx' into 'master'bnewbold2022-10-061-4/+5
|\ | | | | | | | | small fixes to editing process (python and rust) See merge request webgroup/fatcat!139
| * rust: don't set prev_rev on re-update if entity is createdBryan Newbold2022-03-091-4/+5
| | | | | | | | | | | | | | | | | | This applies when re-editing any entity within an editgroup, when the entity does not yet exist other than the current editgroup. The current behavior was resulting in "updated" status, with "prev_rev" pointing to a revision which never existing in the catalog (aka, had never been merged).
* | rust: clippy cleanupsBryan Newbold2022-10-0510-62/+60
| |
* | rust: add some more macaroons/auth test coverageBryan Newbold2022-10-051-6/+29
| |
* | rust: switch from patched macaroons to upstream v0.2.0Bryan Newbold2022-09-261-72/+111
| | | | | | | | | | Much fo the changes here are to deal with the 'ByteString' type that is included as part of the macaroons library itself.
* | Merge branch 'bnewbold-fill-changelog-gaps' into 'master'bnewbold2022-09-061-0/+97
|\ \ | | | | | | | | | | | | rust: fill changelog gap helper tool See merge request webgroup/fatcat!142
| * | rust: new fatcat-doctor fixup tool, with changelog gap fillerBryan Newbold2022-08-121-0/+97
| |/
* / RIP Peter EckersleyBryan Newbold2022-09-061-1/+1
|/ | | | "A man is not dead while his name is still spoken."
* rust: handle database read-only mode (as 5xx errors, not 4xx)Bryan Newbold2022-01-212-8/+16
|
* rust: implement content_scopeBryan Newbold2021-11-174-0/+19
|
* api: add SQL 'ORDER BY' to many reads to stabilize API array orderingBryan Newbold2021-11-051-3/+14
| | | | | | | | | | | | | | The hope is to make things like file entity URLs, fileset manifests, and other arrays in the JSON API "stable", meaning that if you create an entity with a list of a given order, a read back (in any environment, including prod/QA, bulk dumps, etc) will return the array with the same sort order. This was informally happening most of the time, but occasionally not (!) Assumption is that these sorts will have little or no performance impact, as the common case is less than a dozen elements, and the hard cases are a few thousand at most, and there is already a sorted index.
* rust: expand valid hdl identifiersBryan Newbold2021-10-131-3/+7
| | | | Based on real examples found on dblp.org
* rust: prep for possible DOI lowercase enforcementBryan Newbold2021-10-131-1/+5
| | | | | | See also: https://github.com/internetarchive/fatcat/issues/83 This commit is no behavior change, just leaving a note to self.
* rust: implement scheman and API changesBryan Newbold2021-10-135-38/+353
|
* rust: handle new migrations in test helperBryan Newbold2021-10-131-1/+1
|
* rust: implement recent SQL changesBryan Newbold2021-10-132-0/+12
|
* fatcatd: display version correctly, and at startupBryan Newbold2021-10-131-2/+8
|
* fatcat-api: enforce more release ext_id checks at create/updateBryan Newbold2021-10-131-2/+15
| | | | Not enforcing these was a serious bug!
* rust: fix malformed ext id error typeBryan Newbold2020-12-171-2/+2
| | | | This bug was due to copy/paste of SHA-1 check
* rust: rename and improve dblp key (id) syntax checkBryan Newbold2020-12-172-9/+17
|
* update fatcatd rust code for 'oai' external identifierBryan Newbold2020-11-194-11/+189
|
* rustfmtBryan Newbold2020-11-194-86/+134
|
* rust: fatcatd changes for DOAJ+dblp identifiersBryan Newbold2020-11-194-10/+126
|
* fatcat export: flush after batch, not per-lineBryan Newbold2020-08-051-1/+1
| | | | Good catch, thanks Martin
* group-by-work mode for fatcat-exportBryan Newbold2020-08-041-15/+157
|
* fatcatd: fix corner-case in abstracts insertionBryan Newbold2020-01-151-1/+4
| | | | | | | | | | | | | Both the release_abstract relation table and the abstracts table inserts were being gated by a check on new abstracts table rows. I *think* the chance of this having caused problems is low. The most likely would have been updates to exiting entities that somehow removed the abstracts content, but not the sha1 keys. This is not the default behavior of the API: either the entire abstract (content and hash) is returned, or the abstracts are hidden entirely (via `hide` flag). Still, best to be careful!
* add 'component' as a release_typeBryan Newbold2019-11-041-0/+1
|
* entirely remove unused https flag to fatcatdBryan Newbold2019-09-291-15/+6
|
* rust impl token endpoint (and bump crate version)Bryan Newbold2019-09-181-0/+51
|
* API docs default to redoc, not swagger-uiBryan Newbold2019-09-131-1/+10
|
* update missing rust crate namesBryan Newbold2019-09-053-4/+4
|
* rename rust crate fatcat-api-spec -> fatcat-openapiBryan Newbold2019-09-058-12/+12
|
* cargo fix ('dyn' keywords)Bryan Newbold2019-08-262-30/+30
|
* allow editing of WIP entitiesBryan Newbold2019-06-141-6/+1
|
* truncated oauth_oidc generated usernameBryan Newbold2019-06-071-2/+2
|
* truncated oidc username creationBryan Newbold2019-06-071-1/+2
|
* Revert "allow somewhat longer usernames"Bryan Newbold2019-06-071-3/+1
| | | | This reverts commit 123cc92cadb57e3a9e536e08a66ea54adab660ad.
* allow somewhat longer usernamesBryan Newbold2019-06-071-1/+3
|
* hide abstracts and refs in release expansionsBryan Newbold2019-05-201-3/+12
|
* rust impl release expansionBryan Newbold2019-05-201-3/+84
| | | | Not very DRY.
* rust fmtBryan Newbold2019-05-201-2/+0
|
* actually check withdrawn statusBryan Newbold2019-05-201-0/+3
|
* basic controlled vocabulary for withdrawn_stageBryan Newbold2019-05-201-2/+38
|
* include edit_extra on single-entity createsBryan Newbold2019-05-201-0/+1
|
* make some XXX into TODOBryan Newbold2019-05-201-1/+0
|
* allow versioned PMCIDBryan Newbold2019-05-201-2/+5
|
* rust/schema: allow 'retraction' release_typeBryan Newbold2019-05-161-0/+2
|
* codegen and rust impl created timestampBryan Newbold2019-05-143-10/+18
|
* rust: return editors and cl index for editgroup more oftenBryan Newbold2019-05-145-15/+20
|