~lattis


#205 Crash when arrow key pressed if account has invalid source 1 year, 4 months ago

bug added by ~lattis on ~sircmpwn/aerc2

#205 Crash when arrow key pressed if account has invalid source 1 year, 4 months ago

Ticket created by ~lattis on ~sircmpwn/aerc2

In my accounts.conf, I have:

[Account Name]
source = invalid

Then when start aerc and can see this error in the bottom bar: Account Name: Unknown backend

If I type :quit it exits nicely, but if I press up or down I get this error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x82eaedf]

goroutine 1 [running]:
git.sr.ht/~sircmpwn/aerc/widgets.(*MessageList).Store(...)
        /home/lattis/aerc/widgets/msglist.go:170
git.sr.ht/~sircmpwn/aerc/widgets.(*AccountView).Store(...)
        /home/lattis/aerc/widgets/account.go:165
git.sr.ht/~sircmpwn/aerc/commands/account.NextPrevMessage(0x8d34940, 0x8c10060, 0x1, 0x1, 0x8ca26d4, 0x1)
        /home/lattis/aerc/commands/account/next.go:57 +0x17f
git.sr.ht/~sircmpwn/aerc/commands.(*Commands).ExecuteCommand(0x8c746a0, 0x8d34940, 0x8de45f0, 0x4, 0x3, 0x4)
        /home/lattis/aerc/commands/commands.go:47 +0xfc
main.main.func1(0x8de45f0, 0x4, 0x74, 0x7)
        /home/lattis/aerc/aerc.go:102 +0xa1
git.sr.ht/~sircmpwn/aerc/widgets.(*Aerc).BeginExCommand.func1(0x8de45f0, 0x4)
        /home/lattis/aerc/widgets/aerc.go:282 +0x44
git.sr.ht/~sircmpwn/aerc/widgets.(*ExLine).Event(0x8c581e0, 0x846f180, 0x8c58280, 0x8c58280)
        /home/lattis/aerc/widgets/exline.go:47 +0xf8
git.sr.ht/~sircmpwn/aerc/widgets.(*Aerc).Event(0x8d34940, 0x846f180, 0x8c58280, 0x8c58280)
        /home/lattis/aerc/widgets/aerc.go:141 +0x362
git.sr.ht/~sircmpwn/aerc/widgets.(*Aerc).simulate(0x8d34940, 0x8c65840, 0x6, 0x8)
        /home/lattis/aerc/widgets/aerc.go:134 +0x97
git.sr.ht/~sircmpwn/aerc/widgets.(*Aerc).Event(0x8d34940, 0x846f180, 0x8d38720, 0x8d38500)
        /home/lattis/aerc/widgets/aerc.go:156 +0x2bc
git.sr.ht/~sircmpwn/aerc/lib/ui.(*UI).Tick(0x8d92030, 0x838da00)
        /home/lattis/aerc/lib/ui/ui.go:86 +0x99
main.main()
        /home/lattis/aerc/aerc.go:131 +0x333

This is probably low-priority since its cause is a bad config file, but I thought I'd make it known.

#184 502 error when logging in 1 year, 8 months ago

on ~sircmpwn/git.sr.ht

REPORTED RESOLVED FIXED

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

awesome, it works! Thanks so much

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

The parameters are

exchange=...

scopes=.../jobs:write,keys:read,profile:read

state=/?

where ... is an encoded value of some kind

not sure if this is helpful or not, just letting you know in case you see something obvious

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

sure,

  1. close browser
  2. delete cookies
  3. open browser and go to https://git.sr.ht
  4. click the login link at the bottom of page, which redirects me to meta.sr.ht/login
  5. fill in my valid credentials and click log in
  6. get redirected to git.sr.ht/oauth/callback where I get a page containing only a header with the text "Internal Server Error"

#184 502 error when logging in 1 year, 8 months ago

on ~sircmpwn/git.sr.ht

RESOLVED INVALID REPORTED

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

to clarify, this is happenning when I follow the log in link on the git.sr.ht site after logging in to meta.

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

actually, scratch that, it was working when I was logged out, but I had to log back in to comment on this issue and I just tried accessing the git.sr.ht login page via the link on the homepage and got the 502.

#184 502 error when logging in 1 year, 8 months ago

Comment by ~lattis on ~sircmpwn/git.sr.ht

Hey, the issue was apparently related to my cookies because when I cleared them the login page loaded fine. It was still broken until that point. Perhaps somehow a corrupt cookie got set. If you have any idea what that cookie could be called and are interested, I could send you a copy. I backed up my cookies before deleting thim.