Permalink
Commits on Nov 14, 2018
  1. Merge branch 'merge-90272a39-8cac-4dde-9eb7-b203f4875906-JY6EOUUGM7MD…

    yrashk committed Nov 14, 2018
    …RDQ2DO4X6NDP5FHXYANR'
  2. Closed merge request 90272a39-8cac-4dde-9eb7-b203f4875906/JY6EOUUGM7M…

    yrashk committed Nov 14, 2018
    …DRDQ2DO4X6NDP5FHXYANR
  3. Problem: sit web always requests authorship information

    yrashk committed Nov 14, 2018
    Solution: ensure it only does that if none is found
  4. Closed merge request da70b9ff-7df6-4104-9faa-616dce80a743/RM25S5WGOLO…

    yrashk committed Nov 14, 2018
    …VA4KOGTZXIAFSNR4EYSLI
  5. Problem: authorship derivation can't write to a config file

    yrashk committed Nov 14, 2018
    This happens when the config directory doesn't exist.
    
    Solution: during sit's startup, ensure config dir exists
  6. Added merge request: 90272a39-8cac-4dde-9eb7-b203f4875906

    yrashk authored and sit-inbox committed Nov 14, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
  7. Added merge request: da70b9ff-7df6-4104-9faa-616dce80a743

    yrashk authored and sit-inbox committed Nov 14, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
  8. Merge branch 'merge-901c9e38-8c00-4c94-9c0c-e97497d65929-QP5XED5MVDYE…

    yrashk committed Nov 14, 2018
    …MHCVAWM5R66TX6LTJCCH'
  9. Closed merge request 901c9e38-8c00-4c94-9c0c-e97497d65929/QP5XED5MVDY…

    yrashk committed Nov 14, 2018
    …EMHCVAWM5R66TX6LTJCCH
  10. Problem: sit-web produces an obscure error

    yrashk committed Nov 14, 2018
    ```
    thread '<unnamed>' panicked at 'multipart request: WrongContentType', libcore/result.rs:1009:5
    ```
    
    Solution: fail to start sit-web if authorship is not configured
    
    The above failure happens when a user is starting sit web without
    pre-configured authorship (and one can't be derived from elsewhere, like
    git) and is trying to create a record.
    
    `sit record` doesn't have this problem because it checks whether there's
    any authorship to derive and fails if there's none. However, `sit web`
    didn't do this. This patch makes sit-web unable to start until such
    authorship can be derived.
    
    I want to note that (soon-ish) this functionality will be on its way out
    as I have a plan to extract it out of sit as it doesn't really belong
    there (along with timestamps, PGP, etc.). Until this is done, however,
    the tool should be usable and produce no confusing crashes.
  11. Added merge request: 901c9e38-8c00-4c94-9c0c-e97497d65929

    yrashk authored and sit-inbox committed Nov 14, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
Commits on Nov 5, 2018
  1. Merge branch 'merge-e5ccbe3b-37d3-4293-91dc-01917ddc5a45-DJC4L74XEMAV…

    yrashk committed Nov 5, 2018
    …UGTNS5WJ7LOMIG3GKC73'
  2. Closed merge request e5ccbe3b-37d3-4293-91dc-01917ddc5a45/DJC4L74XEMA…

    yrashk committed Nov 5, 2018
    …VUGTNS5WJ7LOMIG3GKC73
  3. Problem: upcoming 2018 edition of Rust

    yrashk committed Nov 5, 2018
    It's changing quite a bit of things and I don't want to be left alone
    with a codebase on an aging edition. SIT is too young for that.
    
    Solution: fix the code to make it compilable on both 2015 and 2018
    editions, but don't commit to 2018 just yet.
  4. Added merge request: e5ccbe3b-37d3-4293-91dc-01917ddc5a45

    yrashk authored and sit-inbox committed Nov 5, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
Commits on Nov 1, 2018
  1. Merge branch 'merge-f1994223-4a26-42ea-982b-7b3df5fa3faf-OACDYQ5USUEZ…

    yrashk committed Nov 1, 2018
    …6LTVJZZ6MKGV5OQYDK2A'
  2. Closed merge request f1994223-4a26-42ea-982b-7b3df5fa3faf/OACDYQ5USUE…

    yrashk committed Nov 1, 2018
    …Z6LTVJZZ6MKGV5OQYDK2A
  3. Problem: make osx fails

    yrashk committed Nov 1, 2018
    The problems are around cross-compiling libbacktrace and other
    libraries.
    
    Solution: make sure cross-compilation uses the right compiler
  4. Added merge request: f1994223-4a26-42ea-982b-7b3df5fa3faf

    yrashk authored and sit-inbox committed Nov 1, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
  5. Merge branch 'merge-795be03e-a365-46c9-9e4c-2777b94b3c18-NVGD2QZCTWGF…

    yrashk committed Nov 1, 2018
    …J2OAXLZWSY2ORNCQARWK'
  6. Closed merge request 795be03e-a365-46c9-9e4c-2777b94b3c18/NVGD2QZCTWG…

    yrashk committed Nov 1, 2018
    …FJ2OAXLZWSY2ORNCQARWK
  7. Problem: make linux fails

    yrashk committed Nov 1, 2018
    It fails because within the container, when cargo is trying to download
    crates, it gets permission denied. This is happening because we're
    passing UID/GID of the current user and cargo is trying to write
    globally.
    
    Solution: make this command build in a designated directory
    that we later allow anybody to overwrite
  8. Added merge request: 795be03e-a365-46c9-9e4c-2777b94b3c18

    yrashk authored and sit-inbox committed Nov 1, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
  9. Merge branch 'merge-4b16df8e-06a5-4556-a68a-c62905bd0035-2MEYJGRUROE5…

    yrashk committed Nov 1, 2018
    …HH4QM3M42TCN4MEHFJA6'
  10. Closed merge request 4b16df8e-06a5-4556-a68a-c62905bd0035/2MEYJGRUROE…

    yrashk committed Nov 1, 2018
    …5HH4QM3M42TCN4MEHFJA6
  11. Problem: Rust 1.29 is outdated

    yrashk committed Nov 1, 2018
    Solution: use 1.30 for builds
  12. Added merge request: 4b16df8e-06a5-4556-a68a-c62905bd0035

    yrashk authored and sit-inbox committed Nov 1, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
Commits on Oct 19, 2018
  1. Problem: it is unclear how the contributions are licensed

    yrashk committed Oct 19, 2018
    Solution: clarify in README's License section
  2. Merge branch 'merge-47381995-4ccd-4022-aee0-39a302eea3de-GGHOMQJQ25ZO…

    yrashk committed Oct 19, 2018
    …Y66NL77LFIZEGR7J5HZM'
  3. Closed merge request 47381995-4ccd-4022-aee0-39a302eea3de/GGHOMQJQ25Z…

    yrashk committed Oct 19, 2018
    …OY66NL77LFIZEGR7J5HZM
  4. Problem: at times it is not possible to retain +x on script

    yrashk committed Oct 16, 2018
    In some cases (for example, filesystems-in-transit that have no UNIX
    attributes, remote copying) it is not possible to retain +x on scripts
    in CLI.
    
    This also currently holds true to scripts recorded inside of SIT records
    (using `sit record`) as it `sit` doesn't currently copy these
    attributes.
    
    Until some measures are taken (for example, implementing something like
    https://wiki.sit.fyi/#SPAT%2F1) it is impossible to call any CLI scripts
    that don't have an executable attribute on UNIX systems.
    
    Solution: if an executable can't be found, try .sh extension
    
    It poses a small problem going forward, though. If we do integrate a Lua
    interpreter with sit (there's some work on this going on right now),
    then it would be tempting to do the same for .lua files. But what if
    both .sh and .lua present? What if we have more languages (JavaScript,
    etc.) available for CLIs -- how do we prioritize this?
Commits on Oct 16, 2018
  1. Added merge request: 47381995-4ccd-4022-aee0-39a302eea3de

    yrashk authored and sit-inbox committed Oct 16, 2018
    Signed-off-by: sit-inbox <sit@inbox.sit.fyi>
Commits on Oct 15, 2018
  1. Problem: AppVeyor builds failing

    yrashk committed Oct 15, 2018
    Solution: attempt to install `make`
    
    It appears that the builds are now failing because `make` can't be
    found:
    
    ```
    make test
    'make' is not recognized as an internal or external command,
    operable program or batch file.
    ```
Commits on Oct 11, 2018
  1. Problem: README's roadmap is outdated

    yrashk committed Oct 11, 2018
    Solution: change it
Commits on Oct 7, 2018
  1. Merge branch 'merge-ef9d0089-dcfa-4c6d-96be-7003afc40648-B27RP5SGT5EG…

    yrashk committed Oct 7, 2018
    …IPR5QRL3ZFOQJPANIRRU'