Add cfssl issuer to support issuing certs from a cfssl CA

This adds support for a cfssl issuer to allow issuing
certificates from a cfssl CA.
Use cfssl client to communicate with remote cfssl server
https://github.com/cloudflare/cfssl/tree/master/api/client

Signed-off-by: Afolabi Badmos<EMAIL_ADDRESS>
What this PR does / why we need it:

Adds cfssl as a issuer. This allows issuing certs from a cfssl CA.
Uses CFSSL's client to communicate with a remote cfssl server.

Special notes for your reviewer:
Release note:

Add support for CFSSL issuer to support issuing certificates from a cfssl CA

Thanks for maintaining this, and keeping it up to date.
As I mentioned on Slack, we've been working on a new integration point in cert-manager (the CertificateRequest resource) that will allow you to implement your own custom issuer types out of tree. I think this sort of thing would be a great candidate for this, as it will a) prove out the new extension mechanism and b) allow you to maintain this and plug into the wider cert-manager ecosystem easily.
You can read a living design document for the new resource type here: https://github.com/jetstack/cert-manager/blob/master/design/20190708.certificate-request-crd.md. There's still a few places to go into place (e.g. #1860 & also updating the Certificates controller to support creating CertificateRequest resources).
These should be landing soon, as will more examples of how you can build your own controller like this (with a 'skeleton' example repo to help get started)

Hi @munnerz
I see some more progress on certificate requests and the implementation for the existing issuers.
Is there a doc/reference on how I can implement a issuer out-of-band, create the required kubernetes crds and register it with cert-manager? I've looked at the design docs but cant figure out how cert-manager will interact with an external issuer.

@badie thanks for your kind words 😄
We have an 'example repo' here that you can use as a reference: https://github.com/jetstack/cert-manager-external-issuer-example
It's not well fleshed out yet (we could really do with a README at the very least...) but it should demonstrate enough for you to get started.
Smallstep have also put together a similar integration for their own CA (the step-issuer), which will be useful as a reference: https://github.com/smallstep/step-issuer
Aside from these two sources, please feel free to ping me if you run into any issues or have any questions. I'm keen to help grow the external CA ecosystem and make sure that out-of-tree issuer types are first class citizens in cert-manager 😄

I've looked at the design docs but cant figure out how cert-manager will interact with an external issuer.

There is no direct interaction between cert-manager and your own code - instead, all interaction is brokered via the Kubernetes API. You simply need to watch for CertificateRequest resources that reference an issuer that you are responsible for issuing for (e.g. a CFSSLInstance), decode the certificaterequest.spec.csr block, request the certificate and set the certificaterequest.status.certificate field (as well as mark the CertificateRequest as 'ready')

@badie hope some of those references above help. If not, please reach out to me on Slack or open an issue here so we can clarify in our documentation and make it clearer for others.
From cert-manager v0.11 onwards, you can use these 'out-of-tree' issuers out of the box, so I think you should be good to go with this now 😄

@badie Did you manage to build an CFSSL issuer? It would be really nice to have CFSSL support in cert-manager.


About Graph Configration

Configration about Graph should be more flexible, and we should figure out a way how to update scope of the class scanner in the begining.

Before class scanning, neutron will locate packages according EventScanner; while after class scanning, event configuration class will load properties from resource.


Provide public APIs to get parse tree/syntax errors

This is a feature request to provide an API in cython which provides users a way of getting the parse tree (AST) as well as syntax errors for cython files.
Ideally it'd be a call where the contents are passed (to deal with working files) and a syntax error is raised or the generated AST is returned.

Sounds good to me. PR welcome.
Look at the TreeFragment class. It's not designed as an external API, but it comes very close to what you want.

Closing as duplicate of #1628.


GDScript Autocomplete for OS not showing writing if statements

Godot version: Godot 3.1 Beta 10

OS/device including version: Windows 10

Issue description / Steps to reproduce:

func _ready():
    OS. # works here
    if OS. # no autocomplete here

Not showing even when pressing Ctrl+Space
Edit: Same with Engine

Likewise.  Usually have to complete the line, then go back to it to trigger the hints.

Related #26114

I closed this as a duplicate of #26114 but renames the original accordingly(to all singletons)


⚠ Bofrost.de has degraded performance

In 605ee48, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1227 ms

Resolved: Bofrost.de performance has improved in 2aa713a after 32 minutes.


ACPI: remove ACPICA source from the kernel.

It is proving to break some principles that we have to not break.
o it is 50KLOC of impenetrable, badly designed, badly written code
o they are asking you to run a giant blob (the ACPI ML) which is
known to be a source of exploits.
o It's a pain to program with.
All hail Plan 9: taking it out required changing 4 files. That's it.
We get to keep the ioapic.c fix as part of the change.
Tested with both clang and gcc on vmware.
Please test. This is ONLY to get us back to status quo ante.
Next step is to pull in the Akaros code that sets up interrupts
using ACPI. That code is small and nice, so not to worry.
We can continue to consider using ACPICA in user mode; in fact,
I suspect we should.
Signed-off-by: Ronald G. Minnich<EMAIL_ADDRESS>

All ok, tested terminal/cpu with new ninep.
LGTM

LGTM

needs rebase

needs another rebase

well, here we go ...


Following installation instructions doesn't work?

I'm not very familiar with Go, so perhaps I'm doing something wrong?
$ go install -v -tags=sqlite_vtable github.com/augmentable-dev/gitqlite
can't load package: package github.com/augmentable-dev/gitqlite: cannot find package "github.com/augmentable-dev/gitqlite" in any of:
        /usr/lib/go-1.10/src/github.com/augmentable-dev/gitqlite (from $GOROOT)
        /home/erez/go/src/github.com/augmentable-dev/gitqlite (from $GOPATH)

I was able to build successfully with the command below:
git clone https://github.com/augmentable-dev/gitqlite.git
cd gitqlite
make build
sudo cp gitqlite /usr/local/bin
gitqlite -h

That gives me a different error. Sorry if I'm missing something obvious
$ go build
gitqlite.go:4:2: cannot find package "github.com/augmentable-dev/gitqlite/cmd" in any of:
        /usr/lib/go-1.10/src/github.com/augmentable-dev/gitqlite/cmd (from $GOROOT)
        /home/erez/go/src/github.com/augmentable-dev/gitqlite/cmd (from $GOPATH)

Hmm... Does the same error occur when running make and make build?
I think there may be a problem with the version of golang. I am using Ubuntu 20.04 on wsl2, and the version of go is:
$ go version
go version go1.13.8 linux/amd64

Mine was
go version go1.10.4 linux/amd64

It's what apt install golang gave me.
Upgrading manually to 1.14 solved it, but now it's missing sqlite bindings:
$ go build
# github.com/augmentable-dev/gitqlite/pkg/gitqlite
pkg/gitqlite/git_log.go:21:70: undefined: sqlite3.VTab
pkg/gitqlite/git_log.go:49:71: undefined: sqlite3.VTab
pkg/gitqlite/git_log.go:55:31: undefined: sqlite3.VTabCursor
pkg/gitqlite/git_log.go:82:39: undefined: sqlite3.InfoConstraint
pkg/gitqlite/git_log.go:82:68: undefined: sqlite3.InfoOrderBy
pkg/gitqlite/git_log.go:82:91: undefined: sqlite3.IndexResult
pkg/gitqlite/git_ref.go:20:70: undefined: sqlite3.VTab
pkg/gitqlite/git_ref.go:34:71: undefined: sqlite3.VTab
pkg/gitqlite/git_ref.go:58:39: undefined: sqlite3.InfoConstraint
pkg/gitqlite/git_ref.go:58:68: undefined: sqlite3.InfoOrderBy
pkg/gitqlite/git_ref.go:58:68: too many errors

If you can use Docker, you can use how to build binaries within Docker. It builds in a clean environment, so it will probably succeed. :)
Dockerfile:
FROM golang:1.14

RUN cd / && \
   git clone https://github.com/augmentable-dev/gitqlite.git && \
   cd /gitqlite && \
   make build

Run:
docker build -t gitqlite-build .
docker run --rm gitqlite-build cat /gitqlite/gitqlite > gitqlite
chmod a+x gitqlite
sudo cp gitqlite /usr/local/bin

I hope you will go well!

I mean, it shouldn't be that hard to install.
I was thinking of using this as an added feature in my project. But if my users will need a docker just to use it, it's probably not worth it.
But thanks for taking the time, and cool idea.

Ah, I confirmed that the required option is missing from the command you gave. Also I confirmed that if required option -tags=sqlite_vtable is missing, then the build fails with the exact same error log.
$ go build -tags=sqlite_vtable gitqlite.go

Hi @erezsh please try running make build with your newly upgraded go version (I'm guessing the build failure you experienced on go1.10 was due to the project not being cloned into your GOPATH, but I could be wrong). go1.14 shouldn't have this requirement and make build will run exactly what @youngminz commented to produce a binary.
I'm sorry it wasn't super easy to setup! I know the installation docs could use some work. I've been thinking about how best to distribute this as well and hope to add a homebrew installation at least.
Thanks for taking the time and hopefully the experience can be improved!

make build worked. Of course I still had to chdmod +x and copy it to the bin folder.
Any idea what I'm doing wrong in this query?
gitqlite "SELECT count(*) FROM commits WHERE [AUTHOR NAME] == 'foo' "
no such column: AUTHOR NAME

@erezsh try gitqlite "SELECT count(*) FROM commits WHERE author_name == 'foo' "
The README also enumerates the column names: https://github.com/augmentable-dev/gitqlite#commits FYI

That's great, I just learned Wednesday is my most productive day, commit-wise :)
SUM(additions) is very slow for some reason, but other than that everything's working pretty well!

@erezsh haha nice! Yes, it's a known issue currently that pulling out commit stats (additions/deletions) is an expensive operation (unfortunately). I have a note to investigate, but a solution probably lies in a change the go-git dependency somewhere/somehow.
I'm going to close out this issue as I think your original ask was answered? The installation instructions do need some love, so that will be improved soon (note the TODO there)


docs: fix contributing guide

Feature or Bugfix

Enhancement

Contributing guide is outdated. Successfully tested Mocked Tests section on my local machine.
Detail

Fix contributing guide

Relates

#2035

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 971a96dd5f8038e1bf196d2b3a032020ccac0799
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


stress: cleanup async goroutine

Codecov Report

Merging #272 into master will increase coverage by 0.36%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #272      +/-   ##
==========================================
+ Coverage   99.01%   99.38%   +0.36%
==========================================
  Files          70       26      -44
  Lines        3057     1308    -1749
==========================================
- Hits         3027     1300    -1727
+ Misses         16        4      -12
+ Partials       14        4      -10

Flag
Coverage Δ

#dot
99.38% <100%> (+0.36%)
:arrow_up:

#dot_changes
100% <ø> (ø)
:arrow_up:

#dot_changes_diff
100% <ø> (ø)
:arrow_up:

#dot_changes_run
100% <ø> (ø)
:arrow_up:

#dot_changes_table
100% <ø> (ø)
:arrow_up:

#dot_changes_types
100% <ø> (ø)
:arrow_up:

#dot_example
100% <ø> (ø)
:arrow_up:

#dot_ops
97.97% <ø> (+0.09%)
:arrow_up:

#dot_ops_bolt
97.67% <ø> (ø)
:arrow_up:

#dot_ops_nw
?

#dot_ops_pg
?

#dot_refs
?

#dot_streams
?

#dot_streams_undo
?

#dot_test_seqtest
?

#dot_x_dotc
?

#dot_x_fold
?

#dot_x_heap
?

#dot_x_rt
?

#dot_x_ui_collab
?

#dot_x_ui_dom
?

#dot_x_ui_html
?

#dot_x_ui_input
?

Impacted Files
Coverage Δ

client.go
100% <100%> (ø)
:arrow_up:

streams/undo/stream.go

streams/scheduler.go

x/dotc/structs.go

x/dotc/union.go

x/dotc/slice.go

streams/s16.go

x/ui/collab/node.go

refs/caret.go

ops/nw/server.go

... and 35 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #272 into master will increase coverage by 0.36%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #272      +/-   ##
==========================================
+ Coverage   99.01%   99.38%   +0.36%
==========================================
  Files          70       26      -44
  Lines        3057     1308    -1749
==========================================
- Hits         3027     1300    -1727
+ Misses         16        4      -12
+ Partials       14        4      -10

Flag
Coverage Δ

#dot
99.38% <100%> (+0.36%)
:arrow_up:

#dot_changes
100% <ø> (ø)
:arrow_up:

#dot_changes_diff
100% <ø> (ø)
:arrow_up:

#dot_changes_run
100% <ø> (ø)
:arrow_up:

#dot_changes_table
100% <ø> (ø)
:arrow_up:

#dot_changes_types
100% <ø> (ø)
:arrow_up:

#dot_example
100% <ø> (ø)
:arrow_up:

#dot_ops
97.97% <ø> (+0.09%)
:arrow_up:

#dot_ops_bolt
97.67% <ø> (ø)
:arrow_up:

#dot_ops_nw
?

#dot_ops_pg
?

#dot_refs
?

#dot_streams
?

#dot_streams_undo
?

#dot_test_seqtest
?

#dot_x_dotc
?

#dot_x_fold
?

#dot_x_heap
?

#dot_x_rt
?

#dot_x_ui_collab
?

#dot_x_ui_dom
?

#dot_x_ui_html
?

#dot_x_ui_input
?

Impacted Files
Coverage Δ

client.go
100% <100%> (ø)
:arrow_up:

streams/undo/stream.go

streams/scheduler.go

x/dotc/structs.go

x/dotc/union.go

x/dotc/slice.go

streams/s16.go

x/ui/collab/node.go

refs/caret.go

ops/nw/server.go

... and 35 more

Continue to review full report at Codecov.

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


fix: recreate watchers after nats connection reset

if the nats connection is reset we need to recreate the watchers, otherwise the watcher stops getting updates.
fixes #864

don't we need locks to update connections?

closing this since this is handled in #889


Fix crash in ScriptRule parsing when PowerShell help system is not initialized on a machine

Verified the fix in elevated/non-elevated environment with/without help system initialization

Changes look good. One question I have is that will adding update-help impact the perfomance? Will it hang a few seconds?

The perf impact is negligible because of:
I am looking for help for a specific module - so not all help is downloaded
the help does not exist out the box for this module - so no help files are downloaded
Verified this on a clean-install machine.

Also, the build is failing since appveyor changes are not integrated with BugFixes

But do we need to call update-help each time when we import customized rule? Is there a way to only download help when there was no "get-help"?

Update-Help optimizes this. it sets up a registry key after the first time.


issues with lock scripts like i3lock, slock, etc

so i've noticed that scripts like i3lock dont activate the camera until after a password is entered. even then, the module fails with this error:
'Data files have not been downloaded, please run the following commands:

	cd /lib/security/howdy/dlib-data
	sudo ./install.sh

Traceback (most recent call last):
  File "/lib/security/howdy/compare.py", line 219, in <module>
    face_locations = face_detector(gsframe, 1)
TypeError: 'NoneType' object is not callable
Data files have not been downloaded, please run the following commands:

	cd /lib/security/howdy/dlib-data
	sudo ./install.sh

Traceback (most recent call last):
  File "/lib/security/howdy/compare.py", line 219, in <module>
    face_locations = face_detector(gsframe, 1)
TypeError: 'NoneType' object is not callable'

However, it works in all other applications, and I do have the data files downloaded. i'm not sure what is going wrong, or if this is somethibng that is related to my config, but if you could please breifly explain what is happening and why, that would literally make my day. thanks!
I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): ubuntu 18.10
Howdy version: latest as of april 1st 2019

Looks like PATH is not pointing to the right folder. Could you add the following statement to compare.py on line 26: (don't forget the tab)
	print(PATH)

What does it print in the error?

/lib/security/howdy
Data files have not been downloaded, please run the following commands:

	cd /lib/security/howdy/dlib-data
	sudo ./install.sh

Traceback (most recent call last):
  File "/lib/security/howdy/compare.py", line 219, in <module>
    face_locations = face_detector(gsframe, 1)
TypeError: 'NoneType' object is not callable

Its the same error. the files are there, but it just is giving that error.

This is the same issue as discussed here, closing this for now to keep the discussion in 1 place.

I don't think this is the same issue as #174, I still have this issue in Ubuntu 18.03 using howdy 2.5.1.
The dlib-data files are in /lib/security/howdy/dlib-data and howdy works fine for sudo, logging in using gdm, unlocking screenlock in Gnome, but not for i3lock or slock.
Could it be some kind of permission issue?

The dlib-data directory had root:root 0744 permissions, meaning that a normal user cannot access any of the files in the directory, except seeing that they are there, even though the files themselves are readable by any user.
Changing the permissions to 0755 fixes the problem.
I don't know what the security implications would be for doing this?


Support for this._super within serializer methods

It would be nice to be able to do:
import BaseSerializer from './application';

export default BaseSerializer.extend({
  serialize(response, request) {
    // something custom
    this._super(response, request);
  }
});

Currently, I just get
this._super() is not a function

Right now extend is taken from Backbone, because (1) I didn't want Mirage to rely on Ember.Object (idea was to be able to extract Mirage from EmberCLI Mirage) and (2) I didn't use ES6 classes since they don't support property declarations.
Backbone's docs say you should be able to explicitly call the parent, so try something like this:
export default BaseSerializer.extend({
  serialize(response, request) {
    // something custom
    BaseSerializer.prototype.serialize.apply(this, arguments);
  }
});

I'm closing this.


Re-evaluate register_test_contract / register_wasm_contract

What problem does your feature solve?
These functions are now bespoke relative to the broader deployer mechanism recently added.
What would you like to see?
We might be able to unify this with the deployer mechanism.
What alternatives are there?
N/A

While working on examples and docs updates it occurred to me that using the deployer will actually make the code more ergonomic. Although it also highlighted to me that we might still need some bespokeness.
For example, this is littered throughout our tests:
let env = Env::default();
let contract_id = BytesN::from_array(&env, &[0; 32]);
env.register_contract(&contract_id, Contract);

But with a change to deployer we could have:
let env = Env::default();
let contract_id = env.deployer().from_test().deploy(Contract);

The side-effect improvements are:

Teaching the developer where real deploys happen.
No need to create fixed contract IDs, which is not intuitive.

This is likely to get overhauled soon because @dmkozh is currently reworking deployment with the env crates.


Remove chain operator

The chain operator is kinda confusing, and I think its uses could be fulfilled by an upcoming 'then' operator instead. So maybe remove it?

What sets the chain operator apart from the then operator?

You used the ++ chain operator as part of a term definition. But the ... then operator can be used as part of a match sequence, so should be more intuitive.
With the chain operator:
Language (
    ++ Sanitise
    :: Expression
)

With the then operator:
Language :: Sanitise ... Expression

Hmm, yes I can see why that would be intuitive, but I can't help but shake the feeling that ... means that something else is omitted between the terms, like "This term makes no difference, it can be anything". Maybe using a , could work instead?

Yes that's true! A different thing would probably be better. The language has really turned into 'symbol hell' so maybe even then would be good.
Language :: Sanitise, Expression

Language :: Sanitise then Expression

Language :: Sanitise & Expression

Language :: Sanitise && Expression

Language :: Sanitise and Expression

I think then would probably work best actually, as it's clearer as to what it does, whereas and could be interpreted as a sequence of terms, which in actuality is just a space

I'll try it out!
Also, maybe the 'any' keyword/symbol could be 'anything that is not the following term'. I'd need to make a 'not' operator or something. Not sure how it would totally work though 🤔

Closing because of upcoming rewrite


API response should include reference to schema, to be completed first

We (Fawzi, Andrius, Markus, Matt, Leopold) propose that the API response should include a reference to  a schema that can be used to validate its responses.
This can include one or two of:

a JSON schema
a NOMAD meta-info schema

Advantages:

machine-readable way for clients to understand the (intended) response format, including custom extensions

Disadvantages:

none that we are aware of

@blokhin Could you please explain your reservations about this point?

@ltalirz I do appreciate this suggestion, just cannot immediately comprehend what are the benefits of choosing the NOMAD's option vs. general-purpose JSON schema.

Ok, I would say this is a separate issue from having a link to a schema in the response.
Obviously the question of which schema to use should be considered carefully, and we did not want to exclude either option during the session. A discussion of the pros and cons of both approaches can be found in the meeting minutes on Google Docs under  Schema, implementation, and testing routines

@ltalirz could you post a link to that document? It's not among those two mentioned at the API repo.

OK, received 👍 pity it's not public.

Would it be possible that API response follow a certain specification ? For example, Citrine Informatics proposed a Materials Information File (MIF) , which is an open JSON-based file format (available at http://citrineinformatics.github.io/mif-documentation ) that we could use. It seems it could be used as a schema for representing the query data output.
An associated paper , entitled " Materials science with large-scale data and informatics: Unlocking new
opportunities " can be found at MRS BULLETIN • VOLUME 41 • MAY 2016 • www.mrs.org/bulletin .

@kxyyang +1 for MIF/PIF, we do already use it for quite some time to represent physical properties in our API.

I'm very much in favor of relying on existing standards but the MIF clearly seems tailored towards representing experimentally measured structures. For example, it doesn't seem to have the concept of atomic positions (other than returning a cif file), so it is not clear to me whether it is a good match for optimade at this point.
However, if someone wants to point out specific terms that could easily be aligned between the two formats to avoid confusion, I'm sure this would have widespread support.

Perhaps it is a good idea to collect somewhere (the wiki?) a list of already defined output formats / return values / materials science ontologies that one may want to keep an eye on as we try to standardize things for OPTIMaDe? So far I'm aware of:

The CIF dictionaries
Electronic Structure Common Data Format
NOMAD Meta Info
Pauling file vocabulary and common terms for phase diagrams
Terms/return values already used in the larger database projects but seemingly defined less stringently than those given above, e.g, Materials project, Aflow, oqmd, materials cloud, etc.
The ontology that was presented in a talk during one of the later days in the OPTIMaDe workshop. I have some difficulty to find hard info on the Internet, but I found this: EMMO from EMMC?
And now then Materials information file

@rartino Great suggestion!
Let me mention that there is a newly formed "Semantic Assets for Materials Science" task group in the Research Data Alliance, and their first point of action will be exactly to collect semantic assets (keyword lists, taxonomies, ontologies) from the field of materials science, likely on the NIST materials registry.
They haven't started yet, though, and there is no reason to wait - once this registry has been established we will simply move our list there.
I've already put your list onto the wiki, feel free to edit!
P.S. If anyone would like to join the task group, contact Vasily Bunakov from the STFC.

Currently MIF does not support the definition of crystalline structure. But as said " A number of key objects have already been defined to encompass common materials concepts (e.g., materials, measurements, phases, phase diagrams), and new objects can be readily created as needed."  It says we could define new object.  So how about we extend the MIF schema by defining a "crystal structure"  object ? And the definition of this "crystal structure" object could link to what we discussed about defining the crystal SYSTEM at the workshop.

Citrine Informatics also proposed an Physical Information File (PIF), which is a schema that is designed to impose structure on information about physical systems (http://citrineinformatics.github.io/pif-documentation/index.html).  Not sure whether this support the definition of crystalline structure... Worth investigating.

I've started preparing a PR so we can actually link the schema in a reply in a standardized way.
I see two ways we can do this:
Alternative 1
It turns the upcoming v1.1 of JSON API have adopted an official way to do this in json-api/json-api#1447. They define a new link type for the top level links field:
"links": {
    "describedby": "http://schemas.optimade.org/v1.0.0/structures.json",
}

We can allow for this, but technically we are then breaking the JSON API v1.0 specification, which says that we are not allowed to provide any other members in these fields than as described by the specification:

Unless otherwise noted, objects defined by this specification MUST NOT contain any additional members.

However, also note this:

Client and server implementations MUST ignore members not recognized by this specification.

Which means that if we add this "extension" to JSON API v1.0, it should not break any well-behaving JSON API v1.0 tools, because they are ordered to ignore our extra member.
Alternative 2
If we want to strictly adhere to JSON API v1.0, the most sensible place to put this is in the top level meta field, since that is allowed to include whatever we want

Where specified, a meta member can be used to include non-standard meta-information. The value of each meta member MUST be an object (a “meta object”). Any members MAY be specified within meta objects.

I.e., this would be ok:
"meta": {
    "schema": "http://schemas.optimade.org/v1.0.0/structures.json"
}

@ltalirz, @giovannipizzi, @sauliusg, @blokhin: Any thoughts on the two alternatives above?


Add support for better detection of libsodium at build time?

is this something people would want?

Yes! It has to at least build on OSX.
Use pkg-config to get the correct compilation flags: https://github.com/GoKillers/go-nacl/pull/5

What about Windows? The Go build system is pretty weird to me. I think it can improve with time.

Closing for now.


test_groupnorm_sharded_narrow_channel_per_group PCC mismatch without L1 clear

For minimum repro, on Grayskull:
git checkout main
TT_METAL_CLEAR_L1=0 pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_groupnorm_sharded.py

This test is for group norm V1, which is no longer used. Will likely be removed soon, no need to fix

no longer has the v1 version


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(devDependencies): update<EMAIL_ADDRESS>from template

Coverage remained the same at 92.308% when pulling e47cab59adeca4eb1d5cf56263329b5980b323a1 on template-sync-1 into 909e306582b1cf46e6beba1aed6b6b0df70ca6f4 on master.


Movies Classification using DL

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Movies Classification
:red_circle: Aim : Classify different genres of movies using deep learning approaches.
:red_circle: Dataset : https://www.kaggle.com/datasets/akshaypawar7/millions-of-movies
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Full name : Vandana Kumari
GitHub Profile Link : https://github.com/Myworld21
Email ID<EMAIL_ADDRESS>Approach for this Project : I will extract numerical features from the textual movie descriptions using techniques like TF-IDF or word embeddings. We then select some deep learning algorithms: Convolutional Neural Networks (CNNs), Recurrent Neural Networks (RNNs), Transformers. These algorithms are trained on the preprocessed data. After training, we compare the models based on metrics such as accuracy, precision, recall, and F1-score. Considering factors like accuracy, training time, and model complexity, we determine the most suitable deep learning algorithm for movie genre classification.
What is your participant role? (Mention the Open Source program) SSOC Participant Season 2

Hi @Myworld21  nice to have you here. I like your approach for solving this issue. This issue will be assigned to you once the program starts officially.
Till then, star the repository and explore more in open source.

Issue assigned to @Myworld21

kindly assign me the issue .
I'd leverage Recurrent Neural Networks (RNNs) on movie overviews alongside genre labels for text-based analysis,.

Make sure you use atleast 2-3 models/methods for this project and find out the best fitted model based on the highest accuracy score.
Issue assigned to you @Dhruv127

Full name : D. Uday Kiran
GitHub Profile Link : https://github.com/the-silent-geek
Email ID<EMAIL_ADDRESS>Approach for this Project : This can be implemented by using models like cnn,rnn, and LSTM.
What is your participant role? social winter of code 23

Full name : Dipayan Majumder
GitHub Profile Link : github.com/dipayan22
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project : I will extract numerical feature from the textual data using TF-IDF , Word Embedding .Then i will used some deep learning algorithms likes RNN , Lstm ,transformer bert etc.
What is your participant role? (Mention the Open Source program) SWOC 24

Assigned to @dipayan22 under SWOC S4.

hey @abhisheks008 i can't upload the Dataset file .Because it's too large . Can upload the link of the kaggle of in dataset file . please assist me.


Update the class style and added an alternative bibliography style

The current class style follows the W&M physical standards (Summer 2024, except it is not sans serif) to make it required pages sans serif the commands \sffamily and textsf would need to be added where appropriate

The bibtex style file 'wmbib_nosrt_wurl.bst' does not sort the bibliography alphabetically, and adds a link if the doi field is present in the entry and the hyperref package is being used.

So I am going to close this pull request and add the changes myself. There are some things in the merge request that I do not wish to include. But I will include your changes to the bibliography style and the change for the Appendices.


[SEDONA-229] Remove Duplicate String Check

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-229.

What changes were proposed in this PR?
This PR disables the scalastyle check called MultipleStringLiteralsChecker. This check is responsible for detecting multiple occurrences of the same string literal in the same file. From what I could gather, the reason for this check is to detect potential cases of "magic numbers" or constants that should be consolidated into a constant variable. There are three issues with this check:

There is a bug in the check which flags fragments of interpolated strings as duplicates even though the string as a whole is not a duplicate.
The main offender for this check are the tests. This is because of very common column names like "geom". The mass majority of these checks are false alerts. There was one instance of this check flagging non-test code and it provided little value to fix it.
Spark SQL uses a lot of strings and I wouldn't call it bad practice to do so.

This check did reveal some refactor points in the tests, but I would think that folks could already see that the tests could use some refactoring. In other words, this check doesn't flag anything that isn't obvious without it.
I did give a go at removing all duplicate strings for the sedona-sql module and it led to some really ugly constant declarations in the test classes. Some nice refactors of the tests did fall out, and I will try to PR those once the linter messages are cleaned up.
How was this patch tested?
Ran the standard build process. This doesn't change any actual code.
Did this PR include necessary documentation updates?

No, this PR does not affect any public API so no need to change the docs.

Well, I was finally able to get to putting these PRs up. This is just one of several more to clean up the linter messages.


require-date

Was causing the following:
  /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler.rb:489:in `rescue in eval_gemspec':  (Bundler::GemspecError)
  [!] There was an error while loading `shutterstock-ruby.gemspec`: uninitialized constant Date
  Did you mean?  Data. Bundler cannot continue.

   #  from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/bundler/gems/shutterstock-ruby-17972c5d4add/shutterstock-ruby.gemspec:8
   #  -------------------------------------------
   #    s.platform    = Gem::Platform::RUBY
   >    s.date        = Date.today.to_s
   #    s.summary     = "An API wrapper for the Shutterstock API's"
   #  -------------------------------------------
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler.rb:481:in `eval_gemspec'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler.rb:423:in `block in load_gemspec_uncached'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/shared_helpers.rb:55:in `chdir'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/shared_helpers.rb:55:in `block in chdir'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/shared_helpers.rb:54:in `chdir'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler.rb:422:in `load_gemspec_uncached'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler.rb:408:in `load_gemspec'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/source/git.rb:243:in `block in serialize_gemspecs_in'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/source/git.rb:239:in `each'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/source/git.rb:239:in `serialize_gemspecs_in'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/source/git.rb:162:in `specs'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/lazy_specification.rb:75:in `__materialize__'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/spec_set.rb:84:in `block in materialize'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/spec_set.rb:81:in `map!'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/spec_set.rb:81:in `materialize'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/definition.rb:159:in `specs'
  	from /opt/rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/gems/bundler-1.15.0/lib/bundler/definition.rb:140:in `resolve_with_cache!'
  	from /opt/elasticbeanstalk/support/scripts/check-for-gem.rb:22:in `<main>'

🚢


Lark gives too meaningful names to terminals equal to punctuation characters, but this may not be always wanted

Consider the following script that simply displays the parse tree for the grammar given later in G2.txt:
# G2.py
import lark

def non_standalone(code, parser=lark.Lark(open('G2.txt').read(), parser='lalr')):
    return parser.parse(code)

root = non_standalone("(not a parenthesis!(not a parenthesis!))")

print(root.pretty())

Here's the first version of G2.txt:
WHATEVER: "not a parenthesis!"

start: WHATEVER start? | "(" start ")"

Here's the output of python3 G2.py:
start
  start
    not a parenthesis!
    start
      start	not a parenthesis!

This works as expected. Now let's go a bit crazy.

Here's the second version of G2.txt:
LPAR: "not a parenthesis!"

start: LPAR start? | "(" start ")"

Yeah, LPAR is not a Left PARenthesis at all, but this should be acceptable, to my mind.
Here's the exception raised after running python3 G2.py:
Traceback (most recent call last):
  File "G2.py", line 9, in <module>
    root = non_standalone(code)
  File "G2.py", line 4, in non_standalone
    return parser.parse(code)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/lark.py", line 223, in parse
    return self.parser.parse(text)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/parser_frontends.py", line 38, in parse
    return self.parser.parse(token_stream, *[sps] if sps is not NotImplemented else [])
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/parsers/lalr_parser.py", line 68, in parse
    for i, token in enumerate(stream):
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/lexer.py", line 259, in lex
    for x in l.lex(stream, self.root_lexer.newline_types, self.root_lexer.ignore_types):
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/lexer.py", line 105, in lex
    raise UnexpectedCharacters(stream, line_ctr.char_pos, line_ctr.line, line_ctr.column, state=self.state)
lark.exceptions.UnexpectedCharacters: No terminal defined for '(' at line 1 col 1

(not a parenthesis!(not a parenthesis!))
^

When LPAR in the grammar above is replaced by RPAR, a similar exception is raised:
# identical lines omitted...
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/lark_parser-0.6.4-py3.6.egg/lark/lexer.py", line 105, in lex
    raise UnexpectedCharacters(stream, line_ctr.char_pos, line_ctr.line, line_ctr.column, state=self.state)
lark.exceptions.UnexpectedCharacters: No terminal defined for ')' at line 1 col 39

(not a parenthesis!(not a parenthesis!))
                                      ^

While using Lark, I noticed that it names anonymous (anonymous!) terminals (like "(" and ")") in "(" start ")" and the names are very meaningful (LPAR and RPAR in this case; there are probably many more). Apparently, when you use these names explicitly in your grammar, the two tokens (auto-generated by Lark and created by user) somehow collide, which messes up the parse.
As I've just found, the names of such terminals are defined here
However, other anonymous terminals, which aren't equal to punctuation characters, (like "if" in "if" expr relop expr block) can very well be handled without meaningful internal names:
import lark

GRAMMAR = '''
IF: "not an 'if' keyword!"
ELSE: "not an 'else' keyword!"

start: "if" start "then" ELSE "else" IF | IF

%ignore " "
'''

def non_standalone(code, parser=lark.Lark(GRAMMAR, parser='lalr')):
    return parser.parse(code)

code = "if not an 'if' keyword! then not an 'else' keyword! else not an 'if' keyword!"

root = non_standalone(code)
print(root.pretty())

Running this yields the expected tree:
start
  start	not an 'if' keyword!
  not an 'else' keyword!
  not an 'if' keyword!

Thanks for the bug report! I pushed a fix to master, it should behave correctly now.


update(plugins/cloudtrail): Increase our default S3 concurrency

Change the default value of S3DownloadConcurrency from 1 to 32. This improves performance noticeably here.

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area plugins

/area registry

/area build

/area documentation

What this PR does / why we need it:
This sets the default download concurrency to 32. This improves performance significantly in my tests here.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geraldcombs, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

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

LGTM label has been added.  Git tree hash: 5d77d568e93c38b90669726b9158bc291d937625


feat(config): use first available open port if PORT env variable unset

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
591

Relevant Lines:
591

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
591

Relevant Lines:
591

💛  - Coveralls


can it use not in a FragmentActivity？

I guess it's a really late answer, but it might help others. I made it work on a fragment by using the activity support fragment manager like this:
((MainActivity) getActivity()).getSupportFragmentManager()


raylib: fix missing sound

Description of changes
Fixes #327747

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@ofborg eval

Maybe I should've waited on Darwin, but hopefully it's all ok.

I assume it's fine as those flags are only enabled by default on Linux, hence shouldn't affect Darwin here.


Is posssible to get work with dvr and thumbnail at the same time?

as above,
Kind Regards

Thumbnails in dvr mode are not supported


Ultisnips - When documentation is true and shown, you cannot jump to the next snippet placeholder

Checkhealth
health#compe#check
========================================================================
## compe:snippet
  - OK: snippet engine detected.

## compe:mapping
  - INFO: `compe#complete` is not mapped
  - OK: `compe#confirm` is mapped: (`i  <CR>        * compe#confirm('<CR>')`)
  - INFO: `compe#close` is not mapped
  - INFO: `compe#scroll` is not mapped

Describe the bug
The bug happens when you select one autocomplete option and the documentation tooltip appears. This disables completely current snippet placeholders, making it unusable.
I suspect the problem happens due to the new buffer created for the documentation.
To Reproduce
vimrc
call plug#begin('~/.config/nvim/plugged')

Plug 'SirVer/ultisnips'
Plug 'hrsh7th/nvim-compe'

call plug#end()

set completeopt=menuone,noselect

let g:compe = {}
let g:compe.enabled = v:true
let g:compe.autocomplete = v:true
let g:compe.min_length = 1
let g:compe.preselect = v:false

let g:compe.source = {}
let g:compe.source.path = v:true
let g:compe.source.buffer = v:true
let g:compe.source.ultisnips = v:true

Expand an Ultisnips snippet with multiple placeholders.
Write something to show the autocomplete options and select one option that displays documentation.

Note: It works correctly when documentation is false.
let g:compe.documentation = v:false

Actual behavior
You're unable to jump to the next placeholder, making Ultisnips basically useless.
Expected behavior
It should jump correctly between placeholders.
Screenshots
Documentation enabled

Documentation disabled

Hm... I can't reproduce it.
https://user-images.githubusercontent.com/629908/128537094-6b375dd6-268d-4632-a48d-9ddf62216819.mp4

It happens after the snippet is expanded. For example, when you are inside href="|", select an autocomplete option that shows documentation (like another snippet or lsp function).

Also... I'm starting to think that this could be a Ultisnips bug. After disabling the documentation, I have another plugin that shows a popup and breaks the placeholder jump too. Still, please take a look. I would like to get your opinion about it. Thanks.

Probably, I found the reason. It caused by Ultisnips#ExpandSnippet. If current activated snippet can jumpable, the function would not effect anymore.

I think we can close this... Not a simple solution for now it seems. I found this one on Ultisnips https://github.com/SirVer/ultisnips/issues/1188


Call stop in beforeDestroy lifecycle hook

This is to prevent camera from staying on when the vue-web-cam component is destroyed.

@hullalex-tek Thank you! I'll get that in there today.

In regards to this second commit, testMediaAccess created a MediaStream that never gets stopped. This means that navigating away from the page would cause the browser to think it is still accessing the camera. I thought for a long time that testMediaAccess was useless, so I attempted to remove it. However, I noticed that on an iPad running safari, it would cause only the front facing camera to work, and you wouldn't be able to switch. I don't fully understand how it does anything meaningful.

@hullalex-tek At the time, it was used to emit the error event as soon as the camera is mounted as well as load the available cameras into the data property. If you have a better way to handle this feel free to make a change that won't break the current implementation.

Not sure of a better way, interestingly enough it seems that without it, my iOS devices running safari don't work.


I made a game for Sprig

Your checklist for this pull request
Author name
Alexxalla
Author:
Alexxalla
About your game
What is your game about?
Avoiding obstacles, using wasd you are supposed to avoid the incoming asteroids
How do you play your game? WASD
Code
Check off the items that are true.

[ x] The game was made using the Sprig editor.
[x ] The game is placed in the in the /games directory.
[x ] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[ x] The game runs without errors.
[ x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x ] The game name is not the same as the others from gallery

Image (If an image is used)

[x ] The image is in the /games/img directory.
[ x] The name of the image matches the name of your file.

Thanks for your PR!
I want a free Sprig 👍

I made gud game. ^^;


Fab deps

Tidies up the dependencies between the conda and setup.py:

The setup.py extras section has packages for general dev.
The earliest clang release available at MO, 8.0.1, tested and added to conda env.

python-clang not added to setup.py because it seems better to install it alongside the linux libclang package so we can match versions. Might be worth a chat about this.

Looks good, just one question about run-configs.sh; Are the commented out build scripts/flags being left in for development purposes? If so, I'm hsppy to approve this.

Yes that's right. The whole script has been replaced with a simpler Python version in another PR anyhoo.


🤖✨ : add all fonts

add all fonts - normal/italic and font weight + change 'a' color
add font styles

change link color in <LandingHeader />

thank you @fyodorio ! I’m looking forward to help contributing more on styling, this is interesting ! 👍🏻

Sure, I'll let you know as soon as I move forward a little bit, if you'll still be interested of course. Cannot find enough time for that yet, unfortunately.


fix cert parsing for ios 12

Connection with issue(s)
Resolve issue #524

Connected to #631

Testing and Review Notes

Build and run in iOS 12 with HTTPS site, expected to stop triggering ASN1ParseError and properly retrieve value from getCertificate.
Screenshots or Videos

To Do

[x] double check the original issue to confirm it is fully satisfied
[x] add testing notes and screenshots in PR description to help guide reviewers

@all-contributors please add @darkang3lz92 for code


Add a released event to widget Responses

Is your feature request related to a problem? Please describe.

I want to be able to drag and drop files inside a widget (like TextEdit for example) but the thing is currently there is no way to find out if the dragged files released inside a specific widget. I tried to use is_pointer_button_down_on for this job, but this function only return true if button pressed/released when hovering on the widget (in other word if I drag a file at top of a widget then release mouse button to drop it, it dont receive any release event...), so I think a released Response that return true when ever a button released at top of it would be good.
Describe the solution you'd like

Having a new function named released that return true when a button released at top of widget.
Describe alternatives you've considered

change is_pointer_button_down_on functionality in order to return true in case that a button released at top of it (and not just when it first hovered on it) although I don't think its a good Idea... having a specific function would be better.
Additional context

()

is https://docs.rs/egui/latest/egui/struct.Response.html#method.drag_released what you want?

is https://docs.rs/egui/latest/egui/struct.Response.html#method.drag_released what you want?

no I was talking about system drag and drop (drag and drop a file from for example windows explorer to program), not the drag and drop inside program itself
Here is the example but the thing is I want to be able to drop files in separate widget, like having multiple input widget that user can drag files into them separately.


New version: StaticPolynomials v1.3.0

Registering package: StaticPolynomials
Repository: https://github.com/JuliaAlgebra/StaticPolynomials.jl
Created by: @saschatimme
Version: v1.3.0
Commit: d0b8b07f297517eeae11b7be3f7df60373e45a32
Reviewed by: @saschatimme
Reference: https://github.com/JuliaAlgebra/StaticPolynomials.jl/commit/d0b8b07f297517eeae11b7be3f7df60373e45a32#commitcomment-33629862

Can you keep the julia constraint? E.g. add
[compat]
julia = "0.7, 1"

to the project file and retrigger the bot?


Contract storage using code gen macro pattern

Motivation
We would like a nice way to define contract storage layout, methods etc. We don't want to go too far from the rustish way of doing things. Solidity offers a "batteries includes" approach with storage whereby storage is affected by variable definition and use. While this is kinda nice, it becomes harmful as it's hard to differentiate between what is an in memory variable and an in storage variable.
This is simply meant to open up a bike shed discussion around storage for the interim.
Solution
Below is an idea for contract storage using a generator / macro like pattern.
Note, I introduce a kind of odd mapping method / concept here, where by an interpreted function signature is used to build the hash mapping. Not sure if this is a very rustish approach.
What I like about this pattern is it's a generator pattern, and all it does is generate a nice set of methods for a contract to use.
contract;

// We import the storage macro and mapping type generator.
use std::storage::*;

////////////////////////////////////////
// ABI declarations
////////////////////////////////////////

/// ABI definition for a subcurrency.
abi Token {
    // Make the balances function public.
    fn balances(account: b256) -> (balance: u64);

    // Mint new tokens and send to an address.
    // Can only be called by the contract creator.
    fn mint(receiver: b256, amount: u64);

    // Sends an amount of an existing token.
    // Can be called from any address.
    fn send(sender: b256, receiver: b256, amount: u64);
}

////////////////////////////////////////
// Storage declarations
////////////////////////////////////////

/// The storage layout which will generate the necessary functions for storage.
/// You can think of this as essentially a proc macro like generator for storage.
/// The notation is similar to the `abi` and `struct` Rust notation.
storage Token {
    // The balances is a hash mapping, intakes fn sig, outputs mapping methods.
    balances: mapping(fn balances(account: b256) -> (balance: u64));
}

/*
// The generated set method.
fn set_balances(account: b256, balance: u64) {
    store(hash_pair(0, account, HashMethod::Sha256), balance);
}

// The generated get method.
fn get_balances(account: b256) -> (balance: u64) {
    get(hash_pair(0, account, HashMethod::Sha256), balance);
}
*/

////////////////////////////////////////
// Constants
////////////////////////////////////////

/// Address of contract creator.
const minter: b256 = 0x9299da6c73e6dc03eeabcce242bb347de3f5f56cd1c70926d76526d7ed199b8b;

////////////////////////////////////////
// ABI definitions
////////////////////////////////////////

/// Contract implements the `Token` ABI.
impl Token for Contract {
    fn balances(account: b256) -> (balance: u64) {
        get_balances(account)
    }

    fn mint(receiver: b256, amount: u64) -> bool {
        // Note: authentication is not yet implemented, for now just trust params
        if receiver == minter {
            let mut amount = get_balances(minter);
            amount = amount + amount;
            set_balances(minter, amount);

            true;
        } else {
            revert(0);
        }
    }

    fn send(sender: b256, receiver: b256, amount: u64) -> bool {
        let mut sender_amount = get_balances(sender);
        sender_amount = sender_amount - amount;
        set_balances(sender, sender_amount);

        let mut receiver_amount = get_balances(receiver);
        receiver_amount = receiver_amount + amount;
        set_balances(receiver, receiver_amount);

        true;
    }
}

Storage has been implemented now. Bikeshedding over mapping vs re-using HashMap can be done in a separate issue.


Some symbols missing in the ILP64 interface

@amontoison  and I seem to have found a bug. The sgeqp3rk and the cgeqp3rk subroutines seem to be missing in the ILP64 interface.
See output of nm from one of your computers
nm -D libopenblas64_.0.3.28.so | grep geqp3rk
00000000018fc4e0 T cgeqp3rk_
00000000017b2060 T dgeqp3rk_64_
000000000166da70 T sgeqp3rk_
0000000001a85f40 T zgeqp3rk_64_

I think that the symbols are just not correctly mangled (missing suffix 64_ for the ILP64 API).

Looks like I may have forgotten to add them to the gensymbol script, sorry.

No worries! Thanks for the swift response.

@martin-frbg When is 0.3.29 version release planned?

End of the year at the latest, maybe early next week if I can find the time (and nothing blocking comes up)

thanks! just checking. No rush!


Remove numbering of external resources, date-order

To ensure there's no bias to the "recommended" ordering of external
resources, use bulleted lists instead of numbered lists and order by
date.
Add dates to links for clarity when making updates. Add the date inside
the link, not after it, to avoid ugly wrapping that happens when long
link-text is followed by short non-link-text.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

@dfarrell07 With https://github.com/submariner-io/submariner-website/pull/519 merged, this has a conflict now


Add CTime and fix linkage error

…ently

Change Description

Add support for time in libc and some of libc++.  Also, fix regression that smart contracts fail to link when using std::stringstream
API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

As of commit #8310058, this now fails to link with std::stringstream on Mac OS X.  But, the issue is resolved for Linux and EOSIO smart contracts.

Replaced by #738.


AccountFollowers Feed doesnt return cursor and more available

AccountFollowers Feed doesn't return cursor and more available
Response from instagram:
{
"users":[],
"big_list":false,
"page_size":200
}

What do you think?

@aleks63 Сould you describe the issue in detail?

i think what he is saying is that on large lists AccountFollowers Feed will only return one long list of around 7500 followers
There is no pagination available to get more. i think this is coming from instagram's side?

yes, still 7500 , any updates ?


Deprecate SSLRedirectMiddleware

Since Django 1.8 added SecurityMiddleware, I don't believe there's any functionality provided by SSLRedirectMiddleware that isn't provided there? It looks like maybe SSL_FORCED_PREFIXES_ONLY isn't covered, but IMO it's not worth keeping an extra middleware around for just that functionality.

I share David's opinion. With free solutions like Let's Encrypt and the general recommendation of "HTTPS everywhere", it's best to put an entire site behind HTTPS at the server level.

+1 from me. Good idea David.
On Mon, 16 May 2016 at 10:50 PM, Ed Rivas<EMAIL_ADDRESS>wrote:

I share David's opinion. With free solutions like Let's Encrypt and the
general recommendation of "HTTPS everywhere", it's best to put an entire
site behind HTTPS at the server level.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/stephenmcd/mezzanine/issues/1600#issuecomment-219444979

Consensus! Let's do it.


关于 't-attn' 's-attn' 'ca-mlp' 选择

感谢开源，有一点关于配置的疑惑：现在的默认配置我理解是以blk_idx==13的‘s-attn' 的信息计算cache_rate，代表当前step全部的SA和TA，如果使用 't-attn' 's-attn' 'ca-mlp' 的差异求一个加权结果是不是会更合理，您有尝试过吗

Thank you for your interest in our work.
In our experiments, we observed that computing the cache-metric on either TA, SA, CA, or MLP residuals is not too different from eachother, but TA gives better quality-latency trade-offs in OpenSora (see ablation Table 3e in the paper). Computing the cache-metric at the middle of the DiT (blk_id = 13) was sufficient (see ablation Table 3d in the paper) in our experiments. We agrree that averaging this metric computed across all layers can be more reasonable, but it also introduces more latency overheads.


IsAlive on dead reference should be false

I found that IsAlive() on a reference to a deleted entity was returning true, leading to my code crashing.
I think the problem is that:

IsAlive() does a version check by comparing this with Entity.Reference(). So if Reference() returns null or a different version, IsAlive() will be false (so far so good...)
Reference() returns version 0 when an entity with a matching id is not found.
So if you have a reference to version 0 of an entity, IsAlive() will always return true for it.

I fixed my problem by making Reference() return EntityReference.Null when an entity is not found.
This had the follow-on problem that IsAlive() would return true for EntityReference.Null, so I added a special case for that.

Could possibly also do
    public EntityReference Reference(Entity entity)
    {
        var entityInfo = EntityInfo.TryGetVersion(entity.Id, out var version);
        return new EntityReference(in entity, entityInfo ? version : -1);
    }

Thanks for discovering and fixing that bug! :)


add option to show error details immediately in dot, list, min, and spec reporters

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions.

Description of the Change

Now if you run mocha with --reporter-options showErrorsImmediately=1 (or whatever string) the dot, list, min, and spec reporters will output error details immediately after test failure instead of after all tests have finished.
To support this I extracted a Base.logTestFailure function from Base.list so that reporters could call it with a single failed test when the showErrorsImmediately option is given.
I also made Base.prototype.epilogue not output error details if called with {listFailures: false}; the dot, list, min, and spec reporters use this to prevent error details from being output again at the end if they were already output inline.
Alternate Designs

I had considered making a third-party reporter package that logs errors immediately, but since Mocha doesn't provide a clean way to use multiple reporters at once, such a package wouldn't be very convenient.
I had also considered outputting errors immediately in other console reporters like landing, progress, and nyan, but since it would garble the appearance of their output I decided against it.
Why should this be in core?

It keeps this option consistent among reporters for which it is sensible to log errors immediately and ensures that immediate error details will have the same formatting as epilogue error details.
Benefits

Developers who have long-running tests will be able to use this option to see error details immediately upon test failure instead of waiting a long time for all tests to finish to see the error details.
Possible Drawbacks

Some users may be confused why other reporters don't support showErrorsImmediately.
Applicable issues

This is an enhancement (minor release)

Coverage increased (+0.1%) to 90.13% when pulling 7ef0c1b5c0f29f34eeb36e538775b180f720f096 on jedwards1211:immediate-errors into b7377b380202d2c0d5634dcb89dc50ea69961fb3 on mochajs:master.

Oh, I didn't know about the --bail option.  That might help, but I still think it might be convenient to keep running other tests while investigating why one failed.  I miss being able to see stack traces immediately  with tools like JUnit in the Java world...I don't really see why not have the option to get them as the tests run.  Also, does --bail --watch work?

I'll work more on this tomorrow, your comments all make sense

@boneskull the CI build is complaining of lint errors in CHANGELOG.md that aren't due to this PR, other than that it passed

@boneskull my current workaround for this is
const {reporters: {Base}} = require('mocha')

afterEach(async function () {
  if (this.currentTest.state === 'failed') Base.list([this.currentTest])
}

@boneskull are you waiting on anything for this?  The CI build failure was not this PR's fault.

Think use of --bail would eliminate much of need for this change.

Speak for yourself.  I'd like to be able to keep running the rest of my (numerous, slow) selenium integration tests while hunting down the cause of failures that have already occured.  Believe me, it would save me time.

Speak for yourself. [SNIP]

My apologies at having offended. My assumption you were using a CI environment. If so, you could run your suite both with and without --bail. From a testing perspective, the first error often causes a cascade. My point being that you could start working on any problem using the result of --bail while your long-running (--no-bail) version continues to test for everything else.

conflicts will need to be resolved ...

@plroebuck it's more convenient for me to just use the following semi-hack for now:
const {reporters: {Base}} = require('mocha')

afterEach(function () {
  const {state, title} = this.currentTest
  if (state === 'failed') {
    Base.list([this.currentTest])
  }
}

I just wanted to get this merged so I don't have to rely on internal API.

@boneskull okay, I resolved all the conflicts

@boneskull have you had any time to look into this? Sounds useful.

🤖 Closing out old PRs to keep the review queue small. Please yell at me if you need it re-opened and can continue working on it. Cheers!


mergre

@tickbox-smc Please a description to your PR and resolve the conflicts.

@tickbox-smc Such changes are not going to be part of this general-purpose module. Closing this PR.


support for lapack functions with mkl

Changes for using the lapack functionalities in MKL.

This is a backward compatible change that does not alter any existing behaviour except that linalg-operators will automatically use MKL-blas  whenever USE_BLAS=mkl is set (todays behaviour is  that the operators do not work at all in this case)

It also allows a user that has a complete installation of MKL (not only MKL2017/MKL_ML) to use MKL's lapack routines. This would still require some editing of configs and mshadows makefiles (as the configuration is currently not setup for using the whole MKL), but at least it is now doable.

In a second step, the make-system should be cleaned w.r.t. MKL-build, but  I would like to separate it from the C++ changes.

I have compiled mxnet in lapack_mkl version, and I got an error"spotrf failed in lapack on cpu" when using linalg_potrf. But other linalg operators work, such as linalg_potri. What' s wrong?

That means that the call failed internally inside the MKL-function. Did you check whether your input is valid (i.e. positive definite symmetric matrix)?

@asmushetzel thx, the matrix has some tiny negtive eigenvalues. After adding a small diagonal matrix, it works.


Fix broken links

./.github/CONTRIBUTING.md

[ ] https://sonarwhal.com/about/code_of_conduct.html => -1 (SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed)
[ ] https://sonarwhal.com/docs/developer-guide/contributing/pull-requests.html => -1 (SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed)

./README.md

[ ] https://sonarwhal.com/docs/user-guide/ => -1 (SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed)

See also: https://travis-ci.org/sonarwhal/sonar/jobs/258441435

Duplicate of #393.


CC3XX: Accommodate cipher entry points in PSA driver wrappers

The hash and cipher implementations in TF-M are not compatible (yet).
Add guards to enable/disable each: HASH_TEST and CIPHER_TEST.
Furthermore, update the CC3XX include macro to PSA_CRYPTO_DRIVER_CC3XX
to conform to the Mbed TLS style and for ease of grepping.
Signed-off-by: Abbas Bracken Ziad<EMAIL_ADDRESS>

Please cherry-pick the associated patch on TF-M gerit.


[Fix] Summary free interests

Se agrega la validación por monto para que no se muestren los intereses cuando las cuotas son sin interés.

Codecov Report

Merging #681 into develop will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           develop     #681   +/-   ##
========================================
  Coverage    28.93%   28.93%
========================================
  Files          243      243
  Lines        17514    17514
  Branches      1520     1520
========================================
  Hits          5067     5067
  Misses       11922    11922
  Partials       525      525

Impacted Files
Coverage Δ

...dopago/providers/ReviewAndConfirmProviderImpl.java
3.96% <0%> (ø)
: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 c065ef7...123c6f3. Read the comment docs.


[Onnxruntime-gpu] update v1.19.2

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] When updating the upstream version, the "port-version" is reset (removed from vcpkg.json).
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Can you explain why the more extensive changes in https://github.com/microsoft/vcpkg/pull/36850 are not needed?

I want to see what happens in #36850

Thanks for the update!


Switches automatically between Fixed Navigation (up to 3 tabs) and Shifting Navigation (3 - 5 tabs)

Hi,
Is it possible   to customize more then 3 images without shifting ?

You can manually set shifting, see README.md#Configuration
(Related to https://github.com/timomeh/react-native-material-bottom-navigation/issues/14#issuecomment-298141038)
Use the prop shifting={false}.
I hope that solves your question. If not, please feel free to reopen this issue.

Thanks.  @timomeh


convert_calendar adds time coordinate to static variables

What is your issue?
I just recognized that convert_calendar adds a time coordinate to variables that have been static before, e.g.,
import numpy as np
import pandas as pd
import xarray as xr

np.random.seed(0)
temperature = 15 + 8 * np.random.randn(2, 2, 3)
precipitation = 10 * np.random.rand(2, 2, 3)
orog = 0 + 100 * np.random.randn(2, 2)
lon = [[-99.83, -99.32], [-99.79, -99.23]]
lat = [[42.25, 42.21], [42.63, 42.59]]
time = pd.date_range("2014-09-06", periods=3)
reference_time = pd.Timestamp("2014-09-05")

ds = xr.Dataset(
    data_vars=dict(
        temperature=(["x", "y", "time"], temperature),
        precipitation=(["x", "y", "time"], precipitation),
        orog = (["x", "y"], orog)
    ),
    coords=dict(
        lon=(["x", "y"], lon),
        lat=(["x", "y"], lat),
        time=time,
        reference_time=reference_time,
    ),
    attrs=dict(description="Weather related data."),
)
ds

I would like to convert the time axis to cftime objects using
ds.convert_calendar(ds.time.dt.calendar, use_cftime=True)
ds

However, this results in an unexpected time coordinate in the orog variable...

It seems like this happens when the time dimensions is broadcasted during masking:
https://github.com/pydata/xarray/blob/41fef6f1352be994cd90056d47440fe9aa4c068f/xarray/coding/calendar_ops.py#L207
Cosequently is does not happen when i have align_on="year"...

@larsbuntemeyer It looks like this has been fixed somewhere on the way to xarray 2024.10.0. At least your MCVE works now. Could you please confirm? This would also affect your PR #7399.

@kmuehlbauer i can confirm that this has been fixed! Thanks!


Design resources every developer need.

🤔 This is a

[x] Feature
[ ] Bug
[  ] Documentation Update
[ ] Translation

✍ Description

I Added a Useful Resources for the developers.

Added to documentation

[x] readme file
[ ] No documentation needed

🐱💻 Use a meme/gif to describe how you feel for contributing (optional)

Hey, please read the contribution guidelines in the contribution.md file. Compare the pull request to the develop branch, write a short description, and check the checkboxes.
I have included an example of how the pr template should be filled 👍🏽

There is one developer branch. i can't find any develop branch. Thanks

Yes, that's what you should compare it to instead of the main branch.

I have taken a look at the design resource repo, it's already under CSS resources.
You can find another Github repo with resources that are not already included. 👍🏽

okay. no issue


[ON HOLD] Add support for ProductReferencesComponent

Used for upsells and cross sells
ProductReferencesComponent

waiting for https://jira.hybris.com/browse/RAY-272 and https://jira.hybris.com/browse/RAY-275

PR: GH-2033

QA steps:
-Go to backoffice > wcms > contentslot
-Find Upselling slot
-Under components, add a productreferencescomponent, such as Similar
-Double click Similar, and click the administration tabs. Under reference types, choose similar or accessories as the reference type because if you look at the product-relations.impex in the b2cmodule, those are the only types that are available/setup
-Navigate to one of the items who has a product references found in the product-relations.impex, such as 358639

Tested on dev2, with reference type "accessories". Able to see the upselling accessories on the storefront.

RAY-319 is in 1905.1