[move-prover] Added spec for Coin1

I wanted to see how far I could get with proving that only the
treasury compliance account can mint Coin1.
Unfortunately, I was able to prove it when it's not true! The problem
is a generic function in another module that can invalidate the invariant.
In the process, I changed spec_has_..._role functions in Roles.move to
take addresses instead of signers as arguments, because it seems to be
more appropriate in specifications.  The corresponding Move functions
all take signers as arguments, which has not been a problem, so far.

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

:umbrella: The latest upstream changes (presumably b2521e2061759e63786dc486b57d66262fdf2f78) made this pull request unmergeable. Please resolve the merge conflicts.

Is this still up for review?


Static content in virtual directory does not work (404 Error)

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am running the latest version of Nancy
[x] I have verified if the problem exist in both DEBUG and RELEASE mode
[x] I have searched open and closed issues to ensure it has not already been reported

Description
I have a Nancy Webservice on a IIS 8 webserver. On the server, the website lies in c:\inetpub\wwwroot\. Also, there is a subfolder \Content with static content (js, css, img, ...).
Due to space constraints, I want to put parts of my static content to the d drive: d:\inetpubd\wwwroot\.
Therefore, I added a virtual directory to the website in IIS mapping d to d:\inetpubd\wwwroot\ (I haven't added the virtual directory in my Visual Studio project since I don't know how to do that).
This works partly fine, e.g. when I use HttpContext.Current.Server.MapPath("~/d/file.html"), I get correctly the string d:\inetpubd\wwwroot\file.html. Also, I can read this file with File.ReadAllText().
What does not work is to include this virtual folder as a static content folder. For that, I would do in the bootstrapper:
protected override void ConfigureConventions(NancyConventions conv)
{
    base.ConfigureConventions(conv);
    // static folders
    conv.StaticContentsConventions.Add(StaticContentConventionBuilder.AddDirectory("/d"));
}

I would now expect to access e.g. the file http://webpage.net/d/file.html and get it returned as a static file. But I get a 404 Error File Not Found.
How can I include virtual directories outside of the webpage source folder in Nancy? What did I overlook?
Note that the file file.html is not available during compile time, but during runtime. I think this should not make a difference.

Nancy's static content stuff works with physical files and folders, so it won't support IIS's "virtual paths" as they are purely an IIS request->file mapping thing. There's two ways I can think of for you to get around this, either disable Nancy for the static content path you're using, and allow IIS to manage it (you can see examples of adding modules/removing modules and specifying paths in the docs here: https://github.com/NancyFx/Nancy/wiki/Hosting-Nancy-with-asp.net, you basically want to remove nancy from that specific path), or create a symbolic link/junction point using MKLINK to create a "physical file system" connection between c:\inetpub\wwwroot\content to d:\inetpub\wwwroot\content.


#1557

Data Import: make file field read only and switch to message box error reporting
And proper grid styling

:+1:


Add news feed broadcast or update for default newsfeed module

Does the pull request solve a related issue?
Nope.

What does the pull request accomplish? Use a list if needed.
Using the default newsfeed module, it can now broadcast news feed items to other modules, alternatively broadcast only news feed updates.

A minor feature, yet it is something useful.

Travis build failed due to incorrect spacing, spaces used rather than tabs

Will submit new PR will fixes, closing current PR.


Integrate Custom Authentication Provider

I have an existing web service from a legacy system that is used for authentication and it also provides some additional user based information as part of the response.
I would like to know the following

Can UAA be configured to use an existing authentication service ?
Does UAA provide options to capture this additional information returned in the response and return the additional information through /userinfo endpoint or even encode it within the JWT?

UAA supports only LDAP/SAML/OIDC based IDPs.
The best is to create a SHIM layer in-front of the legacy system and enable OIDC IDP.
Yes, UAA supports /userinfo and user claims in JWT for all supported IDPs


ENH: Add zolltools.db.verify module to verify correct installation

Problem
Hard to check on a new device is all files have been installed correctly.
Solution
Simple command line tool to check that all files are downloaded
Tasks

[ ] Create a .pkl file with expected metadata for each .parquet file in the NEMSIS database
[ ] Include the data file in the package
[ ] Write the command line tool to read this data and compare it with the local installation

This is too fancy. Not worth the effort.


Addons (Angular2)

How can I use text-mask-addons with Angular2?
I'm following this instructions to use createNumberMask as below:

npm i text-mask-addons --save

(everything is fine with the installation)
And the code:
import createNumberMask from 'text-mask-addons/dist/createNumberMask.js'

const numberMask = createNumberMask({
  prefix: '',
  suffix: ' $' // This will put the dollar sign at the end, with a space.
})

But I'm getting an error message:

TypeScript error TS2307: Cannot find module 'text-mask-addons/dist/createNumberMask.js'.

Any guess?

Ah, I think I need to create TypeScript definitions for those? I'll get to it this weekend. Thanks for the report.

Yes, I think so. I didn't realize that d.ts was missing.
Thanks for your help.

@rafael-iop I published<EMAIL_ADDRESS>which should contain addons that are importable by TypeScript now.

I know this is marked as closed, but I took a look at the d.ts files and they are not typescript definition files.  They merely have:
declare var foo: any
export default foo
When I try to use these I cannot get them to work. Was this actually fixed?
I get this error: error TS2307: Cannot find module 'text-mask-addons'.
I'm using Angular 2.1.0 if that helps.  Overall text-mask is a really needed library for angular2 so I hope we can make this work.  My biggest interest is using the createAutoCorrectedDatePipe.  I already have the angular2-text-mask working, its just the add ons that are giving me a problem.
Thanks!

We just published an update to the addons which has broken the autoCorrectedDatePipe for TypeScript. I'll push a fix within the next couple of hours. Thanks for reporting this!

@jebright I just published the fix.
Make sure you have the latest addons package installed<EMAIL_ADDRESS>and then import and use autoCorrectedDatePipe as follows:
import createAutoCorrectedDatePipe from 'text-mask-addons/dist/createAutoCorrectedDatePipe.js'

const autoCorrectedDatePipe = createAutoCorrectedDatePipe('mm/dd/yyyy')
// As you can see in the line above, you can pass a string argument to `createAutoCorrectedDatePipe`
// to give it the order of day, month, and year in your `mask`.

// ...now you can pass `autoCorrectedDatePipe` to the Text Mask component as the `pipe`

@msafi , thank you for the assistance.  I got this to work now.  Pretty cool!  Here are the relevant steps in case that helps anyone else:
First, I put this in the relevant sections of my systemjs.config.js file:
map: { 	... 	'angular2-text-mask': 'npm:angular2-text-mask/dist', 	'text-mask-addons': 'npm:text-mask-addons' },
packages: { 	... 	'angular2-text-mask': { main: 'angular2TextMask.js', defaultExtension: 'js' }, 	'text-mask-addons': { defaultExtension: 'js' } }
Next, I included these lines in my angular component:
import { TextMaskModule, MaskedInputDirective } from 'angular2-text-mask';
import createAutoCorrectedDatePipe from 'text-mask-addons/dist/createAutoCorrectedDatePipe';
public get dateMask(): any { 	return [/\d/, /\d/, '/', /\d/, /\d/, '/', /\d/, /\d/, /\d/, /\d/]; }
public get autoCorrectedDatePipe(): any { 	return createAutoCorrectedDatePipe('mm/dd/yyyy'); }
And this markup in my html template:
<input type="text" class="form-control" name="dob" id="dob" [(ngModel)]="customer.dob" #dob="ngModel"  [textMask]="{mask: dateMask, guide: false, keepCharPositions: true,  pipe: autoCorrectedDatePipe}" required />

As @jebright commented on 15 Oct:

took a look at the d.ts files and they are not typescript definition files. They merely have:
declare var foo: any
export default foo
This is happening with the newest version (2.0.0)


build: publish package to pypi

Coverage report

This PR does not seem to contain any modification to coverable code.


Emit time-to-render event after first render without skeleton elements

Reason for change
This change emits a manifold-time-to-render event after a <manifold-*> component's first render without skeleton elements. This represents the first "meaningful" render after data loads and the component is displaying useful information.
To start the time-to-render lifecycle, I'm relying on a mutation observer set up in <manifold-performance> to monitor the subtree for any added nodes that start with manifold-. When a new node is added, a data-start attribute is added to that node to represent the initialization time.
To monitor the end of the time-to-render lifecycle, I'm relying on the existing logger decorator that is required on all our elements. I've altered the decorator to examine the rendered output for skeleton elements, and if none exist, I add a data-end attribute to the element and emit the event. This part relies on the component being measured to have @Element() el: HTMLElement; in the component definition. I'll be seeking advice on making that a required part of our components by lint rule.
TODO in followup PRs:

Observe subtree additions within shadowRoots. Currently when a component has a shadowRoot the mutation observer can't observe within the shadow DOM. A follow up is needed to attach those shadowRoot components to the observer (or something like that, if I knew exactly what to do I'd just do it).
The lint rule mentioned above

Testing
The component rendered in the Performance story in Storybook should now log the manifold-time-to-render event to DataDog
Checklist

[x] CHANGELOG: The Unreleased section of CHANGELOG was updated
[ ] Prop changes: docs were updated
[ ] Prop changes: E2E tests were updated, testing from the highest level possible
[ ] Platform testing: If this change should be tested against a platform, has it been?

This is so cool! 🎉

@sslotsky Is it fair to say that any component that does load data does it in componentWillLoad? If so, that's a simplification I'm happy with. We never load our data in connectedCallback for example?
Also, do we have any components where render time could be negatively affected by anything other than async data?


Bug: Images in some One Drive folders won't load the first time

Description
All the images in my music library folder in One Drive would show the preview pane like the screenshot on the left when I clicked on it first time, and if I click on another item and back to this one it shows normally like the screenshot on the right.

Additional info:

The Pictures folder in my One Drive doesn't have this issue.
The Pictures folder is ~400 MB and music folder is ~150 GB in size.
So I did a test and copy an image from the Pictures folder to another folder that's ~27 GB, and it didn't load the first time either.

Steps To Reproduce

Find an image in a fairly large folder in One Drive that's haven't been clicked yet
Click on it, and its image should not load in the preview pane
Click on anotehr item and click it again, it should show the image this time

Requirements

Make it load the first time I click on it, the same way when I click on a image in a smaller folder in One Drive or a local folder of any size.

Files Version
3.0.3
Windows Version
10.0.22631.2506
Log File
debug.log

Thanks for the feedback, I updated the title because this issue affects more than the just preview pane.

We're going to continue tracking this in #14437


[BEAM-11408, BEAM-11772] Add explicit output typehints to ensure coder determinism for BQ with auto-sharding

Also fix the string representation of ShardedKeyCoder to print out the key coder.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @udim

retest this please


FITC method for GPflow

This is not ready to merge yet. Rather it is a "help wanted" PR for @jameshensman to look at.
I working from Carl and Hannes' GPML code:
function [post nlZ dnlZ] = infFITC(hyp, mean, cov, lik, x, y)

% FITC approximation to the posterior Gaussian process. The function is
% equivalent to infExact with the covariance function:
%   Kt = Q + G; G = diag(g); g = diag(K-Q);  Q = Ku'*inv(Quu)*Ku;
% where Ku and Kuu are covariances w.r.t. to inducing inputs xu, snu2 = sn2/1e6
% is the noise of the inducing inputs and Quu = Kuu + snu2*eye(nu).
% We fixed the standard deviation of the inducing inputs snu to be a one per mil
% of the measurement noise's standard deviation sn.
% The implementation exploits the Woodbury matrix identity
%   inv(Kt) = inv(G) - inv(G)*V'*inv(eye(nu)+V*inv(G)*V')*V*inv(G)
% in order to be applicable to large datasets. The computational complexity
% is O(n nu^2) where n is the number of data points x and nu the number of
% inducing inputs in xu.
%
% The function takes a specified covariance function (see covFunction.m) and
% likelihood function (see likFunction.m), and is designed to be used with
% gp.m and in conjunction with covFITC and likGauss.
%
% The inducing points can be specified through 1) the 2nd covFITC parameter or
% by 2) providing a hyp.xu hyperparameters. Note that 2) has priority over 1).
% In case 2) is provided and derivatives dnlZ are requested, there will also be
% a dnlZ.xu field allowing to optimise w.r.t. to the inducing points xu. However
% the derivatives dnlZ.xu can only be computed for one of the following eight
% covariance functions: cov{Matern|PP|RQ|SE}{iso|ard}.
%
% Copyright (c) by Ed Snelson, Carl Edward Rasmussen
%                                               and Hannes Nickisch, 2013-10-28.
%
% See also INFMETHODS.M, COVFITC.M.

if iscell(lik), likstr = lik{1}; else likstr = lik; end
if ~ischar(likstr), likstr = func2str(likstr); end
if ~strcmp(likstr,'likGauss')               % NOTE: no explicit call to likGauss
  error('Inference with inFITC only possible with Gaussian likelihood.');
end
cov1 = cov{1}; if isa(cov1, 'function_handle'), cov1 = func2str(cov1); end
if ~strcmp(cov1,'covFITC'); error('Only covFITC supported.'), end    % check cov
if isfield(hyp,'xu'), cov{3} = hyp.xu; end  % hyp.xu is provided, replace cov{3}

[diagK,Kuu,Ku] = feval(cov{:}, hyp.cov, x);         % evaluate covariance matrix
m = feval(mean{:}, hyp.mean, x);                          % evaluate mean vector
[n, D] = size(x); nu = size(Kuu,1);
cov{3} = reshape(cov{3},[],D);

sn2  = exp(2*hyp.lik);                              % noise variance of likGauss
snu2 = 1e-6*sn2;                              % hard coded inducing inputs noise
Luu  = chol(Kuu+snu2*eye(nu));                         % Kuu + snu2*I = Luu'*Luu
V  = Luu'\Ku;                                     % V = inv(Luu')*Ku => V'*V = Q
g_sn2 = diagK + sn2 - sum(V.*V,1)';          % g + sn2 = diag(K) + sn2 - diag(Q)
Lu = chol(eye(nu) + (V./repmat(g_sn2',nu,1))*V');  % Lu'*Lu=I+V*diag(1/g_sn2)*V'
r  = (y-m)./sqrt(g_sn2);
be = Lu'\(V*(r./sqrt(g_sn2)));
iKuu = solve_chol(Luu,eye(nu));                       % inv(Kuu + snu2*I) = iKuu
post.alpha = Luu\(Lu\be);                      % return the posterior parameters
post.L  = solve_chol(Lu*Luu,eye(nu)) - iKuu;                    % Sigma-inv(Kuu)
post.sW = ones(n,1)/sqrt(sn2);           % unused for FITC prediction  with gp.m

if nargout>1                                % do we want the marginal likelihood
  nlZ = sum(log(diag(Lu))) + (sum(log(g_sn2)) + n*log(2*pi) + r'*r - be'*be)/2;
  if nargout>2                                         % do we want derivatives?
    dnlZ = hyp;                                 % allocate space for derivatives
    al = r./sqrt(g_sn2) - (V'*(Lu\be))./g_sn2;      % al = (Kt+sn2*eye(n))\(y-m)
    B = iKuu*Ku; w = B*al;
    W = Lu'\(V./repmat(g_sn2',nu,1));
    for i = 1:numel(hyp.cov)
      [ddiagKi,dKuui,dKui] = feval(cov{:}, hyp.cov, x, [], i);  % eval cov deriv
      R = 2*dKui-dKuui*B; v = ddiagKi - sum(R.*B,1)';   % diag part of cov deriv
      dnlZ.cov(i) = (ddiagKi'*(1./g_sn2)+w'*(dKuui*w-2*(dKui*al))-al'*(v.*al)...
                                 - sum(W.*W,1)*v - sum(sum((R*W').*(B*W'))) )/2;
    end
    diag_dK = 1./g_sn2 - sum(W.*W,1)' - al.*al;                  % diag(dnlZ/dK)
    dnlZ.lik = sn2*sum(diag_dK);
    % since snu2 is a fixed fraction of sn2, there is a covariance-like term in
    BWt = B*W'; % the derivative as well
    dKuui = 2*snu2; R = -dKuui*B; v = -sum(R.*B,1)';    % diag part of cov deriv
    dnlZ.lik = dnlZ.lik + (w'*dKuui*w -al'*(v.*al)...
                                    - sum(W.*W,1)*v - sum(sum((R*W').*BWt)) )/2;
    for i = 1:numel(hyp.mean)
      dnlZ.mean(i) = -feval(mean{:}, hyp.mean, x, i)'*al;
    end
    if isfield(hyp,'xu')                 % derivatives w.r.t. inducing points xu
      xu = cov{3};
      cov = cov{2};           % get the non FITC part of the covariance function
      Kpu  = cov_deriv_sq_dist(cov,hyp.cov,xu,x);           % d K(xu,x ) / d D^2
      Kpuu = cov_deriv_sq_dist(cov,hyp.cov,xu);             % d K(xu,xu) / d D^2
      if iscell(cov), covstr = cov{1}; else covstr = cov; end
      if ~ischar(covstr), covstr = func2str(covstr); end
      if numel(strfind(covstr,'iso'))>0            % characteristic length scale
        e = 2*exp(-2*hyp.cov(1));
      else
        e = 2*exp(-2*hyp.cov(1:D));
      end
      v = diag_dK-1./g_sn2;        % BdK = B * ( dnlZ/dK - diag(diag(dnlZ/dK)) )
      BdK = B.*repmat(v',nu,1) + BWt*W + (B*al)*al';
      A = Kpu.*BdK; C = Kpuu.*(BdK*B'); C = diag(sum(C,2)-sum(A,2)) - C;
      dnlZ.xu = A*x*diag(e) + C*xu*diag(e);  % bring in data and inducing points
    end
  end
end

(Sorry to paste apparently .m files aren't allowed as attachments).
Currently I get numerical inversion problems when I try to run the code.
The tests currently fail.
Any ideas @jameshensman ?

Okay, I had a look through the code. I think there was a sign error in the calculation of the mahalanobis distance. I also tried to simplify the code a little, and move it closer to pep8.
The tests pass, aside from the tests that ensure that the full_covariance prediction matches the variance prediction: this is just because it's NotImplemented.
I also added FITC to the SanityCheck notebook: looks great.
I note in passing that adding a White kernel to a FITC model does not help in the same way as it does with the variational methods.

Thank you!

@jameshensman  Is it me or is the sign error in Carl and Hannes' expression for the NML too?
nlZ = sum(log(diag(Lu))) + (sum(log(g_sn2)) + nlog(2pi) + r'*r - be'*be)/2;

No, I think their code is correct. Looking back, you didn't have a sign error, but I think this introduced some broadcasting issues:
tf.reduce_sum( tf.mul( tf.transpose(alpha), gamma ) ) )

perhaps it would all work without that transpose.

OK yes that makes sense. There definitely shouldn't be a transpose there.

OK I think FITC regression is finished.
@jameshensman would you mind reviewing the full covariance predictions.
I've repeated the Snelson experiment I did in MATLAB. There are a few tweaks to the optimizer options needed to make it all work but the effect is still there. I'm going to finish it in a separate PR / issue which will reference this one.

Also. I think we shouldn't squash this one. I'd like @jameshensman 's contribution to remain in the GitHub log.

I'm not sure that's the FITC full covariance prediction. It certainly looks
like a sensible expression, but I don't think it's the expression that
you'd get from Carl's code.
If we're working with the FITC model, then far from the pseudo-points we
expect the process to look like white noise. That's not the case here. I
think the correct thing to do is to replace
self.kern.K(Xnew)

with the equivalent FITC prior.
On 13 April 2016 at 15:18, Alexander G. de G. Matthews <
<EMAIL_ADDRESS>wrote:

OK I think FITC regression is finished.
@jameshensman https://github.com/jameshensman would you mind reviewing
the full covariance predictions.
I've repeated the Snelson experiment I did in MATLAB. There are a few
tweaks to the optimizer options needed to make it all work but the effect
is still there. I'm going to finish it in a separate PR / issue which will
reference this one.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/GPflow/GPflow/pull/37#issuecomment-209469697

Thanks for looking at it. Is it possible that what I've got is better?  I derived it by going back to Ed and Zoubin's paper. I took the FITC posterior over points and then integrated through the GP conditional like you would in our AISTATS 2015 paper. I think this means I haven't assumed that the prediction points are independent, but why would you when you don't have to? Indeed I think Carl points out in his review paper that it wasn't clear what Zoubin and Ed intended. Perhaps I am missing the point here.

Oh yay more test speeding up to do!

Agree, it's a strange thing, but you can find plots like that in e.g. this
paper:
http://www.jmlr.org/papers/volume11/lazaro-gredilla10a/lazaro-gredilla10a.pdf
(figure 2).
What you have may well be better, and I think there may be a subtlety
between FITC and FIC. Perhaps you should mimic whatever the GPML code does?
On 13 April 2016 at 16:20, Alexander G. de G. Matthews <
<EMAIL_ADDRESS>wrote:

Oh yay more test speeding up to do!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/GPflow/GPflow/pull/37#issuecomment-209506430

It smells of a straw man / misunderstanding to me. I'll ask Carl what he thinks.

If I remember correctly, there are two reasons why to choose the independent model, even if it seems worse. Firstly, for computational reasons. The matrix that needs to be inverted becomes as large as the number of predictions, which can be larger than M. Secondly, because if you take correlations into account in the predictions, you're using a different p(y|u) in training and test, and so the FITC model does not correspond to a well-defined Gaussan process model anymore.

the FITC model does not correspond to a well-defined Gaussan process
model anymore

This is my favourite view of FITC, that it's al alternative GP model, with
a new kernel. In this case the 'noisy' predictions make sense.
On the other hand, we're splitting hairs here, and Alex's method is also
just fine.
On 13 April 2016 at 16:38, Mark van der Wilk<EMAIL_ADDRESS>wrote:

If I remember correctly, there are two reasons why to choose the
independent model, even if it seems worse. Firstly, for computational
reasons. The matrix that needs to be inverted becomes as large as the
number of predictions, which can be larger than M. Secondly, because if you
take correlations into account in the predictions, you're using a different
p(y|u) in training and test, and so the FITC model does not correspond to a
well-defined Gaussan process model anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/GPflow/GPflow/pull/37#issuecomment-209516006

I just talked to Rich Turner about it. He says do what you would do for variational. i.e integrate out q(u) using the full conditional.
Incidentally isn't GitHub useful?
@markvdw @jameshensman  I think I agree with Mark's second point but I'm not sure I think it is that important. I'd rather have q treat train and test points differently and give a better prediction. I'm not sure I agree with Mark's first point. I think prediction goes as O(nHoldOut^2) rather than O(nHoldOut^3)  (neglecting M dependence) . It is still interesting to look at correlation among a small set of hold out points and in any case we do supply a version that just gives the diagonals of the covariance and scales as O(nHoldOut).

I sped up the tests a bit and this now passes and is ready for merge.

Current coverage is 98.36%

Merging #37 into master will increase coverage by +0.07% as of eb55ef7

@@            master     #37   diff @@
======================================
  Files           20      20
  Stmts         1057    1100    +43
  Branches         0       0
  Methods          0       0
======================================
+ Hit           1039    1082    +43
  Partial          0       0
  Missed          18      18

Review entire Coverage Diff as of eb55ef7

Powered by Codecov. Updated on successful CI builds.


Hash disregards units

Currently, hash is implemented like this:
impl<T: hash::Hash, U: Unit> hash::Hash for Quantity<T, U> {
    fn hash<H: hash::Hasher>(&self, state: &mut H) {
        self.val.hash(state);
    }
}

which disregards units (i.e. 1kg would have the same hash as 1Hz).

Sorry, haven't logged in in some time! This is an interesting issue! I'm not sure this is a huge issue — are quantities with different units likely to be hashed in relation to eachother?


Make discourse.brew.sh https only

Make discourse.brew.sh https only, i.e. redirect http -> https

This is a hosted instance so we don't have control over this. Also, please always fill out the issue template.


Are there updated install steps available?

The tool doesn't seem to build successfully when using the instructions given in the README.
brew install cmake
rustup install nightly-2022-08-03
rustup component add rustc-dev llvm-tools-preview --toolchain nightly-2022-08-03
cargo +nightly-2022-08-03 install --git https://github.com/rust-lang/rust-semverver

The build fails with several similar errors:
error[E0658]: `let...else` statements are unstable
  --> /Users/nfiedler/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-0.67.1/src/cargo/sources/git/known_hosts.rs:92:5
   |
92 | /     let Some(host_key) = cert.as_hostkey() else {
93 | |         // Return passthrough for TLS X509 certificates to use whatever validation
94 | |         // was done in git2.
95 | |         return Ok(CertificateCheckStatus::CertificatePassthrough)
96 | |     };
   | |______^
   |
   = note: see issue #87335 <https://github.com/rust-lang/rust/issues/87335> for more information
   = help: add `#![feature(let_else)]` to the crate attributes to enable

Any help would be appreciated, thank you.

That's because Cargo 0.67.1 is used, we have to pin it to 0.67.0 but it's vulnerable.
Anyway, I wouldn't recommend using this crate currently as it doesn't work nicely on some code and depends on the save-analysis feature which is planned to be removed in the near future. I haven't used it much, but maybe https://github.com/obi1kenobi/cargo-semver-checks is more useful, it detects semver failures reading rustdoc outputs.


Absolutize node names

The clang generates either absolute or relative dependencies (in .d files) depending on its flags. This makes llbuild ninja build miss dependencies sometimes since from llbuild ninja's standpoint the relative path name is different from absolute (this matches OS ninja behavior).
This patch resolves this edge case by absolutizing the node names (dependencies and rules).
An unfortunate consequence of this patch is that the debug output from the llbuild ninja build tool may sometimes differ: the absolute pathnames could be displayed instead of relative ones.
rdar://55235219

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test linux


Detect boolean assertions, mandate t.true()

Assertions like this evaluate to true or false:
t.truthy(array.indexOf(value) !== -1);

We should require you to write them like:
t.true(array.indexOf(value) !== -1);

I've seen a lot of t.truthy() in the wild when t.true() would be better.

Just so I understand this clearly, does t.true() give better error messages, or why should we prefer it in those situations?

@jfmengels It's more correct. Imagine you have a function foo() which normally returns true, but suddenly returns 1 instead. t.truthy(foo()) would not catch that case. IMHO in tests you should always be as strict as possible. It's the subtle bugs that gets you.

Okay, sounds good to me :)

Of course, the tricky ones are the ones this rule won't catch. But it will encourage best practices.
I was thinking about this problem as well. Should we be encouraging them to use the correct assertion in the AVA runtime? Like, if they use t.truthy and we get true, should we issue a warning? Maybe have like a --strict mode?


⚠ DesiTorrents has degraded performance

In 8229b39, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 500
Response time: 4743 ms

Resolved: DesiTorrents performance has improved in a2cb758 after 12 minutes.


App crash after download success but when move the file using moveItem with following message 'Terminated due to memory issue'

After updated the swift 3.0 of alamofire, we are start getting this issue. In previous versions of alamofire it is working fine. We have no clue on what charges are there in new moveItem method of swift 3.0. Please help us on that.

Can you post the code that's causing the crash, along with the versions of Alamofire, Xcode, the operating systems you're seeing the crash on?

self.request = self.backgroundManager!.download(data! as! URLConvertible, to: nil)
                .downloadProgress(queue: DispatchQueue.global(qos: .utility)) {  progress in
                    print("Progress: \(progress.fractionCompleted)")
                    DispatchQueue.main.async {
                        self.updateProgress(Int64(progress.fractionCompleted), totalBytesRead: progress.completedUnitCount, totalBytesExpectedToRead: progress.totalUnitCount)
                    }
                }
                .validate { request, response, temporaryURL, destinationURL in
                    // Custom evaluation closure now includes file URLs (allows you to parse out error messages if necessary)
                    return .success
                }
                .responseString {  response in
                    self.handleResponseOfDownload(response.response, error: response.result.error as NSError?)
            }

Alamofire Version - 4.2
Xcode - 8.1
iOS - 10.2

Have the same issue.   When finish download large file, move the file out of Tmp  directory will raise up the memory.Then the app will kill by system.

I tried this with sample of Alamofire also but end result is same.

Please help us to solve the issue ASAP.

@jshier
Please look into it ASAP. We are urgently looking for solution.

@subicura URLSessionDownloadTask on this have't this problem. I have to use URLSessionDownloadTask  to instead.

@suniljakhar we need a working example here that demonstrates the issue in order to continue to investigate. I'm very doubtful here that the issue is Alamofire itself, however, I want to give you the opportunity here to have us help you investigate further. We just need to do your part and give us more to work with.
I'm going to leave this open for a few days for you to get us more info.

@cnoon You can use download example of Alamofire  with lower end device like 1GB RAM device with following url  http://mirror.nforce.com/pub/speedtests/500mb.bin or any other url of 1GB to reproduce issue.
I will try myself also but if you time please look into it.

@cnoon Here is my findings :-
If we do not pass 'destination' in download statement,  like this Javascript Alamofire.download("http://mirror.nforce.com/pub/speedtests/100mb.bin", to: nil) Javascript
then it is working fine.
OR
If we comment this line in code of downloadTaskDidFinishDownloadingToURL delegate of Alamofire
Javascript         // try FileManager.default.moveItem(at: location, to: destinationURL) Javascript
then is also working fine. So both are the same things, comment moveItem method or pass nil as destination, things are working fine.
But if we pass destination in download statement it sparks the memory footprint and crash the app on lower end devices.
So it seems that there is some problem with 'moveItem' methods of iOS SDK.

@cnoon  Before swift 3, moeItem method is working fine as expected.

@cnoon I have created one sample of URLSessionDownloadTask and there i use moeItem method and it is working fine as expected. So now it seems that there is some issue of threading or process that i m not able find-out in Alamofire. I tried to run   try FileManager.default.moveItem(at: location, to: destinationURL) in DispatchQueue.main.sync block but end result is still same.

What do you mean by you created a URLSessionDownloadTask and then you use moveItem and everything is working fine? Does that mean you created an example that doesn't use Alamofire and there are no memory constraint issues like you're seeing in Alamofire?

Yes

@jshier would you be able to investigate this issue to see what's going on?

@cnoon I am not able to find any thing related issue.

@cnoon  Any update on this.

@suniljakhar I've created a test project using Xcode 8.2.1, Alamofire 4.3, and an iPhone 4S running iOS 9.3.5 (only other iOS device I have) and I can't reproduce your crash. I was able to successfully download a 1.4GB file on the device and move it to my documents folder. Please retest using the latest versions of Alamofire and Xcode. If you still get a crash, please post the crash log.

@cnoon Only other thing I can think of is an iOS 10 issue, do you have an older iOS 10 compatible device to test with? I'm in the process of acquiring one but it'll be a week.

Hmmm...I might @jshier. Could you post your sample project here so I have it just incase? We could also just try the sample project on a newer device running iOS 10 and monitor the memory usage. It shouldn't have to crash for us to be able to detect a memory spike.

Here's my test project, though it has a lot of different test bits, and my original download file was local, since the sites I found that do simple test file downloads were pretty slow.
AlamofireTest.zip

@suniljakhar I've run my test project on an iPhone 5s running iOS 10.2.1 and it worked without issue. I'm closing this issue, as we can't reproduce it. If you come up with a test project that reliably reproduces the issue, let us know.

I've had the same issue and it turned out that netfox was the cause. It seems like it's trying to keep the entire response in memory which leads to memory pressure and an app termination.


[NIFI-2788] update global hamburger menu to have fixed width icons an…

…d align text

Looks good @scottyaslan! This has been merged to master.


Fix status message string initialisation

ccl_cosmology_set_status_message checks if cosmo->status_message is empty, i.e a 0-length string. If cosmo->status_message is initially garbage, that check triggers the warning about overwriting an existing message and prints garbage. This PR explicitly initialises cosmo->status_message as a 0-length string.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.077%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4451

Relevant Lines:
4585

💛  - Coveralls

I tested this and while it solves the issue of throwing bogus warnings on a Cosmology instantiation, sometimes the status message is still nonempty:
In  [1]: ccl.CosmologyVanillaLCDM().cosmo.status_message
Out[1]: ' \udce2\udcb3\x11\udc93\x7f'

and setting a real warning triggers the overwrite warning:
In  [2]: ccl.lib.cosmology_set_status_message(cosmo.cosmo, "actual warning")
WARNING 1064: Status message being overwritten:
STATUS: 0.  (some bogus unicode that breaks github markdown rendering)

Also, compiling this yields this warning:
/home/nick/CCL/src/ccl_core.c:290:28: warning: assignment to 'char' from 'char *' makes integer from pointer without a cast [-Wint-conversion]
  290 |   cosmo->status_message[0] = "\0";
      |                            ^

with some perhaps useful help from stackoverflow.

I'm away and without laptop until next week, at which point I can have another  look at this.

Just a quick ping about this one @tilmantroester

I think I've fixed it. I forgot (although I'm not sure I was ever aware of this fact) that it matters in C whether you use single or double quotes.

I can't reproduce this either. @nikfilippas could it be that you have an old CCL version lingering around?

I can consistently reproduce this after removing every trace of CCL and reinstalling in py37 and py39 on my laptop and on the cluster, with python and ipython. @tilmantroester @damonge  could you confirm that you don't see anything when you run
python -c "import pyccl as ccl; ccl.lib.cosmology_set_status_message(ccl.CosmologyVanillaLCDM().cosmo, 'actual warning')"

?
I get something like
WARNING 1064: Status message being overwritten:
STATUS: 32622. h��~n

as output.

python setup.py clean && pip install -e .
and then
python -c "import pyccl as ccl; ccl.lib.cosmology_set_status_message(ccl.CosmologyVanillaLCDM().cosmo, 'actual warning')"
Produces no outputs for me. python setup.py clean removes ccllib.so, which otherwise can stick around and cause issues.

Doesn't work for me when I delete _ccllib.so and reinstall (I get some weird seg faults) but I guess if both of you can't reproduce that then the issue must be on my part. Happy for this to be merged if David can confirm no output.

I just tried on a clean conda env and clone of the repo and still works on my machine.


pkgsCross.hostPlatform.bash fails to build if buildPlatform.config==hostPlatform.config but  buildPlatform!=hostPlatform

We have a longstanding bug (probably more than one of them) where packages don't build properly if the buildPlatform and hostPlatform are not equal, but yet have equal .config attributes.
The equality test for platforms was made more forgiving by

https://github.com/NixOS/nixpkgs/pull/237512

but this merely concealed the problem.

Test case is in

https://github.com/NixOS/nixpkgs/pull/264992


E2E/Playwright: Add user browser context, reorganize env variables and update screenshots

Summary

Added user browser context to easily login user per browser and its pages
Reorganized env variables in one place only
Fixed tests and updated snapshots
Removed applitools

Release Note
NONE

/update-branch

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

Thank you @saturninoabril ,
I've run this locally, it works well now.
I had one observation, there's lot of explicit mention of 'networidle', wondering of we can make it implicit when Channel() is called, (example)
I can try it in follow up pr

@yasserfaraazkhan Good point! I've addressed it in the other PR - https://github.com/mattermost/mattermost-webapp/pull/12237


ARROW-8298: [C++][MinGW] Fix gRPC detection

gRPC may provide wrong version information by config.cmake and
.pc. See https://github.com/grpc/grpc/pull/22529 for details.
gRPC >= 1.17.0 detection is failed by config.cmake. Then we fallback
to our FindgRPCAlt. FindgRPCAlt uses gRPC_ROOT if it's set. gRPC_ROOT
is set to ARROW_PACKAGE_PREFIX automatically when we don't specify
gRPC_SOURCE. But we always set gRPC_SOURCE in our CI (see
ci/scripts/cpp_build.sh for details). So gRPC_ROOT isn't set.
If gRPC_ROOT isn't set, pkg-config is used to detect gRPC but
version information in grpc++.pc is also broken. gRPC >= 1.17.0
requirement isn't satisfied.
We can't build gRPC with
MinGW. https://github.com/grpc/grpc/pull/21720 is needed.

@github-actions crossbow submit -g nightly


Add proguard rules for InAppBrowser on Android

Description
InAppBrowser was crashing. The error was this: https://sentry.io/organizations/celo/issues/2241119154/?project=1250733&query=is%3Aunresolved&statsPeriod=14d
which matches what someone else was seeing here: https://github.com/proyecto26/react-native-inappbrowser/issues/174 and the solution was to add the proguard rules.
Other changes
N/A
Tested
No. My Android device is not working properly right now 😓  I'll keep trying, but if someone can test this in release mode that would be great.
Related issues

Fixes https://github.com/celo-org/wallet/issues/70

Backwards compatibility
N/A

Nice! FYI the above commands can be simplified to yarn dev:android -r

HI @gnardini We have verified this issue using latest Android Internal Build V1.12.0(1004294340)  and found below issues is fixed.

User is able to open the Moonpay page by tapping moonpay

Fixed issue:

https://github.com/celo-org/celo-monorepo/issues/4734

We will update this ticket if we observe any Crash related to inAppbrowser on android.
Thanks!


Object.keys to use keyof

TypeScript Version:  2.1.1
Code
With the latest keyof feature in TypeScript, I'd expect Object.keys() to return them. In code:
interface ObjectConstructor {
  ...
  keys<T>(o: T): Array<keyof T>;
}

See https://github.com/Microsoft/TypeScript/pull/12253#issuecomment-263132208

you can make a local copy of lib.d.ts then turn off standard definition --noLib from command line or "noLib" from tsconfig.json and then rewrite the local lib.d.ts anyway you want, including a fix to Object.keys

@jwbay thanks. Anders's comment in the other thread makes perfect sense. I'll close this.


cloudtrail_supported_actions contains actions that are not actually logged to cloudtrail

At least, sqs:ReceiveMessage (and various other sqs APIs) do not actually appear in cloudtrail. The only sqs related ones I actually see in cloudtrail across several accounts over the past 30 days are sqs:CreateQueue, sqs:DeleteQueue, sqs:PurgeQueue, and sqs:SetQueueAttributes.
I imagine there are others that are incorrectly present in this list.
I know that this list was updated ~3 months ago. Maybe the procedure for generating/verifying that list's accuracy could be improved or revisited?

It definitely could be improved, as right now there hasn't been a process. :)  All I had done previously was list all the actions from botocore and then manually look through the docs to remove actions that were mentioned as not used. :(
In theory, the concept behind Will Bengston's trailblazer project could be used: https://github.com/willbengtson/trailblazer-aws
He tries to call every single API and then looks in the CloudTrail logs to figure out which calls actually worked.  Unfortunately that concept ran into a lot of issues as documented in https://github.com/willbengtson/trailblazer-aws/issues/2 and there is an associated PR.  To summarize that thread, AWS doesn't record the calls if you don't call them with the correct formatting.  Ie. you need to pass certain arguments for each call, and those often have to match a regex.  So my PR tries to automatically determine what those arguments are and uses a reverse regex to generate arguments that should pass through AWS.  Unfortunately it still failed for a lot of calls, and because I was essentially fuzzing every API, it crashed the Organization service and an AWS on-call tech blew up my phone trying to get ahold of me to stop.  That resulted in the on-call tech setting up a phone call immediately between myself and the AWS Organization PM to discuss the situation.  I promised to stop, and that PM spoke with the CloudTrail PM who promised to document this stuff.  As I later learned in a private conversation with someone, the CloudTrail PM made the promise, knowing he wouldn't keep it, just to get me to stop.  Not cool!  So anyway, I stopped, and moved on to some other things waiting for this to happen.  In the meantime, someone at AWS has been working on getting these actions documented.  Apparently, it involves working with every single one of the 150+ service teams at AWS, so it has been months since I last heard anything about that work. :(

Perhaps the best way forward is for some folks with active AWS environments to provide a list of known APIs that are logged, by collecting that data from their own CloudTrail logs.  Just providing a list of action names is all that is needed.
Then for anything not in that list, we'd just assume it is not documented unless we hear otherwise from someone.


remove time stamp and validate dataset name is unique

remove time stamp from title and make sure dataset name is unique

ready for testing


Feature request: keyboard control to close the modal

This plugin is awesome, thank you. I have a small feature request: close the modal window when a key is pressed, by default 'Esc'. That's a standard feature for modal windows and I'm really missing it.

Hey thanks for the issue! I've been considering this too, I'll have a look at it later today, thank you!

@Alsciende I've added an escapable option, by default is false to prevent drastic changes on the users already using Vuedals as it was, so, just set escapable: true and should be able to dismiss the modal by using the escape key.
Thank you for the issue!


chore: setup CircleCI

@ItsANameToo you can work on the config on the circle branch

CircleCI is now enabled so it runs the tests for this branch.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a9d487c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage          ?   88.83%
=========================================
  Files             ?       38
  Lines             ?      887
  Branches          ?        0
=========================================
  Hits              ?      788
  Misses            ?       99
  Partials          ?        0

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 a9d487c...ed4474a. Read the comment docs.

are you going to look into this or did you just copy the client version? @faustbrian

nah, I'll take a look then


运行lfsr.sh是报错

报错内容为
[6064:0527/153701.122:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is

Please use linux environment with nvidia GPU or using other platform with cpu training.


UI Bug

Issue Type: Bug
The preference icon in File option is not correct. It should be >, not √.

VS Code version: Code - Insiders 1.45.0-insider (9328b32008089c515f39a13db9c71e57c7d36823, 2020-04-22T08:44:55.510Z)
OS version: Windows_NT x64 10.0.18363

Actually duplicate of #95838


can't go back to previous view

the close button seems not to work properly.. i tried to use WillPopScope nothing either

Can you provide more info or show me an example of what your code is trying to do.


'dotnet-migrate' support for project.json ->  fsproj

The dotnet-migrate doesnt support F# yet, to convert project.json to fsproj
WORKROUND: see https://github.com/dotnet/netcorecli-fsc/wiki/How-to-migrate-preview2-projects-to-preview3 tutorial
the dotnet-migrate use dotnet-new templates AFAIK, so fixing templates is half of the work
As note: using --template of dotnet migrate (who override base template instead of dotnet new) may improve current tutorial, didnt checked yet

dotnet cli reference code

dotnet-migrate
Microsoft.DotNet.ProjectJsonMigration
Microsoft.DotNet.ProjectJsonMigration.Tests
ProjectJsonToCSProj.md

If someone want to do that, i added a branch https://github.com/enricosada/cli/tree/dotnet_migrate_fsharp to start (you can develop on you own branch and send pr there, my branch it's just to make thing moving)
Added:

consider project.json with compilerName: fsc (so f# projects)

Atm will convert an f# project.json -> csproj.
TODO:

generate with .fsproj extension
fix fsproj with the things we need

add FSharp.NET.Sdk packagereference
change at end the Microsoft.Csharp.target to Microsoft.Common.target (see templates)

add tests (inside dotnet/cli), minimal for console/lib

all the changes should be inside dotnet-migrate and dotnet/cli repo

Yo!
I'm trying to build the latest version pf dotnet/netcorecli from source in order to address this, but the build fails.
This is what i've done:

installed cmake (and added to PATH)
clone dotnet\netcorecli (ended up on the rel\1.0 branch by default)
run build.cmd

but the build fails with a bunch of errors about attribute duplicates in AssemblyInfo files. Am I missing something here?

Yo!
I'm trying to build the latest version from source (eventually in order to address https://github.com/dotnet/netcorecli-fsc/issues/38), but the build fails.
This is what i've done:

installed cmake (and added to PATH)
clone dotnet\netcorecli (ended up on the rel\1.0 branch by default)
run build.cmd

but the build fails with a bunch of errors about duplicate attributes in AssemblyInfo files. I've tried @enricosada's branch https://github.com/enricosada/cli/tree/dotnet_migrate_fsharp too, with the same result.
Am I missing something in my toolchain here, or is this a legitimate error in the source?

Really sorry @tlycken , i didint see the notification about your comment. Thx a lot for trying to implement that.
I never had your issue building https://github.com/dotnet/cli repository.
But your flow was ok, i can just link the developer doc about that (maybe there is a step you missed?) https://github.com/dotnet/cli/blob/rel/1.0.0/Documentation/developer-guide.md
Anyway open an issue in https://github.com/dotnet/cli with the error message, they can help for sure.

closing, all project are already migrate to new sdk or can do that using the tutorial.


go get -u -v github.com/open-falcon/rrdlite


[HistogramEditor] debug CLUT Editor save/load table

Fixes https://github.com/Inria-Asclepios/medInria-public/issues/538

Open a histogram, add/move vertices, changes colors
Right click -> you can save and load vertices tables

These tables are saved/updated in a LUTs.xml file in the same directory as the database (can be accessed with the Log button at homepage which open this directory).
Example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE medLUTs>
<medLUTs version="1.1">
<table title="Blue">
<node>614.6923;0.4962;0;0;255;127</node>
<node>1182.4615;0.0846;0;0;255;21</node>
</table>
</medLUTs>

The tool name switch from "CLUT Editor" (nobody understand) to "Histogram Editor".
:m:

Is it possible de look at this PR? It would be easier to merge PR before switching the plugins to music3 :)

Sorry I realised this after validating, but the tables are still not deleted in the destructor of medClutEditorToolBox. It's done only in updateSavedTables, so there is still a memory leak there.

Ok, i'm doing a new PR, do not revert ;)


ITE: enable CPU_HAS_FPU for IT8xxx2

This option was previously enabled only if the M extension was
available, because typical compilers do not provide internal libraries
for RV32IAFC so builds fail at link-time. An appropriately-configured
compiler (such as GCC configured with
--with-multilib-generator=rv32iac-ilp32--f) can support such a build
however, so don't lie about the presence of an FPU.
This doesn't affect existing builds because CONFIG_FPU gates use of the
FPU, and is off by default. Enabling CONFIG_FPU will require an
appropriately-configured compiler, possibly also requiring careful
choice of CONFIG_FLOAT_HARD.
Signed-off-by: Peter Marheine<EMAIL_ADDRESS>

@Dino-Li FYI. This makes it possible for me to enable FPU without M.

@Dino-Li FYI. This makes it possible for me to enable FPU without M.

+1 LGTM. I don't have permission to vote a PR.


openssl-1.1.0-pre4 cross compilation failed

Hi,
I am not able to do cross compilation of openssl-1.1.0-pre4 build, I am building for arm and all previous build are working fine.
I m following below steps:
export INSTALLDIR=build-output
export PATH=$INSTALLDIR/bin:$PATH
export TARGETMACH=arm-none-linux-gnueabi
export BUILDMACH=i686-pc-linux-gnu
export CROSS=arm-none-linux-gnueabi
export CC=${CROSS}-gcc
export LD=${CROSS}-ld
export AS=${CROSS}-as
export AR=${CROSS}-ar
export PATH=$PATH:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin
./Configure -DOPENSSL_NO_HEARTBEATS --openssldir=/home/user/priti/workbench/openssl/src/openssl-1.1.0-pre4/build-output shared os/compiler:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
Configuring OpenSSL version 1.1.0-pre4 (0x0x10100004L)
no-crypto-mdebug [default] OPENSSL_NO_CRYPTO_MDEBUG (skip dir)
no-crypto-mdebug-backtrace [forced] OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE (skip dir)
no-ec_nistp_64_gcc_128 [default] OPENSSL_NO_EC_NISTP_64_GCC_128 (skip dir)
no-egd [default] OPENSSL_NO_EGD (skip dir)
no-heartbeats [default] OPENSSL_NO_HEARTBEATS (skip dir)
no-md2 [default] OPENSSL_NO_MD2 (skip dir)
no-rc5 [default] OPENSSL_NO_RC5 (skip dir)
no-sctp [default] OPENSSL_NO_SCTP (skip dir)
no-ssl-trace [default] OPENSSL_NO_SSL_TRACE (skip dir)
no-ssl3 [default] OPENSSL_NO_SSL3 (skip dir)
no-ssl3-method [default] OPENSSL_NO_SSL3_METHOD (skip dir)
no-unit-test [default] OPENSSL_NO_UNIT_TEST (skip dir)
no-weak-ssl-ciphers [default] OPENSSL_NO_WEAK_SSL_CIPHERS (skip dir)
no-zlib [default]
no-zlib-dynamic [default]
Configuring for os/compiler:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
*Warning! target os/compiler:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc doesn't exist!
*
Please let me know whats wrong here.

CROSS_COMPILE=arm-none-linux-gnueabi ./Configure {target} --openssldir=/home/user/priti/workbench/openssl/src/openssl-1.1.0-pre4/build-output shared no-heartbeats

To figure out what you want {target} to be, just run this, and pick from the list of targets presented:
./Configure

The os/compiler[:flags] part of the usage needs to be changed, we have forgotten...

As to the --openssldir option, I'm not sure what you expect from it.  Would you mind elaborating?

--openssldir is to give the destination directory path.

How to change the os/compiler[:flags] usage?? Can I do it at my end?

How to change the os/compiler[:flags] usage?? Can I do it at my end?

No. Sorry, I meant Configure's usage printout. It's misleading.
As for --openssldir, I think --prefix will suit you better.

Why I am not able to build it? All previous builds i was able to build.
I Changed openssldir to prefix.

I am able to build openssl-1.0.2g with the same commands mentioned above but i m not able to build openssl-1.1.0-pre4
As you suggested i checked the os/compiler target by running ./Configure command and my compiler is not mentioned in both the builds but still its able to cross compiled for openssl-1.0.2g not for openssl-1.1.0-pre4

The way you configure and build has changed in 1.1, substantially in some cases.

I added my compiler details in conf file like this:
"arm-none-linux-gnueabi-gcc" => {
cc               => "arm-none-linux-gnueabi-gcc",
cflags           => picker(default => "-Wall -DOPENSSL_THREADS",
debug   => "-O0 -g",
release => "-O3"),
thread_scheme    => "(unknown)",
bn_ops           => "BN_LLONG",
shared_extension => ".so",
},
And while running Configure command passed this config file:
./Configure --prefix=/home/gokul/Desktop/openssl-1.1.0-pre5/build-output --config=/home/gokul/Desktop/openssl-1.1.0-pre5/Configurations/10-main.conf os/compiler:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
And in target list i am able to view my target "arm-none-linux-gnueabi-gcc"
But still i m getting same issue:

Hey, sorry, lost you there for a bit.
I would recommend this in your conf file:
    "my-gcc" => {
        cc               => "gcc",
        cflags           => picker(default => "-Wall -DOPENSSL_THREADS",
                                   debug   => "-O0 -g",
                                   release => "-O3"),
        thread_scheme    => "(unknown)",
        bn_ops           => "BN_LLONG",
        shared_extension => ".so",
    },

And then configure like this:
export CROSS_COMPILE=arm-none-linux-gnueabi-
./Configure --prefix=/home/gokul/Desktop/openssl-1.1.0-pre5/build-output my-gcc

Thanks :) I am able to cross compile it. I was not passing the target name in Configure command because of that i was not able to configure it.

Astha
I am facing same issue, can't compile openssl-1.1.0 for arm-none-linux-gnueabi, can you please share the configure command(with all parameters) you used to configure?


MetricCollection does not share internal state

🐛 Bug
When I use MetricCollection to group auroc metrics with different average mode (which should share the same metric_state), the underlying metric_state is not shared.
To Reproduce
import torch
from torchmetrics import MetricCollection, AUROC
m = MetricCollection({'macro': AUROC(task='multilabel', average = 'macro', num_labels=100), 'micro': AUROC(task='multilabel', average = 'micro', num_labels = 100)})
pred = torch.randn(10, 100)
target = torch.randint(0, 2, (10, 100))
m.update(pred, target)
print(m['micro'].metric_state['preds'][0].data_ptr()) # e.g.,<PHONE_NUMBER>
print(m['macro'].metric_state['preds'][0].data_ptr()) # e.g.,<PHONE_NUMBER>
print(m.compute()) # {'macro': tensor(0.5295), 'micro': e.g., tensor(0.5129)}

Expected behavior
m['micro'].metric_state['preds'][0].data_ptr() and m['macro'].metric_state['preds'][0].data_ptr() should be the same, since the internal state is shared.
Environment

TorchMetrics version: v1.3.0.post0 (pip installed)
Python & PyTorch Version: Python 3.10.13 torch==2.1.1
Any other relevant information such as OS: Linux

I think this works as expected since it looks like __getitem__ will copy the state by default: https://github.com/Lightning-AI/torchmetrics/blob/master/src/torchmetrics/collections.py#L540
Running
import torch
from torchmetrics import AUROC, MetricCollection

m = MetricCollection({
    'macro':
    AUROC(task='multilabel', average='macro', num_labels=4),
    'micro':
    AUROC(task='multilabel', average='micro', num_labels=4)
})
pred = torch.randn(2, 4)
target = torch.randint(0, 2, (2, 4))
m.update(pred, target)
m.update(pred, target)
print(m.__getitem__('micro', False).preds[1].data_ptr())
print(m.__getitem__('macro', False).preds[1].data_ptr())

yields the expected result.

I see. Good catch! Did now know there is copying.


Redirect files &/or display action URLs from legacy

I see some users using legacy URLs like:

https://pypi.python.org/pypi?:action=files&name=limix&version=1.0.14 (on legacy: https://legacy.pypi.org/pypi?:action=files&name=limix&version=1.0.14 )
https://pypi.python.org/pypi?:action=display&name=craft-ai (on legacy: https://legacy.pypi.org/pypi?:action=display&name=craft-ai )
https://pypi.python.org/pypi?:action=display&name=text_progress_bar (on legacy: https://legacy.pypi.org/pypi?:action=display&name=text_progress_bar )

It'd be nice to redirect the display URLs and, potentially, the files URLs to Warehouse.
Followup to #3799.

Working on this.


Error when sending/receiving message and deploy within a minute

The receiver node goes nuts when I send/receive a message and do a new deploy in node red within 1 minute. The receiver node continues to through the following errors:
"[WHIN-Error] WebSocket was closed before the connection was established"
"[WHIN] Connection died"
Errors will keep throughing until the receiver node is deleted, flow newly deployed and node red restarted

Hi, the receiver node will only work on paid subscriptions. In coming releases we will update its look and feel, so that you can turn it on/off... it will be off by default, and we will include a dialog remembering users that it should not be used if they're on a free plan.
I will leave this issue open till this feature is added.

update to 0.0.9 to use the switch and turn on and off the whin receive node. It will not work on free subscriptions.


Xcode Simulator SSL Certificate Warning

Describe the bug
Xcode Simulator throws ssl warning calling a ddev site.
To Reproduce
Steps to reproduce the behavior:

Open /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app
Open your ddev site
Simulator throws ssl warning

Expected behavior
No SSL warning and showing the site.
Screenshots

Version and configuration information (please complete the following information):

Host computer OS and Version: MacOS 10.14.5
Docker version: 19.03.4
ddev version: v1.10.2
config.yaml contents:

APIVersion: v1.10.2
name: www.test.de
type: php
docroot: ""
php_version: "7.2"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.2"
nfs_mount_enabled: false
provider: default
use_dns_when_possible: true
timezone: ""

mkcert installs a system CA, and a firefox CA, but I guess the Xcode simulator doesn't respect the system CA. You can manually add the mkcert CA to your Xcode simulator I'm sure (but I don't yet know how, hope you'll update here).  The CA files to add to your simulator are in mkcert -CAROOT. Probably what you need to add is the file $(mkcert -CAROOT)/rootCA-key.pem

Would you mind making an upstream issue for this in https://github.com/FiloSottile/mkcert ? I'm pretty sure you can explain it completely with your info there. AFAICT from your description, the issue is that the Xcode simulator doesn't use the macOS system store, it must have its own?.

No response from OP. Closing, but happy to continue the conversation here.


skel: common: version: Deleted version.py file

Closes #1257

Please, add hacktoberfest-accepted label to this PR.
Much appreciated!

Seems like removing of version.py file fails some tests. But I couldn't find a connection between this file and failed tests in their logs


watch mode does not watch json with resolveJsonModule

TypeScript Version:  3.5.2
Search Terms:
watch json resolveJsonModule
Code
run tsc --watch with resolveJsonModule: true.
// tsconfig.json
{
  "compilerOptions": {
    "resolveJsonModule": true
  },
  "include": [
    "src",
    "src/artifacts/*.json"
  ]
 }

Expected behavior:
When an included json file is changed, tsc will detect it and copy the file to outDir.
Actual behavior:
didn't happen.

I cannot repro this.. First of all the tsconfig you mentioned only includes the json files from the artificats folder and there is no outDir mentioned and hence the file is not copied. If I add outDir to config it does copy the file to the outDir.
c:\temp\test3>node c:\TypeScript\built\local\tsc.js  --listFiles --listEmittedFiles -w
[11:14:00 AM] Starting compilation in watch mode...

TSFILE: c:/temp/test3/bin/something.json
c:/TypeScript/built/local/lib.d.ts
c:/TypeScript/built/local/lib.es5.d.ts
c:/TypeScript/built/local/lib.dom.d.ts
c:/TypeScript/built/local/lib.webworker.importscripts.d.ts
c:/TypeScript/built/local/lib.scripthost.d.ts
c:/temp/test3/src/artifacts/something.json
[11:14:01 AM] Found 0 errors. Watching for file changes.

You would want to verify that your config and provide more details with the actual repro steps.

When running tsc, the files are copied. it only does not copy when running watch mode.
You can check out an example in eslint-plugin-harmony


Logger Correlation config

Added a logger configuration called Correlation that has two keys:
add_correlation_id : bool
field_name : string
The boolean adds a uuid_v4 to any logs outputted by the component.
The string is to edit the name of the field, which is by default @X-Correlation-Id

Nevermind, the logger is only instanced once so it does not modify the uuid generated for each message


Secondary development request

Hey, guys, thanks for you created this creative project,  It's incredible, I used it in my blog in my and so many side projects.
I love it, But as I use it, I have my own ideas and requirements, such as I prefer white background, I created a modal component, so I had got to override it. so I hope to do a secondary development based on it and release it, would like your permission

Hello @myNameIsDu. Yes, the project is licensed under the MIT license. You can read the license here. So yes you are free to make your own fork. The only requirement is that you keep the LICENSE and copyright intact in your fork.
A link back to the original project is appreciated. Thank you.


backtrace=1 causes 500 Server error

Attempting to run any code on play.rust-lang.org (even just fn main() {}) returns a 500 Server Error when a backtrace has been requested.
I cannot reproduce this error locally.
@alexcrichton: could you see if there is anything useful in the logs?

Perhaps this is relevant?
Aug 28 18:09:56 ip-10-235-19-101 playpen: flag provided but not defined: -eRUST_BACKTRACE
Aug 28 18:09:56 ip-10-235-19-101 playpen: See 'docker create --help'.

Looks like some argument may not be getting passed correctly?

Or maybe docker versions are different?

Yeah, that was my first intuition, that some docker version did not accept the -e flag. Sadly I could not find anything relevant in their changelog :(
Do you know which docker version is running on playpen?

Sure:
$ docker --version
Docker version 1.11.2, build b9f10c9

Alright I found the problem (I think).
Basically, docker 1.12 got smarter when parsing flags: -eFOO=BAR is treated as "set flag -eFOO to value BAR" in 1.11 and as "set flag -e to value FOO=BAR" in docker 1.12.
I'll submit a fix soon.

Thanks @TimNN!

The fix seems to have worked, backtraces are now functional on http://play.rust-lang.org.


Specific http status code if record already exist in DB

API Response for POST/PUT call should contain specify response code if record already exist in the database.

The error codes are now updated for single record for the createExperiment and updateResults as per the following docs
https://github.com/kruize/autotune/blob/mvp_demo/design/MonitoringModeAPI.md
https://github.com/kruize/autotune/blob/mvp_demo/design/CreateExperiment.md
https://github.com/kruize/autotune/blob/mvp_demo/design/UpdateResults.md

@patilsuraj767 Can you please review the API behaviour for a record that already exists and let us know. Thanks!

We have implemented 409 status_code check for one of the API - here  and it is working as expected. :+1:


format: better support for code generating clients

Provide a way to quote a name or a string with the backend-specific syntax (instead of requiring clients to introspect metadata)
Provide a way to introspect the database type name for a given Arrow type, particularly for what the driver will do in scenarios like bulk ingestion (could do this by: binding an empty batch with a schema, then setting an option on the statement before "executing" it to get the results)
Provide a way to generate the name of a bind parameter by index or by name

See mentioned issues below for motivations.

The earliest drafts used a similar design where you requested function pointers by name, but that's very inconvenient to use.

Much of the current design was a concession to requests to be able to use the API directly and not have to pull in the driver manager.

All three of the above could be implemented via existing methods if that's the concern


Fix types for JSX usage

Types are pretty incomplete and in general don't play well with Vite + JSX. Need to work on this.

This has been fixed in 156db5b78591156544a8fb462e2bb5117cd0f057


Draft 24 updates

Now covering all the changes. Fixes #483.

Good stuff! I did find the next_crypto stuff a bit ugly looking, what with all those unwrap()s that are hard to statically check. I wonder if we could come up with a different design for this.


Resources to add

Added

[x] https://github.com/vuejs/awesome-vue#readme

Need to add

I suggest adding work with data visualization - in the form of graphs, charts, dashboards,
preferably interactive
perhaps a separate block or for this one for the other ...
it seems you know better how to do it better
but there is WHAT to add - a link to a good IMHO article: https://habr.com/en/post/457946/
or
https://netology.ru/blog/7-services-data-visualization - this second one is apparently not at all in concept ... though ...

@ink-kin thanks for suggestion, can you give an example that what kind of data visualization in our app. will be useful for developers. so, that i will get clear idea of what you want...


permission_required decorators redirect to a broken URL

When a user attempts to access a view that is guarded by a permission_required decorator, and the user does not have the required permission, they are redirected to a broken URL of the form http://localhost:8000/admin/images/django.contrib.auth.views.login?next=/admin/images/.
To reproduce (on wagtaildemo):

create a group with no permissions apart from 'can log into Wagtail admin'
create a user in that group and no others
log in as that user
visit /admin/images/

Having made some initial steps towards introducing class-based views to wagtailadmin in this branch https://github.com/gasman/wagtail/tree/feature/collections3 , I've discovered that permission_required decorators are quite horrible to integrate into CBVs, and so I've come up with an alternative mixin-based implementation here https://github.com/gasman/wagtail/commit/feb4c08ae116f2cfb62535d4d37b0e51aacbe884 .
As a nice side effect, this implementation doesn't suffer from this issue (because it's not tied to the LOGIN_URL setting). So, we "just" need to convert the rest of the wagtail admin to CBVs, and this will be fixed :-)

Django 1.9 introduces a mixin like that, might be useful as reference: https://docs.djangoproject.com/en/dev/topics/auth/default/#redirecting-unauthorized-requests-in-class-based-views


error! xhr poll error

I am receiving the following error over and over:
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
connected!
authenticated!
error! xhr poll error
The code I am using is directly copied from the example.

Hey, sorry for the long delay in getting to this.
This seems to be caused when Streamtip's server has a lot of connections, and their own code just ignores the error and tries to reconnect, so that's all I'm going to do.
You may still see multiple connected/authenticated events, but xhr ... won't throw an error now.
I don't think this is a big problem since newTip is the main event to be watching anyway.

This still causes problems actually and I don't like just ignoring it as a 'solution', reopening.

I made some modifications to our nginx upstream configuration, as I believe some 0 content length responses on socket.io are causing nginx to think an upstream is encountering issues when it isn't. Please let me know if this helps (it appears to have on my end).

@night I'm still getting many errors, and am struggling to connect and auth.
After several minutes, I usually connect/auth. However, this usually lasts only a few seconds at most before the xhr poll errors resume.
I'm running on a BuyVM VPS with Ubuntu 14.04 and Node.js 0.12.2.

I cannot reproduce that, unfortunately. I've tested this locally with node 0.12.0. I also tested this on BuyVM VPS running Debian 7 with node 0.10.38, and did not encounter this issue. I think there's something funky going on with your connection. Can you "curl -vvv https://streamtip.com" and see what's going on? It sounds like you're unable to connect, which I've encountered before when setting the VPSes main IP to be one of their DDoS protected IPs (although in that instance I was having trouble connecting to api.twitch.tv).

curl -vvv https://streamtip.com on my BuyVM VPS appears to generate pretty normal output. In those moments where I do get a brief connection to the socket, I can receive notifications and everything works. I can connect, but I can't stay connected.
Curiously, running this code on a DigitalOcean droplet results in far fewer xhr errors. They're still happening, but once every 10-20 seconds or so instead of constantly.

Is your BuyVM IP <IP_ADDRESS>? If so, nginx is logging your requests as the following:
2015/04/03 22:34:15 [error] 14915#0: *191866 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_2.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW", host: "streamtip.com"
2015/04/03 22:34:15 [error] 14915#0: *191866 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_3.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW", host: "streamtip.com"
2015/04/03 22:34:15 [error] 14915#0: *191866 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_1.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW", host: "streamtip.com"
2015/04/03 22:34:15 [error] 14915#0: *191866 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_4.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=j2QNJM8k_ra_3GCaAALW", host: "streamtip.com"
2015/04/03 22:34:16 [error] 14918#0: *191922 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_2.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX", host: "streamtip.com"
2015/04/03 22:34:16 [error] 14918#0: *191922 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_3.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX", host: "streamtip.com"
2015/04/03 22:34:16 [error] 14918#0: *191922 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX HTTP/1.1", upstream: "http://unix:/var/run/streamtip/streamtip_1.sock:/socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e4pIYSlDLEcAALX", host: "streamtip.com"
2015/04/03 22:34:16 [error] 14918#0: *191922 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: streamtip.com, request: "GET /socket.io/?client_id=[redacted]&access_token=[redacted]&EIO=3&transport=websocket&sid=v9075e

I'm not sure why your requests are resulting in this error, so it will probably require more debugging.

That is indeed my BuyVM IP.

I'm curious if there is a misconfiguration on your end, since every failing request is only websockets. Is there something on your end blocking websockets? Websockets require HTTP 1.1, so if your client or something in between doesn't support that, it could be why it's failing.

What changes if you enable multiplexing and modify your transports like the following:
        transports: [
            'xhr-polling',
            'jsonp-polling',
            'polling'
        ],

There shouldn't be much room for misconfiguration. This BuyVM VPS is pretty bare. It's got node installed and I'm running NodeCG via PM2. Nothing else. NodeCG itself also uses Socket.IO for all its communication and that does not have issues. I can try wiping the VPS and starting fresh if you think it's a worthwhile route of investigation.
Enabling multiplexing and modifying my transports did not seem to make a difference. Curiously, even if I removed xhr-polling from the list I still got the exact same xhr error.

If you're only testing in an environment with nodecg running, perhaps you should isolate with just this package.
Additionally, client logs would be helpful. Debug instructions are here: http://socket.io/docs/logging-and-debugging/
You can debug like:
DEBUG=* node testing.js

You're right, step one should have been isolating to just this package and trying that. Not sure why I didn't have the presence of mind to do that.
Unfortunately, I'm getting the same error. Here's a gist with the debug output from a few seconds of script execution time: https://gist.github.com/Lange/cd70db7f1588096b68d2

Are you sure the correct version of socket.io is being loaded? Sometimes if you have a package in ~/node_modules node will prefer that over the node_modules in the app dir.

There is no node_modules folder in any parent directory of the test script I was running. The version of socket.io-client being loaded is the one specified in this package's package.json, 1.3.5.

The socket.io in use by Streamtip is lower, 1.2.1

Manually installing<EMAIL_ADDRESS>does not seem to have resolved the error. Additionally, I tried removing the seemingly accidental events dependency (events is a core module) from this package's package.json, but this too had no apparent effect.

It's unfortunate, but I couldn't tell you why you're having issues connecting. Maybe try downgrading from node 0.12.x to 0.10.x, or trying a different server completely. I've tried your client id and access token, and haven't been able to reproduce any issues over at BuyVM or locally.

I've seen the error a handful of times locally and once on my vps (<IP_ADDRESS> if it helps, all subsequent tests connected first try), but it's usually just shown once, socket reconnects, everything's fine, not continued errors.

I tested on 0.10.38 on my BuyVM VPS this morning, no luck.
I'm doing more tests on another DigitalOcean droplet and I'm having very few, if any, xhr poll errors. I think I'll spin up a fresh droplet for the project that I want to use StreamTip for and see if it works.

@MattMcNam Those dropped connections should be what I resolved earlier, as nginx was failing over an upstream if it returned a 5xx error (by default max_fails is set to 1 apparently). Please let me know if you are still seeing this issue often. Seeing it once in a while is normal, as sometimes updates are pushed or an uncaught error occurs (like in net calls in PayPal's sdk, for example) and requires node instances to restart.
@Lange I still have a good belief there's something funky going on with the connection, somewhere. Either the protocol isn't being sent properly or for some reason a websocket cannot be established. I read over the source code that returns a "transport error," and seems to only happen when there's a socket error. Maybe you can try experimenting with what you connect to.
Change "https://streamtip.com" to the following:
http://streamtip.com
http://<IP_ADDRESS>
http://<IP_ADDRESS>
http://<IP_ADDRESS> (BuyVM internal IP in NJ)

Interesting results:

https://streamtip.com/
:x:

http://streamtip.com/
:x:

http://<IP_ADDRESS>/
:white_check_mark:

http://<IP_ADDRESS>/
:white_check_mark:

http://<IP_ADDRESS>
:white_check_mark:

All the entries with a checkmark connected immediately and didn't show any xhr errors during the time I observed them, which was about 60 seconds each.

This definitely seems like a configuration issue somewhere, as the IP addresses provided point to the two nodes Streamtip uses. I'm curious if there's some sort of reverse proxy (or something similar) empoyed that doesn't support the websocket connection and is causing it to be blocked. You might also check that the DNS is resolving properly to the listed IPs. There's definitely something wrong, but I don't believe it's an issue on Streamtip's end (as I can't seem to reproduce this).

My VPS appears to be able to correctly resolve the address of streamtip.com, so perhaps we can use that as a workaround in the library.
@MattMcNam, would it be a good idea to have streamtip-listener resolve the IP of streamtip.com on startup and connect the socket to the IP directly?

Since this seems like a socket.io-client library issue, I'm not sure working around a bug is a good idea. Perhaps if you can reproduce the conditions needed to make this occur, then it could potentially be traced and fixed. Were you able to reproduce this on DigitalOcean? What about another virtual machine (or the same reinstalled) at BuyVM?


Weekly forecast - days of the week

Description
If its possible it will be great to add in weekly forecast days like Mon, Tue, Wed, Thu etc above dates.
For instance, it will be easier if u want to see what will be weather in Friday, this way you need to check calendar or to calculate days.

Priority
Low (Nice-to-have)

https://github.com/ajnart/homarr/pull/1932#issuecomment-1981584562
Because of the current system for options, we have decided against to avoid cluttering too much.
To note that it was thought about and planned to be added.
We'll keep the issue open for reference, thanks

Ok i understand.


Docs: User Guide - Home - Update content to reflect current XFD capabilities

💡 Summary
Update https://docs.crossfeed.cyber.dhs.gov/
Motivation and context
At this time, the xfd application does not allow custom scanning, but the platform will allow CyHy customers to review results of WAS and VS reports.
Implementation notes

We recommend changing the first paragraph in the "About Crossfeed" section to read:
Crossfeed is a web application with a self-service portal that collects and visualizes attack surface data from diverse sources to provide information about organizational assets. The tool continuously enumerates and monitors an organization’s public-facing attack surface in order to discover assets and flag potential security flaws.

We recommend changing the text under the "Analyze your entire inventory of public-facing sites" highlight to read:
Crossfeed can discover all related subdomains from an organization’s root domain and help users understand if certain websites or webpages are unintentionally exposed. Crossfeed may even discover assets that users are not tracking as part of their inventory.

We recommend changing the text under the "Manage and triage your vulnerabilities" highlight to read:
Users can view detailed information about CVEs on the Vulnerabilities page, including detection history, affected products, and additional references.

We recommend changing the title of the "Control Automated Scans on Your Assets" highlight to "Review Results of Recent Scans," and we recommend changing the text in this highlight to:
Users who are enrolled in active scanning services offered by CISA will be able to review the results of these scans in Crossfeed as soon as the information is available, rather than waiting for a weekly report.

Please also change this page to reflect the recent rebranding of this resource as "the CyHy Dashboard."

We recommend changing the first paragraph in the "About Crossfeed" section to read:
The Cyber Hygiene (CyHy) Dashboard is a web application with that collects and visualizes attack surface data from diverse sources to provide information about organizational assets. The tool continuously enumerates and monitors an organization’s public-facing attack surface in order to discover assets and flag potential security flaws.
Please also change the title of this section to "About the CyHy Dashboard"

We recommend changing the text under the "Analyze your entire inventory of public-facing sites" highlight to read:
The CyHy Dashboard can discover all related subdomains from an organization’s root domain and help users understand if certain websites or webpages are unintentionally exposed. The web application may even discover assets that users are not tracking as part of their inventory.

We recommend changing the text under the "Manage and triage your vulnerabilities" highlight to read:
Users can view detailed information about CVEs on the Vulnerabilities page, including detection history, affected products, and additional references.

We recommend changing the title of the "Control Automated Scans on Your Assets" highlight to "Review Results of Recent Scans," and we recommend changing the text in this highlight to:
Users who are enrolled in active scanning services offered by CISA will be able to review the results of these scans in the CyHy Dashboard as soon as the information is available, rather than waiting for a weekly report.

This is OBE. Scope has changed and no requirements were derived for the initial portion of this task.


x/tools/internal/telemetry: implement *wire.Metrics translator

Opening this issue to remind myself to prioritize implementing the translator for metric to *wire.Metrics to enable serialization.

@odeke-em - Should this have the Soon label ? It is only reserved for serious bugs and outages.

@odeke-em - Should this have the Soon label ? It is only reserved for serious bugs and outages.

Sorry about that, undone.

@ianthehat @odeke-em Just as an update, I am currently working on functionally testing this with the OpenCensus agent.

With all the CLs that have been submitted and most recently https://go-review.googlesource.com/c/tools/+/207838, this issue can now be closed.


As a CIF Administrator, I want to be able to track waste as a sector category, so that I can accurately capture and report out on sector related projects

Description:
Feedback from CIF: Can we look at adding "Waste" to the sector drop down list under the project overview tab? One of the 2020 projects (for ex. 2020-RFP-1-VANC-193) has "waste" listed as their sector and Im not able to complete this section (sector is a mandatory field). Or if it makes sense, what about making the sector field "optional" like the Project Type field above it?
Acceptance Criteria:
Given I am an admin user
When I am on the project overview form and select the sector dropdown
Then I have "Waste" as an option
Given I am an admin user
When I am on the project overview form
Then I filling out the sector dropdown is optional and does not prevent form submission???????
Development Checklist:

[ ] Add "Waste" to the cif.sector table using a 001 file (see report_type/report_type_001 for an example)
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

@nanyangpro / @suhafa, do you know if/why sector is mandatory?

From a past ticket (#645): "Tech team wants to know the sector the projects are in. They like to filter projects by sector for when they receive requests for information by sector. Currently the sector is an open field in the spreadsheet, the sectors are not official sectors such as NAICS--just a list of sectors the team uses."
It helps the Tech team filter out projects so that may be one reason why.

Based on @suhafa 's comment above, I'm going to write this ticket with sector remaining mandatory

This should be done by https://app.zenhub.com/workspaces/climate-action-secretariat-60ca4121764d710011481ca2/issues/gh/bcgov/cas-cif/1718


Upgrade to Spring boot 2.2.6

What does this PR do?
Changes applied are coming from the runtime guide, basically using the newest dependencies for Spring Boot 2.2.6.
RHSA-2020:2252 - Security Advisory
Spring boot 2.2.6 runtime guide
Red Hat support for Spring Boot: 2.2.6 Component Details
Is there a relevant Issue open for this?
No open issue
Who would you like to review this?
cc: @redhat-cop/containers-approvers

@schen1 ; is the only reason not moving to latest SB (2.3.0.RELEASE) due to RH support?

@schen1 ; is the only reason not moving to latest SB (2.3.0.RELEASE) due to RH support?

Well, one thing is definitely support. If we want to use the latest SB release, then the readme should not mention the RH Application Runtimes product and we would also need to adapt the repositories URL as RH does not serve the latest SB content.

@schen1 ; thanks for the clarification. leave it as is then.

/approve
/lgtm


Patch handling of end chunk stream events for OpenAI endpoints

Pull Request Type

[ ] ✨ feat
[x] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

Relevant Issues

resolves #1475
Impacted LLMS to test:

[x] Generic OpenAI
[x] OpenAI
[x] GroqAI
[x] HuggingFace
[x] LMStudio
[ ] LocalAI
[x] Mistral
[x] Perplexity
[x] TextWebGenUI
[x] TogetherAI
[x] LiteLLM

What is in this change?
Path OpenAI stream handler to explicitly check for finish_reason key in message chunks before comparison as if it is non-existent it is != '' and != null and ends the stream with no data responses.

Additional Information

Developer Validations

[ ] I ran yarn lint from the root of the repo & committed changes
[ ] Relevant documentation has been updated
[ ] I have tested my code functionality
[ ] Docker build succeeds locally

@shatfield4 please test the unchecked LLMs that their streaming responses function as intended

LGTM other than LocalAI (cannot get running on my machine to test)


Remove deprecations

This PR consists of a number of individual unrelated commits, better reviewed separately.
I don't mind sending them all as separate PRs. However, the changes are quite small and self-contained.
Depends on:

https://github.com/rspec/rspec-support/pull/496
https://github.com/rspec/rspec-expectations/pull/1290
https://github.com/rspec/rspec-mocks/pull/1412
https://github.com/rspec/rspec-rails/pull/2458

Not Done
There are a few things I'm afraid/reluctant of touching, specifically:

described_class behaviour (see https://github.com/rspec/rspec-core/issues/1610#issuecomment-46316040, https://github.com/rubocop-hq/rspec-style-guide/issues/104)
Rake task pattern/FilePath (https://github.com/rspec/rspec-core/blob/11928e0d0fc3265899c74a035c7ec48ce59ffed3/lib/rspec/core/rake_task.rb#L128) - seems that we'll remove a feature with no replacement

Green.


Adding data plane commands for load azure cli extension

We have added data plane commands for load testing service to the existing load cli extension which contains commands for control plane.
In this implementation we will be keeping each command group and files related to it such as helps, params, custom commands, etc. in a separate directory for that particular command group itself.
The commands were not auto generated.
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.


grpc-json transcoder: Support ignoring whitelisted query parameters

Title: grpc-json transcoder: Support ignoring whitelisted query parameters
Description:
It may be desirable to ignore some query parameters. The most common use case would be api key parameter. For example,  /shelves/456/books/123?key=API_KEY wouldn't be transcoded unless variable binding is defined.
The current transcoder implementation does not allow this. I believe the simplest solution would be adding a query parameters field in the transcoder config and pass it to PathMatcherUtility::RegisterByHttpRule.  I'm currently working on a mock up for illustration.

For the first option that @qiwzhang, it would be roughly look like this:
https://github.com/kh-chang/envoy/commit/20110bbc8b2c95c9c71cba2447892136a6a1fbb6

Since transcoding filter will set path to gRPC method,  all query parameters will be discarded.  It will be useful to move some of them to headers so
Another option is to move certain query parameters to headers.  For example
Move
path?key=1234
to
x-api-key: 1234
We could define:
Message MoveQueryParameter {
// the query parameter key will not be used for transcoding.
string query = 1;
// the value will be moved to the header with the name
// if empty,  it will not be added to the header.
string header = 2;
}
//  How to move the query parameter
repeated MoveQueryParameter  query_movers = 5;

As opposed to moving to headers, probably move to the dynamic metadata?

Both are useful for certain cases;  moving to header can be used by another proxy, moving to dynamic metadata can be used by another filter within the same proxy.  How about we support both as:
Message ExtractQuery {
// the key of query parameter to be extracted,
// it  will not be used for transcoding to fill gRPC request body.
string query = 1;
// If not empty, the value will be moved to the header.
string header = 2;
// if not empty, the value will be saved to dynamic metadata.
string metadata = 3;
}

@qiwzhang I think we do ignore all unknown parameters in ESP, no? I thought Envoy does same but if not we might be able to do that, just like it ignores unknown fields in JSON.

For moving parameters to header I think it is a generic one and could be another filter, like we have header_to_metadata filter already. Perhaps open another issue for that?

@lizan ESP has "system_parameter" to exclude from.  Its "system_parameters" defines "key" and "api-key", so path matcher will not fail.  Otherwise if there is unknown query parameters, ESP will fail.

Since we already have header_to_metadata and we cannot change the name easily so I prefer small filters, can you open issue for that? We can discuss there.

Regarding either whitelisting query params to be ignored or simply ignore all invalid query params for transcoder, do we prefer working around from other filters? Or is would it be still worth supporting it in the transcoder filter?

I prefer not to add "ignore_all_unknown" to the grpc transcoding filter.  I am sure it will be useful for some cases. But it also has the drawback of not rejecting requests with typo.

Hi @lizan , there is an issue of doing it in separate small filters.   These request modification actions (moving query parameters to header or metadata) are specific for the grpc_transcoding filter,  they should only activate on the requests that grpc transcoding filter is activated.  For now, the checking is simple, just content-type,  but in the future, it may add other conditions, such as per-route activation (in order to support multiple backends).   Then these small filters need to use the that same activation condition. It will get complicated.
These modification are specific for grpc_transcoding,  I think we should build into grpc_transcoding filter.
You could argue that we can modify all requests regardless grpc_transcoding is activated or not.   But this is not good, a proxy should not modify the requests as much as possible in order to support proxy chaining.   It should only modify the requests if it is necessary, such as grpc transcoding.

OK then, let us just do the change proposed by  kh-chang@20110bb

I will work on a PR.

Sorry for writing on a closed issue but what happened to the discussion about ignoring all unknown parameters? I am currently in a situation where I have clients hitting envoy that add query parameters unpredictably from our side. There is no way we can add an exhaustive list of keywords to the ignored_query_parameters config.

Please raise a new issue of new feature request to allow unknown query parameters.