import of bowser and moment broken with 1.6.2

I use moment and bowser in a component in my project. The import of these libraries worked before upgrading from angular 5.1.1 and angular-cli 1.6.1 to angular 5.1.2 and angular-cli 1.6.2.
Versions
Angular CLI: 1.6.2
Node: 8.1.0
OS: linux x64
Angular: 5.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.0.2
@angular/cli: 1.6.2
@angular/flex-layout: 2.0.0-beta.12
@angular/material: 5.0.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.2
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Other versions
    "bowser": "1.9.0",
    "moment": "2.20.1",
    "moment-es6": "1.0.0",

Repro steps

This is a reduced version of my component:

import {Component} from "@angular/core";
import moment from "moment-es6";
import bowser from "bowser";

@Component({
  selector: "dc-date",
  templateUrl: "./dc-date.component.html"
})
export class DcDateComponent {
  touchUi = bowser.mobile || bowser.tablet;
}

ng serve
error in browser while opening the app

Observed behavior
ERROR TypeError: Cannot read property 'mobile' of undefined
    at new DcDateComponent (dc-date.component.ts:72)
    at createClass (core.js:12470)
    at createDirectiveInstance (core.js:12315)
    at createViewNodes (core.js:13776)
    at callViewAction (core.js:14210)
    at execComponentViewsAction (core.js:14119)
    at createViewNodes (core.js:13804)
    at callViewAction (core.js:14210)
    at execComponentViewsAction (core.js:14119)
    at createViewNodes (core.js:13804)

Desired behavior
The bowser import no longer seems to work. The component is part of a custom library we maintain that is packaged with rollup. We had some issues using import statements with the following form:
import * as bowser from bowser
They worked as long as the app wasn't packaged as a library. If our applications imported the library, the imports caused issues. Switching to the imports in this form fixed that issue:
import bowser from bowser
But now, the latest version of angular-cli seems to have issues with these import statements.

When you upgraded the project did the bowser package get updated as well?  From looking at the project’s change log, it looks like the latest minor version made changes to its typings.

I already checked that option. The version of Bowser changed from 1.8.1 to 1.9.0. But I was able to upgrade this single dep without code changes, while staying on angular 5.1.1.

1.9.1 just came out (today) and the only item in the change log is “fixed” typings.d.ts

Thanks, I will check it out and keep you posted.

I'm not able to get 1.9.1 yet with npm, since it's still so new. But I rolled back to version 1.8.1 and I still get the same error. I also looked at the changes to the typings and they only added a property.

import bowser from 'bowser'; shouldn't work.  There's no default import defined.  import * as bowser from 'bowser'; is correct per the typings.
Also, for information related to packaging an angular library, please see here: https://goo.gl/jB3GVv

I had a similar issue when using js-cookie.  import Cookies from 'js-cookie';  Cookies returned undefined on angular 5.1.2 and angular-cli 1.6.2. downgrading cli to 1.6.1 fixed the problem.


TypeError: Path must be a string. Received null; at index.js:116:15

error output
% ❯ verb                                                                                 November 04, 06:02:12
[06:06:55] starting verb
[06:06:59] ✔ running tasks: [ 'readme' ]
path.js:7
    throw new TypeError('Path must be a string. Received ' + inspect(path));
    ^

TypeError: Path must be a string. Received null
    at assertPath (path.js:7:11)
    at Object.resolve (path.js:1146:7)
    at Function.resolve (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/parse-git-config/index.js:116:15)
    at Function.parseSync [as sync] (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/parse-git-config/index.js:79:24)
    at Schema.module.exports (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/expand-pkg/lib/expanders/git.js:13:36)
    at Schema.normalizeField (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/map-schema/index.js:557:16)
    at Schema.update (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/map-schema/index.js:246:8)
    at Schema.module.exports (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/expand-pkg/lib/expanders/owner.js:14:10)
    at Schema.normalizeField (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/map-schema/index.js:557:16)
    at Schema.normalize (/home/charlike/.nvm/versions/node/v7.0.0/lib/node_modules/verb-generate-readme/node_modules/map-schema/index.js:497:27)

just found it, because just dont have .git/ dir.

Try reinstalling verbose/verb#dev and verb-generate-readme.
This issue on generate is probably referring to the same problem you're having. We updated the versions of the other modules to include the parse-git-config version that fixes this.

Oh yea, really. Forgot that. Probably will work.


Fix typo

Thanks.  Nice that the page at https://github.com/marketplace/actions/setup-ruby-pkgs is from the main branch, no need for a new release.


Yarn

See if we can deploy on Heroku. If so then we are good to go with Yarn

Closing in favor of #110!


Update verify script

Change regex from hardcoded version to any value when changing module source for local testing. Closes #54.
Adds a check to skip downloading Terraform binary if a zip is already present. This is useful during local testing to speed up successive runs of verify.sh when fixing a failure.
Update Terraform version to latest.

Thanks for the review! I've made the suggested change.


glm-4-9b-chat

https://modelscope.cn/models/ZhipuAI/glm-4-9b-chat
thanks !

Thank you for submitting this. Merging with https://github.com/ollama/ollama/issues/4826


BIGTOP-3528. Bump Oozie to 5.2.0

https://issues.apache.org/jira/browse/BIGTOP-3528
We need to fix following issues

compilation error due to version mismatch

hive
hadoop
log4j2
httpclient

migration from Tomcat to Jetty OOZIE-2317

I fixed compilation erros and issues in install_oozie.sh. init script should be fixed too for OOZIE-2317.

@iwasakims Thank you for addressing this! A few comments:

Oozie 5.2.1 has been released recently. How about upgrading to that?

On Ubuntu 18.04 and 20.04, this PR failed with the following error.

ln -s -f /var/lib/oozie/ext-2.2 debian/oozie/usr/lib/oozie/webapps/oozie/ext-2.2
ln: failed to create symbolic link 'debian/oozie/usr/lib/oozie/webapps/oozie/ext-2.2': No such file or directory
make[1]: *** [debian/rules:40: override_dh_auto_install] Error 1
make[1]: Leaving directory '/home/vagrant/bigtop/output/oozie/oozie-5.2.0'
make: *** [debian/rules:27: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -b
 failed

> Task :oozie-deb FAILED

Oozie 5.2.1 has been released recently. How about upgrading to that?

Sure. The patch0 is applicable without update.

ln -s -f /var/lib/oozie/ext-2.2 debian/oozie/usr/lib/oozie/webapps/oozie/ext-2.2
ln: failed to create symbolic link 'debian/oozie/usr/lib/oozie/webapps/oozie/ext-2.2': No such file or directory

fixed this error.

+1, I successfully built and deployed Oozie 5.2.1 with this PR on CentOS 7, 8, Debian 10, and Ubuntu 18.04.
We possibly have to fix its puppet manifest and/or smoke test additionally, because the smoke test failed on my environment. But it can be addressed as another follow-up issue.
Thanks @iwasakims for working on this!


Getting Chai is not defined errors

Hello,
After installing and running I get the following error:

By the way, using an older version (with older dependencies) of this project works fine.

Ok I found the bug, it is with the endsWith function:
var endsWith = function(substr) {
  return function(str) {
    return str.indexOf(substr) === (str.length - substr.length);
  };
};

I had a case where str.length - substr.length === -1, and it returned a false positive.
Wanted to create a pull request, but saw that it is already fixed.
When will it be deployed?

I am getting a similar error:
C:\Users\mchambe4\dev\simple\client>node ./node_modules/gulp/bin/gulp.js unit-tests-dev
[16:29:31] Using gulpfile ~\dev\simple\client\gulpfile.js
[16:29:31] Starting 'unit-tests-dev'...
[16:29:31] Starting Karma server...
WARN [karma]: Port 9876 in use
INFO [karma]: Karma v0.12.37 server started at http://localhost:9877/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.8 (Windows 7 0.0.0)]: Connected on socket fMujwCqRPdmidI3BtCYV with id 16821903
PhantomJS 1.9.8 (Windows 7 0.0.0) ERROR
  ReferenceError: Can't find variable: chai
  at C:/Users/mchambe4/dev/simple/client/node_modules/karma-sinon-chai/node_modules/sinon-chai/lib/sinon-chai.js:17

This works OK on mac, but now I have moved exactly the same setup to Windows, I can no longer run my unit tests.
From that file:
/* istanbul ignore else */
if (typeof require === "function" && typeof exports === "object" && typeof module === "object") {
    // NodeJS
    module.exports = sinonChai;
} else if (typeof define === "function" && define.amd) {
    // AMD
    define(function () {
        return sinonChai;
    });
} else {
    // Other environment (usually <script> tag): plug in to global chai instance directly.
    chai.use(sinonChai);
}

I would expect the condition on the first line to return true because I am running in Node, but for some reason module is not defined.
Any ideas?


Cucumber shorterThan: Running a shorter than for a number or temporal data value does not fail with an error

Bug Report
A shorter than constraint was added to an equal to numeric & temporal value. In these cases it was expected that the system should display an error to the user showing that this constraint would not work for these data types, but no error is shown.

Scenario: Running a 'shorterThan' request using a number to specify a the length of a generated numeric type field should fail with an error message
Given there is a field foo
And foo is shorter than 5
And foo is equal to 1234
Then I am presented with an error message
And no data is created

Scenario: Running a 'shorterThan' request using a number to specify a the length of a generated temporal type field should fail with an error message
Given there is a field foo
And foo is shorter than 25
And foo is equal to 2010-01-01T00:00:00.000
Then I am presented with an error message
And no data is created

Steps to Reproduce:

Run tests from the feature file ShorterThan.feature
See that there is a failure for the test Scenario: Running a 'shorterThan' request using a number to specify a the length of a generated numeric type field should fail with an error message
Note that the error message displayed showing a mismatch of an expected error where none was generated.
See that there is a failure for the test Scenario: Running a 'shorterThan' request using a number to specify a the length of a generated temporal type field should fail with an error message
Note that the error message displayed showing a mismatch of an expected error where none was generated.

Expected Result:
The generator should throw an error as the shorterThan constraint can not work with non-string fields.
Actual Result:
The test fails with an error that indicates that no error was generated:

java.lang.AssertionError:
Expected: is
but: was
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at com.scottlogic.deg.generator.cucumber.steps.GeneralTestStep.dataGeneratorShouldError(GeneralTestStep.java:83)
at ✽.I am presented with an error message(C:/DataGenerator/data-engineering-generator/generator/src/test/java/com/scottlogic/deg/generator/cucumber/ShorterThan.feature:81)

Environment:
shorterThanUpdated Branch running on IntelliJ. Run on full data generation strategy.
Additional Context:
Test set to @ignore and this issue is raised as an enhancement to the framework.

@sl-slaing to review

Priority: High to investigate at least

Accidentally closed

@sl-slaing , @tyankovasc, @cakehurstryan  - This is related to our key decisions discussion.
If we take the approach where:

Constraints should not imply type (unless they are explicit of type constraints)
Each constraint reduces the possible values for a field from a universal set of values

Then there is no issue with the above tests and they should be deleted (or changed to expect data).
Here is why:

foo does not have a explicitly defined type meaning it can be any type.
constraint foo is shorter than 5 means that any strings generated must be shorter than 5 (eliminates any string values greater than 5 from universal set)
constraint foo is equal to date means foo can only be that date (eliminates any values except the date value from universal set)

The date constraint is a further restriction on the shorter than constraint. It is analogous to:
Foo in [A B C] AND
Foo in [A B]
I.e. the first constraint is ultimately pointless but not contradictory and therefore we don't error.

Issue closed in line with conversation above. Soft contradictions are planned to emit any and all possible data and ignore illogical constraints.


Pulling saved trips in my trips

Able to view and update saved trips in 'My Trips'
small change to hasOwnProperty usage in flights controller

going to make another PR with davids login changes


[DOCFIX] update Chinese document

I have updated Chinese document docs/cn/Clients-Hadoop.md to make it more native. In detail, I changed 'Hadoop文件操作会被翻译为文件系统操作。' to 'Hadoop 文件操作会被转换为文件系统操作。'.

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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


Zoom doesn't work on Microsoft surface RT and PRO

While trying to zoom on a surface RT devise the browser zooms the whole page instead of the iscroll.
this also happens on surface PRO with firefox.

Yeah would be great if iScroll could support Windows on the Surface devices

The solution in this answer might help: https://github.com/cubiq/iscroll/issues/583

No that doesn't help. Zoom still doesn't work. I understand you don't have a device to test it on? I will have a look if I can find some time to fix it and send you a pull request.


HDDS-10573. [hsync] Add a freon tool to benchmark hsync/write concurrency.

What changes were proposed in this pull request?
HDDS-10573. [hsync] Add a freon tool to benchmark hsync/write concurrency.
Please describe your PR in detail:
Related to HDDS-9844. We should have a simple tool that does what HBase WAL do: a writer thread to write into output stream buffer, and a thread pool of threads that do hsync non-stop.
Running a full suite of HBase and ycsb is too clunky. A simple tool can help us iterate fast.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10573
How was this patch tested?
Unit test

Superseded by #6925 so close this one.


set-env deprecation

Builds using this action are currently failing due to:
Extracted triplet from command line 'x64-windows'.
  Error: Unable to process command '::set-env name=RUNVCPKG_VCPKG_TRIPLET::x64-windows' successfully.
  Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
  Set task output variable 'RUNVCPKG_VCPKG_TRIPLET_OUT' to value: x64-windows
  Error: Unable to process command '::set-env name=RUNVCPKG_VCPKG_TRIPLET_OUT::x64-windows' successfully.
  Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

It appears  set-env needs to be replaced

Adding:
env:
        ACTIONS_ALLOW_UNSECURE_COMMANDS: true

to the workflow stage is a temporary workaround

@ataffeqeexo  both run-vcpkg@v4 or run-vcpkg@v5 solve the issue (as both contains the security fix)

Ahh thanks for the info, didn't realize there was an update


DS-2871 remove Modernizer from Mirage; it's unused

https://jira.duraspace.org/browse/DS-2871

@helix84 , Moderizr appears to be used here https://github.com/DSpace/DSpace/blob/master/dspace-xmlui-mirage2/src/main/webapp/scripts/forms.js#L11

@terrywbrady it is used by mirage2, but it's referred to in that theme at https://github.com/DSpace/DSpace/blob/master/dspace-xmlui-mirage2/src/main/webapp/xsl/core/page-structure.xsl#L268
@helix84 's PR just removes modernizr from Mirage, not MIrage2, so i think this is all OK.
+1 from me!

Sorry for the delayed response, +1 from me as well.

Merging. Looks good to me as well, already at +2.


WAYK-2198: allow hostnames in addition to IPs

I think you need to run cargo format to fix the build


Decompress after reading in blocks

As identified in #17, a key area of weakness is my strategy for inflating compressed data. Currently, I inflate while reading the data, which is likely slower than reading a contiguous block followed by in-memory inflation. Plus, I should consider spinning out (some of) the compression code into separate package for reusability sake.

Plus, I should consider spinning out (some of) the compression code into separate package for reusability sake.

The compression code is being moved over to https://github.com/tlnagy/Balloons.jl

#127 implements chunked input

Agreed, this issue is mostly superfluous in v0.8.0+


Unable to generate any certificate

Hello !
It's been a few days now that I'm looking for how to generate a certificate for a subdomain on my NAS.
I use the nginx-proxy container from jwilder, with the JrCs companion container.
My tests are done on the Portainer container, but I made others with the container NextCloud from linuxserver.
All containers are up to date, via watchtower.
The parameters of the different containers (filled in via the OpenMediaVault graphical interface and its docker plugin ; only pertinent informations, for this case, are here):
nginx-proxy :

80:80 tcp et 443:443 tcp
/var/run/docker.sock:/tmp/docker.sock:ro
/docker/certs:/etc/nginx/certs
/docker/nginx_proxy/dhparam:/etc/nginx/dhparam
--label com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy

companion :

/docker/nginx_proxy/etc/nginx/vhost.d:/etc/nginx/vhost.d
/docker/nginx_proxy/usr/share/nginx/html:/usr/share/nginx/html
/var/run/docker.sock:/var/run/docker.sock:ro
/docker/certs:/etc/nginx/certs
volume from nginx-proxy

Portainer :

59000:9000 tcp
VIRTUAL_HOST = sub.domain.com
LETSENCRYPT_HOST = sub.domain.com
LETSENCRYPT_EMAIL =<EMAIL_ADDRESS>
Note that joining Portainer via the sub.domain.com address works. Ports 80 and 443 are open in my router.
Only, when the companion tries to generate a certificate, I have the following error in the container log
: CA marked some of the authorizations as invalid, which likely means it could not access [...]
I did other tests, by informing VIRTUAL_PORT, VIRTUAL_PROTO, etc. but I still have the same result (I also had an automatic redirection of the HTTP to the HTTPS, without really understanding why).
Is there a problem in my way of doing things?
If more information is needed, I can try to provide you with it.
Regards,
schizophrene

I have the exact same problem.
I use the setup in separate containers using dockergen and nginx:stable to proxy a few apache containers. This has worked for me so far and I already retrieved several certificates.
It's only for a few days now, that I get the same error @schizophrene has, whenever I try to add a new virtual host.
This is my compose file:
version: '2'

services:
  nginx:
    image: nginx:stable
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /etc/nginx/conf.d
      - /etc/nginx/vhost.d
      - /usr/share/nginx/html
      - /srv/docker-staging/certs:/etc/nginx/certs:ro
      - /srv/docker-staging/htpasswd:/etc/nginx/htpasswd

  docker-gen:
    image: jwilder/docker-gen
    container_name: docker-gen
    command: -notify-sighup nginx -watch /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
    volumes_from:
      - nginx
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - ./nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl
    depends_on:
      - nginx

  letsencrypt:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt
    volumes_from:
      - nginx
    volumes:
      - /srv/docker-staging/certs:/etc/nginx/certs:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      NGINX_PROXY_CONTAINER: nginx
      NGINX_DOCKER_GEN_CONTAINER: docker-gen
    depends_on:
      - docker-gen

networks:
  default:
    external:
      name: proxy

The containers are started this way:
httpd:
        image: httpd:${CONTAINER_HTTPD_VERSION}
        expose:
            - "80"
        volumes:
            - "${PROJECT_ROOT}:/var/www:cached"
        environment:
            VIRTUAL_HOST: ${VIRTUAL_HOST}
            LETSENCRYPT_HOST: ${VIRTUAL_HOST}
        networks:
            - proxy
            - default

Any idea whats causing the problem?

What

OS
Docker version
jrcs/letsencryt-nginx-proxy-companion version

are you using ?
If using jrcs/letsencryt-nginx-proxy-companion:latest, did you pull a new version of the container lately ?
Can you try those troubleshooting steps : https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/wiki/Invalid-authorizations especially the part at the end about creating a dummy file inside /usr/share/nginx/html/.well-known/acme-challenge and accessing it from outside the host ?

Hi guys,
OS = Linux version 4.17.0-0.bpo.1-amd64<EMAIL_ADDRESS>(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.17.8-1~bpo9+1 (2018-07-23)
Docker version = Docker version 18.06.0-ce, build 0ffa825
Companion version = appearly the last, a new pull lets me the version of 08/13
I did 2 troubleshootings steps, possibly related to my problem :

CAA answers : OK
dummy file : NOK, 503 Service Temporarily Unavailable, 404 with subdomain in URL

I noticed that I have again an automatic redirection to HTTPS, even for http://domain.tld (where there is nothing, so I think it's caused by nginx-proxy)
JSON from container logs : I will send you an email with full logs (I don't know what is important in).
Thank you !

@schizophrene can you try with jrcs/letsencryt-nginx-proxy-companion:v1.8.1 ?

I tried, but without more success (but I did it from my phone).
I will try tomorrow from my computer.

For me it was a firewall problem.
A coworker created a rule to block all http traffic except from our IP.


cmd/vet: printf checker does not know about fmt.Formatter

The printf checker should allow any verb for a value that implements fmt.Formatter. It does not.
package main

import "fmt"

type T int

func (t T) Format(f fmt.State, c rune) {
	f.Write([]byte{byte(c)})
}

func main() {
	var t T
	fmt.Printf("%z\n", t)
}

$ go run formatter.go
z
$ go tool vet formatter.go
formatter.go:13: unrecognized printf verb 'z'

As an aside, it looks like the implementation of fmt.Stringer detection in cmd/vet could be simplified by using go/types-based interface satisfaction analysis. (See the copylock check for an example.) I suspect the printf check was written before go/types had that functionality.
cc @valyala @robpike

When this is fixed, we should revert CL 28959.


Non statical controller class

Hi, currently im using Flight with statical classes as controller. Would it be possible to use non-statical method?

@javasworks check solution from here https://github.com/mikecao/flight/issues/227


Multi-level flow inside for loops and conditions, bug for this usage scenario - fixed

Thank you for creating TagUI. It helps me a lot in my daily work.
I just upgraded from TagUI 5 to TagUI 6 and came across the following issue in version 6.14:
I have 3 files: main.tag, flow1.tag and flow2.tag with content as follows:
main.tag:
for i from 1 to 2
 echo main: loop = `i`
 tagui flow1.tag

flow1.tag:
for j from 1 to 2
 echo \ flow1: loop = `j`
 tagui flow2.tag

flow2.tag:
echo \  flow2: A
echo \  flow2: B
echo \  flow2: C

However, when I run tagui main.tag -h, the output is as follows (which is not as expected):
main: loop = 1
 flow1: loop = 1
  flow2: A
 flow1: loop = 2
  flow2: A
  flow2: B
  flow2: C
main: loop = 2
 flow1: loop = 1
  flow2: A
 flow1: loop = 2
  flow2: A
  flow2: B
  flow2: C

Looking at the .raw file generated, a curly bracket is closed early (right after the first line of flow2.tag)
main.raw:
for i from 1 to 2
{
echo main: loop = `i`
for j from 1 to 2
{
echo \ flow1: loop = `j`
echo \  flow2: A
}
echo \  flow2: B
echo \  flow2: C
}

Not sure if there is any workaround with this issue. Thank you for your time.

Closing issue, change included in latest packaged release - https://github.com/kelaberetiv/TagUI/releases/tag/v6.46.0


Using deploy instead of script for docker build

First of all: Thanks for providing this poc!
As an alternative approach for the .travis.yml configuration I would suggest to move the generation of the docker image into the deployment hook.
This way topic teams could easily decide to release based on tags or specific branches instead of every single commit. Which is very valuable especially in the beginning until we have enough unit tests and other safe-guards in place.
The configuration would look as follows:
language: node_js
sudo: required
node_js: node
services: docker
branches:
  only:
    - master
# npm install + npm test are run by default for this language
# custom build commands can be added in the `script` and `before_script` hooks
deploy:
 provider: script
 script: make default
 on:
  tags: true

Moved to https://github.com/ricardo-ch/platform-template-nodejs/issues/1


Potential bugs re. 'static inline' and static variables

Prompted by some discussion on Slack, haven't looked for problems.
If you put
static inline void f(void)
{
	static int x;

	...
}

in a header, you'll get a separate x variable for each translation unit that includes it. It works just like a regular static function there. The inline makes no difference.
@tautologyclub might've found some stuff that assumes x is shared.

Yeah apart from coap_next_id() from coap.h (fix incoming in https://github.com/zephyrproject-rtos/zephyr/pull/19217), I found one instance that looks slightly dubious in subsys/net/ip/net_private.h:
static inline char *net_sprint_ll_addr(const u8_t *ll, u8_t ll_len)
{
	static char buf[sizeof("xx:xx:xx:xx:xx:xx:xx:xx")];

	return net_sprint_ll_addr_buf(ll, ll_len, (char *)buf, sizeof(buf));
}

Not sure it will cause any bugs, but it certainly looks shady. Note that in the case of coap_next_id(), it DID cause very serious bugs.
Note: my methodology for finding them is probably not perfect (basically a chain of twenty grep/cat pipes). Coccinelle might be better?

I did some experimentation and disassembly with minimal examples and gcc (GCC) 8.3.1 20190223 (Red Hat 8.3.1-2). With this compiler I verified that every translation gets its own, private copy of static int x as expected. If that's what the author intended that I wouldn't necessarily call it "shady". Missing a comment maybe.
The bad thing about the ancient "translation units" concept is the lack of LTO and other fancy stuff. The good thing about the ancient "translation units" concept is its simplicity: the compiler treats .h and .c code the same.

The inline makes no difference.

I also verified this.  For these toy examples inline makes absolutely zero difference. The compiled code is exactly the same with or without 'inline. gcc does inline that simple function with -O1 and above, otherwise it doesn't; the inline specifier doesn't matter.

Coccinelle might be better?

Maybe - that or some LLVM plugin/ad-hoc script?

With this compiler I verified that every translation gets its own, private copy of static int x as expected. If that's what the author intended that I wouldn't necessarily call it "shady". Missing a comment maybe.

If that's not what the author intended and the author was trying to share a global across translation units, then I wonder how that passed any testing (or code review).
@tautologyclub if you go back in time before your PR #19217 , can you find any meaningful test actually using this code and passing?

I don't think obviously inlinable functions like 'static int x; return x++' really proves anything, but I also don't believe gcc does anything but the expected (ie the variable probably always becomes translation-unit global). But neither the coap example nor the one I pasted above seems like good use cases for such statics. The question is if there IS a good use case for them - to me they seem to be just as bad (or worse) style wise as bracketless ifs, trigraphs, weird switch case/goto hacks, long jumps etc - just begging for bugs for no practical gain.

I don't think obviously inlinable functions like 'static int x; return x++' really proves anything

It doesn't prove anything wrt to optimizations and speed, however I found it interesting wrt to this particular issue  and the general concept that inline never makes any functional difference. static is all what matters here.

The question is if there IS a good use case for them -

I just posted this in #19217, would have been better here sorry:

I could think of some corner case(s) where you want to avoid the stack growing too much and you know for sure there won't be any concurrent use but... yeah, that would deserve a big fat comment at the very least.

BTW neither gcc -Wall -Wextra  8.3.1 20190223 nor clang -Wall -Wextra 7.0.1-6.fc29 says anything when doing this.

I found one instance that looks slightly dubious in subsys/net/ip/net_private.h:
static inline char *net_sprint_ll_addr(const u8_t *ll, u8_t ll_len)
{
	static char buf[sizeof("xx:xx:xx:xx:xx:xx:xx:xx")];

	return net_sprint_ll_addr_buf(ll, ll_len, (char *)buf, sizeof(buf));
}

Not sure it will cause any bugs, but it certainly looks shady.

This indeed looks shady, but actually using static buf here is good (although it was unintentional). This func is only used in various debug prints and having static buf here makes it unlikely that various debug prints would overwrite each other. Only issue is that we are increasing memory consumption but luckily it is only happening if debug level is high.

So @jukkar you're saying the code above is a trade-off between memory use and correctness where invocations from different translation units are isolated from each other but invocations from the same translation unit are not and could (harmlessly?) corrupt debug output? Just rephrasing to make sure I understood.

but... yeah, that would deserve a big fat comment at the very least.

Sounds pretty ad hoc to me. Either you need reentrancy or you don't. What happens if I call that sprintf function twice in the same stack? Etc... Can you truly 100% vouch for correctness in all such possible situations?

@marc-hb regarding tests etc, I don't believe the coap function was rigorously tested, at least not the aspect of getting called from multiple translation units. It's such a meta thing to test though so I can't blame the author.

So @jukkar you're saying the code above is a trade-off between memory use and correctness where invocations from different translation units are isolated from each other but invocations from the same translation unit are not and could (harmlessly?) corrupt debug output? Just rephrasing to make sure I understood.

There was no intentional trade-offs here :) The function in question was never meant to guarantee that debug output is not corrupted. So originally the idea was to minimize memory usage by using static variable. As the function is inlined, it is actually harder to corrupt the output which is nice in this case.

The compiler is behaving as expected, removing bug label.

The function in question was never meant to guarantee that debug output is not corrupted

I realize this function is located in a file named something_PRIVATE.h, yet I still think this deserve a big comment/warning in the code, something like "very sharp knife here, don't do this at home", etc.

my 5 cents here, we should forbidden this kind o feature. This is totally error prone, the variable is defined in each translation unit that the function is used, and the behaviour is likely not what the developer wanted, this will work as static for each translation unit but not globally.
@marc-hb  @tautologyclub is there anything gating this change ? I can easily do a coccinelle script to change / enforce it.

Well I think it definitely should be done, but I didn't get the impression that there is buyin from everyone involved. To me that sprintf looks like it's 100% begging for trouble.

my 5 cents here, we should forbidden this kind o feature. This is totally error prone, the variable is defined in each translation unit that the function is used, and the behaviour is likely not what the developer wanted, this will work as static for each translation unit but not globally.

I agree. People should not be doing this.

@ceolin first you should find the instances with coccinelle, I doubt my search was exhaustive

There is a deeper problem, that static inline ... isn't actually the best way to do inline functions in gcc. It usually works, except that depending on certain things, like this construct, it will end up putting code for the function in every module that uses it. This should be warnable against, by adding -Winline, which will warn about function that can't be inlined.
Another approach is to use extern inline in the header file. This will generate a link error if something cannot be inlined. It is possible to use ifdefs and have a single C file include the inline, without the extern which will generate code for the function.
It probably isn't worth converting to this, and better to just avoid static variables in an inline function.


Add test for Eno->Helm migration

Adds a test case to make sure Helm releases can adopt resources created by Eno (of course hopefully no one ever uses this 🙃 )

I really hope no one uses this lol


Document how to import rigged character models

A subject that's come up a couple of times is "how do I get rigged character models into Ambient?"
I think there's piecemeal knowledge of this floating around the team, but we should document it properly.
@droqen might be the current expert on this 😅

So https://ambient.run/docs/reference/animations does already cover a lot of it. What might be nice to add though is a step-by-step guide on how to rig a character using Mixamo specifically.


[hotfix][docs] Fix incorrect example in cep doc

What is the purpose of the change
If I understand the Skip Strategy correctly, the example of the comparison between SKIP_TO_FIRST and NO_SKIP is incorrect in CEP doc. This PR try to fix it with minimal modification.
Brief change log

Fix incorrect example in cep doc

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts(all no):

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? no

cc @dawidwys

@dawidwys Thanks for the review!
I've added a new commit fix the problems and it now passes the Travis-ci.


Brotli support for js served

Is it possible to enable BROTLI support for
//imasdk.googleapis.com/js/sdkloader/ima3.js
Or is it possible for me to proxy pass it from my URL?
Example serving it as
www.mydomain.com/js/sdkloader/ima3.js  using an nginx proxy pass so I can compress it on my side?
Thanks. Is something going to break serving it on my domain?

Tested a proxy pass, but I'm getting
IMA SDK is either not loaded from a google domain or is not a supported version

Hi @andreapernici ,
The IMA is built to be loaded from the Google url and error out if loaded from other urls. This is for security reasons. Unfortunately, this means you will not be allowed to host the JS from a different url.
Thank you,
Jackson
IMA SDK Team

Thanks @Kiro705
What about adding Brotli support on your side? If possible also a pre-compressed version in order to save more kb.

Hi @andreapernici ,
The IMA SDK is built to throw the error you see if it is served from a non Google location. We do this fo security reasons. The VideoJS-IMA is open sourced, but maintained mainly by Google (I work at Google), so it will not be possible to implement Brotli support or a non-compressed version of the SDK.

Why is not possible to enable Brotli on your side? Brotli is a Google thing and it is pushing it everywhere. Why not on their properties?

Could you clarify what a Brotli supported SDK would mean in this case?
This would be a Brotli compressed version of ima3.js you could request, or the ability to Brotli compress the SDK on your end?

A brotli compressed versione of the ima3.js should be enough.

Hello @andreapernici ,
Because the compressed version would not be specific to just the videoJS-IMA plugin, I would recommend reaching out via IMA SDK forum with your request. That would be the best way to channel your request to the appropriate team.


Question: Tests are failing without linkFramework("CoreFoundation")

Hey! I'm new to Zig and system programming and macOS development and just wanted to clarify for myself one thing. Maybe you can help me with that.
What do you think could be a reason for some tests failing for me without providing tests.linkFramework("CoreFoundation") in the build.zig? In particular, there is no className property on NSObject class for me without the CoreFoundation linked.
Another symptom of potentially the same problem is the fact that even if I link CoreFoundation explicitly, I still have one test failing: class.zig / copyPropertyList. I definitely have less than 20 props in the class without any framework linked.

Thanks!


prepare release log for Messaging and InstanceID

Looks like the failure is irrelevant.

@chliangGoogle Sorry, It looks like it conflicts with the description I added.

no worries! it's an easy merge.


[Feature/extensions] Warn future developers not to pass headers to extensions

Description
Warn future developers not to pass headers to extensions
Issues Resolved

Related https://github.com/opensearch-project/OpenSearch/issues/4429

Check List

[ ] ~New functionality includes testing.~

[ ] ~All tests pass~

[ ] ~New functionality has been documented.~

[ ] ~New functionality has javadoc added~

[X] Commits are signed per the DCO using --signoff
[ ] ~Commit changes are listed out in CHANGELOG.md file (See: Changelog)~ Note; I did not include any change log changes because I don't see a change log in this branch

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #4430 (039ad26) into feature/extensions (14b899b) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@                   Coverage Diff                    @@
##             feature/extensions    #4430      +/-   ##
========================================================
- Coverage                 70.61%   70.59%   -0.03%
+ Complexity                57436    57416      -20
========================================================
  Files                      4641     4641
  Lines                    276249   276249
  Branches                  40384    40384
========================================================
- Hits                     195083   195016      -67
- Misses                    64847    64930      +83
+ Partials                  16319    16303      -16

Impacted Files
Coverage Δ

...rch/extensions/rest/RestSendToExtensionAction.java
31.25% <ø> (ø)

...g/opensearch/index/analysis/CharFilterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/opensearch/client/indices/DataStream.java
0.00% <0.00%> (-76.09%)
:arrow_down:

.../opensearch/client/indices/CloseIndexResponse.java
17.50% <0.00%> (-73.75%)
:arrow_down:

.../java/org/opensearch/node/NodeClosedException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...ava/org/opensearch/action/NoSuchNodeException.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...cluster/coordination/PendingClusterStateStats.java
20.00% <0.00%> (-48.00%)
:arrow_down:

...opensearch/cluster/NotClusterManagerException.java
60.00% <0.00%> (-40.00%)
:arrow_down:

...java/org/opensearch/threadpool/ThreadPoolInfo.java
56.25% <0.00%> (-37.50%)
:arrow_down:

.../aggregations/support/values/ScriptLongValues.java
34.88% <0.00%> (-27.91%)
:arrow_down:

... and 466 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@opensearch-project/security What do you folks think, is this a worthwhile stopgap measure?


payment_info should return PaymentInfo instead of PaymentStatus

payment_info should return PaymentInfo instead of PaymentStatus just like in ldk-node

This is completed and available in v0.1.0


[FEATURE_REQUEST] Proxmox usage

Is your feature request related to a problem? If so, please describe.
No response
Describe the solution you'd like
System usage like Cpu, storage and so on for whole node in proxmox via the api.
Priority
Low (Nice-to-have)
Is this something you would be keen to implement
None

Nice idea.
One thing I could recommend here would be to install glances on the proxmox host and then let use the dashy glances widget.

yeah i know that this option exists but i like it more to use the build in options

Hey @MobilGame06
Just to clarify, do you mean a widget that shows Proxmox resource usage?
Would this be something that you're interested in working on?
I don't currently have a Proxmox instance, but I can add it to the todo list for a later version.

sadly i don't have the experience and time for that but it would be nice to be added sometime

I'm going to close as out of scope for now. Because this functionality is possible via other resource usage widgets, supporting both Glances, NetData and system (or container) info.
But I'll reopen if many others are interested, or if someone would like to implement this.


Fix: adsc is blocked by sync chan

Signed-off-by: huabing zhao<EMAIL_ADDRESS>Please provide a description for what this PR is for.
Fix the issue in adsc: handleRecv is blocked by sync chan.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@zhaohuabing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
9937a701250c24e454dcf37946955c13ed799014
link
/test release-notes_istio

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

@googlebot I fixed it.

/retest

/test release-notes_istio

@zhaohuabing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
9937a701250c24e454dcf37946955c13ed799014
link
/test integ-pilot-multicluster-tests_istio

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

/retest

@hzxuzhonghu thanks for the reviewing.
integ-pilot-multicluster-test_istio failed.  I'm sorry I can't figure out the reason. I'm not familiar with the integration tests.  Is the failure relevant to this pr?

kubectl apply --kubeconfig=/tmp/tmp.FS0ZOQRmcW/cluster2 -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/namespace.yaml
error: unable to recognize "https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/namespace.yaml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused

I donot think it is related, adsc is actually not used by multicluster test

/retest

/test integ-pilot-multicluster-tests_istio


[Accelerate] [vImage] Fix arrayFromBuffer in tests.

A buffer's data may contain padding (containing undefined data) when the rowBytes isn't equal to the number of channels * width * size of the element. I've updated arrayFromBuffer to return an array that excludes any rowByte padding in that case.
cc: @stephentyrone

@swift-ci please smoke test and merge


Migration document flow has to be reorganized with API-M 3.2.0/4.0.0 to API-M 4.1.0 migration documents

Description:
$Subject
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Close the issue as per above doc Pr


ARAX -- Infores:diseases is not in the infores list

Infores:diseases is not in the infores list. I think this represents the biothings-diseases endpoint? (In infores, we called that infores:biothings-diseases).
Feedback welcome: https://docs.google.com/spreadsheets/d/1Ma4U3aY16mJushsW74vf9mWVacFvf7FiTEdlVqaUi5g/edit#gid=1644860829

Hi @vgardner-renci , we are having trouble finding where this a problem. Do you have a query that reproduces this issue that we can examine?

Hi, we found the source of the issue. We do find an entry called "diseases" in the "External" tab of the workbook. Cell F42.
this is what we are trying to reference. Is that not approved?

Does the entry in External need to be moved to TranslatorResources?

@sierra-moxon request for comment

@edeutsch - you are right, it is there.  Closing as fixed.


Use resourceVersion when setting Admitted=False

What type of PR is this?
/kind bug
What this PR does / why we need it:
Use resourceVersion in the SSA patch when setting Admitted=False. This guarantees that we don't accidentally override an admission that happens in a different routine.
The price to pay is potentially slower scheduling when workloads don't fit because of conflicts, but this should only happen just when a LocalQueue or ClusterQueue is created after a Workload.
Which issue(s) this PR fixes:

Fixes #678
Special notes for your reviewer:

passed 1/10

Passed 2/10
/test pull-kueue-test-integration-main

Passed 4/10
/test pull-kueue-test-integration-main

Passed 5/10
/test pull-kueue-test-integration-main

/hold cancel
Discussed with @tenzen-y offline and we are confident about the fix with 6 passes.


fix: correct the problem when fcn_mask_head takes in invalid bboxes with negative coordinates

#41 Main edit was at the original line 359 - 362

@eric-kwok-nt Thanks for your interests and contributions to QueryInst! We will check this commit asap!


Rename anatomical outputs to conform to BIDS Derivatives RC1

This is my interpretation of RC1. If it's incorrect, we may want to clarify the text.
@oesteban @satra @edickie Can you verify the transforms (bottom) and space- usage?
@ahoopes @edickie Can you verify the probseg/dseg/surfaces?
Filenames
Using examples from ds114/sub-07/anat:

Old
New

sub-07_T1w_preproc.nii.gz
sub-07_desc-preproc_T1w.nii.gz

sub-07_T1w_brainmask.nii.gz
sub-07_desc-brain_mask.nii.gz

sub-07_T1w_class-{CSF|GM|WM}_probtissue.nii.gz
sub-07_label-{CSF|GM|WM}_probseg.nii.gz

sub-07_T1w_dtissue.nii.gz
sub-07_dseg.nii.gz

sub-07_T1w_[surftype].{L|R}.surf.gii
sub-07_hemi-{L|R}_[surftype].surf.gii

sub-07_T1w_label-aparcaseg_roi.nii.gz
sub-07_desc-aparcaseg_dseg.nii.gz

sub-07_T1w_label-aseg_roi.nii.gz
sub-07_desc-aseg_dseg.nii.gz

sub-07_T1w_space-MNI152NLin2009cAsym_preproc.nii.gz
sub-07_space-MNI152NLin2009cAsym_desc-preproc_T1w.nii.gz

...
...

sub-07_T1w_space-MNI152NLin2009cAsym_target-T1w_warp.h5
sub-07_from-MNI152NLin2009cAsym_to-T1w_mode-image_xfm.h5

sub-07_T1w_target-fsnative_affine.txt
sub-07_from-T1w_to-fsnative_mode-image_xfm.txt

sub-07_T1w_target-MNI152NLin2009cAsym_warp.h5
sub-07_from-T1w_to-MNI152NLin2009cAsym_mode-image_xfm.h5

Additionally, we have multiple T1w images, so we have the following per-session files:

Old
New

sub-07_ses-<session>_T1w_space-orig_target-T1w_affine.txt
sub-07_ses-<session>_from-orig_to-T1w_mode-image_xfm.txt

Metadata

T1w file must have Space and SkullStripped metadata
Brainmasks must have RawSources, Space and Type ("Brain") metadata
dseg file should be checked to ensure tissue indices match section 7.4.3
We should add a dseg_labels.tsv that matches aparcaseg and aseg. If it clashes with 7.4.3, we'll probably need to add a desc-aseg tag (and make a copy for aparcaseg).
Transform files will need extensive metadata

I'm sorry, what is xfm? Looks like FLIRT parameter, but doesn't make sense.

Transform.

Sure, but what kind of? I meant it was obviously: affine is linear transform, warp is non-linear transform. But xfm is not self-descriptive and it misleads to which transform we deal with. Only the file format suggests the type of transform now.

This is what is currently specified by the BIDS draft specification. See https://docs.google.com/document/d/17ebopupQxuRwp7U7TFvS6BH03ALJOgGHufxK8ToAvyI/edit#heading=h.rxc844jqesod
It does not appear to have made it into bids-standard/bids-specification#109, but it is currently what we have to work with.

Thank you, I have missed this update of BIDS.

@ahoopes https://github.com/templateflow/tpl-fsaverage/blob/master/tpl-fsaverage_dseg.tsv - thanks!


访问branches报500错误

An error has occurred : no such column: true

I've got the same issue on gogs version <IP_ADDRESS>6 installed by sources.

Same here

Same problem with version: Version: <IP_ADDRESS>6.
Database: sqlite
OS: docker image: gogs/gogs
How reproduce: create a repo, and click in "branches" link;
Output log:

2018/03/15 12:45:44 [ERROR] [...outes/repo/branch.go:38 loadBranches()] GetProtectBranchesByRepoID: no such column: true
2018/03/15 12:45:44 [TRACE] Template: status/500
[Macaron] 2018-03-15 12:45:44: Completed GET /gogs/teste/branches 500 Internal Server Error in 16.133294ms

I do have the same error running a sqlite db:
An error has occurred : no such column: true
Application Version: <IP_ADDRESS>6
Adding a branch to the repository using command line does not make any difference. The repository itself  shows the correct number of branches.

It seems to be solved in <IP_ADDRESS>9.


Nginx 1.7.9  not cleaning up HLS live files

When compiling nginx-rtmp with version 1.7.9 of Nginx, in case of live HLS, the HLS directory keeps being populated with .ts files until the disk is full.
It seems that cache manager is no longer cleaning up obsolete .ts files.
I was able to fix it by reverting back to 1.7.8, and able to reproduce the issue by again updating to 1.7.9

Did you run debugging? Sounds like it could be a owner / mod issue.

Actually the issue seems to have mysteriously disappeared (however it was/is reproducible) with the current 1.9.0 nginx, so to be honest I didn't bother to do anymore investigation.


Change xliff-tasks dependency in Version.Details.xml when consuming Arcade 9

We merged the xliff-tasks repo into arcade which requires us to update the Version.Details.xml entry in all repositories. I see that tye doesn't yet use Arcade Latest (9.0) but when it does, this change should be mimicked in the dependency update PR:
https://github.com/dotnet/razor/pull/9493/commits/fcd1831fc9e41281965fa640f088b096c38454e6

Looks like this repo doesn't have .xlf files and disables the XliffTask so could probably just remove the dependency:
https://github.com/dotnet/tye/blob/75465614e67b5f1e500d1f8b1cb70af22c0c683e/eng/Versions.props#L7C1-L8


Rebase on k8s 1.8 dependencies

One major motivator for this is that we will be able to use explicit versions of these dependenceies that are human-readable and consistent (kubernetes-1.8) instead of a random collection of shas.

What's the plan for upgrading to kubernetes-1.9?
Looks like it's going to be released today:

Wed Dec 13: v1.9.0
Thu Dec 14: v1.10.0-alpha.1

https://github.com/kubernetes/features/blob/master/release-1.9/release-1.9.md

I'd rather go to 1.9 if it's out.

If someone is willing to do the work I would be fine if they went directy
to 1.9.
On Fri, Dec 15, 2017 at 10:35 PM Morgan Bauer<EMAIL_ADDRESS>wrote:

I'd rather go to 1.9 if it's out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/issues/1610#issuecomment-352157697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmJ-_NkNrPhxHM2XRLvnXKuSU-7QTks5tAzqAgaJpZM4Q226l
.

1.9 is not out yet, but should be released sometime soon.
We can wait until it's out, and check if the release branches were correctly cut in apimachinery, apiserver and other repos we depend on.

1.9 was released yesterday and has versions of the apimachinery, client,
etc tagged with kubernetes-1.9.0, example:
https://github.com/kubernetes/apimachinery/tree/kubernetes-1.9.0
On Sat, Dec 16, 2017 at 3:50 PM, Nail Islamov<EMAIL_ADDRESS>wrote:

1.9 is not out yet, but should be released sometime soon.
We can wait until it's out, and check if the release branches were
correctly cut in apimachinery, apiserver and other repos we depend on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/issues/1610#issuecomment-352210906,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmHBO9sD5aNQwEigi1d9kjT-tnd24ks5tBC0cgaJpZM4Q226l
.


For the docs, a CachedValueNotFound error probably means your cache isn't working

I had this error in dev using dummy cache but once I switched to using a database cache it worked fine.

Yes, there are still a lot of improvements to do for the documentation, especially for the cache part. Thanks for reporting this, I'll think of a way to make the dummy cache behave normally and not raising this error.

No problem.  Do you want me to post any more comments here or send you an email?

Please feel free to post your comments here :)

Downing tools for Christmas but this library looks like just what I need so will come back to it later.  Thanks for your help.

No worry, I'd be glad to implement missing features and commit bug fixes if you need it. Also, it's totally okay to open new issues and submit Pull Requests. Merry christmas !

Since there is now a way to disable preference caching via settings, the documentation should probably mention that using dummycache is possible if you also set DYNAMIC_PREFERENCES['ENABLE_CACHE'] = False.


Allow anonymous login

There is a new button for guest login (firebase's Anonymous login).
Fairly straightforward except the button image is an Icon, rather than an asset. Icons will honour the theme sizing but I've had to hardcode a size to match the assets. Incidentally, I'm not sure that the 2x and 3x assets are handled correctly unless there is some magic going on within the theme, if so, then the hardcoding will probably be broken.
This PR also includes the dependency uplift in #23 (which worked fine on Android, yet to test on iOS but there's an initial build error which could be anything and nothing as per usual with iOS :-/ )

Got this working with an iOS build. If you have trouble, then note the comments in this thread for the Facebook flutter plugin.


Clarify TTL behaviour when a TTL is set on topic & subscription

Hi team,
I'd like to suggest adding a note about the TTL, when it is set on the topic & subscription.
In particular, if the topic specifies a smaller TTL than the subscription, the topic TTL is applied.
The page already mentions entity level expiration which suffices for most scenarios. I believe the particular topic+subscription TTL case might be worth its own note, as we have been receiving a few customer queries around it.
The only reference I was able to find is in the docs of an older SDK:  Subscription Description :
"If the topic specifies a smaller TTL than the subscription, the topic TTL is applied."
Since this is not SDK specific, but rather a behaviour of the service, this page might be a good place to mention it.

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

ID: 66f10c27-dd5a-63c4-2933-792979908896
Version Independent ID: 24fb6e36-13ea-ece9-7239-41d826dacb4a
Content: Azure Service Bus - message expiration - Azure Service Bus
Content Source: articles/service-bus-messaging/message-expiration.md
Service: service-bus-messaging
GitHub Login: @spelluru
Microsoft Alias: spelluru

Hi @tiantun - Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

@tiantun - Thank you. Added it as a note in the article.
#please-close


use zyte_api.aio.errors.RequestError instead of IgnoreRequest

Resolves https://github.com/scrapy-plugins/scrapy-zyte-api/issues/25

+1 on using the original zyte_api.aio.errors.RequestError instead of scrapy.exceptions.IgnoreRequest as it provides a lot more information regarding the error.
This means developers could have accompanying debugging information should they need:
print(type(error))
# <class 'zyte_api.aio.errors.RequestError'>

print(error.response_content)
# b'{"type":"/request/invalid","title":"Bad Request","status":400,"detail":"malformed URL"}'

print(error.request_info)
# RequestInfo(url=URL('https://api.zyte.com/v1/extract'), method='POST', headers=<CIMultiDictProxy('Host': 'api.zyte.com', 'User-Agent': 'python-zyte-api/0.1.3 aiohttp/3.8.1', 'Accept': '*/*', 'Accept-Encoding': 'gzip, deflate', 'Authorization': 'Basic YWNkMDBjgTVhNjk5NDdhM2JsNWViM2QyYmY0ODg4OTM7', 'Content-Length': '35', 'Content-Type': 'application/json')>, real_url=URL('https://api.zyte.com/v1/extract'))

print(error.status)
# 400

print(error.headers)
# <CIMultiDictProxy('Date': 'Tue, 16 Aug 2022 06:29:26 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '98', 'Connection': 'keep-alive', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>

print(error.message)
# 'Bad Request'

print(error.parsed)
# ParsedError(response_body=b'{"type":"/request/invalid","title":"Bad Request","status":400,"detail":"malformed URL"}', data={'type': '/request/invalid', 'title': 'Bad Request', 'status': 400, 'detail': 'malformed URL'}, parse_error=None)

Hey! Could you please paste an example from Scrapy logs, before & after? If I recall correctly, the original motivation for IgnoreRequest was to make the logs nice.

@kmike here's the before the change:
2022-08-17 16:11:27 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 1st time calling it.
2022-08-17 16:11:34 [zyte_api.aio.retry] DEBUG: Finished call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request' after 7.050(s), this was the 1st time calling it.
2022-08-17 16:11:34 [zyte_api.aio.retry] DEBUG: Retrying zyte_api.aio.client.AsyncClient.request_raw.<locals>.request in 4.536589228554908 seconds as it raised RequestError: RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 17 Aug 2022 08:11:34 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'.
2022-08-17 16:11:39 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 2nd time calling it.
2022-08-17 16:12:27 [scrapy.extensions.logstats] INFO: Crawled 0 pages (at 0 pages/min), scraped 0 items (at 0 items/min)
2022-08-17 16:13:27 [scrapy.extensions.logstats] INFO: Crawled 0 pages (at 0 pages/min), scraped 0 items (at 0 items/min)
2022-08-17 16:13:34 [scrapy_zyte_api.handler] ERROR: Got Zyte API error (status=521, type='/download/internal-error') while processing URL (https://somesitethatdoesntexist.com): Server encountered a problem while downloading. Check request and contact support.
2022-08-17 16:13:34 [scrapy.core.engine] INFO: Closing spider (finished)

After the change:
2022-08-17 16:08:44 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 1st time calling it.
2022-08-17 16:08:50 [zyte_api.aio.retry] DEBUG: Finished call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request' after 6.124(s), this was the 1st time calling it.
2022-08-17 16:08:50 [zyte_api.aio.retry] DEBUG: Retrying zyte_api.aio.client.AsyncClient.request_raw.<locals>.request in 3.980291660344501 seconds as it raised RequestError: RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 17 Aug 2022 08:08:50 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'.
2022-08-17 16:08:54 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 2nd time calling it.
2022-08-17 16:09:08 [zyte_api.aio.retry] DEBUG: Finished call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request' after 24.523(s), this was the 2nd time calling it.
2022-08-17 16:09:08 [zyte_api.aio.retry] DEBUG: Retrying zyte_api.aio.client.AsyncClient.request_raw.<locals>.request in 5.5720285729643 seconds as it raised RequestError: RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 17 Aug 2022 08:09:08 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'.
2022-08-17 16:09:14 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 3rd time calling it.
2022-08-17 16:09:43 [zyte_api.aio.retry] DEBUG: Finished call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request' after 59.357(s), this was the 3rd time calling it.
2022-08-17 16:09:43 [zyte_api.aio.retry] DEBUG: Retrying zyte_api.aio.client.AsyncClient.request_raw.<locals>.request in 8.801528262547553 seconds as it raised RequestError: RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 17 Aug 2022 08:09:43 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'.
2022-08-17 16:09:43 [scrapy.extensions.logstats] INFO: Crawled 0 pages (at 0 pages/min), scraped 0 items (at 0 items/min)
2022-08-17 16:09:52 [zyte_api.aio.retry] DEBUG: Starting call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request', this is the 4th time calling it.
2022-08-17 16:09:55 [zyte_api.aio.retry] DEBUG: Finished call to 'zyte_api.aio.client.AsyncClient.request_raw.<locals>.request' after 71.802(s), this was the 4th time calling it.
2022-08-17 16:09:55 [scrapy_zyte_api.handler] ERROR: Got Zyte API error (status=520, type='/download/temporary-error') while processing URL (https://somesitethatdoesntexist.com): There is a downloading problem which might be temporary. Retry in N seconds from 'Retry-After' header.
2022-08-17 16:09:55 [scrapy.core.scraper] ERROR: Error downloading <GET https://somesitethatdoesntexist.com>
Traceback (most recent call last):
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/twisted/internet/defer.py", line 1656, in _inlineCallbacks
    result = current_context.run(
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/twisted/python/failure.py", line 514, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/scrapy/core/downloader/middleware.py", line 49, in process_request
    return (yield download_func(request=request, spider=spider))
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/twisted/internet/defer.py", line 1030, in adapt
    extracted = result.result()
  File "/home/kevinoxy/dev/z/scrapy-zyte-api/scrapy_zyte_api/handler.py", line 154, in _download_request
    raise er
  File "/home/kevinoxy/dev/z/scrapy-zyte-api/scrapy_zyte_api/handler.py", line 143, in _download_request
    api_response = await self._client.request_raw(
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/zyte_api/aio/client.py", line 116, in request_raw
    result = await request()
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/tenacity/_asyncio.py", line 86, in async_wrapped
    return await fn(*args, **kwargs)
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/tenacity/_asyncio.py", line 48, in __call__
    do = self.iter(retry_state=retry_state)
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/tenacity/__init__.py", line 360, in iter
    raise retry_exc.reraise()
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/tenacity/__init__.py", line 193, in reraise
    raise self.last_attempt.result()
  File "/home/kevinoxy/.pyenv/versions/3.8.6/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/home/kevinoxy/.pyenv/versions/3.8.6/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/tenacity/_asyncio.py", line 51, in __call__
    result = await fn(*args, **kwargs)
  File "/home/kevinoxy/.pyenv/versions/3.8.6/envs/3.8.6-scrapy-zyte-api-test/lib/python3.8/site-packages/zyte_api/aio/client.py", line 91, in request
    raise RequestError(
zyte_api.aio.errors.RequestError: RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 17 Aug 2022 08:09:55 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'
2022-08-17 16:09:56 [scrapy.core.engine] INFO: Closing spider (finished)

The logs ain't that pretty with the traceback. Nonetheless, it's more usable since the developer can easily discern the exceptions with type RequestError than IgnoreRequest which is a bit generic and doesn't contain debugging information.

Thanks @BurnzZ! I think you're right, and a more verbose output is ok.


LRT Values and other concerns

Hi Zev Kronenberg,
This a great tool, I got to know about this from Brad Chapman's post.
I was testing WHAM and had some issues:

For the result I did not have LRT score for cases and controls mode, all LRT score's where 0. But it did pick up true positive event.
NA: The number of reads that do support any type of structural variant .
Here shouldn't the number of reads be for the specific event. I know you decide whether the event is Deletion, Inversion etc when you classify but this would really help in filtering ).
It would also help if you would put a little more explanation of the use of gene target bed file.
Also when its a translocation which was the true positive in my case. I saw it as being annotated as Deletion. Can you elaborate more on your classification strategy in the help section.

Thanks,
Ronak

Thank you for using Wham and posting an issue.

Can you post a few lines of the VCF where you see this problem?
I will update the wording on the wiki.  It should state: the number of reads supporting the SV reported in the alt field.  For example if WHAM identifies the breakpoints of a deletion, it will be the number of reads supporting the current positions breakpoint.
I will do this in the next couple of days.
The classifier is the newest portion of code.  Brad also pointed out a similar issue.  What I have done is provided a new training dataset:  master/utils/WHAM_training_phase3_10bp_training.txt that may solve some of the classification issues.

I would recommend checking out master rather than v1.7.0.  I'm in the process of tagging v1.8.0, but all the improvements are currently on master.

Here is the output of the true positive events:
22	29688285	.	N	CTTTACGACATAATAAAAATAATGTAACTGACCAAATTGAGATGGAA	.	.	LRT=0;WAF=1e-06,1,0.500001;GC=1,1;AT=0,0,0,0,0.0597015,0,0.0358209,0.0537313,0.0179104,0.0179104,0.940299,0.0119403,0,0,0,0,0;SI=1.80377;PU=33;SU=18;CU=184;RD=335;NC=30;MQ=60;MQF=0;SP=sr;BE=8,145055127,18;DI=f;END=.;SVLEN=.;WC=DEL;WP=0.6,0.088,0.1376,0.1744	GT:GL:NR:NA:NS:RD	1/1:-255,-255,-0.000218:0:218:43:218	0/0:-0.000117,-255,-255:117:0:0:117
22	29688292	.	N	CTAAGCTACATGAAGCCCCACTTTATATTCTAACCTGAGCAC	.	.	LRT=0;WAF=1e-06,1,0.500001;GC=1,1;AT=0,0,0,0,0.0574713,0,0.0344828,0.0517241,0.0172414,0.0172414,0.942529,0.0114943,0,0,0,0,0;SI=1.91911;PU=10;SU=2;CU=185;RD=348;NC=6;MQ=60;MQF=0;SP=sr;BE=21,39775029,2;DI=b;END=.;SVLEN=.;WC=DEL;WP=0.612,0.088,0.1296,0.1704	GT:GL:NR:NA:NS:RD	1/1:-255,-255,-0.00023:0:230:43:230	0/0:-0.000118,-255,-255:118:0:0:118
As you see for both the LRT is given as 0.
For the VCF file all entries have LRT=0.
-bash-4.1$ cat testWham.classify.vcf | grep "LRT=0"| wc -l
666
-bash-4.1$ cat testWham.classify.vcf | grep -v "^#" | wc -l
666
Sure I will probably wait for you to release the v1.8.0 and the try it again.
Thanks for your response.


Weird behaviour with dynamically added chart series

Run into some strange behavior with v0.9.13-beta on dotnet 6.0
I used a completely new project created from the Blazor Server App Template in Visual Studio 2022 to replicate this.
The project can be found here: https://github.com/hofmannmarkus0/BlazorApexcharts-Issue-Showcase
The links further down in this issue, all just link to separate pages I created in this project.
I am trying to dynamically add new Point Series elements to a chart using an @foreach loop in my component.
As long as this happens within OnInitialized everything works as expected and the point series are all rendered properly.
But as soon as I try to add more series later on (e.g. when a button is pressed), rendering of the new series is somewhat "delayed". The first button click has no visual effect and the second button click finally causes the series added by the first click to be rendered (same with consecutive button clicks). This already includes calling ApexChart.UpdateSeriesAsync on the chart reference
Example: component and code behind
Calling ApexChart.UpdateSeriesAsync twice in a row somehow seems to fix this issue, calling StateHasChanged or ApexChart.RenderAsync did not result in any improvement with this issue.
Example: component and code behind
Another issue I noticed while working with this was that the chart completely fails to render with javascript typeerrors when I have no chart series at all when initiallly rendering the html (in case I might not have the data to display a series immediately after loading the page) which can be replicated in this example: component and code behind
It also cant recover from this broken state after adding entries to the source list used to generate the point series as this just results in more javascript errors.
I am not entirely sure if I am just missing something or not, so any help/advice would be appreciated.
(For the last issue, I should be able to work around it in some way, but this does not feel like intended/wanted behavior)

Hello,
Thnak you for a detailed report and the repo. I will look into this asap.

Hi,
I made a PR with some changes.. please have a look and let me know if anything is unclear.
I will have one more look on the second issue, I might be something we can prevent in the integration.
However it is not simple because with no series we are missing some vital information for the chart.

Hello,
thank you for the suggestions.
They definitely work for me in the test project and helped me identify some misunderstandings on my end.
I had tried to add a delay earlier, but so far when I had to use delays, it never mattered wether it blocked the thread completely or just delayed execution of the method and therefore I had tried it using Task.Delay(10).Wait() which obviously also blocks blazor from syncing the changes, and coming from working with wpf and similar desktop ui frameworks, the concept of needing to wait for the changes to be synced with the components was new to me.
Using await Task.Delay(10) as you suggested worked here.
For the second issue, I just found the NoData option. Setting that and adding an empty chart series instead of having no series at all, I can render an empty chart with a hint about having no data, which I prefer over hiding the chart completely in my real use-case, though disabling the chart with the @if (Series != null && Series.Any() also worked to prevent the issue.
Thanks again for the suggestions as they really helped me figuring out what I was doing the wrong way.

just as an addition: for the second "issue" it would be nice if this wrapper could show a warning/error message that makes it more obvious whats wrong as the javascript errors where not really helping with finding the cause.

From: Joakim Dangården @.>
Sent: Tuesday, September 6, 2022 9:17:21 PM
To: apexcharts/Blazor-ApexCharts @.>
Cc: Hofmann, Markus @.>; Author @.>
Subject: Re: [apexcharts/Blazor-ApexCharts] Weird behaviour with dynamically added chart series (Issue #141)
Hi,
I made a PR with some changes.. please have a look and let me know if anything is unclear.
I will have one more look on the second issue, I might be something we can prevent in the integration.
However it is not simple because with no series we are missing some vital information for the chart.
—
Reply to this email directly, view it on GitHubhttps://github.com/apexcharts/Blazor-ApexCharts/issues/141#issuecomment-1238555472, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYVB7BAMLA6ROBQ7PMK5JE3V46KEDANCNFSM6AAAAAAQFEG3KI.
You are receiving this because you authored the thread.Message ID: @.***>

#158

just as an addition: for the second "issue" it would be nice if this wrapper could show a warning/error message that makes it more obvious whats wrong as the javascript errors where not really helping with finding the cause.


how to access it through browser

[Enter feedback here]

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

ID: 597ba957-9501-5919-73a0-6d47b1ca2c6d
Version Independent ID: 6345fa19-b3f2-ffd6-f526-908f845b51f6
Content: Use your TLS certificates for ingress - Azure Kubernetes Service
Content Source: articles/aks/ingress-own-tls.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Hello @rajendar38,
Your question or feedback doesn't have sufficient information. Please add a brief description of your question or feedback.


Handle nested maps in terraform12Adjustments

This tries to handle the case where a field has the same name under different subschemas in the same resource, one of them being a map. Currently, it replaces all occurrences to the map version, but we can properly detect where we are in the hierarchy.

@therve Thanks! I'll test this PR

@therve Can you fix lint errors?


Performance Centre / Markers keyboard shortcut

Alt-Shift-q is missing

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

ID: e8619415-835b-d97c-f7c0-aa01e0d0bc63
Version Independent ID: 330f0119-b76a-8d9e-88da-f5ed513c9573
Content: Move around Customer Engagement apps using keyboard shortcuts
Content Source: ce/basics/keyboard-shortcuts.md
Service: dynamics-365-cross-app
GitHub Login: @kathleenmcgrath
Microsoft Alias: kmcgrath

This needs to go to perf team for review-<EMAIL_ADDRESS><EMAIL_ADDRESS>Please reassign
Thanks,
Hemant
From: kathleenmcgrath<EMAIL_ADDRESS>Sent: Wednesday, June 6, 2018 8:38 AM
To: MicrosoftDocs/dynamics-365-customer-engagement<EMAIL_ADDRESS>Cc: Hemant Gaur<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Performance Centre / Markers keyboard shortcut (#52)
Assigned #52https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F52&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578542706&sdata=X%2B6m5LZ7aeJmZTDI%2FGx4HPPMffM42cOeDVtcdtHYNNM%3D&reserved=0 to @HemantGaurhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FHemantGaur&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578542706&sdata=4QPSNZAORndX%2Bpt%2Fwv%2FugWGLzKIdjf2q31FOwPRh5MQ%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F52%23event-1666467820&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578552714&sdata=UOlWPIxw%2FAJ%2FpwunBfpLrsoeydpw9TZYcOChZ6FwsTA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAbpcZCJMh9nbm2rIVsGQLMe0boOiB9Exks5t5_c_gaJpZM4UXpmg&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578552714&sdata=MIIx24QC45P9a3SfCAsyFZNE%2Bd%2BZEd78bgoksdvh6Z8%3D&reserved=0.

ALT+SHIFT+Q should not be supported on UCI, right?  Is this just referring to web client, and have we previously declared support for using the widget in web client?
From: Hemant Gaur
Sent: Thursday, June 7, 2018 12:14 PM
To: MicrosoftDocs/dynamics-365-customer-engagement<EMAIL_ADDRESS>MicrosoftDocs/dynamics-365-customer-engagement<EMAIL_ADDRESS>Jesse Parsons<EMAIL_ADDRESS>Richard Dickinson<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/dynamics-365-customer-engagement] Performance Centre / Markers keyboard shortcut (#52)
This needs to go to perf team for review-<EMAIL_ADDRESS><EMAIL_ADDRESS>Please reassign
Thanks,
Hemant
From: kathleenmcgrath <notifications<EMAIL_ADDRESS>Sent: Wednesday, June 6, 2018 8:38 AM
To: MicrosoftDocs/dynamics-365-customer-engagement <dynamics-365-customer-engagement<EMAIL_ADDRESS>Cc: Hemant Gaur <hemantg<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Performance Centre / Markers keyboard shortcut (#52)
Assigned #52https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F52&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578542706&sdata=X%2B6m5LZ7aeJmZTDI%2FGx4HPPMffM42cOeDVtcdtHYNNM%3D&reserved=0 to @HemantGaurhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FHemantGaur&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578542706&sdata=4QPSNZAORndX%2Bpt%2Fwv%2FugWGLzKIdjf2q31FOwPRh5MQ%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-customer-engagement%2Fissues%2F52%23event-1666467820&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578552714&sdata=UOlWPIxw%2FAJ%2FpwunBfpLrsoeydpw9TZYcOChZ6FwsTA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAbpcZCJMh9nbm2rIVsGQLMe0boOiB9Exks5t5_c_gaJpZM4UXpmg&data=02|01|hemantg%40microsoft.com|20c18951eb1c4d8d2bb208d5cbc36d86|72f988bf86f141af91ab2d7cd011db47|1|0|636638962578552714&sdata=MIIx24QC45P9a3SfCAsyFZNE%2Bd%2BZEd78bgoksdvh6Z8%3D&reserved=0.

ALT+SHIFT+Q brings up an internal performance widget on the new Unified Interface, but it is not a publicly supported product at this time.  We will consider adding it to our tooling roadmap in the future for self-service.
cc @HemantGaur @evchaki @vashr


centres from global registry

this branch has wis2 nodes only. Global services are still in discussion.

changed to draft until I add the Global services


S3 Bucket from README example missing

This command, listed under "Get test input files from s3" doesn't work:
aws s3 cp s3://cmarkello-vgtoil-test--files/BRCA1_BRCA2_may6.vg /home/mesosbox/debug_eval_input/BRCA1_BRCA2_may6.vg
because the bucket doesn't seem to exist:
aws s3 ls s3://cmarkello-vgtoil-test--files/BRCA1_BRCA2_may6.vg
A client error (NoSuchBucket) occurred when calling the ListObjects operation: The specified bucket does not exist

Pull request is up. Forgot to update README when cleaning up demo file s3 buckets.


Record events against TPR

Fixes #79

@sadlil , can you add events when Deployments, services, servicmonitors are added?

what about update and delete? @tamalsaha


sub_group_size is not documented

besides 2 inconsistent examples:
./docs/_tutorials/zero.md:-    "sub_group_size": 1e9
./docs/_tutorials/zero.md:+    "sub_group_size": 1e9,
./docs/_pages/config-json.md:    "sub_group_size" : 1e12,

sub_group_size is not documented.
And it's unclear in what situations to raise or lower it and by how much.
Thank you!
@samyam

Elsewhere @samyam shared:

sub_group_size controls the granularity in which parameters are updated during optimizer steps. Parameters are grouped into buckets of sub_group_size and each buckets is updated one at a time. When used with NVMe offload in ZeRO-Infinity, sub_group_size therefore controls the granularity in which model states are moved in and out of CPU memory from NVMe during the optimizer step.  This prevents running out of CPU memory for extremely large models.
Most users can leave sub_group_size to its default value of 1e9 when not using NVMe offload. The user may chose to change its value in the following cases:
Running into OOM during optimizer step : User can try reducing sub_group_size to reduce memory utilization of temporary buffers
Optimizer Step is taking a long time: User can try increasing sub_group_size to improve bandwidth utilization as a result of increased data size

I will add it for now into HF Deepspeed docs, as I don't think there is a place for tuning notes anywhere in core docs, but would love to see all those HF docs move here, as they belong to the core.


PROBLEMS TO DEPLOY FTP-SRV IN A CLOUD SERVER

Hi. We have a working implementation of ftp-srv that locally works fine. As soon as it is deployed in a cloud server using PASV MODE the FTP CLIENT gets stuck after PASV OK message is received:
01/02/2021 23:50:07  Sent> PASV
01/02/2021 23:50:07  Recv> 227 PASV OK (ftp://scanntech,stage,guayerd,com,255,231)
ftp-srv is set to use port 2121, the MIN and MAX PASV PORTS are set to 65500 and 65515. The range is ALLOWED for all the interfaces at the Server.
Tried with several FTP Clients. PASV OK message is received, and any ftp gets stucked there.
Not sure what else could be.
Thanks in advance.

Found the PASSIVE SERVER must not have neither the protocol not the port.


"Alexa, sing me a song" command not working

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
When I invoke alexa using command "Alexa, sing me a song", it starts playing song for 1-2 sec, then it stops and becomes unresponsive for ~10 sec.
What is the expected behavior?
It should complete the song that is being played, when user invokes alexa using command "Alexa, sing me a song".
What behavior are you observing?
When I invoke alexa using command "Alexa, sing me a song", it starts playing song for 1-2 sec, then it stops and becomes unresponsive for ~10 sec.
Provide the steps to reproduce the issue, if applicable:

Invoke alexa using command - "Alexa, sing me a song"
Wait for 1-2 sec till it start playing.

Tell us about your environment:
AVS SDK Version 1.18.0 Cross Compiled to run on below Hardware.
PulseAudio
Bluetooth
Spotify Adapter integrated
Alexa-communication integrated
What version of the AVS Device SDK are you using?
AVS-DEVICE-SDK-1.18
Tell us what hardware you're using:
artik305s (samsung's SOC) 1 gb ram, 4 gb emmc
Tell us about your OS (Type & version):
linux (ubuntu)

alexa(1).log
DEBUG9 Logs of the issue.

Hi @prateek-web thanks for posting.
Looking into this issue I was able to reproduce a crash on 1.18 of our SampleApp with sing me a song. We are looking further into this issue.

Hi @prateek-web
This is due to a known issue with the guiRenderer.cpp
This bug was fixed in version 1.21 of the SDK. Please update to a newer version of the SDK or update the guiRenderer.cpp file in your source code.


implement adjustable compression for raw image

Implemented paramtric compression quality only if strem from camera is raw, it can be done when the strem from camera is compressed too but  i tried to avoid double compression.

From your comments, I can now see that you are essentially reimplementing CompressedPublisher::publish instead of CvImage::toCompressedImageMsg. The implementation of CompressedPublisher::publish is much more complex than CvImage::toCompressedImageMsg.
Do you think re-implemening toCompressedImageMsg with the compression quality option would be sufficient for you?

From your comments, I can now see that you are essentially reimplementing CompressedPublisher::publish instead of CvImage::toCompressedImageMsg. The implementation of CompressedPublisher::publish is much more complex than CvImage::toCompressedImageMsg.
Do you think re-implemening toCompressedImageMsg with the compression quality option would be sufficient for you?
Yes it would be sufficient, if it's ok i will copy the function and make the necessary changes and update the pull request. But we still need to call cv_bridge::toCvShare to get a CvImage. Since the function toCompressedImageMsg works on CvImage. But i'll left the format blank so cv_bridge::toCvShare wont do any unnecessary converting.

I tryed to fix all requested changes, if necessary i can go to a new branch with only one commit(if no more issues are present) or let this as it is.

I'll also try to get a PR in original_repo with additional default parameter to the function. Or with a new signature. May be if they merge we can thane change this too.

I'll also try to get a PR in original_repo with additional default parameter to the function. Or with a new signature. May be if they merge we can thane change this too.

That would be awesome and remove the need to keep this function here.

This looks good now. Final request: Can you squash all your commits into one and rebase/force-push to the PR? There are many back and forth changes that are better suited for a single commit.

Squashed the final code into the first commit, and changed the commit to "functionality for compression qualit".

Thanks :). Yesterday i also tryed to get a PR here in the original cv_bridge repo to the humble branch, but i'm not sure if that is the correct way since there are many request that are awaiting. Anyway if they will merge i'll remove the function and pass directly the parameter to the new version. I'll add the tag closes now.


Remove settings file completely from drupal8.

So does this configuration file needs to be created in all projects?

@Chapabu any thoughts on this?

There will need to be a config file of some sort on the project, but this is fairly normal for Drupal hosting (i.e Acquia needs specific settings, Platform.sh needs specific settings, etc).
So long as it's documented, it should be fine.
I'll be backporting settings from a working project into https://github.com/continuouspipe/drupal8-lightning at some point this week.

Thanks @Chapabu. I've created the issue continuouspipe/drupal8-lightning#24 for you :)


Support TypeScript 5.6

Search Terms
TypeScript 5.6 release
Problem
TypeDoc warns about not supporting TypeScript 5.6
Suggested Solution
Add TS 5.6 to the list of supported versions.

Note: API review indicates there were no breaking changes, so while TypeDoc versions prior to 0.26.7 will warn about the version being unsupported, it in practice will work just fine.


How to write sentence with 2 $ signs?

I have to write the sentence:
... product market has been valued at over $1.7 billion in 2013 and is expected to grow over $94 billion by 2024 ...
But the expression between the 2 $ signs gets rendered as TeX (math).
If I escape the $ signs with $, it is all right, but then I get $ in the HTML and PDF instead.
How to fix this?

Thanks for telling me this issue ;)
I will fix this bug as soon as possible.

Hi, the bug should have been fixed ;)
Please delete the package and then reinstall it.
Sorry for the trouble
Please inform me if u find any other bugs ;)


[Doc] Update ranger plugin, add sidebar for cloudcanal, fix function and configuration

Why I'm doing:
What I'm doing:
add links to ranger plugi
add sidebar for cloudcanal and datax
adjust the level of BE static parameters in cn doc
rename like-predicate function folder name
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio rebase


Suport arbitrary JSON pointer references

First off, thank you for writing this tool. It has been very useful to my team.
We ran into an issue recently when importing OpenAPI specs which contain references (for example, PagerDuty's). With this change, we were able to import them as expected. The root cause seems to be that references in API specs can contain characters which require escaping as described in RFC 6901 (forward slashes are particularly common in API specs since they are used as path item key). This PR leverages json-ptr to handle this and support arbitrary references.
Signed-off-by: Matthieu Monsch<EMAIL_ADDRESS>

@Alan-Cha please have a look

@mtth Thank you for the PR, it is important that we get these things right.
I think that the specific issue you point out could also have been fixed by an additional call to unescape at the beginning of resolveRef. For example, unescape('#/paths/~1users~1%7bid%7d/description') (from your test case) yields '#/paths/~1users~1{id}/description'. As such, there is a tradeoff here between a small fix for the specific issue vs. introducing a new runtime dependency. I do like that json-ptr has itself no dependencies, though, and is relatively small with ~90kb (as long as we are not talking browser). And I guess it will resolve other (edge-) cases that our resolveRef (obviously) currently misses. So LGTM!

@mtth Thank you so much for this contribution!!! 🥳

Thank you for a quick review!

Happy to contribute - thank you for the quick review.


Move examplef out of showcase

I did rough thing: moved all examples into examples/showcase/sub folder where it's hard to find them. This PR improves #198, but reparis paths to the examples so that everyone can easily find them.
CI still checking showcase bundle only (which includes all examples as crates).
Fixes #206

bors r+


MVP 681 police force

New concept "as is" is now added to the concept section. It asks the police force with a select menu option containing all forces across the UK.
Also added a the help reveal below it - not sure if we are able to mention calling the police 101 in there?
This design pattern is from GDS https://design-system.service.gov.uk/components/select/
This is the only one they have and is used for sorting tables and data.  I have made the first option blank and disabled it using code so that the first option is blank and not accepted if the user just selects continue to ensure this works for us. Bit clunky.
Ideally would like the dropdown example from: https://alphagov.github.io/accessible-autocomplete/examples/  to be used. the one where when they click on the pattern the full list is shown but they are able to type to search too.
Also may need to confirm the final list of police forces. The list I have used is taken from the justice portal but would like it confirmed to ensure it contains an accurate up-to-date list.

This looks good @maxinedivers. Some of the Scottish ones on Justice are still displaying as the old names so Alan has given me the correct list and I've shared them with you via google sheets.

@Julieallan  I am not sure we should have any hint text here at the moment.   We could add some if the private beta research identifies a need.  Otherwise the content is fine (with the exception of the drop down contents which we have already discussed)

Agreed we can leave police force list as is on the prototype. Dev has the correct list of forces which they will use when developing any dropdown.

Also I agree we should leave out any hint text until we test with users.

@Julieallan I have made content changes, removing the hint text and aligning the reveal content with the page heading.


[Part2] Partition and Sort Enforcement, ExecutionPlan enhancement

Which issue does this PR close?

Partially Closes #3854.
Closes #3653
Closes #3400
Closes #189,
You can see the entire work in https://github.com/apache/arrow-datafusion/pull/3855
Rationale for this change

What changes are included in this PR?

Add methods required_input_ordering() to ExecutionPlan trait to specify the ordering requirements
Fix output_partitioning(), output_ordering(), required_input_distribution() in couple of trait implementations
Add method equivalence_properties() to ExecutionPlan trait to discover the equivalence properties in the Physical plan tree
Support partition aware UnionExec

Are there any user-facing changes?

@alamb @andygrove @Dandandan @isidentical @yahoNanJing
Please help to take a look

Thanks @mingmwang  -- I will review this carefully tomorrow

I am sorry -- I ran out of time today -- will try and find time tomorrow

@liukun4515 and @Ted-Jiang   perhaps you have some time to help review this as well

@alamb @yahoNanJing
Please help to take look again.

retest please

Should we make the Equivalence Properties schema aware ?

It would be great to add this schema constraint. Then we can avoid the ambiguous in
https://github.com/apache/arrow-datafusion/blob/e945c37d25cb173d03929084bcd8aac31f71580e/datafusion/core/src/physical_plan/projection.rs#L202-L209

Hi @alamb, should we merge this PR first so that @mingmwang will be able to continue the part 3 of this unnecessary shuffling optimization?

Hi @alamb, should we merge this PR first so that @mingmwang will be able to continue the part 3 of this unnecessary shuffling optimization?

Yes absolutely!

Sorry for the delay