Repo is not out-of-the box anymore, please specify versions

Hello, It is a really nice repo, however it is not out-of-the box anymore. I have been fighting version-hell for a while. I think that the problem is threefold:

/requirements/*.txt do not contain specific versions.
In /docs/getting_started.md versions mmdet==2.10.0 and mmcv==1.2.4 are given, however there is no hint for mmdet3d version.
The best would be a full pip/conda freeze version snapshot when everything is installed according to INSTALLATION in getting_started.md.

That's a very good point! Did you get yours running? I'm stucked in the version-hell as well. What's the version working for you?

Here are my notes, which I am not 100% sure that complete. I have abandoned playing with TransFusion, I will be back soon, then I awake again the repo from zero and I refresh here my notes.
Requirement: Conda or miniconda installed.
cd ~/install/ # Typically I use ~/install/ for storing install files.
wget http://developer.download.nvidia.com/compute/cuda/11.0.2/local_installers/cuda_11.0.2_450.51.05_linux.run
sudo sh cuda_11.0.2_450.51.05_linux.run # accept, only toolkit to be installed
chmod 777 cuda_11.0.2_450.51.05_linux.run
/usr/local/cuda/bin/nvcc --version # Build cuda_11.0_bu.TC445_37.28540450_0 # nvcc --version
conda remove -n trfu --all -y
If env was created and deleted several times.
conda create -n trfu python=3.7 -y
conda activate trfu
conda install pytorch==1.7.0 torchvision==0.8.0 torchaudio==0.7.0 cudatoolkit=11.0 -c pytorch -y
python
import torch
torch.cuda.is_available()
pip install -U openmim # mim is the package management tool for the OpenMMLab projects, which makes it easy to install mmcv # https://mmcv.readthedocs.io/en/latest/get_started/installation.html
mim install "mmcv<=1.4.0"
mim install "mmdet<=2.10.0"
mim install mmcv-full==1.2.4
git clone https://github.com/open-mmlab/mmdetection3d.git
cd mmdetection3d
git checkout 9802d41
pip install -v -e .  # or "python setup.py develop"
pip uninstall pycocotools -y
pip install mmpycocotools
pip uninstall mmpycocotools
pip install mmpycocotools
Then you can run demo/pcd_demo.py

Thanks a lot!!!! Have you got the Docker running btw?

Thanks a lot!!!! Have you got the Docker running btw?

I do not remember... I will fix that too sooner or later...

Thanks! Lemme know if you have any update. I'm gonna send you my notes too once I get mine working.

Hi,
I'm also trapped into version problem right now, tried all combinations between recommended mmcv (1.2.4 to 1.3.0) and mmdet (2.5.0 to 3.0.0) and it didn't work

Hey @changxu-zhang
I tried @gaborlegradi instruction but ran into cuda errors.
So I tried it with cuda 11.1 and Pytorch 1.8.0
wget https://developer.download.nvidia.com/compute/cuda/11.1.0/local_installers/cuda_11.1.0_455.23.05_linux.run
sudo sh cuda_11.1.0_455.23.05_linux.run --silent --toolkit --override
pip install torch==1.8.0+cu111 torchvision==0.9.0+cu111 torchaudio==0.8.0 -f https://download.pytorch.org/whl/torch_stable.html
pip install -U openmim
... and the further commands of the instruction
After that I had to copy/replace the following files to train with the nuscenes dataset.
From the folder TransFusion/mmdet3d into the folder mmdetection3d/mmdet3d:
./models/detectors
transfusion.py
mvx_two_stage.py
init.py
./models/dense_heads
transfusion_head.py
init.py
./core/bbox/coders
transfusion_bbox_coder.py
init.py
./core/bbox/assigners.py
hungarian_assigner.py
init.py
./datasets
nuscenes_dataset.py
./datasets/pipelines
loading.py
I'm pretty new into this. Maybe there is a better workaround.

Hi @DanielDoerr ,
Could you please post your mmcv, mmdet and mmdet3d verison?
Thanks

@changxu-zhang
mmcv 1.4.0
mmcv-full 1.2.4
mmdet 2.10.0
mmdet3d 0.11.0
What errors do you get during the installation?
I also have many installation attempts before that. The only way that worked for me was the instructions from above.
I installed it on Ubuntu 20.04 and also on WSL2.
Please make sure you install the correct CUDA version for your distribution.

hello @DanielDoerr @gaborlegradi
I have a problem while installing mmdet 2.10.0 to try @gaborlegradi instroductions..
mim install "mmdet<=2.10.0" or pip install mmpycocotools:
ERROR: Failed building wheel for mmpycocotools
I can't google abour this problem because the latest version of mmdet is no longer using mmpycocotools
I'm using CUDA 11.1 and pytorch 1.8.0, gcc 9.4.0 and ubuntu 20.04
how can I solve this problem to run Transfusion?


[Discussion/Question] tolist implementation in cupy

We(cudf) are in the middle of disabling(throwing errors) for methods(__iter__, iteritems, to_dict, tolist) that will result in device to host transfers. This is similar to how we throw an error currently for __array__ in cudf & cupy.
So during a discussion on disabling tolist(in cudf), @jakirkham  pointed out that cupy actually allows calling tolist which creates a device to host transfer. Was there any motivation behind allowing tolist to return a result and restricting __array__ ?

cc: @pentschev @kkraus14

I guess the reason is that __array__ could perform the device-to-host transfer without users noticing it, whereas tolist() does not have this issue (as someone must call arr.tolist() explicitly). If downstream libraries do not call tolist(), it should be fine.

I think our fear from the cuDF side is that tolist() is a built-in API of numpy / Pandas which only has medium performance impact so code may not have been too afraid or thoughtful in using it. Now with CuPy / cuDF, the performance impact of going to a Python list is catastrophic, but it would be unbeknown to the user as to why they're seeing poor performance because it's hidden underneath a library.

Well I think it is commonly known that lists are not the most performant way of operating with data in Python. Certainly there’s an extra performance hit moving from device to host in the GPU cases, but maybe that already fits in with the lists are slow understanding. So I think this mostly gets used when users really want a Python native object in spite of performance issues.


⚠ ClamAV has degraded performance

In 393cbf6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 112 ms

Resolved: ClamAV performance has improved in bdb936d.


Add troubleshooting section in docs

We should create a new section like troubleshooting or so to address all the answers to the most common errors and questions we've been receiving. We can split this new section into multiple parts like installing, deploying, compiling/checking, testing, etc

We have the FAQ section which includes solutions for frequent problems. Any other frequent problems can go there too.


[wizard2] constant var template updates

added more mappings
hooked up user mapping updates from template

thanks for the review!


Very confusing code for tree generation

I've been trying to change the tree shape, but I've run into this:

I can't understand it at all. Is there any documentation on this code? I can't understand it by reading it.

I'm very sorry, but I really don't know how I made this. Even though I made it. I don't know too much c# and Perlin noise to do this

It's not that complicated, it's just creating a random blob of leaves which tapers to the top and bottom. Refactoring it would make it much easier to understand.


[AST] Start with un-calibrated AST clocks

Signed-off-by: Jacob Levy<EMAIL_ADDRESS>Start with uncalibrated AST clock according to clock spec.
Once AST init is done the clocks become calibrated.

@sriyerg  @sha-ron After incorporating the un-calibrated AST clocks to the OS model, the chip level SW tests are
failing the same way as with the NTIL AST.

@tjaychen Oschilator's model issues were fixed and AON oscilator remain calibrated during deep sleep.


Create solved problem page

Still need some CSS styling, only created a basic structure into the index.js


TestID value is put into the Android's View tag

Currently TestID value is put into the Android's View tag, but it is not available via Appium on Android.
UIAutomator2 is not planning to support it: https://github.com/appium/appium/issues/6025#issuecomment-322266065.
I'm aware of a workaround to use AccessibilityLabel (which is the only option), but this information is intended to be read to the end user so I would prefer not to put some testIDs in there.
Are there any plans to work on this issue?

@sonianin Please use the issue template going forward.
As for TestID on android: it has been discussed in the past here: https://github.com/facebook/react-native/issues/7135 and https://github.com/facebook/react-native/pull/9942
Let's continue on those issues.

@chirag04 Both issue and PR you are referring to are closed by now... Is anyone going to work on the closed issue?

nobody that i know is working on it, i can't speak for fb tho. you can put your proposal there if any. Also suggest reading through those issue to see if it helps and come up with a PR.

@chirag04
Given there is a problem - for Android testing with Appium you could use only AccessibilityLabel - what would be the proper way to request the fix/feature?
As was mentioned above using testID seems to be viable solution (ReactNative.testID -> Android.resource-id)

The best way I can tell you is to come up with a proposal and open a PR with POC. If you need this you will have to built it.
I understand this has been a long standing issue. There are tools like detox which now work on android as well, so if you can’t build I suggest you look at them.

Ok, thanks for the reply.
Regarding Detox - they "Currently supports iOS, Android support is coming - status page.". As far as I can see it is in beta with all the risks that come with. Though given all the circumstances it looks like decent option.
Regarding long standing issue - it could be summarized by comment from #7135 on Jul 25 - "we are suffering and they don't care..." :)


better shader with sky/ground light, along with half lambert

Compared with

to

I added Sky/Ground Light along with Half Lambert. Color was removed since it may present special use with custom shader, which is confusing sometime.
TODO: recalculate normal; SSAO for better view

recalculate normal DONE: some mesh may come with wrong normal (or hand modified...)

recalculate version:

Also this step only affects previewing, not exporting

I'm not sure remove color whether it's a good idea, some file like this one
https://mega.nz/#!TA1UiaJZ!odCyq-lbyFKtM9pYQxNb37n0Idf-8MxU-7qffduMBeM
Including colors will make the preview better

what about more preview types:

default mode (as I implemented)
normal mode
color mode
wire frame

more modes supported!
Ctrl+S: switch shade mode (Lambert vs. VertexColor)

Ctrl+W: switch wireframe mode

Ctrl+N: whether to use recalculated normal

ps. This has some conflicts with my another PR, and I'll fix it later after one has merged

OK, I'll merge this first.


feat!: metrics setup, and first metrics

Summary
Adds the setup for metrics into core telemetry init, adds config for it to all our standard services.
Background
Metrics are currently only available through cometbft or rollup nodes, we want to have metrics in our configuration
Changes

Updates all service configs
Updates telemetry to enable initializing prometheus metrics
Adds a couple of metrics for sequencer-relayer, and celestia-client

Breaking Changelist

new configuration fields

This is a replacement PR of https://github.com/astriaorg/astria/pull/716. After otel merges there were significant changes that made it easier to start over.

Heads up that we discovered a couple of warts with the 22 release of metrics. It accidentally broke our reporting because we upgraded main crate without upgrading the<EMAIL_ADDRESS>and<EMAIL_ADDRESS>crates in lockstep.
Unfortunately, for now, this isn't easily remediated because metrics-util pins a dependency and this create an intractable conflict with other hashbrown imports (in your case, one from the jmt crate, and another from the astria-core crate). I have reached out to the upstream to help with releasing a version that removes the pinned dep, and maybe discuss how it affects the "downstream experience".
Sorry about the churn, but although I'm hopeful that this will be sorted out early next week, we might decide to revert back to<EMAIL_ADDRESS>if this stalls for too long (we need metrics).

Heads up that we discovered a couple of warts with the 22 release of metrics. It accidentally broke our reporting because we upgraded main crate without upgrading the<EMAIL_ADDRESS>and<EMAIL_ADDRESS>crates in lockstep.
Unfortunately, for now, this isn't easily remediated because metrics-util pins a dependency and this create an intractable conflict with other hashbrown imports (in your case, one from the jmt crate, and another from the astria-core crate). I have reached out to the upstream to help with releasing a version that removes the pinned dep, and maybe discuss how it affects the "downstream experience".
Sorry about the churn, but although I'm hopeful that this will be sorted out early next week, we might decide to revert back to<EMAIL_ADDRESS>if this stalls for too long (we need metrics).

Thanks for the heads up. Ran into the dependency issue you mentioned myself while trying to update. Will revert to 0.19 for now and upgrade if resolved (as you noted.... we need metrics).


[i18n] Translatable Casper default theme

[i18n] Translatable Casper default theme
no issue

(note: this Casper commit completes a Ghost commit with full translation of Ghost's frontend for site visitors: "[i18n] Translatable Ghost's frontend: Themes, dates, pagination, subscribe forms")

all 21 theme text strings included in translatable {{t}} handlebars helpers in Casper, the Ghost default theme which is the model for all Ghost themes

easily readable original English text in templates, for very simple translation

usage examples, in .hbs templates:

  {{t "mytheme" "Get the latest posts delivered right to your inbox"}}
  {{{t "mytheme" "Proudly published with {ghostLink}" ghostLink="Ghost"}}}

and in .json translation files, for example for Spanish:

  "mytheme": {
      "Get the latest posts delivered right to your inbox": "Recibe los últimos artículos directamente en tu buzón",
      "Proudly published with {ghostLink}": "Publicado con {ghostLink}"
  }

also added two very small stylesheet files, assets/css/en.css and assets/css/es.css, for some css content strings that needed translation by override; stylesheets linked using Ghost's standard getAssetUrl
see the complementary Ghost commit for additional details

The complementary Ghost pull request is:
[i18n] Translatable Ghost's frontend: Themes, dates, pagination, subscribe forms
https://github.com/TryGhost/Ghost/pull/8437

Added a minor commit to this pull request:
[i18n] Renamed new {{i18nCss}} css translation helper as {{t_css}}
pull request #306

renamed new {{i18nCss}} css translation helper as more user friendly {{t_css}} for ease of use and consistency with the rest of helper names
there is a complementary commit for Ghost's PR TryGhost/Ghost#8437

[i18n] Separate .json translation files for themes
pull request #306

for .hbs templates in content/themes, using translation files: content/themes/mytheme/assets/translations/mytheme_en.json, mytheme_es.json, mytheme_en-US.json, etc. (replacing "mytheme" with the active theme, such as casper, etc.)
more details in a complementary commit for Ghost's PR TryGhost/Ghost#8437

[i18n] Moved .css translation files for themes
pull request #306

to facilitate translators' work, moved .css translation files for themes from assets/css/en.css, etc. to assets/translations/mytheme_en.css, etc. (replacing "mytheme" with the active theme, such as casper, etc.)
adjusted {{t_css}} helper and its test accordingly
there is a complementary commit for Ghost's PR TryGhost/Ghost#8437

[i18n] (t) translation helper's subexpressions for {{plural}} and other helpers
pull request #306

using (t) translation helper's subexpressions inside {{plural}}, {{subscribe_form}}, and {{input_email}} helpers for placeholders, etc., instead of "where" parameters
simplified these helpers; now similar to before the pull requests; just a few objects needed conversion to string for {{plural}}
since {{t}} translation helper returns new SafeString, there is no need for {{{t}}} to preserve HTML; using now {{t}} instead in all cases
adapted several templates for these changes
subexpressions requested in pull request review
there is a complementary commit for Ghost's PR TryGhost/Ghost#8437

[i18n] {{t_css}} helper replaced by {{theme}} and {{lang}}
pull request #306

adapted theme template default.hbs for this change, including
see more details in the two complementary commits for Ghost's PR TryGhost/Ghost#8437, and for gscan's PR TryGhost/gscan#48

[i18n] minor improvements for translatability
pull request #306

facilitating more the use of placeholders with subexpressions in full translation strings, rather than translating separate sentence fragments; often those fragments are in different order for different languages, therefore placeholders are better and more flexible
when preserving HTML, back to using {{{t}}}; from now, this helper doesn't use a SafeString object which would prevent escaping, because often other helpers need that (t) returns a string to be able to work as subexpression
because of this, the {{plural}} helper is again like before these pull requests, but with translations working
examples:
{{tags prefix=(t "casper" " on ")}}
{{{t "casper" "Read more posts by this author" url=(url)}}}
there is a complementary commit for Ghost's PR TryGhost/Ghost#8437

[i18n] further usability improvement of translation helper
pull request #306

now there is no need to include the theme name in {{t}}

before:
{{t "mytheme" "Subscribe"}}
after:
{{t "Subscribe"}}

more details in the complementary commit for Ghost's PR TryGhost/Ghost#8437

This work is awesome.
Could you explain me the reasons why this PR is not merged ?
I would be happy to make you a PR for at least call the "t" helper in the templates even if the translation files are not hosted directly in this repo.

I wonder why this PR is not merged too. Translation is a built-in ability for Ghost, but the default theme doesn't support it. Wow.

As mentioned in the comment above, if you want a translated theme you're free to use a fork such as https://github.com/juan-g/WorldCasper2 or any other theme and adapt it to your needs 😉
Casper is intended as a minimal default theme that's useful for Ghost beginners to get started and customise to their needs. Adding localisation features which complicate/obscure the theme development for the large majority of users which don't have any localisation needs is counter to that focus.

@kevinansfield

Adding localisation features which complicate/obscure the theme development
Will it complicate much?  I thought not hard-coding is a good thing.


Fill in more of rttydesc.rs

This makes native vector functions work for vectors of all the numeric types.
I'm still debugging some crashes when dealing with vectors of vectors, and will submit support for more types later.

I see @nvjle has also done this in https://github.com/solana-labs/move/pull/176.

I see @nvjle has also done this in #176.

I did not do U256 in #176, which your patch does. Also, I did not see this PR before I posted my PR, sorry about that. My prgoress was blocked on putting more vectors through the generic function work without adding some more types.
I still cannot test generic functions for vectors of struct, so that would be very worthwhile to add to the runtime.

I'll do a follow up based on your patch.


write permissions for docs

PR Summary

The docs CI test currently fails for forks due to a permissions issue.  This hopefully gives the github runner sufficient permissions to publish to the github-pages branch. Given that anyone can submit a fork, this is a little less secure. As such, I have tightened the security settings on github. A maintainer must click "approve" to run workflows from forks.
The re-git settings are the same as always, only LANL people may trigger runs on LANL resources.
@sfogerty, can you try merging this into your branch?
PR Checklist

[ ] Adds a test for any bugs fixed. Adds tests for new features.
[ ] Format your changes by using the make format command after configuring with cmake.
[ ] Document any new features, update documentation for changes made.
[ ] Make sure the copyright notice on any files you modified is up to date.

Unfortunately it doesn't look like this solves the issue for @sfogerty's pull request. So I'm not sure if this is worth pursuing.


added "What is FOSS" page in footer under handbook column

I added the "what is FOSS" page which is located in "FOSSCU handbook" in the footer section under handbook column. This will help visitors to know about what is FOSS and what does it aim at.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

@Rishika-993 Please open an issues and think this PR to it.

Thx @Rishika-993 Awesome Work


Portfolio view. Receive tokens

When the user clicks on Receive button on Token-centric view start new flow with chain selector

Status verification: ✅


how to get argo link inside worfklow/task definition

Is there a way to get the workflow's link within the workflow itself? I am running training experiments and logging with weights and biases. I want to essentially get the workflow's link within the task so I can log the wandb's configuration to include the link to the workflow.

Hey @nollied! Thanks for the question. Here's an example that shows how you can load the workflow name:
from hera.workflows import Workflow, script, Steps

@script()
def foo(name):
    print('inside workflow {name}'.format(name=name))

with Workflow(name="test-wf-name", entrypoint="s") as w:
    with Steps(name="s"):
        foo(arguments={"name": "{{workflow.name}}"})

w.create()

Inspired by these docs! If you want a full workflow link that would take you to Argo specifically, you could parameterize your function to take your platform's host and scheme and assemble a link inside the print statement above like {scheme}://{host}/{namespace}/{name}. Note that {{workflow.namespace}} is also a variable!

Hey @nollied! Would love to hear if the above worked out for you. Closing this in the mean time as it works out of the box


Fraud Proofs - one PR to rule them all again

This PR is just a reference to #538 which was consolidated changes made by me, however, it was opened by @tzdybal so he could not approve it. We'll use this PR as a proxy for that PR in order for approval.
Please look at #538 for relevant comments.

Codecov Report

Merging #567 (7e3fccc) into main (2e000cf) will decrease coverage by 0.77%.
The diff coverage is 44.73%.

@@            Coverage Diff             @@
##             main     #567      +/-   ##
==========================================
- Coverage   55.81%   55.04%   -0.78%
==========================================
  Files          50       50
  Lines        9555    10256     +701
==========================================
+ Hits         5333     5645     +312
- Misses       3428     3749     +321
- Partials      794      862      +68

Impacted Files
Coverage Δ

config/config.go
86.95% <ø> (ø)

conv/abci/block.go
94.23% <ø> (ø)

conv/addr.go
100.00% <ø> (ø)

conv/config.go
47.05% <ø> (ø)

da/celestia/mock/server.go
50.32% <ø> (ø)

da/registry/registry.go
100.00% <ø> (ø)

mempool/v1/mempool.go
86.09% <ø> (-0.63%)
:arrow_down:

p2p/gossip.go
82.00% <ø> (ø)

rpc/json/handler.go
84.52% <ø> (ø)

rpc/json/service.go
65.00% <ø> (ø)

... and 24 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


fix: MD038/no-space-in-code

Use code fences for multi-line blocks

@nschonni : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@nschonni : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified minor updates.


[Deployments]: AWS Lambdas

Deploy AWS Lambdas using Shuttle

This issue is a part of the Product Feature Poll (all issues). React with :+1: if you want this feature. Comment if you have suggestions related to this feature.

Pulling out a summary of this idea from a Discord discussion.
The proposal would be to accept user code and execute it on the Shuttle runtime in a Function-as-a-Service manner - made famous by AWS Lambda.
Benefits to the user

Worry less about configuring a webserver - choosing between Axum / Rocket etc and maintaining that
Guaranteed successful execution of each call, since the contract with users is that it might be a cold start, but it will eventually complete. Currently infrequently used services fail more often (is my understanding)
Potentially able to write very simple code with a very short time to market - no wrestling with endpoints
Huge advantages over AWS Lambda like the Shuttle deployment system, configuration as code

Benefits to Shuttle

More homegeneous user code is easier to support / less proliferation of webservers / versions
Potentially more economical execution of user code - this needs to be validated
Potentially simpler pricing model / free tier - minutes of execution per month

Below is an example of what user code to register a Shuttle FaaS might look like:

#[derive(serde::Serialize)]
pub struct CalculationResult {
    z: f64,
}

#[derive(serde::Deserialize)]
pub struct CalculationInput {
    x: f64,
    y: f64,
}

pub enum Error {
    InternalError,
}

// More hands-on way of exposing a lambda-like endpoint
#[shuttle_runtime::faas_post("/mutliply")]
pub async fn multiply(input: CalculationInput) -> Result<CalculationResult, Error> {
    Ok(CalculationResult {
        z: input.x * input.y,
    })
}

// Could it be simplified such that someone would only need to do the below? Shuttle
// would then generate the JSON types
#[shuttle_runtime::faas_post("/multiply_simple")]
pub async fn multiply_simple(x: f64, y: f64) -> f64 {
    x * y
}

Things to think about:

Auth
Sync vs async? Could async benefits be realised inside a sandboxed container?
How to handle errors?
Allow all HTTP methods / accept-headers etc?
Allow any form of HTTP result? E.g. would it just be a ShuttleFaas result object?
Are the imagined efficiencies there?

Adding some more benefits that a FaaS model might bring to both users and the platform, largely due to the request-scoped nature of FaaS:

Idling and scale-up concurrent project deployments based on request load
Shuttle can own the availability and scalability of the user by applying resiliency and scalability patterns using request-level success metrics (retries, timeouts, redundancy etc.)
Enable on-demand pricing models that can scale to zero when project not in use
More granular per-request monitoring capabilities for the app out of the box: e.g. per-project availability, latency and breakdown, errors, dependency failures etc.
Event-driven triggers for requests to projects instead of just REST APIs
Continuous security patching of OS and OS deps,


so: fix autoupdate url

Closes #9077

[x] I have read the Contributing Guide.

/verify

/verify

But now this is failing on the windowns build.

/verify

You should run checkver -f so locally to update to ver 0.4.8.

You should run checkver locally to update to ver 0.4.8.
in Powershell:
(SCOOP_DIRECTORY)\buckets\extras\bin\checkver.ps1 -f (PATH_TO_THE_JSON_FILE)

/verify

/verify

/verify

/verify


Sensors sv_* not available after updating Home Assistant Core

custom_component/hahomematic version (if applicable):
1.3.1 via HACS
Home Assistant version (if applicable):
Home Assistant Core 2022.5.4
Home Assistant Supervisor 2022.05.1
Home Assistant OS 7.6
CCU version:
RaspberryMatic <IP_ADDRESS>20430 as HomeAssitant-Addon
Problem-relevant configuration:
Do you use tls? No
Do you use callback? No
Do you use username and password? Yes
Which interfaces do you use? HM-MOD-RPI-PCB/GPIO
Describe the bug
I use sensor.homematic_sv_alarmmeldungen, sensor.homematic_sv_dutycycle and sensor.homematic_sv_servicemeldungen to monitor the status of my Homematic environment.
After the last recent Homeassistant Core Update, all 3 sensors are not available.
To Reproduce
Steps to reproduce the behavior:

perform Homeassistant Core Update, started on 2022-05-13T04:16:37.542Z
After Homeassistant starts, the three sensors are "unavailable". Last sensor change on 2022-05-13T04:20:00.633Z

Screenshots (if applicable)

Relevant HA log entries (full log)
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-05-13 07:16:19 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration homematicip_local which has not been tested by Home Assistant.
Identifying host system: oci, OK
Initializing RTC Clock: no hardware found
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, <IP_ADDRESS>, OK
Identifying Homematic RF-Hardware: ....HmRF: HM-MOD-RPI-PCB/GPIO, HmIP: HM-MOD-RPI-PCB/GPIO, OK
Updating Homematic RF-Hardware: HM-MOD-RPI-PCB: 2.8.6, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: .OK
Starting rfd: .OK
Starting HMIPServer: ............OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: <IP_ADDRESS>20430 (raspmatic_oci_arm64)

Diagnostic Information (available on every device)
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.5.4",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.9.9",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Berlin",
    "os_name": "Linux",
    "os_version": "5.10.103-v8",
    "supervisor": "2022.05.1",
    "host_os": "Home Assistant OS 7.6",
    "docker_version": "20.10.9",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.24.5",
      "requirements": [
        "aiogithubapi>=21.11.0"
      ]
    },
    "homematicip_local": {
      "version": "1.3.1",
      "requirements": [
        "hahomematic==1.3.0"
      ]
    }
  },
  "integration_manifest": {
    "domain": "homematicip_local",
    "name": "Homematic(IP) Local",
    "config_flow": true,
    "documentation": "https://github.com/danielperna84/custom_homematic",
    "issue_tracker": "https://github.com/danielperna84/hahomematic/issues",
    "requirements": [
      "hahomematic==1.3.0"
    ],
    "ssdp": [
      {
        "manufacturer": "EQ3",
        "manufacturerURL": "http://www.homematic.com"
      }
    ],
    "zeroconf": [],
    "homekit": {},
    "dependencies": [],
    "codeowners": [
      "@danielperna84",
      "@SukramJ"
    ],
    "iot_class": "local_push",
    "loggers": [
      "hahomematic"
    ],
    "version": "1.3.1",
    "is_built_in": false
  },
  "data": {
    "config": {
      "entry_id": "81acd35b5879e99e0d1392cdc49bf213",
      "version": 1,
      "domain": "homematicip_local",
      "title": "Homematic",
      "data": {
        "instance_name": "Homematic",
        "host": "de838cd8-raspberrymatic",
        "username": "**REDACTED**",
        "password": "**REDACTED**",
        "callback_host": "<IP_ADDRESS>",
        "callback_port": 0,
        "json_port": null,
        "tls": false,
        "verify_tls": false,
        "interface": {
          "HmIP-RF": {
            "port": 2010
          }
        }
      },
      "options": {},
      "pref_disable_new_entities": false,
      "pref_disable_polling": false,
      "source": "user",
      "unique_id": "<IP_ADDRESS>",
      "disabled_by": null
    },
    "platform_stats": {
      "binary_sensor": 13,
      "climate": 14,
      "cover": 12,
      "sensor": 40
    },
    "devices": [
      "HmIP-BROLL",
      "HmIP-BWTH",
      "HmIP-SWSD"
    ]
  }
}

Expected behavior
The sensor data should be available after upgrading or restarting Homeassistant.

I restarted Home Assistant after adding additional logging information to my config, not it works, sensors are back with data again just after having Home assistant started again.

Hi,
are you running HA and HM-Addon on a Raspberry PI?
Version 3 or 4 (which model)?

Hi, are you running HA and HM-Addon on a Raspberry PI? Version 3 or 4 (which model)?

Yes, Raspberry Pi 4

I think the issue is related to the speed of your HW.
This problem as been reported some times, but as far as i know related to slower HW and an update of HA.
Next release will raise some timeouts.
For future investigations an updated logging would be helpful.
Please add this to your configuration.yaml:
logger:
  logs:
    hahomematic: info
    custom_components.homematicip_local: info

info is less noisy then debug and should give some more hints, if the problem reoccurs in future.
Please close this issue for now, and reopen it, if this issue reoccurs again.

I released a new version (1.3.2) with increased timeouts.

Logging set to info already. I've updated to 1.3.2 and did a complete host reboot (which might be the same scenario as HA Core Update). Started properly with all sensor data available.
I'll reopen if this issue reoccurs in the future.


BUG: Ability to register nodes with duplicate node IDs

Problem
Nodes are identified by a 32-byte identifier, provided as input by the node operator at the time of registration. In flow-go it is represented as a [32]byte, in flow-core-contracts it is represented as a hex-encoded String.
Node IDs must be unique. The smart contract enforces uniqueness by using the node ID as the key in a dictionary, however this results in uniqueness being defined by the string representation, which means two different operators could input (eg.) Abcd and abcd and both would be accepted, despite both referring to the same identifier.
Acceptance Criteria

Node ID uniqueness should be enforced

How can we enforce this in the smart contract, since we take the arguments as strings already?

How can we enforce this in the smart contract, since we take the arguments as strings already?

One way would be to enforce an unambiguous representation, for example requiring all inputs be lowercase or converting them to lowercase.

So would I just iterate through each character and make sure it is a number or lowercase hex character?
0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f

Is there a better way to do it than that?


OpenAPI3 support!

Working implementation based on petstore converted to openapi 3.
Contains multiple structural code improvements as well.

Great job man!


Adding glob or list support for read_parquet

Hi,
Per dask/fastparquet#130, I am trying to read a dir of parquet files into dask using read_parquet. When I am trying to use:
import s3fs
import dask.dataframe as dd
s3=s3fs.S3FileSystem()
filelist = ['s3://'+item for item in s3.ls('bucket_name')
            if item.split('.')[-1] == 'parquet']
dd.read_parquet([item for item in filelist[:3]])

I got the following error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-89-520ffa2e42c4> in <module>()
----> 1 dd.read_parquet([item for item in filelist[:3]])

/opt/anaconda/anaconda<IP_ADDRESS>/lib/python3.6/site-packages/dask/dataframe/io/parquet.py in read_parquet(path, columns, filters, categories, index, storage_options)
     65         filters = []
     66     myopen = OpenFileCreator(path, compression=None, text=False,
---> 67                              **(storage_options or {}))
     68
     69     if isinstance(columns, list):

/opt/anaconda/anaconda<IP_ADDRESS>/lib/python3.6/site-packages/dask/bytes/core.py in __init__(self, urlpath, compression, text, encoding, errors, **kwargs)
    255         self.encoding = encoding
    256         self.errors = errors
--> 257         self.storage_options = infer_storage_options(urlpath, inherit_storage_options=kwargs)
    258         self.protocol = self.storage_options.pop('protocol')
    259         ensure_protocol(self.protocol)

/opt/anaconda/anaconda<IP_ADDRESS>/lib/python3.6/site-packages/dask/utils.py in infer_storage_options(urlpath, inherit_storage_options)
    834     """
    835     # Handle Windows paths including disk name in this special case
--> 836     if re.match(r'^[a-zA-Z]:[\\/]', urlpath):
    837         return {'protocol': 'file',
    838                 'path': urlpath}

/opt/anaconda/anaconda<IP_ADDRESS>/lib/python3.6/re.py in match(pattern, string, flags)
    170     """Try to apply the pattern at the start of the string, returning
    171     a match object, or None if no match was found."""
--> 172     return _compile(pattern, flags).match(string)
    173
    174 def fullmatch(pattern, string, flags=0):

TypeError: expected string or bytes-like object

Here is my environment:

dask                      0.14.1                   py36_0
fastparquet               0.0.5                    py36_1    conda-forge

Can you please try with https://github.com/dask/dask/pull/2207 ?

Any updates here?  Has this been resolved?

The simple case was solved, the more complex case of multiple data-sets in directories was not - and probably should not be, since one could use concat.


\cref macro doesn't produce "section"

The SIAM Style Manual (p31) requires references to section numbers to use the word "section", rather than the symbol "§", e.g., "see section 3.2", rather than "see §3.2". The class file, however, implements the former.
Truth is, I prefer the section symbol, and use it by default, only to find myself changing them all back to SIAM's preferred "section" on submission.
Do we need to adhere to SIAM's style, or does the revised style file imply our request for SIAM to modify the current requirements?

Ah-ha. I obviously did not read the style manual in detail. Thanks for catching this. We can certainly ask SIAM to reconsider. Meanwhile, I will fix this to adhere to the style manual.

Fixed, but not sure how to mark as such.


Version 0.0.13.pre x86-mingw32 does not work

In the 32-bit version of RubyInstaller, that is x86-mingw32, LibUI cannot find the shared libraries.
https://github.com/kojix2/LibUI/blob/b5b6bfb1a7363342f5b373415f583c49b7680b07/lib/libui.rb#L12-L15
RbConfig::CONFIG['host_cpu'] will be i386.  Not x86

0.1.3.pre - November 12, 2023 x86-mingw32 (120KB) Yanked

Are many folks using 32 bit still?

Not many people use the 32-bit version, so dropping its support won't be a major issue.
However, I will add support for x86-mingw32 in libui-ng in the next version, as it's easy to do.


Change from MSI to Nuget package

Change installation from using MSI to Nuget package:
"[Windows installer] is not the general recommended method of using Npgsql - always install via Nuget if possible"
http://www.npgsql.org/doc/index.html#gac-installation

@andresnava : Thanks for your contribution to the Azure documentation! The author, @jasonwhowell, has been notified to review your proposed change.

#sign-off


Initialization error: "Sentence root is not a be-verb"

I'm getting this error when trying to run Whoami:
whoami$ python scripts/run.py
Loading spaCy
Done loading
from whoami.query import get_assertion_definitions, get_question_definitions
from whoami.query import get_assertion_definitions, get_question_definitions []
ERROR:root:Sentence root is not a be-verb
Traceback (most recent call last):
  File "scripts/run.py", line 45, in <module>
    entry, tree = get_assertion_definitions(sentence, subject=synonyms, get_rep=True)
  File "build/bdist.linux-x86_64/egg/whoami/query.py", line 43, in get_assertion_definitions
    entry = extract_assertion(assertion, subject=subject)
  File "build/bdist.linux-x86_64/egg/whoami/defextract.py", line 171, in extract_assertion
    raise ParseError('Sentence root is not a be-verb')
ParseError: Sentence root is not a be-verb

Note that the error occurs on initialization, before trying to analyze any sentences.  Does Whoami try to analyze sentences as part of initialization?
The error "Sentence root is not a be-verb" would be appropriate if we were trying to analyze a sentence of the wrong form, e.g., "Callisto orbits around Jupiter" rather than "Callisto is a moon".  Although most Wikipedia articles' first sentences are of the form "article is/are/was/were ...", some are not, e.g., the (trimmed) first sentence for Polis is "Polis, literally means city in Greek."  (The bogus comma after Polis is sic.)  So the error may occur legitimately.  But not during initialization!

Looking at the latest build of the backend and the associated logs, I see that there were about 663,243 cases of raised ParseErrors because of the sentence root not being a be-verb. This is about 10% of articles which are not disambigs or redirects.
There was an issue with build_types.py which uses whoami in order to create types tables for the backend, in which these errors were preventing updates to the table.
There was another issue where the first paragraph was an empty string, caused by a number of articles having disambiguation statements before the first "real" paragraph.
Both of these issues are being addressed through a PR in WikipediaBase.

@sfelshin, I think this is a user error.  Where in the documentation does it say to run
from whoami.query import get_assertion_definitions, get_question_definitions

?
From what I can see, your input statement is not needed.  Whoami is trying to analyze this import as a sentence, and naturally giving an error when it tries to parse it.  The script already performs this import, so the user doesn't need to worry about it.  A working whoami session looks like this:
python scripts/run.py
Loading spaCy
Done loading
Callisto is a moon
Callisto is a moon []
['moon']
[subject: Callisto [def: moon]]

Unrelatedly, this script is still in python2.

@sfelshin, I think this is a user error.  Where in the documentation does it say to run
from whoami.query import get_assertion_definitions, get_question_definitions

@hanryhu, it says that under Usage:

Example:
>>> from whoami.query import get_assertion_definitions, get_question_definitions

What it does not say is to run python as
$ python scripts/run.py

In fact, it doesn't say anything at all about how to enter python, which is a flaw in the README. To be honest, I'm not sure where I got $ python scripts/run.py from although there is an old Slack post from Pond from Jan 17, 2018 that said:

@Steph If all you need is to be able to play with whoami, I find script/run.py pretty sufficient

I see that if I do
$ python
from whoami.query import get_assertion_definitions, get_question_definitions

I can then run whoami on sentences.
So, please take this issue as a request to clarify the README and to take a look at run.py to see if it provides value, and either fix it or remove it accordingly.
As for your point about python2, please note that we updated the WikipediaBase installation instructions (in https://github.com/infolab-csail/WikipediaBase/pull/441, still not merged) with specialized instructions for python 3.  Either whoami should get the same update or we should Do Something to make us not need the specialized instructions.

As for your point about python2, please note that we updated the WikipediaBase installation instructions (in infolab-csail/WikipediaBase#441, still not merged) with specialized instructions for python 3. Either whoami should get the same update or we should Do Something to make us not need the specialized instructions.

@sfelshin , I don't see any updates related to python 3 in that PR.  There is an update to the wikidata README, but it doesn't look related to python 3.  Did you mean https://github.com/infolab-csail/WikipediaBase/pull/386, which updates the README with extra information on running python 3 in emacs?

@hanryhu, neither of those, and I'm not sure which PR I meant. :open_mouth: But note that the same changes were made in a different README.md in https://github.com/infolab-csail/annotation-tool/pull/23/files.

@sfelshin Looks like the change in that README doesn't need to be ported because in the whoami README, we simply say "use a virtual environment" without going into python version-specific details.

Closing this issue because it is a red-herring for https://github.com/infolab-csail/whoami/issues/118.

@sfelshin Looks like the change in that README doesn't need to be ported because in the whoami README, we simply say "use a virtual environment" without going into python version-specific details.

@hanryhu, my point was that if you just say mkvirtualenv, you won't get a Python 3 virtualenv.  You have to explicitly ask for a Python 3 virtualenv on the command line.  If your point is that people who use Python 3 should be expected to know they have to specify the version on the command line without being told, then okay ... but I will note that some non-python people (like me 😞) may follow installation instructions pretty blindly.


Failed to save 'testvsc.rpgle': Unable to write file ....

I have a "old" fix format RPGLE program when I edit the source in VS Code I get an error message "Failed to save 'testvsc.rpgle': Unable to write file 'member:/ROLAND/qrpglesrc/testvsc.rpgle' (QSYSPRT   *LIBL)". I have looked to see if there were previous reports, the closest I found is #314 , however my error happen with the hex x'22' value in front of the comment lines. When I remove those hex values I do not get the error. I am not allowed to remove these hex values, so I need to know is there a way to get around the problem.
The funny thing is that when I try to recreate the problem, if the number of source lines are less than 1000, the error does not occur, if more than 1000, the error message occurs

⚠ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠

Context
Version

Code for IBM i version
1.9.1

Visual Studio Code version
1.78.2

Operating System
win32_x64

Active extensions
CL (vscode-clle): 1.1.0
COBOL (cobol): 9.5.6
Cloak (vscode-cloak): 0.5.0
Code Coverage for IBM i (code-coverage-ibmi): 0.1.7
Code GPT (dscodegpt): 2.1.10
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.3.1
Db2 for IBM i (vscode-db2i): 0.2.11
ESLint (vscode-eslint): 2.4.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.11.0
Extension Authoring (extension-editing): 1.0.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
Git Project Manager (git-project-manager): 1.8.2
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
GitHub Pull Requests and Issues (vscode-pull-request-github): 0.64.0
GitLens — Git supercharged (gitlens): 13.6.0
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.5
JSON Language Features (json-language-features): 1.0.0
Live Share (vsliveshare): 1.0.5864
Markdown Language Features (markdown-language-features): 1.0.0
Merge Conflict (merge-conflict): 1.0.0
Microsoft Account (microsoft-authentication): 0.0.1
Microsoft Edge Tools for VS Code (vscode-edge-devtools): 2.1.1
NPM support for VS Code (npm): 1.0.1
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Path Intellisense (path-intellisense): 2.8.4
RPGLE (vscode-rpgle): 0.19.2
TODO Highlight (vscode-todo-highlight): 1.0.5
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
WSL: Recommender (remote-wsl-recommender): 0.0.19
json (json): 2.0.2
vscode-icons (vscode-icons): 12.4.0
vscode-json (vscode-json): 1.5.2

Remote system

Setting
Value

IBM i OS
V7R4M0

Tech Refresh
7

CCSID
37

SQL
Enabled

Source dates
Enabled

Enabled features

/QOpenSys/pkgs/bin
/usr/bin

/QSYS.LIB
/QIBM/ProdData/IBMiDebugService/bin

bash
attr
ROLANDVSC.GETNEWLIBL
QZDFMDB2.PGM
startDebugService.sh

chsh
iconv

git
setccsid

grep

ls

md5sum

sort

stat

tar

tn5250

Shell env
BUILDLIB=LSUTILSDEV
CURLIB=LSUTILSDEV
HOME=/home/ROLAN
LIBLS=QDEVTOOLS  xxxxxxxxxxxx QTEMP
LOGIN=rolan
LOGNAME=rolan
MAIL=/var/spool/mail/rolan
OLDPWD=/home/ROLAN
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/ROLAN
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=
SSH_CONNECTION=
TZ=<SAST>-2
USER=rolan
USERNAME=rolan
_=/QOpenSys/usr/bin/env

Variants
{
  "american": "#@$",
  "local": "#@$"
}

Errors
[
  {
    "command": "/QOpenSys/usr/bin/qsh",
    "code": 1,
    "stderr": "CPD4090:  Printer device PRT01 not found. Output queue changed to QPRINT in library QGPL.\nCPF0820:  Program CLNTMPVSC not created.\nCPC2206:  Ownership of object QZSHSYSTEM in QTEMP type *USRSPC changed.",
    "cwd": "/home/ROLAN"
  },
  {
    "command": "system \"QSYS/RUNSQLSTM SRCSTMF('/tmp/vscodetemp-O_Ev0AmLvr') COMMIT(*NONE) NAMING(*SQL)\"",
    "code": 255,
    "stderr": "QSYSPRT   *LIBL",
    "cwd": "/home/ROLAN"
  },
  {
    "command": "system \"QSYS/RUNSQLSTM SRCSTMF('/tmp/vscodetemp-O_Ev0AmLvr') COMMIT(*NONE) NAMING(*SQL)\"",
    "code": 255,
    "stderr": "QSYSPRT   *LIBL",
    "cwd": "/home/ROLAN"
  }
]

@RolandStrauss

however my error happen with the hex x'22' value in front of the comment lines.

Are you able to share a snippet of what this might look like?

Hi Liam,
yes, I am attaching a word document with the snippets and the issue. I have also tried to describe the problem. I hope it helps. I have obfuscated the code lines that are sensitive.
LSPS-1562 POE.docx

Hi Liam,
the show Seu Colors is ticket

I have added a Word doc containing the complete output after the save as requested. I only removed the actual program code for IP privacy reasons
LSPS-1562 Code for IBM I channel output.docx

@worksofliam ,
Thank you for your patience and understanding. I apologize for the delay in getting back to you, as I have been dealing with some production issues. I am currently working on creating a sample of the program source code that is causing the problem, without disclosing the actual code. I will upload it as soon as I finish it.

@worksofliam ,
Sorry for responding only now, I created a mock source of the program causing the issue, it now does not contain any code that could identify our clients and processes. Even after scrubbing all the code out, it still fails.  I am attaching a .txt file with the log right after I get the "Failed to save..." message. I hope the .txt files helps.
OUTPUT - Before Error (Code 4 IBMi).txt
OUTPUT - After Error (Code 4 IBMi).txt

For my own records, here is the spoolfile from the file trying to be saved
spoolfile.txt

@RolandStrauss Is it possible you'd be able to share

the file here as well so we can test the content
the record length of the source file
the ccsid of the source file

@worksofliam I am attaching the source file here (I ctrl+c in VS Code and ctrl+v into the file), I did not paste the source as it is thousands of lines long. If I look at the actual source (hex) on the IBMi the � is x'22'
I changed the extension from .sqlrpgle to .txt
LSPS-1562b.TXT

@worksofliam
I have looked at the vscodetemp-o_VPVx6BHy in folder /tmp, I see there is 2 (two) insert statements, the first insert statement "ends" at line 2580 of the source and the second insert statement starts from the source line 2581. This is exactly where the source "breaks", when I receive the "Failed to save" message. The lines from the second insert is just missing in the VSCODE editor, but the source on IBMi is "gone".
I hope this helps a little bit more.
I have attached the temp file below, which contains the SQL inserts
vscodetemp-O_VPVx6BHy.txt

@RolandStrauss thanks for sharing! I promise to take a look this week. Sorry, very busy week last week and some time off.

@worksofliam
No problem, I know you are extremely busy, so I am just trying to give you as much information as I can, to try and save you some time. It is cool whenever you get to it. I really appreciate what you are doing for the IBMi community

@RolandStrauss Some progress has been made!
My setup: Source dates enabled, SEU colours enabled

Code example
     H OPTION(*SRCSTMT:*NODEBUGIO)
     H DATFMT(*ISO)
     H DATEDIT(*YMD)
     H TIMFMT(*ISO)
     �*

Spool file
      1 '2F')),(4, 230628, translate('     H TIMFMT(*ISO)', x'25', x'2F')),(5, 230628, t
      1 ranslate(UX'00200020002000200020FFFD002A', x'25', x'2F'));
                                 * * * * *  E N D  O F  S O U R C E  * * * * *
5770SS1 V7R3M0 160422               Run SQL Statements             VSCODETEMP                         06/28/23 13:24:31   PAGE     3
Record  *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8   SEQNBR  Last change
MSG ID  SEV  RECORD  TEXT
SQL0171  30       1  Position 1 Argument 1 of function TRANSLATE not valid.
                    Message Summary

So it looks like I can save the member if I turn SEU colours off. The mix of translate and the UX string do not go together.
@chrjorgensen Not asking you to solve this, but wanted you to see that RUNSQLSTM is converting strings with unicode characters to UX'....' before execution/

@RolandStrauss Can you confirm that the file does not save when you have SEU colours disabled?

@worksofliam Thank you for all your efforts, I have confirmed, the SEU colors are disabled, and I still receive the error and the file is not saved

@worksofliam & @chrjorgensen
After the V2.0.0 update the issue seems resolved, if we keep the Seu Colors ticked off. Thank you for the efforts, I believe we can close this issue

So it looks like I can save the member if I turn SEU colours off. The mix of translate and the UX string do not go together.
@chrjorgensen Not asking you to solve this, but wanted you to see that RUNSQLSTM is converting strings with unicode characters to UX'....' before execution.

The same error occurred to me today and this discussion helped me fixed it.
But, I have a concern and a query.

How can we make the Output channel content more readable for users? I think we can start by replacing '\n' with actual new-line. If this isn't a bad-idea, can someone direct me to the files that'd req change?
TRANSLATE(UX'FFFD', x'25', x'2F')...I've used 'X' before, but 'UX' is new for me. Is it for (VAR)GRAPHIC strings? I see they are already decoded as hex, can't X be used here?

I'm not sure about how it'll impact end-results, but the SQL ran successfully on replacing UX with X (as 'FFFD' is hex-code for the white color in SEU)

Thank you for your response @worksofliam.
For 1, I've no idea what all sources would req a change, nonetheless I'll document this as an issue.
For 2, I looked up on the web and find that you're right. Thanks for giving me a direction here.


[ADAM-1611] Extend pipe APIs to Java, Python, and R.

Resolves #1611. Depends on #1397. Adds a Java-friendly pipe method onto GenomicRDD, and     conversion functions in the org.bdgenomics.adam.api.java package. Simultaneously, we add a GenomicRDD base type in the R bindings. With these additions, we then add the pipe method to the GenomicRDD class that exists in both Python and R. The language bindings use reflection     to construct the in/out-formatters and conversion functions.
While I was at it, I also made the toDF implementation in R generic.

Coverage decreased (-1.2%) to 83.504% when pulling 1bedfe9b36fedb7de9ff2872c00a11980f69385e on fnothaft:issues/1611-pype into 76525367a2afa14cd282018d87015d1a9321f039 on bigdatagenomics:master.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2252/Build result: FAILURE[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1613/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains 3f2050816edc17afe4ae5547dc7165b042cbacc4 # timeout=10Checking out Revision 3f2050816edc17afe4ae5547dc7165b042cbacc4 (origin/pr/1613/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 3f2050816edc17afe4ae5547dc7165b042cbacc4First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,2.1.0,centosTriggering ADAM-prb ? 2.3.0,2.11,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.11,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.11,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result SUCCESSNotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Looks good to me, will review further after conflicts are resolved.

Rebased.

@heuermh btw the meat of the interesting stuff is the changes to GenomicRDD.

Coverage decreased (-0.7%) to 83.504% when pulling 74baf8db76c911bc7ac1fe024bd62397529f66ed on fnothaft:issues/1611-pype into 640c44bae1841217f981899c3a2b793c7ae06dcd on bigdatagenomics:master.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2261/Build result: FAILURE[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1613/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains a433274da4081f0cf4bbf0a5e05c1811c6c0e0a1 # timeout=10Checking out Revision a433274da4081f0cf4bbf0a5e05c1811c6c0e0a1 (origin/pr/1613/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f a433274da4081f0cf4bbf0a5e05c1811c6c0e0a1First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,2.1.0,centosTriggering ADAM-prb ? 2.3.0,2.11,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.10,2.1.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.11,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.11,2.1.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result SUCCESSNotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Jenkins, test this please.

Coverage decreased (-0.7%) to 83.504% when pulling 74baf8db76c911bc7ac1fe024bd62397529f66ed on fnothaft:issues/1611-pype into 640c44bae1841217f981899c3a2b793c7ae06dcd on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2268/
Test PASSed.

Thank you, @fnothaft!


hi, how can i confirm or find my  Forex broker's  'FIX_SERVER' address?

FIX_SERVER="h8.p.c-trader.cn"
FIX_BROKER="icmarkets"
FIX_LOGIN="3152339"
FIX_PASSWORD="393214"
FIX_CURRENCY="EUR"
hi, how can i confirm or find my  Forex broker's  'FIX_SERVER' address? Thanks

FIX_SERVER="h8.p.c-trader.cn" FIX_BROKER="icmarkets" FIX_LOGIN="3152339" FIX_PASSWORD="393214" FIX_CURRENCY="EUR"
hi, how can i confirm or find my Forex broker's 'FIX_SERVER' address? Thanks

the server is on the same place you get API dates from ctrader


System notifications not respecting language setting

Steps to Reproduce

Set the app language to something other than English
Receive a notification on your device (outside the app)
Observe the notification still being in English

Attachments

What platform(s) does this occur on?
Android
Device Info
Google Pixel 4a, Android 14
What version of the app are you using?
Build version: <IP_ADDRESS>1; Bundle info: 2a575ad (prod); Bundle date: 24112703; Platform: android; Platform version: 34
Additional Information
No response

I see this too on iOS.


[Feature Request] Add support for generating code from a single GenesisSettings asset

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When executing code generation currently all GenesisSettings assets are discovered and mapped over to generate each one's particular scope of assets. There is not currently a way to generate code for a single GenesisSetting asset.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I'd like to be able to generate code for a single GenesisSettings, via either right-clicking on the asset itself and selecting a context menu item or perhaps a top-level Editor menu item that is programmatically generated. It would also be useful in this context to select a top-level menu item that makes my active selection that asset; this is useful for GenesisSettings in sub-folders.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
There have been some situations where I'd like to generate code for one scope at a time, or I've forgotten where the asset is to configure it.

Included in release v1.2.0 https://github.com/jeffcampbellmakesgames/Genesis/releases/tag/upm%2Fv1.2.0


Assert error in Literals.ml when calling E with trivial goal

When calling zipperposition (main branch) with the following options:
./zipperposition.exe --try-e [e-prover binary] --e-call-point 0.0 -t 30
on the following tptp file:
tff(goal, conjecture, ($true)).
It returns an assert error line 283 in Literals.ml
It seems that this is due to the Literals.Conv.to_tst function being called on an empty clause in eprover_interface.ml (line 136).
To the best of my understanding, since we have an empty clause, the assert false could be replaced by a false TypedSTerm:
| [] -> TypedSTerm.app_builtin ~ty Builtin.false_ []
this has fixed the problem for me, but I'm wary of the assert false being there in order to signal a soundness issue.

Sorry for the late reaction. Could you create a pull request? I'd be happy to merge it.
I assume the assert false is there because an empty clause would usually terminate the prover immediately. With --e-call-point 0.0 that does not happen, which is not ideal but acceptable, I think. I don't think you can get this issue with values larger than 0.0, can you?

Yes, I can make a pull request.
That's exactly what happens, if the prover is allowed to run any amount of time, it terminates instantly.

fixed in #100


Minifying method calls on bare Numbers fails

Originally reported on Google Code with ID 324
Minify commit/version: http://tweakimg.net/files/upload/jsminplus-1.4.zip
PHP version: 5.5.9-1ubuntu4.4

What steps will reproduce the problem?
<?php
require_once('jsminplus.php');
var_dump(JSMinPlus::minify('(6).toString()'));

Expected output:
string(12) "(6).toString()"

Actual output:
string(12) "6.toString()"

Note:
Actual output yields the following error in Chrome:
Error: Line 1: Unexpected token ILLEGAL

Reported by corvass on 2014-10-29 12:14:25

I've just run into this issue with RGraph.line.js too:
(0).toFixed(
converts to
0.toFixed(
I'll report it to the RGraph team as well becuase it does look like some weird code but adding it here as it might help others when searching.

I've removed JSMin+. :person_frowning:

Here's the RGraph post for anyone interested:
http://www.rgraph.net/forum/message.html/conflict-with-rgraph-and-minify-20151011214210.html


SDK automation times out causing SDK azure-resource-manager-schemas to be stuck in queued state

Affected PR:
https://github.com/Azure/azure-rest-api-specs/pull/27391
Example timeout:
https://dev.azure.com/azure-sdk//internal/_build/results?buildId=3417900&view=logs&j=2b4a2910-f027-53b2-4397-cc9d62dced0f
##[error]The job running on agent azsdk-pool-mms-ubuntu-2004-general 32 ran longer than the maximum time of 120 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
Pool: [azsdk-pool-mms-ubuntu-2004-general](https://dev.azure.com/azure-sdk/590cfd2a-581c-4dcb-a12e-6568ce786175/_settings/agentqueues?poolId=&queueId=128)
Image: ubuntu-20.04
Agent: azsdk-pool-mms-ubuntu-2004-general 32
Started: Yesterday at 11:27 AM
Duration: 2h 0m 6s

Re-running the check resulted in the same symptoms.

It's time out issue. It appears to be a generation strategy issue which generates the schemas for all the tags defined in the readme.md.   For a big RP which contains big number of swaggers, the generation cannot be finished within 120 minutes.
This needs the help from ARM team for the script fix. +@anthony-c-martin

Another likely case:

https://github.com/Azure/azure-rest-api-specs/pull/27601/checks?check_run_id=21239433314
Teams discussion


[R] arrow_table: as.data.frame() sometimes returns a tbl and sometimes a data.frame

Describe the bug, including details regarding any error messages, version, and platform.
The documentation for arrow_table() says that you can call as.data.frame() on an arrow table object to convert it to a dataframe. It seems like the behaviour is inconsistent. Example:
> class(as.data.frame(arrow::arrow_table(name = "1", mtcars)))
[1] "tbl_df"     "tbl"        "data.frame"
> class(as.data.frame(arrow::arrow_table(mtcars, name = "1")))
[1] "data.frame"

I created the same arrow_table in both cases but only changed the order of the arguments, and it returned a different object type.
I would expect it to be base R dataframe since as.data.frame() is a generic from base R that is generally assumed to convert to actual data.frame objects, not to tibbles. Right now if I want to guarantee a base R data.frame, I need to do as.data.frame(as.data.frame(table)). I need to ocnvert it using the same function twice, which is extremely awkward and unintuitive. I strongly believe arrow should not conflate data.frame() with tbl_df, it can cause errors for users.
Component(s)
R

Thanks for reporting this, I agree it's not intended behaviour.  Looks like it's something to do with how metadata is handled, will have a closer look at this.


Organizational profile translation

Is it possible to enable translations for organizational profiles? Right now it's only possible to put in one language (or language neutral, but then the content's still in one language).
For a lot of organizations it would be helpful to have the translate options, UN agencies for example.

done


refactor: set openapi server url as close to startup as possible

Closes #248
Will conflict with https://github.com/go-fuego/fuego/pull/245 but it does solve the issue of creating the server too early so that code could be simplified now I believe.
Thanks

Updated with s.url() method.


Trainable parameters for static gen functions

They need to be added first to the IR (static_ir/) and tested there. Then, the static dsl parser needs to know about them (syntax @param should match the syntax used in the dynamic DSL).

Fixed in https://github.com/probcomp/Gen/pull/85


Consumption of Stored Procedures/Server Side Function results

There is no reference to CALL statements in the SPI.  How is it supported?

Care to elaborate on what you mean with "reference to CALL statements"?
R2DBC SPI provides a textual (SQL) interface to databases where the actual statement is sent to the database as-is without further rewrite. That means that you invoke stored procedures/server-side functions through the R2DBC SPI the same way as you would do this with any other command-line based interface.
For SQL Server that is EXECUTE <store-procedure-name> [args], for Postgres you can either CALL <name> ( [ argument ] [, ...] ) or SELECT <function-name>([arguments]).
The only missing bit is the declaration of parameter direction along their out-type which is going to be addressed with #160.

Sorry for not elaborating.
When you call a stored-procedure on the database server, it can return result-sets and also values for the out parameters and in-out parameters. The number of result-sets returned can be more than one. Also the stored-procedure may just do some updates and return nothing.
This differs from the SELECT query where only one result-set is returned. And no out parameters.
So I am not clear on how to use the same mechanism used for SELECT query for the CALL Stored-Procedure as well.
Below are some reference to JDBC on how stored procedures are called and return values are retrieved.
https://www.tutorialspoint.com/how-to-call-a-stored-procedure-that-returns-output-parameters-using-jdbc-program
https://www.tutorialspoint.com/how-to-retrieve-multiple-resultsets-from-a-stored-procedure-using-a-jdbc-program
Hope it helps.
Thanks.

Thanks for the insight. So multiple resultsets are possible as Statement.execute() returns a Publisher<Result> which may emit 0..N Result objects. So what's really left is consumption of out parameters.
We want to do something about out parameter consumption while not going into the way of regular result consumption, which reflects the majority of use-cases.
Technically speaking, drivers could map out parameters to a Row (e.g. Row.get(0) for the first out parameter). I think Postgres does already this.
In any case, we're happy to discuss and review proposals on how out parameters could be consumed in a standard way.

Fixed via #218


CLI output tweaks

I made this change in #1556 to make console clear work better on Windows. However I now discovered this has a significant downside on OS X: now if you first have a bunch of errors, scroll down, and then a successful run, scrolling up brings a confusing mixed view:

This change just reverts my tweak and makes it the way it has been before, with clear boundaries between the test runs in the scroll history:

The second commit adds a newline before the test summary.
This makes it more clearly separated from the log.
Before:

After:

Hmm. Looking at the snapshots, it's unfortunate there's an extra newline when there is an error at the end, but no newline if it is success.

So, ideally, this needs more work.
I want there to always be consistent spacing between last result, and "Test Summary", regardless of whether the last test failed or succeeded.

Extracted first change in #1596.


[formrecognizer] merge canary/prod pipelines into same pipeline

See conversation

Ben seems to be working on this, .NET currently supports this in their "weekly" pipeline. Reach out to him to see if we can get this working in python.

Ben seems to be working on this, .NET currently supports this in their "weekly" pipeline. Reach out to him to see if we can get this working in python.


async send without await

Webex Bot version: latest pip
Python version: 3.8
Operating System: Windows and docker

Description
*****\site-packages\webex_bot\websockets\webex_websocket_client.py:100: RuntimeWarning: coroutine 'WebSocketCommonProtocol.send' was never awaited
  self.websocket.send(json.dumps(ack_message))

What I Did
Just starting the bot
It's just a warning, so I guess just adding 'await' should fix it

Fixed in v0.2.20


RC test: Gravity Force Lab 2.2.0-rc.2

@emily-phet @terracoda @jessegreenberg @arouinfar @kathy-phet @samreid @chrisklus, gravity-force-lab/2.2.0-rc.2 is ready for RC testing.
Document issues in https://github.com/phetsims/gravity-force-lab/issues and link to this issue.
This simulation is outfitted with:

All PhET-iO featured, including a designed api
Sound
Interactive Descriptions (alternative input and auditory descriptions)
Gesture Accessibility with support for mobile iOS

Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Check this LoL spreadsheet and notify AR or AM if it not there.
If this is rc.2 please do a memory test.
When making an issue, check to see if it was in a previously published version
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.

Issues to Verify

[x] https://github.com/phetsims/studio/issues/94
[x] https://github.com/phetsims/phet-io-wrappers/issues/319
[x] https://github.com/phetsims/balancing-act/issues/111
[x] https://github.com/phetsims/studio/issues/92
[x] https://github.com/phetsims/studio/issues/19
[x] https://github.com/phetsims/phet-io-wrappers/issues/321
[x] https://github.com/phetsims/gravity-force-lab/issues/248
[x] https://github.com/phetsims/gravity-force-lab/issues/246
[x] https://github.com/phetsims/gravity-force-lab/issues/245
[x] https://github.com/phetsims/gravity-force-lab/issues/244
[x] https://github.com/phetsims/gravity-force-lab/issues/242
[x] https://github.com/phetsims/gravity-force-lab/issues/240
[x] https://github.com/phetsims/gravity-force-lab/issues/100
[ ] https://github.com/phetsims/gravity-force-lab/issues/180

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

PhET-iO RC Test

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Please at least load all wrappers except studio in the wrapper suite with internet explorer.
make sure to do a complete metacog recording/playback test. Ask @zepumph if you need help. (this doesn't need to be done as much this time around. Make sure to do a test, and any others relating to issues to verify)

Link(s)

Wrapper Index
Test Matrix

Accessibility (a11y) RC Test

What to Test

Specific instructions can be found below.
Make sure the a11y feature doesn't negatively affect the sim in any way.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Issues to Verify

[x] Might be an issue with the radio button group

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)

a11y View
Simulation
Test Matrix

Screen Readers
This sim supports screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to screen readers. If you simply need a refresher on screen readers, please consult the QA Book, which should have all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

[x] Windows 10 + Latest Chrome + Latest JAWS
[x] Windows 10 + Latest Firefox + Latest NVDA
[x] macOS + Safari + VoiceOver
[x] iOS + Safari + VoiceOver (Please test this! Especially with the Ruler interaction)

Critical Screen Reader Information
We are tracking known screen reader bugs in this Google Document. If you find a screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a screen reader.
Final Requests

[x] If this sim is in this list, make an issue in website to ask if PhET research page links need updating. Please assign to @terracoda and @emily-phet.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

@KatieWoe priority supersedes #470

@zepumph I noticed that you can drag the ruler from behind the slider boxes. Doesn't cause any problems and I don't think it needs anything done, but if you disagree and want an issue, let me know.

That seems like a bug, and an issue would be nice here.

QA is done

I still don't see https://github.com/phetsims/balancing-act/issues/111 checked off, did you get to it? Should I reassign it to someone?

Sorry, I thought one of my workiers was looking at it, so I passed it over. I'll check quick.

Done

Reopening for metacog

@samreid and I don't think that metacog testing is necessary for this second RC. We did a lot of metacog testing last RC, and the only issues that came from that were those that were general record/playback issues and could be confirmed from localFile recording.

Alright we are ready for a third rc/spot-check. I will go ahead and close this and create a new RC.