text:
[Addition]: Hummingbird Cluster (9HS)

Hotspot b58 Addresses
1126fuqYUGwCMNUs6yyVWAfwKpoG39qgY6MuoAW9dvJssVNL5bcs
112BhvSw95PK85iXHjQEMLKfS2xLNSmVX2e27UUwv1cGAYmZhgPU
112fbNQcHfTFiptxbuDZXeTMJXMu931zUZLfCtSzn3kNajcaBiU8
112HukYpVyrva2bq8YMBKPJvJ21pT57MgAHa9E54GybBJT1mAndg
112j95snCfixRQHXJwKHvfT64qZoiKRSKGpnec6BwEasvwLWwdPw
112Y76CwTrdre1AzJZ7vkA5ik416Epz2BZka8C1Zrw61h4QKAvSa
11HE4BzSxW7Ug6JrMz4GAMqdKZ3MYqLdudZ7p3QpqHnP8dFCaVP
11o3ib4jvgpcfHaT1djXgvSD9VEXDsTNFXEe3uTQYunpzvDPBZp
11pH4WsosT1MsGoyfMSPJEWGdC4JZdayQR8aFos8PXwRzuoT8cs
Discord Handle
No response
Reason(s)
These Hotspots are only witnessing their own brand, have very often a unlikely (perfect) placement, same assertion date-range(s) and usually there are enough real hotspots arround but these do not get witnessed at all.
High Clustering Coefficient and/or Clique size above the thresholds which are considered normal on the network.
Below some proof of the cluster(s):

作为一个旁观者，我觉得你们对9台机器视为作弊，理由站不住脚。
你怎么证明旁边的机器就是真实的正常的热点？
根据定位形状判断是作弊，证据充分吗，你们能因为黑人把手插进裤兜就果断开枪，所以可以随便判断别人是作弊吗？这代表的是helium官方的态度吗？
而且这批机器也并不是同一时间加入区块的，你们这么判断智能让广大旷工认为你们是为了5G节点而清理一些非嫡系厂商的热点设备。 为什么你们最近这么针对黑豹？ 为什么这么针对中国的热点设备？ 欧洲和美国一大堆作弊的为啥不清理？
用中国的古话说，你们这是掩耳盗铃，继续下去，helium项目将失去人心。

As a bystander, I think you regard the 9 machines as cheating, and the reason is untenable.
How can you prove that the machine next to you is a real and normal hot spot?
Is there enough evidence to judge cheating according to the positioning shape? Can you shoot decisively because the black man put his hand into his trouser pocket, so you can judge others as cheating at will? Does this represent the official attitude of helium?
Moreover, these machines did not join the block at the same time. Your smart judgment made the majority of absentees think that you were cleaning up some hot devices of non affiliated manufacturers for the sake of 5g nodes. Why are you targeting the Panther so much recently? Why is it so targeted at hot devices in China? Why not clean up a lot of cheating in Europe and the United States?
In the old Chinese saying, you are stealing from others. If you continue, the helium project will lose popularity.
报错 笔记

Why do you think this is cheating, and the side is true? Previously, running blockchain requires synchronization, and it is normal for a small region to register at the same time. Why can't you register ten gateways and then go out and install them? I think it's too casual to judge whether cheating is just from behavior. Maybe this person cheated, but I think this way is not rigorous.

In China, not everyone knows the knowledge of blockchain. Most people who know blockchain will buy more and put them in friends or at home. Then it is understandable to register at the same time.

If I have 10 locations to install gateways, why should I choose different brands and register in a few days?

he's a psychopath

Fuck you mom~

Kid whether have a lot of resist stubbornly
Why do the other people read comic strips there
I but Be learning to paint
To this piano talk other people Be playing games
I but Be hiding at home to carry on the back abc
I say I want a huge airplane
I but get an old spiral machine
Why want to listen to the mother's words
You will start knowing these words after growing up
I start to be understand after growing up
Do I why run quicker than other people
Fly higher than the other people
Everyone will see in the future of is all cartoon that I draw
Everyone sings of is all song that I write
The mother's heart she doesn't let you see
Warm matters all in her heart
I am free to have to touch her hand more
The handle knob leads long sleepwalking
Listenning to the mother visits to say goodbye to let her get hurt
Wanting to grow up quickly and quickly then can protect her
It sproutlace in beautiful grey hair happiness
Kindly in the sorcery warmth of angel
Music is your trump card in your future
The in love that that trump card talks
But I don't want to teach you wrong things
Still listen to the mother's words
The old age is in love again
I know you future road
Why clearer than me
You because of too many classmates of studies at this piece of write east to write west
But my suggesting had better listen to a mother, I will study hard
Study hard how can to speak from my mouth
Don't think you lose so want to call you study hard
The mother picks you to want to accept thoroughly to your trouble
Because don't know is I want to tell her I still stay
To I will meet me(Chow Young Fat?)
So you to with classmate show wager absolute being is your father in the future
I can not find the love letter that you write
What you like wants to admit because my willing understand you will lead long her on the drill ground

Point 1: You don't know anything about China. There are no other brand nodes sold in this area, only Hummingbird and Panther, and Panther has been unable to register to the helium network after May 30.There are no other options.
The second point: Do not witness with other nodes, does not necessarily mean that this cluster has the possibility of cheating, other clusters are not cheating? You can look at the distance of the surrounding cluster witness.
The third point:This is just a test to replace satellite communication to complete environmental data monitoring.
The last point: After understanding the Helium network in depth, I found that more than 95%of the world's nodes are cheating. If the project needs to deal with cheating, then when the device joins the helium network, it must be mandatory for the device to use GPS positioning, and can not use manual modification of positioning.
Finally: A person's cognition is limited, and your cognition is not necessarily correct. If you need to prove that others are wrong, then you need to provide more convincing evidence to prove everything you say, notSimple screenshots.I also hope that the Helium project can take every report carefully.

I hope the project party can discuss, what is decentralization? Why decentralize? If a network that can be seized at any time, a network that can be intervened manually, whether there are some insecure factors. So in the future practical application scenario, how can we ensure that the node is not used by some people with ulterior motives to use this reporting mechanism. (Example: commercial espionage or competitors)
At this stage, we do not rule out the possibility of cheating, but look at the entire denylist mechanism from a project perspective. Many people have lost faith in the project. Anyone can be a whistleblower, and there is no cost to whistleblowing. The final determination mechanism is completely centralized to update a denylist. Many people are worried about the data security of the real use of the hulium network in the future and whether the device can run stably on the helium network for a long time without being added to the denylist.


text:
Feature/498 qr add hotspot

Closes #498
TODO: Need to add QR hotspot models and messaging specific to those devices.
Can scan the qr by selecting "QR Hotspot Maker" in the hotspot type list or by using the system camera.
Here's the code I've been working with...

Hi Sir,
Is there a description about the QR code format?
If I want to add a gateway, what information should I provide?
I think  I just need to transfer the information to base64 encoded and create a QR code.
Please advise. Thanks.

@ChunChiehKung it's as follows:
helium://add_gateway/CrUBCiEBGA3C8JRyKndYev4ShcVFw821Vw7pvZDxiDUHIIiX_50SIQCmsAhGVS5c38NyssphK33KatDkC6h1gqA8gQhjgMJ5uyJIMEYCIQCN4Ouytl7WW92Qt6AHlXSQO-FmfoV3sjoHutEykdCR8wIhAPtVs-qAj75G4IxUMe5f9X5lSqpAvkb6XpAba8RCuMRiKiEBGA3C8JRyKndYev4ShcVFw821Vw7pvZDxiDUHIIiX_504AQ
This is a base 64 hash of the following info I believe:

source: gharchive/pull-request

authors: ChunChiehKung matthewcarlreetz shawaj

repo: helium/hotspot-app

license_type: permissive

license_source: github-api


text:
Polling Block seems to fail for me for some reason.

I constantly get this error log when I run the atlas sender. I added more logs to examine what was wrong and it seems poll_slots() is working fine but poll_blocks() doesnt seem to get any geyser messages.

what geyser are you using?

Hey, I was using yellowstone

@harsh4786: the default config doesn't allow to use 'any' when subscribing to blocks: https://github.com/rpcpool/yellowstone-grpc/blob/master/yellowstone-grpc-geyser/config.json#L49C40-L49C45

source: gharchive/issue

authors: Mayeu harsh4786 vovkman

repo: helius-labs/atlas-txn-sender


text:
Routing won't work if methods field is not present in api configuration

By the docs:
https://hellofresh.gitbooks.io/janus/proxy/request_http_method.html
By default, Janus will route a request to an API regardless of its HTTP method.

Unfortunately if I remove methods array from api definition none of methods are accepted and I got a message:
{
    "message": "no API found with those values"
}

Just remove methods from example config to test it out.
Please fix this to state from documentation.
Janus version: latest docker image

@jzyinq Thanks for reporting this. We will work on this a soon as possible

authors: italolelis jzyinq

repo: hellofresh/janus

license: mit

license_source: bigquery


text:
Footer enhancement

Make it something like this:

Social media account links

I would like to work on this😊

authors: anoopjt fahad-israr thisisnitish

repo: helloworld-iiitt/iiitt

license: MIT


text:
[stable/nginx-ingress] 503 on rollback

I've had my nginx-ingress up and running for a while now and tried to upgrade the helm values but it failed so I did a rollback to the previous settings. For reference the upgrade failed due to this issue https://github.com/helm/charts/issues/9227.
The current version I have installed is nginx-ingress-1.1.1
After the rollback all my services were fine apart from 1 which when I do the rollback gives me a 503 error. I've done it twice now and it's always the same service that it happens too.
I can find any errors that would give me any clue to why this is happening, and I only got the service working again after recycling some of the servers and it eventually started working.
I've compared my ingress setup to working services and there is no difference apart from domain names etc.
Can't work out if the issue is the helm chart, the version of ingress-nginx installed by that chart or something I've done wrong. But it seems odd that its the same service although it odder that the service normally runs without issue.
I'm reluctant to try any of the suggestions to get the upgrade working without trying to find out why this keeps happening.

Going to close this as no longer using helm due to the amount of issues it causes.

repo: helm/charts


text:
stable/grafana Datasources added from chart config doesn't work but same datasource added manually works

Describe the bug
I am using stable/grafana chart with some custom config (given below).

grafana:
  rbac:
    create: false
    pspEnabled: false
    pspUseAppArmor: false

  datasources:
    datasources.yaml:
      apiVersion: 1
      datasources:
      - name: Graphite
        type: graphite
        url: http://graphite.monitoring.svc.cluster.local:8080
        access: direct
        isDefault: true

  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.class: nginx
      nginx.ingress.kubernetes.io/rewrite-target: /
      nginx.com/health-checks: "true"
      nginx.ingress.kubernetes.io/enable-access-log: "false"
    hosts:
      - <hostname>

This installs grafana and the default datasource (graphite) is setup. But it doesn't work. If I add the same datasource manually from Grafana UI, it works.
Version of Helm and Kubernetes:
$ helm3 version
version.BuildInfo{Version:"v3.0.3", GitCommit:"ac925eb7279f4a6955df663a0128044a8a6b7593", GitTreeState:"clean", GoVersion:"go1.13.6"}

Which chart: stable/grafana
What happened: Datasource added while deploying chart using custom values.yaml file doesn't work.
What you expected to happen: The datasource added automatically should work.
How to reproduce it (as minimally and precisely as possible):
The environment is as below:
 $ tree setup/grafana/
setup/grafana/
├── Chart.lock
├── Chart.yaml
├── charts
│   └── grafana-5.0.0.tgz
├── templates
│   └── _helpers.tpl
└── values.yaml

2 directories, 5 files
$ cat setup/grafana/values.yaml
# Default values for grafana.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

grafana:
  rbac:
    create: false
    pspEnabled: false
    pspUseAppArmor: false

  datasources:
    datasources.yaml:
      apiVersion: 1
      datasources:
      - name: Graphite
        type: graphite
        url: http://graphite.monitoring.svc.cluster.local:8080
        access: direct
        isDefault: true

  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.class: nginx
      nginx.ingress.kubernetes.io/rewrite-target: /
      nginx.com/health-checks: "true"
      nginx.ingress.kubernetes.io/enable-access-log: "false"
    hosts:
      - <hostname>

Anything else we need to know:
graphite is already installed in using https://github.com/kiwigrid/helm-charts/tree/master/charts/graphite

This issues appears to have been introduced with this PR: https://github.com/helm/charts/pull/20985 and a possible workaround is to declare the previous configuration for the datasource sidecar in the extraInitContainers section.
The reason for the regression is the sidecar responsible with pulling the datasource configuration from configmap/secret objects has been moved from initContainers to containers, but Grafana only appears to provision datasources at startup.

It’s possible to manage datasources in Grafana by adding one or more yaml config files in the provisioning/datasources directory. Each config file can contain a list of datasources that will be added or updated during start up. If the datasource already exists, Grafana will update it to match the configuration file. The config file can also contain a list of datasources that should be deleted. That list is called deleteDatasources. Grafana will delete datasources listed in deleteDatasources before inserting/updating those in the datasource list.

We're also waiting for this PR to fix the Grafana chart so we can update.
Thanks @dvulpe 👏

authors: Annegies dvulpe shubhambhattar


text:
[stable/hazelcast-jet] Updated product logo

What this PR does / why we need it:
Updated product logos to match with the company branding.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/approve

/lgtm

authors: eminn leszko


text:
[stable/rabbitmq] Environment variables in rabbitmq container

What this PR does / why we need it:

env variables: some rabbitmq configuration is done through env variables. For example it might be necessary to control the CONFIG_FILE variable, when using an image that isn't based on the default bitnami image

Special notes for your reviewer:
This is very similar to #14932 for the rabbitmq-ha chart.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @tompizmor

/ok-to-test
/lgtm

authors: PaulFarver carrodher


text:
[stable/concourse] Bump imageTag to match actual released version

Signed-off-by: pikesley sam.pikesley@demandlogic.co.uk
What this PR does / why we need it:
This values.yaml is for the 5.5.0 release of Concourse, but it still has
imageTag: "5.4.1"

Checklist

[x] DCO signed
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

daamnnn that's true! thank you!

@pikesley , seems like the bot is still not satisfied with your DCO signature 🤔

/lgtm

👍

authors: cirocosta pikesley


text:
[stable/dex] Enabling CRDs creation using the chart

Is this a new chart
No
What this PR does / why we need it:
Main motivation: as stated in https://github.com/dexidp/dex/issues/1513 sometimes creating CRDs is an administrative action, which will be done in separated from installing the app using those CRDs. In this PR I'm enabling using this chart to create ONLY the CRDs.
Changes + explanations:

adding the deploy value - the only missing "knob" to enable creating only the CRDs (other resources already have knobs like rbac.create, serviceAccount.create etc...)
adding the crd.install value - this PR enables CRDs installation and support both helm v2 and v3 (see https://github.com/helm/charts/issues/19008), this value is the v2 way of installing CRDs.
replacing crd.present with crd.appInstall (its negation) - mainly to prepare the ground for https://github.com/dexidp/dex/pull/1522, and also I think it will be less confusing than having both crd.install and crd.present

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @desaintmartin

After doing some testing I've discovered that in helm3 it is currently impossible to install only CRDs (https://github.com/helm/helm/issues/7537) closing this until it will be fixed


text:
[stable/prometheus-mysql-exporter] Add ServiceMonitor metricRelabeling

Signed-off-by: Calvin Bui 3604363+calvinbui@users.noreply.github.com
What this PR does / why we need it:
Adds the ServiceMonitor metricRelabelings key as documented in the Prometheus Operator API.
Used for adding, dropping or renaming labels at ingestion time, or to drop entire metrics that are not useful.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @monotek

/ok-to-test

authors: calvinbui monotek


text:
Allow calling helm from go

I would like to embed helm inside a cli program that I'm writing
many cli programs, specially ones written using cobra, allow me to do that like this:
package tools

import (
	k3d "github.com/k3d-io/k3d/v5/cmd"
	"github.com/spf13/cobra"
	kubectl "k8s.io/kubectl/pkg/cmd"
)

var ToolsCmd = &cobra.Command{
	Use:   "tools",
}

func init() {
	ToolsCmd.AddCommand(k3d.NewCmdK3d())
	ToolsCmd.AddCommand(kubectl.NewDefaultKubectlCommand())
	RootCommand.AddCommand(ToolsCmd)
}

When I try to do the same for helm I get the flowing error:
import "helm.sh/helm/v3/cmd/helm" is a program, not an importable package

In order to support this for helm, the main file (named helm.go in this case) needs to be separated from the rest of the code.

I don't really know the legacy behind this structure, but per hip-0004 it cannot be changed before Helm 4.

authors: arikmaor joejulian

repo: helm/helm


text:
Charts should indicate what API/version they require

e.g. v1, v1beta1.
For the first pass, we could use flags like this to alert the user that they must have particular things enabled on their cluster. Combined with @rimusz's suggested helm show command, the user would be able to quickly check what particular things a Chart needed to create.
Example Chart.yaml might be something like this. Assume we have a chart that does the pi job, as described in the k8s documentation. It uses a kind: Job, which is v1beta. And say our chart also uses storage, which i sv1
name: pi
apiVersions:
    - v1
    - v1beta1
version: 0.1.0
description: ...
# ... rest of chart is normal

We could treat certain apiVersions as stable (e.g. v1), and others as unstable (v1beta1), and so issue a warning for the above:
$ helm fetch pi
---> Warning: this chart requires a Kubernetes server with v1beta1 api support.

In the future, we might be able to probe the k8s cluster to determine some useful information pre-install.

+1

With possible addendum for declaring which specific experimental API groups a chart requires: extensions/v1beta1/deployments, extensions/v1beta1/jobs
http://kubernetes.io/v1.1/docs/api.html#api-groups

What would we do with this information?  Check kubectl version and warn? If so, when?  I'm not sure we need this if we have #274.

@gabrtv @slack I just updated the description. I like @slack's idea of maybe allowing individual extensions.

@technosophos thanks for the added clarity. I'm :+1: on using this to issue warnings for experimental extensions / APIs.

The future of Helm is at kubernetes/helm. Helm Classic is in maintenance mode, so I'm closing this enhancement request.

authors: gabrtv mboersma rimusz slack technosophos


text:
Rendering error when using range function along with --set

Output of helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Bare Metal
When using range to loop over env values, rendering will fail if I'm overriding values with --set as seen below.
more values.yaml
image:
  repository: alpine
  tag: latest
  pullPolicy: IfNotPresent

env:
- name: a
  value: 1
- name: b
  value: 2
- name: c
  value: 3

more template.yaml
apiVersion: v1
kind: Pod
metadata:
  name: {{ include "chart.fullname" . }}
spec:
  containers:
    - name: {{ .Chart.Name }}
      image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
      imagePullPolicy: {{ .Values.image.pullPolicy }}

      env:
      {{- range .Values.env }}
      - name: {{ .name }}
        value: {{ .value | quote }}
      {{- end }}

helm install --dry-run --debug .
[debug] Created tunnel using local port: '35057'

[debug] SERVER: "127.0.0.1:35057"

[debug] Original chart version: ""
[debug] CHART PATH: /root/chart-dwcel_edl/chart-ticket

NAME:   killjoy-deer
REVISION: 1
RELEASED: Fri Dec 21 16:34:15 2018
CHART: dwcel_edl-0.1.0
USER-SUPPLIED VALUES:
{}

COMPUTED VALUES:
env:
- name: a
  value: 1
- name: b
  value: 2
- name: c
  value: 3
image:
  pullPolicy: IfNotPresent
  repository: alpine
  tag: latest
replicaCount: 1

HOOKS:
MANIFEST:

---
# Source: dwcel_edl/templates/template.yaml
apiVersion: v1
kind: Pod
metadata:
  name: killjoy-deer-dwcel_edl
spec:
  containers:
    - name: dwcel_edl
      image: "alpine:latest"
      imagePullPolicy: IfNotPresent

      env:
      - name: a
        value: "1"
      - name: b
        value: "2"
      - name: c
        value: "3"

helm install --dry-run --debug --set env.a="0" .
[debug] Created tunnel using local port: '33575'

[debug] SERVER: "127.0.0.1:33575"

[debug] Original chart version: ""
[debug] CHART PATH: /root/chart-dwcel_edl/chart-ticket

Error: render error in "dwcel_edl/templates/template.yaml": template: dwcel_edl/templates/template.yaml:13:17: executing "dwcel_edl/templates/template.yaml" at <.name>: can't evaluate field name in type interface {}

Hey,
--set env.a="0" equals to:
env:
a: "0"
That is probably why the rendering fails for {{ .name }}.
Not sure how to pass a value to an object in an array , but this doesn't seem like an issue to me.
Hope this helps!

Indeed, got some interesting information about this in #1987, thanks

authors: chobolt maorfr


text:
fix(chartutil): Create with seperated registry and repository

closes #12514
What this PR does / why we need it:
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

please take a look @z4ce


text:
Adding backticks for readability

Signed-off-by: Bridget Kromhout bridget@kromhout.org
What this PR does / why we need it:
If you navigate to https://docs.helm.sh/helm/#helm and scroll down a little, you'll see a difficult-to-read paragraph.

Looking at the raw file(https://github.com/helm/helm/blame/master/docs/helm/helm.md#L23-L36), it seems likely it should be rendered literally. This does come with the disadvantage of side-scrolling, but I think it would be an improvement over the current situation.
Special notes for your reviewer:
If applicable:

[X] this PR contains documentation

Ah, thanks, @bacongobbler, for your out-of-band explanation (that as we generate these files, this isn't the right place to add formatting).

@bridgetkromhout @bacongobbler What was the outcome of the discussion? Is there a fix being worked on?  Just wondering as #5344 is open referencing this PR.

authors: bridgetkromhout hickeyma


text:
Feature/add version to helm list

What this PR does / why we need it:

[x] Add field AppVersion to output of helm ls
[x] closes #6529

If applicable:

[x] this PR contains unit tests
[x] this PR has been tested for backwards compatibility

Seems fairly straightforward. LGTM! As this has been marked a size/L, it will need another maintainer's review. Thanks for the contribution!

Pulling this into the beta milestone as it is a missing feature from Helm 2. Will be reviewing soon


text:
New chart request - LOGIQ.ai chart and maintainer details

Requesting addition of LOGIQ helm chart to hub

@rparth The Artifact Hub is live. You can also list your Helm repos there. To do that, you login (or create an account), and list your repository. You can link it to a user or organization.

@mattfarina Thanks!. I pushed to artifact hub as well. Love artifact hub, It's looking very slick and much needed. Great to see things like Falco rules making it in a central repository.

authors: mattfarina rparth

repo: helm/hub


text:
Implemented dark theme

From issue #51

Created a new SCSS partial for managing theme color: _color.scss
Moved all color properties from style.scss to the new color partial
Added a new flag in _config.yml to set the dark theme

Let me know if there is anything else to change :smile:

Hello Astronaut!
Thank you for your contribution!
I'll be merging the cool stuff you brought to Gravity soon!

Super Awesome! Thank you so much for this PR :)

ack 1c400a8 48d902b

authors: hemangsk qgolsteyn

repo: hemangsk/Gravity


text:
🛑 hentaiOS Mail is down

In b5b0dff, hentaiOS Mail (https://mail.hentaios.com) was down:

HTTP code: 502
Response time: 436 ms

Resolved: hentaiOS Mail is back up in d36e770.


text:
Update envoyproxy/go-control-plane

See if there is a newer version of go-control-plane. Beware that the latest go-control-plane may require a newer envoy than 0.11's envoy 1.9.0.

Upgraded to 0.6.8. 0.6.9 introduces some data structure changes so I think we'll punt on those til 0.12 or the next envoy upgrade.

repo: heptio/contour


text:
apis: Fix IngressRoute struct missing omitempty

This fixes #713 by updating the IngressRoute struct to add omitempty to json params so that any params not supplied do not throw errors when integrating with golang.
Other change is the Delegate struct is now a pointer so that we can add omitempty and make that optional. Tests / builder.go have been updated to reflect change.

Per your recommendation in the Kubernetes slack I copied ingressroute.go into my vendors folder and gave it a try. It resolved the omitempty issues.

We're not going to backport this to 0.6.1 because this PR is based on the move of ingressroute to apis/ in #704

authors: amoskyler davecheney stevesloka


text:
Add prioritized resource list for backups

Similar to restores, backups should be able to process resources in a well-defined order.

Is there some documentation around how to prioritize resources on restore?

I see the default list, but It's not obviout to me how to extend this to support custom resources.
https://github.com/heptio/velero/blob/4583aa707821f5860b09b67cc091b70d504e1385/pkg/cmd/server/server.go#L440

It's a flag to velero server: https://github.com/heptio/velero/blob/73514a003b4cdaf1feed4e0976cff5a3400e4405/pkg/cmd/server/server.go#L167

Awesome, thank you @ncdc!

Thanks for this request. We are not currently prioritizing this item within our roadmap, and as such will be closing out the issue. Please feel free to reach out as needed in this issue or a new one.

authors: dymurray ncdc skriss

repo: heptio/velero


text:
Create a logging interface to use instead of logrus.FieldLogger

If we do this, we'll modify every place that references a logrus.FieldLogger once, replacing it with our interface. Then, if we need to swap out the logging implementation, it will be consolidated to a small set of files, instead of all over the entire repository.

Thanks for this request. We are not currently prioritizing this item within our roadmap, and as such will be closing out the issue. Please feel free to reach out as needed in this issue or a new one.

authors: ncdc skriss


text:
feat: change location os tests files

Change the folder of test files in command herbs new to work with new feature in herbarium: https://github.com/herbsjs/herbarium/pull/7

Proposed Changes

Change location of test files

Readiness Checklist
Author/Contributor

[ ] If documentation is needed for this change, has that been included in this pull request
[ ] Remember to check if code coverage decrease, if so, please implement the necessary tests

Reviewing Maintainer

[ ] Label as breaking if this is a large fundamental change
[ ] Label as either automation, bug, documentation, enhancement, infrastructure, or performance

I'm having a problem with an error.
For some reason, the first element of the for is undefined, which causes this error to happen.
D:\Documentos\Programacao\herbs\herbs-cli\node_modules\gluegun\build\index.js:15
    throw up;
    ^

TypeError: usecasesGroup[groupName] is not iterable
    at Command.run (D:\Documentos\Programacao\herbs\herbs-cli\src\commands\spec.js:41:49)
    at Runtime.<anonymous> (D:\Documentos\Programacao\herbs\herbs-cli\node_modules\gluegun\build\runtime\run.js:119:58)    at step (D:\Documentos\Programacao\herbs\herbs-cli\node_modules\gluegun\build\runtime\run.js:44:23)
    at Object.next (D:\Documentos\Programacao\herbs\herbs-cli\node_modules\gluegun\build\runtime\run.js:25:53)
    at fulfilled (D:\Documentos\Programacao\herbs\herbs-cli\node_modules\gluegun\build\runtime\run.js:16:58)
PS D:\Documentos\Programacao\herbs\debug-issue-6\teste6>

However, in the spec.js file, by adding the following code after line 40:
if(usecasesGroup[groupName] === undefined) continue

The tests in the created project work...

@vitorgamer58 as discussed, we are not changing the defaults for a new project.
The only thing we are open to discuss is how CLI / herbarium can accept a different folder as a parameter to the default when herbs update or herbs spec.

@vitorgamer58 as discussed, we are not changing the defaults for a new project.
The only thing we are open to discuss is how CLI / herbarium can accept a different folder as a parameter to the default when herbs update or herbs spec.

Different folder as a parameter, Ok.

@vitorgamer58 as discussed, we are not changing the defaults for a new project.
The only thing we are open to discuss is how CLI / herbarium can accept a different folder as a parameter to the default when herbs update or herbs spec.

Different folder as a parameter, Ok.

repo: herbsjs/herbs-cli


text:
Fix animated extrusion direction.

Fixes regression introduced by #1119 caused by incorrect clamping of
extrusion ratio of not flat buildings.
Related-to: HARP-8421, HARP-8279

Codecov Report

Merging #1205 into master will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1205      +/-   ##
==========================================
- Coverage   51.75%   51.65%   -0.11%
==========================================
  Files         259      247      -12
  Lines       22999    22751     -248
  Branches     5116     5073      -43
==========================================
- Hits        11904    11752     -152
+ Misses      11095    10999      -96

Impacted Files
Coverage Δ

...harp-materials/lib/ShaderChunks/ExtrusionChunks.ts
100% <ø> (ø)
:arrow_up:

...re/harp-text-canvas/lib/rendering/TextMaterials.ts
50% <0%> (-26.93%)
:arrow_down:

@here/harp-mapview/lib/ThemeHelpers.ts
6.55% <0%> (-0.68%)
:arrow_down:

...rp-mapview/lib/text/TextElementsRendererOptions.ts
100% <0%> (ø)
:arrow_up:

@here/harp-datasource-protocol/lib/Outliner.ts
100% <0%> (ø)
:arrow_up:

...ere/harp-materials/lib/LuminosityHighPassShader.ts
100% <0%> (ø)
:arrow_up:

@here/harp-test-utils/lib/WebGLStub.ts
100% <0%> (ø)
:arrow_up:

@here/harp-omv-datasource/lib/clipPolygon.ts
100% <0%> (ø)
:arrow_up:

...p-geoutils/lib/tiling/QuadTreeSubdivisionScheme.ts
100% <0%> (ø)
:arrow_up:

@here/harp-utils/lib/Mixins.ts
70% <0%> (ø)
:arrow_up:

... and 29 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 1d1f33c...455305f. Read the comment docs.

authors: codecov-io zbigg


text:
Makes TextElementsRenderer update- and reset-able

Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

@harpgl-bot retest this please


text:
Heroku login does not pass exit code back

Heroku login exit code is 0 on authentication failure
% heroku login
Enter your Heroku credentials.
Email: test
Password (typing will be hidden):
 ▸    Authentication failure.
% echo $?
0

Is there a way to have the authentication failure reflected on the exit code?
The --exit-code option mentioned in #186 only works for heroku run

fixed here, https://github.com/heroku/heroku-cli/pull/102 will go out with the next release

thanks :+1:

authors: TDaglis dickeyxxx

repo: heroku/heroku


text:
heroku status should fail gracefully when status is down

[12:15:50] <bau> hi all, when i type: heroku status on ubuntu I have this error: === Heroku Status
[12:15:50] <bau> /usr/local/heroku/lib/heroku/command/status.rb:26:in `index': undefined method `[]' for nil:NilClass (NoMethodError)
[12:15:50] <bau> from /usr/local/heroku/lib/heroku/command.rb:167:in `run'
[12:15:50] <bau> from /usr/local/heroku/lib/heroku/cli.rb:9:in `start'
[12:15:50] <bau> from /usr/bin/heroku:30:in `<main>'

it does now

but this is super old so that's not surprising

authors: ddollar dickeyxxx


text:
🛑 Software Center - Test 1 is down

In 1a28dc4, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in cea6354.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In 06bca70, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 077de38.


text:
🛑 Auth-Bridge - Test 1 is down

In b7b0fdb, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 7fff893 after 28 minutes.


text:
🛑 Software Center - Test 1 is down

In 8b49d81, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d1a76fd after 10 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In b0ac2e6, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in ccddcdc after 30 minutes.


text:
🛑 Software Center - Test 1 is down

In a60970d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 4ef5f94 after 10 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In a613717, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 3eadfae after 1 hour, 12 minutes.


text:
🛑 Software Center - Test 1 is down

In 3f89abb, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in fd0c2cb after 21 minutes.


text:
🛑 Software Center - Test 1 is down

In 878900e, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 5a370e4 after 10 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 9365d35, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in c9c0539 after 11 minutes.


text:
🛑 Software Center - Test 1 is down

In 8616c86, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 96d273f after 29 minutes.


text:
🛑 Software Center - Test 1 is down

In 06973b0, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 8aaf8b1 after 43 minutes.


text:
🛑 Software Center - Test 1 is down

In 9d97d45, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in a97e180 after 1 hour, 6 minutes.


text:
🛑 Software Center - Test 1 is down

In c027e7d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in a6686d7.


text:
🛑 Auth-Bridge - Test 1 is down

In 4afc3aa, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in f863544.


text:
🛑 Auth-Bridge - Test 1 is down

In a0307a0, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in cad6356.


text:
🛑 Software Center - Test 1 is down

In abe7bac, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 0058273.


text:
use security scheme configuration

Describe the problem
OpenAPI allows to specify authentication/authorization details in so-called "security schemes" for each request. Examples are Basic Auth, Bearer Auth, API Keys, OAuth2 or OIDC. see https://swagger.io/docs/specification/authentication/
openapi-ts currently seems to ignore the specified authentication methods and currently always sends user/password (Basic Auth) or token (Bearer Auth), no matter whether the API supports the respective authentication type or whether the API requires authentication at all. It uses a global configuration which is used for every request, even if it doesn't require authentication.
For security reasons one might want to avoid sending the user/password (Basic Auth) or token (Bearer Auth) to every endpoint of the API.
Describe the proposed solution
Ideally openapi-ts should respect the security scheme configuration specified in the API specification and only use the authentication types which are specified for the respective request.
Alternatives considered
A possible alternativ solution is to use a custom interceptor, that knows about the authentication schemes and adds the authentication data, instead of using the global OpenAPIConfig provided by openapi-ts.
Downside: authentication scheme mapping needs to maintained separately from OpenAPI spec
Importance
potential security issue; nice to have
Additional information
No response

@swurzinger thanks for creating this issue. I was actually just thinking about this a couple days ago. Would be a great feature.

Note: we also have a ticket about passing schema to interceptors. That would allow for your alternative solution. However, I think we should properly support it internally.

In general that's fine I guess, as authentication can be highly customized in many real-world applications. In my specific case that wouldn't currently work due to the missing request interceptor support for angular clients, though. Is it expected to use HttpInterceptor there?

@swurzinger Yes, you would likely want to use that. I would like to provide better first class support, but I need to do more research into angular itself.

Thanks for the issue @swurzinger and as mentioned above, if you can provide any pointers on Angular clients, that'd be great, as neither one of us is familiar with that ecosystem at the moment

Hey, I'd love to see a proper way to add authentication.
In my mind it would be great if we could have an interceptor for auth which provides the name of the security scheme and the string returned from the interceptor is then placed in the right spot.
I think it fair to view the authentication types as two groups of types:

The OIDC and OAuth types have to be executed and afterwards the token can be extracted without any user interaction
The http and apiKey types rely on a token/key provided by the user and put them somewhere (cookie, header, query, etc.)

Having an interceptor for auth would support the 2nd group of types (http and apiKey) whilst the authentication for the other types could be implemented in another turn to run fully internally.
Let me know what you think of this idea

@WhySoBad sounds like there's something to it, can you show an example API how this would work?

I'm imagining an API similar to the request interceptor described here https://heyapi.vercel.app/openapi-ts/interceptors.html
import { client } from '@hey-api/client-fetch';

client.interceptors.auth.use((scheme, request, options) => {
  if (scheme === "BasicAuth") {
    // get basic auth credentials and return them as a string
  } else if (scheme === "Bearer") {
    // get bearer token and return it as a string
  }
  return null;
});

When returning null or any other falsly value the request can be cancelled on the client side since it would fail anyways (as by the spec the endpoint needs auth).

@WhySoBad so I understand, you'd want to automate the credentials management?

Uh I don't really know what you mean by credentials management. This should be a hook which is called before any request which has an authentication scheme registered.

Is it painful to write this manually yourself?

Do you mean to implement it myself for this library or to have authentication without such a hook? For the latter I have to write down all urls which don't need authentication and check in the request interceptor whether the request is going to one of those locations.

Gotcha. That makes sense, thanks for the context!

I agree in several points:

security scheme configuration from the openAPI spec is missing at runtime and would be needed for proper auth integration
an interceptor is probably the best way for handling authentication, it shouldn't be directly integrated in the client (which currently only supports basic auth anyways and ignores security scheme configuration)
For Angular there's request and response metadata. For this project's custom interceptors (which aren't supported for Angular) adding a new parameter to the signature as suggested by @WhySoBad is probably fine, although I wouldn't put it first and wrap it in options. I'm not sure whether it would make sense for the library to provide default implementations for e.g. BasicAuth or Bearer Auth as they are trivial to implement (just set a header) and the token acquisition/refresh logic needs a customized implementation anyway.

Some also use a custom Authorization scheme type as well:
https://stackoverflow.com/questions/59694733/how-to-define-the-authorization-header-with-a-custom-prefix-in-openapi-3

Are there any plans 'bout this issue? I'm interested in implementing it. For now this problem is show-stopper for me in migration from openapi-typescript-codegen, cause I implemented this feature in my fork and added security scheme to token resolver arguments

@MrFox131 yes, but I'd be looking to implement it only for client packages. If you're working with legacy clients, which it sounds like you are, feel free to port your implementation from openapi-typescript-codegen to this codebase!

Hey all, this will be available in the next release, or you can try it directly from the mentioned pull request above. It's an initial attempt at implementing this feature so it misses a lot of cases, but do give it a try and let me know what works/doesn't work. Thanks!

authors: MrFox131 WhySoBad jordanshatford mrlubos swurzinger theogravity

repo: hey-api/openapi-ts


text:
大佬真牛逼啊

向大佬学习

大佬真牛

厉害了

感谢

repo: heyanLE/EasyBangumi


text:
Extended "plugin" interface

We can extend the plugin interface in a backward compatible way to support several application phases:

Support app.initialize(). Once all plugins are loaded, the initialize method can be called. This method will in turn call every plugin which returned a method called initialize from its construction function. The method can return a promise.

Support app.terminate(). Similar to initialize but it will shut all plugins down. Analogously to initialize it will call a termination method on all plugins that have one

My main doubt about this design is how to make it clear which things go where, especially the config vs initialization phases. Perhaps we could support passing an object to load() in addition to a function - if an object is passed, it has to at least have an initialize method (that can return a promise), and it can optionally have a configuration getter that returns the env variables specs (once loaded it will be replaced with a cached property) as well as a terminate method (that can return a promise)

new Load method:
load(plugin: (app:App)=>void | { configure(app:App):void; load(app:App) => void})
Not sure if good idea to give access to the entire app in configure. Maybe just envaridator?

If its just envaridator, you'd probably need this interface:
interface ConfigururablePlugin<T, U> {
  configure(env: Envaridator):T;
  create(app: App, config:T):U;
}

Another alternative making it easier to fetch this
class MyConfiguration extends ConfigSingleton {
var1 = this.env.register('name', {...})
var2 = this.env.register('name', {...})
var3 = this.env.register('name', {...})
}
app.loadConfigurable({
configuration: MyConfiguration,
create: app => {
app.getSingleton(MyConfiguration) // works anywhere
}
});


text:
The Last Problem Problem Code: TLAPM

Link-  https://www.codechef.com/COOK129B/problems/TLAPM
Language - C++
Please assign me this as a part of hacktober fest.

Can you please assign this @hhhrrrttt222111


text:
Remove reliance on files as much as possible

You should use io.Reader and io.Writer as much as possible to make your library usable in multiple scenarios.
Also for extraction, leave out the file naming and what to do with the exracted content to the library user.
Here is how I managed to do it for Image extraction:
// PDFImageType describe the image file extension
type PDFImageType string

const (
	// JPG jpeg image
	JPG PDFImageType = ".jpg"
	// JPX jpx image
	JPX PDFImageType = ".jpx"
)

// PDFImage provides the content and image format by its extension
type PDFImage struct {
	Body []byte
	Name string
	Type PDFImageType
}

// ExtractImages extracts images to a channel
func ExtractImages(ctx *types.PDFContext, out chan (PDFImage)) {
	for _, i := range sortIOKeys(ctx.Optimize.ImageObjects) {
		ExtractImage(ctx.Optimize.ImageObjects[i], out)
	}
	close(out)
}

// ExtractImage sends image body, ressource name and type to a channel
func ExtractImage(obj *types.ImageObject, out chan (PDFImage)) {
	imageDict := obj.ImageDict

	fp := imageDict.FilterPipeline

	if fp != nil {
		// Ignore imageMasks
		if im := imageDict.BooleanEntry("ImageMask"); im != nil && *im {
			return
		}

		switch fp[0].Name {
		case "DCTDecode":
			out <- PDFImage{Body: imageDict.Raw, Name: obj.ResourceNamesString(), Type: JPG}
		case "JPXDecode":
			out <- PDFImage{Body: imageDict.Raw, Name: obj.ResourceNamesString(), Type: JPX}
		}
	}
}

And then I use it like this:
	var err error
	config := types.NewDefaultConfiguration()
	config.DecodeAllStreams = false

	ctx, err := read.PDFFile("data/somefile.pdf", config)
	if err != nil {
		panic(err)
	}

	err = validate.XRefTable(ctx.XRefTable)
	if err != nil {
		panic(err)
	}

	err = optimize.XRefTable(ctx)
	if err != nil {
		panic(err)
	}

	images := make(chan (pdfextract.PDFImage))
	go pdfextract.ExtractImages(ctx, images)
	for img := range images {
		log.Println(img.Name + string(img.Type))
		// Here you could save the images to files, put them on an object store like S3 or Openstack Swift, resize, crop...
	}

I am aware of this issue and it has high priority. I take it as a reminder.. Too much focus has been on my CLI. Thanks!

For my use case, I would like to be able to stream image objects directly to an object storage, without loading it in memory nor saving it to a temporary file first.
The best approach would be to have a forward only reader in the first place, like SAX is for XML parsing. You can build all the other layers on top of it.
SAX parsing

The processing of extracted data is not within scope of the pdfcpu library.
A layer that writes extracted data (in SAX fashion) to an io.Writer (optionally using channels) may be implemented on top of pdfcpu's API.
I therefore close this issue as being taken care of by the redesigned extraction api of release v0.1.9

authors: Scapal hhrutter

repo: hhrutter/pdfcpu


text:
onGetLayoutInflater() cannot be executed until the Fragment is attached to the FragmentManager

Exception java.lang.IllegalStateException: onGetLayoutInflater() cannot be executed until the Fragment is attached to the FragmentManager.
at androidx.fragment.app.Fragment.getLayoutInflater (Fragment.java:1673)
at androidx.fragment.app.Fragment.onGetLayoutInflater (Fragment.java:1622)
at androidx.fragment.app.Fragment.performGetLayoutInflater (Fragment.java:1654)
at androidx.fragment.app.Fragment.getLayoutInflater (Fragment.java:1639)
at com.hi.dhl.binding.viewbind.FragmentViewBinding.getValue (FragmentViewBinding.kt:51)
at com.aly.ticktube.ui.fragment.VideoFragment. (VideoFragment.kt:39)
at com.aly.ticktube.ui.fragment.VideoFragment.access$getMFragment (VideoFragment.kt:37)
at com.aly.ticktube.ui.fragment.VideoFragment$initView$6$1.onAnimationEnd (VideoFragment.kt:123)
at android.animation.AnimatorSet.onChildAnimatorEnded (AnimatorSet.java:829)
at android.animation.AnimatorSet.-wrap1 (AnimatorSet.java)
at android.animation.AnimatorSet$AnimatorSetListener.onAnimationEnd (AnimatorSet.java:784)
at android.animation.ValueAnimator.endAnimation (ValueAnimator.java:1153)
at android.animation.ValueAnimator.doAnimationFrame (ValueAnimator.java:1313)
at android.animation.AnimationHandler.doAnimationFrame (AnimationHandler.java:146)
at android.animation.AnimationHandler.-wrap2 (AnimationHandler.java)
at android.animation.AnimationHandler$1.doFrame (AnimationHandler.java:54)
at android.view.Choreographer$CallbackRecord.run (Choreographer.java:928)
at android.view.Choreographer.doCallbacks (Choreographer.java:705)
at android.view.Choreographer.doFrame (Choreographer.java:637)
at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:916)
at android.os.Handler.handleCallback (Handler.java:751)
at android.os.Handler.dispatchMessage (Handler.java:95)
at android.os.Looper.loop (Looper.java:154)
at android.app.ActivityThread.main (ActivityThread.java:6816)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1565)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1453)

FragmentViewBinding 里面代码为
`class FragmentViewBinding(
classes: Class,
fragment: Fragment
) : FragmentDelegate(fragment) {
private val layoutInflater = classes.inflateMethod()
private val bindView = classes.bindMethod()

override fun getValue(thisRef: Fragment, property: KProperty<*>): T {
    return viewBinding?.run {
        return this

    } ?: let {

        try {
            /**
             * 检查目的，是为了防止在 onCreateView() or after onDestroyView() 使用 binding。
             * 另外在销毁之后，如果再次使用，由于 delegate property 会被再次初始化出现的异常
             *
             * 捕获这个异常的原因，是为了兼容之前的版本，防止因为升级，造成崩溃
             */
            check(thisRef.viewLifecycleOwner.lifecycle.currentState.isAtLeast(Lifecycle.State.INITIALIZED)) {
                "cannot use binding in before onCreateView() or after onDestroyView() from 1.1.4. about [issue](https://github.com/hi-dhl/Binding/issues/31#issuecomment-1109733307)"
            }
        } catch (e: Exception) {
            e.printStackTrace()
        }

        val bind: T
        if (thisRef.view == null) {
            // 这里为了兼容在 navigation 中使用 Fragment
            bind = layoutInflater.invoke(null, thisRef.layoutInflater) as T
        } else {
            bind = bindView.invoke(null, thisRef.view) as T

        }

        return bind.apply { viewBinding = this }
    }
}

}`

收到，能贴一下，使用这部分的代码吗

你说的是调用的时候吗？ 就是正常调用呀

手机多次运行也不会报错，这个错误是在GP后台看到的。

repo: hi-dhl/Binding


text:
Add Spring app sample

We are using Spring Webflux and it will be great to also add some Spring app sample.

I think you can find some blogs with examples of how to use HR with Spring.
But since we want to minimize dependencies, and since we're not Spring experts, I don't want to have such an example as part of this repo.

authors: alxxyz gavinking

repo: hibernate/hibernate-reactive


text:
HSEARCH-2854 IllegalStateException when sending an Elasticsearch request with a content-length

https://hibernate.atlassian.net//browse/HSEARCH-2854

thanks! merged

authors: Sanne yrodiere

repo: hibernate/hibernate-search


text:
HSEARCH-3531 Upgrade to Lucene 8.0.0

https://hibernate.atlassian.net//browse/HSEARCH-3531

Pull Request Test Coverage Report for Build 1

44 of 48 (91.67%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 88.712%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/search/extraction/impl/LuceneTopFieldCollectorScoreSortPostProcessor.java
3
7
42.86%

Totals

Change from base Build 183:
-0.004%

Covered Lines:
16646

Relevant Lines:
18764

💛  - Coveralls

I fixed the problems you mentioned and rebased. Waiting for CI...

Merged, thanks!

authors: coveralls yrodiere


text:
🛑 Kiwi Farms Forum is down

In 8c66691, Kiwi Farms Forum (https://kiwifarms.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kiwi Farms Forum is back up in b700808 after 5 minutes.

repo: hickoryhouse/kf


text:
Scatter Plot CSV export questions (zoom, extra data)

Please refer to this fiddle:
http://jsfiddle.net/1bLnjyuh/
I have two questions:

When zoomed, is it possible to only obtain CSV data for points in the current zoom area?
Is it possible to have extra data exported to the CSV? (In the above example the parameter named 'extra' with a value of z).

If no to either of the above, do you think there is a way to implement? I am going for both and am willing to patch + create a PR.
+Nadim

Currently this is not implemented, but you can create a wrap for the getDataRows function where you filter out points outside the zoomed bounds. This should get you started: http://jsfiddle.net/highcharts/1bLnjyuh/3/

This is achieved by setting the keys option: http://jsfiddle.net/highcharts/1bLnjyuh/2/

authors: TorsteinHonsi nadim

repo: highcharts/export-csv


text:
Apple nasm (old) used on Mac OS Sierra

Error message when making IncludeOS on Mac Sierra:
apic_boot.asm:58: error: expression syntax error
nasm -v:
NASM version 0.98.40 (Apple Computer, Inc. build 11) compiled on Nov 15 2016
while nasm-2.12.02 is installed (via brew install nasm)
Temporary local bandaid:
In IncludeOS/src/CMakeLists.txt after include_directories:
set(CMAKE_ASM_NASM_COMPILER /usr/local/Cellar/nasm/2.12.02/bin/nasm)

I think the solution is to let the install script for Mac symlink the brew nasm to the IncludeOS bin installation, and have the toolchain set the CMAKE_ASM_NASM_COMPILER.

authors: AndreasAakesson AnnikaH

repo: hioa-cs/IncludeOS


text:
Add support for arbitrary bridge names

Currently we have hardcoded the use of bridge43. This pull enables vmrunner to attach the vm to an arbitrary bridge on the system. Useful if you want the VM to enter a specific bridge (perhaps one used by vmware). Useful for testing.
It disables cleaning of the environment done by sudo when starting qemu. I cannot see any risks here.

I'm obviously missing something here since this seems to break on Linux. Seem to work at my system, though. :-/


text:
None of the Glider events fire.

 const gliderRef = useRef(null);
<Glider ref={gliderRef} onSlideVisible={(c,e) => console.log(c,e)} onLoad={(c,e) => console.log(c,e)}>
 {children}
</Glider>

Nothing gets logged to the console.

I have opened a PR (#65) that resolves this issue.
Note that while debugging this, I identified and filed another issue #66.

Is the maintainer active and accepting PR's?

Yes I think so.

:rocket: Issue was released in v2.2.0 :rocket:

authors: hipstersmoothie kevinfarrugia srameshr

repo: hipstersmoothie/react-glider


text:
关于运行程序中的一些问题

因为oj版本更新，页面元素的定位不同会导致在定位元素的时候找不到元素，从而出现错误‘raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message: ’
提供可能的一种解决方法：

打开浏览器的开发者模式选项，重新查看元素位置，并修改代码
同时还有可能出现上传测试数据不成功的问题，这时需要注意file_input的路径和file_input的定位不是button而是在button下边的input元素。
总结一下：因为oj版本变化，会在定位元素的时候出现各种问题，需要自己仔细查找元素位置

这个由于qduoj开发后有更新了较多版本，所以厚些问题，有兴趣的话，可以自己改一下代码，基本没有什么太大问题就可以搞定。

authors: hirCodd pq-dong

repo: hirCodd/AutoAddProblem


text:
Add ability to include metadata on every event

I find myself wanting to include some additional data to every event, even though the data is not entirely related to the event itself.
For example, in a Middleware I generate a unique request_id and I want that included in every event. I also want to include the current Team that the authenticated user is making the request in.
The implementation follows very closely to the way Laravel handles this in their Queue::createPayloadUsing() function.
I also added some docs, but not sure if this deserves its own page, vs somewhere else on an existing page.

I love this, and definitely want something like this in Verbs. My one question is: do we want metadata to just be a plain array, or do we want to use a collection or bespoke Metadata class to provide some convenience methods?

I figured a basic array was the easiest thing without overcomplicating it. A collection might be nice as well. If we did a full class, maybe it makes sense to put a second column on the event table for metadata and then we can use a custom eloquent cast.

Just throwing some unstructured thoughts out there:

I think I favor a 2nd column for metadata
I think I prefer some knowable structure for metadata. Thus far almost everything you do in a handle() method is typed, so it's very hard to reference things that might not exist. I'm pretty into this as it makes me feel a lot safer replaying events if the classes are at least statically valid. Arrays scare me because I can envision adding keys to that array over time, getting out of sync with old events, and eventually getting to an un-replayable situation.
This plays into a broader conversation @joshhanley @inxilpro and I have been having sort of disjointedly about event versioning #21

So I could see doing kinda the best of both worlds. We could introduce a Metadata class that looks something like:
class Metadata
{
  protected Collection $extra;

  public function __construct(array $data = [])
  {
    // 1. Populate any properties that exist using our serializer
    // 2. Push remaining data into $this->extra
  }

  public function __get(string $name)
  {
    return $this->extra->get($name);
  }

  public function __set(string $name, $value): void
  {
    $this->extra->put($name, $value);
  }

  public function __isset(string $name): bool
  {
    return $this->extra->has($name);
  }
}

And by default we would populate $event->metadata with an instance of that class. Then we could introduce a new configuration that's like verbs.metdata_class that lets you set a custom metadata subclass that has typed properties. Something like:
namespace App\Events\Support;

class Metadata extends \Verbs\Metadata
{
  public ?string $user_agent = null;

  public ?string $ip_address = null;

  public ?int $active_user_id = null;
}

And then in your config you'd set verbs.metdata_class to App\Events\Support\Metadata.
Once that's all hooked up, you could just typehint the Metadata class of your choice inside the event lifecycle methods.
public function handle(App\Events\Support\Metadata $metadata) {
  // Now I have my typed metadata object
}

And Verbs could handle the DI for you. But if you don't want/need a custom metadata object, you could just type hint the base class and it'd still work.
The upside of this is that a package could rely on metadata always being there without having to know its type ahead of time. A package could just dump values into the metadata payload, and if the end user wanted to access them with type safety, all they would have to do is add properties to their custom class.

I really like that approach.
The EventStore::createMetadataUsing() function could look something like
EventStore::createMetadataUsing(function (string $event_class, App\Support\Metadata $metadata) {
    $metadata->request_id = (string) Str::uuid();

    return $metadata;
});

So you could still sprinkle EventStore::createMetadataUsing() throughout the codebase or third party packages.

Yeah, that's cool. We could definitely support type-hinting either version in the createMetadataUsing callback, too.
What's your thinking for wanting the event class in the callback? I would think that anything that's event-specific would live in the event, right? I would think that any global callbacks should only apply global metadata…

I think we're pretty good. @skylerkatz — you want to take a stab at switching to a class-based approach? I think for the first version we could skip the custom DI stuff, and just know that we want to add that eventually.

I think we are just on the "needs to implement stage". Which I plan on working on this week.

@inxilpro I pushed up an initial implementation at a Metadata class, but I don't love it.
I think it may just be an organization thing, but would love your thoughts on it.

authors: DanielCoulbourne inxilpro skylerkatz

repo: hirethunk/verbs


text:
请问能在批量OCR的界面增加 多选删除功能么

Issues

[X] I have browsed through the Issues. 我已浏览过Issues，确定没有重复的建议。

Expected behavior 预期的功能

大佬我主要是 OCR 硬字幕的图片
您看 在批量的时候有个 置信度
置信度相同的基本上 就是 提取字幕的时候多余的重复图
现在只能点击 查看 删除
如果 可以 增加 按住ctrl  或者shift 批量删除的话 会更方便的整理重复的图片
可以考虑考虑吗 给批量OCR这边增加一个 多选删除的功能
Approximate reference (optional) 近似的参考（可选）
点击状态这里

可以视线多选 删除
点击图片是单张查看图片 这个不变  然后点击 状态就可以多选 然后进行删除

了解。后续会考虑支持，不过近期内优先级不高，请等待吧。

嗯嗯 谢谢

repo: hiroi-sora/Umi-OCR


text:
When downloading a wallet via hiro.so info/data to verify the download is excluded

A users asked
Why there isn't a hash or code crc256 to check if application is genuine to thwart supply chain attacks?
We do have signed releases on github. Is there something else we should do here. Or are we assuming that a user who wants to run such a check to be able to find our github repository?
I do not think adding the data to the download (a seperate file with the hashes?) would solve the issue because if hiro.so got compromised both could be replaced by the hacker providing false security.
Should we perhaps provide the option to (a) direct to Github for a user to pick the appropriate version for themselves and/or (b) provide the option to verify authenticity?

You can't download the web wallet from hiro.so. Are they referring to the desktop wallet?

Sorry I will close this here and open it on the desktop repo.

see here https://github.com/hirosystems/stacks-wallet/issues/1146

repo: hirosystems/stacks-wallet-web


text:
fix: tx request padding

Try out this version of the Hiro Wallet - download extension builds.

This PR fixes padding on the choose account and tx request center popup.
Redoing for: https://github.com/hirosystems/stacks-wallet-web/pull/2392

cc/ @kyranjamie @fbwoolf @beguene @He1DAr

Thanks @fbwoolf code LGTM, but can you add the original contributor to the commit ? You could do a simple git cherry-pick for example.

can you add the original contributor to the commit ?

Just curious why this is important if the commit wasn't complete or able to be merged?

@fbwoolf Just to attribute the work also to the external contributor. We welcome all contribution and we should attribute it correctly if possible.

Also, I had to make further changes so adding the commit now seems odd considering it makes it incorrect.

I guess one thing I could do is reopen the original PR and just work from the fork if that is preferred? I just thought it was cleaner to open a new PR but as a learning experience maybe that wasn't the best idea?

@fbwoolf You don't need to reopen his PR
Yes from the fork you can do the following
git checkout -b fix/foo
git fetch https://github.com/mcintyre94/stacks-wallet-web.git
git remote add external https://github.com/mcintyre94/stacks-wallet-web.git
git fetch external
git cherry-pick 577a90d687c13771ed4d61fa135e1fa53db105df

Then you can add your commit on top.

Thanks for help @beguene! Got both commits here now.

Tested the PR fixes padding on the 'choose account' and 'tx request center popup.'
Test passed.Moving it out from QA

authors: Eshwari007 beguene fbwoolf


text:
0.0.1

Main Features：

bcc monitor
memory collector
by-pass filter

Unittest:

Mock bcc monitor

PR(Will merge into main)：

https://github.com/hitsz-ids/duetector/pull/9

Reopen for still works to do:

Docs for plugin system
Docs for developer
Docs for user

May add a CLI

Working on config generator and docs in code
https://github.com/hitsz-ids/duetector/pull/17

Given the release of 0.0.1b0, more test cases will be added next in preparation for the release of 0.0.1rc0

repo: hitsz-ids/duetector


text:
QLoRA报错expected scalar type Half but found Float

在仅设定--quantization_bit 4时训练会报这个错，在设定--quantization_bit 4且设定--fp16时训练不会报这个错。请问quantization_bit是要和fp16同时设置上吗？

同时加

repo: hiyouga/ChatGLM-Efficient-Tuning


text:
关于函数preprocess_pretrain_dataset对预训练样本的拼接

我做的预训练语料每个样本是独立的String，彼此无语义相关。如果按照preprocess_pretrain_dataset方法，会根据model_max_length拼接补齐，这样最终的example数量会少很多，但每个example里面会包含不同的String，这样会对自回归预训练是否有害？请问有没有按照每个样本分词的方法？

这种方法是正确的

我也注意到了这个问题

我做的预训练语料每个样本是独立的String，彼此无语义相关。如果按照preprocess_pretrain_dataset方法，会根据model_max_length拼接补齐，这样最终的example数量会少很多，但每个example里面会包含不同的String，这样会对自回归预训练是否有害？请问有没有按照每个样本分词的方法？

请教一下，好像代码里没有提到会根据model_max_length对example进行拼接补齐呀？

repo: hiyouga/LLaMA-Efficient-Tuning


text:
bf16多卡deepspeed全参数微调chatglm2出错

同一个数据集，用bf16单卡LoRA微调没有问题，但多卡全参数微调就出错，训练过程正常不报错，损失也在下降，但是最终生成结果混乱，且predict的时候batch size>1就报错。
主要环境：
transformers==4.33.2
deepspeed==0.10.0
bitsandbytes==0.41.1

训练代码：
deepspeed --include localhost:$gpu_vis --master_port=$MASTER_PORT LLaMA-Factory/src/train_bash.py \
  --deepspeed deepspeed.json \
  --stage sft \
  --do_train \
  --model_name_or_path chatglm2 \
  --output_dir checkpoint \
  --dataset data \
  --template chatglm2 \
  --finetuning_type full \
  --overwrite_cache \
  --per_device_train_batch_size 16 \
  --gradient_accumulation_steps 1 \
  --per_device_eval_batch_size 1 \
  --lr_scheduler_type cosine_with_restarts \
  --warmup_ratio 0.02 \
  --logging_steps 10 \
  --save_strategy epoch \
  --learning_rate 2e-4 \
  --num_train_epochs 3.0 \
  --plot_loss \
  --bf16 \
  --cutoff_len 2560 \
  --max_new_tokens 512 \
  --overwrite_output_dir

deepspeed配置：
{
  "train_batch_size": "auto",
  "train_micro_batch_size_per_gpu": "auto",
  "gradient_accumulation_steps": "auto",
  "gradient_clipping": "auto",
  "zero_allow_untested_optimizer": true,
  "bf16": {
   "enabled": true
  },
  "zero_optimization": {
    "stage": 2,
    "allgather_partitions": true,
    "allgather_bucket_size": 5e8,
    "reduce_scatter": true,
    "reduce_bucket_size": 5e8,
    "overlap_comm": false,
    "contiguous_gradients": true
  }
}

训练损失下降正常：

做predict时的代码：
python LLaMA-Factory/src/train_bash.py \
    --stage sft \
    --model_name_or_path checkpoint \
    --do_predict \
    --dataset data \
    --template chatglm2 \
    --output_dir result \
    --per_device_eval_batch_size 8 \
    --predict_with_generate

报错信息：
Traceback (most recent call last):
  File "LLaMA-Factory/src/train_bash.py", line 14, in <module>
    main()
  File "LLaMA-Factory/src/train_bash.py", line 5, in main
    run_exp()
  File "LLaMA-Factory/src/llmtuner/tuner/tune.py", line 26, in run_exp
    run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
  File "LLaMA-Factory/src/llmtuner/tuner/sft/workflow.py", line 85, in run_sft
    predict_results = trainer.predict(dataset, metric_key_prefix="predict", **gen_kwargs)
  File "/opt/conda/lib/python3.10/site-packages/transformers/trainer_seq2seq.py", line 216, in predict
    return super().predict(test_dataset, ignore_keys=ignore_keys, metric_key_prefix=metric_key_prefix)
  File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 3044, in predict
    output = eval_loop(
  File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 3157, in evaluation_loop
    loss, logits, labels = self.prediction_step(model, inputs, prediction_loss_only, ignore_keys=ignore_keys)
  File "/train_file/xunhao/LLaMA-Factory/src/llmtuner/tuner/sft/trainer.py", line 45, in prediction_step
    loss, generated_tokens, _ = super().prediction_step(
  File "/opt/conda/lib/python3.10/site-packages/transformers/trainer_seq2seq.py", line 282, in prediction_step
    generated_tokens = self.model.generate(**inputs, **gen_kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 1648, in generate
    return self.sample(
  File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 2730, in sample
    outputs = self(
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/root/.cache/huggingface/modules/transformers_modules/chatglm2/modeling_chatglm.py", line 936, in forward
    transformer_outputs = self.transformer(
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/root/.cache/huggingface/modules/transformers_modules/chatglm2/modeling_chatglm.py", line 821, in forward
    full_attention_mask = self.get_masks(input_ids, past_key_values, padding_mask=attention_mask)
  File "/root/.cache/huggingface/modules/transformers_modules/chatglm2/modeling_chatglm.py", line 692, in get_masks
    full_attention_mask -= padding_mask.unsqueeze(-1) - 1
RuntimeError: output with shape [8, 1, 368] doesn't match the broadcast shape [8, 368, 368]

使用batch size = 1 时可以正常做predict，但是结果出错
{
"predict": "select havingaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxaxax"
}

以上错误在单卡，bf16，QLoRA训练时，都没有出现，最后模型的结果也很正常。但多卡就出问题。fp16和bf16都试过，都会出现同样的问题。

学习率偏高！

authors: JerryDaHeLian laxuryPKU

repo: hiyouga/LLaMA-Factory


text:
关于LoRA微调导出模型以及加载模型继续训练的疑问

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
我使用LoRA微调了ChatGLM3模型。微调后直接使用web界面中的export功能导出（也就是合并）模型。我有几点疑问：

在Web界面导出时，合并的是所提供适配器路径下的哪一个checkpoints，是最后一个吗？
如果我希望指定checkpoints来合并，是不是必须通过命令行来实现？也就是指定参数 --adapter_name_or_path path_to_checkpoint 到相应的checkpoint
我想从某个指定的checkpoint开始继续训练，如果使用web界面，似乎无法指定checkpoint。它是从最后一个checkpoint开始训练的吗？如果想实现这一功能，是不是必须通过命令行实现？也就是指定 --adapter_name_or_path 到相应的checkpoint

Expected behavior
No response
System Info
No response
Others
No response

我也想知道训练中断后如何继续训练。。。

我有个类似问题。假定基础模型Model
1.我在基础模型Model 的基础上用数据集A微调了LoRA权重LoRA_A
2.我想继续在LoRA权重A的基础上，用数据集B微调LoRA权重LoRA_B
我不希望将LoRA_A存成一个基础模型，我希望直接从LoRA_A的权重微调LoRA_B，获得的B_adapter直接能用在原始模型Model的权重上，我该如何操作？

+1

合并时选用的是最后一次保存的 adapter
使用 web 端继续训练时，如果上次的中间点有保存会自动继续，如果没有保存中间点则无法继续

合并时选用的是最后一次保存的 adapter 使用 web 端继续训练时，如果上次的中间点有保存，点击开始会自动继续，如果没有保存中间点则无法继续

为什么web端不支持选择checkpoint合并呢？ 这样用户可以根据eval的情况来选择最好的checkpoint而不是固定的最后一个。 希望可以加上这个功能，谢谢

authors: HaohzW Sakura4036 Xingxiangrui hiyouga ryancurry-mz zhangyue2709


text:
正常训练模型结束后predict报错“RuntimeError: The expanded size of the tensor (496) must match the existing size (495) at non-singleton dimension 3.  Target sizes: [16, 64, 1, 496].  Tensor sizes: [16, 1, 1, 495]”

Reminder

[X] I have read the README and searched the existing issues.

System Info

llamafactory version: 0.8.4
Platform: Linux-5.4.0-193-generic-x86_64-with-glibc2.31
Python version: 3.11.9
PyTorch version: 2.4.0+cu121 (GPU)
Transformers version: 4.43.4
Datasets version: 2.20.0
Accelerate version: 0.32.0
PEFT version: 0.12.0
TRL version: 0.9.6
GPU type: NVIDIA A100-PCIE-40GB
DeepSpeed version: 0.14.4

Reproduction
model
model_name_or_path: /home/jovyan/workspace/intentLMAllDataset/清华实验目录/syw/workspace/llama_models/Meta-Llama-3-70B-Instruct
adapter_name_or_path: /home/jovyan/workspace/code/honor-tsinghua-honor/llm_8card_code/LLaMA-Factory-main_my_____/saves/llama3-70b-bf16/lora/0826_data_loc_next_info_test_ini/checkpoint-624
method
stage: sft
do_predict: true
finetuning_type: lora
deepspeed: examples/deepspeed/ds_z3_config.json
dataset
eval_dataset:  beheaviors_dataset_0826_data_loc_next_info_test
template: llama3
cutoff_len: 1024
max_samples: 7000
overwrite_cache: true
preprocessing_num_workers: 16
output
output_dir: saves/llama3-70b-bf16/lora/predict_0826_data_loc_next_info_eval_true_predict_eval
overwrite_output_dir: true
eval
per_device_eval_batch_size: 16
predict_with_generate: true
ddp_timeout: 180000000
bf16: true
报错如下：
[rank1]:   File "/opt/conda/envs/llama_factory_newest/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1603, in _call_impl
[rank1]:     result = forward_call(*args, **kwargs)
[rank1]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank1]:   File "/opt/conda/envs/llama_factory_newest/lib/python3.11/site-packages/transformers/models/llama/modeling_llama.py", line 603, in forward
[rank1]:     attn_output = torch.nn.functional.scaled_dot_product_attention(
[rank1]:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank1]: RuntimeError: The expanded size of the tensor (496) must match the existing size (495) at non-singleton dimension 3.  Target sizes: [16, 64, 1, 496].  Tensor sizes: [16, 1, 1, 495]
我尝试使用llama3-8B来测试同样的数据集，没有发生异常，可以正常运行，但是70B模型有问题
Expected behavior
使用过最新版的llama-factory调用api进行测试，但是测试的速度太慢了，于是回退版本希望可以同时使用dz_zeros3以及do predictc参数进行批量测试,加快测试的速度
Others
No response

这个问题解决了嘛，我也遇到了

me too


text:
🛑 Griffo is down

In 3326f2f, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 4189dd1 after 27 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 LM Bogen WSV is down

In 661c851, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in a57ef3c after 7 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In 97edc31, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in f341ede after 1 hour, 35 minutes.


text:
🛑 Griffo is down

In d672628, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in b715931 after 31 minutes.


text:
🛑 HJStrauss is down

In 1ae43cc, HJStrauss (https://www.hjstrauss.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in 3dca95a after 9 minutes.


text:
🛑 Opa Hansi is down

In d970c81, Opa Hansi (https://www.opahansi.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Opa Hansi is back up in 4d45691 after 7 minutes.


text:
about V

When generating V,  you cat the image and mask. This is different from STM.  What will be the impact on the results?

STCN：f = torch.cat([image, mask], 1) in ValueEncoderSO to product v.
STM: x = self.conv1(f) + self.conv1_m(m) + self.conv1_o(o) in Encoder_m to product the k and v for memery bank.
What will be the impact on the results?

They are the same.
Proof:
import torch
import torch.nn as nn

img = torch.randn((2, 3, 64, 64))
msk = torch.randn((2, 1, 64, 64))

cat_conv = nn.Conv2d(4, 64, kernel_size=3, padding=1, bias=False)
add_conv_i = nn.Conv2d(3, 64, kernel_size=3, padding=1, bias=False)
add_conv_m = nn.Conv2d(1, 64, kernel_size=3, padding=1, bias=False)

add_conv_i.weight.data = cat_conv.weight.data[:, :3]
add_conv_m.weight.data = cat_conv.weight.data[:, 3:]

cat_out = cat_conv(torch.cat([img, msk], 1))
add_out = add_conv_i(img) + add_conv_m(msk)

print(torch.allclose(cat_out, add_out, atol=1e-6))

I understand. Thanks for your reply

authors: INTOUCHABLE-VS hkchengrex

repo: hkchengrex/STCN


text:
Exposure-Category - clarify functional need

For RIZIV to clarify.

We leave it as an optional extension


text:
Linkable-cards can't have hard coded icons

Currently, the linkable-cards has 1 arrow-down icon added to all cards automatically. However, there are different types of content which need different icon treatments.
Example of 2 that are not:

Looks like we cannot hook into the category (aka "BLOG"), so I propose the :icon-name: solution here as well.

Same approach here - we can pick this based on the target link automatically.
If ends with .pdf (pdf), or not merative.com (external) and decorate the links and then add icons for that by just autoblocking the whole thing and removing the need for authors to have to do anything.

@amol-anand can this issue be closed? I think you and the customer agreed on a solution.

We're switching to using Related Resources block instead of this one since it can handle automatic links as well as curated ones.

Linkable cards and related resources buttons should follow global button markup patterns so that they can take advantage of common button decoration processing.

authors: amol-anand arumsey venturewise

repo: hlxsites/merative


text:
Import links to subdomains of servicenow.com

Whem importing the blog articles the domains of links pointing to subdomains ofservicenow.com are replaced with www.servicenow.com.
See: https://www.servicenow.com/blogs/2022/3-trends-driving-mobile-app-adoption.html

Fixed in 563361fc4009f4ea00b223d467953cc7cafffb34

authors: andreituicu sergiucoman

repo: hlxsites/servicenow


text:
Product Card variation

Test URLs:

After: https://feat-product-cards--takeda-ihs--hlxsites.hlx.page/drafts/stopp/cards-product

Superseded by #61

repo: hlxsites/takeda-ihs


text:
Parent Page

Also port this page: https://www.zeiss.de/semiconductor-manufacturing-technology/news-und-events.html and generate article list from index.

Content: https://adobe.sharepoint.com/:w:/r/sites/HelixProjects/_layouts/15/doc2.aspx?sourcedoc={83147B4B-3A11-4B8C-9F90-DBD0C07E3C68}&file=index.docx&action=default&mobileredirect=true

A per scope definition from Zeiss, the parent page would stay in AEM.

authors: sdmcraft trieloff

repo: hlxsites/zeiss


text:
Kv networkacls

Resolves # . (This is applicable only if this pull request relates to a GitHub issue, delete the line otherwise)
Notes:
Introduces Keyvault Network access control list to prevent pubic access to the keyvaults.

Test Build:
https://sds-sandbox-build.platform.hmcts.net/job/HMCTS_Sandbox_PRE/job/pre-shared-infrastructure/job/demo/37/

private endpoints entails the use of peering and DNS modifications, it is reliant on other jobs outside Jenkins,
using the above directly gives the terraform code the management of the ACL.

repo: hmcts/cnp-module-key-vault


text:
updated configuration

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing this PR as no longer requred

authors: praneethhm priteshkr

repo: hmcts/prl-ccd-definitions


text:
Too many parameters fix

JIRA link (if applicable)
NA
Change description
Too many parameter error in case data has returned following a merge #1866 in the master branch. Changes here will will move 5 variables to a child class to leave some space for extra parameters in case data.
No change in the functional behaviour
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

This PR is merged in case-flags-2.1 and no longer needed.

repo: hmcts/prl-cos-api


text:
PRL-4750 English Cafcass Email Removed

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-4750
Change description
Remove the Cafcass email field for english courts.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

No longer needed as it was created for testing


text:
AccessToken 方式怎么使用？

参数api_reverse_proxy 配置的 https://chat.openai.com/backend-api/conversation，accessToken 是在https://chat.openai.com/ 页面从浏览器拿的。 现在是不是不能用这种方式，我试了调用接口不通，我看其他一些项目，还要配置cookie

api_reverse_proxy 不能直接配 https://chat.openai.com/backend-api/conversation，搭建代理服务的方式参考 https://github.com/linweiyuan/go-chatgpt-api

api_reverse_proxy 不能直接配 https://chat.openai.com/backend-api/conversation，搭建代理服务的方式参考 https://github.com/linweiyuan/go-chatgpt-api
我本地开了VPN，可以访问chatGPT，然后修改了accessToken 方式的请求源码，和api-Key 一样请求的时候加了代理，使用vpn的代理端口，这种方式也不行吗？必须要搭建代理服务才可以吗

不行的，AccessToken 需要绕过 CloudFlare 验证。

api_reverse_proxy 不能直接配 https://chat.openai.com/backend-api/conversation，搭建代理服务的方式参考 https://github.com/linweiyuan/go-chatgpt-api

搭建了代理服务器后将，apiReverseProxy 设置成自己的代理服务器地址就可以了么，还需要什么配置

api_reverse_proxy 不能直接配 https://chat.openai.com/backend-api/conversation，搭建代理服务的方式参考 https://github.com/linweiyuan/go-chatgpt-api

搭建了代理服务器后将，apiReverseProxy 设置成自己的代理服务器地址就可以了么，还需要什么配置

然后再配上自己的 accesstoken 就可以了。

authors: LYXCQX hncboy lkj7b226

repo: hncboy/chatgpt-web-java


text:
added notebook with my code for classifier

Added my code for the image classifier.

I don't need your codes

authors: Abraham-hanks edeediong

repo: hngi/Plate-Number-Classification


text:
allow to include same file from multiple files

add a set of already added files and check if files was already added, in such case do not try to add it again
This happened to me while trying to include same files from multiple files (diamond topology)
got this exception when starting an idea project:
Exception in thread "main" kotlin.io.FileAlreadyExistsException: .../kscripts/utils.kt -> /Users/oshai/.kscript/kscript_tmp_project__ksuite.kts_1530089926297/src/utils.kt: The destination file already exists.
at kotlin.io.FilesKt__UtilsKt.copyTo(Utils.kt:193)
at kotlin.io.FilesKt__UtilsKt.copyTo$default(Utils.kt:184)
at kscript.app.AppHelpersKt.createSymLink(AppHelpers.kt:267)
at kscript.app.AppHelpersKt.launchIdeaWithKscriptlet(AppHelpers.kt:254)
at kscript.app.KscriptKt.main(Kscript.kt:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jetbrains.kotlin.runner.AbstractRunner.run(runners.kt:61)
at org.jetbrains.kotlin.runner.Main.run(Main.kt:109)
at org.jetbrains.kotlin.runner.Main.main(Main.kt:119)

Thanks for the suggestion. I indeed did not think of diamond topologies here.
Couldn't we simply do includeURLs.distinct().forEach { to avoid the harder to read return@forEach and the additional checking logic?
Would it be possible for you to create unit-test example under kscript/test/resources/diamonds and to add it to the test-suite? By doing so we could better prevent regressions of this feature.

sounds a good idea, I hope I will have time soon to fix

I did changes and add diamond file. not sure if this is the testing you meant and where is the suite I should include it.
note I didn't use distinct() but distinctBy{} since it is better to compare strings of the file name itself (or full name, I was not sure if we are creating directories)

Thanks for the PR. distinctBy is indeed more elegant here.

The latest release v2.4.5 contains your patch. Thanks again for your help.

authors: holgerbrandl oshai

repo: holgerbrandl/kscript


text:
v1.0.3 - Fixing some regressions

After revisiting https://github.com/holidayextras/jsonapi-client, bumping the version of jsonapi-server and running the test suite, we identified two minor regressions:

Content-Length headers shouldn't be forwarded on for inclusion requests
Resources with undefined properties shouldn't match using the stock filtering functionality.

In the future I'd like to find a way of running dependent projects against new releases to identify these edge cases before each new release. I'd also like to write some extensive unit tests, but I don't think it's a good use of my time right now.
You can test this by checking out jsonapi-client, updating to the latest jsonapi-server release (v1.0.2) and running npm-test. Update to this version and the tests will pass.

Taking review

Makes sense :+1:

:+1: Tests now passing on the client when using this branch.

repo: holidayextras/jsonapi-server


text:
Withdraw money to bank account

As customer
I want to withdraw some money on my bank account
so i can pay stuff with with it
implementation hints:
enhance the api.yaml (maybe as an account method)
create a separate use case
don't use canonical class design (e.g. Account::withdraw instead of Account::setBalance)

This PR was repeated.

repo: holixon/cqrs-meets-hexagonal


text:
Initial layout of the page

Set up the different sections of the page (introduction, bullet points, project)
Edit layout of each project's text box in the CSS file

Hey Holly. I found Google HTML/CSS style guide, as well as Google Javascript style guide.
https://google.github.io/styleguide/htmlcssguide.html
https://google.github.io/styleguide/jsguide.html
Can you skim through these guides, and see whether this pull request should be updated? The style guides are pretty long, so I understand if you can't remember every part of them. But it'd be nice to check them against this code change.

authors: hollyyuqizheng jamesnam-google

repo: hollyyuqizheng/step-portfolio


text:
modifying UI seems to break (freeze?) entry-contents pane

steps to reproduce:

drag entry-contents pane into its own UI pane-space
click on some App entry in the source-chain pane
....
a. expected: entry-contents pane updates
b. actual: entry-contents pane does not update

Ouch thanks :)

yw! most of the time it's totally fine to leave them where they are, so this issue doesn't bother me too much. I mainly wanted to flag it & make it discoverable by others who might encounter it be confused :slightly_smiling_face:

authors: guillemcordoba mhuesch


text:
Great addition

Hi
This is great, thanks for deveolping it.
couple FRs

black pen color in the dark mode
ability to extend the range of pressure sensitivity, the lowest thickness feels still to thick for emulating ink pens for instance
ability to change the aspect ratio of the notes, they are squares only now

thanks

@gerroon

It seems like the black ink is controlled by Tldraw when switching to dark/light them.
Pressure sensitivity: This is beyond the scope of this plugin, since Tldraw itself handles this
The aspect ratio of the notes is set by Tldraw itself, not this plugin. We would need to add support for custom draw components to support that

I would advise you to make requests to the Tldraw team for features outside the scope of this plugin for feature requests that to apply to the core Tldraw library, which this plugin uses. Their repo is found here: https://github.com/tldraw/tldraw
With that said I think the only feature request that applies here is creating a custom draw component  that functions like the base note component, but allows for different/custom aspect ratios.

authors: gerroon jon-dez

repo: holxsam/tldraw-in-obsidian


text:
MQTT delay in dev branch

I run dev branch of HA on ubuntu/x86, manual install, plenty of resources (quad-core i7-2635QM, 16GB of RAM, SSD). Mosquito is running on the same host as HA (and broker is acceded by 127.0.0.1)
Before dev branch I was running whatever was stable version at the beginning of sumer. But due to tiredness of constant issue with zeroconf on restart I decided to give a try to dev, hopping it is fixed there. It was somewhere at the end of August.
What I found that dev branch introduces tremendous delay. Checked with zigbee2mqtt.
If I switch bulb in front-end, for example, it takes sometimes up to 10 seconds before MQTT message is published.
I tried rules where received MQTT message triggers sending another MQTT message - same story, so it is unlikely frontend.
I enabled debug logging for MQTT component but I see absolutely zero there aside of usual stuff you get when it works normally. It just this stuff delayed by same 1-10 seconds as MQTT messages.
Today I tried to update to current dev, and it is absolutely the same. Nothing change.

According to my testing, issue was introduced between 0.99.2 and 0.99.3

There was an issue with MQTT lags a long time ago https://github.com/home-assistant/home-assistant/issues/12716 , maybe some help to find the culprit.

Interesting. I checked diff between 0.99.2 and 0.99.3...and I see nothing which can affect this delay. Difference only in different frontend version (while test shows that this has nothing to do with frontend) and different zigpy-zigate version, which isn't used on my setup.
But I clearly see a difference when I move to 0.99.3 and rollback to 0.99.2.

@antst This is strange indeed.
If you do a fresh test installation and enable only MQTT, can you reproduce the issue on 0.99.3 but not on 0.99.2?

authors: VDRainer antst emontnemery

repo: home-assistant/home-assistant


text:
yandex_transport plugin issue

Home Assistant release with the issue: 0.100.2

Last working Home Assistant release (if known): never
Operating environment (Hass.io/Docker/Windows/etc.): Ubuntu 18.04.1 LTS

Integration: https://www.home-assistant.io/integrations/yandex_transport/

Description of problem:
yandex_transport: Error on Home Assistant startup.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: yandex_transport
  stop_id: 9639579

Traceback (if applicable):
Fri Oct 18 2019 10:36:06 GMT+0300 (EEST)
Error while setting up platform yandex_transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/yandex_transport/sensor.py", line 44, in setup_platform
    data = YandexMapsRequester(user_agent=USER_AGENT)
  File "/home/fokusas/.homeassistant/deps/lib/python3.6/site-packages/ya_ma.py", line 55, in __init__
    self.set_new_session()
  File "/home/fokusas/.homeassistant/deps/lib/python3.6/site-packages/ya_ma.py", line 84, in set_new_session
    rf'"{CSRF_TOKEN_KEY}":"(\w+.\w+)"', reply
AttributeError: 'NoneType' object has no attribute 'group'

Additional information:
I am getting this error on startup. There is no entity created in states list with yandex name.
Configuration check passes without errors.

Looks like yandex block your request
Can you open  yandex.ru/maps in private mode in browser?

I'm getting this

After entering captcha i get map view.

your ip is blocked,
try again after 1-2 days

we can integrate login to mail@yandex.ru, and hope, then you'll not be block
but for this need to integrate login feature to the ya_ma.pypi.org, and save account data in configuration.yaml

I have the same problem, need any authorization on the service

I reinstalled my ubuntu and now it works. Installed HA 0.101.2 version.

I tried to configure integration with yandex_transport on my Home-assistant 0.101.3 without success.
I added to sensor section of my config following lines:
  - platform: yandex_transport     name: Tram_to_work     stop_id: 96***20
There is no error messages in log (with debug level of info) and no sensor.yandex_transport in entities.
How problem can be resolved?

config seems normal

- platform: yandex_transport
    name: Tram_to_work
    stop_id: 96***20

my config lines on sensor is:
- platform: yandex_transport
  stop_id: 9643739
  name: bus_to_subway
- platform: template
  sensors:
     bus_to_subway_min:
       value_template: "{{ ((as_timestamp(states('sensor.bus_to_subway')) - as_timestamp(now())) / 60)  | round(2) }}"
       unit_of_measurement: 'min'
       friendly_name: "Автобус в метро"

and then i added entities: bus_to_subway and  bus_to_subway_min on my lovelace
entities:
  - sensor.bus_to_subway
  - entity: sensor.bus_to_subway_min
show_header_toggle: true
title: Остановка Гостиница Восход
type: entities

Rishat (aka @rishatik92), thank you for your help!
Nevetheless I don't see any messages in log yet. I don't have sensor in my system after reboot.
What I tried to put in my setup:
`- platform: yandex_transport
  name: Tram_to_center
  stop_id: 9641820
routes:
- 3
- 1
- 16
#- platform: template
sensors:
tram_to_center_min:
friendly_name: "Трамвай в центр"
value_template: "{{ ((as_timestamp(states('sensor.Tram_to_center')) - as_timestamp(now())) / 60)  | round(2) }}"
unit_of_measurement: 'min'`
It's quite strange that when I tried to use routes in sensor, I've got following error -
"Configuration invalid
Error loading /config/configuration.yaml: mapping values are not allowed here
in "/config/sensors/yandex_transport.yaml", line 7, column 9"
Without routes when I tried to add template sensor like in your example I've also got error -
"Configuration invalid
Error loading /config/configuration.yaml: expected '', but found ''
in "/config/sensors/yandex_transport.yaml", line 12, column 1"
Are there any way to debug integration with yandex transport?

i think you don't have problem with yandex_transport.
in my opinion your HA not reading your configuration
Try to add sensor configuration directly in configuration.yaml
чт, 14 нояб. 2019 г. в 20:16, hellad notifications@github.com:

Rishat (aka @rishatik92 https://github.com/rishatik92), thank you for
your help!
Nevetheless I don't see any messages in log yet. I don't have sensor in my
system after reboot.
What I tried to put in my setup:
`- platform: yandex_transport
name: Tram_to_center
stop_id: 9641820
routes: - 3 - 1 - 16
#- platform: template
sensors: tram_to_center_min: friendly_name: "Трамвай в центр" value_template:
"{{ ((as_timestamp(states('sensor.Tram_to_center')) - as_timestamp(now()))
/ 60) | round(2) }}" unit_of_measurement: 'min'`
It's quite strange that when I tried to use routes in sensor, I've got
following error -
"Configuration invalid
Error loading /config/configuration.yaml: mapping values are not allowed
here
in "/config/sensors/yandex_transport.yaml", line 7, column 9"
Without routes when I tried to add template sensor like in your example
I've also got error -
"Configuration invalid
Error loading /config/configuration.yaml: expected '', but found ''
in "/config/sensors/yandex_transport.yaml", line 12, column 1"
Are there any way to debug integration with yandex transport?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/27843?email_source=notifications&email_token=AAXXLLMCJUN4D5ZRIMTRZULQTWBXVA5CNFSM4JCD7A7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECS5XI#issuecomment-553987805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXXLLN5FBKZMEZVS76QRZTQTWBXVANCNFSM4JCD7A7A
.

@rishatik92, I do beleive that my HA reads configuration with sensor section stored in multiple files. My sensors work as intended. You can see example on screenshot attached.

Again, is it possible for non-programmers to debug integration with yandex_transport?

authors: fokusas-IoT hellad rishatik92 varrcan