These releases fix a security flaw (CVE-2018-17456), which allowed an
attacker to execute arbitrary code by crafting a malicious .gitmodules
file in a project cloned with --recurse-submodules.
When running "git clone --recurse-submodules", Git parses the supplied
.gitmodules file for a URL field and blindly passes it as an argument
to a "git clone" subprocess. If the URL field is set to a string that
begins with a dash, this "git clone" subprocess interprets the URL as
an option. This can lead to executing an arbitrary script shipped in
the superproject as the user who ran "git clone".
In addition to fixing the security issue for the user running "clone",
the 2.17.2, 2.18.1 and 2.19.1 releases have an "fsck" check which can
be used to detect such malicious repository content when fetching or
accepting a push. See "transfer.fsckObjects" in git-config(1).
Credit for finding and fixing this vulnerability goes to joernchen
and Jeff King, respectively.
Changes in 3.12.3 since 3.12.2:
* CTest: Fix --test-load regression
* FindMPI: Restore MPI__COMPILE_FLAGS as a command-line string
* FindDoxygen: Ensure policy settings allow use of IN_LIST
* libarchive: Backport fix for build with LibreSSL 2.7
* libuv: do not require PATH_MAX to be defined
* VS: Fix CSharp flag selection when linking to a static C++ library
* CSharp: Fix regression in VS project type selection
* CTest: Fix regression in ctest_start()
* Help: TESTS property: clarify usage.
Version 2.2.2 - September, 2018
-------------------------------
- Fixed bug in SkipTo, if a SkipTo expression that was skipping to
an expression that returned a list (such as an And), and the
SkipTo was saved as a named result, the named result could be
saved as a ParseResults - should always be saved as a string.
Issue 28, reported by seron.
- Added simple_unit_tests.py, as a collection of easy-to-follow unit
tests for various classes and features of the pyparsing library.
Primary intent is more to be instructional than actually rigorous
testing. Complex tests can still be added in the unitTests.py file.
- New features added to the Regex class:
- optional asGroupList parameter, returns all the capture groups as
a list
- optional asMatch parameter, returns the raw re.match result
- new sub(repl) method, which adds a parse action calling
re.sub(pattern, repl, parsed_result). Simplifies creating
Regex expressions to be used with transformString. Like re.sub,
repl may be an ordinary string (similar to using pyparsing's
replaceWith), or may contain references to capture groups by group
number, or may be a callable that takes an re match group and
returns a string.
For instance:
expr = pp.Regex(r"([Hh]\d):\s*(.*)").sub(r"<\1>\2</\1>")
expr.transformString("h1: This is the title")
will return
<h1>This is the title</h1>
- Fixed omission of LICENSE file in source tarball, also added
CODE_OF_CONDUCT.md per GitHub community standards.
Version 2.2.1 - September, 2018
-------------------------------
- Applied changes necessary to migrate hosting of pyparsing source
over to GitHub. Many thanks for help and contributions from hugovk,
jdufresne, and cngkaygusuz among others through this transition,
sorry it took me so long!
- Fixed import of collections.abc to address DeprecationWarnings
in Python 3.7.
- Updated oc.py example to support function calls in arithmetic
expressions; fixed regex for '==' operator; and added packrat
parsing. Raised on the pyparsing wiki by Boris Marin, thanks!
- Fixed bug in select_parser.py example, group_by_terms was not
reported. Reported on SF bugs by Adam Groszer, thanks Adam!
- Added "Getting Started" section to the module docstring, to
guide new users to the most common starting points in pyparsing's
API.
- Fixed bug in Literal and Keyword classes, which erroneously
raised IndexError instead of ParseException.
0.32.0:
Removed wheel signing and verifying features
Removed the "wheel install" and "wheel installscripts" commands
Added the wheel pack command
Allowed multiple license files to be specified using the license_files option
Deprecated the license_file option
Eliminated duplicate lines from generated requirements in .dist-info/METADATA
Fixed handling of direct URL specifiers in requirements
Fixed canonicalization of extras
Warn when the deprecated [wheel] section is used in setup.cfg
Version 7.0:
Drop support for Python 2.6 and 3.3.
Wrap click.Choice's missing message.
Add native ZSH autocompletion support.
Document that ANSI color info isn't parsed from bytearrays in Python 2.
Document byte-stripping behavior of CliRunner.
Usage errors now hint at the --help option.
Implement streaming pager.
Extract bar formatting to its own method.
Add DateTime type for converting input in given date time formats.
secho's first argument can now be None, like in echo.
Fixes a ZeroDivisionError in ProgressBar.make_step, when the arg passed to the first call of ProgressBar.update is 0.
Show progressbar only if total execution time is visible.
Added the ability to hide commands and options from help.
Document that options can be required=True.
Non-standalone calls to Context.exit return the exit code, rather than calling sys.exit.
click.getchar() returns Unicode in Python 3 on Windows, consistent with other platforms.
Added FloatRange type.
Added support for bash completion of type=click.Choice for Options and Arguments.
Only allow one positional arg for Argument parameter declaration.
Add case_sensitive=False as an option to Choice.
click.getchar() correctly raises KeyboardInterrupt on "^C" and EOFError on "^D" on Linux.
Fix encoding issue with click.getchar(echo=True) on Linux.
param_hint in errors now derived from param itself.
Add a test that ensures that when an argument is formatted into a usage error, its metavar is used, not its name.
Allow setting prog_name as extra in CliRunner.invoke.
Help text taken from docstrings truncates at the \f form feed character, useful for hiding Sphinx-style parameter documentation.
launch now works properly under Cygwin.
Update progress after iteration.
CliRunner.invoke now may receive args as a string representing a Unix shell command.
Make Argument.make_metavar() default to type metavar.
Add documentation for ignore_unknown_options.
Add bright colors support for click.style and fix the reset option for parameters fg and bg.
Add show_envvar for showing environment variables in help.
Avoid BrokenPipeError during interpreter shutdown when stdout or stderr is a closed pipe.
Document customizing option names.
Disable sys._getframes() on Python interpreters that don't support it.
Fix bug in test runner when calling sys.exit with None.
Clarify documentation on command line options.
Fix crash on Windows console.
Fix bug that caused bash completion to give improper completions on chained commands.
Added support for dynamic bash completion from a user-supplied callback.
Added support for bash completions containing spaces.
Allow autocompletion function to determine whether or not to return completions that start with the incomplete argument.
Fix option naming routine to match documentation and be deterministic.
Fix path validation bug.
Add test and documentation for Option naming: functionality.
Update doc to match arg name for path_type.
Raw strings added so correct escaping occurs.
Fix 16k character limit of click.echo on Windows.
Overcome 64k character limit when writing to binary stream on Windows 7.
Add bool conversion for "t" and "f".
NoSuchOption errors take ctx so that --help hint gets printed in error output.
Fixed the behavior of Click error messages with regards to Unicode on 2.x and 3.x. Message is now always Unicode and the str and Unicode special methods work as you expect on that platform.
Progress bar now uses stderr by default.
Add support for auto-completion documentation.
Allow CliRunner to separate stdout and stderr.
Fix variable precedence.
Fix invalid escape sequences.
Fix ResourceWarning that occurs during some tests.
When detecting a misconfigured locale, don't fail if the locale command fails.
Add case_sensitive=False as an option to Choice types.
Force stdout/stderr writable. This works around issues with badly patched standard streams like those from Jupyter.
Fix completion of subcommand options after last argument
_AtomicFile now uses the realpath of the original filename so that changing the working directory does not affect it.
Fix incorrect completions when defaults are present
Add copy option attrs so that custom classes can be re-used.
"x" and "a" file modes now use stdout when file is "-".
Fix missing comma in __all__ list.
Clarify how parameters are named.
Stdout is now automatically set to non blocking.
Do not set options twice.
Move fcntl import.
Fix Google App Engine ImportError.
Better handling of help text for dynamic default option values.
Fix get_winter_size() so it correctly returns (0,0).
Add test case checking for custom param type.
Allow short width to address cmd formatting.
Add details about Python version support.
Added deprecation flag to commands.
Fixed issues where fd was undefined.
Fix formatting for short help.
Document how auto_envvar_prefix works with command groups.
Don't add newlines by default for progress bars.
Use Python sorting order for ZSH completions.
Document that parameter names are converted to lowercase by default.
Subcommands that are named by the function now automatically have the underscore replaced with a dash. If you register a function named my_command it becomes my-command in the command line interface.
Hide hidden commands and options from completion.
Fix absolute import blocking Click from being vendored into a project on Windows.
Fix issue where a lowercase auto_envvar_prefix would not be converted to uppercase.
pytest 3.8.2:
Deprecations and Removals
* The item parameter of pytest_warning_captured hook is now documented as deprecated. We realized only after the 3.8 release that this parameter is incompatible with pytest-xdist.
Our policy is to not deprecate features during bugfix releases, but in this case we believe it makes sense as we are only documenting it as deprecated, without issuing warnings which might potentially break test suites. This will get the word out that hook implementers should not use this parameter at all.
In a future release item will always be None and will emit a proper warning when a hook implementation makes use of it.
Bug Fixes
* Fix reload on assertion rewritten modules.
* The .user_properties attribute of TestReport objects is a list of (name, value) tuples, but could sometimes be instantiated as a tuple of tuples. It is now always a list.
* No longer issue warnings about using pytest_plugins in non-top-level directories when using --pyargs: the current --pyargs mechanism is not reliable and might give false negatives.
* Exclude empty reports for passed tests when -rP option is used.
* Improve error message when an invalid Python expression is passed to the -m option.
* MonkeyPatch.setenv and MonkeyPatch.delenv issue a warning if the environment variable name is not str on Python 2.
In Python 2, adding unicode keys to os.environ causes problems with subprocess (and possible other modules), making this a subtle bug specially susceptible when used with from __future__ import unicode_literals.
Improved Documentation
* Add possible values for fixture scope to docs.
3.74.0:
This release checks that the value of the :attr:~hypothesis.settings.print_blob setting is a :class:~hypothesis.PrintSettings instance.
Being able to specify a boolean value was not intended, and is now deprecated. In addition, specifying True will now cause the blob to always be printed, instead of causing it to be suppressed.
Specifying any value that is not a :class:~hypothesis.PrintSettings or a boolean is now an error.
3.73.5:
Changes the documentation for hypothesis.strategies.datetimes, hypothesis.strategies.dates, hypothesis.strategies.times to use the new parameter names min_value and max_value instead of the deprecated names
3.73.4:
This patch ensures that Hypothesis deprecation warnings display the code that emitted them when you're not running in -Werror mode (:issue:652).
3.73.3:
Tracebacks involving :func:@composite <hypothesis.strategies.composite> are now slightly shorter due to some internal refactoring.
3.73.2:
This patch fixes errors in the internal comments for one of the shrinker passes. There is no user-visible change.
3.73.1:
This patch substantially improves the distribution of data generated with :func:~hypothesis.strategies.recursive, and fixes a rare internal error (:issue:1502).
3.73.0:
This release adds the :func:~hypothesis.extra.dpcontracts.fulfill function, which is designed for testing code that uses :pypi:dpcontracts 0.4 or later for input validation. This provides some syntactic sugar around use of :func:~hypothesis.assume, to automatically filter out and retry calls that cause a precondition check to fail (:issue:1474).
3.72.0:
This release makes setting attributes of the :class:hypothesis.settings class an explicit error. This has never had any effect, but could mislead users who confused it with the current settings instance hypothesis.settings.default (which is also immutable). You can change the global settings with :ref:settings profiles <settings_profiles>.
3.71.11:
This patch factors out some common code in the shrinker for iterating over pairs of data blocks. There should be no user-visible change.
pytest-xdist 1.23.2:
Bug Fixes
- Fix issue where Warnings could cause pytest to fail if they do not set the args attribute correctly.
pytest-xdist 1.23.1:
Bug Fixes
- Fix warnings transfer between workers and master node with pytest >= 3.8.py-test-xdist: updated to 1.23.2
Changelog:
Release Notes for Elftoolchain Software Version 0.7.1
=====================================================
About The Project
-----------------
The `Elftoolchain project`_ develops BSD-licensed implementations of
essential compilation tools and libraries for handling ELF based program
objects.
About The Release
-----------------
This is the first release on the v0.7 "stable" code line.
Since the prior v0.6.1 release, we have added support for a few more
machine architectures, improved our support of the DWARF4 debug format,
and have added experimental support for the Microsoft (TM) Portable
Executable format. A number of bugs have been fixed, and the project's
documentation has been improved. An implementation of a link editor
**ld** is in progress.
Libraries and Utilities
~~~~~~~~~~~~~~~~~~~~~~~
This release comprises the following libraries and utilities.
================= ==========================================
**Name** **Description**
================= ==========================================
**ar** Archive manager.
**addr2line** Debug tool.
**brandelf** Manage the ELF brand on executables.
**c++filt** Translate encoded symbols.
**elfcopy** Copy and translate between object formats.
**elfdump** Diagnostic tool.
**findtextrel** Find undesired text relocations.
**libdwarf** DWARF access library.
**libelf** ELF access library.
**mcs** Manage comment sections.
**nm** List symbols in an ELF object.
**ranlib** Add archive symbol tables to an archive.
**readelf** Display ELF information.
**size** List object sizes.
**strings** Extract printable strings.
**strip** Discard information from ELF objects.
================= ==========================================
This release also contains the following software that is under
development:
================= ==========================================
**Name** **Description**
================= ==========================================
**ld** Program linker.
**libpe** PE (Portable Executable) access library.
================= ==========================================
Documentation
~~~~~~~~~~~~~
Each public API and invocable utility has a reference manual entry.
We currently offer 355 manual entries, documented in 197 manual pages.
Additionally, this release contains the following documentation:
================= ==========================================
**Name** **Description**
================= ==========================================
libelf-by-example A tutorial introduction to **libelf**.
================= ==========================================
Test Suites
~~~~~~~~~~~
The release contains the following test suites:
================= ==========================================
**Name** **Description**
================= ==========================================
ar Test the **ar** utility.
elfcopy Test the **elfcopy** utility.
elfdump Test the **elfdump** utility.
libdwarf Test the **libdwarf** library.
libelf Test the **libelf** library.
libelftc Test the **libelftc** support library.
nm Test the **nm** utility.
================= ==========================================
System Requirements
-------------------
This software is designed to run on Unix(TM)-like operating systems
such as the BSD-family of operating systems and GNU/Linux.
This release has been built and tested on the following operating
systems:
==================== =========== ===========================
**Operating System** **Version** **Supported Architectures**
-------------------- ----------- ---------------------------
FreeBSD_ 10.2 amd64 & i386
NetBSD_ 7.0 i386
Ubuntu_ GNU/Linux 14.04LTS x86_64
==================== =========== ===========================
Installation and Upgrades
=========================
Installation
------------
Instructions for building and installing this software from source are
described in the file "INSTALL".
Upgrading
---------
* Consumers of the libdwarf API should note that the `Dwarf_Off` type
has changed to an unsigned type, so as to be compatible with other
open-source libdwarf implementations.
* Three functions in the libdwarf API have been deprecated and two
extension APIs have been added.
Release Information
===================
Changes in this release
-----------------------
Significant changes include:
* **addr2line**
- Support the ``DW_AT_ranges`` debug attribute.
- Improve DWARF4 compatibility.
- **addr2line** supports new options ``-a``, ``-i``, ``-p``.
- Compilation units lacking debug information are handled more robustly.
- Memory leaks were fixed.
* **ar/ranlib**
- The **ranlib** utility is now documented in its own manual page.
- The handling of corrupt archives has been improved.
- **ar** now supports a ``-U`` option that disables its
deterministic (``-D``) mode.
- **ar** no longer allows extraction of archive entries whose
pathnames contain ``..``, or whose target directory would be
altered by a symbolic link.
* **brandelf**
- The documentation for **brandelf** has been improved.
* **elfcopy/strip/mcs**
- **strip** no longer strips local debugging symbols when the ``-x``
option is specified.
- Compatibility with GNU binutils has been improved.
- The **elfcopy** and **strip** utilities will now preserve hard
links when modifying an object file.
- Support for new functionality controlled by options
``--localize-hidden``, ``--extract-dwo`` and ``--strip-dwo`` has
been added.
- Bugs in the behavior of the ``-N`` and ``-X`` options were fixed.
- Nameless global symbols are now handled correctly.
- ``SHT_GROUP`` handling has been fixed in **elfcopy** and
**strip**.
- **elfcopy** now supports the conversion of ELF objects to PE images.
* **elfdump**
- **elfdump** can now dump multiple GOT sections.
- **elfdump** now understands the ``EM_AARCH64``, ``EM_IAMCU``,
``EM_PPC64``, and ``EM_RISCV`` machine types and the
``STT_SPARC_REGISTER`` section type.
- Symbols with ``STB_GNU_UNIQUE`` are now supported.
* **findtextrel**
- The manual pages were improved.
* **ld**
- This utility is new in this release. This utility is currently under
development, and should be considered unstable.
* **libdwarf**
- The line number program generated by **libdwarf** has been improved.
- Support for the DWARF4 ``.debug_types`` section was added.
- Parsing of DWARF4 line sections was fixed.
- New APIs ``dwarf_attroffset()``,
``dwarf_get_cu_die_offset_given_cu_header_offset_b()``,
``dwarf_get_die_infotypes_flag()``,
``dwarf_get_section_max_offsets()``,
``dwarf_get_section_max_offsets_b()``, ``dwarf_highpc_b()``,
``dwarf_loclist_from_expr_b()``, ``dwarf_next_types_section()``,
``dwarf_offdie_b()``, and ``dwarf_siblingof_b()`` have been added.
Of these, ``dwarf_attroffset()`` and ``dwarf_next_types_section()``
are extensions to the SGI libdwarf API.
- Support for operators ``DW_OP_GNU_addr_index``,
``DW_OP_GNU_const_index``, ``DW_OP_GNU_const_type``,
``DW_OP_GNU_convert``, ``DW_OP_GNU_deref_type``,
``DW_OP_GNU_encoded_addr``, ``DW_OP_GNU_entry_value``,
``DW_OP_GNU_implicit_pointer``, ``DW_OP_GNU_parameter_ref``,
``DW_OP_GNU_regval_type``, ``DW_OP_GNU_reinterpret``,
``DW_OP_GNU_uninit`` and ``DW_OP_push_object_address`` have been
added.
- APIs ``dwarf_get_cu_die_offset_given_cu_header_offset()``,
``dwarf_offdie()``, ``dwarf_siblingof()`` have been deprecated.
- **libdwarf** now supports relocation for the ``aarch64``
architecture.
- **libdwarf** now handles architectures that use ".rel" relocations
for debug data correctly.
- The ``EM_IAMCU`` architecture is now recognized.
- Documentation has been improved, memory leaks and other bugs have
been fixed.
* **libelf**
- Reference documentation has been improved.
- Support building on the AARCH64 architecture has added.
- Bug fixes have been applied.
* **libelf-by-example**
- No changes since the prior release.
* **libelftc**
- Support for the Portable Executable format has been added.
- Overview documentation for this support library has been added.
- New APIs ``elftc_string_table_from_section()``.
``elftc_string_table_image()``, ``elftc_string_table_insert()``,
``elftc_string_table_lookup()``, ``elftc_string_table_remove()``
and ``elftc_string_table_to_string()`` have been added.
- The demangling support functions now support IEEE floating point
types, TLS special names and various GNU extensions.
- Other bugs have fixed.
* **libpe**
- This library is new in this release. This library is currently
under development, and should be considered unstable.
* **nm**
- A new alias ``--extern-only`` for option ``-g`` is now supported.
- Bugs have been fixed.
* **readelf**
- The handling of objects with missing symbol names was improved.
- **readelf** now supports dumping ``.debug_types`` sections.
- The ``DW_AT_language``, ``DW_FORM_exprloc``,
``DW_FORM_flag_present``, ``DW_FORM_ref_sig8`` and
``DW_FORM_sec_offset`` types are now supported.
- GNU DWARF operator extensions are now recognized by **readelf**.
- **readelf** can now display architecture specific register names on
some architectures.
- **readelf** now handles AArch64 types and relocations and
recognizes the ``RISC-V`` and ``IAMCU`` architectures.
- Support has been added for printing binary notes for FreeBSD, Xen
and Linux, and for printing core notes for FreeBSD and Linux.
- Support for dumping symbols with the ``STB_GNU_UNIQUE`` binding
has been added.
- Support for dumping symbols with the ``STT_SPARC_REGISTER``
register type has been added.
* **size**
- The manual page for **size** has been improved.
* **strings**
- The manual page for **strings** has been improved.
Outstanding Issues
------------------
There were no outstanding issues at the time of the release.
Known Limitations
-----------------
This release has the following limitations:
:Test coverage:
Our test suites are being developed; test coverage is still
partial.
:Performance and Memory Use:
Our tools have not been fully analyzed for their memory use or for
their performance characteristics.
Test Statistics
---------------
The test summary for this release is presented below:
========= ========== =============== ================ ===================
**Suite** **Tests** **FreeBSD** **NetBSD** **Ubuntu 10.04LTS**
(32&64bit) (i386 & amd64) (i386) (x86_64)
========= ========== =============== ================ ===================
ar 235 & 230 P:235 & 230 P:235 P:230
elfcopy 160 P:160 P:160 P:160
elfdump 155 P:155 P:155 P:155
libdwarf 153 P:153 P:153 P:153
libelf 1030 P:1026, U:4 P:1026, U:4 P:1026, U:4
libelftc 16 P:16 P:16 P:16
nm 183 P:183 P:183 P:183
========= ========== =============== ================ ===================
Key:
:P:
Test successes.
:F:
Test failures.
:U:
Unresolved tests.
Notes
~~~~~
More Information
================
The project's website is at http://elftoolchain.sourceforge.net/.
Developer Community
-------------------
The project's developers may be contacted using the mailing list:
``<elftoolchain-developers@lists.sourceforge.net>``.
Reporting Bugs
--------------
Please use our `bug tracker`_ for viewing existing bug reports and
for submitting new bug reports.
Copyright and License
=====================
This software is copyright its authors, and is distributed under the
`BSD License`_.
.. _BSD License: http://www.opensource.org/licenses/bsd-license.php
.. _`bug tracker`: https://sourceforge.net/p/elftoolchain/tickets/
.. _Elftoolchain project: http://elftoolchain.sourceforge.net/
.. _FreeBSD: http://www.freebsd.org/
.. _NetBSD: http://www.netbsd.org/
.. _Ubuntu: http://www.ubuntu.com/
.. Local Variables:
.. mode: rst
.. End:
SQLite Release 3.25.2:
Add the PRAGMA legacy_alter_table=ON command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME.
Fix a problem with the new window functions implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view.
Fixes for various other compiler warnings and minor problems associated with obscure configurations.
- Fix slightly incorrect generation of default .gitignore file.
- Make cvsreduce work under Python 3, and test for that.
- Revert <2014-11-19T18:11:22Z@flower.powernet.co.uk>, optimization was wrong.
- Fix a typo in a property name that affects interoperability with reposurgeon.
- Savannah changed how you need to interpret pseudo-URLs.
Version 2.19:
- Fix parsing of floating point literals
- Add support for parsing empty structs
- Fix enum formatting in generated C code
- Add support for #pragma in struct declarations
v0.46:
OleFileIO can now be used as a context manager (with...as), to close the file automatically
Improved handling of malformed files, fixed several bugs.
0.5.9:
- Fixed file system error handling.
0.5.8:
- Improved type checking.
- Created scripts to test Python 2.6 because Tox removed support for it.
- Improved byte string handling in Python 3.
- Handle dangling symlinks.
pytest 3.8.1:
Bug Fixes
* .pytest_cache directory is now automatically ignored by Git. Users who would like to contribute a solution for other SCMs please consult/comment on this issue.
* Fix the following error during collection of tests inside packages:
TypeError: object of type 'Package' has no len()
* Fix bug where indirect parametrization would consider the scope of all fixtures used by the test function to determine the parametrization scope, and not only the scope of the fixtures being parametrized.
* Fix crash of the assertion rewriter if a test changed the current working directory without restoring it afterwards.
* Fix issue that prevented some caplog properties (for example record_tuples) from being available when entering the debugger with --pdb.
* Fix UnicodeDecodeError in python2.x when a class returns a non-ascii binary __repr__ in an assertion which also contains non-ascii text.
Improved Documentation
* New Deprecations and Removals page shows all currently deprecated features, the rationale to do so, and alternatives to update your code. It also list features removed from pytest in past major releases to help those with ancient pytest versions to upgrade.
Trivial/Internal Changes
* Improve pre-commit detection for changelog filenames
* Remove legacy code around im_func as that was python2 only
fiber used to fail on Darwin 15, but as of 15.5 with Apple LLVM
>=8.0.0 (clang 8), it works. Because we expect pkgsrc users to be up
to date with respect to minor versions of their (perhaps not
upgradable from) major version, change the regexp to expect fiber on
this platform.
ok minskin@ on tech-pkg
Wed, Aug 1, 2018 - xdebug 2.6.1
= Fixed bugs:
- Fixed issue #1525: Namespace filter does equality match instead of prefix match
- Fixed issue #1532: SIGABRT when using remote debugging and an error is thrown in eval() (Philip Hofstetter)
- Fixed issue #1543: Various memory leaks due to changes in (internal) string handling
- Fixed issue #1556: Crash when register_shutdown_function() is called with a function named call_user_func*
- Fixed issue #1557: Remove 'return' in void xdebug_build_fname
- Fixed issue #1568: Can't debug object properties that have numeric keys
+ Improvements:
- Fixed issue #1487: Re-enable IPv6 test on Travis
## Rails 5.1.6 (March 29, 2018) ##
* Fix check for minimum Ruby version to correctly identify Ruby 2.2.10.
*shia*
* Fix minitest rails plugin.
The custom reporters are added only if needed.
This will fix conflicts with others plugins.
*Kevin Robatel*
## Rails 5.1.6 (March 29, 2018) ##
* Return all mappings for a timezone identifier in `country_zones`
Some timezones like `Europe/London` have multiple mappings in
`ActiveSupport::TimeZone::MAPPING` so return all of them instead
of the first one found by using `Hash#value`. e.g:
# Before
ActiveSupport::TimeZone.country_zones("GB") # => ["Edinburgh"]
# After
ActiveSupport::TimeZone.country_zones("GB") # => ["Edinburgh", "London"]
Fixes#31668.
*Andrew White*
0.13.4 (2018-07-03)
* Support for Python 3.7
* Make the wizard handle unknown file formats gracefully
0.13.3 (2018-04-30)
* Use the TX_TOKEN environment variable to set your Transifex API token. This
essentially replaces the --token argument in the tx init command, and does
not write any credentials in the .transifexrc file.
* Add the --no-interactive argument in the tx pull command, for the case where
no user input is required. This is needed in some cases where a CI does not
want to proceed with user input and needs to fail silently.
0.13.2 (2018-04-02)
* Push and pull files more quickly by using the new --parallel option with tx
push and tx pull to make parallel requests. This is a beta feature - be
careful when using it with many files as it may cause you to hit your API
rate limits.
* --expression is now a named argument for tx config mapping so it¡Çs
consistent with the tx config mapping-bulk command with regard to how you
pass a file path expression.
* The algorithm for locating translation files has been optimized to improve
performance in cases where you have many files in your working directory.
2.1.1 (2018-06-08)
Merged Pull Requests
* Silence the warning for the default positional args case #39 (coderanger)
2.1.0 (2018-05-31)
Merged Pull Requests
* Support signing with ssh-agent (round two) #36 (coderanger)
* Forgot to put sign_version in the opts which would make it nil when p… #37
(coderanger)
* bump version to 2.1.0 #38 (thommay)
2.0.0 (2018-04-12)
Merged Pull Requests
* Move mixlib-auth debugging to trace level #32 (thommay)
# 3.1.2
### Deprecations
* This is the **last version** that supports Rails 4.0 and 4.1 and Ruby 2.0 and 2.1.
### Bug fixes
* When the `permit` matcher was used without `#on`, the controller did not use
`params#require`, the params object was duplicated, and the matcher did not
recognize the `#permit` call inside the controller. This behavior happened
because the matcher overwrote double registries with the same parameter hash
whenever ActionController::Parameters was instantiated.
* *Commit: [44c019]*
* *Issue: [#899]*
* *Pull request: [#902]*
# 3.1.1
### Bug fixes
* Some matchers make use of ActiveSupport's `in?` method, but do not include the
file where this is defined in ActiveSupport. This causes problems with
projects using shoulda-matchers that do not include all of ActiveSupport by
default. To fix this, replace `in?` with Ruby's builtin `include?`.
* *Pull request: [#879]*
* `validate_uniqueness_of` works by creating a record if it doesn't exist, and
then testing against a new record with various attributes set that are equal
to (or different than) corresponding attributes in the existing record. In
3.1.0 a change was made whereby when the uniqueness matcher is given a new
record and creates an existing record out of it, it ensures that the record is
valid before continuing on. This created a problem because if the subject,
before it was saved, was empty and therefore in an invalid state, it could not
effectively be saved. While ideally this should be enforced, doing so would be
a backward-incompatible change, so this behavior has been rolled back.
([#880], [#884], [#885])
* *Commit: [45de869]*
* *Issues: [#880], [#884], [#885]*
* Fix an issue with `validate_uniqueness_of` + `scoped_to` when used against a
model where the attribute has multiple uniqueness validations and each
validation has a different set of scopes. In this case, a test written for the
first validation (and its scopes) would pass, but tests for the other
validations (and their scopes) would not, as the matcher only considered the
first set of scopes as the *actual* set of scopes.
* *Commit: [28bd9a1]*
* *Issues: [#830]*
### Improvements
* Update `validate_uniqueness_of` so that if an existing record fails to be
created because a column is non-nullable and was not filled in, raise an
ExistingRecordInvalid exception with details on how to fix the test.
* *Commit: [78ccfc5]*
[#879]: https://github.com/thoughtbot/shoulda-matchers/issues/879
[45de869]: 45de869848
[#880]: https://github.com/thoughtbot/shoulda-matchers/issues/880
[#884]: https://github.com/thoughtbot/shoulda-matchers/issues/884
[#885]: https://github.com/thoughtbot/shoulda-matchers/issues/885
[78ccfc5]: 78ccfc50b5
[28bd9a1]: 28bd9a10c7
[#830]: https://github.com/thoughtbot/shoulda-matchers/issues/830
# 3.1.0
### Bug fixes
* Update `validate_numericality_of` so that submatchers are applied lazily
instead of immediately. Previously, qualifiers were order-dependent, meaning
that if you used `strict` before you used, say, `odd`, then `strict` wouldn't
actually apply to `odd`. Now the order that you specify qualifiers doesn't
matter.
* *Source: [6c67a5e]*
* Fix `allow_value` so that it does not raise an AttributeChangedValueError
(formerly CouldNotSetAttributeError) when used against an attribute that is an
enum in an ActiveRecord model.
* *Source: [9e8603e]*
* Add a `ignoring_interference_by_writer` qualifier to all matchers, not just
`allow_value`. *This is enabled by default, which means that you should never
get a CouldNotSetAttributeError again.* (You may get some more information if
a test fails, however.)
* *Source: [1189934], [5532f43]*
* *Fixes: [#786], [#799], [#801], [#804], [#817], [#841], [#849], [#872],
[#873], and [#874]*
* Fix `validate_numericality_of` so that it does not blow up when used against
a virtual attribute defined in an ActiveRecord model (that is, an attribute
that is not present in the database but is defined using `attr_accessor`).
* *Source: [#822]*
* Update `validate_numericality_of` so that it no longer raises an
IneffectiveTestError if used against a numeric column.
* *Source: [5ed0362]*
* *Fixes: [#832]*
[6c67a5e]: 6c67a5eb0d
[9e8603e]: 9e8603eb74
[1189934]: 1189934806
[5532f43]: 5532f4359a
[#786]: https://github.com/thoughtbot/shoulda-matchers/issues/786
[#799]: https://github.com/thoughtbot/shoulda-matchers/issues/799
[#801]: https://github.com/thoughtbot/shoulda-matchers/issues/801
[#804]: https://github.com/thoughtbot/shoulda-matchers/issues/804
[#817]: https://github.com/thoughtbot/shoulda-matchers/issues/817
[#841]: https://github.com/thoughtbot/shoulda-matchers/issues/841
[#849]: https://github.com/thoughtbot/shoulda-matchers/issues/849
[#872]: https://github.com/thoughtbot/shoulda-matchers/issues/872
[#873]: https://github.com/thoughtbot/shoulda-matchers/issues/873
[#874]: https://github.com/thoughtbot/shoulda-matchers/issues/874
[#822]: https://github.com/thoughtbot/shoulda-matchers/pull/822
[5ed0362]: 5ed0362419
[#832]: https://github.com/thoughtbot/shoulda-matchers/issues/832
### Features
* Add a new qualifier, `ignoring_case_sensitivity`, to `validate_uniqueness_of`.
This provides a way to test uniqueness of an attribute whose case is
normalized, either in a custom writer method for that attribute, or in a
custom `before_validation` callback.
* *Source: [#840]*
* *Fixes: [#836]*
[#840]: https://github.com/thoughtbot/shoulda-matchers/pull/840
[#836]: https://github.com/thoughtbot/shoulda-matchers/issues/836
### Improvements
* Improve failure messages and descriptions of all matchers across the board so
that it is easier to understand what the matcher was doing when it failed.
(You'll see a huge difference in the output of the numericality and uniqueness
matchers in particular.)
* Matchers now raise an error if any attributes that the matcher is attempting
to set do not exist on the model.
* *Source: [2962112]*
* Update `validate_numericality_of` so that it doesn't always run all of the
submatchers, but stops on the first one that fails. Since failure messages
now contain information as to what value the matcher set on the attribute when
it failed, this change guarantees that the correct value will be shown.
* *Source: [8e24a6e]*
* Continue to detect if attributes change incoming values, but now instead of
immediately seeing a CouldNotSetAttributeError, you will only be informed
about it if the test you've written fails.
* *Source: [1189934]*
* Add an additional check to `define_enum_for` to ensure that the column that
underlies the enum attribute you're testing is an integer column.
* *Source: [68dd70a]*
* Add a test for `validate_numericality_of` so that it officially supports money
columns.
* *Source: [a559713]*
* *Refs: [#841]*
[2962112]: 2962112114
[8e24a6e]: 8e24a6e9b2
[68dd70a]: 68dd70a23d
[a559713]: a559713f96
# 3.0.1
### Bug fixes
* Fix `validate_inclusion_of` + `in_array` when used against a date or datetime
column/attribute so that it does not raise a CouldNotSetAttributeError.
([#783], [8fa97b4])
* Fix `validate_numericality_of` when used against a numeric column so that it
no longer raises a CouldNotSetAttributeError if the matcher has been qualified
in any way (`only_integer`, `greater_than`, `odd`, etc.). ([#784], [#812])
### Improvements
* `validate_uniqueness_of` now raises a NonCaseSwappableValueError if the value
the matcher is using to test uniqueness cannot be case-swapped -- in other
words, if it doesn't contain any alpha characters. When this is the case, the
matcher cannot work effectively. ([#789], [ada9bd3])
[#783]: https://github.com/thoughtbot/shoulda-matchers/pull/783
[8fa97b4]: 8fa97b4ff3
[#784]: https://github.com/thoughtbot/shoulda-matchers/pull/784
[#789]: https://github.com/thoughtbot/shoulda-matchers/pull/789
[ada9bd3]: ada9bd3a1b
[#812]: https://github.com/thoughtbot/shoulda-matchers/pull/812
# 3.0.0
### Backward-incompatible changes
* We've dropped support for Rails 3.x, Ruby 1.9.2, and Ruby 1.9.3, and RSpec 2.
All of these have been end-of-lifed. ([a4045a1], [b7fe87a], [32c0e62])
* The gem no longer detects the test framework you're using or mixes itself into
that framework automatically. [History][no-auto-integration-1] has
[shown][no-auto-integration-2] that performing any kind of detection is prone
to bugs and more complicated than it should be.
Here are the updated instructions:
* You no longer need to say `require: false` in your Gemfile; you can
include the gem as normal.
* You'll need to add the following somewhere in your `rails_helper` (for
RSpec) or `test_helper` (for Minitest / Test::Unit):
``` ruby
Shoulda::Matchers.configure do |config|
config.integrate do |with|
# Choose a test framework:
with.test_framework :rspec
with.test_framework :minitest
with.test_framework :minitest_4
with.test_framework :test_unit
# Choose one or more libraries:
with.library :active_record
with.library :active_model
with.library :action_controller
# Or, choose the following (which implies all of the above):
with.library :rails
end
end
```
([1900071])
* Previously, under RSpec, all of the matchers were mixed into all of the
example groups. This created a problem because some gems, such as
[active_model_serializers-matchers], provide matchers that share the same
name as some of our own matchers. Now, matchers are only mixed into whichever
example group they belong to:
* ActiveModel and ActiveRecord matchers are available only in model example
groups.
* ActionController matchers are available only in controller example groups.
* The `route` matcher is available only in routing example groups.
([af98a23], [8cf449b])
* There are two changes to `allow_value`:
* The negative form of `allow_value` has been changed so that instead of
asserting that any of the given values is an invalid value (allowing good
values to pass through), assert that *all* values are invalid values
(allowing good values not to pass through). This means that this test which
formerly passed will now fail:
``` ruby
expect(record).not_to allow_value('good value', *bad_values)
```
([19ce8a6])
* `allow_value` now raises a CouldNotSetAttributeError if in setting the
attribute, the value of the attribute from reading the attribute back is
different from the one used to set it.
This would happen if the writer method for that attribute has custom logic
to ignore certain incoming values or change them in any way. Here are three
examples we've seen:
* You're attempting to assert that an attribute should not allow nil, yet
the attribute's writer method contains a conditional to do nothing if
the attribute is set to nil:
``` ruby
class Foo
include ActiveModel::Model
attr_reader :bar
def bar=(value)
return if value.nil?
@bar = value
end
end
describe Foo do
it do
foo = Foo.new
foo.bar = "baz"
# This will raise a CouldNotSetAttributeError since `foo.bar` is now "123"
expect(foo).not_to allow_value(nil).for(:bar)
end
end
```
* You're attempting to assert that an numeric attribute should not allow a
string that contains non-numeric characters, yet the writer method for
that attribute strips out non-numeric characters:
``` ruby
class Foo
include ActiveModel::Model
attr_reader :bar
def bar=(value)
@bar = value.gsub(/\D+/, '')
end
end
describe Foo do
it do
foo = Foo.new
# This will raise a CouldNotSetAttributeError since `foo.bar` is now "123"
expect(foo).not_to allow_value("abc123").for(:bar)
end
end
```
* You're passing a value to `allow_value` that the model typecasts into
another value:
``` ruby
describe Foo do
# Assume that `attr` is a string
# This will raise a CouldNotSetAttributeError since `attr` typecasts `[]` to `"[]"`
it { should_not allow_value([]).for(:attr) }
end
```
With all of these failing examples, why are we making this change? We want
to guard you (as the developer) from writing a test that you think acts one
way but actually acts a different way, as this could lead to a confusing
false positive or negative.
If you understand the problem and wish to override this behavior so that
you do not get a CouldNotSetAttributeError, you can add the
`ignoring_interference_by_writer` qualifier like so. Note that this will not
always cause the test to pass.
``` ruby
it { should_not allow_value([]).for(:attr).ignoring_interference_by_writer }
```
([9d9dc4e])
* `validate_uniqueness_of` is now properly case-sensitive by default, to match
the default behavior of the validation itself. This is a backward-incompatible
change because this test which incorrectly passed before will now fail:
``` ruby
class Product < ActiveRecord::Base
validates_uniqueness_of :name, case_sensitive: false
end
describe Product do
it { is_expected.to validate_uniqueness_of(:name) }
end
```
([57a1922])
* `ensure_inclusion_of`, `ensure_exclusion_of`, and `ensure_length_of` have been
removed in favor of their `validate_*` counterparts. ([55c8d09])
* `set_the_flash` and `set_session` have been changed to more closely align with
each other:
* `set_the_flash` has been removed in favor of `set_flash`. ([801f2c7])
* `set_session('foo')` is no longer valid syntax, please use
`set_session['foo']` instead. ([535fe05])
* `set_session['key'].to(nil)` will no longer pass when the key in question
has not been set yet. ([535fe05])
* Change `set_flash` so that `set_flash[:foo].now` is no longer valid syntax.
You'll want to use `set_flash.now[:foo]` instead. This was changed in order to
more closely align with how `flash.now` works when used in a controller.
([#755], [#752])
* Change behavior of `validate_uniqueness_of` when the matcher is not
qualified with any scopes, but your validation is. Previously the following
test would pass when it now fails:
``` ruby
class Post < ActiveRecord::Base
validate :slug, uniqueness: { scope: :user_id }
end
describe Post do
it { should validate_uniqueness_of(:slug) }
end
```
([6ac7b81])
[active_model_serializers-matchers]: https://github.com/adambarber/active_model_serializers-matchers
[no-auto-integration-1]: 049080c673
[no-auto-integration-2]: https://github.com/rr/rr/issues/29
[1900071]: 190007155e
[b7fe87a]: b7fe87ae91
[a4045a1]: a4045a1f9b
[57a1922]: 57a19228b6
[19ce8a6]: 19c38a642a
[eaaa2d8]: eaaa2d83e5
[55c8d09]: 55c8d09bf2
[801f2c7]: 801f2c7c1e
[535fe05]: 535fe05be8
[6ac7b81]: 6ac7b8158c
[#755]: https://github.com/thoughtbot/shoulda-matchers/pull/755
[#752]: https://github.com/thoughtbot/shoulda-matchers/pull/752
[9d9dc4e]: 9d9dc4e6b9
[32c0e62]: 32c0e62596
[af98a23]: af98a23091
[8cf449b]: 8cf449b4ca
### Bug fixes
* So far the tests for the gem have been running against only SQLite. Now they
run against PostgreSQL, too. As a result we were able to fix some
Postgres-related bugs, specifically around `validate_uniqueness_of`:
* When scoped to a UUID column that ends in an "f", the matcher is able to
generate a proper "next" value without erroring. ([#402], [#587], [#662])
* Support scopes that are PostgreSQL array columns. Please note that this is
only supported for Rails 4.2 and greater, as versions before this cannot
handle array columns correctly, particularly in conjunction with the
uniqueness validator. ([#554])
* Fix so that when scoped to a text column and the scope is set to nil before
running it through the matcher, the matcher does not fail. ([#521], [#607])
* Fix `define_enum_for` so that it actually tests that the attribute is present
in the list of defined enums, as you could fool it by merely defining a class
method that was the pluralized version of the attribute name. In the same
vein, passing a pluralized version of the attribute name to `define_enum_for`
would erroneously pass, and now it fails. ([#641])
* Fix `permit` so that it does not break the functionality of
ActionController::Parameters#require. ([#648], [#675])
* Fix `validate_uniqueness_of` + `scoped_to` so that it does not raise an error
if a record exists where the scoped attribute is nil. ([#677])
* Fix `route` matcher so if your route includes a default `format`, you can
specify this as a symbol or string. ([#693])
* Fix `validate_uniqueness_of` so that it allows you to test against scoped
attributes that are boolean columns. ([#457], [#694])
* Fix failure message for `validate_numericality_of` as it sometimes didn't
provide the reason for failure. ([#699])
* Fix `shoulda/matchers/independent` so that it can be required
independently, without having to require all of the gem. ([#746], [e0a0200])
### Features
* Add `on` qualifier to `permit`. This allows you to make an assertion that
a restriction was placed on a slice of the `params` hash and not the entire
`params` hash. Although we don't require you to use this qualifier, we do
recommend it, as it's a more precise check. ([#675])
* Add `strict` qualifier to `validate_numericality_of`. ([#620])
* Add `on` qualifier to `validate_numericality_of`. ([9748869]; h/t [#356],
[#358])
* Add `join_table` qualifier to `have_and_belong_to_many`. ([#556])
* `allow_values` is now an alias for `allow_value`. This makes more sense when
checking against multiple values:
``` ruby
it { should allow_values('this', 'and', 'that') }
```
([#692])
[9748869]: 9748869091
[#402]: https://github.com/thoughtbot/shoulda-matchers/pull/402
[#587]: https://github.com/thoughtbot/shoulda-matchers/pull/587
[#662]: https://github.com/thoughtbot/shoulda-matchers/pull/662
[#554]: https://github.com/thoughtbot/shoulda-matchers/pull/554
[#641]: https://github.com/thoughtbot/shoulda-matchers/pull/641
[#521]: https://github.com/thoughtbot/shoulda-matchers/pull/521
[#607]: https://github.com/thoughtbot/shoulda-matchers/pull/607
[#648]: https://github.com/thoughtbot/shoulda-matchers/pull/648
[#675]: https://github.com/thoughtbot/shoulda-matchers/pull/675
[#677]: https://github.com/thoughtbot/shoulda-matchers/pull/677
[#620]: https://github.com/thoughtbot/shoulda-matchers/pull/620
[#693]: https://github.com/thoughtbot/shoulda-matchers/pull/693
[#356]: https://github.com/thoughtbot/shoulda-matchers/pull/356
[#358]: https://github.com/thoughtbot/shoulda-matchers/pull/358
[#556]: https://github.com/thoughtbot/shoulda-matchers/pull/556
[#457]: https://github.com/thoughtbot/shoulda-matchers/pull/457
[#694]: https://github.com/thoughtbot/shoulda-matchers/pull/694
[#692]: https://github.com/thoughtbot/shoulda-matchers/pull/692
[#699]: https://github.com/thoughtbot/shoulda-matchers/pull/699
[#746]: https://github.com/thoughtbot/shoulda-matchers/pull/746
v0.27.4
-------
This is a security release fixing out-of-bounds reads when
processing smart-protocol "ng" packets.
When parsing an "ng" packet, we keep track of both the current position
as well as the remaining length of the packet itself. But instead of
taking care not to exceed the length, we pass the current pointer's
position to `strchr`, which will search for a certain character until
hitting NUL. It is thus possible to create a crafted packet which
doesn't contain a NUL byte to trigger an out-of-bounds read.
The issue was discovered by the oss-fuzz project, issue 9406.
v0.27.3
-------
This is a security release fixing out-of-bounds reads when
reading objects from a packfile. This corresponds to
CVE-2018-10887 and CVE-2018-10888, which were both reported by
Riccardo Schirone.
When packing objects into a single so-called packfile, objects
may not get stored as complete copies but instead as deltas
against another object "base". A specially crafted delta object
could trigger an integer overflow and thus bypass our input
validation, which may result in copying memory before or after
the base object into the final deflated object. This may lead to
objects containing copies of system memory being written into the
object database. As the hash of those objects cannot be easily
controlled by the attacker, it is unlikely that any of those
objects will be valid and referenced by the commit graph.
Note that the error could also be triggered by the function
`git_apply__patch`. But as this function is not in use outside of
our test suite, it is not a possible attack vector.
1.1.2 (2018-06-10)
* Add example code
* Fix file descriptor leak (forgetting to close).
* Use File.open instead of Kernel#open.
* Fix LocalJumpError
* Follow up changes of Ripper.sexp in 2.6.0dev
* Prevent infinite loop when raising exception in trace event
* Fix ArgumentError when Japanese is included
* Handle character width.
* Cache offset data
1.1.3 (2018-06-24)
* pry-power_assert doesn't work
* Use benchmark-ips
4.12.0 (2018/09/11)
Support for additional APIs
* #1060 Add support for Transfer repository API
* #1070 Add support for List Assignees API
* #975 Add support for Community Profile API
Bugfixes
* #1069 Do not pass wrong params in org membership method
v4.11.0 (2018/08/30)
Code clean up
* #1054 Remove the :name key from #add_team_repository request
Documentation fixes
* #1050 Add in note about require
* #1056 Fixes documentation url for outside_collaborators
Existing endpoint changes
* #1055 Use new app installation token endpoint
Support new endpoints
* #1052 App installation finders
4.10.0 (2018/08/09)
Graduated preview periods
* #1020 Remove preview warning for marketplace API
* #1041 Remove marketplace preview warnings (we mean it, this time)
* #1042 Remove preview warning for Repository Invitations API
* #1047 Rework request review API to support team reviewers
Support for new endpoints
* #1044 Implement Topics API
* #990 Implement delete a pull request review request
Bugfixes
* #1025 Fix contributors endpoint for empty repos
* #1034 Duplicate option to prevent mutating original
* #1018 Convert OCTOKIT_SSL_VERIFY_MODE environment variable to integer
Enhancements
* #1021 Add Faraday retry middleware
* #1032 Use auto pagination when retrieving statuses
4.9.0 (2018/05/08)
Bugfixes
* #1006 Use Addressable::URI instead of stdlib URI for normalization
* #1003 Fix pagination of GitHub App endpoints
* #1000 Call dup on arguments before mutating
Documentation changes
* #969 Document the steps necessary to cut a release
* #972 Url to the review API was wrong
* #973 Fix pull_requests_comments example documentation
* #985 Add tag_name to update_release documentation
* #989 Command example fix in documentation.
* #1008 Fixes documentation for getting single issue comment
* #1011 Fix example call to Octokit.label
Enhancements
* #982 Be able to set an SSL verify mode on faraday
* #1009 Add missing remove_org_membership alias
Maintenance
* #970 Update Ruby versions for CI
* #961 Update VCR gem
Support for additional API endpoints
* #984 Add remove_assignees method to the client
* #959 Commit Search API preview
* #996 Add ability to list a single deployment, by id
Release 2.4.0 (2018/07/23)
* Added username and password validation for elevated option on Windows
* Added support for setting sensitive so that potentially sensitive output is
suppressed
0.2.0 2018/09/04
* Include offending string in error message (#14)
As an aid to debugging, including the string that filesize was unable to
parse in the error message.
* Accept unicode space characters
[[:space:]] includes unicode space characters too, so when Nokogiri
interprets "12.3 MiB" as "12.3\u00A0MiB", Filesize will still work.
[[:blank:]] might be even better because it doesn't include newline and
carriage returns.
* Support unit without B suffix
e.g. Kubernetes uses this format:
https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#memory-units
* added precision parameter to to_s() and pretty(), fixes#21
* fixed an assignment typo
1.7.0 (2018/06/23)
* Only take into account the first dot separeted part of the file name which
matches an authorized locale code
* More straightforward implementation of fix for extracting locale from file
name
* Add a comment on locale segmentation over several yaml files
* Extract locale from file name when they are formated as `some.topic.qq.yml`
11.3.0:
No longer use two techniques for splitting lines. Instead, unconditionally rely on io.open for universal newlines support and always use splitlines.
11.2.0:
Rely on importlib_metadata instead of setuptools/pkg_resources to load the version of the module. Added tests ensuring a <100ms import time for the path module. This change adds an explicit dependency on the importlib_metadata package, but the project still supports copying of the path.py module without any dependencies.
1.6.0:
- add TerminalWriter.width_of_current_line (i18n version of
TerminalWriter.chars_on_current_line), a read-only property
that tracks how wide the current line is, attempting to take
into account international characters in the calculation.
The Python dis module allows you to disassemble bytecode from the same version
of Python that you are running on. But what about bytecode from different
versions?
That's what this package is for. It can "marshal load" Python bytecodes from
different versions of Python. The command-line routine pydisasm will show
disassembly output using Python 3.6 disassembly conventions.
Also, if you need to modfiy and write bytecode, the routines here can be of
help. There are routines to pack and unpack the read-only tuples in Python's
Code type. For interoperability between Python 2 and 3 we provide our own
versions of the Code type, and we provide routines to reduce the tedium in
writing a bytecode file.
This package also has an extensive knowledge of Python bytecode magic numbers,
including Pypy and others, and how to translate from sys.sys_info major, minor,
and release numbers to the corresponding magic value.
So If you want to write a cross-version assembler, or a bytecode-level
optimizer this package may also be useful. In addition to the kinds of
instruction categorization that dis offers, we have additional categories for
things that would be useful in such a bytecode optimizer.
VisualVM 1.4.1 released on April 25th, 2018
Features and Enhancements:
Heap Viewer allows to compare heap dumps
Load Snapshot dialog uses All Supported Files filter by default
Full support for running on JDK 10 and monitoring/profiling Java 10 processes
Fixed Bugs:
GH-51: StackOverflowError at Startup Profiler
GH-52: A11Y - Keyboard navigation using Tab does not work
GH-53: Configurable OQL results limit
GH-54: A11Y - Filter & Find actions not accessible using keyboard shortcuts
GH-55: Make thread view collapsable in heapViewer
GH-57: Why has the "compare to another heap dump" feature disappeared
GH-59: Provide All Files file filter in File | Load
GH-62: OQL engine not available
GH-73: VisualVM 1.4 refuses to launch under JDK 10
VisualVM 1.4 released on December 12th, 2017
Features and Enhancements:
CPU Sampler and Profiler display live call trees, delta results, selected threads, and many other improvements
Memory Profiler allows profiling of defined classes, displays delta results
Introducing a lightweight JDBC profiler for monitoring SQL commands executed by a Java process
Heap Viewer is the new .hprof heap dumps viewer in VisualVM with a lot of improvements over the original HeapWalker
Colored classes/methods in Sampler, Profiler and Heap Viewer views based on user-defined filters
Full support for running on JDK 9 and monitoring/profiling Java 9 processes
Built on NetBeans Platform & profiler 9.0-dev
API Changes:
Compatible: com.sun.tools.visualvm.core.snapshot.Snapshot.computeSnapshotID() added
Fixed Bugs:
GH-3: MBeans plugin doesn't repaint window
GH-7: NullPointerException when starting with eclipse Launcher
GH-14: Can not save snapshots of profiler or sampler when multiple users run VisualVM on the same Machine
GH-31: "Peform GC"
GH-38: Profile and Profiler Snapshot actions always disabled
VisualVM 1.3.9 released on October 4th, 2016
Migration to GitHub:
VisualVM project has been migrated to GitHub, including the sources, downloads and update centers. New project pages have been created at https://visualvm.github.io, the content will be incrementally transferred from the original pages at https://visualvm.java.net.
Features and Enhancements:
Issue 603: remember decisions about future host/connection resolving
Issue 618: --openjmx cli option should take a connection name and allow setting skip ssl
Enabled VM Coredumps support on Microsoft Windows
The --openid and --openpid parameters now accept index of process tab to open
Start Page has been refreshed to contain up to date links to useful resources
Experimental support for running on JDK 9 and monitoring/profiling Java 9 processes
Built on NetBeans Platform & profiler 8.0.2
API Changes:
Compatible: com.sun.tools.visualvm.charts.SimpleXYChartDescriptor.decimal(minValue, maxValue, initialYMargin, chartFactor, customFormat, hideableItems, valuesBuffer) added
Compatible: com.sun.tools.visualvm.core.options.GlobalPreferences.setDoNotShowAgain(key, value) added
Compatible: com.sun.tools.visualvm.core.options.GlobalPreferences.getDoNotShowAgain(key) added
Fixed Bugs:
Issue 458: libprofilerinterface.so exports popular symbol names
Issue 575: Fix sampler memory snapshot type
Issue 594: Cannot load heap dump - ArrayIndexOutOfBoundsException
Issue 601: java.lang.ClassNotFoundException: com.fubar.MyClass$$Lambda$9
Issue 602: SimpleXYChartDescriptor.decimal Should Be Able To Display > 2 decimal places
Issue 604: Tracer dynamic does not work with JDK 8
Issue 605: VisualVM fails to load local java applications when NetbeansBased applications are running
Issue 606: Command line arg --openjmx doesn't ask for credentials in some cases
Issue 607: Incorrect snapshot name
Issue 608: ArrayIndexOutOfBoundsException
Issue 623: Support Lambdas in Java 8
Issue 625: Opening a thread dump may take several minutes
Issue 626: ClassCastException: java.lang.String cannot be cast to [Ljava.lang.Object;
Issue 627: Memory sampling does not work
Issue 636: Thread dump cannot be closed
IssueTracker query to list all changes in NetBeans profiler 8.0.1 and 8.0.2 affecting VisualVM
IssueTracker query to list all changes in NetBeans profiler after 8.0.2 affecting VisualVM
3.71.10:
This patch allows :func:~hypothesis.strategies.from_type to handle the empty tuple type, :obj:typing.Tuple[()] <python:typing.Tuple>.
3.71.9:
This patch updates some internal comments for :pypi:mypy. There is no user-visible effect, even for Mypy users.
3.71.8:
This patch fixes a rare bug that would cause a particular shrinker pass to raise an IndexError, if a shrink improvement changed the underlying data in an unexpected way.
3.71.7:
This release fixes the broken cross-references in our docs, and adds a CI check so we don't add new ones.
3.71.6:
This patch fixes two bugs (:issue:944 and :issue:1521), where messages about :func:@seed <hypothesis.seed> did not check the current verbosity setting, and the wrong settings were active while executing :ref:explicit examples <providing-explicit-examples>.
3.71.5:
This patch fixes a DeprecationWarning added in Python 3.8 (:issue:1576).
3.71.4:
This is a no-op release, which implements automatic DOI minting and code archival of Hypothesis via Zenodo. Thanks to CERN and the EU Horizon 2020 programme for providing this service!
Check our :gh-file:CITATION file for details, or head right on over to doi.org/10.5281/zenodo.1412597
3.71.3:
This release adds the test name to some deprecation warnings, for easier debugging.
3.71.2:
This release makes Hypothesis's memory usage substantially smaller for tests with many examples, by bounding the number of past examples it keeps around.
You will not see much difference unless you are running tests with :obj:~hypothesis.settings.max_examples set to well over 1000, but if you do have such tests then you should see memory usage mostly plateau where previously it would have grown linearly with time.
3.71.1:
This patch adds internal comments to some tree traversals in the core engine. There is no user-visible change.
3.71.0:
This release deprecates the coverage-guided testing functionality, as it has proven brittle and does not really pull its weight.
We intend to replace it with something more useful in the future, but the feature in its current form does not seem to be worth the cost of using, and whatever replaces it will likely look very different.
v40.4.1:
* Bump vendored pyparsing to 2.2.1.
v40.4.0:
* Join the sdist --dist-dir and the build_meta sdist directory argument to point to the same target (meaning the build frontend no longer needs to clean manually the dist dir to avoid multiple sdist presence, and setuptools no longer needs to handle conflicts between the two).
v40.3.0:
* Fixed a bug with namespace packages under Python 3.6 when one package in current directory hides another which is installed.
* Set timestamp of .egg-info directory whenever egg_info command is run.
* build_meta.get_requires_for_build_sdist now does not include the wheel package anymore.
* Suppress warnings in pkg_resources.handle_ns.
* Remove internal use of six.binary_type.
SQLite Release 3.25.1:
Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged.
The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required.
SQLite Release 3.25.0:
Add support for window functions
Enhancements the ALTER TABLE command:
- Add support for renaming columns within a table using ALTER TABLE table RENAME COLUMN oldname TO newname.
- Fix table rename feature so that it also updates references to the renamed table in triggers and views.
Query optimizer improvements:
- Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
- The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
- Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
Use a separate mutex on every inode in the unix VFS, rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
Enhance the PRAGMA integrity_check command for improved detection of problems on the page freelist.
Output infinity as 1e999 in the ".dump" command of the command-line shell.
Added the SQLITE_FCNTL_DATA_VERSION file-control.
Added the Geopoly module
Bug fixes:
The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer.
On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks.
Avoid using a prepared statement for ".stats on" command of the CLI after it has been closed by the ".eqp full" logicc.
The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character.
0.9.1:
Fix missing and misplaced comma's in many providers.
Refactor IPv4 address generation to leverage ipaddress module.
An en_NZ provider for addresses, phone numbers and email addresses.
Add unique argument to words() for returning unique words.
Allow US territories to be excluded from state_abbr() for en_US provider.
Add support for Python 3.7.
Git 2.19 Release Notes
Updates since v2.18
-------------------
UI, Workflows & Features
* "git diff" compares the index and the working tree. For paths
added with intent-to-add bit, the command shows the full contents
of them as added, but the paths themselves were not marked as new
files. They are now shown as new by default.
"git apply" learned the "--intent-to-add" option so that an
otherwise working-tree-only application of a patch will add new
paths to the index marked with the "intent-to-add" bit.
* "git grep" learned the "--column" option that gives not just the
line number but the column number of the hit.
* The "-l" option in "git branch -l" is an unfortunate short-hand for
"--create-reflog", but many users, both old and new, somehow expect
it to be something else, perhaps "--list". This step warns when "-l"
is used as a short-hand for "--create-reflog" and warns about the
future repurposing of the it when it is used.
* The userdiff pattern for .php has been updated.
* The content-transfer-encoding of the message "git send-email" sends
out by default was 8bit, which can cause trouble when there is an
overlong line to bust RFC 5322/2822 limit. A new option 'auto' to
automatically switch to quoted-printable when there is such a line
in the payload has been introduced and is made the default.
* "git checkout" and "git worktree add" learned to honor
checkout.defaultRemote when auto-vivifying a local branch out of a
remote tracking branch in a repository with multiple remotes that
have tracking branches that share the same names.
(merge 8d7b558bae ab/checkout-default-remote later to maint).
* "git grep" learned the "--only-matching" option.
* "git rebase --rebase-merges" mode now handles octopus merges as
well.
* Add a server-side knob to skip commits in exponential/fibbonacci
stride in an attempt to cover wider swath of history with a smaller
number of iterations, potentially accepting a larger packfile
transfer, instead of going back one commit a time during common
ancestor discovery during the "git fetch" transaction.
(merge 42cc7485a2 jt/fetch-negotiator-skipping later to maint).
* A new configuration variable core.usereplacerefs has been added,
primarily to help server installations that want to ignore the
replace mechanism altogether.
* Teach "git tag -s" etc. a few configuration variables (gpg.format
that can be set to "openpgp" or "x509", and gpg.<format>.program
that is used to specify what program to use to deal with the format)
to allow x.509 certs with CMS via "gpgsm" to be used instead of
openpgp via "gnupg".
* Many more strings are prepared for l10n.
* "git p4 submit" learns to ask its own pre-submit hook if it should
continue with submitting.
* The test performed at the receiving end of "git push" to prevent
bad objects from entering repository can be customized via
receive.fsck.* configuration variables; we now have gained a
counterpart to do the same on the "git fetch" side, with
fetch.fsck.* configuration variables.
* "git pull --rebase=interactive" learned "i" as a short-hand for
"interactive".
* "git instaweb" has been adjusted to run better with newer Apache on
RedHat based distros.
* "git range-diff" is a reimplementation of "git tbdiff" that lets us
compare individual patches in two iterations of a topic.
* The sideband code learned to optionally paint selected keywords at
the beginning of incoming lines on the receiving end.
* "git branch --list" learned to take the default sort order from the
'branch.sort' configuration variable, just like "git tag --list"
pays attention to 'tag.sort'.
* "git worktree" command learned "--quiet" option to make it less
verbose.
Performance, Internal Implementation, Development Support etc.
* The bulk of "git submodule foreach" has been rewritten in C.
* The in-core "commit" object had an all-purpose "void *util" field,
which was tricky to use especially in library-ish part of the
code. All of the existing uses of the field has been migrated to a
more dedicated "commit-slab" mechanism and the field is eliminated.
* A less often used command "git show-index" has been modernized.
(merge fb3010c31f jk/show-index later to maint).
* The conversion to pass "the_repository" and then "a_repository"
throughout the object access API continues.
* Continuing with the idea to programatically enumerate various
pieces of data required for command line completion, teach the
codebase to report the list of configuration variables
subcommands care about to help complete them.
* Separate "rebase -p" codepath out of "rebase -i" implementation to
slim down the latter and make it easier to manage.
* Make refspec parsing codepath more robust.
* Some flaky tests have been fixed.
* Continuing with the idea to programmatically enumerate various
pieces of data required for command line completion, the codebase
has been taught to enumerate options prefixed with "--no-" to
negate them.
* Build and test procedure for netrc credential helper (in contrib/)
has been updated.
* Remove unused function definitions and declarations from ewah
bitmap subsystem.
* Code preparation to make "git p4" closer to be usable with Python 3.
* Tighten the API to make it harder to misuse in-tree .gitmodules
file, even though it shares the same syntax with configuration
files, to read random configuration items from it.
* "git fast-import" has been updated to avoid attempting to create
delta against a zero-byte-long string, which is pointless.
* The codebase has been updated to compile cleanly with -pedantic
option.
(merge 2b647a05d7 bb/pedantic later to maint).
* The character display width table has been updated to match the
latest Unicode standard.
(merge 570951eea2 bb/unicode-11-width later to maint).
* test-lint now looks for broken use of "VAR=VAL shell_func" in test
scripts.
* Conversion from uchar[40] to struct object_id continues.
* Recent "security fix" to pay attention to contents of ".gitmodules"
while accepting "git push" was a bit overly strict than necessary,
which has been adjusted.
* "git fsck" learns to make sure the optional commit-graph file is in
a sane state.
* "git diff --color-moved" feature has further been tweaked.
* Code restructuring and a small fix to transport protocol v2 during
fetching.
* Parsing of -L[<N>][,[<M>]] parameters "git blame" and "git log"
take has been tweaked.
* lookup_commit_reference() and friends have been updated to find
in-core object for a specific in-core repository instance.
* Various glitches in the heuristics of merge-recursive strategy have
been documented in new tests.
* "git fetch" learned a new option "--negotiation-tip" to limit the
set of commits it tells the other end as "have", to reduce wasted
bandwidth and cycles, which would be helpful when the receiving
repository has a lot of refs that have little to do with the
history at the remote it is fetching from.
* For a large tree, the index needs to hold many cache entries
allocated on heap. These cache entries are now allocated out of a
dedicated memory pool to amortize malloc(3) overhead.
* Tests to cover various conflicting cases have been added for
merge-recursive.
* Tests to cover conflict cases that involve submodules have been
added for merge-recursive.
* Look for broken "&&" chains that are hidden in subshell, many of
which have been found and corrected.
* The singleton commit-graph in-core instance is made per in-core
repository instance.
* "make DEVELOPER=1 DEVOPTS=pedantic" allows developers to compile
with -pedantic option, which may catch more problematic program
constructs and potential bugs.
* Preparatory code to later add json output for telemetry data has
been added.
* Update the way we use Coccinelle to find out-of-style code that
need to be modernised.
* It is too easy to misuse system API functions such as strcat();
these selected functions are now forbidden in this codebase and
will cause a compilation failure.
* Add a script (in contrib/) to help users of VSCode work better with
our codebase.
* The Travis CI scripts were taught to ship back the test data from
failed tests.
(merge aea8879a6a sg/travis-retrieve-trash-upon-failure later to maint).
* The parse-options machinery learned to refrain from enclosing
placeholder string inside a "<bra" and "ket>" pair automatically
without PARSE_OPT_LITERAL_ARGHELP. Existing help text for option
arguments that are not formatted correctly have been identified and
fixed.
(merge 5f0df44cd7 rs/parse-opt-lithelp later to maint).
* Noiseword "extern" has been removed from function decls in the
header files.
* A few atoms like %(objecttype) and %(objectsize) in the format
specifier of "for-each-ref --format=<format>" can be filled without
getting the full contents of the object, but just with the object
header. These cases have been optimized by calling
oid_object_info() API (instead of reading and inspecting the data).
* The end result of documentation update has been made to be
inspected more easily to help developers.
* The API to iterate over all objects learned to optionally list
objects in the order they appear in packfiles, which helps locality
of access if the caller accesses these objects while as objects are
enumerated.
* Improve built-in facility to catch broken &&-chain in the tests.
* The more library-ish parts of the codebase learned to work on the
in-core index-state instance that is passed in by their callers,
instead of always working on the singleton "the_index" instance.
* A test prerequisite defined by various test scripts with slightly
different semantics has been consolidated into a single copy and
made into a lazily defined one.
(merge 6ec633059a wc/make-funnynames-shared-lazy-prereq later to maint).
* After a partial clone, repeated fetches from promisor remote would
have accumulated many packfiles marked with .promisor bit without
getting them coalesced into fewer packfiles, hurting performance.
"git repack" now learned to repack them.
* Partially revert the support for multiple hash functions to regain
hash comparison performance; we'd think of a way to do this better
in the next cycle.
* "git help --config" (which is used in command line completion)
missed the configuration variables not described in the main
config.txt file but are described in another file that is included
by it, which has been corrected.
* The test linter code has learned that the end of here-doc mark
"EOF" can be quoted in a double-quote pair, not just in a
single-quote pair.
This bug-fix release addresses 6 regressions in Gradle 4.10:
- FileTreeElement.getPath() returns absolute system dependent
filepath.
- Up-to-date checks for missing files can be incorrect
- Gradle fails when no incremental compile snapshot data
available.
- Gradle 4.10 incorrect ordering between dependencies of
dependent tasks.
- tasks.withType(ScalaCompile::class.java).configureEach fails
on multi-project builds.
- Double deprecation message when using publishing plugin.
Notable changes:
- add DiscardUnknown function
- The serialization logic (for both Marshal and Unmarshal) has been
optimized. Testing inside Google demonstrate that the new
implementation is about 1.3x to 2.1x faster.
- Unknown fields in proto3 are now preserved.
- JSON marshal and unmarshal now check for proto2 required field.
- GetExtension returns the raw bytes if the ExtensionDesc does not
have type information.
- Invalid UTF-8 in string types are rejected during marshal and
unmarshal.
- Fields of bad wire types are treated as unknown fields instead of an
error.
- The protoc-gen-go generator supports the paths=source_relative
option.
- Unknown fields in map entries are now ignored instead of causing an
unmarshal error.
- The "import public" feature is now implemented using Go type
aliases.
- jsonpb.Unmarshal correctly handles escaped strings for some of the
well-known types
- jsonpb.Unmarshal correctly returns an error when trying to marshal a
scalar enum into repeated enums.
- jsonpb.Unmarshal correctly handles string versions of numeric
primitives
- jsonpb.Unmarshal correctly handles enum values in maps
- fixes a performance regression where nested maps led to quadratic
behavior
- reverts strict UTF-8 validation for proto2 string fields
- makes UTF-8 validation errors for proto3 string fields non-fatal
0.19.6:
BUG FIXES
* Fix support for custom transport arguments in dulwich.porcelain.clone.
* Fix compatibility with Python 3.8
* Fix some corner cases in path_to_tree_path.
* Support paths as bytestrings in various places in dulwich.index
A Go port of the Ruby dotenv project, which loads env vars from a .env
file. It can be used as a library (for loading in env for your own
daemons etc) or as a bin command.
