Apple Wallet Integration (iOS)

Feature description
I think there should be an option to integrate certificates, passes and other cards directly in Apple Wallet, so this documents could be accessed in one central App and the same place where are already stored things like creditcards from Apple Pay, loyaltycards and tickets.
https://developer.apple.com/wallet/
So there could be displayed an „Add to Apple Wallet“ button in the details of each document, so the user can decide which of them should be added to the iOS-native Wallet-App.
I‘m not sure, if passes in the Wallet-App are stored in the Secure Enclave, but if this isn’t the case, this feature maybe could be at least provided for „simpler“ documents, like vaccination certificates.

Problem and motivation
I really think, it is a very important feature for iOS-Users to create a functionality to use the native Wallet-App for documents like these. And iOS-Users are more often looking towards such an integration, as they really like the simplicity and convenience of things like the native Wallet-App especially if they are already using stuff like Apple Pay.
This would provide a much better experience for the users and this could also help to convince more users from using digital certificates.
As I couldn’t find any information regarding this Apple Wallet topic, I’ve created this feature-request.

Is this something you're interested in working on

No.

It could also allow the certificate/QR code to be shown through Apple Wallet hands-free on the Apple Watch, without having to open the app on the iPhone.
Considering the vaccination certificate will likely be important to show when traveling and crossing borders and the digital certificate is all about making that process easier, it would make a lot of sense to have it right next to where e.g. airline boarding passes are also accessible (in Apple Wallet).

Unfortunately, this is a security and privacy concern, as already discussed in the CWA GitHub. As this would allow the QR code to be visible without any sort of user validation / passcode. We have discussed this internally and came to the conclusion to not implement it because of the security concerns and that it is out of scope.

You can disable access from Lock Screen in the iOS settings.

That's true, navigate to the "TouchID & Code" or "FaceID & Code" or just "Code" section in the Settings and switch the toggle to off for Wallet in the section "Allow access from the lock screen".

And as I said in https://github.com/corona-warn-app/cwa-wishlist/issues/503 you can only access cards which work with Apple Pay from the lockscreen https://support.apple.com/en-us/HT204003

Since we cannot make sure that this is disabled on the iPhone the app is deployed on, this is still a privacy and security issue.
@jucktnich - I can access all my card from the lock screen even those that are not Apple Pay enabled. E.g. discount codes etc.

@PaulBallmann discount cards can also be Apple Pay enable see the support article

You also cannot make sure, that the user has a code enabled at all

I have to admit that I'm disappointed and can't really understand the decision .
As the passes wouldn't be added automatically, the users would have to decide proactive, whether they want the passes and so the personal information to be accessible in such a way (without Passcode and/or verification) or not. Maybe a warning could be implemented to inform the user about that.
Also I think it is problematic too, if the device has to be unlocked to access the information and I have to hand it to a an strange person for scanning the code, verification, etc, as they would have access to the entire device and all my private data and this would be much more problematic than only my personal Information in the wallet pass.
And as in some other thread explained, there are third party apps which let you create your own passes from an image of the qr-code, so they are accessible from the wallet app even if it is not natively supported from the original app. And as the qr-code doesn't change, it would be not that much work, to get it working.
So I don't really see myself using this app actively in the future, maybe only for creating the qr-code a single time for exporting via screenshot or so.
Also it seems more like paternalism for me as it doesn't let me decide on my own if I want to use it and take the risk or not.
So my hope for this topic for now lays on other third party apps and developers which are more user oriented and implement this feature, like the Luca-App, which lets users already export the certificate as image in the photo gallery.
If it is better from an privacy standpoint to be dependant to unknown, untrusted third party developers and (maybe) closed source apps, as the official app doesn't support this features should be discussed too.

@PaulBallmann

Since we cannot make sure that this is disabled on the iPhone the app is deployed on, this is still a privacy and security issue.

But you also can't make sure that the passcode is enabled on every iPhone the app is installed, since it's still not mandatory from iOS to use a passcode.
It would also be possible to inform the users about this security risk and give instructions how to disable the feature.

@Ein-Tim - Yes, we make sure that passcode is enabled else the app won't start.
@ezadoo - Please understand that his is not in our hands. The EU did not put this into their spec and since this is privacy and security related we cannot just implement a feature that would expose a user that does not know about this issue.
Also handing over your phone to get the QR code scanned is not needed. You can unlock your phone and keep it in your hands while the QR code is scanned.

@PaulBallmann

Yes, we make sure that passcode is enabled else the app won't start.

Interesting, thank you. To which app are you referring? The example one?
I'm not sure if CovPass (the German app) has something like this implemented...

@Ein-Tim - Yes. This is implemented in the example wallet-app. I don't know how much of our core or app is used in the CovPass app.

Can someone proof/disproof if the Apple Pay integration is needed to be accessed without authentication

@jucktnich - I don’t know exactly what you mean. The apple wallet is not passcode protected by default and will let you see any certificates that are stored im the wallet on the lockscreen without authentication which goes against DGCA spec.

According to the apple support article you can only access cards with Apple Pay integration from the lockscreen "If you have a credit, debit, prepaid, store card, or a rewards card in Wallet that works with Apple Pay, double-click the Home Button from the Lock Screen to open Wallet. On iPhone X or later, double-click the Side button."

@jucktnich I have a Nespresso membership card that is only visible when the iPhone is unlocked and otherwise not accessible. Is that what you meant?

Yup, same with f.e. the iTunes pass and the tickets of the DB

@PaulBallmann
"The EU did not put this into their spec and since this is privacy and security related we cannot just implement a feature that would expose a user that does not know about this issue."
This is why I said, that a warning could (and should) be implemented, before the user adds it to the wallet, so the user is informed about the risks coming with that decision.
In this case the users themselves would know about this issue, but also could decide to take the risk, for the benefit of using Apple Wallet. I think every user should be able to decide on its own, not to have the EU to decide if the users should be able to make their own decision.
Also I think an institution like the EU and so the developers of this app could try to contact and find a solution with Apple to integrate more security for the sensitive personal informations, so that a verification with Face-ID, Touch-ID or passcode could be enabled, like it is the case for using credit-cards with Apple Pay, as from such an integration would profit millions of iPhone-Users in the entire EU.
As iOS15 in the US already supports drivers licenses in some states, so I see no reason, why not at least it should be tried to find a solution with Apple to integrate an EU-wide solution with an similar topic.

@ezadoo Something like with the driver license would be the icing on the cake

Thank your for your input on this issue. It is still not in spec nor scope. We will keep this in mind in case scope or spec change. There’s just too much fluctuation.

According to the apple support article you can only access cards with Apple Pay integration from the lockscreen "If you have a credit, debit, prepaid, store card, or a rewards card in Wallet that works with Apple Pay, double-click the Home Button from the Lock Screen to open Wallet. On iPhone X or later, double-click the Side button."

I don’t know how this changes the scope of the issue but I will bring this up and will get back to you on that.

@PaulBallmann If you can't access the card from the lockscreen (without authentication) all the security concerns vanish.

@PaulBallmann if you make it an optional step … like [Add to Wallet] as a button the USER can decide whether (s)he want's to use this feature.
I personally prefer to NOT unlock my phone for anyone who wants to see my certificate but I'd be fine if anyone can see my name on the certificate.
Also: if the certificate only shows the QR Code with encrypted data: what can ANYONE see on the locked wallet view anyway? …
I would HIGHLY recommend to think about possible implementation options here. I really don't want to carry paper work with me just to prevent unlocking my phone in a "verification situation".
Thanks,
Rico

I personally prefer to NOT unlock my phone for anyone who wants to see my certificate but I'd be fine if anyone can see my name on the certificate.

As also said in the CWA project, it seems like this won't be possible via the Apple Wallet (https://github.com/eu-digital-green-certificates/dgca-wallet-app-ios/issues/69#issuecomment-860042008).

FYI: If you want your QR-Code in your Apple Wallet now, take a look at: https://twitter.com/kkrdvc/status/1404418854231674885

The comment above me (pointing people at a 3rd party app) getting reactions will be the end result of this: people will use 3rd party apps instead. Who knows what happens to the data then? If the details are sent to the backend, we've already lost.
That, to me, is the real threat of privacy problems here - people will find a way. So from a harm minimisation perspective, imo, it makes sense to include this feature in 1st party apps so they have a trustworthy option.

I was gonna say the same thing. If you've used Pass2U, it takes several seconds to generate a pass, and it will show you an error if you're offline. This indicates that the generation does not happen locally on the phone, but details are sent to a backend. The app's developer (and probably the servers) are in Taiwan, outside the EU. I don't intend to bad-mouth the developer, they may very well have implemented everything in a super privacy-preserving way and perhaps even GDPR-compliant, but who can know? It's not open source like this app. It may very well be that every QR code is uploaded and stored in a database, secretly sold off, or one day gets hacked and thousands of vaccination certificates are leaked and obtainable on the internet. And that's the solution users are being driven to (without being aware of the risks) if the official app does not support Apple Wallet natively. Putting it in the official app means being able to inform the user of potential risks.

Thats exactly what I said in one of my comments above:

If it is better from an privacy standpoint to be dependant to unknown, untrusted third party developers and (maybe) closed source apps, as the official app doesn't support this features...

And a little explanation regarding this topic:
There are many apps for generating wallet passes, all of them are generating the passes on their backend servers.
This seems to be an intended technical/security limitation from Apple as every pass has to be signed to work in the wallet app.
And as you can't include the signing certificate with the app for obvious security reasons, the pass has to be generated on an server with the signing certificate from the developer.
So everyone using such apps have no other choice than trusting the third party developers and that they don't store the sensitive personal information or the generated passes on their servers.
But this is exactly what will happen if the official app doesn't support this feature. And as there are already some users doing this many more will follow doing the same when they have their vaccination certificate.

@felixfbecker I developed a small web app, which lets you add your certificates as a pass: CovidPass. It is developed in accordance with the GDPR and hosted in Germany.

Is it really better to have users download some third party app because they want this feature than just to clarify for the user that the wallet is accessible without a passcode? Not everyone has to use this.
Also one more thing to think about: Analog vaccination certificates also do not require a passcode and they were safe enough for us for a very long time.

I do not really understand the security concerns with having the pass on the Home Screen. The real threat here is all the validator apps that can store all scanned certificates. If we were really concerned about this we should have implemented Terminal Authentication like for ICAO Biometric Passports https://www.icao.int/publications/Documents/9303_p11_cons_en.pdf . As far as I understand, the only way to enable offline verification and limit the verification to only registered apps would be to encrypt the certificate and distribute decryption keys - like in the TA scheme to limit access to f.i fingerprints in passports.
On another note, what is the recommended process for the initial delivery of a digital version of the certificate (not paper) ? How is this done in most EU countries? In Sweden they require login with eIDAS (which many tourists of the tourists making up at least 30% of people tested do not have) to pick up Test certificates. This is a problem and means that a subject needs to visit the clinic twice to get a PDF on paper. In order to get it digitally it seems putting it in your Apple or Android Wallet in the way @marvinsxtr does it has the least security implications beyond using a photo.
This document talks about deployment via SMS https://ec.europa.eu/health/sites/default/files/ehealth/docs/digital-green-certificates_v4_en.pdf . Is this allowed? Would appreciate a pointer to a document regulating this? Or is this the authoritative source?

I don't no if this was stated before, but you can show your Medical ID on the Lockscreen (if this is activated in the settings), in the Medical ID there's you're name, DoB, weight, height, primary language, medical conditions, medical notes, allergies&reactions, medications, blood type, organ donor and you're emergency contacts. I think the data in the vaccination pass is nothing against this.

I don't no if this was stated before, but you can show your Medical ID on the Lockscreen (if this is activated in the settings), in the Medical ID there's you're name, DoB, weight, height, primary language, medical conditions, medical notes, allergies&reactions, medications, blood type, organ donor and you're emergency contacts. I think the data in the vaccination pass is nothing against this.

Exactly, that you have been vaccinated or tested negative is hardly something to hide like an STD.

CovPass and Corona-Warn-App (the Wallet apps from Germany) now both can export PDFs of the saved DCCs.
They both say that this PDF contains private data and should only be shown to authorized people.
I don't understand why it isn't possible to just add a similar note and let the user add the DCC in their wallet. There is literally no difference to the PDF which can be created, the user could set it as their wallpaper on the Lock Screen and the app can't do anything against it. Still this feature was implemented while the wallet integration was declined...
Here is probably the wrong place, I know, but I just had to comment this somewhere.

Good News everyone!
iOS 15.4 Beta 1 added support for EU digital Covid Certificates in the wallet app. See iOS & iPadOS 15.4 Beta Release Notes:

Verifiable health records now support adding vaccination records in the EU Digital COVID Certificate (EU DCC) format to the Wallet and Health apps. (79917344)


Rider IDE support

Can we wait for support this IDE?

Is there any way to get this into rider?

I would literally pay someone to do this. Anyone keen?

I would literally pay someone to do this. Anyone keen?

I did it a while ago, will post it later.

This package can be installed with Rider by using the "install from disk option"
ExceptionalRider-1.0.0.zip

Legend thank you!

This is gold.

@ldy985 Thank you so much!


[iot] Update identity-enabled hub tests to fix endpoint RBAC issues

Description
Updates IoT Hub tests for identity-enabled hubs to fix RBAC endpoint connection issues.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

iot

@c-ryan-k Thank you so much! I'll try it.

I tested it. No problem.

@digimaun Can you review this PR? Thanks


ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client

Hello,
I'm trying to get this running by following your examples, but am running into some issues.  I'm brand new to Docker/Docker-compose, but I've been trying to google/look through the issues list, but don't see this one.
Here is my config.json:
{   "database": {     "engine": "mysql",     "host": "db",     "name": "nginxproxymanager",     "user": "nginxproxymanager",     "password": "password",     "port": 3306   } }
(I had <IP_ADDRESS> in the Host value, but it gave me a connection refused error)
and here is my docker-compose.yaml file:
version: "3" services:   app:     image: jc21/nginx-proxy-manager:2     restart: always     ports:       - 80:80       - 81:81       - 443:443     volumes:       - ./config.json:/app/config/production.json       - ./data:/data       - ./letsencrypt:/etc/letsencrypt     depends_on:       - db     environment:     # if you want pretty colors in your docker logs:     - FORCE_COLOR=1   db:     image: mysql     restart: always     environment:       MYSQL_ROOT_PASSWORD: "password"       MYSQL_DATABASE: "nginxproxymanager"       MYSQL_USER: "nginxproxymanager"       MYSQL_PASSWORD: "password"     volumes:       - ./data/mysql:/var/lib/mysql
After running the "docker-compose up -d" command, I get the following error over and over (as seen in the Portainer UI):
 ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client,
I'm sure I'm missing some noob step, so if so I apologize.  Any ideas on what this could be?

Yeah that is a new one. I suspect that the latest mysql docker image has some changes that haven't been tested with this project yet.
I probably should update the docs with this tip:
You can use a docker image I've forked from Maria that has baked in configuration to use their Aria database engine, which will provide more stability in unexpected docker-type situations. It has been tested with this project. So, your docker-compose.yml should look like:
version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:2
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - ./config.json:/app/config/production.json
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
      # if you want pretty colors in your docker logs:
      - FORCE_COLOR=1
  db:
    image: jc21/mariadb-aria
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "password"
      MYSQL_DATABASE: "nginxproxymanager"
      MYSQL_USER: "nginxproxymanager"
      MYSQL_PASSWORD: "password"
    volumes:
      - ./data/mysql:/var/lib/mysql

However before using this, you'll want to delete your ./data/mysql directory as it will contain files from the previous mysql image that won't be compatible with this one.

Awesome, thank you, I will give this a try.

Hmm, now I'm getting:
[11/30/2018] [9:16:37 PM] [Global  ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
I also tried with "db" in my json.config file.  Should I be using a different IP address in the json.config?

Argh! I feel like it's so close, but I keep getting ECONNREFUSED.  On suggestion from a reddit user, I added a line to the docker-compose file for "hostname: db", so now my two files look like this:
docker-compose.yaml:
version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:2
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - ./config.json:/app/config/production.json
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
      # if you want pretty colors in your docker logs:
      - FORCE_COLOR=1
  db:
    image: jc21/mariadb-aria
    hostname: db
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "mypwd"
      MYSQL_DATABASE: "nginxproxymanager"
      MYSQL_USER: "nginxproxymanager"
      MYSQL_PASSWORD: "mypwd"
    volumes:
      - ./data/mysql:/var/lib/mysql

config.json:
{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "nginxproxymanager",
    "user": "nginxproxymanager",
    "password": "mypwd",
    "port": 3306
  }
}

Any advice on getting this running/what I can check?

Last comment - OK, the issue was that I thought that I was deleting the hidden ./data/mysql folder when I told Portainer to remove the volumes.  I'm not totally sure what that actually does, but I remembered your comment to delete the folder, so I thought I'd just try and remove it with:
sudo rm -rf ./data/mysql
Then
docker-compose up -d
And voila! It works now!

Lol yep that's the solution :)
I meant to get back to your earlier but work got in the way.. Glad it's fixed!


Type of components becomes any in vue2 template

I'm using volar with vuetify2. I manually defined types of all components in a d.ts file like following (ComponentName :DefineComponent<{...props}>), it works perfectly in previous volar.

volar of previous version:

But in the latest version, all the components become any. How can I solve this issue? Is the way that I define the components not correct any more? As Vue 2 UI frameworks don't provide support for volar, a guide of manually defining component types is very helpful. Then we can generate d.ts from vetur component data provided by those frameworks with a simple script.

Ah I fixed by replacing import type { DefineComponent } from 'vue' with import type { DefineComponent } from '@vue/runtime-dom'. Though I don't why it works in the past...


Dependency conflict (numpy version)

Hello,
First of all, thanks a lot for creating mcdm!
I'm now using mcdm in one of my projects but I'm facing some conflicting versions.
I could see that the numpy requirement must be 1.21.3
Is it possible to give more "flexibility" by using numpy>=1.19 in requirements.txt?
I'm pretty sure that older minor versions are working with mcdm.

Hello!
The requirements.txt file is provided for users that are interested in installing the version of NumPy that was used during the latest testing of the mcdm package. The range of supported NumPy versions is defined in the mcdm/_metadata.py file, which is currently defined as numpy>=1.21.3, <2.
If you have an older version of NumPy already installed on your system and you cannot or do not want to upgrade it, then you can avoid the dependency conflict by installing the mcdm package in a Python 3 virtual environment as follows:
$ python3 -m venv venv/
$ source venv/bin/activate
(venv) $ pip install --upgrade pip
(venv) $ pip install mcdm

Hello, thank you for taking the time to guide me through the installation!
This was indeed my problem (numpy version) since another dependency in my project requires numpy <= 1.2
I forced the installation of numpy 1.19 and didn't face any issue with mcdm.
I didn't read all the code but I'm pretty sure that mcdm might support older versions of numpy (Numpy 1.19.0 has been released Jun 20, 2020).
Isn't it better to set a requirement range for the version in requirements.txt instead of exact match?
For example: numpy = ">=1.20.0,<2"
Out of context: thanks for providing the links to the articles explaining the developed methods, the usage is clear!

No problem!
The range of NumPy versions in the mcdm/_metadata.py file is defined to accept (a) the NumPy version that was last used to test the mcdm package and (b) future minor or patch NumPy versions since they should be backwards compatible. Older NumPy versions are not included in that range because they were not used during the latest testing of the mcdm package (even though some of them would most likely work as well). If, for some reason, a future minor or patch NumPy version contains breaking changes, users can use the requirements.txt file to install the NumPy version that was used during the latest testing of the mcdm package as follows:
$ git clone https://github.com/akestoridis/mcdm.git
$ cd mcdm/
$ python3 -m venv venv/
$ source venv/bin/activate
(venv) $ pip install --upgrade pip
(venv) $ pip install -r requirements.txt
(venv) $ pip install .

I added additional installation instructions in the README file in case anyone else faces a similar issue (commit 2511f42767638c466183351fdc8ffd9290d3b391).
Of course, if you are forced to use an older version of NumPy, you could also install an older version of the mcdm package that supports that older version of NumPy.


A little questions about the training.

I used mtcnn to get the aligned face of WebFace. And I used the data to train center loss using the program in "https://github.com/ydwen/caffe-face". The  problem is that it seems the network can't converge without overfitting. My training data consist of 368775 imgs and my testing data consist of 122767 imgs. Is it because of less of data? Or I just didn't train my network well. Please help me!

Can you help me out? It seems that the data of WebFace is not enough if doing rectify.

With less data you would probably have to use a little bit more weight decay. But I haven't looked into caffe-face that much.


Add reusable css for styling an element as visually hidden while keeping it available to the accessibility tree

Pull Request
🤨 Rationale
We have the same style copy/pasted in a few different places to make text visually hidden while still available in the accessibility tree. Therefore, it would be good to have that style single-sourced.
👩💻 Implementation
Create shared cssPartial style that can be used in other css files for components.
Replace existing duplicated code with new style.
🧪 Testing
Manually verified there aren't accessibility violations with the modified components.
Verified no changes in chromatic.
✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@m-akinc, can you buddy these changes?


Added completer for directories

Hello, and congrats for the nice work. Lately, I have been using argcomplete more and more for my administrative Python scripts.
I sometimes came across the situation where i needed directory-only completion (e.g. like complete -d). I have created a completer class to address this, and i thought that it could be usefull to someone.
I did'nt use the subprocess approch that you have followed in FilesCompleter, because the task is quite simple and can be easily performed with plain os.path tools.

Looks good overall, please remove trailing semicolons from your lines.

Also, please add a test for your completer. You should be able to just copy/paste one of the existing tests and build a custom parser that uses this completer. To make it real, you might want to use https://docs.python.org/3.4/library/tempfile.html functions.

Hello @kislyuk. I 've removed the unneeded semicolons.
Regarding to the tests, i suppose we need a test similar to the one at
https://github.com/kislyuk/argcomplete/blob/master/test/test.py#L174 ??

Correct. Thanks.

Hello @kislyuk. I've added a relevant test. Please, check if this is adequate.
And one small question: Before adding this test, Travis failed at the phase of PyPy3 (while checking coverage). Has this failure anything to do with this, i mean are these tests strictly required for the coverage checks to pass ?

Thanks. I'll check this later today. Don't worry about the failure during
coverage checking - that is a bug in the test suite that got recently
introduced, and is not your fault. Sorry about that.
-ak
On Mon, Mar 2, 2015 at 5:50 AM, MichailAlexakis<EMAIL_ADDRESS>wrote:

Hello @kislyuk https://github.com/kislyuk. I've added a relevant test.
Please, check if this is adequate.
And one small question: Before adding this test, Travis failed at the
phase of PyPy3 (while checking coverage). Has this failure anything to do
with this, i mean are these tests strictly required for the coverage checks
to pass ?
—
Reply to this email directly or view it on GitHub
https://github.com/kislyuk/argcomplete/pull/98#issuecomment-76714187.

Hello @kislyuk , is there anything (from my side) pending on this issue ?

Sorry about the delay, thanks for your patience @drmalex07. I went ahead and merged this. I'll try to roll a release soon.

No problem at all, i only asked if anything was missing.
I am pretty sure we all have pressing deadlines on our heads!


Rework Tie Implementation

Create NoteCollection.note(at:) so that the user of it doesn't need to differentiate between a Note and a Tuplet. Then, in Measure, use this to simplify logic for modifying ties. Extend this to Staff as well if possible.

Fixed by pull request #65


distutils setup fails immediately

Prerequisites
The issue tracker is used to report bugs and request new features, NOT to ask questions.
Questions should be posted to the users mailing list which can be accessed at
https://ironpython.groups.io/g/users.

[ yes] Are you running the latest version?
[ yes] Are you reporting to the correct repository?
[ yes] Did you perform a cursory search?

Description
'ipy setup install' does not work, gets an exception.
Steps to Reproduce
ipy

from setuptools import setup

Note, no external files invoked, simply importing setuptools triggers the error (see below)
Expected behavior: [What you expected to happen]
Expected to import the setup function from distutils, not raise an exception
Actual behavior: [What actually happened]
/cygdrive/c/don/work/oom/code/gitstuff/ipy/oom:ipy
IronPython 2.7.10 (<IP_ADDRESS>0)
[.NETFramework,Version=v4.5 on .NET Framework 4.8.4220.0 (64-bit)]
Type "help", "copyright", "credits" or "license" for more information.

from setuptools import setup
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\IronPython 2.7\Lib\site-packages\setuptools_init_.py
", line 151, in
TypeError: a new-style class can't have only classic bases

Versions
See above, IronPython 2.7.10 (<IP_ADDRESS>0).  Note, just installed the latest version, using .msi.  No tweaking, no other packages installed.  'ipy setup.py install' fails out of the box.

Duplicate of https://github.com/IronLanguages/ironpython2/issues/624. Try using 2.7.11-rc1 instead https://github.com/IronLanguages/ironpython2/releases/tag/ipy-2.7.11-candidate1

Thanks, ipy-2.7.11-candidate1 took care of the issue.
From: slozier<EMAIL_ADDRESS>Sent: Monday, September 21, 2020 12:59 PM
To: IronLanguages/ironpython2<EMAIL_ADDRESS>Cc: donboll<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [IronLanguages/ironpython2] distutils setup fails immediately (#744)
Duplicate of #624 https://github.com/IronLanguages/ironpython2/issues/624 . Try using 2.7.11-rc1 instead https://github.com/IronLanguages/ironpython2/releases/tag/ipy-2.7.11-candidate1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/IronLanguages/ironpython2/issues/744#issuecomment-696339544 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6VCJ4BJMJZCMVQORAQHMTSG6WAZANCNFSM4RU5ANNQ .


Missing proj-datumgrid

Hi,
It's missing the vanilla proj-datumgrid : http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
It contains files for the whole world which are not included in datumgrid-world, like egm69_15.gtx.

@Nodd, are you sure you are using a version of proj that is old enough to need these packages?  The current version or proj is 8.2.1 and these packages have not been needed since proj 7.0.0.  I believe you may want to use proj-data instead: https://github.com/conda-forge/proj-data-feedstock
I started working on a PR to add the missing data but I don't think we actually want to maintain this outdated approach.

@xylar You're right, I was lost between all the versions on an old installation, until I found this page : https://pyproj4.github.io/pyproj/stable/transformation_grids.html
Sorry for the noise !


Add regression test for rdar://problem/115515583

@swift-ci Please smoke test and merge

Almost the same test case was added in fa28d145188ad994c3a94a149982d13fe3810613 so I'm going to close this


Enhance dg

Codecov Report

Merging #286 into master will decrease coverage by 0.19%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #286      +/-   ##
============================================
- Coverage     52.47%   52.27%   -0.20%
+ Complexity      619      615       -4
============================================
  Files           132      132
  Lines          2813     2818       +5
  Branches        347      347
============================================
- Hits           1476     1473       -3
- Misses         1190     1197       +7
- Partials        147      148       +1

Impacted Files
Coverage Δ
Complexity Δ

...java/trackitnus/model/lesson/LessonComparator.java
60.00% <0.00%> (-40.00%)
2.00% <0.00%> (-1.00%)

...kitnus/logic/commands/module/AddModuleCommand.java
71.42% <0.00%> (-11.91%)
5.00% <0.00%> (ø%)

src/main/java/trackitnus/model/commons/Code.java
80.00% <0.00%> (-10.00%)
6.00% <0.00%> (-1.00%)

src/main/java/trackitnus/model/commons/Name.java
80.00% <0.00%> (-10.00%)
6.00% <0.00%> (-1.00%)

src/main/java/trackitnus/model/contact/Email.java
80.00% <0.00%> (-10.00%)
5.00% <0.00%> (-1.00%)

src/main/java/trackitnus/model/contact/Phone.java
80.00% <0.00%> (-10.00%)
5.00% <0.00%> (-1.00%)

...n/java/trackitnus/model/lesson/LessonDateTime.java
72.72% <0.00%> (-7.92%)
11.00% <0.00%> (ø%)

...rc/main/java/trackitnus/model/commons/Address.java
75.00% <0.00%> (-5.00%)
5.00% <0.00%> (ø%)

src/main/java/trackitnus/model/module/Module.java
77.27% <0.00%> (-4.55%)
8.00% <0.00%> (-1.00%)

src/main/java/trackitnus/model/lesson/Lesson.java
74.19% <0.00%> (-3.23%)
13.00% <0.00%> (-1.00%)

... and 17 more

Continue to review full report at Codecov.

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


Load fake players in the server main thread, fix incompatibility with c2me (#50)

Tested on servers and clients with c2me, works fine.

Please change the version number in gradle.properties


Should support passing options to encode

ex: Yajl::Encoder.encode(body, :pretty => true, :indent => "\t")
At the moment MultiJson.encode only accepts an object.. simple fix, just add the options hash.

Closed by #28


Tags not displayed on compendium monsters

In GitLab by @Asacolips on Apr 13, 2021, 11:44
Summary
Changes to the sheet listeners have prevented the tagging widget from being applied to compendium actors.
Acceptance Criteria

[x] Tagging widget is displayed even if the actor isn't editable
[x] If the actor isn't editable, make the tagging widget read only.

In GitLab by @Asacolips on Apr 13, 2021, 11:58
marked the checklist item Tagging widget is displayed even if the actor isn't editable as completed

In GitLab by @Asacolips on Apr 13, 2021, 11:58
Resolved in 0.7.3

In GitLab by @Asacolips on Apr 13, 2021, 11:58
marked the checklist item If the actor isn't editable, make the tagging widget read only. as completed


quarantine/disable testing of pdf2parquet per issue #552

Why are these changes needed?
Because this failure is disabling all other PRs.
Related issue number (if any).
#552

This should not be needed. Please review https://github.com/IBM/data-prep-kit/pull/528

This does not seem needed now that we have PR #528 merged which fixes the tests.


[SOP Document] Privacy

Items to consider to be included:

Privacy Check (structured data)
Privacy de-identification
Tool and how to use


Add CLU example to assign deployment resources

See here: https://github.com/Azure/azure-sdk-for-python/pull/27237
This might be a good time to start dynamic test resources. We can create a test-resources.bicep (I recommend over ARM JSON) and eventually use this for more tests. For now, we just need to create an account and maybe a project in which we deploy?
/cc @kristapratico

@heaths I noticed that documentation related to assigning deployment resources seems to have been dropped between 2022-10-01-preview and 2023-04-01 ?  Can you add any clarity on what is going on here?

@TeddMcAdams please open a separate issue so we can triage it to the service team.


crash report

report attached.
coda_crash_report_2021-03-06_08-50-00.444248.tar.gz
Generating crash report
exn: {
"commit_id": "fd3980820fb82c7355af49462ffefe6718800b77",
"sexp": [
"monitor.ml.Error",
[
"Merkle_mask.Masking_merkle_tree.Make(Inputs).Attached.Dangling_parent_reference("dfd937db-6e59-3f36-e37c-baf8184a762a", "File \"src/lib/merkle_mask/maskable_merkle_tree.ml\", line 239, characters 37-44")"
],
[
"Raised at file "src/lib/merkle_mask/masking_merkle_tree.ml", line 116, characters 10-57",
"Called from file "src/lib/merkle_mask/masking_merkle_tree.ml" (inlined), line 131, characters 18-38",
"Called from file "src/lib/staged_ledger/staged_ledger.ml", line 846, characters 45-68",
"Called from file "src/lib/staged_ledger/staged_ledger.ml", line 1063, characters 6-235",
"Called from file "src/deferred0.ml", line 56, characters 64-69",
"Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5",
"Called from file "src/job_queue.ml", line 171, characters 6-47",
"Caught by monitor coda"
]
],
"backtrace": [
"Raised at file "src/lib/merkle_mask/masking_merkle_tree.ml", line 116, characters 10-57",
"Called from file "src/lib/merkle_mask/masking_merkle_tree.ml" (inlined), line 131, characters 18-38",
"Called from file "src/lib/staged_ledger/staged_ledger.ml", line 846, characters 45-68",
"Called from file "src/lib/staged_ledger/staged_ledger.ml", line 1063, characters 6-235",
"Called from file "src/deferred0.ml", line 56, characters 64-69",
"Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5",
"Called from file "src/job_queue.ml", line 171, characters 6-47"
]
}
Mina process exited with status code 1

Closing this issue as it is stale for a long time.


Add logic about running tasks

What is the purpose of the change
Add logic about running tasks.
Brief change log
(for example:)

Add logic about running tasks.

Verifying this change
This change added tests.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@45faf27). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 11161fd differs from pull request most recent head cf79d63. Consider uploading reports for the commit cf79d63 to get more accurate results

@@          Coverage Diff           @@
##             dev     #323   +/-   ##
======================================
  Coverage       ?   18.12%
======================================
  Files          ?      143
  Lines          ?    13173
  Branches       ?     1753
======================================
  Hits           ?     2387
  Misses         ?    10644
  Partials       ?      142

Continue to review full report at Codecov.

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


Build tools against real PAL

Otherwise mock RNG is used and the salt generated by AccessorySetupGenerator is always the same

We have it that way so that it's easier for testing/bringup. Vendors are expected to change it .

@rojer we will take a look at it and get back to you.

We have it that way so that it's easier for testing/bringup. Vendors are expected to change it .

oh, i see. however, it's a rather subtle change to be expected to make.
unlike everything else, which is very clear and well specified.
AccessorySetupGenerator as a tool that can be used pretty much as is, perhpas with some scripting around it so if it is left like this, i predict we'll be seeing a lot of devices in the field with salt<PHONE_NUMBER>4A144E4C1CEE7459C10AD4 :)

Closing this PR, fixing in https://github.com/apple/HomeKitADK/pull/25
The difference is building vs host PAL vs target PAL. Since the tools runs on the host, we need a host-compatible PAL.


Error with KiCad 8

Errore KiCad

[Content]
Traceback (most recent call last):
  File "D:\Users/PC/Documents/KiCad/8.0/scripting\plugins\com_github_gregdavill_KiBuzzard\plugin.py",
	line 93, in run_buzzard
    io = pcbnew.PCB_PLUGIN()
         ^^^^^^^^^^^^^^^^^
AttributeError: module 'pcbnew' has no attribute 'PCB_PLUGIN'

When I try to modify an existing label, I get this error. I tried to search for PCB_PLUGIN in pcbnew.py of version 8 of KiCad and I believe it has been replaced with PCB_IO.
Windows 11
KiCad 8 RC2
KiBuzzard https://github.com/gregdavill/KiBuzzard/commit/207b9701f8974d12ba3a5e0ece8fa42601168edd

Can confirm in 8.0.0-rc2-253-g7e194d5f69 on Windows 11

Only affects editing, can still add new labels.

Solved, just replace io = pcbnew.PCB_PLUGIN() with io = pcbnew.PCB_IO_KICAD_SEXPR()


KCP outside of Unity gives a windows exception about closed sockets

we may or may not want to add this to the unity kcp version:
https://stackoverflow.com/questions/74327225/why-does-sending-via-a-udpclient-cause-subsequent-receiving-to-fail

from stackoverflow:

Maybe have it as a toggle for best of both worlds?

fixed in next kcp release


Add [personal] #issuer #malicious GBE342…6YUHKL

Address: GBE342P5UEALLGT4DOO3IRZGVPSNGWMQ4ELNYU77CUXXEXJZUS6YUHKL
Tags: issuer malicious
Title: personal
Requested by @xdcflyboy

used viewing account to scam. i dont know how we are going adaptation when things like this happen

@Xdcflyboy
Use your first report to give new information.
https://github.com/stellar-expert/public-directory/issues/461


Fix error when reading GDAS data after 2019Jun12

This fix will allow the reader to read in f00 GDAS data files
after the 2019 June 12 12Z upgrade by NCEP. The reader expected
precipitation fields and averaged radiation fields in the f00
GDAS data files. After the upgrade, these fields were removed or
were changed to report instantaneous values, respectively.
This fix adds a new subroutine in read_gdas.F90 that conforms to
the new data file structure. In addition, a check was added so
the new subroutine is only called when the reader is accessing
files after 2019 Jun 12 12Z.
Resolves: #159

Do you have GDAS data we can test with this?  Not necessarily a formal test case, just something we can confirm the code changes with.

Maybe a better question:  Is the bug triggered by the most recent data in /discover/nobackup/projects/lis/MET_FORCING/GDAS?

Yes, the bug is triggered by the data on Discover. It doesn't call an abort or fatal error but it shows up in the logs:
[INFO] LIS cycle time: 06/12/2019 09:00:00
[INFO] LIS cycle time: 06/12/2019 09:30:00
[INFO] Getting new time2 data
[INFO] Reading GDAS file2 (I)
./input/MET_FORCING/GDAS//201906/2019061212.gdas1.sfluxgrbf00.sg
[INFO] Reading GDAS file2 (A)
./input/MET_FORCING/GDAS//201906/2019061206.gdas1.sfluxgrbf03.sg
[INFO] Reading GDAS file2 (A)
./input/MET_FORCING/GDAS//201906/2019061206.gdas1.sfluxgrbf06.sg
[ERR] Could not retrieve entries in file:
./input/MET_FORCING/GDAS//201906/2019061212.gdas1.sfluxgrbf00.sg
[ERR] Error reading files.  Rolling back one day. (try =            1 )

Okay, thanks.  I'll tackle this now.

Hi Daniel:
After looking at this with Jim, we recommend two major changes:
(1) In read_gdas, make sure glbdata_i is initialized to LIS_rc%udef, before calling the "retrieve" subroutine.  This will ensure that "missing" values are set for the two variables dropped in the recent GDAS files.
(2) We suggest staying with a single "retrieve" subroutine (retrieve_gdas_variables), and add a new logical argument to that routine that will dictate whether 7 or 9 variables are retrieved from the GDAS file.  The "retrieve" subroutine would be further modified by setting a new "ivmax" variable (either 7 or 9), and then changing this loop:
do iv=1,9  ! <-- replace 9 with ivmax
if((pds5_val.eq.pds5(iv)).and.&
(pds7_val.eq.pds7(iv)).and.&
(pds16_val.eq.pds16(iv))) then
var_found = .true.
var_index = iv
var_status(iv) = .true.
exit
endif
enddo
This will reduce the amount of code that would have to be maintained.  The current approach with the retrieve_gdas_noprecip) is mostly a cut-and-paste from retrieve_gdas_variables, and results in code bloat.
I'll add Jim to the assignee list in case he has further comments.

Code has been reworked to include the suggested changes. Let me know if you need anything else changed.

Thanks!  I'll look at this now.


Feature/new database

Checklist

[ ] I have performed a self-review of my code
[ ] I have reached out to another developer to review my code
[ ] New and existing unit tests pass locally with my changes
[ ] All Lint and CI checks are passing

There seems to be an issue with the sessions table. Investigating right now

There is an error that gets thrown in the browser console from a call to github/user. I don't think it originated from this PR, so it can be fixed in a future PR.


Exiting: error loading config file

Hello.
Most of all, thank you for your post https://www.elastic.co/kr/blog/getting-started-with-the-elastic-stack-and-docker-compose
It was very helpful.
However, I've got error as bellow.

filebeat
elastic-stack-docker-part-one-filebeat01-1    | Exiting: error loading config file: config file ("filebeat.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/filebeat/filebeat.yml') elastic-stack-docker-part-one-filebeat01-1 exited with code 1

metricbeat
2023-06-23 14:26:48 Exiting: error loading config file: config file ("metricbeat.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/metricbeat/metricbeat.yml')

It gave me suffer because i'm not pro user for docker.
Anyway, I figured out to solve it with giving command like bellow.

filebeat

filebeat01:
depends_on:
es01:
condition: service_healthy
image: docker.elastic.co/beats/filebeat:${STACK_VERSION}
user: root
volumes:
- certs:/usr/share/filebeat/certs
- filebeatdata01:/usr/share/filebeat/data
- "./filebeat_ingest_data/:/usr/share/filebeat/ingest_data/"
- "./filebeat.yml:/usr/share/filebeat/filebeat.yml:ro"
- "/var/lib/docker/containers:/var/lib/docker/containers:ro"
- "/var/run/docker.sock:/var/run/docker.sock:ro"
environment:
- ELASTIC_USER=elastic
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- ELASTIC_HOSTS=https://es01:9200
- KIBANA_HOSTS=http://kibana:5601
- LOGSTASH_HOSTS=http://logstash01:9600
command:
-strict.perms=false

metricbeat

metricbeat01:
depends_on:
es01:
condition: service_healthy
kibana:
condition: service_healthy
image: docker.elastic.co/beats/metricbeat:${STACK_VERSION}
user: root
volumes:
- certs:/usr/share/metricbeat/certs
- metricbeatdata01:/usr/share/metricbeat/data
- "./metricbeat.yml:/usr/share/metricbeat/metricbeat.yml:ro"
- "/var/run/docker.sock:/var/run/docker.sock:ro"
- "/sys/fs/cgroup:/hostfs/sys/fs/cgroup:ro"
- "/proc:/hostfs/proc:ro"
- "/:/hostfs:ro"
environment:
- ELASTIC_USER=elastic
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- ELASTIC_HOSTS=https://es01:9200
- KIBANA_HOSTS=http://kibana:5601
- LOGSTASH_HOSTS=http://logstash01:9600
command:
-strict.perms=false

I am issueing for anybody who suffers like me :)

Restart and Run everthing as the root user.

I cloned the repo and have tried both these commands with the same error:
docker compose up

gets the error, so I run docker compose down to clear everything

sudo docker compose up
Is this supposed to just work?

This should just work - however, the permissions can be a pain depending on the configuration.
I'll commit the changes based on the above command for strict-perms and see if that is helpful.

strict-perms appears to fix this.


Askhade/add quantized matmul

Adding 2 closely related operators

QLinearMatMul -> uint8 * uint8 = uint8
MatMulInteger -> uint8 * uint8 = int32
both use gemmlowp as the underlying low precision lib

Sorry for asking a question which is not directly related to this PR:
I've just realized you and nGraph are adding quantized ops, but I couldn't find anything about these ops in ONNX repository. I found https://github.com/NervanaSystems/ngraph/pull/2495 says "expected in the next ONNX revision". So, I'd assume you are planning to propose these ops to ONNX in near future?


Should not take 10 minutes to print error message when workspace build fails

See original issue on GitLab
In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 7, 2018, 17:45
Here's a typical experience with a build failure. Note FAILURE Running build-commands occurs at 08:10, but FAILURE Command 'cmake --build _builddir -- ${JOBS}' failed with exitcode 1 does not occur until 17:51. That's nearly 10 minutes between informing me that I have a build failure, and informing me what the failure was. This is really terrible for developer productivity. Let's say I have 10 build failures in a row to fix, what would take an hour or two to handle with JHBuild is going to take days with BuildStream.
[--:--:--][????????][build:core-deps/WebKitGTK+.bst      ] STATUS  Running build-commands

    cmake --build _builddir -- ${JOBS}

[00:08:10][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Running build-commands
[00:08:10][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Running build-commands
[00:17:51][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Command 'cmake --build _builddir -- ${JOBS}' failed with exitcode 1

    Sandbox directory: /home/mcatanzaro/.cache/buildstream/build/core-deps-WebKitGTK+-dup1vcv8

    Printing the last 20 lines from log file:
    /home/mcatanzaro/.cache/buildstream/logs/gnome/core-deps-WebKitGTK+/????????-build.4874.log
    ======================================================================
    DerivedSources/ForwardingHeaders/wtf/Variant.h:674:9:   required from ‘void WTF::__variant_data<_Head, _Rest ...>::__destroy(WTF::in_place_index_t<_Index>) [with long unsigned int _Index = 1; _Head = WTF::RefPtr<WebCore::MediaSource>; _Rest = {WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> >}; WTF::in_place_index_t<_Index> = WTF::in_place_tag (&)(WTF::__in_place_private::__value_holder<1>&)]’
    DerivedSources/ForwardingHeaders/wtf/Variant.h:825:13:   [ skipping 2 instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ]
    DerivedSources/ForwardingHeaders/wtf/Variant.h:1470:45:   required from ‘void WTF::Variant< <template-parameter-1-1> >::__destroy_self() [with _Types = {WTF::RefPtr<WebCore::MediaSource, WTF::DumbPtrTraits<WebCore::MediaSource> >, WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> >}]’
    DerivedSources/ForwardingHeaders/wtf/Variant.h:922:9:   required from ‘WTF::__variant_base<_Derived, __trivial_destructor>::~__variant_base() [with _Derived = WTF::Variant<WTF::RefPtr<WebCore::MediaSource, WTF::DumbPtrTraits<WebCore::MediaSource> >, WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> > >; bool __trivial_destructor = false]’
    DerivedSources/ForwardingHeaders/wtf/Variant.h:1439:7:   required from ‘struct std::is_trivially_copy_constructible<WTF::Variant<WTF::RefPtr<WebCore::MediaSource, WTF::DumbPtrTraits<WebCore::MediaSource> >, WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> > > >’
    /usr/include/c++/7.3.0/optional:105:8:   required from ‘class std::_Optional_base<WTF::Variant<WTF::RefPtr<WebCore::MediaSource, WTF::DumbPtrTraits<WebCore::MediaSource> >, WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> > > >’
    /usr/include/c++/7.3.0/optional:453:11:   required from ‘class std::optional<WTF::Variant<WTF::RefPtr<WebCore::MediaSource, WTF::DumbPtrTraits<WebCore::MediaSource> >, WTF::RefPtr<WebCore::Blob, WTF::DumbPtrTraits<WebCore::Blob> > > >’
    ../Source/WebCore/html/HTMLMediaElement.h:1126:19:   required from here
    DerivedSources/ForwardingHeaders/wtf/RefPtr.h:45:14: error: invalid use of incomplete type ‘class WebCore::Blob’
             ptr->deref();
             ~~~~~^~~~~
    In file included from ../Source/WebCore/page/DOMWindow.h:35:0,
                     from ../Source/WebCore/html/canvas/WebGLRenderingContextBase.cpp:33:
    ../Source/WebCore/html/ImageBitmap.h:36:7: note: forward declaration of ‘class WebCore::Blob’
     class Blob;
           ^~~~
    ninja: build stopped: subcommand failed.
    [00:08:10] FAILURE [core-deps/WebKitGTK+.bst]: Running build-commands
    [00:08:10] FAILURE [core-deps/WebKitGTK+.bst]: Running build-commands
    [00:17:51] FAILURE [core-deps/WebKitGTK+.bst]: Command 'cmake --build _builddir -- ${JOBS}' failed with exitcode 1

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 7, 2018, 18:05
It's entirely reproducible, this time it only took 7m30s to finish failing:
[00:01:52][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Running build-commands
[00:01:52][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Running build-commands
[00:09:28][????????][build:core-deps/WebKitGTK+.bst      ] FAILURE Command 'cmake --build _builddir -- ${JOBS}' failed with exitcode 1

In GitLab by [Gitlab user @tristanvb] on May 8, 2018, 13:39
mentioned in commit 9b846ad7728fe4e77e1cdd81bf3b0220c2b1da93

In GitLab by [Gitlab user @tristanvb] on May 8, 2018, 13:39
mentioned in merge request !455

In GitLab by [Gitlab user @tristanvb] on May 11, 2018, 09:46
mentioned in commit 01a02a9a01c31ece723f88327877781a7a0e24fa

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 16, 2018, 15:42
Note: this issue was unfortunately not fixed by !455. See my comment there.

In GitLab by [Gitlab user @danielsilverstone-ct] on Sep 18, 2019, 08:48
It is possible this may be affected by !1563


[BUG] directly referencing a .jsx from

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager yarn
[x] I run Snowpack on OS Mac
[x] I run Snowpack on Node.js v12+

Describe the bug
Just tried snowpack on my working parcel.js v1 app, snowpack serves the index.html but fails to resolve the jsx referenced from the html (404)
To Reproduce

basic config mount: { "src": "/" }
simple src folder containing index.html with <script async importance="high" src="./index.jsx"></script> (relative import) + index.jsx
snowpack dev

Get this error: [21:45:15] [snowpack] [404] Not Found (/index.jsx)
Looking at the demo project, I realize that the script should be modified to use . .js extension instead of .jsx
Expected behavior
Why forcing to change the extension in the script reference? Why not serving the .jsx as it's named?
Anything else?
I had a good look at snowpack's entire doc and couldn't find any hint. I had to inspect a demo react project to figure this out.

Hi @drwpow , thanks. However in this issue I'm questioning/challenging the need for renaming my .jsx to .js in the <script> reference.
What are the reasons for doing that?

Oh sorry; I misunderstood. Basically, it has to do with exposing ESM to the browser. Most servers won’t serve .jsx as application/javascript, so Snowpack must rename it to .js so the browser can handle it properly.
But as to your question of: “why don’t we just require you always use .jsx when developing,“ I guess the answer is it’s just a decision Snowpack made. In the case of .jsx it’s moot, but in something like Svelte, it makes a difference:
<link rel="stylesheet" href="./src/MyComponent.svelte" />
<script type="module" src="./src/MyComponent.svelte">

It’s basically a challenge to serve one .svelte file as 2 different content types (.css or .js), so we made the decision not to. So in Snowpack, you must always reference your final output files, which in Svelte’s case means requesting MyComponent.svelte.css or MyComponent.svelte.js. And in the case of .jsx, it means that .js must always be requested.
I definitely agree that maybe we could have a more helpful error or something, making this suggestion clearer.


disable sensor

Certain sensors consume significant power, for example various gas sensors. Should we add enabled register on case-by-case basis? Or should it maybe be an optional (default on) register on all sensors?
I'm also thinking about the color sensor - they sometimes have a backlight which consumes significant energy. An enabled bit may be useful as well.

sounds like a generic optional enable rw register is useful

Might be a bit of a confusing dev ex? Either the client library would write enable, or it would be on the user to write enable before using? Maybe it should be intrinsic to the server that a write/read sets enabled?
Whichever way you cut it someone’s job gets a bit harder, and the implementation gets a bit muddier and the experience inconsistent.
James

From: Peli de Halleux @.>
Sent: Friday, August 6, 2021 7:21:23 PM
To: microsoft/jacdac @.>
Cc: James Devine @.>; Assign @.>
Subject: Re: [microsoft/jacdac] disable sensor (#553)
sounds like a generic optional enable rw register is useful
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fjacdac%2Fissues%2F553%23issuecomment-894437743&data=04|01|t-jamdev%40microsoft.com|fd7fe795b31a4aa8afbc08d95906ff43|72f988bf86f141af91ab2d7cd011db47|1|0|637638709023058259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=z7BxCp3%2F6n92nCewGXM9JcPZdivl9B%2B5NXPnn%2F98Gv4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABEF4KIFNHKAQ5IRCTZ6VRTT3QR2HANCNFSM5BWLXT4Q&data=04|01|t-jamdev%40microsoft.com|fd7fe795b31a4aa8afbc08d95906ff43|72f988bf86f141af91ab2d7cd011db47|1|0|637638709023068251|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DscSr8JWEoRYlZfjK1yTa%2BVNURvfNzlLsPCAxxkuUn8%3D&reserved=0.

It also makes certain use cases possible - eg battery-powered button-operated color sensor (when you want to measure color of something and save it somewhere).
I think power consumption is one of the features that distinguishes a prototyping system from a toy.

I agree power consumption is important and I am in favour of an overall enable/disable model but I don't think it should be optional. We should also specify the behaviour and implementation of enable/disable so that it is a consistent experience across hardware.

Another way to do it would be to add an optional "sleep" command and have any reading re-enable the sensor. Many of our sensors right now only enable on first reading.
One concern could be that jacdac-ts always (?) enables streaming, so if I wanted to write a vm program that, upon button press, takes one reading and sleeps the sensor, then I think jacdac-ts would wake it immediately because of streaming?

If we set the streaming interval properly, jacdac-ts will wait until asking for another reading.

From: Michał Moskal @.>
Sent: Tuesday, August 10, 2021 5:24:09 PM
To: microsoft/jacdac @.>
Cc: Peli de Halleux @.>; Assign @.>
Subject: Re: [microsoft/jacdac] disable sensor (#553)
Another way to do it would be to add an optional "sleep" command and have any reading re-enable the sensor. Many of our sensors right now only enable on first reading.
One concern could be that jacdac-ts always (?) enables streaming, so if I wanted to write a vm program that, upon button press, takes one reading and sleeps the sensor, then I think jacdac-ts would wake it immediately because of streaming?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fjacdac%2Fissues%2F553%23issuecomment-896401132&data=04|01|jhalleux%40microsoft.com|2e96eb3c9b4744cf047908d95c5e5630|72f988bf86f141af91ab2d7cd011db47|1|0|637642382511031585|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=IUm5au%2BTFO0%2BVUoBYP3LKHGX4i7HxDPJEhjiuTmk7mw%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKLAJCWSWZEMV72H2NLT4G7KTANCNFSM5BWLXT4Q&data=04|01|jhalleux%40microsoft.com|2e96eb3c9b4744cf047908d95c5e5630|72f988bf86f141af91ab2d7cd011db47|1|0|637642382511041582|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=J%2FINxWopGqU%2FDH7U2mKC2HLcu6yhxggF6uR4dPG7V1o%3D&reserved=0.

Current plan of record:

add optional enabled register, to be used mostly as set enabled to false aka sleep
for devices that start disabled, they will (re-)enable themselves on first get reading of set streaming_samples (to non 0) - this is already current behavior for G0 potentiometer, rotary encoder, and env sensors
devices that do not bother with enable/disable (most Padauks) just ignore the enabled register and are always enabled
to deal with sensors that take time to initialize (my gas sensors has 15s startup, but they sometimes need half hour), we can use the status_code generic register (already specified, but never implemented)

This is consistent from the user perspective in the sense if they want to save power, they need to issue sleep command, which may be ignored. Otherwise they don't have to do anything special.
To better deal with with these optional registers (in general) we can consider #564

@mmoskal - can we close this?


tooltip shader is not applicable on MacOS

First of all, thank you for making a great shader.
Minecraft Java Edition supports crossplatform with macOS, but some users cannot connect to the server because macOS only supports OpenGL version 4.1.
I would appreciate it if you could migrate to 4.1 or lower versions.
Thank you.

Fixed.


Write-Verbose should be controllable

Hello
Usually, the -verbose switch is used if one would like to get more information about one module or script.
The reality is, however, that we're flooded with verbose messages.
Therefore it would be great if -verbose could be controlled. Just two ideas:

By specifying a nesting level, e.g. -Verbose <NestingLevel>
-Verbose 2 would activate verbose messages in the directly called script and in all commands which are called by the script itself.
By specifying a script / module filter, e.g. -Verbose @('Build.ps1', 'Invoke-Build')
This would activate verbose messages in the script Build.ps1 and in the command Invoke-Build itself.

Kind regards,
Thomas

-Verbose is not inherited.
Have you give an example of this flood?

@iSazonov:
-Verbose is inherited, but inconsistently: The inheritance via advanced functions relies on implicitly set local preference variables, $VerbosePreference in the case at hand:

binary cmdlets invoked from such an advanced function do honor this preference variable.
advanced functions implemented in a (different) module do not - this is actually what #3106 complains about, and as such it is the opposite of what @schittli is asking for.

This problematic inconsistency is the subject of #4568, but it is ultimately a separate issue.
@schittli:
I understand the desire to have this, but the proposed syntax can't work, because -Verbose is a switch parameter and can therefore not accept an argument other than $True or $False if directly appended with : (e.g., -Verbose:$False).
Something like -Verbose 2 would break backward compatibility; allowing something like-Verbose:2 may work, but it would be a first for the PowerShell language: a parameter with an optional argument (other than the implied Boolean for switches).
With an array argument it gets even trickier, because the value must be a single token: -Verbose:('build.ps1', 'Invoke-Build')

@iSazonov No, not a dup - this is related to #3106 but is it's own issue since it applies to scripts and functions as well.
@mklement0 as daunting as it sounds, a new ubiquitous parameter-VerboseLevel N would be fine.

This problematic inconsistency is the subject of #4568, but it is ultimately a separate issue.

The issue discussed in #4568 is actually an example of an "unfortunate" consistency :-) Local preference variables are still just local variables. Modules provide isolation and so, by design, local variables never cross the module barrier. This includes preference variables.
@schittli

By specifying a script / module filter, e.g. -Verbose @('Build.ps1', 'Invoke-Build')
This would activate verbose messages in the script Build.ps1 and in the command Invoke-Build itself.

You can do this (to some extent) today with $PSDefaultParameterValues . For example:
PS[1] (34) > $PSDefaultParameterValues = @{'Copy-Item:Verbose'=$true}
PS[1] (35) > copy xxx yyy
VERBOSE: Performing the operation "Copy File" on target "Item: C:\temp\xxx Destination: C:\temp\yyy".
PS[1] (36) >

Now the core issue,  the verbose (and debug, log, etc.)  message flood, is definitely a problem but I've always thought of the solution being something more like Just My Code in the VS debugger. (In fact it would nice to have it in the PowerShell debugger too.) @lzybkr and I have discussed this a few times.

@iSazonov:

From this point of view, the inheritance of preference-variable values (in other scopes) looks dangerous.

The behavior defaulting to inheritance is crucial, not just with respect to inheritance of common parameters, but also with respect to directly set preference variables, and that is currently broken, as discussed in #4568:

It is crucial for behavior-controlling parameters -ErrorAction, -Confirm, and -WhatIf.
(To recap the problem with the current behavor: -ErrorAction Stop / $ErrorActionPreference = 'Stop', -WhatIf / $WhatIfPreference = $True not taking effect just because a command such as Expand-Archive happens to be implemented as an advanced function is surprising and potentially destructive.)
Inheritance-by-default is perhaps debatable for diagnostic/supplemental-output parameters such as -Verbose, -Debug, -InformationAction, and -WarningAction, but:

Changing their default behavior would certainly be a breaking change (and note that with a value of Stop you can even make these parameters behavior-controlling).
Inheritance can be desirable, as #3106 shows.
Also note that the output-collecting common parameters (-OutVariable, -ErrorVariable, -InformationVariable, -WarningVariable) exhibit effective inheritance behavior too (by simply collecting stream output across all calls that happen in the advanced function's scope).

To complement the default behavior with opt-in mechanisms for limiting the scope of common-parameter inheritance such as -Verbose, -Debug, -InformationAction, -WarningAction and/or apply filtering makes sense.


Add API support to check if public access is allowed for a R2 bucket

Current cloudflare-go version
Latest
Description
I am trying to fetch my R2 bucket details using the API and following the docs below.
Configure aws-sdk-go for R2
S3 API compatibility
I am trying to get the bucket public access data but didn't find any API that gives any of this data. I have configured my bucket to allow public access. Is there any API using which we can say that the bucket allows public access or similar to that?
Use cases
I have configured my bucket to allow public access from the Cloudflare dashborad. There should be an API that will return if my bucket allows public access and the public bucket URL for that bucket.
Potential cloudflare-go usage
If you can add an API that returns some detail about public access and the public bucket URL of the bucket.

References
No response

there isn't a public API for this so it is not available to check at the moment.

Thanks, @jacobbednarz, for the update. Excited to see more API support in the upcoming releases 🙂.


fix: improve Azure DevOps PR URL parsing and add unit tests

PR Type
Bug fix, Enhancement, Tests

Description

Improved Azure DevOps PR URL parsing to support multiple URL formats:

Standard format: "https://dev.azure.com/organization/project/_git/repo/pullrequest/1"
VisualStudio format: "https://organization.visualstudio.com/project/_git/repo/pullrequest/1"

Enhanced error handling and messages for invalid PR URLs
Added unit tests to verify correct parsing of both URL formats
Simplified the parsing logic by using the presence of "pullrequest" in the URL path

Changes walkthrough 📝
Relevant filesEnhancement

azuredevops_provider.pyEnhance Azure DevOps PR URL parsing

pr_agent/git_providers/azuredevops_provider.py
Improved URL parsing logic to handle different Azure DevOps PR URL formats  Added support for 'visualstudio.com' domain in addition to 'dev.azure.com'  Simplified error handling and improved error messages

+10/-8

Tests

test_azure_devops_parsing.pyAdd unit tests for Azure DevOps PR URL parsing

tests/unittest/test_azure_devops_parsing.py
Added new unit test file for Azure DevOps PR URL parsing  Implemented tests for regular Azure DevOps address and VisualStudio address

+15/-0

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

/add_docs

/analyze


improve extension API documentation and resolve some open questions

renamed AnnotationInfo.MEMBER_VALUE to AnnotationInfo.VALUE_MEMBER
replaced the phrase "component type" with "element type" when speaking
about arrays, because JLS uses both and each has a different meaning
removed ContextConfig, custom context registration is now fully
handled in MetaAnnotations
removed unnecessarily concrete language from @SkipIfPortableExtensionPresent
methods in the Types class now have more specific return types
implementations of AnnotationInfo, AnnotationMember and AnnotationTarget
are now required to define equals and hashCode, and are explicitly
not required to use a single object to represent a single construct
the ClassInfo declaration is now required to return annotations
@Inherited from a superclass, per @Inherited spec and CDI spec
explicitly documented that ClassInfo doesn't provide access to nested
classes or an enclosing class, and PackageInfo doesn't provide access
to package members
corrected some language to distinguish between generic classes (before
type argument application) and parameterized types (after type argument
application)
specified meaning of MethodInfo.name and returnType for constructors,
mirroring what reflection does (returning the declaring class)
defined how implicit bounds are represented in TypeVariable
and WildcardType
removed ObserverInfo.id()
usage of Optional was eliminated everywhere
instead of "void type", we now always use "void pseudo-type"
added @since 4.0 tags everywhere
changed @link tags to @linkplain if the link text isn't an identifier

Hey @Ladicek currently on vacation until 30th of August. Will review when I get back!

Sure, no worries, and enjoy! :-)

Thanks!


Remove PointsTo Edge Class

This should fix the failing test, seems that this removal will complete PR https://github.com/ShiftLeftSecurity/codepropertygraph/pull/1716

@mpollmeier since you understand the domain classes now in the repo, could you say if this will fix the failing pipeline?

@mpollmeier is on vacation. Will merge this now and hope it goes green.


The port of the configuration file is not in effect，SERVICEWEAVER_CONFIG=weaver.toml go run . The command runs the configuration file to take effect

The [single] section of the TOML config file configures a Service Weaver application run with go run and weaver multi single. To configure an app run with weaver multi deploy, you'll have to add a [multi] section like this:
[multi]
listeners.hello = {address = "localhost:12345"}

We've also seen people forget to re-run weaver generate after adding a
listener to their component implementation struct, so please be on the
lookout for that if things still don't work after you add the config.
On Tue, Oct 10, 2023 at 9:07 AM Michael Whittaker @.***>
wrote:

The [single] section of the TOML config file configures a Service Weaver
application run with go run and weaver multi single. To configure an app
run with weaver multi deploy, you'll have to add a [multi] section like
this:
[multi]listeners.hello = {address = "localhost:12345"}
—
Reply to this email directly, view it on GitHub
https://github.com/ServiceWeaver/weaver/issues/654#issuecomment-1755762758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJSQ6UQYAURW6NBXBT4UM3X6VXDLAVCNFSM6AAAAAA5XQ2UPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJVG43DENZVHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Any else solutions? I met the same trouble. The port of the configuration file is not in effect.
But i used go run, after weaver generate ..
my config weaver.toml
[single]
listeners.hello = {address = "localhost:12345"}

listener
type app struct{
    weaver.Implements[weaver.Main]
    reverser weaver.Ref[Reverser]
    hello    weaver.Listener `weaver:"hello"`
}

weaver version
v0.22.0 darwin/amd64

Any else solutions? I met the same trouble. The port of the configuration file is not in effect. But i used go run, after weaver generate ..
my config weaver.toml
[single]
listeners.hello = {address = "localhost:12345"}

listener
type app struct{
    weaver.Implements[weaver.Main]
    reverser weaver.Ref[Reverser]
    hello    weaver.Listener `weaver:"hello"`
}

weaver version v0.22.0 darwin/amd64

Use below command is ok.
SERVICEWEAVER_CONFIG=weaver.toml go run .


Bug save Gun

All gun not save on bdd , i connect buy wearpond and i disconnect i have not wearpond .
Can you help me ?

Depends on your version, this bug has been fixed. If you are not waiting at least 30s after buying, then it's perfectly normal.


skip client-side nav for

closes #546, though there's still room for bikeshedding.
One issue here is that the sveltekit:reload attribute gets squigglied:

I actually have no idea where SvelteKitAnchorProps (which determines which attributes are valid) is defined?
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

in fact, the type error mentioned above is blocking CI. cc @dummdidumm, who likely knows where and how we'd fix this

That needs a change in language tools and new release of svelte-check - will do that tomorrow

reload sounds to me like we're staying on the same page similar to @Conduitry's objection to refresh in the issue https://github.com/sveltejs/kit/issues/546#issuecomment-799850700. I wonder if there's a name that better indicates it's a new page. Perhaps sveltekit:fullnav or sveltekit:servernav or something?

In the context of a link that points to a specific location, I think reload is clear enough. Better to use vernacular that's in widespread use than to come up with something that sounds clunky, I think

New version of svelte-check which supports the sveltekit:reload attribute released.

I just realized we could now ignore rel="external" links when prerendering since those will be dedicated for truly external links. sveltekit:reload links should still be crawled.


Subscription Notification from Sandbox Environment

Hi,
I am not receiving subscription notification from sandbox environment? Is there any upgrade going on ?

I confirm that it's not working at the moment.  Subscription notification from sandbox environment stops working from time to time.  You can send email to<EMAIL_ADDRESS>to report this issue.

thank you for the confirmation

Hi @azwaralam
The Subscription Events are now working fine for :

SMS
Voice Calls


Request cardgamedb images from http not https

Quick fix for https://github.com/Alsciende/netrunnerdb/issues/242
Small disclaimer: I am a fledgeling web-developer, so I might not have seen the bigger picture here.
The https was added to prevent mixed content warnings, but now image requests to cardgamedb fail somehow. Changing it back to http works, but yeah, merge at your own discretion regarding the warnings.

Ugh I now realise this does not work if the imageUrls in the cards are not empty.

Ugh I now realise this does not work if the imageUrls in the cards are not empty.

@Alsciende could you please run the image importer command on the live server to make this change effective? Plus, if you get around to do that, could you take a look at the two open PRs in the cards repo for the Errata and Magnum Opus cards? TIA!

Hmm but wouldn't running the importer command again do nothing now, because of line 42:
$cards = $this->entityManager->getRepository(Card::class)->findBy(['imageUrl' => null]);

Probably needs some
findBy(['imageUrl' => [ null, >>>code that finds strings that start with https://www.cardgamedb.com<<<< ] );
But again, I can't test currently, and I am not familiar with this Doctrine thing.

Thanks, @Alsciende ! Hi-rez scans for the Magnum Opus cards are here: https://drive.google.com/drive/folders/1HTIMOPQwjCRUVPTCiOr26vOys0SlVR-c


Update Docstrings api for documentation (issue #893)

This PR introduces a comprehensive update to our documentation with the addition of an OpenFL API section. This section provides detailed information about the various components of the OpenFL, enhancing the overall understanding and usability of the platform.
Key updates in this PR include:

OpenFL API Section Addition: A dedicated section for OpenFL API has been added to the documentation. This section provides a valuable resource for both new and existing users.
Updated Docstrings: We have revised and updated the docstrings throughout the documentation to ensure clarity and consistency. These docstrings now provide more accurate and detailed descriptions of the functions and methods, facilitating better understanding and usage.
The docstrings for the following modules have been updated:

Component
Cryptography
Databases (TensorDB)
Experimental
Federated
Interface
Native
Pipelines
Plugins
Protocols
Transport
Utilities

The updated docstrings provide a more detailed explanation of these components, enhancing the user's understanding of their functions and roles within the OpenFL.

Addition of Indexes and Tables: To improve the navigability and accessibility of the documentation, we have added indexes and tables where necessary. These additions will make it easier for users to find the information they need.

This PR is a significant step towards improving the quality and comprehensibility of our documentation. We believe that these updates will greatly enhance the user experience and make it easier for users to understand and utilize OpenFL.

Great start for the much needed improvement in docs @manuelhsantana :)
On fixing the lint issues: we have ./shell/{lint.sh}{format.sh} with correct configurations to check and apply fixes. But those files are currently limited to openfl/experimental namespace. You may have to edit those to point to openfl/ instead.
I can help you through any formatting-related test breaks if they happen (likely). We should start with getting the tests below to pass before formatting changes kick in, to reduce error surface.

@manuelhsantana We would need these tests to pass before we can merge it. Let me know if I can be of help here.


adding extra classes to make sidebar toggleable (task #1722)

Adding extra classes that will be used for collapsing the notes sidebar with current layout draft.
Collapsing elements are added to cakephp-qobo-admin-panel.

Current coverage is 61.37% (diff: 100%)

Merging #13 into master will not change coverage

@@             master        #13   diff @@
==========================================
  Files             3          3
  Lines           145        145
  Methods          14         14
  Messages          0          0
  Branches          0          0
==========================================
  Hits             89         89
  Misses           56         56
  Partials          0          0

Powered by Codecov. Last update 03171fc...c5d7873

Following changes are not required, for collapsing the sidebar, thus closing this pull request.


Fix wallet inscriptions so it can list multiple inscriptions on the…

…  #same sat
Fix #2367.

Good catch! Would be great to have a test for this edge case

Expanded this and added tests in #3101


treewide: rename name to pname&version

Motivation for this change
#103997
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

What’s the rationale for this kind of change? Cause unnecessary rebuilds? Create conflicts to annoy people?
Please revert.

my intention was to improve the codebase.

This issue https://github.com/NixOS/nixpkgs/issues/103997.
This causes 73 rebuilds per platform which is nothing to worry about and under normal circumstances this is cached in less than a day and if hydra is less busy in a few hours.
This is not done to create conflicts on purpose or annoy people and I don't like that contributors are accused of this.
There is no reason to revert anything here unless something regressed. Shouldn't that have been cached by an eval error? If so we should consider if it is easily fixable and add a test for it to prevent similar issues in the future.


Skip push cds for sidecar when virtualService updated

Please provide a description of this PR:
VirtualService and Gateway both donot influence sidecar cds.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
a1ae7dc33c24e8faeee6330c6235fa8203149610
link
/test unit-tests_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
a1ae7dc33c24e8faeee6330c6235fa8203149610
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
a1ae7dc33c24e8faeee6330c6235fa8203149610
link
/test integ-pilot-multicluster-tests_istio

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

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
a0faccf9f6f4559201275e857f9240feffc589fc
link
/test integ-pilot-multicluster-tests_istio

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

/test integ-pilot-multicluster-tests_istio

/test integ-pilot-multicluster-tests_istio

I recall we added this for a reason.. will try to see if I can find it and
if it still applies
On Thu, Aug 5, 2021, 5:11 AM Istio Automation @.***>
wrote:

Merged #34537 https://github.com/istio/istio/pull/34537 into master.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/34537#event-5117095536, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXODYLWUXAUAYURDPALT3J5YTANCNFSM5BTPQKHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@howardjohn How did you find the context? I will take a look. thanks

just vaguely remembered a PR about it and looked at git history
On Thu, Aug 5, 2021, 6:09 PM Zhonghu Xu @.***> wrote:

@howardjohn https://github.com/howardjohn How did you find the context?
I will take a look. thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/34537#issuecomment-893928276, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLXD5CH2JICZMPARJDT3MY4JANCNFSM5BTPQKHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Return 405 for Unsupported Methods on Endpoints, 204 for Cross-Origin OPTIONS

Resolves #5483
Previously curl -X POST http://localhost:11434/api/ps --> 404 (corrected to 405)
Resolves #5294
Previously, curl -X OPTIONS http://localhost:11434/api/chat --> 204
curl -X OPTIONS http://<IP_ADDRESS>:11434/api/chat --> 404 (corrected to 204)

you should rebase


Make the send button work on the training page

On the branch "feature-endless-gamemode", the back-end of the send button is not implemented yet.
We need to know if the song sent is correct or not, based on the song the user is listening to.

See commit 0adea42


Authorizing Azure Static Web Apps in GitHub for organizations

The note about authorizing Azure Static Web Apps in GitHub does not mention the necessary steps for authorizing Azure Static Web Apps if the repository is behind an organization. In this case you must request access for the organization. You can do this by going via your own profile settings or e.g.

**Organization Settings -> Third-party application access policy -> your own authorized applications -> Azure Static Web Apps

and request Access from there.
Here is the note I'm referring to:
If you don't see any repositories, you may need to authorize Azure Static Web Apps in GitHub. Browse to your GitHub repository and go to Settings > Applications > Authorized OAuth Apps, select Azure Static Web Apps, and then select Grant. For organization repositories, you must be an owner of the organization to grant the permissions.

Perhaps you also want to look at the instructions for personal repositories?  Repository Settings > Applications does not seem to be a valid path anymore.
// Alexander

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

ID: 63230b97-2269-3fed-7fca-882bb380c5f6
Version Independent ID: feb2708e-5cea-4ad8-eaaa-f3061e18c11a
Content: Quickstart: Building your first static web app with Azure Static Web Apps using the Azure portal
Content Source: articles/static-web-apps/get-started-portal.md
Service: static-web-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@Alexander-Hjelm Thanks for this.  The docs are still not updated at this point so this was super helpful!


Translation Error

https://forums.openmv.io/t/topic/10093/1

This issue has been mentioned on OpenMV Forums. There might be relevant details there:
https://forums.openmv.io/t/topic/10093/2

Fixed


Added control over BlendMode for layers.

Added documentation of struction in code and added option ot set
blendMode.  Also started on adding effect layers

Hi @flemingm thanks for contributing this! I know this is long, long overdue but your changes look good. I was planning to run the new code through it's paces because the changes to PSDWriter.m seemed significant, but it looks like a good chunk of it was whitespace and comments.  Going to go ahead and merge this!


Argument-less cd changes dir to $HOME

Resolves #109

Srange, is FreeBSD build vm missing HOME variable?

sr.ht is a relatively new service - I expect they are changing things and made a mistake.

@X4lldux
Awesome work - if freebsd doesn't have home, I guess you could just set it in the test case with os/setenv. A bit hacky, but probably ok for now.
A better solution may be a more reliable way to find a user home, perhaps something in shlib, but we don't need to worry about that for now.

@andrewchambers I guess I can add a nicer error when it croaks & add hardcode env in test.
Even bash's version of cd depends on $HOME so using a different way is just over complicating it to fix an obscure edge case.

That would be great. Thank you so much.


Error: the command proxy could not be found within PATH or Pipfile's [scripts].

This problem is just caused by force merging (it doesn't work, and it breaks the code instead), and it'll be fixed soon

Solved.


Content type sniffing very limited

When you upload a file, only a small amount of file types are recognized,
others are marked as application/octet-stream (default).
Use case: upload tif file; it will be marked as application/octet-stream.
Because http.DetectContentType only takes web viewable content types
into account?

Currently, the file type is only used to differentiate between PDF and other file formats in the front-office. The backoffice doesn't use the ContentType property. A concrete, future use case would be showing a thumbnail of the cover of the PDF.
As-accurate-as possible file characterization is an archival / pre-ingest concern. At that point, we would rely on PRONOM, a vetted authority offering file format signature lists, rather then a 3rd party tool which has its own signature list baked in. Siegfried is a Go application build by archivists and based on PRONOM.
Do we want as-accurate-as-possible file characterization when a file is first uploaded in Biblio Backoffice? Or are we happy with "good enough" just to satisfy the functional requirements of the backoffice / frontoffice? (e.g. show a cover, an indication of the file type)
File characterization may impact the upload process performance, so implementing as an async process would be the better option. Once the necessary infrastructure (job orchestration) has been made operational; we might consider how to implement this properly.  At that point, we can always apply a file characterization process retro-actively on all uploaded files.
I suggest postponing this.

Currently, the file type is only used to differentiate between PDF and other file formats in the front-office. The backoffice doesn't use the ContentType property. A concrete, future use case would be showing a thumbnail of the cover of the PDF.
As-accurate-as possible file characterization is an archival / pre-ingest concern. At that point, we would rely on PRONOM, a vetted authority offering file format signature lists, rather then a 3rd party tool which has its own signature list baked in. Siegfried is a Go application build by archivists and based on PRONOM.
Do we want as-accurate-as-possible file characterization when a file is first uploaded in Biblio Backoffice? Or are we happy with "good enough" just to satisfy the functional requirements of the backoffice / frontoffice? (e.g. show a cover, an indication of the file type)

I sort of agree, but I am just a bit considered, that if something trivial like well known image types are not recognized, we will see this more often.

File characterization may impact the upload process performance, so implementing as an async process would be the better option. Once the necessary infrastructure (job orchestration) has been made operational; we might consider how to implement this properly. At that point, we can always apply a file characterization process retro-actively on all uploaded files.

file detection is already done by reading part of the file

I suggest postponing this.


Plattform fixes

Some changes to support cross plattform (windows).

Thanks very much!

Thanks very much!

You're welcome.


Blazor client side configured for prerendering returns status 500 instead of 404 for missing resources

Describe the bug
Server should return status code 404 for missing resources. It returns 500 with the following stack trace:
System.InvalidOperationException: The SPA default page middleware could not return the default page '/index.html' because it was not found, and no other middleware handled the request.

   at Microsoft.AspNetCore.SpaServices.SpaDefaultPageMiddleware.<>c__DisplayClass0_0.<Attach>b__1(HttpContext context, Func`1 next)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

To Reproduce
Clone this repository: https://github.com/danroth27/ClientSideBlazorWithPrerendering
It contains Blazor client side application (ASP.NET Core hosted) with prerendering enabled. In index.razor file add something similar to this:
<img src="my-wrong-image-file-name.jpg"/>

and run application. In the browser open developer's tools and look at network tab. You will see status 500 as status code for image request.
Additional context
dotnet --version
3.0.100-preview5-011568

This will no longer be the same with preview 6, since we no longer use the "SPA default page middleware" that is referenced in the error message. It's possible there could still be issues with preview 6, but if there are, the underlying cause would be different.
I'll close this since it definitely doesn't apply as-is to preview 6, but please open a new issue if you can reproduce any similar problem with preview 6. Hope that's OK!

I have just checked in Preview6 - works correctly - status 404, no exception.