raytale / ray Goto Github PK

在使用example中使用分布式转账测试时，扣款事件无法正常处理

Kafka 消息队列 相比 RabbitMq 有很多优势，请求增加Kafka的支持

Per convention, the index name should be named after the table name:

INDEX account_event_id_unique unique(StateId,TypeCode,UniqueId),
INDEX account_event_Version unique(StateId, Version)

Should be

INDEX {subTable.SubTable}_event_id_unique unique(StateId,TypeCode,UniqueId),
INDEX {subTable.SubTable}_event_Version unique(StateId, Version)

希望增加一个简单注册登录的DEMO

账户1的初始余额为0
账户2的初始余额为0
Please enter the number of executions
3
warn: Microsoft.Orleans.Networking[0]
Exception reading message Response S127.0.0.1:30000:0*grn/5C399409/00000001@3f666ab7->*cli/492b42bc@871399aa #6: from remote endpoint 127.0.0.1:30000 to local endpoint 127.0.0.1:57243: System.IO.FileNotFoundException: Could not load file or assembly 'Ray.Core, Culture=neutral, PublicKeyToken=null'. 系统找不到指定的文件。
File name: 'Ray.Core, Culture=neutral, PublicKeyToken=null'
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, RuntimeAssembly assemblyContext, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, AssemblyLoadContext assemblyLoadContext)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, StackCrawlMark& stackMark, AssemblyLoadContext assemblyLoadContext)
at System.Reflection.Assembly.Load(AssemblyName assemblyRef, StackCrawlMark& stackMark, AssemblyLoadContext assemblyLoadContext)
at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
at Orleans.Runtime.CachedTypeResolver.<>c__DisplayClass7_0.g__ResolveAssembly|0(AssemblyName assemblyName)
at System.TypeNameParser.ResolveAssembly(String asmName, Func2 assemblyResolver, Boolean throwOnError, StackCrawlMark& stackMark) at System.TypeNameParser.ConstructType(Func2 assemblyResolver, Func4 typeResolver, Boolean throwOnError, Boolean ignoreCase, StackCrawlMark& stackMark) at System.TypeNameParser.GetType(String typeName, Func2 assemblyResolver, Func4 typeResolver, Boolean throwOnError, Boolean ignoreCase, StackCrawlMark& stackMark) at System.Type.GetType(String typeName, Func2 assemblyResolver, Func4 typeResolver, Boolean throwOnError) at Orleans.Runtime.CachedTypeResolver.TryPerformUncachedTypeResolution(String fullName, Type& type, Assembly[] assemblies) at Orleans.Runtime.CachedTypeResolver.TryPerformUncachedTypeResolution(String name, Type& type) at Orleans.Runtime.CachedTypeResolver.TryResolveType(String name, Type& type) at Orleans.Serialization.TypeSerializer.GetTypeFromName(String assemblyQualifiedTypeName, Boolean throwOnError) at Orleans.Serialization.TypeSerializer.GetTypeFromTypeKey(TypeKey key, Boolean throwOnError) at Orleans.Serialization.ILBasedExceptionSerializer.Deserialize(Type expectedType, IDeserializationContext outerContext) at Orleans.Serialization.ILBasedSerializer.Deserialize(Type expectedType, IDeserializationContext context) at Orleans.Serialization.SerializationManager.DeserializeInner[TContext,TReader](SerializationManager sm, Type expected, TContext context, TReader reader) at Orleans.Serialization.SerializationManager.DeserializeInner(Type expected, IDeserializationContext context) at Orleans.Serialization.BuiltInTypes.DeserializeOrleansResponse(Type expected, IDeserializationContext context) at Orleans.Serialization.SerializationManager.DeserializeInner[TContext,TReader](SerializationManager sm, Type expected, TContext context, TReader reader) at Orleans.Runtime.Messaging.MessageSerializer.OrleansSerializer1.Deserialize(ReadOnlySequence1 input, T& value) at Orleans.Runtime.Messaging.MessageSerializer.TryRead(ReadOnlySequence1& input, Message& message)
at Orleans.Runtime.Messaging.Connection.ProcessIncoming()

这里的命名也有些怪异

这段代码是只能在客户端还是服务端也可以的，还有，这个core 和read 是约定的写法吗？
HandlerStart.Start(new[] { "Core", "Read" }, client.ServiceProvider, client)

In order to foster an inclusive environment, we need a code of conduct, perhaps we can use the on here:

https://www.contributor-covenant.org/version/2/0/code_of_conduct/

We need to get our documentation started.

This story will setup the infrastructure for the docs.

没看到demo和文档有相关描述

The libraries should target netstandard2.0 to increase application target runtimes.

对orleans有一定的了解了，对你们这个项目也很感兴趣。
如何加入你们，一起维护这个项目？

我在运行ray 的example 的时候，很好奇想问下，数据库操作应该在那个代码里写，grain 里还是 eventhandle 处理

我建议换掉RabbitMQ。

这两种配置可否简化来提高易用性？比如在WorkFlowGrain类上面添加[Attribute]和根据Grain名称默认配置消息队列名称？

用户自定义数据作为 IEvent { T Body } 的方式存在，可以更加有利于框架代码的维护。
用户自定义事件的本质其实是自定义了其中的数据，这些自定义数据和时间的原生数据共同组成了事件。
如此设计会更加符合单一职责原则。

Added @ https://gitter.im/RayTale/Ray

i make a simple demo,only a interface , inherit IStock

InvalidOperationException: Cannot find generated GrainReference class for interface 'QtShop.IGrains.IStock'

What's the reason?

EventHandlerExtensions

没有交流的地方吗，qq群

第一次DbGrain抛异常后消息队列没有被ack掉，此bug在昨天已解决。但第二次从消息队列中拉取unacked数据再次抛异常后消息队列却被ack掉了。如下两张图：
正常处理，消息队列没有被删除

拉取unacked中的数据后，DbGrain抛异常消息队列丢失

:)

好像接口使用了ValueTask类型，实现却是使用了Task，这是？？？求解答，大大

`严重性 代码 说明 项目 文件 行 禁止显示状态
错误 MSB3073 命令“"dotnet" "C:\Users\sunrise.nuget\packages\microsoft.orleans.orleanscodegenerator.build\2.1.0\build..\tasks\netcoreapp2.0\Orleans.CodeGeneration.Build.dll" "@obj\Debug\netstandard2.0\codegen\Ray.IGrains.orleans.g.args.txt"”已退出，代码为 3。 Ray.IGrains C:\Users\sunrise.nuget\packages\microsoft.orleans.orleanscodegenerator.build\2.1.0\build\Microsoft.Orleans.OrleansCodeGenerator.Build.targets 82

`

是不是哪里做错了？

There is a Producer attribute in the both RabbitMQ and Kafka assemblies.

Shouldn't this be able to be set by configuration?

The attribute should be part of the framework and allow you to configure per class.

创建多个silo 。如何让客户端动态的选择silo？
silo数量可能会增加，增加后客户端能动态发现并使用吗？
例如客户端for 1000次。平均的分散到10个silo 。每个100次。
代码应该是什么样的？
不是很清楚该怎么写。谢谢。

在调用 followUnitContainer.Register(ObserverUnit.From(serviceProvider)); 代码后抛出异常，原因是由于内部调用tryAdd方法时未能通过，手动抛出异常，不知具体原因

The EventStorage code uses ExecuteAsync, etc.. It's a long-standing bug in MySql.Data (bug 70111) that async I/O is not implemented correctly; thus this method will actually run synchronously. (See also here and here on Stack Overflow.)

To fix this, you could switch to https://github.com/mysql-net/MySqlConnector, an OSS replacement for MySql.Data that supports true asynchronous I/O.

If you're interested in this, I'd be happy to open a PR.