Getting nans as output for predict

Description
The predict function is returning nans despite the values the model fits on having no missing data. The output changes if I include a few more values in the fitted data.
Steps/Code to Reproduce
Example:
from numpy.linalg import LinAlgError
from pmdarima.arima import auto_arima

trainValues = [144.5, 142. , 139. , 137. , 135. , 135. , 134. , 134. , 133. ,
       132. , 133. , 134. , 137. , 135. , 134. , 134. , 137. , 136. ,
       136. , 125. , 120. , 120. , 121. , 120. , 116. , 119. , 125. ,
       134. , 124. , 113. , 110. , 109. , 110. , 111. , 106. , 106. ,
       102. , 101. , 102. , 105. , 105. , 108. , 110. , 109. , 113. ,
       119. , 120. , 118. ]

fitValues = [115., 126., 142., 146., 165., 175., 184., 192., 200., 208., 215.,
       222., 227., 231., 233., 235., 234., 231., 229., 232., 234., 232.,
       223., 212., 207., 200., 191., 191., 194., 195.]

model = auto_arima(trainValues, seasonal=False)

#this is where the issue occurs.
fittedModel = model.fit(fitValues[0:27]) #this fits successfully
print(fittedModel.predict(n_periods=2)) #returns nans

#I would have expected either some sort of error to be thrown or for predicted values
#to be returned. I can get these expected types of output to occur jus by subsetting a
#larger amount of the data I'm fitting on. (See below for examples that produce more
#expected outcomes)

try:
    print(model.fit(fitValues[0:28]).predict(n_periods=2))
except LinAlgError:
    print("LinAlgError")

print(model.fit(fitValues[0:29]).predict(n_periods=2))

Expected Results
I would expect either an error to be thrown if there's an issue with SVD, stationarity, etc. or if the model was fit successfully (which I believe it was), I would expect valid numeric predictions.
Actual Results
[nan nan]
Versions
Linux-4.4.0-139-generic-x86_64-with-debian-stretch-sid
Python 3.5.6 |Anaconda, Inc.| (default, Aug 26 2018, 21:41:56)
[GCC 7.3.0]
pmdarima 1.1.0
NumPy 1.15.2
SciPy 1.1.0
Scikit-Learn 0.20.0
Statsmodels 0.9.0

Hey, thanks for the well-formatted issue! On my end, I get a lot of errors thrown from running your example. Are you by any chance using error_action="ignore"
>>> from numpy.linalg import LinAlgError
>>> from pmdarima.arima import auto_arima

>>> trainValues = [144.5, 142. , 139. , 137. , 135. , 135. , 134. , 134. , 133. ,
...        132. , 133. , 134. , 137. , 135. , 134. , 134. , 137. , 136. ,
...        136. , 125. , 120. , 120. , 121. , 120. , 116. , 119. , 125. ,
...        134. , 124. , 113. , 110. , 109. , 110. , 111. , 106. , 106. ,
...        102. , 101. , 102. , 105. , 105. , 108. , 110. , 109. , 113. ,
...        119. , 120. , 118. ]

>>> fitValues = [115., 126., 142., 146., 165., 175., 184., 192., 200., 208., 215.,
...        222., 227., 231., 233., 235., 234., 231., 229., 232., 234., 232.,
...        223., 212., 207., 200., 191., 191., 194., 195.]

>>> model = auto_arima(trainValues, seasonal=False)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/pmdarima/arima/auto.py:870: ModelFitWarning: Unable to fit ARIMA for order=(1, 1, 2); data is likely non-stationary. (if you do not want to see these warnings, run with error_action="ignore")
  ModelFitWarning)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/base/model.py:488: HessianInversionWarning: Inverting hessian failed, no bse or cov_params available
  'available', HessianInversionWarning)

>>> fittedModel = model.fit(fitValues[0:27]) #this fits successfully
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:674: RuntimeWarning: invalid value encountered in double_scalars
  tmp[kiter] = (macoefs[kiter]-b *macoefs[j-kiter-1])/(1-b**2)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:676: RuntimeWarning: divide by zero encountered in true_divide
  invmacoefs = -np.log((1-macoefs)/(1+macoefs))
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:650: RuntimeWarning: invalid value encountered in true_divide
  newparams = ((1-np.exp(-params))/(1+np.exp(-params))).copy()
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:651: RuntimeWarning: invalid value encountered in true_divide
  tmp = ((1-np.exp(-params))/(1+np.exp(-params))).copy()
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tools/numdiff.py:243: RuntimeWarning: invalid value encountered in add
  **kwargs)).imag/2./hess[i, j]
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tools/numdiff.py:243: RuntimeWarning: invalid value encountered in multiply
  **kwargs)).imag/2./hess[i, j]
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/base/model.py:488: HessianInversionWarning: Inverting hessian failed, no bse or cov_params available
  'available', HessianInversionWarning)

>>> print(fittedModel.predict(n_periods=2))
[nan nan]

I didn’t have error_action set to ignore, but I realized early in my notebook I had a broader warning suppression turned on because a different package kept giving me future warnings. My understanding was that auto-arima tries a bunch of different permutations of parameters, and returns the models in the order of the lowest AIC. For the first warning where it says ModelFitWarning due to stationarity and there’s an issue with the hessian, it just won’t return that as a valid fitted model, right? (There’s nothing intrinsically bad about it trying parameter combinations that don’t fit, right?).  I had trace turned on for a while and saw that some of the parameter permutations didn’t work. Is that warning a problem? I thought it was natural that some permutations wouldn’t work.
As for the second bunch of warnings (the runtime warnings), what’s the difference between when it throws a warning versus and error? Right now I have code that is cycling through the models from best to worse until it finds one that doesn’t throw an error. In this case, since it just threw a warning message, it was accepted (where as the example below that has the SVD LinAlg Error would have been caught).
Sorry to have bothered you, given that it turned out to be an issue with my code and not your package. This was actually the first time I’ve ever filed a git issue (I’m a recent college grad that didn’t major in CS), so I really appreciate your kindness! I didn’t mean to turn this into a stack overflow type problem instead of finding a true bug!

On Feb 16, 2019, at 9:46 AM, Aaron Smith<EMAIL_ADDRESS>wrote:
Hey, thanks for the well-formatted issue! On my end, I get a lot of errors thrown from running your example. Are you by any chance using error_action="ignore"

from numpy.linalg import LinAlgError
from pmdarima.arima import auto_arima

trainValues = [144.5, 142. , 139. , 137. , 135. , 135. , 134. , 134. , 133. ,
...        132. , 133. , 134. , 137. , 135. , 134. , 134. , 137. , 136. ,
...        136. , 125. , 120. , 120. , 121. , 120. , 116. , 119. , 125. ,
...        134. , 124. , 113. , 110. , 109. , 110. , 111. , 106. , 106. ,
...        102. , 101. , 102. , 105. , 105. , 108. , 110. , 109. , 113. ,
...        119. , 120. , 118. ]

fitValues = [115., 126., 142., 146., 165., 175., 184., 192., 200., 208., 215.,
...        222., 227., 231., 233., 235., 234., 231., 229., 232., 234., 232.,
...        223., 212., 207., 200., 191., 191., 194., 195.]

model = auto_arima(trainValues, seasonal=False)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/pmdarima/arima/auto.py:870: ModelFitWarning: Unable to fit ARIMA for order=(1, 1, 2); data is likely non-stationary. (if you do not want to see these warnings, run with error_action="ignore")
ModelFitWarning)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/base/model.py:488: HessianInversionWarning: Inverting hessian failed, no bse or cov_params available
'available', HessianInversionWarning)

fittedModel = model.fit(fitValues[0:27]) #this fits successfully
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:674: RuntimeWarning: invalid value encountered in double_scalars
tmp[kiter] = (macoefs[kiter]-b *macoefs[j-kiter-1])/(1-b**2)
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:676: RuntimeWarning: divide by zero encountered in true_divide
invmacoefs = -np.log((1-macoefs)/(1+macoefs))
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:650: RuntimeWarning: invalid value encountered in true_divide
newparams = ((1-np.exp(-params))/(1+np.exp(-params))).copy()
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tsa/tsatools.py:651: RuntimeWarning: invalid value encountered in true_divide
tmp = ((1-np.exp(-params))/(1+np.exp(-params))).copy()
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tools/numdiff.py:243: RuntimeWarning: invalid value encountered in add
**kwargs)).imag/2./hess[i, j]
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/tools/numdiff.py:243: RuntimeWarning: invalid value encountered in multiply
**kwargs)).imag/2./hess[i, j]
/Users/asmith/envs/pmdarima/lib/python3.5/site-packages/statsmodels/base/model.py:488: HessianInversionWarning: Inverting hessian failed, no bse or cov_params available
'available', HessianInversionWarning)

print(fittedModel.predict(n_periods=2))
[nan nan]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tgsmith61591/pmdarima/issues/101#issuecomment-464357199, or mute the thread https://github.com/notifications/unsubscribe-auth/AWHs7XW8oaF_Tu7Avs6GEnYDtP6LhSt8ks5vOCfggaJpZM4a91ja.

Hey Melissa, welcome to the world of open source 😄 I think Aaron is correct that these are a product of the HessianInversionWarnings in the statsmodels package under the hood, but here are some more clarifying points:

My understanding was that auto-arima tries a bunch of different permutations of parameters, and returns the models in the order of the lowest AIC

This is correct. In addition to AIC, however, you could specify BIC or AICc if you wanted. Not super relevant to your issue, but just in case you weren't aware.

For the first warning where it says ModelFitWarning due to stationarity and there’s an issue with the hessian, it just won’t return that as a valid fitted model, right?

This is correct. When pmdarima detects some of these warnings or errors, it will raise its own warning with a (hopefully) more relevant, helpful message. There is nothing intrinsically bad about these warnings. They often mean your data doesn't pass some test of stationarity so we can't perform time series analysis on them, or that your data may follow a different pattern, like a simple polynomial.

As for the second bunch of warnings (the runtime warnings), what’s the difference between when it throws a warning versus and error?

Unfortunately, this is a design choice made by lower-level package authors. Pmdarima depends on NumPy and statsmodels, both great packages, but which handle errors differently. Consider the following numpy code:
>>> import numpy as np
>>> np.linalg.inv(np.zeros((5, 5)))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/anaconda3/envs/.../site-packages/numpy/linalg/linalg.py", line 532, in inv
    ainv = _umath_linalg.inv(a, signature=signature, extobj=extobj)
  File "/anaconda3/envs.../site-packages/numpy/linalg/linalg.py", line 89, in _raise_linalgerror_singular
    raise LinAlgError("Singular matrix")
numpy.linalg.linalg.LinAlgError: Singular matrix

Numpy will fail out with an error for an operation that cannot be completed, while in many cases statsmodels chooses to warn instead. In fact, you can see the actual code that handles this error handling in auto arima as of v1.1.0 here:
def _fit_arima(x, xreg, order, seasonal_order, start_params, trend,
               method, transparams, solver, maxiter, disp, callback,
               fit_params, suppress_warnings, trace, error_action,
               out_of_sample_size, scoring, scoring_args, with_intercept):
    start = time.time()
    try:
        fit = ARIMA(order=order, seasonal_order=seasonal_order,
                    start_params=start_params, trend=trend, method=method,
                    transparams=transparams, solver=solver, maxiter=maxiter,
                    disp=disp, callback=callback,
                    suppress_warnings=suppress_warnings,
                    out_of_sample_size=out_of_sample_size, scoring=scoring,
                    scoring_args=scoring_args,
                    with_intercept=with_intercept)\
            .fit(x, exogenous=xreg, **fit_params)

    # for non-stationarity errors or singular matrices, return None
    except (LinAlgError, ValueError) as v:
        if error_action == 'warn':
            warnings.warn(_fmt_warning_str(order, seasonal_order),
                          ModelFitWarning)
        elif error_action == 'raise':
            # todo: can we do something more informative in case
            # the error is not on the pmdarima side?
            raise v
        # if it's 'ignore' or 'warn', we just return None
        fit = None

    # do trace
    if trace:
        print('Fit ARIMA: %s; AIC=%.3f, BIC=%.3f, Fit time=%.3f seconds'
              % (_fmt_order_info(order, seasonal_order),
                 fit.aic() if fit is not None else np.nan,
                 fit.bic() if fit is not None else np.nan,
                 time.time() - start if fit is not None else np.nan))

    return fit

There are some statsmodels operations which will internally raise errors (ValueErrors), which we've handled in that loop, but I think what you've identified here may be another case we need to handle. If there are Hessian inversion warnings, there should not be a way for us to really recover for that parameter combination... ideally this would be an error inside of statsmodels, but they left it at warning.
I'm going to add a handler for catching said warnings for our v1.2.0 release. Will leave this issue open in the meantime for related comments or discoveries...

Thank you so much for your thorough explanation! There is one thing I'm still confused about: if the Nans were being produced due to a Hessian inversion warning, does that mean the values produced by ARIMA in the stats modeling package shouldn't be thought of as valid predictions? Consider the following code:

from pmdarima.arima import auto_arima
from statsmodels.tsa.arima_model import ARIMA

trainValues = [144.5, 142. , 139. , 137. , 135. , 135. , 134. , 134. , 133. ,
       132. , 133. , 134. , 137. , 135. , 134. , 134. , 137. , 136. ,
       136. , 125. , 120. , 120. , 121. , 120. , 116. , 119. , 125. ,
       134. , 124. , 113. , 110. , 109. , 110. , 111. , 106. , 106. ,
       102. , 101. , 102. , 105. , 105. , 108. , 110. , 109. , 113. ,
       119. , 120. , 118. ]

fitValues = [115., 126., 142., 146., 165., 175., 184., 192., 200., 208., 215.,
       222., 227., 231., 233., 235., 234., 231., 229., 232., 234., 232.,
       223., 212., 207., 200., 191., 191., 194., 195.]

model = auto_arima(trainValues, seasonal=False)

order = model.order
model = ARIMA(fitValues, order=order)
model_fit = model.fit(disp=0)
model_fit.forecast(steps = 2)

This is the same as what I originally posted except instead of using the fit and predict methods build into auto-arima, I extracted the order and used the arima method from the stats modeling package. In this case, I don't get a warning, nor is the output Nans. If the underlying issue is the hessian inversion, wouldn't I expect to see that warning when I use this other arima function on the same data with the same parameters? Should this new non-nan output be considered valid?

@tgsmith61591 Tagging you so our new Stale bot doesn't close this

On master, I no longer get nans. May have to do with the fact that we recently switched to SARIMAX for everything under the hood (#219).
>>> print(fittedModel.predict(n_periods=2))
[182.60568574<PHONE_NUMBER>2]


Ubuntu reloads /etc/environment at every new login, causing proxy related environment variables to stay till logout. This sometimes causes problems for some applications.

#45 is another one. Closing this.


Vertical bar chart not consistently rendering on iOS

Steps To Reproduce
Visit: https://cbb-world-analytics.netlify.app/years/2017/
Expected Behavior
Two vertical bar charts on the page
Actual Behaviour

Source: https://github.com/zashirah/cbb-world-analytics/blob/main/evidence_project/pages/years/[year].md

Checked into devtools for iOS and saw this warning in the console:
Canvas area exceeds the maximum limit (width * height > 16777216).
Looks like that chart has 165 bars vs. 122 for the other one.
Making the bar width narrower like Archie is proposing in #1320 might solve it by significantly bringing down the dimensions of the chart.
2 other ideas:

When threshold is passed, switch to SVG renderer for that chart
Set a threshold above which the chart will error out

I think once we ship #1320 the charts will still fail silently on ios safari at * some * combination of length and width -- having some kind of failsafe seems necessary.


Profile Career Results Component

Description
A component that shows the Profile Career Results
Fixes #109
How to test?
npm run storybook on your terminal and checkout the Profile Career Result component.
Checklist

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] This PR is ready to be merged and not breaking any other functionality

Very good job Nashmil. It looks ready to be merged for me.

Thank you very much Mohammed!


Add example for json serialization usage

Added example for json serialization usage.

Linux test PASSed.

Windows test FAILed.

verify-windows

Windows test PASSed.


[Release] Add build container dockerfile to release code

Adds a Dockerfile to the release code that constructs an environment capable of building Beam containers. This acts as a workaround in the event that a release manager's local environment provides a different version of Glibc than expected during the release process, as seen in 2.47.0 RC3's initial container rollout.

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

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

The container looks good to me.
I am thinking about for the "docker-in-docker" approach, if we can build necessary artifacts within this container, then take these artifacts out and into another container, instead of build another docker image inside this container, would that mitigate the huge disk size issue?


Regex whitelist feature

Adds a regex set matching feature so that if the request fails and the url matches against the provided whitelist pattern - it will be retried, otherwise not.
Example:
let whitelist = regex::RegexSet::new(vec!["foo", "bar"]).unwrap();
let reqwest_client = Client::builder().build().unwrap();
let client = ClientBuilder::new(reqwest_client)
    .with(RetryTransientMiddleware::new_with_policy(...).with_whitelist(whitelist))
    .build();

let resp = client
        .get("<IP_ADDRESS>/foo")
        .send()
        .await
        .expect("call failed"); // Will be retried if failed according to policy

let resp = client
        .get("<IP_ADDRESS>/bar")
        .send()
        .await
        .expect("call failed"); // Will be retried if failed according to policy

 let resp = client
        .get("<IP_ADDRESS>/something")
        .send()
        .await
        .expect("call failed");  // Will NOT be retried because the url does not match regex

This feels way too specific to be a first-class feature in reqwest-retry.
But it points at an underlying issue: you can't implement this on your own because RetryableStrategy doesn't take into account the request. That's what we should be reasoning about imo.


Bump version number to accomodate Podaacpy 1.9.0 release

Update to reflect the 1.9.0 release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

ack


Recyclerview Autoplay onscroll

On scroll I can get the scrolled item position from that I can get the youTubePlayerView but I cannot access the play function as I cannot access the youTubePlayer interface.
How can I achieve that?
Thanks in advance
This is my code
recyclerView.addOnScrollListener(new RecyclerView.OnScrollListener() {
            @Override
            public void onScrolled(@NonNull RecyclerView recyclerView, int dx, int dy) {
                super.onScrolled(recyclerView, dx, dy);
                int currentPosition = linearLayoutManager.findFirstCompletelyVisibleItemPosition();
                if (currentPosition == 0|currentPosition > 0){
                    RecyclerView.ViewHolder firstViewHolder = recyclerView.findViewHolderForLayoutPosition(currentPosition);
                    View itemView = Objects.requireNonNull(firstViewHolder).itemView;
                    YouTubePlayerView youTubePlayerView = itemView.findViewById(R.id.youtube_player_view);

                }
            }
        });

How do I get that in scroll listener

Your question was: how do I access the YouTubePlayer from my View holder
The answer is there. Save a reference to your YouTubePlayer in the view holder, then Just keep doing what you're doing and instead of using the reference to YouTubePlayerView use the reference to YouTubePlayer.

Tried but don't know the method to get reference to it

You get the reference when the initialization is successful.

Yes but what will be the code to get the reference cause
YouTubePlayerView` youTubePlayerView = itemView.findViewById(R.id.youtube_player_view);
I can get the view by it but how do I get the youtube player

I have highlighted row 58 in the previous link.

actually I need the code that i would put here
            @Override
            public void onScrolled(@NonNull RecyclerView recyclerView, int dx, int dy) {
                super.onScrolled(recyclerView, dx, dy);
                int currentPosition = linearLayoutManager.findFirstCompletelyVisibleItemPosition();
                if (currentPosition == 0|currentPosition > 0){
                    RecyclerView.ViewHolder firstViewHolder = recyclerView.findViewHolderForLayoutPosition(currentPosition);
                    View itemView = Objects.requireNonNull(firstViewHolder).itemView;
                    YouTubePlayerView youTubePlayerView = itemView.findViewById(R.id.youtube_player_view);

                }
            }
        });```

can you help me out with the code please I'm very new to this

The problem you're having is not related to the library, I suggest taking some time to learn how RecyclerView works.
You can learn more about RecyclerView, ViewHolders etc and how to use them by reading the documentation. Good luck!

See I can get reference to any view but I cannot get reference to the YoutubePlayer Preference.
           public void onScrolled(@NonNull RecyclerView recyclerView, int dx, int dy) {
               super.onScrolled(recyclerView, dx, dy);
               int currentPosition = linearLayoutManager.findFirstCompletelyVisibleItemPosition();
               if (currentPosition == 0|currentPosition > 0){
                   RecyclerView.ViewHolder firstViewHolder = recyclerView.findViewHolderForLayoutPosition(currentPosition);
                   View itemView = Objects.requireNonNull(firstViewHolder).itemView;
                   **YouTubePlayerView youTubePlayerView = itemView.findViewById(R.id.youtube_player_view);**

               }
           }
       });

See my player code is initialized in the recycler adapter and I want to get the reference of the player in the main activity and the event is on scroll recyclerview.. There I can get the youtubeplayer view soI can re intitialize it but I need the player to just call play

See my player code is initialized in the Recycler adapter and I want to get the reference of the player in the main activity and the event is on scroll recyclerview..
There I can get the YoutubePlayerView so can re-initialize it but I need the player to just call play.
Please help me out with this..


ARMv8 for raspberrypi3 32 bit?

I'm wondering why cortexa7 is used for raspberrypi3machine configuration. Is there any reason why
DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4"
require conf/machine/include/tune-cortexa7.inc

should not be:
DEFAULTTUNE ?= "cortexa8thf-neon-vfpv4"
require conf/machine/include/tune-cortexa8.inc

in conf/machine/raspberrypi3.conf ?
When we searched online how to compile for the Raspberry Pi 3, people suggested to use armv8.

Take a look at https://github.com/agherzan/meta-raspberrypi/blob/master/conf/machine/raspberrypi3-64.conf

I have already looked at this.
In conf/machine/include/arm/arch-armv8.inc it says require conf/machine/include/arm/arch-arm64.inc, which is obviously for 64 bit. raspberrypi3.conf is for 32 bit, which is what I need. This is why I asked if we could not just change tune-cortexa7.inc to tune-cortexa8.inc, with the proper DEFAULTTUNE?

@michaelbaisch  Raspi is cortexa7 (as far as I remember cortexa8 is quite old - e.g beaglebone).

Oh. I've misread it. I think it was just something we haven't looked into and most probably inherited from RaspberryPi 2. Would you be willing to do some testing and see how it behave compared to ca7?

Actually, I just realised that cortexa8 is an older variant.

Oh okay this is a bit confusing. So cortexa8 is older than cortexa7, and this is what I would have changed with the tune-cortexa***.inc files. What I really want is the ARMv8-A architecture instead of the ARMv7-A architecture. I was confused by the 7 and 8 in the cortex name in relation to the armv architecture name. And the architecture is chosen by the include/arm/arch-armv***.inc files. And there the only armv8 file is 64 bit only. So no luck for armv8 and 32 bit?

So what is the problem you are facing?

We wanted to compile our code with something like -march=armv8-a+crc -mfpu=neon-fp-armv8 and right now we have -march=armv7ve -mfpu=neon-vfpv4.

The Raspberry 3 (B+) actually has a Cortex-A53 (ARMv8).
https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus/
And right now this here is running with -march=armv7ve -mcpu=cortex-a7. I'm guessing this is not optimal?

As far as I can tell there is no way to use ARMv8 in the aarch32 mode in yocto right now. Also I think there is no way to select the right tune cortex-a53 for my raspberry, since the highest I found in yocto was cortex-a17. Other people have done this, I'm not sure why those options for ARMv8 aren't available in yocto…

Do you see any performance impact with the current one we have?

We wanted to keep armv8 as common as possible, in essence similar to x86_64, if someone has real numbers to prove that current tunes are not optimal for real world loads I would be interested to take it further. I have benchmarked current tunes quite a bit as well for my usecases and they hardly make any difference.

We wanted to compile our code with something like -march=armv8-a+crc -mfpu=neon-fp-armv8 and right now we have -march=armv7ve -mfpu=neon-vfpv4.

if you use MACHINE = "raspberrypi3-64" you should be getting armv8 tunes. by default MACHINE = "raspberrypi3" is 32-bit in OE speak.

@michaelbaisch please run some tests and see if you can spot any improvements. For the meanwhile, I'll close this issue but feel free to comment on your findings.


See if we can load zwitterion-config for them

It would be nice to not force the user to explicitly include the zwitterion-config.json script tag

We should be able to do this for them as well as figure out the base href thing...it would be really nice to get rid of that hack. The way we will automatically add zwitterion-config is through regex and modifying the contents of the HTML file before it is loaded...hmmm...this might be harder than I thought actually, since we can't just edit the file before sending it off because it is being loaded over HTTP from the filesystem.


[WIP]:  Notification UI/UX

Is your feature request related to a problem? Please describe.
The current state of Kepler doesn't provide a standard way of displaying errors and it's difficult for users to understand when something is not working the way it should be and for developers to extend UI in a cohesive and consistent way as part of the workflow.
Describe the solution you'd like
If we consider Kepler.gl workflow we have the main steps:

Pick source and load data.
Create your visualization.
Since Kepler.gl can also be consumed as library, the notification feature should be flexible enough to accommodate extensions/plugins.

Given the above use cases, Kepler.gl should provide flexible enough set of APIs to support multiple areas/topics out of the box, e.g. file/url/sharing and in more details
-- Ability to register new topics (maybe this is not needed, we can automatically detect the topic field from the notification entry)
-- Ability to register new notifications
-- Ability to remove notifications
Implementation
This section will describe the implementation of the solution in details and will cover new APIs and their functionalities.
We can start form the the storage of the notifications
The new feature should provide the ability to:

Register notifications through API by calling a method, e.g. registerNotification, and providing the notification type, e.g. error, and which topic of the app the message is targeting hence we need to develop a little bit more on the second parameter and understand how this will be used to address the UI/UX. The register notification api will return the id of the newly generated entry
Remove notifications: the user can call at any time the removeNotification and pass the notification id to remove the notification from the screen.

Storing solution
We are going to take advantage of the uiState reducer and create a property object called notifications. Within the new notifications property we are going create an entry for each part of the application we want to target, e.g. file. The final result should look something like the following snippet:
const reducer = {
      uiState: {
        notifications: {
          file: [
            {
              uuid: 123456,
              type: 'warning',
              message: 'Your file contains invalid rows',
              topic: 'file'
            }
          ],
          url: [
            {
              uuid: 678901,
              type: 'success',
              message: 'Your url is has been loaded correctly',
              topic: 'url'
            }
          ],
          // this is generated by a consumer app
          sharing: [
            {
              uuid: 567890,
              type: 'error',
              message: 'The application is not able to upload the current map onto your dropbox account'
              topic: 'sharing'
            }
          ]
        }
      }
    };

Register a new notification
Kepler.gl will provide a new API (action/helper) to register a new notification, the input of the new API will be an object representing the notification.  In order to make the creation of new notifications we are going to provide helper methods
The signature of said methods are the followings:
export type MessageType = 'error' | 'warning' | 'success';
export type Notification = {
  uuiid: string,
  message: number,
  type: MessageType,
  topic: string
};
function createNotification({
      message: string,
      type: string,
      topic: string
    }): Notification {
      return {
        uuid: 'runtime generate and time uuid',
        message: 'whatever',
        type: 'warning',
        topic: 'file'
      };
    }

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I've found it beneficial to keep error state close to the part of the state tree that the error pertains to:
{
  files: {
    loaded: [...],
    errors: [
      {
          uuid: 123456,
          type: 'warning',
          message: 'One of your files contains invalid rows',
          topic: 'file'
       }
  ],
  alerts: [{uuid: 12345, type: 'error', message: 'Your files just loaded'}]
}

By keeping error-state close to success-state you make it easier to pass the errors into components and you leave room for extremely specific types of file-loading errors like a 'fileBadDrag' or fileExtensionIncorrect without needing add a random fileErrorType or tags property onto the notification.
I believe this is flexible enough to meet the stated requirements since, as you mention above, users can register new notifications and remove notifications by altering Kepler's state in the Redux store - which they already have access to.
Not sure if I understand the register new topics requirement but if more flexibility is needed in terms of displaying notifications within Kepler, a portals-based solution might be worth considering - but that likely is not necessary in the initial implementation.

whynotboth.jpg
I generally agree with Ben for the cases we're considering. But I think we should defer the decision of where this state concretely gets set to the consumer as long as it doesn't introduce too much more boilerplate.
It's a little easier to filter than aggregate. I'd rather have a flat array of errors/alerts and then filter them for my app than have to traverse uiState.notifications.
Other considerations:

I'd rather use something deterministic for ids. Generating a UUID using a random number makes it much harder to write tests. Monotonically incrementing integers for ids are just as effective without introducing non-determinism.
If you're going to allow users to edit Kepler's state, it should ideally only be done through exported helper methods. Directly changing Kepler's exported state makes it hard to enforce invariants, and generally makes the API surface much bigger.

Agree with @macrigiuseppe and @btford on storing the errors/notifications in a central place: ui-state-reducer rather than spread them out to all places of the state.
Agree with @btford to use a flat array of notification instead of a map. each notification should have the same shape. then we can filter them based on type or uuid
type Notification should also be more flexible to allow user pass in additional payload if they need to. One of the common entry of error notification is the new Error object, which usually includes a handy stack trace.


Processing always fails with status 400

Seems to have popped up recently. I will check my Google Cloud configuration when I get a chance. Possibly related to #36.

@commentspae Apologies for the potential notification spam. I just deployed a new revision, and noticed that MP3 uploads are succeeding but YouTube downloads aren't. Were you trying uploaded songs or YouTube videos?

MP3 files, apparently.

Did some investigation, but still haven't been able to pinpoint it as a server or library problem. My current guess is that it's the latter. Are you still experiencing the issue with every upload? And if so, what effects and song (if you can share)? Thanks.

Did some investigation, but still haven't been able to pinpoint it as a server or library problem. My current guess is that it's the latter. Are you still experiencing the issue with every upload? And if so, what effects and song (if you can share)? Thanks.

Consolidating NetworkError threads: https://github.com/beat-machine/beat-webapp/issues/43


FieldError in DateRangePicker ignores isInvalid

Provide a general summary of the issue here
FieldError in DateRangePicker ignores isInvalid prop and renders min/max error when using keyboard arrows to adjust dates.
Only after onBlur event normal "expected" validations are show.

🤔 Expected Behavior?
When isInvalid prop set to "false" is used FieldError should not render any errors.
😯 Current Behavior
FieldError renders min max errors
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
In Example:
https://codesandbox.io/p/sandbox/wonderful-swanson-t3qdc6
Change: year to be in the past.
Error message is displayed even with prop isInValid: false
Version
1.0.1
What browsers are you seeing the problem on?
Microsoft Edge
If other, please specify.
No response
What operating system are you using?
Windows 10
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

I see it happening, and I can see in a Textfield in the same document copied from our docs, that the isInvalid prop set to false will prevent the error message from showing.
I'm not entirely sure why one is working and the other not, however, from looking at the code https://github.com/adobe/react-spectrum/blob/34924436f5b76b44b8adbb0a4fdb64c1c15de99f/packages/%40react-stately/form/src/useFormValidationState.ts#L85
it seems as though this should be
isInvalid != undefined
and the object should just use the isInvalid prop instead of hardcoding it to true two lines below

Hi, I've prepared the PR #5991 with fix.
The error only occurs for DateRangePicker and DateField, because only there useFormValidationState gets additional validation by builtinValidation prop.
https://github.com/adobe/react-spectrum/blob/d66cf4d8cd4657c562ce52d3f37df0a1fa685416/packages/%40react-stately/datepicker/src/useDateRangePickerState.ts#L178-L183
https://github.com/adobe/react-spectrum/blob/d66cf4d8cd4657c562ce52d3f37df0a1fa685416/packages/%40react-stately/datepicker/src/useDateFieldState.ts#L329-L333
That's why the field with an error controlled by isInvalid shows the wrong error. It is overridden by builtinValidation.


Set up Travis/Appveyor for Python 3.6

This is so we can build wheels for python 3.6 on Linux, macOS and Windows.

I'd suggest we also drop python 3.3 now that 3.6 is out.
The CI matrix is getting a bit too long...

The Python 3.3 installer does no longer work on the latest osx Travis images, so I had to remove it
https://travis-ci.org/anthrotype/pyclipper/jobs/192154380#L84
I also removed python 3.3 from Appveyor. Windows users can more easily update their pythons than Linux users who usually have it bundled with their OS.
We still test/build 3.3 for Linux on Travis.

Hmm looks like Appveyor is stuck since three days..
Can you try cancelling and restarting the build maybe?

hey @greginvm, sorry to be such a pain.
Any chances we could restart the Appveyor build (the service had a few hiccups last week), and then tag a new release so we can have python3.6 wheels on PyPI?
If you're busy with other stuff, I could volunteer as co-maintainer for the PyPI account and the CI setup. :)

Hey, thanks for the PR! I absolutely agree about the co-maintainer status, I see you are involved in multiple packages and you seem trustworthy. I added you as a collaborator with admin rights to appveyour, you got push rights to this repo, and owner status at PyPI. I think travis should automatically add you and you should be able to manage builds there. With this rights granted I think you should be able to prepare the release yourself and push it to PyPI, let me know if you'll have any problems with it.

Thank you very much @greginvm! 🎉


Overlay fails with "Invalid path"

I believe as a result of 8a257067374594414b641dd6092ee4548c2a27f3 I'm having issues with Overlay::writable in 0.1.14. nix seems to reject paths it finds containing nulls under some circumstances. If I move from using CStr null terminated to OsStr in overlay.rs that seems to fix the issue. I'm happy to provide a PR if that sounds like a reasonable solution. Thanks!

This is a bit unexpected. And I'm not sure how switching to OsStr would help (since the actual C function uses C-string anyway). Maybe if you'll show me the code I could understand the issue better.

Hmm, yes, I'm not confident my approach was correct. The issue is that we have explicit null terminators, and as some point nix is rejecting a path due to this check: https://github.com/nix-rust/nix/blob/30b04c59a91d83157d5876b31c7ea6b3b2f44340/src/lib.rs#L255 In particular, the options string seems to hit that: https://github.com/tailhook/libmount/blob/b01684416d5fe0599e62911a3d259b7667f8dd42/src/overlay.rs#L89

Hm, yes, this line is not needed anymore. I just have to review the whole patch again to figure out what else issues could be, and push a patch.

Fixed this bug and also tmpfs in 0.1.15. Let me know if anything wrong, because it's a bit hard to test.
(also yanked 0.1.14, should have probaly done it earlier)


Update mrlearning-sharing(photon)-ch2.md

Docs Build status updates of commit 52b2508:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mrlearning-sharing(photon)-ch2.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


dict as data in db

is any plan in code to manage db fields as dicts, like
{
"version": 2,
"keys": [
"age",
"knows_python",
"name",
"codes[{}]"
],
"data": {
"231541323453553701": {
"name": "adwaith",
"age": 4,
"knows_python": true
"codes" : {'sape': 4139, 'guido': 4127, 'jack': 4098}
}
}
}

@zv09 what would be the advantage of using pysondb if the data is to be managed as a regular dictionary without using class interfaces?

ok, how to store wrapped data ?
like "codes" : {'sape': 4139, 'guido': 4127, 'jack': 4098}

>>> from pysondb import PysonDB
>>> db = PysonDB('test.json')
>>> db.add({"codes" : {'sape': 4139, 'guido': 4127, 'jack': 4098}})
'281990590628898407'
>>> db.get_all()
{'281990590628898407': {'codes': {'sape': 4139, 'guido': 4127, 'jack': 4098}}}

well, it's simple.. thx u v m


Fixed igustibagus2024 analysis benchmark issues

There were 2 issues related to the Igustibagus2024-domain-transfer-analysis-benchmark :

The benchmark was computing the OOD average score taking into account also the original domain (hvm) for a total of 13 domains, instead of the 12 out-domains we are interested in;
The benchmark was not reporting the error of the final measures.

Below is an example that locally these points are now solved:

@ernestoBocini did you reopen this PR somewhere?


Installing module in Titanium fails

I'm using 3.5.0.GA.  I installed the module using Titanium Studio, and manually from the command line.  I verified that I cp -R modules/iphone/ti.ispeech/0.2/platform/ platform/
As soon as I tried to add the module in the TiApp Editor, and do a build, I get this message:
[ERROR] :  2015-03-07 09:02:06.766 xcodebuild[90704:5b03]  DeveloperPortal: Using pre-existing current store at URL (file:///Users/fartfartfart/Library/Developer/Xcode/DeveloperPortal%206.1.1.db).
[ERROR] :  ** BUILD FAILED **

Any help would be greatly appreciated.

Correct, the latest version of the iSpeech SDK does not support 64x

Thanks.
This is the first time that I'm using Titanium, and I thought that I was doing something wrong.  Perhaps I should read the instructions.

I would encourage you to ask contact ispeech (https://www.ispeech.org/developers/iphone) and ask them to provide support for both 64x and simulator compile options. This will allow for the module to work correctly

iSpeech just updated their SDK to provide support for both the simulator and x64.  Version v04 of the module now is working as expected.


Create - (853 - The State of Frontend.md)

Auto created with Syntax Production Assistant™

As a note, I set the node version to 20 in the vercel project dashboard, it was set to 18 before.


Make all plugins use the plugin manager.

Instead of being build in. It reduces the binary size, and makes everything more consistent. It also gives the users a little bit more power and keeps micro - the editor - small and lean.

Yeah I was already considering moving the Go plugin out, and also probably the linter plugin. But I'm hesitant to move the autoclose plugin out because I think it's more essential than the others. In any case, it's definitely a good idea.

I've changed my mind with regard to the linter plugin, which is now a default plugin again.


REST API: Add GET /record/ endpoint to directly query single record

Add the endpoint to the REST API
Add a function to get a single record to the Rust and Python client

Closed via #525


Closeable ContentSigner

ContentSigner objects hold an output stream that may need to be closed to prevent resource leaks. A caller can get the stream by calling getOutputStream() method, and close it once the work is done. However, it may be easy to forget to do that.
If ContentSigner extended AutoCloseable:

a caller could use it in a try-with-resources block
static analysis tools could detect places where a ContentSigner.close() is not called

Updating ContentSigner to extend AutoCloseable is definitely an update in the public API. That may potentially result to compilation errors in client apps. Those errors should be easy to fix thought. Moreover, those errors may make developers look at and fix possible resource leaks in their code.
Here is a summary of the update:

Updated interface ContentSigner to extend AutoCloseable.
Implemented close() method in several anonymous classes that implement ContentSigner.

I'm not sure... was there a specific reason you did not suggest changing the return for getOutputStream()?

Do you mean changing the return type of getOutputStream()? I don't think it's going to help. The main idea here is to let ContentSigner close its resources by itself in its close() method. Then, allers are only responsible to close the ContentSigner and it then does all the required work by itself.


[scripts] remove defunct ycsb.sh

We should have a single entry point for our client. Right now we have two and it's clear the python one is being better maintained.
While I'd prefer the portability of having things use shell scripts, we're not there right now and having a partially-done version is confusing.

Looks good to me.


Fixed some minor errors in the documentation.

Hi, I've been trying to configure a CouchDB 2.0 cluster with Ansible. In the process I've found some issues with the URLs and the JSON payload. So I've proposed some changes.

:+1:

merged, thank you! :)

@kafecho due to git[hub/asf] weirdness, the commit isn’t picked up as being merged. Could you please close this PR manually? Thank you! :)


Various pointcloud optimizations - no quantitative changes

Collectively these changes improved the speed of the pointcloud calculations by ~30% on my hardware.  We cache the sobel kernel creation, reduce calls to clear the cuda cache, JIT the inner action of the mean indiscriminate vector, and remove a redundant angular distance calculation.
All existing tests remain passing.

Great work! Lot's of speedups that should make the calculation faster.


Add missing Shory language

Add Shory Language from Stolen Fate Player's Guide

Make sure to git checkout master before starting new branches so you don't have old changes floating around on your PRs.
Also we need to add the language to the languages list in src/scripts/config/index.ts as well as the localization key.

Renamed to be in imperative case. PR titles should finish the sentence "If merged this PR will ", this makes it easier to quickly write the changelog during updates.


[SMALLFIX] Clean up in the test module

Minor fixes in the test module.
IntegrationTestUtils: Fixed link in documentation and introduced automatic resource management in try statement.
FileInStreamIntegrationTest: Introduced automatic resource management in try statement.
LocalBlockInStreamIntegrationTest: Introduced automatic resource management in try statement.
RemoteBlockInStreamIntegrationTest: Introduced automatic resource management in try statement.
ConcurrencyTestUtils: Fixed documentation.

Merged build finished. Test PASSed.

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

Thanks for the improvements, LGTM


Add process "weight" to control scheduling parallel processes

BuildXL has a limited number of process slots that determine how many processes can run concurrently during the build. Previously, all process pips took up one slot, no matter how resource-heavy the process was.
This PR adds the concept of process "weight" that processes can use to indicate they require more resources/slots than average and should not be run in parallel with as many other processes.
Changes

Add "weight" field to Process, which represents how many process slots that process needs to run
The total "weight" of all processes running concurrently must be less than the number of available process slots (dictated by /maxproc and possibly RAM available)
"weight" defaults to 1, converts values < 1 to 1, and considers values >= available process slots to mean the process should run alone

Make sure to tag your commit message with the associated Azure Boards work item

I went on the work item and added the GitHub PR as related work. I assume that is equivalent, but there's nothing in the GitHub UI to indicate it unfortunately.

In reply to: 478784432 [](ancestors = 478784432)

@almiliMSFT is added to the review. #Closed

/azp run Public BuildXL PR Validation


Add SettingEngine entries needed for offline sync

Allow users to set statice ICECredentials and to disable
DTLS Certificate Verification

Codecov Report

Merging #934 into master will decrease coverage by 0.01%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##           master     #934      +/-   ##
==========================================
- Coverage   76.75%   76.74%   -0.02%
==========================================
  Files          59       59
  Lines        4332     4343      +11
==========================================
+ Hits         3325     3333       +8
- Misses        730      733       +3
  Partials      277      277

Impacted Files
Coverage Δ

certificate.go
67.07% <0%> (-1.68%)
:arrow_down:

settingengine.go
52.08% <0%> (-6.06%)
:arrow_down:

dtlstransport.go
72.77% <0%> (-0.78%)
:arrow_down:

icegatherer.go
81.96% <100%> (+0.14%)
:arrow_up:

icetransport.go
77.93% <0%> (+1.37%)
:arrow_up:

internal/mux/mux.go
90.76% <0%> (+6.15%)
:arrow_up:

Continue to review full report at Codecov.

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


add apical_point.py example

Codecov Report

Merging #636 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #636   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          41     41
  Lines        2033   2033
=====================================
  Hits         2033   2033

I think apical_point.py should better live in morph_tool instead. What do you think @mgeplf ?

yup, sounds good to me...this was always just a placeholder


Update last release's CHANGELOG with some tips

Note that we should also think about providing an error message when swiftgen images is passed a non-xcassets directory (instead of making the command line succeed without error but have the generated file contain "// No images found")
\cc @djbe
\ref #175  #214 (imports)
\ref #199 #207 (assets catalogs)
\ref #213 (multiple paths)

We'll have to do this based on the "extension" of the folder, because actool happily tries to parse a folder structure but does not then "dive" into catalog "files", and ignores any other files. Sample output from xcrun actool --print-contents UnitTests/:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.actool.catalog-contents</key>
	<array>
		<dict>
			<key>children</key>
			<array>
				<dict>
					<key>filename</key>
					<string>expected</string>
				</dict>
				<dict>
					<key>filename</key>
					<string>Filters</string>
				</dict>
				<dict>
					<key>children</key>
					<array>
						<dict>
							<key>filename</key>
							<string>Fonts</string>
						</dict>
						<dict>
							<key>filename</key>
							<string>Storyboards-iOS</string>
						</dict>
						<dict>
							<key>filename</key>
							<string>Storyboards-OSX</string>
						</dict>
					</array>
					<key>filename</key>
					<string>fixtures</string>
				</dict>
				<dict>
					<key>filename</key>
					<string>TestSuites</string>
				</dict>
			</array>
			<key>filename</key>
			<string>UnitTests</string>
		</dict>
	</array>
</dict>
</plist>

Yeah, I was more thinking about checking each file extension before invoking actool on each of them

Jup, #217 should be merged alongside this.

Cool!
CI might take some time, it seems like Travis is having issues again: https://www.traviscistatus.com/incidents/nq0sf0srvx8s


Replace oh-my-zsh with zplug

https://github.com/zplug/zplug
https://github.com/zplug/zplug/wiki/Configurations
https://terriblecode.com/blog/zplug-from-a-former-oh-my-zsh-user/

zplug was actually slower, I might consider zim later though


Modelling date/times based on java.time types

Also ignored the entire .idea directory.

@camjo Where did we end up on this? Just an Impala-like "TIMESTAMP" that's basically epoch time?

The merged PR has both instant and LocalDate. After rereading, I think the suggested approach above was to remove LocalDate and have it as a specialisation of a timezone-less Instant. Timezones would be stored as separate fields from the looks of it. @idc101 - Care to raise another PR dropping LocalDate for now until we either decide we need it or implement it on top of Instant?

@ritschwumm The latter. I probably could have phrased that better :)


Add visibility selection (to control ACL) to the uploader

Similarly to #356, but before ingesting a video. Blocked by:

#671

Open question:

What to do when user uploads into a series?

This is done in https://github.com/elan-ev/tobira/pull/911 / https://github.com/elan-ev/tobira/pull/947
Will close this. @dagraf could you create a separate issue with your exact requirements?


Not working correctly with large numbers

Bit representation of large numbers is not correct, here I am using a 64 bit number, and it discards the reading of first 3 bytes, same happens with larger numbers with more discarded bytes

Thank you for raising this issue
I'll try to find a solution for this problem

Fixed the issue in new plugin version 0.3.2 (https://github.com/nia40m/vscode-display-nums/commit/54832c016f24b0f15f0afef339410fec5a092473)
It is already available in the store so please test it when you can @MohamedYKamal


Adding an ability to see full state from a combined reducer

Do you want to request a feature or report a bug?
Feature
Prior Issues
None
New Features
What is the new or updated feature that you are suggesting?
I would like to see state - the entire, full state, not just the slice - passed as the 3rd argument to a reducer used in combinedReducers.
Why should this feature be included?
combineReducers is wonderful for creating nicely separated, logically consistent reducers. However, there's occasionally edge cases where it is justifiable for one reducer to need data from another. Right now it requires some messy code, either special casing a middleware to attach additional data, arbitrarily getting the store, or awkwardly pulling in extra data to an action when it's created.
With state as a 3rd arg it would be possible to grab the required data easily and cleanly. I think this is actually the biggest downside of it as well, since it could encourage abusing this ability to write reducers that break outside their bounds more often than just edge cases.
It would be fully backwards compatible since no reducer expects a 3rd arg right now.
What docs changes are needed to explain this?
https://redux.js.org/api/combinereducers/ & maybe https://redux.js.org/basics/reducers/ 's section on combineReducers

The core code change for this is just a few characters, I wrote this when I realized I'd have to also update the types & tests but could do a PR for this if it's something that would be considered.

The problem is: which state are you expecting to be passed? The one from before the reducer ran, or passed from other reducers? In the latter case, how do you control ordering? What about circular dependencies?
It's not an easy problem to solve, because the answers to those questions mean different things to different people. We've discussed this quite a bit in #2795, #2750, #1904, #1768, and #1527. It's also related to #1518 and #1400.
The conclusion is there isn't a comprehensive answer that also keeps in line with the central tenants of Redux.


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: istio-testing
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test e2e-simpleTests

prow/e2e-simpleTests-cni.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test e2e-simpleTests

prow/e2e-simpleTests-cni.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
a274f0e3e23bc452e6d1cade5047d3efebbfcaa4
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Update attachment-tput-driver for validation and IPAM errors

@matte21 : oddly, I can not find your comment on this PR.  But here is my response.  In the attachment-tput-driver, the other errors from the IPAM controller should never happen and so it is good to stop if and when one appears.

It's because I deleted the comment shortly after writing it.
When I first read the change I missed a negation in an if condition and
thus assumed the code was doing something different.
Reading the same code more carefully provided the answer you gave.
On Sun, Jun 23, 2019 at 7:31 PM Mike Spreitzer<EMAIL_ADDRESS>wrote:

@matte21 https://github.com/matte21 : oddly, I can not find your
comment on this PR. But here is my response. In the attachment-tput-driver,
the other errors from the IPAM controller should never happen and so it is
good to stop if and when one appears.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MikeSpreitzer/kube-examples/pull/64?email_source=notifications&email_token=ADXKVHXKNVSEV2KARTXGUELP36XPRA5CNFSM4H2YBBW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLDIYI#issuecomment-504771681,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADXKVHXESCZNRZOVT6DW63TP36XPRANCNFSM4H2YBBWQ
.


apply new design to build page

Applied new design to build page.
Also added the favicon.

NOTE: merged into dev for testing

Looks good:


hey palant

@palant ... Hi Wladimir, this is just FYI
Article: https://palant.info/2020/12/10/how-anti-fingerprinting-extensions-tend-to-make-fingerprinting-easier/
hackernews: https://news.ycombinator.com/item?id=25374383
snipped now that Wladimir has read it

sorry for wasting anyone's time

Interesting project, thanks for sharing. Yes, my article was very basic. The point was mostly that anti-fingerprinting extensions already tend to get these basics wrong – it’s ridiculous how much anti-fingerprinting can be detected with a very basic and generic approach. I wouldn’t mind moving on to more advanced topics, but that’s pretty pointless right now. :smiley:

For those reading along at home, Chameleon now protects all iframes on TZP - @sereneblue 👍  .. but no one beats my BS pinnochio detector 🍻

but no one beats my BS pinnochio detector 🍻

I will get there... ;)

I will get there... ;)

Challenge accepted... :)
Not sure how you're going to defeat

logic and expected values when claiming to be non-FF
feature detection on items you can't change (but might disrupt)

e.g. being Firefox
e.g. widget fonts (gives me OS) which you could disrupt by blocking getComputedStyle: but it's not the only way to get OS
e.g. FF version test: these are features that can't be changed by the end user in prefs etc. Right now I haven't even added checking the version in userAgent: some of those could be disrupted
^^ but that's a game of whack-a-mole: for example: some versions I do multiple checks, and some can't actually be tampered with AFAICT - never dived too deep into it making uber-robust when under attack

@palant Not sure if you were aware of this:

https://abrahamjuliot.github.io/creepjs/tests/prototype.html
https://github.com/abrahamjuliot/creepjs <-- home
https://github.com/abrahamjuliot/web-fingerprinting <-- also home to prototype lies for some reason

just @abrahamjuliot if have any questions
also: there are mathematical proofs that can unmask a lot of spoofing: by either the browser (not a problem if an enforced set do it: like Tor Browser users) or by an extension


Webpack loader

I want to build a webpack loaded for this. What do you think? Maybe a plugin would be more appropriate?

Not sure! Probably not a loader, since you wouldn't have any tasks that rely on the "transformations" applied by jsinspect (its output). A plugin could maybe make sense if you wanted to constantly write jsinspect's output to some build file automatically. More often than not, it's likely easier to just use it in an npm script.

Closing for now :)


SecretsManager ListSecrets API response deserialisation error

Description
When calling SecretsManager ListSecrets API, the SDK produces a JSON deserialisation error
Context
I am trying to use SecretsManager from a swift application.  Current version of SDK 0.2.6 crashes when calling ListSecrets API
Environment

AWS Swift SDK version used: 0.2.6
Operating System and version macOS 12.5.1
Xcode version (if applicable): 13.4.1
Swift compiler version (if applicable): 5.6.1
Swift Tools version (if applicable): ?

Reproduction Steps
//
//  main.swift
//  TestAWSSDK
//
//  Created by Stormacq, Sebastien on 31/08/2022.
//

import Foundation
import ClientRuntime
import AWSSecretsManager

@main
struct MainApp {
    static func main() async {
        do {
            SDKLoggingSystem.initialize(logLevel: .debug)

            print("preparing")
            let awsSM = try SecretsManagerClient(region: "us-east-2")
            print("calling list secrets")
            let listSecretsOutputResults = try await awsSM.listSecrets(input: ListSecretsInput())
            print(listSecretsOutputResults)

        } catch {
            print("\(error)")
        }
    }
}

Observed Behavior
preparing
calling list secrets
2022-08-31T21:24:34+0200 info SecretsManagerClient : [Logging] Request: POST https:443
 Path: /,
 Authorization: AWS4-HMAC-SHA256 Credential=AKIAXCTVZHOCUDQ5ZBW7/20220831/us-east-2/secretsmanager/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target;x-amz-user-agent, Signature=177c9df03a9e24a20b60de6f8beb90e8b3d0808729ead854b2dca92381bfb63b,
X-Amz-Date: 20220831T192434Z,
Host: secretsmanager.us-east-2.amazonaws.com,
x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: secretsmanager.ListSecrets,
Content-Type: application/x-amz-json-1.1,
Content-Length: 2,
User-Agent: aws-sdk-swift/1.0 api/secrets-manager/1.0 os/macOS/12.5.1 lang/swift/5.6
 Optional([])
2022-08-31T21:24:34+0200 info SerialExecutor : [Logging] Creating connection pool for Optional("https://secretsmanager.us-east-2.amazonaws.com/?")with max connections: 50
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://secretsmanager.us-east-2.amazonaws.com/?")
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] headers were received
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] headers were received
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] headers were received
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] headers were received
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] header block is done
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] incoming data
2022-08-31T21:24:35+0200 info CRTClientEngine : [Logging] stream completed
2022-08-31T21:24:35+0200 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://secretsmanager.us-east-2.amazonaws.com/?") is closing
client(ClientRuntime.ClientError.retryError(Swift.DecodingError.keyNotFound(CodingKeys(stringValue: "RotationEnabled", intValue: nil), Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "SecretList", intValue: nil), _JSONKey(stringValue: "Index 0", intValue: 0)], debugDescription: "No value associated with key CodingKeys(stringValue: \"RotationEnabled\", intValue: nil) (\"RotationEnabled\").", underlyingError: nil))), nil)
Program ended with exit code: 0

Expected Behavior
call returns a ListSecretsOutputResults instance
Possible Solution
Fix the JSON/enum definition for ListSecretsOutputResults

This is bug in the SDK deserilization.
RotationEnabled is boxed but generated as non-null.
https://github.com/awslabs/aws-sdk-swift/blob/0.2.6/release/AWSSecretsManager/models/Models.swift#L4048-L4049
        let rotationEnabledDecoded = try containerValues.decode(Swift.Bool.self, forKey: .rotationEnabled)
        rotationEnabled = rotationEnabledDecoded

should have been
        let rotationEnabledDecoded = try containerValues.decodeIfPresent(Swift.Bool.self, forKey: .rotationEnabled)
        rotationEnabled = rotationEnabledDecoded

Per https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_SecretListEntry.html#SecretsManager-Type-SecretListEntry-RotationEnabled also,  RotationEnabled  is not required.

Thank you for your investigation - this is something that has to be fixed in the SDK generation or Smithy if I understand correctly.
Can you provide an ETA for the fix ?

I understand the change has to be done in either the model definition or in the code generator (I do not know how to do that), but in the meantime, I patched the generated Model.swift file to make it work
➜  mac diff  TestAWSSDK-pkg/.build/checkouts/aws-sdk-swift/release/AWSSecretsManager/models/Models.swift /Users/stormacq/Library/Developer/Xcode/DerivedData/TestAWSSDK-pkg-fxoyjwrfytivhmbgpzhuqsfetfzo/SourcePackages/checkouts/aws-sdk-swift/release/AWSSecretsManager/models/Models.swift
912c912
<             self.rotationEnabled = false
---
>             self.rotationEnabled = nil
953c953
<     public var rotationEnabled: Swift.Bool
---
>     public var rotationEnabled: Swift.Bool?
985c985
<         rotationEnabled: Swift.Bool = false,
---
>         rotationEnabled: Swift.Bool? = nil,
1017c1017
<     let rotationEnabled: Swift.Bool
---
>     let rotationEnabled: Swift.Bool?
1063c1063
<         let rotationEnabledDecoded = try containerValues.decode(Swift.Bool.self, forKey: .rotationEnabled)
---
>         let rotationEnabledDecoded = try containerValues.decodeIfPresent(Swift.Bool.self, forKey: .rotationEnabled)
4048c4048
<         let rotationEnabledDecoded = try containerValues.decode(Swift.Bool.self, forKey: .rotationEnabled)
---
>         let rotationEnabledDecoded = try containerValues.decodeIfPresent(Swift.Bool.self, forKey: .rotationEnabled)
4126c4126
<         public var rotationEnabled: Swift.Bool
---
>         public var rotationEnabled: Swift.Bool?
4148c4148
<             rotationEnabled: Swift.Bool = false,
---
>             rotationEnabled: Swift.Bool? = nil,

Service models are correct, it will be a codegen change. Similar to how init is generated with default value
https://github.com/awslabs/aws-sdk-swift/blob/0.2.6/release/AWSSecretsManager/models/Models.swift#L4148
This default value needs to be set during the deserialization. I have the fix almost ready and will put a PR soon.

@ganeshnj Thank you for the fix, I built a local SDK on my machine and tested the generated code. It now works as expected


cannot navigate w arrow keys in terminal accessibility buffer

inserting adjacent is the problem - needs to be this._terminal.element?.appendChild(this._accessibilityTreeRoot);
specifically https://github.com/xtermjs/xterm.js/pull/4382#discussion_r1084648740
https://user-images.githubusercontent.com/29464607/214367652-d14b2f47-9f83-410e-bfb6-96f99f1f5a19.mov

this is still a problem today in oss off of main
https://user-images.githubusercontent.com/29464607/214602338-908d6356-c843-432b-8916-14cdcd91981b.mov

https://github.com/microsoft/vscode/issues/172394

LGTM on Windows


Fix build break for date formatting change

Defect
Build break in iOS.
Files have been added in the shared folder by 8331a7c, but are missed in iOS project.
Fix
Added the missed files (hopefully all).
Tests
Build on Xcode and see no build error.

Adding @almedina-ms. Please review.

@nesalang made this changes for the ios version so he will have to merge after this

Sorry about that, I had PR integrating the build break changes, and PR was pending on code review; master should be good now, and closing the PR for now.
Thank you.

In reply to: 369464209 [](ancestors = 369464209)


move the status bar from the left side to the right

Move the status line contribution from the left hand side to the right.

I'd rather keep the buttons on the left.

@k2b6s9j Me too

The No Errors is good on the right though.

@k2b6s9j Yep I agree, but for some reasons AsaAyers doesn't, that's why I abandoned https://github.com/AtomLinter/Linter/pull/576

I actually don't have strong opinions about which side it should be on. I do think the status line contribution should be a little more compact...

We are happy to merge it in if you keep the tabs on the left and move the status icon to the right. Just like the in the old PR I referenced above.

Cool, here it is:

:shipit:


unable to fix reference already merged into reference assembly

I am attempting to merge MassTransit 2.8 and Magnum into my own assembly.
Magnum has Newtown.Json merged already into itself, MassTransit references a different version.
Using the latest IL-Repack from Nuget
I get this error
WARN: Method reference is used with definition return type / parameter. Indicates a likely invalid set of assemblies, consider one of the following
WARN:  - Remove the assembly defining Newtonsoft.Json.Utilities.<22393bc1-1b24-4381-8b42-1e880f8e1d97>IWrappedDictionary from the merge
WARN:  - Add assembly defining Newtonsoft.Json.Utilities.<22393bc1-1b24-4381-8b42-1e880f8e1d97>IWrappedDictionary Newtonsoft.Json.Serialization.JsonDictionaryContract::CreateWra
pper(System.Object) to the merge
A type load expection if i try and use the DLL (enumerate the types in it)

I'm observing the exact same problem with this public repository: https://github.com/dennisdoomen/piercer/tree/AttemptToUseILRepack

Same warnings on my side, any fix ?


Enhancement: Extend spo site set command with support for setting the sharing capability of the site

Raised from #1648
We should extend the spo site set command with a new option called --sharingCapability that is optional, which accepts a valid SharingCapabilities value.
The valid values are as follows.

Disabled
ExternalUserSharingOnly
ExternalUserAndGuestSharing
ExistingExternalUserSharingOnly

Source: https://docs.microsoft.com/en-us/previous-versions/office/sharepoint-csom/dn174825(v=office.15)

All yours @arjunumenon 👏

@garrytrinder  / @waldekmastykarz  - I have made the implementation of the new feature which is to add SharingCapabilities  to o365 spo site set
Before I finalize the approach, I just want to confirm the implementation.
Since SharingCapabilities   setting could be enabled only thorough a REST call to the tenant URL. Following are the details
URL : https://TENANTNAME-admin.sharepoint.com/_vti_bin/client.svc/ProcessQuery
Request Body :
<Request AddExpandoFieldTypeSuffix="true" SchemaVersion="<IP_ADDRESS>" LibraryVersion="<IP_ADDRESS>" ApplicationName="Office 365 CLI v2.13.0" xmlns="http://schemas.microsoft.com/sharepoint/clientquery/2009">
    <Actions>
        <ObjectPath Id="2" ObjectPathId="1"/>
        <ObjectPath Id="4" ObjectPathId="3"/>
        <SetProperty Id="5" ObjectPathId="3" Name="SharingCapability">
            <Parameter Type="Enum">2</Parameter>
        </SetProperty>
        <ObjectPath Id="7" ObjectPathId="6"/>
        <ObjectIdentityQuery Id="8" ObjectPathId="3"/>
    </Actions>
    <ObjectPaths>
        <Constructor Id="1" TypeId="{268004ae-ef6b-4e9b-8425-127220d84719}"/>
        <Method Id="3" ParentId="1" Name="GetSitePropertiesByUrl">
            <Parameters>
                <Parameter Type="String">https://TENANTNAME.sharepoint.com/sites/SITENAME</Parameter>
                <Parameter Type="Boolean">false</Parameter>
            </Parameters>
        </Method>
        <Method Id="6" ParentId="3" Name="Update"/>
    </ObjectPaths>
</Request>

Can you verify and let me know the implementation is correct so that I could freeze the approach from my side. Let me know if you have any questions / my approach is not correct.

Hey @arjunumenon I'm not completely up on this API but it looks ok to me. I assume you've taken the approach of using Fiddler to snoop on the CSOM request to understand the required XML payload?

Thanks @garrytrinder for the direction. I did.
I had snooped the fiddler trace for CSOM and have confirmed the payload which is being sent. I also had verified the fiddler trace for PnP PowerShell as well.
I would be finalizing the approach and would be making a PR pretty soon.
Thanks again for the support.

Great, thanks for your help @arjunumenon 👍🏻


Support for configuration tag in plugin's execution tag.

Hi there!,
While using this project for parsing one of my projects, I stumbled upon a problem involving parsing the "configuration" tag in the execution tag of a plugin. The tag I'm referencing is :

build > plugins > plugin > executions > execution > configuration

In my case I'm specifically using execution configurations with the maven-dependency-plugin. Which looks something like :
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <version>3.1.1</version>
    <executions>
        <execution>
            <id>copy-artifact</id>
            <phase>package</phase>
            <goals>
                <goal>copy</goal>
            </goals>
            <!-- VVVV This tag is omitted on parse -->
            <configuration>
                <artifactItems>
                    <artifactItem>
                        <groupId>${project.groupId}</groupId>
                        <artifactId>${project.artifactId}</artifactId>
                        <version>${project.version}</version>
                        <type>jar</type>
                        <destFileName>${outputname}</destFileName>
                    </artifactItem>
                </artifactItems>
                <outputDirectory>./jars/</outputDirectory>
            </configuration>
            <!-- ^^^ Till here -->
        </execution>
    </executions>
</plugin>

Can add a PR with the existing map based struct member for configurations added to PluginExecution struct. Similar to what I see is added to Plugin struct. Wanted to confirm if this is an issue beforehand.

@Gautham-JS Which version are you running? The PluginExecution struct has the Configuration field you are looking for already. It was added in version v0.2.2, so if you upgrade to that version or newer you should be good to go.

Hi there, my bad, I was running version 0.1.2 which is why I was not seeing that execution tag in my code. Apologies for the confusion.
Closing this issue.


[GitHub] TypeError: Cannot read properties of null (reading 'name')

Description
Fixes #4831
Fixes #7796
Checklist

[ x] I read the extension guidelines
[ x] I read the documentation about publishing
[ x] I ran npm run build and tested this distribution build in Raycast
[ x] I checked that files in the assets folder are used by the extension itself
[x ] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer fixed the last errors 😃

Im not able to generate new types though (see https://github.com/raycast/extensions/pull/7824/commits/66df5e503aa74c8a634ad261b629fc54b41942b8#diff-4dfaeb9b21e0a785a07744aee086c85668ea88ccaaa35e5fc08ebde804321b6aR227) but made a workaround


Difficult to read inactive tab names

Tab names for inactive tabs are white on a gray background, difficult to read.
➜  ~ nvim -v
NVIM v0.2.2
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -I/tmp/neovim-20180209-92407-udkzoo/neovim-0.2.2/build/config -I/tmp/neovim-20180209-92407-udkzoo/neovim-0.2.2/src -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20180209-92407-udkzoo/neovim-0.2.2/build/src/nvim/auto -I/tmp/neovim-20180209-92407-udkzoo/neovim-0.2.2/build/include
Compiled by<EMAIL_ADDRESS>

I'm using neovim inside iTerm2

Suggestions on colors or names of other color attributes to match?  Either that or send a PR.

Opened a PR #14 for adding colors for tabs.

Using Vim 8, getting the same result (using the latest version of darcula). What fixes it for me is:
" hi TabLineFill ctermfg=146 ctermbg=16 cterm=NONE guifg=#a9b7c6 guibg=#2b2b2b gui=undercurl
hi TabLine ctermfg=146 ctermbg=16 cterm=NONE guifg=#a9b7c6 guibg=#2b2b2b gui=undercurl
hi TabLineSel ctermfg=146 ctermbg=59 cterm=NONE guifg=#a9b7c6 guibg=#515658 gui=undercurl

Similar lines to these are at the bottom of darcula.vim, but with gui=NONE (not 100% sure why NONE is used here, haven't written a highlighter before).
Uncommenting the first of the above lines will cause the tab bar itself to be colored, which isn't consistent with Vim's default color scheme.


Repeated Field Support?

Is there a way to get repeated field support (i.e., a field that maps into an array)? Use case would be, e.g., a series of checkboxes (arbitrary, unknown length) that all map into a single form field. It seems FormData does support this use case, but I'm having difficulty getting it working.
I was able to kind of work around some of it by allowing either an array or single entry in my Zod configuration, e.g.:
z.preprocess(       (val) => {         // Somewhat awkward -- this gets processed per item in the form,         // but as a whole array in the backend         if (Array.isArray(val)) {           return val;         } else {           return [val];         }       },       z.array(         z.preprocess((val) => {           return typeof val !== 'string' || val === '' ? undefined : Number.parseInt(val);         }, z.number()),       ),     ),
This lets single entry validation work at the field level, while maintaining the whole array validation at the form level.
However, on the backend, it appears preprocessFormData flattens out the FormData and, in doing so, truncates all but the first entry in the corresponding field.

Thought about this some more, and I don't think having multiple inputs with the same name is compatible with the approach taken in this library. Like I said in my last comment, we do support arrays and nested fields which you can read more about here (I'll probably update this documentation to be a little bit more detailed on this topic).
Hopefully that helps, @ddteeter!

Gonna re-open this. After thinking on this more, and learning more about how checkboxes are handled in the standard, I think this is something I would like to support better somehow.

@ddteeter, support for repeated fields is now published in version 3.3.0.


Jwt_Secret_Bruteforce script Added

Description
Jwt_Secret_Bruteforce script is Added olden PR was merged but PR I was unfortunately closed so I was not able to Get marks please Merged these
#398
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I've edited the SCRIPTS.md and link to my code.
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings

Why are just Adding a lines and deleting multiple files in the PR

I deleted other files that are included in this prs @avinashkranjan

What are the contributuions you have made in this PR, Why should I merge it.


Headless Mode / Test Mode

Don't load any windows, maybe don't even init SDL
Optional command line arguments specify filenames for input relay file, output video, memory dump file after some duration.
JSON/XML/TOML test description that specifies replay files along with post-test conditions to expect (color of certain pixels, frame flip count, audio activity)
Possibly do test function outside of the emulator using the outputs instead of integrated? eg. Jest test that analyzes a video and memory dump. Might mean video has to be lossless format though.

This would be very well appreciated!
Even just having some tests for the wdc 65c02 core would be tremendously helpful. I'm pretty sure there are some minor inaccuracies (aside from missing ops and known cycle inaccurate behavior) which continue to exist after my recent prs. Specifically the behavior of the flags when processing ADC/ SBC in decimal mode. Also, manually testing JMP (abs, x) was a total nightmare and I'm left only 98% sure it operates as intended :/


EC2 fixes

Fix a couple of issues I identified with the EC2 driver:

If the instance is removed remotely via a method other than docker-machine, there will be a panic.  This will return the instance as a "Error" state instead.
We were setting d.IPAddress to the wrong value, so this corrects that and fixes an issue where the IP would sometimes not be identified correctly

cc @ehazlett @sthulb

LGTM

LGTM thanks!


flutter test --reporter json includes Android embedding v1 deprecation warning

Steps to Reproduce

Setup Android project with flutter <= 1.12
Update to flutter 2.10.0
run flutter test --reporter json > test-results.json

Expected results:
Test report contains only valid json representing the test results
OR When running either one

flutter --ignore-deprecation test --reporter json > test-results.json
flutter test --ignore-deprecation --reporter json > test-results.json

Test report contains only valid json representing the test results
Actual results:
Test results are preceded by this warning
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Warning
──────────────────────────────────────────────────────────────────────────────
Your Flutter application is created using an older version of the Android
embedding. It is being deprecated in favor of Android embedding v2. Follow the
steps at

https://flutter.dev/go/android-project-migration

to migrate your project. You may also pass the --ignore-deprecation flag to
ignore this check and continue with the deprecated v1 embedding. However,
the v1 Android embedding will be removed in future versions of Flutter.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The detected reason was:

  <path to project>/android/app/src/main/AndroidManifest.xml uses `android:name="io.flutter.app.FutterApplication"`
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

When running either of

flutter --ignore-deprecation test --reporter json > test-results.json
flutter test --ignore-deprecation --reporter json > test-results.json

Could not find an option named "ignore-deprecation".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

Might be related to: Flutter Test should support multiple reporters #69425
Workaround
If you encounter this problem as well, here's my workaround
flutter test --reporter json | grep '^{' > test-results.json
This works because flutter's json reporter stores the test results as a valid json object per line and each json object must start with a {, and no line of the warning starts with {

I do see the same behavior running this use case on latest stable and master:
dhs@Dhss-MacBook-Pro testapp % flutter test --reporter json > test-results.json
This app is using a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to migrate this app to the V2 embedding.
Take a look at the docs for migrating an app: https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.
dhs@Dhss-MacBook-Pro testapp % flutter test --ignore-deprecation --reporter json > test-results.json
Could not find an option named "ignore-deprecation".

 stable, master flutter doctor -v

[✓] Flutter (Channel master, 2.11.0-0.0.pre.452, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.11.0-0.0.pre.452 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ba01ec8faa (27 hours ago), 2022-02-05 22:05:18 -0500
    • Engine revision<PHONE_NUMBER>
    • Dart version 2.17.0 (build 2.17.0-85.0.dev)
    • DevTools version 2.10.0

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 14.4.1 18D61
    • macOS (desktop)           • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 97.0.4692.99

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel stable, 2.10.0, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.10.0 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5f105a6ca7 (2 days ago), 2022-02-01 14:15:42 -0800
    • Engine revision 776efd2034
    • Dart version 2.16.0
    • DevTools version 2.9.2

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.4 19E2269
      darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 97.0.4692.99

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Hey guys, what's up?!
Does anyone know what android:name="${applicationName}" actually do? I've migrated to flutter 2.10, everything is working fine, but I would like to know what this change actually do...

@GaryQian can you take a look at this one? I'm not sure what's going on here.

It looks like flutter test never implemented --ignore-deprecation, which we should add

Off topic, but:
What is --ignore-deprecation?

We are phasing out support for the v1 android embedding. If your app is still using the v1 android embedding, you should migrate to the modern embedding by following the guide here: https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
The --ignore-deprecation flag allows you to force apps using v1 embedding to build. V1 embedding apps are disabled by default. Since we are close to fully disabling v1 builds and removing the ignore flag, we won't be adding the flag for other commands for now. Instead, it is imperative that everyone migrate their apps to the modern android embedding.

Oops, reopening, misunderstood the original issue which is regarding the warning disrupting the JSON output.


[Question][Turbine] Closed water loop

Is it currently possible to create closed waterloop i.e reactor----steam----->turbine----condensating(water)---->reactor....?

It will be in v9.1.


Master tests broken locally

Ruby version: 2.4.1
Bundler version: 1.15.4
macOS Sierra 10.12.6
When trying to run the tests locally, the following failures occur:
Failures:

  1) EtOrbi.make_time turns a Date instance into an EoTime instance
     Failure/Error:
       fail ArgumentError.new(
         "cannot determine timezone from #{zone.inspect}" +
         "\n#{render_nozone_time(s)}" +
         "\n#{self.class.platform_info.sub(',debian:', ",\ndebian:")}" +
         "\nTry setting `ENV['TZ'] = 'Continent/City'` in your script " +
         "(see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)" +
         (defined?(TZInfo::Data) ? '' : "\nand adding gem 'tzinfo-data'")
       ) unless @zone

     ArgumentError:
       cannot determine timezone from "CDT"
       (secs:1477976400.0,utc~:"0046-11-01 05:00:00.0",ltz~:"LMT")
       (etz:nil,tnz:"CDT",tzid:nil,rv:"2.4.1",rp:"x86_64-darwin16",eov:"1.0.6",rorv:nil,astz:nil,
       debian:nil,centos:nil,osx:"America/Chicago")
       Try setting `ENV['TZ'] = 'Continent/City'` in your script (see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
       and adding gem 'tzinfo-data'
     # ./lib/et-orbi.rb:244:in `initialize'
     # ./lib/et-orbi.rb:96:in `new'
     # ./lib/et-orbi.rb:96:in `make_from_time'
     # ./lib/et-orbi.rb:101:in `make_from_date'
     # ./lib/et-orbi.rb:75:in `make_time'
     # ./spec/module_spec.rb:491:in `block (5 levels) in <top (required)>'
     # ./spec/spec_helper.rb:22:in `in_zone'
     # ./spec/module_spec.rb:485:in `block (4 levels) in <top (required)>'

  2) EtOrbi.make_time turns a String into an EoTime instance
     Failure/Error: else expect(eot).to eq(exp)

       expected: #<EtOrbi::EoTime:0x007f97e6387770 @seconds=1478021409.0, @zone=#<TZInfo::TimezoneProxy: America/Bahia_Banderas>, @time=nil>
            got: #<EtOrbi::EoTime:0x007f97e71771c8 @seconds=1478025009.0, @zone=#<TZInfo::TimezoneProxy: America/Bahia_Banderas>, @time=nil>

       (compared using ==)

       Diff:
       @@ -1,5 +1,5 @@
       -#<EtOrbi::EoTime:0x007f97e6387770
       - @seconds=1478021409.0,
       +#<EtOrbi::EoTime:0x007f97e71771c8
       + @seconds=1478025009.0,
         @time=nil,
         @zone=#<TZInfo::TimezoneProxy: America/Bahia_Banderas>>

     # ./spec/module_spec.rb:502:in `block (4 levels) in <top (required)>'

  3) EtOrbi::EoTime#monthdays returns the appropriate "0#2"-like string
     Failure/Error: expect(mds(local(1970, 1, 1))).to eq(%w[ 4#1 4#-5 ])

       expected: ["4#1", "4#-5"]
            got: ["3#5", "3#-1"]

       (compared using ==)
     # ./spec/time_spec.rb:266:in `block (3 levels) in <top (required)>'

Finished in 0.09694 seconds (files took 0.86364 seconds to load)
73 examples, 3 failures

Failed examples:

rspec ./spec/module_spec.rb[1:8:6] # EtOrbi.make_time turns a Date instance into an EoTime instance
rspec ./spec/module_spec.rb[1:8:7] # EtOrbi.make_time turns a String into an EoTime instance
rspec ./spec/time_spec.rb:264 # EtOrbi::EoTime#monthdays returns the appropriate "0#2"-like string

This is from running bundle exec rspec, which I found is the expected way to run tests from the latest CI run, which is indeed passing. I'm on the same SHA as that run, too (ff967e82f5612b01f5db05d46c2e144bddf937b0).
I would assume this is probably a Mac issue.

This seems to be okay on the following version + OS combinations:
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
Bundler version 1.15.4
Fedora release 25 (Twenty Five)

I'm getting this failure with:
Ruby 2.4.2
Bundler 1.16.0.pre.2
Linux 4.9.0-3-amd64 Debian 4.9.30-2+deb9u3 (2017-08-06)
Failures:

  1) EtOrbi::EoTime#monthdays returns the appropriate "0#2"-like string
     Failure/Error: expect(mds(local(1970, 1, 1))).to eq(%w[ 4#1 4#-5 ])

       expected: ["4#1", "4#-5"]
            got: ["3#5", "3#-1"]

       (compared using ==)
     # ./spec/time_spec.rb:266:in `block (3 levels) in <top (required)>'

Finished in 0.04315 seconds (files took 0.35369 seconds to load)
73 examples, 1 failure

Failed examples:

rspec ./spec/time_spec.rb:264 # EtOrbi::EoTime#monthdays returns the appropriate "0#2"-like string

@imtayadeway
Hello,
thanks for reporting. Could you please open a separate issue for the error you're seeing? Could you please indicate in there the timezone for your system (ENV['TZ'] and, more simply, timezone as set in Debian system).
Thanks in advance!

@chrisarcand
Hello,
thanks for reporting. Does following "Try setting ENV['TZ'] = 'Continent/City' in your script (see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) and adding gem 'tzinfo-data'" and setting export TZ='america/chicago' before running bundle exec rspec prevents one, two or all of the spec errors you're seeing?
Thanks in advance!

@carbonin
Hello,
could you please pull the latest https://github.com/floraison/et-orbi/commit/67389818c2b67dc066912cc78445d542ba06625e , run make info and paste the result here?
Thanks in advance!

Hello, I did some work to adapt to latest Travis platform, gh-5. Does that reduce the failures on your sides?

@jmettraux Nope, I pulled the latest changes you made and get the same errors.
Here's the information you seem to have added as output at the top of the tests, if you need it:
--------------------------------------------------------------------------------
Darwin carcand-OSX.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
2.4.2 x86_64-darwin16
(secs:1507039249.3564181,utc~:"0047-10-03 14:00:49.3564181327819824",ltz~:"LMT")
(etz:nil,tnz:"CDT",tzid:nil,rv:"2.4.2",rp:"x86_64-darwin16",eov:"1.0.6",rorv:nil,astz:nil,debian:nil,centos:nil,osx:"America/Chicago")
--------------------------------------------------------------------------------

OK, switched my Macbook to "America/Chicago" and seeing the same failures. Fixing...

Hello, I think I got it fixed. Could you please confirm? Thanks in advance.

Confirmed, everything's green for me now. Thanks!


[W5][W13-2]Chan Ming En Minern

Can consider splitting up the commits into smaller commits :)

    public List<ReadOnlyPerson> sortedImmutableListView() {         internalList.sort(Comparator.comparing(o -> o.getName().toString()));         return Collections.unmodifiableList(internalList);     }
Could consider cases where names are the same
Neat code! 👍