Update error-when-posting-analytical-accounting-transactions-or-save-…

…master-record.md

Docs Build status updates of commit 5132846:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/dynamics/gp/error-when-posting-analytical-accounting-transactions-or-save-master-record.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hi @theley502, thank you for the contribution! This PR is merged. For future changes, I think you can follow https://review.docs.microsoft.com/en-us/help/contribute/contribute-authors-in-public-repo?branch=main to make changes to the private repo. Thanks!

Hi @theley502, the article is live now: https://docs.microsoft.com/en-us/troubleshoot/dynamics/gp/error-when-posting-analytical-accounting-transactions-or-save-master-record


coregistration error

Hi,
When I am running
coregistration(inst=fname, subject='sub29', subjects_dir=freesurf_subject_path)
I have this error:
The 'subject' trait of a MRISubjectSource instance must be '', but a value of 'sub29' <type 'str'> was specified.
Do you have an idea what is wrong? (I am using 0.14dev version)
Thank you!
Romain

Looks like "sub29" is not a valid subject in your subjects_dir, or not recognized as such

Yes, the path was not good... Thank you!


Add prop in vue.config.js to change vue src directory

What problem does this feature solve?
Having the Vue src files and directories in the /src directory works for simple projects, but for more complex projects it doesn't work as well. If you're including the Vuejs project in with another project with other programming languages that follow a different or same src dir causes problems. This feature will separate the vue code from the other project code (js/PHP/C#/Go/python/etc.)
Currently if you want to modify the vue src directory you need to modify vue.config.js:

change the alias @ path.

configureWebpack: {
        resolve: {
            alias: {
            '@': path.join(__dirname, vueSrc)
            }
        }
    }

Use the pages option to change their path:

pages: {
        app_main: {
            entry: path.join(vueSrc, 'main.ts'),
            template: path.join(vueSrc, 'public/index.html'),
            filename: 'index.html',
            title: 'Index'
        }
}

There might be other locations or properties that need to be updated with the change in src directory, but these 2 are the ones I've noticed so far.
There is the public directory that should also be considered. I assume it would also be moved into the specified Vue src directory or made into a separate web.config.js option.
If this is already doable without all the customization mentioned above, let me know.
What does the proposed API look like?

Add an option to vue.config.js called src or vueSrc or vueDir or srcDir or vueSrcDir or whatever is deemed appropriate.
Either assume the public folder is also in the new vueSrc path or create a separate publicSrc (or publicDir) option in vue.config.js.

The value would be starting the current directory so you don't need to include the whole path.
Example: if you wanted to change the src vue directory and files from src to webclient/vue.

Note: The developer would manually create the new webclient directory in the project root. Then rename the src directory to vue and move it into the webclient folder. The public directory would also be moved into webclient/vue.

vue.config.js
module.exports = {
    vueSrcDir: 'webclient/vue', // Default: /src
    publicDir: 'webclient/vue' // Default: /public
}

This is NOT something that would make cli-service / webpack move the files automatically.

The vue-cli would then change the vue src path where used by the cli-service.
The 3 places I've seen so far are:

resolve: { alias: { '@': pathToVueSrc } }
pages / entry / template
The public directory would also be located in the pathToVueSrc or another vue.config.js option.

Thanks!
Keep up the good work!

I hesitant to add options for changing such basic and sensible defaults.
We provide a way to adjust webpack, it should be used.
I would rather like The community to come up with a collection recipes to do such adjustments than add option after potion to vue-cli

@LinusBorg  These options to change defaults will probably lead to greater adoption, as it will make integrating Vue much easier in existing and complex projects. Right now the vue-cli defaults (from what I can tell) are tailored for SPA. Most of the web doesn't run on SPA.

I've updated the above proposed option names to srcDir and publicDir to conform to the syntax similar to outputDir option.

See https://github.com/vuejs/vue-cli/issues/1134#issuecomment-384856754
This is by design.
Anyway, it is still reachable, though not that convenient.
We don't want users to change the folder structure unless absolutely necessary. Providing a first class option will inevitably lead to abuse IMHO.

But @sodatea why do you believe it will lead to abuse? Nobody has outlined the actual cons for this change other than just "we prefer it this way and don't want users to change it". You can configure many directory preferences such as the dist name and location, the devServer url (which literally changes how you can access the app in development).
Not changing the source directory seems like an unjustifiable preference that can't possibly lead to abuse any more than the current options provide.
In the current system, if you want to change the directory (and then do so in the vue.config.js), readers will have a much harder time understanding all of the required changes and opaque configuration and purpose, than if it was just:
sourceDir: "client"

Which is as immediately clear as options like devServer: port, assetsDir and outputDir.

@sam3d I think people should change the directory only after having fully understood what he's doing.

@sodetea that reasoning doesn’t make sense though. To do something as trivial as choosing where my code comes from, why should I have to trawl through the Vue CLI codebase to figure out how to it nondestructively?

The CLI is designed for SPAs or projects that separates front-end from the backend (only communicating via API calls). You can place the Vue CLI project directory anywhere you want - but it should be separate from other code in your entire project. It's not recommended to mix server-side code inside a Vue CLI project root.

Given (1), there's little practical benefits in changing the src or public directory names, other than pure naming preference. Note that this is different form outputDir and devServer, which both serve practical purposes: outputDir affects how the project integrates with deployment; devServer is necessary for users with specific network environments.

We want to encourage a somewhat consistent source code structure across all Vue CLI projects so that users have an easier time jumping into a new project.

There is a maintenance cost in every feature added.


Improvement: check image exists first

What has been done
With this PR, image existence checking has been added in recognition.py. The reason for this change is to solve the situtation that occurs when attempting to find similar faces using the find function. Previously, the function first collected embeddings from the database before searching for faces in the target image. If the path to the target image was incorrect or the image did not exist, the exception would only be raised after the database scan, which could be time-consuming.
How to test
make lint && make test

LGTM


Fix unmarshal error in endpoint interface

Instead of passing the pointer to &ep.iface the current
code is passing the value. So the source variable is not
getting updated properly.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

Thanks @mrjana . LGTM

fixes #527

LGTM


Fix the CEF scroll bug on Windows

This fix is a little hacky and it will have weird effects for those using thirdparty software like X-Mouse or KatMouse (as suggested in #10214), but I confirmed it fixes #10214 and it isn't too wonky.
Obviously, a CEF-side fix would be way better, but apparently the issue doesn't have much priority...

@MarcelGerber Is this bringing back the old behavior. I recall @JeffryBooher mentioning about no of lines scrolled to be 11 against 7. Can you share this data?. And also you mentioned some unwanted behavior might be introduced when using third party software. What are those? If the effects are weird and cause problems in using other applications, can we put this under a preference? Does that make sense.

A more detailed description might help:
In the CEF version we use, there are 2 mousewheel events fired per wheel tick, at least on Windows, while Chrome/Chromium and every other browser only trigger one (which is, obviously, the expected behaviour).
A normal Chrome scroll (triggered by a mouse wheel, not others like touchpad) scrolls 200px, so this bug causes a scroll to span 400px.
The two events both look like "real" events with a different timestamp and both with proper coordinates etc., so it's not easy to decide whether a scroll event is "real" or caused by the bug. The only things they have in common is the scroll distance (deltaX, deltaY) and usually the mouse position (clientX, clientY). The timestamps are not too far apart, but there can well be ~100ms between them (because a render happens in between).
This bug does not only affect the editor (= CodeMirror), but the whole Brackets UI, including dialogs, the sidebar, extension manager, ...
So, I guess @JeffryBooher didn't measure exact values as the scroll distance should have doubled in Release 1.1, compared to Release 1.0. And apparently, the issue is much worse for other users, including me where it currently scrolls 24 lines.
AFAICT, the thirdparty software mentioned above was installed to fix this very problem. I don't know of any other software that hooks the mouse, so with users that didn't explicitly install one of the aforementioned tools, there shouldn't be any issue either.
This fix doesn't cause problems with other software, but for users that use one of those tools, only every second wheel event (= wheel tick) will get through to Brackets (which is bad, I know).
If anyone can think of a better approach, please go ahead.
One could be to either include the patch posted on the CEF issue in our CEF or enable the "--off-screen-rendering-enabled" flag in CEF, as that apparently fixes the issue.
cc @JeffryBooher

Just to be clear: Everyone I talked to that experienced this issue had a different result; for some it was 24 lines of code scrolling but for me the delta wasn't as severe but it was definitely noticeable.
The delta could have been differences between OS versions, System Settings, Hardware and even system timing.
Enabling Off-Screen rendering is definitely worth a shot but it may introduce other issues that may complicate the issue.  It will definitely require quite a bit of testing.
I think if everyone upvotes the CEF issue then Marshall will fix the problem for everyone.

Reading through https://code.google.com/p/chromiumembedded/wiki/GeneralUsage#Off-Screen_Rendering, I no longer think enabling offscreen rendering is a good idea ("Off-screen rendering does not currently support accelerated compositing so performance may suffer as compared to a windowed browser").
I think the differences in impact are not caused by OS differences (it's a Win-only bug, and I don't see why that should make a difference in Chrome's lazy scroll implementation), but rather on differing font sizes & font (would probably be better to give distance in px; for me, it's 400px; one way to get this is to scroll all the way up, scroll one tick down and then issue $(".CodeMirror-scroll").scrollTop()) and probably also on mouse drivers (drivers/software that implement smooth scrolling, for example).
Also, when line wrapping is enabled, you can't just simply calculate the difference of line numbers, you have to instead take wrapped lines into account, too.
But as I just saw the CEF issue is the fifth-most starred CEF issue, I hope this issue will be fixed soon.

IMO we should wait and see if this gets fixed in the next release of CEF.

Where do we find the CEF?

@cbaldwinweb It's on Google Code.
You can find builds on http://cefbuilds.com/ (we currently use Branch 2171 on Windows/Mac).
Also, it'd be great if you could star the corresponding CEF issue.

@MarcelGerber I tested this out on my Win 8 machine and it works great.  I'm in favor of merging this for 1.3 since many people have described it as a blocker to upgrading past 1.0, and it looks like it will be a while before we could get a CEF fix (the CEF bug seems stalled now, and upgrading CEFs takes a lot of time).  Whenever we do pick up a CEF with a fix this will be easy to back out, so I like this as a stopgap workaround until then.
@nethip any concerns about that plan?

I've tested this for some time a while ago and it all seemed to work well, but at some point I wondered why it it suppressed the first and sometimes the second event, and even though that didn't cause any issue, I wonder if that had to do with a bigger issue (like, CEF not always firing doubled scroll events).
Also, I assume you've read the wall(s) of text above, correct? There's some risk of CEF not firing doubled scroll events in all scenarios (possibly depending on mouse drivers, software like KatMouse, Compatibility mode, ...). Obviously, we haven't heard of the one's where scrolling just works (so we don't know how many they are) and if, with this fix merged, only every other wheel tick takes effect, the UX would greatly decrease for them.
I don't quite get though why Marshall, the CEF maintainer, almost completely ignores this issue, which is currently the second-most upvoted issue on the board. Yeah, it's propably some work to figure out what's wrong, but there's plenty of interest in fixing this bug, too (this exact same bug has also caught me in the Windows Spotify client, and it's annoying there too).

@peterflynn Would you be ok with adding this as a preference (maybe also an undocumented, _-prefixed one, like _winScrollFix) defaulting to true, just in case a scenario like the above should happen?

I've just added another commit so this is now preference-based (it even supports on-the-fly changes), so it's now ready to land from my side.
Please let me know if/when you'd like to merge so I can squash commits. I may though not be able to do that tomorrow, but no later than Friday.

@MarcelGerber It seems unnecessary... I'm not aware of any Windows machines where the bug doesn't reproduce.  Have you seen any reports of that?
If someone has applied a KatMouse patch specific to Brackets to halve the scroll rate in order to work around this bug, there's no reason they'd need to leave that patch in place now that Brackets is 'fixed.'  It doesn't seem like this fix should interfere with any other use of those mouse hack tools.
I'm not saying we should give up on fixing the CEF bug.  But realistically even if it was fixed today it would probably be 2+ months before we could get that fix into the hands of users.  That's why I think we should merge this as a stopgap.

This pref change seems fair though.  I'm ok with merging this -- @nethip lmk if you'd have any concerns about this going into 1.3.

@peterflynn No issues. I was waiting for this to be fixed from CEF side, but looks like that is going to take some time. Meanwhile we should push in this fix.

@MarcelGerber Did you want to squash before this is merged?  If you have time on Thursday that would be great.  Otherwise I can just go ahead and merge as-is.

@peterflynn Commits squashed.

Closing since this was superseded by #10930, which is now merged into release


[Android] Bugsnag: unable to find ReactNative bundle task 'bundleReleaseJsAndAssets' on react-native 0.71.x+

Describe the bug
I'm currently testing 0.72.0-rc.3 but this issue exists on 0.71.x too.
As of react native 0.71 this line on xxx/app/build.gradle  is deprecated and totally removed from 0.72:
apply from: "../../node_modules/react-native/react.gradle"
Environment

Bugsnag version: 7.20.2

click to see build.gradle

apply plugin: "com.android.application"
apply plugin: 'com.google.gms.google-services'
apply plugin: "com.facebook.react"

import com.android.build.OutputFile

/**
* This is the configuration block to customize your React Native Android app.
* By default you don't need to apply any configuration, just uncomment the lines you need.
*/
react {
   /* Folders */
   //   The root of your project, i.e. where "package.json" lives. Default is '..'
   // root = file("../")
   //   The folder where the react-native NPM package is. Default is ../node_modules/react-native
   // reactNativeDir = file("../node_modules/react-native")
   //   The folder where the react-native Codegen package is. Default is ../node_modules/react-native-codegen
   // codegenDir = file("../node_modules/react-native-codegen")
   //   The cli.js file which is the React Native CLI entrypoint. Default is ../node_modules/react-native/cli.js
   // cliFile = file("../node_modules/react-native/cli.js")

   /* Variants */
   //   The list of variants to that are debuggable. For those we're going to
   //   skip the bundling of the JS bundle and the assets. By default is just 'debug'.
   //   If you add flavors like lite, prod, etc. you'll have to list your debuggableVariants.
   // debuggableVariants = ["liteDebug", "prodDebug"]

   /* Bundling */
   //   A list containing the node command and its flags. Default is just 'node'.
   // nodeExecutableAndArgs = ["node"]
   //
   //   The command to run when bundling. By default is 'bundle'
   // bundleCommand = "ram-bundle"
   //
   //   The path to the CLI configuration file. Default is empty.
   // bundleConfig = file(../rn-cli.config.js)
   //
   //   The name of the generated asset file containing your JS bundle
   // bundleAssetName = "MyApplication.android.bundle"
   //
   //   The entry file for bundle generation. Default is 'index.android.js' or 'index.js'
   // entryFile = file("../js/MyApplication.android.js")
   //
   //   A list of extra flags to pass to the 'bundle' commands.
   //   See https://github.com/react-native-community/cli/blob/main/docs/commands.md#bundle
   // extraPackagerArgs = []

   /* Hermes Commands */
   //   The hermes compiler command to run. By default it is 'hermesc'
   // hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
   //
   //   The list of flags to pass to the Hermes compiler. By default is "-O", "-output-source-map"
   // hermesFlags = ["-O", "-output-source-map"]
}

project.ext.react = [
       enableHermes: true,
       bundleInDebug: true,
       //        bundleInStaging: true,
       //        devDisabledInStaging: true,
       //        hermesFlagsForVariant: {
       //            def v -> v.name.toLowerCase().contains('release') || v.name.toLowerCase().contains('staging') ? ['-w'] : []
       //        },
       //        deleteDebugFilesForVariant: {
       //            def v -> v.name.toLowerCase().contains('release') || v.name.toLowerCase().contains('staging')
       //        }
]

project.ext.reanimated = [
       buildFromSource: true
]

/**
* Set this to drawtrue to create two separate APKs instead of one:
*   - An APK that only works on ARM devices
*   - An APK that only works on x86 devices
* The advantage is the size of the APK is reduced by about 4MB.
* Upload all the APKs to the Play Store and people will download
* the correct one based on the CPU architecture of their device.
*/
def enableSeparateBuildPerCPUArchitecture = false

/**
* Run Proguard to shrink the Java bytecode in release builds.
*/
def enableProguardInReleaseBuilds = false

/**
* The preferred build flavor of JavaScriptCore.
*
* For example, to use the international variant, you can use:
* `def jscFlavor = 'org.webkit:android-jsc-intl:+'`
*
* The international variant includes ICU i18n library and necessary data
* allowing to use e.g. `Date.toLocaleString` and `String.localeCompare` that
* give correct results when using with locales other than en-US.  Note that
* this variant is about 6MiB larger per architecture than default.
*/
def jscFlavor = 'org.webkit:android-jsc:+'
/**
* Whether to enable the Hermes VM.
*
* This should be set on project.ext.react and mirrored here.  If it is not set
* on project.ext.react, JavaScript will not be compiled to Hermes Bytecode
* and the benefits of using Hermes will therefore be sharply reduced.
*/

/**
* Architectures to build native code for.
*/
def reactNativeArchitectures() {
   def value = project.getProperties().get("reactNativeArchitectures")
   return value ? value.split(",") : ["armeabi-v7a", "x86", "x86_64", "arm64-v8a"]
}

def safeExtGet(prop, fallback) {
   rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}

def FACEBOOK_SDK_VERSION = safeExtGet('facebookSdkVersion', '13+')

android {
   ndkVersion rootProject.ext.ndkVersion
   compileSdkVersion rootProject.ext.compileSdkVersion
   namespace "com.xxxxxx"

   configurations.all {
       resolutionStrategy {
           force "com.facebook.fresco:fresco:2.5.0"
           force "com.squareup.okhttp3:okhttp:4.10.0"
           force "com.squareup.okhttp3:okhttp-urlconnection:4.10.0"
           force "com.squareup.okio:okio:3.3.0"
       }
   }

   signingConfigs {
       debug {
           keyAlias 'key'
           keyPassword 'xxxxxx'
           storeFile file('../app/debug.keystore')
           storePassword 'xxxxxx'
       }

       signing {
           keyAlias 'key'
           keyPassword 'xxxxx'
           storeFile file('../keystores/release.keystore')
           storePassword 'xxxxxxx'
       }

       staging {
           keyAlias 'key_staging'
           keyPassword 'xxxxxxx'
           storeFile file('../keystores/staging.keystore')
           storePassword 'xxxxx'
           v1SigningEnabled true
           v2SigningEnabled true
       }
   }

   packagingOptions {
       pickFirst '**/armeabi-v7a/libc++_shared.so'
       pickFirst '**/x86/libc++_shared.so'
       pickFirst '**/arm64-v8a/libc++_shared.so'
       pickFirst '**/x86_64/libc++_shared.so'
       pickFirst '**/x86/libjsc.so'
       pickFirst '**/armeabi-v7a/libjsc.so'
   }

   defaultConfig {
       applicationId "com.xxxxx"
       minSdkVersion rootProject.ext.minSdkVersion
       targetSdkVersion rootProject.ext.targetSdkVersion
       versionCode 1140
       versionName "2.0.21"
       multiDexEnabled true
   }

   splits {
       abi {
           reset()
           enable enableSeparateBuildPerCPUArchitecture
           universalApk false // If true, also generate a universal APK
           include( * reactNativeArchitectures())
       }
   }

   buildTypes {
       release {
           minifyEnabled false
           signingConfig signingConfigs.signing
       }

       debug {
           signingConfig signingConfigs.debug
       }
       //        staging {
       //            matchingFallbacks = ['release']
       //            signingConfig signingConfigs.staging
       //            applicationIdSuffix ".stage"
       //        }
   }
   // applicationVariants are e.g. debug, release
   applicationVariants.all {
       variant ->
           variant.outputs.each {
               output ->
                   // For each separate APK per architecture, set a unique version code as described here:
                   // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
                   def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
                   def abi = output.getFilter(OutputFile.ABI)
                   if (abi != null) { // null for the universal-debug, universal-release variants
                       output.versionCodeOverride =
                               defaultConfig.versionCode * 1048576 + versionCodes.get(abi)
                   }
           }
   }

   subprojects {
       project.configurations.all {
           afterEvaluate {
               project ->
                   if (project.hasProperty("android")) {
                       android {
                           compileSdkVersion rootProject.ext.compileSdkVersion
                           buildToolsVersion rootProject.ext.buildToolsVersion
                       }
                   }
           }

           resolutionStrategy.eachDependency {
               details ->
                   if (details.requested.group == 'com.android.support' &&
                           !details.requested.name.contains('multidex')) {
                       details.useVersion rootProject.ext.buildToolsVersion
                   }
           }
       }
   }
}

dependencies {
   dependencies {
       constraints {
           implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.8.0") {
               because("kotlin-stdlib-jdk7 is now a part of kotlin-stdlib")
           }

           implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.8.0") {
               because("kotlin-stdlib-jdk8 is now a part of kotlin-stdlib")
           }
       }
   }

   implementation fileTree(dir: "libs", include: ["*.jar"])
   //noinspection GradleDynamicVersion
   implementation "com.facebook.react:react-native:+" // From node_modules
   implementation "com.facebook.android:facebook-android-sdk:${FACEBOOK_SDK_VERSION}"
   implementation "androidx.core:core-splashscreen:1.0.0"
   implementation "androidx.swiperefreshlayout:swiperefreshlayout:1.1.0"
   implementation 'androidx.appcompat:appcompat:1.4.2'
   implementation 'com.facebook.fresco:webpsupport:2.5.0'
   implementation 'com.facebook.fresco:fresco:2.5.0'
   implementation 'com.facebook.fresco:animated-webp:2.5.0'
   implementation 'com.facebook.fresco:animated-gif:2.5.0'
   implementation 'me.leolin:ShortcutBadger:1.1.21@aar'
   implementation 'androidx.multidex:multidex:2.0.1'
   implementation 'com.android.support:support-core-utils:24.2.1'
   implementation 'com.google.android.gms:play-services-location:20.0.0'
   implementation "com.bugsnag:bugsnag-plugin-android-okhttp:5.+"
   implementation("com.squareup.okhttp3:okhttp:4.10.0")
   implementation("com.squareup.okhttp3:okhttp-urlconnection:4.10.0")
   implementation("com.squareup.okio:okio:3.3.0")

   debugImplementation("com.facebook.flipper:flipper:${FLIPPER_VERSION}") {
       exclude group: 'com.facebook.fbjni'
   }

   debugImplementation("com.facebook.flipper:flipper-network-plugin:${FLIPPER_VERSION}") {
       exclude group: 'com.facebook.flipper'
       exclude group: 'com.squareup.okhttp3', module: 'okhttp'
   }

   debugImplementation("com.facebook.flipper:flipper-fresco-plugin:0.182.0") {
       exclude group: 'com.facebook.flipper'
   }

   if (hermesEnabled.toBoolean()) {
       implementation("com.facebook.react:hermes-android")
   } else {
       implementation jscFlavor
   }
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
   from configurations.implementation
   into 'libs'
}

project.ext.vectoricons = [
       iconFontNames: [
               'FontAwesome6_Pro_Solid.ttf',
               'FontAwesome6_Pro_Regular.ttf',
       ]
]

apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle");
applyNativeModulesAppBuildGradle(project)
apply from: "../../node_modules/react-native-vector-icons/fonts.gradle"
apply plugin: "com.bugsnag.android.gradle"
bugsnag {
   uploadReactNativeMappings = true // enables upload of React Native source maps,
   retryCount = 200
   overwrite = true
}

Click to see settings.gradle
rootProject.name = 'xxxxxxxx'
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/@react-native/gradle-plugin')
include ':app', ':react-native-code-push'
project(':react-native-code-push').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-code-push/android/app')

apply from: new File(["node", "--print", "require.resolve('expo/package.json')"].execute(null, rootDir).text.trim(), "../scripts/autolinking.gradle")
useExpoModules()

ps. Please update the react-native examples on the repo, they're still on 0.6x versions!

Hi @efstathiosntonas - we recently released support for uploading React Native source maps on Android via the bugsnag-cli.
Could you try following our React Native 0.71 specific docs to upload with the bugsnag-cli and let us know how you get on?
https://docs.bugsnag.com/platforms/react-native/react-native/rn071/.

@luke-belton I've followed the docs and now the issue is gone. Thanks for the heads up!
just for clarity, I've removed this no longer needed line: apply from: "../../node_modules/react-native/react.gradle" and it builds fine.

@efstathiosntonas I have removed this line and i still have  the same issue

Hi @MaxToyberman
If you are still having issues with this after following our current React Native documentation, would you be able to open a ticket with us directly by contacting<EMAIL_ADDRESS>Please quote this GitHub issue, and include any BugSnag configuration, as well as your build.gradle and settings.gradle files if you can.

Are there any publicly available resolutions to this issue? I get a similar error on React Native Android build:
Bugsnag: unable to find ReactNative bundle task 'bundleMyProdAppReleaseJsAndAssets'
Bugsnag: unable to find ReactNative bundle task 'bundleMyBetaAppReleaseJsAndAssets'

I have two flavors for my Android app: myprodapp and mybetaapp.

Hi @JJSLIoT,
React Native v0.71 introduced some significant changes to the way React Native interacts with Gradle. This means that the BugSnag Android Gradle Plugin is no longer able to automatically upload Android source maps.
The BugSnag CLI has since been improved and is now the recommended tool for uploading React Native source maps.
If you have recently updated your React Native version to 0.71 or higher, you should follow our documentation for manually uploading Android source maps using the BugSnag CLI
The configuration you've mentioned is indeed invalid for React Native 0.71 and above, and we recommend removing the BugSnag Android Gradle Plugin from your application as it will now be incompatible.
If you still want the source maps to be uploaded as part of your build, you can add the command to upload the source maps as a build task after the source map generation.


Check that counts are integers in  _validate_counts_vector

It is possible to pass non-int values to the Shannon entropy without throwing an error:
import skbio.diversity.alpha as skdiv
import numpy as np
counts = [1, 2.2]
skdiv.shannon(counts) # 0.8960

The _validate_counts_vector only checks if the numbers are non-negative and real. I suggest one substitutes the check "isreal" with a "is integer" check.
np.issubdtype(np.asarray([1, 2.2]).dtype, np.integer) # false
np.issubdtype(np.asarray([1, 2]).dtype, np.integer) # true

It's not usual to compute shannon on floating point values. I'm closing as I don't think this is a concern but please reopen if I'm wrong


feat: remove useless spawn_blocking

This usage of spawn_blocking is useless. And waste some performance , since tokio may crate a thread for it.

but the disk I/O will occupy the runtime thread and block other tasks from being scheduled?

note that it's sync I/O here instead of async I/O inside the spawn_blocking

Here is a simple perf stat result.
TPCH 10G data
select
    sum(l_extendedprice) as sum_base_price,
    avg(l_discount) as avg_disc,
    count(*) as count_order
from
    lineitem;

Remove spawn_blocking
         14,113.10 msec task-clock                       #    1.173 CPUs utilized
             7,085      context-switches                 #  502.016 /sec
                64      cpu-migrations                   #    4.535 /sec
           772,980      page-faults                      #   54.770 K/sec
    22,703,318,259      cycles                           #    1.609 GHz                         (82.99%)
     1,784,793,934      stalled-cycles-frontend          #    7.86% frontend cycles idle        (83.49%)
     6,680,958,786      stalled-cycles-backend           #   29.43% backend cycles idle         (83.24%)
    36,582,277,643      instructions                     #    1.61  insn per cycle
                                                  #    0.18  stalled cycles per insn     (83.48%)
     6,194,729,232      branches                         #  438.935 M/sec                       (83.25%)
       194,448,934      branch-misses                    #    3.14% of all branches             (83.63%)

      12.033058573 seconds time elapsed

       8.076494000 seconds user
       6.023971000 seconds sys

The main branch
         23,975.43 msec task-clock                       #    1.418 CPUs utilized
           356,000      context-switches                 #   14.849 K/sec
               281      cpu-migrations                   #   11.720 /sec
           657,275      page-faults                      #   27.415 K/sec
    29,943,693,477      cycles                           #    1.249 GHz                         (83.17%)
     2,389,946,991      stalled-cycles-frontend          #    7.98% frontend cycles idle        (83.23%)
     9,854,147,750      stalled-cycles-backend           #   32.91% backend cycles idle         (83.00%)
    37,148,855,213      instructions                     #    1.24  insn per cycle
                                                  #    0.27  stalled cycles per insn     (83.37%)
     6,336,456,023      branches                         #  264.290 M/sec                       (83.31%)
       217,676,506      branch-misses                    #    3.44% of all branches             (83.95%)

      16.905472146 seconds time elapsed

      11.701711000 seconds user
      11.605966000 seconds sys

By the way, the CPU utilization rate of risinglight is very low even on some complex queries.

All scan executor's IO will be handle by get_block. This func's performance is very curial for us, we should consider refactor it?

By the way, the CPU utilization rate of risinglight is very low even on some complex queries.

The aggregation would be bound by a single cpu core now. We don't partition data and make it parallel yet.

Would you please try block_in_place and see if it improves perf?

Would you please try block_in_place and see if it improves perf?

Ok

Would you please try block_in_place and see if it improves perf?

Updated

Thanks for your work and based on the benchmark result, I would rather opt in for block_in_place. The problem of having I/Os inside the tokio runtime thread is that it avoids other futures from being scheduled. This would only be a temporary relief until we do a full parallelism in the system.


pfe-accordion throwing JS error

With the latest code from master, and after running npm clean && npm install && npm run start, when I view https://www.evernote.com/l/AA7-1NZ14q1P3ZlUxz_mOQ09PB0Za-FT5VA I see this error in the console:
Unchecked runtime.lastError: The message port closed before a response was received.

Likely a browser extension error, not PFE.  Can you try in incognito mode to verify?

@starryeyez024  I'll close this, but feel free to re-open if you're still seeing the issue.


[fix] explicitly add kit to ssr.noExternal

Closes #2237

It would be nice if we could be resolve the issue from our side first without waiting for upstream where we have no control, but delegating this to be handled on the plugin side would be nice too. Fixing it here or moving them to vite-plugin-svelte, and then updating it when upstream fixes it should be ideal either way.

yeah, makes sense


Add Vasileios as editor

In light of contributions to the spec and agreement from the WG, this PR adds Vasileios as an editor to the core spec.

Multiple approvals, discussed in WG slack, no objections, merging.


mac os 12.0 build

macOS 12 is not available yet in Github Actions: https://github.com/actions/virtual-environments/issues/3649#issuecomment-995862148


Group python components into installable package

Closes #14 when complete

Completed:

[x] data_utils is now installable with pip install . and can then be imported with from climsim_utils.data_utils import data_utils
[x] added basic smoke test for importability, and run that test in CI
[x] 🎉 tests pass in CI! https://github.com/leap-stc/ClimSim/actions/runs/5896732534/job/15995137882?pr=16
[x] update data_utils import in preprocessing notebook

TODO (for this PR):

[ ] update data_utils import in all other notebooks
[ ] Document how to install package in README (pip install . from repo root)


Test Issue created at Mon, 28 Feb 2022 02:23:06 GMT

Test issue body  Mon, 28 Feb 2022 02:23:06 GMT

Comment on issue at Mon, 28 Feb 2022 02:23:08 GMT


Add doc for expresjs middleware modules, utility modules

@dougwilson Per #680, I culled the list of middleware modules based on your input.
For the utility modules/functions, I just list them in a table but don't pull in their READMEs.
For now, I have a bash script to pull down the READMEs.  In future, I'd like to write a little Node program to do it instead, but haven't yet had time yet.

I'm going to go ahead and merge this, since Doug already reviewed it at an earlier stage.  I'm happy to make further changes later if needed.

Sorry I didn't respond :( Sounds good!


Do not allocate/copy to a utf-32 string to count a utf-32 len.

This patch prevents us from allocating temporary strings to count
the string's length in unicode code points, and drops the use of
the deprecated API codecvt introduced in
https://github.com/envoyproxy/protoc-gen-validate/pull/256
It is unclear how we wire this against protobuf's header file,
src/google/protobuf/stubs/strutil.h
so this patch is not ready for merging quite yet.
Resolves a win32 issue of missing char32_t-based codecvt
implementations in their stdlib (win32 favors uchar.)
Signed-off-by: Yechiel Kalmenson<EMAIL_ADDRESS>Signed-off-by: William A Rowe Jr<EMAIL_ADDRESS>

/wait

Note this isn't blocked by, but is greatly improved by acceptance of this patch to fix protobuf;
https://github.com/protocolbuffers/protobuf/pull/6844

We've managed to resolve the header inclusion to get this implementation running under envoy's bazel environment.
This patch is ready for review @SecurityInsanity or @lizan - thanks in advance.


Limiting number of cpus used?

I've been noticing that when I run UMAP part of the computation runs in parallel. I'd like to be able to limit the number of processes that get used per transformation. This would be useful for keeping a decent cpu utilization rate without risking getting my jobs killed.
I've tried limiting the number of threads numba uses (numba.config.NUMBA_NUM_THREADS), but that hasn't seemed to work.
Is this something which is currently configurable, or a feature that could be added?
Thanks!

In practice I believe almost all the actual parallel work is actually done with in ARPACK in a call to eigsh, and unfortunately I am not sure how to enforce that to use fewer cores easily. The most trivial approach would be to avoid using that section of code by setting init='random'. That will lose some stability in the embedding, but should avoid the many core aspect.

I just gave that a shot, but still saw a bunch of new processes starting up. I've even tried just disabling numba but still get the same behavior. For reproducibilities sake, here's the code I've been testing with and the environment variables I've tried.
# In bash, previously
# export NUMBA_NUM_THREADS=1
# export NUMBA_DISABLE_JIT=1
from sklearn.datasets import load_iris, load_digits
import umap

digits = load_digits()
reducer = umap.UMAP(init="random")
embedding = reducer.fit_transform(digits.data)

With no numba, and no spectral initialisation you've eliminated most of the options for threading. In general threading is only going to happen in the case of library calls -- everything in umap itself relies on numba for any threading. The most likely candidate for what is going on here is that because you have very little data umap is using pairwise_distances from sklearn, which I believe can and potentially does parallelise the work. I don't have any explicit options set, and I can't say I know how to turn that off. With larger datasets (more than 4096 samples) this will not be the case.

Thanks for the help! Running with a larger dataset, the amount of time with multiple cpus has gone down. It looks like there's something else spawning a bunch of python processes for a short period of work. I haven't quite nailed down what that is – but I suspect scikit-learn. I'm going to investigate that a bit more and will hopefully come back with a configuration for limiting the cpus used.

Can this be closed?

@ivirshup Any updates?

@ivirshup seems to be correct. scikit-learn relies on numpy/scipy routines which are creating multiple processes. What appears to work is setting an environment variable to force the underlying parallelism libraries to use a specific number of processors (per the source below). If scikit-learn was retrieved from pypi (or conda-forge), you need to export the environment variable OPENBLAS_NUM_THREADS, but if it was retrieved from base conda, the environment variable should be MKL_NUM_THREADS (I have not tested this one though). Hopefully this helps anybody else that ran into this issue as well.
Source (scikit-learn)

In newer versions of umap you may also want to add NUMBA_NUM_THREADS to the list. There is a pull request underway that would allow user set at runtime thread limits for numba (numba/numba#4615), but it is not yet complete. When that gets added to numba I'll try to update umap to take advantage of that and allow easier user specified cpu usage.

@lmcinnes any updates on cpu core limiting?

Yes, that pull request got merged and the n_jobs parameter now makes use of it, so it should work if you set it.


cloudlaunch: use Create Project API

It seems there's a programmatic way to create Google Cloud Platform projects now?
See:
https://github.com/google/google-api-go-client/issues/138
(the Cloud Resource Manager API, as of v1beta1?)

This API is now officially launched and out of beta.
Please prioritize using this in our launcher.

ACK, top of TODO list now.

@bradfitz while working on this, I found out that I was getting a 403 when trying to create a new project, using a service account from one of my existing projects to authenticate (the same way we would use the camlistore-website service account in production). I believe the reason is, according to https://cloud.google.com/resource-manager/ , that project creation is invite-only, even using the API.
So I've contacted the sales team, as they request but, even if I do get an invite, and we do get one for the camlistore-website service account, unless I got confused by OAuth2 again, don't we need each user to have that privilege as well, since they are the ones delegating to us whatever the launcher is doing?

Related: https://github.com/google/google-api-go-client/issues/173

https://camlistore-review.googlesource.com/9906


Add proper macro support

-Added TargetInspector component to read in-game target states.
-Allow for hold transfers.
Controls should behave identical to PS4 version now.

The code for this feature is not the best, but it works well.
I will see if I can improve this overtime.


Update profile.ts to add default values

Add some default values to the LinkedIn data import in case of missing data. Default values used in place of optional data in order to minimize changes to other parts of the codebase; since optionals require an extra step to handle.  Default values of whitespace might work better, but I cannot test to be sure.
Closes: #1604

This might help, definitely. I would have preferred them to be empty strings instead of actual values because the end user might get confused as to where this data is coming from. But that's a minor change. Thank you for the contribution! :)


Make it easier to not block the UI with long-running operations

This is somewhat similar to #623 but for the specific use case where an app developer might do a long-running operation (e.g. expensive API call) and still allow the user to do UI work.
Because Mesop queues user events to avoid race conditions, this results in the UI being blocked. There's potentially some creative workarounds, but no good pattern for this at the moment.

Another adjacent use case is being able to cancel the long-running operation which isn't really possible today.

On second thought, I think #623 captures this use case already.


IIR Filter block documentation lacking

I have found the filter taps in /comms/iir_filter block to be in reverse order to what spuce expects.
spuce taps are in b[0], b[..], a[0], a[...] order.
https://github.com/pothosware/PothosComms/blob/434627b8572fed2fa48f11b7876e196f4da85114/filter/IIRFilter.cpp#L64-L68
Should mention taps are in order of b, a
https://github.com/pothosware/PothosComms/blob/434627b8572fed2fa48f11b7876e196f4da85114/filter/IIRFilter.cpp#L29-L31
Thanks

I wonder if this could be better with separate feed forward and feedback taps as parameters.
Anyway, I think the library calls into spuce are right. The same guy wrote both spuce and these blocks, so it should be good :-). The taps are organized as {b_taps, a_taps}, and I think this is also true for the spuce library:
So I think its just an issue with the debug prints being wrong/reversed. Are you seeing the same thing?
From spuce:
  void set_taps(const std::vector<Coeff>& taps) {
    // Divide vector in half, 1st half are feedforward, 2nd half feedback
    assert(taps.size() != 0);
    auto size = taps.size()/2;
    zeros.set_size(size);
    poles.set_size(size-1);
    for (size_t i = 0; i < size; i++) { zeros.settap(i, taps[i]); }
    // Skip 1st feedback and negate the rest
    for (size_t i = 0; i < size-1; i++) { poles.settap(i, -taps[i+size+1]); }
}

@audiofilter if there was a way to set the taps as two parameters (feed-forward, feedback) in the iir_df, we could separate out the taps in the designer and block in to separate arrays: https://github.com/audiofilter/spuce/blob/master/spuce/filters/iir_df.h

I have tested it again with taps from gr_filter_design and the order is B, A. sorry for the false alarm. Its just the debug code thats back to front
Could be handy to have them settable in two separate arrays as they are not always the same length from some generators.


Fixed error when using Phantomjs with CORS

Fixed error "INVALID_STATE_ERR: INVALID_STATE_ERR: DOM Exception 11" when testing in Phantomjs with CORS active.

Hi @Gomes81
Can you please explain what the changes you have here actually address?
is it the apply ing of an empty array as arguments that triggers something in phantom?

Hi Maurice,
First I moved ajax.request.withCredentials = !!settings.withCredentials to a line after ajax.request.open, this seems to be an issue in some other browsers too and this seems to be a requirement as documented in Mozilla (here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Requests_with_credentials).
After that I had to remove the bind, since phantomjs tells me that timeout.bind is not defined (and replaced it with and ugly code that use apply).
Hope this explanation helps. Thanks.

Thanks @Gomes81
This has been merged in 0aa5750f96500fe50c4936cd9984e1147ad053ea and published as<EMAIL_ADDRESS>


[REQUEST]  Add queued download functionality

Is your feature request related to a problem? Please describe.
The program does not allow downloading in queues, as is the case with torrents.
Describe the solution you'd like
add queued download functionality, to start a download as soon as one finishes.
Describe alternatives you've considered
No response
Additional context
No response

Implemented in 2.0.


Make sidebar responsive

Hi. It would be great if you can add option for automatic close sidebar when screen size is < 640px(for example) .

You could probably just implement this yourself:
<div (window.resize)="_onResize($event)">
  <ng-sidebar-container>
    <ng-sidebar #sidebar>
       ...
    </ng-sidebar>
  </ng-sidebar-container>
</div>

_onResize(e: Event) {
  if (window.innerWidth < 640px && this.sidebar.opened) {
    this.sidebar.close();
  }
}

I'm sort of paraphrasing a bit, but I think something like that would work.

Yeah, I did it in the same way. I just thought about having that feature
out of the box.
On Fri, Feb 17, 2017, 22:41 Eugene Cheung<EMAIL_ADDRESS>wrote:

You could probably just implement this yourself:

       ...

_onResize(e: Event) {
if (window.innerWidth < 640px && this.sidebar.opened) {
this.sidebar.close();
}
}
I'm sort of paraphrasing a bit, but I think something like that would
work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arkon/ng-sidebar/issues/47#issuecomment-280700897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKZAIVWDqRk4kyNjjRY4Lmtswg4vxqmuks5rdc2jgaJpZM4MD7vB
.

I'll consider it. I'm thinking of how it'd look like as an option. Something like [autoCollapse]="'640px'"? I guess the value would indicate either the window width or height depending on the positioning of the sidebar. It might also be of interest to throttle the resize event handler.

Yeah, [autoCollapse] is good name. Probably, it's better to create two options, one for width and one for height for better customizing, but it's details.

[autoCollapseHeight] and [autoCollapseWidth] have been added in v3.4.0.

I want to collapse based on width but in the opposite direction, collapse if scren width is larger than we want.
Any idea ?

Make a new issue for a feature request.


Remove version: Canonical.Juju version 2.9.9

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://launchpadlibrarian.net/549394165/juju-setup-2.9.9-signed.exe
Status Code: 200
(Automated message - build 903)

Close with reason: Duplicate;


Support VHELM and image2struct in React app

Fixes a bunch of issues that cause image2struct and VHELM to not render properly.

This is still not working for me. Here are the logs of my browser when I run helm-server on the benchmark output I sent you.


Incorrect shape for sliced array

I noticed some odd behavior when slicing an array. I am getting an incorrect shape for the sliced array, but only under some specific conditions. It seems like I am getting a transpose of what I am expecting. This code should reproduce the issue:
# pythran export slice_matrix()
def slice_matrix():
    # this error only happens for sizes >= 16 and when the base matrix is
    # tranposed
    base = np.zeros((16, 16)).T
    slice1 = base[:10, 10:] # should have shape (10, 6)
    # this error only happens when a second slice is taken of the base matrix
    slice2 = base[:]
    print('slice1 shape: %s' % str(slice1.shape)) # slice1 shape: (6, 10)

Let me know if you need any other information.
Thanks!

Hey @treverhines, thanks for the detailed report! I can reproduce your issue, keep in touch!


Update "Connect your app to the cloud" page for VS2019

The page windows-iotcore/connect-to-cloud/ConnectAppToCloud.md basically says to use a connected service extension in VS2017. However, that extension was never ported to VS2019.

Have you tried it with 2019? I believe it still works. Let me know if you're running into issues.

Yes, I've tried VS2019, but when I go to add a new connected service, Azure IoT Hub is not listed. I've installed the "Azure development" workload, and I don't see anything that looks relevant in the individual components list.

Please post this on our forums. Our GitHub issues are for documentation related inquiries only. Thank you.


Using Laravel Voyager as a cms Unable to log in

Hello, thanks for the wonderful package, I am trying to use this package https://github.com/the-control-group/voyager as a kind of cms then i serve its content through your API boilerplate, i have both installed but the problem is that i cannot seem to log in using voyager i always get a 302,  web login doesn't seem to work when using your package i have even tried generating the laravel auth scaffold and trying from there with the same results
I would really appreciate your help
Thanks

Thanks for writing. However, this doesn't seem related to my package but to something related to Voyager, closing it. Issues should be opened only if related to the package.


Make actions returned FSA compliant

I think it would be best to make sure the actions returned and accepted by the middleware follow a standard. Right now, the actions dispatched from the promise are FSA compliant, but the types array used in the action creators is not a part of the standard. Need to figure out how to handle that.
One thought is to just have one type instead of an array and just append _FULFILLED and _REJECTED to that type.

Auto post fixing works for me.  At the moment I'm using a small generator function to produce the 3 variant action types, so this proposal would remove the need for that.

Great! Yeah, I think this is the way to go. I'm away on vacation until August 10, but I plan to work on this improvement after then. :smile:

It would might be nice to specify the suffix, and another thing to think about is sometimes it's a prefix:
BEGIN_STUFF, SUCCESS_STUFF, ERROR_STUFF
const config = {
   fulfilled: '_SUCCESS',
   rejected: '_ERROR'
}

promiseMiddleware(config)

Having said all that having the decision made for you on async actions is rather nice.

This might need to happen sooner rather than later, with https://github.com/rackt/redux/releases/tag/v3.0.0 being a thing.

It will always create actions with a type other than undefined so this is safe.

But it'll be hard to get those actions into the middleware unless they have a type themselves, won't it?

Yes, that is correct—not sure what I was thinking before. I can change it to type.
Do you have any opinions on sending an array v. not sending one? I am not opposed to my original idea of having one type and appending _FULFILLED and _REJECTED to that type.
The only problem is some people like to have a generic fulfilled/rejected type, e.g., REQUEST_PENDING, MY_ASYNC_ACTION, and REQUEST_REJECTED`. Personally, I don't do this, but a few people on Slack who use this middleware brought that to my attention.

Appending the _FULFILLED and _REJECTED suffixes seems plenty reasonable.
A good middle ground might be an override mechanism, as an escape hatch if there's a particular reason why someone would want their own action names. I would probably end up using this kind of system personally, as I like to keep action names in a separate file so I can see them all in one place.
e.g.
import {
  FETCH_WIDGETS,
  FETCH_WIDGETS_GETREADY,
  FETCH_WIDGETS_ALLDONE,
  FETCH_WIDGETS_OHDEAR,
} from './constants';

dispatch({
  type: FETCH_WIDGETS,
  promiseTypes: {
    pending: FETCH_WIDGETS_GETREADY,
    fulfilled: FETCH_WIDGETS_ALLDONE,
    rejected: FETCH_WIDGETS_OHDEAR,
  },
  // ...
})

+1 for supporting an override at a minimum

Have been using something similar!
Made a PR here: https://github.com/pburtchaell/redux-promise-middleware/pull/10

Nice! I will check it out this weekend and try to get it merged. Just to let you all know, I am also working on some changes to the middleware on the dev branch.

Update: PR #10 looks great; thanks @tomatau! With a rebase and one minor change, this should be resolved.

@pburtchaell Done :)

Ok. So as of version 2.0.0 everything is FSA compliant.


Unreal: Fix transform when loading layout to match existing assets

Changelog Description
Fixed transform when loading layout to match existing assets.
Additional info
Changed the way the transform is applied to match the one for the regular layout loading.
Testing notes:

In Unreal, load assets that have been published in a layout.
Add the assets to a level and save it.
Open the loader, select the layout, and select Load Layout on Existing Scene.
The transform for the assets should be correct.

I was wondering, since we removed the fbx and abc matrix changes, if they are done somewhere else or they are no longer needed?


[BUG]: Updating the dataset names going into Transform dataset does not update the comment with the mapping.

Describe the bug
Don't know which dataset is which if I don't first save the simulation output for reuse. Updating the dataset names does not update the comment with the mapping.
To Reproduce
Steps to reproduce the behavior:

After running two different simulate (but NOT saving for reuse), add a transform dataset to the canvas and plug the output of each dataset into it. It will show two pills at the top both named dataset-1 and nothing mapped in the comment.
Go back to the simulate and save for reuse (give different names). These names are reflected in the pills but the comment is not updated. If I disconnect and reconnect after renaming then it works.

Expected behavior
The comment should indicate which dataset is mapped to each dataframe.
Screenshots

A simulation run that has not been saved will have a name similar to: Forecast run f1d4c215-f7e5-49f1-b098-72542f2ea942
In the first scenario would we like to have #d1 = Forecast run f1d4c215-f7e5-49f1-b098-72542f2ea942?
In the second scenario where a user then renames this dataset we would then like to update it to #d1 = updated_name_here?

Note to complete this task once above questions are answered:
Ensure the following gets updated correctly: https://github.com/DARPA-ASKEM/terarium/blob/main/packages/client/hmi-client/src/components/dataset/tera-dataset-jupyter-panel.vue#L161-L170
Update logic on how we are setting first code cell here: https://github.com/DARPA-ASKEM/terarium/blob/main/packages/client/hmi-client/src/components/llm/tera-jupyter-chat.vue#L442
Depending on above answers we may want to watch defaultPreview and reset notebookItems.value[0]


Guide on how to theme

I guess I could improve the docs a bit.
For example, set THEME in web/.env to:
{"palette":{"type":"light","primary":{"main":"#6a1b9a"},"secondary":{"main":"#3f51b5"}}}

For dark theme set type to "dark".
https://material-ui.com/customization/color/#color-tool shows you the recommended colors. Pick from there, and be sure to replace if needed the named colors with the hex codes.
It'd be difficult to customize anything more than the colors.


Settings Language dropdown not populated on first run

Steps to reproduce

clone ocis
cd owncloud/ocis/ocis
make build ocis
bin/ocis server
browser -> localhost:9200
login as einstein (or any other user)
go to Settings
Languages dropdown is unpopulated

Expected behaviour
It should display English for the logged in user.
Actual behaviour
It shows nothing.

https://github.com/owncloud/ocis/pull/2465 fixes the this issue.

Closed via #2465


UI: let user to configure etcd snapshots for RKE clusters

We should enable etcd snapshot configuration for 2.1.x in the UI. Here are the 3 parameters we have to let user configure (@galal-hussein would update types to provide some meaningful defaults, but assume that snapshot would be set to true by default)
https://github.com/rancher/types/blob/325dce50b65029b88f561ef2788419799ebf921e/apis/management.cattle.io/v3/rke_types.go#L181
https://github.com/rancher/types/blob/325dce50b65029b88f561ef2788419799ebf921e/apis/management.cattle.io/v3/rke_types.go#L183
https://github.com/rancher/types/blob/325dce50b65029b88f561ef2788419799ebf921e/apis/management.cattle.io/v3/rke_types.go#L185

version - 2.2 master 11/14
Verified fixed


Updated listStoragePools response - added new managed parameter

Description
This PR updates listStoragePools response - added new managed parameter.
Partially addresses #8731

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Manually, tested the listStoragePools API.

How did you try to break this feature and the system with this change?

@blueorangutan package

@blueorangutan package

@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10840

@blueorangutan test

@sureshanaparti a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11217)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 59495 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9588-t11217-kvm-ol8.zip
Smoke tests completed. 128 look OK, 5 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_10_attachAndDetach_iso
Failure
816.90
test_vm_life_cycle.py

test_04_deploy_vnf_appliance
Error
92.71
test_vnf_templates.py

test_04_deploy_vnf_appliance
Error
92.71
test_vnf_templates.py

test_05_delete_vnf_template
Error
1.11
test_vnf_templates.py

ContextSuite context=TestVnfTemplates>:teardown
Error
1.20
test_vnf_templates.py

test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL
Error
367.95
test_vpc_redundant.py

test_02_redundant_VPC_default_routes
Error
360.64
test_vpc_redundant.py

test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers
Error
243.05
test_vpc_redundant.py

test_04_rvpc_network_garbage_collector_nics
Error
198.68
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Error
290.63
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Error
290.64
test_vpc_redundant.py

test_01_VPC_nics_after_destroy
Error
181.78
test_vpc_router_nics.py

test_02_VPC_default_routes
Error
182.79
test_vpc_router_nics.py

test_01_redundant_vpc_site2site_vpn
Failure
424.68
test_vpc_vpn.py

test_01_vpc_site2site_vpn_multiple_options
Failure
249.94
test_vpc_vpn.py

test_01_vpc_site2site_vpn
Failure
296.31
test_vpc_vpn.py

@blueorangutan package

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10877

@sureshanaparti a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11260)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 48865 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9588-t11260-kvm-ol8.zip
Smoke tests completed. 131 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_secure_vm_migration
Error
134.38
test_vm_life_cycle.py

test_01_secure_vm_migration
Error
134.39
test_vm_life_cycle.py

test_01_vpc_site2site_vpn_multiple_options
Failure
357.73
test_vpc_vpn.py


Implement privacy mode

There should be a configurable privacy flag preventing Visual Studio Code from making any outbound connections similar to macOS firewall stealth mode. This would be useful to prevent someone with access to github operations data or an administrator of github accounts from tracking you.
Visual Studio Code immediately on launch makes various outbound tcp connections over https to Microsoft Corporation
Some Visual Studio Code out-of-the-box behavior has been seen to contact github every 3 minutes

VSCode Version: 1.16.0
OS Version: Linux

@haraldrudell  here is some information that gets you close, but not all the way there.

update.channel if set to none, we don't contact our update servers
telemetry.enableCrashReporter if set to false, we don't upload any crash data
telemetry.enableTelemetry if set to false, we don't send any telemetry data
git.autofetch and git.autorefresh if set to false, we don't talk to the configured remote anymore without you requesting it explicitly

What you currently can not prevent from happening is that we contact the extension market place to see if there are newer versions of the extensions you have installed.
Also, as extensions have access to the full node API, they can make outbound requests without us being able to control it.

I am on Linux, so I launched vscode with specific group like sg codegroup /usr/share/code/code
then the magic is:
iptables --insert OUTPUT --match owner --gid-owner $(getent group codegroup | cut --delimiter=: --field=3) --jump DROP
iptables --insert OUTPUT --match limit --limit 6/min --jump LOG --log-prefix "ipt-codegroup-output "

Thank you for your suggestions, though anything that does not block by default would not be safe. When I can bring myself to trust Docker, then I might use that.

@haraldrudell I realize this isn't for everyone, but being on linux, you might be interested in flatpak as a more general solution. With it you can put vscode inside its own container and just explicitly allow it access to certain resources (like network or certain folders). Probably not enough security for applications hellbent on breaking out of containment and wreaking havok, but probably enough for apps that are simply too "chatty". There's even a somewhat "official" packages here, and #7112 for a real official package, but both approaches seem to use a "share-all" approach, so if you use those, remember to revoke access to network and/or filesystem before running.
Snap would also be an alternative in the same spirit (#5458), but I haven't looked into the details enough to be able to recommend it.

Some additions to https://github.com/Microsoft/vscode/issues/34503#issuecomment-337695475. For VS Code core we made sure that all functions that make calls to the outside can be configured in settings as described in the FAQ. There is still the issue that extensions may implement their own outbound connections and not allow to configure those.

What you currently can not prevent from happening is that we contact the extension market place to see if there are newer versions of the extensions you have installed.

Can this behavior be disabled or configured to use a proxy? What does VSCodium do?


Is there any way to add HTTPS?

After reading few Issues I see some interests in HTTPS. Sounds like this is considered but it migth take some time. Di any one figured out with current release how to add HTTPS support (opening secure socket externally?) If yes where could I find working example?

Hello,
Pistache does not currently support https. For now, as a workaround, I would suggest using a reverse proxy such as nginx and then use Pistache downstream.
https is definitely something a lot of users have been requesting so it should be supported but I want to work on stabilizing the framework first.
Keeping your issue around when I start prioritizing https.

If it is added, it will likely be a compile-time option.  Some users want HTTPS and do not want the complexity of running a separate process as a proxy (hint: small, embedded systems).

Hi, was it added to pistache? I mean the https. Tks

Yes, PR #226, on 2019-01-28.


Rename port types?

I find it's confusing to remember between elmOutPort and elmInPort which is which. When I'm writing the code I have to check myself to try and remember whether elmIn means "from Elm into Reason" or "from Reason into Elm".
Do you think it might be more clear to name them:
portToElm and portFromElm?

Thank you for your feedback, I definitely think that those names are more clear! I will update these types.

This is done in https://github.com/jaredramirez/bs-elm/releases/tag/v1.0.0

Awesome! 👏 👏👏👏👏
Thanks!


There is an mistake in v4.0, UITableView dose not have an outlet named delegate.

i find that v3.0 does not have the mistake.

there is only one pod in the Podfile, and didn't include any other code in the project.

I never see that error, so I have no idea why are triggering this, but I'm sure it's not related to IBAnimatable.

@tbaranes you can create an new project, add only pod IBAnimatable 4.0, drag an UITableViewController in the storyboard, the mistake will appear

You are right, there is something off, that is also reproducible for UITableView 🤔

@tbaranes Any magic in 4.0? 🌚

@jjjjjeffrey After building the project this error disappears for me. I can also access the delegate of UITableView with no autocomplete error or crashing on a force unwrap.

@SD10 it's not work for me, what Xcode version did you used?

@jjjjjeffrey Sorry for the delay, I had to make sure I wasn't on Xcode9 beta.
I used 8.3.2 and this time the error didn't disappear but UITableView has a delegate property that is the UITableViewController. I tested this by putting a delegate method in for didSelectRow(at:) and nil checking the tableView.delegate property. Really strange behavior...

@jjjjjeffrey I think I've solved this in #506. Thank you for reporting this issue.


Trailing spaces when the number of background jobs is greater than 1

Current behavior
When the number of background jobs is greater than 1, spaceship-prompt shows a number 2 with trailing spaces.
Environment
Spaceship version: 3.2.0
Zsh version: 5.4.2
Zsh framework: None
Zsh plugin manager: zplug
Terminal emulator: iTerm
Operating system: macOS
Screenshot

Possible solution
piping the solution of jobs | wc -l to xargs seems to solve the problem.

I personally can't reproduce, but we had xargs at some point, can as well get it back.
I'm curious where do the trailing spaces come from...

Hey, this I reproduce, it doesn't happen anymore with a single job, but having 2 jobs and then switching directory causes the number to change to 3 😞

Very nice investigation! Can we also stop creating a subshell for jobs then (i.e. drop the parentheses), since we request pwd for each job anyway?

Yep. I will send a PR fixing this issue.


chore(deps): update terraform terraform-ibm-modules/powervs-infrastructure/ibm to v5.2.1

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/powervs-infrastructure/ibm (source)
module
patch
5.2.0 -> 5.2.1

Release Notes

terraform-ibm-modules/terraform-ibm-powervs-infrastructure (terraform-ibm-modules/powervs-infrastructure/ibm)
v5.2.1
Compare Source
Bug Fixes

remove upper limit for required terraform version (#867) (423e87c)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 3.0.0 :tada:
The release is available on:

GitHub release
v3.0.0

Your semantic-release bot :package::rocket:


AL0667: Replacement for RestoreArchiveData

Is there a new method for replacing RestoreArchiveData?
I'm a little confused as the standard documentation for upgrading extensions continues to reference this function.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions
'RestoreArchiveData' is being deprecated in the versions: '6.0' or greater. The features related to data migration from V1 to V2 extensions are being deprecated. This warning will become an error in a future release.AL(AL0667)

We need to update the documentation. What do you use RestoreArchiveData for? What are you trying to achieve?

Nothing more than retaining the data from our custom tables in "embed" upgrades. I understand this function is specifically for V1 to V2 but is there otherwise no specific code we need to have to make sure data from custom tables are retained during an upgrade?

Data is always retained for V2 extensions. The only case where data is removed is if you uninstall the extension and specify -DoNotSaveData or Sync-NavApp -Mode Clean.

Thanks, I'll remove any reference we have to this function.


XLSM Macro file is corrupted after using NPOI to read and write

F

trying to read and write data in XLSM format file using NPOI showing as corrupted

@tonyqus  any idea about this bug?

NPOI doesn't support keeping the built-in VBA module while reading and writing a xlsm file. You may have to check other library.


Demo refactoring

Hello, I'd like to have some feedback about this little refactoring I've done.
Nothing big, just grouped the application's logic in another class and defined some interfaces for a Gps position retriever.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- demo/src/main/java/com/eis/geoCalendar/demo/Behaviour/EventMapBehaviour.java  2
- demo/src/main/java/com/eis/geoCalendar/demo/Localization/LocationManager.java  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- demo/src/main/java/com/eis/geoCalendar/demo/Localization/LocationManager.java  4
- demo/src/main/java/com/eis/geoCalendar/demo/Behaviour/EventMapBehaviour.java  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 3

Complexity increasing per file
==============================
- demo/src/main/java/com/eis/geoCalendar/demo/Dialogs/RemoveMapEventDialog.java  1
- demo/src/main/java/com/eis/geoCalendar/demo/Localization/LocationManager.java  4
- demo/src/main/java/com/eis/geoCalendar/demo/Dialogs/AddMapEventDialog.java  1
- demo/src/main/java/com/eis/geoCalendar/demo/Behaviour/EventMapBehaviour.java  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- demo/src/main/java/com/eis/geoCalendar/demo/Dialogs/AddEventDialog.java  1
- demo/src/main/java/com/eis/geoCalendar/demo/Behaviour/EventMapBehaviour.java  2
- demo/src/main/java/com/eis/geoCalendar/demo/Dialogs/RemoveEventDialog.java  1
- demo/src/main/java/com/eis/geoCalendar/demo/Localization/LocationManager.java  4

See the complete overview on Codacy


Avro "imports"/"extends" is not working

Hi,
While trying to use Avro inheritance features, to include schema A within schema B, using extends and includes, the POJO's got created don't include the base class fields.
Use case:
base.avsc:
fields: [a1, ..., an]
child.avsc:
fields: [b1, ..., bn]
"includes": ["base.avsc"],
"extends": "base"
My expectation is the base class fields will be included within the child class, but that's not happening (checked the POJO created by the plugin for the child class).
Is that supported?
Thanks,
Roni

As far as I know, the Avro schema specification does not support inheritance.
https://avro.apache.org/docs/1.10.2/spec.html#schema_record
This plugin only supports capabilities provided by the Avro SpecificCompiler library provided by the Apache Avro project. So, to answer your question, no, I don't believe this is supported. You are welcome to add such support in your own fork if you wish.

Thanks for the reply.


chore: add ITS addresses

The API handles the address: 0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C (Interchain Token Service) automatically. So, we don't need to add it to the UI.


Redirect Loop when Browser has Blocked Third Party Cookies

Some users of our Angular SPA are stuck in a redirect loop during login, and it has been narrowed down to the browser settings blocking third party cookies. IdentityServer and SPA are hosted on two different domains.
Is there an alternative login flow or other suggestions to support users who choose to block third party cookies?
The root of the redirect loop appears to be the CheckSession IFrame not being able to read the idsrv.session cookie, which generates a new hash and silent refresh loop.
Here is the SPA's UserManager config:
authority: oidcAuthInfo.authority,
client_id: oidcAuthInfo.clientId,
redirect_uri: ${baseHref}auth-callback,
silent_redirect_uri: ${baseHref}silent-refresh.html,
post_logout_redirect_uri: ${baseHref}welcome,
response_type: 'code',
scope: openid profile ${oidcAuthInfo.apiName},
filterProtocolClaims: true,
loadUserInfo: true,
revokeAccessTokenOnSignout: true,
automaticSilentRenew: true

That's a requirement of how the OIDC specs work.

Is there any guidance around preventing the session management iframes from getting into a loop when third party cookies are blocked, in order to avoid avoid excess network traffic and/or page refreshes by end users?

Use the main window, not an iframe. Or use refresh tokens for renewal (but protect that: https://tools.ietf.org/html/draft-ietf-oauth-browser-based-apps-04#section-8).

iOS Safari has the setting "Prevent Cross-Site Tracking". It's turned "On" by default.
This applies to both iOS version 12.x and version 13.x.
But this redirect loop, for us, only happens on version 13.
Is this a known problem?
For us this fails in both a SPA application using old Angular/Knockout js, but it also fails in a fresh SPA application that uses React.
Both of the SPA's work with iOS 12.x, but on iOS 13.x there is a redirect loop.
Tried this: https://www.thinktecture.com/identity/samesite/prepare-your-identityserver/
But does not seem to help for this issue.

Solved this for now by setting
var isIOS = (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream;
automaticSilentRenew = !isIOS
monitorSession = false

@jcd79 I created a new issue with #1074 to track this. We are hitting the same thing with Safari.

I'm currently getting the same, but using Chrome, but not sure if it's the same thing

this is happening now with Chrome Version 83.0.4103.116 (Official Build) (64-bit) on incognito mode

Yep, that's how things are now.

How we can fix the above mentioned issue for chrome?

How we can fix the above mentioned issue for chrome?

You can't, not really.
I've written about the current workarounds/"solutions" I see (I'm an web app developer though, not an IDS expert), loosely based / using input from the excellent leastprivilege.com blogpost "SPAs are dead!? (who is I believe a colleague from brockallan, and they are IDS experts I'd say). Hope that helps. To summarize, the five main directions I currently see:

Serve IDS via a subdomain of your SPA's domain
Proxy your IDS for your SPA via the SPA's domain
"BFF" (Backend For Frontend) architecture, also mentioned by leastprivilege's blog
Use new Browser API's like the "Storage Access API" and inject its functionality in the client side library
Fall back to using Refresh Tokens (with appropriate extra security measures)
??? I surely have missed options.

None of the workarounds/solutions would involve changes to the client side libraries (except maybe 4, which is not as useful as it sounds because of browser support), as far as I can tell. All of them are about rethinking your architecture in varying degrees. For my current project we use option 1, which seems to work out with some tweaks here and there.

@jeroenheijmans I have implemented point 1 already. But still it doesn't work on chrome(iPhone)

Hi @jeroenheijmans
Thanks for your blog, it's a nice summary of solutions and tradeoffs.
If I understand correctly, all options other than 4, will establish an independent session from the main domain, right?
Meaning that session at identity.example.com and product.web will be independent from one another.
I'm interested in options that preserve SSO between both domains:

Option 4: Use new Browser API's like the "Storage Access API" and inject its functionality in the client side library
(not sure if can be implemented in Chrome)
Option 6: BFF architecture + disable Session monitoring + Back-channel Logout
see related info in session management spec

I'd appreciate any comments on this options or other viable options that preserve SSO.


Fix permissions in central service account to allow diagnostic bundle to retrieve pod data

Description
Currently, whe ncreating a diagnostic bundle, the central cluster will contain a errors.txt file with the following error message:
could not list pods in namespace "stackrox": pods is forbidden: User "system:serviceaccount:stackrox:central" cannot list resource "pods" in API group "" in the namespace "stackrox"

Before trying to retrieve any pod data (e.g. logs), we will first check if we can list pods in the specific namespace.
However, the service account of central, which will be used, does not have the permission to list pods within the stackrox-central-diagnostics
role.
This leads to the error during checking if we can list pods, as well as the errors.txt file being created.
This PR fixes the listed resources within the role.
Although we previously didn't announce any changes related to the service accounts RBAC, I've added a changelog to let customers know that the role now includes one additional resource.
Checklist

[ ] Investigated and inspected CI test results
- [ ] Unit test and regression tests added
[X] Evaluated and added CHANGELOG entry if required
- [ ] Determined and documented upgrade steps
- [ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

Testing Performed

Create a diganostic bundle
Ensure that within _central-cluster folder, no errors.txt is found and the log data is available for each pod.

Current dependencies on/for this PR:

master

PR #3394   👈

This comment was auto-generated by Graphite.

/retest

/retest

Test failures are infrastructure related (e.g. issues brining up the cluster), and the current change only applies to the Helm chart, so this can be ignored for this particular PR.


Lighthouse CI as Page Speed Insight

What's the purpose of this pull request?
Use the PSI config in our lhci
How it works?
looking at lhci in pull requests from stores
How to test it?
looking at lhci in pull requests in https://github.com/vtex-sites/marinbrasil.store/pull/270
References
https://github.com/GoogleChrome/lighthouse
https://github.com/GoogleChrome/lighthouse-ci
https://developers.google.com/speed/docs/insights/v5/about

@tlgimenes yes, I will make this.


Add a Gitter chat badge to README.md

platinumazure/eslint now has a Chat Room on Gitter
@platinumazure has just created a chat room. You can visit it here: https://gitter.im/platinumazure/eslint.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

This is a fork of eslint/eslint, so I'm not going to add a badge for my fork. Thanks!


cmd/compile: package-scope and function-scope types get the same name

This programs shows that we can get two different types with the same name.  This is permitted by the reflect package, but it seems unnecessarily confusing.  Should the compiler generate different names for these types?
package main

import (
	"fmt"
	"reflect"
)

type myint64 int64

func main() {
	var i1 myint64 = 100
	fmt.Printf("%T: %v\n", i1, i1)

	t1 := reflect.TypeOf(i1)

	type myint64 int32
	var i3 myint64 = 100
	fmt.Printf("%T: %v\n", i3, i3)

	t2 := reflect.TypeOf(i3)

	fmt.Printf("t1: %v %v\n", t1.Kind(), t1.String())
	fmt.Printf("t2: %v %v\n", t2.Kind(), t2.String())
	fmt.Println(t1 == t2)
}

Output:
main.myint64: 100
main.myint64: 100
t1: int64 main.myint64
t2: int32 main.myint64
false

@ianlancetaylor I need to warn you that you are treading into some messiness. Consider this:
package main

import "fmt"

type myint64 int64

const myi myint64 = 999
const myj myint64 = 999

func main() {
	var closure1 = func (i myint64) { fmt.Printf("i: %T: %v\n", i, i) }

	type myint64 int64 // Note that this is a DIFFERENT myint64 than the one up top.
	var closure2 = func (j myint64) { fmt.Printf("j: %T: %v\n", j, j) }

	closure1(myi)
	closure2(myj) // Cannot use myj (type myint64) as type myint64 in argument to closure2
	closure1(myint64(myi)) // Cannot use myint64(myi) (type myint64) as type myint64 in argument to closure1
	closure2(myint64(myj))
}

In the above example, there are two different types named myint64 which both refer to a int64, but closure1 can only take in the first type of myint64 and closure2 can only take in the second.
That's when they both refer to the same underlying type. Now consider what can happen if they refer to different underlying types:
package main

type myint64 int64

const myi int64 = 100
const myj int16 = 100

func main() {
	// This takes in the first kind of myint64 declared above.
	var closure1 = func (i myint64) { }

	type myint64 int16 // This is another kind of myint64.
	var closure2 = func (j myint64) { }

	closure1(myi) // Cannot use myi (type int64) as type myint64 in argument to closure1
	closure2(myj) // Cannot use myj (type int16) as type myint64 in argument to closure2
	closure1(myint64(myi)) // Cannot use myint64(myi) (type myint64) as type myint64 in argument to closure1
	closure2(myint64(myj))

	{
		// Let's try to call closure1 by redefining myint64 in an inner scope.
		type myint64 int64 // Oops, this int64 is different than the one that closure1 takes in!
		closure1(myint64(myi)) // Cannot use 'myint64(myi)' (type myint64) as type myint64
	}
}

It gets worse. Each inner scope can produce types declarations that have the same name (but different underlying Kind) than the declaration in the outer scope.  I think the issue is that the type of a variable (ex. myint64) doesn't actually tell you the Kind that the variable points to. Like you can have four different variables all of type myint64 and they can all have different Kinds. Maybe put the Kind in the type of the variable. Like instead of %T printing main.myint64, maybe main.myint64-int64, main.myint64-int32, main.myint64-int16, etc.
Either that or throw a deprecation warning at compile time if people declare a new type with the same name as an existing type.
Allowing the inclusion of -Kind would make it clearer what the underlying Kind is:
var i1 main.myint64-Int16 = 1
var i2 main.myint64-Int32 = 2
var i3 main.myint64-Int64 = 3
{ // Inner scope
  type myint64 struct{ s string }
  var i4 main.myint64-Struct = myint64{"hello"}
  var i5 main.myint64-Struct = struct{ s string }{"world"}
}

When it prints the % it can print the entire main.myint64-Int16 instead of just main.myint64 so you can see the Kind without having to do reflect.TypeOf(i1).Kind().

@ianlancetaylor This example below should not compile. It's too confusing. If two declared types have the same package, name, and Kind, they should be interchangeable or the code should not compile.
package main

import "fmt"

// This example should not compile. The two MyTypes should conflict.
func main() {
	type MyType int
	var closure1 = func (i MyType) { fmt.Printf("i: %T: %v\n", i, i) }
	{
		var myInt0 MyType = 100
		type MyType int // Note: this is a DIFFERENT MyType than the one above.
		var closure2 = func (j MyType) { fmt.Printf("j: %T: %v\n", j, j) }
		var myInt1 = 100
		var myInt2 MyType = 100 // This MyType is not the same as the MyType on myInt0.
		closure1(myInt0)
		// closure1(MyType(100)) // Cannot use 'MyType(100)' (type MyType) as type MyType
		closure2(100)
		// closure2(myInt0) // Cannot use 'myInt0' (type MyType) as type MyType
		closure2(MyType(myInt1))
		closure2(myInt2)
	}
}
/*
Output:
i: main.MyType: 100
j: main.MyType: 100
j: main.MyType: 100
j: main.MyType: 100
 */

I don't see why you say that Go's type system has holes.
Don't confuse the name of the type as printed by %T or as used by the reflect package with the actual type.  As the reflect documentation already says, there are cases where different types can have the same name (see the String method in https://golang.org/pkg/reflect/#Type).  This is what your example programs show.
Your example in https://github.com/golang/go/issues/38893#issuecomment-624684945 works as the language spec describes.  Each type MyType declaration introduces a new type.  The different MyType types are separate types that happen to have the same name.  Go permits names to be shadowed, and this is just an example of that.

"I don't see why you say that Go's type system has holes."

I misspoke. It's a little unintuitive is all.
Now before I continue, I'd like to take a little digression. Take this very mundane Go code snippet:
type Point struct {X int; Y int}

Coming from other programming languages like Kotlin and Scala, I expected that code to express the same intent as this code:
// Kotlin
data class Point(var X Int, var Y Int) { }

// Scala
final case class Point(var X Int, var Y Int) { }

That being said, after learning about type declarations, I now see that this Go code means something fundamentally different. What it means is that the type struct {x int, y int} is being assigned to a new, unique type (without modification to the original type). struct {x int, y int} and Point can be used to instantiate structs the same way as one another, but they produce different types (although casting between them is not necessary because struct {x int, y int} is not a defined type). If I did type Point = struct {X int; Y int}, that would mean something different.
With that in mind, let's take a look at this example code:
package main

import (
	"fmt"
	"reflect"
)

type MyInt int
var myInt MyInt = 1

/*
Note: I am expecting all the types in types to be different from one another.
 */
func main() {
	type MyInt int
	var types [5]reflect.Type = [5]reflect.Type{}
	types[0] = reflect.TypeOf(myInt) // Set types[0]
	var myInt MyInt = 1
	types[1] = reflect.TypeOf(myInt) // Set types[1]
	// Surprise: types[2] and types[3] are the same type.
	for i := 2; i < 4; i++ {
		type MyInt int
		var int0 MyInt = 1
		types[i] = reflect.TypeOf(int0)
	}
	{
		// Set types[4]
		type MyInt int
		var int0 MyInt = 1
		types[4] = reflect.TypeOf(int0)
	}

	var type0 = types[0]
	var type1 = types[1]
	var type2 = types[2]
	var type3 = types[3]
	var type4 = types[4]

	fmt.Printf("type0. Kind: %v, String: %v\n", type0.Kind(), type0.String())
	fmt.Printf("type1. Kind: %v, String: %v\n", type1.Kind(), type1.String())
	fmt.Printf("type2. Kind: %v, String: %v\n", type2.Kind(), type2.String())
	fmt.Printf("type3. Kind: %v, String: %v\n", type3.Kind(), type3.String())
	fmt.Printf("type4.  Kind: int, String: main.MyInt
type1. Kind: int, String: main.MyInt
type2. Kind: int, String: main.MyInt
type3. Kind: int, String: main.MyInt
type4.  Notice that when type MyInt int is inside of a loop it doesn't instantiate a new type for each iteration of the loop (even though it does for a similar non-loop scope). The type declaration behaves like a const static variable from the C programming language. Like if I jump over it with a goto it still gets defined and used sort of like a const static variable in C does. I haven't programmed in C since Operating Systems 101 and I found this behavior unexpected.
If your code compiles and you have one type declaration on line 10 and another one with the same name on line 20, everything between line 10 and line 20 with that name gets the first type and everything after line 20 gets the second type, regardless of the presence of loops, closures, goto, etc, and regardless of whether the two type declarations refer to the same Kind or different Kinds.
Oh, and then the compiler says "Cannot use type MyType as type MyType", and when you try to cast your variable to MyType you can't because your variable actually needs to be cast to the MyType on line 10, not the MyType on line 20, which isn't obvious from the error message.
At the very least type declarations should give their enclosing scope. The types are static so it shouldn't be super hard to get that information. Like if there is one MyType in package scope and another in function foo, the first could be package.MyType and the second could be package.foo.MyType. If it were in a closure assigned to a variable named bar it would be nice if it were package.bar.MyType instead of some long ugly anonymous lambda stacktrace name like package.$$Lambda$1/791452441.MyType, but then what about if the closure is anonymous and gets immediately invoked without being assigned? Even then going to the enclosing function would probably be better than package.$$Lambda$1/791452441.MyType.
Also, if the whole path with enclosing scope could show in the output of reflect.Type.String() and in the compiler error message, that would make things more intuitive. Less "which MyType is it talking about?" and no "I can't cast this because it's shadowed by some other MyType in another scope."
It's unintuitive, but I think that would be better.

" Like even in Scala I don't like when I do a type path or type projection for the type of a class inside another class (ex. AClass.BClass or AClass#BClass) and there are two classes with the same name inside of the outer class. In Scala it just grabs the one that is declared closest to the top, but I would prefer it if that sort of scenario couldn't come up in the first place."

Correction:
// These objects are singletons within singletons...
object Failure {
  {
    {
      object Failure {
        object Failure {
          def printFail(): Unit = {
            println("Failure at the top!")
          }
        }
      }
    }
    object Failure {
      object Failure {
        def printFail(): Unit = {
          println("Failure in the middle!")
        }
      }
    }
  }
  object Failure {
    object Failure {
      def printFail(): Unit = {
        println("Failure at the end!")
      }
    }
  }
}

object Main {
  def main(args: Array[String]): Unit = {
    // Guess what this line prints...
    Failure.Failure.Failure.printFail()
  }
}
/*
Output:
Failure at the end!
 */

Yeah, this is horrible, but at least you can access singletons within singletons and types within types in Scala (as long as they're not shadowed). In Go if a type was defined and used inside of a function and that function has been returned from, that type is totally inaccessible regardless of where in the function it was defined or whether it was declared exported or unexported.
I have no expertise whatsoever, but I like the idea of being able to access an exported, declared type via a unique path like: package.function.$closure.innerFunction.$scope.Type, where $closure is an unnamed closure, $scope is an unnamed scope, and Type is the declared type that I am referring to. If all the exported declared types had unique paths, that would be more intuitive. Then I could think of the types like being in a tree.

Getting back to @ianlancetaylor's original question:

Should the compiler generate different names for these types?

I don't see a need to. reflect.Type.String already warns that String has collisions from package names, and so reflect.Type values should be compared directly to test type identity.
I think we can wait until we have a report of a real-world use case where this would be useful.

@ianlancetaylor , would it be okay to bump this to Unplanned?

I think so, yes.

It's true that String says that the result may not be unique, but it strongly implies that this is because of package names, not because it will use the same string within a single package.
I think this should be in Backlog, not Unplanned, and I will change it accordingly.

I don't know if Name() necessarily needs to be unique (within a given package), but it would be nice to have some way of getting a unique name of a type, which isn't something that seems to be provided at all at the moment. (Currently struggling with mapping a type definition from an AST tree to a type obtained using reflection when the type is defined inside a function, since as far as I can see reflect.Type doesn't provide anything that could help with guessing the scope the type was defined in)

I think this issue is blocked waiting on the proposed user-visible changes. For example:
Why are unique strings needed? Why can't types.Type values be disambiguated directly with ==?
How should the strings be further disambiguated? How stable do the disambiguators need to be?
What changes need to be made to the reflect API? These will need to go through the proposal approval process.

Why are unique strings needed? Why can't types.Type values be disambiguated directly with ==?

In my case it's because I need to relate a reflect.Type to an ast.TypeSpec, so I can't compare them directly.

How should the strings be further disambiguated? How stable do the disambiguators need to be?

I just came across #55924 which seems relevant - having some way of accessing the link name for any type might just do the trick. Though that's assuming that the way the link name is constructed is documented and could be calculated deterministically from the AST of a package.
For some more context on my specific issue, given a reflect.Type or one of its fields, I would like to be able to look up the corresponding doc comment from the source code. Incidentally, if a link name (or whatever would be used here) was also generated for anonymous structs to help locate them in the source code, that would also make my life a lot easier. (I'm currently having to do a lot of bookkeeping to keep track of how anonymous structs are accessed.)


Expression TSV-file uploader (v.0.1).

Part of Narrative pipeline related to KBase feature values repo.

Looks to be in good order, merging.


Help Needed for to add where clause in user model

Laravel Version: 5.3.*
Voyager Version: 0.11.5
PHP Version: 5.6.25
Database Driver & Version: 5.7

Description:
Hello,
can anyone let us know how to add where clause in either User model or VoyagerBreadController ? we need to display only specific role users on page ?
Thanks!

This is Laravel functionality, not a Voyager issue.  Please read the Laravel docs.
To point you in the right direction, you need to look into query scopes.


conform to pep8

change syntax to be more conform with pep8

Outdated, but let’s keep formatting improvements in mind.


Font size on iPhone

I think the font size on mobile should be reduced to fit more games on the display and better alignment

Same is from desktop, it's just too big.
I would remove this font-size increase here: https://github.com/Starz0r/AreWeAntiCheatYet/blob/2426bc621270072c6a9824f0fac708d39b3b8988/src/layouts/default.vue#L29