Closed birdflyi closed 5 months ago
LGTM, thanks.
And openDigger.quick
is a legacy API which is deprecated right now and should be removed from the lib, I will do this soon.
And like fixed in #1507 with the default config time value, right now for Jan. 2024, if you do not set the endYear
and endMonth
manually, it will cause a bug in the SQL which leads to the TOO_LARGE_ARRAY_SIZE
problem, it should be fixed after above PR merged.
LGTM, thanks.
And
openDigger.quick
is a legacy API which is deprecated right now and should be removed from the lib, I will do this soon.
OK, I'll remove the replacement function(implemented in python) of this deprecated function openDigger.quick
as well.
And like fixed in #1507 with the default config time value, right now for Jan. 2024, if you do not set the
endYear
andendMonth
manually, it will cause a bug in the SQL which leads to theTOO_LARGE_ARRAY_SIZE
problem, it should be fixed after above PR merged.
Great! This kind of Exception always confuses me with a hint TOO_LARGE_ARRAY_SIZE
.
Purpose
Changes
get_export_module
, the functionget_export_module_open_digger
defined inopen_digger.py
has more suitable default settings for open-digger.requirements.txt
.Notes
openDigger.quick.showAll
seems has bug with parameterrepoName
. I tried to query the activities and openranks of'apache/spark'
, however, it returns the data of an other repository in the memory. Any more, the function can easily trigger an exception TOO_LARGE_ARRAY_SIZE if a query without anylabel
constrants in options.