Not an issue: Puca DSP support added to WLED-MoonModules!

WM8978 support for WLED AudioReactive has been on my to-do list for well over a year - and getting a few Puca DSP boards yesterday pushed me to finally do it:
https://github.com/MoonModules/WLED/pull/84
This should be merged in shortly, and I would expect it'll be accepted up to WLED "mainstream" in due time.
Currently it's set to do line-in with loopback/passthru to line-out, but I may eventually create a separate config for microphone input. I'm mostly working on line-in for audio reactive work as microphones aren't the ideal solution for accuracy in loud environments like DJ events, live performances, etc.
This is a great board, thanks for developing it! A huge improvement over the LyraT I've been targeting (and also added to WLED!)
My working tree is here if anyone wants to try it sooner: https://github.com/troyhacks/WLED/tree/WM8978

Thanks @troyhacks for adding the WM8978 support to WLED AudioReactive!
And also for the feedback on the PUCA DSP board, there are no documented hardware issues with it as far as I'm aware and it was fully tested during development, if you come across anything though please open an issue here as may be useful for other developers.


Feature Request - Add policy option to add s3 object lifecycle to buckets

As I was replacing our internal S3 tools with Cloud Custodian policies I noticed there isn't an option to apply an S3 bucket lifecycle in Custodian.  This would be a great policy option addition as it falls under the cost savings pillar of Custodian.  I would attempt to code this myself but have way too much going on this sprint.  Here is an example policy that I was thinking for adding a LifeCycle config to a bucket:
policies:
- name: apply-s3-lifecycle-policy
  resource: s3
  filters:
        - type: value
          key: "Lifecycle"
          value: null
  actions:
      - type: object-lifecycle
        prefix: "/"
        transition:
              - days: 180
              - storage_class: "STANDARD_IA"
        versionexpiration:
              - noncurrentdays: 35

As an enhancement down the road the ability to load the lifecycle config parameters via a json from s3 something like this:
policies:
- name: apply-s3-lifecycle-policy
  resource: s3
  filters:
      - type: value
        key: "Lifecycle"
        value: null
  actions:
      - type: object-lifecycle
        config_from: s3://bucketname/s3-lifecycle-config.json

Where the s3-lifecycle-config.json file contains something like this:
{
	"Rules": [
		{
			'ID': 'S3-LifeCycle-Policy',
			"Prefix": "/",
			"Status": "Enabled",
			"Transition": {
				"Days": 180,
				"StorageClass": "STANDARD_IA"
			},
			"NoncurrentVersionExpiration": {
				"NoncurrentDays": 35,
			}
		}
	]
}

#1635 addresses this

Merged


mod crashes when joining servers.

mod crashes when joining servers. ples fix or my modpack never work :(.

Hi, I cannot fix without a crashlog. I will need more information than that, thanks.
You can find your crashlogs in the crashlogs directory in your Minecraft folder.


[posix-trel] support TREL URL

This commit supports TREL URL (e.g. trel://eth0) for Posix.

This change here to use URL looks fine to me.
However, there is one point that makes me a bit uneasy for merging this. I'd like to ask that we postpone/delay merging this PR (which is related to TREL posix implementation) before we have added back some tests or at minimum some build checks in our CI for posix build with TREL enabled.
From issue https://github.com/openthread/openthread/issues/6472 and removal of ot-ncp (which also removed the related toranj test-cases that were covering TREL poisx build), I don't think we have  any CI converge for posix BUILD with TREL platform enabled. I think we need at least add back a CI build check under posix in which TREL is enabled (before we merge changes to the related code).

Another point on radio URL use to have in mind:

A radio URL so far has been used as a way to specify and configure a module that acts as a radio platform for OT core, i.e., a module that implements a radio driver and provides otPlatRadio APIs.
The TREL does not actually define and/or provide an otPlatRadio abstraction. It defines its own platform abstraction (which is way different from otPlatRadio definitions).  I think it is important to not think of TREL as a module that provides otPlatRadio APIs

A side-note: I know at first it may seem reasonable to think of multi-radio as having multiple implementations of otPlatRadio APIs but it does not really work and does not allow the behaviors we want from each PHY.
The reason for this is because otPlatRadio APIs are too low-level and very much tied to 15.4 PHY behaviors. The right point for handling multi-radio is at a higher abstraction layer (Mac layer turned out to be proper point for handling multi-radio and that's how it is implemented in our OT core implementation).

From issue #6472 and removal of ot-ncp (which also removed the related toranj test-cases that were covering TREL poisx build), I don't think we have any CI converge for posix BUILD with TREL platform enabled. I think we need at least add back a CI build check under posix in which TREL is enabled (before we merge changes to the related code).

This PR is required by https://github.com/openthread/ot-br-posix/pull/803. The very purpose of this PR is to enable TREL in OT Posix and ot-br-posix (i.e. otbr-agent) in a unified way, so that we can test TREL link in Border Router tests.

The TREL does not actually define and/or provide an otPlatRadio abstraction.

Indeed. However, using TREL URL does not necessarily means that the OT core should treat them equally. The purpose is just to provide a unified and extensible way of specifying radio links. For example, it's easy to extend the TREL URL to include parameters for future extension (e.g. trel::/eth0?desirable=false&use-mdns=true).

This PR is required by openthread/ot-br-posix#803. The very purpose of this PR is to enable TREL in OT Posix and ot-br-posix (i.e. otbr-agent) in a unified way, so that we can test TREL link in Border Router tests.

Having a test in ot-br-posix is good, but still I think we should at minimum have a build check in opethread CI itself as well (for posix build with TREL). It will be useful to make sure future changes/PR won't break the build
I will try to submit a PR to add such a check.

I will try to submit a PR to add such a check.

Thanks! That would be very helpful.

Any further comments on this PR? @bukepo @abtink

Any further comments on this PR? @bukepo @abtink

We need to wait for https://github.com/openthread/openthread/pull/6518 to be merged, then please rebase this PR on it (so we have some CI build checks covering posix TREL and chnaged in this PR).

Merge order tip: @jwhui

Merge this PR first
Merge openthread/ot-br-posix#803 with updated openthread repo


card with actionbar inside tabs

If i put the below example inside tab.  The action bar also take the tab color
http://ionicframework.com/docs/components/#card-showcase

Greetings @awebdeveloper!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @awebdeveloper!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Add explanatory comment to build-deb

After @dothebart pointed this script out I used it to build a package for Ubuntu 16.10. To do so I needed to figure out which packages needed to be installed and where the packages go after they are built.
I thought capturing those things in a comment might be helpful for others.
Let me know if I got the deps wrong.

Thanks ;-)


Config validation SHOULD return ValidationError(s)

Right now we only have one method to validate datadog config.
IsDataDogConfigValid() bool

which only returns a boolean when something is wrong. When using this to migrate old project to new library, I had to dig into the lib code, to understand what keys were missing.
My suggestion is implement:
Validate() (bool, error)

Which returns a set of validation error that are present in the datadog config.

Maybe the implementation SHOULD use https://github.com/hashicorp/go-multierror to return multiple errors.

This sounds like something we should implement. After releasing this function we should deprecate the old one in a later release.


Installing Qt on Ubuntu 12.04

I believe the guides for Debian/Ubuntu installation is outdated. Any updates?

This will be updated in the next major wallet release.


FeedAHelp: implement the following colors

primary: {
deep_orange: "#f6580b",
red: "#e92525",
gold: "#ffd700",
navy_Blue: #001F3F,
white: #ffff,
deep_green: #008000;

}
secondary: {
Dark Teal:"#1A535C",
Aquamarine:"#2A9D8F",
medium_gray: #cccccc
Terra_Cotta: #E2725B,
medium_dark_green: "#327832",
medium_blue: #0466C8;
light_yellow: "#ffff00",
Lime_Green: #32CD32,
Bright_Cyan: #00FFFF,
black: https://github.com/FeedAHelp/FeedAHelpless/pull/111;
}
tertiary: {
lightYellow: "#fff2b6",
lightOrange:" #fed8b1",
lightRed: "#fbc3bc",
lightBlue: "#b8e2f2",
lightTeal: "#b8edeb",
lightGreen: "#caffda",

}

Hero Section:
Background: Soft Sky Blue (#A9D9E2) to evoke a sense of tranquility and compassion.
Center Image Border: Golden Yellow (#FFD700) to highlight the central image.
Text: Charcoal Gray (#333333) for excellent readability against the light background.
Buttons: Warm Orange (#FFA500) for a call-to-action that stands out.
FeedAHelp Status Section:
Background: Soothing Green (#66BB6A) and Warm Yellow (#F7CA18) gradient to symbolize growth, hope, and positivity.
Text: Deep Green (#2C3E50) for legibility.
Progress Bars: Light Blue (#3498DB) and Light Pink (#FF6B6B) to represent progress and care.
Ingredient Search Component:
Background: Creamy White (#FDFEFE) for a clean and simple feel.
Search Box: Fresh Green (#27AE60) for a touch of freshness and vibrancy.
Button: Vibrant Green (#2ECC71) to encourage user interaction.
Search Results: Slate Gray (#95A5A6) for easy readability.
Deshi Menu Search Component:
Background: Warm Beige (#F0E68C) for a homely and inviting atmosphere.
Search Box: Terracotta (#E74C3C) to add an earthy touch.
Button: Rich Maroon (#C0392B) for a striking contrast.
Search Results: Dark Chocolate Brown (#5D4037) for clear visibility.
Footer Section:
Background: Soft Gray (#F5F5F5) to keep it light and neutral.
Text: Dark Charcoal Gray (#2C3E50) for readability.
Links: Royal Blue (#3498DB) for navigation, and Deep Red (#D35400) for important actions.


Add Docker support

Create a new docker image to standardize the environment.
I wasn't quite brave enough to book a refundable flight to fully test it out.  I have one next week to use it on.  Did test the email and that seems to all be working properly.
Installation:
Choose one:
a) Straight Docker
docker build -t southwest-checkin .
docker run -d  -e LUV_HEADERS_FILE='/home/swcheckin/data/southwest_headers.json' -e<EMAIL_ADDRESS>-e<EMAIL_ADDRESS>-e LUV_PASSWORD='supersecurepassword' -e LUV_SMTP_SERVER='smtp.email.com' -e LUV_PORT=587 southwest-checkin
b) Docker-Compose
edit docker-compose.yml with your SMTP variables
docker-compose up -d --no-deps --build southwest-checkin
Add check-in schedule:
Wait a minute or so for the header file to be created after starting the container:
docker exec -it <dockerproc> /bin/sh -c "autoluv schedule AAAAAA Fake Name<EMAIL_ADDRESS>

thanks for working on this! admittedly, i don't have the time right now to really test this. so for now i'm going to leave this unmerged and if people want to try it, they can install it from your branch.
i do think a docker image would greatly simplify things so it is something i want to explore in the future.

Just tested the container and I had some feedback.

By default the container doesn't run since runner.sh doesn't have the execute bit. There should be a chmod +x or similar in the Dockerfile.

> docker-compose up -d
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Removing southwest_checkin
Starting b422d0188270_southwest_checkin ... error

ERROR: for b422d0188270_southwest_checkin  Cannot start service southwest-checkin: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/home/swcheckin/runner.sh": permission denied: unknown

ERROR: for southwest-checkin  Cannot start service southwest-checkin: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/home/swcheckin/runner.sh": permission denied: unknown

Container currently runs as root, should have it run as a low privileged user.

The three characters should be randomly generated.

RUN sudo perl -pi -e 's/cdc_/swc_/g' /usr/bin/chromedriver

This part from runner.sh should probably just be included part of the Dockerfile.

## Setup gem
cd /home/swcheckin/southwest-checkin && \
gem install autoluv

I couldn't get email notifications working without this line: tls: true. We should probably have this as an ENV variable as well.

  PONY_OPTIONS = {
    from: "#{ENV["LUV_FROM_EMAIL"]}",
    via: :smtp,
    via_options: {
      address: "#{ENV["LUV_SMTP_SERVER"]}",
      port: "#{ENV["LUV_PORT"]}",
      user_name: "#{ENV["LUV_USER_NAME"]}",
      password: "#{ENV["LUV_PASSWORD"]}",
      authentication: :login,
      tls: true
    },
  }

Also, this didn't work for me for a reservation with two people.


Inactive subscriptions

(Not a bug a such, but a thought I would like to share for discussion)
The library persists a subscriptions array that is helpful in case of connection loss so we can keep the "state".
In some cases, we might want to remove certain entries from the array as they become obsolete.
For example, in the following flow:

Path find create request for A
Path find close request for A
Path find create request for B

Even if A is not longer a path we want to explore, the path_find request gets created and closed (before path find request B) on every reconnection meaning we will receive some path messages for it for a few seconds.

I considered this before, indeed, and to keep it simple I left it. But I agree. The best way to deal with this is to "diff" subscriptions and let 2 cancel out 1 if equal. This would be tricky (not impossible) when users e.g. subscribe to certain accounts and then unsubscribe to a part of them.

Would you like a PR for this?

Who would say no to that 🎉  PR for an issue/challenge/shortcoming/... is the dream of an open source maintainer :D


gRPC server & native log receiver

The gRPC server & log receiver is for receiving the logData in protocol v3.

LGTM. @EvanLjp Do you need anyone else to recheck?

I think it is enough to merge.

LGTM. @EvanLjp Do you need anyone else to recheck?

I think it is enough to merge.


Evaluate STIGging VM images for compliance

Benefit/Result/Outcome
Currently jumpboxes are deployed out of compliance with a number of the NIST control set but more importantly they are not STIG'd for DoD. There is currently market place items in all clouds for STIG'd linux and Windows VMs. These can be used on MLZ to reach compliance for DoD customers.
Description
These market place items are market place templates so they require the underlying VM template (with custom code extensions) to be extended to TF/bicep  to work in MLZ
Acceptance Criteria

Determine if STIGs are optional feature driven by a parameter, and which default?
Yes/No the work effort to incorporate into MLZ a parametrized set of STIG'd jumpboxes. Parameter for settings and switch for -applyStig.
If yes to above questions, create the backlog items (GitHub Issues) to represent the work to be done.

Customer responsibility.


Execution failed for task ':react-native-orientation:processReleaseResources'. > com.android.ide.common.process.ProcessException: Failed to execute aapt

I got this error, if I try to build an Realease-APK on Android:
Execution failed for task ':react-native-orientation:processReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

This is my build.gradle:
apply plugin: "com.android.application"

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true 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

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"

    defaultConfig {
        applicationId "de.skgEv.app"
        minSdkVersion 16
        targetSdkVersion 23
        versionCode 5
        versionName "1.1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    signingConfigs {
            release {
                if (project.hasProperty('SKG_RELEASE_STORE_FILE')) {
                    storeFile file(SKG_RELEASE_STORE_FILE)
                    storePassword SKG_RELEASE_STORE_PASSWORD
                    keyAlias SKG_RELEASE_KEY_ALIAS
                    keyPassword SKG_RELEASE_KEY_PASSWORD
                }
            }
        }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
	    	signingConfig signingConfigs.release
        }
    }
    // 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]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    compile project(':react-native-orientation')
    compile project(':react-native-video')
    compile project(':react-native-youtube')
    compile project(':react-native-vector-icons')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:22.0.1"
    compile "com.facebook.react:react-native:+"  // From node_modules
}

// 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.compile
    into 'libs'
}

this the package.json
{
	"name": "skgapp",
	"version": "1.1.0",
	"private": true,
	"scripts": {
		"start": "node node_modules/react-native/local-cli/cli.js run-android",
		"run emulator": "/home/suther/Android/Sdk/tools/emulator -avd Nexus5",
		"test": "jest",
		"lint": "eslint .",
		"lintFix": "eslint . --fix",
		"clean-start": "rm -rf ./node_modules && yarn install && npm start --reset-cache",
		"SASU_adb install android": "adb -s '0060472a0804' install -r android/app/build/outputs/apk/release/app-release.apk",
		"SASU_debugMenu on USB-Device": "adb -s '0060472a0804' shell input keyevent 82",
		"SASU_kill_MetroBundler": "lsof -i :8081 | grep node | awk '{print $2}'| head -1 | xargs kill",
		"react-native-debugger": "/usr/bin/react-native-debugger",
		"reactotron": "/usr/bin/reactotron"
	},
	"jest": {
		"preset": "react-native"
	},
	"dependencies": {
		"AsyncStorage": "^0.1.5",
		"babel-plugin-transform-remove-console": "^6.9.4",
		"prop-types": "^15.6.2",
		"react": "16.4.1",
		"react-devtools": "^3.2.3",
		"react-native": "^0.56.0",
		"react-native-communications": "^2.2.1",
		"react-native-elements": "^0.19.1",
		"react-native-orientation": "^3.1.3",
		"react-native-tab-navigator": "^0.3.4",
		"react-native-update-gradle": "^1.0.0",
		"react-native-vector-icons": "^4.2.0",
		"react-native-video": "^3.1.0",
		"react-native-video-controls": "^2.2.3",
		"react-native-video-player": "^0.9.1",
		"react-native-youtube": "^1.1.0",
		"react-navigation": "^2.11.2"
	},
	"devDependencies": {
		"babel-core": "^6.26.3",
		"babel-eslint": "^8.2.6",
		"babel-jest": "^23.4.2",
		"babel-plugin-jest-hoist": "^23.2.0",
		"babel-plugin-module-resolver": "^3.1.1",
		"babel-preset-react-native": "^5.0.1",
		"eslint": "^4.19.1",
		"eslint-config-airbnb": "^17.0.0",
		"eslint-import-resolver-babel-module": "^4.0.0",
		"eslint-plugin-import": "^2.13.0",
		"eslint-plugin-jest": "^21.18.0",
		"eslint-plugin-jsx-a11y": "^6.1.1",
		"eslint-plugin-react": "^7.10.0",
		"jest": "^20.0.4",
		"jest-react-native": "^18.0.0",
		"react-test-renderer": "^16.4.1",
		"reactotron-react-native": "^2.0.0"
	},
}

I only could solved it by setting : https://github.com/yamill/react-native-orientation/blob/master/android/build.gradle
to 27:
apply plugin: 'com.android.library'

android {
    compileSdkVersion 27
    buildToolsVersion "27.0.1"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
}

dependencies {
    compile "com.facebook.react:react-native:+"
}

any Idea, why the settings in /android/app/build.gradle not work for this module?
If I have project-build.gradle on 27 and keep your build.gradle like it was, it throws the above described error.

Maybe you could use a build.gradle like this to prevent such errors in future:
def _ext = rootProject.ext;

def _compileSdkVersion = _ext.has('compileSdkVersion') ? _ext.compileSdkVersion : 26;
def _buildToolsVersion = _ext.has('buildToolsVersion') ? _ext.buildToolsVersion : '26.0.2';
def _minSdkVersion = _ext.has('minSdkVersion') ? _ext.minSdkVersion : 16;
def _targetSdkVersion = _ext.has('targetSdkVersion') ? _ext.targetSdkVersion : 26;

android {
    compileSdkVersion _compileSdkVersion
    buildToolsVersion _buildToolsVersion

    defaultConfig {
        minSdkVersion _minSdkVersion
        targetSdkVersion _targetSdkVersion
        versionCode 1
        versionName "1.0"
    }
    lintOptions {
        abortOnError false
    }
}


Drop deprecated foldMap1Default

Description of the change
Drops deprecated foldMap1Default

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

:ping_pong: @thomashoneyman


[BUG] endless loop

Describe the bug
A new command to update FVM doesn't update

Expected behavior
Update performed
Logs
Please provide the verbose logs by running --verbose after the command.
Windows 11 Pro
FVM 3.0.1
https://github.com/leoafarias/fvm/assets/20865719/b0f3d762-057c-4161-b05d-0733ff7051ab

@TomaszCz This is most likely because it was installed using chocolatey, I have created a PR to add that in the env for a check


fix Failing SWA tests

This PR resolves []
Description

Fix failing SWA LP tests related to old designs

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Thanks a lot for this fix 👌
I wonder if we even need these tests anymore. Most likely these feature flags won't get disabled anymore 🤔

Thanks a lot for this fix 👌
I wonder if we even need these tests anymore. Most likely these feature flags won't get disabled anymore 🤔

@olerichter00 I think removing these tests will be part of the  upcoming cleaning up feature flags task


Landscape licenses are reflected incorrectly.

Some projects on https://landscape.finos.org/ are incorrectly displaying the "not open source" label. Such as https://landscape.finos.org/?selected=morphir that has the  "Apache-2.0 license" on GitHub as seen in the repository  https://github.com/finos/morphir and should thus have the correct "open source software" label.

@AndreyKozlov1984 are you able help with this?

I see that there are also other projects with the same issue, such as https://landscape.finos.org/?selected=regular-table

@TheJuanAndOnly99 - for now, please work around it, by setting the field license in the metadata descriptors, see https://github.com/finos/metadata/blob/dev/toplevel/curref-data/activity-metadata.json#L6
Since you're there, check all items in Landscape and update all items that are having this issue.
Thanks!

To Do:

[ ] JupyterLab Templates
[ ] Regular Table
[ ] Morphir
[ ] Legend

Fixed! TY @TheJuanAndOnly99

I can confirm that license is the proper way to specify the proper license of the project. We rely on GitHub API for the repo_url but it may fail to detect the license properly

Thanks @AndreyKozlov1984 . Thing is that at the moment we see in the Netlify logs that a lot of GitHub API calls are failing:
5:53:56 PM: Fetching github entries
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-go)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/regular-table)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-rust)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-editor)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-scala)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-service)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/jupyterlab_templates)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-examples)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-bosque)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-dotnet)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-elm)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir-jvm)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-sdlc-server-operator)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-engine-server-operator)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-studio-operator)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-gitlab-integrator)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-community-delta)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/morphir)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-persistence)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-libs)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-bundle)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-juju-db-operator)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-integration-morphir)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-integration-juju)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-depot)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-integration-helm)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-engine)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-pure)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-sdlc)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-studio)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend-shared)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/legend)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-aws-cfi-sqs)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-aws-cfi-lambda)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-azurerm-cfi-postgresql)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-aws-cfi-redshift)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-aws-cfi-dynamodb)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-azurerm-cfi-aks)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-google-cfi-gke)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/ansible-cfi-ocp)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/cfi-terraform-template-child-module)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/compliant-financial-infrastructure)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/terraform-aws-cfi-eks)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/devops-automation)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/ScreenShareIndicatorFrame)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/ScreenSnippet2)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/SymphonyWindowsHwndHelper)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/SwiftSearch)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/ScreenSnippet)
5:53:56 PM: Attempt #1 (Status Code: 401) (URI: https://api.github.com/repos/finos/SymphonyElectron)
5:53:56 PM: .......................FFFFFFFFFFFFFFFFFFFFFFF.......FFFFFFFFFFF........F.....FF
5:53:56 PM: FFFFFFFFFFFFF

Any reason for this to happen?

I am going to add one more Github API key. It is a rate limit.


BWT-422: Change the HTML decode library for the staff portal to 'he'

Jira Ticket:
BWT-422
Jira Ticket URL:
https://bcparksdigital.atlassian.net/browse/BWT-422
Description:
Changed the HTML decode library from html-entities (newer library) to he (older library) due to a bug impacting "Kun⨱alas Heritage Site/Conservancy".  The bug impacts the ⨱ (timesbar) entity and the name gets rendered as "Kun×bar;alas Heritage Site/Conservancy"
You can see the bug by searching for "Kun" in the "Select a Park" search field on this page....
https://staff.bcparks.ca/bcparks/dashboard

I accidentally based my branch off Natalia's branch instead of basing it off main. I fixed it and did a force push so my PR just has my changes now


Issue with running baseline model for speaker diarization

I have tried running the baseline model, after completion of scoring first pass diarization on DEV, the code automatically stops without any error

The same issue I am facing. Have you found the solution

Can you please check if exp/displace_diarization_nnet_1a_dev_fbank/per_file_rttm dir has been created? If this  is not there then there is some problem executing the step "# Perform first-pass diarization using AHC."

I am facing same issue and exp/displace_diarization_nnet_1a_dev_fbank/per_file_rttm has been created.

Can you please check if inside your "dev_set_folder/data" there should be file named final.rttm? Also check if you have write permissions in the folder. Thanks

try commenting set -e -u -o pipefail in score_diarization.sh


yarn and npm repositories contain incorrect versions

Both npm and yarn repositories contain (and will install) incorrect versions for datatables.net
npm info datatable.net
Output:
...
versions:
   [ '1.10.9',
     '1.10.10',
     '1.10.11',
     '1.10.12',
     '1.10.13',
     '1.10.14',
     '1.10.15',
     '2.1.1' ],
...

yarn info datatable.net
Output:
...
  versions:
   [ '1.10.9',
     '1.10.10',
     '1.10.11',
     '1.10.12',
     '1.10.13',
     '1.10.14',
     '1.10.15',
     '2.1.1' ],
...

Tried cleaning the cache of both yarn and npm with no improvement.
Because yarn and npm think 2.1.1 is a valid version, it gets installed when providing a version constraint like >=1.10.9.

Thanks for letting me know about that. I must have tagged it by mistake - darn. I'll mark that version as deprecated and update here when done.

Any update on this ? I'm still facing the issue.

Sorry. I'm going to get it fixed early next week.

Contacted npm support and will let you know what the story is. The "version" for npm is correctly at 1.10.15, so it would be good if npm and yarn used that, but 2.1.1 is marked as deprecated and it would be good if it wasn't used at all.

I've just tried creating a little dummy package:
{
  "name": "xxtmp",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "datatables.net": ">=1.10.15"
  }
}

Running npm install will correctly install 1.10.15 and not 2.1.1. 2.1.1 is marked as deprecated, so it looks like npm (correctly) ignores this.
Can you tell me how you have npm configured that it is installing 2.1.1?

I created this repo (https://github.com/fabsb/datatables-poc) trying to reproduce this issue.
Tried with fresh installs of yarn and npm via brew on my macOS Sierra.
$ yarn versions
yarn versions v0.27.5
{ http_parser: '2.7.0',
  node: '8.3.0',
  v8: '6.0.286.52',
  uv: '1.13.1',
  zlib: '1.2.11',
  ares: '1.10.1-DEV',
  modules: '57',
  openssl: '1.0.2l',
  icu: '59.1',
  unicode: '9.0',
  cldr: '31.0.1',
  tz: '2017b' }
Done in 0.03s.

$ npm version
{ npm: '5.3.0',
  ares: '1.10.1-DEV',
  cldr: '31.0.1',
  http_parser: '2.7.0',
  icu: '59.1',
  modules: '57',
  node: '8.3.0',
  openssl: '1.0.2l',
  tz: '2017b',
  unicode: '9.0',
  uv: '1.13.1',
  v8: '6.0.286.52',
  zlib: '1.2.11' }

As you can see from the npm branch eventually npm installs version 2.1.1. This seems to only occur after running npm update
With yarn there is actually a warning when installing for the first time and lockfile does not exist.
$ yarn install
yarn install v0.27.5
info No lockfile found.
[1/4] Resolving packages...
warning<EMAIL_ADDRESS>Packing error
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
Done in 1.08s.

As you can see from the yarn branch, even after the first install (here) version 2.1.1 gets installed for datatables.net.
$ cat node_modules/datatables.net/package.json
{
    "name": "datatables.net",
    "version": "2.1.1",
    "description": "DataTables for jQuery ",
    "files": [
        "js/jquery.dataTables.js"
    ],
    "main": "./js/jquery.dataTables.js",
    "keywords": [
        "filter",
        "sort",
        "DataTables",
        "jQuery",
        "table",
        "DataTables"
    ],
    "homepage": "https://datatables.net",
    "bugs": "https://datatables.net/forums",
    "license": "MIT",
    "author": {
        "name": "SpryMedia Ltd",
        "url": "http://datatables.net"
    },
    "dependencies": {
        "jquery": ">=1.7"
    },
    "repository": {
        "type": "git",
        "url": "https://github.com/DataTables/Dist-DataTables.git"
    }
}

I hope this helps.

Perfect - thanks! I've created a new issue on npm which discusses this issue.

Deprecation does not have any effect on installability. Use ^1.10.15 instead of >=1.10.15 as the specifier instead. All deprecation actually does is generate a warning when someone installs that version, and that's exactly what it's intended to do.

I probably should have been a better community member and reported this and offered the same solution as @zkat a few weeks ago, but I have been just discarding the chunk from my lock file any time I run yarn upgrade and then running yarn to link the correct package before I compile.

see https://github.com/yarnpkg/yarn/issues/4176 for more background of why its using the "wrong" version.

I've proposed a solution at https://github.com/DataTables/Dist-DataTables-Bootstrap/pull/2

@DataTables when you pushed out the fix for this I think this package was missed https://github.com/DataTables/Dist-DataTables-FixedHeader. It is still using >= for datatables.net.

Thanks for spotting that! I'll grep them all tomorrow and make sure they are all correct.

Realised what the issue is. I set it up to update the deps whenever I tag a version of the extensions (to keep their version correct as well as also resolving this issue). I've not tagged FixedHeader and a few extensions yet. I'll get that done and it should resolve itself when done. I should get that done this afternoon.

Can you please update the package datatables? The packages datatables.net, datatables.net-bs do not contain the current code for bootstrap v4.

No, but the datatables.net-bs4 package does :).

Good to know. A note in the Readme.md would be nice there to find what package. ;-)

Fair point. It is highlighting on the download page, but I'll add information about the styling packages to the read me as well.


Implement wallet functions

Features

Added gas fee config
Implemented sendToken, delegate, undelegate and collectAllRewards functions
Introduced cosmos query client

based on #51
refs #55

plz rebase

@chihimng updated :adore2x:

@hochiw i pushed some commits to rename the make functions to newXXX 🙏


change the translation of the term Resolves to "Résout" for fr-FR.md

translation a word "Resolves" to "Résout" in the model Fr_FR.md

+1.
The document recommends to use the same language.


The confusion of running Python script on tagui

hey, I have a Python script(ocr.py), as shown in the picture below. When it runs alone, there is no problem at all. It will call local OCR to recognize the verification code and then return it to the clipboard.

When I combine it with tagui, it doesn't work. I have tried wrapping it with pybegin and pyfinish. But every time it reaches the position shown in the picture, it completely stops.

I have also tried using the following commands to call it.
run python37 ocr.py
run cmd python37 ocr.py
run ocr.bat
etc
Either it will also get stuck, or it will be executed without any feedback. I really don't know where the problem lies. If it's convenient, please help me. Thank you very much

I noticed a GBK encoding issue in tagui_py.log, so I deleted the Chinese comments in the Python script and it can continue. However, there are still issues. I'm wondering if this is related to the presence of multiple Python scripts on my computer at the same time. The default is python313, but my local OCR is all using python37

Hi @KennGuo look for the tagui/src folder there is the tagui.cmd file. Inside there are references of python command. I think u just need to modify it to invoke the right python.

Yes~I find it.
rem start python process if integration file is created during parsing if exist "tagui_py\tagui_py.in" (         start "Python Engine" /min cmd /c python -u tagui_py\tagui_py.py 2^>^&1 ^| tee -a tagui_py\tagui_py.log )
Change python to python37. Thanks a lot.


Feature request: safe shutdown

For all kinds of purposes I'd like to have a stop() method that:

Prevents new items from being queued (enqueueing should reject with an error given as argument to the stop method)
Waits for all running items to finish
Rejects all queued items with a predefined error (given as argument to the stop method)
Resolves when all that is done

This would allow disposing of my queue e.g. when the system is stopped in a controlled manner.
Also very handy for ensuring everything stops when a unittest fails.

I like this idea a lot. I've been experimenting with different types of shutdowns and none met all needs. I'm going to combine your suggestions with the ones from #60. It will take an options object that will let you do exactly what you're describing above. Intentionally failing running jobs is another common use case that needs to be supported.
I should have a prototype for you shortly, would you be interested in trying it out and providing feedback before it is released?

@SGrondin sure I would like to try it! Just let me know.
The shutdown as I described it is quite common in a-synchronous systems. I use it a lot and it works well.

I just realized that there may be cases where you'd want to run the queue empty, i.e. instead of step 3 one might want to just finish all queued items.  I guess that should be an option for the stop() method then.

Yup, that will bee an option.

For my own planning, what is the status and planning for this issue?

No I'm not at the moment

This took a lot of work to get right, but I think the end result is a flexible and elegant solution that should meet most people's needs.
It will be released as v2.5.0 soon, but you can currently try it on this branch (fully tested!):
npm install --save git://github.com/SGrondin/bottleneck.git#limiter-stop
Use it like this:
limiter.stop(options)

stop() takes an optional options object:

dropExisitingJobs (boolean, default true). Drops everything that's not currently executing.
dropError (Error object), error used to reject waiting jobs.
enqueueError (Error object), error used reject jobs added after stop() has been called.

stop() returns a promise that resolves once all waiting jobs have been dropped (if using dropExistingJobs) and once all the executing jobs have completed.
Feedback would be greatly appreciated.

v2.5.0 has been released with the new stop() method. 🎉 😄 Feedback is appreciated!

Sorry I didn't have a look at it in time @SGrondin, I've been too busy lately. Thanks for your efforts and it looks good!

No worries! If you end up trying it out, I'd really appreciate to hear what you think of it, even if it takes months. Whether it's good or bad, I take it into account.

I'm getting an error when running
 this.limiter.stop({}).then(() => {             console.log("Shutdown completed!")         }).catch((error) => {             console.log("ERROR", error)         });

Look at the docs for stop: https://github.com/SGrondin/bottleneck#stop
In the table, you'll see that if dropWaitingJobs is true, then all waiting jobs will be dropped with the message This limiter has been stopped.
If you want to wait for the jobs to complete, then pass dropWaitingJobs: false in the options object here: limiter.stop(options)


checkpatch.sh: add check gerrit Change-Id support

Summary
Add check gerrit Change-Id support, issue an error when a Change-Id line is encountered.
Impact
Testing
Test this patch with Change-Id firstly.

It works in the first patch with change id as the check failed:
../nuttx/tools/checkpatch.sh -g 3b5914f57b91e7d0ff50d15e5a53079d59535b57..HEAD
Remove Gerrit Change-ID's before submitting upstream
Error: Process completed with exit code 1.
I'll force push update without change id to pass check.


Minor UI fixes

@RocketChat/android
Few minor UI changes:

Darker time stamp label color
Close status view if user goes back to the chat screen
Show loading animation when joining an empty DM or channel
2FA input text field has focus on start

@leonardoaramaki Is it ready to merge?


Tests for export/import index and blobs

39892321a removed the tests because they should be a separate test and because the es part fails on elasticsearch v6.8.3 due to some concurrency issue.

done in integration tests


train my dataset

If I collect my dataset, I can train it with the code.

yes，you are right
来自GitHub小程序客户端：


Avoid applying copy-in-before/copy-out-after to all images

Currently we apply a given -copy-in-before or -copy-out-after flag to every -image specified. For example:
https://github.com/ALSchwalm/transient/blob/fbb41075fe2c725276b7b1ddd5686b9bebb624cd/transient/transient.py#L164-L169
This is surprising behavior. For now, it is probably ok to copy only to the first -image. In the future, we may expand the syntax to allow a user to specify which disk, but that will be a separate issue. The current behavior is almost certainly not desired, though, so changing it to be only the first disk will resolve this.

Also, the documentation should be updated to reflect any change made as a part of fixing this.

Could you please assign this to me - Thanks!


Emoji characters break the table layout

extension
v0.6.0

VS Code
v1.41.0

OS
macOs  v10.15.7

Seems like an emoji character is counted as 2 characters :)

@pitizzzle
It is an emoji font issue, same as microsoft/vscode #100730. (https://github.com/microsoft/vscode/issues #100730)
(Sorry for that the link is broken. Correct link is to be a mention to the issue. I thought that it's not good.)
This extension treats emoji characters as 3 times wider character, but it's still not displayed in the exact width.

Hey @takumisoft68. Nice to hear that you already know what's going on.
Would you say this is unfixable? Or what would you suggest to do with this issue here.

No idea.
If you create a new emoji monospaced font, that might work...

I mean if you want to close this GitHub Issue, because the emoji problem is not your concern, or if you rather want to keep it open.
For me this is done here. Thanks for the quick reply and pointing out to the related VS Code thread! <3

The only workaround I could find is adding a zero-width-space character before/after the emoji. Obviously it is invisible because it has no width, but you could copy it from down or visit this page to copy it by clicking the Copy button.
--


Is it possible to add text to the link between 2 nodes?

Thank you for taking the time to report an issue with react-d3-tree!
Feel free to delete any questions that do not apply.
Are you reporting a bug, or opening a feature request?
Feature Request
Is it possible to add text to the link between 2 nodes

i think no.
+1 need for me

I'm also looking for a library that provide this feature.
The TreeLinkDatum contains only two properties which are the source and target Node so I don't think it is possible yet.
https://bkrem.github.io/react-d3-tree/docs/interfaces/_src_types_common_.treelinkdatum.html
Does anyone have an idea on how to add this feature easily or can recommend another library that can customize the text on a link ?

I'm also looking for a library that provide this feature.
The TreeLinkDatum contains only two properties which are the source and target Node so I don't think it is possible yet. https://bkrem.github.io/react-d3-tree/docs/interfaces/src_types_common.treelinkdatum.html
Does anyone have an idea on how to add this feature easily or can recommend another library that can customize the text on a link ?

have you find any library that can add text between the prent and child node?

I'm also looking for a library that provide this feature.
The TreeLinkDatum contains only two properties which are the source and target Node so I don't think it is possible yet. https://bkrem.github.io/react-d3-tree/docs/interfaces/src_types_common.treelinkdatum.html
Does anyone have an idea on how to add this feature easily or can recommend another library that can customize the text on a link ?

have you find any library that can add text between the prent and child node?

try this https://github.com/reaviz/reagraph


How do you process data for nuscenes or other LiDAR segmentation dataset?

Considering that those point clouds are sparse, how do you guys process or maybe divide the data into smaller parts and pass it to the network? Are there any resources that I can refer to learn more about the LiDAR point cloud pre-processing.
Thanks in Advance.

Hi, maybe you can refer config here (https://github.com/Pointcept/Pointcept/blob/main/configs/nuscenes/semseg-spunet-v1m1-0-base.py)
Any questions are welcome. (no need to divide into smaller parts, only 10,000 level points, SpUNet, PTv2, or PTv3 can directly handle them)


Authorization forbidden via graphql

Describe the bug
It seems there is no way to query apiVideoAssets via strapi's graphql endpoint as it results in 'Forbidden Access'.
To Reproduce
I have followed the steps here  in order to access the api-video-asset endpoint via the rest api. This works as expected.
Next setup the the graphql plugin with the configuration as follows:
'use strict';

const { join } = require('path');

module.exports = ({ env }) => ({
  graphql: {
    config: {
      endpoint: '/graphql',
      shadowCRUD: true,
      playgroundAlways: false,
      federation: true,
      apolloServer: {
        introspection: true
      },
      artifacts: {
        schema: join(__dirname, '..', 'schema.graphql'),
        typegen: join(__dirname, '..', 'types.d.ts'),
      },
    },
  },
});

This generates the graphql schema for strapi and includes api.video types such as:
type ApiVideoUploaderApiVideoAsset {
  createdAt: DateTime
  description: String
  hls: String!
  iframe: String!
  metadata: JSON
  mp4: String!
  player: String!
  tags: JSON
  thumbnail: String!
  title: String!
  updatedAt: DateTime
  videoId: String!
}

Using Insomnia or an equivalent hit strapi's graphql endpoint (http://localhost:1337/graphql) with the following query:
{apiVideoUploaderApiVideoAssets{data{attributes{videoId}}}}

This results in Forbidden access:
{
    "errors": [
        {
            "message": "Forbidden access",
            "extensions": {
                "error": {
                    "name": "ForbiddenError",
                    "message": "Forbidden access",
                    "details": {}
                },
                "code": "FORBIDDEN"
            }
        }
    ],
    "data": {
        "apiVideoUploaderApiVideoAssets": null
    }
}

I have also tried adding the same API bearer token which is needed for auth via the rest endpoint (mentioned in the final step of the blog post linked above). This still results in the same forbidden response.
Expected behavior
Expect data to be returned as queried.

I have figured this out, instead of creating a custom API token as in the aforementioned blog, I have created a "full access" token (although I'm unsure if this is best practice?).
This being said an official guide to this would be great - something like this (sorry to mention a competitor!)


Type compatibility error in loop

Godot version:
45d3b965bb55f3111478306070034ed18e8fa5e4
OS/device including version:
Windows 10
Issue description:
The error 'Parser bug (please report): Trying to check compatibility of unset value type' is printed when passing an i variable of a loop into the float function.
Steps to reproduce:
Launch attached project
Minimal reproduction project:
type_compatibility.zip

All these are related to this one: #45139 & #44375
I can confirm it when typing this on my script:
func project_ray() -> void:
	var cam:Camera3D = $Gizmo/Camera3D
	var from = cam.project_ray_origin(mouse_pos)
	var to = from + cam.project_ray_normal(mouse_pos) * 1000
	var result = get_world_3d().direct_space_state.intersect_ray(from
	,to, [self])

In the reproduction project, the p_source (= i) is not set, which means its kind variable is still unresolved when using it in the call.
The i variable type should in fact be guessed from the for i in rang(0,1): expression but it is currently not.
In GDScriptAnalyzer::resolve_for, there is even a TODO comment about this:
	// TODO: If list is a typed array, the variable should be an element.
	// Also applicable for constant range() (so variable is int or float).

Can't reproduce on current master.


Go client formatting is whack; consider running gofmt

As of fa49ffc20, the formatting of the generated Go client is, for the lack of a better word, whack. Indentation is all over the place, with some lines being indented way too deep, and others not being indented at all.
I do not remember this being an issue before. Did we use to pipe the output through gofmt? Or did typescript templates behave differently in the past, stripping certain leading whitespace? At any rate, the status quo is a big no. We're looking at code like this:

This has been already fixed in the latest version (1.27.0).


file service

What this PR does / why we need it (변경 내용 / 필요성):
file service
Which issue(s) this PR fixes (관련 이슈):

#129

https://github.com/kuoss/lethe/pull/132


Warnings during feature extraction

When running examples/classifiers/wrn_gru_mesa.py, I noticed several warnings during extract_features():

sleepecg/sleepecg/feature_extraction.py:363: RuntimeWarning: HR analysis window too short for estimating PSD for feature VLF. 3030.3s required, got 270s
  warnings.warn(msg, category=RuntimeWarning)
sleepecg/sleepecg/feature_extraction.py:225: RuntimeWarning: Mean of empty slice
  meanNN = np.nanmean(NN, axis=1)
sleepecg/sleepecg/feature_extraction.py:226: RuntimeWarning: All-NaN slice encountered
  maxNN = np.nanmax(NN, axis=1)
sleepecg/sleepecg/feature_extraction.py:227: RuntimeWarning: All-NaN slice encountered
  minNN = np.nanmin(NN, axis=1)
sleepecg/.direnv/python-3.10.9/lib/python3.10/site-packages/numpy/lib/nanfunctions.py:1878: RuntimeWarning: Degrees of freedom <= 0 for slice.
  var = nanvar(a, axis=axis, dtype=dtype, out=out, ddof=ddof,
sleepecg/sleepecg/feature_extraction.py:232: RuntimeWarning: Mean of empty slice
  RMSSD = np.sqrt(np.nanmean(SD**2, axis=1))
sleepecg/.direnv/python-3.10.9/lib/python3.10/site-packages/numpy/lib/nanfunctions.py:1217: RuntimeWarning: All-NaN slice encountered
  r, k = function_base._ureduce(a, func=_nanmedian, axis=axis, out=out,
sleepecg/.direnv/python-3.10.9/lib/python3.10/site-packages/numpy/lib/nanfunctions.py:1583: RuntimeWarning: All-NaN slice encountered
  result = np.apply_along_axis(_nanquantile_1d, axis, a, q,
sleepecg/sleepecg/feature_extraction.py:244: RuntimeWarning: Mean of empty slice
  cvSD = SDSD / np.nanmean(SD, axis=1)
sleepecg/sleepecg/feature_extraction.py:244: RuntimeWarning: divide by zero encountered in divide
  cvSD = SDSD / np.nanmean(SD, axis=1)
                                                                                sleepecg/.direnv/python-3.10.9/lib/python3.10/site-packages/numpy/lib/nanfunctions.py:1095: RuntimeWarning: All-NaN slice encountered                    | 12/1970 [00:06<15:03,  2.17it/s]
  result = np.apply_along_axis(_nanmedian1d, axis, a, overwrite_input)
                                                                                sleepecg/sleepecg/feature_extraction.py:252: RuntimeWarning: invalid value encountered in sqrt                                                           | 23/1970 [00:12<17:47,  1.82it/s]
  SD2 = (2 * SDNN**2 - SD1**2) ** 0.5
                                                                                sleepecg/sleepecg/feature_extraction.py:256: RuntimeWarning: divide by zero encountered in divide                                                        | 32/1970 [00:16<15:35,  2.07it/s]
  CSI = SD2 / SD1
sleepecg/sleepecg/feature_extraction.py:257: RuntimeWarning: divide by zero encountered in log10
  CVI = np.log10(SD1 * SD2 * 16)
                                                                                sleepecg/sleepecg/feature_extraction.py:244: RuntimeWarning: invalid value encountered in divide                                                       | 1166/1970 [10:26<07:01,  1.91it/s]
  cvSD = SDSD / np.nanmean(SD, axis=1)
sleepecg/sleepecg/feature_extraction.py:254: RuntimeWarning: invalid value encountered in divide
  SD1_SD2_ratio = SD1 / SD2
sleepecg/sleepecg/feature_extraction.py:256: RuntimeWarning: invalid value encountered in divide
  CSI = SD2 / SD1

Are these warnings problematic? Should we take a closer look and try to fix them? Or if they are OK, how do they influence the results (is a feature nan e.g. when a division by zero occurs)?

Those warnings occur for analysis windows where there are no heartbeats (or just heartbeats with equal distances, voiding some statistical measures), in which case the resulting feature value is nan. We should be able to avoid them by removing those windows from NN before calculating the features (and just directly set the respective entries in the feature matrix to np.nan). Features with value nan are masked in prepare_data_keras, so this does not influence the classification.

Alternatively, we could also catch (and silence) those warnings if there is nothing to warn about. Which solution would you prefer?


ABFRealmSearchViewController

Hey!
I wanted to build a map with realm. I tried the tutorial on realm ( clustered map view ) and on github (https://github.com/bigfish24/ABFRealmSearchViewController).
Actually, I have a bug when I build the projects:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_RLMRealmConfiguration", referenced from:
      type metadata accessor for __ObjC.RLMRealmConfiguration in Utilities.o
  "_OBJC_CLASS_$_RLMSortDescriptor", referenced from:
      type metadata accessor for __ObjC.RLMSortDescriptor in FetchRequest.o
  "_OBJC_CLASS_$_RLMRealm", referenced from:
      type metadata accessor for __ObjC.RLMRealm in ChangeLogger.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Build Active Architecture only is on No.Downloading dependencies
Versions:
cocoapods-0.39.0
RBQFetchedResultsController (2.5)
Realm (0.97.0)
RealmSwift (0.97.0)
SwiftFetchedResultsController (2.5)
TOWebViewController (2.2.1)
Please, let's me know if you know how fix it!
Thanks

It seems like for some reason your project isn't properly linked to the Realm framework target, but that shouldn't be possible if everything goes fine with CocoaPods.
Have you tried to clean your build folder / delete derived data and build again from scratch? If that doesn't help, I'd encourage you to reset the CocoaPods integration. You might want to use the cocoapods-deintegrate plugin for that purpose and just re-run pod install and try building again. This can fix issues if you have changed the way how you integrate. If that shouldn't still help, can you show us your full podfile?

I would like to thank you, I reseted the the CocoaPods integration and after running pod install, everything goes right. By the way great tutorial on the iOS Clustered Map View with Realm.

Thanks for reporting back and the nice feedback. Good to hear that and have fun working with the components.


Added context around why use componentDidMount

I wanted to give some context around why we recommend using componentDidMount to make API calls and why we do not use the constructor, for instance.

I can't imagine this is needed anymore so I am closing it.


replace num_entries with limit for resource history API

Current dependencies on/for this PR:

main

PR #399   👈

This stack of pull requests is managed by Graphite.


feat(sdk): don't require client_id in the auth token

This isn't a claim that is in any spec, except for token exchange drafts
Instead we should allow the roles specified in the token to dictate access to resources.

Given that roles and groups are optional (at least with Keycloak they must be mapped) it would seem that we should utilize jq to allow the platform admin to validate any aspect of the claim. If they want to check for a client_id, role, group, etc then they could.
I assume we can add this kind of enhancement latter. Should we create an issue?

Given that roles and groups are optional (at least with Keycloak they must be mapped) it would seem that we should utilize jq to allow the platform admin to validate any aspect of the claim. If they want to check for a client_id, role, group, etc then they could.
I assume we can add this kind of enhancement latter. Should we create an issue?

I think we can add something to validate custom claims at a later time once someone maybe brings us a valid use case.


Update LS simulator to simulate delete operations

Description:
Right now, the LS simulator workflow only adds content to a source file. Need to update it to remove content from a source file. Especially imports and etc.
Describe your problem(s)
See description
Describe your solution(s)
Need to update the design to support deletion operations

Closing this as a low-priority task with the Icebox label might reopen in the future.


String writing using different  values for each row is extremely slow

Just change the benchmarking code BM_WriteStrings a little bit. Original code:
std::deque<XLCellValue> values(colCount, "OpenXLSX");

for (auto _ : state)    // NOLINT
    for (auto& row : wks.rows(rowCount)) row.values() = values;

Changed code:
for (auto _ : state)    // NOLINT
    for (auto& row : wks.rows(rowCount)) {
        std::deque<XLCellValue> values(colCount, std::to_string(row.rowNumber()));
      row.values() = values;
    }

The code becomes so slow that the benchmarking is not finished after a few minutes. Similar modification to BM_WriteIntegers causes no problem. In practical, it's rare that different rows share the same value. Thus the library behaves much slower than claimed in the doc when there are a lot of strings in the excel file. In my case, writing a file with ~20000 rows, 3 columns (all string) takes 40 seconds.
By attaching the process with gdb I find that it seems to be doing a lot of string comparisons to avoid creating duplicate string nodes in the xml file. With m_stringCache being a std::deque, the performance becomes unacceptable when the number of strings increases. Is it possible to use std::set?
(gdb) bt
#0  0x0000562cb653402e in std::operator==<char> (__rhs="8396", __lhs="82284")
    at /usr/include/c++/9/bits/basic_string.h:6152
#1  OpenXLSX::XLSharedStrings::<lambda(const string&)>::operator() (__closure=<synthetic pointer>,
    s="8396")
    at /home/lijing17/Developer/lireplay/webserver/third_party/openxlsx/OpenXLSX/sources/XLSharedStrings.cpp:74
#2  __gnu_cxx::__ops::_Iter_pred<OpenXLSX::XLSharedStrings::getStringIndex(const string&) const::<lambda(const string&)> >::operator()<std::_Deque_iterator<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char>&, std::__cxx11::basic_string<char>*> > (__it=..., this=<synthetic pointer>)
    at /usr/include/c++/9/bits/predefined_ops.h:283
#3  std::__find_if<std::_Deque_iterator<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char>&, std::__cxx11::basic_string<char>*>, __gnu_cxx::__ops::_Iter_pred<OpenXLSX::XLSharedStrings::getStringIndex(const string&) const::<lambda(const string&)> > > (__pred=..., __last=..., __first=...)
    at /usr/include/c++/9/bits/stl_algo.h:120
#4  std::__find_if<std::_Deque_iterator<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char>&, std::__cxx11::basic_string<char>*>, __gnu_cxx::__ops::_Iter_pred<OpenXLSX::XLSharedStrings::getStringIndex(const string&) const::<lambda(const string&)> > > (__pred=..., __last=..., __first=...)
    at /usr/include/c++/9/bits/stl_algo.h:162
#5  std::find_if<std::_Deque_iterator<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char>&, std::__cxx11::basic_string<char>*>, OpenXLSX::XLSharedStrings::getStringIndex(const string&) const::<lambda(const string&)> > (__pred=..., __last=..., __first=...)
    at /usr/include/c++/9/bits/stl_algo.h:3970
#6  OpenXLSX::XLSharedStrings::getStringIndex (this=this@entry=0x7ffd521afa98, str="82284")
    at /home/lijing17/Developer/lireplay/webserver/third_party/openxlsx/OpenXLSX/sources/XLSharedStrings.cpp:74
#7  0x0000562cb65342bd in OpenXLSX::XLSharedStrings::stringExists (this=this@entry=0x7ffd521afa98,
    str="82284")
    at /home/lijing17/Developer/lireplay/webserver/third_party/openxlsx/OpenXLSX/sources/XLSharedStrings.cpp:84
#8  0x0000562cb6508882 in OpenXLSX::XLCellValueProxy::setString (this=this@entry=0x7ffd521afaa8,
    stringValue=0x7ffd521afb00 "82284") at /usr/include/c++/9/bits/char_traits.h:300

theres a small tweak which can be done to XLCellValue.cpp to skip the shared strings, which helped in my case:
https://github.com/troldal/OpenXLSX/issues/241#issuecomment-2000082534


fix #45 : Psalm integration

see #45

@weierophinney @Ocramius
can you check this please?
Thanks!


Use a random port in cmd/prometheus tests

There are a few tests that will run prometheus command. This can test if there's already something listening on port :9090 since --web.listen-address defaults to <IP_ADDRESS>:9090. To fix that we can tell prometheus to use a random port on loopback interface.

This seems convenient, thanks! I think there are a few more places where the random part should be added in order to have no failing tests because of port conflicts:
https://github.com/prometheus/prometheus/blob/6dbf677122501adac4ac09d664aafe4aa4a0da8e/cmd/prometheus/main_test.go#L124
https://github.com/prometheus/prometheus/blob/6dbf677122501adac4ac09d664aafe4aa4a0da8e/cmd/prometheus/main_test.go#L379
https://github.com/prometheus/prometheus/blob/6dbf677122501adac4ac09d664aafe4aa4a0da8e/cmd/prometheus/main_test.go#L406

I only modified tests that were failing when I had Prometheus running.
Updated to cover tests you mentioned.

Thanks!

I only modified tests that were failing when I had Prometheus running.

Huh, the ones I suggested were also failing when I tested. Thanks for fixing anyway!


Fix/adapters 2

Some more fixes to adapters

Create adapters before the StackXCoder, to ensure no accidental duplication
Prevent LoRA adapter from taking wrapped layer as its child
Flag --log_model_structure for debugging architecture issues

I'm really not into type hints when declaring vars

I've configured nvim to do linting and type checking automatically, and in most projects I aim for zero type checking errors (in mammoth, this is far from the case). I've developed a habit of type hinting a lot because of this.

If you want to enforce typehinting in this project, I think you'd need to incorporate the relevant testing in the actions workflow


[EUWE] Charge volume types

EUWE backport of BZ:https://bugzilla.redhat.com/show_bug.cgi?id=1375506
Replacement of schema change ManageIQ/manageiq-schema#93 is usage of Reserve table here: 91a4b06
cc @gtanzillo
@miq-bot assign @simaishi
Links
https://bugzilla.redhat.com/show_bug.cgi?id=1375506
https://github.com/ManageIQ/manageiq/pull/16264
Replacement of schema change https://github.com/ManageIQ/manageiq-schema/pull/93 is usage of Reserve table here
https://github.com/ManageIQ/manageiq/pull/16277
https://github.com/ManageIQ/manageiq-ui-classic/pull/2496
https://github.com/ManageIQ/manageiq/pull/16321

CI failure is not related to this PR.

@lpichler, @simaishi Is there another BZ for this for Euwe? This BZ above has a target release of 5.9. These are a lot of changes (including using the reserves table in place of schema changes) to be back porting to an older version. Just trying to understand the priority of this.

The request to backport came in an email, but I'm actually not sure if this is still needed... I'll double check.

@gtanzillo yes it is this https://bugzilla.redhat.com/show_bug.cgi?id=1375506. and flags has been changed in this BZ. I think the priority for 5.7 has been set in comment 13. and under comment 28.
And I was asked by @chrispy1 for this backport.
Currently, I cannot not say if this should go 5.7.

closing this PR as it is not requested for 5.7 already.


Update README.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:

An unexpected error has occurred, could you please contact admins. Your RequestID: 093adfc1-0980-4853-9f6c-f7246256b159


Support for Management APIs

Hello,
Im currently exploring the capabilities of the API for Asset management. I would like to know whether the library supports programmatically creating assets using Management APIs, specifically in JavaScript.
Thank you!

Hi @deeptipotdar9, this library is for use with C#/.NET, not JavaScript.


DCO adapter not showing up in ipconfig

I upgraded to OpenVPN 2.6 and my connection was failing. Disabling DCO allowed the VPN to connect. After some debugging I discover the DCO adapter was visible in the Device Manager, Control Panel Network Adapters, but not in ipconfig /all.
Initially I thought it was because OpenVPN Interactive service was crashing each time I started the VPN, but that seemed to be caused by block-outside-dns after it failed to configure the interface. Commenting out block-outside-dns stopped the service from crashing.
I ended fixing the adapter not showing up in ipconfig, by uninstalling OpenVPN and uninstalling Sonicwall Global VPN Client, reboot, then reinstalling OpenVPN.
I'm not sure this is a bug in the adapter, but figured it might help some else who might be having the same or similar problem.

Are you saying interactive service crashes with block-outside-dns if Sonicwall Global VPN Client is installer?

@lstipakov yes the interactive service was crashing in the following situation:

Sonciwall Global VPN Client installed, but not running.
OpenVPN config was attempting to use the DCO adapter
block-outside-dns was in the client config.
The DCO adapter was missing from ipconfig.

If I commented out block-outside-dns and the other 3 conditions still applied, the service would not crash. But the VPN connection would not work since it never completed setting up the interface.

I was able to replicate the issue by:

uninstalling openvpn
installing sonicwall
installing openvpn

Here is what I found in the event viewer regarding the openvpnserv.exe crash:
Fault bucket<PHONE_NUMBER>744968023, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: openvpnserv.exe
P2: <IP_ADDRESS>
P3: 63d14fc1
P4: fwpuclnt.dll
P5: 10.0.19041.2486
P6: 871f7448
P7: c0000005
P8:<PHONE_NUMBER>00a908
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B64.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BB3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BD4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BD2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BF2.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_openvpnserv.exe_bb227d4147eb3611c7436f44e71a93142d21db0_613f2746_dd7091db-bf79-4448-9e8b-f7e266d0a063

Analysis symbol:
Rechecking for solution: 0
Report Id: ba797b67-0cd2-43a9-8bae-ff03ca1648f5
Report Status: 268435456
Hashed bucket: 278bffa4208dda63048db633f5031357
Cab Guid: 0

Here is the log file ovpn-sonicwall-otc.log

@oyarzun Thank you, I was able to reproduce the issue with DCO adapter being semi-functional when Sonicwall client is installed. I will look into that. Meanwhile could you check if this workaround works for you?

in Control Panel, go to DCO adapter settings and on the "Network" tab uncheck "DNE LightWeight filter"

So we have two issues here:

compatibility between Sonicwall filter driver and DCO driver, which will be handled in this issue
access violation in interactive service, to be handled in separate issue

in Control Panel, go to DCO adapter settings and on the "Network" tab uncheck "DNE LightWeight filter"

Thanks, I can confirm that this works around the issue.

Will close when I005 is published.

Fixed in 2.6.0-I005.


No replacement for autosync=False

It looks as though autosync has been removed in in the drive towards zero config.
However, it would be great if there was a flag or similar to disable automatic remote interactions. I (and I'm sure others) like to tell my machine when to talk to the internet.
E.g., would something like gopass --no-sync ... be possible? Then I could alias gopass=/usr/bin/gopass --no-sync.

This is a valid request. We did drop the old autosync to reduce the config complexity but did miss out on some use cases.
Essentially we're still trying to come up with a versatible but easy enough config format (like git configs) that covers all of our use cases.
Failing that we might add a (hidden) flag as a temporary measure.

Much appreciated; thank you! :pray:

Seconding this. I don't mind the automatic syncing, but I was accomplishing this with a cronjob already; the autosync interrupting normal operations with gopass is fairly obnoxious and a way to disable autosyncing would be great.

Makes sense. If y'all are OK with a flag that might get dropped (or rather: turned into a no-op) once we have a proper config handler in place that'd be easy to fix.
The proper fix, i.e. rewriting our config handling, will take some more time. The main concern here is that it's pretty disruptive and we need to try really hard to get it right on the first try (and provide & test migration tooling).

That would be a perfectly acceptable stopgap solution for me.

Same here!

Thank you very much @dominikschulz

@stefanv You're welcome. This was a lot of work. If you could give the 1.15.0-rc2 (or later) a try that would be much appreciated.


Fix win dll not loading

Fixes bug: #8 Nuget package does not copy native libraries to build output on Windows

Change csproj parameters to pack dll into nuget package.
Change DllName to "tesseract53.dll" in TesseractApi.cs to point to output dir (Same with leptonica)
Change windows dlls to be copied to output directory when building project (so works with new DllName)

Fixed in v1.0.6


Nested results of collect are Objects, not Array?

Hello fellow graphers
Say I have 2 node types, Product and Image
Product can have multiple Images
I want to get a list of Products, each having a property (sub-element) containing all of its Images
If the data structure is like so:
MERGE (p:Product {name: "Raygun"})
MERGE (p)-[:HAS_IMAGE]-(i:Image {url: "http://image1.com"})
MERGE (p)-[:HAS_IMAGE]-(i2:Image {url: "http://image2.com"})

My cypher is like
MATCH (p:Product )
OPTIONAL MATCH (p)-[]->(i:Image)
RETURN ({
name: p.name, images: COLLECT(i)
}) as product

The results from Neo4j REST API have "images" as an array, as might be expected (this is exactly what I want) e.g.
{ name: 'Raygun',
images: [
  {url: 'http://image1.com'},
  {url: 'http://image2.com'}
]

However, the results from Seraph have "images" as a dict keyed on index, like
{ name: 'Raygun',
images: {
  "0": {url: 'http://image1.com'},
  "1": {url: 'http://image2.com'}
}

Which version of Seraph are you using?

Sorry - 0.11.2

Could you try updating to 0.11.3 and trying again?

It worked! Thanks Jon

No worries, it was only just fixed :)


Custom entrytypes: inheritance of valid field types

I am using  Biber 2.14 in tool mode. When declaring a new datamodel configuration in a user configuration file (see biber.conf below) then a new entrytype (xyz) does not inherit valid field types (e.g. FILE) from the main biber-tool.conf file but vice-versa: existing entries see new fieldtypes:
biber --tool --validate-datamodel data.bib
> WARN - Datamodel: Entry 'doe' (data.bib): Invalid field 'file' for entrytype 'xyz'

I guess this is a bug and not a design decision?
data.bib
@xyz{doe,
	author = {Doe, J.},
	title  = {Someting important},
	file   = {doe.pdf},
}
@bibnote{miller,
	abc = {some info},
}

biber.conf
<?xml version="1.0" encoding="UTF-8"?>
<config>
	<datamodel>
		<entrytypes>
			<entrytype>xyz</entrytype>
		</entrytypes>
		<entryfields>
			<entrytype>xyz</entrytype>
			<field>author</field>
			<field>title</field>
		</entryfields>
		<entryfields>
			<field>abc</field>
		</entryfields>
		<fields>
			<field fieldtype="field" datatype="literal">abc</field>
		</fields>
	</datamodel>
</config>

It is a bug, thank you for reporting it. I am going to overhaul the datamodel merging code anyway and will update here when done. Should be this weekend.

Biber DEV 2.15 should fix this which is now on Sourceforge. The datamodel customisation has been improved so that additions/modifications through the .conf file should now all work properly. If you with to delete something from the default datamodel or heavily modify the default datamode, use the new --no-default-datamodel option and supply a complete datamodel.

Thanks! This bug of the MWE is indeed fixed. However, I will probably define my own datamodel and use --no-default-datamodel. I have defined custom inheritance rules and they still mess up parsing.
Background (only read if you care...): I created some custom types event, poster, talk and journal.  poster, talk shall inherit via crossref from event (e.g. title will be inherited as eventtitle,location,...) while articles can inherit from journal (e.g. title shall be inherited as journaltitle, issn, shorttitle,....).


Complete the page with

The print screen on the page show that we should add + Chrome :
Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Chrome")
The reference of +chrome is not take into accountin the command after this sentence :
In AD FS configuration, add a user agent string for Chrome on Windows-based platforms:
.. command should be completed

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

ID: abf9cb6e-38be-d28e-6ad3-1151b7e1a379
Version Independent ID: 3eed2746-fc1e-b7c3-ea04-203291aec098
Content: Configuring intranet forms-based authentication for devices that do not support WIA
Content Source: WindowsServerDocs/identity/ad-fs/operations/Configure-intranet-forms-based-authentication-for-devices-that-do-not-support-WIA.md
Product: windows-server
Technology: ad-fs
GitHub Login: @billmath
Microsoft Alias: billmath

I was looking around for some documentation to support your suggestion, mostly because I feel more confident about making the change if I can back it up with official documentation showing that the suggested change is correct. Then I noticed the following search result:
Chrome Phasing out Support for User Agent (March 24, 2020)

https://www.infoq.com/news/2020/03/chrome-phasing-user-agent/

Does this information have any effect on the suggested change, or is it peripheral as in Not Yet implemented?

I was looking around for some documentation to support your suggestion, mostly because I feel more confident about making the change if I can back it up with official documentation showing that the suggested change is correct. Then I noticed the following search result:
Chrome Phasing out Support for User Agent (March 24, 2020)

https://www.infoq.com/news/2020/03/chrome-phasing-user-agent/

Does this information have any effect on the suggested change, or is it peripheral as in Not Yet implemented?

Don't get me wrong, I am very interested in making necessary changes, whenever needed. I simply prefer to know that the change can be referenced properly.

Don't get me wrong, I am very interested in making necessary changes, whenever needed. I simply prefer to know that the change can be referenced properly.

#assign:IngridAtMicrosoft

Thank you for submitting this issue.  Unfortunately, due to high volumes I was unable to respond to this in a timely manner.  At this point, I am going to close this due to it's age and the possibility that it may have been addressed.  If this is still a problem, please consider submitting a new issue.  Thank you.
#please-close


computing image mean

I recall, from version 1 of Cxxnet, that there was a utility for creating the .bin for the image mean; I can iterate through the dataset, compute the mean image, save it as a jpg, and then convert it with ./bin/im2rec, but I was wondering if there was a utility to do this that I missed in the documentation?

On the subject of preprocessing, I'm currently getting some sort of memory allocation I issue I don't understand when  trying to read my own train/test .rec files:
mxnet.base.MXNetError: [21:18:51] src/storage/./cpu_device_storage.h:48: Check failed: (ret) == (0) Allocation failed

My train.lst looks like this (all images are 1024x1024x3):
0	222	w_7812.jpg
1	44	w_4598.jpg

I create the train/test records like so:
./bin/im2rec train.lst /home/user/Desktop/train/ train.rec

and everything seems to work fine. My iterators are defined as follows:
train_dataiter = mx.io.ImageRecordIter(
    path_imgrec="train.rec",
    rand_crop=False,
    rand_mirror=True,
    data_shape=(3,1024,1024),
    batch_size=64,
    preprocess_threads=1)
test_dataiter = mx.io.ImageRecordIter(
    path_imgrec="test.rec",
    rand_crop=False,
    rand_mirror=False,
    data_shape=(3,1024,1024),
    batch_size=64,
    preprocess_threads=1)

And the remainder is just a truncation of the Cifar10 network example
data = mx.symbol.Variable(name="data")
conv1 = ConvFactory(data=data, kernel=(3,3), pad=(1,1), num_filter=96, act_type="relu")
in3a = SimpleFactory(conv1, 32, 32)
in3b = SimpleFactory(in3a, 32, 48)
in3c = DownsampleFactory(in3b, 80)
in4bb =mx.symbol.Dropout(in3c)
in4c = SimpleFactory(in4bb, 80, 80)
in4cc= mx.symbol.LeakyReLU(in4c)
in4d = SimpleFactory(in4cc, 48, 96)
pool = mx.symbol.Pooling(data=in4cc, pool_type="avg", kernel=(7,7), name="global_pool")
flatten = mx.symbol.Flatten(data=pool, name="flatten1")
fc = mx.symbol.FullyConnected(data=flatten, num_hidden=447, name="fc1")
softmax = mx.symbol.Softmax(data=fc, name="loss")

gpus=mx.gpu(0)
model=mx.model.FeedForward(ctx=gpus,symbol=softmax,num_round=2,learning_rate=0.05,momentum=.9,wd=0.0001,initializer=mx.init.Uniform(0.07))
model.fit(X=train_dataiter,eval_data=test_dataiter,epoch_end_callback=mx.callback.Speedometer(64))

Hmm, this could due to the allocation of too large memory chunk being requested. Can you check what was the size being requested on your side https://github.com/dmlc/mxnet/blob/master/src/storage/cpu_device_storage.h#L47

I can check when I get home; is the output of posix_memalign produced at some point in the run?  I'm not entirely clear on how to check the size of the request.

You can change this line https://github.com/dmlc/mxnet/blob/master/src/storage/cpu_device_storage.h#L48 to
  CHECK_EQ(ret, 0) << "Allocation failed, " << "requested size = "<< size;

Do I need to recompile anything?

Yes, you will need to rebuild libmxnet.so, and re-install the python.

It was trying to allocate 73 GB, and I cap out at 32 GB; I'm somewhat surprised, though, as it only looked like it was taking up 16 GB when I loaded them all as numpy arrays.  I suppose  I'm going to have to do segmentation instead of trying to feed them in as is; thank you for the diagnostic help.
Re: the original question, is there an existing tool for computing the image mean, or do I need to build that utility?

The image iterator will automatically calculate/load mean file if you set mean_file=mean.nd. Personally, I set mean_r=117, mean_g=117, mean_b=117 instead of such a mean file. There is no performance hurt.

Is there a GPU equivalent line for the requested CPU memory? Just to make sure I could get it working, I resized all my images to 256x256; even with a batch size of 2, it's throwing
mxnet.base.MXNetError: [10:57:24] src/storage/./gpu_device_storage.h:39: Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading CUDA: out of memory

The fully loaded 256x256 takes up 1.6 GB or so of CPU RAM, and my GPU is a titan X, so it seems unlikely that it genuinely can't find the memory for that.  I've also tried converting to greyscale (1x512x512), although it seemed to have difficulty loading it.

There is no limit on how much memory to get. As everything is cutting the edge of memory, maybe you can check the memory requested, maybe the input size is indeed too large for this configuration(it was used for cifar, which means it expects a small input size). Try to use the one for imagenet, which might solve your probem

I am going to close this for now as the original question of mean image get answered, please feel free to re-open this if there is future questions.

@antinucleon Could you please detail "The image iterator will automatically calculate/load mean file if you set mean_file=mean.nd."? How to write an image iterator to have such functionality?
    train_dataiter = mx.io.ImageRecordIter(
        path_imgrec = args.data_dir + "train.rec",
        data_shape  = data_shape,
        batch_size  = args.batch_size,
        rand_crop   = True,
        rand_mirror = True,
        shuffle     = True, # Note that it will only shuffle in the batch!
        num_parts   = kv.num_workers,
        part_index  = kv.rank)

Besides, will the mean_image or mean_r, mean_g, mean_b also be conducted on the validation and testing data? The document says that they are only augmentation parameters.

Put this line in your training ImageRecordIter (call it what you want, put it where you want)
mean_img           = "../recordIO_dir/mean.bin"
Its not there to start.  But when you fit your model it will be created for you.  (I think after the first epoch but am not positive).  Then when the validation set is run its there and used, same with your test set.

Yeah, Put mean_img="path/to/mean.nd". If the file does not exist, ImageRecordIterator will first create this file and calculate mean value, store result in the file. And then start training. Detail can be seen in file "iter_image_recordio_2.cc", the new version of recordio data iterator under "mxnetRoot/src/io/iter_image_recordio_2.cc". Maybe from line 216, the Normalize init and the CreateMeanImg function.


JEQB 85: Configure QKD connection

This PR provides configurable QKD address connection

@MagisterLeon @kostiask for reference - this is how example address is parsed:

(provided flag was http://<IP_ADDRESS>:8000/alice/etc/QmSk5HQbn6LhUwDiNMseVUjuRYhEtYj4aUZ6WfWoGURpdV)


Add Gamera spectral model example

Hello everyone,
this PR contains an example of how to use the Gamera source modelling tool to fit spectra in gammapy.
There are essentially two ways, one is to subclass SpectralModel with a GameraSpectralModel, the other to use a TemplateNDSpectralModel
One Problem with this is that gamera is not pip installable, therefore the notebook can't just be run after installing the environment from the env.yml, it requires the extra installation of gamera. A link to the installation info i in the notebook, but of course this is not ideal. Do you have any other suggestions for how to deal with this?
Also, are there any figures you would like to see added to this notebook?

@registerrier and @gschwefer I agree making pip install work with Gamera would be very helpful (see https://github.com/libgamera/GAMERA/issues/6)

@adonath @registerrier We are trying to make that happen.
It should already work with:
pip install git+https://github.com/maxnoe/GAMERA@scikit-build

@adonath @registerrier We are trying to make that happen.
It should already work with:
pip install git+https://github.com/maxnoe/GAMERA@scikit-build

This is really cool @maxnoe !
I have first run mamba install gsl swig in a gammapy conda environment.
Then when calling pip install git+https://github.com/maxnoe/GAMERA@scikit-build, I have an error with:
 CMake Error at /private/var/folders/p2/l2vqhn_17zbghwxxwwdnvk0m0000gn/T/pip-build-env-nc41s2nw/normal/lib/python3.10/site-packages/cmake/data/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
        Could NOT find GSL (missing: GSL_INCLUDE_DIR GSL_LIBRARY) (found version
        "2.7.1")

I tried to set the env variable but it did not work. Any idea?

For compiling things in the conda env, also install the compilers package and make sure to deactivate / reactivate the env.
That makes sure everything is setup correctly for libraries to be found.

For compiling things in the conda env, also install the compilers package and make sure to deactivate / reactivate the env.
That makes sure everything is setup correctly for libraries to be found.
Side note: swig is not needed in the conda env, it's only a build time dependency and is installed in the build env automatically.

Thanks. It worked!


Request to correct the location of days-alive.py file

When I made a commit of my days-alive.py program two days ago, I did not place the python file in the right place.
I would like to correct this problem.

I'll make the change.


Uncaught TypeError: $.peekABar is not a constructor

Thanks for this library, unfortunately I can't seem to be able to show the notification.
I put the js in the footer, just under jquery - does it need to be on top?

It needs to be included after jQuery. How are you instantiating the library? You can try the following two ways:
var bar = new $.peekABar(options);

or
var bar = $.peekABar(options);

Thank you for the follow up. I'm using var bar = new $.peekABar(options);

Here's a JSFiddle for your troubles: https://jsfiddle.net/kunalnagar/97v165pd/


Can't go to Collection detail when import account

Describe the bug
Can't go to Collection detail when import account
Account : bc1pmvplws9v2f0rp6q9s36mlfy8yxhtvsqq38g6nygar6ze8cg67jqsnd5rpx

Log :

Version test : http://<IP_ADDRESS>:8900/s/MQ2arXyA2YTJ423
Validation passed in case :

Install/Update version


Discrepancy in the bc5cdr ner model output for different spacy versions and different OS

I have identified a discrepancy in the entities detected by the "en_ner_bc5cdr_md-0.5.1" model between results obtained from a Windows system and an Ubuntu system. According to the readme file of the "en_ner_bc5cdr_md-0.5.1" model, it is trained up to Spacy version 3.5.0. Interestingly, this alignment holds true for the Windows system. Whenever I adjust the Spacy version to a value above 3.5.0, the named entity recognition (NER) results are no longer produced. The model en_ner_bc5cdr_md-0.5.0 worked irrespective of the spacy version.
However, an interesting scenario emerged when I conducted the same experiment on an Ubuntu system. Here, the "en_ner_bc5cdr_md-0.5.1" model generated NER outputs regardless of the Spacy version I employed. I even tested it with versions like 3.6.1 and even lower than that.
This leads me to the question: Why is this discrepancy in behavior occurring between the Windows and Ubuntu systems? Is this a known issue? Am I missing something??

I don't know why there would be a discrepancy between Ubuntu and Windows, but using versions of spacy that are not supported by a model is undefined behavior.


Alternative way to directly parse a sorted list of frames for each calibration type

This is a feature that comes as one of the to-do tasks of this parent issue about EM-gain, k-gain and non-linearity: https://github.com/roman-corgi/corgidrp/issues/226
The task is:
Include an alternative way to directly parse a sorted list of frames for each calibration type.
Marie has decided that I would first work on implementing the sorting algorithm and its unit tests: https://github.com/roman-corgi/corgidrp/issues/231 and https://github.com/roman-corgi/corgidrp/issues/232

Can't we do this manually, with a recipe that species each individual file we want to include in the input dataset, and in the order we want them?
Or is this specifically to handling it in the EM-gain/kgain/non-lin code?

This is specifically for the EM-gain/kgain/non-lin code. You (Jason) suggested this idea. Maybe to keep some flexibility, and also in case some constraints change and the sorting algo is not adequate (?). I'm fine with whichever way you choose. Let me know

Sure, I agree flexibility is good. I'm just not sure what new we need to add here for this.

I think your suggestion is all what is needed: "a recipe that species each individual file we want to include in the input dataset, and in the order we want them"
This way we can easily cover edge cases, like a few frames needed to be retaken due to some issue. With this recipe-alternative, the sorting algorithm can be designed to comply with the default rules that the observer will use when writing the detailed collection of calibration data (contiguity, time-ordered, pairing rules, ...) that I have collected so far from Kevin and Guillermo (who's working with Bijan and Peter Williams on this too)
I'll implement then this option in the sorting function. Once it is done and tested, we can close this issue.
Let me know if you have any further suggestions

Just to clarify I'm thinking the sorting function is a step function we apply to filter down the dataset into just the relevant files. This recipe file solution would just manually list the files in a custom recipe, and process that custom recipe. We would basically skip the sorting function in the manual list case.

I had considered it as an optional argument to the sorting function. As far as there is a clear way on how to choose each option (instead of parsing a non-None argument in the sorting function), I agree with you that it can be outside the sorting function

You would just make the recipe and write out each individual input file into the inputs field of the JSON file.
I don't think we need UTs because other ones already cover this functionality.

Do you mean that the field ""inputs" : []," in the recipe will automatically trigger the creation of a dataset that will be the input for the steps?
If so, we can close this issue, in the sense that there's a definite way to create a dataset provided by ""inputs" : []," and it has been tested

Yes, that's right. That's how the walker creates the first dataset when processing a recipe.