Postconditions of websocket::stream::async_close are not documented

Version of Beast: Boost 1.83.0
The documentation for websocket::stream::async_close does not specify what happens to the underlying TCP socket in both success and error paths (same goes for websocket::stream::close).
I'm guessing the teardown customization point has something to do with this, but there is no mention of it in the async_close documentation.
In particular, I need to know if the underlying TCP socket is closed when websocket::stream::async_close completes either successfully or with an error.
I know that I can do if (websocket_.next_layer().is_closed()) in the completion handler to find out at runtime, but I'd still like to know the behavior.
ADDENDUM: websocket::stream::async_close also does not document whether is_open() == false is a postcondition whether or not the operation succeeds. I would expect is_open() == false to always be a postcondition whether or not it succeeds.

I have a question related to this. When websocket::stream::async_close fails, will read operations receive an error (so that the application knows to end)?

What happens to the tcp socket depends on the other side. I think !is_open() is not a post-condition.
It sends the close frame to the other side, so the server might decide to just drop the connection at this point without a response (unlikely, but possible) in which case you'd get an error from the tcp layer. This would also apply to your second question.
But ideally, you'd send the close-frame to the server, which then initialized an ordered teardown, then tears down the ssl layer (which google usually skips) and then closes the socket.

I have refactored my server logic to not depend on websocket::stream::is_open.
I now also destroy the websocket::stream upon completion of websocket::stream::async_close (regardless of success/failure), so that should take care of closing the underlying TCP socket.

I now also destroy the websocket::stream upon completion of websocket::stream::async_close (regardless of success/failure), so that should take care of closing the underlying TCP socket.

Oops, I think that would violate this note from the websocket::stream destructor documentation:

A stream object must not be destroyed while there are pending asynchronous operations associated with it.

...as the websocket::async_read operation might still be pending.
The Asio sockets are more robust in this respect, as calling close or the destructor cancels all pending asynchronous operations.

As requested by the author here, I'm bumping this issue so that the relationship between websocket::stream::async_close and teardown is better documented:

There's no mention of "teardown" operations in the websocket::stream::close documentation, so one needs to have a least glanced at the entire documentation to be aware that his mechanism exists, and remember that it exists. I have 1485 other things I have to constantly keep in my head, so it's easy for me to forget that websocket::stream::close performs a customizable teardown operation. :grin:  Just a note with a link to the Teardown page in the websocket::stream::close documentation should suffice.
It's not clear if the teardown operation is completed or is kicked off by time the websocket::stream::async_close handler is invoked.
The Teardown documentation page does not describe what the default teardown operation actually does. It sorta implies that the default teardown is per RFC6455 section 7.1.1., but it would be better if this were explicitly stated.
It's not clear what state the underlying TCP socket is in if the websocket::stream::close operation fails. With Asio, ip::tcp::socket::close is a no-fail operation and I can count on the socket being actually closed from my perspective.

I've also been confused by this, but wrote some code that appeared to work well for a few years. But then beast::ssl_stream was deprecated and it started crashing in some cases. At least, in new code, it looks like closing a websocket::stream will close the socket and everything «just works» if you're using ssl or tcp as in the examples? =)

But then beast::ssl_stream was deprecated and it started crashing in some cases. At least, in new code.

The new changes shouldn't affect this behavior. Did you make any other changes to your code? In what scenario does your code crash? Could you provide a minimal reproducible example?

Is that only true if you use a boost::beast::ip::tcp::socket or boost::asio::ssl::stream? Is it true for boost::asio::tcp_stream as well? What about boost::asio::generic::stream_protocol::socket?
I have tried to read the documentation mentioned by @ecorm and agree that the documentation should be clear about this stuff. =)

Is that only true if you use a boost::beast::ip::tcp::socket or boost::asio::ssl::stream? Is it true for boost::asio::tcp_stream as well? What about boost::asio::generic::stream_protocol::socket?

Sorry, which part are you referring to?

Sorry, which part are you referring to?

The part here:

You only need to initiate a websocket::stream::async_close. It handles everything for you.

The async_close / teardown customization stuff doesn't make that perfectly clear.

That's great news. It would be great if the documentation could be equally clear =)


update environment.yml with seaborn dependencies

After installing (or removing) any additional dependencies, running conda env export > environment.yml will overwrite the existing environment.yml to reflect any changes in the environment.

Error Message:

['/usr/local/miniconda/bin/python', '-m', 'pip', 'install', '-U', '-r', '/Users/runner/work/care_nlp_psych/care_nlp_psych/condaenv.4hs5zme_.requirements.txt', '--exists-action=b']
CondaEnvException: Pip failed
Pip subprocess output:

failed
Error: Process completed with exit code 1.

Checked stack  and possible fix could be updating conda with conda update -n base -c defaults conda


Updating cfi-js dependency

Manual testing showed no errors (rendering proper page, page navigation, navigate to bookmarks/toc).

Thanks!


MINOR: Raft request thread should discover api versions

We do not plan to rely on the IBP in order to determine API versions for raft requests. Instead, we want to discover them through the ApiVersions API. This patch enables the flag to do so.
Also fix a small shutdown bug. Current logic closes the log twice: once in KafkaRaftClient, and once in RaftManager. This can lead to errors like the following:
[2021-02-18 18:35:12,643] WARN  (kafka.utils.CoreUtils$)
java.nio.channels.ClosedChannelException
        at java.base/sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:150)
        at java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:452)
        at org.apache.kafka.common.record.FileRecords.flush(FileRecords.java:197)
        at org.apache.kafka.common.record.FileRecords.close(FileRecords.java:204)
        at kafka.log.LogSegment.$anonfun$close$4(LogSegment.scala:592)
        at kafka.utils.CoreUtils$.swallow(CoreUtils.scala:68)
        at kafka.log.LogSegment.close(LogSegment.scala:592)
        at kafka.log.Log.$anonfun$close$4(Log.scala:1038)
        at kafka.log.Log.$anonfun$close$4$adapted(Log.scala:1038)
        at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
        at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
        at scala.collection.AbstractIterable.foreach(Iterable.scala:919)
        at kafka.log.Log.$anonfun$close$3(Log.scala:1038)
        at kafka.log.Log.close(Log.scala:2433)
        at kafka.raft.KafkaMetadataLog.close(KafkaMetadataLog.scala:295)
        at kafka.raft.KafkaRaftManager.shutdown(RaftManager.scala:150)

I have tended to view RaftManager as owning the lifecycle of the log, so I removed the extra call to close in KafkaRaftClient.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

We do not plan to rely on the IBP in order to determine API versions for raft requests. Instead, we want to discover them through the ApiVersions API. This patch enables the flag to do so.

How or where do we check that the connected nodes support the versions we require? Is that coming in a future PR?

@jsancio I may be misunderstanding your question, but api versions are negotiated internally in NetworkClient. If there are no compatible versions, then the client will raise an unsupported version error.
It looks like it would be useful to have at least one test case to verify the expected behavior. At a glance, I could not find any logic to check the returned ClientResponse for version errors.

Okay. I guess we need another KIP that explains how to upgrade a cluster and to determine when it is safe to enable the RaftClient on all of the brokers of a cluster.

Yes, a KIP describing the upgrade process will be necessary. I think api version negotiation is probably the least of our concerns 😆 .

We are missing the handling of authentication and unsupported version exceptions in BrokerToControllerChannelManager. I am working on the test cases now and will submit an update shortly.

I opened a separate PR for the close() bug fix: https://github.com/apache/kafka/pull/10168


Remove InvertibleAdapterConfig class

Remove InvertibleAdapterConfig class and integrate its keys directly into the base adapter config.
Has addition in __setattr__ of AdapterConfig for backwards compatibility.

Yeah, should've been a bit more clear about this:
The nested InvertibleAdapterConfig was a bit unpractical to use if you would want to change the config, i.e. you would have to first instantiate a new invertible config object class and then assign it to the actual config:
inv_config = InvertibleAdapterConfig(block_type="nice", ...)
config = PfeifferConfig().replace(invertible_adapter=inv_config)

Now, you can treat the inv config keys like any other config key:
config = PfeifferConfig().replace(inv_adapter="nice", ...)

or
config = AdapterConfig.load("pfeiffer", inv_adapter="nice")

(I also think someone brought this up as an issue a long time back :)


python3Packages.mcstatus: 6.1.0 -> 6.1.2

Motivation for this change
Update to latest upstream release 6.1.2
https://github.com/Dinnerbone/mcstatus/releases/tag/v6.1.2
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128187 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.mcstatus
python39Packages.mcstatus

@fabaff merge conflict.

Result of nixpkgs-review pr 128187 run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built:

python38Packages.mcstatus
python39Packages.mcstatus

Build failure on linux

Successfully installed homeassistant-2021.6.6
/tmp/nix-build-homeassistant-2021.6.6.drv-0/source
Finished executing pipInstallPhase
@nix { "action": "setPhase", "phase": "fixupPhase" }
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qbbllv468xipcrg67i85csln4p2fd8pb-homeassistant-2021.6.6
patching script interpreter paths in /nix/store/qbbllv468xipcrg67i85csln4p2fd8pb-homeassistant-2021.6.6
checking for references to /tmp/nix-build-homeassistant-2021.6.6.drv-0/ in /nix/store/qbbllv468xipcrg67i85csln4p2fd8pb-homeassistant-2021.6.6...
Rewriting #!/nix/store/2nhfiak8a30vw67mxksc2kdb69np2jcw-python3-3.8.9/bin/python3.8 to #!/nix/store/2nhfiak8a30vw67mxksc2kdb69np2jcw-python3-3.8.9
wrapping `/nix/store/qbbllv468xipcrg67i85csln4p2fd8pb-homeassistant-2021.6.6/bin/hass'...
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
@nix { "action": "setPhase", "phase": "installCheckPhase" }
running install tests
no Makefile or custom installCheckPhase, doing nothing
@nix { "action": "setPhase", "phase": "pythonCatchConflictsPhase" }
pythonCatchConflictsPhase
@nix { "action": "setPhase", "phase": "pythonRemoveBinBytecodePhase" }
pythonRemoveBinBytecodePhase
@nix { "action": "setPhase", "phase": "pythonImportsCheckPhase" }
pythonImportsCheckPhase
Executing pythonImportsCheckPhase
@nix { "action": "setPhase", "phase": "pytestCheckPhase" }
pytestCheckPhase
Executing pytestCheckPhase
mkdir: cannot create directory ‘/build/media’: No such file or directory

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 128187 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.mcstatus
python39Packages.mcstatus


Consider using synchronization context to serialize LS calls

Per https://github.com/Microsoft/vs-streamjsonrpc/issues/88 instead of using home-grown solution when we wait until doc change processing completes.

This is done


[Docs] import/no-named-as-default: Fix typo

add semicolon.

Coverage decreased (-2.0%) to 95.905% when pulling 985e05ad879426f5b4657ab2f5ff6d761e3d6b91 on bicstone:import/no-named-as-default-Fix-typo into bbe529a4ffe7ddb76a1620e55c90be884400456f on benmosher:master.

Coverage decreased (-2.0%) to 95.905% when pulling 985e05ad879426f5b4657ab2f5ff6d761e3d6b91 on bicstone:import/no-named-as-default-Fix-typo into bbe529a4ffe7ddb76a1620e55c90be884400456f on benmosher:master.


support for statistical checkers

Add  --statistics-collect option to analyze which switches on experimental statistics collection checkers:

statisticsCollector.ReturnValueCheck
statisticsCollector.SpecialReturnValue

The option will only be shown if the checkers are available.
The statistics will be stored into in <REPORT-DIR>/statistics directory.
If any of the

api.SpecialReturnValue
api.UncheckedReturnValue

checkers are switched on, look for statistics file in the <REPORT-DIR>/statistics directory.
Introduce a new optional analyze argument --preanalize-dir <PREANALYZE-DIR> which is a <REPORT_DIR> with the CTU and statistics pre-analysis results.
Using this parameter it will be possible to share the pre-analysis results between multiple analysis runs. So if this parameter is given, the --ctu-analyze and the ctu-on-the-fly, and the statistical checkers will search for the CTU and statistics interim files in <PRE-ANALYZE-DIR>/ctu and <PRE-ANALYZE-DIR>/statistics directories.

Are these options OK like this? What do you think?

So I read it correctly that --preanalyze-dir is by default same as <OUTPUT_DIR> (the name of the opstring is NOT report-dir but output-dir!), but we can set it to something else?
I don't like the phrase preanalyze-dir. A better string should be found, one that conveys the fact that extra analysis resources are stored here.


Update auto-generated documentation

Repository: openmicroscopy/ome-documentation
Already up-to-date.
Generated by build OMERO-5.1-latest-docs-autogen#534.

--no-rebase

Looks fine on staging


/profile body parameters: required not omittable

This is a simple clarification hopefully not needing too much time. The current API definition says that displayname and avatar_url in /profile/{}/displayname and /profile/{}/avatar_url respectively are not required. However, Synapse complains - and I think rightfully - when I completely omit the parameter (in a wrong way but that's a separate issue). Should Synapse or the spec be fixed?

In conduit I implemented it so that omitting the parameter will remove info about displayname/avatar_url from your profile, maybe synapse should do something like this too?

Currently removing your profile data is basically undefined in the spec. Element/matrix-org bridges set the strings to be "", but that's not really correct either. Ideally we should spell out in the spec what a removed profile looks like (is the value set to null, empty string or undefined) and how to remove it (DELETE endpoint, omitting the key in the PUT, setting the value to null/empty-string)

Defining semantics for profile info deletion would certainly be great but my question is simpler: as of now (without MSCs), should {} (instead of { "displayname": "" }) be allowed as a body of, say, /displayname, and be treated as clearing the displayname? or should homeservers reject it as invalid?


Week 8 readme refers to nonexistent seminar

https://github.com/yandexdataschool/nlp_course/blob/master/week08_multitask/README.md refers to seminar.ipynb which does not exist anymore, and claims that there is no homework for the week, despite the presence of homework.ipynb in the directory.

Thank you! It should've pointed to homework notebook


quickstart: Updated documentation for version 9 of the patch set

This is the latest quick start guide based on the Linux Secure Launch version 10 patch set that will get posted to LKML in the near future.

This repository is in the process of archivization. Could you move this PR to https://github.com/TrenchBoot/TrenchBoot.github.io/?


Ctrl+Tab in Web

Just perusing the Imgui Manual this morning and came across the part where it says Ctrl+Tab selects window. This won't work on emscripten because that is already bound to change tabs.Not sure what to do about this. Could use vim bindings (Ctrl+w, Ctrl+Shift+w) but those are not as well known to the world. Alt+Tab is in uded in most OSes. Could use Ctrl+Alt+tab but it's cumbersome...
Anyhow, my point was just to catalog the issue for others. - This may be something to bring up to the main Imgui repo. dunno...
Thoughts?

Hum, this is not easy, since this key combination seems to be hardcoded in imgui.cpp, see https://github.com/ocornut/imgui/blob/master/imgui.cpp#L9057

You're right. Seems like this needs to be up-streamed. I thought maybe his could be fixed in the imgui_impl_xxx.cpp file for Emscripten. But the more I dig the more I realize this is NOT trivial to bolt on to change things.
Ideally, this needs to be configurable by each implementation. Probably Alt+Left/Right Arrow would be the most comfortable. But each app should have it's own control over such things...
I'll upstream this and see where it goes...


Rename Repository

Want to run this by some peeps. I personally like repositories with all lowercase names so would people be ok if we renamed this repo similarly to how we did the live site. E.g:
RevolutionUC-Website => revolutionuc-website
Idk personally I think it would look better in file systems and match the naming convention of other repos in this org.

@noahbass

I noticed you changed it to revolutionuc-website-legacy @domfarolino I'm okay with that, but should we add a date to it? I imagine at some point the currently in development site will become the legacy site. My suggested name is revolutionuc-website-prior2016 or sometheing like that


Jest doesn't output anything

🐛 Bug Report
When i try to run node_modules/.bin/jest it does nothing, outputs one empty line
No errors in Developers Tools
node_modules/.bin/jest --debug shows config and then stucks
Env
System:
    OS: macOS High Sierra 10.13.4
    CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 10.0.0 - /usr/local/bin/node
    Yarn: 1.6.0 - /usr/local/bin/yarn
    npm: 5.6.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^22.0.4 => 22.4.3

Sorry, seems to be a watchman issue,  when run with --no-watchman everything works as expected

I'm getting this issue aswell.
It seems that it happens when /proc/sys/fs/inotify/max_user_watches /proc/sys/fs/inotify/max_queued_events /proc/sys/fs/inotify/max_user_instances have a low value.
But it I increase their values and run jest then my system stops responding, seeming that it cannot access the hard drive (cpu and memory seem fine).
And it only happens sometimes.
I'm running jest with the --no-watchman command but I had to disable VSCode extension as it will use watchman and break my system.

Got the same issue, it works again after brew reinstall watchman.


TypeConverter sample code with possible error

When the database final attribute has null value the DateTimeConverter will throws an error when it's convert a null value.
So I have made a correction with try catch to avoid it. May you could update the example on README.md.
class DateTimeConverter extends TypeConverter<DateTime, int> {
  @override
  DateTime decode(int databaseValue) {
    try {
      return DateTime.fromMillisecondsSinceEpoch(databaseValue);
    } catch (e) {
      return null;
    }
  }

  @override
  int encode(DateTime value) {
    try {
      return value.millisecondsSinceEpoch;
    } catch (e) {
      return null;
    }
  }
}

The code above was my fix to documentation, it will be nice to update the docs to help the community. As I got no response from team I am closing it.

@cassioseffrin sorry for the late reply. Feel free to open a PR to improve the project's documentation.

Ok @vitusortner please check the PR:  https://github.com/cassioseffrin/floor/pull/1 . I am not sure I have made it in correct branch.

@vitusortner  I have made the PR, please check it here https://github.com/vitusortner/floor/pull/442
Thks!


RTE in multi field displays blank even if values present

Hi @rohan-pulekar, @davidjgonzalez
I had tried reproducing this issue. But whether I use JSON_STORE or NODE_STORE type structure, I get the values in rte.
Below are the snapshot for the same:

JSON_STORE

And in crx it is:

NODE_STORE

And in crx-de

Also, I tried the same in classic UI(as it is not specified anywhere), I got the same result:

In crx-de:

Hi manisha199010 ,
I am facing the same issue. The Rte in multifield is not retaining the values on re-opening the dialog. Could you please share your package . Also let me know which AEM version you are using.

Hi @asahu02 ,
I had used AEM 6.2.
And this is the touch UI dialog I'm using:
touchui_dialog.txt


How to solve the problem of not supporting Chinese search?

After cloning the code library, modifying the case, adding Chinese options, and using @ to search, it was found that English is acceptable, but Chinese is not.


Post-reconfiguration: remove Base and Counter classes

Maybe transfer them to a core or utils package.
Counter class could just be replaced by a timestamp parameter, like the used in game-meter.

Fixed in https://github.com/dimensionalpocket/game-input-js/pull/127.


gcc11: update darwin support patch to 11.5.0

https://github.com/NixOS/nixpkgs/pull/328380 updated gcc11 from 11.4.0 to 11.5.0 but the darwin patch was not ready then. Let's update it in hopes that it fixed darwin build.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

re breakage
on master x86_64-darwin builds for me
uname -a
Darwin admins-iMac-Pro.local 22.6.0 Darwin Kernel Version 22.6.0: Mon Apr 22 20:54:28 PDT 2024; root:xnu-87<IP_ADDRESS>5.2~1/RELEASE_X86_64 x86_64
admins-iMac-Pro:nixpkgs admin$ nix-build -A gcc11
/nix/store/mwayysnr1af7lg8snb9q48z0vb2a0inx-gcc-wrapper-11.5.0

@gen740 can you provide more info re failure ? and if this PR fixes issue

My environment is as follows:
> nix-shell -p nix-info --run "nix-info -m"
install: skipping file '/dev/fd/63', as it was replaced while being copied
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.6.0, macOS 14.6.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

And the error log from nix-shell -p pkgs.gcc11 (before applying this PR):

Error Log

install: skipping file '/dev/fd/63', as it was replaced while being copied
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
install: skipping file '/dev/fd/63', as it was replaced while being copied
$CPATH is `/nix/store/vb7baj6dq2mvynfh6zmwxz57w83h7w0q-zlib-1.3.1-dev/include'
$LIBRARY_PATH is `/nix/store/y1wp3g6pibvvfjbh5f2k4h2rn140sd1w-zlib-1.3.1/lib'
/nix/store/r3yx58nvr5znhwx3478xs7zaqcpzmlwk-stdenv-darwin/setup: line 268: /nix/store/2wdcsq99cxgcqymfygwvqby4slcrb1nb-cctools-binutils-darwin-wrapper-1010.6/nix-support/libc-ldflags-before: No such file or directory
/nix/store/r3yx58nvr5znhwx3478xs7zaqcpzmlwk-stdenv-darwin/setup: line 268: /nix/store/2wdcsq99cxgcqymfygwvqby4slcrb1nb-cctools-binutils-darwin-wrapper-1010.6/nix-support/libc-ldflags-before: No such file or directory
unpacking source archive /nix/store/88r55xwbifxajhamwd40mh0gdygss920-gcc-11.5.0.tar.xz
source root is gcc-11.5.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gcc-11.5.0/MD5SUMS
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
install: skipping file '/dev/fd/63', as it was replaced while being copied
applying patch /nix/store/8bl27bnyrs5s6hw33xvbh5msxh5zsqjy-fix-bug-80431.patch
patching file gcc/cp/tree.c
Hunk #1 succeeded at 3252 (offset 10 lines).
patching file gcc/testsuite/g++.dg/cpp0x/nsdmi-virtual1a.C
applying patch /nix/store/pz03lhak99nzyyni72m14zsjzfjvqvr8-no-sys-dirs.patch
patching file gcc/cppdefault.c
patching file gcc/gcc.c
Hunk #1 succeeded at 1588 (offset 426 lines).
applying patch /nix/store/k346ih554hrnzq136jps90xq7v11z3vc-no-sys-dirs-riscv.patch
patching file gcc/config/riscv/linux.h
Hunk #1 succeeded at 71 (offset 2 lines).
applying patch /nix/store/632b0y5mkcdwbsw2g3xh5qznw2vv5axr-ppc-musl.patch
patching file gcc/config/rs6000/sysv4.h
Hunk #1 succeeded at 966 (offset -30 lines).
applying patch /nix/store/m4q8mcyx12nr1dabsk2z88g8nnqg5j51-ff4bf326d03e750a8d4905ea49425fe7d15a04b8..gcc-11.4-darwin-r0.diff
patching file Makefile.def
patching file Makefile.in
patching file Makefile.tpl
patching file c++tools/resolver.cc
patching file c++tools/resolver.h
patching file c++tools/server.cc
patching file config/gcc-plugin.m4
patching file config/mh-darwin
patching file configure
patching file configure.ac
patching file fixincludes/configure
patching file gcc/Makefile.in
patching file gcc/aclocal.m4
patching file gcc/ada/gcc-interface/Make-lang.in
patching file gcc/ada/gcc-interface/Makefile.in
Hunk #1 FAILED at 793.
1 out of 1 hunk FAILED -- saving rejects to file gcc/ada/gcc-interface/Makefile.in.rej
patching file gcc/ada/gcc-interface/decl.c
patching file gcc/ada/sigtramp-ios.c
patching file gcc/builtins.def
patching file gcc/c-family/c-attribs.c
Hunk #3 succeeded at 4117 (offset -4 lines).
patching file gcc/c-family/c-opts.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file gcc/c-family/c-opts.c.rej
patching file gcc/c-family/c-pch.c
Hunk #4 succeeded at 371 (offset -1 lines).
patching file gcc/c/c-decl.c
Hunk #7 succeeded at 9026 (offset 15 lines).
Hunk #8 succeeded at 10819 (offset 15 lines).
patching file gcc/c/c-tree.h
patching file gcc/c/c-typeck.c
patching file gcc/calls.c
patching file gcc/calls.h
patching file gcc/common.opt
patching file gcc/config.gcc
patching file gcc/config.host
patching file gcc/config.in
Hunk #3 succeeded at 2239 (offset 12 lines).
patching file gcc/config/aarch64/aarch64-builtins.c
patching file gcc/config/aarch64/aarch64-c.c
Hunk #1 succeeded at 369 (offset 5 lines).
patching file gcc/config/aarch64/aarch64-protos.h
patching file gcc/config/aarch64/aarch64-sve-builtins.cc
patching file gcc/config/aarch64/aarch64.c
Hunk #26 succeeded at 10434 (offset 58 lines).
Hunk #27 succeeded at 10442 (offset 58 lines).
Hunk #28 succeeded at 10460 (offset 58 lines).
Hunk #29 succeeded at 10516 (offset 58 lines).
Hunk #30 succeeded at 11249 (offset 58 lines).
Hunk #31 succeeded at 11455 (offset 58 lines).
Hunk #32 succeeded at 11781 (offset 58 lines).
Hunk #33 succeeded at 11812 (offset 58 lines).
Hunk #34 succeeded at 11872 (offset 58 lines).
Hunk #35 succeeded at 11886 (offset 58 lines).
Hunk #36 succeeded at 12034 (offset 58 lines).
Hunk #37 succeeded at 12511 (offset 58 lines).
Hunk #38 succeeded at 12552 (offset 58 lines).
Hunk #39 succeeded at 12656 (offset 58 lines).
Hunk #40 succeeded at 14749 (offset 58 lines).
Hunk #41 succeeded at 17940 (offset 58 lines).
Hunk #42 succeeded at 18859 (offset 58 lines).
Hunk #43 succeeded at 18898 (offset 58 lines).
Hunk #44 succeeded at 18928 (offset 58 lines).
Hunk #45 succeeded at 19076 (offset 58 lines).
Hunk #46 succeeded at 19087 (offset 58 lines).
Hunk #47 succeeded at 19165 (offset 58 lines).
Hunk #48 succeeded at 19262 (offset 58 lines).
Hunk #49 succeeded at 19449 (offset 58 lines).
Hunk #50 succeeded at 19531 (offset 58 lines).
Hunk #51 succeeded at 20317 (offset 58 lines).
Hunk #52 succeeded at 20337 (offset 58 lines).
Hunk #53 succeeded at 22199 (offset 58 lines).
Hunk #54 succeeded at 22262 (offset 58 lines).
Hunk #55 succeeded at 22898 (offset 60 lines).
Hunk #56 succeeded at 22916 (offset 60 lines).
Hunk #57 succeeded at 22934 (offset 60 lines).
Hunk #58 succeeded at 25884 (offset 60 lines).
Hunk #59 succeeded at 26647 (offset 70 lines).
Hunk #60 succeeded at 26870 (offset 70 lines).
Hunk #61 succeeded at 26965 (offset 70 lines).
Hunk #62 succeeded at 27307 (offset 70 lines).
patching file gcc/config/aarch64/aarch64.h
Hunk #3 succeeded at 994 (offset 10 lines).
Hunk #4 succeeded at 1295 (offset 10 lines).
Hunk #5 succeeded at 1315 (offset 10 lines).
patching file gcc/config/aarch64/aarch64.md
Hunk #3 succeeded at 6741 (offset 1 line).
Hunk #4 succeeded at 6755 (offset 1 line).
patching file gcc/config/aarch64/aarch64.opt
patching file gcc/config/aarch64/constraints.md
patching file gcc/config/aarch64/falkor-tag-collision-avoidance.c
patching file gcc/config/aarch64/predicates.md
patching file gcc/config/avr/avr.c
patching file gcc/config/darwin-driver.c
patching file gcc/config/darwin.c
Hunk #2 succeeded at 129 (offset 13 lines).
Hunk #3 succeeded at 145 (offset 13 lines).
Hunk #4 succeeded at 1063 (offset 13 lines).
Hunk #5 succeeded at 1219 (offset 13 lines).
Hunk #6 succeeded at 1964 with fuzz 2 (offset 28 lines).
Hunk #7 succeeded at 2270 (offset 29 lines).
Hunk #8 succeeded at 3120 (offset 57 lines).
Hunk #9 FAILED at 3630.
Hunk #10 FAILED at 3658.
2 out of 10 hunks FAILED -- saving rejects to file gcc/config/darwin.c.rej
patching file gcc/config/darwin.h
Hunk #3 succeeded at 297 with fuzz 2.
Hunk #4 succeeded at 415 (offset 2 lines).
Hunk #5 succeeded at 495 (offset 2 lines).
Hunk #6 succeeded at 517 (offset 2 lines).
Hunk #7 FAILED at 526.
Hunk #8 succeeded at 569 (offset 7 lines).
Hunk #9 succeeded at 596 (offset 7 lines).
1 out of 9 hunks FAILED -- saving rejects to file gcc/config/darwin.h.rej
patching file gcc/config/darwin.opt
Hunk #1 succeeded at 241 (offset 4 lines).
patching file gcc/config/host-darwin.c
patching file gcc/config/host-darwin.h
patching file gcc/config/host-hpux.c
patching file gcc/config/host-linux.c
patching file gcc/config/host-netbsd.c
patching file gcc/config/host-openbsd.c
patching file gcc/config/host-solaris.c
patching file gcc/config/i386/darwin.h
patching file gcc/config/i386/host-mingw32.c
patching file gcc/config/i386/i386.c
Hunk #1 succeeded at 23916 (offset 60 lines).
patching file gcc/config/i386/i386.h
Hunk #1 succeeded at 955 (offset 2 lines).
patching file gcc/config/pa/pa.c
patching file gcc/config/rs6000/rs6000.c
Hunk #1 succeeded at 20233 (offset -8 lines).
Hunk #2 succeeded at 20937 (offset -8 lines).
Hunk #3 succeeded at 20996 (offset -8 lines).
patching file gcc/configure
Hunk #8 FAILED at 3759.
Hunk #9 succeeded at 17653 (offset 23 lines).
Hunk #10 succeeded at 17711 (offset 23 lines).
Hunk #11 FAILED at 19486.
Hunk #12 FAILED at 19592.
Hunk #13 succeeded at 20491 (offset 23 lines).
Hunk #14 succeeded at 20549 (offset 23 lines).
Hunk #15 succeeded at 22918 (offset 23 lines).
Hunk #16 FAILED at 30821.
Hunk #17 FAILED at 30844.
Hunk #18 FAILED at 30865.
Hunk #19 succeeded at 30960 with fuzz 1 (offset 80 lines).
Hunk #20 succeeded at 32406 (offset 80 lines).
Hunk #21 succeeded at 32449 (offset 80 lines).
Hunk #22 succeeded at 32611 (offset 80 lines).
Hunk #23 succeeded at 33135 (offset 80 lines).
6 out of 23 hunks FAILED -- saving rejects to file gcc/configure.rej
patching file gcc/configure.ac
Hunk #1 FAILED at 236.
Hunk #2 succeeded at 2543 (offset 22 lines).
Hunk #3 FAILED at 6344.
Hunk #4 FAILED at 6365.
Hunk #5 FAILED at 6382.
Hunk #6 FAILED at 6391.
Hunk #7 succeeded at 7678 (offset 45 lines).
5 out of 7 hunks FAILED -- saving rejects to file gcc/configure.ac.rej
patching file gcc/coretypes.h
patching file gcc/cp/call.c
Hunk #1 succeeded at 9430 (offset -5 lines).
Hunk #2 succeeded at 9507 (offset -5 lines).
patching file gcc/cp/class.c
Hunk #1 succeeded at 5769 (offset 1 line).
Hunk #2 succeeded at 5798 (offset 1 line).
patching file gcc/cp/cp-tree.h
Hunk #1 succeeded at 6504 (offset 1 line).
patching file gcc/cp/decl.c
Hunk #2 succeeded at 11835 (offset 2 lines).
Hunk #3 succeeded at 14498 (offset 2 lines).
Hunk #4 succeeded at 14594 (offset 2 lines).
patching file gcc/cp/decl.h
patching file gcc/cp/decl2.c
patching file gcc/cp/g++spec.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/cp/g++spec.c.rej
patching file gcc/cp/module.cc
patching file gcc/cp/name-lookup.c
patching file gcc/cp/parser.c
patching file gcc/cp/typeck.c
patching file gcc/cp/typeck2.c
patching file gcc/doc/extend.texi
patching file gcc/doc/gty.texi
patching file gcc/doc/invoke.texi
Hunk #3 succeeded at 16124 (offset 2 lines).
Hunk #4 succeeded at 16192 (offset 2 lines).
patching file gcc/doc/tm.texi
patching file gcc/doc/tm.texi.in
patching file gcc/function.c
patching file gcc/function.h
patching file gcc/gcc.c
patching file gcc/gengtype-state.c
patching file gcc/gengtype.c
patching file gcc/gengtype.h
patching file gcc/ggc-common.c
patching file gcc/ggc-tests.c
patching file gcc/ggc.h
patching file gcc/ginclude/stddef.h
patching file gcc/hash-map.h
patching file gcc/hash-set.h
patching file gcc/hash-table.h
patching file gcc/hash-traits.h
patching file gcc/hosthooks-def.h
patching file gcc/hosthooks.h
patching file gcc/jit/Make-lang.in
Hunk #1 succeeded at 69 (offset 10 lines).
patching file gcc/machmode.h
patching file gcc/objc/objc-act.c
Hunk #1 succeeded at 1305 (offset 3 lines).
Hunk #2 succeeded at 1443 (offset 3 lines).
Hunk #3 succeeded at 1722 (offset 3 lines).
Hunk #4 succeeded at 1756 (offset 3 lines).
Hunk #5 succeeded at 1809 (offset 3 lines).
Hunk #6 succeeded at 1823 (offset 3 lines).
Hunk #7 FAILED at 3380.
Hunk #8 FAILED at 3393.
Hunk #9 succeeded at 4604 (offset 3 lines).
Hunk #10 succeeded at 5031 (offset 3 lines).
Hunk #11 succeeded at 5497 (offset 3 lines).
Hunk #12 succeeded at 5508 (offset 3 lines).
Hunk #13 succeeded at 5820 (offset 3 lines).
Hunk #14 succeeded at 7002 (offset 3 lines).
Hunk #15 succeeded at 7114 (offset 3 lines).
Hunk #16 succeeded at 7147 (offset 3 lines).
Hunk #17 succeeded at 8176 (offset 3 lines).
Hunk #18 succeeded at 8221 (offset 3 lines).
Hunk #19 succeeded at 8275 (offset 3 lines).
Hunk #20 succeeded at 8302 (offset 3 lines).
Hunk #21 succeeded at 8321 (offset 3 lines).
Hunk #22 succeeded at 8347 (offset 3 lines).
Hunk #23 succeeded at 8358 (offset 3 lines).
Hunk #24 succeeded at 8377 (offset 3 lines).
Hunk #25 succeeded at 8418 (offset 3 lines).
Hunk #26 succeeded at 8949 (offset 3 lines).
Hunk #27 succeeded at 9682 (offset 3 lines).
Hunk #28 FAILED at 9704.
3 out of 28 hunks FAILED -- saving rejects to file gcc/objc/objc-act.c.rej
patching file gcc/objc/objc-next-metadata-tags.h
patching file gcc/objc/objc-next-runtime-abi-01.c
patching file gcc/objc/objc-next-runtime-abi-02.c
Hunk #2 succeeded at 181 (offset 1 line).
Hunk #3 FAILED at 238.
Hunk #4 succeeded at 252 with fuzz 2 (offset 5 lines).
Hunk #5 FAILED at 504.
Hunk #6 FAILED at 1032.
Hunk #7 FAILED at 1672.
Hunk #8 FAILED at 1691.
Hunk #9 FAILED at 1737.
Hunk #10 FAILED at 1787.
Hunk #11 FAILED at 1804.
Hunk #12 FAILED at 1850.
Hunk #13 FAILED at 2118.
Hunk #14 succeeded at 2327 with fuzz 2 (offset 6 lines).
10 out of 14 hunks FAILED -- saving rejects to file gcc/objc/objc-next-runtime-abi-02.c.rej
patching file gcc/objc/objc-runtime-shared-support.c
patching file gcc/output.h
patching file gcc/poly-int.h
patching file gcc/print-tree.c
patching file gcc/stringpool.c
patching file gcc/target.def
patching file gcc/target.h
patching file gcc/targhooks.c
patching file gcc/targhooks.h
patching file gcc/testsuite/g++.dg/abi/aarch64_guard1.C
patching file gcc/testsuite/g++.dg/abi/arm_va_list.C
patching file gcc/testsuite/g++.dg/ext/arm-bf16/bf16-mangle-aarch64-1.C
patching file gcc/testsuite/g++.dg/modules/bad-mapper-1.C
patching file gcc/testsuite/g++.dg/torture/darwin-cfstring-3.C
patching file gcc/testsuite/g++.target/aarch64/bitfield-abi-warning-align16-O2-extra.C
patching file gcc/testsuite/g++.target/aarch64/bitfield-abi-warning-align16-O2.C
patching file gcc/testsuite/g++.target/aarch64/bitfield-abi-warning-align32-O2-extra.C
patching file gcc/testsuite/g++.target/aarch64/bitfield-abi-warning-align32-O2.C
patching file gcc/testsuite/g++.target/aarch64/bitfield-abi-warning-align8-O2.C
patching file gcc/testsuite/g++.target/aarch64/no_unique_address_1.C
patching file gcc/testsuite/g++.target/aarch64/no_unique_address_2.C
patching file gcc/testsuite/g++.target/aarch64/sve/aarch64-sve.exp
patching file gcc/testsuite/g++.target/aarch64/sve/acle/aarch64-sve-acle-asm.exp
patching file gcc/testsuite/g++.target/aarch64/sve/acle/aarch64-sve-acle.exp
patching file gcc/testsuite/g++.target/aarch64/sve2/acle/aarch64-sve2-acle-asm.exp
patching file gcc/testsuite/gcc.dg/builtin-apply2.c
patching file gcc/testsuite/gcc.dg/cwsc1.c
patching file gcc/testsuite/gcc.dg/darwin-segaddr.c
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file gcc/testsuite/gcc.dg/darwin-segaddr.c.rej
patching file gcc/testsuite/gcc.dg/pr26427.c
patching file gcc/testsuite/gcc.dg/pubtypes-2.c
patching file gcc/testsuite/gcc.dg/pubtypes-3.c
patching file gcc/testsuite/gcc.dg/pubtypes-4.c
patching file gcc/testsuite/gcc.dg/tls/pr78796.c
patching file gcc/testsuite/gcc.dg/torture/darwin-cfstring-3.c
patching file gcc/testsuite/gcc.dg/torture/pr100786.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway?   Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/testsuite/gcc.target/i386/memcpy-strategy-10.c.rej
patching file gcc/testsuite/gcc.target/i386/memcpy-strategy-5.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/testsuite/gcc.target/i386/memcpy-strategy-5.c.rej
patching file gcc/testsuite/gcc.target/i386/memset-strategy-5.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/testsuite/gcc.target/i386/memset-strategy-5.c.rej
patching file gcc/testsuite/gcc.target/i386/memset-strategy-7.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/testsuite/gcc.target/i386/memset-strategy-7.c.rej
patching file gcc/testsuite/gfortran.dg/coarray/caf.exp
patching file gcc/testsuite/gfortran.dg/dg.exp
patching file gcc/testsuite/gfortran.dg/pr95690.f90
patching file gcc/testsuite/lib/asan-dg.exp
patching file gcc/testsuite/lib/atomic-dg.exp
patching file gcc/testsuite/lib/scanasm.exp
patching file gcc/testsuite/lib/target-libpath.exp
patching file gcc/testsuite/lib/target-supports.exp
Hunk #1 succeeded at 5831 (offset 19 lines).
Hunk #2 succeeded at 8054 (offset 19 lines).
Hunk #3 FAILED at 9601.
Hunk #4 succeeded at 11075 (offset 26 lines).
1 out of 4 hunks FAILED -- saving rejects to file gcc/testsuite/lib/target-supports.exp.rej
patching file gcc/testsuite/obj-c++.dg/gnu-api-2-class-meta.mm
patching file gcc/testsuite/obj-c++.dg/gnu-api-2-class.mm
patching file gcc/testsuite/obj-c++.dg/torture/strings/const-cfstring-4.mm
patching file gcc/testsuite/obj-c++.dg/torture/strings/const-str-10.mm
patching file gcc/testsuite/obj-c++.dg/torture/strings/const-str-11.mm
patching file gcc/testsuite/obj-c++.dg/torture/strings/const-str-9.mm
patching file gcc/testsuite/objc.dg/gnu-api-2-class-meta.m
patching file gcc/testsuite/objc.dg/gnu-api-2-class.m
patching file gcc/testsuite/objc.dg/torture/strings/const-cfstring-4.m
patching file gcc/testsuite/objc.dg/torture/strings/const-str-10.m
patching file gcc/testsuite/objc.dg/torture/strings/const-str-11.m
patching file gcc/testsuite/objc.dg/torture/strings/const-str-9.m
patching file gcc/tree-cfg.c
patching file gcc/tree-core.h
patching file gcc/tree-nested.c
Hunk #2 succeeded at 2769 (offset 5 lines).
Hunk #3 succeeded at 3366 (offset 5 lines).
Hunk #4 succeeded at 3498 (offset 5 lines).
Hunk #5 succeeded at 3564 (offset 5 lines).
patching file gcc/tree.c
Hunk #1 succeeded at 10770 (offset 1 line).

Hunk #2 succeeded at 834 (offset 1 line).
Hunk #3 succeeded at 1495 (offset 1 line).
Hunk #4 succeeded at 9621 (offset 1 line).
Hunk #5 succeeded at 9679 (offset 1 line).
Hunk #6 FAILED at 11476.
Hunk #7 FAILED at 11582.
Hunk #8 succeeded at 11844 (offset 1 line).
Hunk #9 succeeded at 13527 (offset 1 line).
Hunk #10 succeeded at 13585 (offset 1 line).
Hunk #11 succeeded at 17399 (offset 93 lines).
2 out of 11 hunks FAILED -- saving rejects to file libgomp/configure.rej
patching file libgomp/configure.ac
patching file libiberty/aclocal.m4
patching file libiberty/configure
patching file libiberty/configure.ac
patching file libiberty/simple-object-mach-o.c
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway?   Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file libphobos/testsuite/lib/libphobos.exp.rej
patching file libquadmath/Makefile.am
patching file libquadmath/Makefile.in
patching file libquadmath/configure
patching file libquadmath/configure.ac
patching file libsanitizer/asan/Makefile.am
patching file libsanitizer/asan/Makefile.in
patching file libsanitizer/configure
patching file libsanitizer/configure.ac
patching file libsanitizer/hwasan/Makefile.am
patching file libsanitizer/hwasan/Makefile.in
patching file libsanitizer/lsan/Makefile.am
patching file libsanitizer/lsan/Makefile.in
patching file libsanitizer/tsan/Makefile.am
patching file libsanitizer/tsan/Makefile.in
patching file libsanitizer/ubsan/Makefile.am
patching file libsanitizer/ubsan/Makefile.in
patching file libssp/Makefile.am
patching file libssp/Makefile.in
patching file libssp/configure
patching file libssp/configure.ac
patching file libstdc++-v3/configure
Hunk #1 FAILED at 776.
Hunk #2 succeeded at 913 (offset 2 lines).
Hunk #3 succeeded at 1600 (offset 2 lines).
Hunk #4 succeeded at 10354 (offset 2 lines).
Hunk #5 succeeded at 10412 (offset 2 lines).
Hunk #6 FAILED at 12229.
Hunk #7 FAILED at 12335.
Hunk #8 succeeded at 13219 (offset 2 lines).
Hunk #9 succeeded at 13277 (offset 2 lines).
Hunk #10 succeeded at 15672 with fuzz 2 (offset 2 lines).
Hunk #11 FAILED at 16079.
Hunk #12 FAILED at 16114.
Hunk #13 FAILED at 16149.
Hunk #14 FAILED at 16185.
Hunk #15 FAILED at 16338.
Hunk #16 FAILED at 16380.
Hunk #17 FAILED at 16414.
  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file gcc/testsuite/obj-c++.dg/pr101666-1.mm,
which already exists!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file gcc/testsuite/obj-c++.dg/pr101666.inc,
which already exists!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file gcc/testsuite/obj-c++.dg/property/at-property-unavailable-1.mm
patching file gcc/testsuite/obj-c++.dg/property/at-property-unavailable-2.mm
patching file gcc/testsuite/obj-c++.dg/property/dotsyntax-unavailable-1.mm
patching file gcc/testsuite/objc.dg/attributes/method-unavailable-1.m
patching file gcc/testsuite/objc.dg/attributes/method-unavailable-2.m
patching file gcc/testsuite/objc.dg/attributes/method-unavailable-3.m
The next patch would create the file gcc/testsuite/objc.dg/pr101666-0.m,
which already exists!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file gcc/testsuite/objc.dg/pr101666-1.m,
which already exists!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file gcc/testsuite/objc.dg/pr101666.inc,
which already exists!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file gcc/testsuite/objc.dg/property/at-property-unavailable-1.m
patching file gcc/testsuite/objc.dg/property/at-property-unavailable-2.m
patching file gcc/testsuite/objc.dg/property/dotsyntax-unavailable-1.m
patching file libgcc/config/aarch64/heap-trampoline.c
patching file libgcc/config/aarch64/t-darwin
patching file libgcc/config/aarch64/t-heap-trampoline
patching file libgcc/config/i386/heap-trampoline.c
patching file libgcc/config/i386/t-heap-trampoline
patching file libgcc/config/t-darwin-rpath
patching file libgfortran/config/fpu-aarch64.h

It seems that even after this PR, the issue has not been resolved.
 Pushed it as gcc11: drop libgcc-aarch64-darwin-detection upstreamed patch. Please try that one as well.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4584

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4603

@trofi looking at merge conflict, maybe this PR is not needed anymore ?

I think the patch is still needed. The conflict was caused by e0464e47880a69896f0fb1810f00e0de469f770a "treewide: replace stdenv.is with stdenv.hostPlatform.is". Rebased past it.


tap.if

tap.if
conditional tap
y = tap.if(condition, f)(x)

condition, x => boolean, is a unary function that accepts the input x and returns a boolean value
f, x => any, is a function that is called with x only if condition is met
x is anything
y is x
y is a Promise if any of the following are true

condition is asynchronous
condition(x) is truthy and f is asynchronous

const logIfGreaterThan1 = tap.if(
  number => number > 1,
  () => console.log('Greater than 1'),
)

logIfGreaterThan1(1) /*
1
*/

logIfGreaterThan1(2) /*
Greater than 1
2
*/

groundwork: e4287c5 and 5507711

doin this

done with https://github.com/a-synchronous/rubico/commit/2274a8238cebed5631bd00bfa89590ff65a8ed05


Support gif, bmp, xls, xlsx and pdf @ Write-RSFolderContent & Write-RsCatalogItem

Fixes
#214 (includes the changes on https://github.com/microsoft/ReportingServicesTools/pull/215 that seems to have stood still)
#218
#221
Changes proposed in this pull request:

Make possible to upload new file extensions. Namely: gif, bmp, xls, xlsx and pdf

NOTE: new Pester tests included
How to test this code:

Try to upload a folder with at least one file of the mentioned types

Has been tested on (remove any that don't apply):

Powershell 5.1
Windows 10
SQL Server 2016 and above

Hi @jtarquino ,
Can you, please, take a look at why .xlsx is yielding error?
SoapException: System.Web.Services.Protocols.SoapException: Uploading or saving files with .xlsx extension is not allowed. Contact your administrator if you have any questions. ---> Microsoft.ReportingServices.Diagnostics.ResourceFileFormatNotAllowedException: Uploading or saving files with .xlsx extension is not allowed. Contact your administrator if you have any questions.
I'm able to do it on my local instances (2016 SSRS & 2017 PBIRS).
Thanks!

Check AllowedResourceExtensionsForUpload
https://docs.microsoft.com/en-us/power-bi/report-server/whats-new
Get Outlook for iOShttps://aka.ms/o0ukef

From: Cláudio Silva<EMAIL_ADDRESS>Sent: Saturday, June 8, 2019 8:03:28 PM
To: microsoft/ReportingServicesTools
Cc: Jaime Tarquino; Mention
Subject: Re: [microsoft/ReportingServicesTools] Support gif, bmp, xls, xlsx and pdf @ Write-RSFolderContent & Write-RsCatalogItem (#233)
Hi @jtarquinohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjtarquino&data=02|01|Jaime.Tarquino%40microsoft.com|5b1c9002196d4f640f9508d6ec6de6dd|72f988bf86f141af91ab2d7cd011db47|1|0|636956354102187523&sdata=G2lpy12lrgdbHcKD1efoTefJdH%2FtunyWD7ILlqMiCSo%3D&reserved=0 ,
Can you, please, take a look at why .xlsx is yielding error?
SoapException: System.Web.Services.Protocols.SoapException: Uploading or saving files with .xlsx extension is not allowed. Contact your administrator if you have any questions. ---> Microsoft.ReportingServices.Diagnostics.ResourceFileFormatNotAllowedException: Uploading or saving files with .xlsx extension is not allowed. Contact your administrator if you have any questions.
I'm able to do it on my local instances (2016 SSRS & 2017 PBIRS).
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FReportingServicesTools%2Fpull%2F233%3Femail_source%3Dnotifications%26email_token%3DAB5OLDW3XSMCAM7DN7S7QNLPZRCFBA5CNFSM4HWII4FKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIA3LY%23issuecomment-500174255&data=02|01|Jaime.Tarquino%40microsoft.com|5b1c9002196d4f640f9508d6ec6de6dd|72f988bf86f141af91ab2d7cd011db47|1|0|636956354102187523&sdata=b1UrDs2dWe9YCSlwEB9aRHBMWjZlqCtVsD4i7eDqveA%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB5OLDSFEKB2DJS7AP3XQ4DPZRCFBANCNFSM4HWII4FA&data=02|01|Jaime.Tarquino%40microsoft.com|5b1c9002196d4f640f9508d6ec6de6dd|72f988bf86f141af91ab2d7cd011db47|1|0|636956354102197518&sdata=%2BKl0ffuabm%2Bpfx1CcLAH8jf3aRuztTUjKLoRbESxVeA%3D&reserved=0.

Thanks @jtarquino
If I understood correctly, since the Jan 2019 release the extensions were trimmed for the ones in the documentation, but I see that is configurable.
The error seems to be on the SSRS (SOAP) and not on PBIRS (REST) , is this also configurable on SSRS?
Can you configure here on the repository installation script?

Yes it is configurable and it will be included in the new version of SSRS
It affects both soap and rest
I’m out of town and I can try to add them next week
Get Outlook for iOShttps://aka.ms/o0ukef

From: Cláudio Silva<EMAIL_ADDRESS>Sent: Sunday, June 9, 2019 6:07:46 AM
To: microsoft/ReportingServicesTools
Cc: Jaime Tarquino; Mention
Subject: Re: [microsoft/ReportingServicesTools] Support gif, bmp, xls, xlsx and pdf @ Write-RSFolderContent & Write-RsCatalogItem (#233)
Thanks @jtarquinohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjtarquino&data=02|01|Jaime.Tarquino%40microsoft.com|464a62ca5ee941656c5608d6ecc25278|72f988bf86f141af91ab2d7cd011db47|1|0|636956716690663135&sdata=Q7AlhQ2kg7VULNln3m7DXLM6l31kKtBQXRlx41oI2qk%3D&reserved=0
If I understood correctly, since the Jan 2019 release the extensions were trimmed for the ones in the documentation, but I see that is configurable.
The error seems to be on the SSRS (SOAP) and not on PBIRS (REST) , is this also configurable on SSRS?
Can you configure here on the repository installation script?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FReportingServicesTools%2Fpull%2F233%3Femail_source%3Dnotifications%26email_token%3DAB5OLDX7BLJC7QIWEXLG3N3PZTI7FA5CNFSM4HWII4FKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIHJQY%23issuecomment-500200643&data=02|01|Jaime.Tarquino%40microsoft.com|464a62ca5ee941656c5608d6ecc25278|72f988bf86f141af91ab2d7cd011db47|1|0|636956716690663135&sdata=ZTtUqHu5A0K4jRWUqwdZZ%2B7JMD0%2FFa5XzSAnumrNSPE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB5OLDVUGF2OSLJG3VI6MXDPZTI7FANCNFSM4HWII4FA&data=02|01|Jaime.Tarquino%40microsoft.com|464a62ca5ee941656c5608d6ecc25278|72f988bf86f141af91ab2d7cd011db47|1|0|636956716690673117&sdata=hWiisegtFv%2Bd6JyV7cejES0eJf7CDYRHXUukIVc9VVc%3D&reserved=0.

Cool!
Then I will wait for the changes so we can double check that all tests pass and we can merge it!
Thanks for your help.

I added the config but there is a chance the service isn't ready for receiving it so I would recommend to add it to the test setup , check out https://github.com/microsoft/ReportingServicesTools/blob/ccff67ed35a150e5f49ec83f0c67344f1a8596ad/appveyor.yml#L91

@jtarquino can you help?
Thanks

sure , as I mentioned earlier the file format wasn't applying always (added retries so now you can rely on it)

Thanks @jtarquino. It is still failing  😞

The db tests are probably the cause as they set the new database
I would add the setting of the allowed files to the tests that now require it (mostly to keep every test self contained), those tests are Write-RsFolderContent, Out-RsFolderContent, Write-RsCatalogItem etc

Will it possible to also add .xlsm extensions to it?


Documenting Prismic components to find out if we can remove some

Description
By working on Visual Stories and discussing the possibility of creating new components (or modifying existing ones), we tended to fall into rabbit holes when talking about existing one. It was also discussed that their purpose wasn't always clear and that documentation would be useful moving forward.
I created a document to analyse what we have, how it is used, and started suggesting what could be removed or tweaked to be more useful.
This will be a work in progress for a bit, but the goal is to have tickets come out of it to streamline our Prismic component offer.
Definition of Done:

Cleaned up slices as much as possible
Created a permanent document describing each slice and what they are to be used for/what they look like.

Have booked a meeting with @jennpb on Monday to discuss what is left to answer in the document.

Looking for a first round of review on my Gitbook documentation page. Not putting the ticket down as ready for review as I still have some cleaning up to do (see first point in DoD) and extra editing on the documentation.

The last of the last:

Waiting on #9868
Need a better description for Title Text List ( @jennpb has it on her to do, but if anyone else has a good one)
Do we want to rename Title Text List on the UI or are we happy with that? It's used only once, here https://wellcomecollection.org/pages/YDaP2BMAACUAT7DS

Do we want to rename Title Text List on the UI or are we happy with that?

Maybe "List of links"? That describes what we're actually using it for.
(And maybe trim some of the options while we're here? If you look at the current Prismic model definition, there are several options we aren't using in the one page we use it on. There are no labels, no heading4/list-item, and nothing but single lines of text.

Thanks @alexwlchan !

It's like "List of links with description" though, not just a bullet point of links 🤔 I don't have a clever idea though
Agree tags isn't used, maybe it was for "online" or "library"? @jennpb do you remember and do you think we could remove?
What do you mean by "heading4/list-item"?

heading4/list-item is what I meant to be linking to, from the Prismic model definition:
https://github.com/wellcomecollection/wellcomecollection.org/blob/a94bf4487e3d7701796bcc68ae265209c3615b20/prismic-model/src/parts/body.ts#L141-L150
I don't think we need those extraTextOptions.

Ahh yes I see! @jennpb any objections in regards to how it was first designed?

Agree tags isn't used, maybe it was for https://github.com/wellcomecollection/wellcomecollection.org/issues/6010#issuecomment-775104643? @jennpb do you remember and do you think we could remove?

It was for that purpose, yes. It looks like the content editor has decided to separate the links out into separate sections instead of using the labels, so I think it's fine to remove labels.

what about Descriptive links list?

As far as I can tell, the prismic model still meets the original intent as described here: https://github.com/wellcomecollection/wellcomecollection.org/issues/6010 - there are examples that we'd worked up with the content team at that point.
Descriptive links list is fine. I still think that bulleted text should be allowed in it.

Do you mean something like this?

Clearing out Image List is my last item in this, the only outlier being Media object list which depends on more work on new slices. It has its own ticket in the backlog as #9849 .


Use a safer approach to event tracking

Describe the bug
The code for event tracking here
https://github.com/onflow/kitty-items/blob/e2255bce7ff5f34fca242374489d3601d0ba3daf/api/src/workers/base-event-handler.ts#L41-L44
works fine when connecting to a single AN, but can be unsafe when using a proxy with many ANs behind it like what we recommend for FCL. The problem is that sometimes an Access node will fall behind, resulting in this tracker reprocessing events from past blocks.
To Reproduce
It is hard to force this, but if one of the Access nodes behind a proxy falls behind (it reboots, or is shutdown), and that node is selected for the call to getLatestBlockHeight, the range will be reset potentially thousands of blocks into the past, causing this logic to re-ingest all of the events.
Expected behavior
The event processor should ignore past blocks.
This really only matters as this is an example implementation many new devs may copy, it's it best to demonstrate how to avoid this somewhat common pitfall.

What is the safer approach?

closing because we are archiving in favor of the flow app quickstart


Message test framework

Hi,
I started to prepare message test framework and here is a draft version. As for now the main functionality of Messageframework is implemented and is already more or less typed (thanks @forell !). I started also to rewrite LSU test (function test_body), but due to time which was consumed by typing it is not ready yet.
ToDo:

[ ] add support for Arusekk syntax in functions (probably as separate PR)
[x] add function to combine messages in MessageQueueCombiner
[ ] shorter names
[x] add random wait
[x] add build-in empty generator to start test flow
[ ] rewrite LSU test to new framework
[ ] reduce delay (instead of yield use Settle() as condition var)
[ ] debug problems with TypeVar appears only one (probably pyright bug simmilar to https://github.com/google/pytype/issues/379
[ ] is it possible for type checker to treat add_data_flow as a relation which is transitive in terms of types?

I have uploaded new version of message framework. Changes:

Internal structure of MessageFrameworkProcess is now much simpler (but this make data forwarding between processing steps harder)
MessageFrameworkProcess is now implemented as base class (this caused that test is longer)
calls are now done using standard python syntax (but there is some magic under the hood)
tests for clearing works correctly (more than 50 000 test iterations without any errors)

ToDo/ToDiscussion:

sort MessageFrameworkProcess in topology order to insert correct amount of settles on the beginning
add out-of-the box support for multi input process
improve out-of-the box support for mocks


Issues with NextJS Supabase AuthHelper setup: app Dir to pages Dir

Anyone here have experience with Supabase Auth + Nextjs setup?
can someone help me with this i am using the pages dir i merge it with someone's setup with app dir setup and migrate it to pages dir (since pages dir is the only way i am comfortable coding).
i did follow the https://supabase.com/docs/guides/auth/auth-helpers/nextjs-pages document while converting the source file from app dir to pages dir and find it difficult.
I would really appreciate if someone could help me fix this issue (details can be found at readme): https://github.com/mashwishi/NextJS-Supabase-AuthHelper/

Solved, and this is my solution to _app.tsx i have used my old _app.tsx and merge it with the _app.tsx to the supabase page directory _app.tsx
import "../styles/globals.css";
import App, { AppProps, AppContext } from 'next/app'

import { createPagesBrowserClient } from '@supabase/auth-helpers-nextjs'
import { SessionContextProvider, Session } from '@supabase/auth-helpers-react'
import { useState } from 'react'

function MyApp({ Component, pageProps }: AppProps<{ initialSession: Session }>) {

    // Create a new supabase browser client on every first render.
    const [supabaseClient] = useState(() => createPagesBrowserClient())

    return (
        <SessionContextProvider
        supabaseClient={supabaseClient}
        initialSession={pageProps.initialSession}
        >
        <Component {...pageProps} />
        </SessionContextProvider>
    )

}

MyApp.getInitialProps = async (appContext: AppContext) => {
    const appProps = await App.getInitialProps(appContext)
    const { router } = appContext;
    const { query } = router;

    return {
        pageProps: {
        ...appProps.pageProps,
        },
    }
}

export default MyApp;


MINOR: Fixed deprecated Gradle build Properties.

Gradle properties: baseName, classifier and version has been deprecated. So I have change these to archiveBaseName, archiveClassifier and archiveVersion. More infomration here.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

ok to test

I double checked and it looks like all of these deprecated properties have been replaced, so closing this PR.


Disk size monitoring unexcepted behaviour

Description
VM disk size monitored only one time after opennebula service restart using tm/driver/monitor script.
Sat Dec 29 11:24:24 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sat Dec 29 11:24:24 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242]
Sat Dec 29 11:25:09 2018 [Z0][InM][D]: Host tst.lin.fedora.host (0) successfully monitored.
Sat Dec 29 11:25:09 2018 [Z0][VMM][D]: VM 97 successfully monitored: STATE=a CPU=0.0 MEMORY=807324 NETRX=6317550576 NETTX=127931671 DISKRDBYTES=285341508 DISKWRBYTES=6207442432 DISKRDIOPS=8641 DISKWRIOPS=15705
Sat Dec 29 11:29:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.

As you see in logs, first time system ds is monitored log is followed by VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242], next systems ds monitorings are without VM disk size parsing.
Expected behavior
Disk size monitoring each time system datastore is monitored.
Details

Affected Component: Storage
Hypervisor: KVM
Version: 5.6.2

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Update:
Looks like, that informations about disk sizes are parsed only every hour
Sun Dec 30 04:04:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 04:54:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 05:44:25 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 06:34:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 07:24:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 08:14:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 09:04:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 09:54:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]
Sun Dec 30 10:44:26 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=1246]

system datastore is monitored every 5 minute
Sun Dec 30 04:04:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:04:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:09:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:09:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:14:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:14:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:19:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:19:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:24:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:24:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:29:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:29:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:34:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:34:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:39:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:39:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:44:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:44:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:49:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:49:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sun Dec 30 04:54:22 2018 [Z0][InM][D]: Monitoring datastore 3par_system (0)
Sun Dec 30 04:54:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.

Why? Is there some another option passed to tm_mad/monitor script, which tells if disk_sizes are requested or not? There is some option to configure smalled intervals that actual 1 hour?

I found it in code.
https://github.com/OpenNebula/one/blob/2ff0324bb224dd73d246b864bd0cd9eea115e998/src/image/ImageManagerDriver.cc#L699

Add a configuration option, 0 to disable

Monitor script parses disk usage stats only on each 10th run, so practically every 50minutes
Few proposals:

this variable should be configurable
most important is adding additional argument when calling ds monitor script to inform, that should NOT collect data about disk/snapshot usage, because it cost resources and it is used only every 10th run.

PRs for merge:

one: #3525  into master
docs: OpenNebula/docs#703 into master

Merged into master


podman-pilot cleanup changes

Upstream patch from Michael Meyer<EMAIL_ADDRESS>which shortens some code parts.

Needs testing as there are many changes which I cannot tell if they change the behavior

cleanup patch is great, tested the podman pilot in all functions


Is there a plan to upgrade the master branch to .net 6 or 7?

Cause I found it hard to build this project on my Apple M1 MacBook :)
I noticed a feature/dotnet6 branch with some commits behind the master branch, actually, I'm using this branch in my local env. Just wondering if is there a plan to upgrade the master to .net 6 or 7.
Thx for your answers.

Hi @EanCuznaivy
The feature/dotnet6 will become the latest relaese very shortly.

Hi @EanCuznaivy
The feature/dotnet6 will become the latest relaese very shortly.

Copy, thx

Hi @EanCuznaivy
The feature/dotnet6 will become the latest relaese very shortly.

iis very shortly means one two years?


Building parquet multi-file dataset : duckdb.InternalException: INTERNAL Error: Comparison on NULL values

Hello everyone,
Based on the discussion thread here : https://github.com/duckdb/duckdb/discussions/6304 I was advised to create a bug report here.
My environment:
OS : Windows 11, 64 bits
Python version: 3.10.4 (64 bits)
DuckDB version installed via pip : 0.7.0

Problem description:
In the most recent version, by using the COPY command, one can export the content of a table from a local (persistent) DuckDB database into a directory as multi-file dataset (Parquet format). Something like
db_connection.execute("copy mytab to 'D:\\tmp\\parquet_data_dir' (format parquet, partition_by(col1, col2, col3, col4)))
Now, the problem is that apparently if the first column in the partition_by clause (therefore col1 in the above example) is NULL, then we get the following error message :
duckdb.InternalException: INTERNAL Error: Comparison on NULL values
Test case in order to reproduce the error:

Create the following CSV file which has to be named mydata.csv in the directory of your choice which will be the current working directory once you run the Python program. Note that I introduced intentionally at the first column (region_code) of the first data line (the one after the header line) a NULL value to reproduce the error.

mydata.csv
region_code;department_code;city_code;sector_code;transaction_value
;D1;C1;S1;100000
R1;D1;C1;;79852
R1;D1;C2;S2;479305
R1;D1;C3;S3;
R1;D2;C4;S1;
R1;D2;C5;S2;200000
R1;D2;C6;S3;897450
R1;D3;C7;S1;99
R1;D4;C8;S2;1478
R2;D5;C9;S3;98712000
R3;D6;C10;S6;
R4;D7;C11;S2;8000
R4;D7;C12;S7;9740
R4;D8;C13;S12;87501

Now in the very same directory, create the following Python program. You don't need to change anything in the program, just copy/paste it and save it in a file named myprog.py.
myprog.py
import os
import shutil
import duckdb

def main():
    # Path to the database that will be created in the current directory
    db_file_path = "mydb.duckdb"

    # Path to the CSV file that has also to be put in the current directory
    # and will therefore be imported in our DuckDB database
    data_file_path = "mydata.csv"

    # Path to the directory of Parquet multi-file dataset that the program
    # will create in the very same current working directory.
    parquet_dir_path = "parquet_data"

    # Remove the databse if it already exists
    try:
        file_desc = os.open(db_file_path, os.O_RDONLY)
        os.close(file_desc)
        os.remove(db_file_path)
    except FileNotFoundError:
        pass

    # Remove the Parquet directory if it already exists
    try:
        shutil.rmtree(parquet_dir_path)
    except FileNotFoundError:
        pass

    # Create and connect to a new DuckDB database. The database file is
    # also put in the current working directory.
    db_connection = duckdb.connect(database=db_file_path, read_only=False)

    # Now let's create a table with the same structure as our CSV file
    db_connection.execute(
        "".join(
            [
                "create table mytab(",
                "region_code        varchar, ",
                "department_code    varchar, ",
                "city_code          varchar, ",
                "sector_code        varchar, ",
                "transaction_value  numeric"
                ")",
            ]
        )
    )

    # Import the CSV file into the table that we've just created above.
    db_connection.execute(
        "".join(
            [
                "copy mytab from '",
                data_file_path,
                "' with (",
                "format csv, ",
                "header TRUE, ",
                "NULL '', ",
                "quote '\"', ",
                "delimiter ';'",
                ")"
            ]
        )
    )

    # Finally, let's export the table 'mytab' into a Parquet multi-file dataset
    db_connection.execute(
        "".join(
            [
                "copy mytab to '",
                parquet_dir_path,
                "' (format parquet, partition_by(",
                #
                #
                #
                #
                # And here is where the problem appears, the column 'region_code'
                # in our CSV file is the first column, and at the first
                # row in our CSV file. We introduced intentionally a NULL value for this
                # column. Because of that, Parquet export fails with the
                # above-mentioned error message. It seems that the first
		# column in 'partition_by' clause cannot be NULL.
                "region_code, ",
                #
                #
                #
                #
                "department_code, ",
                "city_code, ",
                "sector_code))"
            ]
        )
    )

    # Closing the connection to the database
    db_connection.close()

if __name__ == "__main__":
    main()

When you run the program you will get the following error message:
duckdb.InternalException: INTERNAL Error: Comparison on NULL values
Now go back to the CSV file, at the first data line, add some value instead of NULL to the first column, that is, the region_code. This time the program works without any problem and the Parquet multi-file dataset (hive-style) is created. Consequently, based on multiple tests that I have done so far, it seems to me that the first column in partition_by(col1, col2, col3, . . .) cannot be NULL.
I hope the description is clear.
Thanks in advance

Can you please create issues in the https://github.com/duckdb/duckdb repository in the future? This issue has nothing to do with the website or docs

I am so sorry for my mistake. Thanks for the remark.


(BKR-1093) Fix Nova Keypair Generation

Firstly this fixes the rspec test that doesn't work, shame on me.  Secondly it
ensures only the hostname part of the host's FQDN is used in keypair generation,
as the FQDN includes periods and is illegal according to Nova.

Can one of the admins verify this patch?

@puppetlabs-jenkins test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3732/


Fixes rules update.

Fixes serialization bug for creating and deserializing rules.
Adds tests for serialization.

Fixes #15723

A separate discussion. SqlRuleFilter and SqlRuleAction have parameters in other languages. But I don't see them in Java.

A separate discussion. SqlRuleFilter and SqlRuleAction have parameters in other languages. But I don't see them in Java.

We do have parameters exposed. https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/servicebus/azure-messaging-servicebus/src/main/java/com/azure/messaging/servicebus/administration/models/SqlRuleAction.java#L81

A separate discussion. SqlRuleFilter and SqlRuleAction have parameters in other languages. But I don't see them in Java.

We do have parameters exposed. https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/servicebus/azure-messaging-servicebus/src/main/java/com/azure/messaging/servicebus/administration/models/SqlRuleAction.java#L81

A separate discussion. SqlRuleFilter and SqlRuleAction have parameters in other languages. But I don't see them in Java.

We do have parameters exposed. https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/servicebus/azure-messaging-servicebus/src/main/java/com/azure/messaging/servicebus/administration/models/SqlRuleAction.java#L81

It's called "parameters" in other languages. Do we need to change the method name to getParameters()?


Release of django-allauth 0.58 breaks templates

django-allauth 0.58 includes the following change:

Refactored the built-in templates, with the goal of being able to adjust the look and feel of the whole project by only overriding a few core templates. This approach allows you to achieve visual results fast, but is of course more limited compared to styling all templates yourself. If your project provided its own templates then this change will not affect anything, but if you rely on (some of) the built-in templates your project may be affected.

The changes were made primarily in https://github.com/pennersr/django-allauth/pull/3466 .

At a minimum, the styled pages of django-auth-style should be reviewed, to see if anything is broken.
Additionally, we should investigate whether it's possible to change this library to apply styles only to the core templates of django-allauth, which may reduce the surface area and maintenance burden of this library significantly.

We should consider this library to be soft-broken by django-allauth >= 0.58.
However, I'm not sure whether it makes sense to pin the requirements accordingly, since this will force downstreams to adopt an older version of an important library, just to prevent some style bugs.

One breaking change is that the link to the account_reset_password page within login.html was removed and instead added as help_text on the password field of LoginForm.
This causes the link to now display twice, with django-auth-style.

The easiest fix is to remove corresponding HTML from django-auth-style, to match the upstream version. However, this will require that django-auth-style depend on django-allauth >= 0.58, which might introduce other breakages.


"Could not start Xvfb" - windows 10

Hi
I am running it on windows, and it wont start. I think this is because it can't create the lockfile.
Do you know a quick way around this?
I'm using the synchronous functions with protractor js.
Also worth noting I'll only be running 1 instance of this at a time so I dont think I need the lockfile part.
Thanks

This library relies on Xvfb, which is not supported on Windows.
Try an alternative, e.g. mentioned at https://stackoverflow.com/questions/944086/is-there-anything-like-xvfb-or-xnest-for-windows


Coreutils: ln --symbolic creates hard links -- part 2 --

This really should have been part of issue #249 but I do not know how to reopen a closed issue.
And here is how to use symlinks.  See Symlinks in Windows, MinGW, Git, and Cygwin · Josh Kelley.  To summarize, "administrators" are, by default, allowed to make symlinks according to the Group Policy entry.  If you are not an administrator, you need Windows 10 Creator release or newer and and a friendly administrator to (1) if necessary, install 'gpedit.msc' in the HOME edition and (2) use 'gpedit.msc' to add your id to the list of users allowed to make symlinks.  Then you can use MSYS=winsymlinks:nativestrict.  It is all explained in much more detail in the above link and it's sublinks.  FWIW - if 'gpedit.msc' is not available on your HOME edition, the files you need to install 'gpedit.msc' are already on the machine, just not installed.  One of the sublinks supplies a batch script to do the install and another describes the way to get to the Group Policy permission entry.
Oops, forgot that you need to enable "developer mode" also. Also described in the above link

Oops, forgot that you need to enable "developer mode" also.  Also described in the above link.

MSYS=winsymlinks:nativestrict is already covered in the original thread. Please close this and keep the discussion in one thread. You can still make comments even if the thread is closed.

Also remember, if you are a member of the Administrators group, even if you add yourself to the list of users who are allowed to create symbolic links, and you will run the shell in an unprivileged mode - you can not create symbolic links. UAC will cut off this rights (

@niklasholm I would be glad to close this thread if you could tell me how to transfer the contents of this thread to the original.  I was considering adding a comment there pointing at this thread.
@vyache-slav Actually, I seem to have a condition opposite others because I have been creating symlinks via the  Command Console's mklink command for quite awhile mostly as unelevated pud user me.  Just recently, I enabled winsymlinks:nativestrict on MSYS and CYGWIN with no problems there.  I  do not remember ever seeing the UAC (if I thought hard enough about it, that would probably be a lie (:-}) ).  FWIW - the "administrators" that I referenced is the "administrators" group (id=544) and all accounts that have administrative rights are members of this group.
There is an additional permission set not mentioned other places that is controlled by the file administration software. On a Command Prompt window, execute the first line below
fsutil behavior query symlinkEvaluation
#fsutil behavior set /?
#fsutil behavior set symlinkEvaluation L2L:1
I can run the first line unelevated as pud me.  Don't know if that requires "administrators" permission or not.  The 1st line printed should say something like "local to local symlinks are allowed.  If that is not the case, an administrator would have to execute the 3rd line.
Another FWIW - as a test via gpedit.msc, I removed permissions for all accounts/groups disabling them to create symlinks, restarted (do not know if that was necessary) and I COULD STILL CREATE SYMLINKS AS PUD USER ME.  There seems to another permission set somewhere (:@{).
Has everybody enabled "Developer mode"?
c

Update - I just disabled "Developer mode", attempted to make a symlink as unelevated pud me and got the following message.
"You do not have sufficient privilege to perform this operation."
Got the same message when elevated.  No UAC was in evidence.
Created a vanilla user.  No problems.  So why is everybody else having problems?


Update N3K-C3172PQ-10GE.yaml

added weight

clone my latest revision, netbox guys made me fix some stuff


Refs #34012 -- Added test for ordering by transform of related fields.

@felixxm Perfect ♥ Not sure if I'm allowed to approve but approving anyway.
One thing I'd like to point out though which should be fixed in #16070 - if I update DateTimePK to add ordering like so:
class DateTimePK(models.Model):
    date = models.DateTimeField(primary_key=True, default=datetime.datetime.now)

    class Meta:
        ordering = ["date"]

The test fails as the ordering code takes preference over the lookup:
FAIL: test_order_by_related_field_transform (queries.tests.Queries1Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
    <<< omitted >>>
AssertionError: Sequences differ: <QuerySet [<ExtraInfo: extra 12>, <ExtraInfo: extra 11>]> != [<ExtraInfo: extra 11>, <ExtraInfo: extra 12>]

First differing element 0:
<ExtraInfo: extra 12>
<ExtraInfo: extra 11>

- <QuerySet [<ExtraInfo: extra 12>, <ExtraInfo: extra 11>]>
? ----------                    ^                      ^  -

+ [<ExtraInfo: extra 11>, <ExtraInfo: extra 12>]
?                     ^                      ^

This is because the ordering is applied before any found lookups are attempted to be applied in find_ordering_name(): https://github.com/django/django/blob/3ba7f2e9069c54db6d6d9d2fd1945b2dbc935d9c/django/db/models/sql/compiler.py#L1002-L1010

By the way, I should point out that if we were to rearrange ordering vs lookup precedence to fix the test failure above, this will also fix the original problem description for not raising an error for unknown 👍

@David-Wobrock Thanks for checking :+1:


DOCS ERROR

https://nuxt-seo.frostbutter.com/options/opengraph
Image Block
<script>
  export default {
    head({ $seo }) {
      return $seo({
        openGraph: {
          image: {
            currency: '',
            amount: ''
          }
        }
      })
    }
  }
</script>

Copy and paste will get you from time to time... quick fix in the works


The program crashed when calling rs2::motion_frame.get_motion_data()

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18

Kernel Version (Linux Only)
4.9.253

Platform
NVIDIA Jetson Xavier NX

SDK Version
2.50.0 }

Language
C++

Issue Description
There are two pipelines in the program, which open depth stream and IMU stream respectively. The IMU data is used for subsequent calculations.
The program runs well at first, but the program crashed when calling rs2::motion_frame.get_motion_data() after about an hour every time.
The main codes are as follows:
cfg.enable_stream(RS2_STREAM_ACCEL, RS2_FORMAT_MOTION_XYZ32F, 250);
cfg.enable_stream(RS2_STREAM_GYRO, RS2_FORMAT_MOTION_XYZ32F, 200);
pipeline.start(cfg, [&](const rs2::frame &frame) {
                            std::lock_guard<std::mutex> lock(pipe_mutex);
                            if (auto mf = frame.as<rs2::motion_frame>()) {
                                if (mf.get_profile().stream_type() == RS2_STREAM_GYRO) {
                                    gyro = mf;
                                    gyro.keep();
                                } else if (mf.get_profile().stream_type() == RS2_STREAM_ACCEL) {
                                    accel = mf;
                                    accel.keep();
                                }
                            }
                        });
...
auto data = accel.get_motion_data(); // program crashed here.
...

Hi @HEIDIES  As you are using the Keep() instruction, I would recommend monitoring over a period of time the amount of available remaining memory that your computer has, using an Ubuntu system monitoring tool such as htop.  This is because Keep() causes frames to be stored in the computer's memory, so the computer's memory capacity is progressively consumed over time.  When available memory falls below a certain level, an application's performance will start to degrade and it will eventually lead to a program freeze or crash.

Hi @HEIDIES  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


label:"help wanted" Need procedure for running iris example

I keep getting lost inside the folders
Documents are bit high tech I guess. Can anyone direct me to run iris project
thanks in advance

Hi there @vjkr!
You are looking at the docs here? https://kedro.readthedocs.io/en/stable/02_get_started/05_example_project.html
Have you already worked through the earlier docs to ensure you meet the pre-requisites and have installed Kedro in a virtual environment?
When you run kedro info what do you see?
What version do you have?
You should then be able to follow the docs for the Iris example:
(1) create a project with kedro new and confirm Y to build in the iris example code at the final prompt
That will give you the project, creating a project directory to store all the subfolders and code.
(2) Change directory into the project directory and type kedro run
What do you see?

Hi @stichbury !
** It worked!! Thanks! **
I had completed all previous steps. But I was unable to comprehend that kedro run is in itself a command. Till now I was familiar with python somefile.py .
Just for information kedro run returned following error.
ModuleNotFoundError: No module named 'pandas'
I fixed it by running conda install pandas
Thanks a ton!

Great! Thanks for letting me know. I'll take another look at those docs and see if I can further clarify things. Your feedback is really helpful for us to improve the docs, so let me know if you hit other issues as your Kedro journey continues. Happy exploring 🗺

@stichbury Honestly the docs are great. This is my first time referring such docs in coding. I will need all the directions you may offer.
Three things

I need help regarding understanding the code flow. I know iris example. But unable to follow all the folders/files/CLI.

I understood importance of  when I hit a barricade during .  helped. Thanks !!

I named my project

When I searched for location of my pipeline, it is at
<src/kedroirispackages/pipelines/data_engineering/pipeline.py>

So for the <getting_started> project in readthedocs I guess location should be
<src/getting_startedpackages/pipelines/data_engineering/pipeline.py>
instead of
<src/getting_started/pipelines/data_engineering/pipeline.py>
Also forgive me for unconventional questions/posting styles. I am new to everything.
Thanks!!

@vjkr You can join us on Discourse and I hope that you got all the help that you needed 🚀 I'll close this issue now.


Unknown argument: '-Xanalyzer'

I have successfully imported my app into Visual Studio with the vsimporter.exe, However when I try and build the application I get multiple occurrences of the error CLANG : error : unknown argument: '-Xanalyzer' in the Build window.
I did some searching and found that the new version of XCode uses treats unknown arguments as errors

The Apple LLVM compiler in Xcode 5.1 treats unrecognized command-line options as errors.

Taken from: https://bruteforce.gr/bypassing-clang-error-unknown-argument.html
Is this error being caused by something similar within Visual Studio?
Any advice to get my app to compile would be greatly appreciated.

I have the same problem with my existing Xcode 7 App.
It seems like the error appears when trying to compile the Pods.
I would appreciate any advise, I really like the idea behind winObjC :)

hi everyone,
i have exactly the same probleme, i have t'y to retargeted the solution as https://github.com/Microsoft/WinObjC/issues/55 , but it didn't work : (

I have the same problem and I think that the problems are the pods.

@ganchito55 you're correct, this happens when you're using a CocoaPod generated Xcode workspace instead of an Xcode project. We don’t currently support CocoaPods since our clang compiler front end doesn’t support virtual filesystems, which CocoaPods depends on. Right now we suggest manually including third party frameworks and SDKs.

Unfortunately, this is a limitation of the clang driver we are using.
The only workaround, at this time, is to open the VCXPROJ files in a text editor and remove the offending flags. The -Xanalyzer option takes a required argument (e.g. -Xanalyzer -analyzer-disable-all-checks), so be sure to remove both tokens.


“Review” button shows in disabled state when a user enters the 0.01 amount in “Amount (Gold/USD)” field while buying the Gold.

Frequency: 100%
App version: Integration build v1.5.2 (101548777)
Repro on: Google Pixel XL 2 (9.0), Samsung Galaxy A8+ (8.0.0)
Repro Steps:

Launch the app.
Tap on Gold tab.
Tap ”Buy” button.
Enter an 0.01 amount.
The Observe review button is shown disabled state.

Investigation:

Review button shows enabled when a user enters 0.01 amount in Amount (Gold/USD) field while selling the gold.
Review button shows in disabled state when the user enters 0.001 amount in the Amount (Gold/USD) field while selling the gold.

Current Behavior: “Review” button shows in disabled state
Expected Behavior: “Review” button should show enabled.
Attachment: Android_ReviewButtonIssue.mp4 (Bug Observed after 07  sec)

Verified with Android play store build v1.8.2 and found that review button is shown enabled when user entering 0.01 amount in Amount (Gold/USD) field


Bug in new version of autocompletion for python

Issue Type: Bug
Since the last update, my autocompletion (python) is not working properly. Either it is not showing any thing or it is partially working. For example with tensorflow, it can see that there is a submodule called keras, but can't see what's inside keras!!!
VS Code version: Code 1.61.0 (ee8c7de, 2021-10-07T18:13:09.652Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

Unfortunately, I'm still getting the same result over and over again. I didn't have any issue untill last update, so something must have hapened.
I don't quite understand what's happening exactly and I'm not expert in vscode modules.
I just use it to code in python with a basic configuration.

Sounds a lot like a duplicate of #1066.

try adding this to the bottom of your  tensorflow/__init__.py
# Explicitly import lazy-loaded modules to support autocompletion.
# pylint: disable=g-import-not-at-top
if _typing.TYPE_CHECKING:
  from tensorflow_estimator.python.estimator.api._v2 import estimator as estimator
  from keras.api._v2 import keras
  from keras.api._v2.keras import losses
  from keras.api._v2.keras import metrics
  from keras.api._v2.keras import optimizers
  from keras.api._v2.keras import initializers
# pylint: enable=g-import-not-at-top

It worked !!!
Thank you very much.
Can you explain why is required? I didn't have the problem before!

the issue is in tensorflow, and how they lazyload their imports.
I'll create a PR in tensorflow so that it gets checked in there.

@judej, I think this can be closed. This is an issue with tensorflow.


Input/output error after mounting

I hadn't used google-drive-ocamlfuse for some time, though it had been updated via apt-get.
Now after mounting I see the following error:
ls: cannot open directory .: Input/Output error
These seem to be the relevant lines from gdfuse.log:
CURLE_SSL_CACERT, ErrorBuffer: server certificate verification
failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none\n")
Backtrace:
[24.910059] TID=33: getattr /
[24.910240] TID=33: BEGIN: Loading metadata from db
[24.911252] TID=33: END: Getting metadata: Not found
[24.911708] TID=33: BEGIN: Refreshing metadata
[25.056741] TID=33: Error during request: Code: 60, Description:
CURLE_SSL_CACERT, ErrorBuffer: server certificate verification
failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

[25.056892] TID=33: Giving up
[25.057002] TID=33: Exception:Failure("Code: 60, Description:
CURLE_SSL_CACERT, ErrorBuffer: server certificate verification
failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none\n")
Backtrace:
[25.742051] TID=35: opendir / O_RDONLY,O_NONBLOCK
[25.742234] TID=35: BEGIN: Loading metadata from db
[25.743032] TID=35: END: Getting metadata: Not found
[25.743171] TID=35: BEGIN: Refreshing metadata
[25.871744] TID=35: Error during request: Code: 60, Description:
CURLE_SSL_CACERT, ErrorBuffer: server certificate verification
failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

[25.871884] TID=35: Giving up
[25.871979] TID=35: Exception:Failure("Code: 60, Description:
CURLE_SSL_CACERT, ErrorBuffer: server certificate verification
failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none\n")

and from curl.log:
[25.779176] curl: info: Connected to www.googleapis.com (<IP_ADDRESS>)
port 443 (#0)
[25.795799] curl: info: found 148 certificates in
/etc/ssl/certs/ca-certificates.crt
[25.795921] curl: info: ALPN, offering http/1.1
[25.865104] curl: info: SSL connection using TLS1.2 /
ECDHE_ECDSA_AES_128_GCM_SHA256
[25.866227] curl: info: server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt CRLfile: none
[25.866332] curl: info: Closing connection 0

The cache had been cleared first but this had no effect.

It looks like you have a problem with certificates on your host. Check this answer on StackOverflow.

Thanks for the link. I reinstalled the certs etc as suggested in the linked answer. Didn't help at all, unfortunately.
When I run with -debug, this block of certificate-related errors keeps occurring:
Backtrace:
[2.013989] TID=17: opendir / O_RDONLY,O_NONBLOCK
[2.014106] TID=17: BEGIN: Loading metadata from db
[2.015069] TID=17: END: Getting metadata: Not found
[2.015155] TID=17: BEGIN: Refreshing metadata
[2.147190] TID=17: Error during request: Code: 60, Description: CURLE_SSL_CACERT, ErrorBuffer: server certificate verification failed. CAfile: /etc/ssl/certs
/ca-certificates.crt CRLfile: none
[2.147329] TID=17: Giving up
[2.147424] TID=17: Exception:Failure("Code: 60, Description: CURLE_SSL_CACERT, ErrorBuffer: server certificate verification failed. CAfile: /etc/ssl/certs/ca
-certificates.crt CRLfile: none\n")

same error


Creating a pencil sketch using Python.

Aim

In this script, we are going to convert any image into its pencil sketch using a python script.

Details
-In our script, the user has to just upload a picture and as an output, he/she will get a pencil sketch of that image. For this purpose, we are going to use OpenCV.
As a process, we will be going to reduce the noise in the image(if any), and then by performing the various operation like image conversion, blurring and many more, we will obtain our required output image.

We already have this script: https://github.com/avinashkranjan/Amazing-Python-Scripts/tree/master/ImageToSketch


Performance/Memory issues with more than 60K records

Hi,
I am trying to render a tree with around 60K items, and I see that the whole page lags and the memory consumption (Heap size) is over 800MB. Is this expected? Is it possible to lazy load the tree to mitigate this issue?

it is not optimized for big data. even if I render placeholders with viewport observer or calculate visible items based on amount of pixels scrolled (while trying not to introduce bugs because of dynamic height of items)... there are still some things under the hood which use a full list walkthrough for some checks.
having that in mind, I would suggest using a custom solution for your case.
feel free to snatch any pieces of code that you find useful.