blaze
> Yolo detector is static in the current implementation I believe. Can't have 2 in the same application easily. Isn't that a bug when I want to make a pipeline...
For now we can live with that by manual code reformatting (probably, once it can be done automatically): ```C# [ExcludePointcut] //or exclude all async voids on the level of assembly...
Very well, thank you!
This technique is very useful. I need a bit other scenario, by default all assembly properties must be weaved by the aspect - it's important from security point of view...
[CompilerGenerated] looks like a good idea!
I think, that behavior must be specified per aspect how to react on [CompilerGenerated].
Yes, that's clear. In my doc normal text and code have different font-sizes, it means that each pasted code must be separately set to the new font-size value...and it's annoying......
Probably this is the same [bug](https://github.com/Formicka/exchangerate.host/issues/37) , inverted only HBAR, but UAH is shown correctly
If you remove logEntry newly connected peers will not be able to restore the state of the database, nobody knows which peer will be chosen as a restoration point, so...