Doesn't work on OpenShift when using the restricted SCC

$helm install --name foo stable/ibm-mqadvanced-server-dev --set license=accept
$ helm status foo
LAST DEPLOYED: Tue Aug 21 16:17:24 2018
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Pod(related)
NAME          READY  STATUS            RESTARTS  AGE
foo-ibm-mq-0  0/1    CrashLoopBackOff  5         7m
Container keeps restarting and the status stays "CrashLoopBackOff". Below listed errors are what I see in the kubernetes pod logs
$ docker logs aa94173b74e7
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x4e8e46]
goroutine 1 [running]:
github.com/ibm-messaging/mq-container/internal/logger.(*Logger).Debugf(0x0, 0x58be27, 0x1f, 0xc420055e30, 0x1, 0x1)
/go/src/github.com/ibm-messaging/mq-container/internal/logger/logger.go:127 +0x26
main.logTermination(0xc4200103a0, 0x1, 0x1)
/go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:100 +0x16e
main.doMain(0xc4200781e0, 0xc420055f78)
/go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:111 +0xae
main.main()
/go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:163 +0x26

That's a fairly catastrophic failure, and there's not much info to go on in that log (as it's failing to even write a debug log entry).  Can you please provide some more details about the Kubernetes environment you're installing into (including things like which PodSecurityPolicy is the default).  Also the results of kubectl describe pod foo-ibm-mq-0 and kubectl get -o yaml statefulset foo-ibm-mq would be useful.

Thanks for looking into this @arthurbarr
I'm installing this to the openshift container platform. I'm installing the IBM chart unaltered.
Below is the pod and sfs description. Let me know if you need anything else.
kubectl describe pod foo-ibm-mq-0
Name:           foo-ibm-mq-0
Namespace:      default
Node:           m1.oc.local/<IP_ADDRESS>
Start Time:     Wed, 22 Aug 2018 11:25:40 -0400
Labels:         app=ibm-mq
chart=ibm-mqadvanced-server-dev
controller-revision-hash=foo-ibm-mq-569f8cf899
heritage=Tiller
release=foo
statefulset.kubernetes.io/pod-name=foo-ibm-mq-0
Annotations:    openshift.io/scc=restricted
productID=98102d16795c4263ad9ca075190a2d4d
productName=IBM MQ Advanced for Developers
productVersion=<IP_ADDRESS>
Status:         Running
Controlled By:  StatefulSet/foo-ibm-mq
Containers:
qmgr:
Container ID:   docker://d417f10989823d13a62765c03e4c147bf39b8c375b15f25389626a1ac3ed1e35
Image:          ibmcom/mq:<IP_ADDRESS>
Image ID:       docker-pullable://docker.io/ibmcom/mq@sha256:144f087d9b6162037d7eae69fb0ecc38598dfa865673a1927ac39c05b7465bfd
Ports:          1414/TCP, 9443/TCP, 9157/TCP
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    2
Started:      Wed, 22 Aug 2018 11:26:29 -0400
Finished:     Wed, 22 Aug 2018 11:26:29 -0400
Ready:          False
Restart Count:  3
Limits:
cpu:     500m
memory:  512Mi
Requests:
cpu:      500m
memory:   512Mi
Liveness:   exec [chkmqhealthy] delay=60s timeout=5s period=10s #success=1 #failure=1
Readiness:  exec [chkmqready] delay=10s timeout=3s period=5s #success=1 #failure=1
Environment:
LICENSE:            accept
MQ_QMGR_NAME:       foo
LOG_FORMAT:         basic
MQ_ENABLE_METRICS:  true
MQ_ADMIN_PASSWORD:  <set to the key 'adminPassword' in secret 'foo-ibm-mq'>  Optional: false
Mounts:
/mnt/mqm from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-dcws5 (ro)
Conditions:
Type           Status
Initialized    True
Ready          False
PodScheduled   True
Volumes:
data:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  data-foo-ibm-mq-0
ReadOnly:   false
default-token-dcws5:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-dcws5
Optional:    false
QoS Class:       Guaranteed
Node-Selectors:
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
Type     Reason                 Age               From                  Message

Normal   Scheduled              1m                default-scheduler     Successfully assigned foo-ibm-mq-0 to m1.oc.local
Normal   SuccessfulMountVolume  1m                kubelet, m1.oc.local  MountVolume.SetUp succeeded for volume "default-token-dcws5"
Normal   SuccessfulMountVolume  1m                kubelet, m1.oc.local  MountVolume.SetUp succeeded for volume "pvc-381bf927-a57f-11e8-b65f-080027ce0b4f"
Normal   Pulled                 17s (x4 over 1m)  kubelet, m1.oc.local  Container image "ibmcom/mq:<IP_ADDRESS>" already present on machine
Normal   Created                17s (x4 over 1m)  kubelet, m1.oc.local  Created container
Normal   Started                17s (x4 over 1m)  kubelet, m1.oc.local  Started container
Warning  BackOff                9s (x8 over 1m)   kubelet, m1.oc.local  Back-off restarting failed container
kubectl get -o yaml statefulset foo-ibm-mq
apiVersion: apps/v1
kind: StatefulSet
metadata:
creationTimestamp: 2018-08-22T15:25:39Z
generation: 1
labels:
app: ibm-mq
chart: ibm-mqadvanced-server-dev
heritage: Tiller
release: foo
name: foo-ibm-mq
namespace: default
resourceVersion: "40913"
selfLink: /apis/apps/v1/namespaces/default/statefulsets/foo-ibm-mq
uid: a05cdf29-a61f-11e8-b65f-080027ce0b4f
spec:
podManagementPolicy: OrderedReady
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app: ibm-mq
chart: ibm-mqadvanced-server-dev
heritage: Tiller
release: foo
serviceName: qm
template:
metadata:
annotations:
productID: 98102d16795c4263ad9ca075190a2d4d
productName: IBM MQ Advanced for Developers
productVersion: <IP_ADDRESS>
creationTimestamp: null
labels:
app: ibm-mq
chart: ibm-mqadvanced-server-dev
heritage: Tiller
release: foo
spec:
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
matchExpressions:
- key: beta.kubernetes.io/arch
operator: In
values:
- amd64
weight: 2
- preference:
matchExpressions:
- key: beta.kubernetes.io/arch
operator: In
values:
- ppc64le
weight: 2
- preference:
matchExpressions:
- key: beta.kubernetes.io/arch
operator: In
values:
- s390x
weight: 2
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: beta.kubernetes.io/arch
operator: In
values:
- amd64
- ppc64le
- s390x
containers:
- env:
- name: LICENSE
value: accept
- name: MQ_QMGR_NAME
value: foo
- name: LOG_FORMAT
value: basic
- name: MQ_ENABLE_METRICS
value: "true"
- name: MQ_ADMIN_PASSWORD
valueFrom:
secretKeyRef:
key: adminPassword
name: foo-ibm-mq
image: ibmcom/mq:<IP_ADDRESS>
imagePullPolicy: IfNotPresent
livenessProbe:
exec:
command:
- chkmqhealthy
failureThreshold: 1
initialDelaySeconds: 60
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5
name: qmgr
ports:
- containerPort: 1414
protocol: TCP
- containerPort: 9443
protocol: TCP
- containerPort: 9157
protocol: TCP
readinessProbe:
exec:
command:
- chkmqready
failureThreshold: 1
initialDelaySeconds: 10
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
resources:
limits:
cpu: 500m
memory: 512Mi
requests:
cpu: 500m
memory: 512Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /mnt/mqm
name: data
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
updateStrategy:
rollingUpdate:
partition: 0
type: RollingUpdate
volumeClaimTemplates:

metadata:
creationTimestamp: null
labels:
app: ibm-mq
chart: ibm-mqadvanced-server-dev
heritage: Tiller
release: foo
name: data
spec:
accessModes:

ReadWriteOnce
resources:
requests:
storage: 2Gi
status:
phase: Pending
status:
collisionCount: 0
currentReplicas: 1
currentRevision: foo-ibm-mq-569f8cf899
observedGeneration: 1
replicas: 1
updateRevision: foo-ibm-mq-569f8cf899

Thanks for the info.  I can see you're using the default OpenShift restricted SCC (openshift.io/scc=restricted).  I'm afraid that the MQ image doesn't currently work with that SCC.  We are planning some changes which should improve the situation, but for now, the easiest thing to do is to use the privileged SCC.

Same issue here, we are really looking forward to the improvements!

we are also looking for this feature. @arthurbarr when can we expect this?

Hi,
I tried the Non-Root Pull-Request #276 on the Openshift and I get this errors:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x50a546]

goroutine 1 [running]:
github.com/ibm-messaging/mq-container/internal/logger.(*Logger).Debugf(0x0, 0x87a609, 0x1f, 0xc420085df8, 0x1, 0x1)
	/go/src/github.com/ibm-messaging/mq-container/internal/logger/logger.go:127 +0x26
main.logTermination(0xc4201ce070, 0x1, 0x1)
	/go/src/github.com/ibm-messaging/mq-container/cmd/runmqserver/logging.go:45 +0x16e
main.doMain(0x0, 0x0)
	/go/src/github.com/ibm-messaging/mq-container/cmd/runmqserver/main.go:40 +0x178
main.main()
	/go/src/github.com/ibm-messaging/mq-container/cmd/runmqserver/main.go:190 +0x22

  | panic: runtime error: invalid memory address or nil pointer dereference
-- | --
  | [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x4e8e46]
  |
  | goroutine 1 [running]:
  | github.com/ibm-messaging/mq-container/internal/logger.(*Logger).Debugf(0x0, 0x58be53, 0x1f, 0xc42006fe20, 0x1, 0x1)
  | /go/src/github.com/ibm-messaging/mq-container/internal/logger/logger.go:127 +0x26
  | main.logTermination(0xc4200103b0, 0x1, 0x1)
  | /go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:103 +0x16e
  | main.doMain(0x5241ea, 0xc42009e210)
  | /go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:114 +0xae
  | main.main()
  | /go/src/github.com/ibm-messaging/mq-container/cmd/runmqdevserver/main.go:166 +0x26

Is there a timeframe that can be communicated for a fix? I am also running into this issue.

This is not a bug, but a current limitation.  We are working on improvements.  The master branch now runs under a non-root user.  The image doesn't work under the default Red Hat SELinux container policy.  You can change the SELinux type to spc_t, but that is not allowed under the restricted SCC.  MQ's current support statement for SELinux is here

MQ 9.2.0 includes a new "no install" version:

Delivered as a simple tar.gz file:
There's no longer an mqm user, and the queue manager will run with whichever ID starts it.
The use of setuid bits has been removed.

This all means that MQ can now run under the restricted SCC.


Camera redirection

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I am trying to redirect video camera output from windows 10 to the Camera Capture module - is this supported, if yes, whats the procedure

Any log messages given by the failure

cv2.error: OpenCV(4.0.0) /io/opencv/modules/imgproc/src/resize.cpp:3784: error: (-215:Assertion failed) !ssize.empty() in function 'resize'
Expected/desired behavior

OS and Version?

Windows 10

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Per my other comment, USB pass-through is on Docker for Windows's backlog but is currently not supported. Alternative is to stream a video feed to your docker VM via a port binding.


Does it have PDF toolbar?

I installed this module but it is only showing one page of the PDF.
and the there is no toolbar on top of the pdf and scrolling does not work.
any help is appreciated

No, there is no toolbar, that is left for the implementor. You can change page by passing it via props. You can check the example implementation from the example directory.

Any suggestions on the toolbar implementations?

@dziamid, check sample/test pages that are included in react-pdf as of 1.6.0 :)


[Question] Carbon all theme not working in Sveltekit production

Hi, i have done theme switcher prior the 0.40 update. It is working in dev, however in production the theme are not working. After 0.40 update, i make use of the Theme component and the result are the same which works in dev but not in production. What should i do to make it working?
Here is my svelte.config.js
/** @type {import('@sveltejs/kit').Config} */
import { optimizeImports, optimizeCss } from "carbon-preprocess-svelte";
import adapter from '@sveltejs/adapter-static';

const config = {
	kit: {
		// hydrate the <div id="svelte"> element in src/app.html
		adapter: adapter({
			// default options are shown
			pages: 'build',
			assets: 'build',
			fallback: null
		}),
		target: '#svelte',
		vite: {
			plugins: [
				process.env.NODE_ENV === "production" && optimizeCss(),
			],
		  },
	},
	preprocess: [optimizeImports()],

};

export default config;

Which StyleSheet are you using?
The Theme component uses CSS variables, so it will only work with carbon-components-svelte/css/all.css.

Which StyleSheet are you using?
The Theme component uses CSS variables, so it will only work with carbon-components-svelte/css/all.css.

i'm using
  @import "carbon-components-svelte/css/all";

with style lang="scss";
i have tried using normal style without the lang option and the result are the same

My next guess would be that the optimizeCss strips away CSS needed for dynamic theming. What happens if you remove that plugin when building for production?

i have tried that too with no luck as well. It's ok, i will try again with new sveltekit project later. I think it is because of the production css too as the html theme props are changing as i change the theme in the inspect tool.
Thanks for your help

Having same issue.

I am struggling with this issue too.
Did anyone figure out how to allow dynamic theming with svelteKit production builds?

@DavidM42 Could you provide a minimal repo? Happy to take a further look

Thanks for your super quick answer :heart:. Went immediately to work creating a minimal repo but there it worked just fine :eyes: .
So false alarm. In the end, I found the error in my repo. I forgot another import of the theme file white.css in my error page which collided with my all.css import but only on production builds not on dev previews.
Lesson learned, minimum viable project makes sense to debug sometimes.
For others stumbling upon this issue:
Check in your editor if you find multiple matches for the search
import 'carbon-components-svelte/css/

and then make sure to only import either the theme you want or all.css


linux/amd64 image not building correctly

While the github workflow definitely seems to be set up to build one, the two architectures built for the docker images are linux/arm64 and unknown/unknown.

After doing some reading, this seems to be a known issue with build-push-action@v5 as discussed here: https://github.com/docker/build-push-action/issues/820
The fix seems as simple as just disabling provenance attestations for the docker build.

@timetinytim Thanks for the fix, I’ve just pushed  v0.3.5 which includes it: https://github.com/damomurf/coredns-tailscale/releases/tag/v0.3.5.


Static method or example to change asset link domains

Motivation
Dedicated support for custom asset domains has long been missing from this SDK.
Proposed solution
Without dedicated support customers lack guidance on best practice solutions for implementing a substitution themselves. If we had a code sample or even a static method that they could make use of it would be a big help. Not just for the custom domain use case but secure access as well, as a user has expressed interest in replacing the URL with their own endpoint, with a file handler, to make calls to our API with the needed keys.
Example:
Bet way to turn
"https://assets-us-01.kc-usercontent.com/778b7b68-e044-0006-e0eb-333eb9503651/45be1c3f-a3b9-428d-bbc6-cb3ea381405e/istockphoto-518322790-1024x1024.jpg" => "https://myassetdomain/778b7b68-e044-0006-e0eb-333eb9503651/45be1c3f-a3b9-428d-bbc6-cb3ea381405e/istockphoto-518322790-1024x1024.jpg"
Additional context
Issue (https://github.com/kontent-ai/delivery-sdk-net/issues/381)
Issue (https://github.com/kontent-ai/delivery-sdk-net/issues/311)

Related: #193

PR out there now: https://github.com/kontent-ai/delivery-sdk-net/pull/398


changed path separator "/" to OS-specific path separator

I setup the project on my windows machine and ran into this.
I tried to be as minimal invasiv as possible.

Don't pull in commits ad6d578 and 90645e5 those shouldn't be included in the pull request. I pushed them afterwards to my master. They only include file reformating and a windows script.

Would you mind making a new pull request that does not contain those commits?


Lineage missing in purview

We have many cases where lineage is missing in purview. We will keep this issue and update logs to investigate.
23/04/05 08:27:02 ERROR EventEmitter: Could not emit lineage w/ exception java.net.SocketTimeoutException: Read timed out 	at java.net.SocketInputStream.socketRead0(Native Method) 	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) 	at java.net.SocketInputStream.read(SocketInputStream.java:171) 	at java.net.SocketInputStream.read(SocketInputStream.java:141) 	at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:476) 	at sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:470) 	at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70) 	at sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1369) 	at sun.security.ssl.SSLSocketImpl.access$300(SSLSocketImpl.java:73) 	at sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:978) 	at io.openlineage.spark.shaded.org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) 	at io.openlineage.spark.shaded.org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) 	at io.openlineage.spark.shaded.org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:280) 	at io.openlineage.spark.shaded.org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138) 	at io.openlineage.spark.shaded.org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) 	at io.openlineage.spark.shaded.org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.jav [log4j-active (7).txt](https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator/files/11166751/log4j-active.7.txt)
log4j-active (8).txt
Attached two logs from databricks with errors. Please do investigate

log4j-active (7).txt

Hi @Kishor-Radhakrishnan, was this also fixed by the changes you made to fix #193, or do you still need us to look into it?

@hmoazam  Yes, As this error is different and we are seeing it frequent in DBR 10.4 LTS
23/04/05 08:27:02 ERROR EventEmitter: Could not emit lineage w/ exception java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at

Hi Kishor, could you please share what data sources you're reading from and writing to when you're getting this error? As well as the DBR you're currently using?

@Kishor-Radhakrishnan would you please try this updated branch to help us collect more information on this issue?
https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator/tree/hotfix/maxQueryPlanOLIn
If you could build and install this version and then run a notebook that is failing to send lineage even after our last fix.
If you could please monitor the logs in the OpenLineageIn function, we should see:

The OpenLineage payload being sent to Event Hubs
The error message of the event being too large.

If you could provide us that full open lineage payload and the error message, we can troubleshoot further and find a fix for this issue.

@wjohnson  attaching log having this error from monitor
openlineage.txt.zip

@Kishor-Radhakrishnan thank you so much for this!  Would you be able to share any snippet of code on how you're reading the /mnt/lob_shippingcycle/active/gcss/value_added_service_booking/ path?
In this case, it appears to not recognize the partitions of the date_part column and results in a large number of inputs and a large number of metadata for column lineage.
I think there are two approaches to solving this.

(Long Term) Understanding why OpenLineage isn't recognizing the date_part partitions as a single input table.
(Short Term) Adding a feature to the Databricks to Purview Solution Accelerator that limits the size of the column lineage metadata.

We could add an app setting named maxColumnLineageSize that would behave similarly to maxQueryPlanSize.

also we face this issue for many different notebooks may be . we need to see why partition is not identified properly.
May we can try short term solution of column lineage skip to see if it capture whole dataset level lineage.

We are adding the column lineage removal as part of the next release.


fix(vars): added css-vars as js to core-components-vars package

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.486%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7391

Relevant Lines:
8365

💛  - Coveralls


[PDI-18423] CSV File input Step does not handle multicharacter field …

…delimters correctly when spanning an NIO block boundary.

:white_check_mark: Build finished in 17m 18s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3617, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 17m 17s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3617, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Add language-nlf to deprecated packages

All features of language-nlf have been merged into language-nsis. The former will no longer be updated.

Hey @idleberg! Thanks for your patience. We're going to go ahead and merge this for now. We're haven't done any investigation to see if there's some sort of build process that has to happen after this. If you wouldn't mind keeping an eye on this and pinging me if the right thing doesn't happen, I would appreciate it!
Thanks again!


Feat 852 multiplanepower

closes #852

We should consider adding a final power field, which would require that someone (and this can likely be automated) use the calibration field along with the power and power ratio to calculate what the power at the plane was...


Development: Update cypress to 12.13.0

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Update cypress to the latest version 12.13.0:
https://docs.cypress.io/guides/references/changelog#12-13-0
Description

Update cypress to the latest version
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Codecov Report

Merging #6656 (e532417) into develop (9fdfbf0) will increase coverage by 4.26%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6656      +/-   ##
=============================================
+ Coverage      76.14%   80.41%   +4.26%
- Complexity         0    13587   +13587
=============================================
  Files           1277     2399    +1122
  Lines          47944    91710   +43766
  Branches        8373    12877    +4504
=============================================
+ Hits           36507    73748   +37241
- Misses          5807     9867    +4060
- Partials        5630     8095    +2465

see 1124 files with indirect coverage changes

Flag
Coverage Δ

client
76.14% <ø> (+<0.01%)
:arrow_up:

server
85.08% <ø> (?)

Continue to review full report in Codecov by Sentry.

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


Upstream Active Connection metric increase after v1.20.0 upgrade

Title: Upstream Active Connection metric increase after upgrade
Description:

We upgraded Envoy from v1.17 to v1.20 for our system. We use Envoy in 2 manner: 1/ As regular Envoy Proxy(the ingress fleet) 2/ As a reverse service proxy for services that talks to the Envoy in #1. After the upgrade to v1.20, we are seeing an increase in upstream_cx_active metric but the upstream_cx_total metric looks as expected(refer the snapshot).
On further debugging, we noticed recurring spike in upstream_cx_destroy and upstream_cx_destroy_local metrics but nothing in envoy_cluster_upstream_rq_timeout or envoy_cluster_upstream_cx_idle_timeout

(Follow the red line go up after 10/20)

I am trying to make sense of why the active upstream connection count has gone up after the upgrade ?
1/ We did not change any other config around connection pool and timeout.
2/ I checked the Connection Manager code changes since v1.17 and couldn't find a relevant change.
3/ I have gone through the release notes, looking for any breaking change, minor behavior change for 1.17, 1.18 and 1.20, and did not find anything specific to this.
Happy to add more logs/metrics.

I think this is due to REUSE_PORT now being the default. I could see this leading to more active connections with more concurrent workers receiving even connections.

Understood. I was confused because the /config_dump API did not return the lb_policy.
Is there another way to verify the Load Balancing in-use?
curl localhost:8081/config_dump | grep -w -A10 clusters
     "clusters": [
      {
       "name": "envoy-to-remote",
       "type": "STRICT_DNS",
       "connect_timeout": "0.200s",
       "health_checks": [


New Rule (Attachment): Fake attachment image lure

Uses beta.parse_eml, so can't merge until that's live.

Also added "EML analysis" as a detection method (because of parse_eml.)
Thoughts?

@aidenmitchell  blast from the past.
We could add an additional or     any(attachments,         .file_type in $file_types_images         and any(ml.logo_detect(.).brands, .name =="FakeAttachment"))     )


Import 'package:esc_pos_utils/esc_pos_utils.dart' to make it work

I added this issue on the wrong package sorry


random patch #1

Random Package for Issue #11
Folder Structure

Created a folder named "Random" to organize code related to random number generation.

Files
Random.cpp

Implementation file for random number generation functions.
Contains functions for generating random float, int, and long values.
Includes initialization function coda_setup for seeding the random number generator.

Random.coda

Coda definition file that defines the "Random" package and scope.
Defines functions for generating random numbers of major types: float, int, and long.
Provides a structured interface for using random number generation functionality.

I would like to merge the branch into dev i.e. SujalChoudhari:dev.
Its as per CONTRIBUTING guide.
Also I noticed the branch name is not up to the conventions.

Creating a new PR with new branch name up to the conventions.
this as branch name feature/ys-random


File mode for download tasks needs to be in octal

For the file-related tasks in the download role, the mode should be an octal (or needs to be quoted), otherwise the permissions will not be set properly.
https://github.com/rancher/k3s-ansible/blob/master/roles/download/tasks/main.yml#L8-L15
These should be like:
mode: 0755

From Ansible's docs on get_url:

You must either add a leading zero so that Ansible's YAML parser knows it is an octal number (like 0644 or 01777) or quote it (like '644' or '1777') so Ansible receives a string and can do its own conversion from string into number.

It seems this is already correct in the k3s role file-related tasks, so let's get these download tasks in the same format.

Also, credit to /u/Sukrim over on Reddit for finding this!


pytest fixes

Working on cleaning up test suite.  Example datasets need to be cleaned up a little bit.
The source seems to be mismatch of data types between the variable and the missing_value attribute.    Doing some tracing finds:
pytest -Werror -vv --pdb

(Pdb) tvar[:]
*** UserWarning: WARNING: missing_value not used since it
cannot be safely cast to variable data type
(Pdb) p axv.t
<class 'netCDF4._netCDF4.Variable'>
int32 time(profile)
    long_name: Profile Time
    standard_name: time
    calendar: standard
    units: seconds since 1970-01-01T00:00:00Z
    axis: T
    ioos_category: Time
    time_origin: 01-JAN-1970 00:00:00
    _CoordinateAxisType: Time
    missing_value: -9999.9
unlimited dimensions:
current shape = (35,)
filling on, default _FillValue of -2147483647 used

One of a few source files:  src/pocean-core/pocean/tests/dsg/profile/resources/om-1dy11.nc
@ocefpaf Were the sample data file hand created or script generated?
Having the missing_value data type match the variable data type is a check performed by the IOOS Compliance Checker.  We will consider looking into this package when reviewing examples for the IOOS Compliance Checker during the code sprint and maybe also look into CF and other issues as well.  https://github.com/ioos/ioos-code-sprint/issues/40

@ocefpaf Were the sample data file hand created or script generated?

Sorry but I have no idea. Those were added long before I got here 😬


Heroku Error

Deployed just fine but when tried to visit the server, it crashed.

Could you try restarting the app and send me the logs, because these logs seem incomplete, the app (main.py) hasn't even started, the errors are coming from Gunicorn which is what serves the app
To restart click More near the top right of the Heroku dashboard and select Restart all dynos

Here are the logs which also contains the point of error in it.
logs.txt

After reviewing the logs, this was the point of error
2021-02-06T19:38:05.377298+00:00 app[web.1]: File "/app/main.py", line 37, in <module>
2021-02-06T19:38:05.377299+00:00 app[web.1]: metadata = src.metadata.writeMetadata(
2021-02-06T19:38:05.377299+00:00 app[web.1]: File "/app/src/metadata.py", line 172, in writeMetadata
2021-02-06T19:38:05.377299+00:00 app[web.1]: "tmdbId"] = item["name"][:-len(item["fullFileExtention"])], "", "", "1900-01-01", ""
2021-02-06T19:38:05.377300+00:00 app[web.1]: KeyError: 'fullFileExtention'

I believe I fixed the issue. You need to manually update your local repository, or if on Heroku redeploy
https://github.com/libDrive/backend/commit/889ca8ea0c2f1a3d672b3210cfcb14ba85fcd8f5

After reviewing the logs, this was the point of error
2021-02-06T19:38:05.377298+00:00 app[web.1]: File "/app/main.py", line 37, in <module>
2021-02-06T19:38:05.377299+00:00 app[web.1]: metadata = src.metadata.writeMetadata(
2021-02-06T19:38:05.377299+00:00 app[web.1]: File "/app/src/metadata.py", line 172, in writeMetadata
2021-02-06T19:38:05.377299+00:00 app[web.1]: "tmdbId"] = item["name"][:-len(item["fullFileExtention"])], "", "", "1900-01-01", ""
2021-02-06T19:38:05.377300+00:00 app[web.1]: KeyError: 'fullFileExtention'

I believe I fixed the issue. You need to manually redeploy the Heroku repository
libDrive/backend@889ca8e

sastaflix-logs-1612725514011.txt
hey I'm facing this issue. Deployed using button.

sastaflix-logs-1612725514011.txt
hey I'm facing this issue. Deployed using button.

You either don't have a TMDB API key or have an incorrect TMDB API key in your config.
Your issue is unrelated the to this topic's issue. If you have more questions, please start a new issue.
Further replies on this issue will not be answered.

The issue still exist.
I redeployed

The issue still exist.
I redeployed

Can you send the new logs please.

@aditya-shri
I was able to reproduce your error and believe I have fixed it. Please try redeploying the latest update. Thank you for your pateince.
https://github.com/libDrive/backend/commit/e26bf9c4058f1941f78396dee11821355e5dda69

Now a new error is happening after login.
logs.txt
I'm using apiv3 of tmdb

Deployed just fine but when tried to visit the server, it crashed.

Same error :(
"2021-02-10T18:50:37.548981+00:00 app[web.1]:   File "/app/.heroku/python/lib/python3.9/configparser.py", line 1254, in getitem
2021-02-10T18:50:37.548981+00:00 app[web.1]:     raise KeyError(key)
2021-02-10T18:50:37.548981+00:00 app[web.1]: KeyError: 'cloudflare'
2021-02-10T18:50:37.549145+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [7] [INFO] Worker exiting (pid: 7)
2021-02-10T18:50:37.715928+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Shutting down: Master
2021-02-10T18:50:37.716038+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Reason: Worker failed to boot.
2021-02-10T18:50:37.785035+00:00 heroku[web.1]: Process exited with status 3
2021-02-10T18:50:37.869776+00:00 heroku[web.1]: State changed from up to crashed
2021-02-10T18:50:45.173709+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=testsa23423.herokuapp.com request_id=e35b36c1-b34c-4856-9c4a-3fe1338732c8 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-02-10T18:50:46.131597+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=testsa23.herokuapp.com request_id=94d36057-2368-4c56-aea0-917262f9eeaa fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https"

Deployed just fine but when tried to visit the server, it crashed.

Same error :(
"2021-02-10T18:50:37.548981+00:00 app[web.1]:   File "/app/.heroku/python/lib/python3.9/configparser.py", line 1254, in getitem
2021-02-10T18:50:37.548981+00:00 app[web.1]:     raise KeyError(key)
2021-02-10T18:50:37.548981+00:00 app[web.1]: KeyError: 'cloudflare'
2021-02-10T18:50:37.549145+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [7] [INFO] Worker exiting (pid: 7)
2021-02-10T18:50:37.715928+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Shutting down: Master
2021-02-10T18:50:37.716038+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Reason: Worker failed to boot.
2021-02-10T18:50:37.785035+00:00 heroku[web.1]: Process exited with status 3
2021-02-10T18:50:37.869776+00:00 heroku[web.1]: State changed from up to crashed
2021-02-10T18:50:45.173709+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=testsa23423.herokuapp.com request_id=e35b36c1-b34c-4856-9c4a-3fe1338732c8 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-02-10T18:50:46.131597+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=testsa23.herokuapp.com request_id=94d36057-2368-4c56-aea0-917262f9eeaa fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https"

This is a completely different issue
It's happening because I'm currently testing something. If you want to fix it, just add this line to the end of your LIBDRIVE_CONFIG:
cloudflare= just leave it empty

Deployed just fine but when tried to visit the server, it crashed.

Same error :(
"2021-02-10T18:50:37.548981+00:00 app[web.1]:   File "/app/.heroku/python/lib/python3.9/configparser.py", line 1254, in getitem
2021-02-10T18:50:37.548981+00:00 app[web.1]:     raise KeyError(key)
2021-02-10T18:50:37.548981+00:00 app[web.1]: KeyError: 'cloudflare'
2021-02-10T18:50:37.549145+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [7] [INFO] Worker exiting (pid: 7)
2021-02-10T18:50:37.715928+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Shutting down: Master
2021-02-10T18:50:37.716038+00:00 app[web.1]: [2021-02-10 18:50:37 +0000] [4] [INFO] Reason: Worker failed to boot.
2021-02-10T18:50:37.785035+00:00 heroku[web.1]: Process exited with status 3
2021-02-10T18:50:37.869776+00:00 heroku[web.1]: State changed from up to crashed
2021-02-10T18:50:45.173709+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=testsa23423.herokuapp.com request_id=e35b36c1-b34c-4856-9c4a-3fe1338732c8 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-02-10T18:50:46.131597+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=testsa23.herokuapp.com request_id=94d36057-2368-4c56-aea0-917262f9eeaa fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https"

This is a completely different issue
It's happening because I'm currently testing something. If you want to fix it, just add this line to the end of your LIBDRIVE_CONFIG:
cloudflare= just leave it empty

log.txt
It looks like it's almost there.

Now a new error is happening after login.
logs.txt

Is this fixed?

@aditya-shri @ronioncloud could you try redeploying with the newest updates
also, make sure you update your LIBDRIVE_CONFIG, the format has changed.

@aditya-shri @ronioncloud could you try redeploying with the newest updates
also, make sure you update your LIBDRIVE_CONFIG, the format has changed.

@eliasbenb Its giving timeout error


Unit testing added for math magician react project.

In this project :-

I tried to write unit tests for the Math Magicians app, using the Jest and React Testing Library librar ies.

Thank you for reviewing my project!!!!.

Hello @juaryimami, since this is a group project, as requested in the project requirements:

We can't proceed with the review 😉. Please make sure to contact your partner and finish the project on the same repository 😄.

STATUS: INVALID REQUEST
Hi @juaryimami 👋,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project that needs to be done in pair programming.
Your Code Review Request will be marked invalid in your Dashboard, so please submit a new one once ready 🙏.
Invalid requests don't count as a review, so don't worry about that 😄!
Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @Gopxfs in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Merge prTesting_201903060914 branch to master branch

OPS Build status updates of commit 485c837:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


This page needs pricing information

I need to make a decision between the options shown here, and I can't make that decision without pricing information.

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

ID: e34a359d-9ba2-a8e3-8391-8dfa780a5c47
Version Independent ID: f8b7a25e-c8ea-c435-7a96-45cdcfd2e60e
Content: Compare Azure Content Delivery Network (CDN) product features
Content Source: articles/cdn/cdn-features.md
Service: azure-cdn
GitHub Login: @duongau
Microsoft Alias: duau

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

Hello @natewaddoups, all pricing information for Azure CDN can be found here: https://azure.microsoft.com/en-us/pricing/details/cdn/. We don't put our pricing information in the documentation section because it is different depending on the zone used. For more information about billing, please see: https://docs.microsoft.com/en-us/azure/cdn/cdn-billing.
Thank you! #please-close


:lock: Bump http-cache-semantics from 4.1.0 to 4.1.1

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Memory issues with TMTV mode

I posted this video before https://watch.screencastify.com/v/poYbBEarUdmzvUhty0J3  which shows what is happening but since it didn't seem to happen on each machine we tested I've done some deeper digging.
We made a google doc to log our tests and I'm hoping the error in the console might point you in the right direction.  of the 4 computers we tested on 2 had the error and 2 did not.  Interestingly the two that had it do not have GPU and the two that did not do.  All had 16 GB RAM.
https://docs.google.com/document/d/1hVltQfBsK9cK-jvB4aBjeAvHIkxF3uDl1Ij8cKk-mIo/edit?usp=sharing

this is a great documented step by step report. Thanks for taking time in filling it.
For each setup can you put a screenshot of the following page? https://webglreport.com/?v=2

Posting some more information here about this bug after using the chrome task manager.  It appears that the memory that is causing the crash is from GPU Process. (This is on my laptop with integrated graphics)
Some advice from the web suggests that if you turn off "use hardware acceleration when available " in chrome the problem will go away and that seems to be correct.
This is a screenshot loading WITH hardware acceleration enabled

and here is one without

Here is the webglreport

Additionally, you asked for the memory dumps/screenshots before and after opening a study.  Here they are along with screen shots (this is with hardware acceleration off.
Before loading:

After loading in viewer

Back at the study list

The memory snapshots can be found here
https://fileshare.uhn.ca/download/82413d55-c71a-4b2c-b6fe-984a558ada84
Please note that this file upload will expire in 30 days.

https://github.com/OHIF/Viewers/issues/3207


Button missing on Remember The Milk (RTM)

Environment details

Operation system: Windows 10 Pro
Extension version: Version (1.1.2)

Expected behavior
Button should show up on all RTM lists.
Actual behavior
Button does not show up.
Steps to reproduce the behavior

Log into Remember the Milk (https://rememberthemilk.com)

Additional details

This started on Thursday, March 3 for me.
I have tried with only Toggl extension running, same problem.
I have not tried on a fresh profile.

RTM is also enabled in the extension settings. Have tried disabling/reenabling there as well.

Yo - thanks for the detailed report, but issue #770 addressed this.
Fix has been merged to master and will go out with the next deploy of the extension (~few days?)
If you're willing to mess around a bit to get it sooner than that, you can git clone this repository, enable Developer mode in chrome://extensions, click 'Load unpacked extension', and point that bad boy at the src/ directory inside of the git clone.
Or wait some time. We'll deploy soon, promise :)

Ah, thanks! I searched for open issues, not closed ones. Sweet, I'll do that, cause I can't be without my Toggl for very long. <3 Keep up the great work.


Feature/add suport for stream encryption/file encryption

Sodium provides a Stream encryption/file encryption. This exposes these functions in libsodium-sys and sodiumoxide.
https://download.libsodium.org/doc/secret-key_cryptography/secretstream.html

Please see #203

hi @dkulic
Sorry for the delay. Can you resolve the conflicts from the latest upstream changes? We can review this after that.

I will create another PR to be cleaner.


MINOR: Close ZKDatabase

Using the EmbeddedKafkaBroker on Windows fills up the temp folder because the ZKDatabase is never closed and therefore the data directory can not be deleted (Windows can't delete files where an open file handle exists).

I pushed an additional commit removing a redundant call and moving the db close to after the server is completely down. @rajinisivaram can you please review my change?

retest this please


Bundle option should rewrite require calls

When importing any module that calls require, I get Error: Cannot find module, due to the module being a dependency of the submodule. it should rewrite the value to be relative to the module in question, i.e. node_modules/<MODULE>/node_modules/<SUBMODULE>.
Alternatively, it should just completely skip non-relative paths, which would probably be the easiest way.

The bundling functionality is geared toward my atypical workflow and setup, so it probably needs a good rework.  (I think the translator just skips require calls in any case.)  It would probably be best to focus on non-bundling workflows first though, and approach this later.

New bundling format is much more like browserify.


Question about EventMesh Topic format

Hi Dear,
I play around with EventMesh project and also studying the EventMesh codes. I see the RMQ Topic created through EventMesh, the topic name needs to be certain format. For example, "FT0-e-80010000-01-1"
From the code, this method check weather the topic is valid:
https://github.com/apache/incubator-eventmesh/blob/develop/eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/util/EventMeshUtil.java#L118
I am wondering why do we have this restriction for topic names.
If we want to create topic names with my own, such as "my-event-topic", what is the solution.
Thanks.

Hi Dear,
I play around with EventMesh project and also studying the EventMesh codes. I see the RMQ Topic created through EventMesh, the topic name needs to be certain format. For example, "FT0-e-80010000-01-1"
From the code, this method check weather the topic is valid:
https://github.com/apache/incubator-eventmesh/blob/develop/eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/util/EventMeshUtil.java#L118
I am wondering why do we have this restriction for topic names.
If we want to create topic names with my own, such as "my-event-topic", what is the solution.
Thanks.

Hi, format validation for event topics may be a bit of a problem for you at the moment. For now, you can create topics in the format FT0-E-80010000-01. Similarly, you can create topics such as:FT0-E-80010001-01, it should be noted that e in the event topic and the fourth position of 80010001 is 1  . We will remove the verification of this part later and provide relevant guidance. Thank you

Thanks for your answer.


Constraints doc edits

https://jira.mesosphere.com/browse/MARATHON-7193

Thanks, @jdef

@jdef could you review it again? Thanks in advance!

Changes made. Thank you, @jdef and @ichernetsky


z-index

Not sure if this is on purpose but it seem like the default  z-index on markers (based on their latitude) is not applied after markers are clustered.
Is there a parameter that can be set for it?

I'm running into the same kind of issue. I have an issue where the clustered markers fall over a 'my location' marker, but in the part where those two markers overlap, the clustered marker is not clickable.
Assigning a higher z-index would be the solution, but it would be good to know if there's a way to set this up properly.

Having exact same problem as @bramwillemse. No matter what Z index you set, cluster marker will always be above your own marker, apparently because cluster markers are rendered in a higher overlay.


Pass through --weak-refs --reference-types flags to bindgen

Fixes #930
Closes #888
I'm wondering if it'd make sense to have a --bind-gen-opts flag which allows the user to manually specify args to pass through

@serprex Thank you for putting this together. It appears that a patch is also required to wasm-opt as well?
I've been successfully building my project using:
cargo build --target wasm32-unknown-unknown
wasm-bindgen ./target/wasm32-unknown-unknown/release/wasm_test.wasm --out-dir pkg --target web --reference-types

But when I attempt to build with your fork I get:
matt@matt-X570-AORUS-ELITE:~/rust/wasm_test$ ~/rust/wasm-pack/target/debug/wasm-pack build --target web --reference-types
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
    Finished release [optimized] target(s) in 0.01s
:-) [WARN]: origin crate has no README
[INFO]: Installing wasm-bindgen...
[INFO]: Optimizing wasm binaries with `wasm-opt`...
[parse exception: Only 1 table definition allowed in MVP (at 0:467)]
Fatal: error in parsing input
Error: failed to execute `wasm-opt`: exited with exit code: 1
  full command: "/home/matt/.cache/.wasm-pack/wasm-opt-4d7a65327e9363b7/wasm-opt" "/home/matt/rust/wasm_test/pkg/wasm_test_bg.wasm" "-o" "/home/matt/rust/wasm_test/pkg/wasm_test_bg.wasm-opt.wasm" "-O"
To disable `wasm-opt`, add `wasm-opt = false` to your package metadata in your `Cargo.toml`.

Yes, I've disabled wasm-opt in my project because it raises errors about mutable global state not being allowed. I added reference-types since that exists in wasm bindgen, but am only actually using --weak-refs

@serprex https://stackoverflow.com/a/64507864

Any updates on this. This could be really useful.

Can this one be merged? It could be really helpful.

We've moved from running wasm-pack to running wasm-bindgen and wasm-opt directly and just hand-coding the package.json and LICENSE file, etc. because we're missing the --weak-refs feature in wasm-pack.
I used this opportunity to test out why wasm-opt was failing, as @mattcollier noticed above.
This PR would simply need a change to pass --enable-reference-types to wasm-opt in order for it to run through.
Perhaps that's the change needed in this PR to get this merging? @serprex are you interested in adjusting this PR with my suggested change?
And @ the maintainers of wasm-pack: Would you merge this PR once it works with wasm-opt enabled?

@matheus23 updated

@serprex Yes, confirming that this works :+1:

Any updates on this PR? Running into this issue as well and would love to be able to pass in --weak-refs to wasm-bindgen

Yes, I'd love to see this merged & released as well!
Is there some remaining work to be done?
The tests seem to be failing due to this:

thread 'build::build_different_profiles' panicked at 'called Result::unwrap() on an Err value: ErrorMessage { msg: "received a bad HTTP status code (404) when requesting https://github.com/WebAssembly/binaryen/releases/download/version_108/binaryen-version_108-x86-linux.tar.gz" }

But that error happens with all recent PRs.
Is there something else To-Do? Do we need to bump the version/write docs? Anything we can do to help this get pushed over the finish line?

Yes, I'd love to see this merged & released as well! Is there some remaining work to be done?
The tests seem to be failing due to this:

thread 'build::build_different_profiles' panicked at 'called Result::unwrap() on an Err value: ErrorMessage { msg: "received a bad HTTP status code (404) when requesting https://github.com/WebAssembly/binaryen/releases/download/version_108/binaryen-version_108-x86-linux.tar.gz" }

But that error happens with all recent PRs.
Is there something else To-Do? Do we need to bump the version/write docs? Anything we can do to help this get pushed over the finish line?

I think the tests just need to be fixed in order to create a new release with this and the other recently merged PRs. If someone would be interesting in debugging and make the tests pass it would be really nice! I don't got much time to debug it right now unfortunately... Another solution would be to revert the PR that caused the failing tests...

Another solution would be to revert the PR that caused the failing tests...

I actually think there wasn't a PR that caused the failing tests, it was just the URLs for the binaryen stuff changing under our feet:
Before/after:
https://github.com/WebAssembly/binaryen/releases/download/version_108/binaryen-version_108-x86-linux.tar.gz
https://github.com/WebAssembly/binaryen/releases/download/version_108/binaryen-version_108-x86_64-linux.tar.gz
You can see that the top URL fails to load (it's the one from the failing test) and the bottom one loads successfully.
I can see if I can create a PR.

Any chance this can be merged soon? Kinda a waste to have to just bypass wasm-pack if features aren't available...

For those coming across this issue, you can also set WASM_BINDGEN_WEAKREF=1 and WASM_BINDGEN_EXTERNREF=1 environment flags and they will be passed down to wasm-bindgen

@bouk
How did you pass the flags? I tried WASM_BINDGEN_WEAKREF=1 wasm-pack build ..., but it didn't work for me.


Implementation of Smith normal form method.

Added class of matrices, so that we can calculate Smith normal form of a matrix and it's rank.
Issue: #39

Requested changes have been implemented.


Update Composer dependencies (2020-08-05-00-15)

Visual regression test passed!
View the visual regression test report


initAuth is not populating auth.user in feathers 3.0

I was having a problem with initAuth that after the first login if the page was refreshed the user would not be populated, yet the payload was there.
I created a fix in a fork that i´ll post below to help anyone with the same problem.
I changed the initAuth function in /src/utils.js
var initAuth = exports.initAuth = function initAuth(options) {
  var _Object$assign = Object.assign({}, authDefaults, options),
      commit = _Object$assign.commit,
      dispatch = _Object$assign.dispatch,
      req = _Object$assign.req,
      moduleName = _Object$assign.moduleName,
      cookieName = _Object$assign.cookieName;

  if (typeof commit !== 'function') {
    throw new Error('You must pass the `commit` function in the `initAuth` function options.');
  }
  if (!req) {
    throw new Error('You must pass the `req` object in the `initAuth` function options.');
  }

  var accessToken = readCookie(req.headers.cookie, cookieName);
  var payload = getValidPayloadFromToken(accessToken);

  if (payload) {
    commit(moduleName + '/setAccessToken', accessToken);
    commit(moduleName + '/setPayload', payload);
  }
  try {
    var user = dispatch(moduleName + '/populateUser', payload.userId)
    return Promise.resolve(user);
  } catch (error) {
    return Promise.resolve(undefined);
  }
};

Hope it helps someone.

It's always appreciated when people publish solutions to the community.  Thank you!  They may also benefit from this article by @Mattchewone: https://medium.com/@mattchewone/feathersjs-nuxt-ssr-authentication-75e97b6ce125
They may even benefit from this comment: https://github.com/feathers-plus/feathers-vuex/issues/93#issuecomment-376476715

Not 100% sure about the solution @guzz. The populateUser would fail since the featherClient authenticate hasn't been called yet with the JWT access token. Following the Medium solution, the auth happens AFTER the initAuth call.

@guzz I don't have access to close it, so you will have to.


Reading data type conversion problem: float64 to int64、int32....

==================================================================
device-mqtt-go/internal/dirver/incominglistener.go Line 54
func onIncomingDataReceived(client mqtt.Client, message mqtt.Message) {
	var response map[string]interface{}
	json.Unmarshal(message.Payload(), &response)
        .......

device-mqtt-go/internal/dirver/driver.go Line 296
func newResult(deviceObject models.DeviceObject, ro models.ResourceOperation, reading interface{}) (*sdkModel.CommandValue, error) {
	var result = &sdkModel.CommandValue{}
	var err error
	var resTime = time.Now().UnixNano() / int64(time.Millisecond)

	switch deviceObject.Properties.Value.Type {
	case "Bool":
		result, err = sdkModel.NewBoolValue(&ro, resTime, reading.(bool))
	case "String":
		result = sdkModel.NewStringValue(&ro, resTime, reading.(string))
	case "Uint8":
		result, err = sdkModel.NewUint8Value(&ro, resTime, reading.(uint8))
	case "Uint16":
		result, err = sdkModel.NewUint16Value(&ro, resTime, reading.(uint16))
	case "Uint32":
		result, err = sdkModel.NewUint32Value(&ro, resTime, reading.(uint32))
	case "Uint64":
		result, err = sdkModel.NewUint64Value(&ro, resTime, reading.(uint64))
	case "Int8":
		result, err = sdkModel.NewInt8Value(&ro, resTime, reading.(int8))
	case "Int16":
		result, err = sdkModel.NewInt16Value(&ro, resTime, reading.(int16))
	case "Int32":
		result, err = sdkModel.NewInt32Value(&ro, resTime, reading.(int32))
	case "Int64":
		result, err = sdkModel.NewInt64Value(&ro, resTime, reading.(int64))
	case "Float32":
		result, err = sdkModel.NewFloat32Value(&ro, resTime, reading.(float32))
	case "Float64":
		result, err = sdkModel.NewFloat64Value(&ro, resTime, reading.(float64))
	default:
		err = fmt.Errorf("return result fail, none supported value type: %v", deviceObject.Properties.Value.Type)
	}

	return result, err
}

===================================================================
I send the data  {"name":"test-device","cmd":"speed","speed":12} to DataTopic, the type of response["speed"]  is float64 via json.Unmarshal(message.Payload(), &response).
In this way, both int64 and int32 will be unified into float64. So, It needs to convert the reading into a data type defined in valueDescriptor.
In this case, the type of speed is int64 in valueDescriptor. So it will run case "Int64": 		result, err = sdkModel.NewInt64Value(&ro, resTime, reading.(int64)). Howerver, this will lead to panic : panic: interface conversion: interface {} is float64, not int64.   I hope that I can pay attention and fix such bugs as soon as possible.
In order to verify that converting reading is the wrong way, I  do a simple test.
package main

import (
	"encoding/json"
	"fmt"
	"reflect"
)

func main() {

	var response map[string]interface{}
	a := []byte(`{"name":"test-device","cmd":"speed","speed":12}`)
	json.Unmarshal(a, &response)
	//reading := response["speed"].(int64) // panic: interface conversion: interface {} is float64, not int64
	reading := int64(response["speed"].(float64))
	fmt.Println(reading)  // 12
	fmt.Println(reflect.TypeOf(reading)) // int64

}

@AhaEdgar  Golang will recognize it as float or int. I have created an issue https://github.com/edgexfoundry/device-mqtt-go/issues/6 and a PR https://github.com/edgexfoundry/device-mqtt-go/pull/11, please feel free to review or test my branch if you like.

@AhaEdgar
Thanks for reporting this issue.
We have made lots of data type checking and transformation #11, and it also covers this issue.
Could you please help try again and see whether we can close this issue?


Split UserSettings form

It's common that different settings connect to different models (in an applications where users have more to do) or that some things like changing your password/email have their own workflow for confirmation/verification.
So rather than using a single <form>, I usually to build a more modular settings menu.
For example, the user settings in LiNT are layed out like this:

My point is not about aesthetics, but the idea is to divide the page into several sections that can function as stand-alone components and use their own <form> (if applicable). For example, the change password option folds out into an old password / new password / repeat new password <form> that has its own submit event. This makes sense because (both here and in LiNT), changing your password connects to a different API endpoint from other settings.
Another advantage of dividing settings into several sub-components is that it's a component that can really grow out of control otherwise.
In this case, it would make sense to divide this page into the following sections:

Username
Personal details (i.e. first/last name)
Email
Password
Delete account

Originally posted by @lukavdplas in https://github.com/CentreForDigitalHumanities/lettercraft/pull/64#discussion_r1598356468

This refactor should also include the /password/change/ endpoint to allow for easy password changes (rather than requesting a password reset link), although that could still be valid as an alternative.


shapes:getPoints() / collider:getPoints()

Would be great to be able to get the points for reading/checking/fault finding etc.
Thanks!

I can definitely add a method to the VertexShape class, but I'm not sure it makes sense to add it to the Collider class 🤔 since there are potentially multiple shapes within a collider. I know a lot of the base ones don't have multiple shapes, but the Collider class is like a tree node. It was meant to provide a way to group multiple shapes together, mainly so concave polygons could be decomposed and treated like anything else

My use case:
I draw all sorts of things during love.draw() and on my current project I scale everything by 5 (x5) because makes sense. I have an object that is displayed at x * 5 and y * 5 and it appears 5 times as large. I do NOT adjust the original / real x/y co-ordinates. My scaling happens during draw routines only. This way, vector maths and manipulations happen at 1:1 and the drawing explodes this to 5:1 (of course the 5:1 is arbitrary).
My objects have a collider but collider:draw() will, naturally, draw 1:1. This means all my colliders are draw in the top left corner of the screen and are totally out of sync with what is being drawn elsewhere.
If I could interogate the points of the collider/shapes (not sure what is best) then I could also render those 5:1 onto the screen during love.draw() and the colliders once again align with the drawn images.
It is the same principle as box2d meter property. It defaults to 30 and scales everything by 30. I'm using the same principle during my draw routine.
Clearly, this is for debugging only. Thanks.

Added a pr for this
Out of curiosity, are you using love's transformations or are you manually passing in the scaling to each draw call?

I do it inside love.graphics.draw(). In the below example, DRAWSCALE is a constant. I set it to 1 (1:1) to debug colliders then set it to 5 (5:1) to debug the game as it's intended to look and feel.
 love.graphics.draw(IMAGE[obj.imageenum], obj.x * DRAWSCALE, obj.y * DRAWSCALE, facingrad, xscale * DRAWSCALE, yscale * DRAWSCALE, xoffset, yoffset)
My code is open source FYI: https://codeberg.org/togfox/WW2SubCombat/src/branch/main/source

I think the problem then is that you're not scaling the drawn colliders. And there's not a parameter for that :(
(There used to be, but I removed it when I added geometry transforms.)
What you might be able to do is this:
love.graphics.scale( DRAWSCALE , DRAWSCALE )
collider:draw()
love.graphics.scale( 1, 1 )

Although I'm not sure if that'll position it properly 🤔
I could look into trying to add the scaling back.

That actually works!!  :)

Ok, cool! I'll still merge the pr, but closing this.


feat: long strings syntax for use in attributes

Feature Request
Describe the Feature Request
Although long strings are far from being implemented in Cairo at runtime, compile-time parts of the language (namely attributes) could already make a good use of them.
Describe Preferred Solution

Add syntax for "long string" literals and allow them in expression context.
Reject long literals during expression lowering phase, but leave them intact for attributes.

Additional Context
@MaksymilianDemitraszek correct me if I'm wrong, but I recall that there was an idea for some attributes in Protostar that required long strings, wasn't it?

no longer relevant - as we actually have "long string" syntax for long strings.


I can't get caching to work, but it's because I don't understand the doc

I'm using the docker image and I have the baget.env file to setup the config, etc..
the only feature I need is read-through caching; essentially I want to be able to do .net builds while abroad on a crappy connection.
in the doc, at https://loic-sharma.github.io/BaGet/configuration/#enable-read-through-caching, I see:
"You can modify BaGet's configurations by editing the appsettings.json file."
but this file is part of BaGet's code, so does that mean I need to rebuild my own docker image and there is no way to set the the read through cache though an external config file?

You're supposed to be able to set an environment variable: MIRROR__ENABLED=true and MIRROR__PACKAGESOURCE=<URL TO PACKAGE SOURCE>. BUT, I haven't been able to get this to work...either via Docker, or by a bare-metal install and modifying the appSettings.json  file. Maybe you could give it a whirl, trying to set the environment variable in your docker image container and see if it works?

This is the asp.net core configuration feature. https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-5.0#environment-variables-1


Macro Stageless payload troubles

The image above shows command output from tool when building payload. Tool version is current build as of today for IVY 1.12 and CS (CobaltStrike 4.7.1).
Stageless payload from CS is "Windows Stageless Payload"->RAW (also tried Stageless Payload Generator->raw)
Here is what was observed:

macro payload in excel appears to execute without visible errors (even when cscript is run on test.txt in the appdata excel path)
test.txt is pulled down from local py webserver, no issues.
outlook.exe spawns -> cscript.exe (with F://jscript .... args) which spawns -> excel.exe
No call back attempt from macro :( verified via FW log and c2 server.

Troubleshooting done so far:

CS c2 profile validated to call home via stageless windows exe. no UDRL in play. not even sleepmask. No CNA's. No kits.
Run w/ -debug command
Tried without -unhook command as well. no change.
No IPS no egress filtering in play

My Current Theory:

Maybe c2 profile has wonky settings not tested with tool? Have you had issues with custom mall c2 profile and tool? (just came to me)
struct.go exec issue for macro?
shellcode file doesnt make its way into payload (but size of b64 blob in test.txt makes me think it does)
Shellcode exec call not working

Any help would be great.

with some changes i got 1 callback working .

what changed?

sry i missed your reply. from what i recall (if i recall correctly) there was a file exists input/output check(s). yep i put the file path in wrong :( and....im sry i forgot the rest.


Pin scikit-learn

Closes #4247
The newest version of scikit-learn is incompatible with the version of imbalanced-learn that we're pinned to. Unfortunately, imbalanced-learn must remain pinned due to lack of nullable type handling, so we can't upgrade scikit-learn. Once imbalanced-learn fixes their nullable type issues, we should be able to unpin both.
Nonetheless, this includes changes to Decision Tree and Extra Trees estimators to remove a deprecated "auto" argument that will be fully removed once we do upgrade to 1.3.0.

In further investigation of the imbalanced-learn error that caused its pinning, I found a workaround since the error is just in one of our tests.
Pausing review on this PR until I can determine if this workaround allows me to unpin imbalanced-learn as well as upgrade scikit-learn instead of pinning it.

Looks like this is blocked until https://github.com/conda-forge/sktime-feedstock/pull/94 is merged

Looks like this is blocked until conda-forge/sktime-feedstock#94 is merged

No longer blocked :-)


Issues finding subject

Payload key for subject is hard-coded - may need to search for "Subject" to prevent errors.

close #9


Added AdSpyglass ad server

AdSpyglass is using some random domains, for example mousecatzilla.com and profield.ddns.net which can be blocked by 0i0i0i0.com CNAME. So I think that it would be a good idea to add 0i0i0i0.com to "cloaked trackers" to find more similar domains.
Screenshot

Per https://www.robtex.com/dns-lookup/0i0i0i0.com#analysis,

We investigated 100 host names that cnames to 0i0i0i0.com . We estimate that it is used via cname by 131 host names.


Rework Labels

Our labels (for selectors) are a mess.  Fix them.
As an example, the master nodes should probably have labels that identify them as such.

Done!


draft version of program output with docusaurus

Proposed changes:

Fixes https://github.com/RasaHQ/rasa/issues/6202

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@tmbo here is a draft for the program-output directive. Can you tell me what you think? If you validate the approach, I'll cleanup + document a bit more + update the other mdx files.
➡ This script parses the docs, get the commands, run them, saves the outputs in a file (separate for each command) in the the docs/sources/ folder. Then there is a custom remark plugin that parses the code blocks and injects the command outputs by reading the files in the docs/sources/ folder.
FWIW I tried to create a docusaurus plugin to make it work, but couldn't, so I decided to run a custom "pre-build" script instead, like for the variables.

yes approach looks good :rocket:


Reverted to stable version of dotnet cli

Reverted to stable version of dotnet cli as latest version is having issues.

Already part of PR #1241.


Unable to select folders in a Shared Library from the OneDrive JS Picker

Category

[x] Question
[ ] Documentation issue
[ ] Bug

Expected or Desired Behavior
A user should be able to select either a folder or file in a Shared library (Private  access) and shared link should be generated.
Observed Behavior
A user is only able to select  files in a Shared library. If a folder is selected the OneDrive JS Picker throws the following error:

Please find the Date, request-id and SPRequestGuid in the screenshot.
What is the permission or feature referenced by this error?
Steps to Reproduce

Create a Shared Library (Private)
Create a folder and file
Access the Shared Library from the OneDrive picker
Select the folder

Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

Nudge :)

Nudge

Bump

@chackman would you be able to help us get this sorted out? I work with @splinter (am on the management side) and this has been escalated by our prospect. Tks.

I need this quite desperately, is this opensource so that I can fix the folder selection?

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Training object detection

Add wrapper to read mot dataset.
Add notebook showing how to launch a training and visualize predictions.

The goal of the repository is to be focused on plastic detection. Code related to COCO or "Balloon" example should be as much as possible removed - in future PRs.


[feature request] Faster Split (data partition)

Besides of histogram construction, the data partition is another time-consuming part in LightGBM. This process is to update the row set for each leaf.
The code is in the following:
https://github.com/microsoft/LightGBM/blob/997a469f780f2720055df3b8276c79d412cb15d3/src/treelearner/data_partition.hpp#L113-L172

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.


Add functionality to static call with custom call

Let the user specify:

Custom calldata
Make deployments inside of a static call, being able to retrieve arbitrary information without deploying any contract

Refactored this PR to just refactor the existing ContractInput and new_evm functions to support contract creation as well.

awesome ^^


Inspect command for mgadm

Inspect command take an image as argument and return information from image and deployment (if present). The function created will be used internally for gathering information for upgrade

@cbosdo , thanks for all your comment, now should be fine. Changes are:

error handling
remove podman/kubernetes argument
improve argument parameter: if image and or tag are not passed, the value are detected by the running image

Closing this PR, this change would be implemented in upgrade PR


Manually-specified variables were not used by the project:

I am trying to build zxipg to use in out application (Feathercoin). Something has happened in Ubuntu 16.04, where our usual build from source has failed (although we already moved over to Qt5) it seems to an issue with -
   -D_GLIBCXX_USE_CXX11_ABI=0

or =1 , which needs to be set the same for both builds, I get the error message :
Manually-specified variables were not used by the project:

 _GLIBCXX_USE_CXX11_ABI

The method which worked before, copying compiled zxing headers to /src/zxing/ sub directory/
we now get error :
src/qt/snapwidget.cpp:71: undefined reference to `zxing::String::getTextabi:cxx11 const'

build zxing-cpp like this:
mkdir zxing && cd zxing
git clone https://github.com/glassechidna/zxing-cpp.git
cd zxing-cpp/
ls
mkdir build
cd build/
export CXXFLAGS="-fPIC"
cmake -G "Unix Makefiles" -DCMAKE_CXX_FLAGS=-D_GLIBCXX_USE_CXX11_ABI=0 -DCMAKE_BUILD_TYPE=Release ..
make && sudo make install


Fonts not working properly

When I try to create a text with a font on Figma it changes it when it gets exported.
this is the Figma project:

And this is the result:

Note that this happens with every font, not only this one

The font you select on the Figma website must be installed on your machine. Check if your selected font is installed on your device.

Also https://github.com/ParthJadhav/Tkinter-Designer/issues/78

The font you select on the Figma website must be installed on your machine. Check if your selected font is installed on your device.

If I try to use Roboto bold on Figma it will export as font = ("Roboto-Bold"). this will show up as some font that is not Roboto bold. if I change the font = ("Roboto-Bold") into font = ("Roboto Bold") it will show up as Roboto bold.

That's Strange because on my side it works perfectly fine ->
Roboto Medium -> Roboto Bold -> Roboto Light
Tkinter -

Figma -

What platform are you testing it on? Windows?

He is testing on windows. From the look of his status bar. Replied for your convenience.

I added it in my PR #87 . Hopefully that will fix the font issues.

Hey @Pigii the problem has been resolved in the latest version.


SHA1 hash algorithm replacement

Replace mentions of using SHA1 with SHA256 (especially), SHA284, or SHA512. This involves:

Conceptual documentation.
Reference documentation. This includes a note in the SHA1 documentation that it is not recommended, and that the suggested replacement is SHA256.
Code. Usage of SHA1 should be replaced except for code for the SHA1 type in the managed reference documentation.

There were separate issues for MD5 (#10198) and SHA1, but the SHA1 work is being done for the MD5 issue, so I'm changing the MD5 issue to be for both and closing this one.


unused_variables, should respect pseudo comment

https://rules.abaplint.org/unused_variables/
should respect pseudo comment "#EC NEEDED

hmm, and/or the pragma ##NEEDED

hmm, and/or the pragma ##NEEDED


Update verification.py adding an exception for Sourceforge

Closes issue #1939

closes #1939

Currently for GitHub and GitLab we don't allow domain verification if you have a deprecated app ID, but since we don't have SourceForge as a login provider I guess this is fine. net.sourceforge should be added in _check_app_id so that no new apps are created with the deprecated ID. Other than that, looks good to me.

Currently for GitHub and GitLab we don't allow domain verification if you have a deprecated app ID, but since we don't have SourceForge as a login provider I guess this is fine. net.sourceforge should be added in _check_app_id so that no new apps are created with the deprecated ID. Other than that, looks good to me.

The sourceforge.net subdomains are deprecated for new projects registered on Sourceforge. If you register today a project in Sourceforge, they give you a sourceforge.io subdomain for your project web. But old projects (prior to 2016) still have one (in addition to a sourceforge.io subdomain). Most old projects have redirections from project.sourceforge.net to project.sourceforge.io, but that is a non compulsory option. Indeed, the HTTPS protocol was enabled in sourceforge.net subdomains since September 2022. The point is that if the old sourceforge.net projects want to be added to GitHub now (they become a new project here), they still should be able to use a net.sourceforge app ID, in my opinion.


🐛 onAdFailedToLoad() argument "error code" different between android and ios?

ios
https://developers.google.com/admob/ios/api/reference/Enums/GADErrorCode
GADErrorInvalidRequest = 0
GADErrorNoFill = 1
GADErrorNetworkError = 2
android
old
https://developers.google.com/android/reference/com/google/android/gms/ads/AdRequest
ERROR_CODE_INTERNAL_ERROR 0
ERROR_CODE_INVALID_REQUEST 1
ERROR_CODE_NETWORK_ERROR 2
new
https://developers.google.com/android/reference/com/google/android/gms/ads/package-summary
cant find

Search result
ios
Search results for GADErrorCode
Did you mean: GETErrorCode site:developers.google.com/admob/ios/
GoogleMobileAds Framework Reference | iOS | Google Developers
Google Developers › Google AdMob › Mobile Ads SDK (iOS)
GADErrorCode. enum GADErrorCode : NSInteger {}. NSError codes for GAD error domain.
<< and more>>
android
Search results for GADErrorCode
Did you mean: GETErrorCode site:developers.google.com/android/
No Results
Search for GADErrorCode on Google

The plugin just passes the error codes directly from GMASDK, which are different between iOS and Android.
Android error codes can be seen here: https://developers.google.com/android/reference/com/google/android/gms/ads/AdRequest#constant-summary
The link you shared contains the iOS error codes: https://developers.google.com/admob/ios/api/reference/Enums/GADErrorCode


Update java docs for DirectConnectionConfig

DirectConnectionConfig has a lot of different tuning variables including idleEndpointTimeout, idleConnectionTimeout, etc.
The java docs on some of these can be improved more to explain their behavior better to the customer.

This is done.


Hierarchy Decorator Bug - Cant unfold at the bottom

Unity Version
Describe the bug
Cant unfold gameobjects which are at the bottom of the hierarchy
To Reproduce (If applicable)
Add children to the gameobject at the bottom of the hierarchy
try to unfold gameobject
Screenshots

Additional context
Add any other context about the problem here.

Ah yeah, it's on my todo list, are you on Unity 2020 (or higher)?
Unity has a lack of control over GUI in some cases and even though the foldout you see above is drawn on top of the two-toned background, it isn't actually interactable. It's just visual.
But Unity still detects interaction on it. It's really frustrating. Anyway, I've actually got a fix for it and it should actually be good to go.
I've noted the issue you're experiencing here as this was reported in the last day or so.
I was going to push it with a fix for the flicker that appears but since it's quite serious I'll push it shortly as a quick fix.
Apologies for the issue it is causing!

Hey! I'm using 2020.3 (LTS) .. This is the only issue I've encountered. Look forward to the fix!

Hey there, I've just released a new version herethat should fix this for you.
If this persists or comes back in the future I'll reopen the issue.
Cheers for reporting this, I appreciate it!
~Wooshii


Convert docs page to an FAQ

Link to internal project
Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
Currently this page https://docs.getdbt.com/docs/building-a-dbt-project/dont-nest-your-curlies lives in the Docs area which seems a bit out of place.
What part(s) of the page would you like to see updated?
Convert the page to an FAQ. Then, create a redirect and update links that point to the page.
Additional information
No response

We moved this and I think it's great where it is. Feel free to reopen if you think we should address this.


Instllation error 500

Zammad version 3.2
Hello
After browse to sms77.rb when i click on install package, I redirect to the following page with Error 500
https://myzammad.com/api/v1/packages

Hi,
are you on PHP 5.x ? That might be the reason.
If that's the case, I can make a custom branch for you that works on PHP 5.x!

Hi
I i am on PHP 5.4.16
Yes please provide me a custom branch that works on PHP 5.x
Regards

Please forget what I said as this is a package written in Ruby :-)
I will look into the issue. Give me a couple of days.

But u must have been able to install it at some point according to this issue?
The package has not changed ever since.

Still I can not install it and i got the error.

You probably need to install Zammad 3.5.x. It works very well with this version I have just tested it.

Now i am on Zammad 3.6.x. with same result, Redirect to page Error 500

What Ruby version are you using ? I will test it with your version.

Version 2.6.6


[BUG with v0.5.2] Calling getPosition on many nodes in a tree somehow modifies Node positions.

I've made a PR at #380. This new method, getPositionFrom, calls only getPosition of nodes in a tree. When I attempt to use this method in my test app, node positions get unexpectedly modified somehow.
I've no idea yet what actually causes the bug, but am observing it using Engine v0.5.2.
Following is code to reproduce it. Paste it into one of the editors on famous.org. You'll notice a weird layout that zooms in and out. Comment/uncomment line 259, the one that looks like:
console.log('position of node from scene', cards[i].goToNode.getPositionFrom(scene))

When that line is commented out, the layout will look as expected. When you toggle that line, you'll notice that the positions of all the Nodes, outputted to console, are either normal (when line 259 is commented out), or extremely huge (when line 259 is uncommented). Line 259 is simply calling the getPositionFrom method on each node (line 22), the same method from in PR #380.
This is the code:
function program() {
    "use strict"

    // Famous dependencies
    let Engine         = famous.core.FamousEngine;
    let Camera         = famous.components.Camera
    let Transitionable = famous.transitions.Transitionable
    let Node           = famous.core.Node
    let DOMElement     = famous.domRenderables.DOMElement
    let Scene          = famous.core.Scene

    let cards = [] // storing temporary "cards" here to lay them out.

    // class BetterNode extends Node
    function BetterNode() {
        Node.apply(this, arguments)
    }

    BetterNode.prototype = Object.create(Node.prototype)
    BetterNode.prototype.constructor = BetterNode

    BetterNode.prototype.getPositionFrom = function getPositionFrom(ancestor) {
        var position = this.getPosition()
        var currentParent = this._parent
        var parentPosition

        var level = 1

        if (!(ancestor instanceof Node))
            throw new Error(''+ancestor+' is not an instance of Node.')

        // Go through all the nodes up through the ancestor.
        while (currentParent && currentParent !== ancestor) {
            parentPosition = currentParent.getPosition()

            position[0] += parentPosition[0]
            position[1] += parentPosition[1]
            position[2] += parentPosition[2]

            currentParent = currentParent._parent
            level+=1
            //console.log('parent position:', parentPosition)
        }

        if (!currentParent)
            throw new Error(''+ancestor+' is not an ancestor of this '+this)

        //console.log('-- level:', level, position)
        return position
    }
    // TEST for getScenePosition()
    //let Engine = famous.core.FamousEngine;
    //var scene = Engine.createScene('.scene')
    //var node1 = scene.addChild(new BetterNode).setPosition(10,0,0)
    //var node2 = node1.addChild(new BetterNode).setPosition(20,0,0)
    //var node3 = node2.addChild(new BetterNode).setPosition(5,0,0)
    //var pos = node3.getPositionFrom(node2)
    //console.log(pos)

    // class Layout extends BetterNode
    function Layout() {
        BetterNode.apply(this, arguments)
        this.columnWidth    = 200 + 20
        this.rowHeight      = 95 + 20
        this.childrenGetter = null
        this.rootItems      = null

        window.n = this
    }

    Layout.prototype = Object.create(BetterNode.prototype)
    Layout.prototype.constructor = Layout

    // traverses the trees in rootItems recursively.
    Layout.prototype.createLayout = function createLayout(numberOfLevels) {
        if (!this.childrenGetter)
            throw new Error(`
                You need to set the child getter with Layout#setChildrenGetter first.
            `.trim().replace(/\s/, ' '))
        if (!this.rootItems)
            throw new Error(`
                You need to specify the root nodes with Layout#setRootItems first.
            `.trim().replace(/\s/, ' '))

        let self = this
        let initialLevels = numberOfLevels

        // TODO: Remove. Random colors for now.
        var colors = []
        for (let i=0; i<numberOfLevels; i+=1)
            colors.push(`rgb(${
                Math.ceil(Math.random()*255)},${
                Math.ceil(Math.random()*255)},${
                Math.ceil(Math.random()*255)})`)

        function _createLayout(numberOfLevels, currentLevelItems) {
            var currentLevelLayoutNodes = []

            if (numberOfLevels > 0) {
                for (let i=0, len1=currentLevelItems.length; i<len1; i+=1) {
                    let currentItem = currentLevelItems[i]
                    let currentLevelLayoutNode = (new BetterNode())
                        .setOrigin(0.5,0.5)
                        .setAlign(0,0)
                        .setMountPoint(0,0)
                        .setSizeMode('absolute', 'absolute')

                    /*
                     * TODO: Remove. These are temporary DOMElements to visualize
                     * the layout spaces, shared globally for the entry point to manipulate.
                     * Cards will be added externally.
                     */
                    let cardNode = scene.addChild(new BetterNode)
                        .setOrigin(0.5,0.5)
                        .setAlign(0,0)
                        .setMountPoint(0,0)
                        .setSizeMode('absolute', 'absolute')
                        .setAbsoluteSize(self.columnWidth,self.rowHeight)
                    let card = new DOMElement(cardNode, {
                        content: `<div style="width: 100%; height: 100%; border: 10px solid white; background: ${colors[numberOfLevels-1]}"></div>`
                    })
                    cards.push(cardNode)
                    cardNode.goToNode = currentLevelLayoutNode

                    new DOMElement(currentLevelLayoutNode, {
                        content: `<div style="width: 100%; height: 100%; border: 10px solid white; background: ${colors[numberOfLevels-1]}; opacity: 0.5"></div>`
                    })

                    currentLevelLayoutNodes.push(currentLevelLayoutNode)

                    let childItems = self.childrenGetter(currentItem, numberOfLevels)
                    let childLayoutNodes = _createLayout(numberOfLevels-1, childItems)

                    for (let j=0, len2=childLayoutNodes.length; j<len2; j+=1) {
                        currentLevelLayoutNode.addChild(childLayoutNodes[j])
                    }

                    // Width and height are multiples of rowHeight and
                    // columnWidth respectively.
                    // TODO, spacing, etc.
                    let sizeX = 0

                    // Cards at level 1 and 2 are the base width.
                    if (numberOfLevels < 3) sizeX = self.columnWidth

                    // otherwise add the widths of the children.
                    else for (let j=0, len2=childLayoutNodes.length; j<len2; j+=1)
                        sizeX += childLayoutNodes[j].getAbsoluteSize()[0]

                    //console.log('-- level, sizeX', numberOfLevels, sizeX)

                    currentLevelLayoutNode.setAbsoluteSize(
                        // the width a multiple of columnWidth and at
                        // least one columnWidth.
                        sizeX,

                        // all nodes are just rowHeight for now.
                        self.rowHeight
                    )

                    let positionX = 0
                    let positionY = self.rowHeight

                    // only the first level is positioned at Y = 0
                    if (initialLevels-numberOfLevels === 0) positionY = 0

                    // place cells from left to right in each level.
                    if (i-1 >= 0) {
                        let previousSizeX = currentLevelLayoutNodes[i-1].getAbsoluteSize()[0]
                        let previousPositionX = currentLevelLayoutNodes[i-1].getPosition()[0]
                        positionX = previousPositionX + previousSizeX
                    }

                    // except in the last level stack cells
                    if (numberOfLevels == 1) {
                        positionX = 0
                        positionY = positionY + i * positionY
                    }

                    currentLevelLayoutNode.setPosition(
                        positionX, positionY, 0
                    )
                    console.log('curent layout node position: ', currentLevelLayoutNode.getPosition())
                }
            }

            return currentLevelLayoutNodes
        }

        let rootLayoutNodes = _createLayout(numberOfLevels, this.rootItems)
        console.log('--------------- root layout nodes', rootLayoutNodes)

        for (let i=0, len=rootLayoutNodes.length; i<len; i+=1) {
            this.addChild(rootLayoutNodes[i])
        }
    }

    // set an array of items that are the roots of trees representing
    // the structure of the layout (the relationships of cards).
    Layout.prototype.setRootItems = function setRootItems(roots) {
        this.rootItems = roots
    }

    // fn called as fn(item, level) where item is the current item
    // being layed out and level is the current level in the map
    // layout.
    // fn should return an array of children.
    Layout.prototype.setChildrenGetter = function setChildrenGetter(fn) {
        this.childrenGetter = fn
    }

    // just a node structure representing the map layout spaces.
    // class MapNode
    function MapNode() {
        this.children = []
        this.parent = null
    }

    let mapNodeList = []
    function createRandomMapNodes(numberOfLevels) {
        let currentLevelNodes = []
        let numberOfNodesThisLevel = Math.ceil(Math.random() * 3)

        if (numberOfLevels > 0) {
            for (let i=0; i<numberOfNodesThisLevel; i+=1) {
                let node = new MapNode()
                currentLevelNodes.push(node)
                mapNodeList.push(node)

                let children = createRandomMapNodes(numberOfLevels - 1)
                node.children = children
            }
        }
        return currentLevelNodes
    }

    Engine.init()
    var scene = Engine.createScene('body')

    // make some random map nodes to arrange
    let numberOfMapLevels = 6
    let userStoryMapRoots = createRandomMapNodes(numberOfMapLevels)

    var layout = new Layout()
    layout.setRootItems(userStoryMapRoots)
    layout.setChildrenGetter(function(mapNode, level) {
        return mapNode.children
    })
    layout.createLayout(numberOfMapLevels)
    scene.addChild(layout)

    // TODO: use the real cards. For now the current sample they are added
    // inside the layout.
    console.log('number of cards:', cards.length)
    for (let i=0, len=cards.length; i<len; i+=1) {
        //let goToPosition = cards[i].goToNode.getPositionFrom(scene)
        //cards[i].setPosition(goToPosition[0],goToPosition[1],goToPosition[2])
        //console.log(cards[i].getPosition() === cards[i].goToNode.getPositionFrom(scene))
        console.log('position of node from scene', cards[i].goToNode.getPositionFrom(scene))
    }

    let cameraNode = scene.addChild()
    let camera = new Camera(cameraNode)
    camera.setDepth(1000)

    // animate the camera. TODO: This will be controlled with zoom...
    let camPositionZ = new Transitionable(0)
    ~function loop() {
        camPositionZ.to(10000, 'easeInOut', 6000).to(0, 'easeInOut', 6000, loop)
    }()

    let cameraAnimation = cameraNode.addComponent({
        onUpdate: function() {
            cameraNode.setPosition(0,0,camPositionZ.get())
            cameraNode.requestUpdateOnNextTick(cameraAnimation)
        }
    })
    cameraNode.requestUpdateOnNextTick(cameraAnimation)

}

program()

Updated, changed
var scene = Engine.createScene('.scene')

to
var scene = Engine.createScene('body')

But still nothing appears visually.

Ah, I forgot Engine.init(), now it all shows up. I've updated the original comment.

Updated original comment and title to reflect that I'm using Engine v0.5.2 in this case.

I've made another working sample: https://github.com/trusktr/meteor-famous-playground/tree/3cb73f92bbc132ce5fcffa875a63c034886a538d
To run, just make sure you have meteor installed then run meteor in the project and visit http://localhost:3000.

In 0.5.2's Node.js:
Node.prototype.getPosition = function getPosition () {
    return this.value.vectors.position;
};

You'll note it's returning a pointer to the actual array.
In getPositionFrom() you have (relevant parts shown with my comments):
+Node.prototype.getPositionFrom = function getPositionFrom (ancestor) {
...
    var position = this.getPosition() // as above, a reference to array itself
...
    while (currentParent && currentParent !== ancestor) {
        parentPosition = currentParent.getPosition()

        position[0] += parentPosition[0] //  \
        position[1] += parentPosition[1] //  - modification of original array
        position[2] += parentPosition[2] //  /

        currentParent = currentParent._parent
    }
...
}

Easy fix is to clone the array like with your function of choice, e.g.:
var position = this.getPosition().slice();

Don't feel bad, I make this kind of mistake all the time :>  But you get used to thinking about what you're manipulating and/or exactly what to look for when this kind of thing happens.  A lot of libraries give you cloned values by default to avoid the possibility of this kind of thing, but it has a performance consequence of course.
The docs should probably also be clearer about what kind of values (reference vs clone) are returned by what.  Even if Famous always returns references as a policy (I don't recall if this is a case or not), it's nice to be explicit in the docs for each method, since I believe an implicit assumption of getter methods is that they return cloned value unless otherwise stated.

Wow! I totally overlooked that.Thank you so much for pointing that out @gadicc! <:


Pagination Support

This PR adds in topic and ditamap driven support for the Bootstrap pagination bar

XSL updates
String internationalization
Documentation

A pagination bar can also be automatically added to the bottom of each page via parameters

@jason-fox Looks like this also includes the strings files changes from #23, so I marked this one as “draft” and added the rebase required label, so we remember to rebase it once the changes from #23 are merged.

@infotexture - Leave this one in draft until the others are complete.

but the use case for some things like pagination isn’t  readily apparent to me.

If you look at  this README for example, there is a prominent list of additional resources displayed on the page.

:books: Documentation
:whale: Docker Hub
:dart: Roadmap

The README uses markdown of course, but I'd like to be able to get the same effect  using the bootstrap pagination look-and-feel - that can be done by marking up an ordered list <ol outputclass=""pagination">inside the <topic>.

If you look at the documentation and scroll to the bottom of the page, you can see Next and Previous buttons.  The equivalent is generated by --bootstrap.pagination=partial - it is similar to rel-links but styled in a bootstrap manner.  --bootstrap.pagination=full shows the same but also lists all the siblings, not sure how useful that one is, but it is most similar to a pagination in classic usage.

This PR doesn't seem to contain DITA examples.

sample/pagination.dita shows the two use-cases in action.

🤔  maybe the way to do this is to split this in PR two.  Pagination could just be the format a list of links into pagination bar as described in use case 1. The add Next and Previous buttons could be a separate plugin extension of DITA bootstrap, that way other esoteric options could be isolated from the main plugin.

Superceded by #28


Fix for a optional 'scope' attribute

Sometimes google maps places API doesnt send a 'scope' attribute eventhough their documentation says it should alwaysbe eiter 'GOOGLE' or 'APP'
So not sending this attribute fails parsing the response with an IllegalArgumentException trying to get Scope.valueOf("")

The travis build is failing after running the unit tests trying to call the remote api and expects a key.

resolves https://github.com/windy1/google-places-api-java/issues/66


[Writable Warm] File Pinning support and TTL based eviction for FileCache

Is your feature request related to a problem? Please describe
With FileCache now being used by Composite Directory in addition to Remote Snapshots we need to add additional functionalities. A few examples below:

Pinning a certain file so that it is safe from eviction
More eviction strategies such as ttl based eviction (currently we only have overflow based eviction)

Describe the solution you'd like
File pinning and ttl based eviction should work.
Will update this section with more details once have a concrete LLD for this.
Related component
Storage:Remote
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2 3 4 5 6 7 8]
@rayshrey Thanks for creating this issue.