Failing Test: replicaset-debian-720

I, [2015-07-14T21:43:58.674590 #40537]  INFO -- replicaset-debian-720: -----> Cleaning up any prior instances of <replicaset-debian-720>
I, [2015-07-14T21:43:58.675110 #40537]  INFO -- replicaset-debian-720: -----> Destroying <replicaset-debian-720>...
I, [2015-07-14T21:44:01.278619 #40537]  INFO -- replicaset-debian-720: ==> default: Forcing shutdown of VM...
I, [2015-07-14T21:44:02.424581 #40537]  INFO -- replicaset-debian-720: ==> default: Destroying VM and associated drives...
I, [2015-07-14T21:44:02.673779 #40537]  INFO -- replicaset-debian-720: Vagrant instance <replicaset-debian-720> destroyed.
I, [2015-07-14T21:44:02.675779 #40537]  INFO -- replicaset-debian-720: Finished destroying <replicaset-debian-720> (0m4.00s).
I, [2015-07-14T21:44:02.676038 #40537]  INFO -- replicaset-debian-720: -----> Testing <replicaset-debian-720>
I, [2015-07-14T21:44:02.676163 #40537]  INFO -- replicaset-debian-720: -----> Creating <replicaset-debian-720>...
I, [2015-07-14T21:44:04.298334 #40537]  INFO -- replicaset-debian-720: Bringing machine 'default' up with 'virtualbox' provider...
I, [2015-07-14T21:44:04.499142 #40537]  INFO -- replicaset-debian-720: ==> default: Importing base box 'opscode-debian-7.2.0'...
I, [2015-07-14T21:44:11.341627 #40537]  INFO -- replicaset-debian-720:
Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%
Progress: 50%
Progress: 60%
Progress: 70%
Progress: 80%
Progress: 90%
==> default: Matching MAC address for NAT networking...
I, [2015-07-14T21:44:12.025526 #40537]  INFO -- replicaset-debian-720: ==> default: Setting the name of the VM: kitchen-mongodb-cookbook-replicaset-debian-720_default_1436924651980_92398
I, [2015-07-14T21:44:13.403672 #40537]  INFO -- replicaset-debian-720: ==> default: Fixed port collision for 22 => 2222. Now on port 2207.
I, [2015-07-14T21:44:13.451170 #40537]  INFO -- replicaset-debian-720: ==> default: Clearing any previously set network interfaces...
I, [2015-07-14T21:44:13.498911 #40537]  INFO -- replicaset-debian-720: ==> default: Preparing network interfaces based on configuration...
I, [2015-07-14T21:44:13.499124 #40537]  INFO -- replicaset-debian-720:     default: Adapter 1: nat
I, [2015-07-14T21:44:13.544690 #40537]  INFO -- replicaset-debian-720: ==> default: Forwarding ports...
I, [2015-07-14T21:44:13.649514 #40537]  INFO -- replicaset-debian-720:     default: 22 => 2207 (adapter 1)
I, [2015-07-14T21:44:13.792632 #40537]  INFO -- replicaset-debian-720: ==> default: Running 'pre-boot' VM customizations...
I, [2015-07-14T21:44:13.835903 #40537]  INFO -- replicaset-debian-720: ==> default: Booting VM...
I, [2015-07-14T21:44:14.061087 #40537]  INFO -- replicaset-debian-720: ==> default: Waiting for machine to boot. This may take a few minutes...
 Retrying...
I, [2015-07-14T21:44:29.834897 #40537]  INFO -- replicaset-debian-720:     default:
I, [2015-07-14T21:44:29.834970 #40537]  INFO -- replicaset-debian-720:     default: Vagrant insecure key detected. Vagrant will automatically replace
I, [2015-07-14T21:44:29.835006 #40537]  INFO -- replicaset-debian-720:     default: this with a newly generated keypair for better security.
I, [2015-07-14T21:44:30.319973 #40537]  INFO -- replicaset-debian-720:     default:
I, [2015-07-14T21:44:30.320045 #40537]  INFO -- replicaset-debian-720:     default: Inserting generated public key within guest...
I, [2015-07-14T21:44:30.379739 #40537]  INFO -- replicaset-debian-720:     default: Removing insecure key from the guest if it's present...
I, [2015-07-14T21:44:30.420910 #40537]  INFO -- replicaset-debian-720:     default: Key inserted! Disconnecting and reconnecting using new SSH key...
I, [2015-07-14T21:44:31.135307 #40537]  INFO -- replicaset-debian-720: ==> default: Machine booted and ready!
I, [2015-07-14T21:44:31.135780 #40537]  INFO -- replicaset-debian-720: ==> default: Checking for guest additions in VM...
I, [2015-07-14T21:44:31.182167 #40537]  INFO -- replicaset-debian-720: ==> default: Setting hostname...
I, [2015-07-14T21:44:42.056221 #40537]  INFO -- replicaset-debian-720: ==> default: Machine not provisioned because `--no-provision` is specified.
I, [2015-07-14T21:44:44.021303 #40537]  INFO -- replicaset-debian-720: [SSH] Established
I, [2015-07-14T21:44:44.021822 #40537]  INFO -- replicaset-debian-720: Vagrant instance <replicaset-debian-720> created.
I, [2015-07-14T21:44:44.022788 #40537]  INFO -- replicaset-debian-720: Finished creating <replicaset-debian-720> (0m41.35s).
I, [2015-07-14T21:44:44.023094 #40537]  INFO -- replicaset-debian-720: -----> Converging <replicaset-debian-720>...
I, [2015-07-14T21:44:44.024320 #40537]  INFO -- replicaset-debian-720: Preparing files for transfer
I, [2015-07-14T21:44:44.024425 #40537]  INFO -- replicaset-debian-720: Preparing dna.json
I, [2015-07-14T21:44:44.024916 #40537]  INFO -- replicaset-debian-720: Resolving cookbook dependencies with Berkshelf 3.3.0...

I, [2015-07-14T21:44:50.411144 #40537]  INFO -- replicaset-debian-720: Download complete.
I, [2015-07-14T21:44:50.421674 #40537]  INFO -- replicaset-debian-720: Downloading Chef 11.12.8 for debian...
I, [2015-07-14T21:44:50.421739 #40537]  INFO -- replicaset-debian-720: downloading https://www.chef.io/chef/metadata?v=11.12.8&prerelease=false&nightlies=false&p=debian&pv=6&m=x86_64
I, [2015-07-14T21:44:50.421760 #40537]  INFO -- replicaset-debian-720:   to file /tmp/install.sh.2821/metadata.txt
I, [2015-07-14T21:44:50.421776 #40537]  INFO -- replicaset-debian-720: trying wget...

I, [2015-07-14T21:44:56.182750 #40537]  INFO -- replicaset-debian-720: downloading https://opscode-omnibus-packages.s3.amazonaws.com/debian/6/x86_64/chef_11.12.8-2_amd64.deb
I, [2015-07-14T21:44:56.182790 #40537]  INFO -- replicaset-debian-720:   to file /tmp/install.sh.2821/chef_11.12.8-2_amd64.deb
I, [2015-07-14T21:44:56.182809 #40537]  INFO -- replicaset-debian-720: trying wget...
I, [2015-07-14T21:45:10.414526 #40537]  INFO -- replicaset-debian-720: Comparing checksum with sha256sum...
I, [2015-07-14T21:45:10.574563 #40537]  INFO -- replicaset-debian-720: Installing Chef 11.12.8
I, [2015-07-14T21:45:10.574620 #40537]  INFO -- replicaset-debian-720: installing with dpkg...
I, [2015-07-14T21:45:10.636067 #40537]  INFO -- replicaset-debian-720: Selecting previously unselected package chef.
I, [2015-07-14T21:45:10.773204 #40537]  INFO -- replicaset-debian-720: (Reading database ...

I, [2015-07-14T21:45:10.774908 #40537]  INFO -- replicaset-debian-720: Unpacking chef (from .../chef_11.12.8-2_amd64.deb) ...
I, [2015-07-14T21:45:13.634449 #40537]  INFO -- replicaset-debian-720: Setting up chef (11.12.8-2) ...
I, [2015-07-14T21:45:13.652001 #40537]  INFO -- replicaset-debian-720: Thank you for installing Chef!
I, [2015-07-14T21:45:13.694041 #40537]  INFO -- replicaset-debian-720: Transferring files to <replicaset-debian-720>
I, [2015-07-14T21:45:14.939503 #40537]  INFO -- replicaset-debian-720: [2015-07-15T01:45:14+00:00] WARN:
I, [2015-07-14T21:45:14.939745 #40537]  INFO -- replicaset-debian-720: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I, [2015-07-14T21:45:14.939990 #40537]  INFO -- replicaset-debian-720: SSL validation of HTTPS requests is disabled. HTTPS connections are still
I, [2015-07-14T21:45:14.940367 #40537]  INFO -- replicaset-debian-720: encrypted, but chef is not able to detect forged replies or man in the middle
I, [2015-07-14T21:45:14.940567 #40537]  INFO -- replicaset-debian-720: attacks.
I, [2015-07-14T21:45:14.940769 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.940976 #40537]  INFO -- replicaset-debian-720: To fix this issue add an entry like this to your configuration file:
I, [2015-07-14T21:45:14.941072 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.941587 #40537]  INFO -- replicaset-debian-720: ```
I, [2015-07-14T21:45:14.941782 #40537]  INFO -- replicaset-debian-720:   # Verify all HTTPS connections (recommended)
I, [2015-07-14T21:45:14.942137 #40537]  INFO -- replicaset-debian-720:   ssl_verify_mode :verify_peer
I, [2015-07-14T21:45:14.942277 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.942504 #40537]  INFO -- replicaset-debian-720:   # OR, Verify only connections to chef-server
I, [2015-07-14T21:45:14.942836 #40537]  INFO -- replicaset-debian-720:   verify_api_cert true
I, [2015-07-14T21:45:14.943025 #40537]  INFO -- replicaset-debian-720: ```
I, [2015-07-14T21:45:14.943149 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.943478 #40537]  INFO -- replicaset-debian-720: To check your SSL configuration, or troubleshoot errors, you can use the
I, [2015-07-14T21:45:14.944323 #40537]  INFO -- replicaset-debian-720: `knife ssl check` command like so:
I, [2015-07-14T21:45:14.944356 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.944375 #40537]  INFO -- replicaset-debian-720: ```
I, [2015-07-14T21:45:14.944400 #40537]  INFO -- replicaset-debian-720:   knife ssl check -c /tmp/kitchen/client.rb
I, [2015-07-14T21:45:14.944418 #40537]  INFO -- replicaset-debian-720: ```
I, [2015-07-14T21:45:14.944432 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.944448 #40537]  INFO -- replicaset-debian-720: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I, [2015-07-14T21:45:14.944463 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:14.944641 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:45:22.342582 #40537]  INFO -- replicaset-debian-720: Creating a new client identity for replicaset-debian-720 using the validator key.

I, [2015-07-14T21:45:42.184063 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.184385 #40537]  INFO -- replicaset-debian-720:  +# Copyright (c) 2007 Javier Fernandez-Sanguino<EMAIL_ADDRESS>I, [2015-07-14T21:45:42.184572 #40537]  INFO -- replicaset-debian-720:  +# Copyright (c) 2011 edelight GmbH
I, [2015-07-14T21:45:42.184902 #40537]  INFO -- replicaset-debian-720:  +#       Author: Markus Korn<EMAIL_ADDRESS>I, [2015-07-14T21:45:42.185153 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.185414 #40537]  INFO -- replicaset-debian-720:  +# This is free software; you may redistribute it and/or modify
I, [2015-07-14T21:45:42.185677 #40537]  INFO -- replicaset-debian-720:  +# it under the terms of the GNU General Public License as
I, [2015-07-14T21:45:42.185876 #40537]  INFO -- replicaset-debian-720:  +# published by the Free Software Foundation; either version 2,
I, [2015-07-14T21:45:42.185907 #40537]  INFO -- replicaset-debian-720:  +# or (at your option) any later version.
I, [2015-07-14T21:45:42.185929 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.185950 #40537]  INFO -- replicaset-debian-720:  +# This is distributed in the hope that it will be useful, but
I, [2015-07-14T21:45:42.185970 #40537]  INFO -- replicaset-debian-720:  +# WITHOUT ANY WARRANTY; without even the implied warranty of
I, [2015-07-14T21:45:42.185991 #40537]  INFO -- replicaset-debian-720:  +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
I, [2015-07-14T21:45:42.186029 #40537]  INFO -- replicaset-debian-720:  +# GNU General Public License for more details.
 It's network accessible, written in C++ and offers
I, [2015-07-14T21:45:42.187037 #40537]  INFO -- replicaset-debian-720:  +#                    the following features:
I, [2015-07-14T21:45:42.187058 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.187079 #40537]  INFO -- replicaset-debian-720:  +#                       * Collection oriented storage - easy storage of object-
I, [2015-07-14T21:45:42.187101 #40537]  INFO -- replicaset-debian-720:  +#                         style data
I, [2015-07-14T21:45:42.187123 #40537]  INFO -- replicaset-debian-720:  +#                       * Full index support, including on inner objects
I, [2015-07-14T21:45:42.187144 #40537]  INFO -- replicaset-debian-720:  +#                       * Query profiling
I, [2015-07-14T21:45:42.187167 #40537]  INFO -- replicaset-debian-720:  +#                       * Replication and fail-over support
I, [2015-07-14T21:45:42.187189 #40537]  INFO -- replicaset-debian-720:  +#                       * Efficient storage of binary data including large
I, [2015-07-14T21:45:42.187210 #40537]  INFO -- replicaset-debian-720:  +#                         objects (e.g. videos)
I, [2015-07-14T21:45:42.187232 #40537]  INFO -- replicaset-debian-720:  +#                       * Auto-sharding for cloud-level scalability (Q209)
I, [2015-07-14T21:45:42.187254 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.187274 #40537]  INFO -- replicaset-debian-720:  +#                    High performance, scalability, and reasonable depth of
I, [2015-07-14T21:45:42.187296 #40537]  INFO -- replicaset-debian-720:  +#                    functionality are the goals for the project.
I, [2015-07-14T21:45:42.187318 #40537]  INFO -- replicaset-debian-720:  +### END INIT INFO
I, [2015-07-14T21:45:42.187338 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:45:42.187370 #40537]  INFO -- replicaset-debian-720:  +NAME=mongod
I, [2015-07-14T21:45:42.187393 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.187414 #40537]  INFO -- replicaset-debian-720:  +PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
I, [2015-07-14T21:45:42.187435 #40537]  INFO -- replicaset-debian-720:  +DESC=database
I, [2015-07-14T21:45:42.187453 #40537]  INFO -- replicaset-debian-720:  +PIDFILE=/var/run/$NAME.pid
I, [2015-07-14T21:45:42.187471 #40537]  INFO -- replicaset-debian-720:  +ENABLE_MONGODB=yes
I, [2015-07-14T21:45:42.187490 #40537]  INFO -- replicaset-debian-720:  +SYSCONFIG=/etc/default/mongodb
I, [2015-07-14T21:45:42.187509 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.187530 #40537]  INFO -- replicaset-debian-720:  +# this should get removed at some point for more shell agnostic init script
I, [2015-07-14T21:45:42.187552 #40537]  INFO -- replicaset-debian-720:  +ulimit -f unlimited
I, [2015-07-14T21:45:42.187573 #40537]  INFO -- replicaset-debian-720:  +ulimit -t unlimited
I, [2015-07-14T21:45:42.187592 #40537]  INFO -- replicaset-debian-720:  +ulimit -v unlimited
I, [2015-07-14T21:45:42.187612 #40537]  INFO -- replicaset-debian-720:  +ulimit -n 64000
I, [2015-07-14T21:45:42.187632 #40537]  INFO -- replicaset-debian-720:  +ulimit -m unlimited
I, [2015-07-14T21:45:42.187652 #40537]  INFO -- replicaset-debian-720:  +ulimit -u 32000
I, [2015-07-14T21:45:42.187672 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.187693 #40537]  INFO -- replicaset-debian-720:  +# Include mongodb defaults if available
I, [2015-07-14T21:45:42.187715 #40537]  INFO -- replicaset-debian-720:  +if [ -f $SYSCONFIG ] ; then
I, [2015-07-14T21:45:42.187735 #40537]  INFO -- replicaset-debian-720:  +    . $SYSCONFIG
I, [2015-07-14T21:45:42.187753 #40537]  INFO -- replicaset-debian-720:  +fi
I, [2015-07-14T21:45:42.187774 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.187793 #40537]  INFO -- replicaset-debian-720:  +# Handle NUMA access to CPUs (SERVER-3574)
I, [2015-07-14T21:45:42.187815 #40537]  INFO -- replicaset-debian-720:  +# This verifies the existence of numactl as well as testing that the command works
I, [2015-07-14T21:45:42.187835 #40537]  INFO -- replicaset-debian-720:  +NUMACTL_ARGS="--interleave=all"
I, [2015-07-14T21:45:42.187855 #40537]  INFO -- replicaset-debian-720:  +if which numactl >/dev/null 2>/dev/null && numactl $NUMACTL_ARGS ls / >/dev/null 2>/dev/null
I, [2015-07-14T21:45:42.187876 #40537]  INFO -- replicaset-debian-720:  +then
I, [2015-07-14T21:45:42.187896 #40537]  INFO -- replicaset-debian-720:  +    NUMACTL="`which numactl` -- $NUMACTL_ARGS"
I, [2015-07-14T21:45:42.187917 #40537]  INFO -- replicaset-debian-720:  +    DAEMON_OPTS="$DAEMON_OPTS"
I, [2015-07-14T21:45:42.187938 #40537]  INFO -- replicaset-debian-720:  +else
I, [2015-07-14T21:45:42.187957 #40537]  INFO -- replicaset-debian-720:  +    NUMACTL=""
I, [2015-07-14T21:45:42.187976 #40537]  INFO -- replicaset-debian-720:  +    DAEMON_OPTS="-- $DAEMON_OPTS"
I, [2015-07-14T21:45:42.187997 #40537]  INFO -- replicaset-debian-720:  +fi
I, [2015-07-14T21:45:42.188016 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.188036 #40537]  INFO -- replicaset-debian-720:  +if test ! -x $DAEMON; then
I, [2015-07-14T21:45:42.188057 #40537]  INFO -- replicaset-debian-720:  +    echo "Could not find $DAEMON"
I, [2015-07-14T21:45:42.188077 #40537]  INFO -- replicaset-debian-720:  +    exit 0
I, [2015-07-14T21:45:42.188097 #40537]  INFO -- replicaset-debian-720:  +fi
I, [2015-07-14T21:45:42.188115 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.188135 #40537]  INFO -- replicaset-debian-720:  +if test "x$ENABLE_MONGODB" != "xyes"; then
I, [2015-07-14T21:45:42.188155 #40537]  INFO -- replicaset-debian-720:  +    exit 0
I, [2015-07-14T21:45:42.188176 #40537]  INFO -- replicaset-debian-720:  +fi
I, [2015-07-14T21:45:42.188194 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.188221 #40537]  INFO -- replicaset-debian-720:  +. /lib/lsb/init-functions
I, [2015-07-14T21:45:42.188247 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.188266 #40537]  INFO -- replicaset-debian-720:  +STARTTIME=1
I, [2015-07-14T21:45:42.188285 #40537]  INFO -- replicaset-debian-720:  +DIETIME=10                  # Time to wait for the server to die, in seconds
I, [2015-07-14T21:45:42.188305 #40537]  INFO -- replicaset-debian-720:  +                            # If this value is set too low you might not
I, [2015-07-14T21:45:42.190139 #40537]  INFO -- replicaset-debian-720:  +                            # let some servers to die gracefully and
I, [2015-07-14T21:45:42.190205 #40537]  INFO -- replicaset-debian-720:  +                            # 'restart' will not work
I, [2015-07-14T21:45:42.190245 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190272 #40537]  INFO -- replicaset-debian-720:  +DAEMON_USER=${DAEMON_USER:-mongodb}
I, [2015-07-14T21:45:42.190293 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190360 #40537]  INFO -- replicaset-debian-720:  +# debugging
I, [2015-07-14T21:45:42.190386 #40537]  INFO -- replicaset-debian-720:  +echo "** Running $NAME ($DAEMON $DAEMON_OPTS)"
I, [2015-07-14T21:45:42.190406 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190426 #40537]  INFO -- replicaset-debian-720:  +set -e
I, [2015-07-14T21:45:42.190445 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190463 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190482 #40537]  INFO -- replicaset-debian-720:  +running_pid() {
I, [2015-07-14T21:45:42.190502 #40537]  INFO -- replicaset-debian-720:  +# Check if a given process pid's cmdline matches a given name
I, [2015-07-14T21:45:42.190522 #40537]  INFO -- replicaset-debian-720:  +    pid=$1
I, [2015-07-14T21:45:42.190540 #40537]  INFO -- replicaset-debian-720:  +    name=$2
I, [2015-07-14T21:45:42.190558 #40537]  INFO -- replicaset-debian-720:  +    [ -z "$pid" ] && return 1
I, [2015-07-14T21:45:42.190577 #40537]  INFO -- replicaset-debian-720:  +    [ ! -d /proc/$pid ] &&  return 1
I, [2015-07-14T21:45:42.190597 #40537]  INFO -- replicaset-debian-720:  +    cmd=`cat /proc/$pid/cmdline | tr "\000" "\n"|head -n 1 |cut -d : -f 1`
I, [2015-07-14T21:45:42.190617 #40537]  INFO -- replicaset-debian-720:  +    # Is this the expected server
I, [2015-07-14T21:45:42.190636 #40537]  INFO -- replicaset-debian-720:  +    [ "$cmd" != "$name" ] &&  return 1
I, [2015-07-14T21:45:42.190655 #40537]  INFO -- replicaset-debian-720:  +    return 0
I, [2015-07-14T21:45:42.190674 #40537]  INFO -- replicaset-debian-720:  +}
I, [2015-07-14T21:45:42.190692 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190709 #40537]  INFO -- replicaset-debian-720:  +running() {
I, [2015-07-14T21:45:42.190729 #40537]  INFO -- replicaset-debian-720:  +# Check if the process is running looking at /proc
I, [2015-07-14T21:45:42.190748 #40537]  INFO -- replicaset-debian-720:  +# (works for all users)
I, [2015-07-14T21:45:42.190767 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.190785 #40537]  INFO -- replicaset-debian-720:  +    # No pidfile, probably no daemon present
I, [2015-07-14T21:45:42.190805 #40537]  INFO -- replicaset-debian-720:  +    [ ! -f "$PIDFILE" ] && return 1
I, [2015-07-14T21:45:42.190823 #40537]  INFO -- replicaset-debian-720:  +    pid=`cat $PIDFILE`
I, [2015-07-14T21:45:42.190843 #40537]  INFO -- replicaset-debian-720:  +    running_pid $pid $DAEMON || return 1
I, [2015-07-14T21:45:42.190864 #40537]  INFO -- replicaset-debian-720:  +    for i in `seq 1 20`; do
I, [2015-07-14T21:45:42.190884 #40537]  INFO -- replicaset-debian-720:  +      nc -z <IP_ADDRESS> 27017 && return 0
I, [2015-07-14T21:45:42.190902 #40537]  INFO -- replicaset-debian-720:  +      echo -n "."
I, [2015-07-14T21:45:42.190921 #40537]  INFO -- replicaset-debian-720:  +      sleep 15
I, [2015-07-14T21:45:42.190939 #40537]  INFO -- replicaset-debian-720:  +    done
I, [2015-07-14T21:45:42.190957 #40537]  INFO -- replicaset-debian-720:  +    return 1
I, [2015-07-14T21:45:42.190993 #40537]  INFO -- replicaset-debian-720:  +}
I, [2015-07-14T21:45:42.191013 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.191033 #40537]  INFO -- replicaset-debian-720:  +start_server() {
I, [2015-07-14T21:45:42.191051 #40537]  INFO -- replicaset-debian-720:  +# Start the process using the wrapper
I, [2015-07-14T21:45:42.191070 #40537]  INFO -- replicaset-debian-720:  +            start-stop-daemon --background --start --quiet --pidfile $PIDFILE \
I, [2015-07-14T21:45:42.191091 #40537]  INFO -- replicaset-debian-720:  +                        --make-pidfile --chuid $DAEMON_USER \
I, [2015-07-14T21:45:42.191110 #40537]  INFO -- replicaset-debian-720:  +                        --exec $NUMACTL $DAEMON $DAEMON_OPTS
I, [2015-07-14T21:45:42.191130 #40537]  INFO -- replicaset-debian-720:  +            errcode=$?
I, [2015-07-14T21:45:42.191149 #40537]  INFO -- replicaset-debian-720:  +    return $errcode
I, [2015-07-14T21:45:42.191168 #40537]  INFO -- replicaset-debian-720:  +}
I, [2015-07-14T21:45:42.191186 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.191204 #40537]  INFO -- replicaset-debian-720:  +stop_server() {
I, [2015-07-14T21:45:42.191224 #40537]  INFO -- replicaset-debian-720:  +# Stop the process using the wrapper
I, [2015-07-14T21:45:42.191244 #40537]  INFO -- replicaset-debian-720:  +            start-stop-daemon --stop --quiet --pidfile $PIDFILE \
I, [2015-07-14T21:45:42.191264 #40537]  INFO -- replicaset-debian-720:  +                        --retry 300 \
I, [2015-07-14T21:45:42.191283 #40537]  INFO -- replicaset-debian-720:  +                        --user $DAEMON_USER \
I, [2015-07-14T21:45:42.191303 #40537]  INFO -- replicaset-debian-720:  +                        --exec $DAEMON
I, [2015-07-14T21:45:42.191321 #40537]  INFO -- replicaset-debian-720:  +            errcode=$?
I, [2015-07-14T21:45:42.191339 #40537]  INFO -- replicaset-debian-720:  +    return $errcode
I, [2015-07-14T21:45:42.191357 #40537]  INFO -- replicaset-debian-720:  +}
I, [2015-07-14T21:45:42.191374 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.191392 #40537]  INFO -- replicaset-debian-720:  +force_stop() {
I, [2015-07-14T21:45:42.191410 #40537]  INFO -- replicaset-debian-720:  +# Force the process to die killing it manually
I, [2015-07-14T21:45:42.191431 #40537]  INFO -- replicaset-debian-720:  +    [ ! -e "$PIDFILE" ] && return
I, [2015-07-14T21:45:42.191452 #40537]  INFO -- replicaset-debian-720:  +    if running ; then
I, [2015-07-14T21:45:42.191471 #40537]  INFO -- replicaset-debian-720:  +        kill -15 $pid
I, [2015-07-14T21:45:42.191489 #40537]  INFO -- replicaset-debian-720:  +    # Is it really dead?
I, [2015-07-14T21:45:42.191507 #40537]  INFO -- replicaset-debian-720:  +        sleep "$DIETIME"s
I, [2015-07-14T21:45:42.191525 #40537]  INFO -- replicaset-debian-720:  +        if running ; then
I, [2015-07-14T21:45:42.191543 #40537]  INFO -- replicaset-debian-720:  +            kill -9 $pid
I, [2015-07-14T21:45:42.191561 #40537]  INFO -- replicaset-debian-720:  +            sleep "$DIETIME"s
I, [2015-07-14T21:45:42.191580 #40537]  INFO -- replicaset-debian-720:  +            if running ; then
I, [2015-07-14T21:45:42.191599 #40537]  INFO -- replicaset-debian-720:  +                echo "Cannot kill $NAME (pid=$pid)!"
I, [2015-07-14T21:45:42.192712 #40537]  INFO -- replicaset-debian-720:  +                exit 1
I, [2015-07-14T21:45:42.192752 #40537]  INFO -- replicaset-debian-720:  +            fi
I, [2015-07-14T21:45:42.192774 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.192793 #40537]  INFO -- replicaset-debian-720:  +    fi
I, [2015-07-14T21:45:42.192812 #40537]  INFO -- replicaset-debian-720:  +    rm -f $PIDFILE
I, [2015-07-14T21:45:42.192831 #40537]  INFO -- replicaset-debian-720:  +}
I, [2015-07-14T21:45:42.192849 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.192866 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.192885 #40537]  INFO -- replicaset-debian-720:  +case "$1" in
I, [2015-07-14T21:45:42.192921 #40537]  INFO -- replicaset-debian-720:  +  start)
I, [2015-07-14T21:45:42.192942 #40537]  INFO -- replicaset-debian-720:  +    log_daemon_msg "Starting $DESC" "$NAME"
I, [2015-07-14T21:45:42.192961 #40537]  INFO -- replicaset-debian-720:  +        # Check if it's running first
I, [2015-07-14T21:45:42.192979 #40537]  INFO -- replicaset-debian-720:  +        if running ;  then
I, [2015-07-14T21:45:42.192998 #40537]  INFO -- replicaset-debian-720:  +            log_progress_msg "apparently already running"
I, [2015-07-14T21:45:42.193017 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg 0
I, [2015-07-14T21:45:42.193035 #40537]  INFO -- replicaset-debian-720:  +            exit 0
I, [2015-07-14T21:45:42.193054 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.193072 #40537]  INFO -- replicaset-debian-720:  +        if start_server ; then
I, [2015-07-14T21:45:42.193091 #40537]  INFO -- replicaset-debian-720:  +            # NOTE: Some servers might die some time after they start,
I, [2015-07-14T21:45:42.193112 #40537]  INFO -- replicaset-debian-720:  +            # this code will detect this issue if STARTTIME is set
I, [2015-07-14T21:45:42.193131 #40537]  INFO -- replicaset-debian-720:  +            # to a reasonable value
I, [2015-07-14T21:45:42.193150 #40537]  INFO -- replicaset-debian-720:  +            [ -n "$STARTTIME" ] && sleep $STARTTIME # Wait some time
I, [2015-07-14T21:45:42.193170 #40537]  INFO -- replicaset-debian-720:  +            if  running ;  then
I, [2015-07-14T21:45:42.193189 #40537]  INFO -- replicaset-debian-720:  +                # It's ok, the server started and is running
I, [2015-07-14T21:45:42.193208 #40537]  INFO -- replicaset-debian-720:  +                log_end_msg 0
I, [2015-07-14T21:45:42.193241 #40537]  INFO -- replicaset-debian-720:  +            else
I, [2015-07-14T21:45:42.193275 #40537]  INFO -- replicaset-debian-720:  +                # It is not running after we did start
I, [2015-07-14T21:45:42.193303 #40537]  INFO -- replicaset-debian-720:  +                log_end_msg 1
I, [2015-07-14T21:45:42.193322 #40537]  INFO -- replicaset-debian-720:  +            fi
I, [2015-07-14T21:45:42.193360 #40537]  INFO -- replicaset-debian-720:  +        else
I, [2015-07-14T21:45:42.193390 #40537]  INFO -- replicaset-debian-720:  +            # Either we could not start it
I, [2015-07-14T21:45:42.193409 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg 1
I, [2015-07-14T21:45:42.193427 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.193444 #40537]  INFO -- replicaset-debian-720:  +    ;;
I, [2015-07-14T21:45:42.193461 #40537]  INFO -- replicaset-debian-720:  +  stop)
I, [2015-07-14T21:45:42.193479 #40537]  INFO -- replicaset-debian-720:  +        log_daemon_msg "Stopping $DESC" "$NAME"
I, [2015-07-14T21:45:42.193497 #40537]  INFO -- replicaset-debian-720:  +        if running ; then
I, [2015-07-14T21:45:42.193516 #40537]  INFO -- replicaset-debian-720:  +            # Only stop the server if we see it running
I, [2015-07-14T21:45:42.193536 #40537]  INFO -- replicaset-debian-720:  +            errcode=0
I, [2015-07-14T21:45:42.193554 #40537]  INFO -- replicaset-debian-720:  +            stop_server || errcode=$?
I, [2015-07-14T21:45:42.193572 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg $errcode
I, [2015-07-14T21:45:42.193589 #40537]  INFO -- replicaset-debian-720:  +        else
I, [2015-07-14T21:45:42.193607 #40537]  INFO -- replicaset-debian-720:  +            # If it's not running don't do anything
I, [2015-07-14T21:45:42.193625 #40537]  INFO -- replicaset-debian-720:  +            log_progress_msg "apparently not running"
I, [2015-07-14T21:45:42.193644 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg 0
I, [2015-07-14T21:45:42.193661 #40537]  INFO -- replicaset-debian-720:  +            exit 0
I, [2015-07-14T21:45:42.193679 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.193705 #40537]  INFO -- replicaset-debian-720:  +        ;;
I, [2015-07-14T21:45:42.193725 #40537]  INFO -- replicaset-debian-720:  +  force-stop)
I, [2015-07-14T21:45:42.193745 #40537]  INFO -- replicaset-debian-720:  +        # First try to stop gracefully the program
I, [2015-07-14T21:45:42.193764 #40537]  INFO -- replicaset-debian-720:  +        $0 stop
I, [2015-07-14T21:45:42.193781 #40537]  INFO -- replicaset-debian-720:  +        if running; then
I, [2015-07-14T21:45:42.193800 #40537]  INFO -- replicaset-debian-720:  +            # If it's still running try to kill it more forcefully
I, [2015-07-14T21:45:42.193819 #40537]  INFO -- replicaset-debian-720:  +            log_daemon_msg "Stopping (force) $DESC" "$NAME"
I, [2015-07-14T21:45:42.193838 #40537]  INFO -- replicaset-debian-720:  +            errcode=0
I, [2015-07-14T21:45:42.193855 #40537]  INFO -- replicaset-debian-720:  +            force_stop || errcode=$?
I, [2015-07-14T21:45:42.194579 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg $errcode
I, [2015-07-14T21:45:42.194609 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.194630 #40537]  INFO -- replicaset-debian-720:  +    ;;
I, [2015-07-14T21:45:42.194649 #40537]  INFO -- replicaset-debian-720:  +  restart|force-reload)
I, [2015-07-14T21:45:42.194668 #40537]  INFO -- replicaset-debian-720:  +        log_daemon_msg "Restarting $DESC" "$NAME"
I, [2015-07-14T21:45:42.194686 #40537]  INFO -- replicaset-debian-720:  +        errcode=0
I, [2015-07-14T21:45:42.194704 #40537]  INFO -- replicaset-debian-720:  +        stop_server || errcode=$?
I, [2015-07-14T21:45:42.194723 #40537]  INFO -- replicaset-debian-720:  +        # Wait some sensible amount, some server need this
I, [2015-07-14T21:45:42.194742 #40537]  INFO -- replicaset-debian-720:  +        [ -n "$DIETIME" ] && sleep $DIETIME
I, [2015-07-14T21:45:42.194760 #40537]  INFO -- replicaset-debian-720:  +        start_server || errcode=$?
I, [2015-07-14T21:45:42.194779 #40537]  INFO -- replicaset-debian-720:  +        [ -n "$STARTTIME" ] && sleep $STARTTIME
I, [2015-07-14T21:45:42.194799 #40537]  INFO -- replicaset-debian-720:  +        running || errcode=$?
I, [2015-07-14T21:45:42.194836 #40537]  INFO -- replicaset-debian-720:  +        log_end_msg $errcode
I, [2015-07-14T21:45:42.194866 #40537]  INFO -- replicaset-debian-720:  +    ;;
I, [2015-07-14T21:45:42.194896 #40537]  INFO -- replicaset-debian-720:  +  status)
I, [2015-07-14T21:45:42.194924 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.194952 #40537]  INFO -- replicaset-debian-720:  +        log_daemon_msg "Checking status of $DESC" "$NAME"
I, [2015-07-14T21:45:42.194980 #40537]  INFO -- replicaset-debian-720:  +        if running ;  then
I, [2015-07-14T21:45:42.195009 #40537]  INFO -- replicaset-debian-720:  +            log_progress_msg "running"
I, [2015-07-14T21:45:42.195029 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg 0
I, [2015-07-14T21:45:42.195046 #40537]  INFO -- replicaset-debian-720:  +        else
I, [2015-07-14T21:45:42.195064 #40537]  INFO -- replicaset-debian-720:  +            log_progress_msg "apparently not running"
I, [2015-07-14T21:45:42.195083 #40537]  INFO -- replicaset-debian-720:  +            log_end_msg 1
I, [2015-07-14T21:45:42.195102 #40537]  INFO -- replicaset-debian-720:  +            exit 1
I, [2015-07-14T21:45:42.195120 #40537]  INFO -- replicaset-debian-720:  +        fi
I, [2015-07-14T21:45:42.195138 #40537]  INFO -- replicaset-debian-720:  +        ;;
I, [2015-07-14T21:45:42.195168 #40537]  INFO -- replicaset-debian-720:  +  # MongoDB can't reload its configuration.
I, [2015-07-14T21:45:42.195241 #40537]  INFO -- replicaset-debian-720:  +  reload)
I, [2015-07-14T21:45:42.195275 #40537]  INFO -- replicaset-debian-720:  +        log_warning_msg "Reloading $NAME daemon: not implemented, as the daemon"
I, [2015-07-14T21:45:42.195298 #40537]  INFO -- replicaset-debian-720:  +        log_warning_msg "cannot re-read the config file (use restart)."
I, [2015-07-14T21:45:42.195318 #40537]  INFO -- replicaset-debian-720:  +        ;;
I, [2015-07-14T21:45:42.195350 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.195370 #40537]  INFO -- replicaset-debian-720:  +  *)
I, [2015-07-14T21:45:42.195388 #40537]  INFO -- replicaset-debian-720:  +    N=/etc/init.d/$NAME
I, [2015-07-14T21:45:42.195409 #40537]  INFO -- replicaset-debian-720:  +    echo "Usage: $N {start|stop|force-stop|restart|force-reload|status}" >&2
I, [2015-07-14T21:45:42.195427 #40537]  INFO -- replicaset-debian-720:  +    exit 1
I, [2015-07-14T21:45:42.195444 #40537]  INFO -- replicaset-debian-720:  +    ;;
I, [2015-07-14T21:45:42.195461 #40537]  INFO -- replicaset-debian-720:  +esac
I, [2015-07-14T21:45:42.195478 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.195495 #40537]  INFO -- replicaset-debian-720:  +exit 0
I, [2015-07-14T21:45:42.195512 #40537]  INFO -- replicaset-debian-720:  +
I, [2015-07-14T21:45:42.196259 #40537]  INFO -- replicaset-debian-720:     - change mode from '' to '0755'
I, [2015-07-14T21:45:42.196453 #40537]  INFO -- replicaset-debian-720:     - change owner from '' to 'root'
I, [2015-07-14T21:45:42.196703 #40537]  INFO -- replicaset-debian-720:     - change group from '' to 'root'
I, [2015-07-14T21:46:17.365798 #40537]  INFO -- replicaset-debian-720:   * package[mongodb] action install
I, [2015-07-14T21:46:17.366152 #40537]  INFO -- replicaset-debian-720:     - install version 1:2.0.6-1.1 of package mongodb
I, [2015-07-14T21:46:17.366200 #40537]  INFO -- replicaset-debian-720: Recipe: mongodb::replicaset
I, [2015-07-14T21:46:27.946691 #40537]  INFO -- replicaset-debian-720:
I, [2015-07-14T21:46:27.946891 #40537]  INFO -- replicaset-debian-720:     - execute the ruby block chef_gem_at_converge_time
I, [2015-07-14T21:46:27.968810 #40537]  INFO -- replicaset-debian-720:   * template[/etc/default/mongodb] action create
I, [2015-07-14T21:46:27.969028 #40537]  INFO -- replicaset-debian-720:     - update content in file /etc/default/mongodb from a35762 to 91c827
I, [2015-07-14T21:46:27.969511 #40537]  INFO -- replicaset-debian-720:  --- /etc/default/mongodb    2015-07-15 01:45:41.277619696 +0000
I, [2015-07-14T21:46:27.970062 #40537]  INFO -- replicaset-debian-720:  +++ /tmp/chef-rendered-template20150715-2898-fo1eck 2015-07-15 01:46:27.156547516 +0000
I, [2015-07-14T21:46:27.970424 #40537]  INFO -- replicaset-debian-720:  @@ -1,2 +1,13 @@
I, [2015-07-14T21:46:27.970619 #40537]  INFO -- replicaset-debian-720:  -ENABLE_MONGODB=no
I, [2015-07-14T21:46:27.970921 #40537]  INFO -- replicaset-debian-720:  +#
I, [2015-07-14T21:46:27.971357 #40537]  INFO -- replicaset-debian-720:  +# Automatically Generated by Chef, do not edit directly!

I, [2015-07-14T21:46:57.848643 #40537]  INFO -- replicaset-debian-720: -----> Setting up <replicaset-debian-720>...
I, [2015-07-14T21:46:57.849436 #40537]  INFO -- replicaset-debian-720: Finished setting up <replicaset-debian-720> (0m0.00s).
I, [2015-07-14T21:46:57.849508 #40537]  INFO -- replicaset-debian-720: -----> Verifying <replicaset-debian-720>...
I, [2015-07-14T21:46:57.850392 #40537]  INFO -- replicaset-debian-720: Preparing files for transfer
I, [2015-07-14T21:46:57.978622 #40537]  INFO -- replicaset-debian-720: -----> Installing Busser (busser)
I, [2015-07-14T21:47:17.094147 #40537]  INFO -- replicaset-debian-720: Fetching: thor-0.19.0.gem
Fetching: thor-0.19.0.gem ( 15%)
Fetching: thor-0.19.0.gem ( 33%)
Fetching: thor-0.19.0.gem ( 37%)
Fetching: thor-0.19.0.gem ( 47%)
Fetching: thor-0.19.0.gem ( 64%)
Fetching: thor-0.19.0.gem ( 72%)
Fetching: thor-0.19.0.gem ( 74%)
Fetching: thor-0.19.0.gem ( 75%)
Fetching: thor-0.19.0.gem ( 81%)
Fetching: thor-0.19.0.gem ( 86%)
Fetching: thor-0.19.0.gem ( 95%)
Fetching: thor-0.19.0.gem (100%)
Fetching: thor-0.19.0.gem (100%)
I, [2015-07-14T21:47:17.353713 #40537]  INFO -- replicaset-debian-720: Fetching: busser-0.7.1.gem
Fetching: busser-0.7.1.gem (  3%)
Fetching: busser-0.7.1.gem ( 70%)
Fetching: busser-0.7.1.gem (100%)
Fetching: busser-0.7.1.gem (100%)
I, [2015-07-14T21:47:17.366612 #40537]  INFO -- replicaset-debian-720: Successfully installed thor-0.19.0
I, [2015-07-14T21:47:17.366913 #40537]  INFO -- replicaset-debian-720: Successfully installed busser-0.7.1
I, [2015-07-14T21:47:17.367147 #40537]  INFO -- replicaset-debian-720: 2 gems installed
I, [2015-07-14T21:47:17.570071 #40537]  INFO -- replicaset-debian-720: -----> Setting up Busser
I, [2015-07-14T21:47:17.570425 #40537]  INFO -- replicaset-debian-720: Creating BUSSER_ROOT in /tmp/verifier
I, [2015-07-14T21:47:17.570864 #40537]  INFO -- replicaset-debian-720: Creating busser binstub
I, [2015-07-14T21:47:17.581797 #40537]  INFO -- replicaset-debian-720: Installing Busser plugins: busser-bats
I, [2015-07-14T21:47:25.910047 #40537]  INFO -- replicaset-debian-720: Plugin bats installed (version 0.3.0)
I, [2015-07-14T21:47:25.912813 #40537]  INFO -- replicaset-debian-720: -----> Running postinstall for bats plugin
I, [2015-07-14T21:47:25.944616 #40537]  INFO -- replicaset-debian-720: Installed Bats to /tmp/verifier/vendor/bats/bin/bats
I, [2015-07-14T21:47:26.123362 #40537]  INFO -- replicaset-debian-720: Suite path directory /tmp/verifier/suites does not exist, skipping.
 Command [/tmp/verifier/vendor/bats/bin/bats /tmp/verifier/suites/bats] exit code was 1
E, [2015-07-14T21:47:26.432608 #40537] ERROR -- replicaset-debian-720: Verify failed on instance <replicaset-debian-720>.
 Command [/tmp/verifier/vendor/bats/bin/bats /tmp/verifier/suites/bats] exit code was 1
E, [2015-07-14T21:47:26.432608 #40537] ERROR -- replicaset-debian-720: Verify failed on instance <replicaset-debian-720>.

Completed as part of the v1 rewrite


about slide-box-disabled

Hi @mattlewis92, and congrats for this amazing work! I'm trying to set the slide box on my calendar but i can't make it working. Also i tried your demo example 'Slidebox is open' and modified the directive of your demo in plunker but finally i cannot make it working...
This is my pretty easy directive:
<mwl-calendar ng-swipe-left="hola"
    events="vm.events"
    view="vm.calendarView"
    view-title="vm.calendarTitle"
    view-date="vm.viewDate"
    on-event-click="vm.eventClicked(calendarEvent)"
    on-event-times-changed="vm.eventTimesChanged(calendarEvent); calendarEvent.startsAt = calendarNewEventStart; calendarEvent.endsAt = calendarNewEventEnd"
    cell-is-open="vm.isCellOpen"
    day-view-start="06:00"
    day-view-end="22:00"
    day-view-split="6"
    slide-box-disabled=false
    cell-modifier="vm.modifyCell(calendarCell)">
  </mwl-calendar>

Am i missing something?
Thank you for your time. Cheers

You're missing the quotes around the attribute value slide-box-disabled=false should be slide-box-disabled="false"

Oh my! ... thats true. And also i thought that the slide box was a slider to change month and years during touch events. Sorry for that.


fix type for collection->whereNotNull

[x] Added or updated tests
[x] Documented user facing changes
[x] Updated CHANGELOG.md

Resolves #1176
Changes
Fixes the type for collection method whereNotNull

Thank you Christian for your work!

Thank you for the fixes!

@canvural updated the pr, 2 failing, but does not seem to be related to thi

@crissi What happened?

@crissi What happened?

Git and I are not always friend:-)

I wanted to support something like this as well, but do not know how....
`
/**@param \Illuminate\Database\Eloquent\Collection<int, \App\User> $foo */
function test(EloquentCollection $foo): void
{
assertType("string", $foo->whereNotNull('has_been_authorized_at')->first()->has_been_authorized_at);
}`

Thank you! Feel free to improve it in further PRs. For example from my testing collect([new User, 1, 'foo'])->whereNotNull('id') results in Collection<int, User>. It somehow removes all non-objects.

Thank you! Feel free to improve it in further PRs. For example from my testing collect([new User, 1, 'foo'])->whereNotNull('id') results in Collection<int, User>. It somehow removes all non-objects.

will take a look


Spelling Mistake on the landing page

There is a spelling mistake on the landing page. Can I rectify it?

@devilkiller-ag 👋
I didn't notice that, 🤣
You are welcome to open a PR about it.


Improve Accessibility of Inputs (Date/Category/Location)

Is your feature request related to a problem?
No, just an enhancement.
The Events Module remarkably passes almost every Accessibility test except the Input controls at the top of the module.  When I test using the  WebAIM Chrome Extension (WAVE) I get errors on all three  (Date/Category/Location) controls.
The errors relate to missing Form Labels, Empty Buttons, and Empty Table Headers.
Describe the solution you'd like
I would like for the controls to be tweaked so they pass WAVE.
Describe alternatives you've considered
Additional context

I will give this some attention for the next release.
BTW a screen shot with some marking would be helpful.

Just a gentle nudge to keep this Issue alive.

Another bump to keep this Issue alive.

Another bump.
Did this even get resolved?

Unfortunately no contribution came in for this issue. If anyone intends to submit a code contribution or sponsor some development for it, feel free to comment and I will be glad to reopen. Stalebot closed it due to inactivity

I'm the original poster and I'd be happy to sponsor the change if it's not too expensive.

Ok, let's start with pinging @EPTamminga as I believe he is the one that knows the most about this module codebase...
@djamell  If you don't hear back in a few days, please comment again and we can see who else can jump in (maybe myself if it's not too rush)...

OK, will do.  No real rush.  Thank you Daniel!

I have been maintaining this module since 2007, with various people contributing code.
It started when needed this module back in those days and there were some errors I fixed.
I do not use this module with any projects we have done in the last 5 yrs or so, As a result, the urgency to enhance or fix things have gone down.. Sorry.
I am not looking for money, If you want to donate anything, please consider becoming a member of the DNNCommunity team on KIVA, https://www.kiva.org/team/dnn_community (if you are not yet) and start with micro financing to people who really need it.
I can do some work, but I can use some detailed instructions on what has to be done.

HI EP.  Thanks for your willingness to do this.  In part, you can refer to the early posts in made in this thread.
Specifically, the three input controls (Date/Category/Location) do not have labels so screen readers can't tell what the comtrol does.  The error is described by the WAVE as the following:
What It Means
A form control does not have a corresponding label.
Why It Matters
If a form control does not have a properly associated text label, the function or purpose of that form control may not be presented to screen reader users. Form labels also provide visible descriptions and larger clickable targets for form controls.
How to Fix It
If a text label for a form control is visible, use the  element to associate it with its respective form control. If there is no visible label, either provide an associated label, add a descriptive title attribute to the form control, or reference the label(s) using aria-labelledby. Labels are not required for image, submit, reset, button, or hidden form controls.
The Algorithm... in English
An  (except types of image, submit, reset, button, or hidden), , or  does not have a properly associated label. A properly associated label is:
a  element with a for attribute value that is equal to the id of a unique form control
a  element that surrounds the form control, does not surround any other form controls, and does not reference another element with its for attribute
a non-empty title attribute, or
a non-empty aria-labelledby attribute.

AFAIK, there are (localizable) labels connected to the controls in the standard DNN way.
I will try to have a look next week.

@djamell I have been analyzing it, I thought I found the solution, by specifying the ID of the in[ut control in the label control. That does did not seem to work correctly.

The date input is a Telerik RAD editor and the input textbox gets a generated name
The combo boxes for location and category are DNNCombobox controls. I linked the control ID to the label (this ID link was missing in the label control), but that did not seem to work correctly.

I had a look at other parts of DNN, eg. the standard settings pages (tabbed page) and also there, some of the controls get a marker from WAVE, others do not. It remains unclear to me why one is OK and the other not.

The "good news" is that the Telerik RAD date control has to be replaced by a none Telerik control I assume that that will solve the case for the date field.
For the DNNCombo controls: I am not sure about how to solve that yet.

The WAVE reference seems to indicate that simply adding "a non-empty title attribute, or
a non-empty aria-labelledby attribute" would work.


Using LIMIT with or without pipe returns the same result

nGQL 1: MATCH (v:player{name:"Tim Duncan"}) --> (v2) RETURN v2 | LIMIT 3
nGQL 2: MATCH (v:player{name:"Tim Duncan"}) --> (v2) RETURN v2 LIMIT 3

Is it coded to be like this?

These two statement are both legal in nGQL. The first one was derived from nebula1.0 and the second one is an openCypher syntax.


Does this support wayland?

If it doesn't, please add that to the README.

It does

If it doesn't, please add that to the README.

It does

Oh ok!


a few more UPat.var -> UPat.cvar in the scheduler [pr]

simplify_reduceop stays even after symbolic+ops_folding since it's folding shape changing ops.
const_arg is simple, self is either GroupOp.Movement(CONST) or CONST(). No more VIEW with len(src) == 2 having a different meaning.

This mixtral regression was weird

i think it's because base isn't cached.

it was .base, we're back.

It can't be cached because of uop mutablity, we need to be very careful with accessing base before the delete_movementops pass.


Detection of Jupyter kernels fails for Python (Microsoft Store version)

Bug: Notebook Editor, Interactive Window, Editor cells
Steps to cause the bug to occur

Install Python 3.8 from the Microsoft Store
Run pip install jupyter
Try to run python code through vscode-python

Actual behavior
vscode-python fails to recognize existing kernels.
The point where things start to fall apart is jupyterKernelSpec.ts#parseKernelSpecs, where the response of jupyter kernelspec list gets parsed. Since Python is running sandboxed (UWP), the kernel specs are NOT located in %APPDATA%\... (as reported by jupyter kernelspec list), but in the redirected location %LOCALAPPDATA%\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\...
The call to fs.fileExists therefore returns false, resulting in a few messages like Kernel not created with the name python38264bitbb49e9738bee4bad94750749010b815e, display_name Python 3.8.2 64-bit. Output is Installed kernelspec python38264bitbb49e9738bee4bad94750749010b815e in C:\Users\stroy\AppData\Roaming\jupyter\kernels\python38264bitbb49e9738bee4bad94750749010b815e
Expected behavior

Jupyter selects the existing python kernel and runs the code

Workaround

Add an environment variable called JUPYTER_DATA_DIR, which points to the redirected AppData folder (à la C:\Users\<User>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\Roaming\jupyter).

Your Jupyter and/or Python environment

Jupyter server running: Local
Extension version: 2020.5.0-dev
VS Code version: 1.44.2
Setting python.jediEnabled: true
Python and/or Anaconda version: 3.8.2 (Microsoft Store version)
OS: Windows 10 1909
Virtual environment: N/A

Developer Tools Console Output
console.log
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

I found a better way:
Add environment variable
JUPYTER_DATA_DIR=C:\Users\[username]\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_[random]\LocalCache\Roaming\jupyter
and work like a charm.

hmm the only folder that I have in the Roaming folder is the Microsoft folder


GET services from a stage endpoint requires stage but contains service in path

Bug: Mismatch between path parameter (service) and actual parameter (stage).

Fix:

The path for the endpoint must be: /project/{project}/stage/{stage}

This seems to be a copy-paste error. I've fixed it (locally) and it seems there are two endpoints now:


[bug]: Updating from version 0.13.3-beta to 0.15.3-beta broke LND

Background
Because of the taproot issue and other advancements I wanted to update my LND version.
After reading it, I used the update script linked on lightningnode.info here
Your environment

version of lnd
(0.13.3-beta => 0.15.3-beta)

which operating system (uname -a on *Nix)
Linux raspi 5.10.52-v7l+ # 1441 SMP Tue Aug 3 18:11:56 BST 2021 armv7l GNU/Linux

version of btcd, bitcoind, or other backend

~ bitcoind --version
Bitcoin Core version v0.21.1
...

any other relevant environment details

Steps to reproduce
Update from version 0.13.3-beta to version 0.15.3-beta on the 2022/10/18 (YYYY/MM/dd)
with 2 open channels but offline due to the error
[ERR] LNWL: Unable to complete chain rescan: readScript: script witness item is larger than the max allowed size [count 33970, max 11000]

Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
Expected behaviour
Normal command execution
Actual behaviour
The following error in the output:
~ lncli listpeers
[lncli] rpc error: code = Unknown desc = wallet locked, unlock it to enable full RPC access

~ lncli unlock
Input wallet password:

lnd successfully unlocked!
~ lncli listpeers
[lncli] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:10009: connect: connection refused"

I can repeat this error for approximately 10s
~ lncli listpeers
[lncli] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:10009: connect: connection refused"

But then it switches back to the first error
~ lncli listpeers
[lncli] rpc error: code = Unknown desc = wallet locked, unlock it to enable full RPC access

Should I restore my SCB?
I look forward to hearing your suggestions. I'm a beginner but could not find anything on this topic. Restarting the node has not solved my issue.
Logs:
2022-10-18 01:48:05.048 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:12.660 [INF] LNWL: Opened wallet
2022-10-18 01:48:13.102 [INF] CHRE: Primary chain is set to: bitcoin
2022-10-18 01:44:57.546 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:44:57.547 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:44:57.546 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:46:00.036 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:46:00.036 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:46:00.037 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:46:00.037 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:47:02.503 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:47:02.503 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:47:02.504 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:47:02.504 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:05.048 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:05.048 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:05.048 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:05.048 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:48:12.660 [INF] LNWL: Opened wallet
2022-10-18 01:48:13.102 [INF] CHRE: Primary chain is set to: bitcoin
2022-10-18 01:48:13.125 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2022-10-18 01:48:13.125 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on <IP_ADDRESS>:28332
2022-10-18 01:48:13.125 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on <IP_ADDRESS>:28333
2022-10-18 01:48:13.134 [ERR] LTND: unable to create partial chain control: parse "<IP_ADDRESS>:28332": first path segment in URL cannot contain colon
2022-10-18 01:48:13.134 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: parse "<IP_ADDRESS>:28332": first path segment in URL cannot contain colon
2022-10-18 01:48:13.164 [INF] LTND: Shutdown complete

2022-10-18 01:48:43.400 [INF] LTND: Version: 0.15.3-beta commit=v0.15.3-beta, build=production, logging=default, debuglevel=info
2022-10-18 01:48:43.400 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2022-10-18 01:48:43.404 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2022-10-18 01:48:43.409 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2022-10-18 01:48:43.409 [INF] LTND: Opening the main database, this might take a few minutes...
2022-10-18 01:48:43.409 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
2022-10-18 01:48:45.799 [INF] LTND: Creating local graph and channel state DB instances
2022-10-18 01:48:49.631 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
2022-10-18 01:48:49.631 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
2022-10-18 01:48:49.631 [INF] LTND: Database(s) now open (time_to_open=6.22211498s)!
2022-10-18 01:48:49.631 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-10-18 01:48:49.631 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
2022-10-18 01:49:07.490 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:49:07.495 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:49:07.495 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-10-18 01:49:07.495 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access

Looks like the issue is your config?
 01:48:13.134 [ERR] LTND: unable to create partial chain control: parse "<IP_ADDRESS>:28332": first path segment in URL cannot contain colon
2022-10-18 01:48:13.134 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: parse "<IP_ADDRESS>:28332": first path segment in URL cannot contain colon
2022-10-18 01:48:13.164 [INF] LTND: Shutdown complete

Thanks for your fast reply!
I've written the following in the lnd.conf:
bitcoind.zmqpubrawblock=<IP_ADDRESS>:28332
sudo lsof -i -P -n | grep LISTEN
shows me that there is a bitcoind listening on port 28332.
So what is wrong there? Is the attribute deprecated or something like that?

Try using this instead: bitcoind.zmqpubrawblock=tcp://<IP_ADDRESS>:28332

Thank you very much!
I needed to update the format on the bitcoind.zmqpubrawtx attribute to tcp://<IP_ADDRESS>:28333 too and made a restart in between so it doesn't throw errors anymore. Thanks again!


[Snyk] Upgrade sequelize from 6.25.1 to 6.25.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade sequelize from 6.25.1 to 6.25.3.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released a month ago, on 2022-10-19.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

already upgraded from another PR


pelion client failed at initialization (error code = 16)

Tested on WISE-1530 with external SD card reader and got the following error messages:

Initializing Pelion Device Management Client...
Pelion Client initialization failed (16)

It looks like it's caused by the latest change to mbed-os.
Need to replace specific filesystem declaration with get_default_instance() API call instead.
FileSystem *fs = FileSystem::get_default_instance();
Once I replaced the fs declaration with the above, PDMC starts to work again

@chuanga Is this still relevant?

Closing - please reopen if continues to be a problem.


Problems when publishing

Dec 01 14:58:15.239 ERRO Error: Cargo error
caused by: Source directory was modified by build.rs during cargo publish. Build scripts should not modify anything outside of OUT_DIR. Modified file: /home/lenij/zondax/ledger-rs/target/package/ledger-transport-zemu-0.7.0/src/zemu.rs
To proceed despite this, pass the --no-verify flag.

Great work @neithanmo !


Implement Database Migration

Follow this guide to enable the database to be automatically migrated
Database migrations will act as a form of version control so if the database becomes invalidated or malformed, it can be rolled back

Closing this ticket since it's not required at the moment or near the future.


Search

The versions that are for dogs not need the gray frame when active. The rest of the page get slightly darker, and that should be enough

Accessibility level: dogs

TO-DO: Remove outline on both


Manga online

Source name
Manga online
Source link
https://mangaonline.blog/
Source language
Português (Brasil)
Other details
No
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Cool!


github-copilot-cli: drop

It was maliciously marked as free: https://github.com/NixOS/nixpkgs/pull/228854
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Not sure about maliciously

It says license = licenses.free. The only reason to do so is if you want to hide that it's unfree. Otherwise not setting meta.license would have the same effect.

Maybe we just mark as unfree instead?

I'm not willing to help fix this package that added 3k lines to nixpkgs while removing it from nodePackages

That's quite the accusation.

It's not necessarily supposed to be taken 100% seriously. But please go ahead and fix this.

I doubt if the package should be deleted, given that it has active users and even a fish plugin in nixpkgs.
Opened #254363 to mark the package as unfree.

I merged #254363 before I saw this PR. I am also in favor of flushing this turd.

This was an oversight on my part. Sorry about that. The package on NPM doesn't contain a license, and not knowing much about how licenses work, I didn't know what to select for the license, so I picked licenses.free, and hoped that other folks would point out if that was wrong. Might be a good idea for the nixpkgs manual to explicitly say in the lib.licenses.unfree that if a package does not have a license explicitly specified, the the package should be marked as unfree.


Recycled Connection uses old idleTimeout stages.

I'm using a BlazeClient http4s v0.20.15 on blaze v0.14.11 and setting a very high idleTimeout but randomly, I still get timeouts after 60 seconds.
java.util.concurrent.TimeoutException: Idle timeout after 60000 ms.
        at org.http4s.blazecore.IdleTimeoutStage$$anon$1.run(IdleTimeoutStage.scala:27)
        at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402)
        at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
        at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
        at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
        at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)

I'm building the client like so:
    for {
        ec2 <- ExecutionContexts.fixedThreadPool[IO](32)
        timeout = 30.minutes
        lemurClient <- BlazeClientBuilder[IO](ec2)
          .withIdleTimeout(timeout)
          .withResponseHeaderTimeout(Duration.Inf)
          .withRequestTimeout(timeout)
          .resource
...

It appears here https://github.com/http4s/http4s/blob/3baf5d6baff7536937b3976595141e686ec31bb1/blaze-client/src/main/scala/org/http4s/client/blaze/BlazeClient.scala#L75
the IdleTimeoutStage is spliced into the connection.
However, here https://github.com/http4s/http4s/blob/63f3dbaf1f5c3887ae6b9baf0d167bb55974d413/client/src/main/scala/org/http4s/client/PoolManager.scala#L161 the connection is recycled without any clearing of the connections stages.
This leads to recycled connections to use idleTimeout from a previous request which may have been used for a different client with a different idleTimeout.

I'm not feeling my sharpest right now, but aren't we removing the stage here before we recycle?

@rossabaker I believe you are correct.
The original issue had nothing to do with the the http4s client (library versioning issue).
Closing this issue.


Permit specification of 1.8 compiler options on properties page for Visual Studio projects

I would like to specify some of these options via the settings for a Visual Studio project.
--noImplicitReturns.
--noFallthroughCasesInSwitch
--allowJs

Currently, this is not possible:

I am aware that VS now supports .tsconfig. Is that going to be the only way forward?

have you considered using a tsconfig.json?

@mhegazy, as I said at the end of the post I was thinking along the same lines. But I'm not sure how tsconfig.json is going to play with NTVS projects. Are you pushing tsconfig.json as the comprehensive solution going forward?

tsconfig.json should work with all project types... if you run into issue I would love to hear about them.
NTVS projects was one of the reasons for broader tsconfig.json support, that way you can contain both the client- and server-side javascript in the same project, but use different settings for both.

tsconfig.json is where we would like the configuration to live moving forward. it is easier to edit and understand for most JS developers, and cheaper to change for us (vs. the property pages UI); also works well with other tools in the build chain.

@paulvanbrenk,@mhegazy, that's good to hear. We have some dependencies on the old _references.ts that we need to rewrite, before switching to tsconfig. I'll let you know how things go.
I'm also glad that NTVS is being taken into account on par with TypeScript development. Their project seems to be slowly lapsing into oblivion and as TypeScript moves forward, it's a bit worrying. There is no good alternative in Visual Studio for developing, testing and debugging NodeJS projects. If you are privy to any information on this, I think a lot of people would be interested.

No "lapsing into oblivion", I would assure you. and we do care about our NodeJS developers. it is just hard to keep updating the UI for the property pages for every option added to the compiler, and tsconfig should solve that moving forward.

I was referring to the lack of commits in the NTVS github project - not to the commitment on the TypeScript side (which of course is exceptional). There are a few key issues that have not been resolved on the NTVS side (such as this one Microsoft/nodejstools#223, which has been open since June last year).

that is what i meant :). @mousetraps can add more.

Hey @NoelAbrahams. @mhegazy is correct - in fact, we are actually in the midst of growing the team! The fact is, however, that we do have a very small core team, can only do so many things at any given time, and unfortunately much of the work that we have been doing lately is not externally visible. That said, your post prompted me to consider potential opportunities to improve communication going forward, so I really appreciate your feedback and would love for you to be involved in this discussion :smiley:. https://github.com/Microsoft/nodejstools/issues/677

The problem for me is that the presence of tsconfig.json seems to shut off VS2015's "Compile On Save" option, despite the fact that it is not really a compiler-level option.  So it's seemingly impossible to get "Compile On Save" and "AllowJs" at the same time without manually firing up an external "tsc --watch".

Compile on Save while you have a tsconfig.json is disabled by default, to enable it go to tools\options\Text Editor\TypeScript\Project and check "Automatically compile typescript files which are not part of a project". note that there is no way in TS 1.8 beta to disable/enable it for a single tsconfig.json file. With https://github.com/Microsoft/TypeScript/issues/2326, which should be in the next TS 1.8 release should have a property ("compileOnSave") to enable/disable Compile on Save in tsconfig.json.

Thanks for the tip. That will work even if the files are part of the csproj?
On Feb 3, 2016 4:39 PM, "Mohamed Hegazy"<EMAIL_ADDRESS>wrote:

Compile on Save while you have a tsconfig.json is disabled by default, to
enable it go to tools\options\Text Editor\TypeScript\Project and check
"Automatically compile typescript files which are not part of a project".
note that there is no way in TS 1.8 beta to disable/enable it for a single
tsconfig.json file. With #2326
https://github.com/Microsoft/TypeScript/issues/2326, which should be in
the next TS 1.8 release should have a property ("compileOnSave") to
enable/disable Compile on Save in tsconfig.json.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/6767#issuecomment-179483696
.

Starting with 1.8.2, setting "compileOnSave" in your tsconfig should enable/disable the feature for this tsconfig.json file.

see https://github.com/Microsoft/TypeScript/wiki/tsconfig.json#compileonsave

@mhegazy, the original problem was not to do with compile-on-save; it was to permit all compiler options to be set via the setting page. As it stands it doesn't make much sense.
Why not just have a free text box so that users can set what they like?

@NoelAbrahams not sure what you mean with a free text box? But I am working on an easier to maintain properties page, so adding changes will be easier in the future.

Just a text box to enter any compiler option that one may want, e.g.

This just gets passed to the compiler.
I'm not sure if this is great UX, but at least it'll get the job done.

json files provide a similar experience, and most js devleopers are already familiar with its syntax. so my recommendation still stands.

Well, yes, we'll probably migrate to using the json config at some point ourselves. My point had more do to with leaving behind a half complete settings page.


Docs: horizontal swiping

We should have an example demoing how to implement horizontal swipe.

Agree, would be lovely! =)

looking forward to it!!

Guys, any news about horizontal swipe?
When i try to render an horizontal Calendar.List it disappears from the screen.

Is it possible to implement horizontal swiping with this library?

Finally, after some inspiration from your WindowsXP calendar, i figured out how to build a performant horizontal calendar!

@kostas64 can you share with us?

Hi, is there any progress on this? Just modifying FlashList to be horizontal does not help.

@AndreyBernardoni Sorry mate, never saw your comment.
I dont know if this is the best way to implement the horizontal, it works for me. I tried to extract as much logic as i could from the library it self in order to understand how it works behinds the scenes. In this way you can construct many types of calendars. I have replicated the same logic to build a strip calendar.
First, you have to calculate the calendarMonthId's for the months you want to render the calendar
  import { toDateId } from "@marceloterreiro/flash-calendar";

  const monthsList = useMemo(() => {
    const temp = [];
    for (let i = 0; i <= monthsToRender; i++) {
      const calendarMonthId = toDateId(addMonths(minDate || new Date(), i));
      temp.push(calendarMonthId);
    }
    return temp;
  }, [monthsToRender, minDate]);

Then you have to calculate the data for the calendar
 import { buildCalendar } from "@marceloterreiro/flash-calendar";

 const calendarData = useMemo(
    () =>
      monthsList.map((calendarMonthId) => {
        const { calendarRowMonth, weekDaysList, weeksList } = buildCalendar({
          calendarMonthId,
          calendarFirstDayOfWeek: "monday",
        });

        return {
          calendarRowMonth,
          weekDaysList,
          weeksList,
        };
      }),
    [monthsList],
  );

Render the calendarData to a FlatList or a Flashlist, whatever fits your needs better. In my case FlatList works
     import { CalendarDayMetadata } from "@marceloterreiro/flash-calendar";

     type TCalendarItem = {
        calendarRowMonth: string;
        weekDaysList: string[];
        weeksList: CalendarDayMetadata[][];
      };

     const renderItem = ({item}: {item: TCalendarItem}) => {
           return <CalendarMonthItem item={item} otherProps />
     }

     return <FlatList
        horizontal
        pagingEnabled
        bounces={false}
        windowSize={3}
        data={calendarData}
        renderItem={renderItem}
        getItemLayout={getItemLayout}
        showsHorizontalScrollIndicator={false}
        {...otherProps}
      />

Last but not least, we have to render the items.
   <View style={{width: WIDTH}}>
        {item.weeksList.map(week, i) => {
              <Calendar.Row.Week
                  theme={{
                      //play around
                  }}>
                 {week.map((day, nestedI) => {
                  <Calendar.Item.Day.Container
                    //manyProps to play here
                  >
                      {Your Day Tile component}
                 </Calendar.Item.Day.Container>
                 }}
              </Calendar.Row.Week>
        }}
   </View>

I hope this helps! Apologies for the lengthy response—I wanted to provide enough detail for clarity and avoid leaving anything unclear.


sklearnserver: ignore converting instances into np.array

Issue #1912

@Suresh-Nakkeran Can you help test with the mixed type example with your change?

/retest

Thanks @Suresh-Nakkeran !
/lgtm
/approve


Typo fix in centrifugo/README.md

line 43: tables lists->table lists
There are many such errors in stable directory.

/assign @sameersbn

/ok-to-test
/lgtm

/lgtm


Removed management of /etc/mesos/zk

Using this module without module-based hiera is problematic for the /etc/mesos/zk file now, as it is removed if it exists. Because this module adds ZK="<zk URL(s)" to /etc/default/mesos-master and MASTER="<zk URL(s)" to /etc/default/mesos-slave - which is what Mesos ends up using. /etc/mesos/zk, on the other hand, is hardcoded in the Marathon framework to be used. I have created a module to configure Marathon, and I am having it manage /etc/mesos/zk.
Would you be agreeable to removing management of /etc/mesos/zk as done in my PR?
Thanks,
Paul

I spent a fair amount of time trying to understand why Travis-CI tests were failing for me while they had passed for you a month ago. Performing a diff of the Travis build logs, I discovered that Puppet 4.0 was installing for me, while Puppet 3.7.5 had been installing for you. This led me to find that the PUPPET_VERSION listed in travis.yml was not being honored, because it was not used in the Gemfile. I have fixed that.

Yeah, the travis.yml definitely needs some updates.
I'm afraid I can't accept the PR as it is. It would be breaking change, at least for some users.  I agree it is redundant to define ZooKeeper in /etc/default/mesos-master, /etc/default/mesos-slave and /etc/mesos/zk. We ended up doing it so, as sort of rapid code evolution.
Mesosphere deb package defines ZK variable in /etc/default/mesos-master as:
ZK=`cat /etc/mesos/zk`

It would make more sense to define ZooKeeper url just in one place, instead of 3 places as it is now.
Instead of complete removal of /etc/mesos/zk management, could you added parameter manage_zk_file or something like this, so that this feature could be disabled?

Totally understandable about not implicitly removing management of /etc/mesos/zk. I'll go ahead with creating a variable to disable /etc/mesos/zk management.

Despite the unit tests, this doesn't actually work with the current organization of the module. When mesos::slave is called, it can be passed manage_zk_file, but that variable is not passed to mesos::config.
I am actually going to approach this another way. Even with a conditional block around the file resource, Puppet still sees it as a duplicate definition when I also have my Marathon module trying to manage the resource.
I am going to close my PR and make a new one with just the Travis-related fixes.

Paul

mesos::slave is called, it can be passed manage_zk_file, but that variable is not passed to mesos::config

That's correct. In order to avoid configuration repetitions mesos::config is shared between slave and master. Thus,
class{'mesos':
  manage_zk_file => false
}
class {'mesos-slave':
#...
}

should install mesos-slave without /etc/mesos/zk.
Or with Hiera you just define property (shared for all masters and slaves):
mesos::manage_zk_file: false

and simply include slave to your node:
class {'mesos-slave':
#...
}

Now it should "magically" not manage /etc/mesos/zk.

I am going to close my PR and make a new one with just the Travis-related fixes.

You could have just rebased the PR.

Good points! I was so focused on figuring out an elegant way on the a Marathon end that I overlooked that.
I'll create a new PR and reference this one for continuity.


werkzeug.datastructures.ResponseCacheControl's s_maxage errors with callable error

Response().cache_control.s_maxage errors with None is not callable
from werkzeug.datastructures import ResponseCacheControl

cc = ResponseCacheControl()
cc.s_maxage = 1

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Input In [13], in <cell line: 1>()
----> 1 cc.s_maxage = 1

File /usr/local/lib/python3.10/site-packages/werkzeug/datastructures.py:1958, in cache_control_property.<locals>.<lambda>(x, v)
   1949 def cache_control_property(key, empty, type):
   1950     """Return a new property object for a cache header. Useful if you
   1951     want to add support for a cache extension in a subclass.
   1952
   1953     .. versionchanged:: 2.0
   1954         Renamed from ``cache_property``.
   1955     """
   1956     return property(
   1957         lambda x: x._get_cache_value(key, empty, type),
-> 1958         lambda x, v: x._set_cache_value(key, v, type),
   1959         lambda x: x._del_cache_value(key),
   1960         f"accessor for {key!r}",
   1961     )

File /usr/local/lib/python3.10/site-packages/werkzeug/datastructures.py:2039, in _CacheControl._set_cache_value(self, key, value, type)
   2037     self[key] = None
   2038 else:
-> 2039     self[key] = type(value)

TypeError: 'NoneType' object is not callable

2.0.3 is OK
Flask use case
from flask import Response

response = Response()
response.cache_control.s_maxage = 1

Environment:

Python version: 3.10.4
Werkzeug version: 2.1.0

I think the change would be something like
s_maxage = cache_control_property("s-maxage", None, int)

Related to https://github.com/pallets/werkzeug/pull/2254, which missed testing ResponseCacheControl.

Cool and speed!


[fontconfig] no absolute paths

For #20469

@autoantwort ,Thanks for your pr, could you please take the error log:

CMake Error at /agent/_work/1/s/scripts/buildsystems/vcpkg.cmake:540 (_add_executable):
  Target "kioexec" links to target "LibMount::LibMount" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
Call Stack (most recent call first):
  src/kioexec/CMakeLists.txt:28 (add_executable)

CMake Error at /agent/_work/1/s/scripts/buildsystems/vcpkg.cmake:578 (_add_library):
  Target "kio_trash" links to target "LibMount::LibMount" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
Call Stack (most recent call first):
  src/ioslaves/trash/CMakeLists.txt:30 (add_library)

CMake Error at /agent/_work/1/s/scripts/buildsystems/vcpkg.cmake:578 (_add_library):
  Target "kcm_trash" links to target "LibMount::LibMount" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
Call Stack (most recent call first):
  src/ioslaves/trash/CMakeLists.txt:95 (add_library)

/azp run

@autoantwort ,Could you please fix the conflict file?

Thanks for the fix!


Any plans to support Phased LSTM

It is more of a request.. There are few implementations out there, but is there any plans to add it to Keras?

Could someone please answer the question :) ?


Stop using SlowImpactsEnum for terms whose docFreq is less than 128.

We currently use SlowImpactsEnum for terms whose docFreq is less than 128 because it's convenient as these terms don't have impacts anyway. But a recent slowdown on nightly benchmarks suggests that this contributes to making some hot calls more polymorphic than we'd like, so this PR moves such terms back to the regular impacts enums.

With Combined tasks in the file (call is 3-polymorphic in the baseline, bimorphic in the modified version):
                            TaskQPS baseline      StdDevQPS my_modified_version      StdDev                Pct diff p-value
                        PKLookup      277.89      (2.3%)      274.07      (2.6%)   -1.4% (  -6% -    3%) 0.079
             FilteredOrStopWords       33.44      (2.3%)       33.42      (1.9%)   -0.1% (  -4% -    4%) 0.935
            FilteredAndStopWords       48.48      (2.6%)       48.48      (1.8%)   -0.0% (  -4% -    4%) 0.994
     FilteredAnd2Terms2StopWords      195.64      (1.8%)      195.89      (1.4%)    0.1% (  -3% -    3%) 0.806
             FilteredAndHighHigh       62.16      (2.2%)       62.25      (1.7%)    0.1% (  -3% -    4%) 0.813
                  FilteredPhrase       25.15      (2.7%)       25.22      (2.5%)    0.3% (  -4% -    5%) 0.720
                          OrMany       18.96      (4.5%)       19.02      (5.6%)    0.3% (  -9% -   10%) 0.853
                FilteredOr3Terms      149.27      (2.0%)      149.75      (1.6%)    0.3% (  -3% -    4%) 0.574
                    CombinedTerm       34.03      (2.8%)       34.17      (2.2%)    0.4% (  -4% -    5%) 0.623
              FilteredOrHighHigh       52.50      (2.3%)       52.71      (1.8%)    0.4% (  -3% -    4%) 0.531
               FilteredOrHighMed      114.91      (2.3%)      115.46      (1.7%)    0.5% (  -3% -    4%) 0.465
                  FilteredOrMany        9.91      (2.8%)        9.96      (3.4%)    0.6% (  -5% -    6%) 0.572
               FilteredAnd3Terms      189.21      (1.8%)      190.35      (1.6%)    0.6% (  -2% -    4%) 0.257
      FilteredOr2Terms2StopWords      109.76      (1.6%)      110.43      (1.2%)    0.6% (  -2% -    3%) 0.169
                    FilteredTerm      159.61      (2.9%)      160.69      (2.2%)    0.7% (  -4% -    5%) 0.401
             CombinedAndHighHigh       15.58      (1.0%)       15.81      (0.8%)    1.5% (   0% -    3%) 0.000
              CombinedAndHighMed       57.04      (1.3%)       57.92      (0.8%)    1.5% (   0% -    3%) 0.000
              FilteredAndHighMed      123.14      (2.9%)      125.29      (3.0%)    1.8% (  -4% -    7%) 0.060
                       And3Terms      162.00      (4.3%)      167.29      (4.5%)    3.3% (  -5% -   12%) 0.019
             And2Terms2StopWords      152.25      (4.1%)      158.02      (4.2%)    3.8% (  -4% -   12%) 0.004
               CombinedOrHighMed       74.69      (0.7%)       78.15      (2.3%)    4.6% (   1% -    7%) 0.000
              CombinedOrHighHigh       19.55      (0.7%)       20.60      (2.5%)    5.4% (   2% -    8%) 0.000
                      AndHighMed      116.33      (4.0%)      122.79      (1.5%)    5.6% (   0% -   11%) 0.000
                     AndHighHigh       39.43      (4.2%)       41.74      (1.9%)    5.9% (   0% -   12%) 0.000
                    AndStopWords       27.82      (5.9%)       29.51      (6.7%)    6.1% (  -6% -   19%) 0.002
                      OrHighRare      265.91      (7.3%)      284.27      (5.1%)    6.9% (  -5% -   20%) 0.000
                        Or3Terms      155.29      (3.8%)      168.35      (5.7%)    8.4% (  -1% -   18%) 0.000
              Or2Terms2StopWords      146.73      (3.2%)      160.57      (5.7%)    9.4% (   0% -   18%) 0.000
                     OrStopWords       28.40      (5.6%)       32.31      (9.5%)   13.8% (  -1% -   30%) 0.000
                       OrHighMed      168.44      (3.9%)      197.35      (1.6%)   17.2% (  11% -   23%) 0.000
                      OrHighHigh       44.17      (4.6%)       53.19      (1.7%)   20.4% (  13% -   28%) 0.000

Without combined tasks in the file (call is bimorphic in the baseline, monomorphic in the modified version):
                            TaskQPS baseline      StdDevQPS my_modified_version      StdDev                Pct diff p-value
             FilteredOrStopWords       33.95      (1.7%)       33.73      (1.8%)   -0.7% (  -4% -    2%) 0.245
                  FilteredOrMany       10.23      (2.7%)       10.22      (2.9%)   -0.1% (  -5% -    5%) 0.928
              FilteredOrHighHigh       53.10      (1.9%)       53.11      (2.0%)    0.0% (  -3% -    3%) 0.962
                FilteredOr3Terms      150.83      (2.0%)      150.98      (2.3%)    0.1% (  -4% -    4%) 0.879
               FilteredOrHighMed      116.00      (2.0%)      116.30      (2.1%)    0.3% (  -3% -    4%) 0.690
                    FilteredTerm      161.02      (2.7%)      161.57      (2.3%)    0.3% (  -4% -    5%) 0.668
      FilteredOr2Terms2StopWords      110.97      (1.3%)      111.36      (1.3%)    0.4% (  -2% -    3%) 0.399
                  FilteredPhrase       25.49      (3.3%)       25.59      (2.8%)    0.4% (  -5% -    6%) 0.693
                       OrHighMed      195.25      (2.5%)      196.56      (1.9%)    0.7% (  -3% -    5%) 0.336
                      OrHighHigh       52.92      (2.6%)       53.32      (2.2%)    0.7% (  -3% -    5%) 0.323
              Or2Terms2StopWords      165.87      (3.3%)      167.13      (3.3%)    0.8% (  -5% -    7%) 0.471
                        Or3Terms      177.06      (3.5%)      178.44      (3.5%)    0.8% (  -6% -    8%) 0.484
                     OrStopWords       34.25      (5.2%)       34.64      (5.2%)    1.1% (  -8% -   12%) 0.492
                        PKLookup      274.02      (1.4%)      277.21      (1.4%)    1.2% (  -1% -    4%) 0.009
                      OrHighRare      282.75      (6.6%)      286.27      (6.9%)    1.2% ( -11% -   15%) 0.559
             And2Terms2StopWords      167.40      (3.0%)      170.65      (3.6%)    1.9% (  -4% -    8%) 0.064
                          OrMany       19.64      (4.0%)       20.22      (3.7%)    2.9% (  -4% -   11%) 0.017
                      AndHighMed      131.41      (1.8%)      135.53      (1.8%)    3.1% (   0% -    6%) 0.000
                     AndHighHigh       44.99      (1.9%)       46.55      (2.2%)    3.5% (   0% -    7%) 0.000
            FilteredAndStopWords       50.36      (2.8%)       52.27      (1.9%)    3.8% (   0% -    8%) 0.000
     FilteredAnd2Terms2StopWords      202.89      (2.1%)      210.87      (1.5%)    3.9% (   0% -    7%) 0.000
                    AndStopWords       32.04      (4.8%)       33.33      (5.9%)    4.0% (  -6% -   15%) 0.018
                       And3Terms      178.11      (3.8%)      185.46      (4.2%)    4.1% (  -3% -   12%) 0.001
             FilteredAndHighHigh       65.05      (2.8%)       68.05      (1.9%)    4.6% (   0% -    9%) 0.000
              FilteredAndHighMed      132.31      (3.0%)      139.26      (3.0%)    5.2% (   0% -   11%) 0.000
               FilteredAnd3Terms      195.92      (1.8%)      209.14      (1.8%)    6.7% (   3% -   10%) 0.000


PawGUI - Update load_default_fonts call to account for all supported OSes

Currently, if the user does not have "resources/fonts/dejavu_sans_mono/DejaVuSansMono.ttf" it looks within windows folder only.
Goal after https://github.com/pawbyte/Game-Pencil-Engine-Editor/issues/80 has been implemented, use the std::string std::string font_system_controller::get_os_font_folder()
and
int font_system_controller::get_os_font_count()
and
font_system_controller::get_os_font_file_location(int pos )
to default to 1st font that is available.
Function to update:
bool pawgui::load_default_fonts( std::string mono_font_location, int font_min_size )

Will move to Summer 2024, but hopefully doable in Spring 2024. Investigations needed and some OSes may not support this as easily.


Copy to proof mode working

Should MouseMove allow for selection to continue taking place? Or should it cancel the selection (like what happens right now)

Mouse move should continuously try to find what should be selected, and only select once the mouse is moved up. Successful selection should be indicated somehow, perhaps with the graph string on the mode's toolbar, rather than with a popup.

Does that mean you want 2 graph strings (1 for the tree and 1 for the selection)? Or should the graph string be changed to just represent the selection?


When I use the '?raw' suffix to get the strings, the program reports an error.

mini repo

Thanks for your feedback.Fixed in v2.0.2


Fix invalid docker version check

Changes

Add proper error information on server docker version validation;
Update minimum docker version checks to match current installation version (26).
Opted to reuse current config value for the server docker version check, to improve re-usability;
Injected minimum docker version ok frontend for onboarding page and server validation checks.

Issues

fix #4128

Thank you for the PR 💜. I will fix some things with the constant but overall looks good.

Thank you for the PR 💜. I will fix some things with the constant but overall looks good.

Thank you and I hope to contribute again.

I look forward to your next contribution.


Conditional attributes

Hi,
I think this is not really related to #56. I have a custom element which defines a placeholder attribute. It works like this:
<rhm-combo-box
            id="group"
            @select="${this.onSelectDepartment.bind(this)}"
            .value="${this.selectedDepartmentItem}"
            .items="${this.departmentComboBoxItems}"
            placeholder="Group"
          ></rhm-combo-box>

However, I only want to set placeholderif a certain condition is met. So I came up with something like this:
<rhm-combo-box
            id="group"
            @select="${this.onSelectDepartment.bind(this)}"
            .value="${this.selectedDepartmentItem}"
            .items="${this.departmentComboBoxItems}"
           ${this.departmentComboBoxItems.length > 1 ? html`placeholder="Group"` : ``}
          ></rhm-combo-box>

However, this ends with TypeError: Cannot read property '2' of null in template.ts line 88. Same if I return null instead of an empty string. Returning html`` does not do the trick either. I have also tried this with the when directive, but that also does not work.
Is this even possible?
Thanks a lot in advance.

Not 💯 sure on this and on phone atm so I can't really check it out easily but, would something like this work?
import { ifDefined } from './directives/if-defined.js';

...
<rhm-combo-box
    id="group"
    @select="${this.onSelectDepartment.bind(this)}"
    .value="${this.selectedDepartmentItem}"
    .items="${this.departmentComboBoxItems}"
    placeholder="${ifDefined(this.departmentComboBoxItems.length > 1 ? 'Group' : undefined)}"
></rhm-combo-box>

You can use the if Defined directive to do that.

Thanks a lot I went with @jsilvermist's solution. That works perfectly.


get files detail

it's a new api that could know exact which chunk is stored on which host,
and every chunk's health
i really want more info that about which piece is actively being processed by which worker and all the progress of the worker
@DavidVorick

the host info in some exact pieces keeps changing which might imply there is more than one host hold a piece which i have not noticed before

I'm ok with the general idea of this, but it needs to be done carefully.
The main issue is that this is a LOT of data. Currently, you are sending numChunks * numHosts FileDetail objects. Each FileDetail object will be about 40 bytes in JSON. So if you are storing a 1 TB file across 50 hosts, that's (1 TB / 4 MB) * 50 FileDetail objects (about 12 million), which encodes to 500 MB of JSON.
Even if we used a binary encoding, a 1 TB file is going to require many MB to describe. it's just a lot of data, there's no way around it. So if we're going to do this, the API call needs to have some form of pagination. Probably this will mean requesting a range of chunk indexes.
I suggest separating the host information from the chunk information. Something like:
{
    "hosts": [
        {"pubkey": "foo", "isoffline": false},
        {"pubkey": "bar", "isoffline": false}
    ],
    "chunks": [
        [0, -1, 1],
        [0, 1, -1]
    ]
}

here, chunks is an array of chunks, where each chunk is an array of pieces, and each element in the piece array is the index of a host in hosts. -1 means the piece isn't stored on any host. Also note that we're trying to switch from netaddress to pubkey.
For a 1 TB file on 50 hosts, there are about 250,000 chunks, and each element of chunks is about 140 bytes of JSON, for a total of 35 MB. That's still probably too much to send in one request, but pagination will help.

i think pagination is reasonable
separating the host information from the chunk information is like a light weight compression which i also agree
use pubkey rather than netaddress might not obvious to end user, maybe i can keep them both cause there would be 50 atmost in recent version(i think)

so the steps maybe like:

separate the host information from the chunk information
add pubkey to result
separate file details to each file request rather than a big filesdetail request
pagination each file detail request

@lukechampine look forward to any further suggestion :)

there are 6 chunks for a file with 45678 bytes in test, a little strange

@lukechampine sorry, on a trip(bad wifi connection) recently.
i'll try to fix those problems

Closing because the renter architecture is being overhauled over the coming weeks. The low-level file semantics will likely change in a way that's incompatible with this PR.


[$250] Web - Clicking on zoom photo line should zoom the photo and the large green button should be place at clicked point reported by @aneequeahmad

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click on use icon to open setting page.
Click on any workspace > general settings > edit photo > upload photo.
Click on the the zoom line

Expected Result:
Should zoom image and drag the green button to clicked point
Actual Result:
Not zooming image and dragging the green button.
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web

Version Number: v1.1.99-4
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/189779379-a51506f4-1646-4f9f-a79b-9b946af9e27e.mp4
Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation:
View all open jobs on GitHub

Proposal
We should use Component Slider from '@react-native-community/slider'
I will give detailed proposal if it is okay to use it.

@varshamb We typically don't use external components since most things can be built pretty easily and specifically just for our use case. Could you make a proposal that is an improvement to our current <Slider> instead?

Can confirm that this is reproducible.

@tgolen is this good to get the exported label?

https://www.upwork.com/jobs/~0117a7dd51bf4a5121

heh why isn't this adding a C+

Maybe because we don't have the help wanted label here

Proposal
We can replace the slider wrapper View with this Pressable
                                <Pressable
                                    style={[styles.mh5, styles.flex1]}
                                    onLayout={initializeSliderContainer}
                                    onPress={(e) => {
                                        const newScale = ((e.nativeEvent.layerX / sliderContainerSize)
                                    * (CONST.AVATAR_CROP_MODAL.MAX_SCALE - CONST.AVATAR_CROP_MODAL.MIN_SCALE))
                                    + CONST.AVATAR_CROP_MODAL.MIN_SCALE;
                                        translateSlider.value = e.nativeEvent.layerX;
                                        scale.value = newScale;
                                    }}
                                >
                                    <Slider sliderValue={translateSlider} onGesture={panSliderGestureEventHandler} />
                                </Pressable>

https://user-images.githubusercontent.com/114033410/191382818-340258d4-a784-4541-b5f7-d869c5c90787.mp4

@mananjadhav bump for review pls ^^

@Abdallah-Ahmed-moh's proposal looks good to me and it'll work.  Though my recommendation is to dry up some lines of the code. We're already doing something similar for the green button, on L200. Let's move the logic to a common function.
@tgolen All yours.
🎀 👀 🎀
C+ reviewed

@tgolen Bump

Applied in upwork, PR will be ready in 2-3 days

@Abdallah-Ahmed-moh Any updates on this for us?

@mananjadhav Iam sorry for being late but iam working on it.

Okay thanks for the update @Abdallah-Ahmed-moh

@Abdallah-Ahmed-moh could you please send a daily update on the PR or the progress? It's been 2 weeks since we've assigned the PR, would appreciate if we can get where are at?

Quick bump @Abdallah-Ahmed-moh on PR comments.

@Abdallah-Ahmed-moh quick bump on this PR comment

@laurenreidexpensify co-assigning cuz I'm part of
[Tracking] [Polish] Image-related feature request and improvements #10894

@Abdallah-Ahmed-moh quick bump on this PR comment

@Abdallah-Ahmed-moh Got a chance to look at this comment?

@Beamanator This job is in progress so I'm not putting on hold pending #10894.
Comment if you disagree

Agreed @mallenexpensify 👍

@laurenreidexpensify I have applied, thanks for mentioning

I have read your issue description on upwork site

Applied @laurenreidexpensify

Still waiting on @Abdallah-Ahmed-moh to apply in Upwork, everyone else has been paid

Ok i have apply on upwork on the new post..

@laurenreidexpensify Quick bump on the above comment, so that we can get this one closed out.

@Abdallah-Ahmed-moh can you please send me a link to your Upwork profile so I can confirm I am paying the correct person? Thanks

@Abdallah-Ahmed-moh can you please send me a link to your Upwork profile so I can confirm I am paying the correct person? Thanks

https://www.upwork.com/freelancers/~01d7c9c17e7faeaa3e
this is my profile, sorry for being late.

@laurenreidexpensify Can you help with the above here and closure of the issue?

@Abdallah-Ahmed-moh contract sent in Upwork, please accept so I can proceed with payment! Thanks

@laurenreidexpensify  i accepted your offer.

Everyone has been paid 🎉 Closing


Add health endpoint

Used to scrape if the container image is healthy.
Should be located at /api/health or similar.
Protect with an configurable API key, should only be available to the backend system.

Already implemented, only configurable API key is missing