| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Parents may be unlinked while another generator sharing part of the
chain is running. As such, we cannot assume that the parent chain
goes all the way to the root. Instead walk backwards from root to
leaf, like we also do during destruction.
|
|
|
|
|
|
|
|
| |
Make sure we always update root and parent references before
releasing the old root object.
This fixes some crashes under aggressive cycle collection, so
hopefully this will also fix bug #75351.
|
|
|
|
|
|
| |
Do not run finally blocks in generators on unclean shutdown (e.g.
caused by exit). This is consistent with how finally blocks outside
of generators behave.
|
|
|
|
|
|
|
|
|
| |
function)"
This reverts commit 816758eda2bcdd69ba505fb6bbb79124a7bf2254.
After this commit relative router scripts were resolved against
docroot rather than shell cwd.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
libtidy 5.6.0 remove the language option from the library, it is only
supported on cli. Prior to that, this option was not used in the
library. Thus, exclude the option presence from test.
|
| |
|
|
|
|
|
|
|
|
|
| |
SEND_UNPACK on iterators was duplicating references in-place,
which effectively leaks the original value and causes an off-by-one
refcount on the duplicated value.
Replace this with a deref, as an actual duplication is not even
needed in this case.
|
|
|
|
| |
This is a cherry-pick of 8a4532319dfae83ff16b2d2bbfeed062924c3c27.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The current doc states max ram for a test VM would be 7.5G, the
currently used container image has even less. This skip should be
revisited, as the available memory amount shifts. The way of checking
/proc/meminfo doesn't work reliably on containers at least, thus
skipping explicitly on Travis-CI makes sense.
|
|
|
|
|
| |
The test requires some untrivial amount of RAM. Added a simple check for
the system free RAM to avoid false positive fails.
|
|\
| |
| |
| |
| | |
* PHP-7.0:
2018
|
| |\
| | |
| | |
| | |
| | | |
* PHP-5.6:
2018
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.0:
2018
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
into PHP-7.1
* 'PHP-7.1-copyright' of https://github.com/kaplanlior/php-src:
Happy new year (Update copyright to 2018)
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| / /
| |/ / |
|
| |\ \
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The error messages are too discrepant and '-' is otherwise not allowed
by the parser.
|
| | |
| | |
| | |
| | | |
SqlServer requires parentheses to the TOP argument.
|
| | |
| | |
| | |
| | |
| | |
| | | |
mpz_setbit seems to have limit of INT_MAX * GMP_NUMB_BITS on
the number of bits supported, and will abort() if that limit
is exceeded.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.0:
[ci skip] update NEWS
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* 'PHP-7.1' of git.php.net:/php-src:
Update NEWS
Fixed bug #75571: Potential infinite loop in gdImageCreateFromGifCtx
Fix bug #74782: remove file name from output to avoid XSS
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
* PHP-7.0:
Update NEWS
Fixed bug #75571: Potential infinite loop in gdImageCreateFromGifCtx
Fix bug #74782: remove file name from output to avoid XSS
|
| | |\ \
| | | |/
| | | |
| | | |
| | | |
| | | |
| | | | |
* PHP-5.6:
Update NEWS
Fixed bug #75571: Potential infinite loop in gdImageCreateFromGifCtx
Fix bug #74782: remove file name from output to avoid XSS
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Due to a signedness confusion in `GetCode_` a corrupt GIF file can
trigger an infinite loop. Furthermore we make sure that a GIF without
any palette entries is treated as invalid *after* open palette entries
have been removed.
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
The string keys were not duplicated into persistent memory in this
case.
|
| | | |
|
| | | |
|