Page MenuHomeSoftware Heritage

swh-storage: consider preventing bogus permission values
Closed, MigratedEdits Locked

Description

To avoid further occurrences of T686, we should consider whether we need to prevent bogus permissions values in the database.

We need to make sure that there is only a handful of valid values, as wild git repositories can contain weird things.

(the queries to check the data are running)

Event Timeline

softwareheritage=> select distinct(perms) from directory_entry_file;
 perms  
--------
  33200
  33248
  33276
  33261
 100644
  16877
 120000
  33152
  32768
  33188
  33216
  33225
  33060
      0
  40960
 295332
  33268
 100755
  33184
  33252
  33272
  33279
  33196
  33277
  33189
  16888
  16895
  33260
  33256
  33204
  16893
  41471
  16832
  33206
(34 rows)

....

zack moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Apr 5 2017, 2:04 PM