eba7f1c628
When no line numbers are available, don't display them
...
(Whether this is needed in practice is unsure; I implemented this
before I noticed that in such cases frame.context_line is also
always missing in my data-set; but I havent' checked the spec and
leaving it in defensively really won't hurt)
2024-04-03 10:29:40 +02:00
f40ee395ee
Make issues/templatetags more robust
...
(the need for which was exposed by the recently added tests)
2024-04-03 10:15:13 +02:00
17b5c0d089
Add integration test for issue-ingestion & rendering
2024-04-03 09:52:50 +02:00
cc9ece8960
Date-filter correction
...
The worst April 1st joke is an April 01st joke
2024-04-01 23:23:41 +02:00
cfdfa67982
Use an (already available) denormalized value
2024-04-01 23:06:34 +02:00
f69befd20a
Harmonize displayed timestamps
...
I picked server-time as the thing which has the most likeliness of being correct
2024-04-01 23:00:19 +02:00
02a29a9029
More pieces of info for the details page
2024-04-01 22:39:03 +02:00
179056192d
push request and log-entry handling into 'details' tab
2024-04-01 22:23:34 +02:00
477ec43487
Fix bug with pygmentize and just-newline lines
2024-04-01 22:22:12 +02:00
85b160d7f8
All issue-views need the mute_options in their context
...
'I see a pattern here'
2024-04-01 22:09:59 +02:00
03225c85e1
issue seen at in the RHS box: use real values
...
the fake nonsense was already confusing me
2024-04-01 22:06:34 +02:00
999f91dfac
non-event-specific issue detail pages: show _some_ event-related stuff at the top
...
(before this commit, switching between the event-related and non-event-related views would show
the size of the box at the top change
2024-04-01 21:59:03 +02:00
192ab2d5dc
Added (dumped) the user info on the details page
2024-03-31 23:35:55 +02:00
212baabe73
Fix on previous commit
2024-03-31 23:26:10 +02:00
b3a86ef38b
pygmentize: deal with context_line=None
2024-03-31 23:24:36 +02:00
37575a7001
Breadcrumbs, at least implement _something_
2024-03-31 23:04:15 +02:00
602678b941
Add 'plain' view (Python-specific; only half-tested)
2024-03-30 23:10:18 +01:00
d411aff46f
Textual ('collapse')
2024-03-30 23:08:50 +01:00
2de91c998c
Show-raise; bigger show x buttons
2024-03-30 22:40:46 +01:00
c6ba49269e
rename issue_stacktrace.js (reflecting what it actually is)
...
which exposed a needed cleanup
2024-03-30 22:26:02 +01:00
d429ccfc56
Resolve/mute buttons: on their own line on small screens
2024-03-30 22:22:33 +01:00
9275657a54
Detail page: buttons will not be squeezed by exc_msg
...
button-containing-div will not shrink;
the texts have overflow-hidden and ellipsis
2024-03-30 22:16:19 +01:00
0f19fbd30c
stacktrace in-app vs non-in-app: distinguish using bold/italics rather than bg-color
2024-03-30 21:55:52 +01:00
09f7911da9
'key info' box: put in better placeholders than 'Lorem ipsum'
2024-03-30 21:38:34 +01:00
601b27b3da
Add command to store events
2024-03-30 21:15:39 +01:00
2966230238
Show 2 types of IDs at the top of the event-admin
2024-03-30 21:10:27 +01:00
fea9d5a90d
Push comments into help-text
2024-03-30 21:02:26 +01:00
61a422719b
send_default_pii for our own error-reporting
...
in a self-hosted environment, this is what makes sense
2024-03-30 20:56:27 +01:00
3aae32b54f
blank=True; as implied by the default=''
2024-03-30 20:50:02 +01:00
041ffd7ef7
Clobbered pdf restored
2024-03-30 11:56:29 +01:00
6745d0e112
Match pygments input-line-counts with output-line-counts and test that this works
2024-03-29 20:49:05 +01:00
aca96e7dc9
Remove workaround for pygments empty newlines; there's a real solution
2024-03-29 18:35:43 +01:00
475977529a
Parse pygment's result, and apply it in my own way (ol/li)
...
Why?
* it's something I had working, and I like the way it looked
* scrolling in the just-do-pygments setup is not as I want it
* even if I don't want an ol/li approach in the future, getting my hands dirty with this output is useful
2024-03-29 17:54:08 +01:00
12bbde947a
Use pygments, the simple way
...
as per their quickstart
2024-03-29 17:29:06 +01:00
b13795b59c
Correct line numbers in stacktrace
2024-03-28 23:28:56 +01:00
6f19528290
hide 'key info' only from lg down
2024-03-28 23:17:40 +01:00
d489b56645
Padding: slightly less squeeze-in of code/vars
2024-03-28 23:08:51 +01:00
49ddf409a6
Fix: one border too many
2024-03-28 23:04:26 +01:00
566a958d1b
Fix ugly cut-off on exception-raising line when another line overflows
2024-03-28 23:03:11 +01:00
6a402fca67
Some sharing of space between LHS/RHS;
...
and the LHS should fill a bunch of space, even if it contains very little
2024-03-28 22:56:40 +01:00
14860a8690
Various fine-tuning of margin & padding
2024-03-28 22:43:02 +01:00
688725fe63
Vars table: slight enhancements (bottom border; remove when no-vars)
2024-03-28 22:40:35 +01:00
ec60aafcf5
Restore border in collapsable frames; add comments for divs
2024-03-28 22:39:29 +01:00
98aee3d5b6
code listings and vars: distinguish visually more clearly by 'bringing them in'
...
i.e. left/right margins/padding
2024-03-28 20:36:45 +01:00
fd4bc3aefd
Implement horizontal scrollbar for code-listings
...
non-trivial (for me); challenges were:
1. the flex-item (much higher up in the dom tree) must have the overflow too
2. setting overflow hides line-numbers (which are list-stylings); use list-inside to bring them back in
3. setting list-inside creates an undesired line-break; make the div elem an inline elem to fix this
4. margin can be made much smaller (it was made big when the list-items weren't inside yet, and we needed space for them)
2024-03-28 20:23:47 +01:00
a6482f0f7f
Remove issue.js from issues/base.html
...
it's entirely specific to the stacktrace code
2024-03-28 20:14:58 +01:00
02f2ba2e8d
Don't stretch out the container (and border) of the LHS box when the RHS is bigger
2024-03-28 19:25:34 +01:00
ed6b1238af
2 boxes on the RHS; the main idea before refinements
2024-03-28 18:36:34 +01:00
aece9f2c4e
Issue stacktrace: Don't show variables on the RHS
...
in the end I find this harder to read. better to keep them in the same place always.
making this move prepares us for the 'key issue insights' box too, because it provides
insight in the 'amount of space used' by the main tab (for which the code lines in the
stacktrace will be the largest)
2024-03-28 17:59:52 +01:00
6059bea0ae
Inline _bottom_nav_bar and add some comments for containers
2024-03-28 17:53:47 +01:00
Klaas van Schelven