Changelog from https://gitlab.com/guile-git/guile-git/-/releases
Changes in 0.5.2
Bug fix
Fix crash when fetching multiple sub-modules
This bug was reported at https://issues.guix.gnu.org/48855. It
could lead to crashes via SIGSEGV or SIGILL while fetching
multiple sub-modules in a row.
Changes in 0.5.1
Bug fix
Fix crash when using config-foreach or config-fold
This bug was reported at https://issues.guix.gnu.org/47808. It
could lead to segmentation faults in tests/config.scm while
running make check.
Changes in 0.5.0
New functionality
New diff bindings in (git diff)
These bindings allow you to compute and print a diff between two
different trees.
New configuration parsing support in (git config)
This new module provides an interface to obtain configuration
value as you would do on with the git config command. As a
corollary, it introduces an incompatible change: the internal
module previously known as (git config) has been renamed to (git
configuration). It is not meant to be used directly by
applications though, so you should not notice it.
New tag procedures: ‘tag-fold’, ‘tag-foreach’
New tree procedures: ‘tree-entry-byname’, ‘tree-entry-type’
New remote procedures: ‘remote-url’, ‘remote-set-url!’
Submodule interface changes
The submodule-update procedure accepts the new #:allow-fetch? and
#:fetch-options arguments. The latter allows you to specify
“fetch options”, such as the URL of an HTTP/HTTPS proxy. There’s
also a new submodule-set-url! procedure.
Bug fixes
commit: Prevent dangling repository references
Fix “make check” for tests involving SSH
Changes in 0.4.0
New Functionality
Support for HTTP and HTTPS proxies
One can now specify the HTTP and HTTPS via the #:proxy-url
parameter of make-fetch-options. Those fetch options must then be
passed to fetch, or they can be added to the clone options passed
to clone.
Support for progress report
Clones and fetches can take some time and you may want to tell
users what’s going on. To help with that, make-fetch-options now
takes a #:transfer-progress option; it should be either #f or a
one-argument procedure that will be called with an
<indexer-progress> record every time progress is made. This
record contains information about the total number of objects
being processed, the number of objects already retrieved, and the
number of objects already indexed.
Bug Fixes
Fix typo that made repository-index and repository-refdb unusable
0.7.3
-----
* Support binary bodies in responses
* fix flake8
* move RequestInfo to compat
* drop \`.travis.yml\`
* basic CI using github actions add codecov and add flake8
* basic CI using github actions
* basic CI using github actions
* basic CI using github actions
* basic CI using github actions
* basic CI using github actions
* (feat) add unit tests
* (feat) allow for callbacks to be called before raising of exception
* add \`py.typed\` (PEP 561)
* Fix setuptools warnings by replacing dashes in keys with underscores
Version 3.0.7
-------------
- Fixed bug 345, in which delimitedList changed expressions in place
using expr.streamline(). Reported by Kim Gräsman, thanks!
- Fixed bug 346, when a string of word characters was passed to WordStart
or WordEnd instead of just taking the default value. Originally posted
as a question by Parag on StackOverflow, good catch!
- Fixed bug 350, in which White expressions could fail to match due to
unintended whitespace-skipping. Reported by Fu Hanxi, thank you!
- Fixed bug 355, when a QuotedString is defined with characters in its
quoteChar string containing regex-significant characters such as ., *,
?, [, ], etc.
- Fixed bug in ParserElement.run_tests where comments would be displayed
using with_line_numbers.
- Added optional "min" and "max" arguments to `delimited_list`. PR
submitted by Marius, thanks!
- Added new API change note in `whats_new_in_pyparsing_3_0_0`, regarding
a bug fix in the `bool()` behavior of `ParseResults`.
Prior to pyparsing 3.0.x, the `ParseResults` class implementation of
`__bool__` would return `False` if the `ParseResults` item list was empty,
even if it contained named results. In 3.0.0 and later, `ParseResults` will
return `True` if either the item list is not empty *or* if the named
results dict is not empty.
# generate an empty ParseResults by parsing a blank string with
# a ZeroOrMore
result = Word(alphas)[...].parse_string("")
print(result.as_list())
print(result.as_dict())
print(bool(result))
# add a results name to the result
result["name"] = "empty result"
print(result.as_list())
print(result.as_dict())
print(bool(result))
Prints:
[]
{}
False
[]
{'name': 'empty result'}
True
In previous versions, the second call to `bool()` would return `False`.
- Minor enhancement to Word generation of internal regular expression, to
emit consecutive characters in range, such as "ab", as "ab", not "a-b".
- Fixed character ranges for search terms using non-Western characters
in booleansearchparser, PR submitted by tc-yu, nice work!
- Additional type annotations on public methods.
Changes in MySQL 5.7.37
Audit Log Notes
Previously, each event logged by MySQL Enterprise Audit included the SQL statement literal text. To provide an alternative (because it is possible that statements contain sensitive information), the audit log filtering language now supports logging a statement's digest rather than its literal text. For example, instead of logging this statement:
SELECT * FROM orders WHERE some_sensitive_column=1234567
The audit log plugin can log this digest:
SELECT * FROM `orders` WHERE `some_sensitive_column` = ?
This is similar to what is already logged for prepared statements, for which parameter markers appear rather than actual data values.
To perform digest logging, use audit filter definitions that replace the statement literal text by its corresponding digest, as discussed in Replacement of Event Field Values.
Because text replacement occurs at an early auditing stage (during filtering), the choice of whether to log statement literal text or digest values applies regardless of log format written later (that is, whether the audit log plugin produces XML or JSON output).
Compilation Notes
Binary packages that include curl rather than linking to the system curl library have been upgraded to use curl 7.80.0.
SQL Function and Operator Notes
Queries making use of the MBRContains() function did not employ all available spatial indexes.
The FORMAT() function returned a formatted number without showing the thousands separator and grouping between separators when either the es_ES or es_MX locale was specified.
Packaging Notes
The GnuPG build key used to sign MySQL downloadable packages has been updated. The previous GnuPG build key is set to expire on 2022-02-16. For information about verifying the integrity and authenticity of MySQL downloadable packages using GnuPG signature checking, or to obtain a copy of our public GnuPG build key, see Signature Checking Using GnuPG.
Due to the GnuPG key update, systems configured to use repo.mysql.com may report a signature verification error when upgrading to MySQL 5.7.37 and higher or to MySQL 8.0.28 and higher using apt or yum. Use one of the following methods to resolve this issue:
Manually reinstall the MySQL APT or YUM repository setup package from https://dev.mysql.com/downloads/.
Download the MySQL GnuPG public key and add it your system GPG keyring.
For MySQL APT repository instructions, see Appendix A: Adding and Configuring the MySQL APT Repository Manually.
For MySQL YUM repository instructions, see Upgrading MySQL with the MySQL Yum Repository.
Bugs Fixed
InnoDB: The buf_validate() function in the InnoDB sources was optimized, improving performance on debug builds.
Thanks to Hobert Lu for the contribution.
Partitioning: Creating a table with nondeterministic functions in generated column expressions should not be possible, but this was not enforced in all cases; a series of one or more ALTER TABLE statements could be employed to arrive at a partitioned table with one or more such generated columns. When attempting to execute the CREATE TABLE statement obtained by running SHOW CREATE TABLE against this table, MySQL rejected the statement with a misleading error message referring to the partitioning expression rather than to the problematic column, despite the fact that the partitioning expression itself was legal.
This was caused by the result of a check for any unsafe expressions defined for a generated column (in the internal variable thd->safe_to_cache_query), which was later checked again without being cleared while parsing the partition expression, leading to an error even when the partition expression did not refer to the problematic generated column expression. Now in such cases, we reset thd->safe_to_cache_query before parsing the partition function.
The issue of allowing the use of certain nondeterminstic functions (AES_ENCRYPT(), AES_DECRYPT(), RANDOM_BYTES()) in generated columns is handled separately.
Partitioning: A query using an index other than the primary key of a partitioned table sometimes resulted in excessive CPU load.
Replication: When the PAD_CHAR_TO_FULL_LENGTH SQL mode was enabled on a replica server, trailing spaces could be added to a replication channel’s name in the replication metadata repository tables, resulting in errors in replication operations that identified the channel using that data. The issue has now been fixed in MySQL 8.0 by using VARCHAR for character columns, and in MySQL 5.7 by disabling the SQL mode when reading from those tables. Thanks to Brian Yue for the contribution.
MySQL 5.7 did not handle the thread_stack variable in the same manner as MySQL 5.6 or MySQL 8.0.
It was possible in some cases to create a generated column of type SERIAL, which is not allowed.
See Numeric Data Type Syntax, and CREATE TABLE and Generated Columns, for more information
Statements which commit a transaction implicitly or explicitly are not allowed inside a trigger or a stored function. Both CREATE TRIGGER and CREATE FUNCTION should report an error (ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG) in this case, but did not correctly handle DROP TABLESPACE.
The MySQL session used for online keyring migration was not closed gracefully after the migration was complete, resulting in an “Aborted connection” note being printed to the error log.
SHOW PROCESSLIST could read freed memory when accessing the query string belonging to a connection that was in the process of deleting a prepared statement.
Privileges were not checked correctly for ALTER USER ... IDENTIFIED WITH ... BY.
-The asynchronous behavior of Xlib is kept intact. It guarantees that the
global shortcut daemon starts correctly with the session after a change in the
behavior of libx11 1.7.3.1.
Upstream changes:
2021-01-06 Antonio Diaz Diaz <antonio@gnu.org>
* Version 1.17 released.
* main_loop.c (exec_global): Make commands 'q' and 'Q' work in a
global command. (Reported by J. A. Harris).
* main.c: New option '-E, --extended-regexp'.
(Suggested by Shawn Wagner).
* io.c (read_stream_line, write_stream): Add filename parameter.
Print the file name in case of error. (Reported by Dan Jacobson).
* global.c: Integrate 'resize_line_buffer' into 'set_active_node'.
* buffer.c: Integrate 'resize_undo_buffer' into 'push_undo_atom'.
2020-02-20 Antonio Diaz Diaz <antonio@gnu.org>
* Version 1.16 released.
* regex.c (line_replace): Accept 's/^/#/g' as valid.
(Reported by Bjoern Wibben).
* main_loop.c: Remove length limit of prompt string.
(Reported by Tim Chase).
* main.c: Set a valid invocation_name even if argc == 0.
* ed.texi: Extended operators depend on regex implementation.
(Reported by Brian Zwahr).
* ed.texi: Several fixes and improvements.
2019-01-01 Antonio Diaz Diaz <antonio@gnu.org>
* Version 1.15 released.
* io.c (print_line): Make command 'l' print '\\' before every
'$' within the text. (Reported by Ori Avtalion).
* main_loop.c (extract_addresses): Fix address ',,' to mean '$,$'
instead of '1,$'. (Reported by Matthieu Felix).
* regex.c (extract_replacement): Allow newlines even if global.
* main_loop.c (exec_command): Make command 'c' reject address 0.
* ed.texi: Minor fixes.
* configure: Accept appending to CFLAGS, 'CFLAGS+=OPTIONS'.
2017-02-22 Antonio Diaz Diaz <antonio@gnu.org>
* Version 1.14.2 released.
* main.c (show_strerror) Revert to using '!scripted' instead of
'verbose' to enable diagnostics.
Upstream changes:
Changes for version 1.991 - 2022-01-21
Enforce text files in some functions, as warned in #18.
Change up some diag messages: 1) lowercase first letter 2) not ! at end, and 3) use "file" instead of "filename". If you were matching on those, you may need to update your patterns.
Upstream changes:
Changes for version 2.10 - 2021-03-27
Fixed handling of undirected graphs in Dot writer. Thanks to Ingrid Falk for bug report and fix: RT#22785
Upstream changes:
0.010 2021-12-01
- Added verbosity to test (uid66)
- Fixed bug with $ref and sibling $id
- Added TO_JSON method to Error class (ehuelsmann)
- Fixed bug with wrong detection of booleans
0.009-TRIAL 2021-11-28
- Trial release to find the bug with type boolean
