Incorrect Decimal Handling for Spending Limit (e.g. for coins like USDT and USDC)

Note from @tschubotz:

This only happens for the initial case when enabling the module with the first spending limit.
The issue doesn't exist when the spending limit is already added to the Safe.
If you need non-18 decimal tokens on Rinkeby, check USDC, USDT or WBTC on https://app.compound.finance/ . They have faucet. Or deploy you own token.

Title/Description
While adding a spending limit for USDC and USDT we noticed the numbers were potentially far too large for those coins as they are only 6 decimals (but the values specified where clearly for an 18 decimal coin, e.g. Dai).
Environment
Browser: Chrome / Brave, Production.
Steps to reproduce

Attempt to add a spending limit for a 6 decimal coin like USDT or USDC
Check the allowanceAmount specified in the proposal under the amount
Check the that the value is correct, which it wont be (too many zeros)

Expected result

The Spending Limit handles coins that are not 18 decimals (i.e. USDT and USDC)

Obtained result

The spending limit is too large and set for 18 decimals.

Attempted but Failed Solve

We attempted to put in a smaller value for the spending limit (i.e. the correct 6 decimal equivalent in 18 decimal conversion), but the UI then rounded the value down to zero
We though this might be a rendering issue
The value was literally rounded down to zero on signing

@tschubotz once the spending limit module is activated, can i just do a separate setAllowance transaction with the transaction build for example, with the correct numbers and time by hand from my Safe?
This module:
0xCFbFaC74C26F8647cBDb8c5caf80BB5b32E43134
Method:
setAllowance
Then do USDT etc with the right values, will that work or will that clobber my last setAllowance with this delegate.
Note, my delegate is the same in this new case as the one previously activated.
Will the UI properly pick this up if I do it by hand?

@SilentCicero Seems I wasn't paying close enough attention last night and I got confused with token decimals on Rinkeby, apologies. I'm actually not able to reproduce you issue.
Here's what I do on mainnet

My Safe is https://gnosis-safe.io/app/#/safes/0xA063Cb7CFd8E57c30c788A0572CBbf2129ae56B6/. It has a threshold of 3.
It holds a small amount of USDT, so 6 decimals https://etherscan.io/token/0xdac17f958d2ee523a2206206994597c13d831ec7
I now set a spending limit of 0.01 USDT for an address

After signing, the UI show the correct amount of USDT on the tx list. (allowanceAmount of 10000 == 0.01 USDT)

Of course, that's only the UI, so here's the payload that my Metamask prompted me to sign:

Payload
```
0x8d80ff0a0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000017200cfbfac74c26f8647cbdb8c5caf80bb5b32e4313400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024e71bdf41000000000000000000000000a063cb7cfd8e57c30c788a0572cbbf2129ae56b600cfbfac74c26f8647cbdb8c5caf80bb5b32e43134000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a4beaeb388000000000000000000000000a063cb7cfd8e57c30c788a0572cbbf2129ae56b6000000000000000000000000dac17f958d2ee523a2206206994597c13d831ec70000000000000000000000000000000000000000000000000000000000002710000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
```

Examining this with 4bytes and https://rimeissner.dev/transaction-decoder/ shows me that this is a multisend, where the first action calls addDelegate and the second one setAllowance (same like visible on the tx list in the Safe interface).
When further decoding the payload of the 2nd action, I can confirm the same params with correct USDT value.

Could you please elaborate on the steps you are taking to get the wrong spending limit params, ideally with some screenshots?

Closing due to inactivity. Once more information is available it can be reopened


Added Hackerrank Python Problems

Description
This pull request introduces a new Chrome extension designed to provide quick and easy access to HackerRank Python problems. The extension features a welcome page with a typewriter effect that greets users and introduces them to the HackerRank Python problems. After the greeting, users can click a button to navigate directly to the HackerRank Python problems page. This extension aims to streamline the coding practice process by offering a convenient way to access Python problems on HackerRank.
Fixes:  #966

Type of change

[X ] New feature (non-breaking change which adds functionality)

Checklist:

[ X] I have made this from my own
[ ] I have taken help from some online resourses
[ X] My code follows the style guidelines of this project
[ X] I have performed a self-review of my own code
[ X] I have commented my code, particularly in hard-to-understand areas
[ X] I have made corresponding changes to the documentation
[ X] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

I have contributing upon Gsooc24

@Sulagna-Dutta-Roy please check i have added new extension


Automated tests don’t cover Python 3

#1674 broke snapshot downloading on machines where Python 3 provides python, but this was not caught by the integration bots.

It'd be great to cover cases like this, but there's no way that we can add a bot for all possible configurations, and this isn't exactly a critical part of the build system so I'm going to close this. We'll certainly always accept packages to work with python 3, however!


Can't upload sqlite3 file onto prod server, but on devel?

Difference due to different usage! No real diff.


bug: {context: 'client'} '{"code":-32602,"message":"May not specify default MetaMask chain."}'

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.4.12
Current Behavior
I get this error trying to send a transaction on sepolia in metamask
Expected Behavior

Steps To Reproduce

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?

https://docs.metamask.io/wallet/reference/wallet_addethereumchain/ i dont understand that here

if i remove the chainId from prepareSendTransaction it works, but i want to use sepolia and the transactoin is on mainnet ...

For some reason now it works. Not sure if metamask published a fix


Nuxt 3.8.1 breaks Subresource Integrity

No SRI attributes in SSG mode
Version
nuxt-security:  1.0.0-rc.4
nuxt:  ^3.8.1
Reproduction Link

https://stackblitz.com/edit/nuxt-starter-3x8r6t?file=README.md
Steps to reproduce
Open Stackblitz repro with DevTools, inspect Response
What is Expected?
<head> elements should contain integrity attributes
What is actually happening?
<head> elements do not contain integrity attributes
Issue description
The issue only appears in SSG mode. SSR mode is not affected.
The Stackblitz repro installs in SSG mode to illustrate the issue.

You can modify the nuxt version to 3.8.0 and the issue will disappear

Origin of issue
Nuxt 3.8.1 modified the behavior of the nitro:build:public-assets hook.

Before 3.8.1, this hook was called before pre-rendering pages
After 3.8.1, this hook is now called after pre-rendering pages

Responsible commit was https://github.com/nuxt/nuxt/commit/a4b333bca2a729b2629d45212b12eb8e046f47be#diff-85b4fe47ac4284e88552626029d5147793563b4dcdab205cd8dc6afb190222aaR462
Resolution
PR #304 will fix

@vejja once again, thank you si much for both finding and fixing an issue! 💚


Icon fonts fail to load

Fonts from d2zywx0xwifbv5.cloudfront.net are blocked by the same-origin policy in Firefox 47.0.

I have the same problem, screenshot:

I spent a good portion of the day yesterday working on this. I thought I had it fixed. It works on all browsers on multiple devices for me now. Maybe try clearing your cache?

Clearing the cache doesn't help. I tried a different system too -- it's the same.

Same for me ,clearing cache has no effect. The issue is: Font from origin 'https://d2zywx0xwifbv5.cloudfront.net' has been blocked from loading by Cross-Origin Resource Sharing policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Origin 'https://www.codewars.com' is therefore not allowed access.

Yeah its the oddest thing. I fixed that issue yesterday. Was able to consistently reproduce it, deployed a fix, it immediately went away. But somehow different sets of old problems that I thought I fixed are showing up for different people on different networks. Its kind of maddening but I'm continuing to look into the issues.

Fixed for me now

Thanks for letting me know. I didnt change anything yet. Let me know if they go away again.

Works for me too. If I remember correctly, Access-Control-Allow-Origin was *, *, now it is *.

Yes cloud front cached the resources. I added nginx into the mix and there was some old heroku based code that added * from within rails, so both were adding their own header. I removed the code from rails and switched nginx to server assets statically without rails. Once deployed the changes took affect immediately for me but I guess they stayed cached on different edge servers.


[type: refactor] support octet-stream context-type.

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2858 (f33fb17) into master (8b06813) will decrease coverage by 0.45%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #2858      +/-   ##
============================================
- Coverage     60.16%   59.71%   -0.46%
+ Complexity     4463     4421      -42
============================================
  Files           691      691
  Lines         19924    19922       -2
  Branches       1775     1774       -1
============================================
- Hits          11988    11897      -91
- Misses         6927     7020      +93
+ Partials       1009     1005       -4

Impacted Files
Coverage Δ

...ugin/response/strategy/WebClientMessageWriter.java
80.85% <100.00%> (+0.41%)
:arrow_up:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
68.75% <0.00%> (-31.25%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
52.12% <0.00%> (-20.22%)
:arrow_down:

...henyu/admin/service/impl/UpstreamCheckService.java
42.85% <0.00%> (-12.70%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...apache/shenyu/admin/utils/ShenyuDictH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...ache/shenyu/admin/utils/PluginHandleH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

.../plugin/grpc/loadbalance/AbstractLoadBalancer.java
70.32% <0.00%> (-9.02%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
70.37% <0.00%> (-7.41%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

... and 27 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 8b06813...f33fb17. Read the comment docs.


Test: Use same QUnit version in CI as on website

Follows-up c9b4b63fd08847281260205b995ae644f6f2f4d2 and 13f71bc9711b3617dd0fd5f1f085655df8505cf8.
Contrary to the commit message, it actually restored the older QUnit 2.6, and not the newer QUnit 2.10 version from package.json.
The oldest Node.js LTS is currently Node 12.
The latest QUnit 2.18 supports Node 10+.
This repo currently has a Node 8 CI job.
While at it, update both to 2.10.1, the last version to support Node 8 (changelog), and pin it to avoid "npm install" from expanding it and saving it to the lock file which Node 8 would see. Hopefully also avoiding e.g. using a newer method which would then fail on the website version later.

Coverage remained the same at 95.217% when pulling 7312895ae1dce8e87c12600f97190a87aaec8221 on Krinkle:same-version into 596a7f2d63bbd8a55d07ee18b804619d727e779f on jashkenas:master.


Log Unauthorized requests

Fixes https://github.com/influxdb/influxdb/issues/1444

+1 on green build.

Why move Authorize func into the server?  ExecuteQuery could log the error returned from Authorize.
My personal preference is for libraries never to log but everyone may not agree on that one.

@dgnorton -- I tend to agree, but it seems to me that we're not dealing with libraries here, so much as "packages".  Also, if we don't have any logging in our packages, we'll have no logging at all.
Let me know if I am missing your point.

@otoolep  It's more than just a word.  In a Go, anything in package main is an app and everything else compiles into a library.  I'm saying only package main should log.  I have a long list of reasons why libraries shouldn't log.  :)

Libraries don't know where or how they're going to be used.  In my app, maybe I only want to use a specific logging framework or logging format.  That gets messed up if a library I'm using has its own logging.

Even if I own all the apps and libraries, let's say I decide the format needs to change or I want to swap out the logging frame work, now I have to go through thousands of lines of logging code.

Thousands of lines of logging code - ugh.  Who wants to look at that or maintain it.  It's cognitive load that doesn't need to be there.

Apps that don't want to log still pay the cost

Logging can change the behavior of the code  (e.g., somebody decides the logging needs to use synchronization when writing to stdout, etc.).

Logging at app level keeps the logging in one spot.  The rest of the code doesn't bloat and slow down with logging over time.  The logging format is uniform.  You don't have to worry about adding logging calls every time you check an error or bubble it up...logging just magically works because you handled errors.  It's rainbows and unicorns all the way up.

I think the comments around logging make sense.  The are outside of the scope of this PR though.  We should open a new issue that discusses logging as a larger concern and decide how we want to proceed from there.  For now, I'm merging this and can revisit once the larger issues have been settled.


Don't show github URL for Bitbucket packages

push tags to git@bitbucket.org:/.git

[new tag]         v1.1.0 -> v1.1.0
✔  to create a release, go to https://github.com//

Fixed


python312Packages.chromadb: 0.5.7 -> 0.5.11

Diff: https://github.com/chroma-core/chroma/compare/refs/tags/0.5.7...0.5.11
Changelog: https://github.com/chroma-core/chroma/releases/tag/0.5.11
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

4 packages marked as broken and skipped:

python311Packages.llama-index
python311Packages.llama-index.dist
python311Packages.private-gpt
python311Packages.private-gpt.dist

6 packages failed to build:

open-webui
open-webui.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist

8 packages built:

python311Packages.chromadb
python311Packages.chromadb.dist
python311Packages.llama-index-cli
python311Packages.llama-index-cli.dist
python311Packages.llama-index-vector-stores-chroma
python311Packages.llama-index-vector-stores-chroma.dist
python312Packages.chromadb
python312Packages.chromadb.dist

Looks like langchain-chroma needs an update too.

Result of nixpkgs-review pr 345372 run on aarch64-darwin 1

10 packages marked as broken and skipped:

open-webui
open-webui.dist
python311Packages.llama-index
python311Packages.llama-index-cli
python311Packages.llama-index-cli.dist
python311Packages.llama-index-vector-stores-chroma
python311Packages.llama-index-vector-stores-chroma.dist
python311Packages.llama-index.dist
python311Packages.private-gpt
python311Packages.private-gpt.dist

8 packages failed to build:

python311Packages.chromadb
python311Packages.chromadb.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.chromadb
python312Packages.chromadb.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist

I'll push out the needed langchain updates this afternoon.
You also have a flaky test at chromadb/test/proto/test_utils.py::test_retry_interceptor

langchain-chroma is current at 0.1.4 (PR #341921)

You need #345803 and then you'll pass all tests on Darwin.

Uff, more failing tests
error: builder for '/nix/store/fvad1rlcb3sxsx98l798ni2jjrazkshz-python3.11-langchain-chroma-0.1.4.drv' failed with exit code 1;
       last 10 log lines:
       > tests/integration_tests/test_vectorstores.py:257: ValueError
       > ============================= slowest 5 durations ==============================
       > 0.67s call     tests/integration_tests/test_vectorstores.py::test_chroma_with_persistence
       > 0.11s call     tests/integration_tests/test_vectorstores.py::test_chroma
       > 0.01s call     tests/integration_tests/test_vectorstores.py::test_chroma_update_document
       > 0.01s call     tests/integration_tests/test_vectorstores.py::test_chroma_search_filter
       > 0.01s call     tests/integration_tests/test_vectorstores.py::test_chroma_async
       > =========================== short test summary info ============================
       > FAILED tests/integration_tests/test_vectorstores.py::test_chroma_update_document - ValueError: The truth value of an array with more than one element is ambig...
       > =================== 1 failed, 26 passed, 3 skipped in 1.55s ====================

Uff, more failing tests

This error is a side-effect of the async test not being called properly (fixed by the PR).
Rebase onto master and you should be fine.

Turns out that the langchain repo's integration tests fail the same way outside nixos:
        # Assert that the updated document is returned by the search
        assert output == [Document(page_content=updated_content, metadata={"page": "0"})]

>       assert new_embedding == embedding.embed_documents([updated_content])[0]
E       ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

tests/integration_tests/test_vectorstores.py:257: ValueError
======================================================================= warnings summary ========================================================================
tests/integration_tests/test_vectorstores.py::test_chroma_async
  /Users/seclark/development/langchain/.devenv/state/venv/lib/python3.11/site-packages/_pytest/python.py:148: PytestUnhandledCoroutineWarning: async def functions are not natively supported and have been skipped.
  You need to install a suitable plugin for your async framework, for example:
    - anyio
    - pytest-asyncio
    - pytest-tornasync
    - pytest-trio
    - pytest-twisted
    warnings.warn(PytestUnhandledCoroutineWarning(msg.format(nodeid)))

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================================== slowest 5 durations ======================================================================
0.07s call     tests/integration_tests/test_vectorstores.py::test_chroma
0.03s call     tests/integration_tests/test_vectorstores.py::test_chroma_with_persistence
0.01s call     tests/integration_tests/test_vectorstores.py::test_chroma_update_document
0.01s call     tests/integration_tests/test_vectorstores.py::test_reset_collection
0.01s call     tests/integration_tests/test_vectorstores.py::test_chroma_search_filter_with_scores
==================================================================== short test summary info ====================================================================
FAILED tests/integration_tests/test_vectorstores.py::test_chroma_update_document - ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
====================================================== 1 failed, 24 passed, 4 skipped, 1 warning in 0.78s =======================================================

I'm willing to call test_chroma_update_document a bad test and plan on disabling it.

Result of nixpkgs-review pr 345372 run on aarch64-darwin 1

10 packages marked as broken and skipped:

open-webui
open-webui.dist
python311Packages.llama-index
python311Packages.llama-index-cli
python311Packages.llama-index-cli.dist
python311Packages.llama-index-vector-stores-chroma
python311Packages.llama-index-vector-stores-chroma.dist
python311Packages.llama-index.dist
python311Packages.private-gpt
python311Packages.private-gpt.dist

8 packages built:

python311Packages.chromadb
python311Packages.chromadb.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.chromadb
python312Packages.chromadb.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist

Looks like you are good to merge.

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

4 packages marked as broken and skipped:

python311Packages.llama-index
python311Packages.llama-index.dist
python311Packages.private-gpt
python311Packages.private-gpt.dist

14 packages built:

open-webui
open-webui.dist
python311Packages.chromadb
python311Packages.chromadb.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.llama-index-cli
python311Packages.llama-index-cli.dist
python311Packages.llama-index-vector-stores-chroma
python311Packages.llama-index-vector-stores-chroma.dist
python312Packages.chromadb
python312Packages.chromadb.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist


Add IoT Edge extension into Azure Pack

@chrisdias Please help review and merge. Thanks.

thanks!


Searching in helpdesk isn't working correctly

IOS, app version 3.7.3 - 172.
When you try to search for anything in the helpdesk in the support page, it shows u another question or nothing.
and page freezes at the end, you can't click anything only option is to go back or change page from menu.
https://github.com/threefoldtech/threefold_connect/assets/109473873/ff18144d-66af-4ed3-b0c9-2eb2ac0da8f6

Works normally.

Verified on Android 14,
Threefold-Connect: 4.0.0-184
APK:12-12-2024
Help desk searching works as expected.

https://github.com/user-attachments/assets/658ac428-45ae-42ea-a4fe-836433ad601e
Related Link:

https://app.testlodge.com/a/26076/projects/40893/suites/206114?expand_section=407475#case_4045878


🐛 Bug Report: TechDocs does not work for custom catalog processor

📜 Description
In implementing a custom catalog processor on the new backend installation, everything is working as expected except for Techdocs. The error being returned from the techdocs plugin is:
techdocs info Unable to get metadata for 'component:default/actions' with error InputError: Unable to resolve location type switchboard-catalog-processor

Our entire backend index.ts file contents:
import {createBackend} from '@backstage/backend-defaults';
import {customAuthPlugin} from "./plugins/auth";
import {catalogModuleSwitchboardCatalogProcessor} from "./plugins/catalog";

const backend = createBackend();
backend.add(import('@backstage/plugin-app-backend/alpha'));
backend.add(import('@backstage/plugin-catalog-backend/alpha'));
backend.add(catalogModuleSwitchboardCatalogProcessor);
backend.add(
  import('@backstage/plugin-catalog-backend-module-scaffolder-entity-model'),
);
backend.add(customAuthPlugin);

backend.add(import('@backstage/plugin-proxy-backend/alpha'));
backend.add(import('@backstage/plugin-auth-backend'));
backend.add(import('@backstage/plugin-search-backend/alpha'));
backend.add(import('@backstage/plugin-search-backend-module-catalog/alpha'));
backend.add(import('@backstage/plugin-search-backend-module-techdocs/alpha'));
backend.add(import('@backstage/plugin-techdocs-backend/alpha'));
backend.start();

The catalog section of our app-config.yaml:
catalog:
  readonly: true
  locations:
    - type: switchboard-catalog-processor
      target: ${CATALOG_PROCESSOR_HOST}/catalog

We also upgraded our entire backstage installation to the very latest.
👍 Expected behavior
I expected the most recent version of the backend Techdocs plugin to respect the custom catalog processor just like every other plugin is doing.
👎 Actual Behavior with Screenshots
Techdocs fails to load.

👟 Reproduction steps

Upgrade to latest backstage installation
Implement custom catalog processor
Use Techdocs

📃 Provide the context for the Bug.

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

What could be the reason?  I got similar issue.
After add msgraph processor in catalog, techdoc not working.

Hi @backstage/techdocs-maintainers could you please take a look?

Hey, I think what @camilaibs suggested in the discord thread about creating a custom preparer is the right path. Since you're using a custom location type and the default techdocs preparer, the preparer is unable to discern where your source files are and won't make any assumptions either.

@PeaWarrior is there an example on how to do that? That's what I tried to do but there is no documentation on doing that and it's not very intuitive on how to do that.

Also, it's worth noting all of the other plugins are operating just fine. I would expect the TechDocs plugin to also function properly with the new location type because it is defined in app-config.yaml catalog section. I have to assume that's why all the other plugins are respecting the new location type.

Hi @jrkt, in conversation with @Rugvip he explained to me that TechDocs locations aren't the same as catalog locations. So the issue here is that the TechDocs dir: type no longer works because it can't resolve relative to a custom catalog location type. You need to have a processor that adds a TechDocs annotation with an absolute url: location instead.
We think that the best solution is to make sure that https://backstage.io/docs/features/software-catalog/well-known-annotations/#backstageiosource-location is populated for the generated entities. Otherwise would have to install a custom dir preparer that knows to resolve to a custom catalog location type instead of using the default one.

@camilaibs how does that annotation need to look for this to work? It looks like it's just a URL. It doesn't specify anything about the new location type.

The interesting thing is that the search shows techdocs in the search results with the little summary which shows some of the actual techdocs content. But, if I click on that search result, I get the error described in this issue.

@camilaibs how does that annotation need to look for this to work? It looks like it's just a URL. It doesn't specify anything about the new location type.

The value of the annotation should an absolute url location,

See more examples here: https://github.com/search?q=backstage.io%2Fsource-location+language%3AYAML&type=code&p=1&l=YAML

@camilaibs is that going to be a problem that the URL points to a private GitHub repository? And now that I'm using a custom processor, I have completely removed the GitHub integration.

You'll want to keep that GitHub integration around just for the sake of being able to resolve URLs and potentially read content or take other actions. That URL in the source-location annotation should then point to the repo as usual. You'll want to set this up even if you don't read TechDocs content directly from the GitHub repo so that edit and issue links work correctly.

@Rugvip if I don't use issue links, when would that GitHub integration ever be used? A normal url parser can resolve GitHub URLs just fine. I would prefer to keep the integration out of it. I don't think we actually need it.

In fact, I was able to get techdocs working by simply setting the backstage.io/source-location annotation to the host name of our custom processor API.


ng build --production does not fully uglify js classes

🐞 Bug report
Command (mark with an x)

ng build --configuration production

[ ] new
[ x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
No

Same, minification/uglification still appears to be incomplete or is this by design and intentional?
Description
When creating a production angular build the output javascript bundles seem to be minified and uglified, but not to the extent that I was expecting.
When looking into the outputted files in the dist folder, parts of the file are indeed minified and uglified. Other parts of the file are in plain javascript and expose quite a lot about the application.
I have attached an example image whereby one can clearly read the app component in the main bundle after being minified and uglified. I would have expected this code to have been obfuscated too.
🔬 Minimal Reproduction
ng new repro-app
Ensure optimization is enabled on angular json for production
ng build --configuration production
Review the outputted bundles and see that for most angular components, the source code is human readable
🌍 Your Environment
node v18
npm v8

This is working as intended.
Mangling properties of objects and classes is considered dangerous and in most cases it is a code-breaking option unless used in a controlled environment example when not using 3rd party libraries.
It is also important to point out that the intended goal of mangling is to reduce the file size and not to increase the security of the application. If there is logic that shouldn't be accessible by the client then it would be better to place it to an API.


Error with command: npm install @primer/react

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR!      C:\Users\Admin\AppData\Local\npm-cache_logs\2022-01-31T13_58_03_031Z-debug.log

Closing for now. Feel free to reopen if you're still having issues.


Create a kitchensink

#Add a kitchensink template to showcase nuCSS components.

[x] HTML Skeleton
[ ] Grid example

I will update this issue when new components are available.

I would like to work on the grid example for the kitchensink. Is that ok for you?

Yeah sure go ahead. It's not quite ready yet but the architecture won't change that much at this point.
Thanks for your help.

Thanks you for your help on this project. Sorry it was so long for me to approve this.

Should I also style the grid? If yes, where to put the styles for the kitchensink?

The theming step will come later. I've started working on these steps, unfortunately I won't have much time in the next to weeks to make any progress in this matter.
In the meantime, if you're still interested in working on this project, you can post your ideas right here -> #34


About version

Excuse me, is there a quic 47 version for draft 19?

There's no QUIC 47 in draft 19.

There's no QUIC 47 in draft 19.


Consider adding hardware optimization levels

x86_64 has a bunch of possible features but these appear usually together in shipped CPUs. So for convenience consider adding something like this:
https://www.phoronix.com/scan.php?page=news_item&px=LLVM-Clang-12-Microarch-Levels
Where the levels are:

x86-64: CMOV, CMPXCHG8B, FPU, FXSR, MMX, FXSR, SCE, SSE, SSE2
x86-64-v2: (close to Nehalem) CMPXCHG16B, LAHF-SAHF, POPCNT, SSE3, SSE4.1, SSE4.2, SSSE3
x86-64-v3: (close to Haswell) AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE, XSAVE
x86-64-v4: AVX512F, AVX512BW, AVX512CD, AVX512DQ, AVX512VL

This would make picking a reasonable set of features much easier. Ideally this would also exist for ARM and other architectures and there would be a catch all annotation that would just compile to all levels that apply to the architecture. Something like #[multiversion-broad] that would just use all these reasonable levels in whatever architecture is being compiled for.

Sorry it's been a while--this has been added to master.
The new API actually allows selecting any target CPU, such as "x86_64/skylake".  Currently, x86-64-v3 doesn't work because std::arch lacks detection of MOVBE.  I've opened a PR to add that in https://github.com/rust-lang/stdarch/pull/1356.

Another new feature has been added that allows you to specify #[multiversion(targets = "simd)], which automatically selects from all SIMD instruction sets.  On x86/x86-64 this corresponds to the microarchitecture levels.

Seems like the lahfsahf target feature also causes issues with this; it's present on v2-v4. It requires a Nightly feature to be enabled (lahfsahf_target_feature), and even then it seems that is_x86_feature_detected doesn't support runtime detection for it and causes a compile error when attempting to use v2-v4 of the x86-64 levels, rendering them entirely unusable.
targets = "simd" is a handy shortcut, but currently doesn't support AVX-512 (requires a Nightly feature, but is functional), and doesn't seem to be customizable at all either. It also excludes other non-SIMD features provided by these levels (e.g. BMI1, potentially useful for tzcnt).


Unabstract executor.create_monitoring_info

This method makes sense for BlockProviderExecutors, where it is used by the JobStatusPoller. It does not make sense for ParslExecutors in general and is not otherwise used. So remove from the ParslExecutor base class, which removes the dependency of parsl.executors.base on parsl.jobs.*, a cleaner separation of concerns.
This method is implemented in HighThroughputExecutor, but the information generated only uses BlockProviderExecutor information and would make sense for other BlockProviderExecutors (Work Queue, Task Vine and the erstwhile IPP and Extreme Scale executors). Using this implementation has been prototyped in the desc branch of parsl since 2021. So move that implementation out of out of HighThroughputExecutor and into
BlockProviderExecutor.
This should not change any behaviour when using HighThroughputExecutor. When using Work Queue or Task Vine, this change will bring block monitoring support to those executors. As noted above, this has been used successfully with Work Queue since 2021 in the desc branch. This PR modifies the basic monitoring test to test against those executors in addition to the HighThroughputExecutor.
This PR modifies the type annotations of create_monitoring_info to type check properly - the previous htex implementation was not type-checked. The return type is modified to a sequence, because List in invariant on its parameter type, which is incompatible with adding Dict[str, Any] to it.
Changed Behaviour
see main description
Type of change

New feature

tests are failing - see #3339 for environment fix


Fixing timeout handling.

Passing the timeout setting through another instance of BlockingSlackApiClient.

Looks good to me.....merged!


fix: document path openrpc json sem rel plugin

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

1.1.3
GitHub release
1.1.3

Your semantic-release bot :package::rocket:


:lipstick: updating component list

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>Proposed Changes

adding a more complete list of offered components

/lgtm


Hydra-in-a-Box - Final Project Update

Hydra-in-a-Box - Final Project Update
Suggested by: Hannah Frost
Presenter: Hannah FrostMichael J. Giarlo
Format: Presentation
Audience: All

i am not familiar with the particulars of hydra-in-a-box, but i assume this project has been very influential on the design of hyrax and therefore would be useful to just about everyone.

added #159 as a possible related topic

+1

+1

Presentation description:
A presentation that reflects on the learnings and accomplishments of the Hydra-in-a-Box project, the 30-month effort by Stanford Libraries, DuraSpace, and the Digital Public Library of America with funding from the IMLS.


Problem with ListStatus

I'm using the SDK via the NuGet package, and I'm running into a problem with ListStatus.  What I want to do is pull the statuses for a list of Envelope Ids, which I'm trying to do like this:
var apiInstance = new EnvelopesApi();
var envelopeIdsRequest = new EnvelopeIdsRequest();
List envelopeIds = new List();
envelopeIds.Add("envelope-id-1");
envelopeIds.Add("envelope-id-2");
envelopeIdsRequest.EnvelopeIds = envelopeIds;
EnvelopesInformation result = apiInstance.ListStatus(accountId, envelopeIdsRequest);
Running this generates the request that I would expect from having looked at the API documentation https://docs.docusign.com/esign/restapi/Envelopes/Envelopes/listStatus/:
**PUT https://demo.docusign.net/restapi/v2/accounts/account-id/envelopes/status HTTP/1.1
X-DocuSign-SDK: C#
X-DocuSign-Authentication: {"Username":"my_username", "Password":"my_password", "IntegratorKey":"my_integrator_key"}
Accept: application/json
User-Agent: Swagger-Codegen/2.1.0/csharp
Content-Type: application/json
Host: demo.docusign.net
Content-Length: 193
Accept-Encoding: gzip, deflate
{"envelopeIds":["envelope-id-1","envelope-id-2"]}**
This request returns an error: "The request contained at least one invalid parameter. Query parameter 'from_date' must be set to a valid DateTime, or 'envelope_ids' or 'transaction_ids' must be specified."
If I edit the request like this, it works, even though this doesn't match the documentation, and isn't what's generated by the SDK:
PUT https://demo.docusign.net/restapi/v2/accounts/account-id/envelopes/status?envelope_ids=envelope-id-1,envelope-id-2 HTTP/1.1
X-DocuSign-Authentication: {"Username":"my-username", "Password":"my-password", "IntegratorKey":"my-integrator-key"}
Accept: application/json
User-Agent: Swagger-Codegen/2.1.0/csharp
Content-Type: application/json
Host: demo.docusign.net
Content-Length: 193
Accept-Encoding: gzip, deflate
{"envelopeIds":[]}
And yes, the request body containing the empty list of envelope Ids seems to be required!
So, what is going on?  Am I not using the SDK correctly, or missing something from the API documentation?  Or what?

The Rest spec and API do not agree on this call. The ListStatusWithHttpInfo method needs to be modified to add teh query paramaters as follows to work:
if (envelopeIdsRequest != null && envelopeIdsRequest.GetType() != typeof(byte[]))
{
localVarPostBody = Configuration.ApiClient.Serialize(envelopeIdsRequest); // http body (model) parameter
localVarQueryParams.Add("envelope_ids", Configuration.ApiClient.ParameterToString(envelopeIdsRequest.EnvelopeIds));//JM change for API
}
else
{
localVarPostBody = envelopeIdsRequest; // byte array
}

This is still an issue and has been open for almost a year, any reason why it hasn't been assigned yet.
I don't see a way of using the SDK in order to return just the envelope ID I want.

Closing this. We have a solution mentioned #196, will update that with our progress.


Added the ability to specify a ref to a schema in the Property attribute

Q
A

Branch?
develop

Bug fix?
no

New feature?
yes

Deprecations?
no

Tickets
Feature #16

License
MIT

Doc PR
N/A

Thanks for your contribution ! 🙏


implement support for multiple include/exclude glob attributes

Hi!
This PR adds a new feature - includes-excludes. With this feature enabled, we can specify multiple attributes with glob values, like #[include = "*.txt"] and #[exclude = "tests/*"], for a fine-grained control over files embedded by rust-embed.
Example:
#[derive(RustEmbed)]
#[folder = "examples/public/"]
#[include = "*.html"]
#[include = "images/*"]
#[exclude = "*.txt"]
struct Asset;

It is related to #96

Thanks for the feedback!
I've implemented suggested changes and addressed clippy warnings.

Thanks for implementing this!

LGTM. Thanks @mbme.


Unable to install Python's jq package via Poetry

Describe the bug
Python's jq library compiles Onigumura internally, which causes devenv to blow up during installation of Python dependencies.
To reproduce
Please see jcf/nix-poetry-langchain for a reproducible example.
I'd like to be able to install any Python dependency in a reproducible way, ideally via Poetry. I tried layering poetry2nix on top to no avail.
See also:

jq override in poetry2nix
Discord thread

Version
$ devenv version
devenv: 0.6.3

Looks like this one depends on #507

@domenkozar I've tried poetry-rewrite to see if I can build Python's jq now; same error as before.
I'm also having some trouble building pyarrow. Would you recommend keeping Python and Nix/devenv separate until the awesome work over in #745 is merged?
Details
Package operations: 1 install, 0 updates, 0 removals

  • Installing pyarrow (13.0.0): Failed

  ChefBuildError

  Backend subprocess exited when trying to invoke build_wheel

  <string>:34: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section'
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-11.0-arm64-cpython-312
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/orc.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/conftest.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_generated_version.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/benchmark.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_compute_docstrings.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/ipc.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/util.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/flight.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/cffi.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/substrait.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/filesystem.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/types.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/dataset.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/cuda.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/feather.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/pandas_compat.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/fs.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/acero.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/csv.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/jvm.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/hdfs.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/json.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/compute.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_tensor.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_ipc.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/conftest.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_convert_builtin.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_misc.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/arrow_16597.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_acero.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_gandiva.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/strategies.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_adhoc_memory_leak.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/arrow_7980.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/util.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_orc.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_table.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_array.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_deprecations.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_io.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_util.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_cuda_numba_interop.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_cpp_internals.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_cffi.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_schema.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_jvm.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_fs.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_udf.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_filesystem.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/pandas_threaded_import.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/pandas_examples.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_cython.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_sparse_tensor.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_dataset.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_builder.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_cuda.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_extension_type.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_feather.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_pandas.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_memory.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_exec_plan.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_flight.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/read_record_batch.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_json.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_compute.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_hdfs.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_strategies.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_csv.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_scalars.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_gdb.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_types.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/test_substrait.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  copying pyarrow/interchange/from_dataframe.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  copying pyarrow/interchange/dataframe.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  copying pyarrow/interchange/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  copying pyarrow/interchange/buffer.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  copying pyarrow/interchange/column.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/interchange
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/vendored
  copying pyarrow/vendored/version.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/vendored
  copying pyarrow/vendored/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/vendored
  copying pyarrow/vendored/docscrape.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/vendored
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/parquet
  copying pyarrow/parquet/encryption.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/parquet
  copying pyarrow/parquet/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/parquet
  copying pyarrow/parquet/core.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/parquet
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/interchange
  copying pyarrow/tests/interchange/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/interchange
  copying pyarrow/tests/interchange/test_conversion.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/interchange
  copying pyarrow/tests/interchange/test_interchange_spec.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/interchange
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_basic.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/conftest.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/encryption.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_parquet_writer.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_metadata.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/__init__.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_datetime.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/common.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_dataset.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_data_types.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_pandas.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_parquet_file.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_compliant_nested_type.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  copying pyarrow/tests/parquet/test_encryption.py -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/parquet
  running egg_info
  writing pyarrow.egg-info/PKG-INFO
  writing dependency_links to pyarrow.egg-info/dependency_links.txt
  writing requirements to pyarrow.egg-info/requires.txt
  writing top-level names to pyarrow.egg-info/top_level.txt
  ERROR setuptools_scm._file_finders.git 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-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_acero.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_acero.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_compute.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_compute.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_csv.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_csv.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_cuda.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_cuda.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_dataset.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_dataset.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_dataset_orc.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_dataset_parquet.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_feather.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_flight.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_fs.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_fs.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_gcsfs.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_hdfs.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_hdfsio.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_json.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_json.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_orc.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_orc.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_parquet.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_parquet.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_parquet_encryption.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_parquet_encryption.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_pyarrow_cpp_tests.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_pyarrow_cpp_tests.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_s3fs.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/_substrait.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/array.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/benchmark.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/builder.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/compat.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/config.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/error.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/gandiva.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/io.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/ipc.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/lib.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/lib.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/memory.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/pandas-shim.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/public-api.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/scalar.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/table.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/tensor.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  copying pyarrow/types.pxi -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/common.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_feather.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_acero.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/__init__.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libgandiva.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_python.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_flight.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_dataset_parquet.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_dataset.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_substrait.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_cuda.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/includes/libarrow_fs.pxd -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/includes
  copying pyarrow/tests/bound_function_visit_strings.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/extensions.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  copying pyarrow/tests/pyarrow_cython_example.pyx -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/feather
  copying pyarrow/tests/data/feather/v0.17.0.version.2-compression.lz4.feather -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/feather
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/README.md -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.jsn.gz -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.orc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.test1.jsn.gz -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.test1.orc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.jsn.gz -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.orc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/decimal.jsn.gz -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  copying pyarrow/tests/data/orc/decimal.orc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/orc
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/parquet
  copying pyarrow/tests/data/parquet/v0.7.1.all-named-index.parquet -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/parquet
  copying pyarrow/tests/data/parquet/v0.7.1.column-metadata-handling.parquet -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/parquet
  copying pyarrow/tests/data/parquet/v0.7.1.parquet -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/parquet
  copying pyarrow/tests/data/parquet/v0.7.1.some-named-index.parquet -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/tests/data/parquet
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow
  creating build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/CMakeLists.txt -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/api.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/arrow_to_pandas.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/arrow_to_pandas.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/arrow_to_python_internal.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/benchmark.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/benchmark.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/common.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/common.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/csv.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/csv.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/datetime.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/datetime.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/decimal.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/decimal.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/deserialize.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/deserialize.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/extension_type.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/extension_type.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/filesystem.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/filesystem.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/flight.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/flight.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/gdb.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/gdb.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/helpers.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/helpers.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/inference.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/inference.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/init.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/init.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/io.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/io.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/ipc.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/ipc.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/iterators.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_convert.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_convert.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_internal.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_interop.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_to_arrow.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/numpy_to_arrow.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/parquet_encryption.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/parquet_encryption.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/pch.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/platform.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/pyarrow.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/pyarrow.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/pyarrow_api.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/pyarrow_lib.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/python_test.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/python_test.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/python_to_arrow.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/python_to_arrow.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/serialize.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/serialize.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/type_traits.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/udf.cc -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/udf.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  copying pyarrow/src/arrow/python/visibility.h -> build/lib.macosx-11.0-arm64-cpython-312/pyarrow/src/arrow/python
  running build_ext
  creating /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/build/temp.macosx-11.0-arm64-cpython-312
  -- Running cmake for PyArrow
  cmake -DCMAKE_INSTALL_PREFIX=/private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/build/lib.macosx-11.0-arm64-cpython-312/pyarrow -DPYTHON_EXECUTABLE=/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp_xpza7zb/.venv/bin/python -DPython3_EXECUTABLE=/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp_xpza7zb/.venv/bin/python -DPYARROW_CXXFLAGS= -DPYARROW_BUILD_CUDA=off -DPYARROW_BUILD_SUBSTRAIT=off -DPYARROW_BUILD_FLIGHT=off -DPYARROW_BUILD_GANDIVA=off -DPYARROW_BUILD_ACERO=off -DPYARROW_BUILD_DATASET=off -DPYARROW_BUILD_ORC=off -DPYARROW_BUILD_PARQUET=off -DPYARROW_BUILD_PARQUET_ENCRYPTION=off -DPYARROW_BUILD_GCS=off -DPYARROW_BUILD_S3=off -DPYARROW_BUILD_HDFS=off -DPYARROW_BUNDLE_ARROW_CPP=off -DPYARROW_BUNDLE_CYTHON_CPP=off -DPYARROW_GENERATE_COVERAGE=off -DCMAKE_BUILD_TYPE=release /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0
  -- The C compiler identification is Clang 11.1.0
  -- The CXX compiler identification is Clang 11.1.0
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: /nix/store/7dkbcs6vgwbkb6rafh03j9j0bn8qpki0-clang-wrapper-11.1.0/bin/clang - 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: /nix/store/7dkbcs6vgwbkb6rafh03j9j0bn8qpki0-clang-wrapper-11.1.0/bin/clang++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- System processor: arm64
  -- Performing Test CXX_SUPPORTS_SVE
  -- Performing Test CXX_SUPPORTS_SVE - Success
  -- Arrow build warning level: PRODUCTION
  -- Build Type: RELEASE
  -- CMAKE_C_FLAGS:  -Wall -Wno-unknown-warning-option -Wno-pass-failed -march=armv8-a  -Qunused-arguments -fcolor-diagnostics  -fno-omit-frame-pointer -Wno-unused-variable -Wno-maybe-uninitialized -Wno-parentheses-equality -Wno-constant-logical-operand -Wno-missing-declarations -Wno-sometimes-uninitialized -Wno-return-type-c-linkage
  -- CMAKE_CXX_FLAGS:  -fno-aligned-new  -Wall -Wno-unknown-warning-option -Wno-pass-failed -march=armv8-a  -Qunused-arguments -fcolor-diagnostics  -fno-omit-frame-pointer -Wno-unused-variable -Wno-maybe-uninitialized -Wno-parentheses-equality -Wno-constant-logical-operand -Wno-missing-declarations -Wno-sometimes-uninitialized -Wno-return-type-c-linkage
  -- Generator: Unix Makefiles
  -- Build output directory: /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/build/temp.macosx-11.0-arm64-cpython-312/release
  -- Found Python3: /var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp_xpza7zb/.venv/bin/python (found version "3.12.0") found components: Interpreter Development.Module NumPy
  -- Found Python3Alt: /var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp_xpza7zb/.venv/bin/python
  -- Arrow version: 12.0.1
  -- Found the Arrow shared library: /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/lib/libarrow.1200.1.0.dylib
  -- Found the Arrow import library: ARROW_IMPORT_LIB-NOTFOUND
  -- Found the Arrow static library:
  -- Configuring done (4.8s)
  -- Generating done (0.0s)
  -- Build files have been written to: /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/build/temp.macosx-11.0-arm64-cpython-312
  -- Finished cmake for PyArrow
  -- Running cmake --build for PyArrow
  cmake --build . --config release --
  [  1%] Compiling Cython CXX source for lib...
  [  1%] Built target lib_pyx
  [  3%] Generating pyarrow/src/arrow/python/lib_api.h, pyarrow/src/arrow/python/lib.h
  [  3%] Built target cython_api_headers
  [  5%] Building CXX object CMakeFiles/arrow_python.dir/cmake_pch_arm64.hxx.pch
  [  7%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/arrow_to_pandas.cc.o
  [  8%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/benchmark.cc.o
  [ 10%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/common.cc.o
  [ 12%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/datetime.cc.o
  [ 14%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/decimal.cc.o
  [ 15%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/deserialize.cc.o
  [ 17%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/extension_type.cc.o
  [ 19%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/gdb.cc.o
  [ 21%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/helpers.cc.o
  [ 22%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/inference.cc.o
  [ 24%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/init.cc.o
  [ 26%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/io.cc.o
  [ 28%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/ipc.cc.o
  [ 29%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/numpy_convert.cc.o
  [ 31%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/numpy_to_arrow.cc.o
  [ 33%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/python_test.cc.o
  [ 35%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/python_to_arrow.cc.o
  [ 36%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/pyarrow.cc.o
  [ 38%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/serialize.cc.o
  [ 40%] Building CXX object CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/udf.cc.o
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:295:10: warning: 'Resize' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    Status Resize(KernelContext* ctx, int64_t new_num_groups) {
           ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:87:18: note: overridden virtual function is here
    virtual Status Resize(KernelContext* ctx, int64_t size) = 0;
                   ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:302:10: warning: 'Consume' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    Status Consume(KernelContext* ctx, const ExecSpan& batch) {
           ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:88:18: note: overridden virtual function is here
    virtual Status Consume(KernelContext* ctx, const ExecSpan& batch) = 0;
                   ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:318:10: warning: 'Merge' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    Status Merge(KernelContext* ctx, KernelState&& other_state,
           ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:89:18: note: overridden virtual function is here
    virtual Status Merge(KernelContext* ct, KernelState&& other, const ArrayData&) = 0;
                   ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:339:10: warning: 'Finalize' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    Status Finalize(KernelContext* ctx, Datum* out) {
           ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:90:18: note: overridden virtual function is here
    virtual Status Finalize(KernelContext* ctx, Datum* out) = 0;
                   ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:582:34: error: no matching constructor for initialization of 'compute::ScalarAggregateKernel'
    compute::ScalarAggregateKernel kernel(std::move(sig), std::move(init),
                                   ^      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:657:3: note: candidate constructor not viable: no known conversion from 'typename remove_reference<shared_ptr<KernelSignature> &>::type' (aka 'std::__1::shared_ptr<arrow::compute::KernelSignature>') to 'std::vector<InputType>' for 1st argument
    ScalarAggregateKernel(std::vector<InputType> in_types, OutputType out_type,
    ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:649:3: note: candidate constructor not viable: requires 5 arguments, but 6 were provided
    ScalarAggregateKernel(std::shared_ptr<KernelSignature> sig, KernelInit init,
    ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:646:21: note: candidate constructor (the implicit copy constructor) not viable: requires 1 argument, but 6 were provided
  struct ARROW_EXPORT ScalarAggregateKernel : public Kernel {
                      ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:646:21: note: candidate constructor (the implicit move constructor) not viable: requires 1 argument, but 6 were provided
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:647:3: note: candidate constructor not viable: requires 0 arguments, but 6 were provided
    ScalarAggregateKernel() = default;
    ^
  /private/var/folders/bt/72h1kztd54n6_fdtn41hn3tc0000gn/T/tmp74wyibkt/pyarrow-13.0.0/pyarrow/src/arrow/python/udf.cc:658:32: error: no matching constructor for initialization of 'compute::HashAggregateKernel'
    compute::HashAggregateKernel kernel(
                                 ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:709:3: note: candidate constructor not viable: no known conversion from 'typename remove_reference<shared_ptr<KernelSignature> &>::type' (aka 'std::__1::shared_ptr<arrow::compute::KernelSignature>') to 'std::vector<InputType>' for 1st argument
    HashAggregateKernel(std::vector<InputType> in_types, OutputType out_type,
    ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:700:3: note: candidate constructor not viable: requires 6 arguments, but 7 were provided
    HashAggregateKernel(std::shared_ptr<KernelSignature> sig, KernelInit init,
    ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:697:21: note: candidate constructor (the implicit copy constructor) not viable: requires 1 argument, but 7 were provided
  struct ARROW_EXPORT HashAggregateKernel : public Kernel {
                      ^
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:697:21: note: candidate constructor (the implicit move constructor) not viable: requires 1 argument, but 7 were provided
  /nix/store/bf6hgykwi1kcmbr4awvh4sw4kyzapgs0-arrow-cpp-12.0.1/include/arrow/compute/kernel.h:698:3: note: candidate constructor not viable: requires 0 arguments, but 7 were provided
    HashAggregateKernel() = default;
    ^
  4 warnings and 2 errors generated.
  make[2]: *** [CMakeFiles/arrow_python.dir/build.make:395: CMakeFiles/arrow_python.dir/pyarrow/src/arrow/python/udf.cc.o] Error 1
  make[1]: *** [CMakeFiles/Makefile2:108: CMakeFiles/arrow_python.dir/all] Error 2
  make: *** [Makefile:136: all] Error 2
  error: command '/etc/profiles/per-user/jcf/bin/cmake' failed with exit code 2

  at /nix/store/3igqm2xzcf2623lyym98flb679mg8ha1-python3.10-poetry-1.5.1/lib/python3.10/site-packages/poetry/installation/chef.py:147 in _prepare
      143│
      144│                 error = ChefBuildError("\n\n".join(message_parts))
      145│
      146│             if error is not None:
    → 147│                 raise error from None
      148│
      149│             return path
      150│
      151│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:

Note: This error originates from the build backend, and is likely not a problem with poetry but with pyarrow (13.0.0) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "pyarrow (==13.0.0)"'.

Using
{
  languages.python = {
    enable = true;
    version = "3.9.17";
    poetry.enable = true;
    poetry.activate.enable = true;
    poetry.install.enable = true;
  };
}

and
inputs:
  nixpkgs-python:
    url: github:cachix/nixpkgs-python

it now works on #1005


aframe  controls

how to add a component ? i have followed all the steps u mentioned , but only change in my case is i am not using 360 degree video, instead i have a collection of videos which i want to create video gallery and add a controls to them.
Problems:

Start and pause button comes initially and get eased out.
I am using a-video tags, but for me controls functionality is not working at all.

Here is a sample of my code:
                                                                   <video id="video_beacon_offers"  loop="true" src="videos/video_beacon_offers.mp4">
Also please suggest me on how to create a video gallery in aframe. i have collection of videos which want user to see them all as thumbnail and click on particular video to play it.
Thanks
Krishna

mmmm... the component is really made for 360 videos, not flat videos, since the UI is 'floating' in 360 space. Probably I'll do a flat version, will keep you informed

Video controls are working for me, at least on desktop browser. But none of the attributes do anything. it would be nice to be able to resize the controls since right now they appear very small.

Found I can resize them using scale attribute.
I'm also interested in a flat controller for  which can exist outside the video player.

can the control be reposition?


Improve and flatten menu bar handling (linux)

📒 Description
This fixes the tray icon menu to display just as one level instead of two (in some environments where that happened). It also simplifies the menu creation process by quite a bit.
🕶 Types of changes

Bug fix (non-breaking change which fixes an issue)

🤯 List of changes
The weird reassignment of QActions in MainWindowController is not present anymore and the actions are now accessed directly through the ui member.
👫 Relationships
Closes #2660
🔎 Review hints
See if the tray has only 1 level and is the same as the menu in the main application (not like in #2660)

Well done!


Add react-map-gl to allowedPackageJsonDependencies

See types field in<EMAIL_ADDRESS>

I'm confused about this. react-map-gl is itself on DT, and is currently failing because of a transitive dependency on gl-matrix. Is this PR supposed to help with that? Or with some dependent of react-map-gl?

react-map-gl currently relies on implicit children (of e.g. FunctionComponent). Since they ship their own types now, we can just drop them from the DT repo.


adds meaningless doc change for the purpose of testing our docs versioning

@riknoll , should this test the new fix from you and Michal?

Shows up on live at:

But not in staging:

So LGTM!


WIP: Implement Mafia

Not trying to merge this; just using diff functionality.

I think it's safe to close this for the time being...


[Codegen] Shall we allow users to pass in a path to a xata directory and work with this instead of schema.json?

Given that the Xata CLI creates a folder and puts multiple files in it (config.json, schema.json, and .gitignore), should we update the codegen CLI to receive an argument for the folder instead and then work with that?
I think this also might make sense since we’d like to use the config.json file according to #25.

Sounds good to me. When we started working on the SDK there was only a schema.json file. But now we have and we are going to use config.json. So yeah, makes sense.


Camel case conversion is forced

Bug report

Bug summary
The  camel case conversion toggled by the convert_camel_case flag  of the Studio object creator is always enforced.
Code for reproduction

from pycromanager import Studio
studio = Studio(convert_camel_case=False)
data = studio.data()
data.summaryMetadataBuilder()

Expected outcome
The camel case flag should be respected
Actual outcome
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'org_micromanager_data_internal_DefaultDataManager' object has no attribute 'summaryMetadataBuilder'. Did you mean: 'summary_metadata_builder'?

Version Info

Operating system: MacOS
pycromanager version: 0.19.2
MicroManager version: Micro-Manager-2.0.1-20220909
Python version: Python 3.10.4
Python environment python shell

Sorry, it appears that after restarting the python shell, the camel capitalization now works. Anyway I will close, sorry for the disturbance. Please delete this isssue.


Integration with API Connections

See if we can integrate with Azure API Connections to avoid having to handle the Azure Storage credentials.

It is not possible at the moment to integrate Azure API Connections in your own API Apps.


[1.20] Issue Block Placer not placing

industrial-foregoing-1.20.1-3.5.7
Block placer not placing blocks.  Shows no working area.

Make sure its not in a protected area

Thanks.  I needed to allow fake players.

for the record, the fake player ID is:
ec5b5875-ebb5-4b47-833b-0de37ac9e6d7
As found here:
https://github.com/InnovativeOnlineIndustries/Industrial-Foregoing/blob/fc4c286af75d164d213c86ac1c9df8cfa4e49977/src/main/java/com/buuz135/industrial/utils/IFFakePlayer.java#L41


Time calculation issue in ControlledRealTimeReopenThread

I have been trying to figure out why ControlledRealTimeReopenThread.Run is in a constant waiting state. It is blocking at the reopenCond.WaitOne call.
I ended up copying all the code into LinqPad that determines the amount of wait time and it seems to me that these calculations aren't correct and it ends up making the wait times very long.
Here's some code that does the same calculations as in ControlledRealTimeReopenThread to determine how long the timeout will be in the WaitOne call:

// These are the values that would be passed into the ctor of ControlledRealTimeReopenThread
var targetMaxStaleSec = 5.0; // this should just wait a max of 5 seconds
var targetMinStaleSec = 0.1; // this should wait a min of 100 milliseconds

// Then the calculations go like this:
var targetMaxStaleNS = (long)(1000000000 * targetMaxStaleSec); // =<PHONE_NUMBER>
var targetMinStaleNS = (long)(1000000000 * targetMinStaleSec); // = 100000000

var hasWaiting = false;

long lastReopenStartNS = DateTime.UtcNow.Ticks * 100;
long nextReopenStartNS = lastReopenStartNS + (hasWaiting ? targetMinStaleNS : targetMaxStaleNS);
long sleepNS = nextReopenStartNS - Time.NanoTime(); // =<PHONE_NUMBER>8200

var wait = TimeSpan.FromMilliseconds(sleepNS / Time.MILLISECONDS_PER_NANOSECOND);

// This is :

// 07:00:04.9990000
// which is more than 7 hours !

// Used for the Time methods above
internal static class Time
{
	public const long MILLISECONDS_PER_NANOSECOND = 1000000;
	public const long TICKS_PER_NANOSECOND = 100;

	public static long NanoTime()
	{
		return DateTime.Now.Ticks * TICKS_PER_NANOSECOND;
		// LUCENENET TODO: Change to
		// return (Stopwatch.GetTimestamp() / Stopwatch.Frequency) *<PHONE_NUMBER>;
		// for better accuracy that is not affected by the system clock
	}
}

The issue is: DateTime.UtcNow.Ticks * 100;
In the Time.NanoTime() method, this calculation is:
DateTime.Now.Ticks * TICKS_PER_NANOSECOND;
The difference being UtcNow vs Now.
Shouldn't this line: https://github.com/apache/lucenenet/blob/b03b93683c4d3a7128e54692525cb7d1315637f5/src/Lucene.Net/Search/ControlledRealTimeReopenThread.cs#L228 use Time.NanoTime(); just like this line does? https://github.com/apache/lucenenet/blob/b03b93683c4d3a7128e54692525cb7d1315637f5/src/Lucene.Net/Search/ControlledRealTimeReopenThread.cs#L257
It also seems like all of this logic could be hugely simplified for just converting the different of "now" and how long to wait based on the supplied seconds, but I could be overlooking something.

Thanks Shannon.
This goes to the heart of one of the issues that I have been meaning to post for awhile now - namely, that because J2N didn't exist when we ported Lucene.NET, we need to go back and review all of the code that depends on system timing. I created a different implementation of Time.NanoTime() in J2N than the implementation in Lucene.Net.Support, but being hyper-aware of the fact that the concurrency code may break by swapping the implementation, migrating to this new method has been put this off until a proper review can be done.
During writing tests and benchmarks, I noticed that Time.NanoTime() isn't as accurate as using a Stopwatch instance, so this needs another pass to ensure that implementation is solid before migrating to it. We might need to use some AsyncLocal approach to fix it so it uses 1 Timestamp instance per parallel process rather than using the static Stopwatch.GetTimestamp().
This is of course compounded by the facts that:

The code was inconsistently translated from Java between DateTime.Now, DateTime.UtcNow,Time.NanoTime(), and Time.CurrentTimeMilliseconds() thoughout the project.
In Java, they are supposed to be using System.nanoTime() for the most accurate timing, but they inconsistently switch between System.nanoTime() and System.currentTimeMillis() throughout the project.

We could fix this by analyzing each use of timing case-by-case and switching them all to using individual Stopwatch instances. I don't think that is so bad if the code is in isolation, but we still should fix J2N.Time.NanoTime() and J2N.Time.CurrentTimeMilliseconds() so they work right so we can also easily translate these lines during future porting efforts without making the same mistakes again.
In the latter case, we may be able to assume that the code works well enough to use CurrentTimeMilliseconds(), but it means we need 2 methods instead of just NanoTime().

System.currentTimeMillis() in Java returns the number of milliseconds that elapsed since January 1, 1970. So we should fix the J2N implementation to do the same to ensure something isn't thrown off by this. Do note that neither of these implementations are based off of the Java code, so we might want to look there and at the .NET implementation at a low level to ensure there are no additional timing gaps to look out for.

Tip:  It may also help to look at the NodaTime project.

Whatever the case, we should aim to factor out the Time class in Lucene.Net.Support and use a common timing method everywhere (from J2N) except in special isolated cases. And ultimately use Stopwatch instead of DateTime.Now or DateTime.UtcNow consistently for timing code.

NOTE: If you wish to fix this in J2N, please base your work off of the release/v2.0 branch and target that same branch when submitting the PR.
Note also that if you don't have Xamarin setup on your dev machine, you can workaround the issue by unloading all of the Xamarin projects and tests.


Support GetEX command

Search before asking

[X] I had searched in the issues and found no similar issues.

Motivation
Redis supports the GetEX command since 6.2.0. We can follow-up as well since this command can benefit users if they want to extend or reduce the expire time when touching.
Solution
Implement the command described in: https://redis.io/commands/getex/
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Can I try it on ? #961

Can I try it on ? #961

Assigned, thank you!


Not able to use custom plugin

🐞 Bug report
Description
When defining a custom plugin and registering it, it can't be used as type,  as defined in the documentation https://github.com/scullyio/scully/blob/master/docs/plugins.md
🔬Minimal Reproduction

Start from a new empty angular-cli project with one route, for example /about.
Add scully, following the docs
Create a new plugin voidPlugin.js in the root of the project.

function voidPlugin(html, route) {
  return Promise.resolve(html);
}
module.exports.voidPlugin = voidPlugin;

import and register the plugin in the scully.config.js

const { registerPlugin } = require('@scullyio/scully/bin');
const { voidPlugin } = require('./voidPlugin');

registerPlugin('render', 'void', voidPlugin);

exports.config = {
  projectRoot: "./src/app",
  routes: {
    "/about": {
      "type": "void"
    }
  }
};

💻Your Environment
Angular Version:

Angular CLI: 9.0.0-rc.7
Node: 12.14.0
OS: darwin x64

Angular: 9.0.0-rc.7
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.0-rc.7
@angular-devkit/build-angular     0.900.0-rc.7
@angular-devkit/build-optimizer   0.900.0-rc.7
@angular-devkit/build-webpack     0.900.0-rc.7
@angular-devkit/core              9.0.0-rc.7
@angular-devkit/schematics        9.0.0-rc.7
@ngtools/webpack                  9.0.0-rc.7
@schematics/angular               9.0.0-rc.7
@schematics/update                0.900.0-rc.7
rxjs                              6.5.4
typescript                        3.6.4
webpack                           4.41.2

Scully Version:

"@scullyio/init": "0.0.9",
"@scullyio/ng-lib": "latest",
 "@scullyio/scully": "latest",

🔥 Exception or Error

> scully

The option outFolder isn't configured, using default folder "/Users/samvloeberghs/Projects/Kwerri/ng-v9-scullyio/dist/static/".
Unknown type "void" in route "/about"

I think an example repo is not really required, because it's actually just the most basic example of setting up a render plugin. But if really needed I have just pushed my test code here: https://github.com/samvloeberghs/ng-v9-scullyio

same in here
https://github.com/stewwan/stewan-io

npm install
ng build
npm run scully

@SanderElias is working in a fix for that

@samvloeberghs You can only list routePlugins in the types.
When you want to add a (couple) of renderPlugins, you can use the
postRenderers: ['plugins','by', 'name'] option in your config
I created a small table of contents plgin that show how this can be done in #161  (might be merged in master by now)

@SanderElias cool, will try it out as soon as it hits master/latest

@samvloeberghs its in master since yesterday. I did push out a new version to NPM too.

@SanderElias I don't think it's solved now. I had to the impression I could add a plugin that gets executed post-render. Basically I just want to run a post-render function that takes the HTML and modifies it. How can this be achieved.
If I'm not mistaken, postRenderers is part of HandledRoutebut that is part of the router plugins?

@samvloeberghs, The type field needs a route-plugin. It will not work with render plugins.
try this:
require('./plugins/testPlugin');

exports.config = {
  projectRoot: './src/app',
  routes: {
    '/about': {
      type: 'default'.
      postRenderers: ['test'],
    }
  }
}

We really need a bit more documentatin around this.

@SanderElias  I tried this, and it doesn't work:
error:
Unknown type "default" in route "/"
Unknown type "default" in route "/about"
Unknown type "default" in route "/not-found"

// scully.config.js
require('./plugins/testPlugin');

exports.config = {
  projectRoot: './src/app',
  routes: {
    '/': {
      type: 'default',
      postRenderers: ['test'],
    },
    '/about': {
      type: 'default',
      postRenderers: ['test'],
    },
    '/not-found': {
      type: 'default',
      postRenderers: ['test'],
    }
  }
};

@SanderElias there is no plugin with default. You have it all configured, but never build it. HAHA!

Use this plugin as type:
const {registerPlugin, configValidator} = require('@scullyio/scully');
function voidPlugin() {
  const name = `voidPlugin-${Math.ceil(Math.random() * 1000)}`;
  voidPluginFunction[configValidator] = async () => [];
  registerPlugin('router', name, voidPluginFunction);
  return name;

  function voidPluginFunction(r){
    return Promise.resolve([{route: r}]);
  }
}

Add this to your config as follows:
...
'/about' : {
  type: voidPlugin(),
  postRenderers: ['minifyHtml'],
}

I cloned your project, and did this, and it worked fine.

@samvloeberghs Turns out, I didn't activate the default plugin :-D
However, yes, there is a defaultPostRenderers, and you can add that to the generic part of your config like:
require('./plugins/testPlugin');

exports.config = {
  projectRoot: './src/app',
  defaultPostRenderers: ['test']
  routes: {
    '/': {
      type: 'default',
    },
    '/about': {
      type: 'default',
    },
    '/not-found': {
      type: 'default',
    }
  }
};

If you specify the postrenderers in a route, those will be use instead of the default ones, not in addition

@SanderElias this is what I needed, thanks!
The route configuration is not required anymore either, as these are auto-discovered by Scully.
require('./plugins/testPlugin');

exports.config = {
  projectRoot: './src/app',
  defaultPostRenderers: ['test']
};

is enough

@samvloeberghs If this works for you, can I close the issue?


4025 - OpenTelemetry Spike

4025 - OpenTelemetry Spike
📲 What
Investigate Open Telemetry
🤔 Why
Technology agnostic telemetry metrics
🛠 How
Adding packeg reference and sending telemetry data.
👀 Evidence
Screenshots / external resources / links / etc.
Link to documentation updated with changes impacted in the PR
🕵 How to test
Notes for QA
✅ Acceptance criteria Checklist
Code peer reviewed?
Documentation has been updated to reflect the changes?
Passing all automated tests, including a successful deployment?
Passing any exploratory testing?
Rebased/merged with latest changes from development and re-tested?
Meeting the Coding Standards?

/azp run