PowerShell

I regularly run scoop update; scoop status to keep all my apps up to date:

> scoop update
Updating Scoop...
Updating 'extras' bucket...
Updating 'java' bucket...
Updating 'main' bucket...
Updating 'nerd-fonts' bucket...
Updating 'versions' bucket...

> scoop status
Scoop is up to date.
Everything is ok!

Today I wanted to try VSCode's new [PowerShell Notebook Mode](htt

Thanks a ton for any helpful feedback

I need help with getting best quality GIFs.

I am not used to CSS syntax so it would be amazing if you add a lot of example config.yml files. Also, try adding config.yml files for the GIFs you are displaying in your README.md. They look fantastic. I have spent hours trying to get perfect GIF but no luck.

I don't know what value to give for shadow

I have created a dracula theme for this awesome terminal:

dracula.zip

Is there a way to push it into the repo?

Description

New-AzPortalDashboard fails to parse a hashtable converted from a JSON dashboard definition downloaded from the portal.
The attached JSON dashboard definition was downloaded from an existing simple dashboard definition created in the portal in order to test creating a new dashboard definition using PowerShell. The commands and output are shown below.

[portal.txt](https://git

Checklist

• Feature request has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

Summary of the feature request

Hi,

we are internally using Gitlab

Describe the bug

Some content served with "content-encoding: gzip" fails to get decompressed. The same URL works when retrieved as $var = Invoke-RestMethod <url> in PowerShell or in the browser.

Still trying to figure out if this might be a server issue

Please complete the following:

Version: 1.0.245702+40c8c12f24bf25871df042025338d97181e1507a
Build date: 2021-09-09T15:5

Feature Request

A simple command that just pulls readable information from msdb..suspect_pages.

Problem to solve

At times you need to monitor the suspect pages a server may have or verify after you get logical errors returned from DBCC results, or even finding the dreaded 823/824 err