Unexpected error when trying to submit an expense

Describe the bug
I got an unexpected error on https://opencollective.com/drupalatx/events/texas-camp-2019-19178ev/expenses/new while I was trying to submit an expense.
To Reproduce

Go to https://opencollective.com/drupalatx/events/texas-camp-2019-19178ev
Click on Submit Expense
See error

Device

OS: MacOS High Sierra
Browser: Chrome

Technical details

onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
texas-camp-2019-19178ev.js:1 Failed to load resource: the server responded with a status of 404 ()
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
_app.js:1 Event: props.collective.startsAt should not be empty. props.collective.id: 53318
(anonymous) @ _app.js:1
_app.js:1 Event: props.collective.startsAt should not be empty. props.collective.id: 53318
(anonymous) @ _app.js:1
_app.js:1 TypeError: Cannot read property 'format' of undefined
    at t.value (event.js:1)
    at new t (event.js:1)
    at wo (commons.52bbea3c433661e3c6b3.js:1)
    at Da (commons.52bbea3c433661e3c6b3.js:1)
    at Xs (commons.52bbea3c433661e3c6b3.js:1)
    at yu (commons.52bbea3c433661e3c6b3.js:1)
    at mu (commons.52bbea3c433661e3c6b3.js:1)
    at iu (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at KqkS.t.unstable_runWithPriority (commons.52bbea3c433661e3c6b3.js:1)
    at zi (commons.52bbea3c433661e3c6b3.js:1)
    at Hi (commons.52bbea3c433661e3c6b3.js:1)
    at Yi (commons.52bbea3c433661e3c6b3.js:1)
    at eu (commons.52bbea3c433661e3c6b3.js:1)
    at qu (commons.52bbea3c433661e3c6b3.js:1)
    at Yu (commons.52bbea3c433661e3c6b3.js:1)
    at $u (commons.52bbea3c433661e3c6b3.js:1)
    at Object.render (commons.52bbea3c433661e3c6b3.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at fe (main-9a1bfa16284755fa25ed.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at te (main-9a1bfa16284755fa25ed.js:1)
    at e.subscription [as sub] (main-9a1bfa16284755fa25ed.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
(anonymous) @ _app.js:1
_app.js:1 TypeError: Cannot read property 'format' of undefined
    at t.value (event.js:1)
    at new t (event.js:1)
    at wo (commons.52bbea3c433661e3c6b3.js:1)
    at Da (commons.52bbea3c433661e3c6b3.js:1)
    at Xs (commons.52bbea3c433661e3c6b3.js:1)
    at yu (commons.52bbea3c433661e3c6b3.js:1)
    at mu (commons.52bbea3c433661e3c6b3.js:1)
    at iu (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at KqkS.t.unstable_runWithPriority (commons.52bbea3c433661e3c6b3.js:1)
    at zi (commons.52bbea3c433661e3c6b3.js:1)
    at Hi (commons.52bbea3c433661e3c6b3.js:1)
    at Yi (commons.52bbea3c433661e3c6b3.js:1)
    at eu (commons.52bbea3c433661e3c6b3.js:1)
    at qu (commons.52bbea3c433661e3c6b3.js:1)
    at Yu (commons.52bbea3c433661e3c6b3.js:1)
    at $u (commons.52bbea3c433661e3c6b3.js:1)
    at Object.render (commons.52bbea3c433661e3c6b3.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at fe (main-9a1bfa16284755fa25ed.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at te (main-9a1bfa16284755fa25ed.js:1)
    at e.subscription [as sub] (main-9a1bfa16284755fa25ed.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
(anonymous) @ _app.js:1
_app.js:1 TypeError: Cannot read property 'format' of undefined
    at t.value (event.js:1)
    at new t (event.js:1)
    at wo (commons.52bbea3c433661e3c6b3.js:1)
    at Da (commons.52bbea3c433661e3c6b3.js:1)
    at Xs (commons.52bbea3c433661e3c6b3.js:1)
    at yu (commons.52bbea3c433661e3c6b3.js:1)
    at mu (commons.52bbea3c433661e3c6b3.js:1)
    at iu (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at KqkS.t.unstable_runWithPriority (commons.52bbea3c433661e3c6b3.js:1)
    at zi (commons.52bbea3c433661e3c6b3.js:1)
    at Hi (commons.52bbea3c433661e3c6b3.js:1)
    at Yi (commons.52bbea3c433661e3c6b3.js:1)
    at eu (commons.52bbea3c433661e3c6b3.js:1)
    at qu (commons.52bbea3c433661e3c6b3.js:1)
    at Yu (commons.52bbea3c433661e3c6b3.js:1)
    at $u (commons.52bbea3c433661e3c6b3.js:1)
    at Object.render (commons.52bbea3c433661e3c6b3.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at fe (main-9a1bfa16284755fa25ed.js:1)
    at main-9a1bfa16284755fa25ed.js:1
    at c (commons.52bbea3c433661e3c6b3.js:1)
    at Generator._invoke (commons.52bbea3c433661e3c6b3.js:1)
    at Generator.e.<computed> [as next] (commons.52bbea3c433661e3c6b3.js:1)
    at i (commons.52bbea3c433661e3c6b3.js:1)
    at s (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at new Promise (<anonymous>)
    at new t (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
    at te (main-9a1bfa16284755fa25ed.js:1)
    at e.subscription [as sub] (main-9a1bfa16284755fa25ed.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at e.value (commons.52bbea3c433661e3c6b3.js:1)
    at commons.52bbea3c433661e3c6b3.js:1
(anonymous) @ _app.js:1
onloadwff.js:71 Uncaught (in promise) TypeError: Cannot read property 'querySelectorAll' of null
    at s.<anonymous> (onloadwff.js:71)
    at l (onloadwff.js:71)
    at Object.next (onloadwff.js:71)
    at n (onloadwff.js:71)
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
new:1 Failed to load resource: the server responded with a status of 500 ()
new.js:1 Failed to load resource: the server responded with a status of 404 ()

Have you asked Alisa Shevchecko?

Hi @ccjjmartin, thanks for opening this issue. We've prioritized a fix, it's currently being deployed.
I'll update on this issue when it's ready.

@ccjjmartin Fix is deployed


Fix import paths to support better tree shaking

Importing directly from @material-ui/core is pulling in the entire bundle instead of the portions used.
This just updates the import paths across the app to use more direct imports which should allow for better tree shaking.

Coverage remained the same at 77.049% when pulling 56acb9c57235c813a548e22873d95b63812adb8b on nathancharles:treeShaking into 267c4cdb3a95fa48bc999beb786612f4dd215f59 on gregnb:master.

@gregnb any chance to get this merged?

Thank you for taking an interest in the project!
My understanding of imports is that the destructuring form of import { dep1, dep2, ... } from 'library' already supports tree shaking by pulling out only the dependencies that are being used, so I don't think this PR is necessary, as all the lines you changed already use the correct form as far as I can tell.

Based on this resource https://developers.google.com/web/fundamentals/performance/optimizing-javascript/tree-shaking/, and my own understanding, I believe this library already supports treeshaking in production builds. Without any further input on this in the next few weeks, I'll close the PR.


Pf1e Successful  Rolls show up green, then immediately turn red and "fail".

It's even set up to fail after 2 failed rolls. But I roll 1 success and after a quick vision of the green success bar, it turns red and the crafting is failed.
Very cool module. Hope it starts working for me soon.

I think its because the result is supposed to be a "scroll". I'll add it to a compendium and see if that works.

It works... I have to make an entire new compendium for scrolls =[.
Still a great module though

well fine that it works now for you. I still can not track what had been a problem you left too few clues.
Usually you do not need to have your results or ingredients come from compendiums but it is recommended as those items then are more stable while items imported into your world can be more easly be deleted or manipulated afterwards.

A recipe stores the link to the item not the item itself so when you delte an imported item your recipe will fail.

The scrolls in pf1 are "generated". There is no item sitting around called
"scroll of magic spell".
This didn't compute in my brain for the 30 minutes I was testing. Only
after I posted on here did it dawn on me.
100% user error. Module is perfect.
Tho I found it humorous that you named the list of recipes "compendium" yet
you cannot store them in a compendium.  :)
On Sat, Feb 10, 2024, 11:23 AM AngryBeaver @.***> wrote:

A recipe stores the link to the item not the item itself so when you delte
an imported item your recipe will fail.
—
Reply to this email directly, view it on GitHub
https://github.com/AngryBeaver/beavers-crafting/issues/121#issuecomment-1937088839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK3YV4SIIR3B7PYQT7422YDYS63KZAVCNFSM6AAAAABDCOFDAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGA4DQOBTHE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 196 ms

Resolved: ClamAV performance has improved in 73f53bc.


Transmission wont start & Permission Issues

I seem to get this output. when trying to install
sudo sh transmissionvpn.sh install
Installing ...
package transmission stop successfully
Binding IPv4 Home Address ...
chown: invalid user: vc-transmission:root
Failed to start package 272
Installed!

It seems like the user is supposed to be svc-transmission.

I did an update earlier and found some changes possibly related to the user and group change. Tested this on DSM 6.1.


Create fork/branch for Tech Demo and remove test code

As a presenter at the Tech Demo, I want to have a version of Platform.Bible to use that doesn't include all the test code so that I'm only highlighting things I want the audience to focus on.
This is probably most easily done as a separate branch, but whatever the team thinks is best is fine.

See the "tech-demo-2023-11" branch for the status here.  I think it's ready for the demo with the only potential change coming of an updated word list extension.


fix(ios, events): fix an issue with PlaybackQueueEnded resulting from…

… a race condition
https://github.com/doublesymmetry/react-native-track-player/issues/1598

This fixes a race condition affecting the PlaybackQueueEnded event on iOS. Previously we were firing this event based off of the playbackEnd event. When that event was fired we were checking to see if the queue had more items left to play by evaluating player.nextItems.count. However, this property was evaluating incorrectly due to a race condition. By the time the handler gets called, the nextItem.count has already been updated by the player so it can be off by a value of 1.
This was causing the PlaybackQueueEnded event to be fired on both the n AND the n - 1 track transitions.
I fixed it by moving the event firing to the PlaybackTrackChanged handler, which is more consistent.

@dcvz running one more test on this.

@dcvz so everything was working fine, but I decided to change player.currentIndex to index when firing the event. I wasn't seeing it but I realized this could be a race condition as well. It's safer to do it this way as that's the value we're using in the track-changed event too.
Sorry for triggering another 20min iOS build :/. Should've thought of that on initial implementation.

@dcvz ready for another approval

@dcvz Could you please consider releasing patch versions when ever such rather substancial bugs are fixed?


Improve related solvers card

We might want to add more than just image and title - maybe codebase under the title, though lots of the titles have the code base included in the title eg (interFoam ESI and interFoam Foundation) so leaving it without for now.


ctrl+shift+alt+forward/back not working

ctrl+shift+alt+forward/back not working on HP Chromebook 14 running Chrome OS canary 40. The only way I can get back to Chrome OS is by logging out.

You could try switching from your chroot to Chrome OS via the command line. In a chroot shell (terminal), enter: croutoncycle cros
Then you can switch from Chrome OS to your chroot via clicking on your chroot name in the 'crouton integration' extension window if you have it installed.

This one is like the common cold - similar symptoms but many potential causes!  I had a similar and long running issue( #1699) with my Asus C300. Finally solved by mkasick:
"I think I might've sorted this out in #2003. The only discrepancy is that the xserver-xorg-video-intel package that ships with trusty does not have the change the causes the problem, but utopic does. Installing an LTS backport or PPA version probably would though."
So check out #2003.  However, that patch was merged with the master on 11 Aug so if your version of the crouton installer is older than that, update it and then update your chroot.  If not, I'm afraid it's a different problem.
Chris

like the common cold

For sure!
Tried to install the newer version of xserver-xorg-video-intel from jessie-backports -- replacing 2:2.21.15-2+b2 with 2:2.99.917+git20160522-1~bpo8+1 -- to fix a bug with shadows on GTK-3 windows in GNOME 3.14
Anybody know if the Intel driver is causing problems in stretch? If not, I may trade in my jessie chroot for stretch.
$ croutonversion
crouton: version 1-20160518095657~master:fd37bb79
release: jessie
architecture: amd64
xmethod: xorg
targets: gnome
host: version 8172.47.0 (Official Build) beta-channel gnawty
kernel: Linux localhost 3.10.18 #1 SMP Wed Jun 1 23:05:52 PDT 2016 x86_64 GNU/Linux
freon: yes

Don't think there is anything actionable in the issue.


[BUG] distutils.ccompiler.CCompiler.has_function does not quote provided includes anymore

setuptools version
67.2.0
Python version
3.x
OS
Linux (but presumably applicable to all)
Additional environment information
No response
Description
As of 56a5b333b2a8064c000d18ac0629385100957db0 (setuptools 67.2.0), the distutils.ccompiler.CCompiler.has_function in the setuptools-provided distutils ceased to quote the provided includes in the generated test C file (here).
Therefore, the compilation of the generated test C file always fails.
Expected behavior
The provided includes should be quoted (as before the change) to retain compatibility with older code using this function.
How to Reproduce

Run the following test code on Linux:

# program.py
import distutils.ccompiler

# Check for `clock` function in the standard library
cc = distutils.ccompiler.new_compiler()
has_clock = cc.has_function('clock', includes=['time.h'])
print("Has clock:" , has_clock)

Output
With setuptools 67.2.0:
$ python program.py
/tmp/clocku2l593gf.c:1:10: error: #include expects "FILENAME" or <FILENAME>
    1 | #include time.h
      |          ^~~~
/tmp/clocku2l593gf.c: In function ‘main’:
/tmp/clocku2l593gf.c:3:5: warning: implicit declaration of function ‘clock’ [-Wimplicit-function-declaration]
    3 |     clock();
      |     ^~~~~
/tmp/clocku2l593gf.c:1:1: note: ‘clock’ is defined in header ‘<time.h>’; did you forget to ‘#include <time.h>’?
  +++ |+#include <time.h>
    1 | #include time.h
Has clock: False

With setuptools 67.1.0:
$ python program.py
Has clock: True

@fweimer-rh

@fweimer-rh, would it be possible to add quotes if the argument does not starts with " either <?

Should I send a PR to fix this?

I believe that a PR to pypa/distutils mentioning this bug in setuptools should be the way to go.


ADBDEV-6438: Fix temp_spill_files_tablespaces GUC sync

Fix temp_spill_files_tablespaces GUC sync
Previously GUC sync worked by sending SET commands to segments. However,
some values (for example the empty string for quoted GUCs) cannot be set this
way. This affects specifically temp_spill_files_tablespaces since "" and
"\"\"" have different semantic meaning for it.
This patch changes the way GUC sync works by using pg_catalog.set_config()
function instead of SET commands. This function sets the value of the GUC
directly without any quoting issues, and so now empty strings are handled
correctly.

Allure report https://allure.adsw.io/launch/82533

Allure report https://allure.adsw.io/launch/82585

new flaky?
DIFF FILE: ../gpdb_src/src/test/isolation2/regression.diffs
----------------------------------------------------------------------
--- \/home\/gpadmin\/gpdb_src\/src\/test\/isolation2\/expected\/parallel_retrieve_cursor\/privilege\.out	2024-10-09 14:33:17.456363204 +0000
+++ \/home\/gpadmin\/gpdb_src\/src\/test\/isolation2\/results\/parallel_retrieve_cursor\/privilege\.out	2024-10-09 14:33:17.476364248 +0000
@@ -165,7 +165,7 @@
 DECLARE
 2: @post_run 'parse_endpoint_info 3 1 2 3 4' : SELECT endpointname,auth_token,hostname,port,state FROM gp_get_endpoints() WHERE cursorname='c3';
  endpoint_id3 | token_id | host_id | port_id | READY
- endpoint_id3 | token_id | host_id | port_id | READY
+ endpoint_id3 | port_id f88b9906f0f2ecdc3e2fcfcd879a | host_id | port_id | READY
  endpoint_id3 | token_id | host_id | port_id | READY
 (3 rows)
 1: SELECT DISTINCT(cursorname), username FROM gp_get_endpoints();

Changed the logic of this patch to modify the way GUC sync works instead. This is a more general solution that would fix all empty string related issues, not just for temp_spill_files_tablespaces.

Allure report https://allure.adsw.io/launch/82636

Could you please add quotes to a couple of tablespaces to check that the quoted lists are installed correctly?
CREATE TABLESPACE "temp_files1'" LOCATION '@testtablespace@_temp_files1';
CREATE TABLESPACE "temp_files2""" LOCATION '@testtablespace@_temp_files2';

Allure report https://allure.adsw.io/launch/82892

Allure report https://allure.adsw.io/launch/82945

Allure report https://allure.adsw.io/launch/82970

Allure report https://allure.adsw.io/launch/83015

Allure report https://allure.adsw.io/launch/84025


[WIP] Change rewrite to return Optional object

Fix the title and write description something like - refactoing the rewrite api

Fix the title and write description something like - refactoing the rewrite api

Done

Commit message should be "Refactor Rewriter API" not "refactored".

Commit message should be "Refactor Rewriter API" not "refactored".

Done


Unsupported 16 bit application with winutils.exe for hadoop-3.0.0/bin

When running winutils.exe of hadoop-3.0.0/bin from command line on Windows 10 pro 21H1 I'm getting error saying that I'm trying to run unsupported 16bit application.
I thought this suppose to be a 64 version for winutils. Am I missing something here?
Thansk

win16 went away a long time ago, as we got stuff like "virtual memory" and "multitasking".
maybe you have a win32 box which got confused, but I'd be surprised.
anyway apache hadoop project is going to be releasing native windows binaries; closing as wontfix.


Added C++ example

As stated in title, simple c++ fizzbuzz
#2

Oops, closed it instead of merging.


Fix #3491 - FromSql query with complex Include not working

Need to consider Include annotations when determining if FromSql is composed
@anpete @maumar

:shipit:


Server won't accept rtmp-stream of Gopro Hero 8

I am running the server on macOS 10.15.4.
It works properly with several sources. But it won't run with my GoPro Hero 8. I tried it with 720p and 1080p.
The Server shows the red camera symbol but I don't get the stream output.

@christophzickler gopro max working just fine.


Claim function is not working

What is a problem?

I can't claim SLP token from the contract.

What I have try?

Deposit more SLP.
Check if lifetimeSLP is more than rewardDept.
Check if wallet address of sender in the list.

In claim function change "claimable - fee" to  "claimable - protocolFee"


Changing the version to v1.8.2 fails building the image.

It seems there is a change in the makefiles and building the image with a different version of Firmware fails.
Step 12/13 : RUN ["/bin/bash", "-c", "     cd ${FIRMWARE_DIR} &&     DONT_RUN=1 make px4_sitl gazebo &&     DONT_RUN=1 make px4_sitl gazebo "]
 ---> Running in fd627ab6b07b
Makefile:378: *** "px4_sitl cannot be the first argument. Use 'make help|list_config_targets' to get a list of all possible [configuration] targets.".  Stop.
The command '/bin/bash -c      cd ${FIRMWARE_DIR} &&     DONT_RUN=1 make px4_sitl gazebo &&     DONT_RUN=1 make px4_sitl gazebo ' returned a non-zero code: 2

If you go back to to v1.8.2 you also need to switch back to the older make target: make posix_sitl_default jmavsim.


Azure Service Bus Queue Python receiver.reconnect() call causes queue message deletion

I have found in V0.50.1 using the Python SDK that when using ReceiveAndDelete mode on the receiver, merely calling the receiver's reconnect() method after a disconnection causes a dequeue and deletion of the most recently added queue item:
Queue len = 6
Reconnecting...
Queue len after reconnect = 5
Please fix this ASAP if possible.

Thanks @rswgnu for reporting this our team will take a look at it!

@annatisch could you take a.look

Thanks @rswgnu  - I have written a short test to confirm this behaviour:
sb_client = ServiceBusClient.from_connection_string(conn_str, debug=True)
queue = sb_client.get_queue(standard_queue)

with queue.get_sender() as sender:
    for i in range(5):
        sender.send(Message(f"Message {i}"))

messages = queue.get_receiver(mode=ReceiveSettleMode.ReceiveAndDelete, idle_timeout=5)
batch = messages.fetch_next()
print(batch[0])
count = len(batch)

print("RECONENCTING")
messages.reconnect()
print("FINISHED RECONNECT")
for message in messages:
    print(message)
    count += 1
assert count == 5

And as you say - a message ("Message 1") always gets lost in the reconnect.
Output:
2019-09-18 07:28:09,791 uamqp.c_uamqp INFO     b'<- [ATTACH]* {receiver-link-c51cb0ab-f48e-4a7d-b4d3-1c07d994aefb,2,false,1,0,* {amqps://pysbtest.servicebus.windows.net/53b54470-b622-4d8c-8fbe-023b19669165,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL},* {SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9,NULL,NULL,NULL,NULL,NULL,NULL},NULL,NULL,0,1048576,NULL,NULL,NULL}'
2019-09-18 07:28:09,792 uamqp.c_uamqp INFO     b'-> [FLOW]* {2,65535,1,65535,2,0,1}'
2019-09-18 07:28:09,796 uamqp.receiver INFO     Message receiver b'receiver-link-c51cb0ab-f48e-4a7d-b4d3-1c07d994aefb' state changed from <MessageReceiverState.Opening: 1> to <MessageReceiverState.Open: 2> on connection: b'SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9'
2019-09-18 07:28:09,849 uamqp.c_uamqp INFO     b'<- [TRANSFER]* {2,1,<>,0,true,false,NULL,NULL,NULL,NULL,true}'
2019-09-18 07:28:09,850 uamqp.c_uamqp INFO     b'-> [FLOW]* {3,65534,1,65535,2,1,1}'
Message 0
RECONENCTING
2019-09-18 07:28:09,859 uamqp.c_uamqp INFO     b'-> [DETACH]* {2,true}'
2019-09-18 07:28:09,860 uamqp.connection INFO     Shutting down connection b'SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9'.
2019-09-18 07:28:09,863 uamqp.c_uamqp INFO     b'-> [DETACH]* {0,true}'
2019-09-18 07:28:09,864 uamqp.c_uamqp INFO     b'-> [DETACH]* {1,true}'
2019-09-18 07:28:09,875 uamqp.c_uamqp INFO     b'-> [END]* {}'
2019-09-18 07:28:09,877 uamqp.c_uamqp INFO     b'-> [CLOSE]* {}'
2019-09-18 07:28:09,879 uamqp.connection INFO     Connection shutdown complete b'SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9'.
2019-09-18 07:28:10,131 uamqp.c_uamqp INFO     b'-> Header (AMQP <IP_ADDRESS>)'
2019-09-18 07:28:10,185 uamqp.c_uamqp INFO     b'<- Header (AMQP <IP_ADDRESS>)'
2019-09-18 07:28:10,186 uamqp.c_uamqp INFO     b'-> [OPEN]* {SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9,pysbtest.servicebus.windows.net,65536,65535,NULL,NULL,NULL,NULL,NULL,{[product:servicebus.python],[version:0.50.1],[framework:Python 3.7.4],[platform:win32]}}'
2019-09-18 07:28:10,240 uamqp.c_uamqp INFO     b'<- [OPEN]* {03c263b2d4f1468e9d45485821064836_G31,NULL,65536,4999,240000,NULL,NULL,NULL,NULL,NULL}'
2019-09-18 07:28:10,241 uamqp.c_uamqp INFO     b'-> [BEGIN]* {NULL,0,65536,65536,4294967295}'
2019-09-18 07:28:10,298 uamqp.c_uamqp INFO     b'<- [BEGIN]* {0,1,5000,65536,255,NULL,NULL,NULL}'
...
2019-09-18 07:28:10,480 uamqp.c_uamqp INFO     b'-> [ATTACH]* {receiver-link-dade5557-9f18-4d23-9b95-9619e10cbd3a,2,true,1,0,* {amqps://pysbtest.servicebus.windows.net/53b54470-b622-4d8c-8fbe-023b19669165},* {SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9},NULL,NULL,NULL,1048576}'
2019-09-18 07:28:10,592 uamqp.c_uamqp INFO     b'<- [ATTACH]* {receiver-link-dade5557-9f18-4d23-9b95-9619e10cbd3a,2,false,1,0,* {amqps://pysbtest.servicebus.windows.net/53b54470-b622-4d8c-8fbe-023b19669165,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL},* {SBReceiver-eb27c68a-2d84-4b8b-b888-8bb131b881e9,NULL,NULL,NULL,NULL,NULL,NULL},NULL,NULL,0,1048576,NULL,NULL,NULL}'
2019-09-18 07:28:10,594 uamqp.c_uamqp INFO     b'-> [FLOW]* {2,65535,1,65535,2,0,1}'
FINISHED RECONNECT
2019-09-18 07:28:10,654 uamqp.c_uamqp INFO     b'<- [TRANSFER]* {2,1,<>,0,true,false,NULL,NULL,NULL,NULL,true}'
2019-09-18 07:28:10,654 uamqp.c_uamqp INFO     b'-> [FLOW]* {3,65534,1,65535,2,1,1}'
Message 2
2019-09-18 07:28:10,712 uamqp.c_uamqp INFO     b'<- [TRANSFER]* {2,2,<>,0,true,false,NULL,NULL,NULL,NULL,true}'
2019-09-18 07:28:10,713 uamqp.c_uamqp INFO     b'-> [FLOW]* {4,65533,1,65535,2,2,1}'
Message 3
2019-09-18 07:28:10,766 uamqp.c_uamqp INFO     b'<- [TRANSFER]* {2,3,<>,0,true,false,NULL,NULL,NULL,NULL,true}'
2019-09-18 07:28:10,767 uamqp.c_uamqp INFO     b'-> [FLOW]* {5,65532,1,65535,2,3,1}'
Message 4
2019-09-18 07:28:15,853 uamqp.client INFO     Timeout reached, closing receiver.

However the client is showing no indication that a frame was ever received during the reconnect process. This could indicate that the service is sending a frame that the client either never receives or it's being immediately discarded because the connection is already in a shutdown state.
I will investigate whether we can improve the behaviour here, however please bear in mind that loss of messages during an connection interruption will always be a risk when using ReceiveAndDelete mode. So if receipt of every message is important, please use PeekLock mode.

it's being immediately discarded because the connection is already in a shutdown state.

Could you explain the above further?
I understand if something like a power outage happens when a client is trying to read a message from a queue that the message may be lost but the queue should not be dropping messages prior to read attempts being made; it should be persistent subject to whatever "time-to-live" policy is given for the queue (regardless of the state of a client).  ServiceBus disconnects clients pretty rapidly in my experience so reconnects are needed all the time and should not affect any items in the queue.  Do you agree with this?
There was a specific reason we chose not to use PeekLock mode though I do not recall it right now.

Thanks @rswgnu - yes I agree - I would think dropping messages due to disconnect/reconnect should be an exceptional case rather than normal behaviour - so I certainly need to do a deeper investigation into the C library to ensure that incoming messages are not being needlessly discarded (as opposed to discarded because they were received erroneously).

Ok, great.  Also, I am pretty sure I verified that the receiver is not in a shutdown state yet the message is still dropped whenever a reconnect is done.  If there were a way we could keep connections open for hours at a time as we would like to do (because we would only have a few clients accessing our queue at a time), then that would help us as well and we wouldn't need the reconnects generally.  Is there any way to do that?

A reconnect is generally performed due to an error in one of the connection/link/authentication - so keeping the connection open is not always an option. Therefore if a reconnect is performed, the receiver would have been in a shutdown state at some point... though it possible that state has not been surfaced to the client due to some kind of error.
Do you know under what circumstances a reconnect is being performed in your case?

I am manually calling reconnect after the receiver is forcibly disconnected from the queue.  Prior to that I was just recreating the receiver to dequeue each item and that did not work properly either as I recall.  The disconnection is incredibly fast relative to the rate at which we want to dequeue items.

Ah that's interesting.
I confess that the reconnect function was never intended to be manually called - however that's on me as I never explicitly marked it as internal either...
Do you notice that messages are still dropped if you use your previous implementation of recreating the receiver each time? I would suspect that the behaviour should be the same and am very curious as to what you observed.

Yes, that is why I then tried using reconnect.  Personally, I think it would be handy to have as part of the API because why do we want to recreate the receiver locally just because the other end of the connection dropped?  Reconnect should be lighter and faster.

Hi Anna:
What is the status.  We need some resolution on this ASAP as it is a blocking bug.  Please let us know if someone is working on this on a daily basis or not.  Thanks.  Full sample code with a valid workaround would work as well.

Hi @rswgnu - yes I am currently working on this alongside a couple of other open issues for the Service Bus library.
Though I would recommend using PeekLock mode as a short term work around for this issue - you mentioned that there's a specific reason you can't, so it would be good to hear more about this to determine whether there's something else that needs to be resolved.

An I just reopen the receiver connection each time I want to dequeue a message and avoid using reconnect?  If not, I will have to revert to PeekLock and all that entails.
-- Bob

On Sep 25, 2019, at 11:53 AM, annatisch<EMAIL_ADDRESS>wrote:
Hi @rswgnu - yes I am currently working on this alongside a couple of other open issues for the Service Bus library.
Though I would recommend using PeekLock mode as a short term work around for this issue - you mentioned that there's a specific reason you can't, so it would be good to hear more about this to determine whether there's something else that needs to be resolved.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't think so - I believe the missing message is happening during either shutting down, or opening a new connection. So either way this is achieved (reconnect or reopen) I think the same behaviour would occur. Therefore I would recommend PeekLock until I can isolate where the missing bytes are going...

Hi @rswgnu -I have finally isolated the root cause of this issue and am working on a fix for it now :)

I have a PR open with a potential fix here:
https://github.com/Azure/azure-uamqp-python/pull/96
And preview builds of uAMQP can be download here:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=119291
The fix for this issue requires no changes to the Service Bus SDK.
So it would be great if you could try out the updated uAMQP to see whether it resolves the issue for you.

Could you provide a step-by-step description for substituting your uAMQP version for the standard one in the SDK, so I don't have to figure it out and can test this faster?  Thanks.

Sure, so start by downloading the uAMQP build according to your platform from below:
Latest build: https://dev.azure.com/azure-sdk/public/_build/results?buildId=121096
Then you should simply be able to install it into your test/dev/local environment:
pip install --upgrade path/to/local/uamqp.whl

Then you should simply be able to re-run your existing tests/code that would have previously reproduced the bug.

With the new uamqp library, as long on the Azure Service Bus queue receiver connection stays open, then dequeing now works properly.  But of course the connection closes fairly rapidly so we need to know the lowest-cost code to re-establish the connection given a prior good handle for the receiver.  Calling get_receiver again (creating a new receiver object) seems to work but we really want something like the reconnect you exposed previously.  How should we handle this?

Could you get this fix into production quickly so we could just update through normal pip channels?  We deploy to multiple virtual machines and share our Python virtual environments, so it would be a bit of a mess to install a custom library into our production servers.

Great - thanks for the feedback @rswgnu!
The reconnect function you were using previously should now also be fixed with this patch.
I will not be "unexposing" the reconnect functionality, and have now added test cases for this scenario - so you should be able to use reconnect again.
All going well we plan to have this update published to PyPI early next week.

Sounds good.  I will test reconnect tomorrow.
-- Bob

On Oct 1, 2019, at 6:25 PM, annatisch<EMAIL_ADDRESS>wrote:
Great - thanks for the feedback @rswgnu!
The reconnect function you were using previously should now also be fixed with this patch.
I will not be "unexposing" the reconnect functionality, and have now added test cases for this scenario - so you should be able to use reconnect again.
All going well we plan to have this update published to PyPI early next week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Anna:  reconnect() is not working if the only change I install is your updated uamqp code.  I get a connection is in unknown state after doing a reconnect().  Please explain any other changes that need to be applied and show a simple use of reconnect() where you wait for 5 minutes (sleep(300)) and then do a reconnect().

Here is my debug output:
INFO:main:Task # 0 "old" command, uuid: 63e169d2-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 0 "old" command: Q Size: 1; Task Addr:<PHONE_NUMBER>74560; JSON: {"cmd_type": "old", "cmds": ["a", "b", "c"], "output_file": null, "number": 0, "at": null, "at_start": null, "at_end": null, "uuid": "63e169d2-e52b-11e9-bdde-f43909d9b385"}
INFO:main:Task # 1 "old" command, uuid: 644891ac-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 1 "old" command: Q Size: 2; Task Addr:<PHONE_NUMBER>73440; JSON: {"cmd_type": "old", "cmds": ["b", "c", "d"], "output_file": null, "number": 1, "at": null, "at_start": null, "at_end": null, "uuid": "644891ac-e52b-11e9-bdde-f43909d9b385"}
INFO:main:Task # 2 "old" command, uuid: 64aff23e-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 2 "old" command: Q Size: 3; Task Addr:<PHONE_NUMBER>74112; JSON: {"cmd_type": "old", "cmds": ["c", "d", "e"], "output_file": null, "number": 2, "at": null, "at_start": null, "at_end": null, "uuid": "64aff23e-e52b-11e9-bdde-f43909d9b385"}
INFO:main:Task # 3 "old" command, uuid: 65173818-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 3 "old" command: Q Size: 4; Task Addr:<PHONE_NUMBER>73216; JSON: {"cmd_type": "old", "cmds": ["d", "e", "f"], "output_file": null, "number": 3, "at": null, "at_start": null, "at_end": null, "uuid": "65173818-e52b-11e9-bdde-f43909d9b385"}
INFO:main:Task # 4 "old" command, uuid: 657da31e-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 4 "old" command: Q Size: 5; Task Addr:<PHONE_NUMBER>73776; JSON: {"cmd_type": "old", "cmds": ["e", "f", "g"], "output_file": null, "number": 4, "at": null, "at_start": null, "at_end": null, "uuid": "657da31e-e52b-11e9-bdde-f43909d9b385"}
INFO:main:Task # 5 "old" command, uuid: 65ee15ea-e52b-11e9-bdde-f43909d9b385: enqueued
Enqueued Task # 5 "old" command: Q Size: 6; Task Addr:<PHONE_NUMBER>57360; JSON: {"cmd_type": "old", "cmds": ["f", "g", "h"], "output_file": null, "number": 5, "at": null, "at_start": null, "at_end": null, "uuid": "65ee15ea-e52b-11e9-bdde-f43909d9b385"}
Queue len = 6
INFO:main:  Task # 0 "old" command, uuid: 63e169d2-e52b-11e9-bdde-f43909d9b385: dequeued
Dequeued Task # 0 "old" command: Q Size: 5; Task Addr:<PHONE_NUMBER>72432; JSON: {"cmd_type": "old", "cmds": ["a", "b", "c"], "output_file": null, "number": 0, "at": null, "at_start": null, "at_end": null, "uuid": "63e169d2-e52b-11e9-bdde-f43909d9b385"}
Pausing for 5 minutes to check handling after timeouts...
Queue len = 5
WARNING:uamqp.connection:ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.')
Trying to dequeue when queue is empty...
Queue len = 5
Reconnecting...
Queue len after reconnect = 4
Queue len after _used cleared = 4

Thanks @rswgnu - can I confirm whether the code you're running looks roughly similar to the test I have here:
https://github.com/Azure/azure-sdk-for-python/pull/7453/files#diff-7c1b8fc70db3a3f3f724231ff9a11da5R62

Yes, fairly similar with a longer delay between reconnects.

Can you replicate the reconnect problem?  Any movement on it yet?

No - I am unable to reproduce any further issues here.
I bumped the delay to 5 minutes but the test still passed.
Current plan is to release the fix as it is early next week and we will reassess status at that time.

Ok, thanks.

The updated uAMQP (v1.2.3) is now released. You should be able to install with:
$ pip install --upgrade uamqp

That’s very good news.
-- Bob

On Oct 7, 2019, at 6:17 PM, annatisch<EMAIL_ADDRESS>wrote:
The updated uAMQP (v1.2.3) is now released. You should be able to install with:
$ pip install --upgrade uamqp
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@rswgnu : Looking forward to your feedback on this

Creating a new receiver object with each get/read works properly now but if I reuse the receiver object, it times out and I can’t find a working method to reconnect.  The reconnect() method does not work after the time out.
Please send the most basic reconnect code you can, using a time.sleep(300) delay between reconnects and dequeues and I will test that.
Thanks,
-- Bob

On Oct 9, 2019, at 6:07 PM, Mayuri Diwan<EMAIL_ADDRESS>wrote:
@rswgnu : Looking forward to your feedback on this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

See my prior comment.  Can we get some followup on this so we don't have to create a new receiver object every time we dequeue a message?  Thanks.

Has there been any resolution on this one?  I believe we are seeing something similar.  I've moved to uamqp v1.2.5 but still seeing exceptions after a connection has gone unused for a few minutes.

Hey folks,
First let me apologize that this sat for so long.
Second, to address the (what I believe are) two distinct points here.

receiver reuse.
Unfortunately in the 0.50.* versions, reuse of the push handler (for message in receiver vs the pull handler fetch_next) was explicitly not allowed due to issues with connection/credential state.  This has been mitigated in the version of this lib pending GA, currently in preview (7.0.0b2 latest), you will be able to call for message in receiver again even if it was already called and exited prior.  That said, I'd still be very surprised that creating a new receiver for each message would be required.  In the occasion that the receiver was terminated for whatever reason, would it not be sufficient to fetch another in the error handler?  E.g. a pattern as such:

while True:
    with queue_client.get_receiver() as receiver:
        try:
            for message in receiver:
                time.sleep(5) #some arbitrary processing
                message.complete()
        except:
            continue

        A similar approach should be workable using fetch_next for the inner loop, if that pattern is
        desired.  Don't hesitate to let me know if I've missed the motivation for why creating a new
        receiver per-message would be needed as a workaround, since as I understand it anna's fix
        addressed the dropped-message issue.

unused connection expiry.
  I'm hoping that this is distinct, and merely incurring the pain of item 1 when it occurs.
  (Rooted in a service-side disconnect at 10 minutes which we mitigated in a recent patch release)
  We've been triaging this with engebret across a few other issues, see #9144 and uamqp #135

Just wanted to mention that we've officially released ServiceBus 0.50.3 which contains the aformentioned fixes for the long-term service side connection disconnect.
I would hope between this and the aformentioned call patterns the issues here are mitigated; if there's any recurrence of this or further questions don't hesitate to reopen and/or reach out.


edit menu not positioned correctly for media

New issue checklist

[x] I have read the README, documentation, and FAQ.
[x] Contributing guidelines confirmation: ____
[ x I have searched existing issues and this is not a duplicate.

General information

JSQMessagesViewController version: https://github.com/jessesquires/JSQMessagesViewController/commit/45fdac769d7354ad19e5990dadbfee285a2e45ee
iOS version: 10.3
Devices/Simulators: iPhone 7, Sim 6s, probably affects all others as well.
Reproducible in the demo project? Yes
Any related issues: https://github.com/jessesquires/JSQMessagesViewController/issues/1722

What happened?
Edit menu is not positioned correctly for media cells.

It should be centered over the cell as it is for text messages.

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


[MINOR] add test_createDataFrame_empty_partition in pyspark arrow tests

What changes were proposed in this pull request?
add test_createDataFrame_empty_partition in pyspark arrow tests
Why are the changes needed?
test edge cases.
Does this PR introduce any user-facing change?
no.
How was this patch tested?
N/A

Merged build finished. Test PASSed.

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

Test build #127276 has started for PR 29398 at commit cda9d54.

Test build #127276 has finished for PR 29398 at commit cda9d54.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Merged to master and branch-3.0.


Suggestion: router.beforeRoute

Currently we need to create rules of the type in each group of routes
routes: [{
  path: 'panel/accounts',
  component: AccountsComponent,
  children: [...],
  // access rules
  meta: { rules: ['admin'] },
  // or
  beforeEnter (to, from, next) {
    //...
  },
}]

Initially this approach is efficient, cut in more complex systems can easily become complex, because it is very fragmented.
router.afterEach helps a lot, however it is very easy to have a lot of code to keep, with many rules.
router.beforeRoute will be a more modular solution
router.beforeRoute('panel/*', (to, from, next) =>  {...})
router.beforeRoute('panel/accounts/*', (to, from, next) =>  {...})
router.beforeRoute('accounts/:id', (to, from, next) =>  {...})

I believe this is much simpler to maintain and componetize the routes, maybe even helping with integrations with vuex
Issues that may be helped with this: #938 #958

Hi, thanks for filling this issue. If you need a modular solution, you can  simply use in-component guards, and define beforeRouteEnter inside components.

In component hook beforeRouteEnter called before any properties of the component initialized thus VUEX mapActions throw an error.


USpudPropertyUtil::GetLogPrefix hasn't got an implementation

I'm getting the following linker errors while building the latest commit in VS2019 against UE4.26.2:
1>Module.SPUD.cpp.obj : error LNK2019: unresolved external symbol "public: static class FString __cdecl SpudPropertyUtil::GetLogPrefix(int)" (?GetLogPrefix@SpudPropertyUtil@@SA?AVFString@@H@Z) referenced in function "protected: void __cdecl USpudState::RestoreObjectProperties(class UObject *,class FMemoryReader &,struct FSpudClassMetadata const &,class TMap<struct FGuid,class UObject *,class FDefaultSetAllocator,struct TDefaultMapHashableKeyFuncs<struct FGuid,class UObject *,0> > const *,int)" (?RestoreObjectProperties@USpudState@@IEAAXPEAVUObject@@AEAVFMemoryReader@@AEBUFSpudClassMetadata@@PEBV?$TMap@UFGuid@@PEAVUObject@@VFDefaultSetAllocator@@U?$TDefaultMapHashableKeyFuncs@UFGuid@@PEAVUObject@@$0A@@@@@H@Z)
1>Module.SPUD.cpp.obj : error LNK2019: unresolved external symbol "public: static class FString __cdecl SpudPropertyUtil::GetLogPrefix(class FProperty const *,int)" (?GetLogPrefix@SpudPropertyUtil@@SA?AVFString@@PEBVFProperty@@H@Z) referenced in function "protected: static bool __cdecl SpudPropertyUtil::TryReadPropertyData<class FBoolProperty,bool>(class FProperty *,void *,struct FSpudPropertyDef const &,int,class FArchive &)" (??$TryReadPropertyData@VFBoolProperty@@_N@SpudPropertyUtil@@KA_NPEAVFProperty@@PEAXAEBUFSpudPropertyDef@@HAEAVFArchive@@@Z)

This appears to be caused by the missing implementation of USpudPropertyUtil::GetLoginPrefix

Thanks for reporting, not sure how I missed that, fixed in 4186ff8d91dfcd6ea135899ee3d12aee48903331

Thank you! 👍

Hello Steve,
I saw this as well, when I was setting up the sanity check of trying to repro this issue using just your SPUDExamples project.
I performed a fresh git clone of that repro and then ran the 2 submodule commands as shown in the help there, but these link errors were still present. I ended up diffing with my separate test project which had SPUD from this repo and noticed the implementations were missing in SPUDExamples (as well as the other edits from https://github.com/sinbad/SPUD/commit/4186ff8d91dfcd6ea135899ee3d12aee48903331). I haven't worked with submodules in git before, but it seems like maybe SPUDExample's submodule reference to this repo is a commit behind?
Thanks,
Anthony

Ah yes I forgot to update SpudExamples to pick up the update, that's done now. Thanks for letting me know.


implement support for rdfs:isDefinedBy in linker

The OBO foundry will be rolling this out soon so we should prioritise it over the current prefix checking, which will fix issues like BFO_0000050 actually being defined in RO. Can test with
robot merge -I http://purl.obolibrary.org/obo/pato.owl -I http://purl.obolibrary.org/obo/ro.owl --annotate-defined-by true -o defined-by.owl

Also we should drop isDefiningOntology from owl2json and populate it in the linker instead ("= is the current ontology ID in the definedBy list after linking").

now part of #222


Find a testing solution

As stated in #41, we should find a proper way to test the portfiles.
An ideal system would be to automatically test new/updated portfiles after each push and ignore those which were untouched.

Maybe at least do dry-run for all packages? To check syntax error in portfile.cmake

As highlighted in https://github.com/Microsoft/vcpkg/issues/77  , a possible bug/regression is that a given package compiles and install correctly, but can't be found from a CMake downstream project.
Having per-package simple tests (like the example attached to  https://github.com/Microsoft/vcpkg/issues/77) that are compiled every time the package changes could help preventing such regressions.

conan, for example, has test_package command that will try compile simple project that use package

Our main issue, there, is to handle scalability.
As the number of provided libraries grows, the time taken to pass the testing will get bigger and bigger.
We need to find a way to only test the packages that have changed.

@KindDragon @traversaro I really like the idea of checking in a simple project which should work if the package was built correctly. Perhaps a ports\<port>\test\ directory which can contain a CMakeLists.txt that builds an executable called main.exe?
One issue that would need working around is that we currently only support pulling libraries from the installed\ directory, but we'd really rather check the packages before installing them. Off the top of my head, this should be as easy as tacking another directory onto the CMAKE_PREFIX_PATH variable, but it'll require some trial and error.
@Ninetainedo Perhaps it could be as easy as just running git diff HEAD~ --stat and grepping the output:
PS D:\src\vcpkg> git diff HEAD~ --stat
 toolsrc/src/commands_help.cpp | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

If we look for changes of the form ports/<name>/....., that would list every port that was touched. This still would have scaling problems w.r.t. deep dependency chains, and lots of packages will be testing boost, but it should help things quite a bit. If we use AppVeyor like your PR suggested, we can also (possibly) cache a copy of the system.

@ras0219-msft Yeah, you're right, parsing the output of a git command might be enough.
This means that we should test each push properly. Otherwise, we might miss a portfile modification.

I'd like to point out, that just testing changed port files - while certainly the most important part - may not be enough. You also need to check if the dependencies still build when you e.g. upgrade a library.
Also, as I mentioned in the referenced issue: Couldn't Microsoft perform a regularly scheduled build of all libraries on their internal servers to check for compatibility issues.
This wouldn't deliver the same kind of feedback as a per port test that would run for each PR, but it complement them (think about Unit vs integration testing)

From #923:

As there is no visible ci going on I was wondering if the MS Team actually checks if all the portfiles work correctly (on which platform / with which compiler / are you running any tests / any test projects?). And if the library versions in the master branch play "nice" together or if there are any incompatibilities.
Especially when less experienced people like me are trying to write a non-trivial portfile or upgrading an existing one it would be nice to have more feedback than just: "It seems to work on my machine"

CI / unit testing / integration testing
While nowhere near as visible as it needs to be, we do have a limited amount of CI that runs on every change to the master branch. You can see some checkmarks beside many of the commits in https://github.com/Microsoft/vcpkg/commits/master. I've also just added the current status badge to our front-page README as well.
This CI system does the following (Win10+VS2017):

bootstrap
recursively purges all out-of-date libraries
build a "core" set, including their dependencies under several flavors

This core set includes azure-storage-cpp opencv protobuf chakracore libuv and several others

[todo: we should check in the script for this, at least as documentation.]
We also do (irregularly) build all ports -- the results from last time showed 6 failing ports (and 3 cascaded) out of ~170 under x86-windows[1]. Most issues we see day-to-day are unfortunately ones that this style of CI system can't reasonably catch: they're due to unique combinations of client and port, such as having files under "C:\OpenSSL" (which confused find_package(OpenSSL) -- fixed!) or having a "site-config.jam" (which confused the boost build -- not fixed ☹).
It would be really awesome to have a dashboard for this! Something like a "sticky" GitHub issue would be ideal, but unfortunately the closest we have to that is perhaps a wiki page? We need to do some research to find the best option. I'd really appreciate links to all your favorite projects in this regard -- who does this the best?
Testing techniques
Today we don't run any tests beyond the build+post-package lint for libraries built inside Vcpkg. This is definitely an area which needs improvement! There are a few obvious ways we can improve testing:

Use the tests inside the library -- what to do about flaky tests?
Provide an example program for each port -- would serve as great documentation!
Build all the ports that depend on the "port under test" -- the CI system above does this for core libraries like boost and openssl, but it would be good to expand this for all update PRs
Expand our automatic post-package tests -- these are great for catching packaging errors like "I accidentally built the wrong architecture" or "I forgot to copy over the include files"

As mentioned in a previous comment, there are some additional core capabilities we need to support some of these. We would need to expand the buildsystem integration to allow pulling from a package's temporary directory before installation.
[1] The failing ports were:
clockutils (since fixed)
hdf5 (since fixed)
libmysql (since fixed)
nana (since fixed)
qt5 (since fixed)
spirv-tools

@ras0219-msft perhaps it is intended to be like that, but if you click on the checkmarks in https://github.com/Microsoft/vcpkg/commits/master , you need to be logged (I guess with some Microsoft/Visual Studio account) to see the results of the CI.

Just to add my 2c
I've been maintaining a little repo (https://github.com/jumpinjackie/vcpkg-port-tests) of little test applications that are sanity tests for vcpkg ports that I am personally interested in or port additions/updates that are currently in the PR queue.
Maybe you could have something like my test.ps1, but parameterized so that you can run it against any incoming PR and the ports that they affect.

In terms of #3431 , I think port testing should be considered as default operation and a portfile has to either run some tests (using vcpkg_test_cmake or other scripts) or define VCPKG_POLICY_NO_TEST just like other policies. And afterwards, this could be confirmed by post-build validation of vcpkg.

@cmpute It is better to provide not only vcpkg_test_cmake but vcpkg_test_msbuild or other scripts for test coverage on varying  build environment. An idea to define VCPKG_POLICY_NO_TEST is good and I'd like to ask a way to define a policy such as "some package is provided for msbuild but no guarantee for cmake build."
It is time consuming and complex task for contributors to test it on every different platform and build system matrix, so contributors may test only on their favorite platform and VC version with favorite build system.

A seemingly dumb question: with Azure Pipelines having unlimited CPU time for building OSS projects for CI/CD purposes, can't we hook all of this testing into that?
#921 should also be added to testing. The route proposed by #3107 is a nice addition for testing the validity of a build, but it doesn't indicate that the install layout is compatible with the potentially patched package config files. That only becomes apparent once an external application tries to consume it in the intended way, which brings us back to providing a fleshed out minimal example of invoking a single function from the dependency, proving headers and linking is right.
And yes, it should be done for all downstreams as well. Building all of Vcpkg in this manner centrally is not feasible IMHO. It can only be done incrementally, enforcing it after a given point for all package updates.
My problem is that nobody is bugging me to fix (or even find out if it needs fixing) my ports for Linux. I feel that a significant proprpotion of the packages have not been touched since Vcpkg went cross-platform and many packages have not been tested on Linux, not to mention OSX. CI/CD could really help out in that regard.

Closed as complete.


HTTP/2 HelloWorld Client Example Bug

Motivation:
The HTTP/2 helloworld client example has 2 bugs:

HttpResponseHandler has a map which is accessed from multiple threads, but the map is not thread safe.
Requests are flushed and maybe completely written and the responses may be received/processed by Netty before an element is inserted into the HttpResponseHandler map. This may result in an 'unexpected message' error even though the message has actually been sent.

Modifications:

HttpResponseHandler should use a thread safe map
Http2Client shouldn't flush until entries are added to the HttpResponseHandler map

Result:
Fixes https://github.com/netty/netty/issues/6165.

@zmyer @vongosling - FYI

Cool, we will have  a try :-)

4.1 (d771526)


BUG: Need to have a Harmonised view of IAK Public Key

Current Veraison Provisioning requirement is:
To have a IAK Key encoded in CoMID as:
The IAK public key is a PEM-encoded as SubjectPublicKeyInfo [RFC5280]
However in the Verifier code base, we need a proper PEM Key with PEM Header:
"--BEGNI PUBLIC KEY---"
So we need to check:
Agree on a consistent format between the Provisioning and the Verification Entity
Ensure that whatever Veraison format is : "User Friendly for Community members"

Users can generate the Public Keys easily.

Users are able to introduce the keys easily in the CoMID for provisioning.

Users can easily access the Private Key to sign the Attestation token containing the Evidence Claims

This has been resolved by https://github.com/veraison/services/commit/f26d1b17ba65e6bb1d5130d50fa9ecc6844766cc


docs: mention warmup in example

see https://github.com/tinylibs/tinybench/pull/50 / comments
previously, readme didn't really mention you should use .warmup().

Thank you so much


KeyError: 'paper_id'

Whats the issue here? After running the python train.py command as in read me. This error shows up

[2020-04-21 12:36:18,824 INFO] * number of parameters: 109483009 [2020-04-21 12:36:18,824 INFO] Start training... [2020-04-21 12:36:18,827 INFO] Loading train dataset from ../bert_data/cnndm.train.123.bert.pt [2020-04-21 12:36:18,934 INFO] Loaded train dataset from ../bert_data/cnndm.train.123.bert.pt, number of examples: 2001 Traceback (most recent call last):   File "train.py", line 395, in <module>     train(args, device_id)   File "train.py", line 323, in train     trainer.train(train_iter_fct, args.train_steps)   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/trainer.py", line 142, in train     for i, batch in enumerate(train_iter):   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/data_loader.py", line 175, in __iter__     for batch in self.cur_iter:   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/data_loader.py", line 274, in __iter__     for idx, minibatch in enumerate(self.batches):   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/data_loader.py", line 260, in create_batches     for buffer in self.batch_buffer(data, self.batch_size * 50):   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/data_loader.py", line 243, in batch_buffer     ex = self.preprocess(ex, self.is_test)   File "/content/drive/My Drive/i_have_no_idea/BertSum/src/models/data_loader.py", line 231, in preprocess     paper_id = ex['paper_id'] KeyError: 'paper_id'

How did you solve it?


Update of [Can I deploy a DHCP server in a VNet?]

[Enter feedback here]
Update of [Can I deploy a DHCP server in a VNet?]
According to the following statement, I think now we can deploy a DHCP server in a VNet.
on-premise client → on-premise DHCP server (relay) →  ExpressRoute/VPN  → Azure VM DHCP server
"You can deploy a DHCP server on a VM with the intent to receive unicast DHCP relay (source port UDP/67, destination port UDP/67) DHCP traffic. A possible scenario is configuring DHCP relay from devices on-premises to an Azure VM running a DHCP server. Customer is responsible for configuring on-premise devices (for example, router configuration) to create this DHCP relay traffic to the VM's IP in Azure."
However, the following statement says unicast DHCP traffic is not supported.
Should we update the following statement?
"You cannot deploy your own DHCP service to receive and provide unicast/broadcast client/server DHCP traffic for endpoints inside a VNet."
Our customer read this docs and is so confused.
Please have a check. Thank you!

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

ID: 07cec477-f584-400f-889c-9a5403f34bad
Version Independent ID: f777fdfd-2f5a-56b9-574f-ae6d2b19f130
Content: Azure Virtual Network FAQ
Content Source: articles/virtual-network/virtual-networks-faq.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

@yanxiu08 , thank you for your feedback. We have assigned this to the content owner/author for review.
@asudbring , for your review.

@yanxiu08
Using a DHCP server as a relay is the only configuration supported in Azure.  Will rework the wording to make it more clear.
#please-close


Improve debug messages in validate_bearer_token()

I was having issues with the token validation and decided to add a couple of changes to improve the displayed messages:

To enable logging I have added at the top of my file:
flog = logging.getLogger('flask_oauthlib')
flog.addHandler(logging.StreamHandler(sys.stdout))
flog.setLevel(logging.DEBUG)

Why do you need those print in the tests?

@lepture I was debugging the tests so I was adding "print" statements -- see my latest commit where I removed all print messages https://github.com/lepture/flask-oauthlib/pull/271/commits/3f71212f60bae29c83824e2a2190410440011c30

@indera Hi, I've updated the codebase. Better close this PR with a new PR.


URL parameters should be java.net.URL, not String

I have a working implementation of this, I'm just waiting for https://github.com/Azure/autorest.java/pull/113 to get merged before I submit the pull request.


https://jira.desk.technology/browse/MSDKI-53

@eldark88 please review

@nartiles looks good, just one comment

@eldark88 please take a look at last commit

@nartiles :shipit:


There is an incorrect error message 'Destination blob name cannot be empty' if using '/' as the destination blob name in the 'Clone and Rehydrate' dialog

Storage Explorer Version: 1.22.0-dev
Build Number: 20211013.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.6
Architecture: ia32\x64
How Found: Ad-hoc testing
Regression From: Not a regression
Steps to Reproduce

Expand one non-ADLS Gen2 storage account -> Blob Containers.
Create a blob container -> Upload one blob -> Update the access tier to 'Archive'.
Right click the blob -> Click 'Clone and Rehydrate'.
Input '/' as the destination blob name -> Click 'Apply'.
Check whether there is a correct error message.

Expected Experience

There is a correct error message.
There is an error message 'Name must not be empty or contain slashes.' when cloning a blob if using '/' or '\' as the name.

Actual Experience
There is an incorrect error message.

Additional Context
If using '\' as the destination blob name, there is a folder with no name that contains a blob with no name.
Here is the screenshot:

@JasonYeMSFT, if using '/' as the destination blob name, display the error message 'Destination blob name cannot be empty.'. This error message doesn't make sense to me. Could you help to take a look on this?


Prevent unnecessary shared_ptr copies by accepting a value in SHAMapInnerNode::setChild

High Level Overview of Change
Because SHAMapInnerNode::setChild takes a shared_ptr const &, every node insertion requires a shared_ptr copy, which causes an increment/decrement of the refcount in the object. This PR makes  SHAMapInnerNode::setChild  take a value which is moved into place.

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ x] Refactor (non-breaking change that only restructures code)
[ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

This does not cause any functional change.

(note from discussion: we'd like 1 more review of this)


Provide example of how to convert toml to dictionary compatible with get_version()

The docs do not show how to convert a toml file to a dictionary to provide to the config value of get_version().
It is neither intuitive, straightforward or documented. I spent time going through the test suite and thought that perhaps Config.parse_toml_file() was what I should do before I figured out that you needed to navigate deeper into the dictionary before get_version() could consume the file converted to a dictionary.

I added a variant of this to the new docs in commit 8b88a87.


Add yarn test:watch task for more enjoyable testing

Add yarn test:watch which gives you a testing mode much faster than
simply running yarn test. With test watch webpack only needs to do the
expensive bundle once and then will watch file changes with incremental
builds, making subsequent test runs very quick.
For a really enjoyable testing experience use describe.only for the
test block that you are focused on!
This change also contains a few karma configuration tweaks to facilitate
file watching and to remove all the noisy warnings from the test output.

Also fixed some low-hanging bugs that were using src instead of
ng-src for attrs that contained angular expressions.

https://www.pivotaltracker.com/story/show/137548067
@AllenBW
@miq-bot add_label euwe/no, enhancement


Request change to ec_math1.jpg

.negate() is incorrect

Thanks Mike! I put up a duplicate issue simultaneously #102 :) I'll close mine.

Closed by #114


Android app open Amap, can not get positioning, error information as follows, hope to get expert advice

Android app open Amap, can not get positioning, error information as follows, hope to get expert advice：
[JS Framework] Failed to execute the callback function:
TypeError: Cannot read property 'points' of undefined
10:14:06.314 reportJSException >>>> exception function:WEEX_CALL_JAVASCRIPT, exception:JavaScript execute error!Uncaught TypeError: Cannot read property 'points' of undefined
at  (/__uniappchooselocation.js.nvue:1:28376)

Thank you very much for your feedback

What version of signature_pad?


some minor problems

Hello!
I have some minor problems with We love colors! :
in the file that generates the gpl files the xml rows should be modified to add one # after each \n ->  <'xml': '\n  #  PANTONE® and related trademarks are the property of\n  #  Pantone LLC (https://www.pantone.com), a division of X-Rite, a Danaher company\n  '>
Otherwise the file is not read by inkskape
fetching prismacolor causes an error in cli.py
copic website has been moved and updated, so trying to extract data outputs an error
<colors fetch --all> outputs an error, claiming that the option does not exist. I think that once upon a time the option must have been eliminated for a simpler: no args=all, but in the readme.md it has not been updated.
For some mysterious causes: <colors fetch && colors process> does not work (on my linux Manjaro at least) It executes the first command and stops. Probably the first does not output anything and the && stops
By the way: thanks for the nice script, it does a very useful job!!!
Desktop (please complete the following information):

OS:  Manjaro Linux

PS
I just don't know how to send a suggestion, so I append here:
Any chance to get an update with NCS palette?
https://www.e-paint.co.uk/NCS-2050-index-colour-chart.asp
https://ncscolour.com/product-category/shop/colour-samples/
:) Thanks!

Hey there!
First of all: Thank you very much! 🎉
It's been a while since we wrote this script, and haven't used or relied on it that much tbh. It was foreseeable that the scraped pages would change someday - BUT given your expressed interest, we'll consider fixing the issues you pointed out - big thanks!
Cheers
S1SYPHOS

That script should be more known, the basic palettes in inkskape are only directed to webdesigners, while the program could be really useful to many other illustrators. Having some standard colours "native" could get new quality users!

Da: Martin Folkers @.>
Inviato: mercoledì 25 gennaio 2023 09:29
A: fundevogel/we-love-colors @.>
Cc: Il-Saggio @.>; Author @.>
Oggetto: Re: [fundevogel/we-love-colors] some minor problems (Issue #17)
Hey there!
First of all: Thank you very much! 🎉
It's been a while since we wrote this script, and haven't used or relied on it that much tbh. It was foreseeable that the scraped pages would change someday - BUT given your expressed interest, we'll consider fixing the issues you pointed out - big thanks!
Cheers
S1SYPHOS
—
Reply to this email directly, view it on GitHubhttps://github.com/fundevogel/we-love-colors/issues/17#issuecomment-1403253085, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY4FMJJQQTIY3EF2KYX6CV3WUDP57ANCNFSM6AAAAAAUFVLJHA.
You are receiving this because you authored the thread.Message ID: @.***>

@Il-Saggio Hey there, I just want to let you know that I started working on it. This repository is a mirror, but you can totally check out any progress here. I will also look into NCS colors! :wink:

FYI v2.1.0 brings support for 'HKS' colors as well

GREAT!!
I'll upgrade as soon as I can! ;)

I'd definitely love to get some feedback if that's alright! And if you encounter any kind of bug or odd behaviour, just let me know 😉


Bug fix for liking a song before playing anything

#125
But I think wrapping everything in an if let currentlyPlayingIndexPath = currentlyPlayingIndexPath is a simpler solution, since if there is no currentlyPlayingIndexPath, then there is no need for this method to actually do anything, since that means the playerCell doesn't have any song anyways.

This will not work, I should be able to like a song in my feed even before it plays as this is expected behavior

You should pass the cell to the controller as an argument in the delegate method, and use that cell's index to get the song

The post view shouldn't have access to the model as this breaks MVC, but we can fix that later after we refactor

? You can still like it before you play any song

Check slack


Convert wifi drivers to use new logger

Codecov Report

Merging #10405 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #10405   +/-   ##
=======================================
  Coverage      53%      53%
=======================================
  Files         210      210
  Lines       25732    25732
  Branches     5672     5672
=======================================
  Hits        13639    13639
  Misses       9779     9779
  Partials     2314     2314

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 049267a...bd91a9b. Read the comment docs.


Updated case events by case id endpoint to take optional category

Motivation and Context
Rops users want to be able to get the timestamp for a completed seft or eq. We have decided for the first iteration to only return the first completed timestamp for SEFT.
What has changed
Updated endpoint to take optional category and return case events based on category, along with said created date stamp.
How to test?
Run in docker dev and hit endpoint to see if matched case events to categories and case id's are returned.
Wanted categories:
OFFLINE_RESPONSE_PROCESSED
COMPLETED_BY_PHONE
SUCCESSFUL_RESPONSE_UPLOAD
Note this end point will return all categories sent if in DB.
Links
TRELLO CARD

Do you not want No Longer Required as well?

@gemmai95 No, although this endpoint can be used to get that info, but i think we only want completions


[question] Reg. Logic-soft Matrix ZDB5100

Version 3.0.3
Build/Run method

[x] Docker

Zwave2Mqtt version: 3.0.3
Openzwave Version: 1.6.1080
Questions
I've just acquired a Logic-soft Matrix ZDB5100, and z2m has discovered a total of 17 devices for it:

6 dimmers (type=light), I expected 1 (the device has only one output)
6 switches (type=light), I expected 4 buttons?.. Maybe one more for an on/off for the devices output
5 scene states (type=sensor)

I've got a few questions.

Z2M reports to HASS, that light_rgb_dimmer_6's (the device I've found to be the dimming output of the unit), is having a brightness going from 0..255 (I've seen this in the value reported over MQTT), when it actually goes from 0..100. Is this an OZW config issue?

The Matrix has 4 physical buttons with an RGB LED behind it. I've been able to control LED no. 1 using Z2M (a User-value for RGB color), but I can't control LEDs 2..4. Z2M also only seems to discover one parameter named Instance 1: Color (20-51-1-0), but non named f.ex. Instance 2: Color (...).

I've not been able to find the Instance 1: Color in the OZW config, so perhaps the product is reporting this and Z2M is missing it?

What decides which values are User/Configuration/System values?

HASS has an RGB selector that disappears when the light is turned off.. Do you think its possible to report to HASS that the RGB can be controlled despite the light being off ? (as they're in fact two different lights ..)

The SW Version is reported to HASS as "Unknown", but Z2M shows it as 1.01.

Mike.

Also. The product is detected as having 6 dimmers.. where I'd expect 1, as only one output exists on it.. (it can only control one light).. I think the remaining can be used in tandem with other similar products.. so that one product controls the light (the master), and others merely send the master "basic set" commands..
Maybe the slaves need the concept of a dimmer for this to work.

Z2M reports to HASS, that light_rgb_dimmer_6's (the device I've found to be the dimming output of the unit), is having a brightness going from 0..255 (I've seen this in the value reported over MQTT), when it actually goes from 0..100. Is this an OZW config issue?

Check the hass configuration and fix the value template if needed, unfortunally not every device works in the same way

The Matrix has 4 physical buttons with an RGB LED behind it. I've been able to control LED no. 1 using Z2M (a User-value for RGB color), but I can't control LEDs 2..4. Z2M also only seems to discover one parameter named Instance 1: Color (20-51-1-0), but non named f.ex. Instance 2: Color (...).

This question is too generic, you should provide the valueid of each one and show a debug log when you try to set a value

I've not been able to find the Instance 1: Color in the OZW config, so perhaps the product is reporting this and Z2M is missing it?

Could be a configuration issue in XML file. Try to open this issue on OZW repo and check

What decides which values are User/Configuration/System values?

It's a parameter of the value, it comes from OZW https://github.com/OpenZWave/node-openzwave-shared/blob/master/src/utils.cc#L336

HASS has an RGB selector that disappears when the light is turned off.. Do you think its possible to report to HASS that the RGB can be controlled despite the light being off ? (as they're in fact two different lights ..)

I'm not an HASS user, can't help with this but I would be happy to help you with a PR for that if you find a way

The SW Version is reported to HASS as "Unknown", but Z2M shows it as 1.01.

That's coming from: https://github.com/OpenZWave/Zwave2Mqtt/blob/master/lib/Gateway.js#L437
I don't know what could cause the unknow, try to delete it from hass and let z2m recreate it

The version is actually class 0x86..
.. so that's odd.

I've played a bit with the brightness / states / RGB and so on..
I've found that HASS has a brightness_scale property, which defines that brightness max value. It defaults to 255. If you set this to 100, then HASS properly scales between 0..100. Doing that could actually remove the workaround (?) Z2M makes, which is:  "brightness_value_template": "{{ (value_json.value / 99 * 255) | round(0) }}",.

I've also found that Z2M defines the state and brightness topics as the same. So what HASS will do, is send both "ON", "OFF" and numerical values (0..100) to Z2M. I think this confuses the wall switch. I bypassed the state topic by temporarily placing it elsewhere, and then HASS started "working properly".
I've found that if I set zwave2mqtt/switch_2/38/6/0/set (brightness topic for my dimmer) to:

0..100 - the light goes from 0..100% brightess
OFF - the light turns off
ON - the light does NOT turn on; but it will turn the light OFF if it was on.

It seems that any value that isn't a number, will turn the lights off. I suppose other lights / switches work differently.. any ideas?

Thanks for the tips btw.. :)

I refreshed the node, and copied out the section of the OZW_Log that relates to this device (it's long .. 2100 lines)..
Regarding version, I see that the device apparently reports 3 instances of COMMAND_CLASS_VERSION ?
OZW_Log.txt

I kicked off Zensys Tools and checked out my wall switch. It correctly detects 5 endpoints, where 4 of them are switches and the last is the output from the product. The 4 switches all have a 0x33 - SWITCH COLOR command class (51) .. so something must be off with OZW as it only detects one of them? ..
I can't figure out how to invoke the Color Set though.. could be cool to test if it actually worked and set colors.

I've made an issue with OZW

I will check this out on Monday Mike! About the version, as you see that one is using 134 that is application version
Sent with GitHawk

By double checking the code I saw that I only check the command class for version, I should also check the index (0=lib version, 1=protocol version, 2=application version)

I've found that HASS has a brightness_scale property

I saw that but I had some hass users having problems when using that property. Does it works for you? If so I will wubmit a fix as you suggested (or ifo you want to make a PR this is the code to edit: https://github.com/OpenZWave/Zwave2Mqtt/blob/master/hass/configurations.js#L156-L185

I can't figure out how to invoke the Color Set though.. could be cool to test if it actually worked and set colors.

Unfortunally I'm not an hass users and I haven't so much zwave devices to play around so I can't tests all them, also hass mqtt autodiscovery doesn't support all kind of devices, about the color I have made just a support for rgb lights, I don't know if hass has an mqtt device that only accepts color inputs. Do you know?

Reg. brightness_scale. The value template converts from 0..255 to 0..99, right? In that case, changing the scale will let HASS do that conversion.
Reg. RGB. I managed to change the lights on the other switches, using a different controller.. Only, I reverted back to OZW before I turned them off, so now they're permanently set .. :D
HASS does not have an RGB-only thing, but light is the proper class for this.
For my specific product, I think I'll split the brightness control and the RGB control into separate devices. They are two different things, with two different states, and shouldn't be mixed. Z2M does nothing wrong here, as it normally will be both the light and the color of the light, that is controlled in one go. When I figure out how to control the intensity of the RGB lights, then it'll be worse, as now "brightness" can mean both RGB light and the output of the dimmer... :P
I also checked with HASS, and they had a long discussion on being able to set RGB colors independently of brightness, but came to the conclusion that one mustn't.

Is there an issue I could read on previous brightness_scale attempts?

Sidequestion: Would it be possible to display devices with their multiple endpoints, like Zensys does it?
I find it really convenient to know that that there are 5 endpoints, 4 of them named the same, etc.. I don't know if all the details are there, in the Z-wave data, or if Zensys has a magic matchup elsewhere..

@LordMike With endpoints you mean groups? If so you will be able to see them in groups tabs. COuld you show me what Zensys does with endpoints?
I cannot find the issue, it could have been a conversation in slack channel too, I only remember that a user was helping me with that and maybe could tell you more about this: @jshridha.
Anyway, the edit to make the test is really simple (just check the link to the code I sent you and edit it there), if it works let me know and I will add it to next release asap :)

Groups would be having one ZW device communicate "directly" with another, right? That's not it.
In my Zensys screenshot, the "endpoints" (I still don't know if this is the name for it), are shown up top. The node, 20, is split into 5 sub-thingies, where each of the 5 (20.1 through 20.5) have a set of command classes associated to just them.
With my device (the wall switch), there are so many classes and values, that identifying which values belong to which of the 5 endpoints becomes a pain.
I can grab a few more screenshots from Zensys in an hour or so. I have to disconnect the Z-wave stick from my HASS server when I do :P

EDIT 2: I see now that "Groups" has a reference to "Multi instance".. I think the following is true:
Z2M's "Groups" might be a misnomer of Z-Waves "associations"
Z2M's "instance" might be Z-waves "endpoint"

Yes that's it :)

@LordMike Could we close this in favor of the new feat request?

Outstanding stuff not related to #417:

Should brightness_scale be 99 by default?
Should on_command_type be brightness by default? -- I don't think so, is overriding by stored discovery doc the way to go?
Why did Z2M identify 6 dimmers? -- I'll check up on this.

@robertsLando I think you're talking about pull request #135. The reason for sending 255 by default for an "on" operation is that all of the Jasco, GE, and zooz dimmers (and probably others also) will return to their previous brightness if they receive 255 command. If they receive anything from 0-99, they will go to that specified brightness %.
@LordMike I believe I tested setting the max scale in home assistant, but that prevented home assistant to be able to send 255 for an "on" command. That is why you have the weird looking work around that does the 0-99 scaling within the value template.

Aha!.. That makes sense then. I've found that for the ZDB5100, if I send .. I think .. a COMMAND_CLASS_SWITCH_BINARY with ON, it goes to its previous brightness.. so perhaps it's a matter of instructing HASS to send to different CC's?
In any case, devices will be different in the end.. Am I meant to resolve it on my end by configuring the discovery document for the devices that differ?

@LordMike I let @jshridha Answer for you as I don't own this devices and I'm not able to make tests

@LordMike that's probably the easiest way to go. You may just need to make a custom mqtt device in home assistant since I'm not sure that zwave2mqtt has build in the ability for hass devices created from one command class to send instructions to a different command class.

I'm not sure that zwave2mqtt has build in the ability for hass devices created from one command class to send instructions to a different command class.

It depends on the configuration used in the command topic, if the command topic should use a different valueid just need to use that valueid in the configuration

That would be the thinking, yes, have it communicate with a different topic.
TBF, I'll probably end up making the entities myself, in HASS, as they'll probably be unmaintainable in Z2M.

TBF, I'll probably end up making the entities myself, in HASS, as they'll probably be unmaintainable in Z2M.

@LordMike That is my suggestion at all, for simple things everything should work but unfortunally mqtt autodiscovery is not so friendly and also doesn't support all features (and also could easily break things after hass updates like it has happen with locks) so that would be the best way to integrate your devices for sure.
This could be a useful tutorial for this: https://selfhostedhome.com/migrating-to-zwave2mqtt-for-home-assistant/

In that case, I don't think there's any remainder in this issue.
The current defaults have their merit, so I'll let this be a discovery of available options :).. Unfotunately, I can hardly point at any HASS docs for discovery, as that documentation is non-existent or scattered in many places :/.

@LordMike Yes, the hass docs for discovery can be tedious / difficult to go through. I just went through it for a different project. But for your use case, you may just want to try out specifying the mqtt yaml and skipping the auto-discovery phase.

All I have follow to make the things you see here are this docs: https://www.home-assistant.io/docs/mqtt/discovery/

@robertsLando is there a way to prevent Z2M from pushing discovery documents?

@LordMike for this nodes, set an empty discovery payload on each entity

Slightly cumbersome. But ok. They won't be recreated at any point?

I havent’t found a friendly way for this yet, do you have any suggestions? Anyway with an empty payload the discovey will fail so there will be no entities on hass, but mqtt values will still be availables. What I could do is to add a field to nodes to disable discovery on some of them, or would you prefer to select single entities to esclude for each node?

Daniel - Software Engineer
Support me at:
Github sponsors

On 11 May 2020, at 15:45, Michael Bisbjerg<EMAIL_ADDRESS>wrote:

Slightly cumbersome. But ok. They won't be recreated at any point?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ooh.. I kinda hoped to use the same topics to publish entities myself. I found the HASS config to be a pain, especially as I'll have to make ~6-8 entities per device, so I made a templating program that pushes to topics in MQTT.
I'll just have to name something differently.
One way is a property next to the discovery_payload, f.ex. discovery: false. (It'll default to true).
For convenience, add a button next to "Rediscover node" that says "disable all discovery".. What it should do, is set this boolean on all devices. Then I can pick and choose, if need be, and quickly disable all discovery, if need be.
When publishing discovery stuff, check this boolean.

One way is a property next to the discovery_payload, f.ex. discovery: false. (It'll default to true).

That could be done yes

@LordMike Just submitted a PR based on this. CHeck it out :)

Cool. Is there a docker image with this in it ?
From the code, I gather this is per node - which is awesome :)
Minor thing. Configurable ignoreDiscovery default, for new nodes?...

Configurable ignoreDiscovery default, for new nodes

This would break existing instances. I should create an option on gateway settings Manual discovery that if is true will set ignoreDIscovery to true by default in all nodes

You need, like, a tri-bool.. :P
Keep the current code that sets ignoreDescovery to false, if it wasn't truthy (to add the property to existing docs).. But add some code in the method that creates new nodes, where you copy in the specified default value - since the default isn't checked with existing nodes, only new ones, it shouldn't affect existing setups.

But add some code in the method that creates new nodes, where you copy in the specified default value

This is what manual discovery would be for in my original idea

Hmm. You could also do migrations :)

@robertsLando I have no need for this issue to stay open, so you can close it if you want :).
I've ended up taking complete control of the entities. I let Z2M send to a different discovery topic prefix, and then I copy those I need over to the actual discovery topic prefix.

@LordMike Ok perfect, thanks :)


Question about rank-0 tensors + Vector dialect

Hi folks,
I'm new to onnx-mlir, so please bear with me.
Does onnx-mlir have an opinion on rank-0 "tensors"? We've been discussing 0-D vectors in the Vector dialect (used by Triton-CPU), and I want to ensure we’re not overlooking any critical use cases:

https://discourse.llvm.org/t/rfc-should-we-restrict-the-usage-of-0-d-vectors-in-the-vector-dialect

Any input would be greatly appreciated (or even better, feedback directly in the Discourse thread. :blush:). Pointers on the usage of Vector dialect within onnx-mlir would be particular helpful.
Thank you!
-Andrzej

@banach-space if anything, the confusion between scalar, 0-D vectors, or 1D vector with 1 element is tiresome :-)

Agreed! We’re definitely keen to bring some clarity and order to Vector. :)


Grant Application: Flow Social Dashboard

Grant category
Please select one:

Educational material

Description
A Flow dashboard on Alphaday:
Alphaday is a powerful crypto workflow aggregator that pulls in news, on-chain data, social media, web3 services and much more into one customizable UI.
Live Product URL: https://app.alphaday.com/
Example Dashboard we built for Dfinity through a grant agreement: https://app.alphaday.com/b/dfinity/
Backed by: Hashkey, Signum, other VCs as well as Ethereum KoLs including Ethereum Foundation members.
Established prominent partners: Aave, TheGraph, Avalanche, Dfinity, Ethereum Classic, RocketPool, and others.
Problem statement

Target audience
We aim to create a dashboard that serves any Flow user, holders, developers, VCs, and pretty much any stakeholder whether they are completely new to the ecosystem or an expert.

Evidence for the need
We’ve conducted market research on users and currently people’s regular crypto workflows consist of jumping from one browser tab to another to check prices, read news, follow social feeds, participate in discussions. A typical crypto user will have 6 to 10 open tabs at any given time and people have referred to Alphaday as the ‘tab killer’ because all the information you’d need across all your different tabs is available on Alphaday. In this sense, we do not have any direct competitor that can provide 50 different types of services and functionality within one dashboard.

Alphaday helps users to stay up to date and informed with Flow through a single customizable UI.
Proposed solution
Alphaday helps solve the issue of information fragmentation. We aim to serve as a central point where any user (whether they are a developer, enthusiast, investor) can instantly get the Flow information they need, stay up to date on the latest videos & podcasts featuring Flow and much more.
Besides helping the existing community with keeping up with what’s going on in Flow on a daily basis, we will engage in co-marketing efforts to bolster user awareness of both Flow as well as Alphaday.
Impact

In what ways does this benefit the broader Flow developer ecosystem?

We launched our public beta in August 2022 and currently have ~15,000 MAU active users (organic) with minimal resources spent on marketing; our roadmap for 2024 is focused on marketing a lot more. Average session time per user is 9 minutes and retention rate across 1/7/30 days is 56%/53%/50% as measured by Hotjar.
In terms of numbers, considering Flow has ~200K twitter followers and using this as a very crude proxy for community size, we would consider it a success if we could serve a modest 1% of them on a monthly basis (~2K MAU) as a start.
Milestones and funding

Note: Please consider adoption and/or maintenance milestones at the end of your project.

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - Development
Draft Dashboard
3 weeks
-
2000

2 - Deployment
Publishing and Marketing of Dashboard
3 weeks
-
2000

3 - Maintenance
Maintenance & improvement of the dashboard
Indefinitely
-
0

Total funding proposed: <4000 USD>
The grant size reflects the team’s hours required to build and maintain the Flow Dashboard.
We will require 3 devs (1 frontend, 1 backend, and 1 content analyst) working on this for 5 days for initial deployment plus maintenance over the longer course. Our estimated total cost for this is roughly 4,000 USD.
Team

Name
Role
Bio
Contact

Deniz Omer
Founder
Has been involved in the Ethereum space since early 2016 and joined Kyber Network in 2017 as Head of Ecosystem Growth before quitting to start Alphaday full-time in 2021. Previously he worked at Thomson Reuters for a decade building financial products that rivaled the Bloomberg Terminal. He is currently also a Venture Partner at IOSG.VC.
https://twitter.com/DenizOmer, https://www.linkedin.com/in/denizomer/

Felipe Faraggi
Co-founder
Has also been involved in Ethereum since 2016 and was a Developer Advocate at Pegasys and Consensys before quitting to work full time on Alphaday.
https://github.com/faraggi, https://twitter.com/felipefaraggi, https://www.linkedin.com/in/faraggi/

Pablo Palomo
Technical Lead
...
https://github.com/ppalomo, https://twitter.com/ppalomo, https://www.linkedin.com/in/pablo-palomo-07127711/

Vicente Almonacid
Software Engineer
...
https://github.com/v-almonacid, https://twitter.com/v_almonacid, https://www.linkedin.com/in/vicente-almonacid/

Charles Nwankwo
Developer
...
https://github.com/Xavier-Charles, https://twitter.com/Chadnium, https://www.linkedin.com/in/charles-nwankwo-01/

Jonathan Irhodia
Developer
...
https://github.com/elcharitas, https://twitter.com/iamelcharitas, https://linkedin.com/in/elcharitas

Gideon Anyalewechi
Developer
...
https://github.com/getgiddy, https://twitter.com/get_giddy, https://www.linkedin.com/in/getgiddy/

Zehra Naz Hacisuleyman
Marketing
...
https://www.linkedin.com/in/zehranazh/, https://twitter.com/zehranazh

Selim Cetiner
Content Specialist & Marketing Operations
...
https://www.linkedin.com/in/selim-cetiner-167364234/, https://twitter.com/selim_jpeg

Michael Hagopian
QA & Partnerships
...
https://twitter.com/MikeJa33, https://www.linkedin.com/in/mikael-h-87bb4ba4/

Hello @franklywatson,
Are there any updates on our proposal? We can provide additional information, if required.
We can also schedule a call if it suits you. My email address is<EMAIL_ADDRESS>See below some relevant links that were not included in our initial proposal:
Live Product: https://app.alphaday.com/
Landing Page: https://alphaday.com/
Twitter: https://twitter.com/AlphadayHQ
Discord: https://discord.com/invite/8KSmPyT5k8
Github: https://github.com/AlphadayHQ
Linkedin: https://www.linkedin.com/company/alphaday
Pitch Deck: https://alphaday.com/deck
Demo: https://www.youtube.com/watch?v=ThCd_W3rK_8
Note that we just released a new mobile version of our app. To view the complete dashboards we create for our partners, please visit our app via desktop.


General Issue: Update links in .lycheeignore

Background Information
I put in a lot of failing links into the ignore file.  Once we are stable we should go back and remove/update the ignore file
Definition of Done
No response

https://github.com/pharmaverse/admiralvaccine/blob/main/.lycheeignore