Hi,
On Tue, Oct 25, 2022 at 4:27 AM Matt Topol wrote:
> I'd prefer not to remove them as there are definitely known users of both
> architectures for the Golang libraries. Is CircleCI an option?
>
No, CircleCI (and DroneIO) is not an option at the moment.
CI services which require write permiss
Hi,
> What version of Go is your system Go?
$ go version
go version go1.19 linux/amd64
> Also, can you go to the `go` subdirectory of the repo and
> run `go install ./...` then try again?
Yes. "go install ./..." created
~/go/bin/arrow-flight-integration-{client,server}.
Should we run "go insta
+1 (binding)
Thanks Andy!
On Mon, Oct 24, 2022 at 4:54 PM Andy Grove wrote:
>
> Thanks for the feedback. Perhaps a better approach would be to create some
> documentation in the repo with recommendations for verifying a release and
> leave the automated script to just run "cargo test".
>
> On M
I'd prefer not to remove them as there are definitely known users of both
architectures for the Golang libraries. Is CircleCI an option?
On Mon, Oct 24, 2022 at 9:13 PM Sutou Kouhei wrote:
> Hi,
>
> https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations
>
> > On November 2nd, 2020,
Hi,
https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations
> On November 2nd, 2020, Travis-CI announced the end of
> unlimited support for open source projects.
>
> Infra is therefore moving our CI offerings away from
> Travis-CI in order to keep our builds pipeline
> cost-effective
@kou What version of Go is your system Go? Also, can you go to the `go`
subdirectory of the repo and run `go install ./...` then try again? Running
that `go install ./...` command should build the binaries that were
missing. Unless you have the environment variable `GOBIN` set, it will
place the bu
I would also support a migration of our issues to GitHub. It seems
unlikely to me that another third-party tool would be good enough to
make the whole experience better (given that we already use GitHub for
PRs). And I agree with others that keep using JIRA is not a good
option with this change.
A
Thanks for the feedback. Perhaps a better approach would be to create some
documentation in the repo with recommendations for verifying a release and
leave the automated script to just run "cargo test".
On Mon, Oct 24, 2022 at 2:11 PM Andrew Lamb wrote:
> +1
>
> The verification process was very
I have started a draft PR [1] with a short blog post announcing the
Ballista 0.9.0 release (expected to be released on Wednesday this week).
It would be great to get some feedback on this.
Thanks,
Andy.
[1] https://github.com/apache/arrow-site/pull/257
Hi,
I've been working through a proof-of-concept migration, moving specific
ARROW issues into a personal test repo on GitHub. I've made this repo
public to help demonstrate limitations, successes and options as we
consider this further:
https://github.com/toddfarmer/test_import/issues?q=is%3Aissu
+1
I ran the followings on Debian GNU/Linux sid:
* TEST_DEFAULT=0 \
TEST_SOURCE=1 \
TEST_INTEGRATION_GO=0 \
LANG=C \
TZ=UTC \
CUDAToolkit_ROOT=/usr \
ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON -Dxsimd_SOURCE=BUNDLED" \
dev/release/verify-release-can
If you don't mind, could you replace your EDDSA PGP key in
https://dist.apache.org/repos/dist/dev/arrow/KEYS and
https://dist.apache.org/repos/dist/release/arrow/KEYS with
4096 bits RSA PGP key?
See also: https://infra.apache.org/release-signing.html
In
"Re: [VOTE] Release Apache Arrow 10.0.0
Hi,
>> /root/apache-arrow-10.0.0/cpp/src/arrow/util/value_parsing_test.cc:805:
>> Failure
>> Expected equality of these values:
>> expected
>> Which is: 1514769420
>> converted
>> Which is: 1514769408
>> Google Test trace:
>> /root/apache-arrow-10.0.0/cpp/src/arrow/util/value_parsing_t
+1
The verification process was very heavy weight (running TPCH, etc) and I
didn't let it complete. -- I wonder if we really need to run the full test
suites as part of doing so
Finished release [optimized] target(s) in 27m 55s
The changelog shows a very impressive list of features. Well don
+1 for GH issues mainly because it lowers the barrier to entry and
JIRA won't be an acceptable solution any longer with infra's proposed
changes. I suspect I'd be +1 even without the infra change though
providing everyone else was willing to make the switch.
On Mon, Oct 24, 2022 at 8:19 AM Jacob
+1
While there will be some work associated with migrating to Github Issues I
think it is the only viable solution that does not impose an untenable
burden on the PMC. Additionally I think that using gh issues will lower the
barrier for new contributions as experienced by arrow-rs. I don't think
a
Is there anything I can do on my side to fix this?
On Mon, 24 Oct 2022 at 07:25, Sutou Kouhei wrote:
> Hi,
>
> Neville's PGP key uses EDDSA and gpg on CentOS 7 is old to
> process EDDSA PGP key. This RC is signed by my non-EDDSA PGP
> key. So ignore the error from "gpg --import" on CentOS 7.
>
>
17 matches
Mail list logo
