Siddhesh Bhupendra Kuakde SiddheshKukade

Installation of Docker Engine on Ubuntu

Video Reference : https://www.youtube.com/watch?v=lqFvoEBHSIQ&t=5s

Supported OS :

Ubuntu Jammy 22.04 (LTS)
Ubuntu Focal 20.04 (LTS)
Ubuntu Bionic 18.04 (LTS)

Introduction RISCV-ISAC: RISC-V ISAC is an ISA coverage extraction tool. Given a set of coverpoints and an execution trace of a test/application run on a model, ISAC can provide a report indicating in detail which of those coverpoints were covered by the test/application. ISAC also holds the capability to provide a detailed quality analysis on data propagation occurring within the test/application.

Feature additions on ISAC:

Instruction object improvement (link)
Improve data propagation reports to capture multiple signatures per coverpoint (link)
Explicitly specify redundant coverpoints in the terminal messages ((link)

Introduction RISCV-CTG: RISCV-CTG is the RISC-V based Compatibility Test Generator. This tool is used to generate tests used in the official RISC-V Architectural Test Suite and the RISC-V

Questions

The first task is mandatory and selection will be based on the performance in the task. The second task is optional and a nice to have.

Write a python program which takes a valid RISC-V ISA string(described in Chapter 27 of the RISC-V specification(unpriv)) and generates coverpoints for each of the relevant bits in the extension field of misa register described in section 3.1.1 of the RISC-V privileged ISA. Briefly describe the events (i.e list out the possible exceptions and why) in the test which will occur while testing one such coverpoint. Refer to the csr_comb node described here to understand the format for the coverpoints. Example: for RV32IM, two relevant coverpoints are to check whether the bit at ind

404 Kittens

This is how we pulled off our amazing 404 page.

A Pen by nclud team on CodePen.

License.

Final Report: GSoC '21

Student: Tasneem Koushar
Github: tasneemkoushar
Organisation: Chromium
Mentors: Jack Franklin, Mathias Bynens
Project: Automation of Puppeteer's Documentation

Whenever I want to create pull requests to a repo that I don't have write access to, I:

Fork the original repo to my account.
Clone the original repo to my local machine.
Add my fork as an additional remote and make it the push default.
Make changes in a new branch locally.
Push this branch to my fork.
Create a pull request from there.

Most active GitHub users (git.io/top)

The list would not be updated for now. Don't write comments.

The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.

Because of GitHub search limitations, only 1000 first users according to amount of followers are included. If you are not in the list you don't have enough followers. See raw data and source code. Algorithm in pseudocode:

githubUsers

	# Codespaces zsh prompt theme
	__zsh_prompt() {
	local prompt_username
	if [ ! -z "${GITHUB_USER}" ]; then
	prompt_username="@${GITHUB_USER}"
	else
	prompt_username="%n"
	fi
	PROMPT="%{$fg[green]%}${prompt_username} %(?:%{$reset_color%}➜ :%{$fg_bold[red]%}➜ )" # User/exit code arrow
	PROMPT+='%{$fg_bold[blue]%}%(5~\|%-1~/…/%3~\|%4~)%{$reset_color%} ' # cwd

	<!DOCTYPE html>
	<html>
	<head>
	<title>Box Shadow</title>

	<style>
	.box {
	height: 150px;
	width: 300px;
	margin: 20px;