stale | Stale identifies | REST library

I am using Firestore in my Flutter app. When I query a collection, I am getting the incorrect number of documents back.

The correct number of documents I should be getting back for my query is 20.

If I initialise Firebase as follows...

I have already brew install mingw-w64. When i check the versions its there.

gcc --version:
gcc (Homebrew GCC 11.2.0_3) 11.2.0.

g++ --version:
g++ (Homebrew GCC 11.2.0_3) 11.2.0

I also run which gcc:
/opt/homebrew/bin/gcc

Then I run my docker-compose with image golang:latest. No errors yet

Another developer came to me with a tricky question today. She proposed the following:

A.) She wants to fire an event whenever a modal closes.
B.) She does not want the event to fire at any other time.
C.) The event must be up to date with state of the component.

A basic example is like so:

I have two useEffect hooks in a component (InternalComponent) that displays a single data item. One useEffect tracks a count as state, POSTing to a database when the user increments the count. The second useEffect resets the count when the item tracked by the InternalComponent changes (due to external manipulation).

The problem is: the useEffect that updates the database will fire when the item changes; it will see the new item value, but will incorrectly send the database the count from the previous item. This occurs because the two useEffects fire "simultaneously", with the state that would indicate the count shouldn't be POSTed not being set until after the POST useEffect is run.

Poetry has some stale dependencies because the use of develop = true packages. Poetry cannot figure out on its own that dependencies have been updated. How do I force Poetry to reinstall everything in its virtualenv to work around this issue?

Cloudfront is getting a RefreshHit for a request that is not supposed to be cached at all.

It shouldn't be cached because:

1. It has cache-control: max-age=0, no-store;
2. The Minimum TTL is 0; and
3. I've created multiple invalidations (on /*) so this cached resource isn't from some historical deploy

Any idea why I'm getting RefreshHits?

I also tried modifying Cache-Control to be cache-control no-store, stale-if-error=0, creating a new invalidation on /* and now I'm seeing a cache hit (this time in Firefox):

There has been other questions on the subject, but nothing seems working for me.
I have a functional CURL, but I want to translate to JS (with Node).

I'm trying to connect a nodejs with mongodb using mongo db compass and im getting the following error:

I recently started writing my first SwiftUI app and ran into an design issue, which can be demonstrated by the simple code below. I know what the issue is, but I wonder why it occurred and what's the recommended way to address it.

In the demo, there are two views. The first is a list view, the second is a detail view. The detail view contains a button to delete the item being displayed. Clicking on the button crashes the app due to the forced unwrapping in the detail view. I didn't expect the crash, because from my understanding when the data model changes, SwiftUI should regenerate the entire view hierarchy. That is, it calls ContentView.body, which calls FooListView.body, which goes through items in the data model and creates NavigationLink for each item.

Since the data model has been changed, there is only one item left. So I don't think SwiftUI would create FooDetailView (or call its body) for the item deleted. If so, how come the FooDetailView code crashed? I tried to debug the code but didn't find much useful information. I believe the FooDetailView that crashed the app is the one that contained the deleted item. That I don't understand. Since SwiftUI regenerates view hierarchy, how could that old view left uncleaned up?

Can anyone explain a bit how you understand it? And how do you address the issue? I currently think out two ways. The first is to pass all the params needed by detail view to avoid accessing data model. But I don't think this approach scales. The second is to not use forced wrapping. That should work fine, but I doubt if this is the recommended way to do it.

BTW, another similar setup to generate the crash is to use three views: list view -> detail view -> delete view. When user clicks on button in delete view, the detail view will crash.

Thanks.

Update:

1. SwiftUI may recall an existing view's body which contains stale data.

@jrturton I was aware that changes to @EnvironmentObject would cause view's body get called. What I didn't realize was that SwiftUI migtht recalled an existing view's body which contain stale data. I never read any discussion about this on the net. Do you know why SwiftUI do that?

I had always thought that when state changes, SwiftUI would regenerate the entire view hierarchy from top down by calling Content.body. If it was so, FooDetailView would always has the up-to-date data when it gets called and there wouldn't be the issue. I had the understanding because SwiftUI is advertised as a state driven architecture, and app developers are supposed to declare the UI based on the current state. By "current" I mean the new state, not the previous state. That's the reason why I thought it should be fine to use forced unwrapping.

1. I doubt if passing all params to detail view is a general solution.

First, this doesn't scale well. For example, suppose Foo is associated with another struct Bar (that is, Foo has a property containing Bar's id) and we want to display Bar's name in detail view, then we will need to add bar name to the params. For a complicated Item, its detail view may contain a lot of things which are determined at runtime, it will be hard to prepare everything ahead by the caller.

More importantly, once we pass these params to detail view, they are effectively outside data model and can easily go stale. It would be issue if user performs delete action using these stale data.

1. Passing binding doesn't solve the crash issue on its own.

@lorem-ipsum, thanks for your suggestion on using binding. I wasn't aware that ForEach can take binding. What's more, I have also beening think if it's good practice to pass binding, instead of regular params, in SwiftUI (I don't know that anwser yet).

That said, passing binding doesn't solve the crash issue on its own, because when the data model changes, SwiftUI still recalls the existing detail view's body which contain stale data.

1. The solution?

I think the root cause is that, although SwiftUI is advertised as a state driven architecture, a view's body may get called with stale data. So the data model's api should deal with invalid params. Hornestly speaking, this isn't a design decison which I prefer to. I usually think the caller should only pass valid params to data model API. Otherwise it's an architecture issue that should be resolved on the caller side in the first place. Unfortunately it seems that's the case with SwiftUI.

(Note: Thank all for pointing out that deletion code should be in data model. I knew that. I didn't do it because I spent long time investigating the issue in my app and was exhausted when I prepared the example code.)