chore: bump docker/login-action from 4.0.0 to 4.1.0 (#873)
Bumps docker/login-action from 4.0.0 to 4.1.0.
Release notes
Sourced from docker/login-action's releases.
v4.1.0
- Fix scoped Docker Hub cleanup path when registry is omitted by
@crazy-maxin docker/login-action#945- Bump
@aws-sdk/client-ecrand@aws-sdk/client-ecr-publicto 3.1020.0 in docker/login-action#930- Bump
@docker/actions-toolkitfrom 0.77.0 to 0.86.0 in docker/login-action#932 docker/login-action#936- Bump brace-expansion from 1.1.12 to 1.1.13 in docker/login-action#952
- Bump fast-xml-parser from 5.3.4 to 5.3.6 in docker/login-action#942
- Bump flatted from 3.3.3 to 3.4.2 in docker/login-action#944
- Bump glob from 10.3.12 to 10.5.0 in docker/login-action#940
- Bump handlebars from 4.7.8 to 4.7.9 in docker/login-action#949
- Bump http-proxy-agent and https-proxy-agent to 8.0.0 in docker/login-action#937
- Bump lodash from 4.17.23 to 4.18.1 in docker/login-action#958
- Bump minimatch from 3.1.2 to 3.1.5 in docker/login-action#941
- Bump picomatch from 4.0.3 to 4.0.4 in docker/login-action#948
- Bump undici from 6.23.0 to 6.24.1 in docker/login-action#938
Full Changelog: https://github.com/docker/login-action/compare/v4.0.0...v4.1.0
Commits
4907a6dMerge pull request #930 from docker/dependabot/npm_and_yarn/aws-sdk-dependenc...1e233e6chore: update generated content6c24eadbuild(deps): bump the aws-sdk-dependencies group with 2 updatesee034d7Merge pull request #958 from docker/dependabot/npm_and_yarn/lodash-4.18.11527209Merge pull request #937 from docker/dependabot/npm_and_yarn/proxy-agent-depen...d39362abuild(deps): bump lodash from 4.17.23 to 4.18.1a6f092bchore: update generated content60953f0build(deps): bump the proxy-agent-dependencies group with 2 updates62c6885Merge pull request #936 from docker/dependabot/npm_and_yarn/docker/actions-to...102c0e6chore: update generated content- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802032778号
nanoarrow
The nanoarrow libraries are a set of helpers to produce and consume Arrow data, including the Arrow C Data, Arrow C Stream, and Arrow C Device, structures and the serialized Arrow IPC format. The vision of nanoarrow is that it should be trivial for libraries to produce and consume Arrow data: it helps fulfill this vision by providing high-quality, easy-to-adopt helpers to produce, consume, and test Arrow data types and arrays.
The nanoarrow libraries were built to be:
Getting started
The nanoarrow Python bindings are available from PyPI and conda-forge:
The nanoarrow R package is available from CRAN:
The C library can be used by generating bundled versions of the core library and its components. This is the version used internally by the R and Python bindings.
CMake is also supported via a build/install with
find_package()or usingFetchContent:The C library can also be used as a Meson subproject installed with:
…and declared as a dependency with:
See the nanoarrow Documentation for extended tutorials and API reference for the C, C++, Python, and R libraries.
The nanoarrow GitHub repository additionally provides a number of examples covering how to use nanoarrow in a variety of build configurations.
Development
Building with CMake
CMake is the primary build system used to develop and test the nanoarrow C library. You can build nanoarrow with:
To build nanoarrow along with tests run:
If you are able to install Arrow C++ you can enable more testing:
Tests can be run with
ctest.Building with Meson
CMake is the officially supported build system for nanoarrow. However, the Meson backend is an experimental feature you may also wish to try.
After setting up your project, be sure to enable the options you want:
You can enable better test coverage if Apache Arrow is installed on your system with
-Dtest_with_arrow=enabled. Depending on how you have installed Apache Arrow, you may also need to pass--pkg-config-path <path to directory with arrow.pc>.With the above out of the way, the
compilecommand should take care of the rest:Upon a successful build you can execute the test suite and benchmarks with the following commands: