[webpubsubclient] Fix a bug that 0 sequenceId won't be sent to service

Packages impacted by this PR
@azure/web-pubsub-client
Issues associated with this PR
Describe the problem that is addressed by this PR
In the previous RP, we found a bug that if sequenceId == 0, then it won't be sent to the service. Which means if no message is received from the service, there won't be a keepalive enabled
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Yes
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

@xirzec Could you help to merge

@xirzec Could you help to merge

Done!


rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found

你正在使用哪个版本的 V2Ray？
V2Ray 4.44.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.17.3 linux/amd64)

你的使用场景是什么？
翻阅内部防火墙

你看到的异常现象是什么？
服务端出现rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found , 并且客户端无法连接网络

你期待看到的正常表现是怎样的？
不出现错误日志，并且客户端可以正常使用网络
请附上你的配置

服务端配置：
// 在这里附上服务器端配置文件
{
  "log": {
    "loglevel": "debug"
  },
  "inbounds": [
    {
        "port": 16823, // 服务器监听端口
        "protocol": "vmess",    // 主传入协议
        "settings": {
          "clients": [
            {
              "id": "b831381d-6324-4d53-ad4f-8cda48b30811",  // 用户 ID，客户端与服务器必须相同
              "alterId": 0
            }
          ]
        }
      }
  ],
  "outbounds": [
     {
      "protocol": "freedom",  // 主传出协议
      "settings": {}
      }
    ],

"dns": {
"servers": [
"<IP_ADDRESS>",
"localhost"
]
 }

}

客户端配置：
// 在这里附上客户端配置
{
    "log": {
        "loglevel": "debug",
        "access": "/var/log/v2ray/access.log", // ~Y~X Linux ~Z~D路~D
        "error": "/var/log/v2ray/error.log"
    },
    "inbounds": [
        {
            "tag": "transparent",
            "port": 12345,
            "protocol": "dokodemo-door",
            "settings": {
                "network": "tcp,udp",
                "followRedirect": true
            },
            "sniffing": {
                "enabled": true,
                "destOverride": [
                    "http",
                    "tls"
                ]
            },
            "streamSettings": {
                "sockopt": {
                    "tproxy": "tproxy", // ~@~O~X~N代~P~F使~T TPROXY ~V~O
                    "mark": 255
                }
            }
        }
    ],
"outbounds": [
        {
            "protocol": "vmess", // 出口协议
            "settings": {
                "vnext": [
                    {
                        "address": "<IP_ADDRESS>", // 服务器地址，请修改为你自己的服务器 IP 或域名
                        "port": 16823, // 服务器端口
                        "users": [
                            {
                                "id": "b831381d-6324-4d53-ad4f-8cda48b30811", // 用户 ID，必须与服务器端配置相同
                                "alterId": 0 // 此处的值也应当与服务器相同
                            }
                        ]
                    }
                ]
            }
        }
    ],
    "dns": {
        "servers": [
            {
                "address": "<IP_ADDRESS>", //中国大陆域名使用 114 的 DNS (备用)
                "port": 53,
                "domains": [
                    "geosite:cn",
                    "ntp.org", // NTP 服务器
                    "$myserver.address" // 此处改为你 VPS 的域名
                ]
            },
{
                "address": "<IP_ADDRESS>", //非中国大陆域名使用 Google 的 DNS
                "port": 53,
                "domains": [
                    "geosite:geolocation-!cn"
                ]
            },
            {
                "address": "<IP_ADDRESS>", //非中国大陆域名使用 Cloudflare 的 DNS
                "port": 53,
                "domains": [
                    "geosite:geolocation-!cn"
                ]
            }
        ]
    }
}

请附上出错时软件输出的错误日志

服务器端错误日志：
// 在这里附上服务器端日志
2022/02/14 18:05:53 <IP_ADDRESS>:35832 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 [Info] [2337968776] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from <IP_ADDRESS>:35832 > common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 <IP_ADDRESS>:35830 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 [Info] [1121610257] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from <IP_ADDRESS>:35830 > common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 <IP_ADDRESS>:35840 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 [Info] [449892505] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from <IP_ADDRESS>:35840 > common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 <IP_ADDRESS>:35838 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 [Info] [117733608] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from <IP_ADDRESS>:35838 > common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 <IP_ADDRESS>:35846 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
2022/02/14 18:05:53 [Info] [4227250692] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from <IP_ADDRESS>:35846 > common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found
^C2022/02/14 18:05:56 [Debug] app/log: Logger closing

客户端错误日志：
// 在这里附上客户端日志

请附上访问日志

// 在这里附上服务器端日志

其它相关的配置文件（如 Nginx）和相关日志
如果 V2Ray 无法启动，请附上 --test 命令的输出
如果 V2Ray 服务运行异常，请附上 journal 日志

这个问题是偶发出现的。 客户端和服务端的 v2ray 重启后，不一定会复现

You don't have to worry about this, it may be the replay attacks from GFW.

You don't have to worry about this, it may be the replay attacks from GFW.

关键这不涉及到 GFW, VMESS协议只跨越一个局域网

Sorry, I didn't read it carefully.
Generally, this is caused by inaccurate system time.

You don't have to worry about this, it may be the replay attacks from GFW.

关键这不涉及到 GFW, VMESS协议只跨越一个局域网

Sorry, I didn't read it carefully.
Generally, this is caused by inaccurate system time.

我试过了，把client和server的时区和时钟都校准了，还是会出现。

Hmm, by design, this doesn't happen when the ID is correct and the time is accurate.

Can reproduce this issue with NTP on. Also tried to move mu clock 60 seconds forward but it won't help.

我也遇到了同样的问题, ip id port 全都对应上了

4.43也遇到了同样的问题。uuid和时间检查了没问题，也能看到connection established，但就是无法连接。

4.44遇到这个问题，一直回退到4.39还是有同样问题

I have encountered the same problem too. There is something wrong with the 16 byte request header. It should be a hash value, but it is actually GET /my-path on my server.

同样的问题+1, 客户端没法翻墙

服务端客户端协议不匹配也会出现这个报错

There are errors in access.log:

rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false. You will not be able to enable legacy header workaround in the future.

When entering v2ray log:

rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found

And I can't browse google.
This problem was solved when I switched the protocol from QUIC to TCP both in server and client config.

如果您使用的linux发行版为debian
不妨执行如下命令:
apt-get install -y ntp && /lib/systemd/systemd-sysv-install enable ntp
当我执行这串命令，再次重启程序，服务端可以进行连接，希望能够帮到你！

遇到同样的问题，分析日志感觉大部分ip是正常的，只有个别比如112.79开头的ip就报错，比如：<IP_ADDRESS>:39219 rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found

关闭VMessAEAD。。。v2ray.vmess.aead.forced = false

遇到同样的问题，发现是服务器时钟快了2分钟。。。

As same as me. I fix it after adjust my client time.

可能是客户端与服务器 alterId 不匹配， 不知道服务器设置的话把客户端的设为0就好了

I faced this issue too.
Windows client works fine, but android client shows 'pipe closed', and server logs shows 'vmess user not found'.
Fix: Just syn date. (e.g: $/timedatectl set-ntp true)

My server time already synced
this error happened when using ws protocol with dynamic ports
but once changed the protocol type into tcp, this error was gone

access.log中存在错误：

拒绝的公共/排水：公共/排水：无法排水连接> EOF > proxy/vmess/encoding：无效用户：强制执行VMessAEAD并接收非VMessAEAD连接。您仍然可以使用环境变量v2ray.vmess.aead.forced = false禁用此安全功能。未来您将无法启用遗留标题变通办法。

输入v2ray log时：

拒绝的普通/排水：普通/排水：无法排水连接> EOF>代理/vmess/编码：无效用户>代理/vmess：未找到

而且我无法浏览谷歌。
当我在服务器和客户端配置中将协议从QUIC切换到TCP时，这个问题得到了解决。

There are errors in access.log:

rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false. You will not be able to enable legacy header workaround in the future.

When entering v2ray log:

rejected  common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user > proxy/vmess: Not Found

And I can't browse google.
This problem was solved when I switched the protocol from QUIC to TCP both in server and client config.

更换协议为tcp也解决了这个问题 感谢！

客户端时间不准会出现该问题


Allow viewing revisions.

Fixes #87
Thoughts on the UI? The whole revision UI in general needs clean up, but thught this might be a good start in integrating at least showing revisions

This UI solves all of our current questions, lessens the feature's prominence, solves our current broken UI, and addresses this problem:

I wrote a long, beautiful description for my talk. I submitted it and didn't get in.
I later trimmed it down to be shorter and more technical, out of fear that I had made it too long.
Even later I realized that I wanted it to be more like my original vision. "How did I word that in my original composition, anyway?", I ask.
So I go to the talk, and click the revisions button, and go to the revision I want to copy from.

I'm gonna merge this version so the live site isn't broken, and then add an issue for us to re-consider the entire UI for revisions.


All firebase libraries must be either above or below 14.0.0

I just follow the android guide but i got the error !
Build file '/Users/alan2305/dougo/android/app/build.gradle' line: 204

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin [id 'com.google.gms.google-services']
   > All firebase libraries must be either above or below 14.0.0

I find any method to solve my problem but it still no work
And the document ask me to replace

distributionUrl=https://services.gradle.org/distributions/gradle-2.14-all.zip

instead of

distributionUrl=https://services.gradle.org/distributions/gradle-2.4-all.zip

But my version is

distributionUrl=https://services.gradle.org/distributions/gradle-4.4--all.zip

So if I change version to 2.14, it will crash
Do anybody know how to fix it ?
This is my app/build.gradle
dependencies {
    compile project(':react-native-google-signin')
    //(For react-native-google-signin) Update android/app/build.gradle with 153~159
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:23.0.1"
    implementation "com.facebook.react:react-native:+"
    // implementation project(':react-native-google-signin'){
    //     exclude group: "com.google.android.gms" // very important
    // }
    compile(project(":react-native-google-signin")){
        exclude group: "com.google.android.gms" // very important
    }
    implementation "com.google.android.gms:play-services-auth:9.2.1" // should be at least 9.0.0

    implementation project(':react-native-fbsdk')

    implementation(project(':react-native-firebase')) {
        transitive = false
    }

    // RNFirebase required dependencies
    implementation "com.google.firebase:firebase-core:15.0.2" // 15.0.0 -> 15.0.2 failed for task ':app:transformClassesWithMultidexlistForDebug'.
    implementation "com.google.android.gms:play-services-base:15.0.1" // 15.0.0 -> 15.0.1

    // RNFirebase optional dependencies
    implementation "com.google.firebase:firebase-ads:15.0.0"
    implementation "com.google.firebase:firebase-auth:15.0.0"
    implementation "com.google.firebase:firebase-config:15.0.2" // 15.0.0 -> 15.0.2 failed for task ':app:transformClassesWithMultidexlistForDebug'.
    implementation "com.google.firebase:firebase-database:15.0.0"
    implementation "com.google.firebase:firebase-invites:15.0.1"
    implementation "com.google.firebase:firebase-firestore:16.0.0" // 15.0.0 -> 16.0.0 failed for task ':app:transformClassesWithMultidexlistForDebug'.
    implementation "com.google.firebase:firebase-messaging:15.0.2" // 15.0.0 -> 15.0.2 failed for task ':app:transformClassesWithMultidexlistForDebug'.
    implementation "com.google.firebase:firebase-perf:15.1.0"
    implementation "com.google.firebase:firebase-storage:15.0.2" // // 15.0.0 -> 15.0.2
    implementation('com.crashlytics.sdk.android:crashlytics:2.9.1@aar') {
        transitive = true
    }

    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:27.0.2"
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation "com.android.support:multidex:1.0.1" // Degug failed for task ':app:transformClassesWithMultidexlistForDebug -- Enable Multidex for Apps with Over 64K Methods
}

// 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'
}

apply plugin: 'com.google.gms.google-services'

Change this line:
implementation "com.google.android.gms:play-services-auth:9.2.1
To:
implementation "com.google.android.gms:play-services-auth:15.0.0"
had the same error. That resolved it

Please follow @jaschaio suggestion, if problems persist feel free to reopen the issue
thank you @jaschaio

I am facing same issue:
Even though I am using implementation "com.google.android.gms:play-services-auth:15.0.0"

This is the android/app/build.gradle, I am using.
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: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

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

apply from: "../../node_modules/react-native-vector-icons/fonts.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 = true

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

android {
    compileSdkVersion 25
    buildToolsVersion '25.0.0'

    defaultConfig {
        applicationId "com.hagnox"
        minSdkVersion 19
        targetSdkVersion 22
        versionCode 17
        versionName "5.0"
    }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    splits {
        abi {
            enable true
            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":15, "x86": 16]
            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-fs')
	compile project(':react-native-image-resizer')
	compile project(':react-native-image-picker')
	compile project(':react-native-fetch-blob')
	compile project(':react-native-fcm')
    compile 'com.google.firebase:firebase-core:10.0.1' //this decides your firebase SDK version
    compile 'com.google.firebase:firebase-messaging:10.0.1'
    compile project(':react-native-vector-icons')
    compile project(':react-native-fcm')
    compile project(':react-native-webview-bridge')
    compile project(':react-native-svg')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:23.0.1"
    compile "com.facebook.react:react-native:+"  // From node_modules
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:23.0.1"
    implementation "com.facebook.react:react-native:+"
    implementation(project(":react-native-google-signin")){
        exclude group: "com.google.android.gms" // very important
    }
    implementation "com.google.android.gms:play-services-auth:15.0.0" // should be at least 15.0.0 to work with most recent APIS
}

// 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'
}

apply plugin: 'com.google.gms.google-services'

I don't know about react but in ionic I fix this issue doing:
1 - go to file platforms/android/app/build.gradle and change the line
compile "com.google.android.gms:play-services-location:15.+"
to:
compile "com.google.android.gms:play-services-location:11.0.1"
2 - file platform/android/project.properties and change the line:
cordova.system.library.1=com.google.android.gms:play-services-location:15.+
to:
cordova.system.library.1=com.google.android.gms:play-services-location:11.0.1

If anyone is still struggling with this. I found an issue that isn't mentioned here that caused this error message. Here is what I found:
  implementation 'com.google.android.gms:play-services-gcm:15.0.1'
  implementation 'com.google.android.gms:play-services-analytics:16.0.1'
  implementation 'com.google.android.gms:play-services-maps:15.0.1'
  implementation 'com.google.android.gms:play-services-auth:15.0.1'
  implementation 'com.google.android.gms:play-services-location:15.0.1'
  implementation 'com.google.android.gms:play-services-ads:15.0.1'

For some reason implementation 'com.google.android.gms:play-services-analytics:16.0.1'
is 16.0.1 - This is a typo, and if you correct it to 15.0.1 it will prevent the error.

Still it's not working for me.

My Android Module level gradle file`apply plugin: 'com.android.application'
apply plugin: 'io.fabric'
apply plugin: 'com.google.firebase.firebase-perf'
android {
compileSdkVersion 26
buildToolsVersion '28.0.3'
defaultConfig {
applicationId "com.bodaty.deyaPay.deyaPay9"
minSdkVersion 19
targetSdkVersion 26
versionCode 15
versionName "2.4"
multiDexEnabled true
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
vectorDrawables.useSupportLibrary = true
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation 'com.google.firebase:firebase-crash:11.4.2'
implementation fileTree(include: ['*.jar'], dir: 'libs')
androidTestImplementation('com.android.support.test.espresso:espresso-core:2.2.2', {
exclude group: 'com.android.support', module: 'support-annotations'
})
implementation 'com.google.firebase:firebase-perf:11.4.2'
implementation 'com.squareup.okhttp3:okhttp:3.10.0'
implementation 'com.google.code.gson:gson:2.8.2'
implementation 'com.squareup.retrofit2:retrofit:2.3.0'
implementation 'com.squareup.retrofit2:converter-gson:2.3.0'
implementation 'com.google.firebase:firebase-messaging:11.4.2'
implementation 'com.google.firebase:firebase-messaging:11.4.2'
implementation 'com.android.support:appcompat-v7:26.+'
implementation 'com.android.support.constraint:constraint-layout:1.0.2'
implementation 'com.google.firebase:firebase-core:11.4.2'
implementation 'com.google.firebase:firebase-database:11.4.2'
implementation 'com.google.firebase:firebase-firestore:11.4.2'
implementation 'com.google.firebase:firebase-auth:11.4.2'
implementation 'com.android.support:design:26.+'
implementation 'com.android.support:cardview-v7:26.1.0'
implementation 'com.android.support:support-vector-drawable:26.+'
implementation 'com.googlecode.libphonenumber:libphonenumber:8.7.0'
implementation 'com.android.support:support-v4:26.+'
implementation 'com.stripe:stripe-android:5.1.0'
implementation 'de.hdodenhof:circleimageview:2.2.0'
implementation 'com.google.android.gms:play-services-wallet:11.4.2'
implementation 'com.crashlytics.sdk.android:crashlytics:2.9.6'
implementation 'com.android.support:recyclerview-v7:26.0.0'
testImplementation 'junit:junit:4.12'
implementation 'com.stripe:stripe-android-issuing-push-provisioning:1.0.3'
implementation 'com.google.android.gms:play-services-tapandpay:17.0.1'
}
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.android.gms.strict-version-matcher-plugin'
`
I'm facing the same issue.Can anyone look to help?


Hyper glitched out

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

Mac OS X 10.11.6:
Hyper.app 1.0.1 (<IP_ADDRESS>9):
**https://gist.github.com/christoga/d5c16ecb8b76c35143fd00695a877f54**:
Dev Console Error: Unknown OSC code: "1"
The issue is reproducible in vanilla Hyper.app:

Issue
I've used the same configuration as I used in the old Hyperterm app, somehow it doesn't work how it was supposed to work, is there something wrong that I miss/did?
Preview: http://imgur.com/a/18Jtr

If you move your config, and restart hyper (to get the default config) Do you still get this problem? @christoga

I don't know what happen, but somehow it doesn't show the glitch anymore. Thanks for helping tho @albinekb


CrossHair with cross lines

Is it possible to have a CrossHair  like the one in here demo ?

Is it possible to have a CrossHair like the one in here demo ?

thanks for showing demo, I've never seen it, it's very top.

I try to find some free time to see if I can add the functionality to crosshairsToll.

@unosbaghaie have you managed to develop the cross lines feature? We need to add something like the demo image to our project but don't know how to start... Thanks.


'multipart/mixed' is not supported in Rest Assured Response

Hi John,
In my service, most of the response is in 'multipart/mixed' format. I am not able to perform any assertions in rest assured since I am getting the following error message:

Please let me know. Thanks in Advance!

What does your test look like?

My test looks like the following:
=== REQUEST ===
Request method:	GET
Request URI:	http://xxx
Proxy:
Request params:
Query params:
Form params:
Path params:	documentId=xxx
Headers:
Cookies:
Multiparts:
Body:
=== RESPONSE ===
HTTP/1.1 200 OK
Content-Type: multipart/mixed;boundary=Boundary_xxxxx;version=4
Date: Wed, 11 Apr 2018 14:32:34 GMT
ETag: xxxx
Server: xxx
transfer-encoding: chunked
Connection: keep-alive
--Boundary_x_xxxx_xxxx
Content-Type: application/xxx+xml;charset=UTF-8;version=4
Response will be here
--Boundary_x_xxxx_xxxx
Content-Type:text/html;charset=UTF-8
--Boundary_x_xxxx_xxxx--
I want to verify the tags & its value in the response.

Oh I get it, I thought you meant the request. Hmm I don't think this is supported in RA, at least I'm not aware of how to solve it since I've never had the need to do this myself.

Hey @johanhaleby we have lot of test cases that needs this fix, do you think you can provide an alternate solution in order to test these sort of tests for our project?
or any other suggested tools/libraries that we can use to test these tests?
P.S: If RA provides a fix it would be really helpful.

any luck on this @johanhaleby

I just built this workaround to extract multipart/form-data. I think the library also supports multipart/mixed:
var response = given()
        .accept(MediaType.MULTIPART_FORM_DATA)
        .when()
        .get(PATH)
        .then()
        .statusCode(OK.getStatusCode())
        .extract()
        .response()

// multipart body
var content = response.asByteArray();

var ctx = new RequestContext() {
    @Override
    public String getCharacterEncoding() {
        return StandardCharsets.UTF_8.displayName();
    }

    @Override
    public String getContentType() {
        // contains also the boundary
        return response.contentType();
    }

    @Override
    public int getContentLength() {
        return content.length;
    }

    @Override
    public InputStream getInputStream() {
        return new ByteArrayInputStream(content);
    }
};

// Files to do checks against. Can also be parsed as JSON or whatever to do further checks.
var files = new FileUpload(new DiskFileItemFactory()).parseRequest(ctx);

With multipart parser dependency:
<dependency>
    <groupId>commons-fileupload</groupId>
    <artifactId>commons-fileupload</artifactId>
    <version>1.4</version>
</dependency>


Update from 4.12.0-0.okd-2023-02-04-212953 to 4.12.0-0.okd-2023-02-18-033438 error

Hello!
When updating a ipi vsphere installation from 4.12.0-0.okd-2023-02-04-212953 to 4.12.0-0.okd-2023-02-18-033438 following error appears:
Retrieving payload failed version="4.12.0-0.okd-2023-02-18-033438" image="[registry.ci.openshift.org/origin/release@sha256:fd08a1dae13a434729451cdb6edd969714a4329904e8d27eb45d94e96021dff4](http://registry.ci.openshift.org/origin/release@sha256:fd08a1dae13a434729451cdb6edd969714a4329904e8d27eb45d94e96021dff4)" failure=The update cannot be verified: unable to verify sha256:fd08a1dae13a434729451cdb6edd969714a4329904e8d27eb45d94e96021dff4 against keyrings: verifier-public-key-ci

Seems we used an outdated GPG key to sign the release :( https://github.com/openshift/release/pull/36617 would fix it for other nightlies
The workaround is to apply the upgrade with --force. Keeping this open to make sure it got resolved in the new stable

Same issue happened from 4.12.0-0.okd-2023-04-16-041331 to 4.12.0-0.okd-2023-11-20-220231 (nightly build) today.


EndOfStreamException thrown when using loaddependencies=true

What You Are Seeing?
Hi! I'm trying to install an addin using the loaddependencies=true parameter:
#addin "nuget:?package=Some.Package&version=0.0.0&loaddependencies=true"

I'm observing an error where Cake scans the dependency graph and attempts to detect if each assembly is a CLR assembly.
  Error: System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
     at System.IO.BinaryReader.InternalRead(Int32 numBytes)
     at System.IO.BinaryReader.ReadUInt16()
     at Cake.Core.IO.FileExtensions.IsClrAssembly(IFile file) in C:\projects\cake\src\Cake.Core\IO\FileExtensions.cs:line 136
     at Cake.Core.Polyfill.AssemblyHelper.LoadAssembly(ICakeEnvironment environment, IFileSystem fileSystem, FilePath path) in C:\projects\cake\src\Cake.Core\Polyfill\AssemblyHelper.cs:line 49
     at Cake.Core.Reflection.AssemblyLoader.Load(FilePath path, Boolean verify) in C:\projects\cake\src\Cake.Core\Reflection\AssemblyLoader.cs:line 31
     at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary`2 arguments) in C:\projects\cake\src\Cake.Core\Scripting\ScriptRunner.cs:line 173
     at Cake.Commands.BuildCommand.Execute(CakeOptions options) in C:\projects\cake\src\Cake\Commands\BuildCommand.cs:line 41
     at Cake.CakeApplication.Run(CakeOptions options) in C:\projects\cake\src\Cake\CakeApplication.cs:line 45
     at Cake.Program.Main() in C:\projects\cake\src\Cake\Program.cs:line 81

I suspect that there's something in the offset reading code in FileExtensions.IsClrAssembly which, when presented with a non-CLR .dll is reading at one offset, finding what it thinks is another offset, and attempting to set the stream pointer to somewhere beyond the stream's end.
It looks like this line sets the stream position to whatever it's read at the previous location without checking whether that puts things beyond the end of the stream.
This also suggests that there might be other non-CLR DLLs being tested by Cake which happen to have a small number at the first offset read, which are sneaking through the test. I haven't dug too far into it so please take that with a grain or two of salt.
What is Expected?
Cake correctly walks the dependency graph and filters out non-CLR assemblies.
Workaround
This is preventing the use of the loaddependencies=true parameter. The best workaround I've found is to include all of the Cake addin's dependencies manually in build.cake as well. There is a long list of dependencies :)
What version of Cake are you using?
0.38.5
Are you running on a 32 or 64 bit system?

win-x64
linux-x64

What environment are you running on?  Windows? Linux? Mac?

Works fine on Windows
Fails on Linux.
Not tested on Mac.

Are you running on a CI Server?  If so, which one?

Fails under TeamCity on a agents running inside Linux containers.
Fails locally running inside a Linux container.
Works locally running on Windows on metal.

How Did You Get This To Happen? (Steps to Reproduce)
I just added an addin directive to my Cakefile with loaddependencies=true. It worked fine locally and then went 💥 on the build server.
Other Cakefiles with other addins seem to work fine so I suspect that it's just the dependencies of this (unfortunately currently internal) addin that cause Cake to throw.
Output logs
Unfortunately sanitising that much of an output log isn't feasible. I've fished out the stack trace (above); hopefully that gives a good pointer to what's going on.

@uglybugger Your analysis was correct and I was able to reproduce the error by creating a Cake add-in that includes a .dll file that is not a valid PE file.
using System.IO;

void Main()
{
    var buffer = new byte[365]; // Minimum size for Cake to consider analyzing it
    using (var stream = new MemoryStream(buffer))
    {
        using (var binaryWriter = new BinaryWriter(stream))
        {
            binaryWriter.Write(new byte[60]);
            binaryWriter.Write(5000); // Tell Cake to jump to a position beyond the length of the stream
        }
    }

    Directory.CreateDirectory(@"C:\Temp");
    File.WriteAllBytes(@"C:\Temp\InvalidPE.dll", buffer);
}

Fixed by #2971


Stability and health-checks via livenessProbe

Not so much an issue (apologies). More as a community resource.
Seeking advice and best practices for livenessProbe health checks on our ES nodes.
We are thinking the following HTTP health-checks would be conservative and allow for high load situations. My concerns / questions are:

Will a destroyed/restarted node have adverse effects on a cluster setup as per this repo?
Will multiple destroyed/restarted masters have any serious side effects?
What are others doing for restart/health-checks? Anything?
Would it be good at a minimum to have a livenessProbe on master nodes, where data persistence is not an issue?

es-client
livenessProbe:
  initialDelaySeconds: 25
  timeoutSeconds: 5
  periodSeconds: 8
  successThreshold: 5
  failureThreshold: 2
  httpGet:
    path: /
    port: 9200

es-data, es-master
livenessProbe:
  initialDelaySeconds: 25
  timeoutSeconds: 5
  periodSeconds: 8
  successThreshold: 5
  failureThreshold: 2
  tcpSocket:
    port: 9300

Honestly, if you want best-practices, implement your own probes instead of using http/tcp. As an example, implement a script or app that queries ES API for a certain node status.

That is such a great idea... Will do so and report back our approach on this issue.

@andrewmclagan wondering if you ever figured anything out around this?
Thanks in advance!

@gsaslis @andrewmclagan Have you guys implemented anything to solve this issue? I am currently facing it, and it would be great if it's already solved.
Thanks.

+1, I am interested too in knowing about the solution you applied

Me as well. Inquiring minds want an answer.

Does this cover it?

Yes it does, Thanks!


Remove implicit EventLog filter from UseWindowsServices and move it to the template

The implicit AddFilter call we run for your in UseWindowsServices is problematic because it is hidden to users and causes confusion and overrides the use of the default logging options in appsettings.json (https://github.com/aspnet/Extensions/issues/1839). Users can override this logic, but they have to add an explicit EventLog section to their logging config.
https://github.com/aspnet/Extensions/blob/f12d709976e382672ce100bc00381a8847f06489/src/Hosting/Hosting/src/Host.cs#L102
Instead, let's remove this and add the filtering to the Worker Service template appsettings.json file:
{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    },
    "EventLog": {
      "LogLevel": {
        "Default": "Warning"
      }
    }
  }
}

Clarification: that's not in UseWindowsServices.

Right, but I believe that line is only in Host to get the filter in place before logging config is read. UseWindowsServices is the only one that registers the provider itself, so only that template would need to be adjusted here. We should double check that of course.

Feh, looks like it is also registered here: https://github.com/aspnet/Extensions/blob/ef5d488c054c3aa850c29c10d851fcdc8a004eed/src/Hosting/Hosting/src/Host.cs#L113

Given that, we probably don't also need it in UseWindowsServices... This is also a little more complicated :(

Also, UseWindowsServices is not in the worker template, it requires an additional dependency.

@anurse Is there any equivalent issue in ASP.NET Core?

Not at the moment. Have we figured out how we're going to do it? @Tratcher 's comment indicates this is going to be more difficult than just updating the template.

In re-thinking this, I actually think we could just leave this as-is. The issue is that previously when you enabled UseWindowsServices, you got Information logs in the Event Log. I'd contend that's too noisy and it's by-design that we only want to send Warnings/Errors to EventLog. You can always override it directly (https://github.com/aspnet/Extensions/issues/1839#issuecomment-501771268).
I'd think that a Windows Service should be logging things Info and below to things like log files rather than the EventLog, but that's just my impression.

Closing as per my above comment (and hearing no disagreement 😄)


How do I make a negative Bars in Blazor-ApexChart

Please, is it possible to make the colors of bars red if the value is negative with Blazor-ApexChart. If yes, I would love to know how I can achieve that. I have tried the demo/documentation website, but I did not find any similar example.
Thanks

Hi,
Please check this, https://apexcharts.github.io/Blazor-ApexCharts/bar-charts#negative values

Hi,
Sorry for delayed response from me.
This does not seems to work for me when the Bar Chart is mixed with line chart(s) or other type of supported chart(s).
How do I make it work in this scenario?
NB: I am also passing an instance of ChartOptions to the ApexChart component.
Thanks


DeepAR sequence padding with zeros leads to nan loss in Gamma and Beta distributions.

Description
When training a DeepAREstimator some of the input is randomly set to 0. This is especially apparent for distributions where 0 is not in the support of the distribution, like for the Beta and Gamma distributions whose support is (0,1), and (0, inf) respectively.
Even though my training and test data is in the interval [0.4, 0.6], the log probability gets calculated on data like this (printed for the student-t Distribution):
[[0.         0.         0.         ... 0.4895292  0.4855527  0.4815994 ]
 [0.5996926  0.5999265  0.59999985 ... 0.41260046 0.41461775 0.41677222]
 [0.5999126  0.59966487 0.5992571  ... 0.41906032 0.42147845 0.4240227 ]
 ...
 [0.         0.         0.         ... 0.52530396 0.5214071  0.5174759 ]
 [0.5995836  0.5991383  0.5985338  ... 0.42206398 0.42463723 0.4273315 ]
 [0.5694312  0.5664917  0.5634455  ... 0.48193955 0.4858951  0.48987332]]

As we can see most data-points can be found in the generated sinusoidal (if one checks), except for the 0.s.
For distributions like Gamma or Beta this leads to numeric issues when calculating the log-prob, HOWEVER, for other models this could potentially significantly impact performance.
To Reproduce
One can see this by setting hybridize=False in the Trainer and then printing x with print(x.asnumpy()) in the log_prob function of the corresponding probability function.
I tested this, and the error occurs at least the Student-t, Gamma and Beta Distributions.
First creating a dataset without any values even close to 0.
freq="1H"
pred_length=48

x = (np.sin(np.linspace(0, 20, 500))/10)+0.5

train_ds = ListDataset(
    [
        {'target': x, 'start': 0}
    ],
    freq=freq
)

test_ds = ListDataset(
    [
        {'target': x[:-pred_length], 'start': 0}
    ],
    freq=freq
)

then we try to train our DeepAREstimator:
estimator = DeepAREstimator(
    prediction_length=pred_length,
    freq=freq,
    distr_output=GammaOutput(),
    trainer=Trainer(learning_rate=0.001, hybridize=False)
    ,scaling=False
)

estimator_name = type(estimator).__name__

print(f"evaluating {estimator_name} on Custom")

agg_metrics, item_metrics = backtest_metrics(
    train_dataset=train_ds,
    test_dataset=test_ds,
    forecaster=estimator
)

Now we modify the log_prob() function to print the matrices:
    def log_prob(self, x: Tensor) -> Tensor:
        # some code ...
        print(x.asnumpy())
        # some code ...
        return ll

Error Message
GluonTSDataError                          Traceback (most recent call last)
<ipython-input-21-2d726dd30ff6> in <module>
     11     train_dataset=train_ds,
     12     test_dataset=test_ds,
---> 13     forecaster=estimator
     14 )

~/WorkingDirectory/gluon-ts/src/gluonts/evaluation/backtest.py in backtest_metrics(train_dataset, test_dataset, forecaster, evaluator, num_samples, logging_file, use_symbol_block_predictor)
    174         serialize_message(logger, estimator_key, forecaster)
    175         assert train_dataset is not None
--> 176         predictor = forecaster.train(train_dataset)
    177
    178         if isinstance(forecaster, GluonEstimator) and isinstance(

~/WorkingDirectory/gluon-ts/src/gluonts/model/estimator.py in train(self, training_data, validation_data)
    221         self, training_data: Dataset, validation_data: Optional[Dataset] = None
    222     ) -> Predictor:
--> 223         return self.train_model(training_data, validation_data).predictor

~/WorkingDirectory/gluon-ts/src/gluonts/model/estimator.py in train_model(self, training_data, validation_data)
    206             input_names=get_hybrid_forward_input_names(trained_net),
    207             train_iter=training_data_loader,
--> 208             validation_iter=validation_data_loader,
    209         )
    210

~/WorkingDirectory/gluon-ts/src/gluonts/trainer/_base.py in __call__(self, net, input_names, train_iter, validation_iter)
    295                     )
    296
--> 297                     epoch_loss = loop(epoch_no, train_iter)
    298                     if is_validation_available:
    299                         epoch_loss = loop(

~/WorkingDirectory/gluon-ts/src/gluonts/trainer/_base.py in loop(epoch_no, batch_iter, is_training)
    274
    275                     # check and log epoch loss
--> 276                     check_loss_finite(loss_value(epoch_loss))
    277                     logging.info(
    278                         "Epoch[%d] Evaluation metric '%s'=%f",

~/WorkingDirectory/gluon-ts/src/gluonts/trainer/_base.py in check_loss_finite(val)
     48     if not np.isfinite(val):
     49         raise GluonTSDataError(
---> 50             "Encountered invalid loss value! Try reducing the learning rate "
     51             "or try a different likelihood."
     52         )

GluonTSDataError: Encountered invalid loss value! Try reducing the learning rate or try a different likelihood.

Environment

Operating system: MacOS
Python version: 3.6
GluonTS version: 4.2

The zeros you are seeing in the target and the error you are getting might be unrelated.
By default, DeepAR also samples training instances from the beginning of the sequence, where the initial part of the sampled window can start before observations are available. This is controlled by the pick_incomplete parameter of the InstanceSplitter, which is true by default:
https://github.com/awslabs/gluon-ts/blob/02131317b676467993df9f8dbea79215eb3eb314/src/gluonts/transform/split.py#L106-L111
In this case, the initial portion (of the target and all time-varying features) is padded with zeros, which seems to be what you are observing here -- this is the intended behavior. However, while the loss function is evaluated on these padded zero values, they are removed from the final loss calculation:
https://github.com/awslabs/gluon-ts/blob/02131317b676467993df9f8dbea79215eb3eb314/src/gluonts/model/deepar/_network.py#L411-L423
The observed_values feature is also zero-padded by the InstanceSplitter, marking the padded target values as unobserved.
You could try modifying DeepAR to use pick_incomplete=False to see if this fixes the problem (in which case there is a bug in the masking code somewhere).

Setting pick_inclomplete=False fixes the problem. So as we can see from how the weighted_loss is computed, the calculated loss is weighted with 0 for not observed values. If the loss is nan, however, (because of log(0) for example), then 0*nan=nan and the weighted loss becomes nan.
We should fix this, by setting the value of the padding dependent on the distribution: e.g. padding with 0.5 for Beta and Gamma instead of with 0.

It’s maybe better to try improving the masking logic first: one way could be to use where instead of multiplication, see https://mxnet.apache.org/api/python/docs/api/ndarray/ndarray.html?mxnet.ndarray.where

It’s maybe better to try improving the masking logic first: one way could be to use where instead of multiplication, see https://mxnet.apache.org/api/python/docs/api/ndarray/ndarray.html#mxnet.ndarray.where

Yeah, I absolutely agree, I just thought of that too omw home.

This is fixed by https://github.com/awslabs/gluon-ts/pull/534.

@AaronSpieler I was just going through this issue since I am faced with the following problem: I have a lot of time series with different lengths in the train set, so I was wondering if I need to pad them with 0 for them to be of the same length. Is that something that I need to to manually using FieldName.IS_PAD and/or FieldName.OBSERVED_VALUES or is that being taken care of  automatically? Also, I don`t know how to use pick_incomplete.
Would greatly appreciate your help.

@StatMixedML no need to pad your time series: if pick_incomplete = True, the model will be trained by occasionally sampling training windows that partially fall outside (to the left) of your time series, and the initial missing data will be automatically padded; if pick_incomplete = False, then only training windows with genuine data will be sampled to form training batches, and no padding happens.
Hope that clarifies!

@lostella Thanks for clarifying. I am still not sure I entirely understand it. Assume that the prediction length = 18 months. However, most of the time series in the training set have length around 6-8 months, some longer, but all are irregularly spaced. For the DeepAR model I set prediction_length = context_length = 24. I padded the time series that have less than 24 months of observations to meet the prediction_length and context_length. All of them also have different starting times.
So you`d suggest NOT TO PAD the training data and to set context_length = min(train_length)? Or how would you tackle the problem of short and irregularly spaced time series? Sorry for the confusion. Also, how can I set pick_incomplete in the code?
Many thanks!

@AaronSpieler, your pull request was merged, but not released yet, right? I'm having possibly the same problem with DeepAR and Negative binomial distribution.

@AaronSpieler, your pull request was merged, but not released yet, right? I'm having possibly the same problem with DeepAR and Negative binomial distribution.

That's correct. It will be in the v0.5 release.

@AaronSpieler, I installed the current master version and I'm still getting NaN using Negative Binomial (sometimes even in the first epoch) with DeepAR. I'm using this distribution because I'm dealing with Demand Forecasting and the DeepAR's paper said they've used this distribution to deal with this kind of TS.

@AaronSpieler, actually, after I've updated to the master's version, it seems that I'm always getting:
  File "/home/fernandocamargo/datascience_workspace/log_inteligente_ai/gazin/task/model/base.py", line 164, in run
    dict(fit=self.fit, cross_validation=self.cross_validate)[self.training_type]()
  File "/home/fernandocamargo/datascience_workspace/log_inteligente_ai/gazin/task/model/gluonts.py", line 185, in fit
    predictor = estimator.train(self.train_dataset)
  File "/home/fernandocamargo/anaconda3/envs/gazin/lib/python3.6/site-packages/gluonts/model/estimator.py", line 240, in train
    training_data, validation_data, num_workers, num_prefetch, **kwargs
  File "/home/fernandocamargo/anaconda3/envs/gazin/lib/python3.6/site-packages/gluonts/model/estimator.py", line 219, in train_model
    validation_iter=validation_data_loader,
  File "/home/fernandocamargo/anaconda3/envs/gazin/lib/python3.6/site-packages/gluonts/trainer/_base.py", line 328, in __call__
    "Got NaN in first epoch. Try reducing initial learning rate."
gluonts.core.exception.GluonTSUserError: Got NaN in first epoch. Try reducing initial learning rate.

And it seems that it happens in the first batch. I've tried to reduce the learning rate with no effect.

@lostella Thanks for clarifying. I am still not sure I entirely understand it. Assume that the prediction length = 18 months. However, most of the time series in the training set have length around 6-8 months, some longer, but all are irregularly spaced. For the DeepAR model I set prediction_length = context_length = 24. I padded the time series that have less than 24 months of observations to meet the prediction_length and context_length. All of them also have different starting times.
So you`d suggest NOT TO PAD the training data and to set context_length = min(train_length)? Or how would you tackle the problem of short and irregularly spaced time series? Sorry for the confusion. Also, how can I set pick_incomplete in the code?
Many thanks!

The fact of irregularly spaced time-series could be a problem. You could try so pre-processing steps like filling the values with the average of the neighboring, or other values that make sense, to have regularly spaced time series in the end. Aggregation is another alternative.
Even bigger problem is if you want to have prediction_length=context_length=24 and your time series is not even 24 long, because you don't even have a proper target at that point. Or do you mean after removing the target 24 you don't have 24 anymore, because in that case you don't need to pad manually, just set pick_incomplete = True as suggested by @lostella .
I checked in case of DeepAR, and it has pick_incomplete = True so you don't need to do anything in that regard.


Spider path

Change the way we define the path for the spider.
The problem is that the spider stops when one of the platforms to which it was supposed to go to disappears, thus making some levels not work the way intended.

Dynamic path finding would take time.
I suggest we redesign the spider.

I agree.
We can design something else, doesn't even have to be a spider.
I should close this issue and open a new one ?

issue closed.


Fix minor issues in html

Fixed some minor issues in html.

👍  Thanks for the patch!

Can you sign the CLA?
Sent from my iPhone

On Jun 29, 2016, at 5:43 PM, Neng Lu<EMAIL_ADDRESS>wrote:
👍 Thanks for the patch!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you sign the CLA?

Signed.


magit does not support 24.3

Is there anyway to use older version of magit? Thanks!

@zcyang You can cd el-get's dir, and do a manually git reset to magit itself.


Update README.md

I'm mainly opening this to check whether the documentation builds automatically on a new PR. This PR addresses the request from #83:  add link to README and github repo, as necessary

@dsgibbons Ah, I suppose this means we don't need a dedicated github action (#85) to build the rtd docs?

It appears not. It doesn't seem like any extra configuration is required. I may just leave #85 open for now in case we need it for some reason.


Prevent read-after-free in the queued CallableCustomStaticMethodPointer, fixes slot >= slot_max errors in release templates

Fixes https://github.com/godotengine/godot/issues/85263 and fixes https://github.com/godotengine/godot/issues/70910

Tested this PR, I confirm it fixes both issues.
For #70910, I tested all the linked MRPs I could find (unless they required C#).
Fixed by this PR:

https://github.com/godotengine/godot/issues/70910#issuecomment-1758935677
#75802
#79318

Already fixed by #78988:

https://github.com/godotengine/godot/issues/75422#issuecomment-1627792623

Thanks! This should solve a lot of pain points publishing release builds.

Cherry-picked for 4.1.4. (I also included some changes to error macros from https://github.com/godotengine/godot/pull/83003 which were causing conflicts when picking.)


create fluentd as deployment

The statefulset type causes pvc > 2 where sts.replicas > 2 . If the deployment object is used, one pvc can be shared.

 Without a valid use case I don't think it would worth implementing that use case.
A few reasons against:

AFAIK most cloud providers do not support readwritemany out of the box
How do you write automation to drain the buffers of a scaled down worker? Currently we can easily detect orphan PVCs and start drainer jobs, but I don't see a good option to do that for deployment replicas.

This is a problem I encountered. I want to improve performance through multiple instances of fluentd, but multiple pvc will cause the collected service logs to be scattered to multiple filesystem directories.


TX for claiming funds for a peer's swap-in fails to be broadcasted?

Running CLN v23.11.2 with peerswap 9d41480cf6a9753ca374ded3e03be768716766e4.
Scenario:
Peer initiated swap-in, but the on-chain funds never arrived to my wallet.
From my side the status is:
      "asset": "lbtc",
      "type": "swap-in",
      "role": "receiver",
      "state": "State_ClaimedPreimage",

CLN logs:
2024-12-27T04:33:17.827Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got msgtype: a455 for swap: <swapid>
2024-12-27T04:33:17.858Z INFO    lightningd: Sending <amount>000msat over 1 hops to deliver <amount>000msat
2024-12-27T04:33:26.728Z INFO    <nodeid>-chan#212: htlc 2549 failed from 0th node with code 0x400f (WIRE_INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS)
2024-12-27T04:33:27.161Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_SwapInReceiver_OnRequestReceived on
2024-12-27T04:33:27.169Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_ActionSucceeded on State_SwapInReceiver_CreateSwap
2024-12-27T04:33:27.170Z INFO    plugin-peerswap: [Swap:<swapid>] swap-in request received: peer: <nodeid> chanId: <chanId> initiator: <nodeid> amount <amount>
2024-12-27T04:33:27.174Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_ActionSucceeded on State_SwapInReceiver_SendAgreement
2024-12-27T04:33:27.851Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got msgtype: a45d for swap: <swapid>
2024-12-27T04:33:28.013Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_OnTxOpenedMessage on State_SwapInReceiver_AwaitTxBroadcastedMessage
2024-12-27T04:33:28.032Z INFO    plugin-peerswap: adding tx watcher for <swapid>
2024-12-27T04:33:28.032Z DEBUG   plugin-peerswap: starting chain observer for <swapid>
2024-12-27T04:33:28.034Z DEBUG   plugin-peerswap: Await confirmation for tx with id: <txid> on swap <swapid>
2024-12-27T04:33:28.034Z DEBUG   plugin-peerswap: new block height=3180754, starting_height=3180754, safety_limit=30 for <swapid>
2024-12-27T04:33:35.648Z DEBUG   plugin-peerswap: new block height=3180755, starting_height=3180754, safety_limit=30 for <swapid>
2024-12-27T04:33:37.793Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:33:47.764Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:33:57.764Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:07.755Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:17.759Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:27.789Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:36.200Z DEBUG   plugin-peerswap: new block height=3180756, starting_height=3180754, safety_limit=30 for <swapid>
2024-12-27T04:34:37.775Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:47.791Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:34:57.766Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:07.767Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:17.756Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:27.772Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:35.608Z DEBUG   plugin-peerswap: new block height=3180757, starting_height=3180754, safety_limit=30 for <swapid>
2024-12-27T04:35:35.804Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_OnTxConfirmed on State_SwapInReceiver_AwaitTxConfirmation
2024-12-27T04:35:37.790Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:45.879Z INFO    lightningd: Sending <amount>000msat over 1 hops to deliver <amount>000msat
2024-12-27T04:35:47.798Z DEBUG   plugin-peerswap: [Messenger] From: <nodeid> got same message for swap: <swapid>
2024-12-27T04:35:50.253Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_ActionSucceeded on State_SwapInReceiver_ValidateTxAndPayClaimInvoice
2024-12-27T04:35:50.253Z DEBUG   plugin-peerswap: [FSM] event:id: <swapid>, Event_ActionSucceeded on State_SwapInReceiver_ClaimSwap
2024-12-27T04:35:50.253Z INFO    plugin-peerswap: [Swap:<swapid>] Swap claimed with preimage <preimage>
2024-12-27T04:40:09.098Z INFO    <nodeid>-channeld-chan#212: Peer connection lost
2024-12-27T04:40:09.098Z INFO    <nodeid>-chan#212: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (62208)
2024-12-27T04:41:00.405Z INFO    <nodeid>-channeld-chan#212: Splice resume check with local_next_funding: omitted, remote_next_funding: empty, inflights: 0

elementsd logs:
2024-12-27T04:35:49Z [peerswap] keypool added 1 keys (1 internal), size=2000 (1000 internal)
2024-12-27T04:35:49Z [peerswap] keypool reserve <n>
2024-12-27T04:35:49Z [peerswap] keypool keep <n>
2024-12-27T04:35:50Z [peerswap] AddToWallet <txid>  new

listtransactions:
  {
    "address": "<address>",
    "category": "receive",
    "amount": n.m,
    "amountblinder": "...",
    "asset": "...",
    "assetblinder": "...",
    "label": "peerswap -- ClaimByInvoice(swap id=....)",
    "vout": 0,
    "confirmations": 0,
    "trusted": false,
    "txid": "<txid>",
    "walletconflicts": [
    ],
    "time":<PHONE_NUMBER>,
    "timereceived":<PHONE_NUMBER>,
    "bip125-replaceable": "yes"
  }

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Possibly related? From @wtogami on discord:

Discount CT is live on liquid on the default relay nodes and 10/15 of the functionary servers. Two more next week. This means there is currently a 5/15 chance at the moment of needing to wait until the next block. That's good enough to begin using it.

For the record, this is my first swap where my side is to receive l-btc using v4.0rc1. I have done swaps where my side has sent l-btc.

For the record, this is my first swap where my side is to receive l-btc using v4.0rc1. I have done swaps where my side has sent l-btc.

Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

I used https://blockstream.info/liquid/tx/push to broadcast my tx in the end. Doing a sendrawtransaction just echoed the txid and seemingly did nothing.
My getinfo:
Chain: liquidv1
Blocks: 3181676
Headers: 3181676
Verification progress: 100.0000%
Difficulty:

Network: in 3, out 10, total 13
Version: 230204
Time offset (s): 0
Proxies: <IP_ADDRESS>:19050 (ipv4, ipv6, onion, cjdns)
Min tx relay fee rate (BTC/kvB): 0.00000100

Wallet: peerswap
Keypool size: 999
Transaction fee rate (-paytxfee) (BTC/kvB): 0.00000000

Balance: {"bitcoin":Infinity}

Warnings:

My elements config:
dbcache=512
maxorphantx=256
txindex=1
blockfilterindex=1
coinstatsindex=1
bind=<IP_ADDRESS>:xyzw
bind=<IP_ADDRESS>:abcd=onion
discover=0
externalip=microsoftconspireswithscammersd.onion
listen=1
listenonion=0
peerbloomfilters=1
peerblockfilters=1
port=xyzw
proxy=tor-proxy:port
upnp=0
<EMAIL_ADDRESS>zmqpubhashblock=tcp://<IP_ADDRESS>:<port>
zmqpubhashtx=tcp://<IP_ADDRESS>:<port>
zmqpubrawblock=tcp://<IP_ADDRESS>:<port>
zmqpubrawtx=tcp://<IP_ADDRESS>:<port>
logips=1
logtimestamps=1
printtoconsole=1
chain=liquidv1
creatediscountct=1
server=1
rest=1
rpcbind=<IP_ADDRESS>
rpcauth=get_phucked:real_hard
rpcport=<rpcport>
rpcallowip=<IP_ADDRESS>/0
rpcthreads=8
rpcworkqueue=128
validatepegin=1
mainchainrpchost=<IP_ADDRESS>
mainchainrpcport=8332
mainchainrpcuser=get_phucked
mainchainrpcpassword=in_the_arse

    "subver": "/Elements Core:23.2.2/",
    "subver": "NBXplorer-840652740337079693",
    "subver": "/Elements Core:23.2.2/",
    "subver": "/Elements Core:22.1.1/",
    "subver": "/Elements Core:23.2.2/",
    "subver": "/Elements Core:23.2.4/",
    "subver": "/Elements Core:23.2.2/",
    "subver": "/Elements Core:23.2.2/",
    "subver": "/Elements Core:23.2.1/",
    "subver": "/Elements Core:23.2.2/",
    "subver": "/Elements Core:23.2.1/",
    "subver": "/Elements Core:<IP_ADDRESS>/",
    "subver": "/Elements Core:23.2.2/",

An examination of elements-cli getpeerinfo found this node had 100% tor peers. At the moment prior to the enabled-by-default elementsd only the default IPv4 bridge nodes are guaranteed to mempool accept discount CT. I had assumed IPv4 elementsd would not run into this problem because they connect to the IPv4 bridge nodes by default. I had forgotten Tor nodes have a higher chance to not always connect with those nodes. This will become increasingly less likely after the official release.
Temporary workaround: addnode=u35hiqs3xje7dsawqahhlv3ofx4fyqv4rphrostoafmkydn7rjee73qd.onion
This reinforces the fact we should not announce the peerswap v4 release until elementsd discount CT is more widely deployed. In the mean time power users know how to make it work.


Rename bidAdapter and add to partners

Related to https://github.com/prebid/Prebid.js/pull/3070

Update

Will be released with 1.26


Allow HistogramWidget to show multiple layers at once

Currently HistogramWidget can only show one selected layer. If multiple layers are selected, it should overlay histograms from each layer on the same plot, and generate a legend to identify each histogram.

I had a play around trying to implement this, and ran into the issue of what to do when multiple RGB layers are selected,
or a mix of grayscale and RGB layers are selected. So I think unless anyone can come back with a suggestion of how to plot these two cases, I'm going to close this as something we won't implement.


Fix for issue #225

Fix for issue #225
Updated code to accept dateFrom and dateTo of API methods with quotes("").

Hi @c0c0n3 , Thanks for the review :-)
I have updated the code as per your suggestion. Please review the updated PR.

@pooja1pathak should I go ahead and merge into master?

Yes you can merge this PR :-)


No need to register resource_group_name in _params.py

No need to register resource_group_name in _params.py.
Remove c.argument('resource_group_name', resource_group_name_type) in _params.py as it is registered automatically in azure cli core.

close it as it may cause confusion for users and codegen won't support this at this time


Inconsistent naming in project, repo folder, exe name, window title

They should all be wv2util or WebView2Utilities

Updated project name, exe name, window title, readme.md, and xaml


Fix typos

In README.md :

Remove leading & trailing spaces
Remove plural from invariable words
Fix typing errors
Fix non-semantic empty header used as separator

In data.js :

Fix missing subreddit name's last letter
Fix missing heading slash from subreddit links

In order to validate data.js's integrity, I created a small Deno function called isSubreddit that you can use the following way :
import { isSubreddit } from 'https://git.kaki87.net/KaKi87/deno-is-subreddit/raw/branch/master/mod.js';

import data from 'https://raw.githubusercontent.com/bestreddit/bestreddit.github.io/master/data/data.js';

for(const { Link } of data){
    if(!await isSubreddit(Link.replace(/^\/r\//, '')))
        console.log(Link);
}

++

Hey @KaKi87
This looks cool :0

Hey @KaKi87
This looks cool :0

You're welcome 🙂

You're welcome 🙂


fix: amount missing bch qrcode

Related to #417

Description
Added logic to add amount to copy url
Test plan
Run the project with yarn:clean:build
Create a bch button or widget and copy the qrcode url check if amount is there

When I copy the QR code by clicking on it, the amount is not present, only the op_return_raw.

Could you try with this config:
"wsBaseUrl": "https://socket.paybutton.org",
"apiBaseUrl": "https://api.paybutton.org",
I just gave it a test and it seems to be working


fix(date-picker-input): require label

Closes IBM/carbon-components-react#1635
Require labelText prop for DatePickerInput for accessibility purposes.
Changelog
Changed

made labelText a required prop (made it a node type like TextInput counterpart: https://github.com/carbon-design-system/carbon-components-react/blob/master/src/components/TextInput/TextInput.js#L135)
removed labelText default prop

Thanks @asudoh! I just committed your suggestion 👍


Use mimalloc as global allocator

This will potentially improve performance instead of the default system allocator, esp. on Linux MUSL that doesn't have a good system allocator.
On Windows, which usually sees a benefit with this for highly-parallel workloads, I didn't see any perf difference though.

Indeed, then it wouldn't be much work to be done.
Can you do a new patch release that contains this?

cmake strikes again!


Badge content overflows on IE11

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

The Badge should expand to accommodate the badge content e.g.

Current Behavior 😯

The badge doesn't expand properly

Steps to Reproduce 🕹

Link:

Visit https://material-ui.netlify.com/components/badges/ on IE11

Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.1.1

React

Browser

TypeScript

etc.

The width of the badge seems to be bound by the width of the wrapped element.

The only solution I can find is to replace the flex container (display: flex) with a line height: https://stackoverflow.com/questions/46049818/flexbox-container-with-position-absolute-doesnt-fit-content-width-in-ie.

Is this something we actually want to change?
diff --git a/packages/material-ui/src/Badge/Badge.js b/packages/material-ui/src/Badge/Badge.js
index ff9530215..a1318a319 100644
--- a/packages/material-ui/src/Badge/Badge.js
+++ b/packages/material-ui/src/Badge/Badge.js
@@ -16,18 +16,13 @@ export const styles = theme => ({
   },
   /* Styles applied to the badge `span` element. */
   badge: {
-    display: 'flex',
-    flexDirection: 'row',
-    flexWrap: 'wrap',
-    justifyContent: 'center',
-    alignContent: 'center',
-    alignItems: 'center',
     position: 'absolute',
     top: 0,
     right: 0,
     boxSizing: 'border-box',
     fontFamily: theme.typography.fontFamily,
     fontWeight: theme.typography.fontWeightMedium,
+    lineHeight: `${RADIUS * 2}px`,
     fontSize: theme.typography.pxToRem(12),
     minWidth: RADIUS * 2,
     padding: '0 4px',

If the lineHeight solution is the only way, I don't think we should.


Include checks on protocols (and tissues?) in the validation view

FEATURE REQUEST
Inspiration
There is now a separate protocols load command that loads both animal treatments and MSRun protocols.  The loads run in the validation view will raise an error about missing or inconsistent protocols when adding new animal treatments in the animal/sample xlsx sheet.
Description
Modify the code in such a way that valid novel protocols do not raise an error but when a protocol is inconsistent (e.g. name matches but descriptions mismatch), the load scripts raise a useful error/exception.  This must be done in a sustainable way too, so that the validation database is left in the same state it was in before the validation.
Alternatives
There are a few alternative that have been discussed:

Run the protocols load on the validation database (using the animal/sample spreadsheet as input) as a part of the validation (being careful to not leave the validation database modified at the end)
Change the paradigm to always populate tissues, compounds, and protocols for a validation run and run the protocols load on the validation database (using the animal/sample spreadsheet as input) (clearing the entire validation database each time)
Treat the protocol loads like tissues and compounds so that when we as curators run it, it keeps the protocols synched in the validation database.  Then modify the sample table loader to not stop when it encounters a missing protocol, but report the errors to be presented to the user (i.e. buffer the errors and issue them at the end).  This is the easiest fix, but it means that users would see protocol errors on all novel protocols.

There may be other options...
John and I discussed it in the comments below and are favoring option 2.  One question that remains is: do we copy data from the default database each time or just run the consolidated protocol loads from files (and the protocol load script on all projects).  If the copy from the default database is straightforward, I'd opt for that.
Dependencies

#581

Comment
The comment from the PR that triggered the creation of this issue:
I agree.  And we could create an issue that handles it in 1 or 2 ways.  Either the sample table loader could make a treatments-tab-aware check so that no change to the validation code is necessary, or the the validation view can run the protocol loader on the submitted sample excel file before running the sample loader code, using the same design pattern of running the sample table loader before the accucor loader.  I'll reference this in a new issue.
Originally posted by @hepcat72 in https://github.com/Princeton-LSI-ResearchComputing/tracebase/pull/538#discussion_r1005935218

ISSUE OWNER SECTION
Assumptions

List of assumptions that the code will not explicitly address/check
E.g. We will assume input is correct (explaining why there is no validation)

Requirements

[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected Components
A tentative list of anticipated repository items that will be changed, labeled
with "add", "delete", or "change".  One item per line.  (Mostly, this will be a
list of files.)

change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job

DESIGN
Interface Change description
Describe changes to usage. E.g. GUI/command-line changes
Code Change Description
Describe code changes planned for the feature. (Pseudocode encouraged)
Tests

[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking

as "features I think would be nice", is if the validator finds any new compounds, tissues, or protocols that it might list them out or reformat them for potential insertion, later (like a "make a standard study directory with loading files + standardized yaml")

That would be a feature of the loading code.  All the validation code does is it runs the loading scripts and reports its errors.  Though it does go to some effort to pretty-up the output.  And I think it should remain that simple.

Note that if a treatment doesn't exist in the database, the validation will include an error like the following:

If the protocol is a standard one that has been loaded, e.g.:
python manage.py load_protocols --protocols DataRepo/example_data/small_dataset/small_obob_protocols.tsv

it will pass:

I believe that we will also at least have an inconsistency/issue WRT default protocols whose description mentions the researcher.

One thing that the validator might try is a call_command to load_protocols --protocols <submitted_animal_and_sample_table.xlsx> --database=validation prior to the sample animal loading attempt into validation.  If the protocol is encoded in the xlsx, and successfully loads into validation database, then the treated animals might be able to load, too.

That's exactly what I was thinking John, so I wonder about the consolidated load factor. Any new entries have to be consistent with previous loads, so I think we need to both load what's in the file and pre-load the consolidated protocols.

I think where I would (potentially) like to be is that the validation database is empty all the time (no script loads both databases, by default) , but when you want to validate, you :

sync the current list of selected models (compounds, tissues, protocols) from production to validation, [so some novel method that replicates a table/models from one database to the other, one-way, to validation]
select the (putative/future?) validator router,
try loading all to validation (capturing feedback),
then init that validation database clean again.
select the (putative/future?) production router (unless there is no cause to worry about database routing changes between processes; I don't know how it works)

Haven't given it much thought, though...

I think that's a good plan. I have had similar thoughts. Because the problem with loading the protocols in the submitted file and having the consolidated protocols pre-loaded, is that the clean up cannot just empty the protocols table. But I think if, like you suggest, we load compounds, tissues, and protocols with each validation, it makes the load scripts simpler and it solves the problem of cleaning out the table after a validation is performed. So I think you're right, that is the way to go.

I'm looking through this issue.  It is at least partially outdated, perhaps even fully implemented? It references the validation database, which is gone.  And the validation view now uses load_study, which loads both tissues and protocols. My only question I want to answer before closing is if the spirit of this is implemented: checks and handling of errors related to those data...


feat(validation): add a rule for KongIngress to the ValidatingWebhookConfiguration

What this PR does / why we need it:
Adds KongIngress to the ValidatingWebhookConfiguration for KIC >= 2.8 (KIC PR).
Which issue this PR fixes
Part of https://github.com/Kong/kubernetes-ingress-controller/issues/3247.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] New or modified sections of values.yaml are documented in the README.md
[x] Commits follow the Kong commit message guidelines

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

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


Issue downloading videos with youtube-dl from udemy course , I already update youtube-dl to latest version.

[udemy:course] Downloading login popup
[udemy:course] Logging in as<EMAIL_ADDRESS>[udemy:course] draft: Downloading webpage
[udemy:course] 138926: Downloading course curriculum
[download] Downloading playlist: 138926
[udemy:course] playlist 138926: Collected 58 video ids (downloading 58 of them)
[download] Downloading video 1 of 58
[udemy] Downloading login popup
[udemy] 850438: Downloading webpage
[udemy] 850438: Downloading lecture JSON
[udemy] 850438: Downloading lecture JSON
ERROR: Unable to download JSON metadata: HTTP Error 403: FORBIDDEN (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
ERROR: 'NoneType' object has no attribute 'copy'
#youtube-dl --version
2<IP_ADDRESS>
Please look into the issue and let me know , when this will fix ??

Carefully read new issue template and provide all requested information.


Proposal to add Last Service Accessed Details to IAM Entities ( User / Role / Group /Policies)

The last service accessed details from access advisor helps find whether the provided permissions are utilised efficiently.
This would be good metadata to add to IAM entities which can be further analysed for over permissions.

@rams3sh thank you for the suggestion. It is something we are planning on the roadmap and tracking it in #4. Since this (and several other reports) require waiters, we are tracking them all in the same issue. I'll close this for one for now. Thanks!


Can't open on MacOs

I went through all the similar issues and couldn't find a solution.
I am using MacOS v12.1 with M1 chip and clicking on the goneovim app does nothing. so I tried to open the executable from the command line and then got the following error
open /Users/chaitanyasharma/.goneovim/setting.toml: no such file or directory
panic: runtime error: index out of range [-9223372036854775808]

goroutine 1 [running, locked to thread]:
github.com/akiyosi/goneovim/editor.(*Window).drawBackground(0xc0003ea000, 0xc000181e68, 0x0, 0x8000000000000000, 0x8000000000000000)
	github.com/akiyosi/goneovim/editor/window.go:1750 +0x5e5
github.com/akiyosi/goneovim/editor.(*Window).paint(0xc0003ea000, 0xc000181e58)
	github.com/akiyosi/goneovim/editor/window.go:222 +0x293
github.com/akiyosi/goneovim/editor.callbackWindow18c51e_PaintEvent(0x600001755d40, 0x208d33410)
	github.com/akiyosi/goneovim/editor/moc.go:5497 +0x9d
github.com/akiyosi/goneovim/editor._Cfunc_Window18c51e_EventDefault(0x600001755d40, 0x208d33410, 0x0)
	_cgo_gotypes.go:4490 +0x45
github.com/akiyosi/goneovim/editor.(*Window).EventDefault.func1(0xc0003ea000, 0x4575668, 0xc000181e50, 0xc000181e50)
	github.com/akiyosi/goneovim/editor/moc.go:5122 +0xa5
github.com/akiyosi/goneovim/editor.(*Window).EventDefault(0xc0003ea000, 0x4575668, 0xc000181e50, 0x5)
	github.com/akiyosi/goneovim/editor/moc.go:5122 +0x4f
github.com/akiyosi/goneovim/editor.callbackWindow18c51e_Event(0x600001755d40, 0x208d33410, 0x400967b)
	github.com/akiyosi/goneovim/editor/moc.go:5117 +0x125
github.com/therecipe/qt/widgets._Cfunc_QApplication_QApplication_Exec(0xc000000000)
	_cgo_gotypes.go:2449 +0x45
github.com/therecipe/qt/widgets.QApplication_Exec(...)
	github.com/therecipe/qt/widgets/widgets-minimal.go:2848
github.com/akiyosi/goneovim/editor.InitEditor(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	github.com/akiyosi/goneovim/editor/editor.go:345 +0xf3d
main.main()
	github.com/akiyosi/goneovim/cmd/goneovim/main.go:53 +0x147

I then added an empty settings.toml and the app still didn't run with this same error

@Chaitanyabsprip
Hi,
Thanks for the issue report.
Let me check a few things about your environment in order to investigate the problem.

What is the version of nvim? The minimum nvim version that Goneovim expects is v0.6.0.
nvim --version

What is the version of Goneovim?
/Applications/goneovim.app/Contents/MacOS/goneovim --version

If you run the following from the command line, is there any change in behavior?
/Applications/goneovim.app/Contents/MacOS/goneovim -u NONE


Warning from jointRRR

Reported by edo.drenth on 21 May 2013 11:58 UTC
Checking the PlanarLoops_analytic model in Dymola 2014 creates warnings of the following format:
The following parameters with fixed = false also have a binding:
jointRRR1.n_b = {0, 0, 1}
jointRRR2.n_b = {0, 0, 1}
jointRRR3.n_b = {0, 0, 1}
Is this correct?

Migrated-From: https://trac.modelica.org/Modelica/ticket/1116

Comment by otter on 22 May 2013 07:00 UTC
This is strange. I do not get this warning message with Dymola 2014 (tried with pedantic check on/off, Evaluate on/off, on Modelica.Mechanics.MultiBody.Joints.Assemblies.JointRRR, and on Modelica.Mechanics.MultiBody.Examples.Loops.PlanarLoops_analytic). Please, provide the model where this message occurs.
I checked the code:
  final parameter Real n_b[3](
    each final unit="1",
    each fixed=false,
    start={0,0,1})
initial equation
     n_b = Frames.resolve2(frame_b.R, Frames.resolve1(frame_a.R, n_a));

and all this is correct Modelica ("start" is a guess value since fixed = false, in case nonlinear loops n_b occur).

Comment by dietmarw on 22 May 2013 07:23 UTC
The error was reported for MSL 3.2 not the development version. There the error is still present but has been fixed for MSL 3.2.1 by adding a missing each. Unfortunately the fix was not documented so it's hard to determine the exact revision when it was fixed.

Changelog modified by dietmarw on 22 May 2013 07:23 UTC
Initialisation of jointRRR corrected by adding a missing each.


housekeeping:  use new nuget package names to enable nuget namespace reservation

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
breaking, disruptive change which is required to be able to implement NuGet package verification, trust and signing program (aka bluetick)
What is the current behavior? (You can also link to an open issue here)
reactiveui                  -> ReactiveUI (if $platform == WPF use ReactiveUI.WPF instead)
reactiveui-androidsupport   -> ReactiveUI.AndroidSupport
reactiveui-blend            -> ReactiveUI.Blend
reactiveui-events           -> ReactiveUI.Events
reactiveui-events-wpf       -> ReactiveUI.Events.WPF
reactiveui-events-xamforms  -> ReactiveUI.Events.XamForms
reactiveui-testing          -> ReactiveUI.Testing
reactiveui-winforms         -> ReactiveUI.WindowsForms
reactiveui-wpf              -> ReactiveUI.WPF
reactiveui-xamforms         -> ReactiveUI.XamForms

What might this PR break?
The community. They will need to update their package references to use the new package names; I wish there was another way.
Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
See https://github.com/NuGet/Home/wiki/NuGet-Package-Identity-Verification#application-process-for-package-id-prefix-reservation

@ghuntley,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Coverage remained the same at 69.589% when pulling 7a3be3d8e113c989d16ec48e5acff20455670275 on nuget-namespace-reservations into a20c4794f743c9b9bbcaabcab5c9d88be68564cd on develop.

Coverage remained the same at 69.589% when pulling e53a033c8f9262cfb16fff3eebf772781c0b9562 on nuget-namespace-reservations into a20c4794f743c9b9bbcaabcab5c9d88be68564cd on develop.


Defaultresolver accesses current directory before box directory

When running in non-packed mode (e.g. through normal go build), the idea is (AFAIU) that the directory passed to to packr.New() is used to serve files from. However, it seems that the global default resolve also allows serving files from the working directory).
Best illustrated by an example:
$ cat main.go
package main

import (
        "fmt"
        "github.com/gobuffalo/logger"
        packr "github.com/gobuffalo/packr/v2"
        "github.com/gobuffalo/packr/v2/plog"
)

func main() {
        plog.Logger = logger.New(logger.DebugLevel)

        box := packr.New("Box", "./box")

        _, err := box.Open("/file_in_box.txt")
        fmt.Println("err=", err)

        _, err = box.Open("/box/file_in_box.txt")
        fmt.Println("err=", err)

        _, err = box.Open("/file_outside_box.txt")
        fmt.Println("err=", err)

        _, err = box.Open("/nonexistent.txt")
        fmt.Println("err=", err)
}

My file tree looks like this:
$ find
./box
./box/file_in_box.txt
./file_outside_box.txt
./main.go

So, I would expect the first Open call to succeed for the file inside the box, and the other three to fail. However, the actual output looks like this:
DEBU[2019-04-11T15:53:59+02:00] packr#New name=Box path=./box
DEBU[2019-04-11T15:53:59+02:00] packr#findBox key=Box name=Box
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#found box="{\"path\":\"/home/matthijs/foo/box\",\"name\":\"Box\",\"resolution_dir\":\"/home/matthijs/foo/box\",\"default_resolver\":null}"
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open name=/file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box key=file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=file_in_box.txt path=/home/matthijs/foo/file_in_box.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=/home/matthijs/foo/box/file_in_box.txt path=/home/matthijs/foo/box/file_in_box.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box file=file_in_box.txt key=file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open file=/file_in_box.txt name=/file_in_box.txt
err: <nil>
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open name=/box/file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box key=box/file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=box/file_in_box.txt path=/home/matthijs/foo/box/file_in_box.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box file=box/file_in_box.txt key=box/file_in_box.txt
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open file=/box/file_in_box.txt name=/box/file_in_box.txt
err: <nil>
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open name=/file_outside_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box key=file_outside_box.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=file_outside_box.txt path=/home/matthijs/foo/file_outside_box.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box file=file_outside_box.txt key=file_outside_box.txt
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open file=/file_outside_box.txt name=/file_outside_box.txt
err: <nil>
DEBU[2019-04-11T15:53:59+02:00] *packr.Box#Open name=/nonexistent.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box key=nonexistent.txt
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=nonexistent.txt path=/home/matthijs/foo/nonexistent.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#InsideResolve name=/home/matthijs/foo/box/nonexistent.txt path=/home/matthijs/foo/box/nonexistent.txt root=/home/matthijs/foo
DEBU[2019-04-11T15:53:59+02:00] *resolver.Disk#Resolve box=Box err="{\"Op\":\"stat\",\"Path\":\"/home/matthijs/foo/box/nonexistent.txt\",\"Err\":2}" key=/home/matthijs/foo/box/nonexistent.txt
err: stat /home/matthijs/foo/box/nonexistent.txt: no such file or directory

As you can see, only the last call (to the actually nonexistent file) returns an error, while the second and third are resolved relative to the working directory rather than the box directory.
Note that I added a little debug information. After these lines https://github.com/gobuffalo/packr/blob/cef464b1513d9b6cf3d4ad6d6983a716e048e89d/v2/file/resolver/disk.go#L25-L29
I added this line:
    plog.Debug(d, "InsideResolve", "root", d.Root, "name", name, "path", path)

Also note that some debug output is missing, since all the parser initialization happens before I set the loglevel.
As you can see, the Disk::Resolve function is called twice. Both times the root directory seems bogus (referring to the directory, not the box), but the second time the name parameter is already a full path (meaning that Disk::Resolve does not really have anything useful to do).
This seems to stem from the Box::Resolve function, which does this:
https://github.com/gobuffalo/packr/blob/v2.1.0/v2/box.go#L196-L220
Essentially, it always tries to use the resolver.DefaultResolver first (also the box' defaultResolver, but that's not set here). The default resolve is defined as: https://github.com/gobuffalo/packr/blob/cef464b1513d9b6cf3d4ad6d6983a716e048e89d/v2/file/resolver/resolver.go#L15-L20
IOW, it looks in the current directory the first time it is called, and ignores its root directory when it is called for the second time.
All this seems confusing to me: I would expect such a box to have its own disk resolver with a proper root path. I also wonder what the point of a global default resolver is. Resolving files in the current directory sounds like a potential security issue. Finally, I wonder why Box::Resolve does this fallback to the box' ResolutionDir, since that sounds like a task for the resolver rather than this function.
It could be that the actual problem is that I have boxes without a defaultResolver of their own, in which case the parsing might be at fault (but even then, the code pointed above makes no sense to me, and if some of it is not meant to be used, it should probably be removed?).

(w00ps, submitted my issue to soon. Description updated now)

Hi,
I'm not sure what the expected behavior is here.
But I agree that it might get a little confusing, especially when switching between dev mode and built mode.
When using a simple file structure like this one:
packr-app/
├── app
│   └── test.html (Right one)
├── go.mod
├── go.sum
├── main.go
└── test.html (Wrong one)

with main.go:
package main

import (
	"log"
	"net/http"

	"github.com/gobuffalo/packr/v2"
)

func main() {
	var app = packr.New("App", "./app")

	http.Handle("/", http.FileServer(app))

	log.Fatal(http.ListenAndServe(":8080", nil))
}

I have two versions of test.html, the "right one" in app/ and the "wrong one" packr-app/.
Running go run . in packr-app/ and opening http://localhost:8080/test.html gets me the wrong one, which is a little unexpected.
After executing packr2 in packr-app, running again go run . and opening http://localhost:8080/test.html now gets me the right one, which is what I expected.
@markbates Is this the expected behavior ?

any package level solution
var _box *packr.Box
func init() {
    _, filename, _, _ := runtime.Caller(0)
    _box = packr.New("name", "../../assets/templates") // relative to this file path
    _box.DefaultResolver = &resolver.Disk{Root: path.Clean(path.Join(path.Dir(filename), _box.Path))}
}

that works for me using this box at any level of app entry point


OSError: [Errno 2] No such file or directory

root@5e60d163e16d:/workspace/gem5-aladdin/sweeps# python generate_design_sweeps.py benchmarks/machsuite.xe
use benchmarks.designsweeptypes.Gem5DesignSweep
begin Gem5DesignSweep single
use benchmarks.machsuite.*
generate configs
generate dma_trace
generate gem5_binary
set output_dir "machsuite"
set source_dir "../src/aladdin/MachSuite"
set simulator "gem5-cpu"
set memory_type "spad"
sweep cycle_time from 1 to 5
set unrolling for bfs_bulk.bfs.loop_horizons 1
On line 4: set unrolling for bfs_bulk.bfs.loop_horizons 1
XenonSelectionError: Failed to find object named b.f.s._.b.u.l.k
root@5e60d163e16d:/workspace/gem5-aladdin/sweeps#

Duplicate of https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/gem5-aladdin-users/8eL3zOQj7GE/lxhX3mCNAAAJ.

I'm newbie to use gem5 and this issue also occurs in my environment.
I'm not sure it's the correct solution but removing the indexed symbol makes it work.
diff --git a/base/common.py b/base/common.py
index 991253c..efdf255 100644
--- a/base/common.py
+++ b/base/common.py
@@ -28,7 +28,7 @@ def getSelectedObjs(select_tokens, env):
select_tokens.append(LIT_STAR)
current_view = env

for token in select_tokens[0]:

for token in select_tokens:
if token == LIT_STAR:
break
try:

Do you have the end <sweep_name> statement at the end?

Do you have the end <sweep_name> statement at the end?

yes, I ran the example, machsuite.xe.


Can't unzip large file ~6Gb

Hello)
Im trying to use UnzipKit and I have a little issue. I have an zip archive with one large file about ~6Gb.  I have an error when I'm trying to unzip this file.
I think I found similar issue
https://github.com/abbeycode/UnzipKit/issues/25
my code:
        do {
            let archive = try! UZKArchive(url: URL(fileURLWithPath: "/Users/alex/Desktop/A.zip"))
            let filesList = try archive.listFilenames()
            let filesInfoArchive = try archive.listFileInfo()
            try archive.extractFiles(to: "/Users/alex/Desktop/folder", overwrite: true, progress: nil)
            print(filesList)
        } catch let error as NSError {
            print("Exeption ...\(error)")
        }

Console:
Error Domain=UZKErrorDomain Code=-103 "Bad zip file" UserInfo={NSLocalizedFailureReason=Bad zip file, NSUnderlyingError=0x60000025fb00 {Error Domain=UZKErrorDomain Code=-103 "Bad zip file" UserInfo={NSLocalizedFailureReason=Bad zip file, NSLocalizedRecoverySuggestion=Error opening archive (-103), NSURL=file:///Users/alex/Desktop/A.zip, NSLocalizedDescription=Bad zip file}}, NSLocalizedRecoverySuggestion=Bad zip file, NSURL=file:///Users/alex/Desktop/A.zip, NSLocalizedDescription=Bad zip file}
Could you please provide some hint on this situation? Thanks)

I'm running on macOS.

How did you install, with CocoaPods? If so, you can try stepping through and looking at the line where it's failing. Also, which version of UnzipKit are you using? Are there multiple different files like that you're having problems with, or is it just this one? I'd offer to take a look and see what I can determine, but it's a little tough for you to send me a 6 GB file to look at it myself, though.

hello) Sorry for hight ping respond.
Steps to reproduce:

Download linked file
Execute code from test project

I’m using ‘1.8.5’ on macOS 10.13.
Simple test project
https://drive.google.com/open?id=1LzpytHWCBBm1c_ss1PkVYuMZzAxM8zqF
Test file
https://drive.google.com/open?id=1p3CRu-rj9n2eVOkxn-iOlNGF_bSUrq_B
Thanks)

Updated simple test project
https://drive.google.com/open?id=1_H_sisp4_L0D-erjSq1UurQdRr0s0PK8

@alexthgil That's super helpful, thanks! I'll take a look when I can

I am SO sorry it took me a year (exactly a year, which is creepy) to look at this. I largely work on open source projects when I'm away from reliable internet, and kept forgetting to download the file when I was.
I looked at it now, and I'm not sure the 6 GB file you sent is actually a zip format archive. Is there any app (or library) you've used to successfully extract it? I tried BetterZip without success. I also opened it up in a hex editor to look for the Zip format header at the beginning of every file, and didn't see one.
I'm going to close this as "works as designed", but please reopen it if you have additional info to help me solve it.


failfast for python client?

It seems disabling failfast for python clients is not implemented. Would be nice to have it.
As a workaround, I tried calling channel._channel.check_connectivity_state(True) but it is not as effective (and also it is not async).

Dupe of https://github.com/grpc/grpc/issues/6770

@mirzazadeh: this smells like a duplicate of issue 6770; do you agree?

Yes, I agree, but IMO this is not P2. It makes grpc python client quite unreliable. Unless there is a good workaround.

@mirzazadeh  Let's take the discussion to the original issue #6770. It's better to have it unified there.
I'd be interested in hearing more about your scenario in which you see gRPC Python as unreliable in comments on #6770.
While I feel your pain, as you can see in the issue tracker, we have not had that many requests to add this urgently in the past two years. We, being an open source project, are also be quite happy to review and accept patches if you have additional cycles and can help us out there.