test

To reproduce:

1. Open Cypress.
2. Click “View App Data” via the context menu.
3. App crashes.

Desired behavior: View App Data works, and errors with View App Data are gracefully handled.

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模块不给力，是

Describe the bug

If I run Vitest in watch mode, it reports the number of tests passing or failing as expected. But if I delete a test file, the said numbers don't update.

Reproduction

Have two test files, say a.test.js and b.test.js. Each of them have one failing test, so we see 2 suites failing, 2 tests failing.

Now, we delete b.test.js. The status stays the same: 2 suites fai

Kotlin stdlib overloads methods for strings and regex (e.g. replace). The same should be done for kotest assertions. I should be able to write

"I love KoTest assertions!" shouldStartWith "I love"
"I love KoTest assertions!" shouldStartWith "I (love|liebe)".toRegex()

Right now I instead have to use

"I love KoTest assertions!" shouldMatch "^I (love|liebe).*".toRegex

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,