Yunlu Wen

It's been years

> SqlSessionFactoryBean 用这个方法解决了问题，这个问题的根因在哪里有人知道吗？

> 已修复，在config配置中注入SqlSessionFactory Bean，里面手动配置扫描包即可 @bean(name ={"SqlSessionFactory"}) public SqlSessionFactory localhostSqlSessionFactory(@qualifier("DataSource") DataSource dataSource) throws Exception { SqlSessionFactoryBean sqlSessionFactory = new SqlSessionFactoryBean(); //因为new了一个SqlSessionFactoryBean 所以yml的mapper-locations的配置没有用，需要手动配置扫描的包 ResourcePatternResolver resolver = new PathMatchingResourcePatternResolver(); sqlSessionFactory.setMapperLocations(resolver.getResources("classpath*:/mapper/*.xml")); //设置扫描的实体包 sqlSessionFactory.setTypeAliasesPackage("com.abc.model"); sqlSessionFactory.setDataSource(dataSource); return...

I think it's nice to have something like this, we're currently having a hard time troubleshooting inconsistent Segments... This doesn't happen a lot though

any updates?

I saw another version today. Didn't find an exactly same one after searching through the issues, but there is a same one under an influxdb topic, here's the stack trace...

I think int64 type in Golang clearly indicates int64 format, why is it still necessary to apply additional tags?

I came across a similar issue today but it's nothing to do with serializer. I was debugging the application on a remote server with https disable. However the cookie was...

I think it's useful when there are immediate events which are trivial. There also could be cases where one event triggers another, as described in [this blog](https://ziobrando.blogspot.com/2013/11/introducing-event-storming.html)

Any news on this so far?