{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":432229659,"defaultBranch":"master","name":"stlc","ownerLogin":"joshiayush","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-11-26T15:50:44.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/70365318?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1637941890.960022","currentOid":""},"activityList":{"items":[{"before":"5758f796ee8d133f4a88f000b4e179952b5e67e2","after":"e97fd116a051e8415d868781a77163806b004651","ref":"refs/heads/master","pushedAt":"2023-04-16T15:10:01.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"FIX #6: Re-allocate `Map` instance if size becomes equal or greater than the capacity\n\nIt was a mistake to leave \"MapInsert()\" function with a bug of not re-allocating\nthe \"Map\" instance when the size become greater or equal to the capacity.\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"<span class=\"issue-keyword tooltipped tooltipped-se\" aria-label=\"This commit closes issue #6.\">FIX</span> <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1669791953\" data-permission-text=\"Title is private\" data-url=\"https://github.com/joshiayush/stlc/issues/6\" data-hovercard-type=\"issue\" data-hovercard-url=\"/joshiayush/stlc/issues/6/hovercard\" href=\"https://github.com/joshiayush/stlc/issues/6\">#6</a>: Re-allocate <code>Map</code> instance if size becomes equal or greater t…"}},{"before":"232def15aaeab57d91c76d178f9d887db74c525e","after":"5758f796ee8d133f4a88f000b4e179952b5e67e2","ref":"refs/heads/master","pushedAt":"2023-04-02T11:42:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Use `PTHREAD_MUTEX_RECURSIVE` to acquire a mutex for preventing deadlock from happening\n\nSince, \"pthread_mutex_lock()\" is called twice on the same mutex by the same\nthread without an intervening unlock, it causes a deadlock. The first call to\n\"pthread_mutex_lock()\" blocks the thread until it acquires the lock, and the\nsecond call to \"pthread_mutex_lock()\" also block the thread indefinitely,\nwaiting for the lock to be released. This results in a situation where the\nthread is stuck waiting for itself to release the lock, which is a deadlock.\n\nTo avoid this, we use a recursive mutex by initializing the mutex with the\n\"PTHREAD_MUTEX_RECURSIVE\" attribute. This allows a thread to acquire the\nmutex multiple times without causing a deadlock, as long as it releases the\nmutex the same number of times.\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Use <code>PTHREAD_MUTEX_RECURSIVE</code> to acquire a mutex for preventing deadl…"}},{"before":"34eab6e347e150780b0582dca47c7d6de616b7fa","after":"232def15aaeab57d91c76d178f9d887db74c525e","ref":"refs/heads/master","pushedAt":"2023-04-02T11:38:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Use `PTHREAD_MUTEX_RECURSIVE` to acquire a mutex for preventing deadlock from happening\n\nSince, \"pthread_mutex_lock()\" is called twice on the same mutex by the same\nthread without an intervening unlock, it causes a deadlock. The first call to\n\"pthread_mutex_lock()\" blocks the thread until it acquires the lock, and the\nsecond call to \"pthread_mutex_lock()\" also block the thread indefinitely,\nwaiting for the lock to be released. This results in a situation where the\nthread is stuck waiting for itself to release the lock, which is a deadlock.\n\nTo avoid this, we use a recursive mutex by initializing the mutex with the\n\"PTHREAD_MUTEX_RECURSIVE\" attribute. This allows a thread to acquire the\nmutex multiple times without causing a deadlock, as long as it releases the\nmutex the same number of times.\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Use <code>PTHREAD_MUTEX_RECURSIVE</code> to acquire a mutex for preventing deadl…"}},{"before":"9cffe99c63e60d38d4a726e28f37310050d3fd43","after":"34eab6e347e150780b0582dca47c7d6de616b7fa","ref":"refs/heads/master","pushedAt":"2023-04-02T10:17:18.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Use `PTHREAD_MUTEX_RECURSIVE` to acquire a mutex for preventing deadlock from happening\n\nSince, \"pthread_mutex_lock()\" is called twice on the same mutex by the same\nthread without an intervening unlock, it causes a deadlock. The first call to\n\"pthread_mutex_lock()\" blocks the thread until it acquires the lock, and the\nsecond call to \"pthread_mutex_lock()\" also block the thread indefinitely,\nwaiting for the lock to be released. This results in a situation where the\nthread is stuck waiting for itself to release the lock, which is a deadlock.\n\nTo avoid this, we use a recursive mutex by initializing the mutex with the\n\"PTHREAD_MUTEX_RECURSIVE\" attribute. This allows a thread to acquire the\nmutex multiple times without causing a deadlock, as long as it releases the\nmutex the same number of times.\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Use <code>PTHREAD_MUTEX_RECURSIVE</code> to acquire a mutex for preventing deadl…"}},{"before":"28a25fce4920d61134151858e0b9992f95104f20","after":"9cffe99c63e60d38d4a726e28f37310050d3fd43","ref":"refs/heads/master","pushedAt":"2023-03-26T10:25:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Use `Init` post-fixed function names for initialising `StringStream` containers\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Use <code>Init</code> post-fixed function names for initialising <code>StringStream</code> …"}},{"before":"5264688eed0d7e268a5337f00ffcaef30b7a5030","after":"28a25fce4920d61134151858e0b9992f95104f20","ref":"refs/heads/master","pushedAt":"2023-03-26T09:51:23.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Use the `Init` convention for `Vector` implementation as well\n\nAlso, change the buffer capacity computation in \"VectorInit()\" to:\n+  ComputeVectorBufferCapacity(size > -1 ? size : VECTOR_DEFAULT_SIZE,\n+                              &capacity);\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Use the <code>Init</code> convention for <code>Vector</code> implementation as well"}},{"before":"613d290635e87fca641ea5686dbf2a87a0bd1081","after":"5264688eed0d7e268a5337f00ffcaef30b7a5030","ref":"refs/heads/master","pushedAt":"2023-03-26T09:16:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Re-order includes - `standard` always on top of `user` includes\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Re-order includes - <code>standard</code> always on top of <code>user</code> includes"}},{"before":"313d73ffe601332e2c47cf51a5f510fa162cbafa","after":"613d290635e87fca641ea5686dbf2a87a0bd1081","ref":"refs/heads/master","pushedAt":"2023-03-26T09:13:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joshiayush","name":"Ayush Joshi","path":"/joshiayush","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/70365318?s=80&v=4"},"commit":{"message":"Drop the use of `u_int65_t` - instead use `size_t` for size type variables\n\nSigned-off-by: Ayush Joshi <ayush854032@gmail.com>","shortMessageHtmlLink":"Drop the use of <code>u_int65_t</code> - instead use <code>size_t</code> for size type vari…"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADGcItbAA","startCursor":null,"endCursor":null}},"title":"Activity · joshiayush/stlc"}