test

Current behavior

According to the docs, https://docs.cypress.io/api/commands/wait#Aliases

and also the type definition for wait() -

wait(alias: string[], options?: Partial<WaitOptions>): Chainable<Interception[]>

a wait that accepts an array of aliases, should return an array of Interception

This doesnt seem to be the case when the array has one interception. The

Description of the problem / feature request:

Bazel crashes due to an internal error when using a bzlmod registry that doesn't correctly specify a bazel_registry.json file. The stack-trace printed by Bazel when it crashes is included in the last section below.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

To demonstra

Currently, when entering epic mode the README is frozen in the last level of the tower. When you're trying to fine-tune the score for a level other than the last one, it would be helpful if we had the README for that level available. The proposal is that when entering epic mode, the README is updated with all levels, one following the other.

Example:

# Starbolt - beginner

uiautomator2的版本号：2.11.1

使用device.image.match时匹配错误

模版图像是：

截图：

匹配结果：{'similarity': 0.9961444735527039, 'point': [319, 673]}

直接使用findit模块测试也是这么高匹配度，估计是findit模块不给力，是

Clear and concise description of the problem

Error enumerable properties are not shown for test case:

import { test } from 'vitest';

test('throw error with context', () => {
  const err = new Error('This is an error with context');
  err.userId = 32;
  err.companyId = 64;
  throw err;
})

![image](https://user-images.githubusercontent.com/600821/156337522-c37b328b-6b28-

Just like Json Matchers, we should have Yaml Matchers, too. While I'm aware that kotlinx.serialization has no built-in support for YAML, there is the multi-platform https://github.com/him188/yamlkt add-on for kotlinx.serialization which we could probably use.

The issue is based on the discussion in #559.

@zvirja

should we probably modify CI so that doc is published automatically on push to master? This way if we don't want doc to be released right now - just keep it in a branch. Otherwise, we have this non-synchronized docs and manual work.. 😟

@dtchepak

I'm not sure what to do about publishing docs. It would be nice to auto-publish,