alibaba / alibaba/euler

BlockParser疑问

Open
#85 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
2.9k
Forks
553
PR merge metrics
No merged PRs in 30d

Description

![image](https://user-images.githubusercontent.com/33892888/55322094-f8b1fb80-54ad-11e9-8168-0ad4e7dcf4ff.png)
计算nodeInfoBytes时for循环用的是getNode_binary_feature_num

![image](https://user-images.githubusercontent.com/33892888/55322164-28610380-54ae-11e9-82b6-a087f2df3ce6.png)
写入时for循环用的是getEdge_binary_feature_num

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue identifies BlockParser and shows a discrepancy between getNode_binary_feature_num and getEdge_binary_feature_num in two loops, but names no file or test. Locate BlockParser and inspect the surrounding calculation and write paths first. Confirm whether the differing loops are intentional; done means documenting or correcting the behavior and adding a regression test if the repository has coverage for it.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.