Can't import Bestiary - Bat Swarm

Can't import the following statblock:
Bat Swarm      CR 2
XP 600
Male bat swarm (Pathfinder RPG Bestiary 30)
N Diminutive animal (swarm)
Init +2; Senses blindsense 20 ft., low-light vision; Perception +11 (+15 when using blindsense)
Defense
AC 16, touch 16, flat-footed 14 (+2 Dex, +4 size)
hp 13 (3d8)
Fort +3, Ref +7, Will +3
Defensive Abilities swarm traits
Offense
Speed 5 ft., fly 40 ft. (good)
Melee swarm  (1d6 plus distraction)
Space 10 ft.; Reach 0 ft.
Special Attacks distraction (DC 11), wounding
Statistics
Str 3, Dex 15, Con 11, Int 2, Wis 14, Cha 4
Base Atk +2; CMB —; CMD —
Feats Lightning Reflexes, Skill Focus (Perception)
Skills Acrobatics +2 (-10 to jump), Fly +12, Perception +11 (+15 when using blindsense); Racial Modifiers +4 Perception when using blindsense
Ecology
Environment any temperate or tropical
Organization solitary, pair, flight (3-6 swarms) or colony (11-20 swarms)
Treasure none
Special Abilities
Blindsense (20 feet) (Ex) Sense things and creatures without seeing them.
Distraction (DC 11) (Ex) Nauseate foes for 1 rd on failed save. (Fort neg.)
Fly (40 feet, Good) You can fly!

Immunity to Precision Damage You are immune to Precision Damage
Immunity to Staggered Immune to staggered.
Low-Light Vision See twice as far as a human in dim light, distinguishing color and detail.
Swarm Attack (1d6) Deal listed damage to any creature occupying same space at end of move.
Swarm Traits Imm to effects targeting number of creatures (unless mind affect vs. hive mind).
Wounding (Ex) Any living creature damaged by a bat swarm continues to bleed, losing 1 hit point per round thereafter. Multiple wounds do not result in cumulative bleeding loss. The bleeding can be stopped by a DC 10 Heal check or the application of a cure spell or

Looks like #52 again.

I got this statblock from Hero Lab.  You might benefit from retesting with aonprd.com.  Sometimes Hero Lab truncates some of the descriptions.
I used the latest Pathfinder system and your latest module to test this.


./pcm-pcie 0.5 -csv=test.log runs >100x faster than expected

Running pcm-pcie with delays below 1-second returns hundreds of entries per second.
# time ./pcm-pcie 0.5 -csv=test.log -i=1000
...
real    0m3.010s
user    0m0.275s
sys     0m2.596s

1000 x 0.5 != 3
pcm-core, pcm-iio, pcm-latency, pcm-memory, pcm-numa, and pcm-power all appear to function properly.

Additionally, whole numbers appear to be doubled:
# time ./pcm/build/bin/pcm-pcie 1 -csv=test.log -i=10
...
real    0m20.489s
user    0m0.293s
sys     0m0.423s

# time ./pcm/build/bin/pcm-pcie 2 -csv=test.log -i=10
...
real    0m40.480s
user    0m0.290s
sys     0m0.563s

Hello @malventano,
Thank you for reporting this issue. The fix will be available in next update

the fix has been merged into the master branch


Update index.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

it was my mistake i was just exploaring github and i have by mistakenly taped on issue sorry


Update test server documentation

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[ ] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[ ] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Description
Adjust test server deployment documentation to include content of confluence (testserver list, github action and bamboo deployment)
Steps for Testing
Look at https://docs.artemis.cit.tum.de/dev/testservers.html and give feedback
Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Summary by CodeRabbit

Documentation

Updated the Test Servers documentation to include detailed configurations for new test servers, deployment methods, and access protocols.
Enhanced GitHub and Bamboo deployment procedures with step-by-step instructions and visuals for clarity.
Revised testing procedures and server release protocols for improved test server utilization and collaboration practices.

https://artemis-platform--8790.org.readthedocs.build/en/8790/dev/testservers.html
This page seems very outdated in general:

Related issue: https://github.com/ls1intum/Artemis/issues/8200

I suggest we merge this because it really helps. We can fix potential issues in follow-up PRs


Support nodeSelector

What problem does this PR solve?
resolve #560
What is changed and how does it work?
add nodeSelector filterByNode in selector spec
Check List
Tests

Unit test
E2E test

Code changes

Has Go code change

Side effects
Related changes
Does this PR introduce a user-facing change?:

NONE

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@shonge Can you fix the conflicts?

@shonge Can you fix the conflicts and DCO?
I will fix it ASAP.

@shonge Can you fix the CI?

/merge


instancetype: Move remaining functional tests to libvmi

What this PR does / why we need it:
b5131c3cdbad7b previously missed some of these, this change switches the
remaining calls from tests.NewRandomVMIWithEphemeralDisk to libvmi.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/area instancetype

/sig code-quality


update spec page to include 6.d and 6.e.PREVIEW

@ab5tract noted on #raku-doc that https://raku.org/specification/ only has a 6.c ref

see also #68


Added v-hide to general plugins section

General

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[x] Fix
[x] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[x] Title as described
[x] Make sure you put things in the right category!
[x] Always add your items to the end of a list

Open Source

[x] Link description does not contain a link to an author / third-party resource
[x] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[x] The documentation is in English.
[x] The project is active and maintained.
[x] The project accepts contributions.
[x] Not a commercial product

Apps/Websites

[x] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[x] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[x] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[x] A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

You should add it to the main readme

sorry. will do shortly

I have updated and added v-hide to the README.md document. Thanks

You should add it to the main readme

I have updated and added v-hide to the README.md document. Thanks


Use --web-environment-add instead of --web-environment in blackfire error

The Problem/Issue/Bug:
Blindly using and running that command deleted my platform.sh CLI token and I had to generate a new one.
How this PR Solves The Problem:
Add the env variables instead of replacing everything
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Thanks so much!


beep example panics 'Failed to get default endpoint' on macOS release builds

I look all through the implementation and couldn't figure out why cpal::get_default_endpoint would return None under release builds. The coreaudio backend always returns Some(Endpoint).  The execution gets all the way down to event_loop.run(); but thread 'main' panicked at 'Failed to get default endpoint' just before it?
This happens on stable and nightly.

This seems to be related to #148

Seems to be resolved in master at the moment (using rustc 1.21). Closing for now.


Update Unreal Engine to 5.2.0

Blocker on #182
Update the instructions and Unreal Cloud Build building steps to use Unreal 5.2.0.

@kennycoder - Quick question - do we move to 5.2.0 or 5.2.1?

Offline chat: check what versions of build containers are available and align with that


pythonPackages.rtf-tokenize: init at 1.0.0

See https://github.com/NixOS/nixpkgs/pull/347354.
https://pypi.org/project/rtf-tokenize/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

see my comment https://github.com/NixOS/nixpkgs/pull/347354#issuecomment-2402784140

I realized I missed a pyproject on this one — I've added it and hopefully it's now ready for review. :slightly_smiling_face:

Hi @natsukium, any further thoughts on this?


Add test case for empty path

Add some test cases to ensure correct handling of an empty path.

i would close this PR in favor of https://github.com/clickbar/dot-diver/pull/11. I don't see any use in merging this PR right before 2.0 where we change this behavior anyways. @saibotk