frairon ( Franz Eichhorn )

I also have one of these and I'm willing to investigate this, I'm a low to mid skill user, but if you need me to type in any commands I'm happy to.
I use Ubuntu 20.10 and 20.04 and can test it on a large variety of workstations.

patricklibert

comment created time in 11 days

issue commentnmikhailov/Validity90

06cb:009b

python-validity seems to have more activity and already supports 009a

KonstaX

comment created time in 22 days

issue commentnmikhailov/Validity90

Add support for 06cb:00be

I too would like to see this supported ☺️

JThyroff

comment created time in 23 days

PR opened lovoo/goka

fix topic manager stream retention not in milliseconds

Noticed that topics created with TopicManager.EnsureStreamExists had much longer retention than expected, and setting it to -1 to avoid deletion doesn't work either. %d on a duration seems to print out number of microseconds, and not milliseconds:

t := 1 * time.Hour
fmt.Printf("%d", t)

gives: 3600000000000

+1 -1

1 commit in tlinford/goka/tree/master lovoo/goka/tree/master

0 comment

1 changed file

pr created time in a month

issue commentlovoo/goka

Processor does not stop on error

#291 approved @frairon

tlinford

comment created time in a month

issue openedlovoo/goka

Processor does not stop on error

If I understand the documentation processor.Run should exit if an error happens in the callback, instead it seems to get stuck retrying forever. For example adapting https://github.com/lovoo/goka/blob/master/examples/1-simplest/main.go to panic or call ctx.Fail:

func runProcessor() {
	cb := func(ctx goka.Context, msg interface{}) {
		panic("something went wrong")
	}

	g := goka.DefineGroup(group,
		goka.Input(topic, new(codec.String), cb),
		goka.Persist(new(codec.Int64)),
	)

	p, err := goka.NewProcessor(brokers, g)
	if err != nil {
		log.Fatalf("error creating processor: %v", err)
	}
	ctx, cancel := context.WithCancel(context.Background())
	done := make(chan bool)
	go func() {
		defer close(done)
		if err = p.Run(ctx); err != nil {
			log.Fatalf("error running processor: %v", err)
		} else {
			log.Printf("Processor shutdown cleanly")
		}
	}()

	wait := make(chan os.Signal, 1)
	signal.Notify(wait, syscall.SIGINT, syscall.SIGTERM)
	<-wait   // wait for SIGINT/SIGTERM
	cancel() // gracefully stop processor
	<-done
}

results in:

2020/12/21 10:05:18 [Processor example-group] Error executing group consumer: kafka: error while consuming example-stream/3: something went wrong
runProcessor.func1
        test/main.go:42
2020/12/21 10:05:24 [Processor example-group] Error executing group consumer: kafka: error while consuming example-stream/3: something went wrong
runProcessor.func1
        test/main.go:42
2020/12/21 10:05:30 [Processor example-group] Error executing group consumer: kafka: error while consuming example-stream/3: something went wrong
runProcessor.func1
        test/main.go:42
2020/12/21 10:05:35 [Processor example-group] Error executing group consumer: kafka: error while consuming example-stream/3: something went wrong
runProcessor.func1

created time in a month

pull request commentlovoo/goka

#239 integrate sarama consumer group

Hey @fkarakas, as you said the "pure GO" implementation was the main driver for the decision. CGO always was and is a problem for us, we had to take extra effort to use goka since this was a requirement. Also goka internally we focused mainly on sarama and supporting confluentlib would have been extra effort. We decided to focus on sarama since it is widely used in the go world for working with kafka and we did not see any mayor limitations or drawbacks when using it.

Regarding the support. Sure librdkafka may get longer support but even if sarama would be deprecated today we would be able to integrate and switch to librdkafka; for us the effort would be almost the same then designing goka with interchangeable kafka libs.

But still. If that's a blocker for you and others we can talk about changing this in future releases.

frairon

comment created time in 2 months

Pull request review commentlovoo/goka

add group getter in context

 func (ctx *cbContext) Offset() int64 { 	return ctx.msg.Offset } +func (ctx *cbContext) Group() Group {+	return Group(ctx.graph.group)

No it's a mistake +1.

*GroupGraph can be nil ? I add check nil ?

qneyrat

comment created time in 2 months

PR opened lovoo/goka

add group getter in context

+7 -0

1 commit in qneyrat/goka/tree/context-group lovoo/goka/tree/master

0 comment

1 changed file

pr created time in 2 months

issue commentnmikhailov/Validity90

TO ANYONE LOOKING FOR UPDATES ON THE PROJECT

Thanks. Just worked on my X1C6 with 06cb:009a on stock Ubuntu 20.04 (gnome desktop) with dual-boot windows.

josh-palan

comment created time in 2 months

issue commentnmikhailov/Validity90

TO ANYONE LOOKING FOR UPDATES ON THE PROJECT

Thank you so much for this, I was starting to think I'd never be able to use the fingerprint sensor!!!

josh-palan

comment created time in 2 months

issue commentnmikhailov/Validity90

TO ANYONE LOOKING FOR UPDATES ON THE PROJECT

And the T460p on arch and ubuntu But he other hardware fprinter should work there, too (Hoping for upstreaming into the vanilla driver)

josh-palan

comment created time in 2 months

issue openednmikhailov/Validity90

TO ANYONE LOOKING FOR UPDATES ON THE PROJECT

I waited and watched this repository for my than 3 years waiting on support for my Lenovo. I still see people landing on this project asking for support for their reader. Unfortunately, it appears this repo is in a dead state and has been for some time now. :/

That said, I was able to install and use the fprint drivers from the following project: https://github.com/uunicorn/python-validity

That repo works for me using a Lenovo T580, synaptics device ID 06cb:009a, on Ubuntu 18.04 and 20.04 using the plasma desktop. I would highly suggest that anyone who hasn't checked it out yet heads over there to see if it'll work for them as well, especially since the project seems very much alive.

created time in 2 months

issue commentnmikhailov/Validity90

How to test on Lenovo Yoga? ID 06cb:0081 Synaptics, Inc.

Hi @nmikhailov , any news about support of 06cb:0081?

leshokunin