Improve some error messages

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
r
Domain
data

Research direction

Start by reproducing the listed failures through tab_rtauargus and the path, including the no-unsafe-cells, amount-table, missing names, additivity, duplicate-name, and file-permission cases. Trace where each underlying error is surfaced and document the expected actionable message for each condition; done means the misleading errors are replaced without hiding genuine failures.

Written by the indexing model from the issue text.

Description

enhancement

Some potential misleading error messages :

  • If there are no unsafe cells, a message to this effect is returned by tab_rtauargus, but also an error.
  • Error in [.data.frame(tabular, , c(explanatory_vars, value, freq, maxscore, : undefined columns selected – this error occurred with amount tables and went away when I commented out cost_var = “n_obs”. Oddly, it worked w/o error when I misspecified cost_var= “n_obs” as cost = “n_obs”.
  • Error: cannot allocate vector of size 361.8 Mb - list_explanatory_vars was missing its names
  • Error in if (sum(has_primary_secret) == 0) { : missing value where TRUE/FALSE needed - there was an additivity problem in the data. I have checks for this now.
  • Error in map(): … Cause by error in [[<-.data.frame: ! replacement has 0 rows, data has 28728 – duplicate name in list_tables so mismatch with list_explanatory_vars
  • This one occurred at , however, the inputs were fine, the TA inputs created by rtauargus were fine, but there was some issue with the file permissions of existing files. Error in read.table(file = file, header = header, sep = sep, quote = quote, : more columns than column names.
Dominant language
HTML
Stars
11
Forks
5
Avg merge
1m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InseeFrLab/rtauargus

All issues in InseeFrLab/rtauargus

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.