The URI returns http://:7086 and no data is generated.
When I run dotnet run on the event-sourcing sample, the URI returns http://:7086 and no data is generated. Are there any omissions or errors in the procedures?
[Execution result] C:\Temp\cosmos-db-design-patterns\event-sourcing\source> dotnet run Unhandled exception. System.InvalidOperationException: The gRPC channel URI 'http://:7086' could not be parsed.
Hellow @markjbrown, @paladique The results of both command runs are attached. dotnet run.txt func start.txt
Hey @paladique can you take a look at this when you get a chance? @enishimu1 is using this repo for a demo in a session.
Thanks!
[like] Eiji Nishimura reacted to your message:
From: Mark Brown @.> Sent: Tuesday, October 1, 2024 11:33:25 AM To: Azure-Samples/cosmos-db-design-patterns @.> Cc: Eiji Nishimura @.>; Mention @.> Subject: Re: [Azure-Samples/cosmos-db-design-patterns] The URI returns http://:7086 and no data is generated. (Issue #33)
Hey @paladiquehttps://github.com/paladique can you take a look at this when you get a chance? @enishimu1https://github.com/enishimu1 is using this repo for a demo in a session.
Thanks!
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/cosmos-db-design-patterns/issues/33#issuecomment-2385536970, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A33RTUHKWLH52NAZFHYN5PDZZKCALAVCNFSM6AAAAABO2JC666VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBVGUZTMOJXGA. You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the output @enishimu1 - I'll take a look into this
Updates here:
- The function needed to be changed to an isolated worker model, see PR here: https://github.com/Azure-Samples/cosmos-db-design-patterns/pull/34
- Since this project was upgraded to .NET 8, there were some additional edits that needed to be made to get this up and running.
- Active branch referenced, still a WIP. Run console app with
dotnet run -- console
[like] Eiji Nishimura reacted to your message:
From: Jasmine Greenaway @.> Sent: Tuesday, October 1, 2024 2:58:11 PM To: Azure-Samples/cosmos-db-design-patterns @.> Cc: Eiji Nishimura @.>; Mention @.> Subject: Re: [Azure-Samples/cosmos-db-design-patterns] The URI returns http://:7086 and no data is generated. (Issue #33)
Thanks for the output @enishimu1https://github.com/enishimu1 - I'll take a look into this
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/cosmos-db-design-patterns/issues/33#issuecomment-2386239261, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A33RTUCQPLRHGYTV5IFRJBLZZK2AHAVCNFSM6AAAAABO2JC666VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBWGIZTSMRWGE. You are receiving this because you were mentioned.Message ID: @.***>
[like] Eiji Nishimura reacted to your message:
From: Jasmine Greenaway @.> Sent: Tuesday, October 1, 2024 4:15:43 PM To: Azure-Samples/cosmos-db-design-patterns @.> Cc: Eiji Nishimura @.>; Mention @.> Subject: Re: [Azure-Samples/cosmos-db-design-patterns] The URI returns http://:7086 and no data is generated. (Issue #33)
The function needed to be changed to an isolated worker model, some things see PR here: #34https://github.com/Azure-Samples/cosmos-db-design-patterns/pull/34
Looking into other app issue as well.
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/cosmos-db-design-patterns/issues/33#issuecomment-2386437246, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A33RTUBGHIWFIGDJX3P62RTZZLDC7AVCNFSM6AAAAABO2JC666VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBWGQZTOMRUGY. You are receiving this because you were mentioned.Message ID: @.***>
Thanks for checking. I'll try this right away.
@paladique
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated" Now, [func start] started without any problems. However, [dotnet run -- console.txt] still does not start. This time, [http://:] was returned. Attached is the exception. (https://github.com/user-attachments/files/17221128/dotnet.run.--.console.txt)
I merged @paladique PR for isolated mode. We are reviewing all of these now to make updates and fixes. We can take another look and get resolved. Thanks.
closing. fixed in #53