Swiftpack.co - Swift Packages by patrick-zippenfenig

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. ## What's Changed * FIx DateTime with TimeZone by @planetMDX in https://github.com/patrick-zippenfenig/ClickHouseNIO/pull/9 **Full Changelog**: https://github.com/patrick-zippenfenig/ClickHouseNIO/compare/1.4.0...1.4.1 ## What's Changed * Support for more ClickHouse-Types by @planetMDX in https://github.com/patrick-zippenfenig/ClickHouseNIO/pull/8 ## New Contributors * @planetMDX made their first contribution in https://github.com/patrick-zippenfenig/ClickHouseNIO/pull/8 **Full Changelog**: https://github.com/patrick-zippenfenig/ClickHouseNIO/compare/1.3.0...1.4.0 This feature release adds support for Nullable datatype This release adds timeouts to make ClickHouseNIO more reliable in production environments. While running ClickHouseNIO we discovered various edge cases where a connection could get stuck. These events are infrequent (once every 2 weeks), but result in annoying deadlocks. Because networks unreliable by nature, ClickHouseNIO uses different timeouts to prevent potential deadlocks while waiting for a server response. All timeouts can be controlled via `ClickHouseConfiguration` and use default values as shown below: ```swift let config = try ClickHouseConfiguration( hostname: "localhost", ..., connectTimeout: .seconds(10), readTimeout: .seconds(90), queryTimeout: .seconds(600)) , ``` All timeouts will close the connection. Different timeouts trigger different exceptions: - `connectTimeout` will throw `NIO.ChannelError.connectTimeout(TimeAmount)` if the connection to the ClickHouse server cannot be establised after this period of time. - `readTimeout`: If a query is running, and the ClickHouseNIO client does not receive any network package, the conncection is closed and throws `ClickHouseError.readTimeout`. This can happen, if the network connection is interrupted while waiting for a response. Usually, even while waiting for a query result, packages are exchanged very frequently. - `queryTimeout` is the total time after a query will be terminated and the connection is closed. Because ClickHouseNIO is also capable of queueing queries, this includes the time in the queue as well. On a very busy server, a long waiting time starts to close connections. If a connection is closed, all queries in the queue will return a failed future with the exception `ClickHouseError.queryTimeout`. Timeouts can also be specified for a single query with `connection.command(sql: sql, timeout: .seconds(30))`, but keep in mind that this also includes queue time. Fixed a bug with the combination of insert & select statements like `INSERT INTO db.table SELECT * FROM db2.table2` which triggered an assertion on non production builds ixed: - Bug #2 ClickHouse uses little endian encoding for UUIDs TLS encrypted connections are now supported! For TLS encrypted connections to the ClickHouse server, a `tlsConfiguration` attribute can be set in the configuration. Usually port 9440 is used. `certificateVerification: .none` disables certificate verification for self signed certificates. TLS connections use BoringSSL with [SwiftNIO SSL](https://github.com/apple/swift-nio-ssl). ```swift let tls = TLSConfiguration.forClient(certificateVerification: .none) let config = try ClickHouseConfiguration( hostname: "localhost", port: 9440, user: "default", password: "admin", database: "default", tlsConfiguration: tls) ``` Fix a small compatibility issue with ClickHouse server 20.x. For DROP TABLE statements a progress message is now send which was unexpected for this library. See https://github.com/patrick-zippenfenig/ClickHouseNIO/commit/789deba0e5e06530ec86c6d2bb7c33f201b5e950 First version declared stable. Before it was in use at meteoblue for a while.

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. Bugfixes: - Fix crash in `inq_grpname`, because swift `String(cString:` requires a null terminator (#2 Thanks @fred-sch) Notes: - Swift 5.6 is now integrated in the CI testing process and works well `setAttribute` now accepts a type parameter to select the netcdf type. This can be used to write an array of Int8 as `char` instead of `byte` type. ```swift // Write attribute as [Char] instead of string with 0 terminator try file.setAttribute("TITLE_CHAR", Array("My data set".utf8CString), type: .char) ``` First release of SwiftNetCDF! This version is already used at www.meteoblue.com to read and write NetCDF files in production APIs. Most commonly used features in NetCDF should be available and working. Hopefully no interface changes are required. Support for user defined data types would be possible, but not on an agenda, because it is really used and more complicated to implement with Swifts fixed type system If you have any comments and suggestions, feel free to open an issue ticket

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. If multiple files at the same time are opened, it may result in `double free` internally in eccodes. An additional lock, prevents concurrent access to `grib_context` Add itterageMessages function to reduce memory consumption Bugfixes: * Improve error handling in case messages cannot be decoded * Fix potential memory leak in case a message is missing the 7777 trailing message Various bugfixes for multi message support Support to read multi part grib files from curl ranges. Only supported via `GribMemory` Basic version to read GRIB files