Converting GTF to ENSEMBL format

Hi,
I am currently working with non-model fish organisms and encountering an issue with your program. Every time I run it, I receive the message "Converting GTF to ENSEMBL format," but it doesn't generate any output containing gene lengths.
Does your program require the GTF files to have gene IDs in the ENSEMBL format to function correctly?
I successfully ran the demo file, so I'm confident the installation was done correctly.
Thanks!

The issue might be related to the chromosome names. Does the chromosome name in the GTF file you provided contain "chr"?


two-fer: Remove extraneous go files.

These files don't look like they serve a purpose since there is already a stub go file that is apparently used for this exercise.

Whoops, I didn't notice that at least one example solution was necessary. I'm still pretty sure the other file I removed wasn't necessary thought.

Ah, my bad I guess I kind of glossed over the comments in that file and assumed that this was just a leftover from some previous approach to organizing exercises. Thanks for the explanation!


Call-indirect caching: protect against out-of-bounds table index during prescan.

Call-indirect caching requires a "prescan" of a module's code section during compilation in order to know which tables are possibly written, and to count call-indirect callsites so that each separate function compilation can enable caching if possible and use the right slot range.
This prescan is not integrated with the usual validation logic (nor should it be, probably, for performance), so it's possible that an out-of-bounds table index or other illegal instruction could be present. We previously indexed into an internal data structure (table_plans) with this index, allowing for a compilation panic on certain invalid modules before validation would have caught it. This PR fixes that with a one-off check at the single point that we interpret a parameter (the table index) from an instruction during the prescan.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68614.
No test case because this requires compilation with non-default parameters, so the usual WAST assert_invalid form can't be used in a WAST test, and requires an invalid module, so a compilation disas test can't be used. Could build out either if desired but that seems like a much larger change.

Ah, right, that's the straightforward and obvious way to test this -- thanks! Added.


[Enhancement Request]: Migrating Cohere Model From API v1 to API v2

Feature/Enhancement Name
Migrating Cohere Model From API v1 to API v2
Enhancement Description
In the new release note of cohere model, they release version 2 of their python SDK and client.
Here is the link to it HERE
Motivation

Makes it easier and faster to build with Cohere.
V2 Chat: Message and chat history are combined in a single messages array
Staying up to date with cohere.
V2 Chat streaming: Uses server-sent events

Potential Solutions
How to Migrate form API v1 to API v2
The link above is a guide for migrating from the API v1 to API v2
Additional Context (optional)
No response
Affected Areas
None
Priority
Low

I am currently working on this

Migration completed


通过环境变量灵活配置 QuickLru 缓存的上限

Please help us to close this issue if everything is ok for you.

Close this issue due to no reply for 7+ days.


[AIRFLOW-1671] Add @apply_defaults back to gcs download operator

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1671

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:
This annotation seemed to have been removed from an PR1582 by accident, adding it back now.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

+1 LGTM
Going to wait for PR tests to pass.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2655   +/-   ##
=======================================
  Coverage   71.49%   71.49%
=======================================
  Files         153      153
  Lines       11746    11746
=======================================
  Hits         8398     8398
  Misses       3348     3348

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 3c3a65a...52b11b7. Read the comment docs.

+1 LGTM


how to apply SpatialDropout2D() in test time

I'm trying to get some kind of uncertainty measure of a CNN's output based on Gal & Ghahramani 2016. According to an other issue (#1606) it's easy to leave dropout on during test time, via:
model.add(Lambda(lambda x: K.dropout(x, level=0.5)))
I was wondering how to extend this to SpatialDropout2D() applied to the convolutional layers, since I get pretty bad results when I start to increase the dropout probability of the convolutional layers...? @fchollet
Would that make sense from the mathematical point of view? @yaringal

y = SpatialDropout2D(0.5)(x, training=True) will apply spatial dropout to x at both training and test time.


Reduce boilerplate using dependencies object

Adds an opt-in way to reduce the amount of boilerplate code needed to declare dependencies to Blindside, and to minimize the code changes needed to later add or remove dependencies for a class.
With Blindside as it is, adding a single dependency requires at least 7 changes, often more. With this PR, adding a dependency can take as little as 1 line of code.
This PR is backward compatible. Existing code using Blindside should be unaffected.
Here's how it works.  If a class called MyClass has some dependencies it needs injected, it encapsulates those dependencies in a simple NSObject subclass called MyClass_Dependencies (this naming convention is the default, but you can override it).
MyClass.m
#import "MyClass.h"
#import <Blindside/Blindside.h>

@interface MyClass_Dependencies : NSObject <BSDependencyProviding>

@property (strong) id<Protocol1> someDependency;
@property (strong) id<Protocol2> foo;
@property (strong) id<Protocol3> bar;

@end
@implementation MyClass_Dependencies @end
...

The protocol BSDependencyProviding has no requirements ... it's simply a flag indicating that this object is solely a bag of properties to inject into another object.  Because it conforms to this protocol, we know we can safely use the ObjC runtime to introspect this class and iterate over its properties, and use this info to provide a default implementation of +[NSObject bsProperties].  (That default implementation still returns nil if the object does not conform to BSDependencyProviding, preserving backward compatibility.)  In this way, Blindside provides the MyObject_Dependencies with all of its object instances through property injection with very little boilerplate.  Adding a dependency can be as simple as adding a @property... line, plus maybe an #import....
To get this populated MyClass_Dependencies object injected, MyClass conforms to another new protocol named BSDependencyInjectable.
MyClass.m ... continued from above:
...
@interface MyClass () <BSDependencyInjectable>

@property (strong) MyClass_Dependencies *dependencies;

@end

@implementation MyClass

- (instancetype)initWithDependencies:(id)dependencies
{
    if (self = [super init]) {
        _dependencies = dependencies;
    }

    return self;
}

- (void)exampleMethod
{
    id thing = [_dependencies.foo someThing];
    ...
}
...

Notice that adding a dependency to MyClass_Dependencies does not require any changes to MyClass.  We don't even need to implement +[NSObject bsInitializer], since the default implementation now returns a BSInitializer for the invariant initWithDependencies: method if the object conforms to BSDependencyInjectable:
@protocol BSInjectable

+ (Class)dependencyProvidingClass;
- (instancetype)initWithDependencies:(id<BSDependencyProviding>)dependencies;

@end

The default implementation of +[NSObject bsInitializer] needs to know the type of the argument, which it can get from [self dependencyProvidingClass].  There's even a default implementation of this method that uses the YourClassName_Dependencies naming convention, so if you follow that convention, you don't even need to implement that.
The only thing you have to implement is the initWithDependencies: method, which can't be avoided since we can't know what class you're subclassing, and thus what [super initWith...] method you need to call.
For many cases, the above code is all you need (plus defining your modules, of course).  Initial setup is easy, and adding or removing dependencies is fast and simple.
A note on BS_DYNAMIC:
Classes that need BS_DYNAMIC arguments in their initializers will require a custom +[NSObject bsInitializer] implementation that includes the dynamic arguments after the BSDependencyProviding object. Adding and removing dynamic arguments then becomes comparable to Blindside without this PR, but you still get the benefits mentioned above whenever adding or removing non-dynamic arguments.

Wow. This is really interesting! This PR certainly makes it easier to add dependencies, and I can imagine how that could be both good and bad, depending on how it was used in an application. It also reminds me of Spring's injector a bit (in a good way).
My personal feeling, re BS_DYNAMIC is that it should be dropped, since it tends to be misused a lot, allows a style of dynamic programming where you're never truly sure if your object will be able to be instantiated, is poorly documented, and rarely used. Blindside's providers, or late binding -configureWithThis:orThat: methods tend to be much more robust and easier to understand than that macro.
What I personally like the most about Blindside, vis a vis its +bsInitializer and provider patterns, is that it makes it easy to have a strong guarantee that your object will be instantiated with all the correct dependencies (or it will fail to compile). BS_DYNAMIC introduces a lack of type safety and uncertainty that usually leads to me regretting using it once I need to refactor. This PR seems to be inline with that value and style of programming, and so I feel pretty good about this.
Is the idea here that the MyClass_Dependencies object be something an injectable instance would hold onto? That seems like a bit of an a strange pattern in iOS, although I suppose you could immediately destructure it and store properties on the object you're instantiating. This also opens you up to more potential nil objects being injected accidentally, although I suppose individuals could take actions against that by marking each @property on their BSDependencyProviding as nonnull. That seems pretty good, but is one small pain point that I would be mindful of, if I was using this.
With all that said, I'm not sure I would ever use this feature myself, but I'm certainly not opposed to it either. It feels like a nice quality of life improvement to Blindside.
My only constructive feedback is that MyClass_Dependencies feels awkward because of the underscore. Are there any good reasons for keeping it? Since the class would need to implement the protocol as well, it seems safe enough to just omit that and go with MyClassDependencies.
Also, are the "Lumos additions" comments and pragma marks desired by your legal and/or engineering teams? I'm more than happy to credit y'all by name in the contributors section, but those comments may rub some folks the wrong way. It's very much against the spirit of "collective code ownership", for one, and fairly uncommon in OSS projects (in my limited experience, at least).

@akitchen @idoru @briancroom @wileykestner @cbguder @younata y'all have some very strong opinions on dependency injection and blindside. Any feedback to share with our friends from Lumos?

I strongly prefer code that is easy to read and reason about, even if that means more boilerplate. This is why I've preferred BSModules & the block syntax in my last few projects. I've seen @wileykestner take this a step further and not even use the auto-injected injector property, which basically means no runtime magic.
To me, it feels like this change is only valuable when everyone on the team is deeply familiar with Blindside and the Objective-C runtime. Maybe a fork would be more appropriate?
Another (lesser) concern is that this mechanism only seems to support injecting dependencies that can be identified by a class or a protocol, so the user would need to resort to other mechanisms to inject anything else (string constants, configured instances, etc.).


Could not find docile-1.1.5 in any of the sources

Hi!
I've a problem bundling this gem.
We are using Rails 5.1 with Ruby 2.3.1, when i bundle locally on my mac the gem installation gone successfully, but on the CI with command
bundle install --deployment --path vendor/bundle
produces this error on docile gem dependency:
Could not find docile-1.1.5 in any of the sources
Any thoughts?
Thank you!

Hi there,
no idea as docile is readily available on rubygems as 1.1.5.
So, I'd guess that you might be hitting one/few of the gotchas for bundler deployment mode
I.e. don't think anything we can do from here :)


full audit of the discord moderation group

As pool support for https://xdag.signal2noi.se
why have i been removed from the chat??
I would advise a full audit of the discord moderation group.
thank you for your time.
Rus

You were permanently banned, by me, after being unbanned at least twice from prior bans for the same reasons listed below, on May 20th 2018.
The #rules-info channel in Discord lists the following rules:
Rules
1.  No referral links.
2. No advertising.
3. No impersonation.
4. No personal information unless it is made publicly available by the person themselves.
5. Be respectful.
6. Post in the correct channel.
7. No punishment evasion.

The largest rule infracted was rule 5. As a community we are pretty open and tolerant. Your abuse of this rule was allowed to slip for some time. As the instigations, namecalling and outright disrespect were amplified, you were asked to stop. When you did not stop and began instigating in response to this question, you were banned, and then permanently banned when you came back and did the same thing.
It has come to my attention that you were on the server as an alt, violating rule 7, and were banned by moderator @mathsw.
For posterity, you had another rude message relayed to me by another member after this ban. I am not certain why you want to be a part of this community when these are the actions you take.
This audit has been completed, and this ticket will be closed.


Image prefix + Unit testing

Not ready

[x] Add sb_camera prefix to images.
[x] Unit test images.

:+1:

:thumbsup:


Fixing typo: 'Learnign' -> 'Learning'

Just noticed that when reading.
This is a really awesome project! Thanks for putting that together!

Haha I introduced that yesterday I think. OOPS. Thank you! And thanks for the thanks too


Incantations Not Picking Up

I can get the app the recognize my voice to awaken and activate, but it will not do anything for incantations. It just sits on the base attunement window. After opening the debug it confirmed that it is hearing me and recognizing the incants, but doesn't recognize the items I have in the belt.

I thought it was just mine cause I saw others using fireball, turns out they were memeing with a grass ball. I'm just blind. Looked at Discord, best of luck with fixing it.


Invalid type for Clouflare Worker url

Cloudflare Worker has type Output<string | undefined> which cannot be assigned (without type error) for example as envvar for static site:
const worker = new sst.cloudflare.Worker("Worker", {
  handler: "worker.ts",
});
new sst.cloudflare.StaticSite("Frontend", {
  ...
  environment: {
    VITE_WORKER_URL: worker.url, // => Type 'Output<string | undefined>' is not assignable to type 'Input<string>'.
  },
});

Problem seems to be here:
https://github.com/sst/ion/blob/7ac17cf1c35d2e9a977dd542f5cb8a256a330e7f/platform/src/components/cloudflare/worker.ts#L466-L470
where this code still returns Output<string | undefined>
this.workerUrl.url.apply((url) => (url ? `https://${url}` : url))

Not sure if asserting the type manually is the best solution, but works in my case:
public get url() {
  return this.workerDomain
    ? interpolate`https://${this.workerDomain.hostname}`
    : this.workerUrl.url.apply(
        (url) => (url ? `https://${url}` : url) as string,
      );
}

Workaround in sst.config.ts:
import { Output } from "@pulumi/pulumi";

const worker = new sst.cloudflare.Worker("Worker", {
  handler: "worker.ts",
});
new sst.cloudflare.StaticSite("Frontend", {
  ...
  environment: {
    VITE_WORKER_URL: worker.url as Output<string>
  },
});

yeah this is a bit annoying with Output - you can try worker.url.apply(val => val!) but your cast is fine too

@jakubknejzlik just checking if you managed to deploy the Cloudflare StaticSite successfully. this is probably user error on my part, but I keep getting the Error 1101 Worker threw exception, even on prod

@zxt-tzx last time i checked it worked fine, but i switched to cloudfront distribution (due to subdomains limitations on cloudflare)

I see. I can't get it to work hmm


Add Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore in NuGet Package Section

Code does in not compile in 'Add API Code' section as NuGet package
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore is missing in previous step. Please update the instructions.

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

ID: ab408035-6313-a183-9940-32de00e0e977
Version Independent ID: ab408035-6313-a183-9940-32de00e0e977
Content: Tutorial: Create a minimal web API with ASP.NET Core
Content Source: aspnetcore/tutorials/min-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hello @useready-andyv ... The instruction is already present (the last bullet point).
https://docs.microsoft.com/en-us/aspnet/core/tutorials/min-web-api?view=aspnetcore-6.0&tabs=visual-studio#add-nuget-packages

Oh! Did you mean for the Visual Studio for Mac tab?

Would suggest moving the last bullet up before selecting the project box for ease of use I missed it some others might miss the same thing too!
Pardon my typos, thumb typed on a handheld.

From: Luke Latham @.>
Sent: Sunday, August 14, 2022 5:21:17 PM
To: dotnet/AspNetCore.Docs @.>
Cc: Andy Vadul @.>; Mention @.>
Subject: Re: [dotnet/AspNetCore.Docs] Add Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore in NuGet Package Section (Issue #26737)
WARNING:"This email is originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe"
Hello @useready-andyvhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fuseready-andyv&data=05|01||c3c7747efe37408d092408da7e3aee94|8177f1d3e6504015b77a6825184034b7|0|0|637961088823061389|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=BNBS%2FIUkZFDBYm3xV%2Bh7IpyfFXfteOJ0x3mJ8huYxys%3D&reserved=0 ... The instruction is already present (the last bullet point).
https://docs.microsoft.com/en-us/aspnet/core/tutorials/min-web-api?view=aspnetcore-6.0&tabs=visual-studio#add-nuget-packageshttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Faspnet%2Fcore%2Ftutorials%2Fmin-web-api%3Fview%3Daspnetcore-6.0%26tabs%3Dvisual-studio%23add-nuget-packages&data=05|01||c3c7747efe37408d092408da7e3aee94|8177f1d3e6504015b77a6825184034b7|0|0|637961088823061389|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=nwHdDE2iLYVbGWC6mZLuYUF9vsubCjAggdqPdZkXtCM%3D&reserved=0
—
Reply to this email directly, view it on GitHubhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2FAspNetCore.Docs%2Fissues%2F26737%23issuecomment-1214451061&data=05|01||c3c7747efe37408d092408da7e3aee94|8177f1d3e6504015b77a6825184034b7|0|0|637961088823061389|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=yWhPJEEahcjBKC5BH9Wl3e8%2FuUs3StKmKFojbxVcay0%3D&reserved=0, or unsubscribehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD2EU66QXVEDABCKGWWLZG3VZFPM3ANCNFSM56QO7QZQ&data=05|01||c3c7747efe37408d092408da7e3aee94|8177f1d3e6504015b77a6825184034b7|0|0|637961088823061389|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=jLRH6T%2BqWErS5qrwY03X0KU86Pbpvp9EAi7kyt7Y%2B1A%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

I don't disagree and made the suggestion a while back. Let's leave this for @Rick-Anderson to take a look at. I was only closing it because I thought that we had it covered. There are two considerations ...

That package has been missed over the years by several devs.
The VS4Mac tab isn't claiming that it should be added, but I don't understand why. Seems like it should be there, too.

We'll look at this on the next update.

Oh! Did you mean for the Visual Studio for Mac tab?

The meta-data links contain the tab and the version when the issue is created.. No need to guess.


Getting "could not instantiate http://SymbolSource.Processing.Tools .PdbSourceExtractor" when trying to publish Symbolsource

Run the nuget push as follows:
nuget push Microsoft.AspNet.OData.5.6.0-rc.symbols.nupkg -source http://nuget.gw.symbolsource.org/Public/NuGet -apiKey XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX
get the follows error:
Failed to process request. 'Package submission failed: Server was unable to process request. ---> ComponentActivator: could not instantiate SymbolSource.Processing.Tools.PdbSourceExtractor ---> Exception has been thrown by the target of aninvocation. ---> Value cannot be null. Parameter name: path1. See http://www.symbolsource.org/Public/Home/Help for possible reasons. Fiddler may help diagnosing this error if your client discards attached detailed information.'.
The remote server returned an error: (506) Package submission failed: Server was unable to process request. ---> ComponentActivator: could not instantiate SymbolSource.Processing.Tools.PdbSourceExtractor ---> Exception has been thrown by the target of an invocation. ---> Value cannot be null. Parameter name: path1. See http://www.symbolsource.org/Public/Home/Help for possible reasons. Fiddler may help diagnosing this error if your client discards attached detailed information
...

We do not own symbol source. Please contact those fellas


test uri behavior on travis

DO NOT MERGE

(Triaging) Hi, @ixti! Is this still a relevant Issue to keep open?

Mm. Thanks for reminder. Will check out today.

Honesly I forgot what was the issue in fact. It works now locally for me... Not sure if behavior is what we desire, but it should be opened (if needed) as an issue:
HTTP::URI.parse("http://example.com:0000").port # => 80
URI.parse("http://example.com:0000").port # => 0


feat: rename 'token' to 'ercContract' in framework

Note
We are renaming 'token' to 'ercContract' as the word 'token' might not be appropriate when it is
not using for ERC20 tokens on PlasmaFramework.
closes issue: https://github.com/omisego/plasma-contracts/issues/273
(PS. if anyone has better naming idea please let me know)

(PS. if anyone has better naming idea please let me know)

I don't, but ercContract is bothering me too :(. I was thinking currency - which is what we use interchangeably (sigh) in code. Maybe a native English speaker could weigh in on how bad it sounds in the context of an ERC721 contract.
But please, consider keeping it to "Token", c.f. https://etherscan.io/token/0x06012c8cf97bead5deae237070f9587f8e7a266d and https://etherscan.io/tokens-nft
they're both using "token" in the context of the ERC721 contract, and "tokenID" for individual items. I think it is perfectly acceptable even if not strictly correct.
BTW, Is there input from anyone who actually was confused by use of the term "token" or are we just future proofing here?

BTW, Is there input from anyone who actually was confused by use of the term "token" or are we just future proofing here?

Just future proofing I guess.

But please, consider keeping it to "Token", c.f. https://etherscan.io/token/0x06012c8cf97bead5deae237070f9587f8e7a266d and https://etherscan.io/tokens-nft

Oh nice, I was keep wondering how people handle ERC721 contract. I wasn't able to find the word from the ERC implementation.
If they are others using token, then sure I don't have strong opinion. I think something from @paulperegud 's recent writing might be a good one: token_contract_address so we don't confuse with what it really means. How do you think @pdobacz ?
Btw, this issue/PR is only targeting the renaming on framework layer as token still makes perfect sense to the PaymentTx and it's clear and simple enough there so I am not proposing to change that. It is just on the framework layer it would be confusing as it is really the ERC contract address and the reason of having that in framework is really just to isolate the exit queue for external contracts.

token_contract_address is quite long and still can be just as confusing, if someone isn't fully aware of how ERC721 is constructed ("since it's called token_contract_address, do individual items have their contract addresses, huh?")
I don't have a strong opinion either, but the pragmatic side of things is:

let's be lax on this
let's be good to ourselves and avoid long names for things (we'll probably still be saying "token" in our conversations...)
let's not change stuff that settled in, if there's no strong reasons to do so ;)
etherscan is kinda source of truth and strong reference, consistency with that will help.

But no strong opinion here too, in the end. Maybe let's not bikeshed and just toss a coin :)

okay, in general I am convinced that token might be able to be enough for a good enough while. Though personally I do hope to make it something like tokenContract at least so we'd know it's really talking about the external contract from framework's point of view.
btw, I haven't dig into this deep yet but there do is sth like this: https://blog.enjincoin.io/erc-1155-the-final-token-standard-on-ethereum-a83fce9f5714 which has multiple token protocol under one contract (ouch....). Anyway, we might never tough that anyway XD

close this in flavor of #285 and stick with name token.


Added dovel.email to email software

Thanks for this awesome list.

Hi @blmayer,
Thank you for contributing but this awesome list is geared towards projects with more traction. I haven't been able to reach the dovel site for a while now.

Did you use https? I don't redirect http to https.
I checked it and it is working here.

It works fine in Chromium but I'm still not able to load it in Firefox. I'm not sure if it's a DNS issue, but likely something on my end.


serialization: Add custom attribute to collection items

Currently we can add custom attribute to single item but not to collection items.
For example, this works:
this.serializeWith('book', factory(function() {
    this.add('publisherId', function(book) {
        return book.publisher.id;
    });
}));

But this doesn't (let's say books is an array):
this.serializeWith('books', factory(function() {
    this.add('publisherId', function(book) {
        return book.publisher.id;
    });
}));

Other methods like rename() works with collection items and I have many use cases of add() with them. This pull request makes add() work too.

@shuhei thanks a lot, it helps me too!
Currently using gem right from your repo. Want it to be merged.

I've encountered another issue using your code, don't sure about it's reason:
I've such configuration:
A team, that have a vehicle and some members (which are mapping between position and user).
Example: Team “Foo” that rides on some Subaru car and driver Anton and navigator Andrey sits inside it):
@app.factory 'Team', (railsResourceFactory, railsSerializer) ->
  railsResourceFactory(
    url: teams_path(),
    name: 'team',
    serializer: railsSerializer ->
        @nestedAttribute('members');
        @resource('members', 'Member');
        @resource('vehicle', 'Vehicle')
        @add 'vehicle_id', (team) -> team.vehicle.id
        @exclude 'crew', 'vehicle'
  )

@app.factory 'Member', (railsResourceFactory, railsSerializer) ->
  railsResourceFactory(
    url: members_path(),
    name: 'member',
    serializer: railsSerializer ->
      @resource('user', 'User')
      @resource('slot', 'Slot')
      @add 'user_id', (member) -> member.user.id
      @add 'slot_id', (member) -> member.slot.id
      @exclude 'user', 'slot'
  )

The problem that is when serializing each member resources user and slot are being excluded before the functions provided to add methods are executed and member.user isn't present inside them. That happens only in nested resources.
Solution that helped me can be found at https://github.com/Envek/angularjs-rails-resource/commit/c0ba3c4d93f79dabf729d1f7799cb81f70249f38

I just ran into the same limitation.  I have a nested resource that I am serializing and it has an attribute I want to add.  I had the same limitations that @Envek was having, and his patch worked perfectly.
+1 for updating this with @Envek's commit and getting it merged.

Thanks for the fix, just pushed 1.2.2 with the fix included

Could we get @Envek's patch included too?  I need it to get serialization to work.  It updates the serialization method so the custom serialization logic is at the end like this:
Serializer.prototype.serialize = function (data) {
                    var result = angular.copy(data),
                        self = this;

                    if (angular.isObject(result)) {
                        angular.forEach(this.customSerializedAttributes, function (value, key) {
                            if (angular.isArray(result)) {
                                angular.forEach(result, function (item, index) {
                                    var itemValue = value;
                                    if (angular.isFunction(value)) {
                                        itemValue = itemValue.call(item, item);
                                    }

                                    self.serializeAttribute(item, key, itemValue);
                                });
                            } else {
                                if (angular.isFunction(value)) {
                                    value = value.call(data, data);
                                }

                                self.serializeAttribute(result, key, value);
                            }
                        });
                    }

                    result = this.serializeValue(result);

                    return result;
                };

@Envek, maybe you should open a pull request with just your patch

This is really quick and dirty hack that just changes order of processing internal and custom serialization logic. So, it may break something (I haven't tested it).
I'll try to make a pull request from it in a few days.

@tpodom Thanks for merging!
@Envek @CyborgMaster I'm sorry for being unresponsive. Does the issue happen only on my path or even on 1.2.1?

@shuhei It's impossible to check whether issue exists in 1.2.1 because serialization of nested resources doesn't work there at all without your patch. If you look on my changes you will see that it seems unrelated to your changes.

@Envek Ah, I see. I am relieved to find that my patch didn't introduce another bug.


[FFM-6778] Update FF release notes

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-633

Preview environment: https://ci.pr.harness.io/pr-633


Fix Windows full path in .pot file

Fixes
Fixes #277 by @krysal
Description
This PR fixes file path in src/locales/po-files/openverse.pot to be consistent between Windows and Linux.
Testing Instructions
Running the following command makes references using the relative path from project root directory src/path/to/file.vue:
npm run i18n:generate-pot

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Thank you for kind words!


Add arbitrary number of environment variables in testNg ant build.xml

TestNg provides support of setting environment variables in ant task.

But in may case I have arbitrary list of environment variables. Is there any way I can do this.
Anyone please help me in this.

@juherr - Any idea on what this issue is all about ?

@krmahadevan No idea.

@juherr - Should we close this off and ask the requester to re-open if they can provide additional details ?

@krmahadevan yes
@abhilekhsingh If your need still exists, could you explain more?


fix artifact naming in release

Thanks for trying; looks like we've still got an issue: https://github.com/bytecodealliance/componentize-py/actions/runs/11507239372/job/32033830809
BTW, I think you should be able to enable Actions on your fork and test this kind of thing by pushing to your main branch.  That's what I've done in the past with other projects.

Thanks for the hint. Resolved here: https://github.com/bytecodealliance/componentize-py/pull/116


Eloquent Generates Valid Postgres That Fails.

Laravel Version: 5.8
PHP Version: 7.2
Database Driver & Version: Postgres 10.6

Description:
An SQL query built by Eloquent is throwing an error when I run it from my app, but when I cut & paste the same SQL into a CLI client, it works fine.
Steps To Reproduce:
$team is just an Eloquent model, the events() relationship defined as
    public function events()
    {
        return $this->hasMany(\App\Event::class);
    }

In a Blade template I have this :
      @foreach ($team->events()
                     ->where('kick_off', '>=', now())
                     ->where('kick_off', '<=', "now() + INTERVAL '1 MONTH'")
                     ->get() as $event)
        @component('components.event-card', ['event' => $event, 'actions' => [] ])
          {{ $event->title }}
        @endcomponent
      @endforeach

Which, according to the error log generates this SQL:
select * from "events" where "events"."team_id" = ea3c5907-bc48-4fd4-8f90-e42fcd29bb33 and "events"."team_id" is not null and "kick_off" >= now() and "kick_off" <= now() + INTERVAL '1 MONTH'

The full error that's being thrown, according to debugbar is:
    * SQLSTATE[22007]: Invalid datetime format: 7 ERROR: invalid input syntax for type timestamp: "now() + INTERVAL '1 MONTH'" (SQL: select * from "events" where "events"."team_id" = ea3c5907-bc48-4fd4-8f90-e42fcd29bb33 and "events"."team_id" is not null and "kick_off" >= now() and "kick_off" <= now() + INTERVAL '1 MONTH') (22007)
    * SQLSTATE[22007]: Invalid datetime format: 7 ERROR: invalid input syntax for type timestamp: "now() + INTERVAL '1 MONTH'" (22007)

I need to wrap the team ID in single quotes to get it to run, but when I use the psql cli to run it, it works fine. (I don't get the same error when I leave the quotes out, I guess that's because it's using a prepared statement?)
For completeness, the table structure is this:
sports_admin=# \d events
                            Table "public.events"
   Column   |              Type              | Collation | Nullable | Default
------------+--------------------------------+-----------+----------+---------
 id         | uuid                           |           | not null |
 created_at | timestamp(0) without time zone |           |          |
 updated_at | timestamp(0) without time zone |           |          |
 title      | character varying(255)         |           | not null |
 kick_off   | timestamp(0) without time zone |           | not null |
 meet_time  | timestamp(0) without time zone |           |          |
 address_id | integer                        |           | not null |
 team_id    | uuid                           |           | not null |
Indexes:
    "events_pkey" PRIMARY KEY, btree (id)

Are you using any additional Composer packages? Laravel doesn't generate queries like this.

Are you using any additional Composer packages? Laravel doesn't generate queries like this.

Apologies, I pasted a workaround I found as the example code, I've replaced it in the bug description and for clarity here it is:
$team->events()
    ->where('kick_off', '>=', now())
    ->where('kick_off', '<=', "now() + INTERVAL '1 MONTH'")
    ->get()

With where(), the values are passed as bindings. The executed query actually looks like this:
... and "kick_off" <= 'now() + INTERVAL \'1 MONTH\''

Use a raw expression (or now()->addMonth()):
$team->events()
    ->where('kick_off', '>=', now())
    ->whereRaw("kick_off <= now() + INTERVAL '1 MONTH'")
    ->get()

I see, and when the error is displayed, the ' is rendered as '
Ok, not a bug (in Eloquent at least).


[Decompiler] vector-v++! is missing a set!

Likely due to a bug in the logic for coloring move elimination.

I'm not totally sure what this problem looked like, but it looks fine now. It's a pretty nice example of the expression building being able to figure out some confusing register moves.
asm:
    daddiu sp, sp, -32
    sd ra, 0(sp)
    sq gp, 16(sp)

    or gp, a0, r0
    lw t9, vector+float*!(s7)
    or a0, gp, r0
    or v1, gp, r0
    or a2, a1, r0
    lw a1, *display*(s7)
    lwc1 f0, 904(a1)
    mfc1 a3, f0
    or a1, v1, r0
    jalr ra, t9
    sll v0, ra, 0

    or v0, gp, r0
    ld ra, 0(sp)
    lq gp, 16(sp)
    jr ra
    daddiu sp, sp, 32

(defun vector-v++! ((arg0 vector) (arg1 vector))
  (vector+float*! arg0 arg0 arg1 (-> *display* seconds-per-frame))
  arg0
  )


[WIP] Target Hyrax instead of CurationConcerns

Work in progress to use Hyrax instead of CurationConcerns.

Changes Unknown when pulling c1314f3e1c5cb5c25993b7a0b2a29b04536b10b9 on hyrax into ** on master**.

Changes Unknown when pulling 7c86142481651874f394a4b160aa081de6794192 on hyrax into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>b91c73b4ad000d77913c62a1cd8a5d on hyrax into ** on master**.

Changes Unknown when pulling 2d1a9be4349ddac69ca513e455d18e3f3f1b23d6 on hyrax into ** on master**.

Changes Unknown when pulling 3a5491374eb7d85865f95181919a606ab88f6e55 on hyrax into ** on master**.

Changes Unknown when pulling 3a5491374eb7d85865f95181919a606ab88f6e55 on hyrax into ** on master**.

Changes Unknown when pulling 9bddebd3aac9de3d7d85489c6b6d05e49d365d01 on hyrax into ** on master**.

Changes Unknown when pulling 54edd46948a0cb77879ebadbafb73c03da3670b3 on hyrax into ** on master**.

Changes Unknown when pulling 54edd46948a0cb77879ebadbafb73c03da3670b3 on hyrax into ** on master**.

Changes Unknown when pulling 8ac3f6681a13831fedf1ae4dd263586ba927ab4d on hyrax into ** on master**.

Changes Unknown when pulling e9b858c785c6d576349a08c76e4880ab65579854 on hyrax into ** on master**.

Changes Unknown when pulling 5bca765360ecd89754ef3d333711fc40abf1f254 on hyrax into ** on master**.

Changes Unknown when pulling 7ee4e45d762bc7d727a3c02d960a2b2243194176 on hyrax into ** on master**.

Changes Unknown when pulling 59baa5da2ebceaaa47649072d54266d2ba1dc165 on hyrax into ** on master**.

Changes Unknown when pulling 59baa5da2ebceaaa47649072d54266d2ba1dc165 on hyrax into ** on master**.

Changes Unknown when pulling 2f507810ef942a2aae96282b5c0146e5985e597a on hyrax into ** on master**.

Changes Unknown when pulling 722fe770d77bd3ccb5dc5533b189efe0fcb1daf4 on hyrax into ** on master**.

Changes Unknown when pulling a98352400bc84775078bae0622352b3d852fb474 on hyrax into ** on master**.

Changes Unknown when pulling 22c0b80e8a68a2b33b331fd26dd05d1d6a4d3af3 on hyrax into ** on master**.

Changes Unknown when pulling 2661e3fb9d9aff2375c03db517e53faa3d7b1b15 on hyrax into ** on master**.

Changes Unknown when pulling 2d111c6125b94970a214d0adc89e3ffe688b6f8f on hyrax into ** on master**.

Changes Unknown when pulling fa667ecab9d37287ab87743b0dbbda264a8c8105 on hyrax into ** on master**.

Changes Unknown when pulling fa667ecab9d37287ab87743b0dbbda264a8c8105 on hyrax into ** on master**.

Changes Unknown when pulling 84d2d0b7612418979c0fa65dea4a0686e5f7fc0a on hyrax into ** on master**.

Changes Unknown when pulling d11a81ebc8efcd84daae7afe9dc559d73c1a605e on hyrax into ** on master**.

Changes Unknown when pulling 1a2ec5a7baf0ee42b889840d278e096076967d2b on hyrax into ** on master**.

Changes Unknown when pulling da15412b3a7da40bd9a8fc189877d0d1b416ae60 on hyrax into ** on master**.

Changes Unknown when pulling a25a925fda07485014b14837a5f968d2196920c4 on hyrax into ** on master**.

Changes Unknown when pulling 450c28d85ec8f49c9d74a694f3235891b00203fb on hyrax into ** on master**.

Changes Unknown when pulling fa2b4429b854b2561c91d10c231e15c981d01c00 on hyrax into ** on master**.


Fix NPC Indicator plugin regression

Fix an issue introduced by #3778 that would prevent the player from clicking the "Tag" option on pillars in the pinball random event.

That's an oddly specific bug. :+1:

Also related:

Usually when we add our own actions they are of type RUNELITE - can you not just check that?

It calls menuManager.addNpcMenuOption which loops over the available NPC actions of that npc's composition to look for an empty spot, then fills it with the new action.
On another note, if all options are already taken there won't be a new one added. I'm not sure if there's NPCs that have that many actions (5) but it is likely possible to happen at some point.

menaphite thugs cant get tagged because of that


[cherry-pick][release/5.9] [Build] Don't configure LLDB with tests enabled if the tests will be skipped

Currently the --skip-test-lldb flag will only skip running the
tests. But we still pass LLDB_INCLUDE_TESTS to CMake when configuring
LLDB.
Since https://github.com/apple/swift/pull/66018 configuring LLDB tests will
now always require libcxx to be built. For some presets (e.g.,
buildbot_osx_package) we don't need to build libcxx and we explicitly
pass --skip-test-lldb; this means if we were to try configure LLDB
tests we would hard error.
The proposed solution is to check whether the user wants to skip LLDB
tests, and if so, set LLDB_INCLUDE_TESTS=FALSE.
rdar://109774179

@swift-ci test


Quickstart: transport: authentication handshake failed

Summary
What happened/what you expected to happen?
When connecting to the UI of Argo Workflows (after port forwarding), I receive this message and virtually no components load:
Service Unavailable: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"

What version of Argo Workflows are you running?
latest (ie 3.2.6)
Diagnostics
Quickstart Guide - follow steps in guide to reproduce
What Kubernetes provider are you using?
EKS/Minikube
Configuration:
    spec:
      containers:
      - args:
        - server
        - --namespaced
        - --auth-mode
        - server
        - --auth-mode
        - client
        - --insecure-skip-verify
        - "true"

kustomization.yaml
resources:
  - namespace.yml
  - https://raw.githubusercontent.com/argoproj/argo-workflows/v3.2.6/manifests/quick-start-minimal.yaml

namespace: argo-workflows

Note: This is reproducible w/ the minimal quickstart via minikube as well

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

I also have this issue

argo-server seems to respond with 503 but can't see it in argo-server pod logs even with -v flag

I've ended up by using --secure=falseas a workaround. Also deleted nginx.ingress.kubernetes.io/backend-protocol: https

@materkey I have done this in the past...its just kind of annoying to update the readiness probe, add a new flag to server start, update ingress; This definitely needs to be resolve by the Argo team bc any new user of workflows is going to be put off by these errors. I have used the quickstart it he past without any issues...so this seems a bit wonky.

I believe I found the issue; the argo CLI is using latest for the image tag, instead of specifying the version tag (ie v3.2.6). I have tested this w/ v3.1.15 and after changing the image tag, it works. I will now validate same for version 3.2.6

I was able to fix this by patching the image off of latest
resources:
  - namespace.yml
  - https://raw.githubusercontent.com/argoproj/argo-workflows/v3.2.6/manifests/quick-start-minimal.yaml

images:
- name: quay.io/argoproj/argocli
  newTag: v3.2.6

namespace: argo-workflows

Please, you must use the manifests attached to the release:
kubectl create namespace argo
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.2.6/install.yaml

@alexec I believe the quickstart guide is broken then, as the latest tag on argocli will spawn the issue mentioned by this bug

I now think this might be bug.

Maybe caused by:
72356abad fix: Allow self-signed Root CA for SSO. Fixes #6793 (#6961)

Maybe
3614db690 feat: adding support for getting tls certificates from kubernetes secret (e.g. (#7621)

@ChaosInTheCRD do you think your commit could have introduced this bug please?

I ran into this error after updating one of my clusters from GKE 1.19 to 1.20. I cannot seem to connect to argo-server since restarting deployments, no matter what I try.

I was able to fix this by patching the image off of latest

This worked for me, too.

Please, you must use the manifests attached to the release:
kubectl create namespace argo
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.2.6/install.yaml

This did it for me. I was using the quick start manifest instead of the release specific. That will have to be updated.

Please, you must use the manifests attached to the release:
kubectl create namespace argo
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.2.6/install.yaml

For kustomize users, it's much easier to reference the remote base from git. We tried to do this for the 3.2.6 tag and experienced the same issue.
We've been doing the same with argo-cd for a while without issues.
It look like they're overriding the images with the correct version when the git tag is created:

https://github.com/argoproj/argo-cd/blob/v2.2.3/hack/update-manifests.sh
https://github.com/argoproj/argo-cd/blob/v2.2.3/manifests/ha/base/kustomization.yaml

I found https://github.com/argoproj/argo-workflows/issues/2715 that seems related, @alexec can you reopen it to continue the kustomize discussion there?

@alexec it seems that yes, the problem has come from my PR, apologies for that. My suspicion is that it is related to the removal of this line, which I overlooked as I guess some process (I guess the UI) can't trust the self signed cert generated. I will investigate this further.
I guess though, the main thing to resolve right now is to ensure that this quickstart does not use the latest image. This way it can be ensured that prerelease bugs like this don't hinder users.
As for the error itself, can I get some clarity on what is resolving the error? Is it directly from the ui or is there something else involved (e.g. API).

This issues is a blocker or v3.3, which we'd hoped to release this week. If you don't have time to look into this, I suggest we revert the commit.

As for the error itself, can I get some clarity on what is resolving the error? Is it directly from the ui or is there something else involved (e.g. API).

I found that I could not submit workflows to the API, so this does not appear to be a UI-only issue. Ensuring latest was not used was the means of resolving the error for me.


File dialog: IEnvironmentService#userHome is deprecated

@alexr00 this is a wip for introducing the native environment service only on the layer of the native file dialog experience.
What is still missing is that getUserHome probably needs to be typed that it may return undefined because that is the reality in the web. Maybe you could take over from here?
In the end, depending on the native environment service userHome is OK, it will stay. Only the common one should go away.

Thank you for the wip!


CVE-2022-2068 and CVE-2021-3999 in most recent release

Hi,
checking the most recent released version with a vulnerability scanner brings up the critical CVE-2022-2068 and high CVE-2021-3999.
Checking can be done with trivy image ghcr.io/prymitive/kthxbye:v0.15
Building a fresh version from the current main branch resolves these, would be great if you could publish a new release to have those resolved in the "offical" images.
Cheers

I believe this is fixed as v0.16:
trivy image ghcr.io/prymitive/kthxbye:v0.16

...
Total: 21 (UNKNOWN: 0, LOW: 11, MEDIUM: 4, HIGH: 6, CRITICAL: 0)
...


Use Jemalloc and blocking tasks for expensive operations

Motivation
This PR uses blocking tasks for add_unconfirmed_transaction and block production. Additionally, Jemalloc is set as the GLOBAL memory allocator.

Closing, as we already use jemalloc, and blocking tasks were proposed separately.


Republish editions when dependent editions change

https://trello.com/c/oYy2udbc
Proposal: How to handle dynamic govspeak elements
following up tracking edition's contact dependencies in https://github.com/alphagov/whitehall/pull/2009, we're doing the same by tracking an edition's dependencies on other editions through use of admin links. the aim is to re-publish dependent editions when draft editions they depend on get published.
important to note, the dependency ceases to exists once the dependable edition is published, hence we clean-up those dependencies. once an edition moves to a superseded or unarchived state, we can clean the dependencies, because we don't need to republish such editions.

Hi Vinay,
I've spent a bit of time thinking through some edge case scenarios. I was concerned about the fact that the dependency is edition->edition but semantically it's edition->document. So I was thinking through possible issues where the depended-upon thing might be published again. I don't think there are issues there, but it was sufficiently complicated to think through that a test case covering that scenario might be warranted. e.g.

E2(published) links to E1(draft)
publish E1
(E2 is republished)
redraft(E2) producing E3
publish E3
(E2 is not republished)

I realise that this scenario is partly covered but like I said there are quite a lot of moving parts and it might be valuable to have extra coverage here. I think it could go in test/unit/services/listeners/edition_dependencies_test.rb
I think there's one edge case around unpublishing however, I don't think this is necessarily a show-stopper. The scenario I'm thinking of is:

E2(published) links to E1(draft)
publish E1
(E2 is republished)
unpublish(E2) setting E2 status to draft
(no dependency record is created... BUG!)
modify title of E2 causing slug to change
publish E2
(E2 is not republished.. BUG!)

I'm writing this a bit late in the day so there's a chance I've made a mistake. I haven't verified this bug in practice, only theoretically.
Like I said this is not necessarily a show-stopper as I think the scenario is unlikely and the side effect is only a failure to republish a dependent edition in this edge case.
David

@heathd
(1) good point about adding a test to cover publishing of subsequent editions of dependable editions. i've added that: https://github.com/alphagov/whitehall/commit/5e2898cc938b579b4c85125815bf03881cabc250
(2) the second edge case you're describing related to unpublishing is not a concern. at step 2 in your illustration, E1 is published, so dependency of E2 on E1 ceases to exist. think about it. once published, E1 is frozen, so it can't be changed. consequently, unpublishing E2 should not require dependency on E1 to be recorded. so there's no BUG! at step 3.

@vinayvinay regarding point (2) I'm afraid I made a mistake in the steps, sorry I was tired.
It should have read:

E2(published) links to E1(draft)
publish E1 (E2 is republished)
unpublish(E1) setting E1 status to draft (no dependency record is created... BUG!)
modify title of E1 causing slug to change
publish E1 (E2 is not republished.. BUG!)

the problem is that the slug of a document CAN be changed when it is unpublished, so when something is unpublished (in step 3) any editions which link to it (E2 in this case) need to have dependencies recreated.

@heathd: now i see... that's a good point! if you think it is worth it, i can cover this scenario, shouldn't take too much effort to do that.

We should fix this scenario. Rather than deleting the edition dependency row when the edition is published, could we have an "active" boolean column that is flipped to false on publish, and back to true on unpublish?

@danielroseman: the other option is to fire one query to select editions that have admin links to the edition being unpublished, and populate dependencies from that. this will make sure the dependencies table holds more valuable information.

@danielroseman, @heathd: i've covered the scenario where the depended-upon edition is unpublished and published again by delaying destroying records of dependent editions: https://github.com/alphagov/whitehall/commit/25786559022c96bc056fdb40da5c1ec79d8a8374
earlier, they were being destroyed when the depended-upon edition was published, so that we clean-up as soon as they're no longer required. now, we continue to hold onto these associations till the time the depended-upon edition is superseded. there's no side-effect because we republish dependants
only when the depended-upon edition is published / force-published.
we're avoiding introducing complexity in code to handle this, at the cost of storing a few more records in the db. theoretically, a depended-upon edition remains depended-upon till the time it is superseded (because it can be unpublished anytime), so we're good with that way of thinking as well.

This looks very sensible, although I'll wait for David to comment.
It will lead to more than a "few" more records, since most editions don't get superseded at all, but I don't think that is a problem.

@danielroseman: i had checked, i should have said "few hundred". in the copy of WH db i've got there are only 287 published editions that contain admin links.

Looks good to me, I'm going to go ahead and merge so it's ready to deploy on Monday.


Add internationalization for the login, projects top bar, documentation and report errors

Added internationalization for:

Login page
Default view on the top bar
Open documentation link
Report error link

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/494 (JID-2218)


tap is disabled when navigating to same page

When navigation starts the process (roughly) is to start navigation (which disables tap ability), find the page, process it and then end navigation (which re-enables tap).
If the page is the current one it stops the process and never proceeds to the end navigation code, so tap is permanently disabled.
I found it due to a bug in my code (A login screen first is rendered with a "current" class but this class remains if the page is reloaded due to an invalid login.  My fix is to not set the "current" class if it is an AJAX call), however, I'm sure this might hit someone else in a legitimate scenario.

See issue #243

Should be fixed in current master, let me know if not.


The training data set confuses me, how to build it?

The training data set confuses me, how to build it?
how can i train on my own dataset? what do i need to prepare?

We describe the training dataset we used and how to prepare it in the README. We also provide the training code, which you can run with python src/main.py, provided that you have the data downloaded and prepared on your machine.
For training on your own dataset, you need to provide your own dataset in the static_dataset.path argument of the configuration file. This should be a folder with two subfolders, train and test, each formatted as a Dataset from the dataset.py file.

We describe the training dataset we used and how to prepare it in the README. We also provide the training code, which you can run with python src/main.py, provided that you have the data downloaded and prepared on your machine.
For training on your own dataset, you need to provide your own dataset in the static_dataset.path argument of the configuration file. This should be a folder with two subfolders, train and test, each formatted as a Dataset from the dataset.py file.

Do you have an example of the data set format?

The CSGO data can be used as an example. You can see the creation of the low res dataset from the high res dataset in process_csgo_tar_files.py for example.

The CSGO data can be used as an example. You can see the creation of the low res dataset from the high res dataset in process_csgo_tar_files.py for example.

CSGO data can not be downloaded. Do you have any other url link to get the datasets?

Thank you for the insights @AdamJelley (and great paper!). The CSGO dataset is currently unavailable as per its own author. Would someone here be able to upload a sample of the training dataset?
It would help a lot with creating a custom dataset, as it's otherwise quite error prone.


Select language for Multilingual?

With multilingual, is there a way of specifying the language? Mine seems to result in English even for French input

Yes. Multilingual model support transcription and translation.
For Transcription, it supports Any -> Any
For Translation, it supports Any -> English
I see your requirement is first one, transcription. But, the generated multilingual model which is in this got repo is for translation. For Transcription, you need to generate model.

Yes. Multilingual model support transcription and translation. For Transcription, it supports Any -> Any For Translation, it supports Any -> English
I see your requirement is first one, transcription. But, the generated multilingual model in this git repo is for translation. For Transcription, you need to generate model.

Thank you for clarifying that.
Are there models available to download anywhere, or did you create these ones yourself? I'm not familiar with this stuff, and am just trying to get some transcription into my existing app.

You can find google colab notebook in one of the comment on this repo

Thank you


Add styling

In this PR, I implemented stylings using Vanilla CSS.
Here is a screenshot of the recommended changes implemented

Alhamdulillah I appreciate you I was super worried but thanks to you @KanzaTahreem


Suppress warnings for spotbugs 4.8.3

Suppress warnings for spotbugs 4.8.3
https://github.com/jenkinsci/plugin-pom/pull/869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later.
Plugin pom 4.77 is likely to include that new version of spotbugs.
Testing done
Confirmed that the spotbugs warnings are visible when using the 4.77-SNAPSHOT plugin pom before this change. With this change, the spotbugs warnings are no longer visible.
### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes

Thanks @kuisathaverat .  This does not require a new release of the plugin.  It can be labeled chore or skip-changelog.  I just don't want the plugin pom upgrade to be blocked by a spotbugs warning.


Update routing-with-expressroute.md

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@kelleyvice-msft - Can you please assist to check, approve and merge the content of this PR?
Thank you.

@kelleyvice-msft - We would like to follow up on this. Can you please assist to check, approve and merge the content of this PR?
Thank you.

@kelleyvice-msft - We would like to follow up on this. Can you please assist to check, approve and merge the content of this PR? Thank you.
cc: @LauraWi

@mypil - sorry! The notifications were going into an Outlook subfolder. Can you tell me where you got verification of the change? If it's been verified, I will merge the PR.

@kelleyvice-msft - this was a PR created by @troofeds, there is no issue related to this.
@troofeds - can you tell us where you got verification of the change?

@troofeds -We would like to follow up.  Can you please tell us where you got verification of the change?

https://docs.microsoft.com/en-gb/azure/expressroute/expressroute-introduction

@kelleyvice-msft - kindly refer to the reply above from @troofeds. Please check if this would suffice to merge this PR. thank you.

Looks good. Thanks for the update!


Language issue when submitted to store

Hi,
I'm using the latest Nuget version, 1.0.3, managed.
My projects has french resources, in a /Resources/fr/resources.resw file.
When I submit my project to the store, it wants me to add a description for the fr-FR language, which is not correct because I don't explicitly support it.
When I remove the XamlBehaviors package it doesn't ask me for an extra language, which is the expected behaviour.
I already tried this solution : http://metronuggets.com/2015/12/03/got-unexpected-extra-languages-in-your-uwp-store-submission/ but it doesn't solve anything.
Any idea about this ?
Regards,

@ScottIsAFool any thoughts?

Not really. Might be something we need to raise with MS


Connection retry every 5 seconds stopped working

The grin-miner no longer reconnects if its connection to the server is broken.
Steps to reproduce:

Start a grin wallet listener
start a grin server with stratum server enabled
start a miner on that stratum server
The miner will connect and start mining.
stop the grin server (and stratum server)
The miner will lose its connection and say "Connection Status: Can't establish server connection to localhost:13416.  Will retry every 5 seconds."
start the grin server (and stratum server)

Expected:   The grin-miner should reconnect within the 5-second interval, and resume mining.
Actual:  The grin-miner remains disconnected with the same connection status message.

Here are the grin-miner logs for the event:
Jan 02 23:05:33.004 ERRO Error reading message: ConnectionError("broken pipe")
Jan 02 23:05:33.112 DEBG Miner received message: StopJob
Jan 02 23:05:33.112 DEBG Stopping jobs
Jan 02 23:05:33.112 DEBG Pause message sent
Jan 02 23:05:33.157 DEBG solver_thread - solver_loop_rx got msg: Pause
Jan 02 23:05:33.220 WARN Connection Status: Can't establish server connection to mwfloopool.com:3333. Will retry every 5 seconds
Jan 02 23:05:33.231 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"login","params":{"agent":"grin-miner","login":"foo16","pass":"bar"}}
Jan 02 23:05:33.343 ERRO
thread 'client_controller' panicked at 'called `Option::unwrap()` on a `None` value': libcore/option.rs:355stack backtrace:
   0:     0x5589ca27ebb6 - backtrace::backtrace::libunwind::trace::h4f1eb391823a5f81
                        at /home/bdoyle/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.9/src/backtrace/libunwind.rs:53
                         - backtrace::backtrace::trace::h6a83df765cc0adc5
                        at /home/bdoyle/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.9/src/backtrace/mod.rs:42
   1:     0x5589ca2792c3 - backtrace::capture::Backtrace::new_unresolved::hde36ae9aafa6a496
                        at /home/bdoyle/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.9/src/capture.rs:88
   2:     0x5589ca27921d - backtrace::capture::Backtrace::new::h6c48d3430f353b80
                        at /home/bdoyle/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.9/src/capture.rs:63
   3:     0x5589ca1a5e87 - grin_miner_util::logger::send_panic_to_log::{{closure}}::hc308aa077f52697d
                        at util/src/logger.rs:120
   4:     0x5589ca2eca06 - std::panicking::rust_panic_with_hook::h71214e7ce0f7ac01
                        at libstd/panicking.rs:480
   5:     0x5589ca2ec551 - std::panicking::continue_panic_fmt::ha8b8442f4ea9bcac
                        at libstd/panicking.rs:390
   6:     0x5589ca2ec435 - rust_begin_unwind
                        at libstd/panicking.rs:325
   7:     0x5589ca33310c - core::panicking::panic_fmt::h0c93626b89c38af6
                        at libcore/panicking.rs:77
   8:     0x5589ca33303b - core::panicking::panic::h158c6e3285d6c3fb
                        at libcore/panicking.rs:52
   9:     0x5589c9e90aff - <core::option::Option<T>>::unwrap::hfaaabe534b19dedf
                        at libcore/macros.rs:20
  10:     0x5589c9e94afe - <grin_miner::client::Stream as std::io::Write>::write::hf6ebfd20836bcaf0
                        at src/bin/client.rs:82
  11:     0x5589c9e95e16 - grin_miner::client::Controller::send_message::ha640b0ceb646ce1f
                        at src/bin/client.rs:213
  12:     0x5589c9e96a13 - grin_miner::client::Controller::send_login::h815ff8d7963ad020
                        at src/bin/client.rs:263
  13:     0x5589c9e9c31b - grin_miner::client::Controller::run::hdcdd345660985d4b
                        at src/bin/client.rs:513
  14:     0x5589c9e569da - grin_miner::main::{{closure}}::hc9188e1152c62b8a
                        at src/bin/grin_miner.rs:206
  15:     0x5589c9ece506 - std::sys_common::backtrace::__rust_begin_short_backtrace::h4b8a46842b717eab
                        at libstd/sys_common/backtrace.rs:136
  16:     0x5589c9eebdb4 - std::thread::Builder::spawn::{{closure}}::{{closure}}::had67f4079cfead58
                        at libstd/thread/mod.rs:409
  17:     0x5589c9e559c4 - <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h40a3d35dcf4e0334
                        at libstd/panic.rs:313
  18:     0x5589c9ea2039 - std::panicking::try::do_call::h942d551848ff4a72
                        at libstd/panicking.rs:310
  19:     0x5589ca2fcd19 - __rust_maybe_catch_panic
                        at libpanic_unwind/lib.rs:102
  20:     0x5589c9ea1917 - std::panicking::try::h783f6e619ccfd1af
                        at libstd/panicking.rs:289
  21:     0x5589c9e55b76 - std::panic::catch_unwind::h82ac0f5d81b44938
                        at libstd/panic.rs:392
  22:     0x5589c9eebb52 - std::thread::Builder::spawn::{{closure}}::he99c462a61ea8b5b
                        at libstd/thread/mod.rs:408
  23:     0x5589c9eebeb4 - <F as alloc::boxed::FnBox<A>>::call_box::h55c628e2df6dc440
                        at liballoc/boxed.rs:672
  24:     0x5589ca2e9e5d - <alloc::boxed::Box<(dyn alloc::boxed::FnBox<A, Output=R> + 'a)> as core::ops::function::FnOnce<A>>::call_once::he3acfc8f1203786f
                        at liballoc/boxed.rs:682
                         - std::sys_common::thread::start_thread::h5213f803a61d7811
                        at libstd/sys_common/thread.rs:24
  25:     0x5589ca2daee5 - std::sys::unix::thread::Thread::new::thread_start::he89121f566d2a8c7
                        at libstd/sys/unix/thread.rs:90
  26:     0x7f26f824b6da - start_thread
  27:     0x7f26f7d5c88e - __clone
  28:                0x0 - <unknown>

@quentinlesceller Can you please take a look?  The crash may be related to the recent TLS work you did?

Excellent!


Option to show advancements, etc as embeds

Research how practical this will be.

There is no hook in the Fabric API for advancements, so this would require a mixin to PlayerAdvancementTracker.


Added height map shape that implement heightmap collision shape

Noticed we didn't have a collision shape for the new height map collision functionality. I guess because this only works in bullet?
I still think its good to have, possibly could use some convenience members so you can convert an image to a height map fast.
Also it does not have a gizmo, does draw the debug shape.

I also need an icon :)

I think having an Image or an ImageTexture parameter (typically because it's also used in shaders) would make it more usable in the editor, although Godot needs to be able to load a float image format.
Otherwise, if we can wait a year or two, I think there is a heightmap-based terrain system in the talks for somewhere in the 4.x series in order to streamline such setups.

I think waiting is not a solution, as nobody will do anything waiting others to do something.
Looking forward for PRs like this to be in as these heavily improve quality of life.

I was thinking of that too, but it should probably be a mode so we don’t
store a copy of the image data in this node.
Once i have my laptop back i’ll see if i can add something nice for that.
I don’t think waiting for a terrain editor being added some day should stop
us from making the tools we have today usable
On Mon, 18 Mar 2019 at 1:43 am, Marc<EMAIL_ADDRESS>wrote:

I think having an Image or an ImageTexture parameter (typically because
it's also used in shaders) would make it more usable in the editor,
although Godot needs to be able to load a float image format.
Otherwise, if we can wait a year or two, I think there is a
heightmap-based terrain system in the talks for somewhere in the 4.x series
in order to streamline such setups.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/27156#issuecomment-473672105,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2vaRa0VGg7mhfuI-G_GQkiT8P3zeHoks5vXlR5gaJpZM4b4SVb
.

--
Kindest regards,
Bastiaan Olij
https://www.facebook.com/bastiaan.olij
https://twitter.com/mux213
https://www.youtube.com/BastiaanOlij
https://www.youtube.com/channel/UCrbLJYzJjDf2p-vJC011lYw
https://github.com/BastiaanOlij

it should probably be a mode so we don’t store a copy of the image data in this node.

The data is copied already, see PhysicsServer heightmap shape.

Hey marc,
Yes it has to be in runtime, i mean storing a copy in the resource itself
as the scene saves the heightdata
On Tue, 19 Mar 2019 at 1:00 am, Marc<EMAIL_ADDRESS>wrote:

it should probably be a mode so we don’t store a copy of the image data in
this node.
The data is copied already, see PhysicsServer heightmap shape.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/27156#issuecomment-473921410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2vaYe0ktuuFh5lvUL7TnixFUHsJftjks5vX5wEgaJpZM4b4SVb
.

--
Kindest regards,
Bastiaan Olij
https://www.facebook.com/bastiaan.olij
https://twitter.com/mux213
https://www.youtube.com/BastiaanOlij
https://www.youtube.com/channel/UCrbLJYzJjDf2p-vJC011lYw
https://github.com/BastiaanOlij

this is wanted, so as long as you guys figure it out feel free to merge

Thanks @Zylann , give me a nudge if I haven't done this by Sunday, I really need to start keeping a todo list :)

Ok I'm happy with this, this can be merged as far as I'm concerned.

Thanks!

Cherry-picked for 3.1.1.


Update/Add Xcode 13.1 RC

Tool name
Xcode
Tool license
Unknown
Add or update?

[ ] Add
[X] Update

Desired version
13.1 RC
Approximate size
No response
Brief description of tool
Xcode 13.1 RC contains all the SDKs and could remove the need for Xcode 13 Beta 5 that's currently in the image to allow macOS 12 code building.
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[X] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Previous conversation here https://github.com/actions/virtual-environments/issues/4084

Ugh. You are right. This is going to be horrible unless we can get macos12 runners ASAP.


Where can I find the resulting picture?

Perhaps I am doing something really stupid here, but I just wanted first to reproduce the very basic example first. I installed the package and created a python script with the following lines:
from supervenn import supervenn
sets = [{1, 2, 3, 4}, {3, 4, 5}, {1, 6, 7, 8}]
supervenn(sets, side_plots=False)

Now I run it - and nothing happens! The script just terminates and I am unable to find resulting picture anywhere. What am I doing wrong?

Most users do any plotting in Python using an interactive environment like Jupyter Notebook. But if for any reason you need it to be run as a script, you can do it as follows:
import matplotlib.pyplot as plt
from supervenn import supervenn
sets = [{1, 2, 3, 4}, {3, 4, 5}, {1, 6, 7, 8}]
supervenn(sets, side_plots=False)
plt.savefig('image.png')


Screen flashing when scrolling on Chrome for Android

In Chrome on Android 5.0.2, when scrolling any of the pages on material-ui.com, at various points, the screen briefly flashes (as if there is a translucent overlay covering the whole viewport).

+1 in Mobile Safari when enable <meta name="viewport" content="width=device-width, initial-scale=1">

@abastardi @kelly-apollo I'm going to close this given that the complete overhaul of styling in the next branch. If you still see the issue on this preview, feel free to reopen the issue.


THREE.WebGLProgram: Shader Error 1282 - VALIDATE_STATUS false

The current npm version of three-csm (1.1.1) doesn't seem to work with the current version of three (0.135.0).
It was spitting out errors about the shader:
THREE.WebGLProgram: Shader Error 1282 - VALIDATE_STATUS false

After switching my import from three-csm to use the official examples, three/examples/jsm/csm/CSM.js, it started working!
I suspect this repo lags behind three?
Anyway, i'm mostly just posting this in case someone else gets stuck :)
Awesome shadows btw :D

I have the same issue.
The right way to import the library is: import { default as CSM } from 'three-csm';

Similar error here. The shader (among other things) seems to have been updated a few times.
Some of the diffs in Shader.js and CSMShader.js in threejs examples

Would be nice if this repo could be used instead of the examples in threejs

Hi, you are right, this repo lags behind three.js examples, I don't update in often enough. But it only matters for new three.js versions.
I will update this repo and package soon (I hope this week), thanks.

I've updated this repo to match the implementation from three.js examples. Current package version - v2.0.0.


fix module generation

Changed UMD wrapper to address the issue.  Also mentioned here

Published as v1.4.4.


Support retry w/ backoff for artifact downloads

The agent should support retry with backoff for artifact downloads to avoid network or rate limiting issues.

Not sure if this is explicitly related, but I have a similar issue that happens frequently.
2021-08-17 21:00:03 INFO   Found 1 artifacts. Starting to download to: <redacted>
--
  | # Received cancellation signal, interrupting

This seems like the same issue. Is there any way to change the https client settings that the buildkite-agent uses? Set retry count or include a retry strategy such as exponential backoff.

Hi @williamblevins I’m not sure what issue you’re describing here, would you be able to get in touch with Buildkite Support to provide more details and we can help you there?

I was working on an artifact plugin request to implement this and found that this is already implemented https://github.com/buildkite/agent/blob/00f2048f77c0e2d6808d1f234b339150569b7279/agent/download.go#L58-L59

thanks for pinging this @toote! will close ^_^


Migrate exporter-collector-grpc to grpc-js

Which problem is this PR solving?

Fixes #2087

Short description of the changes

using grpc-js instead of grpc in exporter-collector-grpc
took a draft rebased, tested then fixed the error

grpc-js is compatible with
"node": "^8.13.0 || >=10.10.0"

I would say it should be fine, but I would like to know what other thinks ?

grpc-js is compatible with
"node": "^8.13.0 || >=10.10.0"
I would say it should be fine, but I would like to know what other thinks ?

cc @dyladan since you have internal stats of dynatrace for this but i would say thats fine too since there are non-grpc exporter available (but we need to update the package.json engines field)

cc @dradetsky

I think it's fine as long as 8.5 customers have the ability to use the http exporter or something else and are not entirely locked out.
At some point we should consider dropping 8.x entirely


Guidance : httpPrefixHeaders

When a Map String -≥ String , is targeted by this trait , implementations are meant to extract all headers , prefix them with the prefix and place them in the map
This seems to be the only trait that grabs all headers in an untargeted fashion.
That said , are there certain headers that SHOULD NOT be placed into the Map ?
From this test , it would seem that the Content-Type header should not be extracted https://github.com/awslabs/smithy/blob/3675c72baffd4565417a96ca1700c0d32fe1f5bb/smithy-aws-protocol-tests/model/restJson1/http-prefix-headers.smithy#L108

No, you're meant to grab all headers. The headers field in the request tests doesn't preclude other headers existing. That test you linked is therefore valid, just incomplete.

this is a response test
the client is meant to deserialize the HTTP response to an object, that object should equal the one modeled in the params

Right, but when you construct the http response to give to a client under test you would only populate those headers that are present. In a real world scenario there may be other things there, but not in the test.


Update docs

Hi @wcandillon , I also noticed that the README for getStyleSheet needs a slight improvement. It looks like your removing it in v3 but I thought for those who are currently using it, it would help to have a better example.

that's awesome thks!


What are best practices for protecting deployment endpoints?

Trying to figure out how to protect a graph node and authenticate deployment requests. I see references to "graph auth" or --access-token parameters here and there, but cannot find any proper docs on any of this.
Does graph-node have any OOTB mechanism for this, or is this something that should be handled at another layer, for ex an Nginx reverse proxy that authenticates the requests?

yes, would love to have some more clarity on this
graph auth seems to be supported with hosted service (graph auth --product hosted-service <token>) but unsure how to enable this authentication when self hosting a graph node

I am also wondering how you do this. Seems like anyone can deploy to my graph node at the moment, which is less than ideal.

For all my purposes, I usually only open the query endpoint to the public (port 8000) and hide all the other api/health/metrics ports

hullo, any news about this?


New package: SUSE.openSUSE.Tumbleweed version 242<IP_ADDRESS> (241001)

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

My VMs cannot enable WSL, so I can't verify:

[Policy] Reaet Feedback


Fix crd validation

Hi folks,
in my last contribution (https://github.com/cert-manager/trust-manager/pull/460) I made a mistake.
I didn't realize the "key" when specifying a source secret with "includeAllKeys" was still required in the CRD.
This causes the webhook to reject bundles which use the new field:
validatingwebhookconfiguration.admissionregistration.k8s.io/trust-manager configured
The Bundle "ecp-internal-cas" is invalid: spec.sources[1].secret.key: Required value

/ok-to-test


[Snyk] Upgrade swagger-ui-react from 4.12.0 to 4.19.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade swagger-ui-react from 4.12.0 to 4.19.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 25 versions ahead of your current version.
The recommended version was released 4 months ago, on 2023-06-12.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Cross-site Scripting (XSS) SNYK-JS-BRAINTREESANITIZEURL-3330766
484/1000  Why? Has a fix available, CVSS 5.4
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@terrytangyuan thought you turned off Snyk?
It is also failing on DCO, PR check, and deduping deps. I was going to make a similar PR myself after #12036 as this was the one UI dep that needed a manual update and test. So we can close this out in favor of that anyway.
But do want to make sure your settings are correctly off for Snyk 😅

Properly upgraded in #12058


[poc] Selector based injection

POC
I added:

a tiltfile
a way to regenerate crd
deleted dead code
modify the CR definition to leverage namespace and pod selector
added some examples

apiVersion: newrelic.com/v1alpha1
kind: Instrumentation
metadata:
  name: matching-whole-test2-namespace
spec:
  namespaceLabelSelector:
    matchExpressions:
      - key: "kubernetes.io/metadata.name"
        operator: "In"
        values: ["test2"]
  configurations:
    java:
      image: newrelic/newrelic-java-init:8.14.0
      env:
       - name: NEW_RELIC_LABELS
         value: "whatever"
    licenseKeySecret: "newrelic-key-secret"

To test it
$ ctlptl create registry ctlptl-registry --port=5005
$ ctlptl create cluster minikube --registry=ctlptl-registry
$ tilt up

in a different terminal:
$  k apply -f local/example-cr.yml
$  k apply -f local/pod-include-namespace-test2.yaml  --server-side=true --dry-run=server -o yaml

Closing this since we created a new branch/PR based on this code.  Thanks for the PoC!


[WIP] Add external TLS-origination tests

It accesses www.cloudflare.com, which has HTTP and HTTPS site versions
the HTTPS version responds with Expect-CT header, this is how it can be
distinguished from the HTTP version.
Expect-CT header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-e2e-envoyv2-v1alpha3

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-e2e-envoyv2-v1alpha3

lint_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test lint

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-e2e-envoyv2-v1alpha3

lint_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test lint

lintmodern_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test lintmodern

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-e2e-envoyv2-v1alpha3

lint_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test lint

lintmodern_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test lintmodern

pilot-multicluster-e2e_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-multicluster-e2e

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-multicluster-e2e

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
a2d3c7be5db35579fc200544d6f13a432697a279
link
/test pilot-multicluster-e2e

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test integ-mixer-k8s-tests

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-multicluster-e2e

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. I understand the commands that are listed here.

Also there are efforts to move tests to test/integration folder so we can run locally as well, and I believe there are some folks running those tests air gapped so this would not work well there

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-multicluster-e2e

e2e-simpleTestsMinProfile_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test e2e-simpleTestsMinProfile

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. I understand the commands that are listed here.

@howardjohn Yes we have such tests https://github.com/istio/istio/blob/master/tests/e2e/tests/pilot/externalservice_test.go.
Once we decide not to use external sites in tests, we will have to rewrite those tests too.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-simpleTestsMinProfile_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test e2e-simpleTestsMinProfile

pilot-multicluster-e2e_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-multicluster-e2e

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-simpleTestsMinProfile_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test e2e-simpleTestsMinProfile

pilot-multicluster-e2e_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-multicluster-e2e

integ-new-install-k8s-tests_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test integ-new-install-k8s-tests

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile_istio
8b388e5150c5fa72f7c5b07a744e85a3127ecb79
link
/test e2e-simpleTestsMinProfile

pilot-multicluster-e2e_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-multicluster-e2e

integ-new-install-k8s-tests_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test integ-new-install-k8s-tests

pilot-e2e-envoyv2-v1alpha3_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-e2e-envoyv2-v1alpha3

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. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-multicluster-e2e

integ-new-install-k8s-tests_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test integ-new-install-k8s-tests

pilot-e2e-envoyv2-v1alpha3_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-simpleTestsMinProfile_istio
77f043fcf0581a8ccc698efaed689ac93d571130
link
/test e2e-simpleTestsMinProfile

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. I understand the commands that are listed here.


New Build Website for the SDK V1 Release

Expected Behavior
cc @vslavich @cmcewen @mcortesi
Current Behavior
What is the current behavior?

closing in favor of https://github.com/celo-org/celo-labs/issues/249


Sort alphabetically the columns in the viewcolumn dialog.

Is it possible?
Thanks

you can display the sorted data coming from your BE by using onTableChange: (action, tableState) => {...}.

I see. You can use . You're able to pass custom components to there.  For example, copy TableToolbar codes in this repo, change wherever you want. in my opinion, it'll be helpful for you.


Add restricted access

Hello,
May it be possible to set up an access restriction with user/password or token (for HA integration)? Currently anyone who knows the IP address is able to connect (and change all the configuration). It is indeed easier during the implementation but all the users of the network are not necessarily intended to do all these manipulations
Regards

I am currently mopping up version 2.0 which has password restrictions for the gears menu among other things like groups, fixed ip addresses, tab interface, and additional mqtt interfaces.

Great  !

I would prefere a password restriction for the whole device :)
(Normaly it is not operated directly via the ESPSomfy-RTS WebPage, but via HA or higher-level systems and only for the people who I have released it for.)
Also I think this would make it easier to implement :)

Yeah I have built an api key implementation. You can choose between all or just the config.

Getting closer I will need to secure the apis next but that will require some changes to the HASS plugin first.  When I am done you will be able to set either a pin or username/password.

There is a lot coming in this release including the ability to pair up groups.  This should be posted to the repo in the next week.

The main repo contains the binaries for v2.0.0.  At this point you can flash your device with these binaries for the firmware and application. This will give you the security functions you are looking for as well as motor groups.
The interface has changed quite a bit and I have begin rewriting the wiki.  There is also a UI reference that can be found at
https://github.com/rstrouse/ESPSomfy-RTS/wiki/User-Interface-Reference

I have not published so they do not yet have a tag.  The binaries are in the main repo.

Working great !!

v2.0.0 has been released.  Don't forget to check out the new grouping functionality as well.


Alchemyst Dig 02 is the wrong version

The current version of Alchemyst Dig 2 that is supplied as a GDash caveset is out of date. The newest version, 13 May 2021, fixed a bug in Cave IV (start 2). Please pull my current release under /BDCFF-sets, all caves present are the most recent caves.

https://github.com/revvv/gdash-export-CrLi/pull/35/commits/80b2d829bc006c991abc6d36573cfe6a1b361123

Thank you. This is the update.