propose | Propose Your Crush - Propose Your Valentine

It seems to be a bug in the ipython prompt toolkit (version >= 3)

Try doing this for your environment:

Run php artisan list to see all the commands available

There is none app:name

To change the name of your project edit your .env and modify APP_NAME

Both current and proposed are being initialized as the same object. Instead, assign a copy of blank...

When applying common_type to three or more template arguments, common_type::type is defined to be common_type_t where C is common_type_t. If T1 and T2 don't have a common type then the type typedef doesn't exist.

This means that common_type is defined to work from left to right on its arguments, and it can be done in O(n). It also means that rearranging the order of arguments can lead to different results.

In your own implementation, you work from right to left, which is why you got different results.

I think you might be causing yourself angst because of how you are handling the relationships.

Considering StateWithFacilities

You appear to be saying get the school who's id is equal to the schoolId column in the state.

While the realtionship should be from a column in the School that stores the appropriate StateId.

You appear to be using the reverse.

Example

Perhaps consider this example based upon what you appear to be wanting to do: (States, Schools and Locations have been given a name column to make the output easier to understand)-

State class (Entity and therefore Table) which is top of the hierarchy.

Could this code do what I ask?

Well, it could, but you cannot rely on that. Do not do this; it is not a way to write correct programs.

When you write b->x = 22;, the compiler is entitled to behave as if there were a whole struct test at b. You may be thinking, “I am just putting 22 in the bytes for the member x,” but the compiler may use a “store eight bytes” instruction:

• Consider some architecture where memory is organized into eight-byte groups. The bus can only read and write whole eight-byte chunks.
• Since there is no way to write four bytes in hardware, writing four bytes to memory requires reading eight bytes, manipulating them in processor registers to insert the desired values in four of the bytes, and writing eight bytes back to memory.
• The compiler wants to optimize b->x = 22;, and it knows y has not been set yet, so it is allowed to have any value. So, instead of using an inefficient write-four-byte sequence, the compiler generates an eight-byte store that puts 22 in b->x and 0 in b->y.

Then this fails because the compiler has just written 0 to memory that might be in use for something else because it is not part of the space you allocated for b.

“If you lie to the compiler, it will get its revenge.” — Henry Spencer

Some code from my extension Find and Transform:

Your issue is immediately solved if ProposedChange is a struct and not a class. Unless its instances have their own life cycle, then they are just holders of value, so should be semantically a struct.

The reason your issue is solved is because mutating a property of a struct mutates the struct, so SwiftUI knows to recompute the view, whereas with a class you need to subscribe to changes.

Assuming ProposedChange is a struct:

1. JSON Web Key Set (JWKS aka JWK Set) is a list of JSON Web Keys (JWKs). Since JWK Set is simply a container, it contains no metadata such as an expiration date/time.

2. It does not expose this for at least two reasons:

• RFC 7517 is the specification that governs the behavior of JWKs and JWK Set. It does not mention or require the provider to publish an expiration date/time. Perhaps this is so due to reason #2:
• The provider should be able to remove keys for any reason at any time. Possible reason: key has been compromised. (For a private/public keypair, this would mean the private key has been compromised and the corresponding public key published via JWKS should be removed from circulation). This example is an outlier but it does happen and the provider would have to act immediately to fix it.

Emergencies notwithstanding, providers do rotate keys on a regular basis as a matter of good security hygiene. To handle key rotation (be it planned or emergency), your application should adhere to a simple algorithm. It should periodically fetch the keys from JWKS endpoint, build a local replica of all keys and add/remove keys from this replica based on the last fetch. Only keys found in the local replica should be used by your application to perform a cryptographic operation such as verifying a signature on a JWT.

Each JWK has a kid (key id) parameter and this parameter is used to match a specific key. RFC 7517 recommends using kid to choose among a set of keys within a JWK Set during key rollover. When your application does a fetch of keys from JWKS, you'll be comparing the set of keys coming from JWKs to the set of keys in your local replica. The comparison is based on kid. If a key with some kid is present in JWKS but not present in your local replica, you should add this key to your replica. Vice versa, if a key with some kid is present in your local replica but not present in JWKS, you should remove this key from your local replica.

How frequently should your application fetch the keys from JWKS? This is up to you, it depends on the risk tolerance of your app and/or your organization. Some apps fetch every minute, others do it hourly or daily.

Let's say your app never does this fetch, the key is hardcoded in your app. This will work until the key is removed by the provider. (We're assuming that we're talking about a public key here. A JWK could represent a private key...and that you will not want to embed into your app). Some providers don't rotate keys or do so once in a very long while. If you're dealing with a well-known (to you) provider and they guarantee to you that they won't rotate keys, your risk of embedding a key into your app is low.

In general, embedding a public key into the app is not a good idea. If you're going to be using a JWKS endpoint, implement a simple fetch + update solution as outlined above.