current_temperature is null

First of thank you very much for this custom component.
Today I found some time to play around with your custom component and mostly works.
For  water_heater.dhw1 and climate.hc1 current_temperature is reported null.
The Gateway reports: iCom_Low_NSC_v1 (buderus logamatic km200)
Do you have any idea what the waterheater program HCprogram is for?
operation_list: Off,high,HCprogram,ownprogram
For the integration page it would also be great if you could list the other sensors created.

Do you use Buderus app?
Do you have current temperature there? Are you waiting long enough? I mean more than 3 minutes.
About programs. I'm going to open WIKI and with shared forces we gonna explain all programs for everybody.
Integration page - I could, but for some reason HA community AFAIK doesn't want to include sensors in integration page. I don't know why, but I have to follow these rules

Wiki started - https://github.com/pszafer/home-assistant-bosch-custom-component/wiki/Water-heater

Do you use Buderus app?
Do you have current temperature there? Are you waiting long enough? I mean more than 3 minutes.

Yes, the componten was up and running for several hours.
This is a screenshot from the Buderus MyDevice App:

The value I would expect is listed in the sensor sensor.hotwater_temp
The water_heater in ha looks like:

water_heater.dhw1
ownprogram
current_temperature: null min_temp: 30 max_temp: 80 temperature: 55 target_temp_high: null target_temp_low: null operation_mode: ownprogram operation_list: Off,high,HCprogram,ownprogram CALENDAR: null friendly_name: Buderus Wasserkessel supported_features: 3

About programs. I'm going to open WIKI and with shared forces we gonna explain all programs for everybody.

Thanks. This already answered another finding regarding the  -3276.8 for sensor.return_temp

Integration page - I could, but for some reason HA community AFAIK doesn't want to include sensors in integration page. I don't know why, but I have to follow these rules
That is very pitty. Some integrations e.g. the MQTT does this and this is very handy.

Hello,
VorlaufTemperatur is not the same as the Current temperature.
current temperature is the actual temperature in the room where your thermostat is installed. I some case thermostat is installed inside your heater, then current temperature is disabled.
the vorlauf temperature is the temperature of the water inside the heater.
this is given in Home assistant as a sensor :
{
   "id": "/system/sensors/temperatures/supply_t1",
   "name": "Actual supply temp"
}

Hi moustic,
I use the componement also and it works great.
I have the same question as leinich but doesn't understand what to do, or what you will do with our requests?
I have also a sensor which is not working as aspected. sensor.hotwater_temp gives Invalid.
Is this the same sensor as current _temperature?

Also I would ask or it is possible to implement the maintenance messages also in HA.
Geen actuele meldingen means "at this moment no actual messages".

Regards,
Little

@Railittle current temperature in water heater is actualTemp.
Values in app and HA are totally different, 63C vs 47C.
I think only @moustic999 can elaborate about your installation and what can we do to adjust HA component for your installation.

@Railittle regarding the issue with water temperature. there are many paramters which can be retrieved from the gateway.
I will check which one is the best to use and I will check with @pszafer to adapt if any.
I know that since the last release of firmware buderus/bosch changed the way some parameter are working and it could be one which we did not find before.

@Railittle In order to understand, I would like some explanatation regarding you heater installation.
which heater and which setup /  where is located the thermostat, 1 or more thermostat and how is the water heated ? is it instantly or via an external boiler (160l, 200l ...)
there is 2 different way to heat water : instantly with very small reserve, model such as Buderus GB162T40 ...
or via an external boiler which keep hot water in a big reserve.
dependant of this, different sensor must be checked.
the sensor :  /system/sensors/temperatures/hotWater_t2 (HA : sensor.hotWater) does not seem to be used in your case, as well as in my case. I suspect it is used only in case of instant water, but I don't have this.
for the boiler the current temperature will be
/dhwCircuits/dhw1/actualTemp
not sure why current_temperature is ? now. I will check which value is taken into account for this.

@moustic999
I have a nefit boiler (300L) and the boiler is heated with my Heatpump. In the boiler there is a sensor and this sensor is connected in my heatpump and is called TW1 in the manual (see picture).

My system is like below. I have one external thermostat in my living room.

@Railittle , @leinich when HA 0.96 will be update, please update this component (released already, hope there won't be any last minutes changes).
I added extra service to HA bosch.debug_scan which creates json with your system setup (without any personal info like UUID).
Provide us log with your setup, so we can try add temperature which fulfills your needs.

Sorry for the late reply. I finally found time to update.
Please find attached the requested JSON.
Thank you very much for your effort in developing this ha component.
bosch_scan.zip

@leinich can you paste print screen of HA states of water_heater and climate.
If possible try to contact me on Discord. Maybe we will figure out what's wrong faster that way.

@Railittle if you are willing to give us your rawscan, please create another issue as your setup is different and this issue is becoming hard to follow.

Sorry i’m on holiday in France. I’m back next week. Then I can help you.
Regards,
R
Verstuurd vanaf mijn privé iPhone
Op 22 jul. 2019 om 14:09 heeft Pawel <notifications<EMAIL_ADDRESS>het volgende geschreven:
@Railittlehttps://github.com/Railittle if you are willing to give us your rawscan, please create another issue as your setup is different and this issue is becoming hard to follow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pszafer/home-assistant-bosch-custom-component/issues/1?email_source=notifications&email_token=AJ5KWU37POY6XW6BVQ43BUDQAWPQVA5CNFSM4HN433SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PW3TA#issuecomment-513764812, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJ5KWU5GW77Z75HRJIU3KNLQAWPQVANCNFSM4HN433SA.

Sorry for the late reply. I finally found time to update.
Please find attached the requested JSON.
Thank you very much for your effort in developing this ha component.
bosch_scan.zip

I checked the scan, and I don't see any "specialties" in it ?
@leinich Can you explain what is wrong for you ?  because there is multiple case in this topic and I'm a bit confused.

This topic is a little mess and it is based on very old version of component.
Closing it. Feel free to open new one if you still have a problem using this component.


seem like no one update this ? is ERC1400 dead or popular ?

seem like no one update this ? is ERC1400 dead or popular ?

You can find the ERC1400 implementation here!
Link: https://github.com/ndaxio/ERC1400


Console isn’t persisting

I’ve enabled the Ubuntu console, but it’s not always persisting changes to the filesystem across reboots. I’m presuming that after installing git, for example, it should be there the next time?
Another issue (maybe related?) is that every time I ssh in, the very first time I’m presented with the BusyBox console, I have to exit and ssh in once again to see the Ubuntu console.
Thanks to you all for the hard work on RancherOS, it’s a joy to use.
RancherOS 0.4.4 on a bare metal, Intel Xeon server.
sudo ros service list
disabled amazon-acs-agent
disabled centos-console
disabled delian-console
disabled fedora-console
enabled  kernel-headers
disabled kernel-headers-system-docker
disabled resize-fs
enabled  ubuntu-console

sudo system-docker images
REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
rancher/os                 v0.4.4              593f2d72f0c3        2 weeks ago         194.3 MB
rancher/os-console         v0.4.4              9fbb7b73e2f6        2 weeks ago         25.37 MB
rancher/os-network         v0.4.4              83eae390036b        3 weeks ago         25.36 MB
rancher/os-ubuntuconsole   v0.4.4              1a65d9d9a15b        3 weeks ago         279.1 MB
rancher/os-udev            v0.4.4              d235101d62c9        3 weeks ago         25.36 MB
rancher/os-syslog          v0.4.4              0dbab1f29c72        3 weeks ago         25.36 MB
rancher/os-statescript     v0.4.4              e5d1e104bc88        3 weeks ago         25.36 MB
rancher/os-state           v0.4.4              c8623545794b        3 weeks ago         25.36 MB
rancher/os-preload         v0.4.4              878eb607eb2e        3 weeks ago         25.36 MB
rancher/os-ntp             v0.4.4              1f2357dc848b        3 weeks ago         25.36 MB
rancher/os-docker          v0.4.4              2d6422d4e3e3        3 weeks ago         25.36 MB
rancher/os-cloudinit       v0.4.4              5d7a11ee87d5        3 weeks ago         25.36 MB
rancher/os-autoformat      v0.4.4              f1f308a52c35        3 weeks ago         25.36 MB
rancher/os-acpid           v0.4.4              204329c16b89        3 weeks ago         25.36 MB
rancher/os-preload         v0.4.3              983c005fe53f        10 weeks ago        25.65 MB
rancher/os-console         v0.4.3              d9b2845438df        10 weeks ago        25.66 MB
rancher/os-udev            v0.4.3              8dc9eee7501f        12 weeks ago        25.65 MB
rancher/os-syslog          v0.4.3<PHONE_NUMBER>65        12 weeks ago        25.65 MB
rancher/os-statescript     v0.4.3<PHONE_NUMBER>0e        12 weeks ago        25.65 MB
rancher/os-state           v0.4.3              0fe21afc3049        12 weeks ago        25.65 MB
rancher/os-ntp             v0.4.3              3e2d57d4ae21        12 weeks ago        25.65 MB
rancher/os-network         v0.4.3              5288f2eb944e        12 weeks ago        25.65 MB
rancher/os-docker          v0.4.3              6a4e2f959df2        12 weeks ago        25.65 MB
rancher/os-cloudinit       v0.4.3              5c47e775e016        12 weeks ago        25.65 MB
rancher/os-autoformat      v0.4.3              00182a66713c        12 weeks ago        25.65 MB
rancher/os-acpid           v0.4.3              0fa901101944        12 weeks ago        25.65 MB

sudo system-docker ps
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS              PORTS               NAMES
7c6a90949044        rancher/os-ubuntuconsole:v0.4.4   "/usr/sbin/entry.sh /"   31 minutes ago      Up 31 minutes                           console
8b4bd6dd2d68        rancher/os-docker:v0.4.4          "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           docker
bbde6f99b5b1        rancher/os-network:v0.4.4         "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           network
90f4f452e1ff        rancher/os-ntp:v0.4.4             "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           ntp
c60702eb0bae        rancher/os-udev:v0.4.4            "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           udev
62a2b3139696        rancher/os-syslog:v0.4.4          "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           syslog
81e7c983295c        rancher/os-acpid:v0.4.4           "/usr/sbin/entry.sh /"   11 days ago         Up 31 minutes                           acid

@neeklamy How are you running RancherOS?  For example, if you are running VMware/Virtualbox booting from the ISO, you would be running from memory and nothing is ever persisted.

It’s running on bare metal (I used netboot.xyz to install RancherOS).
Between most reboots it does persist (packages stay installed, created directories remain), every now and then it doesn’t. I always make sure to stop any running Docker containers before safely shutting it down (shutdown -h now).
Thankfully the contents of the persisted directories always remain (/home and so on).

@neeklamy When it's not persisted, are you sure that you were booted into the ubuntu-console?

Yes, always logged into the ubuntu-console. Although I’ve had to logout and back in again on some boots, because the ubuntu-console doesn’t always appear the first time, could that be related?

@neeklamy That's definitely related! The console container changes by being recreated, and so each time the Ubuntu console didn't appear it was being recreated and losing persistence. I'm pretty sure the underlying problem here is #937, but just to be sure can you post the output of ip addr show as well as any networking configuration in your cloud config?

Thanks for getting back to me @joshwget, here’s the details you asked for (still on 0.4.4):
rancher@rancher:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope global lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: docker-sys: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker-sys
       valid_lft forever preferred_lft forever
    inet6 fe80::3415:88ff:febf:c33c/64 scope link
       valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 44:39:c4:55:79:ed brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::4639:c4ff:fe55:79ed/64 scope link
       valid_lft forever preferred_lft forever
12: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:b8:72:54:d9 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:b8ff:fe72:54d9/64 scope link
       valid_lft forever preferred_lft forever

rancher@rancher:~$ sudo cat /var/lib/rancher/conf/cloud-config.yml
rancher:
  modules:
  - zfs
  services_include:
    kernel-headers: true
    ubuntu-console: true

I was previously experimenting with using a ZFS storage pool (but not for RancherOS, I left that on its default OverlayFS and ext4).
rancher@rancher:~$ sudo ros service list
disabled amazon-ecs-agent
disabled centos-console
disabled debian-console
disabled fedora-console
enabled  kernel-headers
disabled kernel-headers-system-docker
disabled resize-fs
enabled  ubuntu-console

But booting up the system and logging in just now, I’m at the BusyBox console.

I've experienced the same problem with RancherOS 0.4.5, ubuntu-console and experimenting with ZFS.

It's possible that ZFS is just coincidence here. I think the easiest way to find out is to see if these problems remain in v0.5. The next release will cache service definitions (such as consoles), and that should prevent persistence issues. If the problem remains then there's likely some other issue specific to ZFS that we'll have to look into.

@neeklamy @ashmckenzie If either of you are using v0.5.0 now, I'd be very interested to know if this issue is still present :smile:

I’ve just upgraded to v0.5.0 – so easy, wow! Ubuntu console was still enabled after the update and a reboot, but it wouldn’t appear on log in, looking closer it hadn’t been updated from v0.4.4.
So, I ran sudo ros console switch ubuntu and Ubuntu console was updated to 0.5.0-3, and from some very brief testing, Ubuntu console is now appearing on boot.
Was that the right way to update Ubuntu console?
Shouldn’t updating the system (sudo ros os upgrade) have updated Ubuntu console too?
sudo system-docker images
REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
rancher/os                 v0.5.0              23d0fd47159d        3 weeks ago         196.7 MB
rancher/os-console         v0.5.0              f36a7c4a794b        3 weeks ago         24.48 MB
rancher/os-udev            v0.5.0              d4487f4b38df        3 weeks ago         24.46 MB
rancher/os-syslog          v0.5.0              1615a263bb62        3 weeks ago         24.47 MB
rancher/os-statescript     v0.5.0              16dfc1fb4776        3 weeks ago         24.46 MB
rancher/os-preload         v0.5.0              fa5795599bce        3 weeks ago         24.47 MB
rancher/os-autoformat      v0.5.0              dde7c4eae540        3 weeks ago         24.47 MB
rancher/os-cloudinit       v0.5.0              b69a38db132f        3 weeks ago         24.46 MB
rancher/os-base            v0.5.0              c23bee6091fe        3 weeks ago         24.46 MB
rancher/os-ubuntuconsole   v0.5.0-3            9ceb147fcd39        4 weeks ago         284.3 MB
rancher/os                 v0.4.4              593f2d72f0c3        3 months ago        194.3 MB
rancher/os-console         v0.4.4              9fbb7b73e2f6        3 months ago        25.37 MB
rancher/os-network         v0.4.4              83eae390036b        3 months ago        25.36 MB
rancher/os-ubuntuconsole   v0.4.4              1a65d9d9a15b        3 months ago        279.1 MB
rancher/os-udev            v0.4.4              d235101d62c9        3 months ago        25.36 MB
rancher/os-syslog          v0.4.4              0dbab1f29c72        3 months ago        25.36 MB
rancher/os-statescript     v0.4.4              e5d1e104bc88        3 months ago        25.36 MB
rancher/os-state           v0.4.4              c8623545794b        3 months ago        25.36 MB
rancher/os-preload         v0.4.4              878eb607eb2e        3 months ago        25.36 MB
rancher/os-ntp             v0.4.4              1f2357dc848b        3 months ago        25.36 MB
rancher/os-docker          v0.4.4              2d6422d4e3e3        3 months ago        25.36 MB
rancher/os-cloudinit       v0.4.4              5d7a11ee87d5        3 months ago        25.36 MB
rancher/os-autoformat      v0.4.4              f1f308a52c35        3 months ago        25.36 MB
rancher/os-acpid           v0.4.4              204329c16b89        3 months ago        25.36 MB
rancher/os-preload         v0.4.3              983c005fe53f        5 months ago        25.65 MB
rancher/os-console         v0.4.3              d9b2845438df        5 months ago        25.66 MB
rancher/os-udev            v0.4.3              8dc9eee7501f        5 months ago        25.65 MB
rancher/os-syslog          v0.4.3<PHONE_NUMBER>65        5 months ago        25.65 MB
rancher/os-statescript     v0.4.3<PHONE_NUMBER>0e        5 months ago        25.65 MB
rancher/os-state           v0.4.3              0fe21afc3049        5 months ago        25.65 MB
rancher/os-ntp             v0.4.3              3e2d57d4ae21        5 months ago        25.65 MB
rancher/os-network         v0.4.3              5288f2eb944e        5 months ago        25.65 MB
rancher/os-docker          v0.4.3              6a4e2f959df2        5 months ago        25.65 MB
rancher/os-cloudinit       v0.4.3              5c47e775e016        5 months ago        25.65 MB
rancher/os-autoformat      v0.4.3              00182a66713c        5 months ago        25.65 MB
rancher/os-acpid           v0.4.3              0fa901101944        5 months ago        25.65 MB

sudo system-docker ps
CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS               NAMES
1c1863fadd99        rancher/os-console:v0.5.0   "/usr/sbin/entry.sh /"   43 seconds ago      Up 42 seconds                           console
10ab1fd69c5c        rancher/os-base:v0.5.0      "/usr/sbin/entry.sh /"   2 hours ago         Up 42 seconds                           docker
988b4a228442        rancher/os-base:v0.5.0      "/usr/sbin/entry.sh n"   2 hours ago         Up 43 seconds                           network
9888decd8525        rancher/os-base:v0.5.0      "/usr/sbin/entry.sh n"   2 hours ago         Up 47 seconds                           ntp
56b63bed667e        rancher/os-udev:v0.5.0      "/usr/sbin/entry.sh /"   2 hours ago         Up 48 seconds                           udev
d360550090b1        rancher/os-base:v0.5.0      "/usr/sbin/entry.sh /"   2 hours ago         Up 48 seconds                           acpid
0f28937e4671        rancher/os-syslog:v0.5.0    "/usr/sbin/entry.sh /"   2 hours ago         Up 48 seconds                           syslog

@neeklamy This is a tricky question because there are good reasons to expect the console to be upgraded and there are good reasons to expect it to not be upgraded as well.
Upgrading a console means the old console container is destroyed and a new one is created. All packages and files not in a persistent directory will be gone. This is especially important since Docker runs inside the console (#1133). At the same time, most users are confused that their console version is not upgraded along with the rest of the system.
The current behavior is to only upgrade the default console. Originally all consoles were not persistent, but some users were getting confused that packages weren't remaining after rebooting. As a result, only non-default consoles (those with a package manager) were made to be persistent. In the upcoming release we're switching the default console to Alpine, which does have a package manager.
A better approach is probably for console persistence to be a user choice and not be dependent on the type of console. At the very least, I think upgrades should offer the user the choice of what they want to happen with their console.
Long-winded response to your question, but the best way to upgrade the console currently is probably to switch to the default console and back.

@neeklamy If you are still able to reproduce on v0.5.0, can you please re-open?


Bugfix JWT expiration convert

Fixed remaining bug in date conversion process in "JsonWebTokenEncoderGuiTool.cs" .
Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] New feature or enhancement
[ ] UI change (please include screenshot!)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Internationalization and localization
[ ] Other (please describe):

What is the current behavior?
Application crashes when entering decimals in date and time.

Issue Number: N/A
What is the new behavior?

Changed from using Convert.ToInt32 to int.TryParse for date/time conversion.

Other information

Quality check
Before creating this PR:

[x] Did you follow the code style guideline as described in CONTRIBUTING.md
[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
[ ] Did you verify that the change work in Release build configuration
[ ] Did you verify that all unit tests pass
[x] If necessary and if possible, did you verify your changes on:

[x] Windows
[ ] macOS
[ ] Linux

Hello,
Thank you for your contribution, and sorry for the very late review. This PR looks good to me!


Switch code and tests to PSR-4

Switch code and tests to PSR-4
Also:

Add .gitattributes
Update .travis.yml

I like this!
What about aidan or something similar as namespace?
@aidantwoods Since you have already released a 1.0 version, how about creating a new branch that breaking PRs like this one can be sent to? I would like to send one for the framework adapters as well. :)

Hey Franz, wie geht's? ;-)
Maybe Aidan\ or Aidantwoods\ ? Let me know @aidantwoods
Totally up for a new branch too !

Looks great! 😄
Maybe go for aidantwoods\SecureHeaders for the namespace? (Might as well make it copy-pastable from the packagist name/github URL)
New branch sounds good too! If I create a 2.x branch, then we can collate a few of these changes into the next major release without changing the major version every couple days 😜

@aidantwoods I've just updated the namespace with https://github.com/aidantwoods/SecureHeaders/pull/8/commits/e5bffd7f5cf1d604174b3f3332b5edbd427ee7e9.
Can find the 2.0 branch, can you create it so I can retarget all my PRs to this new branch?

@aidantwoods Maybe keep the vendor name in the same format as PSR-2? e.g. AidanWoods, or capitalize the A at the start at the very least?

Okay, yeah that's a good point @ameliaikeda – shall we just go with AidanWoods then?
@lucasmichot there's a 2.0 branch there now :)

:+1: PR looks good.
Once @lucasmichot has changed the namespace. (And hi back. It's funny how small the PHP world is.)

And Berlin is even smaller :-)
@aidantwoods the namespace has been changed to Aidantwoods\SecureHeaders and this PR now targets branch 2.0


AttributeError: module 'shiny.ui' has no attribute 'input_task_button'. Did you mean: 'input_action_button'?

I  am using pyhton 3.12.1 and using shiny-0.10.2 but I get the error AttributeError: module 'shiny.ui' has no attribute 'input_task_button'. Did you mean: 'input_action_button'?

Are you sure that you are running Shiny 0.10.2? Sometimes Python environments can get mixed up.
Can you put this at the top of your app to confirm?
import shiny

print(f"Shiny version: {shiny.__version__}")

Thank you, the problem is solved now

Good to hear that!


fix(Client) - Fix PlatformError

Please check if the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Scope (check one with "x")
[ ] <root>
[ ] @zetapush/cli
[x] @zetapush/client
[ ] @zetapush/cometd
[ ] @zetapush/common
[ ] @zetapush/core
[ ] @zetapush/create
[ ] @zetapush/http-server
[ ] @zetapush/platform-legacy
[ ] @zetapush/testing
[ ] @zetapush/troubleshooting
[ ] @zetapush/user-management
[ ] @zetapush/worker

What is the current behavior? (You can also link to an open issue here)
Unhandled promise error when the connection failed
What is the new behavior?
Error catched when the connection failed
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Je trouve ça un peu bizarre d'avoir une classe qui dans son constructeur s'instancie elle même.


Doesn't work with ruby 1.9 due to String#[]

f64676 makes it work with ruby 1.9 - implemented internal Bytes class which emulates old String#[] behavior.


Adding Hover effect to cards

the card look good but it should have hover effects whenever cursor is pointed to cards

@Manishkr1007 plz assign me this

Adding an Hover effect to these card would make the website visually appealing and would increase user interaction.
I would like to work on this issue, Please assign this to me.
@Manishkr1007


Make the function menu less annoying to use

This needs no further comments, just trying to use it will show multiple shortcomings.

Neverless, specifying the shortcomings could make for a clearer issue report, as it's a bit vague as is.

Let's try to make a start:

it wastes too much space
function categories should not expand down in an already vertical menu
the menu should not appear partially offscreen
also should not expand into offscreen
please no scrollbars
expanded categories should not have empty lines
it is visually inconsistent
the current grouping in categories itself is of little use, unless you know what to find where
alphabetic ordering is not good with many rarely used items and lots of operators
uncommon blocks should not be on the first row

A way to deal with much of the positioning and layout stuff could be to use a regular JavaFX ContextMenu, at least on non-touch devices, as it automatically positions itself in a sensible way so that it doesn't move offscreen. Another advantage is that it has a consistent size that doesn't depend on the zoom level, and that people are used to the way it works.
The grouping and ordering things could perhaps be approached, again at least on non-touch devices, by adding (prefix-, type- or fuzzy) keyboard-based search.

And I forgot one important thing, that is being able to drag new block from the function menu to the location you want them. Having a click menu stack them all in one spot is very inconvenient.

Oops did overlook #164, let's continue here.

From https://github.com/wandernauta/viskell/pull/304#issuecomment-163381402

The margins around the buttons could perhaps use some fiddling around with to make them look neater
I get the extra Close button from a balance standpoint, but I don't think it's good UX - if people see a close button at that position, they will get used to it being there. 'Suddenly' hiding it when the user switches backend would then not be ideal. I'd prefer to just leave the space blank (or purple).
...aaand when you're playing around with the FunctionMenu css anyway - maybe the Close button could use a splash of color to help distinguish it from the others?

I think basicly all that can be improved with this style of function menu has been done.
Further non trivial improvement will require a complete redesign.


Anyone having trouble sending firmware to LPP using Windows and MIDI-OX?

Sorry, this is a little off topic, but I think I've tried everything. I can not get the LLP to acknowledge it is being sent firmware via sysex. I tried this on two computers and then a third which is only a few weeks old and has no other MIDI software installed. So, I installed MIDI-OX and tried to send first of all the stock firmware which I downloaded from the Resources directory. The LLP just sits there with the top 16 buttons and three others lit but no sign of life.
I did notice that MIDI-OX reports that there are 7 data errors in the file if I first load it into the Command window and then run "Check data".
Has anyone else had to tweak things to get this working?

I'm sorry to hear you're having trouble. I can't get to my Windows machine to test this right now, so I may not be much help. Does the Launchpad at least show up as a destination in MIDI-OX, or in software like a DAW? There was this issue https://github.com/dvhdr/launchpad-pro/issues/9 where Windows doesn't recognize the Open Firmware as a midi device at all, but that didn't effect the bootloader mode.

Thanks, I found that the firmware files I download numerous times from Github were corrupt. This is strange as I have never had such a consistent run of bad downloads. A bit of Googling came up with search results of similar problems. This was by clicking the specific file in the resources folder; downloading the zip of the project worked though.
Perhaps we should use checksums as it would remove one of the variables? MIDI-Ox has some config options that I spent ages playing with.


Fix example assertion in Readme

Trying out this crate and tried to run the example code in the Readme. Noticed this error.
error[E0609]: no field `contents` on type `TestResponse`

Hey, thanks for pointing these out!
it should actually be .text() (it was named contents in an old versions). I've just pushed that up to master and released it.


Please upgrade ember-cli-babel to ^7

Hello @RSSchermer,
I've got this warning when creating new project with Emberjs 4+ :
WARNING: [DEPRECATION] [DEPRECATION] Usage of the Ember Global is deprecated. You should import the Ember module or the specific API instead.

See https://deprecations.emberjs.com/v3.x/#toc_ember-global for details.

Usages of the Ember Global may be caused by an outdated ember-cli-babel dependency. The following steps may help:

* Upgrade the following addons to the latest version:
  * ember-multiselect-checkboxes

### Important ###

In order to avoid repeatedly showing the same deprecation messages, no further deprecation messages will be shown for usages of the Ember Global until ember-cli-babel is upgraded to v7.26.6 or above.

To see all instances of this deprecation message, set the `EMBER_GLOBAL_DEPRECATIONS` environment variable to "all", e.g. `EMBER_GLOBAL_DEPRECATIONS=all ember test`.

### Details ###

Prior to v7.26.6, ember-cli-babel sometimes transpiled imports into the equivalent Ember Global API, potentially triggering this deprecation message indirectly, even when you did not observe these deprecated usages in your code.

The following outdated versions are found in your project:

*<EMAIL_ADDRESS>currently used by:
  *<EMAIL_ADDRESS>    * Depends on<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>(Dormant)
    * Depends on<EMAIL_ADDRESS>    * Added by<EMAIL_ADDRESS>
Note: Addons marked as "Dormant" does not appear to have any JavaScript files. Therefore, even if they are using an old version ember-cli-babel, they are unlikely to be the culprit of this deprecation and can likely be ignored.

Here is my environment:
ember -v
ember-cli: 4.12.2
node: 18.19.0
os: linux x64

Seems need to upgrade the ember-cli-babel and is there any plan to upgrade this great add on for supporting Emberjs 4+ ?

I been a long time since I've used Ember myself, so this addon has fallen quite far behind the current Ember version. I just spent a few hours this afternoon upgrading to Ember 3.28 LTS, which is the most recent version of the Ember major version this addon was last updated for and published this as version 0.12.0; this does include an update to the Babel version to ^7.26.10.
Does upgrading your ember-multiselect-checkboxes version to 0.12.0 resolve your issue?

Thank you @RSSchermer for responding me with the update of the new release..
Btw, I still have some problems when running the app, like message shown below:

Is there anything that I missed ?
Here is my route & template:
routes/application.js
...
  async model() {
    return await this.store.findAll('corelocale');
  }
...

templates/application.hbs
<Multiselect-checkboxes
  @options={{@model}}
  @labelProperty='name'
  @selection={{this.selectedUsers}}
/>

I've solved it, set the EXTEND_PROTOTYPES value to true in environment.js..
Thank @RSSchermer for this great addon...


Can we bundle ESLint and Espree directly in this repository on build?

We currently bundle lib/linter/linter.js and espree and copy the bundles into this repository during the release script.
It would be nice if we could just do all the bundling directly in this repository every time we build.
Some problems to solve:

The publish step occurs after the site is generated, so we can't just pull and build the latest version on commit.
We would have to figure out how to bundle the latest releases while not changing the versions we're using to lint this repository.

Benefits:

eslint/eslint wouldn't have to worry about bundling any more
We can consolidate the Webpack/Babel configs in this repository.

The issue with that is updates to the site that happen outside of regular ESLint release schedule. In that case, we might've already merged some changes into master on ESLint/espree repositories, but haven't yet published them. Site will pull whatever is latest. If we can make it pull from the last known tag, I'd be fine with that (faster release build is always a good thing).

Should have clarified, but that’s what I was intending above. Definitely should build with the latest published release, not what’s in master on GitHub.

Relevant discussion here https://github.com/eslint/eslint/pull/12006#issuecomment-513076818

I would love to see if we could have a build/release step which pulls in ESLint and espree and builds them here. Additionally, this repo could be responsible for copying the documentation from the ESLint repository. This would allow ESLint to go back to a mostly standard release (i.e., wouldn't need to add much to what eslint-release already provides), and this repository can then fully "own" the logic for building and deploying the website.

I really like that idea. We could then change our release build to do the following:

Clone eslint/eslint and eslint/website
Run the release script in eslint/eslint
Run the release script in eslint/website, which copies the doc files from eslint/eslint and generates the eslint/espree bundles and commits them so that the Netlify build can then also bundle them.

It would be nice if we could bundle eslint/espree directly into the build step bundles (since it could potentially reduce bundle size), but that would require a much more complicated build step (we'd have to specify the eslint version to bundle and clone it from GitHub directly, I think, since we don't necessarily want to update the site's ESLint version on every release).

Would love to continue this discussion! At this point, would it be best to bring this to the TSC?

I don't think this requires TSC approval. I'm for trying this out. Seems like a good idea.

@kaicataldo has this been addressed? It looks like there were some PRs merged related to this, so just checking.

Ah, yes! We should be good to go here. Thanks.


Updated glog to 0.3.5 and then to 0.4.0, added microseconds to LogSink::send().

Also replaced the os.path.exists()-based logic in ext_modules.py.in with logic based on automake substitutes.

Moved to ASF Reviewboard:
https://reviews.apache.org/r/70388/


Add configuration object to ga('send')?

Is this possible to add a configuration object to the GA tracker??
We track multiple apps and need tofilter the data per app like below:
ga('send', 'screenview', {
  'appName': 'myAppName',
  'appId': 'myAppId',
  'appVersion': '1.0',
  'appInstallerId': 'myInstallerId',
  'screenName': 'my overridden screen name'
});

More details https://developers.google.com/analytics/devguides/collection/analyticsjs/screens
Is this possible?
PS: love your package, integrates nicely.

Same feature as in #7, right?

Well that is my question, is it the same? Because on each route transition we need to fire at GA the screenview (not the pageview) and insert the route like so.
// in app/router.js
var Router = Ember.Router.extend(googlePageview, {
  location: config.locationType,
  notifyGoogleAnalytics: function() {
    return ga('send', 'screenview', {
      'appName': 'bookings',
      'screenName': this.get('url')
    });
  }.on('didTransition')
});

Does your package allow customisation to screenview and to add the route URL?

In your README.md you use the following example:
import Ember from 'ember';
import config from './config/environment';
import googlePageview from './mixins/google-pageview';

var Router = Ember.Router.extend(googlePageview, {
  location: config.locationType
});

Router.map(function() {
  ...
});

export default Router;

Can I safely overwrite pageview to screenview and add my custom variables like below??
var Router = Ember.Router.extend(googlePageview, {
  location: config.locationType,
  notifyGoogleAnalytics: function() {
    return ga('send', 'screenview', {
      'appName': 'bookings',
      'appId': 'new',
      'appVersion': '1.0',
      'screenName': this.get('url')
    });
  }.on('didTransition')
});

+1
Wondering the same, we use custom dimensions it'd be great to push them along with the pageviews.


New version: QuantumToolbox v0.21.2

Registering package: QuantumToolbox
Repository: https://github.com/qutip/QuantumToolbox.jl
Created by: @albertomercurio
Version: v0.21.2
Commit: d11841dff0b3cc551e77563a27597910316e4817
Reviewed by: @albertomercurio
Reference: https://github.com/qutip/QuantumToolbox.jl/commit/d11841dff0b3cc551e77563a27597910316e4817#commitcomment-148947062
Description: Quantum Toolbox in Julia

Stop merging

please close


Update how-to-configure-private-link.md

fix a typo

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

@RichardLi1437 Thanks for the typo fix; merging.


Unable to reach OS keychain (Void Linux)

Environment:

OS: Void Linux
Kernel 6.5.9_1

When I try to initially sync after install I get a keychain error.
With reference to these steps under issue #43 I did the following:

xbps-install pass (libsecret and gnome-keyring were already installed)
updated /etc/pam.d/login as per the above
updated /etc/pam.d/passwd as per the above

Here is the output from running dcli configure save-master-password-true --debug:
warn: Unable to reach OS keychain because of error: "Platform secure storage failure: zbus error: org.freedesktop.Dbus.Error.UnknownMethod: Object does not exist at path: "/org/freedesktop/secrets/collection/login"", so its use has been disabled. To retry using it, please execute `dcli configure save-master-password-true`. Until then, you will have to retype your master password each time you run the cli.

The error went away when I logged out and logged back in and the program is working as expected now.


How to parse all three parts: header, payload, signature?

As a developer, I want to be able to easily access each of the three parts of a "JWT": the header, and the payload, as well as the signature bits, as described in various JWT documentation.
https://jwt.io/
jose appears to call the payload portion of JWT's, "JWT", and present the rest of these pieces as "JWS". Furthermore, jose does not make it easy to obtain both the header and the payload, as the existing parser methods only yield one or the other of these attributes. And the payload structure does not appear to nest within the "JWS".
As a workaround, I might end up having to parse my token twice :P

I am having the same issue. I need to know the "kid" which is in the header. :(


When using a wrapper component then Flowbite pages/components are not working

I created a website page template that sets my sites basic look and feel, but when I pass the main section as a CHILDREN prop then the Flowbite events do not fire.  I did lot of experimentation and the culprite is the wrapper.  Here is a basic example of how it is setup.
import { Component } from "solid-js";

// Define the layout component
const Layout: Component = (props) => {
  return (

        {/* Add header content here */}

        {/* Render the page component here */}
        {props.children}

        {/* Add footer content here */}

  );
};

// Define a page component
const HomePage: Component = () => {
  return
Welcome to my website!
;
};

// Use the layout component to wrap the page component
const App: Component = () => {
  return (
    <Layout>
      <HomePage />
    </Layout>
  );
};

If you set a simple button and tooltip within the Home Page it will not activate.  But if you duplicate the exact same code into the App component directory or just comment out the "Layout" tags then it works just fine.
Is there something I'm just not configuring correctly? I even attempted to import flowbite into every component but it makes no difference.  I tried setting this up in Stackblitz but it doesn't compile.

I also discovered that using lazy loading breaks Flowbite as well.  But my workaround for the whole issue is to put my code in the App.tsx and wrap my router with decorator code.

Related to: #530. Someone may find it useful!


[#22] add manualDataImport function

[x]  create function that updates dataframe with manually filled data
[x]  include tests
[ ] test data

code is ready up to uploading the test data as soon as storing location is clarified.

ready for review


Attempt to fix redirection to certain Facebook subdomains

Fixes #592
Please let me know if there is a better way to do this.

can anyone without this redirect issue verify that the normal path still works as expected? (@ravkr )

Hope this works for people having this issue! Thanks for the fix :)

I just tested the old and this version. Both can work. 👍

Great, thanks @ALiangLiang


Heading top

Hi,
How to position the heading/title on the top of every page ??
Also, is there a way to set the color of #  or ##  lines?
Thanks,
Roy

Hi,
No, not that I know of, Marp does support this yet.
@yhatt would it be hard to do? (if you show me the file to edit, I will try to figure it out)

@yhatt Any news about this feature?

To set the position of the heading to the top of the page you need to change the default theme.
Note: You need to run Marp from source or rebuild Marp for this to work.

Go to this file: /path/to/the/marp/source/code/sass/themes/default.sass (https://github.com/yhatt/marp/blob/master/sass/themes/default.sass)
Remove line 10
Add the following code one line after the line you just deleted:

  .slide_inner
    margin-top: 100px

Yep, and Marp Next (#267) can be easy to create theme and tweak style.
See also: https://github.com/marp-team/marpit/issues/153#issuecomment-481252049


Installing on second PC

When I install Swing Wallet on another PC I am given a different address. How to I transfer the settings from my first PC installation to my new one? Or is there some way to log into that wallet from the new wallet?

The wallet.dat file contains the private keys to controlling the ZEN coins. The wallet.dat file may be copied manually when the GUI wallet and zend are not running. Make sure you have a backup copy of it on a safe external medium.
The wallet.dat file may also be transferred from one PC to another ... when the GUI wallet and zend are not running!

Thank you for the info. I cannot find the wallet.dat file. This is a windows installation, and I have searched everywhere in the wallet folder where I unzipped the download. Can you suggest a proper path to the file?
Frank Wyatt
Ma.k-Tau-IG
 maksig

From: vaklinov<EMAIL_ADDRESS>Sent: Tuesday, November 07, 2017 2:28 PM
To: ZencashOfficial/zencash-swing-wallet-ui
Cc: Canefire; Author
Subject: Re: [ZencashOfficial/zencash-swing-wallet-ui] Installing on second PC (#25)
The wallet.dat file contains the private keys to controlling the ZEN coins. The wallet.dat file may be copied manually when the GUI wallet and zend are not running. Make sure you have a backup copy of it on a safe external medium.
The wallet.dat file may also be transferred from one PC to another ... when the GUI wallet and zend are not running!
—
You are receiving this because you authored the thread.
Reply to this email directly, view https://github.com/ZencashOfficial/zencash-swing-wallet-ui/issues/25#issuecomment-342594501  it on GitHub, or mute https://github.com/notifications/unsubscribe-auth/AK1peGoI2txiGBNU9w2s2GVEAn4aHJbsks5s0K9EgaJpZM4QVOoy  the thread.  https://github.com/notifications/beacon/AK1peOFdZAOTak3_jo2pU0Reh1M9aHFWks5s0K9EgaJpZM4QVOoy.gif

Found wallet.dat in users..appdata...roaming. Exchanged into new PC, worked as it should. Thanks for the help.


The password email may be sent to the spam folder

From the antonivs's comment on reddit.
Edit: Forgot to mention, I installed it with no trouble except that I was dutifully
waiting 20+ minutes for the password email, when I realized that it had gone
into my junk folder like 15 minutes before. I guess that's because the from
address is invalid.

I've added the notice about the password email to README. As the other option, it is possible to ask the SES ARN and FROM address and send the verification email from the address. But I didn't since I don't want to increase parameters to create a stack.
Screenshot:


Pacman has problems with architecture recognition? Libraries libgpg-error.

/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x3c4): undefined reference to libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x3c4): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x50b): undefined reference to libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x50b): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x6eb): undefined reference to libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x6eb): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x738): undefined reference to libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x738): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x778): undefined reference to libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x778): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x78c): more undefined references to libintl_gettext' follow /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x78c): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x7a0): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x7c8): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x7dc): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext' /usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x7f8): relocation truncated to fit: R_X86_64_PC32 against undefined symbol libintl_gettext'
/usr/lib/libgpg-error.a(libgpg_error_la-argparse.o):(.text+0x80c): additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:474: cleanupdelta.exe] Error 1

I forgot about the libgpg 1.31-1 and pacman 5.1.0-2 versions.

I cant reproduce this because I already upload this packaes

I have this problem because I just loaded a new version of pacman. And I was debugging pacman myself with the newly found errors from the repository. The problem is the new libgpg-error library.

What the problem?
This https://github.com/Alexpux/MSYS2-packages/commit/0a181ce4a084bb0192137f789a86c5234ca76c68 fix the linking errors

My version of mingw-w64-cross-gcc-arm has problems with pacman and I had to add a patch but in the new version libgpg-error-1.31 pacman had given problems with the compilation. I checked pacman from your repository but now I see clearly that this is my mistake. I added an old patch file.


Stop -dsgc passing invalid empty parameter to git

When -dsgc (or its expanded version) is given to makejdk.sh it results in a blank parameter being given to the git command (without -dsgc it's set to --depth=1) which confuses git and gives this error (note the double space between clone and -b wher the "empty" parameter is sitting:
Git repo cloning mode: deep (preserves commit history)
git clone  -b dev https://github.com/adoptopenjdk/openjdk-jdk11.git /space/pi3/workspace/openjdk11_build_arm32_linux/openjdk
Too many arguments.

usage: git clone [options] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet

33 seems to have passed. It looks like (I'm not entirely sure why) this problem is surfacing when I try to run a AO10/hotspot release build too - https://ci.adoptopenjdk.net/job/openjdk10_build_x86-64_linux/251
(Requirement via DavidJoeColey on twitter who was asking me for an updated 10)


Try using yarn instead of npm to install our project dependencies to fix tests

For some reason travis is failing to install dependencies with npm, and so I'm throwing a hail mary here and seeing if just switching to yarn is enough to fix tests.

The actual fix ended up being to use LTS node instead of the oldest available. But using Yarn is a good thing to do too.

Thanks @korvinszanto


Training through an Estimator is much slower than writing a for loop when using a Dataset

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Happens with stock code
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu Server 17.10.1
TensorFlow installed from (source or binary):
Source
TensorFlow version (use command below):
b'v1.6.0-0-gd2e24b6039' 1.6.0
Python version:
3.6
Bazel version (if compiling from source):
0.11.0
GCC/Compiler version (if compiling from source):
gcc (Ubuntu 6.4.0-8ubuntu1) 6.4.0 20171010
CUDA/cuDNN version:
9.1/7.0.5
GPU model and memory:
not applicable
Exact command to reproduce:
not applicable

I have a dataset that consists of one feature and one label, both are int64, there are 7166 steps of batches consisting of 128 and run for 10 epochs. I have tested this using two approaches, the first uses 100 tfrecord files that are read through the tf.data.Dataset API, the second reads the tfrecord data into memory then creates a tf.data.Dataset utilizing from_tensor_slices.
Obviously the in-memory version runs much faster than the read-from-disk method.
When I train my model using a custom while loop, 10 epochs runs 20 seconds faster than running it using the tf.estimator.Estimator.train API. This 20 seconds is a blanket 20 seconds, whether I am running it using the in-memory dataset or the read-from-disk method.
I thought, the overhead could be from storing checkpoints, etc. so I supplied a RunConfig that disables checkpoints and sets the various save/log step counts to very high numbers. This helped, but only a little bit, it went from a blanket 20 seconds to a blanket 17 seconds. 17 seconds doesn't seem like much, but if I am running for a large number of epochs, or if I use a much larger dataset, those seconds can turn into hours.
Is this something inherent with tf.estimator.Estimator or could I be hitting a problem?

Can you reproduce this issue again with tf-nightly? Thanks

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 44 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


When polly is used at rest client level and an (locally running) API is called which throws an error, the API is not retried

Description
I've created an API running locally which throws/returns a NotFound exception. A NotFound exception code is also added in the policy when creating the Policy Handler. The API is expected to be retried, but the retry never happens.
To Reproduce
   var testClient = GetRestClient();

    try

    {

        await testClient.GetTestData("test");

    }

    catch(ApiException ex)

    {

        Console.WriteLine(ex.StatusCode);

    }
//////////////////////////// RestClient/////////////////////////
private ITeamplayEntitlementApi GetRestClient()
{

    var policyHandler = new PolicyHttpMessageHandler(RetryPolicyOnException());

    DelegatingHandler delegatingHandler = policyHandler;

    if (delegatingHandler != null && delegatingHandler.InnerHandler == null)
    {
        delegatingHandler.InnerHandler = new HttpClientHandler();
    }

    HttpClient httpclient = new HttpClient(delegatingHandler)
    {
        BaseAddress = new Uri("https://localhost:5001/weatherforecast")
    };
    return RestClient.For<ITestApi>(httpclient);
}

private IAsyncPolicy<HttpResponseMessage> RetryPolicyOnException()
{
    TimeSpan timeOut = TimeSpan.FromMilliseconds(50000);
    void OnRetry(Exception ex, TimeSpan t, int retryAttempt, Context context)
    {
        if (retryAttempt <= 2)
        {
            Console.WriteLine($"Call failed with exception : {ex.Message}. The call will be retried.");
        }

        Console.WriteLine($"Call failed. Retrying the call. Retry-Attempt:{retryAttempt}.");
    };
    return new DefaultPolicyFactory()
                .BuildPolicyBuilder(new List<int>())
                .WaitAndRetryAsync(new List<TimeSpan> { TimeSpan.FromSeconds(1), TimeSpan.FromSeconds(1) , TimeSpan.FromSeconds(1) }, OnRetry)
                .AsAsyncPolicy<HttpResponseMessage>();
}

public class DefaultPolicyFactory : IPolicyBuilderFactory

{

    public PolicyBuilder BuildPolicyBuilder(List<int> errorCodesToExclude)
    {

        return Policy.Handle<ApiException>(ex => ex.StatusCode == HttpStatusCode.NotFound && !IsExcluded(errorCodesToExclude, HttpStatusCode.NotFound))

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.RequestTimeout && !IsExcluded(errorCodesToExclude, HttpStatusCode.RequestTimeout))

                    .Or<ApiException>(ex => (int) ex.StatusCode == 423 && !IsExcluded(errorCodesToExclude, 423))

                    .Or<ApiException>(ex => (int) ex.StatusCode == 425 && !IsExcluded(errorCodesToExclude, 425))

                    .Or<ApiException>(ex => (int) ex.StatusCode == 429 && !IsExcluded(errorCodesToExclude, 429))

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.InternalServerError && !IsExcluded(errorCodesToExclude, HttpStatusCode.InternalServerError))

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.BadGateway)

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.ServiceUnavailable)

                    .Or<HttpRequestException>()

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.GatewayTimeout)

                    .Or<ApiException>(ex => ex.StatusCode == HttpStatusCode.TooManyRequests);

    }

    private static bool IsExcluded(List<int> errorCodesToExclude, HttpStatusCode statusCode)
    {
        return errorCodesToExclude.Contains((int) statusCode);
    }

    private static bool IsExcluded(List<int> errorCodesToExclude, int statusCode)
    {
        return errorCodesToExclude.Contains(statusCode);
    }
}

///////////////////////// API ///////////////////////////////////
  [HttpGet("test")]
    public IActionResult Get()
    {
        Console.WriteLine("API Called"); // Gets called only once
        return NotFound();
    }

Version Info

RestEase version: 1.5.0
Target framework version: net6.0

Additional Info
One surprising thing is when I don't start the API, and just run the code to call API with retry, the call fails with error "No connection could be made because the target machine actively refused it" and it gets retried.

The layers here are RestEase --> Polly --> HttpClientHandler --> Internet. RestEase is the thing which throws an ApiException, but Polly never sees that this happens after Polly has returned a response to RestEase.
Write your policy based on what the HttpClientHandler returns, i.e. based on the HttpResponseMessage.


WinAppDriver and WinForms MenuStrip control

I'm using WinAppDriver v1.1.1809.18001 and am having problem seeing items within a MenuStrip dropdown menu in a WinForms app. I can reproduce the issue by making a new C# WinForms application in VS2015, adding a MDIForm and editing program.cs to open the MDI form on startup.
Using WinAppDriver I can see and click the menus along the menu bar (File / Edit / Help) , but I can't select or click items within the dropped down menus.
Using inspect.exe in MSAA mode and navigating the MDIForm with the mouse, I can see items within the menu (e.g. Help / About).
Using inspect.exe in UI Automation mode and navigating the MDIForm with the mouse, I can't see items within the menu. Navigating with the keyboard, the Focus event gets the Name of the menu item in the tooltip, but it is not shown in the main inspect.exe application pane.
Now I can work around this like this:
 // Click Help
 session.FindElementByName("Help").Click();
 // Use keyboard to select About item.
 session.Keyboard.SendKeys("a");

But I'd prefer to select and click the About item more explicitly.
This comment in issue 185: https://github.com/Microsoft/WinAppDriver/issues/185#issuecomment-350407651  suggests that properly implemented MSAA controls will project into UIAutomation. Is there anything that can be done to help the ToolStripMenuItem control project into UIAutomation properly? Thanks

Hi @edw-c,
We don't know of any way to modify ToolStripMenuItem to support UIAutomation properly - though there have been discussions on this topic before.

@edw-c did you find a properly way to click the menuitem explicitly?

@tu-mcleish - Unfortunately not.

@edw-c
I am seeing the same issue. I am clicking on Help and trying to get to About in the app.  When I try using the keyboard shortcut to select the About menu nothing happens though.  Any thoughts??
public void ClickMenuItem(string menuItem)
{
session.FindElementByName(menuItem).Click();
}
[TestMethod]
public void VerifyMenuBar()
{
ClickMenuItem("File");
ClickMenuItem("Reports");
ClickMenuItem("Maintenance");
ClickMenuItem("Customize");
ClickMenuItem("Utilities");
ClickMenuItem("Help");
//Open About
session.Keyboard.SendKeys("b");
    }

I've recently come across this same issue - the WinForms menu bar buttons (File, Edit, Help, etc) can be found easily, and the menus that open from those buttons can have an AccessibilityName property defined and found using a desktop driver. However, in the PageSource, those menus have no child items for the individual menu buttons; the menu is a black box control.
Here's where it gets interesting. Using the inspect.exe tool, set to Watch Cursor, I get the same issue as found in the PageSource: menu (which appears as a separate window in the UI hierarchy), but no individual items. However, if you set inspect to use Watch Focus, you can mouse over individual menu items and find them perfectly (and the menu and entries are both part of the application hierarchy).
Why, if that information is available, does it not appear in the PageSource that WinAppDriver builds? And what's the difference in the Watch Focus and Watch Cursor functionalities in inspect.exe that allows the former to find what we're looking for?


outdated text in universal-windows-apps-cpp.md

the tutorial is updated for UWP.

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

Thanks @jiangsheng


Turkish translation added

The maintainers of this repository would appreciate it if you could provide more information.

I have added a Turkish translation


Use protobuf-java-util for protobuf parsing (to and from JSON)

Description of the Change
I propose to use http://mvnrepository.com/artifact/com.google.protobuf/protobuf-java-util for parsing protobuf messages to and from JSON instead of a combination of self-written code and http://mvnrepository.com/artifact/com.googlecode.protobuf-java-format/protobuf-java-format.
Benefits

Exchanging protobuf-java-format (is not being maintained anymore, last release: November 2015) with the actively maintained protobuf-java-util
protobuf-java-util provides standardized serialization and deserialization
version of protobuf-java-util matches the protobuf version we use in the projects
using official code published by google instead of our own version

Possible Drawbacks
None, as far as I know.

Thomas, I think the implementation looks great.  I think we need some more test cases before I'd be comfortable merging it, however.  enums, byte strings and sub-messages are my main concerns.

Okay, I will add some more testcases.


Kubernetes KIND failing to complete any workflow

Summary
When running in Kubernetes KIND with extra volume mounts to the host machines docker sock, the following error occurs in the executor pod every time (Error response from daemon: No such container:). This causes failure even if the other pod succeeds.
If no extra mount is added, the pods eventually fail with no logs, however, there is an event saying: MountVolume.SetUp failed for volume "docker-sock" : hostPath type check failed: /var/run/docker.sock is not a socket file
Motivation
All development is conducted on KIND clusters. We are attempting to wrap Argo workflow in our Operators to standardize our CI process

Got an answer in the Slack channel. Posting the answer here in case someone is searching the web for something similar:
Change your containerRuntimeExecutor to pns in your configmap. This will get it to work with containerd vs dockerd based installations. Thank you Daniel Herman

Got an answer in the Slack channel. Posting the answer here in case someone is searching the web for something similar:
Change your containerRuntimeExecutor to pns in your configmap. This will get it to work with containerd vs dockerd based installations. Thank you Daniel Herman

Can you show the configuration in ConfigMap? There is no default configuration in my ConfigMap.
kubectl get cm workflow-controller-configmap -n argo -o yaml
apiVersion: v1
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ConfigMap","metadata":{"annotations":{},"name":"workflow-controller-configmap","namespace":"argo"}}
  creationTimestamp: "2020-09-08T03:47:13Z"
  name: workflow-controller-configmap
  namespace: argo
  resourceVersion: "701849"
  selfLink: /api/v1/namespaces/argo/configmaps/workflow-controller-configmap
  uid: 64a9089e-4fbe-49d5-8b28-c2bb2a99be7e

apiVersion: v1
kind: ConfigMap
metadata:
  name: argo-workflow-controller-configmap
  labels:
    chart: argo-0.10.2
    release: argo
    heritage: Helm
data:
  config: |
    instanceID: INSTANCEID
    containerRuntimeExecutor: docker #change this to pns if on kind
    artifactRepository:
      s3:
        accessKeySecret:
          key: accesskey
          name: argo-minio
        secretKeySecret:
          key: secretkey
          name: argo-minio
        bucket: argo-artifacts
        endpoint: argo-minio:9000
        insecure: true

apiVersion: v1
kind: ConfigMap
metadata:
  name: argo-workflow-controller-configmap
  labels:
    chart: argo-0.10.2
    release: argo
    heritage: Helm
data:
  config: |
    instanceID: INSTANCEID
    containerRuntimeExecutor: docker #change this to pns if on kind
    artifactRepository:
      s3:
        accessKeySecret:
          key: accesskey
          name: argo-minio
        secretKeySecret:
          key: secretkey
          name: argo-minio
        bucket: argo-artifacts
        endpoint: argo-minio:9000
        insecure: true

Thank you.


ARXIVNG-974 cleanup and refactoring

Coverage increased (+4.8%) to 88.458% when pulling 31c7884102d12f8582a01d3c469f392292fab6b9 on feature/ARXIVNG-974 into 08df4e0196a04a06eac1d26477b3ad56ebf56f08 on develop.


Ability to view HTTP headers

Would it be possible to add an inspector on the HTTP requests to view the headers and body as well?

You can try add new hooks in "+ Hooks" tab. But I really recommend you use a "proxy tool", like Burp Suite.


add template isSlice in ndslice.slice

As a Slice can be a Range, I was finding the template isSlice quite useful when working on the random API. Probably it makes sense to expose this template to the user too - what would be the best spot to add it?

Lets think about it after sparse matrixes

Current coverage is 98.12%

Merging #86 into master will increase coverage by +0.01% as of 41a8e81

@@            master     #86   diff @@
======================================
  Files            7       7
  Stmts         2498    2500     +2
  Branches         0       0
  Methods          0       0
======================================
+ Hit           2451    2453     +2
  Partial          0       0
  Missed          47      47

Review entire Coverage Diff as of 41a8e81

Powered by Codecov. Updated on successful CI builds.

Lets think about it after sparse matrixes

ok, but they will have a different type?
E.g. isSparse and maybe unified to isMatrix?

ok, but they will have a different type?

This is complex quesion

update: it's already part of slide.d, but just private
private enum bool _isSlice(T) = is(T : Slice!(N, Range), size_t N, Range);

see https://github.com/DlangScience/mir/blob/master/source/mir/ndslice/slice.d#L140

update: it's already part of slide.d, but just private

OK, please move this declaration to ndslice.slice and make it public

Should be opened in discussed in Phobos


Update main.go

Includes a comment explaining the purpose of the code, a constant for the exit code, and error handling for the os.Exit() function call.

That's not a runnable code, it's only used for testing purposes, so let's keep as it is.


Provisioning from unverified domain

Hi,
the "Connector limitations" section mentions that "Atlassian Cloud allows provisioning of users only from verified domains.", however, Atlassian added this feature as mentioned here

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

ID: 04509836-867e-279f-c1d6-135a237d357e
Version Independent ID: e05a10ce-c46b-334e-78e2-30b416ed904a
Content: Tutorial: Configure Atlassian Cloud for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/atlassian-cloud-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @zhchia
Microsoft Alias: jeedes

@jankoada
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

#reassign:twimmers

Thanks for the feedback, I'm made a doc change to address this
#please-close


Support raw AAC in HLS

Originally raised in https://github.com/google/shaka-player/issues/887#issuecomment-338913950
Our HLS parser must guess container and codecs from the limited information provided in an HLS playlist.  Currently, we don't understand raw AAC.
MediaSource seems to support raw AAC with the MIME type "audio/aac" (no codecs parameter), so we should be able to handle this.
Sample streams:
https://content.jwplatform.com/manifests/vM7nH0Kl.m3u8

Recognizing raw AAC is easy, but given the new timestamp parsing code we are using to fix #1011, we still won't be able to fully support raw AAC until we have a parser for it.

@media-square, no update.  We have not worked on this at all yet.
Re: the patch suggested by @avelad, no, that would not work for live streams as far as I can tell.

Will the work involved here be a function to getStartTimeFromAacSegment_ implemented to parse the aac segment and pull it's start time?

Yes, that's the idea.

So basically, there is a solution which should work for live streams but...
When can we expect a patch or will this issue not being fixed?

We are interested in this patch as well

+1

@bes @peet-j Thanks for expressing interest!
@joeyparrish Could you, please, advise if this is on our road map?

As far as I can tell, containerless formats like MP3 and raw AAC do not have their own timestamps.  So long as the video and audio content are properly aligned and the content is VOD, we could just use the patch from @avelad.  But I don't think there are any timestamps to parse out, so we're left with guessing at "0".
I'm not certain what will happen with that patch and any non-zero-start-time content or any live content, though.  What happens for raw AAC in live depends on how MediaSource behaves with timestamp-less raw content.  I'm reaching out to the Chrome team for clarification, but I suspect this will not work yet for live.

I heard from Chrome team.  The way AAC and MP3 work in MediaSource is that timestampOffset determines the starting time of each new append in the SourceBuffer, and after each append, the browser updates timestampOffset to reflect the amount of data that was appended.  This is 'sequence' mode, even if you didn't set it explicitly on the SourceBuffer.
If we had the right metadata, we could make that work, including for live.  But it will require refactoring in our HLS implementation.  That refactor would overlap significantly with #1558.

Hi @joeyparrish, are there any updates on when this feature might be implemented? Thanks!

I happened to see this issue in passing. Just to correct the previous comment about containerless formats not having timestamps - this isn't true. The HLS spec requires that all packed audio formats (such as raw AAC/MP3 etc) have an ID3 PRIV tag inserted at the very start with the timestamp information.
Please see: https://tools.ietf.org/html/draft-pantos-http-live-streaming-23#section-3.4
This is a "MUST" item in the spec, and it goes so far as to add that clients "SHOULD NOT" play back audio data like this unless it contains this timestamp!
BR
Tony

It turns out that the timestamps in the HLS parser are only a small part of the problem of supporting raw AAC.  The bigger issue is support for containerless formats generally at the MediaSource level.  Every time we clear the buffer or seek, the timestampOffset needs to be set before appending containerless segments.
I filed issue #2337 to track full containerless format support.  I will close this issue as soon as the HLS parser has been taught to recognize raw AAC.  Until we can play it correctly, though (#2337), we will reject raw AAC HLS content.


[UT] fix s3fs related unit tests

workaround minio special feature
close s3 clients in UT to avoid aws sdk shutdown before all aws objects destroyed

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[X] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[X] 3.2
[X] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio backport branch-3.2 branch-3.1

@mergifyio backport branch-3.0


Shift key invokes FancyZones when not moving the mouse

Microsoft PowerToys version
0.75.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
FancyZones
Steps to reproduce

I updated to PowerToys 0.75.0 through the in-app updater from the previous version.
After the update, FancyZones was showing its zones when holding the Shift key, but not moving the mouse.
I toggled the option "Hold Shift key to activate zones while dragging a window" off and then toggled it back on.
Issue stopped after the setting was back where it originally was, but I had to turn it on/off to make the setting behave as expected.

Looks like a post-update bug for 0.75.0.
✔ Expected Behavior
FancyZones should only bring up its zones if holding Shift and moving the mouse.
❌ Actual Behavior
FancyZones showed its zones when only holding Shift. When this is happening, other keypresses aren't registered, so I found this out by simply trying to type an asterisk (*) character. The zones loaded behind my active windows, so I didn't notice the bug at first either.
Other Software
No response

Not able to repro this, going to close. Let us know if you see this again!


Migrate run details page to GraphQL.

Summary
Migrating the run details page to GraphQL

Wow, this was an incredible change @gbochora! Unfortunately, we're looking at dramatically reducing the scope of the Playbooks featureset, and I don't think we'll need these changes right now. Still, appreciate the effort, and sad that we didn't get to ship this together :/


[BUG] macOS: Opening the vult backup file does not process the backup file

Describe the bug
Opening the backup via mac app only opens the import view and leaves the field blank.

it is working

@johnnyluo @Rockindash imo it is not working properly.

[ ] When opening it always opens a new window, It should just open import view in the already opened screen
[ ] Some backups work to be imported and loaded some do not.

I think we need to hone it out still


Correction to firehose migration doc

Correction to firehose migration doc.
This PR has:

[x] been self-reviewed.

Already backported to 25.0.0 in #13419


refactor(test): renames the output vars in test;

resolves #2583
as per the discussion on the above issue.

This is has been fixed by #2640; closing this PR.


MSID: 93906 Version: 2 DOI: 10.1101/2<IP_ADDRESS>2953

MSID: 93906
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2953
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=93906
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2953

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/93906v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2953
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/93906/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

waiting for AR to update


#24 Updated session.ts under api and player.ts under database

Updated getParticipants to parse sessionId correctly. Wrote the getPlayersForSession function

#24

looks good


checkboxes do not validate with v-model

Versions

vee-validate: 2.1.0-beta.8
vue: 2.5.2

Describe the bug
I have multiple check boxes. All are bound to v-model. I have vee validate on the first one, but it only validates that specific one and does not validate the rest. Meaning the form can not be submitted with out that specific checkbox checked. For the rest of the checkboxes, vee validate does not care if checked or not.
Expected behavior
Based on what's written on the documentation, v-validate directive on the first checkbox would suffice. But, that's not the case in this situation.
Desktop (please complete the following information):

OS:  iOS
Browser: firefox
Version: 61.0.1

https://codesandbox.io/s/24qp725w2n
Thanks

You need to bind the checkboxes to an array. Check the VueJS docs for details https://vuejs.org/v2/guide/forms.html#Checkbox.
I have updated your code: https://codesandbox.io/s/18qp7m0r4l.
NB: Vee-Validate's required validation will not validate the length of the array https://baianat.github.io/vee-validate/guide/rules.html#required. it will make sure it is not empty. Once an array is not empty, it will pass the validation.
What you're looking for is the length validation. https://baianat.github.io/vee-validate/guide/rules.html#length. It should be able to check the length of the array.. But for some reason, it doesn't work and that is why I am here :).
So best luck.

The problem you are facing is due to the fact that each checkbox in your example is using a different model than the first one, which doesn't work well with how vee-validate expects the checkboxes/radio buttons to work. Normally they all would modify the same model.
What @clintonyeb said is the workaround for your case, have your checkboxes insert/remove items from an array and validate its length instead, you can easily then transform it back to an object to match with your app logic, but for validation purposes it should be an array.

I have submitted a pull request clarifying this in the docs :)

I need to store those checkboxes' values in an object in order to push them to the database at the backend.
I am gonna figure it out a way to use an array instead and then convert into an object, just like you suggested.
Thank you guys, I appreciate your help with this.. both of you..


Hooks with Typescript:  ts(2339) Property 'handleClickOutside' does not exist.

Update: Another thing I noticed with this pattern is that when you have multiple instances of the same Component, only the last one triggers handleClickOutside.
Here is my code, grossly simplified (sorry if it is more of a TS question rather than this library, but in any way it would be nice to see an example).
error: Property 'handleClickOutside' does not exist on type '({ options, }: Props) => Element'. ts(2339)
The code works fine but in the editor Dropdown.handleClickOutside lines highlights this error.
Other than using // @ts-ignore, how can I solve this issue? how can I specify the property?
import * as React from 'react';
import onClickOutside from 'react-onclickoutside';

interface Props {
    options: string[];
}

export const Dropdown = ({
    options,
}: Props) => {
    const [isOpen, setIsOpen] = React.useState(false);

    Dropdown.handleClickOutside = () => {
        setIsOpen(false);
    };

    return (

                {options.map((option, i) => {
                    return (

                            {option}

                    );
                })}

    );
};

export default onClickOutside(
    Dropdown,
    { handleClickOutside: () => Dropdown.handleClickOutside }
);

try this in the same file:
namespace Dropdown {
  export let handleClickOutside: () => void;
}

thanks for the tip 👍

I tried this solution but typescript complains this:

Cannot redeclare block-scoped variable 'StoryListInput'.

I become the same error as @nerdmax

I also tried it and I get "Duplicate identifier Dropdown".
react-onclickoutside v6.8.0, typescript v.3.3.4000

Third on the train, the create-react-app default linter doesn't like it
Failed to compile.

./src/components/MenuBar/MenuBar.tsx
  Line 45:  ES2015 module syntax is preferred over custom TypeScript modules and namespaces  @typescript-eslint/no-namespace

Search for the keywords to learn more about each error.

not an error, but if someone could suggest an alternative solution, would be great.

As a solution you can get rid of this library and use this small hook from https://usehooks.com/useOnClickOutside/:
import { useState, useEffect, useRef } from 'react';

// Usage
function App() {
  // Create a ref that we add to the element for which we want to detect outside clicks
  const ref = useRef();
  // State for our modal
  const [isModalOpen, setModalOpen] = useState(false);
  // Call hook passing in the ref and a function to call on outside click
  useOnClickOutside(ref, () => setModalOpen(false));

  return (

      {isModalOpen ? (

          👋 Hey, I'm a modal. Click anywhere outside of me to close.

      ) : (
        <button onClick={() => setModalOpen(true)}>Open Modal</button>
      )}

  );
}

// Hook
function useOnClickOutside(ref, handler) {
  useEffect(
    () => {
      const listener = event => {
        // Do nothing if clicking ref's element or descendent elements
        if (!ref.current || ref.current.contains(event.target)) {
          return;
        }

        handler(event);
      };

      document.addEventListener('mousedown', listener);
      document.addEventListener('touchstart', listener);

      return () => {
        document.removeEventListener('mousedown', listener);
        document.removeEventListener('touchstart', listener);
      };
    },
    // Add ref and handler to effect dependencies
    // It's worth noting that because passed in handler is a new ...
    // ... function on every render that will cause this effect ...
    // ... callback/cleanup to run every render. It's not a big deal ...
    // ... but to optimize you can wrap handler in useCallback before ...
    // ... passing it into this hook.
    [ref, handler]
  );
}

Defining the handler on the function after its definition worked for me. I think it's ok, as its value will be set on rendering the component anyways.
import {useState} from 'react'
import onClickOutside from 'react-onclickoutside'

const UserInfo = () => {
  const [menuVisible, setMenuVisible] = useState(false)
  UserInfo.clickOutside = () => setMenuVisible(false)

  return (

 setMenuVisible(!menuVisible)}
    >

Click me

I am zee menu

I am zee menu

  )
}
UserInfo.clickOutside = null

export default onClickOutside(UserInfo, {
  handleClickOutside: () => UserInfo.clickOutside,
})

Just a note: if you've already written the code to make hooks work, PRs that add a hook solution are most certainly welcome, and I'll be more than happy to push out a new version.


No AP-Mode-Access

Checklist

[X] I have installed the latest release (or BETA) version of the integration and home assistant.
[X] I have prepared DEBUG log output (for technical issues) | In most of the cases of a technical error/issue I would have the need to ask for DEBUG log output of the integration. There is a short tutorial/guide 'How to provide DEBUG log' here
[X] I am aware that rotating the tibber pulse reading head anti clockwise can improve data quality | See this user comment and the next comment as well
[X] I confirm it's really an issue | In the case that you want to understand the functionality of a certain feature/sensor Please be so kind and make use if the discussion feature of this repo (and do not create an issue) - TIA

Add a description
I tried to set the bridge to AP-Mode for at least 5 times, both discribed ways doesn't work - no green light, no AP-WLAN available.
Bridge-Model T3H01, delivered in 12.2023. What can I do?
Thanks in advance!
Add your DEBUG log output
No response

Contact Tibber support


feat!: masking exception for readiness checks

Description
BREAKING CHANGE.
Masking known exceptions for all readiness checks - they will be reported as CheckStatus.ERROR
Motivation and Context
There are two reasons:

for readiness checks, the exceptions thrown by FirewallProxy usually means that the check failed. Reporting that fact in one situation as failed check and in the other as exception made interface not consistent
when wrapping this class into an Ansible module, when an exception is thrown, the Ansible output becomes cluttered and hard to read (especially if you run the code against several devices at the same time). For readiness checks it makes more sense to fail the module with an error message, even if it comes from an exception.

Please keep in mind that this change is only for known exceptions. All other exception coming from pan-os-python or any other package are thrown as usual.
Also closes #44
This PR also introduces some reorganisation in the exception classes, hence marked as a breaking change.
How Has This Been Tested?
All method were run using example scripts.
Screenshots (if appropriate)

Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

TODO:

[ ] line length to 130
[ ] docstring line length ~130

This PR should also help to close #65 as it will bump the minor version by 1


Add ssh_docker module

Looking really good. :) I think you need to rebase and/or merge to get the package.json (and presumably yarn.lock) synchronized, and add a test suite and this is good to go. :)

this is really nice


Unexpected search ordering

For this search: https://beta.webcomponents.org/search/paper-button
Expected
<paper-button> to be at the top, or at least the top results to be some combination of the most popular and closest textual match to the tag name
Actual
<paper-button>, which has the most github stars and is the closest match to the search is the fifth search result.
Top ten search results:

material-toggle-button
paper-buttons-group
paper-button-group
paper-icon-button
paper-button
paper-confirm-button
paper-toggle-button
paper-more-button
paper-radio-button
paper-menu-button

Hmm, this is tricky to rectify. I think in our attempts to make sure better, we've actually degraded quality in some cases. The prefix matching and description mean that button can get matched more often and produces higher rankings.
Two solutions come to mind:

Implement weighting - not supported by GAE, but we could implement our own weighting system which works by adding a field multiple times to the search document based on its weight.
Implement a second query and coalesce results - searching for repo: paper-button produces more expected results, so we could merge these with the existing results. This would double the number of search queries & hence performance and I imagine the coalescing will be difficult with cursors etc.

@dstockwell: thoughts? I'm leaning towards the weighting solution to fake field weighting.

Thanks for filing @rictic!
Latest set of results for the same query:

Awesome! I tried a handful of other searches and the results all seemed great. Thanks!


Urlencode the arguments before passing to the API

There is a company M&M in India whose ticker symbol is M&M. This causes an issue when querying the API directly. The & needs to be encoded before passing it along to the API.

Let me know if I can take this up and submit a PR.

Yes, definitely.


Increment version with DDM

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/86021
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.4 -m "<description of version>" ec664712c80b1c5bcbb56bfaca1f4fbae339260f
git push origin v0.3.4


Clarify nuget/mono isn't supported and never was on Unixy platforms.

There are 35 files in this docs repo that mention mono. This is a good first step, but I think we need to change wording on other pages too, for example, the page on installing/obtaining nuget. For better or worse, about half the mono search results look to be release notes, and I don't think we need to make any changes there, so I think the effort required is smaller than the 35 files with results makes it sound to be.

I agree that there are no changes really needed to be made. Older mono versions will still exist and be relevant. We can add notes later


Release new version to enable new webdriver-manager that fixes core functionality on Windows

Without it selene can't run tests on Firefox cause it won't start.

Uh!
we'll try to fix this asap!

@alkuzad, done!
https://pypi.org/project/selene/2.0.0a39/

normally it wouldn't be a problem but with poetry ... I managed to hack it using git dependencies instead of pypi but I'm glad you released new version fast :) It's common problem in OpenSource that not every merge == new release and ones that seem not important get lost in the limbo


os-squid: segmentation fault at reload of service

Important notices
Describe the bug
If i reload the service after changing the configuration a popup window appears which shows parsing the squid.config. The last line shows the message "Segmentation fault"
The changes took no effect.
To Reproduce
Install opnsense 24.1, upgrade to 24.1.1, install plugin os-squid.
Change values in plugin Squid Web proxy, apply  and then restart service in upper right corner
A Pop-up window appears with the last line "Segmentation fault"
Expected behavior
clean restart of the service
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
an installation which started with 23.7, update to 24.1.1, does not have this bug.
*Environment
OPNsense 24.1.1 (amd64).
in virtual box vm

Opening a new issue using a template


severity as array in the call to the formatter

The formatter gets called like this on line 96:
clean(formatter.call([severity], Time.now, progname, communication))

Any reason why the severity is wrapped in an array? The default ruby logger does not use an array here but sends a Severity object which provides a label like "INFO" or "DEBUG" when .to_s is applied.
We are migrating to syslog for all logging in our application and just noted that the call to the formatter is different.

Well here the commit that adds the formatter : https://github.com/crohr/syslogger/commit/e9749cdedee9d99e07eb20065dafd1f73e78affe
Nothing explains why severity is wrapped in an array...


CldOgImage.vue component & useCldOgImage.ts composable

Is your feature request related to a problem? Please describe.

https://next-cloudinary.spacejelly.dev/components/cldogimage/basic-usage
https://next-cloudinary.spacejelly.dev/helpers/getcldogimageurl/basic-usage
Describe the solution you'd like

Describe alternatives you've considered

Additional context

these are both basically identical to their non-OG counterparts, the only thing they do is set safe defaults
https://github.com/colbyfayock/next-cloudinary/blob/main/next-cloudinary/src/components/CldOgImage/CldOgImage.tsx#L20
https://github.com/colbyfayock/next-cloudinary/blob/main/next-cloudinary/src/helpers/getCldOgImageUrl.ts#L13
one thing i decided to add in my implementation of CldOgImage is a default Twitter Title for OG images, because without it, the Large Cards won't render on Twitter. so if someone doesnt provide a value, it's just an empty tag, which is better than not rendering
maybe the Nuxt API for the Head component has a better solution for dynamically grabbing the title for instance from the page


Event for open the dropdown

I think it'll be very useful to add a new event when the dropdown is opening. This could help to fetch options with ajax.

+1

It's done: https://github.com/optimistex/ngx-select-ex/releases/tag/3.3.5