greyfox
greyfox
PostsComments
CC#
Created by eddyrick on 3/3/2025 in #help
Concurrency issues - distributed system
Might be a good idea to remove the triggers and consolidate the business rules in the application
7 replies
CC#
Created by eddyrick on 3/3/2025 in #help
Concurrency issues - distributed system
Have you sharded your db?
7 replies
CC#
Created by eddyrick on 3/3/2025 in #help
Concurrency issues - distributed system
Have you read Designing Data Intensive Applications? https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/B08VL1BLHB/
7 replies
CC#
Created by eddyrick on 3/3/2025 in #help
Concurrency issues - distributed system
Dumb question, but I assume you've already added a shedload of resources to the database server(s)? What kind of setup do you already have?
7 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
I may have been wrong, console may be correct for this.
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Follow the steps here: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
No
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Ok, if it's running locally then the text file it'll be logged on your local machine on whatever file path you designate as the log folder
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Where are you hosting the webapi?
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
It does write to the terminal. But it's a background process, it isn't displayed anywhere.
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
You don't know what a console is, do you...
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Can't tell with the lack of logging. Could be any number of things, a resource isn't accessible, or a permission error, or a missing dll, or anything really.
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
If you didn't add any logging at all it would be more useful because then at least (if hosted on Windows) the exception and stack trace would be logged to the Event Viewer
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Logging sent to the console isn't persisted. You should write to a text file or a database or something.
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Man, why'd you do that on a webapi?
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
What does your logging say happened?
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
Is the one at the bottom of the screenshot the same?
32 replies
CC#
Created by πR on 3/2/2025 in #help
Dotnet webapi test failing on GitHub Workflow
What does the stack trace say?
32 replies
CC#
Created by Lamar on 2/17/2025 in #help
✅ How to notify clients when an db update occurs
Could also use webhooks.
134 replies
CC#
Created by Lamar on 2/17/2025 in #help
✅ How to notify clients when an db update occurs
Alternatively you can use a message broker service like RabbitMQ or the like to handle all your requests, and which will queue the notifications for you.
134 replies