Memcached 1.6.12
Fixes a missing file from the 1.6.11 release.
Memcached 1.6.11
Bugfixes, potential performance improvements, improvements to logging. Includes some upstreamed changes for an upcoming feature.
Changes:
2.34.0
------
- Add support for HTTP/2 when building with libsoup3.
- Add support for CSS Scroll Snap.
- Add support for date and datetime-local input elements.
- Add support for display capture.
- Add support for ICC color management.
- Add support color-schemes CSS property.
- Add support for link preconnect when building with libsoup3.
- Add support for client side certificates when building with libsoup3.
- Add multi-track support to MSE media backend.
- Add new API to handle web process unresponsiveness.
- Add API to disable CORS on a web view for particular domains.
- Add new API to access/modify capture devices states.
- Add new API to configure the memory pressure handler.
- Removes the linux patches, since htop has native NetBSD support.
Changes since 3.0.5:
What's new in version 3.1.0
* Updated COPYING file to remove the PLPA exemption (appendix 2)
With this change the license is now GPLv2 without any additional wording.
* Improved default sort ordering
Note for users: This may lead to an inverted sort order on startup of
htop 3.1.0 compared to previous versions.
This is due to what is stored in your htoprc file. Solution: Press I
(to invert sort order).
This changed setting will be saved by htop on exit as long as it can
write to your htoprc file.
* The compile-time option to cater specifically for running htop as
setuid has been removed
* Add read-only option
This allows htop to be run in an non-intrusive fashion where it acts only
as a process viewer disabling all functions to manipulate system state.
Note: This is not a security feature!
* Move the code for handling the command line formatting related tasks
to be shared across all platforms
This means important features like stale binary/library highlighting
can now be available on all supported platforms.
* Make the EXE and COMM columns available on all platforms
All supported platforms have the name of the executable (EXE) and a
self-chosen thread/command name (COMM) available one way or the other.
Moving this column to be handled as a platform-independently available
information simplifies the markup of the command line.
* Introduce configuration file versioning and config_reader_min_version
Starting with this version the configuration file contains a version
identifying the minimum version of the configuration parser needed to
fully understand the configuration file format.
Old configuration file formats are automatically upgraded when
saving the config file (htoprc).
* Make the configuration parser friendlier to users (thanks to Bart Bakker)
With this change only settings that cannot be parsed properly are
reset to their defaults.
* Improve default display for systems with many CPUs
* Add the process ELAPSED time column
* Improve the process STATE column sorting
* Reworked handling resize and redrawing of the UI
* Fixed an issue where the LED meter mode could overflow allotted space
* Allow text mode Meters to span empty neighbors to the right
* Rescale graph meters when value of total changes
(thanks to Michael Schönitzer)
* Update generic process field display
Usually "uninteresting" values in columns like 1 thread, nice value
of 0, CPU and memory of 0%, idle/sleeping state, etc. are shown with
reduced intensity (dark grey)
* Option and key ("*") to collapse / expand all branches under PID 1
(and PID 2 if kernel threads are shown) (thanks to Krishna Chaitanya)
* Keep following a process when inverting the sort order, displaying
the help screen or hiding/unhiding userland threads.
If a thread is currently selected the selection is updated to point
to the thread's parent process. (thanks to Gonzalo, et.al.)
* Reorder process scanning to be performed before updating the display
of the meters in the header
* Always check the user for a process for any changes.
This affects multiple platforms that previously didn't correctly handle
the user field for a process to change at runtime (e.g. due to seteuid
or similar syscalls).
* Disable mouse option when support is unavailable
* Support curses libraries without ncurses mouse support
(thanks to Santhosh Raju)
* Support offline and hot-swapping of CPUs on all platforms
* Fix the CPU Meter for machines with more than 256 CPUs
* Supplemented the "show updated/deleted executables" feature (red basename)
to indicate when linked libraries were updated (yellow basename)
* Apply the stale binary highlighting for the EXE column in addition to
the command line field
* Add new combined Memory and Swap meter
* Implement bar and graph mode for NetworkIO Meter
(thanks to Michael F. Schönitzer)
* Rework TTY column to be more consistent across platforms
* Make the CWD column generally available on all platforms
(thanks to Santhosh Raju et. al.)
* Add Performance Co-Pilot (PCP) platform support
This is added via a separate pcp-htop(1) binary which provides remote host
analysis, new Meters for any PCP metric and new Columns for any PCP process
metric - see the pcp-htop(5) man page for further details.
(thanks to Sohaib Mohamed)
* Add Linux columns and key bindings for process autogroup identifier
and nice value
* Change available and used memory reporting on Linux to be based on
MemAvailable (Kernel 3.14+) (thanks to Chris Cheney and Tomas Wido)
* Add a new SysArchMeter showing kernel and platform information
(thanks to ahgamut)
* Linux memory usage explicitly treats tmpfs memory usage as shared memory
This is to make memory used by tmpfs visible as this cannot be freed
unlike normal filesystem cache data.
* Exclude zram devices when calculating DiskIO on Linux
* Use PATH lookup for systemctl in systemd meter (thanks to Scott Olson)
* Add native platform support for NetBSD
This allows htop to run on NetBSD without the need for active Linux
emulation of the procfs filesystem.
(thanks to Santhosh Raju and Nia Alarie)
* Add NetworkIO, DiskIO, CPU frequency, and battery meter support on NetBSD
(thanks to Nia Alarie)
* Fix NetBSD display of in-use and cached memory (thanks to Nia Alarie)
* Rework NetBSD CPU and memory accounting (thanks to Santhosh Raju)
* Fix NetBSD accounting of user and kernel threads (thanks to Santhosh Raju)
* Initial work to allow building with default libcurses on NetBSD
(thanks to Santhosh Raju)
* FreeBSD updates - implement process majflt and processor column values
* Add FreeBSD support for CPU frequency and temperature
* Fixes and cleanups for ZFS Meters and metrics
* Correctly color the ZFS ARC ratio (thanks to Ross Williams)
* Bugfixes related to CPU time display/calculations for darwin on M1 systems
(thanks to Alexander Momchilov)
* Harmonize the handling of multiple batteries across different platforms.
The system is now considered to run on AC if at least one power supply
marked as AC is found in the system.
Battery capacity is summed up over all batteries found.
This also changes the old behavior that batteries reported by the
system after the first AC adapter where sometimes ignored.
* Correctly handle multiple batteries on Darwin.
Resolves a possible memory leak on systems with multiple batteries.
* Handle Linux Shmem being part of Cached in the MemoryMeter
* Add SwapCached to the Linux swap meter (thanks to David Zarzycki)
* Convert process time to days if applicable (thanks to David Zarzycki)
* Always show the number of threads in the TaskMeter, even when threads
are not shown in the process list
* Fix Linux --drop-capabilities option handling
* Correctly detect failure to initialize Linux boottime
* Overhaul the Linux memory fields to partition them like free(1) now does
* Improve the Linux process I/O column values
* Rework the libsensors parsing on Linux
* Update the MemoryMeter to display shared memory
* Update OpenBSD platform - implement additional columns, scan LWP,
proper markup for STATE, show CPU frequency
* Fix the tree view on OpenBSD when hiding kernel threads
* Remove old InfoScreen lines before re-scanning (thanks to Øystein Hiåsen)
* Document historic naming of Light-Weight Processes column aka threads
* Improve user interaction when the last process entry is selected
* Draw the panel header on the TraceScreen (thanks to Youngjae Lee)
* Add mouse wheel scroll and fix mouse selection on the InfoScreen
(thanks to Youngjae Lee)
* Add a HugepageMeter and subtract hugepages from normal memory
* Display wide characters in LED meters and restore non-wide ncurses support
* Add command line option to drop Linux capabilities
* Support scheduler affinity on platforms beyond Linux
* Report on any failure to write the configuration file
* Cache stderr to be able to print assert messages.
These messages are shown in case htop terminates unexpectedly.
* Print current settings on crash
* Reset signal handlers on program exit
* Add configure script option to create a static htop binary
* Resolved longer-standing compilation issues on Solaris/Illumos
* Check for availability of set_escdelay in configure
(thanks to Stefan Polluks)
* Build system updates for autotools 2.70
3.9.7:
All Components
All bytecode is now compiled using the +deterministic compiler flag. This should eliminate the capture of some irrelevant build environment attributes in produced artifacts, improve consistency between builds, and reduce the file level diff between release artifacts.
Core Server
Enhancements
Classic queue shutdown now uses a much higher timeout (up to 10 minutes instead of 30 seconds).
In environments with many queues (especially mirrored queues) and many consumers this means that the chance of queue indices rebuilding after node restart is now substantially lower.
Prometheus Plugin
Enhancements
More configurability for metrics exposed via the Prometheus endpoint.
Shovel Plugin
Bug Fixes
Shovel URIs could be logged with credentials in some scenarios.
3.9.6:
Core Server
Bug Fixes
TLS information delivered in Proxy protocol header is now attached to connection metrics as if it was provided by a non-proxying client.
max_message_size had a one-off error in the validator.
mirroring_sync_batch_size was incorrectly validated as if it represented batch size in bytes. It represents batch size in number of messages, so the new default hard cap is now 1M (a very high number that's impractical)
Stream Plugin
Bug Fixes
Offset parameters were not stored correctly in some cases.
Partitions list order is now stable.
When stream clients close connections abruptly, publisher and consumer metrics get cleaned up correctly.
Management Plugin
Enhancements
Stream publishers are now listed on the individual stream page.
Counters have been added to the tiles of several sections on detail pages.
3.9.5:
Core Server
Bug Fixes
Virtual host metadata (description, tags) was not imported from definitions.
Reduced unnecessary debug logging from streams.
AWS Peer Discovery Plugin
Enhancements
AWS API calls are now retried multiple times.
Contributed by AWS.
Management Plugin
Enhancements
PUT /api/vhosts/{name} now can update metadata (tags and descriptions) for existing virtual hosts.
3.9.4:
Core Server
Enhancements
New Prometheus metrics for alarms
Nodes will now use four more environment variables, if set: RABBITMQ_DEFAULT_USER (overrides default_user in rabbitmq.conf), RABBITMQ_DEFAULT_PASS (overrides default_pass), RABBITMQ_DEFAULT_VHOST (overrides default_vhost) and RABBITMQ_ERLANG_COOKIE (sets shared authentication secret value). These variables are not recommended to be used in production but can be the only realistic option in some environment, such as service containers, ECS, and so on. Most users should continue using rabbitmq.conf and a securely generated local cookie file.
Definitions now can be imported from different sources, including those provided by plugins. Original local filesystem source is still supported in a backwards-compatible way.
3.9.3:
Core Server
Bug Fixes
Queues that had messages with per-message TTL in them could fail to recover their indices after a restart.
JSON logging could fail with an exception when a logged event included epoch-based timestamp value.
JSON logging now uses integers (as opposed to floats) to represent epoch-based timestamps
Enhancements
RabbitMQ application no longer reports the stopping event to systemd. This was counterproductive when the application was stopped but the runtime (Erlang VM) was kept running, e.g. via rabbitmqctl stop_app or by the pause minority partition handling strategy.
Now systemd service monitoring will recognize a node as stopped only when the runtime is stopped, which is usually the behavior operators expect.
3.9.2:
CLI Tools
Bug Fixes
rabbitmq-upgrade drain and rabbitmq-upgrade revive now log warning and info level instead of alert.
Shovel Plugin
Bug Fixes
Multiple Shovels could be started in some cases involving node restarts of failures.
Federation Plugin
Bug Fixes
Multiple Federation links could be started in some cases involving node restarts of failures.
3.9.1:
Core Server
Bug Fixes
Clients that used global QoS prefetch (deprecated as of 3.9.0) ran into an exception when acknowledging deliveries.
Improved resiliency of stream coordinator in certain conditions.
Nodes failed to start when hostname contained non-ASCII (broader Unicode) characters.
CLI Tools
Bug Fixes
rabbitmq-diagnostics stream_status fails with an exception when the --tracking option was used.
rabbitmq-diagnostics stream_status used an outdated documentation guide link.
RabbitMQ Erlang Client
Bug Fixes
New releases of the client are again published to Hex.pm.
connection_timeout was adjusted to avoid a confusing warning.
Corrected a typo in direct connection net tick time adjustment.
3.9.0:
Streams
Erlang 24 Support
Kubernetes
Logging in JSON
5.0.13 2021-09-24
=================
Added knowledge of Python versions 3.6.15 and 3.7.12.
However the main motivation was to impove packaging to handle administration
of the 3 different branches or dialects of Python 2.4-2.7, 3.1-3.2, 3.3-3.5, and 3.6+
Restrict wheel packaging for Python 3 only.
Use the wheel for only the 3.x and newer version of Python.
Use eggs for 2.x versions (and others as well).
3.3.2
- Fixed cancellation problem on asyncio where level-triggered cancellation for **all** parent
cancel scopes would not resume after exiting a shielded nested scope
Stellarium v0.21.2
The major changes of this version:
Annual aberration correction. Planet positions are finally very accurate!
Bookmarks replaced by Observation Lists
Politically neutral geonames
Right-click opens plugin configuration
Improved computation of rising, transit, setting times
“Goto next twilight” functionality
Two new Greek skycultures
Updated Mul-Apin skyculture with new artwork
Improved fidelity of Lunar eclipses
Fixed display of stellar proper motion
Many fixes in core and plugins
2020-10-14 Alex Tutubalin <lexa@lexa.ru>
* LibRaw 0.20.2
Reverted 0.20.1 change:
- const buffer for open_buffer() and open_bayer() calls
Because of 0.20.0 ABI break
2020-10-14 Alex Tutubalin <lexa@lexa.ru>
* LibRaw 0.20.1
* Improvements:
- exif callback is called on EXIF GPS and EXIF Interop IFDs
- open_bayer call documented
- Canon (ColorDatsSubver==32): parse Specular White instead of hardcoded value
* Fixes for normal files processing:
- Olympus XZ-1: do not provide linear_max (it is wrong in metadata)
- Nikon Z cameras: added space in camera list
- raw-identify: fixed wb-preset print
- Pentax Optio 33WR: maker index was incorrect
- dcraw_emu: corrected help line for -6 option.
- raw-identify: corrected range check for color matrices print
- use_camera_matrix option: fixed a bug introduced when making
compiler more happy.
* Fixes for damaged/special crafted files processing:
- Fix for truncated CR3 files parsing
- DNG metadata merger: all color loops are limited to MIN(4,colors)
- Check for marings: should be less than raw image size
- Check for xmpdata present in Samsung Lens ID assignment
- Check for column range in leaf_hdr decoder
- Additional checks in Hasselblad model parser
- Fuji rotate: better limits check
- DNG files: limit tiff_samples
* Not fixes, but makes ASAN/compilers/etc happy:
- corrected GPS EXIF output
- const buffer for open_buffer() and open_bayer() calls
2020-07-23 Alex Tutubalin <lexa@lexa.ru>
* LibRaw 0.20
== Camera Format support ==
Canon CR3
GoPro (via GPR SDK)
Panasonic 14-bit
Fujifilm compressed/16bit
Rapsberry Pi RAW+JPEG format (if USE_6BY9RPI defined)
Foveon X3F support changed: it is supported only if USE_X3FTOOLS defined
at build (see below for 'Imported code policy changed')
== Camera support (+59, 1131 total) ==
Canon: PowerShot G5 X Mark II, G7 X Mark III, SX70 HS,
EOS R, EOS RP, EOS 90D, EOS 250D, EOS M6 Mark II, EOS M50, EOS M200
EOS 1DX Mark III (lossless files only)
DJI Mavic Air, Osmo Action
FujiFilm GFX 100, X-A7, X-Pro3, X100V, X-T4 (uncompressed/lossless compressed only), X-T200
GoPro Fusion, HERO5, HERO6, HERO7, HERO8
Hasselblad L1D-20c, X1D II 50C
Leica D-LUX7, Q-P, Q2, V-LUX5, C-Lux / CAM-DC25, SL2, M10 Monochrom
Nikon D780, Z50, P950
Olympus TG-6, E-M5 Mark III, E-PL10, E-M1 Mark III,
Panasonic DC-FZ1000 II, DC-G90, DC-S1, DC-S1R, DC-S1H, DC-TZ95
PhaseOne IQ4 150MP
Ricoh GR III
Sony A7R IV, A9 II, ILCE-6100, ILCE-6600, RX0 II, RX100 VII
Zenit M
also multiple smartphones (the tested ones are listed in LibRaw::cameraList)
== Source code re-arranged ==
* dcraw.c is not used in the generation and build processes
* dcraw_common.cpp and libraw_cxx.cpp are split into multiple code chunks
placed in separate subfolders (decoders/ for raw data decoders,
metadata/ for metadata parsers, etc)
* dcraw_common.cpp and libraw_cxx.cpp remain to preserve existing
build environments (these files are now just a bunch of #include directives).
* It is possible to build LibRaw
a)without postprocessing functions (dcraw_process() and called function)
b)without postprocessing and LibRaw::raw2image() call (and called function).
It may be useful to reduce library memory/code footprint.
See Makefile.devel.nopp and Makefile.devel.noppr2i for the list of source
files needed to build reduced/stripped library.
== Normalized make/model ==
There is a huge number of identical cameras sold under different names,
depending on the market (e.g. multiple Panasonic or Canon models)
and even some identical cameras sold under different brands
(Panasonic -> Leica, Sony -> Hasselblad).
To reduce clutter, a normalization mechanism has been implemented in LibRaw:
In imgdata.idata:
char normalized_make[64]; - primary vendor name (e.g. Panasonic for
Leica re-branded cameras)
char normalized_model[64]; - primary camera model name
unsigned maker_index; - primary vendor name in indexed form (enum
LibRaw_cameramaker_index, LIBRAW_CAMERAMAKER_* constant).
These fields are always filled upon LibRaw::open_file()/open_buffer() calls.
const char* LibRaw::cameramakeridx2maker(int index): converts maker_index
to normalized_make.
We recommend that you use these normalized names in a variety of data tables
(color profiles, etc.) to reduce the number of duplicate entries.
New vendor index values will be added strictly to the end of the
LibRaw_cameramaker_index table, ensuring that the numbers assigned to
vendors that are already known to LibRaw will not change.
== DNG frame selection ==
DNG frames selection code re-worked:
- by default all frames w/ the NewSubfileType tag equal to 0
(high-res image) are added to the list of available images (selection
performed via imgdata.params.shot_select field, as usual)
- the special case for Fuju SuperCCD (SamplesPerPixel == 2) works as
before: shot_select=1 will extract second sub-image.
- Additional flags to imgdata.params.raw_processing_options:
LIBRAW_PROCESSING_DNG_ADD_ENHANCED - will add Enhanced DNG frame
(NewSubfileType == 16) to the list of available frames
LIBRAW_PROCESSING_DNG_ADD_PREVIEWS - will add previews
(NewSubfileType == 1) to the list.
- By default, DNG frames are not reordered and are available in same order
as in DNG (LibRaw traverses IFD/Sub-IFD trees in deep-first order).
To prioritize the largest image, set LIBRAW_PROCESSING_DNG_PREFER_LARGEST_IMAGE
bit in imgdata.params.raw_processing_options.
- DNG Stage2/Stage3 processing via DNG SDK (request via flags in
raw_processing_options)
== Imported code policy disclaimer ==
We've changed the policy regarding 3rd party code imported into LibRaw.
We (like other authors of open-source RAW parsers) gladly import support
code for various RAW formats from other projects (if the license allows it).
This is done to expand camera support.
Unfortunately, not all imported code can tolerate truncated or otherwise
damaged raw files, as well as arbitrary conditions or arbitrary data;
not all authors handle rejecting unexpected input well.
LibRaw is now widely used in various projects, including ImageMagick, which,
in turn, is often used on web sites to process any input images, including
arbitrary data from unknown users.
This opens up wide possibilities for exploiting the various vulnerabilities
present in the code borrowed from other projects into LibRaw. In order to
avoid such security risks, - the borrowed code will no longer compile
by default.
We are not able to support it in general case, and the authors refuse
to add code to reject unexpected input.
Thus, if you use some kind of camera for which the support is disabled
by default, you need to recompile LibRaw for your specific case.
Formats currently affected:
X3F (Foveon) file format.
Code is imported from Kalpanika X3F tools: https://github.com/Kalpanika/x3f
To turn the support on, define USE_X3FTOOLS
Rapsberry Pi RAW+JPEG format.
Code is imported from https://github.com/6by9/dcraw/,
To turn the support on, define USE_6BY9RPI
Format support is indicated via LibRaw::capabilities() call with flags:
LIBRAW_CAPS_X3FTOOLS - Foveon support
LIBRAW_CAPS_RPI6BY9 - RPi RAW+JPEG support
== GoPro .gpr format support ==
GoPro format supported via open-source GPR SDK
See README.GoPro.txt for details.
== Windows support/Windows unicode (wchar_t*) filenames support ==
* (old) LibRaw's WIN32 external define split into 3 defines to fine tune
compiler/api compatibility:
LIBRAW_WIN32_DLLDEFS - use to compile DLLs (__dllimport/__dllexport attributes)
LIBRAW_WIN32_UNICODEPATHS - indicates that runtime has calls/datatypes for wchar_t filenames
LIBRAW_WIN32_CALLS - use Win32 calls where appropriative (binary mode for files, LibRaw_windows_datastream, _snprintf instead of snprintf, etc).
If the (old) WIN32 macro is defined at compile time, all three new defines are defined in libraw.h
If not, these defines are defined based on compiler version/libc++ defines
* LibRaw::open_file(wchar_t*) is always compiled in under Windows, but
if LIBRAW_WIN32_UNICODEPATHS (see above) is not defined, this call will
return LIBRAW_NOT_IMPLEMENTED.
Use (LibRaw::capabilities() & LIBRAW_CAPS_UNICODEPATHS) on runtime
to check that this call was really implemented (or check for #ifdef LIBRAW_WIN32_UNICODEPATHS after #include <libraw.h>)
== LibRaw*datastream simplified ==
* tempbuffer_open, subfile_open are not used, so removed from
LibRaw_abstract_datastream and derived classes.
* jpeg_src() call implemented using ->read() call and own buffering
(16k buffer).
* buffering_off() call added. It should be used in derived classes
to switch from buffered reads to unbuffered.
== minor/unsorted changes ==
* new flag LIBRAW_WARN_DNGSDK_PROCESSED to indicate decoder used
* LibRaw::open() call, max_buf_size special meaning:
== 1 => open using bigfile_datastream
== 2 => open using file_datastream
* Add support for zlib during configure
* Fixed multiple problems found by OSS-Fuzz
* Lots of changes in imgdata.makernotes (hope someone will document it)
* DNG SDK could be used (if enabled) to unpack multi-image DNG files.
* DNG whitelevel calculated via BitsPerSample if not set via tags.
* DNG: support for LinearDNG w/ BlackLevelRepeat.. pattern
* Generic Arri camera format replaced w/ list of specific camera models in supported cameras list.
* new samples/rawtextdump sample: allows one to dump (small selection) of RAW data in text format.
* samples/raw-identify:
* +M/-M params (same as in dcraw_emu)
* -L <file-w-filelist> parameter to get file list from a file
* -m paramerer to use mmap'ed IO.
* -t parameter for timing
* samples/dcraw_emu: fixed +M handling
* better support for Nikon Coolscan 16-bit NEF files.
* Visual Studio project files: re-generated to .vcxproj (Visual Studio 2019), different
intermediate folders for different sub-projects to allow 1-step rebuild.
* imgdata.makernotes...cameraspecific: removed the vendor name prefix from variables.
* Bayer images: ensure that even margins have the same COLOR() for both the active sensor area and the full sensor area.
* raw processing flag bit LIBRAW_PROCESSING_CHECK_DNG_ILLUMINANT inverted and renamed to
LIBRAW_PROCESSING_DONT_CHECK_DNG_ILLUMINANT. If not set, DNG illuminant will be checked.
* New libraw_decoder_t flags:
LIBRAW_DECODER_FLATDATA - in-file data could be used as is (if byte order matches), e.g. via mmap()
LIBRAW_DECODER_FLAT_BG2_SWAPPED - special flag for Sony ARQ: indicates R-G-G2-B channel
order in 4-color data
* Camera-recorded image crop data is parsed into imgdata.sizes.raw_inset_crop structure:
ctop,cleft,cwidth,cheight - crop size.
aspect - LibRawImageAspects enum (3to2, 4to3, etc)
* New define LIBRAW_NO_WINSOCK2 to not include winsock2.h on compile
* New processing flag LIBRAW_PROCESSING_PROVIDE_NONSTANDARD_WB
If set (default is not), and when applicable, color.cam_mul[] and
color.WB_Coeffs/WBCT_Coeffs will contain WB settings for a non-standard
workflow.
Right now only Sony DSC-F828 is affected: camera-recorded white balance
can't be directly applied to raw data because WB is for RGB, while raw
data is RGBE.
* New processing flag: LIBRAW_PROCESSING_CAMERAWB_FALLBACK_TO_DAYLIGHT
If set (default is not), LibRaw::dcraw_process() will fallback to
daylight WB (excluding some very specific cases like Canon D30).
This is how LibRaw 0.19 (and older) works.
If not set: LibRaw::dcraw_process() will fallback to calculated auto WB if
camera WB is requested, but appropriate white balance was not found in
metadata.
* Google changes cherry-picked (thanks to Jamie Pinheiro)
* speedup: ppg interpolate: const loop invariant
* Bugs fixed
-Fixed several UBs found by OSS Fuzz
-Fixed several problems found by other fuzzers.
- Thumbnail size range check (CVE-2020-15503)
Thanks to Jennifer Gehrke of Recurity Labs GmbH for problem report.
- fixed possible overflows in canon and sigma makernotes parsers
- fixed possible buffer overrun in crx (cr3) decoder
- fixed memory leak in crx decoder (if compiled with LIBRAW_NO_CR3_MEMPOOL)
- fixed possible overrun in Sony SRF and SR2 metadata parsers
* Fixed typo in longitude (member of parsed GPS structure), update required for code that uses it.
