Bundler cannot resolve right relative paths since version 1.11.2 (Test example attached)

Hello, have no idea why it worked for me so long time and why I didn't meet it before, but looks like problem exists.
My case
I have a rails based CMS. I use it for some projects. Some pojects based on this CMS have to use some specific gems. That is why in my Gemfile I use something like this:
source 'https://rubygems.org'
gem 'rails'
eval_gemfile "./Gemfiles/#{ ENV['PROJECT_NAME'] }_specific_gems.rb"

Also, in my app I have

a directory for specific Gemfiles (folder has name Gemfiles)
a directory for specific gems (folder has name gems)

The problem
Looks like since version 1.11.2 bundler cannot resolve right paths to my local gems.
When I use paths like this:
gem 'gem1', path: './gems/gem1'

Bundler gives to me:
/PATH/TO/RELEASES/RAILS_CMS/current/Gemfiles/gems/gem1

But it should be /PATH/TO/RELEASES/RAILS_CMS/current/gems/gem1, and it was so before.
And when I use
gem 'gem1', path: '../gems/gem1'

Bundler gives to me:
/PATH/TO/RELEASES/RAILS_CMS/gems/gem1

But actually I expected to get:
/PATH/TO/RELEASES/RAILS_CMS/current/gems/gem1 # <= this one is right path, but it's impossible to get it somehow

/PATH/TO/RELEASES/RAILS_CMS/current/Gemfiles/gems/gem1 # <= this one is wrong
/PATH/TO/RELEASES/RAILS_CMS/gems/gem1           # <= this one is wrong too

TEST CASE
There is simple test case to reproduce my problem
https://github.com/the-forks/bundler_test_case
You can find steps to reproduce in a README.md
PS:
I tried to play with ENV BUNDLE_GEMFILE. It didn't help

This was an intentional change. Bundler now expands relative paths relative to the gemfile being evaluated's directory rather than the parent gemfile.
The following diff fixes things!
diff --git a/Gemfiles/specific_1.rb b/Gemfiles/specific_1.rb
index a9c9f87..afd8c8a 100644
--- a/Gemfiles/specific_1.rb
+++ b/Gemfiles/specific_1.rb
@@ -1,2 +1,2 @@
-gem 'gem1', path: './gems/gem1'
-gem 'gem2', path: './gems/gem2'
\ No newline at end of file
+gem 'gem1', path: './../gems/gem1'
+gem 'gem2', path: './../gems/gem2'

@segiddins Hello!
Thank you for your answer!
Unfortunately it doesn't work.
If you haven't time to install and reproduce my case there is my video demo where I try to use your recommendation.
https://drive.google.com/file/d/0B1E1Md_wjncLRV9iSHltdnJiRDQ/view?usp=sharing
Thanks for your help and time.

PS: I can reproduce this problem on my Mac and on my Debian 8.5 server on DigitalOcean & I user RVM.

When applying my change, it passed on my machine, so perhaps another reproduction case is required?

@segiddins oh. Let me check it yet another time. It's really strange

@segiddins we tested it with my college on his local machine. He reproduced this bug. Problem exists.
To reproduce this bug you can just use this steps:
rm -rf ./bundler_test_case

git clone git@github.com:the-forks/bundler_test_case.git
cd bundler_test_case

gem install bundler -v=1.13.0

bundler _1.13.0_
bundler _1.13.0_

Please, try it again. Do you really have not any issues?

Fetching gem metadata from https://rubygems.org/.
Fetching version metadata from https://rubygems.org/
Resolving dependencies...
Using gem1 0.1.0 from source at `./../gems/gem1`
Using gem2 0.1.0 from source at `./../gems/gem2`
Using bundler 1.13.0
Bundle complete! 2 Gemfile dependencies, 3 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

@segiddins did you run bundler _1.13.0_ twice?
it's not a mistype, you need to run it twice.
first time it can find gems - it's ok. But Gemfile.lock will have wrong paths, and on second time bundler _1.13.0_ should give an error.
Sorry, that I disturb you, but I'm pretty sure that problem exists. 2 friends of mine produced it.

this is my Gemfile.lock after bundle
PATH
  remote: ./../gems/gem1
  specs:
    gem1 (0.1.0)

PATH
  remote: ./../gems/gem2
  specs:
    gem2 (0.1.0)

GEM
  remote: https://rubygems.org/
  specs:

PLATFORMS
  ruby

DEPENDENCIES
  gem1!
  gem2!

BUNDLED WITH
   1.13.0

but it has to have paths like:
PATH
  remote: ./gems/gem1
  specs:
    gem1 (0.1.0)

PATH
  remote: ./gems/gem2
  specs:
    gem2 (0.1.0)

Never mind, it finally reproduced

https://github.com/bundler/bundler/pull/4976 should fix this


Daily Update

add serial port handle class named AgilexBaseSerialPort
add motion mode in SystemStateFrame struct
add LimoBase , the driver of a small new car called Limo
add read imu data and decode in the agx_msg_parser.c
add MotionMode enum to sperate different motion mode passed from chassis

merge

Daily Update


Add support for remote writing from one Prometheus to another

Enhancement Proposal
We need to support use cases where users want to tier their Prometheus deployments to avoid excessive pressure. By adding send-remote-write to Prometheus, and remote writing whatever we receive, we've effectively accomplished this.

Note: reopen and append #410 when receive customer request with requirements.
For discussion around the feature please see #376

it was added at some point (#376) but it was later removed (when?, by whom? why?)
does @simskij remember? Or maybe @beliaev-maksim?


Xcode Manual Signing - Can't Find iOS App Store provisioning profiles matching 'my.bundle.id'

Required Information
Bug
Xcode Manual Signing Failing - Unable to find downloaded provisioning profile
Enter Task Name: Xcode
Environment
Server - TFS on-premises

If using TFS on-premises, provide the version: I manually upgraded the tasks, so this probably is not helpful

Task Versions:

Install Apple Certificate: 2.214.0
Install Apple Provisioning Profile: 1.212.0
Xcode: 5.213.0

Agent - Private:

If using private agent, provide the OS of the machine running the agent and the agent version: MacOS Ventura

Issue Description
I have a pipeline set up to build and sign an ios app. I run the install certificate/provisioning profile tasks beforehand, but the xcode build will fail every time on the export. I have it set to manual signing because my understanding is auto would not work for app store.
Task logs
I can share these privately but do not want to post them here publicly.
Error logs
error: exportArchive: No profiles for 'my.bundle.id' were found

Error Domain=IDEProfileLocatorErrorDomain Code=1 "No profiles for 'my.bundle.id' were found" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=No profiles for 'my.bundle.id' were found, NSLocalizedRecoverySuggestion=Xcode couldn't find any iOS App Store provisioning profiles matching 'my.bundle.id'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.}

Hi @jdwirrenga, could you please attach agent logs where the issue has occurred?

@sergey-koryshev sent you the log files and yaml but postmaster@microsoft blocked the email. Could you add<EMAIL_ADDRESS>to the allowed senders list, or shall I try a different address?

@jdwirrenga, is there a reason of this blocking in email from postmaster?

@sergey-koryshev

@jdwirrenga, please try to send email to this address<EMAIL_ADDRESS>

Related email-thread with logs for reference: Fwd: Xcode Manual Signing - Can't Find iOS App Store provisioning profiles matching 'my.bundle.id' #17478

This is still broken, has anyone looked into it?

Still doesn't work, a year later.

Still broken, 2 years later.


Which system codes for Chembl?

In commit ab02add1bee33b47e45bfdee7f89190681e9bcf2 @egonw added to org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txt:
ChEMBL compound	Cl	http://www.ebi.ac.uk/chembl/	https://www.ebi.ac.uk/chembl/compound/inspect/$id	CHEMBL308052	metabolite		1	urn:miriam:chembl.compound	^CHEMBL\d+$	ChEMBL compound

Using system code Cl here clashes with the equivalent entry in org.bridgedb.rdf, which uses ChEMBLCompound - what was the reason for going with Cl?
See both IdentifiersOrgDataSource.ttl and in IdentifiersOrgDataSource.txt
This (luckily) causes the IdentifersOrgReaderTest test to fail with:
Caused by: java.lang.IllegalArgumentException: System code does not match for DataSource ChEMBL compound was Cl so it can not be changed to ChEMBLCompound
	at org.bridgedb.DataSource.findOrRegister(DataSource.java:640)
	at org.bridgedb.DataSource.register(DataSource.java:620)
	at org.bridgedb.rdf.BridgeDBRdfHandler.readDataSource(BridgeDBRdfHandler.java:131)
	at org.bridgedb.rdf.BridgeDBRdfHandler.getDataSource(BridgeDBRdfHandler.java:121)
	at org.bridgedb.rdf.BridgeDBRdfHandler.readAllDataSources(BridgeDBRdfHandler.java:113)
	at org.bridgedb.rdf.BridgeDBRdfHandler.doParseRdfInputStream(BridgeDBRdfHandler.java:92)
	... 33 more

The system codes used for ChEMBL within IdentifiersOrgDataSource.txt are not ideal:

ChEMBLCompound
ChemblId
ChemblMolecule
chembl.target
ChemblTarget (!)
Chembl16TargetComponent

Those are both very long, includes (wrong) version number, and has duplicates and are inconsistent.
At Identifiers.org we find the names

chembl.compound
chembl.target

(but nothing for molecules, assays or target component)
Cc is already used by CCDS.
After discussing this with @egonw I suggest modifying org/bridgedb/bio/datasources.txt to use system codes:

ChC (ChEMBL compound)
ChT (ChEMBL target)
ChTC (ChEMBL Target Component) -- or ChP for "protein"?

CamelCasing here mimics other entries like EnMm (Ensembl Mouse).
Views?

The rule I always applied to datasource system codes was

use existing BridgeDB code if it already exists! (Even if now deprecated)
use the identiers.org code if BridgeDB does not already have the DataSource
Make up a new one only if neither of the above apply.
I intentional used longer names here to not clash with possible future BridgeDB codes

So while we may not like the identiers.org codes I would still recommend using these until BridgeDB as a project selects a project wide code.
As I am no longer part of the BridgeDB project so I have no input to which new codes should be approved project wide. Except of course they should not clash with previously used (even deprecated) ones
Christian

From: Stian Soiland-Reyes<EMAIL_ADDRESS>Sent: Wednesday, September 09, 2015 1:09 PM
To: bridgedb/BridgeDb
Subject: [BridgeDb] Which system codes for Chembl? (#16)
In commit ab02addhttps://github.com/bridgedb/BridgeDb/commit/ab02add1bee33b47e45bfdee7f89190681e9bcf2 @egonwhttps://github.com/egonw added to org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txt#L11:
ChEMBL compound Cl  http://www.ebi.ac.uk/chembl/ https://www.ebi.ac.uk/chembl/compound/inspect/$id   CHEMBL308052    metabolite      1   urn:miriam:chembl.compound  ^CHEMBL\d+$ ChEMBL compound
Using system code Cl here clashes with the equivalent entry in org.bridgedb.rdf, which uses ChEMBLCompound - what was the reason for going with Cl?
See both IdentifiersOrgDataSource.ttlhttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.ttl#L953 and in IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84
This (luckily) causes the IdentifersOrgReaderTest test to fail with:
Caused by: java.lang.IllegalArgumentException: System code does not match for DataSource ChEMBL compound was Cl so it can not be changed to ChEMBLCompound
at org.bridgedb.DataSource.findOrRegister(DataSource.java:640)
at org.bridgedb.DataSource.register(DataSource.java:620)
at org.bridgedb.rdf.BridgeDBRdfHandler.readDataSource(BridgeDBRdfHandler.java:131)
at org.bridgedb.rdf.BridgeDBRdfHandler.getDataSource(BridgeDBRdfHandler.java:121)
at org.bridgedb.rdf.BridgeDBRdfHandler.readAllDataSources(BridgeDBRdfHandler.java:113)
at org.bridgedb.rdf.BridgeDBRdfHandler.doParseRdfInputStream(BridgeDBRdfHandler.java:92)
... 33 more
The system codes used for ChEMBL within IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84 are not ideal:

ChEMBLCompound
ChemblId
ChemblMolecule
chembl.target
ChemblTarget (!)
Chembl16TargetComponent

Those are both very long, includes (wrong) version number, and has duplicates and are inconsistent.
At Identifiers.org we find the names

chembl.compoundhttp://identifiers.org/chembl.compound/
chembl.targethttp://identifiers.org/chembl.target/

(but nothing for molecules, assays or target component)
Cc is already used by CCDS.
After discussing this with @egonwhttps://github.com/egonw I suggest modifying org/bridgedb/bio/datasources.txt to use system codes:

ChC (ChEMBL compound)
ChT (ChEMBL target)
ChTC (ChEMBL Target Component) -- or ChP for "protein"?

CamelCasing here mimics other entries like EnMm (Ensembl Mouse).
Views?
—
Reply to this email directly or view it on GitHubhttps://github.com/bridgedb/BridgeDb/issues/16.

While there are definitely codes I would have created differently, I second Christian in support of using identifiers.org codes in order to avoid re-inventing the wheel. If anyone needs to create a new identifiers.org code, you can easily submit a ticket here:
http://sourceforge.net/p/identifiers-org/new-collection/new/
Anders
----- Original Message -----

From: "Christian Brenninkmeijer"<EMAIL_ADDRESS>To: "bridgedb/BridgeDb"
<EMAIL_ADDRESS>Cc: "EU openPHACTS project members based at the University of Manchester"<EMAIL_ADDRESS>"bridgedb-discuss"<EMAIL_ADDRESS>Sent: Wednesday, September 9, 2015 5:20:05 AM
Subject: [bridgedb] RE: [BridgeDb] Which system codes for Chembl? (#16)
The rule I always applied to datasource system codes was

use existing BridgeDB code if it already exists! (Even if now deprecated)
use the identiers.org code if BridgeDB does not already have the
DataSource
Make up a new one only if neither of the above apply.
I intentional used longer names here to not clash with possible future
BridgeDB codes

So while we may not like the identiers.org codes I would still recommend
using these until BridgeDB as a project selects a project wide code.
As I am no longer part of the BridgeDB project so I have no input to which
new codes should be approved project wide. Except of course they should not
clash with previously used (even deprecated) ones
Christian

From: Stian Soiland-Reyes<EMAIL_ADDRESS>Sent: Wednesday, September 09, 2015 1:09 PM
To: bridgedb/BridgeDb
Subject: [BridgeDb] Which system codes for Chembl? (#16)
In commit
ab02addhttps://github.com/bridgedb/BridgeDb/commit/ab02add1bee33b47e45bfdee7f89190681e9bcf2
@egonwhttps://github.com/egonw added to
org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txt#L11:
ChEMBL compound Cl  http://www.ebi.ac.uk/chembl/
https://www.ebi.ac.uk/chembl/compound/inspect/$id   CHEMBL308052
metabolite      1   urn:miriam:chembl.compound  ^CHEMBL\d+$ ChEMBL
compound
Using system code Cl here clashes with the equivalent entry in
org.bridgedb.rdf, which uses ChEMBLCompound - what was the reason for going
with Cl?
See both
IdentifiersOrgDataSource.ttlhttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.ttl#L953
and in
IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84
This (luckily) causes the IdentifersOrgReaderTest test to fail with:
Caused by: java.lang.IllegalArgumentException: System code does not match for
DataSource ChEMBL compound was Cl so it can not be changed to ChEMBLCompound
at org.bridgedb.DataSource.findOrRegister(DataSource.java:640)
at org.bridgedb.DataSource.register(DataSource.java:620)
at
org.bridgedb.rdf.BridgeDBRdfHandler.readDataSource(BridgeDBRdfHandler.java:131)
at
org.bridgedb.rdf.BridgeDBRdfHandler.getDataSource(BridgeDBRdfHandler.java:121)
at
org.bridgedb.rdf.BridgeDBRdfHandler.readAllDataSources(BridgeDBRdfHandler.java:113)
at
org.bridgedb.rdf.BridgeDBRdfHandler.doParseRdfInputStream(BridgeDBRdfHandler.java:92)
... 33 more
The system codes used for ChEMBL within
IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84
are not ideal:

ChEMBLCompound
ChemblId
ChemblMolecule
chembl.target
ChemblTarget (!)
Chembl16TargetComponent

Those are both very long, includes (wrong) version number, and has duplicates
and are inconsistent.
At Identifiers.org we find the names

chembl.compoundhttp://identifiers.org/chembl.compound/
chembl.targethttp://identifiers.org/chembl.target/

(but nothing for molecules, assays or target component)
Cc is already used by CCDS.
After discussing this with @egonwhttps://github.com/egonw I suggest
modifying org/bridgedb/bio/datasources.txt to use system codes:

ChC (ChEMBL compound)
ChT (ChEMBL target)
ChTC (ChEMBL Target Component) -- or ChP for "protein"?

CamelCasing here mimics other entries like EnMm (Ensembl Mouse).
Views?
—
Reply to this email directly or view it on
GitHubhttps://github.com/bridgedb/BridgeDb/issues/16.
--
You received this message because you are subscribed to the Google Groups
"bridgedb-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>Visit this group at http://groups.google.com/group/bridgedb-discuss.
For more options, visit https://groups.google.com/d/optout.

I also support the use of identifiers.orghttp://identifiers.org codes here.
Alasdair
On 9 September 2015 at 19:25:25, Christian Y. Brenninkmeijer (notifications<EMAIL_ADDRESS>wrote:
While there are definitely codes I would have created differently, I second Christian in support of using identifiers.org codes in order to avoid re-inventing the wheel. If anyone needs to create a new identifiers.org code, you can easily submit a ticket here:
http://sourceforge.net/p/identifiers-org/new-collection/new/
Anders
----- Original Message -----

From: "Christian Brenninkmeijer"<EMAIL_ADDRESS>To: "bridgedb/BridgeDb"
<EMAIL_ADDRESS>Cc: "EU openPHACTS project members based at the University of Manchester"<EMAIL_ADDRESS>"bridgedb-discuss"<EMAIL_ADDRESS>Sent: Wednesday, September 9, 2015 5:20:05 AM
Subject: [bridgedb] RE: [BridgeDb] Which system codes for Chembl? (#16)
The rule I always applied to datasource system codes was

use existing BridgeDB code if it already exists! (Even if now deprecated)
use the identiers.org code if BridgeDB does not already have the
DataSource
Make up a new one only if neither of the above apply.
I intentional used longer names here to not clash with possible future
BridgeDB codes

So while we may not like the identiers.org codes I would still recommend
using these until BridgeDB as a project selects a project wide code.
As I am no longer part of the BridgeDB project so I have no input to which
new codes should be approved project wide. Except of course they should not
clash with previously used (even deprecated) ones
Christian

From: Stian Soiland-Reyes<EMAIL_ADDRESS>Sent: Wednesday, September 09, 2015 1:09 PM
To: bridgedb/BridgeDb
Subject: [BridgeDb] Which system codes for Chembl? (#16)
In commit
ab02addhttps://github.com/bridgedb/BridgeDb/commit/ab02add1bee33b47e45bfdee7f89190681e9bcf2
@egonwhttps://github.com/egonw added to
org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.bio/resources/org/bridgedb/bio/datasources.txt#L11:
ChEMBL compound Cl http://www.ebi.ac.uk/chembl/
https://www.ebi.ac.uk/chembl/compound/inspect/$id CHEMBL308052
metabolite 1 urn:miriam:chembl.compound ^CHEMBL\d+$ ChEMBL
compound
Using system code Cl here clashes with the equivalent entry in
org.bridgedb.rdf, which uses ChEMBLCompound - what was the reason for going
with Cl?
See both
IdentifiersOrgDataSource.ttlhttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.ttl#L953
and in
IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84
This (luckily) causes the IdentifersOrgReaderTest test to fail with:
Caused by: java.lang.IllegalArgumentException: System code does not match for
DataSource ChEMBL compound was Cl so it can not be changed to ChEMBLCompound
at org.bridgedb.DataSource.findOrRegister(DataSource.java:640)
at org.bridgedb.DataSource.register(DataSource.java:620)
at
org.bridgedb.rdf.BridgeDBRdfHandler.readDataSource(BridgeDBRdfHandler.java:131)
at
org.bridgedb.rdf.BridgeDBRdfHandler.getDataSource(BridgeDBRdfHandler.java:121)
at
org.bridgedb.rdf.BridgeDBRdfHandler.readAllDataSources(BridgeDBRdfHandler.java:113)
at
org.bridgedb.rdf.BridgeDBRdfHandler.doParseRdfInputStream(BridgeDBRdfHandler.java:92)
... 33 more
The system codes used for ChEMBL within
IdentifiersOrgDataSource.txthttps://github.com/bridgedb/BridgeDb/blob/ab02add1bee33b47e45bfdee7f89190681e9bcf2/org.bridgedb.rdf/resources/IdentifiersOrgDataSource.txt#L84
are not ideal:

ChEMBLCompound
ChemblId
ChemblMolecule
chembl.target
ChemblTarget (!)
Chembl16TargetComponent

Those are both very long, includes (wrong) version number, and has duplicates
and are inconsistent.
At Identifiers.org we find the names

chembl.compoundhttp://identifiers.org/chembl.compound/
chembl.targethttp://identifiers.org/chembl.target/

(but nothing for molecules, assays or target component)
Cc is already used by CCDS.
After discussing this with @egonwhttps://github.com/egonw I suggest
modifying org/bridgedb/bio/datasources.txt to use system codes:

ChC (ChEMBL compound)
ChT (ChEMBL target)
ChTC (ChEMBL Target Component) -- or ChP for "protein"?

CamelCasing here mimics other entries like EnMm (Ensembl Mouse).
Views?
—
Reply to this email directly or view it on
GitHubhttps://github.com/bridgedb/BridgeDb/issues/16.
--
You received this message because you are subscribed to the Google Groups
"bridgedb-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>Visit this group at http://groups.google.com/group/bridgedb-discuss.
For more options, visit https://groups.google.com/d/optout.

—
Reply to this email directly or view it on GitHubhttps://github.com/bridgedb/BridgeDb/issues/16#issuecomment-138998259.
--
Alasdair J G Gray
http://www.alasdairjggray.co.ukhttp://www.alasdairjggray.co.uk/
ORCID: http://orcid.org/0000-0002-5711-4872
Twitter: @gray_alasdair
Telephone: +44<PHONE_NUMBER><tel://Telephone:
+44%20131%20451%203429>
Office: EM 1.39

We invite research leaders and ambitious early career researchers to
join us in leading and driving research in key inter-disciplinary themes.
Please see www.hw.ac.uk/researchleaders for further information and how
to apply.
Heriot-Watt University is a Scottish charity
registered under charity number SC000278.

My proposed pull request #20 is raised as discussion point to settle this according to what you said:

chembl.compound
chembl.target
chembl.targetcomponent

and adding the two first of these to datasource.txt of org.bridgedb.bio
For the http://linkedchemistry.info/ identifiers I can't find have any direct equivalent in Chembl, so I've renamed the confusing "chemblTarget" and "chemblMolecule" etc to linkedchemistry.chembl.id, linkedchemistry.chembl.target and linkedchemistry.chembl.molecule.

See also #21 - I really struggle to do any kind of change on this.

@stain let's Skype chat in the coming week?


Support tern migration files

What do you want to change?
Tern, from the creator of pgx, is a new migration tool. It's migration files are SQL files, but use a different delimiter than golang-migrate.
create table t1(
  id serial primary key
);

---- create above / drop below ----

drop table t1;

What database engines need to be changed?
No response
What programming language backends need to be changed?
No response

I think it is really good to support both the "tried and true" and the cutting edge migration systems, especially since I'd consider sqlc cutting edge itself.
That said, it will always be a game of whack-a-mole to support them all, I've been using:
pg_dump --no-privileges --no-acl --no-owner --schema-only --no-comments --encoding=utf8 MY_DB_URI

Then I use that schema.sql file to feed to sqlc.  The database I manage has 957 migrations, and I think a source of truth schema file is a best practice anyway.
Perhaps we can publish (in the docs) that kind of workaround for anyone with an exotic migration system?
The workflow would be:
1. `your_migration_tool up` # to a dev database
1. `pg_dump ...`
1. `sqlc generate`

🤷 it works for me, maybe useful for others too.

Turns out this is already supported as of https://github.com/kyleconroy/sqlc/pull/286

Perhaps we can publish (in the docs) that kind of workaround for anyone with an exotic migration system?

We could add that to this documentation page https://docs.sqlc.dev/en/stable/howto/ddl.html


User menu review

Separated presenter and view
Removed logout action
Included username tests

+1.
master: 2562b504c35da79cd280779c64012d7ee05d492a


Strange behavior with sort order in lists - Dragula with Aurelia

I'm submitting a bug report

Library Version:
Aurelia Templating 1.1.2

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
6.2.0

NPM Version:
3.8.9

JSPM OR Webpack AND Version
JSPM 0.16.32

Browser:
Chrome

Language:
ESNext

Current behavior:
I am using Dragula with Aurelia and everything works fine. However I did not called DragApi.cancel to cancel Dragula events like here https://github.com/jdanyow/aurelia-solitaire/blob/master/src/drag-and-drop.js#L41
because I need specific Dragula functionalities such as animations when drag-dropping, auto scrolling etc.
I have a weird behavior. I use server side sorting for items inside list.
When I drag-drop few items (change sort order of items) in list , save new sort order on server side and then refresh data like this:
 this.columnList = result;
sort order of items in list I get from server side is changed on client side.
It seams like Aurelia try to re-apply drag and drop operations that previously happens and apply same operations.
This way sort order of items in list is changed.
Expected/desired behavior:
Not sure why is this happening. Why drag and drop can affects Aurelia behavior and how to prevent this?

@jdanyow You've got some experience with Dragula. Any ideas?

If you allow Dragula to move a DOM element that is managed by the Aurelia repeat.for, things will get out of sync. The repeat.for has no knowledge of the things Dragula is doing to the DOM.

@jdanyow @EisenbergEffect  Any suggestion what to do? If I understand correctly Aurelia just don't play nice with popular Drag and Drop libraries like Dragula or Sortable right? I will try to create dummy empty project to reproduce this behavior.

@jdanyow @EisenbergEffect I managed to solve all issues by calling DragApi.cancel and removing / add elements from arrays manually. Just wanted to say keep up the good work. Aurelia is great.


Replace NSUndefinedDateComponent with NSDateComponentUndefined

NSUndefinedDateComponent is deprecated from:

iOS 8
OS X 10.10
watchOS 2.0

NSDateComponentUndefined is available from:

iOS 7
OS X 10.9
watchOS 2.0
tvOS 9.0

Sorry I botched the branches, will fix and issue another pull request.

Coverage remained the same at 83.844% when pulling 07e60bcac09fd83795abd09627560a3984d9d737 on danielctull-forks:deprecations into 4f83cc81781afb6ce3c0f1e0affdff6a0584fa4f on boredzo:master.


Rename the proposal from "extensions" to "static dispatch operator"

Currently the proposal is named as "Extensions and :: operator". I'm considering rename it to "static dispatch operator" (contrasts with . and [], which are dynamic dispatch operators).
Though extension methods/accessors are the important motivation/use cases of the proposal, there are also other motivation/use cases. For example utilize :: operator to get good syntax for first-class protocol and static invoking in the classes.
Another issue is not every people know extensions concept well, and it also has different with extensions of other programming languages (use :: operator instead of . operator, has receiver::X:foo form).
So renaming the proposal to "static dispatch operator" could give the more precise description --- provide a form of method dispatch which resolve the method/function statically, contrasts with a.foo and a["foo"] which resolve the method/function dynamically.
As such renaming, Symbol.extension will also be renamed to Symbol.dispatcher.

I plan to change the syntax to dot based (eg. receiver.x'foo), so let's keep the word "extension".
x'foo could be seen as a "compound identifier" which is a two identifiers combined by the separator, so the proposal name might become "extensions and compound identifier".


How to see what Interop policy is currently assigned to someone?

There doesn't appear to be a way to pull the InteropPolicy for a user who already has one set... where do we see this?

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8354e80d-02da-7f51-a713-e698322e8ec1
Version Independent ID: ef42d9af-336a-e014-de0a-b7bf7bb1f87d
Content: Quick start guide - Configuring Calling Plans in Microsoft Teams
Content Source: Teams/configuring-teams-calling-quickstartguide.md
Service: msteams
GitHub Login: @arachmanGitHub
Microsoft Alias: MyAdvisor

@arachmanGitHub Can you respond to this comment please?

hi @webash, you can grant $null policy for the intended user to remove the interop policy applied to a user. Example: Grant-CsTeamsInteropPolicy -Identity<EMAIL_ADDRESS>-PolicyName $null

Maybe it's worth adding that as an example?
Also, it's not clear that you need to use Get-CsOnlineUser to see the existing Interop Policy, so can I recommend adding that as a related command?

Great feedback @webash, I'll make sure the suggestions are accommodated in the next update of the article.

Has the cmdlet New-CsTeamsInteropPolicy been removed from the SfB Online module? What is then the alternative to create new custome Teams Interop policies?
I cannot create a new custom Teams Interop Policy as described in the guide. Whenever I try to create a new Teams Interop Policy I get the following error message: "New-CsTeamsInteropPolicy : The term 'New-CsTeamsInteropPolicy' is not recognized as the name of a cmdlet, function, script file or operation program."
Additionally, I do not see the cmdlet listed under the Skype PowerShell reference: https://docs.microsoft.com/en-us/powershell/module/skype/?view=skype-ps
However, the cmdlets Get-CsTeamsInteropPolicy and Grant-CsTeamsInteropPolicy are available and work.

@rrgonzalezz I believe your question has been answered in the different thread. To sum up, we're in the process of retiring TeamsInteropPolicy and you need to use the pre-canned instances moving forward:
• DisallowOverrideCallingDefaultChatDefault
• DisallowOverrideCallingSfbChatSfb
• DisallowOverrideCallingTeamsChatTeams


Accessibility Issue Adaptive Card - Input fields and visual labels are not associated

Issue Description : -
If a relationship between elements is expressed with visual cues, it also needs to be programmatically determined. This enables assistive technology to communicate the relationship to users. Content may otherwise seem unstructured or disorganised.
There are form fields that are not associated with their visual labels. The purpose of the form fields may be unclear to users.
Success Criteria : -
Any relationship presented through visual cues must also use the appropriate semantics. Make sure that form fields are associated with their visual labels. In this case, wrap the visual label such as “Please give us some more…”, “First name”, “Last name” and “Email address” within the element. For example:
<label for="i1"...>
<span ...>Please give us some more details to help us respond
<span...>Required

Avoid using multiple labelling techniques on the same form field. For example, using and aria-label together will cause the aria-label to overwrite the . As well, using aria-labelledby will overwrite any other labelling techniques.

Steps to reproduce :-
Observe the visual labels for the form fields.
Inspect the form fields and review the DOM.
Observe that the visual labels are not associated with the form fields.
Observe that there is not an alternative labelling method that serves the same purpose
Webchat Version :- 4.13.0
Link to raised Issue :-
There is an issue thread raised to Microsoft Bot framework - webchat Team and as per their Comments it is an adaptive card Issue.
Please check this link for detailed information :- https://github.com/microsoft/BotFramework-WebChat/issues/4468.

Would using associatedInputs in Action.Submit not work for this?

Hi @paulcam206 , @JeanRoca ,
please reopen this issue as workaround which you have given me as an input is not working as expected from accessibility point of view.
is it possible to use single associated id for label and form control instead of multiple ids ??
please recheck this link for more information provided by webchat team :- https://github.com/microsoft/BotFramework-WebChat/issues/4468

Hi @paulcam206 , @JeanRoca ,
please reopen this issue as workaround which you have given me as an input is not working as expected from accessibility point of view. is it possible to use single associated id for label and form control instead of multiple ids ?? please recheck this link for more information provided by webchat team :- microsoft/BotFramework-WebChat#4468

@Bradrajkumar which part is not working from an accessibility point of view? Please provide more details on this.
@anna-dingler FYI

@JeanRoca you can refer to https://github.com/microsoft/BotFramework-WebChat/issues/4468 on why the DOM tree is incorrect on accessibility perspective. Although this issue was originally filed to Web Chat repo, I repro-ed this bug on Adaptive Cards Designer.
For further information, please talk to the customer directly @Bradrajkumar.


Re-enable TaskResize test in CI

Testing the failing tests in local environment for #122  I found this test passes.  Trying it in CI.

interesting, I ran this specific tests a bunch of times locally but I will see if I can reproduce running in a loop locally.  I don't ability to re-trigger the jobs here so might do that on my branch as well.

I ran this single, specific test 100 times successfully. Will try a few more times and also try in CI with all the tests running incase its a issue when running with everything:
=== RUN   TestTaskResize
=== PAUSE TestTaskResize
=== CONT  TestTaskResize
--- PASS: TestTaskResize (1.10s)
ok      github.com/containerd/containerd/integration/client     2.704s
make integration completed successfully for 100 attempts.

I got it on the 190th run locally:
INFO[0000] start to pull seed image                      image="ghcr.io/containerd/busybox:1.32"
=== RUN   TestTaskResize
=== PAUSE TestTaskResize
=== CONT  TestTaskResize
    container_test.go:2357: failed to create shim task: ttrpc: closed: unknown

Needs more investigation, I tried it with the fix that went into ttrpc (https://github.com/containerd/ttrpc-rust/pull/208) but it didn't help. I've added a note to #122
/close


Ctrl+J and Ctrl+K navigation not working even with activation mode disabled

Describe the bug
Ctrl+J and Ctrl+K keybindings are doing nothing with activation mode disabled.
Version
0.10.3
Minimal Config
{
    "activation_mode": {
        "disabled": true
    }
}

To Reproduce

Disable activation mode with configuration shown above.
Launch Walker
Try to use Ctrl+J and Ctrl+K to go to next and previous entries

Expected behavior

Ctrl+J should navigate to the next entry
Ctrl+K should navigate to the previous entry

Screenshots
Moving with arrow keys:
https://github.com/user-attachments/assets/cab1a575-0aee-4054-8393-7a9a6a12177e
Trying to move with Ctrl+J and Ctrl+K (Nothing happens):
https://github.com/user-attachments/assets/76b86164-e82a-4f03-85b5-1f2191467703
Desktop

EndeavourOS
Hyprland

Additional context
config.json
This exact config was working fine before I updated Walker, and I don't see a reacon why it shouldn't work now.

That's because you need:
{
  "activation_mode": {
    "disabled": true
  },
  "list": {
    "keyboard_scroll_style": "vim"
  }
}

It defaults to emacs with ctrl+n/ctrl+p.


updated troposphere

Coverage remained the same at 39.511% when pulling 1e5b5116728ac984ddc4a6860a0cf079e8f317ef on akhon:master into 7840f8d5df003dba9943f218b95369ed5a8b485d on bninja:master.


[SPARK-46471][PS][TESTS][FOLLOWUPS] Reorganize OpsOnDiffFramesEnabledTests: Factor out test_arithmetic_chain_*

What changes were proposed in this pull request?
Factor out test_arithmetic_chain_*
Why are the changes needed?
for testing parallelism
Does this PR introduce any user-facing change?
no
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

ci link: https://github.com/zhengruifeng/spark/actions/runs/7286653712/job/19855868674

cc @HyukjinKwon @itholic

Merged to master.


Add console-operator CRD and generate from types

Following #475, generating the console-operator CRD.
/cc @spadgett @jhadvig
/cc @damemi looks like you owned review of the last one!
I do not have the line:
// +kubebuilder:validation:PreserveUnknownFields

So I am not sure why preserveUnknownFields: false is not in the YAML.
Todo after merge:

[ ] bump deps in console-operator and consume new manifest.

Mentioned this in pm, but for documentation preserveUnknownFields is not a validation generator field (it's only spec.preserveUnknownFields) and so it needs to be added manually since our generator only touches the openAPIV3Schema section of CRD yaml

// +kubebuilder:validation:PreserveUnknownFields

So I am not sure why preserveUnknownFields: false is not in the YAML.

This is only on a per-field basis, you still need the global preserveUnknownFields set to false b/c that allows the schema to be structural and that's one of the requirements to publish openapi.

Great, thanks!  Updated to include.

/lgtm

/cc @spadgett @bparees
care to approve?

/approve


Added page about IDE

@emmaxdan fixed all grammar mistakes and typos, should be ready to go, please have a look one last time


az commands always empty despite having VMs

Describe the bug
I've encountered a very strange issue where I can use az resource list to show all of my resources and it shows me a few VMs. However, when I use az vm list I always get an empty list [] returned to me regardless of the fact that there are VMs and I can access them via the web interface. I've tried specifying the resource group, running queries, and nothing seems to make a difference. I've also experienced similar issues with az network ... commands. Some commands do work like az storage account list, az account list, and az group list.
Here is a shot of az resource list with sensitive details blurred. We can see that there are multiple Microsoft.ClassicNetwork/virtualNetworks:

To Reproduce
az login
az account set --subscription <subscription_id>
az resource list
az vm list
Expected behavior
A JSON list of the VMs. One for each VM shown in the az resource list.
Environment summary
Using 2.0.32 Azure CLI on Mac. I also tried on Windows and got the same result. I also tried using the Azure Cloud Shell and got the same result.
Additional context
I have a contributor role, not an owner role. Not sure if this could be an issue, but based on the role permissions it seems like it should not be a factor.

Did you have default resource group defined through az configure? you can use --debug to cross check the request payload which was sent on the wire.

After digging in more and verifying that the behavior is the same even if I use Powershell, I finally found this documentation that seems to indicate that 'classic' resources can't be viewed via Powershell and, presumably, via the CLI either.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-deployment-model
Leaving here so that someone more familiar with the CLI can validate that this is indeed the issue and then happy for it to be closed out.

Yes, @billmccord this is the case for strongly-typed commands like VM and network.  They are using only the resource providers Microsoft.Compute, Microsoft.Network, Microsoft.Storage etc.

Let us know how to get the the values for VM Classic machines details in Azure CLI ?

For classic VMs, you can use CLI 1.0

i'm tried using azure cli  --version 0.10.14  and getting no vm listed .

I am having this same issue with the CLI.
az account list returns my subscriptions, but no other list command returns anything. Is there a solution to fix this? I have uninstalled and reinstalled the CLI even, but I'm getting the same issue. I have owner IAM control over all these resources as well.

@mgeorgebrown89 and others with this issue, try deleting your ~/.azure directory and run az login again.  (in my case I completely re-installed the az cli, but I think only removing the .azure dir may have been sufficient.)


covrpage

At this point my best guess is that there's a missing token, or that the GITHUB_TOKEN isn't set to be able to write, or something along those lines. The covrpage vignette about CI is still Travis-focused, so I'm not sure. And to make sure that part is clear, I can't see settings/secrets/etc for this repo, so I can't fix that part.

Covrpage works on gha. I’ll take care of it

@yonicd It still hasn't ran via GHA on this repo (the files that are here are from me running it on my laptop). It works on slackcalls and I can't see a difference in the repo that would cause the failure. Maybe it's a setting?


Upgrade ruby to 3.x.x

Why
New version for Ruby is out. We better update our Ruby to LTS version.
Who Benefits?
developers

note: Check if this issue is resolved
warning: parser/current is loading parser/ruby27, which recognizes2.7.5-compliant syntax, but you are running 2.7.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.

https://github.com/nimblehq/rails-templates/pull/307#issuecomment-1009567503

note: Check if this issue is resolved
warning: parser/current is loading parser/ruby27, which recognizes2.7.5-compliant syntax, but you are running 2.7.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.

#307 (comment)

For this issue, we need to set the parser to match a version of ruby as explained here -> https://github.com/whitequark/parser#backwards-compatibility

Parser does not use semantic versioning. Parser versions are structured as x.y.z.t, where x.y.z indicates the most recent supported Ruby release (support for every Ruby release that is chronologically earlier is implied), and t is a monotonically increasing number.

so we need to set it to 3.0.1.x. Done here ✅

Please check the issue where I can't upgrade to Ruby 3.1.0 on the PR description - https://github.com/nimblehq/rails-templates/pull/312#issue-1105663837
That needs some more work 💪

Created a new issue https://github.com/nimblehq/rails-templates/issues/316 to Upgrade Ruby to 3.1.x


Abstract MIMIC and create new random generation

close #8

@ebrahimebrahim I want to add doc strings/remove some debugging code, but the core code should be finished. Running the script overnight to make sure it works as expected.

This is great, I'll review soon!

@ebrahimebrahim ready for review. It seems the identifier tag isn't required and the tuple(value,system) doesn't have to be unique.

There seems to be a simple merge conflict with the main branch, can you resolve that?

@ebrahimebrahim ready for review. Feel free to review now or wait until I handle the date parsing changes.

@ebrahimebrahim ready for review. Feel free to review now or wait until I handle the date parsing changes.

Thanks! I'll wait for the date parsing changes to increase the chances of it being a final; lmk when those are ready.


Improve support for Rouge 1.x and 2.x

Improve support for Rouge 1.x and 2.x
This commit improves support for Rouge 1.x and adds support for Rouge 2.x.

Support for following options are introduced:

inline_theme (default: nil)
line_numbers (default: false)
start_line (default: 1)
wrap (default: false)

Support for HTMLLegacy, HTMLInline, HTMLLinewise, HTMLPygments, HTMLTable is introduced for Rouge 2.x

Changes Unknown when pulling 1e0090c7a08e834b152b085afb1b6162e7beb918 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling efaa344ef57b6059b904ecbcaec3a2d4863e518e on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling efaa344ef57b6059b904ecbcaec3a2d4863e518e on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 2cdf46309ef4f3d2519f3f8291b250fa7da4b532 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 2cdf46309ef4f3d2519f3f8291b250fa7da4b532 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 223de1ac2b0a83addbbe5d8ac002bde2eac385db on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 3d1c2236648766f734c4979e0b96310c872664e6 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 3d1c2236648766f734c4979e0b96310c872664e6 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 3d1c2236648766f734c4979e0b96310c872664e6 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 7f046935bb0ac91cf3744ade44f61c06bc06332c on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling f2083a93c4fda71a91f4640709f286e606fd8028 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling af37a8cf13e2d5af7e09c093ad37882407416a02 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling cce5817f8e88be66f0daa6ed8e35b59ea2f88f59 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling cce5817f8e88be66f0daa6ed8e35b59ea2f88f59 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling d62d579eb7e564aa59a7cb9ef0717319a387ba73 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 4376d2ea48c7ad2782f865f1b80e66a4183909bb on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 4376d2ea48c7ad2782f865f1b80e66a4183909bb on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 51c9e3b6e02232b2d7fa190bcf2981dbeb93114a on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 51c9e3b6e02232b2d7fa190bcf2981dbeb93114a on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling c6f3b1bf58803976c5f511f36044f4e720087c8b on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 31805a8bd8a8d796301ccb86a86f8e942c7cf486 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling b83e4d3e5b4d6551eec487549827f76dedf10bc8 on feature/improve-rouge-support into ** on master**.

Changes Unknown when pulling 66aa1978bcca71a7b600ff8bce4abe1261136ea3 on feature/improve-rouge-support into ** on master**.

Coverage increased (+0.04%) to 98.372% when pulling f693b569338852b6beb2e1d53c33ff1011a91683 on feature/improve-rouge-support into<PHONE_NUMBER>cf4b7b02f62a774989ac43d9d26454 on master.

Coverage increased (+0.04%) to 98.372% when pulling f693b569338852b6beb2e1d53c33ff1011a91683 on feature/improve-rouge-support into<PHONE_NUMBER>cf4b7b02f62a774989ac43d9d26454 on master.


remove jammerful

Description of changes
@jammerful has no contributions to GitHub since 2021-10-21.
Latest contribution to Nixpkgs was a review: https://github.com/NixOS/nixpkgs/pull/89288, version 3.1.5 of Gerrit (now  3.8.3).

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

@jammerful friendly ping

Merging this since @jammerful didn't respond for a week.


Slow inference on sphoradic stremaing data

I need to perform inference on streaming data of 1 row.
I need the inference to be fast.
When I inference a single row each time (I cannot inference a batch because the data arrives each row at a time). The inference time is relative high: ~10-40msec.
When i tried to test stand alone script, i get the first inferences slow (~10-40msec) and the rest are fast (~0.5msec). How can i achieve fast inference also for the first inferences?
The following sample code shows the problem:
X = [-2.0, 0.4, 14, 17, 67, 0.7, 393, 12.8, 81.5]
for _ in range(100):
start = time.time()
motion_predicted_class = self.xgboost_classification_model.predict(np.array(X).reshape(1, -1))[0]
t = np.round((time.time() - start)*1000, 1)
print(f'{t} msec')
output:
29.7 msec
40.1 msec
30.1 msec
40.2 msec
40.2 msec
14.8 msec
0.5 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec
0.4 msec

XGBoost is not particularly optimized for these types of usage. For low latency inference with streaming data, I would probably look into other libraries or create my own. There are dedicated inference frameworks out there.

I work for the rapidsai team, which has a tree inference library called FIL as part of cuml: https://medium.com/rapids-ai/rapids-forest-inference-library-prediction-at-100-million-rows-per-second-19558890bc35 it may or may not suite your need, but that's the general direction to look for (an inference optimized library).


Fixed the x/y/z plot script args error.

The x/y/z plot script have a new args format, so the example in README.md is out of date.  This change has led to the emergence of an error message:
list indices must be integers or slices, not str

For further information, please consult the following link: https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/11736

@mix1009 can we get this to merge?


WIP: Blackduck Importer v2 - License and Security Risk

Changes
Because Blackduck is designed to scan an application for the components it's importing and check them for vulnerable versions and license risks, I felt that a change to the resulting Findings to more closely align with that model was necessary.

Findings are either Security Risks or License Risks
Security risks contain details about the risks in the description, but the solutions/mitigation is to update to a secure version.
License risks are created based on the components csv and the description has details from the csv file about the license in use.
No longer require the source csv, instead the components csv is needed.
Does not support uploading a csv file by itself, it needs the zip file that contains both security and components csv.

Here is an example of how findings are displayed.

This is an example of a license risk finding and its description.

This is an example of the description of a Security risk finding and its description.
Looking for Feedback:
models.py
Because these findings don't contain a CWE, CVE, or Line number; as well as the fact that for each package, the FilePath being use is the same, each finding will be considered a "Similar Finding" with every other finding. This Similar Finding's function is defined in dojo/models.py. I have updated it to include a unique_id_from_tool to avoid this issue. Looking for feedback on this.
The name
Wasn't sure what else to call it besides V2. It ingests the same kind of report as the other Blackduck integration, but represents the findings much differently.
License Risk Severity
Currently I have it hardcoded to High. Not sure the best way to handle this, I don't want to decree that all license risks should be considered High for everyone.
To Test:
blackduck_hub_v2.zip
Zip file only contains necessary files and the ProjectPath is fictional.

Will certainly take a deeper look next week, I should have more time.
Glancing at it, looks OK to have a complete different v2 version until we could eventually deprecate the other one. And also to have someone like @Apipia who's apparently on the ball there for this :) (I don't use blackduck at all so).

Travis says chrome crashed during some selenium test.. how can I run travis again?

Closed and re-opened to trigger Travis again.

forms.py was not updated to have this new scanner show in the dropdown selection box. Was that intentional?

Also missing an addition to fixture test_type.json.

Also missing an addition to fixture test_type.json.

Should be good to go now. Lmk if you see anything else.

So I am still unsure on whether bending the current model to risk is a good thing.
If I understand correctly, the latest dev "version 1" of the Blackduck scanner now does all the vulnerabilities correctly, including backward compatible format and new format and this v2 does the same.
For clarity's sake, do you think we should rather decouple the vulnerabilities and risks in their own parsers? That would be leave the v1 parser as is, and your v2 (to be renamed) here would solely be dedicated to managing the risk part. Therefore, people interested in this part would know exactly what to look for and there is no surprise. I would probably be more in favor of that.
I am sure some people will like/need the risk part that you bring up, but the current defectdojo model is not necessarily suited for that. Maybe there needs to be a deeper discussion around the model if we ever want to integrate these kind of findings in the future.
@Maffooch thoughts?

I see where you're coming from but let me just take one more crack at this before we decide.
Blackduck is not a tool for scanning code for vulnerabilities like a static code analysis tool. A team would not purchase Blackduck to find SQL injection or any other code vulnerabilities. A team purchases Blackduck to scan builds and looks at the packages (components) that are imported and used to make sure that they are not at a version that has vulnerabilities, and that they do not have any license risk associated with them.
If Blackduck finds something, the mitigation is always to go and update the version (if its vulnerable) or find another component (if there is license risk). The "vulnerabilities" imported in version 1 of the blackduck importer are not vulnerabilities in your code, they're vulnerabilities in the packages/components that you are importing. The fact that Blackduck tells you what the vulnerabilities are in one of these vulnerable versions of a component is a kind of added bonus. Reporting those as findings, in my opinion, is a little misleading. It's not like you can fix those vulnerabilities (they exist in the code base of a component you're importing).
So version 1 says: "Hey you've got a few CVE's in your code, you need to fix those CVE's". My version 2 says: "Hey you've got a vulnerable version of a component (foo version 2.1.0) that has a few CVE's in it, you need to update that component."

A lot of tools will indeed focus on the OWASP A9, using components with known vulnerabilities.

So version 1 says: "Hey you've got a few CVE's in your code, you need to fix those CVE's". My version 2 says: "Hey you've got a vulnerable version of a component (foo version 2.1.0) that has a few CVE's in it, you need to update that component."

I would still create a finding per CVE as to comply with the current model as it stands, instead of having it all in the description field, only be it from a "data model" point of view. It will also make it harder (impossible?) for dedupe and harder for search. You can still aggregate these individual findings later to a component level for reporting needs. But I guess what you've tried to achieve here is to just give it another "view" in the end? If so, maybe there would be some other solution? (like a new view to pivot on data?)
(I also tried to ingest the v1 sample files, but none of them make the new parser happy -- just a note)

This looks good to me. I don't think it should be V2 parser unless both versions can be used reliably under a single parser. Seems like they are doing things slightly different anyways. The idea @madchap had for an extension of BlackDuck is probably the best way go.
The license issue is neat and definitely could be useful to those worried about that info. I don't see any huge differences in here that digress away from the finding model. Similar with the security risk finding, it be super cumbersome to have individual findings for each CVE found in a package. There is not a lot (if anything) to be done to fix those issues. Deduplication would not work here whatsoever though. I guess the tradeoff is either triage tons of CVE findings from the same package or not have deduplication.
I think scrapping deduplication would be the most practical since it would allow all new changes to be seen. Manually looking at all results is going to happen one way or other. Comes down to the lesser evil.

Alright, works for me. Only question I have then is what do we name this parser?
Blackduck Component and License Risk (bit of a mouthful)
Blackduck Component Risk?

I'll fix the merge conflicts once we know what it's called, since I'll have to change it all anyway.

BlackDuck Competent Risk sounds good. @madchap is all this cool with you?

I am cool with it ;-)

Bet. @Apipia you know what to do! I'll approve afterwards.

Merged in dev and some stuff caught fire so this may take some time. Hopefully I'll have this ready by tomorrow


首次安装失败

sudo make install
cd ./scripts && bash ./main.sh init_cfg
/usr/local/bin/docker-compose up -d
[+] Running 5/12
 ⠦ wk-nginx 7 layers [⣿⠀⠀⠀⠀⠀⠀]      0B/0B      Pulling                                                                                23.5s
   ✔ a378f10b3218 Already exists                                                                                0.0s
   ⠸ 4dfff0708538 Retrying in 9 seconds                                                                                21.3s
   ⠸ 2135e49ace4b Retrying in 9 seconds                                                                                21.3s
   ⠸ c843f6b280ce Retrying in 9 seconds                                                                                21.3s
   ⠸ 6f35ab6f1400 Waiting                                                                                21.3s
   ⠸ 6c538b49fa4a Waiting                                                                                21.3s
   ⠸ d57731fb9008 Waiting                                                                                21.3s
 ✘ wk-postgres Error                                                                                23.5s
 ✘ wk-outline Error                                                                                23.5s
 ✘ wk-oidc-server Error                                                                                23.5s
 ✘ wk-redis Error                                                                                23.5s
Error response from daemon: Head "https://registry-1.docker.io/v2/outlinewiki/outline/manifests/0.72.0-3": toomanyrequests: too many failed login attempts for username or IP address
make: *** [Makefile:9: start] Error 18

找到解决办法了。
https://forums.docker.com/t/unauthorized-incorrect-username-or-password/35677/28


[SelectField] Inconsistent coloring on focus

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

If you navigate to the Select element using the tab key it gets focused and both the underline and the input label gets colored.
If you select an option from the Select using the mouse or the keyboard after the element gets selected and it's value gets updated the Select remains in focus and both the underline and the input label remains colored.

Current Behavior
Switching to an Select is working as intended however if you select an option using the mouse or the keyboard only the underline remains colored, the input label loses the coloring.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/7yplykn0rq

Click on a Select element
From the menu select an option
When the select is updated with the newly selected option the coloring of the input label disappears

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.24

React
16.2.0

browser
Electron (Chrome 61.0.3163.100)

I just verified and it seems that on 1.0.0-beta.36 the issue is no longer present. Should I close the issue?

@LevTaylor I can confirm: https://codesandbox.io/s/2nyzp1j0n. Thank you for raising it!


error: failed to run custom build command for ffmpeg-sys-next v6.0.1

I'm trying to build a cargo with RUST but I always seem to get this error upon installing these ffmpeg crates
**error: failed to run custom build command for ffmpeg-sys-next v6.0.1
Caused by:
process didn't exit successfully: G:\Documents\ghwt-de-volatile-master\rust-ffmpeg\target\debug\build\ffmpeg-sys-next-633df82b3238d16e\build-script-build (exit code: 101)
--- stdout
Could not find ffmpeg with vcpkg: Could not find library in Vcpkg tree package ffmpeg is not installed for vcpkg triplet x64-windows
cargo:rerun-if-env-changed=LIBAVUTIL_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-pc-windows-msvc
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_pc_windows_msvc
cargo:rerun-if-env-changed=HOST_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-pc-windows-msvc
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_pc_windows_msvc
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-pc-windows-msvc
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_pc_windows_msvc
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-pc-windows-msvc
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_pc_windows_msvc
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: "pkg-config" "--libs" "--cflags" "libavutil" did not exit successfully: exit code: 1
error: could not find system library 'libavutil' required by the 'ffmpeg-sys-next' crate
--- stderr
Package libavutil was not found in the pkg-config search path.
Perhaps you should add the directory containing libavutil.pc'   to the PKG_CONFIG_PATH environment variable   No package 'libavutil' found   ', C:\Users\Diego\.cargo\registry\src\index.crates.io-6f17d22bba15001f\ffmpeg-sys-next-6.0.1\build.rs:715:14   note: run with RUST_BACKTRACE=1` environment variable to display a backtrace**
Can anybody help me with this issue? Thank you!

I had the same with libavfilter and libavdevice, turns out ffmpeg-sys-next 6.0.1 needs both of them, so the necessary packages to install are (exceprt from my devcontainer's Dockerfile):
RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
    && apt-get -y install --no-install-recommends \
    clang \
    libavcodec-dev \
    libavdevice-dev \
    libavfilter-dev \
    libavformat-dev \
    libavutil-dev \
    pkg-config

Hi, how to fix it in Windows?

try this: vcpkg install ffmpeg:x64-windows

I managed to fix it after 7 hours of work. What I did was using the GNU build guide found in the build wiki of this repo. Afterwards I:
installed vcpkg
ran vcpkg integrate install
ran: vcpkg install ffmpeg[core,avcodec,avformat,swscale,avdevice,avfilter] --triplet x64-windows --recurse
The avdevice component includes libavdevice, and the avfilter component includes libavfilter.
You should than get this error:
usr/include/libswresample/swresample.h is missing error (or something along these lines, it will appear at the bottom of the screen)
the file is located in this path (if you used the default download location for vcpkg) :
C:\Users\USERNAME\vcpkg\buildtrees\ffmpeg\src\n5.1.2-f31542651f.clean (libswresample will be one of the folders in here)
move it over to:
C:\Users\USERNAME\vcpkg\installed\x64-windows\include
run cargo build again and it should work just fine.


Minor improvements

Adds a preference to move the cursor to next node after selecting a candidate in the MS IME style (candidate after cursor). Since it is very possible that a user uses the left key to go backward to select a candidate, the new preference can help users to jump back to where he or she is from.
Notifies the users if they are selecting a duplicated phrase when using shift left/right.
Adds more unit tests.

A GitHub action file to do building and testing using Xcode 12 is also added.


Breakpoints unbound when debugging web extension on Insiders build

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version: 1.64.0-insider (user setup)
Commit: 7b9e5c32a053669d4e72f998e4fa217090c32f59
Date: 2021-12-22T05:15:28.225Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044
OS Version:
Microsoft Windows 10 Pro
10.0.19044 N/A Build 19044

Steps to Reproduce:

Open the helloworld-web-sample in Code Insiders.
Set a breakpoint on the console.log statement of the activate method
Launch the debugger

Expected behavior: debugger breaks at breakpoint
Actual behavior: debugger doesn't break at breakpoint. breakpoint greyed out and hover text reads "Unbound Breakpoint"

Can you please try out the nightly debugger and let me know if you experience the same issue there? I put in a fix earlier this iteration which may solve your case.

Nope, still broken.
More Info:
version v2022.1.717
Released on: 11/12/2019, 20:47:26
Last updated: 1/7/2022, 17:07:53
Identifier: ms-vscode.js-debug-nightly

/jsDebugLogs

Thanks this should be fixed on the next Insiders build with js-debug-nightly.

Still not working
Released on 11/12/2019, 20:47:26
Last updated 1/12/2022, 17:07:00
Identifier ms-vscode.js-debug-nightly

The next Insiders build has not yet been released

I'm sorry, I thought you meant it was fixed with the update to the debugger. I will test again when next insiders comes out

Just tested with latest insiders / JS Debug and it worked!
Insiders:
Version: 1.64.0-insider (user setup)
Commit: 0e435cf51d0e45293a94466fc3b1299ba70fa9b1
Date: 2022-01-13T21:33:48.622Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044
JS Debug Nightly:
Released on 11/12/2019, 20:47:26
Last updated 1/13/2022, 17:08:22
Identifier ms-vscode.js-debug-nightly

Thanks for confirming!


CDPS-956: Update document type for distinguishing mark images.

[x] Updated references to the PHYSICAL_IDENTIFIER_PICTURE document type to DISTINGUISHING_MARK_IMAGE to align with changing being made in the document management service (PR here).

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

Project coverage is 85.26%. Comparing base (24440cf) to head (06b2c2b).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #134   +/-   ##
=========================================
  Coverage     85.26%   85.26%
  Complexity      676      676
=========================================
  Files           103      103
  Lines          2165     2165
  Branches        202      202
=========================================
  Hits           1846     1846
  Misses          191      191
  Partials        128      128

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


chore: bdd-sbrp-import-1582924975 to 0.0.1

chore: Promote bdd-sbrp-import-1582924975 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


"Get set for our algorithm challenges" overview page does not progress. Link is broken.

Challenge Name
Get set for our algorithm challenges
Issue Description
This isn't a challenge, it is just the overview/instruction page for basic-algorithm-scripting. It loads page 1/4 but the "Go to my next step" button is broken so you cannot navigate to pages 2, 3, and 4. You have to just skip to the first challenge. That means you don't get that satisfying green checkbox on the map.
Tested with Chrome and IE

I think this might be a duplicate. I confirmed similar behavior on this bug that was reported a while ago:
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/10688

Closing as a duplicate of #10688. @jdbarras could you please let us know in that thread if clearing your browser cache solves the issue for you?

@ltegman not sure as it simply worked today without any action being taken. I don't know if clearing the cache would have worked yesterday though because when it didn't work on Chrome I tried it on IE, which I haven't ever used on codecamp with the same result.
In any case it's working now, thanks.


Prevent API failing on empty files

This patch fixes the problem that the REST docs include fields to upload
files foor the POST /api/events requests which will result in empty
fields being send when trying to schedule over which Opencast will
stumble and fall (500 Internal Server Error).
This patch makes the API ignore empty file fields in the
multipart/form-data request.
This fixes #3249
Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch
[x] include migration scripts and documentation, if appropriate
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

I think upload will also fail if there is no file extension later down the line (at least for tracks). Maybe this should also be a requirement [for some element types]?

That sounds reasonable, but I think that's a different issue and would also require a different response. I just ignore empty fields in here. But you wouldn't want to do that if you actually have a file. Either you would want to make it work with no file extension, or you would want the endpoint return a 400 bad request. Can you file an issue (or submit a patch) for that?


[BasicLocal UI Test], The chromosome region selection entry doesn't update counts

This is a manual UI test based on this template.
Please, always report a link to the template a UI test is about and also its ID in the title. This is useful to find test instances from the template. The best way to do that is copying this headline to every new instance. This template is reported at the end of the template.
Tests from the template that aren't mentioned hereby are intended as passed.
...
Select the example Yield-related Ara

[x] Check it matches qtl-search-form.png
[ ] In the Chromosome Region section, check that changing chromosome changes count

Fails: the count remains 0. Tested on ci-test too. I guess this is about recent changes I've seen in the past days. Did you do any test of such changes?
...

[ ] At the end, check the Javascript console

Fails: probably relate to the above issue, the Js console shows this:
init-utils.js:173 Uncaught TypeError: Cannot read properties of undefined (reading 'closest')
    at getChromosomeRegionIndex (init-utils.js:173:30)
    at findChromosomeGenes (data-utils.js:400:32)
    at HTMLInputElement.onfocus ((index):305:163)
    at Object.trigger (jquery-bstrap.min.js:32:39398)
    at HTMLInputElement.<anonymous> (jquery-bstrap.min.js:32:46735)
    at Function.each (jquery-bstrap.min.js:21:3035)
    at h.fn.init.each (jquery-bstrap.min.js:21:1000)
    at h.fn.init.trigger (jquery-bstrap.min.js:32:46710)
    at h.each.h.fn.<computed> [as focus] (jquery-bstrap.min.js:32:76078)
    at HTMLAnchorElement.<anonymous> (knet-selector.js:245:47)

Updated: Select the example Yield-related Ara

[ ]  Check it matches qtl-search-form.png
[ ] In the Chromosome Region section, check that changing chromosome changes count
[ ] Check add/remove chromosome regions

This is working now, thanks


SRO->Syl: Implement <U+166E CANADIAN SYLLABICS FULL STOP>!

Full-stops should be transliterated into full-stops!

[x] Write test
[x] Implement
[x] Document
[x] Refactor

Finished in 197c24b


Add bosh_cli gem to gemspec

Hi, from concourseci.slack.com conversation:
infrared [10:55 PM]
Looks like `bosh_cli` gem disappear after switching to alpine image. `gem install bosh_cli` line was removed from dockerfile and not added to gemfile. maybe i missed smth :thinking_face:
https://github.com/concourse/bosh-deployment-resource/commit/289d7e33babfb8800ea1e9d02cf4c11eec97e15c
https://github.com/concourse/concourse/commit/78597dffaf8809329f531563a119d40cdaa4bfff (edited)

jtarchie [11:05 PM]
@infrared, no it looks like it was meant to be in the gemspec, but isn’t — https://github.com/concourse/bosh-deployment-resource/blob/master/bosh_deployment_resource.gemspec#L17

 [11:05]
It is funny that the test pass, though.

[11:06]
We can fix this.

[11:07]
Though this is deprecated resource.

Thanks!

@Infra-Red Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Infra-Red Thank you for signing the Contributor License Agreement!

thanks!

thks :+1:
@vito we just stumble into this on concourse 3.6.0, do you plan to cut a new concourse bosh release soon ?

Not sure yet. Not for this fix anyway. I would recommend switching to the
cloudfoundry resource, this one is deprecated.
On Tue, Nov 14, 2017, 6:45 AM Pierre Oblin<EMAIL_ADDRESS>wrote:

thks 👍
@vito https://github.com/vito we just stumble into this on concourse
3.6.0, do you plan to cut a new concourse bosh release soon ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/concourse/bosh-deployment-resource/pull/49#issuecomment-344234120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHWOuIaPONt8DMFG-EStU5CRUCiPFmks5s2X1UgaJpZM4QX0ZB
.

@vito we started to migrate to the new bosh-deployment resource but we still have some v1 manifest. The new resource is not fully compliant with v1 manifest, see https://github.com/cloudfoundry/bosh-deployment-resource/issues/9. So it would be great to have a new concourse version including this fix.

Hi @vito, we upgraded our concourse to 3.6.0 and we also have an old big maintenance pipeline which we can not easily change and now it breaks because of this. Is there a possibility to cut a concourse patch version with this fix? Thanks

@o-orand @vito
A temporary solution which worked for us was to explicitly include the concourse bosh-deployment resource in pipeline's resource_types. This way it pulls and uses the latest docker image which contains the above fix instead of using the problematic packaged resource.
resource_types:
- name: bosh-deployment
  type: docker-image
  source:
    repository: concourse/bosh-deployment-resource
    tag: latest


Update About Us subpage: content + UX/UI

Design only as per two-column "About-Desktop" frame on Figma: https://www.figma.com/file/qbibGHgcV1LBcpvd2EoHSM/FindTheMasks?node-id=287%3A4547
Latest Content page 9-12
https://docs.google.com/document/d/1b9lj2j3vqJrZgqfozbZ2reSO6xnC_a00VtKO-xxUB7g/edit#

text sections indicated which should go on the right column
right column is region-specific

@linderr https://findthemasks-feature-ux-bpcxgf.herokuapp.com/whoweare

@ngottlieb this is sooooooooo much better!


How to set Stochastic Oscillator parameter cause the result will be the same as yahoo fiance

The Stochastic Oscillator method in most finance web call kd value (ex: yahoo finance) with parameter with 9 days.
I choose the same stock_id(2330.TW) in yahoo finance with one year period, the k value is 80.23
d value is 89.89, is really different from the ta library result
The default method in yahoo finance usually smooth the k, d value. below is the code that calculate kd value without smoothing,
Is any method to create the same result with yahoo finance?
import requests
import pandas as pd
from ta.momentum import StochasticOscillator

url = "http://api.finmindtrade.com/api/v3/data"
params = {
        'dataset':"TaiwanStockPrice",
        'stock_id':"2330",
        'date':"2019-06-14",
        "end_date":"2020-06-14",
        "user_id": "",
        "password": "",
    }
res = requests.get(url, verify=True, params=params)
ret = res.json()
base_data = pd.DataFrame( ret["data"])

kd = StochasticOscillator(
    high=base_data["max"],
    low=base_data["min"],
    close=base_data["close"],
    n=9, d_n=3
)

base_data["K"] = kd.stoch()
base_data["D"] = kd.stoch_signal()
print(base_data[["date", "K", "D"]])

           date           K          D
0    2019-06-14         NaN        NaN
1    2019-06-17         NaN        NaN
2    2019-06-18         NaN        NaN
3    2019-06-19         NaN        NaN
4    2019-06-20         NaN        NaN
..          ...         ...        ...
239  2020-06-08   96.551724  98.092999
240  2020-06-09  100.000000  98.092999
241  2020-06-10   95.588235  97.379986
242  2020-06-11   80.597015  92.061750
243  2020-06-12   64.516129  80.233793

Hi @machineCYC,
I am not familiarized with the way Yahoo calc the indicators.
StochasticOscillator implements exactly the calc described in https://school.stockcharts.com/doku.php?id=technical_indicators:stochastic_oscillator_fast_slow_and_full. Also, it has the tests developed using the example spreadsheet in the last link.
You can check the implementation of indicator, the test implementation and the input data.
Best,
Dario

Thanks , great information for me.
I check the kd value in yahoo finance,  it is a smoothing version kd value. formula is blew:
N = 3
RSVt is the same as kd.stoch() in ta library
Kt = ( 1－1/N ) Kt-ı + ( 1 / N ) RSVt
Dt  = ( 1－1/N) Dt-ı + ( 1 / N ) Kt
Maybe you can consider add this version kd in the library, it is useful for user
import requests
import pandas as pd
from ta.momentum import StochasticOscillator

url = "http://api.finmindtrade.com/api/v3/data"
params = {
        'dataset':"TaiwanStockPrice",
        'stock_id':"2330",
        'date':"2019-06-14",
        "end_date":"2020-06-14",
        "user_id": "",
        "password": "",
    }
res = requests.get(url, verify=True, params=params)
ret = res.json()
base_data = pd.DataFrame( ret["data"])

kd = StochasticOscillator(
    high=base_data["max"],
    low=base_data["min"],
    close=base_data["close"],
     n=self.kdays,
)
rsv_ = kd.stoch().fillna(50)

_k = np.zeros(base_data.shape[0])
_d = np.zeros(base_data.shape[0])
for i, r in enumerate(rsv_):
    if i == 0:
        _k[i] = 50
        _d[i] = 50
    else:
        _k[i] = _k[i-1] * 2 / 3 + r / 3
       _d[i] = _d[i-1] * 2 / 3 + _k[i] / 3

base_data["K"] = _k
base_data["D"] = _d
print(base_data[["date", "K", "D"]])

           date          K          D
0    2019-06-14  50.000000  50.000000
1    2019-06-17  50.000000  50.000000
2    2019-06-18  50.000000  50.000000
3    2019-06-19  50.000000  50.000000
4    2019-06-20  50.000000  50.000000
..          ...        ...        ...
239  2020-06-08  91.271136  81.063862
240  2020-06-09  94.180757  85.436160
241  2020-06-10  94.649916  88.507412
242  2020-06-11  89.965616  88.993480
243  2020-06-12  81.482454  86.48980

Hi! Just to you know:
I'm having the same issue here. It seems stoch() is not processing the stochastic as tradingview or others do. And it is only with stochastic, other indicators are returning correct data, so the problem must be on stoch()


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 3056 ms

Resolved: Samsung performance has improved in 1ffd0b8.


NSMgr v1.12.1-rc.1 causes latency spikes at certain traffic level

Question
Were there any modification in NSMgr between v1.11.2 and v1.12.1-rc.1 that can cause latency spikes?
Examples
In NSM v1.11.2 and before we managed to run traffic up to 30k TPS without spikes in latency, but with v1.12.1-rc.1 we observed significant latency spikes (up to 5 seconds) that caused disturbances and even disconnection of the SCTP peers.
To exclude the different NSM components we tried to run the same test with the previous release that worked well but added the components from the new RC one by one. When we used the forwarder-vpp from the RC and the other components from 1.11.2 the setup worked as expected, without latency spikes. The new forwarder-vpp and new registry-k8s combination also performed well, but when we added the NSMgr from the RC the latency spikes appeared.
So, it seems the NSMgr component has influence on this behavior.
Important to note that the mentioned latency spikes come periodically, in every two minutes, and this behavior starts when we reach 15k TPS traffic level.
Context

Kubernetes Version: 1.27.1
NSM v1.12.1-rc.1

In the meantime we repeated the tests with increased CPU resource limit for NSMgr pod and the latency spikes disappeared. It proves that something changed in NSMgr that causes higher CPU need periodically.

@glazychev-art, please find the logs attached.

cc @VitalyGushin


Investigate if viper maps env-id to ENVID or it also allows ENV_ID

As you can see by following logic in Viper's find function, it quite literally merges the EnvPrefix (we've set to kubecompose) with an underscore and then with the input to find (originally from GetString in our case), all made uppercase.
Because of this, whatever we pass to GetString will be the suffix of the env var it looks for. We are currently passing envid, which is why our env var is ENVID. If we want ENV_ID instead, we need to pass env_id to viper.GetString.


Evaluate transition to Angular 2 and TypeScript for UI.

As of right now, Angular 2 is still too prone to change without any reasonable notice. Because of this, we will await the first stable release before re-evaluating this path.


UsbDk not working in tiny11

When I the doesn't works. Or doesn't initialise

I suggest to take the issue with tiny11 maintainers


tfsec downloads are failing when a version is specified.

There are url typos in recent changes that are breaking tfsec downloads with this action. Just submitted #22 to help in getting this sorted since it currently fails a number of builds for us when invoking this action pointing at master.

We are also having this issue tfsec does not download when pointing to specific versions. Issue confirmed here too.

Confirmed

Fixed in #22


can you please push 4.1.0 to npm

current latest version is 3.10.0, it doesn't have some of the hooks such a cache

@sarkistlt, As noted in the docs  under Usage(https://feathers-plus.github.io/v1/feathers-hooks-common/#Usage), you can use it directly by installing the master branch repo.
Until its published on npm, you can get install v4.0.0 with "feathers-hooks-common": "git://github.com/feathers-plus/feathers-hooks-common.git#master" in package.json.

I see, thanks for pointing to the link


Implemented Infinity Scroll

Things Changed

Changed the whole system to use Redux instead of states
Load more images when viewing the last element
Added a spinner when the data is loading

Related Issue #5

Hey @theshubhagrwl, I looked into it and found that there is something wrong with the API. If you go to redditstatus.com, you will see there is an escalated number of errors with the APIs, which the Reddit team is trying to resolve. So I guess we have to wait till they resolve the issue.

Hey @theshubhagrwl, I looked into it and found that there is something wrong with the API. If you go to redditstatus.com, you will see there is an escalated number of errors with the APIs, which the Reddit team is trying to resolve. So I guess we have to wait till they resolve the issue.

Hi, I think your code is correct and for the part of the API, we cannot do anything.
I will approve this PR but I won't merge as this will break the app.
I will merge when Reddit guys will fix the issue.
Thanks for contributing 😃
the issue is still open if anyone wants to make any changes

Hey, I just check. Now the API is working without any problem so is the program. You can try it now.


Introduce --contract and --script to forc init

$ forc init --script -> create an empty script. Question: is a Rust test harness required with this?
$ forc init --contract -> create two Sway files: one for the ABI and one for its implementation. Also create a test harness populated with boilerplate code.
We could also do --predicate and --library.
The default should probably be a contract.

create an empty script. Question: is a Rust test harness required with this?

I would say yes. While we may choose to put simple script tests in the e2e test suite for our project, most users will only have the SDK for testing so might as well make it easy for them.
The sway test suite is a special use case, so deleting a bit of code that's not needed isn't a big deal; I'm already deleting the tests directory & cargo.toml at a minimum when setting up new test projects.

The library could be forc init --lib <name of lib> or forc init --library <name of lib>
library abi;

abi SomeName {
    fn some_action(parameter: type) -> bool {}
}

The current forc init would need to remove the Cargo.toml file and remove the Sway dependency in Forc.toml + remove the tests directory (all according to the docs) iirc, moreover remove the impl since it starts as a contract
The contract could be forc init <name of contract> or forc init --contract <name of contract>
contract;

use abi::SomeName;

impl SomeName for Contract {
    fn some_action(parameter: type) -> bool {
        // maybe do something with parameter here
        true
    }
}

Need to link the abi (library) in Forc.toml too and remove the default abi that it provides since it starts as a contract
The script could be forc init --script <name of script>
script;

use abi::SomeName;

fn main() -> bool {
    let caller = abi(SomeName, <contract address>);  // new contract syntax may be used instead, soon
    let success = caller.some_action(<some parameter>);

    success
}

Need to link the abi (library) in Forc.toml too and remove the default abi that it provides since it starts as a contract


Feature Request: Set system "global" node interpreter for scripts

Request:
have nvm update the system node aliases (for node and nvm) - such as /usr/local/bin/node to the currently selected version so that command line node scripts that use something like
#! /user/local/bin/node
would benefit from the selected node interpreter
TIA

Command line scripts should be run from a login shell, with a shebang like #!/usr/bin/env node, and they'll work just fine.
Mutating the system aliases is far beyond the scope of nvm.

Thanks for the info, that  is exactly what I need :-)
On Tue, Apr 11, 2017 at 4:50 PM, Jordan Harband<EMAIL_ADDRESS>wrote:

Command line scripts should be run from a login shell, with a shebang like #!/usr/bin/env
node, and they'll work just fine.
Mutating the system aliases is far beyond the scope of nvm.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/creationix/nvm/issues/1503#issuecomment-293395795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKIUWRg_dVbALIbiORWZ0iKmlaEc8h2Uks5ru-eXgaJpZM4M6VGV
.


PSP migration policy - Allowed Volume Types

From comment here, when 1.6.0 is released assuming support for https://github.com/kyverno/kyverno/pull/2543 is available, this policy becomes possible:
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: allowed-vols
spec:
  validationFailureAction: enforce
  background: false
  rules:
  - name: allowed-vols
    match:
      resources:
        kinds:
        - Pod
    preconditions:
      all:
      - key: "{{request.operation}}"
        operator: In
        value:
        - CREATE
        - UPDATE
      - key: "{{ request.object.spec.volumes[].keys(@)[] | length(@) }}"
        operator: GreaterThan
        value: 0
    validate:
      message: "Only emptyDir and projected volumes are allowed."
      deny:
        conditions:
          all:
          - key: "{{ request.object.spec.volumes[].keys(@)[] }}"
            operator: AnyNotIn
            value:
            - name
            - projected
            - emptyDir

With the recent updates to the upstream Pod Security Standards, the control which previously was a deny list has been inverted into an allow list thereby covering this policy. PR #241 contains this file here. Since the request in this issue is now effectively the same as how this updated PSS policy is written, it doesn't make sense to duplicate the rule/policy.


Go: invalid join for var, const, import list

Join of var, const list produces invalid code:
package main

func main() {
	var (
		one = 1
		two = 2
	)

	_, _ = one, two
}

Joining vars produces:
var (one = 1, two = 2)

that is invalid:
./main.go:4:20: syntax error: unexpected = in grouped declaration; possibly missing semicolon or newline or )

I think, better is do not join at all, leave code unmodified.

Same problem appears for imports:
import (
	_ "math"
	_ "net"
)

Joining does
import (_ "math", _ "net")

Go compiler errors:
main.go:3:17: expected ';', found ','

But if we insert ; instead of ,, code becomes valid:
import (_ "math"; _ "net")

Instead of this, what would be the correct way to group these declarations?
var (one = 1, two = 2)

Would it be this?
var one, two = 1, 2

I see more different cases now:

A type can be explicitly added, for example:var (
	one int = 1
	two int = 2
)

It can be joined to:var one, two int = 1, 2

But what if types are different?var (
	one int    = 1
	two string = "2"
)

There is no way to join it to an one-liner, the only possible is a two-liner:var one int = 1
var two string = "2"

Maybe you will accept this solution, but it doesn't look like join operation.
The same case is with value omitted:var (
	one int
	two int
)

becomesvar one, two int

But it doesn't work with different types:var (
	one int
	two string
)

Again, only a two-liner can be written.
Actually, it can be joined in common case, even with literals of different types:var one, two = 1, "2"

but only if there are no type definitions and there are values.

Also, seems like if we join list to comma-separated values, the split operation won't work symmetrically, it will produce:
var (
	one, two = 1, 2
)

Related to issue #201.

I think, the correct way to join is this:
var (one int = 1; two string = "2")

So the operation is fully reversible.

But it makes no big sense, I think

We can join to comma-separated list, if it's possible, otherwise, join with semicolon.
I think, that will be the best solution.

Yes, I completely agree with you, joining imports block to ;-separated values makes no sense, since gofmt will format it block back.
I'll check the fix later.

For history: main development was done and decisions were done in related issue.

I think we handled everything here in #201, so I'll go ahead and close it. Feel free to reopen if there's something related to imports I've missed.


Remove ExportPublicKey from crypto interface

This change makes exportability checks more idiomatic
and the interface a little less cluttered.
RELEASE_NOTES=n/a
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #1721 (33f34e2) into master (2d1b875) will decrease coverage by 0.02%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##           master    #1721      +/-   ##
==========================================
- Coverage   57.82%   57.80%   -0.02%
==========================================
  Files         195      195
  Lines        9151     9154       +3
==========================================
  Hits         5291     5291
- Misses       3256     3259       +3
  Partials      604      604

Impacted Files
Coverage Δ

internal/action/setup.go
17.20% <0.00%> (-0.45%)
:arrow_down:

internal/backend/crypto.go
70.83% <ø> (ø)

internal/backend/crypto/age/unsupported.go
0.00% <ø> (ø)

internal/store/leaf/recipients.go
39.23% <55.56%> (ø)

internal/store/leaf/crypto.go
37.70% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d1b875...33f34e2. Read the comment docs.

Codecov Report

Merging #1721 (33f34e2) into master (2d1b875) will decrease coverage by 0.02%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##           master    #1721      +/-   ##
==========================================
- Coverage   57.82%   57.80%   -0.02%
==========================================
  Files         195      195
  Lines        9151     9154       +3
==========================================
  Hits         5291     5291
- Misses       3256     3259       +3
  Partials      604      604

Impacted Files
Coverage Δ

internal/action/setup.go
17.20% <0.00%> (-0.45%)
:arrow_down:

internal/backend/crypto.go
70.83% <ø> (ø)

internal/backend/crypto/age/unsupported.go
0.00% <ø> (ø)

internal/store/leaf/recipients.go
39.23% <55.56%> (ø)

internal/store/leaf/crypto.go
37.70% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d1b875...33f34e2. Read the comment docs.


nginxparser can not work.

Traceback (most recent call last):
  File "/Users/jack/bin/script/vhost.py", line 39, in <module>
    init();
  File "/Users/jack/bin/script/vhost.py", line 18, in init
    getProjects(vhost_path);
  File "/Users/jack/bin/script/vhost.py", line 32, in getProjects
    getProjectInfo(dirpath + "/" + filename)
  File "/Users/jack/bin/script/vhost.py", line 37, in getProjectInfo
    print load(open(file_path, "r"))
  File "build/bdist.macosx-10.10-intel/egg/nginxparser/__init__.py", line 98, in load
  File "build/bdist.macosx-10.10-intel/egg/nginxparser/__init__.py", line 94, in loads
  File "build/bdist.macosx-10.10-intel/egg/nginxparser/__init__.py", line 45, in as_list
  File "build/bdist.macosx-10.10-intel/egg/nginxparser/__init__.py", line 39, in parse
  File "/usr/local/lib/python2.7/site-packages/pyparsing.py", line 1125, in parseString
    raise exc
pyparsing.ParseException: Expected "}" (at char 219), (line:9, col:33)

throw parse exception.

config file valid is not.


Consider changing the wording on the character importer

In the import tool, several modules are named as "strongly recommended for best results", especially under the 'Active Effect Options' header. This often confuses new users of the dnd5e system, as they (1) don't know what Active Effects actually are (often confusing them with animations), and they (2) are not made aware that this is for 'best results' only if one is seeking high automation; they then install most, if not all, of these modules believing them to be required for best results of using the import tool, rather than for the added benefit that they may not be at all interested in.
Please consider changing the wording to make it more explicit that none of these modules are in fact required, needed, or provide any benefit, unless one actively wants to delve into the same high automation that the relevant modules provide.

Admittedly a bit surprised that this hasn't even gotten a sideways glance in 3 weeks for what should be a 2-minute change. The request is simply to inform users about what they are being encouraged to install, and why.

I did tweak the wording @krbz999 , but forgot to link back to this request. https://github.com/MrPrimate/ddb-importer/commit/f81f7e73337ecc1b00195e04b157a82894b728e8
If you wish to change it further for your own understanding of the issue, then please submit a PR. I know you know how.

Done.


Qualify bokeh OverlayPlot legend style_opts

Avoids the confusion in https://github.com/ioam/holoviews/issues/1785 by qualifying border line options with the border_ prefix.

Ready to merge.

Looks good and the tests are passing. Merging.


chore: fix typo in comment

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)

friendly ping~