mriqc bare metal install - skullstrip fails

I have a bare metal install of mriqc. I do not think there is an issue related to any of the pre req packages as the checks for those packages run fine. The error I always get is related skullstrip failing to run on the host.
2017-12-08 10:30:52,391 workflow:WARNING [Node] Exception "workflow_enumerator.anatMRIQCT1w.AFNISkullStripWorkflow.skullstrip" (/gpfs/group/sjw42/default/freesurfer_subjects/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file..gpfs..group..sjw42..default..freesurfer_subjects..ds001..sub-16..anat..sub-16_T1w.nii.gz/skullstrip)
2017-12-08 10:30:54,054 workflow:ERROR Node skullstrip.a15 failed to run on host comp-ic-0016.aci.ics.psu.edu.
2017-12-08 10:30:54,054 workflow:ERROR Saving crash info to /gpfs/group/sjw42/default/freesurfer_subjects/out/logs/crash-20171208-103054-vus133-skullstrip.a15-2e72625e-1de4-432d-aac5-50799a29a0d1.txt
I'm not sure what the cause could be. Please let me know if you require any additional information. I'm running python 3.6, and the latest versions of all the packages specified on the bare metal install page.
Thank you.

Could you share the content of /gpfs/group/sjw42/default/freesurfer_subjects/out/logs/crash-20171208-103054-vus133-skullstrip.a15-2e72625e-1de4-432d-aac5-50799a29a0d1.txt ?

Hi chrisfilo,
The content is:
Node: workflow_enumerator.anatMRIQCT1w.AFNISkullStripWorkflow.skullstrip
Working directory: /gpfs/group/sjw42/default/freesurfer_subjects/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file..gpfs..group..sjw42..default..freesurfer_subjects..ds001..sub-16..anat..sub-16_T1w.nii.gz/skullstrip
Node inputs:
args =
environ = {}
ignore_exception = False
in_file = /gpfs/group/sjw42/default/freesurfer_subjects/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file..gpfs..group..sjw42..default..freesurfer_subjects..ds001..sub-16..anat..sub-16_T1w.nii.gz/inu_n4/sub-16_T1w_conformed_corrected.nii.gz
num_threads = 1
out_file =
outputtype = NIFTI_GZ
terminal_output =
Traceback (most recent call last):
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 62, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 404, in run
self._run_interface(execute=True)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 508, in _run_interface
return self._run_command(execute)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 639, in _run_command
result = self._interface.run()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 459, in run
env['DISPLAY'] = config.get_display()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py", line 286, in get_display
ndisp = int(sysdisplay.split(':')[-1])
ValueError: invalid literal for int() with base 10: '1000.0'

Thanks. What is the DISPLAY environment variable set to in the Shell you
are running mriqc from?
Best,
Chris
On Dec 8, 2017 7:57 AM, "isLitt"<EMAIL_ADDRESS>wrote:

Hi chrisfilo,
The content is:
Node: workflow_enumerator.anatMRIQCT1w.AFNISkullStripWorkflow.skullstrip
Working directory: /gpfs/group/sjw42/default/freesurfer_subjects/work/
workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file
..gpfs..group..sjw42..default..freesurfer_subjects..ds001..
sub-16..anat..sub-16_T1w.nii.gz/skullstrip
Node inputs:
args =
environ = {}
ignore_exception = False
in_file = /gpfs/group/sjw42/default/freesurfer_subjects/work/
workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file
..gpfs..group..sjw42..default..freesurfer_subjects..ds001..
sub-16..anat..sub-16_T1w.nii.gz/inu_n4/sub-16_T1w_
conformed_corrected.nii.gz
num_threads = 1
out_file =
outputtype = NIFTI_GZ
terminal_output =
Traceback (most recent call last):
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/
pipeline/plugins/multiproc.py", line 62, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 404, in run
self._run_interface(execute=True)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 508, in _run_interface
return self._run_command(execute)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 639, in _run_command
result = self._interface.run()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py",
line 459, in run
env['DISPLAY'] = config.get_display()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py",
line 286, in get_display
ndisp = int(sysdisplay.split(':')[-1])
ValueError: invalid literal for int() with base 10: '1000.0'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/issues/672#issuecomment-350298626,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkpxfplkFNQx0n4XR7pMeXIm_3R39Xks5s-VxmgaJpZM4Q7Qtl
.

Hi Chris,
It is <IP_ADDRESS>:1000.0
Could that be the issue?

Yes - could you try unsetting it?
Best,
Chris
On Fri, Dec 8, 2017 at 8:22 AM, isLitt<EMAIL_ADDRESS>wrote:

Hi Chris,
It is <IP_ADDRESS>:1000.0
Could that be the issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/issues/672#issuecomment-350305320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkpyiXm8g4Gw4g7z7HesUy9xsqgVKVks5s-WJDgaJpZM4Q7Qtl
.

Hi Chris,
When I do that I get a bunch of errors that look like this with different skullstrip node numbers.
2017-12-08 11:30:38,780 workflow:ERROR Node skullstrip.a15 failed to run on host comp-ic-0016.aci.ics.psu.edu.
2017-12-08 11:30:38,781 workflow:ERROR Saving crash info to /gpfs/group/sjw42/default/freesurfer_subjects/out/logs/crash-20171208-113038-vus133-skullstrip.a15-8de98503-220b-4831-bd48-706cba4c988b.txt
Traceback (most recent call last):
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 62, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 404, in run
self._run_interface(execute=True)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 508, in _run_interface
return self._run_command(execute)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 639, in _run_command
result = self._interface.run()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 459, in run
env['DISPLAY'] = config.get_display()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py", line 309, in get_display
self._display = Xvfb(nolisten='tcp')
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/xvfbwrapper.py", line 41, in init
raise EnvironmentError(msg)
OSError: Can not find Xvfb. Please install it and try again.

This is the crash log output:
Node: workflow_enumerator.anatMRIQCT1w.AFNISkullStripWorkflow.skullstrip
Working directory: /gpfs/group/sjw42/default/freesurfer_subjects/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file..gpfs..group..sjw42..default..freesurfer_subjects..ds001..sub-16..anat..sub-16_T1w.nii.gz/skullstrip
Node inputs:
args =
environ = {}
ignore_exception = False
in_file = /gpfs/group/sjw42/default/freesurfer_subjects/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file..gpfs..group..sjw42..default..freesurfer_subjects..ds001..sub-16..anat..sub-16_T1w.nii.gz/inu_n4/sub-16_T1w_conformed_corrected.nii.gz
num_threads = 1
out_file =
outputtype = NIFTI_GZ
terminal_output =
Traceback (most recent call last):
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 62, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 404, in run
self._run_interface(execute=True)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 508, in _run_interface
return self._run_command(execute)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 639, in _run_command
result = self._interface.run()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 459, in run
env['DISPLAY'] = config.get_display()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py", line 309, in get_display
self._display = Xvfb(nolisten='tcp')
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/build/lib/python3.6/site-packages/xvfbwrapper.py", line 41, in init
raise EnvironmentError(msg)
OSError: Can not find Xvfb. Please install it and try again.

You would need to install Xvfb for this to work. Alternatively you can try
setting DISPLAY to "<IP_ADDRESS>:1000".
To avoid all such headache I really recommend using Singularity or Docker.
Best,
Chris
On Fri, Dec 8, 2017 at 8:34 AM, isLitt<EMAIL_ADDRESS>wrote:

This is the crash log output:
Node: workflow_enumerator.anatMRIQCT1w.AFNISkullStripWorkflow.skullstrip
Working directory: /gpfs/group/sjw42/default/freesurfer_subjects/work/
workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file
..gpfs..group..sjw42..default..freesurfer_subjects..ds001..
sub-16..anat..sub-16_T1w.nii.gz/skullstrip
Node inputs:
args =
environ = {}
ignore_exception = False
in_file = /gpfs/group/sjw42/default/freesurfer_subjects/work/
workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/in_file
..gpfs..group..sjw42..default..freesurfer_subjects..ds001..
sub-16..anat..sub-16_T1w.nii.gz/inu_n4/sub-16_T1w_
conformed_corrected.nii.gz
num_threads = 1
out_file =
outputtype = NIFTI_GZ
terminal_output =
Traceback (most recent call last):
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/
pipeline/plugins/multiproc.py", line 62, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 404, in run
self._run_interface(execute=True)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 508, in _run_interface
return self._run_command(execute)
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py",
line 639, in _run_command
result = self._interface.run()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py",
line 459, in run
env['DISPLAY'] = config.get_display()
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py",
line 309, in get_display
self._display = Xvfb(nolisten='tcp')
File "/gpfs/group/sjw42/default/sjw42_collab/sw/Python-3.6.3/
build/lib/python3.6/site-packages/xvfbwrapper.py", line 41, in init
raise EnvironmentError(msg)
OSError: Can not find Xvfb. Please install it and try again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/issues/672#issuecomment-350308511,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp7E6uBMlKC4j5Qmeh_CWw0LwCXOvks5s-WUwgaJpZM4Q7Qtl
.

Hi Chris,
Setting DISPLAY to "<IP_ADDRESS>:1000" seems to have fixed the problem.
Thank you very much!


Fix build and overlay position

@PWKad Seeing as you're in the mood for merging... I have a couple of slight fixes that might interest you.  They might be things you've picked up on your own, but the build fix is really annoying - took me a wee while to figure out what was happening.

Just got finished merging and re-basing so after I push it out here in a minute I'll ask you to rebase these changes on top :)

ok, sounds good.

Merged.


Undefined name 'xdoc' in ubelt/util_colors.py

flake8 testing of https://github.com/Erotemic/ubelt on Python 3.6.3
$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
./ubelt/util_colors.py:107:5: F821 undefined name 'xdoc'
    xdoc.doctest_module()
    ^
1     F821 undefined name 'xdoc'
1

Thanks for raising the issue! This was a holdout from refactoring the old internal ubelt doctesting harness into the new xdoctest module. I just fixed it with a hotfix in the master branch.


GROOVY-10925: @TupleConstructor namedVariant breaks on setting privat…

…e final fields in constructor

Codecov Report

Merging #1854 (99d08c6) into GROOVY_4_0_X (3bfef49) will decrease coverage by 0.0089%.
The diff coverage is 100.0000%.

@@                  Coverage Diff                   @@
##             GROOVY_4_0_X      #1854        +/-   ##
======================================================
- Coverage         67.8204%   67.8115%   -0.0089%
+ Complexity          28151      28145         -6
======================================================
  Files                1425       1425
  Lines              112388     112385         -3
  Branches            19235      19233         -2
======================================================
- Hits                76222      76210        -12
- Misses              29657      29666         +9
  Partials             6509       6509

Impacted Files
Coverage Δ

...vy/transform/options/ImmutablePropertyHandler.java
77.0270% <ø> (-4.3063%)
:arrow_down:

...s/groovy/transform/ImmutableASTTransformation.java
67.0157% <ø> (+0.3490%)
:arrow_up:

...y/transform/TupleConstructorASTTransformation.java
85.5000% <100.0000%> (ø)

...in/java/groovy/lang/ReadOnlyPropertyException.java
50.0000% <0.0000%> (-50.0000%)
:arrow_down:

...ovy/transform/MapConstructorASTTransformation.java
80.9091% <0.0000%> (-0.9091%)
:arrow_down:

...org/codehaus/groovy/vmplugin/v8/IndyInterface.java
85.2459% <0.0000%> (-0.8197%)
:arrow_down:

...va/org/codehaus/groovy/ast/tools/GeneralUtils.java
83.5351% <0.0000%> (-0.4843%)
:arrow_down:

...ncurrentlinkedhashmap/ConcurrentLinkedHashMap.java
44.8617% <0.0000%> (-0.1976%)
:arrow_down:

...us/groovy/transform/AbstractASTTransformation.java
76.6169% <0.0000%> (+0.4975%)
:arrow_up:

... and 1 more

I'll close this and work on a more comprehensive PR (or two) to improve consistency in several places.


Join with fill('null') should not deadlock

I realize there is the following in https://docs.influxdata.com/kapacitor/v1.2/nodes/stats_node/:

WARNING: It is not recommended to join the stats stream with the original data stream. Since they operate on different clocks you could potentially create a deadlock. This is a limitation of the current implementation and may be removed in the future.

However it wasn't clear to me whether that also applied for joins with the .fill('null') chain method or not. I also wasn't able to find the github issue that tracked the fix either way.
Below is a TICKscript and write script that can reproduce the issue somewhat reliably on Kapacitor v1.2.1 (git:  4628bda2e3fbcc43df694707ec3f640f213cb0dc):
TICKscript:
var from = stream
    |from()
        .measurement('test')

var stats = from
    |stats(1s)

stats
    |join(from)
        .as('stats', 'from')
        .tolerance(1s)
        .fill('null')
    |log()

Write script:
#!/usr/bin/env bash
nanos=$(date +%s)000000000
curl -i -XPOST 'http://localhost:9092/write?db=test&rp=default' --data-binary "test f1=0,f2=\"v2\""
sleep 1s
for i in `seq 1 10`;do
    timestamp=$((nanos+i))
    curl -i -XPOST 'http://localhost:9092/write?db=test&rp=default' --data-binary "test f1=$i,f2=\"v2\" $timestamp"
done

The output before it deadlocks:
[httpd] ::1 - - [20/Apr/2017:21:46:49 -0700] "POST /write?db=test&rp=default HTTP/1.1" 204 0 "-" "curl/7.51.0" 88421c89-264d-11e7-83e3-000000000000 91
[bug:log6] 2017/04/20 21:46:49 I!  {"Name":"stats","Database":"","RetentionPolicy":"","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{},"Fields":{"from.emitted":null,"stats.emitted":0},"Time":"2017-04-21T04:46:47Z"}

[bug:log6] 2017/04/20 21:46:50 I!  {"Name":"stats","Database":"","RetentionPolicy":"","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{},"Fields":{"from.emitted":null,"stats.emitted":0},"Time":"2017-04-21T04:46:48Z"}

[bug:log6] 2017/04/20 21:46:51 I!  {"Name":"stats","Database":"","RetentionPolicy":"","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{},"Fields":{"from.emitted":null,"stats.emitted":0},"Time":"2017-04-21T04:46:49Z"}

[bug:log6] 2017/04/20 21:46:52 I!  {"Name":"stats","Database":"","RetentionPolicy":"","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{},"Fields":{"from.f1":0,"from.f2":"v2","stats.emitted":0},"Time":"2017-04-21T04:46:50Z"}

@jsotelo Unfortunately the warning applies to join with any of the options including fill.
What are you trying to do with the join? Maybe we can find another way to accomplish it.

@nathanielc We would like to satisfy all the points below:

Be alerted as soon as (within a second) the throughput of a stream is higher than a specific max count for a duration period (size of the sliding window)

For example, if my max is 3, my duration is 120 seconds and 4 messages are sent all within the first second, We'd like to be alerted immediately after the 4 point (as opposed to waiting the entire 120 seconds)

Along with the alert, pass along some of the fields or tags of the point (preferably the last in the window) that caused the alert.

For example, if a stream contains  "warnings" strings each tagged with the host they originated from, we would want to group by host and make sure the alert included which host exceeded the "max-throughput"

As soon as the sliding window sees less the max count, we would like to see an "ok" alert

For example, say the max count is 3, the window size is 5 seconds and a point is received within the first second then 3 more points are received at fourth second, We'd like to see a "critical" alert go out by the fifth second but then an "okay" alert go out by the sixth second, since the first point is now outside of the 5 second window

The approach we are trying to take is something like this (simplified for clarity):
var maxCount = 3
var periodSeconds = 5

var from = stream
    |from()
        .measurement('warning')
    |groupBy('host')

from
    |stats(1s)
    |derivative('emitted')
        .unit(1s)
        .nonNegative()
    |window()
        .periodCount(periodSeconds)
        .everyCount(1)
    |sum('emitted')
        .as('count')
    |join(from)
        .as('sum', 'from')
        .tolerance(1s)
        .fill('null')
    |default()
        .field('sum.count', -1)
        .field('from.host', '')
    |where(lambda: "sum.count" >= 0 AND "from.host" != '')
    |alert()
        .crit(lambda: "sum.count" > maxCount)
        .log('/tmp/alert.log')

Any help is appreciated, thanks!


definition for 'melanotic mass'

FBbt:00005064 'melanotic mass' has a large amount of curation, but no definition.
The related dpo term FBcv:0000446 'melanotic mass phenotype' has a comment saying:

Melanotic capsules are formed around foreign bodies in wild-type animals as part of the immune response, for example as a protection against parasitoid wasps. Some, but not all melanotic mass phenotypes involve ectopic activation of this immune response. While melanotic masses are commonly referred to as melanotic tumors in the historical literature, this is a misnomer as they are rarely neoplastic.

After looking at some other references too, I think a suitable definition would be something like:
"Dark melanin-containing mass that is formed  at a wound site in response to injury (Markus et al., 2005; Tang, 2009; Evans et al., 2022). Its formation is mainly mediated by hemocytes (Tang, 2009)." [FlyBase:FBrf0187734, FlyBase:FBrf0215359, FlyBase:FBrf0252938]

Are all melanotic masses formed in response to wounds? I am pretty sure I remember having some mutants that had them spontaneously.

The FBbt:00005064 definition looks good to me.
This made me question the definition of FBbt:00005064. Why does it say "in the absence of foreign bodies" if melanotic capsules are formed around foreign bodies (at least most of the times)?
Lastly, while you are at it, could you please consider removing  the "melanotic tumor" Related Synonym from FBbt:00005064 and the "melanotic 'tumor'" Exact Synonym from FBcv:0000446? Having those synonyms create a confusion when the comment states that FBcv:0000446 term shouldn't be referred to as melanotic tumors.
Thanks.


Add primary keys to tables to support PXC

Add primary keys to the token and setup tables.
Also update .gitignore for the imagelist.txt file that was added.

@richard-cox This passed the gate!


dApp keeps redirecting to splash screen after connecting

Steps to Reproduce

Pull the latest master as of 26/3/2020
Press connect

Expected Result

dApp connecting using my chosen MetaMask account or a dedicated Raiden account and then redirect to the transfer screen.

Actual Result

dApp connects and briefly displays the transfer screen before redirecting back to the splash screen.

Additional Infos (Optional)
Creating a completely fresh account did not help
Running npm ci did not help
Console displays:

Logs:
raiden_2020-03-26T09_41_03.178Z.log

@taleldayekh setLevel is called only in two places, and the most probably instance of this issue seems to be the getter for log in the Raiden public interface. This would only fail if something at initialization went wrong, and this error seems to be masking the actual issue. I'll make a PR to improve on this, please, keep the account & state triggering this issue around, so we can investigate.
Thanks for the report.

The other instance (matrix-js-sdk logger) would only happen if you're out of sync with raiden-ts's package.json, which requires matrix-js-sdk 5.1+, which changed the logger export there. Any chance of this being the case?

@taleldayekh can you try same account on #1245 , please?  The onlyraidenShutdown reason I get is providerAccountChanged when shifting between accounts but that is expected.

@nephix your error is specifically on state version=2, which is the WIP Receive branch. It means you tried to load the state you were testing on that branch, on master on on another branch. Notice our migration doesn't support downgrades, only ugprades, so state/account you used on that branch shouldn't be used on a previous branch or master, or you'll get these validation errors.

Yeah that's what I thought too


add PySocks to requirements.txt

Attempting to launch with "DMM HTTPS Proxy" set to a URL beginning with socks5:// returns the following error:
Traceback (most recent call last):
  File "launch.py", line 46, in thread
  File "launch.py", line 60, in launch
  File "lib\DGPSessionWrap.py", line 11, in read_cookies
  File "lib\DGPSessionV2.py", line 298, in read_cookies
  File "lib\DGPSessionV2.py", line 222, in login
  File "lib\DGPSessionV2.py", line 177, in get
  File "requests\sessions.py", line 600, in get
  File "requests\sessions.py", line 587, in request
  File "requests\sessions.py", line 701, in send
  File "requests\adapters.py", line 456, in send
  File "requests\adapters.py", line 352, in get_connection
  File "requests\adapters.py", line 217, in proxy_manager_for
  File "requests\adapters.py", line 62, in SOCKSProxyManager
requests.exceptions.InvalidSchema: Missing dependencies for SOCKS support.

Add PySocks as described by https://requests.readthedocs.io/en/latest/user/advanced/#socks (pip install requests[socks])

Thanks for sending the pull request.
I will review and release when I have time.


feat(besu): add prometheus exporter

Commit to be reviewed

feat(besu): prometheus exporter metrics integration
Primary Change
--------------

1. The besu ledger connector plugin now includes the prometheus metrics exporter integration
2. OpenAPI spec now has api endpoint for the getting the prometheus metrics

Refactorings that were also necessary to accomodate 1) and 2)
------------------------------------------------------------

3. GetPrometheusMetricsV1 class is created to handle the corresponding api endpoint
4. IPluginLedgerConnectorBesuOptions interface in PluginLedgerConnectorBesu class now has a prometheusExporter optional field
5. The PluginLedgerConnectorBesu class has relevant functions and codes to incorporate prometheus exporter
6. Added Readme.md on the prometheus exporter usage

Fixes #533

Signed-off-by: Jagpreet Singh Sasan<EMAIL_ADDRESS>

@jagpreetsinghsasan The GH Actions CI seems to be stuck on this one as well so you have a couple of options to try and kick it back into action

Push a dummy commit (that later you can and should squash back into the original one) and see if this re-triggers the CI run
If 1) fails then close this PR and open a brand new one with the exact same content
If 2) also fails then it's time to contact Github support, but I'm hoping 1 or 2 will fix it.

@jagpreetsinghsasan Please rebase this and then it's ready to go! :-)


Replace call to get user then id, with just id()

No need to retrieve the full user object to get the id from it as the auth guard interface $app['auth'] has a method for this: https://github.com/laravel/framework/blob/5.4/src/Illuminate/Contracts/Auth/Guard.php#L29

This unfortunately doesnt exist in all versions of laravel, so we'd want to feature detect this to avoid breaking existing behavior

This correct, this was implemented in Laravel 5.2 so might be better to leave it as is since the implementation in Laravel retrieves the full user object anyway.

https://github.com/laravel/framework/blob/5.4/src/Illuminate/Auth/SessionGuard.php#L200

Since this nice Laravel "sugar syntax" is not available in every Laravel version we support and internally Laravel does the same thing as we currently do, I am going to close this.


Update OWNERS

/hold

I need to verify whether we need to keep the component as a single word since the transition from BZ to Jira.

/unhold

/cherry-pick release-4.12


doesn't work with latest tinted-theming

Not sure what is going on here, but seems to be some changed standards and missing coordination between projects?

https://github.com/tinted-theming/tinted-foot/issues/8#issuecomment-2371141311

Not sure what is going on here

What exactly is the problem?
It seems that https://github.com/tinted-theming renamed some of their repositories. I will submit a Stylix PR for this.

they also:

changed data structure, see the config.yaml
YAML parser started failing on [aString] list

@nazarewk, I have not looked into this yet. Could you clarify what exactly is the problem with the current tinted-foot verision?

#572 has been merged; has this improved the situation?

#572 didn't change anything, but updating tinted-foot will result in:
trace: Warning (base16.nix): failed to parse YAML file without an IFD.
trace: Warning (base16.nix): A config.yaml does not follow base16 conventions or was incorrectly parsed.
Defaulting to an empty extension.
Please consult https://github.com/SenchoPens/base16.nix/tree/main#%EF%B8%8F-troubleshooting
trace: Warning (base16.nix): failed to parse YAML file without an IFD.
trace: Warning (base16.nix): A config.yaml does not follow base16 conventions or was incorrectly parsed.
Defaulting to an empty extension.
Please consult https://github.com/SenchoPens/base16.nix/tree/main#%EF%B8%8F-troubleshooting
base16-nix-parse-check> Running phase: checkPhase
base16-nix-parse-check> Output of "jd /nix/store/w0j2i02sfmpl19jmnprrd5ll4l068yj0-fromYAML /nix/store/nzxhrh19vbjzsnz1wb896w45y0wfdjnm-parsed-yaml-as-json":
base16-nix-parse-check> @ ["base16","supported-systems"]
base16-nix-parse-check> - ["base16"]
base16-nix-parse-check> + "[base16]"
base16-nix-parse-check> @ ["base24","supported-systems"]
base16-nix-parse-check> - ["base24"]
base16-nix-parse-check> + "[base24]"
base16-nix-parse-check> Error (base16.nix): /nix/store/rqh827dzqi5n11vwfv21gggwaaf24338-source/templates/config.yaml was parsed incorrectly during nix evaluation.
base16-nix-parse-check> Please consult https://github.com/SenchoPens/base16.nix/tree/main#%EF%B8%8F-troubleshooting
home-manager-path> created 4071 symlinks in user environment

updated stylix today and having the same issue with nord now with kitty and tmux

Is this caused by https://github.com/danth/stylix/pull/588?

updated stylix today and having the same issue with nord now with kitty and tmux

Is this caused by #588?

it seems. I reverted stylix to 63426a59e714c4389c5a8e559dee05a0087a3043 and I can complie

I am already looking into this. I will try to properly resolve this today.

I am already looking into this. I will try to properly resolve this today.

Feel free to test https://github.com/danth/stylix/pull/589 and leave a comment if it works.

Hello,
I have the same issue even on https://github.com/danth/stylix/commit/63426a59e714c4389c5a8e559dee05a0087a3043
However this is my first time using nixos, I might have done something wrong. This is how I declare it in flake.nix stylix.url = "github:danth/stylix?rev=63426a59e714c4389c5a8e559dee05a0087a3043";
And I try to use it simply by setting enable to true and give it an image

I am already looking into this. I will try to properly resolve this today.

Feel free to test #589 and leave a comment on whether it works.

I confirm it works


Fix: exit error when setting limit via cross-env

https://github.com/endel/increase-memory-limit/issues/11

Thanks a lot @toddb!


Add hdr as option to percentile function

Use case: Percentiles can be slow and elasticsearch's documentation suggest its possible to use HDR to decrease the time it takes to calculate a percentile.
Feature description:
It'd be helpful if we could specify the logic when using the percentile function, possibly by passing in a param? PERCENTILE(column, 0.95, 'hdr')
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-percentile-aggregation.html#_hdr_histogram

Both have trade-offs as the link you posted states.
We value this feature request, but as there is already a percentile implementation in place, we consider it as low priority.


[HUDI-6047] Clustering operation on consistent hashing index resulting in duplicate data

Change Logs
Following changes added

Hudi loads consistent hashing committed bucket metadata file on the basis of replace commit present on active timeline, but when replaced commit gets archived it falls back to default metadata file which result in data duplication.
Added patch for this bug https://issues.apache.org/jira/browse/HUDI-6047

Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
none
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Will raise a new PR found few issues, will fix those


Release 1.0.4 is not available on npm

npm still reports and installs 1.0.3 as latest release.

Published.

Thank you for letting me know!


[ci.yaml] xcode versions are not testable on presubmit

See https://github.com/flutter/engine/pull/30357 where the xcode parameter was rolled but the osx_sdk property was not changed.

Since this is the only place we have nested properties, I suspect it has to do with Cocoon's buildbucket RPCs and not playing nicely with the expected format
flutter {
  osx_sdk: 123
}

Orthogonal to this, we should remove the need for this property. All the properties should confirm to <String, String> so they can be directly mapped from the ci.yaml.

I started a chat in LUCI users - https://chat.google.com/room/AAAAXGgrwSo/aB8Zfm8kho4
I can't see why this is an issue in the Cocoon code, other than there may be some non-trivial way of sending recipe_module properties. Worst case, this may require some refactoring to use a recipe level property instead of the $ property.

@jmagman this should be testable now. Feel free to reopen if you run into issues.


Attributes not required

A reading of the schema seems to indicate that only the "Id" parameter is required and all others are optional.
Additionally, in the CT_NewClass there are 8 additional child elements listed that are missing from this page.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5b9899c3-e4cf-9f45-5a6c-d1f5d42911a3
Version Independent ID: 5b9899c3-e4cf-9f45-5a6c-d1f5d42911a3
Content: com4:Class (in InProcessServer) - Windows UWP applications
Content Source: winrt-related-src/schemas/appxpackage/uapmanifestschema/element-com4-inprocessserver-class.md
Product: uwp
Technology: winrt-reference
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

@TimMangan Thanks for catching this! Somehow I got turned around and treated the default for attributes as required instead of optional. I've fixed the attribute tables and added the missing child elements for all of the elements of type CT_NewClass.


[Feature Request] Show poll end time in timestamp

Is your feature request related to a problem? Please describe
Currently the poll timestamp doesn't do anything since the message has a timestamp.
Describe the solution you'd like
The timestamp should give the timestamp of when the poll will end.
Describe alternatives you've considered
N/A
Additional context
N/A

Note: Android client has a bug where timestamp will always show as "Today" for future times. The issue is currently marked wontfix and it is not likely to change. This should probably be accounted for and steps taken to mitigate - time would need to be shown somewhere in plaintext.


.NET Core 3.0 Preview8 IntelliSense (English)

These are the IntelliSense files obtained from the latest Docs repo Live build, generated for Preview8.
Some files are gone: Ahson and I investigated each one of them and all the removals seem to be expected.
The APIs did not disappear, they were moved to a different assembly.

One of the reasons why some files were gone is because this Live build was generated using the latest batch of reference assemblies that @safern sent to @mairaw. The previous batch was sent to the Docs team about a month ago, so the changes are expected.

Looking more closely, a lot of files seem to be getting removed now. Can you spot check a couple (maybe System.xml and System.Security.xml) and make sure those APIs still exist/are documented elsewhere? I remember we saw System.Xml.xml and found the documentation/types were already within System.Xml.XmlReaderWriter.xml, but I don't see that file here.


Copy enough code from Forest to sign a message

Implementing a Filecoin faucet requires signing messages. Forest has the code for signing messages but is not available as an independent crate.
We need:

forest_filecoin::key_management::keystore::KeyInfo
forest_filecoin::key_management::wallet::Key
crate::key_management::sign

Both SignatureType::Bls and SignatureType::Secp256k1 have to be supported.
Test by importing a key and signing a test message. The output should be identical to forest-wallet sign -m [MSG].

Does the code need to be copied? Could we re-use instead by adding forest-filecoin into the dependencies? This might require some visibility changes in the forest-filecoin crate, but otherwise should be feasible.

I'm fairly sure forest-filecoin doesn't compile to WASM. But splitting off smaller crates is certainly a future goal.

@lemmih Is this already done?

Done!


Communities

I mean this is building and testing correctly and this individual bits have all been reviewed, right? :D

You'd hope so...

I mean this is building and testing correctly and this individual bits have all been reviewed, right? :D

You'd hope so...


[WIP] Changes to prepare rhel (ppc64/le) and ubuntu(ppc64le) build machines

[WIP]
Changes to prepare rhel (ppc64/le) and ubuntu(ppc64le) build machines

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.

Created a rebase'd PR https://github.com/opscode-cookbooks/omnibus/pull/94


file transfer

How do i use the file transfer feature? I'm pretty sure it uses FTP but I cannot figure out how to get it working

It's not using FTP. Here are the important parts:

FileSplit class used to split files into 64kb parts and merge them again
Server-side FileManager class, only the server can initiate downloads or uploads.
Client-side FileManager class used to answer to file transfer requests


Polygon.to_mask includes an assert that may not be needed

🐛 Bug
Describe the bug
Polygon.to_mask has an assert in case it thinks that polygons overlap. This was triggered by my data, even though I wasn't needing to use the segmentation information/masks. It should't trigger an unrecoverable error in such a case.
Additional context
A simple fix:
def patch_to_mask(self, h, w):
        erle = self.to_erle(h=h, w=w)
        mask = mask_utils.decode(erle).sum(axis=-1)  # Sum is for unconnected polygons
        # assert mask.max() == 1, "Probable overlap in polygons"
        if mask.max() == 1:
            print("Probable overlap in polygons")
        return MaskArray(mask)
Polygon.to_mask = patch_to_mask

I'll be investigating this further, but I believe this assertion might be essential while training a segmentation model.
After all the model expects binary masks, the assert makes sure the mask only has 0's and 1's.
I believe you're using the coco parser? If so, and you want to train a model without segmentation masks, use the option mask=False

With #510 the way Polygon gets converted to masks changed so the assert is not there anymore


relaxed setting should also accept IP address

'relaxed' => ['localhost', '<IP_ADDRESS>'],
Calling from <IP_ADDRESS> throws 500 error.
I guess this config parameter only accepts names? In development LAN there's often no DNS...

Paste curl request and results here:
$ curl --include --ipv4 http://<IP_ADDRESS>
...

@tuupola  Ahhh! I did misunderstand the option: I thought I have to add the IP/name of the clients for which SSL is not required (which would make more sense IMHO).

To make my issue more clear: Maybe needs better description in the doc of how exactly the 'relaxes' property is treated.
I added the IP of the client from which I wanted to connect with plain text connection...

Improved the wording on the security section: https://github.com/tuupola/slim-jwt-auth/pull/241


AL Language Extension on macOS doesn't work

I installed VsCode and the VsCode Extension AL Language from Visual Studio Marketplace on macOS. When I try to publish my AL Solution I get the Error Message:

command 'al.resolveDebugCommand' not found

The current version is windows only. We still have a couple of wrinkles to iron out in the MacOS version.

With the AL Language Extension 0.11.14434 this error doesn't occurred anymore. In order to call the Pre-Compiler I change the extensionService.js:
        serverPath = path.join(serverPath, 'Microsoft.Dynamics.Nav.EditorServices.Host');
        //if (osHelpers_1.isWindows()) {
            serverPath += ".exe";
        //}
        return 'mono ' + serverPath;

Mono can't run the Pre-Compiler on macOS because of Windows API Dependencies of Microsoft.ApplicationInsights. You get this exception:
exception inside UnhandledException handler: The type initializer for 'Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces.Log.ProjectTelemetry' threw an exception.

[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces.Log.ProjectTelemetry' threw an exception. ---> System.TypeLoadException: Could not load type of field 'Microsoft.ApplicationInsights.Extensibility.Implementation.Platform.PlatformImplementation:CS$<>9__CachedAnonymousMethodDelegate1' (0) due to: Could not load file or assembly 'Windows, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:Windows, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null type:<unknown type> member:<none>
  at Microsoft.ApplicationInsights.TelemetryClient..ctor (Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration configuration) [0x00026] in <bfa6064e6ad94bacb5ae41e461d83c53>:0
  at Microsoft.Dynamics.Nav.Deployment.Telemetry.AppInsightsTelemetryService..ctor (System.String key) [0x00041] in <f2ab4875aab94c82a2c62df9de9111e8>:0
  at Microsoft.Dynamics.Nav.Deployment.Telemetry.TelemetryServiceFactory.CreateTelemetryService () [0x00000] in <f2ab4875aab94c82a2c62df9de9111e8>:0
  at Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces.Log.ProjectTelemetry..cctor () [0x0000a] in <f82446c53b354bcd8a35f2cf9da8840b>:0
   --- End of inner exception stack trace ---
  at Microsoft.Dynamics.Nav.EditorServices.Protocol.Utility.Logger.Write (System.Exception ex) [0x00000] in <1a4c005790b246afb00433e888ef2dcc>:0
  at Prod.EditorServices.Host.Program.CurrentDomain_UnhandledException (System.Object sender, System.UnhandledExceptionEventArgs e) [0x00006] in <a8d199f4ad044ba9884e635c1de864bb>:0

.NET Core would also be a possible, but I guess the Solution has to be compiled for .NET Core before.
Is there a Roadmap?

The currently released version is Windows only. We are working on a .net core version. We have it working (as shown on conferences), but we still need to finalise a number of thing before we can release it. Please be patient, we will get there.

Scott Hanselman had a nice Blog Entry yesterday about Writing smarter cross-platform .NET Core apps with the API Analyzer and Windows Compatibility Pack. He mentions even the .NET Portability Analyzer.


Not really an Issue

Describe the bug
Its in Fact a Question:
i have implemented this but in TypeScript and when implementing a component i connect this to the auth hook... state.. and then i see on my component repeated info. the state from the auth hook and same time the properties passed from the WrappedComponent.
... Is the Auth reducer really necesary? isAuthenticated property could also be passed on the WrappedComponent or not?
I did not Find a way to contact you sorry for the Issue...
thanks for your project it helped me to start on MSAL with React :)

@genesisemmloh you're welcome : ) isAuthenticated  is simply a flag to keep track of the app's state and show the appropriate UI elements. It's part of the auth reducer since the sample demonstrates React & Redux pattern. But of course you can keep track of this in other ways (for instance, as a state in 'authProvider' HOC).
Not sure I understand your question here -do you want to avoid using Redux in general? Can you elaborate on some code snippet?

I'm not a Pro in react, your example helped me but the fact that the authprovide is a hoc, means will be on all the components passed as properties, and perhaps it doesn't need to have a reducer or what was the intention?

I see. The sample was aiming to show how to use MSAL.js together with Redux and HOC patterns in a React application. There's no hard requirement here, you can certainly avoid using Redux at all (if you are wondering why use Redux in general, you can see their documentaiton).
If you would like to see an MSAL.js & React sample using only the HOC pattern please take a look at here.

@genesisemmloh , can you share the typescript based implementation?

@derisen , I also saw some breaking changes in beta.4 vs beta.2, so the sample will need to be updated.

@mohsinonxrm a typescript based sample would be a good idea, thank you for the suggestion. Unlikely for this particular sample but we will consider releasing a typescript sample.
Regarding beta.4 update -thank you for the heads up, will be done asap

@mohsinonxrm see this for a typescript sample

Closing this as no further action to take.


Bug - cannot update to v0.8.18

Keep seeing this error when trying to update version. Also tried uninstalling and reinstalling the app.

Hi @ilidnew !
Thanks for your issue.
This issue is for Boostnote desktop, so I will close this issue.
Please check this issue.


can't open item

When I scroll to bottom, delete any one in the screen. After that I can't open any item of the screens.

Same problem.

Seems that when you delete an item at the bottom(iOS), the ListView would scroll up a little bit and over its bottom, then unless you restore the unexpected scroll state the Row will never respond touch event.
I resolve it by force scrollToEnd() when yScrollOffset >= contentHeight - layoutHeight in onContentSizeChange().
onLayout={e => this.layoutHeight = e.nativeEvent.layout.height}
onContentSizeChange={(w, h) => this.contentHeight = h}
onScroll={e => this.yScrollOffset = e.nativeEvent.contentOffset.y}

ps. Same issue as #109

Hey @DominicHan thanks for the report. @dotcink is right that this is a dupe of #109. Currently working on a fix but don't have anything yet. Thanks for the helpful comments, will look into them as possible solutions.
Going to close this issue though and track it in the original, thanks!
(sorry for the late response!)


feat: implement custom remote backend

Closes #1467
Closes #1827
Closes #1481
Closes #1557

[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

Codecov Report

Merging #2165 (52ed970) into master (b92c519) will increase coverage by 0.05%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories.  Learn more

Will this PR allow vscode-like "attach to running container" style connections. Those are used for connecting into docker containers. I see you're closing #1481 - are there more steps required to enable connecting to containers?


SDK Install from Instructions: Error finding vapi-runtime

I am using the latest SDK (or trying to), and haven't even got to the point of trying to authenticate to vCenter. I have searched existing issues. I searched old issues and found a few things but those issues were fairly old it seemed.
Environment

sdk package version:
Trying to install per the documentation / README.md at https://github.com/vmware/vsphere-automation-sdk-python, meaning the latest version via "pip install --upgrade git+https://github.com/vmware/vsphere-automation-sdk-python.git".

python version: 3.6.8

vSphere version: 7.0.2

Operating System/Shell (used to run SDK-based apps): CentOS 7

Steps or code snippet to reproduce

Install CentOS 7.2003 Minimal on VMware VM.

Install python3:
sudo yum -y install python3

Create and activate venv:
python3 -m venv
cd
source ./bin/activate

Following instructions, update pip and setuptools:
pip install --upgrade pip setuptools

Following instructions, attempt install:
pip install --upgrade git+https://github.com/vmware/vsphere-automation-sdk-python.git

Actual behavior
Full output, error near bottom:
Collecting git+https://github.com/vmware/vsphere-automation-sdk-python.git
Cloning https://github.com/vmware/vsphere-automation-sdk-python.git to /tmp/pip-ubq0vit8-build
Collecting lxml>=4.3.0 (from vSphere-Automation-SDK==1.71.0)
Using cached https://files.pythonhosted.org/packages/a8/fe/56385f42495bfaf005d1e694a33622718a18d1ea4b6491b32be6461d8158/lxml-4.6.4-cp36-cp36m-manylinux_2_5_x86_64.manylinux1_x86_64.whl
Requirement already up-to-date: pyVmomi>=6.7 in ./lib/python3.6/site-packages (from vSphere-Automation-SDK==1.71.0)
Collecting vapi-runtime@ file://localhost//tmp/pip-ubq0vit8-build/lib/vapi-runtime/vapi_runtime-2.30.0-py2.py3-none-any.whl (from vSphere-Automation-SDK==1.71.0)
Could not find a version that satisfies the requirement vapi-runtime@ file://localhost//tmp/pip-ubq0vit8-build/lib/vapi-runtime/vapi_runtime-2.30.0-py2.py3-none-any.whl (from vSphere-Automation-SDK==1.71.0) (from versions: )
No matching distribution found for vapi-runtime@ file://localhost//tmp/pip-ubq0vit8-build/lib/vapi-runtime/vapi_runtime-2.30.0-py2.py3-none-any.whl (from vSphere-Automation-SDK==1.71.0)
Expected behavior
Successful install...

I could not reproduce  this  issue neither in centos 7 or ubuntu.

Weird, I see vapi-client-bindings in requirements.txt.
But I get an error suggesting it is not available? Is this not on PyPI?
$ pip3 download vapi-client-bindings
ERROR: Could not find a version that satisfies the requirement vapi-client-bindings (from versions: none)
ERROR: No matching distribution found for vapi-client-bindings
I don't see anything in the requirements.txt that would point it to a different repo, unless I'm missing something.
I am running inside a virtual environment per recommendations in the docs, but the above pip3 command gives the same result regardless.

Weird it seems to have worked today............. I did not change anything on my side though.

I am having this issue on some machines, but it is working on other machines, and I'm not sure what the difference is. I thought it was the Python version at first, but that appears to not be the case.

Weird, I see vapi-client-bindings in requirements.txt.
But I get an error suggesting it is not available? Is this not on PyPI?
$ pip3 download vapi-client-bindings ERROR: Could not find a version that satisfies the requirement vapi-client-bindings (from versions: none) ERROR: No matching distribution found for vapi-client-bindings
I don't see anything in the requirements.txt that would point it to a different repo, unless I'm missing something.
I am running inside a virtual environment per recommendations in the docs, but the above pip3 command gives the same result regardless.

bindings and runtime are not in pypi. !!

I am having this issue currently as well.

Closing this issue.
If you are facing issue again, please feel free to reopen.

pip3 install pip-tools
thx for all!


Windows "Some of these settings are managed by your organization" message

First the message appeared in my browser, I freaked out and reset my PC and all the passwords thinking I had gotten a malware. After the fresh install when I ran this app again, this time the warning appeared in the systems privacy settings. Is there a way to disable/revert this? It seems the app applies some kind of group policy/registry tweak or something.

Unfortunately, no. This program uses the registry to change the privacy settings on a machine. I don't believe there is any way of removing these "Some of these settings are managed by your organization" messages and to revert these settings you would need to revert them through the BloatyNosy software.

Same here, fully reinstalled windows after thinking some obscure malware had got me lol. (Probably needed it though eh).
Later realised it may have been this app, since the message occured after a reinstall and in both chrome and edge.
Is it possible to revert them through bloatynosy? I can't see an otion to do this in the app.
Could the registry entries in question be posted here?

Same here, fully reinstalled windows after thinking some obscure malware had got me lol. (Probably needed it though eh). Later realised it may have been this app, since the message occured after a reinstall and in both chrome and edge.
Is it possible to revert them through bloatynosy? I can't see an otion to do this in the app.
Could the registry entries in question be posted here?
(Also, might be worth considering warning users about this. Even as an advanced user, this is a difficult one to pin down the origin of).

This. Would also like a warning on that the app would show this in the settings.

Can be managed by editing registry under [Computer\HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge]
and these policies can be reloaded from edge://policy
I needed only these policies enabled:
AutofillAddressEnabled
LocalProvidersEnabled

The successor Winpilot only tracks settings of the currently logged-in user. These notifications are now a thing of the past.


project does not work please help

I cannot figure out please help my boss fire

yes

then you'll have no boss


Codable Class Causes Warning When Using @Observable Macro

Description
When a class marked as Codable is made observable by applying the @Observable macro the following warning is emitted:
 • Immutable property will not be decoded because it is declared with an initial value which cannot be overwritten

The immutable property is generated by the @Observable macro on the line declaring property _$observationRegistrar:
 • @ObservationIgnored private let _$observationRegistrar = Observation.ObservationRegistrar()

A workaround to suppress the warning is to define a CodingKeys enum that includes all of the visible class properties, leaving out the hidden _$observationRegistrar property. This means that the autogenerated Codable conformance cannot be used when making a class observable using the new Observation framework. It also means that mutable (var) properties must be preceded with an underscore when defining them in the CodingKeys enum to match their redefinition in the macro. This seems verbose and unnecessarily exposes underlying details included in the macro expansion.
Reproduction
import SwiftUI

@Observable
class MyObservable: Codable {
    var observedInt: Int

    init(int: Int) {
        self.observedInt = int
    }

//    enum CodingKeys: CodingKey {
//        case _observedInt
//    }
}

Expected behavior
I would expect this to compile without a warning.
Environment
I am compiling using Xcode 15.1 beta 3, but I believe this to be an issue using any version of Xcode 15.
Additional information
No response

This has also been submitted as FB13440388 - Codable Class Causes Warning When Using @Observable Macro


Feature/rooms users extended search

Added Room/Users extended search parameters according to Gitter API.

"q": searchQuery
"skip": records to skip
"limit": record limit

Parameters Implemented as requested using an object to encapsulate parameters. Class name is RoomUsersRequestParams.
Implementation added for Sync, Async and Rx libraries.

@amatkivskiy
Could not add tests due to not understanding of setup of local mock server. I will be very happy to include tests. Can you point me in the right direction. Thanks?

Coverage decreased (-0.1%) to 14.407% when pulling b5aa567669b8f87d8e29f419c324f0ec9370ca27 on asantibanez:feature/rooms-users-extended-search into 8042b215807f869b417fec75492d4c98742b0351 on Gitteroid:dev.

@asantibanez please see PR #34 . I've extracted common gitter request parameters to separate class so it can be used for any request.

@asantibanez Any updates on this?


Add support for WHERE IN clause

Would be super useful to have, however I gather the rawQuery method has to be used.
i.e. delete where id in(1,2,3,4)
int[ ] deleteIds = { 3,4,5 };
Integer deletedCount = Inquiry.get()
		.deleteFrom("people", Person.class)
		.where("_id in(?)", deleteIds)
		.run();

Added in the latest release, see the tutorial on the front page for details. A lot has changed in version 3.0.1 and 3.1.0.

Awesome thanks!


Remove unused CSS rules from completion-modal.css

Description
The completion-modal.css contains a lot of unused CSS rules, which should be cleaned up.
The unused rules/classes are:

.challenge-success-modal
.btn-lg
.btn-cta-big
.completion-modal-body
.completion-message
.completion-challenge-name

Requirements

Remove the above classes from https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/templates/Challenges/components/completion-modal.css
Test and confirm that the modal displays properly after the changes

Hi, I can help with this If you would like to assign it to me.


Added estimate_rct_tx_size

Depends on https://github.com/mymonero/mymonero-core-cpp/pull/12

Hey @gutenye, could I trouble you to rebase?

@paulshapiro rebased

Would be worthwhile to add this method back to the readme now that I've removed it but I can handle that. Thanks for the PR!!

@gutenye you're missing the estimate_rct_tx_size implementation from serial_bridge ...

(Scratch my previous comment of course - Guten corrected me as I was looking on master and had neglected to merge develop)


Update migration-guide.md

Change Description
Fix "Listen on all interfaces" snippet for v1

Thanks!


⚠ Movie Manager has degraded performance

In 85e82de, Movie Manager ($SITES_URL_MOVIE_MANAGER) experienced degraded performance:

HTTP code: 523
Response time: 3371 ms

Resolved: Movie Manager performance has improved in f799e2f after 28 minutes.


[Enhancement] Expose listening APIs

Currently, the fvp native player's APIs lack events or methods for directly listening to changes in position, duration, and buffering state. This makes it difficult to create features like progress bars, time displays, or custom buffering indicators. Exposing these APIs would significantly improve the developer experience and enable the creation of more advanced playback functionalities. The current native player APIs do not provide any built-in mechanisms for developers to track or react to changes in position, duration, or buffering.
Proposal
We propose the following adding some API improvements, like:
player.onPositionChange((duration) {})
and similar methods for other options.

events are already in video_player and video_player_mdk.dart, the can be reused in your code


Set user-select: none on the app preloader

It bugs me that you can select 'phosphorus' on the preloader.

FYI
also on your index page you can select a project from the drop down list say 'O by DPU..', then as it starts to load, press 'a' lots of times and it loads another 'Alone in the depths...'


cmd/scollector: Add MTU, AdminStatus, and OperationStatus to SNMP int…

…erface polling

Can review, but please don't merge as it needs to be tested.


Linkplay Spotify Not work

What version of Music Assistant has the issue?
2022.8.2
The problem
To play a spotify playlist I had configured this automation and I was playing on the media player created by music assistant now it no longer works and I can't even play a tts or other I use an integrated speaker with linkplay, if I use local music and the media_player player. seeme_hifi works but with media_player.mass_seeme_hifi it does not work, I see that the state is changed in playback but the speaker does not emit any sound
alias: V Spotify
description: ""
trigger:
  - platform: event
    event_type: rhasspy_Spotify
condition: []
action:
  - service: media_player.play_media
    data:
      media_content_type: playlist
      media_content_id: >-
        https://open.spotify.com/playlist/2LC2VouwE0aoOFVhmAffCf?si=f186971dba244936
    target:
      entity_id: media_player.mass_seeme_hifi
mode: single

How to reproduce
Use a linkplay speaker and try to play any source of music from music assistant, if i switch  on this configuration Create mediaplayers for Music Assistant players in Home Assistant i have an only music player but not works, if i switch of i have two different music player  the original media_player.seeme_hifi and the other created from Music Assistant media_player.mass_seeme_hifi, the last one doesn t work
Relevant log output
2022-08-12 18:17:15.380 INFO (MainThread) [music_assistant.players.stream] Start Streaming queue track: database://track/452 (Vale pain/Neima Ezza - 1 COLPO) for queue SEEMEHiFi - crossfade: False
2022-08-12 18:17:18.860 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:21.860 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:24.862 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:25.379 WARNING (MainThread) [music_assistant.players.stream] Abort: client(s) did not connect within 10 seconds.
2022-08-12 18:17:25.862 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.seeme_hifi is taking over 10 seconds
2022-08-12 18:17:27.864 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:30.866 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:33.867 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-12 18:17:36.869 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03

Additional information
No response
What version of Home Assistant Core are your running
2022.8.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi

Hi @lucasimons
Is this a Spotify specific problem? What happens with local mp3 files or radio sources?
Does only the automation fail? Or also when selecting a Spotify playlist in MA?
Best Eric

Hi @erkr
The player created from MA (media player.mass_name)does not work with any music source (local mp3,  tts Spotify) now I can't use MA with my speaker, I use it from the beginning to before the update of MA and HA... I try to install old versions of MA but doesn't work with the previous release

I think that is a linkplay specific issue. @nagyrobi can you help out with this one ?

I don't know what is the problem....because the original media player works with tts and local mp3 but the media player created by MA doesn't work with any source of music.... Are there any other people that use link play speakers and MA?

Linkplay is the only (custom) integration that interacts with MA directly so maybe something broke in the recent releases.
You say that you can't play anything from MA to the linkplay device ?
You did try this from the Music Assistant interface as test too ?

I use MA for 1 month without problems.. Now if I try to play a mp3, a tts or Spotify songs or Playlist I can see the song start but in the log are some errors and the speakers doesn't play any music

It's some character encoding issue...

I update HA and MA but the error  remains
2022-08-16 10:46:44.313 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/config/custom_components/linkplay/media_player.py", line 543, in async_update
    await self.async_get_status(no_throttle=True)
  File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status
    resp = await self.call_linkplay_httpapi("getPlayerStatus", True)
  File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi
    data = await response.json(content_type=None)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json
    return await super().json(*args, loads=loads, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json
    return loads(stripped.decode(encoding))
LookupError: unknown encoding: VISCII
2022-08-16 10:46:47.317 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/config/custom_components/linkplay/media_player.py", line 543, in async_update
    await self.async_get_status(no_throttle=True)
  File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status
    resp = await self.call_linkplay_httpapi("getPlayerStatus", True)
  File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi
    data = await response.json(content_type=None)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json
    return await super().json(*args, loads=loads, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json
    return loads(stripped.decode(encoding))
orjson.JSONDecodeError: unexpected control character in string: line 1 column 127 (char 126)
2022-08-16 10:46:47.920 WARNING (MainThread) [music_assistant.players.stream] Abort: client(s) did not connect within 10 seconds.
2022-08-16 10:46:50.315 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/config/custom_components/linkplay/media_player.py", line 543, in async_update
    await self.async_get_status(no_throttle=True)
  File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status
    resp = await self.call_linkplay_httpapi("getPlayerStatus", True)
  File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi
    data = await response.json(content_type=None)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json
    return await super().json(*args, loads=loads, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json
    return loads(stripped.decode(encoding))
orjson.JSONDecodeError: unexpected control character in string: line 1 column 127 (char 126)
2022-08-16 10:46:53.313 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/config/custom_components/linkplay/media_player.py", line 543, in async_update
    await self.async_get_status(no_throttle=True)
  File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status
    resp = await self.call_linkplay_httpapi("getPlayerStatus", True)
  File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi
    data = await response.json(content_type=None)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json
    return await super().json(*args, loads=loads, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json
    return loads(stripped.decode(encoding))
orjson.JSONDecodeError: unexpected control character in string: line 1 column 127 (char 126)

I'm sorry but the error is originating from the Linkplay integration/player itself.
As I do not own any Linkplay based players I'm having a hard time assisting you. @nagyrobi can you please help and see if this is maybe an error in the linkplay integration itself ?

A little busy lately, I'll try to look next week.

@nagyrobi just checking if you have had a chance to look at this for us?

Not yet, sorry.

The error still is the same
2022-08-30 15:17:53.546 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/config/custom_components/linkplay/media_player.py", line 543, in async_update
    await self.async_get_status(no_throttle=True)
  File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status
    resp = await self.call_linkplay_httpapi("getPlayerStatus", True)
  File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi
    data = await response.json(content_type=None)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json
    return await super().json(*args, loads=loads, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json
    return loads(stripped.decode(encoding))
orjson.JSONDecodeError: unexpected control character in string: line 1 column 131 (char 130)

The problem is caused by invalid JSON returned by your Linkplay device.
When this error occurs, access in your browser the URL below and post output here.
http://YOUR.PLAYER.IP.ADDRESS/httpapi.asp?command=getPlayerStatus

I think the problem is the title of track
{"type":"0","ch":"0","mode":"10","loop":"4","eq":"0","status":"stop","curpos":"1823","offset_pts":"1823","totlen":"1000","Title":"V§+0lZ","Artist":"","Album":"","alarmflag":"0","plicount":"0","plicurr":"0","vol":"29","mute":"0"

Yep, likely that causes the issue. What track did you try to play? Does it have any metadata on its own? Played through MA or by other means?
@marcelveldt do you think that's something MA does, injecting metadata in the stream?

The last error is without play any song... If I play a local song with browser media it is works fine but there is the other error

media_player.seeme_hifi fails

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state

await self.async_device_update()

File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update

raise exc

File "/config/custom_components/linkplay/media_player.py", line 543, in async_update

await self.async_get_status(no_throttle=True)

File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status

resp = await self.call_linkplay_httpapi("getPlayerStatus", True)

File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi

data = await response.json(content_type=None)

File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json

return await super().json(*args, loads=loads, **kwargs)

File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json

return loads(stripped.decode(encoding))

orjson.JSONDecodeError: unexpected control character in string: line 1 column 135 (char 134)

2022-08-30 19:00:16.619 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.seeme_hifi fails

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state

await self.async_device_update()

File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update

raise exc

File "/config/custom_components/linkplay/media_player.py", line 543, in async_update

await self.async_get_status(no_throttle=True)

File "/config/custom_components/linkplay/media_player.py", line 469, in async_get_status

resp = await self.call_linkplay_httpapi("getPlayerStatus", True)

File "/config/custom_components/linkplay/media_player.py", line 419, in call_linkplay_httpapi

data = await response.json(content_type=None)

File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 52, in json

return await super().json(*args, loads=loads, **kwargs)

File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1119, in json

return loads(stripped.decode(encoding))

orjson.JSONDecodeError: unexpected control character in string: line 1 column 135 (char 134)

If I try to play with MA nothing work

If I paly a tts there are strange caracter in the title,
ch":"0","mode":"10","loop":"4","eq":"0","status":"stop","curpos":"7523","offset_pts":"7523","totlen":"7000","Title":"V§+ĞC[","Artist":"","Album":"","alarmflag":"0","plicount":"0","plicurr":"0","vol":"29","mute":"0"

I'm sorry this is specific to your setup. Try restarting Linkplay device, play stuff without MA and then with MA, see difference.

I have tried with MA not work nothing, without MA works local mp3 l, tts but I can't play Spotify songs or Playlist with HA i must use the Spotify app and select the speaker manually

Try Playing Spotify from your mobile phone and select the Linkplay speaker within the Spotify app. That way won't go through HA.

Also try playing TTS directly not through MA.

Yes it works but I can use this automation,
alias: V Spotify
description: ""
trigger:
  - platform: event
    event_type: rhasspy_Spotify
condition: []
action:
  - service: media_player.play_media
    data:
      media_content_type: playlist
      media_content_id: >-
        https://open.spotify.com/playlist/2LC2VouwE0aoOFVhmAffCf?si=f186971dba244936
    target:
      entity_id:
        - media_player.seeme_hifi
mode: single

If playing media outside MA works fine, the problem unfortunately is not within Linkplay component.
Somehow the MA streams your system generates include some metadata bytes which are decoded by the Linkplay hardware errorneously.

In that case disable the metadata in the stream settings...
Music Assistant interface --> click Queue --> click the dots in the upper right corner for the contextmenu
choose advanced --> Set "ICY metadata" to disabled.

i have done some test but with MA not works,
there is always this error of a caracter of the title, but i don t know who send this title?
"status":"load","curpos":"1823","offset_pts":"0","totlen":"0","Title":"V§+V§+"

i turn off the module when it is connected to wiki there isn t any strange caracter,
{"type":"0","ch":"0","mode":"0","loop":"0","eq":"0","status":"stop","curpos":"0","offset_pts":"0","totlen":"0","Title":"556E6B6E6F776E","Artist":"556E6B6E6F776E","Album":"556E6B6E6F776E","alarmflag":"0","plicount":"0"

when i play a tts without MA, appear the error, so i return off the module and i try to use MA and it not works because the songs doesn t start but there aren t any errors
"eq":"0","status":"stop","curpos":"0","offset_pts":"0","totlen":"0","Title":"http://<IP_ADDRESS>:8095/a999328a34084907b57a54777994850b.flac","Artist":"556E6B6E6F776E","Album":"556E6B6E6F776E"

No error with strange caracter but the music doesn t start
2022-08-30 23:16:37.218 INFO (MainThread) [music_assistant.players.stream] Start Streaming queue track: spotify://track/5Pg4qYTcvCUBBq3jBhKq0t (Daddy Yankee/Pitbull - HOT) for queue SEEMEHiFi - crossfade: False
2022-08-30 23:16:38.666 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:41.667 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:44.668 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:47.217 WARNING (MainThread) [music_assistant.players.stream] Abort: client(s) did not connect within 10 seconds.
2022-08-30 23:16:47.669 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:50.670 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:53.671 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:56.691 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:16:59.684 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:02.688 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:05.691 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:08.694 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:11.696 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:14.697 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:17.698 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:20.699 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:23.699 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:29.702 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:32.741 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:35.740 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:36.704 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.seeme_hifi is taking over 10 seconds
2022-08-30 23:17:38.741 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:41.742 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:44.743 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-30 23:17:47.744 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03

Updating linkplay media_player took longer than the scheduled update interval 0:00:03 happens because the error triggers right within the main update cycle of the component and since it crashes, it doesn't generate any updated state, whilst HA still waits for the data...
I can't see how this could be fixed within the Linkplay component as the failure invalidates the entire JSON decoding so even if I would catch the error to not show in the logs, the updated info would still be missing.
So this is either:

the Linkplay speaker firmware bug, allowing invalid control characters in the httpapi json responses
streams generated by HA/MA contain invalid control characters in the metadata.

Control characters in this context are those with character codes in the 0-31 range, including \t (tab), \n, \r, \0, etc. These aren't allowed in metadata anyways. @marcelveldt perhaps you could take a look, could it be that metadata contains any of such chars? If yes, maybe a filter could be applied?

In that case disable the metadata in the stream settings...
Music Assistant interface --> click Queue --> click the dots in the upper right corner for the contextmenu
choose advanced --> Set "ICY metadata" to disabled.

Is this global? Applies to any player's queue, any stream? Eg TTS's too?

Is this global? Applies to any player's queue, any stream? Eg TTS's too?

No, it is per player(queue) and only for the music stream. TTS does not have ICY metadata at all.
@lucasimons did you try the instructions above to completely disable the ICY metadata or set it to smaller chunk size ?

Can you play TTS from HA to the linkplay player ?
Can you play TTS from HA to the "mass" player created for the linkplay player ?
Can you play a random radio station URL ?

Hmm, looking at your log above I notice something very strange:
http://<IP_ADDRESS>:8095 Is that your internal URL ?
Is that URL reachable from your player ? Notice that MA derives the IP-address from the "Internal URL" field of the HA config. A DNS name will be auto resolved. Do not enter an external dns name there because the MA stream service is local only.

Is this global? Applies to any player's queue, any stream? Eg TTS's too?

No, it is per player(queue) and only for the music stream. TTS does not have ICY metadata at all.
@lucasimons did you try the instructions above to completely disable the ICY metadata or set it to smaller chunk size ?

Can you play TTS from HA to the linkplay player ?
Can you play TTS from HA to the "mass" player created for the linkplay player ?
Can you play a random radio station URL ?

I completely disable icy metadata or smaller chunk size but not change anythings

TTS, radio, local mp3 works with linkplay player
nothings works with mass player

Hmm, looking at your log above I notice something very strange: http://<IP_ADDRESS>:8095 Is that your internal URL ?
Is that URL reachable from your player ? Notice that MA derives the IP-address from the "Internal URL" field of the HA config. A DNS name will be auto resolved. Do not enter an external dns name there because the MA stream service is local only.

i don t know what is ... but now i see this in the title box
TTS with linkplay player
"Title":"http://my.homeassistant.ip:8123/api/tts_proxy/e2e2bf3c44f701484bcc019e61f92f087473f0cf_it_-_google_translate.mp3"
Radio with linkplay player
"Title":"http://ice07.fluidstream.net:8080/KissKiss.mp3"
if i try to play something with MA player the title non change so doesn t start to play

The title is just a symptom and not the cause otherwise you would have heard music.
I really think you should have a look at the internal URL field in HA config because that does not seem right now.
Settings --> System --> Network --> Home Assistant URL --> Local network (set to automatic or use your internal HA IP).

The title is just a symptom and not the cause otherwise you would have heard music. I really think you should have a look at the internal URL field in HA config because that does not seem right now.
Settings --> System --> Network --> Home Assistant URL --> Local network (set to automatic or use your internal HA IP).

This is set to automatic ...

OK, change it then manually to your local IP ?
http://<IP_ADDRESS>:8123

I have changed Local Network setting with my ip, and restarted HA but the MA player not works

Enable deboog logger in configuration.yaml:
logger:
  logs:
    custom_components.linkplay: debug
    custom_components.mass: debug

Try to play a web radio first look for a line like this on the .log file:
2022-08-31 15:05:41.798 DEBUG (MainThread) [custom_components.linkplay.media_player] For: Up2Stream  cmd: setPlayerCmd:play:http://ice07.fluidstream.net:8080/KissKiss.mp3  resp: OK
If this is OK and sounds, try to play a sound through MA and look for the same line containing setPlayerCmd:play what's the URL passed by HA to the player?
Can you play that URL on your PC with VLC or something?

Local mp3
linkplay player
2022-08-31 15:54:34.640 DEBUG (MainThread) [custom_components.linkplay.media_player] For: SEEMEHiFi  cmd: setPlayerCmd:play:http://ip:8123/media/media/Musica/2022/Capelli%20blu.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiIwMzQwMzljYTliMzA0ZDhiODFjYjNkMGRhY2JkNTVmZCIsInBhdGgiOiIvbWVkaWEvbWVkaWEvTXVzaWNhLzIwMjIvQ2FwZWxsaSBibHUubXAzIiwicGFyYW1zIjp7fSwiaWF0IjoxNjYxOTU0MDc0LCJleHAiOjE2NjIwNDA0NzR9.1grVyOVVJ7tet-OJa8-p14W_3W3TyuVVOLpRj8X5SX4  resp: OK

local mp3
MA player
2022-08-31 15:56:00.265 WARNING (MainThread) [music_assistant.music.file] /media/Musica/2022/Capelli blu.mp3 is missing ID3 tag [album]
2022-08-31 15:56:00.284 DEBUG (MainThread) [custom_components.linkplay.media_player] 06 Update URI final detect media_player.seeme_hifi, SEEMEHiFi
2022-08-31 15:56:01.916 DEBUG (MainThread) [music_assistant.event] queue_items_updated media_player.seeme_hifi
2022-08-31 15:56:01.930 DEBUG (MainThread) [music_assistant.event] queue_updated media_player.seeme_hifi
2022-08-31 15:56:02.261 DEBUG (MainThread) [custom_components.mass.player_controls.media_player.seeme_hifi] play_url: http://<IP_ADDRESS>:8095/45b57276c48844fca7edf772c08fab9e.flac
2022-08-31 15:56:02.262 DEBUG (MainThread) [custom_components.linkplay.media_player] Trying to play media. Device: media_player.seeme_hifi, Media_type: music, Media_id: http://<IP_ADDRESS>:8095/45b57276c48844fca7edf772c08fab9e.flac
2022-08-31 15:56:02.262 DEBUG (MainThread) [custom_components.linkplay.media_player] For: SEEMEHiFi detect URI redirect-from:   http://<IP_ADDRESS>:8095/45b57276c48844fca7edf772c08fab9e.flac
2022-08-31 15:56:02.262 DEBUG (MainThread) [custom_components.linkplay.media_player] For: SEEMEHiFi detect URI redirect - to:   http://<IP_ADDRESS>:8095/45b57276c48844fca7edf772c08fab9e.flac
2022-08-31 15:56:02.404 DEBUG (MainThread) [music_assistant.players.stream] Starting Queue audio stream for Queue SEEMEHiFi (PCM format: s16le - sample rate: 44100)
2022-08-31 15:56:02.405 INFO (MainThread) [music_assistant.players.stream] Start Streaming queue track: file://track/2022capelliblump3 (Unknown Artist - Capelli blu) for queue SEEMEHiFi - crossfade: False
2022-08-31 15:56:02.406 DEBUG (MainThread) [music_assistant.event] queue_updated media_player.seeme_hifi
2022-08-31 15:56:02.514 DEBUG (MainThread) [music_assistant.helpers.audio] start media stream for: file://track/2022capelliblump3
2022-08-31 15:56:02.516 DEBUG (MainThread) [custom_components.linkplay.media_player] For: SEEMEHiFi  cmd: setPlayerCmd:play:http://<IP_ADDRESS>:8095/45b57276c48844fca7edf772c08fab9e.flac  resp: OK
2022-08-31 15:56:02.987 DEBUG (MainThread) [music_assistant.event] queue_updated media_player.seeme_hifi
2022-08-31 15:56:02.990 DEBUG (MainThread) [music_assistant.event] queue_updated media_player.seeme_hifi
2022-08-31 15:56:03.320 DEBUG (MainThread) [custom_components.linkplay.media_player] 06 Update URI final detect media_player.seeme_hifi, SEEMEHiFi
2022-08-31 15:56:06.217 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:09.219 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:12.219 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:12.403 WARNING (MainThread) [music_assistant.players.stream] Abort: client(s) did not connect within 10 seconds.
2022-08-31 15:56:12.495 DEBUG (MainThread) [music_assistant.helpers.audio] media stream aborted for: file://track/2022capelliblump3
2022-08-31 15:56:13.231 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.seeme_hifi is taking over 10 seconds
2022-08-31 15:56:15.219 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:18.233 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:21.234 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:24.235 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:25.039 DEBUG (MainThread) [music_assistant.event] player_updated media_player.seeme_hifi
2022-08-31 15:56:27.236 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03
2022-08-31 15:56:30.237 WARNING (MainThread) [homeassistant.components.media_player] Updating linkplay media_player took longer than the scheduled update interval 0:00:03

Instead of <IP_ADDRESS>, you should have the same ip that you see in the first log above.
Your Home Assistant instance seems to be severely misconfigured...

A quick whois lookup for the address above looks like belonging to an Amazon AWS...
Maybe you also have a misconfigured network, perhaps some VPN involved...?

Instead of <IP_ADDRESS>, you should have the same ip that you see in the first log above. Your Home Assistant instance seems to be severely misconfigured...

I didn t change any network configuration, all works fine instead of MA player... would be a problem of MA that pass the  wrong  url?

You should configure a local URL in the HA Network config. Music Assistant derives the stream URL from there.
This is not a Linkplay nor Music Assistant issue but a configuration issue. Somehow your internal URL resolves to "<IP_ADDRESS>" now which is never going to work.

You should configure a local URL in the HA Network config. Music Assistant derives the stream URL from there. This is not a Linkplay nor Music Assistant issue but a configuration issue. Somehow your internal URL resolves to "<IP_ADDRESS>" now which is never going to work.

I didn t change my network settings, in this month, so i think the problem is not od my config... i use MA for one month and it works fine but from 20 days ago the MA player doesn t work

You have a virus then, or your system has been compromised :-(

A quick whois lookup for the address above looks like belonging to an Amazon AWS...
Maybe you also have a misconfigured network, perhaps some VPN involved...?

I don't know what is the problem I use zerotier and cloud flare but I Don know is the <IP_ADDRESS>? There are any component that use the internal ip like MA?

I'm going to close this issue. You have wasted a lot of our time. As explained over and over again in the docs and here in this support thread, Music Assistant relies on LOCAL NETWORK to stream audio so no, things like zero tier will not work.
Configure your network so that it can also be reached locally or uninstall Music Assistant. Thanks.

I'm going to close this issue. You have wasted a lot of our time. As explained over and over again in the docs and here in this support thread, Music Assistant relies on LOCAL NETWORK to stream audio so no, things like zero tier will not work.
Configure your network so that it can also be reached locally or uninstall Music Assistant. Thanks.

I use MA locally and It not works without using zerotier... The linkplay component works fine and sent the correct ip of my ha system

You have some serious routing issues then.

You have some serious routing issues then.

i don t think , i have write a wrong answear, the zerotier vpn is always turn off, i have tried to stop the integration but doesn t change anythinks

@lucasimons you should configure the right IP in the HA settings at internal URL. Please do that, it will fix your issue.

you should configure the right IP in the HA settings at internal URL. Please do tha

is there a way to see if i set up the internal URL correctly?

Good question, I'm not sure. I'd say try that URL on one of your client computers on the same network as the speakers ?
The URL should look something like http://<IP_ADDRESS>:8123

I have configured the right ip yesterday because it was on Automatic but this settings doesn t change the MA code when i m starting to play sometings the ip still wrong .... cmd: setPlayerCmd:play:http://<IP_ADDRESS>:8095/33d0050f5eb445e080a64e62b53f8fcf.flac  resp: OK

Did you restart HA after correcting the URL ? That IP is coming from somewhere....

yes I have restarted even several times, I have to put something in the file configuration.yaml? Do you know of any other integrations that use that url and that I can install to see if it works with those?

Hmm, looking at your log above I notice something very strange: http://<IP_ADDRESS>:8095 Is that your internal URL ?
Is that URL reachable from your player ? Notice that MA derives the IP-address from the "Internal URL" field of the HA config. A DNS name will be auto resolved. Do not enter an external dns name there because the MA stream service is local only.

i don t know what is ... but now i see this in the title box
TTS with linkplay player "Title":"http://my.homeassistant.ip:8123/api/tts_proxy/e2e2bf3c44f701484bcc019e61f92f087473f0cf_it_-_google_translate.mp3"
Radio with linkplay player "Title":"http://ice07.fluidstream.net:8080/KissKiss.mp3"
if i try to play something with MA player the title non change so doesn t start to play

if i use the linkplay player there is the correct ip address @nagyrobi where is this address taken from ?

Are you on a default HAOS installation or are you running the core etc. yourself ? Please look in your configuration.yaml if there's something old in there that messes with the internal URL.
Easy way to test is to use the tts service to send a tts message to the speakers, that should send the internal URL. You are 100% sure that you filled the local IP that internal URL field ? So something like "http://<IP_ADDRESS>:8123" or "http://homeassistant.local:8123" ? Filling in an external DNS name there will NOT work.

i use HAOS and i m 100% sure that i fill the ip correctly

If you use TTS from HA to the linkplay player directly it uses the same logic to get the internal address.
Maybe you need to re-set the DHCP setting for the network or something like that ?

the problem was that i set the static ip of my HAOS on my router, but i also have set the static ip in the network setting of HA, i think that it was the problem, because i set dhcp yesterday but seam that it doesn t work but this morning i shutdown my raspy and i turned it on, now everething works fine

Told you. Your network issues.

Told you. Your network issues.

it was very strange because everything worked fine
except MA


Update gradle, kotlin, compose

Is there any progress in this repo @Tlaster and @janbina? Or is it mostly dead and I should rely on the forks?

This one is dead, development continues in https://github.com/mxalbert1996/Zoomable.


message-bus is wrongly used as a id

I used MessageBus in my Article model. In ArticlesController#update, a message is published and the browser is redirected to article page
def update
  respond_to do |format|
    if @article.update(article_params)
      MessageBus.publish<EMAIL_ADDRESS>{
        collectable_type: 'Article',
        collectable_id: @article.id
      }
      format.html { redirect_to<EMAIL_ADDRESS>@article] }
    else
      format.html { render :edit }
    end
  end
end

but I saw there is an error in the log:
Started GET "/users/1/articles/message-bus.js" for <IP_ADDRESS> at 2015-09-05 18:59:37 +0800
Processing by ArticlesController#show as JS
  Parameters: {"user_id"=>"1", "id"=>"message-bus"}
  User Load (0.2ms)  SELECT  "users".* FROM "users" WHERE "users"."id" = $1  ORDER BY "users"."id" ASC LIMIT 1  [["id", 1]]
  Article Load (0.2ms)  SELECT  "articles".* FROM "articles" WHERE "articles"."id" = $1 LIMIT 1  [["id", 0]]
Completed 404 Not Found in 3ms (ActiveRecord: 0.4ms)

ActiveRecord::RecordNotFound (Couldn't find Article with 'id'=message-bus):
  app/controllers/articles_controller.rb:103:in `set_article'

Why message-bus.js is in the URL?

I found this error is caused by the following line:
<script src="message-bus.js" type="text/javascript"></script>

After remove it, the error is gone. Then I noticed that I have created a file message_bus.js in app/assets/javascripts/, after I changed that line to:
<script src="message_bus.js" type="text/javascript"></script>

The error is gone. But I also tried to remove that line completely, and it also works.

Yeah ... this is a user error :) is there anything wrong in the docs that needs fixing?


Port pm io

Added the code necessary for Parsing from PowerModels. @kdheepak I made some changes to the logging that require careful revision.

Okay this is ready to be merged right now. I'll add the logging changes required as a separate PR.


At authentication/social/additional-claims fixes google scope

Updated docs
see source for reference

Thank you for the PR, @Bludator!