Problem with Knockout after upgrading to Angular 7

Package versions:
devexteme version: 18.2.6
devextreme-angular version: 18.2.6
Devexpress.AspNetCore.Reporting version: 18.2.6
The angular report viewer was working fine until I upgraded angular version from 6 to 7. I deleted node_modules but with no luck. I updated rxjs to 6+.
Errors details from the console:
core.js:15723 ERROR TypeError: Unable to process binding "foreach: function(){return parts }"
Message: Unable to process binding "template: function(){return { name:templateName,data:model} }"
Message: Unable to process binding "template: function(){return {name:'dxrd-toolbar-tmplt',data:actionLists.toolbarItems} }"
Message: Unable to process binding "foreach: function(){return $data }"
Message: Unable to process binding "if: function(){return $data.templateName }"
Message: Unable to process binding "template: function(){return templateName }"
Message: Unable to process binding "dxMenu: function(){return { disabled:$data.disabled(),items:items,cssClass:'dxrdp-export-to-menu',onItemClick:clickAction} }"
Message: Unable to process binding "attr: function(){return { title:$root.getLocalization(text,$data.textId)} }"
Message: $root.getLocalization is not a function
at attr (eval at parseBindingsString (knockout-latest.js:74), :3:78)
at update (knockout-latest.js:96)
at function.a.$.l (knockout-latest.js:79)
at Function.xd (knockout-latest.js:55)
at Function.yd (knockout-latest.js:55)
at Function.ha (knockout-latest.js:54)
at Object.a.o.a.$ (knockout-latest.js:52)
at knockout-latest.js:79
at Object.C (knockout-latest.js:11)
at q (knockout-latest.js:78)

defaultErrorLogger
@
core.js:15723

<EMAIL_ADDRESS>@
core.js:15771

(anonymous)
@
core.js:18125

push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke
@
zone.js:391

push../node_modules/zone.js/dist/zone.js.Zone.run
@
zone.js:150

<EMAIL_ADDRESS>@
core.js:17257

<EMAIL_ADDRESS>@
core.js:18125

(anonymous)
@
core.js:18009

push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke
@
zone.js:391

onInvoke
@
core.js:17298

push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke
@
zone.js:390

push../node_modules/zone.js/dist/zone.js.Zone.run
@
zone.js:150

<EMAIL_ADDRESS>@
core.js:17212

next
@
core.js:18009

schedulerFn
@
core.js:13514

push../node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.__tryOrUnsub
@
Subscriber.js:194

push../node_modules/rxjs/_esm5/internal/Subscriber.js.SafeSubscriber.next
@
Subscriber.js:132

push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._next
@
Subscriber.js:76

push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber.next
@
Subscriber.js:53

push../node_modules/rxjs/_esm5/internal/Subject.js.Subject.next
@
Subject.js:47

<EMAIL_ADDRESS>@
core.js:13498

checkStable
@
core.js:17267

onHasTask
@
core.js:17311

push../node_modules/zone.js/dist/zone.js.ZoneDelegate.hasTask
@
zone.js:443

push../node_modules/zone.js/dist/zone.js.ZoneDelegate._updateTaskCount
@
zone.js:463

push../node_modules/zone.js/dist/zone.js.Zone._updateTaskCount
@
zone.js:291

push../node_modules/zone.js/dist/zone.js.Zone.runTask
@
zone.js:212

drainMicroTaskQueue
@
zone.js:601

push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask
@
zone.js:502

invokeTask
@
zone.js:1744

globalZoneAwareCallback

My package.json
"dependencies": {
"@angular/animations": "^7.2.7",
"@angular/cdk": "^7.3.3",
"@angular/common": "^7.2.7",
"@angular/compiler": "^7.2.7",
"@angular/core": "^7.2.7",
"@angular/flex-layout": "^7.0.0-beta.23",
"@angular/forms": "^7.2.7",
"@angular/http": "^7.2.7",
"@angular/material": "^7.3.3",
"@angular/platform-browser": "^7.2.7",
"@angular/platform-browser-dynamic": "^7.2.7",
"@angular/platform-server": "^7.2.7",
"@angular/router": "^7.2.7",
"@angular/upgrade": "^7.2.7",
"@ng-bootstrap/ng-bootstrap": "^4.0.4",
"@ngx-loading-bar/core": "^2.2.0",
"@ngx-loading-bar/http-client": "^2.2.0",
"@ngx-loading-bar/router": "^2.2.0",
"@types/lodash": "^4.14.109",
"acorn": "^6.1.1",
"angular-user-idle": "^2.0.0",
"bootstrap": "^4.0.0",
"chart.js": "2.7.1",
"core-js": "^2.6.5",
"crypto-js": "^3.1.9-1",
"devexpress-reporting-angular": "18.2.6",
"devextreme": "18.2.6",
"devextreme-angular": "18.2.6",
"devextreme-aspnet-data-nojquery": "^2.0.0",
"flag-icon-css": "2.9.0",
"font-awesome": "^4.7.0",
"jszip": "^3.1.5",
"lodash": "^4.17.10",
"moment": "2.20.1",
"moment-timezone": "^0.5.21",
"ng2-charts": "1.6.0",
"ngx-bootstrap": "^3.0.1",
"npm": "^5.7.1",
"popper.js": "^1.12.9",
"rxjs": "^6.4.0",
"rxjs-compat": "^6.4.0",
"simple-line-icons": "^2.4.1",
"spinkit": "^1.2.5",
"ts-helpers": "1.1.2",
"xlsx": "^0.12.13",
"zone.js": "^0.8.29"
},
"devDependencies": {
"@angular-devkit/build-angular": "^0.13.3",
"@angular/cli": "^7.3.3",
"@angular/compiler-cli": "^7.2.7",
"@angular/language-service": "^7.2.7",
"@types/jasmine": "^3.3.9",
"@types/jasminewd2": "2.0.3",
"@types/node": "^11.9.5",
"cldr-data": "^34.0.0",
"codelyzer": "^4.5.0",
"devextreme-intl": "18.2.6",
"globalize": "^1.4.0",
"jasmine-core": "^3.3.0",
"jasmine-spec-reporter": "^4.2.1",
"karma": "^4.0.0",
"karma-chrome-launcher": "^2.2.0",
"karma-cli": "^2.0.0",
"karma-coverage-istanbul-reporter": "1.4.1",
"karma-jasmine": "^2.0.1",
"karma-jasmine-html-reporter": "^1.4.0",
"protractor": "^5.4.2",
"rxjs-tslint": "^0.1.7",
"ts-node": "4.1.0",
"tslint": "^5.13.0",
"typescript": "^3.1.1"
},
"engines": {
"node": ">= 8.9.4",
"npm": ">= 5.6.0"
}

This solution worked.
https://www.devexpress.com/Support/Center/Question/Details/T717982/javascript-errors-occur-in-browser-while-using-html5-reporting-widgets-with-the-latest


Docker container can't load static files on remote host

When I run the docker image I've built locally from localhost it works as expected
When I run the same image on the remote host it can't find the static files
Expected Behavior
Be able to serve the static files
Current Behavior
Static files are not being served
Possible Solution
Not sure
Steps to Reproduce
Here are the logs from the remote host
2022-02-06T15:45:39.106Z backstage info Loaded config from app-config.yaml
2022-02-06T15:45:39.119Z backstage info 0 secrets found in the config which will be redacted
2022-02-06T15:45:39.133Z backstage info Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucket{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
2022-02-06T15:45:39.248Z catalog info Performing database migration type=plugin
2022-02-06T15:45:39.414Z auth info Configuring "database" as KeyStore provider type=plugin
2022-02-06T15:45:39.429Z techdocs info Creating Local publisher for TechDocs type=plugin
2022-02-06T15:45:39.433Z proxy info [HPM] Proxy created: /test  -> https://example.com type=plugin
2022-02-06T15:45:39.434Z proxy info [HPM] Proxy rewrite rule created: "^/api/proxy/test/?" ~> "/" type=plugin
2022-02-06T15:45:39.435Z search info Added DefaultCatalogCollator collator for type software-catalog type=plugin
2022-02-06T15:45:39.435Z search info Added DefaultTechDocsCollator collator for type techdocs type=plugin
2022-02-06T15:45:39.439Z app info Serving static app content from /app/packages/app/dist type=plugin
2022-02-06T15:45:39.727Z app info Injecting env config into module-backstage.66a308d6.js type=plugin
2022-02-06T15:45:39.768Z app info Storing 0 updated assets and 251 new assets type=plugin
2022-02-06T15:45:39.911Z backstage info Initializing http server
2022-02-06T15:45:39.914Z backstage info Listening on :7007
2022-02-06T15:45:39.960Z backstage info ::ffff:<IP_ADDRESS> - - [06/Feb/2022:15:45:39 +0000] "GET / HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36" type=incomingRequest
2022-02-06T15:45:40.219Z backstage info ::ffff:<IP_ADDRESS> - - [06/Feb/2022:15:45:40 +0000] "GET / HTTP/1.1" 200 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36" type=incomingRequest
2022-02-06T15:45:40.818Z catalog warn No processor recognized the entity as valid, possibly caused by a foreign kind or apiVersion type=plugin entity=template:default/golang-starter

Context

Your Environment
The remote host runs on Ubuntu 16.04.6 LTS
Docker version 20.10.7, build f0df350
OS:   Linux 4.4.0-173-generic - linux/x64
node: v16.13.2
yarn: 1.22.17
cli:  0.13.1 (installed)

Dependencies:
  @backstage/app-defaults                                  0.1.6
  @backstage/backend-common                                0.10.6
  @backstage/backend-tasks                                 0.1.5
  @backstage/catalog-client                                0.5.5
  @backstage/catalog-model                                 0.9.10
  @backstage/cli-common                                    0.1.6
  @backstage/cli                                           0.13.1
  @backstage/config-loader                                 0.9.3
  @backstage/config                                        0.1.13
  @backstage/core-app-api                                  0.5.2
  @backstage/core-components                               0.8.7
  @backstage/core-plugin-api                               0.6.0
  @backstage/errors                                        0.2.0
  @backstage/integration-react                             0.1.20
  @backstage/integration                                   0.7.2
  @backstage/plugin-api-docs                               0.7.1
  @backstage/plugin-app-backend                            0.3.23
  @backstage/plugin-auth-backend                           0.9.0
  @backstage/plugin-catalog-backend                        0.21.2
  @backstage/plugin-catalog-common                         0.1.2
  @backstage/plugin-catalog-graph                          0.2.9
  @backstage/plugin-catalog-import                         0.8.0
  @backstage/plugin-catalog-react                          0.6.13
  @backstage/plugin-catalog                                0.7.11
  @backstage/plugin-github-actions                         0.4.34
  @backstage/plugin-org                                    0.4.1
  @backstage/plugin-permission-common                      0.4.0
  @backstage/plugin-permission-node                        0.4.2
  @backstage/plugin-permission-react                       0.3.0
  @backstage/plugin-proxy-backend                          0.2.17
  @backstage/plugin-scaffolder-backend-module-cookiecutter 0.1.10
  @backstage/plugin-scaffolder-backend                     0.15.23
  @backstage/plugin-scaffolder-common                      0.1.3
  @backstage/plugin-scaffolder                             0.12.1
  @backstage/plugin-search-backend-node                    0.4.5
  @backstage/plugin-search-backend                         0.4.1
  @backstage/plugin-search                                 0.6.1
  @backstage/plugin-tech-radar                             0.5.4
  @backstage/plugin-techdocs-backend                       0.13.2
  @backstage/plugin-techdocs                               0.13.2
  @backstage/plugin-user-settings                          0.3.18
  @backstage/search-common                                 0.2.2
  @backstage/techdocs-common                               0.11.6
  @backstage/test-utils                                    0.2.4
  @backstage/theme                                         0.2.14
  @backstage/types                                         0.1.1
  @backstage/version-bridge                                0.1.1
Done in 0.74s.

Browser Information: Chrome 97

Hmm, so there's a few things to look at here. It looks like it's some configuration. There's a hardcoded :7007 port there, but it's running over https: so i'd just export no port there. Make sure that the app-config.yaml has correct setup for app.baseUrl this will be the endpoint that you hit in the browser to hit the container, and if you're deploying frontend and backend together these will most likely be the same as backend.baseUrl

Well spotted! Indeed it tries to load the static files from https... but there is no https in the config and the URL is http...

I'm closing this issue. I wasn't aware that the browsers these days will request files over HTTPS even if the origin is in HTTP... Thank you for your help

It was the CSP configuration :)

@chchrist Can provide more details on what you changed in CSP configuration to handle this? Or did you install certs to enable HTTPS?

Well spotted! Indeed it tries to load the static files from https... but there is no https in the config and the URL is http...

It was the CSP configuration :)

@cb-narayanan-krishnamurthy , @chchrist I too facing similar problems. what is the solution and what is CSP config here?

@guhanath @cb-narayanan-krishnamurthy set csp as follows solved my problem. It's because  upgrade-insecure-requests option default value is true.
csp:
    connect-src: ["'self'", "http:", "https:"]
    upgrade-insecure-requests: false


Refactor #109 Exchange Issuance to Flash Mint

Adds to 109 the refactor commits.
refactor: ExhangeIssuance to FlashMint (WIP)
refactor: ExhangeIssuance to FlashMint.

Relevant pieces cherry picked into the branch and pushed in 74bfbe596786126855c66f4c052d84c6924f11b2


Same markers are getting merged/ignored

https://github.com/labsyspharm/quantification/issues/12
Issue fixed:
https://github.com/labsyspharm/quantification/pull/13
Currently testing

Tested works great! Thank you @JoshuaHess12


Analysis: Look into alternatives to Kafka for a more suitable system for the internal needs of Notifications

Description
Kafka was not a very good match with what Notification needs. In this issue we should work on finding a suitable replacement. A part of this tasks is to take input and experiances from other teams with similar needs.
Additional Information
Dialogporten and Authorization is picking Azure Service Buss and using Mass Transit.
https://www.youtube.com/@nickchapsas/search?query=mass transit
Tasks

[ ] Collect experiences other teams are having with their choices.
[ ] List pros and cons

[ ] Hosting options
[ ] Costs

[ ] Arrange a heated debate

Acceptance Criterias

[ ] A well documented choice of new queue product for Notifications.

Closing as not prioritized. We need external discussions to mature before a change is required. #544 was created to prepare and uncover any blockers for refactoring to the (assumed to be) least complex solution.


Containerize cri tests

add dockerfile to create cri test runner container
add cri runner container setup script
update cri_test makefile
removed rnnserving from the test as it fails to deploy on cri test container

To start the runner:

clone this kind repo fork.
run go build
start a container using ./kind create cluster --image vhiveease/cri_test_runner

Signed-off-by: Shyam Jesalpura<EMAIL_ADDRESS>

please do not forget to add an image for development


Issue running llava/eval/model_video_chatgpt_general.py - Missing eval folder

hi, I am trying to run llava/eval/model_video_chatgpt_general.py, but I noticed that there is no eval folder within the llava directory. Is that wrong?

You can find it at :https://github.com/LLaVA-VL/LLaVA-NeXT/tree/video_inference/llava/eval.


Trib to Buck crossing re assessment was ~60m south of 2020 assessment

I remember thinking this was a little strange when I re assessed this one. It was definitely about 60m away from where the old assessment was on the map. I'm assuming the location will get updated once the re assessments get submitted?

yup


Support setting tags as a single string

Describe the Feature
Datadog supports adding non key:value pairs of tags on a monitor. This module appears to force a key:value pair if the key does not exist.
For example, I have defined:
tags = ["AWS", "Terraform", "EKS"]

What this does is add the following tags to the datadog monitors:

0:AWS
1:Terraform
2:EKS

Expected Behavior
I would like to be able to add a list of tags without prepending their list position as a key for each of the tags.
These tags should instead be added to the monitor:

AWS
Terraform
EKS

Use Case
Datadog supports adding tags this way, so I'd like to add tags as such.
Describe Ideal Solution
N/A
Alternatives Considered
No response
Additional Context
No response

Ok, this may be working as intended and an issue with how we're calling this module. I am working with some existing code and noticed that we're pinning directly to the monitors module.
Apologies for the noise; I will close this.


restore TestUtilities#invokeBytes(String,String,byte[])

In our Tests, we use TestUtilities#invokeBytes(String,String,byte[]) to send dynamically generated content to our services.
This is no longer possible with CXF 3.5 since it was removed in b902794f187035a6efe39e3632ccc7be0adc8a89.
This PR reintroduces the method (and a variant accepting InputStreams).

Since this code is not used in CXF tests - there is no reason to keep it in the sources.


Ingress problem

I configured the master-ip in vars I have also enabled k3s, persistance volume and suffix in vars.jsonnet. My k3s master has the ip <IP_ADDRESS> and the worker <IP_ADDRESS>. Then I did the make vendor, make and make deploy all pods are running but for some reason I cannot access grafana, prometheus and alertmanager. So I checked did kubectl get ingress --all-namespaces and the result was the following. Is there anything wrong with the steps I have perfomed ?
NAMESPACE    NAME                CLASS    HOSTS                             ADDRESS       PORTS     AGE
monitoring   alertmanager-main    alertmanager.<IP_ADDRESS>.nip.io   <IP_ADDRESS>   80, 443
monitoring   grafana              grafana.<IP_ADDRESS>.nip.io        <IP_ADDRESS>   80, 443   12s
monitoring   prometheus-k8s       prometheus.<IP_ADDRESS>.nip.io     <IP_ADDRESS>   80, 443

Sorry I was wrong prometheus-k8s and grafana in sudo kubectl get pods -n monitoring -o wide have pending status

Maybe your PVs were not created. Do you have a storageClass to provide them since you enabled persistence?

I have created 2 pvs one for grafana with the name grafana-pv-volumewith storageClass grafanapv and one for prometheus prometheus-pv-volume with storageClass prometheuspv. If I disable the persistance the status change to running but yet again I cannot access prometheus UI and grafana UI.
enablePersistence: {
prometheus: true,
grafana: true,
prometheusPV: 'prometheus-pv-volume',
prometheusSizePV: '2Gi',
grafanaPV: 'grafana-pv-volume',
grafanaSizePV: '20Gi',
},
Is it normal in ingress to show on host the ip of the master and in the address the ip of the worker ?

I don't know if I have to change something in base_operator_stack.jsonnet to perform the persistant volume claim. For example in the section of prometheus :
(if vars.enablePersistence.prometheusPV != '' then pvc.mixin.spec.withVolumeName(vars.enablePersistence.prometheusPV))
// Uncomment below to define a StorageClass name
+ pvc.mixin.spec.withStorageClassName('prometheuspv')
Also I see that in the section of grafana the pvc part is a litttle bit different and there is not a line like the last one in the above example. I have found this ingress problem in the last commit. I aplogize for writing too many comments, but I was trying some changes at the same time.

After all you were right there is something in persistence volume that is causing the problem, I disabled the persistance and prometheus and grafana UI working fine now. I will try to find what I am doing wrong and I will inform you. I think that the problem is in the claim because in sudo kubectl get pv returns both pvs that I have created.

I found my mistake it was in the persistance volume, I was referring to a storageClassName that it didn't exitst. So I searched if there is one already in the k3s cluster and I found the local-path storageClassName which I also used in the pv yaml files. It finally works !!! Sorry for the trouble
apiVersion: v1
kind: PersistentVolume
metadata:
name: prometheus-pv-volume
labels:
type: local
spec:
storageClassName: local-path
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/mnt/tb1/data"

I have a problem with the persistence of grafana, it cannot create files and folders. When I go to see the logs in the pod I get the error:
GF_PATHS_DATA`` = '/ var / lib / grafana' is not writable. You may have issues with file permissions

Can you retest with latest master?

Can you retest with latest master?
Might be related to 71e9e55
Nothing. I had to change the permissions with chmod 777.

I've enabled Grafana persistence and pointed it to the local-path StorageClass of a K3s cluster. It created the PV and used it correctly to persist dashboards.

I've enabled Grafana persistence and pointed it to the local-path StorageClass of a K3s cluster. It created the PV and used it correctly to persist dashboards.

I did the same thing but nothing. Also in the "grafana" folder in nfs share I only have 1 file and 2 folders:
grafana.db, the plugins folder (empty) and the png folder (empty).

Can you remove the stack, deleting all resources including the namespace and do a fresh deploy?
 Grafana creates files with UID:GID 472:472 and Prometheus with 1000:0.

I've already done it this afternoon. These are my PV, am I doing something wrong?
kubectl get pvc -n monitoring
NAME                                 STATUS   VOLUME       CAPACITY   ACCESS MODES   STORAGECLASS   AGE
grafana-storage                      Bound    grafana      10Gi       RWO            local-path     6h14m
prometheus-k8s-db-prometheus-k8s-0   Bound    prometheus   10Gi       RWO            local-path     6h14m

grafana.persistentvolume.yml
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: grafana
  labels:
    type: local
spec:
  storageClassName: local-path
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/mnt/nas/grafana"
---

prometheus.persistentvolume.yml
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: prometheus
  labels:
    type: local
spec:
  storageClassName: local-path
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/mnt/nas/prometheus"
---

If you are using the local-path provisioner from K3s, don't pre-create the PVs. Just enable the persistence, and define: storageClass: 'local-path', in the vars.jsonnet. Keep the PV names blank.
The stack PVCs will ask for a PV for the StorageClass.

I'm doing a clean installation. But what do your "grafana" and "prometheus" folders contain?

Something like:
❯ tree
.
├── grafana
│   ├── grafana.db
│   ├── plugins
│   └── png
└── prometheus
    └── prometheus-db
        ├── chunks_head
        │   └── 000001
        ├── queries.active
        └── wal
            └── 00000000

Ah ok then all right. Now it works, thank you friend :D.
One last question, how can I assign the prometheus pods to a node? It consumes a lot of memory and I don't know why it always assigns it to the node with less memory.

You need to set node affinity.
Check https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/


Gluon dense layer gets segfault on large arrays when MKLDNN is built in MXNet.

The code below gets segfault when MKLDNN is built in MXNet.
import mxnet as mx
from mxnet import gluon
def run_linear():
    data = mx.nd.ones(shape=(50*1000*1000, 100))
    linear = gluon.nn.Dense(100)
    linear.initialize(ctx=mx.cpu(0))
    res = linear(data)
    res.wait_to_read()

run_linear()

Thanks for the case. MKL-DNN has the plan to support large inputs and will back you later.

@mxnet-label-bot add [MKLDNN, Gluon]

Currently MKL-DNN doesn't support large dimension (> INT_MAX) and that will be change in the v1.0 release of it. Before that, we need fallback the computation to MXNet if the input/output dimension is larger than INT_MAX.
@zheng-da Do you know if large NDArray is already enabled in MXNet or it is just an effort ongoing? Do we need to change MKL-DNN backend in the coming release?

@pengzhao-intel @TaoLv This is a critical bug for the DGL release. @apeforest is working on fixing all mxnet operators. could you please fix this one as well. Thanks.

I‘m working on this issue. Actually, 50*1000*1000 doesn't exceed the range of int32. This case works well with use_bias=False on my side.

@TaoLv a matrix of<PHONE_NUMBER> rows and 100 columns has 5B elements. It exceeds the range of int32.

Yes, but I think that should be covered by MKL-DNN. If not, it's absolutely a bug. I'm working with MKL-DNN team to root cause this issue. Will update to you if any progress. Thanks.

Closed via #13668 .


ctx.params.id is '1' (a string) instead of 1 (a number)

ctx.params seem to be parsed as strings, when it should parse numbers as numbers.

Or maybe not.
There could be Int overflows, float unprecision, etc.
Booleans would be good but false would return if (!input) controversal to a string.


I will create the bitters styleguide as a sketch file with text and element styles included

Hi @simon-smalle
Issues are typically for posting problems or feature requests for the framework. This seems like a personal todo item, so I am going to close this issue.


cli arg excludes not working

apply plugin: "io.gitlab.arturbosch.detekt"

detekt {
        version = "1.0.0-RC15"
        input = files("$projectDir/src/main/java")
        config = files("$project.rootDir/detekt/detekt_config_codecc.yml")
        baseline = file("$project.rootDir/detekt/detekt.xml")
        parallel = true
        disableDefaultRuleSets = false
        debug = false
        excludes = ". */one/. *"
        reports {
            xml {
                enabled = true
                destination = file("$project.rootDir/build/reports/detekt.xml")
            }
            html {
                enabled = true
                destination = file("$project.rootDir/build/reports/detekt.html")
            }
        }
    }

Expected Behavior
work
Observed Behavior
Gradle not work, error message:

What went wrong:
A problem occurred evaluating script.
Could not set unknown property 'excludes' for object of type io.gitlab.arturbosch.detekt.extensions.DetektExtension.

Steps to Reproduce
we use in android app.
Your Environment

Version of detekt used: RC15
Version of Gradle used (if applicable): 4.9
Operating System and version: mac os 10.14.4
Link to your project (if it's a public repository):

That behavior is correct. The property is called exclude without a s.

That behavior is correct. The property is called exclude without a s.

Stil not work with or without s

What went wrong:
A problem occurred evaluating script.
Could not set unknown property 'exclude' for object of type io.gitlab.arturbosch.detekt.extensions.DetektExtension.

The pattern is still wrong. Detekt uses globbimg pattern since RC15.
Reference
Changelog

Argh, @3flex @schalkms should we do an emergency rename from excludes to exclude to match the gradle way or stay with excludes as these are "two different worlds"?

I don't think exclude or excludes was ever supported on the extension? The parameter was named filters (now noop in the plugin and marked with a deprecation message).
Includes & excludes need to be set on the task (see SourceTask)
Perhaps the deprecation message on filters on the extension of "Replace with task setIncludes/setExcludes" is not clear?

Oh I meant the cli flag which got renamed from filters to excludes.
The gradle plugins allows:
    exclude("**/build/**")
    setExcludes(listOf("**/build/**", "\"**/resources/**\""))

I wouldn't do it.

@schalkms yeah with groovy dsl excludes = [..] is possible.

@arturbosch I think we should be more careful with breaking changes towards v1.
I guess we can close this issue.


0.5 staging

Generated new genesis to launch staging 0.5

Superseeded by https://github.com/input-output-hk/cardano-sl/pull/1059


Refactor cstyle render const [run_process_replay]

Resolves #5313

@Qazalin regarding

Should also fix DEFINE_ACC's extra type_verify assert.

I was looking at you convo with geohot regarding thisbut I wasn't able to come to a firm conclusion whether you were saying that fixing #5313 requires an update to the assert, or will be implicitly fixed by the requested change. If the assert needs updating, please let me know.

I'm diff'ing process replay runs + ASSERT_PROCESS_REPLAY=0 with and without commit 61f9453 and I'm seeing different kernels getting generated. So looks like I've got more work to do.

directionally correct.

Note: I added the GEP-VECTORIZE-CONST rule because I was getting some strange UOps sequences without it after updating UOps.const(). Attaching GRAPHUOPS=1 images with (gg.uops.svg) and without the rule (bg.uops.svg) -- note the extra PHI-GEP-VECTORIZE-CONST on the bottom of bg.uops.svg.
Adding assert dtype.count == 1 to render_const causes a bunch of tests to fail, so I'll investigate this and see where that takes me. I'm guessing the reason I'm failing the assert is connected to the CI failures I'm seeing.

@greg-niemeyer when I was playing around with the code, when rendering DEFINE_ACC, it calls render_const with vectorized dtypes sometimes. That might be part of the assert fail.

@greg-niemeyer when I was playing around with the code, when rendering DEFINE_ACC, it calls render_const with vectorized dtypes sometimes. That might be part of the assert fail.

right, I'm digging into the DEFINE_ACC stuff as we speak

Had to add the render_cast for !(int, bool, float) back -- there are longs, shorts, etc. that need their long-form cast rendered.

I'm not super happy with DEFINE_ACC implicitly vectorizing CONST in cstyle. Should I update DEFINE_ACC in UOps such that its src is VECTORIZE or CONST, consistent with its dtype?

Had to add the render_cast for !(int, bool, float) back -- there are longs, shorts, etc. that need their long-form cast rendered.

Yeah I see why you need it.

I'm not super happy with DEFINE_ACC implicitly vectorizing CONST in cstyle. Should I update DEFINE_ACC in UOps such that its src is VECTORIZE or CONST, consistent with its dtype?

Correct, DEFINE_ACC should vectorize the const in src[0].

should also pass run_process_replay.
Seeing extra consts: https://github.com/tinygrad/tinygrad/actions/runs/9878626439/job/27282996159#step:24:52

Also, I'm pretty sure the UPats I wrote are nonsensical and need to be redone. I will be busy the next couple of days but I'll work on this when I can.

Also, I'm pretty sure the UPats I wrote are nonsensical and need to be redone. I will be busy the next couple of days but I'll work on this when I can.

i rewrote the UPats, but they're very verbose. i plan to rework them after i figure out this uop issue.

I'm able to reproduce the GPU/IMAGE and openpilot test failures locally on my M1 macbook with only these two commits:
0152a86c66ff7d7432d5c6fc8ecdf4063ff03155: remove test_const_vectorize_fold
0ff3cb92c13e291b216d949c5a48015f213873a1: remove const folding UPat for VECTORIZE
As I understand it, these patches shouldn't result in test failures, only process_replay failures due to extra casts. Probing further, I found that these patches pass the same tests prior to migrating to the new lowerer, but fail afterward.
This branch was synced to the commit immediately preceding the lowerer change, while this one was synced to the lowerer change itself prior to cherry-picking the aforementioned commits.
The test commands I'm using are:

GPU=1 IMAGE=2 python -m pytest -n=auto test/test_ops.py
PYTHONPATH="." FLOAT16=0 DEBUGCL=1 GPU=1 IMAGE=2 python examples/openpilot/compile2.py
JIT=2 METAL=1 python -m pytest -n=auto test/ --ignore=test/external --ignore=test/models --durations=20

The METAL tests should pass regardless of whether my two patches are present.

FORWARD_ONLY=1 GPU=1 IMAGE=2 python -m pytest test/test_ops.py::TestOps::test_simple_padding_conv2d -s is what I use for most of my debugging, since it seems to be the simplest repro case I have.
Two data points I think are interesting:

I was able to get the tests to pass again by updating the fix_image_idx() function using CONSTs instead of VECTORIZE in the LOAD. Demo branch here. Perhaps it's obvious that this would "fix" the issue given the error signature, but the confirmation is nice.
I was able to get the GPU/IMAGE tests by commenting out a UPat that folds CONSTs via exec_alu(). Demo branch here.

This one was a bit of a surprise to me, though perhaps it should be taken with a grain of salt since it also caused a bunch of the METAL tests to fail.

I tried a bunch of other experiments printing and stepping through various parts of cstyle, and uopgraph with the debugger, but I'm having trouble narrowing the issue down furtherer. Any suggestions would be appreciated.

I instrumented the PatternMatcher rules and identified this UPat as the source of the divergent behavior when using VECTORIZE instead of CONST in the post-lowerer branch. Changing the rule to use UOp.var() instead of UOp.cvar() results in VECTORIZE being matched properly and fixes the GPU/IMAGE and openpilot tests. The AMD test is still failing, so that's the next thing to work on.

can you use vectorize for WMMA too?

Didn't have too much time to work on this today, but I managed to fix the AMD test failure and address some of the review feedback. Tomorrow I'll have more time, so I should be able to make decent progress on cleaning up the UPats, writing tests, and WMMA.

can you use vectorize for WMMA too?

Also, I'll look into what I can do to fix process_replay

Also, I'll look into what I can do to fix process_replay

I was able to remove the extra cast, but undoing the diff to the way parentheses and some dtype casts (e.g. half) are applied in edge cases proved difficult. I tried:

Reverting the conditional logic and val assignment in render_const
adding half here
adding isinf() and isnan() checks here

But these changes caused diffs in other places.

yea that extra render_cast in cstyle is fine for now, it's not your fault. WMMA looks ok too.

I'd keep the cstyle render_cast for now and add [run_process_replay] back. We'll remove that in another diff.
Let's focus this diff on just the CONST -> VECTORIZE change.

I'd keep the cstyle render_cast for now and add [run_process_replay] back. We'll remove that in another diff. Let's focus this diff on just the CONST -> VECTORIZE change.

I made the requested changes and added [run_process_replay] to the PR title, but even with just the minimal update to cstyle required for CONST -> VECTORIZE to work, we have that extra cast in process_replay.
Also, I'm getting on a plane in a couple hours and will be traveling the next two weeks, so my availability will be limited.

I was able to fix the process_replay for METAL tests, but its ugly. AFAICT, ugliness is tough to get rid of due to the differences in VECTORIZE vs implicitly vectorized CONST renders cascading into higher level uops with their own rendering idiosyncracies.

We'll cleanup the rendering diff, because this diff changes UPats too it's better to assert process replay to avoid regressions.

Update -- been short on time due to travel, but making progress. I've got the issue repro'ing locally with gpuocelot in a docker. The particular assertion we're seeing in CI is related to the diff between STORE rendering VECTORIZE vs implicitly vectorized CONST. I tried inlining the const render in the STORE but it results in another diff, so I need to think a little more on how to maintain parity between the renders.

I'm working on a WMMA-related process_replay regression introduced after merging upstream master in my dev branch. Should have it figured out tomorrow.

@Qazalin in light of geohot's comment in #5729, I reverted my process replay hacks in the PTX renderer and kept the change needed to functionally pass the tests. I can provide a detailed write-up of all the classes of PTX process_replay diffs if that's what it takes to get this merged without [run_process_replay]. There are 3 distinct classes of diff and they can all be coherently explained. Additionally, I can revert my hacks in cstyle and do the same for all the process replay diffs there if desired.
I could also just shelve this if it's better to just keep implicitly vectorized CONST for now and not worth the effort to review the diffs.

renderers look much cleaner now! I don't think we need the extra logic for vmin and vmax though

spent some time with this code, I like sconst, you can remove [run_process_replay] from the title, this is gonna simplify kernels.

Woohoo checks passed! Should I mark this PR ready for review?

holding on merging this because AMD got a big performance regression. I think their HIP compiler is missing optimizations it would've done otherwise.
This is a good simplification for tinygrad's internals but we can't do it at the cost of almost 2 orders of magnitude regression in AMD=1 sdxl, even if it's a compiler weirdness.
Are you interested in seeing if we can work around this in a clean way in cstyle? I think we can give you tinybox access.

Are you interested in seeing if we can work around this in a clean way in cstyle? I think we can give you tinybox access.
yeah let's do it

fyi either @wozeparrot or me will give you the tinybox access by EOD.

holding on merging this because AMD got a big performance regression. I think their HIP compiler is missing optimizations it would've done otherwise.

this perf regression was completely my fault. I wrote some pathological UPats that used lists instead of tuple for VECTORIZE.src. since we are using vec(8)'s on AMD, we were doing 8! (+40,000) comparisons when we should have been doing one, worst-case.
still seeing a minor perf regression. with my change, sdxl takes roughly 800ms longer on the first step, then is 300ms faster on the second step, so ~500ms slower in aggregate on AMD=1 sdxl.
this branch:
(tinygrad) greg-niemeyer@tiny10:~/tinygrad$ PYTHONPATH="." AMD=1 python3 examples/sdxl.py --seed 0 --noshow --timing --weights=./weights/sd_xl_base_1.0.safetensors --out=./rendered.png | tee sdxl_good_enuff.txt
ram used:  6.93 GB, sigmas                                            : 100%|█|
100%|███████████████████████████████████████████| 10/10 [00:26<00:00,  0.38it/s]
loaded weights in 17849.89 ms, 6.93 GB loaded at 0.39 GB/s
created batch
step in 13785.81 ms, using 5.30 GB
step in 3052.05 ms, using 7.59 GB
step in 1291.28 ms, using 7.59 GB
step in 1161.24 ms, using 7.59 GB
step in 1162.83 ms, using 7.59 GB
step in 1155.86 ms, using 7.59 GB
step in 1162.48 ms, using 7.59 GB
step in 1157.88 ms, using 7.59 GB
step in 1166.16 ms, using 7.59 GB
step in 1151.83 ms, using 7.59 GB

master:
(tinygrad) greg-niemeyer@tiny10:~/tinygrad$ PYTHONPATH="." AMD=1 python3 examples/sdxl.py --seed 0 --noshow --timing --weights=./weights/sd_xl_base_1.0.safetensors --out=./rendered.png
| tee sdxl_master.txt
ram used:  6.93 GB, sigmas                                            : 100%|█|
100%|███████████████████████████████████████████| 10/10 [00:25<00:00,  0.39it/s]
loaded weights in 17865.05 ms, 6.93 GB loaded at 0.39 GB/s
created batch
step in 13015.36 ms, using 5.30 GB
step in 3394.70 ms, using 7.59 GB
step in 1295.29 ms, using 7.59 GB
step in 1163.01 ms, using 7.59 GB
step in 1163.04 ms, using 7.59 GB
step in 1165.24 ms, using 7.59 GB
step in 1166.17 ms, using 7.59 GB
step in 1165.33 ms, using 7.59 GB
step in 1167.06 ms, using 7.59 GB
step in 1158.80 ms, using 7.59 GB

yea sdxl is still too slow, https://github.com/tinygrad/tinygrad/actions/runs/10216851155/job/28269312677#step:9:1
Can you diff the kernels it's creating by running process replay locally? https://github.com/tinygrad/tinygrad/blob/master/test/external/process_replay/README.md#running-locally
I'd expect this to be a noop change for performance.

Can you diff the kernels it's creating by running process replay locally? https://github.com/tinygrad/tinygrad/blob/master/test/external/process_replay/README.md#running-locally
I'd expect this to be a noop change for performance.

It's not an issue with the generated kernels. I applied my old cstyle hacks for process_replay parity and confirmed that the perf issue is still present, even with identical kernels.
I've been diffing sdxl runs instrumented with cProfile to see if there are any noticeable anomalies in the functions where sdxl is spending the most time, and it looks like the match is still adding significant overhead. I was able to remove two of the GEP-related rules with no discernible impact on local process_replay, and that shaved off some of it, but I still need to figure out the other sources. Will keep digging.

On the tip of my dev branch (after removing the unneeded GEP rules) I'm consitently seeing ~300-400ms overhead when compared to master at the same point in time. The overhead persists regardless of process_replay differences, and I conducted perf analysis on both this dev branch, and one branched from this dev branch + my cstyle hacks for process_replay parity. The results are the same.
Since the kernels aren't the problem, I collected time spent in each function call with cProfile:
PYTHONPATH="." AMD=1 python3 -m cProfile -o sdxl_dev.prof examples/sdxl.py --seed 0 --noshow --timing --weights=./weights/sd_xl_base_1.0.safetensors --out=./rendered.png
and output the top-100 functions sorted by cumtime (see the docs for more details). I diffed the results from my dev branch vs master, and what I see is significantly more calls to PatternMatcher machinery that appear to simply be a function of the increase in UOpGraph edges due to use of more vec(8) UOps:
dev branch:
   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
996688/999    1.363    0.000   22.602    0.023 uopgraph.py:450(__inner_rewrite)
1394669/11943    0.395    0.000   22.389    0.002 uopgraph.py:452(<genexpr>)
   299555    1.899    0.000   19.471    0.000 uops.py:198(rewrite)
5491152/2380667    7.640    0.000   10.755    0.000 uops.py:171(_match)

vs
master:
   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
966380/999    1.592    0.000   22.226    0.022 uopgraph.py:449(__inner_rewrite)
1352103/11943    0.376    0.000   22.014    0.002 uopgraph.py:451(<genexpr>)
   291156    1.870    0.000   18.937    0.000 uops.py:194(rewrite)
5395541/2346966    7.456    0.000   10.168    0.000 uops.py:167(_match)

I think its worth pushing to update_benchmark again to confirm the overhead is not as extreme as what's seen in

yea sdxl is still too slow, https://github.com/tinygrad/tinygrad/actions/runs/10216851155/job/28269312677#step:9:1

But I'm not sure I can do much to eliminate the remaining overhead in the context of this PR. I can keep digging and thinking about it though.

due to use of more vec(8) UOps
Are you sure? Which of these patterns are compounding to 18% slower sdxl? Can we make them faster?

Are you sure? Which of these patterns are compounding to 18% slower sdxl? Can we make them faster?

I'm actively working on this and trying to answer your question definitively, but the going is slow. I am strongly suspecting WMMA as the problematic UOp, but the precise reason why is currently eluding me. I'll have a better write-up for you soon, hopefully.
One thing that concerns me -- I'm unable to reproduce a performance regression of the magnitude seen in the latest update_benchmark run you pushed. If you look at the SDXL run, we see that first step running at step in 23420.09 ms, using 5.30 GB, which is ~2x the normal time.
Running manually on tiny10, i see step1 of this dev branch running around ~13400-13700ms, which is roughly 400ms or so slower than what I see master running at, which is somewhere around 12900-13200ms. That's like a 3% slower run as opposed to a 100% slower run. Is there any environment difference that I should be aware of between tiny10 and the machine CI is running on? Perhaps a different python version or something?

Thanks, really looking forward to merging this.
I just pushed to update_benchmark again, if the issue still remains I'll try to repro on both tinyboxes and give you an update.
Our CI doesn't run on tiny10.

I am strongly suspecting WMMA as the problematic UOp, but the precise reason why is currently eluding me. I'll have a better write-up for you soon, hopefully.

After adding a bunch of instrumentation to the pattern matcher, I see that on master when we have an implicitly vectorized CONST, WMMAs get created, then they hit this rule:
 (NOp.var("add") + NOp(UOps.WMMA, name="wmma"),     lambda add, wmma: UOp(wmma.op, wmma.dtype, (wmma.src[0], wmma.src[1], wmma.src[2]+add), wmma.arg)),
and then, in a lot of cases, the output of that rule gets rewritten by:
(NOp.var('x') + 0, lambda x: x),
When explicit VECTORIZE + CONST is sub'd for the implicitly vectorized CONST, the +0 rule doesn't get hit because the +0 creates a CONST NOp with dtype=None. We still get the correct UOp output in the end, but it goes through a longer, multi-step series of rewrites.
So basically, I'm missing VECTORIZE'd versions of the generic ALU const folding rules. The +0 one is the one hit most by sdxl, and this is responsible for the overwhelming majority of the extra rewrite calls I was seeing.
My latest change includes a hack that I found minimizes the difference of the (relatively minor) perf regression I was able to observe on tiny10, which I was unable to generalize because doing so added back overhead (weirdly enough). My hope was that if the regression observed in CI was correlated with what I was seeing on tiny10, this would prove it and help and I would be able to work on a cleaner solution after the fact.

Thanks, really looking forward to merging this.
I just pushed to update_benchmark again, if the issue still remains I'll try to repro on both tinyboxes and give you an update.
Our CI doesn't run on tiny10.

Unfortunately, by the looks of the latest update_benchmark my hack didn't seem to help, so I'm a bit stuck now. I'm also looking forward to getting this merged, but I'm a little depressed by the results lol. Looking forward to your investigation, thanks for helping.

So all I did was remove the hack and rebase on master, and the benchmark in CI is now showing much improved numbers, though still not exactly the same as what I'm seeing on tiny10. Testing locally on tiny10, I see similar behavior as before where this branch performs step 1 a couple hundreds of a millisecond slower, consistently. If I reapply the hack, that slowdown goes away. Regardless, if I just wrap the sdxl.py command with time, there's basically no diff between the perf of this branch (with or without the hack) and master (synced to the same state that's getting merged back into the dev branch) -- and looking at how process_replay works and the headers from the update_benchmark job, wrapping the command in time is not too far off from how CI is benchmarking the run.

timings look much better! Let's move forward with this once CI passes.

I wonder if render_const and some more cstyle/ptx stuff can be simpler now.

I wonder if render_const and some more cstyle/ptx stuff can be simpler now.

I think so -- the original purpose of #5313 can probably be addressed. I'm down to push more changes toward this end.

#5991 simplifies cstyle render_const. I can look for more simplifications and push them in separate PRs, or pile more into that one if there's other low hanging fruit.

oof -- i forgot there's process replay stuff that happens when trying to simplify that way. i closed it and will open another when i have something decent.

#6024 should be good for render_const


BUGFIX - Dynamic paths with new file structure

Fixing previously static paths that were not functioning with the new file structure

@RomanGoEmpire would you check this quickly and confirm that this is needed and works with your file structure. Found some parts of code that had static paths


Is it necessary to send notifications when the status changes from down to up?

Hi, when I looked at the source code I had a question.
We know that the initial state is init, It is currently handled here:
❌ no notification
✅ send notification

init -> up Initial Status ❌
init -> down ✅
up -> down ✅
down -> up ✅ // here
up -> down ✅
down -> down ❌
up -> up ❌

So my question is do we need to send a notification when the status changes from down to up?

we do send the notification when the status is changed from down to up!

thank your update, I get new knowledge.
but I have a little question, If we are sending notifications when the state changes(ET), then why don't we do anything when the state changes from init to up?

because this is the first time, it's a special case.

okay, thank you a lot.


[HHH-14676] PostgreSQLSkipAutoCommitTest ends up with a NPE on PostgreSQL Plus 13.1

https://hibernate.atlassian.net/browse/HHH-14676
https://issues.redhat.com/browse/JBEAP-22074

Thanks


Precompute mapping of string content types to well known types to imp…

…rove mediatype parsing when content types are known.
MediaType.parse is relatively slow as it supports all the variability of a content type. As servers only deal with a small number of media types in practice, it is wasteful to do this parse for every single request. Conveniently, servers also have a good idea of what media types they will support, so we can just precompute a mapping from String to MediaType.
A map like this should save memory / minimize garbage as all hits will result in sharing the same MediaType instance among requests. MediaType.parse itself has an interning cache, but it only recognizes its well known types, while this one also includes our SerializationFormats.
A LoadingCache could also be used to be more general, but I feel like it would help a more limited use case (we'd probably want to add it as a layer after the precomputed map either way since it would have some synchronization overhead).
Benchmark
Benchmark                           Mode  Cnt         Score         Error  Units
HttpHeadersBenchmark.parseKnown    thrpt   20  13516374.953 ±  758315.535  ops/s
HttpHeadersBenchmark.parseUnknown  thrpt   20    700837.841 ±   38172.512  ops/s

Good point - moved

@anuraaga Seems like there's some cyclic dependencies involved during class initialization. Could you check the build log?

Great job, @anuraaga ! :-)


Dropbox Folder Issue

I have successfully mounted the dropbox. It shows up in my file system, and I am able to see the first level of folders in my dropbox. However, I cannot access anything past the first level of folders in my dropbox. I can select the folders but not open them. The file system essentially freezes up. I have tried restarting my device but that did not change anything.

@turbotgu I cannot understand your situation. Probably, some error occurred. Could you check the Console Log on the DevTools using the way described below?
https://github.com/yoichiro/chromeos-filesystem-dropbox/wiki/How-to-Capture-the-Console-Log-of-DevTools

I followed the instructions from the link. Here is the result.

@turbotgu It seems that there is no error... Could you re-capture the console log after you enter the directory where this issue is reproduced?

Sorry for the delay. My chromebook installed an update today and after I re-mounted the dropbox, it started working properly.

@turbotgu I see, close this issue. If you find some issue again, register it as a new issue. Thank you for the reporting.


PhantomJS error while npm install

Hello,
I am trying to do npm install but it gets failed with following stacktrace

<EMAIL_ADDRESS>install /home/harish/Projects/a-server/node_modules/phantomjs-prebuilt
node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1//phantomjs-2.1.1-linux-x86_64.tar.bz2
Saving to /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
Receiving...
[=---------------------------------------] 2%
Error making request.
Error: read ECONNRESET
at exports._errnoException (util.js:870:11)
at TLSWrap.onread (net.js:544:26)
Please report this full log at https://github.com/Medium/phantomjs
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phantomjs-prebuilt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs phantomjs-prebuilt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls phantomjs-prebuilt
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/harish/Projects/a-server/npm-debug.log

ECONNRESET generally means a network error. Try again? Perhaps on a different network?


Not an issue: How can we create a circle?

Just like section box(SEC class) can we create a circle?

Hi @saurabhsonkar,
so SEC in PTOCA is Set Extended Color. I can think of several options to create a circle in AFP

include an image (IOCA or object container)
include a pdf that has a vector image in it (object container)
use a font like wingdings that has some circle shaped glyph
use an arc command in a GOCA drawing subset

Programming wise number 2 may be the easiest one. Depending on what you want to achieve number 4 may make the most sense but also is a lot of programming effort (lots of structured fields to create).

Thank you, Yan for brief reply. I'm just curious about the last approach. Could you please provide me a snippet.

no I don't have a sample, sorry :) - closing as this is a year old


Attribute fix for backend dispatch module

Thank you @shyim.
This PR is identical to #421. As written there, we won't implement this fix due to a whole new attribute management in Shopware 5.2. For more informations refer to PR #421.


Feature/connectors

@alexflav23 do you have a timeline for when this will land back in develop / into a release?

@benjumanji Yes, within the next 2 - 3 days. I'm aiming for today but that's overly optimistic. I will let you know when an intermediary has been published, at the very least I can have something on the Websudos Maven repo soon enough.

2 - 3 days suits me perfectly, and if I need to test it quicker I'll just stash a local build. Thanks!


coral-web: Move deployment dropdown to main nav

Description

move deployment dropdown to top of page so it is less hidden
auto-select the first available deployment on page load

Desktop

Mobile

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


origin/history-chat

update for the function

Jon there's no bugs but the issue is all the chats are being displayed in reverse order and are being stacked one on top of the other. We only want the one most recent past chat if that's possible


Storages as a public api? And a delete function?

Have we considered making storages part of the public API of the CacheClient objects?
Here's my thinking for why it might make sense. Over at Patent Client, I deal with a lot of US and EU government systems that are super flakey in their responses, and sometimes I get a bad response with a valid status code (i.e. a 200 status code with an error message in the body). I frequently want to detect that and delete the response out of the cache (but otherwise cache the response if it is valid).
Right now, I subclass out a file storage and add this feature expressly, as seen in my base session.py. But it might be handy to be able to arbitrarily delete cache entries manually as a first-class feature. And it would support potentially including other utility functions for interacting with the cache directly to add/delete/inspect responses in the cache.
Something that would look like this:
>>> import hishel
>>> client = hishel.CacheClient
>>> response = client.get("https://www.super-flakey.com")
>>> response
<Response 200>
>>> response.body
'ERROR! I hate this response and gave you bad data'
>>> client.storage.delete(response.extensions['cache_metadata']['cache_key'])
>>> response = client.get("https://www.super-flakey.com")
>>> response
<Response 200>
>>> response.body
`Here is the data you asked for: data`
>>> response.extensions['from_cache']
False

Or you could clean up the API a bit and allow the storage.delete function to take a Response object and strip off the cache key or raise an error if it isn't from the cache:
>>> client.storage.delete(response)

Thoughts?

The first thing that comes to mind is not the delete functionality, but some kind of middleware or filter functionality that the user can provide to prevent some responses from being cached.

For example:
import hishel

def response_filter(response) -> bool:
    if response.status_code == 202:
        return True
    return False

storage = hishel.SQLiteStorage(filters=[response_filter])  # :memory: be default
hishel.CacheClient(storage=storage)

First, thanks for this much needed package!
I wonder if there's been any progress on this? Having an option to do client.storage.delete(response) can be very helpful, especially, for cases where the response is always a json, even if a request fails, that contains an error message.
I am the developer of a package called AsyncRetriever that uses aiohttp-client-cache. I want to switch to using httpx and the deleting functionality is the only missing feature in hishel.

First, thanks for this much needed package!
I wonder if there's been any progress on this? Having an option to do client.storage.delete(response) can be very helpful, especially, for cases where the response is always a json, even if a request fails, that contains an error message.
I am the developer of a package called AsyncRetriever that uses aiohttp-client-cache. I want to switch to using httpx and the deleting functionality is the only missing feature in hishel.

Hi!
Actually, I thought about something like filtering. I think it will cover more cases, but for now, let's just add something like storage.remove.
I will try to find time to add this feature, or if someone is interested, I can guide them on how we can do that.

Thanks! I'd be happy to help.

My apologies for the delayed response. I have opened an issue related to this matter, where I have described the necessary changes we need


[Bug report] default theme sidebar item fails to be active in build mode

Bug report
Description
The default theme sidebar item fails to be active in built prod static site.

import { defineUserConfig } from 'vuepress';

export default defineUserConfig({
  themeConfig: {
    sidebar: [
      {
        text: 'hello',
        children: ['/hello', '/hello/other']
      }
    ]
  }
});

Build the static site, and then open a http server on the dist.
Open the hello page (http://<IP_ADDRESS>:3000/hello/), the sidebar item "index" is not properly active.

Steps to reproduce

Reproduction link / repo: https://github.com/yjl9903/vuepress-sidebar

Expected Screenshots

Environment info

Browser: Microsoft Edge 99.0.1150.46 (64)
Output of vuepress info:

# Paste output of `vuepress info` here
  System:
    OS: Windows 10 10.0.19043
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
    Memory: 17.86 GB / 31.90 GB
  Binaries:
    Node: 16.14.0 - ~\AppData\Local\Temp\fnm_multishells\25188_1647919077642\node.EXE
    Yarn: Not Found
    npm: 8.3.1 - ~\AppData\Local\Temp\fnm_multishells\25188_1647919077642\npm.CMD
  Utilities:
    Git: 2.35.1.


New Release

Can you please add a new release with the newest code? Cause the latest release Is from a year ago. I know i can manually download newest version but it would be much simpler to just download from release
Thank you :)

(also I love this script so much!)

Updated just for you 🙏

Thank you  you are the kindest:D


Adding minimum CPU instructions to common customizations section

Add minimum CPU instructions to common customizations section
Instructs user how to specify a minimum CPU during cluster and node creation.

This change is

/assign
/ok-to-test

Preview: https://deploy-preview-1463--competent-brattain-de2d6d.netlify.com/docs/gke/customizing-gke/#specify-a-minimum-cpu

Hi @sarahmaddox, thanks for the feedback, those are good practices to keep in mind; I've revised my PR per your suggestions. Please let me know if I missed anything.

Thanks @Meadosc!
/lgtm
/approve


Segmentation fault when running Squoosh with Node 16 (ARM)

Describe the bug
Squoosh causes a segmentation fault when compressing images when using Node V16 (ARM build).
To Reproduce
Steps to reproduce the behavior:

Install Node 16 (ARM native version) on an ARM device. (The error will not occur with non ARM versions of node)
Clone this repository that contains a simple node application that converts a jpg and png to webp using squoosh.
Install the dependencies.
Run the index.js script.
See the following error:

Expected behavior
Squoosh should be able to convert the images to WEBP without causing a segmentation vault when using the ARM native Node V16.
Version:

OS w/ version: macOS Big Sur 11.4
Node version: 16.3.0
npm version: 7.15.1

Additional context, screenshots, screencasts
This issue first came up in the following issue on the next.js repository.

I just published @squoosh/lib v0.3.0 which has a rebuild of all our codecs. I just tested it on my M1 with Node 16 and it worked. Can you give it another try?
I’ll close this bug, but please re-open if it’s still breaking for you!

The reproduction I shared still throws an error for me: zsh: bus error  node index.js when upgrading to v0.3.1

Interesting. You seem to have found a v8 bug with WebAssembly on M1 here.
Your test case works fine if we disable the optimizing compiler: node --no-wasm-tier-up ./index.js
I’ll see if I can get this reduced further to forward to the v8 team.

Another fun thing: It also doesn’t crash (for me) if I restrict v8’s thread pool size to < 4: node --v8-pool-size=3 ./index.js

So it seems to be an upgrade issue. If I disable either the baseline compiler or the optimizing compiler, everything works fine. If I wait like 500ms before invoking the webp encoder, everything works fine. It seems that the Wasm module starts running with the output from the baseline compiler but then switches over to the output of the opimizing compiler and that makes it fail. The issue also happens with AVIF and WebP2, but not with JPEG-XL, MozJPEG or OxiPNG.
Sadly, I haven’t been able to reproduce that issue in a smaller test-case.

Sounds interesting! Unfortunately my knowledge of WASM fairly limited 😅
Thanks for looking into it! 🙏🏻

Talked to the v8 team. It is likely that this bug has been fixed a couple of days ago, and the fix should be included as of v8 9.3.
I checked the nightlies of Node 17, which is still based on v8 9.1, so we’ll have to wait a couple of days until I can check that this is indeed fixed.
Until then, I’m trying to figure out if there is a user-land workaround. I know that waiting ~100ms between Wasm instantiation and Wasm usage can significantly reduce the chances of the error happening, but not sure how to expose that or bake that in.

@surma Which version of Node.js was it fixed in?
I was still able to reproduce with Node.js v17.0.0-nightly202107074de6f207dc that was built today.
git clone https://github.com/trm217/reproduce-squoosh-segmentation-vault-on-arm
cd reproduce-squoosh-segmentation-vault-on-arm
curl https://nodejs.org/download/nightly/v17.0.0-nightly202107074de6f207dc/node-v17.0.0-nightly202107074de6f207dc-darwin-arm64.tar.gz | tar -zx
./node-v17.0.0-nightly202107074de6f207dc-darwin-arm64/bin/node index.js

It was fixed is no version of Node as of yet. I thought it was fixed in v8 v9.3 (you can see your v8 version via process.versions.v8). But they found another bug related to this on M1, so my hunch is that we have to wait for v8 v9.4.

It was fixed is no version of Node as of yet. I thought it was fixed in v8 v9.3 (you can see your v8 version via process.versions.v8). But they found another bug related to this on M1, so my hunch is that we have to wait for v8 v9.4.

Are these issues tracked somewhere that are publicly accessible?

Sure: https://crbug.com/1224882

Opened a bug on Node to backport the fix to Node 16: https://github.com/nodejs/node/issues/39327

The underlying issue is reported to be fixed as of Node 16.5.
Ref:
https://github.com/vercel/next.js/issues/24421#issuecomment-880076739

Hi! I'm having the same error than this thread is talking about. My mac is an intel one x86. I'm using @squoosh/lib 0.4.0 and trying to do a simple webservice to optimize image size with express.js.
I'm getting: zsh: bus error npm run start error every time I try to encode an image.
Steps to reproduce:

Install Node 16 LTS, last version the time writing this is: 16.13.1.
Run the code that I will paste here.
Run npm run start.
Post an image, I'm testing with a 35MB image png.

index.mjs
import express from 'express';
import formidable from 'formidable';
import fs from 'fs';
import {cpus} from 'os';
import {ImagePool} from '@squoosh/lib';

const app = express();
const port = 9091;

app.post('/squoosh', (req, res) => {
  const form = formidable({});

  form.parse(req, async (err, fields, files) => {
    if (err) {
      console.log(err);
      return;
    }

    const file = files.file[0];

    if (file) {
      const data = fs.readFileSync(file.filepath);
      const imagePool = new ImagePool(cpus().length);
      const image = imagePool.ingestImage(data);
      await image.decoded;

      const encodeOptions = {
        mozjpeg: {},
        jxl: {
          quality: 90,
        },
      };

      const optimizedImage = await image.encode(encodeOptions);
      console.log('Image encoded');
    }
  });
});

app.listen(port, () => {
  console.log(`App listening at http://localhost:${port}`);
});

package.json
{
  "name": "squooshsaas",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node --no-wasm-tier-up index.mjs"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.17.2",
    "@squoosh/lib": "^0.4.0",
    "formidable": "^3.2.1"
  }
}

Version:

OS w/ version: Monterey 12.0.1
Node version: v16.13.1
npm version: 8.1.2
v8 version: <IP_ADDRESS>-node.14


Custom error parsing

My API behaves so that when the user tries to login and it fails, the error is given as a JSON body in the response like this:
{"non_field_errors":["Unable to log in with provided credentials."]}
Sadly all that I get back from CodyFire is "Something went wrong..." from here, since the error response doesn't contain a message property and it's not an array.
Would it be possible to simply give the entire JSON response back to the error? Or that I can override the error handling logic on a per-request basis?

Ah never mind, I see that I do have access to error.raw. Still, it would be very nice if CodyFire wouldn't make assumptions about error responses like it does now :)

Hm sadly the Data extension parseJSON is not public but internal, so it's not very easy to parse the raw error without duplicating this logic.
Even better of course would be to have Codable errors, strongly typed. I am now doing something like this, but would hate to do that for every request:
    }.onError { error in
      if let rawErrorData = error.raw {
        let decoder = JSONDecoder()
        decoder.keyDecodingStrategy = .convertFromSnakeCase

        do {
          let decodedError = try decoder.decode(LoginError.self, from: rawErrorData)
          print("decodedError: \(decodedError.nonFieldErrors[0])")
        } catch {
          print("Well, it's not a `nonFieldErrors` type of error :p")
        }
      }
    }

Another good example of an error I get is from the register endpoint:
{
  "username":["A user with that username already exists."],
  "email":["Enter a valid email address."]
}


value-suppressing uncertainty palettes

I saw this a year ago, but only now found the need to use value-suppressing uncertainty palettes. Is there a mechanism for defining such a color palette in holoviews? It's essentially a bivariate color palette.
https://medium.com/@uwdata/value-suppressing-uncertainty-palettes-426130122ce9

That looks pretty cool! You could probably emulate something like it using color=dim(value_dimension), alpha=dim(value_dimension_uncertainty). I know it's not the same, but it should make colours appear at least paler depending on their uncertainty, no?

In our published work we have used the hv.HSV() element for this purpose, which is a ternary space where the Saturation can be used for uncertainty when using a white background, and the Value can be used for uncertainty when using a black background, with the Hue for the actual variable of interest.  That works well only for a cyclic variable (orientation in our applications), unless you clip your value to a small range of the Hue space.  And HSV is a highly nonlinear perceptual space, which has many disadvantages.
The complex_colormap package provides a perceptually uniform bivariate space that I've previously thought might be useful.  I'd be happy to include that code in colorcet if someone wants to package it nicely into a PR; I haven't had any time to make that a priority.  And I'd be happy to have other bivariate approaches in colorcet if they are perceptually uniform; again it would be great to see a PR on colorcet.  Once it's in colorcet we should be able to make use of it in HoloViews.
There is also some ternary colormap code from the author of colorcet's colormaps that could be useful.

Would it currently be feasible to implement a way of directly including such multivariate colormaps into holoviews Elements in the same way, using something like a color=[dim(vdim1), dim(vdim2)] syntax?


Align sample in JavaDoc

Coverage remained the same at 98.295% when pulling 3b3cb910e50f0f9d7d390bd583418839bf563de8 on Abrasha:feature/align-samples-in-javadoc into ccfb4562b71c5abf4ddf5f761b56acc90bdc4af2 on apache:master.

Thanks!


GAM update on MacOS 15.1.1 not working

im on MacOS 15.1.1 (m3 chip) running GAM 7.00.40
and when i try to upgrade i get:
bash <(curl -s -S -L https://git.io/install-gam) -l
Checking GitHub URL https://api.github.com/repos/GAM-team/GAM/releases/latest for latest GAM release (unauthenticated)...

Getting file and download URL...

Sorry, you are running MacOS 15.1 but GAM on arm64 requires MacOS  or newer. Exiting.

Short term fix:
go here: https://github.com/GAM-team/GAM/releases/tag/v7.02.00
download: gam-7.02.00-macos15.1-aarch64.tar.xz to ~/bin
do: cd ~/bin
do: tar -xvf gam-7.02.00-macos15.1-aarch64.tar.xz
What do these show:
uname -m
sw_vers -productVersion
echo $(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}')

Cheers Ross @taers232c
manual install worked.
outputs:
uname -m
arm64
sw_vers -productVersion
15.1.1
echo $(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}')
15.1
python -V
zsh: command not found: python
python3 -V
Python 3.9.6

Can we do a Meet/Zoom right now?
Ross Scroggs
@.***

On Dec 9, 2024, at 6:08 PM, Ben McNeil @.***> wrote:
Cheers Ross @taers232c https://github.com/taers232c
manual install worked.
outputs:
uname -m
arm64
sw_vers -productVersion
15.1.1
echo $(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}')
15.1
python -V
zsh: command not found: python
python3 -V
Python 3.9.6
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1727#issuecomment-2530046275, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL2J2A3SNJUYJSQOK2T2EZEKNAVCNFSM6AAAAABTHXAOU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZQGA2DMMRXGU.
You are receiving this because you were mentioned.

It sounds like GAM is failing to retrieve the release information from GitHub, that's where the required version information is determined. My guess is your device or network is blocking the install script from retrieiving GitHub URLs. What does:
curl -vvvv https://api.github.com/repos/GAM-team/GAM/releases/latest

show on the machine?

ohh enterprise ssl inspection crap is a very likely cause and im embarresed
to say i didnt try and by-pass that before i reported it here.
i cant easily test that theory on my prod machine as the update bash now
spews an error i dont understand at all:
Checking GitHub URL
https://api.github.com/repos/GAM-team/GAM/releases/latest for latest GAM
release (unauthenticated)...

On Thu, Dec 12, 2024 at 9:31 AM Jay Lee @.***> wrote:

It sounds like GAM is failing to retrieve the release information from
GitHub, that's where the required version information is determined. My
guess is your device or network is blocking the install script from
retrieiving GitHub URLs. What does:
curl -vvvv https://api.github.com/repos/GAM-team/GAM/releases/latest
show on the machine?
—
Reply to this email directly, view it on GitHub
https://github.com/GAM-team/GAM/issues/1727#issuecomment-2537335505, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALQQBYKUJROQMLQ2452BIUD2FC4KXAVCNFSM6AAAAABTHXAOU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXGMZTKNJQGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

That's a temp error I created trying to provide better error reporting
here. Try again in a minute and it should work.
Jay Lee
On Wed, Dec 11, 2024 at 3:34 PM Ben McNeil @.***> wrote:

ohh enterprise ssl inspection crap is a very likely cause and im
embarresed
to say i didnt try and by-pass that before i reported it here.
i cant easily test that theory on my prod machine as the update bash now
spews an error i dont understand at all:
Checking GitHub URL
https://api.github.com/repos/GAM-team/GAM/releases/latest for latest GAM
release (unauthenticated)...

On Thu, Dec 12, 2024 at 9:31 AM Jay Lee @.***> wrote:

It sounds like GAM is failing to retrieve the release information from
GitHub, that's where the required version information is determined. My
guess is your device or network is blocking the install script from
retrieiving GitHub URLs. What does:
curl -vvvv https://api.github.com/repos/GAM-team/GAM/releases/latest
show on the machine?
—
Reply to this email directly, view it on GitHub
https://github.com/GAM-team/GAM/issues/1727#issuecomment-2537335505,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ALQQBYKUJROQMLQ2452BIUD2FC4KXAVCNFSM6AAAAABTHXAOU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXGMZTKNJQGU>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/GAM-team/GAM/issues/1727#issuecomment-2537416989, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDIZMGERZ2YCKENWMSY2UL2FDDZ5AVCNFSM6AAAAABTHXAOU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXGQYTMOJYHE
.
You are receiving this because you were assigned.Message ID:
@.***>

confirmed, the update command does now work on my production machine (that i manually upped to 7.02.00 earlier.
for me test is the way to get a specific version:
bash gam-install.sh -v 7.00.38

on my test machine, with the enterprise ssl inspection stuff:
bash gam-install.sh -v 7.00.38 did install 7.00.38
then  bash <(curl -s -S -L https://git.io/install-gam) -l successfully updated it to 7.02.00
¯_(ツ)_/¯


Update codespace

Update the Codespace tutorial to open a branch and commit to this branch.
@shiltemann Could you take a look it something is missing. Is it ok to delete the parts where they did not had to create a branch? Or is it better to show this as a third option?

thanks @teresa-m!


Add jenkins config file and job details for all tests

Signed-off-by: Sayali Gaikawad<EMAIL_ADDRESS>Description
Add jenkins config file and job details for all tests
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
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 #2660 (606f480) into main (da8cc11) will increase coverage by 6.05%.
The diff coverage is n/a.

:exclamation: Current head 606f480 differs from pull request most recent head e0e8eb3. Consider uploading reports for the commit e0e8eb3 to get more accurate results

@@              Coverage Diff              @@
##               main     #2660      +/-   ##
=============================================
+ Coverage     93.94%   100.00%   +6.05%
=============================================
  Files           219         6     -213
  Lines          4494       105    -4389
  Branches         29        19      -10
=============================================
- Hits           4222       105    -4117
+ Misses          266         0     -266
+ Partials          6         0       -6

Impacted Files
Coverage Δ

src/ci_workflow/ci_check_lists.py

src/release_notes_workflow/release_notes.py

src/ci_workflow/ci_manifest.py

src/test_workflow/integ_test/service_opensearch.py

src/build_workflow/builder.py

src/manifests/manifests.py

src/sign_workflow/signer_windows.py

src/test_workflow/test_recorder/test_recorder.py

...sts/jenkins/jobs/ArchiveAssembleUpload_Jenkinsfile

src/git/git_repository.py

... and 203 more

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


Use defer function for tmpfile

I was thinking that perhaps it is better to try to remove the tmpfile regardless of any success or errors may follow via a defer function.
It couldn't be done like this for the bakgo folder because some os.Stat checks are made on the godir and depending on the result of that process the bakgo folder is removed or not. However should it not always be attempted to remove the tmpfile?

The tmpfile is put in the TMPDIR, so it will automatically get removed by the OS. Personally I like to have it left there so that I can go investigate what went wrong — if unpacking fails, I want to be able to look at the thing it failed to unpack, and determine why the failure happened.
However, I'd definitely support having the program print out the path to the tmpfile for the user to decide what to do with it.

I see, do you mean something like this?


Schema definition incorrect and causes sample streaming application to fail

The schema definition specified in the first notebook code cell is incorrect.  The Spark types need to be changed from IntegerType to LongType.  Otherwise, the streaming application failed.
Here's the corrected schema definition (replaces lines 12 and 13
StructField("wcs_click_date_sk",LongType,true), StructField("wcs_click_time_sk",LongType,true), StructField("wcs_sales_sk",LongType,true), StructField("wcs_item_sk",LongType,true),
StructField("wcs_web_page_sk",LongType,true), StructField("wcs_user_sk",LongType,true)

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

ID: 1c639fd7-43ee-f24d-ce5e-530077367aab
Version Independent ID: 28059c60-abe8-e4f8-08c5-221c926f007e
Content: Ingest data with Spark jobs - SQL Server big data clusters
Content Source: docs/big-data-cluster/tutorial-data-pool-ingest-spark.md
Product: sql
Technology: big-data-cluster
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@dgshaver  Thank you for the feedback, assigning this to the author for review.

Opening pull request to resolve.


Mount-SPContentDatabase will also create a database if it doesn't exist

Instead of returning an error, Mount-SPContentDatabase will actually create a brand new blank content database if the specified database doesn't already exist.
This can lead to hours of head-scratching trying to find "missing" site collections when a typo on a database name is made.
Ideally the behaviour could be changed, or a "-ErrorIfMissing" added, etc., but at the very least a mention here in big letters here in the docs would be great.
<3
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9e5b70e0-6664-00dc-0083-89b2451fb344
Version Independent ID: 99ad8c9d-f333-adda-b0fd-5c9cf426f66c
Content: Mount-SPContentDatabase (sharepoint-server)
Content Source: sharepoint/sharepoint-ps/sharepoint-server/Mount-SPContentDatabase.md
Product: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

Hello @fowl2 James,
Thanks for your feedback, I could verify this on SHP2019, will make an edit to the article to improve it to warn about this.
Thanks again


Add persistent volume configuration to support NFS

The fix contains following content:

Add NFS related configuration in kubernetes/internal/persistent-volume-template.yaml
Add two configurable parameters (persistenceType and nfsServer) in kubernetes/create-domain-job-inputs.yaml
Update kubernetes/create-domain-job.sh
3.1 Validate the two input parameters. The value of persistenceType must be hostPath or nfs. If using nfs, nfsServer must be specified.
3.2 Generate the correct persistent volume yam file based on input parameters.
Fix a typo.  validatePersistenVolumeName --> validatePersistentVolumeName

Jenkins passed http://wls-jenkins.us.oracle.com/job/weblogic-kubernetes-operator/86/

Looks good to me.
It would be nice if we could add a test case in the integration test suite for this feature. We'll need a NFS server that is accessible from different environments, such as hosted box, wercker pipeline, and Jenkins machines.

I agree with Dongbo that a run.sh test case would be nice - perhaps by modifying one of the existing domains that are already tested (domain3 or domain4?).    I suggest testing it only when QUICKTEST is not true and JENKINS=true with Brian Moyers help to setup a permanent NFS location.   You can design the test on hosted linux, but IIRC, getting NFS up on running on arbitrary hardware is problematic --  we don't want to assume there's root access on hosted linux or Jenkins.

Fixes issue #100

Since the commit has been merged, I suggest close this pull request.
I have created a new JIRA task for testing NFS in  integration test suite. See https://jira.oraclecorp.com/jira/browse/OWLS-63719

Can you add the new parameters to the table in weblogic-kubernetes-operator/site/creating-domain.md?

A new pull request is created for it. Thanks.


Fixes #12 Modernize

is this all that I need to do for this? @grizz (nevermind)

remove precommit from dev deps


bitmex swagger Generated API

I have active operations with kucoin, and have no issues with odrotleff progress on wallet usecase.
i did not roll back my kucoin merge before tackling bitmex, but I would say it's ready for others to beat on, it WFM.
I have attempted Bitmex wallet usecases and there is a stackoverflow recursive call in getAccountInfo and most methods are still stubs.  i found a way to move forward.
I found the swagger.json on bitmex's site and generated the api therein
the bitmex codebase is incomplete, but sort of works with XChange.   the swagger code IS complete, but this exchange is obviously a ferrari and the XChange controls are for a prius with no common design or porting done yet.
if there's a bounty, I could be encouraged to look into this further.
Thanks

I'm not sure if I'm a fan of all the swagger generated code. 264 new files? Since Kucoin and bitmex are already implemented, why is this better? Sorry for the Swagger ignorance.

im normalizing, i can split out the jkucoin and revise.  the docs is included in the patch request, the generated artifacts are one per api, but small.  if i could find a swagger->mmazi solution i would re-issue this patch generating thru that.
the tradeoffs for the generated file s(and docs) is that these are code-generation, and the technical debt is low, if the api changes, the codebase will not be far behind the republished swagger IDL.
the existing bitmex stopped my progress because:
a) use base64 which is unspecified anywhere, and conflicts with all 8+  other ecxhanges i store api keys for causing failure on load
b) never implemented accountService which was what prompted me to find an implementation strategy (calling accountInfo method causes stack overflow!)
c) the impl's in place are hand built for some personal usecases that have no resemblance to anywhere else in the codebase, especially the bimap wierdness.
noone has ever implemented the signature header (until yesterday?) so im not sure what level of implementation or rigor was applied.
d) numerous brittle inventions (guava, bimaps anyone?) focussed on futures.

im detecting some new conflicts i hadnt yet seen before.
will revisit.

"placeStopOrder" has been problematic for getting this merge in.  it builds/tests fine if i dont merge upstream.

this is the third or fourth time I have stepped away from a working patch set and returned to find conflicts.  the bottom line is that the bitmex client is vastlky more complex than what is implemented in the bitmex attempts to date, and also comes with a code generation option.  it appears there are 3 concurrent attempts to solve the same problems, access to the online api's.
i've got no time to keep patching conflicts.  i will disable bitmex from my codebase if the features don't work.


fix for blur

oops, i broke the ability to clear out a route with  #161. this fixes that.

not want your static/.DS_Store...


--show-source used together with isort and line continuation characters panics

from module import member1, \
     member2

❯ RUST_BACKTRACE=1 cargo run test.py --show-source --select I --no-cache
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Line index out of bounds: line index 3, Rope/RopeSlice line count 2', /home/squiddy/.cargo/registry/src/github.com-1ecc6299db9ec823/ropey-1.5.0/src/rope.rs:764:41

<snip>

   4: ropey::rope::Rope::line_to_char
             at /home/squiddy/.cargo/registry/src/github.com-1ecc6299db9ec823/ropey-1.5.0/src/rope.rs:764:9
   5: ruff::source_code_locator::SourceCodeLocator::slice_source_code_range
             at ./src/source_code_locator.rs:43:19
   6: ruff::message::Source::from_check
             at ./src/message.rs:58:22
   7: ruff::linter::lint::{{closure}}
             at ./src/linter.rs:353:26

<snip>

When running cargo run resources/test/fixtures/isort/* --show-source --select I I can see some seemingly wrong check locations. The source code slices are cut off, e.g.
resources/test/fixtures/isort/combine_as_imports.py:1:1: I001 Import block is un-sorted or un-formatted
  |
1 | / from module import Class as C
2 | | from module import CONSTANT
3 | | from module import function
4 | | from module import function as f

(Just clarifying to myself that this requires that the file is missing a trailing newline.)


Fix MeltanoQuery using Table.name instead of the Table's SQL name

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/785
Originally created by @iroussos on 2019-07-12 14:49:33

There are currently 2 bugs in the MeltanoQuery implementation:

The Table.name is used in the join portion of the base_join_query when HDA queries are built instead of the proper Table.sql_table_name.
That results in invalid queries when a Table's name does not match their sql_table_name.

The Table.name is used in add_schema_to_query() instead of the proper Table.sql_table_name.
That results in queries without a schema when a Table's name does not match their sql_table_name.

View 2 previous comments from the original issue on GitLab


Trouble to run the example execution - Error executing process > detect:pprmeta (1)

Dear,
When I try to run the example execution with -profile local,singularity I get the following error message:
ERROR:

ERROR ~ Error executing process > 'detect:pprmeta (1)'

Caused by:
  Process `detect:pprmeta (1)` terminated with an error exit status (255)

Command executed:

  [ -d "pprmeta" ] && cp pprmeta/* .
  ./PPR_Meta assembly_renamed_filt1500bp.fasta assembly_pprmeta.csv

Command exit status:
  255

Command output:
  (empty)

Command error:
  INFO:    Environment variable SINGULARITYENV_NXF_TASK_WORKDIR is set, but APPTAINERENV_NXF_TASK_WORKDIR is preferred
  Could not access the MATLAB Runtime component cache. Details: fl:filesystem:SystemError; component cache root:; componentname: PPR_Meta

Work dir:
  /scratch/lukak/virify/89/da5d86a7234aabd05dfd7b618633e0

I don't have many experience with singularity/apptainer so any kind of help would be much appreciated.
Best regards,
Luka

Hey @krluka
Apologies for a very delayed response.
That looks like a there are issues with permissions on the directory the task is being executed. Do you have write/read/execute permissions on /scratch/lukak/virify/89/da5d86a7234aabd05dfd7b618633e0? I'm not very familiar with the MATLAB runtime, and I have never bumped into this problem.
If you are running this on an HPC cluster, could you contact your support team? They may be able to provide some guidance.
Cheers

Hey @mberacochea
Thank you for your reply.
I checked with local support and it seems that necessary permissions are in place.
Best,
Luka

Hey @krluka
Can you share the whole .nextflow.log file for the run please?. I'm not sure what is going one, and that log file may have some clues.
Cheers

Hey @mberacochea
Sure, I'm attaching it to this post.
Best,
Luka
nextflow.log

Hey @krluka,
I had the same issue on HPC without admin rights, and I was able to fix it by setting up the MCR_CACHE_ROOT=</writable/dir> environment variable with writable directory.

@dbespiatykh Can you try @dbespiatykh suggestion?
Thanks @dbespiatykh I will add this to the documentation

Hey @dbespiatykh,
Thank you for the suggestion - I will try that the first chance I get.
@mberacochea I'll post the outcome as soon I have it.

Hi @egenomics
Did you try @dbespiatykh suggestion?
I had the same issue on HPC without admin rights, and I was able to fix it by setting up the MCR_CACHE_ROOT=</writable/dir> environment variable with writable directory.
Cheers

I am in a local machine (testing it). When I use your suggestion about setting upthe MCR_CACHE_ROOT I get a similar error:
ERROR ~ Error executing process > 'detect:pprmeta (1)'
Caused by:
Process detect:pprmeta (1) terminated with an error exit status (255)
Command executed:
[ -d "pprmeta" ] && cp pprmeta/* .
./PPR_Meta assembly_renamed_filt1500bp.fasta assembly_pprmeta.csv
Command exit status:
255
Command output:
(empty)
Command error:
Could not access the MATLAB Runtime component cache. Details: fl:filesystem:SystemError; component cache root:; componentname: PPR_Meta
Work dir:
/soft/test_viral./work/ae/9ed47b42f085011346e1ceff79c36e
Tip: when you have fixed the problem you can continue the execution adding the option -resume to the run command line
-- Check '.nextflow.log' file for details

Hey @egenomics,
Try doing this:

Inside the VIRify database directory, locate the /pprmeta directory, and rename file PPR_Meta to something like PPR_Meta_w

Create file named PPR_Meta and paste the following code in it:

export MCR_CACHE_ROOT=/your/writable/directory

./PPR_Meta_w "$@"

Run chmod +x PPR_Meta

And try running the pipeline again

Hi,
I did it and it works with the test!
thanks

Hey @egenomics,
Try doing this:
* 1. Inside the VIRify database directory, locate the `/pprmeta` directory, and rename file `PPR_Meta` to something like `PPR_Meta_w`

* 2. Create file named `PPR_Meta` and paste the following code in it:

export MCR_CACHE_ROOT=/your/writable/directory

./PPR_Meta_w "$@"

* 3. Run `chmod +x PPR_Meta`

And try running the pipeline again

Brilliant, and validated by @egenomics. I'll add this to the README.
Thank you @dbespiatykh

export MCR_CACHE_ROOT doesn't work on nfs shares. I had to set it on local filesystem.


Use junit5 extension

Draft PR to use the new junit5 extension.
Will update the version of the dependency to 0.1 once the extension has been released to maven central.

Closing in favour of  #178


Automated dependency update (2020-02-24 07:08:20)

Codecov Report

Merging #389 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #389   +/-   ##
======================================
  Coverage    99.3%   99.3%
======================================
  Files           8       8
  Lines         287     287
  Branches       54      54
======================================
  Hits          285     285
  Partials        2       2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8ea61a...29fdcee. Read the comment docs.


feature:

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
How do I solve the problem?

Describe the solution you'd like
.
Describe alternatives you've considered
.
Additional context
.

I believe you're missing a C compiler in your OS. This is not an issue with LazyVim, rather a configuration issue with the OS you use.
Also it'd really help a lot if you put a more elaborate effort from your side when creating issues. You can't expect those who will try to help you to make guesses about your problem. There's a reason the issue template comes with some sections that you should complete.

@07Rafael08,
Kindly close this issue


[gt4py] mysterious versions

The versions listed here
https://github.com/C2SM/spack-c2sm/blob/b7e55dbe3b33c471aaa67329c94395ac2b214ce8/repos/c2sm/packages/py-gt4py/package.py#L19-L21
are not released https://github.com/GridTools/gt4py/releases .
This looks like gt4py didn't release these versions to the public, but the package manager spack knows about them. That's odd, isn't it?
Also https://github.com/GridTools/gt4py knows these commits as icon4py_20230413, while spack refers to them as 1.1.2. Why the mismatch? Isn't this confusing?

@abishekg7 can you unconfuse me?

Basically, gt4py has not have any official releases since v1.0.1 and the gt4py team reserved the numbered tag names for official releases. What we had instead was these temporary tag names. But on the spack side we needed the numbered tag names to allow for easier version management, and hence what you see here.
All this said, we made a tiny error choosing these internal spack version numbers. It should have been v<IP_ADDRESS>, v<IP_ADDRESS> instead of 1.1.1 and 1.1.2.  @jonasjucker and I were just discussing about changing these version names (to v<IP_ADDRESS> etc) so that when gt4py actually has an 1.0.2 release it won't conflict with our naming.

v<IP_ADDRESS>, etc makes sense. You could also name them v20230413 to align with the tags if you like.
But still, why does the package manager knows about more versions than the package itself?
If you need more gt4py versions, ask the gt4py people for more versions. If they don't want to commit to them, they can set them as pre-release versions (they will be labeled as non-production ready).
It's not the responsibility of a package manager to fix a versioning problem, that's what version control is for ;-)

Fair. For now I'll do the version renaming in a spack PR. But I'll bring it up with the gt4py team re. how to handle these intermediate tags better.

The mysterious version are my bad.
Since gt4py-team did not like to do tags with meaningful semantics I had to do some versioning for spack-c2cm CI.

Wait until icon4py uses more stable gt4py versions.


Should only allow portrait mode

I saw the design only for portrait mode, this PR will prevent users from seeing broken UI due to phone rotation

If only allow portrait mode, the admin portal might not be scrollable

I have removed the orientation restrictions in admin portal, so far I tested myself the user side can prevent landscape mode, not sure about the admin side as I do not have an admin account 🥲

Here's the admin account if you want to test it:
Email<EMAIL_ADDRESS>Password: 87654321
I only provide the apk file in the repo, so there's no plan for iOS support for now.

I have self tested user side only allow portrait mode and admin side only allow landscape mode since portrait mode can cause rendering error when navigating to the first page in the admin portal. You try it on your side if there is no problem then I think can merge.
btw, after user logs out from admin portal and logs in back again cannot log in. I checkout your master branch oso got this problem sometimes pops up error message but most of the time error message just flashing cant see clearly. I think that is another issue need to solve separately.

Logging out from admin and log back in one I think is the UI problem, since the admin portal is from a template, therefore it's quite difficult to solve it. I open another issue #41 for that.


Which stride did the baseline choose?

Hi! I am puzzled about which stride was used in the baseline and gaze360 model's training. I have read the paper and the answer is 3. But the config in common shows that the default stride is 13.

And for anther ,  you have provided us with checkpoints including lam-best and gaze360-lam-best.  But it seems that gaze360-lam-best is the version that had been fine-tuned in lam task yet. Can I get a version of orginal gaze360 checkpoint which you use in training process? That is the version that haven't been fine-tuned yet.
Thank you a lot!

During training, we used a stride of 3, the default value was only used for debug.
You can find the pretrained checkpoint of gaze360 here.

Thanks a lot!