NO-TICKET: Logging erroneous synchronizer starts

You can change the trace to error if you prefer.

Is it an error in the None case?

You can change the trace to error if you prefer.

Is it an error in the None case?

You can change the trace to error if you prefer.

Is it an error in the None case?

Hmm, rather unlikely. That could happen if between the moment LinearChainSync is initialized and the moment joiner reactor transitions to validator, LinearChainSync component receives a NewPeer event and then sends Start to itself…
OK, even though it sounds as an indication of some problem it's not strictly speaking an error. You're right.

You can change the trace to error if you prefer.

Is it an error in the None case?

Hmm, rather unlikely. That could happen if between the moment LinearChainSync is initialized and the moment joiner reactor transitions to validator, LinearChainSync component receives a NewPeer event and then sends Start to itself…
OK, even though it sounds as an indication of some problem it's not strictly speaking an error. You're right.


Integration into Orleans

For Backplane usage, I am considering learning both this library (simple spike worked, thanks) and using Orleans as a way to broker messages, etc. between a front-end and a cluster of MQTTnet servers.
If I go this route, would someone be willing to discuss connection lifetimes or similar?  I believe we would be able to implement this similar to how the SignalR Orleans library is implemented.
My difficulty is that without inline or other docs, I'm not sure where/how to draw parallels between SignalR and MQTTnet.  I do realize that the concept of "users"; "groups"; and "clients" is not available with MQTTnet, but I believe that outside of that restriction, there is enough similarity where this would indeed be possible.
I would suspect then that you would use sticky sessions within your nginx configuration, and subsequently have what you need end-to-end.
Feedback is welcome/encouraged on this hair-brained idea.
Thanks.

Can you discuss a little more in-depth, @JTrotta on how you've implemented?  Trying to determine if Orleans is going to be overkill for my needs or not, which is why I'm inquiring.

@dealproc, well yes of course, but I do not think this is the best place. I will try to give you some hints now, then we can discuss on the complete project I'm using.
First of all this library is a very good client, but as server side there are already many others, older, proved in production and stable app. As far as the server side of this library will not become stable and 'old', I do not suggest you to use it in a production environment (even if I did sometimes, because I like it). ActiveMQ is the best and complete AMQP server on the market, and can be used with no pain on Linux servers.
I realized a mixed architecture called ENNIO. Basically it's a cluster of CentOS servers. All servers are perfectly equals, they have the same cpu/ram/disk and the same applications, they are omomorphic  and, more over, we say that they live in a 'democratic' cluster: there is no server with more rights than others.
Each server has some (five/six) services: ActiveMQ as AMQP front-end, AKKA.net based application working as microservices ESB, NGinx and ASP.net as web server and application, Postgres sql as relational DB, and ElasticSearch as NON-Relational DB.
Each service has its own cluster architecture, and the whole cluster is arbitrated by the ESB I wrote in AKKA.net. The idea is that in a modern enviroment you need: a AMQP server (a broker) to manage the mass clients connections and messages, than those messages must be managed by an ESB (correctness, ACL, routing, etc), then you need to persist them somewhere on (today) a non relational DB. Finally you would need a CMS to manage the cluster or the application you want realiaze over the cluster.
In this way your architecture has got High Availability (HA) and is Fault Tolerant (FT).  ENNIO  (the architecture I realized and exposed) is HA because you can distribute the load over the cluster servers at EACH level (broker, web application, DB ), it's FT because if a server goes down the others can manage the load, and no data is lost (DB are syncronized inside the cluster).
The best is that you can add/remove a cluster server during the production without problems (hot switching server). I have now a production system with 5 servers in cluster, managing million of messages coming from MQTTNet clients. When the clients grow up (as everyone expects) you can add a server switching it on, it will found the cluster by it's own and will enter the cluster receiving data from DBs. When the clients decrease you can switch off a server to save energy.
That's all.
JJ

@chkr1011 Not sure how to get a dialog with you, but if you would happen to have some time, I'd like to discuss this with you and see if we can't get something going.  I believe that this would be a rather simplistic implementation once I understand the server library and where all the hook points are at.  I think, at the end, it's going to be using one of the OnClientConnected calls and capturing the connection, "subscribing to it", and letting the silo know about it.... but am unsure.

If anyone is interested... this is what I came up with... I still need to test it, etc., but it seems to work as you would expect so-far. https://github.com/dealproc/MQTTnet.Orleans

looks interesting was thinking to use orleans too but didnt have the time yet to investigate

Yea... I took inspiration from the signalr orleans backplane to bring this online.  so far, it seems to be working... need to get the docker nodes into a 'production' environment and load-test it.  what's nice with the Orleans implementation is that you don't seem to need as much plumbing as you would with other ways for things like the Online status of the device, etc.

I'm going to close this... @chkr1011 If you want to add this to a "group" where we can move the MQTTnet project into as well... let me know, as i would be willing to provide MQTTnet.Orleans into that group as well.  If others have extension/helper projects for MQTTnet, it may indeed make sense to push it all into a group/org to make it easier to discover long-term.


Adding glamour support for issue descriptions

Greetings!
charmbracelet/glamour is a go commandline markdown renderer.
This pull request shows a simple implementation of glamour into the issue_show function. If you pass the flag ´-g´ onto ´lab issue show 18´, glamour will be used to render the markdown.

This looks promising! I believe there's at least 1 issue we can link that desires something like this. If we can get the tests and ideally a screen shot up I see no reason not to bring this in as the default 💪

sure, I will take a look into this the next days!


Use HTTPS for ChartJS website links

Use HTTPS for ChartJS website links

@simonbrunel I've done that in a new PR here: https://github.com/chartjs/Chart.js/pull/5915

I only updated the docs. I didn't update this file. We should still merge this PR

Done for all URLs in b3d3df4239


remove KJAR plugin from DROOLS

we don't produce kjar anymore.

@elguardian What is the background of this issue? Kjar is still a normal use case for Drools.


Describe runtime key rotation in encryption page.

This has been added recently. Also tweaked language here and there.

This change is

Oh, also mentioned information written to the logs (also new). There will be a few more changes once another PR or two lands, but nothing major.
I threw this page together a while back. It could probably use a thorough examination and some serious polish.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3f6bd1f5c511e39be9b481fc84b00460f51f2390/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/869ab6594092e9fe4d5885e19ec220a7f25dd70e/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/500fce1470d320c4132a9f89dd2e4c91d577801f/


Fix a typo in documentation

I assume that is a typo

Hello @oh6hay,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

sure, like this?

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook


fix: path resolution

Changes

Replace the default base path with $CIRCLE_WORKING_DIRECTORY.
Manually replace the tilde ~ with the content from $HOME to avoid errors with the Vale CLI.
Add a subdirectory with files in samples to test how the glob reacts to nested files.
Include a test to check globs for named files (e.g., */test.md).
Add a test for files in the root directory.

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/vale?version=1.0.1


Can you explain the solution of round2 C?

You solution is much simpler than official solution, I want to learn but I don't understand how it works. I would be appreciated if you explain the details of the code.
Thanks in advance.

Add some comments to these codes.
Hope it is useful to you.
Thank you.


[flutter_adaptive_scaffold] Add fuchsia platform on mobile

I am writing a set of articles on the flutter adaptive scaffold package and noticed a coding error in the breakpoints file:
const Set<TargetPlatform> _desktop = <TargetPlatform>{   TargetPlatform.fuchsia,   TargetPlatform.linux,   TargetPlatform.macOS,   TargetPlatform.windows }; const Set<TargetPlatform> _mobile = <TargetPlatform>{   TargetPlatform.iOS,   TargetPlatform.android };
notice that there is no entry in mobile for fuchsia. Should there be an entry in mobile for the fuchsia platform since it runs on mobile platforms?

@fredgrott Labeling this issue as a proposal. Thanks!

Fuchsia breaks our current model since it's the only TargetPlatform that's cross-platform.
cc @gspencergoog, I think that we should remove the platform-specific logic from this package as it adds another dimension of adaptivity that will increase the complexity of this package.

Fuchsia breaks our current model since it's the only TargetPlatform that's cross-platform.

What about the web?  That's pretty cross-platform.
Aren't there small mobile (phones) and large mobile (tablets)?

What about the web? That's pretty cross-platform.

Yeah, I totally forgot about that one.

Aren't there small mobile (phones) and large mobile (tablets)?

Right. That's why I think we should remove concerns about the platform from the package.
  /// A window whose width is less than 600 dp and greater than 0 dp.
  static const Breakpoint small = WidthPlatformBreakpoint(begin: 0, end: 600);

  /// A window whose width is greater than 0 dp.
  static const Breakpoint smallAndUp = WidthPlatformBreakpoint(begin: 0);

  /// Remove this.
  static const Breakpoint smallDesktop =
      WidthPlatformBreakpoint(begin: 0, end: 600, platform: _desktop);

  /// Remove this.
  static const Breakpoint smallMobile =
      WidthPlatformBreakpoint(begin: 0, end: 600, platform: _mobile);

But might it be the case that you want things to adapt on a phone, but not adapt on a web page? I think we recently had a customer that found that the designers didn't like their adapting to the mobile size on the desktop, even though it was a better UI for the size of the window.

But might it be the case that you want things to adapt on a phone, but not adapt on a web page (or a desktop app)?

If we remove dimensions of platform adaptivity from the package, clients can still adapt to the platform.
Before (current):
SlotLayout(
  config: <Breakpoint, SlotLayoutConfig?>{
    Breakpoints.mediumMobile: SlotLayout.from(
      key: const Key('mobile'),
      builder: (_) {}
    ),
    Breakpoints.mediumDesktop: SlotLayout.from(
      key: const Key('desktop'),
      builder: (_) {}
    ),
  },
),

After removing breakpoints like Breakpoints.mediumMobile & Breakpoints.mediumDesktop in favor of no platform adaptivity.
SlotLayout(
  config: <Breakpoint, SlotLayoutConfig?>{
    Breakpoints.medium: SlotLayout.from(
      key: const Key('mobile'),
      builder: (_) {
	  	switch (TargetPlatform platform) {
			// here we are delegating platform adaptivity to the client rather than handling it in the library ourselves
        }
      }
    ),
  },
),

As for the initial question posed in this issue, I think we probably should move Fuchsia to mobile, if only to keep it consistent with the testing infrastructure: currently TargetPlatformVariant.mobile() includes Fuchsia. You can argue that Fuchsia is both desktop and mobile, or neither, so I don't think it makes a practical difference.


a few renames.

Renamed a few files
Updated the qml for the services sample

@ldanzinger Can you please review?

looks good


PR#3 minor fixups

Remove some extra spaces, fix one italics ending, and change one 'an' to 'a'.

Thanks!


Fix incorrect docker image names #1690

Both the bamboo and jenkins codequality collectors are using the docker image name "hygieia-jenkins-build-collector". This causes the real hygieia jenkins build collector docker image to get overwritten.
Resolves #1690

@tabladrum LGTM


Localize contributor cheatsheet in Hindi

What would you like to be added
Contributor cheatsheet content:
https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet
Comments
Working on PR #14001

/language hi

/kind feature
/cc @kubernetes/sig-docs-it-owners

@kubernetes/sig-docs-it-owners it is the Italian team, somehow I did not see the Hindi team.

We will form one soon!

Hey @avidLearnerInProgress,
What's the process of adding cheatsheet? I can also tag along.

Hey @avidLearnerInProgress,
What's the process of adding cheatsheet? I can also tag along.

Sure why not. Lets collaborate!

Sure, why not. I have already started localising the cheatsheet. But you can surely hop in.!

Sure, why not. I have already started localizing the cheatsheet. But you can surely hop in.!

Have you created any PR for the same?

Can you look into creating the Hindi team? Didn't find quality time to look into that aspect.

Will start work on that.

checkin?
/remove-lifecycle stale

@avidLearnerInProgress Have you opened the PR for contributor cheatsheet?

@avidLearnerInProgress Shouldn't this issue be the part of Kubernetes/community repository?

/priority backlog
/kind feature


Is free version of novoalign not adequate to NCLscan ?

Hello,
I just came about a trouble as the follows. Did the use of  free version of novoalign cause this ?
My PC environments is Ubuntu 14.04LTS. i7-6700K, 64GB RAM.
All pre-required 5 tools were installed by using Linuxbrew that is equivalent to Homebrew in OSX.
Moreover, NCLscan was run on Python 2.7.12 |Anaconda 4.2.0 (64-bit).
Sincerely,
Yaoi T
License file not found.
Licensed for evaluation, educational, and not-for-profit use only.
novoalign -r A 1 -g 99 -x 99 -d /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.JS.ndx -f /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.main.unmapped_1.fastq -o SAM
Starting at Thu Nov  3 20:17:47 2016
Interpreting input files as Sanger FASTQ.
Error: /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.JS.ndx does not appear to be a valid novoindex. Code 9
novoalign (V3.02.13 - Build Jun 29 2015 @ 12:27:18 - A short read aligner with qualities.
(C) 2008-2015 NovoCraft Technologies Sdn Bhd.
License file not found.
Licensed for evaluation, educational, and not-for-profit use only.
novoalign -r A 1 -g 99 -x 99 -d /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.JS.ndx -f /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.main.unmapped_2.fastq -o SAM
Starting at Thu Nov  3 20:17:47 2016
Interpreting input files as Sanger FASTQ.
Error: /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.JS.ndx does not appear to be a valid novoindex. Code 9
End of file reading 4 bytes
Total time cost = 0.00139594078064 sec
End of file reading 4 bytes
Total time cost = 0.00144004821777 sec

Hello,
I write another information in the below:
In NCLscan.config, I wrote the PATH to tools
bedtools_bin      = /home/tyaoi4/.linuxbrew/bin/bedtools
blat_bin          = /home/tyaoi4/.linuxbrew/bin/blat
bwa_bin           = /home/tyaoi4/.linuxbrew/bin/bwa
samtools_bin      = /home/tyaoi4/.linuxbrew/bin/samtools
novoalign_bin     = /home/tyaoi4/.linuxbrew/bin/novoalign
novoindex_bin     = /home/tyaoi4/.linuxbrew/bin/novoindex
Sincerely,
Yaoi T

Hello,
I retried to run after obtaining trial license.
However, the following error message was returned.
Error: /media/tyaoi4/SeaGate3TB/NCLscan_Results/CT11_NCLscan_Result/CT11_NCLscan.JS.ndx does not appear to be a valid novoindex. Code 9
What does " Code 9" mean ?
How can I do to resolve this problem ?
I apprecite any advice.
Thanks,
Yaoi T

Hi,
You may check the two files first,

"CT11_NCLscan.JS.fa"
"CT11_NCLscan.JS.ndx"

Do these two files have normal file size?
Thanks!

Hi,
Thanks for your quick response.
Those files have 0 kb and 18.9 kb respectively.
I don't know normal file size of them, but the size of "CT11_NCLscan.JS.fa" is probably not adequate.
Would you tell me the other check list ?
Thanks,
Yaoi T

Hi,
Please check the file size of the following files,

CT11_NCLscan.sam
CT11_NCLscan.unmapped.sam
CT11_NCLscan.rG.psl
CT11_NCLscan.chi0.bed
CT11_NCLscan.chi.bed
CT11_NCLscan.preJS.bed
CT11_NCLscan.preJS.info2
CT11_NCLscan.JS.info
CT11_NCLscan.JS.cleaned.info
CT11_NCLscan.preJS.seq
CT11_NCLscan.preJS.seq2
CT11_NCLscan.preJS.seq12

Thanks!

Hi,
Thanks for your reply.
I attach the following files:
" output_name_size_list.txt " is the list of all produced files including
each size.
" NCLscan.config " includes the actually used information. Herein, I
conducted the runs by using mouse genome data files.
Moreover, I tried a run by using the max_fragment_size = 1139 because the
maximum in the fragment size distribution is shown to be from 1125 to
1139 (count
300). The max_read_len value is default because the read length is 90.
However, I got the same results.
" Mus.genome.ref_name_size_list.txt " is the list of mouse reference genome
that includes both the downloaded  files and the files produced by the
program.
Thanks,
矢追 毅
京都府立医科大学・院・分子病態病理学
助教
京都市上京区河原町通広小路梶井町465
TEL/FAX<PHONE_NUMBER>
2016-11-14 8:07 GMT+09:00 Tai-Wei Chiang<EMAIL_ADDRESS>
Hi,
Please check the file size of the following files,

CT11_NCLscan.sam
CT11_NCLscan.unmapped.sam
CT11_NCLscan.rG.psl
CT11_NCLscan.chi0.bed
CT11_NCLscan.chi.bed
CT11_NCLscan.preJS.bed
CT11_NCLscan.preJS.info2
CT11_NCLscan.JS.info
CT11_NCLscan.JS.cleaned.info
CT11_NCLscan.preJS.seq
CT11_NCLscan.preJS.seq2
CT11_NCLscan.preJS.seq12

Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TreesLab/NCLscan/issues/9#issuecomment-260220085, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQMHiaUGlMEZZfMTw40VahdO7e1KeTXaks5q95hCgaJpZM4KpI9H
.

AllRef.fa<PHONE_NUMBER>
AllRef.fa.amb 11343
AllRef.fa.ann 11449641
AllRef.fa.bwt<PHONE_NUMBER>
AllRef.fa.pac 723714829
AllRef.fa.sa<PHONE_NUMBER>
AllRef.ndx<PHONE_NUMBER>
GRCm38.p4.genome.fa<PHONE_NUMBER>
GRCm38.p4.genome.fa.fai 3255
RepChrM.fa 33151
gencode.vM11.annotation.gtf 810222289
gencode.vM11.lncRNA_transcripts.fa 20821697
gencode.vM11.pc_transcripts.fa 143553912
CT11_NCLscan.2.chi.bed 0
CT11_NCLscan.2.info 0
CT11_NCLscan.2.info.fa 0
CT11_NCLscan.2b.info 0
CT11_NCLscan.3.info 0
CT11_NCLscan.3b.info 0
CT11_NCLscan.4.info 0
CT11_NCLscan.4b.info 0
CT11_NCLscan.JS.GRCh37.2.psl 0
CT11_NCLscan.JS.cleaned.info 0
CT11_NCLscan.JS.clear.fa 0
CT11_NCLscan.JS.fa 0
CT11_NCLscan.JS.info 0
CT11_NCLscan.JS.info_1 0
CT11_NCLscan.JS.info_2 0
CT11_NCLscan.JS.ndx 16877
CT11_NCLscan.JS.seq 0
CT11_NCLscan.JS.seq12 0
CT11_NCLscan.JS.seq_1 0
CT11_NCLscan.JS.seq_2 0
CT11_NCLscan.JS1.Idx 0
CT11_NCLscan.JS1.preIdx 0
CT11_NCLscan.JS2.Idx 0
CT11_NCLscan.JS2.cleaned.info 0
CT11_NCLscan.JS2.fa 0
CT11_NCLscan.JS2.info 0
CT11_NCLscan.JS2.info_1 0
CT11_NCLscan.JS2.info_2 0
CT11_NCLscan.JS2.ndx 16877
CT11_NCLscan.JS2.preIdx 0
CT11_NCLscan.JS2.prefa 0
CT11_NCLscan.JS2.result.info 0
CT11_NCLscan.JS2.seq 0
CT11_NCLscan.JS2.seq_1 0
CT11_NCLscan.JS2.seq_2 0
CT11_NCLscan.PreJS2.bed 0
CT11_NCLscan.PreJS2.info 0
CT11_NCLscan.PreJS2.info2 2
CT11_NCLscan.PreJS2.seq 0
CT11_NCLscan.PreJS2.seq2 2
CT11_NCLscan.chi.bed 0
CT11_NCLscan.chi0.bed 0
CT11_NCLscan.chi2.bed 0
CT11_NCLscan.chi3.bed 0
CT11_NCLscan.colinear.psl 0
CT11_NCLscan.info 0
CT11_NCLscan.linearJS 0
CT11_NCLscan.main.JS2.sam 0
CT11_NCLscan.main.JS2b.sam 0
CT11_NCLscan.main.bwa.bam 106688204
CT11_NCLscan.main.bwa.unmapped.sam 12378112
CT11_NCLscan.main.bwa.unmapped.sam.id 0
CT11_NCLscan.main.bwa.unmapped_1.fastq 0
CT11_NCLscan.main.bwa.unmapped_2.fastq 0
CT11_NCLscan.main.sam 0
CT11_NCLscan.main.um3.fa 0
CT11_NCLscan.main.unmapped.fa 0
CT11_NCLscan.main.unmapped.sam 0
CT11_NCLscan.main.unmapped.sam.id 0
CT11_NCLscan.main.unmapped_1.fastq 0
CT11_NCLscan.main.unmapped_2.fastq 0
CT11_NCLscan.main_1.JS.sam 0
CT11_NCLscan.main_1.um3.fastq 0
CT11_NCLscan.main_2.JS.sam 0
CT11_NCLscan.main_2.um3.fastq 0
CT11_NCLscan.ncl.sam 0
CT11_NCLscan.preJS.bed 0
CT11_NCLscan.preJS.info 0
CT11_NCLscan.preJS.info2 2
CT11_NCLscan.preJS.seq 0
CT11_NCLscan.preJS.seq2 2
CT11_NCLscan.preResult 0
CT11_NCLscan.rG.non_un.psl 0
CT11_NCLscan.result.info 0
CT11_NCLscan.result.sam 0
CT11_NCLscan.result.tmp 0
CT11_NCLscan.tmp.info 0
CT11_NCLscan.tmp2.info 0
CT11_NCLscan.un.psl 0
CT11_NCLscan.unmapped.2.fa 0
CT11_NCLscan.unmapped.fa 0
all.CT11_NCLscan.1.result 0
all.CT11_NCLscan.1.sam 0
all.CT11_NCLscan.1b.result 0
all.CT11_NCLscan.1b.sam 0
all.CT11_NCLscan.JS.Parsered.sam 0
all.CT11_NCLscan.JS.sam 0
all.CT11_NCLscan.JS2.sam 0
all.CT11_NCLscan.JS2b.sam 0
all.CT11_NCLscan.b.result 0
all.CT11_NCLscan.result 0
all.CT11_NCLscan.um3.colinear.psl 0
all.CT11_NCLscan.um3.fa 0
temp.list 0
tmp.info 0

Hi,
It seems that there are no "unmapped reads" in the your input dataset.
You may check these two files first:

"CT11_NCLscan.main.bwa.bam"
"CT11_NCLscan.main.bwa.unmapped.sam"

"CT11_NCLscan.main.bwa.bam" was the alignment result mapped by bwa, and "CT11_NCLscan.main.bwa.unmapped.sam" was the unmapped part filtered by samtools.

Hi, Tai-Wei
Thank you for reply.
CT11_NCLscan.main.bwa.bam 106688204
CT11_NCLscan.main.bwa.unmapped.sam 12378112
I am sorry to trouble you, but thank you for your continuous support.
Yaoi T

I'm mean ...
Are there some "unmapped-reads-removing" pre-processes on your input dataset?
because it looks like that there are no unmapped reads in the dataset.
NCLscan needs the unmapped reads to find the NCL candidates.
Thanks!


Semaphore is shared between Jobs when using a Pipeline library.

As the title says:
Using a semaphore is a pipeline libary that is imported in multiple projects is shared between jobs.
Is this intended ?
How can I prevent this ?

Do we have any update in this topic? We are heavily using shared pipelines and this causes deadlocks in our jobs.

I've the same Problem. With this restriction isn't usable in a multibranch pipeline. I think this is because the pipeline is always executed on the master.

Which is fine if the job name and build number is part of the "key".
Am Fr., 16. Okt. 2020 um 20:41 Uhr schrieb Michael Förderer <
<EMAIL_ADDRESS>
I've the same Problem. With this restriction isn't usable in a multibranch
pipeline. I think this is because the pipeline is always executed on the
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/concurrent-step-plugin/issues/13#issuecomment-710402779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMXU3IXGV54WAPYE3ZKZIDSLCHWHANCNFSM4RB2WEJQ
.

@Xyaren But there is no key option.

@Xyaren But there is no key option.

I've searched arround and didn't a semaphore implementation with named semaphores. I think the only solution for this is to implement a own semaphore with synchronized functions doing spinlock with a sleep or using a BlockingQueue.

I've been impacted by the same thing. I never had any issues using the plugin until I began using it in another job's pipeline code.

Have you found any jenkins/groovy friendly solutions @Spacetown ?

@touting15 No.

Has there been any solution or workaround yet? We would really like to use this feature in a multibranch pipeline.

Has there been any solution or workaround yet? We would really like to use this feature in a multibranch pipeline.

Not from my side.


Make CommandSyntaxException a ComponentMessageThrowable

I explored using a Mixin plugin to only load the Mixin in loader 0.14+, but couldn't think of a good way to detect the loader version, so for now this just requires loader 0.14+, which isn't ideal.
I also tested adding CommandSyntaxException to hackilyLoadForMixin, which caused loader constraint violation errors on loader pre-0.14.

Maybe try com.mojang.brigadier.Message for older Loader versions?: https://gitlab.com/stellardrift/colonel/-/blob/dev/src/main/java/ca/stellardrift/colonel/impl/BrigadierMixinEntry.java#L27

That works, updated

Since we can't do interface injection on library classes (sigh), could you add a static method to FabricAudiences' along the lines of FabricAudiences.asComponentThrowable(CommandSyntaxException)` to make this more discoverable?


ImportError: DLL load failed: The specified module could not be found

I have 64-bit Python 3.7.2 from python.org installed on Windows 10 Professional 64-bit. PIP upgraded to the latest version, Both (32 and 64-bit)  VS2015 C++ Redistributable exists. After PIP install opencv-contrib-python  i've got folder and files for opencv <IP_ADDRESS> in my Python directory on disk. Seems everything is fine. But import cv2 command doesn't work. I have error: ImportError: DLL load failed: The specified module could not be found.

Check the missing dependency with https://github.com/lucasg/Dependencies

Seems there are three missing dependences.

I'm pretty sure there's some Windows package missing (hard to say if those dependencies are false positives or not).

Check that you do not have any conflicting cv2 installation anywhere: create a new fresh virtualenv and install opencv-python there - does the import work?
If the above does not help, try to install latest redistributables again: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Also have a look at this (probably does not help as you are not using Windows Server version): https://github.com/skvark/opencv-python/pull/170/files
Check also this: https://github.com/skvark/opencv-python/issues/154#issuecomment-444374364

Closing for inactivity.


doesn't work for some images?

In looking to merge https://github.com/IIIF/awesome-iiif/pull/108 I tried out one of my images. Any idea why this example doesn't work?
https://jbhoward-dublin.github.io/IIIF-imageManipulation/index.html?imageID=https://iiif.lib.ncsu.edu/iiif/segPap_002

I know this is an old issue, but just poking around it looks like the demo page has an issue with the @context property.  It is expecting a string (in order to run a match) and the resource you give it has a list as its value for the @context
"@context": [ "http://iiif.io/api/image/2/context.json", { "ronallo": "http://ronallo.com/ns/", "gravityBangs": { "@id": "ronallo:gravityBangsFeature", "@type": "iiif:Feature" } } ]
This is my best guess for the problem.


Fix: Export createWorkerBox function separately in addition to default export

I exported the createWorkerBox in the TypeScript typings but forgot to export it in the JavaScript file. This is a fix for that.

Just a sec, I'll fix conflicts.

Now it's fine :)

Awesome, thanks @raimohanska


Proposal: can we transfer snabbdom to Cycle.js org?

Hi @paldepind and contributors,
As many of you know, we (= @TylorS and I) use and depend heavily on snabbdom in http://cycle.js.org. It's a very handy virtual DOM library that keeps to its promise of being: damn fast, small, with a functional API and decent hook system. Previously, we were using virtual-dom, which was also good, but not as fast, not as small, not so functional API.
However, one of the main reasons why we migrated from virtual-dom to snabbdom is that that library was largely unmaintained. The core authors didn't have time to merge PRs, manage issues, make new developments. It was rotting, and it was sad. Snabbdom seemed more maintained at that time.
This time, unfortunately, we feel that Snabbdom is rather unmaintained too. Or at least we feel like we could move much faster if Snabbdom as a repository would receive faster issue management and PR merging and authoring, etc. For instance, Tylor forked snabbdom to write https://github.com/TylorS/snabbdom-ts and then again to write https://github.com/TylorS/flow-dom.
So, here's a proposition: to transfer this snabbdom repo over to the cyclejs org. And to calm the nerves, here are the terms:

Tylor and I would actively maintain it (meaning: handling issues, PRs, basic janitoring)
Paldepind would still be the contributor, would still have all the same access rights
Tylor and I would proceed to make https://github.com/paldepind/snabbdom/issues/150 happen
Tylor and I would experiment with immutable APIs for snabbdom, like https://github.com/TylorS/flow-dom
None of the above must drastically affect snabbdom performance or size (unless it's an improvement)

I can totally understand if you don't want to do this. In that case, we would fork snabbdom and make a virtual DOM library mostly compatible with snabbdom, but with the changes mentioned above. That would be ok, but it would be, well... a fork. And if the community can avoid a fork, that's better so there's less confusion, and less scattering of open source workforce.
What do you think?

Hi, @staltz !
Maybe good idea is to add you and Tylor to maintainers of this repo?

Whatever @paldepind decision ends up being, you (contributors) can count on the helper package snabbdom-to-html to be there as well. Whatever helps the community best.
: )

I can certainly see where you are coming from. When building a framework such as Cycle it is of course very important that the packages you depend on are reliable so that you're never stuck because a third party dependency isn't moving along fast enough. And while I wouldn't call Snabbdom unmaintaned I am certainly handling the maintenance at a very slow pace. I think that you and @TylorS offering to help maintain Snabbdom is great news for Snabbdom. I hold both of you in high regard and am certain that your contributions would be beneficial to Snabbdom and it's overall health.
I am happy that Snabbdom is useful to Cycle. I think Cycle is a great framework. When I created Snabbdom my hopes where excactly that people would find it useful for building their own things on top. And several people has done so which is nice. It is important to me that Snabbdom can continue to serve people in this respect. I.e. not only serve Cycle but other users as well. I feel that moving Snabbdom to the Cycle organization might end up implying to some people that Snabbdom is a virtual DOM library just for Cycle. And not an independent virtual DOM library for everyone, whatever you might want to do.
Thus instead of moving Snabbdom to the Cycle org I think it might be a better idea to set up a GitHub organization specifically for Snabbdom. If the respective authors are interested they'd be invited to move their Snabbdom related packages to this organization. For instance @acstll's snabbdom-to-html, snabbdom-jsx, snabbdom-helpers, babel-snabbdom-jsx, and the other Snabbdom related projects. I, @staltz, @TylorS and the interested related packages owners would be part of this organization and maintain Snabbdom together.
I feel like this would be a great move both for Cycle who can be certain that Snabbdom is timely maintained and for the rest of the Snabbdom users who would still be certain that Snabbdom remains a general purpose virtual DOM library. Additionally it would help me fell less guilty for not dedicating enough time to maintaince :sweat_smile:
Something completely different: This is the first time I've heard about flow-dom. Is there somewhere where I can read more about it?

While I think moving Snabbdom to the Cycle.js org would be great, I like @paldepind idea better. In the end we want things to move forward. I'll be happy to have my package join a Snabbdom org and make it better with your help.

i can't wait the #150 happen. I check @TylorS repo, and i think it should merge here somehow (maybe just create a branch for it).

@paldepind I think that's a wonderful idea.
Regarding flow-dom it was an experiment to see if the mutation used heavily in snabbdom could be avoided by using recursion instead of while loops and by having hooks/modules return a new VNode instead of mutating the current. It works to some extent, but it definitely has issues at present. I'm also rather certain than if and when fixed, it'd be rather slow because there are so many extra object being created. If you're interested, I'd be happy to talk about it

Thus instead of moving Snabbdom to the Cycle org I think it might be a better idea to set up a GitHub organization specifically for Snabbdom.

Sure. It didn't even cross my mind that it was an option, but now it seems even more reasonable than moving to Cycle.js org.
Let's do it?

I've created the organization and sent out invitations 😄

I'm glad to move https://github.com/bloodyKnuckles/snabbdom-template to the snabbdom org. May I have an invite?

Issue seems done. I'll start contributing and putting things in shape probably in October when I get some time.

@bloodyKnuckles Indeed you may :smile:

@paldepind another small but essential request: @TylorS and I need write access to this repo in order to merge pull requests and whatnot. :)
And in npm, we could be added as contributors: cycle and tylors.
When it comes to making decisions and consensus, we could setup https://lgtm.co/ on this repo so that at least 2 people need to give a thumbs up to a PR before it can be merged.

Yes. Of course. I've added both of you :)
https://lgtm.co/ looks cool. I've never heard of it. I'm not sure if setting it up is worth it though.

Thanks! Soon contributing

On another matter, I got some ideas for a logo for snabbdom, but I need to work on them before sharing anything. Is that something you'd be interested in @paldepind ?

@acstll I've actually given a logo some thought but without coming up with any good ideas. If you have the good ideas I think that would be totally awesome!

Alright! I'm gonna give it a try then. 😃

I'm looking forward to seeing that. Feel free to open an issue related to the logo :smile:

Hello! Something else that was done on top of snabbdom:  https://github.com/AlexGalays/kaiju

Nice. I've sent you an invite @AlexGalays :smile: Please open issues about those issues. I see your point with regards to the create hook.


initialize Repository has no response (I can't press the initialize repository vs code button)

Issue Type: Bug
I can't press the initialize repository vs code button...
VS Code version: Code 1.68.0 (4af164ea3a06f701fe3e89a2bcbb421d2026b68f, 2022-06-08T11:44:16.822Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 7 5800H with Radeon Graphics          (16 x 3194)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (7.61GB free)

Process Argv
--enable-proposed-api TabNine.tabnine-vscode --crash-reporter-id 88ac5f48-0bab-4fe1-a667-41cabd59760e

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

dart-code
Dar
3.42.1

flutter
Dar
3.42.0

material-icon-theme
PKi
4.18.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

https://user-images.githubusercontent.com/103085770/173528635-c7839fa2-e7b0-4d21-8157-1b2776ab09b1.mp4
initialize Repository has no response

@VSCodeTriageBot

@Vram-AH, apologies for not getting back to you on this until now.  Could you please use the following wiki page to set the log level to trace. After that reload the folder/workspace and share the contents of the git output channel. Thank you very much!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Detections are stucking on rviz

Thank you for open source this great framework.
I am running the package in the docker environment. My computer is an Intel® Core™ i9-10900X CPU @ 3.70GHz × 20I, with a NVIDIA Corporation TU102 [GeForce RTX 2080 Ti], and 128.0 GiB of RAM.
I have downloaded hauptgebaeude_sequence_1 in DOASL for testing. The simulations on Rviz are slow and stuck.
https://github.com/ethz-asl/dynablox/assets/12784079/5acfc79d-e3ef-46fe-8f1f-0f90c9b18e8f
I would be grateful for any help!

Hi @lidiaxp
Have you tried running without RVIZ (and e.g. print the frame rate)? Your machine should definitively be able to run Dynablox at a high rate, sometimes RVIZ itself is not very quick (e.g. if there's some graphics drivers issues in some cases).

Hello @Schmluk, I've just tested it. Even when I don't open RVIZ, the frame rate remains at 0.16 Hz.
I've also examined the point cloud frame rate, and it fluctuates between 8 and 14 Hz. So, I'm not sure why Dynablox is experiencing performance issues.

I think maybe it's similar what I met before: https://github.com/ethz-asl/dynablox/issues/7#issuecomment-1535796272
Try to make it with Release Type:
catkin config --cmake-args -DCMAKE_BUILD_TYPE=Release

It worked, thank you very much. Do you know why do we need it?

Great, it helps you!
Mainly because of the cmake type, release will have o2 optimization.

Oh, I got it, I haven't known it was possible to change this in ROS. I am going to read more about it. Thank you very much for your help.


Migrate to Tan Stack table - Custom Data Table

Proud to announce the new and improved Data Table for global usage within DiSSCover.
The new data table component is built by using the Tan Stack table library, which is a headless library.
Headless means that it does not provide a full component to be used, but rather an API that can be requested and used for passing functionality onto a plain HTML table.
The custom Data Table component has several options built in at the moment:

Functionality for filtering per column
Sticky header when scrolling down
Row selection
Pinned columns
Dynamic width of table columns based upon REM value

The columns and data to pass to the data table should be defined loosely from the component itself.
That is why table configuration files have been introduced to take care of the column configuration.
Most of this code is repeatable and takes a lot of space, these files should help prevent code from becoming messier.
New features to the Data Table component may be introduced in the future by demand.

⚡ Ok, I don't know if I get it all but didn't see anything strange. Looking forward to seeing it in action

I can maybe explain it on Thursday, when you see the logic, it is pretty straightforward!


KeyError when trying to lookup up timezone with reverse_timezone

I'm getting the following error when running the following code (with the correct usernames):
import json
from geopy.geocoders import Nominatim, GeoNames

lat = 40.6997716
lon = -73.9753359

geolocator = Nominatim(user_agent="test")
tz_lookup = GeoNames(user_agent="test", username="test")
tz = tz_lookup.reverse_timezone((lat, lon))
print tz

Traceback (most recent call last):
  File "set_timezone.py", line 9, in <module>
    tz = tz_lookup.reverse_timezone((lat, lon))
  File "/usr/local/lib/python2.7/dist-packages/geopy/geocoders/geonames.py", line 301, in reverse_timezone
    return self._parse_json_timezone(response)
  File "/usr/local/lib/python2.7/dist-packages/geopy/geocoders/geonames.py", line 304, in _parse_json_timezone
    return from_timezone_name(response["timezoneId"], raw=response)
KeyError: 'timezoneId'

Apparently the issue you're experiencing is due to the username not being accepted by GeoNames:
$ http 'http://api.geonames.org/timezoneJSON?lat=40.75376406311989&lng=-73.98489005863667&username=test'
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: no-cache
Connection: Keep-Alive
Content-Length: 117
Content-Type: application/json;charset=UTF-8
Date: Wed, 12 Dec 2018 20:17:05 GMT
Keep-Alive: timeout=5, max=100
Server: Apache/2.4.6 (CentOS) mod_jk/1.2.41 OpenSSL/1.0.1e-fips

{
    "status": {
        "message": "user account has not been confirmed. Check your email for the confirmation email.",
        "value": 10
    }
}

The error should be gone if you'd use a username which GeoNames considers valid. The same request with a correct username seems to work for me.
Although I'd still call it a bug in geopy, because it should've been a clearer GeocoderAuthenticationFailure exception instead of an obscure KeyError, so thanks for reporting!

Another issue I discovered during investigation is that the case of non-existing timezones is not handled properly by geopy. For example, at lat=79&lng=80 GeoNames does return GMT/DST offsets, but doesn't return a timezone name (in the Olson DB format). A similar problem applies to GoogleV3 as well.
I started working on the fix, hopefully it'll be done by this weekend.

@KostyaEsmukov Interesting! I have already clicked through the email and confirmed my account name. Is there another account I have to make in addition to the one with GeoNames? I've double-checked and I'm using my correct username that has an existing GeoNames account.
Is it necessary to include the user_agent?
Thanks for looking into this.

Is there another account I have to make in addition to the one with GeoNames?

I don't remember the exact steps.
You may try to perform an http query manually and see what would GeoNames tell you there. The query I posted before might be used for that (just put your username value in place of test. The http command is https://httpie.org/, but if you don't have or want it, curl might be used instead. Something like this:
$ curl 'http://api.geonames.org/timezoneJSON?lat=40.75376406311989&lng=-73.98489005863667&username=YOUR_ACTUAL_USERNAME'

Is it necessary to include the user_agent?

No, AFAICT GeoNames doesn't require custom user agent value (like Nominatim does). A username should be enough.

Fixed via #339.
Now the same code snippet would raise the following instead of a KeyError:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kostya/Code/_contrib/geopy/geopy/geocoders/geonames.py", line 311, in reverse_timezone
    self._call_geocoder(url, timeout=timeout)
  File "/Users/kostya/Code/_contrib/geopy/geopy/geocoders/geonames.py", line 329, in _parse_json_timezone
    self._raise_for_error(response)
  File "/Users/kostya/Code/_contrib/geopy/geopy/geocoders/geonames.py", line 323, in _raise_for_error
    raise GeocoderAuthenticationFailure(message)
geopy.exc.GeocoderAuthenticationFailure: user account has not been confirmed. Check your email for the confirmation email.

This will be released as 1.18.1 on PyPi today.


Adds docstring to the python package

@davidbrochart, feel free to modify it since you wrote that code.

Thanks for the review @davidbrochart!
I pushed a commit with the changes, could you take a look at the signatures carefully? I tried to type them all following your comments.


Link to ZAP HUD group

From tutorial and a new desktop Online menu item

We already refer to the std ZAP User Group as such, so I was concerned there would be confusion there. I was also thinking this would be both for HUD users and developers, as I'm hoping we can make it sufficiently easy to tweak the HUD for there to be more overlap between the 2 than we see with ZAP...

Just added an update to the changelog.


buid(deps): bump Yarn from 3.5.0 to 3.6.0

Changelog: https://github.com/yarnpkg/berry/compare/<EMAIL_ADDRESS>

We'll need to hold off merging this for a bit more, but going to approve so we know that it's good to go once we're ready

Please note that 3.6.0 is out and I just updated this pull request


Autocomplete: Fix Closing For Touch Devices (Server Side)

Description
Fixes #3958.
Same with select, autocomplete didn't close in Server Side when touch an item.
Not the best solution, but at least solves most of async situations and can use as a workaround safely.
Also added LockScroll parameter the same as Select.
How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

https://user-images.githubusercontent.com/78308169/160583865-09299653-54ab-4697-98f7-f74f0045db6b.mp4
Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

@henon this test first failed for me, i changed it a bit, then is passed, but look fail here again.

The fix works locally but doesn't work when deployed.

The fix works locally but doesn't work when deployed.

How do you test it?

How do you test it?

I deployed it to a vps and it didn't close the popup. I added a bigger delay 500 instead of 1 and it works remotely.

How do you test it?

I deployed it to a vps and it didn't close the popup. I added a bigger delay 500 instead of 1 and it works remotely. This needs a more proper fix 🤔

I agree, but i think if it works with 10-50 delay, its worth to add it temporarily, the bug has been standing for a long time.

@bugproof what about #4326?

what about #4326?

Works fine. Nice work.

what about #4326?

Works fine. Nice work.

@henon we approved from this side

Maybe change form 1ms to 50ms to be sure. 1ms is too dangerous not to work especially when not local

Oh, sorry, this PR is closed.


Add user URL to context

Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context

Easier than I thought so I knocked it out before heading out to hang on my porch.
NOTE: It is only for User results records and if I don't find one on the user, I give it a blank string.

Note: Also - it want appear until totals are recalculated for a challenge - either from activity (any activity) or force recall from admin page


ESC/POS Printing over network

Dear bebo925,
is it possible to print ESC/POS over the network, changing this.printService.setDriver(this.webPrintDriver, 'WebPRNT'); to this.printService.setDriver(this.webPrintDriver, 'ESC/POS'); does not work.

@CasualGermans  Are you getting any errors or is it printing gibberish?


Particles don't work in Godot 4.0, really want to test them . .

Godot version:
Godot 4.0 hash a474926ac
OS/device including version:
Windows 10 PC . .
Issue description:
This might not be a bug, but the particlesystem doesn't work . . It's disabled . .

The particle system is getting updated, it might be why, I simply don't know . . No matter what, Godot 4.0 is already a beast, a real pro looking engine, it looks like Unreal engine and, better than Unity . .
Steps to reproduce:
Added a particle system, and it didn't work, sry . .
Minimal reproduction project:
REALLY want to test some particles, hope you add it soon, I know you work super-hard, cool stuff, CAN'T wait, for Godot 4 <3 . . Thx . . . Also, changing name from Particles, to GPUParticles helps me a lot, as it was confusing before, thank you . . .

Particles haven't been implemented yet in the Vulkan renderer: https://github.com/godotengine/godot/issues/35353


Notification Banners - UI - Pages, Dashboards, and Forms 2/3

As a Ministry user, I need to be able to publish banners on the various SIMS sites for different users, to notify about system changes or outages.
Acceptance Criteria
Create Page

[ ] Create Notification Banner form has 6 fields:

Name (required, not unique, 100 chars)
Portal (minimum one required, can select all)
Start Date (required, enforce today's date or future date)
Message (required, max 250 chars) Please include simple formatting options like bold/italics and hyperlinks. (not shown in mock-up, please add/enable)._

[ ] 5 different portals that banners can be shown in:

authenticated institution portal - "Institution"
unauthenticated institution portal - "Institution (Login Page)"
authenticated ministry portal - "Ministry"
authenticated student portal - "Student"
unauthenticated student portal - "Student (Login Page)"
unauthenticated supporting user portal - "Supporting User (Login Page)"

[ ] notification banner statuses:

Active (start date today or in the past)
Scheduled (future start date)
Inactive (has been deactivated)

Business Context
Fig 1:

" alt="image.png" />

duplicate


ETH: fix getTransactions filtering boundaries

fixed getTransactions method
bumped v0.21.2

works well with local yarn link for ASGDX project
https://user-images.githubusercontent.com/67793194/120477149-1d6acc00-c3b4-11eb-9afe-9cd1a571113a.mov
closes #343

This PR is related to https://github.com/thorchain/asgardex-electron/issues/1487


NewServerConfiguration() called twice after config reload with -watch causing e.g. double health probes/jobs

With -watch, after a config reload,

the probe is shut down later than the server, and
I get two health probes.

Example:
server {
  hosts = ["*:8080"]
  endpoint "/" {
    proxy {
      backend = "be"
    }
  }
}

definitions {
  backend "be" {
    origin = "https://blackhole.webpagetest.org"
    beta_health {
      interval = "10s"
      timeout = "3s"
    }
  }
}

Start Couper
INFO[0000] watching configuration file(s)                build=dev type=couper_daemon version=0 watch="map[max-retries:5 retry-delay:500ms]"
INFO[0000] ulimit: max open files: 1048576 (hard limit: 1048576)  build=dev type=couper_daemon version=0
INFO[0000] couper is serving: <IP_ADDRESS>:8080               build=dev type=couper_daemon version=0

Normal health check:
ERRO[0000] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:20.997 total:3000.255]" type=couper_backend uid=cfcjk5beg9scfeq3hfig url="https://blackhole.webpagetest.org" version=0
WARN[0003] new health state: failing                     backend=be build=dev type=couper_daemon uid=cfcjk5beg9scfeq3hfig url="https://blackhole.webpagetest.org" version=0

Reload config:
INFO[0008] reloading couper configuration                build=dev type=couper_daemon version=0
INFO[0008] ulimit: max open files: 1048576 (hard limit: 1048576)  build=dev type=couper_daemon version=0
ERRO[0008] retry 1/5 due to listen error: listen tcp4 :8080: bind: address already in use  build=dev type=couper_daemon version=0
WARN[0008] shutting down                                 build=dev deadline=0s delay=0s type=couper_daemon version=0
INFO[0008] http: Server closed: <IP_ADDRESS>:8080             build=dev type=couper_daemon version=0
INFO[0008] ulimit: max open files: 1048576 (hard limit: 1048576)  build=dev type=couper_daemon version=0
INFO[0008] couper is serving: <IP_ADDRESS>:8080               build=dev type=couper_daemon version=0

Double health check log:
ERRO[0008] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:24.815 total:3000.822]" type=couper_backend uid=cfcjk7beg9scfeq3hfj0 url="https://blackhole.webpagetest.org" version=0
WARN[0011] new health state: failing                     backend=be build=dev type=couper_daemon uid=cfcjk7beg9scfeq3hfj0 url="https://blackhole.webpagetest.org" version=0
ERRO[0008] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:20.787 total:3000.621]" type=couper_backend uid=cfcjk7beg9scfeq3hfjg url="https://blackhole.webpagetest.org" version=0
WARN[0011] new health state: failing                     backend=be build=dev type=couper_daemon uid=cfcjk7beg9scfeq3hfjg url="https://blackhole.webpagetest.org" version=0

Health probe shutdown log:
WARN[0013] shutdown health probe                         backend=be build=dev type=couper_daemon url="https://blackhole.webpagetest.org" version=0

Still double health check logs:
ERRO[0021] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:20.353 total:3000.917]" type=couper_backend uid=cfcjkajeg9scfeq3hfk0 url="https://blackhole.webpagetest.org" version=0
ERRO[0024] backend error: backend error: connecting to be 'blackhole.webpagetest.org' failed: i/o timeout: new health state: unhealthy  backend=be build=dev error_type=backend_unhealthy type=couper_daemon uid=cfcjkajeg9scfeq3hfk0 url="https://blackhole.webpagetest.org" version=0
ERRO[0021] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:23.634 total:3000.681]" type=couper_backend uid=cfcjkajeg9scfeq3hfkg url="https://blackhole.webpagetest.org" version=0
ERRO[0024] backend error: backend error: connecting to be 'blackhole.webpagetest.org' failed: i/o timeout: new health state: unhealthy  backend=be build=dev error_type=backend_unhealthy type=couper_daemon uid=cfcjkajeg9scfeq3hfkg url="https://blackhole.webpagetest.org" version=0

ERRO[0034] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:27.049 total:3000.152]" type=couper_backend uid=cfcjkdreg9scfeq3hfl0 url="https://blackhole.webpagetest.org" version=0
ERRO[0034] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:21.148 total:3000.795]" type=couper_backend uid=cfcjkdreg9scfeq3hflg url="https://blackhole.webpagetest.org" version=0

ERRO[0047] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:20.394 total:3000.424]" type=couper_backend uid=cfcjkh3eg9scfeq3hfm0 url="https://blackhole.webpagetest.org" version=0
ERRO[0047] backend error: context deadline exceeded      backend=be build=dev custom="map[]" error_type=backend method=GET request="map[headers:map[user-agent:Couper / 0 health-check] host:blackhole.webpagetest.org method:GET name:health-check origin:blackhole.webpagetest.org path: proto:https]" status=0 timings="map[dns:21.6 total:3000.629]" type=couper_backend uid=cfcjkh3eg9scfeq3hfmg url="https://blackhole.webpagetest.org" version=0

go p.probe(opts.Context) is called in transport.NewProbe()
transport.NewProbe() is called in transport.NewBackend()
transport.NewBackend() is called in runtime.newBackend()
runtime.newBackend() is called in runtime.NewBackend()
runtime.NewBackend() is called for conf.Definitions.Backend in runtime.NewServerConfiguration()
runtime.NewServerConfiguration() is called in both Run.Execute() and for a reload in realmain()
Run.Execute() is also called for a reload in realmain()

So we have
func realmain(ctx context.Context, arguments []string) int {
...
		case _, more := <-reloadCh:
...
			_, reloadErr = runtime.NewServerConfiguration(cf, logger.WithFields(fields), tmpMemStore)
...
			execCmd, restartSignal = newRestartableCommand(ctx, cmd) // replace previous pair
			go func() {
				// logger settings update gets ignored at this point
				// have to be locked for an update, skip this feature for now
				errCh <- execCmd.Execute(args, confFile, logger)
			}()

with
func (r *Run) Execute(args Args, config *config.Couper, logEntry *logrus.Entry) error {
...
	srvConf, err := runtime.NewServerConfiguration(config, logEntry, memStore)

Jobs are started twice after reload, too.

We have a context key called request.ConfigDryRun which should prevent go-routines gets fired on object creation.
We should add this condition to all related objects like jobs or maybe jwks_url configuration_url (oidc) too.
Same pattern as in probe.go:100

The ConfigDryRun already seems to be working.
The NewServerConfiguration() called directly from realmain() has ConfigDryRun set in its context preventing the probe from running.
But there are 2 calls to execCmd.Execute() following a reload.
The first is the already mentioned:
	reloadCh := watchConfigFiles(confFile.Files, logger, flags.FileWatchRetries, flags.FileWatchRetryDelay)
	for {
		select {
...
		case _, more := <-reloadCh:
...
			restartSignal <- struct{}{}                              // shutdown running couper
			<-errCh                                                  // drain current error due to cancel and ensure closed ports
			execCmd, restartSignal = newRestartableCommand(ctx, cmd) // replace previous pair
			go func() {
				// logger settings update gets ignored at this point
				// have to be locked for an update, skip this feature for now
				errCh <- execCmd.Execute(args, confFile, logger)
				         ^^^^^^^^^^^^^^^
			}()

The other is caused in response to an error.
(see the error in the log)
ERRO[0008] retry 1/5 due to listen error: listen tcp4 :8080: bind: address already in use  build=dev type=couper_daemon version=0

		case err = <-errCh:
			if err != nil {
				if netErr, ok := err.(*net.OpError); ok {
					if netErr.Op == "listen" && errRetries < flags.FileWatchRetries {
						errRetries++
						logger.Errorf("retry %d/%d due to listen error: %v", errRetries, flags.FileWatchRetries, netErr)

						// configuration load succeeded at this point, just restart the command
						execCmd, restartSignal = newRestartableCommand(ctx, cmd) // replace previous pair
						time.Sleep(flags.FileWatchRetryDelay)

						go func() {
							errCh <- execCmd.Execute(args, confFile, logger)
							         ^^^^^^^^^^^^^^^
						}()
						continue
...

I guess, the first of the two mentioned calls to execCmd.Execute() comes too early. If I add
				time.Sleep(flags.FileWatchRetryDelay)

(or similar) ahead of the call, there's no retry error and so only one probe running after a reload.

However, even if the retry is triggered differently, there should only be one probe.


Spanish locale

I'm not sure why this was missing while the key was translated in other locales, but here it is :)

Already covered by #13, thanks. I'm going to merge that PR because it also solve other issues.

Sorry I didn't check before submitting! Thanks for the merge anyway :)


Partial-eval-optimize authz introspection

Description
Paying more on policy updates, but having faster query responses, similar to what we do with IsAuthorized, could help UI performance a lot.

For completeness' sake, other things that'll likely improve authz introspection performance:

Generating all the mappings and inverse mappings between HTTP method+verb pairs and IAM resource+action pairs once and relying on that for processing.
Baking those mappings  into OPA's store.

Currently, these are calculated (twice, IAM v1 and v2, I believe) at run time in automate-gateway for each and every request, and sent down the request path to authz-service (and thus OPA).

this work has been deprioritized, so closing.


[Feature Request]:  Adding animation

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Your landing page already looks fantastic, but incorporating a 3d image with animation could make it even more captivating. With my experience in this area, I'm eager to contribute to this enhancement.
If you could assign me this task under GSSOC24, I would be thrilled to work on it.
Use Case
This upgrade in your page will make your website look more appealing
Benefits
No response
Add ScreenShots

ON THIS PAGE I WANT TO ADD THIS

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

Ok this can be done make something slick and add. Also look for some matching background

Yess on it

@harshmishra19 updates?

Working on that logo

@ashutosh-rath02
Do you like it

Hello @harshmishra19! Your issue #190 has been closed. Thank you for your contribution!


Antlr 4.10.1 -> 4.13.0

Thank you for submitting this pull request
NOTE!: Double check the target branch for this PR.
The default is main so it will target Drools 8 / Kogito.
If this PR is not strictly related to drools and kogito project in drools.git, it should probably target 7.xas a branch
Ports If a forward-port or a backport is needed, paste the forward port PR here
link
JIRA: (please edit the JIRA link if it exists)
link
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

paste the link(s) from GitHub here
link 2
link 3 etc.

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests

for a full downstream build

for jenkins job: please add comment: Jenkins run fdb
for github actions job: add the label run_fdb

a compile downstream build please  add comment: Jenkins run cdb

an upstream build please add comment: Jenkins run upstream

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native

for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts

for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Hi @tarilabs, what do you mean by "requires consumer of kie-dmn to make use of aligned antlr runtime" please?

Hi @tarilabs, what do you mean by "requires consumer of kie-dmn to make use of aligned antlr runtime" please?

If the end-user is just building an app using Drools as a dependency, the antlr runtime will be inherited transitively, no problem.
Say instead the end-user is building an app using Drools but also frameworks or other dependencies which also rely on antlr-generated parsers; in that case, the end user would need to ensure it is using antlr runtime 4.13.0 while making use of DMN/FEEL in order to not have warnings emitted by the antlr infra detecting a mismatched antlr runtime--but might otherwise see analogous warning messages being emitted by the generated parsers coming from the "frameworks or other dependencies".
Hope this clarifies?

Yes, thank you. Approving.


can not run as you say

I did as you said step by step, but the result isn,t same as yours.

do you copy node_modules/puer-mock/example files to your project root directory?
what about your nodejs version? please try node 6.x

thank you for your answer. I updated my node to v7.x first, it didn't run. Then I installed node v6.10, it Worked.

@BoothLuo you are welcome.
It all OK now? No error anymore, and puer-mock worked?
You can try config your mock api now?

yes, it works very well. I'm trying my mock api now and you can close this issue. And thank you again for helping me.


InternalInnerText string concatenation to StringBuilder.Append

I got an issue with getting InnerText for large html, it just got stuck with huge memory consumption. I found that changing string to StringBuilder in this method solves the problem.

Hello @Tora-Bora ,
Thank you for the pull.
Yes, using StringBuilder will go make it faster for sure.
We will probably make it a little bit different and pass the StringBuilder in parameter to the InternalInnerText method to make it even faster.
We are a little bit busy at this moment and a lot of request for HAP are currently pending but we will try to make them all very soon.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Hello @Tora-Bora ,
The v1.11.14 has been released.
As said, we did it a little bit differently to make sure we re-use the same StringBuilder instead of creating many instances.
Let me know if your memory consumption is now back to normal with the latest version.
Thank again for your pull ;)
Best Regards,
Jonathan

Hey Jonathan,
Thank you, great job!
Best regards,
Maxim
On Tue, 1 Oct 2019, 04:47 Jonathan Magnan<EMAIL_ADDRESS>wrote:

Hello @Tora-Bora https://github.com/Tora-Bora ,
The v1.11.14 has been released.
As said, we did it a little bit differently to make sure we re-use the
same StringBuilder instead of creating many instances.
Let me know if your memory consumption is now back to normal with the
latest version.
Thank again for your pull ;)
Best Regards,
Jonathan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zzzprojects/html-agility-pack/pull/334?email_source=notifications&email_token=AA6PMIHQXSNFVFKHCBXVM4LQMJCUBA5CNFSM4I2VF3SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76V4AI#issuecomment-536698369,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6PMIHLTIQMNUDFZS7HRJDQMJCUBANCNFSM4I2VF3SA
.


Make 'queue:table' and 'queue:failed-table' respect tables config

Today I configured a new app to use "database" queue driver, and changed the default table name configuration from "jobs" to "laravel_jobs". Right after, I ran php artisan queue:table command and, to my surprise, the migration created had "jobs" as table name, instead of "laravel_jobs", as expected.
I dived into the framework code, and it is so f* good that I was able to quickly craft this PR, which uses the configured custom table names (both for "queue:table" and "queue:failed-table".

Unfortunately, it seems the build fails if I use the config() helper at a command... ? Hmm... let me try again...

Now what? I don't know if the issue is with the PR code or with tests/Queue/QueueSyncQueueTest.php code...

I have no clue of what is Travis complaining about. All versions simply work. The error message seems completely unrelated. I don't know what to do.


saving Bidirectional @OneToMany produce extra update statement

Hello,
I have Bidirectional @OneToMany relation similar like in this article:
https://vladmihalcea.com/the-best-way-to-map-a-onetomany-association-with-jpa-and-hibernate/
Child entity has jsonb column.
if set values to jsonb column, hibernate produce extra update statement during saving parent entity  like:
Hibernate: update SITEMAPURL set created=?, lastmodified=?, alternateLinks=?, changeFreq=?, lastMod=?, loc=?, priority=?, reference=?, SITEMAPURLSET=? where id=?
if jsonb column is empty, then hibernate doesn't execute update statement.
I'm using spring boot 2.6.1 and Hibernate Types 55 version 2.14.0
Do you have any idea what could be the problem?
Thank you.

Check out if you implemented equals and hashCode properly for the elements contained in the collection.

Thank you. Seems that was the problem :) After adding Lombok annotation @EqualsAndHashCode no extra update is present. Thank you :)

I'm glad I could help.


syft extract the full description of the license in python

What happened:
I scanned an image of python, and one of the packages has a full description of the license.
here is an example:
        {
          "path": "/usr/local/lib/python3.9/site-packages/numpy-1.26.4.dist-info/RECORD",
          "layerID": "sha256:6baba55ee976c6469c4b3b5a3c4585320bc0da3e3c9638e2169195f7243b8d03",
          "accessPath": "/usr/local/lib/python3.9/site-packages/numpy-1.26.4.dist-info/RECORD",
          "annotations": {
            "evidence": "supporting"
          }
        }
      ],
      "licenses": [
        {
          "value": "Copyright (c) 2005-2023, NumPy Developers.\n All rights reserved.\n \n Redistribution and use in source and binary forms, with or without\n modification, are permitted provided that the following conditions are\n met:\n \n * Redistributions of source code must retain the above copyright\n notice, this list of conditions and the following disclaimer.\n \n * Redistributions in binary form must reproduce the above\n copyright notice, this list of conditions and the following\n disclaimer in the documentation and/or other materials provided\n with the distribution.\n \n * Neither the name of the NumPy Developers nor the names of any\n contributors may be used to endorse or promote products derived\n from this software without specific prior written permission.\n \n THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\n LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR\n A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT\n OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,\n SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT\n LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,\n DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY\n THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

What you expected to happen:
In case license has \n inside of it, I think syft should trim it so it will not make the SBOM look weird.
Steps to reproduce the issue:
Here is the Dockerfile to build a sample of an image:
# Use the official Python 3.9 image from Docker Hub
FROM python:3.9

# Set the working directory in the container
WORKDIR /app

# Install the specific version of NumPy
RUN pip install numpy==1.26.4

# Specify the command to run on container start
CMD ["python"]

Anything else we need to know?:
Environment:

Output of syft version: 1.9.0
OS (e.g: cat /etc/os-release or similar): mac

Hi @tomersein, thanks for the report! I was able to  reproduce this issue. I appreciate the inclusion of a Dockerfile - it makes reproducing the issue a lot easier.

Make a Dockerfile exactly as above (thanks!)
Run docker build -t syft3088 .
Run syft -o json syft3088 > syft-sbom.json
Run cat syft-sbom.json | jq '.artifacts[] | select(.name=="numpy") | { name: .name, licenses: .licenses }'

You can see that the license set has a value that's the whole text of the license and the SPDX expression is blank.
Interestingly, on GitHub, the license is also shown as just "license" rather than having some automatic identification: https://github.com/numpy/numpy?tab=License-1-ov-file

my suggestion is to use split \n and take the 1st part of the value in cases like that.
what do you think?

👋 thanks for the license issue @tomersein!
It looks like syft is pulling this value from the following path in the container:
/usr/local/lib/python3.9/site-packages/numpy-1.26.4.dist-info/METADATA
This happens when the Python cataloger runs and we construct package details from the Egg/Wheel metadata:
https://github.com/anchore/syft/blob/9d40d1152e91fd520602f159e5d02a8736cb16ac/syft/pkg/cataloger/python/parse_wheel_egg.go#L186-L192
Here is the field definition from we key off of from the python Metadata specification:
https://packaging.python.org/en/latest/specifications/core-metadata/#license
In this case the package distributor opted to put the full text of the license in this field.
This is a valid value for when we go and decode the map structure of this file here:
https://github.com/anchore/syft/blob/9d40d1152e91fd520602f159e5d02a8736cb16ac/syft/pkg/cataloger/python/parse_wheel_egg_metadata.go#L39-L51
I appreciate the suggestion of using a split \n to truncate longer values in this case, but I am afraid that might be inadequate in the general sense.
If you look at the contents of this license block the Author's take a good amount of effort to address different distributions they consume as a part of NumPy:
First the general clause for redistribution of the software
        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
        "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
        LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
        A PARTICULAR PURPOSE ARE DISCLAIMED.

More information (not in their github license.txt) about what they distribute
        The NumPy repository and source distributions bundle several libraries that are
        compatibly licensed.  We list these here.

        Name: lapack-lite
        Files: numpy/linalg/lapack_lite/*
        License: BSD-3-Clause
          For details, see numpy/linalg/lapack_lite/LICENSE.txt

        Name: tempita
        Files: tools/npy_tempita/*
        License: MIT
          For details, see tools/npy_tempita/license.txt

        Name: dragon4
        Files: numpy/core/src/multiarray/dragon4.c
        License: MIT
          For license text, see numpy/core/src/multiarray/dragon4.c

        Name: libdivide
        Files: numpy/core/include/numpy/libdivide/*
        License: Zlib
          For license text, see numpy/core/include/numpy/libdivide/LICENSE.txt

        Note that the following files are vendored in the repository and sdist but not
        installed in built numpy packages:

        Name: Meson
        Files: vendored-meson/meson/*
        License: Apache 2.0
          For license text, see vendored-meson/meson/COPYING

        Name: spin
        Files: .spin/cmds.py
        License: BSD-3
          For license text, see .spin/LICENSE
        ----

There are also considerations for the following (there are more truncated for brevity):
        Name: OpenBLAS
        Files: numpy.libs/libopenblas*.so
        Description: bundled as a dynamically linked library
        Availability: https://github.com/OpenMathLib/OpenBLAS/
        License: BSD-3-Clause
          Copyright (c) 2011-2014, The OpenBLAS Project
          All rights reserved.

        Name: LAPACK
        Files: numpy.libs/libopenblas*.so
        Description: bundled in OpenBLAS
        Availability: https://github.com/OpenMathLib/OpenBLAS/
        License: BSD-3-Clause-Attribution

        Name: libquadmath
        Files: numpy.libs/libquadmath*.so
        Description: dynamically linked to files compiled with gcc
        Availability: https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=libquadmath
        License: LGPL-2.1-or-later

Cutting the license off at the new line here would remove this information from the SBOM.
I know long field values are ugly and bloat the document, but in this case the value of the license file is as accurate as we can make it without resorting to some specialized parsing for this unique case.
@anchore/tools should we NOT be including this when we discover it associated with the package?

Maybe we should add a new fullText field on the existing package License structure, so that we can separate when we do detect the different use cases here into a separate field. This can be leveraged directly in SPDX too, which is nice.

hi @wagoodman , what is the decision?
may I have a way to help with the solution?

Hey @tomersein!
We talked about this on our livestream the other day. We're moving forward with FullText field being added to the license struct. What do you think is the best way forward detecting this? Just doing a simple len(arbitraryNumber) to see if it's the full text?
https://www.youtube.com/@Anchore/streams

i suggest \n character. I don't think saving twice the long license value is a good practice.

@spiffcs , https://peps.python.org/pep-0639/ has been provisionally accepted which will hopefully make this metadata field more standardised for future python package releases at least

Regarding:

What do you think is the best way forward detecting this? Just doing a simple len(arbitraryNumber) to see if it's the full text?

My suggestion would be to do this:
a) fuzzy match the license to an SPDX ID - don't include "full text" if we're just given an SPDX ID
b) for all other cases: include the license text we used as a fullText field, as was suggested above, and additionally try to classify the license using the library and if it returns a license that we can match to SPDX ID include that ID as well as the original license text


Task: Simple First PR to NumPy - Update internal links

If you have never contributed a PR to an open-source project before, then here is a short task that can get you started.
At the triage meeting on May 1, we discussed an improvement to NumPy that is wanted and welcome.  As you spend time in the documentation, you'll notice that occasionally the links for internal functions are missing (or perhaps broken). These are simple to fix and provide a great chance to practice the PR (pull request) process. We'll be in the documentation a lot over the next 3 months, so we can tackle this bit by bit.
Make sure you start by reading the style guide. In particular, the tiny bit at the bottom about common reST concepts is crucial. Many of the missing links appear because someone used double back ticks, when all they needed were single back ticks. Here's some examples.
``default_rng`` #appears as monospace. Should be avoided for numpy functions
`default_rng` #creates internal link to default_rng, of which the only one is numpy.random.default_rng
`~default_rng` #same as above, the tilde isn't needed
`numpy.random.default_rng` #creates internal link to numpy.random.default_rng
`~numpy.random.default_rng` #creates internal link to numpy.random.default_rng, but the link text is default_rng

In many places in the code you'll see spots where people have added an extra tilde that isn't needed. We don't need to remove the tilde. We can replace the double back ticks with single back ticks, when the monospaced item is a function inside NumPy. If two classes have a function with the same name, then you may need the tilde.
After you've made changes, remember to build the docs locally on your machine and verify the links were appropriately created.  Some NumPy functions don't have docs attached (perfect, let's try to generate some with AI). In this case, when we try to create a single backticked internal link, we get an error in the docs build process.
Functions that are not part of NumPy have also been double backticked (displaying as monspace).  These can be improved as well, using more Sphinx markup. The bit below creates a link to the python function secrets.randbits.  See this implemented at https://numpy.org/devdocs/reference/random/parallel.html.
:py:func:`secrets.randbits`

The OSS maintainers would prefer this be done bit by bit. They manually check each change, and would prefer to NOT have to spend hours checking hundreds of links all at once.  A few here and there is fine. If someone wants to write a script to do all the replacements, and that script can be run and verified by the maintainers, then they would welcome that as well.
If you decide to pick up this task, please leave a comment below.
Remember that PRs should not be submitted directly to numpy. Either @bmwoodruff or @InessaPawson needs to review the work first. Here a possible workflow.

Make changes locally on a feature branch, and test them (build the docs for this example).
After you've tested things work, push the changes to the feature branch of your numpy fork.
Create an issue here in genai-numpy with an @bmwoodruff tag letting me know your work needs review.
Once you have approval, you can submit the PR to numpy.

Contributing to an open source project can be difficult.  There's an initial mental hurdle to pass, namely that your work will be completely open and you have no idea how things will turn out.  Mars Lee created the following comic to help newcomers alleviate the anxiety that comes with doing so.  It's a fun read.
https://heyzine.com/flip-book/3e66a13901.html#page/1

@bmwoodruff Hello Ben, I'm interested in working on this issue. Could you spare some time this week? I would appreciate your guidance on a few things. Starting might be a bit of a challenge, but once I have a complete idea, then I will be okay moving forward.


disable inline rename to prevent crash

Filed #2303 to track this.
@KevinRansom @cartermp

Good fix 👍


Add the release date to the changelog

It would be nice to see in the changelog when a release has been published. Functionality for that could possibly be added here: https://github.com/swisspost/design-system/blob/main/packages/changelog-github/src/index.ts.

Not possible with the current setup. The design-system-changelog-github package can only change one single change line in the log. Would need to dig into changesets a little further. No priority right now.
The issue is already rased by https://github.com/changesets/changesets/issues/658 and could be implemented in a future version of changesets.


Service Accounts

Change translation to the homepage instead of translating this page

https://kubernetes.io/docs/concepts/security/service-accounts/

Hi @HakimMiao, Could you please share some more information on the issue in the description section?

/sig security
/language en

/sig security
/language en
/triage needs-information

When I switch languages in the serviceaccount interface, the page will redirect to the main page instead of redirecting to the language interface I have chosen.
Sorry, my picture cannot be uploaded

Bahasa Indonesia

Italiano (Italian)

It is happening because the corresponding page in the selected regional language is not available.

you can help to translate  https://kubernetes.io/docs/concepts/security/service-accounts/ page to your regional language

if you got the answer, please close the issue


Fix variable initialization flow in component-element

[Issue] https://github.com/Samsung/TAU-Design-Editor/issues/304
[Problem] Several errors connected with triggering functions or fields
on undefined variables
[Solution] Fix variable initialization flow in component-element
Signed-off-by: Hubert Siwkin<EMAIL_ADDRESS>

Is it also apply the default index.html file?

It should apply to all scenarios in which component-element.js is used (it essentialy fixes a couple of console errors that kept occurring during execution of code from this file). So it applies both for new pages and initial html.
When it comes precisely to #304 - from what I see in the current version of DE ui-content works properly on all kinds of the new page (empty page, footer & header page) - it's quite small initially but resizes after being filled with components.


JSON Schema for v1.2 API Declaration authorizations is wrong

The way things should work, based on the Swagger 1.2 Specification is you should define authorizations in the Resource Listing and then reference them using the authorizations property in the API Declarations and the Operations.  Based on the current schema, the authorizations property in the API Declaration is for defining authorizations instead of referencing them so you are unable to have authorization references at the API Declaration level.
Originally opened in reverb/swagger-spec/issues/118.

@whitlockjc Can this issue be closed?

I think we can close it.  My understanding is that enhancements/fixes to 1.x isn't happening right now.  @webron can reopen if he thinks we should address it.


revise all CFP related legal files

cfp
cfp-data
visitors-data

@jprzybylski4 ALL FILES are now located under https://github.com/ecommerceberlin/ecommerceberlin.com/tree/master/texts in PURE markdown for better readability (github - like https://github.com/ecommerceberlin/ecommerceberlin.com/blob/master/texts/cfp.md) and editability (personally i recommend IA WRITER Classic but Visual Studio Code also handles *.md files perfectly)

resolved  via https://github.com/ecommerceberlin/ecommerceberlin.com/commit/e20dff0f34d4da13940e2574a3e31f2fb0a2babb


Input: Editable Input behavior

Looks like the input in read-only mode has a different width than in edit mode—this is leading to some horizontal shifting when toggling between the two modes
When the user enters edit mode, let's focus the input so they can immediately begin typing
In edit mode, let's toggle the edit icon to a button with a check mark, sitting next to a button with an 'x' or circle-slash icon. The latter should be disabled and both visibility: hidden and aria-hidden="true" should be set.

Created a PR - linked to this issue. Let me know if there is anything I should fix. Thanks!

Created a PR - linked to this issue. Let me know if there is anything I should fix. Thanks!


KeyError on missing grain

Just ran into the previous error:
# salt-run vault.show_policies ip-10-241-208-27.ec2.internal
Exception occurred in runner vault.show_policies: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/client/mixins.py", line 395, in _low
    data['return'] = self.functions[fun](*args, **kwargs)
  File "/var/cache/salt/master/extmods/runners/vault.py", line 50, in show_policies
    return _get_policies(minion_id, config)
  File "/var/cache/salt/master/extmods/runners/vault.py", line 77, in _get_policies
    for expanded_pattern in _expand_pattern_lists(pattern, **mappings):
  File "/var/cache/salt/master/extmods/runners/vault.py", line 113, in _expand_pattern_lists
    (value, _) = f.get_field(field_name, None, mappings)
  File "/usr/lib64/python2.7/string.py", line 640, in get_field
    obj = obj[i]
KeyError: 'Environment'

Hm, I don't think you're running the latest code. I merged the try/except code yesterday evening, so you might need to pull again. The line numbers in your stack trace don't match the code in master, at least.

Right you are. Current version looks good. Thanks!


#591 implemented HTTP request timeout config value

close #591 implemented HTTP request timeout config value + lint

it seems that not works.
i have errors in sendMessage:
cURL error 28: Failed to connect to api.telegram.org port 443 after 10001 ms: Timeout was reached


CSS position property not working as intended for Vue/React based nodes in Safari

Describe the bug
While adding CSS position property to any element within the Vue/React node, it renders fine in Chrome. But in Safari, it's not working as intended. The element is placed at the beginning.
Your Example Website or App
https://codesandbox.io/s/vue-shape-forked-s6x9nz?file=/src/components/Count.vue
Steps to Reproduce the Bug or Issue
Please open the below sandbox in both chrome and safari to spot the differences
Vue based nodes
React based nodes
Expected behavior
Ideally it should work as expected in chrome
Screenshots or Videos

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

This is a bug in safari. See here for details and solutions.

I also met ,it renders well in others,but not well in ios

this problem is confusing me and struggling me
bro, did u solve this problem？


Fix unique key length at 62 hex chars

The host os looks to have been using 16 for the uuid for a very long time (at least 11 months, I didn't dig into exactly when it started), my guess is it was just an accident

@page I don't think this was a mistake. It was one of @petrosagg requests for the 2.0 release I believe

Oh wtf, do you have any idea why @shaunmulligan? We still use 31 bytes everywhere else so it just makes the host os registration diverge from every other method

Closing as per https://www.flowdock.com/app/rulemotion/resin-devices/threads/GVS9p9zBqizP2T5LDR99rs92ScH


PHONE version  - remove blue banner above video (header)

Reference:

This is caused by the css of the video, position: absolute, and only appears on the main page. I think would be resolved by changing it to position: fixed.


Convert wildcard parameters

The situation is that [Route("search/{*key}")] will be rendered as search/{*key} instead of 'search/${key}' because the asterisk (*) is not considered to exist.
This change is necessary because my key may contain slashes (a/b/c) and only the wildcard parameter can catch these kind of values.
I updated the regex to allow the existence of an optional single asterisk and tested the change.
It would be awesome if it would be included in V1.4 V1.5 :+1:
Thank you!

I didn't updated the tests yet, but here is a testcode sample.
var regex = @"\{\*?(\w+):?\w*\??\}";
var resultWithoutWildcard = Regex.Replace("search/{key}", regex, m => $"${{{m.Groups[1].Value}}}");
var resultWithWildcard = Regex.Replace("search/{*key}", regex, m => $"${{{m.Groups[1].Value}}}");
Assert.AreEqual(resultWithoutWildcard,  resultWithWildcard);

Nice work!

Thanks! When will you release the next version?

Just released 1.4.1 (including this PR)

Works fine thank you for the quick release!


[5.7][CSClosure] Fix some aspects of property wrapper handling in closures

Cherry-pick of https://github.com/apple/swift/pull/61052

Explanation:

Fixes a couple of issues related declaring and using property wrappers in closures which regressed in 5.7.

Always pre-check init targets of wrapped vars

If a variable with attached property wrapper has an initializer
expression it could be modified by implicit wrapper application,
if there is no initializer - one would be synthesized by the
compiler (without arguments). In both cases target has to be
pre-checked before constraints are generated for it.

Use correct type for implicit wrapper variables

Using computeWrappedValueType is incorrect because
that return a type of the wrapped variable and not
the wrapper variable (one that starts with _).

Scope: Property wrapper variable references in closures (_<name>) and property wrapped variable declarations with extra arguments.

Main Branch PR: https://github.com/apple/swift/pull/61052

Resolves: https://github.com/apple/swift/issues/61024, https://github.com/apple/swift/issues/61017

Risk: Very low

Reviewed By: @hborla

Testing:  Added a regression test-case to the suite.

@swift-ci please test

@swift-ci please nominate


cleanup created docker containers

Cancelled or timeouted workflow would keep the docker container running. Closes game-ci/unity-test-runner#197
This has two parts:
Part one. The entrypoints.
runs.post: GitHub Action metadata allow running something after the action (regardless of a failure, crash, timeout, ...). https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspost
However, it needs to be a .js file and it can't be configured to pass any arguments.
There already was index.js used as the main entrypoint. The build process of this file uses typescript compiler and ncc to pack all dependencies into one .js file. And ncc has no way of generating multiple files in one go, so the only solution would be to run ncc twice and generate two independent files.
That would be quite unfortunate, wasting time and storage. So I rather came up with a new entrypoint that symlinked from two locations. And this new entrypoint understands how it was executed, so it can run the correct behaviour. This makes it easy to add runs.pre if needed.
This new entrypoint is in index.ts. The original index.ts is now in main.ts.
Part two.
The signals. I've tried:

try/catch/finally around the await Docker.run. Catch and finally are not executed when process receives SIGINT. See the discussion in: https://github.com/nodejs/node/discussions/29480
New AbortController and AbortSignal. Great concept, but the action.exec does not support it. So it can't be aborted.
Doing cleanup on process.on('exit'). Unfortunately you can't really do async stuff from there, so can't really run the docker rm command to delete the container.
Using process.on('SIGINT'). For some reason that wasn't really executing for me. I'd not put my hand in fire for this, but I assume because it was in the signal handler it does something special, or would heed to be scheduled for later with setTimeout(0).

Evaluating all these I came to a conclusion that it is fragile and just relying on a runs.post is much better and safer.
I've not tested this on Windows, so that probably needs to happen. I've tried running locally with act and it worked. Worked also on my hosted linux runner.

Great explanation! Thanks for the elaborate details, it will be very helpful for merging this.

Evaluating all these I came to a conclusion that it is fragile and just relying on a runs.post is much better and safer.

Ok, based on your research I would agree. Let's go for your approach.

Using process.on('SIGINT'). For some reason that wasn't really executing for me. I'd not put my hand in fire for this, but I assume because it was in the signal handler it does something special, or would heed to be scheduled for later with setTimeout(0).

As I understand it, that's probably because an event listener doesn't stop the event from bubbling and you only have a few milliseconds to do any cleanup.

I've updated it to clear up things brought in the review.
I've also added some type annotations to the new code, so it explicitly handles default values.
IMO that is important in case this ever gets executed outside of Github Action Runner (like unit tests, or trying it locally).

LGTM. This can be merged once it's tested.

I'm running this on my hosted runner with concurrency limited cancellable workflows and it works well.
Don't have Windows pipeline to try it on.