Add desktop screenshots to web app manifest

Hello @jakearchibald,
Following recent Intent to Implement and Ship: Rich PWA installation dialogs - desktop, this PR adds desktop screenshots to https://squoosh.app so that desktop users see wide screenshots instead of narrow screenshots in the PWA rich install UI.

@beaufortfrancois I've made some optimisations. Does it still look good to you?

Good catch. I've fixed the screenshots.


added example docs

added example docs

Codecov Report

Merging #136 into v0.1 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             v0.1     #136   +/-   ##
=======================================
  Coverage   72.36%   72.36%
=======================================
  Files          87       87
  Lines        4089     4089
=======================================
  Hits         2959     2959
  Misses       1130     1130

Flag
Coverage Δ

#unittests
72.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Codecov Report

Merging #136 into v0.1 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             v0.1     #136   +/-   ##
=======================================
  Coverage   72.36%   72.36%
=======================================
  Files          87       87
  Lines        4089     4089
=======================================
  Hits         2959     2959
  Misses       1130     1130

Flag
Coverage Δ

#unittests
72.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Feature webhook

Addresses issue #331
The resource DSL has been updated to include a webhook_token attribute that allows the end user to configure an arbitrary string to be used to trigger a resource to perform a check.
The webhook would be http://{yourserver}/api/v1/teams/:team_name/pipelines/:pipeline_name/resources/:resource_name/check/webhook?access_token=somevalue
There is also a convenience method to generate a token value
http://{yourserver}/api/v1/teams/:team_name/auth/access_token
A separate pull request would need to be submitted to pull in the dependency on https://github.com/satori/go.uuid

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

@mainephd Thank you for signing the Contributor License Agreement!

The acceptance test seems to be behave more consistently locally when i change the default timeout and polling configurations of the Eventually assertions from
SetDefaultEventuallyTimeout(10 * time.Second)
SetDefaultEventuallyPollingInterval(100 * time.Millisecond)

to
 SetDefaultEventuallyTimeout(20 * time.Second)
 SetDefaultEventuallyPollingInterval(1 * time.Second)

Awesome, thanks! 🎊

The CI failure is in acceptance/ - not your fault. I've logged a bug to have us clean that up, it's really annoying for PRs. Merging!

What is the right way to deal with check_every when setting the webhook_token?


Create generator-generic-ossf-slsa3-publish.yml

Discover the cultural heart of Bali as you wander through ancient temples, witness traditional dance performances, and immerse yourself in the vibrant local arts scene. From the majestic sea temples of Tanah Lot to the serene rice terraces of Ubud, Bali offers a tapestry of cultural experiences waiting to be explored.

wat?


Warnings from libffi

I tried submitting a PR to your libffi library, but I can't.

Hi @sigsbeym , May I know what your PR is for?

I was just trying to update from the parent repo.  I was hoping it would resolve the warnings.

Hi see, @sigsbeym . Actually, I use a fork of libffi:  https://github.com/623637646/libffi/tree/release/iOS
There are some changes to support iOS using libffi. I remember I spend a lot of time to make it work. Upgrading libffi is not an easy job. If it works fine, just with some warnings. Just let it go and your life will be easier.

If you use cocoapods, this may help you to ignore the warning. https://stackoverflow.com/questions/13208202/ignore-xcode-warnings-when-using-cocoapods

hi @sigsbeym
Just upgrade libffi to the newest version 3.4.4.
https://github.com/623637646/libffi/tree/release/iOS_3.4.4
Seems the warning is still there.


[docs] Update ref-mariadb-mysql-rqd-connector-cfg-props.adoc

fix property name table-exclude-list to table.exclude.list

Hi @moyq5 please remove the merge commit and make sure all commits are prefixed with [docs].
Thanks!

Thanks @moyq5, applied to main (=3.0) and branch 2.7.


Add function decorator

When function decorators become stable, we should use them to allow simplifying mem calls:
const mem = require("mem")

@mem.Decorator()
function helloWorld() {
	//...
}

Would be nice. The decorator proposal has stalled for years though, so this might not happen anytime soon. I don't want to add it until there's support in at least the latest Node.js version.

Why not? TypeScript supports them. Worst case scenario, you drop them or replace them in a future breaking release, but until then we can use them.
Currently using a simplified version on https://github.com/fregante/webext-options-sync-per-domain/blob/409d408150b8d7dfdd536204437e3b24f9128872/index.ts#L72

Last time I looked into decorators, TS implemented an obsolete version of the spec. That might have changed though. Anyway, I would merge a good PR for this, since there's interest.


Update pfp and trkg4id

Changed track to MCTruth ID to use TruthMatchUtils
Changed the way to compute completeness.
Cicle all hits only once when start to save tracks.
Fix PFP for tracks and showers
Shower's ID is always stored as -999 (at the art root file level). To fix
this, instead of using the map between PFP and ShowerID, I use the
association and create the showerID when looping through the showers.
I also updated the selection isTrack and isShower, to deal with the fact
that both recob::Tracks and recob::Showers have all PFParticles stored.

Thanks!


WIP - Chapter 4/5

https://jrdngr.github.io/pngme_book/chapter_4.html
https://jrdngr.github.io/pngme_book/chapter_5.html

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 24 lines in your changes missing coverage. Please review.

Project coverage is 93.7%. Comparing base (cce833e) to head (b6a5da7).

Files with missing lines
Patch %
Lines

src/main.rs
0.0%
10 Missing :warning:

src/commands.rs
0.0%
8 Missing :warning:

src/args.rs
0.0%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

Files with missing lines
Coverage Δ

src/args.rs
0.0% <0.0%> (ø)

src/commands.rs
0.0% <0.0%> (ø)

src/main.rs
0.0% <0.0%> (ø)


Version 4.0 - Calling Set Battery Charge service returns error

When I call the Alpha ESS: Set Battery Charge service it doesn't set the battery parameters and it returns Unknown Error in my automation.
If I can provide more info, please let me know

After Update to Alpha ESS v.4.0 logon failed. Error Message " Unknown error". Can you pleased fixed?

Did you follow the instructions https://github.com/CharlesGillanders/homeassistant-alphaESS#alphaess-openapi to change the authentication to use your OpenAPI developer AppID and AppSecret?

I too am getting the error when it comes to using the service to set charge.

Everyone makes mistakes.
Thanks for you work on this. It is appreciated.

—
Reply to this email directly, view it on GitHub
https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/80#issuecomment-1811232695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5GM6ZDHTVCK5XS2XJXOMW3YEPJHBAVCNFSM6AAAAAA7K76M46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRGIZTENRZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks as always for your work on getting this new version out (and to everyone who helped with diagnosing / designing that) and for getting this latest fix out so quickly.
Your hard work and timeliness are always appreciated.

Can confirm that 0.4.1 has fixed the issue, thanks once again.

Also for me - my overnight battery charge was set as usual.

It work fine. Many thank for your support.
Best regards
Joerg Voelschow
Von: CharlesGillanders @.>
Gesendet: Donnerstag, 16. November 2023 16:48
An: CharlesGillanders/homeassistant-alphaESS
@.>
Cc: J-89436 @.>; Comment
@.>
Betreff: Re: [CharlesGillanders/homeassistant-alphaESS] Version 4.0 -
Calling Set Battery Charge service returns error (Issue #80)
Closed #80
https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/80  as
completed.

Reply to this email directly, view it on GitHub
<https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/80#event
-10982561322> , or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO3AL52PKT4PWQWPSAOAAULYE
YYUJAVCNFSM6AAAAAA7K76M46VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC
5DJN5XDWMJQHE4DENJWGEZTEMQ> .
You are receiving this because you commented.
<https://github.com/notifications/beacon/AO3AL57RW6UK2MVAOGGWUVTYEYYUJA5CNFS
M6AAAAAA7K76M46WGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3
PNVWWK3TUL5UWJTYAAAAAFDU4SYVA.gif> Message ID:
@.***
ithub.com
<mailto:CharlesGillanders/homeassistant-alphaESS/issue/80/issue_event/109825
@.***> >


Regen

Part of https://github.com/gtk-rs/gir/pull/647
cc @sdroege @EPashkin

@GuillaumeGomez Thanks
👍


[BUG] When working with Semantic Kernel, while invoking ChatCompletion API, unable to specify data sources

Library name and version
Microsoft.SemanticKernel, Microsoft.SemanticKernel.ChatCompletion
Describe the bug
When calling the OpenAI's chat completion API, the SDK doesn't provide an option to specify extra field such as "data_sources"
https://learn.microsoft.com/en-us/azure/ai-services/openai/references/on-your-data?tabs=rest#context
Expected behavior
the SKD should support additional parameter to chat completions API
Actual behavior
the SKD doesn't support additional parameter to chat completions API
Reproduction Steps
Microsoft.SemanticKernel.ChatCompletion.IChatCompletionService.GetStreamingChatMessageContentsAsync()
This method doesn't accept additional parameters to query data on custom data sources
Environment
VS 2022
.NET 6.0
Windows

@Rtoribiog

This issue has been transferred to the repository where the Microsoft.SemanticKernel packages are maintained as #6061.


Only use label_singular when one item is rendered in the listControl

Fixes #1397.
Check the size of the item list and set the listLabel based on that.
If no label_singular is set, fall back to the normal label
- Summary
The list control always used the singular name as label if one is specified, even when the list contains 0 or > 1 items. It's now based on the amount of items thats provided.
- Test plan
Tested with the existing authors settings in the example CMS.
With 2 authors:

With 1 author:

With 0 authors:

- Description for the changelog
Base the listLabel on the size of the list provided.
- A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit aea97b29e3bd8de656b49408bba0ae0273c6ef05
https://deploy-preview-1422--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit aea97b29e3bd8de656b49408bba0ae0273c6ef05
https://deploy-preview-1422--cms-demo.netlify.com


Post-order element traversal

Cascaded unions are a desirable feature for the geo library. However, the algorithm requires post-order traversal of the tree in order to work, but iteration order is currently not specified.

I may be out of depth here, but the data in the R-Tree is only at the leaf-nodes right?  So what does a post-order traversal mean for a R-Tree?  Also, does locate_with_selection_function help?  It offers to selectively open each intermediate bounding box based on a custom predicate.

I think the idea is that we begin with unions of the smallest subsets (the deepest leaf nodes?) before moving up, and it's this that requires the post-order (reverse post-order, so moving from right-to-left would also work I think?); unless I'm misunderstanding that's where the efficiency comes from: the closer you get to the root, the less work there is to do.
I'm not sure how the locate-with-selection-function would help here, but I've never used it and I may well be being dense about that.

Got it.  The issue is that the R-Tree itself has no user-data available at the intermediate nodes, so all the iterations have no concept of post-order.
I suppose you want to be able to do a map-reduce op on the R-Tree, where each intermediate (aka ParentNode) is reduced to a new polygon (union of its children), and do that in a bottom-up fashion.  The locate-with-selection is essentially the reverse:  it is a "pre-order" traversal as it queries if you intend to traverse a given intermediate node, before delving into it.
Here is one suggestion (just thinking aloud):  we add a function to the trait SelectionFunction that also signals when we are done with a particular intermediate node.
trait SelectionFunction<...> {
  fn finished_unpacking_parent(...) {}
}

This can(?) then be used to drive a post-order / map-reduce op.  Unfortunately, the trait SelectionFunction seems to take &self and not &mut self which seems a bit restrictive in the first-place.

Also, note that the root node, and then children of intermediate nodes can be accessed via public methods, so we can implement the union-algorithm without using the iterators.

Got it.  The issue is that the R-Tree itself has no user-data available at the intermediate nodes, so all the iterations have no concept of post-order.
Ahh, yep.

I suppose you want to be able to do a map-reduce op on the R-Tree, where each intermediate (aka ParentNode) is reduced to a new polygon (union of its children), and do that in a bottom-up fashion.

This is my understanding too, yes.

Here is one suggestion (just thinking aloud):  we add a function to the trait SelectionFunction that also signals when we are done with a particular intermediate node.

trait SelectionFunction<...> {

  fn finished_unpacking_parent(...) {}

}

This can(?) then be used to drive a post-order / map-reduce op.  Unfortunately, the trait SelectionFunction seems to take &self and not &mut self which seems a bit restrictive in the first-place.

Don't we still have the problem of not knowing where to start, though?

The SelectionFunction already has a method should_unpack_parent that tells when it starts unpacking a parent node.  That along with some nifty usage of a vec/stack should let us do it.   However, it all seems more complicated than just directly recursing on the RTree nodes.
I would support introducing a new trait to support this type of map-reduce-fold if we could brain-storm a little bit.  There are a couple of diff. use-cases here:

Pure reduce.  This is the current use-case you've mentioned iiuc; the final output is same as the R-Tree type T
Map + reduce.  First an intermediate T -> R on the data nodes, then reduce bottom-up to a final output R.  Note that the R may not itself be an RTreeObject so it's hard to divide this up into two composable ops
Fold.  In iterators (std, rayon) there is also a distinction between reduce and fold.  This is if leaf is not mapped from T -> R, but the penultimate intermediate nodes compute [T] -> R;  the rest of the levels still compute [R] -> R.  It could be rephrased as map + reduce, but the T -> R, and then [R] -> R might be more inefficient, than just directly converting from [T] -> R.  This only helps at the bottom most level, so may be not worth it for trees.

Now, unfortunately the naive trait defn. I could think of to handle the above seems to involve many intermediate Vec allocations, that seems to hinder it's usage in a good algo impl.  The direct recursion on the nodes seems simpler as it is more flexible.

The direct recursion on the nodes seems simpler as it is more flexible.

So something like
fn fold_reduce<T, S, I, F, R>(tree: &RTree<T>, mut init: I, mut fold: F, mut reduce: R) -> S
where
    T: RTreeObject,
    I: FnMut() -> S,
    F: FnMut(S, &T) -> S,
    R: FnMut(S, S) -> S,
{
    fn inner<T, S, I, F, R>(parent: &ParentNode<T>, init: &mut I, fold: &mut F, reduce: &mut R) -> S
    where
        T: RTreeObject,
        I: FnMut() -> S,
        F: FnMut(S, &T) -> S,
        R: FnMut(S, S) -> S,
    {
        parent
            .children()
            .iter()
            .fold(init(), |accum, child| match child {
                RTreeNode::Leaf(value) => fold(accum, value),
                RTreeNode::Parent(parent) => {
                    let value = inner(parent, init, fold, reduce);

                    reduce(accum, value)
                }
            })
    }

    inner(tree.root(), &mut init, &mut fold, &mut reduce)
}

?

I think what is also nice about this way of doing things is that it has a straight-forward parallel version using Rayon which could come in handy for large data sets:

fn parallel_bottom_up_fold_reduce<T, S, I, F, R>(tree: &RTree<T>, init: I, fold: F, reduce: R) -> S
where
    T: RTreeObject,
    RTreeNode<T>: Send + Sync,
    S: Send,
    I: Fn() -> S + Send + Sync,
    F: Fn(S, &T) -> S + Send + Sync,
    R: Fn(S, S) -> S + Send + Sync,
{
    fn inner<T, S, I, F, R>(parent: &ParentNode<T>, init: &I, fold: &F, reduce: &R) -> S
    where
        T: RTreeObject,
        RTreeNode<T>: Send + Sync,
        S: Send,
        I: Fn() -> S + Send + Sync,
        F: Fn(S, &T) -> S + Send + Sync,
        R: Fn(S, S) -> S + Send + Sync,
    {
        parent
            .children()
            .into_par_iter()
            .fold(init, |accum, child| match child {
                RTreeNode::Leaf(value) => fold(accum, value),
                RTreeNode::Parent(parent) => {
                    let value = inner(parent, init, fold, reduce);

                    reduce(accum, value)
                }
            })
            .reduce(init, reduce)
    }

    inner(tree.root(), &init, &fold, &reduce)
}

Thanks for fleshing out the details @adamreichold !  Looks quite on track; like the easy rayon support.   Just a few minor comments / points to discuss:

The init parameter should probably take the bounding-box AABB as ref, as it is available anyway, and might help in initializing some structures that help with the reduce/fold.

Is (S, S) -> S as efficient as (&mut S, S) if S is big?  Rust may be optimizing it away as we're just storing the returned value back into the accumulator for the next iteration, but I wasn't too sure.

I wonder if there are use-cases where it is more efficient to directly reduce &[S] -> S.  Even with polygon clipping, the underlying data-structure is better built once for the sequence than during each iterative reduction.  Unfortunately, I don't see a neat way to handle that use-case without many Vec allocations.

The init parameter should probably take the bounding-box AABB as ref, as it is available anyway, and might help in initializing some structures that help with the reduce/fold.

:+1:

Is (S, S) -> S as efficient as (&mut S, S) if S is big? Rust may be optimizing it away as we're just storing the returned value back into the accumulator for the next iteration, but I wasn't too sure.

Both std and `rayon seem to pass the accumulator by value. I think, if it was really expensive to move and not optimized properly, one would box it?

I wonder if there are use-cases where it is more efficient to directly reduce &[S] -> S. Even with polygon clipping, the underlying data-structure is better built once for the sequence than during each iterative reduction. Unfortunately, I don't see a neat way to handle that use-case without many Vec allocations.

I do not know the details of those auxiliary data structures, but maybe moving them into the closures would help? (At least in the serial case. Not sure whether thread-local storage is worth that in the parallel case.)
Maybe the above could also accommodate this differently: S could keep auxiliary allocations around, e.g. a Vec<T> to delay the union computation until the next call to reduce?
In any case, I think the main take away could also be that we do not really need to make these decisions in a general context as the traversal/reduction can be written against the existing rstar API (and I don't see any obvious performance gains from having access to its internals) so when geo implements cascaded unions, it can use code like the above but tailored to its specific use case.
 Should it then also optionally provide the parallel variant?

Adding a vote for this feature https://discord.com/channels/598002550221963289/598002550221963291/1068880307664724060
Use case is similar to https://github.com/geopolars/geopolars/issues/20

The single-threaded implementation of this will land in geo at some point: https://github.com/georust/geo/pull/1246.

I didn't investigate the AABB hint or auxiliary allocation for S (not sure how that would work), but perf on intermediate real-world workloads (39k polygons, around 73.8 mb of WKT) is excellent: 11 seconds wall-clock for a complete union op on the tree.
Here's what I ended up with:
fn bottom_up_fold_reduce<T, S, I, F, R>(
    tree: &RTree<T>,
    mut init: I,
    mut fold: F,
    mut reduce: R,
) -> S
where
    T: RTreeObject,
    I: FnMut() -> S,
    F: FnMut(S, &T) -> S,
    R: FnMut(S, S) -> S,
{
    fn inner<T, S, I, F, R>(parent: &ParentNode<T>, init: &mut I, fold: &mut F, reduce: &mut R) -> S
    where
        T: RTreeObject,
        I: FnMut() -> S,
        F: FnMut(S, &T) -> S,
        R: FnMut(S, S) -> S,
    {
        parent
            .children()
            .iter()
            .fold(init(), |accum, child| match child {
                RTreeNode::Leaf(value) => fold(accum, value),
                RTreeNode::Parent(parent) => {
                    let value = inner(parent, init, fold, reduce);
                    reduce(accum, value)
                }
            })
    }

    inner(tree.root(), &mut init, &mut fold, &mut reduce)
}

with init, fold, and reduce specified as:
let init = || MultiPolygon::<T>::new(vec![]);
let fold = |mut accum: MultiPolygon<T>, poly: &Polygon<T>| -> MultiPolygon<T> {
    accum = accum.union(poly);
    accum
};
let reduce = |accum1: MultiPolygon<T>, accum2: MultiPolygon<T>| -> MultiPolygon<T> {
    accum1.union(&accum2)
};

I'm very happy to keep the implementation in consumer libraries, but it would be good to capture the mechanism for this kind of full traversal and intermediate processing in the crate's docs somewhere – it's complex and deep knowledge of the rstar's internal API is rare enough.


Error in Lint/RedundantCopDisableDirective

An error occurred while Lint/RedundantCopDisableDirective cop was inspecting following file:
class Foo
  # rubocop:disable Style
  include Bar
  # rubocop:enable all
end

Expected behavior
No errors.
Actual behavior
$ be rubocop test.rb -d
For ...: configuration from .../.rubocop.yml
Default configuration from .../gems/rubocop-1.38.0/config/default.yml
Use parallel by default.
Skipping parallel inspection: only a single file needs inspection
Inspecting 1 file
Scanning .../test.rb
An error occurred while Lint/RedundantCopDisableDirective cop was inspecting .../test.rb.
Couldn't find Style/ArrayCoercion in comment: # rubocop:disable Style
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:256:in `cop_range'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:233:in `block in add_offense_for_some_cops'
.../lib/ruby/3.1.0/set.rb:511:in `each_key'
.../lib/ruby/3.1.0/set.rb:511:in `each'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:233:in `map'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:233:in `add_offense_for_some_cops'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:212:in `block in add_offenses'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:208:in `each'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:208:in `add_offenses'
.../gems/rubocop-1.38.0/lib/rubocop/cop/lint/redundant_cop_disable_directive.rb:51:in `on_new_investigation'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:153:in `block (2 levels) in invoke'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:160:in `with_cop_error_handling'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:153:in `block in invoke'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:153:in `each'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:153:in `invoke'
.../gems/rubocop-1.38.0/lib/rubocop/cop/commissioner.rb:84:in `investigate'
.../gems/rubocop-1.38.0/lib/rubocop/cop/team.rb:154:in `investigate_partial'
.../gems/rubocop-1.38.0/lib/rubocop/cop/team.rb:82:in `investigate'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:315:in `inspect_file'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:172:in `block in add_redundant_disables'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:193:in `team_for_redundant_disables'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:171:in `add_redundant_disables'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:139:in `block in file_offenses'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:163:in `file_offense_cache'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:137:in `file_offenses'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:128:in `process_file'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:109:in `block in each_inspected_file'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:108:in `each'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:108:in `reduce'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:108:in `each_inspected_file'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:94:in `inspect_files'
.../gems/rubocop-1.38.0/lib/rubocop/runner.rb:47:in `run'
.../gems/rubocop-1.38.0/lib/rubocop/cli/command/execute_runner.rb:26:in `block in execute_runner'
.../gems/rubocop-1.38.0/lib/rubocop/cli/command/execute_runner.rb:52:in `with_redirect'
.../gems/rubocop-1.38.0/lib/rubocop/cli/command/execute_runner.rb:25:in `execute_runner'
.../gems/rubocop-1.38.0/lib/rubocop/cli/command/execute_runner.rb:17:in `run'
.../gems/rubocop-1.38.0/lib/rubocop/cli/command.rb:11:in `run'
.../gems/rubocop-1.38.0/lib/rubocop/cli/environment.rb:18:in `run'
.../gems/rubocop-1.38.0/lib/rubocop/cli.rb:72:in `run_command'
.../gems/rubocop-1.38.0/lib/rubocop/cli.rb:79:in `execute_runners'
.../gems/rubocop-1.38.0/lib/rubocop/cli.rb:48:in `run'
.../gems/rubocop-1.38.0/exe/rubocop:19:in `block in <top (required)>'
.../lib/ruby/3.1.0/benchmark.rb:311:in `realtime'
.../gems/rubocop-1.38.0/exe/rubocop:19:in `<top (required)>'
.../bin/rubocop:25:in `load'
.../bin/rubocop:25:in `<top (required)>'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli/exec.rb:58:in `load'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli/exec.rb:58:in `kernel_load'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli/exec.rb:23:in `run'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli.rb:483:in `exec'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli.rb:31:in `dispatch'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/cli.rb:25:in `start'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/exe/bundle:48:in `block in <top (required)>'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
.../lib/ruby/gems/3.1.0/gems/bundler-2.3.14/exe/bundle:36:in `<top (required)>'
.../bin/bundle:25:in `load'
.../bin/bundle:25:in `<main>'
.

RuboCop version
$ [bundle exec] rubocop -V
1.38.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.23.0, running on ruby 3.1.2) [x86_64-linux]

This issue may be the same as https://github.com/rubocop/rubocop/issues/11143.

For what it's worth, I've also experienced this exact same bug, with a different Style cop, but with the exact same stacktrace.
I can trigger it with the following file:
# rubocop:disable Style
def foo bar

end
# rubocop:enable Style

And in a yaml file:
Style/AccessorGrouping: { Enabled: false }

And then run with `rubocop -c tmp/rubocop-err.yml tmp/rubocop-err.rb
With some experimentation, the "Couldn't find" comment seems to reference the first (alphabetically) Style cop that with Enabled: false in the config file.  If I enable the cop with the error, the next cop (alphabetically) that is disabled will cause the error.

I'm going close this issue because it has been resolved with latest RuboCop 1.41. Please upgrade to the latest RuboCop.


[cxx-interop] Rename swift-interop-support.h -> swift/bridging.

There are some updates to the contents as well. Those will be a different patch.

@swift-ci please smoke test

🌉


Could not Pass Data Source Credentials?

Hello Team,
First of all, thank you very much for the extension and appreciate you.
We're able to deploy the data source (.rds) and report files (.rdl) to existing folder structure (Can't create a folder using other SQL Server folder structure relese extension).
But in release definition we don't find options to pass the username and password for data source (.rds)
Kindly help to set up this in release definition, because we use different user name and password in each environment.
Below are reference screenshots.

Release definition confiuration

Deployed atrifacts

Please let us know if I can provide any further details.
Thanks,
Sathi Reddy

You should be able to add them in the connectionstring

Muziekklas,
I tried different ways to pass the credentials in the connection string.
Please give an example which you have tried and worked for you.

Something like this should work: Server=myServerAddress;Database=myDataBase;User Id=myUsername;
Password=myPassword;


workspace is incorrectly indented

In this page, there is a section talking about workspace. One of the coding snippets it has workspace inside of pool which is miss-leading.

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

ID: 67504b34-d64b-02a4-2e10-ab99f3b8cfe4
Version Independent ID: 2cf63b2e-184b-7726-3b8a-d8baffd6fcce
Content: Jobs in Azure Pipelines and TFS - Azure Pipelines
Content Source: docs/pipelines/process/phases.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

Fixing in PR MicrosoftDocs/azure-devops-docs-pr/pull/2841
Will close when change is merged.


Create test cases for ListErrors

Issue summary
A unit test should be created for the ListErrors.vue component. It should be in the /tests/unit/components component. There are also similar examples in this folder for unit tests. The component should be tested for different errors props.
Acceptance criteria

A unit test is created and passing for the ListErrors.vue component

I'll give this a go


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/68091
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 9221b21268a6be0adc0e20a7b20c8eb99d683183
git push origin v0.1.2


Winners gallery updates

Fixes #653
This PR helps fix the winners gallery so that the app will now show the appropriate gallery of winners based on the winners announcement date instead of waiting for when a new scholarship is created.
Updates include:

style updates to various administrative forms
reduced the initial SQL queries to collect the winner's data from 20+ to 4 total
better caching control, so that winners galleries are cached based on scholarship id, and when winner data is updated, the cache is cleared so the gallery will immediately update with the new information.
a few other efficiency gains and additional cleanup

@angaither
CC: @mikefantini @lizzydivine
Note: Future PR coming up will handle clearing the cache for Scholarship settings, so if any of that data is changed the cache will update. This will help avoid the need to manually clear cache settings via SSHing in and running a terminal command! This PR will also include an update to allow removing an applicant's status as a winner in case they were designated as one in error.

:cool: :cool: I would just double check that this works with many different winners cases, like if there aren't winners/if there are two sets/etc/etc
Also looks like we need to add that composer-self-update step to werker... the build failed :anguished:

Yep, it should but I can double-check. If there are no winners, then it doesn't show anything. It only selects a single set of winners based on Scholarship ID so there shouldn't be an issue with sets (that is if I interpreted what you mean by set ;)

Yeah, also mentioned in that PR I ended up closing that Wercker was failing due to the composer update. Would this be a @blisteringherb thing?


How do I include Root and Intermediate certs?

First off, thanks so much for your efforts! Much appreciated! :)
I get a X509_verify_cert error trying to verify the signature. The error further states err=20; msg=unable to get local issuer certificate so it is because the signature lacks the Root and Intermediate information.
How can I get the signature to include the Root/Intermediate certs?

Do you have any sample code or additional information? Ideally, a test that reproduces the problem would be provided so that we can see how to reproduce the issue and can verify that the fix works, and stays working. Please consider contributing one.


Unexpected result for mat-dialog-close

#9020 is still relevant, please see #9020 for details.

The reason why #9020 was closed still stands: there's no way for us to distinguish between <button mat-close> and <button [mat-close]="''"> so we can't close the dialog with undefined by default.

Closing this because it's not feasible for us to distinguish between an intentional empty string an an attribute without a binding


Error when i try to install AMUSE with 'pip install amuse'

I'm trying to install amuse in a WSL 2 ubuntu app in windows 10, i've installed almos every prerequisites created the enviroment and everyting, but when it comes to use te command 'pip install amuse' the console  sends me this:
 ERROR: Command errored out with exit status 1:
   command: /home/seba/Amuse-env/bin/python3 /home/seba/Amuse-env/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-_42pxwgb/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'amuse-framework>=13.0.0[MPI]' 'amuse-athena>=13.0.0' 'amuse-bhtree>=13.0.0' 'amuse-brutus>=13.0.0' 'amuse-bse>=13.0.0' 'amuse-capreole>=13.0.0' 'amuse-evtwin>=13.0.0' 'amuse-fastkick>=13.0.0' 'amuse-fi>=13.0.0' 'amuse-fractalcluster>=13.0.0' 'amuse-gadget2>=13.0.0' 'amuse-galactics>=13.0.0' 'amuse-galaxia>=13.0.0' 'amuse-halogen>=13.0.0' 'amuse-hermite>=13.0.0' 'amuse-hop>=13.0.0' 'amuse-huayno>=13.0.0' 'amuse-kepler>=13.0.0' 'amuse-kepler-orbiters>=13.0.0' 'amuse-mameclot>=13.0.0' 'amuse-mercury>=13.0.0' 'amuse-mmams>=13.0.0' 'amuse-ph4>=13.0.0' 'amuse-seba>=13.0.0' 'amuse-secularmultiple>=13.0.0' 'amuse-smalln>=13.0.0' 'amuse-sphray>=13.0.0' 'amuse-sse>=13.0.0' 'amuse-twobody>=13.0.0'
       cwd: None
  Complete output (149 lines):
  DEPRECATION: Extras after version '>=13.0.0[MPI]'. pip 21.0 will remove support for this functionality. A possible replacement is moving the extras before version specifiers.
  Processing ./.cache/pip/wheels/1e/83/49/ce4178d5e049caf9b0682d47822c6756bc4c074ffc147c879e/amuse_framework-13.2.1-py3-none-any.whl
  Processing ./.cache/pip/wheels/1e/30/a4/d399a51ea193917dd4fa27b5d633745bcf42cdfa0acba8b2b6/amuse_athena-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/36/e7/ab/27171f71f87fb155d2d8ae3590834a5e14157e9ca9f0c496d0/amuse_bhtree-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/e3/95/f4/4ae32d9531b1cc57ce79a7dc6c224094756b85de28e4f4300c/amuse_brutus-13.2.1-py3-none-any.whl
  Processing ./.cache/pip/wheels/f8/d7/db/995113bcad3cf0e1b014c324dc874739823e14a845d6b39c6a/amuse_bse-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/9d/f9/86/51af5ed6fdbf6ef222a0ef687b079e421a5139c6fecc03aded/amuse_capreole-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/0a/fe/35/08d8910d4e8c98e379695f19d5c5cc3e47dca3877d1bd86a42/amuse_evtwin-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/2a/58/f7/cd02f9fbe2041b2fdb52fa200cce7d4c318c3fd3afc156b9dc/amuse_fastkick-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/70/8d/00/962850ae24cc0570570108714950e7d67dfe755c6d6a9ca692/amuse_fi-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/ee/9b/fd/7a7a800f4c756560e2f54325cebed123e6685b7ffafa7fe1a4/amuse_fractalcluster-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/9c/e6/7a/3a1f1a75d912225b1ac083618af14ed864329cf1e41bcbfbcc/amuse_gadget2-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/43/02/7e/27133d9908f3ea873258c8d5a9f3b64b531019ce505fc40966/amuse_galactics-13.2.0-py3-none-any.whl
  Collecting amuse-galaxia>=13.0.0
    Using cached amuse-galaxia-13.2.0.tar.gz (36 kB)
    Installing build dependencies: started
    Installing build dependencies: finished with status 'done'
    Getting requirements to build wheel: started
    Getting requirements to build wheel: finished with status 'done'
      Preparing wheel metadata: started
      Preparing wheel metadata: finished with status 'done'
  Processing ./.cache/pip/wheels/1d/d7/52/c187dd742d50e1f7b5fabab5725766f129ba93e22c25753e9c/amuse_halogen-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/5c/a6/ab/c6d55d658ecbe6e433c03c34fc29f7c09a7f26d0c952017e3d/amuse_hermite-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/b7/47/f2/e0918c12acf0345ba1cad36f23df5ae39761c5d5b59ed80d8a/amuse_hop-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/74/08/51/5e6ee2b0a5e7a9ccff1ce31f431a5c6d415ad998084cf7a8a5/amuse_huayno-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/4c/44/ee/b2a6db9a316804d0a48d21007c19d763b20fe9ad35550496cc/amuse_kepler-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/e8/ec/5d/71adb89e9e024cf3255f98da4f98fb91b2cc8c899a0bf32104/amuse_kepler_orbiters-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/d5/60/1c/93006e6ab9f40fffdb52f64e8d0411061bbe01c514e471cac5/amuse_mameclot-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/a8/3c/9d/1f85edb4287fe0bc03700c2660a730f348098a3dbea3bde0c8/amuse_mercury-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/ec/b0/e3/07e4de03531c62a8e8342ccea341db3453f993a6bf241d7e20/amuse_mmams-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/f8/32/7b/f16bb944b6b28767a8b3d5e3890148768d5ebe7da7bfcf6f67/amuse_ph4-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/f2/5e/ad/45e999c323900a784284506d32c8515b2a362e00a298b57924/amuse_seba-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/69/a7/08/bb6f0b2664ef5cdf025c72db6e554d12ed5ad50d02592e2aa3/amuse_secularmultiple-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/eb/98/6b/8591ef82dbd378103adb2f258d4bf1a25243c6915037f3d222/amuse_smalln-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/69/d3/e9/dfc8dde52c2423c4aeb75c91577578af846e8e120f3f2a0bc0/amuse_sphray-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/2b/80/68/bb82809a3db47451a7c1bcd50ea6e9d7ddddb3ce0cb9c5cd32/amuse_sse-13.2.0-py3-none-any.whl
  Processing ./.cache/pip/wheels/d7/13/24/6cac26ee0d9b7d32e5f493b190b95fe3cb87481cce1d2599a0/amuse_twobody-13.2.0-py3-none-any.whl
  Collecting setuptools>=41.0.0
    Using cached setuptools-50.3.0-py3-none-any.whl (785 kB)
  Collecting pytest>=4.0
    Using cached pytest-6.0.2-py3-none-any.whl (270 kB)
  Collecting h5py>=1.1.0
    Using cached h5py-2.10.0-cp38-cp38-manylinux1_x86_64.whl (2.9 MB)
  Collecting pip>=19.0.0
    Using cached pip-20.2.3-py2.py3-none-any.whl (1.5 MB)
  Collecting wheel>=0.32
    Using cached wheel-0.35.1-py2.py3-none-any.whl (33 kB)
  Collecting numpy>=1.2.2
    Using cached numpy-1.19.2-cp38-cp38-manylinux2010_x86_64.whl (14.5 MB)
  Collecting docutils>=0.6
    Using cached docutils-0.16-py2.py3-none-any.whl (548 kB)
  Processing ./.cache/pip/wheels/ff/61/0c/c516bd6b85f61f0acf333b0fbf5102fe39928a3563bf245a88/mpi4py-3.0.3-cp38-cp38-linux_x86_64.whl
  Collecting toml
    Using cached toml-0.10.1-py2.py3-none-any.whl (19 kB)
  Collecting py>=1.8.2
    Using cached py-1.9.0-py2.py3-none-any.whl (99 kB)
  Collecting more-itertools>=4.0.0
    Using cached more_itertools-8.5.0-py3-none-any.whl (44 kB)
  Collecting attrs>=17.4.0
    Using cached attrs-20.2.0-py2.py3-none-any.whl (48 kB)
  Collecting iniconfig
    Using cached iniconfig-1.0.1-py3-none-any.whl (4.2 kB)
  Collecting packaging
    Using cached packaging-20.4-py2.py3-none-any.whl (37 kB)
  Collecting pluggy<1.0,>=0.12
    Using cached pluggy-0.13.1-py2.py3-none-any.whl (18 kB)
  Collecting six
    Using cached six-1.15.0-py2.py3-none-any.whl (10 kB)
  Collecting pyparsing>=2.0.2
    Using cached pyparsing-2.4.7-py2.py3-none-any.whl (67 kB)
  Building wheels for collected packages: amuse-galaxia
    Building wheel for amuse-galaxia (PEP 517): started
    Building wheel for amuse-galaxia (PEP 517): finished with status 'error'
    ERROR: Command errored out with exit status 1:
     command: /home/seba/Amuse-env/bin/python3 /home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmp_gun8xr_
         cwd: /tmp/pip-install-zrjshivb/amuse-galaxia
    Complete output (68 lines):
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build/lib
    creating build/lib/amuse
    creating build/lib/amuse/community
    creating build/lib/amuse/community/galaxia
    copying src/amuse/community/galaxia/interface.py -> build/lib/amuse/community/galaxia
    copying src/amuse/community/galaxia/__init__.py -> build/lib/amuse/community/galaxia
    running build_codes
    building libraries and community codes
    build, for logging, see 'build.log'
    creating build/temp.linux-x86_64-3.8
    creating build/temp.linux-x86_64-3.8/codes
    creating build/temp.linux-x86_64-3.8/codes/galaxia
    copying src/amuse/community/galaxia/interface.py -> build/temp.linux-x86_64-3.8/codes/galaxia
    copying src/amuse/community/galaxia/interface.f90 -> build/temp.linux-x86_64-3.8/codes/galaxia
    copying src/amuse/community/galaxia/Makefile -> build/temp.linux-x86_64-3.8/codes/galaxia
    copying src/amuse/community/galaxia/__init__.py -> build/temp.linux-x86_64-3.8/codes/galaxia
    [15:35:41] building galaxia
    will copy worker: src/amuse/community/galaxia
    galaxia
    Community codes not built (because of errors):
    ================================================================================
     * galaxia
    ================================================================================
    0 out of 1 codes built, 0 out of 0 libraries built
    Traceback (most recent call last):
      File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
        main()
      File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
        json_out['return_val'] = hook(**hook_input['kwargs'])
      File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 204, in build_wheel
        return _build_backend().build_wheel(wheel_directory, config_settings,
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 216, in build_wheel
        return self._build_with_temp_dir(['bdist_wheel'], '.whl',
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 202, in _build_with_temp_dir
        self.run_setup()
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 253, in run_setup
        super(_BuildMetaLegacyBackend,
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 145, in run_setup
        exec(compile(code, __file__, 'exec'), locals())
      File "setup.py", line 36, in <module>
        setup(
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/tmp/pip-build-env-js1rdt2m/overlay/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 290, in run
        self.run_command('build')
      File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/usr/lib/python3.8/distutils/command/build.py", line 135, in run
        self.run_command(cmd_name)
      File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/tmp/pip-install-zrjshivb/amuse-galaxia/support/setup_codes.py", line 1093, in run
        raise Exception("No succesful builds detected. Aborting.")
    Exception: No succesful builds detected. Aborting.
    ----------------------------------------
    ERROR: Failed building wheel for amuse-galaxia
  Failed to build amuse-galaxia
  ERROR: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
  ----------------------------------------
ERROR: Command errored out with exit status 1: /home/seba/Amuse-env/bin/python3 /home/seba/Amuse-env/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-_42pxwgb/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'amuse-framework>=13.0.0[MPI]' 'amuse-athena>=13.0.0' 'amuse-bhtree>=13.0.0' 'amuse-brutus>=13.0.0' 'amuse-bse>=13.0.0' 'amuse-capreole>=13.0.0' 'amuse-evtwin>=13.0.0' 'amuse-fastkick>=13.0.0' 'amuse-fi>=13.0.0' 'amuse-fractalcluster>=13.0.0' 'amuse-gadget2>=13.0.0' 'amuse-galactics>=13.0.0' 'amuse-galaxia>=13.0.0' 'amuse-halogen>=13.0.0' 'amuse-hermite>=13.0.0' 'amuse-hop>=13.0.0' 'amuse-huayno>=13.0.0' 'amuse-kepler>=13.0.0' 'amuse-kepler-orbiters>=13.0.0' 'amuse-mameclot>=13.0.0' 'amuse-mercury>=13.0.0' 'amuse-mmams>=13.0.0' 'amuse-ph4>=13.0.0' 'amuse-seba>=13.0.0' 'amuse-secularmultiple>=13.0.0' 'amuse-smalln>=13.0.0' 'amuse-sphray>=13.0.0' 'amuse-sse>=13.0.0' 'amuse-twobody>=13.0.0' Check the logs for full command output.

hmmm, appaerently amuse-galaxia is failing to build - which version of ubuntu are you on? You can try to check the build log to see what the error is: do a pip install amuse-galaxia --no-clean -v and tehn search for the build.log file in the build directory reported...

Currently im using ubunto 20.04 LTS, the one that you can find on miscrosoft store.
I did the pip install amuse-galaxia --no-clean -v and it gave me the folliwing error:
.
.
.
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-install-p4iw7qvg/amuse-galaxia/support/setup_codes.py", line 1093, in run
raise Exception("No succesful builds detected. Aborting.")
Exception: No succesful builds detected. Aborting.
Building wheel for amuse-galaxia (PEP 517) ... error
ERROR: Failed building wheel for amuse-galaxia
Failed to build amuse-galaxia
ERROR: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Exception information:
Traceback (most recent call last):
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 228, in _main
status = self.run(options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 182, in wrapper
return func(self, options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/commands/install.py", line 364, in run
raise InstallationError(
pip._internal.exceptions.InstallationError: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Removed build tracker: '/tmp/pip-req-tracker-k8yvag7h'

Update, now everytime I try using 'pip install amuse' the console send me this:
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f26c74b6e80>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f26c74dc070>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f26c74dc1c0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f26c74dc310>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f26c74dc430>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse/
ERROR: Could not find a version that satisfies the requirement amuse (from versions: none)
ERROR: No matching distribution found for amuse

this last error seems to indicate a problem with your network connection and/or pip ..for the previous error: can you check at the beginning of the output after the pip install amuse-galaxia --no-clean -v, where it reports the temporary build directory (some /tmp/... dir)? Somewhere in the that directory (or one of it subdirectories) ther will be a build.log file. Probably there will be some information on what went wrong for the compile in there....

I get this message:
(Amuse-env) seba@DESKTOP-M1MRTA0:~$ pip install amuse-galaxia --no-clean -v
Using pip 20.2.3 from /home/seba/Amuse-env/lib/python3.8/site-packages/pip (python 3.8)
Non-user install because user site-packages disabled
Created temporary directory: /tmp/pip-ephem-wheel-cache-cgca8tzh
Created temporary directory: /tmp/pip-req-tracker-ktkzsb5r
Initialized build tracking at /tmp/pip-req-tracker-ktkzsb5r
Created build tracker: /tmp/pip-req-tracker-ktkzsb5r
Entered build tracker: /tmp/pip-req-tracker-ktkzsb5r
Created temporary directory: /tmp/pip-install-h3jgiwhu
1 location(s) to search for versions of amuse-galaxia:

https://pypi.org/simple/amuse-galaxia/
Fetching project page and analyzing links: https://pypi.org/simple/amuse-galaxia/
Getting page https://pypi.org/simple/amuse-galaxia/
Found index url https://pypi.org/simple
Looking up "https://pypi.org/simple/amuse-galaxia/" in the cache
Request header has "max_age" as 0, cache bypassed
Starting new HTTPS connection (1): pypi.org:443
Incremented Retry for (url='/simple/amuse-galaxia/'): Retry(total=4, connect=None, read=None, redirect=None, status=None)
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f09076f9f10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse-galaxia/
Starting new HTTPS connection (2): pypi.org:443
Incremented Retry for (url='/simple/amuse-galaxia/'): Retry(total=3, connect=None, read=None, redirect=None, status=None)
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f09076f9c10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse-galaxia/
Starting new HTTPS connection (3): pypi.org:443
Incremented Retry for (url='/simple/amuse-galaxia/'): Retry(total=2, connect=None, read=None, redirect=None, status=None)
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f09076f9ca0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse-galaxia/
Starting new HTTPS connection (4): pypi.org:443
Incremented Retry for (url='/simple/amuse-galaxia/'): Retry(total=1, connect=None, read=None, redirect=None, status=None)
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f0907610160>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse-galaxia/
Starting new HTTPS connection (5): pypi.org:443
Incremented Retry for (url='/simple/amuse-galaxia/'): Retry(total=0, connect=None, read=None, redirect=None, status=None)
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f09076102b0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/amuse-galaxia/
Starting new HTTPS connection (6): pypi.org:443
Could not fetch URL https://pypi.org/simple/amuse-galaxia/: connection error: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/amuse-galaxia/ (Caused by NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f0907610400>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) - skipping
Given no hashes to check 0 links for project 'amuse-galaxia': discarding no candidates
ERROR: Could not find a version that satisfies the requirement amuse-galaxia (from versions: none)
ERROR: No matching distribution found for amuse-galaxia
Exception information:
Traceback (most recent call last):
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 228, in _main
status = self.run(options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 182, in wrapper
return func(self, options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/commands/install.py", line 323, in run
requirement_set = resolver.resolve(
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/resolution/legacy/resolver.py", line 183, in resolve
discovered_reqs.extend(self._resolve_one(requirement_set, req))
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/resolution/legacy/resolver.py", line 388, in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/resolution/legacy/resolver.py", line 339, in _get_abstract_dist_for
self._populate_link(req)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/resolution/legacy/resolver.py", line 305, in _populate_link
req.link = self._find_requirement_link(req)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/resolution/legacy/resolver.py", line 270, in _find_requirement_link
best_candidate = self.finder.find_requirement(req, upgrade)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/index/package_finder.py", line 926, in find_requirement
raise DistributionNotFound(
pip._internal.exceptions.DistributionNotFound: No matching distribution found for amuse-galaxia
Removed build tracker: '/tmp/pip-req-tracker-ktkzsb5r'

can you install other packages (e.g. numpy or some other often used one..)?

Ok so, in the current virtualenv (Amuse-env) i tried 'pip install pip-install-test' and i got the same message:
(Amuse-env) seba@DESKTOP-M1MRTA0:~$ pip install pip-install-test
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f21f55c0fd0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f21f55f7040>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f21f55f7190>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f21f55f72e0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f21f55f7430>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
ERROR: Could not find a version that satisfies the requirement pip-install-test (from versions: none)
ERROR: No matching distribution found for pip-install-test
Now im going to try it on a clean virtualenv

same result in a clean virtualenv:
(test-env) seba@DESKTOP-M1MRTA0:~$ pip install pip-install-test
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9025b32640>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9025b32d90>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9025b32c70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9025b32580>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9025b32850>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/pip-install-test/
ERROR: Could not find a version that satisfies the requirement pip-install-test (from versions: none)
ERROR: No matching distribution found for pip-install-test

So i closes my venv for a while, opened it again and try testing pip, it workd, then tried with 'pip install amuse-galaxia --no-clean -v' and sent me a very very very long code with lots of 'Skipping link' and the following error:
Exception: No succesful builds detected. Aborting.
Building wheel for amuse-galaxia (PEP 517) ... error
ERROR: Failed building wheel for amuse-galaxia
Failed to build amuse-galaxia
ERROR: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Exception information:
Traceback (most recent call last):
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 228, in _main
status = self.run(options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 182, in wrapper
return func(self, options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/commands/install.py", line 364, in run
raise InstallationError(
pip._internal.exceptions.InstallationError: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Removed build tracker: '/tmp/pip-req-tracker-d2zyroo6'

yea, pip can give a lot of superfluous output on all the dependencies and all the package version it is not using...but the important bit is in the beginning: like the "Created temporary directory: /tmp/pip-install-h3jgiwhu" you had above.. the directory mentioned here (different for each build) should contain a build.log file (if it doesn't its failing before it tries to compile..)

Oh ok, so should i look for build.log in every temporary directory that is created in the code?

Here is the amuse-galaxia tmp part:
Building wheels for collected packages: amuse-galaxia
Created temporary directory: /tmp/pip-wheel-8hlld5uv
Destination directory: /tmp/pip-wheel-8hlld5uv
Running command /home/seba/Amuse-env/bin/python3 /home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmps2z82_dz
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/amuse
creating build/lib/amuse/community
creating build/lib/amuse/community/galaxia
copying src/amuse/community/galaxia/interface.py -> build/lib/amuse/community/galaxia
copying src/amuse/community/galaxia/init.py -> build/lib/amuse/community/galaxia
running build_codes
building libraries and community codes
build, for logging, see 'build.log'
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/codes
creating build/temp.linux-x86_64-3.8/codes/galaxia
copying src/amuse/community/galaxia/interface.py -> build/temp.linux-x86_64-3.8/codes/galaxia
copying src/amuse/community/galaxia/interface.f90 -> build/temp.linux-x86_64-3.8/codes/galaxia
copying src/amuse/community/galaxia/Makefile -> build/temp.linux-x86_64-3.8/codes/galaxia
copying src/amuse/community/galaxia/init.py -> build/temp.linux-x86_64-3.8/codes/galaxia
[14:38:50] building galaxia
will copy worker: src/amuse/community/galaxia
galaxia
Community codes not built (because of errors):

galaxia
================================================================================
0 out of 1 codes built, 0 out of 0 libraries built
Traceback (most recent call last):
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in
main()
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 204, in build_wheel
return _build_backend().build_wheel(wheel_directory, config_settings,
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 216, in build_wheel
return self._build_with_temp_dir(['bdist_wheel'], '.whl',
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 202, in _build_with_temp_dir
self.run_setup()
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 253, in run_setup
super(_BuildMetaLegacyBackend,
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 145, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 36, in
setup(
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-build-env-oxlm6iej/overlay/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 290, in run
self.run_command('build')
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3.8/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-install-jiozgqsj/amuse-galaxia/support/setup_codes.py", line 1093, in run
raise Exception("No succesful builds detected. Aborting.")
Exception: No succesful builds detected. Aborting.
Building wheel for amuse-galaxia (PEP 517) ... error
ERROR: Failed building wheel for amuse-galaxia
Failed to build amuse-galaxia
ERROR: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Exception information:
Traceback (most recent call last):
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 228, in _main
status = self.run(options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 182, in wrapper
return func(self, options, args)
File "/home/seba/Amuse-env/lib/python3.8/site-packages/pip/_internal/commands/install.py", line 364, in run
raise InstallationError(
pip._internal.exceptions.InstallationError: Could not build wheels for amuse-galaxia which use PEP 517 and cannot be installed directly
Removed build tracker: '/tmp/pip-req-tracker-572w8u3m'

so in either /tmp/pip-wheel-8hlld5uv or /tmp/tmps2z82_dz (not sure) there will be a build.log..

Ok, so i have to make sure that those tmp's have their building logs?

sorry about my questions but im not sure what to do

my bad! I didn't actually mention it above, but could you post the build.log here? btw, I have tried it myself and for me the build.log ended up in some /tmp/pip-install-..  directory (I had to search for it, it helps to check the file dates..)..one thing that I see that could go wrong is the installation of blas and lapack libs though..

Hi I don't know if I should open up my own issue, or comment here. So please let me know.
I think I'm having the same issue as SAguilar2000. Namely this error about PEP 517.
The first package that fails for me when I run
pip install amuse
is amuse-athena
so I've attached the log that's produced when running
pip install amuse-athena --no-clean -v
Any advice would be much appreciated.
log.txt

I am seeing much the same problem - but on my Mac (Catalina, 10.15.6).
I have followed all the installation steps (except I use python3.8 from anaconda rather than brew). I have a separate virtualenv and everything works well until pip install amuse. This command works for some frameworks (amuse-gadget2 at least) but fails for most.
The build.log file is however different in different cases. When I try to install amuse-galaxia I get:
more ./pip-install-puri6z75/amuse-galaxia/build.log

Building libraries and codes

Building code: galaxia, target: all, in directory: build/temp.macosx-10.9-x86_64-3.8/codes/galaxia

make: Entering directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-puri6z75/amuse-galaxia/build/temp.macosx-10.9-x86_64-3.8/codes/galaxia'
amusifier --type=f90 interface.py  BarAndSpiralsInterface -o worker_code.f90
x86_64-apple-darwin13.4.0-gfortran -c -g -O2 -fPIC -llapack -lblas -o interface.o interface.f90
mpif90 -g -O2 -fPIC -I/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-build-env-pkl0xefk/overlay/share/amuse/lib/forsockets worker_code.f90 interface.o -o GalaxyModel_worker  -L/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-build-env-pkl0xefk/overlay/share/amuse/lib/forsockets -lforsockets -llapack -lblas
worker_code.f90:130.8:
USE mpi
    1

Fatal Error: File 'mpi.mod' opened at (1) is not a GNU Fortran module file
make: *** [Makefile:28: GalaxyModel_worker] Error 1
make: Leaving directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-puri6z75/amuse-galaxia/build/temp.macosx-10.9-x86_64-3.8/codes/galaxia'

Building finished

while when trying to build amuse-smalln I get
more ./pip-install-m17mh2qe/amuse-smalln/build.log

Building libraries and codes

Building code: smalln, target: all, in directory: build/temp.macosx-10.9-x86_64-3.8/codes/smalln

make: Entering directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-m17mh2qe/amuse-smalln/build/temp.macosx-10.9-x86_64-3.8/codes/smalln'
amusifier --type=c interface.py SmallNInterface -o worker_code.cc
amusifier --type=h interface.py -i amuse.support.codes.stopping_conditions.StoppingConditionInterface  SmallNInterface -o interface.h
make -C src all CXX='mpicxx'
make[1]: Entering directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-m17mh2qe/amuse-smalln/build/temp.macosx-10.9-x86_64-3.8/codes/smalln/src'
mpicxx -g -O2 -fPIC -Wall -g -I/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-build-env-o78a6odx/overlay/share/amuse/lib/stopcond -Isrc -g -Wall -I/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-build-env-o78a6odx/overlay/share/amuse/lib/stopcond -c smallN.cc -o smallN-lib.o
In file included from smallN.cc:68:
In file included from ./hdyn.h:9:
In file included from ./stdinc.h:10:
In file included from /Users/jarle/anaconda3/bin/../include/c++/v1/iostream:38:
In file included from /Users/jarle/anaconda3/bin/../include/c++/v1/ios:215:
In file included from /Users/jarle/anaconda3/bin/../include/c++/v1/iosfwd:90:
/Users/jarle/anaconda3/bin/../include/c++/v1/wchar.h:119:15: fatal error: 'wchar.h' file not found
#include_next <wchar.h>
^~~~~~~~~
1 error generated.
make[1]: *** [Makefile:48: smallN-lib.o] Error 1
make[1]: Leaving directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-m17mh2qe/amuse-smalln/build/temp.macosx-10.9-x86_64-3.8/codes/smalln/src'
make: *** [Makefile:35: src/libsmallN.a] Error 2
make: Leaving directory '/private/var/folders/bj/l10yvm9m8xlgl2006s6gv0k00000gn/T/pip-install-m17mh2qe/amuse-smalln/build/temp.macosx-10.9-x86_64-3.8/codes/smalln'

Building finished

@cheekyparticle can you attach the build.log file? (not the log output of the pip command) Its explained above where to find it...

@jbrinchmann I think you have to check the compiler configurations: the first error (amuse-galaxia) seems to indicate mpi.mod  (and hence MPI) is compiled with a different (incompatible) fortran compiler than the one you are using right now (ie the mpif90 finds mpi.mod compiled by a different compiler)...
the error for smalln also points to a weird compiler config error (c++ included file tries to include file which does not exist. The athena error also points to a serious compiler configuration error (the mpicc not being able to compile a simple test script..

Thank you @ipelupessy - I'll have a look - I agree it looks very much like this is the problem.
I should not though, that I strictly followed the installation instructions & activation instructions on https://amusecode.github.io/installation so this might if so point to some oddity in the latest Catalina version.

Thanks @ipelupessy, my apologies!
build.log

@cheekyparticle no problem - you can see in the build log that the mpicxx command (which wraps the c++ compiler) is not finding the c++ compiler it depends on - this indicates some installation issue for mpi - apparently its installed with conda, so I would check the conda packages (maybe you need to update the conda mpi packages)..

@jbrinchmann yea, @rieder has more experience with mac so maybe he can comment on this issue?

@ipelupessy  thanks for your advice. Indeed I updated my mpi through anaconda and came up against some other issues with where lapack and blas were. I resolved to install through anaconda to see if that would change anything.
Interestingly amuse-galaxia seems to successfully install.
buildgalaxia.log
but amuse as a whole doesn't. I checked with amuse-athena too and that fails also.
buildathana.log

ok, amuse as a whole will fail if any of the sub packages fails...its still the mpicxx problem; mpicc is working, can you check whether there is something different about mpicxx compared to mpicc? (what does which mpicxx report vs which mpicc, same for mpicc --version)

@cheekyparticle in addition, one thing to make sure after updating your environment when using pip is to make sure there are no old cached packages used (--no-cache-dir option, and maybe just deleting the pip cache dir, location of which depends on your system);

btw, conda might need an additional package for mpicxx, e.g. openmpi-mpicxx - is that installed?)

Thanks for all the work! It turns out I did need to update openmpi-mpicxx on anaconda as well.
after which mpicc
/home/andrew/anaconda3/bin/mpicc
and after mpicc --version
x86_64-conda_cos6-linux-gnu-cc (crosstool-NG <IP_ADDRESS>9-a04d0) 7.3.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Now the errors have changed somewhat, at first I thought athena was no longer a problem but I think it is.
buildathena.log

hmm, the "/usr/include/stdlib.h:25:10: fatal error: bits/libc-header-start.h: No such file or directory
#include <bits/libc-header-start.h>" bit seems to indicate you are missing some development headers (either c or c++)

@ipelupessy, it seems that was the error, I decided to get off anaconda and perform the installation instructions again and it worked. I'm not sure if this was the same problem as the original poster.
Thanks so much!

close as solved


Suggested HUD refactor and input routing fix

These commits contain a suggested refactor (feel free to ignore or partially apply) and a fix for the structure of the input tree. See commit messages for details. You're welcome to take part of these changes and incorporate them however you want, rather than merging this PR directly. I release these changes into the public domain under the terms of the UNLICENSE.

This looks good. Thanks a lot for your help, I really appreciate as always ;).


Text changes to the Spec, also try to have 1 sentence per line.

Signed-off-by: Heiko W. Rupp<EMAIL_ADDRESS>@Steve-Fontes @pavolloffay

+1 LGTM


Feature request: KMS encryption of boot volume

It was added in the AWS CFN templates: https://github.com/awslabs/amazon-eks-ami/pull/33/files

I no longer need this so will close.


Unexpected behavior that can corrupt application data

https://github.com/vasa-c/go-db/blob/c65eecde33df27be9252999e74021886710e0ddb/goDB/Helpers/Templater.php#L474
I just had following situation:

Prepared query like that UPDATE ?t:tableName SET ?s:setValues WHERE ?w:whereCondition
Gave data for placeholders:
'tableName' => 'manager',
'setValues' => ['companyId' => '61eaf81b8a5b11e39ba6c436c32fa3a3'],
'whereCondition' => 'id = ?:id',
'id' => '61eaf81b8a5b11e39ba6c436c32fa3a3'

I expected that templater will replace all placeholders recursivly, but it not happend.
Okey, its my fault, i was not attentive when read documentation. But, more interesting what query i got: UPDATE manager SET companyId="61eaf81b8a5b11e39ba6c436c32fa3a3" WHERE 1=1
It means if you will give something that is not array or FALSE in ?w-placeholder you will update ENTIRE TABLE. Code will not abort with exception, it silently will corrupt your data.

@teso Sorry to hear that, I hope you could recover your data.
I agree, the WHERE placeholder should be more picky about the type of data provided to it.
The problem here is that if we start throwing exceptions on everything except, lets say, boolean or array, we might break backwards compatibility.
@vasa-c What do you think? Throwing an exception, at least for a string, sounds reasonable, to prevent thoses kind of mistakes.
I hope no one really uses strings there.

@mkedo Fortunately, it happend on the dev environment (but i have no dump for restoring).
We can left this ability only for SELECT queries (for backwards compatibility) and throw exceptions for other cases (if something except array will be given).


vectorize fails with boolean outputs with return after a for loop containing a function call

The following example:
from numba import vectorize
import numpy as np

def g(p):
    return p*2

@vectorize(['bool_(uint64)'])
def f(n):
    for j in range(n):
        a1 = g(j)
    return True

integers = np.arange(10, dtype=np.uint64)
print(f(integers))

Results in the following traceback:
Traceback (most recent call last):
  File "b.py", line 7, in <module>
    @vectorize(['bool_(uint64)'])
  File "/home/gmarkall/work/numba/numba/npyufunc/decorators.py", line 69, in wrap
    return vec.build_ufunc()
  File "/home/gmarkall/work/numba/numba/npyufunc/ufuncbuilder.py", line 114, in build_ufunc
    dtypenums, ptr, keepalive = self.build(cres, sig)
  File "/home/gmarkall/work/numba/numba/npyufunc/ufuncbuilder.py", line 149, in build
    cres.objectmode, envptr)
  File "/home/gmarkall/work/numba/numba/npyufunc/wrappers.py", line 175, in build_ufunc_wrapper
    pyapi, env)
  File "/home/gmarkall/work/numba/numba/npyufunc/wrappers.py", line 96, in build_obj_loop_body
    signature, env)
  File "/home/gmarkall/work/numba/numba/npyufunc/wrappers.py", line 51, in _build_ufunc_loop_body_objmode
    store(retval)
  File "/home/gmarkall/work/numba/numba/npyufunc/wrappers.py", line 92, in store
    out.store_direct(retval, builder.load(store_offset))
  File "/home/gmarkall/work/numba/numba/npyufunc/wrappers.py", line 262, in store_direct
    assert ptr.type.pointee == value.type
AssertionError

Performing a more simple assignment in the for loop body (e.g. a1 = 1) does not appear to have the same effect.
Note: An issue with vectorize and boolean outputs was already noted and fixed in #610.

This now works correctly.


Moving average weight parameter

A question regarding the following code in linear_block.py in the method update_cov:
        ....
        self._activations_cov.add_to_average(activation_cov, cov_ema_decay)
        self._sensitivities_cov.add_to_average(sensitivity_cov, cov_ema_decay)

The method add_to_average(self, value: torch.Tensor, decay: float = 1.0, weight: float = 1.0) takes a weight as parameter.
Shouldn't be the weight set to 1- cov_ema_decay such that the overall sum of decay and weight is 1.0?
This is done in that way in other implementations, like here: https://github.com/lzhangbv/kfac_pytorch/blob/master/kfac/utils.py#L66 or here https://github.com/Thrandis/EKFAC-pytorch/blob/master/kfac.py#L174 (here cov_ema_decay corresponds to alpha).

I use an implementation of the exponential moving average that is not prone to the initialization problem. Typically, the very first value disproportionately impacts the overall performance. This is not the case in my implementation. The weight here is different than in the implementations you linked. My is similar to the official TB kfac implementation https://github.com/tensorflow/kfac


Hashtags that include numbers don't always work?

Yay for hashtags on Bluesky! I've noticed they don't always work, however.
Example: #3tofollow
My first post in this thread using the hashtag DID have a working/clickable hashtag:
https://bsky.app/profile/debbieohi.com/post/3kmlhbzcyg62j
Further down in the thread, however, you'll see that the hashtag stops working (isn't clickable).
Also, I've noticed if I do click on the hashtag from the first post, it does NOT show all posts on Bluesky with that hashtag.
As proof, see the custom feed I created via Skyfeed to show #3tofollow posts:
https://bsky.app/profile/did:plc:5amsebbtpuqieuxuqadmmvcv/feed/aaaez5gf22o2e
One user helped me test this and concluded that having a number in the post is the problem:
https://bsky.app/profile/thebarbarienne.bsky.social/post/3kmliwe5so52a
(but this doesn't explain why my first post DOES have a clickable #3tofollow hashtag).

Debbie

And here's a screenshot showing an example of a reply to the thread shown above.
#3tofollow hashtag IS clickable in the first post, but not in replies.

I tried to click this hashtag earlier and it didn’t work for me, either.

Fixed by https://github.com/bluesky-social/social-app/pull/3055
It should be following Twitter's hashtags in the next app update: A hashtag cannot be just numbers, but can start, end, or contain numbers.


Remove channel usages - getByteChannel(), ... etc

$subject according to the https://docs.google.com/spreadsheets/d/18Yg9LsOk3YJ60-hbLK4u_YawjVgXsJuLXxGjAC7SRko/edit#gid=1104991983
subtask of #576

FIxed by https://github.com/ballerina-platform/module-ballerina-mime/pull/46 and https://github.com/ballerina-platform/module-ballerina-http/pull/181

FIxed by https://github.com/ballerina-platform/module-ballerina-mime/pull/46 and https://github.com/ballerina-platform/module-ballerina-http/pull/181


import methods from datasets + refactor

Add what was defined in datasets. Will remove it there once we merge here.
A tiny breaking refactor to factor the logged in state and factor out the request handling

Closing as breaking change is not acceptable for dependencies (transformers & datasets) and moving endpoints from datasets is out of scope for this project, which is limited to repo interactions.


Create Alertmanager Makefile

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.

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

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna]

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

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

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna]

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

/meow

/meow

@abhay-krishna:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@abhay-krishna:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


new feature: add privacy-router for sf-lr-mix

Type of change

[ ] Add new papers (Please tell us why you think this paper is awesome!)
[ ] Fix the category of an existing paper/papers (Please tell us the reasons)
[x] Add a new tool/primitive/application with a new markdown page (Thank you! Also, please tell us more about this awesome thing!)

Description

Please include a summary of the change and the relevant motivation.
Supply a new component "Privacy-Router" for enabling mutual conversion between homomorphically encrypted data and secret-shared data.

CLA 签署信息 https://github.com/secretflow/secretflow/pull/753


Feature: Arduino support

What version of nebula are you using?
1.4.0
What operating system are you using?
linux
Describe the Bug
Do you think it is possible to write a client for arduino? This would enable a whole new way to communicate with IOT devices. The data that will be transmitted is very low bandwith. What do you think? Perhaps we can partner with the ESPHome project for implementation.
Oliver
Logs from affected hosts
No response
Config files from affected hosts
No response

why not try compiling the binary w/ https://blog.arduino.cc/2019/08/23/tinygo-on-arduino/ tinygo?
what's stopping you from running it today, a lack of an OS?


Include release asset for v1.22.0

Can the nupkg release package be included for v1.22.0 in the same way that it was for previous versions?
Thanks!

Yes, can do. You can download it from PowerShell Gallery as well but happy to keep it this way if it's helpful to have on release as well

Yes please. We prefer install the package directly from the latest GH release, so having it there is essential

@TylerJang27 nupkg now uploaded to release: https://github.com/PowerShell/PSScriptAnalyzer/releases/tag/1.22.0


Add server slow start feature

add server upstream slow start feature which has been already implemented by nginx plus:
http://nginx.com/products/application-health-checks/

slow_start=time
sets the time during which the server will recover its weight from zero to a nominal value.

个人理解官方的效果是在设定时间内，从0逐步增加到所配置的权重。
在最普通的情况下，peer->weight = 1，代码上看 peer->effective_weight的值在设定时间内就一直在0和1间徘徊，虽然比设定的权重低，但也是一个固定权重， 没有逐步提升的效果。不知道是否有更好的方案？

 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.

 All committers have signed the CLA.


Video Prevew not working

Video preview not working in demo too
https://collab-project.github.io/videojs-record/examples/audio-video.html
Just record a video and try to preview

Lol, the problem is in
https://webrtc.github.io/adapter/adapter-latest.js
the file not working.

lol? I'm also seeing the warning below, I'll take a look.

i downloaded this version for adapter.js and now working  fine
https://codeload.github.com/webrtc/adapter/zip/master

@bobyper can you try with https://unpkg.com/webrtc-adapter/out/adapter.js?

working fine with https://unpkg.com/webrtc-adapter/out/adapter.js

Cool, updated the examples with that URL.


Third batch of updating sql tests to use assert_batches_eq

Which issue does this PR close?

Continued work on #743 task 2.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Thank you @matthewmturner  -- I think the reason this is failing is that the github executors have 2 cores, but your machine had 8, but the physical explain plans depend on the number of cores. I'll fix up the tests (as I have a vested interest in pushing this project along)

@alamb noted, thanks!
it might be a silly question, but would you be able to provide color on why the physical explain plan depend on the number of cores?

it might be a silly question, but would you be able to provide color on why the physical explain plan depend on the number of cores?

It is not silly at all @matthewmturner  -- the core reason is that the target concurrency defaults to the number of cores -- so when DataFusion goes through the exercise is splitting the input into several output datastreams (partitons), it tries to make just enough output streams to keep all the cores busy.


Support http proxy

Hi team,
Thanks for your contribution in this project and it is really useful.
Would it be possible to add a new feature, configuring http proxy in UI on Mac or IOS client?
Some RSS feeds are not reachable directly. It would be convenient to access them via proxy for NetNewsWire instead of OS system proxy.

Duplicate of #478


[DOC] Migration guide link for Updating WSO2 Products redirects to non existing page

Doc:
[1] https://docs.wso2.com/display/IS570/Upgrading+From+an+Older+Version+of+WSO2+IS#UpgradingFromanOlderVersionofWSO2IS-Migratingthedata
[2] https://docs.wso2.com/display/IS570/Upgrading+from+the+Previous+Release

Link Updating WSO2 Products doesnt exists. It should be https://docs.wso2.com/display/updates/Using+WSO2+Update+Manager

Fixed from IS-5.2.0 to IS-5.8.0
[1] https://docs.wso2.com/display/IS580/Upgrading+from+the+Previous+Release


Make Survival Analysis Estimators consistent, and pass all required arguments

Description of feature

consistency
E.g. tl.kmf operates on two arrays (see also #387) while tl.nelson_aalen operates on an anndata.
The latter should be the norm here if suitable.
passing all required arguments
Then, e.g. tl.weibull doesnt take the entry column or any way to pass this to the fitter; harmonizing this to ensure all flexibility offered by lifelines is userfacing would be a great enhancement!

Can also make a suitable checkpoint list here together if it helps!

[ ] Update Readme in Notebooks to include an installation command for locally cloned repos
[ ] make method signatures uniform and kwargs
[ ] update notebook example using kmf
[ ] update documentation

Trying to gather a few more detailed points, some might already be ticked off :)

[ ] Remove kmf from the documentation, and raise deprecation warning when it is called anyways
[ ] Add kaplan_meier as the new fitter (consistent with how the other fitters of survival analysis)
[ ] Add new tests for kaplan_meier
[ ] Remove kmf usage throughout the docs:

[ ] plot_kmf (here, a consider simple renaming to plot_kaplan_meier?), update its examples
[ ] tutorials

Update Readme in Notebooks to include an installation command for locally cloned repos

@aGuyLearning if you're interested in adding this, feel free to do so in a new PR!


Episode upload failing in pupeteer with TypeError: text is not iterable

Hi,
I am getting the following error. I have setup the secrets under Organization=>Project=>Secrets.
upload.yml
    env:
      ANCHOR_EMAIL: ${{ secrets.ANCHOR_EMAIL }}
      ANCHOR_PASSWORD: ${{ secrets.ANCHOR_PASSWORD }}

Launching puppeteer
TypeError: text is not iterable
at Keyboard.type (/home/aru/git/youtube-to-anchorfm/node_modules/puppeteer/lib/cjs/puppeteer/common/Input.js:222:28)
at ElementHandle.type (/home/aru/git/youtube-to-anchorfm/node_modules/puppeteer/lib/cjs/puppeteer/common/JSHandle.js:522:35)
at process._tickCallback (internal/process/next_tick.js:68:7)
===================== DEBUG ===============
puppeteer:protocol:RECV ◀ {"id":20,"result":{"result":{"type":"object","subtype":"node","className":"HTMLInputElement","description":"input#email.styles__input___2RwvF","objectId":"-2447221228543748801.3.2"}},"sessionId":"1A64137E15A99E636F94C9926AC5BD94"} +2ms
puppeteer:protocol:SEND ► {"sessionId":"1A64137E15A99E636F94C9926AC5BD94","method":"Runtime.callFunctionOn","params":{"functionDeclaration":"(element) => element.focus()\n//# sourceURL=puppeteer_evaluation_script\n","executionContextId":3,"arguments":[{"objectId":"-2447221228543748801.3.2"}],"returnByValue":true,"awaitPromise":true,"userGesture":true},"id":21} +1ms
puppeteer:protocol:RECV ◀ {"id":21,"result":{"result":{"type":"undefined"}},"sessionId":"1A64137E15A99E636F94C9926AC5BD94"} +6ms
TypeError: text is not iterable
at Keyboard.type (/home/aru/git/youtube-to-anchorfm/node_modules/puppeteer/lib/cjs/puppeteer/common/Input.js:222:28)
at ElementHandle.type (/home/aru/git/youtube-to-anchorfm/node_modules/puppeteer/lib/cjs/puppeteer/common/JSHandle.js:522:35)
at process._tickCallback (internal/process/next_tick.js:68:7)
puppeteer:protocol:RECV ◀ {"method":"Network.requestWillBeSentExtraInfo","params":{"requestId":"146887.66","associatedCookies":[],"headers":{":method":"POST",":authority":"m.stripe.com",":scheme":"https",":path":"/6","content-length":"2572","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/88.0.4298.0 Safari/537.36","content-type":"text/plain;charset=UTF-8","accept":"/","origin":"https://m.stripe.network","sec-fetch-site":"cross-site","sec-fetch-mode":"cors","sec-fetch-dest":"empty","referer":"https://m.stripe.network/inner.html","accept-encoding":"gzip, deflate, br","accept-language":"en-US"}},"sessionId":"1A64137E15A99E636F94C9926AC5BD94"} +97ms

It's seems like there is not secrets.
Can you try to write down in the action.yml file the secrets as string? Then, try again
Thanks

Thank you for the response.
Following is the content from the action.yml. However, I am still getting the same error.
name: 'Upload Episode from YouTube To Anchor.Fm'
description: 'An automation tool to publish your podcast from youtube to anchor.fm'
branding:
icon: 'upload-cloud'
color: 'green'
runs:
using: "docker"
image: "Dockerfile"
on:
push:
paths:
- episode.json
branches: [master]
jobs:
upload_episode:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Upload Episode from YouTube To Anchor.Fm
uses<EMAIL_ADDRESS>env:
ANCHOR_EMAIL: "THE ACTUAL EMAIL for Anchor account"
ANCHOR_PASSWORD: "THE ACTUAL PASSWORD for Anchor account"
I also tried with following content in action.yml and got the same error.
    env:
      ANCHOR_EMAIL: ${{ secrets.ANCHOR_EMAIL }}
      ANCHOR_PASSWORD: ${{ secrets.ANCHOR_PASSWORD }}

I am able to run git commit and git push without password from the directory: ~/git/youtube-to-anchorfm
thanks.

Hi,
Thanks for sharing this great tool. This will save a lot of my time. Appreciate your help!!
thank you.

 Consider to share it to everyone and to drop a star :)


[FALSE-POSITIVE]

Domains or links
https://app.duel.network
More Information
I think the domain is incorrectly marked as Phishing on Phishtank.
Additional context
You can check https://duel.network website to understand what we do. https://app.duel.network is our app. There is no problem with our website actually. If there is something wrong, please let me know what it is. "Fraud Warning" message which prevents people from accessing the site appears on Opera browser. There is no problem with Chrome, Firefox and Safari.

@mitchellkrogza https://app.duel.network still shows "Fraud Warning" message and when I checked from PhishTank.org, I still see that it seems like "verified: is a pish". You can check with submission id #7282387. If there is a problem with website codes, please let me know. Otherwise could you remove from the database, please? Because some of our users still can't access with Opera browser and using an antivirus program also blocks the website. Thanks.


Automate release to npmjs when creating GH Release

It's a good opportunity to learn how to do this with a GH workflow. I'll take care of this ticket.

Done in #54


Added 8-digit hexadecimal and rgba color support

Added 8-digit hex color support to implement the functionality requested in #3.
Added bool argbHexColors OpAttributeSanitizerOptions parameter to indicate whether such colors are in #AARRGGBB format (true, default) as in Flutter, or in #RRGGBBAA as in HTML.
Also added rgba color support.

Closing this PR in favor of #16


feat(ratatui): add conversion to ratatui Color

Ratatui is an actively maintained fork of tui-rs. See https://ratatui.rs

hey, so sorry i missed this! i didn't have the repo watched so i didn't get any notifications for it. thanks for the submission, i'll publish a new minor version soon with this feature included.

No problem. Thanks for the merge.

published in 1.4.0