"Invalid fingerprint" when doing a lit publish

[Geoff Bourne]

Hi,

I have seem to have successfully authenticated, using

./lit auth itzg

and then claimed the organization "virgo-agent-toolkit" using

./lit claim virgo-agent-toolkit

However, when I go to push a new version of the "virgo" package I get the following and the new version indeed doesn't seem published by using https://luvit.io/lit.html#name:virgo . The fingerprint it mentions is my proper SSH identity that was picked up during the lit auth.

➜  ~/git/virgo-base-agent git:(master) ./lit publish .

lit version: 3.5.4

luvi version: v2.7.6

command: publish .

load config: /Users/geof0549/.litconfig

checking for updates: virgo-agent-toolkit/virgo

connecting: wss://lit.luvit.io/

compiling filter: /Users/geof0549/git/virgo-base-agent/** excludes by default (first rule is positive)

including: client/client.lua

including: client/connection_messages.lua

...SNIP...

including: utils.lua

including: winsvcwrap.lua

no change: virgo-agent-toolkit/virgo/v2.1.7

skipping: virgo-agent-toolkit/vi...@2.1.6: Obsoleted version

publishing: virgo-agent-toolkit/virgo/v2.1.7

fail: [string "bundle:libs/codec.lua"]:123: Invalid fingerprint 35:d9:8b:10:55:4b:62:5a:de:3f:c9:e7:9d:19:b0:d9 for virgo-agent-toolkit

stack traceback:

[C]: in function 'assert'

[string "bundle:libs/codec.lua"]:123: in function 'read'

[string "bundle:libs/rdb.lua"]:221: in function 'push'

[string "bundle:libs/core.lua"]:286: in function 'publish'

[string "bundle:commands/publish.lua"]:9: in function <[string "bundle:commands/publish.lua"]:1>

[string "bundle:main.lua"]:52: in function <[string "bundle:main.lua"]:39>

[C]: in function 'xpcall'

[string "bundle:main.lua"]:39: in function <[string "bundle:main.lua"]:31>

[Tim Caswell]

I think I've seen this before.  Have you tried resetting (deleting) your local `$HOME/.litconfig` and `$HOME/.litdb` and authing again to see if that helps.  Also Ryan or I could look to see what's exactly on the server.

On Monday, October 9, 2017 at 8:34:50 AM UTC-5, Geoff Bourne wrote:

Hi,

I have seem to have successfully authenticated, using

./lit auth itzg

and then claimed the organization "virgo-agent-toolkit" using

./lit claim virgo-agent-toolkit

However, when I go to push a new version of the "virgo" package I get the following and the new version indeed doesn't seem published by using https://luvit.io/lit.html#name:virgo . The fingerprint it mentions is my proper SSH identity that was picked up during the lit auth.

➜  ~/git/virgo-base-agent git:(master) ./lit publish .

lit version: 3.5.4

luvi version: v2.7.6

command: publish .

load config: /Users/geof0549/.litconfig

checking for updates: virgo-agent-toolkit/virgo

connecting: wss://lit.luvit.io/

compiling filter: /Users/geof0549/git/virgo-base-agent/** excludes by default (first rule is positive)

including: client/client.lua

including: client/connection_messages.lua

...SNIP...

including: utils.lua

including: winsvcwrap.lua

no change: virgo-agent-toolkit/virgo/v2.1.7

skipping: virgo-agent-toolkit/virgo@2.1.6: Obsoleted version

[Tim Caswell]

Also what kind of KEY do you have locally.  I've personally switched to ed25519 keys for most stuff, but lit can only work with RSA keys.

[Geoff Bourne]

Thanks, Tim, that fixed it! I had purged my .litdb before, but that hadn't helped. Now that I deleted the .litconfig that fixed it.

FWIW, I'm using an RSA key.

[Tim Caswell]

Glad it fixed it!

--
You received this message because you are subscribed to the Google Groups "luvit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to luvit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.