Updated for <IP_ADDRESS>

I doubt that you'll want to merge it straight away, but thought I'd still make a PR from my (very modest) changes. The only change is adding support for Implicit having another boolean parameter, indicating whether a module was imported implicitly like this:
import Prelude

or like this:
import Prelude (..)

I think for psc-ide it doesn't matter, didn't really add any extra logic.
This PR won't build as-is, as you'll need to point your stack.yaml file to the purescript src of version <IP_ADDRESS>.
Simon

I think they reverted thr extra boolean field in this commit: https://github.com/purescript/purescript/pull/1747.

 Closing...

Thanks a lot for looking into this. The real problem is that psc-ide relies on compiler internals that are not semantically versioned. We'll have to find a way to guard against the symptoms of that problem.
It's probably best to only develop against fixed versions of the compiler and bind our psc-ide releases to a certain compilerversion. We might even want to split the purescript dependant part out into it's own package that we could version in sync with the compiler.

Yeah using only the actual releases seems prudent, albeit a bit inflexible. Didn't I read somewhere that @paf31 preferred for psc-ide not to use the externs?

Yeah it would be better if we devised an editor/tooling specific format that could be emitted by psc-docs. But for now I rather deal with the few changes over having to maintain a completely new format.

Oh definitely, these small things are really not an issue to support.


ORM Problems

I used this as an example (thanks) to build a shipping method. However, I found that repeated saves of the method through the dashboard lead to one record for each attempt.
The fix is to use the same ORM mechanism as used in the bundled community store methods, ie:
private function addOrUpdate($type, $data )
{
//////$em = Database::connection()->getEntityManager();
$em = \ORM::entityManager();
}
public function addMethodTypeMethod($data)
{
/////return $this->addOrUpdate('add', $data);
        return $this->addOrUpdate('update', $data);
}

Is this the same as what I was scratching my head on here?
https://github.com/concrete5-community-store/community_store/issues/167

It sounds like exactly the issue I observed, yes. The two changes fixed it for me. I'm a bit of a noob at this ORM stuff, but it does seem to be the case that it's easy to detach or unmerge an object from ORM, such as might happen when creating a new instance of the entity manager, and that leads to a new record being inserted.

The code I ended up with is here:
https://github.com/JeRoNZ/community_store_shipping_nz_flat_rate


spring session with spring security error

org.redisson.client.RedisException: Unexpected exception while processing command
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not construct instance of org.springframework.security.authentication.UsernamePasswordAuthenticationToke
n: no suitable constructor found, can not deserialize from Object value (missing default constructor or creator, or perhaps need to add/enable type information?)
at [Source: io.netty.buffer.ByteBufInputStream@3a0db884; line: 1, column: 184] (through reference chain: org.springframework.security.core.context.SecurityContextImpl["aut
hentication"])

try to use another codec

Please see https://github.com/redisson/redisson/issues/1161


Falco restarted hundreds of times during a week of deployment

Hi, I am testing falco daemonset on our GKE cluster in GCP, it works great except that after a week of running, all the the falco pods have been restarted hundreds of times and it’s probably clogging the kublet’s rate limit to cause new pods from properly running (they kept crashing, delete falco daemonset solves the issue).
Perhaps the default rulesets are probably too intensive and too noisy for a typical k8s environment. I’ve read through falco rules wiki page but nothing jumps out for me to solve them. Can anyone give me some additional pointers to fine tune those default rules? Where should I start? Thanks.
K8s info:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.11-gke.1", GitCommit:"5c4fddf874319c9825581cc9ab1d0f0cf51e1dc9", GitTreeState:"clean", BuildDate:"2018-11-30T16:18:58Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

kubectl logs && kubectl describe pod Logs: https://gist.github.com/ye/0f4195faf3f80e7d4c8d618ae6b590b2

@ye are you still seeing this?

@mfdii yes, I am stilling seeing this behavior.
Here is a recent episode:
$ kubectl describe po falco-pqpdc
Name:           falco-pqpdc
Namespace:      default
Node:           gke-maven-stateless-pool-1512435801-f55a0382-7lxs/<IP_ADDRESS>
Start Time:     Thu, 07 Mar 2019 17:42:21 -0500
Labels:         app=maven-falco
                controller-revision-hash=764563707
                name=monitored-nodes
                pod-template-generation=1
                role=security
Annotations:    <none>
Status:         Running
IP:             <IP_ADDRESS>
Controlled By:  DaemonSet/falco
Containers:
  falco:
    Container ID:  docker://e6a22cdb403345411ee9af64c4de621caf4557959e4157502e8149f8aa8fe10d
    Image:         falcosecurity/falco:0.14.0
    Image ID:      docker-pullable://falcosecurity/falco@sha256:8176b851e5a6c2fb0662c32ab7ce18d59d0d8a896cd46844c810c6766b0c817c
    Port:          <none>
    Host Port:     <none>
    Args:
      /usr/bin/falco
      -K
      /var/run/secrets/kubernetes.io/serviceaccount/token
      -k
      https://kubernetes.default
      -o
      json_output=true
      -o
      program_output.enabled=true
      -o
      program_output.program=jq '{text: .output}'
    State:          Running
      Started:      Thu, 07 Mar 2019 18:17:24 -0500
    Last State:     Terminated
      Reason:       Error
      Exit Code:    139
      Started:      Thu, 07 Mar 2019 17:42:22 -0500
      Finished:     Thu, 07 Mar 2019 18:17:23 -0500
    Ready:          True
    Restart Count:  1
    Requests:
      cpu:     20m
      memory:  160M
    Environment:
      SYSDIG_BPF_PROBE:
    Mounts:
      /host/boot from boot-fs (ro)
      /host/dev from dev-fs (rw)
      /host/etc from etc-fs (ro)
      /host/lib/modules from lib-modules (ro)
      /host/proc from proc-fs (ro)
      /host/usr from usr-fs (ro)
      /host/var/run/docker.sock from docker-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from falco-service-account-token-hfplx (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          True
  PodScheduled   True
Volumes:
  docker-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:
  dev-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /dev
    HostPathType:
  proc-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:
  boot-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /boot
    HostPathType:
  lib-modules:
    Type:          HostPath (bare host directory volume)
    Path:          /lib/modules
    HostPathType:
  usr-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /usr
    HostPathType:
  etc-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /etc
    HostPathType:
  falco-service-account-token-hfplx:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  falco-service-account-token-hfplx
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/disk-pressure:NoSchedule
                 node.kubernetes.io/memory-pressure:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute
                 node.kubernetes.io/unreachable:NoExecute
Events:
  Type    Reason                 Age               From                                                        Message
  ----    ------                 ----              ----                                                        -------
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "proc-fs"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "boot-fs"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "docker-socket"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "usr-fs"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "dev-fs"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "etc-fs"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "lib-modules"
  Normal  SuccessfulMountVolume  36m               kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  MountVolume.SetUp succeeded for volume "falco-service-account-token-hfplx"
  Normal  Pulled                 1m (x2 over 36m)  kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  Container image "falcosecurity/falco:0.14.0" already present on machine
  Normal  Created                1m (x2 over 36m)  kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  Created container
  Normal  Started                1m (x2 over 36m)  kubelet, gke-maven-stateless-pool-1512435801-f55a0382-7lxs  Started container
[ye@mvnmac-058 falco (sysdig-falco)]$ kubectl logs -f falco-pqpdc
* Setting up /usr/src links from host
ls: cannot access '/host/usr/src': No such file or directory
* Mounting debugfs
Found kernel config at /proc/config.gz
* COS detected (build 10452.101.0), downloading and setting up kernel headers
* Downloading https://storage.googleapis.com/cos-tools/10452.101.0/kernel-src.tar.gz
* Extracting kernel sources
* Configuring kernel
* Trying to compile BPF probe falco-probe-bpf (falco-probe-bpf-0.14.0-x86_64-4.14.22+-8953a03c1317cdc6d882d1f17b7fe001.o)
* BPF probe located, it's now possible to start sysdig
Thu Mar  7 23:20:17 2019: Falco initialized with configuration file /etc/falco/falco.yaml
Thu Mar  7 23:20:17 2019: Loading rules from file /etc/falco/falco_rules.yaml:
Thu Mar  7 23:20:17 2019: Loading rules from file /etc/falco/falco_rules.local.yaml:
Thu Mar  7 23:20:17 2019: Loading rules from file /etc/falco/k8s_audit_rules.yaml:
Thu Mar  7 23:20:18 2019: Starting internal webserver, listening on port 8765
{"output":"23:20:23.718171130: Notice Namespace change (setns) by unexpected program (user=<NA> command=<NA> parent=<NA> host (id=host))","priority":"Notice","rule":"Change thread namespace","time":"2019-03-07T23:20:23.718171130Z", "output_fields": {"container.id":"host","container.name":"host","evt.time":1552000823718171130,"proc.cmdline":"<NA>","proc.pname":null,"user.name":null}}
{
  "text": "23:20:23.718171130: Notice Namespace change (setns) by unexpected program (user=<NA> command=<NA> parent=<NA> host (id=host))"
}
{"output":"{\"container.id\":\"host\",\"container.name\":\"host\",\"evt.time\":1552000823718176168,\"proc.cmdline\":\"<NA>\",\"proc.pname\":null,\"user.name\":null}","priority":"Notice","rule":"Change thread namespace","time":"2019-03-07T23:20:23.718176168Z", "output_fields": {"container.id":"host","container.name":"host","evt.time":1552000823718176168,"proc.cmdline":"<NA>","proc.pname":null,"user.name":null}}
{
  "text": "{\"container.id\":\"host\",\"container.name\":\"host\",\"evt.time\":1552000823718176168,\"proc.cmdline\":\"<NA>\",\"proc.pname\":null,\"user.name\":null}"
}

One question I have for the above log is that it's complaining /host/usr/src folder not existing (it's probably not in CoreOS image), but it seems that it's working (genreating log outputs in STDOUT). Is it okay to that falco pods restarted frequently? In this particular instance, I check the k8s events and pod logs, nothing really telling me why it restarted.

17 hours later, some of the pods have almost hourly restarts. The last log line that is non-json is a call to free(). Is that fishy?
$ kgpo -l app=maven-falco
NAME          READY     STATUS    RESTARTS   AGE
falco-6vjq9   1/1       Running   17         17h
falco-hsdpt   1/1       Running   7          17h
falco-jxbrr   1/1       Running   1          17h
falco-k85kz   1/1       Running   5          17h
falco-pqpdc   1/1       Running   15         17h
falco-qzh8g   1/1       Running   9          17h
falco-tmw8k   1/1       Running   10         17h
falco-xctvk   1/1       Running   17         17h
falco-z9c7r   1/1       Running   18         17h
falco-zrtzp   1/1       Running   6          17h
$ kubectl logs falco-6vjq9 -c falco --previous | tail -n 1
free(): double free detected in tcache 2

I'll let @mstemm or @gianlucaborello comment on the free messages. That's out of my depth.
Would you please let us know the following:

COS version
GKE version
# of average container in this env
rate at which containers churn in this environment

You can tune the number of events you're getting by changing the minimum priority for rules in the falco.yaml. If you're using the default falco.yaml it sets this to debug (which we should probably change). https://github.com/falcosecurity/falco/blob/dev/falco.yaml#L60

@mfdii thanks for your response. Here are the answers from my end:

COS version: cos-69-10895-138-0
GKE version: v1.10.4-gke.2
Number of average container in this env: ~40 pods, each pod has anywhere between 1 to 3 contains inside.
rate at which containers churn in this environment: roughly 1 restart per hour, some falco pods churns faster than that some slower

Here is excerpt output from kubectl get nodes -o wide (anonymized node identifiers and IPs)
$ kubectl get nodes -o wide
AGE       VERSION         OS-IMAGE                             KERNEL-VERSION   CONTAINER-RUNTIME
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
173d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2
212d      v1.10.4-gke.2   Container-Optimized OS from Google   4.14.22+         docker://17.3.2

Sorry. What rate do your application containers churn at, not the falco containers.

It's hard to estimate, our application pods aren't churn at a constant pace or have a regular pattern, we have deployments throughout the day, sometimes 3-5 times a day during work hours sometimes we don't deployment for a few days. I don't seem to find any pattern related to the application deployments to the best of my knowledge.

fixed in https://github.com/draios/sysdig/pull/1330

@mstemm @mfdii any plans to release this fix in a new version soon? Still waiting anxiously here after seeing the restarts in recent audit.
free(): double free detected in tcache 2
Btw, I've seen significantly reduced crashes on the COS version 69-10895 with 4.14.91+ kernel and together with Kubernetes version v1.12.5-gke.10 but they are still crashing. FYI.

We should have a release that fixes this out later this week. @mstemm is prepping some other changes that need to go out, and when he cuts a release, this will be picked up.

 The release page only list the previous version 0.14.0 https://github.com/falcosecurity/falco/releases. So does the Docker Hub page: https://hub.docker.com/r/falcosecurity/falco/tags
Please let me know how to get a pre-released falco build so that I can test it and confirm. Thanks!

@mfdii @mstemm any updates on a new release? I am still seeing 0.14.0 is the latest release on the release page here.

@mfdii fyi, been over 3 days since I last deploy the dev image builds of the falco, it hasn't had any crash yet.

Closing this as it appears to be fixed in dev.


api_service: Panic for incomplete pods

Environment
rkt Version: 1.7.0

What did you do?
rkt api-service &
rkt run --uuid-file-save=/tmp/uuid  quay.io/coreos/alpine-sh --exec=sh -- -c 'ls'
rm -f /var/lib/rkt/pods/run/$(cat /tmp/uuid)/appsinfo/alpine-sh/manifest
# run grpc ListPods(Detail: true) somehow

	/usr/lib/go/src/runtime/panic.go:464 +0x3e6
main.fillAppInfo(0xc82030d8c0, 0xc8203c8640, 0xc82032cdc0)
	/opt/build-rkt/gopath/src/github.com/coreos/rkt/rkt/api_service.go:450 +0xb85
main.(*v1AlphaAPIServer).ListPods.func1(0xc8203c8640)
	/opt/build-rkt/gopath/src/github.com/coreos/rkt/rkt/api_service.go:405 +0xc3
main.walkPods(0x7f81cc50f41e, 0xc8204f7a98, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/coreos/rkt/rkt/pods.go:145 +0x82b
main.(*v1AlphaAPIServer).ListPods(0xc82013ca88, 0x7f81cc50f1f0, 0xc82017b650, 0xc820146e40, 0xb, 0x0, 0x0)
...

What did you expect to see?
No panic!

I encountered this in the wild while running rktnetes is why I increased the priority; this doesn't only occur after manually messing with the pod directory. It's possible there's a more complex reason why the pod was in that state to begin with.
Other bits of possible interest: list-pods.go for easier repro, and a commit that fixes it. If I finish writing a functional test for it I'll have a PR with that soon.


Improve the Kafka websubhub example

Description:

$subject

Following tasks should be completed:

[x] Improve the scalability of websub subscribers by providing support to add multiple consumers (of the same subscription) into the same kafka consumer group.
[x] Incorporate mTLS to the connection between kafka cluster and hub.
[x] Add a new load-balancing service to the setup.

Completed this with following PRs:

https://github.com/ballerina-platform/module-ballerina-websubhub/pull/874
https://github.com/ballerina-platform/module-ballerina-websubhub/pull/876
https://github.com/ballerina-platform/module-ballerina-websubhub/pull/877


MultiPartBodyParser Refactor

Description
The refactor centers around the addition of an NSData extension function "components".  It operates similar to String.components where NSData can be split into an array of NSData elements using a separator.  In the case of MultiPart parsing, the separator is the boundary.
String components function:
  func components(separatedBy separator: String) -> [String] { ... }

New NSData components extension:
  func components(separatedBy separator: NSData) -> [NSData] { ... }

The new components function may be useful in other parts of Kiitura.
Motivation and Context
During development of MultiPartBodyParser.swift, there was a goal of an eventual refactor.  No functionality was changed.
How Has This Been Tested?
Tested on Mac and Linux.  A new negative test case was added as well.
Checklist:

[x] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

@dfirsht - Here is the refactor we spoke about for issue #438.  There was an initial Linux build failure which I fixed, however the last Linux build appears to have stalled (72ed16d).  Is there a way to attempt the Linux build again?

@dsperling I restarted it.

@dfirsht thanks.  That is more like it.

Hey we are actually moving all development to be PRs against master. Please reopen your PR against the master branch.


Wrong Python version with Ubuntu in Dockerfile

When building and running the docker container with WSL2, Ubuntu 20.04.6, Python 2 is the default version (i.e., /usr/bin/python is python2, python-config is python2-config). This breaks part of the Python scripts, e.g., test_general.py will not execute as it was written with Python 3 syntax. sst will query the detault Python version with python-config.
To make Python 3 the default version, the following changes to the dockerfile resolved the issue for me:+
RUN apt-get install --yes python python2 python3 python3-dev

RUN apt-get install --yes python-is-python3
...
RUN apt-get install --yes\
        python3-numpy

Thanks for raising the issue. Could you specify which DockerFile are you referring to?


Errors during JIT compilation of template for DashboardComponent: Opening tag "app-ui-help-tag" not terminated while running tests

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[x] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Our application is working fine with older versions of Angular v12 and below. Issue observed only with v13 and v14 upgrades. Issue observed only while running unit tests.
Description
We have a hybrid application (AngularJS and Angular), we keep the Angular version updated regularly and currently working fine on the v2 version.  Recently I tried to upgrade the application to v13, application upgraded successfully to v13 and working fine without any issues. But we are getting below exception while running unit tests for each of the components.
Note: This issue is only observed while running unit tests, serve is working fine. I tried to upgrade to v14, still it has the same issue.
🔬 Minimal Reproduction
NA

🔥 Exception or Error

 ng test wifi-aware --watch=false --reporters spec,kjhtml,coverage,junit --browsers=ChromeHeadlessNoSandbox --code-coverage --progress false

    Stylus usage is deprecated and will be removed in a future major version. To opt-out of the deprecated behaviour, please migrate to another stylesheet language.

11 07 2022 09:57:04.179:INFO [karma-server]: Karma v6.4.0 server started at http://localhost:9881/
11 07 2022 09:57:04.190:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency unlimited
11 07 2022 09:57:04.201:INFO [launcher]: Starting browser ChromeHeadless
11 07 2022 09:57:06.277:INFO [Chrome Headless 99.0.4844.74 (Mac OS 10.15.7)]: Connected on socket Uv0QiFWntPWc7I6tAAAB with id 98987548
Chrome Headless 99.0.4844.74 (Mac OS 10.15.7) LOG LOG: 'JQMIGRATE: Migrate is installed with logging active, version 3.3.2'
Chrome Headless 99.0.4844.74 (Mac OS 10.15.7) LOG: 'JQMIGRATE: Migrate is installed with logging active, version 3.3.2'
Chrome Headless 99.0.4844.74 (Mac OS 10.15.7) WARN LOG: 'JQMIGRATE: jQuery.isArray is deprecated; use Array.isArray'

  DashboardPerformanceComponent
    ✗ should test parseClientsByAvgDataRateResponse
	Failed: Errors during JIT compilation of template for DashboardPerformanceComponent: Opening tag "app-ui-help-tag" not terminated. ("export default "[ERROR ->]\n\n\n[ERROR ->]\n\n\n[ERROR ->]\"): ng:///DashboardPerformanceComponent/template.html@0:110, Unexpected closing tag "div". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags ("tag>\n[ERROR ->]\n\n    \n"): ng:///DashboardPerformanceComponent/template.html@0:204, Opening tag "app-body-container" not terminated. ("iv #shadowElement class=\"mojo-dynamic-height-header mojo-shadow-on-scroll padding-top-15\">\n[ERROR ->]\n    \n        "): ng:///DashboardPerformanceComponent/template.html@0:212, Opening tag "div" not terminated. ("adow-on-scroll padding-top-15\">\n\n    [ERROR ->]\n        \n         "): ng:///DashboardPerformanceComponent/template.html@0:272, Opening tag "div" not terminated. ("app-body-container [shadowElement]=\"shadowElement\">\n    \n        [ERROR ->]\n            \n           "): ng:///DashboardPerformanceComponent/template.html@0:313, Opening tag "div" not terminated. (" class=\"container-fluid\">\n        \n            [ERROR ->]\n
I verified that HTML markup is proper in templates.
🌍 Your Environment

Angular CLI: 13.3.8
Node: 16.15.1
Package Manager: npm 8.5.5
OS: darwin x64

Angular: 13.3.11
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... upgrade

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1303.8
@angular-devkit/build-angular   13.3.8
@angular-devkit/core            13.3.8
@angular-devkit/schematics      13.3.8 (cli-only)
@angular/cdk                    12.2.2
@angular/cli                    13.3.8
@schematics/angular             13.3.8 (cli-only)
ng-packagr                      13.3.1
rxjs                            7.5.5
typescript                      4.4.4

I tried switching between typescript version 4.4 and 4.6 (default installed with v13), still no luck.
Also, I tried clearing node_modules multiple times and install clean, issue was not resolved.
I came across below issues, and tried multiple solutions from there, still no luck.
https://github.com/angular/angular-cli/issues/16873
https://github.com/angular/angular/issues/34387

This would need a minimum reproduction, as it's not otherwise clear what is going on here.

The project is internal to our organization. I will try to create reproduction steps on fresh repository if possible. But can we have some guess where we are going wrong?

Hi @swapnilfarande
Custom builders or issues that arise from customizing the webpack configuration are not supported by the Angular team.

Hi @swapnilfarande
Custom builders or issues that arise from customizing the webpack configuration are not supported by the Angular team.

I updated Angular version for 7 to 14. I was using @angular-devkit, and after updating I was getting error of sass-loader, that an additional loader is required. when I used  Custom webpack it resolved this error. And now I am getting Error that
Uncaught Error: JIT compiler unavailable     at Ya (main.js:1:1446217)     at Module.z3 (main.js:1:1603347)     at main.js:1:4524     at 98133 (main.js:1:4785)     at r (runtime.js:1:147)     at 13098 (main.js:1:352008)     at r (runtime.js:1:147)     at Me (main.js:1:2250429)     at main.js:1:2250450     at s (runtime.js:1:4115)
I have tried so many solutions for my Problem but nothing worked.
I have uploaded my first error (which I was getting before Using Custom-webpack) and other detail here
https://stackoverflow.com/questions/73078680/you-may-need-an-additional-loader-to-handle-the-result-of-these-loaders-angular

Closing as custom Webpack configurations are not supported by the Angular team.


See if we can put the example tests under /doc/examples

A symlink of doc/examples/vendor to src/server/vendor should do it I think. And the client code is 'vendored' via symlink under src/server/vendor so that should get use the right client code as well

What's the motivation for this?

The short answer is just my OCD :-P
Organizationally, I think it makes sense to keep the tests for examples alongside the examples.
But doing this and trying some of the obvious things for vendoring it wasn't super straightforward. Also I think there are some edge cases w running all tests w vendoring / symlinks / and the Makefile.
Sooo .... I don't think its worth the trouble.


scroll_with_delta doesn't work

Describe the bug
scroll_with_delta doesn't seem to work.
To Reproduce
Steps to reproduce the behavior:

Create an app with eframe.
Copy the scroll_with_delta example from documentation.
Click Scroll down button.
See that nothing happens.

use eframe::egui::{self, Vec2};

fn main() -> Result<(), eframe::Error> {
    eframe::run_native(
        "My egui App",
        eframe::NativeOptions::default(),
        Box::new(|_cc| Box::new(MyApp {})),
    )
}

struct MyApp {}

impl eframe::App for MyApp {
    fn update(&mut self, ctx: &egui::Context, _frame: &mut eframe::Frame) {
        egui::CentralPanel::default().show(ctx, |ui| {
            let mut scroll_delta = Vec2::ZERO;
            if ui.button("Scroll down").clicked() {
                scroll_delta.y -= 64.0; // move content up
            }
            egui::ScrollArea::vertical().show(ui, |ui| {
                ui.scroll_with_delta(scroll_delta);
                for i in 0..1000 {
                    ui.label(format!("Item {}", i));
                }
            });
        });
    }
}

Expected behavior
Content scrolls down.
Screenshots

video
Desktop (please complete the following information):

OS: GNU/Linux

It looks like this is the code that handles the scroll_delta:
https://github.com/emilk/egui/blob/f94187ab718e8513084e591fcef73356a4971d6b/crates/egui/src/containers/scroll_area.rs#L700-L716
It only takes the delta into account if the pointer is inside the scroll area, so the example will never work, since you have to click a button that is outside the area. If I remove this condition, it works as intended. I don't know why it is written this way, and both the code above and the scroll_with_delta method are untouched for almost a year. I also tested with the commit that originally introduced the method (676ff047e9c), and it didn't work there either. If there is no other reason for the && ui.rect_contains_pointer(outer_rect) condition, I supposed it could just be removed and the method will be fixed. But I'll wait to see if anyone has anything to say about it, and do some tests to see if it breaks anything else.
I suspect that since the scroll_delta is set in the Context, and is therefore global to the whole UI, the idea is that if there is more than one scroll area, the one that is hovered by the mouse would be the one to use the delta. But I guess if you set it from within the show() method of the scroll area that you want to manipulate, that will not be a problem. But I'm not sure I fully understand how this is supposed to work.


Implement python 2.7 support

As of now this codebase only works for python >=3.6. Steps to fix this:

[ ] Some maintenance (e.g. from __future__ import print_function) need to be done in some places to make things work
[ ] Travis CI build instructions need to be updated to include python 2.7 builds

Resolved in #20


Is a seccomp profile active for the containers?

Are the containers on Azure Container Instances constrained by a seccomp profile as in the default docker setup?
If so, is it possible to modify or disable (unconfined) that profile?

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

ID: f275d757-c0ac-498e-cf5f-b2aa1b6aade7
Version Independent ID: 4b198221-09d2-6d0d-69ae-972745621e50
Content: Security for container instances - Azure Container Instances
Content Source: articles/container-instances/container-instances-image-security.md
Service: container-instances
GitHub Login: @dlepow
Microsoft Alias: danlep

#reassign macolso

I am also interested in the answer to this question


fix: Token group matches necessary token group interface

Problem: Current account does not comply with token extension design.
Use TLV helpers to setup the account, keep the anchor account shell for convenience. Technically we could have more extensions in that one single account.
https://github.com/solana-labs/solana-program-library/tree/master/token-group/interface

This makes it easier to do the client-side fetching of the group fields right?
Also, wouldn't it be necessary to have the same setup for the Group Member Pointer Extension?

Not sure this would be much of an improvement immediately, though it would make the migration from this to in-mint Group/GroupMember accounts easier for clients. Do you have an example of how this would simplify things on client side right now?


Git User's Survey 2016 has been closed

I'm sorry for not sending this issue request as I was closing the survey.
The banner about the survey should be removed.

No problem. Thanks for reminding me.


Visual studio code workspace settings for java

Signed-off-by: Julien Vermillard<EMAIL_ADDRESS>

you need the official java extension (IIRC there is a popup proposing to install the first time you open a java file)

I need to re-check but the last time I tried that it was not working. Apparently it a bug which was fixed in vscode long time ago :thinking:


Updating DAQ release to R5-V5.0

This has been installed on the TTS and appears to be working. I think we're ready to pull, change the puppet environment and close the IT Jira. I can do as many of those things as you like.


SIMD-0207: Raise block limit to 50M

Problem

https://github.com/solana-foundation/solana-improvement-documents/pull/207

Summary of Changes

Add feature to the feature set for raising block limits
Clean up old limit justification(s)
Add function to get new limits for SIMD-0207
Add feature-activation path for SIMD-0207

Fixes #

Small patch to raise limits for https://github.com/solana-foundation/solana-improvement-documents/pull/207.
There are 34 lines of test, so "functional" patch is small, and I think should be backported so we can raise chain capacity slightly at a much earlier date.


How to scale Dagger in production?

Problem
We haven't conclusively answered the question: "what is the best way to scale Dagger in production?". This is in part because there is a wide variety of requirements and preferences, depending on the use case and constraints.
So far there are 2 competing approaches: horizontal scaling and vertical scaling. We have not conclusively decided which one is better, and why.
Solution
Using our collective experience running Dagger in production since the cloak release (0.3):

discuss the different ways to scale Dagger in production
debate horizontal versus vertical scaling, and which is the best for which situation
reach a consensus on best practices
document them clearly
If necessary, change the design and architecture to fit the best practices

Conversation starter
Horizontal scaling vs. vertical scaling: which is best, and why?
Discuss 😁

For those of us that can't use dagger cloud yet, is horizontal scaling even an option?
FWIW, we have a massive Jenkins cluster/s in Kubernetes and we still only scale vertical as that's the only option AFAIK. We find it sufficient for 99% of CICD jobs. There are some exceptional cases that run into issues with running out of resources. The usual culprits like big monorepos.

For those of us that can't use dagger cloud yet, is horizontal scaling even an option?
FWIW, we have a massive Jenkins cluster/s in Kubernetes and we still only scale vertical as that's the only option AFAIK. We find it sufficient for 99% of CICD jobs. There are some exceptional cases that run into issues with running out of resources. The usual culprits like big monorepos.

I'm very interested in your vertical scaling setup.

Do all Jenkins runners send work to a single Dagger host? Or is it a 1-1 mapping where each Jenkins runner gets its own Dagger host, and each jenkins/dagger host pair are scaled vertically together?
How is the right job dispatched to the right host?
How do you manage Dagger cache data?

For those of us that can't use dagger cloud yet, is horizontal scaling even an option?
FWIW, we have a massive Jenkins cluster/s in Kubernetes and we still only scale vertical as that's the only option AFAIK. We find it sufficient for 99% of CICD jobs. There are some exceptional cases that run into issues with running out of resources. The usual culprits like big monorepos.

I'm very interested in your vertical scaling setup.

Sorry I should have clarified. My statement was regarding our current non-dagger setup. Our scaling also is not automatic. Cloudbees Jenkins Core works by distributing it's workloads between many kubernetes nodes. Each job is basically a Pod (Agent) and multiple containers are spun up within that agent to get the job done. The agent gets a static amount of resources based on a user "t-shirt" sizing config (sm, x, xl etc.). Since it's a single pod it never spans beyond a single Node and is resource limited based on the Node size.
I have run dagger in this setup. What I did was use a docker-in-docker (dind) image to pull down the dagger engine at runtime and perform the given tasks. There is basically no cache. All storage is ephemeral as are the agent pods. This is not a very efficient way to run dagger to say the least but right now that's the only option we have. We are starting to provision "caching" by pushing and pulling from S3. Even that won't be great for dagger but I am planning to utilize it to see what sort of speed gains I can get.

You can control parallelism with the --parallel flag, defaults to GOMAXPROCS(1)
These nodes are pretty expensive, but they get automatically shut down when not in use. Still, i don't know if they are used very efficiently. They're sized to be able to perform tasks like this when requested, but most of the time they're not really being used even at 50% capacity. That's where I think horizontal scaling would really shine.

FWIW, k8s has had in-place pod resource updates in alpha since v1.27, so it's now possible to write custom triggers to scale vertically in-place. This would prove to be even easier when support is added to the native Vertical Pod Autoscaler CRD as it will supposedly become the default resize mechanism.

@gerhard summarized a lot of the tradeoffs I would have mentioned 🙂 So I'll just add some more thoughts

For users already invested in a horizontal scaling architecture, they would most likely prefer to not have to re-architect to get caching working with Dagger optimally.

I realize this is debatably a different question than "what is the ideal architecture", but it feels like an important consideration nonetheless. Being able to meet users where they are is always nice, all else being equal.

Also, with some handwaving, you could also argue that the "set of developer laptops + CI" are a form of horizontal scaling too 🙂 Just in that it's compelling if cache and state can be shared between them.

I'd actually view cloud cache as somewhat orthogonal to vertical vs. horizontal scaling. Basically, vertical scaling is not contradictory with a remote cloud cache.
Even though it's not 100% reliant on it like the horizontal scaling case, remote caching still offers some benefits:

When you need to provision a new vertical instance (i.e. blue-green deploy, etc.), it's nice if you don't have to throw out all your cache along the way.

There's certainly plenty of shenanigans you can try to do this without a remote cache, but they devolve very quickly in the details into lots of complications+tradeoffs.

Even though vertical instances rely more on local cache, local cache needs to be pruned, so remote cache can still have a role to play as "tier 2" cache for data that has been pruned locally.

This is definitely not going to be applicable to every use case by any means, since obviously remote cache needs pruning eventually too.
It comes down to economics of remote storage costs vs local disk costs (which in turn is often tied into the size of the instance, at least using AWS as an example), which is obviously quite complicated.
It also involves the type of data the user works with. E.g. I'd suspect that users working with lots of huge files might benefit from this more often, especially if their needs in terms of disk space/cpus ratio is fairly high.

And just generally speaking hypothetically, the features a cloud cache offers expand out to things completely independent of vertical vs. horizontal architecture. This probably gets out of scope of this discsussion, but very briefly, it can be an important backbone for various features around:

debugging
sharing cache between CI and local development
reproducibility/supply-chain-security
performance improvements like lazy filesystem image pull-through cache
etc. etc. Can expand if needed.

Point is, I just wouldn't make the strong association of horizontal scaling == cloud cache, vertical scaling == local cache.

I'd actually view cloud cache as somewhat orthogonal to vertical vs. horizontal scaling. Basically, vertical scaling is not contradictory with a remote cloud cache.

Agree on that point. Additionally, I believe the problem can be split/clarified further:

Ephemeral vs Persistent storage (as @gerhard mentioned):  Horizontal vs Vertical has no bearing on this -- one can have an ephemeral "vertical" instance or persistent horizontal instances
In the case of horizontal vs vertical, the perceived advantage of vertical is the persistency, but that can be achieved using horizontal scaling as well
The sole difference between vertical and horizontal is the (local) cache hit ratio. With 1 node that's going to be 100%. With 2 nodes, 50% and so on
Local cache will eventually spread to all nodes: in a cluster of N nodes, the cache will eventually spread everywhere after N builds (and the hit ratio eventually converging to 100%)

For users already invested in a horizontal scaling architecture, they would most likely prefer to not have to re-architect to get caching working with Dagger optimally.

Agreed as well -- IMHO it's a slider. Vertical scaling is a special case of horizontal with 1 node and 100% cache hit. Works for some, doesn't for others.

It's true that "horizontal vs vertical" doesn't adequately capture every dimension of the choice we are facing. I do think there is a binary choice to be made. Of course there is further refinement, variations etc. But fundamentally I believe there are two major architectural patterns, and you either choose one or the other. I am now unsure what to call them.
The dimensions where they differ are:

Persistence of local storage: ephemeral vs. long-lived?
Job scheduling: one big compute pool, or discrete mapping of certain jobs to certain machines?

I think (as explained in other comments) how CPU is added to the overall infra (growing existing machines vs. adding more) is not the right dimension because both are potentially applicable in either architecture.

Quoted from @gerhard:
The biggest downsides of this vertical scaling approach is having an instance which we need to pay for even when it is not being used. A few solutions which are known to help contain this [...]

I would also add another solution: stopping / resuming the dagger engine instance on demand (it does not have to be the same instance over time, as long as the local cache fits on an EBS volume which can be the only resource you persist).
About vertical scaling, it's worth considering that over time, given concurrency and load increase, you may want to have several dagger-engine machines that you round-robin, in this case like Andrea mentioned, it impacts the cache-hit ratio. And doing this means going back to horizontal scaling, but without a remote cache.
Eventually what we should extract from all of this conversation, is the best production setup for most users. And I see a lots of compelling arguments to always start from a dagger-engine with its cache locally accessible.

as long as the local cache fits on an EBS volume which can be the only resource you persist).

@samalba This may seem like a small detail, but it's a good example of the sometimes unobvious tradeoffs here so worth noting: if you want an EBS volume that is both fast and has a lot of space, you will be paying a lot of money for it. And you will be paying for it as long as it exists, whether it's attached to any running instance or not.
This is as opposed to ephemeral instance storage which is typically fast nvme + comes with the instance itself. The tradeoff there obviously being that it's ephemeral.

TL;DR: For us, the only way to scale is horizontally.
I would like to share my thoughts. At my company, we're considering daggerizing our CI pipelines for our embedded Linux device software, including all involved lifecycle tools and processes, such as platform components, desktop applications, testing, and more. Our environment is bilateral for the most parts: On one side, we have quick, smaller tasks such as running a linter or building documents. On the other side, we have the heavy-weight jobs such as building our embedded Linux distribution, synthesise FPGA bitstreams, and training AI models.
For us, stability, reliability, reproducibility and performance are the most critical aspects of our CX infrastructure.
As @gerhard pointed out, for software building, it mostly comes down to how you handle caching. For smaller jobs, it's often faster to simply rebuild, as compute can be quicker than restoring the cache from remote storage, even with good network latency and throughput. For larger tasks, many tools have their own independent caching mechanisms. For instance, ccache is used for C/C++, Conan to manage pre-built packages, and download and sstate caches for Yocto projects. For these builds, network latency and throughput are equally as important as compute performance.
Furthermore, caching can be complex and may lead to inconsistent results if your dependency chain is not fully locked and the cache is not shared between all engines on all nodes. To avoid unreliable build results, we currently opt for ephemeral build agents and stateless pipelines with one engine per build job as described by @gerhard. This way we keep our nodes simple (and thus our cluster easily horizontally scalable) and our builds idempotent. This also helps us avoid conflicts with locked cache volumes.
In my previous company, we used KEDA to spin up a new pod on an AKS when a job is waiting in the build queue, where this pod included both an agent and buildkit engine containers. This allowed us to scale to zero and reduce operational costs. We also defined three different sizes of agents: S, M, and L, and predetermined which job requires which agent size (this is what @shykes mentioned here). We only use the sizing to reserve resources on the cluster (i.e., requests), without imposing any limits. This strategy helps us avoid overprovisioning the nodes and distribute the builds more evenly. A previous approach involved monitoring each build on the cluster and optimizing the parameters accordingly. However, this approach was unsuccessful as the performance deteriorated over time.
We discovered that vertical scaling is quite limited in software building (even without considering the physical limits of the hardware). As mentioned earlier, we use Yocto to build our embedded Linux, which is essentially a build framework that builds a complete Linux distribution from source. It maximizes performance by parallelizing the build task as much as it can. We often use it to benchmark the build performance of various systems, and we've gained substantial experience by benchmarking many different solutions, including from multiple cloud providers. When evaluating performance, we found the following two aspects most important:

Parallelization on a single machine or node is limited, and beyond a certain point, builds begin to cannibalize each other.
Most software builds still have numerous single-thread bottlenecks. With today's hardware generation, we've found that single-core performance is more crucial than the number of cores. For instance, a consumer-grade 16-core CPU with a high clock speed can be 20-30% faster than a 32-core or 64-core server-grade CPU running the same build. However, having just 16 cores basically only allows us to run a single build job on one node.

Thus, vertical scaling, if you can call it such here, is essentially about choosing the right hardware for our nodes in the first place and scale horizontally.
Looking at comparable software like Docker BuildX, it appears they adopt a horizontal scaling approach.
This, however, only covers our CX infrastructure so far. In the second scenario, we want our developers to use the same cluster to remotely build their local changes. Currently, we achieve this by running a pod for each user indefinitely. Since the engine caches can grow indefinitely, we wipe them periodically. It would be great if we could implement a similar scale-to-zero approach. For example, when running Dagger locally, the CLI creates a local engine container if one doesn't already exist. Ideally, we'd like to replicate this process for a remote K8s cluster, such as spinning up a job pod on demand that shuts down and is removed once the build has completed.

Also an aspect that hasn't been mentioned above that matters a lot for using tools in the corporate environment especially for initial PoC and potential migration path is that to my understanding compared to the dagger engine, the Cloud Cache is not open source and I can't self-host it e.g. to use it with internal GitLab runners. So scaling horizontally (multi-node) is not easily available. Ideally there would be an integration to use "external cache" with facilities already provided by GitLab (or other providers).

@Rots yes that is something we are actively developing. We have lowered the priority of our commercial cache offering- we only built it to fill a feature gap in the first place, but didn't anticipate how quickly enterprise deployments started happening. This makes BYOS more important. So we're prioritizing that :)

We were talking with @nadirollo today, and the following was mentioned:

This means a single Dagger Engine shared among all CI runners. The requirements for this Dagger Engine instance are: fast network (10Gbit or more) with low latency to clients (sub 1ms RTT)

I would like to expand on: sub 1ms RTT
There is a constant, streaming data exchange between the CLI and the Engine. It looks like this:
https://github.com/user-attachments/assets/c53daf03-e7db-494d-8ed6-fc575f76c166
The higher the latency between the CLI and the Engine, the slower this exchange becomes. Also, the CLI usually sends all the source code to the Engine - including the parent directory in certain cases (see https://github.com/dagger/dagger/issues/8395 for more details) - which means that there could be a lot of data exchanged and slow networks will result in a slow Dagger experience.
While this has been mitigated since v0.13.0 (September 11, 2024), CLI to Engine connections used to timeout after 1s: https://github.com/dagger/dagger/pull/8328. We are still thinking about a longer-term solution which would make things more performant for local Engines, and still support distant Engines (1s+).
In a nutshell, the 1ms RTT is NOT a hard requirement. With the latest improvements, the Engine could be 1s away and everything would still work. You will probably notice some slow-down when the Engine is more than 100ms away from the clients, but I don't think that the experience will be terrible.

I am going to update my original comment so that it reflects all the changes since January 2024.


BUG: bool data type not converting, when it should

Hello,
This resolves (for me at least) #208.
I have a MSSQL table with a bit data column. In odo, we are converting that to bool, which is fine. However, bool types throw an error here. I'm not an expert on what is supposed to be going on here, but this gets it to work for me.
Thanks.

The issue here is that numpy does not have support for Option(bool) so we cannot convert that type. If your dataset has NULL, numpy cannot store that in a bool field.

@llllllllll Ahhh...
Should I close this then? Or is there a better way?
Really the usecase is that I have a MSSQL database that I read from with BIT fields. Its probably safe assuming that that when NULL implies False and I'd like odo/blaze to assume as much, even with a warning.
Would the blaze ecosystem be OK with a patch that automatically assumed this, but maybe throw an error? Maybe this is an odo behavior?

Actually I may have missed something, but this seems to work now when I have odo=0.5.1. It coerces bits to False when they are NULL which is fine by me.
Closing, and thanks to whoever/whatever fixed this.

Weird, I know there was some work in in that edge but I didn't think the mssql stuff got updated. I am not totally sure I support the current behavior, but only because it makes it easy to not realize that you actually had a bunch of NULLs in your data. I do agree that if you needed to pick, False is a better default, but it is not hard to make it explicit. With blaze you could do: bz.transform(tbl, col=tbl.col.coalesce(False)) which would always do the right thing and be explicit about any conversions.
I don't feel so strongly that I want to go change this right now but I don't know if this was an intended change. Right now the MSSql backend is not run with automated testing so it is hard to make sure the behavior stays the same.

@llllllllll I'm happy to attempt to write some testing code, if someone can give hints. Its not obvious to me how to test MSSQL...
I'd appreciate some clues.

We can probably use mostly the same set of tests for postgres or sqlite. What I don't know is how we would get an database available for travis to use.

@llllllllll I'd guess the answer w.r.t. travis is "no". From the brief amount of experience I have trying to get a *nix client to talk to MSSQL, its an absolute nightmare.
With that said, appveyor appears to support it, but the question would be would the odo team want to add appveyor testing? I'm aware that appveyor can be very messy...

I have worked with appveyor before and don't find it to be too much of a hassle. I am not sure who has access to enable the github hooks for appveyor for odo but if someone wanted to write an appveyor file I wouldn't mind adding it. I will open an issue on odo and xref this one.


avoid UserWarning: Unknown type for SavedVersions

This warning message appears when the file is read, so it cannot be modified to prevent it from appearing.


dcterms link to terms.tdwg.org

Noticed that the linkes in "Comments" for the dcterms point to the correct term names but prefixed by "dwc" instead of "dcterms". The links thus does not work. Eg. http://terms.tdwg.org/wiki/dwc:type should be http://terms.tdwg.org/wiki/dcterms:type
I have also submitted a corresponding proposed update to the document: dwc/build/config/terms.csv
I assume the terms.tdwg.org links originates from that document?

See: https://github.com/tdwg/dwc/pull/183

In the pull request is also proposed adding "dcterms" prefix to the term names in the navigation overview. Eg: "dcterms:type | dcterms:modified | dcterms:language ..." instead of "type | modified | language | license | rightsHolder | accessRights | bibliographicCitation | references".

Hi @dagendresen, thanks for the effort!

Regarding the correct links: www/guides/index.html is generated automatically from (amongst others) dwc/build/config/terms.csv. So I ran build.py on your updates in #183 and those are now updated. The guide is never maintained manually.

Regarding prefixing term labels with dcterms: in the navigation, we already decided not to do this to make it more easily readable (cc @tucotuco). We did the same for dwciri. The anchor link itself does include the domain name to uniquely point to the correct term:

type

Sidenote: this type of updates on the layout should be done in build/config/index.tmpl, which is also used by the build script to render the quick reference guide. 👌


Test case failing due to :Error: No Mock online

`kamrink@kamrink-ub:~/Desktop/Projects/orange_gassistant_bot$ npm test

<EMAIL_ADDRESS>test /home/kamrink/Desktop/Projects/orange_gassistant_bot
jasmine

Started
(node:21088) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: No Mock online
got Message: undefined
FF
Failures:

TestMyBot Sample Conversation Test Suite should answer to hello
Message:
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
Stack:
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
Message:
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
`

TestMyBot seems to lack configuration. How does your testmybot.json look like ?

{
"botium": {
"Capabilities": {
"PROJECTNAME": "gassistant-bot",
"FACEBOOK_API": true,
"FACEBOOK_WEBHOOK_PORT": 3000,
"FACEBOOK_WEBHOOK_PATH": "webhook",
"CLEANUPTEMPDIR": false,
"STARTCMD": "node index.js"
},
"Envs": {
"NODE_TLS_REJECT_UNAUTHORIZED": 0,
"NODE_ENV": "dev"
}
}
}

I have tried with both 5000,3000 port

Please enable logging ("export DEBUG=botium*,testmybot*") and attach the log output

Any news?


H2 database support fails when H2 is started with MODE=MSSQL

In Registry.java there is a line regarding H2 database:
if (dbProduct.equals("h2") && "INFORMATION_SCHEMA".equals(rs.getString("TABLE_SCHEMA"))) continue; //skip h2 INFORMATION_SCHEMA table columns.
In MSSQLServer compatibility mode this table does not exist resulting in an exception:
Column "TABLE_SCHEMA" not found [42122-185] 	at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) 	at org.h2.message.DbException.get(DbException.java:179) 	at org.h2.message.DbException.get(DbException.java:155) 	at org.h2.jdbc.JdbcResultSet.getColumnIndex(JdbcResultSet.java:3120) 	at org.h2.jdbc.JdbcResultSet.get(JdbcResultSet.java:3208) 	at org.h2.jdbc.JdbcResultSet.getString(JdbcResultSet.java:302) 	at com.mchange.v2.c3p0.impl.NewProxyResultSet.getString(NewProxyResultSet.java:908) 	at org.javalite.activejdbc.Registry.getColumns(Registry.java:328) 	at org.javalite.activejdbc.Registry.fetchMetaParams(Registry.java:302) 	at org.javalite.activejdbc.Registry.init(Registry.java:140)

(Fixed mode string in title to be MSSQLServer)

@Garagoth , do you know what to look for in H2 for a case like that?

Fixed in my fork. Column name is "TABLE_SCHEM" according to the javadoc.
@ipolevoy, I can push this to master after today's release.

This is fixed now in version 1.4.11-SNAPSHOT.

Wanted to test it, but build fails during tests:
testNumericValidator(org.javalite.activejdbc.ValidatorsTest)  Time elapsed: 0.002 sec  <<< ERROR! org.javalite.test.jspec.TestException: Test object: java.lang.Integer == <1> and expected java.lang.Integer == <0> are not equal, but they should be.

Works fine.


About Section Responsiveness added

issue no #797
I have added fully responsiveness to about section with text and size of big round and also with yellow background in that text shown now all things under about section is responsive.
For Large Screen

For Medium Screen

For Small Screen

@Kalivarapubindusree @Its-Aman-Yadav Please check it and merge !


More details on valid values for multicast and clone session ids

Based on the PSA spec.
Fixes #44

@jafingerhut thanks for the review.
There is some information about where the mapping comes from in the spec already:

The first argument to the @p4runtime_translation annotation is a URI that indicates to the P4Runtime server which numerical mapping - provided by the out-of-band switch configuration mechanism - to use to translate between the SDN value and the dataplane value. The second argument is the bitwidth of the SDN representation of the translated entity (32-bit in the case of ports).


Rewrite the .NET Uninstall Tool page

Summary

Single page split into multiples.
Rewrote CLI command content into individual pages.
Updated CLI reference style.
TOC update and redirect.
Used macOS/Windows pivots

Fixes #40883
@tdykstra

Internal previews

📄 File
🔗 Preview link

docs/core/additional-tools/uninstall-tool-cli-dry-run.md
docs/core/additional-tools/uninstall-tool-cli-dry-run

docs/core/additional-tools/uninstall-tool-cli-list.md
docs/core/additional-tools/uninstall-tool-cli-list

docs/core/additional-tools/uninstall-tool-cli-remove.md
docs/core/additional-tools/uninstall-tool-cli-remove

docs/core/additional-tools/uninstall-tool-overview.md
docs/core/additional-tools/uninstall-tool-overview

docs/core/install/remove-runtime-sdk-versions.md
docs/core/install/remove-runtime-sdk-versions

I put these questions in email to the product team, but I'm going to merge this now and follow up with changes, if required.


expected output from nodes.get_components() when ignore?

I want to confirm expected output with nodes.get_components() when using the ignore keyword.
https://github.com/uscuni/sgeop/blob/33104e84ff1866f1522540e159ecbf1ee5cce5be/sgeop/nodes.py#L85
In [1]: import geopandas, shapely, sgeop
   ...:
   ...: p1, p2, p3 = shapely.Point(1,1), shapely.Point(2,2), shapely.Point(3,3)
   ...:
   ...: line_1_2 = shapely.LineString((p1, p2))
   ...: line_2_3 = shapely.LineString((p2, p3))
   ...:
   ...: print(sgeop.nodes.get_components([line_1_2, line_2_3]))
   ...: print(sgeop.nodes.get_components([line_1_2, line_2_3], ignore=geopandas.GeoSeries([p2])))
[0 0]
[2. 3.]

I would think, intuition would be for the second output to be [0. 1.]. I am sure there is a reason we the [2. 3.] output, but I am not sure what it is. Maybe something later with artifact identification?

This is expected. I need labels of connected components. But when there is a node we need to retain, that needs to split the component in two. The easiest way of doing so is to drop that node from graph creation. That way line_1_2 and line_2_3 are not seen as neigbbors as they no longer have a point in common and their component labels are different. If I keep the node there, they are connected via this component and have the same component label.
If it is 0, 1 or 2, 3 does not matter much in practice. The reason this shows up here is that the graph is based only on stuff that has a potential to form a component and to ensure that we get labels for everything, we fill the missing values with a rande starting from max label value + 1. so 0, 1 becomes 2, 3. Expected.

Great explanation!


EPIC: Support for teachers & students

As a teacher, I want to write my own exercises.
As a student, I want to solve exercises.
As a student, I want to give my professor information about my progress

Possible tasks

documentation on how to set up exercises with exercise structure and tests, exercise_info.yaml, test, hint (if it gets implemented), order of exercises, ...
command to generate exercise_info.yaml?
documentation: forking repo, basic github guide -> pushing changes so professor can check progress
command to generate summary of progress (progressbar, file of current exercise or progressbar, finished exercises, current exercise)

https://medium.com/@evaGachirwa/running-python-script-with-arguments-in-the-command-line-93dfa5f10eff


TypeError: Cannot read property 'PROCESS_ASSETS_STAGE_ADDITIONS' of undefined when using speed-measure-webpack-plugin

As soon as I add the smp.wrap(..) around my webpack config, I am getting the following exception:
(node:29480) [DEP_WEBPACK_COMPILATION_NORMAL_MODULE_LOADER_HOOK] DeprecationWarning: Compilation.hooks.normalModuleLoader was moved to NormalModule.getCompilationHooks(compilation).loader
[webpack-cli] TypeError: Cannot read property 'PROCESS_ASSETS_STAGE_ADDITIONS' of undefined
    at Proxy.<anonymous> (C:\proj\app\node_modules\copy-webpack-plugin\dist\index.js:462:45)
    at C:\proj\app\node_modules\speed-measure-webpack-plugin\WrappedPlugin\index.js:52:19
    at Hook.eval [as call] (eval at create (C:\proj\app\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:5:1)
    at Hook.CALL_DELEGATE [as _call] (C:\proj\app\node_modules\tapable\lib\Hook.js:14:14)
    at Compiler.newCompilation (C:\proj\app\node_modules\webpack\lib\Compiler.js:990:30)
    at C:\proj\app\node_modules\webpack\lib\Compiler.js:1033:29
    at eval (eval at create (C:\proj\app\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:10:1)
    at C:\proj\app\node_modules\speed-measure-webpack-plugin\WrappedPlugin\index.js:44:9
    at Proxy.<anonymous> (C:\proj\app\node_modules\webpack\lib\DllReferencePlugin.js:80:12)
    at C:\proj\app\node_modules\speed-measure-webpack-plugin\WrappedPlugin\index.js:40:16

As you can see, we are using the copy-webpack-plugin.
Without the smp.wrap(...), everything works as expected.
The environment is:

node v12.19.0
webpack 5.16.0
copy-webpack-plugin 7.0.0
webpack-cli 4.4.0

same situation

same situation

[webpack-cli] TypeError: Cannot read property 'PROCESS_ASSETS_STAGE_ADDITIONS' of undefined

[webpack-cli] TypeError: Cannot read property 'PROCESS_ASSETS_STAGE_ADDITIONS' of undefined

Relates to https://github.com/stephencookdev/speed-measure-webpack-plugin/issues/149

Relates to https://github.com/stephencookdev/speed-measure-webpack-plugin/issues/149

Getting the same error with:

node v14.10.0
webpack v5.18.0
webpack-cli v4.4.0

Getting the same error with:

node v14.10.0
webpack v5.18.0
webpack-cli v4.4.0

I am having the same issue. It seems to be caused by copy-webpack-plugin v7.0.0 . Downgrading back to v6.0.4 seems to resolve the error for now.

I am having the same issue. It seems to be caused by copy-webpack-plugin v7.0.0 . Downgrading back to v6.0.4 seems to resolve the error for now.

I have the same issue with favicons-webpack-plugin at version ^5.0.0-alpha.11

I have the same issue with favicons-webpack-plugin at version ^5.0.0-alpha.11

i have the same  issue too


Hangman: Add /g command as a shortcut of /guess

/g wasn't taken, so I used it

Id rather not add this tbh, just because /guess is easy to type, and /guess is already a shortcut.

Ok


ci: android & ios builds

android & ios builds
fix win-aarch64 builds
fix linux aarch64 builds. using QEMU, so this is slow :(

EDIT: Now usingbuildjet-4vcpu-ubuntu-2204-armfor arm builds, (still using docker so this is still compatible with default GHA runners)

WOOHOO 🚀


added authorize method

after this update you can do something like this
FilamentSpatieLaravelHealthPlugin::make()
    ->authorize( fn () => auth()->user()->can("page_HealthCheckResults") )

inside NavadminPanelProvider to enable access to restricted roles or permissions.

Thanks @phpust


Outlook Calendar - Provide the dates for calendar entries in users timezone

Steps to reproduce the problem:

Create an agent with outlook calendar bundle.
Ask to list all calendar entries for any particular day
Notice that the calendar entries start date and end date are provided in UTC timezone (In my case PST is my timezone)

Both List Events and Get Event Details shows the meeting start/end date in UTC

Debug logs -
calls - 2024-11-12T135229.314.json
calls - 2024-11-12T135217.799.json

I heard a rumor that @ibuildthecloud was going to be doing something to try to resolve the timezone issues across the board instead of doing tool-specific changes. That's probably something we would need here to make it work for datasets.


Prevent old versions of tool to be used

Throw exception in In ToolResolutionStrategy.Resolve when multiple tools are found, to
prevent that we use an outdated version of a tool
This is the simplest fix I could find for #2280 - I'm a little unsure if CakeException is the correct thing to throw, so any advice is appreciated.

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


MasterKeyProtection never works with the CRD backend

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium never recreates master keys that are still in local use. It calls crdBackend.UpdateKey when a CiliumIdentity is removed, but UpdateKey does nothing because AcquireReference always returns nil.
https://github.com/cilium/cilium/blob/dfa6b157e8e9484c65fd938b2b45a4f5f50c61f9/pkg/k8s/identitybackend/identity.go#L126
Cilium Version
Client: 1.11.4 https://github.com/cilium/cilium/commit/9d2546357ef7302514f87b04534933c995340ec6 2022-04-15T08:33:55-07:00 go version go1.17.9 linux/amd64
Daemon: 1.11.4 9d25463 2022-04-15T08:33:55-07:00 go version go1.17.9 linux/amd64

Kernel Version
$ uname -a
Linux rack0-cs5 5.15.32-flatcar #1 SMP Tue Apr 5 17:17:31 -00 2022 x86_64 AMD EPYC 7413 24-Core Processor AuthenticAMD GNU/Linux

Kubernetes Version
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"archive", BuildDate:"2022-03-23T08:04:34Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

cc @timoreimann @aanm I believe this is the issue we are tracking from Cilium Slack.

Do you think Cilium should check if the CiliumIdentity is referenced from CiliumEndpoints before recreating the master key? I think Cilium should recreate it regardless of that if the removed identity that is still referenced from the localKey is missing. Otherwise there is a risk that CiliumEndpoints use an identity that does not exist.
The callers of UpdateKey intend to recover the case in which CiliumIdentity that is still in local use is missing.
https://github.com/cilium/cilium/blob/6f9fedd43cc369b27f5a5a4c8a0634fe7629fe01/pkg/allocator/allocator.go#L499
https://github.com/cilium/cilium/blob/314ca7baeff4f568ffc0bad95124e40665b1f88c/pkg/allocator/cache.go#L151


GCP Credentials File not found.

Is this a BUG REPORT
BUG REPORT INFO
Environment

Cloud provider:  GCP

OS details (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Linux 4.14.13-300.fc27.x86_64 x86_64
NAME=Fedora
VERSION="27 (Workstation Edition)"
ID=fedora
VERSION_ID=27
PRETTY_NAME="Fedora 27 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:27"
HOME_URL="https://fedoraproject.org/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=27
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=27
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Version of Ansible (ansible --version):

ansible <IP_ADDRESS>
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/dungdm93/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.14 (default, Feb 17 2018, 10:42:17) [GCC 7.3.1 20180130 (Red Hat 7.3.1-2)]

Version of Jinja (pip freeze | grep -i jinja):

Jinja2==2.9.6

Version of Shade (pip freeze | grep -i shade):  N/A

The openstack-ansible-contrib version (commit) (git rev-parse --short HEAD):

tag: v3.7.0 (and also bug in master)

Copy of inventory files and custom variables used (please omit your secrets!):
Command used to invoke ansible:
./ocp-on-gcp.sh -vvv

Output of ansible run:
TASK [gold-image-instance : delete temp instance disk] **************************************************************************************************************************************
task path: /home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/playbooks/roles/gold-image-instance/tasks/main.yaml:93
Using module file /usr/lib/python2.7/site-packages/ansible/modules/cloud/google/gce_pd.py
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: dungdm93
<localhost> EXEC /bin/sh -c 'echo ~ && sleep 0'
<localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351 `" && echo ansible-tmp-1519898358.14-215124360734351="` echo /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351 `" ) && sleep 0'
<localhost> PUT /tmp/tmp0S2SRK TO /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351/gce_pd.py
<localhost> EXEC /bin/sh -c 'chmod u+x /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351/ /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351/gce_pd.py && sleep 0'
<localhost> EXEC /bin/sh -c '/usr/bin/python /home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351/gce_pd.py; rm -rf "/home/dungdm93/.ansible/tmp/ansible-tmp-1519898358.14-215124360734351/" > /dev/null 2>&1 && sleep 0'
The full traceback is:
  File "/tmp/ansible_AXdm6M/ansible_modlib.zip/ansible/module_utils/gcp.py", line 252, in _validate_credentials_file
    with open(credentials_file) as credentials:

fatal: [ocp-tmp-instance -> localhost]: FAILED! => {
    "changed": false,
    "invocation": {
        "module_args": {
            "credentials_file": "/home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/inventory/gce/hosts/gce/hosts/project.json",
            "delete_on_termination": null,
            "detach_only": null,
            "disk_type": "pd-standard",
            "external_projects": null,
            "image": null,
            "image_family": null,
            "instance_name": null,
            "mode": "READ_ONLY",
            "name": "ocp-tmp-instance",
            "pem_file": null,
            "project_id": "dungdm93",
            "service_account_email"<EMAIL_ADDRESS>
            "size_gb": "10",
            "snapshot": null,
            "state": "absent",
            "zone": "asia-east1-a"
        }
    },
    "msg": "GCP Credentials File /home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/inventory/gce/hosts/gce/hosts/project.json not found."
}

PLAY RECAP **********************************************************************************************************************************************************************************
localhost                  : ok=7    changed=2    unreachable=0    failed=0
ocp-tmp-instance           : ok=5    changed=3    unreachable=0    failed=2

Failure summary:

  1. Hosts:    ocp-tmp-instance
     Play:     modify temp instance
     Task:     Gather facts
     Message:  MODULE FAILURE

  2. Hosts:    ocp-tmp-instance
     Play:     modify temp instance
     Task:     delete temp instance disk
     Message:  GCP Credentials File /home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/inventory/gce/hosts/gce/hosts/project.json not found.

Anything else do we need to know:
credentials_file place at /home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/inventory/gce/hosts/project.json
(not .../ansible/inventory/gce/hosts /gce/hosts /project.json)

Hm, maybe some change in the latest Ansible.. To workaround, just set credentials_file variable in your config.yaml file.

I tried. It's throw another exception:
TASK [ssh-config-tmp-instance : configure ssh for ocp temp instance] **********************************************************************************************************************************************
task path: /home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/playbooks/roles/ssh-config-tmp-instance/tasks/main.yaml:2
fatal: [localhost]: FAILED! => {
    "failed": true,
    "msg": "The task includes an option with an undefined variable. The error was: u\"hostvars['ocp-tmp-instance']\" is undefined\n\nThe error appears to have been in '/home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/playbooks/roles/ssh-config-tmp-instance/tasks/main.yaml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: configure ssh for ocp temp instance\n  ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: u\"hostvars['ocp-tmp-instance']\" is undefined"
}

PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost                  : ok=4    changed=0    unreachable=0    failed=1

Failure summary:

  1. Hosts:    localhost
     Play:     create temp instance for gold image creation
     Task:     configure ssh for ocp temp instance
     Message:  The task includes an option with an undefined variable. The error was: u"hostvars['ocp-tmp-instance']" is undefined

               The error appears to have been in '/home/dungdm93/Workspace/openshift-ansible-contrib/reference-architecture/gcp/ansible/playbooks/roles/ssh-config-tmp-instance/tasks/main.yaml': line 2, column 3, but may
               be elsewhere in the file depending on the exact syntax problem.

               The offending line appears to be:

               ---
               - name: configure ssh for ocp temp instance
                 ^ here

               exception type: <class 'ansible.errors.AnsibleUndefinedVariable'>
               exception: u"hostvars['ocp-tmp-instance']" is undefined

BTW, I also downgrade Ansible to <IP_ADDRESS>. But... the same problem!
ansible <IP_ADDRESS>
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/dungdm93/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.14 (default, Feb 17 2018, 10:42:17) [GCC 7.3.1 20180130 (Red Hat 7.3.1-2)]

Please try ./ocp-on-gcp.sh --soft-redeploy. It should clean up after an error, but..


How and Why?

Just one simple question after a went through with all the articles here. "How to access Standard AL Code for Standard Objects when someone needs to alter Standard things in BC?" and it leads to "Why Microsoft has made everything so complicated and went back to the 'stoneage' with this AL and VSCode Integration?"
We all know, we could do better in Classic NAV Development Environment than this "new" coding environment.
Please correct me if I am missing something. Eagerly waiting to know something new, and this is not a complaint.

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

ID: e0d4a3e9-4d62-af9f-d178-fd65880bb44c
Version Independent ID: 047ceb19-5f8f-701b-86a2-785322ed467e
Content: Developer and IT-Pro Help for Business Central - Business Central
Content Source: dev-itpro/index.md
Service: dynamics365-business-central
GitHub Login: @solsen
Microsoft Alias: solsen

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-events-in-al

@susanne: Thanks for the illumination. But my feedback/problem was regarding the Development Documentation. I thought about a lacking area. That's why I thought this would be the best option to give and get a feedback. Please forgive me if I'm still out of the track.
@srenders: That article greatly explains how to get around with Events, which I have already used (not mostly btw) with NAV also, which is great btw. But, they do have plenty of limitations right? Like, we just can't walk into some standard functions (triggers) and comment something on Std. Code and re-code based on our Requirement. Sometimes, hate to say, but end clients need heavy customizations to their systems. Do I have a documented support to that area please? If so, it'd be very much helpful.


i18n: plurals handling

In some languages there are different ways to handle plurals, will Misskey i18n support them? For example, in Polish we have (char = znak):
1 znak
2-4, 22-24, 32-34 etc. znaki
5-21, 25-31 etc. znaków
English is simpler, we only have 1 char and 0 or 2-∞ chars…

hmm....
Are there any good ideas?

Looks like i18n refactorization fixed it, I’ll check it when I get some internet connection on a computer 😆

Looks like it works, let me close this issue and create another one about pluralizing all the strings


fix of the uncaught exception in promise within asyncValidation

Codecov Report

Merging #3227 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3227   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      68
  Lines        1519    1519
======================================
  Hits         1519    1519

Impacted Files
Coverage Δ

src/createReduxForm.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Can you prove this?

Read the issue https://github.com/erikras/redux-form/issues/1297, please. It's status is closed, but the problem still exists.

About test case, the asyn validation is not covered within src/__tests__/Form.spec.js at all. It might be too coprehensive issue. I think, it will be better to implement the test cases by authors of the project.

Can you confirm whether your issue is with https://github.com/erikras/redux-form/issues/1297#issuecomment-277038603?
It's the only way I found to reproduce that issue consistently.

Yep. Exactly. This is the case.
If the sync validation is OK and async fails, the uncaught promise error from submit method appears.

Published in v7.0.3.

I believe this leads to errors being swalled in other cases: https://github.com/erikras/redux-form/issues/3303


[Build] Error check failing

Description
The error check build step is failing at https://github.com/layer5io/meshery-nsm/runs/644121144?check_suite_focus=true#step:4:20

@ashiscs do you mind having a look here?

As a result of https://github.com/layer5io/meshery-nsm/actions/runs/96816395 result. I believe We can close this issue.
Reference PR: #68 #69


Typing "^" in normal mode to go to the binning of the line inserts "^"

If I am in normal mode and type a circumflex to go to the beginning of a line, a circumflex is inserted like it would in insert mode.

Also happens with default settings and no other extensions enabled.
macOS 10.14.6
VSCode 1.43.1
vscode-neovim 0.0.50
Neovim 0.4.3
Keyboard layout: German

I can now confirm that this only happens on keyboard layouts with dead keys.

Duplicate of #151


Player doesn't seek with 't' query parameter

Browser: Chromium 55
OS: Linux 4.8
Clappr Version: 0.2.64
Steps to reproduce:

Start the player with ?t=10 in the url
Player doesn't seek to 10 seconds

Did you try to reproduce this issue at http://cdn.clappr.io/ Yes
It did work before, but I don't remember the exact version

Oh, nevermind, the code to do initial seek is only present in html5_video and flashls playback. I will do a pull request with same functionality for hls.js playback.

If somebody is curious, you can use startPosition property in hlsjsConfig to set the starting time.


AsyncHTTPClient should export metrics

Developers want to monitor metrics of outgoing http requests to identify potential causes of issues with dashboards.
While it is possible to generate some metrics by implementing a custom HTTPClientResponseDelegate today, this is quite a burden. Further there are some metrics AsyncHTTPClient users don't have access to. For example:

Number of active http/1.1 requests to a host
Number of requests in the queue to a host

The metrics should be exported to SwiftMetrics directly or with a delegate protocol call comparable to URLSession:task:didFinishCollectingMetrics: exporting NSURLSessionTaskMetrics. If the latter approach is chosen, there should also be a callback/delegate to observe the connection pool size and requests queued per ConnectionPool.Key.

how many Waiters do we have
how many connections do we have open
how many connections are parked in the pool


The type of nextPageToken and prePageToken parameters in CursorPaginatedNonFungibleBalanceWithTypes is not string but string?

Default information

lbd-sdk-js version: 1.3.0
nodeJs version: v16.11.1
module-type: commonJs

Description of the bug
export class CursorPaginatedNonFungibleBalanceWithTypes {
  constructor(
    readonly list: Array<NonFungibleBalanceWithType>,
    readonly prePageToken: string,
    readonly nextPageToken: string,
  ) { }
}

The type of nextPageToken and prePageToken parameters in CursorPaginatedNonFungibleBalanceWithTypes is string now. But This api is returning nextPageToken and prePageToken response  as string?.
I don't know whether this difference is a bug of the document or the implementation.
Example codes
If the api returns status 1000 and responseData.list is not empty, then returns ''(empty string) or 'xxxxx'(page token) as nextPageToken and prePageToken responses. But it returns status 1000 and responseData.list is empty, then returns null as nextPageToken and prePageToken responses.
const sdk = require("@line/lbd-sdk-js");
const load = require("ts-dotenv").load;

const env = load(
    {
        "HOST_URL": String,
        "SERVICE_ID": String,
        "SERVICE_API_KEY": String,
        "SERVICE_API_SECRET": String
    }, {
    "path": "./sdk.env"
}
);

const client = new sdk.HttpClient(env.HOST_URL, env.SERVICE_API_KEY, env.SERVICE_API_SECRET);

const request = new sdk.CursorPageRequest();
client.nonFungibleTokenBalancesWithTypeOfUser("USER_ID", "CONTRACT_ID", request).then(response => {
    console.log("responseData", response.responseData);
});

Error logs
Nothing
Anything else we need to know
Nothing

Oh, I guess that is a sort of mistake on this sdk, I will check it again and let you know when it is fixed. Thank you.

PTAL https://github.com/line/line-blockchain-developers-sdk-js/pull/59

I will close this because this issue has been fixed by #59 and will be released soon.


Master -> Live

Docs Build status updates of commit 174d618:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/app-quality-criteria.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/MRTK_HandJointChaser_Main.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/MRTK_StandardShader.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/MRTK_UX_Slider_Main.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/mrtk-getting-started.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrtk-porting-guide.md
:white_check_mark:Succeeded
View

mixed-reality-docs/spatial-sound-design.md
:white_check_mark:Succeeded
View

mixed-reality-docs/typography.md
:white_check_mark:Succeeded
View

mixed-reality-docs/vuforia-development-overview.md
:white_check_mark:Succeeded
View

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.


Fix incorrect repo url.

Incorrect repo url is making the NPM page look scary:

Updated the repo url in the package.json, but haven't bumped the version number.

Thanks!


Git: pull requests

duplicate berthots video into the github section not just the preface

https://github.com/cloudmesh/book/blob/master/section/doc/github-fork.tex


Streamline the eager load of relationships in crud objects

WHY
BEFORE - What was wrong? What was happening before this PR?
We could only eager load relationships in in columns crud object type and that prevented us from eager loading the relationships for fields in the update form.
AFTER - What is happening after this PR?
We can eager load relationships for multiple object types (eg: columns and fields), and by consequence we can now eager load relationships on the update form.
HOW
How did you achieve that, in technical terms?
Generalizing the eager load method and creating some additional helper methods we can now eager load columns and fields.
Added settings to disable this behavior on the relevant operations, for list operation it eager loads by default to keep previous behavior, and in update is disabled by default to avoid potentially breaking changes.
We have the opportunity to enable it by default in the next version for update.
Is it a breaking change?
I don't think so, no.
How can we test the before & after?
Enable the feature in config/backpack/opeations/update.php. Create a monster with a few relationships, like 3 or 4 belongs to many entries. See the number of queries in main vs this branch.

I absolutely LOVE this. Very nicely implemented, Pedro! Cleans up things quite a bit, for something that was inconsistent. I love it! Haven't tested it, but given the code a good look - doesn't seem like it would cause problems to me. I noticed you kept the same behaviour as before (the defaults).
Nice!