[FEATURE REQUEST]Disable TIFF print statements in release build

There are a lot of TIFF warning messages when loading files that have issues.  Can these be disabled for release builds?
This is what is being printed to the console when scanning drives for images:
IFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFReadDirectory: Warning, Unknown field with tag 34016 (0x84e0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34017 (0x84e1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34018 (0x84e2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34019 (0x84e3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34020 (0x84e4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34021 (0x84e5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34022 (0x84e6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34023 (0x84e7) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34024 (0x84e8) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34025 (0x84e9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34026 (0x84ea) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34027 (0x84eb) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34028 (0x84ec) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34029 (0x84ed) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34030 (0x84ee) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34031 (0x84ef) encountered.
_TIFFVSetField: foo: Null count for "Tag 34022" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34025" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34026" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34031" (type 1, writecount -3, passcount 1).
TIFFReadDirectory: Warning, Unknown field with tag 34016 (0x84e0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34017 (0x84e1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34018 (0x84e2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34019 (0x84e3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34020 (0x84e4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34021 (0x84e5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34022 (0x84e6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34023 (0x84e7) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34024 (0x84e8) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34025 (0x84e9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34026 (0x84ea) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34027 (0x84eb) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34028 (0x84ec) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34029 (0x84ed) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34030 (0x84ee) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34031 (0x84ef) encountered.
_TIFFVSetField: foo: Null count for "Tag 34022" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34025" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34026" (type 1, writecount -3, passcount 1).
_TIFFVSetField: foo: Null count for "Tag 34031" (type 1, writecount -3, passcount 1).
TIFFReadDirectory: Warning, Unknown field with tag 59932 (0xea1c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 59932 (0xea1c) encountered.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFReadDirectory: Warning, Unknown field with tag 34821 (0x8805) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 34821 (0x8805) encountered.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.
TIFFFetchNormalTag: Warning, Incompatible type for "RichTIFFIPTC"; tag ignored.

Ignore.  I had to use a separate TIFF loader because OIIO cannot read TIFF files from memory.

Reopening, this is a legit issue, and I see what's going wrong now.

Are you saying "ignore the fact that OIIO does this, because ultimately I'm not going to use the OIIO code for this purpose?"
Or are you saying "never mind, this wasn't OIIO code making the calls that produced these messages"?
I'm kind of suspecting the latter, because I do install error handlers and looking at the libtiff code, I think they should be working to not echo these messages. But if it's OIIO code making those TIFF calls, let me know and I'll poke around the error handlers more.

I am not using OIIO for reading TIFF images because it does not support
reading from memory, which I need.  I disabled the error reporting in my
local version.
I can use OIIO for TIFF reading to test this, if you like.
-Doug

In my local version of the TIFF library, specifically.
-Doug

I think it should work already, I do install error and warning handlers.

Is there an interface to disable them?  Like a —quiet flag?--
-Doug

No, I mean, the handlers already suppress them from printing, but put them in a place where, when OIIO needs to issue an error of its own, they can be incorporated into the error message.
No OIIO operation should print to the console. ImageInput::open(), for example, returns a bool for whether it succeeded, and if you want a message, you can call ImageInput::geterror(), and what you get back from that will contain (in part) the libtiff error message that was originally suppressed.

From the point of view of an OIIO-calling app, the only errors that will print are the ones you retrieve from geterror() and print yourself.

Excellent.  Just the way it should be :)
I think this can be closed now.
-Doug

Closing. I'm taking a quick look at the TIFF proxy case to see if it's easy to add.


Fix command to create a backend plugin

Hey, I just made a Pull Request!
Fix command to create a backend plugin
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

np


Need to uninstall OneNote 2016

Hello,
We have many clients that have OneNote 2016 installed along with O365 suite. However, our customer wants to use OneNote for Windows 10 and do not want OneNote 2016.
We can configure xml file to exclude OneNote from installing on new clients. However, how to uninstall OneNote 2016 on the clients that have already installed it along with O365 suite.
Thanks,
Upendra

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2319f44f-09fc-2649-2667-58fa159e3151
Version Independent ID: 0b6c5c52-edaa-436d-95dd-0943d0b0c303
Content: Deployment guide for OneNote
Content Source: DeployOffice/deployment-guide-onenote.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@Upendra365 Scheck out this blog post for an explanation how to achieve that: https://techcommunity.microsoft.com/t5/office-365-blog/excluding-and-re-including-applications-within-the-office-365/ba-p/1250367. We will backport some information into the article you mentioned, thanks for flagging.
@DHB-MSFT Can be closed then


Create sandbox for host file system access

Add --mount parameter for "whitelisting" guest_paths and defining their respective filesystem paths on the host FS
Add UhyveFileMap structure, unit and integration tests
Implement sandbox for open() and unlink() syscall

A few points that could be further worked are unit tests, handling more of the parsing using the clap library directly and performance optimizations.

Fixes https://github.com/hermit-os/uhyve/issues/767

Tasks that should be done:

Unit tests for UhyveFileMap structure. (Nevertheless, a review would be appreciated.)

Additional ideas:

Linux-only configuration option for storing any files that were not explicitly defined in /tmp.
Option that allows explicitly locks down filesystem access completely, instead of giving full host access if no --mount parameter exists.

Addressing the first round of review comments in https://github.com/n0toose/uhyve/commits/sandbox-uhyvefilemap-review-round-1
Will rebase shortly and force-push to sandbox-uhyvefilemap.

Currently working on a proof-of-concept for temporary files tracked under this branch, so as to completely remove unfettered host file system access: https://github.com/n0toose/uhyve/tree/sandbox-uhyvefilemap-tempfile
I'll squash the work done and move it under sandbox-uhyvefilemap once it is done to keep the sandbox-uhyvefilemap tree clean.

My approach so far has been to create a temporary directory and perhaps append the file path to UhyveFileMap, but, as I kind of suspected, this may be an awful idea.
I'm using the crate tempfile: https://docs.rs/tempfile/latest/tempfile/

tempfile will (almost) never fail to cleanup temporary resources. However TempDir and NamedTempFile will fail if their destructors don’t run.

Using a TempDir seems like a solid approach, because it also allows us to use the created path with e.g. Landlock (which can only whitelist existing paths and not append any new paths in retrospect) and reopen files. However, other processes have the ability to write to it, so there's not a considerable security benefit compared to whitelisting /tmp. Which brings me to trusting /tmp...

Security
In the presence of pathological temporary file cleaner, relying on file paths is unsafe because a temporary file cleaner could delete the temporary file which an attacker could then replace.

(Source: https://docs.rs/tempfile/latest/tempfile/#security)
The middle-ground solution is to allow the kernel to write into a file, but not store it internally if it needs to be reused at a later point.

Creating a directory that remains "stable"

I'll figure out how / if this can be sufficiently prevented: https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File

TODO: Add sandbox to unlink.

@jounathaen I understand that this feature could use some additional work, but would it be possible to get a review (with the goal of having it merged upstream soon)? I can hide everything behind a feature flag.
I admittedly struggled over the past two days because of the need to rebase across separate branches for features like benchmarks and using main's latest features - this would help me speed things up with the most urgent priorities and the tasks that will come after them on top of the current design.

A flaw of my current approach - which is currently not affecting us, as Uhyve is not "generally used for directories" - is that each file and directory has to be mapped by the user.
I devised a method that recursively "searches" the parent directories until it finds a mapped parent directory, and then adds all directories and the file itself in the map: https://github.com/n0toose/uhyve/tree/sandbox-uhyvefilemap-directories
This method is not ready yet. This process takes place during an open() and is costly - a cost that might be saved if we add preexisting directories and files during UhyveFileMap::new. Benchmarks are necessary to demonstrate the costliness and justify this method.
https://github.com/hermit-os/uhyve/commit/ae00483140b16af423c4ad107dc5d1a2e28c7a11#diff-eccc3941b4969c091455caa35d7e7aee0ee82ff99ab85eb7cc713df9adc4e2cdR107

A flaw of my current approach - which is currently not affecting us, as Uhyve is not "generally used for directories" and processes files under /root/ so far - is that each file and directory has to be mapped by the user.
I devised a method that recursively "searches" the parent directories until it finds a mapped parent directory, and then adds all directories and the file itself in the map: https://github.com/n0toose/uhyve/tree/sandbox-uhyvefilemap-directories

I don't fully understand, what you mean by "adds all directories and the file itself in the map"? I think the map should not be altered once created (besides when new files/directories are created from the kernel). I see a lot of issues with dead entries in the map if this route is taken.

This method is not ready yet. This process takes place during an open() and is costly - a cost that might be saved if we add preexisting directories and files during UhyveFileMap::new. Benchmarks are necessary to demonstrate the costliness and justify this method.

I am not sure if this is really that costly. How deep are directories typically nested? 10 entries deep? 10 string splits and lookups in a HashMap should not create a lot of overhead.

I don't fully understand, what you mean by "adds all directories and the file itself in the map"? I think the map should not be altered once created (besides when new files/directories are created from the kernel). I see a lot of issues with dead entries in the map if this route is taken.

Hm, I see. We could just check for the parent directory every time a file is opened then - the modifications should be minor. Do you think that we should check for child directories / files during the creation of the UhyveFileMap?

this rebase will be fun :D
adding you as a co-author to relevant commits

I don't fully understand, what you mean by "adds all directories and the file itself in the map"? I think the map should not be altered once created (besides when new files/directories are created from the kernel). I see a lot of issues with dead entries in the map if this route is taken.

Hm, I see. We could just check for the parent directory every time a file is opened then - the modifications should be minor. Do you think that we should check for child directories / files during the creation of the UhyveFileMap?

No, why should we? A recursive lookup will be just fine. Also, this allows to reflect file/directory changes outside uhyve in the kernel during runtime.

No, why should we? A recursive lookup will be just fine. Also, this allows to reflect file/directory changes outside uhyve in the kernel during runtime.

Well, you have a point (plus, this does make my job much easier, so even less of a reason to object, and it can be revisited later :D). I'll integrate it once the initial changes get an OK and once I'm done with rebasing and fixing up a few additional details that I've noticed.

I pushed a new feature for directory support for UhyveFileMap. This should be ready for review.
A problem with the current implementation is that open, in the way that we use it provides a relative path that contains the file name foo.txt, which is mostly equivalent to /root/foo.txt. The UhyveFileMap sees those two files as "separate". If /root/ is whitelisted, and the user attempts to open foo.txt (which is basically /root/foo.txt), the open will fail. I attempted to use tests to "document" its behavior. As things are right now, this approach is better than nothing, and I think that it's merge-able as it is "more production-ready than a hypervisor that provides full host system access", despite the risk of confusion for the user.
However, the current design needs to be reworked with the answers to the following questions in mind:

If the guest_path does not contain an explicit absolute path, do we assume that the file is in /root and prepend it ourselves? (A previous early design took this into account - together with a virtiofsd-like "shared directory", but was removed after discussions. Now feels like a good time to bring it up again.)
Should we "get the current working directory" from the UhyveVm to compare the entire path against UhyveFileMap? How do other implementations handle it?
Do we need to make the virtual machine "aware" of what we have mapped, and let the VM reject specific paths? Are "bad" maps (what is "bad"? everything outside of /root?) capable of breaking things, or is the flexibility of being able to map everything to everything advantageous (e.g. to /etc/...)?

https://man7.org/linux/man-pages/man7/path_resolution.7.html

If the pathname does not start with the '/' character, the
starting lookup directory of the resolution process is the
current working directory of the process — or in the case of
openat(2)-style system calls, the dfd argument (or the current
working directory if AT_FDCWD is passed as the dfd
The current working directory is inherited from the parent, and
can be changed by use of the chdir(2) system call.


aarch64: Remove useless _curr_cpu struct

small fix suggested by @jharris-intel.
~Please note that if this is merged before #32854 we will have to fix the userspace PR because get_cpu now needs 3 registers to be clobbered.~

@nashif can you merge this?


Bug when using current date in maxDate and using current datetime in defaultDate

https://codepen.io/Renlid/pen/XWdQaqd
When using "today" (or a "Y-m-d" string representing the current date) as config option value for maxDate, flatpickr does no longer accept the defaultDate if it is set to current datetime, because flatpickr seems to create a "max date-time" of {maxDate} 00:00:00 instead of {maxDate} 23:59:59.
Any time/hour "inside" maxDate should be allowed, or please do change the doc to "exclusive" instead of "inclusive".
e.g. if maxDate is "2020-09-28" then defaultDate of "2020-09-28 15:25:00" should be allowed. All the more since manually setting this value inside flatpickr is allowed. It just bugs for defaultDate.
Also, setting a full datetime in maxDate as a workaround does not work, since flatpickr only accepts a date here.
However, setting new Date() in maxDate works partially, in the sense that the defaultDate works but we can't select a "later" hour/time of today inside flatpickr.
If the time part of a Date object is used inside flatpickr for the maxDate option, then shouldn't you also allow users to specify a string datetime ("Y-m-d H:i:s"), for consistency?
If someone does have a workaround for this, please do tell (different than passing a manually created Date object containing current date and "23:59").
Your Environment

flatpickr version used: 4.6.6
Browser name and version: Chrome 85.0.4183.121
OS and version: Windows 10

Same bug when using enable Option.
Your Environment
flatpickr version used: 4.6.6
Browser name and version: Firefox 84.0.2
OS and version: Ubuntu 20.04

Same bug when using enable Option.
Your Environment
flatpickr version used: 4.6.6
Browser name and version: Firefox 84.0.2
OS and version: Ubuntu 20.04


Include synthetic test manifests in test logs

These checks are built up internally, but including them in the test logs will guard against regressions in the check code.  Basically, there will be two layers of checks.

Implemented in 148836f.


Update Composer dependencies (2023-11-24-00-14)

Visual regression test passed!
View the visual regression test report


Simplify deployment to servers by using virtual environments.

Partially fixes #12 . Should we containerize converter to docker though?

Tested the code - seems fine to me. Don't see any issues with merging this.


Multipart request gets aborted.

I am testing my REST API using Supertest. I use Mocha for testing and Multiparty for form parsing.
My test is :
  it('Multipart request with two files, one right', function(done) {
    request(app)
      .post('/api/Pictures/upload')
      .set('Accept', 'application/json')
      .set('Content-Type','multipart/form-data')
      .set('connection', 'keep-alive')
      .field('dailyThemesId','1')
      .field('themeId','1')
      .field('pictureTimeZone','GTM+1')
      .field('pictureText','Muy porno')
      .attach('file', './test/File/fileSuperSmall.mp4', 'video.mp4')
      .attach('video', './test/File/fileSuperSmall.mp4', 'video.mp4')
      .query({ 'access_token': token1})
      .end(function(err, res) {
          if( err) {
            console.log(err);
          } else {
            console.log(res.body);
          }
          done();
    });
  });

On my Multiparty the next error is emitted.
[Error: Request aborted]

The  error returned by SuperTest is.
{ [Error: socket hang up] code: 'ECONNRESET', response: undefined }

As far as I debug it it looks like Supertest is aborting the request so the errors raise.  As far as I know the request should not be aborted unless .abort() is called. Please, ¿Could someone give an insight of this behaviour?

I got this error when the path is wrong. The path should be specified from where you run your tests

I could only get this working with a full path, nothing relative seemed to work :(

I think you could use
.attach("file", ${__dirname}/sample.txt)

@francescobarbera yes, surely, but the example in the docs show this -

https://github.com/visionmedia/supertest
And there was mention in other issues that the file was going to be loaded relative to the location from where the test was being run. The attach code is here in superagent:
https://github.com/visionmedia/superagent/blob/84206c75214e20bbc688d0645880696ecd773c27/src/node/index.js#L246-L273
And readStream appears to just be using the raw file param-

export const createMusicTest = async (
  app: INestApplication,
  token: string,
  optionalData: {
    title?: string;
    description?: string;
    hashtags?: string[];
    duration?: number;
    explicit?: boolean;
    publishStatus?: MUSIC_STATUS;
    bpm?: number;
    vocal?: boolean;
    vocalLanguage?: string;
    keyScaleId?: number;
  } = {
    title: 'title',
    description: 'description',
    hashtags: ['jazz', 'hiphop'],
    duration: Math.floor(Math.random() * 100),
    explicit: Math.random() < 0.5,
    publishStatus: 'PUBLIC',
    bpm: Math.floor(Math.random() * 9999),
    vocal: Math.random() < 0.5,
    vocalLanguage: 'ja',
    keyScaleId: 1,
  },
) => {
  const {
    title,
    description,
    hashtags,
    duration,
    explicit,
    publishStatus,
    bpm,
    vocal,
    vocalLanguage,
    keyScaleId,
  } = optionalData;
  const folder = __dirname;

  const sampleAudio = {
    fileName: '/asset/audio/sampleAudio.mp3',
    mimetype: 'audio/mpeg',
  };

  const sampleImage = {
    fileName: '/asset/image/sampleImage.png',
    mimetype: 'image/png',
  };

  const query = `
    mutation($mp3: Upload!,$artWork: Upload!) {
      createMusic(
        description: \"${description}\"
        duration: ${duration}
        explicit: ${explicit}
        hashtags: \["${hashtags}"]\
        publishStatus: ${publishStatus}
        title: \"${title}\"
        vocal: ${vocal}
        vocalLanguage: \"${vocalLanguage}\"
        bpm: ${bpm}
        keyScaleId: ${keyScaleId}
        mp3File: $mp3
        artWork: $artWork
      ) {
        id
        title
        description
        explicit
        bpm
      }
    }`;
  try {
    const res = await request(app.getHttpServer())
      .post('/graphql')
      .set('Authorization', `Bearer ${token}`)
      .field(
        'operations',
        JSON.stringify({
          query,
          variables: {
            mp3: null,
            artWork: null,
          },
        }),
      )
      .field(
        'map',
        JSON.stringify({
          audio: ['variables.mp3'],
          image: ['variables.artWork'],
        }),
      )
      .attach('audio', folder + sampleAudio.fileName)
      .attach('image', folder + sampleImage.fileName);
    return {
      data: res.body.data.createMusic as Music,
      errors: res.body.errors as GraphQLError,
    };
  } catch (e) {
    console.log('Errr======', e);
    throw e;
  }
};

In graphql , if I upload 1 file , that's ok , but multiple file will get error (aborted without any message )
I'm using nestjs + graphql for upload file

Resolving the file path worked for me.
  const filePath = "./sample-asset/image.jpg"  ❌
  const filePath = path.resolve(__dirname, 'sample-asset', 'image.jpg'); ✅ // remember to import path from 'path'

  const response = await request
    .post(`${BASE_URL}/upload-media/`)
    .set('Authorization', `Bearer ${token}`)
    .attach('file', filePath, {contentType: 'multipart/form-data'})
    .expect(HTTPStatus.OK);

   //*****************

Just an advice, be careful when explain an example code, because you have written an inappropriate text.
It is funny, but now it is on the supertest issues history.

I think you could use
.attach("file", `${__dirname}/sample.txt`)

Yepp . Solved my issue !


How do I store a dataframe for future use?

we will need to conform to a schema to use HDF. You are almost certainly safer to store to pickle for now
https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.to_pickle.html

Well. OK. To write to HDF5, we'd probably either find a way of serializing the geometry column, or drop it. The latter:
roi.drop(columns='geometry').to_hdf('roi.h5', key='roi')

For now: pickle or geopackages. We have not come up with an hdf schema yet.
I would think all it takes would be converting some of the data types. Is
this a priority for you?
On Sun, May 8, 2022, 09:12 Rilee @.***> wrote:

[image: image]
https://user-images.githubusercontent.com/6934724/167305015-8e973489-698c-4ddd-9fdc-7b7be729258f.png
—
Reply to this email directly, view it on GitHub
https://github.com/SpatioTemporal/STAREPandas/issues/94, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQHY2Z2N6MSCERGCWKFODLVI7RYFANCNFSM5VMEDFZQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


What is the buffer in time between when a timeslot is added by the admin and the users can schedule the meeting?

This could be affeted by the re-design of the scheduler component

As soon as the meeting is available to be queried by Office API. We should be good so closing this issue


SWARM-962 - Uberjar does not handle dependencies with classifier

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Ok to test

Ignore Windows failure.


ListItemIcon missing onClick event in typescript definition ( ListItemIcon.d.ts )

The ListItemIcon typescript definition looks wrong, it should be as ListItemText someting like
export interface ListItemIconProps extends StandardProps<React.HTMLAttributes, ListItemIconClassKey> {
children: React.ReactElement;
}
but it's
export interface ListItemIconProps extends StandardProps<{}, ListItemIconClassKey> {
children: React.ReactElement;
}
txs a lot guy for the great work

it's working here -> https://codesandbox.io/s/jp7krr9m79

This component should ideally allow whatever props its child element allows, but that's hard to provide an accurate type for (see #11731). I guess we could allow any React.HTMLAttributes, even though that's not strictly accurate, but why not just pass the props directly to the child, e.g. instead of
<ListItemIcon onClick={this.handleClickListItem}>
  <InboxIcon />
</ListItemIcon>

do
<ListItemIcon>
  <InboxIcon onClick={this.handleClickListItem} />
</ListItemIcon>

?

This was fixed in #13067 and released with<EMAIL_ADDRESS>


Update the ringbuffer tail here if the cmd is timedout in ringbuffer in kernel space

Here we add one timer for each scsi command in tcmu-runner, and the time out value is (cmd_time_out + 5) seconds to make sure before the timer is fired in userspace here, the timer in ringbuffer in kernel space has already been fired.
Fixed: #485
@mikechristie @pkalever Please review.

Do you need to consider the case where qfull_timeout hits which then calls tcmu_check_expired_cmd() in kernel? That would then time out all the commands in the queue if that timer is hit right? Do you need to update the tail ringbuffer in userspace in that case?

For the case where the qfull or cmd timer fires and tcmu_check_expired_cmd runs and there are expired running commands, the kernel does not clear the ring, because we do not have any synchronization with userspace, so we do not know if it is accessing the pages or not. And then we do not clear the ring for non-running commands, because they are not in the ring yet.
We could add some sort of lock/bits for the running cmd case, but if runner is dead then there is normally no point. The commands would just keep timing out until you hit the initiator side retry limit so either way the path/device is going to go down/offline. Note, when runner restarts then it will clean up the ring in newer kernels.
If runner is up and if a command timesout in userspace by the timer in xiubo's patches then it would complete the command with a failure to the kernel. This will free up the space in the ring, and the kernel would take commands from the cmdr_queue and put them in the ring or execute new commands.

Yeah, that's right.
And also this fix will depend on the following kernel fix:
scsi: tcmu: avoid cmd/qfull timers updated whenever a new cmd comes
https://patchwork.kernel.org/patch/10644889/

Without this, there will be the ringbuffer broken issue due to the cmd_time_out timer is not working as it is expected.

Update it done.

@mikechristie @pkalever @bgly
Test done.

@lxbsz
I am closing this for now. Reopen or make a new PR against:
https://github.com/open-iscsi/tcmu-runner/pull/568
We can add a handler callout that is called in check_for_timed_out_cmds, or call a function to do the ring cleanup from there, etc.


feat: bitblasting theorems about unsigned bitvector inequalities

This PR adds theorems that relate unsigned bitvector comparisons BitVec.ult and BitVec.ule to BitVec.carry. These lemmas are a prerequisite to bit-blasting these comparisons in LeanSAT.

awaiting-review


Update reference to Danny's GitHub account

Addresses islandora-claw/CLAW#312

Current coverage is 92.79% (diff: 100%)

Merging #56 into master will not change coverage

@@             master        #56   diff @@
==========================================
  Files             4          4
  Lines           222        222
  Methods          36         36
  Messages          0          0
  Branches          0          0
==========================================
  Hits            206        206
  Misses           16         16
  Partials          0          0

Powered by Codecov. Last update a0b06b6...4bf3740

@ruebot I think I rebased? First time I've tried it this way.


Max number of maps?

The what's new help topic indicates this template can be used to compare up to four maps, but I was able to add more than that...

Thanks yeah its a typo in the doc. You can compare an unlimited amount of maps. Although at some point the app becomes a bit unwieldy.


[SPARK-17640][SQL]Avoid using -1 as the default batchId for FileStreamSource.FileEntry

What changes were proposed in this pull request?
Avoid using -1 as the default batchId for FileStreamSource.FileEntry so that we can make sure not writing any FileEntry(..., batchId = -1) into the log. This also avoids people misusing it in future (#15203 is an example).
How was this patch tested?
Jenkins.

/cc @jerryshao

Test build #65801 has started for PR 15206 at commit d9177e5.

@zsxwing Will this break streaming jobs if someone upgrades their Spark version, since they won't be able to deserialize the class correctly?

@zsxwing Will this break streaming jobs if someone upgrades their Spark version, since they won't be able to deserialize the class correctly?

@brkyvz No. This doesn't change the file format. FileEntry(..., batchId = -1) is only used in SeenFilesMap which is only in memory.
By the way, people cannot just upgrade the Spark version since FileStreamSource's format has been changed in #13513.

@brkyvz right now we cannot support upgrading anyway since the execution metadata uses Java serialization.

Test build #65803 has started for PR 15206 at commit f506a43.

LGTM, thanks for the fix.

Test build #65801 has finished for PR 15206 at commit d9177e5.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class FileEntry(path: String, timestamp: Timestamp, batchId: Long) extends Serializable

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65801/
Test PASSed.

Merged build finished. Test PASSed.

Test build #65803 has finished for PR 15206 at commit f506a43.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class FileEntry(path: String, timestamp: Timestamp, batchId: Long) extends Serializable

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65803/
Test PASSed.

Merged build finished. Test PASSed.

Thanks. Merging to master and 2.0.


Variables for coupons

i think the /coupon add cmd should have variables like
{console}: execute command as console
{player}: player name
so that it would be better

Related to #18.

As it is already, %p will be replaced with the player's name
The command is already run as console.
What's left of this issue is already addressed by #18


Internal search not working in case of multiple versions.

Error Description
Internal searching only works in v1.0. When we create docs for v1.2 or v1.3, it does not work. When we click on the search icon, it shows - result not found.
Also, when we click on search icon, it shows a 500 internal server error in ajax call.
This is the ajax URL - /docs/search-index/1.2
See the error traces in the screenshot attached.
Error traces screenshot
You can also have a look at the error live -
Online docs
To Reproduce
Steps to reproduce the behavior:

Create two versions of docs.
Switch to internal searching.
First, try in v1.0, the search will work.
Then, switch to another version v1.2, and click on the search icon. And you'll see the error.

Screenshots
Error traces screenshot
Desktop (please complete the following information):

Linux (Ubuntu 18.04)
Browser Chrome, safari
Version latest

please make sure you have a correct version structure.
after adding the version you need inside config/larecipe.php
run this command which will take care of the structure to make the search work.
php artisan larecipe:docs

See docs here: https://larecipe.binarytorch.com.my/docs/2.2/artisan-commands#docs-command
and here: https://larecipe.binarytorch.com.my/docs/2.2/search#available-engines


[BUG] ErrImagePull after k3d image import using latest tag

What did you do

How was the cluster created?

 k3d cluster create demo -p "8081:80@loadbalancer" --wait

What did you do afterwards?

$ k3d image import myapp:latest -c demo
INFO[0000] Importing image(s) into cluster 'demo'
INFO[0000] Loading 1 image(s) from runtime into nodes...
INFO[0007] Importing images '[myapp:latest]' into node 'k3d-demo-server-0'...
INFO[0024] Successfully imported image(s)
INFO[0024] Successfully imported 1 image(s) into 1 cluster(s)

$ docker exec -it k3d-demo-server-0 crictl images
IMAGE                                      TAG                    IMAGE ID            SIZE
docker.io/library/myapp                    latest                 06f7f2a4f851c       587MB
docker.io/rancher/coredns-coredns          1.8.3                  3885a5b7f138c       12.9MB
docker.io/rancher/klipper-helm             v0.6.6-build20211022   194c895f8d63f       84.5MB
docker.io/rancher/klipper-lb               v0.3.4                 746788bcc27e2       3.33MB
docker.io/rancher/library-traefik          2.4.8                  deaf4b1027ed4       27.8MB
docker.io/rancher/local-path-provisioner   v0.0.19                148c192562719       13.6MB
docker.io/rancher/metrics-server           v0.3.6                 9dd718864ce61       10.5MB
docker.io/rancher/pause                    3.1                    da86e6ba6ca19       327kB

$ kubectl run -it --image=myapp:latest myapp
error: timed out waiting for the condition

$ kubectl get events --sort-by='{.lastTimestamp}'
LAST SEEN   TYPE      REASON                    OBJECT                       MESSAGE
7m44s       Normal    Pulling                   pod/myapp                    Pulling image "docker.io/library/myapp:latest"
7m38s       Warning   Failed                    pod/myapp                    Failed to pull image "docker.io/library/myapp:latest": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/myapp:latest": failed to resolve reference "docker.io/library/myapp:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
7m38s       Warning   Failed                    pod/myapp                    Error: ErrImagePull
7m26s       Warning   Failed                    pod/myapp                    Error: ImagePullBackOff
4m13s       Normal    BackOff                   pod/myapp                    Back-off pulling image "docker.io/library/myapp:latest"

What did you expect to happen
Image is found and pod started.
Which OS & Architecture
darwin/amd64
Which version of k3d
k3d version v5.2.2
k3s version v1.21.7-k3s1 (default)
Which version of docker

docker version
Client:
 Cloud integration: v1.0.22
 Version:           20.10.11
 API version:       1.41
 Go version:        go1.16.10
 Git commit:        dea9396
 Built:             Thu Nov 18 00:36:09 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.11
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.9
  Git commit:       847da18
  Built:            Thu Nov 18 00:35:39 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.7.1)
  compose: Docker Compose (Docker Inc., v2.2.1)
  scan: Docker Scan (Docker Inc., v0.14.0)

Server:
 Containers: 116
  Running: 3
  Paused: 0
  Stopped: 113
 Images: 51
 Server Version: 20.10.11
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc version: v1.0.2-0-g52b36a2
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.76-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 7.773GiB
 Name: docker-desktop
 ID: N6FS:ZMSR:L6NJ:2AZY:TTDX:ULSI:RM3M:3YGV:T5FK:WO6H:M3TX:LUOU
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 62
  Goroutines: 59
  System Time: 2022-01-11T06:12:04.498921447Z
  EventsListeners: 3
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

The above does not happen when using a tag other than latest, eg:
k3d image import myapp:local -c demo
kubectl run -it --image=myapp:local myapp

Hi @tekumara , thanks for opening this issue!
This is actually pretty interesting and I can confirm your experience there.
Now this doesn't seem to be an issue on k3d's side though, as everything it does works exactly as expected :thinking:


Java visual update to remove VisualResults

Removing VisualResults from Java.
Updated the API to make projectName and testName mandatory in all of the appropriate constructors.
Add advanced data driven visual example.

Need to add examples like here https://github.com/saucelabs-training/demo-java/blob/main/selenium-junit4-examples/src/test/java/com/saucedemo/selenium/junit4/SimpleVisualE2ETest.java#L115-L158
Also, should create some docs on how to make the transition from old way to new way


Logging: Rename event_data members of skua_move event

For most of the events involving x/y/z coordinates, we used posX, posY, and posZ.
skua_move has both a "from" and "to" set of coordinates, so we need to take that into account when setting the names of each coordinate in the event_data. However, as written, we completely broke with the convention, using from_position_x, to_position_x, etc.
To keep better consistency between events, let's rename those to the form of from_posX, to_posX, etc
In other words, keep position shortened to pos, don't add an underscore between pos(ition) and x/y/z, and keep the coordinate letter upper-case (X instead of x).

4c7b677fdf1facdaf87022dcb57e4a57aa72ed33


Response viewer does not update

usePusher has not been updated in 2 years and is dependent on React 16 which causes a dependency conflict.
The viewer should be updated to no longer use the package and restore original realtime functionality.

Removed hardcoded Pusher value and uninstalled use-pusher


Serializing a vector of classes?

I have a vector* of class* (vector<Doctor*> doctors) and I need to serialize it. The class Doctor has some other vector of class* that have to be serialized too. The question is, do I need to create to_json and from_json methods for vector*<Doctor*>, and for any other vectors of classes inside Doctor? I have already created the methods for the class doctor and for every other class that needs it, yet I keep getting the "could not find to_json() method in T's namespace".
I am using MSVS 2017. Thank you in advance for your help!

Are the methods in the right name space? Can you try without any pointers just to make sure this works?

It does work when the vector is for the class Doctor and not for a pointer.

Maybe @theodelrieu has an idea.

Pointer to user-defined types conversion is not supported by the library.
But you can do it, you have to specialize adl_serizalizer on pointer types (I would recommend supporting Doctor* to begin with though).

Thanks @theodelrieu ! We should put this into the README at some point...

In fact it's way simpler, for a single type at least:
namespace my_ns {
  void to_json(json& j, const Doctor* doc) {}
}

Never thought about that before... So if you want to support both Doctor* and Doctor&, you have to write two to_json overloads.

But I have more vector to class pointers inside the Doctor class that also need serialization. I have to create a to_json and from_json overload for each of them?
Thank you for the great help btw!

I have to create a to_json and from_json overload for each of them?

Absolutely, that's a bit tedious though. I don't know what is your exact use-case for having vectors of pointers, but I would advise not doing that if you can avoid it.
Unless you're using base classes and inheritance, storing Doctor instead of Doctor* gives you back a real copy (value semantics, instead of reference semantics).

I am using inheritance and I am sadly required to have pointers instead of values. I will try to create the methods for class pointers and will report back.

Not yet, I will have more soon.

Sadly same error. I created the to_json methods for every class* and I still get that the to_json method doesnt exist.

Unfortunately, the current error is already an improvement, because it is very difficult to indicate errors there. Can you share some code so we can better understand what's going wrong?

For sure. I uploaded the peoject here https://github.com/voidblaze/CPP-Appointment-Scheduler

I could compile the project with latest GCC on Linux (with -fpermissive though, there are some errors unrelated to json).

Yeah sorry, I forgot to uncomment the line that was causing the error.  Its on data handler, line 191. I believe the errors have something to do with the file opening on line 188, on a path that obviously doesn't exist on your machine.
I pushed the fixed solution.

You're trying to serialize a std::vector<...>**, I would advise passing such argument by reference in the first place.
Changing the problematic line to json jDoctors = *doctors makes the project compile.
Personally, I would keep pointers for virtual classes, and use references everywhere else.

Thanks @theodelrieu for helping out!
@voidblaze What would you add to the documentation?


State transition manager test coverage

What ❔
This PR enhances the test coverage for the StateTransitionManager contract. Specifically, it includes additional unit tests to cover edge cases and scenarios that were previously untested.

opened to main repo dev


!##[RUGBY@STREAMs]!## Scotland vs Fiji Live 𝐒𝐭𝐫𝐞𝐚𝐦𝐬 CoVeRaGe oN TV Channel 02 November 2024 #1337

Scotland are set to face Fiji in their first match of the autumn internationals on Saturday evening. This weekend will see only four teams in action, with England taking on New Zealand at Twickenham.
🅻🅸🆅🅴🔴▶ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶ CLICK HERE TO LIVE STREAM
The Test at Murrayfield should provide the Scots with the physical battle they need in preparation for hosting world champions South Africa in eight days' time. Throughout November, rugby fans can look forward to a feast of Test match action, with 21 games scheduled.
Scotland will also play matches against emerging rugby nation Portugal and southern hemisphere heavyweights Australia. Here's everything you need to know about the match in the Scottish capital.
What time does Scotland v Fiji kick-off?
The Scotland v Fiji match kicks off at 5.40pm on Saturday, November 2, at Murrayfield Stadium in Edinburgh.
Which TV channel is showing Scotland v Fiji?
The Scotland v Fiji match will be broadcast live on TNT Sports.
How can I live-stream the match?
The Scotland v Fiji match can be live-streamed using the Discovery+ app. An active TNT Sports subscription is required to stream, which is available for £30.99 on a rolling monthly basis with Discovery+ Premium and also includes the UEFA Champions League, Europa League, boxing, NBA and WWE.
What's the team news?
Scotland XV: Kyle Rowe; Darcy Graham, Huw Jones, Sione Tuipulotu (C), Duhan van der Merwe; Adam Hastings, Ali Price; Pierre Schoeman, Ewan Ashman, Zander Fagerson, Grant Gilchrist, Scott Cummings, Matt Fagerson, Rory Darge, Jack Dempsey.
The Scotland and Fiji teams have been announced, with no shortage of talent on the reserves bench for both sides. The replacements for Scotland include Dylan Richardson, Rory Sutherland, D'Arcy Rae, Max Williamson, Gregor Brown, Jamie Dobie, Tom Jordan, and Stafford McDowall.
Meanwhile, Fiji will have Mesulame Dolokoto, Livai Natave, Jone Koroiduadua, Mesake Vocevoce, Vilive Miramira, Simi Kuruvoli, Kemueli Valetini, and Waqa Nalaga standing ready. .
Fiji XV: Isaiah Ravula; Vuate Karawalevu, Apisalome Vota, Inia Tabuavou, Ponipate Loganimasi; Caleb Muntz, Frank Lomani; Haereiti Hetet, Tevita Ikanivere (C), Samuela Tawake, Isoa Nasilasila, Ratu Leone Rotuisolia, Ratu Meli Derenalagi, Kitione Salawa, Elia Canakaivata into the fray.
Coaches from both teams shared their views ahead of the match. Scotland head coach Gregor Townsend said: "I think Adam [Hastings] has really settled in being back at Glasgow, playing with real pace, and his experience now as a club 10, as an international 10 has been evident.
"And Ali [Price] has just got into some excellent form. The nine position was very competitive with George [Horne] and Jamie [Dobie]. Obviously, Ben [White] is not available."


Fix test failed by multiple process group initialization

Summary:
Unit tests are currently failed, because process group is initialized multiple times without cleanup.
I also updated the test case to work both nccl and gloo backend.

@KanchiShimono thanks for jumping in to fix this!
We actually have an internal  diff which is being exported now to fix this  issue (you're right in the root cause ) - see https://github.com/pytorch/torchrec/pull/153

@colin2328
Thanks for reply and review!
TorchRec is most interesting project for me!
I'm very excited about your teams shared such amazing library as OSS!
So I wanna contribute this project continuously.
The issue is fixed by #153, so I close this PR.


test_000022.iamf

Hello, I'm Yongmin.
test_000022 is an example of incorrect roll_distance, with -5 in the roll_distance value when 960 num_samples_per_frame.
According to Part 4.6(https://www.rfc-editor.org/rfc/rfc7845#page-11), the value of the sample before at least 3840 should be seen, and the case seems to satisfy the condition. (960 * 5 = 4800 samples)
Please check about this issue.

This was intended behavior. test_000022.textproto has is_valid set to false. That means the test vector is intentionally a "should-fail" test case intended to verify the decoder can catch incorrect roll distances.

I think my explanation was not enough.
If you check the following phrase in the specification, I think roll_distance: -5 is possible.
(https://aomediacodec.github.io/iamf/#roll_distance)

It shall be set to -1 for IAMF-AAC-LC and -R (R = 4 when the frame size = 960) for IAMF-OPUS. IAMF-FLAC may ignore this field. Where, R is the smallest integer greater than or equal to 3840 divided by the frame size.

Also, as in my first comment, 'at least 3840' seems to allow 4800 samples like the test_000022.
So, what I meant was that I thought it is right to change is_valid: true.
What do you think about this?

I think the following sentences mean for any frame size, there is only one valid roll distance, which is -R.

-R (R = 4 when the frame size = 960) for IAMF-OPUS
R is the smallest integer greater than or equal to 3840 divided by the frame size.

And R is ceil(3840 / frame size). There is no freedom to choose other values of R. So roll_distance: -5 is invalid for frame_size = 960.


Merge 'logging-api' branch to master.

@tseaver Anything for me to do here? Also, any idea what triggered AppVeyor?

@dhermes I don't think further review is really needed:  each of the commits on the branch are the result of reviewed PRs.  I know there will be a (small) conflict with your datastore-v1b3ta3 branch in system_tests/run_system_test.py:  I presume it will be a trivial fix to resolve.
@jgeewax I plan to merge tomorrow, if that doesn't conflict with anything else planned for the day.


Add flake.nix

Adds flake.nix, allows for development on NixOS

I'm still testing this, please hold off on merging

I don't understand why it costs that lots of code.
How did the pkgs.haskellPackages.h-raylib works? It seems work well before ( broken in unstable now).
I am not very familiar with nix, but why system default drv works well, is anybody make a patch to it?
See https://github.com/NixOS/nixpkgs/issues/197407

the problem is that h-raylib brings its own raylib and glfw. Which works well on other distros but is very un-NixOS-sy imo. Removing that simplifies packaging a lot.

I will have to update the git revision for raylib in flake.nix every time I pull the raylib source right?

there is no easy way to include a submodule. Nix doesn't do submodules.

After recheck code in nixpkgs, i.e. pkgs.haskellPackages.h-raylib, I found it fetch tar.gz directly from Hackage, and that works well with simplest callCabal2nix build scripts. The difference between tar.gz source code and this git repo, is in the raylib sub-folder, the hackage one contains a CmakeFiles folder, and that makes nix build works! see my repo directly using code downloaded form hackage https://github.com/futu2/h-raylib-<IP_ADDRESS>

diff h-raylib-<IP_ADDRESS>/raylib/ h-raylib/raylib/

Only in h-raylib/raylib/: BINDINGS.md
Only in h-raylib/raylib/: CHANGELOG
Only in h-raylib/raylib/: cmake
Only in h-raylib-<IP_ADDRESS>/raylib/: CMakeFiles
Only in h-raylib/raylib/: CMakeLists.txt
Only in h-raylib/raylib/: CMakeOptions.txt
Only in h-raylib/raylib/: CONTRIBUTING.md
Only in h-raylib/raylib/: CONVENTIONS.md
Common subdirectories: h-raylib-<IP_ADDRESS>/raylib/examples and h-raylib/raylib/examples
Only in h-raylib/raylib/: FAQ.md
Only in h-raylib/raylib/: .git
Only in h-raylib/raylib/: .github
Only in h-raylib/raylib/: .gitignore
Only in h-raylib/raylib/: HISTORY.md
Only in h-raylib/raylib/: LICENSE
Only in h-raylib/raylib/: logo
Common subdirectories: h-raylib-<IP_ADDRESS>/raylib/parser and h-raylib/raylib/parser
Common subdirectories: h-raylib-<IP_ADDRESS>/raylib/projects and h-raylib/raylib/projects
Only in h-raylib/raylib/: raylib.pc.in
Only in h-raylib/raylib/: README.md
Only in h-raylib/raylib/: ROADMAP.md
Common subdirectories: h-raylib-<IP_ADDRESS>/raylib/src and h-raylib/raylib/src

there is no easy way to include a submodule. Nix doesn't do submodules.

Can nix flake fetch a raylib repo right in the ./. folder?
My simple callCabal2nix flake scripts run nix build successfully if delete git info by running mv .git .git.bk

yeah deleting .git is a horrible hack, nix just does not work with submodules.


Implement request_close() support for Windows in druid-shell

This PR implements the Windows part of #1159 "Implement close request interception".

This is my first PR for this project; hope my submitting a PR without an introduction or any warning is OK?
I've just encountered the non-working CLOSE_WINDOW while working on an app I'm building as an exercise to grok the Rust way, and fixing it seemed straightforward.
Hope it can be of use.

Thanks for the patch! Can you add it to the changelog also? Look for the line containing #1118

done!

(updated from master)

Thank you!


Adding loading support for CommonJS managers

I belive this was fixed in https://github.com/gsklee/ngStorage/commit/8df9a7bbc239233f5bce63e02792b8afbd92e8df


Highlight tsxCloseTagName

Right now tsxCloseTagName doesn't have any highlighting
Lets fix that
Before:

After:

Great thanks!


Copy testgrid distribution to jenkins slaves

Purpose

Contains additional steps required to copy the TestGrid distribution to the slave nodes to run tests.
Resolves #504

Goals

Adding the TestGrid distribution to the jenkins slave nodes

Approach

Adding another stage to deploy to the slave node in the Jenkins continuous-delivery pipeline

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

This cannot be resolved through the CD pipeline since the slave jenkins in OpenStack is not reachable from AWS nodes.


Inferred default parameter is erroneous using "typedef" "parameter"

Bug Report

TSLint version: 3.10.2
TypeScript version: 1.8.10
Running TSLint via: Visual Studio Code

TypeScript code being linted
class C {
  fn(str = '') {
  }
}

or
class C {
  fn(str: string = '') {
  }
}

with tslint.json:
{
  "rules": {
    "typedef": [
      true,
      "parameter"
    ],
    "no-inferrable-types": true
  }
}

Actual behavior
You either get "LHS type (string) inferred by RHS expression, remove type annotation" or "expected parameter: 'str' to have a typedef"
Expected behavior
To not get "expected parameter: 'str' to have a typedef" if you specified a inferable default parameter value.

Yes, this is an issue unfortunately. See https://github.com/palantir/tslint/issues/711 and #739


Add power measurement quirk for Xiaomi CN/AU lumi.plug

This adds a quirk for the Chinese version of the Xiaomi plug lump.plug.
The quirks adds a sensor for power usage in watts.
Addresses #397

Thanks!

Thanks for merging 🙂


try building aarch64 with cibuildwheel

using https://cibuildwheel.readthedocs.io/en/stable/faq/#emulation
alternative to #2239
fixes #2187

Humm, this seems to be working. The problem is that build time has increased from 9 minutes for that stage to over an hour!
We build wheels on every commit to master to avoid build errors when we deploy, so this change could cause massive backups of builds, which slows development. Additionally the feedback look to fix any error with building wheels would grow enormously.
Is aarch64 really used enough to warrant this?
Is there another work around? A flag that makes compilation quicker, a way to run these steps nightly only or a way to ask github for our actions to run on a faster machine (I doubt it)?

@odidev you created the original issue, what are your thoughts on this?

@samuelcolvin, I can see that it taking around ~30 minutes to build the aarch64 wheels.
Unfortunately, there is no way to make the wheel build faster for aarch64. One thing you can do is to build aarch64 wheels only on release of a tag in the next step.
Currently, I am working on cross compiling aarch64 wheels through 'cibuildwheel'. The will speedup the wheel build process for aarch64. For more details, please check: https://github.com/joerick/cibuildwheel/issues/598

Thanks so much for looking into this @odidev.
How do you feel about closing this and waiting for a fix in cibuildwheel?

Yes, please close this PR. I will make another PR when cibuildwheel have cross compilation support.


How to turn the parameter of "continuous_queries_enabled" on?

I downloaded PIPELINEDB rpm 0.85 for Centos 6 and installed it according to the installation instruction.
I started the server, created a stream, and tried to insert some values. Then I got the warning as below:
pipeline=# INSERT INTO test_stream (payload) VALUES ('key test');
ERROR:  cannot insert into stream test_stream since continuous queries are disabled
HINT:  Enable continuous queries using the "continuous_queries_enabled" parameter.

I tried to modified "pipelinedb.conf", but the parameter seems already turned on by default.
What would be the mistakes I made here? My OS is CentOS release 6.7 (Final).

Oops, need to fix that hint. You can enable continuous queries using 'ACTIVATE'.
https://www.pipelinedb.com/blog/pipelinedb-0-8-5

Thank you for the lightning fast reply.


Unbelievable! coin master free coins - The Ultimate Hack to Get coin master free coins Players Revealed!

Unbelievable! coin master free coins - The Ultimate Hack to Get coin master free coins  Players Revealed!  Amassing a steady stream of these virtual currencies is crucial for unlocking new villages, upgrading your base, and engaging in the game's various mini-games and challenges. Whether you're a seasoned player or a newcomer to the Coin Master realm, mastering the art of earning free coins can significantly enhance your gaming experience and propel you towards your ultimate goals.
One of the most straightforward ways to acquire free coins in Coin Master is through the daily spin mechanic. Each day, players are granted a limited number of free spins that can yield a variety of rewards, including coins, resources, and even village pieces. Maximizing the potential of these free spins is essential, as they can provide a steady influx of coins without requiring any additional investment.
Another lucrative source of free coins in Coin Master is the game's social features. By engaging with your friends, sending them gifts, and participating in raids, you can unlock a multitude of rewards, including a share of the coins and resources collected from successful raids. Additionally, joining a Coin Master clan or alliance can open up opportunities to collaborate with other players, share resources, and collectively work towards common goals, all of which can lead to increased coin earnings.
Completing in-game achievements and challenges is another effective way to earn free coins in Coin Master. The game offers a wide array of objectives, ranging from reaching specific village levels to performing certain actions a certain number of times. By systematically working towards these achievements, players can unlock substantial coin rewards, as well as additional bonuses and resources that can further enhance their coin-earning potential.
Leveraging the game's daily rewards and login bonuses is also a crucial strategy for earning free coins in Coin Master. The game often offers daily login rewards, which can include a varying number of free coins, as well as special event-based bonuses and rewards that can be claimed by logging in and completing specific tasks. Staying consistent with your daily login and taking advantage of these rewards can provide a steady stream of free coins to fuel your gameplay.
In addition to the in-game methods, there are also external resources and strategies that Coin Master players can utilize to earn free coins. One such approach is engaging with the game's social media channels, such as Facebook, Twitter, and Instagram, where the developers often share promotional codes, giveaways, and other opportunities to earn free coins. Additionally, there are various online communities and forums dedicated to Coin Master, where players can share tips, strategies, and even discover free coin offers and special deals.
It's important to note that while Coin Master does offer many avenues for earning free coins, players should always be cautious of any offers or methods that seem too good to be true. Scams and unauthorized coin generators can pose a risk to the security of your account, and it's crucial to only engage with legitimate and official sources when seeking to earn free coins in the game.
In conclusion, mastering the art of earning free coins in Coin Master is a crucial aspect of ensuring a successful and enjoyable gaming experience. By leveraging the game's various mechanics, social features, and external resources, players can maximize their coin earnings and propel their progression through the game's expansive and engaging content.


Can't import from SystemKernelExtensions.kc on ARM64 macOS 13.0.1

To Reproduce
Steps to reproduce the behavior:

Go to Import file and choose /System/Library/KernelCollections/SystemKernelExtensions.kc
In the Container File Detected dialog choose "File System"
Try to import "System/Library/Extensions/acfs.kext"
Get "Unable to import file acfs.kext". Cause: invalid start position: 0

Environment (please complete the following information):

OS: macOS 10.13
Java: 17
Ghidra Version: 10.2.2
Ghidra Origin: official

I'm reproducing this.  I think i just need to add support for LC_FILESET_ENTRY to MachoPrelinkFileSystem.

I'm reproducing this. I think i just need to add support for LC_FILESET_ENTRY to MachoPrelinkFileSystem.

For my own future notes: the issue is actually that XML integer values are being read as hex instead of decimal.  Fixing that though reveals more problems, such as the  chained fixups not working because the file offsets are not being adjusted when the extracted Mach-O is put into its own provider which starts at 0.


[Hackadoc] Updates to hbase mvn build tutorial, fixing typo

Hi @abhiver, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Windows and CustomJars: Invalid Escaping

Hey @andypetrella ,
just worked on some stuff and needed the spark-csv library, so I used the great :dp functionality on windows (naturally ^^), which worked fine until the very end when the ReplCalculator had to integrate the custom jars (via the CustomJars variable). One thing sure to fail are Windows \ (backshlash) as scala interprets this as an escaping character... sooooo once again, a windows fail.
There is one small change needed (ReplCalculator): .replace("\","\\")
I will see if I can manage another PR for this, okay? Or do you have any other ideas?

Ohhh damned, indeed...
So better use pathSeparator instead?
WDYT?

I don't thinks that's the problem here - this is the error message:
2015-09-23 20:00:29,918 ERROR [Remote-akka.actor.default-dispatcher-3] (notebook.client.ReplCalculator) - Error in init script:
:2: error: invalid escape character
val CustomJars = Array("C:\Users\Carsten\AppData\Local\Temp\spark-notebook\repo\f6eec9e4-0ed7-4b5d-92cf-40392b85b183\cache\com.databricks\spark-csv_2.10\jars\spark-csv_2.10-1.2.0.jar","C:\Users\Carsten.m2\repository\org\scala-lang\scala-library\2.10.4\scala-library-2.10.4.jar","C:\Users\Carsten\AppData\Local\Temp\spark-notebook\repo\f6eec9e4-0ed7-4b5d-92cf-40392b85b183\cache\org.apache.commons\commons-csv\jars\commons-csv-1.1.jar","C:\Users\Carsten\AppData\Local\Temp\spark-notebook\repo\f6eec9e4-0ed7-4b5d-92cf-40392b85b183\cache\com.univocity\univocity-parsers\jars\univocity-parsers-1.5.1.jar")
Which points the problem towards the '' sign. I thought about an elegant way, but the truth is, that my suggestion is most likely and unfortunatly the best way to deal with this. Yes it seems like a dirty fix, but it isn't. You are generating code here and only here it is important to know that a \ character within your data (deps) will cause trouble. Even if you use triple double quotes (yikes what a combo!) you stumble over \un with seems to be a unicode escaping character - wierd. This isn't only a windows phenomena, though it is absolutely inavoidable, but it may happen for situations where you have real \ in a linux path - okay that's quite unlikely, but still, it should be handled.

isn't this on fixed too ^^?

Yep, I think so. It hasn't shown up since!
I'll close this, okay?
Cya and Cheers!


can't write zwc file

Hi there,
Recently I moved my dotfiles to a new location and now when I open my terminal I get this message:
-antigen-cache-generate:zcompile:65: can't write zwc file: $HOME/.dorothy/user/sources/plugins.zsh.zwc

I don't know how or where this path is set that fixes this, or if there is something else that I need to do.
Does any of you guys here know what I should do to fix this?
Just to be clear, ~/.dorothy/user/sources is not where I keep my plugins script anymore.

lol I am not sure what I did but the error went away.
One thing that I am sure that I did is the following:
purge rupa/z and bundle wookayin/fzf-fasd @ master and then eval init fzf fasd in zshrc.


last item fetched

Store last fetched date or post id
So we can remove items without creating them again on the next fetch

Fixed in https://github.com/quicoto/RSS-Reader/commit/17053f67868deaf7a9498fa91acfffb490bee42d


Display/Download raw message data from UI

We should have an option to show or download the raw message data for messages, similar to how most email clients allow you to open the raw email message. Right now, the only way to access raw message data is to ssh into the server, find the message record using the Rails console, copy and paste the raw data or download the message via scp or a similar tool. That takes quite a lot of time, can be down only  by devs and is error-prone.

I think there are at least two use cases for this:
1) Deciding wether unsupported contents are important, recovering unsupported contents
We’ve had quite a few situations where actual contributors sent us emails containing unsupported contents. In many of those cases, the reasons for the "unsupported content" warning probably is caused by attached images in email signatures (e.g. company logos), contact cards (e.g. vcf files), email signatures (e.g. p7s) files.
However, in some cases, the attached files might actually be relevant to the message. While ideally 100eyes should support receiving any email attachment, for know it would already help if it was possible to open/download the raw message data. This would allow us to quickly evaluate what a problem with a message is and, if necessary, to decode the attachment from the raw email.
2) Recovering parts of messages that have been incorrectly stripped out
As email clients format HTML emails in lots of different ways, it happens from time to time that the logic that removes all HTML markup incorrectly also removes parts of the actual message content. In those cases, even tech-savvy editors could use that feature to quickly see the actual message contents.

As we now have an admin dashboard, I'd suggest adding this to the dashboard instead of the main application. Apart from that, there is still a need to download the raw message data to easily debug/retrieve messages that contain unsupported content types and/or use unsupported messenger features.

Yes, please.


Facets: allow selection of a single kind

bonus: reworked the ui a bit to be more space efficient
bonus: added tooltips

#3920

Kam, see the issue (#3920) for a screenshot

This pull request introduces 1 alert when merging 1d55ef1f7ad507fd3afe0a016c0eae2eff4ba9ba into 5f833ea2f61582a2f71cf567e28cfd1d2880e961 - view on LGTM.com
new alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com


How to create with tabs?

Hi,
Thanks for a great plugin.
I'm trying to create ColResize with tabs but only working on the first active tab. Here is the example https://codepen.io/yurenlimbu/pen/PMwzEy?editors=1010.

@yurenlimbu I assume it's because the content has not rendered correctly and the widths cannot be calculated. You'll need to trigger the intances on tab switch.


Accessing ActiveMQ on Amazon MQ

Hello,
I am using masstransit in a Lambda function to create a queue using Amazon MQ with ActiveMQ.
The uri I am connecting with:
amqp+ssl://b-97e4e5d9-f48d-4bc8-8e4a-34a028cb9b77-1.mq.eu-west-1.amazonaws.com:5671
The code is below:
public IBusControl CreateBus(string amqpUri, string username, string password, string queueName, Action<IReceiveEndpointConfigurator> receiveEndpoint)
        {
            var busControl = Bus.Factory.CreateUsingActiveMq(async cfg =>
            {
                //var uri = $"amqps://{amqpUri}.mq.eu-west-1.amazonaws.com:5671";
                var uri = $"amqp+ssl://{amqpUri}-1.mq.eu-west-1.amazonaws.com:5671";

                await Console.Out.WriteLineAsync("amqp uri: " + uri + " |");

                cfg.Host(new Uri(uri), h =>
                {
                    h.UseSsl();
                    h.Username(username);
                    h.Password(password);
                });

                cfg.ReceiveEndpoint(queueName, ep => receiveEndpoint.Invoke(ep));
            });

            return busControl;
        }

    Which is invoked with:

    `var busControl = new ActiveMQBroker().CreateBus(amqpUri, "****", "****", "tweetstream", null);`

However, I am seeing the following exception:
The address scheme is not supported: amqp+ssl (Parameter 'address')
I have tried a few variations using: amqp:// , amqps:// , etc but no luck
I have the following ports opened on Amazon MQ for inbound:
{
                        "CidrIp" : "<IP_ADDRESS>/0",
						"FromPort" : 8162,
						"IpProtocol" : "tcp",
						"ToPort" : 8162
                    },
					{
                        "CidrIp" : "<IP_ADDRESS>/0",
						"FromPort" : 61617,
						"IpProtocol" : "tcp",
						"ToPort" : 61617
                    },
					{
                        "CidrIp" : "<IP_ADDRESS>/0",
						"FromPort" : 5671,
						"IpProtocol" : "tcp",
						"ToPort" : 5671
                    },
					{
                        "CidrIp" : "<IP_ADDRESS>/0",
						"FromPort" : 5672,
						"IpProtocol" : "tcp",
						"ToPort" : 5672
                    }

And the Lambda functions allows all traffic outbound.
Here is the full exception:
Lambda encountered an UnhandledException via 'AppDomain.CurrentDomain.UnhandledException' event:
{
"errorType": "ArgumentException",
"errorMessage": "The address scheme is not supported: amqp+ssl (Parameter 'address')",
"stackTrace": [
"at MassTransit.ActiveMqTransport.ActiveMqHostAddress..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ConfigurationHostSettings..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ActiveMqHostConfigurator..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.ActiveMqHostConfigurationExtensions.Host(IActiveMqBusFactoryConfigurator configurator, Uri hostAddress, Action`1 configure)",
"at Twitter.Analysis.Core.MessageBrokers.ActiveMQBroke ...
27 Jan 2021 16:08:27,543 [WARN] (invoke@invoke.c:331 **errno: Address family not supported by protocol) run_dotnet(dotnet_path, &args) failed**

This should have been a discussion, and will be moved once that feature is enabled.

ActiveMQ support is via OpenWire only, not AMQP. You need to configure the OpenWire connector to ActiveMQ on AmazonSQS.

This should have been a discussion, and will be moved once that feature is enabled.

ActiveMQ support is via OpenWire only, not AMQP. You need to configure the OpenWire connector to ActiveMQ on AmazonSQS.

activemq does support amqp.
http://activemq.apache.org/amqp

activemq does support amqp.
http://activemq.apache.org/amqp

The .NET ActiveMQ client library, which is used by MassTransit, only supports OpenWire.

The .NET ActiveMQ client library, which is used by MassTransit, only supports OpenWire.

I see, thanks.
I've attempted to reconfigure using OpenWire.
Using uri: ssl://b-97e4e5d9-f48d-4bc8-8e4a-34a028cb9b77-1.mq.eu-west-1.amazonaws.com:61617
But I see the same error message:
The address scheme is not supported: ssl (Parameter 'address')
{
"errorType": "ArgumentException",
"errorMessage": "The address scheme is not supported: ssl (Parameter 'address')",
"stackTrace": [
"at MassTransit.ActiveMqTransport.ActiveMqHostAddress..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ConfigurationHostSettings..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ActiveMqHostConfigurator..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.ActiveMqHostConfigurationExtensions.Host(IActiveMqBusFactoryConfigurator configurator, Uri hostAddress, Action`1 configure)",
Any tips?

I see, thanks.
I've attempted to reconfigure using OpenWire.
Using uri: ssl://b-97e4e5d9-f48d-4bc8-8e4a-34a028cb9b77-1.mq.eu-west-1.amazonaws.com:61617
But I see the same error message:
The address scheme is not supported: ssl (Parameter 'address')
{
"errorType": "ArgumentException",
"errorMessage": "The address scheme is not supported: ssl (Parameter 'address')",
"stackTrace": [
"at MassTransit.ActiveMqTransport.ActiveMqHostAddress..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ConfigurationHostSettings..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.Configurators.ActiveMqHostConfigurator..ctor(Uri address)",
"at MassTransit.ActiveMqTransport.ActiveMqHostConfigurationExtensions.Host(IActiveMqBusFactoryConfigurator configurator, Uri hostAddress, Action`1 configure)",
Any tips?

Changing the code to:
`var uri = $"{amqpUri}-1.mq.eu-west-1.amazonaws.com";
            await Console.Out.WriteLineAsync("uri: " + uri + " |");

            cfg.Host(uri, 61617, h =>
            {
                h.UseSsl();
                h.Username(username);
                h.Password(password);
            });`

            Seems to have done it.

            Thanks for your help.

            Are you aware of any plans to introduce AMQP?

Changing the code to:
`var uri = $"{amqpUri}-1.mq.eu-west-1.amazonaws.com";
            await Console.Out.WriteLineAsync("uri: " + uri + " |");

            cfg.Host(uri, 61617, h =>
            {
                h.UseSsl();
                h.Username(username);
                h.Password(password);
            });`

            Seems to have done it.

            Thanks for your help.

            Are you aware of any plans to introduce AMQP?

Are you aware of any plans to introduce AMQP?

I haven't seen any development in the ActiveMQ .NET libraries to add support for AMQP yet.

Are you aware of any plans to introduce AMQP?

I haven't seen any development in the ActiveMQ .NET libraries to add support for AMQP yet.


fix: Example compute\resource-manager\Microsoft.Compute

$top is an integer

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

Can one of the admins verify this patch?


Upgrade puppet-brewcask dependency

It looks like something has changed in the ecosystem. I started seeing
errors running boxen:
Error: Execution of 'brew boxen-latest brew-cask' returned 1: Error: No available formula with the name "brew-cask"
Error: /Stage[main]/Brewcask/Package[brew-cask]/ensure: change from absent to present failed: Execution of 'brew boxen-latest brew-cask' returned 1: Error: No available formula with the name "brew-cask"

And all of my boxen::personal::osx_apps would be skipped.
This change reflects the fact that cask now comes with brew now.

Fixes #824.

I'm not convinced this is going to solve the issue as the version bump only manages the brewcask tasks within homebrew itself. Would you be able to elaborate a little more on your reasoning here? I'm all for getting this updated regardless but I don't want to close off #824 if it's not related.
Have you also tried brew update && brew upgrade to ensure it's not something to do with an outdated homebrew installation?

Had experienced that last week but after seeing the latest puppet-brewcask version, I changed my Puppetfile same as the changes of @jabley then it solves the problem.

My side thought here is that the Puppetfile change may have initiated the update/upgrade itself so version bumping was an indirect fix. Does that make sense? For what it's worth, I haven't delved too deep into that code (yet!) but plan to in the coming months so either way I'm happy here.

brew update && brew upgrade had not fixed this for me, hence the reason I went digging and found the change in the puppet module.
Also saw the problem on multiple machines.


Use of github.com/bugsnag/osext instead of github.com/kardianos/osext

Problem
github.com/bugsnag/osext is imported in panicwrap_test.go
But https://github.com/bugsnag/panicwrap is using github.com/kardianos/osext
Is this intentional?
Expected
That both bugsnag-go and panicwrap would import the same version of osext.
(github.com/kardianos/osext)
Note
I found this issue while trying to use dep to vendor bugsnag-go.
Since bugsnag-go depends on github.com/bugsnag/osext then the latest version of github.com/bugsnag/panicwrap that can be used is https://github.com/bugsnag/panicwrap/tree/1.1.0 instead of the (i believe) intended master branch.

We haven't noticed this issue when using govendor since it removes test files (panicwrap_test.go)

Thanks for the report, @peterhellberg. This looks like an oversight from bugsnag/panicwrap#3. Updating accordingly.


Add numerical support of other real types (linear_advection)

Continue #1909.
Linear advection seems easier to review and merge, so I do these first in equations.
Tasks:

[x] linear_scalar_advection 1d, 2d, 3d
[ ] unit tests for above

Okay

Ready for final review @ranocha :/


[BUG] After send request to stake, can not unstake

Describe the Bug
When send request to stake, we can not unstake in android r2.1.4, but I can unstake in ios. We need to stay consistent.
When we send a request to stake, flow port will show information like  below.

In ios app version 2.1.3(6), the staking information is shown. And when we click unstake, the available amount is 50 flow. So we can unstake the committed amount

But in Android and extension, the available account is 0 flow. So we can not unstake the commited amount.

Expected experience
Can unstake committed amount in Android and extension.
Steps To Reproduce

Go to staking page.
staking with a new node.
click unstake button

Environment
-Android r2.1.4
-Extension 2.1.8

IOS version use below script:
https://www.flowdiver.io/tx/dc2f8737455bda52cd6d7190e26bef8af475a27dfbd343253379a3e1be7d6224?tab=script

This issue already fixed in Android prod version i1.4.13


test webhook

testing webhook

Hi Phosters I am happy to work with u and clarify your doubts regarding testing webhook. please explain your concern


Lily interpreter locks up when instantiating a class with a constructor taking an optional parameter.

This code appears to lock up the lily (867d7f40b2b78342d0ce3468167ed871907e448f) interpreter:
class Test(value: *Integer = 10) {
	define output {
		print(value)
	}
}

var test = Test()

On OS X 10.11.6 it will run for at least 30+ seconds:
$ time ../build/lily lockup.lly
^C

real	0m33.957s
user	0m29.831s
sys	0m1.835s
$

I'm unsure if it eventually finishes executing. Haven't let it run for more than about 30 seconds.
It showed the same behaviour on Ubuntu Linux 16.04.

Hey, that's a name that I haven't seen in a while. As for this bug, I think it's a duplicate of what #183 is talking about (optional arguments and closures don't mix well). But just in case it's not, I'm going to leave this open for the time being.


Add support for alternative menu animation

Description
Add support for legacy Material Design 2 animation
https://kstatic.googleusercontent.com/files/e640e0522edecb81d7957409e9277cde9728adade05a4929bcbbf46f4acfb3af8478f9d0146d55e5baa53ed53f82f14925dedd7add889137d4c5e1a1e1180a51

Providing M2 animations is out of scope for this library, which implements M3.
See https://github.com/material-components/material-web/discussions/5549#discussioncomment-8933947 for more info on plans to support customizable motion.