reread | Source of https : //reread.io | Runtime Evironment library

I share many of the same frustrations! It's so hard to get Typescript working nicely with Javascript and the microsoft documentation is so obtuse!

In your case : the path to a library is always looked for in node_modules so in that case you don't need to add the full path.

You also never need to import a .d.ts file. You can just put the .d.ts file somewhere in your working folder and VS Code will detect it.

If you have the .d.ts file for moment.js, you will get type completion in VS Code. You don't need to import moment.js when you load it with a

The supervisor is not present in Amazon Linux2 by default.You just have to rewrite this script to run celery under the supervision of systems like this

The easiest way(that I can think is) to do is open the file

read the file and save the lines

and then empty the file

The function did not return anything. Here is a somewhat improved version of your function. If you want to keep the output it would make more sense to provide a full path, rather then saving it to a temp folder. I also note that you are not using the argument source_srs

Create the source connector with a different name, or give the CSV file a new name. Both should cause it to be re-read.

What is wrong with your program? It appears to work fine - from parameter passing point of view at least. I tweaked your code a bit (added a random choice and added sleep to the main process to avoid it exiting right away) and it seems to be doing fine:

Yes, it's undefined behavior from the standpoint of standard C - or at least, the value of foo is indeterminate and can't be safely used for anything.

C17 (n2176) 7.13.2.1 (3):

All accessible objects have values, and all other components of the abstract machine have state, as of the time the longjmp function was called, except that the values of objects of automatic storage duration that are local to the function containing the invocation of the corresponding setjmp macro that do not have volatile-qualified type and have been changed between the setjmp invocation and longjmp call are indeterminate.

That's precisely the situation here: foo has automatic storage duration and is local to the function where setjmp is invoked, it's not volatile-qualified, and it is changed between setjmp and longjmp.

The authors of the code were probably thinking that passing &foo to lib_var would ensure that it is allocated in memory, not in a register, and that since the compiler couldn't know whether lib_var would modify foo, it couldn't constant-propagate the value NULL into the else block. But as you say, LTO or various other optimizations could break this. It's possible the authors intended only to support a particular compiler that they knew didn't do any such thing, or that provided some stronger guarantees beyond what the standard says, but it's also possible they were just confused.

The correct fix would be to declare foo as volatile, i.e. struct Foo * volatile foo = NULL;.

Strictly speaking, not even re-reading the directory listing should save you, since the directory can change between re-reading the listing and submitting another CHANGE_NOTIFY request. The race condition just moves to a different spot.

Except there is no race condition.

This took a little digging, but it’s all there in the specification. In MS-SMB2 v20200826 §3.3.5.19 ‘Receiving an SMB2 CHANGE_NOTIFY Request’, it is stated:

The server MUST process a change notification request in the object store as specified by the algorithm in section 3.3.1.3.

In §3.3.1.3 ‘Algorithm for Change Notifications in an Object Store’, we have:

The server MUST implement an algorithm that monitors for changes on an object store. The effect of this algorithm MUST be identical to that used to offer the behavior specified in [MS-CIFS] sections 3.2.4.39 and 3.3.5.59.4.

And in MS-CIFS v20201001 §3.3.5.59.4 ‘Receiving an NT_TRANSACT_NOTIFY_CHANGE Request’ there is this:

If the client has not issued any NT_TRANSACT_NOTIFY_CHANGE Requests on this FID previously, the server SHOULD allocate an empty change notification buffer and associate it with the open directory. The size of the buffer SHOULD be at least equal to the MaxParameterCount field in the SMB_COM_NT_TRANSACT Request (section 2.2.4.62.1) used to transport the NT_TRANSACT_NOTIFY_CHANGE Request. If the client previously issued an NT_TRANSACT_NOTIFY_CHANGE Request on this FID, the server SHOULD already have a change notification buffer associated with the FID. The change notification buffer is used to collect directory change information in between NT_TRANSACT_NOTIFY_CHANGE (section 2.2.7.4) calls that reference the same FID.

Emphasis mine. This agrees with how Samba implements it (the fsp structure persists between individual requests). I wouldn’t expect Microsoft to do worse than that by not keeping the promise they made in their own specification.

You need to get all the functions, then sort and print :