Skip to content

Conversation

@pull
Copy link

@pull pull bot commented May 10, 2022

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label May 10, 2022
@squash-labs
Copy link

squash-labs bot commented Feb 14, 2023

Manage this branch in Squash

Test this branch here: https://master-n02a3.squash.io

pekkaklarck and others added 28 commits May 7, 2025 08:57
- Escape variables used in documentation.
- Remove test that didn't actually test anything.
…src/web/npm_and_yarn-7ad2ad6968

Bump base-x from 3.0.9 to 3.0.11 in /src/web in the npm_and_yarn group across 1 directory
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.4.0 to 5.6.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5.4.0...v5.6.0)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: 5.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Normal type hints should be used instead. Part of #3278.
This documentation was added as part of #5396.
- Document the ERROR level under the Log levels section.

- Clarify documentation related to logging with the ERROR level when
  `--exit-on-error` is enabled.

- Explain that TRY/EXCEPT cannot catch errors stopping the whole
  execution.

Fixes #5424.
Move validation that embedded args with library keywords don't support
embedded types to a better place. Also move related tests to suite
testing embedded args with library keywords. Related to #3278.
No need to use typing_extensions.TypedDict in these tests when
typing.TypedDict works just fine. That avoids problems with
Python 3.14 (#5352) caused by a bug in typing_extensions:
python/typing_extensions#593
Also some cleanup to requirements in general.
Missing part of the already closed #5417.
Also small adjustment to when to raise a timeout on resume. Earlier
timeout was raised on the first resume after timeout had been
exceeded, but now the runner must be fully resumed. This behavior is
more logical than the earlier.

The change shouldn't affect execution at all. The reason is that if
timeout is paused in nested manner, `BuiltIn.run_keyword` has been
used in recursively and each recursive call has its own timeout. The
last one of them will raise a timeout on resume immediately after the
timeout has been exceeded anyway.

This is part of #5417.
This mostly simplifies unit tests.
- Enhance tests related to pausing timeouts.
- Fix the aforementioned tests on Windows.
- Enhance Windows timeout code to avoid race conditions.

Related to #5417.
pekkaklarck and others added 30 commits November 6, 2025 16:23
The change was done in 366b7f5. It was proposed in #5533 and that
issue explains why it was initially considered a good idea and why we
eventually decided otherwise.
The new libdoc build pipeline optimizes html so that attributes are not quoted.
Take that inot account when writing generator information.
…s/actions/setup-node-6

Bump actions/setup-node from 5 to 6
There are use cases for printing a warning or error message to the log
but not to the console.

This commit adds an optional also_console argument to logger.write,
logger.warn, and logger.error. Its value is stored in the message object
and based on it the loggers in src/robot/output/console/ print the
message or not.

Fixes #5460.

* atest: Update "Write messages to console" test

Messages logged with `also_console=True` are now printed to stderr
instead of stdout (see previous commit).

* atest: Test writing warning and error messages only to log
- Rename `also_console` argument to `console`. Preserve the old
  argument with `robot.api.logger.info` for backwards compatibility
  reasons for now.

- Enhance argument documentation in `robot.api.logger`.

- When writing normal messages (i.e. not warnings or errors) to
  console, always write them to `stdout` and never use extra
  prefix. This was a bug in PR #5462.

- Write normal messages to console in a single place.

- Enhance `Log` so that it can log warnings and errors so that they
  aren't written to console.

- Use standard ValueError, not DataError, if log level is invalid.

Related to issue #5460.
Mostly cleanup. In some cases tests were also enhanced to validate
more values.
Based on my last review to PR #5528. Part of #5527.
Only done if `None` is an explicit type, not if `None` is only used as
a default value.

Fixes #5545.
Use explicit `_string_convert` and `_non_string_convert` instead of
`_convert` where feasible.
- Sets require converted values to be Collection instances, being
  Container is not enough.

- We should in general talk about collections, not containers.
- Clarify how true and false strings are handled.
- Remove references to ancient RF versions.
- Fix indentation with Secret and mention it's new in RF 7.4.
Hopefully makes all tests pass
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.