text:
Pod Scraping does not seem to be working.

Description
We are using the 0.3.1 Release of nrotelk8s which added the pod scraping next to service scraping for metrics. However i don't see any metrics coming from Pods/Pod Scraping. The Metrics disappeared/stopped coming when i removed the Service prometheus annotations and are not coming from the pod prometheus annotations (as example flux-system namespace and zookeeper namespace)
Steps to Reproduce
Install the 0.3.1 nrotelk8s Release with global config enabled and 2 accounts. The flux-system Pods (for example - notification-controller) are marked with:
    prometheus.io/port: '8080'
    prometheus.io/scrape: 'true'

When i expose the notification-controller through a service with the same annotations, metrics are getting sent to the opsteam NR Account, but when i remove the annotations from the service and use the Pod Annotations instead, no metrics are getting sent.
Expected Behavior
The metrics of the Pod schould be getting sent to the corresponding account in newrelic (this should be for example opsteam NR Account for flux-system), or devteam1 NR Account for let's say solr-devteam1-int Namespace. This still works, if the metrics are exposed through Service Annotations, but not for Pod Annotations.
Relevant Logs / Console output
There are no error logs i could find in the STS regarding flux-system namespace Pod Scraping. I found following logs for the zookeeper namespace scraping, but i guess the Problem there lies in me not annotating the prometheus metrics port via annotation, i only have prometheus.io/scrape: 'true' on the zookeeper pods.
Here are the logs for zookeper namespace, however there are no error logs for flux-system namespace, where the pods are tagged correctly:
2023-10-30T10:40:19.092Z	warn	internal/transaction.go:123	Failed to scrape Prometheus endpoint	{"kind": "receiver", "name": "prometheus", "data_type": "metrics", "scrape_timestamp": 1698662419087, "target_labels": "{__name__=\"up\", instance=\"10.240.0.238:3888\", job=\"kubernetes-pods\", namespace=\"zookeeper\", node=\"aks-system-14590509-vmss00000a\", pod=\"zookeeper-2\"}"}
2023-10-30T10:40:40.285Z	warn	internal/transaction.go:123	Failed to scrape Prometheus endpoint	{"kind": "receiver", "name": "prometheus", "data_type": "metrics", "scrape_timestamp": 1698662440284, "target_labels": "{__name__=\"up\", instance=\"10.240.0.190:2181\", job=\"kubernetes-pods\", namespace=\"zookeeper\", node=\"aks-system-14590509-vmss000009\", pod=\"zookeeper-1\"}"}
2023-10-30T10:40:48.604Z	warn	internal/transaction.go:123	Failed to scrape Prometheus endpoint	{"kind": "receiver", "name": "prometheus", "data_type": "metrics", "scrape_timestamp": 1698662448602, "target_labels": "{__name__=\"up\", instance=\"10.240.0.52:2181\", job=\"kubernetes-pods\", namespace=\"zookeeper\", node=\"aks-system-14590509-vmss000008\", pod=\"zookeeper-0\"}"}

Your Environment

Versions of your OTel collectors: 0.3.1
Kubernetes manifest files:

nameOverride: nr-otel
clusterName: my-cluster-name
traces:
  enabled: true
deployment:
  ports:
    prometheus:
      port: 8888
  prometheus:
    importantMetricsOnly: false
    lowDataMode: true
logs:
  enabled: true
metrics:
  enabled: true
events:
  enabled: true
daemonset:
  ports:
    prometheus:
      port: 8888
  prometheus:
    importantMetricsOnly: false
    lowDataMode: true
statefulset:
  resources:
    requests:
      cpu: 50m
      memory: 0.5G
    limits:
      cpu: 250m
      memory: 1G
  replicas: "3"
  prometheus:
    importantMetricsOnly: false
    lowDataMode: true
    kubeStateMetrics:
      enabled: false
      serviceNameRef: kube-prometheus-stack-kube-state-metrics
    nodeExporter:
      enabled: false
      serviceNameRef: kube-prometheus-stack-prometheus-node-exporter
  ports:
    prometheus:
      port: 8888
global:
  newrelic:
    enabled: true
    endpoint: otlp.eu01.nr-data.net:4317
    teams:
      opsteam:
        licenseKey:
          secretRef:
            name: otel-monitoring-keys
            key: opsteam-shared-ingest-key
        namespaces:
        - kube-system
        - cert-manager
        - flux-system
        - monitoring
        - ops-system
        - opentelemetry
        - ingress*
        - default
        - solrcloud-operator
        - zookeeper
      devteam1:
        licenseKey:
          secretRef:
            name: otel-monitoring-keys
            key: devteam1-ingest-key
        namespaces:
        - .*devteam1*

Additional information
I have the feeling, that the pods are probably getting scraped, but the metrics are not getting sent to NR, but i might be wrong.

Fixed with #77. I'll publish a new release today.


text:
chore(main): release 1.251.1

When this PR is merged, a new tagged release will be created with the notes below.
1.251.1 (2024-01-29)
Bug Fixes

Fix deferred Session Replay payloads (#868) (f69e4b0)
Pass unload options to simultaneous harvests in Session Replay (#870) (655aa5d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/newrelic/newrelic-browser-agent/releases/tag/v1.251.1 :sunflower:

source: gharchive/pull-request

repo: newrelic/newrelic-browser-agent

license_type: permissive

license_source: github-api


text:
NR-261761: NSSecureCoding

This PR replaces the New Relic iOS agent usage of NSCoding with NSSecureCoding.
More information in JIRA ticket here: https://new-relic.atlassian.net/browse/NR-261761

Capital One has found that, in our open source agent, there are several instances where NSCoding is used instead of the more secure NSSecureCoding. The files indicated by them are NRMAAnalyticEventProtocol, NRMAMobileEvent, and NRMAPayload. We should investigate whether these can be updated to use NSSecureCoding, and if possible, do so.

@cdillard-NewRelic @mbruin-NR @smalsam-newr Hi guys I am from team Capital One, kindly ask when will this change be included in a stable version tag, thanks

OK. This will be released in our next version of the New Relic iOS agent ASAP.

@cdillard-NewRelic thanks for the quick reply, Could you please give an possible ETA for the next iOS agent tag?

We'll aim to have this done ASAP this week or next week.

We'll aim to have this done ASAP this week or next week.

thank you, wish you have a good one!

Wanted to follow up and let you know we've released this change in 7.4.12. Let us know if you have any other issues or questions. Have a good day!

Thanks I already tested 7.4.12, seems we don’t have previously scanned
issue, the latest version works, thank you and have a nice weekend.
On Fri, May 31, 2024 at 5:10 PM Chris Dillard @.***>
wrote:

Wanted to follow up and let you know we've released this change in 7.4.12.
Let us know if you have any other issues or questions. Have a good day!
—
Reply to this email directly, view it on GitHub
https://github.com/newrelic/newrelic-ios-agent/pull/249#issuecomment-2142981839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJF2KSFACU6D3VRHB7DMYTZFDRMVAVCNFSM6AAAAABIEGLZRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHE4DCOBTHE
.
You are receiving this because you commented.Message ID:
@.***>

authors: cdillard-NewRelic lipengxuan

repo: newrelic/newrelic-ios-agent


text:
nri-ecs release binary/manifest and tests

https://fsi-build.pdx.vm.datanerd.us/view/all/job/nri-ecs-release-binary
https://fsi-build.pdx.vm.datanerd.us/view/all/job/nri-ecs-release-manifests
Commands are already grouped in makefile targets that can be called
Since to run tests we need access to the ecs environment we might have to run e2e when merging to master only and unit tests at PR time when coming from forks
We can invest time to check if there is a way to spin up a local ECS environment to run tests

Removing from this task the migration of tests, it will be taken care of in a different one.

source: gharchive/issue

repo: newrelic/nri-ecs


text:
infrastructure/kubernetes: pin latest version compatible with helm v2

nri-bundle versions older than 3.2.11 are not compatible with Helm v2, as they use a v3-introduced function get: https://github.com/newrelic/helm-charts/issues/671
This PR pins version 3.2.11 if Helm v2 is detected during installation.

Closing as we have decided the CLI should not support Helm v2 (internal thread).

repo: newrelic/open-install-library


text:
Update documentation

updated architecture documentation
updated runbook documentation

Relates to: #757

@nr-kkenney is this a PR you are still actively working on?

@jpvajda nope. i just let it sit since we thought it should wait until after we migrate. the work is done, just the merging needs to happen.

removing stale label as this will be done when we migrate to gatsby

authors: jpvajda nr-kkenney

repo: newrelic/opensource-website


text:
Are we identifying all affected Ubuntu packages?

While working on the SUSE Oval importer, I've been exploring the Debian and Ubuntu OVAL importers and noticed that in one set of test files, we are reporting potrace as an affected package but arguably should also report libpotrace0 as an affected package.
I think the relevant oval_parser.py code is here.  This function searches the <object> element for a var_ref field and when found uses RegEx to extract the name of a package from the comment field.
With the test file ubuntu_oval_data.xml, for example, it seems the term potrace is extracted from comment="The 'potrace' package binaries." on line 83.
However, in the <variables> element below, there is not only a similar comment field, but two nested <value> elements, one with the text libpotrace0 and the other with the text potrace.  I suspect that we actually want to report both of these as affected packages, but current report only potrace (see ubuntu-oval-expected.json).
BTW, based on minor sampling thus far, it appears that neither Debian nor SUSE includes a <variables> element in their respective OVAL XML structures.

also see #1172

Taking a new look at this issue I created, it strikes me as low priority at best and correctly tagged Data collection and enhancement, but does not concern data quality -- so I am removing that tag.

authors: armijnhemel johnmhoran

repo: nexB/vulnerablecode


text:
Add summary of vulnerabilities in UI and API

See for instance this https://www.cvedetails.com/product/34754/C-ares-Project-C-ares.html?vendor_id=15926

I'm wondering how can we extract year data... perhaps date_published could be of some use here...


text:
1단계 - 화면 응답 개선하기

리뷰어님 안녕하세요.
이번 미션 관련하여 리뷰 요청 드리게 된 한동희라고 합니다.
앞으로 잘 부탁드립니다!
이번 단계의 경우에는 기능을 하나씩 단계별로 추가하는 구조로 되어 있다보니
하나씩 추가하면서 성능을 측정하는 방식으로 진행하게 되었습니다.
gzip 적용이나 redis 적용 같은 경우에는 어느정도 성능 개선 효과를 느낄 수 있었으나,
다른 기능의 경우는 생각보다 체감이 많이 되지 않았던 것 같습니다.
시간 여유 되실 때 리뷰 부탁드립니다.
감사합니다! 🙏🏻

동희님, 남은 학습 기간이 많지 않아서 코멘트 드린 내용을 지금 모두 반영하실 필요는 없습니다.
빠르게 적용해보거나 학습하고 싶으신 부분만 해보시고, 다음 단계 미션 진행하고 싶으시면 슬랙 DM이나 깃헙 코멘트 남겨주세요! 😀

repo: next-step/infra-subway-performance

license: MIT


text:
step4 - 인덱스 설계

안녕하세요 리뷰어님
안정적인 서비스 만들기 4단계 인덱스 설계 리뷰 요청드립니다.
감사합니다.

지금 보니 다음 단계 [추가] 미션도 있었군요 !! ㅎㅎ
나머지 미션까지 진행해보셔도 좋을 것 같습니다 👍


text:
Bug/data fixes

Fixes TGD-114

@mikepspc there is a bug when choosing "ile-de-la-madelaine" in the "destination" field, populating origin and date fields and then clicking on "Start".  On English page it seems to through a form validation required field error and on the French side I get a blank page after hitting "Start".  Let me know if you need screenshots or more information.

authors: jpmscrum mikepspc

repo: nextgentravel/standalone-estimator


text:
Update README.md

added notes regarding watch-paths and neovim

This change to readme will no longer be needed (generally) if bumping version of https://github.com/gmethvin/directory-watcher to 0.17.3 or above in your beholder dependency. (see https://github.com/gmethvin/directory-watcher/issues/88).
Users of clerk that have reloading issues can bump this themselves by adding an explicit dependency.

Hi @davesann, thanks for looking into this. I've cut a new beholder release with the directory watcher bump and upgraded Clerk. Assume that fixes your issue, please let me know if there's anything else we need to do here.

I included  com.nextjournal/beholder {:mvn/version "1.0.2"}  and the problem is resolved for me using neovim. Note that there are still some editors for which there may be issues.

authors: davesann mk

repo: nextjournal/clerk

license: ISC


text:
🛑 /getMusicFeed - Get music feed by URL or ID is down

In d98bdea, /getMusicFeed - Get music feed by URL or ID (https://tiktok.nextpost.tech/getMusicFeed?query=7129970471625362182&cache_timeout=0&license_key=$API_KEY) was down:

HTTP code: 400
Response time: 3910 ms

Resolved: /getMusicFeed - Get music feed by URL or ID is back up in db7f294 after 11 minutes.

repo: nextpost-tech/tiktok-status


text:
[BUG] - Input Clear Button No Longer Working

NextUI Version
2.3.5
Describe the bug
When you try to clear the input using the clear button, the value is emptied, but the input still displays the uncleared text.
You can try it directly on the docs page: https://nextui.org/docs/components/input#clear-button
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
You can try it directly on the docs page: https://nextui.org/docs/components/input#clear-button and try to clear the input.
Expected behavior
I still see the text I tried to clear and I cannot get rid of it.
Screenshots or Videos
No response
Operating System Version
macOS Sonoma 14.3.1 (23D60)
Browser
Chrome

Hello, In the documentation example, onClear calls console.log so it has no working when the Clear button is clicked. You can switch to other state-changing operations like setState()
import {Input} from "@nextui-org/react";

export default function App() {
  return (
    <Input
      isClearable
      type="email"
      label="Email"
      variant="bordered"
      placeholder="Enter your email"
      defaultValue="junior@nextui.org"
      onClear={() => console.log("input cleared")}
      className="max-w-xs"
    />
  );
}

@ShrinidhiUpadhyaya I'll take over this.

authors: Zz-ZzzZ clementohNZ wingkwong

repo: nextui-org/nextui


text:
docs(themes): add theme generator

Closes #3066
📝 Description
This PR introduces a theme generator to the NextUI documentation. The theme generator is accessible via a new navigation item, Themes, making it easier for users to create and customize themes.

⛳ Current Behavior
Currently, the NextUI documentation does not include a theme generator, limiting users' ability to easily create and preview custom themes.
🚀 New Behavior
With this PR, a theme generator will be added to the NextUI documentation, allowing users to generate and customize themes directly within the platform.
💣 Breaking Change
No, this PR does not introduce any breaking changes.
📝 Additional Information
There is an issue with the default color in the white theme; it does not perfectly match the tints and shades of the zinc color used by NextUI's default palette. Although a suitable solution hasn't been found yet, this should not be a blocker, as users can manually adjust the colors. Efforts to resolve this issue will continue.
This version is more concise and polished, improving clarity and flow while retaining all important details.

Summary by CodeRabbit

New Features

Added a NavbarItem for direct navigation to the themes section.
Introduced a FontSizes component for configuring font size settings.
Added FontSizeInput components for various font size categories.
Launched a FontSizeShowcase component to display text elements with different font sizes.

Bug Fixes

Resolved issues related to state management and color updates in theme components.

Documentation

Updated documentation to reflect new components and usage instructions.

Chores

Added new dependencies for color management and UI enhancements.

@wingkwong I fixed the ts error and also implemented the feedback from coderabbitai, but the new reviews from coderabbit ai feels a little bit overkill and don't think they improve the quality of code. I don't find that level of abstraction needed for this simple case.

Thanks. We'll review gradually.

Hmm...it's weird why it's complaining about brand color not being defined since...since the types seems to be correct. Will look into it.

I'm unable to see why there is a issue with that.
The Config interface looks like this
export interface Config {
  light: ConfigColors;
  dark: ConfigColors;
  layout: ConfigLayout;
}

The ThemeType type loooks like this:
export type ThemeType = "light" | "dark";

And the issue is mentioned in brand-colors.tsx, where it says that config[theme] is undefined, which, based on the types definition of Config and ThemeType it can't be true.

Can it be a Typescript compiler issue or I'm missing something?

So the problem was related to SSR. The theme builder was rendered on server side and because of this some values were initialized with false. I've added a check to render the theme builder only on client side and while the js is loading, a loader is displayed.

Hey @xylish7 thanks for this great contribution 🙏🏻 could you please fix the conflicts?

Sure! Will look into it today 👍🏻

@jrgarciadev I've fixed the merge conflicts. Only pnpm-lock.yaml was conflicting.
I also run the build and test command which successfully ran, but there was an error related to the usage of new Image which I haven't touched, so not sure if that was already present or it was because I regenerated the pnpm-lock.yaml file

authors: jrgarciadev wingkwong xylish7


text:
Krakenuniq build module emits lots of unnecessary files (including all the input FASTAss)

Description of the bug
See title
Command used and terminal output
No response
Relevant files
No response
System information
No response

Should update module to follow this guidelines:
You can delete all files but database.{kdb,idx} and taxDB now, if you want

Clean up should be optional

Also fix that diff/patch about the taxonomy staging for seqid2

repo: nf-core/createtaxdb


text:
Broken link to truth info

Description of the bug
https://nf-co.re/variantbenchmarking/truth is not working, linked in README.md, usage.md and truth.md.
Command used and terminal output

Relevant files
No response
System information
No response

That happen due to my assumption probably, I wanted to have a separate readme on truth files and though truth.md will be directly emitted from the web-site.. I will remove the link. Thank you!

repo: nf-core/variantbenchmarking


text:
Add additional information for multi-tool modules

Multi-tool module guidelines

It seems there's already a lot of guidelines present for multi-tool modules.

Modules that optimize resource usage should therefore be referred to as multi-tool modules.
Fixing the term makes it easier to search for in the page since the information is scattered.

Clever use of the Github search box should be able to help people find these modules in nf-core repositories.

No need to label them.

Only allow multi-tool modules that have an explicit chain order.

Makes naming easier, e.g. SAMTOOLS/COLLATEFASTQ
Tools used solely for compression don't need to be in the name. e.g. bwa mem -> samtools sort/view.

How do we name modules that chain over multiple packages?

Connected discussions

Slack discussion: https://nfcore.slack.com/archives/C043UU89KKQ/p1702456394353949
Example of PR that should be kept local: https://github.com/nf-core/modules/pull/4571

Reason for exclusion: the Groovy code is potentially too complex to understand for the average user. Pipeline developers should be able to understand quickly what a module is doing.

Example of PR that could be included: https://github.com/nf-core/modules/pull/3310

How do we name modules that chain over multiple packages?

I guess it's something that we will see on a case by case basis

authors: mahesh-panchal maxulysse

repo: nf-core/website


text:
More Than one iOS device

Can I use more than one iOS device to connect? I've added on but when I try to add the second device it will not find home bridge.
Thanks.

Duplicate of #82 I believe - reopen if that's not the problem though!

repo: nfarina/homebridge

license_source: bigquery


text:
Running Homebridge on OSMC Bootup

Hi,
I have managed to get homebridge-nest running on my OSMC but I want to be able to set so it starts on bootup but it doesnt seem to be working. I know that OSMC uses the /home/osmc/ for the root directory. Does this mean I need to do the following:
Original Example:
sudo nano /etc/init.d/homebridge
[paste clipboard contents]

#!/bin/sh
### BEGIN INIT INFO
# Provides: homebridge
# Required-Start:    $network $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start daemon at boot time
# Description:       Enable service provided by daemon.
### END INIT INFO

dir="/home/pi"
cmd="DEBUG=* /usr/local/bin/homebridge"
user="pi"

sudo chmod 755 /etc/init.d/homebridge
sudo update-rc.d homebridge defaults

What I think is right:
sudo nano /etc/init.d/homebridge
[paste clipboard contents]

#!/bin/sh
### BEGIN INIT INFO
# Provides: homebridge
# Required-Start:    $network $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start daemon at boot time
# Description:       Enable service provided by daemon.
### END INIT INFO

dir="/home/osmc"
cmd="DEBUG=* /usr/local/bin/homebridge"
user="osmc"

sudo chmod 755 /etc/init.d/homebridge
sudo update-rc.d homebridge defaults

Is this correct and do I need to change anything else?
Any help would be great!

Same environment ( OSMC ) maybe same HW ( RPI 2 ? ) ... systemd was the right way for me.
Look at the https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi#running-homebridge-on-bootup-systemd ;-)

authors: iomax joeecreative


text:
docs: switch to new build status badge

This switches to the badge provided by Shields.io.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8992fca) 60.13% compared to head (542c42c) 60.13%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   60.13%   60.13%
=======================================
  Files           2        2
  Lines         148      148
=======================================
  Hits           89       89
  Misses         59       59

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter nfischer

repo: nfischer/framily-tree


text:
BREAKING: Neon.Service package split into .NET Core and .NET Standard versions

We need to figure out how to enable detailed .NET Runtime metrics collection.  prometheus-net has a package for this:
https://github.com/prometheus-net/prometheus-net/tree/master/Prometheus.NetCore
...but it only supports ,NET Core, not .NET Framework (there is no package for the .NET Framework runtime).  I'd like to enable full runtime metrics by default but the Neon.Service library is .NET Standard so it can't reference a .NET Core nuget.
Perhaps it's time to ditch .NET Framework support, at least for Neon.Service or else we could release two packages, one for .NET Core and the other for .NET Standard.
Since the Neon.Service changes for neonLIBRARY v2.5.0 are already breaking, I'm going to convert the Neon.Service package to .NET Core 3.1 and add a new Neon.Service.Framework package for .NET Framework folks (I know there probably aren't any but we need to get used to supporting "The Community")

Hmmm: It's not going to be that simple because Neon.Service is referenced by other .NET Standard libraries like Neon.Xunit and I don't want to do special .NET Framework versions for those libraries (and tools).

We're not going to do this.

repo: nforgeio/neonKUBE


text:
Use workstation GC to reduce RAM usage?

It might make sense to switch neonkube related services from server GC to workstation mode to save memory:
https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/performance#issue-generation-0-is-too-big
These services won't really see high traffic, so this will probably be OK:

[ ] neon-acme
[ ] neon-cluster-operator
[ ] neon-node-agent
[ ] neon-sso-session-proxy

In the future, perhaps we could pass in an environment variable that the containers can use to configure server GC for multi-node clusters,

CLOSING: I poked around and I doubt that we'll save much here: cluster-operator is only 60MB and node-agent is 74MB which isn't too bad.


text:
服饰细节部分纹理还是区别挺大的

感觉这套方案的上限比较低，和传统的try on的方案相比，质量会差很多～

感觉这套方案的上限比较低，和传统的try on的方案相比，质量会差很多～

有具体的case吗？想看看是色差还是纹理质感的区别

感觉这套方案的上限比较低，和传统的try on的方案相比，质量会差很多～

传统的try on是指哪些方案，求推荐

authors: haoxurt tnickMoxuan trikim

repo: nftblackmagic/catvton-flux


text:
feat(helm): add helm lang to parser.c

This way the same parser.c file can be used for both helm and gotmpl in neovim.
If this is an acceptable solution we can automate it in the package.json and maybe also add tests.
You can already test it with https://github.com/nvim-treesitter/nvim-treesitter/pull/6050.
If using this version of nvim-treesitter all you need to do is:
:TSInstall yaml
:TSInstall helm

An other option would be to do it with java-script and create two separate parser.c files. We could copy this from https://github.com/MichaHoffmann/tree-sitter-hcl/blob/main/dialects/terraform/grammar.js

repo: ngalaiko/tree-sitter-go-template


text:
ngcc build error

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
When I run ngcc on a project with transloco I get the following error on the transloco build:

Compiling @ngneat/transloco : main as umd
Error: Expected UMD module file (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/flat/index.js) to contain exactly one statement, but found 6.
    at UmdReflectionHost.computeUmdModule (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:75:23)
    at FactoryMap.factory (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:31:84)
    at FactoryMap.get (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/utils.js:93:48)
    at UmdReflectionHost.getUmdModule (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:56:36)
    at UmdReflectionHost.getModuleStatements (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:70:34)
    at UmdReflectionHost.computeExportsOfUmdModule (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:84:53)
    at FactoryMap.factory (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:32:84)
    at FactoryMap.get (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/utils.js:93:48)
    at UmdReflectionHost.getExportsOfModule (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/umd_host.js:50:94)
    at DelegatingReflectionHost.getExportsOfModule (/Users/timingensiep/Projects/bauhaus/gus-cms/node_modules/@angular/compiler-cli/ngcc/src/host/delegating_host.js:71:34)

Expected behavior

It should run without errors.
Minimal reproduction of the problem with instructions
Create Angular 9.1.x Project and add transloco.
For bug reports please provide the STEPS TO REPRODUCE and if possible a MINIMAL DEMO of the problem, for that you could use our stackblitz example
What is the motivation / use case for changing the behavior?
To use Angular with Jest you need to run ngcc to make it work.
Environment

Angular version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: v12.16.3
- Platform:  Mac

Others:

just upgraded to angular 9 and getting this too

@gkTim @danyo1399
I'm getting this error as well, though it happened for me when upgrading from Angular version 9.1.4 to 9.1.6.
Pinning Angular to 9.1.4 fixes this problem. I assume this is an error on Angular's side.

I got the same error too

wonder if the flat dependency is the only issue. it wouldnt be a big effort to remove that dependency.

@mohamedaarab1994 @danyo1399
Guys... the flat dependency isn't the issue here. Please go to your package.json and pin all Angular dependencies to version 9.1.4, it's an issue with the latest Angular compiler.
e. g.:
  "dependencies": {
    "@angular-devkit/build-angular": "~0.901.5",
    "@angular/animations": "9.1.4",
    "@angular/cli": "~9.1.5",
    "@angular/common": "9.1.4",
    "@angular/compiler": "9.1.4",
    "@angular/compiler-cli": "9.1.4",
    "@angular/core": "9.1.4",
    "@angular/forms": "9.1.4",
    "@angular/language-service": "9.1.4",
    "@angular/platform-browser": "9.1.4",
    "@angular/platform-browser-dynamic": "9.1.4",
    "@angular/router": "9.1.4",
  }

Remove any ^ or ~ signs and set it to version 9.1.4, then run npm install.
If for some reason npm install doesn't work, try removing the node_modules folder and then running npm install again.
That fixed it for me, version 9.1.6 has some compiler issue.

9.1.7 seems to work for me

@giorgi0203 Since you're specifying your version with ~ you will get later version than 9.1.4. Read the previous comments, you need to pin them.

Can someone create an Angular issue that informs them of their breaking compiler change? I'm too lazy to do that 😄
They changed something since version 9.1.5 that breaks existing libraries that were supported until 9.1.4 like what happened with this one.

I am closing this issue since it seems to be Angular compiler's issue, for those who still have any difficulties I suggest you open an Issue in Angular's repository.

@krokofant you placed the wrong link 🙂

@shaharkazaz 🤦♂
https://github.com/angular/angular/issues/37508

authors: HitomiTenshi danyo1399 gkTim itayod krokofant mohamedaarab1994 shaharkazaz

repo: ngneat/transloco


text:
Can untilDestroyed from @ngneat/until-destroy be used with View Engine?

It's unclear from the Readme file whether untilDestroyed from @ngneat/until-destroy can be used with View Engine, or one must use the untilDestroyed from ngx-take-until-destroy.
Is @ngneat/until-destroy reserved for Ivy only?
If the answer is affirmative, then migrating to @ngneat dependency in case of View Engine wouldn't be possible for the time being.

Correct. Use ngx-take-until-destroy if you are working with ViewEngine.

authors: NetanelBasal micobarac

repo: ngneat/until-destroy


text:
Update db.ngo.us

Pull Request Template for .ngo.us Domain Registration

Checklist for Domain Registration Application
1. Zone File Edit

[x] Alphabetical Order: Confirm your domain block is added in alphabetical order by your organization’s name.
[x] Two Comment Lines:

First line: Full organization name.
Second line: Organizational contact email (must be different from the .ngo.us domain applied for).

[x] Nameserver Entries:

At least two NS (Nameserver) records with a TTL value of 86400.
Correct format for the domain block (see README for examples).

Example:
; Happy Cat Foundation
; Submitted by networking team <happycat@example.org>
happycat 86400 IN NS ns1.example.com.
happycat 86400 IN NS ns2.example.com.

2. PR Description
a. Intended Use of Domain

b. Organization Online Presence URLs for Verification

c. Proof of Domain Mention

3. Agreement to Terms

By submitting this pull request, I agree to the following:

My organization is a non-commercial entity that is not affiliated with any government body.
My organization operates legally and in good faith according to the stated purpose.
I have provided accurate and truthful information throughout this application.
Other terms outlined in the Registry's Terms of Service.

4. Final Checklist Before Submitting

[x] Zone file edited correctly, following format and alphabetical order.
[x] At least two valid nameservers with correct TTL (86400).
[x] Domain block includes required comments with organization name and contact email.
[x] Intended use of the domain clearly explained.
[x] URLs for verification included with the exact domain name mentioned on the public profile.
[x] Agreement to terms signed.

I Agree Terms of Service

repo: ngo-us/registry


text:
unable to see the domains

Even though I'm the only user, and admin. Also, End of last year, I was able to access the domains in pDNS, and now, I can't. I've eliminated the only problem - the backend - and it's not pDNS itself. I could've missed something, but I doubt it right now.

I have observed the same behavior when I encountered this issue @ #893
Can you verify if you get the same error messages?

I think domains on the dashboard page are loaded from the PDNS API each time you refresh the page. Check the url and key settings, and try to see in pdns if there are api request incoming.
It can be the pdns admin source address not allowed to access pdns api as well.

authors: ericcotelnu jbe-dw norve

repo: ngoduykhanh/PowerDNS-Admin

license: mit


text:
Add Active directory authentication and Timeout for large zone

Tested in our environment, thanks for this great frontend.

Long time no see, @vdchuyen  :P :P

LOL, miss u so much my dear :heart:

+1 .

Your changes look good to me. Pulling...Thank you for your contribution @vdchuyen .

authors: ngoduykhanh onimsha vdchuyen


text:
Problem with login

I have ubuntu server LTS with wireguard installation by this guide: https://insights.ditatompel.com/en/tutorials/installing-wireguard-ui-to-manage-your-wireguard-vpn-server/
When i want to login by user and password configured in file .env i see this:

WireGuard UI is runnning on this config:
/etc/systemd/system/wireguard-ui-daemon.service
[Unit]
Description=WireGuard UI Daemon
Wants=network-online.target
After=network-online.target
[Service]
User=root
Group=root
Type=simple
WorkingDirectory=/opt/wireguard-ui
EnvironmentFile=/opt/wireguard-ui/.env
ExecStart=/opt/wireguard-ui/wireguard-ui -bind-address "0.0.0.0:5000"
[Install]
WantedBy=multi-user.target
/opt/wireguard-ui/.env
#SESSION_SECRET=wGb2XNFEVuxKVRg!mgvb2iX4Qk5X&8@REm*BzR
WGUI_USERNAME=admin
WGUI_PASSWORD=admin
I have external Nginx for proxy.
Status was:
sie 27 14:13:09 wireguard wireguard-ui[2236]: {"time":"2024-08-27T14:13:09.560191561Z","level":"INFO","prefix":"-","file":"rout:"routes.go","line":"78","message":"Cannot query user admin from DB"}

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Someone have the same problem?

Si tu as modifier le mot de passe et l'utilisateur après avoir lancé l'installation, cela pose des porblème !
J'ai eu le même soucis sur docker compose, j'ai du remettre le mot de passe d'origine et ensuite le changer dans l'interface de wireguard ui

repo: ngoduykhanh/wireguard-ui


text:
Separate featuresets

What
Describe what the change is solving
Separate the feature sets into different functions and options.
How
Describe the solution

Add feature flags for ingress and gateway
Split up featureset registration in main.go

Breaking Changes
Are there any breaking changes in this PR?

@jonstacks @alex-bezek I hope I separated these featuresets at the correct boundaries.
Q. What is the ngrok traffic policy controller and when does it need to be running?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#442
#441  👈
#440
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hjkatz and the rest of your teammates on  Graphite

Merge activity

Oct 7, 2:42 PM EDT: @hjkatz started a stack merge that includes this pull request via Graphite.

repo: ngrok/ngrok-operator


text:
Fix typo

Cool doc! Fixing small typo.

thank you thank you!

authors: inconshreveable sshkel


text:
pep8 compliance

I ran pep8 on the codebase and fixed nearly every compliance issue.

thank you @tjlang for addressing this, we should really run pep8 more often.
I don't want tell you what to do, you should always do what you are interested in and what your time allows, that being said there is some documentation that could use a revision:  https://rawgit.com/gamaanderson/artview/documentation/docs/build/html/index.html

@tjlang Any chance you'd run pep 8 on the latest commit real quick and submit a PR?
I was in the process of accepting changes when I saw this PR. Sorry.

Done.

authors: gamaanderson nguy tjlang

repo: nguy/artview


text:
🛑 Vnetwork is down

In 0ef1fa8, Vnetwork (https://vnetwork.vn) was down:

HTTP code: 503
Response time: 1198 ms

Resolved: Vnetwork is back up in 1dd57b0.


text:
update releases on github ?

Hey thank you for making great software !
don't forget to update the releases on github when you have a moment (it still says the latest is 0.8.0).

Done!

authors: happysalada ngyewch

repo: ngyewch/svelte-leaflet


text:
IE8 에서 edit 후 enter, esc 입력 시 셀 포커스를 잃어버리는 문제

안녕하세요.
IE8에서 edit 후 esc 또는 enter 로 종료한 경우 포커스를 잃어버리는 현상이 발생하는 것 같습니다.
예제(https://nhnent.github.io/tui.grid/api/tutorials/example4.html) 기준으로 테스트 하였습니다.
감사합니다 ~

안녕하세요.
재현상황 확인했습니다. 기존에 있던 버그인데.. 그동안 발견을 못하고 있었던 것 같네요..
수정되는대로 다음 패치 버전에 반영하도록 하겠습니다.
제보 감사드립니다 :)

1.7.1  버전에 반영되었습니다. 이슈 클로즈합니다.

authors: dongwoo-kim nofaterock


text:
fix: 🐛 add explicit types to React hooks and Vue composables

closes https://github.com/nhost/nhost/issues/1484

Codecov Report

Merging #1485 (d42c27a) into main (3c78d0e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1485   +/-   ##
=======================================
  Coverage   85.97%   85.97%
=======================================
  Files          83       83
  Lines        9236     9236
  Branches      506      506
=======================================
  Hits         7941     7941
  Misses       1295     1295

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

Shouldn't we patch @nhost/nextjs as well?

Shouldn't we patch @nhost/nextjs as well?

The packages are linked, but I'm not sure it would add the changeset in the change log. I just updated the changeset

repo: nhost/nhost


text:
🛑 Core is down

In 523d268, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in 184d906 after 4 minutes.

repo: nhs-work/test-upptime


text:
🛑 Auth is down

In d7a4d1e, Auth ($AUTH_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth is back up in 8545b82 after 29 minutes.


text:
Add ECR Image Scanning reports make targets

This PR is to add some make targets to facilitate ECR image scanning so that reports can be scanned and output to a Pipeline. With the correct input this can also block a pipeline so that docker images with warnings aren't deployed.
This PR is in draft as it still in testing in the DI Pipelines

This has now been tested in a DI pipeline for test evidence I can provide screenshots

repo: nhsd-exeter/make-devops


text:
Dashboard_CYPWaitsAccess

Thanks for sharing your SQL code!
Do you have the script that populates NHSE_Sandbox_MentalHealth.dbo.Dashboard_CYPWaitsAccess. I couldn't see it unless I've missed something? I'm trying to recreate the access metric so that I can break it down further (locality, age, ethnicity, etc).
Kind regards,
Alex

Hi Alex,
I'll get that code added today. The access metric is produced by NHS D and and all our code does is pick up the published values. NHS D made the logic (and code!) available via their meta data file, here: https://digital.nhs.uk/data-and-information/data-collections-and-data-sets/data-sets/mental-health-services-data-set/statistics-and-reports
This looks at each month individually. If you need a time series I can share some logic that does this in one go.

Hi Carl,
Thanks for getting back to me, that would be a great help.

closed as complete

authors: CarlMHStats alextoddnhs

repo: nhsengland/MHSDS


text:
Feature - org mapper

Added org mapper to prioritise results matching org
Updated to use cypress for integration tests

There's three random mp4 files, which I think are assets from the test run. If these are not required for the execution of tests can they be a) deleted, and b) the output directory added to .gitignore?

authors: joefitter lennym

repo: nhsx/standards-registry


text:
Update analyzers and frameworks to latest versions

Justification
ASW now supports VS2019 16.9+ (decision). This allows us to use the latest versions of Roslyn analyzers.
Implementation

Updated non-analyzer frameworks to be NET Core 5 or NET 4.6.1 (required for a Windows namespace)
Updated analyzer frameworks to be NET Standard 2.0 (framework used when creating an analyzer through VS template)
Updated analyzer references to be the latest stable version (except for StyleCop, which has not moved out of beta for years)
Added project-specific PackageReferences

Testing

Ensured code builds and tests pass

I'm adding @ccifra and @gregr-ni  to this to get their thoughts on the update. This would still need to be a 2.0 release of the analyzer since it's a big change.

I'm adding @ccifra and @gregr-ni to this to get their thoughts on the update. This would still need to be a 2.0 release of the analyzer since it's a big change.

We do need to stay up to date on these. Does seem like a 2.0 is appropriate as this is likely to require work on clients to adopt.

@pakdev btw I'm just waiting for all the checks to pass and I'll take a look again this. No rush, just wanted to let you know

@pakdev btw I'm just waiting for all the checks to pass and I'll take a look again this. No rush, just wanted to let you know

Yeah, got busy. Hopefully the build is fixed now

@jryckman this is ready for review

@pakdev since this is a big change is will result in the analyzer doing a major version bump, how is that handled? If we don't make any modifications outside of this PR, it will just autobump the version and publish a newer minor version, right?

@jryckman Yes, I think so. Since I enabled commmit-message-incrementing, one can use +semver: breaking or +semver: major to increase the major version.
You can also directly modify GitVersion.yml by setting up the next-version.
Details can be found https://gitversion.net/docs/reference/version-increments

Ok, I added +semver: breaking at the end of my commit message. That's sufficient, right?

Ok, I added +semver: breaking at the end of my commit message. That's sufficient, right?

I think so? I haven't used that before, so I'm not sure what's going to happen. @Everest2020 would know best as he's the one who set it all up

@pakdev I disabled the step to publish the Nuget package. Feel free to commit this PR, I will take a look at whether the generated Nuget version is as expected tomorrow.

authors: Everest2020 gregr-ni jryckman pakdev

repo: ni/csharp-styleguide


text:
NI-FGEN on Linux?

Per https://github.com/ni/grpc-device/releases/tag/v2.0.0 NI-FGEN on Linux is not supported via gRPC.
NI-FGEN does work on Linux: https://www.ni.com/pdf/manuals/ni-linux-device-drivers-2022-q4.html
Is this a documentation mistake or is there something in NI gRPC Device Server that prevents it from working on Linux while it works on other similar drivers like NI-DCPower?
AB#2282675

Corrected Release Notes for 2.0 and main branch's Supported NI Drivers  section of the README to reflect that FGEN is supported on Linux.

authors: marcoskirsch reckenro

repo: ni/grpc-device


text:
Updates behavior when new session name is in use in different resource repository.

What does this Pull Request accomplish?

Created a new SessionException struct in the shared library
Throw a SessionException from the session resource repository when trying to add a session that's already in a different resource repository instead of returning a warning status of 1.
Update codegen so all "Init" service handlers catch the new SessionException and return a gRPC Status of INVALID_ARGUMENT with the exception's message attached.
Update the session resource repository unit test to now expect the SessionException to be thrown when trying to add a session where the session name is already in use in a different resource repository.

Why should this Pull Request be merged?
Addresses #685
If a proposed session name is already used by a different driver, grpc-device was returning a warning status 1 on the return message's status field. This both allows programs making the call to keep running since it's treated as a warning and if the client does check the status code it can be ambiguous depending on the driver.
This change addresses this by instead immediately returning a gRPC Status of INVALID_ARGUMENT with a message explaining that the session name is already in use.
What testing has been done?
Updated a unit test testing the old behavior to now ensure the new SessionException is thrown if the session name is used in a different resource repository.
Ran the examples like they were specified in the Issue.
Now, running the daqmx example while dcpower is running using "my task" as the session name produces:
PS ~\grpc-device\examples\nidaqmx> python .\analog-input.py
The session name "my task" is already being used in a different driver's service. Please use a different name.

And similarly, running the dcpower example while the daqmx example is running (with time.wait(60.0)) stops the program with the same message:
PS ~\grpc-device\examples\nidcpower> python .\measure-record.py
The session name "my task" is already being used in a different driver's service. Please use a different name.

@reckenro I added the breaking change tag here. The old behavior was pretty wrong and a bit of an edge/probably-a-mistake case anyway. But (I think) it's possible that someone could have worked around the old behavior in a way that would now break.

authors: astarche reckenro


text:
Updated NI-DCPower example to rely on exceptions

What does this Pull Request accomplish?

Removes checks for errors after each call since they are no longer warranted.
Adds handling for the UNKNOWN exception code including parsing the fields.

Why should this Pull Request be merged?
Part of Task 2103385: Update examples to handle new errors
What testing has been done?
Verified that the error handling is correct both for failure to connect (which hasn't changed) as well as invalid resource.
>> python measure-record.py localhost 31763 dev1
Device was not recognized. The device is not supported with this driver or version.

Invalid Identifier: dev1
Status: -1074118656

To fix the validate_python step in the build, I'd recommend installing Black to automatically reformat it. You can look at https://github.com/ni/grpc-device/wiki/Development-Tips-and-Tricks#black-format-on-save to see how to install and run it from a shell or as a vs-code extension.

To fix the validate_python step in the build, I'd recommend installing Black to automatically reformat it. You can look at https://github.com/ni/grpc-device/wiki/Development-Tips-and-Tricks#black-format-on-save to see how to install and run it from a shell or as a vs-code extension.

I opened it in VS Code and the problem was obvious. The trailing semicolon after the function call exposes my C/C# background.

authors: dmondrik reckenro


text:
Multiple Enums Copying Incorrectly to Cluster

This bug was found in InstrumentStudio using MeasurementLink LabVIEW where multiple consecutive enums were not being sent from the client (InstrumentStudio) to the server (MeasurementLink LabVIEW measurement) correctly. Debugging into this, it seems that the issue lies somewhere grpc-labview where the only the first enum's values get transcribed into the cluster structure. Sumit Jain (@ni-sujain) asked me to recreate this bug item directly in the grpc-labview repo.
Further details and an example measurement that demonstrates this issue can be found in this AzDO bug item.
For completeness, I've also detailed the issue and debugging steps taken below.

Bug Description
This behavior was reported by Andy Tan Wei Keat (andy.wei.keat.tan@ni.com) using MeasurementLink LabVIEW v1.2.0.2 which is built against grpc-labview v1.0.0.1. An example measurement was provided to reproduce this issue and attached.
Sample Plugin 1001.zip
Note that MeasurementLink LabVIEW is currently incompatible with the latest version of grpc-labview and cannot be upgraded from v1.0.0.1.
This example sets up two enums where the configuration pipes directly into the result.

When we have two continuous enums in a Measurement Configuration, the second enum will not receive the data in the Measurement Result.

Note that if a non-enum control is inserted in between the two enum controls, the data is passed as expected.

Debugging Steps Taken
On the grpc client side, InstrumentStudio correctly serializes the measurement's configuration parameter values. In this example, there are two bytes per parameter, the first byte for the parameter id and Google.Protobuf.WireFormat.WireType (in this case, the wire type is VarInt = 0 so the entire first byte can be considered the parameter id) and the second byte for the value.

On the grpc server side, MeasurementLink LabVIEW correctly receives the serialized configuration parameter message. It then takes that message and passes it into grpc-lvsupport-release.lvlib:UnpackFromAny.vim. This eventually calls down into the UnpackFromBuffer method in the labview_grpc_server.dll assembly.

Here the unpacked value only contains the information for the first enum, but the second enum's value is left as default which is incorrect.
It looks like we are getting the correct message in UnpackFromBuffer and the issue likely isn't in the transmission.

Here we found an issue where it looks like we are copying the value into the cluster as a LVUInt32MessageValue rather than a LVEnumMessageValue (which has int32 underlying), however it appears to have been fixed in a newer version of grpc-labview  (#263 and #283). Manually applying these changesets to v1.0.0.1 resolves this typing weirdness, but does not affect the described problem.

Looking at the data we're copying into the cluster itself, it looks like we're correctly using 4 bytes for int32s as expected. One thing to note is that the widths of these values are sourced from clusterOffset which comes from the metadata of the message rather than calling size(), though I don't think this is relevant as the 4-byte widths look correct.

The missing data for the second enum appears after the values are copied into the cluster. Maybe this is because the cluster is a int8_t or because the debugger simply interprets it as a pointer to a value rather than a pointer to an array (or cluster structure, I'm not really sure how this works here).

AB#2490682

I tried reproducing this on my machine with a simple proto file that has two enums next to each inside the same message. I didn't not face any issues sending across enum values from the server to the client, even though there was no numeric field in between the enums.
Could you please attach the proto file that you are using for the project that you have attached?
I will try to install Measurement Link on my machine and debug the attached project, but in the meantime, it would be helpful if I could see the proto file as well.

TL;DR
Solution:
In the typedefs, Measurement Configuration.ctl and Measure Results.ctl, change the representation of the enum  from U16 to U32.
Reason:
This is happening because of mismatch in the numeric representation of the enum type across the Measurement UI code and the gRPC LabVIEW code.

Details
gRPC LabVIEW code assumes that the enum types passed to it are 32-bit integers. This is because proto files define enums as 32-bit integers.
The enums in the Measurement UI side of the code, however were 16-bit integers. These are the enums present in the typedefs, Measurement Configuration.ctl and Measure Results.ctl.
When the client is run, the protobuf is parsed by gRPC LabVIEW and the value is copied into a cluster on the Measurement UI code (MeasurementPlugin.lvclass::Unpack For Grpc.vi). This VI internally calls UnpackFromAny.vim, which actually parses the protobuf and returns the value as a LabVIEW cluster. The API in labview_grpc_server.dll writes the correct value of the protobuf into the cluster pointer. But once the cluster is returned to the LabVIEW side, and typecast to one of the typdefs mentioned above, it would read only the first [16 + 16] bytes, as opposed to the first [32 + 32] bytes of actual value. This was why the second enum value would read 0 and just select the default value of the enum.
Changing the representation of the enum in the typdef fixes the issue.

Since this is a fix that needs to go into the attached project, and not into the gRPC LabVIEW code, closing this bug.

repo: ni/grpc-labview


text:
Chromatic always does full snapshots on new branches

🧹 Tech Debt
In the following scenario:

main is up to date.
the latest commit on main is an applying package updates [skip ci] type of commit

this commit does not have a storybook calculated for it
this commit modifies package.json and package-lock.json

create a branch with a new commit that does not modify package.json
push the branch and the CI runs on the push, builds, and publishes to chromatic and you see the following example build log

Chromatic CLI v11.2.0

...

Retrieving git information
Found 12 changed files:
  angular-workspace/projects/ni/nimble-angular/CHANGELOG.json
  angular-workspace/projects/ni/nimble-angular/CHANGELOG.md
  angular-workspace/projects/ni/nimble-angular/package.json
  angular-workspace/tsconfig.json
  change/@ni-nimble-components-26aadfad-c24c-4ad0-ae8e-e75769665e95.json
  change/@ni-nimble-components-f36f5e68-2f6a-4e85-bb86-9fcf7ad37a8d.json
  package-lock.json
  packages/nimble-blazor/package.json
  packages/nimble-components/CHANGELOG.json
  packages/nimble-components/CHANGELOG.md
  packages/nimble-components/package.json
  packages/nimble-components/tsconfig.json

...

Could not retrieve dependency changes from lockfiles; checking package.json
⚠ TurboSnap disabled due to file change
Publishing your built Storybook
    → Calculating file hashes
Found a dependency change in angular-workspace/projects/ni/nimble-angular/package.json
A full build is required because this file cannot be linked to any specific stories.

...

We found 90 components with 290 stories.

So note that even though my change has no package.json changes, the latest commit from main does and causes all snapshots to be retaken. This only impacts the first commit to a branch.
Solutions

We could try and figure out how to get a story published for the applying package updates [skip ci] commits. We would have to actually run the CI and publish a storybook. It will still need to capture all snapshots unnecessarily because there is a package.json change which is a fake signal (the change is just bumping the versions of packages in the monorepo, no actual dependencies are changing)

I don't really think this is worth doing. I think it'll bee a bit of a wash. We will run an extra full storybook build for every commit to main but have one fewer in branches that are made.

We could ask storybook for a way to have turbosnap ignore changes from certain commits (i.e. ones with the [skip ci] tag). Files that change in those commits don't effect storybook results (at least for us).

I think this would be the preferred direction. We don't want snapshots to be made for these commits even if special files like package.json are modified.

Next step is to create an issue upstream for a feature request for skipping commits like skip tags

repo: ni/nimble


text:
[Question] Customizing the Application

Hello I'm trying to modify Veristand Application Menu and I want to display "Operate" Menu.
Could you let me know which command should I use?

or I would like to use  "Deploy" tool below

I tried add "MenuPathCommand.RunMenu.UniqeId" in _allowedCommands but it dose not work.

I'm really appreciated if you help me out how to modify deployment menu.

Hello,
As you've identified, the editor customization example uses CustomApplicationFeatureSet.CanExecuteCommand to hide all commands that have not been explicitly permitted by the _allowedCommands set when the HideEditor preference has been enabled. Given that configuration, the following entries would need to be added to _allowedCommands in order to show the Operate menu and its contents:
VeriStandCommands.OperateMenu.UniqueId,
VeriStandCommands.DeployCommand.UniqueId,
VeriStandCommands.UndeployCommand.UniqueId,
Shell.ProjectCommands.GatewayConnectCommand.UniqueId,
Shell.ProjectCommands.GatewayDisconnectCommand.UniqueId,

Thanks very much for your support.
I tried to add Commands which you mentioned, and It works well.
Can I ask two more questions regarding Custom Application?

Which command should I use to enable "Zoom" function of Veristand.

Can I customize "Window Title and Icon" of Custom Veristand Application as like Splash Screen customization?

thanks very much for your help
Best regard

Hello,
The following command IDs can be added to the same set that was referenced earlier in order to allow Zoom within the product:
DocumentCommands.Zoom.UniqueId,
DocumentCommands.AutoFitZoom.UniqueId,
DocumentCommands.FitToSelectionZoom.UniqueId,
ZoomControl.SelectZoomLevelCommand.UniqueId,

Regarding your second question, that functionality is beyond the current scope of this set of examples.

authors: hunter-ni trionix-hiro

repo: ni/veristand-editor-plugin-examples


text:
why streamlit_antd_components can't work with extra_streamlit_components or Streamlit-Cookies-Controller

streamlit_antd_components : VERSION__ = "0.3.2"
extra_streamlit_components：pip3 install extra_streamlit_components
if __name__ == '__main__':
    st.set_page_config(page_title="人资共享业务系统", page_icon='📈', layout='wide', initial_sidebar_state='expanded')
    cookie_manager = CookieManager()
    cookies = cookie_manager.get_all()
    modified = sac.Tag('修改密码', color='blue', bordered=False)

it will be full blank ，please help!

Same for me. If CookieController is used in the app, the 'antd_components' wizard is totally blank.
Please help if possible.

authors: DrLuRen thebergz

repo: nicedouble/StreamlitAntdComponents


text:
本地运行问题

src/helper/nodemailer.js 文件中4、5行引入的./../config/secret 没有secret文件
注册功能无法使用
3./api/getSysConf 404,这个接口做什么用的？

其实，这个库已经未在维护了；对于 secret 文件，可以创建一个 secret .js，内容格式如下即可。
module.exports = {
  email_163: {
    account: 'your-163-account',
    password: 'your-163-pwd',
  },
  email_qq: {
    account: 'your-qq-account',
    password: 'your-qq-pwd',
  }
}

/api/getSysConf  这个接口使用来拉取后台系统配置的；可以参见 nicelinks.site 请求。

感谢，想咨询一下如果在本地运行 nicelinks-vue-client, 方便更好的学习。后端应该怎么部署？感谢

@jessjava 可以运行此项目 npm run start，当然前提是需要手动安装并打开 MongoDb 和 Redis。

authors: jessjava nicejade


text:
Allow continue-on-error for use in composite actions

From @czifro on a previously closed issue:
I think there's a valid case now to support this in action. With the rollout of improved composite actions: https://github.blog/changelog/2021-08-25-github-actions-reduce-duplication-with-action-composition/ , there is no way to specify continue-on-error. Furthermore, composite actions don't support if: failure(), so it is not possible to have failure tracks in composite actions.
Originally posted by @czifro in https://github.com/nick-invision/retry/issues/11#issuecomment-925268683

@czifro continue_on_error input has been added and merged.

repo: nick-invision/retry


text:
typo fix

Hello! I found a very small typo in the popup.

Hey @Hello9999901, I appreciate the heads-up! This branches here are a bit behind at the moment but I've put a fix in my current dev branch and deployed from that 👍

repo: nickcoutsos/keymap-editor