OpenDigger Biweekly Meeting: 2024-06-19

[Peng99999]

Description

Description

Meeting

🕣Time: 12:30~13:30, Wednesday of every two weeks 📞Tencent Meeting：146-764-173(link)

Agenda

Opendigger：

Bug：

1. The "issue-author-association" field in the cloud based clickhouse database only has the "COLLABORATOR" type, and querying other types cannot obtain results. #1579

if the "issue author association" field here represents the relationship between the user who opened the issue and the repository? If so, but I tried to query other relationships and did not get any results. However, the column "issue-comment-author-association" can reflect the actual situation very well. If "issue author association" represents the relationship between the user who opened the issue and the repository, then it should be able to reflect the actual relationship between the user who performed the behavior and the current repository, just like the column "issue_comment-author-association".

Sure, I found that this is a bug in the importer program, I will fix this soon and re-import the GitHub log recently. Thanks for the report. The re-import process has been started and will finish in about 3 days. The reason that all the value is COLLABORATOR is that this value is the default value for this column, but in the new data, NONE will be the default value instead to avoid ambiguity.

2. Python kernel building bug #1578

When building the python kernel, the image source of py2neo prompts that this version is not found. This version should now be 2021.2.4

If this python kernel is no longer used, the readme file should be modified to prompt users how to deploy opendigger in other ways.

[birdflyi]

Reason

The problem arises from the chaotic relationship between dependency files and readme files. Each kernel has its own requirements：

• the default js kernel dependencies: package.json
• the early python kernel dependencies: requirements_python.txt, with a README.md
• the python_v2 kernel dependencies: python_v2/requirements.txt, with a README.md
• the pycjs kernel dependencies: pycjs/requirements.txt

When we run Dockerfile in the root directory, we actually use the early pyhton kernal dependencies. python_v2/README.md should change the Dockerfile to point to its own python_v2/requirements.txt.

Temporary Solution

If you want to use python_v2 right away, change the Docker file and the python_v2 dependency file python_v2/requirements.txt like this: Note: continuumio/miniconda3 imported by Dockerfile in the root directory is too old for pandas==1.4.4.

Discussion

Should I write a README file and a Docker file for each kernel? Where should I put it?