Explore Projects

This project will develop the core execution engine for Music Blocks 4, an educational platform that helps students explore music, mathematics, and programming through block-based coding. The Program Engine will allow users to create musical programs by arranging visual blocks and then execute these programs to generate music with precise timing. I will implement a robust Abstract Syntax Tree (AST) representation of programs, an interpreter that executes block instructions, a state manager to track variables and program state, and a scheduler for time-based musical operations. Key deliverables include a complete execution system for basic programming constructs, music generation capabilities, concurrent execution for multi-part compositions, and comprehensive error handling to provide clear feedback to users. The end result will be a performant, reliable foundation that enables Music Blocks users to create, share, and learn through interactive musical programming, with special attention to educational use cases and accessibility.

The proposal is about improving the QEMU emulator for the armv7 architecture on FreeBSD OS, it's goal is to get a simple C++ hello-world program to compile and run inside an armv7 jail hosted on an amd64 machine, using clang. To achieve this, about 32 syscalls need to be implemented for the qemu-bsd-user master branch, they are already implemented in the blitz branch, by the project mentor. The project is to add them to the master branch, perform testing and debugging of any errors, add them in a series of patches, each should pass the code review guidelines set up by QEMU developers. The solution starts by getting a stack trace of the syscalls that the compiler calls when using the blitz build of qemu-bsd-user, then compare them to the ones that succeed when using the master build of the qemu-bsd-user. Having done this, now we know which syscall are already added and those that are not. Now we proceed to add the missing ones, the project plan is included in the proposal. I will be delivering 32 patches to the qemu-devel mailing list, each one corresponding to a missing syscall.

Apache HugeGraph's query engine relies on Java 11, TinkerPop 3.5.1, and Groovy 2.5.x, facing critical issues: the security sandbox depends on Java's deprecated SecurityManager and a blacklist already bypassed in CVE-2024-27348, while TinkerPop 3.5.x lacks 26 new Gremlin steps, GraphBinary, and JDK 17 support. This project will execute a phased upgrade to Java 17 + TinkerPop 3.7.x + Groovy 4, covering full TinkerPop API migration with custom Steps/Strategies adaptation, a security sandbox redesign from runtime blacklist to a three-layer compile-time whitelist defense using Groovy 4's @CompileStatic and AST Customizers with configurable enforcement modes (strict/warn/off), extension to PD/Store distributed modules, and performance benchmarking on the Twitter-2010 dataset. Deliverables include the upgraded codebase (PR), the new compile-time security sandbox, PD/Store module upgrade, a quantified performance benchmark report, full regression test reports, and a complete documentation set.

Project focused on improving the user experience of editing Gradle Kotlin Scripts (KTS) in Eclipse. With contributions to the Gradle Eclipse plugin, users will benefit from improved code error highlighting, code completion, and Ctrl-Click to definition functionality. By improving support for editing KTS in Eclipse, developers will be able to work more efficiently, resulting in faster and higher quality software development.

This project is focused on enhancing the functionality of Kotlin Coroutines by developing parallel stacks for use in the debugger. The goal is to provide developers with an effective means of debugging their asynchronous and concurrent code. To achieve this objective, an IntelliJ IDEA plugin will be developed that will communicate with the Kotlin compiler during a debugging session. The plugin will be able to retrieve relevant information about coroutines at any state of the program and leverage this information to generate a parallel stacks view. This will provide developers with a comprehensive overview of the execution flow of their coroutines, allowing them to more effectively identify and resolve issues in their code. Overall, this project represents a significant advancement in the toolset available to Kotlin developers, enabling them to build more reliable and performant coroutine-based applications.

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>Currently, Android uses its own annotations that are similar to some in the Checker Framework. Examples include the <em>@NonNull</em>, <em>@IntRange</em>, <em>@IntDef</em>, and others annotations. The goal of this project is to create Android Resource and Thread type checkers using the Checker Framework. Then, do a case study to show the utility (or not) of pluggable type-checking, by comparison with how Android Studio currently checks the annotations.</p>

<p>Index Checker warns the user about code that can throw an IndexOutOfBoundsException. In this case study, four open source libraries will be annotated using Index Checker. Some improvements to Checker Framework JDK annotations are expected. The goal is to find possible inconsistencies or bugs in the annotated libraries or in the checker itself.</p>

<p>The goal of this project is to implement a checker for bounded-size strings in the <a href="https://checkerframework.org" target="_blank">Checker Framework</a>, as described on the <a href="https://checkerframework.org/gsoc-2017-ideas.html#Bounded-size_strings" target="_blank">GSoC 2017 Ideas page</a>. The checker will be based on a type system in the form of Java type annotations (<a href="https://jcp.org/en/jsr/detail?id=308" target="_blank">JSR 308</a>). The annotations will state that the annotated strings and arrays have a bounded size, and running the checker will statically check that the specified size is never exceeded.</p>

I propose to develop NullnessLight, a lightweight, easy-to-use nullness checker built on the Checker Framework. NullnessLight will trade full soundness for usability and speed, helping developers catch common null-related bugs without requiring extensive annotations or setup. Inspired by tools like NullAway, NullnessLight will disable some of the more complex features of the existing Nullness Checker, such as initialization analysis and alias invalidation, and provide user-configurable options for these trade-offs. This project will broaden the Checker Framework's usability spectrum and help users gradually adopt deeper verification. Deliverables include the implementation of NullnessLight, a suite of comparisons with existing checkers (e.g., NullAway, FindBugs), and documentation with usage recommendations.

<p>The JavaParser plays a significant role in the functioning of the StubParser project. The StubParser (sub-project of the Checker Framework) is the tool that is designed to parse stub files with AST (Abstract Syntax Tree) generation and visitor pattern support. Stub files are a way to describe the specification of a library. They could be Java classes or have method bodies that may be skipped for brevity. The project was created by modifying and extending the JavaParser v.1.0.7 several years ago. Hence StubParser is missing a number of Java 6, 7, and 8 features.</p> <p>The goal of the "Update to the newer version of JavaParser" project is creating a new version of the stub parser that is based on the latest version of JavaParser tool which is 3.1.4.</p>

<p>Checker Framework has a Dataflow Framework for Java Language. This is useful to infer more specific types in Checker Framework. This framework is not limited to Checker Framework and helps to implement other tools to analyze Java programs.</p> <p>Dataflow Framework will provide a builder which creates control flow graphs from ASTs. It also provides transfer functions, analyze, abstract value and store interfaces. Checker Framework has their own data flow analyzer to infer more specific types.</p> <p>Some of dataflow issues are reported which cause false negative or positive and performance problems. In this project, I'll address most of these issues to make it more accurate and faster and remove some false positives or negatives from Checker Framework.</p> <p>I'll do</p> <ul> <li>fix to handle correctly switch, varargs call, try-catch, finally, postfix inc or dec, and inner classes</li> <li>improve performance for many assignments in a block</li> <li>fix to handle correctly flow expression</li> </ul>

<p>This project consists of:</p> <p>1.)Allowing the Signedness Type System to capture the signedness of boxed integral types, special Java wrappers for integral primitives and BigInteger class.</p> <p>2.) Annotate and provide new methods with the JDK and Guava classes.</p> <p>3.) Extend the refinement of Value Checker based on their value ranges to wrappers classes and expressions.</p> <p>4.) Doing case studies on files and annotate the necessary changes.</p>

<p>This project consists of:</p> <ol> <li><p>Annotating <em>ASM</em> with signature string checker of checker framework.</p> </li> <li><p>Find and report bugs if any found during the process.</p> </li> <li><p>Maintain an annotated fork of <em>ASM</em>.</p> </li> <li><p>Do the same with other similar tools in any time left in the summers.</p> </li> </ol>

<p>This project is about enabling the checker framework to handle JDK9. As of now, the checker framework runs only on JDK 8. Since JDK 9 has already been released and JDK 10 is around the corner, the checker framework needs to be handling them. Many project owners are not able to use the power of such a powerful framework owing to the compatibility issues. This project attempts to make the checker framework compatible with JDK 9. Moreover, it also attempts to create a log file of the changes made to the framework, which can then be implemented as an instruction set for the people who want to annotate the JDK or make the framework compatible with the future releases of Java.</p>

My project will be Making a New Documentation Site Engine for Keptn which can handle a large number of documentations projects of Keptn. Currently, the Keptn documentation site is based on Hugo based theme called hugo-serif-theme. For tutorials, Codelabs is also used. While extremely handy for smaller projects and initial versions of Keptn, this toolchain has serious deficiencies for larger-scale projects like Keptn. I am going to propose a New Documentation Site Engine that will be based on Docusaurus. Docusaurus is an optimized site generator in React. Docusaurus helps you to move fast and write content. Build documentation websites, blogs, marketing pages, and more. The main focus of Keptn New Documentation Site Engine will be managing large-scale documentation and complex documentation projects. So two major things which are needed in the documentation engine are Multiple repository docs support and Versioning of Docs support. Find my detailed GSoC 2022 Project Proposal at https://github.com/iamrajiv/GSoC-2022/blob/main/GSoC_2022_Project_Proposal.md.

This project will focus on improving Zulip web app and shipping new features. Deliverables focuses on zulip message system and permission settings but this will probably end up reaching wider areas of Zulip.

<p>Nmap has become my fascination ever since I started actively using it. It is undoubtedly one of the best security tools. My project Idea is "Vulnerability and Exploitation Specialist" and I would be spending my summers looking for the vulnerabilities that would be suitable to be added to Nmap Scripting Engine and will implement them. I will also be working on some web scanning scripts.</p>

<p>GNOME is lacking a chat client which looks “modern” and is thus visually and user experience-wise attractive to new users. Dino fits well into the GNOME desktop and improving Dinos functionality would provide the community with a good chat client. This project adds an efficient and visually appealing message search with a good user experience in Dino.</p>

<p>The current UI of Pitivi serves well to its aim of being an intuitive and flexible application for newbies as well as professionals but a little bit of polishing can take it more closer to that aim. This project will focus on improving the UI of Pitivi to enhance user experience. This consists of two tasks:</p> <p>1) Integrating the Welcome dialog box into Pitivi's main window and displaying projects in a more informative, discoverable, and user friendly layout.</p> <p>2) Allowing easy resizing of the video previewer.</p>

Description: Chaos Mesh is not like Chaos Engineering as a Service now: - Poor observability: the result of chaos experiments are not easy to observe and judge, the users need to check whether the Chaos effects by manual. - Chaosd(for physic node) is too simple: only supports command line operation, does not support task scheduling and life cycle management. - The costs of learning operation and maintenance are high: the maintenance of Chaos Mesh and Chaosd are not unified. - It should be a unified place to manage Chaos experiments for multiple platforms and multiple clusters, and can see the monitoring data of the experiment.

<p>The current finance industry practice in reporting risk and performance measure estimates of assets and portfolios does not typically include reporting the standard error of these estimates: consumers have no clue as to how accurate those estimates are. With the recent work of Chen and Martin (2018), a new approach based on influence functions has been developed to provide an accurate estimate of standard errors of risk and performance of assets and portfolios for returns with both serially uncorrelated and seri- ally correlated returns. This project involves (1) developing a new R package named InfluenceFunctions and (2) integrating the R package EstimatorStandardError in conjunction with InfluenceFunctions into the existing R package PerformanceAnalytics, with the goal of giving PerformanceAnalytics pack- age users more functionality and the option for the first time to report the standard errors of a very wide range of risk and performance measure estimates of assets and portfolios when returns are serially correlated as well as when they are uncorrelated.</p>

The runtimes error handling code stems from ancient times where rust was younger, and we were more naive. As such, it is more grown than designed in many places. With the knowledge of the past three years and stabilization of the codebase, now is a good time to polish it and make errors an exciting user experience.