fatcat/rust, branch v0.3.2 [no description] https://git.bnewbold.net/fatcat/atom?h=v0.3.2 2020-01-22T21:41:11Z more TODO/proposal cleanup 2020-01-22T21:41:11Z Bryan Newbold bnewbold@robocracy.org 2020-01-22T21:41:11Z urn:sha1:2e3988fcf6441bef7ee4b030e499fd129e7cb189 fatcatd: fix corner-case in abstracts insertion 2020-01-15T23:33:24Z Bryan Newbold bnewbold@robocracy.org 2020-01-15T23:33:22Z urn:sha1:96df40583576d6a00dd585628bb9569996d038b5 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! bump required rust to 1.36 2019-12-03T18:43:54Z Bryan Newbold bnewbold@robocracy.org 2019-12-03T18:43:52Z urn:sha1:a330cbb94c90aa79bb5016d83540c99e671a91f3 This isn't a fatcat rust requirement, but instead a diesel requirement, via rust-smallvec, which in v1.0 uses the alloc crate: https://github.com/servo/rust-smallvec/issues/73 I think the reason this came up now is that diesel-cli is an application and doesn't have a Cargo.lock file, and the build was updated. Using some binary mechanism to install these dependencies would be more robust, but feels like a yak shave right now. add 'component' as a release_type 2019-11-04T19:59:05Z Bryan Newbold bnewbold@robocracy.org 2019-11-04T19:56:17Z urn:sha1:0ff42081a71d8f878feedca236fa8ffe282fec3a update rust README with fatcat_test db creation note 2019-10-03T20:35:37Z Bryan Newbold bnewbold@robocracy.org 2019-10-03T20:35:37Z urn:sha1:0e5ca287570de54657f11723b8749ea688a2c11f update rust README re: openssl 2019-10-01T19:37:54Z Bryan Newbold bnewbold@robocracy.org 2019-10-01T19:37:52Z urn:sha1:1cb871a0f7a276db09a1c2705cd7cc7bb9cff721 I believe an openssl library is still required locally, but with the SSL/TLS removal it now doesn't matter if it is OpenSSL 1.0 or 1.1. This is only a temporary work-around. When we update rust code generation, we will need to revisit these changes. The current version of swagger-rs still depends on HTTPS and OpenSSL 1.0 (via dependencies). entirely remove unused https flag to fatcatd 2019-09-29T20:50:49Z Bryan Newbold bnewbold@robocracy.org 2019-09-29T20:50:49Z urn:sha1:d17712902a17fad39f2f668d7f46bc5e42bb120d cargo update fatcat rust after openssl removal 2019-09-29T20:49:21Z Bryan Newbold bnewbold@robocracy.org 2019-09-29T20:49:21Z urn:sha1:626c7e677e23813ce02b6b85955441f360ac36c0 remove 'client' and hyper-openssl options from fatcat-openapi rust crate 2019-09-29T20:47:32Z Bryan Newbold bnewbold@robocracy.org 2019-09-29T20:47:32Z urn:sha1:d3fedefe129bd991c9cc75ae715b1b195d9bfe69 rust: use SPDX exact short license names 2019-09-19T04:20:52Z Bryan Newbold bnewbold@robocracy.org 2019-09-19T04:19:57Z urn:sha1:65f88b72165d9ea0e554eb2d403939f397e0f5bb