Socket hang up behind a proxy

Description
socket hang up error when attempting to install behind a proxy.
Steps to Reproduce
.typingsrc contents:
proxy=http://proxy:9999
rejectUnauthorized=false

command:
typings install dt~angular-protractor --save --global

Expected behavior:
a successful install
Actual behavior:
typings ERR! message Unable to read typings for "angular-protractor". You should check the entry paths in "angular-protractor.d.ts" are up to date
typings ERR! caused by Unable to connect to "https://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/f9c44651705f574f6d4258fe5e1c335462bdcc19/angular-protractor/angular-protractor.d.ts"
typings ERR! caused by socket hang up

typings ERR! system Darwin 14.5.0
typings ERR! command "/usr/local/bin/node" "/usr/local/bin/typings" "install" "dt~angular-protractor" "--save" "--global"
typings ERR! node -v v5.7.0
typings ERR! typings -v 1.0.4

Versions
node -v v5.7.0
typings -v 1.0.4
Thanks for the help!

Full interface definition for typingsrc is at https://github.com/typings/core/blob/master/src/interfaces/rc.ts
Try using JSON format with the added properties, it worked for me, I'm behind a corporate firewall as well.
{
	"strictSSL": false,
        "githubToken": "YourGithubToken"
}

Hi we are also facing the similar issue but instead of Angular we are doing it for react.
Current version of Nodejs is 4.4
and Typings version 1.0.4
Error Stack:
$ typings install 'dt~react-dom' --save --global
typings ERR! message Unable to connect to "https://api.typings.org/entries/dt/react-dom/versions/latest"
typings ERR! caused by socket hang up
typings ERR! cwd G:\workspace4brackets\typscript-0
typings ERR! system Windows_NT 6.1.7601
typings ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\xxx\AppData\Roaming\npm\node_modules\typings\dist\bin.js" "install" "dt~react-dom" "--sav
e" "--global"
typings ERR! node -v v4.4.4
typings ERR! typings -v 1.0.4
typings ERR! code EUNAVAILABLE
typings ERR! If you need help, you may report this error at:
typings ERR!   https://github.com/typings/typings/issues

in your typingsrc file set your registry url to use http rather than https.  Setting a proxy sets both httpProxy and httpProxy.
proxy=http://proxy:9999
rejectUnauthorized=false
registryURL=http://api.typings.org/

The full list of allowed settings in typingsrc is here:

Property
Description

proxy
A HTTP(s) proxy URI for outgoing requests. Setting this sets both httpProxy and httpProxy if they are not set, as this is  used as a fallback variable if both httpProxy and httpProxy.

httpProxy
Any standard http-proxy as supported by the request package. (default: process.env.HTTP_PROXY). For example, "http://<IP_ADDRESS>:8888/" or real proxy from  incloak.com/proxy-list/. If your proxy requires authentication, you may need to include a username and password in your url: "http://domain\\myusername:password@myproxyServer:port", or if you are not on an AD domain: "http://username:mypassword@myProxyServer:port"

httpsProxy
The proxy to use for HTTPS requests (default: process.env.HTTPS_PROXY).

noProxy
A string of space-separated hosts to not proxy (default: process.env.NO_PROXY).

rejectUnauthorized
Reject invalid SSL certificates (default: true). Useful behind (corporate) proxies that act like man-in-the middle on https connections. This setting is passed to the request package to handle connection.

ca
A string or array of strings of trusted certificates in PEM format.

key
Private key to use for SSL.

cert
Public x509 certificate to use.

userAgent
Set the User-Agent for HTTP requests (default: "typings/{typingsVersion} node{nodeVersion} {platform} {arch}").

githubToken
Add your GitHub token for resolving github:* locations. You can create this token on Github.com at https://github.com/settings/tokens/new. The OAuth token can be used to boost the Github API rate-limit from 60 to 5000 (non-cached) requests per hour. This token just needs 'read-only access to public information' so no additional OAuth scopes are necessary. Note: keep in mind the .typingsrc file is not secured. Don't use a token with additional scope unless you know what you are doing.

registryURL
Override the registry URL. (Default: "https://api.typings.org".)

defaultSource
Override the default installation source (E.g. when doing typings install debug) default: npm). Allowed options: file, npm, github, bitbucket, bower, http, or https

I'm also seeing this issue.  My .typingsrc file looks like
httpProxy=http://my.proxy.com:someport
httpsProxy=https://my.proxy.com:adifferentport
rejectUnauthorized=false

I also tried it with just proxy set to either the http or https version.  Node/npm work fine and I also have my proxy environment variables set.

@bensontrent I was able to verify and your comment works
.typingsrc
proxy=http://http.proxy.domain.com:8000 rejectUnauthorized=false registryURL=http://api.typings.org/

I don't know how many hours we've been struggling to make this work behind a corporate proxy and we're still having issues.
.typingsrc
proxy=http://user:pwd@http.proxy.domain.com:8080
rejectUnauthorized=false
registryURL=http://api.typings.org/

This command works fine!
typings search --name react
But this command fails with socket hang up
typings install dt~react
We're getting this message:
typings ERR! message Unable to read typings for "react". You should check the entry paths in "react.d.ts" are up to date
typings ERR! caused by Unable to connect to "https://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/f9117cf5dd3420b4fcb4342bf287945695a953a4/react/react.d.ts"
typings ERR! caused by socket hang up

node -v v6.2.1
typings -v 1.3.3

While you're now able to connect to api.typings.org (via http), it appears you're unable to connect to raw.githubusercontent (via https).  I had the same issue before I adding a github token.
You might try something like this, if you're unsuccessful configuring your certificate authority through your firewall:
.typingsrc file
proxy=http://user:pwd@http.proxy.domain.com:8080
rejectUnauthorized=false
registryURL=http://api.typings.org/
githubToken=YourVeryLongTokenString

Other registries my require you to connect to other domains, I believe those domains can be routed with a .netrc file.  An example .netrc for routing the github.com domain:
.netrc file
# .netrc
## To generate a github token with read only access, see:
## https://help.github.com/articles/creating-an-access-token-for-command-line-use/
machine github.com login <token>

Thanks for spending your time on this bensontrent. However I'm afraid that creating a github token didn't help. Neither using the file _netrc helped me out. (I read that it should be called _netrc on Windows).

I think I have a solution.

Take the url from your error code.
https://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/f9117cf5dd3420b4fcb4342bf287945695a953a4/react/react.d.ts

Remove the s from https.
http://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/f9117cf5dd3420b4fcb4342bf287945695a953a4/react/react.d.ts

Prefix the name of the package to the url.
react=

Take a lock of hair from behind your ear and put it in the knot of a tree, along with a dish rag.  When you are taller than the knot in the tree, you will be cured. (This is actual advice from my whitty dearly departed Tennessean grandmother on curing asthma, and inexplicably my cousin swears it's what cured her) I don't know why this is relevant either.

Put it all together:
typings install react=http://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/f9117cf5dd3420b4fcb4342bf287945695a953a4/react/react.d.ts --save --global

That should circumvent errors thrown by modified certificates when behind a firewall.  Please let your network admin know you are having problems, it's best to use the correct certificate.

Thanks again but I'll put this to rest for a while. I can't even get it to work by removing the s from https. Getting 503 when doing so.
Step 4 would be really good but as you can see from my picture I don't have enough hair on my head to be able to take a lock! Darn! :)
Yes, I think I'll have to convince the network department to put some effort in making life a bit easier for the developers in our company.

@blakeembrey @magwalls's issue could be best addressed with a modification to the way rejectUnauthorized works. The goal being that any call to a https url uses http instead? Or a new setting called strictSSL? I can put together a pull request in the core package.


⚠ ClamAV has degraded performance

In 7c96ca7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 478 ms

Resolved: ClamAV performance has improved in 95fe088.


Documenting all error codes with examples

I am using tryceratops 1.1.0 as a flake8 plugin. Anyways, I am getting quite a few errors, some of which are self-explanatory and some of which aren't. Is it possible to add a section to the docs explaining each error along with examples (i.e. recommended/pass patterns for failure conditions)?
For example, this one is throwing me off TC003 Avoid specifying long messages outside the exception class and I'm not sure exactly what the issue is. Other than that, though, I don't have anywhere to go to get more information to fix the error.
def fn(pattern):
    if not isinstance(pattern, str):
        raise TypeError("pattern must be a string, blah, blah, blah")

The docs with examples on each violation live inside the docs dir. For example, the one you mentioned, it's available here: https://github.com/guilatrova/tryceratops/blob/main/docs/violations/TC003.md
Do you have any ideas on how can we make it more obvious/easy to find for new people?

Gotcha, thanks. I didn't see https://github.com/guilatrova/tryceratops#violations while scrolling through the docs, my bad.


added regions(Taoudénit and Ménaka) to Mali

Added two missing regions, Taoudénit and Ménaka to Mali

Thanks @ibravoh149!


Maybe use concept list from Concepticon after all?

I just checked, and the mapping in etc/concepts seem to be exactly the same as in https://github.com/clld/concepticon-data/blob/master/concepticondata/conceptlists/Zgraggen-1980-380.tsv - except for cases where the concepticon list has received new mappings of so far unmapped concepts.

yes, I agree, @tresoldi can also look into this, as he added the data by then.

Yes -- the concepticon mapping is more likely to be updated and stay up to date, so I think we should prefer those instead of local ones in etc/

removed in https://github.com/lexibank/zgraggenmadang/commit/81d899363efecb57a5e0990f4c9987bcd8bde81e

careful. The curent solution still uses concepts.csv! The rpoblem is that the matches aren't exact, so I had to map both the concepts in concepticon and the ones not there as fallback. So this will destroy the current setting.

I could take of it tomorrow, when I update the code for using the concept lists in nagano and yang. If so, just reopen the issue and assign it to me.

this works in my opinion, but we just need to re-add the conceptlist, if you check my code, that also uses the orthography profile (with zero errors this time).

yes, I just realised that, sorry.

I put back the concept list, but there is now some error in the code where the same form ("aN") is propagated to all entries, I will check right now.

wait please, let me check that I have pushed everything, was perfectly working for me yesterday!

It was running, but you had already pushed with the repeated value: https://github.com/lexibank/zgraggenmadang/commit/2de70de674a3b13cd59b9c52f0903003d81d6cf4
Looking at code now, I am pretty sure it is because add_lexemes is getting counterpart as value, which was the previous code. But I'll wait.

Allright, go ahead, the error was also in my version.

Ah, and important: delete all statements that MAKE tokens manually, we don't need them with the orthography profile. And if the orthoprofile is checked now, make please also sure that

it runs perfectly, without errors, and
no _ is used, but + instead as a morpheme segmentation marker

I am sorry but I don't get what you mean my manual tokenization in my previous code. What I had was reading the COUNTERPART column from the raw data and using self.tokenizer. I suppose the lingpy wordlist would not be necessary if we don't want the automatic cognate judgement anymore, but the tokenization was already done using the profile.
If you refer to the parentheses removal with a regular expression, it is impossible to do so with an orthographic profile (unless, of course, we list all the cases for grammatical notes), because only (a) parentheses at the end of the string, (b) preceded by a space and (c) with a variable number of characters inside should be removed -- all other parentheses are phonological material. This was explained in the comment I had back then.

I've pushed my changes, please check and let me know.

I am sorry but I don't get what you mean my manual tokenization in my previous code. What I had was reading the COUNTERPART column from the raw data and using self.tokenizer. I suppose the lingpy wordlist would not be necessary if we don't want the automatic cognate judgement anymore, but the tokenization was already done using the profile.

This is done automatically, if you only add the counterpart, and you specify an orthography profile. So you do not need to create any tokens "manually", i.e., within your code!

If you refer to the parentheses removal with a regular expression, it is impossible to do so with an orthographic profile (unless, of course, we list all the cases for grammatical notes), because only (a) parentheses at the end of the string, (b) preceded by a space and (c) with a variable number of characters inside should be removed -- all other parentheses are phonological material. This was explained in the comment I had back then.

You know the basic drill of lexibank, right?

value -> form , using functions clean_form and lingpy's clean_string, which also includes a splitting routine, and a stripping of brackets, so you need to override that function
form -> tokens, using the orthography profile

so instead of fiddling in the code itself, you should overwrite the existing functions that turn a value into a form, and that turn a form into tokens.

Had a look. The general problem is that the orthography profile is not used, and that you do not use the internal lexibank functions to clean the string, etc. Things we wanted to avoid.
So the relevant functions to check here are: Dataset.clean_form, see allenbai, where I used that, and also clldutils.text, with strip_brackets, and split_text (or similar). Both offer a wealth of standardized possibilities to handle these cases more consistently. Segments should be procuded from the existing orthoprofile, not from using lingpy's tokenizer.

Ok, I see the point having .add_lexeme() automatically segmenting the values, but how is calling Dataset.tokenizer() a "manual segmentation using lingpy"? Redundant at this point, granted, but isn't it exactly what is called internally?
As for clean_form(), I could follow the standard now, it was not possible before because we needed the clean forms in advance in order to run the automatic cognate judgment analysis. Actually, is not even needed anymore.
Just pushed the new version, please check.

Don't get mad about the use of words I have, please, but I thought it was clear, also if you check all the issues we had int eh past, with the bug-fix I added to modify clean_form, to not produce the form two times, etc., that we no longer clean in an unstandardized way, right? So we should use similar routines, and this is the goal for all lexibank datasets for the new version, specifically in those cases where segmentation is involved.
Exceptions are those datasets which are already segmented, such as cihui, and to some degree allenbai.

Not mad, don't worry, just really puzzled. :wink:
Just please check if it is ok now, so we can close the issue.

Nice, even without lingpy import. Thanks!

Awesome, thanks for slogging through and sorting this out @tresoldi !


feat(styles-migration): add automatic migration for form label class

Preview environments are getting posted here, as soon as they are ready!


Could not load session: 404: Not Found

Steps to reproduce

On a project that uses the "Agile" process adcc42ab-9882-485e-a3ed-7678f01f66bc, create a new estimation session that contains work items.
Open the created session.
Observe the following error:

Analysis
The error looks to be related to the process type. Apparently, for a project with this new "inheritance" model, the extension requests the workitems from two URLs:

https://tfs.example.org/SomeProjectCollection/{SomeGuid}/_apis/wit/workItemTypes
https://tfs.example.org/SomeProjectCollection/_apis/work/processes/adcc42ab-9882-485e-a3ed-7678f01f66bc/workItemTypes

The latter call is not present in older (XML?) based process configurations, and 404s in our "agile" project, probably causing the 404 error.
Additional information
In the original bug report, it was not clear why this was happening in some collections and not in others. @ray-cuadra and I noticed that it might be related to project collections that were upgraded from some prior version to Azure DevOps Server 2020. I previously reported this to MS, but unfortunately, it was closed as "not a bug".
The service is called in the following line: https://github.com/microsoft/azure-boards-estimate/blob/1004739ea32fa6b211aeb82072ca4f8422aa9302/src/services/workItems.ts#L189-L191
Links to prior issues

cschleiden/azure-boards-estimate#86
cschleiden/azure-boards-estimate#156
hangy/azure-boards-estimate#28
Work Item Types - List 404 - Developer Community

Thanks @hangy for a great issue report! We'll dig into this now.

Also having this issue.

Just for the sake of completeness: we're encountering the same problem on Azure DevOps Server 2020 On Premise, but we're using the Hosted-XML templates.

Any update on this issue? @MOlausson

We are also having this issue. let us know if there's useful debug information we can help you collect.

@Robinlievrouw @jmilgie are you also seeing this on xml type processes?

I'm not sure what you mean by this @MOlausson, could you elaborate?

We have had this issue and are just trying to delete/end the old session. Doesn't seem to respond to that request when we use the UI to 'End session." The prompt tells us this is going to affect every user in the session and we proceed. But the session is still there.

Hello. Our team also has this problem since a week ago. We were doing a quick demo of the group-voting-to-estimate process for another team with online/query/Fibonacci options, and now the session tile is stuck. We cannot enter the session with a 404 error, and it won't end from its drop-down menu item, 'End session.' It also affects other sessions we've created since then - we cannot end other sessions from the Estimate frame, but we can end sessions from within the session.

Any update @MOlausson  @AminTi

I'm not sure what you mean by this @MOlausson, could you elaborate?

@Robinlievrouw regarding xml processes I was referring to if the environment you are on are use the old process types or the newer ones (which you can configure in the UI)? We're trying to repro but haven't been able to so looking for clues to in when it's happening. If you can describe your scenario and environment could be helpful.

Having similar issues with this extension.

Websockets fail and the documents list gets a 404.
This a cloud hosted instance of AZDO.

Would it be possible to get an update on the status of this open issue?

Good afternoon.
Please tell me who solved this error? Latest version similarly causes errors
**

{"$id":"1","innerException":null,"message":"%error="1660002";%:The collection does not exist\r\n%error="1660002";%:The collection does not exist","typeName":"Microsoft.VisualStudio.Services.ExtensionManagement.WebApi.DocumentCollectionDoesNotExistException, Microsoft.VisualStudio.Services.ExtensionManagement.WebApi","typeKey":"DocumentCollectionDoesNotExistException","errorCode":0,"eventId":3000}

**
Запросить URL: https://ХХХХХХХХХ/tfs/DefaultCollection/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/estimate/Data/Scopes/Default/Current/Collections/sessions/Documents
Метод запроса: GET
Код статуса: 404 Not Found
Удаленный адрес: ХХ.ХХ.ХХ.ХХХ:443
Правило для URL перехода: strict-origin-when-cross-origin

This has not been fixed.

Good afternoon.
Please tell me who solved this error? Latest version similarly causes errors
**

{"$id":"1","innerException":null,"message":"%error="1660002";%:The collection does not exist\r\n%error="1660002";%:The collection does not exist","typeName":"Microsoft.VisualStudio.Services.ExtensionManagement.WebApi.DocumentCollectionDoesNotExistException, Microsoft.VisualStudio.Services.ExtensionManagement.WebApi","typeKey":"DocumentCollectionDoesNotExistException","errorCode":0,"eventId":3000}

**
Запросить URL: https://ХХХХХХХХХ/tfs/DefaultCollection/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/estimate/Data/Scopes/Default/Current/Collections/sessions/Documents Метод запроса: GET Код статуса: 404 Not Found Удаленный адрес: ХХ.ХХ.ХХ.ХХХ:443 Правило для URL перехода: strict-origin-when-cross-origin

This has not been fixed.

it work as expected for me.

Hi @AminTi ,
I recently installed Estimate on our Azure and OnPrem 2020 collections.
This issue is still appearing on the legacy project created with XML template.
It does not happen with the recently created project.
Any hope to release a fix and work with the legacy APIs ?

@AminTi , I'm also facing same issue- Could not load session: 404: Not Found.
Appreciate if you could help to resolve the issue??

We've been using the tool without issues for over a year with our Azure DevOps Services. We can no longer access sessions, and I get the following console error:

Any updates here? We still cannot use the plugin. I've removed the extension, re-added it, no effect. Just document not found every time I open any session..

We've been having this issue for weeks and we might have just figured it out on our side. Team members of mine would create estimate sessions and title them with date such as "Team A 4/3/2023" or "Sprint 4 - 3/17/23" and it was causing the problem. So I would load up a session and call it "April 3rd" or "Blue team - Mar 31st" and it worked.
We also had previous estimating sessions that were not closed out from before that had the / in them, and we could not open those either. We tested . and - and a few other special characters and determined it was just the / in the title causing problems.
Hope this helps anyone else out there because that is what's solved our issue!

We've been having this issue for weeks and we might have just figured it out on our side. Team members of mine would create estimate sessions and title them with date such as "Team A 4/3/2023" or "Sprint 4 - 3/17/23" and it was causing the problem. So I would load up a session and call it "April 3rd" or "Blue team - Mar 31st" and it worked.
We also had previous estimating sessions that were not closed out from before that had the / in them, and we could not open those either. We tested . and - and a few other special characters and determined it was just the / in the title causing problems.
Hope this helps anyone else out there because that is what's solved our issue!

I see you opened an issue specifically for this.
I can confirm that this is the issue causing our inability to load sessions (we had been naming them based on the date.)

We have this issue for a year now. and look at the comment above. No one @AminTi seems to be worrying about this. Bad service. So we might as well as look for another solution and delete this extension

As of today, we still encounter this issue on Version Azure DevOps Server 2022.0.1 (AzureDevOpsServer_20230602.5). We're also using the legacy XML Process Model until we manage to migrate to inherited

Hi guys, the issue happens when you deleted the query or when the query is private. I created a reset button, the functionality will remove all sessions.

@AminTi is there a roadmap or anything where we can see when this goes live? According to the marketplace, the last update was on the 19th of june and I cannot find anything regarding releases neither on github nor on the marketplace

check now

Still the same

Oh I think I know the issue. Might it be that you only released this fix for Azure DevOps Services, but not for Azure DevOps Server 2022?

just uninstall and install it again

Thank you that worked. Unfortunately, the issue still persists. When trying to open a session on a query or sprint that still uses the old process model, when trying to open the session I get a 404 with the following error

I'm also still getting this issue. Also working with Azure DevOps Server. This only happens in one of the collections of my environment, the other ones seem to work fine.
I have three collections in my organization: Two XML based ones (imported from TFS) (lets call them A and B), and one inherited (created anew on Azure DevOps Server) (lets call it C). Collection B and C work fine, but collection A (any project in it) has the issue.
I am already on the latest version, and tried uninstalling and installing again and it still is not working correctly.


Flickypedia logins are broken

This has been happening since at least 26 June.
When you log in, you get an error:

The application logs have very little detail:
[2024-07-03 11:11:49,383] ERROR in wikimedia: Error exchanging authorization code for token: invalid_request: The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.

I can reproduce the issue by running the app locally with commit ed31a03.
I don’t think any of this code has changed recently, but I’ll roll back to an earlier version to check.

I rolled back to 9e3155f05373dccf5fc457d03fffaf24ca9a55c0 and the issue recurs, which makes me think it's not a code issue.
I rolled back to 17deb0fd66cd3301d73687c5aebae37ca946bd7f, which is 4 months old, and the issue still recurs.

I've logged in as Alexwlchan and found Flickypedia in my list of OAuth consumers (https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/list):

I can't see anything obviously wrong with this, e.g. somebody deliberately revoking or restricting the key.

I've found somebody with a similar error here, but no helpful reply: https://www.mediawiki.org/wiki/Topic:Vk8w5hwrh7kxy9vx

I added some print debugging to auhtlib and got the exact API error message from Wikimedia:
{
  "error": "invalid_request",
  "error_description": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.",
  "hint": "Check the `` parameter",
  "message": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."
}

Helpful!

Another idea: is this an issue with a dependency upgrade with authlib?
Signs point to know: I've tested with 1.1.0, 1.2.0, 1.2.1, 1.3.0 and 1.3.1 and all have the same issue.

I'm using q to try to inspect the responses. This led to another bug: https://github.com/zestyping/q/issues/71

I've tried to follow the authentication flow manually on https://api.wikimedia.org/wiki/Authentication#User_authentication, and I run into the same error.
(I also ran into an issue with those instructions, raised here: https://api.wikimedia.org/wiki/Talk:Authentication#Missing_Content-Type_headers_in_curl_example?)

Okay, so following the authentication flow manually was a useful clue! I ran Flickypedia locally and I was able to isolate the issue.
Here are the steps I followed:

I followed the instructions in the Wikimedia OAuth docs to create an authorization URL:
https://meta.wikimedia.org/w/rest.php/oauth2/authorize?client_id=YOUR_CLIENT_ID&response_type=code

I approved the app, and I was redirected to http://localhost:5000/callback/wikimedia?code=[code]

I tried to request an access token using the instructions in step 2. This failed with an HTTP 415 error:
 $ curl -X POST -F 'grant_type=authorization_code' \
       -F 'code=MY_AUTHORIZATION_CODE' \
       -F 'client_id=CLIENT_ID' \
       -F 'client_secret=CLIENT_SECRET' \
       https://meta.wikimedia.org/w/rest.php/oauth2/access_token | jq .
 {
   "errorKey": "rest-unsupported-content-type",
   "messageTranslations": {
     "en": "Unsupported Content-Type: multipart/form-data"
   },
   "httpCode": 415,
   "httpReason": "Unsupported Media Type"
 }

I looked at the request being sent by Flickypedia in the vcrpy cassettes in the tests. It sends a request with content-type: application/x-www-form-urlencoded. Let's try that instead:
 $ curl -X POST -F 'grant_type=authorization_code' \
       -F 'code=MY_AUTHORIZATION_CODE' \
       -F 'client_id=CLIENT_ID' \
       -F 'client_secret=CLIENT_SECRET' \
       -H 'content-type: x-www-form-urlencoded' \
       https://meta.wikimedia.org/w/rest.php/oauth2/access_token | jq .
 {
   "errorKey": "rest-unsupported-content-type",
   "messageTranslations": {
     "en": "Unsupported Content-Type: multipart/form-data"
   },
   "httpCode": 415,
   "httpReason": "Unsupported Media Type"
 }

How else can I send data with curl? I tried the --data flag:
 $ curl -X POST \
         --data 'grant_type=authorization_code' \
         https://meta.wikimedia.org/w/rest.php/oauth2/access_token | jq .
 {
   "error": "invalid_request",
   "error_description": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.",
   "hint": "Check the `client_id` parameter",
   "message": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."
 }

That gets a similar error message to the one above -- but notice this hint names the client_id parameter, whereas the prior hint didn't name any parameter!

So let's put in all the parameters as a --data argument, and see if that does the trick:
 $ curl -X POST --data 'grant_type=authorization_code&code=MY_AUTHORIZATION_CODE&client_id=CLIENT_ID&client_secret=CLIENT_SECRET' \
       https://meta.wikimedia.org/w/rest.php/oauth2/access_token | jq .
 {
   "token_type": "Bearer",
   "expires_in": 14400,
   "access_token": "ACCESS_TOKEN",
   "refresh_token": "REFRESH_TOKEN"
 }

Success!

So why does Flickypedia fail? Have another look at the test cassette: https://github.com/Flickr-Foundation/flickypedia/blob/b823e908af7c11febc763953b0c1b98286fa5755/tests/fixtures/cassettes/test_can_get_token_from_wikimedia.yml#L3
What's that token_endpoint field doing in there? That's not mentioned in the Wikimedia Commons OAuth documentation.
Let's try it in curl:
 $ curl -X POST \
           --data 'grant_type=authorization_code&token_endpoint=https%3A%2F%2Fmeta.wikimedia.org%2Fw%2Frest.php%2Foauth2%2Faccess_token' \
           https://meta.wikimedia.org/w/rest.php/oauth2/access_token | jq .
 {
   "error": "invalid_request",
   "error_description": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.",
   "hint": "Check the `` parameter",
   "message": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."
 }

And there's the hint with the empty parameter name.

Where's it coming from in Flickypedia?
It comes from this call here: https://github.com/Flickr-Foundation/flickypedia/blob/b823e908af7c11febc763953b0c1b98286fa5755/src/flickypedia/uploadr/auth/wikimedia.py#L419-L423
Any extra parameters to that function are included in the token endpoint body. I'm not sure why token_endpoint_url is included there – it looks like a bug.

So what happened?
I think something has changed in Wikimedia's OAuth implementation.
Previously, it would simply ignore any unrecognised parameters passed to the oauth2/access_token endpoint. I can see this definitely used to work, because we have vcrpy cassettes that pass it and got a successful response.
Now, it takes a stricter approach and rejects any requests that include parameters it isn't expecting. This is probably the more correct thing to do, but the error message it emits is slightly misleading.
Next steps

I'll update Flickypedia to stop passing the unnecessary token_endpoint_url parameter to the oauth2/access_token endpoint.
I'll leave a comment on the OAuth Wikimedia docs about the broken code example.
I'll open a Phabricator ticket about the confusing hint.

I fixed Flickypedia in #479
Comment about the broken docs is here: https://api.wikimedia.org/wiki/Talk:Authentication#curl_command_for_“Get_access_token”_does_not_work
Phabricator ticket is here: https://phabricator.wikimedia.org/T369156

Closing as done.

Actually I'm going to reopen this to cover adding custom error pages.

Closing as actually done now!


The regression forecast result is that there is only one value.

Hello, thanks for your work in the "tft-torch" ! I am facing a problem that using multivariate time series to forecast an univariate time series (similar to the stock dataset). However, I get a bad forecast result when run the model in my dataset, and I don't know what went wrong.
The model config is
data_props = {'num_historical_numeric': input_size,
                  'num_future_numeric': 3,
                  'num_static_numeric': 1,
                  }
configuration = {
        'model':
            {
                'dropout': 0.05,
                'state_size': 64,
                'output_quantiles': [0.1, 0.5, 0.9],
                'lstm_layers': 2,
                'attention_heads': 4
            },
        'task_type': 'regression',
        'target_window_start': None,
        'data_props': data_props
}

I don't have static numeric data, so I set 1.0 for the numeric data.
and the pytorch-lightning code is
class TFTLeaner(pl.LightningModule):
    def __init__(self, model: TemporalFusionTransformer):
        super(TFTLeaner, self).__init__()
        self.model = model
        self.quantiles_tensor = torch.tensor([0.1, 0.5, 0.9])

    def training_step(self, batch, batch_nb):
        outputs = self.model.forward(batch)
        target = batch['target']
        predicted_quantiles = outputs['predicted_quantiles']
        q_loss, q_risk, _ = tft_loss.get_quantiles_loss_and_q_risk(outputs=predicted_quantiles,
                                                                   targets=target,
                                                                   desired_quantiles=self.quantiles_tensor)
        self.log('train_loss', q_loss, prog_bar=True)
        self.log('val_q_risk_0.1', q_risk[0][0], prog_bar=True)
        self.log('val_q_risk_0.5', q_risk[0][1], prog_bar=True)
        self.log('val_q_risk_0.9', q_risk[0][2], prog_bar=True)
        return {'loss': q_loss}

    def validation_step(self, batch, batch_nb):
        outputs = self.model.forward(batch)
        target = batch['target']
        predicted_quantiles = outputs['predicted_quantiles']
        q_loss, q_risk, _ = tft_loss.get_quantiles_loss_and_q_risk(outputs=predicted_quantiles,
                                                                   targets=target,
                                                                   desired_quantiles=self.quantiles_tensor)
        self.log('val_loss', q_loss, prog_bar=True)
        self.log('val_q_risk_0.1', q_risk[0][0], prog_bar=True)
        self.log('val_q_risk_0.5', q_risk[0][1], prog_bar=True)
        self.log('val_q_risk_0.9', q_risk[0][2], prog_bar=True)
        return {'loss': q_loss}

    def test_step(self, batch, batch_idx):
        return self.validation_step(batch, batch_idx)

    def configure_optimizers(self):
        optimizer = torch.optim.Adam(self.model.parameters(), lr=0.01, weight_decay=1e-2)
        scheduler = torch.optim.lr_scheduler.StepLR(optimizer, step_size=10, gamma=0.1)
        return {"optimizer": optimizer, "lr_scheduler": scheduler}

I hope you can solve my problem！

Hello @chooron,
Can you please provide more details regarding:

the expected behavior/outcome
the observed behavior/outcome
Are there any errors that appear? Is there only a mismatch between the expected and observed outcomes?

Are you sure there aren't any static attributes associated with your data/use case?
Just as an example:
If the dataset is composed of time-series data associated with specific entities, you can encode these entities, and these encodings can serve as static (categorical) data (See the examples in the tutorial as a reference).
In the paper this repository is implementing, the static attributes have an essential role as part of the model. Take a look at the Static Covarite Encoding component (both in the paper and in the associated blogpost). They affect the variable selection mechanisms, sequence-to-sequence processing, and representation enrichment.
According to your response, we'll be able to understand if there is a need for a solution that does not require the user in specifying static variables.

Hello @Dvirbeno ,
Thanks for your reply, you can find the dataset in this link, the "historical_numeric" is the ['close', 'high', 'low', 'open'], the "future_numeric" is the ['year','month','dayOfmonth'], the outcome is 'volume', and there aren't any static attributes.

In the case of your dataset, if you would have had records of other stocks, as an example, you could encode the identity of the corresponding stock as a static (categorical) input.
I see that your dataset includes only a single stock. We will work on a solution for cases when there aren't any static inputs.
In the meantime, you can feed the model with a dummy static input, e.g. a tensor of ones (for each element in the batch).
By the way, it seems reasonable to include both ['year','month','dayOfmonth'] and the volume signal as part of the historical time-series as well.

Thanks for your suggestion, I will try to use other stock records, and use the ['year','month','dayOfmonth'] and volume as historical time-series.


Change log level of some messages

Coverage remained the same at 18.027% when pulling 2251687a6e5fbb0fd6b17e35777051bbfc8f1940 on mcanevet:log_level into 00ced1d54ea1c37e0699e9a11f637d50ff61a832 on camptocamp:master.


Introduces markdown output for documentation purposes. Closes #2908

Introduces markdown output for documentation purposes. Closes #2908

Thank you. Will review it shortly

Thank you. Manually merged


Add types to TS

I currently work Vue table lite in TS and present error as it doesn't have types

I currently work Vue table lite in TS and present error as it doesn't have types

OK,  supported on the ver1.0.4, update to ver1.0.4 plz.

I am closing this issue. If you still have problem, reopen the issue.

Where are the type declarations, or how to get them? Installing 1.0.6 doesn't install any type definitions, and npm i --save-dev @types/vue3-table-lite can't find any either. Also tried with 1.0.4 with the same results.

Where are the type declarations, or how to get them? Installing 1.0.6 doesn't install any type definitions, and npm i --save-dev @types/vue3-table-lite can't find any either. Also tried with 1.0.4 with the same results.

If you install it from npm i vue3-table-lite --save-dev, you haven't need any type definitions files.
Because it's already compiled.
So I tried to created a new project and installed it.
$ npm init vite@latest my-vue-app -- --template vue
$ cd my-vue-app
$ npm i vue3-table-lite --save-dev
$ npm run dev

And push import TableLite from "vue3-table-lite"; to App.vue
<template>

  <HelloWorld msg="Hello Vue 3 + Vite" />
  <TableLite />
</template>

It's work good.

Hi, I'm looking forward using this lightweight table, however this issue is still alive.
Using yarn and adding with yarn add -D vue3-table-lite adds it to the devDependencies in package.json but import fails with the same missing types error (using vite as a builder btw). This is with version 1.0.9.

Hi @hspaay
I am created a new typescript project and install vue3-table-lite v1.0.9 by Vite.
I add declare module "vue3-table-lite" to env.d.ts only, and it's good working.
This is my install command and HelloWorld.vue.
$ npm init vite@latest
��� Project name: ��� vite-project
��� Select a framework: ��� vue
��� Select a variant: ��� vue-ts

Scaffolding project in /Users/lin/Sites/vue/vite_pj/vite-project...

Done. Now run:

  cd vite-project
  npm install
  npm run dev

$ cd vite-project
$ npm i vue3-table-lite --save-dev
$ vi src/env.d.ts

Add declare module "vue3-table-lite" to env.d.ts, and edit default HelloWorld.vue
HelloWorld.vue:

<template>

    <TableLite
      :has-checkbox="true"
      :is-loading="table.isLoading"
      :is-re-search="table.isReSearch"
      :columns="table.columns"
      :rows="table.rows"
      :total="table.totalRecordCount"
      :sortable="table.sortable"
      :messages="table.messages"
      @do-search="doSearch"
      @is-finished="tableLoadingFinish"
      @return-checked-rows="updateCheckedRows"
    />

{{ msg }}

    Recommended IDE setup:
    VSCode
    +
    Volar

See README.md for more information.

     Vite Docs
    |
    Vue 3 Docs

  <button type="button" @click="count++">count is: {{ count }}</button>

    Edit
    components/HelloWorld.vue to test hot module replacement.

</template>

Hi @hspaay

Unfortunately it adds approx 120K to the bundle size... probably because the bundle now includes "compiler-core.esm-bundler.js"

I am removed Vue Dependency at bundle, so the bundle will not bundle compiler-core.esm-bundler.js now. Please upgrade to version 1.1.0.

I think this broke non typescript support
I don't use TS in my project and I can no longer build using 1.1.0

I think this broke non typescript support
I don't use TS in my project and I can no longer build using 1.1.0

Hi Alex, Your means you can't build on your TypeScript project on v1.1.0?
...I don't know why, because I use vite created my TypeScript project and install v1.1.0, it's working...

No I don't have a typescript project,
I have a normal javascript project,
which now breaks because I do not have typescript

No I don't have a typescript project, I have a normal javascript project, which now breaks because I do not have typescript

OK...,I know I made a serious mistake, I am changed import file. Can you update to v1.1.2 and try it work or not work on your javascript project?


[STABILITY] - Discover If Test harness Instability is Causing CI Flakiness

What is this task and why do we need to work on it?
Ref: https://github.com/EspressoSystems/HotShot/pull/2716#issuecomment-1984394847

My only concern is: we did have a failure (today) in test_consensus_task: https://github.com/EspressoSystems/HotShot/actions/runs/8192042140/job/22402665222#step:7:1863 and this was non-deterministic (and very rare).

I don't know if the failure is exposing a timing issue in the old test harness (which is fine) or the consensus logic (bad), but I want to suggest we keep the old tests around for a while (especially since we'll be adjusting the log level soon, which should give us a much better idea of why it failed).

I think we could have e.g. test_consensus_task_old, with a comment to delete it once we know why that failure happened, or if the consensus task changes and the test needs to be rewritten or anyway, or a few months have passed without the failure showing up again.

This is an important task as we eventually want to move to the newer testing framework as is it easier to follow and more maintainable. However, until we know the cause of the regressions that we occasionally see in CI, we do not quite want to delete the old tests just yet. The idea here is to figure out if the CI instability is indeed caused by the old test harness.
What work will need to be done to complete this task?
We need to verify what the root cause of the CI failures is, which may be decidedly non-trivial, but a good first step would be to simply check if the problem originates with consensus itself, or with the old testing infrastructure.
Are there any other details to include?
No response
What are the acceptance criteria to close this issue?
We need to find the root cause of the CI problems and then simply delete the code postfixed with old in the test.
Branch work will be merged to (if not the default branch)
No response

I think we can close this one, the old test is removed and I believe the cause of the issue


RE: ngrx/store in feature module

I have a ngrx/sotre in main app.module, also also have a ngrx/store in feature module.
When I try to import the feature module into the app.module, I find that the store in feature module is not being called at all. I have read somewhere that the ngrx/store should only be initialised and used only once per application. If this is the case, I will need to redesign the application.
Thanks for answering me.

For now, ngrx/store is a one-module thing only.
But changes are going to happen. You might want to read this:
https://gist.github.com/MikeRyan52/5d361681ed0c81e38775dd2db15ae202
Also your problem is fully discussed over at #211

Is there any news about this topic?
I would be awesome to be able to use nrgs in different modules

@arangelp #269 provides a solution, it has been merged but the feature is not documented fully nor released.

@abdulhaq-e I checked the ticket #269 but I couldn't find how to proper use the Store in different modules with AOT
Could you provide a short example how to achieve this?

Implemented and released in v4.


Add ability to build SGX SDK when building crates

The vendored feature has been added.  This feature allows for the SDK
to be downloaded and built when the SGX crates are built.

Current dependencies on/for this PR:

develop

PR #36   👈

This comment was auto-generated by Graphite.


Fix ISE when enumerating a call to an aggregate function.

Aggregate functions are not allowed in ROWS FROM (...).
Related #7983

@msullivan the error is generated by postgres for putting aggregate functions in ROWS FROM, where postgres defines aggregate functions as taking a set of inputs.
We do have a few functions which take and return sets, such as assert_exists, but they special case functions and don't end up using process_set_as_func_enumerate.

The SQL generated when doing select enumerate(count((select Person)));:
FROM LATERAL (
    FROM LATERAL (
        FROM LATERAL (
            FROM LATERAL (
                FROM LATERAL (
                    FROM edgedbpub."default::Person" AS "Person~4"
                    SELECT
                        "Person~4".id AS "Person_value~1"
                ) AS "Person~5"
                SELECT
                    "Person~5"."Person_value~1" AS "Person_value~2"
            ) AS "Person~6",
            LATERAL ROWS FROM (count("Person~6"."Person_value~2")) WITH ORDINALITY  AS "f~1"("v~1", _i)
            SELECT
                ("f~1"._i - 1) AS "0_value~1",
                "f~1"."v~1" AS "1_value~1"
        ) AS "q~1"
        SELECT
            "q~1"."0_value~1" AS "0_value~2",
            "q~1"."1_value~1" AS "1_value~2"
    ) AS "expr-11~2"
    SELECT
        "expr-11~2"."0_value~2" AS "0_value~3",
        "expr-11~2"."1_value~2" AS "1_value~3"
) AS "expr-12~2"
SELECT
    (("expr-12~2"."0_value~3", "expr-12~2"."1_value~3"))::edgedbpub."tuple<std|int64, std|int64>_t" AS "tuple_serialized~1"
LIMIT (
    SELECT
        (101)::int8 AS "expr~13_value~1"
)


Could Not Create SSH Tunnel with command

hi,
I have similar or same issue as mentioned in https://github.com/stechstudio/laravel-ssh-tunnel/issues/16 .
Error:
Could Not Create SSH Tunnel with command:
	/usr/bin/ssh -o StrictHostKeyChecking=no  -N -i /home/projectX/.ssh/id_rsa -L 13306:
remoteIP:3306 -p 22<EMAIL_ADDRESS>Check your configuration

  at /home/projectX/laravel/vendor/stechstudio/laravel-ssh-tunnel/src/Jobs/CreateTunnel.php:72
    68|             // Wait a bit until next iteration
    69|             usleep(config('tunneler.wait'));
    70|         }
    71|
  > 72|         throw new \ErrorException(sprintf("Could Not Create SSH Tunnel with command:\n\t%s\nCheck your configuration.",
    73|             $this->sshCommand));
    74|     }
    75|
    76|

  Exception trace:

  1   STS\Tunneler\Jobs\CreateTunnel::handle()
      /home/projectX/laravel/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:32

In https://github.com/stechstudio/laravel-ssh-tunnel/issues/16#issuecomment-365608183  you have mentioned that it is permissions problem. I am running from same user who owns the Laravel project and folder there. I don't know where to look for problem now. Any help would be appreciated. Thanks

Does the SSH tunnel work when you run that command directly?

@V13Axel sorry forgot to mention that. Yes it is working if I run command manually.

I have the same issue.  If I add dispatch(new \STS\Tunneler\Jobs\CreateTunnel()); prior to using the tunnel, I get the above error.. and it obviously never allows the script to go past that point. If however, I go back into the file where that command is and comment it out, and then run it again, then it actually works. So it looks like the tunnel does get created, even though the error is thrown every time
The same script works fine on my dev environment
It is failing on Ubuntu 18.04
If I run the command manually on the production server, then it also works fine without error

Please see my PR here https://github.com/stechstudio/laravel-ssh-tunnel/pull/32
I believe you've run into the same issue as I have which relates to the nc (netcat) command not working with the -z flag alone on newer versions
My PR adds the -vz command which fixes this issue. The other fixes in my PR are also probably needed to remove all errors

This is resolved by the latest release 2.0.0 hot of the press, thanks to @vesper8 .

hey all, i seem to also be having a similar issue here. running on ubuntu 20.04 lts.
Could Not Create SSH Tunnel with command:
        ssh   -N -i /var/www/api/*****.key -L 43306:remote_ip:3306 -p 22<EMAIL_ADDRESS>Check your configuration.

I've checked to make sure I have the latest version pulled, it seems that the tunnel actually does get created when running the command, as I can see it when running netstat -tulpen | grep 43306
tcp        0      0 <IP_ADDRESS>:43306         <IP_ADDRESS>:*               LISTEN      1001       23038      1351/ssh

Also seems to run fine when manually running the ssh command shown in the error.
Permissions seem to be fine. Any ideas?


End the voting once all players vote

closed https://github.com/sopra-fs24-group-12/PeekSeek-server/commit/ca568674e50f397ca21cc9d52718bc0847ea4a43


Revert "Delete System.Threading.Tasks.Channels from corefxlab"

This reverts commit 29db22ae8636cbe83944461a5fa0516799fc91fa.
This is to prepare packages for SignalR (https://github.com/aspnet/SignalR/issues/1060).
cc @stephentoub, @pakrym, @KrzysztofCwalina, @muratg

@ahsonkhan, we now have a copy of the code in corefx and this reverted copy in corefxlab, which will no longer be maintained.  When will you be re-deleting it from here?

we now have a copy of the code in corefx and this reverted copy in corefxlab

I reverted the deletion only for the signalr alpha 2 branch so that I can produce signed packages for their consumption. I did not see the package with these APIs in the latest build on myget.


Question on api_swagger_cors example

I would appreciate some guidance here from anyone who has managed to successfully deploy api_swagger_cors example.
I have replaced both <> and <> as instructed. However, CloudFormation stack creation failed with the following error:
Errors found during import: Unable to put integration on 'ANY' for resource at path '/': Invalid integration URI specified
I'm not sure what this error mean. Much appreciated for your help.

I think it means it can't find your Lambda. I had more luck using inline swagger and referencing my Lambda function with                      Fn::Sub: arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${MyLambdaFunction.Arn}/invocations

There is a bug with the template. It should use !GetAtt instead of !Ref to get ARn of the Lambda function.
I have fixed the template. Can you check now?

I have my SAM template refer to external swagger yaml file. Following the example...
https://github.com/awslabs/serverless-application-model/blob/master/examples/2016-10-31/api_swagger_cors/swagger.yaml#L23
I defined my variable exactly the same way. It didn't work for me. The resulting API for the method shows ${stageVariables.LambdaFunctionName} instead of the actual function name.

Okay, thanks @dimitrovs!
In my subsequent deployment, LambdaFunctionName: !GetAtt notHotdogFunction.Arn in SAM template and ${stageVariables.LambdaFunctionName}/invocations in Swagger definition
seems to have fixed the issue.

hey @jfuss . FYI  It looks like the api_swagger_cors example still has the incorrect swagger and template yaml. https://github.com/awslabs/serverless-application-model/blob/master/examples/2016-10-31/api_swagger_cors/swagger.yaml#L24
there should be an output called LambdaFunctionName in SAM template and ${stageVariables.LambdaFunctionName}/invocations in swagger def as described in the comment.
does your team accept PRs?  I can submit a fix if you'd like

disregard. i saw my issue.  I didn't notice the AWS:Include statement in DefinitionBody
https://github.com/awslabs/serverless-application-model/blob/master/examples/2016-10-31/api_swagger_cors/template.yaml#L15-L20


Install issue on proxmox lxc

The install process was easy and straightforward. I was excited to get started with ambar, but at the very end I received a message in the console
sysctl: cannot stat /proc/sys/net/ipv4/tcp_fin_timeout: No such file or directory
I know lxc containers have an issue running docker (which I was able to get around by modifying the lxc conf file to include some extra parameters. I realize this is probably not the safest practice but the container would only be accessible on a local network. Since I'm still having issues with the container I was hoping to see if anyone had a solution I missed.

Hello @tscibilia ! This line sysctl -w net.ipv4.tcp_fin_timeout=30  was added to tune Ubuntu tcp/ip stack, I think in your case just comment it out in your ambar.py file:
# runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30')

thanks that worked, except i had to comment out a few other errors.
# runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30')
# runShellCommandStrict('sysctl -w net.core.netdev_max_backlog=2000')
# runShellCommandStrict('sysctl -w net.ipv4.tcp_max_syn_backlog=2048')

Nice!


How to download the NEEMS

I read the NEEM-Handbook and followed it instruction to install Hadoop and DVC. However, when i try to download specific episodes using dvc get or dvc pull, it seems that my host can't connect to the hadoop cluster.
how to solve this problem？ Is it only possible to download via the university’s intranet?
The error message as follow:
"INFO ipc.Client: Retrying connect to server: <IP_ADDRESS>/<IP_ADDRESS>:9000. Already tried 15 time(s); maxRetries=45"
"Caused by: java.io.InterruptedIOException: Interrupted while waiting for IO on channel java.nio.channels.SocketChannel[connection-pending remote=<IP_ADDRESS>/<IP_ADDRESS>:9000]. Total timeout mills is 20000, 15242 millis timeout left."
"ERROR: unexpected error - [Errno 255] Opening HDFS file '/neems/ease-2020-pr2-setting-up-table/fe/c13d30d60434f8f1c0ffc4999ead57' failed. Detail: [errno 255] Unknown error 255  "

Hello, I think the better repository for this issue would have been the SOMA repo. I think I resolved the problem with you by sending the files, so I would close this issue here.


[Feature Request] support custom data in Route component and collect them in a hoc.

It looks like this:
// use api to create custom route data with a key.
const data = Route.createData('key', someObject);

<Router>
  <App>
    { /* 'data' is a extra prop for provide the custom data. */ }
    <Route path="/to/some/path1" component={Component1} data={data} />
      ...
    { /* withRouteData is a hoc which provide the wrapped component with the custom data of special keys */ }
    <Route Path="/to/some/path2" component={withRouteData(['key'])(Component2)} />
  </App>
</Router>

If you want to pass extra data to the component rendered for a route, you should use <Route render>.
<Router>
  <App>
    <Route
      path="/to/some/path1"
      render={routeProps => (
        <Component1 {...routeProps} data={data} />
      )}
    />
  </App>
</Router>

@pshrmn Please reopen it. The key is collect data in some where, not provide the data.

@vipcxj based on what you have provided, I do not see this being implemented in core React Router. Maybe it should just exist as a separate package?
If you are really convinced that this is something that should exist in RR, you will need to at the very least write up a few paragraphs describing exactly what abilities the feature should perform and why this cannot be accomplished other ways/why it is better than other approaches. More ideally, you would write a PR to add this functionality yourself, but as I said, I don't think this would be added to core RR, so you should start with the outline.


Option --logging-config crash the decider

Traceback (most recent call last):
  File "bin/caravan-decider", line 14, in <module>
    sys.exit(Command.main())
  File "/opt/python-postalx/local/lib/python2.7/site-packages/caravan/commands/base.py", line 26, in main
    cmd._setup_logging()
  File "/opt/python-postalx/local/lib/python2.7/site-packages/caravan/commands/base.py", line 95, in _setup_logging
    logging.config.fileConfig(self.args.logging_config)
AttributeError: 'module' object has no attribute 'config'

Fixed in 74c77462ff79b2991574a65e42e4806e33331656


Wrong IP address is being populated on an ingress

Using version v0.6.1 mate choses the public ip address of the node instead of the ingress controller alias to populate the route53 address.  I'm using a simple example here:
kops ingress-nginx
and I've changed the ingress yaml in the above example to point to route53 zone instead of foo:
here is the original I changed it to foo.c.tropo.com and bar.c.tropo.com
Here is a snippet from my route53 console
bar.c.tropo.com.  A <IP_ADDRESS> - - 300
bar.c.tropo.com.  TXT "mate:mate-managed" - - 300

default-ingress-nginx.c.tropo.com.  A ALIAS ac2f3241cffbc11e6bab612aafb8d2fa-1674343966.us-east-1.elb.amazonaws.com. (z35sxdotrq7x7k) Yes -
default-ingress-nginx.c.tropo.com.  TXT "mate:mate-managed" - - 300

foo.c.tropo.com.  A <IP_ADDRESS> - - 300
foo.c.tropo.com.  TXT "mate:mate-managed" - - 300

Here is the snippet from the mate container:
time="2017-03-03T03:10:20Z" level=info msg="ADDED: default/echomap"
time="2017-03-03T03:10:20Z" level=warning msg="[Ingress] The load balancer of ingress 'default/echomap' does not have any ingress."
time="2017-03-03T03:10:20Z" level=info msg="MODIFIED: default/echomap"
time="2017-03-03T03:10:20Z" level=info msg="[AWS] Processing (foo.c.tropo.com., <IP_ADDRESS>, )\n"
time="2017-03-03T03:10:20Z" level=info msg="[AWS] Processing (bar.c.tropo.com., <IP_ADDRESS>, )\n"
time="2017-03-03T03:10:44Z" level=info msg="[Synchronize] Synchronizing DNS entries..."

I setup the mate deployment to look like below, only change I put in was  I put the annotation to use a specific policy role that I created:
/work/Official/kops-installs/mate$ cat mate-deployment.yml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: mate
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: mate
      annotations:
        iam.amazonaws.com/role: mate-route53-role
    spec:
      containers:
      - name: mate
        image: registry.opensource.zalan.do/teapot/mate:v0.6.1
        env:
        - name: AWS_REGION
          value: us-east-1
        args:
        - --producer=kubernetes
        - --kubernetes-format={{.Namespace}}-{{.Name}}.c.tropo.com
        - --consumer=aws
        - --aws-record-group-id=mate-managed

Here are my two mate policies basically i'm trying to limit mate to just two zoneid's
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1488504089000",
            "Effect": "Allow",
            "Action": [
                "route53:ChangeResourceRecordSets"
            ],
            "Resource": [
                "arn:aws:route53::::hostedzone/ZVO7JZ181S8PP"
            ]
        },
        {
            "Sid": "Stmt1488504193000",
            "Effect": "Allow",
            "Action": [
                "route53:ChangeResourceRecordSets"
            ],
            "Resource": [
                "arn:aws:route53::::hostedzone/Z1N71K8UHPS27L"
            ]
        },
        {
            "Sid": "Stmt1488504240000",
            "Effect": "Allow",
            "Action": [
                "route53:GetChange"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

and the elb policy
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1488504551000",
            "Effect": "Allow",
            "Action": [
                "elasticloadbalancing:*"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

could you please do
kubectl get -o yaml ingress echomap

Looks strange...
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: '{"kind":"Ingress","apiVersion":"extensions/v1beta1","metadata":{"name":"echomap","creationTimestamp":null},"spec":{"rules":[{"host":"foo.c.tropo.com","http":{"paths":[{"path":"/foo","backend":{"serviceName":"echoheaders-x","servicePort":80}}]}},{"host":"bar.c.tropo.com","http":{"paths":[{"path":"/bar","backend":{"serviceName":"echoheaders-y","servicePort":80}},{"path":"/foo","backend":{"serviceName":"echoheaders-x","servicePort":80}}]}}]},"status":{"loadBalancer":{}}}'
  creationTimestamp: 2017-03-03T03:10:20Z
  generation: 1
  name: echomap
  namespace: default
  resourceVersion: "23478101"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/echomap
  uid: ef2ca658-ffbe-11e6-bab6-12aafb8d2fa6
spec:
  rules:
  - host: foo.c.tropo.com
    http:
      paths:
      - backend:
          serviceName: echoheaders-x
          servicePort: 80
        path: /foo
  - host: bar.c.tropo.com
    http:
      paths:
      - backend:
          serviceName: echoheaders-y
          servicePort: 80
        path: /bar
      - backend:
          serviceName: echoheaders-x
          servicePort: 80
        path: /foo
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>

@snoby we already discussed this issue previously here: https://github.com/zalando-incubator/mate/issues/85
As mentioned in the issue, Mate does its job integrating with ingress-controllers by reading whatever loadBalancervalue is provided by ingress resource, and that's where Mate's responsibility ends. You can also find some more useful information in the above mentioned issue link. Closing this issue

@snoby mate doesn't modify the Ingress object, so it's your ingress controller putting the "wrong" IP there. Are you using the nginx-ingress-controller?

Yes I am.  I guess I need to find a way to make the nginx-ingress-controller put the right dns alias in that field.  Honestly I suspect 80% of the people using k8s are going to be using nginx-ingress controller.

@snoby @ideahitme I did some digging and have good news.
https://github.com/kubernetes/ingress/tree/master/examples/static-ip/nginx#acquiring-an-ip perfectly describes our issue. They mention to put a Type=LoadBalancer in front of the nginx controller to get an ELB for it. In this case one should pass the --publish-service flag to nginx-controller so that:
--publish-service string

Service fronting the ingress controllers. Takes the form
namespace/name. The controller will set the endpoint records on the
ingress objects to reflect those on the service.

This flag only exists in the non-released 0.9 version of nginx-controller. https://github.com/kubernetes/ingress/tree/master/examples/static-ip/nginx has the corresponding manifest files.
However, I also found https://github.com/kubernetes/kops/tree/master/addons/ingress-nginx#creating-a-simple-ingress where the Ingress clearly receives the DNS name of the exposed ELB. Though, looking at the manifests they seem to use 0.8.3 and also put a service in front of the controller. So, I guess it also somehow works with this version. Maybe it discovers the service by a hardcoded name and in 0.9 the name is just configurable?
@snoby You want to give 0.9 pointing it to your service a try?

@linki
I did some playing around with this today and discovered a couple of things:

in the 0.9.0-beta.2 release of the nginx ingress controller they changed the argument to the binary from --nginx-configmaps to just --configmaps.
2.) I added to  my service annotation :
service.beta.kubernetes.io/external-traffic: OnlyLocal

Everything looks correct and MATE correctly sets the ip address to the ELB alias now!, unfortunately this is definitely a beta because the health check in the ELB suggests that none of my nodes were in service.
All that being said @linki 's suggestion was correct.  Here is my updated ingress:
kind: Service
apiVersion: v1
metadata:
  name: nginx-default-backend
  namespace: default
  labels:
    k8s-addon: ingress-nginx.addons.k8s.io
spec:
  ports:
  - port: 80
    targetPort: http
  selector:
    app: nginx-default-backend

---

kind: Deployment
apiVersion: extensions/v1beta1
metadata:
  name: nginx-default-backend
  labels:
    k8s-addon: ingress-nginx.addons.k8s.io
spec:
  replicas: 1
  template:
    metadata:
      labels:
        k8s-addon: ingress-nginx.addons.k8s.io
        app: nginx-default-backend
    spec:
      terminationGracePeriodSeconds: 60
      containers:
      - name: default-http-backend
        image: gcr.io/google_containers/defaultbackend:1.0
        livenessProbe:
          httpGet:
            path: /healthz
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 30
          timeoutSeconds: 5
        resources:
          limits:
            cpu: 10m
            memory: 20Mi
          requests:
            cpu: 10m
            memory: 20Mi
        ports:
        - name: http
          containerPort: 8080
          protocol: TCP

---

kind: ConfigMap
apiVersion: v1
metadata:
  name: ingress-nginx
  namespace: default
  labels:
    k8s-addon: ingress-nginx.addons.k8s.io
data:
  use-proxy-protocol: 'true'
  enable-sticky-sessions: 'true'
  enale-vts-status: 'true'

---
#
# must include external-traffic: OnlyLocal to preserve the source ip address and so that
# the load balancer Ip address will be set instead of the node ip address.
#
kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx
  labels:
    k8s-addon: ingress-nginx.addons.k8s.io
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: '*'
    service.beta.kubernetes.io/external-traffic: OnlyLocal
spec:
  type: LoadBalancer
  selector:
    app: ingress-nginx
  ports:
  - name: http
    port: 80
    targetPort: http
  - name: https
    port: 443
    targetPort: https

Follow up to the previous post.  I have it all working now,
DO NOT USE the  OnlyLocal annotation.  So take out the above line:
service.beta.kubernetes.io/external-traffic: OnlyLocal

@snoby it would be awesome to have this use-case documented in the mate readme files. If you wish to do so, please let us know and kindly create a PR. Otherwise, me or @linki will do that 👍

I will put something together and submit a PR,
Thanks for your help!


adding network

am unable to add node network or connect with the current one to activate staking of MIOTA
kindly help me wih the issue as soon as possible

If you are using a Developer profile and are connected to the "Chrysalis testnet" do this;
Do not use developer profiles in the Firefly Wallet if you are not a Developer. A developer Profile will connect you to the Testnet and generate addresses that do not work on IOTA Mainnet. These testnet addresses start with "atoi1" instead of the mainnet addresses "iota1".
If you have accidentally created a developer profile and did send funds to an "atoi1" address you have not lost your funds.
To make these funds accessible you need to use the "recover a wallet" function in Firefly while creating a new profile.
Create a "non developer" profile and use the 24 words that you have saved from your "developer profile" to restore this new profile (non developer).
Your funds will show up in this new profile.
If you only have issues with the mainnet network, change node by doing the following;
Settings -> Network config -> Manual -> add https://mainnet-node.tanglebay.com/ as a node and set it as primary.

Am having issue with mainnet not developer testnet,I can't add the network

Anything I want to change node it will tell me something went wrong

Are you trying to migrate?
If so, download the 1.2.0 version and use that.
also can you check menu -> firefly -> error log and see what errors you have?
cannot see the screenshot.

Am not trying to migrate am trying to add the network node:
https://mainnet-node.tanglebay.com/ but I always received this error message: SOMETHING WENT WRONG
And the error I sent the screenshot above

Hmm, are you using a work PC or maybe a PC with some strict firewall/VPN?
Looks like it is not allowing outgoing calls.

Please how can I disable that

How is node network connected with outgoing calls boss?

Not allowing outgoing calls is that the issue

Yes. You need to make sure that you have a proper connection to the node

Can you please help me with at least the correct settings of firewall

I´m sorry but I don´t know which firewall you have.

What other software should I disable for me to be able to stop receiving "something went wrong"  if I want to add node

Aside from firewall

Antivirus

Ok but I don't use antivirus
Any other one

Please join the IOTA Discord server (https://discord.iota.org/) and go to the #help channel. Otherwise it would be difficult to help you with this issue.

I can't join discord it keeps telling me am using vpn and vpn is not
allowed there
And I did not use vpn
On Tue, Dec 28, 2021, 5:08 PM MiKeF05 @.***> wrote:

Please join the IOTA Discord server (https://discord.iota.org/) and go to
the #help channel. Otherwise it would be difficult to help you with this
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/iotaledger/firefly/issues/1922#issuecomment-1002176479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AURNLM5JMXWF2Q3CKO7P4OLUTHOHNANCNFSM5K4ANCRQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Everything about this project AIRDROP is so stressful
On Tue, Dec 28, 2021, 5:14 PM Olatuyi Tony @.***> wrote:

I can't join discord it keeps telling me am using vpn and vpn is not
allowed there
And I did not use vpn
On Tue, Dec 28, 2021, 5:08 PM MiKeF05 @.***> wrote:

Please join the IOTA Discord server (https://discord.iota.org/) and go
to the #help channel. Otherwise it would be difficult to help you with this
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/iotaledger/firefly/issues/1922#issuecomment-1002176479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AURNLM5JMXWF2Q3CKO7P4OLUTHOHNANCNFSM5K4ANCRQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Something with your internet connection is really weird. You need to figure this out. But I can´t help you with this issue as it is not related to Firefly.

@Olatuyitony347 what is your Discord username?

@rajivshah3  Olatuyitony347#0136 is my discord username

Hi . i have the same problem. giorgica#3883 discord username.
maybe you can olso help me.

@Olatuyitony347 fixed ✅
@giorgica can you please try rejoining again and then make sure you respond to the DM from the bot?

@rajivshah3 What was the issue for Olatuyitony?

Ah I probably should have clarified — he's able to access the Discord server now. The bot was blocking him for some reason

i am here. i dont have message on discord

@giorgica please try rejoining the Discord server by clicking here

Duplicate issue.


News sources: European Union

I'd like to compile a feed for all the EU countries. I'm choosing EU, since there is an official boundary of which countries are considered in EU, opposed to Europe, where one can argue that a country is in Europe or outside of it.

https://www.euronews.com/rss

most big outlets have 'europe' section that we can leverage...
    "https://www.lemonde.fr/europe/rss_full.xml",
    "https://www.spiegel.de/international/europe/index.rss",
    "https://www.politico.eu/feed/",
    "https://rss.nytimes.com/services/xml/rss/nyt/Europe.xml",
    "http://feeds.bbci.co.uk/news/world/europe/rss.xml",
    "https://www.euronews.com/rss?level=program&name=europe-news",
    "https://www.ft.com/world/europe?format=rss",
    "https://www.economist.com/europe/rss.xml",
    "https://feeds.npr.org/1124/rss.xml",
    "https://www.euronews.com/rss?level=vertical&name=my-europe",
    "https://www.scmp.com/rss/322263/feed",

[
  "https://officialblogofunio.com/feed/",
  "https://ecipe.org/blog/feed/",
  "https://www.express.co.uk/latest/european-union/rss",
  "https://www.nytimes.com/svc/collections/v1/publish/https://www.nytimes.com/topic/organization/european-union/rss.xml",
  "http://eulawanalysis.blogspot.com/feeds/posts/default",
  "https://ecfr.eu/feed/",
  "https://www.euractiv.com/feed/"
]

[
  "https://www.reddit.com/r/europe/.rss",
  "https://www.reddit.com/r/europes/.rss",
  "https://www.reddit.com/r/esa/.rss",
  "https://www.reddit.com/r/europeanparliament/.rss",
  "https://www.reddit.com/r/europeanunion/.rss",
  "https://www.reddit.com/r/EuropeanFederalists/.rss",
  "https://news.google.com/rss/topics/CAAqIQgKIhtDQkFTRGdvSUwyMHZNREpxT1hvU0FtVnVLQUFQAQ?hl=en-US&gl=US&ceid=US%3Aen&oc=11",
  "https://news.google.com/rss/topics/CAAqJAgKIh5DQkFTRUFvS0wyMHZNRjgyZEY5Nk9CSUNaVzRvQUFQAQ?hl=en-US&gl=US&ceid=US%3Aen&oc=11"
]


bug(extensions): emoji extension not opening on Linux

The extension is detected by uplink and the button appears but clicking the emoji button doesn't open the menu.
edit: doesn't work on Mac either

it's back to working again.

I think I figured it out - seems that if i cargo build --package emoji_selector then it doesn't work. but if i cargo build to make everything at once, then it works.

I think I figured it out - seems that if i cargo build --package emoji_selector then it doesn't work. but if i cargo build to make everything at once, then it works.

Interesting. Does building in the crate directory not work either?

i'm not sure but I assume so since specifying --package causes all the dependencies used by that package to be re-built.


Small code optmizations.

Thank you for the suggestion. I appreciate it. :)
I noticed that you replace string with vars. Vars shouldn't be overused for simple types and if you value readability. :)

Done.

@brunao05 Merged your changes. Thank you.
Can you please email me your full name and blog site so I can include you in the contributor list? Thanks!

Sure thing

Cool!
If you don't mind, can you star the repo to show support. :)
Send your name and blog link if you have here: vmsdurano at gmail dot com. Thanks!


Form with one field - submit issue

Submit event is getting triggered on Enter key press even when submit button is in disabled state (disabled="disabled")
This happens only when form has one input field.
In Safari 9x and IE 11, submit action is getting triggered on Enter key press. In chrome it works fine
plnkr.co/edit/l9UURtqV43JBoTqBEJ5J?p=preview

This is normal behaviour for forms with a single field. It's detailed in the html specifications. Google will return quite a few people asking a similar question, along with a few different solutions.
One possible solution is to add a second, hidden, input field.
As this isn't specifically a formly issue, I'm going to close this. If you have any more questions, someone should be able to help out

I agree .. Form submit trigger even on disabled submit button is part of html specification.
Is that possible for formly to catch that submit event and evaluate all the formly fields are valid or not before triggering associated submit function.
In my example, i have attached length validation to first name field.

  			  lengthValidation: function($viewValue, $modelValue, scope) {
  			    if ($viewValue.length > 3) {
  			      return true ;
  			    }

  			    return false;
  			  }

Sure. I use form.$valid before submit.
Either in the controller
vm.doSubmit = function() {
        if (vm.form.$valid) {
          alert('Submit');
        }
};

or in the template
<formly-form ng-submit="vm.form.$valid && vm.doSubmit()"></formly-form>

Is this not a good feature to have in Formly instead of adding $valid check or adding hidden field manually ?

If this is really part of the specification, it's odd and unexpected. In formly we often do things that abstract away the unexpected parts of the specification. So I think a PR to abstract this away would be acceptable. My thinking is to add a hidden field if there's only one field in fields. Could easily accomplish this in the formly-form template right above this line:
<input type="hidden" />

I'm thinking that should do it. Any pull request should accompany tests. makeapullrequest.com :-)

Might be worth pointing out what the specification says about implicit form submission.
The angular docs also talk a bit about form submission and the HTML specification.

Hmmm... I suppose that this might be expected behavior on the part of users. Maybe it's better for the developer to be explicit about how they solve this problem rather than just doing it ourselves.

I just a had a quick search through the angular github and found angular/angular.js#3205
I'm not sure of an alternative to what I've already suggested sorry...

As you said "In formly we often do things that abstract away the unexpected parts of the specification", i think its worth putting it as part of formly form options.

preventSingleFieldInvalidFormSubmit=true or false(default...normal behavior)

Actually, I'm pretty confident that the API for formly is already too big. You could easily accomplish this with a field transform: https://jsbin.com/yinuda/edit?js,output
app.run(function(formlyConfig) {
  formlyConfig.extras.fieldTransform.push(fieldTransform)

  function fieldTransform(fields) {
    return fields.concat({
      type: 'input',
      templateOptions: {
        type: 'hidden'
      },
      hideExpression: 'fields.length !== 2' // where 2 === this one plus one another.
    })
  }
})

If you'd like, you can create a plugin for this and I'll add it to the plugins list

Neat generic solution.  :clap: :clap: :clap:
But adding hidden field is not solving this problem in Safari 9x.
http://plnkr.co/edit/x7scTQuTz4Qu0iwCgCn7?p=preview
I know this is nothing to do with Formly anyway.


Add security related headers to build.servo.org

Add some headers to build.servo.org to improve our Mozilla Observatory
score. The helps the cause of #473, by raising our score from F (0) to a
whopping B- (65). The testing is still basic, the docker-observatory
based testing will go in a different PR.
To get to an A+ we must first implement https.
This is the local observatory report:
Score Rule                       Description
-20 redirection                Does not redirect to an https site.
-20 strict-transport-security  HTTP Strict Transport Security (HSTS)
header cannot be set for sites not available over https.
-5 contribute                 Contribute.json file missing from root
of website.
5 content-security-policy    Content Security Policy (CSP)
implemented without 'unsafe-inline' or 'unsafe-eval'.
5 x-frame-options            X-Frame-Options (XFO) implemented via
the CSP frame-ancestors directive.
Score: 65
Grade: B-

This change is

Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @aneeshusa (or someone else) soon.

@jarondl Can you point me to some documentation about the contribute.json file? I haven't heard of this and didn't see it on the observatory results.

Yes, http://contribute.json/  is quite obscure. I have found about it only when I've browsed through the observatory code to resolve some bug.
According to the observatory, only Mozilla related websites must have it, see for example:
https://observatory.mozilla.org/analyze.html?host=mozilla.org

The list of mozilla related sites is hard coded here: https://github.com/mozilla/http-observatory/blob/7dd04ff5b51e39698a8b683df33ef430b4ed4213/httpobs/conf/httpobs.conf#L33
and servo is not there, but in all fairness it should be. We should submit a PR to add it, and degrade us from 70 to 65.

I believe the tests have failed because buildbot is down in travis. We can circumvent this by letting nginx serve 200 on some page (say http://buildbot.servo.org/generate200/ ), but I don't really like this solution. We should have something more similar to real life. Also, we plan to use the observatory, and it also check the contents of the page.
@aneeshusa, could you explain why buildbot and homu don't work during testing? Is there anything we can do about that?

Buildbot immediately stops on Travis after being started (due to our fake test credentials not validating IIRC), which I don't have an easy fix for. In the meantime, I believe this is why I added the make_cors_request function in #375, since Nginx should still add the headers even though the status code indicates error (since Buildbot is down). Try adding/using that in this test.

Also, please open a separate issue about contribute.json to keep this PR about headers.

Hi @aneeshusa , thanks for reviewing, I will work on it.


Support ecma part 2

a follow up to #1
Essentially cut over the the webpack loader to use ES6 Modules with working tests. Added a circle ci job to test to kick off on code pushes. README is updated to accurately reflect usage and requirements as well as package.json
Eventually I will make a PR to get this as a feature in the original library via a flag.
~I am also starting with a beta canary on publish (once I have access) to test functionality outside npm link~ . We will be referencing this in the webapp via a tag on master

If the original library rejects the pr, will we just need to patch any updates that we want to apply
to ejs-loader ourselves?

@electrachong unfortunately yes, but hopefully we can avoid that and not maintain this fork long term. Hopefully they will accept the change 😄

my contributions are just typos and spell check :P

Thank you as always for being my spellchecker 😆

@electrachong spelling errors should now be fixed 😄

@jessewagstaff @electrachong @al-the-x @racoleman the changes needed here were implemented upstream. We likely don't need this fork anymore and can just use ejs-loader version 0.4.1 🎉 .
From https://github.com/groveco/grove/pull/9160

I am now a contributor on ejs-loader and ES6 modules PR was merged 🎉 . update the webpack options parsing was closed due to some of the commits being included in the ES6 modules PR. However, the default options commit was missing, which was merged in right after

ES6 modules was included in version 0.4.0 and default options commit was included in version 0.4.1. The webapp now has both 😄 .


Switch to yarn

(This one is really easy to approve...)

RIP, @TheSonAlsoRises 's review doesn't count :-P

Ok, I have updated this to include installation instructions and include the commands for both yarn and npm. I think this is what we agreed in chat @SnowPhoenix
I have also removed the stuff for pre-6, because that's no longer LTS so there's no reason to support it anymore.


ERROR: no schema has been selected to create in

Bug description
When running npx prisma migrate dev for the 2nd time I get this error
Environment variables loaded from ../.env
Prisma schema loaded from schema.prisma
Datasource "db": PostgreSQL database "test-dev", schema "public" at "test-dev.postgres.database.azure.com:5432"

Error: P3006

Migration `20210930002201_init` failed to apply cleanly to the shadow database.
Error:
db error: ERROR: no schema has been selected to create in
   0: sql_migration_connector::flavour::postgres::sql_schema_from_migration_history
             at migration-engine/connectors/sql-migration-connector/src/flavour/postgres.rs:373
   1: migration_core::api::DevDiagnostic
             at migration-engine/core/src/api.rs:93

How to reproduce

create a schema file with shadowDatabaseUrl
run npx prisma migrate dev, tables gets created, migration gets created
run npx prisma migrate dev again. you encounter the error above

Expected behavior

it should either create a new migration file if there are changes or return with no errors

Prisma information
generator client {
  provider = "prisma-client-js"
  output = "../src/db/prisma"
}

datasource db {
  provider = "postgresql"
  url      = env("CONN_STRING")
  shadowDatabaseUrl = env("SHADOW_DB_URL")
}

model feeds {
  id      Int     @id @default(autoincrement())
  title   String? @db.VarChar(255)
  rss_url String? @db.VarChar(255)
  colour  String? @db.VarChar(255)
}

model sessions {
  sid    String   @id(map: "session_pkey") @db.VarChar
  sess   Json     @db.Json
  expire DateTime @db.Timestamp(6)

  @@index([expire], map: "IDX_session_expire")
}

model users {
  id              Int       @id @default(autoincrement())
  email           String    @unique(map: "users_email_unique") @db.VarChar(255)
  password        String
  role            String
  rss_url         String?
  credentials     String?
  title           String?
  city            String?
  prov_state      String?
  country         String?
  first_name      String?
  middle_name     String?
  last_name       String?
  show_email      Boolean?  @default(false)
  notes           String?
  unsubscribe     Boolean?  @default(false)
  last_sign_in_at DateTime? @db.Timestamptz(6)
  created_at      DateTime  @default(now()) @db.Timestamptz(6)
  updated_at      DateTime  @updatedAt
}

Environment & setup

OS: Windows (WSL Ubuntu 20.04)
Database: PostgreSQL (Azure)
Node.js version: v14.17.4

Prisma Version
 0.423.0

Do you need any information from me?

What version of Prisma are you using? 0.423.0 looks like Prisma Studio only.
Will using the schema you changed and running these commands reproduce the problem for us? Both your databases on Azure? Any specific product in Azure or will this be obvious for us when reproducing? Can you also reproduce outside of Azure?

Does anyone have any informations about this issue?

I have the same error running npx prisma migrate dev --name initial-migration --create-only in a newly created database.
datasource db {
    provider          = "postgresql"
    url               = env("DATABASE_URL")
    shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
}

DATABASE_URL=postgresql://myuser:mypass@localhost:5432/mydb?schema=myschema
SHADOW_DATABASE_URL=postgresql://postgres:mypass@localhost:5432/mydb?schema=myschema

Also started having this issue, I'm no longer able to apply or create any new migrations to the dev database with or without a shadow database URL configured. When trying to apply them to a newly created database the same error occurs:

I'm running both databases in an azure, however, when I created a PR in github to test this command specifically the migration was created successfuly:

Are you all using PostgreSQL on Azure? Is it only reproducible there?

For anyone having the same issue I found this stackoverflow thread that solved it for me: https://stackoverflow.com/questions/41207259/no-schema-has-been-selected-to-create-in-error#:~:text=You get this error when,users ).
As in that thread granting create and usage permissions on the public schema had the migrations working for me again:

grant usage on schema public to public; grant create on schema public to public;

I resolved this by using my root user as the only connection url in schema.prisma

Where do I add this line?
grant usage on schema public to public;   grant create on schema public to public;

I've got hit by this yesterday, in my case, we had a migration that was creating a FUNCTION that had no schema prefixed.
Something like this:
CREATE OR REPLACE FUNCTION the_function_name()

This ended up failing to apply when running prisma migrate dev. If we manually added the schema to it, it started working.
The other solution we found was to remove the following line from the initial migration:
SELECT pg_catalog.set_config('search_path', '', false);

Which, after removed, made things work again.


SVG support for toDataUrl()

To sync with this: https://github.com/typpo/quickchart/issues/85

Thanks!  This has been published on npm as version 1.0.7


fix auto select active project (#4146)

This change addresses item #4146
This fixes the active project change behavior
The following change is proposed:

Update utils function isFileInsideFolder to avoid partial match and thus, wrong active project change

Contributed by STMicroelectronics
Signed-off-by: Matthieu NAUD<EMAIL_ADDRESS>

@MNASTM Looks like there are some linter errors, could you fix them so that the build succeeds?

@MNASTM Pinging about agreeing to the license agreement.

@MNASTM Pinging about agreeing to the license agreement.

I am in touch with my legal department and waiting for their approvals.


mpeg2dec: do not change the status reported

Client needs to know about the format change on the first
time they'll try to decode a sequence header.
Fixes #505
Signed-off-by: Daniel Charles<EMAIL_ADDRESS>

Before we think on changing the API, let's work with the current one.  start(configBuffer) gets a configBuffer that can have nal units in the buffer member.  That information has to be processed.  I think it is okay to return the FORMAT_CHANGE if needed but it can also hold it till the first time Client calls decode(videoBuffer).
I would prefer to keep the current functionality and have that across the board with the codecs.  Then we work on cleaning up the API.
@mypopydev  mpeg2 start will not return FORMAT_CHANGE unless you call it with a valid nal unit from the bitstream.  FORMAT_CHANGE will be returned by decode if you send the first nal unit on it.

Hi @chivakker :
So we do not need change anything about this, right? @mypopydev Just need getFormatInfo after he call start.

@xuguangxin @chivakker
I will call getFormatInfo() after the first decode() success, but I think it's a work round. :)
Tks.

User should call getFormatInfo in two situation:

after after start() decoder witch codec data, and start() return YAMI_SUCCUESS.
decode return a format change.
So, you did not get format  info from first situation?

In current code, I think I need to:

call getFormatInfo() after the first decode() success, but I think it's a work round. :)
call getFormatInfo() after decode() return a format change.

@mypopydev  you can call getFormatInfo whenever you want in your two cases. If called after decode(), it is because it returned FORMAT_CHANGE
The patch enables you to do it after calling decode.  The first use case was already covered and it is not a workaround

@chivakker  Now is working, Thanks.

Hi @chivakker
Do we still need merge this patch?

@chivakker What is the status of this patch?

This can be merged as the functionality might be required by another customer.  I know the original reporter decided to use the other logic.  IMO, it can be merged.

Hi @chivakker
But this patch will return FORMAT_CHANGE in start right?

@xuguangxin, no this patch does not modify start.  I'll submit a separate patch to remove FORMAT_CHANGE from start and we discuss there the implications.

Actually you're right based on the discussion about what start should return. Closing this as no-op


[RESTEASY-2148] Enable utf8 encoding of filename only when explicitly…

… requested, disabled by default

I confirm that functionality of this fix is correct. I miss some tests here, tests would be useful if this commit will be backport to older streams. We can assume future backport, because original jira is blocker ...

Thanks @marekkopecky . The configuration option is actually tested in EncodingMimeMultipartFormProviderTest , but yes, I agree we could have a more thorough coverage. Given the tight schedule, I'll move on with the merging and backporting to 3.6, as yes, this is needed and blocking for the WFLY16 release. We can add further tests later on.


feat/add test case

feat: add test that matching by title not test case id
chore: format

Codecov Report
Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 65.97%. Comparing base (0f5ba8e) to head (4927149).
Report is 3 commits behind head on main.

Files
Patch %
Lines

lib/TestrailReporter.js
66.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   61.50%   65.97%   +4.46%
==========================================
  Files           5        5
  Lines         478      479       +1
  Branches       61       70       +9
==========================================
+ Hits          294      316      +22
+ Misses        181      160      -21
  Partials        3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


New check to avoid adding the same option contract multiple times

Description

New check for sample C#/Py OptionChainProviderAlgorithm to avoid adding the same option contract multiple times.
Removed some white spaces in Py sample.

Related Issue

Closes https://github.com/QuantConnect/Lean/issues/2159
Motivation and Context

Sample algorithms should use the API as best as possible.
Requires Documentation Change

N/A
How Has This Been Tested?

Manually
Types of changes

[x] 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 change)
[ ] Non-functional change (xml comments/documentation/ect)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description or feature-<issue#>-<description>

Neither algorithm has a regression test associated. I can confirm they are both generating the same result as before


@six.add_metaclass and Django models

Originally reported by: sodas tsai (Bitbucket: sodastsai, GitHub: sodastsai)

While making Django models with custom metaclass,
I used the decorator to keep compatibility between Python 2 and 3:
from django.db import models
from django.db.models.base import ModelBase
import six

class CustomModelBase(ModelBase):
    def __init__(cls, name, bases, attrs):
        super(CustomModelBase, cls).__init__(name, bases, attrs)
        print(name)

@six.add_metaclass(CustomModelBase)
class CustomModel(models.Model):
    some_field = models.CharField(max_length=128)

But while starting my Django server, I got following exceptions:
Traceback (most recent call last):
  File "<input>", line 5, in <module>
  File "/work/venv/lib/python3.4/site-packages/django/__init__.py", line 21, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/work/venv/lib/python3.4/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "/work/venv/lib/python3.4/site-packages/django/apps/config.py", line 202, in import_models
    self.models_module = import_module(models_module_name)
  File "/work/venv/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/work/core/models/__init__.py", line 88, in <module>
    class CustomModel(models.Model):
  File "/work/venv/lib/python3.4/site-packages/six.py", line 794, in wrapper
    return metaclass(cls.__name__, cls.__bases__, orig_vars)
  File "/work/venv/lib/python3.4/site-packages/django/db/models/base.py", line 168, in __new__
    new_class.add_to_class(obj_name, obj)
  File "/work/venv/lib/python3.4/site-packages/django/db/models/base.py", line 297, in add_to_class
    value.contribute_to_class(cls, name)
  File "/work/venv/lib/python3.4/site-packages/django/db/models/options.py", line 129, in contribute_to_class
    if self.meta:
AttributeError: 'Options' object has no attribute 'meta'

By using Python 3's metaclass syntax, the CustomModel class works correctly without such AttributeError.
from django.db import models
from django.db.models.base import ModelBase

class CustomModelBase(ModelBase):
    def __init__(cls, name, bases, attrs):
        super(CustomModelBase, cls).__init__(name, bases, attrs)
        print(name)

class CustomModel(models.Model, metaclass=CustomModelBase):
    some_field = models.CharField(max_length=128)

It seems the decorator forgot to copy some attributes that set by Django's ModelBase metaclass.
I'm using Python 3.4.2, six 1.9.0, and Django 1.7.4 on OS X 10.10.2.

Bitbucket: https://bitbucket.org/gutworth/six/issue/118

I believe this issue as an instance of the caveat that benjamin highlighted here. I'm not aware of a workaround other than to use the alternate with_metaclass.

I was able to replicate your finding by running this script under rwt:
__requires__ = ['django', 'six']

import django.conf
from django.db import models
from django.db.models.base import ModelBase
import six

django.conf.settings.configure(
    INSTALLED_APPS=['__main__'],
)

django.setup()

class CustomModelBase(ModelBase):
    def __init__(cls, name, bases, attrs):
        super(CustomModelBase, cls).__init__(name, bases, attrs)
        print(name)

@six.add_metaclass(CustomModelBase)
class CustomModel(models.Model):
    some_field = models.CharField(max_length=128)
    app_label = "my_app"

I don't yet have an explanation.

I have this problem:
@six.add_metaclass(abc.ABCMeta)
AttributeError: module 'six' has no attribute 'add_metaclass'

Is there a workaround for this bug?
I use python 3.7.4 and six 1.12.0.

@R-Studio Your problem is different from the reported issue, but honestly the problem is likely in your implementation. When you get the error, you should inspect "six" to see if it's the module from six-1.12.0. Likely you have another module in your path six.py that's masking the six package.