.Net Framework 4.6.2 MVC Application.

Hi,
I've been through the "quick starts" as far as getting ID4 run-able and responding correctly to the example MVC .net core application.
We have an already existing .net application which is using MembershipReboot that we'd like to switch to using ID4.  As a quick test I created an basic .Net Framework 4.6.2 MVC app and have the startup.cs file set as follows...
using Microsoft.Owin;
using Microsoft.Owin.Security.Cookies;
using Microsoft.Owin.Security.OpenIdConnect;
using Owin;
using System.Collections.Generic;
using System.IdentityModel.Tokens;

[assembly: OwinStartup(typeof(MVC_OWIN_Client.Startup))]

namespace MVC_OWIN_Client
{
    public class Startup
    {
        public void Configuration(IAppBuilder app)
        {
            string baseClientAddress = "http://localhost:44301/";

            var authority = JwtSecurityTokenHandler.InboundClaimTypeMap = new Dictionary<string, string>();

            app.UseCookieAuthentication(new CookieAuthenticationOptions
            {
                AuthenticationType = "Cookies"
            });

            app.UseOpenIdConnectAuthentication(new OpenIdConnectAuthenticationOptions
            {
                ClientId = "mvc.standard",
                Authority = "http://localhost:5000/",
                RedirectUri = baseClientAddress + "signin-oidc",
                PostLogoutRedirectUri = baseClientAddress + "signout-callback-oidc",
                ResponseType = "code id_token",
                Scope = "openid api1 offline_access",

                UseTokenLifetime = false,
                SignInAsAuthenticationType = "Cookies"
            });
        }
    }
}

In ID4 config, I created a client to match...
 public static IEnumerable<Client> GetClients()
 {

	...

	new Client
        {
	    ClientId = "mvc.standard",
            ClientName = "MVC Client2",
            AllowedGrantTypes = GrantTypes.HybridAndClientCredentials,

            ClientSecrets =
            {
                new Secret("secret".Sha256())
            },

            RedirectUris           = { "http://localhost:44301/signin-oidc" },
            PostLogoutRedirectUris = { "http://localhost:44301/signout-callback-oidc" },

            AllowedScopes =
            {
                    IdentityServerConstants.StandardScopes.OpenId,
                    IdentityServerConstants.StandardScopes.Profile,
                    "api1"
            },
            AllowOfflineAccess = true
	}
};

The application will progress through the login and permissions page and ID4 finally indicates the user signed in....
info: IdentityServer4.ResponseHandling.AuthorizeInteractionResponseGenerator[0]
      User consented to scopes: openid, api1, offline_access
info: IdentityServer4.Endpoints.AuthorizeCallbackEndpoint[0]
      Authorize endpoint response
      {
        "SubjectId": "2",
        "ClientId": "mvc.standard",
        "RedirectUri": "http://localhost:44301/signin-oidc",
        "State": "OpenIdConnect.AuthenticationProperties=pnxKmthLCWSNS1Tj8sBS1K4K-Erxq8_W3Sfj1gg3zXhTCqP-gKV-Hsfgh_pRLPYQcIdVJONhzA3VMdBNv4xqE7y8uX-pzEmeNKBYb0cPAh6Q9lm5knIS5ds9gccYKubK1U0NpnGAW7tw38brRzD7dEG-EkSgXqjnEGeS4pMCrFaG2CFwq08_-KyA85VufscpT3y9sL0hTLLYYbRiJhWIZBOM427piwaHpR-jbl7KXGo",
        "Scope": "openid api1 offline_access"
      }
info: Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler[10]
      AuthenticationScheme: idsrv signed in.
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
      Request finished in 152.1613ms 200 text/html; charset=UTF-8

That's it.  The MVC Application is never restored, it sits there until it times-out.
Is there something missing from this?

Sorry, it's not clear what the issue is. It also sounds more like the issue is on your client app, rather than anything wrong going on in IdentityServer.

I didn't point the finger at ID4, just want to know whether there were some missing settings as 'the issue' is Identity Server 'appears' to be not replying in a way that a .net framework web application understands.
I needed to ask the question of someone who is working with ID4 on a daily basis as all the examples for ID4, that I can find, are for .net core not .net framework so there's nothing to corroborate with.

The issue tracker for IdentityServer is not for general questions. If you have a problem with how to configure components ASP.NET Core (which is what you're struggling with above), then contact Microsoft's support, please.

I'm not struggling with .net core.  The client and server are working when it's a .net core web application contacting Identity Server, it doesn't when it's contacted from a .net framework app.  I thought this was fairly clear from the descriptions I've provided previously.   I believe it's an issue because there's no response from ID4 back to a .net framework app.

@andy194  sounds like its a issue with your redirect uri like your not getting the response back.   This really isnt an issue with this library you may want to consider asking a question on stackoverflow.com

Why oh why didn't someone just point me to the page on the subject?  This is for anyone else looking for an answer...
https://leastprivilege.com/2017/03/03/extending-identityserver4-with-ws-federation-support/

Thank you for your advice

@andy194 so was your solution to implement ws-federation instead of using openid on your .net framework app?

Yes, if you don't, you end up with the eternal loopback scenario, never
getting a response from ID4.
On Thu, 16 Aug 2018, 20:54 Kevin Aung<EMAIL_ADDRESS>wrote:

@andy194 https://github.com/andy194 so was your solution to implement
ws-federation instead of using openid on your .net framework app?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IdentityServer/IdentityServer4/issues/2059#issuecomment-413665333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGMKYEbAhDl0m05xzA_F64xKqVe_m4fiks5uRc4RgaJpZM4R-Osk
.

I read a lot of issues reported to these guys, and from what I experience they are notorious for misunderstanding obvious questions, blaiming other software, and closing issues without any solutions.   I was able to follow everything you have stated in this post just fine.  Pretty sure they day drink on the regular.

I read a lot of issues reported to these guys, and from what I experience they are notorious for misunderstanding obvious questions, blaiming other software, and closing issues without any solutions. I was able to follow everything you have stated in this post just fine. Pretty sure they day drink on the regular.

I moved to Azure AD B2C because of that.

I agree with their reply. Some questions are really irrelevant to ids4

Given that one of them wrote the article I then found and which pointed me at a solution, you're missing the point, they could have chosen to not be abrupt and just pointed me to it, easily.  There are two types of smart people on this planet, a decent type and the smart-arsed type.

This question is clearly related to Id4.   His question is asking whether or not he is missing something in his configuration that could be causing this issue.  A simple yes or no would be sufficient and at least pointed him in the right direction.

I read a lot of issues reported to these guys, and from what I experience they are notorious for misunderstanding obvious questions, blaiming other software, and closing issues without any solutions. I was able to follow everything you have stated in this post just fine. Pretty sure they day drink on the regular.

And the issue template states that this is not for general support on your architecture or other bugs. We try to be as clear and upfront on this point as we can so as to save us all time and frustration. We work on this project in our free time and we don't have time to debug everyone else's issues. I suspect many folks opening questions here are doing it as a result of a project you're build at work while being paid. I am not being paid to build the OSS, or reply to your issues here. It's a different OSS than that from Microsoft or some other company that funds devs working on it, so I'm sorry your expectations are misaligned.

You are right. I apologize.  The fact you are not getting paid is a valid reason to blatently misunderstand obvious questions.

You should read more Eran Hammer:
https://hueniverse.com/how-to-use-open-source-and-shut-the-fuck-up-at-the-same-time-d933471d59de
https://hueniverse.com/no-cure-for-entitlement-38eb3c80d808

Pretty sure they day drink on the regular.

Yeah - you should better apologize...
https://www.dotnetfoundation.org/code-of-conduct

You guys work too damn hard and produce awesome software to be treated like that! Thank you for all you do!

You are right.  I apologize for being rude.

I ran into the same problem yesterday, and the problem is the cookie configuration I've found.
This was my code
app.UseCookieAuthentication(new CookieAuthenticationOptions
{
//AuthenticationType = "Application",
//AuthenticationMode = AuthenticationMode.Passive,
});
When the commented code is uncommented (for that matter it seems that the AuthenticationType is the big culpret) it went into an infinite loop replying with a new token every time. I was tracking the Notifications in the OpenIdConnectAuthenticationOptions and started to play around with the cookie settings. Was not an IDS4 problem, but was still very confusion.


Time-only behavior is broken

Parsing a time-only string such as “T14:23-0800” will produce a string with the wrong date when the current local date is within the specified time zone offset from the next day UTC.
This is caused by #29. The underlying dateComponentsFromString: methods interpolate the current local date into the components, and dateFromString: then interprets those components in the specified time zone, creating a date that's a day too early (or, presumably, in some time zones, late).

Apparently [3cb3921] (XCTest conversion) reinstated these tests by accident! Oops.


tdweb: Method 'addProxy' is not supported

Hello,
do you have plans to add support proxy for tdweb?
At the time, I receive an error:
{
  "_": "error",
  "@extra": {
    "query_id": 9
  },
  "code": 400,
  "message": "Method 'addProxy' is not supported"
}

No. There is no way it can be supported, because connections are handled by browser and there is no way to force it to use a Socks5, an HTTP or an MTProto proxy.

Ok, thank you for the clarifying


twitter auth Experiment 5

We are getting "TWITTER_RATE_LIMIT_ERROR: 429 Too Many Requests" errors.
Added logging one each tweepy.client to see what is happening.

👍 @SailingSteve we also keep track of how many Twitter queries we make in a day on this page https://api.wevoteusa.org/admin/statistics/

(it is slow at loading, and it is no surprise we are hitting our limit. I'll push this pull request live shortly.


improve: prevent redundant nightly release

The nightly version will be released without a new commit, so the same version will release binaries with different hashes.
Therefore, it may not be possible to update the version with scoop.
So I added a job to check the log date because the release workflow works once a day.

@shiena
Thanks for this PR!
Looks good and I'll merge it.


follow pep8 guidelines

@malverick, the changes cause at least one python syntax error, and introduce a couple of pep8 errors which are currently ignored, mostly E128. But we won't tell it where. 😋

@malverick, I've seen your ping on irc asking about the issues I was referring to, though I haven't seen any of them being fixed before asking for further guidance.
I believe being a gsoc student requires at least initiating action and attempting to discover your mistakes, it can't be expected that maintainers will micromanage everything, including every single syntax error.
These changes introduce pep8 issues:
https://github.com/kivy/kivy/pull/4822/files#diff-81918be91ba63f929fab4570f1bd005cR1085
https://github.com/kivy/kivy/pull/4822/files#diff-81918be91ba63f929fab4570f1bd005cR1069
https://github.com/kivy/kivy/pull/4822/files#diff-ed66fa7317c70c7e7d9afa9867c5e0dcR63
The printed string will contain the spaces used for indentation:
https://github.com/kivy/kivy/pull/4822/files#diff-2d79b53f5ac75b34374ce991529310feR205
Syntax errors/bugs:
https://github.com/kivy/kivy/pull/4822/files#diff-a5080129bf15b963d770e884609e7c55R61
https://github.com/kivy/kivy/pull/4822/files#diff-b79c5046620071b699db11009469a22aR121
@malverick, @saqib1707, @phunsukwangdu: thanks for your contributions so far guys, we will fix the remaining style issues. Please make sure that future prs don't delete previously merged commits, introduce unrelated code, or contain multiple issues like the ones listed above. Reading the changes a couple of times, even after the pr has been submitted, can make a real difference.

@dessant, I am really sorry for not looking thoroughly to my commits and for not discovering these mistakes on my own. I will definitely remember this from now on and will explicitly mention when my PR will be ready to merge and will go through my commits multiple times after submitting pr.
Please accept my apologies and thank you for your guidance. I am looking forward to learn a lot from you all.

@malverick, it's ok, don't be discouraged. 😋 I thought it would be good to clarify our position from the beginning, since we've seen these issues in the prs of all mentioned students.

@dessant, yeah I appreciate that.


Add a failing test case

(caught using quickchecking)

It also fails before the migration go Word types, it seems.

Hmm, I might have done something wrong calculating the example, maybe everything is right… stay tuned.

Sorry, was a bug in Blob.toArray.


Tests: remove LinuxMain.swift

This precludes building tests on Windows.  The use of top-level
expressions requires -parse-as-library, which we cannot pass along.
Furthermore, at this point, it is of questionable value to add the entry
stub as SPM can generate this.  This change allows running the test
suite on Windows.
Test Suite 'All tests' started at 2021-12-15 13:23:44.241
Test Suite 'debug.xctest' started at 2021-12-15 13:23:44.257
Test Suite 'AllScalarsTests' started at 2021-12-15 13:23:44.257
Test Case 'AllScalarsTests.testCollectionConformance' started at 2021-12-15 13:23:44.257
Test Case 'AllScalarsTests.testCollectionConformance' passed (0.406 seconds)
Test Case 'AllScalarsTests.testIndexOf' started at 2021-12-15 13:23:44.663
Test Case 'AllScalarsTests.testIndexOf' passed (0.126 seconds)
Test Case 'AllScalarsTests.testProperties' started at 2021-12-15 13:23:44.789
Test Case 'AllScalarsTests.testProperties' passed (1.275 seconds)
Test Suite 'AllScalarsTests' passed at 2021-12-15 13:23:46.064
         Executed 3 tests, with 0 failures (0 unexpected) in 1.807 (1.807) seconds
Test Suite 'UtilTests' started at 2021-12-15 13:23:46.064
Test Case 'UtilTests.testTupleTypeConstruction' started at 2021-12-15 13:23:46.064
Test Case 'UtilTests.testTupleTypeConstruction' passed (0.0 seconds)
Test Case 'UtilTests.testTypeErasedTupleConstruction' started at 2021-12-15 13:23:46.064
Test Case 'UtilTests.testTypeErasedTupleConstruction' passed (0.0 seconds)
Test Suite 'UtilTests' passed at 2021-12-15 13:23:46.064
         Executed 2 tests, with 0 failures (0 unexpected) in 0.0 (0.0) seconds
Test Suite 'RegexConsumerTests' started at 2021-12-15 13:23:46.064
Test Case 'RegexConsumerTests.testAdHoc' started at 2021-12-15 13:23:46.064
Test Case 'RegexConsumerTests.testAdHoc' passed (0.006 seconds)
Test Case 'RegexConsumerTests.testRanges' started at 2021-12-15 13:23:46.070
Test Case 'RegexConsumerTests.testRanges' passed (0.01 seconds)
Test Case 'RegexConsumerTests.testReplace' started at 2021-12-15 13:23:46.080
Test Case 'RegexConsumerTests.testReplace' passed (0.0 seconds)
Test Case 'RegexConsumerTests.testSplit' started at 2021-12-15 13:23:46.080
Test Case 'RegexConsumerTests.testSplit' passed (0.0 seconds)
Test Suite 'RegexConsumerTests' passed at 2021-12-15 13:23:46.080
         Executed 4 tests, with 0 failures (0 unexpected) in 0.016 (0.016) seconds
Test Suite 'PTCaRetTests' started at 2021-12-15 13:23:46.080
Test Case 'PTCaRetTests.testAcquireRelease' started at 2021-12-15 13:23:46.080
Test Case 'PTCaRetTests.testAcquireRelease' passed (0.0 seconds)
Test Case 'PTCaRetTests.testComplex' started at 2021-12-15 13:23:46.080
Test Case 'PTCaRetTests.testComplex' passed (0.0 seconds)
Test Case 'PTCaRetTests.testDirectCall' started at 2021-12-15 13:23:46.080
Test Case 'PTCaRetTests.testDirectCall' passed (0.0 seconds)
Test Case 'PTCaRetTests.testHappensBefore' started at 2021-12-15 13:23:46.080
Test Case 'PTCaRetTests.testHappensBefore' passed (0.0 seconds)
Test Suite 'PTCaRetTests' passed at 2021-12-15 13:23:46.080
         Executed 4 tests, with 0 failures (0 unexpected) in 0.0 (0.0) seconds
Test Suite 'UnicodeTests' started at 2021-12-15 13:23:46.080
Test Case 'UnicodeTests.testUnsafeDecoding' started at 2021-12-15 13:23:46.080
Test Case 'UnicodeTests.testUnsafeDecoding' passed (0.0 seconds)
Test Suite 'UnicodeTests' passed at 2021-12-15 13:23:46.080
         Executed 1 test, with 0 failures (0 unexpected) in 0.0 (0.0) seconds
Test Suite 'ExercisesTests' started at 2021-12-15 13:23:46.080
Test Case 'ExercisesTests.testAll' started at 2021-12-15 13:23:46.080
Test Case 'ExercisesTests.testAll' passed (0.943 seconds)
Test Suite 'ExercisesTests' passed at 2021-12-15 13:23:47.023
         Executed 1 test, with 0 failures (0 unexpected) in 0.943 (0.943) seconds
Test Suite 'RegexTests' started at 2021-12-15 13:23:47.023
Test Case 'RegexTests.testRender' started at 2021-12-15 13:23:47.023
Test Case 'RegexTests.testRender' passed (0.004 seconds)
Test Case 'RegexTests.testUnit' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testUnit' passed (0.0 seconds)
Test Case 'RegexTests.testLegacyCompile' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testLegacyCompile' passed (0.0 seconds)
Test Case 'RegexTests.testLegacyMatchLevel' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testLegacyMatchLevel' passed (0.0 seconds)
Test Case 'RegexTests.testLegacyPartialMatches' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testLegacyPartialMatches' passed (0.0 seconds)
Test Case 'RegexTests.testLegacySubrangeMatches' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testLegacySubrangeMatches' passed (0.0 seconds)
Test Case 'RegexTests.testLegacyVMs' started at 2021-12-15 13:23:47.027
Test Case 'RegexTests.testLegacyVMs' passed (0.037 seconds)
Test Case 'RegexTests.testCompilerInterface' started at 2021-12-15 13:23:47.064
Test Case 'RegexTests.testCompilerInterface' passed (0.008 seconds)
Test Case 'RegexTests.testLexicalAnalysis' started at 2021-12-15 13:23:47.072
Test Case 'RegexTests.testLexicalAnalysis' passed (0.0 seconds)
Test Case 'RegexTests.testMatch' started at 2021-12-15 13:23:47.072
Test Case 'RegexTests.testMatch' passed (0.0 seconds)
Test Case 'RegexTests.testParse' started at 2021-12-15 13:23:47.072
Test Case 'RegexTests.testParse' passed (0.02 seconds)
Test Case 'RegexTests.testParseErrors' started at 2021-12-15 13:23:47.092
Test Case 'RegexTests.testParseErrors' passed (0.0 seconds)
Test Case 'RegexTests.testModernCaptures' started at 2021-12-15 13:23:47.092
Test Case 'RegexTests.testModernCaptures' passed (0.001 seconds)
Test Case 'RegexTests.testModernComments' started at 2021-12-15 13:23:47.093
Test Case 'RegexTests.testModernComments' passed (0.0 seconds)
Test Case 'RegexTests.testModernQuotes' started at 2021-12-15 13:23:47.093
Test Case 'RegexTests.testModernQuotes' passed (0.001 seconds)
Test Case 'RegexTests.testModernRanges' started at 2021-12-15 13:23:47.094
Test Case 'RegexTests.testModernRanges' passed (0.0 seconds)
Test Case 'RegexTests.testSemanticWhitespace' started at 2021-12-15 13:23:47.094
Test Case 'RegexTests.testSemanticWhitespace' passed (0.001 seconds)
Test Suite 'RegexTests' passed at 2021-12-15 13:23:47.095
         Executed 17 tests, with 0 failures (0 unexpected) in 0.072 (0.072) seconds
Test Suite 'PEGStringTests' started at 2021-12-15 13:23:47.095
Test Case 'PEGStringTests.testCamelCase' started at 2021-12-15 13:23:47.095
Test Case 'PEGStringTests.testCamelCase' passed (0.0 seconds)
Test Case 'PEGStringTests.testCharacterClasses' started at 2021-12-15 13:23:47.095
Test Case 'PEGStringTests.testCharacterClasses' passed (0.006 seconds)
Test Case 'PEGStringTests.testComments' started at 2021-12-15 13:23:47.101
Test Case 'PEGStringTests.testComments' passed (0.005 seconds)
Test Case 'PEGStringTests.testEvenZeroesOnes' started at 2021-12-15 13:23:47.106
Test Case 'PEGStringTests.testEvenZeroesOnes' passed (0.002 seconds)
Test Case 'PEGStringTests.testHappensBefore' started at 2021-12-15 13:23:47.108
Test Case 'PEGStringTests.testHappensBefore' passed (0.0 seconds)
Test Suite 'PEGStringTests' passed at 2021-12-15 13:23:47.108
         Executed 5 tests, with 0 failures (0 unexpected) in 0.013 (0.013) seconds
Test Suite 'MatchingEngineTests' started at 2021-12-15 13:23:47.108
Test Case 'MatchingEngineTests.testAEaters' started at 2021-12-15 13:23:47.108
Test Case 'MatchingEngineTests.testAEaters' passed (0.003 seconds)
Test Suite 'MatchingEngineTests' passed at 2021-12-15 13:23:47.111
         Executed 1 test, with 0 failures (0 unexpected) in 0.003 (0.003) seconds
Test Suite 'RegexDSLTests' started at 2021-12-15 13:23:47.111
Test Case 'RegexDSLTests.testCharacterClasses' started at 2021-12-15 13:23:47.111
Test Case 'RegexDSLTests.testCharacterClasses' passed (0.0 seconds)
Test Case 'RegexDSLTests.testCombinators' started at 2021-12-15 13:23:47.111
Test Case 'RegexDSLTests.testCombinators' passed (0.0 seconds)
Test Case 'RegexDSLTests.testDynamicCaptures' started at 2021-12-15 13:23:47.111
Test Case 'RegexDSLTests.testDynamicCaptures' passed (0.001 seconds)
Test Case 'RegexDSLTests.testGraphemeBreakData' started at 2021-12-15 13:23:47.112
Test Case 'RegexDSLTests.testGraphemeBreakData' passed (0.001 seconds)
Test Case 'RegexDSLTests.testNestedCaptureTypes' started at 2021-12-15 13:23:47.113
Test Case 'RegexDSLTests.testNestedCaptureTypes' passed (0.0 seconds)
Test Case 'RegexDSLTests.testNestedGroups' started at 2021-12-15 13:23:47.113
Test Case 'RegexDSLTests.testNestedGroups' passed (0.001 seconds)
Test Case 'RegexDSLTests.testSimpleStrings' started at 2021-12-15 13:23:47.114
Test Case 'RegexDSLTests.testSimpleStrings' passed (0.0 seconds)
Test Case 'RegexDSLTests.testUnicodeScalarPostProcessing' started at 2021-12-15 13:23:47.114
Test Case 'RegexDSLTests.testUnicodeScalarPostProcessing' passed (0.001 seconds)
Test Suite 'RegexDSLTests' passed at 2021-12-15 13:23:47.115
         Executed 8 tests, with 0 failures (0 unexpected) in 0.004 (0.004) seconds
Test Suite 'debug.xctest' passed at 2021-12-15 13:23:47.115
         Executed 46 tests, with 0 failures (0 unexpected) in 2.858 (2.858) seconds
Test Suite 'All tests' passed at 2021-12-15 13:23:47.115
         Executed 46 tests, with 0 failures (0 unexpected) in 2.858 (2.858) seconds

@swift-ci please test linux

@swift-ci please test linux


Wallet Can't wrap things up..

Android, Note 9. All latest versions as of 28/01/2020
Used wallet, logged in synced all alright, ish.
Once finished with the wallet and I try to close, I'm hit with a white box in the middle of the screen and it says "Wrapping things up.... This can take a while!"
Since the last release, this take longer than my battery can last ( restart phone after an hour) and drains my battery to Zero.
Seems the app can't wrap up and even in the background just drains the battery like crazy. This happens every time I run the wallet.

Seems this might be an issue with lokid itself, we've created a patch to fix it but it won't be released for another 2 days while i wrap up final stuff with session :(

An update has been released, could you let me know if it works?

fixed thanks
On Thu, Feb 6, 2020 at 9:00 AM Mikunj Varsani<EMAIL_ADDRESS>wrote:

An update has been released, could you let me know if it works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/loki-project/loki-android-wallet/issues/27?email_source=notifications&email_token=AKGXGR6EO77YT2BCVVOTEU3RBMZIZA5CNFSM4KMKR5SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK5ESTQ#issuecomment-582633806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKGXGR2MWVPBZVKONFDQE4LRBMZIZANCNFSM4KMKR5SA
.

--


App package env var default version

Can we add a description for the env var which is available when using the default version of an application package (without "#version" postfix)

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

ID: fe76a04d-fca3-b64a-9fdf-b12de26d3d19
Version Independent ID: 9dbb15f3-8665-595d-2322-fb8cdfc0c6e3
Content: Task runtime environment variables - Azure Batch
Content Source: articles/batch/batch-compute-node-environment-variables.md
Service: batch
GitHub Login: @laurenhughes
Microsoft Alias: lahugh

@davidkydd
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


Using nested headers with Tree Table caused "TypeError: Cannot read property 'Header' of undefined"

Is this a general question about implementation, support, api, or anything else?
I don't believe so!
What version of React-Table are you using?
The latest: 6.8.6.
What bug are you experiencing, or what feature are you proposing?
When I add a nested Header for a TreeTable, I get the following error: "TypeError: Cannot read property 'Header' of undefined." To be explicit, if I change
{                   Header: "First Name",                   accessor: "first_name"                 },                 {                   Header: "Last Name",                   accessor: "last_name"                 }
to
{ Header: "Names",               columns: [                 {                   Header: "First Name",                   accessor: "first_name"                 },                 {                   Header: "Last Name",                   accessor: "last_name"                 }               ]             },
the error occurs. In a regular ReactTable, this works fine.
Use https://codesandbox.io/embed/jlkyyj9nr9 (by clicking the "Fork" button) to reproduce the issue.
What are the steps to reproduce the issue?
I provided the steps to reproduce the issue from the Tree Table demo. A simple copy+paste should do. I'm welcome to being told "you're an idiot, here's what you're doing wrong" because I'm new to React and React-Table. :)
Thank you!

This feature/issue has been tagged as one that will likely be fixed or improved in the next major release of React-Table. This release is expected to be completed in the next 6 - 8 months. Please see #1143 for more detail. If you believe this feature can be easily fixed, we invite you to fork the project, attempt the fix, and use it until the latest version is available. If the fix is simple enough, we will also consider it as a PR to the current version.


Container registry

Do we wanna store our built docker images in a container registry?

I think I found them.


Fix race condition with Parquet filter pushdown modifying shared hadoop Configuration

This is https://github.com/NVIDIA/spark-rapids/pull/11672 but against branch 24.10 specifically.

build


使用hive catalog和hive外表报URL using bad/illegal format or missing URL错后，所有be节点挂掉

sr版本2.3.0 release

创建了hive catalog，core-site,hdfs-site等配置文件都已配好，export JAVA_HOME也加进了start_be.sh里。在交互界面简单的查了下hive表，返回rpc failed错误，然后全部be节点都挂掉！
下面是be节点报错日志截图，报错日志只有这两行：

试了下不通过hive catalog查询，而是单独建一张hive外表，也是一样的问题。简单select，然后返回rpc failed错误，然后全部be节点都挂掉！

could you post be.out and coredump file?

which version of JDK you are using, Is it JDK8?

which version of JDK you are using, Is it JDK8? It seems you didn't setup java environment correctly

jkd8，我是参考这个帖子（https://forum.starrocks.com/t/topic/3084）在start_be.sh里加了export java_home，因为不加的话，会报env ‘JAVA_HOME’ is not set的错，不过我刚刚看了下start_be.sh，应该是加错位置了，应该加在73行前面

Is your issue solved after move statement export JAVA_HOME to LOC73.

next time if you encounter any issues, you could ask us on forum directly: https://forum.starrocks.com/

next time if you encounter any issues, you could ask us on forum directly: https://forum.starrocks.com/

之前在论坛里有发表过关于这问题的帖子(https://forum.starrocks.com/t/topic/3236/2)，不过一直没人回复。


[PAGOPA-1800] fix: Update Stamp converter

List of Changes

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Refactored in https://github.com/pagopa/pagopa-debt-position/pull/241


chore(fs12): @leanplum/react-native-sdk v2.0.0

Should we update the docs to let users know what version of LP we are targeting? Or should we always try to target the latest? It might be helpful for people to roll pack to an older version of a plugin.

Correct, we need to generate new docs for the next release after the re-design.


Simplification produces reversed faces

Simplifying this mesh produces output with 1 face reversed.
input wireframe:

output wireframe:

output with backface culling showing 1 reversed face:

Here is the input mesh, and a small repro to make sure the settings for the simplifier are just right.
The repro outputs a reduced.obj which should contains the rogue reversed face.
It should also output the following:
face 27 [18 14 16] is flipped

Duplicate of #346

P.S. Pretty sure it's a duplicate of the issue I linked (same symptom, can be resolved by changing threshold in hasTriangleFlips from 0 to 1e-9 - not a generally correct fix but still), but it's the best repro out of that entire issue by far in terms of being easy to investigate :) Thanks for preparing that!


HDDS-4512. Remove unused netty3 transitive dependency

What changes were proposed in this pull request?
Ozone uses Netty either as direct dependency (ozone-csi) or from the ratis shaded dependency (for ratis gprc server). Both use Netty 4.x.
But netty 3 is also included in share/lib/ozone which is not required. The declared netty 3 version has security issues, we need to remove it to make it clear it's not used. (And make classpath safer)
It turned out that netty (and other dependencies) came with the test-jar dependencies used from Hadoop.
Based on the reference of Maven, compile time dependencies of a test dependency should be used as test dependency (https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) but in this case it doesn't work:
cd hadoop-hdds/container-service
mvn dependency:tree

...
[INFO] +- org.apache.hadoop:hadoop-hdfs:test-jar:tests:3.2.1:test
[INFO] |  +- org.eclipse.jetty:jetty-server:jar:9.4.34.v20201102:test
[INFO] |  |  +- org.eclipse.jetty:jetty-http:jar:9.4.34.v20201102:test
[INFO] |  |  \- org.eclipse.jetty:jetty-io:jar:9.4.34.v20201102:test
[INFO] |  +- org.eclipse.jetty:jetty-util-ajax:jar:9.4.34.v20201102:test
[INFO] |  +- com.sun.jersey:jersey-core:jar:1.19:test
[INFO] |  |  \- javax.ws.rs:jsr311-api:jar:1.1.1:test
[INFO] |  +- com.sun.jersey:jersey-server:jar:1.19:test
[INFO] |  +- commons-cli:commons-cli:jar:1.2:compile
[INFO] |  +- commons-codec:commons-codec:jar:1.11:compile
[INFO] |  +- commons-daemon:commons-daemon:jar:1.0.13:test
[INFO] |  +- javax.servlet:javax.servlet-api:jar:3.1.0:test
[INFO] |  +- io.netty:netty:jar:3.10.5.Final:compile
[INFO] |  +- org.apache.htrace:htrace-core4:jar:4.1.0-incubating:compile
[INFO] |  \- com.fasterxml.jackson.core:jackson-databind:jar:2.10.3:compile
[INFO] \- junit:junit:jar:4.11:test
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
...

Here all the dependencies of the hadop-hdfs:test-jar suppposed to have test scope.
I didn't find the exact MVN issue, but found that there are multiple open issues related to transitive dependency resolution (can be the https://issues.apache.org/jira/browse/MNG-1378, but there are other open issues, too).
As a result, we should remain on the same side. I ssugest:

Exclude ALL the TRANSITIVE test dependencies for hadoop test-jars. Hadoop test-jars can still be used, but if we need any other class, they should be requested with an explicit dependency

hadoop-ozone-dependency-test should be used everywhere instead of using hadoop-hdfs or hadoop-common test jars (because it includes all the required excludes )

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4512
How was this patch tested?
With full CI on the fork. If all the components are started and testable, it supposed to be OK (and it was green)
Also tested with checking the existence of netty3 jar in share/lib/ozone.

Thanks @elek for the improvement and @risdenk for the review.


initial browserify compatible version

some major cleanup and refactoring
removed obsolete stuff that are related to node.js and server-side
promised versions are default in this version

This can't be merged and I have zero idea what is about it. @sinan and @gokmen could you please look at it ?

@tetsuo it's not in a merge-able state right now, can u fix it? and also can u provide more details why do we need this, why are you removing tests, when they are going to be ready, what is our goal with this PR?

And please don't merge it manually either, many files are trashed we may need to keep them. I will talk to @tetsuo first and probably make another pass on this.

see: https://github.com/tetsuo/kite.js/tree/0.5.x


Update design and tidy-up

Code changes

remove Raise hand signal
Avoid duplication with the built-in Raise hand functionality in Google Meet

replace individual button components that had very similar but slightly different logic with one Reaction component where we pass the type and send the appropriate message and emoji

cleanup

Design change
Before

After

How to test

remove extension
build and load local - see https://github.com/alphagov/hand-signals#how-to-test-the-extension-locally

Nice, I think I see some leftover handup stuff in the dist js and the map - but those will be regenerated I guess?

correct

this might constitute a major release ?

I'd vote yes: actual functionality change rather than just appearance changes.


DLL Not Find，I try to Config DLL into X64 or X86,while ,this does not help

DllNotFoundException: SpatialUnderstanding

Can You please provide more info.
Can You find SpatialUnderstanding.dll in project ?

If you have added the DLL into your project, but it still can't be found when you run your app, try deleting the App folder (or whatever you build from unity to), and then restart unity and then do a fresh build.

@nrchuanqi did you resolve this issue?


New Landing Page Layout: Tutorials

Slightly revised content (from what is currently on staging) and inclusion of page content navigation is in the mock-up (PSD - Layer Comp "Tutorials Landing")
** I can see this landing page needing a re-think/update when more tutorials are made available.

Related to what is currently on staging:

[ ] The first paragraph beneath the page title should be styled with slightly larger than body, grey text (mimicking what is found on the docs homepage). Currently, the styling on the docs homepage is inline as style="color:#888888;font-size:1.35rem;line-height:1.9rem;"

looks good on staging


Add gh-pages-android-api workflow

Adds a workflow which downloads the android javadocs from maven and deploys them to the GitHub Pages branch.
The url would be something like https://maplibre.org/maplibre-gl-native/android/api/
You can see a live demo of the Android API at:
https://wipfli.github.io/maplibre-gl-native/android/api/

Hi @wipfli, I see this one triggers manually. Should we trigger it now?

I triggered it and turned on gh pages...


Wrong handling of Instant timestamps

Version: 4.5.0-4.8.5
Module: quill-jdbc
Database: postgres 16.3
Expected behavior
Inserting timestamp of type Instant, to column of type TIMEZONE should store exact Instant value, without introducing timezone offsets
Actual behavior
being e.g. in CET/CEST timezone and
storing
Instant.ofEpochSecond(1L)
stores in DB:
1970-01-01 01:00:01.000000 instead of
1970-01-01 00:00:01.000000
1 hr difference while in CET
storing
Instant.parse("2018-04-08T19:52:29Z")
stores in DB:
2018-04-08 21:52:29.000000 instead of
2018-04-08 19:52:29.000000
2 hr difference while in CEST
Issue introduction
The issue has been introduced here:
https://github.com/zio/zio-quill/commit/8117a0ea257c4cf57f131cf64effd47f323b1b0a#diff-5161e16f0f0a107bd28613fe49aa063e2e7390ec87a61c5a8fd540ca191f67beR83
Workaround
Storing Instants in TIMESTAMP with time zone columns seems to work. But it is very confusing.
Reasoning
Instant type is supposed to be a time-zone agnostic moment in time. The same goes for the TIMESTAMP type in Postgres.
Binding time-zone agnostic type with explicitly time-zone aware TIMESTAMP with time zone type seems to be a mistake.
@getquill/maintainers

Is your JVM running in the CEST tz? JDBC drivers typically pick the current machine timezone, which unfortunately leads to such interactions. In the commit you linked, Instant is converted to a java.sql.Timestamp. There's still an open discussion in pgjdbc about supporting Instant natively, e.g. https://github.com/pgjdbc/pgjdbc/issues/1325#issuecomment-438847217

Thank you @vladimir-lu ! But is it really converted to java.sql.Timestamp? It seems more that it is actually converted to OffsetDateTime in this line https://github.com/zio/zio-quill/commit/8117a0ea257c4cf57f131cf64effd47f323b1b0a#diff-5161e16f0f0a107bd28613fe49aa063e2e7390ec87a61c5a8fd540ca191f67beR101
I also reached the conclusion that I need to have TIMESTAMP WITH TIME ZONE (see Workaround), but it is very disappointing and counter intuitive (see Reasoning)


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

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

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

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

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

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

Update your project to use WithAuthenticationAndAuthorization:

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

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

For further information, suggestions, and guidance:

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

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

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

/cc @sairameshv

@cpmeadors has pointed out that we are using a redhat mirror of this image for the operator-sdk bundle.

ocp version of bundle uses registry.redhat.io/openshift4/ose-kube-rbac-proxy-rhel9

We do not use the gcr image for this.
https://github.com/openshift/instaslice-operator/blob/fd84c947ce76bd6c97847037cdbfada20ac4e570/bundle-ocp/manifests/instaslice-operator.clusterserviceversion.yaml#L256
Looks like we are using the red hat registry image so we should be good for now.

/assign

Hi @kannon92
I see other problem with : https://github.com/openshift/instaslice-operator/issues/291#issuecomment-2517671961
You are not pinning versions.
For example, the auto-generation of certs is deprecated, and this project is alpha.
Therefore, any change introduced in the project risks breaking your old distributions.
The images should always be pinned in some specific version.

/unassign
I'm not sure if I will get to this after all.

Hi @kannon92 ^ I tried simplify the comment above.

https://github.com/openshift/instaslice-operator/pull/338 to pin kube-rbac-proxy for downstream OCP.

/assign


Is there any way to save an email or a ItemAttachment to eml file?

Hello.
I'm looking for the way to handle pst file, XstReader is excellent.
I want to save an email or a ItemAttachment (an attachment which IsEmail is true) to eml file, but I can't find the way.
Is there any method to get whole email's MimeContent?

If you right click on an email in a folder, you can choose Export Email. This will save the body of the email in one of three formats: HTML, RTF or text, depending on the format of the email itself. In all three cases, a mail header is injected above the actual email body. In the case of a pure text email, the result is very close to an .eml file as most implementations interpret it. In the other two cases, you can get to .eml format (which as far as I know, only says anything about pure text files) by converting them to text using open tools, such as a browser or OpenOffice, but of course, this is a very lossy process.
Dijji

thanks a lot!


Make pat::parsing::multi_pat_with_leading_vert public in some form

This is used in the Parse impl for Arm, and would be useful when building custom parsing inside and around match statements.
CC: udoprog/genco#12

This is now available as Pat::parse_multi_with_leading_vert.


Media type strings do not match IANA registry

Similar to #484, many of the media types do not match their representation in the IANA registry, which can make it difficult to handle them generically. Most of the offenders are due to the inclusion of the RFC suffix.

Happy to make the necessary updates here, @jkralik are you open to moving towards matching the IANA registry?

@Danielius1922 I am happy to work on this if you want to assign me 🙂

Sounds alright to me, I've checked our repositories and the only place we use it is in a test. But there might be some hidden code I don't have access to, so we must wait for @jkralik to say if it is alright.

@hasheddan I've talked with @jkralik about this, and we think can remove the RFC suffixes.

@Danielius1922 thanks! Will do shortly 👍🏻


add multi-region round-robin support for Bedrock API calls

Implement support for configuring multiple AWS regions using a single '/'-separated string. Enables easy setup of region failover chain through either config file or environment variable.

Thanks to this elegant framework that significantly simplifies Bedrock API interactions. As a data scientist and consultant at AWS, I frequently encounter API quota limitations in client projects, especially in high-throughput LLM applications. This enhancement adds automatic region failover through a simple '/'-separated string configuration (e.g., "us-west-2/us-east-1"), eliminating the need for complex rotation logic while maintaining backward compatibility with single-region setups.

@rohitprasad15  @ksolo @jeffxtang @andrewyng @johnsanterre @standsleeping
Hello everyone! I would appreciate it if you could review this PR at your convenience~


Error in Tax Form tests

Describe the bug
When executing CI, the Tax Form tests are generating an error.
See for example: https://circleci.com/gh/opencollective/opencollective-api/17389
    sendHelloWorksUsTaxForm
      ✓ updates the documents status to requested when the client request succeeds
Cannot find module 'pg-native'
error: Failed to initialize tax form {"dataValues":{"_salt":"$2b$10$D.AyFHhEgb7kvAFmrByf6O","refresh_token":"$2b$10$QnF7M2otFrrTdqEEmOHAeu","createdAt":"2019-08-06T06:10:29.429Z","updatedAt":"2019-08-06T06:10:29.478Z","newsletterOptIn":false,"id":

This is really strange. I never saw anything like this when I was developing.
There is this issue: https://github.com/sequelize/sequelize/issues/3781 that might be the problem. Has the pg module or something pg related been updated recently?

The first CI run highlighting the error is https://circleci.com/gh/opencollective/opencollective-api/17348 triggered after https://github.com/opencollective/opencollective-api/pull/2351
@Betree any idea?

Found it, I introduced this by logging the user object -- logging sequelize models is usually a bad idea. Pushing a fix now.


Fix typo in unit test

frozen_stages and out_indices assertions are not the same as the assertions in the backbone.
Mis-position of BN and GN.

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


Binding EventEmitter class for custom events

Regarding Streams (bound in ReasonNode.Stream) and them being instances of the EventEmitter class:
How would you handle (emit and on) for custom events?
There are several parser (and other libs) in the node eco-system leveraging custom events. How would you bind those libraries using ReasonNode.Stream? Separate custom binding of on for each?
I understand it's complicated (if even possible) to find a generic solution due to the polymorphism of the EventEmitter class. I'd like to know your thoughts and ideas on this topic.
Thank you both for your huge efforts and amazing work!

Thanks for bringing up this issue, @woeps . As you mentioned in the Discord channel, it is a bit complicated to create generic bindings for EventEmitter. I attempted to write such bindings early on, but it became clear to me that it would be very difficult. I think @sikanhe would agree.
At one point, I started to build a chart of each built-in EventEmitter subclass, the specific events they emitted, and the type signatures of their on and emit functions for each case. I found that in many cases, the arity of those functions was inconsistent. Even for two separate EventEmitter subclasses emitting the same event, they would expect different callback signatures.
There might be a way to implement the on and emit functions using functors to provide the correct type signatures. I'll see if I can come up with an example.
In either case, it might be just as much work for the user to implement their own custom bindings from scratch. But I'm completely open to suggestions.

@woeps Here is an example of how to provide a reasonable API for generating the EventEmitter.on function. I haven't tested it out yet, but it compiles with the current version of this library.
module EventEmitter = {
  module OnEvent = {
    module Impl =
           (
             T: {
               type t;
               type event('a);
               let eventToString: event('a) => string;
             },
           ) => {
<EMAIL_ADDRESS>external on: (T.t, string, 'a) => unit = "on";
      let on: type a b. (T.t, T.event(a => b), a => b) => unit =
        (eventEmitter, event, callback) => {
          let eventString = T.eventToString(event);
          on(eventEmitter, eventString, callback);
        };
    };
  };
};

module MyEmitter = {
  type t = Stream.Readable.t(Buffer.t);
  type data = Buffer.t;
  type event(_) =
    | Data: event(data => unit)
    | Error: event(Js.Exn.t => unit)

  include EventEmitter.OnEvent.Impl({
    type nonrec t = t;
    type nonrec event('a) = event('a);
    let eventToString: type a. event(a) => string =
      fun
      | Data => "data"
      | Error => "error"
  });
};

<EMAIL_ADDRESS>external emitter: MyEmitter.t = "emitter";

let stdout = Process.(stdout(process));

let () =
  MyEmitter.(
    emitter->on(Data, buffer => {Stream.write(stdout, buffer)->ignore})
  );

This allows you to use (GADT) variants as event names, and allows you to implement custom callback type signatures for each event. The final API looks really nice, IMO.
There are downsides to this approach, including runtime performance costs, a minor increase in bundle size, and the usual complexity of using functors and GADT's in your code.
I'm not sure the benefits outweigh the costs here, but it's an option.

This looks pretty nice to me!
It's definitely not a zero-cost binding anymore, that's true. I see why you would be hesitant to include such bindings in this library.
Personally, I'd still use such a binding. It feels good to have the compiler on my team even in this case. I wouldn't worry too much about a recognizable performance hit.
I'm wondering, if it's possible to use Bucklescript's @unboxed feature to get rid of eventToString and just define the event like  | Data("data"): event(Buffer.t => unit).

@woeps Yeah, it would be nice to be able to use @unboxed type as a GADT with multiple variant constructors, but unfortunately, @unboxed only allows us to use a single constructor, which prohibits us from having multiple callback signatures.
As for the extra function call, it's not a huge deal, especially since adding/removing event listeners is rarely performed in a hot path. Even the emit function will not have to serialize/de-serialize anything when it is called.
My main concern is more about scope creep than anything else. We strongly prefer zero-cost bindings where possible, and encourage other library authors to implement "idiomatic Reason" abstractions on top of it.
However, since EventEmitter is such a critical and pervasive class that is sub-classed by a lot of user-land code in the Node ecosystem, it might make sense to make an exception here. @sikanhe may have different views on this, but I think it's worth considering.

For now, I think it would be a good idea to create a PR to experiment with the implementation. Even if we decide not to include it in the final library, it would be nice to have something like this in the ecosystem.

agreed with @austindd A PR is welcome to help us talk about something more concrete

@woeps @sikanhe
Here is an interesting way of accomplishing the same thing with effectively zero-cost bindings:
module EventEmitter = {
  module Impl = (T: {
                   type t;
                   type event('a) = pri string;
                 }) => {
<EMAIL_ADDRESS>    external on: (T.t, T.event('a => 'b<EMAIL_ADDRESS>('a => 'b)) => unit =
      "on";

<EMAIL_ADDRESS>    external off: (T.t, T.event('a => 'b<EMAIL_ADDRESS>('a => 'b)) => unit =
      "off";

<EMAIL_ADDRESS>external emit: (T.t, T.event('a => 'b), 'a) => unit = "emit";
  };
};

module MyEmitter = {
  type t = Stream.Readable.t(Buffer.t);
  type event('a) = pri string;

  let data: event(Buffer.t => unit) = Obj.magic("data");
  let error: event(Js.Exn.t => unit) = Obj.magic("error");

  include EventEmitter.Impl({
    type nonrec t = t;
    type nonrec event('a) = event('a);
  });
};

let (stdin, stdout) = Process.(stdin(process), stdout(process));

let () = {
  MyEmitter.(
    stdin->on(data, buffer => {Stream.write(stdout, buffer)->ignore})
  );
};

As of bs-platform v7.3.1, this compiles to the following JS code:
// Generated by BUCKLESCRIPT, PLEASE EDIT WITH CARE
'use strict';

var Process = require("process");

function Impl(T) {
  return { };
}

var EventEmitter = {
  Impl: Impl
};

var data = "data";

var MyEmitter = {
  data: data,
  error: "error"
};

var stdin = Process.stdin;

var stdout = Process.stdout;

stdin.on(data, (function (buffer) {
        stdout.write(buffer);

      }));

exports.EventEmitter = EventEmitter;
exports.MyEmitter = MyEmitter;
exports.stdin = stdin;
exports.stdout = stdout;
/* stdin Not a pure module */

This approach avoids using GADT variant types, which eliminates the need for (de-)serialization. This should avoid any runtime overhead, aside from the usual functor artifacts in the JS. These artifacts should be compiled away with modern bundlers.
The performance should be roughly equivalent to plain, optimized JS. It may even be faster, since the 'event name' strings are pre-allocated (although V8 might optimize string literals). So I do like this approach.
Issues:

If the user is not expecting to implement an abstract type, then this API might seem a little strange to them. My concern is that the expected design pattern is not immediately obvious without looking at an example or explanation. But the same argument applies to the GADT solution as well.

Any feedback on this is appreciated!

@woeps I am currently in a new branch working on a solution that might eliminate the need for the module functor, and might play nicely with our standard subtyping pattern. So we could potentially model Stream types as subtypes of EventEmitter.

I'd be very interested in your approach. Sounds great so far.

Actually, now that I've though more about it, it seems problematic. The main issue is tracking the types of data that can be passed as arguments to event listeners. The Stream.<Subclass>.t type is a special case of EventEmitter where one or more data types are provided by a type parameter. This is specific to streams and is not possible to generalize across all EventEmitter implementations.
In order to track the types of data that are important to a stream, the event('a => 'b) type would need extra type parameters that correspond the the subclass and it's own type variables, at least if you want any hope of type safety.
Therefore, it seems to me that the only way to make this work is to use a functor to generate the EventEmitter API for a given type t. It's really hard to safely encode polymorphic event emitters & callbacks with this design, which is probably a good thing.
The downside is that we cannot implement it such that streams are considered subtypes of EventEmitter.
If anyone wants to see code examples of what I'm talking about, I could probably come up with minimal versions of the different designs. But trust me when I say that this is inherently tricky.

@woeps I just submitted a PR to add the EventEmitter bindings:
https://github.com/sikanhe/reason-nodejs/pull/30
Feel free to take a look and offer any feedback or concerns.

This should be good to go for the next release. See the code here:
https://github.com/sikanhe/reason-nodejs/blob/release/13.0.0-beta.2/src/EventEmitter.re

#30


Missing attributes in cidaas_app in v3.0.0/3.0.1

Little regression in 3.0.0: The state of cidaas_app doesn't seem to include empty mandatory fields redirect_urls and allowed_logout_urls.
They're not included when showing state with tofu state show. After adding and applying them, they'll keep being shown as unapplied changes.
And while cidaas_user_groups can now be created just fine, the group keeps showing up as changed (with no visible change) even though state and config appear to be identical.
Tested with 3.0.1 also, still applies.

Tujit, thank you for looking into the issues. Today I tried v3.0.2 and it solves the issue regarding empty allowed_logout_urls.
Empty redirect_uris still show up as unapplied changes, same with the cidaas_user_groups.

Hi @joschug , we have released the version 3.0.3 with the required changes. Please try the new build and let us know if it resolves your issues.
We appreciate your patience and thank you for your continued support!

Since we haven’t heard back we’re closing this issue. If you encounter any other issue, please let us know by opening a new one.


Support getitem for type types.

The syntax for an array uses square brackets, for example: int64[:]. Numba currently does not support this syntax within an njitcontext. For example the following will not work:
from numba import njit
from numba.types import int64
from numba.typed import List
import numpy as np

@njit
def foo():
    l = List.empty_list(int64[:])
    l.append(np.zeros(23))
    return l

foo()

And will instead error out with:
Traceback (most recent call last):
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 155, in propagate
    constraint(typeinfer)
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 398, in __call__
    self.fallback(typeinfer)
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 618, in __call__
    self.resolve(typeinfer, typeinfer.typevars, fnty=fnty)
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 515, in resolve
    sig = typeinfer.resolve_call(fnty, pos_args, kw_args)
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 1459, in resolve_call
    return self.context.resolve_function_type(fnty, pos_args, kw_args)
  File "/Users/vhaenel/git/numba/numba/core/typing/context.py", line 214, in resolve_function_type
    raise last_exception
  File "/Users/vhaenel/git/numba/numba/core/typing/context.py", line 197, in resolve_function_type
    res = self._resolve_user_function_type(func, args, kws)
  File "/Users/vhaenel/git/numba/numba/core/typing/context.py", line 249, in _resolve_user_function_type
    return func.get_call_type(self, args, kws)
  File "/Users/vhaenel/git/numba/numba/core/types/functions.py", line 148, in get_call_type
    failures.raise_error()
  File "/Users/vhaenel/git/numba/numba/core/types/functions.py", line 77, in raise_error
    raise errors.TypingError(self.format())
numba.core.errors.TypingError: Invalid use of Function(<built-in function getitem>) with argument(s) of type(s): (class(int64), slice<a:b>)
 * parameterized
In definition 0:
    All templates rejected with literals.
In definition 1:
    All templates rejected without literals.
In definition 2:
    All templates rejected with literals.
In definition 3:
    All templates rejected without literals.
In definition 4:
    All templates rejected with literals.
In definition 5:
    All templates rejected without literals.
In definition 6:
    All templates rejected with literals.
In definition 7:
    All templates rejected without literals.
In definition 8:
    All templates rejected with literals.
In definition 9:
    All templates rejected without literals.
In definition 10:
    All templates rejected with literals.
In definition 11:
    All templates rejected without literals.
In definition 12:
    All templates rejected with literals.
In definition 13:
    All templates rejected without literals.
In definition 14:
    All templates rejected with literals.
In definition 15:
    All templates rejected without literals.
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: typing of intrinsic-call at foo070.py (9)
[2] During: typing of static-get-item at foo070.py (9)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "foo070.py", line 14, in <module>
    foo()
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 401, in _compile_for_args
    error_rewrite(e, 'typing')
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 342, in error_rewrite
    raise e
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 353, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "/Users/vhaenel/git/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 794, in compile
    cres = self._compiler.compile(args, return_type)
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 81, in compile
    raise retval
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 91, in _compile_cached
    retval = self._compile_core(args, return_type)
  File "/Users/vhaenel/git/numba/numba/core/dispatcher.py", line 109, in _compile_core
    pipeline_class=self.pipeline_class)
  File "/Users/vhaenel/git/numba/numba/core/compiler.py", line 568, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/vhaenel/git/numba/numba/core/compiler.py", line 339, in compile_extra
    return self._compile_bytecode()
  File "/Users/vhaenel/git/numba/numba/core/compiler.py", line 401, in _compile_bytecode
    return self._compile_core()
  File "/Users/vhaenel/git/numba/numba/core/compiler.py", line 381, in _compile_core
    raise e
  File "/Users/vhaenel/git/numba/numba/core/compiler.py", line 372, in _compile_core
    pm.run(self.state)
  File "/Users/vhaenel/git/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/vhaenel/git/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/vhaenel/git/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/vhaenel/git/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/vhaenel/git/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/vhaenel/git/numba/numba/core/typed_passes.py", line 98, in run_pass
    raise_errors=self._raise_errors)
  File "/Users/vhaenel/git/numba/numba/core/typed_passes.py", line 70, in type_inference_stage
    infer.propagate(raise_errors=raise_errors)
  File "/Users/vhaenel/git/numba/numba/core/typeinfer.py", line 994, in propagate
    raise errors[0]
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function(<built-in function getitem>) with argument(s) of type(s): (class(int64), slice<a:b>)
 * parameterized
In definition 0:
    All templates rejected with literals.
In definition 1:
    All templates rejected without literals.
In definition 2:
    All templates rejected with literals.
In definition 3:
    All templates rejected without literals.
In definition 4:
    All templates rejected with literals.
In definition 5:
    All templates rejected without literals.
In definition 6:
    All templates rejected with literals.
In definition 7:
    All templates rejected without literals.
In definition 8:
    All templates rejected with literals.
In definition 9:
    All templates rejected without literals.
In definition 10:
    All templates rejected with literals.
In definition 11:
    All templates rejected without literals.
In definition 12:
    All templates rejected with literals.
In definition 13:
    All templates rejected without literals.
In definition 14:
    All templates rejected with literals.
In definition 15:
    All templates rejected without literals.
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: typing of intrinsic-call at foo070.py (9)
[2] During: typing of static-get-item at foo070.py (9)

File "foo070.py", line 9:
def foo():
    l = List.empty_list(int64[:])
    ^

Implementing getitem for type types should resolve this.

Can I work on this?


[BUG] LocalStorage recents limit exceeded

Describe the bug

I got the following error when trying to load a large image library into the dive interface: "quota exceeded error. Failed to execute on setItem on storage: setting the value of desktop.recent exceeded the quota."  This occurred when the images were both stored on my desktop and on a server.

https://github.com/electron/electron/issues/8337
Related data
Need to verify this bug on a huge dataset.
Desktop (please complete the following information):
Unknown
Additional context
Will likely need to evaluate other json key/value storage mechanisms and migrate to one.

This is not an issue anymore.  Thanks @BryonLewis


feat: Add Python runtime specification to Binder

Add a Python 3.10 runtime spec with binder/runtime.txt.

@nsmith- this is ready for review.

@nsmith- I now see that correctionlib is listed as only having support up to Python 3.9
https://github.com/cms-nanoAOD/correctionlib/blob/8d9ec74bb6df2457c522104841ee442d3ea410d1/setup.cfg#L21-L26
Is there anything keeping it from using Python 3.10? Or has this just not been updated?

It builds and runs fine on 3.10, as conformed by the wheel building. I just did not update the setup.cfg

Okay great! I just wanted to make sure I hadn't setup a runtime that would fail. :+1:


[SUPPORT] Still "You exceeded your current quota" after added a new credit balance

My account is out of credit balance.
I added a new credit balance.
When I try to call the API it  still shows You exceeded your current quota

Searched overall, people need to make a new account (why?) or re-create a new API (does not help) or wait for 48 hours (still no luck)
Please fix this ASAP thanks.

Hi! If you're looking for support on our API, please visit the OpenAI help center: https://help.openai.com/en/.


Standardize pushing to Hub in examples

What does this PR do?
Standardise pushing to hub in the examples. Will help #2123.
adds
     # Save and push to hub
     trainer.save_model(training_args.output_dir)
     if training_args.push_to_hub:
         trainer.push_to_hub()

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a GitHub issue? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


change version to gittag

Coverage remained the same at 54.449% when pulling ebbdc7d7473558578af1e338526fb50a4ba91ba6 on wy65701436:dev into 6450b4eb3433f3ba1fa467ecc7fad9dca864fdba on vmware:dev.

Coverage increased (+0.03%) to 54.479% when pulling 4f8174a497948b3ea74ffb15273100bd7fcfbe1a on wy65701436:dev into 6450b4eb3433f3ba1fa467ecc7fad9dca864fdba on vmware:dev.


Disable LZO Compression to mitigate VORACLE

Prevent compression oracle mitm attacks on HTTP data until --tls-version-min 1.3 can be enforced.

Thanks, merged!


Flexible Pricing: Add additional data to Approve dialog and to request table

As a course team member, I'd like to be able to see for what program or course a learner has applied for flexible pricing, and to be able to see (and optionally override) the tier that the learner has been placed in.
Designs and Mockups
The data should be added in two places:

In the list view:

Add a column to the table that displays the current tier/discount. This should be read-only. In the MicroMasters dashboard, this is after Date Calculated:

Add a column to the table that displays the courseware object associated with the request (this will be either a course or a program). I think this should go before the Income column but ultimately it should just make sense.

In the status change dialog:

Add an item with the tier data for the courseware object. This will require a new API; we don't expose the tier data in any way right now. If the status of the request will be Approved, this should be a dropdown that is changeable; otherwise, it should be static. I think this should go above the Justification field (but again am open to suggestions here):

Add a description of the courseware item. This should be at the top of the data elements, I think (around Current Status).

Acceptance Criteria:

[ ] Can see the request's associated courseware object in the Flexible Pricing dash
[ ] Can see the learner's assigned tier in the Flexible Pricing dash
[ ] Can adjust the learner's assigned tier when approving the request

[ ] Resulting approval email reflects the selected tier discount
[ ] Checkout reflects the selected tier discount

[ ] Can see the request's associated courseware object in the status change dialog
[ ] Can see the learner's assigned tier in the status change dialog, but not change it if Denying or Resetting the request

@jkachel @pdpinch I have a few queries about this ticket. Can you please explain a bit more?

Add a column to the table that displays the courseware object associated with the request (this will be either a course or a program). I think this should go before the Income column but ultimately it should just make sense.

I am assuming that we will display the title of Course/Program.

Add a column to the table that displays the current tier/discount. This should be read-only. In the MicroMasters dashboard, this is after Date Calculated.

What do we want to display in this case? Adjusted cost (Will be calculated using product price and discount type etc) OR the discount that is applicable like ($100 off or 10% off etc)?

Add an item with the tier data for the courseware object. This will require a new API; we don't expose the tier data in any way right now. If the status of the request will be Approved, this should be a dropdown that is changeable; otherwise, it should be static. I think this should go above the Justification field (but again am open to suggestions here):

What kind of tier data do we want to display here? I assume it's something similar to the above tier/discount.
Displaying a dropdown when the status is approved. Data for the dropdown? I think we want to display a list of discounts available maybe?

Add a column to the table that displays the courseware object associated with the request (this will be either a course or a program). I think this should go before the Income column but ultimately it should just make sense.
I am assuming that we will display the title of Course/Program.

I think the readable id would be better and take less space, i.e. program-v1:MITxT+DEDP or course-v1:MITxT+14.750x

Add a column to the table that displays the current tier/discount. This should be read-only. In the MicroMasters dashboard, this is after Date Calculated.
What do we want to display in this case? Adjusted cost (Will be calculated using product price and discount type etc) OR the discount that is applicable like ($100 off or 10% off etc)?

I think adjusted cost will be better. Takes up less space, and is less ambiguous. Currently all our flexible price discounts are fixed price discounts. In the future we will like have a percent off. Displaying the adjust cost makes for a nice consistent presentation.

Add an item with the tier data for the courseware object. This will require a new API; we don't expose the tier data in any way right now. If the status of the request will be Approved, this should be a dropdown that is changeable; otherwise, it should be static. I think this should go above the Justification field (but again am open to suggestions here):

What kind of tier data do we want to display here? I assume it's something similar to the above tier/discount.

Again, I think the adjusted cost is most understandable. Take a look at the micromasters implementation for reference:

Displaying a dropdown when the status is approved. Data for the dropdown? I think we want to display a list of discounts available maybe?

same, a list of available adjusted costs.

That makes sense. Will do it this way. Thanks for the details.

Is there a way to fetch the CourseRun || ProgramRun associated with a financial assistance request? Currently, Course/Program is associated with a financial assistance request. I am assuming that we will be having multiple course runs available at a time, so, user can opt for any of the available course runs. Also, course runs can have different pricing.
As per my understanding:

We can have multiple course runs at a time for a course.
Similarily, Product is attached to a Run object. So, we can have multiple prices maybe for multiple course runs of a single course.
FlexiblePrice and FlexiblePriceTier is associated with Course || Program.
So, How do we fetch the CourseRun/Program || Product using FlexiblePrice || FlexiblePriceTier || Discount?

@jkachel Maybe you have a better idea of what I am talking about.
@pdpinch Maybe you can answer as well.

Instead of displaying the adjusted cost (which requires the price from the product), let's display the discount. The discount will be consistent for all courses in the program.


Multiple characters in a label cause a segfault

When I try to use a multiple-character string as a label, I get a segfault.
For example:
import torch
import ctcdecode
labels = ["_", "SIL", "A"]
decoder = ctcdecode.CTCBeamDecoder(labels, blank_id=0)
decoder.decode(torch.randn(3,3,3))

triggers a segfault, whereas
import torch
import ctcdecode
labels = ["_", "A", "B"]
decoder = ctcdecode.CTCBeamDecoder(labels, blank_id=0)
decoder.decode(torch.randn(3,3,3))

does not. Is it possible to do this somehow?

Not today, see #31.


Disassembly view in debugger has inconsistent indenting

The code disassembly panel debugger indents opcodes following an if opcode, but only in the lower part of the listing. It should show consistent behavior.

Released in v1.1.8


java.lang.NoSuchFieldError: No static field Companion of type BoxScope$Companion

Describe the bug
I'm using insets lib and it crashes all the time.
To Reproduce
Steps to reproduce the behavior:

add implementation 'com.google.accompanist:accompanist-insets:0.7.1'
install app and run
crash

Environment:

Android OS version: Android 11
Device: Pixel 3a
Accompanist version: 0.7.1

Additional context
It is okay if I use dev.chrisbanes.accompanist:accompanist-insets:0.6.2

Duplicate of #322


Cannot get Powershell Obfuscation to work.

Empire Version
2.5
OS Information (Linux flavor, Python version)
Kali Rolling x64, Python 2.7
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
Cannot get Powershell Obfuscation to work.
Screenshot of error, embedded text output, or Pastebin link to the error
https://pastebin.com/P74q8ZVr
Any additional information

@re8el what troubleshooting steps have you taken?

Add this line to your ".bashrc"
export TERM=xterm
it should solve the problem

@re8el I'm going to close this for lack of activity.


maint: remove redundant instances of clone() and to_owned()

@andy5995 Sorry for the delay in getting back to you on this. These changes where in the branch 'v0.6.0 api' which has recently been merged with the 'master' branch.


[SPARK-41876][CONNECT][PYTHON] test_dataframe should catch both AnalysisException and SparkConnectAnalysisException

What changes were proposed in this pull request?
When using test_dataframe.py to test spark connect's python API, an error occurs.
Traceback (most recent call last):
  File "/Users/s.singh/personal/spark-oss/python/pyspark/sql/tests/test_dataframe.py", line 1486, in test_to
    self.assertRaisesRegex(
AssertionError: AnalysisException not raised by <lambda>

The root reason is Spark connect covert AnalysisException to SparkConnectAnalysisException.
This PR lets test_dataframe catch both AnalysisException and SparkConnectAnalysisException.
Why are the changes needed?
Lets test_dataframe catch both AnalysisException and SparkConnectAnalysisException.
Does this PR introduce any user-facing change?
'No'.
New feature.
How was this patch tested?
Manual tests.

@HyukjinKwon https://github.com/apache/spark/pull/39693 fixed the issue.


Record each task's maximum memory usage in metrics

We want to record peak memory usage as part of the metrics collected for each task.
The built-in resource library looked like a promising solution, but there were a couple of issues:

It is not included in Windows installations of Python.

It looks like the most detailed statistic that it  can provide is the maximum "Resident Set Size". That includes shared memory such as libraries which may be used by several processes without actually "belonging" to the process whose memory usage we are interested in.

The psutil module can provide more comprehensive information about processes, and it appears to be fairly widely-used. It can report the "Unique Set Size" for a process and its children, which only includes memory dedicated to that process.
This approach should work on Windows/OSX/Linux/etc, but it appears to return values of zero bytes when run within a Windows/Linux subsystem (v1). I wasn't able to find a simpler, more cross-platform approach within a small timebox, but I would be open to suggestions if there are better built-in options.

Does this correlate with the values reported by openroad, yosys, surelog?

It's not an exact match of what the tools report, because this change polls each running process at an interval. But it seems to be very close (on the order of ~1-10MiB difference) for non-trivial designs.
On very small designs, such as the GCD or heartbeat example, each step usually takes less than a second to run. We poll every 0.1+ seconds, so we don't always catch the transient peak. We still see the correct order of magnitude though, e.g. ~35MiB reported vs. ~50MiB actual in yosys.
On longer-running designs, such as ZeroSoc, the results are much better. Taking yosys as an example, we reported ~1.3x memory usage when child processes were included in the psutil accounting. When we only check the main PID, however, we calculate 298.48MiB compared to the 299.88MiB reported in yosys.log. OpenROAD is similar; the main PID's post-routing memory usage is reported as 2162.74MiB, compared to the 2,163.06MiB post-routing peak recorded in route.log.
Considering those results, I've removed child process memory usage from our final tallies. If we can find a way to catch process termination with callbacks rather than polling, we can probably improve the accuracy of results for small designs.

Here are the results from a few trial runs of ZeroSoc, in megabytes. I would include more tasks, but most of them don't currently print utilization statistics to log files:

Step
Memory (reported)
Memory (actual)
Relative error

syn0
296.29
299.16
-0.96%

route0
2140.61
2144.25
-0.17%

syn1
296.5
299.16
-0.89%

route1
2171.12
2171.43
-0.01%

syn2
296.37
299.15
-0.93%

route2
2201.47
2201.79
-0.02%

It looks like this method tends to lowball the statistics by a few megabytes, but the error margin is pretty small, so it should be close enough to gauge how much memory a design requires to build. If we need more precise accuracy, maybe we could investigate wrapping the subprocess commands with a memory profiler such as time or valgrind (may be too slow).

Thanks for going through the exercise of correlating with the tool reporting! This looks fantastic. Just resolve the conflicts and we are good to go.


tts: unstable-2020-06-17 -> 0.0.8

We need to wait until a function model is released: https://github.com/mozilla/TTS/pull/592#issuecomment-766327178
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

umap-learn is also updated here: https://github.com/NixOS/nixpkgs/pull/110688

umap-learn is also updated here: https://github.com/NixOS/nixpkgs/pull/110688


Fix Module Index Server Startup

We can't load a path from a SensitiveString so needed to change the path back to a string

bors merge


Implemented all commands

I implemented all known Rainbird commands in RainbirdController class and covered it by tests.

@jbarrancos Hello, may I ask you for another merge and publish round?
I implemented all known endpoinds, added tests and improved return data

Thx

Done
From: Petr Vraník<EMAIL_ADDRESS>Sent: Monday, 9 September 2019 12:30
To: jbarrancos/pyrainbird<EMAIL_ADDRESS>Cc: Jordy Barrancos<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [jbarrancos/pyrainbird] Implemented all commands (#13)
@jbarrancoshttps://github.com/jbarrancos Hello, may I ask you for another merge and publish round?
I implemented all known endpoinds, added tests and improved return data
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/jbarrancos/pyrainbird/pull/13?email_source=notifications&email_token=AHO4AOFD2JRFT5L32CNQQC3QIYQTFA5CNFSM4IUVAQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6HBTLI#issuecomment-529406381, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHO4AOHBJRM6OOZZQAVIKJTQIYQTFANCNFSM4IUVAQSA.

Great! Thank you.


Error when building BasicDecoder

I am trying to build a pretty simple seq2seq model and I keep getting weird error even though I am following tutorial.
I keep getting ValueError at the decoding stage
ValueError: Could not flatten dictionary. Key had 2 elements, but value had 1 elements. Key: [<tf.Tensor 'decoding/decoder/transpose:0' shape=(70, ?, 128) dtype=float32>, <tf.Tensor 'decoding/decoder/transpose_1:0' shape=(70, ?) dtype=int32>]
Here is my decoder code:
batch_size=70
nodes=128

lstm_dec = tf.contrib.rnn.LSTMCell(nodes)
helper = tf.contrib.seq2seq.TrainingHelper(
    output_embed, output_len, time_major=False, name = "trainHelper"
)
projection_layer = tf.layers.Dense(DICTIONARY_SIZE, name="projection_layer")
# Decoder
decoder = tf.contrib.seq2seq.BasicDecoder(
    lstm_dec,
    helper,
    last_state
)
# Dynamic decoding
outputs, _, _ = tf.contrib.seq2seq.dynamic_decode(decoder)
logits = projection_layer(outputs.rnn_output)

Sadly I couldn't find any explanation for that issue.
The only difference I see is that I am using time_major=False and I tried with time-major data but I got similar error

@Zakkery  were you able to solve this? I am facing a similar issue


Allow swift to be built for iphoneos-armv7s, a variation on armv7,

What's in this pull request?
Allow swift to be configured for iphoneos-armv7s, similar to iphoneos-armv7.  armv7s is a variation on armv7, used in Apple A6 and later 32-bit devices.
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[x] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

used with the Apple A6 and later 32-bit devices.

@swift-ci Please test


Update chart grafana to 8.2.1

This PR contains the following updates:

Package
Update
Change

grafana (source)
patch
8.2.0 -> 8.2.1

Release Notes

grafana/helm-charts (grafana)
v8.2.1
Compare Source
The leading tool for querying and visualizing time series and metrics.
What's Changed

[grafana] Update Grafana to 11.1.0 by @sboulkour in https://github.com/grafana/helm-charts/pull/3191

New Contributors

@sboulkour made their first contribution in https://github.com/grafana/helm-charts/pull/3191

Full Changelog: https://github.com/grafana/helm-charts/compare/grafana-8.2.0...grafana-8.2.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


fix: update unchecked base model to not coerce none

@armandobelardo merging to unblock, but can you follow this up with a unit test?


Rerun skipped

Added button to rerun skipped tests for each group.
I'm not sure if I should fix the launch/patient scope issue (during second launch attempt) in this PR. Let me know if I should.

Let's keep the launch/patient issue separate, as it is independent of this.  Show me that issue when I'm in the office next.

:100 this is awesome.  Much cleaner than I expected it to be!  We probably should add language about how you don't have to have all required Resources within a single launch.  But I think it is probably fairly self evident as-is.  Great job!