Mohamed Awnallah mohamedawnallah

Gotta Catch 'Em All - GSoC 2023 Ceph Project

Below are detailed instructions regarding the Gotta Catch 'Em All - GSoC 2023 Ceph Project

Introduction

Coverity is a tool used by the Ceph project to find issues in the code. Even though Coverity it is a commercial product, they perfom regular scans for many Open Source project, including Ceph.

The Ceph storage system has an S3 compatible Object Store interface, implemented by the RADOS Gateway (or RGW) component of Ceph.

Keybase proof

I hereby claim:

I am mohamedawnallah on github.
I am mohamed_awnallah (https://keybase.io/mohamed_awnallah) on keybase.
I have a public key ASAbuUZPIrSpVfLAL443rSyh_13Rd5BrXHCoXX2gahG7Xwo

To claim this, I am signing this object:

sequenceDiagram
    participant User
    participant LND_A as LND Node A
    participant LND_B as LND Node B

    %% Initialization Phase
    User->>LND_A: UpdateChannelParams RPC
    LND_A->>LND_A: Status: Initialized
    LND_A->>LND_A: Validate parameters

	dev@dev:~/side-header-loading-ab-testing-experiments/neutrino_playground$ ./script.sh
	--- Benchmarking with memory limit: 16MB (16777216 bytes) ---
	16777216
	0
	./script.sh: line 11: 6017 Killed timeout 300s sudo cgexec -g memory:neutrino_headers_import_mem_limiter /usr/local/go/bin/go run main.go 2> /dev/null
	App Exit Code: 137
	Total Time: .149283609 seconds
	Peak Memory Usage (from events.local:max): 1408 bytes
	OOM Events: 72
	OOM Kills: 2

	#!/bin/bash

	# Test cases
	commands=(
	"./run_pytest.sh test_suite 'tests/unit' ''"
	"./run_pytest.sh test_suite 'tests/unit' '--maxfail=3 -m slow -n 4'"
	"./run_pytest.sh test_suite 'tests/integration' '--maxfail=3 -m \"slow or flaky\" -n 4'"
	"./run_pytest.sh test_suite 'tests/unit' '--maxfail=3 -m 'slow or flaky and not unreliable' -n 4'"
	"./run_pytest.sh test_suite 'tests/unit' '--maxfail=3 -m slow -k test_function -n 4'"
	"./run_pytest.sh test_suite '' '--maxfail=3 -m nonexistent_marker'"

	This is a common issue when building `grpcio-tools` on ARM64/aarch64 architecture. The compilation is failing during the C++ extension build process. Here are several solutions to try:

	## Solution 1: Use Pre-compiled Wheels
	First, try updating pip and using pre-compiled wheels instead of building from source:

	```dockerfile
	# Update your Dockerfile line 65 to:
	RUN pip3 install --upgrade pip setuptools wheel && \
	pip3 install --only-binary=grpcio,grpcio-tools grpcio-tools mypy-protobuf
	```

	{
	"ID": "cc885c6f-bb0a-4b46-8960-cff38aa91c88",
	"Containers": 0,
	"ContainersRunning": 0,
	"ContainersPaused": 0,
	"ContainersStopped": 0,
	"Images": 0,
	"Driver": "overlayfs",
	"DriverStatus": [
	[

	// Copyright (c) 2025 The btcsuite developers
	// Use of this source code is governed by an ISC
	// license that can be found in the LICENSE file.

	package wallet

	import (
	"fmt"
	"testing"
	"time"

Mohamed Awnallah mohamedawnallah

Gotta Catch 'Em All - GSoC 2023 Ceph Project

Introduction

Table of Contents

Keybase proof