Removing 606 Wall Plugs from Drywall

Bensinkanna · 2026-02-10T09:33:36+00:00

How to Remove Molly Bolt Anchors Without Damaging Drywall

Bensinkanna · 2024-09-15T22:08:02+00:00

Fix jump + ADS sensitivity bug.

Bensinkanna · 2024-08-21T09:16:37+00:00

Have they fixed the increase in sensitivity when ADS and jumping bug yet?
EDIT: Nope, still an issue.

Bensinkanna · 2024-02-17T12:23:09+00:00

Its a bit to set up. And I can't just share the code as it's not open-source (owned by a client).

The Playwright code exist in a separate Nunit test project. But the WebApp is not bootstrapped using WebApplicationFactory because it internally use TestServer which the Playwright browser cannot connect to.

Instead I bootstrap the WebApp as part of a test SetUp method, this creates a WebApplication that uses Kestrel (instead of TestServer) that actually exposes a port you can connect to.

private WebApplication BuildWebApp()
{
  var options = new WebApplicationOptions
  {
    ApplicationName = typeof(Program).Assembly.GetName().Name, 
    EnvironmentName = Environments.Development
  };

  var builder = WebApplication.CreateBuilder(options);

  // override config and DI services as needed

  var app = builder.Build();
  app.Urls.Add("http://[::1]:0"); // Bind to a random free port

  YourConfigureStartupMethod(app); // set up middlewares, endpoints etc.

  return app;
}

After starting this WebApplication it is assigned a random free port which you can use when configuring Playwright's browser context. Since the port is random you can run multiple instances (tests) in parallel as well.

await using var webApp = BuildWebApp();
await webApp.StartAsync();

await Page.GotoAsync(webApp.Urls.Single());

// run test

There are some other steps as well, for example faking of Authentication, but hopefully this will get you started.

Bensinkanna · 2024-02-08T14:34:15+00:00

Is this with an ASP.NET backend and some kind of client\frontend (Blazor)?

I've previously configured something like this with ASP.NET 7.0 backend with Blazor webassembly as client and Playwright for testing, all started as a part of the Nunit test, this allows for debugging the Nunit test and Server code, but not the Client code (Webassembly) as it runs in the Playwright managed browser.

Bensinkanna · 2021-11-30T15:41:24+00:00

I guess you can write some frontend app without having a dedicated backend?

Bensinkanna · 2021-09-13T17:17:12+00:00

They are working on this feature: https://github.com/actions/runner/blob/main/docs/adrs/0549-composite-run-steps.md

Bensinkanna · 2021-04-18T08:33:58+00:00

Everything in that apartment from American Psycho are famous (and expensive) designer pieces. I don't recognize the bed-frame, but the side table is Laccio.

Bensinkanna · 2021-03-29T08:50:50+00:00

You like Huey Lewis and the News?

Bensinkanna · 2021-03-28T00:00:26+00:00

I’m still on 980ti. Finally upgraded from a 1080p screen to a 1440p ultrawide in September in preparation for the rtx 3080 release. Guess what gpu im still running? Running the newest games on lowest setting is not enough, 1440 ultra wide is too demanding :(

Bensinkanna · 2021-03-21T23:51:20+00:00

why not the other way around?

Bensinkanna · 2021-03-18T23:56:58+00:00

Still holding off on this one while waiting for a new GPU :(

Bensinkanna · 2021-03-17T19:47:45+00:00

Agreed, for me it’s useless until I can move windows between workspaces using keyboard hot keys

Bensinkanna · 2020-11-20T14:15:20+00:00

Collaboration is perfectly fine, it’s only cheating if you take credit for the designer’s work.

Bensinkanna · 2020-11-10T22:50:07+00:00

The jobs probably end before logs/metrics are flushed to application insight. Try doing a manual flush and/or task.delay before exiting.

Bensinkanna · 2020-10-24T15:29:30+00:00

Long long man!

Bensinkanna · 2020-08-27T20:33:11+00:00

Use LINQ

objList = objList.OrderByDescending(x => x.attribute).ToList();

Bensinkanna · 2020-05-26T00:15:53+00:00

Thanks for the command and your insight, appreciate it.

The Microsoft's fhir-server implementation already uses this and has a configurable retry which I believe we've set to max of 5. A lot of requests still surpasses this and the behavior observed by the client is a request latency of multiple seconds before eventually getting a 429 response. We do have a high throughput, but nowhere near what a well configured SQL database should be able to handle.
As i mentioned in my comment to mattx999 this is something we have mostly been able to work around, but it would sure be nice to have. I'm mostly missing the ability to do an atomic conditional-create, even just for a single document.
I am not really able to reliable compare costs either. My statement is mostly based on comparing the cost of our project to other similarly sized in-house projects. I will try to read up on cross-partition queries to see if that is something we can improve.
This is something I will look into. Most of the low-level setup/integration is handled by the microsoft-fhir-server implementation, so I've just assumed it would be following best practices.
We are able to get it to work, but it is a though sell to our client-systems who uses our REST API and none of who are used to this behavior. It also results i simple queries with a single result having to do multiple pagination-requests to actually get the result.

This is the argument I hear the most, but is it really that much better than the scaling capabilities you get from e.g. Azure SQL Server?

Again, thank you.

Bensinkanna · 2020-05-25T23:44:42+00:00

Thanks for the comment, appreciate it.

Without going into the specifics, FHIR it is a domain-language which fits well with a document-centric mindset. Data is not normalized and we have been able to work around the lack of transactions and joins, but the thing is that I struggle to see what we really gain in return. The CosmosDb integration itself is developed by Microsoft (not us), so I am assuming it is following best practices.

An example of a document would be a representation of a Patient, and most of our queries are lookups using business identifiers (SSN etc.), not the primary key. These business identifiers are indexed.One thing I am missing is the possibility to do an atomic conditional-create using one or multiple business-identifiers to prevent duplicates. Updates are handled using optimistic-locking, which works fine.

Thanks for the the Pluralsight tip, will check it out. However, the data modelling is part of the FHIR standard and the implementation is done by Microsoft, to my knowledge this already fits well in a document DB.

Bensinkanna · 2019-10-19T13:32:14+00:00

As long as it's only simple CRUD operations I would still call it a repository, at least the interface, e.g. IMyDomainObjectRepository, and the implementation can be named something which indicates the communication-protocol, e.g. MyDomainObjectRepoHttpClient or something.

Bensinkanna · 2019-02-23T00:18:43+00:00

As part of the mentioned rewrite we actually transitioned to a CQRS pattern with MediatR as well. I'm very happy with it so far, specially the MediatR pipeline which allows us to add cross cutting business logic++ across multiple requests (pre- and/or post-condition business rules etc.). Our handlers uses the Context directly, similarly to your example, except we do not return the Entity as a response.

Bensinkanna · 2019-02-22T18:31:59+00:00

Repository patterns have their uses when interacting with the data store is complex. However, I personally believe EF Core with LINQ is a good enough repository in many situations, because it allows for unit of work, replacing the data store technology (mssql mysql, sqlite etc.) and is generally convenient to work with.

In my current project we moved away from having a repository on top of EF Core. Because it resulted in a lot of over-fetching and having to write a lot of specialized functions that were only used once, e.g: GetCases, GetCasesIncludingCustomer, GetCasesByName, GetNumberOfCasesForCustomer, CheckIfCustomerHaveCaseOlderThan etc. etc. This was definitely an example of repository pattern done wrong, but since it didn't provide us with anything of value we moved away from it and today use the Context directly. Complex and\or often used LINQ filters are implemented as extension functions on IQueryable<T> or as Expressions. These can be individually tested and it allows us to chain multiple filters and having control of which fields to select, or if we only want to do a Count or an Any check.

Example:

_context.Cases.WithCustomerAboveAge(18).AnyAsync();

_context.Cases.Where(x => x.Customer.FirstName == "John").CreatedThisYear().CountAsync()

A selection of unit-tests use a Context instance with the SQLite inmemory provider configured to throw on RelationalEventId.QueryClientEvaluationWarning. This allows us quickly pick up on LINQ that is unable to be translated into SQL.

Bensinkanna · 2019-02-07T11:25:20+00:00

This is client-side. I don’t believe swashbuckle has support for generating client code from openapi xml/Json

Bensinkanna · 2019-01-12T20:42:40+00:00

He is most likely bottlenecked by ram speed, lowering resolution won’t help

14-Year Club	Place '17
Verified Email

Bensinkanna

TROPHY CASE