-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make actions #41
Comments
Once you create the method mentioned in #40, you can proceed with this issue. |
@saledouble Please upload an example CSV file. |
The file: https://drive.google.com/file/d/1a3vsOZbloO5ybWSkwQQ4uok6ME6jYQw_/view?usp=sharing The file content:
|
@saledouble Why is there an extra line at the top of the file? |
Otherwise, looks nice. Are you sure these suggestions look good? |
This line is not from the project. I cleared the previous content and might not delete this line. The local file does not contain this line. I generate a new file and it looks fine: https://drive.google.com/file/d/1TKzJy-MsWGw4XPaFBu6sjZpV7O1_gRZi/view?usp=sharing |
Actually, I am not sure, but this is what I could get for now. |
Why are you unsure?
On Mon, 2018-07-02 at 14:34 -0700, Grace Tang wrote:
Are you sure these suggestions look good?
Actually, I am not sure, but this is what I could get for now.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub<#41 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AB9DP2ytMIlg7jOoVqUdbFPe_MBdAhR1ks5uCpHVgaJpZM4UvzTj>.
|
These suggestions for logging level are from DOI for enclosing methods which is one of the factors to influence the logging levels. I think we should consider more factors in the future. In the previous discussion, the reason that we use DOI model is that logging level is also a reflection of the developer's interests. But I am thinking about whether the interests in DOI model and logging level are same. The interests in DOI model of our project shows frequency that the developers interact with the enclosing method, which the logging level shows the interests of message content. Hence, we may need to analyze the message content and improve our model. |
Once you the (preliminary) mismatches, then take action. If there's no mismatch, no action needed, but you should record that in
log_actions.csv
as Action.NONE. If there's a mismatch, you need to fix the log level.First, let's document it action an action. Then, we'll do the transformation later.
┆Issue is synchronized with this Asana task
The text was updated successfully, but these errors were encountered: