Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 18 10:25
    biohazard999 closed #632
  • Aug 18 10:25
    biohazard999 commented #632
  • Aug 04 16:33
    TheFellow opened #668
  • Jul 30 00:06
    TheFellow opened #667
  • Jul 30 00:01
    TheFellow edited #666
  • Jul 28 21:42
    TheFellow opened #666
  • Jul 21 00:33
    TheFellow opened #665
  • Jul 20 22:06

    jeremydmiller on master

    Apply configurations when updat… Pulsar allows native scheduled … Rename classes to be specific t… and 5 more (compare)

  • Jul 20 22:06
    jeremydmiller closed #664
  • Jul 20 22:04

    jeremydmiller on master

    Make exception_message and exce… Prepend all jasper tables with … Fix typo (compare)

  • Jul 20 22:04
    jeremydmiller closed #659
  • Jun 30 13:41
    JarrodJ83 review_requested #664
  • Jun 24 15:11
    JarrodJ83 opened #664
  • Jun 23 11:14

    JarrodJ83 on pulsar-cleanup

    Add Kafka readme and example (compare)

  • Jun 23 00:32

    JarrodJ83 on pulsar-cleanup

    Ignore tests not applicabale to… Implement KafkaCallbackChannel (compare)

  • Jun 22 23:39

    JarrodJ83 on pulsar-cleanup

    Update pkg details Implement DotPulsar channel cal… (compare)

  • Jun 22 17:53

    JarrodJ83 on pulsar-cleanup

    Apply configurations when updat… Pulsar allows native scheduled … Rename classes to be specific t… (compare)

  • Jun 15 12:15

    jeremydmiller on master

    Optional Parallel Rabbit MQ lis… (compare)

  • Jun 04 20:51
    JarrodJ83 commented #629
  • Jun 04 20:51
    JarrodJ83 commented #629
Svein Ellingsen
@lovmoen
Has there been a recent change in how Jasper uses Marten/database? When I started my project back in May, I set up marten backed persistence and everything worked falwlessly until I recently deployed my project with a fresh/empty database. Now I keep getting these exeptions: '[ERR] Running Recover persisted outgoing messages
Npgsql.PostgresException (0x80004005): 42P01: relation "public.jasper_outgoing_envelopes" does not exist' and 'Npgsql.PostgresException (0x80004005): 42P01: relation "public.jasper_incoming_envelopes" does not exist'. I set the marten option AutoCreateSchemaObjects to AutoCreate.All. Are there other (new?) initialization procedures that need to be performed?
Svein Ellingsen
@lovmoen
If I manually restore the tables from my old database, the exceptions go away.
Jeremy D. Miller
@jeremydmiller
Yeah, there has. I did a lot of work this spring to put the Sql Server backed persistence and Postgresql backed persistence on the same common core, so it got much less Marten-centric. Slightly different table structure now
The docs are up to date on how to seed your database, but I didn’t do anything for conversion:(
Svein Ellingsen
@lovmoen
Should have seen that Thanks! :)
Svein Ellingsen
@lovmoen
Any idea what could cause this on startup:
[11:09:25 FTL] An error occurred stopping the application
System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Jasper.Messaging.Durability.DurabilityAgent.StopAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func2 callback) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func2 callback)
at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.StopAsync(CancellationToken token)
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Jasper.Messaging.Durability.DurabilityAgent.StopAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func`2 callback)<---
[11:09:25 FTL] An error occurred stopping the application                                                                                             
System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at Jasper.Messaging.Durability.DurabilityAgent.StopAsync(CancellationToken cancellationToken)                                                      
   at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func`2 callback)                                                       
   --- End of inner exception stack trace ---                                                                                                         
   at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func`2 callback)                                                       
   at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.StopAsync(CancellationToken token)                                                  
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.                                                          
   at Jasper.Messaging.Durability.DurabilityAgent.StopAsync(CancellationToken cancellationToken)                                                      
   at Microsoft.AspNetCore.Hosting.Internal.HostedServiceExecutor.ExecuteAsync(Func`2 callback)<---
Everything works great when I run locally, but when deploying to my test environment with docker containers, this is all I get from my headless jasper service.
Jeremy D. Miller
@jeremydmiller
Yeah, I do, and it’s already fixed in master. Bad ordering of when a CancellationToken was cancelled. I wanted to do a little more, but this and a couple other things makes it worth pushing out a new batch of Nugets today
Svein Ellingsen
@lovmoen
Sounds great! :)
Mark Warpool
@CodingGorilla
@jeremydmiller Do you think you will get some new nugets out tonight or maybe tomorrow morning?
Jeremy D. Miller
@jeremydmiller
Yes. I’ve got this yet to go: JasperFx/jasper#531
If that doesn’t go fast, I’ll just push nugets
Next thing up though is going to be converting to .Net Core 3.0 if that’s okay with you and @lovmoen
Mark Warpool
@CodingGorilla
yea, do you plan that for a "1.0"?
or do you think it will still be in pre-release mode for a couple more releases
Jeremy D. Miller
@jeremydmiller
Yes. Have to look at what else we’d wanna do for a 1.0. Biggest thing was waiting a bit for 3.0. Then having time to do a big blog push for it.
Nah, I’d rather get to 1.0 sooner, then follow up w/ 2.0 if I need to.
Mark Warpool
@CodingGorilla
Do you plan to support both netcoreapp2 and netcoreapp3 at the same time? Or just the latest?
Jeremy D. Miller
@jeremydmiller
I was hoping to only have to do one, but we could probably get away with dual support.
Jeremy D. Miller
@jeremydmiller
@CodingGorilla I’ve pushed 0.9.14, but it’ll take a bit for Nuget to catch up. What was your call on netcoreapp3.0 only vs supporting both that and netcoreapp2.0?
Mark Warpool
@CodingGorilla
That's totally up to you, I have at least one app that won't go to netcoreapp3 for a bit, but I'm also fine with just leaving it at 0.9.14 (assuming it works) until I can get around to upgrading it
Jeremy D. Miller
@jeremydmiller
@lovmoen What do you think about going to netcoreapp3.0?
Svein Ellingsen
@lovmoen
I'm with @CodingGorilla on that. I can make do with 0.9.14 until I'm ready to go 3.0.
Jeremy D. Miller
@jeremydmiller
I hate to do the fork, but we can do that. Honestly though, it’s probably going to be at least a week or two before I can get to it. I probably need to worry about the projects with more usage first:(
Mark Warpool
@CodingGorilla
@lovmoen Have you upgrade to .14 by chance?
Jeremy D. Miller
@jeremydmiller
Uh oh, why? Not too much changed other than your PR
Svein Ellingsen
@lovmoen
Not yet. Busy on other stuff until Thursday.
Mark Warpool
@CodingGorilla

My API won't start, I'm getting:

Exception thrown: 'System.MissingMethodException' in Jasper.dll
Exception thrown: 'System.MissingMethodException' in System.Private.CoreLib.dll
Exception thrown: 'System.OperationCanceledException' in System.Private.CoreLib.dll
Exception thrown: 'System.OperationCanceledException' in System.Private.CoreLib.dll

looks like it might actually be Marten though:
System.MissingMethodException
HResult=0x80131513
Message=Method not found: 'DocumentMappingExpression1<!0> DocumentMappingExpression1.Duplicate(System.Linq.Expressions.Expression1<System.Func2<!0,System.Object>>, System.String, System.Nullable1<NpgsqlTypes.NpgsqlDbType>, System.Action1<Marten.Schema.IndexDefinition>)'.
Source=Jasper.Persistence.Marten
StackTrace:
at Jasper.Persistence.Marten.MartenBackedPersistence.<>c.<Configure>b__0_0(StoreOptions options)
at Jasper.Settings.SettingsBuilder`1.Build(WebHostBuilderContext context)
well, Jasper's use of marten
Jeremy D. Miller
@jeremydmiller
MissingMethodException is always a mismatch in assembly versions
What version of Marten are you using? I didnt’ think to update Jasper.Persistence.Marten
Mark Warpool
@CodingGorilla
just upgraded to the latest, 8.3.0 ?
3.8.0 lol
Jeremy D. Miller
@jeremydmiller
3.8 you mean?
Mark Warpool
@CodingGorilla
I knew there was a 3 and a 8 in that number somewhere :laughing:
Jeremy D. Miller
@jeremydmiller
Gotcha. I’ll doa sweep at lunch time for that. Should be small
Mark Warpool
@CodingGorilla
yea, rolling back to 3.7.1 fixes the problem
that means there must have been a breaking change between 3.7.1 and 3.8.0, shame on them :P
Jeremy D. Miller
@jeremydmiller
I can’t say anything because I didn’t catch it. Wonder if an optional arg got added, because that breaks compatibility even though your code using Marten wouldn’t have to change.
Jeremy D. Miller
@jeremydmiller
@CodingGorilla And ugh, I’ve already gone back and forth on this several times, but are you using the HTTP support at all? I have a lot more I theoretically want to do on the HTTP side of things to get to 1.0, but much less on the messaging side.
Mark Warpool
@CodingGorilla
I am not, I turn off all the HTTP "stuffs"
Jeremy D. Miller
@jeremydmiller
What do you think about trying to completely separate the HTTP support off to the side? I might pull a small 3rd assembly out for “core” support, but then again maybe not
Just so I can push a Jasper 1.0 as just the messaging and command executor stuff
Mark Warpool
@CodingGorilla
I, personally, like that idea, because I will probably never use Jasper's http mechanics, I have too much already invested in MVC (as much as I dislike large parts of it)
Jeremy D. Miller
@jeremydmiller
So the only big things I can think of I want to add to the messaging is some kind of idempotency checks and maybe EF Core Saga and/or storage support.
Maybe circuit breaker support for the queueing, but that doesn’t have to be there for 1.0