unexpected behaviour when seed is passed

Hey. Kudos for chancejs, I find it a great piece of software.
Still I have a question / remark regarding the implementation of name generation.
The following puzzled me a bit when writing tests for my application:
Actual
const chance = new Chance('seed');
console.log(['', chance.name(), chance.name(), chance.name()].join('\n  - '));

// result:
      - Jayden Marsh
      - Frances Baldwin
      - Lula Moss

whilst the result is always the same, reading the docs I'd assume with the same seed it should result in the same name all the time.
Now it seems to me that chancejs is taking care of uniqueness -- which is fine but I couldn't find it in the documentation regarding name generation. Further I wouldn't know if I can trust it to be absolutely collision-free.
Could you please cover this topic a bit more in the documentation, or as a reply?
Thank you!

Hey @iilei ,
This is actually the desired behavior.
The seed isn't saying that it should return the same result every single time a function is called, it is saying that it should generate repeatable results. So, for example if you do the following:
const chance1 = new Chance('seed');
const chance2 = new Chance('seed');
console.log('---- Chance 1 ----');
console.log(['', chance.name(), chance.name(), chance.name()].join('\n  - '));
console.log('---- Chance 2 ----');
console.log(['', chance.name(), chance.name(), chance.name()].join('\n  - '));
// result:
       ---- Chance 1 ----
      - Jayden Marsh
      - Frances Baldwin
      - Lula Moss
      ---- Chance 2 ----
      - Jayden Marsh
      - Frances Baldwin
      - Lula Moss

In more nerdy terms, the seed is actually just seeding the random number generator, which for Chance is actually a Mersenne Twister, which is a pseudo-random generator. It generates mostly random numbers, but has the added benefit that a given seed can be provided which starts it at the same place, but each subsequent random number it generates will come in a known sequence.
Anyway, I'm not sure if I'm explaining it well (as you suggest I'll try to update the documentation to do a better job of explaining this!) but this is the intended behavior.
Put another way, if chance.name() generated the same thing every single time if you just provide a seed, it wouldn't be a very useful library.
Will leave this issue open until I can update the docs with clearer description of the seed and the behavior.

Thanks for your explanation, which I find most helpful.


'Can't find variable : fetch' on Safari 10.0.1

hi there, my understanding is that this polyfill fetch should support Safari 6+. However even if I import 'whatwg-fetch' before using fetch keyword, i still get this error message.
Just want to confirm if 'whatwg-fetch' works with the safari 10.0.1?

Yes, the polyfill will apply to any browser that doesn't implement widow.fetch itself, and Safari 10.0.1 is among them. Therefore, if you've loaded whatwg-fetch properly, the window.fetch() function is guaranteed to be defined.
It sounds like you didn't import whatwg-fetch in a correct way, but we can't help with that, because everyone seems to import libraries in their projects a little differently.


EventHubs AAD resource name

What is the resource name to request tokens from AAD for EventHubs?
For example in order to access storage via AAD tokens the resource name needs to be https://storage.azure.com/ (or a specific storage account) as mentioned in https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-msi#azure-storage-resource-id, I am looking for the corresponding values for event hubs.

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

ID: 8719fae6-003f-f9a8-aba4-639db206780b
Version Independent ID: d3426eb2-66eb-99d4-ce9f-7daf1adf7c25
Content: Authenticate an application to access Azure Event Hubs resources
Content Source: articles/event-hubs/authenticate-application.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@nikhilboreddy Thank you for reaching out and bringing this to our notice. At this time we are reviewing the ask and will provide an update as appropriate


The application /Applications/Atom.app cannot be opened because its executable is missing.

Hi I'm getting the error when running atom from the command line in OSX
ProductName:    Mac OS X
ProductVersion: 10.11.1
BuildVersion:   15B42
Atom Version: 1.1.0

cc @zcbenz @joshaber

did you try Atom Menu > Install Shell Commands?

@alvinsj This is a fresh install with shell commands installed.

Only when running from the command line? Does it launch fine from Finder?

@joshaber It launches fine in Finder and Spotlight.

What's the output of running:
$ ls -la $(which atom)

Is it possible tmux is doing something with PATH?

@timothysu would you mind opening a new Issue? I want to make sure that your Issue gets handled and if @jasonlagaac isn't using tmux, it sounds like a different problem.
@jasonlagaac are you no longer running into this problem?

A common method for starting CLI apps on OSX is to use open -a
open -a Atom README.txt
This works for me 9 times out of 10 and then will fail with the same error message from the OP.  Restarting iTerm/Fish/Tmux fixes the issue for me.
This isn't just an Atom issue. I have the same issue intermittently with open -a Firefox 'http://example.com'

I'm getting the same problem under 10.11.4 beta with atom 1.5.3.   Also using fish and tmux.   However the old reattach-to-user-namespace trick works fine so I've created an alias to run
If you don't know about the reattach-to-user-namespace it is installable with brew.  And you can google it for more details.
function e
    echo "using fish alias to open atom"
		reattach-to-user-namespace atom -n $argv
end

Have the same problem here. os x 10.11.3.
Atom was  installed via brew. Happening now on version 1.5.4, not happening before (I was using atom update feature to get updates).
ls -la $(which atom)
lrwxr-xr-x  1 501  admin  79 Jul  8  2015 /usr/local/bin/atom -> /opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/atom.sh

meet the same, fixed after iTerm restart

opppps can't use it in tmux

I'm having the same issue:
ls -la $(which atom)
lrwxr-xr-x  1 myusername  admin  78 Apr 28 23:59 /usr/local/bin/atom -> /opt/homebrew-cask/Caskroom/atom/1.7.2/Atom.app/Contents/Resources/app/atom.sh
I installed with homebrew as well....
however if i open atom via command line, it works using either of these methods
atom
open -a Atom
I will glady provide ANY information.

It sounds like this is a problem restricted to Homebrew installations? Is anyone still running into this that is not installing via Homebrew?
Homebrew Casks are installed to /User/[username]/Applications not /Applications, so if you have a copy of Atom.app in /Applications, it is probably broken and should be deleted.

I can verify that Homebrew has been installing into
~/Applications
so this is not the problem.

The title of this Issue specifically mentions a problem with /Applications/Atom.app, so if you are having a problem with an Atom.app installed in another location, please open a new Issue.

@jasonlagaac are you running into this problem anymore?

Closing due to lack of response. If you start running into this Issue again, please feel free to reopen it and give us the new information. Thanks!

@lee-dohm I've just started running into this same issue.
This only happens with tmux but the atom {fileName} and 'open {filenNme} -a {applicationName}work fine inzsh`.
This isn't localized to just Atom; this same error is output whenever I try to open a file using tmux in an application outside iTerm. I'll write to the tmux Git page and open up an issue there since it seems like this is a tmux issue.
Just wanted to let you know in case others contact you with this same issue! I will provide another update once I have (hopefully) resolved the issue after contacting the tmux devs so you can direct them to that issue.

@paanvaannd has this been fixed with newer tmux?
The haven't (yet) occured for me with tmux 2.3

that happens when you force quit  atom for some reason, try to restart atom, and iterm/terminal then it should work fine.

@Pipeliner I tried to replicate the issue with the newer version of tmux and running atom {fileName} will now work just fine, but open {fileName} -a {applicationName} works yet results in the following message on occasion:
The window server could not be contacted.  open must be run with a user logged in at the console, either as that user or as root.
I'm not sure what causes this message to pop up. Using the open {fileName} -a {applicationName} method with Atom on an HTML file, I get the error and no file or application opening. Using the same method on the same file but with Microsoft Word, I get no error and the application opens the file. Using TextEdit, the application opens the file but I get the error message as well... strange stuff.

I was able to fix this by clicking "Install Shell Commands" in Atom, then restarting iTerm.


feat: Ignore existing whitespace

Ignores existing whitespaces when reformatting.
Example:
Right now
<root>
.<child />
</root>

becomes
<root>
...<child />
</root>

when prettified.
After this PR, whitespaces in the original are ignored, so the result is:
<root>
..<child />
</root>

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          23     24    +1
=====================================
+ Hits           23     24    +1

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

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 061f822...464230a. Read the comment docs.


Update path, enable conda

Was unable to test the environment using the example in the docs.
Was able to resolve the error by:

Updating path from ./test/ecoli  to .test/ecoli [./.test/ecoli would also work].
Including --use-conda in the command, otherwise it was unable to build the environments

Thanks for catching this Andrew. The docs are mostly done for now but obviously are still in need of some work.
Let me know if you find any sections confusing or unclear!


Update README.md

Codewars site added as an example sites for online learning.

Thank you for your contribution! Sorry I don't think CodeWars is a site that we should recommend to people. There are plenty of platforms for practicing coding but the aim here is to curate the existing products and only recommend the best to people. Codewars imo is not a good platform to practice for interviews and LeetCode is a superior alternative.


Many syntax errors

I installed kaggle on windows machine with python 3.7.0b4 64 bit
pip3 install kaggle --cert"....."
getting same errors on every use of kaggle
Traceback (most recent call last):
File "c:\users<username>\appdata\local\programs\python\python37\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "c:\users<username>\appdata\local\programs\python\python37\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users<username>\AppData\Local\Programs\Python\Python37\Scripts\kaggle.exe_main.py", line 5, in
File "c:\users<username>\appdata\local\programs\python\python37\lib\site-packages\kaggle_init.py", line 18, in
from kaggle.api.kaggle_api_extended import KaggleApi
File "c:\users<username>\appdata\local\programs\python\python37\lib\site-packages\kaggle\api_init_.py", line 22, in
from kaggle.api.kaggle_api_extended import KaggleApi
File "c:\users<username>\appdata\local\programs\python\python37\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 27, in
from ..api_client import ApiClient
File "c:\users<username>\appdata\local\programs\python\python37\lib\site-packages\kaggle\api_client.py", line 289
response_type=None, auth_settings=None, async=None,
^
SyntaxError: invalid syntax

I was able to reproduce with 3.7b4, but not 3.6.5.  I'll make a note to check this out, but I can't prioritize problems with a beta version of Python.  Obviously there will need to be a fix in the next month or so before the official release, but I can't promise anything before then.

Just did an update that should address the 3.7 issues.  Please reopen if you're still having problems in 1.4.1+.


[typescript-language-features] Add setting for autoImportFileExcludePatterns

Counterpart to https://github.com/microsoft/TypeScript/pull/49578

Thanks @andrewbranch! Merging this in so users can test it with TS 4.8 using the next stable vscode release


Only import BlazingSQL as necessary

BlazingSQL is broken: https://github.com/BlazingDB/blazingsql/issues/1037
This workaround allows the repo to work when BlazingSQL isn't enabled.

Any progress here?

It would be great to handle that case as well to ensure the benchmark can be run without the presence of blazinsql in the existing environment.

I agree, but that change can be made separately from this one.  It's better practice to have smaller commits that do just one thing each rather than one big commit which will be harder to revert if a revert is needed.  As suggested here: https://softwareengineering.stackexchange.com/a/206984
So how about we submit this one and then do more in another one?

I agree, but that change can be made separately from this one. It's better practice to have smaller commits that do just one thing each rather than one big commit which will be harder to revert if a revert is needed. As suggested here: https://softwareengineering.stackexchange.com/a/206984

If the premise of the PR is "to make blazingSQL optional" the suggested change is necessary. It doesn't make this PR less atomic to include a necessary change to accomplish the goal. With that said, a follow-up is fine.

Would it even be possible to fix the other one?  We can only do it at runtime.  Does that code run after we already know if blazingsql will be used or not?

Python will throw an ImportError or ModuleNotFoundError if it's not available, which could be caught as an exception and skipped at runtime.
Alternatively, I believe that code only exists due to a period in the spring/summer in which the ordering of imports of RAPIDS libraries was critical to avoiding some subtle errors. I suspect this might no longer be necessary, in which case it could be ripped out

Approving existing changes, the rest can be handled in a followup Pr. Will raise an issue for tracking.


SMD5 MySQL

Hi all,
I would like to use passwords stored in a MySQL database hashed with the folowing function (salted md5 - php) :
public function crypt_password($cleartext_password) {         $salt="$1$";         $base64_alphabet='ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/';         for ($n=0;$n<8;$n++) {             $salt.=$base64_alphabet[mt_rand(0, 63)];         }         $salt.="$";         return crypt($cleartext_password, $salt);     }
But, I don't really understand the meaning of the encoding process described in the pgina doc :

encoding ( hash( password + salt ) + salt )

Do I have to add  a base64_encode() at the end of the previous function to get it work with pgina ?
Thanks guys !

I'm not using php, you should ask that there https://stackoverflow.com/questions/tagged/php

Ok, but, forgetting the php aspect, could you help me understanding the meaning of "encoding ( hash( password + salt ) + salt )" ? "+" means concatenate ?
Thanks for your answer

I haven't done that part of the doc, but it seems so.
append salt to password and hash it, than append salt on the hash and create a base64 encoded string.
To be honest, i don't have the motivation to verify the doc from the devs.
The code that does the stuff can be found at
https://github.com/MutonUfoAI/pgina/blob/master/Plugins/MySQLAuth/MySQLAuth/UserEntry.cs#L113
Please let us know if the doc is correct or not.


Would be good if you didn't have to scroll down to see the question

have everything sized to fit one one page

This should be addressed by CSS prettification. :)
On Sat, Dec 12, 2015, 2:18 PM linbug<EMAIL_ADDRESS>wrote:

have everything sized to fit one one page
—
Reply to this email directly or view it on GitHub
https://github.com/linbug/planigale/issues/20.


(FACT-1373) Prevent fact calls from external facts

Prior to this commit, it was possible to make a facter call from
within an external fact. This would result in a fork bomb where
facter would be constantly calling into itself. In order to prevent
this, set an environment variable that allows us to ensure facter
is not already running when we make the call to evaluate external
facts.

CLA signed by all contributors.


deseq size factors was producing inf values, have defaulted to normal…

…isation with simple total-column until issue is identified

Thanks, Adam.
I would like a second opinion on this one. @CGATOxford/contributors do you agree?

Not quite sure, it seems to me that it is quite desirable to have deseq size factors for the normalization. If there are issues computing them, best solved upstream?

I have been unable to locate the precise issue and it may take sometime to pinpoint the problem (It was an issue that was raised during the SCRUM and @haniap also looked into this) but I assumed that because the normalisation was only used for summary_plotting it shouldn't be too much of an issue if it was defaulted to total-column. Currently the pipeline breaks unless it uses total-column.

ok. Is it a frequent occurrence? If not, then I would test for inf values and only then use normalization by total.

It seems to happen to all of my data and I think @haniap has the same issue with her data.

Ok. Make the change and we can revert later. Remind me to debug upstream. It would be good if the deseq size normalization worked.

@sebastian-luna-valero can we merge?

I was wondering whether @TomSmithCGAT @jscaber @Charlie-George @IanSudbery or @jethrojohnson can comment on this issue as they have previously contributed to this pipeline as well.
It looks to me as if we were solving one problem here and then creating new ones.
@Acribbs have you had a look at the code here:
https://github.com/CGATOxford/cgat/blob/master/CGAT/Counts.py#L167
in which line are you getting inf values?

The issue is that if I use "deseq-size-factors" to normalise the data for producing PCA plots Inf values are created in the columns for certain samples, therefore I assume there must be a division by zero somewhere. Its not consistent throughout all of the samples too. Out of 15 samples, only some show columns of Inf values. Hania also has the same issue.
I haven't had time to fully debug the issue. At the moment the code doesn't work in its present form unless "total-column" is used to normalise. Since we were supposed to close all branches I wanted to merge this so the pipeline is functional again. But if the branch can stay open during the Py3 change then I can debug with @AndreasHeger when we both have time?

Thanks @Acribbs
Could you please run the regression tests on this branch as explained here: https://github.com/CGATOxford/CGATPipelines/pull/280#issuecomment-277614681
and confirm whether the tests pass?

Thanks @Acribbs
All tests passing now locally. Travis errors are due to a pysam update that will be fixed soon so I am going to merge this into the master.


test kitchen not running

on ubuntu the server does not start up correcly, due to a wrong passowrd (and etchosts file too)
on centos it doesn't find the box.

       These processes exited early (check above for their output):
        'GORACE="halt_on_error=1" exec ./bin/boulder-sa --config test/boulder-config.json' with pid 25461 exited 1
       started exec listenbuddy -listen :5673 -speak boulder-rabbitmq:5672 with pid 24823
       export GO15VENDOREXPERIMENT=1
       GOBIN=/opt/go/src/github.com/letsencrypt/boulder/bin go install  ./...
       started GORACE="halt_on_error=1" exec ./bin/boulder-wfe --config test/boulder-config.json with pid 25457
       started GORACE="halt_on_error=1" exec ./bin/boulder-ra --config test/boulder-config.json with pid 25458
       started GORACE="halt_on_error=1" exec ./bin/boulder-sa --config test/boulder-config.json with pid 25461
       started GORACE="halt_on_error=1" exec ./bin/boulder-ca --config test/boulder-config.json with pid 25464
       started GORACE="halt_on_error=1" exec ./bin/boulder-va --config test/boulder-config.json with pid 25470
       I212423 boulder-wfe Versions: boulder-wfe=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       started GORACE="halt_on_error=1" exec ./bin/boulder-publisher --config test/boulder-config.json with pid 25473
       I212423 boulder-ra Versions: boulder-ra=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       started GORACE="halt_on_error=1" exec ./bin/ocsp-updater --config test/boulder-config.json with pid 25476
       started GORACE="halt_on_error=1" exec ./bin/ocsp-responder --config test/boulder-config.json with pid 25482
       I212424 boulder-sa Versions: boulder-sa=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       I212424 boulder-wfe WFE using key policy: goodkey.KeyPolicy{AllowRSA:true, AllowECDSANISTP256:true, AllowECDSANISTP384:true, AllowECDSANISTP521:false}
       I212424 boulder-wfe Server running, listening on <IP_ADDRESS>:4000...

       I212424 boulder-ra loading hostname policy, sha256: 3ddc932620e3f59623af52971fcc3cf38c9759f64575fd018a7097875427ea5e
       started GORACE="halt_on_error=1" exec ./bin/ct-test-srv --config test/boulder-config.json with pid 25484
       started GORACE="halt_on_error=1" exec ./bin/dns-test-srv --config test/boulder-config.json with pid 25487
       I212424 boulder-ca Versions: boulder-ca=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       I212424 boulder-ca loading hostname policy, sha256: 3ddc932620e3f59623af52971fcc3cf38c9759f64575fd018a7097875427ea5e
       started GORACE="halt_on_error=1" exec ./bin/mail-test-srv --config test/boulder-config.json with pid 25489
       E212424 boulder-sa [AUDIT] Couldn't connect to SA database: Error 1045: Access denied for user 'sa'@'localhost' (using password: NO)
       Couldn't connect to SA database: Error 1045: Access denied for user 'sa'@'localhost' (using password: NO)
       started GORACE="halt_on_error=1" exec ./bin/ocsp-responder --config test/issuer-ocsp-responder.json with pid 25493
       I212424 boulder-va Versions: boulder-va=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       I212424 boulder-publisher Versions: boulder-publisher=(Unspecified Unspecified) Golang=(go1.5) BuildHost=(Unspecified)
       started GORACE="halt_on_error=1" exec ./bin/caa-checker --config cmd/caa-checker/test-config.yml with pid 25499

       These processes exited early (check above for their output):
        'GORACE="halt_on_error=1" exec ./bin/boulder-sa --config test/boulder-config.json' with pid 25461 exited 1

akos@akos-ui ~/projects/freelancer/chef/chef-acme $ kitchen converge ssl-centos-7
Expected array default value for '--driver'; got "kitchen-vagrant" (string)
-----> Starting Kitchen (v1.14.0)
-----> Creating <ssl-centos-7>...
       Bringing machine 'default' up with 'virtualbox' provider...
       ==> default: Box 'opscode-centos-7.1' could not be found. Attempting to find and install...
           default: Box Provider: virtualbox
           default: Box Version: >= 0
       ==> default: Box file was not detected as metadata. Adding it directly...
       ==> default: Adding box 'opscode-centos-7.1' (v0) for provider: virtualbox
           default: Downloading: opscode-centos-7.1
An error occurred while downloading the remote file. The error
       message, if any, is reproduced below. Please fix this error and try
       again.

       Couldn't open file /home/akos/projects/freelancer/chef/chef-acme/.kitchen/kitchen-vagrant/kitchen-chef-acme-ssl-centos-7/opscode-centos-7.1
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>>     Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'opscode-centos-7.1' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'opscode-centos-7.1' (v0) for provider: virtualbox
    default: Downloading: opscode-centos-7.1

STDERR: An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Couldn't open file /home/akos/projects/freelancer/chef/chef-acme/.kitchen/kitchen-vagrant/kitchen-chef-acme-ssl-centos-7/opscode-centos-7.1
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on ssl-centos-7
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

tl;dr: I don't know how to fix the CentOS issue, but I'm going to at least try and fix the Ubuntu kitchen issue.
For CentOS, I was able to partially fix this with with patch:
index c6c192a..b651232 100644
--- a/.kitchen.yml
+++ b/.kitchen.yml
@@ -26,7 +26,7 @@ driver:
 platforms:
 - name: centos-7
   driver:
-    box: opscode-centos-7.1 # virtualbox
+    box: bento/centos-7.1   # virtualbox
     image: centos-7-0-x64   # digitalocean
 - name: ubuntu-14.04
   run_list:

However, it now errors with an error that I'm not sure how best to fix acme-53-centos-error.txt
This looks to be due to the resolved erlang cookbook being quite outdated. To be sure, I completely removed my ~/.berkshelf/ folder and retried, and it still errored. acme-53-Berksfile.lock.txt contains the resolved dependency details.
For Ubuntu, I'm getting a similar issue with nothing propagating into /etc/hosts. It looks like this traces back to a few commits in the boulder project, all relating to letsencrypt/boulder#1639, with the two most notable being:
letsencrypt/boulder@d98eb634d134863717b91e348a09182eb7020c6a
diff --git a/README.md b/README.md
index 049df95..491d8bc 100644
--- a/README.md
+++ b/README.md
@@ -57,6 +57,10 @@ or

 (On OS X, using port, you will have to add `CGO_CFLAGS="-I/opt/local/include" CGO_LDFLAGS="-L/opt/local/lib"` to your environment or `go` invocations.)

+Edit /etc/hosts to add this line:
+
+    <IP_ADDRESS> boulder-rabbitmq boulder-mysql
+
 Resolve Go-dependencies, set up a database and RabbitMQ:

     ./test/setup.sh

and
letsencrypt/boulder@dfc1f9465c284fd1f7492ba1b7c3734b51b750da
diff --git a/test/setup.sh b/test/setup.sh
index 1581a1a..21d1f74 100755
--- a/test/setup.sh
+++ b/test/setup.sh
@@ -24 +24 @@ go get \
-go run cmd/rabbitmq-setup/main.go -server amqp://localhost &
+go run cmd/rabbitmq-setup/main.go -server amqp://boulder-rabbitmq &

Ah, nevermind my last comment. I missed that you had uploaded PR #54.

Should be fixed now for CentOS!


add test for extra tls alert

#2080 rebased

Needs to be 8.0 only for now.

Why was this marked draft @victorjulien ? Shall I change something here?

Why was this marked draft victorjulien ? Shall I change something here?

I think you need a new PR with "8.0 only for now."

Why was this marked draft victorjulien ? Shall I change something here?

I think you need a new PR with "8.0 only for now."

ah. I thought that was just a comment for something already done. Thank you!

Rebased in https://github.com/OISF/suricata-verify/pull/2173


Add InitializeTracing function and call it from controller and dispatcher main

Fixes #22
In order to have tracing (via the config-tracing configmap) work properly, a call to SetupDynamicPublishing() needs to be made.  This adds those calls to the main functions of the controller and dispatcher.

/lgtm
/approve


Reactnative/release 2.1

Please find the below task/issues completed:
Release 2.1

Upgraded React-Native version.
Refactored Image component.
Added requires/fallback support.
Added theme config support wiki
Fixed keyboard issues
Fixed Issues in BackgroundImage  component.
Handled container style issues.


Operator request: CumSum

Please add: https://github.com/onnx/onnx/blob/master/docs/Operators.md#CumSum

This is a pretty elementary operator so it would be nice to start with.

Added in v0.1.8 (and in the toolchain)


Hangar column API

Description
Hangar 0.5 is introducing a backward-incompatible column API and replacing arrayset API. This PR includes necessary changes to make it work with hangar 0.5. It also, makes hangar 0.5 as the minimum version that stockroom could work with
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

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

Hey @hhsecond do you need a review here?

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

Codecov Report

Merging #12 into master will increase coverage by 1.07%.
The diff coverage is 91.20%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   90.94%   92.01%   +1.07%
==========================================
  Files          15       18       +3
  Lines         574      551      -23
  Branches       42       40       -2
==========================================
- Hits          522      507      -15
+ Misses         41       33       -8
  Partials       11       11

Impacted Files
Coverage Δ

stockroom/storages/data.py
77.77% <66.66%> (-22.23%)
:arrow_down:

stockroom/core.py
76.78% <76.78%> (ø)

stockroom/storages/experiment.py
81.81% <81.81%> (ø)

stockroom/storages/model.py
81.81% <83.05%> (-6.42%)
:arrow_down:

stockroom/keeper.py
91.66% <91.66%> (ø)

stockroom/__init__.py
100.00% <100.00%> (ø)

stockroom/cli.py
88.88% <100.00%> (+88.88%)
:arrow_up:

stockroom/parser.py
100.00% <100.00%> (ø)

stockroom/storages/__init__.py
100.00% <100.00%> (ø)

tests/conftest.py
100.00% <100.00%> (ø)

... and 18 more

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 d133577...7f756e1. Read the comment docs.

Closing in favor of #16


Can you Auto merge digest changes in Dockerfiles?

Hey, like the title suggests, just wondering if there's a way to automatically merge digest changes in Dockerfiles.

Awesome thanks @rarkins! 👍

Actually.. a plan has come together. The extra logging I added the last time you had automerge problems has caught something:
[
  {
    "msg": "getBranchStatus(renovate\/docker-node-8)",
    "time": "2017-11-07T22:38:21.183Z"
  },
  {
    "statuses": [
      {
        "url": "https:\/\/api.github.com\/repos\/LearningLocker\/xapi-state\/statuses\/d527adc74b9ff1f6b9fcd1b05cfb586c68a40ac9",
        "id":<PHONE_NUMBER>,
        "state": "failure",
        "description": "The Travis CI build failed",
        "target_url": "https:\/\/travis-ci.org\/LearningLocker\/xapi-state\/builds\/298779541?utm_source=github_status&utm_medium=notification",
        "context": "continuous-integration\/travis-ci\/push",
        "created_at": "2017-11-07T21:25:08Z",
        "updated_at": "2017-11-07T21:25:08Z"
      }
    ],
    "msg": "branch status check result",
    "time": "2017-11-07T22:38:21.314Z"
  },
  {
    "branch": "renovate\/docker-node-8",
    "dependencies": [
      "node"
    ],
    "msg": "Branch status is \"failure\" - skipping automerge",
    "time": "2017-11-07T22:38:21.314Z"
  },
  {
    "branch": "renovate\/docker-node-8",
    "dependencies": [
      "node"
    ],
    "msg": "Ensuring PR",
    "time": "2017-11-07T22:38:21.314Z"
  }
]

The relevant link is: https://travis-ci.org/LearningLocker/xapi-state/builds/298779541
So it seems like it was in a failing state at some time and that's why the PR was created. Currently we don't automerge a PR if the branch automerge previously failed - we leave it for humans.

BTW my own code inspection + reproduction seemed to indicate no problem automerging digest updates, I think it was this branch status that is the problem.

Wow nice, that's awesome good find 👍


[PoC] Use Express-style path matching

This demonstrates ripping out all of our path matching logic and just using the logic from Express.
This would be a breaking change due to the change to syntax for optional parameters, along with handling for unnamed parameters (e.g. splats).
This would allow using custom regexes (and potentially path arrays for multiple-choice matching) for path parameters, but I haven't added tests demonstrating that yet.
For more details, for how this would work, see:

http://expressjs.com/en/guide/routing.html
https://github.com/pillarjs/path-to-regexp#readme

cc @j

Thoughts? This matches Express and Koa and seems to hit a good balance of easy and flexible.
It's not my first choice, but it's non-breaking for most use cases (e.g. for all of my current ones), and brings us in line with backend frameworks.

I've added a commit with new test cases demonstrating the new possibilities.

I thought we wanted to make pattern matching pluggable? We would need something like that to maintain a BC path. And then you could have something like <Router matcher={expressMatcher}> for now and put in some deprecation warnings when using the old matcher to inform folks about the change.
As it is, I do like this as a default. It's more expressive and matches an existing paradigm. It looks like the only change is the loss of a non-greedy splat. But we added that fairly recently and only for some edge cases, so I don't think it's a big deal. And they should be able to get around the issue with this new format anyways.
I'm curious if there are implications for how this might change our interaction with Express/Koa. If we have compatible matching rules, we could potentially build an express router to do early matching before you get into a middleware function. You could get some good perf benefits by avoiding much of the common setup code for things like Redux stores and memory histories, and short circuiting for things like 404s and redirect routes. Maybe there are other things you could do too.

I was thinking that, but now I sorta feel like – why bother? Do Express or Hapi lose real expressiveness for not having pluggable route matching? Most web frameworks on the backend that I'm aware of just give you a single way to declare routing rules. Seems to work well enough for those in practice.

I suppose if someone has simple routes and a need for speed, they could write something like fastMatcher that only does simple string matching. Not that I think that's a practical need (the regex compilation is cached and Crankshaft/IonMonkey/FTL should optimize something that hot pretty early on).
Or maybe they want to have an i18n mapping for things like /en-US/programs and /en-GB/programmes.
I don't think those are important and should be something we build for. Just throwing out some ideas. I'm OK with not making it pluggable. But how should we handle BC?

What about a toggle to the old matcher for BC?

That'd definitely be an option. The trick is getting access to the appropriate formatPattern in <Redirect>.

this.context.router.formatPattern?

Not quite – it gets called from https://github.com/reactjs/react-router/blob/v2.0.0/modules/Redirect.js#L38.  Probably the best thing might be to set this there to the transition manager.

Easier to do a global toggle, I think.

My current thought is to have a global toggle, unless we're really confident that having pluggable matching at a global level is worth having.

I don't think we need to go pluggable. Forget I brought that up :) A toggle makes sense to me. Router.useOldPatternMatching() should work for those that need BC.

Hey @taion, I brushed through some of this and it looks like it'll fix all the current cases that I have.    But it was an easy fix.  Just change (/:paramName) to /:paramName?

I've wanted to use path-to-regexp for a while (https://github.com/ryanflorence/nested-router/blob/master/index.js)

@ryanflorence Do you know why we didn't use it in the first place? Was it just not available at the time or something?

For BC I think we add the "matcher" prop, and then we can warn that the default is changing when they don't provide a matcher in 2.1, then in 3.0 we remove the old matcher, set this as the default

@ryanflorence That part is tricky, because there are a number of places where we access PatternUtils as a global singleton, most notably in <Redirect>. We'd have to more or less build full-fledged pluggable matcher support to get this to work. Since path-to-regexp allows users to specify arbitrary regexes for parameters or other parts of their routes, I think we might not actually need pluggable route matching as a feature.

I think main reason for me was I hate the idea of regex route paths, I
expect people to accidentally do weird things with it that they could
easily do with a normal looking route config, but I'm over it.
On Thu, Feb 25, 2016 at 6:38 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

@ryanflorence https://github.com/ryanflorence That part is tricky,
because there are a number of places where we access PatternUtils as a
global singleton, most notably in . We'd have to more or less
build full-fledged pluggable matcher support to get this to work. Since
path-to-regexp allows users to specify arbitrary regexes for parameters
or other parts of their routes, I think we might not actually need
pluggable route matching as a feature.
—
Reply to this email directly or view it on GitHub
https://github.com/reactjs/react-router/pull/3105#issuecomment-189084995
.

I'm probably being naive, but I hope the matcher prop is a function that
gets a route and a location and then returns true or false, then we pass it
to PatternUtils etc.
On Thu, Feb 25, 2016 at 6:46 PM Ryan Florence<EMAIL_ADDRESS>wrote:

I think main reason for me was I hate the idea of regex route paths, I
expect people to accidentally do weird things with it that they could
easily do with a normal looking route config, but I'm over it.
On Thu, Feb 25, 2016 at 6:38 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

@ryanflorence https://github.com/ryanflorence That part is tricky,
because there are a number of places where we access PatternUtils as a
global singleton, most notably in . We'd have to more or less
build full-fledged pluggable matcher support to get this to work. Since
path-to-regexp allows users to specify arbitrary regexes for parameters
or other parts of their routes, I think we might not actually need
pluggable route matching as a feature.
—
Reply to this email directly or view it on GitHub
https://github.com/reactjs/react-router/pull/3105#issuecomment-189084995
.

@ryanflorence I think the way to do that might be something like @j's https://github.com/reactjs/react-router/pull/3098, where there's another check after we finish the standard route matching, to let the user say "no match". Perhaps this might even be possible to do with onEnter (as replace(null) or something).

@taion @ryanflorence yeah, granted I slapped that PR together fairly quickly to get my hands dirty in this code, it's pretty dumb simple.  At some point I think every router library needs some sort of "post-match" style functionality where user's can do simple checks without regex (if they want to), and perhaps param/query type casting (preferably supporting async like my example).  Keeping it pluggable can allow for people to bring their own stuff.  One other example that comes to mind when using a simple "validate" property without any regexes in the path is that I could not even use the match function on the server and dynamically create server-side routes (for the sake of argument, lets say Hapi routes), that way I can take advantage of per-route Hapi caching and not have just one catch all route that renders react views then somehow just call "validate" on the specific route. But this is just getting more complicated, lol.
Anyway, back to what I did, if it returns a "no match", then it moves on to the next route in the chain.  Using "onEnter" would sound kind of confusing to allow for moving on?  Dunno.

onEnter actually wouldn't work, now that I think about it.
Are we all agreed that this sounds like a reasonable way forward? If we're okay with this, plus having a global toggle to switch to path-to-regexp for paths, I can work toward getting this ready for 2.1 or whatever our next point release might be.

:+1: from me.

That would be awesome.  Till then "react-router": "git@github.com:taion/react-router.git#path-to-regexp" for us over here ;)

@j Consider moving to your own fork – I'm likely to update this branch soon to make the new matching opt-in, and will probably delete it anyway if it gets merged.

What is the use case you're trying to solve with this change, @taion? Is it just "let people use regexps"? Or is there some kind of pattern that you can't actually match right now?
People have brought up this issue several times before and it usually just comes down to "i wanna use a regexp". Thing is, by splurging and giving everyone that kind of flexibility, it makes it harder for us to analyze all the paths that could possibly be matched, which could also make it harder to do stuff like warn when a route can't actually be matched.

If that's the case, why not just document that by using regex routes you (may) loose the following...

@mjackson shouldn't cases such as the one you mentioned be covered in your tests?  Also, your use-case is is more-so checking equality on a route and warning on repeated routes.  For regex routes, I'd always add unit tests on the matcher and/or integration tests on the route & handler.  And perhaps if warnings are needed, to run known non-regex routes against the regex routes and warn if the regex route comes before the non-regex one?

I think the biggest benefit is just not maintaining our own route/regex building code and moving to a style that's fully consistent with Express, instead of something that is close but not quite the same.
This is in fact useful for me for asserting that some routes only take integers or UUIDs as URL params, though, and @j has an interesting use case with enums.
In the fully general case, for testing route reachability, I think the user has to specify values for URL parameters anyway – we can't in general arbitrarily find "safe" URL parameter values (and IMO we shouldn't anyway), so I think in fullness, https://github.com/reactjs/react-router/pull/2987 will shape up to some sort of utility function anyway.

Why is everyone so eager to shoot themselves in the foot? Regexps make your route config harder to read! Someone please show me something you can't do with our current path matching.

For my use case, I have a number of routes where the only valid value for the URL parameter is an integer. It's pretty convenient to allow this to fall out in the route matching and just drop to the next route. I don't plan on using more complicated regexes than that (and I'm not sure if it would even work).
I expect that most users won't use regexes – the main benefit for the median user is just that we'd have consistent route definition syntax with Express and Koa.

@taion i agree with the not maintaining the route matching logic.
@mjackson i agree with you as well.
Switching to this matcher does solve my issues, yes.  I'd still rather not use regex and instead use a simple matcher function for my enum use-case, but the fact that this PR already will allow me to remove about 20+ hard-coded routes is a win IMO.  Also, you don't have to use regex if you don't want. ;)
I still would like to see some sort of matcher function (i.e. #3098) where you don't "need" to use regex for simple cases with built in param conversion (i.e. string numbers to real numbers, string mongo object ids to an ObjectID object, etc, etc).   Perhaps the function can be passed in the params and query object and the callback can pass in new param and query objects if they wanted with converted items.  That way someone could use something like https://github.com/hapijs/joi if they wanted (which handles conversions for you and returns the new converted object).
For example:
// validations.js
var user = Joi.object().keys({
  params: Joi.object().keys({
    id: Joi.number()
  }),
  query: Joi.object().keys({
    showFriends: Joi.boolean(),
    someEnumField: Joi.any().allow(['a', 'b'])
  })
});

var wrapJoi = (schema) => {
  return (request, callback) => {
    schema.validate(request, (err, value) => {
      if (err) {
        callback(err.isJoi ? null : err, false);
      } else {
        callback(null, true, value);
      }
    });
  };
};

exports.user = wrap(user);

// routes.js
const validations = require('./validations');

const routes = (
  <Route path="/" component={App}>
    <IndexRoute component={Home} />
    <Route path="/users/:id" component={User} condition={validations.user} />
  </Route>
);

The above is "sudo-coded", but I'd be able to share my validation objects that I already have in Hapi with react-router.  And you can see that using any validation method could be used.  Note the isMatch property can be used to return false to tell the router to move to the next route, or true to try rendering the route, and someone (i suppose) can modify the params to pass an "error" object so that the Component can render appropriate error messages.

@j I think handling this via a separate prop would be more interesting if that prop was polymorphic. It could take in a function, a regex to apply to all params, or an object of regexes or functions that would get mapped to params of the same name. So, these would all be valid:
// Function(match[, callback])
<Route path="/user/:user_id/posts/:category" condition={someConditionalFunction} />
// Regex
<Route path="/user/:user_id/posts/:category" condition={/\d+/} />
// Object
<Route path="/user/:user_id/posts/:category" condition={{user_id: /\d+/, category: someConditionalFunction}} />

That way you can remain concise and still get the functionality you want here.

I don't think we want to do that – having a function that returns true or false is a nice, minimal API, and users can build whatever abstractions they need on top of it.
The reason this change puts the regex in the path isn't because I think it's the right thing to do in some sense – it's because that's what path-to-regexp does, and because I think architecturally it makes sense to use path-to-regexp to handle this, instead of having it in our own code.

#3098 doesn't add a boolean function prop, but one that deals with a callback. I was referring to doing it in the context of that implementation.

I think architecturally it makes sense to use path-to-regexp to handle this, instead of having it in our own code.

I agree with this. The less we have to do ourselves, the better. The big downside, like @mjackson said, is that this introduces complexity and added difficulty into the "simple" matcher currently used. A new, optional prop is better for developer experience and involves less BC hassle. And it's more powerful.
I'm leaning more towards the extra prop at the moment.

How does this introduce complexity?

What I mean is:

This is less code on our side to maintain; we get to rip out our unique bespoke path matching, and it's one less place for bugs to arise
This is one less route definition system for our users to use – they use the same syntax as they do elsewhere
The core use case of routes with params-that-match-anything is unchanged

We should think of this as a code-cleaning refactor; that it does bring in support for regex URL params is secondary.

I'm interested in creating a router that is actually better than stuff
people use elsewhere. To me, the fact that most routers use regexps just
for string matching is a lazy decision that doesn't provide users with much
value, if any at all. Flexibility, sure. But the whole routing system is a
LOT more difficult to understand and it's more difficult for us to build
tooling around it/statically analyze it.
Also, if you guys could please use fewer words that would definitely help
me understand what you're saying. :)
On Wed, Mar 2, 2016 at 12:35 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

What I mean is:

This is less code on our side to maintain; we get to rip out our
unique bespoke path matching, and it's one less place for bugs to arise
This is one less route definition system for our users to use – they
use the same syntax as they do elsewhere
The core use case of routes with params-that-match-anything is
unchanged

We should think of this as a code-cleaning refactor; that it does bring in
support for regex URL params is secondary.
—
Reply to this email directly or view it on GitHub
https://github.com/reactjs/react-router/pull/3105#issuecomment-191418075
.

To summarize a discussion w/@mjackson on Discord, I think in the near term the plan is to look at doing something like Hapi-style static route conflict detection, which would preclude the use of regexes in routes.
If it's feasible to do that, I think it might be a worthwhile tradeoff. I don't think it'd help for e.g. the case motivating #3098, though.
I think the consensus is to leave this PR on hold for a moment, and see how static checking for route collisions works out.
If anybody here has feedback on how this works in practice with Hapi v. its absence in Express or Koa, I think we'd be very open to feedback on whether such features are useful.

This is the specific blocker: https://github.com/reactjs/react-router/issues/1923#issuecomment-195439126.

I'd suggest we close this for now since it's something I believe we should not incorporate into the router at this point. I'd be open to re-opening and discussing again later if we get a ways down the road and find scenarios we just can't satisfy with our current route config, but I haven't seen any yet.

I think this is useful as a PoC for integrating with an external path-matching library. It's the most straightforward way to get customizable route parameters per https://github.com/reactjs/react-router/issues/2286, and is going to be familiar to users of Express, Rails, Nginx, Django, &c. This PR isn't mergeable as-is anyway; at this point it's just to demonstrate what would be involved code-wise.
We should figure out on the unreachable routes issue (https://github.com/reactjs/react-router/issues/1923 ) what we want to do there.

@taion Can you push the branch to the @reactjs repo? We can keep it around for possible revisitation in the future.

https://github.com/reactjs/react-router/tree/path-to-regexp
My opinion remains that unless we want to go with option 2 per https://github.com/reactjs/react-router/issues/1923#issuecomment-195439126, our presumption should be in favor of using the most common widely-adopted third-party library for doing our route matching.


Add a friendly 404 route/page

From @Tratcher on October 4, 2016 22:52
The web application (starter web) template does not have a friendly 404 experience, you end up with a blank page. There should be a default route/page with a simple message similar to the Error page.
Copied from original issue: aspnet/Templates#675

From @Tratcher on October 4, 2016 22:53
@rynowak

From @mlorbetske on October 6, 2016 17:45
@sayedihashimi can you take a look at this?

From @peterblazejewicz on October 5, 2016 19:27
https://github.com/h5bp/html5-boilerplate/blob/master/dist/404.html
https://github.com/h5bp/html5-boilerplate/blob/master/dist/404.html#L60
https://github.com/h5bp/html5-boilerplate/pull/1443#issuecomment-25915714
https://webmasters.googleblog.com/2008/08/make-your-404-pages-more-useful.html
https://blogs.msdn.microsoft.com/ieinternals/2010/08/18/friendly-http-error-pages/
hth

From @sayedihashimi on October 6, 2016 18:0
@Damianedwards any thoughts about what default content we want for a 404 page? If not I can work on a proposal and send it your way.

Closing because there are no plans to implement this.


Issue 43 - Need to account for already repaid amount in liquidations

Need to account for already repaid amount in liquidations
if a loan had already been partially repaid,  the pool WILL have more tokens, but the estimated value of the pool will not increase because we arent (we cant) include tokens repaid amount in the tool est value.  In this story, if the loan is normally repaid in full so there is no issue.
However, if a loan is repaid 95% but the remaining 5% is unpaid, then it goes into liquidation, this is more complex.
For example, if the loan auction is at a shortfall of $200 but the loan was previously partially repaid $1800 , the loan really isnt at a shortfall but it is up $1600 overall. SO that is how it should affect the accounting.  Before, we would account that it was a total shortfall of $200.

used TDD to help me improve and simplify this -  built 6 unit tests with different scenarios/stories
rebuilt some of the logic related to liquidations.   The amount taken from the liquidator is actually now the amount that remained unpaid  -- not the total loan amount.


Decode 433Mhz sensors of the existing alarm system

Decode 433Mhz sensors of the existing alarm system to use them in automations.
Related to: #18

Have you come across RTL_433? This might be possible to decode your sensors. I use this to sniff the data from my weather station unit.
https://github.com/merbanan/rtl_433

Have you come across RTL_433? This might be possible to decode your sensors. I use this to sniff the data from my weather station unit.
https://github.com/merbanan/rtl_433

That's actually great!
I should look into that and see if I can bring them in ;)


Improved Nsight Tooling

Description of changes

Adds supports for aarch64-linux for nsight host tools, also clean up the platforms meta information
Make it easier to override source for nsight_systems since Nvidia still hasn't included the x86_64 version in Jetpack 5.1 deb package
Fixed fonts issue where the applications don't render texts properly

Testing

x86_64 builds were tested on dev laptop
arm64 builds were tested on an Orin NX

We've chatted independently about a series of things to do to improve this, but that can be done in another PR.


Fix the "everything" tab on RssLogs

Wasn't working.

Coverage: 93.661% (-0.003%) from 93.663% when pulling 6f1f6b783c49d50e0fee6a1928f7bc5c5f37dd9b on nimmo-active-menu-items into 781af83a9fde68b001e0d23695c667cb7f7d8a3e on main.


'import sitecustomize' failed; use -v for traceback

From<EMAIL_ADDRESS>on 2013-03-12T13:57:41Z
I use Python 2.7 with IPython 0.13.1 and I just installed spyder-<IP_ADDRESS>.win32.
When I try to launch IPython interpreter I get this:
'import sitecustomize' failed; use -v for traceback
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
C:\Python27\lib\site-packages\spyderlib\widgets\externalshell\startup.py in <module>()
94         #      above (banner has to be shown afterwards)
95         #FIXME: Windows platforms: pylab/GUI loop support is not working
---> 96         ipythonshell.stdin_encoding = os.environ['SPYDER_ENCODING']
97         del banner2
98     except ImportError:
C:\Python27\lib\os.pyc in getitem(self, key)
421                 self.data[key.upper()] = item
422             def getitem(self, key):
--> 423                 return self.data[key.upper()]
424             try:
425                 unsetenv
KeyError: 'SPYDER_ENCODING'
Should I set anything prior trying to run IPython interpreter?
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1310

From pierre.raybaut on 2013-03-13T10:14:55Z
No, setting this environment variable is not required.
Please see issue #771 (especially the last comments).
It may be a side effect of the installation process (not Spyder's fault, but we could however take action on this if necessary).
Status: Duplicate
Mergedinto: 771

From<EMAIL_ADDRESS>on 2013-03-12T12:56:53Z
set SPYDER_ENCODING=utf-8
solves this, thou I can't see where is this mentioned.


Make onboarding checklist filterable for specific responsibilities

In order to easily generate incremental checklists that only reflect the minimal tasks a new team member is expected to perform to be ready to tackle a new responsibility in the team, we want a filterable set of onboarding tasks related to particular skills in our skills map
Acceptance Criteria

[ ] WHEN I select a subset of skills in the onboarding sheet of the cloud.gov skills map
THEN I see only the related new-starter/buddy tasks related to those skills
AND I can easily copy-and-paste those tasks into a GitHub issue checklist.

Implementation sketch

[x] Add Onboarding sheet.
[x] Enter all the existing onboarding/offboarding tasks and whether it's a mentor/mentee task.
[ ] Migrate each task from the legacy Onboarding Checklist to a row underneath the competency/skill it relates to.
[ ] Format every cell under all the people columns as checkboxes for all the filtered "onboarding task" rows.
[ ] Create a saved filter for each new person reflecting the skills they're onboarding into at the current time (starting with Ben).

Previously I said:

I'd like to return to this someday, but I don't think I'll be able to before we get a passel of new people joining, so I'm backlogging it.

..but @hillaryj has expressed some interest in taking this back up!


What features are expected for a fan?

I’ll all info later - but just wondering what is expected from the plugin?
My fan is in the supported list but all I am able to do is turn it off and on. No settings, oscillation or otherwise.
Just wondering if that is the expected behavior?

You should at least be able to control power + fan speed. If your fan supports oscillation it should also show those controls in the home app. What model do you have?

It’s the DR-HTF001S

oh.. I have NOT added homebridge to apple Home  -  if that makes a difference?

Reason for that is I want to add my Dreo to Home assistant

ok.. hmm.. so the plot thickens..
I added the homebridge & dreo to "home" on my Iphone.
Here the fan works as I had expected.. I can set speed, oscillation etc.
So in homebridge dashboard.. I still cannot.

removed it from apple home (deleted homebridge etc in docker) and added it to homeassistant.
in HA I can also only turn on fan and turn off.
only in Apple Home do I have the features shown in the plugin code frontpage.
Very strange.

added it to Home assistant.
If I open the fan entity then I also have all the options (fan speed, on/off, oscillation on/off.)

added it to Home assistant. If I open the fan entity then I also have all the options (fan speed, on/off, oscillation on/off.)

Hi - you mind explaining how you were able to achieve this?
I don't really understand how this "plugin" works & where it is being added. So from there to getting it on Home Assistant, I'm lost.
Appreciate any help

Hey
So how far did you get?

I have the fan + home assistant is set up.
Part of me thinks feels in order to add the plug in to Home Assistant, I need to add it as an Add-On through the Repository. Am I on to something?

You need homebridge .. fx running in docker.
https://hub.docker.com/r/oznu/homebridge/
Then that should be picked up by HomeKit controller integration in HA
In homebridge you add the dreo integration
HA will pick up the dreo AND the homebridge.
I didn’t add homebridge to HomeKit.. only dreo

I'm running into an issue where the fan shows up and I can turn it on/off and control the fan speed but I don't have an option to control oscillation unless I go into the fans additional settings, . My fan is supported (DR-HTF002S). Hopefully I'm just missing a setting and this is an easy problem to fix. attached are screenshots of what I'm talking about.

@azalvarez03 - same as mine. What is your expectation? What would you like to be different?

@Symbiot78 I'm looking to get the oscillation setting in the main settings rather than having to go into additional setting and flipping the toggle to turn oscillation on and off.

@Symbiot78 I'm looking to get the oscillation setting in the main settings rather than having to go into additional setting and flipping the toggle to turn oscillation on and off.

This is an iOS 17 beta issue. Homebridge exposes the controls to iOS and it's up to Apple to choose how they are displayed.


[example] Configure source-maps for React Render Tracker to open editor

This sets up React Render Tracker in the example to work for anyone.
@lahmatiy Do you think this is an acceptable generic solution that we can add to your README?

LGTM. However, keep in mind that this will work for VS Code users only.

LGTM. However, keep in mind that this will work for VS Code users only.

Fair point 👍  I guess for this example app I am going to make that assumption.


[ALLUXIO-2749] Make AlluxioWorkerInfoTest final

https://alluxio.atlassian.net/browse/ALLUXIO-2749

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15624/
Test FAILed.

@IMissSoMuch two comments left. Also, can you resolve conflict?


feat(circuits): circuit options using binary

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[x] Lint (yarn lint --check) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Closes #181
Closes #183
What is the new behavior?

This PR changes the public signal structure to encode many signals in a single signal. This is done by adding a constant number of constraints. In this PR the number of public signals in the epoch key proof is reduced by 2 while only adding ~10 constraints (a 0.3% increase). The reputation proof gains new functionality (prove max rep, prove 0 rep) while reducing the number of public signals by 3.
Both proofs now allow the epoch key nonce to optionally be revealed.
The proof classes have been moved from @unirep/contracts to @unirep/circuits so they can be used in the circuits tests.
Does this introduce a breaking change?

[x] Yes
[ ] No

Other information

@vivianjeng This is ready for review. Needs a few more tests but I think the strategy works. I moved the proof classes into the @unirep/circuits package so we can use them in the circuits tests.

Also needs updated docs

@vivianjeng I don't understand the other comments, could you explain more?

5d6be7e
Sure, these are mostly style changes in the tests. I try to avoid leaving too many style comments unless it's very hard to understand the control flow, or introduces bugs.


Add SECURITY.md file

Closes: https://github.com/oras-project/community/issues/11
This is the last one


Include init containers in calculation of pod resource requirements

Current calculation of pod resource requirements adds requests of all containers in pod. Kubernetes scheduler includes init containers in the pod in the calculation of resource allocation to the pod. Thus, mcad should also include init containers.

@atantawi can we close this issue now?


Changes for discussion to the PR Template

This PR is intended for discussion purposes.

@m-nash could you add .NET collaborators from the management plane team?

I like where we're landing -- I am wondering if we should put this into contributing.md as @heaths was mentioning and link to it from here? Thoughts?

I'd also like to see us try to come to some agreement about sign-offs. I know a lot of people like using "Add single comment" because they don't trust that uncommitted PR comments are saved. These appear as if someone made a single comment and resolved their PR review as merely "Comment". But how do PR authors know when they are done? They should either approve or request changes as their last review so we know when they are done. Otherwise, we're left here waiting a while to see if more come in, or have to ping them over Teams (if available) to ask and it becomes a big waste of time.

I'd also like to see us try to come to some agreement about sign-offs. I know a lot of people like using "Add single comment" because they don't trust that uncommitted PR comments are saved. These appear as if someone made a single comment and resolved their PR review as merely "Comment". But how do PR authors know when they are done? They should either approve or request changes as their last review so we know when they are done. Otherwise, we're left here waiting a while to see if more come in, or have to ping them over Teams (if available) to ask and it becomes a big waste of time.

Did you leave this as a single comment ironically? 😄
I agree, I think general PR comments should be avoided unless they are due to a general comment that applies to the whole PR like "this gemeral approach should be reconsidered".

Did you leave this as a single comment ironically? 😄

Let's just say it was a reminder. 😉

I agree, I think general PR comments should be avoided unless they are due to a general comment that applies to the whole PR like "this gemeral approach should be reconsidered".

Perhaps, but I've used this a few times where I didn't want to sign off one way or another because I was an area expert, but happened to notice a PR (or was asked to review) and had a few opinions. Moreover, I think just some way to signal "I'm done reviewing for now" is helpful to PR authors.


[rc2] Powershell commands do not work on csproj

The Package Manager Console powershell commands does not currently work on projects using csproj.
Issues:

[ ] OperationHandlers.cs does not compile. (Fix already in #5021 )
[ ] Cannot new-up a DbContext at design time due to "MissingMethodException" in MemoryCacheServiceCollectionExtensions

Repro
File -> New Project... (Console App)
Add this a simple dbcontext.
    public class TestContext : DbContext
    {
        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.UseSqlServer("Database=test;Server=(localdb)\\mssqllocaldb");
        }
    }

From PMC
Install-Package Microsoft.EntityFrameworkCore.SqlServer -Pre -Source https://www.nuget.org/F/aspnetcirelease/
Install-Package Microsoft.EntityFrameworkCore.Commands -Pre -Source https://www.nuget.org/F/aspnetcirelease/
Add-Migration FirstMigration

First error looks like
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: c:\Users\namc\Documents\Visual Studio 2015\Projects\ClassLibrary2\packages\Microsoft.EntityFrameworkCore.Commands.1.0.0-rc2-20529\tools\OperationHandlers.cs(35) : ; expected

c:\Users\namc\Documents\Visual Studio 2015\Projects\ClassLibrary2\packages\Microsoft.EntityFrameworkCore.Commands.1.0.0-rc2-20529\tools\OperationHandlers.cs(34) :

c:\Users\namc\Documents\Visual Studio 2015\Projects\ClassLibrary2\packages\Microsoft.EntityFrameworkCore.Commands.1.0.0-rc2-20529\tools\OperationHandlers.cs(35) : >>>         public virtual int Version => 0;

c:\Users\namc\Documents\Visual Studio 2015\Projects\ClassLibrary2\packages\Microsoft.EntityFrameworkCore.Commands.1.0.0-rc2-20529\tools\OperationHandlers.cs(36) :

When OperationHandler.cs is fixed, the error is:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.MissingMethodException: Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.DependencyInjection.MemoryCacheServiceCollectionExtensions.AddMemoryCache(Microsoft.Extensions.DependencyInjection.IServiceCollection)'.
   at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServiceCollectionExtensions.AddQuery(IServiceCollection serviceCollection)
   at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServiceCollectionExtensions.AddEntityFramework(IServiceCollection serviceCollection)
   at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.<>c__DisplayClass4_0.<GetOrAdd>b__1(Int64 k)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.GetOrAdd(IDbContextOptions options)
   at Microsoft.EntityFrameworkCore.DbContext..ctor(DbContextOptions options)
   at Microsoft.EntityFrameworkCore.DbContext..ctor()
   at ClassLibrary2.TestContext..ctor()
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.Activator.CreateInstance(Type type)
   at Microsoft.EntityFrameworkCore.Design.DbContextOperations.<>c__DisplayClass11_3.<FindContextTypes>b__13()
   at Microsoft.EntityFrameworkCore.Design.DbContextOperations.CreateContext(Func`1 factory)
   at Microsoft.EntityFrameworkCore.Design.DbContextOperations.CreateContext(String contextType)
   at Microsoft.EntityFrameworkCore.Design.MigrationsOperations.AddMigration(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigrationImpl(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigration.<>c__DisplayClass0_1.<.ctor>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)

cc @divega

Additionally, on VS15 I get this:
System.Management.Automation.MethodInvocationException:
  Exception calling "CreateDomain" with "3" argument(s): "The domain manager specified by the host could not be instantiated." --->
  System.TypeLoadException: The domain manager specified by the host could not be instantiated. --->
  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Platform.AppDomainManager, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Activator.CreateInstance(String assemblyString, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(String assemblyName, String typeName)
   at System.AppDomain.CreateInstance(String assemblyName, String typeName)
   at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
   at System.AppDomain.CreateAppDomainManager()
   --- End of inner exception stack trace ---
   at System.AppDomain.CreateAppDomainManager()
   at System.AppDomain.Setup(Object arg)
   at System.AppDomain.nCreateDomain(String friendlyName, AppDomainSetup setup, Evidence providedSecurityInfo, Evidence creatorsSecurityInfo, IntPtr parentSecurityDescriptor)
   at System.AppDomainManager.CreateDomainHelper(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
   at System.AppDomainManager.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
   at System.AppDomain.InternalCreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
   at System.AppDomain.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)

With VS2015, on a csproj, build 1.0.0-rc3-20540, Add-Migration does work with the changes to OperationHandlers.cs

@BradBarnich thanks for sharing. What happens if you try RC2 bits? Install from https://www.nuget.org/F/aspnetcirelease/

@natemcmaster used 1.0.0-rc2-20539, same result. With the fixes to OperationHandlers.cs, VS2015 works and VS15 does not.

@BradBarnich the issue you are seeing in VS15 Preview is the likely the same issue added here: https://github.com/NuGet/Home/issues/2162. As you'll see, the issue was closed because it is a bug in VS itself.

Update: with fixes to OperationHandler.cs, the error does not reproduce on all machines. I tried on a clean install of VS2015.

Closed via #5037


ASA prompt checking

Hello, netdev execution fails in case ASA is configured with non-default prompt. Like "(config)# prompt hostname priority state". There is a small fix which is not ideal, but helps to avoid exceptions in some longer prompts.
    prompt = await self._find_prompt()
    context = 'system'
    # Cut off prompt from "prompt/context"
    splitted_prompt = prompt[:-1].split('/')
    # In case prompt is "hostname/context"
    if len(splitted_prompt) == 2:
        prompt = splitted_prompt[0]
        context = splitted_prompt[1]
    # In other cases like "hostname" or "hostname/priority/state" or whatever else
    else:
        prompt = splitted_prompt[0]
    self._base_prompt = prompt
    self._current_context = context
    delimiters = map(re.escape, type(self)._delimiter_list)

After that fix module works like a charm for me!
Thank you very much for your project.

@romankuchin  Hello! Thank you for your report! I never think about changing prompt with command prompt. I find out that it has several params:
configure mode commands/options:
  cluster-unit     Display the cluster unit name in the session prompt
  context          Display the context in the session prompt (multimode only)
  domain           Display the domain in the session prompt
  hostname         Display the hostname in the session prompt
  management-mode  Display management mode
  priority         Display the priority in the session prompt
  state            Display the traffic passing state in the session prompt

So it can consist more than 3 part with '/' separator. I think that we can omit it all in the _set_base_prompt function except first part (it is usually hostname in the most cases).
I will release new code for ASA in several days after some testing :)

@romankuchin Hello! I changed this code for working with your case. Now it should just work without any workarounds. Can you test it in your environment?

Thank you for submitting successful work!


Improve formatting of draws table

This rounds to 6 digits and makes it so that resizing the tab doesn't lead to very skinny columns that wrap.
Before:

After:

Not sure if there is a good way to avoid the treedepth column (which is integer-valued) from getting all the .00000s -- @jsoules?
A very-JS suggestion I've seen online is "divide by 1 afterwards", which 1. makes TSC unhappy, but 2. does seem to work, hilariously

Not sure if there is a good way to avoid the treedepth column (which is integer-valued) from getting all the .00000s -- @jsoules?
A very-JS suggestion I've seen online is "divide by 1 afterwards", which 1. makes TSC unhappy, but 2. does seem to work, hilariously

It's JavaScript, of course it makes no sense and yet works!
So a couple options here, but they're going to involve writing a helper function. Question is just what that helper function would look like. One solution would be to check if the number is an integer (or within tolerance of an integer) and if so don't do the toPrecision call. You could also do some postprocessing on the string to trim right-hand-side zeroes, up to and including a decimal point if any; could result in ragged numbers depending on the situation...

How about detecting whether it's an integer column, and then using a different format function. It will give approximately the same result as having the conditional inside the format function... but I think it's more correct in the rare case where you have a mix of integers and non-integers in the same column.

Looks good to me


Fixed indexing error in SolrClient

The non-json indexing function was calling itself infinitely.

Already fixed: https://github.com/moonlitesolutions/SolrClient/blob/dev/SolrClient/solrclient.py#L144


Fix istio-ingress dashboard

How to categorize this PR?

/area networking
/area monitoring
/kind bug
What this PR does / why we need it:
Fix istio-ingress dashboard.
The graph for sent tcp traffic used the incorrect metric.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Istio-ingress gateway dashboard now shows the correct sent tcp traffic metric.

/cc @DockToFuture @axel7born

/lgtm


Disable test/stdlib/ErrorBridgedStatic.swift on no_asserts builds

For some reason this test fails on the bots.
I could not reproduce the failure locally.
rdar://39473208

@swift-ci Please smoke test and merge


Use the passed-in state instead of calling getBlockState

Fixes Aang23/UndergroundBiomesConstructs#3 and probably some other bugs I don't know about. Is also a tiny performance win.

Thanks!

Would you mind pushing a new build to curse then?

I did provide a workaround in UBC too.

New build out tonight ;)

Perfect ! Thanks.
I think the I'll let the fix in for something like 2 weeks in case some peoples takes time to update.

New build out tonight ;)

Great. :D

Awesome!


packagegroup-onl-platform-*: set arch

All referenced packages are arch-specific, so it does not make sense for the packagegroups themselves to be generic.

I am curious: when or where will this make a difference?

Currently it does not, but if we may decide in the future to have a shared opkg repository (because e.g. all packages are sharable), both would appear e.g. in http://repo.bisdn.de/pub/onie/generic-x86-64/packages-v5.1.0/ipk/all/ but e.g. the arm variant would appear in opkg, but be uninstallable in x86 and vice versa.


Global code search "View File" link broken

Gitea version (or commit ref): 1.14.0
Git version:
Operating system: 1.14 docker image (a491dc1f1e69) on linux amd64

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No since REPO_INDEXER_ENABLED seems to be disabled

Log gist:

Description

When using Code Search the "View File" link adds the organisation/repo path after the already existing one ending up with a broken 404 link like: https://foo.bar/test/repo/test/repo/src/commit/<hash>/README.md instead of https://foo.bar/test/repo/src/commit/<hash>/README.md.
Steps to Reproduce

Create a new Gitea Instance (I used Docker) and set REPO_INDEXER_ENABLED=true in the  app.ini file.
Create an Organisation and a repository
Commit a file to the repository
Search for some content in the file and press "View File"

This seems to only affect the repository code search (/orga/repo/search?q=foo) and not the explore code search (/explore/code).


Something wrong with new model generating 128 embeddings?

Hi @davidsandberg,
Thanks for sharing the new model that generates 128 embeddings.
I am already testing it and there is something that is puzzling me: is it possible that somehow this new model only provides meaningful embeddings for images that are forward-passed in the same sess.run execution? If I run a batch process calling sess.run multiple times (say with one face at a time), the embeddings are so close to each other that the euclidean distance between different faces is 0.0000006 or so, and the accuracy is simply not good. If I pass those faces in the same sess.run in the images_placeholder input array (as in the example in compare.py), then the embeddings make sense and the distances are much greater.
I guess I am doing something wrong, but I just don't seem to see what it is exactly. You can reproduce what I describe if you do the following in compare.py:
Instead of:
feed_dict = { images_placeholder: images, phase_train_placeholder:False }
emb = sess.run(embeddings, feed_dict=feed_dict)

This:
emb = np.zeros((nrof_images, 128))
for i in range(nrof_images):
        npimages = np.stack([images[i]])
        feed_dict = { images_placeholder: npimages, phase_train_placeholder:False }
        emb[i, :]  = sess.run(embeddings, feed_dict=feed_dict)

The result is that the distance matrix is 0.0000 in all cases.
Any ideas?

Hi @dleonsanchez,
Thanks for spotting this!!!
I believe this is caused by the batch norm for the bottleneck layer always being in training mode.
it should be possible to fix by setting the parameter is_training, something like this:
        batch_norm_params = {
            # Decay for the moving averages.
            'decay': 0.995,
            # epsilon to prevent 0s in variance.
            'epsilon': 0.001,
            # force in-place updates of mean and variance estimates
            'updates_collections': None,
            # Moving averages ends up in the trainable variables collection
            'variables_collections': [ tf.GraphKeys.TRAINABLE_VARIABLES ],
            # Only update statistics during training mode
            'is_training': phase_train_placeholder
        }

I haven't tested this yet though.

I've tested @davidsandberg's method, and it solved the problem.
Thanks for the hint.

@ugtony can you please elaborate on how you fixed it?
I seem to be spinning my wheels here
Thank you very much

@RakshakTalwar,
First, I modified facenet_train_classifier.py as what davidsandberg's had suggested.
And then I used that script to save the model after the preload_model was restored.
The script for test time was kept unchanged.
I think it is also possible to directly manipulate the graph after import_meta_graph(), but it's more difficult for me to do that.

@ugtony Thank you so much I literally spent last 4 hours wondering why none of the results made any sense, there were surely bugs in my code like cropping instead of scaling, not whitening in same manner, but eventually it wouldn't work in spite of having a complete blank image. As soon as I changed model files with the link you provided it worked beautifully!

@AKSHAYUBHAT
You're welcome.
I was also checking cropping, resizing, and whitening as you did. And then this opened issue came to my head and solved my problem. Thank dleonsanchez 's question and davidsandberg 's solution that saved my time.

Thanks @ugtony etc!
I committed this fix and updated the meta files for the pretrained models. I hope it works...


Perception packages support CUDA 11.4 and TensorRT 8.2.2

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Perception packages are ported from https://github.com/tier4/AutowareArchitectureProposal.iv and some of them depend on CUDA 11.1 and TensorRT 7.2.1, but https://github.com/autowarefoundation/autoware requires CUDA 11.4 and TensorRT 8.2.2.
Therefore, the packages below should be checked to work.

[x] traffic_light_ssd_fine_detector
[x] traffic_light_classifier
[x] lidar_centerpoint
[x] tensorrt_yolo
[x] lidar_apollo_instance_segmentation

Purpose
The perception packages work on the https://github.com/autowarefoundation/autoware environement.
Possible approaches
If necessary, refer to https://github.com/tier4/tensorrt_common to switch the TensorRT version.
Definition of done
The packages are checked to work on both versions.

I confirmed lidar_centerpoint works. https://github.com/autowarefoundation/autoware.universe/issues/643#issuecomment-1090090877

apollo

yolo

traffic light

Thank you! :clap:

We checked for the packages to work, so close this issue.


Set minimum PyTorch version to 1.6

What does this PR do?
See title.
TODO: Make sure the "Current build statuses" table in the README is correct

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[n/a] Did you write any new necessary tests? (not for typos and docs)
[n/a] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hey @ananthsub,
Would you mind to validate there is no specific reason for us to keep supporting 1.4 and 1.5 ?
Best,
T.C

Hey @ananthsub,
Would you mind to validate there is no specific reason for Lightning to keep supporting 1.4 and 1.5 ?
Best,
T.C

As discussed today, this is primarily motivated by how long the backward-compatibility window ought to be. Users can always pin themselves to older versions of Lightning if they absolutely need older PyTorch support. Given how stable the PyTorch API has been, there's less risk of breaking changes across these versions that Lightning needs to cover for. However there are a ton of features users will get with both PyTorch and Lightning by updating to recent versions. Plus CI time/$ savings for contributors, but this is a minor concern compared to user adoption.
@carmocca @Borda if you want to be more conservative, we could start with not supporting PyTorch v1.4, see how the community receives this, and then determine if this is a pattern we can continue for the next releases (e.g. always support the latest N releases of PyTorch, or PyTorch versions within last T time).

I may say that with adding support for future PT 1.10 #8133 we can do a bit bigger step and drop also PT 1.5 for the upcoming PL 1.4

we could start with not supporting PyTorch v1.4, see how the community receives this

I may say that with adding support for future PT 1.10 #8133 we can do a bit bigger step and drop also PT 1.5 for the upcoming PL 1.4 (so we would have still 5 minor PT support)

Yes, I think it is a good approach.


Mixing implicit and explicit wait

Hi there,
it seems in pytest-splinter it is not possible to disable implicit wait (see here https://github.com/pytest-dev/pytest-splinter/blob/5522d59fcabfa8904385c1e10ca61460a25193e0/pytest_splinter/plugin.py#L596)
but the issue is that if I want to use an explicit wait (pytest-splinter allow this) it will result in mixing explicit (the one I define) and implicit wait and this can take to strange waits behaviour (see: https://octopus.com/blog/selenium/8-mixing-waits/mixing-waits).
How to address this issue or disable implicit wait?

Hi @jobezic I had a quick glance at the plugin (in work atm), the default is None, so it will only be applied I assume if you explicitly pass such value on the CLI? - I only took a very quick skim mind you.

Hi @jobezic I had a quick glance at the plugin (in work atm), the default is None, so it will only be applied I assume if you explicitly pass such value on the CLI? - I only took a very quick skim mind you.

you can override a fixture / set the option to have implicit wait timeout be 0, which should effectively disable implicit wait

you can override a fixture / set the option to have implicit wait timeout be 0, which should effectively disable implicit wait

@jobezic was the problem solved? Do you need any more assistance?


Revise __WD_EscapeString to further encode strings

Pull request
Proposed changes
Use Json_StringEncode to perform string encoding. Also support stripping tabs and CR/LFs
Checklist
Put an x in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!
This is simply a reminder of what we are going to look for before merging your code.

[x] I have read and noticed the CODE OF CONDUCT document
[x] I have read and noticed the CONTRIBUTING document
[ ] I have added necessary documentation or screenshots (if appropriate)

Types of changes
Please check x the type of change your PR introduces:

[ ] Bugfix (change which fixes an issue)
[ ] Feature (change which adds functionality)
[ ] Code style update (formatting, renaming)
[x] Refactoring (functional, structural)
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
Please describe the current behavior that you are modifying, or link to a relevant issue.
What is the new behavior?
See #465
Additional context
Add any other context about the problem here.
System under test
Please complete the following information.

OS: [e.g. Windows 10]
OS Arch.: [e.g. X64]
Browser [e.g. firefox]
Browser version [e.g. 96.0.3]

Will look deeply this weekend

According to https://github.com/Danp2/au3WebDriver/issues/466
https://github.com/Danp2/au3WebDriver/blob/8340123db20a3bcb684f153dc29a8630eadab41d/wd_helper.au3#L2611-L2617
This line
https://github.com/Danp2/au3WebDriver/blob/8340123db20a3bcb684f153dc29a8630eadab41d/wd_helper.au3#L2617
should be changed to:
$sResult = _WD_ExecuteScript($sSession, $sScript, __WD_JsonElement($sElement) & ',"' & __WD_EscapeString($sValue) & '"')

_WD_Storage() SET should be checked if $vValue should be escaped
_WD_Storage() GET should be checked if $vResult should be de escaped with Json_StringDecode()

@mlipok Discussion on _WD_Storage doesn't belong in this PR. Feel free to submit a separate issue or a PR with suggested changes.

the last thing to consider is:

According to #466
https://github.com/Danp2/au3WebDriver/blob/8340123db20a3bcb684f153dc29a8630eadab41d/wd_helper.au3#L2611-L2617

after which I think this is fine and could be merged.

@mlipok Again, separate issue that would be handled, if needed, as a separate PR.

So here I'm fine with this PR


Click and mouseover can not be triggered at transparent area

let app = new PIXI.Application(800, 600);
document.body.appendChild(app.view);

app.stage.interactive = true;
app.stage.on('click', () => {
    console.log('CLICKED');
})
app.stage.on('pointerdown', () => {
    console.log('POINTER DOWN');
})

Expect
Events are triggered when click stage.
Actual
Nothing happen

It is strange...
let app = new PIXI.Application(800, 600);
document.body.appendChild(app.view);

app.stage.interactive = true;
app.stage.buttonMode = true;
app.stage.addChild(PIXI.Sprite.fromImage('http://pixijs.io/examples/required/assets/BGrotate.jpg'))
app.stage.on('click', () => {
    console.log('CLICKED');
})
app.stage.on('pointerdown', () => {
    console.log('POINTER DOWN');
})

Event I add a Image, not every part of the image can trigger click and pointerdown.

Finnally I found that is because I have another  in html file, which is cover on stage.


Added "withSearchBar" navbar example. Also fixes #63

The transition from desktop to mobile is simply phenomenal. Congratulations!


Update Composer dependencies (2021-12-04-00-04)

Visual regression test passed!
View the visual regression test report


Added support for customizing container apps in ACA via the CDK

Description

Added Aspire.Hosting.Azure.ContainerApps. This exposes 3 APIs used to configure and customize container app resources.
Added deployment target support to project and container resources in the manifest writer. This allows developers to express that a project/container gets deployed using the nested resource type. This requires a branch of azd to wire up and test.

Fixes #5179
Relies on https://github.com/Azure/azure-dev/pull/4286 in azd for making deployment work.
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[x] Yes
[ ] No

Did you add public API?

[x] Yes

If yes, did you have an API Review for it?

[ ] Yes
[x] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[x] Yes
[x] No

[ ] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[x] Yes

Link to aspire-docs issue:

[ ] No

Microsoft Reviewers: Open in CodeFlow

/azp run

Should we additionally wait for Job host started in https://github.com/radical/aspire/blob/e2830042b191c9f0239c1c69fc477c2a60d5dd72/tests/Aspire.Playground.Tests/ProjectSpecificTests.cs#L70-L77 ? I think there might be a slight race here in when MyAzureBlobTrigger: blobTrigger appears vs Job host started. And we end up getting connection refused because are not using http resilience on the client either (right?).

Should we additionally wait for Job host started in https://github.com/radical/aspire/blob/e2830042b191c9f0239c1c69fc477c2a60d5dd72/tests/Aspire.Playground.Tests/ProjectSpecificTests.cs#L70-L77 ? I think there might be a slight race here in when MyAzureBlobTrigger: blobTrigger appears vs Job host started.

Yep, this is a good hunch. We could add a check for the Job host started to see if that helps stabilize the tests.

Retries will probably make it more stable.


fix: parse XDR Result to JSON; encode RawVal return types

What
Two new tests show some errors that revealed themselves while adding CLI tests:

the errors example showed that valid Ok results were not being correctly parsed to JSON
the deployer example showed that RawVal return types were causing errors

Why
These tests expose real problems that have existed in soroban-cli's main branch since updating to the latest XDR definitions
Known limitations
N/A

The reason that we we used both was for the UDT cases. That is JSON -> ScVal for Enums and Structs differs than if we use ScVal  -> JSON


Inotify: invalid post occuring at shutdown.

Got rid of the use of iostream in internal thread.

Split into two commits and merged in [e19168e]


Tensorflow CUDA A100 compatibility issue

Click to expand!
Issue Type
Support
Source
binary
Tensorflow Version
tensorflow-gpu==1.12.0
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 16.04
Mobile device
No response
Python version
3.7
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
Nvidia A100
Current Behaviour?
The compatibility table given in the tensorflow site does not contain specific minor versions for cuda and cuDNN. However, if the specific versions are not met, there is an compatibility error when I try to use tensorflow. For example for, tensorflow-gpu==1.12.0 and cuda==9.0, the compatible cuDNN version is 7.1.4 and if I have A100, tensorflow is not compatible. I can use them on a V100 GPU but not on A100 GPU.

Standalone code to reproduce the issue
pip install --upgrade pip
pip install tensorflow-gpu==1.12.0

Relevant log output
No response

Hi @Debby123 !
1.x versions are not supported anymore.
Could you test latest instructions from latest build/install document (It suggests Installing necessary Cuda toolkits according to hardware according to conda channels now  instead of setting path manually).
Please check the tested the configs if you want to build from source.
Thank you!

Hi @mohantym,
I was trying to reproduce some research code that uses tf 1.x version. Although I tried using the latest build, there were code incompatibilities.  Anyway, I reckon I will have to rewrite the code as per the latest builds.
Thank you for looking into this!


add 2 new artifact effects

About the PR
artifacts get 2 new types of effects:
Spiral Attraction and Spiral Repulsion.
Media
https://github.com/space-wizards/space-station-14/assets/96445749/a9125e6b-8859-4ceb-90b9-c3f8fc92354a

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Added 2 new artifact effect: attraction and repulsion

Make both of these more common. These could very much just be t1 or t2.

Done

14 minute speedrun

god bless TheShuEd