Skip to content

Release v0.2.3 (KeepGoing)

Compare
Choose a tag to compare
@odeke-em odeke-em released this 01 Jun 03:09
· 440 commits to master since this release

This release features mostly fixes and a couple of lessons learnt mostly from an education by the users of drive.

  • Fixed emptyTrash: This was reported in issue #204 by @sulicz. The code got broken by not expanding on the params passed into the list args struct for traversing children hence a wrong child count was always returned and emptyTrash would always get aborted. This was addressed by PR #205.
  • Push over 100%: This was reported in #207, self diagnosed and addressed by @4f0v3ny35. The end result was an education that improper access permissions probably caused multiple seeks and retries. Note: this issue seems to be a subset of open issue #177 so there might be something to learn from this. Also it has reminded me to make sure to check for readFrom access.
  • nil pointer deference on http.Get fail: This was reported in #217 by @sselph. @sselph resolved this by showing to me the proper handling of Get by following by spec and result from Go's http library. @sselph however couldn't make a PR asap because they needed permission from the employer to contribute to this project in code. The diagnosis was enough however, for me to spin up a PR with the same thoughts. This was addressed by #218.
  • mimeType fixes for diverse open document formats: This was reported in issue #215 by @GoGoris because lack of an explicit mimeType(derived by drive) was leaving mimeType resolution upto the Google Drive backend which processed such files as archives. This was addressed by PR #216.
  • handling reads from named pipes: named pipes can potentially hang the program up. For now they are temporarily skipped/err on encounter until a simple way of user acknowledgement for named pipe reading can be introduced. This was reported in issue #208 and addressed by PR #209.
  • Fixed result of --force on changes by ensuring that a noop gets converted to an addition and a conflict gets changed to a modification, no other operation gets modified. This was addressed by d76733e

Thank you everyone for the information, help, participation and for using drive!