Windows node support in Kubernetes

In what area(s)?

/area runtime
/area operator
/area placement
/area docs
/area test-and-release

Describe the feature
I would like to utilize dapr on .NET framework applications that have been lift-and-shifted, but will talk to Linux micro-services via dapr. Currently, if I understand correctly, the sidecar injector has no context to distinguish if a pod is on a Windows or Linux node. I can currently create a Windows dapr image and configure that in my cluster, but then my cluster would not support Linux.

Correct, the sidecar injector takes a single image of the daprd runtime and injects it to any pod.
Would an ad-hoc solution targeting Windows be enough (for example, provide an additional ENV var to the injector for a Windows image and then add a Dapr annotation on the Pod spec like dapr.io/windows?

I think so, I'm looking into making a nanoserver image for dapr for this case, pretty new to this toolchain though.

This is to support windows containers on k8s.Changes needed: a windows container image for daprd and changes in injector to inject correct image based on platform.

@msfussell @orizohar there is another customer (@Phiph) who wants to run dapr on windows. We have already generated Windows binaries. But we have not built windows container images and validate it properly. I think in the community call, we can ask the needs of windows cluster support.
Most of work will be the engineering tool change and validation. the work size will be 1 week for 1 engineer, including validation.

@msfussell @orizohar there is another customer (@Phiph) who wants to run dapr on windows. We have already generated Windows binaries. But we have not built windows container images and validate it properly. I think in the community call, we can ask the needs of windows cluster support.
Most of work will be the engineering tool change and validation. the work size will be 1 week for 1 engineer, including validation.
Any update?
I need this also, we are locked (for now) in .Net Framework services but I suspect many  app modernization programmes will also need windows container support. Dapr isn't platform? agnostic  if its all linux? So please provide guidance on the status, if there is a manual build process can we get some docs to help us create the windows binaries? Thanks, we look forward to using Dapr :)

@msfussell @orizohar as we discussed before, I marked this issue as one of work item of 0.9.0 release.
cc/ @yaron2 @amanbha

We need to write up the specs for the below scenarios:

Deploy dapr control plane to linux nodes and deploy apps to windows and linux nodes
Deploy dapr control plane to windows nodes and deploy apps to windows and linux nodes

Expected work items:

[ ] Create Windows docker image and push them to dockerhub
[ ] Build CI pipeline for windows docker image
[ ] inject windows dapr image by Checking nodeSelector in deployment yaml - https://docs.microsoft.com/en-us/azure/aks/windows-container-cli#run-the-application
[ ] Expand E2E test environment to Windows node.

All subtasks are done. Closing epic.


Bump libs; drop java 8

Changes being made
Brief description of changes being made
Additional context
Please provide any context of the changes if needed

Addressed #126


Path to app in README.md

The path in the README.md to the application is
compass-webapp/
but that does not work. It should be
compass/

You are totally correct. Sorry for missing that. Fixed as per above commit.


Disabled class vs attribute (property)

Why is the .disabled class toggled instead of the element property disabled?

It's so the form can display all errors when a submit is attempted. If it
was truly disabled, the event wouldn't be triggered.
On Thursday, September 24, 2015, Zach Johnson<EMAIL_ADDRESS>wrote:

Why is the .disabled class toggled instead of the element property
disabled?
—
Reply to this email directly or view it on GitHub
https://github.com/1000hz/bootstrap-validator/issues/204.


feat: simplify mutations

Explanation
Simplify mutations.

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

Comparison is base (44d153c) 20.48% compared to head (fe64666) 20.48%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #306   +/-   ##
=======================================
  Coverage   20.48%   20.48%
=======================================
  Files          33       33
  Lines        2143     2143
=======================================
  Hits          439      439
  Misses       1678     1678
  Partials       26       26

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


[ldd-img] add iso attributes to Detector

Issue Type
Enhancement
Describe the issue identified (if applicable)
Missions are using more and more COTS cameras. Some of these have processing built in that needs to be identified in the label. In this case, the SACA camera for CADRE has an "iso" setting, analogous to gain, that should be reported.
This is similar to gain, except that the numbers are different.  So for example if ISO=100 is the default, ISO=200 means 2x the gain (DN's are twice as high), etc.  The IMG DD has gain_number which is a float multiplicative factor, and gain_mode_id which is a mission-dependent thing, but not an ISO setting.  ISO seems to be a fairly standard terminology for digital cameras.
Describe the solution you'd like
New class under Detector:
img:ISO .  child of Detector.  Definition: Specifies the ISO gain level set for the camera.
Attributes:
iso_number - int, cardinality 0:1, definition: The ISO gain number set for the camera.  The number has its origin in film sensitivity, so ISO 100 is a typical number for daylight scenes and higher numbers have more gain (and more noise).  This should generally conform to ISO 12232:2019 unless specified otherwise in iso_mode_id.
iso_mode_id card 0:1 - description of how ISO is used.  @crombie should assign a definition here.
Only one VICAR keyword, ISO
Describe alternatives you've considered
The values could be direct children of Detector rather than using an intervening ISO class.
Also considered GAIN_MODE_ID instead of ISO for VICAR, but why not be explicit.
Comments from Kate Crombie:
ISO sub-class with in the Detector class: After a bit of looking into what ISO is vs gain, I think that adding iso_number and iso_mode_id to an ISO class would be reasonable, where iso_number is the value and iso_mode_id is a description of how the mission defines and uses ISO (which according to my reading should conform to the specifications outlined in ISO 12232:2019, but :woman-shrugging:).  This addition should get a ticket on the LDD Issues page.
LDD Dictionary Version
none
PDS4 IM Version
n/a
Need-by Date
I need to know if this approach is acceptable by end of Nov (so I can change the vicar labels if needed). I won't need it actually in the DD until spring 2024 (flexible).
Additional context
nope

iso_mode_id should be optional and is defined as the mission specific definition of how the value is actually used.

ISO and attributes added to v<IP_ADDRESS>. I will look at adding the other ticket also.
Builds for testing here: https://github.com/pds-data-dictionaries/ldd-img/tree/release/<IP_ADDRESS>/build/development/c864d417002d6ee3e332da1cd6f198fd2d29abc7

LGTM, thanks!


Support iOS 8?

Hi, I saw the Doc says this lib supports iOS 8, but the podspec shows the project only supports iOS 10,which one is right?

Hello @dsmo I just download the project and work perfectly on iOS 8, if you tried and get problems please close this issue and open a new one with more information to help you.
see you

🤔 Maybe its because this line s.platform = :ios, '10.0' in KDIntroView.podspec ?

I just checking again and the there is another KDIntroView,podspec.json that says that the platform is 8.0, anyway, it seem that you need yo use 10.0, try changing the deployment target on your Xcode project configuration.


[FEATURE REQUEST]

Feature Request
Autotrain with hyperparameters (epochs, learning rate, etc) fine-tuning and base model selection
Motivation
The value proposition of autotrain is to have a model automatically trained without much manual fine tuning or manual model selection. The Autotrain product a few years back had this feature.
Additional Context
No response

yes, hopefully!


i18n and multiline strings

Hi, I'm enjoying so far using your lib!
One thing I'm not sure about is if multiline values coming from resource bundles are supported? More specifically - will new lines be preserved? In my case this seems to fail.
When I define:
foo.bar=Hi,\
there\
\
how are\
\
you?

and evaluate the template, i get Hi,therehow areyou? evaluated.
Any hint?
Thanks

Did you try to set newLineTrimming to false ?

private val engine: PebbleEngine = PebbleEngine.Builder().newLineTrimming(false).build()

I'm using that engine.

Maybe some tests can be added to https://github.com/PebbleTemplates/pebble/blob/master/pebble/src/test/java/com/mitchellbosecke/pebble/I18nExtensionTest.java#L24


Request: way to open/load an image from a File or file: URI

We have an image stored on the filesystem on our device. This image is not a pre-bundled asset. Instead, it comes from the camera, so it's created during runtime.
We saw NetworkImage and we tried to use a file: URI, but that resulted in an Unsupported 'file' in URI.
Not sure how yall want to solve this, but we have a file path, and we'd love to load this up as an image.
Thanks!

fyi @faisalabid

cc @Hixie

Addressed by https://github.com/flutter/flutter/pull/6853

Thanks @Hixie !


Warnings signed unsigned

This is part of PR #229

This has been rebased over master and updated to accommodate #407

This has been rebased over master do to merge conflicts.


Allow agreements to be cleared individually

The existing clear-signed-agreements.py script
will delete all the agreements for each supplier
in the given framework.
This adds the ability to specify certain suppliers
in that framework to target.
Related to the story to upload 2 new framework agreements: https://www.pivotaltracker.com/story/show/119371899

Personally I'd just have gone into S3 and deleted the files for two suppliers... but this looks like it will work.

It does feel a bit like over-egging the custard but I do need to set the flag for those suppliers too and I was going to go through the commands manually so though I should just extend this script.

This is missing work to only mark the flag for supplier on the list if its sent in. Closing until this is added.

I've rewritten it after chatting to @allait about the previous comment on the type conversion happening to the supplier_ids.
The script now includes validation of any ids sent in as options and keeps all ids in the supplier_ids list as ints.

👍


Rearrange partials

Code review for @diliger's branch that implements https://github.com/StarcounterPrefabs/Images/issues/49

Yesterday I was playing with this branch and noticed that few things don't work with Chatter. I will take a look into that today.
Another observation: I believe that partial URLs should match the object ID that you are passing to them.
 Can you fix this if you agree?

I agree about object names, but dont agree about pluralisation.
/images/partials/content/{Content ObjectID} - it is a single content, so why it should be plural? the same for edit.
/images/partials/illustrations/{Something ObjectID} - this is an url for multiple illustrations, so it is plural, but if i replace it with something then it is an url for a carousel of single something so it shouldn't be plural as well.

I have made a few adjustments to make Chatter work again.
Merging to develop. @aloscha you are now free to make your merge of changes from the SweOffshore-Checklist-UriMapping branch to develop.

Thanks @diliger once again!


[Please help] IE 11 not working inject store

I used lib version:
I trying to build and run my application on IE 11 with some tricks but not working.

Import @babel/polyfill
import proxy-polyfill
import es6-symbol/implement

I used lib version like below:
Mobx: 5.13.0
Mobx-React: 5.4.3

I'm trying to downgrade mobx 4 for support IE11. It's worked but mobx 4 don't re-render when I change properties observable.
Ex:
@observable tracks = {};
const media = this.tracks[userId].find(t => t.type === 'video')
try to modifier
media.muted = !media.muted;
It's not re-render component, but when I used mobx 5 it's worked.
So now I don't know do somethings for support IE 11 or fix issue re-render in mobx 4.
Somebody please help me.
Thanks you so much.

You have to use MobX 4 for IE 11 support - Proxies which are in MobX 5 cannot be polyfilled by any means.

@FredyC But when I used Mobx 4 for IE11, I've happen issue re-render.
Can you help me?
I've explain my issue in first post.

Please, provide a reproduction with eg. CodeSandbox.


Implement GeoJSON download

Before we implement live editing and addition of features, we'll need the GeoJSON download feature to be working for proper testing.

Done. Two more tickets will be raised for specific issues of implementation, though.


BooleanExpressionComplexityCheck  false positive detection

In following examples BooleanExpressionComplexityCheck issues were found by hyperstyle, but used boolean expressions are not really complicated.

for (int i = 0; i < a && b; i++) { ... }
if (i != j && a[i][j] != a[j][i]) { ... }
if (a == 0 && b == 0) { ... }
if (a >= b && b <= c) { ... }

Presumably the problem is in the parameter settings of java code quality analyzers.

Sorry, this is a hypestyle-analyze's tool bug. This issue can be closed.


        Options
        -------
        ftol : float
            Precision goal for the value of f in the stopping criterion.
        eps : float
            Step size used for numerical approximation of the Jacobian.
        disp : bool
            Set to True to print convergence messages. If False,
            `verbosity` is ignored and set to 0.
        maxiter : int
            Maximum number of iterations.
        finite_diff_rel_step : None or array_like, optional
            If `jac in ['2-point', '3-point', 'cs']` the relative step size to
            use for numerical approximation of `jac`. The absolute step
            size is computed as ``h = rel_step * sign(x0) * max(1, abs(x0))``,
            possibly adjusted to fit into the bounds. For ``method='3-point'``
            the sign of `h` is ignored. If None (default) then step is selected
            automatically.
        """
        _check_unknown_options(unknown_options)
        iter = maxiter - 1
        acc = ftol
        epsilon = eps

        if not disp:
            iprint = 0

        # Constraints are triaged per type into a dictionary of tuples
        if isinstance(constraints, dict):
            constraints = (constraints, )

        cons = {'eq': (), 'ineq': ()}
        for ic, con in enumerate(constraints):
            # check type
            try:
                ctype = con['type'].lower()
            except KeyError:
                raise KeyError('Constraint %d has no type defined.' % ic)
            except TypeError:
                raise TypeError('Constraints must be defined using a '
                                'dictionary.')
            except AttributeError:
                raise TypeError("Constraint's type must be a string.")
            else:
                if ctype not in ['eq', 'ineq']:
                    raise ValueError("Unknown constraint type '%s'." % con['type'])

            # check function
            if 'fun' not in con:
                raise ValueError('Constraint %d has no function defined.' % ic)

            # check Jacobian
            cjac = con.get('jac')
            if cjac is None:
                # approximate Jacobian function. The factory function is needed
                # to keep a reference to `fun`, see gh-4240.
                def cjac_factory(fun):
                    def cjac(x, *args):
                        if jac in ['2-point', '3-point', 'cs']:
                            return approx_derivative(fun, x, method=jac, args=args,
                                                     rel_step=finite_diff_rel_step)
                        else:
                            return approx_derivative(fun, x, method='2-point',
                                                     abs_step=epsilon, args=args)

                    return cjac
                cjac = cjac_factory(con['fun'])

            # update constraints' dictionary
            cons[ctype] += ({'fun': con['fun'],
                             'jac': cjac,
                             'args': con.get('args', ())}, )

        exit_modes = {-1: "Gradient evaluation required (g & a)",
                       0: "Optimization terminated successfully",
                       1: "Function evaluation required (f & c)",
                       2: "More equality constraints than independent variables",
                       3: "More than 3*n iterations in LSQ subproblem",
                       4: "Inequality constraints incompatible",
                       5: "Singular matrix E in LSQ subproblem",
                       6: "Singular matrix C in LSQ subproblem",
                       7: "Rank-deficient equality constraint subproblem HFTI",
                       8: "Positive directional derivative for linesearch",
                       9: "Iteration limit reached"}

        # Transform x0 into an array.
        x = asfarray(x0).flatten()

        # SLSQP is sent 'old-style' bounds, 'new-style' bounds are required by
        # ScalarFunction
        if bounds is None or len(bounds) == 0:
            new_bounds = (-np.inf, np.inf)
        else:
            new_bounds = old_bound_to_new(bounds)

        # clip the initial guess to bounds, otherwise ScalarFunction doesn't work
        x = np.clip(x, new_bounds[0], new_bounds[1])

        # Set the parameters that SLSQP will need
        # meq, mieq: number of equality and inequality constraints
        meq = sum(map(len, [atleast_1d(c['fun'](x, *c['args']))
                  for c in cons['eq']]))
        mieq = sum(map(len, [atleast_1d(c['fun'](x, *c['args']))
                   for c in cons['ineq']]))
        # m = The total number of constraints
        m = meq + mieq
        # la = The number of constraints, or 1 if there are no constraints
        la = array([1, m]).max()
        # n = The number of independent variables
        n = len(x)

        # Define the workspaces for SLSQP
        n1 = n + 1
        mineq = m - meq + n1 + n1
        len_w = (3*n1+m)*(n1+1)+(n1-meq+1)*(mineq+2) + 2*mineq+(n1+mineq)*(n1-meq) \
                + 2*meq + n1 + ((n+1)*n)//2 + 2*m + 3*n + 3*n1 + 1
        len_jw = mineq
        w = zeros(len_w)
        jw = zeros(len_jw)

        # Decompose bounds into xl and xu
        if bounds is None or len(bounds) == 0:
            xl = np.empty(n, dtype=float)
            xu = np.empty(n, dtype=float)
            xl.fill(np.nan)
            xu.fill(np.nan)
        else:
            bnds = array(bounds, float)
            if bnds.shape[0] != n:
                raise IndexError('SLSQP Error: the length of bounds is not '
                                 'compatible with that of x0.')

            with np.errstate(invalid='ignore'):
                bnderr = bnds[:, 0] > bnds[:, 1]

            if bnderr.any():
                raise ValueError('SLSQP Error: lb > ub in bounds %s.' %
                                 ', '.join(str(b) for b in bnderr))
            xl, xu = bnds[:, 0], bnds[:, 1]

            # Mark infinite bounds with nans; the Fortran code understands this
            infbnd = ~isfinite(bnds)
            xl[infbnd[:, 0]] = np.nan
            xu[infbnd[:, 1]] = np.nan

        # ScalarFunction provides function and gradient evaluation
        sf = _prepare_scalar_function(func, x, jac=jac, args=args, epsilon=eps,
                                      finite_diff_rel_step=finite_diff_rel_step,
                                      bounds=new_bounds)

        # Initialize the iteration counter and the mode value
        mode = array(0, int)
        acc = array(acc, float)
        majiter = array(iter, int)
        majiter_prev = 0

        # Initialize internal SLSQP state variables
        alpha = array(0, float)
        f0 = array(0, float)
        gs = array(0, float)
        h1 = array(0, float)
        h2 = array(0, float)
        h3 = array(0, float)
        h4 = array(0, float)
        t = array(0, float)
        t0 = array(0, float)
        tol = array(0, float)
        iexact = array(0, int)
        incons = array(0, int)
        ireset = array(0, int)
        itermx = array(0, int)
        line = array(0, int)
        n1 = array(0, int)
        n2 = array(0, int)
        n3 = array(0, int)

        # Print the header if iprint >= 2
        if iprint >= 2:
            print("%5s %5s %16s %16s" % ("NIT", "FC", "OBJFUN", "GNORM"))

        # mode is zero on entry, so call objective, constraints and gradients
        # there should be no func evaluations here because it's cached from
        # ScalarFunction
        fx = sf.fun(x)
        try:
            fx = float(np.asarray(fx))
        except (TypeError, ValueError):
            raise ValueError("Objective function must return a scalar")
        g = append(sf.grad(x), 0.0)
        c = _eval_constraint(x, cons)
        a = _eval_con_normals(x, cons, la, n, m, meq, mieq)

        while 1:
            # Call SLSQP
            slsqp(m, meq, x, xl, xu, fx, c, g, a, acc, majiter, mode, w, jw,
                  alpha, f0, gs, h1, h2, h3, h4, t, t0, tol,
                  iexact, incons, ireset, itermx, line,
>                 n1, n2, n3)
E           ValueError: failed to initialize intent(inout) array -- input 'O' not compatible to 'd'
/usr/local/lib/python3.7/site-packages/scipy/optimize/slsqp.py:419: ValueError

Scipy/Numpy/Python version information:
numpy              1.18.1
scipy              1.5.0

Might be caused by the bounds which have arrrays in them. This worked in 1.4.x but not in 1.5.0.
bounds = [(-inf, inf), (array([4.61883478e-06]), array([4.61887937]))]

The following MWE gives the same ValueError:
import numpy as np
from scipy.optimize import minimize, rosen

x0 = np.array([0.01036698, 0.46188348])
bounds = [(-np.inf, np.inf), (np.array([4.61883478e-06]), np.array([4.61887937]))]

minimize(rosen, x0, bounds=bounds, method='slsqp')

However, there is also a VisibleDeprecationWarning which originates from numpy which your CI might miss:
/Users/andrew/miniconda3/envs/dev3/lib/python3.8/site-packages/scipy/optimize/_constraints.py:317: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
  lb = np.array([x if x is not None else -np.inf for x in lb])
/Users/andrew/miniconda3/envs/dev3/lib/python3.8/site-packages/scipy/optimize/_constraints.py:318: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
  ub = np.array([x if x is not None else np.inf for x in ub])

The offending code is:
>>> lb, ub = zip(*bounds)
>>> print(lb)
(-inf, array([4.61883478e-06]))
>>> lb = np.array([x if x is not None else -np.inf for x in lb])
>>> repr(lb)
'array([-inf, array([4.61883478e-06])], dtype=object)'

I'm guessing on a previous version of numpy lb.dtype would've been np.float64. Now it's an object.
There are two ways of proceeding here.

The original code is cleaned up.
The scipy code is amended to something like lb = np.array([float(x) if x is not None else -np.inf for x in lb]).

I have a preference for 1. The only thing stopping recommending 2. as well is that it enables the behaviour that the numpy VisibleDeprecationWarning was trying to prevent in the first place.

I think the best thing would be for scipy to raise TypeError on the invalid
bounds array.  That would have made it immediately clear that I was doing
the wrong thing. I have already fixed my library by squeezing to a float
before constructing the bounds.
On Thu, Jun 25, 2020, 00:07 Andrew Nelson<EMAIL_ADDRESS>wrote:

The following MWE gives the same ValueError:
import numpy as np
from scipy.optimize import minimize, rosen
x0 = np.array([0.01036698, 0.46188348])
bounds = [(-np.inf, np.inf), (np.array([4.61883478e-06]), np.array([4.61887937]))]
minimize(rosen, x0, bounds=bounds, method='slsqp')
However, there is also a VisibleDeprecationWarning which originates from
numpy which your CI might miss:
/Users/andrew/miniconda3/envs/dev3/lib/python3.8/site-packages/scipy/optimize/_constraints.py:317: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
lb = np.array([x if x is not None else -np.inf for x in lb])
/Users/andrew/miniconda3/envs/dev3/lib/python3.8/site-packages/scipy/optimize/_constraints.py:318: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
ub = np.array([x if x is not None else np.inf for x in ub])
The offending code is:

lb, ub = zip(*bounds)
print(lb)
(-inf, array([4.61883478e-06]))
lb = np.array([x if x is not None else -np.inf for x in lb])
repr(lb)
'array([-inf, array([4.61883478e-06])], dtype=object)'

I'm guessing on a previous version of numpy lb.dtype would've been
np.float64. Now it's an object.
There are two ways of proceeding here.

The original code is cleaned up.
The scipy code is amended to something like lb = np.array([float(x)
if x is not None else -np.inf for x in lb]).

I have a preference for 1. The only thing stopping recommending 2. as well
is that it enables the behaviour that the numpy VisibleDeprecationWarning
was trying to prevent in the first place.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/issues/12422#issuecomment-649119257, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKTSRN56PJM5UNSJ3YYWWDRYKBLRANCNFSM4OGXYSQQ
.

What would be the best way of checking this? Presumably lb and ub could contain any int/float/float64, but not complex/object.

I would guess int, float, np.integer or np.floating might all be OK. Pretty
much anything that can be cast to double.
On Thu, Jun 25, 2020, 00:18 Andrew Nelson<EMAIL_ADDRESS>wrote:

What would be the best way of checking this? Presumably lb and ub could
contain any int/float/float64, but not complex/object.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/issues/12422#issuecomment-649122621, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKTSRNE7GWP47QVRCEBQ53RYKCS5ANCNFSM4OGXYSQQ
.

I think we should just cast the items to Python floats, given that all the algorithms anyway work in float. In Numpy, 1-element arrays have always been castable to float; there are plans in Numpy to deprecate this, and I believe we should leave this deprecation as something for Numpy to do instead of trying to do it piecemeal in different places in Scipy. Moreover, this is a backward compat break and I'd rather restore the previous behavior than do deprecation cycles with this on our side.
gh-12437


When multiple items are selected the options shows in second line.

When multiple options are selected which actually adds up to a width greater than the container field which holds the options, then options shows in second line.
Is there an option to show message saying, +2 options for example.

Such an option is not available. I'll add it as feature request, but there are quit some others with higher priority, so I don't expect this to be implemented soon, definitely not in the 1.0.0 version.


Add robust _antidote completions

See title.
Also, move #58 into this issue and close as dupe.

https://github.com/mattmc3/antidote/issues/58#issue-1360882088


Fixed foundry solc config to match hardhat compile bytecode

Describe Changes
Changes performed:

The main objective was to get the same deployedBytecode when compiling with foundry, than we have when doing so with hardhat. We changed the solidity compiler options on foundry to match the hardhat ones.
Modified the deploy scripts to get the correct HolographGenesis when deploying in localhost

Checklist before requesting a review

[x] I have performed a self-review of my code
[x] Code styles have been enforced
[ ] All Hardhat tests are passing

I apply the merge


Change gem & repo name to underscore casing to match ruby idioms?

The gem name is currently EmojifyRspecFormatter. It is more idiomatic ruby to use underscore case or dashes for gem names instead of camel case. This would make the gem name emojify_rspec_formatter or emojify-rspec-formatter.
It's also better if the repo name (macebake/emojify-rspec_formatter) matches the gem name, so the gem to add to the Gemfile is more guessable and consistent.
These are minor things though! The gem looks cool.

Good point! All fixed! 😍


React slick adding slick-list class to slick-arrow

Hi, this is my slider config:
slidesToShow: 4,
slidesToScroll: 4,
initialSlide: 0,
dots: false,
infinite: false,
responsive: [
  {
    breakpoint: BREAKPOINT_XL,
    settings: {
      dots: false
    }
  },
  {
    breakpoint: BREAKPOINT_LG,
    settings: {
      slidesToShow: 4,
      slidesToScroll: 4,
      dots: false
    }
  },
  {
    breakpoint: BREAKPOINT_MD,
    settings: {
      slidesToShow: 2,
      slidesToScroll: 2,
      dots: false
    }
  },
  {
    breakpoint: BREAKPOINT_SM,
    settings: {
      slidesToShow: 1,
      slidesToScroll: 1,
      dots: false
    }
  }
]

I am using custom arrows for slider:
export const NextArrowCustom = props => {
  const { className, onClick } = props;
  return (
    <StyledCustomArrow className={className} onClick={onClick}>
      <StyledArrowIcon className="nc-ic_keyboard_arrow_right_48px" />
    </StyledCustomArrow>
  );
};

On smallest breakpoint for unknown reason react-slick id adding slick-list class to arrow component.
When there is more then 4 items in slider it works as expected.
Thanks.

same problem here. My config contains following:
  nextArrow: <CardSliderArrow />,
  prevArrow: <CardSliderArrow />,

CardSliderArrow:
const CardSliderArrow = ({ onClick }) => {
  return (
    <CardSliderArrowStyled {...{ onClick }}>
      Arrow Here
    </CardSliderArrowStyled>
  );
};

but I finally Ive got these:
https://cl.ly/51b9787b94d8
highlighted line and there is an arrow

try to replace the first tag of arrow with "non-div" tag.
it would be just fine~


PRs can sometimes take a long time to merge

Something I noticed with the following two pull requests, which were opened 8 and 10 hours ago respectively https://github.com/chaosbot/Chaos/pull/280 https://github.com/chaosbot/Chaos/pull/278, but still hadn't merged.  Both PRs have a single commit, but Chaos was saying their voting window ended at the same time, despite the PRs being opened hours apart.
Digging into the merge_commit_sha 630d9e50a30d6bbcc1ca7fa4639628b88d5231ee (which we use for "reliable" branch push times) for #278:
 'commit': {'author': {'date': '2017-05-26T17:28:44Z',
                       'email'<EMAIL_ADDRESS>                       'name': 'Phil Rukin'},
            'comment_count': 0,
            'committer': {'date': '2017-05-26T17:28:44Z',
                          'email'<EMAIL_ADDRESS>                          'name': 'GitHub'},
            'message': 'Merge ae12b7022a2b81fca5e0b4bed22baaf4b9c55aa0 into '
                       'd1cfad21414e019975c4a316faad20029b9afe07',
            'tree': {'sha': '46ad01b78c0194e5a8399cd5a7b8c13d76853cc5',
                     'url': 'https://api.github.com/repos/chaosbot/Chaos/git/trees/46ad01b78c0194e5a8399cd5a7b8c13d76853cc5'},
            'url': 'https://api.github.com/repos/chaosbot/Chaos/git/commits/630d9e50a30d6bbcc1ca7fa4639628b88d5231ee'},

And comparing to #278's single commit ae12b7022a2b81fca5e0b4bed22baaf4b9c55aa0:
  'commit': {'author': {'date': '2017-05-26T10:07:13Z',
                        'email'<EMAIL_ADDRESS>                        'name': 'Phil Rukin'},
             'comment_count': 0,
             'committer': {'date': '2017-05-26T10:07:13Z',
                           'email'<EMAIL_ADDRESS>                           'name': 'Phil Rukin'},
             'message': 'Add homepage to the repo\n'
                        'See github api docs here: '
                        'https://developer.github.com/v3/repos/#edit',
             'tree': {'sha': 'e68d1cb57377f02e69f8ae9bf16501a4b1f506c1',
                      'url': 'https://api.github.com/repos/chaosbot/Chaos/git/trees/e68d1cb57377f02e69f8ae9bf16501a4b1f506c1'},

It looks like the Github may sometimes have a significant delay between a push to a PR and the merge_commit_sha existing.  In this case, it was over 7 hours(!)  I did the same comparison for #280, and the merge_commit_sha f0fd79b4a4e87cfa5fd137c01cae52b3cd282d66 has the exact same timestamp as the one from #278, 630d9e50a30d6bbcc1ca7fa4639628b88d5231ee.  This would suggest that maybe Github's merge commit job runner had died, restarted hours later, and crunched through the pending merge test jobs.
So maybe this isn't something to worry about yet, but it may be important to keep in mind if people wonder why their PRs are taking so long

In the time it took me to write that, the merge commit for #278 got reset again 6a8e6b4e20d023e183f15ba18dc22ab7fca0e99d and pushed the voting window back, for no apparent reason:
 'commit': {'author': {'date': '2017-05-26T20:28:45Z',
                       'email'<EMAIL_ADDRESS>                       'name': 'Phil Rukin'},
            'comment_count': 0,
            'committer': {'date': '2017-05-26T20:28:45Z',
                          'email'<EMAIL_ADDRESS>                          'name': 'GitHub'},
            'message': 'Merge ae12b7022a2b81fca5e0b4bed22baaf4b9c55aa0 into '
                       '4cae365b4094bc9ce73635a46bcb4cfbe58d1e0e',
            'tree': {'sha': '7f9081fb6075e21c7ccf1cbb1ea48c4edee72dcf',
                     'url': 'https://api.github.com/repos/chaosbot/Chaos/git/trees/7f9081fb6075e21c7ccf1cbb1ea48c4edee72dcf'},
            'url': 'https://api.github.com/repos/chaosbot/Chaos/git/commits/6a8e6b4e20d023e183f15ba18dc22ab7fca0e99d'},

I think the merge_commit_sha stuff might need to be reverted?  Wish I had a github contact :)

@amoffat Tell me If I can help in any way ^_^
P.S. I actually wanted to ask why this is happening, but I've seen some PRs related to change of voting window and thought it's related.
P.P.S Is it possible that it's because I'm in CET(GMT+2 right now)?

@phil-r thank you!  I think you are fine, this is probably an issue with github :)  I've reached out to them to see if they know what's going on.  If I don't hear from them soon, I'll revert the changes that introduced this problem.  Then your stuff should merge in a more timely manner

I know why the temp merge_commit_sha keeps resetting... it has to reset each time master gets a push, not just the branch backing the PR.  So what was happening was, one PR would get merged in, causing all PRs to reset their vote window.  Then another PR would get merged in, etc.  Bad.  Reverting #271


v2.0.0-beta3 - Master node not identified in imported cluster

Rancher versions:
rancher/server: 2.0.0-beta3
rancher/agent: 2.0.0-beta3
Infrastructure Stack versions:
network-services: calico
kubernetes: 1.10.1
Docker version:
17.03.2
Operating system and kernel:
CentOS 7.4 x86_64
Type/provider of hosts:
Bare-metal/KVM
Setup details:
Single node Rancher
Cluster created with kubeadm 1.10.1 (1 master, 6 workers)
Steps to Reproduce:

Create cluster with kubeadm (calico network)
Import cluster into Rancher 2.0
Verify nodes

Results:
Master node shows up having "Worker" role

Additional info:
# kubectl get nodes -o wide
NAME      STATUS    ROLES     AGE       VERSION   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION               CONTAINER-RUNTIME
i-0050.   Ready     master    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0051.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0052.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0053.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0054.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0055.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2
i-0056.   Ready     <none>    1d        v1.10.1   <none>        CentOS Linux 7 (Core)   3.10.0-693.21.1.el7.x86_64   docker://17.3.2

# kubectl describe node i-0050.
Name:               i-0050.

Capacity:
 cpu:                2
 ephemeral-storage:  83873664Ki
 hugepages-2Mi:      0
 memory:             3881696Ki
 pods:               110
Allocatable:
 cpu:                2
 ephemeral-storage:<PHONE_NUMBER>5
 hugepages-2Mi:      0
 memory:             3779296Ki
 pods:               110
System Info:
 Machine ID:
 System UUID:
 Boot ID:
 Kernel Version:             3.10.0-693.21.1.el7.x86_64
 OS Image:                   CentOS Linux 7 (Core)
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  docker://17.3.2
 Kubelet Version:            v1.10.1
 Kube-Proxy Version:         v1.10.1
PodCIDR:                     <IP_ADDRESS>/24
ExternalID:                  i-0050.
Non-terminated Pods:         (9 in total)
  Namespace                  Name                                                      CPU Requests  CPU Limits  Memory Requests  Memory Limits
  ---------                  ----                                                      ------------  ----------  ---------------  -------------
  kube-system                calico-etcd-pvhzx                                         0 (0%)        0 (0%)      0 (0%)           0 (0%)
  kube-system                calico-kube-controllers-5d77565b59-t9c4w                  0 (0%)        0 (0%)      0 (0%)           0 (0%)
  kube-system                calico-node-98qph                                         250m (12%)    0 (0%)      0 (0%)           0 (0%)
  kube-system                etcd-i-0050.                       0 (0%)        0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-apiserver-i-0050.             250m (12%)    0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-controller-manager-i-0050.    200m (10%)    0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-dns-86f4d74b45-g5kjc                                 260m (13%)    0 (0%)      110Mi (2%)       170Mi (4%)
  kube-system                kube-proxy-jp4xj                                          0 (0%)        0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-scheduler-i-0050.             100m (5%)     0 (0%)      0 (0%)           0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests  CPU Limits  Memory Requests  Memory Limits
  ------------  ----------  ---------------  -------------
  1060m (53%)   0 (0%)      110Mi (2%)       170Mi (4%)
Events:         <none>

@alena1108 - I talked with Darren and he would like the roles to be returned in general for imported clusters.

@sangeethah the test case that we really want to verify is that when we start a HA cluster, you'd be able to see the roles for the "local" cluster.

Tested with v2.0.0-rc1.  The nodes displayed the roles as expected


Coder Camps inappropriately links to Code Platoon

In: src/scenes/home/codeSchools/partnerSchools/partnerSchools.js
Coder Camps' link under “Partnered Schools” on operationcode.org’s website links to Code Platoon. Needs to be directed to http://www.operationcodercamps.com/.

I'm looking to start contributing here. I can handle this if no one is working it. Should be a quick and easy fix.

All yours!

Ok, I've updated the link and created the PR. I think I've done everything correctly, but this is my first ever commit/pr so if I've messed up something, or not followed a step please let me know so I can change that going forward (I want to keep contributing here!)


Request for explicit proxy support

Jean-Baptiste MARCILLE-ext requested explicit proxy support, to resolve issue with:
...
<IP_ADDRESS>:8080 - [2022-09-16T19:08:24.308Z] GET:/ 200 1.221ms
[POST] https://fgt.pharmaledger.pdmfc.com/bricking/traceability/put-brick Error: connect ETIMEDOUT <IP_ADDRESS>:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -110,
  code: 'ETIMEDOUT',
  syscall: 'connect',
  address: '[<IP_ADDRESS>](http://<IP_ADDRESS>/)',
  port: 443
}
...

19 de setembro de 2022 07:08
·         curl -k –noproxy ‘*’ -XGET https://fgt.pharmaledger.pdmfc.com/ fails because of a timeout
·         curl -k -XGET  https://fgt.pharmaledger.pdmfc.com/ indeed returns the homepage (http(s)_proxy environment variables are set in the pod and curl uses them)
19 de setembro de 2022 14:39

What I can do is forward your question to the OpenDSU team, so I am sending this email to Sinica.
What is the proper way to configure and run an apihub so that all OpenDSU operations use an explicit http(s) proxy for some domains ?
(Seems that nodejs does not honor the http(s)_proxy environment variables transparently).

The OpenDSU team suggested the following workaround:

    create a new proxy service http://my-proxy/*  statically configured to proxy all requests to [https://fgt.pharmaledger.pdmfc.com/](https://fgt.pharmaledger.pdmfc.com/any-path)* (adjust local name, port number, etc, as needed.)
    (This could be done creating a new pod to run nginx or apache or other proxy software of your preference, in the same network as your MAH pod).
    inside the MAH runing container files, the file /fgt-workspace/apihub-root/external-volume/config/bdns.hosts should currently have

"traceability": {
    "replicas": [],
    "brickStorages": [
      "https://fgt.pharmaledger.pdmfc.com"
    ],
    "mqEndpoints": [
       "https://fgt.pharmaledger.pdmfc.com/"
    ],
    "anchoringServices": [
      "https://fgt.pharmaledger.pdmfc.com/"
    ],
    "notifications": [
      "https://fgt.pharmaledger.pdmfc.com/"
    ]
  },

Replace those entries with

"traceability": {
    "replicas": [],
    "brickStorages": [
      "http://my-proxy"
    ],
    "mqEndpoints": [
       "http://my-proxy/"
    ],
    "anchoringServices": [
      "http://my-proxy/"
    ],
    "notifications": [
      "http://my-proxy/"
    ]
  },

(I guess that this can be done on your private helm-charts configuration files).

Best regards,


Arch/Manjaro install

Hello,
I'm unaware of any guide to install on Arch based systems. Will I need to build it from scratch or does anyone have a guide to install and get this running on Arch?

You can simply install opencl-amd-dev from the AUR or miopen-hip from community-testing.


Create NI-FGEN Standard Function Example

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Creates an NI-FGEN example to demonstrate the use of the new session management API with NI-FGEN, generates a waveform using standard function mode.
Why should this Pull Request be merged?
AB#2533780: Create Standalone MeasurementLink NI-Fgen Example
What testing has been done?
Able to run the example in InstrumentStudio and MeasurementUI Editor with a persistent simulated device.

Measurement Configuration:

Measurement Results:

Measurement Logic:

FGEN Logic:

Measurement UI:

InstrumentStudio:

MeasurementUI Editor:

I noticed that the driver definitions for enum-like controls (in this case waveform-type) are defined as rings types even if they satisfy the conditions for an enum (sequential ordering starting at val = 0). The LabVIEW service only supports auto-annotating enum types which means we won't be able to get auto-populating behavior if we use the driver defined type. We could still use the driver type but without the annotations it will show up in TestStand as a numeric instead of a ComboBox with selectable values and to get a ComboBox in .measui you would need to define a ring control for it in UI Editor.
For now in this example I've chosen to create my own enum type that maps to the values of the driver type but this is really just a workaround. We should  consider adding support for auto-annotating LabVIEW ring types if we want to support driver rings natively.

I'm assuming we'll also want a TestStand .seq file as well. The existing DCPower example has some nontrivial helper VIs for setting up pinmap and sessions and I'm not sure where they came from. If our plan is to just copy these VIs into other examples then I can do that as part of this PR, otherwise I'll wait to get more info on how we want to handle that.

I'd suggest modifying the Document tab width and height so the white box around the controls is smaller.

I'd suggest modifying the Document tab width and height so the white box around the controls is smaller (in the .meaui).

Fixed:

I'm assuming we'll also want a TestStand .seq file as well. The existing DCPower example has some nontrivial helper VIs for setting up pinmap and sessions and I'm not sure where they came from. If our plan is to just copy these VIs into other examples then I can do that as part of this PR, otherwise I'll wait to get more info on how we want to handle that.

There will be some discussions about API changes for TestStand code modules happening soon. Ultimately, I would like to centralize a lot of this code into a pin map service client library and the session management library. However, none of that work has been captured or planned yet so I'm not sure how much we'll get done before release. Hopefully there will be better guidance on this by the end of the week.

Also make sure you try building the measurement into an exe and running it that way. You don't necessarily have to run it as a static measurement. You can just build it into an exe, run it, and then open it using InstrumentStudio.

Also make sure you try building the measurement into an exe and running it that way. You don't necessarily have to run it as a static measurement. You can just build it into an exe, run it, and then open it using InstrumentStudio.

I had to modify the build spec to include the additional files I added but I was able to open and run inside of InstrumentStudio after doing that.


feat: provide a pluggable logging abstraction and some refactoring

This PR was meant to help fixing https://github.com/dylibso/chicory/issues/151 but it turned out to be a little bit more invasive than expected so a number of other things have also been amended.
The main change is the introduction of a module builder:
var module = Module.builder("my-module.wasm")
    .withLogger(new MyLogger())
    .withType(ModuleType.TEXT)
    .build()

This would allow to easily add further configuration options later on.
Also the builder is in charge to read the actual module bits (from File, Path, byte[], classpath, ect) instead of delegating it to the Parser class.
Let me know if it goes to far.

Thanks you! I think changing the public API will add a little more scrutiny but I think it's the correct direction. We probably want to apply a builder pattern on some of these public classes because there will increasingly be more options for constructing and validating them and this is the most flexible API choice.
Will leave it to @andreaTP to say if the pattern fits our other builder patterns.

I like the direction, it is a good enhancement over the current API, but I want to review this PR carefully as it's growing on the big side.
@lburgazzoli let me know when you think you are close to the end 👍

no additional changes expected in this pr to avoid making it a bigger monster:)
will open new prs as follow up

Sounds good! Can you have a look at the CI? Seems like something accidentally broke 😢

Sounds good! Can you have a look at the CI? Seems like something accidentally broke 😢

ok, ci is happy now

Apologies about all the code changing underneath it. We've been merging a lot of small changes the past couple days.

Apologies about all the code changing underneath it. We've been merging a lot of small changes the past couple days.

no worries, can you double check to verify I've not made any mistake while rebasing and fixing conflicts ?

Reminder: we should follow up with a small readme section about how to use this when we get the chance. Not urgent though!

For the Module builder pattern change i think this small change takes care of it: https://github.com/dylibso/chicory/pull/191


Does async validation works after update to beta?

Hi guys.
I used your example from here in order to implement dynamic async validaton.
After I've updated my angular to beta I have the next issue:

I created async validation directive (attribute, gets control from arguments);
On document ready this validation runs, but I prevent it execution because the input is untouched yet;
But on input change it doesn't run.

I tried to do it with running validate method using OnChange interface and ngOnChange method - no results.
If I use composeAsync my control.errors is broken because it becomes not a plain JS object as it should be, but the promise.
Please, help.
Here is my directive's code:
import {
  provide,
  Directive,
  OnInit,
  ElementRef,
} from 'angular2/core';
import {
    NG_ASYNC_VALIDATORS,
    Control,
    Validator
} from 'angular2/common';

@Directive({
  selector: '[duration]',
  properties: [
    'notParsedValue: duration',
    'message: durationMsg',
    'control: ngControl'
  ],
  providers: [
    provide(NG_ASYNC_VALIDATORS, {
      useExisting: Duration,
      multi:       true
    })
  ]
})
export class Duration implements Validator, OnInit {
  public notParsedValue: string;
  public message: string = 'File duration is invalid';
  public control: Control;

  // some inner logic here ...

  /**
   *
   * @param control
   * @returns {Promise<T>}
   */
  validate(control: Control): {[key: string]: any} {
    console.log('Duration validator running');
    return new Promise( resolve => {

      if (this._doesInputFilled(this.control) && this._shouldRun()) {
        this._validate(this.control.value).then(resolve, err => {
          this._addError(err);
          resolve(err);
        });
      } else {
        resolve(null);
      }

    });

  };

  /**
   *
   * @param element
   */
  constructor(element:ElementRef) {
    this._element    = element;
    // ...
  }

  /**
   *
   */
  ngOnInit() {
    console.log('Duration directive OnInit', this);
    // ...
  }

}

@pkantsedalov As far as I can see from the running app, the async validation is still working. It must be your implementation logic that might be broken.

Thanks for response.
I found the next one inside my root app:
public onChange(event) {
    let val = this.flags['isMultiple'] ? event.target.files : event.target.files.item(0);

    this._fileInputControl.updateValue(val);
    this._fileInputControl.markAsDirty();
}

updateValue runs sync validators but doesn't run async.
Do you know anything about this case?

Also, I can see missing logic here, so there is no way for me to tell what you are doing wrong. Make sure that the validate() {} method returns something like:
validate(control: Control): {[key: string]: any} {
    return new Promise((resolve) => {
        resolve(
            isSomethingWrong
                ? {'validatorKey': true}
	        : null
            );
    });
}

Here is the validate method
validate(control: Control): {[key: string]: any} {
    console.log('Duration validator running');
    return new Promise( resolve => {

      if (this._doesInputFilled(this.control) && this._shouldRun()) {
        this._validate(this.control.value).then(resolve, err => {
          this._addError(err);
          resolve(err);
        });
      } else {
        resolve(null);
      }

    });

  };

But even this line
console.log('Duration validator running');

is not run.

Why are you using markAsDirty()? Are you doing anything special there? Unless you specifically turned off change detection on that component/directive, things should update. Though, I can see you are using a file input, so things might be different.

Are you adding the Duration as a directive dependency as such? And are you sure there one of [ngControl], [ngFormControl], [ngModel] on the same element?

Yep, I'm working with file input.
And yep, Duration directive has [ngControl] on its element and is included inside the script.
And now I've tried this inside my Duration directive:
ngOnInit() {
  // here is Control instance
  this.control.registerOnChange(this.validate.bind(this)); // this.validate - is async validator I need to run
}

And it works after
this.control.updateValue(...);

Strange, because in alpha validation's run straight after input change, not after updateValue() run.

Ok, lets summarize:

I have the next template (generally):

<my-input-file duration="{duration}" durationMessage="{durationMessage}"></my-input-file>

I have the next root component template:

<input type="file" duration="{durationValue}" />

I have the next code of my root component MyInputFile:

import {
  Component,
  OnInit,
  ElementRef,
} from 'angular2/core';
import {
    FORM_DIRECTIVES,
    CORE_DIRECTIVES,
    Control,
    Validator
} from 'angular2/common';

@Component({
  selector: '[my-file-input]',
  input: [
    'duration: duration',
    'durationMessage: durationMsg',
    'control: ngControl'
  ]
})
export class MyInputFile implements OnInit {
  public duration: string;
  public durationMessage: string = 'File duration is invalid';
  public control: Control;

  // some inner logic here ...

  /**
   *
   * @param element
   */
  constructor(element:ElementRef) {
    this._element    = element;
    // ...
  }

/**
   *
   * @param event
     */
  public onChange(event) {
    let val = this.flags['isMultiple'] ? event.target.files : event.target.files.item(0);

    // WITHOUT THAT ANY ANOTHER DIRECTIVE - SYNC ONE - DOESN'T RUN
    this.control.updateValue(val, {
      onlySelf: true,
      emitEvent: true,
      emitModelToViewChange: true
    });
    this._fileInputControl.markAsDirty();
  }

  /**
   *
   */
  ngOnInit() {
    console.log('Duration directive OnInit', this);
    // ...
  }

}

I have the next code of my duration directive:

import {
  provide,
  Directive,
  OnInit,
  ElementRef,
} from 'angular2/core';
import {
    NG_ASYNC_VALIDATORS,
    Control,
    Validator
} from 'angular2/common';

@Directive({
  selector: '[duration]',
  properties: [
    'notParsedValue: duration',
    'message: durationMsg',
    'control: ngControl'
  ],
  providers: [
    provide(NG_ASYNC_VALIDATORS, {
      useExisting: Duration,
      multi:       true
    })
  ]
})
export class Duration implements Validator, OnInit {
  public notParsedValue: string;
  public message: string = 'File duration is invalid';
  public control: Control;

  // some inner logic here ...

  /**
   *
   * @param control
   * @returns {Promise<T>}
   */
  validate(control: Control): {[key: string]: any} {
    console.log('Duration validator running');
    return new Promise( resolve => {

      if (this._doesInputFilled(this.control) && this._shouldRun()) {
        this._validate(this.control.value).then(resolve, err => {
          this._addError(err);
          resolve(err);
        });
      } else {
        resolve(null);
      }

    });

  };

  /**
   *
   * @param element
   */
  constructor(element:ElementRef) {
    this._element    = element;
    // ...
  }

  /**
   *
   */
  ngOnInit() {
    console.log('Duration directive OnInit', this);
    // ONLY THIS WAY RUNS THE VALIDATION ON INPUT CHANGE
    this.control.registerOnChange(this.validate.bind(this));
  }

}

I am closing this as it is not an issue with this code base. I'm sorry I cannot help you with your problem, but I would suggest starting in a fresh plunk or something and having as little code as possible in order to track the problem you are having.

Thanx a lot man!
On Fri, Jan 29, 2016 at 9:01 PM, Roland Groza<EMAIL_ADDRESS>wrote:

Closed #46 https://github.com/rolandjitsu/ng2-lab/issues/46.
—
Reply to this email directly or view it on GitHub
https://github.com/rolandjitsu/ng2-lab/issues/46#event-531754150.


Use CMAKE_SYSTEM_PROCESSOR to check for SIMD support options

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

Maybe this fixes issue #3482.


Add docs

convert llmariner/docs using pandoc

Looks like subsections are sorted in the alphabetical order

hmm, not sure where the configuration exists. @Ladicle , could you please take a look?

The order can change by the weight of the page metadata. Some pages have already set the weight in the top of the file, surrounded ---------.

Ah I see!


Disable no-commit-to-branch in GitHub Actions

We are usually merging to protected branches when running GHA, so it should be disabled. Otherwise, checks will always fail on the default branch.

The checks succeeded after merging, so it's all good!


Kubernetes Version Configurability per Worker Pool

How to categorize this PR?

/area usability
/kind enhancement
/platform equinix-metal
/merge squash
What this PR does / why we need it:
This PR implements support for gardener/gardener's WorkerPoolKubernetesVersion feature gate. Since there are neither CSI migration nor any Kubernetes version specific constraints in the kubelet configuration, the only task is documenting that it supports the feature with the next release.
Which issue(s) this PR fixes:
Part of gardener/gardener#3501
Special notes for your reviewer:
✅ ~Depends on #188, hence, PR is in draft state.~
Release note:

This extension does now support `gardener/gardener`'s `WorkerPoolKubernetesVersion` feature gate, i.e., having [worker pools with overridden Kubernetes versions](https://github.com/gardener/gardener/blob/8a9c88866ec5fce59b5acf57d4227eeeb73669d7/example/90-shoot.yaml#L69-L70).

/ready


File size

Is it possible to get file size without downloading the file?

You could try using svnlook http://svnbook.red-bean.com/en/1.7/svn.ref.svnlook.c.filesize.html

Thanks.


muting_ui: Fix bug with same name of function parameter and a file.

The parameter passed to 'handle_topic_updates' is 'muted_topics'
and there is also a javascript file with same name.
So 'muted_topics.get_muted_topics' gives error, and this commit
fixes this by changing the parametr name to 'muted_topics_list'.
This was introduced in  5f74e78beeac0a.
Reported by Aman in https://chat.zulip.org/#narrow/stream/6-frontend/topic/mute.20migration.

Testing plan:  Tested manually in dev server.

Merged, thanks @sahil839 !


RFC 0075 Payment decorator doesn't account for fiat

If the goal of this of RFC is to handle various forms of payment then we are missing a lot of information. This works for peer to peer payments like cash but in the real world that is not how payments work.
There are actually 4 parties when it comes to payments: Payer, payer's issuing bank, payee's acquiring bank, and payee. With credit/debit cards, the payer authorizes the payee to charge his card. The payee passes the consent to charge to his acquiring bank which then passes it to the credit/debit card networks.  The issuing bank checks the consent and releases the funds over the network back to the acquiring bank. The acquiring bank holds the funds until the payee fulfills his part of the deal. This can be selling something to the payer and must deliver the product to collect payment. Reimbursement is different because payee has already delivered something.
I think this is low priority right now for the spec but wanted to make sure that this portion is noted.

Since this was modeled on an existing WebPayments standard, I suspect we may be missing that extra data because it doesn't belong in the protocol. The decorator isn't proposing to consummate payment--only to report that it is required (part 1) and has been completed (part 2). It should already work for fiat, since that's what the WebPayments standard supports.

I think the response from @dhh1128's is correct, and the question doesn't apply to the RFC 0075, the decorator. When we actually get to the point that we have a payment protocol, the issues raised will come out.
Closing. Please reopen if appropriate.


Return the itemType information in getERC1155Listings

We should return the itemType information about each ERC1155 so the client doesn't need to look it up.

We have decided not to implement this change, closing.


Migration script fails when haskell/projects or blocklyXML/projects do not exist

The migration script halts with an error if the directories haskell/projects or blocklyXML/projects do not exist. It should either assume nothing needs to be migrated there or create those directories if they are needed.

This is also the case for the directory data/codeworld/projects, if it does not yet exist.

Okay, this shouldn't be hard to fix, at least.

FYI @nixorn


Format code with gofumpt

Type of change

[ ] 🐛 Bug fix (non-breaking change which fixes an issue)
[ ] 🌟 New feature (non-breaking change which adds functionality)
[ ] 🔨 Breaking change (fix or feature that would cause existing functionality)
[x] 📖 Docs change / refactoring / dependency upgrade to change)

Description
I'm planning to contribute some changes and noticed that the code isn't formatted consistently.
Used gofumpt -w -extra ./clerk/ ./examples/ ./tests/ to do just that.

@mlafeldt Thanks! 🎉


Remove pub from 'inner' field in write barrier

I think that because the inner field is pub, external code could potentially modify it which would be unsafe. By making inner private it also removes the need for struct Write to be non_exhaustive.
However, this does introduce some weirdness in needing an 'explicit' deref function to be used in the field!macro as well as a new way of asserting that the $value is of type Write.

Not really sure what caused the failing tests output to change... I'm sure it has to do with changing the field! macro, but I think the output is still acceptable.

I think that because the inner field is pub, external code could potentially modify it which would be unsafe.
Third-party code accessing __inner (or constructingg a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

Additionally, your version of the field! macro evaluates its argument twice, which definitely shouldn't happen.

I think that because the inner field is pub, external code could potentially modify it which would be unsafe.
Third-party code accessing __inner (or constructingg a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

Additionally, your version of the field! macro evaluates its argument twice, which definitely shouldn't happen.

Oh I didn't realize that! I think a fix is to save it to a variable? like this?
{
            let value = $value;
            let _: &$crate::barrier::Write<_> = value;

            match value.get_inner() {
                $type { ref $field, .. } => unsafe {
                    $crate::barrier::Write::__from_ref_and_ptr($field, $field as *const _)
                },
            }
        }

Oh, my first objection (and most important one!) was eaten by the quote formatting, let me copy it again:
Third-party code accessing  __inner (or constructing a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

Third-party code accessing __inner (or constructing a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

Full agreement, accessing a double underscore variable which is #[doc(hidden)] is not part of the API at all, so it's not possible by definition for it to be an unsafe interface (since it is not even an interface).
The goal of a safe interface is not to protect against industrial espionage, and the compiler is not supposed to be a security boundary.

Third-party code accessing __inner (or constructing a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

I actually didn't fully appreciate moulins' point either, which is that EVEN IF you consider the __inner field to be a public interface, it's STILL (arguably) not unsound.
If you simply construct a Write value, then this gives you no extra powers that you didn't already have. If you access the __inner field of an existing Write then same deal, you could already do that via Deref / DerefMut.
The only way to get a dangerous &Write<T> is through mem::transmute-ing a &T with unsafe interior mutability that exists inside a Gc.
I suppose if the definition of Write was...
/// A transparent wrapper of anything at all with no guarantees whatsoever.
///
/// You can freely call `mem::transmute` to convert a `&T` to a `&Write<T>` if you want.
#[repr(transparent)]
pub struct Write<T: ?Sized> {
    pub inner: T,
}

Then that would be unsound..... documentation? But that's not what the documentation says, and the inner field is specifically documented to not be part of the public API at all.
So yeah, this makes for a stronger case against needing to change anything.

Even if this isn't merged, I appreciate the PR and I definitely appreciate any and all effort looking at gc-arena's API and trying to find unsoundness, so thank you.
I don't think this is an example of unsoundness, but still... many eyes are a good thing!
I'll leave this open in case anyone can figure out a way that accessing __inner without additional unsafe code can lead to potential UB, but even then I still think that a #[doc(hidden)] public field should not really count.

Oh, my first objection (and most important one!) was eaten by the quote formatting, let me copy it again:
Third-party code accessing __inner (or constructing a Write<_> by value) isn't actually unsafe, only undesirable and mostly useless. As such, I don't think this change is necessary.

My mistake, I do believe you're right! For some reason I was thinking the write barrier worked a different way


Bump image versions in values.yml

Problem:
bump images in values.yml for v1.4 branch
Solution:
bump images in values.yml for v1.4 branch
Related Issue:
#6568
Test plan:

Waiting for the upcoming release of the network-controller-harvester.


🚨 Potential Security Vulnerability - huntr.dev

⚠ Potential Vulnerability in polyfig
👋 Hello, @JamieSlome - @jamieslome has disclosed a potential vulnerability in your repository. To validate or invalidate this potential vulnerability, please visit https://huntr.dev/bounties/1-other-JamieSlome/polyfig and join our community in helping secure open-source code.

☎ Need further support?
Come and join us on our Discord and a member of our team will be happy to help! 🤗
cc - @JamieSlome

yo

📦 A patch has been submitted for this report. 🔗 Check the patch (https://github.com/jamieslome/polyfig/compare/HEAD...huntr-tester:master) or visit the advisory page (https://huntr.dev/bounties/1-other-jamieslome/polyfig) for more information.

📦 A patch has been submitted for this report. 🔗 Check the patch (https://github.com/jamieslome/polyfig/compare/HEAD...huntr-tester:master) or visit the advisory page (https://huntr.dev/bounties/1-other-jamieslome/polyfig) for more information.

📦 A patch has been submitted for this report. 🔗 Check the patch (https://github.com/jamieslome/polyfig/compare/HEAD...huntr-tester:master) or visit the advisory page (https://huntr.dev/bounties/1-other-jamieslome/polyfig) for more information.

📦 A patch has been submitted for this report. 🔗 Check the patch (https://github.com/jamieslome/polyfig/compare/HEAD...psmoros:main) or visit the advisory page (https://huntr.dev/bounties/1-other-jamieslome/polyfig) for more information.

hello there bro would you like to have some chooocolate bro<EMAIL_ADDRESS>

chocllate.

blar.


Is the Breakout Room limit 299 or 300?

This page says "Breakout rooms can only be created in meetings that have fewer than 300 attendees." (emphasis added). But in the next sentence it says, "creating breakout rooms... limits the number of meeting attendees to 300."
So is the limit 299 (i.e., "fewer than 300"), or is the limit 300? Should it read "Breakout rooms can only be created in meetings that have 300 attendees or fewer."?
Thanks!

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

ID: 905e2c09-ef3e-07cc-0809-6ff171157c47
Version Independent ID: c0d33162-183d-fff8-32e9-a999f391ea51
Content: Limits and specifications for Microsoft Teams - Microsoft Teams
Content Source: Teams/limits-specifications-teams.md
Service: msteams
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

Hello @GitRomney
This is what I could find out
You start a meeting and you have <300 attendees. Until you hit that 300 number, – the meeting can scale beyond 300 people as more people can join, and you can also create breakout rooms
Once that 301st participant joins,  then you can no longer have breakout rooms for that meeting.
Now let’s say that the meeting organizer initiated breakout rooms before the 301st joins. That will cap the meeting at 300 attendees, and then the 301st won’t be able to join the meeting because he’s the 301st.
Hope this answers your question,
@scanum I think this can be closed now.

Thanks. So in that case, the article should read "Breakout rooms can only be created in meetings that have 300 attendees or fewer
instead of "Breakout rooms can only be created in meetings that have fewer than 300 attendees." The current language is incorrect, since you can create breakout rooms in a meeting with 300 attendees.

@GitRomney thanks for your feedback, will pass it on.


RuntimeWarning

trend.py:170: RuntimeWarning: invalid value encountered in double_scalars
  dip[i] = 100 * (dip_mio[i]/trs[i])

trend.py:174: RuntimeWarning: invalid value encountered in double_scalars
  din[i] = 100 * (din_mio[i]/trs[i])

site-packages\ta\trend.py:468: RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i]/self._trs[i])
site-packages\ta\trend.py:472: RuntimeWarning: invalid value encountered in double_scalars
din[i] = 100 * (self._din[i]/self._trs[i])

site-packages\ta\trend.py:468: RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i]/self._trs[i])
site-packages\ta\trend.py:472: RuntimeWarning: invalid value encountered in double_scalars
din[i] = 100 * (self._din[i]/self._trs[i])

same issues

same issue

same issue

Same issue
\.venv\lib\site-packages\ta\trend.py:543: RuntimeWarning: invalid value encountered in double_scalars
  dip[i] = 100 * (self._dip[i]/self._trs[i])
\.venv\lib\site-packages\ta\trend.py:547: RuntimeWarning: invalid value encountered in double_scalars
  din[i] = 100 * (self._din[i]/self._trs[i])

Hi all,
This is a warning error.
I will fix it asap.
Best,
Dario

Hi, first off thanks for doing this! Second, im just curious if there is and ETA for this fix?
Thanks again,
Dan

RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i]/self._trs[i])

Still present

Any update on this? I am still encountering the same issue.

RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i] / self._trs[i])
this problem is still present

I get error RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i] / self._trs[i])
Looks like divide by zero error. I see it has been previously reported. Several times. I appreciate your library but this makes it unusable for me. If I fix it, I run into another divide by zero error. If I fix that, I run into a different error. Cascading issues.

Yeah, this fails with pretty much all data. Even basic yahoo finance data can't run because of the divide by zero errors. Great library otherwise, though.

Hey what's the timeline for this? It's not something major but it's nice to have the log clean😛

Hey what's the timeline for this? It's not something major but it's nice to have the log clean😛

Getting the same error...

This is so annoying I had answer this issue with a beatiful explanation and Github decided to erase what i was writing and send me to another page gr.. So in short now, line 715 in Trend.py:
pdm = _get_min_max(self._high, close_shift, "max")
pdn = _get_min_max(self._high, close_shift, "max")
diff_directional_movement = pdm - pdn
And then goes to line 726:
for i in range(1, len(self._trs) - 1):
self._trs[i] = (
self._trs[i - 1]
- (self._trs[i - 1] / float(self._window))
+ diff_directional_movement[self._window + i]
)
If the Dataset has missing values (NaN) then since self._trs[i] is being filled with self._trs[i-1] as part of the formula the first Nan it encounters will continue to fill all values with NaN. So you end up with a self._trs that has a lot of missing values so when you divide something with self._trs you get that warning, but of course is not only a warning you are actually messing up with the results of the indicators involved. I solved my particular issue by adding a fillna method just after line 717 like this:
pdm = _get_min_max(self._high, close_shift, "max")
pdn = _get_min_max(self._high, close_shift, "max")
diff_directional_movement = pdm - pdn
---> diff_directional_movement.fillna(method='ffill',inplace=True) <--- New line
However you can also add some vectorized numpy solution to the _get_min_max function in utils.py so it makes sure to clean all Nan values of the series that are feed to it, or maybe just fillna the whole dataset somehow.

@Neogus :+1: You should make a PR

@Neogus thx that fixed it for me!

or we could simply add this line at the beginning of the code
np.seterr(divide='ignore', invalid='ignore')
We know there will be nan or 0 values at the beginning of data range while calculating an indicator, and that will throw this warning. So by adding this one line, solves that issue.

or we could simply add this line at the beginning of the code
np.seterr(divide='ignore', invalid='ignore')
We know there will be nan or 0 values at the beginning of data range while calculating an indicator, and that will throw this warning. So by adding this one line, solves that issue.

kinda new to this, can you explain how this solves the issue?

@formula-x
The runtime warning happens when the program is trying to divide a value by zero or nan value. We know in order to calculate our Indicators, some of the initial values will be either zero or nan, which inevitably are going to throw the runtime warning.
So, what this line does is to ignore such warnings, pertaining only to divide function. Rest of warnings will still work.
I've tried to fix another part of the library , and similar issue cropped up, but that time I took the long method of solving it. This time I felt ignoring divide warning is a more efficient way of handling it.

@formula-x
The runtime warning happens when the program is trying to divide a value by zero or nan value. We know in order to calculate our Indicators, some of the initial values will be either zero or nan, which inevitably are going to throw the runtime warning.
So, what this line does is to ignore such warnings, pertaining only to divide function. Rest of warnings will still work.
I've tried to fix another part of the library , and similar issue cropped up, but that time I took the long method of solving it. This time I felt ignoring divide warning is a more efficient way of handling it.

Ok I get it, thanks for the explanation bro I appreciate it.. do you have a discord or anything I can reach you on incase I have more questions pertaining to this library? Judging by your reply, there are other areas of this library where I might run into similar issues..

sure, leave a comment here, will reply to you :-) This library is very well done, this is the only minor irritant.

Still have this error on different line:
/usr/local/lib/python3.7/dist-packages/ta/trend.py:768: RuntimeWarning: invalid value encountered in double_scalars
dip[i] = 100 * (self._dip[i] / self._trs[i])
/usr/local/lib/python3.7/dist-packages/ta/trend.py:772: RuntimeWarning: invalid value encountered in double_scalars
din[i] = 100 * (self._din[i] / self._trs[i])

For me, it started popping up recently. Same issue.

You’d be better slicing out the bits where you expect the error, otherwise you might not catch genuine errors.

On 16 Aug 2021, at 19:52, summa-code @.***> wrote:

For me, it started popping up recently. Same issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Getting some similar errors:
/trend.py:769: RuntimeWarning: invalid value encountered in double_scalars
/trend.py:774: RuntimeWarning: invalid value encountered in double_scalars
/trend.py:938: FutureWarning: The default dtype for empty Series will be 'object' instead of 'float64' in a future version. Specify a dtype explicitly to silence this warning.
  self._psar_up = pd.Series(index=self._psar.index)
trend.py:939: FutureWarning: The default dtype for empty Series will be 'object' instead of 'float64' in a future version. Specify a dtype explicitly to silence this warning.
  self._psar_down = pd.Series(index=self._psar.index)

Maybe do the calcs with numpy and wrap with np.errstate()?

This Commit fix this Problem:
https://github.com/bukosabino/ta/pull/196/commits/d0cccf8e31e4cfc889b0d2cbac36e2b0dcd1dbac
But there are other line numbers

C:\Users\addev\anaconda3\lib\site-packages\ta\trend.py:769: RuntimeWarning: invalid value encountered in double_scalars
dip[idx] = 100 * (self._dip[idx] / value)
C:\Users\addev\anaconda3\lib\site-packages\ta\trend.py:774: RuntimeWarning: invalid value encountered in double_scalars
din[idx] = 100 * (self._din[idx] / value)

C:\Users\eldem\AppData\Local\Programs\Python\Python310\lib\site-packages\ta\trend.py:780: RuntimeWarning: invalid value encountered in double_scalars
dip[idx] = 100 * (self._dip[idx] / value)
C:\Users\eldem\AppData\Local\Programs\Python\Python310\lib\site-packages\ta\trend.py:785: RuntimeWarning: invalid value encountered in double_scalars
din[idx] = 100 * (self._din[idx] / value)


Allow for setting a editor background image

Currently we need hacks and workarounds just to make a simple feature work : Setting Background Images.
This is what i could do 7 years ago in ATOM editor : Could add background with translucency and CSS text effect.
https://github.com/v3ss0n/steam-pirate-ui

I understand that enabling full CSS features could be performance problem , so what i am requesting is only following features.

A Proper API to set Background
Optional Translucency/Tinting support
Optional Blurring support

It was requested here : https://github.com/microsoft/vscode/issues/84120
but shot down  : https://github.com/microsoft/vscode/issues/84120#issuecomment-551072767

How does that increase productivity? I find it unlikely that we would allow this, but maybe there is a good argument to do it.

This is not just for "Looking Good' as  It have a lot of productivity use cases and could make a lot of useful extensions that:

Cheatsheets as Background Images , changes depending on programming languge/framework
Charts / Graphs / {Stock,Crypto} Prices / Process Monitors  Dynamically updated at the back ground.
Motivational / Quotes chaning every set hours.

This is some of very few usecases that is not just for looks but

/duplicate https://github.com/microsoft/vscode/issues/112192

+1 this request - adjustable transparency and blur


Fix move and slide regression by allowing multiple collision direction

4.0 version of #51556

Thanks!


feat: implement did-core JSON-LD @context representation

Signed-off-by: Chris Abernethy<EMAIL_ADDRESS>Title:
Implement did-core JSON-LD @context representation
Description:
Current implementation assumes @context can only be []string, but did-core v1 defines @context for DID documents in JSON-LD representation to be either a string or a list containing maps and/or strings.
Summary:

Created type Context {}interface to represent did document contexts with appropriate comment for IDE integration.
Modified did.parseContext to add parsing of string and []interface{} context representations.
Added LookupContextString helper to search for context string through entire context (used by requiresLegacyHandling)
Added LookupSchemaFromContext helper to peek first string in context. Replaces direct references to context[0]
Modified existing tests to account for new context format
Added tests for new helper functions

great addition now that did-core is officially a TR


Retired the UDR parameter since it's twice as slower as plain rsync w…

…hen copying databases between servers with different hardware, you also need to recompile UDR for every new server. I replaced UDR with TCP arcfour (default parameter) which works in all the situations, worst case scenario it will be as fast as plain rsync, in all the other scenarios it will be twice as fast as plain rsync, copy can go up to 110 MB/s or faster

Coverage increased (+0.28%) to 74.7% when pulling 10f7b51a11454547cd053fa821eefa0364c02d0e on thomasmaurel:copydboverservertcp into 21507df6fbc7fc9201f13f2a7915e08b61bcf5cc on Ensembl:master.

Fair enough.

fine with me, thanks for the change


Should warn when a bug is fixed in nightly, tracked in aurora & beta but no uplift request

For example, in https://bugzilla.mozilla.org/show_bug.cgi?id=1194706 , Liz had to ping the developer. The developer should receive a notification.

Maybe even when the bug is not tracked, but is marked as affected.

:+1:

We had the similar issue with this bug https://bugzil.la/1241558
I agree with Liz, even if it is not tracked, the release management team should receive an email.
Either uplift or wontfix in the branch.

In this commit:
https://github.com/calixteman/relman-auto-nag/commit/b81b18382a55fa018a9cdef4ce5564662215bbf1?diff=unified
I added a script to add this feature.

Fixed


Small bug in the instruction / explanation of the challenge

Challenge Style Multiple Elements with a CSS Class has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
It's not about the code, it's about the instruction of the challenge.
There is a sentence: "But also remember that class declarations don't use a period, like this:"
Especially this is a little bit confused: "class declaration".
The thing is that this is not a declaration of a class.
In my opinion this sentence would be better:
"But remember that pointing a class that is used to affect an html element don't use a period, like this: "
Based on this definition of class selector:
http://www.w3schools.com/cssref/sel_class.asp
http://www.w3schools.com/tags/att_global_class.asp

I think youre right, its not as accurate as it could be given that what its referring to is class attributes.
Maybe change it to something like: "But also remember that HTML class attributes don't use a period" ?

Mmm I agree that this could be misinterpreted differently. Maybe we could change it to this.

But remember that using classes in HTML elements don't need periods.

Nonetheless, something to that effect should be used to replace the text.


EISDIR: illegal operation on a directory, read error after library upgrade

Hello!
We recently upgraded @auth0/auth0-spa-js to a more recent version and our production build started failing with this error:
cleaning up...
Build Error (UglifyWriter)
EISDIR: illegal operation on a directory, read

Notably v1.6.2 does not have this error, but anything from 1.7.0 does.
Reproducing it locally I found this log from the error dump:
ERROR Summary:

  - broccoliBuilderErrorStack: Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:523:3)
    at tryReadSync (fs.js:348:20)
    at Object.readFileSync (fs.js:385:19)
    at getSourceMapContent (/Users/meirish/code/cloud-ui/node_modules/broccoli-uglify-sourcemap/lib/get-sourcemap-content.js:18:30)
    at processFile (/Users/meirish/code/cloud-ui/node_modules/broccoli-uglify-sourcemap/lib/process-file.js:41:19)
    at Function.processFileParallel (/Users/meirish/code/cloud-ui/node_modules/broccoli-uglify-sourcemap/lib/worker.js:9:10)
    at MessagePort.<anonymous> (/Users/meirish/code/cloud-ui/node_modules/broccoli-uglify-sourcemap/node_modules/workerpool/dist/workerpool.min.js:25:16559)
    at MessagePort.emit (events.js:311:20)
    at MessagePort.onmessage (internal/worker/io.js:78:8)

What ends up happening here is srcURL.from() here: https://github.com/ember-cli/broccoli-uglify-sourcemap/blob/master/lib/get-sourcemap-content.js#L10 returns an empty string '' as the first item in the urls array when it gets to our app's vendor.js file, which then errors here: https://github.com/ember-cli/broccoli-uglify-sourcemap/blob/master/lib/get-sourcemap-content.js#L18 when it tries to read a directory instead of a file.
Removing the empty string from the array results in a successful build, but with this warning:
[UglifyWriter][WARN] (broccoli-uglify-sourcemap) "chunk.40bafbb6f4ed25560db2.js.map;", "chunk.cc45f8eb6b4af1864c92.js.map//#" referenced in "assets/vendor.js" could not be found

Which seems to point to ember-auto-import.
I'm uncertain where the issue is - is it in the auth0 source map urls, the source-map-url package that returns '', or maybe ember-auto-import. Has anyone ever seen this or have any guidance for where to look further?

I'm hitting a similar issue.

Interestingly, this is happening when I upgrade from @auth0/auth0-spa-js 1.16.0 to 1.16.1.

@meirish @wagenet Ran into something similar. This seems to be fixed in this PR https://github.com/ember-cli/broccoli-terser-sourcemap/pull/313

Should be released, too: https://github.com/ember-cli/broccoli-terser-sourcemap/releases/tag/v4.1.1
does upgrading to 4.1.1 solve this for ye?

I was able to fix it by installing<EMAIL_ADDRESS>in my project. I noticed that ember-cli-terser wasn't auto installing the latest version for whatever reason? Even though their package.json allows for it https://github.com/ember-cli/ember-cli-terser/blob/f3b5fd4875697c223fb1a9414c568c3aadbc017c/package.json#L25

likely has to do with your lockfile -- generally when you need to update transient / sub-sub deps, I like to delete the entries in the lockfile, and let the package manager re-resolve what the correct version is.
anywho! most excellent!
I'm going to close this issue, and we can probably open a new one if a similar issue arises!


Discover how to zoom in & out on data visualizations (multiple means)

Multiple ways to zoom are needed. Examples:

A visible affordance in UI
Discoverable keyboard shortcuts
Keyboard+drag operations (z+drag to zoom to the extent of the drag)
Select element or elements, then auto-zoom to extent of element?

Issue source: @ssmagula's user tests + brainstorming with TC and tool team members, other users emphasized discoverable navigation as a priority

I like the idea of having a chart that has an overview being used to zoom and also provide context for what you're looking at. The video shows:

Select an area of the overview chart to zoom (smaller to zoom in, larger to zoom out).
While hovering on chart, Ctrl+Scroll to zoom (selected area in overview chart adjusts automatically).
Return to default zoom by selecting the whole overview chart.

https://user-images.githubusercontent.com/28311615/114595224-2369e980-9c5c-11eb-9920-b158bd2760c0.mp4

kernelshark also zooms to selected area on a graph:


Extend to 3 hours

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
Java docindex validate and update package info once the version changes. We usually ran into traffic peak during the monthly release. Extend the pipeline to 3 hours to take care of the timeout.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1958961&view=results
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

I'm ok increasing the timeout as long as feel like there isn't any work we can cut out.

The validation step takes time but lucky this only happens every month.


Allow default values for NLOHMANN_DEFINE_TYPE_INTRUSIVE and NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE

These two macros use json::at for deserializing from json to obj, but it will throw exceptions and is not good for backward-compatibility if the struct adds new fields but the json is still unchanged.
This simple patch uses the default value from struct type (the type should be default constructible), and use json::value to set default value if some fileds is missing in json value. Hope it helps.

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

It failed unit test "unit-udt_macro.cpp" as line 256 expects an exception is thrown. No idea if this behavior should be changed.

This would be a breaking change, hence the tests fail. Best would be to introduce a new macro, though I'm not sure what a good name could be.

This change also requires that the destination type be default constructible, which I believe is explicitly not a requirement currently.

Changes to old macros are reverted and new macros are added witih passed unit tests, which are

NLOHMANN_DEFINE_TYPE_INTRUSIVE_WITH_DEFAULT
NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_WITH_DEFAULT

Coverage remained the same at 99.982% when pulling 7aeda9d433a88db56276b78696993636cb888fd8 on harry75369:develop into 18a5f4c7ca30d9e0a2e4f12240c13f3e8ff4c82e on nlohmann:develop.

Can you please also edit
* https://github.com/nlohmann/json/blob/develop/doc/mkdocs/docs/features/macros.md

* https://github.com/nlohmann/json/blob/develop/doc/mkdocs/docs/features/arbitrary_types.md#simplify-your-life-with-macros

Done.

Why is this PR still not merged yet after so many days? All including docs are already editted as sugguested.

Because this is a side project of mine and i did not find the time to check your last changes.

I messed up the CI lately, I'm sorry. Can you please update to the latest develop branch?

I messed up the CI lately, I'm sorry. Can you please update to the latest develop branch?

Do you mean I make an empty commit to trigger the CI?

Just update your branch and commit the changes.

I was surprised to find this just as I made my own macro for pretty much the same thing. I'd love for this to get merged in.
Here was my attempt on it
#define NLOHMANN_JSON_FROM_OPTIONAL(v1) if (const auto it = nlohmann_json_j.find(#v1); it != nlohmann_json_j.end()) {it->get_to(nlohmann_json_t.v1);}

#define NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_OPTIONAL(Type, ...)  \
    inline void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) { NLOHMANN_JSON_EXPAND(NLOHMANN_JSON_PASTE(NLOHMANN_JSON_TO, __VA_ARGS__)) } \
    inline void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) { NLOHMANN_JSON_EXPAND(NLOHMANN_JSON_PASTE(NLOHMANN_JSON_FROM_OPTIONAL, __VA_ARGS__)) }

I'm confused - did you update to the latest develop branch?

I'm confused - did you update to the latest develop branch?

Yes, I pulled latest develop branch, and rebased.

I'm confused - did you update to the latest develop branch?

Yes, I pulled latest develop branch, and rebased.

I am confused, because the diff now shows me changes in 51 files. 🤔

I still have no idea that if this works or not. But from the README.md that macro does'nt work at all. Or is it in progress ?

No, this PR is not yet merged.

I'm confused - did you update to the latest develop branch?

Yes, I pulled latest develop branch, and rebased.

I am confused, because the diff now shows me changes in 51 files. 🤔

Hey @harry75369, can you please fix the branch by updating it to the latest develop branch?

Any update on this? I really like the macros for backward compatibility. Please let me know if there's anything I can help with to get it merged.

Still not merged? Those macros are really usefull!

Still not merged? Those macros are really usefull!

The PR needs to be rebased. Can you do this, @harry75369 ?

Still not merged? Those macros are really usefull!

The PR needs to be rebased. Can you do this, @harry75369 ?

Hi Nils!
I cherry-picked @harry75369 's commits in PR https://github.com/nlohmann/json/pull/3143. I don't know the protocol for stalled PRs, I hope that this is ok. I would really like to have this feature as well.

Can be closed as https://github.com/nlohmann/json/pull/3143 is merged. Thanks a lot everybody!


Upload binary releases

Can you upload some binary releases and preferably targeting .NET 2.X ?

There are no plans for supporting 2.x.
@irsdl got it working at least for 1 gadget but Im not sure how can we get it working for all versions

Created CI integration and released binaries

There are no plans for supporting 2.x.
@irsdl got it working at least for 1 gadget but Im not sure how can we get it working for all versions

I am going to release what I have soon in another PoC Repo as my solution is hacky and still probably requires .NET3.5 DLLs on the box (I need to investigate this further). Watch this space :)


V

Ditch V, make it in x86 assembly.

Ditch V, make it in x86 assembly.

That's funny because I'm coding in x86 Assembly using the NASM assembler rn :rofl:

yessss, if you need help, im pretty decent 👀

yessss, if you need help, im pretty decent 👀

But if so, by what way should I message you ?

my email is<EMAIL_ADDRESS>my discord is .md.11.


Add link to doc sites to head of project

Next to the project description

duplicate, please close. https://github.com/rackt/react-router/issues/1232

This actually isn't a duplicate. My suggestion was to add a link to top of the page as that's more convenient than going hunting down in the README.

Oh nvm, it wasn't a duplicate, it just wasn't fixed by https://github.com/rackt/react-router/commit/aef87479b16d1f12fdf02cfbd297e2d8e1032392

That is what @ericclemmons is suggesting in #1232


Button timing

The click type timing is very sensitive. It is especially hard to issue a proper double click. There is a huge potential for improvement in this area.

Improved in 1.4


Does Erasure Coding negatively impact availability on clusters with few servers?

Seaweed uses RS(10,4) for erasure coding. Let's say I have a file stored with 010 replication (1 copy on different rack) in a cluster that only has 2 volume servers, each in a different rack. If 1 volume server goes down, file is still available. As soon as the volume is sealed and Erasure coding starts, shards will be split between 2 volume servers. If 1 volume server goes down, more than 4 shards are missing and the file is not available anymore.
Am I getting this right?

Correct. If not enough volume servers, EC is not good.

Can EC be disabled altogether for small clusters? Can it be turned on later as cluster grows larger?

If the admin script "ec.encode" is not run, no EC will happen.


Add project Evaluating Voting Design Tradeoffs for Retro Funding

This PR adds the project "Evaluating Voting Design Tradeoffs for Retro Funding" to the OSS Directory. The project is hosted at https://github.com/GovXS/Evaluating-Voting-Design-Tradeoffs-for-Retro-Funding and evaluates tradeoffs in voting mechanisms for retroactive funding.
Artifacts added:
https://github.com/GovXS/Evaluating-Voting-Design-Tradeoffs-for-Retro-Funding

/validate 647a0a88ee9984de4c4e7a6587b2e134f36026c5


CSS Modify Search Results Description Height (Option)

Optional Display
We created a CSS style to make each description a consistent size and make it easier to scan the list of results. This cuts off the text if it goes on too long.  This allows three lines of text to display.  A person could figure out how to "collapse" the description, but this is a quick fix.
/* Style for descriptions creates a cap of a few lines of text  */
.g-item-card .g-item-description {
	max-height: 46px;
	overflow: hidden;
        width: 85%;
}

@KathleenPate  Thanks, we added this to our main.css;