dehydrated | acme client implemented as a shell-script – | TLS library

Yes, that’s expected and documented here: https://react-query.tanstack.com/reference/QueryClient#queryclientprefetchquery

prefetchQuery is an asynchronous method that can be used to prefetch a query before it is needed or rendered with useQuery and friends. The method works the same as fetchQuery except that it will not throw or return any data.

If you want data returned, you can use fetchQuery, but for hydration, you don’t need to. Prefetching will put the data in the cache and then you can send the cache to the client. There is also an example in the docs that does it exactly like that: https://react-query.tanstack.com/guides/ssr#using-hydration

I had a misunderstanding of the whole API and here is how I understand the API now, to help other people, who are struggling with it.

You have to register your sync root and connecting your app to it. In case of connecting it, you will receive a CF_CONNECTION_KEY, which is needed to communicate with the virtual filesystem. Then you can add extended attributes to all files inside of your sync root. The most important are custom attributes you can choose by yourself to identify the file object by your app if needed and then the PinState and SyncState. Mostly the SyncState don't have to be changed by the app, besides marking a file as synced after it was processed by the app. (you can do it at the moment you update your custom attributes) Because in case a file changed, the SyncState will automatically be changed. The PinState declares which final state a file should have. For example UNPINNED means, that the file should be dehydrated, and PINNED the opposite. It does not mean, that the file necessarily has already this state. My misunderstanding was, that I thought in case I unpinned a file, it will be automatically dehydrated. Or in case I pinned a placeholder I will receive a request via the callback function I mentioned in my question. But this is not the case. Your app needs to find out via a FileWatcher (i can recommend my own created FileWatcher project: https://github.com/neXenio/panoptes) that the file attribute of specific files was changed. Then your app has to process every step. Like already mentioned in case of dehydrating, the app needs to call CfDehydratePlaceholder. In case of hydrating, you need to open a transfer session via CfGetTransferKey and then hydrate (send the data to the empty file) via the method CfExecute, where you need the connection key and the transfer key. And that's are the basics. There is much more to tell about it, but I guess with this beginning, everybody can figure it out by himself.

This is a known issue in Windows cloud filter API. It affects Windows 20H1 and later versions. Here is the discussion about this issue: https://docs.microsoft.com/en-us/answers/questions/75240/bug-report-cfapi-ackdelete-borken-on-win10-2004.html There is no any real solution for now as far as I know. Returning any specific error code does not help. The only possible solution would be recreating the deleted file in the local file system during synchronization at some later time.

The solution is adding to the COM object the empty value 'ContextMenuOptIn':

The best way is to add the dependencies of your query function to the queryKey. react-query is declarative and will re-fetch automatically if the queryKey changes. If you have to reach to useEffect and refetch, it's likely not the easiest solution:

Anything you can do in normal shell script syntax is legal in an entrypoint shell script. I might write this as:

Try this:

I was able to solve this by combining two of my fetching functions into one like so

To redirect both stdout and stderr of a command to a sequence of commands, and finally to both the console and a file, you can do it with this syntax