issue with TMT modifications & OMSSA

Hi there,
I wanted to use Ursgal to search TMT modifications on any Ntermini and as fixed modification on K.
I adapted the all_mods as follows:
    'K,fix,any,TMT6plex',
    '*,opt,N-term,TMT6plex',

But I get this error when Ursgal starts OMSSA (it works with most of the other search engines):
[ WARNING  ]
The combination of modification name and aminoacid is not supported by
OMSSA. Continuing without modification: {'id': '737', 'org': 'K,fix,any,TMT6plex', 'name': 'TMT6plex', 'composition': {'O': 2, 'N': 1, '15N': 1, '13C': 4, 'C': 8, 'H': 20}, 'mass': 229.162932, 'unimod': True, 'aa': 'K', '_id': 3, 'pos': 'any'}
[ WARNING  ]
The combination of modification name and aminoacid is not supported by
OMSSA. Continuing without modification: {'id': '737', 'org': ',opt,N-term,TMT6plex', 'name': 'TMT6plex', 'composition': {'O': 2, 'N': 1, '15N': 1, '13C': 4, 'C': 8, 'H': 20}, 'mass': 229.162932, 'unimod': True, 'aa': '', '_id': 0, 'pos': 'N-term'}
If I look in the OMSSA mods.xml file, TMT is there but has slightly different names:
<MSModSpec_name>TMT 6-plex on n-term peptide</MSModSpec_name>
<MSModSpec_name>TMT 6-plex on K</MSModSpec_name>
Any help gratefully received!
Toby

Thanks for using Ursgal :)
I will have a look tomorrow, there may be a quick workaround.
Cheers,
JL

I have changed the code to correctly map these mods for OMSSA.
Could you please check if it works now? Thanks!
A good reference would be the overlap of peptides to the other engines i think.
Cheers,
JL

Hi, erm I pulled the new repo but I still get the error. [ WARNING  ]
The combination of modification name and aminoacid is not supported by
OMSSA. Continuing without modification: {'composition': {'15N': 1, 'N': 1, 'C': 8, '13C': 4, 'O': 2, 'H': 20}, 'id': '737', 'mass': 229.162932, 'unimod': True, 'org': 'K,fix,any,TMT6plex', 'pos': 'any', '_id': 3, 'aa': 'K', 'name': 'TMT6plex'}
[ WARNING  ]
The combination of modification name and aminoacid is not supported by
OMSSA. Continuing without modification: {'composition': {'15N': 1, 'N': 1, 'C': 8, '13C': 4, 'O': 2, 'H': 20}, 'id': '737', 'mass': 229.162932, 'unimod': True, 'org': ',opt,N-term,TMT6plex', 'pos': 'N-term', '_id': 0, 'aa': '', 'name': 'TMT6plex'}
am I doing something wrong? Thanks for your quick response!

Hi,
I tried it with the newest version on samples without TMT labeling, so no idents for that, but I didn't get the error/warning, so for me it seems like it works.
Have you installed ursgal in the python site-packages? If yes, you need to run 'python setup.py install' after pulling the new version ...

ah ha, I re installed as instructed and it seems to run without the warning. Will let you know if successful. Thanks for the help so far!

Does this work now? Can this be closed?

Yes, Ursgal now works for TMT with OMSSA. It can be closed. Thanks for your
help
Toby
On 23 March 2017 at 09:36, Johannes Leufken<EMAIL_ADDRESS>wrote:

Does this work now? Can this be closed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ursgal/ursgal/issues/17#issuecomment-288650672, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJy7hCkXGMEbii4CMI7r3zwZV8vXg6Dlks5roi76gaJpZM4MVqxX
.


Usage without repository scope

Hello,
is it possible to use the action without mentioning a repository so that the token is valid for multiple repositories the app has permissions to?
I get the following error:

Best regards,
Markus

Okay if i understood correctly it is not "scoping" the individual token permissions. But what is it used then for?
Fixed the problem by giving the app permissions to the default (starting repository).

Hey Markus, you seemed to have resolved your issue on your own. Can we close this?


fix order status

Fix order status event parameters

@mfrener @Tsopic - I know it's probably night-time at your ends, so I'll just merge this tiny PR, all checks have passed successfully, please have a look when you're up if there's an issue


Add initial dockerfile for Hawkular BTM server

Not published to docker hub yet - need to find out who to talk to about that.

That would be me ;)

@goldmann Ok good to know. Once the PR has been reviewed (I guess by someone on the hawkular team), I'll ping you.

@goldmann should be ready to publish to dockerhub - let me know if you need any further info. Thanks.

Done, a tagged version will be triggered when the repo will be tagged.

Forgot to add the link: https://hub.docker.com/r/jboss/hawkular-btm/

@goldmann thanks


bStats doesn't appear to work this is what I get in console:

[09:19:15] [bStats-Metrics/INFO]: [KPManager] Sent bStats metrics data: {"playerAmount":1,"onlineMode":1,"bukkitVersion":"REMOVED-IT (MC: 1.19.3)","bukkitName":"CraftBukkit","javaVersion":"17.0.2","osName":"Linux","osArch":"aarch64","osVersion":"5.15.0-1027-oracle","coreCount":4,"service":{"pluginVersion":"v1.8","id":17490,"customCharts":[]},"serverUUID":"REMOVED-IT","metricsVersion":"3.0.0"} [09:19:15] [bStats-Metrics/WARN]: [KPManager] Could not submit bStats metrics data java.io.IOException: Server returned HTTP response code: 429 for URL: https://bStats.org/api/v2/data/bukkit 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1997) ~[?:?] 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589) ~[?:?] 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?] 	at in.rs.milivojevic.KPManager.utils.Metrics$MetricsBase.sendData(Metrics.java:329) ~[?:?] 	at in.rs.milivojevic.KPManager.utils.Metrics$MetricsBase.lambda$submitData$4(Metrics.java:298) ~[?:?] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?] 	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?] 	at java.lang.Thread.run(Thread.java:833) ~[?:?] 	[09:25:36] [Spigot Metrics Thread/INFO]: [Metrics] Received fatal alert: internal_error

Hey, 429 just means that your plugin got ratelimited for sending data too often. This is very common (especially after a server start) and not a bug. See https://github.com/Bastian/bstats-metrics/issues/86


Minimal UI5 project throws multiple errors

OpenUI5 version: 1.124.1
Browser/version (+device/version): Chrome + Safari (latest) on macOS
Any other tested browsers/devices(OK/FAIL): FAIL
Steps to reproduce the problem:

Create this index.html and open it in a browser:

<!DOCTYPE html>
<html>
<head>
	<meta http-equiv="X-UA-Compatible" content="IE=edge" />
	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
	<title>Bookshop</title>
	<script>
		window["sap-ushell-config"] = {
			defaultRenderer: "fiori2",
			applications: {}
		};
	</script>
	<script id="sap-ushell-bootstrap"
		src="https://sapui5.hana.ondemand.com/test-resources/sap/ushell/bootstrap/sandbox.js"></script>
	<script id="sap-ui-bootstrap" src="https://sapui5.hana.ondemand.com/resources/sap-ui-core.js"
		data-sap-ui-libs="sap.m, sap.ushell, sap.collaboration, sap.ui.layout"
                data-sap-ui-compatVersion="edge"
		data-sap-ui-async="true"
                data-sap-ui-preload="async"
                data-sap-ui-theme="sap_horizon"
		data-sap-ui-frameOptions="allow"></script>
	<script>
		sap.ui.getCore().attachInit(async () => (await sap.ushell.Container.createRenderer("fiori2", true)).placeAt("content"));
	</script>
</head>
<body class="sapUiBody" id="content"></body>
</html>

What is the expected result?
There are zero errors for this single-line-of-code app.
What happens instead?
There are multiple errors thrown by the library:

Log-dbg.js:499 2024-06-17 10:31:43.442000 [FUTURE FATAL] The registered Event Listener 'init' must not have a return value. - __renderer0---Shell-home-component. This seems similar to https://github.com/SAP/openui5/issues/4014 and you get it when creating the basic async renderer as I do above. I don't register any 'init' event handler myself, so I'm not able to fix this error.
Defining the object type ('sap.m.PageAccessibleLandmarkInfo') via its string name is deprecated, since it leads to accesses to the global namespace. The object type either stems from an explicitly given 'Type' value or was inferred from the default aggregation type. Please require the respective object type module beforehand. For control development, please also refer to the runtime metadata property 'defaultClass', which allows you to specify a default aggregation class type via constructor reference.. As I'm not defining any sap.m.PageAccessibleLandmarkInfo this also seems to be faulty library coding.
The font configuration for collection 'Fiori2' is not registered
Also, the eager requests to /sap/es/ina/GetServerInfo and /sap/opu/odata/sap/ESH_SEARCH_SRV/ServerInfos?$expand=Services/Capabilities fail for new projects, unless those endpoints are set up in the backend. Imho that practice should be rethought. It's just not a good look to spam the developer console with errors for empty UI5 projects.
Similarly, the missing fioriSandboxConfig.json throws multiple errors. Why isn't there a default coming with the sandbox.js I pull from the CDN?

I think the only acceptable number of errors for such a minimal app is zero. This currently introduces a broken window effect for every new UI5 app from the beginning.
Any other information? (attach screenshot if possible)

Hi @swaldmann, sap.ushell is not part of SAPUI5. Please create an incident in the SAP internal support system.


Remove rust-toolchain.toml And Control MSRV From CI Instead

Resolves #57
This was the simplest solution I could find.
There's a repository called actions-rs that can be used for toolchain management in Github CI (among other things, I'm sure).
However, looking into that would take more time than I'm looking to spend right now.
We should also consider adding stable to the CI process as well. Currently we have some warnings that are emitted on stable that are not present on 1.63.0.

Right. rustfmt and clippy never get installed now.
One moment.


Added 'Hello World' in Azerbaijani(AZ)

I added the hello world in azerbaijani and turkish language.

a53bda6b74ee6dc97ac171233c972b6d4b9b7b924d2f3f8d300093f1ed8a4c8b

ISO: correct
Translation: correct
Approved

@Kenan7 Coins sent!

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?


Installing from yum repo fails repomd.xml signature could not be verified for couchdb

Description
Attempting to follow Installation using the Apache CouchDB convenience binary packages on a RedHat/CentOS system fails to install the package
i am facing this issue couchdb is failing due to below error
Steps to Reproduce
yum install -y yum-utils
yum-config-manager --add-repo https://couchdb.apache.org/repo/couchdb.repo
yum install -y couchdb
Expected Behaviour
CouchDB is installed from an RPM downloaded from the repository.
Your Environment
Operating system and version: CentOS 7.9
Additional Context
Full output from commands:
[root@45ae2b263cc5 /]# yum install -y yum-utils
Loaded plugins: ovl
There are no enabled repos.
Run "yum repolist all" to see the repos you have.
To enable Red Hat Subscription Management repositories:
subscription-manager repos --enable
To enable custom repositories:
yum-config-manager --enable
[root@45ae2b263cc5 /]# yum-config-manager --add-repo https://couchdb.apache.org/repo/couchdb.repo
Loaded plugins: ovl
adding repo from: https://couchdb.apache.org/repo/couchdb.repo
grabbing file https://couchdb.apache.org/repo/couchdb.repo to /etc/yum.repos.d/couchdb.repo
repo saved to /etc/yum.repos.d/couchdb.repo
[root@45ae2b263cc5 /]# cat /etc/yum.repos.d/couchdb.repo
[couchdb]
name=couchdb
baseurl=https://apache.jfrog.io/artifactory/couchdb-rpm/el$releasever/$basearch/
gpgkey=https://couchdb.apache.org/repo/keys.asc https://couchdb.apache.org/repo/rpm-package-key.asc
gpgcheck=1
repo_gpgcheck=1
enabled=1
[root@45ae2b263cc5 /]# yum install -y couchdb
Loaded plugins: ovl
https://apache.jfrog.io/artifactory/couchdb-rpm/el7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
etrieving key from https://couchdb.apache.org/repo/keys.asc
Importing GPG key 0x7A00258D:
Userid     : "The Apache Software Foundation (Package repository signing key<EMAIL_ADDRESS>Fingerprint: 390e f70b b1ea 12b2 7739 6295 0ee6 2fb3 7a00 258d
From       : https://couchdb.apache.org/repo/keys.asc
Is this ok [y/N]: y
Retrieving key from https://couchdb.apache.org/repo/rpm-package-key.asc
couchdb/7/x86_64/signature                                                                                |  11 kB  00:00:03
https://apache.jfrog.io/artifactory/couchdb-rpm/el7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for couchdb
Trying other mirror.
One of the configured repositories failed (couchdb),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=couchdb ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable couchdb
    or
        subscription-manager repos --disable=couchdb

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=couchdb.skip_if_unavailable=true

failure: repodata/repomd.xml from couchdb: [Errno 256] No more mirrors to try.
https://apache.jfrog.io/artifactory/couchdb-rpm/el7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for couchdb

See https://github.com/apache/couchdb/issues/5010 . All the apache jfrog repositories are down since friday.

All should work again!


Undefined local variable or method `deserialized_params'

After 4eb7951b4851170e0a948781dcc029f4bc7d530e the #render_errors_for no longer works.
Please take a look.

Hi @stas upgrade to the latest version of jsonapi_suite and it should work. Please bear with us while we solidify things for 1.0

Actually, I'm using this package standalone. I tried to understand why this dependency was introduced and went back keeping the v0.1.1 instead.
Feel free to close the ticket if you think it's not relevant anymore.

I'm also seeing this error. How is deserialized_params suppose to be defined?


Metadata Catalogue - Git Hosting

As a user I want to be able to get to the metadata catalog website.
Note, at this point the metadata catalogue will be a simple online STAC editor for editing LINZ STAC extensions. It will simply have the options to create or upload a STAC record. Capture the fields required, and for the user to copy or download the records. This is a simple, stateless, online utility, that exposes no secrets and should not require any security.
Tasks:

[ ] Create Git website for static STAC editor

Definition of done:

[ ] Going to the git pages URL of the LINZ STAC editor will show the editor on any browser supported by Flutter (most current browsers)

Issue moved to linz/ds-infra-team #885 via ZenHub


Executable files for windows

How did you get the executables for windows? Do I understand correctly that they are not built with py2exe?
And one more question. Why didn't the executables ask for additional DLL packages? Did you build them into the exe or use any libraries when building the exe file?

No, executables are build with pyinstaller. Yes, separate DLLs only make more noise in EDRs so I left them out.

Can I know which DLL files you included in the project? I was getting confused at this step.


June and July Blog Analytics

@Maroyafaied
July analytics are up on the Blog wiki: https://github.com/ONRR/blog-nrrd/wiki/Analytics
You can use this linked excel sheet to review.

@cthomasONRR I'm not able to access the spreadsheet

@Maroyafaied Thought I already shared it with you. You should have access now and here's the link again (I moved the file location so not sure if that messed up the link).

@cthomasONRR looks great, everything matches! Thanks.


Stack View button has illogical sequence for screen readers

Describe the bug
The interstitial content in the stack view presents an illogical reading sequence for screen reader users. When screen reader users hear a button announce an expanded or collapsed state they will think that the button controls the readability of upcoming content.
Discovering content related to the stack-block-label button immediately after hearing that it is in a collapsed state may be confusing. While this is a low severity issue when there is a small amount of interstitial content, the severity will increase in relation to the amount of interstitial content.
How to reproduce
https://stackblitz.com/github/clane/clarityTest2/tree/master/clarity-test-app
Steps to reproduce the behavior:

Using a screen reader go to Stackview example
Read one of the collapsed stack-block-label buttons
Observe that you read the value of the stack's key value pair immediately after reading the collapsed button.

Expected behavior
The Stack view's implementation should combine the stack-block-label and the interstitial content in the first stack-block-content element into a single control, specifically a button. The stack's key value pair can be used to provide an accessible name and description for this button. This can be done with aria-label or aria-labelledby and aria-describedby.
Versions
App

Angular: [e.g. 6]
Node: [e.g. 8.10.0]
Clarity: [e.g. 0.12.5]

Device:

Type: [e.g. MacBook]
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional notes
Add any other notes about the problem here.

When we last met in Palo Alto we decided to concatenate the key and and value and use the resulting string as the accessible name. Then we would advice consumers to use short values to prevent abnormally long button names with documentation.

I apparently linked this from the wrong PR.
Setting the pipeline accordingly.

Additionally,  a low vision user using zoom or magnification functionality may not be able to visually perceive the toggling effect of the stack view button because of the interstitial content filling the viewport.

@Jinnie
Is this effort complete?

Need to verify if this was fixed fully

Fix verified on https://clarity.design/documentation/stack-view


[Feature] [Documentation] Document state and status fields

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
RayCluster state and status fields should be documented.
Context:
https://ray-distributed.slack.com/archives/C02GFQ82JPM/p1660150063061029
Use case
State/status fields could be useful for users and for external systems managing RayClusters.
The meanings should be clearly documented (once the state and status fields are stable and we have a clear consensus on the meanings).
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

/cc  @scarlet25151 is the feature owner. Please help update the docs.


URI's being treated as labels

Somehow a couple of URI's are being mistaken for labels.
Currently, our output is inconsistent and looks like this:
bf:expressionOf https://trellis.sinopia.io/repository/washington/b7ef5c30-4e4c-459c-8361-2c371359894f; or
bf:expressionOf [ a bf:Work ;
rdfs:label "https://trellis.sinopia.io/repository/washington/0a4ea663-988e-474b-a25e-659b935b65a9" ],
[ a bf:Work.subclass ;
rdfs:label "https://trellis.sinopia.io/repository/washington/0a4ea663-988e-474b-a25e-659b935b65a9" ] ;
bf:relatedTo has the same issue with URIs being listed as labels. I'm not sure whether we need to fix this or if it's a Sinopia issue.

@briesenberg07 Crud, for the properties also in our sinopia application profiles in AdminMetadata, we're outputting bad BIBFRAME. We only did it correctly for bf:status. We need to fix these. I don't know where our profiles are living right now or where the AdminMetadata profile is, but if you point me in the right direction I can fix this problem and future source data won't look this way (at least for the data that starts out as BIBFRAME).

@CECSpecialistI I believe that the place to fix it, if you wanted to fix it at this point, would be in the source profile, as this is processed to output the AdminMetadata profile that is actually loaded into Sinopia.
BUT WAIT! No, none of this applies anymore! There is no more loading JSON profiles to Sinopia! There are no more profiles in Sinopia, period--only resource templates!
I'd think that your best bet would be to wait until the UW RTs have been converted to the new RDF format on production and then edit them there (in the Linked-Data Editor itself, which will now be the graphical editing interface for RTs).
More long-term, I hope to output new Sinopia RDF RTs from an updated source. So we would want to make sure that the proper structure was input for BIBFRAME adminMetadata/AdminMetadata/etc. in this new source.

That makes sense. We still have a problem with the properties outside of AdminMetadata, but we can wait on the AdminMetadata properties until we can edit the input forms themselves (unless it's super easy to fix the data! because if it is, and we're adding this data to sinopia, we should probably clean the data in addition to fixing the original problem with the resource templates)?

(unless it's super easy to fix the data! because if it is, and we're adding this data to sinopia, we should probably clean the data in addition to fixing the original problem with the resource templates)?

I don't think we've seriously considered cleaning our RDA/RDF. We've considered it as experimental data, and going forward it may be considered as "legacy data." If we were close to loading converted BF into the Sinopia backend, perhaps this would change and we would consider some data cleanup? But I don't think it would be super easy.
As has been discussed, there are a few things between now and loading converted BF into Sinopia:

Further refinement of RML conversion
Alignment of output BF with stable Sinopia RTs
Establishment of a workflow for loading triples into mongoDB en masse

With new resource templates for creating RDA/RDF in Sinopia, the data created with these will benefit from all of the above steps, could begin flowing back into Sinopia, and might be considered as something more than experimental...

bf:descriptionLanguage and bf:source values should be bnodes with values of bf:Language and bf:Source, like this:

@CECSpecialistI I don't understand what you're saying that AdminMetadata output should look like based on your snippet above. Seems like it got a little garbled somehow, maybe from copy/paste? Is it supposed to be RDF/XML?
Also, I don't understand how the value for bf:descriptionLanguage would be a bnode since given the snippet
bf:descriptionLanguage
<bf:Language rdf:about="http://id.loc.gov/vocabulary/languages/eng">
bf:codeeng</bf:code>
</bf:Language>
</bf:descriptionLanguage>

I may be reading this incorrectly, but my best interpretation is that this is RDF/XML making two statements on a given IRI, http://id.loc.gov/vocabulary/languages/eng:

It has rdf:type bf:Language
It has bf:code value "eng" (looks like maybe some copy/paste garbling here)

Please clarify what you think the output should look like--thank you!

instanceOfBf:AdminMetadata bf:descriptionLanguage https://id.loc.gov/vocabulary/languages/eng
--or, in RDF/XML:
<rdf:Description rdf:node="AdminMetadataNode">
<bf:descriptionLanguage rdf:resource="https://id.loc.gov/vocabulary/languages/eng"/>
...is correct. No type bf:Language is needed due to direct IRI entry.
Does that make sense?
So I think this is not a problem issue.
However if IRIs are being output as literals (as in the expressionOf example) that leads to problems, as we have one way of processing the RDA input if the value is a literal and another if the value is an IRI. I suspect the problem is in the input RDA data. We'll need to look at that. I'll be on the watch for that. All triples I've seen with http://expression-as-bf-Work bf:expressionOf http://rdaWork-as-bf-Work have had IRI values as the triple's object.

ack you guys are right about language

Updated the issue to only include the one thing we need to watch.

I wrote up a simple script (fix_URIs.py) that can fix URIs that have been entered as literals by mistake! It basically just goes through the RDFXML looking for this:
<(property)>(literal beginning with "http")</(property)>
and replaces it with this:
<(property) rdf:resource=(that same literal now as a URI)/>
With that all fixed, the output BF will be fixed, too.
The only issue: are there any instances in our data where a URI is supposed to be a literal? If not, this script is good to go, but if so, I'll need to make some exceptions.

Need to take a closer look at this...
I knew that Sinopia was generating URI labels for URIs
<> <property> <uriValue01>
[...]
<uriValue01> <rdfs:label> "http://uriValue01.com"

But I wasn't aware that the URIs-as-literals were actually ending up in the object position, like...
<> <property> "http://uriValue01.com"

Issue is with original RDA, not with RML mapping. Currently resolved by fix_URIs.py.


Prevent double counting of goals

Put some protection in to ensure two people don't record the same goal

Options:

have to send the current score with any attempt to record a goal. If the prev- sent is different then reject
min time between goals for the same scorer (i.e. next goal has to be at least x seconds)

Or all of the above


Add baconian cipher

Same as https://github.com/TheAlgorithms/JavaScript/pull/1416. Review of that PR will decide whether we accept it here (as long as the types are valid, of course).

Same as TheAlgorithms/JavaScript#1416. Review of that PR will decide whether we accept it here (as long as the types are valid, of course).

That should have been a question for this PR: https://github.com/TheAlgorithms/Python/pull/5251
I saw the algorithm is already in the site in Python and though about adding the JS version :)
I think this one is useful because someone studying ciphers might want to see the implementation in JavaScript.

Same as TheAlgorithms/JavaScript#1416. Review of that PR will decide whether we accept it here (as long as the types are valid, of course).

I suppose this one has to be closed as the other PR was not accepted.


parser: support cast as bigint

What problem does this PR solve?
Support cast(xxx as bigint) or cast(xxx as int)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ci: Add CodeQL Analysis Workflow

Description
This change introduces a CodeQL Analysis workflow to enhance the security and code quality of the project. The workflow is configured to run on push and pull request events for the main branch, as well as on a weekly schedule (every Sunday at 1:30 AM UTC).
This addition will help identify potential vulnerabilities and code quality issues automatically, improving the overall security posture of the project.
fixes #44

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

#37
#36
#35  👈
#34
#33
#32
main

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

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Sep 25, 5:07 PM EDT: @JackPlowman merged this pull request with Graphite.


How to use webed in existing app?

Looks like a great CMS and exactly what i'm looking for!
However when trying to integrate this cms in my existing (fairly large) app, i'm running into a few problems.
When publishing (resource) assets, following errors occur:
Can't locate path: </Users/barry/Sites/webedtestproject/vendor/sgsoft-studio/shortcode/src/Providers/../../resources/root>
(many times)
I'm also encountering the problem that i already have a users-table.
Is it possible to have 2 user-tables (users for my 'main' app and we_users for the webed-cms) and how to implement this in Auth.php?
(when i change the web login model in config/auth.php to WebEd\Base\Users\Models\User::class, the webed cms-part is working, except for the missing texts/labels, but my main app isn't working anymore because it's searching users in the wrong table)
I also tried to derive my 'normal' User model from WebEd\Base\Users\Models\User, but that's giving the same problems.
Any help is appreciated!

Dear,

The error messages shown when you run vendor:publish because of I defined the publish path, but nothing to publish. Everything still ok.

You can change the auth config by run this command:

php artisan core:vendor:publish webed-users

Then open the file config/webed-auth.php and modify the guard. The default guard is web.

Thanks!

Sorry for my enthousiasm, but php artisan core:vendor:publish webed-users doesn't publish any webed-auth.php file in the config dir.
Do you have any idea wy not?


Performance difference between running model in python vs c++?

Hi @yasenh ,
The code is beautifully written in c++. Even I tried but could not perform the end to end successfully due to lack of expertise in c++ in libtorch. Could you also provide some sort of statistics that could tell whether running the model in c++ improves the performance as compared to running the same model in python in GPU?
What I guess is there should not be much difference, even if it exists. And if exists, why such performance difference is coming? I know I am asking too much, but if you could analyze it, it would be really useful.

Hi @govindamagrawal, there are some benchmark under "issue https://github.com/yasenh/libtorch-yolov5/issues/3".
For the more detailed analysis, I may still need little bit time to get more familiar with libtorch and pytorch (e.g. asynchronous execution), I will post the updates once I get better understanding :)


Fix error comparing screenshots in mobile tests

Coverage increased (+0.007%) to 90.904% when pulling 0e74a73fec0d81a620c61a7fcce223b6e3936242 on fix/mobile_visual into cfde6aeb81d26730dfacca3dbc820157e671485a on master.


fix: refactor generator/docs links to match PR #793 refactor

Description

Updated the filter and configuration-file links to match the new structure of the generator docs

Related issue(s)
See #793

@Florence-Njeri  when do you need to have it merged? :slightly_smiling_face:
If this is dependent on your work in the Generator tool repo getting merged, we should add a temporary "do not merge" label for example.

@alequetzalli PR in generator merged, so I think you can merge this PR


Can't compile by gitian - make: execvp: ./config.guess: Permission denied

make -j2 -C /home/ubuntu/build/zealium/depends HOST=x86_64-w64-mingw32
make: execvp: ./config.guess: Permission denied
make: Entering directory /home/ubuntu/build/zealium/depends' make: execvp: ./config.sub: Permission denied make: execvp: ./config.guess: Permission denied make: execvp: ./config.sub: Permission denied Makefile:72: hosts/.mk: No such file or directory Makefile:74: builders/.mk: No such file or directory /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Makefile: not found /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected /bin/sh: 1: Syntax error: "|" unexpected make: config.site.in: Command not found /bin/sh: 1: Syntax error: "|" unexpected make: config.site.in: Command not found /bin/sh: 1: Syntax error: "|" unexpected make: *** No rule to make target builders/.mk'.  Stop.
make: Leaving directory `/home/ubuntu/build/zealium/depends'

try:
chmod 764  ./config.guess
chmod 764  ./config.sub
(read from https://github.com/LIMXTEC/BitCore/issues/26 )


[sigh] Fix entitlements merging when changing team while resigning

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
These are the changes from https://github.com/fastlane/fastlane/pull/12131 updated to master and with merge conflicts resolved. Please see that issue for more in-depth detail.
Description
Testing Steps
supersedes #12131

Can you fix the CLA thing please @snatchev @joshdholtz?

@janpio It looks like the commit was authored by<EMAIL_ADDRESS>who has not signed the CLA.
@silvervest needs to either amend the commit with git commit --amend --author="Author Name<EMAIL_ADDRESS>or (I think) reply to googlebot with "I consent."

@googlebot I consent.

Thanks @snatchev, consent from @kapfab was already at https://github.com/fastlane/fastlane/pull/12131 so I hoped I could override the message here, but only you could - mentioning @kapfab solved the problem as well of course. (Thanks!)

@janpio This was closed without merging - possible to reopen and give it some ❤? We're still affected, and other users too it seems.

Closing was unintentional, sorry: https://github.com/fastlane/fastlane/issues/16048
You can always help us by trying and reviewing the code yourself and let us know if it does what you want it to.

I can't seem to do any kind of formal review, Github notes review is required by reviewers with write access. I did however resolve the newly developed merge conflict so this is good to go again.

I was debugging a different fastlane issue and completely forgot about this PR, and deleted my repo to fork it completely fresh.
I have since salvaged these changes in my fork, and resolved the conflicts for this, but the PR is stuck linked to an "unknown repository" now. This change should still go out however. Any ideas on how to fix this, or should I open a new PR and link to this one?

You can pull down the patch from this PR and apply that to your local copy.
https://coderwall.com/p/6aw72a/creating-patch-from-github-pull-request

I don't need the patch, I still had my local branch. However, this PR itself has unlinked from my repository in Github but I still would like to see this change merged.

Oh right. Well, close this PR and link it to a new one? This one had already been approved so as long as they're the same, the process should be quicker (I would guess).
I'm just a contributor and cannot speak to how quickly the actual maintainers of the repo respond.

No updates here?

I will take a look at this tomorrow and see if I can get the merge conflict resolved 😊

FYI @joshdholtz, I’ve merged the changes a few days ago (https://github.com/kapfab/fastlane/tree/resign_fixes) and successfully ran a few tests chaining team while resigning.

Due to lost head branch, I've reopened this as #18713, which is up-to-date with master and has no merge conflicts.


Mark ember-cli-uglify package as deprecated

npm deprecate ember-cli-uglify "Renamed to ember-cli-terser."

Increase visibility that the package with the old name is deprecated/renamed.

https://www.npmjs.com/package/ember-cli-uglify
https://github.com/ember-cli/ember-cli-terser/pull/230

done ✅


Several languages to Franz Dictionary

Hey Franz! I am using Version 5.0.0-beta.11 (5.0.0-beta.11.135)
I talk in English & French on my WhatsApp and it seems like you can only choose one language at a time in the Settings. I chose English. It is annoying to have the red doted line under every word I write in French.
Keep it up

Duplicate of #92


Upgrade to React 16

Upgrades to React 16. Couple of notes:

Enzyme has a new setup method to support both 15 and 16
React 16 requires requestAnimationFrame.
React 16 no longer supports string refs. I've removed those tests (though we'll unofficially support them until we can figure out what to do about them).

Codecov Report

Merging #426 into master will increase coverage by 2.83%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #426      +/-   ##
========================================
+ Coverage   82.17%    85%   +2.83%
========================================
  Files          45     45
  Lines        1335   1327       -8
  Branches      243    240       -3
========================================
+ Hits         1097   1128      +31
+ Misses        203    170      -33
+ Partials       35     29       -6

Impacted Files
Coverage Δ

packages/microcosm/src/addons/model.js
97.26% <0%> (-2.74%)
:arrow_down:

packages/microcosm/src/addons/action-form.js
100% <0%> (+100%)
:arrow_up:

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 2bec173...fd0e558. Read the comment docs.


TranslateClient throwing exception with any use of translate() method, other methods work fine

Using the latest version "google/cloud": "^0.20.2"
I can't seem to get translation working at all.
$client = new Google\Cloud\Translate\TranslateClient(['key' => 'xxxx', 'projectId' => 'xxxx']);
$client->translate('How are you?', ['target' => 'es']);

throws the following exception
Google\Cloud\Exception\BadRequestException with message '{
  "error": {
    "code": 400,
    "message": "Invalid JSON payload received. Unknown name \"model\": Cannot bind ''. Field 'model' could not be found in request message.",
    "errors": [
      {
        "message": "Invalid JSON payload received. Unknown name \"model\": Cannot bind ''. Field 'model' could not be found in request message.",
        "domain": "global",
        "reason": "badRequest"
      }
    ],
    "status": "INVALID_ARGUMENT"
  }
}'

If I specify the 'model' as 'base' (I don't think I have nmt enabled)
$client->translate('How are you?', ['target' => 'es', 'model' => 'base']);
I get a very similar exception:
Google\Cloud\Exception\BadRequestException with message '{
  "error": {
    "code": 400,
    "message": "Invalid JSON payload received. Unknown name \"model\": Cannot bind 'base'. Field 'model' could not be found in request message.",
    "errors": [
      {
        "message": "Invalid JSON payload received. Unknown name \"model\": Cannot bind 'base'. Field 'model' could not be found in request message.",
        "domain": "global",
        "reason": "badRequest"
      }
    ],
    "status": "INVALID_ARGUMENT"
  }
}'

However other requests are working fine:
$client->detectLanguage('How are you?');

returns
[
     "languageCode" => "en",
     "input" => "How are you?",
     "confidence" => 0.47573137283325,
]

I've tried using the translate method with different targets, adding sources, with and without the model option, and changing the format between plain-text and html. I've created new projects in console and none of them work.
Any ideas?

On a hunch I edited TranslateClient and commented out the addition of the model option and it works
I edited TranslateClient::translateBatch() like this:
    public function translateBatch(array $strings, array $options = [])
    {
        // $options += [
        //     'model' => '',
        // ];

        $response = $this->connection->listTranslations($options + [
            'q' => $strings,
            'key' => $this->key,
            'target' => $this->targetLanguage,
            // 'model' => $options['model']
        ]);

        $translations = [];
        $strings = array_values($strings);

        if (isset($response['data']['translations'])) {
            foreach ($response['data']['translations'] as $key => $translation) {
                $source = isset($translation['detectedSourceLanguage'])
                    ? $translation['detectedSourceLanguage']
                    : $options['source'];

                $model = (isset($translation['model']))
                    ? $translation['model']
                    : null;

                $translations[] = [
                    'source' => $source,
                    'input' => $strings[$key],
                    'text' => $translation['translatedText'],
                    'model' => $model
                ];
            }
        }

        return $translations;
    }

and now I get this response:
[
     "source" => "en",
     "input" => "Hello, how are you?",
     "text" => "Hei, hvordan har du det?",
     "model" => null,
]

I've verified this. Let me dig around and I'll get back to you. Sorry for the inconvenience!

Hey @alexleonard, I've opened a PR to address this issue. (#344) Would you be able to give that a shot and make sure it fixes the error?

Thanks John, I've wrapped up for the day here but will check it in the
morning.
Cheers,
Alex
On Wed 22 Feb 2017 18:25 John Pedrie<EMAIL_ADDRESS>wrote:

Hey @alexleonard https://github.com/alexleonard, I've opened a PR to
address this issue. (#344
https://github.com/GoogleCloudPlatform/google-cloud-php/pull/344) Would
you be able to give that a shot and make sure it fixes the error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-php/issues/343#issuecomment-281739524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADFoY8OazarW0Dlk59RdjXaAuirrvkiOks5rfG-UgaJpZM4MIvgm
.

--
Alex Leonard ~<EMAIL_ADDRESS>~ plus.google.com/+AlexLeonard
Websites: alex.leonard.ie ~ ebauche.net http://www.ebauche.net/


Remove duplicate parameter from "/schedules" path

Found it when I was importing the API to Postman.

Could you please also check if this thing is also duplicated anywhere in the code comments? We generate these json files based on the comments/annotations we add in the code.

Sure, will look into it.

Done 👌.


empty proxy group selector that contains other proxy group or keyword

  - name: 🗿QUIC
    type: select
    proxies:
      - REJECT
      - PASS

picrel empty expanded section.

tested with Firefox seems to be ok. only with kiwi browser it occurs. using incognito mode no extensions also the same. hmmm 🤔

🧐


[Bug][Gitlab] No table for gitlab_issue_assignees

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

What do you expect to happen
No error. This is happening because there is no migration defined for this table. It needs to be added.  Double check #5321 to ensure other affected plugins don't have this problem.
How to reproduce
Run Gitlab plugin against one or more scopes (i.e. projects).
Anything else
No response
Version
main - 4fc799e7e7af3b58d2559c41a8136db41bf51206
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

@mindlesscloud Can you take a look? It looks like you worked on #5321.


Add extraPorts option (#8945)

Signed-off-by: Scott Stanton<EMAIL_ADDRESS>
What this PR does / why we need it:
This PR adds an extraPorts option that allows additional ports to be exposed by the daemonset.  This is needed to support hostPort access to a forward type input.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #8945

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

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign mattfarina

@snstanton thanks for submitting the PR - I have the same need and grateful to see what someone put this change out there.
It looks like the Chart.yaml is now in conflict (due to another PR getting merged and conflicting the chart version no doubt).  Any chance you can resolve and bump the chart version?  Hopefully one of the chart owners will take a look soon!

/assign @unguiculus

Please fix conflicts and bump minor version.

Done.  Hopefully we can get it merged before another conflict shows up.

/lgtm

/ok-to-test

I pulled and merged from master.  There were no changes to the chart.  What is left to do to get approval?

/lgtm

@unguiculus any chance you can take a look at this one again?

/lgtm


Fix publishing pipeline

Reason: since v4.1.1, no wheels are being released anymore. The change in #820 is responsible for that. If you look at the publishing pipelines, those fail b/c poetry python X is not a valid command. This PR amends that.
Checklist

[x] I have read contributing guidelines
[x] I'm sure that I did not unrelated changes in this pull request
[ ] I have created at least one test case for the changes I have made only changes in CI config

Related issues
None
@lk-geimfari right now, I see the tag 5.0.0 in the repo, but there were no dists pushed to PyPI on merging #1035. I'm not sure if this was a deliberate decision or the pipeline just failed and no one looked at it. If the latter - is it possible to release a 5.0.0.post1 or 5.0.1 which has the same codebase as 5.0.0, only with wheels on PyPI?

@hoefling Although we have created the 5.0.0 release, we are not publishing it on PyPi yet, since were found some critical issues.

Thank you!

@lk-geimfari thank you for your response! Don't merge this in yet though, there's still stuff to do (like MANIFEST.in obsoletion etc). Will do later this evening and ping you when done.

@hoefling I'll wait for ping. Thank you!

@lk-geimfari I would also rewrite the minifier to 1. get rid of setup.py and 2. get rid of using distutils API since deprecated and the minifier doesn't really need any of that. However, this could be food for a separate PR, as the changes get too big otherwise.

@lk-geimfari other than that, I think this is ready for a review now!

@hoefling Okay then. I'm merging this PR. Thank you very much!


Center Settings - Scrolling to bottom of page breaks infinite scroll

Login as an admin
Go to the main Center page
From the menu choose "Center Settings"
On the resulting page scroll to the bottom.

In your console you will see a error "Invariant Violation: replaceState..."

Click the Shopping Bag to go back to Center.
Scroll to the bottom of the page.

Infinite Scroll is now broken.

Passed on Latest.

Passed on staging.


Wallpaper not being set on all monitors after specific monitor wallpaper is set

I found an edge case where if you are using hyprctl hyprpaper to set wallpapers: The following behavior occurs with these steps:

Turn on hyprpaper in the terminal
Unload all wallpapers using hyprctl hyprpaper unload all
Preload wallpaper using hyprctl hyprpaper preload WALLPAPER
Set wallpaper on all monitors using hyprctl hyprpaper wallpaper ,WALLPAPER
Unload all wallpapers using hyprctl hyprpaper unload all
Preload wallpaper using hyprctl hyprpaper preload OTHER_WALLPAPER
Set  wallpaper to a specific monitor using hyprctl hyprpaper wallpaper MONITOR,OTHER_WALLPAPER
Unload all wallpapers using hyprctl hyprpaper unload all
Preload wallpaper using hyprctl hyprpaper preload ANOTHER_WALLPAPER
Set wallpaper on all monitors using hyprctl hyprpaper wallpaper ,ANOTHER_WALLPAPER
The wallpaper is not changed on MONITOR

If I check the output of hyprpaper I can see that the image is being preloaded but it not being set for the monitor that was addressed individually. It changes for the monitors that were not addressed individually but not for the one(s) that were. Is this intended behavior?

this is indeed intended behavior. empty monitor means a fallback wildcard

key part: without a set wallpaper

this is indeed intended behavior. empty monitor means a fallback wildcard
key part: without a set wallpaper

Oh OK then. Thank you for the quick reply.


nsecx.go

Stuff in that file is half done and has been for more than 2 years. Either fix or delete.

The Denialer interface should be removed and both "implementations" (for nsec it always returned true). This is going to happen soonish.


Credentials from .usqlpass file are not used

First of all thanks for this handy tool! I'm just playing around with it for an hour so maybe I'm just too dumb to use it and this isn't really a software problem. Here is my issue:
I'm using usql to connect to a CockroachDB Serverless instance and this is working fine when I provide the full connection string which includes the credentials:
usql 'cockroach://myuser:mypass@free-tier5.gcp-europe-west1.cockroachlabs.cloud:26257/defaultdb?sslmode=verify-full&options=--cluster%3Dmycluster-3361'

Connected with driver postgres (PostgreSQL 13.0.0)
Type "help" for help.

cr:myuser@free-tier5.gcp-europe-west1.cockroachlabs.cloud:26257/defaultdb=>

What I really would like to do is to move the credentials in the ~/.usqlpass file like so:
# format is:
# protocol:host:port:dbname:user:pass
cockroach:*:*:*:myuser:mypass

However, the client does not seem to pick up this information when I try to connect:
usql 'cockroach://myuser@free-tier5.gcp-europe-west1.cockroachlabs.cloud:26257/defaultdb?sslmode=verify-full&options=--cluster%3Dmycluster-3361'
error: pq: 28000: password authentication failed for user myuser

Am I doing something wrong or is this a bug? Can I somehow check whether the ~/.usqlpass file is read at all?
usql --version
usql 0.10.0

Try cockroachdb. If that doesn't work, just use the postgres name, as cockroach just uses the postgres connection.

@kenshaw It works when I use cockroachdb. Thanks a lot!
I assumed that I can use any scheme alias in the .usqlpass file but that does not seem to be the case. Is there a general rule on which scheme identifier can be used in this file? Maybe the documentation could be improved in this regard?

It needs to be the primary name. I chose to do it that way for a number of reasons. The rule is that it can't be an alias on the dburl documentation.


adds support for the V2 HTTP API

Will detect when fetching an image if the V2 API is supported, and fall
back to the V1 API if it is not. Auth currently unsupported.
Partially addresses https://github.com/appc/docker2aci/issues/46 and https://github.com/coreos/rkt/issues/1583.

As of right now all the information for the given layers comes from the "v1Compatibility" field, which I feel really uneasy about. The schema for the manifest doesn't say if it's an optional field, if it needs to conform to the schema of the v1 API, or much else about it.
The example manifest in their documentation doesn't even have the correct number of elements in the history array to be able to correlate each one to a layer in the image. I can't find anywhere else in the API that contains the information in it though (the information is what would have been returned in the V1 API by a GET /v1/images/(image_id)/json request here.
So either this field is poorly documented and their example manifest is malformed, or there's some way to get the necessary information about each layer in the V2 API I'm missing.

Can you ping upstream about this to check? #docker-distribution on IRC should be the place to start.

Will do

Missing license headers.

Since auth is not supported, is there any v2 registry to test this against?

There isn't a public one, but it's easy enough to run your own:
https://github.com/docker/distribution/blob/master/docs/deploying.md

There isn't a public one, but it's easy enough to run your own:
https://github.com/docker/distribution/blob/master/docs/deploying.md

Thanks!
The PR looks good in general.
Some comments:

We still use the v1 annotations (appc.io/docker/v1/registryurl and so on) even if we get the image from a v2 registry.
The --insecure flag is described as "Allows unencrypted connections when fetching images". As far as I can see it forces unencrypted connections by using http://. Also, it should be added to the example string (docker2aci [--debug] [--nosquash] IMAGE).
When trying to connect to a v2 that doesn't support TLS, the error message is not very descriptive: Error: conversion error: Get https://localhost:5000/v2: tls: oversized record received with length 20527, perhaps we should detect that the server doesn't support it and return a proper error.
We can't merge this before we suppor auth because it breaks pulling images from the Docker Hub:

> docker2aci docker://busybox
Error: conversion error: unexpected http code: 401, URL: https://registry-1.docker.io/v2/busybox/manifests/latest

any luck badgering upstream about auth?

Still on my to do list :p
On Fri, Nov 13, 2015 at 11:10 AM, Jonathan Boulle<EMAIL_ADDRESS>wrote:

any luck badgering upstream about auth?
—
Reply to this email directly or view it on GitHub
https://github.com/appc/docker2aci/pull/99#issuecomment-156529168.

I asked in IRC about the v1Compatibility thing I described earlier in this thread, and docker is "working on an improved manifest format". Until that's done, we "need to use v1Compatibility". So expect docker2aci needing to be modified in the future for their new format, but that's the field we want to get this information from for now.

I figured out the auth issue. Turns out my curl commands failed because any repo named like centos is actually library/centos. I just updated the commit to have the auth stuff, so please review the changes.
There is an issue atm though, where some images will spit out the following error:
Error: conversion error: error squashing image: error rendering squashed image: image hash does not match expected (sha512-5b1aa5a55395cb7bd9f9c0a0d247908a82c406e8da7690a04be2d5ed71d16784f33c0588ddb3396c168d816d6b3da2f4c5e45dd81d2b4d8ba001fd026e17eab7 != sha512-bbcacd83a85b6b0157de97ceb691d797ef4f0bebbfef1f31edb5c5fa57376880c866f3955453a8523e7b1507a68b13a2cfe72190f9eec1bd0ae1446690c49906)

I'm looking in to that now. For anyone who wants to test auth against the public registry, I've been able to successfully convert the alpine and ubuntu images.

@iaguis any ideas on that error?

Hm...
We import the converted layers to a in-memory conversion_store that hashes the ACI, generates a key from the hash and has functions to return the ACI file path by key.
That error means that the stored hash doesn't match the actual hash of the file. Which is very weird, we don't do anything fancy in conversion_store.go.

Some layers have the same sha256 so they end up with the same name and overwrite each other:
> docker2aci --nosquash docker://quay.io/coreos/etcd
Downloading sha256:f05e5: [====================================] 3.98 MB/3.98 MB
Downloading sha256:af189: [====================================] 3.5 MB/3.5 MB
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B

Converted ports:
	name: "2379-tcp", protocol: "tcp", port: 2379, count: 1, socketActivated: false
	name: "2380-tcp", protocol: "tcp", port: 2380, count: 1, socketActivated: false
	name: "4001-tcp", protocol: "tcp", port: 4001, count: 1, socketActivated: false
	name: "7001-tcp", protocol: "tcp", port: 7001, count: 1, socketActivated: false

Generated ACI(s):
coreos-etcd-d21dd9a5886270b7c2c379c02fc548e0696b139c43bb12fdb2d9b63409717485-latest-linux-amd64.aci
coreos-etcd-620329641f386e62c7b0e0fa60a9acef100e71058124ddc7f1969557c72b2458-latest-linux-amd64.aci
coreos-etcd-9cd3f08f7ccfaad24c73757a5b4f79601f2790726d6ccdd556a82e5c9c5ddbfa-latest-linux-amd64.aci
coreos-etcd-9cd3f08f7ccfaad24c73757a5b4f79601f2790726d6ccdd556a82e5c9c5ddbfa-latest-linux-amd64.aci
> ls
coreos-etcd-620329641f386e62c7b0e0fa60a9acef100e71058124ddc7f1969557c72b2458-latest-linux-amd64.aci
coreos-etcd-9cd3f08f7ccfaad24c73757a5b4f79601f2790726d6ccdd556a82e5c9c5ddbfa-latest-linux-amd64.aci
coreos-etcd-d21dd9a5886270b7c2c379c02fc548e0696b139c43bb12fdb2d9b63409717485-latest-linux-amd64.aci

Wild guessing here: could it be that because the images are now content-addressable and both are the same (empty), only one layer is served?
Trying with other images, it seems the empty layers have the same sha256 (note the 32 B images):
Downloading sha256:6ffe5: [====================================] 65.8 MB/65.8 MB
Downloading sha256:f4e00: [====================================] 71.5 KB/71.5 KB
Downloading sha256:e99f3: [====================================] 680 B/680 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:7e1e5: [====================================] 83.2 MB/83.2 MB
Downloading sha256:4c72f: [====================================] 167 B/167 B
Downloading sha256:881ef: [====================================] 135 B/135 B
Downloading sha256:43f0b: [====================================] 438 B/438 B
Downloading sha256:e9421: [====================================] 545 B/545 B
Downloading sha256:9ad12: [====================================] 203 B/203 B
Downloading sha256:731c8: [====================================] 242 B/242 B
Downloading sha256:af655: [====================================] 243 B/243 B
Downloading sha256:e85be: [====================================] 277 B/277 B
Downloading sha256:728f7: [====================================] 626 B/626 B
Downloading sha256:bb6b0: [====================================] 1.01 KB/1.01 KB
Downloading sha256:9c9e5: [====================================] 680 B/680 B
Downloading sha256:bd75f: [====================================] 295 B/295 B
Downloading sha256:47d9c: [====================================] 53.1 KB/53.1 KB
Downloading sha256:0be50: [====================================] 144 B/144 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Downloading sha256:a3ed9: [====================================] 32 B/32 B
Error: conversion error: error squashing image: error rendering squashed image: image hash does not match expected (sha512-a4062020e8770a42626219c3cb10c3adc03e21b045fe9da06aee76a484ba99fcae979ea2740d5247e5a3968b13731c8913a764ff3b3153a986df3741447a37b0 != sha512-1d540e7e737ca872995b8cf610a811119ca473941b7caa136fe25f19e362e97534a9c43baa28175ca4119f85ed0f44f3c66ab4dddac4bf17b39fe7be85f880c5)

I added a "random" number to the end of the file name and I can't reproduce the error anymore.

This wouldn't be a problem if we could generate reproducible images. This is not the case now because

Golang maps are randomized: the order of the fields in the manifest can be different on each execution.
https://github.com/appc/docker2aci/issues/89

I'm not sure about that pax one, but at least on the manifest side I would
LOVE to see patches to serialize them deterministically..
On Fri, Nov 27, 2015 at 7:56 AM, Iago López Galeiras <
<EMAIL_ADDRESS>wrote:

This wouldn't be a problem if we could generate reproducible images. This
is not the case now because

Golang maps are randomized: the order of the fields in the manifest
can be different on each execution.
#89 https://github.com/appc/docker2aci/issues/89

—
Reply to this email directly or view it on GitHub
https://github.com/appc/docker2aci/pull/99#issuecomment-160165723.

I'm not sure about that pax one, but at least on the manifest side I would
LOVE to see patches to serialize them deterministically..

I have some somewhere, I'll clean them up :)

https://github.com/appc/docker2aci/pull/107

Oh, I was thinking of the appc serialization code but is the answer there
that it's already deterministicish because the go json package happens to
serialize maps in order?
Does this mean this should now work but for the pathological pax cases?
Iago López Galeiras<EMAIL_ADDRESS>schrieb am Di., 1. Dez. 2015
01:09:

#107 https://github.com/appc/docker2aci/pull/107
—
Reply to this email directly or view it on GitHub
https://github.com/appc/docker2aci/pull/99#issuecomment-160900926.

I just applied @iaguis's patch. I'd personally prefer to instead just number the layers and append the layer's number (as in 0, 1, 2, ...), but knowing the number of what layer it's working on would be messy there.
Seems to work for me fully now, should be ready for another pass.

For the record, my patch was a proof of concept and I also prefer numbering the layers.

Oh, I was thinking of the appc serialization code but is the answer there
that it's already deterministicish because the go json package happens to
serialize maps in order?

AFAICT, there're no maps in the spec. The problem was that Docker uses maps for ports and volumes which get randomized, causing the converted manifest to be non-deterministisch.

Does this mean this should now work but for the pathological pax cases?

I think so, yes.

The layers are now numbered in order, instead of randomly.

Cool, it works! :D
Some nits but after fixing them LGTM.

Nits should be fixed. Want to give this a final :+1:?

LGTM :+1:


Ignore null message in assertNotEquals methods

Closes #432
Fixes #432  .
Did you remember to?

[ ] Add test case(s)
[ ] Update CHANGES.txt

We encourage pull requests that:

Add new features to TestNG (or)
Fix bugs in TestNG

If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the
TestNG-dev before you spend time working on it.

ping @missedone - Just thought I would let you know on this one, because I have added a new entry into org.testng.internal.EclipseInterface and the javadocs says that entries into this interface should also have a parallel update happening to the eclipse plugin (in case its required)


[feat]: Parse schema with partial fallback values #155

Implements https://github.com/fabian-hiller/valibot/issues/155 including unit tests to reflect behavior.
Happy for feedback 😀

I think that getDefaults should return the default value of optional, nullable and nullish and not the value of fallback. I think that fallback was only an example in issue #155.

I have implemented getDefaults. The API will be available in the next version. Thank you for your contribution!

v0.20.0 is now available


Find out who wrote the song and produced it:

Purpose: Provide users with information about the songwriters and producers.
Implementation: Integrate with APIs like MusicBrainz or Genius to fetch song credits.

I can see it now ;)
Just a quick ChatGPT prompt generated this:
Title: Add Songwriter and Producer Information to Song Pages

Description:
We want to provide users with more information about the people behind the music, such as songwriters and producers. This feature will make the song pages more informative and engaging.

Feature Requirements:
	1.	Song Credits Section:
	•	Add a section to display the songwriters and producers for each song.
	•	Include their names and roles (e.g., songwriter, producer).
	2.	API Integration:
	•	Use APIs like MusicBrainz or Genius to fetch song credit information.
	•	Ensure data is fetched dynamically based on the song ID.
	3.	Clickable Names:
	•	Make songwriter and producer names clickable, leading to a page with more details about their work (optional).
	4.	Fallback for Missing Data:
	•	If credits are unavailable, show a message like “Credits not available for this song.”

Acceptance Criteria:
	•	The song page displays songwriters and producers for all songs with available data.
	•	Song credits are accurate and fetched dynamically using an API.
	•	The page handles missing data gracefully without breaking the layout.

Priority: Medium

Estimated Effort: 3-5 story points

Additional Notes:
	•	Coordinate with the backend team to set up API connections if necessary.
	•	Verify API reliability and test with different songs to ensure coverage.

You just have to convert it to markdown format ;)

btw, this is probably too complex for this project... you should come up with simpler features unless you know your way around this


DOC-7652: Document how to manage channels via the System Console

Summary
Detailed steps for the channel administration workflows were required but absent. So, this PR aims to add the steps for all those workflows for channel management on the User management configuration settings page.
The following workflows have been added.

Find Channels
Filter channel searches
Review channel configuration
Advanced Access Controls

Create Posts
Post Reactions
Manage Members
Channel Mentions
Manage Bookmarks

Channel Management

Sync Group Members
Public Channel or Private Channel

Groups (Skipped)
Members

Add a Member
Remove a Member

Archive a channel

Ticket Link
This PR fixes #7652
Checklist

[x] This PR follows the Mattermost Contributing Guidelines.
[x] Relevant product screenshots in the Denim theme have been added.
[x]  Workflows are structured as a numbered list for the steps instead of paragraphs.
[x] The changes are tested using a local build.

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

@cwarnermm Please review and suggest changes, if any. Thanks.

@cwarnermm Thanks for the review. All the requested changes have been applied, and the PR is ready for your evaluation.


fix: avoid positive lookbehind in snake case extension

What kind of change does this PR introduce?
Bug fix #100
What is the current behavior?
Use reg exp to generate the snake cases
What is the new behavior?
Generate the snake cases without using reg exp

Nice! Could we add some tests to make sure this snakeCase function outputs the correct value?

Done ✅ I have already implemented the tests for the new implementation of the ToSnakeCase extension. If you have another case to test I will add it without problems. Thanks in advance.


Usage with scoped packages?

I have a package named: @scope/core, and when generating the readme, the name of the package in the readme file becomes: scope, not core or @scope/core. How can I get the correct package name in the readme?

are you using so-called verb#dev? readme here, still mentions only npm install verb which is pretty old. try installing verbose/verb#dev instead.
I dont think the name is handled differently, so you should get it directly from the pkg json.

I'm using verbose/verb#dev

My package.json:
{
  "name": "@guybrusssh/color",
}

My .verb.md:
    # {%= name %} v{%= version %}

My generated README.md:
    # guybrusssh v0.0.0

Could it be that verb-repo-data or generate-data is actually escaping @ and / ?

Ookey, thanks. So we should track it down to somewhere in the deps. I cant remember where the populating is done, but checked verb-data, generate-data and few more places and didnt find anything specific for the name.. hm.

neither.. probably in verb-repo-helpers

@phun-ky and @olstenlarck I had this issue and I thought that I fixed it. I might not have merged a PR or published the change though. I'll take a look and get it published. It had to do with how the name and alias were normalized.

@phun-ky I published a patch of a dependency where this is fixed. You'll have to make sure to uninstall and re-install verb-generate-readme to get the latest dependencies.
{%= name %} in the templates should have the scope on them now. If you need to update your "usage" section (if that's still in your .verb.md), then use varname instead of name:
## Usage

```js
var {%= varname %} = require('{%= name %}');
```

@doowb where did you publish that patch? I can't find reference of it in this in your code. I've uninstalled and installed verb-generate-readme with no luck:
 npm uninstall -g verb-generate-readme && npm cache clean --force && npm install -g verb-generate-readme

varname and name are still: guybrusssh


Verilog reader doesn't resolve scope correctly when new wire is declared with same named wire in assignment

Test1
Repro Instructions
yosys -p "read_verilog test1.v"

test1.v
module test1 (data);

input wire [127:0] data;

generate if (1)
  begin: g0
        wire [31:0] data = data[63:32];
  end
endgenerate

endmodule

Actual Behavior
-- Running command `read_verilog -sv test1.v' --

1. Executing Verilog-2005 frontend: test1.v
Parsing Verilog input from `test1.v' to AST representation.
Generating RTLIL representation for module `\test1'.
test1.v:7: Warning: Range select [63:32] out of bounds on signal `\g0.data': Setting all 32 result bits to undef.
Successfully finished Verilog frontend.

Warnings: 1 unique messages, 1 total
End of script. Logfile hash: c42ece85ad
CPU: user 0.01s system 0.00s, MEM: 42.18 MB total, 13.00 MB resident
Yosys 0.9+932 (git sha1 0d037bf, gcc 5.4.0-6ubuntu1~16.04.11 -Og -fPIC)

Expected Behavior
No warning about an out of bounds signal select.
Commercial tools, as well as iverilog, are doing this right. Verilator with --lint-only complains with a similar error:
vagrant@ubuntu-xenial:~/projects/bitec_dp$ /opt/verilator/bin/verilator --lint-only test1.v
%Warning-SELRANGE: test1.v:7: Selection index out of range: 63:32 outside 31:0
                   ... Use "/* verilator lint_off SELRANGE */" and lint_on around source to disable this message.
%Error: test1.v:7: Wire inputs its own output, creating circular logic (wire x=x)
%Error: Exiting due to 1 error(s), 1 warning(s)
%Error: Command Failed /opt/verilator/bin/verilator_bin --lint-only test1.v

Test 2
Repro Instructions
yosys -p "read_verilog -sv test2.v"

test2.v:
module test2 (data);

input wire [127:0] data;

generate if (1)
  begin: g0
        wire [31:0] data = data[63:32];

        if (1) begin : g1
                wire [7:0] data = data[15:8];
        end
  end
endgenerate

endmodule

Actual Behavior
-- Running command `read_verilog test2.v' --

1. Executing Verilog-2005 frontend: test2.v
Parsing Verilog input from `test2.v' to AST representation.
Generating RTLIL representation for module `\test2'.
test2.v:7: ERROR: Failed to detect width of signal access `\g0.data'!

Expected Behavior
No error.
Like test1, iverilog has no issues with this, while verilator fails.

Do you have a reference to one of the IEEE standards for the correct behaviour?
FWIW, Verific behaves the same way as Yosys - it produces this warning
VERIFIC-WARNING [VERI-1216] oob.v:7: index 32 is out of range [31:0] for 'data'

and sets g1.data to 32'bx

Do you have a reference to one of the IEEE standards for the correct behaviour?

I do not.
But the code example is a heavily reduced version of code that has been used for years, and successfully, with tools like ModelSim, VCS, DC, Quartus, Vivado, and others.

The reduced example was reduced to the point to where it reproduces the same error messages, but I didn't run it through one of the commercial tools. I may have reduced it too much.
So hold off until I've verified that.

I had changed the minimum example too much to protect the innocent. I have filed issue #1456 instead.
Closing this one.


6.2.0 breaks gestures in other components that use PanResponder

Environment

Description

After upgrading to 6.2.0 it broke pan gesture handler in other components eg. sortable/draggable lists. I have no clue how it's possible as I've never encountered such a thing before but downgrading to 2.1.4 the drag and drop worked as it should. The draggable list is this one: https://github.com/SHISME/react-native-draggable-grid and it's using PanResponder from react-native.
deps:
"resolutions": {
    "react-native-pager-view": "6.2.0",
  },
  "dependencies": {
    "react-native-gesture-handler": "^2.9.0",
    "react-native": "0.71.4",
    "react-native-reanimated": "^3.0.2",
    "@react-navigation/bottom-tabs": "^6.5.7",
    "@react-navigation/core": "^6.4.8",
    "@react-navigation/elements": "^1.3.17",
    "@react-navigation/native": "^6.1.6",
    "@react-navigation/native-stack": "^6.9.12",
    "@react-navigation/stack": "^6.3.16",
    "react-native-pager-view": "6.2.0"
}

With version 6.1.4:
https://user-images.githubusercontent.com/717975/228487658-18e5f152-f9f9-4add-a0d7-b7c3c772480b.mov
With version 6.2.0:
https://user-images.githubusercontent.com/717975/228488935-75a06e04-8190-4c30-a30b-10bacf7fc019.mov
Reproducible Demo

After using this fork of the draggable list that uses react-native-gesture-handler instead of PanResponder the issue went away. 🤔

@efstathiosntonas are you also using fullScreenGestureEnabled from react-navigation? can you please share a minimal reproducible repo?

@intergalacticspacehighway no, i'm not using this prop.
I've tried reproducing it but I couldn't. Maybe my app has something different than the minimal, I really can't tell. I'll stick to 2.1.x for now.
Here's the repo:
https://github.com/efstathiosntonas/react-native-pager-view-bug

@intergalacticspacehighway thanks for confirming, glad you managed to reproduce it. I believe we’re hitting an edge case here and it might not worth it. This library is quite old and it should be using rngh 2.x.

At least add a note on readme to beware of onShouldBlockNatiVeResponder if it’s being used in other areas of the app.
I also think that the draggable lib has this code there for no reason and it’s a leftover.

after installing react-native-pager-view@next it worked just fine.

Any updates here?

after installing<EMAIL_ADDRESS>it worked just fine.
@intergalacticspacehighway is 7.0.0-rc.0 safe to use in production?

7.0.0-rc.0 fixed it for me too.

Somehow it worked :)

Hello, any updates here? We tried updating the version to 6.3.1 because we encountered an issue in top tab navigation when RTL is enabled for Arabic language.
It was fixed however it broke a swiping action that we have using Gesture.Pan. Upon investigation, the attempt to swipe a row for example triggers the following: onTouchesDown then onTouchesCancelled, the onChange is not triggered.
But the tricky part is that the issue only happens on a component inside a top tab navigation but not with other component which isn't wrapped with top tab.
I tried checking out the latest version which is 6.3.3 and the pre-release version 7.0.0-rc.0 but the issue still persists. For now, downgrading to 6.1.4 fixes the issue.

Hello, just wanted to check if pre-release version 7.0.0-rc.0 is going to be merged into a release version anytime soon? I saw that you released 6.5.0 8 hours ago but that release doesn’t include this code and it would be great to have it to fix this issue.


divide operator

I want an endpoint called divide in HTTP GET that takes 2 parameters and divides the first to the second.
the endpoint gives me a json in similar fashion of the sum endpoint

The output should be in json objects with message, operation, operators and result.


Add UserInfo into AdmissionReview struct

This PR is to add AdmissionReview struct to UserInfo field.
Signed-off-by: eastwd<EMAIL_ADDRESS>

Hi @eastwd, thanks for the contribution!
Could you give me more context why this is required or the use case?
As you may know, this information can be obtained also from OriginalAdmissionReview object that has everything, however, some fields are already set on the model to make life easier for the users, but I would like to maintain a small API/model so the thing doesn't get complex.
If we merge this, I would ask for some minor changes if you don't mind: Basically maintain the import in the same way as the other Kubenrete packages:
from:
//...
	admissionv1 "k8s.io/api/admission/v1"
	admissionv1beta1 "k8s.io/api/admission/v1beta1"
	v1 "k8s.io/api/authentication/v1"
	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
	"k8s.io/apimachinery/pkg/runtime"
//...

to:
//...
	admissionv1 "k8s.io/api/admission/v1"
	admissionv1beta1 "k8s.io/api/admission/v1beta1"
	authenticationv1 "k8s.io/api/authentication/v1"
	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
	"k8s.io/apimachinery/pkg/runtime"
//...

Thank you for reviewing!

Could you give me more context why this is required or the use case?

Yes, of course. I'm developing an admission webhook controller that verifies that the user has different resource permissions than requested.  UserInfo field is necessary for valifing the permission of different resource by getting the CluterRole/Role resource binded to the user.
More specifically, Rancher doesn't support for creating namespace resource with kubectl.
User can create a namespace, but user has no permission in the namespace, because the namespace doesn't have    field.cattle.io/projectId annotation (https://github.com/rancher/rancher/issues/23376)
To fix this problem, I have to develop two admission webhook controllers.

mutating admission webhook controller that create a new project, and adds the annotation of its projectId when new namespace created that doesn't have field.cattle.io/projectId annotation.
validating admission webhook controller that valify user has creating project resources and namespace  when new namespace created that doesn't have field.cattle.io/projectId annotation.

The validating admission webhook controller needs a username to check if user has permission to create a project from the Rancher API based on the username

Thanks for the awesome explanation! Makes sense, I think that would be helpful to others, so let's go with it!

@eastwd thanks for the PR! I'll cut a new release in the following weeks when I update everything for K8s 1.21.

Thank you for merging! I'm looking forward to release.

New release with your change! v2.1.0
It took more than expected because I was waiting for Kind v0.11 release so I could test the update to Kubernetes v1.21 with the integration tests.
Many thanks!


Jupyter notebook import scanpy.api

I have followed these instructions to install scanpy into my miniconda environment:

Whether I try to import scanpy straight from terminal, it keeps giving me an error:
Python 3.5.5 |Anaconda, Inc.| (default, Mar 12 2018, 23:12:44)
[GCC 7.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import scanpy.api as sc
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/scanpy/__init__.py", line 24, in <module>
    import anndata
  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/anndata/__init__.py", line 1, in <module>
    from .base import AnnData, _MAIN_NARRATIVE
  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/anndata/base.py", line 287
    return f'Backing file manager of file {self._filename}.'
                                                           ^
SyntaxError: invalid syntax
>>>

I also get the error when I try to use it with jupyter notebook:
import scanpy.api as sc

Traceback (most recent call last):

  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/IPython/core/interactiveshell.py", line 2910, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)

  File "<ipython-input-1-4a13c503728c>", line 1, in <module>
    import scanpy.api as sc

  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/scanpy/__init__.py", line 24, in <module>
    import anndata

  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/anndata/__init__.py", line 1, in <module>
    from .base import AnnData, _MAIN_NARRATIVE

  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/anndata/base.py", line 287
    return f'Backing file manager of file {self._filename}.'
                                                           ^
SyntaxError: invalid syntax

What is the issue? How can I get over this?
Thank you!

Hi! Thanks for using scanpy!
The error is in anndata so filing a bug there would be more fitting.
Lastly, please do ```pytb for your python tracebacks blocks so we get syntax highlighting:
```pytb
import scanpy.api as sc

Traceback (most recent call last):

  File "/home/unix/tamarao/miniconda3/envs/tamara_env/lib/python3.5/site-packages/IPython/core/interactiveshell.py", line 2910, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)

  […]

SyntaxError: invalid syntax
```

the fix should be in the next anndata release (0.6.2 or 0.7)

Thank you for the prompt response! I did not install anndata separately, I just followed instructions from https://scanpy.readthedocs.io/en/latest/installation.html to install scanpy using pip install scanpy in miniconda environment. Do I need to reinstall another version of anndata? Or of scanpy? Sorry, still not sure how to fix this. Thank you!

try pip install anndata~=0.6.4, this should get you a version where this is fixed!

Perfect! That fixed it! Thanks a lot!


[PDI-13981] Google Analytics Input Step: Duplicate entry on 1001st entry

This is a forward-port PR containing Andrey's fix for this case, I verified locally that it works (using @matthewtckr 's reproduction transformation).

@dkincade Can we merge this in, so I can forward-port #1460?  Thank you.


chore(automation): remove previous labels when PR is updated

Issue number: #1335
Summary
Changes

Please provide a summary of what's being changed

save_pr_details.js: saves labels as a part of the PR artifact object
label_pr_based_on_title.js: removes old labels as they're found based on the list within the same file
reusable_export_pr_details.yml: adds PR labels as an output.

User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[X] Meet tenets criteria
[X] I have performed a self-review of this change
[X] Changes have been tested
[X] Changes are documented
[X] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[X] Migration process documented
[X] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

YEEEESSS!!!!

Merging as soon as release completes ;)


Remote file reference URIs are broken on Windows

I'm working on an archive tool for a client, who wanted an 8chan archiver.  I decided to use swagger to document and use their API, and pyswagger in particular, since my archiver is written in python and is older than God. It also, unfortunately, currently runs on Windows.
With the background out of the way: pyswagger has many issues on Windows with Python 3.6.
Summary
$refs pointing to a relative URI receive the wrong path seperator on Windows machines when accessing a remotely hosted YML or JSON file.
My JSONified schema (YAML triggers other bugs): https://gitlab.com/N3X15/8chan-API/blob/0fdd6548a94ff869c4588f2f36ccc6e79b58a74d/8chan.swagger.json
Log: https://hastebin.com/topoxitepe.txt
Reproduction Steps

Make a schema with relatively-referenced fragments, like "$ref": "definitions/Hurf.json"
Ensure the referenced files exist and are valid.
Upload everything to a server somewhere.
Run App.create() on the URI
Duck.

Expected response
App.create() succeeds.
Observed response
App.create implodes with 404 errors, and the log shows that the base URI of the schema is joined with a backslash rather than the correct forwardslash.
e.g. Instead of https://example.com/api/definitions/Thing.json, we get https://example.com/api\definitions/Thing.json
Environment
(.virtualenv) Rob@RAGE F:\Projects\ChanManBot
> python --version
Python 3.6.3

(.virtualenv) Rob@RAGE F:\Projects\ChanManBot
> pip freeze
attrs==17.3.0
Automat==0.6.0
beautifulsoup4==4.6.0
certifi==2017.11.5
chardet==3.0.4
colorama==0.3.9
constantly==15.1.0
hyperlink==17.3.1
idna==2.6
incremental==17.5.0
Jinja2==2.10
lxml==3.7.2
MarkupSafe==1.0
mysqlclient==1.3.9
olefile==0.44
Pillow==4.3.0
psutil==5.4.2
pyaml==17.10.0
pybuildtools==0.2.1
pyparsing==2.2.0
pyswagger==0.8.36
python-json-logger==0.1.8
pywin32==220.1
PyYAML==3.12
pyzmq==16.0.3
requests==2.18.4
six==1.11.0
SQLAlchemy==1.1.15
toml==0.9.3
tqdm==4.19.5
Twisted==17.9.0
urllib3==1.22
validate-email==1.3
zope.interface==4.4.3

@N3X15 I think the problem is here and would look into this problem later.
I would also investigate using AppVeyor to make sure pyswagger works on Windows platform (since I don't have one at hand)

OK, I should have a PR up shortly that fixes it and a few other minor niggles.


Minor changes to introduction

-Added a note about how heterogenous cells can repopulate diversity.
-Expanded the paragraphs discussing the previous efforts in tHMMs by talking about linkage analyses and then more about tHMMs used in the context of tree restoration.

#116 Should be done with this if approved.

i saw a couple typos that you should change, but merge this  . thanks good work


This still work?

Title: [Bug/Query/(leave empty)] No error. Question Rather.
Body: So, tokens are kinda gone.
Problem:
Would this still be possible to do without access to your token?

You can still get the token. Simply logout and login with the chrome developer tools open.
And yes, the bot is still operational.


[Ad hoc metrics for OPS] Add option to show counters data

Description
Refactor https://github.com/ManageIQ/manageiq/pull/12165

[x] Add option to show counter metrics (currently only gauges visible)
[x] Add option to get counter metrics (currently we only get gauges)

Screenshot

@miq-bot add_label providers/containers,ui,enhancement
@simon3z @zeari @moolitayer please review

we should not display tenants and metric type in the same category, that is confusing.

I recommended in a different pr to drop the tenants from here in favor of always showing them in the autocomplete box.
I would expect by default to see all metric types (not including strings: gauge, counter, availability)

@moolitayer 👍

I recommended in a different pr to drop the tenants from here in favor of always showing them in the autocomplete box.

done in https://github.com/ManageIQ/manageiq/pull/13016

I would expect by default to see all metric types (not including strings: gauge, counter, availability)

Currently we only use the metric id, id is not unique over types. If we decide to to show all metrics types in one page we will have to think about:
a. backend, use id+type and not just id
b. front end, show to the user id+type and not just id.
we can do that in another PR.

we should not display tenants and metric type in the same category, that is confusing.

@simon3z @moolitayer we should wait with this one until #13016 is merged and the tenants will be evicted fro this drop-down.

moved to https://github.com/ManageIQ/manageiq-ui-classic/pull/29


Use nested coproduct list support from Iota 0.2.x

This build will fail because the docs depend on the integration library which depends on the core macros for generating the free boilerplate. I've added a type to the @free generated code, so the integration library build is now outdated.

Once we eventually have this PR passing, is there an easy way to compile the documentation against this release before we merge (to make sure it's all working 👍 )?

@andyscott It's already being checked: https://github.com/frees-io/freestyle/blob/feature/iota-nested-coproducts/.travis.yml#L30

Codecov Report

Merging #326 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #326   +/-   ##
======================================
  Coverage    82.4%   82.4%
======================================
  Files          25      25
  Lines         216     216
  Branches        2       2
======================================
  Hits          178     178
  Misses         38      38

I'm merging since current issues are related to coursier cache. Checked locally and it's working as expected.


:warning: Action Required: Replace Deprecated gcr.io/kubebuilder/kube-rbac-proxy

Description
:warning: The image gcr.io/kubebuilder/kube-rbac-proxy is deprecated and will become unavailable.
You must move as soon as possible, sometime from early 2025, the GCR will go away.

Unfortunately, we're unable to provide any guarantees regarding timelines or potential extensions at this time. Images provided under GRC will be unavailable from March 18, 2025, as per announcement. However, gcr.io/kubebuilder/may be unavailable before this date due to efforts to deprecate infrastructure.

If your project uses gcr.io/kubebuilder/kube-rbac-proxy, it will be affected.
Your project may fail to work if the image cannot be pulled. You must take action as soon as possible.

However, if your project is no longer using this image, no action is required, and you can close this issue.

Using the image gcr.io/kubebuilder/kube-rbac-proxy?
kube-rbac-proxy was historically used to protect the metrics endpoint. However, its usage has been discontinued in Kubebuilder. The default scaffold now leverages the WithAuthenticationAndAuthorization feature provided by Controller-Runtime.
This feature provides integrated support for securing metrics endpoints by embedding authentication (authn) and authorization (authz) mechanisms directly into the controller manager's metrics server, replacing the need for (https://github.com/brancz/kube-rbac-proxy) to secure metrics endpoints.
What To Do?
You must replace the deprecated image gcr.io/kubebuilder/kube-rbac-proxy with an alternative approach. For example:

Update your project to use WithAuthenticationAndAuthorization:

You can fully upgrade your project to use the latest scaffolds provided by the tool or manually make the necessary changes. Refer to the FAQ and Discussion for detailed instructions on how to manually update your project and test the changes.

Alternatively, replace the image with another trusted source at your own risk, as its usage has been discontinued in Kubebuilder.

For further information, suggestions, and guidance:

📖 FAQ and Discussion
💬 Join the Slack channel: #kubebuilder.

NOTE: This issue was opened automatically as part of our efforts to identify projects that might be affected and to raise awareness about this change within the community. If your project is no longer using this image, feel free to close this issue.

We sincerely apologize for any inconvenience this may cause.
Thank you for your cooperation and understanding! :pray:

Maybe as an easy drop-in replacement, we could use https://catalog.redhat.com/software/containers/openshift4/ose-kube-rbac-proxy/5cdb2634dd19c778293b4d98 or https://catalog.redhat.com/software/containers/openshift4/ose-kube-rbac-proxy-rhel9/652809a5244cb343fb4a4b66 (which we are using for DWO downstream)?

HI @AObuchow
Suppose you want to use the Red Hat images. In that case, that is a valid approach if you distribute this solution ONLY to anyone with access to this registry to pull the image and if you can use it according to its terms and conditions.
Anyway, the best approach is to use the feature provided by controller-runtime, and for prod envs, ensure that you have certificates set as well. That would be my recommendation.
Do not really in any extra dependency when it is not required and do not need to relay in any registry


[stable/nginx-ingress] Deployments are targeting wrong pods

Describe the bug
The controller and default-backend deployments are targeting the same pods (eg. the controller is targeting both the controller pods and default backend pods. The same goes for the default-backend deployment).
They are both missing the component label from their respective .spec.selector.matchLabels
Version of Helm and Kubernetes:
Which chart:
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Both 1.34.0 and 1.34.1 are presenting the issue, resulting in no apparent failure, but making the service unavailable because no pods are matching the selector. That happens even when setting useComponentLabel: false although this was supposed to preserve old behavior.


SEARCH - Add pagination

Let's move away from the "click to view more" approach and add in pagination to the search results.
Let's show a default view of say.. 20, and provide a dropdown that lets users select how many results per page (placed at the bottom of results - next to pagination) - Content could be: "Show [20 dropdown] results per page"

Flagging here that we discussed in IRC the question of what it means to paginate on a mixed-type view, and that @samjianga will come back with a specific proposal.

The search API supports this now, pass &page=[positive integer], with two caveats:

Current page size is 30, not 20 (easily changed)
If object type is All (vs. Case, Method, etc.) then 30 (or PAGE_SIZE) of each object type is returned. Returning an interleaved set, interleaved by selected sort order, in combination with paging is a non-trivial problem.

Let's avoid non-trivial work for the "All" filter - this view actually has very little value for users. That being said, if we can mix results, instead of section by "Case" "Method" etc... I understand that most items will be cases by default, but the only real value we'd get from this view is perhaps the "featured" items which we're still deciding on.

OK.  @dethe, let's change the semantics of the current search API selectedCategory=All to mean interleave.

@samjianga ignore me if you are already on this, but there was mention in the meeting today about the need for design related to options for selecting previous / next / first page / last page on search results. Thanks!

Needs some styling decisions, but also need https://github.com/participedia/api/issues/84

@davidascher @andreadelrio @jesicarson - this is what I have in terms of structure. The design can be dealt with in browser. Might be better to think of this screen as a "wireframe" for the content of the pagination piece.

@samjianga what do you mean by "the design can be dealt with in browser"? Thanks!

@jesicarson - If we're not cool with that design - I can edit the CSS directly to change the visual designs, rather than making a series of mockups.

@samjiangweb Gotcha, thanks!

No pagination on xyz as of today

This works well, but we should show the number of results (ie: 1-20) out of the total number of content items in each category (all, cases, methods, orgs) instead of the number of pages. so for cases it would be "1-20 of 735" . Also, is 20 too few results per page? I think maybe 40 would be better.

The current site shows

is that ok?
Changing page size from 20 to 40 is easy, let me know if you still want that @jesicarson.

@davidascher yes that works perfectly for results on a search term. However, on the homepage, if I haven't searched for anything, it just shows "page x of x", not the number of results. I want to be able to see the total number of articles on the site (on the "all" tab), and individually the total number of cases, methods and orgs on those tabs as well.
So on home it should be "xx Results (page x of x)"
And yes, 40 results per page would be good please.
Thanks!

If that's a requirement, add an issue for it. The back-end already supports passing an option for how many results to return. Not infinite scroll though, that is an abomination that should have been drowned at birth.
I think anything besides picking a reasonable default is probably overkill, but maybe that's just me.

Ahaha! I always choose infinite scroll (and will continue to do so just to spite that comment!)
Sure, I'll add an issue for this but it's totally P2 (or Pnever)


fix: go.sum diff in tests/certification/pubsub #1356

Description
I noticed that more pull requests are stuck with the failure of go.sum diff from tests/certification/pubsub. Try to fix this particular issue with this PR.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1356
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Note that this fix is incomplete; other certification tests will also need to have their go dependencies updated. Like the conformance tests, not all certification tests run in the PR results due to the dependency on Azure backend. #1325 contains a more complete set of go mod file updates.
For future reference, any time we see that the certification tests are failing go.mod tidy validation, just run make modtidy-all from the root of the project and it will basically run go mod tidy on the subdirectories.

Then I will close this PR.