Swiftpack.co - Swift Packages by m-barthelemy

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. # 3.0.0 beta1 This new major release will hopefully fix a long-standing issue with Mysql. ## Breaking changes - When upgrading from previous versions, the existing jobs DB storage table will not be used anymore. This new version **cannot process pending jobs stored by the previous releases** of this package. In fact, after successfully upgrading, you can delete the table created by the 1.x releases of QueuesFluentDriver. - The ability to list the existing jobs via the (non-standard) `list()` method has been removed. Not sure if anyone was really using this feature; can be added back upon request. - This version now assumes that the jobs will always have a unique ID. When you specify a custom `JobIdentifier`, it is now your responsibility to ensure that you don't create another job with the same ID as a job that still exists in the QueuesFluentDriver DB tables.
 Generally, we don't recommend using custom `JobIdentifier`s with this package (unless you are absolutely certain that your custom values will be unique). - Jobs that are completed are now **deleted** from the database tables, instead of using Fluent's _soft delete_ feature. You can opt in for the previous behavior by setting `app.queues.use(.fluent(useSoftDeletes: true))` Fixes https://github.com/m-barthelemy/vapor-queues-fluent-driver/issues/15 The previous rc.2 release has been reasonably well tested on macOS and Linux and no issue has been found so far. This 1.0.0 release doesn't contain any change compared to rc.2. It just removes the `rc` prefix to dissipate any doubts about the stability of the project. Previously, when the application was shutting down, the following kind of errors could appear: ``` ERROR: Cannot schedule tasks on an EventLoop that has already shut down. This will be upgraded to a forced crash in future SwiftNIO versions. ERROR: Cannot schedule tasks on an EventLoop that has already shut down. This will be upgraded to a forced crash in future SwiftNIO versions. ERROR: Cannot schedule tasks on an EventLoop that has already shut down. This will be upgraded to a forced crash in future SwiftNIO versions. ERROR: Cannot schedule tasks on an EventLoop that has already shut down. This will be upgraded to a forced crash in future SwiftNIO versions. Fatal error: leaking promise created at [...] ``` Fix from https://github.com/m-barthelemy/vapor-queues-fluent-driver/pull/11 This release removes the internal implementation of `.returning()` used with Postgres. Instead, we now rely on the implementation of RETURNING recently added to SQL-kit 3.5.0 Bumping release number to 1.0.0-rc now that this project has been used by quite a few people with no reports of issues. **UPGRADE NOTES**: If you want to upgrade to this release and use Postgres, make sure you use `postgres-kit` >= 2.1.0. Update Fluent to 4.0.0, cleanups (https://github.com/m-barthelemy/vapor-queues-fluent-driver/pull/12) • Upgrade Queues, Fluent and Sql-Kit • Use transaction for Sqlite (https://github.com/m-barthelemy/vapor-queues-fluent-driver/pull/10). This _might_ allow this driver to work with Sqlite in testing/specific scenarios (1 single Queues worker) - Improve startup errors handling and reporting. Now we fail (crash) early if something is off. - Add missing `Foundation` imports (https://github.com/m-barthelemy/vapor-queues-fluent-driver/pull/8) - Update README to swift-tools-version:5.2 - Cleanup: remove now useless `guard` statements, remove unused `dbType`(https://github.com/m-barthelemy/vapor-queues-fluent-driver/issues/7) • `FluentQueue` is now public, allowing to really use the `list()` custom method (https://github.com/m-barthelemy/vapor-queues-fluent-driver/issues/5) • Code cleanups

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Make some Docker info fields optional as the daemon can return null values for those. - Add container kill endpoint - Add optional timeout to container stop endpoint Make some Swarm Nodes structs public. - Use upstream WebSocketKit package - Rename `deamon` to `daemon`

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release contains a working implementation. It is sub-optimal, performance and memory-wise, and doesn't have any unit tests yet.