Hi,
Could you upload the log to something such as
https://gist.github.com/ and share the URL?
Thanks,
--
kou
In
"Re: Building Arrow Cpp: Cannot find Boost on MacOS" on Tue, 1 Feb 2022
16:47:45 -0500,
Li Jin wrote:
> Hi!
>
> I ran
>
> "cmake .. -DARROW_BUILD_TESTS=ON -DARROW_COMPUTE=O
In my opinion, any PMC member should be allowed to use the Twitter account
without any other checks, balances, or friction. They know that they are
speaking for the project, and only for the project. They are PMC members so we
trust them to do the right thing.
If committers and other non-PMC co
Could you please share the retro board so that we can all comment on the issues?
I’m very sorry for at least two of the redos were actually related to ORC with
one of them caused by a simple import error I didn’t find in my Python docker
tests which is caused by the fact that my old way to run P
Hi!
I ran
"cmake .. -DARROW_BUILD_TESTS=ON -DARROW_COMPUTE=ON -DARROW_DATASET=ON
-DCMAKE_BUILD_TYPE=Debug -DCMAKE_FIND_DEBUG_MODE=ON"
and here is the log.
Perhaps Cmake cannot find where Brew installed this by default? (Just
guessing, new to CMake too..)
Li
On Tue, Feb 1, 2022 at 4:30 PM Suto
Hi,
Could you run cmake with -DCMAKE_FIND_DEBUG_MODE=ON and
share log of it?
FYI: Boost 1.76.0 is found in our CI:
https://github.com/apache/arrow/runs/5017148285?check_suite_focus=true#step:7:183
-- Found Boost: /usr/local/lib/cmake/Boost-1.76.0/BoostConfig.cmake (found
suitable version
Hello!
I am new to the Arrow cpp code and play with it a little. Unfortunately I
hit this error when trying to cmake with preset "ninja-debug-basic". I
wonder if anyone else has hit an similar issue?
cmake .. --preset ninja-debug-basic
...
-- ARROW_ZSTD_BUILD_VERSION: v1.5.1
-- ARROW_ZSTD_BUIL
To be clear I haven't used that twitter-together action myself, was
just using it as an example for how such a workflow could be set up. I
imagine it won't be too much work for us to write our own action if
needed.
Thanks,
QP Hou
On Tue, Feb 1, 2022 at 5:31 AM Neal Richardson
wrote:
>
> I like t
For anyone interested on the topic, I got some feedbacks that suggest it
might be more effective to have a meeting dedicated to the topic with the
people who have been involved in preparing the release and subsequently
share the outcome of that meeting with everyone at the Arrow biweekly
meeting.
I like the idea too. If we were to use the github action to send tweets, we
would need to get INFRA to add it to the allowlist since they restrict
which actions we can use. I don't think it's a blocker, just would add some
extra time in the process of getting it set up.
Neal
On Tue, Feb 1, 2022
I never used https://github.com/gr2m/twitter-together previously, in the
past I used Hootsuite to set up approval workflows, but I think that the
idea of setting up a workflow through github PRs looks like a good idea. It
would be able to leverage committer/pmc membership to merge the PRs and
would
Given the unexpected amount of tries we had to go through to publish
version 7 (I don't think there were past cases where RC10 was reached), it
would be helpful to go through what happened, what didn't work and what we
can do to prevent it from happening again in the future.
I created a meeting fo
11 matches
Mail list logo
