My preference order would be:
"black" then "autopep8" then "no change"
Echoing Joris's and Neal's comments I'm a huge fan of having tools fix
things for me (and the more it handles the better). Maybe I just need to
setup my editor better to deal with PEP8 issue but I find I spend more time
then
Frank Du created ARROW-8401:
---
Summary: [C++] Add AVX2/AVX512 version of
ByteStreamSplitDecode/ByteStreamSplitEncode
Key: ARROW-8401
URL: https://issues.apache.org/jira/browse/ARROW-8401
Project: Apache
Arrow Build Report for Job nightly-2020-04-10-2
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-04-10-2
Failed Tasks:
- conda-win-vs2015-py36:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-04-10-2-azure-conda-win-vs2015-py36
-
Krisztian Szucs created ARROW-8400:
--
Summary: [Python][Dataset] Infer the filesystem from the first
path if multiple paths are passed to dataset()
Key: ARROW-8400
URL:
Mahmut Bulut created ARROW-8399:
---
Summary: [Rust] Extend memory alignments to include other
architectures
Key: ARROW-8399
URL: https://issues.apache.org/jira/browse/ARROW-8399
Project: Apache Arrow
None of the open issues look like they should prevent a release
candidate from being cut.
Fixing the nightly and packaging builds seems like the last remaining
task, but some of them need to be tracked by JIRA issues. Can you
write a list here of what's definitely currently broken?
On Fri, Apr
Krisztian Szucs created ARROW-8398:
--
Summary: [Python] Remove deprecation warnings originating from
python tests
Key: ARROW-8398
URL: https://issues.apache.org/jira/browse/ARROW-8398
Project: Apache
Krisztian Szucs created ARROW-8397:
--
Summary: [C++] Fail to compile aggregate_test.cc on Ubuntu 16.04
Key: ARROW-8397
URL: https://issues.apache.org/jira/browse/ARROW-8397
Project: Apache Arrow
Mahmut Bulut created ARROW-8396:
---
Summary: [Rust] Remove libc from dependencies
Key: ARROW-8396
URL: https://issues.apache.org/jira/browse/ARROW-8396
Project: Apache Arrow
Issue Type:
We still have 12 open issues, about half of them are not essential.
The more pressing problem is the number of failing builds including
packaging builds (see the nightly reports).
Releasing today doesn't look realistic, but if we're able to resolve
the issues over the weekend I can start the
Arrow Build Report for Job nightly-2020-04-10-1
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-04-10-1
Failed Tasks:
- conda-win-vs2015-py36:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-04-10-1-azure-conda-win-vs2015-py36
-
The scheduled report job had issues in the last couple of days because
the tasks took longer to finish and the reporter periodically polls
the results and eventually fail.
I've re-scheduled the cron triggers and reports without polling
(waiting every tasks to finish) the results bit with a wider
dwang created ARROW-8395:
Summary: [Python] conda install pyarrow defaults to 0.11.1 not
0.16.0
Key: ARROW-8395
URL: https://issues.apache.org/jira/browse/ARROW-8395
Project: Apache Arrow
Issue
Shyamal Shukla created ARROW-8394:
-
Summary: Typescript compiler errors for arrow d.ts files, when
using es2015-esm package
Key: ARROW-8394
URL: https://issues.apache.org/jira/browse/ARROW-8394
Projjal Chanda created ARROW-8393:
-
Summary: [C++][Gandiva] Make gandiva function registry
case-insensitive
Key: ARROW-8393
URL: https://issues.apache.org/jira/browse/ARROW-8393
Project: Apache Arrow
15 matches
Mail list logo
