python-api

Based on @karthikeyann's work on this PR rapidsai/cudf#9767 I'm wondering if it makes sense to consider removing the defaults for the stream parameters in various detail functions. It is pretty surprising how often these are getting missed.

The most common case seems to be in factory functions and various ::create functions. Maybe just do it for those?

Right now the macros for banded alignment like CUDAPOA_BANDED_MATRIX_RIGHT_PADDING are not shared between the kernel code and other sources that determine sizes for bands (such as in batch.cu). For now they're hard coded to specific numbers, but this is error prone. This needs to be fixed to the macros are shared between files.

When running the regression, the resulting logs seem to end up in third_party/tests/$TEST/.... This of course is not unnoticed by git, so a git status shows a ton of non-added new files added.

To reproduce:

make
make regression
git status   # observe all the files

Build or test artifacts should never clutter the rest of the code-base (we should regard them as read-only in

Persian, nonstandardly, uses ~ to separate variants. Fix these upstream, and then rescrape.

The src/examples/server/pets.py file contains stubs for all the functions corresponding to the the operation IDs as defined in the petstore.yaml specification. However, only find_pets_by_status has any implementation, while all others