Shenyang Cai
Shenyang Cai
Could you clarify the purpose of this PR? BigFrames 2.29.0 has already been released with https://github.com/googleapis/python-bigquery-dataframes/pull/2242
The next step is add logics of type conversions from BQ schema to Pandas
> doctest failures appear to be related > > ``` > FAILED bigframes/bigquery/_operations/ai.py::bigframes.bigquery._operations.ai.generate > FAILED bigframes/bigquery/_operations/ai.py::bigframes.bigquery._operations.ai.generate_bool > FAILED bigframes/bigquery/_operations/ai.py::bigframes.bigquery._operations.ai.generate_double > FAILED bigframes/bigquery/_operations/ai.py::bigframes.bigquery._operations.ai.generate_int > ``` Yeah those look like permission failures....
> cl/828515544 may be a useful example. that's where I granted the samples tests users permissions. that shouldn't affect doctest, though. doctest should use the compute engine service account from...
Do not merge this PR until related failures in doc tests and notebook tests are gone
Closing this obsolete PR.
> Can we please not log internal op initializers, or really anything not directly tied to user intentions or server requests? I worry this is very fragile. I need to...
Talked with @TrevorBergeron: the concern at the moment is that this PR is trying to log internal mechanisms instead of user intentions, which deviates from the purpose of the `class_logger`....
Looks like there's a lint error. Could you fix it? Thanks a lot!