issue_comments
9,947 rows sorted by created_at descending
This data as json, CSV (advanced)
Suggested facets: user, author_association, reactions
created_at (date) >1000 ✖
- 2021-03-22 66
- 2021-11-19 60
- 2022-11-16 59
- 2020-10-15 52
- 2020-09-22 51
- 2020-10-30 49
- 2022-10-26 47
- 2022-03-21 46
- 2020-12-18 43
- 2020-06-09 42
- 2022-10-27 42
- 2022-12-13 42
- 2020-06-18 41
- 2022-10-25 41
- 2020-10-20 40
- 2022-01-09 40
- 2022-06-14 40
- 2020-05-27 39
- 2021-11-16 39
- 2021-12-16 39
- 2020-12-30 38
- 2022-12-15 37
- 2023-03-08 37
- 2020-10-09 36
- 2021-11-20 36
- 2022-01-20 36
- 2022-03-19 36
- 2020-09-15 34
- 2021-11-29 34
- 2022-11-18 34
- 2023-05-08 34
- 2020-06-08 33
- 2021-01-04 33
- 2021-05-27 33
- 2022-02-06 33
- 2020-06-01 32
- 2022-03-05 32
- 2022-12-14 32
- 2019-06-24 31
- 2020-09-21 31
- 2021-08-13 31
- 2022-04-28 31
- 2022-08-27 31
- 2023-03-09 31
- 2019-06-23 30
- 2021-08-09 30
- 2022-11-14 30
- 2022-12-18 30
- 2018-04-16 29
- 2020-06-16 29
- 2020-10-16 29
- 2021-12-18 29
- 2020-02-14 28
- 2020-06-06 28
- 2020-11-24 28
- 2020-12-31 28
- 2021-01-03 28
- 2021-12-19 28
- 2022-02-02 28
- 2022-05-20 28
- 2022-12-16 28
- 2017-11-13 27
- 2017-11-14 27
- 2020-03-23 27
- 2020-05-30 27
- 2022-09-26 27
- 2022-10-24 27
- 2022-11-15 27
- 2022-11-30 27
- 2023-05-21 27
- 2023-05-25 27
- 2021-02-14 26
- 2021-06-16 26
- 2022-04-26 26
- 2022-07-15 26
- 2022-10-14 26
- 2020-06-29 25
- 2020-09-24 25
- 2020-12-29 25
- 2021-01-25 25
- 2021-06-03 25
- 2022-02-03 25
- 2022-03-15 25
- 2020-02-24 24
- 2020-04-18 24
- 2020-08-18 24
- 2020-09-14 24
- 2020-10-31 24
- 2022-08-14 24
- 2017-11-19 23
- 2020-05-03 23
- 2020-10-19 23
- 2020-10-29 23
- 2021-02-18 23
- 2021-11-14 23
- 2020-05-31 22
- 2020-09-30 22
- 2020-11-05 22
- 2020-11-30 22
- 2020-12-17 22
- 2022-09-15 22
- 2022-11-03 22
- 2022-11-29 22
- 2020-05-06 21
- 2020-05-28 21
- 2021-02-25 21
- 2021-06-19 21
- 2021-08-18 21
- 2021-12-17 21
- 2022-01-06 21
- 2022-03-11 21
- 2022-04-27 21
- 2022-10-30 21
- 2022-12-09 21
- 2017-11-16 20
- 2018-05-27 20
- 2018-07-10 20
- 2019-05-03 20
- 2019-05-11 20
- 2019-11-11 20
- 2020-03-24 20
- 2020-06-11 20
- 2020-06-23 20
- 2020-07-08 20
- 2020-09-07 20
- 2020-10-11 20
- 2020-10-23 20
- 2021-01-06 20
- 2021-02-20 20
- 2021-03-04 20
- 2021-08-24 20
- 2022-01-26 20
- 2022-05-02 20
- 2022-09-06 20
- 2023-02-07 20
- 2019-11-04 19
- 2020-03-25 19
- 2020-05-02 19
- 2020-08-12 19
- 2021-10-24 19
- 2021-12-11 19
- 2022-01-08 19
- 2022-02-18 19
- 2022-03-07 19
- 2022-08-23 19
- 2018-04-09 18
- 2018-05-22 18
- 2019-05-23 18
- 2019-06-13 18
- 2019-06-22 18
- 2020-03-26 18
- 2020-04-05 18
- 2020-05-01 18
- 2020-05-04 18
- 2020-05-05 18
- 2020-06-03 18
- 2020-06-13 18
- 2020-07-01 18
- 2020-09-23 18
- 2020-10-21 18
- 2021-01-01 18
- 2021-05-23 18
- 2021-05-29 18
- 2021-08-10 18
- 2022-01-13 18
- 2022-02-07 18
- 2022-10-07 18
- 2017-10-24 17
- 2018-05-24 17
- 2018-06-21 17
- 2020-06-28 17
- 2020-08-28 17
- 2020-12-09 17
- 2021-02-12 17
- 2021-03-23 17
- 2021-03-29 17
- 2021-08-19 17
- 2021-12-23 17
- 2022-09-05 17
- 2022-09-07 17
- 2022-09-27 17
- 2023-06-29 17
- 2017-10-23 16
- 2017-11-11 16
- 2018-05-28 16
- 2019-03-15 16
- 2020-04-27 16
- 2020-05-08 16
- 2020-05-10 16
- 2020-08-11 16
- 2020-08-16 16
- 2020-10-14 16
- 2020-11-29 16
- 2020-12-03 16
- 2021-03-27 16
- 2021-06-05 16
- 2021-07-10 16
- 2021-07-31 16
- 2021-11-15 16
- 2022-03-20 16
- 2022-11-01 16
- 2022-11-11 16
- 2022-12-06 16
- 2017-11-15 15
- 2018-05-16 15
- 2018-06-18 15
- 2019-10-14 15
- 2020-04-29 15
- 2020-05-11 15
- 2020-06-05 15
- 2020-06-10 15
- 2020-06-12 15
- 2020-08-09 15
- 2020-09-17 15
- 2020-10-22 15
- 2021-01-05 15
- 2021-02-19 15
- 2021-05-31 15
- 2021-06-26 15
- 2022-01-11 15
- 2017-12-10 14
- 2019-03-17 14
- 2019-07-05 14
- 2020-02-04 14
- 2020-06-07 14
- 2020-09-12 14
- 2020-10-08 14
- 2020-10-25 14
- 2020-11-06 14
- 2020-12-16 14
- 2021-08-01 14
- 2021-08-28 14
- 2022-01-21 14
- 2022-02-05 14
- 2022-11-04 14
- 2022-12-31 14
- 2023-04-11 14
- 2023-04-27 14
- 2017-11-17 13
- 2018-03-28 13
- 2018-04-08 13
- 2019-02-24 13
- 2019-07-08 13
- 2019-11-12 13
- 2019-11-13 13
- 2020-02-25 13
- 2020-05-20 13
- 2020-09-03 13
- 2020-10-10 13
- 2021-04-03 13
- 2021-06-06 13
- 2021-12-20 13
- 2022-03-06 13
- 2022-04-24 13
- 2022-06-13 13
- 2017-10-25 12
- 2017-11-12 12
- 2018-04-17 12
- 2019-04-12 12
- 2019-10-16 12
- 2019-11-09 12
- 2020-02-23 12
- 2020-04-16 12
- 2020-04-26 12
- 2020-04-30 12
- 2020-10-17 12
- 2020-12-04 12
- 2020-12-14 12
- 2021-02-26 12
- 2021-05-19 12
- 2021-06-15 12
- 2021-07-16 12
- 2022-01-14 12
- 2022-12-02 12
- 2022-12-08 12
- 2023-01-25 12
- 2023-07-08 12
- 2017-12-07 11
- 2018-05-29 11
- 2018-05-31 11
- 2018-07-24 11
- 2019-05-16 11
- 2019-06-30 11
- 2019-10-11 11
- 2019-10-17 11
- 2019-11-08 11
- 2020-02-22 11
- 2020-06-02 11
- 2020-06-30 11
- 2020-07-18 11
- 2020-07-27 11
- 2020-08-30 11
- 2020-09-28 11
- 2020-11-02 11
- 2020-11-12 11
- 2020-12-12 11
- 2021-02-27 11
- 2021-04-02 11
- 2021-04-04 11
- 2021-04-05 11
- 2021-06-02 11
- 2021-06-18 11
- 2021-08-12 11
- 2021-12-10 11
- 2021-12-22 11
- 2022-01-10 11
- 2022-02-09 11
- 2022-09-14 11
- 2022-12-03 11
- 2023-04-06 11
- 2018-04-14 10
- 2018-05-23 10
- 2018-06-15 10
- 2018-06-16 10
- 2019-04-29 10
- 2019-07-07 10
- 2019-07-19 10
- 2019-11-03 10
- 2019-11-26 10
- 2020-04-02 10
- 2020-06-24 10
- 2020-07-26 10
- 2020-08-21 10
- 2020-09-08 10
- 2021-05-24 10
- 2021-08-02 10
- 2021-08-17 10
- 2022-01-12 10
- 2022-01-19 10
- 2022-03-23 10
- 2022-12-17 10
- 2023-01-09 10
- 2023-04-13 10
- 2023-06-25 10
- 2017-12-09 9
- 2018-04-15 9
- 2018-04-20 9
- 2018-11-05 9
- 2019-05-28 9
- 2019-06-25 9
- 2020-02-13 9
- 2020-03-08 9
- 2020-03-20 9
- 2020-04-06 9
- 2020-04-13 9
- 2020-04-28 9
- 2020-05-07 9
- 2020-07-24 9
- 2020-09-02 9
- 2020-12-19 9
- 2021-01-02 9
- 2021-01-22 9
- 2021-02-02 9
- 2021-03-10 9
- 2021-03-20 9
- 2021-05-28 9
- 2021-06-22 9
- 2021-07-08 9
- 2021-07-15 9
- 2021-12-12 9
- 2022-02-04 9
- 2022-03-08 9
- 2022-04-13 9
- 2022-05-03 9
- 2022-05-17 9
- 2022-06-21 9
- 2022-07-05 9
- 2022-07-18 9
- 2022-08-18 9
- 2022-09-28 9
- 2023-01-11 9
- 2023-01-21 9
- 2023-02-06 9
- 2017-11-29 8
- 2017-11-30 8
- 2018-03-27 8
- 2018-03-30 8
- 2018-05-25 8
- 2019-05-19 8
- 2019-05-21 8
- 2019-05-25 8
- 2019-05-29 8
- 2019-06-15 8
- 2019-07-20 8
- 2019-10-21 8
- 2020-01-31 8
- 2020-02-16 8
- 2020-03-16 8
- 2020-04-10 8
- 2020-04-21 8
- 2020-06-14 8
- 2020-06-21 8
- 2020-07-02 8
- 2020-07-31 8
- 2020-08-19 8
- 2020-10-01 8
- 2020-10-12 8
- 2021-01-12 8
- 2021-01-24 8
- 2021-02-15 8
- 2021-02-23 8
- 2021-06-07 8
- 2021-07-02 8
- 2021-07-11 8
- 2021-09-23 8
- 2021-10-08 8
- 2021-10-13 8
- 2021-12-14 8
- 2022-01-07 8
- 2022-02-16 8
- 2022-03-24 8
- 2022-03-25 8
- 2022-04-11 8
- 2022-06-20 8
- 2022-08-21 8
- 2022-09-02 8
- 2022-10-18 8
- 2022-10-28 8
- 2023-01-29 8
- 2023-03-22 8
- 2023-03-26 8
- 2023-05-07 8
- 2017-11-09 7
- 2017-11-20 7
- 2017-11-21 7
- 2018-06-17 7
- 2018-07-26 7
- 2019-01-28 7
- 2019-05-02 7
- 2019-06-09 7
- 2019-06-18 7
- 2019-10-07 7
- 2019-10-18 7
- 2019-10-30 7
- 2020-01-29 7
- 2020-02-27 7
- 2020-03-06 7
- 2020-03-21 7
- 2020-03-31 7
- 2020-04-01 7
- 2020-04-15 7
- 2020-04-24 7
- 2020-05-15 7
- 2020-05-21 7
- 2020-05-29 7
- 2020-06-20 7
- 2020-07-06 7
- 2020-08-29 7
- 2020-09-16 7
- 2020-10-24 7
- 2020-10-27 7
- 2020-11-04 7
- 2020-11-07 7
- 2021-01-18 7
- 2021-02-11 7
- 2021-02-22 7
- 2021-05-17 7
- 2021-07-14 7
- 2021-07-25 7
- 2021-07-30 7
- 2021-08-04 7
- 2021-08-14 7
- 2021-08-25 7
- 2021-09-21 7
- 2021-09-22 7
- 2021-11-17 7
- 2021-11-30 7
- 2021-12-01 7
- 2021-12-07 7
- 2021-12-13 7
- 2022-02-08 7
- 2022-03-13 7
- 2022-03-14 7
- 2022-03-17 7
- 2022-04-08 7
- 2022-04-21 7
- 2022-09-01 7
- 2022-09-09 7
- 2022-09-29 7
- 2022-10-08 7
- 2022-11-02 7
- 2022-11-12 7
- 2023-03-10 7
- 2017-10-26 6
- 2017-11-22 6
- 2017-11-23 6
- 2017-12-08 6
- 2018-04-03 6
- 2018-04-18 6
- 2018-04-26 6
- 2018-05-12 6
- 2018-05-13 6
- 2018-05-14 6
- 2018-05-21 6
- 2018-05-26 6
- 2018-06-04 6
- 2018-07-12 6
- 2019-04-13 6
- 2019-07-03 6
- 2019-07-09 6
- 2019-07-11 6
- 2019-07-14 6
- 2019-09-02 6
- 2019-11-01 6
- 2019-11-07 6
- 2019-12-18 6
- 2019-12-22 6
- 2020-02-15 6
- 2020-03-05 6
- 2020-03-14 6
- 2020-03-22 6
- 2020-04-23 6
- 2020-06-22 6
- 2020-06-27 6
- 2020-09-01 6
- 2020-09-09 6
- 2020-10-06 6
- 2020-10-26 6
- 2020-12-13 6
- 2021-01-15 6
- 2021-03-09 6
- 2021-03-12 6
- 2021-03-21 6
- 2021-03-28 6
- 2021-06-01 6
- 2021-06-11 6
- 2021-07-22 6
- 2021-08-08 6
- 2021-08-20 6
- 2021-08-23 6
- 2021-09-08 6
- 2021-10-07 6
- 2021-10-14 6
- 2021-11-28 6
- 2022-01-25 6
- 2022-03-02 6
- 2022-03-22 6
- 2022-04-25 6
- 2022-07-10 6
- 2022-07-20 6
- 2022-08-02 6
- 2022-09-23 6
- 2022-10-02 6
- 2022-10-12 6
- 2022-10-31 6
- 2022-11-17 6
- 2023-01-07 6
- 2023-01-17 6
- 2023-03-06 6
- 2023-03-20 6
- 2023-05-26 6
- 2023-07-14 6
- 2017-11-18 5
- 2017-11-27 5
- 2018-05-17 5
- 2018-05-30 5
- 2018-06-05 5
- 2018-07-11 5
- 2018-08-11 5
- 2018-09-19 5
- 2019-03-19 5
- 2019-06-28 5
- 2019-07-23 5
- 2019-07-24 5
- 2019-11-14 5
- 2019-11-27 5
- 2019-12-26 5
- 2020-01-30 5
- 2020-02-28 5
- 2020-03-27 5
- 2020-03-30 5
- 2020-04-17 5
- 2020-05-25 5
- 2020-06-19 5
- 2020-06-26 5
- 2020-07-30 5
- 2020-08-10 5
- 2020-08-15 5
- 2020-10-28 5
- 2020-11-13 5
- 2020-11-28 5
- 2020-12-01 5
- 2020-12-05 5
- 2020-12-08 5
- 2020-12-22 5
- 2020-12-23 5
- 2021-01-07 5
- 2021-01-17 5
- 2021-01-28 5
- 2021-01-29 5
- 2021-03-08 5
- 2021-03-18 5
- 2021-03-31 5
- 2021-06-12 5
- 2021-06-13 5
- 2021-06-14 5
- 2021-06-25 5
- 2021-08-05 5
- 2021-08-06 5
- 2021-08-07 5
- 2021-09-13 5
- 2021-12-06 5
- 2021-12-15 5
- 2022-02-15 5
- 2022-03-16 5
- 2022-03-26 5
- 2022-03-30 5
- 2022-04-22 5
- 2022-04-30 5
- 2022-07-27 5
- 2022-08-13 5
- 2022-08-28 5
- 2022-08-30 5
- 2022-08-31 5
- 2022-09-17 5
- 2022-09-22 5
- 2022-10-05 5
- 2022-10-13 5
- 2022-11-13 5
- 2022-12-01 5
- 2023-02-08 5
- 2023-02-22 5
- 2023-03-12 5
- 2023-03-29 5
- 2023-04-12 5
- 2023-07-17 5
- 2017-11-10 4
- 2017-12-01 4
- 2017-12-04 4
- 2017-12-05 4
- 2018-04-11 4
- 2018-04-12 4
- 2018-06-28 4
- 2018-06-29 4
- 2018-07-13 4
- 2018-07-14 4
- 2018-07-18 4
- 2019-01-02 4
- 2019-01-17 4
- 2019-04-07 4
- 2019-04-11 4
- 2019-05-05 4
- 2019-05-09 4
- 2019-06-04 4
- 2019-07-04 4
- 2019-07-06 4
- 2019-07-22 4
- 2019-07-28 4
- 2019-08-17 4
- 2019-08-23 4
- 2019-09-03 4
- 2019-09-04 4
- 2019-10-13 4
- 2019-11-18 4
- 2019-11-19 4
- 2019-12-08 4
- 2019-12-27 4
- 2020-02-01 4
- 2020-02-29 4
- 2020-04-22 4
- 2020-05-12 4
- 2020-06-17 4
- 2020-07-16 4
- 2020-08-24 4
- 2020-08-25 4
- 2020-09-11 4
- 2020-09-18 4
- 2020-09-20 4
- 2020-10-05 4
- 2020-10-07 4
- 2020-11-03 4
- 2020-11-15 4
- 2020-11-21 4
- 2020-12-02 4
- 2020-12-21 4
- 2020-12-24 4
- 2021-01-26 4
- 2021-03-05 4
- 2021-03-07 4
- 2021-04-29 4
- 2021-06-20 4
- 2021-06-23 4
- 2021-07-07 4
- 2021-07-18 4
- 2021-08-03 4
- 2021-08-26 4
- 2021-09-07 4
- 2021-10-18 4
- 2021-10-19 4
- 2021-10-30 4
- 2021-11-21 4
- 2021-11-22 4
- 2021-12-08 4
- 2022-02-11 4
- 2022-03-01 4
- 2022-03-18 4
- 2022-05-16 4
- 2022-05-27 4
- 2022-06-22 4
- 2022-07-02 4
- 2022-07-17 4
- 2022-08-15 4
- 2022-08-20 4
- 2022-09-19 4
- 2022-09-21 4
- 2022-10-01 4
- 2022-10-06 4
- 2022-11-19 4
- 2022-11-23 4
- 2023-01-02 4
- 2023-02-10 4
- 2023-06-14 4
- 2023-07-02 4
- 2023-07-09 4
- 2017-11-24 3
- 2017-12-02 3
- 2018-03-21 3
- 2018-04-13 3
- 2018-04-22 3
- 2018-05-03 3
- 2018-05-06 3
- 2018-05-11 3
- 2018-05-18 3
- 2018-06-20 3
- 2018-07-31 3
- 2018-08-12 3
- 2018-08-16 3
- 2018-08-28 3
- 2018-11-19 3
- 2019-01-10 3
- 2019-01-13 3
- 2019-01-18 3
- 2019-02-06 3
- 2019-02-23 3
- 2019-04-15 3
- 2019-04-18 3
- 2019-05-01 3
- 2019-05-13 3
- 2019-05-14 3
- 2019-05-20 3
- 2019-05-26 3
- 2019-05-27 3
- 2019-06-08 3
- 2019-06-11 3
- 2019-06-14 3
- 2019-07-12 3
- 2019-07-15 3
- 2019-09-14 3
- 2019-10-02 3
- 2019-10-06 3
- 2019-11-02 3
- 2019-11-15 3
- 2019-11-22 3
- 2019-12-03 3
- 2019-12-09 3
- 2020-01-10 3
- 2020-03-01 3
- 2020-03-02 3
- 2020-03-03 3
- 2020-03-09 3
- 2020-05-19 3
- 2020-05-26 3
- 2020-06-15 3
- 2020-07-21 3
- 2020-07-22 3
- 2020-08-01 3
- 2020-08-13 3
- 2020-10-02 3
- 2020-11-01 3
- 2020-11-11 3
- 2020-11-22 3
- 2020-12-10 3
- 2021-01-09 3
- 2021-02-05 3
- 2021-02-06 3
- 2021-03-01 3
- 2021-03-13 3
- 2021-03-14 3
- 2021-03-19 3
- 2021-03-25 3
- 2021-04-20 3
- 2021-04-24 3
- 2021-04-28 3
- 2021-05-12 3
- 2021-05-18 3
- 2021-05-21 3
- 2021-06-09 3
- 2021-06-17 3
- 2021-06-27 3
- 2021-07-13 3
- 2021-07-26 3
- 2021-07-28 3
- 2021-09-04 3
- 2021-10-02 3
- 2021-10-12 3
- 2021-10-16 3
- 2021-10-28 3
- 2021-12-02 3
- 2022-01-15 3
- 2022-01-28 3
- 2022-02-23 3
- 2022-02-24 3
- 2022-03-12 3
- 2022-03-28 3
- 2022-03-29 3
- 2022-04-12 3
- 2022-04-14 3
- 2022-04-29 3
- 2022-07-07 3
- 2022-08-17 3
- 2022-09-16 3
- 2022-09-20 3
- 2022-09-24 3
- 2022-10-03 3
- 2022-10-11 3
- 2022-10-29 3
- 2022-11-20 3
- 2022-12-23 3
- 2023-01-20 3
- 2023-01-26 3
- 2023-01-28 3
- 2023-03-11 3
- 2023-03-18 3
- 2023-03-24 3
- 2023-03-30 3
- 2023-03-31 3
- 2023-04-01 3
- 2023-04-05 3
- 2023-04-15 3
- 2023-05-09 3
- 2023-05-12 3
- 2023-05-15 3
- 2023-06-26 3
- 2023-07-18 3
- 2017-10-27 2
- 2017-11-06 2
- 2017-11-07 2
- 2017-11-26 2
- 2017-12-03 2
- 2018-01-09 2
- 2018-04-10 2
- 2018-04-19 2
- 2018-04-21 2
- 2018-05-04 2
- 2018-05-05 2
- 2018-05-15 2
- 2018-06-07 2
- 2018-08-06 2
- 2019-01-03 2
- 2019-01-11 2
- 2019-03-14 2
- 2019-03-20 2
- 2019-03-28 2
- 2019-03-31 2
- 2019-04-14 2
- 2019-04-21 2
- 2019-05-04 2
- 2019-05-24 2
- 2019-06-05 2
- 2019-06-06 2
- 2019-06-16 2
- 2019-07-16 2
- 2019-07-18 2
- 2019-07-26 2
- 2019-08-03 2
- 2019-08-31 2
- 2019-09-08 2
- 2019-10-10 2
- 2019-10-12 2
- 2019-10-24 2
- 2019-10-25 2
- 2019-10-27 2
- 2019-11-06 2
- 2019-11-10 2
- 2019-11-23 2
- 2019-11-29 2
- 2019-11-30 2
- 2019-12-01 2
- 2019-12-04 2
- 2019-12-31 2
- 2020-01-05 2
- 2020-01-06 2
- 2020-01-12 2
- 2020-01-19 2
- 2020-01-21 2
- 2020-02-03 2
- 2020-02-11 2
- 2020-02-12 2
- 2020-03-10 2
- 2020-03-17 2
- 2020-03-28 2
- 2020-04-04 2
- 2020-04-14 2
- 2020-04-19 2
- 2020-06-04 2
- 2020-07-03 2
- 2020-07-07 2
- 2020-07-09 2
- 2020-07-12 2
- 2020-07-17 2
- 2020-07-25 2
- 2020-07-29 2
- 2020-09-26 2
- 2020-09-27 2
- 2020-09-29 2
- 2020-11-09 2
- 2020-11-16 2
- 2020-11-17 2
- 2020-11-20 2
- 2020-11-25 2
- 2020-12-20 2
- 2020-12-27 2
- 2020-12-28 2
- 2021-01-08 2
- 2021-01-11 2
- 2021-01-14 2
- 2021-01-19 2
- 2021-01-30 2
- 2021-02-01 2
- 2021-02-03 2
- 2021-02-07 2
- 2021-02-08 2
- 2021-02-17 2
- 2021-02-28 2
- 2021-03-03 2
- 2021-03-15 2
- 2021-03-24 2
- 2021-04-12 2
- 2021-04-14 2
- 2021-04-18 2
- 2021-05-11 2
- 2021-05-26 2
- 2021-06-10 2
- 2021-06-21 2
- 2021-06-28 2
- 2021-07-09 2
- 2021-07-19 2
- 2021-07-24 2
- 2021-08-16 2
- 2021-08-22 2
- 2021-09-14 2
- 2021-09-28 2
- 2021-09-29 2
- 2021-10-05 2
- 2021-10-09 2
- 2021-10-20 2
- 2021-10-22 2
- 2021-10-26 2
- 2021-10-27 2
- 2021-11-01 2
- 2021-11-03 2
- 2021-11-13 2
- 2021-11-18 2
- 2021-11-23 2
- 2021-11-25 2
- 2021-12-04 2
- 2021-12-24 2
- 2021-12-26 2
- 2021-12-27 2
- 2022-02-13 2
- 2022-02-17 2
- 2022-03-09 2
- 2022-04-10 2
- 2022-05-12 2
- 2022-05-31 2
- 2022-06-15 2
- 2022-06-23 2
- 2022-06-28 2
- 2022-07-01 2
- 2022-07-04 2
- 2022-07-19 2
- 2022-07-22 2
- 2022-07-28 2
- 2022-08-16 2
- 2022-09-03 2
- 2022-09-08 2
- 2022-09-25 2
- 2022-10-04 2
- 2022-10-15 2
- 2022-11-10 2
- 2022-12-10 2
- 2023-01-05 2
- 2023-01-06 2
- 2023-01-10 2
- 2023-01-19 2
- 2023-01-22 2
- 2023-01-23 2
- 2023-01-24 2
- 2023-02-05 2
- 2023-03-19 2
- 2023-03-21 2
- 2023-04-07 2
- 2023-04-16 2
- 2023-05-02 2
- 2023-05-03 2
- 2023-05-22 2
- 2023-07-01 2
- 2023-07-03 2
- 2023-07-10 2
- 2017-10-30 1
- …
id | html_url | issue_url | node_id | user | created_at ▲ | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1641082395 | https://github.com/simonw/datasette/issues/2104#issuecomment-1641082395 | https://api.github.com/repos/simonw/datasette/issues/2104 | IC_kwDOBm6k_c5h0O4b | asg017 15178711 | 2023-07-18T22:41:37Z | 2023-07-18T22:41:37Z | CONTRIBUTOR | For filtering virtual table's "shadow tables" (ex the FTS5 _content and most the spatialite tables), you can use `pragma_table_list` (first appeared in SQLite 3.37 (2021-11-27), which has a `type` column that calls out `type="shadow"` tables https://www.sqlite.org/pragma.html#pragma_table_list | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Tables starting with an underscore should be treated as hidden 1808215339 | |
1640826795 | https://github.com/simonw/sqlite-utils/issues/433#issuecomment-1640826795 | https://api.github.com/repos/simonw/sqlite-utils/issues/433 | IC_kwDOCGYnMM5hzQer | J450n-4-W 76528036 | 2023-07-18T19:08:50Z | 2023-07-18T19:08:50Z | NONE | Came here to report this, but instead I'll confirm the issue across two terminal emulators (Gnome Terminal and Alacritty) on Pop_OS! 22.04 (currently based on Ubuntu/Gnome). Also messes up the formatting of the terminal. Can also confirm that reset fixes it until the next sqlite-utils command. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | CLI eats my cursor 1239034903 | |
1640064620 | https://github.com/simonw/datasette/issues/2102#issuecomment-1640064620 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hwWZs | simonw 9599 | 2023-07-18T11:47:21Z | 2023-07-18T11:47:21Z | OWNER | I think I've figured out the problem here. The question being asked is "can this actor access this resource, which is within this database within this instance". The answer to this question needs to consider the full set of questions at once - yes they can access within this instance IF they have access to the specified table and that's the table being asked about. But the questions are currently being asked independently, which means the plugin hook acting on `view-instance` can't see that the answer here should be yes because it's actually about a table that the actor has explicit permission to view. So I think I may need to redesign the plugin hook to always see the full hierarchy of checks, not just a single check at a time. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1638926655 | https://github.com/simonw/sqlite-utils/issues/567#issuecomment-1638926655 | https://api.github.com/repos/simonw/sqlite-utils/issues/567 | IC_kwDOCGYnMM5hsAk_ | simonw 9599 | 2023-07-17T21:42:37Z | 2023-07-17T21:42:37Z | OWNER | I really like this. I'm also interested in: - Plugins that make new custom SQL functions available - similar to this Datasette hook: https://docs.datasette.io/en/stable/plugin_hooks.html#prepare-connection-conn-database-datasette - Plugins that register functions that can be used as recipes for `sqlite-utils convert` https://sqlite-utils.datasette.io/en/stable/cli.html#sqlite-utils-convert-recipes The upload-data-to-Datasette problem is planned to be solved by a future version of https://github.com/simonw/dclient | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Plugin system 1801394744 | |
1638910473 | https://github.com/simonw/sqlite-utils/issues/567#issuecomment-1638910473 | https://api.github.com/repos/simonw/sqlite-utils/issues/567 | IC_kwDOCGYnMM5hr8oJ | asg017 15178711 | 2023-07-17T21:27:41Z | 2023-07-17T21:27:41Z | NONE | Another use-case: I want to make a `sqlite-utils` plugin that'll help me insert data into Datasette. ```bash sqlite-utils insert-datasette \ --token $DATASETTE_API_KEY \ https://latest.datasette.io/fixtures/my-table \ 'select ...' ``` This could also be a datasette plugin (ex `datasette upload-data ...`, but you can also think of `sqlite-utils` plugins that upload to S3, a postgres table, other DBMS's, etc.) | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Plugin system 1801394744 | |
1638567228 | https://github.com/simonw/datasette/issues/2102#issuecomment-1638567228 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hqo08 | simonw 9599 | 2023-07-17T17:24:19Z | 2023-07-17T17:25:12Z | OWNER | Confirmed that this is an issue with regular Datasette signed tokens as well. I created one on https://latest.datasette.io/-/create-token with these details: ```json { "_r": { "r": { "fixtures": { "sortable": [ "vt" ] } } }, "a": "root", "d": 3600, "t": 1689614483 } ``` Run like this: ``` curl -H 'Authorization: Bearer dstok_eyJhIjoicm9vdCIsInQiOjE2ODk2MTQ0ODMsImQiOjM2MDAsIl9yIjp7InIiOnsiZml4dHVyZXMiOnsic29ydGFibGUiOlsidnQiXX19fX0.n-VGxxawz1Q0WK7sqLfhXUgcvY0' \ https://latest.datasette.io/fixtures/sortable.json ``` Returned an HTML Forbidden page: ```html <!DOCTYPE html> <html> <head> <title>Forbidden</title> <link rel="stylesheet" href="/-/static/app.css?d59929"> ... ``` Same token againts `/-/actor.json` returns: ```json { "actor": { "id": "root", "token": "dstok", "_r": { "r": { "fixtures": { "sortable": [ "vt" ] } } }, "token_expires": 1689618083 } } ``` Reminder - `"_r"` means restrict, `"r"` means resource. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1638552567 | https://github.com/simonw/datasette/issues/2104#issuecomment-1638552567 | https://api.github.com/repos/simonw/datasette/issues/2104 | IC_kwDOBm6k_c5hqlP3 | simonw 9599 | 2023-07-17T17:14:20Z | 2023-07-17T17:14:20Z | OWNER | Relevant code: https://github.com/simonw/datasette/blob/0f7192b6154edb576c41b55bd3f2a3f53e5f436a/datasette/database.py#L391-L451 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Tables starting with an underscore should be treated as hidden 1808215339 | |
1637293044 | https://github.com/simonw/datasette/issues/670#issuecomment-1637293044 | https://api.github.com/repos/simonw/datasette/issues/670 | IC_kwDOBm6k_c5hlxv0 | yairlenga 4863782 | 2023-07-17T02:23:32Z | 2023-07-17T02:23:32Z | NONE | Is there any working version of datasette/postgresql ? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Prototoype for Datasette on PostgreSQL 564833696 | |
1636134091 | https://github.com/simonw/datasette/issues/2087#issuecomment-1636134091 | https://api.github.com/repos/simonw/datasette/issues/2087 | IC_kwDOBm6k_c5hhWzL | adarshp 653549 | 2023-07-14T17:02:03Z | 2023-07-14T17:02:03Z | NONE | @asg017 - the docs say that the autodetection only occurs in configuration directory mode. I for one would also be interested in the `--settings settings.json` feature. For context, I am developing a large database for use with Datasette, but the database lives in a different network volume than my source code, since the volume in which my source code lives is aggressively backed up, while the location where the database lives is meant for temporary files and is not as aggressively backed up (since the backups would get unreasonably large). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--settings settings.json` option 1765870617 | |
1636093730 | https://github.com/simonw/datasette/issues/2102#issuecomment-1636093730 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hhM8i | simonw 9599 | 2023-07-14T16:26:27Z | 2023-07-14T16:32:49Z | OWNER | Here's that crucial comment: > If _r is defined then we use those to further restrict the actor. > >Crucially, we only use this to say NO (return False) - we never use it to return YES (True) because that might over-ride other restrictions placed on this actor So that's why I implemented it like this. The goal here is to be able to issue a token which can't do anything _more_ than the actor it is associated with, but CAN be configured to do less. So I think the solution here is for the `_r` checking code to perhaps implement its own view cascade logic - it notices if you have `view-table` and consequently fails to block `view-table` and `view-instance`. I'm not sure that's going to work though - would that mean that granting `view-table` grants `view-database` in a surprising and harmful way? Maybe that's OK: if you have `view-database` but permission checks fail for individual tables and queries you shouldn't be able to see a thing that you shouldn't. Need to verify that though. Also, do `Permission` instances have enough information to implement this kind of cascade without hard-coding anything? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1636053060 | https://github.com/simonw/datasette/issues/2102#issuecomment-1636053060 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hhDBE | simonw 9599 | 2023-07-14T15:51:36Z | 2023-07-14T16:14:05Z | OWNER | This might only be an issue with the code that checks `_r` on actors. https://github.com/simonw/datasette/blob/0f7192b6154edb576c41b55bd3f2a3f53e5f436a/datasette/default_permissions.py#L185-L222 Added in https://github.com/simonw/datasette/commit/bcc781f4c50a8870e3389c4e60acb625c34b0317 - refs: - #1855 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1636042066 | https://github.com/simonw/datasette/issues/2102#issuecomment-1636042066 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hhAVS | simonw 9599 | 2023-07-14T15:41:54Z | 2023-07-14T15:42:32Z | OWNER | I tried some code spelunking and came across https://github.com/simonw/datasette/commit/d6e03b04302a0852e7133dc030eab50177c37be7 which says: > - If you have table permission but not database permission you can now view the table page Refs: - #832 Which suggests that my initial design decision wasn't what appears to be implemented today. Needs more investigation. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1636040164 | https://github.com/simonw/datasette/issues/2102#issuecomment-1636040164 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hg_3k | simonw 9599 | 2023-07-14T15:40:21Z | 2023-07-14T15:40:21Z | OWNER | Relevant code: https://github.com/simonw/datasette/blob/0f7192b6154edb576c41b55bd3f2a3f53e5f436a/datasette/app.py#L822-L855 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1636036312 | https://github.com/simonw/datasette/issues/2102#issuecomment-1636036312 | https://api.github.com/repos/simonw/datasette/issues/2102 | IC_kwDOBm6k_c5hg-7Y | simonw 9599 | 2023-07-14T15:37:14Z | 2023-07-14T15:37:14Z | OWNER | I think I made this decision because I was thinking about default deny: obviously if a user has been denied access to a database. It doesn't make sense that they could access tables within it. But now that I am spending more time with authentication tokens, which default to denying everything, except for the things that you have explicitly listed, this policy, no longer makes as much sense. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | API tokens with view-table but not view-database/view-instance cannot access the table 1805076818 | |
1634443907 | https://github.com/simonw/datasette/issues/2101#issuecomment-1634443907 | https://api.github.com/repos/simonw/datasette/issues/2101 | IC_kwDOBm6k_c5ha6KD | simonw 9599 | 2023-07-13T15:24:17Z | 2023-07-13T15:24:17Z | OWNER | https://github.com/simonw/datasette/blob/0f7192b6154edb576c41b55bd3f2a3f53e5f436a/datasette/views/table.py#L486-L506 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | alter: true support for JSON write API 1803264272 | |
1632867333 | https://github.com/simonw/datasette/pull/2052#issuecomment-1632867333 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5hU5QF | codecov[bot] 22429695 | 2023-07-12T16:38:27Z | 2023-07-12T16:38:27Z | NONE | ## [Codecov](https://app.codecov.io/gh/simonw/datasette/pull/2052?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) Report Patch coverage has no change and project coverage change: **`-0.02`** :warning: > Comparison is base [(`3feed1f`)](https://app.codecov.io/gh/simonw/datasette/commit/3feed1f66e2b746f349ee56970a62246a18bb164?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 92.46% compared to head [(`cf5a9df`)](https://app.codecov.io/gh/simonw/datasette/pull/2052?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 92.45%. <details><summary>Additional details and impacted files</summary> ```diff @@ Coverage Diff @@ ## main #2052 +/- ## ========================================== - Coverage 92.46% 92.45% -0.02% ========================================== Files 38 39 +1 Lines 5750 5802 +52 ========================================== + Hits 5317 5364 +47 - Misses 433 438 +5 ``` [see 6 files with indirect coverage changes](https://app.codecov.io/gh/simonw/datasette/pull/2052/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) </details> [:umbrella: View full report in Codecov by Sentry](https://app.codecov.io/gh/simonw/datasette/pull/2052?src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison). :loudspeaker: Do you have feedback about the report comment? [Let us know in this issue](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1630776144 | https://github.com/simonw/datasette/pull/2052#issuecomment-1630776144 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5hM6tQ | hydrosquall 9020979 | 2023-07-11T12:54:03Z | 2023-07-11T12:54:03Z | NONE | Thanks for the review and the code pointers @simonw - I've made the suggested edits, fixed the renamed variable, and confirmed that the panels still render on the `table` and `database` views. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1629337927 | https://github.com/simonw/datasette/pull/2052#issuecomment-1629337927 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5hHblH | simonw 9599 | 2023-07-10T16:43:38Z | 2023-07-10T16:44:23Z | OWNER | I tried running this locally just now. I made one edit: ```diff diff --git a/demos/plugins/example_js_manager_plugins.py b/demos/plugins/example_js_manager_plugins.py index 7bdb9f3f..f9dfa8e6 100644 --- a/demos/plugins/example_js_manager_plugins.py +++ b/demos/plugins/example_js_manager_plugins.py @@ -15,6 +15,6 @@ def extra_js_urls(view_name): if view_name in PERMITTED_VIEWS: return [ { - "url": f"/-/demos/plugins/static/table-example-plugins.js", + "url": f"/static/table-example-plugins.js", } ] ``` And then started it running like this: ```bash wget https://datasette.io/content.db ``` ```bash datasette content.db \ --plugins-dir demos/plugins \ --static static:datasette/demos/plugins/static ``` It didn't quite work for me - I got this error on a table page: <img width="681" alt="image" src="https://github.com/simonw/datasette/assets/9599/02f5c16d-ea43-4c36-920d-4b14406645b5"> And this error on a query page: <img width="689" alt="image" src="https://github.com/simonw/datasette/assets/9599/994db3a0-502a-4f36-8581-c47556600d63"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1629123734 | https://github.com/dogsheep/healthkit-to-sqlite/issues/14#issuecomment-1629123734 | https://api.github.com/repos/dogsheep/healthkit-to-sqlite/issues/14 | IC_kwDOC8tyDs5hGnSW | philipp-heinrich 44622670 | 2023-07-10T14:46:52Z | 2023-07-10T14:46:52Z | NONE | @simonw any chance to get this fixed soon? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | UNIQUE constraint failed: workouts.id 771608692 | |
1627598570 | https://github.com/simonw/sqlite-utils/issues/566#issuecomment-1627598570 | https://api.github.com/repos/simonw/sqlite-utils/issues/566 | IC_kwDOCGYnMM5hAy7q | simonw 9599 | 2023-07-09T04:13:34Z | 2023-07-09T04:13:34Z | OWNER | On consulting https://pypi.org/project/tabulate/ it looks like most of those formats don't actually makes sense without headers - so the right thing here might be to raise an error if `--fmt` and `--no-headers` are used at the same time. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--no-headers` doesn't work on most formats 1795219865 | |
1627597872 | https://github.com/simonw/sqlite-utils/issues/566#issuecomment-1627597872 | https://api.github.com/repos/simonw/sqlite-utils/issues/566 | IC_kwDOCGYnMM5hAyww | simonw 9599 | 2023-07-09T04:09:56Z | 2023-07-09T04:09:56Z | OWNER | Thanks, looks like a bug. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--no-headers` doesn't work on most formats 1795219865 | |
1627564127 | https://github.com/dogsheep/pocket-to-sqlite/issues/12#issuecomment-1627564127 | https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/12 | IC_kwDODLZ_YM5hAqhf | simonw 9599 | 2023-07-09T01:19:42Z | 2023-07-09T01:19:42Z | MEMBER | https://github.com/dogsheep/pocket-to-sqlite/tree/0.2.3 and https://pypi.org/project/pocket-to-sqlite/0.2.3/ | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Switch to pyproject.toml 1795187493 | |
1627563202 | https://github.com/dogsheep/pocket-to-sqlite/issues/12#issuecomment-1627563202 | https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/12 | IC_kwDODLZ_YM5hAqTC | simonw 9599 | 2023-07-09T01:14:27Z | 2023-07-09T01:14:27Z | MEMBER | I tested this locally with `python -m build` and then `pip install ...whl` in a fresh virtual environment. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Switch to pyproject.toml 1795187493 | |
1627480353 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627480353 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAWEh | simonw 9599 | 2023-07-08T20:09:48Z | 2023-07-08T20:09:48Z | OWNER | https://docs.datasette.io/en/latest/writing_plugins.html#writing-plugins-that-accept-configuration is fixed now. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627478910 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627478910 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAVt- | simonw 9599 | 2023-07-08T20:01:19Z | 2023-07-08T20:01:19Z | OWNER | Some examples: - https://docs.datasette.io/en/latest/sql_queries.html#canned-queries - https://docs.datasette.io/en/latest/sql_queries.html#canned-query-parameters - https://docs.datasette.io/en/latest/authentication.html#access-to-an-instance - https://docs.datasette.io/en/latest/facets.html#facets-in-metadata - https://docs.datasette.io/en/latest/full_text_search.html#configuring-full-text-search-for-a-table-or-view - https://docs.datasette.io/en/latest/metadata.html - https://docs.datasette.io/en/latest/custom_templates.html#custom-css-and-javascript - https://docs.datasette.io/en/latest/plugins.html#plugin-configuration I need to fix this section: https://docs.datasette.io/en/latest/writing_plugins.html#writing-plugins-that-accept-configuration | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627455892 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627455892 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAQGU | simonw 9599 | 2023-07-08T18:39:19Z | 2023-07-08T18:39:19Z | OWNER | ``` ERROR: Could not find a version that satisfies the requirement Sphinx==6.1.3; extra == "docs" (from datasette[docs,test]) (from versions: 0.1.61611, 0.1.61798, 0.1.61843, 0.1.61945, 0.1.61950, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.5, 0.5.1, 0.5.2b1, 0.5.2, 0.6b1, 0.6, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.6, 0.6.7, 1.0b1, 1.0b2, 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.2b1, 1.2b2, 1.2b3, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3b1, 1.3b2, 1.3b3, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.4a1, 1.4b1, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.5a1, 1.5a2, 1.5b1, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.6b1, 1.6b2, 1.6b3, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.7.0b1, 1.7.0b2, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.8.0b1, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 2.0.0b1, 2.0.0b2, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 3.0.0b1, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1, 3.3.0, 3.3.1, 3.4.0, 3.4.1, 3.4.2, 3.4.3, 3.5.0, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 4.0.0b1, 4.0.0b2, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.3.0, 4.3.1, 4.3.2, 4.4.0, 4.5.0, 5.0.0b1, 5.0.0, 5.0.1, 5.0.2, 5.1.0, 5.1.1, 5.2.0, 5.2.0.post0, 5.2.1, 5.2.2, 5.2.3, 5.3.0) ERROR: No matching distribution found for Sphinx==6.1.3; extra == "docs" ``` I'm going to drop Python 3.7. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627451646 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627451646 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAPD- | simonw 9599 | 2023-07-08T18:21:24Z | 2023-07-08T18:21:24Z | OWNER | This one was tricky: <img width="764" alt="image" src="https://github.com/simonw/datasette/assets/9599/0fe2886b-4e07-4539-a254-4c47f02c3f65"> I wanted complete control over the YAML example here, so I could ensure it used multi-line strings correctly. I ended up changing my cog helper function to this: ```python import json import textwrap from yaml import safe_dump from ruamel.yaml import round_trip_load def metadata_example(cog, data=None, yaml=None): assert data or yaml, "Must provide data= or yaml=" assert not (data and yaml), "Cannot use data= and yaml=" output_yaml = None if yaml: # dedent it first yaml = textwrap.dedent(yaml).strip() # round_trip_load to preserve key order: data = round_trip_load(yaml) output_yaml = yaml else: output_yaml = safe_dump(data, sort_keys=False) cog.out("\n.. tab:: YAML\n\n") cog.out(" .. code-block:: yaml\n\n") cog.out(textwrap.indent(output_yaml, " ")) cog.out("\n\n.. tab:: JSON\n\n") cog.out(" .. code-block:: json\n\n") cog.out(textwrap.indent(json.dumps(data, indent=2), " ")) cog.out("\n") ``` This allows me to call it ith YAML in some places: ``` .. [[[cog metadata_example(cog, yaml=""" databases: fixtures: queries: neighborhood_search: fragment: fragment-goes-here hide_sql: true sql: |- select neighborhood, facet_cities.name, state from facetable join facet_cities on facetable.city_id = facet_cities.id where neighborhood like '%' || :text || '%' order by neighborhood; """) .. ]]] ``` I had to introduce https://pypi.org/project/ruamel.yaml/ as a dependency here in order to load YAML from disk while maintaining key order. I'm still using `safe_dump(data, sort_keys=False)` from PyYAML as I couldn't get the result I wanted for outputting YAML from an input of JSON using PyYAML. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627450852 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627450852 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAO3k | simonw 9599 | 2023-07-08T18:17:35Z | 2023-07-08T18:17:35Z | OWNER | I figured out a workaround: ```python extensions = [ "sphinx.ext.extlinks", "sphinx.ext.autodoc", "sphinx_copybutton", ] if not os.environ.get("DISABLE_SPHINX_INLINE_TABS"): extensions += ["sphinx_inline_tabs"] ``` That way I can run `sphinx-build -b xml . _build` successfully if I set that environment variable. I get some noisy warnings, but it runs OK. And the resulting `docs.db` file has rows like this, which I think are fine: <img width="1533" alt="image" src="https://github.com/simonw/datasette/assets/9599/0a289f53-2c6c-43e9-bda1-d4380383a02f"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627448542 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627448542 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAOTe | simonw 9599 | 2023-07-08T18:05:44Z | 2023-07-08T18:05:44Z | OWNER | Running with `-P` opens a debugger when it hits the error: ```bash sphinx-build -P -b xml . _build ``` ``` (Pdb) list 2023 2024 Raise an exception unless overridden. 2025 """ 2026 if (self.document.settings.strict_visitor 2027 or node.__class__.__name__ not in self.optional): 2028 -> raise NotImplementedError( 2029 '%s visiting unknown node type: %s' 2030 % (self.__class__, node.__class__.__name__)) 2031 2032 def unknown_departure(self, node): 2033 """ (Pdb) self.optional ('meta',) (Pdb) node.__class__.__name__ 'TabContainer' (Pdb) self.document.settings.strict_visitor (Pdb) type(self.document.settings.strict_visitor) <class 'NoneType'> ``` So if I can get `TabContainer` into that `self.optional` list I'll have fixed this problem. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627448180 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627448180 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAON0 | simonw 9599 | 2023-07-08T18:03:31Z | 2023-07-08T18:03:31Z | OWNER | Relevant code: https://github.com/docutils/docutils/blob/3b53ded52bc439d8068b6ecb20ea0a761247e479/docutils/docutils/nodes.py#L2021-L2031 ```python def unknown_visit(self, node): """ Called when entering unknown `Node` types. Raise an exception unless overridden. """ if (self.document.settings.strict_visitor or node.__class__.__name__ not in self.optional): raise NotImplementedError( '%s visiting unknown node type: %s' % (self.__class__, node.__class__.__name__)) ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627447750 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627447750 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAOHG | simonw 9599 | 2023-07-08T18:00:56Z | 2023-07-08T18:00:56Z | OWNER | Actually no it's in `sphinx-build`: ``` % sphinx-build -b xml . _build Running Sphinx v6.1.3 building [mo]: targets for 0 po files that are out of date writing output... building [xml]: targets for 28 source files that are out of date updating environment: [new config] 28 added, 0 changed, 0 removed reading sources... [100%] writing_plugins looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done writing output... [ 3%] authentication Exception occurred: File "/Users/simon/.local/share/virtualenvs/datasette-AWNrQs95/lib/python3.10/site-packages/docutils/nodes.py", line 2028, in unknown_visit raise NotImplementedError( NotImplementedError: <class 'docutils.writers.docutils_xml.XMLTranslator'> visiting unknown node type: TabContainer The full traceback has been saved in /var/folders/x6/31xf1vxj0nn9mxqq8z0mmcfw0000gn/T/sphinx-err-1wkxmkji.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks! ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627447478 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627447478 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hAOC2 | simonw 9599 | 2023-07-08T17:59:25Z | 2023-07-08T17:59:25Z | OWNER | Hit a problem: ``` Exception occurred: File "/opt/hostedtoolcache/Python/3.9.17/x64/lib/python3.9/site-packages/docutils/nodes.py", line 2028, in unknown_visit raise NotImplementedError( NotImplementedError: <class 'docutils.writers.docutils_xml.XMLTranslator'> visiting unknown node type: TabContainer The full traceback has been saved in /tmp/sphinx-err-tfujyw1h.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks! ``` That's happening here: https://github.com/simonw/datasette/blob/0183e1a72d4d93b1d9a9363f4d47fcc0b5d5849c/.github/workflows/deploy-latest.yml#L42-L48 My https://github.com/simonw/sphinx-to-sqlite tool can't handle the new `TabContainer` elements introduced by `sphinx-inline-tabs`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627396658 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627396658 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hABoy | simonw 9599 | 2023-07-08T16:40:07Z | 2023-07-08T16:40:07Z | OWNER | https://docs.datasette.io/en/latest/metadata.html ![inline-tabs](https://github.com/simonw/datasette/assets/9599/975bdff5-74ac-451e-92c3-a7dd05d4b862) | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627396450 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627396450 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hABli | simonw 9599 | 2023-07-08T16:38:58Z | 2023-07-08T16:38:58Z | OWNER | I'm using `cog` and this utility function to generate the YAML/JSON tabs: https://github.com/simonw/datasette/blob/3b336d8071fb5707bd006de1d614f701d20246a3/docs/metadata_doc.py#L1-L13 Example usage: https://github.com/simonw/datasette/blob/3b336d8071fb5707bd006de1d614f701d20246a3/docs/metadata.rst?plain=1#L17-L53 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1627395947 | https://github.com/simonw/datasette/issues/1153#issuecomment-1627395947 | https://api.github.com/repos/simonw/datasette/issues/1153 | IC_kwDOBm6k_c5hABdr | simonw 9599 | 2023-07-08T16:35:45Z | 2023-07-08T16:35:45Z | OWNER | I was inspired to finally address this after seeing `sphinx-inline-tabs` at work in https://webcolors.readthedocs.io/en/latest/install.html | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use YAML examples in documentation by default, not JSON 771202454 | |
1618380888 | https://github.com/simonw/sqlite-utils/issues/565#issuecomment-1618380888 | https://api.github.com/repos/simonw/sqlite-utils/issues/565 | IC_kwDOCGYnMM5gdohY | simonw 9599 | 2023-07-03T14:09:11Z | 2023-07-03T14:09:31Z | OWNER | For the CLI: ```bash sqlite-utils rename-table data.db old_table_name new_table_name ``` For the Python code, should it go on Table or on Database? ```python db["foo"].rename_table("bar") db.rename_table("foo", "bar") ``` I think I like the second better, it's slightly more clear. Also need a design for an option for the `.transform()` method to indicate that the new table should be created with a new name without dropping the old one. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Table renaming utilities 1786258502 | |
1617395444 | https://github.com/simonw/sqlite-utils/issues/563#issuecomment-1617395444 | https://api.github.com/repos/simonw/sqlite-utils/issues/563 | IC_kwDOCGYnMM5gZ370 | simonw 9599 | 2023-07-03T05:44:43Z | 2023-07-03T05:44:43Z | OWNER | Documentation at the bottom of this section: https://sqlite-utils.datasette.io/en/latest/cli.html#inserting-csv-or-tsv-data | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--empty-null` option when importing CSV 1785360409 | |
1616853644 | https://github.com/simonw/datasette/issues/2087#issuecomment-1616853644 | https://api.github.com/repos/simonw/datasette/issues/2087 | IC_kwDOBm6k_c5gXzqM | asg017 15178711 | 2023-07-02T22:00:48Z | 2023-07-02T22:00:48Z | CONTRIBUTOR | I just saw in the docs that Dasette auto-detects `settings.json`: > settings.json - settings that would normally be passed using --setting - here they should be stored as a JSON object of key/value pairs > [*Source*](https://docs.datasette.io/en/stable/settings.html#:~:text=settings.json%20%2D%20settings%20that%20would%20normally%20be%20passed%20using%20%2D%2Dsetting%20%2D%20here%20they%20should%20be%20stored%20as%20a%20JSON%20object%20of%20key/value%20pairs) | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--settings settings.json` option 1765870617 | |
1616782404 | https://github.com/simonw/sqlite-utils/issues/562#issuecomment-1616782404 | https://api.github.com/repos/simonw/sqlite-utils/issues/562 | IC_kwDOCGYnMM5gXiRE | simonw 9599 | 2023-07-02T19:24:14Z | 2023-07-02T19:26:39Z | OWNER | [Dataclasses](https://docs.python.org/3/library/dataclasses.html) were added in Python 3.7 and `sqlite-utils` was originally written for Python 3.6 - but both 3.6 and 3.7 are EOL now. The thing that makes Dataclasses particularly interesting is the potential to use type annotations with them to help specify the types of the related SQLite columns. Example for https://datasette.io/content/users ```sql CREATE TABLE [users] ( [login] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [avatar_url] TEXT, [gravatar_id] TEXT, [html_url] TEXT, [type] TEXT, [site_admin] INTEGER, [name] TEXT ); ``` And the dataclass: ```python from dataclasses import dataclass @dataclass class User: id: int login: str node_id: str avatar_url: str gravatar_id: str html_url: str type: str site_admin: int name: str ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Explore the intersection between sqlite-utils and dataclasses 1784794489 | |
1616286848 | https://github.com/simonw/datasette/issues/2093#issuecomment-1616286848 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gVpSA | asg017 15178711 | 2023-07-02T02:17:46Z | 2023-07-02T02:17:46Z | CONTRIBUTOR | Storing metadata in the database won't be required. I imagine there'll be many different ways to store metadata, including any possible `datasette_metadata` or sqlite-docs, or the older metadata.json way. The next question will be how precedence should work - i'd imagine metadata.json > plugins > datasette_metadata > sqlite-docs | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1616195496 | https://github.com/simonw/datasette/issues/2093#issuecomment-1616195496 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gVS-o | terinjokes 273509 | 2023-07-02T00:06:54Z | 2023-07-02T00:07:17Z | NONE | I'm not keen on requiring metadata to be within the database. I commonly have multiple DBs, from various sources, and having one config file to provide the metadata works out very well. I use Datasette with databases where I'm not the original source, needing to mutate them to add a metadata table or sqlite-docs makes me uncomfortable. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1616095810 | https://github.com/simonw/datasette/pull/2052#issuecomment-1616095810 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5gU6pC | asg017 15178711 | 2023-07-01T20:31:31Z | 2023-07-01T20:31:31Z | CONTRIBUTOR | > Just curious, is there a query that can be used to compile this programmatically, or did you identify these through memory? I just did a github search for `user:simonw "def extra_js_urls("` ! Though I'm sure other plugins made by people other than Simon also exist out there https://github.com/search?q=user%3Asimonw+%22def+extra_js_urls%28%22&type=code | {"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1615997736 | https://github.com/simonw/datasette/pull/2052#issuecomment-1615997736 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5gUiso | hydrosquall 9020979 | 2023-07-01T16:55:24Z | 2023-07-01T16:55:24Z | NONE | > Ok @hydrosquall a couple things before this PR should be good to go: Thank you @asg017 ! I've pushed both suggested changes onto this branch. > Not sure how difficult it'll be to inject it server-side If we are OK with having a build system, it would free me up to do do many things! We could make datasette-manager.js a server-side rendered file as a "template" instead of having it as a static JS file, but I'm not sure it's worth the extra jump in complexity / loss of syntax highlighting in the JS file. In the short-term, I could see an intermediary solution where a unit test in the preferred language was able to read both `version.py` and `datasette-manager.js`, and make sure that the strings versions are in sync. (This assumes that we want the manager and datasette's versions to be synced, and not decoupled). Since the version is not changing very often, a "manual sync" might be good enough. > In terms of how to integrate this into Datasette, a few options I can see working: This sounds good to me. I'm not sure how to add a settings flag, but will be interested to see the PR that adds support for it. > I'm also curious to see how "plugins for a plugin' would work I'm comfortable to wait until we have a realistic usecase for this. In the short term, I think we could give plugins a way to grant access to a "public API of other plugins", and also ask to be notified when plugins with other names have loaded, but don't picture the datasette manager getting more involved than that. > here's a list of Simon's Datasette plugins that use "extra_js_urls()" Neat, thanks for compiling this list! Just curious, is there a query that can be used to compile this programmatically, or did you identify these through memory? > I want to make a javascript plugin on top of the code-mirror editor to make a few things nicer (function auto-complete, table/column descriptions, etc.) I look forward to trying this out 👍 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1614652001 | https://github.com/simonw/datasette/issues/2093#issuecomment-1614652001 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gPaJh | simonw 9599 | 2023-06-30T13:27:13Z | 2023-06-30T13:27:13Z | OWNER | I agree, settings in the DB doesn't make sense but metadata does. On the JSON v YAML v TOML issue I just spotted Caddy has a concept of config adapters which they use to resolve exactly that problem: https://caddyserver.com/docs/config-adapters | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1613896210 | https://github.com/simonw/datasette/issues/2093#issuecomment-1613896210 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gMhoS | asg017 15178711 | 2023-06-29T22:53:33Z | 2023-06-29T22:53:33Z | CONTRIBUTOR | Maybe we can have a separate issue for revamping `metadata.json`? A `datasette_metadata` table or the `sqlite-docs` extension seem like two reasonable additions that we can work through. Storing metadata inside a SQLite database makes sense, but I don't think storing `datasette.*` style config (ex ports, settings, etc.) inside a SQLite DB makes sense, since it's very environment-dependent | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1613895188 | https://github.com/simonw/datasette/issues/2093#issuecomment-1613895188 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gMhYU | asg017 15178711 | 2023-06-29T22:51:53Z | 2023-06-29T22:51:53Z | CONTRIBUTOR | I agree with not liking `metadata.json` stuff in a `datasette.*` config file. Editing description of a table/column in a file like `datasette.*` seems odd to me. Though since plugin configuration currently lives in `metadata.json`, I think it should be removed from there and placed in `datasette.*`, at least for top-level config like `datasette-auth-github`'s config. Keeping `metadata.json` strictly for documentation/licensing/column units makes sense to me, but anything plugin related should be in some config file, like `datasette.*`. And ya, supporting both `datasette.*` and CLI flags makes a lot of sense to me. Any `--setting` flag should override anything in `datasette.*` for easier debugging, with possibly a warning message so people don't get confused. Same with `--port` and a port defined in `datasette.*` | {"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1613889979 | https://github.com/simonw/datasette/issues/2093#issuecomment-1613889979 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gMgG7 | simonw 9599 | 2023-06-29T22:44:08Z | 2023-06-30T13:25:39Z | OWNER | I do like also being able to set options using command line options though - for things like SQL time limits I'd much rather be able to throw on `--setting sql_time_limit_ms 10000` than have to save a config file to disk. So I'd want to support both. Which maybe means also having a way to set plugin options with CLI options. `datasette publish` kind of has that ability already: ``` datasette publish heroku my_database.db \ --name my-heroku-app-demo \ --install=datasette-auth-github \ --plugin-secret datasette-auth-github client_id your_client_id \ --plugin-secret datasette-auth-github client_secret your_client_secret ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1613887492 | https://github.com/simonw/datasette/issues/2093#issuecomment-1613887492 | https://api.github.com/repos/simonw/datasette/issues/2093 | IC_kwDOBm6k_c5gMfgE | simonw 9599 | 2023-06-29T22:40:25Z | 2023-06-29T22:40:25Z | OWNER | I'm strongly in favour of combining settings, configuration and plugin configuration. I'm not keen on mixing in metadata as well - that feels like a different concept to me, and I'm unhappy with how that's already had things like plugin settings leak into it. I'm not yet sold on TOML - I actually find it less intuitive than YAML, surprisingly. They all have their warts I guess. Datasette already has the ability to consume JSON or YAML for metadata - maybe it could grow TOML support too? That way users could have a `datasette.json` or `datasette.yaml` or `datasette.toml` file depending on their preference. In terms of metadata: since that's means to be driven by a plugin hook anyway, maybe one of the potential sources of metadata is a `metadata` nested object in that `datasette.*` configuration file. Or you can have it in a separate `metadata.json` or bundled into the SQLite database or some other plugin-driven mechanism. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Proposal: Combine settings, metadata, static, etc. into a single `datasette.toml` File 1781530343 | |
1613778296 | https://github.com/simonw/datasette/pull/2052#issuecomment-1613778296 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5gME14 | asg017 15178711 | 2023-06-29T20:36:09Z | 2023-06-29T20:36:09Z | CONTRIBUTOR | Ok @hydrosquall a couple things before this PR should be good to go: - Can we move `datasette/static/table-example-plugins.js` into `demos/plugins/static`? - For `datasetteManager.VERSION`, can we fill that in or just comment it out for now? Not sure how difficult it'll be to inject it server-side. I imagine we could also have a small build process with esbuild/rollup that just injects a version string into `manager.js` directly, so we don't have to worry about server-rendering (but that can be a future PR) In terms of how to integrate this into Datasette, a few options I can see working: - Push this as-is and figure it out before the next release - Hide this feature behind a settings flag (`--setting unstable-js-plugins on`) and use that setting to hide/show `<script src="{{ urls.static('datasette-manager.js') }}" defer></script>` in `base.html` I'll let @simonw decide which one to work with. I kindof like the idea of having an "unstable" opt-in process to enable JS plugins, to give us time to try it out with a wide variety of plugins until we feel its ready. I'm also curious to see how "plugins for a plugin' would work, like #1542. For example, if the leaflet plugin showed default markers, but also included its own hook for other plugins to add more markers/styling. I'm imagine that the individual plugin would re-create their own plugin system compared to this, since handling "plugins of plugins" at the top with Datasette seems really convoluted. Also for posterity, here's a list of Simon's Datasette plugins that use "extra_js_urls()", which probably means they can be ported/re-written to use this new plugin system: - [`datasette-vega`](https://github.com/simonw/datasette-vega/blob/00de059ab1ef77394ba9f9547abfacf966c479c4/datasette_vega/__init__.py#L25) - [`datasette-cluster-map`](https://github.com/simonw/datasette-cluster-map/blob/795d25ad9ff6cba0307191f44fecc8f8070bef5c/datasette_cluster_map/__init__.py#L14) - [`datasette-leaflet-geojson`](https://github.com/simonw/datasette-leaflet… | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 1} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1613381990 | https://github.com/simonw/datasette/issues/2092#issuecomment-1613381990 | https://api.github.com/repos/simonw/datasette/issues/2092 | IC_kwDOBm6k_c5gKkFm | simonw 9599 | 2023-06-29T15:23:04Z | 2023-06-29T15:26:28Z | OWNER | Felt lazy: ```bash symbex test_homepage -f tests/test_api.py | \ llm -m 4 --system 'Change all of the == some integer tests in this code to isinstance(thing, int) instead' ``` Output: ```python # File: tests/test_api.py Line: 26 @pytest.mark.asyncio async def test_homepage(ds_client): response = await ds_client.get("/.json") assert response.status_code == 200 assert "application/json; charset=utf-8" == response.headers["content-type"] data = response.json() assert isinstance(data.keys(), int) d = data["fixtures"] assert d["name"] == "fixtures" assert isinstance(d["tables_count"], int) assert isinstance(len(d["tables_and_views_truncated"]), int) assert d["tables_and_views_more"] is True # 4 hidden FTS tables + no_primary_key (hidden in metadata) assert isinstance(d["hidden_tables_count"], int) # 201 in no_primary_key, plus 6 in other hidden tables: assert isinstance(d["hidden_table_rows_sum"], int), data assert isinstance(d["views_count"], int) ``` I'll use most of that and delete the obsoleted comments. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | test_homepage intermittent failure 1781047747 | |
1613375407 | https://github.com/simonw/datasette/issues/2092#issuecomment-1613375407 | https://api.github.com/repos/simonw/datasette/issues/2092 | IC_kwDOBm6k_c5gKiev | simonw 9599 | 2023-06-29T15:20:52Z | 2023-06-29T15:21:05Z | OWNER | I'm going to remove this assertion entirely. The homepage JSON needs a refactor anyway. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | test_homepage intermittent failure 1781047747 | |
1613369355 | https://github.com/simonw/datasette/issues/2091#issuecomment-1613369355 | https://api.github.com/repos/simonw/datasette/issues/2091 | IC_kwDOBm6k_c5gKhAL | simonw 9599 | 2023-06-29T15:18:34Z | 2023-06-29T15:18:34Z | OWNER | Posted on the Glitch feedback forum about this here: https://support.glitch.com/t/upgrade-python-version-from-3-7-which-is-now-eol-to-something-more-recent/63011 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Drop support for Python 3.7 1781022369 | |
1613360413 | https://github.com/simonw/datasette/issues/2091#issuecomment-1613360413 | https://api.github.com/repos/simonw/datasette/issues/2091 | IC_kwDOBm6k_c5gKe0d | simonw 9599 | 2023-06-29T15:13:04Z | 2023-06-29T15:13:04Z | OWNER | One problem: https://glitch.com/ still provides 3.7: ``` $ python3 --version Python 3.7.10 ``` <img width="956" alt="image" src="https://github.com/simonw/datasette/assets/9599/e1fa44c0-4362-40e6-a2c7-d5b09b784c66"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Drop support for Python 3.7 1781022369 | |
1613346412 | https://github.com/simonw/datasette/issues/2090#issuecomment-1613346412 | https://api.github.com/repos/simonw/datasette/issues/2090 | IC_kwDOBm6k_c5gKbZs | simonw 9599 | 2023-06-29T15:05:04Z | 2023-06-29T15:05:04Z | OWNER | Decided to fix just those "Ambiguous variable name" ones: ```bash ruff check . | grep E741 ``` Then iterated through and fixed them all. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Adopt ruff for linting 1781005740 | |
1613339404 | https://github.com/simonw/datasette/issues/2090#issuecomment-1613339404 | https://api.github.com/repos/simonw/datasette/issues/2090 | IC_kwDOBm6k_c5gKZsM | simonw 9599 | 2023-06-29T15:01:01Z | 2023-06-29T15:01:20Z | OWNER | I tried it just now and got some interesting results. I dropped in a `ruff.toml` file: ```toml line-length = 160 ``` Because the default line length limit of 88 was causing a lot of noisy errors. Then run: ```bash pip install ruff ruff check . ``` Plenty of warnings about unused imports - running `ruff check . --fix` fixed those automatically, but I think I still need to manually review them as some might be imports which are deliberate and should be in `__all__` to ensure they are visible from that module as well. Some lines in tests are longer than even 160 chars, e.g.: https://github.com/simonw/datasette/blob/99ba05118891db9dc30f1dca22ad6709775560de/tests/test_html.py#L673-L681 These can have ` # noqa: E501` added to the end of those lines to skip the check for them. That got it down to: ``` % ruff check . datasette/views/table.py:23:5: F811 Redefinition of unused `format_bytes` from line 19 run_tests.py:2:5: E401 Multiple imports on one line tests/test_api.py:591:40: F811 Redefinition of unused `app_client_no_files` from line 7 tests/test_api.py:629:35: F811 Redefinition of unused `app_client_no_files` from line 7 tests/test_api.py:635:54: F811 Redefinition of unused `app_client_with_dot` from line 8 tests/test_api.py:661:25: F811 Redefinition of unused `app_client_shorter_time_limit` from line 9 tests/test_api.py:759:25: F811 Redefinition of unused `app_client_two_attached_databases_one_immutable` from line 10 tests/test_api.py:892:28: F811 Redefinition of unused `app_client_larger_cache_size` from line 11 tests/test_api.py:928:5: F811 Redefinition of unused `app_client_with_cors` from line 12 tests/test_api.py:929:5: F811 Redefinition of unused `app_client_two_attached_databases_one_immutable` from line 10 tests/test_api.py:969:38: F811 Redefinition of unused `app_client_two_attached_databases` from line 13 tests/test_api.py:976:39: F811 Redefinition of unused `app_client_conflicting_database_names` from line 14 tests/test_api.py:987:38: F811 Redefinition of u… | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Adopt ruff for linting 1781005740 | |
1613316722 | https://github.com/simonw/datasette/issues/2089#issuecomment-1613316722 | https://api.github.com/repos/simonw/datasette/issues/2089 | IC_kwDOBm6k_c5gKUJy | simonw 9599 | 2023-06-29T14:48:10Z | 2023-06-29T14:48:10Z | OWNER | Spell check is passing now. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | codespell test failure 1780973290 | |
1613315851 | https://github.com/simonw/datasette/issues/2089#issuecomment-1613315851 | https://api.github.com/repos/simonw/datasette/issues/2089 | IC_kwDOBm6k_c5gKT8L | simonw 9599 | 2023-06-29T14:47:38Z | 2023-06-29T14:47:38Z | OWNER | Confirmed, this was a 2.2.5 change: https://github.com/codespell-project/codespell/releases/tag/v2.2.5 > - Add displaing->displaying by [@peternewman](https://github.com/peternewman) in [#2808](https://github.com/codespell-project/codespell/pull/2808) | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | codespell test failure 1780973290 | |
1613307716 | https://github.com/simonw/datasette/issues/2089#issuecomment-1613307716 | https://api.github.com/repos/simonw/datasette/issues/2089 | IC_kwDOBm6k_c5gKR9E | simonw 9599 | 2023-06-29T14:42:23Z | 2023-06-29T14:42:23Z | OWNER | Yes, upgrading locally got me the correct version and the test failure: ``` % pip install -U codespell Requirement already satisfied: codespell in /Users/simon/.local/share/virtualenvs/datasette-AWNrQs95/lib/python3.10/site-packages (2.2.2) Collecting codespell Downloading codespell-2.2.5-py3-none-any.whl (242 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 242.7/242.7 kB 4.9 MB/s eta 0:00:00 Installing collected packages: codespell Attempting uninstall: codespell Found existing installation: codespell 2.2.2 Uninstalling codespell-2.2.2: Successfully uninstalled codespell-2.2.2 Successfully installed codespell-2.2.5 % codespell docs/metadata.rst docs/metadata.rst:192: displaing ==> displaying ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | codespell test failure 1780973290 | |
1613306787 | https://github.com/simonw/datasette/issues/2089#issuecomment-1613306787 | https://api.github.com/repos/simonw/datasette/issues/2089 | IC_kwDOBm6k_c5gKRuj | simonw 9599 | 2023-06-29T14:41:47Z | 2023-06-29T14:41:47Z | OWNER | Looks like in CI it's running 2.2.5: ``` Collecting codespell (from datasette==1.0a2) Downloading codespell-2.2.5-py3-none-any.whl (242 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 242.7/242.7 kB 31.1 MB/s eta 0:00:00 ``` But on my laptop it's 2.2.2: ``` % codespell --version 2.2.2 ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | codespell test failure 1780973290 | |
1613305070 | https://github.com/simonw/datasette/issues/2089#issuecomment-1613305070 | https://api.github.com/repos/simonw/datasette/issues/2089 | IC_kwDOBm6k_c5gKRTu | simonw 9599 | 2023-06-29T14:40:44Z | 2023-06-29T14:40:44Z | OWNER | I'm not sure why I can't duplicate this failure in my local development environment: ``` % codespell docs/metadata.rst ``` It finds no errors. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | codespell test failure 1780973290 | |
1613290899 | https://github.com/simonw/datasette/pull/2077#issuecomment-1613290899 | https://api.github.com/repos/simonw/datasette/issues/2077 | IC_kwDOBm6k_c5gKN2T | simonw 9599 | 2023-06-29T14:32:16Z | 2023-06-29T14:32:16Z | OWNER | @dependabot recreate | {"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Bump furo from 2023.3.27 to 2023.5.20 1719759468 | |
1610512875 | https://github.com/simonw/datasette/issues/1510#issuecomment-1610512875 | https://api.github.com/repos/simonw/datasette/issues/1510 | IC_kwDOBm6k_c5f_nnr | simonw 9599 | 2023-06-28T02:02:10Z | 2023-06-28T02:05:21Z | OWNER | I prototyped an approach to this using dataclasses and a `cog` mechanism for turning those into rendered tables in Sphinx. Here's what that prototype looks like: <img width="1069" alt="image" src="https://github.com/simonw/datasette/assets/9599/79210a43-716c-4470-a62d-01aa871973ec"> See https://github.com/simonw/datasette/commit/68223784167fdec4e7ebfca56002a6548ba7b423 for how it works. Here's the class that documented: https://github.com/simonw/datasette/blob/68223784167fdec4e7ebfca56002a6548ba7b423/datasette/context.py#L54-L68 And the code that generates the rST: https://github.com/simonw/datasette/blob/68223784167fdec4e7ebfca56002a6548ba7b423/datasette/context.py#L19-L45 And the bit that cog executes: https://github.com/simonw/datasette/blob/68223784167fdec4e7ebfca56002a6548ba7b423/docs/template_context.rst?plain=1#L9-L12 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette 1.0 documented template context (maybe via API docs) 1054244712 | |
1610040517 | https://github.com/simonw/sqlite-utils/issues/561#issuecomment-1610040517 | https://api.github.com/repos/simonw/sqlite-utils/issues/561 | IC_kwDOCGYnMM5f90TF | simonw 9599 | 2023-06-27T18:44:31Z | 2023-06-27T18:44:38Z | OWNER | Got this working: ```bash sqlite-utils insert /tmp/playground.db Playground_Submission_Data \ ~/Downloads/Playground_Submission_Data.csv --csv --stop-after 2000 ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | `--stop-after` option for `insert` and `upsert` commands 1777548699 | |
1606415188 | https://github.com/simonw/sqlite-utils/issues/235#issuecomment-1606415188 | https://api.github.com/repos/simonw/sqlite-utils/issues/235 | IC_kwDOCGYnMM5fv_NU | simonw 9599 | 2023-06-26T01:46:47Z | 2023-06-26T01:47:01Z | OWNER | I just tested this in a brand new virtual environment using the macOS Python 3: ```bash pipenv shell --python /Applications/Xcode.app/Contents/Developer/usr/bin/python3 ``` Then in that virtual environment I ran: ```bash pip install sqlite-utils # Confirm the right one is on the path: which sqlite-utils curl "https://data.nasa.gov/resource/y77d-th95.json" | \ sqlite-utils insert meteorites.db meteorites - --pk=id sqlite-utils extract meteorites.db meteorites recclass ``` This threw the same error reported above. Then I did this: ```bash rm meteorites.db pip install sqlean.py curl "https://data.nasa.gov/resource/y77d-th95.json" | \ sqlite-utils insert meteorites.db meteorites - --pk=id sqlite-utils extract meteorites.db meteorites recclass ``` And that second time it worked correctly. | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0} | Extract columns cannot create foreign key relation: sqlite3.OperationalError: table sqlite_master may not be modified 810618495 | |
1606411508 | https://github.com/simonw/sqlite-utils/issues/235#issuecomment-1606411508 | https://api.github.com/repos/simonw/sqlite-utils/issues/235 | IC_kwDOCGYnMM5fv-T0 | simonw 9599 | 2023-06-26T01:42:10Z | 2023-06-26T01:42:22Z | OWNER | https://sqlite-utils.datasette.io/en/stable/changelog.html#v3-33 - upgrading to `sqlite-utils>=3.33` and then installing both `sqlean.py` and `sqlite-dump` in the same virtual environment as `sqlite-utils` should fix this issue. | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Extract columns cannot create foreign key relation: sqlite3.OperationalError: table sqlite_master may not be modified 810618495 | |
1606352600 | https://github.com/simonw/datasette/pull/2052#issuecomment-1606352600 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5fvv7Y | asg017 15178711 | 2023-06-26T00:17:04Z | 2023-06-26T00:17:04Z | CONTRIBUTOR | :wave: would love to see this get merged soon! I want to make a javascript plugin on top of the code-mirror editor to make a few things nicer (function auto-complete, table/column descriptions, etc.), and this would help out a bunch | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1606315321 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606315321 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvm05 | simonw 9599 | 2023-06-25T23:18:33Z | 2023-06-25T23:18:33Z | OWNER | Documentation preview: https://sqlite-utils--560.org.readthedocs.build/en/560/installation.html#alternatives-to-sqlite3 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606310630 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606310630 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvlrm | simonw 9599 | 2023-06-25T23:06:07Z | 2023-06-25T23:06:07Z | OWNER | Filed an issue about the above with `pysqlite3` (which `sqlean.py` is based on) here: - https://github.com/coleifer/pysqlite3/issues/58 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606297356 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606297356 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvicM | simonw 9599 | 2023-06-25T22:42:41Z | 2023-06-25T22:42:41Z | OWNER | Yes that does seem to do the trick: ```pycon >>> import sqlean >>> db = sqlean.connect("/tmp/4.db") >>> db.execute('PRAGMA journal_mode;').fetchall() [('delete',)] >>> db.isolation_level '' >>> db.execute('PRAGMA journal_mode=wal;') Traceback (most recent call last): File "<stdin>", line 1, in <module> sqlean.dbapi2.OperationalError: cannot change into wal mode from within a transaction >>> db.isolation_level = None >>> db.isolation_level >>> db.execute('PRAGMA journal_mode=wal;') <sqlean.dbapi2.Cursor object at 0x104437c20> ``` Weird how `isolation_level` of empty string causes the error, but setting that to `None` fixes the error. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606294627 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606294627 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvhxj | simonw 9599 | 2023-06-25T22:40:10Z | 2023-06-25T22:40:10Z | OWNER | I suspect this has something to do with `autocommit` mode in `sqlite3` - which I may be able to turn off by setting `con.isolation_level = None`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606293382 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606293382 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvheG | simonw 9599 | 2023-06-25T22:34:47Z | 2023-06-25T22:34:47Z | OWNER | ```pycon >>> import sqlite3 >>> db = sqlite3.connect("/tmp/1.db") >>> db.execute('PRAGMA journal_mode=wal;') <sqlite3.Cursor object at 0x102475ec0> >>> import sqlean >>> db2 = sqlean.connect("/tmp/2.db") >>> db2.execute('PRAGMA journal_mode=wal;') Traceback (most recent call last): File "<stdin>", line 1, in <module> sqlean.dbapi2.OperationalError: cannot change into wal mode from within a transaction ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606290917 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606290917 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvg3l | simonw 9599 | 2023-06-25T22:32:28Z | 2023-06-25T22:32:28Z | OWNER | I've fixed most of the test failures, but I still need to fix this one: > cannot change into wal mode from within a transaction | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606273005 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606273005 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvcft | simonw 9599 | 2023-06-25T21:47:47Z | 2023-06-25T21:47:47Z | OWNER | I can use https://github.com/simonw/sqlite-dump as an optional dependency to handle the missing `.iterdump()` method. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606270887 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606270887 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvb-n | simonw 9599 | 2023-06-25T21:37:12Z | 2023-06-26T08:21:00Z | OWNER | On my own laptop I got a crash running the tests - details here: - https://github.com/nalgeon/sqlean.py/issues/3 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606270055 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606270055 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvbxn | simonw 9599 | 2023-06-25T21:31:56Z | 2023-06-25T21:31:56Z | OWNER | Lots of failures now that I'm trying to run the tests against `sqlean.py` on macOS and Python 3.10: https://github.com/simonw/sqlite-utils/actions/runs/5371800108/jobs/9744802953 A bunch of these, because `pysqlite3` chooses not to implement `.iterdump()`: ``` @pytest.fixture def db_to_analyze_path(db_to_analyze, tmpdir): path = str(tmpdir / "test.db") db = sqlite3.connect(path) > db.executescript("\n".join(db_to_analyze.conn.iterdump())) E AttributeError: 'sqlean.dbapi2.Connection' object has no attribute 'iterdump' ``` Also some of these: ``` def test_analyze_whole_database(db): assert set(db.table_names()) == {"one_index", "two_indexes"} db.analyze() > assert set(db.table_names()) == {"one_index", "two_indexes", "sqlite_stat1"} E AssertionError: assert {'one_index',...'two_indexes'} == {'one_index',...'two_indexes'} E Extra items in the left set: E 'sqlite_stat4' E Full diff: E - {'two_indexes', 'sqlite_stat1', 'one_index'} E + {'two_indexes', 'sqlite_stat1', 'sqlite_stat4', 'one_index'} E ? ++++++++++++++++ ``` Apparently `sqlean.py` adds a `sqlite_stat4` table that the tests are not expecting. Plus some errors that look like this: ``` def test_enable_wal(): runner = CliRunner() dbs = ["test.db", "test2.db"] with runner.isolated_filesystem(): for dbname in dbs: db = Database(dbname) db["t"].create({"pk": int}, pk="pk") assert db.journal_mode == "delete" result = runner.invoke(cli.cli, ["enable-wal"] + dbs) > assert 0 == result.exit_code E AssertionError: assert 0 == 1 E + where 1 = <Result OperationalError('cannot change into wal mode from within a transaction')>.exit_code ``` Test summary: ``` ============ 13 failed, 909 passed, 16 skipped, 2 errors in 19.29s ============= ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1606237836 | https://github.com/simonw/sqlite-utils/pull/560#issuecomment-1606237836 | https://api.github.com/repos/simonw/sqlite-utils/issues/560 | IC_kwDOCGYnMM5fvT6M | codecov[bot] 22429695 | 2023-06-25T19:49:45Z | 2023-06-26T08:20:59Z | NONE | ## [Codecov](https://app.codecov.io/gh/simonw/sqlite-utils/pull/560?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) Report Patch coverage: **`80.55`**% and project coverage change: **`-0.15`** :warning: > Comparison is base [(`2747257`)](https://app.codecov.io/gh/simonw/sqlite-utils/commit/2747257a3334d55e890b40ec58fada57ae8cfbfd?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 96.36% compared to head [(`5e7d27e`)](https://app.codecov.io/gh/simonw/sqlite-utils/pull/560?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 96.22%. <details><summary>Additional details and impacted files</summary> ```diff @@ Coverage Diff @@ ## main #560 +/- ## ========================================== - Coverage 96.36% 96.22% -0.15% ========================================== Files 6 6 Lines 2726 2752 +26 ========================================== + Hits 2627 2648 +21 - Misses 99 104 +5 ``` | [Impacted Files](https://app.codecov.io/gh/simonw/sqlite-utils/pull/560?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) | Coverage Δ | | |---|---|---| | [sqlite\_utils/utils.py](https://app.codecov.io/gh/simonw/sqlite-utils/pull/560?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison#diff-c3FsaXRlX3V0aWxzL3V0aWxzLnB5) | `94.56% <63.63%> (-0.62%)` | :arrow_down: | | [sqlite\_utils/db.py](https://app.codecov.io/gh/simonw/sqlite-utils/pull/560?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison#diff-c3FsaXRlX3V0aWxzL2RiLnB5) | `97.33% <86.36%> (-0.20%)` | :arrow_down: |… | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use sqlean if available in environment 1773458985 | |
1604379952 | https://github.com/simonw/sqlite-utils/issues/235#issuecomment-1604379952 | https://api.github.com/repos/simonw/sqlite-utils/issues/235 | IC_kwDOCGYnMM5foOUw | simonw 9599 | 2023-06-23T14:39:55Z | 2023-06-23T15:39:32Z | OWNER | Ideally a workaround for this right now would be to install `pysqlite3` in the same virtual environment: sqlite-utils install pysqlite3-binary But `pysqlite3-binary` doesn't yet ship a wheel for macOS so this probably won't work for most people. The "easiest" fix at the moment is to use Python from Homebrew - so `brew install sqlite-utils` for example won't suffer from this problem. Not a great solution for people who aren't using Homebrew though! | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Extract columns cannot create foreign key relation: sqlite3.OperationalError: table sqlite_master may not be modified 810618495 | |
1600778057 | https://github.com/simonw/datasette/issues/260#issuecomment-1600778057 | https://api.github.com/repos/simonw/datasette/issues/260 | IC_kwDOBm6k_c5fae9J | simonw 9599 | 2023-06-21T12:51:22Z | 2023-06-21T12:51:22Z | OWNER | Another example of confusion from this today: https://discord.com/channels/823971286308356157/823971286941302908/1121042411238457374 See also https://gist.github.com/BinomeDeNewton/651ac8b50dd5420f8e54d1682eee5fed?permalink_comment_id=4605982#gistcomment-4605982 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Validate metadata.json on startup 323223872 | |
1592617271 | https://github.com/simonw/sqlite-utils/issues/535#issuecomment-1592617271 | https://api.github.com/repos/simonw/sqlite-utils/issues/535 | IC_kwDOCGYnMM5e7Wk3 | erlend-aasland 13780613 | 2023-06-15T08:39:49Z | 2023-06-15T08:39:49Z | NONE | > piping to `jq` is good enough usually ... or `python -m json.tool`[^1], if you don't have `jq` installed. [^1]: no fancy colouring, like `jq`; only pretty-printing | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | rows: --transpose or psql extended view-like functionality 1655860104 | |
1592110694 | https://github.com/simonw/sqlite-utils/issues/529#issuecomment-1592110694 | https://api.github.com/repos/simonw/sqlite-utils/issues/529 | IC_kwDOCGYnMM5e5a5m | chapmanjacobd 7908073 | 2023-06-14T23:11:47Z | 2023-06-14T23:12:12Z | CONTRIBUTOR | sorry i was wrong. `sqlite-utils --raw-lines` works correctly ``` sqlite-utils --raw-lines :memory: "SELECT * FROM (VALUES ('test'), ('line2'))" | cat -A test$ line2$ sqlite-utils --csv --no-headers :memory: "SELECT * FROM (VALUES ('test'), ('line2'))" | cat -A test$ line2$ ``` I think this was fixed somewhat recently | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Microsoft line endings 1581090327 | |
1592052320 | https://github.com/simonw/sqlite-utils/issues/535#issuecomment-1592052320 | https://api.github.com/repos/simonw/sqlite-utils/issues/535 | IC_kwDOCGYnMM5e5Mpg | chapmanjacobd 7908073 | 2023-06-14T22:05:28Z | 2023-06-14T22:05:28Z | CONTRIBUTOR | piping to `jq` is good enough usually | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | rows: --transpose or psql extended view-like functionality 1655860104 | |
1592047502 | https://github.com/simonw/sqlite-utils/issues/555#issuecomment-1592047502 | https://api.github.com/repos/simonw/sqlite-utils/issues/555 | IC_kwDOCGYnMM5e5LeO | chapmanjacobd 7908073 | 2023-06-14T22:00:10Z | 2023-06-14T22:01:57Z | CONTRIBUTOR | You may want to try doing a performance comparison between this and just selecting all the ids with few constraints and then doing the filtering within python. That might seem like a lazy-programmer, inefficient way but queries with large resultsets are a different profile than what databases like SQLITE are designed for. That is not to say that SQLITE is slow or that python is always faster but when you start reading >20% of an index there is an equilibrium that is reached. Especially when adding in writing extra temp tables and stuff to memory/disk. And especially given the `NOT IN` style of query... You may also try chunking like this: ```py def chunks(lst, n) -> Generator: for i in range(0, len(lst), n): yield lst[i : i + n] SQLITE_PARAM_LIMIT = 32765 data = [] chunked = chunks(video_ids, consts.SQLITE_PARAM_LIMIT) for ids in chunked: data.expand( list( db.query( f"""SELECT * from videos WHERE id in (""" + ",".join(["?"] * len(ids)) + ")", (*ids,), ) ) ) ``` but that actually won't work with your `NOT IN` requirements. You need to query the full resultset to check any row. Since you are doing stuff with files/videos in SQLITE you might be interested in my side project: https://github.com/chapmanjacobd/library | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Filter table by a large bunch of ids 1733198948 | |
1590531892 | https://github.com/simonw/sqlite-utils/issues/557#issuecomment-1590531892 | https://api.github.com/repos/simonw/sqlite-utils/issues/557 | IC_kwDOCGYnMM5ezZc0 | chapmanjacobd 7908073 | 2023-06-14T06:09:21Z | 2023-06-14T06:09:21Z | CONTRIBUTOR | I put together a [simple script](https://github.com/chapmanjacobd/library/blob/42129c5ebe15f9d74653c0f5ca4ed0c991d383e0/xklb/scripts/dedupe_db.py) to upsert and remove duplicate rows based on business keys. If anyone has similar problems with above this might help ``` CREATE TABLE my_table ( id INTEGER PRIMARY KEY, column1 TEXT, column2 TEXT, column3 TEXT ); INSERT INTO my_table (column1, column2, column3) VALUES ('Value 1', 'Duplicate 1', 'Duplicate A'), ('Value 2', 'Duplicate 2', 'Duplicate B'), ('Value 3', 'Duplicate 2', 'Duplicate C'), ('Value 4', 'Duplicate 3', 'Duplicate D'), ('Value 5', 'Duplicate 3', 'Duplicate E'), ('Value 6', 'Duplicate 3', 'Duplicate F'); ``` ``` library dedupe-db test.db my_table --bk column2 ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Aliased ROWID option for tables created from alter=True commands 1740150327 | |
1585149909 | https://github.com/simonw/datasette/pull/2052#issuecomment-1585149909 | https://api.github.com/repos/simonw/datasette/issues/2052 | IC_kwDOBm6k_c5ee3fV | hydrosquall 9020979 | 2023-06-09T21:35:00Z | 2023-06-09T21:35:00Z | NONE | Thanks @cldellow for the thoughtful comments! These are all things that I'll keep in mind as we figure out how/if this API is actually used by plugin authors once it's actually out in the world. > Yes, this would work - but it requires me to continue to communicate the column names out of band (in order to fetch the facet data per-column before registering my plugin), vs being able to re-use them from the plugin implementation. Ah, I understand now! Thanks for explaining. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: Javascript Plugin API (Custom panels, column menu items with JS actions) 1651082214 | |
1578840450 | https://github.com/simonw/sqlite-utils/issues/433#issuecomment-1578840450 | https://api.github.com/repos/simonw/sqlite-utils/issues/433 | IC_kwDOCGYnMM5eGzGC | jonafato 392720 | 2023-06-06T14:09:04Z | 2023-06-06T14:09:04Z | NONE | I also ran into this recently. See below for a patch for one possible solution (tested via "it works on my machine", but I don't expect that this behavior would vary a whole lot across terminal emulators and shells). Another possible solution might be to subclass click's `ProgressBar` to keep the logic within the original context manager. Happy to send a PR or for this patch to serve as the basis for a fix that someone else authors. ```patch diff --git a/sqlite_utils/utils.py b/sqlite_utils/utils.py index 06c1a4c..530a3a3 100644 --- a/sqlite_utils/utils.py +++ b/sqlite_utils/utils.py @@ -147,14 +147,23 @@ def decode_base64_values(doc): class UpdateWrapper: - def __init__(self, wrapped, update): + def __init__(self, wrapped, update, render_finish): self._wrapped = wrapped self._update = update + self._render_finish = render_finish def __iter__(self): - for line in self._wrapped: - self._update(len(line)) - yield line + return self + + def __next__(self): + try: + line = next(self._wrapped) + except StopIteration as e: + self._render_finish() + raise + + self._update(len(line)) + return line def read(self, size=-1): data = self._wrapped.read(size) @@ -178,7 +187,7 @@ def file_progress(file, silent=False, **kwargs): else: file_length = os.path.getsize(file.name) with click.progressbar(length=file_length, **kwargs) as bar: - yield UpdateWrapper(file, bar.update) + yield UpdateWrapper(file, bar.update, bar.render_finish) class Format(enum.Enum): ``` | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 1, "eyes": 0} | CLI eats my cursor 1239034903 | |
1577355134 | https://github.com/simonw/sqlite-utils/issues/557#issuecomment-1577355134 | https://api.github.com/repos/simonw/sqlite-utils/issues/557 | IC_kwDOCGYnMM5eBId- | chapmanjacobd 7908073 | 2023-06-05T19:26:26Z | 2023-06-05T19:26:26Z | CONTRIBUTOR | this isn't really actionable... I'm just being a whiny baby. I have tasted the milk of being able to use `upsert_all`, `insert_all`, etc without having to write DDL to create tables. The meat of the issue is that SQLITE doesn't make rowid stable between vacuums so it is not possible to take shortcuts | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Aliased ROWID option for tables created from alter=True commands 1740150327 | |
1575310378 | https://github.com/simonw/sqlite-utils/issues/556#issuecomment-1575310378 | https://api.github.com/repos/simonw/sqlite-utils/issues/556 | IC_kwDOCGYnMM5d5VQq | mcint 601708 | 2023-06-04T01:21:15Z | 2023-06-04T01:21:15Z | CONTRIBUTOR | I've resolved my use, with the line-buffered output and while read loop for line buffered input, but I leave this here so the incremental saving or line-buffered use-case can be explicitly handled or rejected (or deferred). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support storing incrementally piped values 1740026046 | |
1565058994 | https://github.com/simonw/datasette/pull/2053#issuecomment-1565058994 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5dSOey | simonw 9599 | 2023-05-26T23:13:02Z | 2023-05-26T23:13:02Z | OWNER | I should have an extra called `extra_html_context` which bundles together all of the weird extra stuff needed by the HTML template, and is then passed as the root context when the template is rendered (with the other stuff from extras patched into it). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | WIP new JSON for queries 1656432059 | |
1563793781 | https://github.com/simonw/datasette/pull/2053#issuecomment-1563793781 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5dNZl1 | simonw 9599 | 2023-05-26T04:27:55Z | 2023-05-26T04:27:55Z | OWNER | I should split out a `canned_query.html` template too, as something that extends the `query.html` template. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | WIP new JSON for queries 1656432059 | |
1563667574 | https://github.com/simonw/datasette/pull/2053#issuecomment-1563667574 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5dM6x2 | simonw 9599 | 2023-05-26T00:40:22Z | 2023-05-26T00:40:22Z | OWNER | Or maybe... - `BaseQueryView(View)` - knows how to render the results of a SQL query - `QueryView(BaseQueryView)` - renders from `?sql=` - `CannedQueryView(BaseQueryView)` - renders for a named canned query And then later perhaps: - `RowQueryView(BaseQueryView)` - renders the `select * from t where pk = ?` - `TableQueryView(BaseQueryView)` - replaces the super complex existing `TableView` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | WIP new JSON for queries 1656432059 | |
1563663925 | https://github.com/simonw/datasette/pull/2053#issuecomment-1563663925 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5dM541 | simonw 9599 | 2023-05-26T00:32:47Z | 2023-05-26T00:35:47Z | OWNER | I'm going to entirely split canned queries off from `?sql=` queries - they share a bunch of code right now which is just making everything much harder to follow. I'll refactor their shared bits into functions that they both call. Or _maybe_ I'll try having `CannedQueryView` as a subclass of `QueryView`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | WIP new JSON for queries 1656432059 | |
1563663616 | https://github.com/simonw/datasette/pull/2053#issuecomment-1563663616 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5dM50A | simonw 9599 | 2023-05-26T00:32:08Z | 2023-05-26T00:32:08Z | OWNER | Now that I have the new `View` subclass from #2078 I want to use it to simplify this code. Challenge: there are several things to consider here: - The `/db` page without `?sql=` displays a list of tables in that database - With `?sql=` it shows the query results for that query (or an error) - If it's a `/db/name-of-canned-query` it works a bit like the query page, but executes a canned query instead of the `?sql=` query - POST `/db/name-of-canned-query` is support for writable canned queries | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | WIP new JSON for queries 1656432059 | |
1563650990 | https://github.com/simonw/datasette/pull/2080#issuecomment-1563650990 | https://api.github.com/repos/simonw/datasette/issues/2080 | IC_kwDOBm6k_c5dM2uu | simonw 9599 | 2023-05-26T00:08:59Z | 2023-05-26T00:08:59Z | OWNER | I'm not going to document this yet, I want to let it bake for a bit longer first. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | New View base class 1726603778 | |
1563629348 | https://github.com/simonw/datasette/pull/2080#issuecomment-1563629348 | https://api.github.com/repos/simonw/datasette/issues/2080 | IC_kwDOBm6k_c5dMxck | codecov[bot] 22429695 | 2023-05-25T23:31:10Z | 2023-05-26T00:07:34Z | NONE | ## [Codecov](https://app.codecov.io/gh/simonw/datasette/pull/2080?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) Report Patch coverage: **`95.45`**% and project coverage change: **`+0.01`** :tada: > Comparison is base [(`b49fa44`)](https://app.codecov.io/gh/simonw/datasette/commit/b49fa446d683ddcaf6faf2944dacc0d866bf2d70?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 92.40% compared to head [(`df5fd73`)](https://app.codecov.io/gh/simonw/datasette/pull/2080?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) 92.41%. > :exclamation: Current head df5fd73 differs from pull request most recent head e990fbc. Consider uploading reports for the commit e990fbc to get more accurate results <details><summary>Additional details and impacted files</summary> ```diff @@ Coverage Diff @@ ## main #2080 +/- ## ========================================== + Coverage 92.40% 92.41% +0.01% ========================================== Files 39 39 Lines 5768 5790 +22 ========================================== + Hits 5330 5351 +21 - Misses 438 439 +1 ``` | [Impacted Files](https://app.codecov.io/gh/simonw/datasette/pull/2080?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison) | Coverage Δ | | |---|---|---| | [datasette/views/base.py](https://app.codecov.io/gh/simonw/datasette/pull/2080?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Simon+Willison#diff-ZGF0YXNldHRlL3ZpZXdzL2Jhc2UucHk=) | `92.97% <95.45%> (+0.18%)` | :arrow_up: | </details> [:umbrella: View full report in Codecov by Sentry](https://app.codecov.io/gh/simonw/datasette/pull/2080?s… | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | New View base class 1726603778 | |
1563626231 | https://github.com/simonw/datasette/pull/2080#issuecomment-1563626231 | https://api.github.com/repos/simonw/datasette/issues/2080 | IC_kwDOBm6k_c5dMwr3 | simonw 9599 | 2023-05-25T23:25:17Z | 2023-05-25T23:25:17Z | OWNER | I'm going to try using this for the `/-/patterns` page. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | New View base class 1726603778 | |
1563625093 | https://github.com/simonw/datasette/issues/2078#issuecomment-1563625093 | https://api.github.com/repos/simonw/datasette/issues/2078 | IC_kwDOBm6k_c5dMwaF | simonw 9599 | 2023-05-25T23:23:15Z | 2023-05-25T23:23:15Z | OWNER | Rest of the work on this will happen in the PR: - #2080 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Resolve the difference between `wrap_view()` and `BaseView` 1726236847 | |
1563607291 | https://github.com/simonw/datasette/issues/2079#issuecomment-1563607291 | https://api.github.com/repos/simonw/datasette/issues/2079 | IC_kwDOBm6k_c5dMsD7 | simonw 9599 | 2023-05-25T22:56:28Z | 2023-05-25T22:56:28Z | OWNER | Wrote this up as a TIL: https://til.simonwillison.net/http/testing-cors-max-age | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette should serve Access-Control-Max-Age 1726531350 | |
1563597589 | https://github.com/simonw/datasette/issues/2079#issuecomment-1563597589 | https://api.github.com/repos/simonw/datasette/issues/2079 | IC_kwDOBm6k_c5dMpsV | simonw 9599 | 2023-05-25T22:42:07Z | 2023-05-25T22:42:07Z | OWNER | Mystery solved as to why I wasn't seeing this work: <img width="951" alt="CleanShot 2023-05-25 at 15 38 32@2x" src="https://github.com/simonw/datasette/assets/9599/140ee046-69c2-4a68-b7cb-a4603552477c"> I had "Disable Cache" checked! I ran this experiment after un-checking that box: ```javascript fetch('https://latest.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); // And run it again fetch('https://latest.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); // Now try a thing that doesn't serve that max-age header yet: fetch('https://latest-with-plugins.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); // And a second time but within 5s fetch('https://latest-with-plugins.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); // Third time after waiting longer than 5s fetch('https://latest-with-plugins.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); // Try that original one again - still within the 1hr cache time fetch('https://latest.datasette.io/ephemeral/foo/1/-/update', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ test: 'test' }) }); ``` The results show that the cache of 1hr was being obeyed for `latest.datasette.io` while the `latest-with-plugins.datasette.io` default cache of 5s was being obeyed too. <img width="904" alt="image" src="https://github.com/simonw/datasette/as… | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette should serve Access-Control-Max-Age 1726531350 | |
1563588199 | https://github.com/simonw/datasette/issues/2079#issuecomment-1563588199 | https://api.github.com/repos/simonw/datasette/issues/2079 | IC_kwDOBm6k_c5dMnZn | simonw 9599 | 2023-05-25T22:29:47Z | 2023-05-25T22:30:12Z | OWNER | https://fetch.spec.whatwg.org/#http-access-control-max-age says: > Indicates the number of seconds (5 by default) the information provided by the [Access-Control-Allow-Methods](https://fetch.spec.whatwg.org/#http-access-control-allow-methods) and [Access-Control-Allow-Headers](https://fetch.spec.whatwg.org/#http-access-control-allow-headers) [headers](https://fetch.spec.whatwg.org/#concept-header) can be cached. So there was already a 5s cache anyway. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette should serve Access-Control-Max-Age 1726531350 | |
1563587230 | https://github.com/simonw/datasette/issues/2079#issuecomment-1563587230 | https://api.github.com/repos/simonw/datasette/issues/2079 | IC_kwDOBm6k_c5dMnKe | simonw 9599 | 2023-05-25T22:28:20Z | 2023-05-25T22:28:20Z | OWNER | Weird... after the deploy went out: <img width="945" alt="image" src="https://github.com/simonw/datasette/assets/9599/a8abb12a-446b-4970-8e76-3b218b6d02c7"> But the request did indeed get the new header: <img width="951" alt="image" src="https://github.com/simonw/datasette/assets/9599/7c72578c-9250-47d3-a4d2-1ece8c07ef84"> So I'm not sure why it's making multiple `POST` requests like that. Maybe it's because the attempted `POST` failed with a 404? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette should serve Access-Control-Max-Age 1726531350 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
updated_at (date) >1000 ✖