design a pkgcraft icon for the organization

Something with package and crafting themes probably would be appropriate, but shouldn't limit other ideas.

Here a relatively busy version with the Gentoo color theme.

Looks decent! Perhaps use the rustier version of the gear if we're going to copy the shell from the rust logo anyway. :smile:
I think their logo licensing allows that as long as attribution is provided.

the gear is the svg from their one, which one do you have in mind?

the gear is the svg from their one, which one do you have in mind?

I linked an example on irc.

The rust color is a gradient, this is the svg source, if somebody wants to use different color combinations.

Here a simple 1step radial gradient

Thanks for you work on this, I guess I like the non-gradient form better and have made it the current org icon.
As discussed on IRC, I'll leave this issue open for now since I still think there are more apt designs out there that don't use any rust-related iconography.


Remove centralized crypto constants

This PR contains two small commits:

Consolidate tablet obscuring code
This fixes #1805
Move implementation of tablet obscuring code into KeyExtent and remove
duplicate implementations.
Also fixup trivial constant in VisMetricsGatherer, so it is private and
fix typo in ZKSecurityTool to clarify that the salt length is 8 bytes by
default, not the hash length

Update SystemCredentials to use crypt(3) format
This fixes #1810
This updates the SystemToken generation to use SHA-512 while hashing the
system's instance.* configuration properties (including
instance.secret) by using commons-codec's crypt(3) implementation.
It also adds more javadocs and makes the code a bit more readable, while
removing a hard-coded global constant and an unneeded new instance
property introduced in #1798. That property is unneeded, since the
existence of the property itself creates wire-incompatibility. Instead,
this change explicitly bumps the wire version.
Also add sanity checks in SystemCredentialsTest for the wire version
values and to detect significant changes in the default algorithm used
by commons-codec to hash the credentials to prevent suprises when
upgrading the commons-codec library in future.

All ITs passed. Some ITs unrelated to these changes were flaky initially, but passed on subsequent runs.

While this is change contains multiple enhancements to the cryptography in the code, I feel like this is a regression in the maintainability.  Why not keep the cryptography constants in Constants.java as a pointer to the other parts of the code?  If someone wanted to see how we use the different algorithms, before they could search on those constants.  Now the encryption is scattered across vastly different and obscure parts of the code (KeyExtent, VisMetricsGatherer, SystemCredentials and ZkSecurityTool).  If they know to search for the string "SHA-256" they may be able to find these different pieces but as the different constants change (possibly independently) over time, this code will become even more difficult to maintain.

Why not keep the cryptography constants in Constants.java as a pointer to the other parts of the code?

The problem with Constants.java is that it makes it hard to modularize code, and it leaks implementation details, and can also make code harder to read, because you have to track variables through multiple layers of indirection. In general, constants should be as local as possible to the code where they get used. We have very little use of these as global constants.

Now the encryption is scattered across vastly different and obscure parts of the code (KeyExtent, VisMetricsGatherer, SystemCredentials and ZkSecurityTool).

No. It's not scattered. Addressing these point-by-point:

KeyExtent and VisMetricsGatherer are not using this in any cryptographic way. It's just part of it's local serialization code... which can change independently of crypto-related stuff. If it changes, it'd be because made a design to change the way KeyExtent or VisMetricsGatherer serializes those objects... and not because of some system wide decision pertaining to cryptographic strength. We shouldn't use a global constant unless we're trying to enforce some system wide decision, but that's not the case for these two.

For ZkSecurityTool, the only thing there now pertaining to SHA-256 is the code that allows us to read legacy formatted entries... which would not change based on any global decision.

There are no "SHA-X" constants in SystemCredentials now. There is a hard-coded constant for the salt prefix, because of a quirk with the way the commons-codec Crypt API works. We need to keep a consistent salt so that different servers don't generate different system passwords. Ideally, we'd always use the strongest hash supported by Crypt. We could programmatically extract the prefix associated with the strongest hash. However, I opted instead to create a JUnit test case to make us aware of any changes of that nature, so we can evaluate whether we need to use a different algorithm. Otherwise, it will just use SHA-512, which is Crypt's default.

So, really, there's no need for a centralized constant. The only uses for the constants we previously had are either non-crypto purpose serialization, code to interpret legacy values, or necessary to keep a consistent salt that only applies in one area of the code.

Thanks for addressing my concerns.  I guess my only concern now is how to address future requirements, when the hashes get out of date.  So if someone asks what hashes do we support, we just answer whatever the latest version we use of Apache commons Crypt library supports?

Thanks for addressing my concerns. I guess my only concern now is how to address future requirements, when the hashes get out of date. So if someone asks what hashes do we support, we just answer whatever the latest version we use of Apache commons Crypt library supports?

Well, now that we're using a standard format, we should be able to read any of the hashes that the Crypt library supports. The method we're calling in the Crypt API uses the default for that library, which is currently SHA-512, but it could change over time. Even if it changes, we will still be able to read the old values. However, the old values won't automatically upgrade like they are now doing for the legacy format we previously used. Users will benefit from the new hash supported by the library only if they change their password. That's typical for how crypt(3) is used with passwd files in Linux, so I think it's a normal expectation. However, as you saw, we do have a unit test to give us a heads up if something changes with the default, so we can address it on a case-by-case basis if it comes up. SHA-3 is being slowly adopted, so I expect we'll have to deal with it at some point, but probably not for quite a while.


Incorrect example for InlineIfLambda in page What's new in F# 6

The example in https://docs.microsoft.com/en-us/dotnet/fsharp/whats-new/fsharp-6#inlineiflambda seems totally wrong:

For example, consider the following iterateTwice function to traverse an array:
let inline iterateTwice ([<InlineIfLambda>] action) (array: 'T[]) =
    for j = 0 to array.Length-1 do
         action array[j]
     for j = 0 to array.Length-1 do
         action array[j]

If the call site is:
let arr = [| 1.. 100 |]
let mutable sum = 0
arr  |> iterateTwice (fun x ->
    sum <- sum + x)

Then after inlining and other optimizations, the code becomes:
let arr = [| 1.. 100 |]
let mutable sum = 0
for j = 0 to array.Length-1 do
    sum <- array[i] + x
for j = 0 to array.Length-1 do
    sum <- array[i] + x

Note the use of array instead of arr, replacing sum instead of x and [i] instead of [j].
This is a fixed version (unless I missed something :P ):
let arr = [| 1.. 100 |]
let mutable sum = 0
for j = 0 to arr.Length-1 do
    sum <- sum + arr[j]
for j = 0 to arr.Length-1 do
    sum <- sum + arr[j]

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

ID: e2dea170-a8f4-90f6-e578-e406fb43fef1
Version Independent ID: 885f9f09-d2ff-112c-6dda-9a31bccc0e8a
Content: What's new in F# 6 - F# Guide
Content Source: docs/fsharp/whats-new/fsharp-6.md
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: dotnetcontent

@KathleenDollard @dsyme


proxy: Invalid nexthop IPs

Describe the bug
When an NSM interface connecting the Proxy with and LB is removed before the connection is closed, the proxy won't be informed about the event. Thus, the nexthop IP associated with the closed NSM connection will be kept.
Such invalid nexthop IPs can cause problems if they won't get reused by an NSM connection connecting the proxy with an LB.
That's because route(s) for the invalid nexthop IPs might emerge causing traffic disturbance, when the set of stored nexthop IPs changes and thus routes get updated according to the known nexthop addresses.
In certain environments it had been observed, that failed NSM connection refresh could lead to NSM connection expire, where the network interface got removed from the proxy POD before the connection close. Resulting in the same invalid nexthop IP issue.
To Reproduce
Steps to reproduce the behavior:

Deploy a working trench with at least 1 LB-FE.
When everything is in place. In a proxy delete all the NSM interfaces connecting it with LBs. Then, swiftly scale-in the LB-FEs to 0.
Inspect the proxy logs: it won't remove the nexthops.

Optionally, one might try to significantly increase the replica count of the example target deployment to have multiple PODs running collocated with the proxy where the NSM interfaces were manually removed. The aim is to re-allocate the IPs formerly used by the proxy-LB NSM connections.
Then, scaling out the LB-FEs most probably will result in new IPs being handed out to the related connections. If, so the proxy logs can be inspected to check the number of nexthops have increased, and there should be more outbound nexthop routes than LB-FEs.
Expected behavior
Proxy must be able to remove nexthops irrespective of the order of events.
Context

Network Service Mesh: 1.11.2
Meridio: v1.0.15
...

Logs
NA

proposal:
-Proxy should listen for netlink based inteface delete events:
On delete event, check if the interface is linked to the bridge. The interface index
should help in this (should be sufficent to identify the inteface). If there's a hit,
the interface delete event is related to a bridge slave interface, thus the proxy should
act. First, the networking.Iface must be unlinked from the bridge mainly to free up the
associated memory resources (the interface should be already detached by the kernel).
Then, it must be identified which nexthop addresses are affected, that were provided via
the disappeared interface. This could be achieved by investigating the stored networking.Iface
by reading GetNeighborPrefixes. The VIPs must be updated via RemoveNexthop().
The nexthop addresses could be learnt by other means as well such as, listening for netlink
address delete events, or by using a custom networkservice client chain to get informed about
NSM connection close events. Probably non of these are necessary if the proxy pays attention
to netlink based interface events. At least, if we can assume the nexthop IPs won't change
in case of an active NSM connection between the proxy and the LB (TODO: double check).
There's also the question, if using a custom network service client chain to intercept connection
close would be a better option than relying on netlink interface events. IMHO, the former won't tell
anything about the lost interface, and relating the connection to a networking.Iface entry e.g. based
on the addresses is ugly.
Possibly, listening for both NSM connection close events and netlink interface events seems to be the most reliable choice...
-nexthops handling must be protected by locking. Maybe the vip handling as well. Double check.
Summary:
Proxy won't get any InterfaceDeleted() event in case the network interface is unavailable by the time
the NSM connection is closed. This is a serious problem and shortcoming of our custom interfacemonitor
client (can't figure out the interface index solely based on the connection). This results in invalid
nexthops being stuck in the proxy.
Although the related nexthop route is most probably removed by the kernel when the network interface is
removed by NSM, the VIPs (networking.SourceBasedRoute) will keep the invalid nexthops. Therefore,
any vip.RemoveNexthop()/AddNexthop() call via nexthop route update would reinsert invalid routes.
Hence, manually removing such lingering invalid routes is not a future proof workaround for example.


add the resources() dsl method back to providers

Custom resource actions were picking this up via delegation to
the wrapping resource, and that wiring was removed in 14, so that
API then got dropped accidentally.  This should fix that back
up.  It also consistently injects the resource APIs into resources
and providers both now (and consistently across core resources
and custom resources).

this probably needs a test


[Event Request] ccodeunit 8894 "Email Account" - New Event OnBeforeConvertEmailAddress

Hi Team,
we are trying to implement a Send-To Group Feature in Mail Editor (like in Outlook -> Add Groupname as Recipient), but the email address validation is blocking this scenario as the group is not a valid email address (e.g. accounting-group [contains n email-addresses]). Is it possible to introduce an event to handle email-address-validation?
My proposal in codeunit 8889 "Email Account Impl.":
[TryFunction]
local procedure ConvertEmailAddress(var EmailAddress: Text)
var
    MailAddress: DotNet MailAddress;
    EmailAccount: Codeunit "Email Account";
    IsHandled: Boolean; // New Var
begin
    // New Event
    EmailAccount.OnBeforeConvertEmailAddress(EmailAddress,IsHandled);
    if IsHandled then
        exit;
    // --

    // throws an exception if the address is invalid
    MailAddress := MailAddress.MailAddress(EmailAddress);

    EmailAddress := MailAddress.Address;
end;

Event definition in public codeunit 8894 "Email Account"
[IntegrationEvent(false, false)]
internal procedure OnBeforeConvertEmailAddress(var EmailAddress: Text; var IsHandled: Boolean)
begin
end;

Thanks,
Christian

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11004.


Added static method Input.Keys.isValidKeyCode(int)

Added static method Input.Keys.isValidKeyCode which can validate if keycodes are within [0,255], or whatever future range of valid keycodes.

I think this should be done in application code. Also, each backend is responsible for validating key codes before returning anything. I'd rather fix up bugs in there than rely on a method like this.


hybrid/subtle: use big.Int.FillBytes when ComputeSharedSecret

As the method is designed dedicated for this use case.
See:

https://github.com/golang/go/issues/35833
https://go-review.googlesource.com/c/go/+/230397

Kindly ping @chuckx
Also cc @thaidn

@chuckx could you please review this? i'll merge once you've approved.


Status (Progress bar) restructuring

Status both refreshes the page and shows pages left but currently generates lots of queries.

First draft of fixing this in
https://github.com/DigitalCurationCentre/roadmap/commit/a43aaa884e913e5ec7c75f8ffa577b9c35b7280d
This reduces the number of queries to 3 for the plan.status where it was nearer 25-50 depending on the plan. Will need revisited at some point but this will do for now.

Performance of plan page is lightning fast compared to pre-refactoring and status bar is working as expected. Closing this issue.


BigQuery + Pubsub push example is incorrect

File: themes/default/content/registry/packages/gcp/api-docs/pubsub/subscription/_index.md
Example from https://www.pulumi.com/registry/packages/gcp/api-docs/pubsub/subscription/#pubsub-subscription-push-bq
The resulted subscription has the wrong type (need to be "BigQuery")

I tried this out and the subscription created seems as expected:

Are you sure you copied the right example? https://www.pulumi.com/registry/packages/gcp/api-docs/pubsub/subscription/#pubsub-subscription-push-bq


Add support for publishing events using EventDataBatch

Part of August Preview is to expose/support sending an EventDataBatch.
Producers create EventDataBatch through EventHubProducer.createBatch() or EventHubProducer.createBatch(BatchOptions).
After populating the EventDataBatch, they use EventHubProducer.send(EventDataBatch) to push the batch to the service.

Fixes #4137
Fixes #4263

@JonathanGiles Alright. I've made fixes to those late night CR errors. 😢 Hopefully it looks good now.


Turns subtle multi-line ternaries into more explicit function call

There! Thoughts?
I know it'll conflict with changes @ethanbb is planning to make, but I can deal with those.

Example of the kinds of things that could go wrong with <RenderIfTrue>:
https://codepen.io/knod/pen/bxemOj?editors=0011


Add function references for SQL and Python API's.

Signed-off-by: Jason T. Brown<EMAIL_ADDRESS>

Now need to update to cell_types from cellTypes since #98 fixed by #100


Sorry... how to install/run?

Hi, would really like to get this running, but don't have much experience of javascript outside browsers. Could you do a couple of lines on getting started?
Thanks!

Hi Tom! I'm a huge fan of your work, and as I write this I'm admiring a Mutable Ears and Radio Music on my desk :)
I had just been thinking recently that I should revisit this code and clean it up. It would help me to know, are you interested in pen plotting, or laser cutting the results, or some other SVG export or just seeing it on a screen?

Hi, that's great to hear!  I have an Axidraw on the way, so I'd be looking for SVG or some other interface there.

OK, I've added some documentation to the bottom of the main README. I don't actually (yet) have a pen plotter myself, so I haven't tested the full end to end process, but the SVG output should be optimized for a plotter in that the lines are sorted to be drawn in an alternating back and forth motion. Let me know if you have any issues, or any success with plotting!

Fantastic, thank you, it's working! Will share some plots once I get a machine .

https://user-images.githubusercontent.com/1890544/107127082-985f2280-68ab-11eb-9046-4738652844df.mov
Email me<EMAIL_ADDRESS>and I'll send you a print

Excellent! Will do, thanks so much.


Report from publicapis.dev

Name: Hirak FaceAPI
Category: Machine Learning
Issue: Broken link
This report was sent from publicapis.dev.

Removed from the repository and soon from the website.


Many racer processes left around consuming large amounts of CPU time

I've just uninstalled atom-racer due to issue #80 and issue #82, but afterwards my machine was behaving incredibly sluggishly, and my top output includes the entries below.
This could be a racer issue, but given the problems atom-racer has with temp files I am currently making the assumption that it is an atom-racer issue.
This is a release build of racer from tag 2.0.10, on Linux/x86_64.


Enhancement: Part Fields

At the moment the part fields are "manf#" and "newark#", "digikey#", "mouser#"
It would be nice if the supplier specific fields were documented in the docs on how to use KiCost.
As the program grows, I could imagine more custom fields being used.  Would it make sense to create some sort of field name space, so that other programs wont clash with the fields dedicated to kicost.  Something like "KiCost:manf#" instead of "manf#", etc.  It might also make the Schematic fields more self documenting, when someone other than the author see's those fields they have some idea of their purpose or at least when they google search "KiCost:manf#" it will probably turn up something useful.

Here is a proposal for a name space:
kicost:::... = Value
instead of manf#:
kicost:manf# =  or "VALUE"
The purpose of "VALUE" is to keep the schematic information DRY (Do Not Repeat Yourself) some components which are not replaceable, I like to put the actual manufacturer part number in the value field, so that its obvious what the selected part is.  This shouldn't have to be repeated in the kicost:manf# field so a token "VALUE" informs kicost to get the part number from the standard value field.  The "VALUE" token should work for any kicost component fields, even though it might not make sense for some.
kicost:dist:<newark# / digikey# / mouser# / anysupplier# > =  or "VALUE"
Add a special supplier called "manual" its used to provide manual pricing for parts kicost can not find.
eg:
kicost:dist:manual# =
Then to support this new fields:
kicost:manual:price = "<$.CC>" or "qty:price,qty2:price2,qty3:price3,..."
So one could supply just a unit price to be applied for any qty, or a qty price break list like a normal supplier.
kicost:manual:source = "URL where the price was obtained"
This field could be put into the spreadsheet or just used for documentation purposes.
To support generic components:
kicost:generic = "Generic specifier"
The Generic specifier is a string to help Kicost look up the generic component, its basic format would be something like"
<component type:param,param,param,param...>
The params would vary depending on the component, params would be name/value pairs that you are interested in.  such as V=33 (means value = 33)
The params would need to be different for each component type.
Examples:
0603 SMD 33Ohm Resistor
kicost:generic = "RES:V=33,P=0603"
This would find the cheapest 0603 33 Ohm resistor from each supplier in the required qty.
0603 SMD 33Ohm 1% Resistor
kicost:generic = "RES:V=VALUE,T=1%,P=0603"
This would look up the VALUE field in the component for the V (value) parameter.  Which in this example is 33Ohm, the Tolerance "T" is set to 1% and the Package "P" is set to 0603.  Its not possible to reliably use the Footprint field, because there is no guarantee that the package and footprint are the same names.  But in the spirit of DRY, could always put P=FOOTPRINT and it could be looked up.
Ignoring parts could be as simple as:
kicost:ignore=True
This would address issue of ignoring things like fiducials, mounting points, pcb edge connectors, test points, etc. Without resorting to using a heuristic which might or might not work accurately.
Variant Part Lists:
I am working on a design at the moment with 7 variations based solely on component selection.  Pass a parameter to kicost called "variant" or something like that.  Then in addition to looking up these, also look up:
kicost::ignore = "true"/"false"
kicost::manf# =
kicost::dist:<dist#> =
kicost::generic:=
and so on.
If ANY "variant" field exists when that "variant" is selected it is used in preference to the base non variant fields, this way its possible to have a field which is ignored normally but in a particular variant is not ignored. Or vice versa, or in the normal case its a generic 33Ohm resistor but in the variant case its a specific part from Mouser.
Using the name space allows easier extension, is easy to generate the required field keys pragmatically, is easy to read and maintain inside the schematic itself.
Can also emit errors if a field starting with "kicost:" is found but the rest of it is unable to be deciphered, so that the designer knows when they have made a mistake.
These are just suggestions, but i am working on a design with 7 variants, and I plan on enhancing kicost to deal with that, making a name space seems like the easiest way to manage the plethora of options that are useful for this kind of application.

I implemented the "kicost:" prefix to distinguish KiCost-related fields from those of other tools. (The manf# field is still supported.) You can also add a label after that for a source or distributor. Then a final label indicating the type of data for the field's value (e.g., pricing). So, for example, the custom pricing field for a part might be:
kicost:my_special_dist:pricing    =    1:$0.90; 10:$0.80; 100:$0.60

You can also have fields for cat# (the distributor's catalog number) and link (a link to the part's documentation). Parts can have multiple sources for each of these items.
You can also leave out the source label. This will imply a source of "local". So "kicost:pricing" would have a source of "local".
All the info for parts from a particular source is grouped into a section of the spreadsheet and labeled with the name of the source.


fix broken 'this script' link

We ran this PR by the landscape app creators, and it was determined that this change, although technically correct, is not necessary to the functionality of the landscape. We've decided to close this for the time being.


compile error :StateConstraint.h:48:29: error: enclosing class of constexpr non-static member function ‘ocs2::ConstraintOrder ocs2::StateConstraint::getOrder() const’ is not a literal type

/home/robot/ws_perceptive_mpc/src/ocs2/ocs2_core/include/ocs2_core/constraint/StateConstraint.h:48:29: error: enclosing class of constexpr non-static member function ‘ocs2::ConstraintOrder ocs2::StateConstraint::getOrder() const’ is not a literal type
I use cmake 3.14.7 in ubuntu16.04 kinetic environment

Hi @dbdxnuliba,
Please follow the provided bug report template. Also, group related compiler issues (#13, #14) in a single ticket.
As described in the prerequisites section of the documentation, Ubuntu Xenial 16.04 does not satisfy the requirements. Please make sure your system satisfies the mentioned requirements. Consider running OCS2 in a container if you are not able to update your system.


Add maintainers

Hi @bollwyvl,
Would you mind adding me as a recipe maintainer? Ping @mattpap and @bryevdv in case they want to be added too.

You bet! I :heart: having primary maintainers on the teams! I'll add you on #4 when i get around to reviewing the upstream changes and getting it up and running.
Or, perhaps better: make a new PR that supercedes #4, fixes the 3.0 issues, and adds yourself and I will happily merge it!

Thanks, as far as I can tell the changes in #4 look good.

Looks like @philippjfr is up, feel free to have additional maintainers PR themselves! It's easier than playing telephone...

Thanks @bollwyvl, appreciate it.


add option to Bundler#mkdir_p to force Bundler to not use sudo

What was the end-user problem that led to this PR?
There is a bug for functionality that was added in #6258.  In certain scenarios, Bundler will create a folder for a temporary gem install with root:root permissions. This is happening because Bundler#mkdir_p checks for requires_sudo? which is creating a folder owned by root:root when it should be creating the folder with the current user.
What was your diagnosis of the problem?
See #6535
I can see that Bundler is creating the bin folder with root:root permissions
[vagrant@localhost ~]$ ls -la /tmp/bundler20180519-24861-1y67io7rake-12.3.1/
total 4
drwx------. 3 vagrant vagrant   17 May 19 07:36 .
drwxrwxrwt. 9 root    root    4096 May 19 07:36 ..
drwxr-xr-x. 2 root    root       6 May 19 07:36 bin

What is your fix for the problem, implemented in this PR?
Add an option for Bundler#mkdir_p to prevent it from using sudo even though requires_sudo? is true.
Fixes #6535

@bundlerbot r+

@bundlerbot r+

@bundlerbot retry


releng: Bump promoter to v3.4.7

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This commit bumps the promo-tools version to v3.4.7 in:
   modified:   VERSION
   modified:   cloudbuild.yaml
   modified:   dependencies.yaml
   modified:   workspace_status.sh

Which issue(s) this PR fixes:
Part of #659

Special notes for your reviewer:
/cc  @puerco @Verolop @ameukam @jeremyrickard @saschagrunert  @xmudrii
Does this PR introduce a user-facing change?

NONE

/lgtm


set runAsNonRoot

https://github.com/open-cluster-management/backlog/issues/8598

closing this pr as the user has been set in the container for downstream build

closing this pr as the user has been set in the container for downstream build


Update aws-iam-authenticator

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve
/unhold

/lgtm


Autocomplete doesn't use the .a files built from vendor directories

I've just cleaned out my entire Go folder structure, including deleting all packages that were built in the pkg directory, and because of this the autocomplete stopped working.
I know that gocode needs the built package files in order to work, but the difference between my previous folder contents and the contents now is that I use vendor folders for every single project, so nothing gets built and put into the pkg directory by default anymore.
Because of this I started including the -i flag in my calls to go install, so my install command looks something like this go install -i -v <project-here>.
Using the -i flag like this does build .a package files into the pkg folder for me, but autocomplete still doesn't work. I think this is because the -i flag builds vendored packages in a different path to the one that appears in the imports in the code.
For example, if I import the package "github.com/go-chi/chi" in my source code and that package only exists in the vendor folder in my project, then normally it won't show up as a built package in the pkg folder through a regular go install.
If I were to just use go get and not a tool like dep, then it would be built as a package in the pkg folder under a path like <arch>/github.com/go-chi/chi.a, but if I use the -i flag with go install for my project then the dependency package will be built under a path like <arch>/my/project/vendor/github.com/go-chi/chi.a.
As you can see the path "my/project/vendor/github.com/go-chi/chi" is quite different from the import path of "github.com/go-chi/chi" in the source code.
If I manually move the built package file into a directory that matches the path of the import in the source code then the autocomplete starts working again.
Is there a way to tell gocode, through GoSublime, to check the vendor directories that exist under pkg as well?
If not is there some other way around this problem that doesn't involve just using go get to force the package to be built under the pkg directory?

I didn't test on the current released version of GoSublime, but it works for me on the development branch.
This is the whole pkg tree:
/tmp/pkg/linux_amd64/
/tmp/pkg/linux_amd64/tst
/tmp/pkg/linux_amd64/tst/vendor
/tmp/pkg/linux_amd64/tst/vendor/github.com
/tmp/pkg/linux_amd64/tst/vendor/github.com/go-chi
/tmp/pkg/linux_amd64/tst/vendor/github.com/go-chi/chi.a

I also enabled AutoBuild, so I didn't need to manually install the pkg.
Switching will/should show you a message telling you to enable margo.sh by pressing ctrl+.,ctrl+.x which will open a copy of extension-example.go. Hopefully the comments in the file are clear enough.
The usual warning: this will break any features you might've configured in the GoSublime settings, but everything like autocompletion and linting, etc. is available in the new version of margo as well.


consistent jQuery usage

There were (jQuery || django.jQuery) and ($ || django.jQuery). This caused an js error ".livequery is not a function" in some cases.

Thanks!


update README.md

Hi,
I think that the documetation needs update :

@connect is no more used
server.SSR disappeared from the config file
catcher.js no more used (why?)
by the way enabling catcher prevents the app from starting.
I noticed also that if we try to register a user with special characters in his username the rendered validation message is "Internal Server Error" and not the more precise one written in server/routes/account.js line 52

@zorganovic
I've fixed catcher.js and updated the README file a bit.
About SSR, people have told me this starter is more of a Ferrari than a basic app, making it hard to get started for beginners. So I tried to simplify it a bit.
Maybe I should move a lot of the complicated logic into core and hide it inside a npm package just like next.js.

Thank you for the quick fix on a saturday night !!!
Better have a Ferrari that one can try to learn how to drive it, than a dull 2CV going no where :wink:


[SPARK-11423] remove MapPartitionsWithPreparationRDD

Since we do not need to preserve a page before calling compute(), MapPartitionsWithPreparationRDD is not needed anymore.
This PR basically revert #8543, #8511, #8038, #8011

Merged build triggered.

Merged build started.

Test build #44692 has started for PR 9381 at commit 374ec3b.

Merged build triggered.

Merged build started.

Test build #44692 has finished for PR 9381 at commit 374ec3b.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44692/
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44693/
Test FAILed.

Test build #1962 has started for PR 9381 at commit fed4ab6.

Test build #1962 has finished for PR 9381 at commit fed4ab6.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #44696 has started for PR 9381 at commit 258d275.

Test build #44696 has finished for PR 9381 at commit 258d275.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44696/
Test PASSed.

Avoid of using mapPartitions can help us reduce the costs on closure cleaner. Should we create MapPartitionsRDD directly?

@yhuai I just rollback the changes, we use mapPartitions a lot, they should not have much different.

Since this PR just revert some patches, I will merge it to unblock #9383


Adjust front page according to design

Hello, please adjust the front page according to design  which is shared in zip website-specs-tamiat
Thank you

@nikkanetiya adjust the homepage to make it example of the features we haveThis means it will not have static content, but rather use the information from the CMSso converting the static content their in the homepage into content from the CMS
there is a section of the work examplesbut should be reading from the CMS not static contentWhat others Say section, should also be from the CMSblog sectionand so on
If something not clear you can always ask
Thank you

@mahnouman Safe to close it.


Support Backfill feature in Cronworkflow

Summary
Replay/Retrigger the past events between dates.  In Data processing or ML usecase, the User wants to process the past event on a new algorithm/code.
What change needs making?
Provide CLI like argo corn backfill <cronworkflow name> --name <backfill name> --start <startdate> --end <enddate>
Use Cases
In Data processing or ML usecase, the User wants to process the past event on a new algorithm/code.
When would you use this?

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

link #3649

Duplicates #2706

@alexec, @sarabala1979 can you point me to any docs on what is the best way to do backfill?

#3094 added documentation: https://argoproj.github.io/argo-workflows/cron-backfill/


Feature/css reset update

Description of the Change

Change the css reset from normalize to modern-normalize
Add some general css reset enhancements
Update package.json and package.lock files

Closes #182
How to test the Change

Assuming local setup already running as expected.
Remove node modules files across project (root, plugin, theme)
At root, make sure on correct verson of npm with npm use
Run npm install at the root
Run npm run start to compile files
Test front end output. Should notice box-sizing: border-box; on any divs.

Changelog Entry

Added - modern-normalize npm package to theme
Changed - import modern-normalize from node_modules in theme - replacing normalize
Changed - package.json and package.lock files due to the package updates
Removed - normalize from package.json
Fixed - Includes box-sizing: border-box; by default

Credits
Props @10up/frontend-leads, @devinle, and @dainemawer
Checklist:

[x] I agree to follow this project's Code of Conduct.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my change (N/A)
[x] All new and existing tests pass.

@fabiankaegy
You had mentioned adding some default CSS (WordPress specific). Can define what those are?
In the scaffold, we have the wordpress.css file.
I also added reset.css and included the isolation declaration from your reset for stacking context.
While I'm in here - I'd love to add any common additions you may have been thinking of. Please let me know when you have a moment. Thanks!
Once we have that figured out, I'll have the FE Leads review, then move this forward.

@fabiankaegy Your issues have been resolve. Please review again - and let me know if there are any other CSS resets you would like to see added at this time. Thanks!

@darylldoyle this is ready for review and merged once approved.
@fabiankaegy - your previous issues have been resolved.
Let me know if you have any questions or concerns.

Thanks @joesnellpdx!
@fabiankaegy any chance you can take a look at this since you reviewed before, please?

@joesnellpdx I don't seem to have the permissions to merge in this repo now, but since this is approved, you should be good to do so!


[bug]: nodes API - only the first invocation generates an image

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
16GB
What happened?
Using the nodes API, the first request to invoke a session generates a result. All subsequent requests respond with 202: Accepted, but generation silently fails. Reproducible with this script:
#!/bin/bash
api_url=http://localhost:9090

res=$(curl -s -X 'POST' \
  "${api_url}/api/v1/sessions/" \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "id": "1",
    "nodes": {
        "1": {
            "id": "1",
            "type": "txt2img",
            "prompt": "amazeballs",
            "sampler": "ddim",
            "steps": 30,
            "seed": 42
        },
        "2": {
            "id": "2",
            "type": "show_image"
        }
    },
    "edges": []
}')

id=$(echo $res | jq -rc '.id')

echo "${id}"

curl -s -X 'PUT' \
  "${api_url}/api/v1/sessions/${id}/invoke?all=false" \
  -H 'accept: application/json'

res=$(curl -s -X 'GET' -H 'accept: application/json' "${api_url}/api/v1/sessions/?query=${id}")

echo $res | jq '.items[].errors'

The error is as follows:
{
  "e0d435fc-5277-4b02-93f2-21ff08a30005": "Traceback (most recent call last):\n File \"/opt/invokeai/.venv/lib/python3.10/site-packages/invokeai/app/services/processor.py\", line 54, in __process\n outputs = invocation.invoke(\n File \"/opt/invokeai/.venv/lib/python3.10/site-packages/invokeai/app/invocations/generate.py\", line 71, in invoke\n generate_output = next(outputs)\n File \"/opt/invokeai/.venv/lib/python3.10/site-packages/invokeai/backend/generator/base.py\", line 125, in generate\n model_name = model_info['model_name']\nTypeError: string indices must be integers\n"
}

Restarting the process (killing the pod in this case) brings generation back to life for one more request
Screenshots
No response
Additional context
No response
Contact Details
No response

What branch are you on?

This looks to be using the new code introduced in https://github.com/invoke-ai/InvokeAI/pull/2902. We'll have to investigate and fix it.

Ok. I know where the bug is. We’ll fix

Thank you! And yes, this is on main

Found the issue - model manager was returning the model name in some cases instead of the model.


Clone bundles in parallel way for speedup

Currently :BundleInstall takes forever for the first time (server setup).

@jdevera might be worth re-opening now that Vim 8 supports async.


Generic link to the latest release

In https://github.com/ZotPlus/zotero-better-bibtex#installation-one-time, the link to the latest release in the sentence: "After installation, the plugin will auto-update to newer releases." is hard coded, currently:
https://zotplus.github.io/better-bibtex/zotero-better-bibtex-0.8.11.xpi
I would suggest to replace it by a generic one, e.g.:
https://zotplus.github.io/better-bibtex/zotero-better-bibtex-latest-release
which turns to go to the relevant current .xpi file.

I can't do redirects on Github Pages, unfortunately. The link is indeed hardcoded, but the deployment script always updates it during the publishing process, and after the first-time installation the plugin is auto-updated by the firefox extension upgrade mechanism, which polls for https://zotplus.github.io/better-bibtex/update.rdf, which in turn always points to the latest version. So the redirect is there, after a fashion. After first-time installation, there;s really no need to ever download the xpi again, and even if you have stumbled upon an older version, auto-update will take care of it.

I knew for the automatic update but my feature request was because I'd want to give, in a LaTeX course PDF file available online, the direct link to the zotero-better-bibtex's (latest) installation file. But I understand the problem and will instead give the link to the Web page https://github.com/ZotPlus/zotero-better-bibtex#installation-one-time. Thanks.

Ah, that's what you mean. You can use https://zotplus.github.io/better-bibtex/index.html#xpi, which will always trigger a download of the latest version.

This does the trick: thanks!


Add disabled:opacity-70 to checkbox and radio

Almost every form component has these disabled-modifier except a few, including radio and checkbox.

Have you checked CheckboxList?

Thank you


new thumbnails

Adding the new thumbnails. I have chosen to create a folder with the thumbnails separately (following the idea of large thumbnails).
In the end I chose not to delete the old ones. They remain in their original demo folder. This is because they could be used within the demo for explanation purposes. This  PR does not create any inconsistency with the other repositories , I'll update them to the new images

Look great! Thanks @KetpuntoG


Feat: implement default converter

@sixaphone it is not necessary. It can take you too much time

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FEAT] Using *arg resp **kwargs for add_path resp add_query

It would be convenient to be able to call methods like this:
url.add_path('foo', 'bar', 'xyz')
url.add_query(foo=1, bar=2)

I do agree! I've implemented it, but it might still need some polishing.


[java] Update Graal to JDK 21 for spring-boot-3-native weblog

Motivation
We want to collect profiling information for Graal native images built on top of JDK 21 rather than 17
Changes
Modifies the pom.xml to fit the expected configuration format for JDK 21, changes the base image to use a release from https://github.com/graalvm/container that contains GraalVM JDK 21 + native image tooling.
Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[x] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[x] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

Ping @mcculls @PerfectSlayer


Allow certain hardware time to initialize.

Would not work previously using Monado with the Oculus CV1.  There are some magic commands that need to be sent to the CV1 over USB to turn the display on and have X recognize it.  This delay allows the device to startup before hello_xr attempts to access it.  Before this addition, hello_xr would complain that no non-desktop display devices were found, and now it works out of the box with OpenHMD 0.3.0-rc1 and the master branch of Monado.

 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.

I'm wondering if this would be better off in the OpenHMD driver, because developers probably don't need to be thinking about these kinds of timing issues when working with a high-level API.  Let me know what you think.

Yeah, this is a runtime bug and needs to be fixed in the runtime. Applications should not include a delay.

Ok. I'll take this to OpenHMD.


Plugin HTTP Error - 404 Client Error: Not Found for url

Netflix add-on version
1.12.14
Operative systems used
LibreELEC
Kodi version used
Kodi 18 (Leia)
Description of the bug
When the plugin is open and it should show the list of media content, it returns the error:
404 Client Error: Not Found for url: https://www.netflix.com/api/shakti/vedfdb694/pathEvaluator?materialize=false&original_path=%2Fshakti%2Fvedfdb694%2FpathEvaluator&categoryCraversEnabled=false&isVolatileBillboardsEnabled=true&isTop10Supported=true&routeAPIRequestsThroughFTL=false&withSize=false&drmSystem=widevine
Note: Authentication key is used as authentication method. The plugin worked fine yesterday but today got this error. Rebooting the system nor re authenticating did not solve the problem.
Steps to reproduce the behavior

Go to Add-on and open Netflix addon
The account main menu is shown, with the account name and the "Children" menu items.
Click on the account name to access the content -> The "404 Client Error: Not Found for url" is returned

Debug log - mandatory
https://paste.kodi.tv/bacicebiko.kodi
Possible fix
No response
Additional context
No response
Screenshots
No response

Dupe of #1425?

Updating from 1.18.1 to 1.18.10 worked for me

despite different error shown at screen it is same problem of #1425

Thanks guys!
I saw https://github.com/CastagnaIT/plugin.video.netflix/issues/1425 yesterday before opening this one but I didn't realise that it could be the same.
Do you want me to put these info in the https://github.com/CastagnaIT/plugin.video.netflix/issues/1425 or will you merge them together?

we keep this one open as well, having a different error name will redirect users to the right thread,
preventing someone else from opening another issue like this again

Is this also causing this error that is suddenly occuring this morning for me?


explore capability for event check/in registration

Any way we could do live event check-in, account creation at an event?

being addressed by different means


New package: Panda3D.Panda3D version 1.10.14

Pull request has been created with komac v2.2.1 :rocket:
Resolves: https://github.com/microsoft/winget-pkgs/issues/155232
Microsoft Reviewers: Open in CodeFlow

This package installs and launches normally on a Windows 10 VM.


Sidenav instead of drawer

In GitLab by @lakhoune on Dec 3, 2020, 02:24

Location: navigation list
Description: use the mat-sidenav instead of drawer to show navigation. This should also fix the bug with elements height and scrollbars

In GitLab by @lakhoune on Dec 3, 2020, 14:24
mentioned in commit 348a706959ac2024fb6cc3de2cb30bb04c032cd7


Kubernetes Service unavailable

Rancher versions:
rancher/server:1.6.1
rancher/agent:1.6.2
Infrastructure Stack versions:
healthcheck:0.3.1
ipsec:holder
network-services:metadata=0.9.1, manager=0.7.1
scheduler:0.8.1
kubernetes (if applicable):1.5.4
Docker version: (docker version,docker info preferred)
Containers: 3
Running: 1
Paused: 0
Stopped: 2
Images: 2
Server Version: 1.12.6
Storage Driver: overlay
Backing Filesystem: xfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay host null bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-514.21.1.el7.x86_64
Operating System: Red Hat Enterprise Linux Server 7.3 (Maipo)
OSType: linux
Architecture: x86_64
CPUs: 40
Total Memory: 157 GiB
Name: ip-10-205-81-7.dqa.capitalone.com
ID: BF2X:BPWL:G46E:2L6X:3XJE:FRH4:3CI3:DXYX:7D3W:GLBG:F3G2:PN5B
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: http://aws-proxy-dev.cloud.capitalone.com:8099
Https Proxy: http://aws-proxy-dev.cloud.capitalone.com:8099
No Proxy: <IP_ADDRESS>,s3.amazonaws.com,kdc.capitalone.com,cloud.capitalone.com
Registry: https://index.docker.io/v1/
Insecure Registries:
<IP_ADDRESS>/8
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
3.10.0-514.21.1.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:
Created an AWS instance (we run in a private IP range behind corp. proxies) and bring up Rancher
Turn on local auth
Create Kubernetes env
Click on Kubernetes UI
Results:
Service unavailable
The CLI works fine

I did some more digging, but being new to both Rancher and Kubernetes I am not sure if it helps. There is no external IP on the dashboard...
Run kubectl commands inside here
e.g. kubectl get rc

kubectl get deployment kubernetes-dashboard --namespace=kube-system
NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
kubernetes-dashboard   1         1         1            0           1d
kubectl get svc kubernetes-dashboard --namespace=kube-system
NAME                   CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
kubernetes-dashboard   <IP_ADDRESS>           9090/TCP   1d

Do you have the required ports open that are needed for k8s?
http://rancher.com/docs/rancher/v1.6/en/kubernetes/#required-ports

Can you share logging from the kubernetes dashboard container?

How do I get it?
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Sebastiaan van Steenis<EMAIL_ADDRESS>Date: 6/29/17  8:40 AM  (GMT-05:00) To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Can you share logging from the kubernetes dashboard container?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rancher/rancher","title":"rancher/rancher","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rancher/rancher"}},"updates":{"snippets":[{"icon":"PERSON","message":"@superseb in #9188: Can you share logging from the kubernetes dashboard container? "}],"action":{"name":"View Issue","url":"https://github.com/rancher/rancher/issues/9188#issuecomment-311954230"}}}

Infrastructure -> Containers -> kubernetes-dashboard -> View Logs.

I will get those, but i just went into the kubernetes infrastructure, and kubernetes shoes degraded, and rancher ingress and kubernetes agent both show unhealthy.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Sebastiaan van Steenis<EMAIL_ADDRESS>Date: 6/29/17  9:26 AM  (GMT-05:00) To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Infrastructure -> Containers -> kubernetes-dashboard -> View Logs.
—
You are receiving this because you authored the thread.

Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Sebastiaan van Steenis<EMAIL_ADDRESS>Date: 6/29/17 9:26 AM (GMT-05:00)
To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Infrastructure -> Containers -> kubernetes-dashboard -> View Logs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rancher/rancher/issues/9188#issuecomment-311965674, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMXywur5L2b8_bHJrBxITLreKHLVk_Csks5sI6YcgaJpZM4OIEzG.

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

And there is no dashboard.
I made some progress, based on a hunch from work I did with DCOS. In our environment, the DNS names do not match the name given by AWS. I put in a fix that corrects the hostname during the build, and now all the services start except the ingress and rancher k8s agent, and it looks like the kube hostname lookup cycles now and then, and has:
6/29/2017 11:36:55 AMtime="2017-06-29T15:36:55Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:37:27 AMtime="2017-06-29T15:37:27Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:38:03 AMtime="2017-06-29T15:38:03Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:38:36 AMtime="2017-06-29T15:38:36Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:39:08 AMtime="2017-06-29T15:39:08Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:39:40 AMtime="2017-06-29T15:39:40Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:40:12 AMtime="2017-06-29T15:40:12Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:40:44 AMtime="2017-06-29T15:40:44Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:41:15 AMtime="2017-06-29T15:41:15Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:41:48 AMtime="2017-06-29T15:41:48Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:42:22 AMtime="2017-06-29T15:42:22Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
6/29/2017 11:42:55 AMtime="2017-06-29T15:42:55Z" level=fatal msg="Get http://rancher-metadata/2015-12-19/version: dial tcp: lookup rancher-metadata: no such host"
Even with the change I made, the host names still show incorrect. Where does Rancher get the hostnames? I currently only fixed them on the Kubernetes nodes, but DNS would be returning the correct ones as well.
From: "joe.bryant"<EMAIL_ADDRESS>Date: Thursday, June 29, 2017 at 10:30 AM
To: rancher/rancher<EMAIL_ADDRESS>rancher/rancher<EMAIL_ADDRESS>Cc: Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
I will get those, but i just went into the kubernetes infrastructure, and kubernetes shoes degraded, and rancher ingress and kubernetes agent both show unhealthy.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Sebastiaan van Steenis<EMAIL_ADDRESS>Date: 6/29/17 9:26 AM (GMT-05:00)
To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Infrastructure -> Containers -> kubernetes-dashboard -> View Logs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rancher/rancher/issues/9188#issuecomment-311965674, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMXywur5L2b8_bHJrBxITLreKHLVk_Csks5sI6YcgaJpZM4OIEzG.

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

When I say all services, I am referring to Kubernetes, not Dashboard
From: "joe.bryant"<EMAIL_ADDRESS>Date: Thursday, June 29, 2017 at 10:30 AM
To: rancher/rancher<EMAIL_ADDRESS>rancher/rancher<EMAIL_ADDRESS>Cc: Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
I will get those, but i just went into the kubernetes infrastructure, and kubernetes shoes degraded, and rancher ingress and kubernetes agent both show unhealthy.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Sebastiaan van Steenis<EMAIL_ADDRESS>Date: 6/29/17 9:26 AM (GMT-05:00)
To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Infrastructure -> Containers -> kubernetes-dashboard -> View Logs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rancher/rancher/issues/9188#issuecomment-311965674, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMXywur5L2b8_bHJrBxITLreKHLVk_Csks5sI6YcgaJpZM4OIEzG.

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?

Fresh
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Adrian Goins<EMAIL_ADDRESS>Date: 6/29/17  3:35 PM  (GMT-05:00) To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rancher/rancher","title":"rancher/rancher","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rancher/rancher"}},"updates":{"snippets":[{"icon":"PERSON","message":"@oskapt in #9188: Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?"}],"action":{"name":"View Issue","url":"https://github.com/rancher/rancher/issues/9188#issuecomment-312077907"}}}

In fact, they are built with aws car's that start the host docker command to join the kubernetes cluster (I update the car after I create the env)
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Adrian Goins<EMAIL_ADDRESS>Date: 6/29/17  3:35 PM  (GMT-05:00) To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rancher/rancher","title":"rancher/rancher","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rancher/rancher"}},"updates":{"snippets":[{"icon":"PERSON","message":"@oskapt in #9188: Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?"}],"action":{"name":"View Issue","url":"https://github.com/rancher/rancher/issues/9188#issuecomment-312077907"}}}

I'll be leaving shortly, but it looks like almost everything in namespace kube-system is having heartache. I am watching it on the host screen as the hosts con inline.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Adrian Goins<EMAIL_ADDRESS>Date: 6/29/17  3:35 PM  (GMT-05:00) To: rancher/rancher<EMAIL_ADDRESS>Cc: Joe Bryant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rancher/rancher] Kubernetes Service unavailable (#9188)
Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rancher/rancher","title":"rancher/rancher","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rancher/rancher"}},"updates":{"snippets":[{"icon":"PERSON","message":"@oskapt in #9188: Is this a fresh install an a new instance or have you deployed and deleted and reinstalled k8s on this node?"}],"action":{"name":"View Issue","url":"https://github.com/rancher/rancher/issues/9188#issuecomment-312077907"}}}


Add Contributing.md file

Define You:

[x ] Contributor

Is your feature request related to a problem? Please describe.
For new users who want to contribute to any open-source project, it becomes difficult to start when they are not aware of the basic steps. Having a file that describes the initial steps will be helpful for them.
Describe the solution you'd like...
I suggest adding a contributing.md file to the project. You can assign this task to me, and I will create the file

https://github.com/p2plabsxyz/dscan/blob/main/.github/CONTRIBUTING.md


spice-client-glib-usb-helper: Error setting facl: Operation not permitted

Describe the bug
After merging: https://github.com/NixOS/nixpkgs/pull/97826 spice usb redirection in virt-viewer still yields: spice-client-glib-usb-helper: Error setting facl: Operation not permitted
To Reproduce
Steps to reproduce the behavior:

set: virtualisation.spiceUSBRedirection.enable = true
Start virt-viewer from command line and attach to vm
Redirect a usb device to vm

Expected behavior
USB device should be redirected to VM.
Additional context
According to the documentation here, spice-client-glib-usb-acl-helper should be installed with setuid permissions. But on my system it is not. sudo chmod u+s $(which spice-client-glib-usb-acl-helper) is a workaround for the issue.
Do we maybe need a setuid = true; around here ?
Notify maintainers

@lheckemann

Metadata

system: "x86_64-linux"
host os: Linux 5.4.77, NixOS, 21.03pre252083.2deeb58f494 (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.8
channels(root): "home-manager, nixos-21.03pre252083.2deeb58f494, nixos-hardware"
channels(ente): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
  - virtualisation.spiceUSBRedirection

No, it shouldn't need setuid, the fowner capability as set by the module should be enough… Is it set correctly on your system? Check using getcap /run/wrappers/bin/spice-client-glib-usb-acl-helper.

$ getcap /run/wrappers/bin/spice-client-glib-usb-acl-helper
/run/wrappers/bin/spice-client-glib-usb-acl-helper cap_fowner,cap_setpcap=ep

I ran into the same issue. The aforementioned setuid workaround did work as well.

I ran into the same issue. The aforementioned setuid workaround did work as well.

I can reproduce this. getcap returned exactly the same as @Enteee. Only after applying workaround does usb redirection work.

I can reproduce this. getcap returned exactly the same as @Enteee. Only after applying workaround does usb redirection work.

tested in virt-manager and it works

We might have actually switched to capabilities too soon. The MR implementing them has only been merged in 0.39, see https://github.com/NixOS/nixpkgs/pull/152044/files.


chore: release 1.1.6

:robot: I have created a release beep boop
1.1.6 (2022-12-13)
Miscellaneous Chores

deps: update actions/dependency-review-action digest to 0efb1d1 (#51) (0916ce2)
deps: update actions/upload-artifact digest to 83fd05a (#52) (01fc3e8)
deps: update all non-major dependencies (#53) (6bae620)
deps: update mcr.microsoft.com/dotnet/nightly/aspnet:7.0-jammy-chiseled docker digest to 1768d50 (#50) (eaaf6ad)
deps: update mcr.microsoft.com/dotnet/nightly/aspnet:7.0-jammy-chiseled docker digest to 5210087 (#48) (7e40e36)
deps: update mcr.microsoft.com/dotnet/sdk:7.0-jammy docker digest to 1f03f26 (#49) (1eccb8a)
deps: updated scorecards (4ae71dd)
deps: updated skaffold to v3 schema (#54) (56d3d84)

CI/CD

implemented slsa3 provenance (4ae71dd)
migrate to release-please (#55) (4ae71dd)
use release-please (4ae71dd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/chgl/magniFHIR/releases/tag/v1.1.6 :sunflower:


Bootloader update bricked a new TinyFPGA BX

Hope this is the right repo for this issue. This is a brand new board I got from Digikey. I was following the instructions in the TinyFPGA BX User Guide. I'm running Ubuntu 18.10. Prior to this log I installed apio via pip3 install apio, installed serial udev rule via apio drivers --serial-enable, and installed tinyprog via pip3 install tinyprog
atlas:~δ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 005 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 036: ID 1209:2100 InterBiometrics
Bus 001 Device 003: ID 062a:4102 Creative Labs
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
atlas:~δ tinyprog --update-bootloader

    TinyProg CLI
    ------------
    Using device id 1d50:6130
    Only one board with active bootloader, using it.

    The following update:

        New Version: 1.0.1
        Notes: Updates USB VID:PID to fix issues with APIO not recognizing the board.

    is available for this board:

        /dev/ttyACM0: TinyFPGA BX 1.0.0
            UUID: dbce8bd3-7702-4fd3-815b-2aabe7e0c942
            FPGA: ice40lp8k-cm81

    Would you like to perform the update? [y/N] y
    Fetching stage one...
    Programming stage one...
    Erasing: 100%|████████████████████████████████████████████████████████████████████████████████████████| 135k/135k [00:00<00:00, 157kB/s]
    Writing: 100%|███████████████████████████████████████████████████████████████████████████████████████| 135k/135k [00:01<00:00, 86.9kB/s]
    Reading: 100%|███████████████████████████████████████████████████████████████████████████████████████| 135k/135k [00:01<00:00, 86.5kB/s]
    ...Success!
    Waiting for stage one to reconnect....connected!
    Fetching stage two...
    Programming stage two...
    Erasing:   0%|                                                                                | 0.00/299k [00:00<?, ?B/s]
Traceback (most recent call last):
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 19, in to_int
    return ord(value)
TypeError: ord() expected a character, but string of length 0 found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/luke/.local/bin/tinyprog", line 11, in <module>
    sys.exit(main())
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__main__.py", line 314, in main
    perform_bootloader_update(port)
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__main__.py", line 184, in perform_bootloader_update
    if p.program_bitstream(0, bitstream):
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 419, in program_bitstream
    return self.program(addr, bitstream)
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 375, in program
    self.erase(addr, len(data), disable_progress=False)
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 347, in erase
    self._erase(addr, erase_length)
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 301, in _erase
    self.wait_while_busy()
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 290, in wait_while_busy
    while to_int(self.read_sts()) & 1:
  File "/home/luke/.local/lib/python3.6/site-packages/tinyprog/__init__.py", line 21, in to_int
    return int(value)
ValueError: invalid literal for int() with base 10: b''
atlas:~δ tinyprog --update-bootloader

    TinyProg CLI
    ------------
    Using device id 1d50:6130
    No port was specified and no active bootloaders found.
    Activate bootloader by pressing the reset button.
atlas:~δ tinyprog --update-bootloader

    TinyProg CLI
    ------------
    Using device id 1d50:6130
    No port was specified and no active bootloaders found.
    Activate bootloader by pressing the reset button.
atlas:~δ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 005 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 062a:4102 Creative Labs
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
atlas:~δ echo Wat
Wat
atlas:~δ

As shown in the log, the board no longer enumerates on USB, even when unplugged/replugged (performed in between the two "no active bootloaders found" messages). The heartbeat LED on the board is now illuminated at a constant, dim level, which is consistent with an unconfigured iCE40 with pins in default weak-pullup state.
I noticed that out of habit I used pip3 rather than pip to install the packages. Could this be the cause of this?
I also would quite like to rescue this board, so are there any flat binary images floating around I can use to reimage the SPI flash, including the iCE40 warmboot applet etc? I don't mind a bit of soldering.
Thanks! I am happy to add any more details, although further testing on my end will be a challenge :)

@Wren6991 I happened to spot both this issue, and some relevant discussion on the TinyFPGA discourse, while looking for something else, and wondered if you knew about this thread:
https://discourse.tinyfpga.com/t/error-while-updating-bootloader-invalid-literal-for-int-with-base-10/484/3
which seems to contain a link to firmware that could be programmed directly into the SPI if you knew how to solder onto the SPI pins, and run a SPI programmer (there's some hints in that post for where those pins are).
The details at https://github.com/tinyfpga/TinyFPGA-Bootloader/issues/18 seem pretty similar to your results (which was also the same person as that Discourse thread above).
Ewen


Remove limit checking from SBE stub generation

Now that the underlying buffer are the Agrona buffers we could remove the bounds checking from the SBE stubs and relay in the Agrona buffers bounds checking.
I propose we remove the SBE bounds checking in Java to simplify the generated code.

:+1:

Now depends on Agrona buffers doing the check.


SSL: CERTIFICATE_VERIFY_FAILED on macOS Sonoma 14.5 AND on macOS Sequoia 15.0 beta 2

When using python3 app.py on macOS (the supplied web interface to resemble-enhance,
when using a public shared link OR when using localhost:7860,
the following error was seen in resemble-enhance/enhancer/download.py...
def download(run_dir: str | Path | None = None):
...
       torch.hub.download_url_to_file(url, str(path))   # <---- SSL CERTIFICATE_VERIFY_FAILED Error

IS THIS because macOS and Windows does not permit multiple redirects?
IS the only work-around at the moment to run from Linux?
Can this be run locally without having to ask the server which does multiple redirects?
Here is the detailed stack trace...
Downloads/resemble-enhance-main % python app.py
[2024-06-26 21:37:44,816] [INFO] [real_accelerator.py:161:get_accelerator] Setting ds_accelerator to mps (auto detect)
[2024-06-26 21:37:45,218] torch.distributed.elastic.multiprocessing.redirects: [WARNING] NOTE: Redirects are currently not supported in Windows or MacOs.
Running on local URL:  http://<IP_ADDRESS>:7860
Running on public URL: https://02876e1f2a3e690306.gradio.live
This share link expires in 72 hours. For free permanent hosting and GPU upgrades, run gradio deploy from Terminal to deploy to Spaces (https://huggingface.co/spaces)
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 1348, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 1303, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 1349, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 1298, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 1058, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 996, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/http/client.py", line 1475, in connect
self.sock = self._context.wrap_socket(self.sock,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/ssl.py", line 517, in wrap_socket
return self.sslsocket_class._create(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/ssl.py", line 1104, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/ssl.py", line 1382, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/gradio/queueing.py", line 541, in process_events
response = await route_utils.call_process_api(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/gradio/route_utils.py", line 276, in call_process_api
output = await app.get_blocks().process_api(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/gradio/blocks.py", line 1928, in process_api
result = await self.call_function(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/gradio/blocks.py", line 1514, in call_function
prediction = await anyio.to_thread.run_sync(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/anyio/to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2177, in run_sync_in_worker_thread
return await future
^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 859, in run
result = context.run(func, *args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/gradio/utils.py", line 833, in wrapper
response = f(*args, **kwargs)
^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/Downloads/resemble-enhance-main/app.py", line 24, in _fn
wav1, new_sr = denoise(dwav, sr, device)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/Downloads/resemble-enhance-main/resemble_enhance/enhancer/inference.py", line 29, in denoise
enhancer = load_enhancer(run_dir, device)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/Downloads/resemble-enhance-main/resemble_enhance/enhancer/inference.py", line 16, in load_enhancer
run_dir = download(run_dir)
^^^^^^^^^^^^^^^^^
File "/Users/williammccarthy/Downloads/resemble-enhance-main/resemble_enhance/enhancer/download.py", line 48, in download
torch.hub.download_url_to_file(url, str(path))
File "/Users/williammccarthy/.virtualenvs/asj/lib/python3.11/site-packages/torch/hub.py", line 620, in download_url_to_file
u = urlopen(req)
^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 519, in open
response = self._open(req, data)
^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 536, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 496, in _call_chain
result = func(*args)
^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 1391, in https_open
return self.do_open(http.client.HTTPSConnection, req,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py", line 1351, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)>

The submit button on the app.py app (as of this writing) works only on Linux -- I got it to work by installing VMWare Fusion on the macOS (Ubuntu 22), AND by installing Python  3.11 and pip 3.11 using deadsnakes, then created and activated a virtual environment using python 3.11 and ran  it by typing python app.py. THEN I could call submit without it failing (but have patience: it took 40+ seconds to process a very short audio file.
Using macOS or Windows it would error out in less than 5 seconds.


ENH - Separate the information goal from the path-setting goal in aaClass and global aa

Both the "global aa" and aaClass have a dual use, with very little overlap between the uses.
The first use is to provide information (from the combined .json file and .git info).
The second use is to have the paths set, and have a way to check whether they indeed have been set.
By separating the first use into a dedicated function (with a local persistent variable to hold the info, so the file processing only has to be done once), it can be made much easier to evaluate whether the second use is done correctly.

Then also replace code like
[aahome,~,~] = fileparts(which('aa_ver5'));
with a call to the info function, and use the .Path from there.


BioModel Discussion Issue for eos1af5

Summary !!!

BioModel Name: Jiménez-Luna2021 - Coloring molecules for Caco-2 cell permeability.

BioModel Tag: Machine learning model, Ersilia

Metadata Comments:
The endpoints for this model is for Caco-2 cell permeability.

Contributor:

roles
Names

Curator
@Zainab-ik

Code contributor
@miquelduranfrigola

Reviewer
@GemmaTuron

Curation status :  manually curated

Annotation file: here

Let's check if the data is available in the cited publications:
For this endpoint, passive permeability data from 239 compounds were collected from two independent studies.47,48

Reference 47 - dataset in supplementary information here - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5744993/bin/pone.0190319.s001.docx
Reference 48 - dataset in supplementary information - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4655101/bin/peerj-03-1405-s001.xls
Both added in annotation


Problem with pushing multi-arch images to gcr.io

When I'm trying to push Heapster images after support for multiple architectures was introduced in #1387 I can see the following issue:
./manifest-tool push from-args --platforms linux/amd64,linux/arm,linux/arm64,linux/ppc64le,linux/s390x --template gcr.io/google_containers/heapster-ARCH:v1.3.0-beta.1  --target gcr.io/google_containers/heapster:v1.3.0-beta.1
INFO[0000] Retrieving digests of images...
INFO[0002] Image "gcr.io/google_containers/heapster-amd64:v1.3.0-beta.1" is digest sha256:<hash>; size: 949
INFO[0004] Image "gcr.io/google_containers/heapster-arm:v1.3.0-beta.1" is digest sha256:<hash>; size: 950
INFO[0006] Image "gcr.io/google_containers/heapster-arm64:v1.3.0-beta.1" is digest sha256:<hash>; size: 950
INFO[0008] Image "gcr.io/google_containers/heapster-ppc64le:v1.3.0-beta.1" is digest sha256:<hash>; size: 950
INFO[0010] Image "gcr.io/google_containers/heapster-s390x:v1.3.0-beta.1" is digest sha256:<hash>; size: 950
FATA[0030] Registry push unsuccessful: response 400: 400 Bad Request
make: *** [push] Error 1

It seems that images for specific architectures was pushed but there is no generic image.

I've contacted some gcr.io folks, I'm waiting for an answer from them.
It works fine on docker hub and should work on gcr as well, but doesn't
Meanwhile, heapster-grafana-amd64:v4.0.2 is available

Another limitation of gcr.io is it doesn't have any human way to find tags. You can use docker search to find images, but then you need to using the API to find tags, e.g. curl https://gcr.io/v2/google-containers/heapster-influxdb-amd64/tags/list, these appear to be the current tags.
gcr.io/google_containers/heapster-influxdb-amd64:v1.1.1
gcr.io/google_containers/heapster-grafana-amd64:v4.0.2
gcr.io/google_containers/heapster-amd64:v1.3.0-beta.1

ping @luxas

Sent a PR: #1502

@piosz This was fixed by inactivating the functionality temporarily, we can now close this

Can we reopen this? GCR now has multiarch support.

@vielmetti please send a PR with the small change to re-enable manifest lists :)


rename the configuration file to the right name

MLH uses cilium-actions.yml as its configuration file. Should then be
named accordingly.
Fixes: 5b8a8405425b (".github: Add maintainer's little helper integration")
Signed-off-by: André Martins<EMAIL_ADDRESS>

Couldn't we change maintainer's little helper instead? cilium-action.yaml as a name for a file under .github/workflows is really not helping tell what it's about
I'm happy to send the PRs to cilium/cilium and maintainer's little helper if that's all that's needed.

That includes all stable branches in cilium/cilium as well as in hubble.

I'm happy to send the PRs to cilium/cilium and maintainer's little helper if that's all that's needed.

That includes all stable branches in cilium/cilium as well as in hubble.

That's totally fine to me. I can send as many PRs as required :-)

PRs opened:

https://github.com/cilium/cilium/pull/16455
https://github.com/cilium/cilium/pull/16456
https://github.com/cilium/cilium/pull/16457
https://github.com/cilium/cilium/pull/16458
https://github.com/cilium/hubble/pull/569

Closed by https://github.com/cilium/github-actions/pull/15


ErrorHandling concept with user defined actions

Brief feature description
In a safety certified environment the user may would like to define what reaction certain errors cause. Like:

call to std::terminate
throw an exception
inform some watch dog and go into a spinlock

Furthermore, to avoid death tests in unit tests customizing the behavior so that exceptions can be thrown can be useful. This would require to get rid of noexcept. The idea would be that iceoryx never throws an exceptions but allows the user to overload/define the error handling so that it is capable of throwing custom exception which is at the moment impossible since noexcept is in place.
Details
Iceoryx as a framework should enable the user to pursue any error concept they like with a fitting interface. This error concept should then be used uniformly in all iceoryx components so that we have one single call like errorHandler( instead of a wild mixture of std::terminate, cxx::Expects, cxx::Ensures, assert etc.
This call may require the origin, cause, severity of the error so that user defined callbacks can be defined to react differently based on origin, severity and cause.
@elBoberido fell asleep on his keyboard and maybe the products of his dreams can provide us with further insights, see here
Definition of done
The error handling concept is documented in: doc/design/error-handling.md. For this the current error handling concept may have to be discarded/rewritten.
Follow-up issues can then implement the error concept.
Further insights
We have the ability to allow the user to throw exceptions in callbacks, cxx::function or cxx::function_ref but noexcept will cause always a std::terminate.
This is especially a problem in tests where we avoid fatal errors with Expects or the error handler. This is untestable since the errorhandler calls the custom handler and then continues - we require an exception here to make the code testable.
Think of testing this piece of code:
void doStuff(someClass * ptr) {
  iox::cxx::Expects(ptr != nullptr);

  ptr->doStuff();
}

A test like
auto handle =
    iox::ErrorHandler::setTemporaryErrorHandler([&](auto, auto, auto) { wasErrorHandlerCalled = true; });
doStuff(nullptr);
EXPECT_TRUE(wasErrorHandlerCalled);

will always end up with a segfault since the code in doStuff continues after the error handler call. But if we would allow exceptions we could throw an exception in the error handler and safely return to the test.
Then the test only has to verify that the exception was thrown and this indicates that we correctly used the error handler in doStuff.
Requirements
Open for discussions

exchange error handling on compile time, switch on runtime is forbidden

must be defined via iceoryx_platform and stored in platform

no dependencies to iceoryx_hoofs
it should support exceptions, the whole iceoryx code base should support exceptions (remove noexcept)
3 error levels, moderate, error and fatal

on fatal the error handler must be blocking

Todo

[ ] Replace all assert with the new one
[ ] Taken from #1196 : remove requires.hpp and replace Expects and Ensure with IOX_ASSERT

@elfenpiff Thanks for creating this error! I checked the SEI CERT C++ rule-set mentioned in the CONTRIBUTING.md: It's quite plausible that terminating the program abruptly without calling the d'tor may cause security issues e.g. left-over open sockets. See rule ERR50-CPP.

Working on this now. Starting with a list of requirements followed by a prototype.

@MatthiasKillat Is there anything still to be done for the release v3.0 in this issue?


Factor 1/2 in get_molecular_hamiltonian

In the function get_molecular_hamiltonian of the molecular_data class, you go from spatial orbitals to spin-orbitals for a given set of molecular integrals to initialize an InteractionOperator:
for p in range(n_qubits // 2):
            for q in range(n_qubits // 2):

                # Populate 1-body coefficients. Require p and q have same spin.
                one_body_coefficients[2 * p, 2 * q] = one_body_integrals[p, q]
                one_body_coefficients[2 * p + 1, 2 * q +
                                      1] = one_body_integrals[p, q]
                # Continue looping to prepare 2-body coefficients.
                for r in range(n_qubits // 2):
                    for s in range(n_qubits // 2):

                        # Mixed spin
                        two_body_coefficients[2 * p, 2 * q + 1, 2 * r + 1, 2 *
                                              s] = (
                                                  two_body_integrals[p, q, r, s]
                                                  / 2.)
                        two_body_coefficients[2 * p + 1, 2 * q, 2 * r, 2 * s +
                                              1] = (
                                                  two_body_integrals[p, q, r, s]
                                                  / 2.)

                        # Same spin
                        two_body_coefficients[2 * p, 2 * q, 2 * r, 2 * s] = (
                            two_body_integrals[p, q, r, s] / 2.)
                        two_body_coefficients[2 * p + 1, 2 * q + 1, 2 * r +
                                              1, 2 * s + 1] = (
                                                  two_body_integrals[p, q, r, s]
                                                  / 2.)

I think the factor 1/2 is confusing here. This will cause the two_body_coefficients in this function and the InteractionOperator.two_body_tensor to be 1/2 times the molecular integrals. Maybe it would be better to incorporate this factor 1/2 in the InteractionOperator object intrinsically, such that the InteractionOperator.two_body_tensor gives you back exactly the integrals?

Hi @Emieeel I understand how this can be confusing but I think it is consistent with what is output to Interaction operator.  InteractionOperator is strictly coefficient * operator (in matrix form).  There is a 1/2 in front of all the coefficients when defining the Hamiltonian in the spin-orbital basis.
I agree that there is a bit of confusion here so maybe we can elaborate on the documentation in this function.  Another nice thing would be to have the spin-orbital interaction matrix (antisymmetrized <pq||rs>) which corresponds just to the integrals be available from the molecular integrals or active space integrals.  More broadly, having functionality to get J, and K matrices so we can supply methods like Slater-Condon rules would also fall into a similar upgrade.  Are you interested in working on these things?

I see, I understand you would have the InteractionOperator representing not only Hamiltonians with this convention but rather general operators.
I could incorporate a function to return the antisymmetrized integrals and J and K matrices within the InteractionOperator or Molecular_data class, would that be useful?

Yes that would be a really great addition.  Within the MolecularData class is the most appropriate place.  I would recommend writing stand alone functions and then exposing those functions through the MolecularData class.  That way we can use those tools later and we won't be burdened with instantiating a MolecularData object.

Oh, and do you want them in the basis of spatial orbitals or spin-orbitals? I think spatial orbitals (i.e. the one/two_body_integrals object) would be sufficient for doing Slater-condon type calculations as openfermion works in the restricted formalism as far as I know.

Spatial for J and K are fine for all cases.  For the antisymmetric integrals I think you need spin-orbital version...but I'll check on that


Dynamically disable validation for a form

Environment

Ember Version: 2.16.2
Ember CLI Version: 2.16.2
Ember CP Validations Version: 3.5.0

Steps to Reproduce
I have the following in app/validations/change-password.js
import EmberObject, { computed, get, set, setProperties } from '@ember/object';
import {
    buildValidations,
    validator
} from 'ember-cp-validations';
import Mixin from '@ember/object/mixin';

const Validations = buildValidations({
    'passwordObj.current_password': [
        validator('presence', {
            disabled: computed.not('component.editPasswordMode'),
            presence: true
        })
    ],
...

export default Mixin.create(Validations);

The issue I'm having is that I need this fields validations to be disabled/turned off if a property on the parent component is set. In other words, if the user did not click "change password" button on our parent form edit, we want to exclude those fields/validations, likewise include them if they did choose to edit the password.
Currently this doesn't work or I can't seem to get it to work so I'm wondering if I'm missing something or it's not possible? I should say that it needs to be bound to the value so if a user toggles the key, the "disabled" state adjusts with it.
Here is how I hacked the component into the "model" on the parent component:
     set(this. {
                    passwordObj: {
                        component: this,
                        current_password: get(user, 'current_password'),
                        password: get(user, 'password'),
                        confirm_password: get(user, 'confirm_password')
                    },

I'm not sure what component is in this context:
disabled: computed.not('component.editPasswordMode')

But it should either be model.editPasswordMode or model.component.editPasswordMode

got it working thanks!


sqlBatch and "IN" operator

Does parentBatch support sql IN operator?

Can you be more specific? In what sense should it "support" it. When the next batch is fetched, it collects the values from whichever column you specified as the parentKey. It interpolates those values into a SQL IN operator and matches against the child key.