net/torsocks: build failure #217
Comments
jperkin
pushed a commit
that referenced
this issue
Jan 3, 2020
Version 3.1.1.1 * Fix for GHCJS. #431 Version 3.1.1.0 * A new API: gracefulClose. #417 * touchSocket, unsafeFdSocket: Allow direct access to a socket's file descriptor while providing tools to prevent it from being garbage collected. This also deprecated fdSocket in favor of unsafeFdSocket and withFdSocket. #423 * socketToFd: Duplicates a socket as a file desriptor and closes the source socket. #424 Version 3.1.0.1 * getAddrInfo: raise exception if no AddrInfo returned. #410 * Avoid catching SomeException. #411 Version 3.1.0.0 * Making GC of socket safer. #399 * Deprecating fdSocket. Use withFdSocket instead to ensure that sockets are GCed in proper time. #399 Version 3.0.1.1 * Fix blocking if_nametoindex errors on Windows #391 Version 3.0.1.0 * Added getSocketType :: Socket -> IO SocketType. #372 * Correcting manual and brushing up test cases #375 * Fixed longstanded bug in getContents on mac #375 * Fixing regression: set correct sockaddr length for abstract addresses for Linux. #374 Version 3.0.0.1 * Fixed a bug in connect where exceptions were not thrown #368 Version 3.0.0.0 * Breaking change: the Network and Network.BSD are removed. Network.BSD is provided a new package: network-bsd. * Breaking change: the signatures are changed: old fdSocket :: Socket -> CInt new fdSocket :: Socket -> IO CInt old mkSocket :: CInt -> Family -> SocketType -> ProtocolNumber -> SocketStatus -> IO Socket new mkSocket :: CInt -> IO Socket * Breaking change: the deprecated APIs are removed: send, sendTo, recv, recvFrom, recvLen, htonl, ntohl, inet_addr, int_ntoa, bindSocket, sClose, SocketStatus, isConnected, isBound, isListening, isReadable, isWritable, sIsConnected, sIsBound, sIsListening, sIsReadable, sIsWritable, aNY_PORT, iNADDR_ANY, iN6ADDR_ANY, sOMAXCONN, sOL_SOCKET, sCM_RIGHTS, packSocketType, getPeerCred. * Breaking change: SockAddrCan is removed from SockAddr. * Socket addresses are extendable with Network.Socket.Address. * "socket" is now asynchronous-exception-safe. #336 * "recvFrom" returns (0, addr) instead of throwing an error on EOF. #360 * All APIs are available on any platforms. * Build system is simplified. * Bug fixes. Version 2.8.0.1 * Eensuring that accept returns a correct sockaddr for unix domain. #400 * Avoid out of bounds writes in pokeSockAddr. #400 Version 2.8.0.0 * Breaking change: PortNumber originally contained Word16 in network byte order and used "deriving Ord". This results in strange behavior on the Ord instance. Now PortNumber holds Word16 in host byte order. #347 * Breaking change: stopping the export of the PortNum constructor in PortNumber. * Use bytestring == 0.10.* only. * Use base >= 4.7 && < 5. Version 2.7.0.2 * Removing withMVar to avoid the deadlock between "accept" and "close" #330 * "close" does not throw exceptions. A new API: "close'" throws exceptions when necessary. #337 * Fixing the hang of lazy sendAll. #340 * Installing NetDef.h (#334) #334 Version 2.7.0.1 * A new API: socketPortSafe. #319 * Fixing a drain bug of sendAll. #320 * Porting the new CALLCONV convention from master. #313 * Withdrawing the deprecations of packFamily and unpackFamily. #324 Version 2.7.0.0 * Obsoleting the Network module. * Obsoleting the Network.BSD module. * Obsoleting APIs: MkSocket, htonl, ntohl, getPeerCred, getPeerEid, send, sendTo, recv, recvFrom, recvLen, inet_addr, inet_ntoa, isConnected, isBound, isListening, isReadable, isWritable, aNY_PORT, iNADDR_ANY, iN6ADDR_ANY, sOMAXCONN, sOL_SOCKET, sCM_RIGHTS, packFamily, unpackFamily, packSocketType * Breaking change: do not closeFd within sendFd. #271 * Exporting ifNameToIndex and ifIndexToName from Network.Socket. * New APIs: setCloseOnExecIfNeeded, getCloseOnExec and getNonBlock * New APIs: isUnixDomainSocketAvailable and getPeerCredential * socketPair, sendFd and recvFd are exported even on Windows. Version 2.6.3.5 * Reverting "Do not closeFd within sendFd" #271 Version 2.6.3.4 * Don't touch IPv6Only when running on OpenBSD #227 * Do not closeFd within sendFd #271 * Updating examples and docs. Version 2.6.3.3 * Adds a function to show the defaultHints without reading their undefined fields #291 * Improve exception error messages for getAddrInfo and getNameInfo #289 Version 2.6.3.2 * Zero memory of sockaddr_un if abstract socket #220 * Improving error messages #232 * Allow non-blocking file descriptors via setNonBlockIfNeeded #242 * Update config.{guess,sub} to latest version #244 * Rename my_inet_ntoa to avoid symbol conflicts #228 * Test infrastructure improvements #219 #217 #218 * House keeping and cleanup #238 #237 Version 2.6.3.1 * Reverse breaking exception change in Network.Socket.ByteString.recv #215 Version 2.6.3.0 * New maintainers: Evan Borden (@eborden) and Kazu Yamamoto (@kazu-yamamoto). The maintainer for a long period, Johan Tibell (@tibbe) stepped down. Thank you, Johan, for your hard work for a long time. * New APIs: ntohl, htonl,hostAddressToTuple{,6} and tupleToHostAddress{,6}. #210 * Added a Read instance for PortNumber. #145 * We only set the IPV6_V6ONLY flag to 0 for stream and datagram socket types, as opposed to all of them. This makes it possible to use ICMPv6. #180 #181 * Work around GHC bug #12020. Socket errors no longer cause segfaults or hangs on Windows. #192 * Various documentation improvements and the deprecated pragmas. #186 #201 #205 #206 #211 * Various internal improvements. #193 #200 Version 2.6.2.1 * Regenerate configure and HsNetworkConfig.h.in. * Better detection of CAN sockets. Version 2.6.2.0 * Add support for TCP_USER_TIMEOUT. * Don't conditionally export the SockAddr constructors. * Add isSupportSockAddr to allow checking for supported address types at runtime.
jperkin
pushed a commit
that referenced
this issue
Apr 19, 2020
Changelog picked from https://github.com/tdewolff/minify/releases v2.7.3 external minifiers can now use input/output files instead of only stdin/stdout using the $in and $out keywords SVG: don't minify inside foreignObject, fixes #291 v2.7.2 SVG: bugfix for C, S, Q, and T commands where if the control points would not overlap with the start or end points of the curve, it would still be converted to a line. v2.7.1 DataURI: if the original data URI is shorter than the URL-encoded/base64-encoded URI, use the original instead, fixes #282 Bugfix: decimal (i.e. without exponentials) incorrectly minified 139.9 to 230 instead of 140 v2.7.0 Use custom URL encode/decode functions to fix #180 and #243 Decimal and Number now take precision to mean the number of significant digits, and not the number of digits behind the dot (decimals); includes a few subtle bugfixes. Decimals option renamed to Precision Move Hash definitions and EntitiesMap from tdewolff/parse to this repository to prevent releasing new versions of tdewolff/parse everytime cmd: add --sync functionality cmd: make --watch work for newly created directories cmd: various fixes and improved messages CSS: keep quotes around IE font families, fixes #251 CSS: major refactor to allow nested functions to be minified CSS: improved HSL/RGB minification CSS: minify more properties: color, background-color, border-color, border-*-color, caret-color, outline-color, fill, stroke, column-rule, text-shadow, text-decoration, text-emphasis, flex, flex-*, order, fixes #217 CSS: minify background better if it has multiple layers CSS: improve box-shadow minification CSS: accept CSS functions where numbers/lengths are required, such as calc, min, max, clamp, attr, var SVG: print new path command after bad command, fixes #275 SVG: print A command correctly with boolean largeArc and sweep SVG: avoid precision errors for alternative (absolute or relative commands) path v2.6.3 Add install.sh and Makefile to ./cmd/minify. No changes to binaries (use v2.6.2). v2.6.2 HTML: ignore CSS minification for amp-boilerplate HTML: add KeepQuotes option for attributes XML: bugfix for recent changes to XML parser v2.6.1 Upgrade to tdewolff/parse@2.3.14: Re-parse input immediately when encountering parse error. Previously this was only done if the error was actually read which would save us from re-parsing the file (i.e. better performance). However, an error is (a) rare and (b) happens only once per file. Re-parsing on errors does not impact the performance of well formatted files, and a reliable error message is valued more. Bugfix: prevent infinite loop on error on input file that contains unicode code points (i.e. any character bigger than 0xC0 usually followed by more bytes). Improve error messages for parsers to include parser name and print offending byte(s) v2.6.0 CSS: remove space after function in property value; margin:calc(10px) calc(20px) => margin:calc(10px)calc(20px) SVG: parse A path command correctly when the booleans largeArc and sweep are not separated by a space, such as in A10 10 0 0120 0 which is equivalent to A10 10 0 0 1 20 0 SVG bugfix: make sure we are processing a valid path command SVG bugfix: prevent panic when having insufficient path arguments cmd: surpress error when minifying empty directory HTML: only minify attributes for known HTML5 tags, fixes #270 HTML, XML, SVG: minify entities with parse@2.3.13 such as: " => ", " => ", " => ", ’ => ’, ✏ => ✏. v2.5.2 Bugfixes: SVG: don't convert polyline/rect/polygon/line to path, which can break CSS, fixes #260 SVG: relative SVG Bézier commands not properly minified CSS: don't remove whitespace in nested unknown at-rules, fixes #262 CSS: fix panic for background when it contains functions other than calc for background-position, fixes #263 CSS: fix panic for background-position with three numbers CSS: fix panic for url() with only whitespace or only one quote v2.5.1 Remove import comments SVG: do not convert line/rect to path if coordinates are relative percentages CSS: fix bug with inline CSS encountering } v2.5.0 CSS: fix position information in error context CSS: fix background-position panic with offsets that are zero HTML: trim and collapse whitespace in certain attribute values SVG: shorten cubic and quadratic Beziér path data to their shorter format or to line segments v2.4.0 When minifying floating points, remove trailing zeros and not other numbers Make M concurrent-safe HTML: keep double quotes around XML-flavour RDFa attributes CSS: revert the use of the #RRGGBBAA format as proposed in Color Module Level 4 as it is not yet an official W3C recommendation CSS: background-position (also within background) now works with 3 and 4 values as well SVG: skipping metadata or rect tags properly even if they are closed by a void tag (like <rect/>) SVG pathdata: when cursor doesn't move, don't emit any commands
jperkin
added a commit
that referenced
this issue
Aug 26, 2020
Version 2.11 - 9 Jul 2020
- Introduction of the barman-cli-cloud package that contains all cloud
related utilities.
- Add barman-cloud-wal-restore to restore a WAL file previously
archived with barman-cloud-wal-archive from an object store
- Add barman-cloud-restore to restore a backup previously taken with
barman-cloud-backup from an object store
- Add barman-cloud-backup-list to list backups taken with
barman-cloud-backup in an object store
- Add support for arbitrary archive size for barman-cloud-backup
- Add support for --endpoint-url option to cloud utilities
- Remove strict superuser requirement for PG 10+ (by Kaarel Moppel)
- Add --log-level runtime option for barman to override default log
level for a specific command
- Support for PostgreSQL 13
- Bug fixes:
- Suppress messages and warning with SSH connections in barman-cli
(GH-257)
- Fix a race condition when retrieving uploaded parts in
barman-cloud-backup (GH-259)
- Close the PostgreSQL connection after a backup (GH-258)
- Check for uninitialized replication slots in receive-wal --reset
(GH-260)
- Ensure that begin_wal is valorised before acting on it (GH-262)
- Fix bug in XLOG/WAL arithmetic with custom segment size (GH-287)
- Fix rsync compatibility error with recent rsync
- Fix PostgreSQLClient version parsing
- Fix PostgreSQL exception handling with non ASCII messages
- Ensure each postgres connection has an empty search_path
- Avoid connecting to PostgreSQL while reading a backup.info file
If you are using already barman-cloud-wal-archive or barman-cloud-backup
installed via RPM/Apt package and you are upgrading your system, you
must install the barman-cli-cloud package. All cloud related tools are
now part of the barman-cli-cloud package, including
barman-cloud-wal-archive and barman-cloud-backup that were previosly
shipped with barman-cli. The reason is complex dependency management of
the boto3 library, which is a requirement for the cloud utilities.
Version 2.10 - 5 Dec 2019
- Pull .partial WAL files with get-wal and barman-wal-restore,
allowing restore_command in a recovery scenario to fetch a partial
WAL file's content from the Barman server. This feature simplifies
and enhances RPO=0 recovery operations.
- Store the PostgreSQL system identifier in the server directory and
inside the backup information file. Improve check command to verify
the consistency of the system identifier with active connections
(standard and replication) and data on disk.
- A new script called barman-cloud-wal-archive has been added to the
barman-cli package to directly ship WAL files from PostgreSQL (using
archive_command) to cloud object storage services that are
compatible with AWS S3. It supports encryption and compression.
- A new script called barman-cloud-backup has been added to the
barman-cli package to directly ship base backups from a local
PostgreSQL server to cloud object storage services that are
compatible with AWS S3. It supports encryption, parallel upload,
compression.
- Automated creation of replication slots through the server/global
option create_slot. When set to auto, Barman creates the replication
slot, in case streaming_archiver is enabled and slot_name is
defined. The default value is manual for back-compatibility.
- Add '-w/--wait' option to backup command, making Barman wait for all
required WAL files to be archived before considering the backup
completed. Add also the --wait-timeout option (default 0, no
timeout).
- Redact passwords from Barman output, in particular from
barman diagnose (InfoSec)
- Improve robustness of receive-wal --reset command, by verifying that
the last partial file is aligned with the current location or, if
present, with replication slot's.
- Documentation improvements
- Bug fixes:
- Wrong string matching operation when excluding tablespaces
inside PGDATA (GH-245)
- Minor fixes in WAL delete hook scripts (GH-240)
- Fix PostgreSQL connection aliveness check (GH-239)
Version 2.9 - 1 Aug 2019
- Transparently support PostgreSQL 12, by supporting the new way of
managing recovery and standby settings through GUC options and
signal files (recovery.signal and standby.signal)
- Add --bwlimit command line option to set bandwidth limitation for
backup and recover commands
- Ignore WAL archive failure for check command in case the latest
backup is WAITING_FOR_WALS
- Add --target-lsn option to set recovery target Log Sequence Number
for recover command with PostgreSQL 10 or higher
- Add --spool-dir option to barman-wal-restore so that users can
change the spool directory location from the default, avoiding
conflicts in case of multiple PostgreSQL instances on the same
server (thanks to Drazen Kacar).
- Rename barman_xlog directory to barman_wal
- JSON output writer to export command output as JSON objects and
facilitate integration with external tools and systems (thanks to
Marcin Onufry Hlybin). Experimental in this release.
Bug fixes:
- replication-status doesn’t show streamers with no slot (GH-222)
- When checking that a connection is alive (“SELECT 1” query),
preserve the status of the PostgreSQL connection (GH-149). This
fixes those cases of connections that were terminated due to
idle-in-transaction timeout, causing concurrent backups to fail.
Version 2.8 - 17 May 2019
- Add support for reuse_backup in geo-redundancy for incremental
backup copy in passive nodes
- Improve performance of rsync based copy by using strptime instead of
the more generic dateutil.parser (#210)
- Add ‘--test’ option to barman-wal-archive and barman-wal-restore to
verify the connection with the Barman server
- Complain if backup_options is not explicitly set, as the future
default value will change from exclusive_backup to concurrent_backup
when PostgreSQL 9.5 will be declared EOL by the PGDG
- Display additional settings in the show-server and diagnose
commands: archive_timeout, data_checksums, hot_standby,
max_wal_senders, max_replication_slots and wal_compression.
- Merge the barman-cli project in Barman
- Bug fixes:
- Fix encoding error in get-wal on Python 3 (Jeff Janes, #221)
- Fix exclude_and_protect_filter (Jeff Janes, #217)
- Remove spurious message when resetting WAL (Jeff Janes, #215)
- Fix sync-wals error if primary has WALs older than the first
backup
- Support for double quotes in synchronous_standby_names setting
- Minor changes:
- Improve messaging of check --nagios for inactive servers
- Log remote SSH command with recover command
- Hide logical decoding connections in replication-status command
This release officially supports Python 3 and deprecates Python 2 (which
might be discontinued in future releases).
PostgreSQL 9.3 and older is deprecated from this release of Barman.
Support for backup from standby is now limited to PostgreSQL 9.4 or
higher and to WAL shipping from the standby (please refer to the
documentation for details).
Version 2.7 - 21 Mar 2019
- Fix error handling during the parallel backup. Previously an
unrecoverable error during the copy could have corrupted the barman
internal state, requiring a manual kill of barman process with
SIGTERM and a manual cleanup of the running backup in PostgreSQL.
(GH#199)
- Fix support of UTF-8 characters in input and output (GH#194 and
GH#196)
- Ignore history/backup/partial files for first sync of geo-redundancy
(GH#198)
- Fix network failure with geo-redundancy causing cron to break
(GH#202)
- Fix backup validation in PostgreSQL older than 9.2
- Various documentation fixes
Version 2.6 - 4 Feb 2019
- Add support for Geographical redundancy, introducing 3 new commands:
sync-info, sync-backup and sync-wals. Geo-redundancy allows a Barman
server to use another Barman server as data source instead of a
PostgreSQL server.
- Add put-wal command that allows Barman to safely receive WAL files
via PostgreSQL's archive_command using the barman-wal-archive script
included in barman-cli
- Add ANSI colour support to check command
- Minor fixes:
- Fix switch-wal on standby with an empty WAL directory
- Honour archiver locking in wait_for_wal method
- Fix WAL compression detection algorithm
- Fix current_action in concurrent stop backup errors
- Do not treat lock file busy as an error when validating a backup
jperkin
pushed a commit
that referenced
this issue
Sep 9, 2020
pkgsrc changes: - Fix a typo in DISTNAME/PKGNAME: it is now go-ffuf (instead of go-fuff) - Only installs bin/ffuf and its README - Reset MAINTAINERship, requested by <nikita> Changes: 1.1.0 ----- - Add unsupported arch/os to goreleaser ignore list (#267) - Release 1.1 (#266) - Fix crash with 3xx requests without location header (#265) - Update random seed logic (#262) - fix file get thing (#226) - Update CONTRIBUTORS.md to add bsysop (#258) - Fixed behavior of wordlist:keyword separator in Windows (#240) - Add Host information to JSON output file (#223) - Support outputting all file formats concurrently (#218) - Increase default rows per page on html report (#217) - Add the wordlists to the header information (#211) - Fix error with missing usage info (#195) - Feature178 (#186) - Fix for #193 (#194) - Fix for issue #179 (#180) - Prepare for 1.1.0-git (#176)
jperkin
pushed a commit
that referenced
this issue
Sep 16, 2020
Update ruby-logging package to 2.3.0. == 2.3.0 / 2020-07-04 Enhancements - all appender output is now synchronized [PR #219] - renamed the `LogEvent#method` to no longer conflict with `Kernel#method` [PR #218] - @bhuga (not the Fortnite star) added a `raise_errors` method for debugging [PR #203] - thanks to @olleolleolle for keeping on top of Travis and Ruby versions Bug Fixes - conosle appenders can be reopened [PR #220] - fixed a race condition in the rolling file appender [PR #216] - fixed a race condition when opening log file destinations [PR #208 #217] - @MikaelSmith fixed a race condition in Logger creation [PR #201] - documentation bug fixes [PR #184 #185 #188 #194 #209]
jperkin
pushed a commit
that referenced
this issue
Sep 16, 2020
Update ruby-mixlib-shellout package to 3.1.6. 3.1.6 (2020-09-10) * Use dir instead of FILE #220 (tas50) * Simplify things a bit with &. #221 (tas50) 3.1.4 (2020-08-13) * Fix a few typos #217 (tas50) * Optimize requires for non-omnibus installs #218 (tas50) 3.1.2 (2020-07-24) * convert helper to default_paths API #216 (lamont-granquist) 3.1.1 (2020-07-18) 3.1.0 (2020-07-17) * shellout_spec: make "current user" independent of the environment #203 (terceiro) * Minor doc fixes #205 (phiggins) * extracting shell_out helper to mixlib-shellout #206 (lamont-granquist) * Bumping minor version #207 (lamont-granquist) * Test on Ruby 2.7 final, update chefstyle, and other CI fixes #208 (tas50) * Bump minor for release #210 (lamont-granquist) * Bumping minor for release again, again. #211 (lamont-granquist)
jperkin
pushed a commit
that referenced
this issue
Sep 18, 2020
0.60: Asciidoc: * Introduce "compat" option to parse like asciidoc or asciidoctor. Text (and Markdown): * Fix the support of nested lists (GitHub's #131). Other: * Remove the experimental C extension that was never built, distributed, tested nor modified since 2007. XML: * Provide a meaningful message when the translators butcher the <placeholder> attributes instead of truncating the file. (GitHub's #254) 0.59.1: po4a tool: * Really fix --srcdir and --destdir handling (Debian's #960892 again). Even with the previous fix, the aptitude package was still broken. Documentation: * Clarify the syntax of -o parameters (GitHub's #233). Sgml: * Sort the attributes. Without this, msgids are randomly fuzzied. (Debian's #725931 and Debian's #810988) 0.59: po4a tool: * Fix --srcdir handling (GitHub's #237 and Debian's #960892). This bug was breaking the build of several packages, including dpkg. Addendum: * New mode 'eof' to easily add at the end of the file (Debian's #960949). Documentation: * Fix many typos and glitches * Start a section about external projects using po4a Tests: * po4a: Add a test for the [po_directory] feature Overall: * Improve the displayed messages, don't translate debug messages. 0.58.1: Documentation: * Document an option of the XML parser (GitHub's #223). * Small glitches found during the translations. Tests: * Also ignore 'Project-Id-Version' when diffing PO files (GitHub's #224) * asciidoc: reactivate tablecells tests AsciiDoc: * Fix management of images in tables (Github's #226) * Tolerate underline length variations in two lines titles (Github's #212) 0.58: AsciiDoc: * Accept numbered list items beginning with any number of dots (GitHub's #210) Markdown: * Avoid translating Markdown fenced code block info string (GitHub's #194) * List Markdown fenced code block info string as text type (GitHub's #195) * Support YAML Front Matter (GitHub's #196). This requires YAML::Tiny. * Introduce options yfm_keys and yfm_skip_array to respectively specify which YAML keys should be translated, and that the array content should not be translated. * Work around a bug in YAML::Tiny that quotes numbers (GitHub's #217) * Add gettext flag "markdown-text" for relevant entries (GitHub's #208) Text: * Honor the (existing) --neverwrap option to handle every content verbatim. Texinfo: * Add the comments starting with 'TRANSLATORS:' to the po file (GitHub's #162) XHTML: * Don't fail nor warn when a closing tag is missing, that's legit in HTML. (GitHub's #179) XML and DocBook: * Allow attributes with no value (GitHub's #178). * Processing Instructions are handled as inline tags by default, but you can change them back to breaking with '-o break-pi' (GitHub's #170) Yaml: * Introduce option to skip array values. (GitHub's #187) po4a tool: * Cleanups and fixups about options' parsing (now tested and documented) _ / \ You may need to upgrage your po4a.conf if you were using /_!_\ "unwanted features" (ie, bugs) of the previous implementation. * Do not touch source dir when --destdir is provided (Debian #602387) * Pass --add-location=file to msgmerge when receiving option porefs. (requires gettext >= 0.19 -- June 2014) * Option --master-charset sets the charset of the generated POT file. * Option --master-language sets the language of the generated POT file. * Add support for addendum path in po4a_paths (Debian #823189) * Stop pretending that --porefs can control the wrapping of reference comments, as the gettext tools used internally always rewrap them. Scripts: * Rename po4aman-display-po to po4a-display-man * Rename po4apod-display-po to po4a-display-pod Core: * Use UTF-8 by default (the 20th century is over -- Debian #862460) po4a used to prefer ascii unless it proved impossible. But the underlying detection would fail, possibly for document containing UTF-8 chars composed on printable ascii chars only. * Add a --wrap-po option to control how the po file is wrapped, and chose between either nicely wrapped files that tend to produce git conflicts, or ugly files that are easy to automatically deal with. Tests: * Completely refactor most tests. They are now more reliable and the error messages are much more useful to understand the issues. * Many bugs to po4a and the core were ironed out in the process. * PO files content are now tested too (GitHub's #67) Documentation: * Various cleanups by Golubev Alexander (GitHub's #190 & #191)
jperkin
pushed a commit
that referenced
this issue
Jan 13, 2021
Pkgsrc changes: * Remove patch integrated upstream. * Update checksums. Upstream changes: [3.18.0] - 2021-01-08 ===================== - allow UIDs and GIDs to be specified numerically (#217) - add support for Zstandard compressed files (#355) - make `delaycompress` not to fail with `rotate 0` (#341)
jperkin
pushed a commit
that referenced
this issue
Feb 23, 2021
Changelog: What's New in libchewing 0.5.1 (May 18, 2016) --------------------------------------------------------- * Bug fixed: - Fix wrong CHEWING_DATADIR definition in CMake build #222. - Fix j, k selection when symbol in between #149 #221. What's New in libchewing 0.5.0 (May 2, 2016) --------------------------------------------------------- * New feature - Add Carpalx keyboard layout support #217. * Dictionary - Update dictionary #151 #155 #188 #191 #201. - Add debug tool: dump_database. - Sort tsi.src #212. * Misc - Tweak several comments. - Fix libchewing document. - Remove old/dead code. - Improve code readability and consistency. - Update automake syntax #114. - Add test cases #169 #177. - Update Python sample code. - Add debug tool dump_database. - Integrate coverity scan in https://scan.coverity.com/. * Platform-specific - Update README for OS X. - Set WITH_INTERNAL_SQLITE3 to true by default in MS-Windows. - Fix Visual Studio compiling warnings/errors #168 #171 #189 #190 #213. - Add a cmake option BUILD_DLL to enable building *.dll with MS VC++ #185. - Make the python binding of libchewing support Windows dll files #186. - Don't use SIGSTOP in MS-Windows. * Bug fixed - Check if ld supports --no-defined #144. - Fix unexpected candidate disorder for '1' #153 - Replace bash-izm '==' operator with '=' for test(1) # 158. - Fix several Coverity errors #172 #173. - Fix ChewingKillChar which is disabling OpenSymbolChoice #160 #181. - ㄅ cannot overwrite ㄆ in HSU and ET26 #170 #183. * Successful stories: - Rime Input Method Engine (RIME) takes partial dictionary from libchewing. - PIME (writing input methods for Windows easily with Python) supports Chewing IM by default.
jperkin
pushed a commit
that referenced
this issue
Apr 8, 2021
Bug-fix and maintenance update after the previous version 0.4.3.
All users of wildmidi-0.4.x are strongly encouraged to upgrade.
What's new in 0.4.4:
Fixed integer overflow in midi parser sample count calculation (bug #200).
Fixed 8 bit ping pong GUS patch loaders (bug #207).
Fixed wrong variable use in reverb code (bug #210).
Reset block status of tty after playback (bug #211).
Fixed broken file name handling for 'save as midi' command during playback.
Clamp MUS volume commands (PR #226).
CMake project improvements (bugs: #214, #216, #217, #218) - cmake version 3.1 or newer is now required.
jperkin
pushed a commit
that referenced
this issue
Aug 23, 2021
# tidyselect 1.1.1 * Fix for CRAN checks. * tidyselect has been re-licensed as MIT (#217).
jperkin
pushed a commit
that referenced
this issue
Nov 15, 2021
v5.0.5 -NetBSD: Don't check the output of `session()`, addressing #217. -Wayland: Sway and Qtile users don't need `wmctrl` to see their window manager information. -Unix: Fixed failing "Host" and "Shell" readouts. v5.0.4 -Fixed a compilation error upon cargo installation. -Windows' dependencies have been bumped. (libmacchina#93) -Windows' Local IP readout is a lot more user-friendly now. (libmacchina#94)
jperkin
pushed a commit
that referenced
this issue
Nov 28, 2021
0.5.8 (2021-11-10) Added * Added more documentation files to packaged gem, e.g. SECURITY.md, CODE_OF_CONDUCT.md Fixed * Removed reference to RUBY_VERSION from gemspec, as it depends on rake release, which is problematic on some ruby engines. (by @pboling) 0.5.7 (2021-11-02) Added * Setup Rubocop (#205, #208 by @pboling) * Added CODE_OF_CONDUCT.md (#217, #218 by @pboling) * Added FUNDING.yml (#217, #218 by @pboling) * Added Client Certificate Options: :ssl_client_cert and :ssl_client_key (#136, #220 by @pboling) * Handle a nested array of hashes in OAuth::Helper.normalize (#80, #221 by @pboling) Changed * Switch from TravisCI to Github Actions (#202, #207, #176 by @pboling) * Upgrade webmock to v3.14.0 (#196 by @pboling) * Upgrade em-http-request to v1.1.7 (#173 by @pboling) * Upgrade mocha to v1.13.0 (#193 by @pboling) * HISTORY renamed to CHANGELOG.md, and follows Keep a Changelog (#214, #215 by @pboling) * CHANGELOG, LICENSE, and README now ship with packaged gem (#214, #215 by @pboling) * README.rdoc renamed to README.md (#217, #218 by @pboling) * Require plaintext signature method by default (#135 by @confiks & @pboling) Fixed * Fixed Infinite Redirect in v0.5.5, v0.5.6 (#186, #210 by @pboling) * Fixed NoMethodError on missing leading slash in path (#194, #211 by @pboling) * Fixed NoMethodError on nil request object (#165, #212 by @pboling) * Fixed Unsafe String Comparison (#156, #209 by @pboling and @drosseau) * Fixed typos in Gemspec (#204, #203, #208 by @pboling) * Copyright Notice in LICENSE - added correct years (#217, #218 by @pboling) * Fixed request proxy Class constant reference scopes - was missing :: in many places (#225, #226 by @pboling) Removed * Remove direct development dependency on nokogiri (#299 by @pboling)
jperkin
pushed a commit
that referenced
this issue
Jan 18, 2022
Changelog:
Version 1.78.0
Known Issues
These are patches from library authors which were found too late to be fixed in
the release.
* Boost.Build silently skips installation of library headers and binaries in
some cases, see #104.
+ Fixed in PR#113, patch.
* Boost.Atomic fails to build when targeting UWP, see #54. Patch.
New Libraries
* No new libraries.
Updated Libraries
* Asio:
+ Added an io_uring backend that may optionally be used for all I/O
objects, including sockets, timers, and posix descriptors.
+ Added support for files, with new new classes for stream-oriented and
random-access files. This feature currently supports I/O completion
ports on Windows, and io_uring on Linux.
+ Added support for portable pipes on POSIX and Windows (when I/O
completion ports are available).
+ Added support for registered buffers, which are optimised when using
the io_uring backend.
+ Added experimental support for channels, that may be used to send and
queue completions as messages.
+ Implemented improvements to experimental::coro.
+ Disabled aligned_alloc on clang when using an MSVC runtime.
+ Changed to use a faster implementation for ip::network_v4::canonical().
+ Added template specialisations for common uses to improve compile time.
+ Reduced the size of io_context executors to a single pointer.
+ Increased the small object buffer size for execution::any_executor and
any_io_executor.
+ Fixed multi-signature handling when variadic templates are disabled.
+ Fixed compatibility with new versions of gcc and clang.
+ Fixed compilation on Solaris.
+ Fixed defence against Qt-defined macros when building with MSVC.
+ Improved error messages emitted by ssl facilities.
+ Fixed bind_executor compatibility with completion tokens.
+ Fixed build errors when BOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT is
defined.
+ Added missing move assignment operator to awaitable<>.
+ Fixed an access violation when using coroutines with MSVC, due to
incorrect alignment of allocated memory.
+ Fixed a cleanup issue in experimental::parallel_group that occured when
the execution context was shut down with parallel operations still
pending.
+ Added clarifications to the documentation on concurrency hints.
+ Added documentation on error handling techniques for C++20 coroutines.
+ Fixed various warnings.
+ Consult the Revision History for further details.
* Assert:
+ Added source_location::to_string.
* Atomic:
+ Use process-local futex operations on Android for non-IPC waiting and
notifying operations.
+ Added support for Linux targets that only define SYS_futex_time64
syscall, such as riscv32.
+ Added a workaround for incorrect result of std::alignment_of on clang 8
for 64-bit types on 32-bit x86 targets.
+ Added a ulock backend for waiting and notifying operations on Darwin
systems since Mac OS 10.12, iOS 10.0, tvOS 10.0 or watchOS 3.0.
+ On Windows, corrected discrepancy between atomic-type
::always_has_native_wait_notify and the corresponding capability macros
when targeting Windows 8 or later. The library will now directly use
WaitOnAddress and related APIs from public headers and therefore
require user to link with synchronization.lib if the user requires
Windows 8 or later by defining BOOST_USE_WINAPI_VERSION, _WIN32_WINNT
or similar macros. The library is linked automatically on compilers
that support auto-linking (e.g. MSVC).
+ Added support for types with padding bits, except unions, on compilers
that provide a way to clear the padding bits. This feature is supported
by gcc 11 and MSVC 14.2 (compiler version 19.27) and newer, as well as
other compilers supporting similar intrinsics. On compilers that don't
allow to clear the padding bits, types with padding are still generally
not supported with the exception of 80-bit long double on x86 targets.
A new BOOST_ATOMIC_NO_CLEAR_PADDING capability macro is defined to
indicate when clearing the padding is not supported.
+ Initializing constructors of atomic_ref and ipc_atomic_ref no longer
use atomic instructions to clear the padding bits in the referenced
object. This reduces the cost of the atomic reference construction.
+ Initializing constructors of atomic and ipc_atomic are now constexpr
for enums, classes and floating point types. For classes and floating
point types, the constructors are constexpr if the compiler supports
constexpr std::bit_cast, the type has no padding bytes and no padding
is required to implement native atomic operations.
+ In accordance with C++20, default constructors of atomic and ipc_atomic
now perform value initialization of the contained object. For types
without a user-defined default constructor, this means the
default-constructed atomic will be zero-initialized.
+ Added a workaround for compilation error on AIX caused by the assembler
tool not supporting numeric labels. (PR#50)
+ Added a workaround for compilation error with Visual Studio 2015 prior
to Update 3. (#52)
+ See changelog for more details.
* Beast:
+ This maintenance update brings minor bug fixes and updated CI
reporting.
+ Fixed security vulnerability CVE-2016-9840 in zlib implementation.
+ Fixed WebSocket permessage_deflate implementation. This should result
in an increase in compression performance when using Beast WebSockets.
+ Removed the test stream and test framework's dependency on RTTI. You
can now use our handy test stream to check your embedded asynchronous
communications code!
+ We'd love to know how you or your company use Beast, consider adding an
entry to the Companies and Individuals Using Beast list.
+ See the full Release Notes for a complete list of changes.
* Core:
+ Added a generic implementation to <boost/core/cmath.hpp>, enabled when
BOOST_CORE_USE_GENERIC_CMATH is defined or when the platform does not
provide the necessary facilities in <cmath>.
+ Added boost::core::type_name, a utility function that returns the name
of a type as a string.
+ Added boost::span, a C++11 implementation of C++20's std::span (Glen
Fernandes).
* Describe:
+ Added has_describe_enumerators, has_describe_bases,
has_describe_members.
+ Added enum_to_string, enum_from_string.
+ Added relational and stream insertion operators.
+ Added descriptor_by_name, descriptor_by_pointer.
* DLL:
+ Fixed missing #include, thanks to Denis Blank (PR#54)
+ Dropped TravisCI in favor of GithubAction CI
* Filesystem:
+ v4: path::filename and path::iterator no longer return an implicit
trailing dot (".") element if the path ends with a directory separator.
Instead, an empty path is returned, similar to C++17 std::filesystem.
This also affects other methods that are defined in terms of iterators
or filename, such as path::stem, path::compare or
lexicographical_compare. For example, path("a/b/") == path("a/b/.") no
longer holds true. (#193)
+ v4: path::lexically_normal no longer produce a trailing dot (".")
element and omits a directory separator after a trailing dot-dot ("..")
element in the normalized paths.
+ v4: path append operations now consider root name and root directory in
the appended path. If the appended path is absolute, or root name is
present and differs from the source path, the resulting path is
equivalent to the appended path. If root directory is present, the
result is the root directory and relative path rebased on top of the
root name of the source path. Otherwise, the behavior is similar to v3.
(#214)
+ path::lexically_normal now converts directory separators to preferred
separators in the root name of the normalized paths.
+ Optimized overloads of path::assign, path::append, path::concat and the
corresponding operators to avoid unnecessary path copying and reduce
the amount of code redundancy.
+ On POSIX systems, fixed absolute(p, base) returning a path with root
name base.root_name() if p starts with a root directory. In such a case
p is already an absolute path and should be returned as is.
+ create_directories no longer reports an error if the input path
consists entirely of dot (".") and dot-dot ("..") elements. The
implementation is no longer using recursion internally and therefore is
better protected from stack overflow on extremely long paths.
+ On Windows, remove now supports deleting read-only files. The operation
will attempt to reset the read-only attribute prior to removal. Note
that this introduces a possibility of the read-only attribute being
left unset, if the operation fails and the original value of the
attribute fails to be restored. This also affects remove_all. (#216)
+ remove_all now returns static_cast< uintmax_t >(-1) in case of error,
similar to C++17 std::filesystem.
+ Fixed a linking error about unresolved references to
Boost.ContainerHash functions when user's code includes boost/
filesystem/path.hpp but not boost/container_hash/hash.hpp and the
compiler is set to preserve unused inline functions. (#215)
+ Added a workaround for MSVC and compatible compilers eliminating path
globals cleanup in release builds. This could lead to a memory leak if
Boost.Filesystem shared library was repeatedly loaded and unloaded in
the process. (#217)
* Geometry:
+ Improvements
o PR#894 Optimization and refactoring of rtree queries.
o PR#913 DynamicGeometry and GeometryCollection support in various
algorithms (undocumented for now).
o PR#922 DynamicGeometry and GeometryCollection support in distance
(undocumented for now).
+ Solved issues
o #867 Poor performance of rtree query iterator with nearest
predicate for big k.
o #870 Compilation error in boost::geometry::self_turns.
o #896 Assertion failure in get_turns with
BOOST_GEOMETRY_NO_ROBUSTNESS.
+ Bugfixes
o PR#906 Invalid result of buffer on macos-11 with clang-12.
o PR#921 Compilation errors with c++20 (various compilers) and gcc-5.
o Various fixes in set operations and buffer.
* JSON:
+ Standalone mode of the library is deprecated.
+ Allow external libraries to forward declare value_to and value_from.
+ Fixed signed integer overflow in number parsing.
+ Add support for /Zc:implicitNoexcept- on MSVC.
* Lambda2:
+ Added special cases in operator<< and operator>> when the first
argument is a stream, to allow std::cout << _1.
+ Added operator->*.
+ Added first, second.
* Log:
+ General changes:
o Updated detection of std::codecvt specializations for char16_t and
char32_t for compatibility with C++17 and later. (PR#159)
o Added support for C++17 std::byte type to receive methods of the
inter-process message queue.
o On Windows, when building the library for Windows 8 or later, the
library will use nt62 tag in the version namespace to denote the
target OS ABI. For example, the version namespace could be named as
v2_mt_nt62. This name will be part of all symbols exported by the
library. Use the BOOST_USE_WINAPI_VERSION macro consistenly when
building Boost and your code to request the minimum target Windows
version.
o Improved performance of SSSE3 and AVX2 implementations of the dump
stream manipulator.
o Added support for CMake build system. Only library build is
supported at this moment, Boost.Build is still used for running
tests.
+ Bug fixes:
o Fixed a race condition on POSIX systems in reliable_message_queue::
open_or_create or the equivalent constructor. Multiple threads or
processes calling open_or_create concurrently with sending or
receiving messages from the same queue could end up corrupting the
queue contents and potentially crashing the process. (#162)
o Added a workaround for b2 install failing on Windows because of
missing boost_log_setup library if
BOOST_LOG_WITHOUT_SETTINGS_PARSERS is defined. (#164)
+ See changelog for more details.
* Math:
+ Add support for cubic roots.
+ Add support for constexpr versions of various standard library math
routines.
+ Add support for Bezier polynomials.
+ Improve worst-case tanh-sinh integration performance.
+ Disable inadvertant use of integral types in integration routines.
+ Minor update for erf approximations when the result is with 2ulp of 1.
+ Allow Bernoulli code to be used on platforms with no atomic integers.
+ Improve the mode of the non-central Chi Squared distribution.
+ Improve certain edge cases for <cstdfloat> complex-valued elementary
functions, see #507.
* Multi-index Containers:
+ Added contains to key-based indices (issue #35).
+ Added merge operations to key-based indices. The functionality goes
beyond the standard specification for (unordered) associative
containers in a number of ways, most notably:
o The source index can be of any type, including non key-based
indices.
o Partial merge is provided: for instance, x.merge(y,first,last)
merges only the elements of y within [first,last).
+ Previous versions of splice for sequenced and random access indices
were destructive, i.e. elements were copy-inserted into the destination
and then erased from the source. Now, splice is based on node transfer
much as merge in key-based indices, and has been similarly extended to
accept source indices of any type: in fact, splice can be regarded as a
frontend to the same functionality provided by merge in key-based
indices. For reasons of backwards compatibility, the destructive
behavior of splice has been retained in the case that the source and
destination containers have unequal allocators.
+ The fact has been documented that index iterator types do only depend
on node_type and the position of the index in its multi_index_container
, (except for hashed indices, where uniqueness/non-uniqueness is also a
dependency). This has implications on the validity of iterators to
elements transferred by merge or splice. This property is a variant of
what has been called SCARY iterators in the C++ standard mailing lists.
SCARYness is currently (August 2021) not mandated for standard
containers.
+ Iterator SCARYness is now also preserved in safe mode.
* Multiprecision:
+ Rework rational_adaptor to remove dependency on Boost.Rational and
improve performance.
+ Fix issue with type_traits and clang, see #383.
+ Fixed buggy Lehmer's GCD routine, see #370.
+ Fix mpc_complex constructors so that lossy conversions are explicit,
see #363.
+ Correct miscellaneous configuration issues (Intel intrinsic usage and
Apple clang).
+ Correct some iostream operators for unsigned char types.
+ Correct mpq_rational conversions to integer types, see #342.
* PFR:
+ Added missing #include <memory> for inclusion of std::addressof
+ Fixed -Wzero-length-array warning when dealing with empty aggregates
+ Fixed compilation on msvc compilers <= 1920 (thanks to Alexey Romanov
aka @alexey-romanov)
+ Added basic CMakeLists.txt support (thanks to @pdimov aka Peter Dimov)
+ Multiple improvements for docs, including links to https://github.com/
apolukhin/pfr_non_boost
+ Added misc/strip_boost_namespace.sh script to remove boost:: and BOOST_
prefixes
* Predef:
+ Version 1.13.1
+ Fix spelling of "epoch".
+ Add missing parenthesis in sparc.h (from tkoecker).
+ Update documentation to use Rouge code styling and Amber general style.
* Regex:
+ Breaking Change: Change \B to be the opposite of \b as per Perl
behaviour.
+ Change w32_regex_traits.hpp so that windows.h is no longer included.
+ Fxed fuzzing related issues #151, #152, #153, #156.
* System:
+ Added support for source locations to error_code.
+ Added error_code::to_string, error_condition::to_string, error_code::
what.
+ system_error::what() now contains the source location, if present.
+ Added result<T, E = error_code>, a class holding either a value or an
error, defined in <boost/system/result.hpp>.
* Utility:
+ Library documentation converted to QuickBook (thanks to Alan de
Freitas, PR#79).
* Variant2:
+ Added <boost/variant2.hpp>.
+ Added unsafe_get<I>.
+ Added visit_by_index.
+ Added operator<<.
Updated Tools
* Build:
+ Includes release of B2 version 4.7.2.
jperkin
pushed a commit
that referenced
this issue
Apr 19, 2022
# glue 1.6.2 * Modify a test for better forward compatibility with R. # glue 1.6.1 * Glue Now registers its custom knitr engines in a way that is more robust to namespace-loading edge cases that can arise during package installation (#254). # glue 1.6.0 * `glue()`, `glue_data()`, `glue_col()`, and `glue_data_col()` gain a new `.literal` argument, which controls how quotes and the comment character are treated when parsing the expression string (#235). This is mostly useful when using a custom transformer. * Trailing whitespace-only lines don't interfere with indentation (#247). # glue 1.5.1 * Jennifer Bryan is now the maintainer. * The existing custom language engines for knitr, `glue` and `glue_sql`, are documented in a new vignette (#71). *Detail added after release: glue now sets up registration of these engines in `.onLoad()`.* * `glue_col()` gives special treatment to styling functions from the crayon package, e.g. `glue_col("{blue foo}")` "just works" now, even if crayon is not attached (but is installed) (#241). * Unterminated backticks trigger the same error as unterminated single or double quotes (#237). * `glue_sql()` collapses zero-length `DBI::SQL` object into `DBI::SQL("NULL")` (#244 @shrektan). # glue 1.5.0 ## Breaking changes * Long deprecated function `collapse()` has been removed (#213) ## New functions and arguments * New `glue_sql_collapse()` function to collapse inputs and return a `DBI::SQL()` object (#103). * `glue()` gains a new `.comment` argument, to control the comment character (#193). * `glue()` gains a new `.null` argument, to control the value to replace `NULL` values with (#217, @echasnovski). ## Bugfixes and minor changes * `sql_quote_transformer()` is now allows whitespace after the trailing `*` (#218). * `compare_proxy.glue()` method defined so glue objects can be compared to strings in testthat 3e without errors (#212) * `print.glue()` no longer prints an empty newline for 0 length inputs (#214) * Unterminated comments in glue expression now throw an error (#227, @gaborcsardi) * Unterminated quotes in glue expressions now throw an error (#226, @gaborcsardi)
jperkin
pushed a commit
that referenced
this issue
May 13, 2022
fping 5.1 (2022-02-06) ====================== ## Bugfixes and other changes - Use setcap to specify specific files in fping.spec (#232, thanks @zdyxry) - Netdata: use host instead name as family label (#226, thanks @k0ste) - Netdata: use formatstring macro PRId64 (#229, thanks @gsnw) - Allow -4 option to be given multiple times (#215, thanks @normanr) - Documentation fix (#208, thanks @timgates42) - Retain privileges until after privileged setsockopt (#200, thanks @simetnicbr) - Set bind to source only when option is set (#198, thanks @dinoex) - Update Azure test pipeline (#197, thanks @gsnw) - Fix getnameinfo not called properly for IPv4 (#227, thanks @aafbsd) - Fixed wrong timestamp under Free- and OpenBSD and macOS (#217, thanks @gsnw) - Documentation updates (#240, thanks @auerswal) - Updated autotools (autoconf 2.71, automake 1.16.5, libtool 2.4.6) fping 5.0 (2020-08-05) ====================== ## Incompatible Changes - In non-quiet loop and count mode, a line is printed for every lost packet (#175, thanks @kbucheli): ``` $ fping -D -c2 8.8.8.8 8.8.8.7 [1596092373.18423] 8.8.8.8 : [0], 64 bytes, 12.8 ms (12.8 avg, 0% loss) [1596092374.18223] 8.8.8.7 : [0], timed out (NaN avg, 100% loss) [1596092374.18424] 8.8.8.8 : [1], 64 bytes, 12.3 ms (12.5 avg, 0% loss) [1596092375.18344] 8.8.8.7 : [1], timed out (NaN avg, 100% loss) 8.8.8.8 : xmt/rcv/%loss = 2/2/0%, min/avg/max = 12.3/12.5/12.8 8.8.8.7 : xmt/rcv/%loss = 2/0/100% ``` - The returned size in bytes now always excludes the IP header, so if before it reported '84 bytes' e.g. when using 'fping -l', now it reports '64 bytes'. This is to make the reported size consistent with ping(8) from iputils and also with fping when pinging a IPv6 host (which never included the IPv6 header size). ## New features - The number of sent pings is only counted when the pings are received or have timed out, ensuring that the loss ratio will be always correct. This makes it possible, for example, to use loop mode (-l) with interval statistics (-Q) and a timeout larger than period, without having the issue that initially some pings would be reported as missing (#193) - Improved precision of measurements from 10us to 1us (#136, thanks @tycho) ## Bugfixes and other changes - The reported size of received packets is now always correct on Linux even for packets > 4096 bytes (#180) - Travis CI automated testing now also macos testing and additional ubuntu distributions (#196)
jperkin
pushed a commit
that referenced
this issue
Jun 2, 2022
Upstream changes:
R6 2.5.1
Removed unused packages from Suggests section in DESCRIPTION.
R6 2.5.0
Resolved #195: Slightly clearer message when there is an error in the initialize() method.
Fixed #214: When a non-portable object inheritance was cloned, methods that were inherited (and not overridden) had the wrong environment. (#215, #217)
Printing R6 objects, no longer includes .__active__.
jperkin
pushed a commit
that referenced
this issue
Sep 13, 2022
37.1 (2022-09-03) ----------------- * Allow HTML5 `nav` tag through cleaner (#259) 37.0 (2022-08-21) ----------------- * Remove command line example from docs (#197) * Multiple pyproject.toml fixes (#251) * Confirm handling multiple inline strong (#252) * Convert RST output to HTML5 (#253) * Add Typing to classifiers (#254) * Development tweaks - coverage reporting, actions updates (#255) * Add test confirming behavior with unknown lexers (#256) 36.0 (2022-08-06) ----------------- * Enable gitpod development (#238) * Allow rst admonitions to render (#242) * Add badges to README (#243) * Update codebase for modern Python (#244) * Fix table cell spans (#245) * Allow ``math`` directive in rst (#246) * Preserve ``lang`` attribute in ``pre`` (#247) 35.0 (2022-04-19) ----------------- * Add py.typed to the built wheel (#228) * Use isolated build for tox (#229) * Fix renderer ignore (#230) * Remove legacy check command and distutils (#233) * Emit a warning when no content is rendered (#231) * Drop support for Python 3.6 (#236) * Update html attribute order in tests (#235) 34.0 (2022-03-11) ----------------- * Add static types (#225) 33.0 (2022-03-05) ----------------- * Support cmarkgfm>=0.8.0 (#224) 33.0 (2022-02-05) ----------------- * Support cmarkgfm>=0.8.0 (#224) * Support Python 3.10 32.0 (2021-12-13) ----------------- * Allow start attribute in ordered lists (#216) * No limit rendering RST one column field names (#219) 31.0 (2021-12-09) ----------------- * Render disabled checkboxes from Markdown (#217) 30.0 (2021-09-30) ----------------- * support cmarkgfm>=0.6.0 (#209)
jperkin
pushed a commit
that referenced
this issue
Jan 4, 2023
[0.17.0] - 2022-11-08
Features
Add support for nested json syntax, see #217 (@ducaale)
Add Support for bearer auth in .netrc, see #267 (@porglezomp)
Support forcing ipv4/ipv6, see #276 (@zuisong)
Other
Allow building xh using native-tls only, see #281 (@jirutka)
Warn users when translating --follow + non GET method, see #280 (@jgoday)
jperkin
pushed a commit
that referenced
this issue
Mar 12, 2023
# rgl 1.0.1 ## Major changes * The long promised deprecations of the `rgl.*` functions have happened. Now deprecated: `rgl.abclines`, `rgl.bbox`, `rgl.bg`, `rgl.clear`, `rgl.clipplanes`, `rgl.close`, `rgl.light`, `rgl.lines`, `rgl.linestrips`, `rgl.material`, `rgl.open`, `rgl.planes`, `rgl.points`, `rgl.quads`, `rgl.select3d`, `rgl.set`, `rgl.setAxisCallback`, `rgl.sprites`, `rgl.surface`, `rgl.texts`, `rgl.triangles`, and `rgl.viewpoint`. * A vignette "Deprecating the `rgl.*` interface" has been added. * Also deprecated: `elementId2Prefix`, `writeWebGL` ## Minor changes * Since `rgl.material` is deprecated and no longer contains the list of material types in its argument list, `rgl.material.names` and `rgl.material.readonly` have been added. * Similarly, `rgl.par3d.names` and `rgl.par3d.readonly` contain lists of properties that may be set or queried in `par3d()`. * The flexibility improvements for `surface3d()` in 0.111.6 were incomplete. * Argument `flip` has been added to `surface3d()` to allow front and back to be switched. # rgl 0.111.6 ## Minor changes * Added a panning example to the help page for `setUserCallbacks()`. * Replaced all calls to `sprintf` from C/C++ code with calls to `snprintf`. * `surface3d` and `rgl.surface` are now more flexible, allowing any of the 3 coordinates to be a vector or matrix as long as at least one is a matrix. * `material3d` can now specify an `id` to query properties for individual objects. * Since `rgl.material` is soon to be deprecated and no longer contain the list of material types in its argument list, `rgl.material.names` and `rgl.material.readonly` have been added. * Similarly, `rgl.par3d.names` and `rgl.par3d.readonly` contain lists of properties that may be set or queried in `par3d()`. * Made some examples conditional on interactive use to save time on CRAN. ## Bug fixes * Default mouse modes used when a window is opened by an `rgl.*` call (which is not recommended!) now match the defaults in `rgl::r3dDefaults`. * Missing values could cause `surface3d()` to segfault. * The C source code for `gl2psGetFileFormat` missed declaring a prototype. # rgl 0.110.2 ## Major changes * Material property `"blend"` has been added, to allow various kinds of blending for semi-transparent objects (issue #245). ## Minor changes * The `Buffer` object now handles reading of sparse accessors. * Low level drawing of primitives has been made more memory efficient. This is only likely to make a noticeable change with very large objects, where R was running out of memory because of unnecessary duplication. (Related to issue #260.) * Recycling of x, y and z vectors in several functions is more consistent. * The `polygon3d()` function now chooses coordinates automatically, as `triangulate()` does (PR #262.) * The `mtext3d()` and related functions such as `title3d()` now accept language objects other than expressions, as `plotmath3d()` always has (issue #273). ## Bug fixes * The bounding box could be calculated incorrectly if data all had large values (issue #250). * Shiny displays failed to load the shaders (issue #249). * `transform3d()` failed due to missing argument (issue #253). * `readOBJ()` is now more flexible in what kinds of separators it will accept. (issue #258). * Failure to initialize could cause a segfault. * On non-macOS platforms, gray-scale textures failed to display, with a message about an invalid enumerant. * The third coordinate for `adj` that was added in 0.108.3 was not rendered properly in `rglwidget()` displays of text. This sometimes caused text to disappear when it was near the far limit of the display (issue #269). * The X11 error fix in 0.109.6 could result in R freezing in `Rcmdr`. * Low level drawing functions are now more consistent about returning an invisible `NULL` if asked to plot zero items, rather than raising an error or crashing (issue #274). * Calling `axis3d()` with no ticks or labels no longer triggers an error, it now silently returns `NULL`. # rgl 0.109.6 ## Minor changes * `rglwidget()` displays now act on "pointer" events, not just "mouse" events, so they should be more usable on touch screens and tablets (PR #240). ## Bug fixes * Plotting `scene3d()` objects didn't handle suppressed axes properly, drawing the default axis instead (issue #241). * On some systems using X11, `rgl` would segfault when the "fixed" font was not found. * X11 errors could cause R to abort. # rgl 0.109.2 ## Major changes * Changes to support glTF animation: - Handling of `embedding = "modify"` for the model matrix has changed. Now the centering step is only done for `embedding = "replace"`. In addition, various bugs have been fixed. - If a subscene has no lights defined, the lights from the parent are used. - `plot.rglscene()` now ends with the root subscene as current. It also allows specification of `open3d()` parameters in a list. - The `MATn` types in `Buffer` are returned as arrays with dim `c(n, n, count)`. - The `plot3d.rglscene` method now passes `...` to `open3d()`. - The `setUserShaders()` function now allows arrays of 4x4 matrices as "uniforms", and allows additional textures to be specified. * `sprites3d()` now has the option of `rotating = TRUE`, to allow 3D sprites to rotate with the scene. * Added `getShaders()` function to get shaders used in WebGL. * Now detects if `rgl` is running within `reprex::reprex()` and if so arranges that a screenshot will be included in the output. * Added default shaders to be used in `rglwidget()`, rather than constructing them on the fly. This incompatibly affects the use of lights and clipping planes with user shaders: their data is now stored in arrays rather than multiple numbered variables. ## Minor changes * Now that `pkgdown` 2.0.0 has been released, a number of internal workarounds to support the development version have been removed. * Added `as.mesh3d()` methods for `"rglsubscene"` and `"rglscene"`. * `open3d()` now handles `useNULL` and `silent` arguments passed in `params`. * Controls passed to `playwidget()` may now include a component specifying HTML dependencies. * Added `rglwidgetClass.readAccessor()` method to let other code use the buffering. * Changed the internal organization of bounding box calculations. * All functions that produce meshes now accept material properties. Newly modified to do so using the `...` argument: `cylinder3d()`, and `getBoundary3d()`. * Updated the system requirements and installation instructions. * Solid bounding box decorations now try harder to display 3 faces (issue #206). * Now that `webshot2` is on CRAN, instructions for installing it from Github have been removed. * Sometimes `webshot2` snapshots are very slow, so the default for the `webshot` argument to `snapshot3d()` now depends on the `RGL_USE_WEBSHOT` environment variable, using `TRUE` if it is unset. (Reported by Prof. B. D. Ripley.) * If the Chrome browser is not found, `snapshot3d(webshot = TRUE)` now issues a warning and reverts to using `rgl.snapshot()`. * Buffers now use "normalized integers" to store color or texture coordinate values that lie between 0 and 1 when it saves some space. * At the request of CRAN, the `akima` package is no longer suggested. ## Bug fixes * `as.mesh3d.rglobject()` didn't handle objects with indices properly. * In WebGL, the front vs back calculation sometimes got the wrong result (issue #164). * `pop3d(tag = x)` did not always find the objects with `tag == x` if they were not in the current subscene. * The default values for `front` and `back` in `rgl.material` and `material3d` are now `"filled"`, as documented in some places. * The `fog` setting wasn't handled properly by `bg3d()`. * Numerous cases of partial argument matching were fixed (suggestion of Henrik Bengtsson in issue #170.) * Argument `col` is accepted as a synonym for `color` in `material3d()` and `rgl.material()`. * `planes3d()` objects were not displayed consistently in `rgl` windows and WebGL displays, because the bounding boxes were not computed consistently (issue #169). * Some initialization wasn't done properly in Shiny apps, so they failed after a redraw (issue #173). * Buffers are now optional, as they don't work with Shiny scene changes (also issue #173). * The NULL device would sometimes miscalculate the bounding box. * `selectpoints3d(closest = TRUE)` selected too many points when multiple objects were in the scene. * Clearing nested subscenes could cause a segfault and crash. * In `knitr` and `rmarkdown`, blank plots could be shown when `par3d(skipRedraw=TRUE)` was set (issue #188). * Objects drawn with `sprites3d()` weren't lit correctly in WebGL (issue #189). * Objects with textures were sometimes drawn more than once, both before the texture loaded and after. This was most noticeable for objects with user textures. * Axis mode `"pretty"` got lost when scenes were redrawn. * Tick labels were sometimes lost in WebGL displays and `snapshot3d()` results (issue #197). * The new material properties from 0.107.10 and 0.108.3 were not handled properly by `plotmath3d()`. * `rglMouse()` did not set the default value of the drop-down selector properly (issue #213). * `merge.mesh3d()`, used by `filledContour3d()`, didn't handle colors properly (issue #212). * `bg3d(sphere = TRUE)` has been fixed (issue #207). * Textures were not appearing on spheres, and front-back differences weren't being rendered (issue #217). * When "knitting" within RStudio under R 4.2.0 on Windows, `rgl` scenes didn't appear (reported by Dieter Menne.) A workaround has been added. * In `rglwidget()`, axis labels were not always displayed, and did not move with solid bounding box decorations properly (issue #206). * On some systems, `lines3d()` using both missing values and transparency did not draw properly (issue #234, originally reported by Gaspar Jekely). * The `rglShared()` example failed when `crosstalk` was uninstalled. # rgl 0.108.3.2 ## Bug fixes * Changes introduced in 0.100.50 lacked checks; these caused segfaults in Windows with R 4.2.0 and RStudio (issue #208). * A typo caused problems loading fonts on some systems. # rgl 0.108.3 ## Major changes * Added `getBoundary3d()` function to extract the boundary edges of a mesh. * Added material property `tag`, a string associated with each object. The value is reported by `ids3d(tags = TRUE)` and may be used to select objects in most functions that use ids, but otherwise is largely ignored by `rgl`. The `tagged3d()` function returns information on tags. * Primitive types (points, lines, segments, triangles, quads) can now accept an `indices` parameter, similar to the indices in `mesh3d` objects. * Added `Buffer` object, based on glTF design, for holding binary data for `rglwidget()`. ## Minor changes * Allowed for a third coordinate in `text3d()`'s `adj` parameter. * Added support for `adj`, `pos` and `offset` to `sprites3d()`. * Added support for `pos` values of `0` (at specified location), `5` (in front of it), and `6` (behind it) in `text3d()`, `sprites3d()` and `plotmath3d()`. * `crosstalk` is now a Suggested package, rather than a required one. * The `Makevars.ucrt` file has been modified with contributions from Tomas Kalibera to work with his `winutf8` build of R. * `bgplot3d()` no longer pauses for each page when running examples. * `deldir` version 1.0-2 is incompatible with `rgl`. Added the `checkDeldir()` function to avoid running it. * `shade3d()` treated texture coordinates like colors, and duplicated the first one for the whole face when `meshColor = "faces"` was chosen. Instead, they are now treated like vertex coordinates. (Reported by Michael Sumner in issue #145). * Corrected the documentation and made the implementations of `asHomogeneous()`, `asEuclidean()` etc. more consistent. * An `as.rglscene()` generic has been added, though no methods are defined in this package. * `downlit` 0.4.0 has been released with support for `rgl`, so instructions for installing the devel version have been removed. ## Bug fixes * Fixed rendering of text as sprites3d() objects. * Added `--static` flag to configure script for FreeType installation. (Suggestion of Simon Urbanek and Prof. Brian Ripley.) * `shade3d()`, `wire3d()` and `dots3d()` overrode `"front"` and `"back"` material settings in mesh objects. * `rglwidget()` handling of bounding box decorations had several bugs. * `rgl` could not find routines in the DLL on some Windows installs (Issue 148.) * Some cases where allocations were not protected have been fixed.
jperkin
pushed a commit
that referenced
this issue
Oct 20, 2023
Fix PKGNAME while here. Changelog for rest-server 0.12.1 (2023-07-09) ============================================ The following sections list the changes in rest-server 0.12.1 relevant to users. The changes are ordered by importance. Summary ------- * Fix #230: Fix erroneous warnings about unsupported fsync * Fix #238: API: Return empty array when listing empty folders * Enh #217: Log to stdout using the `--log -` option Details ------- * Bugfix #230: Fix erroneous warnings about unsupported fsync Due to a regression in rest-server 0.12.0, it continuously printed `WARNING: fsync is not supported by the data storage. This can lead to data loss, if the system crashes or the storage is unexpectedly disconnected.` for systems that support fsync. We have fixed the warning. restic/rest-server#230 restic/rest-server#231 * Bugfix #238: API: Return empty array when listing empty folders Rest-server returned `null` when listing an empty folder. This has been changed to returning an empty array in accordance with the REST protocol specification. This change has no impact on restic users. restic/rest-server#238 restic/rest-server#239 * Enhancement #217: Log to stdout using the `--log -` option Logging to stdout was possible using `--log /dev/stdout`. However, when the rest server is run as a different user, for example, using `sudo -u restic rest-server [...] --log /dev/stdout` This did not work due to permission issues. For logging to stdout, the `--log` option now supports the special filename `-` which also works in these cases. restic/rest-server#217
jperkin
pushed a commit
that referenced
this issue
Oct 31, 2023
texmath (0.12.8.4) * TeX reader: ignore `\allowbreak` (#230). * TeX reader: handle `*{5}{lr}` in array column specifier (#229). * OMML reader: allow `m:e` to be missing in `m:nary` (#228). Technically this is not allowed, according to the spec, but Word and LibreOffice seem to tolerate it. texmath (0.12.8.3) * OMML writer: use "on" and "off" instead of "1" and "0" for m:CT_OnOff type. It is said that "1" and "0" work in Word but not Powerpoint. texmath (0.12.8.2) * Typst writer: use binom instead of a fraction (jgm/pandoc#9063). texmath (0.12.8.1) * Typst writer: several fixes (#223, Lleu Yang). + Escape quotes (") in inQuotes + Accent `\8407` corresponds to `arrow()` + Write `#none`'s for matrices with blanks at the beginning of a row texmath (0.12.8) * Expose Text.TeXMath.Shared [API change] * Typst writer: Fix bug where 's' turned into 'space' (#219). * Typst writer: Fix handling of overline (#214). * Typst writer: Fix underbrace (#217). * Typst writer: Improve some accents (#216). * TeX writer: don't include \ on last line of matrix. * TeX writer: Remove escaping of spaces inside \text{}. It isn't needed, and it causes problems in MathJax rendering. * TeX reader: allow empty matrices. * MathML writer: Fix rendering of vectors (#218). * Depend on external typst-symbols package. texmath (0.12.7.1) * Typst writer: + Improve under/overbrace/bracket/line. + Fix bugs with super/subscript grouping (#212). + Fix case where super/subscript is on an empty element, by inserting a zws. texmath (0.12.7) * Add typst writer. New module: Text.TeXMath.Writers.Typst. * TeX reader: Support multilined environment. Closes #210.
jperkin
pushed a commit
that referenced
this issue
Nov 27, 2023
What's Changed - Added: Horizontal Scrollbar to Editor by @AmmarAbouZor in #217 - Changed: Upgrade Crates Ratatui & Tui-Textarea with breaking changes by @AmmarAbouZor in #224 - Added: Visual Mode to Built-in Editor by @AmmarAbouZor in #239
jperkin
pushed a commit
that referenced
this issue
Jan 25, 2024
## Version 0.5.1
Changes:
* LaTeX math extension (`MD_FLAG_LATEXMATHSPANS`) now requires that opener
mark is not immediately preceded with alpha-numeric character and similarly
that closer mark is not immediately followed with alpha-numeric character.
So for example `foo$ x + y = z $` is not recognized as LaTeX equation
anymore because there is no space between `foo` and the opening `$`.
* Table extension (`MD_FLAG_TABLES`) now recognizes only tables with no more
than 128 columns. This limit has been imposed to prevent a pathological
case of quadratic output size explosion which could be used as DoS attack
vector.
* We are now more strict with `MD_FLAG_PERMISSIVExxxAUTOLINKS` family of
extensions with respect to non-alphanumeric characters, with the aim to
mitigate false positive detections.
Only relatively few selected non-alphanumeric are now allowed in permissive
e-mail auto-links (`MD_FLAG_PERMISSIVEEMAILAUTOLINKS`):
- `.`, `-`, `_`, `+` in user name part of e-mail address; and
- `.`, `-`, `_` in host part of the e-mail address.
Similarly for URL and e-mail auto-links (`MD_FLAG_PERMISSIVEURLAUTOLINKS` and
`MD_FLAG_PERMISSIVEWWWAUTOLINKS`):
- `.`, `-`, `_` in host part of the URL;
- `/`, `.`, `-`, `_` in path part of the URL;
- `&`, `.`, `-`, `+`, `_`, `=`, `(`, `)` in the query part of the URL
(additionally, if present, `(` and `)` must form balanced pairs); and
- `.`, `-`, `+`, `_` in the fragment part of the URL.
Furthermore these characters (with some exceptions like where they serve as
delimiter characters, e.g. `/` for paths) are generally accepted only when
an alphanumeric character both precedes and follows them (i.e. these cannot
be "stacked" together).
Fixes:
* Fix several bugs where we haven't properly respected already resolved spans
of higher precedence level in handling of permissive auto-links extensions
(family of `MD_FLAG_PERMISSIVExxxAUTOLINKS` flags), LaTeX math extension
(`MD_FLAG_LATEXMATHSPANS`) and wiki-links extension (`MD_FLAG_WIKILINKS`)
of the form `[[label|text]]` (with pipe `|`). In some complex cases this
could lead to invalid internal parser state and memory corruption.
Identified with [OSS-Fuzz](https://github.com/google/oss-fuzz).
* [#222](mity/md4c#222):
Fix strike-through extension (`MD_FLAG_STRIKETHROUGH`) which did not respect
same rules for pairing opener and closer marks as other emphasis spans.
* [#223](mity/md4c#223):
Fix incorrect handling of new-line character just at the beginning and/or
end of a code span where we were not following CommonMark specification
requirements correctly.
## Version 0.5.0
Changes:
* Changes mandated by CommonMark specification 0.30.
Actually there are only very minor changes to recognition of HTML blocks:
- The tag `<textarea>` now triggers HTML block (of type 1 as per the
specification).
- HTML declaration (HTML block type 4) is not required to begin with an
upper-case ASCII character after the `<!`. Any ASCII character is now
allowed. Also it now doesn't require a whitespace before the closing `>`.
Other than that, the newest specification mainly improves test coverage and
clarifies its wording in some cases, without affecting the implementation.
Refer to [CommonMark
0.30 notes](https://github.com/commonmark/commonmark-spec/releases/tag/0.30)
for more info.
* Make Unicode-specific code compliant to Unicode 15.1.
* Update list of entities known to the HTML renderer from
https://html.spec.whatwg.org/entities.json.
New Features:
* Add extension allowing to treat all soft break as hard ones. It has to be
explicitly enabled with `MD_FLAG_HARD_SOFT_BREAKS`.
Contributed by [l-m](https://github.com/l1mey112).
* Structure `MD_SPAN_A_DETAIL` now has a new member `is_autolink`.
Contributed by [Jens Alfke](https://github.com/snej).
* `md2html` utility now supports command line options `--html-title` and
`--html-css`.
Contributed by [Andreas Baumann](https://github.com/andreasbaumann).
Fixes:
* [#163](mity/md4c#163):
Make HTML renderer to emit `'\n'` after the root tag when in the XHTML mode.
* [#165](mity/md4c#165):
Make HTML renderer not to percent-encode `'~'` in URLs. Although it does
work, it's not needed, and it can actually be confusing with URLs such as
`http://www.example.com/~johndoe/`.
* [#167](mity/md4c#167),
[#168](mity/md4c#168):
Fix multiple instances of various buffer overflow bugs, found mostly using
a fuzz testing. Contributed by [dtldarek](https://github.com/dtldarek) and
[Thierry Coppey](https://github.com/TCKnet).
* [#169](mity/md4c#169):
Table underline now does not require 3 characters per table column anymore.
One dash (optionally with a leading or tailing `:` appended or prepended)
is now sufficient. This improves compatibility with the GFM.
* [#172](mity/md4c#172):
Fix quadratic time behavior caused by unnecessary lookup for link reference
definition even if the potential label contains nested brackets.
* [#173](mity/md4c#173),
[#174](mity/md4c#174),
[#212](mity/md4c#212),
[#213](mity/md4c#213):
Multiple bugs identified with [OSS-Fuzz](https://github.com/google/oss-fuzz)
were fixed.
* [#190](mity/md4c#190),
[#200](mity/md4c#200),
[#201](mity/md4c#201):
Multiple fixes of incorrect interactions of indented code block with a
preceding block.
* [#202](mity/md4c#202):
We were not correctly calling `enter_block()` and `leave_block()` callbacks
if multiple HTML blocks followed one after another; instead previously
such blocks were merged into one.
(This may likely impact only applications interested in Markdown's AST,
and not just converting Markdown to other formats like HTML.)
* [#210](mity/md4c#210):
The `md2html` utility now handles nested images with optional titles
correctly.
* [#214](mity/md4c#214):
Tags `<h2>` ... `<h6>` incorrectly did not trigger HTML block.
* [#215](mity/md4c#215):
The parser incorrectly did not accept optional tabs after setext header
underline.
* [#217](mity/md4c#217):
The parser incorrectly resolved emphasis in some situations, if the emphasis
marks were enclosed by punctuation characters.
jperkin
pushed a commit
that referenced
this issue
Apr 3, 2024
Features / Improvements ✨
Links should be "openable" (#43)
Add support for previewing images in room scrollback (#108)
Enable sending strikethrough text (#141)
Support composing messages in an external editor (#155)
Add support for logging in with SSO (#160)
Add new command for logging out of iamb session (#162)
Support custom sorting for room and user lists (#170)
feat: desktop file for GUI environment launchers (#178)
Add a new :chats window that lists both DMs and Rooms (#184)
Add support for desktop notifications (#192)
Support coloring entire message with the user color (#193)
Indicate and sort on rooms with unread messages (#205)
Support following the .well-known entries for a username's domain (#209)
Add support for threads (#216)
Add support for custom key macros (#217)
Support displaying shortcodes instead of Emojis in messages (#222)
Support configuring user gutter width (#223)
Enable autolinking when rendering Markdown (#226)
Support notifications via terminal bell (#227)
Support loading a TOML configuration (#229)
Add commands for importing and exporting room keys (#233)
Documentation / README updates 📚
Fix example config (#140)
Add more documentation (#166)
Update README.md to add openSUSE Tumbleweed (#191)
Add snap install instructions (#210)
Add example of mapping "V" to toggle message selection mode (#195)
Update manual pages to use mdoc(7) and list commands (#230)
Add an icon for iamb (#232)
Bug Fixes 🐞
Fix not showing display names in already synced rooms (#171)
Fix image preview offset (#179)
Update to ratatui-image@0.4.3 to use native sixel lib (#181)
Fix truncation/padding for non-ASCII sender names (#182)
Fix crash on small image preview (#198)
Download rooms keys from backups if they exist (#211)
Ignore key releases on platforms that support it (#220)
Provide better error message for M_UNKNOWN_TOKEN (#101)
Fix entering thread view when there's no messages yet (#224)
Fix image previews in replies (#225)
Reset message bar when ! is passed with :cancel (#231)
Wait to log in before starting background tasks (#234)
Performance ⏱️
Reduce CPU usage by instead fetching read receipts after related sync events (#168)
Load receipts for room before acquiring lock (#213)
Building / Housekeeping 🧹
Update Cargo.lock file (#157)
Update modalkit for newer ratatui and crossterm
Fix CI workflow (#164)
Use mozilla-actions/sccache-action for caching builds (#169)
Enable direnv for Nix flakes (#183)
Update to matrix-sdk@0.7.1 (#200)
Rename Nix flake build input from pkgconfig to pkg-config (#203)
Update modalkit dependencies (#204)
Move LTO into its own "release-lto" profile (#207)
Fix Nix flake hashes (#206)
Pull in modalkit repository with a Cargo.lock (#208)
Nix flake updates (#214)
Update to ratatui-image@0.8.1 (#215)
Support linking against system OpenSSL (#218)
GitHub workflow should use --locked to avoid broken Cargo.lock (#219)
Fix odd Windows-only compile error (#221)
jperkin
pushed a commit
that referenced
this issue
May 1, 2024
Version 1.7.0 ............. Released on 2024-04-27 * Drop Python 3.7 support, add Python 3.12 support * `#221 <https://github.com/Kozea/cairocffi/pull/225>`_: Add environment variable to set folder where DLLs are installed on Windows * `#225 <https://github.com/Kozea/cairocffi/pull/225>`_: Use Ruff instead of Flake8 and isort Version 1.6.1 ............. Released on 2023-07-24 * `#217 <https://github.com/Kozea/cairocffi/issues/217>`_: Repair installation with PyInstaller Version 1.6.0 ............. Released on 2023-06-12 **This version uses a new CFFI mode that may break your program.** CairoCFFI now uses Flit for packaging and is also distributed as a Python wheel. Please test carefully and don’t hesitate to report issues before using it in production. * `#216 <https://github.com/Kozea/cairocffi/pull/216>`_: Use ABI-level in-line CFFI mode Version 1.5.1 ............. Released on 2023-04-15 * `#212 <https://github.com/Kozea/cairocffi/issues/212>`_: Bring back XCB support during wheel generation Version 1.5.0 ............. Released on 2023-03-17 * `#106 <https://github.com/Kozea/cairocffi/issues/106>`_, `#200 <https://github.com/Kozea/cairocffi/issues/200>`_: Fallback to manual PNG file creation on hardened systems * `#210 <https://github.com/Kozea/cairocffi/pull/210>`_: Use pyproject.toml for packaging and remove other useless files Version 1.4.0 ............. Released on 2022-09-23 * `#205 <https://github.com/Kozea/cairocffi/pull/205>`_: Use pikepdf to parse generated PDF * `#171 <https://github.com/Kozea/cairocffi/pull/171>`_: Don’t use deprecated pytest-runner anymore Version 1.3.0 ............. Released on 2021-10-04 * `2cd512d <https://github.com/Kozea/cairocffi/commit/2cd512d>`_: Drop Python 3.6 support * `#196 <https://github.com/Kozea/cairocffi/pull/196>`_: Fix import `constants.py` import * `#169 <https://github.com/Kozea/cairocffi/pull/169>`_: Add extra library name "cairo-2.dll" * `#178 <https://github.com/Kozea/cairocffi/pull/178>`_: Workaround for testing date string with cairo 1.17.4 * `#186 <https://github.com/Kozea/cairocffi/pull/186>`_: Fix link in documentation * `#195 <https://github.com/Kozea/cairocffi/pull/195>`_: Fix typo in documentation * `#184 <https://github.com/Kozea/cairocffi/pull/184>`_, `a4fc2a7 <https://github.com/Kozea/cairocffi/commit/a4fc2a7>`_: Clean .gitignore Version 1.2.0 ............. Released on 2020-10-29 * `#152 <https://github.com/Kozea/cairocffi/pull/152>`_: Add NumPy support * `#143 <https://github.com/Kozea/cairocffi/issues/143>`_: Make write_to_png function work on hardened systems * `#156 <https://github.com/Kozea/cairocffi/pull/156>`_: Use major version name to open shared libraries * `#165 <https://github.com/Kozea/cairocffi/pull/165>`_: Don’t list setuptools as required for installation Version 1.1.0 ............. Released on 2019-09-05 * `#135 <https://github.com/Kozea/cairocffi/pull/135>`_, `#127 <https://github.com/Kozea/cairocffi/pull/127>`_, `#119 <https://github.com/Kozea/cairocffi/pull/119>`_: Clean the way external libraries are found * `#126 <https://github.com/Kozea/cairocffi/pull/126>`_: Remove const char* elements from cdef * Support Cairo features up to 1.17.2 * Fix documentation generation Version 1.0.2 ............. Released on 2019-02-15 * `#123 <https://github.com/Kozea/cairocffi/issues/123>`_: Rely on a recent version of setuptools to handle VERSION Version 1.0.1 ............. Released on 2019-02-12 * `#120 <https://github.com/Kozea/cairocffi/issues/120>`_: Don't delete _generated modules on ffi_build import Version 1.0.0 ............. Released on 2019-02-08 6 years after its first release, cairocffi can now be considered as stable. * Drop Python 2.6, 2.7 and 3.4 support * Test with Python 3.7 * Clean code, tests and packaging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: