text:
[stable/nextcloud] Adding cron for the background jobs

What this PR does / why we need it:
Ajax mode is enabled by default on the nextcloud installation which is running on every page load. These changes give the possibility for the chart users to use k8s CronJob resource to execute cron.php script automatically over the web (webcron).
Further notes
Ideally, we should execute cron.php directly through the CLI with php but that would require setting up the volumes and env all over again in the CronJob template. I do not like the idea of copy-pasting those from Deployment.yaml. Maybe we should reconsider that later using a shared template. Something like files/image-template.yaml which will contain volumeMounts and env and then include it in both Deployment and CronJob templates? Suggestions are welcome.
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])

/ok-to-test

@billimek I have rebased with the master now and fixed the conflict. Are we OK to merge this one?

@pfuhrmann thanks for the contribution!  This looks great.
/lgtm

authors: billimek pfuhrmann


text:
[stable/prometheus-operator] add resources field to admissionWebhooks jobs

What this PR does / why we need it:
Currently the admissionWebhooks jobs (both job-createSecret.yaml and job-patchWebhook.yaml) of prometheus-operator do not allow for configurable resource requests and limits. This PR adds the capability, and also updates the README accordingly.
With this, all pods should now have configurable resource sections.
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 @bismarck

/ok-to-test

@sjentzsch
I think you might need to resolve Chart.yaml conflict.

@zanhsieh done.

/assign @bismarck
/assign @vsliouniaev

@vsliouniaev
@bismarck
Could you guys LGTM this PR please? Thank you.

/lgtm
Not really certain that there's a use for this outside of some restricted environments where specifying resources is mandatory.

/lgtm
Not really certain that there's a use for this outside of some restricted environments where specifying resources is mandatory.

Exactly that's our use case.

source: gharchive/pull-request

authors: sjentzsch vsliouniaev zanhsieh

repo: helm/charts

license_type: permissive

license_source: github-api


text:
[stable/datadog] Use Capabilities.APIVersions.Has instead of semver compare

What this PR does / why we need it:
Use Capabilities.APIVersions.Has to check for available rbac API.
Found at https://github.com/rook/rook/pull/1569.
Received the following error with Helm 2.7+:
[ERROR] templates/: render error in "datadog/templates/clusterrolebinding.yaml":
template: datadog/templates/_helpers.tpl:54:7: executing "rbac.apiVersion" at
<semverCompare ">=1.8...>: error calling semverCompare: Invalid Semantic Version

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): Did not create an issue.
Special notes for your reviewer: I'm not sure if this is backwards-compatible with older versions of Helm.

@hkaj @irabinovitch Any interest..?

/assign @sameersbn

/assign @hkaj


text:
[stable/wordpress] Improve getting LoadBalancer address in NOTES.txt

Testing a K8s cluster where LoadBalancer service returns hostname and not ip.
This PR change our current approach in bitnami helm charts where we report IP by doing
-o jsonpath='{.status.loadBalancer.ingress[0].ip}'

The new approach is to use
--template "{{"{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"}}"

where the . returns value for whatever field is in the map.
Source: https://github.com/helm/charts/issues/84#issuecomment-257754892
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

/approve

/lgtm

authors: carrodher davidkarlsen paulczar


text:
Unreasonable warning messages write to stderr

Helm v3.10.1
Unreasonable warning message redirect to stderr pipeline.
Since we used helm upgrade install xxx  command to install a chart to our cluster and it returned some warning messages.
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /devops/helm/deployCache/ffa49176-4f97-11ea-8974-ca049e4892c0_1672194886753413765/ins_14/bi/1.0.20/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /devops/helm/deployCache/ffa49176-4f97-11ea-8974-ca049e4892c0_1672194886753413765/ins_14/bi/1.0.20/config
W1228 02:34:48.144924    8736 warnings.go:70] autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler
W1228 02:34:48.149614    8736 warnings.go:70] autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler
W1228 02:34:48.235054    8736 warnings.go:70] autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler
W1228 02:34:48.235390    8736 warnings.go:70] autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler

It looks like some warning messages, but i have no idea about why these message is sent to stderr pipeline?  This caused our program failed.
And why these messages should not be in stdout?

The first two are printed by helm. See https://github.com/helm/helm/issues/8776#issuecomment-812146980 for some context.
The latter four are printed by kubernetes client-go. And beyond the control of helm.

@gjenkins8  Thanks for reply me.
Maybe we have a mistaken and here is my Go code
cmd := exec.Command(helmPath, commands...)
var stderr, stdout bytes.Buffer
cmd.Stdout = &stdout
cmd.Stderr = &stderr

Here i used exec package to execute helm upgrade install xxxx command and the above warning messages came from the stderr.  I wonder why these warning messages were in stderr rather than stdout?

@magicLian -- I'm not sure I understand. In your code snippet, you have helm's stderr going to the stderr buffer.
Did you mean to have something like cmd.Stderr = &stdout? (though I'm not familar enough with go's exec.Command(..) to know if both stdout and stderr can be written to the same bytes.Buffer).

I wonder why these warning messages were in stderr rather than stdout?

Because they're not part of the output of the program. If you were parsing yaml or json output from helm, those warnings would destroy your output.

Since this was answered and there's been no further activity, I'm going to go ahead and close this.

source: gharchive/issue

authors: gjenkins8 joejulian magicLian

repo: helm/helm


text:
Helm retry rollback fails when newly created resources are not cleared

Output of helm version: v3.10.3
Output of kubectl version: v1.25.3
Problem Description：
During Release rollback, if the resource waiting phase fails, Helm does not clear the newly created resources. As a result, subsequent rollback attempts fail.
1、During the first rollback, resources fail to be obtained because the network times out when waiting for the deployment to be ready. As a result, the rollback fails. Although CleanupOnFail is set to true, Helm does not clear the resources created during rollback.
2、During subsequent rollback retries, the resources created during the first rollback are not cleared. As a result, the subsequent rollback fails and the following error is reported:
warning: Rollback \"seq-gaussdb-demarcation-standby\" failed: no Service with the name \"seq-gaussdb-demarcation-standby\" found"

Cleanup on fail set, cleaning up 0 resources

an error occurred while cleaning up resources. original rollback error: no Service with the name \"seq-gaussdb-demarcation-standby\" found: unable to cleanup resources: object not found, skipping delete

Helm code:
https://github.com/helm/helm/blob/main/pkg/action/rollback.go#L234C4-L234C4
if r.Wait {
		if r.WaitForJobs {
			if err := r.cfg.KubeClient.WaitWithJobs(target, r.Timeout); err != nil {
				targetRelease.SetStatus(release.StatusFailed, fmt.Sprintf("Release %q failed: %s", targetRelease.Name, err.Error()))
				r.cfg.recordRelease(currentRelease)
				r.cfg.recordRelease(targetRelease)
				return targetRelease, errors.Wrapf(err, "release %s failed", targetRelease.Name)
			}
		} else {
			if err := r.cfg.KubeClient.Wait(target, r.Timeout); err != nil {
				targetRelease.SetStatus(release.StatusFailed, fmt.Sprintf("Release %q failed: %s", targetRelease.Name, err.Error()))
				r.cfg.recordRelease(currentRelease)
				r.cfg.recordRelease(targetRelease)
				return targetRelease, errors.Wrapf(err, "release %s failed", targetRelease.Name)
			}
		}
	}

Question：
When CleanupOnFail is set to true, can helm help clean up newly created resources when waiting for resources fails so that subsequent rollback retry succeeds?

I found that during the release upgrade, if the upgrade fails, the failRelease method provides a cleanup mechanism, but the rollback does not.


text:
Added List mode for Role, ClusterRole and Bindings

refs #5267
What this PR does / why we need it:
Kubernetes supports RoleList, RoleBindingList, ClusterRoleList and ClusterRoleBindingList, in order for a Role to be bound, it must already exist, for the List references, see: https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/rbac/types.go

Thanks @hickeyma ,
I have added it to the UninstallOrder and signed the commits.

Closing in favor of #5748


text:
Improve markdown rendering of commands help for shell completion

What this PR does / why we need it: Allow to have a readable doc on the onine Helm doc website
Special notes for your reviewer: Cf. helm/helm-www#1100
If applicable:

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

I've asked and the policy is that only regressions can be added to an RC.  So this will need to wait until the 3.7 release.
With some luck, the RC will have no problems and it will be the final 3.6 release, so it makes sense not to add anything unless it is absolutely critical.
I will merge into main.

authors: marckhouzam zigarn


text:
Unable to pull multiple in-line secrets

Operating system
Ubuntu 22.04.2 LTS
Helmfile Version
0.161.0
Helm Version
3.13.2
Bug description
I initially thought this was related to the helm-secrets plugin, although I may have been mistaken. Here is the original issue: https://github.com/jkroepke/helm-secrets/issues/449
TL;DR if I have the following environment values
secret1: ref+awssecrets://database#/user
secret2: ref+awssecrets://database#/pass

and reference those in my release's values (in a single line of yaml specifically)
userPass: { .Values.secret1 }ZZZ{ .Values.secret2 }

it renders as
userPass: awssecrets://database#/pass

instead of
userPass: usernameZZZmysecretpassword

I've found that using fetchSecretValue fixes this. So perhaps a question is, in what circumstances should you or should you not use fetchSecretValue?
Relevant discussion
https://github.com/jkroepke/helm-secrets/issues/449

After some digging, I found that I need to add a + to the end of the secret ref, which indicates the end of a secret ref.
Using the following works just as I expect now!
secret1: ref+awssecrets://database#/user+
secret2: ref+awssecrets://database#/pass+

repo: helmfile/helmfile

license: MIT


text:
Configure OpenShift

The QuickStart I created:
https://hub.openshift.com/quickstarts/298-helpy
Deploy link for the QuickStart (which the button would link to):
https://hub.openshift.com/quickstarts/deploy/298-helpy
I'm currently having problems with the deployment (seems hard to debug without the full logs) but will try again later. Not sure what will be involved to get it fully working, but it seems to be getting quite far.

Next issue:
Your Ruby version is 2.0.0, but your Gemfile specified 2.2.1

... for now I've removed the ruby version lock from Gemfile, because later Ruby versions are not yet supported. This page suggests that Ruby 2.0.0 is "Online (Next Gen)" which is promising, although there seems to be no cartridge available named ruby-2.2...

We need to make a decision about which version of the OpenShift platform we want to use.
The legacy version (v2?) seems to be the default; examples are for Rails 4 (or Rails 3), and it's almost working, although the Ruby version is locked to 2.0 (and unlikely to be updated to 2.2 on the legacy platform I would assume).
The new (containerised) version (v3?) has a Rails 4 example here, but seems more complicated to manage, and certainly seems more complicated to set up initially, and I don't see any reference to the "OpenShift Button" idea.
@brianjking do you have any other ideas?

If OpenShift doesn't meet our needs, we could alternatively create an AWS Marketplace offering, which should be pretty quick for users to get up and running.

Thanks for digging into this @olliebennett! It seems like their implementation is not quite as easy to work with as Heroku.  We could also create and maintain an "official" openshift branch and try to backport to Ruby 2 but I don't see a lot of value there.

authors: olliebennett scott

repo: helpyio/helpy

license: mit

license_source: bigquery


text:
Rename project

This project will be renamed to helx-search to be published on the PyPI repo with a more descriptive name. We will also organize it into a namespace repository, with "helx" as the parent namespace (other helx projects will subsequently be moved under this namespace).
Whereas currently users access it as
from dug import ...

The namespace will change to
from helx.search import ...

Likewise CLI tooling will change, from
dug crawl ...
dug search ...

to
helx crawl ...
helx search ...

Thats also entails archiving this repo and migrating the code to a new one

Marking this task as closed, since the install from source is easy and the Docker image is what we're really interested in anyway

repo: helxplatform/dug


text:
Update kube to 0.82 and k8s-openapi to 0.18 (and release as 0.22.0)

Release-As: 0.22.0
updated-dependencies:

dependency-name: kube dependency-type: direct:production
dependency-name: k8s-openapi dependency-type: direct:production

@hendrikmaus Gentle ping. I'm happy to help with the maintenance of this crate if you need, too.

Thanks for the help, I missed the notification on this one. My bad. I am happy to invite you into the project.

authors: hendrikmaus jbg

repo: hendrikmaus/kube-leader-election


text:
Wrong arXiv link in main read me file

Paper is easy to find anyway, but just in case you want to fix :)

Thanks, fixed :)

authors: hendrycks santiontanon

repo: hendrycks/apps


text:
解决方案检查

[X] 我已搜索issue列表(https://github.com/hennessey-v/GlaDOS_Checkin_ql/issues?utf8=✓&q=)，并没有发现类似的问题

青龙版本
正式版 v2.15.17
操作系统
Ubuntu 22
问题反馈
已获取并使用Env环境 Cookie
共获取到2个GlaDOS账号Cookie

脚本执行时间(北京时区): 2023/07/26 17:13:23

解析登录结果失败：'data'
解析登录结果失败：'data'
签到失败，请检查账户信息以及网络环境
GlaDOS签到通知

签到失败，请检查账户信息以及网络环境

按照readme安装配置脚本，首次运行提示没有requests模块，自行去“依赖管理”安装了requests。
附加信息
No response

问题已经解决，解决方法：把提取到的cookie按如下整理再填入变量：
koa:sess=***;koa:sess.sig=***

希望作者把这一步补充进readme免得有人像我一样。
另外希望在安装第一步添加说明依赖项requests

问题已经解决，解决方法：把提取到的cookie按如下整理再填入变量：
koa:sess=***;koa:sess.sig=***

希望作者把这一步补充进readme免得有人像我一样。 另外希望在安装第一步添加说明依赖项requests

好的，感谢反馈！

authors: RepentStar hennessey-v


text:
🛑 hentaiOS GitLab is down

In 5c8a1c0, hentaiOS GitLab (https://gitlab.hentaios.com) was down:

HTTP code: 403
Response time: 585 ms

Resolved: hentaiOS GitLab is back up in 7e590e7 after 5 minutes.


text:
🛑 hentaiOS Download Page is down

In ce99af1, hentaiOS Download Page (https://downloads.hentaios.com) was down:

HTTP code: 403
Response time: 51 ms

Resolved: hentaiOS Download Page is back up in 8394b09.


text:
Check for backup existence before trying to create it during backup sync

I'm using Ark 0.6.0, on GKE 1.8.6, It's working great (thank you for such a great tool)! Backups/restores are working correctly.
However, when I login to the GCP control panel, and click on "activity" (2nd tab on the main dashboard) I see the following errors:

Here are the logs from this specific backup (I see nothing notable):
ark.log
I only have two schedules currently, and they're for different namespaces:
$ ark schedule get
NAME                 STATUS    CREATED                         SCHEDULE        BACKUP TTL   LAST BACKUP   SELECTOR
APP1-bidaily   Enabled   2017-12-27 18:28:38 -0500 EST   25 6,12 * * *   720h0m0s     5h ago        <none>
APP2-bidaily      Enabled   2017-12-27 18:27:29 -0500 EST   25 6,12 * * *   720h0m0s     5h ago        <none>

Failed is a very strong word in application logs, and I can understand why @robbyt raised this issue.
Marking as a Bug and adding to v1.0.0 milestone for prioritization and scheduling.

authors: robbyt rosskukulinski

repo: heptio/ark


text:
替换过时的依赖项 rust-crypto

rust-crypto 已经很久没有更新了，它依赖了 rustc-serialize，在新版本的rust编译时会产生warning，类似于
warning: the following packages contain code that will be rejected by a future version of Rust: rustc-serialize v0.3.24

所以使用 https://github.com/RustCrypto/hashes 替换了 rust-crypto

赞！
先接受pr，这两天抽空发个新版本。

authors: cwbhhjl heqingpan


text:
Can't understand the step 2

Hi, I can't understand the step 2. Can you wrote more about it, I can't do anything it's so confusing fora non english native speaker and a begginner...

Hi @aesthetically1940s,
You can find "install path" setting in VSCode settings:

The preview still don't work... I'm sorry I'm new in it I can sounds stupid...

You need to pair { and }. It looks like there are several }s missing at the end of your script.
I recommend you to type a } immediately after typing { so it can't be missed.

Ok, I think I correct everything and now I can't see my focus tree omg this drives me crazy...

I changed a thing and now it says no fucos tree... I'm very lost...

Reason of no focus tree is that in first line "f" of focus_tree is removed.
In line 12 after modifier, an additional "}" is typed so "focus_tree = {" is closed, making it no focus inside the tree.
I recommend you to use syntax tools extension such as cwtools. There will be error markers when you meet such issues.


text:
stdenv -> module system

Move away from stdenv and its hooks.
Bash provides mediocre means of composition at best. I've helped someone troubleshoot an error that got its position distorted by eval. It's left us severely disillusioned.
Another potential issue is environment variables leaking from the effect's stdenv into nix-shell/nix develop.
Instead, effects could be composed using the module system allowing the reuse of some NixOS idioms, with the benefits of more type checking and a cleaner process environment.

Still keeping some of stdenv, which is useful, but can now start porting things to module style, since #107

repo: hercules-ci/hercules-ci-effects


text:
HARP-13055: Add individual TextElementStates for line markers

Signed-off-by: stefan.dachwitz stefan.dachwitz@here.com
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!

macbook tests please


text:
Adding CatalogEndpointProvider.

Api url can be static. In such cases we can avoid lookup request and
save some time. For that purpose we are adding CatalogEndpointProvider
to ApiLookupSettings.
ApiLookupClient will try to get url using the provider from settings
instead of making api lookup request. If it can't be done, behavior
of the client is unchanged.
Also adding unit and integration test for ApiLookupClient.
Resolves: OLPEDGE-2187
Signed-off-by: Kostiantyn Zvieriev ext-kostiantyn.zvieriev@here.com

Please fix your commit message:

Why are we adding this?
What is the purpose of this change?
What exactly did you add?

Additionally unit tests alone are not enough! Integration tests with VersionedLayerClient please!

added some details to the commit message and integration tests :-)

repo: heremaps/here-data-sdk-cpp


text:
C applications compiled with playground do not run with qemu

When I try to run a C application compiled with the method described in this repository with qemu, I always get the error message below.
The application runs without any error when using uhyve.
I am not sure if this is a bug or just not supported (yet). However , it would be great to be able to use qemu, as uhyve behaves not exactly the same and/or lacks of debugging messages in certain cases.
$ qemu-system-x86_64 -display none -smp 1 -m 64M -serial stdio  -kernel /path/to/rusty-loader -initrd /path/to/application -cpu qemu64,apic,fsgsbase,rdtscp,xsave,xsaveopt,fxsr
[LOADER] Loader: [0x100000 - 0x335018]
[LOADER] Found Multiboot information at 0x9500
[LOADER] Found module: [0x337000 - 0x4e0e20]
[LOADER] Module length: 0x1a9e20
[LOADER] Found an ELF module at 0x337000
[LOADER] Map 201 pages at 0x337000 (page size 4 KByte)
[LOADER] Map 1 pages at 0x400000 (page size 2048 KByte)
[LOADER] Allocating 0x70 bytes at 0x132D80, index 0
[LOADER] Allocating 0x4C8 bytes at 0x132E00, index 128
[LOADER] PANIC:
[LOADER] src/lib.rs:149:
[LOADER] assertion failed: elf.header.e_type == elf::header::ET_DYN
[LOADER]

It should now work. I updated the loader to support Qemu.

repo: hermitcore/hermit-playground


text:
Add refresh tokens to authentication API - PREVIEW

refresh tokens have separate expiry and encryption key config - DONE
refresh tokens are returned in Session object alongside the regular token - DONE
refresh tokens can only be used with AuthenticateRefresh request - DONE (provided the refresh_encryption_key is different from encryption_key)
/v2/authenticate/refresh plus Authorization header carrying the Bearer <refresh_token> returns a renewed token pair - DONE
Currently only added to AuthenticateDevice but I assume it will need adding to all other auth methods ?
what about before and after auth hooks ?
Also not implemented is the one-timeness of the refresh token - i think it will require some kind of state that keeps the track of already used tokens
default expiry of the refresh tokens is currently 3600 sec but should be longer probably

Merged under https://github.com/heroiclabs/nakama/pull/527.

Merged under https://github.com/heroiclabs/nakama/pull/527.

authors: michal-harish zyro

repo: heroiclabs/nakama


text:
feature: conditional per request timeout setting

Conditional timeout
You can set a conditional timeout per request.
Although make sure to always meet your requirements (e.g. Heroku 30s timeout) in all cases.
If the block returns nil or false, timeout will be disabled for this request.
# set conditional_timeout to a callable block
# config/initializers/rack_timeout.rb
Rack::Timeout.conditional_timeout = proc { |env| env["PATH_INFO"] =~ /^\/admin/ ? 20 : 5 }

# equivalent for Sinatra/Rack apps
use Rack::Timeout, conditional_timeout: ->(env) { env["PATH_INFO"] =~ /^\/admin/ ? 20 : 5 }

@kch Please look into this. Would help resolve Heroku timeouts.

You might want to see #56 (and #64 #67 #107)

Sad, but protecting developers from their very own mistakes is not an
attitude I would encourage. If they want to break their app in weird ways
let them. We are all using turing complete languages, and we should all use
them with great care. And if somebody builds software for the medical or
nuclear sector in Ruby... A whole different category of fail.
I submitted this patch because Rack::Timeout is a valuable tool even
outside of Heroku. In my case, allowing for long running requests on the
admin tool enables us, without much hassle, to do some heavier processing
in the request cycle.
We are luckily not running on Heroku so this does not cost us much, nor
does it break the whole app.
 gem "rack-timeout", github: "Overbryd/rack-timeout"

Cheers, Lukas

sent from my mobile

Am Dienstag, 30. August 2016 schrieb Jonathan Dance :

You might want to see #56 https://github.com/heroku/rack-timeout/pull/56
(and #64 https://github.com/heroku/rack-timeout/issues/64 #67
https://github.com/heroku/rack-timeout/issues/67 #107
https://github.com/heroku/rack-timeout/issues/107)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/heroku/rack-timeout/pull/110#issuecomment-243363584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABSd1wlmrEtGKnv21Zw-R1S6XFDi1RTks5qk-PYgaJpZM4JnYN3
.

I think this is one of the cleanest implementations I've seen submitted, and, yes, people keep requesting this feature and, yes, it is generally a bad idea, but people keep asking for it. I am not sure.
Whether you are on Heroku or not doesn't matter, the longer a request runs the more resources you are tying up. Using large deployments of Unicorn or Puma helps but if you have too many /admin requests your app will start suffering badly.
That said, rack-timeout is really a debugging tool and should not be relied upon to keep your app performing well. Aborting requests is actually quite dangerous and can lead to problematic database connections, etc. You really want other things to timeout before rack-timeout comes into play, like using statement_timeout for Postgres.
So, in short, this lets people shoot themselves in the foot either a bit more or a bit less, but rack-timeout is all about foot-shooting anyway, so does it really matter?

@Overbryd I think you have done a great job here and I would recommend that it gets merged as it is simplified and is something that many have requested (@sattish316, @hamitturkukaya, @ankane, 	@rpechayr, @zhuochun)
@wuputah If the functionality is added, then it should be up to the developer to shoot themselves in the foot. If this can allow exceptions to go past the Heroku (Or any other) timeout, then it should be an option Per Query not across the whole app. What we need is an option to use it when certain criteria is met.
@kch I had a look at #9 #56 #64 #67 #107 and there is mention of other methods to go around "long running reports/background jobs" but no mention in the Read Me or mention of a certain fork that would not cause other issues.

I think it's not really abut one particular case, at least the one I'm faced with it's not related to either Heroku, payments or whatever has already been mentioned in previous PRs or comments in this thread.
I don't want to explain my case particularly, because I think this feature should be added on the base of "Give developers flexibility". Yes, most of the times rack-timeout will be used with performance and protection in mind, but we can't just pretend that all software behaves exactly the same for exactly all cases.
adding this feature is not something that breaks any apps immediately and even more so, it's not like you're being forced to define a special route in the initializer.
It doesn't open any gaps or introduces any errors, it just gives people flexibility and that's good.

I'll just say that I'm not against this. Tho feet are really important and I'd personally refrain from shooting them, myself.

Last comment was from two years ago. I think that you can effectively get this same behavior by writing your own custom middleware that optionally calls rack-timeout which gives you maximum flexibility.
I say we close this for now. If you want, you could write a gem that does what I said (wraps rack-timeout) and publish it, perhaps as rack-timeout-conditional.

Shame that we have to increase ALL our timeouts just because of one endpoint. Would be awesome to have the possibility of configuring timeouts per endpoint for those odd cases when it actually does make sense. Yes a background worker would be better but adding it for one endpoint in an otherwise super simple service also adds dependencies on something like redis that then needs to be used.
Would have been super to just be able to bump a timeout for that one endpoint that processes some files.

Sure, I understand the desire which is why I would recommend making another library. If it's successful and the need is proved and the bugs are worked out then we can re-consider adding it back into this library.

authors: DJSAMPAT Overbryd elfenars kch mhenrixon schneems wuputah

repo: heroku/rack-timeout


text:
🛑 Software Center - Test 1 is down

In 2f99ff2, 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 1428ff8.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In dcae56e, 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 f913d50.


text:
🛑 Auth-Bridge - Test 1 is down

In b370851, 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 62de1e5.


text:
🛑 Software Center - Test 1 is down

In 78f4839, 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 2b48f0f.


text:
🛑 Auth-Bridge - Test 1 is down

In ce910ad, 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 fd938a1.


text:
🛑 Auth-Bridge - Test 1 is down

In 411b5a0, 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 d088d73 after 668 days, 5 hours, 5 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 3d241f9, 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 8e56107 after 671 days, 20 hours, 6 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In c3696d9, 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 9b499d6 after 21 minutes.


text:
🛑 Software Center - Test 1 is down

In c63a5a0, 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 eeb47a8 after 34 minutes.


text:
🛑 Software Center - Test 1 is down

In 3a8a7a3, 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 dcb4116 after 31 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 54cb6d7, 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 b02f536 after 18 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 2cde354, 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 525a570 after 34 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 0d46735, 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 1445a70 after 22 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 8fe1011, 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 5b94eb9 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In f17a60e, 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 17ae82c after 10 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 00343a6, 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 b157668 after 15 minutes.


text:
🛑 Software Center - Test 1 is down

In 3967a92, 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 bca71dc after 38 minutes.


text:
🛑 Software Center - Test 1 is down

In 5c4bacb, 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 491a202.


text:
🛑 Auth-Bridge - Test 1 is down

In 7efa08e, 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 2a6b9a4 after 22 minutes.


text:
🛑 Software Center - Test 1 is down

In a85620c, 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 b9ac375.


text:
🛑 Auth-Bridge - Test 1 is down

In 8edf36e, 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 cf5677a after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In cce74e4, 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 864ac3e after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 33e195c, 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 6cd16ba after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In e35df7b, 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 e8b6962 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 231d2fe, 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 905dcd1.


text:
🛑 Software Center - Test 1 is down

In eaee9e5, 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 63b3a4a.


text:
🛑 Software Center - Test 1 is down

In c2dea9c, 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 efc0f34.


text:
🛑 Software Center - Test 1 is down

In 2f643f9, 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 0b4fa5f.


text:
evaluate() meta element

$evaluate() $eval() $e()
Evaluates a generator set to one of its elements.
Accepts arguments similiar to pick().
Having a card: [[$abc:one:two]], and [[$eval(abc:0)]] would replace the generator set with its first element.
These definitions overwrite each other similiar to $style() meta elements (should be stored in a dict, in a step before evaluating generator sets).
Using wildcards and multiple indices, [[$eval(src1:*:0)]] Can become a way to imlement cloze cards

Some examples:
e(*) -> evaluate all zeroth sets to a random element
e(*:*) -> evalutate all zeroth sets to a random element
e(test:*) -> evaluate zeroth test to a random element
e(test) -> evaluate zeroth test to a random element
e(test:1:*) -> evaluate first test to a random element
e(test:*:2) -> evaluate all test to second element

If I compile $pick() and $eval() statements into a list, I can also add support for uniqueness constraints on $eval() statements: $eval(*:*, uc1). Would make $pick() and $eval() resemble each other.

Works.

repo: hgiesel/anki-set-randomizer


text:
make Dialect implement TypeContributor and FunctionContributor

There is little concrete benefit to this change, and it's slightly break-y but:

it removes a dependence on the @Incubating type QueryEngine from Dialect
we eat our own dogfood, that is, use our own abstractions
it appears that this was how it was originally intended to be

... and, I guess I just like it.

It looks cleaner indeed, but let's ask @sebersole about how he feels about the breakage.

Closing in favor of #5893

authors: beikov gavinking

repo: hibernate/hibernate-orm


text:
Require approval for Jenkins builds on PRs from external contributors + Safely publish build scans even for pull requests

This PR:

Makes sure that the Jenkins pipeline won't execute for PRs of external contributors until it's been approved. No approval is needed for members of the Hibernate organization.
Makes sure that secrets are exposed only to build steps that really need them, and in particular not to the actual build
Changes the GitHub actions build to use the pull_request_target event instead of pull_request, to have access to secrets, while still checkout out the PR head. This is a bit dodgy but safe if we're careful, see comments. More importantly this is strictly equivalent to what we're doing on Jenkins.
Adds publication of build scans to both the GitHub Actions build and the Jenkins build.

For Jenkins, the approval screen (using BlueOcean) will look like this:

Note we'll need to merge this PR before we can see the effect of the GitHub Actions changes.

There's something fishy about the credentials. The envrionment variable seems to get set unreliably.
For example it worked here: https://ci.hibernate.org/blue/organizations/jenkins/hibernate-orm-pipeline/detail/PR-8066/5/pipeline/91
But not here: https://ci.hibernate.org/blue/organizations/jenkins/hibernate-orm-pipeline/detail/PR-8066/6/pipeline/91
I'm starting to suspect that withCredentials stops working after an exception is thrown... but that's a bit wild.
Hey @marko-bekhta , did you notice something similar with Hibernate Search builds? Build scans not getting published on PRs due to missing credentials after a Maven execution failed?

did you notice something similar with Hibernate Search builds

Hmm, no. I think the only time I've noticed problems with the build scan publishing was when the token was rejected...

Ok I give up. This problem is specific to the s390x node. Looks like some unexpected behavior on OpenJ9 or the s390x architecture, but I don't have enough information to debug it.
I disabled build scans for PR builds on s390x, see last commit. Let's merge if the build passes :)

Merged. @beikov you'll know what to revert if things go wrong... If that happens, hopefully I'll be able to have a look after Devoxx.

authors: marko-bekhta yrodiere


text:
Add profile for the maven-dependency-check plugin

This is a plugin we're now using on Infinispan to spot CVEs in case you're interested.
The report is saved on target/dependency-check-report.html and can be generated with
mvn -Powasp clean install -DskipTests=true

thanks, interesting. Coincidence: I was just at a security related meetup yesterday night and they persuaded me into trying their tool which does something similar. Let's start with this though :+1:

authors: Sanne gustavonalle

repo: hibernate/hibernate-search


text:
Another set of performance related improvements

https://hibernate.atlassian.net/browse/HV-1501
https://hibernate.atlassian.net/browse/HV-1502
https://hibernate.atlassian.net/browse/HV-1503

Bean Validation benchmark (lower is better, average of 2 runs):

5.4.2.Final: 22938 ms
6.0.3.Final: 10488.5 ms
6.0.4-SNAPSHOT: 7418.5 ms

@gunnarmorling I reorganized the commits to remove the noise.
The only thing that still requires discussion is the Optional usage. Just let me know if you feel strongly about it and I'll move to the dummy constraint validator approach.

@gunnarmorling I think I fixed all your concerns. I also added a couple of cleanup commits that I kept for when we would agree on the approach.

@gsmet thanks a lot for the quick fixes! It looks great overall. The one thing I'm still feeling a bit unsure about is the usage of CHM in ConstraintTree (also if it's just when not using the default CVF), which could lead to creation of thousands of instances.
Did you have the chance to compare memory usage before and after the change? I think CHM isn't using as much memory when empty or with a few elements as it used to, but perhaps we can instantiate it with more fine-tuned settings at least?
I'm terms of an alternative, I only can think of either a dedicated map implementation geared towards our use case of very few elements or "turning around" the entire model and have a model instance per CVF. It'd allow to have a single, final CV in ConstraintTree,  but it'd be a substantial change and it may end up using even more memory, though.

Yes, that's something that's been bothering me too. But I don't think having a ContraintTree per CVF is such a good idea.
I think our best bet for now would be to keep the current situation as it is if not the default CVF i.e. to rely entirely on the ConstraintValidatorManager cache if the CVF is not the default one. It's far more efficient now that the CacheKey is based on the AnnotationDescriptor.

LGTM, merging. Thanks a lot, @gsmet!

authors: gsmet gunnarmorling

repo: hibernate/hibernate-validator


text:
🛑 Kiwi Farms Forum is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Kiwi Farms Forum is back up in bee13ad after 18 minutes.

repo: hickoryhouse/kf


text:
🛑 kiwifarms.hk is down

In 1a73821, kiwifarms.hk (https://kiwifarms.hk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kiwifarms.hk is back up in a062868 after 4 minutes.


text:
Fix use of deprecated asyncio functions

get_event_loop() throws a deprecation warning on Python 3.10, and will lose its ability to implicitly create an event loop in future versions.
Since Python 3.7, using asyncio.run() is preferred. And since heisenbridge seems to demand >=3.8, we can just safely switch to the new functions.
Likewise, asyncio.start_server() has losts its loop parameter in Python 3.10, so removing usage of that as well. It should always be able to deduce the current loop on its own.

Tested and LGTM, thanks!

authors: BtbN hifi

repo: hifi/heisenbridge


text:
styles/school-book.css applies style to all  (element selector, no classes)

Hi there!
I'm facing a case where my bundle un-intendenly included all the css files from hljs/styles (that's something I ought to fix, yes, but...)
Unlike all other .css files, school-book.css has a block defining styles for all pre elements, without any specificity
That's causing that, without initializing hljs in any way, all <pre> blocks are getting that yellow background image.

closed via https://github.com/highlightjs/highlight.js/pull/2034

thanks for your help on this @tincho!

authors: marcoscaceres tincho


text:
WIP: sql improvemenets

Resolves #2744.

much simpler SQL grammar
less context dependent so SQL snippets can be better highlighted
adds variable support
adds operator support
bloated SQL grammar moved to sql_more and aliased as "mysql" and "oraclesql"
reduces scope of the SQL grammar to "common" SQL
moves prior SQL support into sql_more and adds mysql and oraclesql aliases

But should we consider the SQL Standard?

It doesn't help that the "standard" isn't really available for viewing that I know of... am I wrong?

Should we highlight known function names? If yes, which ones?

The ones in the standard?

Highlighting just some of function calls looks ugly to me.

That's where I think we're helped if this is scoped to the "standard"... that should limit the number of functions significantly I'd think.  And if you're really just talking about user defined vs built-ins... I'm not sure why that's an issue... in many grammars we highlight built-in functions but not user defined ones...

And we unfortunately cannot tell function call from, say, table declaration.

Can't we?  CREATE TABLE is pretty clear. :-)  There may indeed be too many contexts to properly detect function dispatch, I haven't given it much thought.

For example, varchar2 is Oracle-only datatype

I specifically left the list of datatypes "wide".  I have no idea what data types might be in the "standard"

Third. List of keywords must be checked carefully. For example ... [snip] ... last_insert_rowid is SQLite-only function etc.

Well, again the lack of available docs on an actual "standard" is really an issue... so I actually based this off of SQLite as a "lowest common denominator"... I was fully expecting we'd grown and improve this slightly after the first pass.  Is there actual free/public documentation somewhere of the actual SQL standard?

Honestly I'm a little less interested in the "purity" of this rather than the reduction in scope and having some idea what's in it (plus making it easier to maintain)... just googling 1000 keywords from the existing SQL one by one to figure out what was from what was NOT on my bucket list.
I definitely would like to avoid "keyword of the week" contributions (from random SQL variants) to the grammar going forward though. :-)  I kind of imagined something like:

keyword is proposed/suggested
do all major DBs support?
If yes, then add.
If no, add to vendor specific grammar.

It doesn't help that the "standard" isn't really available for viewing that I know of... am I wrong?

Full document is available for $$$. But e.g. https://modern-sql.com/standard gives a great list of freely available resources, including BNF grammar and working drafts of the standard. It is enough for sure.

And we unfortunately cannot tell function call from, say, table declaration.

Can't we? CREATE TABLE is pretty clear. :-) There may indeed be too many contexts to properly detect function dispatch, I haven't given it much thought.

Right, too many contexts. I remember I gave up when working on pgsql.

Honestly I'm a little less interested in the "purity" of this rather than the reduction in scope and having some idea what's in it (plus making it easier to maintain)...

Well, I see a problem in it. If the sql grammar is purified down to the standard + "common denominator", it is easy to reject complains like "this is highlighted incorrectly for my database system". But if you left, e.g. varchar2, but get rid of CONNECT BY, it is more difficult to justify. It will look like we simply messed up Oracle support for no reason.
"Common denominator" is also needed in addition to the standard. E. g. there is no such thing as index in the standard (and hence no CREATE INDEX), although it is supported by each and every DBMS.

I definitely would like to avoid "keyword of the week" contributions

Absolutely agree.

If the sql grammar is purified down to the standard + "common denominator", it is easy to reject complains like "this is highlighted incorrectly for my database system".

Yeah... I follow.  I was just laying out my thoughts.  If this ends up just LCD that's fine...

@egor-rogov I think this is not going to be super easy... For example I'm familiar with BLOB, but not "BINARY LARGE OBJECT"... so it seems there may be a lot of cases where the standard says one thing but then the implementation is totally different... so having "BINARY LARGE OBJECT" in our grammar wouldn't accomplish much at all.
I think I could get a handle on the datatypes and AGG functions, but that still leaves other built in functions and then the large list of "keywords" in general.

And just to make it harder there is Google's "Standard SQL": https://cloud.google.com/bigquery/docs/reference/standard-sql/scripting
No idea how standard it is.

@egor-rogov I'm fine dropping all the non-aggregate functions for a first pass if you think that's simpler... but how do you want to handle the keyword list?  I did some googling plus my knowledge of SQL and took a quick pass and flagged almost half of the keywords as "good to go"...  would you want to do the same?
Then at the end we just remove those we are unsure of?
Any chance we could have this cleaned up in the next week?  I was hoping to release 10.3 around mid-month, but I suppose I could push it off a bit further.

And just to make it harder there is Google's "Standard SQL": https://cloud.google.com/bigquery/docs/reference/standard-sql/scripting
No idea how standard it is.

It is not.

I did some googling plus my knowledge of SQL and took a quick pass and flagged almost half of the keywords as "good to go"...  would you want to do the same?

Yes I'm going to do the same. Not sure how much time will it take, let's see.

Some thoughts on keywords.
SQL has so-called reserved words, most of which can go straight to our keywords: https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html#reserved-word
Although there are such words as AVG, COUNT etc, which should rather be built-ins.
Also SQL has so-called non-reserved words, which can have special meaning in some contexts, while can be used freely in other contexts: https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html#non-reserved-word
The latter are harder ones... E. g. KEY is a non-reserved word. In PRIMARY KEY it is a keyword, but you can rightfully create a table with key column.

I made a quick pass through the datatypes.
The following are non-standard: bool (?), void (PostgreSQL), number (Oracle).
What class should we use for datatypes? We have type class, which seems to be a better choice to me than built-in.
Now, the standard has the following large range of datatypes (a lot of nultiword combos):
-- character

character
char
character varying
char varying
varchar

national character
national char
nchar
national character varying
national char varying
nchar varying

-- LOBs

character large object
char large object
clob
national character large object
nchar large object
nclob
binary large object
blob

-- binary

binary
binary varying
varbinary

-- numbers

numeric
decimal
dec
smallint
integer
int
bigint

float
real
double precision

decfloat

-- boolean

boolean

-- date & time

date
time
timestamp
time
time ... with timestamp
time ... without timestamp
timestamp
timestamp ... with timestamp
timestamp ... without timestamp

-- others

interval
row
ref
scope
array
multiset

Note that character types can have length specifier in form of \d+ CHARACTERS or \d+ OCTETS. How these two keywords should be highlighted?..

time ... with timestamp
time ... without timestamp

Do you mean timezone?

row
ref
scope
array
multiset

I'm not very familiar with these...  do you think they all should be built-in/datatypes rather than keywords?

The latter are harder ones... E. g. KEY is a non-reserved word. In PRIMARY KEY it is a keyword, but you can rightfully create a table with key column.

I'm ok with special casing these "pairs" if there aren't too many... that way we decrease false positives in auto-detect against other languages as well as making the grammar smarter.

Also SQL has so-called non-reserved words, which can have special meaning in some contexts, while can be used freely in other contexts:

Ok, yikes, that's a ton.  I think I'm in favor of just leaving almost all of these out of the grammar...  maybe pull in a few that are SUPER common (like KEY in FOREIGN KEY, PRIMARY KEY, etc) that we can specify contextual rules... I didn't see a lot of others that jumped out at me though.

The latter are harder ones... E. g. KEY is a non-reserved word. In PRIMARY KEY it is a keyword, but you can rightfully create a table with key column.

You only mean unquoted without context?  Surely I can name a column some of these reserved words if it was properly quoted, yes?

Do you mean timezone?

Oh, of course.

row
ref
scope
array
multiset

I'm not very familiar with these... do you think they all should be built-in/datatypes rather than keywords?

Hmm... Looks like we don't really want any of those except ROW. They are intended for use in procedural languages like Ada, PL/I etc. I don't think we want to support all of those languages inside sql grammar (:
ROW is a datatype, like INTERVAL.

I think I'm in favor of just leaving almost all of these [non-reserved keywords] out of the grammar...

I don't think so. Probably we'd better add them as keywords by default and move some of them to "combos"... But don't hurry, give me some time to have a look.

You only mean unquoted without context? Surely I can name a column some of these reserved words if it was properly quoted, yes?

Sure. Quoted identifiers are easy.

As TIMEZONE not in the keywords list, I think WITH TIMEZONE and WITHOUT TIMEZONE should be in MULTI_WORD_BUILT_INS.

I've identified the following functions (or expressions that are not technically functions, but otherwise look like functions) in the list of reserved keywords:
ABS
ACOS
ARRAY_AGG
ASIN
ATAN
AVG
CAST
CEIL
CEILING
COALESCE
COS
COSH
COVAR_POP
COVAR_SAMP
CUME_DIST
DENSE_RANK
DEREF
ELEMENT
EXP
FIRST_VALUE
FLOOR
JSON_ARRAY
JSON_ARRAYAGG
JSON_EXISTS
JSON_OBJECT
JSON_OBJECTAGG
JSON_QUERY
JSON_TABLE
JSON_TABLE_PRIMITIVE
JSON_VALUE
LAG
LAST_VALUE
LISTAGG
LN
LOG
LOG10
LOWER
MAX
MIN
MOD
NTH_VALUE
NTILE
NULLIF
PERCENT_RANK
PERCENTILE_CONT
PERCENTILE_DISC
POSITION
POSITION_REGEX
POWER
RANK
REGR_AVGX
REGR_AVGY
REGR_COUNT
REGR_INTERCEPT
REGR_R2
REGR_SLOPE
REGR_SXX
REGR_SXY
REGR_SYY
ROW_NUMBER
SIN
SINH
SQRT
STDDEV_POP
STDDEV_SAMP
SUBSTRING
SUBSTRING_REGEX
SUM
TAN
TANH
TRANSLATE
TRANSLATE_REGEX
TREAT
TRIM
TRIM_ARRAY
UNNEST
UPPER
VALUE_OF
VAR_POP
VAR_SAMP
WIDTH_BUCKET

Maybe there are more. What about them? Should we highlight them as function calls?
Also there are some expressions that also look like functions, but don't require () after them. Those are mainly CURRENT_*. And what about them?..

As TIMEZONE not in the keywords list, I think WITH TIMEZONE and WITHOUT TIMEZONE should be in MULTI_WORD_BUILT_INS.

Sure.

What about them? Should we highlight them as function calls?

Sure.

Also there are some expressions that also look like functions, but don't require () after them. Those are mainly CURRENT_*. And what about them?..

Why not just keywords?  Are you saying you're now in favor of only CURRENT_* and this list and letting any others in the non-reserved just fall to the floor?

Why not just keywords? Unless you're saying the functions should be built-ins... moving the data types to "type". So if that was the question then I'm fine with CURRENT_* being built-in...

Hm... Standard calls them "functions". And some of them can be used either with or without parens. E. g. current_time or current_time(3) (time precision).
Here is the list of strictly-no-parens to start with:
CURRENT_CATALOG
CURRENT_DATE
CURRENT_DEFAULT_TRANSFORM_GROUP
CURRENT_PATH
CURRENT_ROLE
CURRENT_SCHEMA
CURRENT_TRANSFORM_GROUP_FOR_TYPE
CURRENT_USER
SESSION_USER
SYSTEM_TIME
SYSTEM_USER

And here are the others:
CURRENT_TIME
LOCALTIME
CURRENT_TIMESTAMP
LOCALTIMESTAMP

Now, let's decide what to do with expressions like extract.
The syntax is like follows:
EXTRACT ( field FROM expression )

Here "field" is one of the following:
TIMEZONE_HOUR
TIMEZONE_MINUTE
YEAR
MONTH
DAY
HOUR
MINUTE
SECOND

Okay, FROM is a keyword for sure. What about EXTRACT and field names?
Looks like EXTRACT should be a function, just like SUBSTRING, which also has the fancy syntax like SUBSTRING ( expression FROM start_position FOR length USING units ).
And field names maybe built-ins? Or keywords? They all are reserved keywords, but intuitively I'd like to "draw a line" somewhere, as you suggested.

Standard calls them "functions". And some of them can be used either with or without parens.

I'm lost, what are we talking about?  Are you talking about whether we color them built_in or keyword?  I'm inclined to just leave them in the original groups (per the reference page) and see if anyone cares about the distinction later.

What do you think about leaving SQL/XML and SQL/JSON out of scope? Both are languages in themselves...

HAHA, I'm fine with this... sounds like sublanguages or submode problem anyways.

I'm tempted to just remove the separate lists and have ONLY a single reserved word list... and do it all contextually... thoughts?
[word]      # must be keyword (no dispatch)
[word](    # built_in/func
[word] (   # built_in/func

@egor-rogov The COMBOS are potentially for relevance though I haven't gone there yet. "create table" screams SQL where-as "table create" not so much.

I'm really temped to add a UPPERCASE = keyword rule as well since this is our generic grammar...

And field names maybe built-ins? Or keywords?

I say just leave them keywords for now.

@egor-rogov Any thoughts on last pass?

I really want to get back to it, but I won't have enough time to concentrate in the next 3 weeks or so.

@egor-rogov  Probably going to push 10.5 soon, any chance you have any time to revisit this?

Standard calls them "functions". And some of them can be used either with or without parens.

I'm lost, what are we talking about? Are you just talking about whether we color them built_in or keyword?

I am trying to say that it's natural (to me at least) to highlight, say, extract(...) as function call, like any other functions like count() etc. Currently it's built_in (but perhaps we'll need another class for function calls someday).
Disagree?

I am trying to say that it's natural (to me at least) to highlight, say, extract(...) as function call

We do already, it's in RESERVED_FUNCTIONS.

Currently it's built_in

Right, that's what we typically highlight functions as...

(but perhaps we'll need another class for function calls someday).

We need a "function dispatch" which is mention in other threads... and that would prevent the hard coded list entirely and we could just match any BLAH() pattern as a function.  I'm not sure there is a strong need to highlight functions as functions if they have no ()... but we could cross that bridge when we get there.
Personally I feel like this is "good enough" to merge and we can continue to tweak over time.  Otherwise it's going to miss 10.5 and get pushed to 2021. :(

Following this logic, you can easily justify addition of some non-standard keywords, popular in some db engines. It doesn't cause problems, ugh?

Also, just to be 100% clear the problem was never non-standard keywords.  The problem was that the current list was unmaintainable and would take HOURS to google/sort them... Now I don't want to start adding a ton of keywords back to this - I think it should stay simple (and encourage 3rd party grammars) - but if the vendor-specific keywords had all been nicely grouped into ORACLE_KEYWORDS, MYSQL_KEYWORDS, etc... I would have had far less issue and there would have been far less need for this reboot.

I am trying to say that it's natural (to me at least) to highlight, say, extract(...) as function call

We do already, it's in RESERVED_FUNCTIONS.

Yeah, great. And what about, say, localtime? According to the standard, you can use it as localtime(3) or localtime (no parens). Should it be built_in in the first case? And in the second case?
(My answer is yes for both.)

We need a "function dispatch" which is mention in other threads... and that would prevent the hard coded list entirely and we could just match any BLAH() pattern as a function. I'm not sure there is a strong need to highlight functions as functions if they have no ()... but we could cross that bridge when we get there.

Consider CREATE TABLE foo(a integer);. I can't see a (easy) way to tell foo from function call. And I'm afraid there are other cases like this.

Consider CREATE TABLE foo(a integer);. I can't see a (easy) way to tell foo from function call.

Well it's immediately proceeded by CREATE TABLE for one, but this is a problem for another day.

According to the standard, you can use it as localtime(3) or localtime (no parens). Should it be built_in in the first case? And in the second case?
(My answer is yes for both.)

That's just adding built_in: FUNCTIONS to keywords... I'm find with doing that.

Now I don't want to start adding a ton of keywords back to this - I think it should stay simple (and encourage 3rd party grammars) - but if the vendor-specific keywords had all been nicely grouped into ORACLE_KEYWORDS, MYSQL_KEYWORDS, etc... I would have had far less issue and there would have been far less need for this reboot.

You contradict yourself (:
Having vendor-specific keywords/types/etc does not encourage 3rd party grammars. It encourages complaints on poor support of XXX database.

That's just adding built_in: FUNCTIONS to keywords... I'm fine with doing that. But if the problem is it's only "some" functions (which I believe is correct) then are you wanting to provide me with that list of WHICH ones?

https://github.com/highlightjs/highlight.js/pull/2740#issuecomment-707861055

Do we really want to maintain that list long-term if there is no official list of these but we're doing it "by sight"?

I think the list is pretty static.

Having vendor-specific keywords/types/etc does not encourage 3rd party grammars. It encourages complaints on poor support of XXX database.

I wasn't making an argument to go backwards, just saying that just having the keywords wasn't the biggest problem with SQL...  I also think it can be BOTH.  Just having a slightly enhanced list of types makes SQL super useful for CREATE TABLE style snippets for example.  But if someone is writing super complex queries then yes, they will always be better served by a more specific grammar.
Like almost everything in life I don't think this is black and white.

I've made some kinda real-life tests. Generally everything looks decent.
Some more tweaks:

Add count and lead to RESERVED_FUNCTIONS.
Both words from combos must be highlighted as keywords.
I'd add desc, asc, and view to NON_RESERVED_WORDS.
I'd remove null from LITERALS (it's in RESERVED_WORDS). Not sure it's correct to call NULL literal, and clauses like IS [NOT] NULL look strange that way.

Both words from combos must be highlighted as keywords.

Are we just simply missing some words from keywords you mean?

Done and done.  Anything else? :)

authors: egor-rogov joshgoebel


text:
investigate Killarney campgrounds

La Cloche Silhouette trail should have a bunch of campgrounds in its northeast quadrant, but seems to have none

I did a quick spot check against https://www.timandvictoria.com/blog/2019-11-11-hike-la-cloche-silhouette-trail/, and enabled camp_pitch POIs -- I think they're legitimately absent from OSM, not a bug on my end, so closing.

repo: hikeratlas/basemap


text:
いいところ診断の結果に優しさを追加したい

以下の結果を追加したい
'{userName}のいいところは優しさです。あなたの優しい雰囲気や立ち振る舞いに多くの人が癒やされています。'

これから対応します。

repo: hillwalker/assessment


text:
Update chart after props change

I'm new to svelte so I may be missing something. I have code like this
    let reducedData = regionalData.reduce(foldfn, {});
    let vals = Object.values(reducedData);
    let datasets = [];
    let data = {
        labels: [],
        datasets,
    };

    afterUpdate(() => {
        datasets = selectedRegions.map((item) => {
            const fqn = item[0] + "-" + item[1];
            return { name: item[1], values: vals.map((r) => r[fqn]) };
        });
        data = {
            labels: Object.keys(reducedData),
            datasets,
        };
        if (chartRef) chartRef.update(data);
    });
</script>

    <Chart
        type="line"
        height="500"
        {data}
        {lineOptions}
        {axisOptions}
        bind:this={chartRef} />

selectedRegions is set by the props and can change. But although I see data changing (use @debug) the chart does not redraw.
I noticed that you add bind:this={chartRef} through the examples when they are supposed to be updatable, and use chartRef in the example. But the use of chartRef is missing in the update all example. It seemed as though .update should have worked but I am getting TypeError: chartRef.update is not a function

I believe there may be some confusion in the documentation about what chartRef actually is. It is not the chart constructed by calling new frappe.Chart, but instead is a Svelte component binding (using this):

Note that you shouldn't need to add that afterUpdate call at all, because this component already does that when the props update. So as far as I can tell, your issue might be with how you're using Svelte here. I think by making your selectedRegions a reactive declaration (and/or perhaps some other variables in your code), you might be able to have this working like you expect. This library reacts to prop changes though, so I would expect your charts to redraw on prop changes.
In any case, I don't think this is an issue with svelte-frappe-charts, so I will close this for now, but I am happy to re-open if you have any more info or think there is indeed a bug in this library! 👍

I believe there may be some confusion in the documentation about what chartRef actually is. It is not the chart constructed by calling new frappe.Chart, but instead is a Svelte component binding (using this):

Note that you shouldn't need to add that afterUpdate call at all, because this component already does that when the props update. So as far as I can tell, your issue might be with how you're using Svelte here. I think by making your selectedRegions a reactive declaration (and/or perhaps some other variables in your code), you might be able to have this working like you expect. This library reacts to prop changes though, so I would expect your charts to redraw on prop changes.
In any case, I don't think this is an issue with svelte-frappe-charts, so I will close this for now, but I am happy to re-open if you have any more info or think there is indeed a bug in this library! 👍

repo: himynameisdave/svelte-frappe-charts


text:
🛑 Main Page is down

In 6469e03, Main Page (https://hinzwifi.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main Page is back up in fdc3f5e after 16 minutes.

repo: hinzwifi/uptime-hinz


text:
Make Verbs Table Name Configurable

The PR introduces the ability to configure the table names used by Verbs. The idea behind this is that some people wish to prefix their table names based on which part of the system the table belongs to or change the database table name entirely.

@onairmarc thanks for the PR! Tests are failing as it looks like the setTable method needs to be public. Also could you see if you can add some tests for this? Thanks!

@joshhanley Yep! Already on it! Thanks!

@joshhanley added!

@joshhanley is there anything else you need me to change for this?

@onairmarc nope, looks good to me. But merging isn't up to me, @inxilpro or @DanielCoulbourne have the final say 🙂

@onairmarc do you see any issues with my refactor? I think it's better to just use the default getTable() behavior of Laravel, rather than override how setTable() works. (I also made a minor change to the config names, but that's just superficial.)

@inxilpro LGTM!

authors: inxilpro joshhanley onairmarc

repo: hirethunk/verbs


text:
Extension doesn't work with WSL

When I tried to add this extension to my WSL it wasn't able to start LSP client, failed to deliver proper syntax highlighting and messed up with brackets highlighting.
Unfortunately I can't provide any meaningful logs as extendible doesn't produce any.

Hey @LNow! Do you mind trying again with the latest release from the Marketplace (0.5.3)? Thanks!

@lgalabru now it works correctly.
Thank you for fixing it!

authors: LNow lgalabru

repo: hirosystems/clarity-lsp


text:
Indexing from scratch always detects gaps and stops

Indexing from scratch always detects gaps, this seems to happen with all latest releases of ordinals-api. I've tried v2.1.1 , v2.2.0, v3.0.0, and getting the same result at block height near 810k+-:
{
  "level": "error",
  "time": "2024-03-01T13:19:21.676Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "err": {
    "type": "BadPayloadRequestError",
    "message": "Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.",
    "stack": "BadPayloadRequestError: Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.\n    at assertNoBlockInscriptionGap (/app/dist/src/pg/helpers.js:23:19)\n    at /app/dist/src/pg/pg-store.js:85:59\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async scope (/app/node_modules/postgres/cjs/src/index.js:226:18)\n    at async Function.begin (/app/node_modules/postgres/cjs/src/index.js:213:14)\n    at async PgStore.updateInscriptions (/app/dist/src/pg/pg-store.js:52:9)\n    at async /app/dist/src/ordhook/server.js:57:9\n    at async Object.<anonymous> (/app/node_modules/@hirosystems/chainhook-client/dist/server.js:177:17)",
    "name": "BadPayloadRequestError"
  },
  "msg": "ChainhookEventObserver bad payload"
}
{
  "level": "info",
  "time": "2024-03-01T13:19:21.677Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "reqId": "req-51",
  "res": {
    "statusCode": 400
  },
  "responseTime": 116.15277099609375,
  "msg": "request completed"
}

{
  "level": "error",
  "time": "2024-03-01T13:19:21.676Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "err": {
    "type": "BadPayloadRequestError",
    "message": "Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.",
    "stack": "BadPayloadRequestError: Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.\n    at assertNoBlockInscriptionGap (/app/dist/src/pg/helpers.js:23:19)\n    at /app/dist/src/pg/pg-store.js:85:59\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async scope (/app/node_modules/postgres/cjs/src/index.js:226:18)\n    at async Function.begin (/app/node_modules/postgres/cjs/src/index.js:213:14)\n    at async PgStore.updateInscriptions (/app/dist/src/pg/pg-store.js:52:9)\n    at async /app/dist/src/ordhook/server.js:57:9\n    at async Object.<anonymous> (/app/node_modules/@hirosystems/chainhook-client/dist/server.js:177:17)",
    "name": "BadPayloadRequestError"
  },
  "msg": "ChainhookEventObserver bad payload"
}
{
  "level": "info",
  "time": "2024-03-01T13:19:21.677Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "reqId": "req-51",
  "res": {
    "statusCode": 400
  },
  "responseTime": 116.15277099609375,
  "msg": "request completed"
}

@alexqrid can you share more details about the ordhook setup you have? there could be a version mismatch between the two

Closing this, please reopen if you have any more questions

authors: alexqrid rafaelcr

repo: hirosystems/ordinals-api


text:
add intro and example of stain norm docs

Description
Update documentation with stain normalization methods (Macenko and Reinhard)
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR

Fixes:

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

IMHO I'd add an example of the usage of the stain normalizer

Hi @nicolebussola I agree with @ernestoarbitrio, a usage example would be great!

@nicolebussola ehm the docs are not rendering the API docs and the example (you can see the readthedocs check), can you fix this please?

I can see the page @alessiamarcolini  https://histolab--506.org.readthedocs.build/en/506/api/stain_normalizer.html

@ernestoarbitrio yes the page does exist, the docs are not rendering the API docs and the example

@ernestoarbitrio yes the page does exist, the docs are not rendering the API docs and the example

what do you see? I do see this:

is ☝🏽 wrong?

when will these features be made available in a conda package? i'd implement them in my pipelines today if they were available.

Hi @hannah413
this PR only introduces changes to the documentation, the features are already included in our latest release :)

@alessiamarcolini hmm. histolab 0.5.1 is the most up to date version available on conda. i have histolab 0.5.1 installed and can run tissue extraction with it, but when i try to import a stain normalizer like this it says the module doesn't exist:

ModuleNotFoundError                       Traceback (most recent call last)
Cell In[1], line 1
----> 1 from histolab.stain_normalizer import ReinhardStainNormalizer

ModuleNotFoundError: No module named 'histolab.stain_normalizer'

@hannah413 it looks like the latest 0.6.0 release is only available on PyPI for some reason 🤔 on it!

@alessiamarcolini thank you!!!

authors: alessiamarcolini ernestoarbitrio hannah413 nicolebussola

repo: histolab/histolab


text:
V-COCO Evaluation Error

Hello,
Many thanks for your great work.
I am trying to evaluate your pre-trained models on V-COCO.

So, I first generate the official detection pickle via:

python generate_vcoco_official.py \
        --param_path ./params/qpic_resnet50_vcoco.pth \
        --save_path ./logs_vcoco/vcoco.pickle \
        --hoi_path ./data/v-coco

Later, I use the official evaluation code via the following:

from vsrl_eval import VCOCOeval

vsrl_annot_file_s='./data/v-coco/data/vcoco/vcoco_val.json'
split_file_s='./data/v-coco/data/splits/vcoco_val.ids'

coco_file_s='./data/v-coco/data/instances_vcoco_all_2014.json'
vcocoeval = VCOCOeval(vsrl_annot_file_s, coco_file_s, split_file_s)

file_name= './logs_vcoco/vcoco.pickle'
vcocoeval._do_eval(file_name, ovr_thresh=0.5)

Please note that I adapted the latter script from VSG-Net repo. I face the following error during evaluation:
zero-size array to reduction operation minimum which has no identity
on       assert(np.amax(rec) <= 1) within  _do_agent_eval()  function execution.
I wonder if this is a common error, and how it can be mitigated?
Many thanks.

Resolved by changing val to test set. Some images in the validation set do not return any results failing the evaluation.

repo: hitachi-rd-cv/qpic


text:
NotAuthorizedOrNotFound

When I run the script it returns:
{
"code": "NotAuthorizedOrNotFound",
"message": "Authorization failed or requested resource not found."
}
I tried to do:
oci iam user get --user-id {USER-ID}
To check is the API fine and looks fine
what might be happening?

I had double checked:
OCI_REGION
OCI_USER_ID
OCI_TENANCY_ID
OCI_KEY_FINGERPRINT
OCI_PRIVATE_KEY_FILENAME
against my .oci/config file
and if I modify only a single letter of the above parameters the error changes to:
{
"code": "NotAuthenticated",
"message": "The required information to complete authentication was not provided or was incorrect."
}
How I can enable the --debug flag in the script to have more information about was wrong?

I found the problem the OCI_IMAGE_ID variable had a line break that I didn't notice before.
Anyway thank you for your good work!!!

repo: hitrov/oci-arm-host-capacity


text:
不要と思われる一文が記載されている

gas_slack_lecture_text.pdf (v1.1) の P.51 に「2019 年冬に私の勤務している株式会社」という一文があります。
文脈を踏まえると恐らく不要な文かと思われます。

コード上では下記の箇所になると思います。
https://github.com/hitsumabushi845/gas-slack-integration-text/blob/b5a45a95957fa587dcdd951d13ee35e381a210bc/gas_slack_lecture_text.tex#L1389

@ossan-pg
ご指摘ありがとうございます。
修正し、リリースしました。
https://github.com/hitsumabushi845/gas-slack-integration-text/releases/tag/v1.2


text:
Remember the streaming response object in watch-queries

Short story:
For a termination of a streaming response from outside, the response object should be exposed from the watch-queries.
Long story:
pykube uses the streaming responses of requests for watching over the objects. These responses can be cancelled when a chunk/line is yielded to the consumer, and the streaming socket itself is waiting.
However, if a streaming response is in the blocking read() operation on a socket, and nothing happens on the stream (i.e. no k8s watch-events), it can remain there for long time — minutes, hours — until some data arrives on the socket. This, in turn, makes the application to hang on exit, holding its pod from restarting, since the thread is not finished until the read() call is finished.
There is no easy way to terminate the blocking read() operation on a socket, and therefore the watching stream — if it runs in a parallel thread. The only way is a dirty hack with the process signals, which interrupt the I/O operations. See a preview in https://github.com/zalando-incubator/kopf/pull/143. This hack can be done only from the main thread, and therefore is only suitable for the runnable application rather than for a library.

Thanks!

authors: hjacobs nolar

repo: hjacobs/pykube


text:
Transitioning to the Angular 6+ is not possible for Angular CLI

Hello,
I have a project that is working on Angular 5.
The table component is working like a charm.
However, after I update the project to Angular 6, by using this link
I get the following error:

Package "@angular-generic-table/core" has an incompatible peer dependency to "@angular/core" (requires "^4.0.0" (extended), would install "6.1.10").
Package "@angular-generic-table/core" has an incompatible peer dependency to "@angular/common" (requires "^4.0.0" (extended), would install "6.1.10").

Could you please help?

Hi @demid5111 , in angular cli documentation you can find parameters when running ng update for this kind of errors,
please try
ng update --all --force
It basically avoids/ignores all the dependency-checks and updates all the packages wherever applicable.
I hope it helps.
Thanks

Does that mean that tables will be still working with Angular 6? пятница, 02 ноября 2018г., 23:30 +03:00 от Dennis Gonzalez  notifications@github.com :

Hi  @demid5111 , in angular cli documentation you can find parameters when running ng update for this kind of errors,
please try
ng update --all --force
It basically avoids/ignores all the dependency-checks and updates all the packages wherever applicable.
I hope it helps.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly,  view it on GitHub , or  mute the thread .

however, I get the error as updating to the 6th version also requires to use rxjs v6

@demid5111 Hi, this is not my library, Im just trying to help,
Did you try to run in your angular folder?
 npm install rxjs-compat tether --save
That library is for compatibility to previous version of rxjs lib( i read somewhere they plan to removed in next versions but no sure is they did it on version 7)
i have it running on version 6 with no problem and i use very complex concepts like lazy loading in some cases, customs header components and custom rows.
Also if you can't make it work check other alternatives like material https://material.angular.io/components/table/examples
Thanks

Sorry for being a little late to the party and thanks @crash1988 for helping out:) It should work just fine with angular 6 following the steps crash explained above. However I haven’t tried using it with angular 7 just yet but it should work too as there are no major breaking changes between angular 6 and 7 that should affect angular-generic-table.
That said I hope I’ll get some time soon to release a new version using the latest version of angular including version 6 of rxjs.
There are a lot of things on the list of things that could be improved since both angular and angular cli has come a long way since this library was written. Not to mention some interesting things to come with the new ivy compiler that hopefully will be release soon:)
Anyways, let me know if the above solotion doesn’t work for you @demid5111 until a new version is released:)

@hjalmers thanks for the response, please create a new branch like you said https://github.com/hjalmers/angular-generic-table/issues/253#issuecomment-393270462  and i will try to help, i know you have to change a lot since now we can move everything to a library but once that step is done the rest should be easier, and also update the rxjs

Yeah first step would just be to use latest angular version and update rxjs (hopefully I'll find some time to do it this week). I just tried using the library with latest version of angular (7.0.3) and I can confirm that it works when doing:
npm install rxjs-compat tether --save

#253

repo: hjalmers/angular-generic-table


text:
🛑 HJStrauss is down

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

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in 0f6ebcd after 25 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 LM Bogen WSV is down

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

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 6f499a6 after 52 minutes.


text:
🛑 HJStrauss is down

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

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in f04c5d1 after 16 minutes.


text:
🛑 Griffo is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in b87cddf after 8 minutes.


text:
🛑 Opa Hansi is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Opa Hansi is back up in b0a9967 after 22 minutes.


text:
[Remove]: infolink.pavv.co.k is a "non-domain entry"

Domain
infolink.pavv.co.k
Why should this domain be added?
"infolink.pavv.co.k" is still in, even though you have fixed it in the now deprecated file #1
Please go over the text file to make sure not more changes were lost.
Thanks!
[i] Target: https://raw.githubusercontent.com/hkamran80/blocklists/main/smart-tv
[✓] Status: Retrieval successful
[✓] Parsed 202 exact domains and 0 ABP-style domains (ignored 1 non-domain entries)
Sample of non-domain entries:
- "infolink.pavv.co.k"
List
Smart TV
Anything else?
No response
Code of Conduct

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

That's odd. I wonder why it didn't get copied over. I'll fix that.


text:
group.play.notification plays notification sound multiple times

Description
Got the folowing function node in-line with an universal node:
msg.topic = "group.play.notification";
msg.volume = "60";
msg.payload =  "http://192.168.0.15:8123/local/media/conf.mp3";
return msg;

It should play the mp3 file, and does it too. But it plays it multiple times, mostly, the "echoes" are quiter than the first one. If the doorbell sound was played before, activated by another flow it sometimes plays the doorbell sound as "echoes"...
Very strage...
In case of a bug: Are you able to reproduce the error
yes
Versions and Infrastructure
**what system: Node Red with HASSIO
**node-red-contrib-sonos-plus version: 6.3.0
**Node-RED version: 11.1.1

Hi Alex.
The notification command is "handmade" - means not a SONOS build in function. The command needs time (several seconds) to capture the current state of the group, playing the notification and finally restoring the original state.
During this time, any additional command (change the stream, stop, pause, etc) arriving at the player "interfere" with the notification - usally problems restoring the original state and playing multiple times.
Are you sure that there are no additional messages arriving at the player during that time? How does your flow look (export)?
At my home I did solve it by putting a "queue function" in front of the sonos node - see tts example  block serialize msgs and play notifications.

My flow is as simple as that. You see the code in the function node above. There are no additional messages.

Functions are always "critical". Could you please post the content of the function or just export it?
You can put a debug node after "confirmed sound" and check, when messages are send.

You can see the content of the node in my initial post

Please replace the function node with a change node - function nodes are for real functions not just assignements.
Put a debug node behind it and verfiy that per call only one message is send to the SONOS node.
You can also put a simple queue node between the change node and the SONOS node to ensure that only one message is send.

no response - closed!

authors: Alex-joomla hklages

repo: hklages/node-red-contrib-sonos-plus


text:
Linter seems to not pick up .zip release

Hello, I tried to use your linter for my project https://github.com/eliasblume/powertoys-run-jetbrains-projects here.
I think the release is in OK format but somehow your linter doesn't pick it up, any ideas ?

when i run  ptrun-lint https://github.com/eliasblume/powertoys-run-jetbrains-projects i get
PTRUN1201: Release should be valid
 - Asset ".zip" missing

If you want to fix the regex and create a PR, you are welcome.

I changed the names, though the error remained - so idk if its a caching issue or smth

could i be that i upload the ZIPs after initial release ?

It seems like your packages has the content type binary/octet-stream:

https://api.github.com/repos/eliasblume/powertoys-run-jetbrains-projects/releases/latest

The linter are looking for something with zip, for example application/zip.
I wonder how the content_type is decided.

When I download the archive, it works fine - I suspect the action is a bit to blame.
Once I download and re-upload the ZIPs, it seems to work fine so probably I need to look into my action

(this issue truly is my messed-up plugin.json)

The hash errors are a bit of nit picking.
I put the SHA256 hashes in the release notes:

https://github.com/hlaueriksson/GEmojiSharp/releases/tag/v4.0.1

They are generated with a script:

https://github.com/hlaueriksson/GEmojiSharp/blob/master/src/GEmojiSharp.PowerToysRun/release.ps1

@hlaueriksson i finally had the time to fix it - works great now, thx for the help :)

For the next release I have a few things on my TODO list. For example:

Also look for packages with extension .zip
Lax the regex to match v prefix of version in the filename

authors: eliasblume hlaueriksson


text:
Unreadably tiny fonts on Windows 10

I've just installed doom-emacs on my Windows 10 machine, following the instructions here.  The problem is the fonts are all far too small to read.
This is on a Surface Book (high DPI screen) and with emacs 26.3, downloaded by the choco package manager.  If I run emacs without the doom configs, the fonts are reasonably sized, no matter what Windows machine and display I run it on.   So it seems that the doom configs are overriding something that works sensibly on this Windows build of emacs.

Open up ~/.doom.d/config.el in another editor and find this line:
(setq doom-font (font-spec :family "monospace" :size 14))

And either

Change :size 14 to, say, :size 24
Or delete the whole line altogether.

Does either fix your issue?

Thanks.  If I just comment out that line, fonts look normal again, so that fixes it for me.
But I'm not sure what should be done for Windows users in general.

In f47ec8b I've removed the default setq line for doom-font, so this should affect future Windows users. For now I'll consider this temporarily resolved, and hopefully revisit it in the future when I have time to look at improving Windows support in general. Thanks for bringing it to my attention!

authors: hlissner notuntoward

repo: hlissner/doom-emacs


text:
When refiling: Invalid function: org-preserve-local-variables

What did you expect to happen?
refile correctly with no error when triggerring org-refile
What actually happened?
I updated (and upgraded) doom emacs today. I encountered the same from a previous issue. I tried

doom compile :plugins
doom purge && doom compile
doom build
reinstall doom emacs by deleting ~/.emacs.d and git clone and doom install

However, the problem remains.
When I call org-refile, *Backtrace*
Debugger entered--Lisp error: (invalid-function org-preserve-local-variables)
  org-preserve-local-variables("Copied: Subtree(s) with 1190 characters")
  org-copy-subtree(1 nil t)
  org-refile(nil)
  funcall-interactively(org-refile nil)
  call-interactively(org-refile nil nil)
  command-execute(org-refile)

in *Messages*
Copied: Subtree(s) with 1190 characters
org-copy-subtree: Invalid function: org-preserve-local-variables

Steps to reproduce:
M-x org-refile
System information:

output of `M-x doom/info`:
```
emacs   version    26.3
        features   XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS GLIB NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD LCMS2
        build      May 19, 2020
        buildopts  (--prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-wide-int --with-modules 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now)
        windowsys  x
        daemonp    server-running
doom    version    2.0.9
        build      grafted, HEAD -> develop, origin/develop, origin/HEAD 96ab60d 2020-07-29 16:10:31 -0400
        dir        ~/Projects/myrepos/dotfiles/doom-emacs/.config/doom/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /bin/fish
        uname      Linux 5.4.53-1-lts #1 SMP Wed, 22 Jul 2020 20:16:09 +0000 x86_64
        path       (~/.scripts ~/go/bin ~/.local/share/cargo/bin ~/.luarocks/bin ~/.emacs.d/bin ~/.config/vifm/scripts ~/.local/bin /opt/bin /usr/local/bin /usr/bin /sbin/ /bin /usr/sbin/ /usr/bin/core_perl/ ~/.local/share/texlive/2020/bin/x86_64-linux/ /usr/lib/emacs/26.3/x86_64-pc-linux-gnu/)
config  envfile    envvar-file
        elc-files  186
        modules    (:completion company ivy :ui deft doom doom-dashboard doom-quit fill-column hl-todo modeline nav-flash neotree ophints (popup +defaults) vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold multiple-cursors snippets :emacs (dired +icons +ranger) ibuffer vc :term eshell term :checkers syntax :tools debugger (eval +overlay) gist lookup lsp magit pdf rgb tmux :lang cc data emacs-lisp (go +lsp) (haskell +dante) javascript latex lua markdown (org +roam +dragndrop +gnuplot +hugo +pandoc +present) (python +lsp) (rust +lsp) (sh +fish +lsp) web :email notmuch :app calendar :config literate (default +bindings +smartparens))
        packages   ((simplenote2) (emojify) (org-roam-server))
        unpin      (n/a)
        elpa       (simple-httpd s org-roam-server org-roam org-re-reveal org htmlize f emacsql-sqlite3 emacsql dash)
```

You have a conflict between a) the packages you have installed with package.el (e.g. M-x package-install or use-package's :ensure keyword):
        packages   ((simplenote2) (emojify) (org-roam-server))
        unpin      (n/a)
        elpa       (simple-httpd s org-roam-server org-roam org-re-reveal org htmlize f emacsql-sqlite3 emacsql dash)

Stop using package.el (remove all package-* calls in your config and :ensure t's in your use-package blocks, if any).
Run doom sync -p. -p will purge any package.el-installed packages on your system.
Restart Emacs.

You don't need to install any of the above packages yourself; they are all installed for you by the Doom modules you already have enabled.

I am also having this problem since this morning's upgrade. I have checked the above and all of my use-package calls are not using :ensure t and I don't have any package-* calls as far as I can tell. I have also run doom sync -p but the problem still persists.
Running doom doctor shows the following message: "‘org’ was already loaded by the time lang/org loaded, this may cause issues".  I'm guessing this is related?
I'm using some org-related packages in my packages.el file as follows: -
(package! ox-twbs)
(package! org-drill)

Hopefully this helps to narrow down the problem.

I'm surprised doom build didn't fix your issue, in that case do you have a link to your config?

With the exception of simplenote2 and emojify, you don't need to install any of the above packages yourself; they are all installed for you by the Doom modules you already have enabled.

This is my current package.el
(package! simplenote2)
(package! emojify)

Do you mean that I can load them using doom modules ? I thought i have to install them using package! since i didn't find related modules in the this doom-emacs repo. What's the correct way of doing this ?

Stop using package.el (remove all package-* calls in your config and :ensure t's in your use-package blocks, if any).
Run doom sync -p. -p will purge any package.el-installed packages on your system.
Restart Emacs.

What i have tried now is:

comment out org-roam-sever (that's introducing org dependency) in packages.el

;;; my current packages.el
(package! simplenote2)
(package! emojify)
;; (package! org-roam-server)

comment out org-roam-server related config in use-package block.
doom sync -p , restart emacs

However, the problem remains. (invalid-function org-preserve-local-variables)
Another question is:

how to install org-roam-server correctly if not using package! in packages.el ?

I have the same issue. Here is the relevant doom/info part:
        modules    (:completion (company +childframe) (ivy +icons) :ui deft doom doom-dashboard doom-quit hl-todo modeline ophints (popup +defaults) vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold multiple-cursors snippets :emacs (dired +icons) electric undo vc :term eshell :checkers syntax spell :tools (eval +overlay) lookup magit make pass pdf :lang coq data emacs-lisp javascript latex ledger lua markdown ocaml (org +gnuplot +roam +journal +noter) sh :email notmuch :app calendar irc (rss +org) :config literate (default +bindings +smartparens))
        packages   ((ebdb) (emojify) (org-review) (xah-replace-pairs) (org-ref) (gnuplot) (ts) (magit-todos :disable t) (elpher) (org-roam-bibtex) (leuven-theme) (unicode-fonts) (beacon) (xah-math-input))
        unpin      (n/a)
        elpa       (n/a)

Is it possible that any of you have elisp packages installed through your OS package manager? For instance, mu (for mu4e). Some OSes may be loading org long before ~/.emacs.d is sourced, meaning you are forever stuck with the old org that is built into Emacs. That was true for gentoo users for a time, it may be for other OS users. You'd have to check your site files.
In any case, the problem is that org is being loaded to early by something, and I suspect that something, if not in your config (in your init.el's in particular), then by something outside of it, which I have no control over.
I also notice that @alexlai97's config is byte-compiled. Please run doom clean, then try doom sync && doom build and see if that changes anything. It's never a good idea to debug issues while your config is byte-compiled.

Here's some more information from my perspective, hopefully this will help.
I've just tried this on my second computer and everything worked fine, and doom doctor reported no issues. I upgraded Doom (doom upgrade) with these changes: https://github.com/hlissner/doom-emacs/compare/aac73f4c01ed6515347dc6b264c20230d7e8bb71...e07cc77c19a410bc38bf9a109ad01983a123ecd2. During this upgrade process, org-mode updated from 82b496c -> a1e5bee. Following this upgrade doom doctor reports the above issue again and refiling no longer works. So something must have happened between these commits to cause this.
Henrik, to answer your previous comment directly, I have only the following Emacs-related packages installed on my system: -
emacs-bin-common/focal,now 1:26.3+1-1ubuntu2 amd64 [installed,automatic]
emacs-common-non-dfsg/focal,focal,now 1:26.3+1-1 all [installed]
emacs-common/focal,focal,now 1:26.3+1-1ubuntu2 all [installed,automatic]
emacs-el/focal,focal,now 1:26.3+1-1ubuntu2 all [installed,automatic]
emacs-gtk/focal,now 1:26.3+1-1ubuntu2 amd64 [installed]
emacs/focal,focal,now 1:26.3+1-1ubuntu2 all [installed]
emacsen-common/focal,focal,now 3.0.4 all [installed,automatic]

I have mailbox-utils installed but not the mu4e system (Ubuntu) package. I do have mu4e enabled in init.el.
The value of org-version when running Doom Emacs is "9.4" and when running emacs -Q it is "9.1.9".

I also notice that @alexlai97's config is byte-compiled. Please run doom clean, then try doom sync && doom build and see if that changes anything. It's never a good idea to debug issues while your config is byte-compiled.
No, nothing's changed.
In any case, the problem is that org is being loaded to early by something, and I suspect that something, if not in your config (in your init.el's in particular), then by something outside of it, which I have no control over.
Yeah, i think that's case as well. Need to dig into where causes org to load early when i have time.

I've been trying to figure out what's going on and I have a feeling it might be something to do with mu4e loading Org too early as you suggested. However I've removed mu4e completely from my system, from init.el, packages.el and my custom config.el. In fact I removed all custom config. I then ran doom sync -p, doom clean and doom build and I still had the same problem (and the same message from doom doctor) so I'm not sure if mu4e is actually the problem.
Nevertheless, I wanted to ask if my set-up is correct.  I'm using Ubuntu 20.04 and I have the maildir-utils system package installed as described in the mu4e module readme. If I un-comment (mu4e +gmail) in init.el I get the "No such file or directory, mu4e" error mentioned here when trying to run mu4e. The only way I have been able to get mu4e working properly is to install the mu4e system package, which installs mu4e .el files in /usr/share/emacs/site-packages/. Installing this, then running doom sync again allows mu4e to operate properly.
Is this the correct way of doing it however? I assumed that (mu4e +gmail) in init.el would install mu4e itself and the only support package required on the system would be maildir-utils which provides mu. But it seems that this is not the case and I also need to install the mu4e Ubuntu package.
Could you confirm whether I'm doing this correctly? I have a feeling this is something to do with this problem.
Thanks!

I updated doom emacs today and the issue was gone. 😇

Ah, my bad. I fixed this a short while ago, in f3740d476, and forgot to tag or mention it! If the issue resurfaces let me know.

Hi, I upgraded Doom a couple of days ago and I'm experiencing the same.

Hi, I upgraded Doom a couple of days ago and I'm experiencing the same.