ef core is great for simple queries and modification of your data while using the changetracker.
You can use AsNoTracking/Projection to perform similar like dapper for queries.
When using command query seperation you can also use dapper for queries and ef core for commands.
I think we weren't paying for support and it was standard Business Support they were pitching. At the time we were having pretty fundamental problems with Azure Single Server Postgres which was really just a terribly engineered solution which they admitted had some nasty issues (there was some bug that would cause the storage IO threads to deadlock causing Postgres to crash)
in many cases: no service health alerts, no status page updates and no confirmations from the support team in tickets.
still we can confirm these issues from different customers accross europe. Mostly the issues are regional dependent.
Where do these alerts supposedly come from? I started having issues around 4PM (GMT), couldn't access portal, and couldn't make AKV requests from the CLI, and initially asked our Ops guys but with no info and a vague "There may be issues with Portal" on their status page, that was me done for the day.
This is the single most frustrating thing about these incidents. As you're harmstrung on what you can do or how you can react until Microsoft officially acknowledges a problem. Took nearly 90mins both today and when it happened on 9th October.
Constrained generation guarantees syntax. It does not guarantee semantic correctness tho. Imagine you want a json object with "hp" and "damage". If you use a grammar, the model will be forced to output a json object with those two values. But it's not guaranteed to get sensible values.
With a 2nd pass you basically "condition" it on the text right above, hoping to get better semantic understanding.
I'm pretty sure the grammar is generated from the Json schema, it doesn't just constrain json syntax, it constraints on the schema (including enums and such). The schema is also given to the model (at least in openai) you can put instructions in the json schema as well that will be taken into account.
Perhaps I worded that poorly. What I mean by semantic correctness is that the model could output nonsensical values for some things. Say in a game, "normal" health is ~100hp and the model creates a wizard with 50hp but then a mouse with 10000hp. So you're guaranteed to get a parsable json object (syntactically correct) but what the values are in that json is not guaranteed to make sense in the given context.
I find it does pretty well given a reasonable prompt and (especially) well-named keys/JSON structure. So if you had boss.mouse.hp you would get higher HP than random_enemies.mouse.hp, or better: enemies.level_1.mouse.hp.
what is a unhealthy request? is searching for a user which was _not found_ by the server unhealthy? was the request successful? thats where different opinions exist.
Sure, there's some nuance to it that depends on your application, but it's the server's responsibility to do so, not the client's. The status code exists for this reason and the standard also classifies status codes under client error and server error so that clients can determine whether a server is unhealthy simply by looking at the status code.
The idea is to replicate the weights of the network in the electronics. Somehow like our brains work? This way an analog input signal could lead to a neural network processed output signal without the digital emulation on an gpu. As this is very much simplified, the question is if this could work for modern llms?
Though if it is on or under the surface of the earth, “straight” will be a bend radius of around 6,370km. We don’t make a lot of buildings that deal with this but transcontinental or transoceanic cables certainly do. If someone designed a fiber that required absolutely no bend in order to work you’d have to use it in buildings or dig much deeper holes.
There was an encoding mechanism proposed about 10-15 years ago that used spirally polarized light to carry more channels, but it required the surface of the fiber to be polished to a much higher degree than existing cables in order for the light to go around bends properly.
If you’re using the planet as your “flat surface” then sure. If, however, you’re willing to deal with exiting the atmosphere at each end, you can use Real Straightness. But I don’t know anyone running a single segment for that distance.
I’m sure there are some microwave antennas still out there doing the Lord’s Work. At least in the Plains states where hills are low and putting antennas on two of them gives you some extra distance. How far do microwaves bend over the horizon?
Don't they generally do the opposite of bend over the horizon? Two towers that are observed (visible wavelength = tiny Fresnel zone) to have line-of-site can easily be obstructed (microwave = huge Fresnel zone).
If you're going out of the atmosphere may as well skip the fiber and just point lasers through the vacuum of space directly and reap the benefits of the faster speed of light through a vacuum vs glass!
There are not far more types of fiber cable, there are far more types of jackets :)
You are confusing the cable jacket with the fiber cable inside of it.
This is the spec on the jacket they use and they didn't design this particular jacket to be flexible enough to survive flexing at the level the fiber cable inside of it can. Sure - not all jackets can be bent as much as the fiber. Some because they are not made to be as flexible (as here), some because it's basically impossible (armored interlocking jackets), etc.
I'm not sure what this changes?
The part number with suffix AB0403 (the SMF A1 fiber), if you cut the jacket, you should be able to bend the fiber cable inside at a radius of 10mm and have it be fine. It appears to be standard G.657A1 fiber cable inside.
There are really not far more types of fiber cable than i listed, and this spec sheet definitely does nothing to support that claim, since as i said, it has A1 fiber cable inside the cable jacket that will happily support a 10mm bend radius.
BTW, as an aside, I wouldn't use this stuff - just looking at this sheet and pricing at my normal fiber distributors - it is both overpriced and underspec'ed for its price. Which seems pretty typical for leviton :)
Most 24 standard I/O plenum cable is going to be 7.8mm (this is 9.9, so 30% thicker), and have less than half that bend radius even with non-flexible OFNP rated jackets. If you are being charged more than 2 bucks a foot for it, you should consider other options.
> There are not far more types of fiber cable, there are far more types of jackets :)
Ahhhh, thanks for clarifying! Now I understand what you’re saying, the jacket and fibers have different bend radiuses (radii). I appreciate you taking the time to explain :) also, noted about there only being a few types of fiber, with a multitude of jackets.
I’ll let my low voltage subcontractor know about the underwhelming Leviton cable, it’s a plan and spec public job so it’s possible the Leviton rep is friends with the engineer and got their cable flat specced, wouldn’t be the first time!
I’m only responsible for the raceway, it’s a 2500’ run between two college campuses separated by a highway that runs outside for a good chunk of the distance so it’s possible the jacket is beefy and inflexible for temp resistance. I’m much more familiar with electrical conductor jackets, THHN and XHHW-2, which are PVC and XLPE, respectively.
