Is your feature request related to a problem? Please describe.

I try to execute my first GET request and get this result:

I think the first-time-user experience could get improved here.

The hint to F12 vanishes soon, and I think accessing the error message via F12 is not a

Chrome Canary: 90.0.4417.0 (Official Build) canary (64-bit)
OS: Windows 8.1
Lighthouse: 7.0.1

Lighthouse 7.0.1 now issues this deprecation warning when it encounters ::webkit-details-marker:

[Deprecation] ::-webkit-details-marker pseudo element selector is deprecated. Please use ::marker instead. See https://chromestatus.com/feature/6730096436051968 for more details

The info

Summary

When import streamlit and supervisely_lib together in a project there occurs a TypeError.

Steps to reproduce

Code snippet:

import streamlit as st
import supervisely_lib as sly

If applicable, please provide the steps we should take to reproduce the bug:

1. run the code with streamlit run ...
2. see error/traceback when you open the streamlit page

🐞 bug report

✍️ Description

When i press f5 the page(s) are not refreshing. I would expect the page to refresh on all devices.

🕵🏼‍♂️ Is this a regression?

no

🌍 Your Environment

windows

The typescript sample project does not compile the .ts files when ENV is production.

When ENV=development, tsc-watch compiles the code in place before starting node. However, there is no corresponding compile step when ENV=production.

Not a huge deal, as only the dev profile is defined, but I think the README should mention that the compile step is missing when ENV=production.

Please add video length on the video thumbnail just like the official Developer app from Apple.

Right now, I can see the length if I click to go to detail screen, but I would have to do it one by one. It would be great to see the length of each video in a glance so that if i have like 15 minutes, I know which one I can watch.

something like certs in the config for the remotes instead of using AWS_CA_BUNDLE/REQUESTS_CA_BUNDLE, etc.

Related: iterative/dvc#3450, iterative/dvc.org#1079

I am having a project structure as follows:
.
├── README.md
├── modules
│ ├── function-app-consumption
│ │ ├── locals.tf
│ │ ├── main.tf
│ │ ├── output.tf
│ │ └── variables.tf
│ └── storage-account
│ ├── main.tf
│ ├── output.tf
│ └── variables.tf
└── sandbox
├── eastus
│ ├── regional.tfvars
│ ├── functionapp-svc
│ │ └─

Summary

Go 1.16 was released in February and the feature we're most excited about is go:embed. Relevant articles:

• https://golangtutorial.dev/tips/embed-files-in-go/
• https://golang.org/doc/go1.16
• https://golang.org/pkg/embed/

Currently we use pkger to embed web app assets into the binary. This is only enabled in production builds.

Objective

Switch from pkger to