sl.post_install script sometimes fails to run to completion

@ju2wheels I am debugging provisioning of Windows guests on SoftLayer and am trying to get the default Windows image ready for vagrant use through the use of a post_install script.
The particular script I am using is at https://gist.github.com/lonniev/7d967b09add6ca1f3a8a and it launches a powershell script to do the real work once it has elevated the privilege of the session to run powershell scripts.
My curiosity at the moment is why might SL fail to run the script to completion? I am seeing that the script (which runs to completion rapidly when run manually on a virgin guest after connecting through RDP) may stop midway and never complete.
Yesterday, the delays with DAL05 were atypically long. Is there some heartbeat monitoring between the host/remote vagrant session and the SL-local provisioning process where the post_install might be aborted if the vagrant session either gives up on the process or if the vagrant session has not responded to a "ping" from the SL session?
If not, I would expect that the SL guest would run the post_install to completion, quickly, without participating in any monitoring back to the vagrant session.
It may be that DAL05 had inside-to-outside network issues and the post_install script hung trying to pull in its chocolately installs. However, I would have expected to see something in the post_install log file about any (or most) abnormal terminations.
Not an issue yet, just a question.

Exception calling "DownloadString" with "1" argument(s): "The underlying
connection was closed: An unexpected error occurred on a send."
At line:1 char:1
+ iex ((new-object
net.webclient).DownloadString('https://gist.githubusercontent.c ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

This is one example of the issues with post installation. Meanwhile the awaiting "vagrant rebuild" or "vargrant up --provider=softlayer" process stalls waiting for Boot to finish.
Because the post_install fails (for issues not having to do with the script itself), crucial capabilities like the vagrant user and ssh and rsync don't get added and so vagrant is never going to get status until it balks and gives up.
Is there a way that vagrant can get notified that the post install process failed so that the recovery can occur sooner? Is there a way to learn why SL internally has such difficulty in performing the post installs reliably?

Yesterday, the delays with DAL05 were atypically long. Is there some heartbeat monitoring between the host/remote vagrant session and the SL-local provisioning process where the post_install might be aborted if the vagrant session either gives up on the process or if the vagrant session has not responded to a "ping" from the SL session?

No, theres no heartbeat monitoring. After we issue an order we just keep polling for the transaction status of the machine and wait for completion of the order transaction and for the machine to be running. Theres no push notification to vagrant-sofltayer about the state its always pull by us asking the API. vagrant-softlayer continues to wait for the order transaction completion and server running status until the server is ready or one of the vagrant-softlayer timeouts has been reached.

Is there a way that vagrant can get notified that the post install process failed so that the recovery can occur sooner? Is there a way to learn why SL internally has such difficulty in performing the post installs reliably?

The problem with the post_install is not one we can detect to avoid having to wait for the server to come up if the post_install fails (the only notification of that which im aware of is the notification emails).
If you are having problems with this your best bet is to open a ticket with SL support. The behavior of how the post_install works is one I havent seen good docs for. In particular, some of the questions brought up here through other issue were:

Is the post_install blocking/non blocking? Is the blocking/non blocking behavior different for OS type (Win/Linux) or even between different versions of the OS?
Is the post_install on a SL API side timeout? ie How long will the SL API side wait for the post_install if it even does wait for it?

From my own testing with the Windows post_install a few months ago, I can tell you it fails just about 100% of the time on older Windows versions and sporadically on the newer ones. I had no luck with tickets that I opened to try to track down the issue. My edumacated guess as to why its so sporadic (being that I have 0 working knowledge of the SL API internals) is that the post_install is being run after Windows patches/updates have been applied but has not been restarted to allow those to finish and possibly leaving the .NET env and Windows in a wonky state.

https://control.softlayer.com/support/tickets/17943221

@ju2wheels if it is an automated execution of Windows Update that is shutting down the Windows instance while it is running the post_install script, would it be possible and effective to have a Windows box image that has Windows Update disabled?
If that would stop the apparent reboot during the post_install script, then it could be left to the user of the image to either call Windows Update manually or reenable the service once they want to be able to handle any reboots.
This may not be effective if (1) it isn't a Windows Update reboot that is causing the mysterious abort of the post_install or (2) SoftLayer forcibly runs a Windows Update on all its Windows instances whether or not the instance has the service enabled.

I just checked the Windows Update history on one of the SL instances and it claims it was last updated "Never". That suggests that my hope that maybe Windows Update was a guilty troublemaker is pretty slim.
If not that, then why is the post installation script getting aborted so often?

I dont think its Windows Update but rather some SL internal update/normalization process. If you enable vagrant debug logging and watch the transaction states as its going, IIRC there is a reboot at some point and then it does an update process (which I think is their attempt to install .NET components and other stuff that is not normally installed with base Windows installs as some of the older Windows versions have more recent .NET versions installed).

Perhaps if I create a new SL instance, let it run entirely to an idle state, save that as a clone, and then use that image as the effective base box. I’d still like the opportunity to run a post install script but maybe SL would keep itself out of the process for that?
—Lonnie VanZandt
303-900-3048
Sent from Dropbox's Mailbox on Mac
On Mon, Apr 20, 2015 at 4:48 PM, Julio Lajara<EMAIL_ADDRESS>wrote:

I dont think its Windows Update but rather some SL internal update/normalization process. If you enable vagrant debug logging and watch the transaction states as its going, IIRC there is a reboot at some point and then it does an update process (which I think is their attempt to install .NET components and other stuff that is not normally installed with base Windows installs as some of the older Windows versions have more recent .NET versions installed).
Reply to this email directly or view it on GitHub:
https://github.com/audiolize/vagrant-softlayer/issues/54#issuecomment-94472818

Sorry to be an SL tyro: how does one find the GUID for a Softlayer Standard Template Image? I hope to be able to find the GUID for the image I just made from the Windows Server that has been prepped for Vagrant use. However, I cannot find a way to get a GUID for the image whether the resource is a Private Image, Public Image, or exported ObjectStore resource. Where is the GUID revealed?

Install the Softlayer Python cli tool and use that to run the cli tool:
pip install SoftLayer
sl image list

Nothing is so easy. ;-)
I get to resolve this error now: https://github.com/softlayer/softlayer-python/issues/486

Did it not add the sl or slcli command to your PATH ? or do you get that error using the CLI tool too? Not sure how that behaves on a Mac.

python and pip were a hash of brew and macosx. I had to update, upgrade, and doctor brew. Then uninstall python, then install it, then link it. Then "sl" complained that it is obsolete and I should use "slcli" instead. Currently, slcli is complaining about the format of my .softlayer file, a file I haven't looked at for a year. Now trying to find out WTF it wants. ;-)

slcli setup obviously regenerates the ~/.softlayer file. However, what is the right choice for "endpoint" and what happened to the setting for the domain name?

Ah, I see what's happening: originally, I created ~/.softlayer to source in the SL_* environment variables and now this CLI app also wants to use the same filename. I can move mine to ~/.softlayer.env and let slcli have the .softlayer file.
Answering my own question, "public" is the right endpoint.

Ive only ever had username, api_key, and endpoint_url in mine, no idea what the domain name was for. You can either backup your file and run slcli config setup and it will drop in the right value for endpoint_url.

Perhaps I made it up? I reference it in the Vagrantfile to pass the default domain name into the CCI provisioner.
Anyway, in the end, slcli list image reveals the guids. Thank you, once again.

@ju2wheels what is the relationship between cci.vm.box and sl.guid_image? How do we convince the provisioner that we want an image_guid and not a box image?
      #Note: If you use SL_GENERIC box you must set sl.image_guid or sl.operating_system/sl.dis_capacity, otherwise it is pre-set for you by the box

This might be better said that if you want to use a global image, then you can't set sl.operating_system and you must set the box to be SL_GENERIC.
However, this isn't enough. Something else is guiding the provisioner to think that sl.operating_system is set even though it is not explicitly set [in the Vagrantfile]. It may that I am trying to destroy an image that was created with a box after modifying the Vagrantfile for the image use. Perhaps it is reading machine metadata and is complaining.

It is not the case that an existing machine from a prior configuration causes the conflict. Some setting in the Vagrantfile is either incorrect or missing.
Is there any code that says, "hey, the user wants, say, winrm. Therefore, let's set sl.operating_system to :windows for them." That would be bad.

Explicitly setting sl.operating_system = nil allows the provisioning to carry on. Whether or not SL actually loads the requested global image remains to be seen.

Great! That worked. Vagrant informed SL to provision the right image and it did it. The image has all the vagrantization performed on the bootstrapping instance with the intermittent post_install script.
Now, I need only get vagrant 1.7.3 to get the path-making fix for rsync. (Or that's all I know I need right now!)

By the way, Windows Update definitely runs on the original image because the update history shows a boatload of Windows updates that are installed "today" and none others after the August 2014 build date in your image.


[Feature] Changelog

Hi,
I see a lot changes in this repo, but it was quite hard to look into the git log to find out what actual changed.
A changelog would give me a better overview what is going on :)
If I overlooked it, I am sorry for it.

@conradkirschner basically we migrated from bash scripts to Golang binary doing the same logic. This wasn't yet released but new commands are already in README.md.

I was more into the permission fixes, if you had included it and how you did it... :D (As my pull request wasn't that good)
That's why I was digging in the git log.
It's more a general thing for all your open repos, looking into gitlog to find out what changed is harder than read a small changelog...
But it's up to you, if you dislike changelogs for any reason (too time consuming) just close this request and I will stay with the gitlog
More Help if you like Changelogs or not:
https://keepachangelog.com/en/1.0.0/

@conradkirschner I think we could start adding changelog to Github releases like we do e.g. for Selenoid.

It's possible to auto generate a change log from git tags and commit history. So instead of starting MORE work, let most of it be automated. Which provides a clearer communication what what exactly happened in the version being released. https://github.com/CookPete/auto-changelog is a simple tool to do this to save time on rewriting every change into a change log.
Below is an exact copy and paste of the change log generated by this tool
You can click this link to view it in a separate tab. https://github.com/CookPete/auto-changelog/blob/master/CHANGELOG.md
Changelog
All notable changes to this project will be documented in this file. Dates are displayed in UTC.
Generated by auto-changelog.
v2.2.0

3 July 2020

add --prepend option as altenative to prepend-token #172
Fix bug when no existing tags #170

v2.1.0

14 June 2020

Add --hide-credit option #166
Add --unreleased-only option #165
Fix --starting-version #164
Add ability to prepend to an existing changelog #156
Use tag date rather than first commit date #162
Add CONTRIBUTING.md #141
Add merge and fix support to commit-list helper #146

v2.0.0

10 April 2020

Refactor codebase #144
Breaking change: Remove the need for core-js and building with babel 2383380
Breaking change: Refactor git data fetching logic 09325ac
Improve progress output a2ba4ac

v1.16.4

2 April 2020

Pin semver to v6 #160
Add node 12 to travis builds ac77a53
Remove node 8 from travis builds e7d557d

v1.16.3

25 March 2020

Bump handlebars from 4.1.2 to 4.3.0 #147
Bump packages 1ced7a8
Add FUNDING.yml 107445f

v1.16.2

29 October 2019

fix parsing of --issue-url and -i options #138
Use noEscape option rather than triple brackets everywhere #131 #133

v1.16.1

4 September 2019

Encode < and > in commit messages #129
Update test data generation c2c9bd8
Refactor release parsing b1ab27e
Add HTML characters to test data b4eb7d7

v1.16.0

31 August 2019

Add --commit-url, --merge-url and --compare-url options #93
Bump packages 84a1bda
Update readme a04c0ff
Lint fixes 7d3c25a

v1.15.0

13 August 2019

Add --config option #127
Infer semver versions from numeric tags #126

v1.14.1

8 July 2019

Add regenerator-runtime dependency #125

v1.14.0

7 July 2019

Update babel/rimraf/nyc #122
HTTPS links to external sites #120
Add support for alternate date sorting #113
fix for handlebars-setup arg #110
Add --append-git-log option #118 #117
Update test data bb3a347
Add commit object to merge data 2a8de35
Fix commander argument syntax 01739fe

v1.13.0

16 April 2019

Support partial semver tag sorting #94
Update --package option to accept file path #106
Tidy up getOptions 0168216
Tidy up readJson util 36bfd9e
Space out error logs 2bc35ce

v1.12.1

11 April 2019

Change behaviour of ignoreCommitPattern to see tags on ignored commits #102
Bump packages b371147
Remove greenkeeper b0841c8

v1.12.0

18 March 2019

Add main entry to package.json #87
Update mocha to the latest version 🚀 #88
Add --merge-pattern option #86
yarn upgrade #91
Add --handlebars-setup option #96 #89 #90
Add --sort-commits option #95 #97

v1.11.0

14 January 2019

Add --stdout option #83
Fix sortReleases for non-semver tags #81
Add backtick characters to test data ab73c8a

v1.10.3

4 January 2019

Clarify includeBranch config array in readme #75
Remove package-lock.json from repo 512205b
Sort and slice commits for latest release 7d7f377
Fix breaking commit sorting 73c05a1

v1.10.2

18 November 2018

Upgrade all packages #59
Remove package-lock.json 791a261

v1.10.1

13 November 2018

Use readline for log util #73 #74

v1.10.0

10 November 2018

Update tests 644f5d8
Add better progress logging 64ebb30
Add --backfill-limit option 5240b1e

v1.9.0

8 November 2018

Add support for azure devops and visualstudio.com #72
Bump packages #56 #60 #61
Add --tag-pattern option #70
Add support for .auto-changelog config #66
Add --release-summary option #69
Add tests for .auto-changelog feature 17b0926
Add tests for sortReleases 9d80b9d
Fix quote style 5c18eda

v1.8.1

8 October 2018

Fix Bitbucket compare links. #65
Update markdownlint-cli to the latest version 🚀 #54
Update markdownlint-cli to the latest version 🚀 #51
Add author to fixes and merges #58
Remove unsupported node versions from travis builds df63917
Add timeout to URL fetching test d635a06
Add node 6.0 to travis builds 088077e

v1.8.0

23 July 2018

Add support for external templates #49 #50
Bump nyc #46
Add README.md to lint checks 5aab29f
Tweak readme headings 9f08899
Remove git from engines bac0248

v1.7.2

28 June 2018

Fix unreleased section sorting #48
Add markdown linting #47
Fix changelog spacing 5e8ffe5
Use %B for supported git versions 1b9c3d7
Enable partial line coverage with codecov e0d24de

v1.7.1

31 May 2018

Fix releases sorting when unreleased enabled #45
Use async fs utils instead of fs-extra #42
Update git log format to support earlier git versions #43

v1.7.0

23 May 2018

Add replaceText package option 77d73ee

v1.6.0

17 May 2018

Add --breaking-pattern option #41
Add --include-branch option #38
Fix duplicate test data commit hashes 7f448ce

v1.5.0

16 May 2018

Feat: match template helper #40
Add commit-list template helper #36 #39
Use UTC dates by default #37
Move helper tests to separate files 71388c2
Remove unused imports from template tests 5ca7c61

v1.4.6

15 March 2018

Added support for old git versions #35

v1.4.5

27 February 2018

Correctly prefix package version #33

v1.4.4

22 February 2018

Do not show date for unreleased section #31
Fix unreleased compare URL 24fbc63

v1.4.3

21 February 2018

Add tag prefix to compare URLs #30

v1.4.2

20 February 2018

Support for gitlab subgroups and self-hosted instances #28
Update standard to the latest version 🚀 #29

v1.4.1

30 January 2018

Support commits with no message #27

v1.4.0

18 January 2018

Update mocha to the latest version 🚀 #26
Add support for generating logs without a git remote #23
Update niceDate tests to avoid timezone issues #24 #25
Add --tag-prefix option #22
Change use of "origin" to "remote" 7c9c175
Add --ignore-commit-pattern option 8cbe121
Add merge commit to test data 4462118

v1.3.0

21 December 2017

Update fs-extra to the latest version 🚀 #19
Add --starting-commit option #21
Add --issue-pattern option #18
Add --latest-version option #17
Override package options with command line options 20e3962
Update tests 2a74da4

v1.2.2

5 December 2017

Fix error when using --unreleased flag #16

v1.2.1

4 December 2017

Filter out merge commits #14
Add commit to test data to trigger sorting 9aa7ed4
Add tests 02613a3
Add commit with matching PR message to test data e9a43b2

v1.2.0

1 December 2017

Add issue-url option to override issue URLs #13
Add major release to test data e14f753
Update readme aaa69d0
Slightly larger heading for major releases d618f01

v1.1.0

9 November 2017

Support modifying commit limit with --commit-limit #12
Move test origins to separate file f8b98b5
Add origin tests f50dced
Add run tests a6ae95e

v1.0.3

7 November 2017

Fix pull request URL 3f6daaa
Bump packages 510c798
Fix version script f849dac

v1.0.2

31 October 2017

Tweak package read logic 5ca75a2
Fall back to https origin protocol 74e29b4

v1.0.1

27 October 2017

Filter out commits with the same message as an existing merge 2a420f7
Update readme 54fc665

v1.0.0

27 October 2017

Update dependencies to enable Greenkeeper 🌴 #10
Refactor codebase dab29fb
Add greenkeeper-lockfile support 126c6fb
Tweak readme badges bf73f55

v0.3.6

23 October 2017

Use origin hostname instead of host #9
Correct bitbucket compare URLs 9d34452

v0.3.5

6 October 2017

Add babel-polyfill #8

v0.3.4

5 October 2017

Add code coverage 786af11
Use async/await instead of promises dff4653
Remove need for array.find polyfill 78a1cb8

v0.3.3

24 September 2017

Bump packages #7
Use babel-preset-env 3eb90ce
Lint fix 67c38dd

v0.3.2

14 September 2017

Prevent duplicate commits being listed #3

v0.3.1

9 September 2016

Improve origin URL parsing #2 #5
Remove semicolons 2ff61e2
More robust log separators adc1dcc
Improve error handling 96b7666

v0.3.0

11 January 2016

Add semicolons after class properties 07b2de5
Remove unique issue filter 11acb7e
Add support for minimumChangeCount in templates 612d80b

v0.2.2

2 January 2016

Add a commit-only release to test data 99927a9
Update templating logic 12c0624
More sensible formatDate db92947

v0.2.1

2 January 2016

Replace toLocaleString usage with months array 0008264

v0.2.0

2 January 2016

Add support for specifying templates 369b51e
Add FAQ to readme 9351ad0
Rearrange usage docs c6bfb0b

v0.1.1

31 December 2015

Explicitly render links for PRs and issues 0a384cd
Fix --package bug 7f12f81

v0.1.0

31 December 2015

Add option for specifying output file #1
Add support for --package 772fbb9
Update badges d17791f
Remove todo list from readme 4446226

v0.0.1

31 December 2015

First commit 436b409

@conradkirschner are you seeing this under releases page?

From the screenshot changelogs will be much better and less clutter. Not in my brightest moment right now, on a trip, but can we regenerate older release changelogs to follow this format?


[KYUUBI #6590] Support http bearer token authentication

:mag: Description
Issue References 🔗

This pull request fixes #6590
Describe Your Solution 🔧
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Support http bearer token authentication by adding an new interface.
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Thanks for review, updated the design based on comments.

Please also add UT in KyuubiRestAuthenticationSuite.

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

Project coverage is 0.00%. Comparing base (d3e1768) to head (f2bbfbf).
Report is 2 commits behind head on master.

Files
Patch %
Lines

...p/authentication/BearerAuthenticationHandler.scala
0.00%
29 Missing :warning:

...authentication/AuthenticationProviderFactory.scala
0.00%
15 Missing :warning:

...kyuubi/service/authentication/BasicPrincipal.scala
0.00%
10 Missing :warning:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
0.00%
9 Missing :warning:

...ver/http/authentication/AuthenticationFilter.scala
0.00%
9 Missing :warning:

...che/kyuubi/service/authentication/Credential.scala
0.00%
7 Missing :warning:

...apache/kyuubi/server/http/util/HttpAuthUtils.scala
0.00%
4 Missing :warning:

...tication/AnonymousAuthenticationProviderImpl.scala
0.00%
2 Missing :warning:

...yuubi/server/http/authentication/AuthSchemes.scala
0.00%
1 Missing :warning:

...tp/authentication/BasicAuthenticationHandler.scala
0.00%
1 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6608   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         677     680    +3
  Lines       41907   41989   +82
  Branches     5721    5731   +10
======================================
- Misses      41907   41989   +82

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

could you update the PR description for more details? @George314159

also cc @pan3793

For ThriftHttp protocol, https://github.com/apache/kyuubi/pull/6621

LGTM

Thanks, merged to master


Build documentation references ambiguous file with no equivalent obvious

The current documentation for the Build package references '../build-example-kit.js', which is ambiguous, upon trying to find this file I found one, which did not correspond to the docs, and gave me little in the way of assistance.

Yep, sorry about that, the README docs got a bit stale. Follow https://github.com/breadboard-ai/breadboard/issues/2687 which tracks full docs on our documentation website.


[TVMC] 'tvmc run' --rpc-tracker and --rpc-tracker fail due to argparse misconfiguration

Fix an error with tvmc, that causes --rpc-tracker and --rpc-key to be identified as a list of strings, rather than the expected string type.
Removing the unnecessary nargs solves the issues.
cc @giuseros @comaniac

Thanks @leandron


Closes #2813: Add Filter and View on Lists for TenantGroup

Closes: #2813
Added Filter for TenantGroup to the following Forms and Filter classes

circuit.Circuit
dcim.Site
dcim.Rack
dcim.RackElevation
dcim.RackReservation
dcim.Device
ipam.IPAddress
ipam.Prefix
ipam.VRF
ipam.VLAN
virtualization.VirtualMachine

Added List View to the following classes:

circuit.Circuit
dcim.Site
dcim.Rack
dcim.RackReservation
dcim.Device
ipam.IPAddress
ipam.Prefix
ipam.VRF
ipam.VLAN
virtualization.VirtualMachine

The filter stuff is fine, but we probably want to create an inheritable e.g. TenantFilterSet with the appropriate fields to stay DRY, like we do with CustomFieldFilterSet.
Aside from that, pulling the TenantGroup into the object lists seems like reaching too far. As it is, it would generate an additional SQL query for each object with a tenant assigned: tenant__group would need to be pulled in by select_related() for each view. But it doesn't seem like there's much value in including the tenant group when the tenant itself a) provides more precise information and b) is clickable anyway.

@jeremystretch @lampwins
One of the things I have come up against is configcontext is in extras, and if I throw in the import from tenancy.forms and tenancy.filters it causes a circular import.
Would like some thoughts on the best way to resolve this, as I would like to add the form/filter to configcontext as well.


How to track erros and usage ?

Sometimes my socket goes to 100% CPU consumption.
For now I'm using for about 100~150 concurrent connections and I use MongoDB to store some kind of incoming messages.
Is there anyway to track where is the bottleneck ? Checking the supervisord logs the only thing I get is the normal incoming/outcoming messages.

Sometimes my socket goes to 100% CPU consumption.
For now I'm using for about 100~150 concurrent connections and I use MongoDB to store some kind of incoming messages.
Is there anyway to track where is the bottleneck ? Checking the supervisord logs the only thing I get is the normal incoming/outcoming messages.

Similar behavior in my system too I am using homstead, iam testing one in normal window another in incognito window chrome cpu ratio is going to 100% in task manager, but when i open one window in normal chrome another in firefox its taking less cpu like 45 - 60% this also seems to me bad ratio.


Allow clients to specify a sessionid when connecting.

This is a proposal for new functionality.
The intended use case is to allow clients to reconnect using the same sessionid that they originally connected with.  This, combined with the RedisStore would allow a socket server to fall out of a cluster, a client to reconnect to another server in the cluster, all while maintaining data associated with the socket.
My proposal would be to modify the Manager.handleHandshake method to pull a sessionid from the query if it exists.
In order to utilize this feature, clients would have to set the sessoinid in the socket.options.query (client).
Any thoughts?
I'll submit a pull request including a new test for your consideration!

+1


Prepare-Release scripts buggy with OneDrive folder

New setup.
I have azure-sdk-for-python in my OneDrive folder. I try running the Prepare-Release.ps1 with
 .\Prepare-Release.ps1 azure-monitor-opentelemetry-exporter -ServiceDirectory monitor -ReleaseDate 04/04/24 as usual but get the following errors:

However, when I clone the repo into a regular folder the script works as expected.
There seems to be an error 'C:\Users\lechen\OneDrive' is outside repository at 'C:/Users/lechen/OneDrive - Microsoft/Documents/Projects/Microsoft/azure-sdk-for-python' On branch monitor-release. For context, ``'C:\Users\lechen\OneDrive'` is a symbolic link to the OneDrive folder above, so perhaps the script is messing up on the iterating through folders to find the CHANGELOG file.
@pvaneck

@praveenkuttappan could you take a look?

Any updates on this?


test: Add ExampleLexParse test

Adds a doc test that implements a basic template language.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1ae0a58) 83.56% compared to head (f98035e) 85.75%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
+ Coverage   83.56%   85.75%   +2.19%
==========================================
  Files           3        3
  Lines         365      365
==========================================
+ Hits          305      313       +8
+ Misses         46       37       -9
- Partials       14       15       +1

see 2 files with indirect coverage changes


I managed to Exchange the ARC for a sagecomm

heres this Screenshot hopefully this tool can eventually support this gateway

@highvolt-dev hopefully this program can work with the Sagecomm eventually :3

@hamhamfreak the Sagecomm and Arcyadan have similar APIs, have you tried tmo-live-graph with the Sagecomm configured as an ARC? The Sagecomm support I added to tmo-monitor came from user reports indicating the compatibility, so now it uses the same configuration as the ARC with an explicit third option for Sagecomm that just reuses the ARC logic.


how to watch the event of contract

Hi!
I recently development dapp using Perigord. Perigord is cool and easy to understand.
BTW, I would like to watch the event of contract, but will someone tell me how to do it?
Thank you and best regards.

Hi, thanks for your interest in the project! An example of watching contract events can be found
in the WatchForEvents function in our main repo ( https://github.com/polyswarm/polyswarm/blob/2694baaaf5db2500400c6f94040c7ae81fbe5f11/bounty/registry.go#L138 )

Thank you. I will try it! :D


Broke Tabs with tables

When I put div tab-content inside of a table, the tabs no longer work. I reproduced it from my application to a codepen.

Browser and version Chrome: 55.0.2883.95
Test case: http://codepen.io/imcodingideas/pen/oBNMqw?editors=1000

The issue is between line 26-> 58

Hi, do not put div inside table, put table inside tab content

So for my layout that's how it needs to happen. On top I have the tabs and the tr's are the tabbed content.

You can't put div inside table tag, so you should change your layout


Conflicting files arre not detected

When two Python packages ship the same documentation file, the collision needs to be handled with manual overrides. That's not a big deal, but maybe we can also find automatic overrides for these cases?
For example, skpro, and sktime both ship

site-packages/build_tools/changelog.py, and
site-packages/docs/source/conf.py.

One can solve this collision using the following override
{ pkgs }:
final: prev: {
  skpro = prev.skpro.overrideAttrs (old: {
    postInstall = ''
      rm $out/lib/python${final.python.pythonVersion}/site-packages/build_tools/changelog.py
      rm $out/lib/python${final.python.pythonVersion}/site-packages/docs/source/conf.py
    '';
  });
}

Yes, I agree. Especially since it is not easy to decide which package to prefer. Also, if this package is installed alone, the file should NOT be removed...

I think you'll actually want to solve this problem by telling the pyproject.nix venv builder to ignore the collision.
I see two possible, not mutually exclusive, options:

Ignore collisions for a certain path:

(mkVirtualEnv "foo-env" { foo = []; }).overrideAttrs(old: {
  ignoreVenvCollisions = [
    "lib/python${final.python.pythonVersion}/site-packages/build_tools"
  ];
})

Control which path is the origin for a certain path:

(mkVirtualEnv "foo-env" { foo = []; }).overrideAttrs(old: {
  venvOverrides = {
    "lib/python${final.python.pythonVersion}/site-packages/build_tools" = "${pythonSet.foo}/lib/python${final.python.pythonVersion}/site-packages/build_tools";
  };
})

Reported as https://github.com/pyproject-nix/pyproject.nix/issues/220 in pyproject.nix.


webdriver: Request failed due to Error forwarding the new session Error forwarding the request null

Running tests doesn't seem to work at my machine:
dmitry.lomakin@dlomakin-mb sample-test-function % npm run test

><EMAIL_ADDRESS>test /Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function
> wdio

Execution of 1 spec files started at 2021-06-30T18:30:45.095Z

2021-06-30T18:30:45.097Z INFO @wdio/cli:launcher: Run onPrepare hook
2021-06-30T18:30:45.099Z INFO @wdio/local-runner: Start worker 0-0 with arg:
[0-0] 2021-06-30T18:30:45.369Z INFO @wdio/local-runner: Run worker command: run
[0-0] RUNNING in chrome - /src/google.specs.js
[0-0] 2021-06-30T18:30:45.579Z INFO webdriverio: Initiate new session using the webdriver protocol
[0-0] 2021-06-30T18:30:45.581Z INFO webdriver: [POST] http://testi-selen-*******.eu-central-1.elb.amazonaws.com:4444/wd/hub/session
[0-0] 2021-06-30T18:30:45.581Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: {
      browserName: 'chrome',
      'goog:loggingPrefs': [Object],
      'goog:chromeOptions': [Object]
    },
    firstMatch: [ {} ]
  },
  desiredCapabilities: {
    browserName: 'chrome',
    'goog:loggingPrefs': { browser: 'ALL' },
    'goog:chromeOptions': { args: [Array] }
  }
}
[0-0] 2021-06-30T18:31:04.160Z WARN webdriver: Request failed due to Error forwarding the new session Error forwarding the request null
[0-0] 2021-06-30T18:31:04.160Z INFO webdriver: Retrying 1/3
2021-06-30T18:31:04.161Z INFO webdriver: [POST] http://testi-selen-*******.eu-central-1.elb.amazonaws.com:4444/wd/hub/session
[0-0] 2021-06-30T18:31:04.161Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: {
      browserName: 'chrome',
      'goog:loggingPrefs': [Object],
      'goog:chromeOptions': [Object]
    },
    firstMatch: [ {} ]
  },
  desiredCapabilities: {
    browserName: 'chrome',
    'goog:loggingPrefs': { browser: 'ALL' },
    'goog:chromeOptions': { args: [Array] }
  }
}
[0-0] 2021-06-30T18:31:04.223Z WARN webdriver: Request failed due to Error forwarding the new session Error forwarding the request null
[0-0] 2021-06-30T18:31:04.223Z INFO webdriver: Retrying 2/3
2021-06-30T18:31:04.223Z INFO webdriver: [POST] http://testi-selen-*******.eu-central-1.elb.amazonaws.com:4444/wd/hub/session
[0-0] 2021-06-30T18:31:04.223Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: {
      browserName: 'chrome',
      'goog:loggingPrefs': [Object],
      'goog:chromeOptions': [Object]
    },
    firstMatch: [ {} ]
  },
  desiredCapabilities: {
    browserName: 'chrome',
    'goog:loggingPrefs': { browser: 'ALL' },
    'goog:chromeOptions': { args: [Array] }
  }
}
[0-0] 2021-06-30T18:31:04.285Z WARN webdriver: Request failed due to Error forwarding the new session Error forwarding the request null
[0-0] 2021-06-30T18:31:04.286Z INFO webdriver: Retrying 3/3
2021-06-30T18:31:04.286Z INFO webdriver: [POST] http://testi-selen-*******.eu-central-1.elb.amazonaws.com:4444/wd/hub/session
[0-0] 2021-06-30T18:31:04.286Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: {
      browserName: 'chrome',
      'goog:loggingPrefs': [Object],
      'goog:chromeOptions': [Object]
    },
    firstMatch: [ {} ]
  },
  desiredCapabilities: {
    browserName: 'chrome',
    'goog:loggingPrefs': { browser: 'ALL' },
    'goog:chromeOptions': { args: [Array] }
  }
}
[0-0] 2021-06-30T18:31:04.349Z ERROR webdriver: Request failed due to unknown error: Error forwarding the new session Error forwarding the request null
    at getErrorFromResponseBody (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/webdriver/build/utils.js:121:10)
    at Request._callback (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/webdriver/build/request.js:121:64)
    at Request.self.callback (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:185:22)
    at Request.emit (events.js:314:20)
    at Request.EventEmitter.emit (domain.js:483:12)
    at Request.<anonymous> (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:314:20)
    at Request.EventEmitter.emit (domain.js:483:12)
    at IncomingMessage.<anonymous> (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:420:28)
[0-0] 2021-06-30T18:31:04.350Z ERROR webdriver: unknown error: Error forwarding the new session Error forwarding the request null
    at getErrorFromResponseBody (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/webdriver/build/utils.js:121:10)
    at Request._callback (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/webdriver/build/request.js:121:64)
    at Request.self.callback (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:185:22)
    at Request.emit (events.js:314:20)
    at Request.EventEmitter.emit (domain.js:483:12)
    at Request.<anonymous> (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:314:20)
    at Request.EventEmitter.emit (domain.js:483:12)
    at IncomingMessage.<anonymous> (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:420:28)
[0-0] 2021-06-30T18:31:04.351Z ERROR @wdio/runner: Error: Failed to create session.
Error forwarding the new session Error forwarding the request null
    at startWebDriverSession (/Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/node_modules/webdriver/build/utils.js:45:11)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
[0-0] Error: Failed to create session.
Error forwarding the new session Error forwarding the request null
[0-0] FAILED in chrome - /src/google.specs.js
2021-06-30T18:31:04.469Z INFO @wdio/cli:launcher: Run onComplete hook

Spec Files:	 0 passed, 1 failed, 1 total (100% completed) in 00:00:19

2021-06-30T18:31:04.469Z INFO @wdio/local-runner: Shutting down spawned worker
2021-06-30T18:31:04.722Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2021-06-30T18:31:04.723Z INFO @wdio/local-runner: shutting down
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `wdio`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/dmitry.lomakin/Sources/scaling-test-execution/run-selenium-tests-at-scale-using-ecs-fargate/sample-test-function/.npm/_logs/2021-06-30T18_31_04_738Z-debug.log
dmitry.lomakin@dlomakin-mb sample-test-function %

Any clue on what could break?

 Sometimes I have seen this happening when using it with VPN, try disconnecting from VPN.
S2: Try increasing the value of timeout_seconds attribute in AWS ALB. I modified timeout_seconds attribute in my load balancer and you can do the same by following the below steps:

AWS Console —> EC2 —> Load Balancer —> Select the load balancer —> Action —> Edit attributes
Update the value of Idle timeout to 4000 (thats the max value).

After the updates, I ran 40 concurrent session of sample test case that's checked in part of the GitHub repo, in a loop and I could see at-least one session running in each of these nodes.
Test batch 1 (20 concurrent run - in view):

Test batch 2 (20 concurrent run - in view):

Grid console:

Hope this helps. Thanks

This same error occurs for me too.
Not using a VPN
ALB timeout is 60 seconds. Error occurs within 5 or 6 seconds of running the test.

This same error occurs for me too.
Not using a VPN
ALB timeout is 60 seconds. Error occurs within 5 or 6 seconds of running the test.
Using this project gives a remoteHost of 'null'

Looks like the data nodes are not getting registered to master node. Ideally, when the data node starts up, it will use the below environment properties and startup commands to register itself to the master node:
env: {
      HUB_PORT_4444_TCP_ADDR: options.loadBalancer.loadBalancerDnsName,
      HUB_PORT_4444_TCP_PORT: '4444',
      NODE_MAX_INSTANCES: this.seleniumNodeMaxInstances.toString(),
      NODE_MAX_SESSION: this.seleniumNodeMaxSessions.toString(),
      SE_OPTS: '-debug',
      shm_size: '512',
  },

PRIVATE=$(curl -s http://<IP_ADDRESS>/v2/metadata | jq -r '.Containers[1].Networks[0].IPv4Addresses[0]') ; export REMOTE_HOST=\"http://$PRIVATE:5555\" ; /opt/bin/entry_point.sh

Can you check the logs of the data nodes to see for any errors?

I'm getting the same errors, but seeing nothing on the logs other than the fact that the remoteHost url is null:
12:45:25.230 DEBUG [RegistrationServlet.process] - getting the following registration request  : {
  "class": "org.openqa.grid.common.RegistrationRequest",
  "configuration": {
    "browserTimeout": 200000,
    "capabilities": [
      {
        "applicationName": "",
        "browserName": "chrome",
        "maxInstances": 500,
        "platform": "LINUX",
        "platformName": "LINUX",
        "seleniumProtocol": "WebDriver",
        "server:CONFIG_UUID": "fee0fc50-c652-4615-be0e-9159f3d6199e",
        "version": "94.0.4606.61"
      }
    ],
    "custom": {
    },
    "debug": true,
    "downPollingLimit": 2,
    "enablePlatformVerification": true,
    "host": "<IP_ADDRESS>",
    "hub": "http:\u002f\u002ftestin-Selen-qidwISh9glTz-1519287742.eu-west-2.elb.amazonaws.com:4444\u002fgrid\u002fregister",
    "id": "http:\u002f\u002fnull:5555",
    "maxSession": 500,
    "nodePolling": 5000,
    "nodeStatusCheckTimeout": 5000,
    "port": 5555,
    "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
    "register": true,
    "registerCycle": 5000,
    "remoteHost": "http:\u002f\u002fnull:5555",
    "role": "node",
    "servlets": [
    ],
    "timeout": 180,
    "unregisterIfStillDownAfter": 60000,
    "withoutServlets": [
    ]
  },
  "description": null,
  "name": null
}
12:45:25.231 DEBUG [BaseRemoteProxy.getNewInstance] - Using class org.openqa.grid.selenium.proxy.DefaultRemoteProxy
12:45:25.232 DEBUG [BaseRemoteProxy.setupTimeoutListener] - starting cleanup thread
12:45:25.233 DEBUG [BaseRemoteProxy$CleanUpThread.run] - cleanup thread starting...
12:45:25.233 INFO [DefaultGridRegistry.add] - Registered a node http://null:5555
12:45:25.233 DEBUG [RegistrationServlet.lambda$process$0] - proxy added http://null:5555
12:45:30.235 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:45:35.235 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:45:35.235 INFO [DefaultRemoteProxy.onEvent] - Marking the node http://null:5555 as down: cannot reach the node for 2 tries
12:45:40.237 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:45:45.238 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:45:50.240 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:45:55.241 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:46:00.242 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:46:05.243 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:46:10.244 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:46:15.245 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:46:20.247 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:46:25.247 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:46:30.249 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null: Name or service not known
12:46:35.249 DEBUG [DefaultRemoteProxy.isAlive] - Failed to check status of node: null
12:46:35.249 INFO [DefaultRemoteProxy.onEvent] - Unregistering the node http://null:5555 because it's been down for 60014 milliseconds

12:33:44.476 DEBUG [SelfRegisteringRemote.registerToHub] - Updated node configuration: {
  "browserTimeout": 200000,
  "capabilities": [
    {
      "applicationName": "",
      "browserName": "chrome",
      "maxInstances": 500,
      "platform": "LINUX",
      "platformName": "LINUX",
      "seleniumProtocol": "WebDriver",
      "server:CONFIG_UUID": "fee0fc50-c652-4615-be0e-9159f3d6199e",
      "version": "94.0.4606.61"
    }
  ],
  "custom": {
  },
  "debug": true,
  "downPollingLimit": 2,
  "enablePlatformVerification": true,
  "host": "<IP_ADDRESS>",
  "hub": "http:\u002f\u002ftestin-Selen-qidwISh9glTz-1519287742.eu-west-2.elb.amazonaws.com:4444\u002fgrid\u002fregister",
  "id": "http:\u002f\u002fnull:5555",
  "maxSession": 500,
  "nodePolling": 5000,
  "nodeStatusCheckTimeout": 5000,
  "port": 5555,
  "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
  "register": true,
  "registerCycle": 5000,
  "remoteHost": "http:\u002f\u002fnull:5555",
  "role": "node",
  "servlets": [
  ],
  "timeout": 180,
  "unregisterIfStillDownAfter": 60000,
  "withoutServlets": [
  ]
}
12:33:44.476 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://testin-Selen-qidwISh9glTz-1519287742.eu-west-2.elb.amazonaws.com:4444/grid/register
12:33:44.486 INFO [SelfRegisteringRemote.registerToHub] - The node is registered to the hub and ready to use
12:34:54.550 DEBUG [SelfRegisteringRemote.registerToHub] - Fetching browserTimeout and timeout values from the hub before sending registration request

To me, this suggests this line https://github.com/aws-samples/run-selenium-tests-at-scale-using-ecs-fargate/blob/main/lib/index.js#L135 is failing to read the ip address correctly and thus returning a broken host. But I haven't been able to debug it yet, I'll try to figure it out tomorrow, but if someone already knows the answer (or I'm totally misled), I'd appreciate them sharing it.

Forgot to update this, but I managed to get this working by replacing the aforementioned line of code with:
command: ["PRIVATE=$(curl -s $ECS_CONTAINER_METADATA_URI_V4 | jq -r '.Networks[0].IPv4Addresses[0]') ;  export REMOTE_HOST=\"http://$PRIVATE:5555\" ; /opt/bin/entry_point.sh"],


add support for derangement streams

Implements issue #2:

Add support for derangement streams
Add docs using Asciidoctor
Add test: DerangementsSpec.groovy
Add example: Hats.java
computeNext() is left unimplemented as I couldn't find an implementation that's not overcomplicated and clearly more efficient than unrank()

Thanks for your PR, @polmauri !
I will read through it tomorrow.

Wow! This was a challenging task and you did an awesome job, @polmauri !
You mentioned in the PR comment that you also added docs using Asciidoctor.
Did you forget to commiit the docs changes?

Forgot to add docs change to the original commit. Adding it now.

Thanks!


Update semver to >= 4.3.2

Mitigates semver Regular Expression Denial of Service.
Automated build systems performing nsp audit-package on build are tripped by the vulnerable semver version used by bower.

My bad, semver semantics were actually changed. Never mind => closing

Bower will have to be updated sooner or later.


Store: Add Time & duration based partitioning

Changes
New start of https://github.com/thanos-io/thanos/pull/1077
Verification
Multiple tests added.

Sure, but not for this PR (:

Guys, what do you think about implementing the same in the sidecar?

For Sidecar I think we have a similar PR open https://github.com/thanos-io/thanos/pull/1267


Update "Manage your uploaded files" help center page

We should update https://zulip.com/help/manage-your-uploaded-files to follow our current help center documentation patterns.

@drrosa This one is not urgent, but it would be great if you could add it to your todo list.

@zulipbot claim

@zulipbot claim


queue().empy!

Hi: @seasonSH Yichun
thank you for your work .i trained the base model,how can i do?
essing/queues.py", line 105, in get
    raise Empty
queue.Empty
Process Process-3:
Traceback (most recent call last):
  File "/home/a302/laojiu/anaconda3/envs/tensorflow1.2.0/lib/python3.6/multiprocessing/process.py", line 249, in _bootstrap
    self.run()
  File "/home/a302/laojiu/anaconda3/envs/tensorflow1.2.0/lib/python3.6/multiprocessing/process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "/home/a302/laojiu/github/DocFace/src/utils.py", line 245, in batch_queue_worker
    batch = self.get_batch(config.batch_size, config.batch_format)
  File "/home/a302/laojiu/github/DocFace/src/utils.py", line 202, in get_batch
    indices_batch.extend(self.index_queue.get(block=True, timeout=30))
  File "/home/a302/laojiu/anaconda3/envs/tensorflow1.2.0/lib/python3.6/multiprocessing/queues.py", line 105, in get
    raise Empty
queue.Empty
Traceback (most recent call last):
  File "src/train_base.py", line 111, in <module>
    main(args)
  File "src/train_base.py", line 80, in main
    batch = trainset.pop_batch_queue()
  File "/home/a302/laojiu/github/DocFace/src/utils.py", line 260, in pop_batch_queue
    batch = self.batch_queue.get(block=True, timeout=60)
  File "/home/a302/laojiu/anaconda3/envs/tensorflow1.2.0/lib/python3.6/multiprocessing/queues.py", line 105, in get
    raise Empty
queue.Empty
(tensorflow1.2.0) a302@a302-DGX-Station:~/laojiu/github/DocFace$
``` @

Have you solved this problem？I had the same problem.

I checked if the worker raises any exceptions, ending the 4 workers and not generating any more batch
src/utils.py
    def batch_queue_worker(seed):
        np.random.seed(seed)
        while True:
            try:
                batch = self.get_batch(config.batch_size, config.batch_format)
                if batch is not None:
                    batch['image_paths'] = batch['images']
                    batch['images'] = preprocess(batch['image_paths'], config, is_training)
                self.batch_queue.put(batch)
            except Exception as e:
                print(e)

Have you solved this problem？I had the same problem.

朋友你解决了吗？交流一下

你好，我之前向作者问过，作者给了我以下答复：
seems like your batch_queue is not defined there (it's None). You need to initialize the queue.
我后面不做人脸识别了，就没有继续修改。
| |
15732072757
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 11/12/2019<EMAIL_ADDRESS>wrote：
Have you solved this problem？I had the same problem.
朋友你解决了吗？交流一下
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Is there any way to ignore some table?

In my legacy system, there are one or two tables which I do not want to generate any codes for them. How to do?

@leopku  You can use the --exclude=,  to exclude tables - this has just been added, pull the latest version

@alexj212 Thanks for response so quickly.


optimize serialized format of models

The model store can shave a few bytes off each model by not storing the StableID in the serialized JSON and just placing it in the model store tags. The StableID is already present in the tags, the system just needs to keep from serializing the StableID

closing for now as it's unclear if we really need this optimization


Allow user to specify loss function using LossFunctions.jl

It would be nice to also allow users to pass in losses from LossFunctions.jl: https://github.com/JuliaML/LossFunctions.jl
Currently, we define the following method signature:
https://github.com/dahong67/GCPDecompositions.jl/blob/cfd310fb08ec721978f770fe3109fb6d5ff18a2c/src/gcp-opt.jl#L17-L18
The simplest way to support LossFunctions.jl is probably to define an additional method signature as follows:
gcp(X::Array, r, loss::SupervisedLoss, lower=-Inf) = _gcp(X, r, ???, ???; lower)

where the ??? are what need to be filled in.
@alexmul1114, to start you may want to read through the LossFunctions.jl docs and try some examples. The following parts will be particularly relevant (using v0.10 docs since docs for current version appear to currently be missing the docstrings):

https://juliaml.github.io/LossFunctions.jl/v0.10/user/interface/#Computing-the-Values
https://juliaml.github.io/LossFunctions.jl/v0.10/user/interface/#Computing-the-1st-Derivatives

Closed by #11


TP 650 - Schedule workbasket upload to bucket

Triggers workbasket upload on setting workbasket to 'READY_TO_EXPORT'.

Codecov Report

Merging #312 (f932b6a) into master (8d82074) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #312   +/-   ##
=======================================
  Coverage   90.29%   90.29%
=======================================
  Files         268      268
  Lines       13432    13450   +18
  Branches      974      975    +1
=======================================
+ Hits        12128    12145   +17
  Misses       1095     1095
- Partials      209      210    +1

Impacted Files
Coverage Δ

common/tests/test_models.py
100.00% <100.00%> (ø)

conftest.py
85.85% <100.00%> (+0.04%)
:arrow_up:

workbaskets/models.py
89.32% <100.00%> (+0.21%)
:arrow_up:

workbaskets/tests/test_models.py
100.00% <100.00%> (ø)

workbaskets/tests/test_views.py
100.00% <100.00%> (ø)

quotas/business_rules.py
95.27% <0.00%> (-0.79%)
:arrow_down:

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 8d82074...f932b6a. Read the comment docs.

After discussion of the team, have decided to leave the mid-file import to avoid circular import problems for now. We may need to look more into how we queue tasks if we get many more of them.


can not start the program with "--stay-awake"

can not start the program with "--stay-awake"
os: win 10
device: Oneplus LE2100 (Android 11)
PS C:\Users\Desktop\scrcpy-win64-v1.19> .\scrcpy.exe --stay-awake
INFO: scrcpy 1.19 <https://github.com/Genymobile/scrcpy>
C:\Users\Desktop\scrcpy-win64-v1.19\scrcpy-server... file pushed, 0 skipped. 46.7 MB/s (37330 bytes in 0.001s)
[server] INFO: Device: OnePlus LE2100 (Android 11)
[server] ERROR: Could not invoke method
java.lang.reflect.InvocationTargetException
        at java.lang.reflect.Method.invoke(Native Method)
        at com.genymobile.scrcpy.wrappers.ContentProvider.call(ContentProvider.java:108)
        at com.genymobile.scrcpy.wrappers.ContentProvider.putValue(ContentProvider.java:161)
        at com.genymobile.scrcpy.wrappers.ContentProvider.getAndPutValue(ContentProvider.java:167)
        at com.genymobile.scrcpy.Server.scrcpy(Server.java:39)
        at com.genymobile.scrcpy.Server.main(Server.java:255)
        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:419)
Caused by: java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
        at android.os.Parcel.createExceptionOrNull(Parcel.java:2389)
        at android.os.Parcel.createException(Parcel.java:2373)
        at android.os.Parcel.readException(Parcel.java:2356)
        at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:190)
        at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:142)
        at android.content.ContentProviderProxy.call(ContentProviderNative.java:733)
        ... 8 more
Caused by: android.os.RemoteException: Remote stack trace:
        at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2368)
        at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:1413)
        at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:1367)
        at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:501)
        at android.content.ContentProvider.call(ContentProvider.java:2448)

same issue was happening to me, i fixed it by toggling "stay-awake when charging" and rebooting. i dont know how, but it was fixed

I had the same problem - device not staying awake when executing scrcpy with --stay-awake option, but I solved it differently. I mention this different solution as it might be relevant to further development of scrcpy.
I had the same line amongst the output from executing scrcpy --stay-awake:
Caused by: java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
I noticed that @rom1v suggested querying and changing the relevant setting directly via adb - see https://github.com/Genymobile/scrcpy/issues/2612#issuecomment-913036144. I attempted the change command:
adb shell settings put global stay_on_while_plugged_in 7
and got this error:
adb shell settings put global stay_on_while_plugged_in 7 Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
I search this last error statement and tried the solution found here. i.e. On the android phone, go to Settings > Developer Options > Disable permission monitoring. Set this option to disable. Having done this, I no longer get errors when running the scrcpy or adb commands above. The terminology and menu structure that I mention here may be specific to my Android OS (Oppo ColorOS V7.1)
The question (perhaps) for developer/s is whether this setting could be adjusted by scrcpy while it runs, potentially avoiding this whole issue.

The question (perhaps) for developer/s is whether this setting could be adjusted by scrcpy while it runs, potentially avoiding this whole issue.

Probably not: if the vendor added an option to prevent writing secure settings via adb, they would not allow to disable this setting va adb.


How to use without  being a Wrapper ?

Is there a way to return the Actual Component instead of Wrapping the component within  because when using isomorphic-relay-router the Component has to be a RelayContainer
So Instead of
  <CodeSplit chunkName="home" modules={{ Home: require('./components/App/Home') }}>
     { ({ Home }) => Home && <Home {...routerProps} /> }
   </CodeSplit>

Something like this
const Home = CodeSplit({chunkName="home", modules={{ Home: require('./components/App/Home') }});
return <Home {...routerProps} />

Hmmm, I am not familiar with relay or the isomorphic-relay-router, but off hand I can't think of why this wouldn't work.  On the server side the async behaviour of CodeSplit is disabled, so it should just end up resolving your component with the relay routing attached.

Project has been deprecated. 💖


multiple trees in same root, problems with backporting

Hello :)
I'm trying to get multiple subtrees into the same root directory, and have run into problems with backporting commits.
My setup is as follows:
I have a core repo and a plugin repo. I create a new repo 'main', and add both subtrees. Then I modify a file in each subtree, and commit those changes to the 'main' repo. Things work fine so far, git log shows two commits.
Then I try to run git stree push, and run into problems.
This is a trace of what I see:
+ cd /tmp/
+ rm -fR /tmp/test
+ mkdir test
+ cd test
+ mkdir core
+ cd core
+ echo core
+ git init .
Initialized empty Git repository in /tmp/test/core/.git/
+ git config user.name me
+ git config user.email<EMAIL_ADDRESS>+ git config push.default simple
+ git add README.core
+ git commit -m 'core readme'
[master (root-commit) 13b649a] core readme
 1 file changed, 1 insertion(+)
 create mode 100644 README.core
+ cd ..
+ mkdir plugin
+ cd plugin
+ echo plugin
+ git init .
Initialized empty Git repository in /tmp/test/plugin/.git/
+ git config user.name me
+ git config user.email<EMAIL_ADDRESS>+ git config push.default simple
+ git add README.plugin
+ git commit -m 'plugin readme'
[master (root-commit) ec3db0c] plugin readme
 1 file changed, 1 insertion(+)
 create mode 100644 README.plugin
+ cd ..
+ mkdir main
+ cd main
+ git init
Initialized empty Git repository in /tmp/test/main/.git/
+ git config user.name me
+ git config user.email<EMAIL_ADDRESS>+ git config push.default simple
+ echo 'main repo'
+ git add README
+ git commit -m 'initial commit'
[master (root-commit) a93efc4] initial commit
 1 file changed, 1 insertion(+)
 create mode 100644 README
+ git stree add core -P repo ../core
warning: no common commits
[master 2411722] [STree] Added stree 'core' in repo
 1 file changed, 1 insertion(+)
 create mode 100644 repo/README.core

✔ STree 'core' configured, 1st injection committed.

+ git stree add plugin -P repo ../plugin
warning: no common commits
[master b5d0c78] [STree] Added stree 'plugin' in repo
 1 file changed, 1 insertion(+)
 create mode 100644 repo/README.plugin

✔ STree 'plugin' configured, 1st injection committed.

+ cd repo
+ echo 'core v2'
+ git add README.core
+ git commit -m '[core] updated readme'
[master 74e01cc] [core] updated readme
 1 file changed, 1 insertion(+), 1 deletion(-)
+ echo 'plugin v2'
+ git add README.plugin
+ git commit -m '[plugin] updated readme'
[master 6a82afe] [plugin] updated readme
 1 file changed, 1 insertion(+), 1 deletion(-)
+ cd ..
+ git stree push plugin HEAD~1 HEAD~1
error: could not apply 74e01cc... [core] updated readme
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
✖ Could not cherry-pick 74e01cc [core] updated readme

What am I doing wrong here? Is putting multiple subtrees into the same directory unsupported? I'd really need this :-/
Thanks for any help!
  To push to the upstream branch
on the remote, use

    git push stree-plugin HEAD:master

To push to the branch of the same name on the remote, use

    git push stree-plugin stree-backports-plugin

After applying the one-line change from https://github.com/tdd/git-stree/issues/13, the error is:
+ cd repo
+ echo 'core v2'
+ git add README.core
+ git commit -m '[core] updated readme'
[master 2a71b55] [core] updated readme
 1 file changed, 1 insertion(+), 1 deletion(-)
+ echo 'plugin v2'
+ git add README.plugin
+ git commit -m '[plugin] updated readme'
[master 3476ded] [plugin] updated readme
 1 file changed, 1 insertion(+), 1 deletion(-)
+ cd ..
+ git stree push plugin HEAD
• 3476ded [plugin] updated readme
git push --quiet -u stree-plugin stree-backports-plugin:master
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To ../plugin
 ! [remote rejected] stree-backports-plugin -> master (branch is currently checked out)
error: failed to push some refs to '../plugin'

git branch -va shows:
* master                      3476ded [plugin] updated readme
  remotes/stree-core/master   2d35e0a core readme
  remotes/stree-plugin/master 8499127 plugin readme

It seems like it should work, but for some reason the backport seems to target master instead of the remote?

Hey there,
Oh WOW you should absolutely refrain from using a single directory for
multiple subtrees.  Actually, stree should prevent you from doing so.
This is NOT at all how subtrees in general were intended to be used.
You should absolutely use per-subtree subdirs.  Otherwise you're not
splitting concerns properly across your repos.
Backporting and splitting uses history filtering based on subtree dir,
which is the nominal, "approved" way of doing it.  So of course it'll
get confused when backporting from two conflicting-dir subtrees.
Thanks a lot for bringing this to my attention, though!
--
Christophe Porteneuve
Founder & CTO, Delicious Insights
<EMAIL_ADDRESS>+33 662 059 656

Unfortunately there is no way around this, some PHP projects (like Joomla or Moodle) force modules to be part of the normal directory structure. Yes, it is a very bad idea, but there just is no way around this for those projects :(

just for your information, the following works fine:
make bare repos for core, and all plugins. add strees for all, pointing to the same prefix for all. apply the patch I mentioned above to stree.
Things work fine then.
If I may suggest this, would you consider not forbidding this, as it seems to work fine.
a) there are no path conflicts between both subtrees
b) you explicitly state which commits to push
c) these commits are all subtree-specific
This is a rather tall order for most ways.
Agreed for the warning and confirmation request instead of hard error.
--
Christophe Porteneuve
<EMAIL_ADDRESS>

I'd expect the developer to take care of this, if s/he really wants to do this (against better judgement, only if really necessary).
for a), if there are any, it's your own fault as a developper, don't do that
for b), yes, there's no simple way around that, as far as I understand there's no way to find out which remote "has" a file in git
for c), that again is my burden as a developer, if I do this wrong, I'll have to go back and split the commits.
Thanks for your help, git stree works great here (even though not intended to :)


integrate glitch with petstore

how does the integrate flag work?
how does one get generated api docs (i noticed swagger-middleware as dependency in package.json), and what's the url?

[sqz@localhost/tmp]  $ node -v
v6.9.1
[sqz@localhost/tmp]  $ datafire integrate --openapi http://petstore.swagger.io/v2/swagger.json
Created integration petstore_swagger in ./integrations/petstore_swagger
path.js:7
    throw new TypeError('Path must be a string. Received ' + inspect(path));
    ^

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.join (path.js:1211:7)
    at callback (/tmp/node_modules/datafire/src/commands/integrate.js:55:33)
    at fs.writeFile.e (/tmp/node_modules/datafire/src/commands/integrate.js:90:11)
    at /tmp/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:123:15)

You just need the --name flag. I've just pushed a patch that marks this flag as required for the integrate command.
For example,
datafire integrate --openapi http://petstore.swagger.io/v2/swagger.json --name petstore

The integrate command just downloads the Open API spec to a local file, and creates a small index.js that initializes the integration from this file.

For Open API docs, it won't serve SwaggerUI, but you can access an Open API spec for your DataFire API at /openapi.json.  Just added a note to the Cookbook


Baseline security profile today in a single tenant cluster

Baseline security profile today in a single tenant cluster
Using the current release of Kubernetes (1.13), assuming an entire Kubernetes cluster is used by a single team (i.e. no multitenancy), document the baseline recommended security profile to run a “secure” single tenant cluster.

1 tenant per cluster, 1 Kubernetes cluster per tenant, no changes to Kubernetes upstream other than configuration

/remove-lifecycle stale


Citation

I'm using your data for a school project and i want to cite your repository; i think it would be cool to have a Citation.md

For the moment you will need to cite one of the R packages - any of these are fine: https://nflverse.nflverse.com/authors.html#citation, https://nflreadr.nflverse.com/authors.html#citation,
https://www.nflfastr.com/authors.html#citation
depending on what you’re using

Thanks for the help & and i'm a big fan of your work


add native client auth

This provides authentication support for native client auth. tested against SpinningCubeServer and our temp turn creds enabled identity service (with oauth24d support) and turn server
Related docs changes

[ ] document new config values
[ ] document how to use oauth24d
[ ] document how to setup an oauth24d server (and link to our version)

Changes

TLDR: native client can now use user auth (oauth24d flow) and temporary turn creds

Steal TurnCredentialProvider from feature/authentication (note: this means we'll need to merge properly when we do feature/authentication)
Steal AuthenticationProvider from feature/authentication (same note)
Add OAuth24DProvider implementing oauth24d flow for native client auth
Modify the DefaultMainWindow ui to support async authentication, and presentation of auth values
Add new config values and parsing code for webrtcConfig.json

latest commit fixes a bug, didn't open an issue for it though since this stuff isn't merged in yet.

do you think we should use input fields as opposed to labels for the new auth ui stuff?

closing in favor of https://github.com/CatalystCode/3dtoolkit/pull/63


feat(logging): Allow log to a file

This feature adds the ability to log to a file using a separate log level.
You can configure it like this:
// stryker.conf.js
module.exports = function(config) {
  config.set({
    fileLogLevel: 'trace' // defaults to 'off'
  });
}

Note: The console logger can still be configured as expected using logLevel: 'info'.
This also adds logging to the stryker api. Plugin creators can now opt in to stryker logging by do this:
import { getLogger, Logger } from 'stryker-api/logging';
const logger: Logger = getLogger('myLoggerCategory');

They no longer have to 'role there own config'. Stryker will take care of the logging appearing in the expected places (console and file).

Finally got a green build! I even ran into a race condition with the log4js logging service. I still want to make the code in the LogConfigurator a bit cleaner though. Otherwise it can be reviewed.

Just one question left @simondel. I'll try to update the peer dependency version later today as well. (But might be tomorrow)

Looks good to me! Just one question, do we want to upgrade to log4js 3.0 in this PR or separately?

@simondel I've refactored the code to remove the  IsolatedRunnerOptions interface. I also add the dependency to log4js 3.0.0. Could you merge this PR before merging others today? (don't want to keep resolving package.json merge conflicts)

Merged 🎉


Improve tests

I'm going to add some more test to this pull request.
Let's start by simplifying the current tests by using a common bootstrap file.

Added a fix because getPluralForms wasn't working (see http://3v4l.org/2d41L )

https://github.com/oscarotero/Gettext/commit/c6e2dd5031f03d20f83583eb004d15930d1fc3eb: because Translation instances had already the pluralTranslation array initialized to the correct size and new values were appended to them, giving longer pluralTranslation

https://github.com/oscarotero/Gettext/commit/5d5952aead161a95808ff21c649eb6fed2e23ccf check if a cloned Translations actually clones its Translations, and it seems that it doesn't...

https://github.com/mlocati/Gettext/commit/3c294c59731fc44ce90e9e51824a07007ccc2588: fixed typo

Plurals handling seems really good! :wink:

I guess version 3.0 is coming soon :wink:

I'm done with this PR

I hope to release the 3.0 version today or tomorrow. I want to check it before but I have to find time


How to use this project?

Please add good README file. I want to run this project but have many problems with running it

тут соглы+++


the threshold in vedio.py

Is the threshold in vedio.py is 0.25? But in test.py and train.py is 0.35?

this is just a simple threshold for the video


Strict mode for library

Are you using OpenAPI 2, 3.0.X, or 3.1.0?
Version 3.0.0, but it doesn't matter, such functionality will be useful for all versions.
Would this solve a problem or make something easier?
Not only will I be able to enforce existing contracts using tests and Swagger, but I will also be able to "force" a developer to describe Swagger if they add a new field.
What would you like to happen?
Strict mode will allow you to check not only the fields that will return an endpoint when tested, but also those that are not described in the schema. That is, if I get extra fields that are not described in the schema, I want to get an error, and not get an error only if the fields described in Swagger have not changed.
Describe alternatives you've considered
Honestly, I don't see any alternatives
Additional context or screenshots
To enable this mode, for example, you could do the following
jestOpenAPI(path.resolve(__dirname, '../../src/openapi.yaml'), { mode: 'strict' });

Are you going to resolve the issue?
I'm not sure if I'm gonna make it

do you have "additionalProperties": false in your schema? when i do, it correctly fails to validate when an additional field is present.
https://json-schema.org/understanding-json-schema/reference/object#additional-properties


Error in Electra model

I am getting this error:
The model did not return a loss from the inputs, only the following keys: logits. For reference, the inputs it received are input_ids,token_type_ids,attention_mask.
How do i fix this?

Are you training your own ELECTRA model or predicting with the pretrained model? Able to share the code snippet?

Closing due to inactivity. Please refer to infer.ipynb if you wish to predict with the finetuned ELECTRA model.


Moves permalink hashtag into gutter in docs

Moving the permalink hashtag into the left gutter makes the header for the method more visually distinguishable. It can be difficult when looking at a large doc to distinguish where one method ends and another begins. With the octothorp in the gutter a user can use their peripheral vision, which mean better UX.
Before

After

Before

After

@samueleaton could you update your master & rebase? your master does not include your previous contributions.

@bcardiff I'm not using my master branch. Should I still do it?

@samueleaton the parent of 0c1403b4b81e329d39642d3516df962fc5f66bf3
is eae4ce37d77f3054504314977c0bf2daf677d486 and crystal master head is currently 61a3b69946116952705b1dc46ce75e4a63a047ef . Your previous contributions are at 06639e68cc383c295ecb7cea52f117169d2f0234 and affect the same files. I could rebase and commit in master directly but it was strange that the above screenshots include your previous visual changes but the commit does not.
I might be missing something, but that is way I see at:

@bcardiff let me know if its not fixed

Thanks @samueleaton !


Refactor the GUI code

This is a draft PR because I have not tested it yet.

This is what the GUI looks like now.


Shadow on forms

Is it possible to have 4-sides shadow , not only on right and bottom? It would be really nice to have ?

I'm with mace17 here. Is it possible to change drop shadow parameters like offset, blur and shadow opacity/intensity so that it looks like this:

https://github.com/Wagnerp/Krypton-NET-5.470
https://github.com/Wagnerp/Krypton-NET-5.470#2019-04-15-build-901---drop-shadows


Provide a Snap Package

Providing a snap package will make it easier to deliver and update this app

Well, it's just overcomplicating stuff with all the Canonical procedure in order to update the snap package using their infrastructure ....
i will give it a try (already did but i've failed)


Better UI needed for Superhero information

Can I create a visually more appealing UI for the superhero information page, the information currently appears like this as shown below in the screenshot?

We need to fetch hero's information using an API and display the dynamically searched information as well.
Use this API - https://www.superheroapi.com/
Are you interested to work on it?

Yes I would like to work on this @madhurafulkar

Could you please provide an update on the current status of the assigned task?
@MurtazaShikari

We are unassigning this issue as we've been waiting for your pull request, but it appears you're not interested in completing the work. @MurtazaShikari


[STORY] WA-10 - Update URL

:bulb: Task
:busts_in_silhouette: Role
User
:point_up: Want
Update URL/API
:+1: Result
To Get correctly the weather information
:ok_hand: Criteria

Must use new SMN API
Must be authorize
Must show correctly the Weather info

New API: https://ws1.smn.gob.ar/v1/forecast/location/{{substation}}
Header: Auhtorization: JWT {{token}}
Need to find the right token secret key.

Token Info:
{
   sub: 'web',
   scopes: 'ROLE_USER_FORECAST,ROLE_USER_GEOREF,ROLE_USER_HISTORY,ROLE_USER_IMAGES,ROLE_USER_MAP,ROLE_USER_STATISTICS,ROLE_USER_WARNING,ROLE_USER_WEATHER',
   iat,
   exp
}


Correct syntax errors in PNA_CONNTRACK version of code

When one #define's the preprocessor symbol PNA_CONNTRACK, parts of the code enabled have syntax and semantic errors. These changes correct those errors.

Hi @jfingerh can the code be compiled with the existing toolchain and suitable macro flag, and if so, I'd propose we make a CI pipeline to test it with every build. I can help.

If/when we have a BE, this will be ok


Vertical divider

A vertical divider may help with layout arrangement.
Some use cases:

navbar
  <button class="transparent square">
    home
  </button>

  <button class="transparent square">
    list_alt
  </button>
  <button class="transparent square">
    search
  </button>

split list

 {{ i }}

 {{ i }}

When used in navbar, I think, something like inline-size: 0.8rem should be okay. When come to more "generic" usage like dividing two vertical lists, it's a little bit hard to decide height property of .divider element.
I tried to mix .horizontal with exsited .xx-line and .xx-height to make the demos above. But I wonder if there is a better solution, or even "vertical divider" can/should be covered by pure CSS lib?

Hi @FirokOtaku ,
The *-line helpers are used to set the space between text lines.
I would to suggest just divider vertical or divider vertical max to set the divider as vertical.
Can you update this PR to have just this css?
// Minimum height

// Maximum height

.divider.vertical {
  inline-size: 0.0625rem;
}

.divider.vertical.max {
  align-self: stretch;
  flex: none;
}

Sure. *-line and *-height are removed.


Ultra seqfaults with -p > 2781

If it's a memory issue, it would be nice if it told me that. If it's a code issue, it would be nice if it supported higher values. Thanks for writing this software.

We've used ULTRA with larger values of -p and 2781, so there's something specific happening. Segfault means that it's somehow escape our error handling, which likely means that the "something specific" is something we haven't prepared for.
If you'd like us to try to figure it out, please provide us with a bit more information. Things like this are a good start:

What are the characteristics of the dataset that you're analyzing with ULTRA? (size of the genome? anything interesting about it, like number of sequences? is it a publicly-available genome, and if yes, is there a link?).
What was the entire command that you ran (this helps us understand if there may be some interplay with other flags)
What are the characteristics of the machine you're using? (What OS? How much RAM?)
Does ULTRA work for other data sets that you've tested? Or for other choices of -p? (I get the impression that -p 2781 works, but -p 2782 does not; is that right?

Basically: more information to us ==> better chance that we can figure out what's going on.

I was hoping it was known issue... In any case I always appreciate a prompt response from the PI. This is for five genomes, 6-7Mb each. All of them seqfault at -p 2782 and not at -p 2781. Sorry, they aren't publicly available, but I decided to test on one that is...
https://www.ncbi.nlm.nih.gov/nuccore/110645304
...and yes, same error profile. (I downloaded the complete nucleotide sequence from that site, getting a sequence.fasta file that appears to be proper genome nucleotide sequence.) The only other flag used is -o. The OS is Ubuntu 22.04.4 on an AWS EC2 c7i-4xlarge instance.

Runningultra -p 2782 Pseudomonas_aeruginosa.fa works fine for me. Running ultra -p 2782 --mem reveals that the run is expected to take around 32 GB, and so the AWS EC2 c7i-4xlarge is likely running out of memory. I just pushed an update (1.0.2b) that will reduce the default memory usage for large models and also always print the expected memory usage before performing analysis. In 1.0.2b you should use a bit over 17 GB when running ./ultra -p 2782
Large period repeat finding is computationally challenging. Two setting adjustments I have found useful when running ULTRA with a large maximum repeat period:

-i 2 -d 2. This reduces the number of indels ULTRA is able to detect, and in doing so reduces memory/runtime for large period repeats by a factor of 5.
--win_size <at least 10X the repeat period>: This reduces the size of ULTRA's DP matrix, allowing for (potentially) large reductions in memory usage. Decreasing the window size does cause a slight increase in runtime, and may also slightly lower the annotation quality. I generally avoid this unless I am working with very very large models.

I'm closing this issue, but please open a new issue if problems persist.

Thanks! I appreciate the help with this issue.


Receiving includes tips from ~users with bad credit card info

From https://gratipay.freshdesk.com/helpdesk/tickets/3240.
~user is seeing a higher number than he is receiving weekly.  This is not due to arrears, because the credit card info for one of the people tipping his team is bad.

Where is the documentation for how the receiving number is calculated?  It's some sort of moving average, right?

Is this the desired behavior?

!m @rohitpaulk @mattbk

I'm noticing that the receiving on teams has been fixed, but the taking values on team owners are still stale. Reopening this, looking into it.


CIVET: 'Test linux' failure

Testing bba6603
Test linux : Failed
View the results here.

not valid


start/stop appserver till the DUTY_CYCLE is up

Before we were working on starting/stopping a single AppServer per
DUTY_CYCLE. This patch will work on multiple AppServer till our time is
up. We don't want to take it past the DUTY_CYCLE to ensure we can
re-evaluate priorities.

OCD run https://ocd.appscale.com:8080/job/Daily Build/3478/


Feature request: make one-way expression bindings for components

See http://teropa.info/blog/2015/10/18/refactoring-angular-apps-to-components.html#replace-two-way-binding-with-one-way-binding
There seems to be little value in the ability of components to change values in the parent scope via two-way =-bindings. @-bindings are one-way, but they can be used only for string values. It'd be logical to introduce a new kind of one-way bindings for expressions of any type or to change the behavior of =-bindings for components (defined with the component method).

:+1: This would make it a lot easier to migrate components across to Angular 2, as well - the less we're relying on two-way binding, the less we'll have to refactor later on. At the minute I'm just trying to enforce 'don't mutate the inputs' as a code convention, but it'd be great to not have to rely on that.

There's actually a PR for that: https://github.com/angular/angular.js/pull/12835
I personally like the idea.

Nice start. Out of curiosity, what is the reasoning for using '#' for specifying the binding mode?

I believe it's still not late for the 1.5 release to include this. It'd be really consistent with the rest of the changes related to the component approach. Please consider extracting it from the ice box before the release.
Let me quote the description of the Ice Box milestone:

Milestone for valid issues and bugs that we have no aspirations on fixing any time soon because they are not affecting primary use-cases and are not aligned with our goals.

I can't agree that it's not aligned with the current goal of migration facilitation.

@thorn0 +1

We'll talk about this in the meeting today.
Regarding the symbol for it, there's nothing set, but > is favorable. - is also okay, but might be confused with the dash delimiter. # has no real connection to bindings.

@Narretz That's great. As for the argument of 'further complicating the DDO API', the API docs can be made to appear less complicated by adding a standard highlighted paragraph 'Best Practice', which would recommend using these new bindings for inputs and & (or events?) for outputs.

Is this being targeted for 1.5?

@robstove
Yes, last minute addition for 1.5. Although, compared to the PR here https://github.com/angular/angular.js/pull/12835 We are not going to copy the parentValue, instead we just set it on the isolate scope. This means, if you have bind an object and then change a property on that object, it'll be reflected in the origin scope. This is because completely copying the object to the isolate scope is very difficult. If you need to make a copy, you can always do that yourself.

Perfect! Will look forward to this enhancement. Thanks guys.

Where do we bikeshed about the symbol ? I think < is better :smiley:
(No, seriously, I do... :stuck_out_tongue: )

Dash '-' seemed appropriate to me. I see '=' as two directions and '-' as one direction (not the boy band).

@gkalpak Why <? To me >, because parent > child

bindings: { propertyName: "<attrName" }

Which means: the value is copied from the attribute attrName to the property propertyName.
Indeed, < looks better.

How does this look:
binding: { propertyName: "*attrName" }

@robstove * is already in use. It can be combined with = for watching collections. The new one-way binding should support collections too so we might end up with propertyName: "**attrName" if we choose *.

@thorn0 Ah good point. Forgot about collections.

I personally like the idea.

@Narretz Well thank you!

Nice start. Out of curiosity, what is the reasoning for using '#' for specifying the binding mode?

@robstove This is pretty much what came into my mind when I was prototyping the idea
For me though, from the ideas in this post, it would make more sense to use '>' as you are sending something to the child as @Narretz described


Allow local overrides of Maximum Screen Space Error on sections of tilesets

This issue is kind of similar to the clipping planes issue, but it would be hugely helpful if we could define an area where you can change the SSE on everything inside the area but not the area outside.
This is especially important when working on levels involving a section of the Cesium World Terrain - you may need the immediate area to have very low SSE, but setting the SSE low means the entire world is rendered at that detail, which is terrible for performance.

@argallegos Just an aside, a given max SSE only means that we tolerate the same error over the entire world in the screen space (roughly at least). So actually things will still be aggressively unrefined the further from the camera you get since even large geometric errors will result in small SSE if they are a large distance away. This is how the SSE is calculated from a tile's geometric error:
https://github.com/CesiumGS/cesium-native/blob/b824699d3dd9503a5943007247f683b6adc132d4/Cesium3DTiles/src/ViewState.cpp#L157-L164

Ah, good to know! Maybe then we could define a volume that overrides tile LOD calculations for all tiles within, and tries to keep the tiles at a specific LOD. In that case, it sounds like it would be entirely separate from the Max SSE setting.

I think the idea is still good even if we do it based on SSE! I just mentioned that to address the last part of your comment:

but setting the SSE low means the entire world is rendered at that detail, which is terrible for performance.


Subsequent selections dont work

In your scatterplot example, subsequent selections (after the first) are a little flaky - they dont stop completely, but only occasionally work. Might also be worth keeping the lasso in place until de-selection!

Didnt notice you need to close the loop, ie. make sure cursor is near the start - this may require a little training, so would be good to have it always close!

There is a parameter that controls how close you need to be to close the
loop. If you want it to always close, you can just set this parameter
arbitrarily high, like
lasso.closePathDistance(10000)
On Tue, Aug 25, 2015 at 1:27 PM, nite<EMAIL_ADDRESS>wrote:

Didnt notice you need to close the loop, ie. make sure cursor is near the
start - this may require a little training, so would be good to have it
always close!
—
Reply to this email directly or view it on GitHub
https://github.com/skokenes/D3-Lasso-Plugin/issues/4#issuecomment-134678037
.

great, thanks!
On 25 August 2015 at 18:36, Speros Kokenes<EMAIL_ADDRESS>wrote:

There is a parameter that controls how close you need to be to close the
loop. If you want it to always close, you can just set this parameter
arbitrarily high, like
lasso.closePathDistance(10000)
On Tue, Aug 25, 2015 at 1:27 PM, nite<EMAIL_ADDRESS>wrote:

Didnt notice you need to close the loop, ie. make sure cursor is near the
start - this may require a little training, so would be good to have it
always close!
—
Reply to this email directly or view it on GitHub
<
https://github.com/skokenes/D3-Lasso-Plugin/issues/4#issuecomment-134678037
.

—
Reply to this email directly or view it on GitHub
https://github.com/skokenes/D3-Lasso-Plugin/issues/4#issuecomment-134680143
.


Create Babel-types page

PR related to #1006.
Babel-handbook section for babel-types points to the package README on Github (see).
Since #990, I guess more internal package will be published on the website. I suggest the /docs/internals/ path.

we can say packages too?

Babel has many packages. These seems to me more internal.
This is also related to the handbook. We could just name it handbook/types ?

I don't think we need to relate it to the handbook - it's part of babel/babel like in https://github.com/babel/babel#core-packages

Ok, so what about /docs/core-packages/?

The preview:

This isn't linked from anywhere yet so we'll want to create a page for core

@hzoo Could we merge this ? I created an issue #1021.

Ok but yeah no one will be able to find it atm 😄 ?


Add schema.org annotation of the blog posts

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond. The aim is to improve the web by creating a structured data markup schema supported by major search engines.
It is embedded in the HTML as JSON-LD to tag pages with metadata (title, authors, date, etc).
It would be nice to add in the blog post template the addition of the schema.org annotation

Solved with #605


Unable to find type [Xceed.Words.NET.Container]

Hi,
Firstly, great script think it's awesome! I've just tried the latest one and i'm getting the following error
Unable to find type [Xceed.Words.NET.Container] is this an easy fix?

Do you have PSWriteWord installed?
Install-Module PSWriteWord

and then in the script you are about to start
Import-Module PSWriteWord

Also please provide
$PSVersionTable

Just tried that and same issue
Unable to find type [Xceed.Words.NET.Container].
At C:\Users\alex.NSM-SIDCUP.001\Documents\WindowsPowerShell\Modules\PSWriteWord\Public\PSWordMain.ps1:26 char:110

... eFromPipeline, Mandatory = $true)][Xceed.Words.NET.Container]$WordDoc ...

                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (Xceed.Words.NET.Container:TypeName) [], RuntimeException
FullyQualifiedErrorId : TypeNotFound

Save-ExcelDocument : Cannot bind argument to parameter 'ExcelDocument' because it is null.
At C:\Users\alex.NSM-SIDCUP.001\Documents\WindowsPowerShell\Modules\PSWinDocumentation\Public\Start-DocumentationAD.ps1:63 char:56

... $ExcelData = Save-ExcelDocument -ExcelDocument $ExcelDocument -FilePa ...

                                               ~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Save-ExcelDocument], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Save-ExcelDocument

VERBOSE: Time to gather data: 00:00:14.3045330
VERBOSE: Time to create documents: 00:00:00.4924543
VERBOSE: Time total: 00:00:14.9474380
PS C:\WINDOWS\system32> $PSVersionTable
Name                           Value

PSVersion                      5.1.17134.228
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.228
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

How are you actually starting this script? How your config file looks like?

Ah i feel silly now! i found the issue and it was the person behind the keyboard :) it's all fixed and working now :) thank you once again for a fantastic script :)

That's great! But can you tell me what it was? Maybe I can add some additional checks to make sure when people run it it doesn't break or give meaningful warning.


Hops patch doesn't show up on infobox.

I've made sure to click the notification bell for hops patches under time tracking as well as clicking the hops patch box in the time tracking reminder plugin. Any help would be appreciated! Thanks.

Hey, what is your "Prefer soonest completion" setting of the "Time Tracking" plugin?

I have it turned on. The hops patch is working but now I cant see the tree info box.

It also doesn't work with it turned off also. I've tried re-installing the plug in as well.

With it on it should show the box if any patches are grown or empty, with it off it will only show the box if all patches are grown or empty (including the patches in the farming guild). It will not show the box if all of the patches are currently planted & growing.
With the hops patch starting to work, is this the case for you?

Closing since no feedback in 3 weeks.