Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 14

The DOI matches its Crossref record; 43 of the 43 references it cites were found in a registry or an index.

On the Temporal Relations between Logging and Code

Ding, Zishuo, Tang, Yiming, Li, Yang, Li, Heng, Shang, Weiyi·2023·2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE)

Abstract

Prior work shows that misleading logging texts (i.e., the textual descriptions in logging statements) can be counterproductive for developers during their use of logs. One of the most important types of information provided by logs is the temporal information of the recorded system behavior. For example, a logging text may use a perfective aspect to describe a fact that an important system event has finished. Although prior work has performed extensive studies on automated logging suggestions, few of these studies investigate the temporal relations between logging and code. In this work, we make the first attempt to comprehensively study the temporal relations between logging and its corresponding source code. In particular, we focus on two types of temporal relations: (1) logical temporal relations, which can be inferred from the execution order between the logging statement and the corresponding source code; and (2) semantic temporal relations, which can be inferred based on the semantic meaning of the logging text. We first perform qualitative analyses to study these two types of logging-code temporal relations and the inconsistency between them. As a result, we derive rules to detect these two types of temporal relations and their inconsistencies. Based on these rules, we propose a tool named TempoLo to automatically detect the issues of temporal inconsistencies between logging and code. Through an evaluation of four projects, we find that TempoLo can effectively detect t…

Overview

Integrity signals

Registry

Crossref · 10.1109/icse48619.2023.00079

Cites

43 of 43 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Research works printed but not linked: 7

  1. li, 0, Where shall we log? studying and suggesting logging locations in code blocks, 35th IEEE/ACM International Conference on Automated Software Engineering ASE 2020, 361
  2. kabinna, 2016, Logging Library Migrations: A Case Study for the Apache Software Foundation Projects, 2016 IEEE/ACM 13th Conference on Mining Software Repositories (MSR), 154
  3. barik, 2016, The Bones of the System: A Case Study of Logging and Telemetry at Microsoft, 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C) ICSE-C, 92
  4. honnibal, 2017, spaCy 2 Natural language understanding with Bloom embeddings convolutional neural networks and incremental parsing
  5. 2020, Mood & modality and dialogue sentiment to- I wards data science
  6. nicholas, 2017, JavaParser
  7. hamm, 2021, Tense and Aspect, The Stanford Encyclopedia of Philosophy

Cited by

See all 14

Metadata

Authors
Ding, Z., Tang, Y., Li, Y., Li, H., & Shang, W.
Venue
2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE)
Publisher
IEEE
Published
2023-05
Pages
843-854
Cited by
14
References
43

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.