AclNet - Model description

Add model description for sound classification with AclNet
Co-authored by: Paulo Lopez Meyer<EMAIL_ADDRESS>Signed-off-by: Sathish Kuttan<EMAIL_ADDRESS>

Jenkins ok to test

cc @vladimir-dudnik

Jenkins please retry a build

Jenkins please retry a build

Jenkins please retry a build

@vladimir-dudnik I looked at the broken links (first of all its pretty cool that you check for broken links) - and they seem unrelated to the audio model - so I assume this is a temporary / intermittent CI failure - if not and there is something I can help with - please let me know.

@nnshah1 do not worry, we do separate real issues from just temporal network instability. This will not stop us from merge PR.

@vladimir-dudnik Thanks for pushing on this.


Selecting option with circular reference causes errors

Description
When you have option, which referes some kind of cycle, RangeError: Maximum call stack size exceeded occurs.
Example
https://jsfiddle.net/qfja0nnv/
Steps to reproduce

Create option which refers itself
Select this option in multiselect
Option won't get assigned to model,  RangeError: Maximum call stack size exceeded occurs.

Observations
I looked at the sources, and it looks like the component is making deep copy of its options at some point. Is this neccessary?
If it's so, some kind of circular reference protection would be nice.

I believe it’s a bad idea to use unserialisable data as options. The copying is necessary at the moment. Might not be necessary for the 3.0 rewrite I’m planning.
Thanks for noticing though! :)

This also brakes typescript support. An array of typescript objects is passed as option but  the resulting values bound with v-model contains copied json objects.
Probably it also brakes normal js objects with methods.

This should no longer be a problem after the changes to master branch (removed deep cloning).Preparing a release.


Seg fault running tarmak clusters list with invalid config directory

/kind bug
What happened:
I ran tarmak clusters list -c ~/.tarmak/tarmak.yaml
And I get a seg fault:
[signal SIGSEGV: segmentation violation code=0x1 addr=0x110 pc=0xe98c96]
...

What you expected to happen:
To see a list of clusters in that config file.
I'd expect the following commands to return the same thing:
tarmak clusters list -c ~/.tarmak/tarmak.yaml
tarmak clusters list -c ~/.tarmak/

Or the first should print an error message if we don't want people doing that for some reason.
How to reproduce it (as minimally and precisely as possible):
I have checked with Luke, he get's the same thing. My local tarmak binary is built from 3e4f5ae

@charlieegan3 This sees to be fixed for me. Should this be closed?

yeah - I can't replicate this any more either.
/close


Replace exceptions with error events

Kinda depends on #42.

This is a really old issue and I believe this has been resolved in the meantime :shipit: :+1:


neon-desktop cluster never stabilizes

I added code to neon-desktop cluster deployment to wait until all of the cluster pods and containers to stabilize by reporting being ready.  The code that waits for this to happen is at:
KubeSetup.PrepareCluster.cs:556

It looks like Istio is having trouble attaching the cacerts volume which I presume means that any provisioning a website with SSL isn't going to work either.  Have you tried deploying your demo app on neon-desktop?  We should also try all of this on the laptop.
Here's the bad pod info (I don't know if there are other failed pods):
λ kubectl describe pod -n=neon-ingress istiod-857994fc9d-d6bhx
Name:                 istiod-857994fc9d-d6bhx
Namespace:            neon-ingress
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Service Account:      istiod
Node:                 neon-desktop/<IP_ADDRESS>
Start Time:           Thu, 20 Jul 2023 20:30:33 -0700
Labels:               app=istiod
                      install.operator.istio.io/owning-resource=unknown
                      istio=pilot
                      istio.io/rev=default
                      operator.istio.io/component=Pilot
                      pod-template-hash=857994fc9d
                      sidecar.istio.io/inject=false
Annotations:          cni.projectcalico.org/containerID: 8fc6bb094a8b5e0dbda16471c2f6998030d0a79385dbb09609a70ee30894538b
                      cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                      sidecar.istio.io/inject: false
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/istiod-857994fc9d
Containers:
  discovery:
    Container ID:  cri-o://cda93e311c9d8a2bc3003670296290c0c94a3e919887725837311a5e30b37c8e
    Image:         registry.neon.local/neonkube/pilot:1.14.1-distroless
    Image ID:      ghcr.io/neonkube-stage/pilot@sha256:46272406b75b9e3340fd015d087fcd95a34324f23323030aa7c8519bf498d1b1
    Ports:         8080/TCP, 15010/TCP, 15017/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Args:
      discovery
      --monitoringAddr=:15014
      --log_output_level=default:info
      --log_as_json
      --domain
      cluster.local
      --keepaliveMaxServerConnectionAge
      30m
    State:          Running
      Started:      Wed, 26 Jul 2023 14:18:23 -0700
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Wed, 26 Jul 2023 14:17:49 -0700
      Finished:     Wed, 26 Jul 2023 14:18:22 -0700
    Ready:          True
    Restart Count:  2
    Limits:
      cpu:     2
      memory:  2Gi
    Requests:
      cpu:      10m
      memory:   32Mi
    Readiness:  http-get http://:8080/ready delay=1s timeout=5s period=3s #success=1 #failure=3
    Environment:
      GOGC:                                         25
      REVISION:                                     default
      JWT_POLICY:                                   third-party-jwt
      PILOT_CERT_PROVIDER:                          istiod
      POD_NAME:                                     istiod-857994fc9d-d6bhx (v1:metadata.name)
      POD_NAMESPACE:                                neon-ingress (v1:metadata.namespace)
      SERVICE_ACCOUNT:                               (v1:spec.serviceAccountName)
      KUBECONFIG:                                   /var/run/secrets/remote/config
      PILOT_TRACE_SAMPLING:                         1
      PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_OUTBOUND:  true
      PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_INBOUND:   true
      ISTIOD_ADDR:                                  istiod.neon-ingress.svc:15012
      PILOT_ENABLE_ANALYSIS:                        false
      CLUSTER_ID:                                   Kubernetes
    Mounts:
      /etc/cacerts from cacerts (ro)
      /var/run/secrets/istio-dns from local-certs (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-vpzh6 (ro)
      /var/run/secrets/remote from istio-kubeconfig (ro)
      /var/run/secrets/tokens from istio-token (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  local-certs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  <unset>
  istio-token:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  43200
  cacerts:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cacerts
    Optional:    true
  istio-kubeconfig:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-kubeconfig
    Optional:    true
  kube-api-access-vpzh6:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 :NoSchedule op=Exists
                             :NoExecute op=Exists
Events:
  Type     Reason       Age                     From               Message
  ----     ------       ----                    ----               -------
  Normal   Scheduled    5d17h                   default-scheduler  Successfully assigned neon-ingress/istiod-857994fc9d-d6bhx to neon-desktop
  Normal   Pulled       5d17h                   kubelet            Container image "registry.neon.local/neonkube/pilot:1.14.1-distroless" already present on machine
  Normal   Created      5d17h                   kubelet            Created container discovery
  Normal   Started      5d17h                   kubelet            Started container discovery
  Warning  Unhealthy    5d17h (x2 over 5d17h)   kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:8080/ready": dial tcp <IP_ADDRESS>:8080: connect: connection refused
  Warning  FailedMount  8m28s (x2 over 8m30s)   kubelet            MountVolume.SetUp failed for volume "cacerts" : failed to sync secret cache: timed out waiting for the condition
  Normal   Pulled       7m40s (x2 over 8m15s)   kubelet            Container image "registry.neon.local/neonkube/pilot:1.14.1-distroless" already present on machine
  Normal   Created      7m40s (x2 over 8m14s)   kubelet            Created container discovery
  Normal   Started      7m40s (x2 over 8m14s)   kubelet            Started container discovery
  Warning  Unhealthy    7m37s (x15 over 8m13s)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:8080/ready": dial tcp <IP_ADDRESS>:8080: connect: connection refused

FIXED: This was my bad.  The loop checking for bad pods wasn't actually re-polling for status and this pod did eventually stabilize after several minutes.  I've pushed the fix.


compile in mac

What dev env do you have set up? We are able to compile on OS X with the repo as is

Just locally on my mac sierra. My /usr/include/gssapi/gssapi.h doesn't have the line typedef const struct gss_name_struct *gss_const_name_t;

Coverage remained the same at ?% when pulling 598f9f3b287808b0e16f37ebfad6c1bd09737a67 on beltran:compile_mac into 5fb4217df13b8e6878046fe1e5c10e560e1b86dc on apcera:master.

See the building instructions for OS X at
https://github.com/apcera/gssapi#building

I have the error after doing that as well. I seem to get a deprecation warning when issuing the command:
Error: homebrew/dupes was deprecated. This tap is now empty as all its formulae were migrated.

For clarity, this is the error I get when running the tests locally:
# github.com/apcera/gssapi
./name.go:213:9: could not determine kind of name for C.wrap_gss_canonicalize_name

clang errors for preamble:
./name.go:90:2: error: unknown type name 'gss_const_name_t'
        gss_const_name_t input_name,
        ^
1 error generated.

FAIL	github.com/apcera/gssapi [build failed]

@beltran @liggitt FWIW, I think this repo is no longer maintained, I am trying to revive it at https://github.com/levb/gssapi; this issue is fixed, it builds and tests on a Mac


Update wp.tex

Many thanks for your contribution, we truly appreciate it. We will appreciate it even more, if you make sure that you can say "YES" to each point in this short checklist:

You made a small amount of changes (less than 100 lines, less than 10 files)
You made changes related to only one bug (create separate PRs for separate problems)
You are ready to defend your changes (there will be a code review)
You don't touch what you don't understand
You ran the build locally and it passed

This article will help you understand what we are looking for: http://www.yegor256.com/2015/02/09/serious-code-reviewer.html
Thank you for your contribution!

@yegor256/z please, pay attention to this pull request

@silverbonegg thanks!

@silverbonegg/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

Codecov Report

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

@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   37.52%   37.52%
=======================================
  Files          38       38
  Lines        1551     1551
=======================================
  Hits          582      582
  Misses        969      969

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 685a61b...d04cc38. Read the comment docs.

The job is not in WBS, won't close the order


[Bug] No module named 'tenacity.asyncio' when running dbt-athena

Is this a new bug in dbt-athena?

[X] I believe this is a new bug in dbt-athena
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
08:05:33  Running with dbt=1.7.11
08:05:33  Encountered an error:
No module named 'tenacity.asyncio'
08:05:33  Traceback (most recent call last):
...
...
...
  File "/home/runner/.local/lib/python3.10/site-packages/dbt/adapters/athena/__init__.py", line 2, in <module>
    from dbt.adapters.athena.connections import AthenaConnectionManager, AthenaCredentials
  File "/home/runner/.local/lib/python3.10/site-packages/dbt/adapters/athena/connections.py", line 12, in <module>
    import tenacity
  File "/home/runner/.local/lib/python3.10/site-packages/tenacity/__init__.py", line 653, in <module>
    from tenacity.asyncio import AsyncRetrying  # noqa:E402,I100
ModuleNotFoundError: No module named 'tenacity.asyncio'

The issue is due to a breaking change in https://github.com/jd/tenacity/issues/471, which is automatically installed due to the dependency on tenacity~=8.2 - which equates to tenacity>=8.*
Hopefully this problem will be resolved with a release of version 8.5 which will automatically be used by this repository https://github.com/dbt-athena/dbt-athena/blob/main/setup.py#L62
Expected Behavior
Queries should run - this is not a bug with dbt-athena specifically, though, so nothing should tangably change with this library.
Steps To Reproduce

Install dbt-athena (any version where the tenacity~=8.2 is defined in the setup.py)
Run any dbt job

Environment
- OS: Ubuntu 22.04
- Python: 3.10
- dbt: 1.7.11
- dbt-athena-community: 1.7.2

Additional Context
No response

@t04glovern looks like that the fix is simple as installing forceing the installation of "tenacity~=8.3" here
https://github.com/dbt-athena/dbt-athena/blob/main/setup.py#L62.
Feel free to propose a fix for it, otherwise I will take care of it in the next days.
Also, as you might have done already, you can force the installation of "tenacity~=8.3" in your python env, and that should fix the issue as well as a workaround.

This is fixed with 8.4.1: https://github.com/jd/tenacity/issues/475#issuecomment-2173259665

Pretty sure this can be closed


Load dials env as a pre-launch task for tests

As a developer, I want to run the unit tests via the vscode GUI without having to run the load_dials_env prelaunch task, as it is currently configured to do, so that I can develop against beamlines that are unrelated to dials without extra setup and develop in a non-dls_sw environment (e.g. my laptop or a devcontainer).
See below snippet from launch.json:
           ...
            "purpose": [
                "debug-test"
            ],
            "console": "integratedTerminal",
            "preLaunchTask": "load_dials_env",
            "env": {
                // The default config in setup.cfg's "[tool:pytest]" adds coverage.
                // Cannot have coverage and debugging at the same time.
                // https://github.com/microsoft/vscode-python/issues/693
                "PYTEST_ADDOPTS": "--no-cov"
            },
           ...

@DominicOram @dperl-dls is the dials env still a requirement for dodal? If so then maybe we can make load_dials_env be a no-op if the environment is unavailable.
Acceptance Criteria

The vscode test launch config no longer requires the fake dials env to start

Sure, although thinking about it, should we make the vscode tests do exactly the same thing as tox -e pytest? I.e. pytest -m 'not s03' {posargs}

Yeah that makes sense, I like the look of the hyperion setup. I'll make another issue for that, this one can remain just "make the dials env task ignore if unavailable"

@callumforrester is this a still requested feature?


Got this while doing a go build v3

cannot find module providing package gopkg.in/robfig/cron.v3
any idea what might cause it?

Yep - since v3 uses modules, you should import it as github.com/robfig/cron/v3 instead. From what I understand, modules does not allow you to import the same module via different import paths, and since gokpg.in was a workaround for not having such a mechanism, I chose to use the github.com path instead. Please let me know if that doesn't work for you.

thanks @robfig it's building now but got referencing problem when writing code in ide, is that a workaround for that matter?

Thanks! I am able to build now but is there a workaround to referencing cron when writing code using github.com/robfig/cron/v3? Cause it doesn't seem to work anymore, or is that an ide issue?

Can you please fix the doc here ( the import statement at the top ). I spent a long time figuring out this issue.


stdenv: Validate meta.outputsToInstall

If meta.outputsToInstall is set to include absent outputs, various
tools break including channel updates and nix-env.
grahamc@Morbo> nix-env -i -f . -A elf-header-real
installing 'elf-header'
error: this derivation has bad 'meta.outputsToInstall'

This patch adds a mandatory verification phase to the stdenv's meta
check to ensure the list is correct:
grahamc@Morbo> nix-build . -A elf-header-real
error: Package ‘elf-header’ in /home/grahamc/projects/nixpkgs/pkgs/development/libraries/elf-header/default.nix:36 has invalid meta.outputsToInstall, refusing to evaluate.

The package elf-header has set meta.outputsToInstall to: bin

however elf-header only has the outputs: out

and is missing the following ouputs:

  - bin

(use '--show-trace' to show detailed location information)

Note, now the nix-env experience is decidedly worse:
grahamc@Morbo> nix-env -i -f . -A elf-header-real; echo $?
0

though since this is already an issue for unfree, broken, unsupported,
and insecure validity problems I'm not sure we should do something
different here.
One possible question is should this be moved to the checkMeta phase, and not part of every evaluation.
Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on x86_64-darwin (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/95bw3cdcgc8c0rrvqwvhvc805pdv7rmx-stdenv-darwin

Success on aarch64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/pjq5v1xgljr4ygb1h1xfybdjydczcqiw-stdenv-linux

Success on x86_64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/i6vl5lwlz5jbkg4r6p340dwmj6fha3xq-stdenv-linux

What is the impact on evaluation performance?

Success on x86_64-linux (full log)
Attempted: elf-header-real, stdenv
Partial log (click to expand)
these paths will be fetched (0.03 MiB download, 0.16 MiB unpacked):
  /nix/store/d90nn8g9711j6xfb89a7wl0yc66l7gzj-elf-header
copying path '/nix/store/d90nn8g9711j6xfb89a7wl0yc66l7gzj-elf-header' from 'https://cache.nixos.org'...
/nix/store/d90nn8g9711j6xfb89a7wl0yc66l7gzj-elf-header
/nix/store/i6vl5lwlz5jbkg4r6p340dwmj6fha3xq-stdenv-linux

Success on aarch64-linux (full log)
Attempted: elf-header-real, stdenv
Partial log (click to expand)
these paths will be fetched (0.03 MiB download, 0.16 MiB unpacked):
  /nix/store/9wx3gfqmqcr2w5s9gnp79zfjbvca8zi1-elf-header
copying path '/nix/store/9wx3gfqmqcr2w5s9gnp79zfjbvca8zi1-elf-header' from 'https://cache.nixos.org'...
/nix/store/9wx3gfqmqcr2w5s9gnp79zfjbvca8zi1-elf-header
/nix/store/pjq5v1xgljr4ygb1h1xfybdjydczcqiw-stdenv-linux

Success on x86_64-darwin (full log)
Attempted: elf-header-real, stdenv
Partial log (click to expand)
these paths will be fetched (0.03 MiB download, 0.16 MiB unpacked):
  /nix/store/0psyvq9qnn2v0j2kv9zk6qkknpyf7wc0-elf-header
copying path '/nix/store/0psyvq9qnn2v0j2kv9zk6qkknpyf7wc0-elf-header' from 'https://cache.nixos.org'...
/nix/store/0psyvq9qnn2v0j2kv9zk6qkknpyf7wc0-elf-header
/nix/store/95bw3cdcgc8c0rrvqwvhvc805pdv7rmx-stdenv-darwin

on master:
[1] grahamc@Morbo> time  nix-env -qa --json --file .  > /dev/null
nix-env -qa --json --file . > /dev/null  6.08s user 0.37s system 100% cpu 6.447 total

on this branch:
[141] grahamc@Morbo> time  nix-env -qa --json --file .  > /dev/null
nix-env -qa --json --file . > /dev/null  6.36s user 0.41s system 100% cpu 6.761 total

what do you think @edolstra?

I think at +.3s it should be only run if checkMeta is set to true:
-    in builtins.length missingOutputs > 0;
+    in if shouldCheckMeta
+       then builtins.length missingOutputs > 0
+       else false;

but wouldn't mind leaving it on always if you think that is better.

this branch:
grahamc@Morbo> for i in `seq 1 10`; do time  nix-env -qa --json --file .  > /dev/null; done
nix-env -qa --json --file . > /dev/null  6.14s user 0.38s system 100% cpu 6.510 total
nix-env -qa --json --file . > /dev/null  6.09s user 0.38s system 100% cpu 6.465 total
nix-env -qa --json --file . > /dev/null  6.08s user 0.36s system 100% cpu 6.446 total
nix-env -qa --json --file . > /dev/null  6.10s user 0.40s system 100% cpu 6.501 total
nix-env -qa --json --file . > /dev/null  6.17s user 0.41s system 100% cpu 6.579 total
nix-env -qa --json --file . > /dev/null  6.03s user 0.43s system 100% cpu 6.454 total
nix-env -qa --json --file . > /dev/null  6.05s user 0.39s system 100% cpu 6.426 total
nix-env -qa --json --file . > /dev/null  6.06s user 0.39s system 100% cpu 6.445 total
nix-env -qa --json --file . > /dev/null  6.12s user 0.36s system 100% cpu 6.471 total
nix-env -qa --json --file . > /dev/null  6.15s user 0.39s system 100% cpu 6.538 total

master:

grahamc@Morbo> for i in seq 1 10; do time  nix-env -qa --json --file .  > /dev/null; done
nix-env -qa --json --file . > /dev/null  7.16s user 0.46s system 99% cpu 7.618 total
nix-env -qa --json --file . > /dev/null  6.42s user 0.38s system 100% cpu 6.795 total
nix-env -qa --json --file . > /dev/null  6.14s user 0.37s system 100% cpu 6.507 total
nix-env -qa --json --file . > /dev/null  6.06s user 0.39s system 100% cpu 6.442 total
nix-env -qa --json --file . > /dev/null  6.11s user 0.38s system 100% cpu 6.489 total
nix-env -qa --json --file . > /dev/null  6.08s user 0.36s system 100% cpu 6.442 total
nix-env -qa --json --file . > /dev/null  6.12s user 0.39s system 100% cpu 6.508 total
nix-env -qa --json --file . > /dev/null  6.03s user 0.38s system 100% cpu 6.403 total
nix-env -qa --json --file . > /dev/null  6.07s user 0.39s system 100% cpu 6.456 total
nix-env -qa --json --file . > /dev/null  6.07s user 0.37s system 100% cpu 6.432 total

Backport: https://github.com/NixOS/nixpkgs/pull/46838


4 or 8 bit wiegand support ?

Is it possible to get wiegand 4 bits or 8 bits support ?

Yes, 4 and 8 bits modes are supported.
Unfortunately I don't own a device that produces 4/8 bits messages,but it has been reported to work ;)
Please give it a try and let me know

@paulo-raca
I've tested 4 and 8 bits and it shows nothing on terminal, i have keypad that sends keypressed with 4 or 8 bits dependig what you configure, and cards as 26 or 34 bits. when i read a card it's fine i get the UID , but when i pres the key nothing is showed on terminal, that's why i asked.
Does the example need some adjustments to handle 4 or 8 bits ? or it should work "out of the box" ?

Did you try using the latest code from git?
Looks like I've forgotten to make a new release with 4/8 bit support, so it's not on Arduino's library manager yet.

I've updates the README and tagged a new release, so the update with 4/8 bits support should appear on the Library Manager soon


update internal explain comments

Looks good to me.  Perhaps we can update the eslint config to include jsdoc to validate the comments.
@yyx990803 yours thoughts?

@blake-newman sounds like a good idea, although there might be a lot to fix since current jsdoc in Vue source may not be fully compliant ;)

@yyx990803 always the case when adding more linting,  will look into it at somepoint this week.


Let "condition" support "true" and "false"

like
st=>start
op=>operation: Your Operation
cond=>condition: True or false?
e=>end

st->op->cond
cond(true)->e
cond(false)->op

This would be fantastic - if the parser could support generic text, that would be awesome. Like:
cond(toast)->e
cond(passed)->deploy
cond(weekend)->overtime->beer

That would also solve the language problem, e.g. in German cond(Ja) cond(Nein)

PR are welcome ;-)

Agree. I have a three branch condition, which I can't render with flowchart.js
None of the branches are YES or NO


Need to Update the paging style as shown

Hi,

I am working on designing the data table with the given features. But unable to change the style as per attached document for pagination. Could you please help me with this feature on how to apply styles to the datatable pagination

Thank you``
![pagingdesign](https://cloud.githubusercontent.com/assets/17860925/24626795/121dea44-1878-11e7-8b62-dcaa8a9b4fd3.jpg)

Unable to implement ... feature as per design. Here ... stands for number of pages which is not in the viewed scope.
For example : if there are 10 pages . We  have to set the data table to 1,2,3,4,5 .... 10
Trying to implement this kind of feature - http://codepen.io/crawlink/pen/qNbwpE

I believe this would be covered under #547

Thank you for the suggestion. But how to add custom icon to the pagination footer. By default it is previous icon .I need to implement arrow on the previous and next page on footer page. Any suggestion ?

Able to implement the custom icon for the pagination footer.But not able to implement ... feature as attached in the post. Any  idea is helpful.

https://swimlane.gitbooks.io/ngx-datatable/content/api/table/inputs.html
cssClasses

Custom CSS classes that can be defined to override the icons classes for up/down in sorts and previous/next in the pager. Defaults:

sortAscending: 'icon-down',
sortDescending: 'icon-up',
pagerLeftArrow: 'icon-left',
pagerRightArrow: 'icon-right',
pagerPrevious: 'icon-prev',
pagerNext: 'icon-skip'

To change the pager icons you need to add [cssClasses] as an input on your grid and provide it with an object containing these values. If you tell me what icons you want to use I can provide you with an example.
Further customization of the pager isn't currently possible.

I use Font Awesome so as an example:
 customClasses = {
        sortAscending: 'fa fa-sort-asc',
        sortDescending: 'fa fa-sort-desc',
        pagerLeftArrow: 'fa fa-chevron-left',
        pagerRightArrow: 'fa fa-chevron-right',
        pagerPrevious: 'fa fa-step-backward',
        pagerNext: 'fa fa-step-forward'
    };
template: `
// only the relevant bits here
<ngx-datatable [cssClasses]='customClasses'><ngx-datatable>
`

Thanks Adam. I am able to modify the custom icon on the pager. But not able to implement the functionality as mentioned.  We can't customize the paging component of the ngx datatable ?
As per design we need to provide this feature(...) to users.
http://plnkr.co/edit/JVQMPvV8z2brCIzdG3N4?p=preview
Any other ideas ?

Not currently; the issue I linked earlier suggests that it is a planned feature they are currently accepting PRs for. If this is a feature you need I'd recommend submitting a PR for it yourself.

Thanks adam. I just raised PR on your suggestion.

Is there any way to show the last page with respect to other pages as attached.

Not currently.
Your best option is to build your own external pager component until this feature is supported by this project. (No guarantees this is something that will ever happen)

I think a custom footer template would be nice for things like this. Others have asked for it too, so I'll plan to get this in soon.

Thank you Austin. Please let me know once it is available.

Hi Austin,
Any idea when the feature will be available please?
Thanks

Hi Austin,
May i know when this feature is avilable please?
Thanks.

Any update on this please?

Resolved by custom footer in 8.2.0

Hi, I am trying custom CSS pagination next and prev button instead of an icon. If you have any example help me


Make headers compatible with C++

add necesary casts in glib-integration
make sol-log (int-check) compatible with c++
added target to test public headers with g++
added missing stdbool include

@thiagomacieira could you please take a look in https://github.com/solettaproject/soletta/commit/e47cf001ab7d704db2575b74d1cbeea0961e6451
I guess there are better solutions for this problem. I could not find something equivalent with __builtin_choose_expr() in c++.

we can avoid the __builtins_types_compatible() but we still can't have the same implementation that C. _SOL_TYPE_FORMAT will be processed as the function _sol_int_format() and we will not be able to concat it in the macro.
We will still need get the result and concat with the other parameters using the stack.
Am I wrong ?

Yeah, I see the problem. I tried to come up with something, without success. @cmarcelo @thiagomacieira ideas?

I haven't had the time to look into this yet. Give me a day or two.

don't worry, thank you for helping with it.

Added a few comments.

committed with suggestions


add speedup ratio comparison

Added speedup ratio comparison. If suggest_speedup / current_speedup < 1.05, the batch size will not change.
Red is original implementation. Blue is the new feature.

Codecov Report

Merging #58 into master will increase coverage by 4.71%.
The diff coverage is 12.50%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
+ Coverage   57.55%   62.26%   +4.71%
==========================================
  Files          29       29
  Lines        2177     2205      +28
  Branches      333      338       +5
==========================================
+ Hits         1253     1373     +120
+ Misses        861      763      -98
- Partials       63       69       +6

Impacted Files
Coverage Δ

adaptdl/adaptdl/torch/data.py
75.98% <9.09%> (-1.27%)
:arrow_down:

adaptdl/adaptdl/speedup.py
90.42% <20.00%> (-1.97%)
:arrow_down:

adaptdl/adaptdl/reducer.py
88.00% <0.00%> (+2.00%)
:arrow_up:

adaptdl/adaptdl/collective.py
57.69% <0.00%> (+3.84%)
:arrow_up:

adaptdl/adaptdl/torch/_metrics.py
79.50% <0.00%> (+4.91%)
:arrow_up:

adaptdl/adaptdl/checkpoint.py
92.10% <0.00%> (+5.26%)
:arrow_up:

adaptdl/adaptdl/env.py
90.90% <0.00%> (+9.09%)
:arrow_up:

adaptdl/adaptdl/torch/__init__.py
69.44% <0.00%> (+25.00%)
:arrow_up:

adaptdl/adaptdl/torch/adascale.py
94.15% <0.00%> (+33.76%)
:arrow_up:

... and 1 more

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 7b6290e...0c12941. Read the comment docs.


Puerto Rico - STLT onboarding

What You Need to Know

[ ] Terms of Service agreement signed
[x] Kickoff meeting completed
[x] Receiver intake form completed:

To Do

[x] create individual tickets for this epic
[ ] RS team member who originates this ticket: add any dependencies, as needed

Puerto Rico Completed their Intake Form:

We reviewed a private key from Puerto Rico but we need a public key instead. I am waiting on Puerto Rico. If they need assistance, I can get on a call with them to get the right key.

Update. Puerto Rico sent the public key file but ReportStream couldn't make a connection to PR's system. We will follow another approach where CDC sends them the public key.
Next steps are:
Send Elvis (Puerto Rico) public key
Elvis to create credentials for Donald
Assign the public key to those credentials so Donald can log into
Elvis to share credentials with Donald
Donald to create the yaml file in the format below and save in keybase.
Here is the basic format of the yaml file.
state: PR
sftp:
host: # the host name provided by the receiver
port: # the port to connect to
path: # provided by the receiver (the file path we write to)
userName: # provided by the receiver
password: # not used
ppkPassword: # the password generated above
ppkFileName: # the file name generated above
ppkFileContents: # the pub key file contents (or the putty file contents)

Connected successfully to Puerto Rico via ReportStream.


Account field not populated when a Contact is Created by Contact Matching in Salesforce org with Standard Architecture

Summit Events does not populate the Account field when new Contacts are created by Contact Matching.  This is because the architectures used by the early adopters of Summit Events such as St. Thomas (Enrollment RX), Crown College (TargetX), and the personal sandboxes of our developers (EDA or NPSP) all populate the Account field. However as we discovered during the September 2020 Sprint when Summit Events is installed in a standard Salesforce architecture org without one of these apps then an Account value is not added to the Contact.
These Contacts that aren't associated with an Account record are called "Private Contacts" because they are always private, regardless of your organization’s sharing model. The downside of Private Contacts is that they're easy to forget because they're hidden from all users except their owner and the system administrator (per https://help.salesforce.com/articleView?id=contacts_private.htm&type=5).
We need a way to tell Summit Events that an Account value is needed for Contacts and to define what this Account value should be when a standard Salesforce architecture is used.  I believe the easiest solution is to add a record to the Custom Metadata mappings for the "Account" field on the Contact object and map a hardcoded value to a specific Account record (such as an "Unknown Account").  This could be handled through documentation and wouldn't require any coding changes.

@rdblake21 @tcdahlberg We talked about this issue that we experienced for the first time at the September Sprint of the Account field not being populated, so I added it as an issue here.  The good news is that I believe I've identified an easy solution which is to add a record to the Custom Metadata mappings for the "Account" field on the Contact object and map a hardcoded value to a specific Account record (such as an "Unknown Account"), this way the Contact Matching method will populate the Account field. This solution could be handled through documentation and wouldn't require any coding changes.

This has been resolved as part of Contact matching.


If SIGUSR1 or SIGUSR2 are received, flush the coverage data (Fixes #278)

If SIGUSR is already being used by some other part, this code will screw things up. We need a better, permanent solution (I'll create an issue for this), but for now this works.


Optionally allow instrumentation key for each track request and allowing unique Id for track request.

Please provide a description in the PR on the scenario where you would need an instrumentation key per call.

@bottlenecked, could you please merge this soon and publish it to hex?


Feature/dynelf_build_id

diff with #23

Add feature build_id
Add some comments for DynELF and MemLeak
Move find_elf_base from MemLeak to DynELF
Remove TODOs

This change is

I'll split this PR into 2 PRs (TODO and feature/dynelf_build_id).


[GOBBLIN-1780] Refactor/rename YarnServiceIT to YarnServiceTest

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
This renaming is done as YarnServiceTest currently is disabled on CI testing. We would like to add unit tests in this file that are run during CI, but this requires removing some components. This rename is so we don't override YarnServiceTest Git history, simply a rename to YarnServiceIT. After renaming the tests to YarnServiceIT, there will be another PR that has a new file of the original name (YarnServiceTest.java) will be created, new unit tests will be created there, and those new tests will run in CI testing.
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1780

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3637 (4309c2b) into master (667d797) will decrease coverage by 2.78%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3637      +/-   ##
============================================
- Coverage     46.56%   43.79%   -2.78%
+ Complexity    10666     2063    -8603
============================================
  Files          2133      409    -1724
  Lines         83541    17639   -65902
  Branches       9288     2152    -7136
============================================
- Hits          38905     7725   -31180
+ Misses        41074     9056   -32018
+ Partials       3562      858    -2704

Impacted Files
Coverage Δ

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
62.22% <0.00%> (-0.31%)
:arrow_down:

...lin/runtime/messaging/DynamicWorkUnitProducer.java

...apache/gobblin/hive/avro/HiveAvroSerDeManager.java

.../org/apache/gobblin/dataset/DatasetDescriptor.java

...va/org/apache/gobblin/metrics/event/TaskEvent.java

...xtractor/exception/RestApiProcessingException.java

...vice/modules/core/GobblinServiceConfiguration.java

.../dataset/SimpleDatasetHierarchicalPrioritizer.java

...apache/gobblin/writer/GobblinOrcMemoryManager.java

...nt/retention/version/FileStatusDatasetVersion.java

... and 1716 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


(PDB-1034) Ezbake source based testing

This change switched PuppetDB over to use the ezbake_utils helpers in ezbake
to install PuppetDB via source. This effectively means the old installation
methodology can be retired.
The beaker-tests-source.sh script is now modified to ensure that leiningen
is now installed (since its required by ezbake helpers in beaker).
Some minor code was removed that is no longer needed, but a major retirement
patch will be forthcoming to remove the greater amount of code no longer
required. Since it was deemed such a patch would make this patch hard to read.
Signed-off-by: Ken Barber<EMAIL_ADDRESS>

CLA signed by all contributors.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/392/

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/398/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/399/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/400/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/401/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/404/

Closing this PR for now, as I plan on making changes and don't want to create testing noise here. I'll re-open it later when its ready.


[DOC] Please fix doc sample

Please fix the "Add IdentityUser POCO Navigation Properties" example code on this page register entities: in my case I have derivated types for IdentityUser, IdentityRole, IdentityUserRole, IdentityUserToken, IdentityUserLogin (they have int primary/foreign  key), with "long" naming of navigation properties (User has a navigation property named "UserRoles" instead of "Roles"...)
Then my user has UserRoles, UserTokens, UserLogins navigation properties, my Role has UserRoles navigation property.
I end up with correct initial migration with these mapping declarations: in addition to the example code, I declare the one to many relationship from Role to UserRole, so that "RoleId1" column isn't created.
modelBuilder_.Entity<User>().HasMany(e => e.UserRoles).WithOne().HasForeignKey(e => e.UserId).IsRequired().OnDelete(DeleteBehavior.Cascade);
modelBuilder_.Entity<User>().HasMany(e => e.UserRoles).WithOne().HasForeignKey(e => e.RoleId).IsRequired().OnDelete(DeleteBehavior.Cascade);
modelBuilder_.Entity<Role>().HasMany(e => e.UserRoles).WithOne().HasForeignKey(e => e.RoleId).IsRequired().OnDelete(DeleteBehavior.Cascade);
modelBuilder_.Entity<User>().HasMany(e => e.UserLogins).WithOne().HasForeignKey(e => e.UserId).IsRequired().OnDelete(DeleteBehavior.Cascade);
modelBuilder_.Entity<User>().HasMany(e => e.UserTokens).WithOne().HasForeignKey(e => e.UserId).IsRequired().OnDelete(DeleteBehavior.Cascade);

This issue was moved to aspnet/Docs#5028


is this meant to be punts?

I think this is what you mean. I did not understand the sentence if not like this

It was actually spelled correctly; a "pun" is

a joke exploiting the different possible meanings of a word or the fact that there are words which sound alike but have different meanings. the Railway Society reception was an informal party of people of all stations (excuse the pun) in life.

But now when I see the definition, I see that this is not what I meant. Thank you for letting me know!
Btw, what are "punts"?

In some way punts might not be perfect. But was something that mostly fitted.
A punt is a speculative try at something. Something that has a chance of not working out quite right but you give it a go anyway.

In this context we wanted to say that they make fun of JavaScript for being so weird :grin:


Refactor relative humidity funcs from fv3fit to vcm

Move some thermodynamics calculations from fv3fit.emulation.thermo to vcm.calc.thermo. Add a math kwarg to these functions so that they can operate on either numpy arrays (the default) or on tensorflow tensors. Also refactor some functions from vcm.calc.thermo to a new module at vcm.calc.vertical_coordinate.
Added public API to vcm:

relative_humidity
saturation_pressure
specific_humidity_from_rh
density
pressure_thickness
layer_mass

Significant internal changes:

add math kwargs as necessary

[x] Tests added

The namespacing is actually pretty confusing. depending on the function you can either get it in vcm.<func>,  vcm.thermo.<func> , vcm.calc.thermo.<func>. Can we clean up vcm/__init__.py a bit and make this more consistent?

The namespacing is actually pretty confusing

Yes, I did not touch the vcm/calc/__init__.py and imported all the new funcs in vcm/__init__.py. But I can finish the job and remove everything else in vcm/calc/__init__.py.


Crash reporter crashes very silently very often

VSCode doesn't start up with a console. However, I often start it from powershell with start code . instead of just code . (Since occasionally VSCode ends up dumping data into a console that I'm using for something else, and starting with the latter doesn't truly isolate the process, it rather just runs the message loop still connected to the same console).
However starting it that way, it exposed certain errors that ends up being hidden otherwise. During startup, about a 1 in 3 times, these messages end up on the console:
[11576:11580:0226/211032:VERBOSE1:crash_service_main.cc(68)] Session start. cmdline is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --application-name=VSCode --v=1]
[11576:11580:0226/211032:VERBOSE1:crash_service.cc(142)] window handle is 000B03EC
[11576:11580:0226/211032:VERBOSE1:crash_service.cc(290)] pipe name is \\.\pipe\VSCode Crash Service
dumps at C:\Users\PVL\AppData\Local\Temp\VSCode Crashes
[11576:11580:0226/211032:VERBOSE1:crash_service.cc(294)] checkpoint is C:\Users\PVL\AppData\Local\Temp\VSCode Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[11576:11580:0226/211032:VERBOSE1:crash_service_main.cc(84)] Ready to process crash requests
[11576:11596:0226/211032:VERBOSE1:crash_service.cc(323)] client start. pid = 11356
[11576:11596:0226/211032:VERBOSE1:crash_service.cc(323)] client start. pid = 3656
[11608:11612:0226/211033:VERBOSE1:crash_service_main.cc(68)] Session start. cmdline is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --application-name=VSCode --v=1]
[11608:11612:0226/211033:VERBOSE1:crash_service.cc(142)] window handle is 00010B36
[11608:11612:0226/211033:VERBOSE1:crash_service.cc(290)] pipe name is \\.\pipe\VSCode Crash Service
dumps at C:\Users\PVL\AppData\Local\Temp\VSCode Crashes
[11608:11612:0226/211033:VERBOSE1:crash_service.cc(294)] checkpoint is C:\Users\PVL\AppData\Local\Temp\VSCode Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[11608:11612:0226/211033:ERROR:crash_service.cc(301)] could not start dumper

And the crash checkpoint files in the dump above, doesn't seem to have much of meaningful data, but just:
GBP1
20160209
1

Most likely, its harmless and just some issue with the dumper - but I'm just filing it for the purposes of documenting it, if it is indeed harmless.

FYI: the Electron crash service process that lies underneath uses a system global unique pipe name ("\\.\pipe\$1 Crash Service"  ==> "VSCode Crash Service") and if this pipe is already open (e.g. from a second copy of VSCode running) then it will print this error. So, it is probably a bug/design flaw in Electron rather than VSCode itself.
I have no idea whether the original VSCode process's crash service process is able to handle secondary VSCode processes' crashes or not, or if you exit the original, if it also terminates the crash service and leaves secondary VSCode processes without a crash service. But hopefully this explains to you why you see an error message there. :P  For reference, https://github.com/electron/electron/blob/master/atom/common/crash_reporter/win/crash_service.cc#L300

@bpasero There is no action item here for us I believe?

Not sure, would be interesting if our latest Electron use shows the same issue still.

@prasannavl Its been a long while since Feb 2016
Do you still see the messages on crash reporter initializations?
If not, then @bpasero I suggest to close this issue

@ramya-rao-a I haven't seen this in a long time. I suspect it was likely fixed upstream somewhere. Eitherway, I suppose it can be reopened if someone else comes across it. Closing.

Thanks @prasannavl


Writing simultaneous messages to same Channel with different InboundHandler issue

We are having a multi thread application and want to avoid linear channel size based on simultaneous requests E.g., 30 parallel requests served by 30 open channels. So, we planned to use same channel for writing multiple messages wit adding different inbound channel handlers to pipeline. However, certain cases the response message for one handler is read by other handler and there is a request/response mismatch. Is there a better way of handling high transactions/second (TPS) without actually creating that many channels as it does not look practical (our TPS can go upto 100, so creating 100 channels!!).
Please suggest how we can handle request/response matching? Thanks..

@normanmaurer Seeking your suggestion for above issue. Thank you.

@arunsraogithub We use StackOverFlow for usage questions. Github issues are for reporting bugs, suggesting/discussing new features.

@NiteshKant Ok Sure. I am new to this and did not realize. Thanks!


Empty first line in a map throws "Not a valid beatmap!" error

If there is an empty line above the osu file format v line, the parser throws Error: Failed to decode a beatmap: Not a valid beatmap!.
This only really appeared in 1 map out of the ~2,500 I've parsed (https://osu.ppy.sh/b/1485848), so it's not a very big problem as far as I know.

A quick fix I tried adding was:
this._reset();
this._lines = this._getLines(data);
this._setEnabledSections(typeof options !== 'boolean' ? options : {});
this._sbLines = this._shouldParseStoryboard(options) ? [] : null;

// Remove first line if it's empty
if (this._lines[0] == '') this._lines.shift()

const fileFormatLine = this._lines[0].trim();

if (!fileFormatLine.startsWith('osu file format v')) {
  throw new Error('Not a valid beatmap!');
}

inside the decodeFromLines() function at node.cjs:2700 and node.mjs:2696.
or at BeatmapDecoder.ts:121.

Oh, that's a good catch. I never really thought this could be found in a submitted beatmap.

Hopefully it's one of those rare cases, like Skystar's Asymmetry map having that "\uFEFF" symbol.
The editor seems to do it's best trimming all the extra whitespace, so I can't imagine newer maps having it.
Regardless, this is a great parser, thank you for your work!


Clean up boilerplate UI

Remove unused pages and Layout from boilerplate, replace with our own.
Acceptance Criteria:

pages/Home and pages/Documentation are removed from the project
app/Layout is removed/replaced with our own baseline Layout
Routes for 404 and 500 are leveraged using the new baseline Layout

Remaining tasks:

[ ] Update production PROJECT_URL in project-configs.js
[ ] Create new baseline layout
[ ] Instrument baseline layout on all existing pages

Task completed with PR #15


operation - shut down procedure

Added to Helpdesk articles Correct Shutdown Sequence

@mnacinopa a few edits:
Make sure to follow the proper shut down procedure to help keep your machine running smoothly. Do not turn off the back power switch before running the on-screen shut down  sequence.
On the printer's touchscreen, navigate to Options >> System >> Shut Down
Follow the on-screen instructions and wait until the screen turns black.
Once the screen turns black, shut off the printer using the power switch located on the back of the printer.

@peries  Got it. Updated


Update repository path for nxp/imx

Description of changes
Updated repositories for NXP/imx platform.
Old repositories doesn't exist anymore.
Fixed compilation issues.
Things done

[ ] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

@mergify queue


Mutex is not safe on multi-core systems

On a multi-core system, disabling interrupts does not prevent the other core from operating, and so values protected by a bare_metal::Mutex will be incorrectly marked Sync.
Since the overwhelming majority of embedded use cases are single-core, I propose putting a prominent warning in the Mutex docstring for now, and working to develop a safe multi-core extension to the Mutex which can be enabled with a feature gate. Probably something using an atomic to implement a spinlock on top of requiring a CriticalSection.

@therealprof I was looking into this again this morning.
It is not Mutex that is unsound for multiple cores.
It's using cortex_m::interrupt::free to provide the CriticalSection that is unsound on multi-core.
It is possible to implement a different mechanism to provide the CritcialSection that would be sound.
https://gist.github.com/rubberduck203/20415cb0bdc0726b2ebf0903e7193665

Just to be clear, the lock I linked to isn’t sound either, it should use a compare and swap, not an exchange, but is just to prove out that sound methods of providing a lock for the existing mutex can be implemented.

Yeah, this has been discussed back and forth.
Problem is: spinlocks are not ideal either for other reasons and also this implementation will not work on e.g. all Cortex-M0 and M0+ because they don't have CAS instructions so it's not an universally applicable approach.

I think that’s the point. There is no universal approach, but the existing Mutex does allow for individualized approaches that will. It’s maybe not an ideal API, but that’s another matter.
Since the Mutex isn’t the soundness problem, should this issue be closed in preference of the other mutex discussions happening?

There seems to be some confusion about what CriticalSection and Mutex provide here.

CriticalSection is just a token that guarantees, for the duration of its existence, that the current core is in a critical section (ie. has any interrupts that could preempt execution disabled). The contract of this type means that any safe code that constructs a CriticalSection without disabling interrupts is unsound.
Mutex then takes this no-interrupts guarantee to provide mutual exclusion. This is sound if we adopt https://github.com/rust-embedded/wg/pull/419, but not at the current state. It's sound in any case if the data is only accessible from a single core.

I'll improve the docs of CriticalSection to make its contract clearer.

That’s a good idea @jonas-schievink. It took me quite a minute to completely grok how the two interact, and the guarantee that CriticalSection must provide. Would you mind explaining to me why Mutex itself is unsound on multi-core though? I’m not understanding why a CriticalSection couldn’t be provided to it from a global monitor, as described in the ARM synchronization primitives paper.

perhaps having a trait here to be implemented in hw specific crates might make sense. However, in that case, I would argue that a Mutex trait belongs in the embedded-hal crate instead.

I am of the opinion that we're still thinking in terms of ARM cores, or even ARM Cortex M cores.
On SoC with hybrid cores there could be a mix of Cortex A and Cortex M cores, or even non-ARM cores such as RISC-V, so I expect there must be a HW peripheral that could properly implement the synchronization across cores, so, just as I suggested in my 2019 Oxidize Conf presentation (https://www.youtube.com/watch?v=IKXrNlXXfL4#t=29m11s), a trait for such HW-enabled mechanisms is desirable.

That would be by mutex-trait and custom cross-core Send/Sync traits that do not yet exist.

cross-core Send/Sync traits that do not yet exist.

Actually you might not even need this if the cores have their own peripherals and a shared mutex peripheral.

I’d like to be clear, I referenced the ARM paper, but the problem & solution are the same for any platform.

This issue was effectively closed by https://github.com/rust-embedded/wg/pull/419; the Mutex in bare-metal is only considered sound on single-core systems and some other abstraction will be required for multi-core systems.


Added Changes to the Table in the Readme File

🛠 Fixes Issue
I added an extra row to the table in the Readme file for the Inshorts clone. I also fixed a small spelling mistake in the Hulu row.

👨💻 Changes proposed

I made the formatting for Official-Website column more consistent. All of the rows will follow this guideline:
<Website Title> Official Web.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

🗒 Note
I didn't add a link to the Inshorts clone. I believe I would need to create a GitHub Page for that. That's something I'll work on later.

LGTM💫


V8 Thread

To minimize the impact of script execution on GL thread, we create
a dedecated thread called V8 thread, aka 'gvrf-v8' in framework. All
script execution will happen on this thread from now on.

Should we close for now?

Ok then. Planning to close on Thursday.

Closing until we have an update for it.


attempt fixing content type issue

buggy headers look like:
{Fn-Http-Status=[200], Opc-Request-Id=[/x/y], Connection=[keep-alive], Fn-Call-Id=[123], Fn-Http-H-Content-Type=[application/json], Content-Length=[462], Date=[Thu, 21 May 2019 12:31:35 GMT], Content-Type=[None]}

but should have Content-Type: [application/json] and not
Content-Type:[None] nor Fn-Http-H-Content-Type

@denismakogon feel free to fix up, i'm out for the day (possibly weekend). please get a test working around this if you get into it :) the setup_fn_call stuff in test fixtures as well as some of the normal path code seems to assume that the headers are gateway headers always (on request and response), but Fn-Intent=httprequest must be set for this to be the case - outside of that, the logic for Content-Type seems wrong for gateway headers, it seems like we need to test both of these things and fix. see https://github.com/fnproject/fdk-go/blob/master/handler.go#L157 for example, I don't see this check anywhere here. thanks!

that's about all I've got in me for the day... I think it's just a matter of fixing up the tests at this point, and possibly adding some more, think I got most of the http gateway context stuff the way we need it though. feel free to pick up (I'm back on 5/28)

@denismakogon got this working now, but not sure how much you/me likes it. I do think the tests verify that it behaves as it's supposed to now, however, which is good. I put details on commit msg here https://github.com/fnproject/fdk-python/pull/83/commits/25d4469c284013dc1a5a536ba51c75f4f24fa7c5 if you could review it (kinda urgent, customer found this issue), thanks!

@denismakogon updated, thanks

@denismakogon bump

thanks!


Cb lang

Pull request
Proposed changes

Live https://maehr.github.io/collectionbuilder-csv/

See https://github.com/CollectionBuilder/cb-translate/pull/7

See https://github.com/CollectionBuilder/cb-translate/issues/4

See https://github.com/CollectionBuilder/cb-translate/issues/5

Types of changes

[x] New feature (non-breaking change which adds functionality).
[ ] Enhancement (non-breaking change which enhances functionality)
[ ] Bug Fix (non-breaking change which fixes an issue).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist

[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Enhanced multilingual support across the site, including dynamic translations for button texts, table configurations, component titles, and link text based on the site's language setting.
Updated dynamic content generation for titles of included components and "View Full Record" button text to support multiple languages.

Bug Fixes

Fixed an issue where language-specific DataTables configuration was not applied when the language was not English, ensuring consistent functionality across languages.

Documentation

Updated documentation to reflect changes in multilingual support and dynamic content updates.

@koilebeit for bug hunting I set up https://maehr.github.io/collectionbuilder-csv/
There are many 😅

Thanks for the huge amount of work. I think there are still some translations missing, especially for buttons like the "view item" button on the carousel on the start page, and the search button on the search page.
Should the markdown pages in the pages folder also be translated? But this would not work via the translations.yml?

Thanks for the huge amount of work. I think there are still some translations missing, especially for buttons like the "view item" button on the carousel on the start page, and the search button on the search page.
Should the markdown pages in the pages folder also be translated? But this would not work via the translations.yml?

The markdown files will not be translated. Can you point to the code with the missing translations?

Thanks for the huge amount of work. I think there are still some translations missing, especially for buttons like the "view item" button on the carousel on the start page, and the search button on the search page.
Should the markdown pages in the pages folder also be translated? But this would not work via the translations.yml?

The markdown files will not be translated. Can you point to the code with the missing translations?

https://github.com/Stadt-Geschichte-Basel/forschung.stadtgeschichtebasel.ch/blob/5c1864d9bc66f833057853c4237cd6c40c988cf3/_layouts/timeline.html#L26-L28
https://github.com/Stadt-Geschichte-Basel/forschung.stadtgeschichtebasel.ch/blob/5c1864d9bc66f833057853c4237cd6c40c988cf3/_layouts/timeline.html#L38
https://github.com/Stadt-Geschichte-Basel/forschung.stadtgeschichtebasel.ch/blob/5c1864d9bc66f833057853c4237cd6c40c988cf3/_layouts/search.html#L36C1-L38C22
https://github.com/Stadt-Geschichte-Basel/forschung.stadtgeschichtebasel.ch/blob/5c1864d9bc66f833057853c4237cd6c40c988cf3/_includes/index/carousel.html#L23

I fixed all. If you could use the inline comment feature next time https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#starting-a-review GitHub can automate even more steps of the review.

@koilebeit Ready for review. I fixed some more obvious bugs ;)

It seems that the translation in the search bar in the navigation bar is not working:

Fixed it


Linking issue with libboost and libyaml with CPM

Describe the bug
Using CPM to install libboost and libyaml does not work. Compilation works but objects are not linked properly against it.
Previously this does not break our CI machines because the deps are installed at the system level.
When running on the latest dev docker image where these deps are not installed, devs will find issues importing libboost or libyaml
To Reproduce
Steps to reproduce the behavior:
clone tt-metal
export TT_METAL_HOME=$(pwd)
export ARCH_NAME
export PYTHONPATH=$(pwd)
./build_metal.sh
./create_venv.sh
pytest --co models/demos/resnet/tests/test_perf_resnet_2cqs.py::test_perf_2cqs_bare_metal[20-0.005-16-device_params0]

Expected behavior
A clear and concise description of what you expected to happen.
mchiou@aus-gs-07-special-mchiou-for-reservation-1578105:~/tt-metal$ pytest --co models/demos/resnet/tests/test_perf_resnet_2cqs.py::test_perf_2cqs_bare_metal[20-0.005-16-device_params0]
=================================================================================================================================================== test session starts ====================================================================================================================================================
platform linux -- Python 3.8.10, pytest-7.2.2, pluggy-1.5.0 -- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /home/mchiou/tt-metal, configfile: pytest.ini
plugins: dash-2.15.0, anyio-4.4.0, split-0.8.2, timeout-2.2.0
timeout: 2400.0s
timeout method: signal
timeout func_only: False
collecting ... 2024-06-18 22:24:05.019 | DEBUG    | ttnn:<module>:142 - Initial ttnn.CONFIG:
{'cache_path': PosixPath('/home/mchiou/.cache/ttnn'),
 'comparison_mode_pcc': 0.9999,
 'enable_comparison_mode': False,
 'enable_detailed_buffer_report': False,
 'enable_detailed_tensor_report': False,
 'enable_fast_runtime_mode': True,
 'enable_graph_report': False,
 'enable_logging': False,
 'enable_model_cache': False,
 'model_cache_path': PosixPath('/home/mchiou/.cache/ttnn/models'),
 'report_name': None,
 'root_report_path': PosixPath('generated/ttnn/reports'),
 'throw_exception_on_fallback': False,
 'tmp_dir': PosixPath('/tmp/ttnn')}
collected 1 item

<Module models/demos/resnet/tests/test_perf_resnet_2cqs.py>
  <Function test_perf_2cqs_bare_metal[20-0.005-16-device_params0]>

Please complete the following environment information:

OS: [e.g. Ubuntu 20.04]
Version of software (eg. commit)

Additional context
Add any other context about the problem here.

The issue has to do with boost being built as a static lib on the very first clean build, but as a shared lib for all subsequent builds, due to the CMake variable leaking into the Boost CMake config. I'll push a fix soon to force the build to always be static.

closing as issue is fixed in #9532


Using explicit dependencies checks on CI

Use https://github.com/cb372/sbt-explicit-dependencies do declare all dependencies
Enable undeclaredCompileDependenciesTest and unusedCompileDependenciesTest (to avoid test dependencies evicting main ones) on the CI

This can be tackled module by module, I think.

unusedCompileDependenciesTest is already enforced.

undeclaredCompileDependenciesTest was introduced, and backed off, in #3880.  A lot of the work to re-enable that is in an intermediate commit.  And if we'd gone with that, we would not have had this bug.

cats-laws shouldn't be a compile dependency of http4s-client, or most modules.  That may be an orthogonal issue: I am unsure whether that triggered the test dependency to upgrade our core dependency.

The rest of the team hates this, but I still contend we're running with scissors without it.


window: tests and fixes

Fix window() operator to dispose window Subjects when the destination Subscriber is unsubscribed.

Change looks good to me, I'll check in this PR.

Merged with 5168f73, thanks @staltz


[Bug] Module shows up in list for non-SWFFG systems

https://i.imgur.com/SBTY8ti.png this is in a pf2e world.
Looking at your module.json, I see you have the system as a dependency, but no top level "system":["starwarsffg"], which I think is the problem.

Ha. I'll test this out at some point. I only use Foundry for SW FFG :)

Fixed; will be released in 0.2.8. Thanks for the report, and even more thanks for the fix!


fix: release action

superseded by https://github.com/keptn/lifecycle-toolkit/pull/2420

superseded by https://github.com/keptn/lifecycle-toolkit/pull/2420


Direction Problem

I have Acceleration data and Gyroscope data with 100Hz. When I am trying to use this, the direction showing is total opposite than the actual direction. Like If I am going in North Direction then it is showing I am going into South Direction. Why is that so??
And what are the parameters I should vary to make it compatible with my sensor(MPU6050 GY-521) ??

An accelerometer and gyroscope alone cannot provide a measurement of magnetic heading.  The direction of heading will instead be arbitrary.

Okk,,,so is there any way to find the appropriate direction also?? If I add magnetometer data in this code will it work then??
If you have something else in mind which might help me please tell me

The inclusion of a magnetometer will allow allow measurements of heading to be relative to magnetic north.

ok,,,but there is a case where when is_moving[index] value let's say 4 and for that I get a direction,,,but when I change that value let's say 4.5 the direction is getting totally opposite(180 degree)...why is that??

I am sorry that I couldn't make it clear my point. Actually I was talking about this line -
    is_moving[index] = numpy.sqrt(acceleration[index].dot(acceleration[index])) > 4.5 # threshold = 3 m/s/s

I need one more help. Let's say I have magnetometer data then what changes do I need to do in this section ??
delta_time = numpy.diff(timestamp, prepend=timestamp[0])

euler = numpy.empty((len(timestamp), 3))
internal_states = numpy.empty((len(timestamp), 3))
acceleration = numpy.empty((len(timestamp), 3))

for index in range(len(timestamp)):
    gyroscope[index] = offset.update(gyroscope[index])

    ahrs.update_no_magnetometer(gyroscope[index], accelerometer[index], delta_time[index])

    euler[index] = ahrs.quaternion.to_euler()

    ahrs_internal_states = ahrs.internal_states
    internal_states[index] = numpy.array([ahrs_internal_states.acceleration_error,
                                          ahrs_internal_states.accelerometer_ignored,
                                          ahrs_internal_states.acceleration_recovery_trigger])

    acceleration[index] = 9.81 * ahrs.earth_acceleration  # convert g to m/s/s

Please Help !!

You would replace ahrs.update_no_magnetometer with ahrs.update as per the examples and documentation in Fusion.


friendlier saving of log info to file [enhancement request]

I for one would love to have an -o log-to-file option in both getpapers and quickscrape please :)

this will be -f or --logfile in the next release


include node local client loadbalancer address in kube-apiserver signing ips

In-cluster clients should be able to talk directly to the node local apiservert ip address and as a best practice should all be configured to use it. This load balancer provides added benefit in cloud environments of healthchecking the path from the machine to the load balancer fronting the kube-apiserver. It becomes more cruicial in baremetal/on-prem environments where there may not be a load balancer and instead just 3 unique endpoints directly to redundant kube-apiservers. In this case: if using just dns: intermittent traffic failures will be experienced if a control plane instance goes down. Using the node local load balancer: there will be no traffic disruption

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/approve

/retest

/jira OCPBUGS-30769


Adding HASURA_ENDPOINT environment variable to services

Proposed fix for Issue #308

I'm closing this as everything is working as expected with NHOST_BACKEND_URL for internal communication between functions and other Nhost services.


Added highlight of selected brush, and eraser.

This will help the user understand what he had selected.

Looks really cool!


Will it works with Bluetooth PAN ?

Will it works with Bluetooth PAN ?
I want to connect my laptop with Bluetooth.
So , I heard this question.

No, this will only work on TCP (socket) connection.

Will it work on Bluetooth ?


Unclosed quote error within comments

Verbose output:

Running "px_to_rem:dist" (px_to_rem) task
Options: base=16, fallback=false, fallback_existing_rem=false, max_decimals=20, ignore=[], map=false
Reading sass/styles.scss...OK
Warning: styles.scss:1:239: Unclosed quote Use --force to continue.

This error is misleading, i originally thought it was coming from normalize, but just realized it's pointing to styles.scss, which is just imports:
// Don't add external dependencies to libraries, such as compass, here.
// Use Gruntfile.js

@import 'core/variables';
@import 'vendor';
@import 'core/functions';
@import 'core/mixins';
@import 'base';
@import 'layout';
@import 'component';

Ok. Great.. Try running px-to-rem on the compiled css files.

HAH! rookie mistake. it was parsing Sass comments.

works like a charm, thanks for spotting that. this grunt plugin made my day, cheers!


Better handling of container addresses

Singularity and docker container addresses are currently not handled in the best way. This is made difficult by the fact that we have nfcore on dockerhub and nf-core on singularity hub 🤦♂
This issue continues discussion started on PR #42

Ah yeah, the other problem with the current setup is that specifying -with-singularity will have a different effect to -profile singularity. It would be best if we could define the container in some way that allows the expected behaviour for nextflow default flags.

This issue was moved to nf-core/tools#98


Beautiful library!

I just stumbled across this library, and I very much agree with this idea that the interface does not provide network services, just pure OAuth functionality - you "BYONI" (Bring Your Own Networking Interface). What do you think about leveraging Beast's HTTP message model to generate complete messages which Beast can send?
https://github.com/vinniefalco/Beast
Thanks!

@vinniefalco Not sure what you'd be looking for here since the intent is to remain agnostic to the networking layer. Since Beast seems to provide builder-style interfaces for requests, the integration seems like it would be pretty minimal anyway, right?

No follow up, so going to close. Feel free to re-open if there's some concrete next steps you'd like to propose.


Improve responsiveness

Hey, i noticed that in your header part the logo of the ironman is disappearing once website width is decreased,

i would like to change this and make it more visible which thus improves the UI of your website.
Please let me work on it and fix it under GSSoC and Hacktober fest.🙏

@SurajSG23 Go ahead. Make sure it's responsive too

Assigned u.
Level will be given based on the work. So dw about it.

sure thank you, I will work on it now !!


fix(ci): Wait longer for mempool query delay in lightwalletd send transactions test

Motivation
CI timed out waiting for Zebra to log a RPC call that was never made:
https://github.com/ZcashFoundation/zebra/actions/runs/6503861323/job/17665273725?pr=7740#step:9:473
Complex Code or Requirements
This gRPC is extremely hard to test and maybe we should just give up on the unreliable parts of the test.
Solution
The most likely issue is that the wait time is too short. Using exactly the same wait time as lightwalletd creates a race condition.

increase the wait times
add extra logging to make future bugs easier to diagnose

Review
This will continue to occasionally fail PRs until it is fixed.
It doesn't need to be part of the release freeze because CI fixes don't go in the changelog.
Reviewer Checklist

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work
If this test continues to be unreliable, disable those parts of the test.

This has had 2 CI runs in this PR, and 1-2 in PR #7740, and they have all passed.


libnl: update to 3.7.0

Update libnl to latest, and drop the mdb patch that was merged upstream.
Signed-off-by: Jonas Gorski<EMAIL_ADDRESS>

Since 3.7.0 is out, I update to it as well.


starsector: 0.96a-RC10 -> 0.97a-RC7

During this update, due to a new version of Java, the software broke.
On startup it crashed with the error: "Conflicting collector
combinations in option list". This was due to mixing the default
-XX:+UseG1GC and the -XX:+UseConcMarkSweepGC -XX:+UseParNewGC flags.
I removed the latter flags, leaving the default garbage collector
Furthermore, on succesful launch, the game wound warn about the
-XX:PermSize=192m -XX:MaxPermSize=192m flags, that were removed in
Java 8. Thus, those flags were also removed.
The substituteInPlace deprecated --replace argument was also
replaced by the new alternatives.
Description of changes

Release notes of 0.97a-RC7: https://fractalsoftworks.com/2024/02/02/starsector-0-97a-release/
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

cc. @necauqua .
You were the one that added those extra JVM flags, on PR #181422, of which two caused a conflict with the default enabled GC. I remove those new GC flags in favour of the default one. However, do you agree with this? Are those flags, in general, superior to G1GC? Your opinion would be really appreciated!

I honestly don't remember the specifics, but those flags were more like a recommendation that I was using at the time, so it should be fine
The important bit is disabling bytecode verification :)

I honestly don't remember the specifics, but those flags were more like a recommendation that I was using at the time, so it should be fine
The important bit is disabling bytecode verification :)

Ok, thanks for the quick answer! It might be worthed reviewing the remaining flags, to check if they are still relevant and if there are newer recommendations.

@head-gardener , you can review this PR, if you wish :)

lgtm, game runs fine

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3408


Travis account

Hi @ludofleury , would be nice if you could register at https://travis-ci.org/ and add this repository. Everyone could check build status :)

Done, first build is on the way. Congrats

Side note, I'll recommend you to always work on a branch and PR this branch to master, to keep an easy track of the semver tagging + change log


[BUG] The Icons on the Navbar got transparent

All the icons on the Navbar got transparent or black

Make it look like the Original UI

I want to work on this issue.

Please assign me this issue, will fix

@Aman-Mandal I want to work on this issue.

Go ahead Sir :))

Please assign me this issue, will fix

Hey, sorry mate!! But @Anish-Sarawgi asked first, and you can check out other issues in the repo!! I hope you will find a nice one

Any updates @Anish-Sarawgi ?


[BUG] datadog agent not starting on bottlerocket 1.9.2

The system-probe container within the datadog agent does not start on bottlerocket 1.9.2 (it works fine with 1.9.0 beforehand, and downgrading the nodes back to 1.9.0 resolved the datadog agent failure to start)
I suspect this is related to the runc upgrade from 1.1.3 to 1.1.4 in bottlerocket 1.9.2
Agent Environment
Agent 7.38.2 - Commit: ba442fd - Serialization version: v5.0.23 - Go version: go1.17.11

agent status returns nothing
Describe what happened:

failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec /opt/datadog-agent/embedded/bin/system-probe: operation not permitted: unknown

Describe what you expected:
system-probe starts
Steps to reproduce the issue:
Install datadog agent from helm chart (we're using 2.37.9 but 3.0.1 looks like it would behave identically) and add a bottlerocket 1.9.2 node to the cluster.
Additional environment details (Operating System, Cloud provider, etc):
AWS
EKS 1.23
Bottlerocket 1.9.2

Seeing the same behaviour...
Bottlerocket 1.9.2-b8074d44
Datadog Helm Chart 3.0.1
Datadog Agent 7.38.2

Looks like this is/will be fixed in the next version of datadog helm chart
https://github.com/DataDog/helm-charts/pull/740

I’ll close this as it’s fixed in version 3.0.3
https://github.com/DataDog/helm-charts/compare/datadog-3.0.2...datadog-3.0.3


Reconcile loggers

This pull request fixes a regression introduced with #567 and (slightly) tries to improve the overall approach to logging. There is still material for three more pull requests.

There is still material for three more pull requests

follow-up issue(s)? :D

Or even pull requests: will depend on the new branch.


cargo can't install package because of permission problems

Problem
When I run cargo install usvg inside a gitlab CI pipeline which is basically a docker container instead of installing the package it gives me an error. When I try the same container build with podman on my local machine it works. So I can't reproduce it at the moment. Haven't tried local docker yet.
The error:
$ ls -la /home/bernd
total 48
drwx------ 1 bernd bernd 4096 Feb  7 22:34 .
drwxr-xr-x 1 root  root  4096 Feb  7 22:33 ..
-rw-r--r-- 1 bernd bernd   21 Dec 20 18:44 .bash_logout
-rw-r--r-- 1 bernd bernd   57 Dec 20 18:44 .bash_profile
-rw-r--r-- 1 bernd bernd  141 Dec 20 18:44 .bashrc
drwxr-xr-x 6 bernd bernd 4096 Feb  7 22:34 .rustup
$ cargo install usvg
error: failed to initialize index git repository
Caused by:
  failed to resolve path '/home/bernd/.cargo/registry/index/github.com-1ecc6299db9ec823/.git/': Operation not permitted; class=Os (2)

You can see it in action here: https://gitlab.com/gerbolyze/build-containers/-/jobs/1013841597
Steps

Start docker image with archlinux:latest
Install arch rustup package
Install rust toolchain with:rustup install stable
rustup default stable

Try installing usvg withcargo install usvg

Possible Solution(s)
I'm not sure whats going wrong here. As I said when I try the same container build locally with podman it works. I still don't think it's a docker issue. It must be something simple that I don't see.
Notes
Output of cargo version: cargo 1.49.0 (d00d64df9 2020-12-05)
Here is the Dockerfile in question:
FROM archlinux:latest

LABEL description="archlinux build container for gerbolyze"

ARG PCB_TOOLS_EXT_DEPS="python-cffi python-cairocffi python-pycparser"
ARG GERBOLYZE_DEPS="python-numpy python-slugify python-lxml python-click"

RUN pacman -Syyu --needed --noconfirm --noprogressbar base-devel pugixml opencv pango cairo git python python-pip make clang rustup cargo pkgconf $GERBOLYZE_DEPS $PCB_TOOLS_EXT_DEPS \
 && useradd --home-dir /home/bernd --create-home --shell /bin/sh --uid 1000 --user-group bernd

USER 1000:1000

RUN rustup install stable \
 && rustup default stable \
 && cargo install usvg \
 && pip install --user git+https://git.jaseg.de/pcb-tools-extension.git \
 && echo "export PATH=\$HOME/.local/bin:\$HOME/.cargo/bin:\$PATH" >> $HOME/.profile

Is the home directory maybe mounted read-only? Does the user have read and write permissions to that directory?  Is it maybe mounted with a bind mount or a volume mount?  Does the actual home maybe ultimately exist on an NFS mount?
Unfortunately EPERM is not too descriptive.  Does setting net.git-fetch-with-cli maybe help?

Using env CARGO_NET_GIT_FETCH_WITH_CLI=true cargo install usvg didn't work.
 But I should have write access everywhere. I can touch files in my home etc.

It looks like whatever the issue is with glibc and archlinux also affects cargo.  I think when you run pacman, it is overwriting the modifications from your previous step of extracting the old glibc. Something like the following seems to work:
FROM archlinux:latest

RUN patched_glibc=glibc-linux4-2.33-4-x86_64.pkg.tar.zst \
 && curl -LO "https://repo.archlinuxcn.org/x86_64/$patched_glibc" \
 && bsdtar -C / -xvf "$patched_glibc"

RUN pacman -Syyu --needed --noconfirm --noprogressbar base-devel rustup pkgconf

RUN useradd --home-dir /home/bernd --create-home --shell /bin/sh --uid 1000 --user-group bernd

# ***Extract again***
RUN bsdtar -C / -xvf glibc-linux4-2.33-4-x86_64.pkg.tar.zst

USER 1000

RUN rustup install stable --profile=minimal

RUN cargo install ripgrep

FWIW, I have no idea what that issue is about archlinux, so I have no idea if that's a good idea to do that.  Reading https://bugs.archlinux.org/index.php?do=details&task_id=69563, it looks like that is on the road to being properly fixed.

Yeah, that makes sense. I'll try that as long as the issue lasts. Hopefully this gets fixed soon.


Update v2ray to Pre-release v4.39.1

this commit can solve problem with MacOS Big Sur.
see https://github.com/shadowsocks/v2ray-plugin/issues/234

this patch works for me on MacOS 11.14 Big Sur! thanks for the fix!


Progress with  PR #781

@o0rebelious0o - don't know if I missed the progress with #781, whatever happened with the proposed PR? I'm really keen to see the proposed tooltip implementation. Sorry if I missed something obvious as I wasn't following up as much as I liked to couple of weeks ago.

Yeah, sorry, I'm not really sure what happened on it, been a bit distracted the past couple of weeks.  I'm older and wiser now, so will take a look at it with fresh eyes, and with the current state of the code and see what we can do :)

Thank you.


Package readmes are outdated

It must wait until I decide either to update manually or improve markpanso.

This should be fixed, unless I have missed anything.
If somebody stops by, for future reference I am developing a Python script called MarkPanso, which is currently riddled with bugs and only works in the situations where you have very simple triggers, to automate the process of generating a README from a YML file.


publish blobs to beacon node

sync from https://github.com/gattaca-com/helix/pull/31

@coderabbitai review


[PDI-16884] - Cassandra Output step does not work with apache-cassand…

…ra-2.1.0
@mbatchelor, could you please take a look?

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f build.xml clean-all resolve jacoco && ant -f build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  src/org/pentaho/cassandra/legacy/CassandraColumnMetaData.java


Update vpc.yaml

Sam Zhou asked me to add these to this template. I will reference this template, under best practice in the CodeBuild user guide, for VPC support.

This PR breaks the indenting quite badly, resulting in an invalid YAML file.

Wichert,
Please dis-regard my changes. There was a mis-communication and I didn’t realize that this belonged to AWSLabs.
As soon as I realized, I tried to back out my changes.
I apologize for any inconvenience that this caused.
Regards,
James
James Burdon
Tech Writer, AWS Documentation
Tel:<PHONE_NUMBER> x 4351512
docs.aws.amazon.comhttp://docs.aws.amazon.com/
[ws-logo]
[AWS_Certified_Tag__SAA_294x230-Color]
From: Wichert Akkerman<EMAIL_ADDRESS>Sent: Thursday, November 30, 2017 10:42 PM
To: awslabs/ecs-refarch-cloudformation<EMAIL_ADDRESS>Cc: Burdon, James<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [awslabs/ecs-refarch-cloudformation] Update vpc.yaml (#35)
This PR breaks the indenting quite badly, resulting in an invalid YAML file.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/awslabs/ecs-refarch-cloudformation/pull/35#issuecomment-348414794, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ae30TCEGlhP5DavbajfhNwtcZNdhMtmZks5s75_HgaJpZM4QxnPL.


End Customer Impacted - OpenSSL Crash. (Official Intel Corp. submitted bug)

Hi, would someone be able to tell me the change log for  OPENSSL 1.0.2h - such that C2000 Rangeley can pass, C3000 Failed, but then was fixed with the Latest OpenSSL.  Unfortunately - END CUSTOMER cannot change openssl version and must keep openssl 1.0.2h, so I need to identify why it fails on C3000 but passes on C2000.  Any hints would be appreciated.

Sure, look in the git commit log for all the details.  Download the release you care about and look at the NEWS and CHANGES file.  All releases can be found at https://www.openssl.org/source/old/


⚠ Samsung has degraded performance

In daf58d1, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2054 ms

Resolved: Samsung performance has improved in 1135777.


"Other Events" screen

Should be a screen that shows static scores from one or more other events

Working as of this commit


⚠ Bofrost.lu has degraded performance

In 11120d1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1629 ms

Resolved: Bofrost.lu performance has improved in 636c29b after 6 minutes.


Question about filtering out nonsythesisable constructs

I'm trying to filter-out nonsythesisable constructs in yosys. WIP branch can be found here: https://github.com/SymbiFlow/yosys-f4pga-plugins/pull/243
I'm using following test:
module dut();
initial begin
  $displayb("\nTEST PASSED CHECKS");
end
endmodule

According to SynthSubset displayb should be marked as nonsythesisable: https://github.com/chipsalliance/UHDM/blob/master/templates/SynthSubset.cpp#L42, but it is still present in the UHDM:
   \_initial: , parent:work@dut
     |vpiStmt:
     \_begin: (work@dut), line:2:9, endln:4:4
       |vpiFullName:work@dut
       |vpiStmt:
       \_sys_func_call: ($displayb), line:3:3, endln:3:37, parent:work@dut
         |vpiArgument:
         \_constant: , line:3:13, endln:3:35, parent:$displayb
           |vpiDecompile:\nTEST PASSED CHECKS
           |vpiSize:20
           |STRING:\nTEST PASSED CHECKS
           |vpiConstType:6
         |vpiName:$displayb

I've also tried to change 3rd argument of SynthSubset to true, but it also didn't result in error and instead it displays name of the function to stdout (it doesn't happen when 3rd argument is set to false):
1. Executing UHDM frontend.
$displayb
design: (work@dut)
|vpiName:work@dut
|uhdmallPackages:
\_package: builtin (builtin::), file:, parent:work@dut
...

Parsing this test with surelog and -synth option, results in error.
Is this expected behavior? Do I need to parse annotate set myself or nodes from UHDM should be automatically deleted by listen_designs?
Used UHDM version: ad9a41ed8dd74964401586b26843f3aca37fcab5
Used Surelog version: 5d993c5e64ae48192144217dff96806460dca6ac

The -synth option should be passed to Surelog, either as an option or programmatically (CommandLineParser::setReportNonSynthesizable()), Surelog will output the violations (Errors) while parsing the design. You should not set the reportError to true, it is already done while parsing.
In your UHDM client code, you need to check the annotation set to see which node is non-synthesizable, the nodes are not filtered out from UHDM.
What gets filtered are code in between "pragma translate_off, translate_on" during preprocessing when -synth is on.

Please note that UHDM has a client payload datastructure, you can use that to annotate the property on each node.
ClientData* BaseClass::Data() const { return clientData_; }
void BaseClass::Data(ClientData* data) { clientData_ = data; }

Ok, thank you. I was able to parse the set in yosys code and filter-out nonsythesisable objects.


Error readAsText on FileReader

We are getting an error when utilizing this code base
error: TypeError: Failed to execute 'readAsText' on 'FileReader': parameter 1 is not of type 'Blob'.

I missed the key part is that you are using  and not


Added the ability to register a helper like in Handlebars, e.g. {{myHelper someField}}

Currently in mustache# you can create custom tags, the equivalent of helpers in Handlebars. However the syntax is not the same in some cases. For example in Handlebars if I want to create a custom expression helper to format a phone, I would register it like this
modifyHandlebars.registerHelper("formatPhoneNumber", function(phoneNumber) {
	phoneNumber = phoneNumber.toString();

	return "(" + phoneNumber.substr(0,3) + ") " + phoneNumber.substr(3,3) + "-" + phoneNumber.substr(6,4);
});

and in my code, I would use it like so.

Phone: {{formatPhoneNumber phoneNumber}}

In mustache#, the formatPhoneNumber tag needs to be prefixed with # for it to work, e.g.

Phone: {{#formatPhoneNumber phoneNumber}}

which is fine if you are only rendering this template on the server. However, the project I'm on is rendering the template on the server and the client. If you keep with the format

Phone: {{#formatPhoneNumber phoneNumber}}

on the client-side, Handlebars will throw an error, i.e.
var verifyMatch = function(open, close) {
	if(open.original !== close.original) {
		throw new Handlebars.Exception(open.original + " doesn't match " + close.original);
	}
};

I created a separate regex for this so as to not interfere with existing functionality in mustache#. To keep things uniform on the server-side and client-side, I propose to allow the expression helper syntax on the server-side as well.

I'm not trying to create a server side-compatible version of handlebars. I can understand why you'd not want to have two different templates. If you're shooting for absolute identical functionality, you might consider using node.js.

@jehugaleahsa , thanks for your feedback. I use node in another project, but this project is on the .NET stack. I will continue with my fork making any other changes required to maintain isomorphic templating.
Regards,
Nick

Calling into Node.js using .NET is awkward, I agree. My biggest concern is backward compatibility. Without the #, my code wouldn't know if the name was referring to a key or a tag name. I wouldn't want to break someone else's code if they happened to have a key with the same name as one of their tags.


Make the programming interface simpler

At the moment, we have a set of methods in worker.js that allow you to interact with the DUT to

flash
power on/off
set testbot network ap
execute commands
push locally

We need to simplify naming, or make it more clear what helpers are available, We could also add more helpers

Add a reboot and wait function:
Currently in about 5 OS tests, there is the same snippet of code that:

creates a file in /tmp
reboots the DUT via /sbin/reboot
tries to ssh into the DUT and checks if that file is present in /tmp - if it isn't we can say the DUT has rebooted
it should have built in retry/wait

Completed this one with #439, and a bigger goal for #436