| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
[0.3.0] - 2021-09-10
Bug Fixes:
-Fix default regexes and references in docs (#7)
Documentation:
-Update installation instructions for Arch Linux
-Add badge for joining the Matrix chat
-Update example regexes
-Update the default regex in scoped config example
Features:
-Support parsing the missing scopes with default_scope (#8)
-Support generating a changelog scoped to a directory (#11)
Miscellaneous Tasks:
-Upgrade dependencies
|
|
v102
----
- Add `BinaryenUpdateMaps` to the C API.
- Adds a TrapsNeverHappen mode (#4059). This has many of the benefits of
IgnoreImplicitTraps, but can be used safely in more cases. IgnoreImplicitTraps
is now deprecated.
- Adds type argument for BinaryenAddTable method (#4107). For the binaryen.js api
this parameter is optional and by default is set to funcref type.
- Replace `BinaryenExpressionGetSideEffects`'s features parameter with a module
parameter.
|
|
This release contains numerous bug fixes, and also the following
new features:
* The GNU Binutils sources now requires a C99 compiler and library to
build.
* Support for the arm-symbianelf format has been removed.
* Support for Realm Management Extension (RME) for AArch64 has been
added.
* A new linker option '-z report-relative-reloc' for x86 ELF targets
has been added to report dynamic relative relocations.
* A new linker option '-z start-stop-gc' has been added to disable
special treatment of __start_*/__stop_* references when
--gc-sections.
* A new linker options '-Bno-symbolic' has been added which will
cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
* The readelf tool has a new command line option which can be used to
specify how the numeric values of symbols are reported.
--sym-base=0|8|10|16 tells readelf to display the values in base 8,
base 10 or base 16. A sym base of 0 represents the default action
of displaying values under 10000 in base 10 and values above that in
base 16.
* A new format has been added to the nm program. Specifying
'--format=just-symbols' (or just using -j) will tell the program to
only display symbol names and nothing else.
* A new command line option '--keep-section-symbols' has been added to
objcopy and strip. This stops the removal of unused section symbols
when the file is copied. Removing these symbols saves space, but
sometimes they are needed by other tools.
* The '--weaken', '--weaken-symbol' and '--weaken-symbols' options
supported by objcopy now make undefined symbols weak on targets that
support weak symbols.
* Readelf and objdump can now display and use the contents of .debug_sup
sections.
* Readelf and objdump will now follow links to separate debug info
files by default. This behaviour can be stopped via the use of the
new '-wN' or '--debug-dump=no-follow-links' options for readelf and
the '-WN' or '--dwarf=no-follow-links' options for objdump. Also
the old behaviour can be restored by the use of the
'--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly
changed. When enabled, the option allows for the loading of symbol
tables and string tables from the separate files which can be used
to enhance the information displayed when dumping other sections,
but it does not automatically imply that information from the
separate files should be displayed.
If other debug section display options are also enabled (eg
'--debug-dump=info') then the contents of matching sections in both
the main file and the separate debuginfo file *will* be displayed.
This is because in most cases the debug section will only be present
in one of the files.
If however non-debug section display options are enabled (eg
'--sections') then the contents of matching parts of the separate
debuginfo file will *not* be displayed. This is because in most
cases the user probably only wanted to load the symbol information
from the separate debuginfo file. In order to change this behaviour
a new command line option --process-links can be used. This will
allow di0pslay options to applied to both the main file and any
separate debuginfo files.
* Nm has a new command line option: '--quiet'. This suppresses "no
symbols" diagnostic.
|
|
Highlights of mold 0.9.5:
- In 0.9.4, we changed the mold's behavior on remaining weak undefined
symbols, so that they would be resolved to address zero if we were
creating a shared object file with the -z defs option. Now, such symbols
will be promoted to dynamic symbols so that they'll get another chance
to be resolved at run-time. This change fixes a regression of Firefox
build failure (#114), which depends on this particular linker behavior
to export symbols from libxul.so.
- mold can now be built on macOS. Note that mold is still able to produce
only ELF (Unix) files — so you can use it for cross compilation on
macOS for Linux, but you can't use mold for macOS native development.
- Relocation overflow are now reported as errors on AArch64 and
i386. Previously, such relocations were silently producing incorrect
output.
Highlights of mold 0.9.4:
- mold -run now intercepts invocations of ld, ld.lld and ld.gold wherever
they are in the directory hierarchy. Previously, they were intercepted
only if they were in /usr/bin. This change was made because it is not
uncommon to install a compiler toolchain into a directory other than
the system bin directory.
- AArch64 (Arm 64-bit) support has been significantly improved. mold
can now link many real-world programs including itself for AArch64.
- Fix an issue that relocation addends were not handled correctly
for i386.
- mold is now able to link LLVM compiler-rt's CRT files.
- Fix an issue that a dynamic relocation was created for a read-only
section if the relocation refers an unresolved weak symbol.
- Undefined weak symbols are now always resolved to address 0 instead
of being promoted to dynamic symbols.
|
|
Upstream changes (from github logs):
1.1.0
- ruby 3.0 support
- rubocop
- drop ruby 2.5 support
1.0.3
- accept addressable <3.0
- circleci
|
|
8.9.0
-----
* New functions
* :func:`interleave_evenly` (thanks to mbugert)
* :func:`repeat_each` (thanks to FinalSh4re)
* :func:`chunked_even` (thanks to valtron)
* :func:`map_if` (thanks to sassbalint)
* :func:`zip_broadcast` (thanks to kalekundert)
* Changes to existing functions
* The type stub for :func:`chunked` was improved (thanks to PhilMacKay)
* The type stubs for :func:`zip_equal` and `zip_offset` were improved (thanks to maffoo)
* Building Sphinx docs locally was improved (thanks to MarcinKonowalczyk)
|
|
Version 1.6.2
-------------
No functionality changes with respect to 1.6.1
* Added `python_requires>=3.5` to `setup.py`
* Formatted the codebase with `black`
* Added type annotations
* Added CI checks for typing, security and linting
|
|
**3.3.1**
- Added missing documentation for the ``ExceptionGroup.exceptions`` attribute
- Changed the asyncio test runner not to use uvloop by default (to match the behavior of
``anyio.run()``)
- Fixed ``RuntimeError`` on asyncio when a ``CancelledError`` is raised from a task spawned through
a ``BlockingPortal``
- Fixed asyncio warning about a ``Future`` with an exception that was never retrieved which
happened when a socket was already written to but the peer abruptly closed the connection
|
|
Release 0.10.9
Fixed
- Fix flexmock not mocking methods properly on derived classes.
Release 0.10.8
Fixed
- Fix ``with_args`` not working built-in functions.
Release 0.10.7
Fixed
- Fix ``with_args`` not working built-in methods.
- Fix previous pytest ``--durations`` fix not working.
Release 0.10.6
Fixed
- Fix flexmock broken with Pytest 4 & 5.
- Fix new_instances method not working with Python 2.7.
- Fix multiple expectations for the same classmethod are not matched.
|
|
|
|
version 3.1.9
---------------------------------------
(version 3.1.8 was pulled due to serious issues)
Another maintenance release.
* Fixed a couple of outdated results in the readme (Issue 214).
* Some more documentation tidying.
* Turned off some debug code by default.
* Fixed a couple of failing tests in different Python versions.
* Fix for consistent pos initialisation semantics for different types.
* Change to allow wheels to be uploaded to PyPI.
* More work for LSB0 mode, but still not finished or documented (sorry).
|
|
|
|
# waldo 0.3.0
* `compare()` is now considerably faster when comparing complex objects that
don't have any differences (thanks to strategic use of `identical()`) (#86).
* `compare()` gains two improvements to low-level diffs:
* Structurally identical data frames (#78) and numeric matrices (#76) gain
a row-by-row diff that makes it easier to see where exactly values differ.
* An element-by-element diff will be automatically used if it's shorter than
the "smart" diff. This improves diff quality when comparing two vectors
that aren't really related (#68).
* `compare()` gains a `list_as_map` argument thanks to an idea from @dmurdoch.
It allows you to compare the behaviour of two lists when they are used to
connect names to values (i.e. the list is operating as a map or dictionary).
It removes `NULL`s and sorts named components (#72).
* The objects involved in `compare()` (as opposed to the caller of `compare()`)
gained much greater ability to control the comparison.
* Objects can now contain a `waldo_opts` attribute, a list with the same
names and valid values as the arguments to `compare()`, which overrides
the default comparisons (@dmurdoch).
* `compare_proxy()` is now called earlier (before type comparison) making
it more flexible (#65).
* `compare_proxy()` gains a second argument, `path`, used to report how the
proxy changed the object. This makes it easier to see when and how a proxy
is used (#73).
* Proxies now exist for comparing RProtoBuf objects, converting them to
proto text format (#82, @michaelquinn32).
* Comparing a list with symbol to a list without that element no longer errors
(@mgirlich, #79).
|
|
|
|
|
|
pytest 6.2.5
Python 3.10 is now supported.
Enable compatibility with ``pluggy 1.0`` or later.
|
|
- Bugfix release.
(Looks like an extraneous debug statement was removed, and that's it.)
|
|
Upstream changes:
2.05 2021-07-03 NEILB
- Include META.json in releases
- Switch to github issues for bug tracker
- Simplified the README some more
2.04 2021-05-19 NEILB
- Made all mentions of licence consistent with the statement
in the documentation. RT#132447 from KENTNL.
|
|
Upstream changes:
Changes for version 0.334 - 2021-06-18
add a perl-support block to docs
update author contact info
|
|
Upstream changes:
1.012004 2021-07-29
[ Documentation ]
- Fixed typo in Types::Standard documentation where StrMatch regexp
parameter didn't use qr// properly.
Lucas Tiago de Moraes++
|
|
Changes:
- Documentation: release notes for NSS 3.70.
- Documentation: release notes for NSS 3.69.1.
- Bug 1726022 - Update test case to verify fix.
- Bug 1714579 - Explicitly disable downgrade check in TlsConnectStreamTls13.EchOuterWith12Max
- Bug 1714579 - Explicitly disable downgrade check in TlsConnectTest.DisableFalseStartOnFallback
- Formatting for lib/util
- Bug 1681975 - Avoid using a lookup table in nssb64d.
- Bug 1724629 - Use HW accelerated SHA2 on AArch64 Big Endian.
- Bug 1714579 - Change default value of enableHelloDowngradeCheck to true.
- Formatting for gtests/pk11_gtest/pk11_hpke_unittest.cc
- Bug 1726022 - Cache additional PBE entries.
- Bug 1709750 - Read HPKE vectors from official JSON.
- Documentation: update for NSS 3.69 release.
|
|
Bug Fixes:
-Pin the cargo-chef version in Dockerfile
Documentation:
-Update docker commands to only mount the .git directory
Miscellaneous Tasks:
-Bump git-conventional to 0.10.1 (fixes #6)
-Bump dependencies
-Bump cargo-chef version in Dockerfile
|
|
|
|
New in 2021.08
Core:
+ [2f5c21fb] Fix another bug in `MVM_str_hash_fsck`
+ [7355f744] Free filename if exception when loading bytecode
+ [8cc7fbdf,7907b85b,0c032a00,a81f129a,7f8bc1e7] Switch `MVM_coerce_n_s`
to Ryū from Grisu3 with a `sprintf` fallback
JIT:
+ [2932ef5b] Add JIT templates for `(bind|get)attr(s)?_*`
Spesh:
+ [d4a8093e] Fix deadlock by untimely GC in multi-threaded programs
+ [a932b173] Fix spesh optimizing away still needed label register
|
|
This package contains py.test plugin that allows you to add
environment variables.
It is needed for running gdal tests, and despite being released in
2017, I heard from gdal-dev@ that it is merely tiny rather than
unmaintained.
|
|
0.14.2
Java
THRIFT-5383 - THRIFT-5383 TJSONProtocol Java readString throws on bounds check
Go
THRIFT-5369 - TConfiguration.GetMaxMessageSize() now also applies to container sizes in TProtocol implementations provided
|
|
- Allow to override the text in the notification and the voice via
environment variables `MOB_NOTIFY_MESSAGE` and `MOB_VOICE_MESSAGE`.
- Allow to override the stash name used for stashing uncommitted changes
via the environment variable `MOB_STASH_NAME`.
- Allow to override the cli name of the tool via `MOB_CLI_NAME` so you
can use `pair`, `ensemble`, `team`, or whatever you like best, instead
of `mob`. Just install the `mob` tool, set an alias in your cli and
set the environment variable `MOB_CLI_NAME` to the name of your alias.
|
|
|
|
Traitlets 5.1
-------------
Traitlets 5.1 brings a couple of updates and changes to traitlets, and is
recommended for all users. What follow is a non-exhaustive list of changes:
- Removal of the ``ipython_genutils`` dependency, this should remove any direct
and indirect reliance on ``nose`` and prepare traitlets 5.1 for Python 3.10
and above compatibility, some test suite changes also accommodate Python 3.10 changes.
If you package traitlets downstream, make sure to remove this dependency.
- Removal of ``ipython_genutils`` may have change the default encoding detected
for the command line argument parsing when not utf-8. We expect this to
affect a small portion of older windows version. If you encounter issue let
us know.
- Stop recommendation of ``CUnicode`` in some circumstances as it's
deprecated.
- Our test suite is now using GitHub action instead of travis CI. If you are
packaging downstream using the git repository, you may have to exclude the
``.github`` folder now, and can remove exclusion of
- It fixes a parsing issue for list of one single element on the CLI.
- We reserve the right to remove official support for Python 3.7 in subsequent
minor revisions.
|
|
3.10.0.2:
Unknown changes
|
|
this is still wrong, but it's less wrong than before and once again
both arm64 and arm64eb (and amd64) build.
this is really strange. the code in sha512.c uses:
#if !defined(USE_HW_SHA2) || !defined(IS_LITTLE_ENDIAN)
which originally this patch attempted to match, but IS_LITTLE_ENDIAN
is never defined inside nss, even though it's used a few dozen times.
there is a MP_IS_LITTLE_ENDIAN defined that is setup, but almost
never used.
|
|
|
|
Allow depending to ruby-addressable>=2.8.0.
Bump PKGREVISION.
|
|
0.2.7
Wrap finalizer in class method.
Otherwise, the finalizer holds a reference to the object to be finalized, so
it can never run.
|
|
2.0.1 (2021-08-29)
* Exclude bin/* files from the gem package.
* Fix the attribute tests to work with Ruby that allows attribute methods to
be traced.
|
|
2.1.0 (2021-08-27)
* Remove taint checking https://github.com/grosser/fast_gettext/pull/133
|
|
* Drop Redmine 4.0 support.
* Switch default version of Redmine to 4.2.x.
|
|
Redmine 4.0.9 was last release of Redmine 4.0 seriese. No more fixes
including security problem and there are security release for 4.1/4.2
but not for 4.0.
Discussing with MAINTAINER, we decide to remove ruby-redmine package.
Please migrate to ruby-redmine41 or ruby-redmine42.
|
|
|
|
|
|
Bugs fixed:
- Bug 1722613 (Backout) - Disable DTLS 1.0 and 1.1 by default
- Bug 1720226 (Backout) - integrity checks in key4.db not happening on private components with AES_CBC
|
|
|
|
This is a bugfix release. The most notable changes are: compatibility
with Mercurial 5.9, and a bug that could lead to data loss when using
evolve commands on a merge commit was fixed.
|
|
== New Features ==
* `hg config` now has a `--source` option to show where each
configuration value comes from.
== Internal API Changes ==
The Dirstate API have been updated as the previous function leaked some
internal details and did not distinct between two important cases: "We are
changing parent and need to adjust the dirstate" and "some command is changing
which file is tracked". To clarify the situation:
* the following functions have been deprecated,
- dirstate.add,
- dirstate.normal,
- dirstate.normallookup,
- dirstate.merge,
- dirstate.otherparent,
- dirstate.remove,
- dirstate.drop,
* these new functions are added for the "adjusting parents" use-case:
- dirstate.update_file,
- dirstate.update_file_p1,
* these new function are added for the "adjusting wc file" use-case":
- dirstate.set_tracked,
- dirstate.set_untracked,
- dirstate.set_clean,
- dirstate.set_possibly_dirty,
See inline documentation of the new functions for details.
|
|
6.0.0 (2021-07-09)
Changed
* Updated cucumber-core ~> 10.0.0 and cucumber-messages ~> 17.0.0 This
brings breaking changes because of internal changes in
Cucumber::Messages. (#44)
6.0.1 (2021-07-19)
Changed
* Patched cucumber-core and cucumber-messages
6.1.0 (2021-08-09)
Added
* The possibility to verify if the plugin has already been installed or
not. To do so, use Cucumber::Wire::Plugin.installed?. (46)
Changed
* cucumber-wire is now able to install itself as a plugin into
cucumber-ruby. (46)
6.1.1 (2021-08-27)
Changed
* Use the new InstallPlugin hook rather than AfterConfiguration. (#52)
|
|
10.0.1 (2021-07-19)
* Patched cucumber-gherkin and cucumber-messages
10.0.0 (2021-07-09)
Dependencies
* Upgraded to gherkin v20 and messages v17.
This removes protocol buffers from the runtime dependencies.
This deeply impacts the API as the internal representation of messages has
changed from Protocol Buffer objects to new auto-generated DTOs.
|
|
17.0.0 (2021-07-08)
Added
* Added Ci#buildNumber field (#1632 #1606 aslakhellesoy)
* [Ruby] Generate DTOs from the json schemas to avoid usage of plain ruby
hashes (#1574 #1605)
Changed
* BREAKING Move willBeRetried field from TestStepResult to TestCaseFinished
(#902 #1631)
|
|
12.1.2 (2021-08-17)
* Relax semver for @cucumber/* libs, fix ruby update warnings
* use new berp for all platforms
* Use canned berp recipes for all platforms
* make grammar file location configurable
|
|
macholib 1.15.1
* Remove a debug print introduced in the previous release.
|
|
- smake: While expanding the right side of a macro assignment with.
the operators :::= and +:=, smake no longer expands $$ to $, but
rather leaves $$ untouched.
This is based on a concept change from BSD make for the := operator
in BSD make that was introduced in 2016 by the BSD people. It has.
been recently decided by POSIX to be a mandatory behavior, as this
avoids the need to know the expansion nesting level for $$ while
using immediate expansion assignments.
In former times this could lead to a need for $$$$$$$$$$$$$ constructs
as every nesting level in an immediate expansion assignment did
"expand" every $$ to $.
It turns out that the change in BSD make to no longer expand $$
for immediate expand assignments was the best solution for dealing
with the problems with immediate expansion assignments. This is
why both smake and SunPro Make integrated a similar change.
In former times, the problem with $$ expansion was no problem since
he $$ usage in makefiles was extremely rare. Today, more people
are using $(cmd) shell constructs in makefiles instead of `cmd`
and as a result, $$ usage has become more frequent in makefiles
because of the need to use $$(cmd) in make rule commands in such
a case.
- smake: The dynamic macros $? and $^ now work for implicit rules
as well. For $?, this is required by POSIX and was required by POSIX
for a longe time, but in former times, the same but wrong requirement
did exist for $* and $< as well. It therefore was unclear whether the
requirement for $? in the POSIX standard was a similar mistake.
In March 2021 we agreed on a POSIX teleconference call that $? should
be expanded for implicit rules as well. It had been forgotten to
implement that change to smake in time. This has now be catched up.
- smake: is now version 1.6
|
