I just had this[1] crash while loading a buffer with has:lkml.
Crash occurs in,
@threads = @ts.threads.select { |t| !@hidden_threads[t] }.sort_by { |t|
[t.date, t.first.id] }.reverse
Is this perhaps the result of an index inconsistency? It seems to me
that t.first should never be nil. Seems like sup is very susceptible to
these nils slipping in unexpectedly. Is there perhaps a better way to
deal with it other than crashing the client? Seems like a pretty extreme
measure (although granted, it''s a pretty serious issue as well)
- Ben
[1] Exception log
--- RuntimeError from thread: load threads for thread-index-mode
wrong id called on nil
/opt/exp/sup/lib/sup.rb:17:in `id''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `update''
/opt/exp/sup/lib/sup/hook.rb:121:in `sort_by''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `each''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `sort_by''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `update''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:223:in `synchronize''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:223:in `update''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:637:in
`__unprotected_load_n_threads''
(eval):12:in `load_n_threads''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:609:in
`load_n_threads_background''
/opt/exp/sup/lib/sup.rb:77:in `reporting_thread''
/opt/exp/sup/lib/sup.rb:75:in `initialize''
/opt/exp/sup/lib/sup.rb:75:in `new''
/opt/exp/sup/lib/sup.rb:75:in `reporting_thread''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:608:in
`load_n_threads_background''
/opt/exp/sup/lib/sup/modes/thread-index-mode.rb:679:in
`__unprotected_load_threads''
(eval):12:in `load_threads''
/opt/exp/sup/lib/sup/modes/label-search-results-mode.rb:33:in
`spawn_nicely''
/opt/exp/sup/lib/sup/modes/label-list-mode.rb:93:in `select_label''
/opt/exp/sup/lib/sup/mode.rb:51:in `send''
/opt/exp/sup/lib/sup/mode.rb:51:in `handle_input''
/opt/exp/sup/lib/sup/buffer.rb:267:in `handle_input''
/usr/bin/sup:238