standardize registers on W for all that dont have kW in their name, add disconnect method

Few minor changes

use sun2000 defaults, remove kW unit and only use W
fix gain as per review comments, remove redundant connected attribute, add disconnect method and commentary

Test are clean:
python3 -m unittest discover -v
test_decode_bitfield16 (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_bitfield32 (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_int16_be (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_int32_be (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_invalid (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_multidata (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_string (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_uint16_be (test_sun2000_modbus.TestDataTypes) ... ok
test_decode_uint32_be (test_sun2000_modbus.TestDataTypes) ... ok
test_connect_fail (test_sun2000_modbus.TestSun2000) ... ERROR:root:Connection to inverter failed
ok
test_connect_success (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_init (test_sun2000_modbus.TestSun2000) ... ok
test_read_bitfield16 (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_formatted_bitfield16 (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_formatted_uint32be (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_formatted_with_mapping (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_range_from_disconnected_unit (test_sun2000_modbus.TestSun2000) ... ERROR:root:Connection to inverter failed
ok
test_read_range_from_unavailable_unit (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ERROR:root:A connection error occurred
ok
test_read_range_returns_range_of_register_values (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_range_with_both_quantity_and_end_address_defined (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_range_with_end_address_not_being_greater_than_start_address (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_range_with_no_right_border (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_range_with_quantity_set_to_0 (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_raw_value_bitfield16 (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_raw_value_string (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_raw_value_string_connection_unexpectedly_closed (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ERROR:root:A connection error occurred
ok
test_read_raw_value_string_from_disconnected_unit (test_sun2000_modbus.TestSun2000) ... ERROR:root:Connection to inverter failed
ok
test_read_raw_value_string_from_unavailable_unit (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ERROR:root:Inverter unit did not respond
ok
test_read_raw_value_uint16be (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_raw_value_uint32be (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_raw_value_with_mapping (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_returns_float (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok
test_read_uint32be (test_sun2000_modbus.TestSun2000) ... INFO:root:Successfully connected to inverter
ok

----------------------------------------------------------------------
Ran 33 tests in 0.002s

OK

I'm currently on sickness-leave, will need a few days to come up with this review.

totally overlooked unit test fixes. done now:
python3 -m unittest discover tests
.........ERROR:root:Connection to inverter failed
.......ERROR:root:Connection to inverter failed
.ERROR:root:A connection error occurred
..ERROR:root:Connection to inverter failed
.ERROR:root:Connection to inverter failed
.ERROR:root:Connection to inverter failed
.ERROR:root:Connection to inverter failed
...ERROR:root:A connection error occurred
.ERROR:root:Connection to inverter failed
.ERROR:root:Inverter unit did not respond
......
----------------------------------------------------------------------
Ran 33 tests in 0.002s

OK

@olivergregorius can you please re-start workflow? tests should be all clean now

Sry for the delay, approved and merged.


Newsletter Section Added

Description
Added the Newsletter section at the footer.
Fixes #793
Replace issue_no with the issue number which is fixed in this PR
Screenshots

Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

You have to add this feature under the FAQ section and the coloro of subscribe button should be : #3c38b9


Combine Tags in Robot Files

Is it possible in robot files to need several tags, to run a test case?
Similar to calling from console with option "-i tag1ANDtag2".
Example:
*** Test Cases ***
Test 1
    [Tags]    tag1
    do something...
Test 2
    [Tags]    tag2
    do something....
Test 3
    [Tags]    tag1ANDtag2
    do something....

I would like to run all thee tests with including the tags "tag1" and "tag2" (e.g. with robot -i tag1 -i tag2 ./test_suite.robot
If I specify only the tag "tag1", then only the first test should be executed. (e.g. with robot -i tag1 ./test_suite.robot)
Is there any solution for me?

I'm not certain did I understand what you try to do, but if you just want to give multiple tags to a single tests, use
[Tags]    first    second

Anyway, this tracker is for bug reports and concrete enhancement requests. Questions are best asked on dedicated support forums such as robotframework-users mailing list or on our Slack community.

doing -i tag1ANDtag2 will only run tests with BOTH tag1 AND tag2 set. What you want s to use the OR operator. -i tag1ORtag2 This will run any test with either the tag1 or that tag2 tags set. You can further exclude tags by either adding more tags to the -i argument with  NOT or use the -e argument to exclude any tags listed just like -i includes tags. See the documentation for more information.


Insanse backup size for a small database

PocketBase v0.22.12
I suddenly could not access my pb instance.
After few hours of debugging between hosting and cloduflare, i narrowed it down to db being corrupted or something (i cannot access it to verify).
I downloaded the 700MB backup from S3 unzipped it and VOILA!

Tried to open the file and it seems it has tons of empty spaces. Which explains how 13GB file got zipped to 700 MB.

I don't know what happened. I can take into account even vulnerability / security / hack attempt. I might have such "fans" on the project.
Will try to use one of the older 7days backups.. this one obviously unusable and done.

LE: all my auto-backups are corrupted.
Also,

Ok, somehow (since I was using S3 and did not have to manually upload the backup) .. I could restore one of the backups.
Everything seems normal.. any ideas what to debug !?

@bloor Before making bold statements like "insane" and that something is corrupted it will help to provide an error illustrating that. The side-car -wal file is not a plain text and I'm not sure what exactly do you expect to see as a content.
In any case, what actually is the problem - the backup size?
The WAL file could grow if there is a blocking transaction, as it is the case with the backup operation:

https://www.sqlite.org/wal.html
A checkpoint can only complete when no other transactions are running, which means the WAL file cannot be reset in the middle of a write transaction. So a large change to a large database might result in a large WAL file. The WAL file will be checkpointed once the write transaction completes (assuming there are no other readers blocking it) but in the meantime, the file can grow very big.

This unfortunately is a limitation of both the current SQLite WAL implementation (there was attempt to fix it in WAL2 but the effort exist only as experimental SQLite trunk/branch) and how the PocketBase backups work (during backup the application is in "read-only" mode and writes are blocked).
For the latter part, there are plans to optimize it together with https://github.com/pocketbase/pocketbase/issues/4647 but remains for later consideration because it has a lot of edge cases and I don't want to block further v0.23.0 release.
If the current backups implementation causes you trouble, you can simply disable them and chose a different backup strategy, e.g. running sqlite3 .backup command + rsync (you can find an example script in https://github.com/pocketbase/pocketbase/discussions/4254; while more performant note that this has the limitation that the db file is not locked with the storage changes meaning that during the db backup generation there could be storage files that were removed or added).
I also strongly recommend to update your PocketBase executable to v0.22.25 because there were several fixes since v0.22.12 (including a security one related to the OAuth2 email autolinking). For more details, please check the v0.22.x CHANGELOG (technically big jump with just ./pocketbase update should be safe in this case but make sure to test it first locally and to have a recent backup for just in case).
If the above doesn't help, please elaborate more clearly what actually is the issue but for now there is nothing much I can help you further with.

I've pushed a small update in v0.22.26 that performs manual checkpoints and eventually help with the accumulated data of the -wal file(s) but again as mentioned above the WAL files can grow if there are blocking transactions and it just how the current backup implementation works.

Well, good to know, but as you can see manual backups acts ok. 55MB or ~130MB if I add 2days logs retention.

Still 700MB for my tiny project ?! And from the printscreens above you can see the autobackup was on a constant size increase. Even though the db usage was fairly constant and Logs Settings is set for 2 days retention. Basically it unknowingly grew from 130MB to 700MB in ~3months (and then it crashed).
Not a DB guru, don't know how WALS work, but having 12 GB WAL for a ~10MB of data (if u exclude the few thumbnails from backup file) seems unreasonable.
But in my case, something happened and the whole pocketbase instance crashed and was 100% all my 6 vCPUs.
I restarted server, service etc.. the only way it worked was to install a fresh pb instance and use the backups.
So obviously the issue was somewhere lying in the database itself. Something was throttling process even after several restarts.
I will update the version. Again, my attempt was to find out what happened, so it doesn't happen again.

Please update to the latest version and test again.

After updating version it seems the backup is no longer increasing "randomly" in size


Code refactor & more proper null safety update

General refactor of android part, small refactor of ios part
updated logic for some methods and fixed AndroidStudio warnings
replaced JSONObject with HashMap(supported by MethodChannels) in androidInAppPurchasePlugin.java
deprecated originalJsonAndroid and dataAndroid as it is always the same object as transactionReceipt
refactored Dart part

@hyochan Could you please test if there are no type errors with subscriptions and consumables IAPs for android and IOS? As I use just non-consumables and it works fine with them?

@hyochan Could you please test if there are no type errors with subscriptions and consumables IAPs for android and IOS? As I use just non-consumables and it works fine with them?

Hm. Looks like we need others to test this out because I don't have any related example currently 😞
All we have is an example project in current repo.


Update awssdk:core, awssdk:sts to 2.15.33

Updates

software.amazon.awssdk:core
software.amazon.awssdk:sts

from 2.15.29 to 2.15.33.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #125.


Set Up Kanban board

We prepare a new Kanban board with a GitHub project. Our project link pokedex board. There are two members on our team: me  and Paul Sáenz Sucre.

[x] Create an empty repository for the group project.
[x] Follow the steps described in curriculum-tools-copy-projects.
[x] Open the GitHub project (Kanban board) in our team repo.
[x] Make sure that in the card titles you can see: Student A, Student B, or Student C.
[x] Make sure that each card starts with [Xpt] - that number indicates the number of points that shows how complex the task is. 1 point = 1 hour of work.
[x] As our group includes two people - remove all cards with Student C in the title.
[X] Decide me as Student B and Paul Saenz Sucre as Student A.
[X] Each of the team members should assign themselves to the correct cards.

Hi Team, 👋🏻👋🏻
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉🚀🔥🎉🎉

Highlights ✨✨

No Linters errors ✅
Great working on the kanban board and assigning the tasks to the cards🔥🚀🎉
Descriptive PR ✅🔥🔥

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Added Discord Button

2.

3.
Other minor changes
applied changes can be viewed at
https://testsiteecell.netlify.app/

@Sam-Ny  sir please review the changes


Telescope Options

Telescope Options
https://github.com/ibhagwan/fzf-lua

Could you elaborate, please?


Add a menu

Pretty self-explanatory. Add a nice drop-down menu.

I really should get around to this...

But for now, it's fine without.


Fixed emotion default value size to TEXT

1. Why is this change necessary?
The current column has a limitation to 256 Characters. A html example is currently not possible with this size.
2. What does this change do, exactly?
The migration makes the default value field of elements the same size like the value (s_emotion_element_value.value)
3. Describe each step to reproduce the issue or behaviour.
Create a emotion world field with a longer default value
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-20228
Please use this issue to track the state of your pull request.

Hi @shyim,
thanks for the pull request.
The changes are merged and will be available with version 5.3.5.


How to setup SSDB for HA/failover?

It seems SSDB can do replication in a master/slave setup (like Redis). However, I can't find any docs on this. For instance, does SSDB support Sentinel to check for Master failure and do Slave -> Master promotion?
In general I'm looking to implement this setup (which contains Sentinel + HaProxy). Would that work for SSDB?
If not, how do companies using SSDB in production handle this?

@ideawu clustering is very important for all types of databases
i wish you make it soon

HA doesn't require clustering, per se.  You just need to assign the master and slave and reassign as needed dynamically.

@ideawu Is ssdb-cluster still under development? Is there anywhere we can find the documentation or design roadmap


Exclude bastion machines from status phase check since they are always in Provisioned state

Fix MachineUnhealthy by excluding bastion host which are always stuck in Provisioned State

and MachineDeploymentReplicasMismatch

Checklist

[x] Update CHANGELOG.md
[ ] Add Unit tests
[ ] Follow Alert structure
[ ] Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
[ ] Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

lgtm, but could you add an unit test for this?
https://github.com/giantswarm/prometheus-rules/blob/master/test/tests/providers/capz/capi.rules.test.yml


Detect Invalid Helm Release Names Before Deployment

Is your feature request related to a problem? Please describe.
There is an inconsistency between what Zarf allows in Helm chart releaseName and what the Kubernetes API server accepts when creating resources. Specifically, Zarf allows release names that include periods (e.g., ollama-0.47.0), which conform to RFC 1123 Label Names. However, these names cause errors when Kubernetes attempts to create certain resources, despite being theoretically valid according to the naming conventions.
Describe the expected behavior

Given a Zarf configuration file (zarf.yaml) that includes a Helm chart with a release name containing periods
When running zarf lint, zarf package create, and zarf package deploy
Then Zarf should either:

Detect and warn about potential issues with resource names during lint and package creation, or
Handle the conversion of release names to ensure compatibility with all Kubernetes resources during deployment

Steps to reproduce

Create a zarf.yaml file with the following content:

kind: ZarfPackageConfig
metadata:
  name: ollama-api
  description: "A Zarf Package for deploying Ollama on Kubernetes."

components:
  - name: ollama-helm
    description: "Deploys Ollama API service"
    charts:
      - name: ollama
        url: https://otwld.github.io/ollama-helm
        releaseName: "ollama-0.47.0" # This causes issues with some Kubernetes resources
        version: 0.47.0
        namespace: ollama

Run zarf lint

Lint Output
┌[17:00:03]─────>
│ github.com/jamestexas/ollama-demo
└> zarf dev lint .

 NOTE  Saving log file to
       /var/folders/qh/9h3zdnss3sq

Run zarf package create . --confirm

Create Output
┌[17:00:12]─────>
│ github.com/jamestexas/ollama-demo
└> zarf package create . --confirm

 NOTE  Saving log file to
       /var/folders/qh/9h3zdnss3sq7c0688kzzw4l40000gn/T/zarf-2024-07-26-18-02-03-3751241269.log

 NOTE  Using build directory .

  📦 PACKAGE DEFINITION

kind: ZarfPackageConfig

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
metadata:  information about this package

  name: ollama-api
  description: A Zarf Package for deploying Ollama on Kubernetes.
  architecture: arm64

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
components:  components selected for this operation

- name: ollama-helm
  description: Deploys Ollama API service
  charts:
  - name: ollama
    version: 0.47.0
    url: https://otwld.github.io/ollama-helm
    namespace: ollama
    releaseName: ollama-0.47.0

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✔  Create Zarf package confirmed

  📦 OLLAMA-HELM COMPONENT

  ✔  Processing helm chart ollama:0.47.0 from repo https://otwld.github.io/ollama-helm
  ✔  Creating SBOMs for 0 images and 0 components with files.
  ✔  Package saved to "zarf-package-ollama-api-arm64.tar.zst"

Run zarf package deploy

Package Deploy Output
Deploys Ollama API service
? Deploy the ollama-helm component? Yes
  ✔  Waiting for cluster connection
  ✔  Gathering additional cluster information (if available)

  📦 OLLAMA-HELM COMPONENT

  ✔  Loading the Zarf State from the Kubernetes cluster
  ⠙  warning: Upgrade "ollama-0.47.0" failed: failed to create resource: Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')
 WARNING  Attempt (1/3) failed with: failed to create resource: Service "ollama-0.47.0" is invalid:
          metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case
          alphanumeric characters or '-', start with an alphabetic character, and end with an
          alphanumeric character (e.g. 'my-name', or 'abc-123', regex used for validation is
          '[a-z]([-a-z0-9]*[a-z0-9])?')

 WARNING  Retrying in 5s
  ⠹  warning: Upgrade "ollama-0.47.0" failed: failed to create resource: Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end   ⠸  warning: Upgrade "ollama-0.47.0" failed: failed to create resource: Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end   ⠼  warning: Upgrade "ollama-0.47.0" failed: failed to create resource: Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end   ⠴  warning: Upgrade "ollama-0.47.0" failed: failed to create resource: Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?') (1s)^C

Actual behavior
Zarf successfully lints the configuration and creates the package without any warnings. However, during deployment, Kubernetes fails to create certain resources (like Services) due to the period in the release name, despite this name conforming to RFC 1123 Label Names.
Expected behavior
Zarf should either:

Warn users during the lint and package creation processes that certain release names, while valid according to RFC 1123, may cause issues with some Kubernetes resources, or
Automatically adjust release names during deployment to ensure compatibility with all Kubernetes resources, while maintaining uniqueness and traceability to the original release name.

Additional context
This issue highlights a discrepancy between the Kubernetes naming conventions documentation and the actual behavior of the Kubernetes API server for certain resources. While the release name "ollama-0.47.0" conforms to RFC 1123 Label Names, it causes issues with resources that may have more stringent naming requirements.
Addressing this inconsistency in Zarf would greatly improve the user experience by preventing unexpected deployment failures and aligning Zarf's behavior more closely with the actual constraints of Kubernetes resource creation.
Environment

Zarf version: v0.36.1
Operating System: MacOS

└> sw_vers
ProductName:		macOS
ProductVersion:		14.5
BuildVersion:		23F79

Kubernetes version:

└> zarf tools kubectl version
Client Version: v1.30.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.6+k3s2

Describe alternatives you've considered

User-side workaround: Users could manually adjust their release names to avoid periods and other potentially problematic characters. However, this puts the burden on the user and doesn't address the underlying inconsistency.

Helm chart modification: Zarf could potentially modify the Helm charts to use a sanitized release name internally, while still allowing users to specify their preferred release name. This would require careful handling to ensure that all references to the release name within the chart are updated consistently.

Stricter validation: Zarf could implement stricter validation rules that align with the most restrictive Kubernetes resource naming requirements. While this would prevent deployment failures, it might be overly restrictive for some use cases.

Additional context

This issue is particularly relevant for users who are migrating existing Helm deployments to Zarf, as they may be using release names that have worked directly with Helm but cause issues when deployed through Zarf.
The discrepancy between the Kubernetes documentation and actual API server behavior regarding resource names can be confusing for users and may lead to inconsistent practices across different tools and platforms.

I did some further investigation and found that the issue is due to the DNS-1035 label standards, which are a requirement for naming in Kubernetes and consequently enforced by Helm. When attempting to install the Helm chart with a name containing dots, I encountered the following error:
┌[08:57:41]─────>
│ github.com/jamestexas/ollama-helm
└> helm install ollama-0.47.0 ollama-0.47.0.tgz --namespace ollama --create-namespace

W0729 09:57:44.914889   16262 warnings.go:70] metadata.name: this is used in Pod names and hostnames, which can result in surprising behavior; a DNS label is recommended: [must not contain dots]
Error: INSTALLATION FAILED: 1 error occurred:
	* Service "ollama-0.47.0" is invalid: metadata.name: Invalid value: "ollama-0.47.0": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')


this plugin doesn't show the empty

I've followed the tutorial.but
I can't find where the "empty" is displayed.
help me,please

Hello!
Did you provide a removable: true option in the JS initialization? Or a data-removable="true" attribute on the select?


iOS build failure using from command line

Describe the bug
Attempting to build the latest version of bgfx for iOS from the command line fails with a compilation error
To Reproduce
Open a terminal
create a new directory and enter it
mkdir bgfxbuild
cd bgfxbuild
pull the latest git source
'git clone https://github.com/bkaradzic/bx.git 'git clone https://github.com/bkaradzic/bimg.git
'git clone https://github.com/bkaradzic/bgfx.git`
Move into the bgfx folder
'cd bgfx`
Run Genie
../bx/tools/bin/darwin/genie --gcc=ios-arm64 gmake
Run Make
make -R -C .build/projects/gmake-ios-arm64 config=release
Output
==== Building bx (release) ====
Creating ../../ios-arm64/obj/Release/bx
Creating ../../ios-arm64/obj/Release/bx/bx/src
Creating ../../ios-arm64/bin
allocator.cpp
bounds.cpp
bx.cpp
commandline.cpp
crtnone.cpp
debug.cpp
dtoa.cpp
easing.cpp
file.cpp
filepath.cpp
hash.cpp
math.cpp
mutex.cpp
os.cpp
process.cpp
semaphore.cpp
settings.cpp
sort.cpp
string.cpp
thread.cpp
timer.cpp
url.cpp
Archiving bx
==== Building bgfx (release) ====
Creating ../../ios-arm64/obj/Release/bgfx
Creating ../../ios-arm64/obj/Release/bgfx/src
bgfx.cpp
../../../src/bgfx.cpp:2655:87: warning: converting the result of '?:' with integer constants to a boolean always evaluates to 'true' [-Wtautological-constant-compare]
 2655 |                 { gl::rendererCreate,     gl::rendererDestroy,     BGFX_RENDERER_OPENGL_NAME,     !!BGFX_CONFIG_RENDERER_OPENGLES   }, // OpenGLES
      |                                                                                ^
../../../src/config.h:99:8: note: expanded from macro 'BGFX_CONFIG_RENDERER_OPENGLES'
   99 |                                         ? BGFX_CONFIG_RENDERER_OPENGLES_MIN_VERSION : 0)
      |                                           ^
../../../src/config.h:88:54: note: expanded from macro 'BGFX_CONFIG_RENDERER_OPENGLES_MIN_VERSION'
   88 | #               define BGFX_CONFIG_RENDERER_OPENGLES_MIN_VERSION (0 \
      |                                                                   ^
1 warning generated.
debug_renderdoc.cpp
dxgi.cpp
glcontext_egl.cpp
glcontext_html5.cpp
glcontext_wgl.cpp
nvapi.cpp
renderer_agc.cpp
renderer_d3d11.cpp
renderer_d3d12.cpp
renderer_gl.cpp
renderer_gnm.cpp
renderer_mtl.mm
../../../src/renderer_mtl.mm:15:11: fatal error: 'Cocoa/Cocoa.h' file not found
   15 | #       include <Cocoa/Cocoa.h>
      |                 ^~~~~~~~~~~~~~~
1 error generated.
make[1]: *** [../../ios-arm64/obj/Release/bgfx/src/renderer_mtl.o] Error 1
make: *** [bgfx] Error 2

Expected behavior
It should build without errors.
It looks like the code around the #include is as follows:
#if BX_PLATFORM_OSX
#	include <Cocoa/Cocoa.h>
#endif

BX_PLATFORM_OSX probably shouldn't be set for iOS?
Also commenting out #include <Cocoa/Cocoa.h> leads to an error further on:
==== Building bx (release) ====
==== Building bgfx (release) ====
renderer_mtl.mm
../../../src/renderer_mtl.mm:402:35: fatal error: unknown type name 'io_registry_entry_t'
  402 |         static uint32_t getEntryProperty(io_registry_entry_t _entry, CFStringRef _propertyName)
      |                                          ^
1 error generated.
make[1]: *** [../../ios-arm64/obj/Release/bgfx/src/renderer_mtl.o] Error 1
make: *** [bgfx] Error 2

Additional context
I am running OSX Sonoma 14.7.2 and have tried XCode 15.2 and XCode 16.2

The compiler flag is not set properly from bgfx. I had to manually force it in the bx/include/bxplatform.h file in bx library.
I placed this near the end of the file before "#endif // defined(__cplusplus)"
#undef BX_PLATFORM_OSX
#undef BX_PLATFORM_IOS
#define BX_PLATFORM_OSX 0
#define BX_PLATFORM_IOS 1

This is a temporary fix until someone fixes the ios-arm64 build in the bgfx makefile to properly set the compiler flag. Or fix bx library to recognize that we are compiling for iOS and not MacOS! Im not an expert of the library, hopefully someone knows where to put that fix. I'm just trying to make a program for iOS with BGFX.

It looks like there are issues with the define checks for ios and osx in bx/include/bx/platform.h as suggested by @Orman
My potential fix is to add in this block of code above the large if-else chain (after #endif // BX_CPU_PPC)
// Detect if we are on apple and if we are ios or osx
// https://stackoverflow.com/a/42040445
#if defined(__APPLE__) && defined(__MACH__)
#include <TargetConditionals.h>
	#if TARGET_IPHONE_SIMULATOR == 1
		#define APPLE_PLATFORM_IOS 1 // Apple iOS
	#elif TARGET_OS_IPHONE == 1
		#define APPLE_PLATFORM_IOS 1 // Apple iOS
	#elif TARGET_OS_MAC == 1
		#define APPLE_PLATFORM_OSX 1 // Apple OSX
#endif
#endif

And then change the IOS and OSX detection sections below to:
#elif  defined(APPLE_PLATFORM_IOS)
#	undef  BX_PLATFORM_IOS
#	define BX_PLATFORM_IOS 1

and
#elif defined(APPLE_PLATFORM_OSX)
#	undef  BX_PLATFORM_OSX
#	define BX_PLATFORM_OSX __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__

I have tested this building with:
make ios-arm64 and make osx-arm64 and both seem to build the libraries without fault.
Additional:
@Orman As for getting the examples to run on iOS - I've never tried, but wouldn't imagine it's very easy.

:eyes: at it...

Get this https://github.com/bkaradzic/bx/commit/7dc7dfc380e250d4157b6968268fe7e1f5aa3c43 and try it again.

but why have you removed the ability to build android-arm?

Makefile is there just to simplify build steps for those that are starting. It's basically invoking GENie + makefiles GENie generated. Once you're familiar and know what you need to use, you could do that inside your own build system.


Discussion of ModelState in error handling doc is out of place

This section: https://docs.asp.net/en/latest/fundamentals/error-handling.html#handling-model-state-errors doesn't have much in common with the topics discussed elsewhere in the document.
I wouldn't come to this doc to try and find information about validation - which is a topic that all MVC actions taking user-input need to deal with.

It's also covered in detail here: https://docs.asp.net/en/latest/mvc/models/validation.html. It's worth a mention, IMO, in Error Handling, but can pretty much link to the validation article for details.

@rachelappel  can you make sure this gets fixed for RTM as part of your model binding work?

38bf6953d7510e83f39ea46973cb2cb34bc5b696


Autarky and Disiregime not having election options

You can't encourage your population to care about these options

Yeah this needs to be added but it might need to be done so the trade policy and economic policy election events change after fascism is invented since it makes no sense for it to exist before. But I was also thinking maybe we could go back to vanilla election events since they look better and give more information or have an option the game to play with one or the other

Yeah this needs to be added but it might need to be done so the trade policy and economic policy election events change after fascism is invented since it makes no sense for it to exist before. But I was also thinking maybe we could go back to vanilla election events since they look better and give more information or have an option the game to play with one or the other


Import Features from other German Corona apps

Hello,
is it possible to import the features of the "CovPass Check" and the "CovPass" Apps?
In Detail:

From the "CovPass Check" app the ability to prove the validity of COVID-certificates and,
from "CovPass" app to save the imported COVID-certificate as an pdf-file.

These features would make the app more useful, also the other two obsolete. The main improvement would be Nr. 1, because many people doesn't know that the CovPass Check app exists.

Hi @bugleugner
Thanks for your suggestions!
Regarding number one

From the "CovPass Check" app the ability to prove the validity of COVID-certificates

we already have this issue: #633
And concerning number two

from "CovPass" app to save the imported COVID-certificate as an pdf-file.

This is actually already possible, you can find more information here: https://www.coronawarn.app/en/faq/#eu_dcc_export
I hope this helps! Have a nice evening and a good night!

So, basically you are asking for the additional feature to do this check with the camera/scanner without importing a certificate, right?

yes, that's what i meant


Flutter Layout spends 50% of its time in "File backed page in"

This tracker is for issues related to:

Dart VM

I've been investigating the performance of the Layout operation in Flutter and I was surprised to find that a large amount of time spent in layout isn't actually occupied in CPU.  I'm seeing that 50% of the time is spent in VM page faults.
For this example I'm just using the default Flutter project that is just simply a button.  I'm running on an iPhone SE 2 (3 GB ram), with the Profile configuration.  I've added signposts around the Layout event here.
What I'm seeing is that during the 25ms it takes to execute Layout, the thread is only active 16ms:

The total time spent in system calls for this time range is 128 µs, so it isn't because of system calls that the thread is not running.
If you look at the virtual memory usage though, a large percentage of time is spent in page faults (11.56ms):

Looking at the timeline, we see that the time the thread is inactive is correlated to the "File backed page in":

I don't know what the solution to this problem is, but given that this is the simplest Flutter project you can make on a device with a reasonable amount of RAM, we shouldn't be spending 50% of our time with page faults.
cc @a-siva @mraleph

I wonder if this is related to locality, where loading the renderobject tree is taking us all over the place in memory.  It might not be so much a problem with the Dart VM but a result of our data structure.

It's really hard to get good data locality in UI applications...

Would "File backed page in" actually be used for our datastructure though, or would iOS only use that for read-only memory like machine code?

After looking through the profiles a bit I'm pretty sure this related to paging in the compiled code.  I'm not sure if there is a way we can make this more efficient?  Maybe using differ optimization flags to reduce code size, making sure debugging symbols aren't blowing up code size, maybe prefetch certain symbols we know will be required at startup for every flutter project?  I don't have any experience making these sort of optimizations.  Maybe the VM team will have a better idea if there is something actionable here.

@mraleph had talked at some point about profiler guided layout for code.

For starters we can try something simpler than PG based code layout - try to arrange code based on unweighted call-graph.

I don't know what the solution to this problem is, but given that this is the simplest Flutter project you can make on a device with a reasonable amount of RAM, we shouldn't be spending 50% of our time with page faults.

I would expect that page-faults reduce/disappear after initial startup? Is this not the case? Can you look at how number evolve in several subsequent layouts?

Slava in a different channel suspects it is not the presence of debugger symbols which is causing page faults since they are supposed to be placed in a different part of the binary, not inline with the code.  As an experiment I was asked to try turning off the profiler which I did with the following diff:
--- a/runtime/dart_vm.cc
+++ b/runtime/dart_vm.cc
@@ -209,9 +209,9 @@ static std::vector<const char*> ProfilingFlags(bool enable_profiling) {
 // Disable Dart's built in profiler when building a debug build. This
 // works around a race condition that would sometimes stop a crash's
 // stack trace from being printed on Android.
-#ifndef NDEBUG
+//#ifndef NDEBUG
   enable_profiling = false;
-#endif
+//#endif

It looks like that eliminated the VM page faults too:

I'm not sure what the action items are now.  For sure benchmarks should be making sure they don't have the dart profiler turned on.  I don't know if there is any other work we should be doing.  If we could avoid the overhead until someone actually attaches to the profiler that would be nice too.

Thanks for running the experiments @gaaclarke!
It would be great to understand why exactly profiler is triggering this, but I think realistically this might be rather hard to figure out given how sealed and non-transparent iOS is so I will just close this one as resolved.


Stealth Solar plant icon

The icon is briefly displayed at zoom level between 11 and 10.97 when you play with the mouse wheel.

Yeah, this is kind of a bug in Mapbox GL JS and how it interacts with my logic for determining how to display plant icons based on power output. There's no easy fix for it at the moment.


Updated website for Beam release 2.32.0

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@angoenka Should we merge this now or wait?

I think this is merged after the release is voted for.


feat(server): expose server event lifecycle in public API

Return the EventEmitter instance so that it's possible to into various lifecycle events. Add a browsers_ready event so that it's possible to know when the karma server has finished starting up.
Enables and partially resolves #1037
I am very interested in resolving #1037 (it's breaking our grunt and gulp builds), so if this is not quite the way you want it to be done, let me know and I'll do it differently! :)

I signed it!

So in general I like the approach, though I would prefer not returning the globalEmitter from the start function. In my mind the code (not only yours) needs to be refactored in a way that the interacting api would look like
var karma = require('karma')

karma.on('browsers_ready', function (event) {
  // ...
})

karma.start()

but I'm not a 100% sure yet what the best way is to introduce these changes into the code base.

Thank you for taking a look at this :)
It seems quite a major undertaking to refactor everything but I agree it's the best idea longterm. I could take a stab if it's not in the near future for any of the regular maintainers.
One option to have this quickly and then still support easy migration/backwards compatibility later is to return a subset of the emitter, sort of an interface object. So something like this:
{on: globalEmitter.on.bind(globalEmitter), ...}

Then, in the future, it could just start returning karma itself. I think there's a general need to expand the public API a little bit to enable more diverse workflows.

So it turned out, it wasn't that hard to do :) see #1485 and feel free to give it a test drive

Oh, that's actually impressively quick! It seems like it will do the trick quite well. I think we're good to close this PR and the issue I mentioned if #1485 goes through. I'll play around with your branch tomorrow.
:+1:

Great


js.Dynamic.global not working with Node.JS

In scalajs-react tests, there's a file component-es3.js that declares const ES3_P = ....
In Phantom.JS, both of the following work, where as in Node.JS, this works:
scalajs.js.eval("ES3_P")

but this doesn't:
scalajs.js.Dynamic.global.ES3_P

Versions
> node -v
v7.7.2
> npm -v
4.4.1
> phantomjs -v
2.1.1

Looks like a duplicate of #2800. See also the Stack Overflow question mentioned in that post for a workaround.

Put another way, the fact that it works in PhantomJS is a bug of the latter (or of its JS engine).

Ah I didn't realise that was the same issue. Ok cool, happy to close this if you are.


ci: retry flaky test when running in Windows with Webpack

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
I was afraid this would be the case but it makes sense that this flakiness is present for both scroll to top tests, should have included it in the previous PR. This one likely got triggered less as the previous test failed more often, preventing this test from being reached?

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[ ] I have updated the documentation accordingly.

@BobbieGoede, WDYT about adding this one too?
https://github.com/nuxt/nuxt/actions/runs/7733731134/job/21086407948?pr=25548#step:11:70

@DamianGlowala
Honestly, we might as well add retries to all known flaky tests if you ask me, it may not be pretty but we're rerunning the jobs anyway. Going to have to change the retry conditional for the test in this PR as well based on this: https://github.com/nuxt/nuxt/actions/runs/7732935327/job/21084024589?pr=25514
Maybe we should also open issues for tests showing flaky behaviour if we allow them to retry?

Yes, we should definitely aim to resolve flakiness rather than just 'allowing' it. Sometimes flaky tests identify genuine bugs.


Update OpenOCD on release-4.2 branch (IDFGH-4069)

Please consider cherry picking commit f857ab85c3c2bf509bf2e2fc6f59c73a0f2ca536 onto the release-4.2 branch.
I'm using that branch for my ESP32-S2 Kaluga devkit and the July version of OpenOCD has a few new config files that makes idf openocd work with that hardware.
Thanks!

Thanks for the reminder @zx64, will do.

Appears to have been fixed by 7d8d2b982e114904bce724d555ff11b7e436a68e, thanks!
(Worth pointing out that for some reason this issue didn't get notified and/or closed automatically by whatever process you have for internally triaging and managing issues etc.)

Thanks for the updates.


Error: You must supply options.input to rollup

I'm a little confused by the above error message. I don't see an "options.input" anywhere in the options to snowpack-plugin-rollup-bundle.
Here is my configuration:
    [
      "snowpack-plugin-rollup-bundle",
      {
        // equivalent to inputOptions.input from Rollup
        entrypoints: "index.js",

        extendConfig: (config) => {
          // https://rollupjs.org/guide/en/#outputoptions-object
          // config.outputOptions = { ... }

          // https://rollupjs.org/guide/en/#inputoptions-object
          // config.inputOptions = { ... }

          return config;
        },
      },
    ],

Maybe it means that config.inputOptions is required?

@canadaduane so I think I should make it a little more clear, but your entrypoint should be where you build with Snowpack build.
So if your out directory is set to build you should have an entrypoint of:
entrypoints: "build/index.js"
Let me know how that works for you!

I see! That makes sense, thank you.


api_key is always set to be in "query" on UI index.html

I believe it's around line 120 of the "index.html" custom-asset.

I believe there is a pull request that addresses this: #401

Resolved by #401


assign correct records and cache to child compilations

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
no

If relevant, link to documentation update:
N/A

Summary
fixes #2777
creating a child compiler now assigns correct cache and records
compiler name is made relative

Does this PR introduce a breaking change?
yes
This is a breaking change because plugins or loader could rely on this incorrect behavior

Other information
When using child compilations plugins and loaders should use a unique compiler name or use a consistent order

When will this be merged? It looks like https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/389 will be fixed afterward. (I don't mean to rush anybody, I just want to know whether I should wait for this to happen soon)

It will be merged into the next major version.


Test TLS support with locally respected SSL wildcard cert made with mkcert

use this: https://github.com/FiloSottile/mkcert to avoid paying for a SSL cert for development but without fiddling with certificate authority store

done


Inlining KDoc samples

Description
Because Dokka doesn't support readonly code samples, we would like to introduce an internal Gradle task responsible for inlining function's body of samples. This task should detect each line in Kotlin main files ending with the sample tag block @sample <identifier>. Each line detected should be replaced by their corresponding function's body, located in the *Test module.
This task should work for Kotlin and Java code samples.
For example, if there is the line @sample kotools.types.number.div_KotlinSample in the documentation of the NonZeroInt.div(NonZeroInt) function, located in the kotools.types.number.NonZeroInt.kt file, and if the targeted function exists in the test module and is located in the samples.kotools.types.number.NonZeroInt.kt file, then the body of divKotlinSample should replace the @sample kotools.types.number.divKotlinSample tag.
// In commonMain/kotools/types/number/NonZeroInt.kt

/**
 * @sample kotools.types.number.div_KotlinSample
 */
operator fun NonZeroInt.div(NonZeroInt): Int

// In commonTest/samples/kotools/types/number/NonZeroInt.kt

fun div_KotlinSample() {
    val x: NonZeroInt = 8.toNonZeroInt()
        .getOrThrow()
    val y: NonZeroInt = 2.toNonZeroInt()
        .getOrThrow()
    val result: Int = x / y
    println(result) // 4
}

// Should result in

/**
 * ```kotlin
 * val x: NonZeroInt = 8.toNonZeroInt()
 *     .getOrThrow()
 * val y: NonZeroInt = 2.toNonZeroInt()
 *     .getOrThrow()
 * val result: Int = x / y
 * println(result) // 4
 * ```
 */
operator fun NonZeroInt.div(NonZeroInt): Int

Also, for ensuring the correctness of code samples, we should test their output through another test class. In this example, the test class could be named NonZeroIntSampleTest.
Checklist

[ ] Create the Gradle task and test it on a single file.
[ ] Make the Dokka tasks depending on this new task.
[ ] Update the task for working on multiple files from the commonMain source set.
[ ] Update the task for working on all *Main source sets.
[ ] Create issues for replacing hard-coded samples by sample tags in all files.

We should wait for the resolution of the issue #368 for using a newer version of Gradle.

Done in #610.


The order of PartialSchemas matters for Interfaces, Unions, and ConnectionTypes - is this intentional?

I noticed that when partial schemas are used to build a new schema, that the order of them matters.  This creates a number of issues, including the potential for a circular reference issue that used to happen and was fixed in #84.  I think it would be better if the schemas were all evaluated together at the same time.
For example, right now if SchemaB depends on an Interface in SchemaA, then SchemaA has to be listed first in the builder array.  From my understanding, the current implementation makes it impossible to have two schemas that each depend on a field from the other.
@d-exclaimation @NeedleInAJayStack I'm not sure if this an issue with SchemaBuilder or PartialSchema

As a side note, I'm really excited to refactor my existing 1500+ line schema and start using PartialSchemas!  I've already noticed a lot of improvement with the code completion in the smaller schemas while trying them out.

I'll take a look at this. I am assuming the problem is about using those types in a query, mutation, or subscription field(s) require them to be in the correct order.

@d-exclaimation Interesting.  It also is an issue if an interface is after a type that implements it.

@d-exclaimation Interesting. It also is an issue if an interface is after a type that implements it.
Got it. I was able to reproduce the issue. I noticed this is also might be a problem with just regular Schema, where intefaces need be declared before any types that uses it

Yeah, I am able to recreate too. Ideally no ordering should be required - I'll look at fixing this tonight. Thanks for reporting @cshadek

Yeah, I am able to recreate too. Ideally no ordering should be required - I'll look at fixing this tonight. Thanks for reporting @cshadek

Not sure exactly how to properly fix this, but one idea I had is to sort the component declared by like a priority, for example:
Scalars > Enums > Inputs > Interface > Type (Object) > Union > Query > Mutation > Subscription
I guess this would have solve the case where something like a Union is referenced by a Type (Object), Interfaces, or other Unions. However, so far this method seems to work

@d-exclaimation lol, that's exactly what I did! Great minds think alike!
@cshadek could you try this https://github.com/GraphQLSwift/Graphiti/pull/97 and validate that it fixes your Connection issue as well?

  Nice work!


[WIP] Added subscriptions

Done:
Added subscribe button to file and channel pages
Saves channels that have been subscribed to
Once you have subscribed to one or more channels, it presents 10 recent videos on the discover page under the "Subscription" section
Not Done:
I made the subscribe button on the file page work, but not on the channel page.
Ideally, the subscribe button would say unsubscribe after you click it (and you would be able to unsubscribe).
It does not save the state in local storage -- subscriptions go away after a refresh
There is nothing to prevent storing duplicate subscriptions
There appears to be some performance issues when generating the list of subscription videos to display on the discover page.
I would be more than happy to continue working on any of these problems, but I thought the code is to a point where I touched all key functionality, thus demonstrating my abilities.
Let me know if you have any questions or comments.

This needs further thought, I'm closing this pull request for now.


Rework error reporting

There are couple things which should be completed:

Do not utilise cmdliner for the error reporting when Fastpack fails, since it does a lot of smart undesired formatting.
Use the fmt library in order to make sure formatting is consistent and text is readable.

Links:

fmt
tutorial

Closing this one, as it is done


COMP: Add missing iostream include for CUDA classes

@SimonRit As discussed this seems to fix the dashboard issues, but then I get a redefinition error.

Thanks. Actually, replacing std::cout with itkGenericExceptionMacro would be preferable I think, see e.g., here. Do you mind modifying your PR?

Sure! Just did the change. After solving this issue I get:
error LNK2005: "public: virtual __cdecl itk::ExceptionObject::~ExceptionObject(void)" (??1ExceptionObject@itk@@UEAA@XZ) already defined in cuda_compile_1_generated_rtkCudaBackProjectionImageFilter.cu.obj
Let's see if dashboards reproduce it once it's merged.


No Audiofiles

Hello,
I'm trying to use this tool at the moment, but I have the problem that in the final P.808_acr.html audioclips aren't available when I run it in a Webbrowser. It starts in the Setup section with question number 2-6. The Training sections works, but in the Rating section they are also not available. In the rating_clips.csv, trapping_clips.csv, golden_clips.csv and the general.csv files I updated all links to my AmazonAWS directory. The developers console in the browser says that it searches for the files in my local project.
I checked everthing twice what what written in your Preperation of ACR test, but didn't saw the problem.
In the master.cfg I saw coincidentally the section about the definition of the URLs and Paths of the clips. There you write that I should use the azure storage and give the information for that.
Is this the problem? And if yes, what do I have to do / have to change, when I'm using AmazonAWS for all the files?
Thank you!

when you run the master script, you get 3 files. The HTML file is a template with variables for all the URLs you see missing. You need to follow the steps here: https://github.com/microsoft/P.808/blob/master/docs/running_test_mturk.md
upload the HTML file when creating new project in Mturk.com. After that click on the Publish Batch in the mturk and upload the csv file. The csv file contains all the links you see is missing in your local computer.
For testing rather you can use mturk developer sandbox or the HitApp server from https://github.com/microsoft/P.910

Thank you very much, that worked! So the lower part in the master.cfg where you write the information about the azure account is irrelevant and doesn't has to be filled?
At the moment I have the problem, that I don't really understand how the pattern for the randomization works.
I will have 24 conditions that have to be included in the experiment. The sequence can be random, but all conditions have to be in it. Now the point is, that every Condition exists in variants like Male voice 1 and 2 and Female voice 1 and 2. Those Variants also have the next variation, the they can be clean or have a kind of loss.
My file-name-structur is:
P501_C01_F1_S01
C is for the conditions 01-24, then the options M1,M2,F1,F2 and at least S01 for noloss and S02 for a kind of loss.
What has to be the pattern and configuration (conditions_keys, clip_packing_strategy and block_keys) that you get all 24 conditions but randomly selected out of the options M1,M2,F1,F2 and S01,S02?

Oh thank you! Now everything runs. I'm not sure at the moment how many conditions I will finally have at the end. What would you say is your recommended amount? The concept of the block design was for me unfortunately not clear enough. I just understood roughly the condition pattern.
For the finalisation I need to know another important thing. In the "P.808_acr.html" the trapping question gets checked in "tp_check". So if it's zero the question was answered right and -1 if not. Is that just a variable that I get in the results to check or is it reused in an other file of yours that already checks that and validate it?
I ask because I got the requirement that everyone gets checked at the end and gets a code (defined by us) if the trapping question was answered right or nothing if not. To implement that I need to understand the connection / variables. If it's just a variable in the result sheet, would you say it makes more sense to just check the number instead of a extra given code?
Sorry for all the questions, but this whole project is a lot harder for me than I thought.
Thank you and have a nice weekend!


Unify node description and dialog settings

Use the new node guidelines regarding naming and settings for the geospatial nodes.

@steffen-fissler will start with the nodes in the Open Datasets category and I will start with the Spatial IO category.

Related tickets:
https://github.com/spatial-data-lab/knime-geospatial-extension/issues/142


Incorrect table DDL generation in azure sql server

System information:

Operating system (distribution) and version : Windows 10
DBeaver version : <IP_ADDRESS>207240747
Additional extensions

Connection specification:

Database name and version :  Azure SQL
Driver name : Azure SQL Server
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
We created a table. There are many columns with  column type nvarchar(35).
When we checked the table definition, we can see that the generated DDL shows nvarchar(17).
If we check it in the information_schema it shows the proper value.
Steps to reproduce, if exist:
create table sandbox.test_table
(
address nvarchar(35)
);
--check
select table_name , COLUMN_NAME , CHARACTER_MAXIMUM_LENGTH  from INFORMATION_SCHEMA.COLUMNS
where TABLE_NAME = 'test_table'
;
shows the proper value (35)
Generate the DDL:
-- dwh_test.sandbox.test_table definition
-- Drop table
-- DROP TABLE dwh_test.sandbox.test_table;
CREATE TABLE dwh_test.sandbox.test_table (
address nvarchar(17) COLLATE Hungarian_Technical_100_CI_AS_SC_UTF8 NULL
);
Include any warning/errors/backtraces from the logs

thanks for the report

Closed as duplicate of #16996


Issues when attempting to compile API Client

<!--

Thanks for contributing to CARLA!

If you are reporting an issue, please use the following outline:

CARLA version: 1.2.37
Platform/OS: Windows
Problem you have experienced:

C:\Carla\carla-dev>make PythonAPI
-[BuildUE4Plugins]: [Batch params]: --build --all
HEAD is now at 260273d Correct descriptor
-[BuildUE4Plugins]: STREETMAP has been successfully installed in "C:\Carla\carla-dev\Unreal\CarlaUE4\Plugins\"
-[Setup]: [Batch params]: --boost-toolset msvc-14.2 --generator "" --all
-[Setup]: Asynchronous jobs:  16
-[Setup]: Boost toolset:      msvc-14.2
-[Setup]: Generator:          "Visual Studio 16 2019"
-[Setup]: Install directory:  "C:\Carla\carla-dev\Build\"
-[Setup]: Installing zlib...
    -[install_zlib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\"
    -[install_zlib]: A zlib installation already exists.
    -[install_zlib]: Delete "C:\Carla\carla-dev\Build\zlib-install\" if you want to force a rebuild.
    -[install_zlib]: Exiting...
The system cannot find the path specified.
        0 file(s) copied.
-[Setup]: Installing libpng...
    -[install_libpng]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --zlib-install-dir "C:\Carla\carla-dev\Build\zlib-install\"
    -[install_libpng]: A libpng installation already exists.
    -[install_libpng]: Delete "C:\Carla\carla-dev\Build\libpng-1.2.37-install\" if you want to force a rebuild.
    -[install_libpng]: Exiting...
-[Setup]: Installing rpclib...
    -[install_rpclib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_rpclib]: A rpclib installation already exists.
    -[install_rpclib]: Delete "C:\Carla\carla-dev\Build\rpclib-install\" if you want to force a rebuild.
    -[install_rpclib]: Exiting...
-[Setup]: Installing Google Test...
    -[install_gtest]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_gtest]: Not cloning Google Test because already exists a folder called "gtest-src".
    -[install_gtest]: Generating build...
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19045.
CMake Deprecation Warning at googlemock/CMakeLists.txt:42 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at googletest/CMakeLists.txt:49 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Warning (dev) at googletest/cmake/internal_utils.cmake:239 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  googletest/CMakeLists.txt:84 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done (0.3s)
-- Generating done (0.4s)
-- Build files have been written to: C:/Carla/carla-dev/Build/gtest-src/build
    -[install_gtest]: Building...
Microsoft (R) Build Engine version 16.11.2+f32259642 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  1>Checking Build System
  gmock.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\Release\gmock.lib
  gmock_main.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\Release\gmock_main.lib
  gtest.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\gtest\Release\gtest.lib
  gtest_main.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\gtest\Release\gtest_main.lib
  Building Custom Rule C:/Carla/carla-dev/Build/gtest-src/CMakeLists.txt
  1>
  -- Install configuration: "Release"
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-cardinalities.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-actions.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-function-mockers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-function-mockers.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-matchers.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-nice-strict.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-nice-strict.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-more-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-more-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-spec-builders.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-generated-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-generated-actions.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/README.md
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-generated-internal-utils.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-generated-internal-utils.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-internal-utils.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gmock.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gmock_main.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gmock.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gmock_main.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestTargets.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestTargets-release.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestConfigVersion.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestConfig.cmake
  -- Up-to-date: C:/Carla/carla-dev/Build/gtest-install/include
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-death-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-message.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-param-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-param-test.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-printers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-spi.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-test-part.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-typed-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest_pred_impl.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest_prod.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest-printers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/README.md
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-death-test-internal.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-filepath.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-internal.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-linked_ptr.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util-generated.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util-generated.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-port-arch.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-string.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-tuple.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-tuple.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-type-util.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-type-util.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gtest.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gtest_main.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gtest.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gtest_main.pc
neq was unexpected at this time.

    -[install_gtest]: Google Test has been successfully installed in "C:\Carla\carla-dev\Build\gtest-install\"
    -[install_gtest]: Exiting...
-[Setup]: Installing "Recast & Detour"...
    -[install_recast]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_recast]: A "Recast & Detour" installation already exists.
    -[install_recast]: Delete "C:\Carla\carla-dev\Build\recast-install\" if you want to force a rebuild.
    -[install_recast]: Exiting...
-[Setup]: Installing Boost...
    -[install_boost]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --toolset msvc-14.2 --version 1.80.0 -j 16
The system cannot find the batch label specified - arg-parse

-[Setup]:
   Ok, and error ocurred, don't panic
   We have different platforms where you can find some help :)

   - Make sure you have read the documentation:
       http://carla.readthedocs.io/en/latest/how_to_build_on_windows/

   - If the problem persists, you can ask on our Github's "Building on Windows" issue:
       https://github.com/carla-simulator/carla/issues/21

   - Or just use our Discord channel
       We'll be glad to help you there :)
       https://discord.gg/42KJdRj
make: *** [setup] Error 1

C:\Carla\carla-dev>make PythonAPI
-[BuildUE4Plugins]: [Batch params]: --build --all
HEAD is now at 260273d Correct descriptor
-[BuildUE4Plugins]: STREETMAP has been successfully installed in "C:\Carla\carla-dev\Unreal\CarlaUE4\Plugins\"
-[Setup]: [Batch params]: --boost-toolset msvc-14.2 --generator "" --all
-[Setup]: Asynchronous jobs:  16
-[Setup]: Boost toolset:      msvc-14.2
-[Setup]: Generator:          "Visual Studio 16 2019"
-[Setup]: Install directory:  "C:\Carla\carla-dev\Build\"
-[Setup]: Installing zlib...
    -[install_zlib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\"
    -[install_zlib]: A zlib installation already exists.
    -[install_zlib]: Delete "C:\Carla\carla-dev\Build\zlib-install\" if you want to force a rebuild.
    -[install_zlib]: Exiting...
The system cannot find the path specified.
        0 file(s) copied.
-[Setup]: Installing libpng...
    -[install_libpng]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --zlib-install-dir "C:\Carla\carla-dev\Build\zlib-install\"
    -[install_libpng]: A libpng installation already exists.
    -[install_libpng]: Delete "C:\Carla\carla-dev\Build\libpng-1.2.37-install\" if you want to force a rebuild.
    -[install_libpng]: Exiting...
-[Setup]: Installing rpclib...
    -[install_rpclib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_rpclib]: A rpclib installation already exists.
    -[install_rpclib]: Delete "C:\Carla\carla-dev\Build\rpclib-install\" if you want to force a rebuild.
    -[install_rpclib]: Exiting...
-[Setup]: Installing Google Test...
    -[install_gtest]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_gtest]: Not cloning Google Test because already exists a folder called "gtest-src".
    -[install_gtest]: Generating build...
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19045.
CMake Deprecation Warning at googlemock/CMakeLists.txt:42 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at googletest/CMakeLists.txt:49 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Warning (dev) at googletest/cmake/internal_utils.cmake:239 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  googletest/CMakeLists.txt:84 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done (0.3s)
-- Generating done (0.2s)
-- Build files have been written to: C:/Carla/carla-dev/Build/gtest-src/build
    -[install_gtest]: Building...
Microsoft (R) Build Engine version 16.11.2+f32259642 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  gmock.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\Release\gmock.lib
  gmock_main.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\Release\gmock_main.lib
  gtest.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\gtest\Release\gtest.lib
  gtest_main.vcxproj -> C:\Carla\carla-dev\Build\gtest-src\build\googlemock\gtest\Release\gtest_main.lib
  1>
  -- Install configuration: "Release"
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-cardinalities.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-actions.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-function-mockers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-function-mockers.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-matchers.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-nice-strict.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-generated-nice-strict.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-more-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-more-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock-spec-builders.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/gmock.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-generated-actions.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-generated-actions.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-matchers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/gmock-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/custom/README.md
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-generated-internal-utils.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-generated-internal-utils.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-internal-utils.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gmock/internal/gmock-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gmock.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gmock_main.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gmock.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gmock_main.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestTargets.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestTargets-release.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestConfigVersion.cmake
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/cmake/GTest/GTestConfig.cmake
  -- Up-to-date: C:/Carla/carla-dev/Build/gtest-install/include
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-death-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-message.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-param-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-param-test.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-printers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-spi.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-test-part.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest-typed-test.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest_pred_impl.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/gtest_prod.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest-printers.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/gtest.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/custom/README.md
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-death-test-internal.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-filepath.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-internal.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-linked_ptr.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util-generated.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util-generated.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-param-util.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-port-arch.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-port.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-string.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-tuple.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-tuple.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-type-util.h
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/include/gtest/internal/gtest-type-util.h.pump
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gtest.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/gtest_main.lib
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gtest.pc
  -- Installing: C:/Carla/carla-dev/Build/gtest-install/lib/pkgconfig/gtest_main.pc
neq was unexpected at this time.

    -[install_gtest]: Google Test has been successfully installed in "C:\Carla\carla-dev\Build\gtest-install\"
    -[install_gtest]: Exiting...
-[Setup]: Installing "Recast & Detour"...
    -[install_recast]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_recast]: A "Recast & Detour" installation already exists.
    -[install_recast]: Delete "C:\Carla\carla-dev\Build\recast-install\" if you want to force a rebuild.
    -[install_recast]: Exiting...
-[Setup]: Installing Boost...
    -[install_boost]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --toolset msvc-14.2 --version 1.80.0 -j 16
The system cannot find the batch label specified - arg-parse

-[Setup]:
   Ok, and error ocurred, don't panic
   We have different platforms where you can find some help :)

   - Make sure you have read the documentation:
       http://carla.readthedocs.io/en/latest/how_to_build_on_windows/

   - If the problem persists, you can ask on our Github's "Building on Windows" issue:
       https://github.com/carla-simulator/carla/issues/21

   - Or just use our Discord channel
       We'll be glad to help you there :)
       https://discord.gg/42KJdRj
make: *** [setup] Error 1

C:\Carla\carla-dev>make PythonAPI
-[BuildUE4Plugins]: [Batch params]: --build --all
HEAD is now at 260273d Correct descriptor
-[BuildUE4Plugins]: STREETMAP has been successfully installed in "C:\Carla\carla-dev\Unreal\CarlaUE4\Plugins\"
-[Setup]: [Batch params]: --boost-toolset msvc-14.2 --generator "" --all
-[Setup]: Asynchronous jobs:  16
-[Setup]: Boost toolset:      msvc-14.2
-[Setup]: Generator:          "Visual Studio 16 2019"
-[Setup]: Install directory:  "C:\Carla\carla-dev\Build\"
-[Setup]: Installing zlib...
    -[install_zlib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\"
    -[install_zlib]: A zlib installation already exists.
    -[install_zlib]: Delete "C:\Carla\carla-dev\Build\zlib-install\" if you want to force a rebuild.
    -[install_zlib]: Exiting...
The system cannot find the path specified.
        0 file(s) copied.
-[Setup]: Installing libpng...
    -[install_libpng]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --zlib-install-dir "C:\Carla\carla-dev\Build\zlib-install\"
    -[install_libpng]: A libpng installation already exists.
    -[install_libpng]: Delete "C:\Carla\carla-dev\Build\libpng-1.2.37-install\" if you want to force a rebuild.
    -[install_libpng]: Exiting...
-[Setup]: Installing rpclib...
    -[install_rpclib]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
    -[install_rpclib]: A rpclib installation already exists.
    -[install_rpclib]: Delete "C:\Carla\carla-dev\Build\rpclib-install\" if you want to force a rebuild.
    -[install_rpclib]: Exiting...
-[Setup]: Installing Google Test...
    -[install_gtest]: [Batch params]: --build-dir "C:\Carla\carla-dev\Build\" --generator "Visual Studio 16 2019"
The system cannot find the batch label specified - already_build

-[Setup]:
   Ok, and error ocurred, don't panic
   We have different platforms where you can find some help :)

   - Make sure you have read the documentation:
       http://carla.readthedocs.io/en/latest/how_to_build_on_windows/

   - If the problem persists, you can ask on our Github's "Building on Windows" issue:
       https://github.com/carla-simulator/carla/issues/21

   - Or just use our Discord channel
       We'll be glad to help you there :)
       https://discord.gg/42KJdRj
make: *** [setup] Error 1

What you expected to happen: Should proceed without saying this.
Steps to reproduce:
Other information (documentation you consulted, workarounds you tried):

We need a description of the issue. Otherwise it will be closed inmmediatly


[14.0] ISPN-14377 Stats command inaccurate results

https://issues.redhat.com/browse/ISPN-14377

We don't want to do this in 14.x


[CLI] Error attempting to restore (after cache clean)

C:\Projects\LibManCLITesting>libman restore
Failed to restore<EMAIL_ADDRESS>cdnjs, lib\twitter-bootstrap}"

[LIB002]: The<EMAIL_ADDRESS>library could not be resolved by the "cdnjs" provider

I regularly do cache clean and then restore when testing changes, and haven't encountered this in recent memory.


fix(as-3565): fix sql message queue table

fix(as-3565): fix sql message queue table

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix linting failure

Fix the linting failure caused by previous change.

Just found that 2 failure test case. Coverting it into draft PR for further fixes


Under Schwarz and density fit, how to get vhf by mf.get_veff?

dear developers,
Under Schwarz and density fit, how to get vhf by mf.get_veff in the latest pyscf?

mf = mol.RHF().density_fit()
vhf = mf.get_veff(mf.get_init_guess())


Multiple GPU support

Hello,
I was wondering if lama-cleaner has support for more than one NVIDIA GPU on Linux?
Thanks!

Sorry, currently no multi-GPU support


Access to "Unit Identifier" byte in NMBS_TRANSPORT_TCP mode is impossible

I wanted to use the library for creation modbus TCP to RTU gateway. But in the library impossible get access to "Unit identifier" byte. In function recv_msg_header() I see reciveing this byte: nmbs->msg.unit_id (this string), but I can't access this field from outside the library.

I find only one variant: I can use sometsing like as
 nmbs_set_platform_arg(&nmbs, (void *) &nmbs);
before calling nmbs_server_poll(&nmbs) and
nmbs_t *nmbs = (nmbs_t *) arg;
uint8_t unit_id = nmbs->msg.unit_id;
in my server request callbacks. But the documentation says:

All struct members are to be considered private, it is not advisable to read/write them directly.

It is only way?

This was a bit of an oversight, it doesn't make sense to not expose the RTU unit ID in server callbacks. Can you try this branch https://github.com/debevv/nanoMODBUS/tree/unit_id_callback and check if it's enough?

Yes, that's enough.

Fixed in cbd4fa69fbc8be6d7a57a224f75f830ce16dd159


[BUG] Flaky remote integration test (delete detector)

What is the bug?
Two flaky test suites for integration tests. The first test failure occurs cause a detector isn't deleted when it should be and the second failures occurs because no "create sample detector" button is found. The second failure happens because of the first test failure, the "create sample detector" button should only show up if no detectors are created.
CI failure: https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/runs/6971719640?check_suite_focus=true
Do you have any additional context?
This can be reproduced locally but it is a lot more flaky locally then on github runners.

Closing as this hasn't been seen again, will re-open if it shows up. If it shows up on 3.0 branch I will create a separate issue


feat(plugin-driver): add execute module

Summary

Test Plan

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

Current dependencies on/for this PR:

main

PR #4737   👈

PR #4718

This stack of pull requests is managed by Graphite.


Copying text in OS X with two Apple virtualization VM's running causes UTM to crash

Pressing Cmd+C to copy text in OS X while more than one Apple virtualization VM is open can result in an instant UTM crash.
Steps to reproduce

Open two Apple virtualization stack VM's
Copy text in each of them
Copy text in OS X

Result
UTM will instantly crash as soon as the copy starts, such as the instant Cmd+C is pressed. The attached crash log includes the following:
Crashed Thread:        10  Dispatch queue: com.apple.virtualization.spice-agent
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

I can reliably reproduce this crash with two VM's open.
Configuration
UTM Version: 4.0.9 (68)
macOS Version: macOS 13.0 (22A380)
Mac Chip (Intel, M1, ...): M1 Max
Crash log
Attached:
UTM-2022-11-04-142305.ips.zip

Filed FB11815988

Apple fixed this in macOS 14 beta:

Please verify this issue with macOS 14 beta and update your bug report with your results by logging into https://feedbackassistant.apple.com/ or by using the Feedback Assistant app.
macOS 14 beta (23A5257q)
https://developer.apple.com/download/
Posted Date: June 5, 2023
If the issue persists, please attach a new sysdiagnose captured in the latest build and attach it to the bug report. Thank you.


Read timeout in ClientImpl.php on line 422 because of ResponseMessage being considered as a List

If you run:
$response = $pamiClient->send(new CommandAction('database show blacklist', ''));
you'll get a read timeout in ClientImpl.php on line 422.
The reason is that in PAMI\Message\Response\ResponseMessage.php in line 137 the response of asterisk to the "database show ...." contains the string "Message: Command output follows" and there is considered as a list while it's only some raw output.
The message is therefore not considered completed and "getRelated()" won't return anything and therefore send() will time out.
This seems to be a bug.
I thin it's to greedy to scan the message for the word "follow" since this could be in any kind of message.

+1

+1


tileservices: add Cache-Status HTTP header to inform HIT or MISS on cached tiles

Once enabled by the config directive show_cache_status, the non-standard
HTTP header Cache-Status will provide information whether the response data
origin is cached data (HIT) or not (MISS).
Also, on each thousand requests made to the tile services, it will be logged the
ratio (%) of hits and misses.

@weskamm Any idea why this PR wasn't merged? It sounds like a really good idea/feature.
I'd be happy to help, if any is required.

Did you see my comment? I guess there is a check missing around the logging if logs should be produced at all.
Besides, tests and documentation for this new feature would be required. Feel free to jump in!

I'm not sure the logging feature is that useful, even if configurable.

It will reset on each restart of the process (which can happen regularly, depending on the deployment method).
You will get multiple logs of the same count when using multi-threaded deployment methods (race condition).
You will get multiple logs of different counts when using multi-process deployment methods (globals are note shared).

Just add the headers and write a WSGI middleware that moves the stats into something like Prometheus.

@weskamm. Also, I think there's a bug in the original implementation (I've re-implemented myself and found the cache status header was not working until I applied a fix).
@olt I totaly agree with you. I don't really mind the logging/count feature, it should not be here. the Cache-Status  header is what I care about.
I'm willing to contribute a cleaner PR (header addition only) and documentation, If you'd like me to :-)

@weskamm. Also, I think there's a bug in the original implementation (I've re-implemented myself and found the cache status header was not working until I applied a fix).
@olt I totaly agree with you. I don't really mind the logging/count feature, it should not be here. the Cache-Status  header is what I care about.
I'm willing to contribute a cleaner PR (header addition only) and documentation, If you'd like me to :-)

@sheinbergon

I'm willing to contribute a cleaner PR (header addition only) and documentation, If you'd like me to :-)

I don't have anything to decide, but I'd be highly interested in it.

@weskamm @olt any comments regarding my suggestion?

@weskamm @olt ?

@weskamm @olt any comments regarding my suggestion?

Feel free to make another pr with documentation and tests included. seems like a useful feature to me

ok will close this now as its superseeded


Dot not in middle when line height not 1.5

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
5.3.2
Describe the bug
Dot when line height set as 2 in minimal theme settings, not in center

This is 1.5 line height

Debug info
SYSTEM INFO:
Obsidian version: v0.15.9
Installer version: v0.14.15
Operating system: Windows 10 Pro 10.0.22000
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Minimal
Snippets enabled: 3
Restricted mode: off
Plugins installed: 45
Plugins enabled: 34
1: Calendar v1.5.10
2: Advanced Tables v0.17.3
3: Stille v1.2.1
4: Recent Files v1.3.3
5: Collapse All v1.5.2
6: File path to URI v1.4.0
7: Note Folder Autorename v0.1.2
8: Folder Note v0.7.3
9: Style Settings v0.4.10
10: Minimal Theme Settings v5.3.2
11: Dataview v0.5.41
12: Templater v1.12.0
13: Frontmatter Tag Suggest v0.4.1
14: Better Word Count v0.8.1
15: Obsidian Charts v3.6.2
16: Tag Wrangler v0.5.3
17: Admonition v9.0.3
18: Customizable Sidebar v2.2.1
19: Hotkeys for specific files v1.2.0
20: Local images v0.14.2
21: Kanban v1.3.11
22: Excel to Markdown Table v0.4.0
23: Dictionary v2.21.1
24: Hider v1.1.1
25: Sortable v0.2.5
26: Contextual Typography v2.2.4
27: Banners v1.3.3
28: Tasks v1.11.0
29: Advanced Slides v1.15.0
30: QuickAdd v0.5.5
31: Remember cursor position v1.0.7
32: Excalidraw v1.7.8
33: Flashcards v1.6.3
34: LanguageTool Integration v0.3.0
RECOMMENDATIONS:
Custom theme: for cosmetic issues, please first try updating your theme to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

This will be fixed in Minimal 6.0 which will be coincide with the next major version of Obsidian


eyedropper tool to pick colors from screen

Hi I was wondering if there is an option to turn on a color picker to pick colors from your screen Like we have in chrome. I will attach screenshot below

hi Did you solve it i have the same problem

Hi I was wondering if there is an option to turn on a color picker to pick colors from your screen Like we have in chrome. I will attach screenshot below

hi Did you solve it i have the same problem

Hi I was wondering if there is an option to turn on a color picker to pick colors from your screen Like we have in chrome. I will attach screenshot below

hi Did you solve it i have the same problem


[Feature] Add basic bar visibility change to IPC

Adds a set_visible IPC command which takes a boolean visibility and string bar_name fields.
Simultaneously adds a new config name option to name each bar individually (defaults to the monitor name)
Behavior as-is will show/hide every bar with a given name. e.g, 2 bars both with the name test will be shown/hidden if we pass
{"type":"set_visible","visible"=true,bar_name="test"}

A couple of issues left from yesterday & a few more minor tweaks, but the implementation looks solid now. Cheers :)


typo found in function name (satus -> status)

first time contributing on github

Please merge

Please merge