movoin / slacker Goto Github PK

We are a group of researchers from Yale University building a tool to finding bugs in configurations files. To evaluate the effectiveness of our tool, we randomly selected 1000 open source configuration files to verify and are requesting feedback on our error report. Your file https://raw.githubusercontent.com/movoin/slacker/267510b47b097e8b0e2881d0737a51ec5e3611db/module/mysql/5.6.15/conf/my.cnf was among those files. When we ran our tool your file, it reported the following potential errors.

[TYPE ERROR: for keyword "basedir"
Found value:[""]
In the training set we saw: String 37 times, Path 136 times, Size 0 times, Int 0 times, Bool 0 times

TYPE ERROR: for keyword "datadir"
Found value:[""]
In the training set we saw: String 37 times, Path 246 times, Size 0 times, Int 0 times, Bool 0 times

FINE GRAINED ERROR: Expected innodb-flush-log-at-trx-commit[mysqld] * innodb-log-file-size[mysqld] <= innodb-buffer-pool-size[mysqld]
Found values: ["innodb-buffer-pool-size[mysqld]=64m","innodb-flush-log-at-trx-commit[mysqld]=2","innodb-log-file-size[mysqld]=32m"]
In the training set we saw: ">=" 4 times, "<=" 77 times, "==" 0 times
]

The training set referenced in the report is taken from the industrial configuration files at https://github.com/tianyin/configuration_datasets. Note that even if your system is currently working, these bug may manifest itself only under large traffic loads or different system environments.

If you feel the any of above errors may indeed cause problems either on your system, or a different system, please comment on this issue report in the space below. This will help use to improve our tool. If you do not believe this is a potential bug, please feel free to close this issue. If possible we would appreciate your feedback before July 27.

If you would like find out more about how we detected these bug, you can find the open source tool at https://github.com/santolucito/ConfigV. For a quick overview of this tool, you can watch this video at https://youtu.be/plliEh-5MpM. If you have further questions, or would like to get involved with this project, feel free to reach out over email at [email protected].

Thank you for your time!