Adrien JALLAIS Naedri

Synthèse

1. OS

Faire l’interface entre:
- les demandeurs (applications dites utilisateur) en ressources (espace memoire, fichiers, connexions reseaux, ...)
- les ressources disponibles : processeurs, memoire, disques, carte reseau, ...
Gerer les offres et les demandes dans leur ensemble, pour arbitrer leur attribution:
dans l’espace (allocation)

VS Code Snippets

Customize VS Code with some code snippets so you can insert them into your projects

For more info see:

Snippets in Visual Studio Code in the docs.
VS Code homepage.

Tasks

Guide for using tasks in VS Code

Tasks menu

How to open and use the tasks menu

Based on the Tasks tutorial.

Run any task

React Context as a store

TYPESCRIPT | useState

Context configuration

// src/services/context/StoreContext.tsx
import React, { createContext, Dispatch, PropsWithChildren, SetStateAction, useState } from "react";

export interface IStore {
  props1: string;

Adding co-authors to Git commits

How do you share credit for a new or altered piece of code when one person commits the change in a pair programming or mob programming session? And when you have questions about a particular change, how can you see in Git who has been working on that change, besides the committer? You add co-autors to your commits. This gist contains information on how to do that, so that the Git commit message contains a list of co-authors, and all co-autors for a commit are automatically listed in GitHubs web UI.

GitHub has some info on specifying co-authors here. This is good info, pretty straightforward. The gist of it (pun intended) is to include at least one blank line and then a line for each co-author like so Co-authored-by: name <[email protected]> at the very end of your commit message.

GitHub's recipe tells you [how to find the right e-mail address to use](https:

Vue Responsive Container

A container component reacting to breakpoints on its own width or height, powered by ResizeObserver and scoped slots.

It is similar to things like vue-resize in that you can use it to observe a component's size. However the ResponsiveContainer will not emit any events, its whole point is to work as declaratively as possible, taking a predefined set of breakpoints you can access in your component.

	Since it's been days, I am guessing this was solved. I am just adding my two cents here for future readers.

	The problem lies with the JwtModule and the JwtStrategy instantiation. They aren't configured properly.
	You need to pass in the algorithms you'd use for signing and verifying the tokens, along with the keys.
	To verify whether the tokens are actually getting generated with the RS256 algo, check the header in the token at https://jwt.io/.
	It would probably show HS256, and since your code didn't use the correct algorithm to sign the token.
	And it fails while token gets verified using the public key.

	To generate signed tokens properly with the RSA key pair:

	{
	// See https://go.microsoft.com/fwlink/?LinkId=733558
	// for the documentation about the tasks.json format
	"version": "2.0.0",
	"tasks": [
	{
	"label": "tsc-watch",
	"group": "build",
	"command": "./node_modules/.bin/tsc",
	"type": "shell",

	{
	// Use IntelliSense to learn about possible attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
	{
	"name": "Start",
	"type": "node",
	"request": "launch",