ENH: Make stats.kappa3 work with array inputs

See details at: #13582
cc @mdhaber

Windows tests are timeout failures. How does this look now @mdhaber ?

I tried implementing my suggestion above, and there is still something wrong. I'm not sure if it's a problem with the changes in this PR; it might be a bug in the stats method. (That logic is so complicated, I wouldn't be surprised.)
We should expect res and res2 below to be equal:
import numpy as np
from scipy.stats import kappa3
shapes = [0.5, 1.5, 2.5, 3.5, 4.5]
moments = 'mvsk'
res = np.array([[kappa3.stats(shape, moments=moment) for shape in shapes]
                for moment in moments])
res2 = np.array(kappa3.stats(shapes, moments=moments))

and they should both look something like:
array([[        nan,  2.31495165,  1.1276457 ,  0.90331047,  0.80679709],
       [        nan,         nan,  3.95525273,  0.6693471 ,  0.37900734],
       [        nan,         nan,         nan,  5.73627082,  2.0308587 ],
       [        nan,         nan,         nan,         nan, 25.19163476]])

The diagonal and below should be nan because the order of the moment is greater than the shape parameter.
Unfortunately, we only get that in res. res2 is:
array([[        nan,  2.31495165,  1.1276457 ,  0.90331047,  0.80679709],
       [        inf,         nan,  2.6836679 ,  0.6693471 ,  0.37900734],
       [        nan,         nan,         nan,  5.73627082,  2.0308587 ],
       [        nan,         nan,         nan,         nan, 25.19163476]])

So something is screwy about the variance calculation when you are calculating the variance and other moments versus when only the variance is calculated.

Yes, there's something with variance. Looking into it with the same example and the above suggestion, I see that the problem is here:
https://github.com/scipy/scipy/blob/d11a3d9906dd7b83b3c6bce6a6b37502eba99bea/scipy/stats/_distn_infrastructure.py#L1176-L1177
Here, from the above example:
mu = np.array([np.nan, 2.31495165, 1.1276457, 0.90331047, 0.80679709])
mu2p = np.array([np.nan, np.nan, 3.95525273, 1.4853169,  1.02992889])

Since, np.isfinite(np.nan) is False, we get np.inf (in variance[0]). But still unable to find why variance[2] differs.

That line could just become
mu2 = np.where(~np.isinf(mu), mu2p - mu**2, np.inf)

For the numerical difference, I think it's a central vs noncentral moment thing. Surprisingly, I think the vectorized line, rather than the loop, is correct in this case.
In the vectorized case, consider these lines.
https://github.com/scipy/scipy/blob/d11a3d9906dd7b83b3c6bce6a6b37502eba99bea/scipy/stats/_distn_infrastructure.py#L1149-L1161
mu2 is None as it should be, and g1 is also None.  We don't get to line 1158, and mu2 stays None.
Then later in
https://github.com/scipy/scipy/blob/d11a3d9906dd7b83b3c6bce6a6b37502eba99bea/scipy/stats/_distn_infrastructure.py#L1170-L1180
mu2 is None, so it gets calculated there, with some adjustments that turn the noncentral moment from _munp into a central moment.
In the loop over scalars case, mu2 is None as it should be, but g1 is nan. We get to line 1158, and mu2 gets calculated - but it's the noncentral moment. Later, In L1170-L1180, it doesn't go through the adjustments that turn the noncentral moment into a central moment.
It seems that maybe in L1158, mu2 should have had a different name, maybe mu2p like in L1172.

@Smit-create Please see Smit-create/scipy#6. If that looks good, please merge and add tests, and this will be good to go. Can we do the same thing for kappa4?

I'll add a test. Thanks for the great explanation :)

Can we do the same thing for kappa4?

Yes, I will look into that once kappa3 fixes gets merged.

Thanks @Smit-create! Ping me on a PR about kappa4, please! Hopefully it's just more of the same.


How to pair Android 11+ devices?

Is the pair command supported by Dadb?
If not, it would be great to add this feature.
https://developer.android.com/studio/command-line/adb#connect-to-a-device-over-wi-fi-android-11+

Hi @sharpordie - I'd like to understand your use case a bit better.
Today the following is supported:

Pair your device over wifi using the standard adb pair HOST:PORT CODE command. eg: adb pair <IP_ADDRESS>:5555 123456
Once your device is paired, you can connect to your device using your device's IP address (same as HOST above): Dadb.discover(<IP_ADDRESS>) or Dadb.connect(<IP_ADDRESS>, 5555).

These steps requires the adb binary to initially set up the pairing, but since this is a one-time setup per laptop maybe that acceptable.
Do these steps satisfy your use case or are you looking for something else?

Btw I just added documentation on this in the README: https://github.com/mobile-dev-inc/dadb/blob/master/README.md#connecting-to-a-physical-device
But I'm still interested in whether this solves your use case or if there's a reason you'd need / prefer built-in USB support for dadb?

@sharpordie Please don't hesitate to reopen this issue if the above documentation doesn't work for your usecase!

Dadb is presented as a library to connect to android device without an adb binary or server.
So for me using adb binary to pair (or connect) a device first is a nonsense.
I think a pair method like here in LADB would be more consistent.
https://github.com/tytydraco/LADB/blob/main/app/src/main/java/com/draco/ladb/utils/ADB.kt#L182
But it requires to find out how the official adb forges the "request" for pairing process for a proper dadb implementation.

Here is a adb pair implement: https://github.com/RikkaApps/Shizuku/blob/master/manager/src/main/jni/adb_pairing.cpp

And here is a pure java implementation: https://github.com/MuntashirAkon/libadb-android/blob/master/libadb/src/main/java/io/github/muntashirakon/adb/PairingAuthCtx.java

@tiann
This is exactly what I would like in Dadb (with Kotlin).

Not sure on timeline yet but opening this back up as it does seem like a use case folks are asking for.

This would certainly be a game changer. I'd be willing to put forward some work into this as best I can. This library opens up so many possibilities.

Hi dadb team,
You guys made a great library. I would like ask that any progress on this issue. Because i'm also want pair using dadb and don't want use adb binary either

Hello dadb team,
I hope you guys are doing great,
Thank you for the amazing library...
I am interested in using dadb to pair instead of having other libraries do that...

Google started removing debug over wifi, started with Google pixel watch (March 2023 update), dadb does not work for those watches as the needs to be paired with the device first...

This makes things uncertain whether other watches will follow or stay as they are...
Thank you so much for your hard work...
Regards

We really need adb pair


File uploading using a stream fails when length is unavailable

FTP OS: Windows
FTP Server: IIS
Computer OS: Windows
FluentFTP Version: 35.2.1
I'm passing a stream to UploadAsync which is of an unknown length and has CanSeek set to false. UploadFileInternalAsync tries to access the Length property of the stream, and causes the below exception:
FluentFTP.FtpException: Error while uploading the file to the server. See InnerException for more info.
 ---> System.NotSupportedException: This stream does not support seek operations.
   at System.Net.Sockets.NetworkStream.get_Length()
   at FluentFTP.FtpClient.UploadFileInternalAsync(Stream fileData, String localPath, String remotePath, Boolean createRemoteDir, FtpRemoteExists existsMode, Boolean fileExists, Boolean fileExistsKnown, IProgress`1 progress, CancellationToken token, FtpProgress metaProgress)
   --- End of inner exception stack trace ---
   at FluentFTP.FtpClient.UploadFileInternalAsync(Stream fileData, String localPath, String remotePath, Boolean createRemoteDir, FtpRemoteExists existsMode, Boolean fileExists, Boolean fileExistsKnown, IProgress`1 progress, CancellationToken token, FtpProgress metaProgress)
   at FluentFTP.FtpClient.UploadAsync(Stream fileStream, String remotePath, FtpRemoteExists existsMode, Boolean createRemoteDir, IProgress`1 progress, CancellationToken token)

Thanks for reporting this.

Thanks for reporting this.

We have never tested uploading streams whose length cannot be known, as we have to calculate the upload blocks based on stream length. For now just convert your data into a memory stream with a known length and then try to upload it.

We have never tested uploading streams whose length cannot be known, as we have to calculate the upload blocks based on stream length. For now just convert your data into a memory stream with a known length and then try to upload it.


Do not AddChange when change is null

GetChange will return null When CanUndoProperty return false
But always AddChange to undoStack. Lead to CanUndo is true

Thanks for the info on this issue.
I'll investigate.


Replace 'component' with 'template' in integrations

This PR is to address this issue https://github.com/carstenlebek/svelte-email/issues/5.
The code snippets in the integrations is wrong and causes this error error when run.
TypeError: Cannot read properties of undefined (reading 'render')
    at Module.render (project_name/node_modules/svelte-email/render.js:10:14)
    at GET (project_name/src/routes/api/invite/teacher/+server.js:22:43)
    at Module.render_endpoint (project_name/node_modules/@sveltejs/kit/src/runtime/server/endpoint.js:49:24)

Instead of passing component into render, rather I have replaced it with template.

This looks like a duplicate of This PR that is already open

This looks like a duplicate of This PR that is already open

Thanks for pointing that out. Curious why it hasn't been merged in.


Custom Labels: support git diff view

Hello,
The new feature Custom Labels works well for normal file view, but not for git diff view, could you please add it ?
In the below screenshot, the left tab is the normal view, and the right one is the git diff view.
In the left normal view, I can see that the folder name app is appended as I defined in the custom lable.

/duplicate #211050

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Get data from Binance

Use the Binance API to pull data for processing

How?

Have not figured that out yet 😓
Binance has an API but I haven't had time to play around with it.


fix and improve commands

[line 109]
the switch for truncate is --size, not - size, also there should be a space between two parameters.
[line 110]
Dollar sign is not part of the command and should be removed from the beginning of the command.
It also makes it more aligned with the rest of the document.
[line 111]
remove suppernumerary hyphen character in "- copy" in an English sentence.
[lines 208-212]
The correct command is useradd, not useadd.
Bash commands are case sensitive. I fixed it for useradd, passwd, su and cp commands.
define and use variable, instead of repeating storage account name several times.

@aysabzevar : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

#sign-off


Don't output errors comment

renders a template with errors, but does not display them on the screen.

Task closed


Gradle 5.5 fails similarly to what is already reported and closed

This needs to be resolved, issue reported as gradle 5.0 not working is closed and contains a non-applicable workaround, as the workaround doesn't work. The documentation outlined in two posts also broken. Were is the supported gradle version listed for the macos vmImage. Circular references.

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

ID: 00499395-fdc3-b150-3469-aee2f9fb7cbc
Version Independent ID: 44e630e1-1689-2d2e-212b-3ce2baf8771f
Content: Gradle build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/gradle.md
Product: devops
Technology: devops-cicd
GitHub Login: @DavidStaheli
Microsoft Alias: dastahel

Figured it out, it was due to .gitignore not working properly and excluding the jar file.


onPress cannot work outside the ViewOverflow area.

<View style={{height: 200, backgroundColor: 'white'}}>
  <ViewOverflow style={{width: 200, height: 100, backgroundColor: 'pink'}}>
    <View style={{width: 100, height: 100, position: 'absolute', left: 100, bottom: -50, backgroundColor: 'yellow'}}>
      <TouchableHighlight onPress={() => { console.log(1) }}>
        <View style={{backgroundColor: 'skyblue', height: '100%'}} />
      </TouchableHighlight>
    </View>
  </ViewOverflow>
</View>

zIndex?

zIndex does not work

@gabrielbull  Did you managed to solve this?

@alejandropinson No, onPress does not work in overflowed area with this library.

@gabrielbull  Did you find another workaround with another library, Im creating a dropdown and I need the overflow functionality :/, Thanks anyways! :)

@alejandropinson You can start looking for a solution here: https://stackoverflow.com/questions/27010172/clipped-button-doesnt-receive-touch-input and fix this library with a PR ;-)

Found this https://stackoverflow.com/questions/27727981/android-passing-touch-events-of-a-child-view-drawn-outside-of-view-clip-bounds, I tried to implement the first answer but the app crashes, I'm also quite ignorant in android native development. If anyone could give it a try...
`@Override
public boolean onTouchEvent(MotionEvent event) {
switch (event.getAction()) {
case MotionEvent.ACTION_MOVE:
return ((ViewGroup) getParent()).dispatchTouchEvent(event);
case MotionEvent.ACTION_UP:
int childCount = ((ViewGroup) getParent()).getChildCount();
int x = (int) event.getX();
int y = (int) event.getY();
for (int i = 0; i < childCount; i++) {
final View child = ((ViewGroup) getParent()).getChildAt(i);
if (childContains(child, x)) {
new Handler(Looper.getMainLooper()).postDelayed(new Runnable() {
@Override
public void run() {
child.callOnClick();
}
}, 100);
return true;
}
}
break;
}
    return ((ViewGroup) getParent()).dispatchTouchEvent(event);
}

int[] loc = new int[2];
private boolean childContains(View child, final int x) {
    child.getLocationOnScreen(loc);
    int x1_child = loc[0];
    int x2_child = x1_child + child.getWidth();
    int x0 = x;
    boolean isInside = x0 >= x1_child && x0 < x2_child;

    return isInside;
}`

Any news about that issue?

@jpbretanha You can add press listener on father components, then calculate the area of click events, so you will know which child would be clicked

any example? @xiaweiss a lot of people are struggling, I tried some java code with onTouchEvent(MotionEvent event)  but was unsuccessful
ref: https://github.com/entria/react-native-view-overflow/issues/32

We can use images or icons for view overflow whenever possible as this seems to work fine for me.

@Saksham96 Could you give an example of what you mean? I'm a little bit confused as to how you used an icon for view overflow.

Yeah this issue is happening to me, while I'm trying to use it along react-navigation. I have a tab bar at the bottom of my screen, accompanied with the react-native-action-button floating on top of it; which I cannot press. The parent component of it is the tab-bar, wrapped in a <ViewOverflow> and while I've tried setting the zIndex and elevation, I'm afraid that the underlying reason I can't press is because of this android issue...

bump

I've the same trouble, didn't find any answer

@Xifeat whar rn version you are using.
as far as I remeber they have fixed the android overflow issue in the latest rn version.
So you shoudnt need to use react-native-view-overflow anymore.
https://github.com/react-native-community/react-native-releases/blob/master/CHANGELOG.md#android-specific-changes-2

@kevinNejad I updated All my library and react native 0.57.5 but it's stil not working.
I followed this tutorial https://itnext.io/react-native-tab-bar-is-customizable-c3c37dcf711f
With this branch : https://github.com/alex-melnyk/Tabber/tree/overflow_fixed
But when I press my console.log is never written when I use overflow

@kevinNejad @Xifeat It looks like react-native only added support foroverflow: visible.
Click events on this view are still not working.

I have the same problem. Any news about this issue?
react-native --version
react-native-cli: 1.2.0
react-native: 0.57.4

I use TouchableOpacity & Animated.View classes from react-native.

@tasosxak It simply is not possible on android. try do do it some other way.

+1

@userbq201 Does your brain work? Can you read? why are you spamming a +1? Don't you have anything better to do? It's useless. Don't bother. This will never work, not possible.

@xiaweiss You can close the issue. Not possible

@filipef101 what's wrong with you ? someone else is having the same problem. I will work if you know how to fix it.

It is not possible, it's something android doesnt do

@filipef101 tbh, I attempted to use this library a while ago but it as far as I remember the click event was working. at the end, I had to write a native component and bridge it into RN. Its true that it's sth that RN android does not support atm. but it will be possible to implement it in native and use the component in RN. However, it may not be a good idea to do for big scale project.

Same issue! Anyone solved it ?

Add a TouchableWithoutFeedback wraped all child components(the grey square), then when you touch in the  grey area, in the "onPress" function you can calculate the touch point position.
if the x and y of postion is right, do something
react-native  verison 0.58 supported "overflow:visiable", you might don't need this repo.

Hi @xiaweiss
The solution you gave is still a workaround. The problem is not solved yet, and the issue should be opened I think.
Furthermore the workaround doesn't solve for a case like mine where I need the parent view (the TouchableWithoutFeedback in your exemple) to not take place, pushing down views below it, where the button in absolute is placed.

Using the workaround you told will have the following result.

Does anyone found a descent trick for Android ?  This one is a serious issue ! 😓None of the tricks said above works. Since It's kind a trick setup.
<View>
    <SomeStuff/>
    <SomeOtherStuff style={{position:absolute, bottom:-50, height:100}}/>
</View>

Half of the SomeOtherStuff component will be clickable, the one on the top, (on the screen inside the parent view), the part with negative bottom, half of the component, "outside" the parent one is not .

@xiaweiss just try the TouchableWithoutFeedback, it doesn't work on Android. it actually make the whole view not responding to touch at all.
I think this is still a valid use case that RN not supporting, would be great if we can re-open this.

TouchableWithoutFeedback

TouchableWithoutFeedback is working for me when I using View.Animated.

PR https://github.com/facebook/react-native/pull/26374 should fix this.

+1

In my case i solved this by doing the following, wont always worked. As I wanted my component at the top of the screen, I positioned it absolute, top 0, then gave everything else a top margin of the height of the parent View of the component.

My issue is solved by using this peackge....
import {TouchableOpacity, ScrollView} from 'react-native-gesture-handler';

My issue is solved by using this peackge....
import {TouchableOpacity, ScrollView} from 'react-native-gesture-handler';

This is a pretty old thread but the issue is still prevalent to this day, after tinkering around to find a fixable solution, I ended up landing on the zIndex: value, styling prop, now this isn't an ideal solution, but for now, if anyone encounters this issue, this is a viable solution for some.

The only solution i have found is to place the object absolutely with the root view and placing the corresponding tag at just before the root view tag ends, also to make it responsive, i have normalised the position with respect to screen sizes, though it works but is not the best solution to consider.

My issue is solved by using this peackge.... import {TouchableOpacity, ScrollView} from 'react-native-gesture-handler';

Thanks, this worked


New hook check-macro-has-description

The new hook will fail if a macro has no description in the schema files or in the manifest.
Added tests and "macros" key to manifest in conftest.py

🎉 thanks for contribution @PabloPardoGarcia it looks good!


Add the initial TypeScript setup to begin using it in the repo

I would love to work on implementing the initial Typescript setup so developers can start adding ts and tsx files.
Ideally, rather than using prop-types, TypeScript provides are more robust solution that will improve documentation and scalability.
Give me the go ahead and I'll add the setup and convert the existing code into TypeScript.
This should not interfere with those that would still like to create javascript files, in fact it would only improve their developer experience!

That's a great idea @gaber85.
Go for it.


Allow Mods to bypass command cooldown

Title is very self explanatory, allow mods to bypass cooldown on commands such as +mostdrops as this is a very necessary tool at times when performing moderator duties!! This would not allow mods to bypass cooldown on commands such as =spawnlamp =givebox or any commands that could benefit the user with items, simply just utility commands :)

Done in next update.


pldm: Disabling Active Memory Mirroring for Bonnell

Removed the bios attribute hb_memory_mirror_mode and hb_memory_mirror_mode_current
Fixes: 588132
Tested:
Poweron/poweroff and reset reload case, verified
/redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry

Please change the commit title "pldm" to "oem-ibm". Also add some more info in to the commit message description on why we are removing it.


[Docs] Add API menu and demo button

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

This PR adds a shortcut menu to view the relevant API docs for a particular component, and also an icon to jump to the relevant demo when viewing the API docs.
Most of the menus are automatically generated, but where this isn't possible they can be manually supplied in apiMenuData.js. This file also contains mappings for non-conforming component names, and non-standard demo locations.

I have the following error locally

Sorry, I had missed a check for no path on the home page.
I've moved all that logic into its own component, but I think it will be clearer still to separate the logic for the demo button and the API menu. There will be some code duplication, but I think it will be worth the trade off.

I have noticed two UX points:

On the demo page, I don't think that we should focus the first item.
On the BottomNavigationButton page, I think that we should focus the second item.

I just pushed a split out version, but I'll update based on your code review which I only saw afterwards. 👍

I just pushed a split out version

Which seems to have broken it for certain components. 🙊

Good idea on the menus - I've updated it so that the correct menu item is selected, however when no item is active (i.e when on a demo page), the focus is on the first item by default.
Since focus, hover and selected are the same color, it makes it look selected.

While I think of it - when putting this together I noticed that the switches don't have an API docs page because of the way the code is structured. What was the plan for those?

I think that we should really stop using magic rules 🐰 for doing the mapping.

There really is no easy way around it. Mapping from the API page to the demo page either requires consistent naming & logic, a mapping, or mapping by exception when the logic doesn't apply.

The first (consistent naming & logic) isn't possible by itself.
The second (a mapping) by itself would require a bunch of 1:1 mappings that don't add value. If one of the actually required (exception) mappings was omitted, the result would be the same as now.
The current solution (mapping by exception when the logic doesn't apply) is not perfect for the same reason as above, but at least we're only having to create mappings where they're needed. If I missed one, I'll fix it.

The same logic applies to the API menus, we either provide all of them (I started with that approach) or we only provide those that can't be generated.
I know it's messy, whichever way around. C'est la vie!

A small part of the complexity also stems from the fact we're using different directory naming between components (singuar) and demo directory (plural). I understand the desire to match the MD usage of plural for the docs descriptions, but it might be better if the directory names themselves stayed the same as on master, not least so that external links don't break when the next docs site finally gets published.

 If one of the mappings was omitted, the result would be the same as now.

I'm coming back to my previous comment. I believe that the following structure will address all our needs. Declarative, performant enough, no 1:1 mapping.
mappingRoutesPropTypes: {
  'layout/responsive-ui': [
    'layout',
  ],
  'component-demos/bottom-navigation': [
    'bottom-navigation',
    'bottom-navigation-button',
  ],
  // ...
}

external links don't break when the next docs site finally gets published.

Given how the demos are structured, we are going to have broken links no matter what.

it might be better if the directory names themselves stayed the same as on master

It depends on what's the motivation. I don't think that we should be motived by the implementation constraints but rather by our users experience.

I don't think that we should be motived by the implementation constraints but rather by our users experience.

Okay, I'll switch the demo directory names to singular so external html links to the MUI docs don't break when we finally publish next docs.

Summarizing our discussion regarding keeping the mapping up to date as the documentation evolves and pages/components get renamed.
I think that we could automatically generate the above structure.
Let's see what Bootstrap is doing.
We could add the following markups in each markdown files:
---
components: Checkbox, Form, Radio, Switch
---

# Selection Controls

[Selection controls](https://material.google.com/components/selection-controls.html) allow the user to select options.

...

in each markdown file

And also in the source of each component? One of the biggest issues we're trying to solve is switching between  related component API pages when the left nav is closed.

And also in the source of each component?

Why is that for? I don't think we need that fine grain. As long as they are under the same demo, we can consider displaying them as sibling in the API page section.

I have been receiving feedback from the next documentation (a co-worker). That's feature is really important. I'm will prioritize it.

@mbrookes Do you want me to have a look at this new iteration?

@oliviertassinari Not yet, still a work in progress (I only pushed as a backup), but I"d be interested in your thoughts on the simplified directory structure before I build on it.
Part of the motivation was to be able to find all the relevant md files in require.context(), but I also think it makes the tree easier to navigate.

I would definitely do the following changes

/docs/site/demos/ => /docs/component-demos
/docs/site/pages/layout/ => /docs/layout
/docs/site/pages/style/ => /docs/style

I feel like it's going back to the master approach.

I think it's cleaner & clearer than both master and the current next structure.
My main concern with moving everything up to the root directory was mixing site and configuration files. That makes the structure harder to follow, and the code that parses the site content more complex, (larger black or white-lists to maintain) .

A perfect world for me would be having a flat markdown folder structure and a /site folder handling the core documentation generation.

I find it slightly odd to have the site component files and tooling config in a subdirectory, and the site in the root - the hierarch seems inverted... but I'm always happy to compromise (after vigorous debate! :wink) - let me try that and see how it looks - at least it addresses the 'mixing' problem, and surfaces the most actively modified files.

I'm suggesting the inverted folder structure for discoverability. But in the end, linking matters a lot more. As long as we link the content correctly, users will be able to discover it.
Yes, let's fix the inconstancy (markdown at different location) and make the autogenerator smarter.

Closed with #6455


update ci user

This updates the CI user configuration to use a CFN template and remove the encrypted variables from travis/appveyor.
cc @mapbox/core-tech

Thanks @mapsam - looks good, will merge now.


Confirm Email Does not stop login

Thanks for the great work. Not sure of the value of the "ConfirmEmail" if login is still permitted without having confirmed the email.  Is there something I'v missed?

To my understanding it is the responsibility of the back-end to provide with the right message or error that the account has not been yet confirmed and prevent from returning an authentication-token.
For example if you look at the MVC5-SPA-Angular Demo that uses asp.net Web api you can add this code and in the ApplicationOAuthProvider class:
public override async Task GrantResourceOwnerCredentials(OAuthGrantResourceOwnerCredentialsContext context) {
var userManager = context.OwinContext.GetUserManager();
		User user = await userManager.FindAsync(context.UserName, context.Password);

		if (user == null) {
			context.SetError("invalid_grant", "The user name or password is incorrect.");
			return;
		}

        if (!userManager.IsEmailConfirmed(user.Id))
        {
            context.SetError("uncomfirmed_account", "The user's account has not been activated.");
            return;
        }

.... rest of the code ommited...
This way your back-end will not Login users that have not confirmed their email address.

Exactly right @Developer-Kostas, let me know if you need any more clarification on this.


BackupStatus and Sequoia

Hello,
Just wanted to check if the problem is on my side after installing Sequoia or there is a problem with the app itself.
When clicking on Backup Disk, Loading is shown briefly and then instead of revealing  the disk menu it just shows a tiny portion of drop menu.
Here are the screenshots of the behaviour under Mac OS 15:

same here...

Duplicate of issue #10. See this comment for a potential solution.


Missing parenthesis breaks deployment of windows VM's

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


verticalOffset prop

Adds verticalOffset prop to fix bug with react-navigation header.

Could you please also update the doc?

I'd like to accept this PR to resolve the integration issue #1 once the #3 has been included into this PR and all the comments got resolved.


Cannot launch Node.js applications: Can't find Node.js binary "node"

Issue Type: Bug
I'm developing a Node.js webserver application with the following launch configuration:
{
    // Use IntelliSense to learn about possible Node.js debug attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Program",
            "type": "node",
            "program": "${workspaceFolder}/dist/server.js",
            "request": "launch",
            "preLaunchTask": "npm: build"
        },
        {
            "type": "node",
            "request": "attach",
            "name": "Attach by Process ID",
            "processId": "${command:PickProcess}",
            "protocol": "inspector"
        }
    ]
}

This has been working perfectly until version 1.49 has been installed. Since then, I get the following error when launching the application:
Can't find Node.js binary "node": path does not exist. Make sure Node.js is installed and in your PATH, or set the "runtimeExecutable" in your launch.json
Output from echo $PATH:
/Users/ben/.rbenv/shims:/Users/ben/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/ben/Library/Android/sdk/platform-tools/

Out from which node:
/usr/local/bin/node

Of course I can add the argument runtimeExecutable to launch.json, but I think this should not be necessary.
VS Code version: Code 1.49.0 (e790b931385d72cf5669fcefc51cdf65990efa5d, 2020-09-10T17:39:53.251Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.02GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

angulardoc-vscode
Ang
6.1.3

vscode-eslint
dba
2.1.8

xml
Dot
2.5.1

EditorConfig
Edi
0.15.1

vscode-npm-script
eg2
0.3.13

prettier-vscode
esb
5.6.0

php-debug
fel
1.13.0

twig-language-2
mbl
0.9.2

debugger-for-chrome
msj
4.12.10

vscode-react-native
msj
0.17.0

vscode-jest
Ort
3.2.0

vscode-icons
vsc
10.2.0

markdown-all-in-one
yzh
3.3.0

Where do you have your PATH configured in that way? If you launch VS Code from the shell (code -- with no existing running VS Code instance) it will inherit those variables, but if you launch it from the desktop app it might not have the same variables
You can see the PATH that VS Code has by running Developer: Toggle Developer Tools and entering process.env.PATH in the console.

@connor4312 Output from Developer tools console:
process.env.PATH
"/Users/ben/.rbenv/shims:/Users/ben/bin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Apple/usr/bin:/Users/ben/Library/Android/sdk/platform-tools/"

Since /usr/local/bin is in path, everything should be working. It has been working for month until 1.49 was installed automatically.

I have the same problem after I upgraded to 1.49 !
Version: 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T17:39:53.251Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

I hit this error

If I changed runtimeExecutable I hit the following error

If I changed runtimeExecutable and runtimeArgs I hit the following error

That's coming from your shell.
In js-debug to find Node we run which node or where node in the current environment. https://github.com/microsoft/vscode-js-debug/blob/8581c0bcda559b775d8666fb5765641c4118498b/src/common/pathUtils.ts#L15 Your observation that running npm directly does not find Node validates that the environment is wrong in the ext host.
As a workaround, you may be able to get things to work by setting console: integratedTerminal in your launch config along with the runtime executable, so that your program is run in a real shell.
@sandy081 / @isidorn did something change in 1.49 that would interfere with the environment that the extension host receives?

Hi added console: integratedTerminal  but even more strange is that after I restarted vscode the problem goes away!
I didn't remember whether I restarted vscode yesterday but today that did fix the problem!

I have same problem after upgrade to 1.49.0.

Same problem after upgrading to 1.49.0. Problem went away after downgrading to 1.48.2.

Sorry, I have no idea. If it is extensionHost related pinging @alexdima

Can someone impacted please try:

open developer tools (Help > Toggle Developer Tools)
in the console, evaluate process.env['PATH']. Is this the same $PATH as in your terminal?
also evaluate process.env['DYLD_LIBRARY_PATH']

The only change that happened in this timeframe that I'm aware of is https://github.com/microsoft/vscode/commit/1b5fbcabd86f522da49c59fd80a90745f8a86f10 which removes DYLD_LIBRARY_PATH from the environment because it was causing some crashes.
ping @joaomoreno

I got an error message: We did not find "node" on your path, so can not enable auto-attach in your environment ... on Linux.
I am using the insider version and do an update everyday. I don't have this issue yesterday, so the problem must be caused by changes between the insider version "d1f267742169584db010716d92addf50d4cd8139" and "9e505675670d65138405321a60b0df4ddec28799".

I have checked both process.env['PATH'] and process.env['DYLD_LIBRARY_PATH'] with the two insider versions I mentioned, I got the same results.

And in my case, installing the nightly version of JavaScript Debugger can make that error message gone (https://github.com/microsoft/vscode/issues/106938).
Any explanation?

I'm not sure how the debugger version is related to the issue, I haven't touched this area since the stable release. Curious whether this works for everyone, like @Ben-WD and @qiulang.

Just updated and have what is likely a related problem. In my case I have the path to electron specified in launch.json:
           "type": "node",
           "request": "launch",
           "name": "Electron Player2",
           "runtimeExecutable": "~/workspace/electron_build/electron_x/dist/electron",
           "program": "${workspaceFolder}/app/main.js",
           "console":"integratedTerminal",
           "args": ["--playernum=player2"]
       },

Error message on launching debug states that the path does not exist:

This worked correctly before updating to 1.49.0. Hope this is useful.
Version: 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T13:20:50.359Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 4.15.0-112-generic

That's not related, but does it work if you replace the tilde ~ with the complete path? We don't untildify those at the moment, and I know 'some things' fail with them.

Thanks. Untildifying did make a difference. Now I am getting a permission denied error in the debug console and no popup dialog. I will try to track that down, but as you said this is not related to the issue above.

@connor4312 After I restart vscode I don't have the problem any more. I tried to reproduce it but I can't

Same problem here when platform is WSL but works fine when platform is Windows.
Version: 1.49.1 (user setup)
Commit: 58bb7b2331731bf72587010e943852e13e6fd3cf
Date: 2020-09-16T23:27:51.792Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.20170
Opened VS Code from WSL terminal ( code . ) and Launch Program
Received error message: Can't find Node.js binary "node": path does not exist. Make sure Node.js is installed and in your PATH, or set the "runtimeExecutable" in your launch.json
Output from: echo "$PATH" (in WSL: Ubuntu-20.04 terminal)
/home/greg/.asdf/shims:/home/greg/.asdf/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/c/Python38/Scripts/:/c/Python38/:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/c/WINDOWS/System32/OpenSSH/:/c/Program Files/PowerShell/7/:/c/Program Files/dotnet/:/c/Program Files/Git/cmd:/c/Program Files/Docker/Docker/resources/bin:/c/ProgramData/DockerDesktop/version-bin:/c/Program Files/nodejs/:/c/ProgramData/chocolatey/bin:/c/Users/Greg/AppData/Local/Microsoft/WindowsApps:/c/Users/Greg/AppData/Local/Programs/Microsoft VS Code Insiders/bin:/c/Users/Greg/AppData/Roaming/npm:/c/Users/Greg/AppData/Local/Programs/Microsoft VS Code/bin:/snap/bin:/home/greg/.local/bin:/usr/local/go/bin:/home/greg/go/bin:/home/greg/dart-sass:/home/greg/.fzf/bin:/home/greg/.local/bin:/usr/local/go/bin:/home/greg/go/bin:/home/greg/dart-sass
Output from: which node (in WSL: Ubuntu-20.04 terminal)
/home/greg/.asdf/shims/node
Output from: process.env['PATH'] (in VS Code dev console)
C:\Python38\Scripts;C:\Python38;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\PowerShell\7;C:\Program Files\dotnet;C:\Program Files\Git\cmd;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Users\Greg\AppData\Local\Microsoft\WindowsApps;C:\Users\Greg\AppData\Local\Programs\Microsoft VS Code Insiders\bin;C:\Users\Greg\AppData\Roaming\npm;C:\Users\Greg\AppData\Local\Programs\Microsoft VS Code\bin
No WSL paths!
Works with work-around by adding:
"linux": {
        "runtimeExecutable": "/home/greg/.asdf/shims/node"
}

to launch.json
launch.json:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "program": "${workspaceFolder}/app.js",
            "linux": {
                "runtimeExecutable": "/home/greg/.asdf/shims/node"
            }
        }
    ]
}

Also just to check, switched to Windows with Remote-WSL: Reopen Folder in Windows and Launch Program
No errors, works fine.

@greglnye do you add the .asdf shims to your path inside your .bashrc or similar file? If so, VS Code will only pick those up if you also launched the VS Code application from the shell--which is not possible in remote scenarios. You may be able to fix this by setting the shims path in your .profile instead. (my previous investigation into this: https://github.com/microsoft/vscode-js-debug/issues/717)

cc @aeschli who has looked into some environmental variable fixes for WSL.

Did same thing as @greglnye and @connor4312 said, set up runtimeExecutable to whatever path your node executable is.

@MatayoshiMariano  nvm is a known case where (in their default install) we won't always pick it up, because it's set in your .bashrc which isn't run by VS Code and won't be applied unless you launch code from the command line. See here https://github.com/microsoft/vscode-js-debug/issues/717#issuecomment-680190832

I had the same problem. Many of you restarted VScode so i tried it and it solved the problem. Thanks you guys.

Hi! I'm having the same problem. I had this problem in some projects and after updating to Visual Studio Code 1.49.3 it's happening to me in all the projects so I cannot debug any of my applications. Please help! I don't know what else to try, I have already restarted the software several times, restarted the Mac and installing another versión of node with nvm but the problem keeps appearing.
Hope you can help me,
best regards!

@PRossetti where is Node installed?

@MatayoshiMariano nvm is a known case where (in their default install) we won't always pick it up, because it's set in your .bashrc which isn't run by VS Code and won't be applied unless you launch code from the command line. See here microsoft/vscode-js-debug#717 (comment)

Before upgrading 1.49 everything was working fine

@MatayoshiMariano nvm is a known case where (in their default install) we won't always pick it up, because it's set in your .bashrc which isn't run by VS Code and won't be applied unless you launch code from the command line. See here microsoft/vscode-js-debug#717 (comment)

Before upgrading 1.49 everything was working fine

I'm using also nvm and never head a problem before updating to 1.49. Problem was gone for days and appeared suddenly again some days ago. Restarting VSCode fixed it.

Had the problem using vscode 1.49.3 and NVM on a project that had .vscode configuration without runtimeVersion set.
I set "runtimeVersion": "12.16.3" which is the active NMV version and it worked.

From what I've seen so far in this issue, the issue seems to be due to setting or updating paths in .*rc files. To summarize what I mentioned above--on most operating systems these variables are not automatically set for desktop applications. If you launch VS Code from the shell, though (without any other VS Code window open), they will be inherited. Since it's dependent on how its launched and how your system is set up, restarting VS Code might fix it.
Alternately, you can set the path to your runtimeExecutable or, if you're using a a supported version manager like nvm or nvs, set runtimeVersion so that js-debug will do the lookup for you.
There are an assortment of ways, again depending on your OS, to set environment variables in a way that they're inherited in applications by default. For example:

Ubuntu (for a shortcut) https://help.ubuntu.com/community/EnvironmentVariables#Launching_desktop_application_with_an_environment_variable
Ubuntu (user-wide or system-wide environment variables) https://help.ubuntu.com/community/EnvironmentVariables#Persistent_environment_variables
OSX via the /etc/launchd.conf file

I am not sure why you have closed this again.
There seems to be a difference in behavior between 1.48 and 1.49 that is causing all these issues, I am not sure if this change could at least be explained or documented in some way.
I've gotten the same issue myself on OSX.

@alexrecuenco how do you have node installed, where is which node?

@connor4312 Node is installed on /Users/macintoshhd/.nvm/versions/node/v13.14.0/bin/node (I am using nvm)

Keep in mind that it is working on 1.48 with no changes to my setup, so something has happened between 1.48 and 1.49 that changed how environment variables are inherited on the debug creation.
I must say, in my case, It is really inconvenient if this change is purposeful. We use vscode because with the correct setup for new developers "it just works". But if we need to change environment variables on /etc/launchd.conf it would be inconvenient.
Thanks for the effort looking into this.

cc @deepak1556 -- I'm unable to reproduce the issue described here, anything in Electron you know of?

I forgot to mention it, but my PATH environment in process.env['PATH'] in 1.49 is simply /bin:/sbin/..  just the basic default ones.
On the other hand, when I went back to 1.48  my process.env['PATH'] included my profile PATH environment

@joaomoreno @bpasero Did we change anything in the way we read shell env variables between 1.48 and 1.49 ?

@alexdima yes, for sandbox work: https://github.com/microsoft/vscode/commit/653e7e26df3be4cc5185982a8a4780b44523ef8e
But conceptually it should still work as before, though I decreased the timeout from 10s to 3s. To verify that is the issue, the devtools would show a warning message such as: Preload: Unable to resolve shell environment in a reasonable time
@alexrecuenco can you check that?

Same problem and restarting VSCode does not fix it.

Good afternoon,
I was unable to reproduce this error on version 1.49 again, it is true that my computer was particularly slow when this showed up (running some docker images).
@bpasero , after your comment, I tried adding a sleep command on my bash profile and that appears to make the problem show up inconsistently, but it does show a
preload.js:177 Preload: Unable to resolve shell environment in a reasonable time.
After running a >Developer: Reload Window command, sometimes the node executable is available
This is the copy-pasted devtools console log when it failed
preload.js:177 Preload: Unable to resolve shell environment in a reasonable time
(anonymous) @ /Applications/Visual Studio Code 1.49.app/Contents/Resources/app/out/vs/base/parts/sandbox/electron-browser/preload.js:5
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.r.
Old grammar file: file:///Applications/Visual%20Studio%20Code%201.49.app/Contents/Resources/app/extensions/r/syntaxes/r.tmLanguage.json.
New grammar file: file:///Users/macintoshhd/.vscode/extensions/ikuyadeu.r-1.4.6/syntax/r.json
register @ TMScopeRegistry.ts:43
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.yaml.
Old grammar file: file:///Applications/Visual%20Studio%20Code%201.49.app/Contents/Resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.
New grammar file: file:///Users/macintoshhd/.vscode/extensions/redhat.vscode-yaml-0.11.1/syntaxes/yaml.tmLanguage.json
register @ TMScopeRegistry.ts:43
console.ts:137 [Extension Host] Sync : Connected with user : 'alex-ubitec'
console.ts:137 [Extension Host] rejected promise not handled within 1 second: Git error {  "exitCode": 128,  "gitErrorCode": "IsInSubmodule",  "stdout": "",  "stderr": "fatal: Pathspec '/Users/macintoshhd/ubibot-workspace/ubibot-botkit/src' is in submodule 'ubibot-botkit'\n"}
t.log @ console.ts:70
log.ts:197   ERR Git error
3console.ts:137 [Extension Host] rejected promise not handled within 1 second: Git error {  "exitCode": 128,  "gitErrorCode": "IsInSubmodule",  "stdout": "",  "stderr": "fatal: Pathspec '/Users/macintoshhd/ubibot-workspace/ubibot-botkit/src' is in submodule 'ubibot-botkit'\n"}
t.log @ console.ts:70
console.ts:137 [Extension Host] [vscode-icons] v11.0.0 activated!
console.ts:137 [Extension Host] rejected promise not handled within 1 second: Git error {  "exitCode": 128,  "gitErrorCode": "IsInSubmodule",  "stdout": "",  "stderr": "fatal: Pathspec '/Users/macintoshhd/ubibot-workspace/ubibot-botkit/src' is in submodule 'ubibot-botkit'\n"}
t.log @ console.ts:70
log.ts:197   ERR Git error
3console.ts:137 [Extension Host] rejected promise not handled within 1 second: Git error {  "exitCode": 128,  "gitErrorCode": "IsInSubmodule",  "stdout": "",  "stderr": "fatal: Pathspec '/Users/macintoshhd/ubibot-workspace/ubibot-botkit/src' is in submodule 'ubibot-botkit'\n"}
t.log @ console.ts:70
console.ts:137 [Extension Host] No editors associated with document: /Users/macintoshhd/ubibot-workspace/ubibot-botkit/tsconfig.json
t.log @ console.ts:70
log.ts:197   ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.

Old grammar file: file:///Applications/Visual%20Studio%20Code%201.49.app/Contents/Resources/app/extensions/r/syntaxes/r.tmLanguage.json.

Old grammar file: file:///Applications/Visual%20Studio%20Code%201.49.app/Contents/Resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.

Just a comment to those finding this issue. My vscode instance was loaded by MacOS on a reboot using the "reopen all windows" option.  So I believe it was started before the path was set for node in my shell.  After closing and restarting vscode again manually it seemed to work just fine.  Not sure if this is the case for everyone, but maybe an idea to help debug.

restarting vscode didn't help (MacOS).
This is the output from VScode terminal node:
> process.env['PATH']
'/Users/assapir/.rbenv/shims:/Users/assapir/.nvm/versions/node/v8.17.0/bin:/Users/assapir/bin:/usr/local/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/bin:/usr/local/opt/mysql@5.6/bin:/Users/assapir/.go:/usr/local/opt/libpq/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/assapir/.rvm/bin'

and from regular terminal:
'/Users/assapir/.nvm/versions/node/v8.17.0/bin:/Users/assapir/.rbenv/shims:/Users/assapir/bin:/usr/local/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/bin:/usr/local/opt/mysql@5.6/bin:/Users/assapir/.go:/usr/local/opt/libpq/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/assapir/.rvm/bin'

@bpasero should I reassigned this to you? As far as I see there's no action I should take on the debugger side here.

I can look into it if someone can post steps how to reliably reproduce this. Otherwise this issue will close in 7 days automatically.

We have a substantial number of reports for this (~20 in this thread and some duplicates) that it's probably worth trying to diagnose even barring a reliable repro.

Yeah sure, I am happy to run through steps that are minimal without a lot of setup on my end if possible.

I was able to reproduce this getting

Any node's project opened in viscose
Add the line sleep 10 to your profile or bashrc
Quit vscode, then open it again on that project. Most times when you try to run the debugger it will show the message above
Run the reload windows command, you'll notice that now you can run the nodejs debugger.

@alexrecuenco that is expected, we only wait 3s before giving up on resolving the shell environment:
https://github.com/microsoft/vscode/blob/99b13b8fbfea262f03d4ec818c857003b463c7b2/src/vs/base/parts/sandbox/electron-browser/preload.js#L229-L234
This used to be 10s and now is 3s, so there was a change. But I really see no reason why resolving the shell environment would take any longer than <1s. Note that this blocks the window from opening, so it is really bad for performance.

@bpasero If you don't plan to change it back, would it be possible to write some documentation about the change? And, if possible, some setting to set it back the previous default.
Sometimes some bash extension can take a while to load, specially when the computer is strained (running a debugger, a docker container, and a db at the same time). And this seems to have caused many people here to get a very counterintuitive result that is very hard to debug without knowing this quirk of the system.
Thanks for looking into this.

fyi @joaomoreno on my change. I really think this is not the right solution all in all because for a user you may be surprised that opening the first window always takes up to 10s (now 3s) without fully understanding what is going on in the background.
I think a setting for this could work, but is hard to discover too. Alternatively we could simply proceed with opening the workbench and let the process environment come in async with possibly an event to emit once that happens so that parties that need to update can subscribe to?

But I really see no reason why resolving the shell environment would take any longer than <1s.

It happens a lot, and that's why it was set to 10.
Overall, the user env is really only needed when further spawning more processes, so the real fix here is to just have an IExecutionService which should get the user env whenever spawning processes, instead of having that dependency in the renderer. This is a big refactoring which will likely break many things, but it's the right thing to do. I've created this item to follow up:
Until then, I suggest to revert to the 10s timeout.

@jrieken made sure this doesn't block the window from opening, just the workbench from loading, back when he introduced
lazyEnv. @bpasero, this is now known as whenEnvResolved, since your latest refactorings.

I really do not see how this good. The workbench not loading in 10s is equally bad as the window not loading in 10s. All that matters is the time to blinking cursor in the editor and that is what we measure in our perf runs.
https://github.com/microsoft/vscode/issues/108804 sounds like a good idea and I think we should really tackle it soon not late.
Back to 3s vs 10s: what I don't like is this:

even 10s might not be enough it is just a number you or Jo picked which may fail or may not fail
if this happens (you wait 10s) there is no feedback as to why you waited for 10s
users will never learn that they have to look into their shell config to figure out why VSCode is slow starting up

If we had a setting this would at least enable this flow:

workbench starts slow
we can show a notification offering to inform user why it was slow
we can even notify that we could not resolve the shell environment in time
we can guide users towards tweaking the setting to either reduce the time or increase it as needed

Sorry for interjecting,
I understand your concern @bpasero, but in my opinion ---from a user perspective--- it'd be better not to modify the current behavior. Thus avoiding a couple threads of confused people from undocumented behavior changed.

I've had this same error happen recently as well, rendering VSCode useless for me until I figured out what was going on, and it took me a good bit of time to even figure out that this was the root cause, as I didn't get notified that the environment loading was timed out.
My eventual "resolution" was to disable extensions until my environment could be loaded in time. Given that I actually would like to use some of these extensions I disabled, I obviously can't consider this a real fix (this is something I will have to shelve VSCode for if it a must-have extension that is causing the problem, but I haven't gotten that far yet).
A setting to override the timeout would be great, I could change it and move on. The initial timeout is probably fine for a lot of people and the arguments for not having it set to 10s as a default are solid, but the lack of feedback about the environment not loading combined with the inability to override this behavior is a killer combination. I see that there is a feature request already put in to provide a real fix, but it would be amazing if, in the interim, we can get a setting + a prompt to update this setting if the environment load runs afoul of that timeout.

Developer: Reload Windows resolved my issue. Might not work for you just try. It worked for me.

I have this issue too with 1.50. never had with 1.49 ( or at least it never happened ). Solved with Developer: Reload windows

I've had the same problem with version 1.51.1 on macOS and solved (or worked around) it by re-starting VSCode.

Same problem Developer: Reload windows solved it

Since I think the current solution is just wrong (blocking the startup to resolve shell environment waiting for N seconds), I will close this as duplicate of https://github.com/microsoft/vscode/issues/108804 which is the correct solution: resolve the shell environment when it is needed.

In case anyone else comes across this, this problem started for me after installing the macOS Big Sur 11.1 update.

I'm not on big sur, still get problems launching with debugger. restarting vs code fixes it.
Version: 1.52.1
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:30:02.420Z (1 wk ago)
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0


Feedback from NativeScript Air ep. 5

Below is the summarized feedback the NativeScript Plugins team received during NativeScript Air ep.5. Feel free to contribute! We :green_heart: PRs!
🔴  Add more detailed instructions how to generate typings for 3rd party native libraries in the README of the seed
🌟  Provide demo-ng by default (or better - provide schematics about it, it's a good candidate. we aim for simple seed that serves plugin generic needs)
⬛  Add debug configuration in the seed
🚩  Amend the mocha tests in typescript instead of javascript
⚫  If possible, add some badges by default in the README i.e. travis, npm, downloads . See Firebase plugin for example
🔵  If possible, simplify the issue template
Thank you @EddyVerbruggen, @shiv19, @davecoffin for your feedback!

Just a TODO list here as I hope to contribute here:

[ ] Add more detailed instructions how to generate typings for 3rd party native libraries in the README of the seed
[ ] Provide demo-ng by default (or better - provide schematics about it, it's a good candidate. we aim for simple seed that serves plugin generic needs)
[ ] Add debug configuration in the seed
[ ] Amend the mocha tests in typescript instead of javascript
[ ] If possible, add some badges by default in the README i.e. travis, npm, downloads . See Firebase plugin for example
[ ] If possible, simplify the issue template

Another thing I now saw in the video is the suggestion to add a "create plugin" button in Sidekick- would be very helpful to have a template for UI plugins for example, perhaps maybe add that as an option in the postclone script


adapter enters crash loop when client's password is missing

log shows this when a tasmota client with missing password tries to access; adapter restarts afterwards
sonoff.0 | 2019-01-19 16:09:37.326 | info | terminating
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.emit (events.js:211:7)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at emitOne (events.js:116:13)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Object.onceWrapper (events.js:315:30)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.<anonymous> (/usr/local/iobroker/node_modules/mqtt-connection/connection.js:53:12)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.emit (events.js:211:7)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at emitOne (events.js:116:13)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.emitPacket (/usr/local/iobroker/node_modules/mqtt-connection/connection.js:10:8)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.emit (events.js:211:7)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at emitOne (events.js:116:13)
sonoff.0 | 2019-01-19 16:09:36.823 | error | at Connection.client.on.packet (/usr/local/iobroker/node_modules/iobroker.sonoff/lib/server.js:1554:34)
sonoff.0 | 2019-01-19 16:09:36.823 | error | TypeError: Cannot read property 'forEach' of undefined
sonoff.0 | 2019-01-19 16:09:36.823 | error | uncaught exception: Cannot read property 'forEach' of undefined

Please test 2.3.0


Issue: To sole the alignment issue in the blog section of ISKCON events

Issue and Steps to Reproduce:
The blog section of the  ISKCON events page overlaps with the date
Screenshots:

Expected:
To re-align the blog section

Please assign this issue to me, I will contribute to this issue under GSSoC'23. This issue will be solved by me with the help of CSS and HMTL


[Feature Request] Calculation or Formula field

Feature Request
What's the feature you think Backpack should have?
I've been tinkering with backpack for a few hours, and haven't found any official way to do it :
I'd like to have a field that display a value computed from two other fields.
The use case would be this one :
On a "item" CRUD, I have those fields :

purchase price  (type number)
margin (type number)
minimum sell price :  a calculated value : purchase price * margin
sell price (type number)
gross margin :  a calculated value sell price / purchase price * 100

Those two fields do have to be refresh every time the user change any of the two values.
Have you already implemented a prototype solution, for your own project?
Not yet. I can barely imagine something like this :

Need for a javascript helper function, that would return the value of any input field . ex : $.CRUD("purchase_price")
The calculated field would be defined as this :

                'name' => 'minimum_sell_price',
                'type' => 'computed',
                'label' => "min. sell price.",
                'depends_on' => ["purchase_price","margin"],
                'formula' => " $.CRUD('purchase_price') * $.CRUD('margin') ",
                // optionnal settings
                'suffix' => " €",

When such a field is used, it binds an event on each "depends_on" fields.
When the event triggers, it evaluates the formula and sets the field value.
The formula would not be limited to maths, it could be any JS processing the dev would like to hack ;)... Ajax call to retrieve an image, some other text, etc....

Do you see this as a core feature or an add-on?
Core, I see many use cases ;)

I see many use cases ;)

I agree with you on that one @LemarinelNet ! 😆 In fact, I see so many use cases that it's difficult to create something general enough to cover all use cases, I think. It's one of the reasons why we haven't created anything like this yet. But there are other problems with this that... don't feel quite right. I'll explain in more detail below.

Your use case, though, where you just add a formula to the field and it calculates that formula using JS, shouldn't be too difficult to achieve by creating a custom field type. You could start from the number field:
-
+
@include('crud::fields.inc.wrapper_start')
    {!! $field['label'] !!}
    @include('crud::fields.inc.translatable_icon')

    @if(isset($field['prefix']) || isset($field['suffix']))
 @endif
        @if(isset($field['prefix']))
{!! $field['prefix'] !!}
 @endif
        <input
        	type="number"
        	name="{{ $field['name'] }}"
+               data-init-function="bpFieldInitTotal"
+               data-formula="{{ $field['formula'] }}"
            value="{{ old(square_brackets_to_dots($field['name'])) ?? $field['value'] ?? $field['default'] ?? '' }}"
            @include('crud::fields.inc.attributes')
        	>
        @if(isset($field['suffix']))
{!! $field['suffix'] !!}
 @endif

    @if(isset($field['prefix']) || isset($field['suffix']))
 @endif

    {{-- HINT --}}
    @if (isset($field['hint']))

{!! $field['hint'] !!}

    @endif
@include('crud::fields.inc.wrapper_end')

and at the bottom of the file add the JS logic it needs, something like:

{{-- ########################################## --}}
{{-- Extra CSS and JS for this particular field --}}
{{-- If a field type is shown multiple times on a form, the CSS and JS will only be loaded once --}}
@if ($crud->fieldTypeNotLoaded($field))
    @php
        $crud->markFieldTypeAsLoaded($field);
    @endphp

    {{-- FIELD JS - will be loaded in the after_scripts section --}}
    @push('crud_fields_scripts')

    @endpush

@endif
{{-- End of Extra CSS and JS --}}
{{-- ########################################## --}}

In the example above, I've done some changes to your addField syntax:
                'name' => 'minimum_sell_price',
-                'type' => 'computed',
+                'type' => 'total',
                'label' => "min. sell price.",
-                'depends_on' => ["purchase_price","margin"],
-                'formula' => " $.CRUD('purchase_price') * $.CRUD('margin') ",
+                'formula' => " $('input[name=purchase_price]').val() * $('input[name=margin]').val()",
                // optional settings
                'suffix' => " €",

depends_on is not really needed I think. Also formula should probably be JS code, complete with selectors and everything, so it's as broad as possible.
There are some caveats to this approach though:

there can be no double-quotes inside the formula code (or they should be escaped or smth);
you're basically writing JS and jQuery inside the PHP controller; I expect a lot of people won't like this 😄
the JS formula is run using eval(), which has some big security implications; though for admin panel usage, where you expect your admin to be trustworthy, that shouldn't be such a big problem, I think;
you pretty much have to know the HTML output of the fields, to create the right selectors - yes most of the time it will be an input, but sometimes it'll be a textarea or something;

The field above should work pretty well, I think (haven't tested the code), but... I don't know if it should make it into the Backpack core, because of the problems above... I'll think about it, but in the meantime I'll move this issue to the add-ons repo, because I do think this would make for a very cool Backpack add-on; not everybody will need it, but those who will, will super-appreciate that it exists. Please let me know if you'll consider turning this into an add-on @LemarinelNet - I can help with feedback and stuff. If not, we might consider creating an official add-on of it, but only if it garners some more support from the community, if more people ask for it.
Hope my directions above help. Please post here your final code if you end up with something that works well enough for you. And let us know if you'll be creating the add-on.
Cheers!


11 add domain specific data types for ship situation etc using pydantic models

Added domain specific data types for Ship, Situation etc. using pydantic models.
Changed all code to use the new data types.
Added type hints.
Refactored tests to work with the new data types.
Added tests for reading files and writing files.

Hi @tomarnepedersen
I am currently comparing the output files from the tests between commit
Commit e8c2bba9 (open)
by Claas, 2023-11-23 14:44
and latest commit in this branch
Commit db91fb5e (open)
by Claas, 2023-11-25 01:24
I see there are some small differences in the output files.
Have hence reset this pull request to draft, until I investigated and we are sure that the changes in code do not change the output files (at least not content / number-wise).

ship_traffic_generator.generate_traffic_situations() : Corrected an error I introduced with commit 185418af on 2023-11-25 00:16
lat_lon_0 of the new traffic_situation needs to be set to lat_lon_0 from the encounter settings. It was, though, set to lat_lon_0 from the desired traffic situation (which is usually None). I introduced the error when changing the code to use the new pdantic data types.
Now corrected. Also added a related assertion to the tests to ensure the error does not get introduced again.

Hi @tomarnepedersen ,
this PR contains quite a lot of code changes as I introduced pydantic data classes to serve as domain specific types.
Please have a look whether you feel comfortable with it.
I also introduced type hints, resolving the 177 issues that pyright raised after activating the "reportMissingParameterType" rule in pyproject.toml.
There is one spot in the code where I suspect there might be an error. At least the docstring does not match the return values.
Would be good if you can throw a dedicated glimpse on that.
It is in module encounter.py, function calculate_relative_bearing().
If you search for @TODO in the code, you will easily find it.
Best greetings
Claas

Done a few changes. Performing the merge.


Looker Studio reports for Editorial

The Editorial team has not used GA4 before. There are certain Data Studio reports that have since been converted into Looker Studio that they are not aware of. The more self serving they are able to do, the less pressure will come to the Digital Experience team's way.

Created QR code tracking Looker Studio report:
https://lookerstudio.google.com/u/0/reporting/7fc7c37a-c60f-4c3b-9838-2fb28c6ef39c/page/p_b4fwbyb9fd/edit
@LaurenFBaily @davidpmccormick @gestchild 👀
Created QR code URL generator for use in creating codes that GA4 can read:
https://wellcomecloud.sharepoint.com/:x:/r/sites/wcdigitalexperience/_layouts/15/Doc.aspx?sourcedoc={1C4987D2-9B46-4631-B58D-0BB39B892921}&file=Book.xlsx&action=default&mobileredirect=true


Bitdb2.0: Accessing BCH balances and UTXOs

Is it possible to use this library for accessing BCH balances and UTXOs ?
I thought i read somewhere that SLPDB only syncs data starting at the block where SLP tokens were made. If I just change this number, will I be able to use this lib in websockets with BitDB and bitcoin queries?
I can't get any of unwriter's bitdb 2.0 queries to work but they work on his explorer but not slpdb's

SLPDB only stores SLPDB related UTXOs at the moment. Closing this for now.


Full stack functional tests for RawKernel

I've tried to keep up with unit tests with all the submissions, but can't really add full stack functional tests until we are routed up to the end. Since we have both the old code path and the new kernels we need to test both paths. We could also consider given that we own the Session / Kernel / Future layers now some functional tests that work on real ZMQ Kernels to exercise just those levels with some different scenarios.

What we would probably need here is a class that returns back sequences of jupyter messages to create a mock JMP connection in the case where we are not in a rolling build. This would probably be quite similar to the lower levels of the current mock jupyter session that we use in testing.

Some of this is done. To finish, change the default when running functional tests to be the raw kernel.

Note for validation. This doesn't encompass creating a new mock raw layer. Just moves over the nightly full python functional tests to use raw as the default.

Tests seem to be passing (although we still seem to have failures).


"View board" not displaying properly in Safari

In Safari (8.0.4), under assignment progress, the "view board" text on the accordion is not on the same line. The "view" is a bit lower than the "board". Fine in Chrome.

This has changed to "View Assignment" I think, on the student page:

(which is still a little out of alignment)
but has been replaced with "View Mark Sheet" for teachers which gets rid of that image and so fixes the alignment issue above.

Appears to be fixed.


Wrong warnings on font-family property in @font-face directive

Some fonts have a number in its name. But SCSS-Lint warns wrongly if these fonts are used in @font-face directive like this:
@font-face {
  font-family: "A 1a";
}

$ scss-lint t.scss
t.scss:2 [W] PropertyUnits: a units not allowed on `font-family`; must be one of (%, Hz, ch, cm, deg, dpcm, dpi, dppx, em, ex, grad, in, kHz, mm, ms, pc, pt, px, q, rad, rem, s, turn, vh, vmax, vmin, vw)

This happens only inside @font-face directive.

Thanks for the report! In my tests, this seems to be affecting all quoted values that are similar to what you included in your example, not just quoted values in @font-face directives. I'll push a PR for a fix in a minute.


Demonstrate multi-line comment reconstruction

Changes:

No change to one-line comment capture.
Change only indentation and line separator for multi-line comment.

The reconstruction might be a bit hard given the current comment capture from apache/zookeeper#2206. I am OK to both approches.

I checked the generated file, and the format of comments are kept as origin given the changes in zookeeper.jute.

Changes:

No change to one-line comment capture.
Change only indentation and line separator for multi-line comment.

The reconstruction might be a bit hard given the current comment capture from apache#2206. I am OK to both approches.

Oh, I understand now. This way, the blank lines between multiple comments can also be maintained. Thank you very much. I will modify it accordingly.


$ElementType returns undefined when used in objects

Bug reproduction:
https://flow.org/try/#0C4TwDgpgBA9gRgKygXigbwFBSgawiALigDsBXAWzggCcAaDAXwG4MMAKNXfKIgVigZF4CAJQt2vIgBIAogBsI5CMWAAVcBAA8w2lADkeEHoB8YjAGMYxAM7ASFImUo0UUXuLZPp8xcrUbtRF0DfBMzDFBIWDBgAEsrAEM5AHlEV0xsQwB+bwUlFXVIQIRgwxN6ZlYOLhAeNwEhGPjiJNTRJihWSxs7YQBJHoTicwghNNROQz4BFjZ+weHR6LjElMQxKAB6TagAERgIa2I9OwB3GGocIA
19: (objInstance: optionalObj); // Doesn't work
     ^ Cannot cast `objInstance` to `optionalObj` because number [1] is incompatible with undefined [2] in property `key`.
References:
2:   key: number,
          ^ [1]
13:   key?: $ElementType<obj, 'key'>,
            ^ [2]

My use case is that I define an object shape but need a parallel type where all keys are optional (to support partial updates through merge). I want to use $ElementType to reduce duplication of types definitions of the fields but it doesn't work.

This may actually not be an issue with $ElementType but rather with the comparison between object types: https://flow.org/try/#0C4TwDgpgBA9gRgKygXigbwFBSgawiALigDsBXAWzggCcAaDAXwG4MNRJYxgBLGYgQwA2AeUQp0WXPgD8RMpRr1mrABRopIKEQCsUBkXgIAlEygB6M1ADuMajgDOUfo4gAPSAGNgEACYY1GlpQuvqcPHxCosamFta2Dk4u7hBevv7qoTBcvAIiiCbmljZ2js5Qbp7efgGZ+TGWACIwEPbEAOTAcXaJ5cmpfhgefPadhgCSxCP8xB4QBmKo6niEwXosKuOTwNOzBtkRedGFUE0t7Z3FOFBwpJ0VKVWsQ1uwiBNTMxAATHvhuVHiJb4HRrfybD6zH6vI6xU6tDpdK5le79IA

Not a bug
See #5997 or #6009 for references

This probably can be closed.
/cc @vkurchatkin

Thanks for the links @apsavin I think I understand that the issue related to pointers of different types pointing to the same real object. I wonder if it would be possible to clarify the error message in these cases to indicate that as the source of the issue. The error message I got was especially confusing because of the direction of the sentence didn't seem to match the situation since [2] (as an optional type) is number | undefined so saying that number was not compatible with that didn't make sense.
Something as simple as reversing the order might help:
^ Cannot cast `objInstance` to `optionalObj` because undefined [2] is incompatible with number [1] in property `key`.

    References:

    2:   key: number,
              ^ [1]

    6:   key?: number,
               ^ [2]

This seems to be a similar issue as described in https://flow.org/en/docs/lang/depth-subtyping/, perhaps a reference there could also be a reference to that added to the error.


Reimplement Find Tabs (Dev 0.8.0)

The functionality formerly had by the find tabs were to assist in locating something specific but currently there is no search functionality easily found if at all existing.

Related to #362

Not a bug, known enhancement.


What is the gpu requirement for inference?

My bad, on a careful look into the paper I found out that they have the team has trained on 4 Nvidia 2080 GPUs. Brilliant work !


finvasia terminal requires scipy pip

Add scipy in finvasia requirements.txt ..

update the reame.md with  command pip install -r requirements.txt

Another good to have instruction in readme.md would be
python -m venv  .venv pip install -r requirements.txt
in Start.bat
call .venv\Scripts\Activate python Finvasia_Core_V3_002.py timeout 20


Support float64 for severity parsing

Is your feature request related to a problem? Please describe.
Parsing the severity using the pri field will not work, because json numbers are decoded as float64 values.
{
  "uid": 62,
  "time":<PHONE_NUMBER>,
  "pri": 6,
  "tag": "pve-ha-lrm",
  "pid": 33690,
  "node": "pve-1",
  "user": "root@pam",
  "msg": "end task UPID:pve-1:0000839B:000C5C3F:6067BB15:qmshutdown:100:root@pam: OK"
}

I can resolve this with a quick patch to operator/helper/severity.go, however, my solution is not production ready
func (m severityMap) find(value interface{}) (entry.Severity, string, error) {
	switch v := value.(type) {
	case int:
		strV := strconv.Itoa(v)
		if severity, ok := m[strV]; ok {
			return severity, strV, nil
		}
		return entry.Default, strV, nil
	case float64:
		strV := strconv.Itoa(int(v))
		if severity, ok := m[strV]; ok {
			return severity, strV, nil
		}
		return entry.Default, strV, nil
...

This works great for my example, will perform incorrectly when the value being parsed is actually a float64.
Describe the solution you'd like
The ability to handle float64 with an optional precision parameter would be nice.
For example, if the pri value is 6.5, my solution would return 6, which may not be acceptable.
Describe alternatives you've considered
An operator for converting a value's type could be used instead. This would allow the user to convert from float64 to a string or int. Some control over the precision would still be required. I think this operator would be useful in general, but very clunky for solving this specific problem.

I haven't seen any use cases where a numeric severity is actually meant to be a float value, so my opinion is that we can cast it to int as you've shown.
There's been discussion about a type conversion operator before, and I think we probably do need this at some point. Someone needs to spec out what it would be capable of, how it is configured, how it handles various error scenarios, etc.


Fixes slack link in documentation navbar

Description
The slack link in the documentation navbar was broken. This PR fixes it.

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

Hey @shlokkhemani Thanks for this but for now we are not showing slack on docs. So closing this PR.


Non-deterministic classloader chosen when running tests

problem
This issue in specs2 shows a project with 2 modules, m1 and m2 where running tests for m1 can see the classpath for m2 being used. This is non-deterministic.
steps
This can be reproduced with this project.
expectation
Each module should only be able to access its own classpath.
notes
sbt version: 0.13.15

huh! I wonder if this is related to #3515, which is about classpath resources in sbt 1..

Using sbt 1.3.0 project2/test prints out the following error message:
sbt:specs2-concurrent-boom-boom> project2/test
[info] Compiling 1 Scala source to /private/tmp/specs2-concurrent-boom-boom/project2/target/scala-2.11/classes ...
[info] Compiling 1 Scala source to /private/tmp/specs2-concurrent-boom-boom/project2/target/scala-2.11/test-classes ...
sbt.internal.LayeredClassLoader@2bad36e2
sbt.internal.LayeredClassLoader@2bd73304
[warn] Thread[ForkJoinPool-1-worker-13,5,main] loading com.elemica.boom.ThisIsBoom2 after test or run has completed. This is a likely resource leak.
[info] TestTheBoom
[info] DoTheBoom should
[error]   ! create a ThisIsBoom2
[error]    java.lang.ClassNotFoundException: com.elemica.boom.ThisIsBoom2 (DoTheBoom2.scala:9)
[error] com.elemica.boom.DoTheBoom2.boomItOut(DoTheBoom2.scala:9)
[error] com.elemica.boom.TestTheBoom$$anonfun$1$$anonfun$apply$1$$anonfun$apply$2.apply(TestTheBoom.scala:9)
[error] com.elemica.boom.TestTheBoom$$anonfun$1$$anonfun$apply$1.apply(TestTheBoom.scala:9)
[error] com.elemica.boom.TestTheBoom$$anonfun$1$$anonfun$apply$1.apply(TestTheBoom.scala:9)
[info] Total for specification TestTheBoom
[info] Finished in 179 ms
[info] 1 example, 0 failure, 1 error
[error] Test suite com.elemica.boom.TestTheBoom failed with java.lang.ClassNotFoundException: com.elemica.boom.ThisIsBoom2.
[error] This may be due to the ClassLoaderLayeringStrategy (ScalaLibrary) used by your task.
[error] To improve performance and reduce memory, sbt attempts to cache the class loaders used to load the project dependencies.
[error] The project class files are loaded in a separate class loader that is created for each test run.
[error] The test class loader accesses the project dependency classes using the cached project dependency classloader.
[error] With this approach, class loading may fail under the following conditions:
[error]
[error]  * Dependencies use reflection to access classes in your project's classpath.
[error]    Java serialization/deserialization may cause this.
[error]  * An open package is accessed across layers. If the project's classes access or extend
[error]    jvm package private classes defined in a project dependency, it may cause an IllegalAccessError
[error]    because the jvm enforces package private at the classloader level.
[error]
[error] These issues, along with others that were not enumerated above, may be resolved by changing the class loader layering strategy.
[error] The Flat and ScalaLibrary strategies bundle the full project classpath in the same class loader.
[error] To use one of these strategies, set the  ClassLoaderLayeringStrategy key
[error] in your configuration, for example:
[error]
[error] set project2 / Test / classLoaderLayeringStrategy := ClassLoaderLayeringStrategy.ScalaLibrary
[error] set project2 / Test / classLoaderLayeringStrategy := ClassLoaderLayeringStrategy.Flat
[error]
[error] See ClassLoaderLayeringStrategy.scala for the full list of options.
[error] Error: Total 1, Failed 0, Errors 1, Passed 0
[error] Error during tests:
[error]   com.elemica.boom.TestTheBoom
[error] (project2 / Test / test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 2 s, completed Sep 24, 2019 5:14:57 PM

Adding Test / classLoaderLayeringStrategy := ClassLoaderLayeringStrategy.Flat to both subprojects fixes the test.
In general, sbt's test task emulates the JVM using function call into a ClassLoader, so doing anything ClassLoader related is not going to be safe.
See:

https://www.scala-sbt.org/1.x/docs/In-Process-Classloaders.html
https://www.scala-sbt.org/1.x/docs/Forking.html

Thanks for the update Eugene, there are still many things related to classloaders which I don't know.


Failed to execute GIT always coming in Visual Studio code on top

VSCode Version: Code 1.4.0 (6276dcb0ae497766056b4c09ea75be1d76a8b679, 2016-08-04T16:45:31.680Z)
OS Version: Windows_NT ia32 10.0.17134

Steps to Reproduce:

/needsMoreInfo


3.0 changes to fork()

In CHANGELOG.md I've spotted a change in 3.0, which states:

fork - It is no longer possible to call fork after a call to consume. Attempting to do so will result in an error.

This change eliminates a certain stream structure which can be depicted as:

This structure can be used to take data and "preprocess" it, then split the data based on certain conditions to process individually.
What can be done in version 3.0 to create the same (or similar) stream structure?

That still works. What no longer works is this corner case
const stream = head.consume(consumer1).consume(consumer2);
stream.take(1); // Stream is consumed.
stream.fork();  // This will fail.

The following still works
stream.fork().filter(filter1);
stream.fork().filter(filter2);

That entry means you can't call fork after a consume on the same stream. Each call to consume creates a new stream, even though it might not look like it.

I've updated the changelog to add a code example that hopefully illustrates the intent of that entry better.

Now I see the difference. Thanks!


and etc. -> etc.

"etc." is an abbreviation of "et cetera", which is Latin for "and so forth", and "et" specifically being the Latin for "and". "and etc." is therefore quite redundant, so I've removed the "and" in all such cases I could find.

Thanks a lot for the fix @glennsl !


Add JDBC source

Within this issue, implement query push down (e.g. execute scalaql.Query as SQL query as much as possible)

Closed in favour of #37


Types\SellerProfilesType -- ProfileID Int larger than 32bit php_int_max

Change integer to string in the respective profile types

nope, you have to switch to 64bit

Just changed int to string works fine. Here for anyone else that runs into it.

that´s a bad hack. next time this SDK gets an update, you may not forget to redo all your hacks. use 64bit, we no longer live in the stone age.

what does bad hack mean?

it´s the opposite of something good. i guess you can close this issue because there is nothing in here that helps somebody.

If someone is running this on a 32 bit system and ran into this problem, would this not help them?

no. this person should switch to 64bit - that´s the only solution that makes sense when working with this SDK and ebay at all.
btw. this issue is already adressed here and more detailed here.

Whats the point of the integer data type requirement? Since xml doesn't send data types, ebay would kick back an error anyway, if the input was wrong. Im no php api expert, so your knowledge on the subject would be appreciative.

Pardon, my intention is to help, not to discuss why it makes sense to use a 32bit system these days, nothing more this is about. I'm out.

I guess you misunderstood the question?

Duplicate of #101 - just to keep track of things. :)


Separate config for GPU_LAYERS for text, code et.al.

Closed using https://github.com/kodlokal/kodlokal-gateway/pull/19


Add step for clarity on updating Secret URI

There should be a step right before the code example to change the following line:
WebRequest kvRequest = WebRequest.Create("https://{YourKeyVault}.vault.azure.net/secrets/{YourSecret}?api-version=2016-10-01");
Great article otherwise!!!

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

ID: ffad04ad-5d9e-56de-c688-f0c6dd9de549
Version Independent ID: 8f370b3c-3c2f-5493-1041-be919bb73e58
Content: Tutorial - How to use Azure Key Vault with Azure Windows Virtual Machine in .NET - Azure Key Vault
Content Source: articles/key-vault/tutorial-net-windows-virtual-machine.md
Service: key-vault
GitHub Login: @prashanthyv
Microsoft Alias: pryerram

@RonStack Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@prashanthyv Hi, could you please check this feedback? Thank you.

This looks great, thanks!

GitHub user prashanthyv has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

I made a pull request to add this to the document. https://github.com/MicrosoftDocs/azure-docs-pr/pull/88137


Example for HTTP::FormData::Builder is passing the wrong variable

In the api docs for HTTP::FormData::Builder there's an example not actually passing the correct memory buffer to the file method.
builder.file("upload", io, FileMetadata.new(filename: "test.txt"))
Should be
builder.file("upload", file, FileMetadata.new(filename: "test.txt"))

Duplicate of #4898.


Version: 0.30.0 (1st December 2021) - Issues with adding an Instance compute to VCN

Hi there
I am not sure if this would be considered a bug. But, the deployed OKIT version doesn´t allow me to add a Computer instance into the VCN. Also, the information from my OCI Infrastructure is not retrieving as well.
Would you please put instructions on how to get OCI Infrastructure or multiple regions infrastructure ?
I followed each step by step instruction.

@jaalsuca Instances can only be dropped on a subnet or compartment. Existing infrastructure is retrieved using the query menu item

Hi @toxophilist
Could you please be a bit specific? I know and it is quite logical to retrieve current infrastructure from the query menu.
Now, I can see a new version but the documentation does not specify how to update it.
Regards;
Jairo Suarez

How to be specific when someone requires help.
If you already have OKIT installed and you want to update it. Please follow these steps.
I am using Oracle Linux as OS
PATH=$PATH:$HOME/.local/bin:$HOME/bin
OKIT_DIR=/okit
export OKIT_DIR
export PATH
[opc@okit-server02 ~]$ sudo systemctl stop gunicorn.service
[opc@okit-server02 ~]$ cd /okit/
[opc@okit-server02 okit]$ ls
[opc@okit-server02 okit]$ git pull
error: cannot open .git/FETCH_HEAD: Permission denied
[opc@okit-server02 okit]$ sudo git pull
remote: Enumerating objects: 21781, done.
remote: Counting objects: 100% (21781/21781), done.
remote: Compressing objects: 100% (5957/5957), done.
remote: Total 21385 (delta 15170), reused 20169 (delta 14232), pack-reused 0
Receiving objects: 100% (21385/21385), 7.48 MiB | 12.55 MiB/s, done.
Resolving deltas: 100% (15170/15170), completed with 207 local objects.
From https://github.com/oracle/oci-designer-toolkit
84d7149..a55ccfa  master     -> origin/master

[new tag]         v0.30.1    -> v0.30.1
From https://github.com/oracle/oci-designer-toolkit
[new tag]         v0.10.0    -> v0.10.0
[new tag]         v0.10.1    -> v0.10.1
[new tag]         v0.10.2    -> v0.10.2
.........
...............
........................
visualiser/query/ociRegionQuery.py                    |   8 ++-
visualiser/templates/terraform/copyright.jinja2       |   4 ++
visualiser/templates/terraform/provider.jinja2        |   4 --
visualiser/templates/terraform/region_data.jinja2     |  13 -----
32 files changed, 515 insertions(+), 296 deletions(-)
create mode 100644 okitweb/okitExport.py
create mode 100644 okitweb/static/okit/view/terraform/css/view.css
create mode 100644 okitweb/static/okit/view/terraform/js/view.js
create mode 100644 visualiser/templates/terraform/copyright.jinja2

[opc@okit-server02 oci]$ sudo systemctl start gunicorn.service

After successful update of OKIT, I am still confused in regards of add into the deployment compartment by default, a new VCN, into the new VCN should include a Compute Instance or Analytics instance but I am now allowed to do it., why?

After successful update of OKIT. I am still fighting to retrieve information from my OCI Infrastructure.

If you please can offer specific information where I must modify the config file, I much really appreciate it.
3 things basic steps I have done.
First, follow the documentation here https://github.com/oracle/oci-designer-toolkit/blob/master/documentation/Installation.md#config-file
Second, copy the config file here /okit/containers/oci
Third, copy and modify the file here /okit/config/config with different tittle, I put ADMIN.
The result is the same as per showed above.
Jairo

@jaalsuca This is usually an issue with the config file key file entry
Can you log into the container
docker exec -it okit bash
cat ~/.oci/config
It should show 'key_file=~/.oci/oci_api_key.pem' and the file has to be in the '/root/.oci' directory.
The entry should be something similar to that above with the file in ~/.oci

Closed due to no recent update


Jetty 9.4.x module

well finally the code will be hosted in jetty source repo.

Merged in Jetty 9.4.7.v20170914 - Issue should be closed
see https://github.com/eclipse/jetty.project/issues/1571


Point out composition-api registration for vue 2

Ran into this issue today and i couldn't figure out why until i found this post on the discord by chance, figured i should add it.

Added this. Thanks.


Fix dd

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 3 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 85.045%

Files with Coverage Reduction
New Missed Lines
%

qiskit_research/utils/pulse_scaling.py
3
89.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1126

Relevant Lines:
1324

💛  - Coveralls


feat: add all content

@tbpg Would you mind taking a look at this too when you have a chance :)

@tbpg Is this Go expert approved?

@codyoss is this ready to merge?

@averikitsch Yes, I believe so!


xlsx multiple worksheet

xlsx reader failed to read data from multiple sheets. It read data from only one sheet rather than either failing or reading all.

I also tested and confirmed that this is not an issue with the current version of textract on this multipage excel spreadsheet:
vagrant@dev:/vagrant$ textract multipage.xlsx

a b c d
1.0 2.0 3.0 4.0

I'm not sure if this happened to get fixed somewhere along the way or if we have a dependency version problem, but if you continue to have this issue @tomron, please feel free to reopen this issue and I'll be happy to look into it for you. In the meantime, I'm going to close this out.


SIL: let SingleValueInstruction only inherit from a single SILNode (2nd try)

After fixing a bug, this reinstates https://github.com/apple/swift/pull/35554 (after reverted by https://github.com/apple/swift/pull/35600).
Letting SingleValueInstruction only inherit from a single SILNode removes the ambiguity when casting from a SingleValueInstruction to SILNode, which makes the code simpler. E.g. the "isRepresentativeSILNode" logic is not needed anymore.
Also, it reduces the size of the most used instruction class - SingleValueInstruction - by one word.
Conceptually, SILInstruction is still a SILNode. But implementation-wise SILNode is not a base class of SILInstruction anymore.
Only the two sub-classes of SILInstruction - SingleValueInstruction and NonSingleValueInstruction - inherit from SILNode. SingleValueInstruction's SILNode is embedded into a ValueBase and its relative offset in the class is the same as in NonSingleValueInstruction (see SILNodeOffsetChecker).
This makes it possible to cast from a SILInstruction to a SILNode without knowing which SILInstruction sub-class it is.
Casting to SILNode cannot be done implicitly, but only with an LLVM cast or with SILInstruction::asSILNode(). But this is a rare case anyway.
Only the last commit of this PR does the actual SILNode change. All previous commits contain small cleanups, which are required for the change, but are good for their own.

@swift-ci test

@swift-ci test


Ensure JavaTestRunner fileURL on Windows uses forward slashes

Ensure JavaTestRunner on Windows uses a fileURL that is valid for java.net.URI, which the framework validates with.
Signed-off-by: Andrew Leonard<EMAIL_ADDRESS>

Test grinder for jck-runtime-api-java_net_0 passes.

@Mesbah-Alam This may possibly fix for openj9 too? https://github.com/adoptium/aqa-tests/blob/1061a877efc5fb26d08a426438dccba77ba8f8c4/jck/runtime.api/playlist.xml#L495

@andrew-m-leonard , I had missed your comment in https://github.com/adoptium/aqa-tests/pull/4172#issuecomment-1331262776 : Actually, we had disabled jck-runtime-api-java_net due to various intermittent failures (details in the related backlog issues listed in the excludes) observed over a period of time. It is currently run by the CR team manually on the excluded platforms.


Mandatory service_id and plan_id for last_operation requests in 1.0.3

Hi,
it seems that 1.0.3 enforces service_id and plan_id as mandatory request parameters for last_operation requests. In the OpenServiceBroker API Spec 2.13 they are optional, though. Is that done on purpose? Am I missing something?
Best,
Thomas

Hi @thomasjanke, Thanks for reaching out!
Looks like 1.0.3.RELEASE was based on the OpenServiceBroker API Spec version 2.11 where last_operation had those parameters as mandatory: https://github.com/openservicebrokerapi/servicebroker/blob/v2.11/spec.md#polling-last-operation
https://github.com/spring-cloud/spring-cloud-open-service-broker/blob/1.0.3.RELEASE/src/main/java/org/springframework/cloud/servicebroker/controller/ServiceInstanceController.java#L101-L104
On the latest 2.0.1.RELEASE version, the issue was addressed and it should be compatible with the latest Spec version:
https://github.com/spring-cloud/spring-cloud-open-service-broker/blob/2.0.1.RELEASE/spring-cloud-open-service-broker-core/src/main/java/org/springframework/cloud/servicebroker/controller/ServiceInstanceController.java#L149-L150
Is there anything stopping you from upgrading?
Thanks,
Alberto

Good catch! You are completely right @thomasjanke. Those parameters were optional, just the way it was described changed and it was missed.
I understand that upgrading to boot 2.x is a major change, so we will release a new 1.0.x version with this fixed.
As a note, Spring Boot 1.x EOL is in less than a year now: https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
Thanks again!
Alberto

so we will release a new 1.0.x version with this fixed.
Great. Thanks a lot!

This was resolved in #118