citelab / jamscript Goto Github PK

Test whether this is happening.. might be related to the behaviour found by Xiru?

Is there a bug in the delete_sem reuse?

Particularly with large number of user-level tasks.

We need to investigate the scalability and dependability of the RPC implementation.

Need to switch to tcc for second stage. Also include and library paths are wrong.

If return is Null, Segfault occurs in jamlib

On Ubuntu 14, with libcbor 0.4.0

Scons should automatically make libtask

When generating the code for a sync function with return type of char *
The return value needs to be strdup before freeing the arg_t. Otherwise, we get
deallocated error.

e.g Now

arg_t *res = .....
ret = res->val.sval
command_arg_free(res)
return ret;

Here, the ret is actually freed.

Should be corrected to
ret = strdup(res->val.sval)
command_arg_free(res)

On my ubuntu machine, I keep getting Unhandled rejection No devices connected.
Will attempt to fix it.

Using C2J and J2C async at the same time causes freezes issues. The program just stops.

Jamworker line 224, these few lines caused the J2C async to go crazy. Commenting it out made the program work

Old broadcaster is still active.
We need to disconnect from the old broadcaster.

Check and resolve the sendinfo query bug.

We need to make J2C synchronous call wait for all replies based on the collection policy.

So the call should return as follows:

= Return if all replies are received.
= Return with success if at least some replies are there by timeout, otherwise return with error

Check and resolve the --bg flag issue in jam run.

We need to recreate the Req-Rep socket so that a rebooting server will work with old clients.

I am not sure how to fix this but
jwork_process_subsock for async will signal js->atable->globalsem
But the only place which waits this semaphore is inside the event loop.
However when we make J2C async call, it seems despite signalling it, the event loop will never be hit.

This needs further testing.

We need to reuse the registrations. It seems sometimes it is not happening.

Need to initiate redis in the proper way.