Installer hash does not match the Release v0.47.0 documentation hash

Provide a description of requested docs changes
Please see the Release v0.47.0 link: https://github.com/microsoft/PowerToys/releases/tag/v0.47.0
The said installer hash 58EF4AE2F24080DCFAABC1CC03BE05F8637AD41D3DD6D66EC6AC8AC5037389BC does not match the hash from the PowerToysSetup-0.47.0-x64.exe which contains a hash of 33D9A55E5D133EC521669FA05473A3B3F04F06B786016A36E92ADC83002502E1
I checked it using the Get-FileHash of the PowerShell.
Am I doing it right or I am just wrong in checking the hashes?

The hash I've calculated is as same as it on the release page (58EF4AE2F24080DCFAABC1CC03BE05F8637AD41D3DD6D66EC6AC8AC5037389BC), both from PowerShell and 7-zip shows the same result. Please download your installation file and verify again.

cc: @dedavis6797

Oh nice! I got the same hash using the 7-zip checker thank you 😁 Will close this now.


Explicitly mention that developer should create a new .env.server file, and not use .env.server.example

Is that the idea, did I get it right? I got across this at https://docs.opensaas.sh/guides/authentication/#google-auth, where it is mentioned to add stuff to .env.server file, but we never created it in the first place. So I wasn't sure if I should create a new one, reuse the example one or sth else. Would be nice to have some tip about this.

I believe it is mentioned in the Docs -> Getting started:

yep! thanks @GavPierce 🙏
is that enough @matijaSos or do you think the instructions could be improved somehow?

What I did in wasp new is actually added a command to do it:
cp .env.server.example .env.server

I would consider doing that. I know for me, when reading docs, most of my focus goes on code to copy and execute :D, and less on text, and this way you make it really easy for me to do the right thing.


Updated subRequest to get serverParams correctly

Reading your pr I see 2 questions/comments :

I think we should use the same request type then the one in the container
That means the container should only give the Request class not a Request instance and the App should create this new Request for request and sub-request.
Or you should clone the current request to make subrequest what can make sense too, so subrequest could become an alias for __invoke__ .

$app->get('/bar', function($req, $res) use($app) {
    $uri = $req->getUri()->withPath('/foo');
    $sub_req = $req->withUri($uri);
    return $app->subRequest($sub_req,  $res);
});

Why do not run App middleware ? Maybe that make no sense for session but that can be usefull for a cachemiddleware.
Maybe We should add a request stack.
App stack once per HTTP request,
Request stack once per internal request,
Route stack once per route per request

@lalop not sure I understand point 2. In point 1 the code example seem to carry the wrong signature for the subRequest method.

Hello @silentworks,
For point 1, subRequest has a wrong signature because it's what I propose, having the same signature for App::subRequest and App::__invoke.
For point 2, I wanted to notice that with this implementation app's middlewares will not see subrequests.
That can be okay in most of case but maybe not for all so I proposed to add a new middlewae stack between App and Route, App's stack will be run once, Request's stack will be run once per (sub)request, and Route's stack is defined for each route.
Is that more clear ?

Re point 1, subRequest exists solely to avoid you having to create the correct request object yourself.
i.e., you could do:
$app->get('/bar', function($req, $res) use($app) {
    $uri = $req->getUri()->withPath('/foo');
    $sub_req = $req->withUri($uri);
    return $app($sub_req,  $res);
});

without needing this method at all.
As such, subRequest is a convenience method, and that's okay.
Re point 2: I can see the argument, but disagree. a sub request runs in the context of the first request, not as a completely independent thing. If you have middleware that needs running on both the request and subrequest, then use route middleware.
three places to put middleware would just be confusing for a very specialised edge-case.

Merged


Switch to using -destination instead of -sdk

the -sdk flag apparently isn't super useful. We should switch to using -destination
Specifically:

when building an iOS app: -destination 'generic/platform=iOS'
when testing an iOS app: -destination 'platform=iPhone Simulator,device=iPhone 6'
when building or testing a mac app: -destination 'platform=OS X' (haven't tested this)

obviously it'd be nice to specify that device as well.


Browser download always blocks file

My Chrome browser always prevents the PDF from downloading. Is there a way to permanently allow this?

Do you have any screenshots or context of what you are on about? Also are you using nginx or anything

You can try this:

Open Chrome Settings.
Go to Privacy and Security and then Site Settings.
Find PDF Documents settings.
Enable "Download PDF files instead of automatically opening them in Chrome."

Stirling pdf has a settings cog menu in top right
Have you changed the setting within that to be "download file?"
Is the above still required after that change?

there is no "download file" when clicking the cog

there is no "download file" when clicking the cog

"Choose download option:"
"Open in same window"
Changing that should stop it opening in same window

I use Vivaldi Browser and "Download File" also dosnt work anymore. Firefox is normal.
No error in Console log.
Only:
Deprecated feature used
Unload event listeners are deprecated and will be removed.
downloader.js:261

Do you still see this issue, and does it also happen for installs like
https://stirlingpdf.io/
particularly wondering on

In Chrome the download works but tells me the download is insecure, luckily I can override it, but it's not ideal.

as I cant reproduce this, closing ticket for now, please let me know!


Split into multiple artifacts on maven central

The problem with this library is that it pulls log4j and logback whether or not you need them. This can cause issues where they fight each other.

Thanks, that kind of bothered me for a while too.
But I was thinking "if nobody complains, then maybe is not an issue" :-)
Working on it (I had a few commits already).
Want to do a bite more cleanup, but will push a new release soon(ish)

Done, version 10.0.7 has 3 modules, split per logger, with minimal dependencies.
In theory I can split is further to have versions with / without jansi, but it is a bit too much maintenance...


Bitron AV2010/32 thermostat

Device description
Bitron AV2010/32 Wireless wall thermostat with relay
MQTT message with device information
PUT here the device data you receive when publish message with topic
zigbee2mqtt/bridge/config/devices, as example
https://www.zigbee2mqtt.io/devices/AV2010_32.html

"ieeeAddr":"0x000d6f000ef17265","type":"EndDevice","networkAddress":42412,"model":"AV2010/32","friendly_name":"Thermostaat","manufacturerID":4209,"manufacturerName":"Bitron Home","powerSource":"Battery","modelID":"902010/32","hardwareVersion":2,"softwareBuildID":"V1b225-20151013","dateCode":"2017082217234152","lastSeen":1574720337979}``

**MQTT messages from device**

zigbee2mqtt/Thermostaat', payload '{"local_temperature":20.6,"linkquality":63,"occupied_heating_setpoint":16.5}'

**MQTT state change commands**
If device supports state change put MQTT topics + payload examples to change device state here
https://www.zigbee2mqtt.io/devices/AV2010_32.html

Done. Could you please update plugin and check.

Works like a charm!! Thank you very much!


Some unexpected errors from repetitively goto'ing same URL

While testing with a simple loop that repetitively requests the same URL, I've run into a some different unexpected error situations.
In one case, requesting https://www.whatismyip.com/ led to some uncaught DNS-related errors. Sample code & results txt:
process.env.SA_SHOW_REPLAY="false";
const { Agent } = require('secret-agent');

async function run() {
  var agent = await new Agent();
  let url = 'https://www.whatismyip.com/';
  for (let i = 0; i < 10; i++) {
    try {
      console.log('here 1');
      let resource = await agent.goto(url, 5000);
      console.log('here 2');
      let statusCode = await resource.response.statusCode;
      console.log(`here 3: ${statusCode}`);
    } catch (err) {
      console.log(`Caught an exception: ${err}`);
    }
  }
  await agent.close();
}
run();

Results:
Results1.txt
I'm not clear where the reference to ipv6.whatismyip.com came from, does that site sometimes redirect to that as an anti-bot technique? Also not clear if this is the expected behavior from secret-agent for a DNS lookup error, in terms of the unhandled errors?
In a 2nd case, repeatedly requesting https://www.slashdot.org/ using the same loop code, led to:
Results:
Results2.txt
Not clear what caused that or if it is important.
Lastly, repeatedly requesting http://www.posthuman.com/ leads to the requests timing out after the 1st success. I've tried removing my 5 sec timeout and then the normal 30 sec timeout eventually occurs. This site is a basic web hosting site on 1and1/Ionos shared hosting. They advertise as providing anti-DDOS protection, could this behavior be some anti-bot detection system, or is it something else? The behavior is perfectly repeatable, always after starting the program it gets 1 working 200 status response, then everything times out after that.
Results:
Results3.txt
Results without me catching the error:
Results4.txt

@A-Posthuman thanks for reporting!
It looks like the errors in whatsmip.com are because we don't support ipv6 yet. On the actual page, that site is just trying to show you what your ip is on ipv4 and ipv6. Their ipv6 address doesn't have an ipv4 ip (which is rare on the web), and since we can't find an address, it's unable to load. Depending on your use case, this is likely just ignorable. That said, we should be catching it, so I'll look into that part.
Slashdot: I'm unsure if these errors are impacting loading your pages, but it shouldn't be exploding if the socket is undefined. I see a spot that should be fixed for this one.
I'm seeing the same with Posthuman, but it looks like something is just hanging internally. I'm looking deeper into this one.

@A-Posthuman fyi, we weren't properly handling cached loads for repeatedly loading posthuman. Will be fixed in the next release.

Cool, y'all are the best! BTW I had posted on the discord asking is there a build howto or recipe on how to build the current github codebase if I ever want to clone it, like for example if I want to make a local build to test out some of the latest code before you publish a new official build version?

Testing using 1.3.0 alpha 2, seeing a different issue with trying to get statusCode of the 2nd request to www.posthuman.com:
debug.txt
Testing https://www.whatismyip.com/ the DNS/IPv6 issue is fixed, however seeing an occasional issue:

UnhandledPromiseRejectionWarning: Error: Failed to load url

On successive random runs of my program, perhaps 10% of them fail with this. When this happens all my .goto attempts immediately all fail instantly if I try/catch. If I stop and wait a little while and rerun my program then it tends to work ok again for a bit. Sorry I don't have a reliable way to replicate this other than repeatedly running my program several times.
debug.txt

Would you mind grabbing the session database from the logs? e141c6d0-6b42-11eb-b12b-f16875b05b03.db. Thanks!

Sure, here it is:
e141c6d0-6b42-11eb-b12b-f16875b05b03.zip

I dumped that session above, may be related to hitting a hCaptcha, but that's as far as I could figure out.
Regarding the other issue with the 2nd requests to posthuman.com not getting a statusCode, do you need the session db for that one? I've attached that one too if you do:
13f22f50-6b40-11eb-9a69-c9d190609444.zip

For the e141c6d0-6b42-11eb-b12b-f16875b05b03.zip one, it looks like you're getting sent to a CloudFlare "whatsmyip" site. This site seems to have max-requests allowed per IP.

The second request to Posthuman (BTW, is this your site?) is using cache, so doesn't have a response. I'll tweak the response so that it always returns an object, and adds a parameter for responses loaded from cache

Thanks for the additonal cache fix. On the e141c6d0-6b42-11eb-b12b-f16875b05b03 / whatismyip issue, I'm not clear on if the behavior being returned from the redirect to the captcha is expected, or a bug?
As a user, I would expect the tab should redirect/navigate to whatever page it ends up being sent to, and then if it successfully loads a captcha screen, I should get back access to that content body and a statusCode, etc. I'm not clear on why if it is a captcha then instead I get returned a an unhandled "UnhandledPromiseRejectionWarning: Error: Failed to load url" ?

You're absolutely correct. I was assuming this was coming from the browser, but I see we're actually looking for errors >=400 and sending back a navigation error. I think it makes much more sense to return the status code you landed on as a successful "load" even if you landed on a 404 or 403 (as in this case).

Following up, when testing the cache issue with posthuman.com, on the 2nd and subsequent requests, instead of getting a 200 statusCode back, I'm getting "undefined".

Yeah, there’s no http request since it’s an in memory cache. There’s a field though that indicates if it has been cached. Do you think it would be preferable to return a special code like a negative status code?

On Mar 18, 2021, at 8:48 PM, A-Posthuman @.***> wrote:

Following up, when testing the cache issue with posthuman.com, on the 2nd and subsequent requests, instead of getting a 200 statusCode back, I'm getting "undefined".
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


bug: Card and ion-list in the same view

Type: bug
Platform: mobile webview
If you emulate with mobile (iphone 4 / nexus 4), the last ion-list-item has less height. What is wrong?
http://codepen.io/danicomas/pen/gbmvEm

Greetings, @danicomas!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Your progress on this issue has been saved at the following url:
link to Ionic issue form
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

http://forum.ionicframework.com/t/ion-scroll-you-can-scroll-down-too-much/2764


v0.25.4 error: unable to parse import map JSON

After upgrading to v0.25.4, I'm getting an error when running any lume command (see video).
There doesn't seem to be anything in the changelog that would have caused this.
https://user-images.githubusercontent.com/43307367/126526623-a1b8fd27-917a-42ec-8020-406fec724674.mp4

mmm, that's weird. We have made some changes here (basically removed the base64 encode to the url). Let me check in windows.

Ok, I just released v0.25.5. Seems like in Windows the import map argument is not properly escaped by deno.
I'm closing this. Feel free to reopen if it's not fixed.

I tried to upgrade lume to 0.25.5 but got this error:
$ deno upgraded && lume upgrade
....
Download<EMAIL_ADDRESS>error: Unable to load<EMAIL_ADDRESS>import map

Caused by:
    Import<EMAIL_ADDRESS>failed: 404 Not Found

Update successful! You’re using the latest version of lume: v0.25.5!
See the changes in https://github.com/lumeland/lume/blob/v0.25.5/CHANGELOG.md

$ lume --version
🔥lume v0.20.2

$ lume -s
Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>lume: Import<EMAIL_ADDRESS>failed: 404 Not Found
    at file:///home/kusaeni/project/deno/responsive/_config.js:2:0
TypeError: Import<EMAIL_ADDRESS>failed: 404 Not Found
    at file:///home/kusaeni/project/deno/responsive/_config.js:2:0
    at async buildSite (https://deno.land/x/lume@v0.20.2/cli/utils.js:19:19)
    at async Module.run (https://deno.land/x/lume@v0.20.2/cli/build.js:46:16)
    at async maybeRun (https://deno.land/x/lume@v0.20.2/cli.js:108:28)
    at async cli (https://deno.land/x/lume@v0.20.2/cli.js:116:5)
    at async https://deno.land/x/lume@v0.20.2/cli.js:55:5

Ubuntu 20.04.2 LTS - WSL

Hi @kuspoes.
Yes, It can happens on upgrade from some old versions.
Reinstall again (deno run -A https://deno.land/x/lume/install.ts) solve the problem.
Version 1.0.0 will be releases soon, and after that there won't be more backward breaking changes.


⚠ ClamAV has degraded performance

In 051c0ea, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in cb04809.


Remove unsupported props from native

There was some discussion about the potential cost of forwarding unsupported props to React Native versus stripping them in the RSD runtime.

A similar thing would probably make sense for the stylex shim where we use the list to support @supports.


Fix windows doc

Replace the name of the libnabo cmake variables to match the ones in the cmake scripts
(like here)

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

ok to test

Thanks a lot for adapting the documentation !

Thanks a lot for adapting the documentation !


Fix issues arising with material-ui v1

material-ui was released a day ago and broke a couple stuff, including import paths for menu.
You can checkout the breaking changes here: https://github.com/mui-org/material-ui/releases
I'll try to put together a PR to fix things.

Hey @charlax,
Thanks for bringing this to my attention. I really appreciate your continued usage of <MUIPlacesAutocomplete>. Life has been so busy lately that I haven't had much time to continue to iterate and improve <MUIPlacesAutocomplete>.
Bug #38 was also filed for the same reasons so I am going to close this bug as a duplicate of that. I'll try to resolve the issues and close out bug #38 ASAP.


[Python] Unable to build pyarrow wheel for macOS 10.13 when installing from PyPI

Describe the bug, including details regarding any error messages, version, and platform.
I'm trying to install pyarrow on macOS 10.13 using pip.
As of pyarrow 10.0 there are no pre-built wheels for macOS 10.13, so pip tries to build a wheel from source.
I get the following error message:
  CMake Error at CMakeLists.txt:63 (find_package):
    By not providing "FindArrow.cmake" in CMAKE_MODULE_PATH this project has
    asked CMake to find a package configuration file provided by "Arrow", but
    CMake did not find one.

    Could not find a package configuration file provided by "Arrow" with any of
    the following names:

      ArrowConfig.cmake
      arrow-config.cmake

    Add the installation prefix of "Arrow" to CMAKE_PREFIX_PATH or set
    "Arrow_DIR" to a directory containing one of the above files.  If "Arrow"
    provides a separate development package or SDK, be sure it has been
    installed.

  -- Configuring incomplete, errors occurred!
  See also "/private/var/folders/2h/gnd6b40x36n7xwscj8712hsc0000gn/T/pip-install-gqi21gpr/pyarrow_24109b85dd934301b68bc56161834085/build/cpp/CMakeFiles/CMakeOutput.log".
  error: command '/opt/local/bin/cmake' failed with exit code 1
  [end of output]

See full install log below:

❯ python3 -m venv venv
❯ . venv/bin/activate
❯ pip install pyarrow
Collecting pyarrow
  Using cached pyarrow-10.0.1.tar.gz (994 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting numpy>=1.16.6
  Using cached numpy-1.24.1-cp310-cp310-macosx_10_9_x86_64.whl (19.8 MB)
Building wheels for collected packages: pyarrow
  Building wheel for pyarrow (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pyarrow (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [318 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.macosx-10.13-x86_64-cpython-310
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/orc.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/conftest.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_generated_version.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/benchmark.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_compute_docstrings.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/ipc.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/util.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/flight.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/cffi.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/substrait.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/filesystem.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/__init__.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/plasma.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/types.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/dataset.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/cuda.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/feather.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/pandas_compat.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/fs.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/csv.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/jvm.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/hdfs.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/json.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/serialization.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/compute.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_tensor.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_ipc.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/conftest.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_convert_builtin.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_misc.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/arrow_16597.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_gandiva.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/strategies.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_adhoc_memory_leak.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/arrow_7980.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/util.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_orc.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_table.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_array.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_deprecations.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_serialization_deprecated.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/__init__.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_io.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_util.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_cuda_numba_interop.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_cpp_internals.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_cffi.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_schema.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_jvm.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_plasma_tf_op.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_fs.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_udf.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_filesystem.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/pandas_threaded_import.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/pandas_examples.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_cython.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_sparse_tensor.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_dataset.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_builder.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_cuda.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_extension_type.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_feather.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_pandas.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_memory.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_exec_plan.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_flight.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/read_record_batch.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_json.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_serialization.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_compute.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_hdfs.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/deserialize_buffer.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_strategies.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_csv.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_plasma.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_scalars.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_gdb.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_types.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/test_substrait.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/vendored
      copying pyarrow/vendored/version.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/vendored
      copying pyarrow/vendored/__init__.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/vendored
      copying pyarrow/vendored/docscrape.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/vendored
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/parquet
      copying pyarrow/parquet/encryption.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/parquet
      copying pyarrow/parquet/__init__.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/parquet
      copying pyarrow/parquet/core.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/parquet
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_basic.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/conftest.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/encryption.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_parquet_writer.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_metadata.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/__init__.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_datetime.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/common.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_dataset.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_data_types.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_pandas.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_parquet_file.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_compliant_nested_type.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_encryption.py -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/parquet
      running egg_info
      writing pyarrow.egg-info/PKG-INFO
      writing dependency_links to pyarrow.egg-info/dependency_links.txt
      writing entry points to pyarrow.egg-info/entry_points.txt
      writing requirements to pyarrow.egg-info/requires.txt
      writing top-level names to pyarrow.egg-info/top_level.txt
      listing git files failed - pretending there aren't any
      reading manifest file 'pyarrow.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      warning: no files found matching '../LICENSE.txt'
      warning: no files found matching '../NOTICE.txt'
      warning: no previously-included files matching '*.so' found anywhere in distribution
      warning: no previously-included files matching '*.pyc' found anywhere in distribution
      warning: no previously-included files matching '*~' found anywhere in distribution
      warning: no previously-included files matching '#*' found anywhere in distribution
      warning: no previously-included files matching '.git*' found anywhere in distribution
      warning: no previously-included files matching '.DS_Store' found anywhere in distribution
      no previously-included directories found matching '.asv'
      writing manifest file 'pyarrow.egg-info/SOURCES.txt'
      copying pyarrow/__init__.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_compute.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_compute.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_csv.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_csv.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_cuda.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_cuda.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_dataset.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_dataset.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_dataset_orc.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_dataset_parquet.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_exec_plan.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_feather.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_flight.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_fs.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_fs.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_gcsfs.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_hdfs.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_hdfsio.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_json.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_orc.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_orc.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_parquet.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_parquet.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_parquet_encryption.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_parquet_encryption.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_plasma.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_pyarrow_cpp_tests.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_pyarrow_cpp_tests.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_s3fs.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/_substrait.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/array.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/benchmark.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/builder.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/compat.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/config.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/error.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/gandiva.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/io.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/ipc.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/lib.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/lib.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/memory.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/pandas-shim.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/public-api.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/scalar.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/serialization.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/table.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/tensor.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      copying pyarrow/types.pxi -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/common.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_feather.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/__init__.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libgandiva.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_python.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_flight.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_dataset_parquet.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_dataset.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_substrait.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_cuda.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libarrow_fs.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/includes/libplasma.pxd -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/includes
      copying pyarrow/tests/bound_function_visit_strings.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      copying pyarrow/tests/pyarrow_cython_example.pyx -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tensorflow
      copying pyarrow/tensorflow/plasma_op.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tensorflow
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      copying pyarrow/src/ArrowPythonConfig.cmake.in -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      copying pyarrow/src/ArrowPythonFlightConfig.cmake.in -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      copying pyarrow/src/CMakeLists.txt -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      copying pyarrow/src/arrow-python-flight.pc.in -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      copying pyarrow/src/arrow-python.pc.in -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/feather
      copying pyarrow/tests/data/feather/v0.17.0.version.2-compression.lz4.feather -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/feather
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/README.md -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.jsn.gz -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.orc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.test1.jsn.gz -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.test1.orc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.jsn.gz -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.orc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/decimal.jsn.gz -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/decimal.orc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/orc
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.all-named-index.parquet -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.column-metadata-handling.parquet -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.parquet -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.some-named-index.parquet -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/tests/data/parquet
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow
      creating build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/CMakeLists.txt -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/api.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_pandas.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_pandas.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_python_internal.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/benchmark.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/benchmark.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/common.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/common.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/csv.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/csv.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/datetime.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/datetime.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/decimal.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/decimal.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/deserialize.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/deserialize.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/extension_type.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/extension_type.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/filesystem.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/filesystem.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/flight.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/flight.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/gdb.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/gdb.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/helpers.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/helpers.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/inference.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/inference.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/init.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/init.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/io.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/io.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/ipc.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/ipc.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/iterators.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_convert.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_convert.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_internal.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_interop.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_to_arrow.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_to_arrow.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/parquet_encryption.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/parquet_encryption.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pch.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/platform.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow_api.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow_lib.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_test.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_test.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_to_arrow.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_to_arrow.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/serialize.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/serialize.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/type_traits.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/udf.cc -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/udf.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/visibility.h -> build/lib.macosx-10.13-x86_64-cpython-310/pyarrow/src/arrow/python
      running build_ext
      creating /private/var/folders/2h/gnd6b40x36n7xwscj8712hsc0000gn/T/pip-install-gqi21gpr/pyarrow_24109b85dd934301b68bc56161834085/build/cpp
      -- Running CMake for PyArrow C++
      cmake -DARROW_BUILD_DIR=build -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_LIBDIR=lib -DCMAKE_INSTALL_PREFIX=/private/var/folders/2h/gnd6b40x36n7xwscj8712hsc0000gn/T/pip-install-gqi21gpr/pyarrow_24109b85dd934301b68bc56161834085/build/dist -DPYTHON_EXECUTABLE=/Users/dwales/Desktop/test/venv/bin/python3 -DPython3_EXECUTABLE=/Users/dwales/Desktop/test/venv/bin/python3 -DPYARROW_CXXFLAGS= -DPYARROW_WITH_DATASET=off -DPYARROW_WITH_PARQUET_ENCRYPTION=off -DPYARROW_WITH_HDFS=off -DPYARROW_WITH_FLIGHT=off /private/var/folders/2h/gnd6b40x36n7xwscj8712hsc0000gn/T/pip-install-gqi21gpr/pyarrow_24109b85dd934301b68bc56161834085/pyarrow/src
      -- The C compiler identification is AppleClang <IP_ADDRESS>01145
      -- The CXX compiler identification is AppleClang <IP_ADDRESS>01145
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      CMake Error at CMakeLists.txt:63 (find_package):
        By not providing "FindArrow.cmake" in CMAKE_MODULE_PATH this project has
        asked CMake to find a package configuration file provided by "Arrow", but
        CMake did not find one.

        Could not find a package configuration file provided by "Arrow" with any of
        the following names:

          ArrowConfig.cmake
          arrow-config.cmake

        Add the installation prefix of "Arrow" to CMAKE_PREFIX_PATH or set
        "Arrow_DIR" to a directory containing one of the above files.  If "Arrow"
        provides a separate development package or SDK, be sure it has been
        installed.

      -- Configuring incomplete, errors occurred!
      See also "/private/var/folders/2h/gnd6b40x36n7xwscj8712hsc0000gn/T/pip-install-gqi21gpr/pyarrow_24109b85dd934301b68bc56161834085/build/cpp/CMakeFiles/CMakeOutput.log".
      error: command '/opt/local/bin/cmake' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pyarrow
Failed to build pyarrow
ERROR: Could not build wheels for pyarrow, which is required to install pyproject.toml-based projects

Component(s)
Python

You're using Homebrew, right?
If so, could you install apache-arrow (brew install apache-arrow) before pip install pyarrow?

I'm using MacPorts. (Homebrew doesn't support 10.13 anymore.) But I'll try the equivalent and report back after work.

Ah, then you need to install Apache Arrow C++ manually.
See also:

https://arrow.apache.org/docs/dev/developers/python.html#building-on-linux-and-macos
#33814

I don't think 10.13 is still maintained by Apple. I'm still using it because I still have 32 bit apps, and 32 bit apps aren't supported by 10.15+.

BTW, is macOS 10.13 still maintained?

Officially, also 10.14 and 10.15 are no longer maintained (the release notes still shows them, but the last releases for 10.14 was more than a year ago, wiki says "Unsupported as of October 2021"), but I think we should still try to provide binaries for MacOS < 11 at the moment (as long at that is reasonably possible).
(note, I don't use Mac myself, I don't have a good idea about how common it is to have a Mac that can't be updated to at least 10.14. According to this site, 10.14 (Mojave) should run typically on machines from 2012)

In general, I want to drop support for platforms that aren't maintained by upstream including macOS 10.13. We already have many supported platforms. I think that we don't have enough resources to support unmaintained platforms.
Anyway, we can discuss this on<EMAIL_ADDRESS>


Laravel Collection keyBy

Hi, I was testing the below code in laravel tinker.
$c=collect([(object)['id'=>0,'name'=>'asd'],(object)['id'=>1,'name'=>'qwe']]);
$c->keyBy("id")

results for the above code is
Illuminate\Support\Collection {#4317
     all: [
       {#4340
         +"id": 0,
         +"name": "asd",
       },
       {#4338
         +"id": 1,
         +"name": "qwe",
       },
     ],
   }

When I changed the id of the first element to a non zero value like the below code
$c=collect([(object)['id'=>3,'name'=>'asd'],(object)['id'=>1,'name'=>'qwe']]);
$c->keyBy("id")

It gives the intended results as below
Illuminate\Support\Collection {#4340
     all: [
       3 => {#4341
         +"id": 3,
         +"name": "asd",
       },
       1 => {#4339
         +"id": 1,
         +"name": "qwe",
       },
     ],
   }

Is there is a way to get a result like below when there is an element with value zero in laravel collection?
Illuminate\Support\Collection {#4340
     all: [
       0 => {#4341
         +"id": 0,
         +"name": "asd",
       },
       1 => {#4339
         +"id": 1,
         +"name": "qwe",
       },
     ],
   }

Originally posted by @upeksha1996 in https://github.com/laravel/framework/discussions/35279

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

@driesvints I asked it in the discussion but I anyway posted it as a bug since it was not mentioned in the documentation that keyBy cannot be used with zero as a key.

found any solution?


fixed typo from 'Training has starting' to '...has started'

I noticed this when checking the progress of my training run. Cheers!

Thank you :)


Small fixes on init

password is not required
default value for remote MySQL host is localhost instead of remotehost

Looks good, thanks for your contribution


feat(backend): batch_process_todo接口性能优化

关联研发信息
dev_branch: feat/batch_process_todo/#8109
target_branch: v1.5.0


[Bug]: Does not work with eslint v9

Contact Details
No response
What happened?
I wanted to use this package with eslint v9, but it does not support it yet.
Version
4.3.0
What browsers are you seeing the problem on?
No response
Relevant log output
Error: This method cannot be used with flat config. Add your entries directly into the config array.
    at assertEslintrcConfig (/Users/erica.gucciardo/observe/code/js/node_modules/eslint/lib/linter/linter.js:1256:15)
    at Linter.getRules (/Users/erica.gucciardo/observe/code/js/node_modules/eslint/lib/linter/linter.js:2185:9)
    at Object.<anonymous> (/Users/erica.gucciardo/observe/code/js/node_modules/eslint-plugin-disable-autofix/index.js:39:29)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

https://github.com/chiefmikey/eslint-plugin-disable-autofix/releases/tag/v5.0.0


Opaque type support

Hello. How is the support for opaque types. I saw that the PR #293 was abandoned.
Is there any hope that support will be introduced or are there any problems that need to be solved

I read the PR #293 story. I did not find any blocking problem and it is not clear why it was abandoned.
I am ready to complete this task.

@rogurotus Hi thanks for your interest :) I will check the history and list blockers here, probably after 10 minutes.

Oh I see it. In addition to

https://github.com/fzyzcjy/flutter_rust_bridge/pull/293

Also need to read

https://github.com/fzyzcjy/flutter_rust_bridge/issues/243
https://github.com/fzyzcjy/flutter_rust_bridge/issues/68

And the comment says:

    (Sad) updates:

External size is just an input to GC scheduling heuristic.
However please don't use this type. It was introduced for some internal usage and has somewhat confusing semantics.

https://github.com/dart-lang/sdk/issues/47900

Please don't use this type. It was introduced for some internal usage and has somewhat confusing semantics.

https://github.com/dart-lang/sdk/issues/47901
In short: We should NOT use type Dart_CObject_kNativePointer.

Originally posted by @fzyzcjy in https://github.com/fzyzcjy/flutter_rust_bridge/issues/243#issuecomment-1038525958

I have quickly gone through the issues and PRs. Looks like, if we want fully automatic way, i.e. let Dart GC to free Rust memory, we are "strongly discouraged" in https://github.com/fzyzcjy/flutter_rust_bridge/issues/243#issuecomment-1002827809. However, if we just do a half automatic way, i.e. let users manually call dispose, and the Dart GC is just a sanity checker, then I have not see immediate blockers yet.

@rogurotus I am ready to complete this task.

I am willing to review and merge the PR :)

I read the PR #293 story. I did not find any blocking problem and it is not clear why it was abandoned.
I am ready to complete this task.

A lot of things have changed since that PR was opened, the most significant of which are WeakReference and FinalizationRegistry. Now there might be a better way to do this that doesn't force the user to use the Opaque wrapper anymore.

For future readers: It is sometimes strongly needed to have dispose() manually called; but for other cases, it is unneeded, and you can forget dispose(): https://github.com/fzyzcjy/flutter_rust_bridge/issues/1448


chore: added lint rule for function definitions

Before it never picked picked up most functions, if this is too noisey we can turn it off but I think all functions should have jsdoc comments
before:

after:

Ooof this is going to add a lot of warnings to existing code

Ooof this is going to add a lot of warnings to existing code

Yep that is the point!

but its just a warning so it should only annoy you and not block anything

im in


Develop an automatic packing for the extractor

Develop an automatic packing for the extractor
Currently, the extractor program use a reference of packing optimizations.
Problem 1 : it takes time
Problem 2: it is limited to 750 bodies

use "-fibo"


R23: Web Application: The software shall be tested in Amazon Web Services (AWS) Environment

Done.  Several bugs exist. DR tickets created.


Update version of go, and run vuln checking

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@8716294). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #184   +/-   ##
=======================================
  Coverage        ?   31.17%
=======================================
  Files           ?        8
  Lines           ?      526
  Branches        ?        0
=======================================
  Hits            ?      164
  Misses          ?      333
  Partials        ?       29

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add a link to service on router detail view

What does this PR do?
This PR adds the way to go to a service displayed in the router view detail by a click
Motivation
I used a lot Traefik to have an overview of my router and my service and ensure all is correct when I am doing my configuration. However, I cannot go to the service from the router detail view, I have to click on "services" tab, search my service (among 30, for the moment...) and click again. I add the link and it works perfectly!
Additional Notes
I did the feature the more simple way I could find and the most soft. I am opened to every suggestions or changes to respect the code's guidelines of the project :)
Thank for your work! ❤

You are welcome :)


chore: bdd-spring-1574839839 to 0.0.1

chore: Promote bdd-spring-1574839839 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


SOLR-17265: Fix randomized PRS testing

https://issues.apache.org/jira/browse/SOLR-17265
This fixes the test errors introduced by https://github.com/apache/solr/pull/2230
I'm not really certain what the previous logic was supposed to be doing, but isPRS() practically returned a random true or false every time it was called, since the "use.per-replica" sysProp was never set.
I've simplified the logic considerably. Before a class is run "solr.prs.default" is set to either true or false (either randomly, or determined by the Class annotation). Then ever call to isPRS() will read that sysProp to determine if the default is PRS or not.

Thanks for the info on those. I've standardized both the reseting of sysProps as well as where the option is set from.


DeserializeObject with empty string returns unexpected null

Source/destination types
public class TestsEmptyString
    {
        public string str { get; set; }
    }

Source/destination JSON
"\"\""

Expected behavior
var str = """";
var test = JsonConvert.DeserializeObject(str);
Should throw an exception / go to a custom TypeConverter if there is any.
In my case, I have a TypeConverter that takes the string and creates TestsEmptyString object with str set as the string.
This works every time except in the case of  """".
For example  ""foo"" gets to my TypeConverter ConvertFrom and CanConvertFrom methods
But """" just returns null without getting to that converter.
Please note that any other string like ""foo"" will behave differently than  """".
Also, my project is configured with nullable annotation context enabled which makes TestsEmptyString not nullable, so I don't understand how it even works.
Actual behavior
returns null to a non-nullble object
Steps to reproduce
var str = "\"\"";
var test = JsonConvert.DeserializeObject<TestsEmptyString>(str); // returns null

var otherStr = "\"foo\"";
var test = JsonConvert.DeserializeObject<TestsEmptyString>(otherStr); // throws an exception

I would like to stress one point here - since C# we have nullable reference types in the language. If the assembly calling to Newtonsoft has opted in to nullable aware context, then 'null' is no longer a legitimate value for a string type from the developers' perspective.
Thus the empty string coersing behavior of Newtosoft.Json performed by CoerceEmptyStringToNull() method (as mentioned in #1687) is seriously wrong as the one that  makes C# string not round-tripable, if the nullable annotation context is enabled.

I have a similar problem. I have a type with required fields. I'd want to rely on json serializer to throw serialization exception if it can't correctly deserialize required fields, but an empty string doesn't trigger serialization exception (be it just an empty string "" or a emtpy json string "\"\"");
using Newtonsoft.Json;
using Newtonsoft.Json.Serialization;
using Newtonsoft.Json.Converters;

public class ApiResponse<T>
{
    [JsonProperty(Required = Required.Always)]
    public bool Ok { get; set; }

    [JsonProperty(Required = Required.Always)]
    public T Result { get; set; }
}

var emptyJsonString = @"""""";
JsonConvert.DeserializeObject<ApiResponse<int>>(emptyJsonString)  // returns null

var emptyString = "";
JsonConvert.DeserializeObject<ApiResponse<int>>(emptyString)      // returns null

System.Text.Json work like expected and when trying to de-serialize empty string will (always?) fail:
System.Text.Json.JsonException: 'The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. Path: $ | LineNumber: 0 | BytePositionInLine: 0.'
Same is true for all:
Newtonsoft.Json.JsonConvert.DeserializeObject(""); // null
System.Text.Json.JsonSerializer.Deserialize(""); // error
Newtonsoft.Json.JsonConvert.DeserializeObject(""); // null
System.Text.Json.JsonSerializer.Deserialize(""); // error
Newtonsoft.Json.JsonConvert.DeserializeObject(""); // null
System.Text.Json.JsonSerializer.Deserialize(""); // error

Hello! This is still actual. It is very ambiguous because missing required property is treated as an Exception, however, something like this "   " return null.
I understand, that just starting to throw exceptions, in this case, may break backward compatibility, but could you please consider adding an option to JsonSerializerSettings which would enable throwing Exceptions in such cases?


Fetch upstream change which resolves axios security vulnerability

Resolves https://github.com/advisories/GHSA-cph5-m8f7-6c5x

I think @tmeasday is the right person to tag here?

Thanks @adayNU

We will try and get this released ASAP.

Released as v2.0.4.


NowPlaying.app won't start on OS X 10.8.2, error: Trace/BPT trap 5

Hi there,
I was very happy with NowPlaying.app on previous installations of OS X, but on my freshly installed OS X 10.8.2 (Mountain Lion) it just won't start.
Starting it from command line gives an error:

$ /Applications/NowPlaying.app/Contents/MacOS/NowPlaying
Trace/BPT trap: 5
I hope this can be fixed soon, I really miss it. :)
Regards,
Eveline.

I'm running it on Mac OS 10.11.2 (El Capitan) if anyone wants a copy


2023-05-08 - KDB Project Call Meeting Agenda

Date
Monday, May 8, 2023 - 9:30am ET / 2:30pm UK
// Second Monday of every month
Attendees

Fullname
Affiliation
GitHub Username

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

(5 min) Convene, roll call, welcome new people.
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
(5 min) Approve previous meeting minutes.
(5 min) Updates on Anaconda?
(10 min) Module loader interoperability.

Any updates on PyKX / dep.q overlaps?
Firmer ideas on namespace conventions?

(5 min) PyKX / verbose.q next steps?

https://code.kx.com/pykx/1.4/api/q/q.html
Comparison operator baked into the string:

https://code.kx.com/pykx/1.4/api/query.html#pykx.query.SQL.prepare
pykx.q.qsql.select(qtab, where=['col1=`a', 'col2<0.3'])

(5 min) Splaying from one HDB into another?

Possibly made safer with qclone.q.

(5 min) KX Con

Any new items on the schedule worth calling out?

(5 min) Any interest in a FINOS LLM Project?

Colin Ebererhardt's post made the front page of Hacker News:

"Re-implementing LangChain in 100 lines of code (scottlogic.com)"

https://news.ycombinator.com/item?id=35820931
https://blog.scottlogic.com/2023/05/04/langchain-mini.html

Getting easier to fine tune LLMs for finance / fintech / regtech:

"Hello Dolly: Democratizing the magic of ChatGPT with open models (databricks.com)"

https://news.ycombinator.com/item?id=35288063
https://www.databricks.com/blog/2023/03/24/hello-dolly-democratizing-magic-chatgpt-open-models.html

(5 min) AOB, Q&A, Adjourn.

Decisions Made

Decision 1
Decision 2
...

Action Items

Action 1
Action 2
...

WebEx info
Webex

https://finos.webex.com/finos/j.php?MTID=me61719ca3c3295a7cc76762d78392bc3

Dial-in and Project Materials

US: +1-415-655-0003 US Toll
UK: +44-20319-88141 UK Toll
Access code: 2704 417 0390
GitHub Repos:

https://github.com/finos/kdb
https://github.com/finos/kdb-studio

Wiki Page:

https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/329383945/kdb+Project

KDB Metrics on FINOS

https://metrics.finos.org/goto/033b15c80f0d08cab70f40f4358932f6

hi

hi today as well

hi

James McLeod / FINOS

Howdy

FINOS Big Boost Mondays Event - Monday 12th June at Synechron, Belfast, Northern Ireland - https://tg.zngly.com/znglist/big-boost-mondays-belfast-june-12th-at-synechron/?c=cG9zdDo5OTExMzg=


jcenter() closed

recyclerview-flexibledivider package was hosted on jcenter() but it is closed now.
Can you put it in another repository and can the change the read.me file

Hi,
I need it too.
Thanks.

Add this repository to your build.gradle maven { url 'https://repo.spring.io/plugins-release/' }

replace with:
implementation 'com.github.mazenrashed:RecyclerView-FlexibleDivider:1.5.0'


Set timeouts to AirbrakeNotifier's connection

HttpURLConnection#setReadTimeout and ConnectTimeout methods should be called before sending requests to the servers. You should parameterize those timeout values ideally.

Thanks!


Fix syntax errors in config.php template

Thanks @CthulhuDen.
This should target 4.0 branch.
You can either rebase and change the target thanks to GitHub's new feature by clicking on "edit" on the title of the PR, or we can handle it on merge.

👍

@HeahDude I tried to do that, but it seems it now tries to merge master into 4.0. Perhaps I should just open another PR.

@CthulhuDen If you don't know how to rebase on 4.0, just reset the target branch to master, we will handle it on merge. Thank you.

@HeahDude I just checked, this bug is not in 4.0 branch, it was introduced during merge.

Nice, thanks again :)

Any ideas when this will be applied?

Thank you @CthulhuDen.


[Suggestion] Automatically provide a valid access token without server exchange

Use case
The proposal in README already is "The Embedded App SDK handles the communication between Discord and your iframed application", expectations would be to allow developers to create solo client side apps without the need to spin up a server only to exchange the code<>token.
As example, Twitch extensions automatically generate a valid user access token once they accept to share the scope, this allows to skip the server and build fully static deployed apps while still making requests to the discord API from the client.
For specific cases where you need to fetch external data, do special validations, you could reuse the token like Twitch, check integrity (using secret id) and allow/deny actions. (This being an optional flow)

Thank you for the suggestion and use case explanation. While we'd love to support implicit token grant flows we don't have a solid path forward for them at the moment. There is a possibility to expand for this use case, but it's not something we're ready to support at this time.


signal deploy go routine to stop when timeout happens

I tried to create a way to communicate to the deploy go routine that the timeout channel was signaled by using the channel itself but struggled with a decent implementation. So i just used the context which was only used for shared values and added a signal flag on it.

:+1:


Add E2E test for Statement

add e2e test for statement list page and detail page;
find a TiDB bug when testing search function on statement list page.

We can hold this PR for a moment, wait https://github.com/pingcap/tidb/pull/33052 to be merged and test again. Meanwhile the code review can happen. cc @shhdgit @baurine

Codecov Report

Merging #1196 (0965cd5) into master (f8c59bc) will decrease coverage by 7.08%.
The diff coverage is n/a.

:exclamation: Current head 0965cd5 differs from pull request most recent head d6ceb38. Consider uploading reports for the commit d6ceb38 to get more accurate results

@@            Coverage Diff             @@
##           master    #1196      +/-   ##
==========================================
- Coverage   29.43%   22.34%   -7.09%
==========================================
  Files         287      164     -123
  Lines       16945    14139    -2806
  Branches      648        0     -648
==========================================
- Hits         4987     3159    -1828
+ Misses      11727    10749     -978
  Partials      231      231

Flag
Coverage Δ

be_integration_test_latest
9.29% <ø> (ø)

be_integration_test_v4.0.1
9.27% <ø> (ø)

be_unit_test
24.07% <ø> (+0.01%)
:arrow_up:

e2e_test
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f8c59bc...d6ceb38. Read the comment docs.

Maybe we can update the e2e test script later so that the tiup process can be stopped.
The rest LGTM.

/merge


fix(public): place pdf assets in public/assets dir so it's available on /assets/filename.pdf

Description

Fixes broken icla, ccla, sgla pdf links on /contributions page
See: https://vite.dev/guide/assets#the-public-directory

Current Behavior
New Behavior

Screenshots

Related Issue

Pull Request Type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation changes

Checklist

[x] My code follows the code style of this project.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Does this introduce a breaking change?

[ ] Yes
[x] No

@aarontitus If you want any new assets (like pdfs) available on http://crisiscleanup.org/assets/<filename.pdf>, place them in public/assets directory of the repo.


[Bug]: Null cached_data values when rendering annotations on multi-series cases with OHIF3 viewer

Describe the Bug
Hello,
We are currently using the OHIF3 viewer and have encountered some unexpected behavior that we are trying to understand.
To reproduce the issue, we have observed that while attempting to add raw measurements using the provided OHIF functionality, the behavior becomes problematic when dealing with multi-series cases that contain annotations on series other than the first one. In such cases, the cached_data is failing to be calculated - the values are initiated to null value and remain with this value, resulting in rendering errors and buggy behavior - We have attached a video demonstrating this behavior for reference.
Upon further investigation, we found that the issue arises when Cornerstone attempts to call _calculateCachedStats, where it fails to retrieve the targetImage due to a null value returned by the this.getDefaultActor() function in the
`stackViewport` class.
// Tool file for example -<EMAIL_ADDRESS>const image = this.getTargetIdImage(targetId, renderingEngine)

//<EMAIL_ADDRESS>
getImageDataGPU() {
        const defaultActor = this.getDefaultActor();
        if (!defaultActor) {
            return;
        }
……
}

We managed to mitigate this behavior by adding an event listener to ANNOTATION_MODIFIED and setting the annotation as invalidated. This ensures that in the next render round(s), the cached_stats will be calculated, resolving the issue since getTargetIdImage is then no longer undefined - we can also see in the attached video the selecting annotations for rendering on different order effects the behavior, such that annotation that was selected first wasn’t rendered correctly, but when selected second it did managed to rendered.
As part of our research, we have noticed that for multi-series studies, we are missing FrameOfReferenceUID DICOM tags, could this be causing the problem?is it a must have data for adding raw annotations? Are there any other necessary data to provide that cause such an issue?
We will really appreciate your assistance :pray:
Steps to Reproduce

Open multi-series study while loading raw measurements on multi-series
Choose measurements on series other than the first one (upper series)
Observe that the chechdata is not calculated as expected

The current behavior
cached_data values are null when annotation is rendering
https://cornerstonejs.slack.com/files/U050A090MNH/F05M79PGTS4/multi_series.mov
The expected behavior
cached_data values are according to the annotation
OS
macOS Ventura 13.5
Node version
v20.2.0
Browser
Chrome Version 115.0.5790.114

This might have been fixed by PR #3696. @shirula please have a look.

@jbocce What do you mean? is it fixed? can you reproduce it anymore?

I think this is fixed by #3696 in master. @shirula if you consider it not fixed, please let us know or reopen the issue.


[BUG] my left click is was not working in games

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v.8.1
What problem did you encounter?
MY LEFT CLICK ISNT WORKING WHEN IM PLAYING I THOUGHT IT MIGHT BE MY PC BUT WHEN I LEFT CLICK OUTSIDE OF BLOXSTRAP IT WORKS
Bloxstrap Log
N/A

Client related issues are no longer accepted.


[BUG] Retry on sampled out telemetry is looping infinitely

Description/Screenshot
When we activate sampling in applicationInsights the SDK appears to retry over and over again on each logs that was sampled out. The ping calls never resolve, they stay pending infinitely.

Even though setting the sampling at 100% the track calls are returning a 200 response status code which do not trigger the retry logic, we should be able to reduce sampling without having this side effect on the client side

Steps to Reproduce

Reduce sampling to something below 100% on azure portal
Send telemetry with trackEvent function on client side

OS/Browser: Chrome 120.0.6099.109
SDK Version [e.g. 22]: 3.0.6
How you initialized the SDK:

Expected behavior
The sampled telemetry do not get resent
Additional context

This isn't specifically a sampling issue, I (think) it's related to this issue #2205, which we are currently publishing a fix for.
The npm package is already published and the CDN will be updated within the next hour.

Sorry, got distracted by performing the release steps for v3.0.7 on this

The ping calls never resolve, they stay pending infinitely.

This is a side effect of the browser "queuing" the requests, according to the specification, the browser is eventually supposed to send the batch events.
What is happening here is that during the page unload, we go into "send all batched events now" mode (so they are not lost), as part of this process we use either the sendBeacon API or when available the fetch() (with the keep-alive flag set). Previously (before these API's existed) we use to send the events as synchronous XMLHttpRequests (which are now banned) and this API blocked page navigation until all of the events are sent and responses received.
With the sendBeacon and fetch (with keep-alive) both of these API's have a maximum payload size limit of 64kb, so if (when) you have more than 64kb of serialized events (JSON encoded) we need to "split" the payload into multiple requests (at the least) and if the API's tell us that it could not accept the payload (even if we constructed a size < 64kb) then we go into a mode where we try and send as many events as possible (1 event per-request) until we are told that no more can be scheduled.
Why are there so many request?

Part of the answer is the above
The other part is that are part of some recent refactoring (in v3.0.3) we introduced an edge case bug where when this sequence occurs we went into a loop which caused events to be sent more than once 😢

We believe that we have now fix the introduced these edge cases and we have also introduced a new configuration that you can use to disable this behavior if your use-cases causes the frequent splitting / sending of multiple "pings" during page unload / navigation (which is also triggered by switching tabs)

This issue has been closed, because it was linked to the v3.0.7 release which is now fully deployed. If this version doesn't resolve your issue (or you just want more information), please feel free to continue commenting as if it's not fixed we can reopen and further investigate.

Thanks! The version 3.0.7 definitely fixed this issue. But we are still seeing some ping request never getting resolved (we waited over 10mins). We were stress testing our app with 50 000 logs to be sent over to appinsight using the trackEvent function. We are sending 1000 logs every 30 secs. Like you said, when we switch tabs the ping requests get sent, but some of them never resolve ?
Also, we set our sampling to 50% on our microsoft azure application insights, but every single log sent from the client browser with the trackEvent function are getting a 206 (Telemetry sampled out) ?

But we are still seeing some (around 25%) ping request never getting resolved (we waited over 10mins).

This is underlying browser functionality and I'm not sure exactly on "when" it would send out the requests, just that based on the specification once a browser "accepts" the request it is supposed to guarantee that it will deliver the request (I don't recall if there is a time limit involved as part of the spec). So either this is a browser bug (where it's not sending it) or just a UI issue where teh dev tools don't get updated ???

Also, we set our sampling to 50% on our microsoft azure application insights, but every single log sent from the client browser with the trackEvent function are getting a 206 (Telemetry sampled out)

Hmm, not sure why that would be as one would expect the sampling to be based on some form of randomness (not a direct part of my team), maybe they are using a combination of the source location / time or something. I'll ping some people to see if I can find an answer on why or whether this was just bad timing / luck.


[models] Rename Field.help_text → Field.description

Follow-up of #188
TODO

[ ] Migration: Field.help_text → Field.description
[ ] Migration: Item.help_text  → Item.description
[ ] Make sure that schema already serialized are still working1

Notes

Maybe implement a mapping, and raise a python warning to tell developers that the field won't be available soon

I see that the schema migration mechanism is ready in the codebase but... I think there's something missing like:

a way to easily run all the wanted migrations in order to upgrade the saved schemas from a version to the next one, and then eventually save them,
a documentation on how to do it,
integrate this migration mechanism in our internal (secret) projects, on-the-fly (would cost CPU, but would guarantee Blue/Green-like behaviour) or via a one-shot script (beware on how to keep it blue/green ?)


Project System: Remove dependency on vslang from AppDesigner property pages

From @davkean on December 1, 2015 20:33
We need to replace usages of VsLangProj.ProjectProperties from the AppDesigner property pages so that we they continue to run on the new project system.
Copied from original issue: dotnet/roslyn#7157

We are tracking property pages through individual issues.


Add option for appending V2 API to URL

Fixes #2

@dsplaisted , @rikoe
Please your thoughts on this change. Removing always api/v2/package would be a non-backwards-compatible change. (e.g. you need to change the publish URL when this is released).
The option is maybe not the best solution, but it's an improvement and makes the process more transparent.

I think this is at least an improvement. So merge. We can change this in the future.


Decline button not translated

The text for the button 'decline' isn't translated anymore on the cookie consent view. In the source it is translated.
1 week ago this still works.
insites.pdf

The code generator seems to set the property "dismiss" but in de code the property name is "deny" for that buttons' text.
Changing this fixed it for me.

The code generator seems to set the property "dismiss" but in de code the property name is "deny" for that buttons' text.

The property depends on the compliance type.

The 'dismiss' property is used for compliance type "Just tell users that we use cookies".
The 'deny' property is used for opt-in and opt-out.

On the website cookieconsent.insites.com/download/ you can customize the dismiss text, but not the deny text.
They might as well use the same property because there is no compliance type that use both of them.

This is coming in a PR currently in the dev branch on our next release.


Add Name Column to Own Addresses

After creating a few addresses it can be hard to track which is for what purpose.
Having a user editable column e.g. 'Name' would allow the user to have a human readable nickname to keep track and minimize the chance of accidentally using the wrong address for a receive or worse a send.
@vaklinov Are Git Issue Labels user editable? I was going to tag as enhancement.

The existing "Address book" functionality mostly fulfils this requirement: Having a user editable column e.g. 'Name'.
As an enhancement the wallet could be made more convenient - to be like Bitcoin-QT.
Git labels are editable... but edits rights are required.

Thank you vaklinov, I think you understood the ask but let me clarify in case.
Address book is good to having a human readable description for target addresses.
My ask is to have the same for wallet addresses (source) on the Own Address tab. Having a number of addresses it would be much simpler to keep them straight.

This is now implemented.


Map - maybe promote marker configuration "little filters" to "big filters" when changing to another variable

Related to #511 - because if "All other values" is switched off in categorical marker configurations, the marker config becomes a quite specific little filter.
When the user changes to another variable, they could be presented with the option to add their marker config (checkbox choices) as a big filter.  Perhaps only when "All other values" is disabled. Need to think carefully about UX.

When thinking about UX, do we even offer the option to create a big filter even if no value checkboxes have been clicked when "all other values" is switched off?  And the same for continuous variables?
For continuous variables, the big filter would have to be from [rangeMin TO rangeMax]
For categorical vars, the big filter would need to be for a) all values if marker config not customised, b) checked values if customised
What if there was already a big filter on that variable?


Add more detail to events listing on homepage

Refers to codeforgreenville/hackgreenville-com#58

Issue description
@allella

The screenshot here shows an example of the issue.
It's unclear which group is hosting the meetups and there's no way to see more details that clarify the issue.
Perhaps we can list the organization's name instead of the event name. Then, in the pop-up we have the event title, a link to the event homepage, or some such?
As far as I'm concerned, it's fine if people leave the website, so we don't need to worry making it easy for people to click away to the actual event.

Requirements

Some form of reference to hosting group in both initial listing and popup
Link in description to off-site event page

Options for showing hosting group

In events list, show host as event title (taken from above description)
In events list, show host under event name

@zach2825  I think this is only a couple changes, but would you like to review PRs?

@allella @zach2825 don't worry about review just yet. I was trying out creating a draft PR as a place of discussion while I work on this. The little bit I did yesterday was so I could both create this draft PR and confirm that I found the parts of the code I needed to work on.

I pulled issue 58's description to this PR for quicker reference. Also included an alternative idea that I'm currently playing with for the events listing.

@zach2825 what do you think about this so far?
In particular, is altering the "confirm" button's text and behavior alright if an event has a uri value in the DB, or is it preferable to let the "confirm" button behave normally and instead insert a link into the popup's HTML content?

Taking this out of draft status in case you guys want to merge it as is.

@JSn1nj4 this should now be showing at https://stage.hackgreenville.com
Can you check that things are working as expected?
We can pull it live upon confirmation.
Thanks

Looks like there is a 500 error on the calendar page.

The 500 error on the calendar page is unrelated. I'll check it out

Thanks. The error message in the logs is [previous exception] [object] (PDOException(code: 42S22): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'cancelled_at' in 'where clause' at /vendor/doctrine/dbal/lib/Doctri
ne/DBAL/Driver/PDOConnection.php:61)
[stacktrace]


Add method to update GlossaryTerm in Python SDK

Is your feature request related to a problem? Please describe.
When creating Glossaries from SDK, I'm using CreateGlossaryTermRequest  with create_glossary_term method, but it can only create new term and it will not update existing terms.
For example:
We have this as a first pass:
Parent A > Child 1
Parent B > Child 2
Then on second pass we want to change Child 2's parent to Parent A, then we get:
Parent A > Child 1
Parent A > Child 2
Parent B > Child 2
Child 2 is created as a new term, and not updated the existing term.
Describe the solution you'd like
We could have a simple method create_or_update_glosary_term using the API endpoint PUT /v1/glossaryTerms
As discussed on Slack: https://openmetadata.slack.com/archives/C02B6955S4S/p1677233629287539?thread_ts=1677228836.335459&cid=C02B6955S4S
Describe alternatives you've considered
Additional context

Thanks @schlameel , appreciate the effort in bringing all these methods to the sdk

This will be the third mixin that will use a protected method called _fetch_entity_if_exists which originated in patch_mixin.py. I am moving this method to a super class which the three classes using the method will inherit. I am proposing to put the super class into /ingestion/src/metadata/ingestion/ometa/mixins/patch_mixin_utils.py.
With #3809 I moved a bunch of PATCH mixin specific constants to ingestion/src/metadata/ingestion/ometa/patch.py. The constants were all strings and were grouped into enums.  Should these enums be moved to the same file? Some of the methods using the enums accept them as parameters so the user will need access to them if that sways the decision.
As a matter of process, does the team prefer one commit with a description that covers all changes or a commit for each file (or logical groups of files or similar)?

hi, sounds good, we can move these to patch_mixin_utils.
Regarding the commits, whatever works best for you. We will squash merge the PR, so as long as the name references the issue and the description works, we're good to go


Start oni on terminal

Is it possible to start oni inside an hyper terminal instead of opening a new electron window?
If I understand correctly how oni works it opens an electron frame, so why not reuse the one the terminal has already opened?

Interesting, I actually haven't used hyper but it looks like a cool project.
In theory, it should be doable - in practice, there might be some tricky aspects - there are things that we handle outside the BrowserWindow (like ensuring a single instance and communicating between Oni processes). In addition, there are potential issues with conflicting electron versions.
Personally, I'm more interested in the opposite scenario - hosting a terminal inside Neovim / Oni - but I'm open to PRs here if this is something that would be useful to others. Thanks for the suggestion!


Document the API a bit more

Some more clarity on the README, especially in the example around how shake vs stream are used.

Love it, thank you!

Thanks for merging!


Remove artifacts related to previously using TravisCI

TravisCI previously provided us with a badge related to build creation, as well as possibly running unit tests. It hasn't been hooked up properly for a while, and travis-ci.org is being shut down in favor of a paid travis-ci.com, so there's little point in keeping the old TravisCI artifacts around.

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[ ] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

This community post about a security leak on public repos linked to TravisCI led me to look into our connection to the site.
As part of this PR, we may want to try and delete all data/connection to cc_ng from the travis-ci.org website. Not sure what the process is like for that, but can look into it.

Looks good to me, @ctlong feel free to reach out about removing the connection on travis's end.
Merging


fix: Linux Powershell update

Add Import-Module Microsoft.PowerShell.Management -Force to fix the linux powershell update task in the pipeline.

Strange that we need this, is this a breaking change on the DevOps machine?

Indeed strange, since earlier this week we are getting this error:

Test-Path: /home/vsts/work/_temp/459fcf8a-2715-48a9-9f20-a0cb1acad4bc.ps1:4
Line |
4 |  if (!(Test-Path -LiteralPath variable:LASTEXITCODE)) {
|        ~~~~~~~~~
| The 'Test-Path' command was found in the module
| 'Microsoft.PowerShell.Management', but the module could not be loaded.
| For more information, run 'Import-Module
| Microsoft.PowerShell.Management'.

Haven't changed anything in the pipelines, but this PR should fix it 👍🏻


Design Meeting Notes, 5/21/2021

importsNotUsedAsValues: preserve-exact
https://github.com/microsoft/TypeScript/pull/44137

People expect import fs from "fs" to compile to import fs from "fs" in importsNotUsedAsValues: preserve

We don't - we just preserve the import itself.

Came up offhandedly.

The idea: new flag.

Same as importsNotUsedAsValues: error.

No, that's only an error if you never import a value.

The PR stops short of some of the work from last time.

Specifically, type modifiers on imports.

Would erase away those named imports.

How does that play with when you have a default?
import type fs, { yadda } from "yadda";

Ambiguous? Maybe disambiguate with type: fs
Not clear that that actually helps at all.

Requires es2015+ as a module target.

Doesn't make sense for if you're mixing CJS/ESM.
The "eval" thing doesn't quite work for our emit anyway.

How does tooling work with this?

We currently don't "promote" a type import to a value import.
A lot of people would prefer not to - sometimes people are using this mode defensively to prevent themselves from bundling more.

As long as we can improve in the future and have room.

This rule applies to both imports and exports
import { foo } from "./module.js";

foo();

interace Thing {}

export { Thing };

Getting a read for how these options interact is hard.

What is the mode that will allow you to be maximally compatible with compilers?

--isolatedModules
But that won't change things.

Meaningful use case: import means value import, import type means erased import.

But how do you deal with export { A }?

Do you need to write export type { A }?
Feels different.

Okay, harder case:
import Yadda from "yadda";
export { Yadda };

Okay, but one is local, we know exactly what it'll be.

Not consistent with "leave my imports and exports alone".

We seem to feel that a local export {} is exempt from elision rules because the constructs are all local.

If TypeScript was a greenfield project, this is probably what our default would be.

Would it be?
Would we use this ourselves?
Managing import vs import type is very annoying.

Not super big on giving an error in ES5.

Need to think through this a bit more, come up with a coherent write-up.

The addition of import type and export type really needs a companion flag that errors when using regular import or export with an interface or type. Something to automate the conversion process and provide enforcement.


[BUG] 8.5.5. broke forms with associations in Express Forms?

It seems that in 8.5.5. Express form validation falsely flags a not-required association when submitting the form without selecting an association.
Steps to reproduce:

create two Data Objects (e.g. Object A and Object B) with associations (e.g. many-to-many) to each other
add an entry to Object A (no form needed)
add a form to Object B that includes the association, which is not marked as required
try to add an entry to Object B and leave the association deselected
––> the entry isn't saved due to error "You must select a valid Object A"

We upgraded from 8.5.2 where it worked, but I don't know if this bug was introduced in 8.5.5. or even earlier.
All our objects have associations to each other so now we cannot create a single entry without selecting an association...

Yes, it definitely something changed. In my ExO I could enter empty/null value for associated on 8.5.2 and from 8.5.3/4 I can not.
I think on clean install with 8.5.5 should be fine but often brokes after updates.

Thanks for the comment. I tested now with a fresh 8.5.4 (using docker mlocati/docker5:8.5.4-full – no 8.5.5.) available and I could reproduce the error there, too. So it isn't an upgrade problem.

Digging deeper I noticed that this seems to have been fixed already in December 2019 in b5375bfa54a8d58d5a424784f7e127e9ab538b2a by @aembler – is there a specific reason it hasn't been included in 8.5.4/5?


Error when using sign in with server

When I try to sign in, I get this error:
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/.config/chromium/SingletonLock
I think this started when I checked "Keep me signed in", but I've tried clearing all Microsoft cookies and it doesn't get any better. Does anybody know how to help me with this?

Ooopsies, the library wasn't the problem. Sorry! Thanks!