Ordering by id_in

Hi,
As requested by @schickling, a feature request describing ordering a list by the id_in input.
I have the following use case:
enum CompanyRelationType {
  LIKE
  DISLIKE
  WAITING
}

type CompanyRelation {
  type: CompanyRelationType!
  withCompanyId: ID!
  ownerId: ID!
  // etc..
}

type Company {
# ..etc.
relations: [CompanyRelation!]!
}

Companies are able to relate to each other with a certain type (LIKE, DISLIKE, WAITING) where only one relation type can exist between company A & company B and vice versa.
What I want is to be able to retrieve a 'ranked' list, where I first get the companies that this users company hasn't ranked yet, and then the companies that have been ranked in a certain order. The first part is easy, e.g.:
prisma.companies({where: {
  relations_none: {
    withCompanyId: "current users company id"
  }
})

Now comes the harder part because I would like to return the rest of the companies where the current users company does have a relation with in a specific order of the relation type, WAITING first, then LIKED and DISLIKED last.
I've tried two solutions, the first being just getting the 'no-relation' companies first, then the one with relation type WAITING, and so on. In the end merging them together and returning. This makes it hard (though not impossible) to paginate without skipping items I don't want to be skipped 😄
The second solution should work better(I think :)) as it works like this:
const relations = await prisma.companyRelations({
  where: {
    withCompanyId: "current users company id"
  },
  orderBy: 'type_DESC'
})

This gives me a list of relations in the exact order I want to return them, but I need the companies and not the companyRelation, so I need to do this:
await prisma.companies({
  where: { id_in: relations.map(relation => relation.ownerId) },
})

This returns the companies in a different order then the order of the relations, which is the exact order I need. What would fix it for me is to be able to either: orderdBy: id_in, which would mean I still have to get all the relations as per the example above (which isn't a big issue), or be able to orderBy: companyRelation_type_DESC or something like that. I know there's an open PR for that last option.
I hope any of this makes sense 😄 Perhaps I'm overthinking it and there's a better solution or model for my problem. It's probably an edge case pretty specific to my use case, but maybe there are more people who have the same problem.
We absolutely love working with Prisma BTW, thanks very much for a great product! 🎉

Hey @Corjen ,
thanks for such a thorough writeup! 🙏
May i know why you modeled CompanyRelation with fields of type ID? My intuition would be to model it like the following. In this case you would not need to do the id_in query.
type CompanyRelation {
  type: CompanyRelationType!
  withCompanyId: Company!
  ownerId: Company!
  // etc..
}

Hi @mavilein,
Thanks for the quick reply! That does indeed make it easier to get the relations connected to a certain company, but still doesn't solve the issue of getting the companies without a relationship first, right?
In your solution, I would have to do something like:
const relations = await prisma.company({id: "my company id"}).relations()

const companiesWithNoRelation = await prisma.companies({where: {
relations_none: {
   id_not_in: relations.map(relation => relation.id) } })
}

And to get the company of a relation, wouldn't I have to loop trough the entire connections list to get each company?


[FEATURE]: Skins System

Scope
Web
Feature Description
A skin system that allows you to customize colors and logos of the txAdmin website.
Use Case
No response
Proposed Solution
No response
Additional Info
No response

No.
That would be a nightmare to support... also we are not winamp lol


Boldly advertise gitup as user agent

I'd like to request that gitup/<version> will be send with User-Agent for the following reasons:

This is not the official Git client, stop pretending to be.
It may help to pinpoint issues on the server-side when someone assumes that the real Git client is accessing which is not. Just avoid confusion.
Other clients like JGit boldly advertise as such: https://github.com/eclipse/jgit/blob/88e924e86beaa7e4911f4496e847a10833ac1c15/org.eclipse.jgit/src/org/eclipse/jgit/transport/TransportHttp.java#L904-L907
When this makes into FreeBSD base this might help the infra team make better analysis which clients access most the Git repos via HTTP.

Sounds good to me

Sounds good to me

The server appears to reject requests that come from user agents other than "git/[version]" (if you change the user agent in line 962 to "gitup/%s", the server returns a 404 error).  I did some testing today and it doesn't complain about appending additional information to the expected user agent -- it responds to "git/2.28 (gitup/0.88)" requests the same as it does to "git/2.28" requests.

The server appears to reject requests that come from user agents other than "git/[version]" (if you change the user agent in line 962 to "gitup/%s", the server returns a 404 error).  I did some testing today and it doesn't complain about appending additional information to the expected user agent -- it responds to "git/2.28 (gitup/0.88)" requests the same as it does to "git/2.28" requests.

Which server exactly? git.freebsd.org? If so, this needs to be discussed with @emaste or someone from infra. This isn't right. I will test this server with JGit too then.

Which server exactly? git.freebsd.org? If so, this needs to be discussed with @emaste or someone from infra. This isn't right. I will test this server with JGit too then.

I've mentioned this to @lwhsu who has done most of the git infra work

I've mentioned this to @lwhsu who has done most of the git infra work

This seems to work now:
$ curl --verbose https://git.freebsd.org/src.git/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying 2604:1380:2000:9501::e6a:1:443...
* Connected to git.freebsd.org (2604:1380:2000:9501::e6a:1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=git.freebsd.org
*  start date: Nov 10 20:23:01 2020 GMT
*  expire date: Feb  8 20:23:01 2021 GMT
*  subjectAltName: host "git.freebsd.org" matched cert's "git.freebsd.org"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET /src.git/info/refs?service=git-upload-pack HTTP/1.1
> Host: git.freebsd.org
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Mon, 04 Jan 2021 19:53:32 GMT
< Content-Type: application/x-git-upload-pack-advertisement
< Transfer-Encoding: chunked
< Connection: keep-alive
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
<
000eversion 2
0015agent=git/2.29.2
000cls-refs
0012fetch=shallow
0012server-option
0017object-format=sha1
* Connection #0 to host git.freebsd.org left intact

This seems to work now:
$ curl --verbose https://git.freebsd.org/src.git/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying 2604:1380:2000:9501::e6a:1:443...
* Connected to git.freebsd.org (2604:1380:2000:9501::e6a:1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=git.freebsd.org
*  start date: Nov 10 20:23:01 2020 GMT
*  expire date: Feb  8 20:23:01 2021 GMT
*  subjectAltName: host "git.freebsd.org" matched cert's "git.freebsd.org"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET /src.git/info/refs?service=git-upload-pack HTTP/1.1
> Host: git.freebsd.org
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Mon, 04 Jan 2021 19:53:32 GMT
< Content-Type: application/x-git-upload-pack-advertisement
< Transfer-Encoding: chunked
< Connection: keep-alive
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
<
000eversion 2
0015agent=git/2.29.2
000cls-refs
0012fetch=shallow
0012server-option
0017object-format=sha1
* Connection #0 to host git.freebsd.org left intact

It was happening on both git.freebsd.org and github.com.  I just committed an update that sends "gitup/version" to *.freebsd.org and "git/version (gitup/version)" to any other host to enable those who want to use github.com to continue to do so.  Thank you!

It was happening on both git.freebsd.org and github.com.  I just committed an update that sends "gitup/version" to *.freebsd.org and "git/version (gitup/version)" to any other host to enable those who want to use github.com to continue to do so.  Thank you!

BTW I didn't do any modification on git.freebsd.org in the past 48 hours.

BTW I didn't do any modification on git.freebsd.org in the past 48 hours.

Here is your problem: You are accessing the wrong URL on GitHub.
Wrong:
mosipov@bsd1srv:/usr/home/mosipov
$ curl --verbose https://github.com/freebsd/freebsd-src/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying <IP_ADDRESS>:443...
* Connected to github.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=github.com
*  start date: May  5 00:00:00 2020 GMT
*  expire date: May 10 12:00:00 2022 GMT
*  subjectAltName: host "github.com" matched cert's "github.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> GET /freebsd/freebsd-src/info/refs?service=git-upload-pack HTTP/1.1
> Host: github.com
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< date: Tue, 05 Jan 2021 08:53:58 GMT
< content-type: text/plain; charset=utf-8
< server: GitHub.com
< status: 404 Not Found
< vary: X-PJAX, Accept-Encoding, Accept, X-Requested-With
< cache-control: no-cache
< strict-transport-security: max-age=31536000; includeSubdomains; preload
< x-frame-options: deny
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
< expect-ct: max-age=2592000, report-uri="https://api.github.com/_private/browser/errors"
< content-security-policy: default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'
< Set-Cookie: _gh_sess=LjrjonoS59i933CqCQUEkW4%2F%2BKbhGluJ%2Fd1MUTF7aHb6BY%2Bq6OBMnvzpHseJ3e62KD9sNAo3H7pEQ%2FQrYuCLZvGoIcVH71KQkkIOxHMXyT388%2BK45i5npZeM9KACgITD5T3DrxKwyJmclTFDwEm4dDGR3HsVbH4XKXwBo3Zj%2BspjIdsKTSknglM7VVlwRD%2Fh9Rpux7UgdlvOR6n3Km7X%2FdePWwtg%2Fjt%2BOxmR4MjhDWv%2FyCuiVl8hrVkwztwBohTV1ZOBOfcpJiOzFiGe1xN7kg%3D%3D--PVOBsSre1huURBue--hIJQ13b6oxcwEWaNB%2BZS%2BA%3D%3D; Path=/; HttpOnly; Secure; SameSite=Lax
< Set-Cookie: _octo=GH1.1.1845365942.1609836838; Path=/; Domain=github.com; Expires=Wed, 05 Jan 2022 08:53:58 GMT; Secure; SameSite=Lax
< Set-Cookie: logged_in=no; Path=/; Domain=github.com; Expires=Wed, 05 Jan 2022 08:53:58 GMT; HttpOnly; Secure; SameSite=Lax
< Content-Length: 9
< X-GitHub-Request-Id: 8649:A66A:407EE04:5B979CB:5FF42926
<
* Connection #0 to host github.com left intact
Not Found

Right:
$ curl --verbose https://github.com/freebsd/freebsd-src.git/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying <IP_ADDRESS>:443...
* Connected to github.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=github.com
*  start date: May  5 00:00:00 2020 GMT
*  expire date: May 10 12:00:00 2022 GMT
*  subjectAltName: host "github.com" matched cert's "github.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> GET /freebsd/freebsd-src.git/info/refs?service=git-upload-pack HTTP/1.1
> Host: github.com
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: GitHub Babel 2.0
< Content-Type: application/x-git-upload-pack-advertisement
< Transfer-Encoding: chunked
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
< Vary: Accept-Encoding
< X-Frame-Options: DENY
< X-GitHub-Request-Id: FB4A:A66C:D8FD455:1379A055:5FF42939
<
001e# service=git-upload-pack
0000000eversion 2
0023agent=git/github-gb13cc0c1a7bd
000cls-refs
0019fetch=shallow filter
0012server-option
0017object-format=sha1
* Connection #0 to host github.com left intact
0000

By convention, git repos end with .git. That is why you get the 404 intitially. Please update the sample gitup.conf and it will work w/o hacks for GitHub.

Here is your problem: You are accessing the wrong URL on GitHub.
Wrong:
mosipov@bsd1srv:/usr/home/mosipov
$ curl --verbose https://github.com/freebsd/freebsd-src/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying <IP_ADDRESS>:443...
* Connected to github.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=github.com
*  start date: May  5 00:00:00 2020 GMT
*  expire date: May 10 12:00:00 2022 GMT
*  subjectAltName: host "github.com" matched cert's "github.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> GET /freebsd/freebsd-src/info/refs?service=git-upload-pack HTTP/1.1
> Host: github.com
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< date: Tue, 05 Jan 2021 08:53:58 GMT
< content-type: text/plain; charset=utf-8
< server: GitHub.com
< status: 404 Not Found
< vary: X-PJAX, Accept-Encoding, Accept, X-Requested-With
< cache-control: no-cache
< strict-transport-security: max-age=31536000; includeSubdomains; preload
< x-frame-options: deny
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
< expect-ct: max-age=2592000, report-uri="https://api.github.com/_private/browser/errors"
< content-security-policy: default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'
< Set-Cookie: _gh_sess=LjrjonoS59i933CqCQUEkW4%2F%2BKbhGluJ%2Fd1MUTF7aHb6BY%2Bq6OBMnvzpHseJ3e62KD9sNAo3H7pEQ%2FQrYuCLZvGoIcVH71KQkkIOxHMXyT388%2BK45i5npZeM9KACgITD5T3DrxKwyJmclTFDwEm4dDGR3HsVbH4XKXwBo3Zj%2BspjIdsKTSknglM7VVlwRD%2Fh9Rpux7UgdlvOR6n3Km7X%2FdePWwtg%2Fjt%2BOxmR4MjhDWv%2FyCuiVl8hrVkwztwBohTV1ZOBOfcpJiOzFiGe1xN7kg%3D%3D--PVOBsSre1huURBue--hIJQ13b6oxcwEWaNB%2BZS%2BA%3D%3D; Path=/; HttpOnly; Secure; SameSite=Lax
< Set-Cookie: _octo=GH1.1.1845365942.1609836838; Path=/; Domain=github.com; Expires=Wed, 05 Jan 2022 08:53:58 GMT; Secure; SameSite=Lax
< Set-Cookie: logged_in=no; Path=/; Domain=github.com; Expires=Wed, 05 Jan 2022 08:53:58 GMT; HttpOnly; Secure; SameSite=Lax
< Content-Length: 9
< X-GitHub-Request-Id: 8649:A66A:407EE04:5B979CB:5FF42926
<
* Connection #0 to host github.com left intact
Not Found

Right:
$ curl --verbose https://github.com/freebsd/freebsd-src.git/info/refs?service=git-upload-pack -H "User-Agent: gitup/2" -H "Git-Protocol: version=2"
*   Trying <IP_ADDRESS>:443...
* Connected to github.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: none
*  CApath: /etc/ssl/certs/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=github.com
*  start date: May  5 00:00:00 2020 GMT
*  expire date: May 10 12:00:00 2022 GMT
*  subjectAltName: host "github.com" matched cert's "github.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> GET /freebsd/freebsd-src.git/info/refs?service=git-upload-pack HTTP/1.1
> Host: github.com
> Accept: */*
> User-Agent: gitup/2
> Git-Protocol: version=2
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: GitHub Babel 2.0
< Content-Type: application/x-git-upload-pack-advertisement
< Transfer-Encoding: chunked
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
< Vary: Accept-Encoding
< X-Frame-Options: DENY
< X-GitHub-Request-Id: FB4A:A66C:D8FD455:1379A055:5FF42939
<
001e# service=git-upload-pack
0000000eversion 2
0023agent=git/github-gb13cc0c1a7bd
000cls-refs
0019fetch=shallow filter
0012server-option
0017object-format=sha1
* Connection #0 to host github.com left intact
0000

By convention, git repos end with .git. That is why you get the 404 intitially. Please update the sample gitup.conf and it will work w/o hacks for GitHub.

Works for me:
root@bsd1srv:~/gitup (main *%=)
# git diff
diff --git a/gitup.c b/gitup.c
index a619b3f..5858fa0 100644
--- a/gitup.c
+++ b/gitup.c
@@ -2068,10 +2068,7 @@ load_configuration(connector *connection, const char *configuration_file, char *

    /* Build the user agent string. */

-   if (strstr(connection->host, "freebsd.org") != NULL)
-       snprintf(connection->user_agent, sizeof(connection->user_agent), "gitup/%s", GITUP_VERSION);
-   else
-       snprintf(connection->user_agent, sizeof(connection->user_agent), "git/%s (gitup/%s)", GIT_VERSION, GITUP_VERSION);
+   snprintf(connection->user_agent, sizeof(connection->user_agent), "gitup/%s", GITUP_VERSION);

    return argument_index;
 }

stderr:
 939 # Branch: refs/heads/stable/12
 940 ! /usr/src/UPDATING has been modified.
 941 # Action: repair
 942 POST /freebsd/freebsd.git/git-upload-pack HTTP/1.1^M
 943 Host: github.com:443^M
 944 User-Agent: gitup/0.88^M
 945 Accept-encoding: deflate, gzip^M
 946 Content-type: application/x-git-upload-pack-request^M
 947 Accept: application/x-git-upload-pack-result^M
 948 Git-Protocol: version=2^M
 949 Content-length: 171^M
 950 ^M
 951 0011command=fetch0022agent=git/github-gb13cc0c1a7bd0001000dthin-pack000fno-progress000dofs-delta0032want ac80b270c8c4723d9fbcf64fe0f938d4e949bc7d
 952 000cdeepen 10009done
 953 0000
 954
 955 ^M==> bytes sent: 448
 956 ^M==> bytes read:338    bytes_expected:0    total_bytes_read:338^M==> bytes read:46 bytes_expected:338  total_bytes_read:384^M==> bytes read:3  bytes_expected:372  total_bytes_read:375^M==> bytes read:1370
 957
 958 pack version: 2, total_objects: 1, pack_size: 32727
 959
 960 e20577e6e9b45081efa6318cdc2e1d64 refs/tags/release/7.4.0_cvs
 961 004ccc28c79becc0c69f0d33337062166295c1f52d63 refs/tags/release/7.4.0_cvs^{}
 962 00455bf34779cc092b6457077b01fa89c1a5e9117a76 refs/tags/release/8.0.0
 963 004859dd044d1cb744d3dba6b41c41e196b54e8fd9f8 refs/tags/release/8.0.0^{}
 964 00490b061ae00ceb5ece24fe73255269e1ad3027e746 refs/tags/release/8.0.0_cvs

Works for me:
root@bsd1srv:~/gitup (main *%=)
# git diff
diff --git a/gitup.c b/gitup.c
index a619b3f..5858fa0 100644
--- a/gitup.c
+++ b/gitup.c
@@ -2068,10 +2068,7 @@ load_configuration(connector *connection, const char *configuration_file, char *

    /* Build the user agent string. */

-   if (strstr(connection->host, "freebsd.org") != NULL)
-       snprintf(connection->user_agent, sizeof(connection->user_agent), "gitup/%s", GITUP_VERSION);
-   else
-       snprintf(connection->user_agent, sizeof(connection->user_agent), "git/%s (gitup/%s)", GIT_VERSION, GITUP_VERSION);
+   snprintf(connection->user_agent, sizeof(connection->user_agent), "gitup/%s", GITUP_VERSION);

    return argument_index;
 }

stderr:
 939 # Branch: refs/heads/stable/12
 940 ! /usr/src/UPDATING has been modified.
 941 # Action: repair
 942 POST /freebsd/freebsd.git/git-upload-pack HTTP/1.1^M
 943 Host: github.com:443^M
 944 User-Agent: gitup/0.88^M
 945 Accept-encoding: deflate, gzip^M
 946 Content-type: application/x-git-upload-pack-request^M
 947 Accept: application/x-git-upload-pack-result^M
 948 Git-Protocol: version=2^M
 949 Content-length: 171^M
 950 ^M
 951 0011command=fetch0022agent=git/github-gb13cc0c1a7bd0001000dthin-pack000fno-progress000dofs-delta0032want ac80b270c8c4723d9fbcf64fe0f938d4e949bc7d
 952 000cdeepen 10009done
 953 0000
 954
 955 ^M==> bytes sent: 448
 956 ^M==> bytes read:338    bytes_expected:0    total_bytes_read:338^M==> bytes read:46 bytes_expected:338  total_bytes_read:384^M==> bytes read:3  bytes_expected:372  total_bytes_read:375^M==> bytes read:1370
 957
 958 pack version: 2, total_objects: 1, pack_size: 32727
 959
 960 e20577e6e9b45081efa6318cdc2e1d64 refs/tags/release/7.4.0_cvs
 961 004ccc28c79becc0c69f0d33337062166295c1f52d63 refs/tags/release/7.4.0_cvs^{}
 962 00455bf34779cc092b6457077b01fa89c1a5e9117a76 refs/tags/release/8.0.0
 963 004859dd044d1cb744d3dba6b41c41e196b54e8fd9f8 refs/tags/release/8.0.0^{}
 964 00490b061ae00ceb5ece24fe73255269e1ad3027e746 refs/tags/release/8.0.0_cvs

Thank you for finding this bug.  I really appreciate the amount of time and effort you're putting in to help this project move forward.  Thank you!

Thank you for finding this bug.  I really appreciate the amount of time and effort you're putting in to help this project move forward.  Thank you!

Thank you for finding this bug. I really appreciate the amount of time and effort you're putting in to help this project move forward. Thank you!

Very much welcome, hoping to get this into base because got will take years to land. I have noticed a few other things and will report shortly.

Thank you for finding this bug. I really appreciate the amount of time and effort you're putting in to help this project move forward. Thank you!

Very much welcome, hoping to get this into base because got will take years to land. I have noticed a few other things and will report shortly.

Issue is fixed on main.

Issue is fixed on main.


fix(dangerMode): dont convert objects to HTML

Changes

[x] Fix  linuswillner/react-console-emulator#860
Don't run the html() conversion method on non-string inputs when the terminal is in [dangerMode]. (I tried to add a test for this as well, but I wasn't actually able to reproduce the problem in the Jest env… 😬)
https://github.com/linuswillner/react-console-emulator/blob/1d1fabbd21f48a446204f9f22c68685152e32bd5/src/TerminalMessage.jsx#L18-L19

[x] Add a new test-watch NPM script.
Not really relevant to the changes herein, but it is convenient!

Testing
Check out this forked branch locally and start the demo. Scroll down to the new "Raw HTML Output" demo and try running the html command. If you see colorful output and you don't see the [object Object] error, this worked!

Thanks a bunch for your contribution Rafe!


API.request is not working properly if superagent is not set in config

I have created a PR for this.
To allow people to install mobx-model from a git repo, it will be nice to commit the files in the lib folder and set directories configured in package.json.
npm i http://github.com/wearevolt/mobx-model.git

Fixed. Thanks @vijayst


Cannot use excelastic when x-pack installed

Cannot use excelastic when x-pack installed the error message is cannot connected

Hello,
would it be possible to provide some more information?

which x-pack components are you using, is security enabled?
how does you excelastic configuration look like? did you enable http basic auth?
is the elasticsearch server running on https?

Thanks for submitting an issue, Regards.

As noted in another issue TLS was not actually enabled for the ES client. The readme has been updated, see elastic_tls for connecting to secured servers.


Async behavior

I'm working on the part that manages the sending of images. Using futures provides a way to handle things quite flexible for the user. Except I found out that awaiting a Future that gets set by a traitlets callback blocks. It turns out that Jupyter notebook is "single threaded" concerning the comm io: https://github.com/ipython/ipython/issues/12786
Options:

Wait for this to get fixed (and then force at least that version of the notebook). - not feasible.
Implement communication ourselves, via a ws. - Prefer not to go there.
Don't do async.
Another workaround ... ?

In #8 we implement a non-async approach.


fix: warning CS0436: The type 'ModuleInitializerAttribute'

in './src/…Shared/ModuleInitializer.cs' conflicts with the imported type 'ModuleInitializerAttribute' in 'Avalonia.Base'.
What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0024198-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Limit ourselves to /bin/sh

Thank you very much for your contribution. We highly appreciate the time
and effort you put into pull request. Before you submit the pull request,
please review the Contribution Guidelines.
Make sure you check the following boxes.
For all changes:

[x] Sign the Gradle CLA.

For all non-trivial changes that modify the behavior or public API:

[x] Before submitting a pull request, you started a discussion on the
Gradle developer list
or can reference a JIRA issue.
[x] You considered writing a design document. A design document can be
brief but explains the use case or problem you are trying to solve,
touches on the planned implementation approach as well as the test cases
that verify the behavior. Optimally, design documents should be submitted
as a separate pull request. You can find samples
in the Gradle GitHub repository. Please let us know if you need help with
creating the design document. We are happy to help!
[ ] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
you ran a build on your local machine via the command ./gradlew quickCheck
and the tests for the modified module.
[x] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

Some systems do not have bash installed. For this reason unixStartScript.txt should be /bin/sh compatible. It seems that only incompatibility was using arrays from line 155 onwards so I replaced use of arrays with some variable substitution.

Hey Alex, thanks for the contribution. Unfortunately your changes break our integration tests as you can check yourself at https://builds.gradle.org/viewLog.html?buildId=741834&tab=buildResultsDiv&buildTypeId=Gradle_PullRequest_LinuxJava17withSanityCheck Would you mind looking into this? We need these tests to pass to verify Gradle behaves as expected. Thanks and cheers,
René

Fixed it!
I forgot the script passes first through a template engine and forgot to comment the $ sign in front of $JVM_OPTS thus groovy tried to find this property and failed. The integration tests should be ok now. regarding this incident.

Hey Alex,
there are still unit and integration tests failing with your change. check https://builds.gradle.org/viewLog.html?buildId=743010&tab=buildResultsDiv&buildTypeId=Gradle_PullRequest_LinuxJava17withSanityChec

@alexproca Thanks for the additional fixes. There're still some failing tests. Would you mind looking into those?

Hi @bmuschko!  I'm working to solve those too.
I ran ./gradlew iT on my machine and did not catch those tests.

@alexproca Have you fixed the conflicts?

@jaredsburrows conflicts fixed ! but still some tests failing

@alexproca: There has been no activity on this PR for one month. Are you still interested in working on this?

@wolfs I would like to have it done but the change is impacting the gradle distribution itself and it triggers many failures in tests run on CI. I cannot reproduce this failures myself. In order to finish it I would need some support from someone in the gradle team to help me understand test failures.

How did you try to reproduce these tests? From the command line you can do for example
./gradlew plugins:integTest --tests "*ApplicationPluginIntegrationTest"
./gradlew wrapper:integTest

Is this enough information for you or do you need some more guidance?

It looks like that when running the Gradle wrapper script with --gradle-user-home "some dir" then this does not work. A test exhibiting this behaviour is WrapperChecksumVerificationTest.  Strangely for me it works from the IDE but fails on the command line. Any ideas from your side? It seems to be related to the change in unixStartScript.txt, since when reverting those changes the test again works from the command line.

@alexproca : Did you have time to look into this? Do you need further guidance?

@alexproca Hi, Alex. Did you have chance to look into the failing test?

Hi guys. It seems the environment variable expansion for this variables \$DEFAULT_JVM_OPTS \$JAVA_OPTS \$APPLICATION_OPTS is causing troubles. Actually this is the reason bash arrays were used in the first place. I'm thinking of an awk script that can concatenate the content of these variables.

@alexproca awk should be fine. Ubuntu migrated from bash to sh, perhaps some information here can help you.

I have investigated this more and I think a good plain solution is to escape the application arguments and JVM options one after another using $@ and store each as one string.
Something like this:
# Escape application args
for s in "\${@}" ; do
    s="\""\$s"\""
    APP_ARGS=\$APP_ARGS" "\$s
done

# Escape and collect JVM options
set -- \$DEFAULT_JVM_OPTS
for s in "\${@}" ; do
    s="\""\$s"\""
    JVM_OPTS=\$JVM_OPTS" "\$s
done
set -- \$JVM_OPTS
for s in "\${@}" ; do
    s="\""\$s"\""
    JVM_OPTS=\$JVM_OPTS" "\$s
done
set -- \$${optsEnvironmentVar}
for s in "\${@}" ; do
    s="\""\$s"\""
    JVM_OPTS=\$JVM_OPTS" "\$s
done

And then use this execution command (mix between original and new version):
eval "\$JAVACMD" "\$JVM_OPTS" <% if ( appNameSystemProperty ) { %>"-D${appNameSystemProperty}=\$APP_BASE_NAME" <% } %>-classpath "\"\$CLASSPATH\"" ${mainClassName} "\$APP_ARGS"

For that part this test would need adjustment again (2 occurrences):
https://github.com/gradle/gradle/pull/621/files#diff-7193b85bfb11e9658cebe0b527f463a0R66
Furthermore we should remove remaining [[,]] and == from the following line to conform to POSIX standard (use single character versions of those instead):
https://github.com/alexproca/gradle/blob/e4135019b30a74b34c23352ee05b1526c0648244/subprojects/plugins/src/main/resources/org/gradle/api/internal/plugins/unixStartScript.txt#L158
@alexproca would you mind to have a look at this and check if it works for you? And if yes, incorporate these changes. Then we should be able to go forward with integrating this. Thanks a lot.

Thank you @alexproca for your contribution! This has been integrated now and will be part of the Gradle 3.2 release.

@jjohannes Can you please create an internal review via Crucible and link to from here?

Internal Review: https://code-review.gradle.org/cru/REVIEW-6235

Great guys, small features like this one make people a bit more open to use this great tool. Good job


FAQ Spacing

starting at 'will there be buses?'. Q should be left, not directly below prior question.

With the way its currently designed, a quick fix is to rearrange the questions until it works :P I'll look into a better way later but for now this is the only way to do it with floats


Install description shows supported Sublime Text versions as 2 & 3

versus Prettify/Minify/Query/Goto/Validate/Lint JSON plugin for Sublime Text 3 & 4 on the README.md file.

@dzhibas Can you update the repo Description to Prettify/Minify/Query/Goto/Validate/Lint JSON plugin for Sublime Text 3 & 4

thank you guys, this is done


Add modular safeguard support

My team recently came across a really nasty issue where spring kept our ActiveRecord::Base.connection_config cached. In that case, the current ENV var based safeguards failed us (luckily nobody was seriously injured).
For example,
# First, let's run a console
> DATABASE_URL=$(heroku config:get DATABASE_URL -a my-prod-app) bin/rails console

# :tada: we're running tests against the old DATABASE_URL even though it's not set
> bin/rspec

There are lots of different ways to get into this scenario (like other code loaders or multiple ORMs that use other variables). While checking for the ENV vars works for some low hanging fruit, it doesn't let ORMs (or maybe even other app/test frameworks) make more intelligent decisions.
We actually just added this to our test suite and it works great (based on the idea in https://github.com/DatabaseCleaner/database_cleaner/pull/521#issuecomment-380757595)
# Simplified version
DatabaseCleaner::Safeguard::CHECKS << Class.new do
	def run
    	# Prevent running tests against protected environments
        #   - This is the same mechanism that the `rake` tasks use so you can't
        #     run destructive operations like `db:reset` against production
        ::ActiveRecord::Tasks::DatabaseTasks.check_protected_environments!
    end
end

I think it could be very useful to modularize the concept of a Safeguard so that various ORM modules could provide their own (the above case could something like DatabaseCleaner::ActiveRecord::Safeguard::ProtectedEnvironment).
I would be more than willing to work on this, but wanted to gauge interest and possibly talk about some design decisions before going ahead with it.

@thefotios I really like this idea. We're on the verge of releasing v2.0.0, so let's circle back to this after the release is made and we can look at figuring out doing something with this for v2.1.


Change video quality depends of internet speed

This feature can save a lot of traffic for users, examples like youtube works

This isn’t something we’d build into the player. Better done with HLS or similar.

Add the following code in the

Add the following code in the

i'm also experiencing this, any clue?


AL:GO! fails with System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>

After going directly to vs code on the VM the command AL:GO fails with:
System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>...
Unhandled Exception: System.AggregateException: One or more errors occurred. ---> System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
--- End of inner exception stack trace ---
at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.MessageWriter..ctor(Stream outputStream, IMessageSerializer messageSerializer)
at Microsoft.Dynamics.Nav.EditorServices.Protocol.Channel.StdioServerChannel.Initialize(IMessageSerializer messageSerializer) in C:\Agent_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Channel\StdioServerChannel.cs:line 27
at Microsoft.Dynamics.Nav.EditorServices.Protocol.Channel.ChannelBase.Start(MessageProtocolType messageProtocolType, ProtocolEndpointCompletionSource completionSource) in C:\Agent_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Channel\ChannelBase.cs:line 40
at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.ProtocolEndpoint.d__4.MoveNext() in C:\Agent_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\MessageProtocol\ProtocolEndpoint.cs:line 27
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Prod.EditorServices.Host.Program.Main(String[] args) in C:\Agent_work\47\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Host\Program.cs:line 103
[Error - 8:44:21 AM] Connection to server got closed. Server will not be restarted.
Any idea?
Kind regards,
Sebastian

You don't state which version you are deploying, so I can only guess that you are running into the issue, Erik is describing here: https://dynamicsuser.net/nav/b/admin/posts/al-crash-with-dynamics-nav-2018-cu5-109454445#.Wv8-cD1OnVQ.twitter

Hi Freddy,
thanks!
Best,
Sebastian


PKG_CHECK_MODULES on Ubuntu 14.04.5

Hi,
I'm on compiling on Ubuntu 14.04.5 at ./configure stage and got error below.
I don't need to install training tools.
# ./configure
<skip>
configure: WARNING: Training tools WILL NOT be built because of missing icu library.
configure: WARNING: Try to install libicu-devel package.
./configure: line 17228: syntax error near unexpected token `pango,'
./configure: line 17228: `PKG_CHECK_MODULES(pango, pango, have_pango=true, have_pango=false)'

Here's the autoconf version
# autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

How can to fix it?
Thanks,

What version of tesseract you try to build?

3.05.00dev
download the zip from github

did you run ./autogen.sh as stated in https://github.com/tesseract-ocr/tesseract/blob/master/INSTALL.GIT.md?

Oops forgot to mention. I run it and looks OK.
# ./autogen.sh Running aclocal Running libtoolize libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, config'.
libtoolize: copying file config/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, m4'.
libtoolize: copying file m4/libtool.m4' libtoolize: copying file m4/ltoptions.m4'
libtoolize: copying file m4/ltsugar.m4' libtoolize: copying file m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
Running autoheader
Running automake --add-missing --copy
configure.ac:321: installing 'config/compile'
configure.ac:86: installing 'config/config.guess'
configure.ac:86: installing 'config/config.sub'
configure.ac:69: installing 'config/install-sh'
configure.ac:69: installing 'config/missing'
api/Makefile.am: installing 'config/depcomp'
Running autoconf
All done.
To build the software now, do something like:
$ ./configure [--enable-debug] [...other options]
`

Hmmm... What the right solution on this? Thanks

Try
./autogen.sh
autoreconf -ivf
./configure
ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com
On Wed, Aug 31, 2016 at 5:28 PM, Bayu Widyasanyata<EMAIL_ADDRESS>
wrote:

Hmmm... What the right solution on this? Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/405#issuecomment-243742032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_o6yjw6iYBVnU4C7zEuaFQ5PHF-gmks5qlWxMgaJpZM4JxZUl
.

@billydekid
What's the output of dpkg -l | grep pkg-config ?

@billydekid : I am sorry I misunderstood your comment - I thought it is fixed.

@Shreeshrii it works! thanks bro! :+1:  taken from autoreconf man page
By default, it only remakes those files that are older than their sources.
@amitdo here's the output:
# dpkg -l | grep pkg-config
ii  pkg-config                            0.26-1ubuntu4                       amd64        manage compile and link flags for libraries

Should this "autoreconf -ivf" add to wiki?
Thanks!

Just add some notes. The problem still exist until we should also install the pango lib dev (apt-get install libcogl-pango-dev). I thought it confuses as described on Wiki (https://github.com/tesseract-ocr/tesseract/wiki/Compiling), while it's not necessary to install (lib pango dev) if we're not plan to install training tools.

@billydekid: Does it mean that have to install pango-dev to fix problem? If yes, that it is bug that need to be fixed! (in this case please reopen this issue)

Just add some notes. The problem still exist until we should also install the pango lib dev (apt-get install libcogl-pango-dev). I thought it confuses as described on Wiki (https://github.com/tesseract-ocr/tesseract/wiki/Compiling), while it's not necessary to install (lib pango dev) if we're not plan to install training tools.

That was happened to one of my server. To ensure I will reinstall from fresh on my new vm box, and update / or reopen this issue if it problems.

libcogl-pango-dev is not needed by Tesseract!
libcogl-pango-dev has these dependencies:
libpango1.0-dev
libcairo2-dev
pkg-config (recommended)

Hi, Just want to update if it was fine when I installed without pango lib-dev packages (no training tools). Just got WARN messages on config.log. Thanks!


Fix typo in signing details

A small typo, but one that made the sentence much harder to understand until I figured out what it was actually trying to say. ;)

LGTM


Make external labels available in federation matchers

What did you do?
I am experimenting with horizontal scalability, sharding and multiple cross-federated servers.
What did you expect to see?
External labels in federation matchers.
What did you see instead? Under which circumstances?
No external labels in federation matchers. Always.
In a multiple cross-federated setup external labels are not on every time series so those can be used to filter some targets.
Find below a sample setup which will use the requested feature:
global:
 external_labels:
  shard: 0
 scrape_interval: 15s
 scrape_timeout: 10s
 evaluation_interval: 10s

rule_files:
 - /etc/prometheus/recording.rules
 - /etc/prometheus/alerting.rules

alerting:
 alert_relabel_configs:
 - source_labels: [shard]
   action: replace
   replacement: 'all'
   target_label: shard

scrape_configs:

 - job_name: 'federate'
   honor_labels: true
   metrics_path: /federate
   params:
    match[]:
     - '{shard=~"1|2"}'
   static_configs:
    - targets:
      - 'master-0:9090'
      - 'master-1:9090'
      - 'master-2:9090'

 - job_name: 'node'
   file_sd_configs:
    - files:
      - /etc/prometheus/targets/node.yml
   relabel_configs:
   - source_labels: [__address__]
     modulus: 3
     target_label: __tmp_hash
     action: hashmod
   - source_labels: [__tmp_hash]
     regex: ^0$
     action: keep

This was discussed previously in #1811 and is intended behaviour.

I am just wondering if now I have a valid use case for this feature to be implemented. On the other hand I can solve it by simply adding a static label to all my jobs.

The purpose of external labels is to uniquely identify Prometheus servers. Thus filtering on them isn't of much use, as you're already talking to the Prometheus server you want to.

Ok, I guess I am trying to (ab)use it. Thank you for the clarification.


Too many events on project grant audit

Describe the bug
The change log on a project grant shows to many changes. It looks like there are all events from the whole project shown and not only of the project grant.
To Reproduce
Steps to reproduce the behavior:

Go to a projec grant in the console
See last changes
To many events

Expected behavior
Should only show events from the project grant
Screenshots

@hifabienne what about this ones prio?

i fixed this while i had to fix other project grant stuff 😄


Add DIN (wf_standard-font) to Package

The DIN font used in most visuals - specified as wf_standard-font in CSS - is not included in custom visuals. We can add this in so that if someone does specify wf_standard-font as a font family, then they will get a consistent result with other visuals.

Resolved in build 158


Installation abort On raspberry Pi with latest O/S version

VSCode Version: Trying to install
OS Version: root@raspi3~# uname -a
Linux raspi3.maison.ca 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux

Steps to Reproduce:
1.Run the installer (See screen output below)
2.
root@raspi3~# uname -a
Linux raspi3.maison.ca 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux
root@raspi3~# cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
root@raspi3~# . <( wget -O - https://code.headmelted.com/installers/apt.sh )
--2017-05-21 10:55:35--  https://code.headmelted.com/installers/apt.sh
Resolving code.headmelted.com (code.headmelted.com)... <IP_ADDRESS>, <IP_ADDRESS>, 2400:cb00:2048:1::681b:bb50, ...
Connecting to code.headmelted.com (code.headmelted.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-sh]
Saving to: ‘STDOUT’

                                           [ <=>                                                                                ]   2.26K  --.-KB/s   in 0.001s

2017-05-21 10:55:35 (3.77 MB/s) - written to stdout [2313]
Detecting architecture...
Architecture detected as armv7l...
Installing bintray GPG key...
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.j3Gh0veG7K --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
gpg: requesting key D401AB61 from hkp server keyserver.ubuntu.com
gpg: key D401AB61: "Bintray (by JFrog<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Done!
Installing headmelted GPG key...
OK
Done!
Installing headmelted repository...
deb https://dl.bintray.com/headmelted/deb-code-oss
Repository install complete.
Updating APT cache...
E: Malformed line 4 in source list /etc/apt/sources.list (dist)
E: The list of sources could not be read.
Done!
Installing Visual Studio Code...
Reading package lists... Error!
E: Malformed line 4 in source list /etc/apt/sources.list (dist)
E: The list of sources could not be read.
E: The package lists or status file could not be parsed or opened.
Visual Studio Code install failed.
Connection to raspi3 closed.
Reconnect to raspberry Pi because connection was closed
root@holmes:~# ssh raspi3
Last login: Sun May 21 10:52:26 2017 from holmes.maison.ca
root@raspi3~# cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
deb https://dl.bintray.com/headmelted/deb-code-oss
root@raspi3~#

I have found that in order to fix the 'Malformed line' error, the line in /etc/apt/sources.list should be changed from this:
deb https://dl.bintray.com/headmelted/deb-code-oss

...to this:
deb https://dl.bintray.com/headmelted/deb-code-oss/ wheezy main

To finish the installation, update your apt-get sources and then install code-oss:
apt-get update
apt-get install -y code-oss

I considered making a pull request to fix this issue, but I'm not sure if the edits to sources.list will break something on previous versions. Would you happen to know, @headmelted?

Thank You !!!
On Thu, Jun 8, 2017 at 8:50 PM, Jen Garcia<EMAIL_ADDRESS>wrote:

I have found that in order to fix the 'Malformed line' error, the line in
/etc/apt/sources.list should be changed from this:
deb https://dl.bintray.com/headmelted/deb-code-oss
...to this:
deb https://dl.bintray.com/headmelted/deb-code-oss/ wheezy main
To finish the installation, update your apt-get sources and then install
code-oss:
apt-get update
apt-get install -y code-oss
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/headmelted/codebuilds/issues/20#issuecomment-307265646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGFDCTE2DUzOdaY9v8qU86QUJ_-UhOlMks5sCJa9gaJpZM4Nhn6X
.

Hi, I've now switched the repository from bintray to packagecloud (bintray abruptly locked the repo and asked me to use their artifactory product instead, frustratingly).
Can you try a fresh install from the script now on the website (so I know you're also running the latest build) and post back here your result?

Just Tried it seem to install correctly, but when I run "code-oss" nothing
happen .
See Screen output below
root@raspi3/etc# . <( wget -O -
https://code.headmelted.com/installers/apt.sh )
--2017-06-14 09:20:38--  https://code.headmelted.com/installers/apt.sh
Resolving code.headmelted.com (code.headmelted.com)... <IP_ADDRESS>,
<IP_ADDRESS>, 2400:cb00:2048:1::681b:bb50, ...
Connecting to code.headmelted.com (code.headmelted.com)|<IP_ADDRESS>|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-sh]
Saving to: ‘STDOUT’

                      [ <=>                           ]   2.29K

--.-KB/s   in 0.001s
2017-06-14 09:20:38 (3.10 MB/s) - written to stdout [2340]
Detecting architecture...
Architecture detected as armv7l...
Installing headmelted GPG key...
OK
Done!
Installing headmelted repository...
deb https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial main
Repository install complete.
Updating APT cache...
 Done
W: Duplicate sources.list entry
https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf
Packages
(/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_xenial_main_binary-armhf_Packages)
W: You may want to run apt-get update to correct these problems
Done!
Installing Visual Studio Code...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
code-oss
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 40.8 MB of archives.
After this operation, 1,478 kB disk space will be freed.
Get:1 https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main
code-oss armhf 1.14.0-1497385449 [40.8 MB]
Fetched 40.8 MB in 48s (840 kB/s)
Reading changelogs... Done
(Reading database ... 146272 files and directories currently installed.)
Preparing to unpack .../code-oss_1.14.0-1497385449_armhf.deb ...
Unpacking code-oss (1.14.0-1497385449) over (1.14.0-1497093446) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Setting up code-oss (1.14.0-1497385449) ...
Visual Studio Code install complete.
Installing git...
Reading package lists... Done
Building dependency tree
Reading state information... Done
git is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
git install complete.
Installing any dependencies that may have been missed...
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Missed dependency install complete.
Installation complete!
You can start code at any time by calling "code-oss" within a terminal.
A shortcut should also now be available in your desktop menus (depending on
your distribution).
root@raspi3/etc# logout
jacques@raspi3:~$ code-oss
jacques@raspi3:~$ uname -a
Linux raspi3.maison.ca 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017
armv7l GNU/Linux
jacques@raspi3:~$ date
Wed Jun 14 09:44:45 EDT 2017
jacques@raspi3:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
jacques@raspi3:~$
On Wed, Jun 14, 2017 at 6:50 AM, Jay Rodgers<EMAIL_ADDRESS>wrote:

Hi, I've now switched the repository from bintray to packagecloud (bintray
abruptly locked the repo and asked me to use their artifactory product
instead, frustratingly).
Can you try a fresh install from the script now on the website (so I
know you're also running the latest build) and post back here your result?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/headmelted/codebuilds/issues/20#issuecomment-308395635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGFDCXKqu3QuHDpt8pWTlhyQXN1_kFb4ks5sD7rtgaJpZM4Nhn6X
.

Can I ask you to try a fresh install from the script one last time?
I've made changes to the toolchain to use Debian Jessie with emdebian, rather than Ubuntu Ports, which should take the base package versions required back to a release that will hopefully work for everyone (Jessie / Trusty).

Yes it is Working Now !!!! Great !
I had to set my DISPLAY environment variable (Which I tought was already
set) to make it work.
jacques@raspi3:~$ export DISPLAY=<IP_ADDRESS>:0
jacques@raspi3:~$ code-oss
Here is the output of the installation below
Thanks Again
root@raspi3~# date
Fri Jun 16 11:29:07 EDT 2017
root@raspi3~# uname -a
Linux raspi3.maison.ca 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017
armv7l GNU/Linux
root@raspi3~#
root@raspi3~# . <( wget -O - https://code.headmelted.com/installers/apt.sh )
--2017-06-16 11:29:19--  https://code.headmelted.com/installers/apt.sh
Resolving code.headmelted.com (code.headmelted.com)... <IP_ADDRESS>,
<IP_ADDRESS>, 2400:cb00:2048:1::681b:ba50, ...
Connecting to code.headmelted.com (code.headmelted.com)|<IP_ADDRESS>|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-sh]
Saving to: ‘STDOUT’

                                    [ <=>
                                    ]   2.29K  --.-KB/s   in 0.001s

2017-06-16 11:29:20 (3.45 MB/s) - written to stdout [2340]
Detecting architecture...
Architecture detected as armv7l...
Installing headmelted GPG key...
OK
Done!
Installing headmelted repository...
deb https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial main
Repository install complete.
Updating APT cache...
 Done
W: Duplicate sources.list entry
https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf
Packages
(/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_xenial_main_binary-armhf_Packages)
W: Duplicate sources.list entry
https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf
Packages
(/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_xenial_main_binary-armhf_Packages)
W: You may want to run apt-get update to correct these problems
Done!
Installing Visual Studio Code...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
code-oss
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 40.8 MB of archives.
After this operation, 229 kB of additional disk space will be used.
Get:1 https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main
code-oss armhf 1.14.0-1497617842 [40.8 MB]
Fetched 40.8 MB in 55s (740 kB/s)
Reading changelogs... Done
(Reading database ... 146079 files and directories currently installed.)
Preparing to unpack .../code-oss_1.14.0-1497617842_armhf.deb ...
Unpacking code-oss (1.14.0-1497617842) over (1.14.0-1497385449) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Setting up code-oss (1.14.0-1497617842) ...
Visual Studio Code install complete.
Installing git...
Reading package lists... Done
Building dependency tree
Reading state information... Done
git is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
git install complete.
Installing any dependencies that may have been missed...
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Missed dependency install complete.
Installation complete!
You can start code at any time by calling "code-oss" within a terminal.
A shortcut should also now be available in your desktop menus (depending on
your distribution).
root@raspi3~#
root@raspi3~#
root@raspi3~# code-oss
It is recommended to start vscode as a normal user. To run as root, you
must specify an alternate user data directory with the --user-data-dir
argument.
root@raspi3~# code-oss --user-data-dir /home/jacques
It is recommended to start vscode as a normal user. To run as root, you
must specify an alternate user data directory with the --user-data-dir
argument.
root@raspi3~#
root@raspi3~# su - jacques
jacques@raspi3:~$ code-oss
jacques@raspi3:~$
YES IT IS WORKING
jacques@raspi3:~$ export DISPLAY=<IP_ADDRESS>:0
jacques@raspi3:~$ code-oss
jacques@raspi3:~$
On Fri, Jun 16, 2017 at 10:03 AM, Jay Rodgers<EMAIL_ADDRESS>wrote:

Can I ask you to try a fresh install from the script one last time?
I've made changes to the toolchain to use Debian Jessie with emdebian,
rather than Ubuntu Ports, which should take the base package versions
required back to a release that will hopefully work for everyone (Jessie /
Trusty).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/headmelted/codebuilds/issues/20#issuecomment-309034274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGFDCX2X8XMii5uoUy_WS7ExFkfA-fR-ks5sEoscgaJpZM4Nhn6X
.

 Done
W: Duplicate sources.list entry https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf Packages (/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_xenial_main_binary-armhf_Packages)
W: You may want to run apt-get update to correct these problems
how can i fix it?
thanks.

Interesting.. You shouldn't have two entries in there. I may need to put a
check on the script in case of multiple runs.

Find the FIRST line that ENDS with this:
https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf
(It should look something like this:)
deb [arch=armhf] https://packagecloud.io/headmelted/codebuilds/ubuntu/
xenial/main
armhf
Delete that line from the file after checking that there's a duplicate line
further down.
Once this is done save, exit, and try the update again. If it doesn't work
please reply with the terminal output so I can see what's happening.
Thanks!
 Done
W: Duplicate sources.list entry https://packagecloud.io/
headmelted/codebuilds/ubuntu/ xenial/main armhf Packages
(/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_
xenial_main_binary-armhf_Packages)
W: You may want to run apt-get update to correct these problems
how can i fix it?
thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/headmelted/codebuilds/issues/20#issuecomment-320739886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKYVoEMraXLcxf1ltPYrlAr0MK6RQ-gVks5sV1SBgaJpZM4Nhn6X
.

I have been following this article to use a 4 pin DHT11 sensor on a Raspberry Pi:
http://www.circuitbasics.com/how-to-set-up-the-dht11-humidity-sensor-on-the-raspberry-pi/#
I have a Raspberry Pi-3 with the latest Jessie installed and wanted to try the Python example:
I did a sudo apt-get-update, then
followed the instructions:
sudo apt-get install git-core
git clone https://github.com/adafruit/Adafruit_Python_DHT.git
cd Adafruit_Python_DHT
sudo apt-get install build-essential python-dev
sudo python setup.py install
Then I tried to run the program snippet:
#!/usr/bin/python
import sys
import Adafruit_DHT
while True:
humidity, temperature = Adafruit_DHT.read_retry(11, 4)
print 'Temp: {0:0.1f} C  Humidity: {1:0.1f} %'.format(temperature, humidity)
And got these errors:
Traceback (most recent call last):
File "dht11_test.py", line 7, in
humidity, temperature = Adafruit_DHT.read_retry(11, 4)
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 94, in read_retry
humidity, temperature = read(sensor, pin, platform)
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 80, in read
platform = get_platform()
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 55, in get_platform
from . import Raspberry_Pi_2
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/Raspberry_Pi_2.py", line 22, in
from . import Raspberry_Pi_2_Driver as driver
ImportError: cannot import name Raspberry_Pi_2_Driver
I did another sudo apt-get-update and repeated the process above.
I did notice this message - but do not know how to resolve it:
Reading package lists... Done
W: Duplicate sources.list entry https://packagecloud.io/headmelted/codebuilds/ubuntu/ xenial/main armhf Packages (/var/lib/apt/lists/packagecloud.io_headmelted_codebuilds_ubuntu_dists_xenial_main_binary-armhf_Packages)
W: You may want to run apt-get update to correct these problems
How can I resolve the  "W:" messages or
the "ImportError: cannot import name Raspberry_Pi_2_Driver" messages,
Please?
Regards

I believe, although I'm not certain, that this should be resolved with the black-screen fixes in the latest release, but let me know if this is not the case.


Split TWCoinTypeConfigTests into small files

TWCoinTypeConfigTests becomes quite big now, easy to cause conflicts when adding multiple new coins, we can split it into small files and put them under each blockchain folder.
we can also replace dummy tx id 123 to real tx id

Proposed steps:

Update TWCoinTypeConfigTests to be in sync with current coins.json
Reorganize such that instead of test cases per use case (about 8) there should be test cases per coin, containing all use cases
Split the tests in separate files, one per coin

A helper script is probably useful.  I start working on this.

Don't forget to update the documents: https://developer.trustwallet.com/wallet-core/newblockchain#blockchain-definitions

PRs #696 and https://github.com/trustwallet/developer/pull/60 merged, one leftover: update branch ton-address.


Bump to 0.7.3

Just released 3 days ago. 😄

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Release

[x] Bump __version__ in __init__.py. Use semantic versioning to decide whether it's a major, minor, or patch bump.
[x] Make a release commit: git commit -m 'RLS: v0.2.0'
[x] Push the RLS commit git push upstream master: https://github.com/pydata/pydata-sphinx-theme/pull/530
[ ] Make a GitHub release

[x] Call the release the current version, e.g. v0.2.0
[x] In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
[x] In the Target: dropdown, pin it to the release commit that you've just pushed.
[x] Add release notes in the field below (if it's a minor/major version bump)
If you wish, use github-activity to generate a changelog, eg github-activity pydata/pydata-sphinx-theme --since v0.2.2 --until v0.3.0.

CANCELED THE RELEASE PROCESS HERE

[ ] Confirm that this github action job has completed successfully in the actions tab
[ ] Confirm that the PyPI version is updated
[ ] Celebrate, you're done!

I didn't yet have time to look into https://github.com/pydata/pydata-sphinx-theme/pull/502#issuecomment-951642507, but since that's a regression, I would like to see it either fixed or reverted for now, before doing a release.

hmm - do we have that encoded in an issue? Given that we've already made a release since that PR was made, I think we've already shipped this regression. For now, I've stopped the release process and will delete the tag.
But FWIW, I think we should just release early and often even if there are minor regressions, as long as there's an issue to track the improvement, unless the regression is really major. If we have an issue that we think must block a release, why don't we use a github label for this like block-release? Otherwise it'll be really hard to know when to intentionally not release.

Yeah, I should already have long ago created an issue, sorry .. Or just reverted it once I discovered the regression, until we have a fix (which would ensure master is in a releasable state)
I think it's a good idea to have a policy about having the main branch in a releasable state (so someone can always do a release), and if not have a label for issues that would block a release, as you propose.

Given that we've already made a release since that PR was made, I think we've already shipped this regression.

The previous release was from a branch, so didn't include that commit

BTW, I think it's a relatively major regression, if you have a site with a sidebar that doesn't fit a single page, then it's quite unusable if it doesn't center on where you are.
But I can also take a look at it now, so we can do a 0.8.1 release quickly instead of deleting 0.8.0

I've already stopped the release process, so we don't need to release something new right now, but happy to discuss w/ you and re-release if you like. The main reason that I wanted to release now was because I consider #526 to be a pretty big bug (on sites w/o an image logo, the text padding is pretty bad right now).
I opened up https://github.com/pydata/pydata-sphinx-theme/issues/532 to discuss a release policy, so we don't lose track of that one. Happy to iterate there.


Feature request: Include custom domain base path mapping on zappa settings

Context
When deploying an application using zappa there is no option to specify the base path mapping on API gateway custom domain configuration. With this limitation it is not possible to use the same domain to deploy different APIs changing only the  base path.

Expected Behavior

If a user want to deploy an API using an existing domain in a different base path he specifies the base_path option in zappa settings stage configuration and zappa create/update base path mappings according to this configuration.
Actual Behavior

There is no option to make this configuration.
Possible Fix

Include an option on stages configuration to specify the base path to use on custom domain mapping.
Change certify command to do the base path mapping configuration on AWS API Gateway.
Steps to Reproduce

N/A
Your Environment

N/A

i think this issue can be closed. the feature has been merged in (see above).
just use the base_path option in your apps config. its also documented in the readme:
"base_path": "your-base-path", // Optional base path for API gateway custom domain base path mapping. Default None.

It was resolved in PR #1505


Fix for expired profiles when lifetime isn't used.  issue #1679

(cherry picked from commit a6813063f3fbab31c486d5c6a1b632db67db72bc)
Conflicts:
pac4j-oidc/src/test/java/org/pac4j/oidc/profile/OidcProfileTests.java
Before submitting any pull request, please read the contribution guide: http://www.pac4j.org/docs/contribute.html

Thanks again


QRCoder is generating a wrong QRCode

Bug found.
When you use QRCoder for rendering a QRCode for the number 46821232 it wil create a wrong QRcode with another number 46921232.
You can try yourself at the demo. https://www.aspsnippets.com/Demos/880/
How is this possible?

Thanks  Raffael Herrmann ,
Trying but there is an error. See below.
PM> Install-Package QRCoder
Install-Package : 'QRCoder' already has a dependency defined for
'System.Drawing.
Common'.
At line:1 char:16

Install-Package <<<<  QRCoder

CategoryInfo          : NotSpecified: (:) [Install-Package],
InvalidOperat
ionException
FullyQualifiedErrorId : NuGetCmdletUnhandledException,
NuGet.PowerShell.Com
mands.InstallPackageCommand

PM>
2018-06-03 8:24 GMT+02:00 Raffael Herrmann<EMAIL_ADDRESS>
This is possible because aspsnippets provides a really old version of this
library including a bug. I already wrote them twice to replace the link,
but they don't react. Have a look at #113
https://github.com/codebude/QRCoder/issues/113 or #67
https://github.com/codebude/QRCoder/issues/67
To "fix" your problem just use the current version of this library from
Nuget as explained here: https://github.com/codebude/QRCoder
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/codebude/QRCoder/issues/130#issuecomment-394140319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmBSpfFLGLEeg21wDyWktDKlrA52afnOks5t44E5gaJpZM4UX4Uy
.

Hi @HJFB
I never saw this error, but this reads like, an outdated Nuget package manager is the source of this error. Try to update it, like described here: https://stackoverflow.com/questions/25725545/nuget-x-already-has-a-dependency-defined-for-y

Hi  Raffael Herrmann,
Thank you for your quick response.
I have updated Nuget package manager and tried again. Unfortunately it did
not help. Maybe there is another way to get the latest QRcoder.dll file?
Thanks again, kind regards,
Met vriendelijke groet,
Herman Becking
<EMAIL_ADDRESS>06-51446612 <06%2051446612>
Customer View
Palmweg 35
3941 BN  DOORN
Postbus 421
3700 AK  Zeist
2018-06-06 22:39 GMT+02:00 Raffael Herrmann<EMAIL_ADDRESS>
Hi @HJFB https://github.com/HJFB
I never saw this error, but this reads like, an outdated Nuget package
manager is the source of this error. Try to update it, like described here:
https://stackoverflow.com/questions/25725545/nuget-x-
already-has-a-dependency-defined-for-y
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codebude/QRCoder/issues/130#issuecomment-395206020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmBSpfjxZUcD-zKT7hpmwpgw9WeGGB5Rks5t6D32gaJpZM4UX4Uy
.

Hi @HJFB ,
there seems to be something wrong with your Nuget. Maybe the update didn't work out... Another solution would be to download the project from Github ( https://github.com/codebude/QRCoder/archive/master.zip ), then open the QRCoderProject.sln and compile/create the QRCoder project yourself.


Wrong method name in Step 9

In the description, says to change some code in the method updateRepoListFromInputupdateRepoListFromInput(), but the right name is updateRepoListFromInput()

Codelab updated.
Thanks for reporting this!

Hi, I want to add something related to the step 9. In the description says to update initSearch method and at every new emission of the flow, let's scroll to position 0 adding this code:

But at the end, in the Activity with the complete code shows this:


Error Module Build Failed when using top-level await.

🐞 bug report
Description
When I enable top-level await in Tyoescrpt. (setting module do esnext  and set target to es2017 (or higher)  TS and JS support using top-level await.
That means that this becomes valid:
  const { BrowserModule } = await import('@angular/platform-browser');
  const { NgModule } = await import('@angular/core');

  const { AppRoutingModule } = await import('./app-routing.module');
  const { AppComponent } = await import('./app.component');
  const { HomeComponent } = await import('./home/home.component');
  const { HttpClientModule } = await import('@angular/common/http');

  @NgModule({
    declarations: [AppComponent, HomeComponent],
    imports: [BrowserModule, AppRoutingModule, HttpClientModule],
    providers: [],
    bootstrap: [AppComponent],
  })
  export class AppModule {}

This is now valid typescript, which translates into valid modules.
However, When I try to use this with the CLI, I'm facing a syntax error?

This is not a syntax error from typescript. Where does it come from, and why is it there?
When this would work, it enables a way more fine-grained control over lazy-loading, and would cut down bundle-size in a huge way.
🌍  Your Environment
Angular Version:

Angular CLI: 11.2.2
Node: 14.15.5
OS: linux x64

Angular: 11.2.3
... animations, common, compiler, compiler-cli, core, elements
... forms, language-service, platform-browser
... platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1102.2
@angular-devkit/build-angular   0.1102.2
@angular-devkit/core            11.2.2
@angular-devkit/schematics      11.2.2
@angular/cli                    11.2.2
@schematics/angular             11.2.2
@schematics/update              0.1102.2
ng-packagr                      11.0.3
rxjs                            6.6.3
typescript                      4.1.5

This is caused by Webpack 4 which doesn't support top level await. With Webpack 5 it is possible to enable top-level await but it's still in experimental mode.
@clydin thoughts about enabling this experimental feature?

Top-level await is currently in stage 3 and changes are still being made to the spec based on issues found during implementation.  Correct implementation of the spec is also complex and defects can result in hard to troubleshoot problems within applications.  Once the Webpack considers its implementation stable and spec compliant, the Angular CLI should be able to enable it by default (assuming Webpack does not enabled it by default first).
Something else to also consider is that top level await usage is recommended to be evaluated from a total application performance perspective.  This is especially relevant in that its usage can cause tasks that can be parallelized to be execute serially and not just in the containing module but also indirectly in parent modules as well.  Combined with the code splitting behavior of bundlers, there can be additional overhead regarding more module loading/parsing/evaluation as well.  The spec overview has several sections discussing this topic: https://github.com/tc39/proposal-top-level-await#will-top-level-await-cause-developers-to-make-their-code-block-longer-than-it-should

Following a convo with @clydin. Let’s revisit top level await when Webpack’s implementation in non experimental and spec compliant, likely when this happen we won’t have to do any changes from our end anyways to support this.


Dev drive not mounted after reboot

Dev Home version
0.601.297.0
Windows build number
10.0.22631.0
Other software
No response
Steps to reproduce the bug

Create a dev drive
Store some code on it
Reboot the machine

Expected result
The dev drive should be mounted after the reboot
Actual result
The dev drive is missing.
I am able to mount the VHD manually and it restores it to the right drive letter, but I'm unsure why this doesn't happen automatically. I have another machine where this works as expected and the mounted dev drive is available after reboots.
Included System Information
No response
Included Extensions Information
No response

+1

I'm also experiencing this issue. Oddly enough I have another VHD with VMs on it that mounts automatically after a reboot.

The Virtual Disk gets automatically removed when the computer reboots.

I have done the same thing. I think I found the reason behind this:
Because the one which is still mounted is because something is stopping it from dismounting, but the other one is not getting mounted because, nothing is stopping it from dismounting. The one which is not getting dismounted should be a in a Storage Pool or something like that.

I have the same issue, a colleague mentioned his dev drive remounts on reboot.

Same problem over here!

I have the same issue. Made a scheduled task to mount it as a workaround.

@niikoo how did you do that exactly?

This is how I set it up @JonathanBout
Task Scheduler
General
Name: Auto-Mount DevDrive VHDX at Startup
When running the task, use the following user account: [I selected an account with administrative rights]
Selected Run whether user is logged in or not , Do not store password and Run with highest privileges.
Triggers

At startup
At log on

Actions
Action: Start a program
Program/script: diskpart.exe
Arguments: /S "C:\devdrive.automount.diskpart"
Conditions
Unchecked everything.
Settings
Checked the top 5 checkboxes.
Set Do not start a new instance on the last dropdown.
Create the diskpart file
Path: "C:\devdrive.automount.diskpart"
File contents:
select vdisk file="C:\devDrive.vhdx"
attach vdisk
exit

Replace "C:\devDrive.vhdx" with the path to your DevDrive VHDX file.

@niikoo thank you, it works great!

The Virtual Disk gets automatically removed when the computer reboots.

That is not true, as I stated in my OP, I have 2 VHDs. One remains mounted after reboots, the dev drive does not.

@jimmychanga, does the one which stays still, in a storage pool.

Close this if fixed.

Close this if fixed.

I don't see a workaround as a fix, @skanda890. Hope to get a proper fix that works out of the box.

No, it is not. It is a NTFS formatted local vhd. The only difference between the two are that the DEV drive is formatted with ReFS.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Nikolai Ommundsen @.>
Sent: Saturday, February 3, 2024 3:44:58 AM
To: microsoft/devhome @.>
Cc: Joe Marr @.>; Mention @.>
Subject: Re: [microsoft/devhome] Dev drive not mounted after reboot (Issue #1903)
Close this if fixed.
I don't see a workaround as a fix, @skanda890https://github.com/skanda890. Hope to get a proper fix that works out of the box.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/devhome/issues/1903#issuecomment-1925219672, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASLOXNV2X6HQK6J44TGUPDYRX2IVAVCNFSM6AAAAAA7NPUUHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGIYTSNRXGI.
You are receiving this because you were mentioned.Message ID: @.***>

@jimmychanga, Thanks.

Happening to me too, though intermittently. It seems random whether the dev drive is mounted on boot or not.

For everyone that is experiencing this problem, can you open a Feedback Hub issue under Developer Platform->Dev Drive and collect traces? Then post the link here.
Thanks,
Adam

I unmounted my dev drive in order to optimize the vhdx file, when i mounted it back it won't automount after a reboot.
Also, i can't create new dev drives, they just end up in RAW format and won't work unless i manually format them as NTFS (which defeats the whole point of dev drives)

Hi @griffi-gh, sorry to hear that. I wonder if the vhdx file was attached using diskmgmt.msc or other tools. If so, could you please detach the vhdx file using diskmgmt and retry attaching it using the System\Storage\Disks & Volumes Settings UX page? The behavior to auto-mount the vhdx files on reboot needs to be explicitly opted in and only the Settings UX for Disks & Volumes is updated to request the new behavior.
For the intermittent issue, thanks for reporting this. It will be more helpful to have the Feedback filed like @AdamBraden suggested as that would include the required logs. In this case, the System event log should have additional info on why the attempt to attach the vhd(x) failed.

The behavior to auto-mount the vhdx files on reboot needs to be explicitly opted in and only the Settings UX for Disks & Volumes is updated to request the new behavior.

This explains why it doesn't work for me. I mount the volume using explorer or from a shell script, mounting it through Settings does not work for me (probably due to some company managed policy).

Due to company-wide security policies dev drive creation via settings panel is not possible. For testing this feature, we used an elevated powershell with something along new-VHD ... | Mount-VHD | ... to create the dev drive. Its gone after a reboot.

The behavior to auto-mount the vhdx files on reboot needs to be explicitly opted in and only the Settings UX for Disks & Volumes is updated to request the new behavior.

Indeed, there is a new _ATTACH_VIRTUAL_DISK_FLAG called ATTACH_VIRTUAL_DISK_FLAG_AT_BOOT, added sometime around the end of 2023. You can pass this argument to AttachVirtualDisk to auto-mount VHDs. WIM and PowerShell have not been enlightened to do this.
I've written a sample C# app that will enable auto-mounting for a given VHD(X): citelao/automount-vhd. Most of the code is written by my friend @jazzdelightsme; I adapted it to CsWin32.
Note: I work for Microsoft, but I do not own these APIs.

Unfortunately, it seems this worked only once :-( Now, the script has no effect other than mounting the dev drive. Its gone after a reboot. However, I'm not sure if my company has some weird group policies that interfere somehow.

Hi @griffi-gh, sorry to hear that. I wonder if the vhdx file was attached using diskmgmt.msc or other tools. If so, could you please detach the vhdx file using diskmgmt and retry attaching it using the System\Storage\Disks & Volumes Settings UX page? The behavior to auto-mount the vhdx files on reboot needs to be explicitly opted in and only the Settings UX for Disks & Volumes is updated to request the new behavior.
For the intermittent issue, thanks for reporting this. It will be more helpful to have the Feedback filed like @AdamBraden suggested as that would include the required logs. In this case, the System event log should have additional info on why the attempt to attach the vhd(x) failed.

Differentiating VHDX files is a dangerous act that leads to these exact bugs. There is no need to treat them differently, and if they truly are different then don't use the same underlying format, make a new one. I should be able to use my VHDX file between VMs, as a dev drive etc as that is what the format is for. Having one UI do one thing with hidden flags and another do another thing is not only inconsistent but how we get security issues etc. down the road as no one checks what the other system did. Respect the API as created.
I just started using dev drives and ran into this exact issue, of course after creating my VHDX via diskman. Forcing me to use the new clunky UI for the same tech (or worse preventing me from using PowerShell) is a scary future indeed.

This has just started happening to me this week since rebuilding my machine / fresh Windows install

@matt-gribben would you mind filing a report from the Feedback Hub? You can log it under the 'Developer Platform -> Dev Drive' category and use the share option to include a link to it here.  If, like me, using a surface tablet, you have a SDHC card permanently in the machine, well, no good to put the dev drive file on that and want it to automount on boot.
Moved the file to the C: drive and mounted it, and it automounts on boot now.
Sigh.

@rickhoskins - putting a Dev Drive VHD on an SD card is not going to give you the perf benefits of Dev Drive compared to your SSD. Can you help me understand your desired scenario? If perf is not a major concern, you could just create a normal VHD and use a scheduled task to get it to mount - or put your content directly on the SD card. You could then use a folder exclusion to minimize Defender overhead (and do scheduled scans at appropriate times for the security threat/risk your project requires).

Is the only way to get traction on this the feedback hub? And if so why is there this Github repo if our bug reports come back with no response. The Dev Drive  concept is fairly DOA if you can't even mount things to it. I still have to manually mount my dev drive on every single reboot, which for me is often as I do not leave my computer on when I am not using it.

@rickhoskins - thanks for the information on your scenario. The isolation and portability of a dev drive vhd is interesting to explore if more devs operate this way.
@JosiahBradley - we are working with the file system team to fill in the gaps in the tools that support mounting and dismounting drives to ensure they support automount of a dev drive vhd. I cannot comment on a timeline at this time.

This is how I set it up @JonathanBout
Task Scheduler
General Name: Auto-Mount DevDrive VHDX at Startup When running the task, use the following user account: [I selected an account with administrative rights] Selected Run whether user is logged in or not , Do not store password and Run with highest privileges.
Triggers

At startup
At log on

Actions Action: Start a program Program/script: diskpart.exe Arguments: /S "C:\devdrive.automount.diskpart"
Conditions Unchecked everything.
Settings Checked the top 5 checkboxes. Set Do not start a new instance on the last dropdown.
Create the diskpart file
Path: "C:\devdrive.automount.diskpart" File contents:
select vdisk file="C:\devDrive.vhdx"
attach vdisk
exit

Replace "C:\devDrive.vhdx" with the path to your DevDrive VHDX file.

Here's my Task that doesn't need a extra file:
Task Scheduler
General Name: Auto-Mount DevDrive VHDX at Startup When running the task, use the following user account: [I selected an account with administrative rights] Selected Run whether user is logged in or not , Do not store password and Run with highest privileges.
Triggers

At startup
At log on

Actions Action: Start a program Program/script: powershell Arguments: Mount-DiskImage -ImagePath "C:\DevDrive.vhdx"
Conditions Unchecked everything.
Settings Checked the top 5 checkboxes. Set Do not start a new instance on the last dropdown.
Replace "C:\DevDrive.vhdx" with the path to your DevDrive VHDX file.

This just happened to me too, I cloned the git repo @citelao shared and it worked, however, I am interested in the feature in Dev Home to mount an existing disk instead of always creating a new one


SELECT WHERE ID in with duplicated IDs

Given the following SQLite table:
CREATE TABLE "users" ("id" integer NOT NULL,"name" varchar NOT NULL, PRIMARY KEY (id));

With two users:

id
name

1
user 1

2
user 2

If we manually run the following query:
SELECT * FROM users where id in (1,2,1)

It returns two rows. If we do the same with sqlfx:
const GetById = sql.resolverId('GetUserById', {
  id: S.number,
  result: UserDbo,
  resultId: (_) => _.id,
  run: (ids) => sql`SELECT * FROM users WHERE id IN ${sql(ids)}`,
});

const getUserById = (id: number) =>
  Effect.gen(function* (_) {
    const user = yield* _(
      GetById.execute(id).pipe(Effect.map(Option.map((p) => new UserDbo(p))))
    );

    return user;
  });

const main = Effect.gen(function* (_) {
const { getUserById } = yield* _(UserRepro);

const allUsers = yield* _(
  Effect.all(
    pipe(
      [1, 2, 1],
      ReadonlyArray.map((id) => getUserById(id))
    ),
    { batching: false }
  )
);

console.log(allUsers);

return null;
});

It returns 3 rows:
[
  {
    _id: 'Option',
    _tag: 'Some',
    value: UserDbo { id: 1, name: 'user 1' }
  },
  {
    _id: 'Option',
    _tag: 'Some',
    value: UserDbo { id: 2, name: 'user 2' }
  },
  {
    _id: 'Option',
    _tag: 'Some',
    value: UserDbo { id: 1, name: 'user 1' }
  }
]

If we set batching to true, it gives the following error
Exited failure state: All fibers interrupted without errors.

Is it expected? Shouldn't the code return 2 rows in both cases?
Repro

clone https://github.com/tatchi/sqlx-repro
git checkout same-id
pnpm i
./src/main.ts

Thanks 🤗 Just to be sure, it doesn't fail anymore but returns 3 rows (with duplicate user 1) both with batching on or off. Is this the expected result?

Yes, with a resolver this is the correct behaviour :)


[BUG] possible memory leak in AsyncBufferedChannel

Still figuring out whether this is a bug in my code or AsyncExtensions. I'm seeing a bunch of small leaks from AsyncBufferedChannel when used by AsyncCurrentValueSubject. Note in order to aid debugging I've modified the code to use checked continuations, although I will revert this once it is fixed.
More information as I have it, just wondering if anyone else has seen this.
relates to internal bug PADL/inferno_ui#15
STACK OF 1 INSTANCE OF 'ROOT LEAK: <Swift._ContiguousArrayStorage<AsyncExtensions.AsyncBufferedChannel<SwiftOCA.OcaProperty<SwiftOCA.OcaBoundedPropertyValue<Swift.Float>>.PropertyValue<>>.Awaiting<>>>':
18  libsystem_pthread.dylib               0x19d069d28 start_wqthread + 8
17  libsystem_pthread.dylib               0x19d06afd0 _pthread_wqthread + 228
16  libdispatch.dylib                     0x19ced06b8 _dispatch_worker_thread2 + 156
15  libdispatch.dylib                     0x19cecfea8 _dispatch_root_queue_drain + 392
14  libswift_Concurrency.dylib            0x2651dc470 swift_job_runImpl(swift::Job*, swift::ExecutorRef) + 72
13  libswift_Concurrency.dylib            0x2651db2e0 swift::runJobInEstablishedExecutorContext(swift::Job*) + 436
12  ocacli                                0x100f82e38 back deployment fallback for withCheckedContinuation<A>(isolation:function:_:) + 144  /<compiler-generated>:0
11  ocacli                                0x100f82fac closure #1 in withCheckedContinuation<A>(isolation:function:_:) + 220  /<compiler-generated>:0
10  ocacli                                0x100f7d8bc closure #1 in closure #2 in AsyncBufferedChannel.next(onSuspend:) + 728  AsyncBufferedChannel.swift:182
9   ocacli                                0x100ff9610 ManagedCriticalState.withCriticalRegion<A>(_:) + 188  Locking.swift:136
8   ocacli                                0x100f306a4 $ss13ManagedBufferCsRi__rlE25withUnsafeMutablePointersyqd_0_qd_0_SpyxG_Spyq_Gtqd__YKXEqd__YKs5ErrorRd__Ri_d_0_r0_lF + 172  /<compiler-generated>:0
7   ocacli                                0x100ff977c partial apply for closure #1 in ManagedCriticalState.withCriticalRegion<A>(_:) + 52  /<compiler-generated>:0
6   ocacli                                0x100ff96e0 closure #1 in ManagedCriticalState.withCriticalRegion<A>(_:) + 124  Locking.swift:139
5   ocacli                                0x100f83000 partial apply for closure #1 in closure #1 in closure #2 in AsyncBufferedChannel.next(onSuspend:) + 44  /<compiler-generated>:0
4   ocacli                                0x100f7e0d8 closure #1 in closure #1 in closure #2 in AsyncBufferedChannel.next(onSuspend:) + 1040  AsyncBufferedChannel.swift:188
3   libswiftCore.dylib                    0x1acd63c10 _allocateUninitializedArray<A>(_:) + 144
2   libswiftCore.dylib                    0x1ad0e27b8 swift_allocObject + 64
1   libswiftCore.dylib                    0x1ad0e24cc swift_slowAlloc + 36
0   libsystem_malloc.dylib                0x19cea8adc _malloc_zone_malloc_instrumented_or_legacy + 264
====

The leaked value is this (line 188 in my branch):
            case .idle:
              state = .awaiting([Awaiting(id: awaitingId, continuation: continuation)])
              return .suspend

Also, I suspect moving to Mutex in Synchronization might be worth it as it will save a bunch of mallocs, as will replacing generateId() with an atomic.

Another data point: we are using an AsyncCurrentValueSubject for audio metering information which is updated 60 times per second. So if there's a race, this will likely trigger it.

I also have the PR from #40 in my branch FYI (this didn't improve things though).

I can see this also when running leaks on the test suite:
STACK OF 7 INSTANCES OF 'ROOT LEAK: <Swift._ContiguousArrayStorage<AsyncExtensions.AsyncBufferedChannel<Swift.Int>.Awaiting<>>>':
18  libsystem_pthread.dylib               0x19d069d28 start_wqthread + 8
17  libsystem_pthread.dylib               0x19d06afd0 _pthread_wqthread + 228
16  libdispatch.dylib                     0x19ced06b8 _dispatch_worker_thread2 + 156
15  libdispatch.dylib                     0x19cecfea8 _dispatch_root_queue_drain + 392
14  libswift_Concurrency.dylib            0x2651dc470 swift_job_runImpl(swift::Job*, swift::ExecutorRef) + 72
13  libswift_Concurrency.dylib            0x2651db2e0 swift::runJobInEstablishedExecutorContext(swift::Job*) + 436
12  AsyncExtensionsPackageTests           0x1023971dc back deployment fallback for withCheckedContinuation<A>(isolation:function:_:) + 144  /<compiler-generated>:0
11  AsyncExtensionsPackageTests           0x102397350 closure #1 in withCheckedContinuation<A>(isolation:function:_:) + 220  /<compiler-generated>:0
10  AsyncExtensionsPackageTests           0x102391564 closure #1 in closure #1 in AsyncBufferedChannel.next(onSuspend:) + 708  AsyncBufferedChannel.swift:160
9   AsyncExtensionsPackageTests           0x10240d2c4 ManagedCriticalState.withCriticalRegion<A>(_:) + 188  Locking.swift:136
8   AsyncExtensionsPackageTests           0x102344a50 $ss13ManagedBufferCsRi__rlE25withUnsafeMutablePointersyqd_0_qd_0_SpyxG_Spyq_Gtqd__YKXEqd__YKs5ErrorRd__Ri_d_0_r0_lF + 172  /<compiler-generated>:0
7   AsyncExtensionsPackageTests           0x10240d430 partial apply for closure #1 in ManagedCriticalState.withCriticalRegion<A>(_:) + 52  /<compiler-generated>:0
6   AsyncExtensionsPackageTests           0x10240d394 closure #1 in ManagedCriticalState.withCriticalRegion<A>(_:) + 124  Locking.swift:139
5   AsyncExtensionsPackageTests           0x1023973a4 partial apply for closure #1 in closure #1 in closure #1 in AsyncBufferedChannel.next(onSuspend:) + 44  /<compiler-generated>:0
4   AsyncExtensionsPackageTests           0x102391ae4 closure #1 in closure #1 in closure #1 in AsyncBufferedChannel.next(onSuspend:) + 976  AsyncBufferedChannel.swift:166
3   libswiftCore.dylib                    0x1acd63c10 _allocateUninitializedArray<A>(_:) + 144
2   libswiftCore.dylib                    0x1ad0e27b8 swift_allocObject + 64
1   libswiftCore.dylib                    0x1ad0e24cc swift_slowAlloc + 36
0   libsystem_malloc.dylib                0x19cea8adc _malloc_zone_malloc_instrumented_or_legacy + 264
====

BTW, I've made a few other fixes on my branch to use the newer async test expectations API, use atomics, etc.

lhoward/AsyncExtensions@dabc2282009f0b223975f468d4e12bba31f3271f seems to fix this (using Array instead of OrderedSet for awaitings). Why, I don't know.

This diff unfortunately won't cleanly apply as I've fixed a bunch of other issues (e.g. using the new withTaskCancellationHandler signature). But if you are amenable to merging I will prepare a PR.

Yes, this could be it - I've gone around in circles this week looking for the leak - but I am careful to remove the reference to the task on cancellation.
https://github.com/PADL/FlutterSwift/blob/main/Sources/FlutterSwift/Channel/FlutterEventChannel.swift#L165

Also I knew leak detection isn't always completely deterministic but surely I'd still see the leak after switching to Array. I'll check if the tests are still leaking with my workaround.