Explore Projects

fsck.erofs currently relies on a strictly synchronous execution path for image unpacking and verification. This design causes the main thread to become heavily bottlenecked by synchronous I/O during file extraction, which subsequently blocks the CPU-intensive decompression phase. As EROFS images scale in size, this sequential pipeline creates a significant performance barrier across container environments, embedded systems, and developer workflows. This project resolves the synchronous I/O bottleneck by introducing a multi-threaded decompression pipeline built on a producer-consumer architecture. A background workqueue will enable the main thread to handle directory walks and queue compressed blocks, while a dedicated worker thread pool processes the decompression payloads. To eliminate heavy scheduling overhead and lock contention, the project introduces dynamic pcluster batching, which groups sequential blocks into a single work unit and scales the batch size based on the specific compression algorithm in use. Additionally, the extraction process will be further accelerated by a thread-safe, LRU-bounded metadata cache protected by read-write semaphores to prevent redundant I/O and strictly bound memory usage. The deliverables for this project include a scalable, multi-threaded extraction pipeline for fsck.erofs integrated with erofs_workqueue , alongside dynamic pcluster batching heuristics optimized for LZ4, LZMA, DEFLATE, and Zstandard to minimize futex overhead. Additionally, the project will provide a thread-safe, LRU-bounded metadata cache designed to significantly reduce redundant I/O , and the implementation will be validated through comprehensive regression tests, edge-case validations for corrupted images, and Flamegraph-backed performance benchmarks.

GCC's static analyzer (-fanalyzer) lacks C++ class hierarchy awareness, causing it to miss bugs in exception catch blocks that use base types and limiting virtual function resolution. This project implements exception subclass matching (PR119697) and improves virtual function dispatch (PR97114) by adding type hierarchy infrastructure to the analyzer.

<p>Bringing the 'maps' parameter with its full functionality to the TemplateData GUI editor to make it easier for the average non-technical user to modify the “Maps” parameter.</p>

The purpose of this project is to add Temporal Graph Neural Networks (TGNNs) to GraphNeuralNetworks.jl. The first part of the project will be dedicated to creating a temporal graph type and providing it with all the accessory functions. After that, new layers will be added to the package to build models that fall under the category of STGNNs. Thus, new datasets of temporal graphs will be included in MLDatasets.jl to be used for training the models. Finally, tutorials will be produced to complete the project, introducing the new temporal graph type and showing how to perform temporal graph tasks using the added data, model and features.

<p>At the end of the project, the following objectives should be met:</p> <ul> <li>host-based statistics are maintained and presented to user when asked to do so</li> <li>website-based statistics are maintained and presented to user when asked to do so</li> <li>test coverage is increased</li> <li>wget2 documentation is enhanced to include “wget2 internals” dev doc along with the updated user manual.</li> </ul>

This project creates a strong, production-ready Behavioral Framework for Mesa by addressing the limits of hardcoded agent logic. Using iterative prototyping, comparing it to classic models like Sugarscape and Wolf-Sheep, and analyzing across different frameworks such as Agents.jl and GAMA, this initiative provides event-driven decision rules, lazy-evaluated states, and constraint patterns.

<p>Development of a MBDyn interface from-and-to Flight Gear, that easily lets to get current values of any arbitrary field from the Flight Gear Property Tree, or impose them in order to control Flight Gear using MBDyn as flight-dynamics model. The interface must allow MBDyn-users to communicate with Flight Gear without the need to manage:</p> <ul> <li>sockets</li> <li>data cast when getting or sending values (and related byte-order troubles)</li> <li>data padding dependent on the architecture and on the structure of Flight Gear classes (FGNetFDM, FGCtrlsFDM)</li> </ul>

Seeing the current increasing demand of high performance batteries, accurate thermal modelling of battery behaviour is essential. This project extends PyBaMM by adding the capability to simulate battery temperature in three dimensions. It starts by developing 3D meshes (box, cylinder etc) and FEM method. Then we develop a 3D thermal model for batteries, initially assuming a constant heat source. This thermal model is then coupled with existing battery models (like the SPM or DFN) so that the heat generated during battery operation can be simulated. The model will also eventually allow temperature data from the thermal simulation to feed back into the battery model, enabling more realistic, two-way interactions.

I am C Innocent Pious, a final-year B.Tech Computer Science student from Chennai with hands-on experience in the colcon mixin codebase. Prior to this proposal, I identified and fixed a multi-year bug in multi-mixin argument merging (Issue #40, PR #59), adding six regression tests with all tests passing. This project introduces mixin composition to colcon mixin, allowing a mixin to declare dependencies on other mixins via a "mixin" key. These dependencies will be resolved automatically using a dependency graph, topological ordering, and cycle detection, eliminating the need for users to manually specify transitive dependencies in every colcon invocation. The deliverables include a dependency resolution system, cycle-safe ordering mechanism, well-defined argument merge semantics, comprehensive test coverage, and updated documentation integrated into the upstream repository.

<p>PortfolioAnalytics is a popular R package designed to provide optimized solution and visualizations for portfolio allocating problems with complex constraints and objectives. In order to finish the optimization tasks, it contains many solvers from other R packages. In the summer of 2019, I implemented three optimization engine into PortfolioAnalytics package. I implemented Rglpk as an advanced linear programming problems solver to manage assets objective to the ratio of a portfolio return over its expected shortfall. I implemented osqp as a more involved quadratic programming problems solver to build a portfolio according to Modern Portfolio Theory, and generate efficient frontier as a preference for users. I implemented mco as a progressive multicriteria optimization tool to satisfy portfolio managers' complex needs. With the effort of these new engines, the PortfolioAnalytics is able to solve the optimization problems precisely, fast, and squeeze all possible profit.</p>

Description: Pixie performs automatic tracing and parsing of various protocols (e.g. HTTP, MySQL, Kafka), but there are many others that still need to be added. You can help add protocol parsers for technologies such as Mongo, AMQP (used by RabbitMQ and other message queues), or another protocol of your choice.

<p>Large scale haskell projects tend to have a problem with lockstep distribution of packages (especially backpack projects, being extremely granular). The unit of distribution (package) coincides with the buildable unit of code (library), and consequently each library of such an ecosystem (ex. amazonka) requires duplicate package metadata (and tests, benchmarks...).</p> <p>This project aims to separate these two units by introducing multiple libraries in a single cabal package.</p> <p>This proposal is based on <a href="https://github.com/haskell/cabal/issues/4206" target="_blank">this issue</a> by ezyang.</p> <p>Current status: <a href="https://github.com/haskell/cabal/projects/5" target="_blank">https://github.com/haskell/cabal/projects/5</a> and <a href="https://summer.haskell.org/news.html" target="_blank">https://summer.haskell.org/news.html</a></p>

Scrum Helper is a Chrome extension that helps developers automatically generate scrum reports from their source control activity. Today, it works exclusively with GitHub, leaving out a large portion of development teams who rely on GitLab, Gitea, or Bitbucket for their daily workflows. This project extends Scrum Helper into a true multi-platform tool. By introducing a clean plugin-based adapter architecture, each SCM platform gets its own isolated integration while the core reporting logic stays platform-agnostic. The result is a more maintainable codebase that any future contributor can extend with minimal effort. By the end of this project, developers on GitHub, GitLab, Gitea, and Bitbucket will all be able to generate automated scrum reports from a single extension, without changing how they work.

<p>QuTiP is best known for solving open quantum system dynamics. At the same time, it also has a Quantum Information Processing (QIP) submodule representing ideal quantum circuits. A tempting ideal to combine them is introducing random noise into the circuit by linking the circuit back to the Hamiltonian driving the evolution of the qubits. This could then be used to study the possible noise occurring in the experiments and how it will influence the result.</p>

WebAssembly's call stack limit is unspecified by the spec and varies across host environments. As a result, any Kotlin/Wasm program that uses mutual recursion or deep tail calls is vulnerable to stack overflow at runtime, with no way to guarantee safe execution across browsers and runtimes. Kotlin's existing tailrec modifier mitigates this for simple self-recursion by rewriting functions as loops, but it cannot handle mutual recursion or indirect calls, and requires an explicit annotation that many developers will not add. The WebAssembly Tail Call proposal (standardized and part of the Baseline target since 2024) addresses this at the instruction level with return_call and return_call_ref, which discard the current stack frame before transferring control and reduce stack consumption from O(n) to O(1) regardless of recursion structure. This project integrates that proposal into the Kotlin/Wasm compiler backend. The work covers adding the missing RETURN_CALL opcode to the Wasm IR layer, detecting tail call positions in the code generation pipeline and emitting return_call and return_call_ref in place of the current call + return two-instruction sequence, writing a test suite covering mutual recursion and virtual dispatch across multiple host environments, and benchmarking return_call against the existing loop transformation to evaluate the tradeoffs.

<p>Building a library that would take customer and transactional data as input to identify Good/Bad Loans, Frauds and other risk management activities using Machine Learning Algorithms</p>

<p>"The goal of the Web of Things is to extend the web of pages into a web of things by giving connected devices URLs on the World Wide Web. This will allow the web to be used as a unifying application layer for a decentralized Internet of Things."</p>

After Postorius and Hyperkitty call the API of Mailman Core to manage the data, they need to poll the Core to confirm that the modification has been successfully executed. This blind query mechanism will increase network and server load and be difficult to scale. This theme uses NATS's publish subscribe mechanism to optimize the steps of getting modification result. After the modification is successfully executed in Mailman Core, a message will be posted on the publish-subscribe(pub-sub) topic. Postorius and HyperKitty can obtain information about the modification result by subscribing to the pub-sub topic and then proceed to the other step.

<p>Reliability is essential for communication using XMPP. Although basic XMPP is not reliable in some situations. One of these situations is losing long-lived TCP connection between client and server or server and server because of network or destination failure. If this connection isn’t properly closed, sender will be unaware of the loss and connection will appear as open to server until TCP timeout is reached. All messages which will be sent by server during this time will be lost.</p> <p>The goal of this project is to implement XEP-0198 for server-to-server communication in ejabberd. This extension allows to request stanza acknowledgement and quickly resume session. Any messages that were not delivered over previous connection will be retransmitted during session resumption without duplication.</p>

Tenants in Thanos Receivers currently get one external label which indicates their tenant ID. We would like to implement attaching arbitrary external labels to each Thanos Tenant. This functionality is useful for various different use cases, such as improving performance when querying data for tenants which share the same labels.

By finishing this project, we could provide an event-driven application that connects EventMesh to Knative. Apache EventMesh community could obtain the ability of Knative, including publishing/subscribing event messages. It also provide convenience to users who want to use Knative, and as we provide a mature SDK, users can directly use our SDK in EventMesh to build their applications.

CRIU can checkpoint/restore a trivial hello_word process to running Linux containers. However, with the current implementation of CRIU, it can't checkpoint/restore a process that has a memfd_secret file descriptor(s) opened. So, the purpose of the proposed project is to add new functionality to successfully checkpoint/restore any process that has memfd_secret file descriptor(s) opened.

<p><strong>Mininet is a network emulator for creating virtual networks. The nodes that it spins up are isolated in network namespaces and use real kernel instances(shared kernel space) all in one host OS. So you have a full blown network up and running on top of a single Linux kernel. </strong></p> <p><strong>The goal of the project is to enable creation of XIA networks and configuration of XIA nodes using Mininet.</strong></p> <p><strong>Put in other words, the Mininet APIs should allow configuration of the XIA nodes and creation of complex topologies. The proposal throws more light on how I plan to use the existing Mininet APIs and create new ones to configure the hosts using XIA specific parameters.</strong></p>