Latest HA requires ac-infinity-ble 0.4.2 but fails to install it

The problem is already well documented in https://github.com/hunterjm/ac-infinity-hacs so I'm just adding it here as a pointer.
The problem is that this version is missing and can't be installed manually if running HAoS (no access to the underlying os). There's no way to run pip or docker on HAOS (supervised).  SSH into it only grants access to a separate docker shell and not the underlying os. Then when pip is run, it spears to succeed. However, after rebooting HAOS the system log file shows that it isn't actually installed:
``2023-09-10 22:06:09.397 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration ac_infinity: Requirements for ac_infinity not found: ['ac-infinity-ble==0.4.2'].
homeassistant.requirements.RequirementsNotFound: Requirements for ac_infinity not found: ['ac-infinity-ble==0.4.2'].

I have the same issue

Here's a workaround until @hunterjm is available to create a new release.

The problem is that this version is missing and can't be installed manually

FWIW, Home Assistant provides a misleading error message in this scenario. It's not that ac-infinity-ble isn't found, it's that it couldn't be installed due to dependency requirement conflicts. To uncover the useful error message, you have to run pip install with the package_constraints.txt from Home Assistant.
ERROR: Cannot install ac-infinity-ble==0.4.2 because these package versions have conflicting dependencies.

The conflict is caused by:
    ac-infinity-ble 0.4.2 depends on bleak<0.21.0 and >=0.20.2
    The user requested (constraint) bleak==0.21.1

Resolved in ac-infinity-hacs 0.4.3

Resolved in ac-infinity-hacs 0.4.3


Baidu tts

Description:

Update the requirement version, from baidu-aip==1.6.6 to baidu-aip==2.2.8
the option range for speed&pitch, from[0..9] to [0..15]
use the options input in get_tts_audio, to support input options from service tts.baidu_say

Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[X] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

somebody has changed it:)


Android 13 Notification Icon invisible against the background

Device: Samsung Galaxy S22 Plus
OS: Android 13
My device updated to Android 13 and now the background color of the notification icon is same as the icon color itself. Which makes the icon almost invisible.
I guess the background color is configured somewhere and could be changed to a different color. BUT I think changing the notification icon to be fully white could be a better solution.

Related to the above:
Before upgrading to Android 13 (Samsung Galaxy S20+) the notification icon in the status bar was 'adaptable', white on dark background, black on light background.
At the moment the icon is green and stays green in both situations. I'm attaching screenshots.

I can confirm the "always green" icon as well.

I have not been able to reproduce either case in the emulator, but it occurs on my phone as well. Very odd.

I have not been able to reproduce either case in the emulator, but it occurs on my phone as well. Very odd.

I too have this issue on my S22. I think (from my limited android dev experience, so please dismiss me if you know better) that you can set various different icon types in some kind of manifest, and provide them as a bunch of resources, some of those resources intentionally being monochrome icons for situations such as these.

As you can see, FitnessSyncer also has this issue partially, but they don't appear to have a theme colour set. The other apps such as Automate have monochrome icons correctly configured so do not exhibit this issue.

Should be fixed in https://github.com/binwiederhier/ntfy-android/pull/46 - Please try out the .apk and let me know if it works for you, and maybe post a screenshot too.
@alexhorner @s-h-a-r-d @clmbmb
https://drive.google.com/file/d/12Q9mejiBP1EZ84OFjvHyyPPoAklkTBPd/view?usp=share_link

@binwiederhier All tested, looking snazzy!

May I also make the recommendation that you configure the subscription service notification category to be minimised by default? As you can see in my screenshot, I have manually configured it to be minimised.
Thanks for your awesome work!

May I also make the recommendation that you configure the subscription service notification category to be minimised by default?

I briefly checked and I don't think this can be toggled programatically.

EDIT: And maybe make that notification also undismissable?

You mean make it so that it can be swiped away? That's not possible for foreground service notifications. It's desired behavior in Android.

Done. Will be in the next release.

May I also make the recommendation that you configure the subscription service notification category to be minimised by default?

I briefly checked and I don't think this can be toggled programatically.

Quasseldroid, Conversations and Automate as you can see in my screenshots have it minimised by default. I believe Quasseldroid and Conversations are open source so maybe that could be of help?

EDIT: And maybe make that notification also undismissable?

You mean make it so that it can be swiped away? That's not possible for foreground service notifications. It's desired behavior in Android.

The opposite. Both Quasseldroid and Automate are undismissable (cannot be swiped away). Conversations and ntfy both are dismissable (can be swiped away) right now, and don't seem to reappear without killing them and starting them again.
I will open a separate issue for this.

Interesting. Yeah please feel free to create two new issues for this.


Enhancement: Make the "Select an artboard" resizable and/or add a title on hover

Hi there,
Most of the time the input "Select an artboard" isn't long enough for me to select the right artboard.
It would be great if I can resize the artboard or at least when I hover the options of the input having a title

Thanks

I think you posted an issue to the wrong repository. 😁

Oh yeah sorry 😁
Thanks


Transporter Path Finder Crash at World Loading

I got this crash in another version of Mekanism, but when I upgraded to 228 it fixed it. Now after a few weeks with 228 I get the same problem again.
http://pastebin.com/nxY1sHB3
I will need to downgrade to 216 again to play Minecraft.

I have confirmed that this issue was fixed in developmental, but now the problem is the energy network  intermittently crashes. I think 228 doesn't have the necessary changes to TransporterPathfinder merged yet.

Aidan said that he fixed it in developmental, that was before 228, which actually fixed the problem.

Why did you close this Aidan?

It's fixed on my end in development and we're nearing a release. Expect an update in the next 2 days


Update doc to remove usage of exporter component

Description
Replace usage of exporter components with corresponding changes in Dapr Configuration.
Issue reference
Please reference the issue this PR will close: https://github.com/dapr/docs/issues/967

@orizohar @msfussell can you please help review?  Thanks


Update Character “thaishin”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
c20b30ce757de26f0c09227f9b046a2e17891884

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/62ebfa8a24020000090d5d99


hedweb js directory should be in static

The js directory is temporarily under templates so that jinja2 and blueprints finds it.  Structurally it should be under static, but I was not able to get it to work on my first pass.  It probably requires a different app.register and possibly setting some URL_PREFIX.  I am putting it here to remember to go back and address.

Decided to live with the current structure.


SignerPayloadJSON type mismatch

The pub(extrinsic.sign) payloads sent by PAPI to the wallet don't match the expected shape
Wallets expect this shape (HexString for most fields) :
https://github.com/polkadot-js/api/blob/master/packages/types/src/types/extrinsic.ts#L32
Payload actually sent by PAPI :

As you can see nonce, specVersion and transactionVersion (maybe more) are numbers instead of HexString.
I suspect this is why Nova breaks (app just closes, can't get any log) each time the dapp sends a payload to the wallet for signature

Thanks a lot for reporting this @0xKheops !
I do remember that first we tried passing binary data as HexStrings and it didn't work. I'm super certain of that. However, it seems that the reason why it didn't work is because we were sending the binary data as SCALE encoded data (adhering to the on-chain definitions found in the metadata). Then, out of trial and error we noticed that sending the data like this did work with the PJS extension, with Talisman and with Subwallet, so we just left it like that. I wish there was a proper spec on this, TBH.
On that note, please know that we have been collaborating with Parity to define a better (and library agnostic) PolkadotSigner interface that shouldn't have any of these issues.
We will try changing all those fields to send HexString data, but it would be really, really helpful if you could explain to us what is the "canonical" way of encoding those values as binary given the fact that it's quite obvious that they are not being SCALE encoded.
Thanks a lot!

Hey @josepot
We actually had to make a fix to Talisman to support specVersion being sent as number in the payload, did that when i first tried PAPI.
https://github.com/TalismanSociety/talisman/pull/1399
It looks like numbers are meant to be encoded as base 16, so I assume 0x${value.toString(16)} should work


Create USCM API PR-FAQ

Few questions-
We already have the SCI Open Data project, where we have started looking at various sources, process to allow request of new sources and the ntention is to provide an API on top of it. It would be good to align both these projects and have a consolidated requirements. @srini1978 , pls share your inputs.
The FAQ that we created for data, methodology and overall claculation is now transfered to SCI Guidance project


specifying "false" for seconds doesn't work in some cases

is this expected?
> distance_of_time_in_words(Time.now, 1.5.seconds.ago, false)
=> "1 second"
> distance_of_time_in_words(Time.now, 1.5.seconds.ago, true)
=> "1 second"

Hi again @jjb! Yes, this is indeed expected behaviour, as documented in https://github.com/radar/dotiw#dotiw-

Gotcha, thanks.


feat: Prevent creating multiple fidelity bonds with same expiry date

This request stems from a user suggestions. Thank you, btw :pray:
As the title says, as Jam is tailored towards non-expert users, address reuse should be prevented (as much as possible) when creating fidelity bonds . Since the address of the bond is shown beforehand, if someone really wants to do this - for whatever reason - it can still be done manually or by using the CLI. However, the UI should try to stop this from happening if possible.
Out of scope:
Since Jam does not know any historical, expired (and subsequently moved) fidelity bonds, recreating FB with the same expiry date afterwards cannot be prevented. However, should it be prevented to create multiple FBs in the first place?

Since Jam does not know any historical, expired (and subsequently moved) fidelity bonds, recreating FB with the same expiry date afterwards cannot be prevented.

Actually it can. Jam could do request to Esplora (blockstream.info) and / or mempool.space APIs via Tor, then at least display warning to the user if address has been used before. But need to be sure to not reuse Tor circuits for multiple requests for privacy reasons and also handle situations when API service(s) are down.
https://github.com/Blockstream/esplora/blob/master/API.md#get-addressaddress
https://mempool.space/docs/api/rest#get-address

Hey @kristapsk. Appreciate any contribution and suggestion from you. I have a hard time wrapping my head around it, as Jam is still limited to the browser and would only be able to do this in special environments, e.g. if Tor browser is used. Otherwise we'd need a server component running alongside a Tor daemon (i.e. on the same machine as the backend). As you know, the possibility of a small server component comes up time and time again, but this adds yet another burdon on the user. I have always had hoped that any information Jam needs can come from JM itself (mempool info, transaction history, etc.). Let me know what you think.

that sounds promising for so many different problems and use cases. lets hope it can be done directly inside JM :) right @kristapsk right?! :D

hey @theborakompanioni , i am Bhavesh (SOB applicant). I have gone through the issue, and what i understand is that we need to prevent creating multiple fidelity bonds with same expiry date to avoid address reuse. I on my development setup and i think this is the issue..

I already created a bond which is to be expired in august. And when i create a new one. It suggests me that same month, whereas it should not.. right? please let me know if I am going in the right direction.
Also do we have to completely avoid the expiry date, or should we suggest user to avoid it?

I already created a bond which is to be expired in august. And when i create a new one. It suggests me that same month, whereas it should not.. right? please let me know if I am going in the right direction. Also do we have to completely avoid the expiry date, or should we suggest user to avoid it?

Hey @barrytra! Yes, you are completely right, you are going into the right direction.
I think - so this is a personal opinion - that we should not prevent the user from creating a Fidelity Bond with the same expiry date if that is what he wants to do - instead I think a big warning message with a button that say "I understand what I am doing - I really want to create another Fidelity Bond with the same expiry date" is okay.
However, there are some things to consider, e.g. in most cases, it does not make sense to create multiple FBs in the first place.
Currently, the option to create another FB is very prominent - we should keep that in mind too. Also, if someone wants to create another FB with a same expiry date,  it does not really make any sense to create an additional one with a lower amount - I cannot think of any reason where that makes sense, other than wanting to lock coins - for which I am sure there are other tools available.
Finally, there is a ticket for a complete overhaul of the FB creation flow: https://github.com/joinmarket-webui/jam/issues/650
We should tackle that after this feature is implemented. Currently, the code regarding FBs is of rather poor quality and not very pretty.

cool I am working on the issue, and done with the logic part. Now I have to mess a bit with frontend to display the warning message. please let me know if this message "I understand what I am doing - I really want to create another Fidelity Bond with the same expiry date" is enough to display or we should add anything else.
Can you also assign me this issue, if this is how things work here. Although I can start a draft pull request as well.
Probably we should get this issue fixed by tomorrow :)

cool I am working on the issue, and done with the logic part. Now I have to mess a bit with frontend to display the warning message. please let me know if this message "I understand what I am doing - I really want to create another Fidelity Bond with the same expiry date" is enough to display or we should add anything else.

ping @editwentyone

Can you also assign me this issue, if this is how things work here. Although I can start a draft pull request as well.

Assigned. :raised_hands:

Probably we should get this issue fixed by tomorrow :)

Hey, no pressure and no time schedule necessary. Let's discuss in the PR. Undraft it whenever you feel a review is due.

you could make a [checkbox] + text: "I understand what I am doing - I really want to create another Fidelity Bond with the same expiry date" that needs to be checked before the "Next" Button is available for you.
this checkbox is only visible when we checked that the same month + year is selected
good work :)


Fixed type on VI.10

Escaped a character on section VI step 10 to make text appear.

https://github.com/Plailect/Guide/commit/28d37dc0dd09b6aa49ee97e1beb8f55e553f4df4


Convert attributes to array in all convert functions

The convert function for products and categories already convert the attributes to an array calles attributes. This PR adds the conversion for all extendable structs to that you dont't have to use e.g. $group.attributes.core->get('my_cool_attribute') in the frontend templates

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-17426.
Please use this issue to track the state of your pull request.

We decided to close this PR because of time constraints and limited overall benefit to the product. If this change is still important to you, please create a new issue on https://issues.shopware.com so people can up-vote this feature.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.

Time constraints? This one is easy to merge ...


Skip JUnit tests to fix failing android build

Details

Fix failing build due to gradle attempting to compile Junit tests https://github.com/dkurt/openvino_java/actions/runs/5219539621/jobs/9441828252?pr=22
Explicitly disable JUnit tests on Android

Fixes https://github.com/openvinotoolkit/openvino_contrib/pull/668#discussion_r1229010943

Oh, many thanks


FIXED UI ISSUES

Detailed Information

Related Issues
Closes #

Type of Change

[ ] 🐛 Bug fix or ⚙ enhancement
[ ] ✨ New feature or Chore (change with no new features or fixes)
[ ] 📚 Documentation update

Checklist (select as many as applicable)

[ ] The code follows the style guidelines of this project.
[ ] All new and existing tests pass.
[ ] This pull request is ready to be merged and reviewed.

Please add the issue number @Otaiki1


When using .play() with nicovideo.jp link, it have some distube error

When I use <Distube>.play() with nicovideo.jp link, I have this URL error maybe from yt-dlp and distube:
06-10-2023 09:53:11 - ERROR       - DisTubeError [INVALID_TYPE]: Expected 'an URL', but got 'niconico_dmc:sm42833545/archive_h264_360p/archive_aac_64kbps' (string)
{
  level: 'error',
  message: DisTubeError [INVALID_TYPE]: Expected 'an URL', but got 'niconico_dmc:sm42833545/archive_h264_360p/archive_aac_64kbps' (string)
      at Function.DirectLink (D:\Github\AzurDream\node_modules\distube\src\core\DisTubeStream.ts:56:13)
      at _QueueManager.createStream (D:\Github\AzurDream\node_modules\distube\src\core\manager\QueueManager.ts:171:26)
      at _QueueManager.playSong (D:\Github\AzurDream\node_modules\distube\src\core\manager\QueueManager.ts:193:27)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async _QueueManager.create (D:\Github\AzurDream\node_modules\distube\src\core\manager\QueueManager.ts:39:19)
      at async _DisTubeHandler.playSong (D:\Github\AzurDream\node_modules\distube\src\core\DisTubeHandler.ts:340:24)
      at async _DisTube.play (D:\Github\AzurDream\node_modules\distube\src\DisTube.ts:210:9) {
    errorCode: 'INVALID_TYPE'
  },
  timestamp: '06-10-2023 09:53:11'
}

Maybe is from yt-dlp or distube?
Further information:

Plugin version: 1.1.3
DisTube version: 4.0.5
discord.js version: 14.13.0
Node.js version: 20.6.0
Operating system: Windows 11 x64

This is due to yt-dlp not returning the correct stream url for this provider I guess. I will check it later.


dnsmasq complains about /etc/hosts line 23

I use dnsmasq Version 2.89 as a DNS forwarder. During start it complains about  line 23 in /etc/hosts saying  "Wrong Address":
fe80::1%lo0 localhost
I am not familiar with dns resp. hosts syntax. is that something that has to be fixed here or with dnsmasq?

I just found https://github.com/StevenBlack/hosts/issues/1714
which talks about the same issue


Wrong nbextension version loaded via script

Environment data

VS Code version: 1.63)
Jupyter Extension version (available under the Extensions sidebar): 2021.11.100
Python Extension version (available under the Extensions sidebar): v2021.12.1559732655
OS (Windows | Mac | Linux distro) and version: Mac
Python and/or Anaconda version: 3.9.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Poetry
Jupyter server running: Local

Expected behaviour
Load the latest version of the nbextension distrbuted with a Python package as per this template repo
Actual behaviour
An old version of the nbextension is loaded every time even if I manually reach into the extension and delete the scripts folder.
Steps to reproduce:
pip install idom_jupyter==0.6.5

Then in a notebook cell run:
import idom_jupyter
from idom import component, html

@component
def Demo():
    return html.h1("Hello")

Demo()

This should display something like

Then, inside the scripts folder there should be the following file:
6d1d3934e795883f824531b16d0687f5a5124b176639403c4da6c0bbe0dbd3fd/index.js

I assume the 6d1d3934... is some sort of hash so that should be a way of verifying the contents. If not though, doing a search for "useLazyModule" inside index.js should yield a result. This function, useLazyModule does not exist in the latest version of the nbextension.
While the example above displays correctly, there are other features of this idom widget that do not work on account of this older version of the extension being loaded (it's hard to explain how to demonstrate the failure of these features due to other issues).
I'd be happy to hop on a call to talk through this since I'm not really sure what other information might be relevant to solving this.

I think this might be because I forgot to run jupyter nbextension install --py --sys-prefix idom_jupyter. Closing for now.

Never mind. That hasn't fixed it.

It looks to me like the python code (inside of idom_jupyter) is passing along the wrong version. It always asks for 4.0.
https://github.com/idom-team/idom-jupyter/blob/e3a9fc0ecffd9b01a0e4be7e678ac99d10e56213/idom_jupyter/widget.py#L59
You should probably ask idom_jupyter to upgrade their widget request.

The reason this works fine in jupyter is because jupyter supports loading nbextensions. Nbextensions don't work in VS code because they make a lot of assumptions about the DOM currently in use.
We load widgets from a CDN instead (not the nbextensions folder). When widgets are packaged for a CDN, they generally include everything they need to run independently of jupyter.
The failure in this case is that the python code is asking for the wrong version.


⚠ Bofrost.be has degraded performance

In 5bc53ab, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1410 ms

Resolved: Bofrost.be performance has improved in 12367f1.


Debug logging causes memory exception

After updating to nginx version 1.2.2, a debug log line in njs.d/dns/dns.js looks like it causes a memory exception:

2023/03/18 07:57:25 [error] 1384#1384: *270 js exception: MemoryError while proxying and sending to client, client: <IP_ADDRESS>, server: <IP_ADDRESS>:8053, upstream: "<IP_ADDRESS>:7053", bytes from/to client:140/0, bytes from/to upstream:43/27

2023/03/18 07:57:25 [error] 1384#1384: *267 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: query.doh.example.org, request: "POST /dns-query HTTP/2.0", upstream: "http://<IP_ADDRESS>:8053/dns-query", host: "query.doh.example.org"

After I added several more debug lines to see where the problem happened, I narrowed it down to this:
debug(s, "DNS Res Packet: " + JSON.stringify( Object.entries(packet)) );

(Note that the earlier debug line that dumps packet.answers to the log does work.)
I'm not skilled enough with JavaScript or the Nginx JS module to narrow down further, my apologies.  But commenting out this line and making no other changes allows the module to work again.  From what little I do know, I don't see an obvious reason why this log line would up and fail.
For context, my DoH setup is based on Scott Helme's instructions to use Nginx + DoH + Pi Hole, extended from the Nginx blog.

I don't know why either, but you're correct.
Setting var dns_decode_level = 0; instead of 3 makes the DNS queries work again.

Hi @wesmi - can you tell me what version of NJS you are using please?
Thanks,
Mark

Hello
I have the same problem using a docker image docker.io/library/nginx:1.21.1 it is perfectly fine.
With a docker.io/library/nginx:1.22.1 it crashes.
The njs version for 1.21.1:
dpkg -s nginx-module-njs
Package: nginx-module-njs
Status: install ok installed
Priority: optional
Section: httpd
Installed-Size: 3928
Maintainer: NGINX Packaging<EMAIL_ADDRESS>Architecture: amd64
Version: 1.21.1+0.6.1-1~buster
Provides: nginx-module-njs-r1.21.1
Depends: libc6 (>= 2.25), libpcre3, libreadline7 (>= 6.0), nginx-r1.21.1
Description: nginx njs dynamic modules
 njs dynamic modules for nginx
Homepage: https://nginx.org/

./usr/bin/njs -v
0.6.1

The njs version for 1.22.1:
dpkg -s nginx-module-njs
Package: nginx-module-njs
Status: install ok installed
Priority: optional
Section: httpd
Installed-Size: 4740
Maintainer: NGINX Packaging<EMAIL_ADDRESS>Architecture: amd64
Version: 1.22.1+0.7.11-1~bullseye
Provides: nginx-module-njs-r1.22.1
Depends: libc6 (>= 2.29), libpcre2-8-0 (>= 10.32), libreadline8 (>= 6.0), libssl1.1 (>= 1.1.1), libxml2 (>= 2.7.4), nginx-r1.22.1
Description: nginx njs dynamic modules
 njs dynamic modules for nginx
Homepage: https://nginx.org/

/usr/bin/njs -v
0.7.11

Ant

Sorry for the delay in replying, I am also on njs 1.22.1:
dpkg -s nginx-module-njs Package: nginx-module-njs Status: install ok installed Priority: optional Section: httpd Installed-Size: 4846 Maintainer: NGINX Packaging<EMAIL_ADDRESS>Architecture: amd64 Version: 1.22.1+0.7.11-1~jammy Provides: nginx-module-njs-r1.22.1 Depends: libc6 (>= 2.35), libpcre2-8-0 (>= 10.32), libreadline8 (>= 6.0), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), nginx-r1.22.1 Description: nginx njs dynamic modules  njs dynamic modules for nginx Homepage: https://nginx.org/

This was caused by the packet object containing the binary DNS packet inside packet.data.
I've added a new $dns_debug_level variable so that debugging can be enabled at decode levels lower than 3 (max). If the packet is going to be logged, then I delete the data entry from packet before logging it.
See https://github.com/TuxInvader/nginx-dns/commit/e04a8d784f86f33a9923c9adb94fbda8abcd2309


VRV.co extractor error has occurred. (caused by KeyError('streams',))

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.09.24. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[ x] I've verified and I assure that I'm running youtube-dl 2017.09.24
$ youtube-dl --version
2017.09.24

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
There are a couple of issues, but they're tagged geo-restricted and other user failures. I believe my issue is unique.

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-u', 'PRIVATE', '-p', 'PRIVATE', 'https://vrv.co/watch/G675N2D1R/HarmonQuest:The-Quest-Continues', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.09.24
[debug] Python version 3.6.2 - Linux-4.12.10-2-zen-x86_64-with-arch
[debug] exe versions: ffmpeg 3.3.4, ffprobe 3.3.4, rtmpdump 2.4
[debug] Proxy map: {}
[vrv] G675N2D1R: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/youtube_dl/extractor/common.py", line 434, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.6/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
    streams_path = video_data['__links__']['streams']['href']
KeyError: 'streams'
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/youtube_dl/extractor/common.py", line 434, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.6/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
    streams_path = video_data['__links__']['streams']['href']
KeyError: 'streams'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 777, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.6/site-packages/youtube_dl/extractor/common.py", line 447, in extract
    raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

I have verified that my username/password on the commandline are correct and that I'm able to view this episode using the given URL in my browser. I also tried the shorter URL https://vrv.co/watch/G675N2D1R which also failed in the same manor.

I'm also having this issue. I noticed the other one is geo-restricted so if it helps at all, I'm in the US
`youtube-dl https://vrv.co/watch/GYX084D3R/HarmonQuest:The-Quest-Begins --verbose
[debug] System config: ['--prefer-free-formats']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://vrv.co/watch/GYX084D3R/HarmonQuest:The-Quest-Begins', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.5.4 - Linux-4.13.10-100.fc25.x86_64-x86_64-with-fedora-25-Twenty_Five
[debug] exe versions: none
[debug] Proxy map: {}
[vrv] GYX084D3R: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 434, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
streams_path = video_data['links']['streams']['href']
KeyError: 'streams'
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 434, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
streams_path = video_data['links']['streams']['href']
KeyError: 'streams'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/youtube_dl/YoutubeDL.py", line 783, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 447, in extract
raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.`

Okay so the account-needed tag was added but I have an account I've paid for and I've tried authenticating as well. Here's the output for the time I authenticated
[debug] System config: ['--prefer-free-formats']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://vrv.co/watch/GYX084D3R/HarmonQuest:The-Quest-Begins', '-u', 'PRIVATE', '--verbose']
Type account password and press [Return]:
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.5.4 - Linux-4.13.10-100.fc25.x86_64-x86_64-with-fedora-25-Twenty_Five
[debug] exe versions: none
[debug] Proxy map: {}
[vrv] GYX084D3R: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 434, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
    streams_path = video_data['__links__']['streams']['href']
KeyError: 'streams'
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 434, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/vrv.py", line 110, in _real_extract
    streams_path = video_data['__links__']['streams']['href']
KeyError: 'streams'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/youtube_dl/YoutubeDL.py", line 783, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 447, in extract
    raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.```

an account is needed for developers interested/willing to add support for authentication, currently youtube-dl only support videos that don't require an account(free and non age-restricted videos).

So it's failing because it can't find watch.mediaResource.json.__links__.streams. I went through the mediaResource object and found that indeed streams isn't there. The main thing it was getting from streams was the href which has been moved up to just watch.mediaResource.json.href. After changing line 110 from streams_path = video_data['__links__']['streams']['href'] to streams_path = video_data['__href__'] I got the below error after running pytho3n youtube_dl/__main__.py https://vrv.co/watch/GYX084D3R/HarmonQuest:The-Quest-Begins -u<EMAIL_ADDRESS>--verbose
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://vrv.co/watch/GYX084D3R/HarmonQuest:The-Quest-Begins', '-u', 'PRIVATE', '--verbose']
Type account password and press [Return]:
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.11.06
[debug] Git HEAD: 61fb07e15
[debug] Python version 3.6.2 - Linux-4.13.5-200.fc26.x86_64-x86_64-with-fedora-26-Twenty_Six
[debug] exe versions: ffmpeg 3.3.4, ffprobe 3.3.4
[debug] Proxy map: {}
[vrv] GYX084D3R: Downloading webpage
[vrv] GYX084D3R: Downloading CMS Signing JSON metadata
[vrv] GYX084D3R: Downloading streams JSON metadata
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/twiclo/Projects/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
    ie_result = ie.extract(url)
  File "/home/twiclo/Projects/youtube-dl/youtube_dl/extractor/common.py", line 437, in extract
    ie_result = self._real_extract(url)
  File "/home/twiclo/Projects/youtube-dl/youtube_dl/extractor/vrv.py", line 139, in _real_extract
    self._sort_formats(formats)
  File "/home/twiclo/Projects/youtube-dl/youtube_dl/extractor/common.py", line 1075, in _sort_formats
    raise ExtractorError('No video formats found')
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

It looks like VRV changed the way they serve videos. Here's a blog post talking about it in March: https://medium.com/ellation-tech/improving-video-quality-for-crunchyroll-and-vrv-dd587261a364
It looks like a lot of the extractor is going to need a rewrite because of this. Am I right in thinking this or is there something I'm missing?

The main thing it was getting from streams was the href which has been moved up to just watch.mediaResource.json.href. After changing line 110 from streams_path = video_data['links']['streams']['href'] to streams_path = video_data['href'] I got the below error after running

it hasn't moved up, you're requesting the same data that the extractor already have(video_data).

It looks like VRV changed the way they serve videos. Here's a blog post talking about it in March: https://medium.com/ellation-tech/improving-video-quality-for-crunchyroll-and-vrv-dd587261a364
It looks like a lot of the extractor is going to need a rewrite because of this. Am I right in thinking this or is there something I'm missing?

no, the article you're referring to is about their change from old CBR RTMP streams to the new VBR HLS streams.

Okay so, just to clarify with your previous comment about authentication, does the program not support authentication AT ALL or has it just not yet been built into this extractor?

does the program not support authentication AT ALL or has it just not yet been built into this extractor?

it's on the VRV extractor, every extractor that require authentication need's to add some code to handle the login process(and sometimes auth tokens if needed), this code is specific to that website.
as an example lynda and udemy extractors both support authentication but the code to add support is different.

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-f', 'best', 'https://vrv.co/watch/GYX0EDP5R/', '-u', 'PRIVATE', '-p', 'PRIVATE', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.11.15
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: ffmpeg N-89073-gff8f40a630, ffprobe N-89073-gff8f40a630
[debug] Proxy map: {}
[vrv] GYX0EDP5R: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\extractor\common.py", line 437, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\extractor\vrv.py", line 110, in _real_extract
KeyError: 'streams'
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\extractor\common.py", line 437, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\extractor\vrv.py", line 110, in _real_extract
KeyError: 'streams'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\YoutubeDL.py", line 784, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp10f7prtw\build\youtube_dl\extractor\common.py", line 450, in extract
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('streams',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This particular video requires a subscription to view, so authentication appears to be an issue.

I think I see the probem.
I've been trying to download a movie off of vrv.co manually, and they've encrypted their videos inside a .M3u8 file referencing an array of .ts files with AES-128-CBC encryption. I'm working on decrypting a segment using the OpenSSL binaries, but unfortunately programming this into Youtube-DL is a bit over my level.
If any devs need me to provide my vrv.co account, I'd be happy to!

If you have the latest firefox (57) you can downgrade to the prior release (56.0.2), and then get the addon video downloader helper to download from vrv and other similar sites.  Disable updates for the browser if need be or it will autoupdate.
Version 7 of VDH is partially broken so these steps are needed to use the prior release which is 6.3.3 on firefox.
Chromes version of VDH doesn't work.
I am doing this until youtube-dl gets full login functionality for these sites.

Just to clarify for everyone, the issue is that a login is required to view this video and the login hasn't been built into the vrv extractor yet. It works just fine if you're watching a video that requires no account. Doesn't have anything to do with the video format. Thanks for all the help everyone

Oh okay, seems I was mistaken.

So i've been looking into this bug, if you use the cookies you should be able to get around the login.  The problem is you still can't get the streams.

Hi, has there been any progress on this?

Hi, is anyone working on this bug?

If someone donates a premium account is a dev from youtube-dl willing to work on this issue?

Using 'Flash Video Downloader' to get the stream url and ffmpeg to download ffmpeg -i <url> -c copy -bsf:a aac_adtstoasc output.mp4 it works.
Looks like the download_hls url from the streams json file works too.
@hadees I think you were close. That ID can be found in the episodes endpoint (there's a stream object that points to the stream json) which can be built using the episode id from the url.
Not sure how it would work with one-off files like movies but it's a start.

Playing around with it, definitely an auth issue. We might be able to get around calling the cms_resource route by just building the resource urls ourself by using the url signature from: window.__INITIAL_STATE__.index.endpoints.discIndex.href
I feel like Im close, can hit the generated url in curl and get data, but using _download_json gives me a 403.
Anyone else wanna jump in?

I can't really do this (or even provide an account -- not sure I want to supply my normal credentials) however I do want to add this as it may be relevant.
I have a VRV account linked to CrunchyRoll.  I'm noticing that if I use an authenticated account (cookies method) that is currently using the HTML5 player to download a CrunchyRoll url that it will retrieve from the VRV servers.  It might help someone checking it out.
Oh and please don't forget about subs.  Flash Video Downloader doesn't download soft subs from VRV.

It has a 30 Day Free Trial.  I would think this could be used to add support.

If someone donates a premium account is a dev from youtube-dl willing to work on this issue?

I'm willing to donate a premium account for 2 months to help fix this issue and add login support for VRV.

The odd thing is that this isn't a problem with all VRV.co content.  I watched all of Cells at Work! and The Ancient Magus' Bride appears to be fine too, just to name a few.  The quality difference with Madvr and a .3dlut vs viewing in any web browser make me love this extension, so the hit and miss nature kind of sucks.  For bandwidth savings, it makes me wonder if VRV actively encrypts high-volume titles knowing that extensions like this exist.

If this can get fixed soon by anyone let me know.  Funimation will be pulling their content from VRV (including Funimation owned Crunchyroll content), so we need this working in time to download those series before they get removed from VRV.

Anyone adding support for this?

Hi can some help me im trying to download from vrv is my command wrong or does it not work anymore i have the latest version of Youtube-dl   but this command is not working
youtube-dl -u -p pasword  https://vrv.co/watch/GYW42W906/The-Fruit-of-Grisaia:An-Ordinary-School-Life


CAR Inline Example currently not working

Hello there,
the inline example in atproto/car/init.py stopped working last week.
The line repo = client.com.atproto.sync.get_repo({'did': client.me.did})
https://github.com/MarshalX/atproto/blob/1e1829efece8242343fff264d29b0b35cd780b10/atproto/car/__init__.py#L40
throw an atproto.exceptions.BadRequestError:
Response(success=False, status_code=400, content=XrpcError(error='InvalidRequest', message='Could not find repo for DID: '), headers=Headers({'date': 'Mon, 20 Nov 2023 14:09:40 GMT', 'content-type': 'application/json; charset=utf-8', 'content-length': '100', 'connection': 'keep-alive', 'x-powered-by': 'Express', 'access-control-allow-origin': '*', 'ratelimit-limit': '3000', 'ratelimit-remaining': '2998', 'ratelimit-reset': '1700489680', 'ratelimit-policy': '3000;w=300', 'etag': 'W/"64-u+z2SVfRs2zfn34PuZ9u5A4P55k"', 'vary': 'Accept-Encoding'}))
I could verify the correctness of the DID in other ways.
Additional information: the more or less 'official' indigo-implementation seems to have a similar issue. Did they change the handling in the protocol?
Thanks for looking into it.
Harald

Hello, maybe this is related https://github.com/bluesky-social/atproto/discussions/1832

Thanks for your quick reaction, especially since the release 1.0.0 is still further up on the road...
It looks like it might be:
client.me.did possibly returns a DID that's no longer valid for get_repo
Will you be able to fix this on the python side to get back to the previous behavior, or will the coding just get more complicated for users of your python wrapper?
(I assume the issue won't simply disappear when they have fiished the roll-out, or will it?)
Cheers
Harald

You receive the server side error. Python SDK works properly and show  this error as expected. To be honest I don't know why server returns this error for you. Perhaps your account has not been migrated yet or something. Try to login to the official bsky app. Also, maybe you are using the deprecated server method. Double-check if there is another way to get a repo
I'll try to run this example with my account later

True, the SDK's get_repo just gives the server side error. Using indigo you'll get the same error, as indeed @ericvolp12 with his Bluesky Walker can't do but write this error message into the CAR file for download.
Getting a repo essentially works without login. I can look for the DID elsewhere, say my_did, and just use
repo = client.com.atproto.sync.get_repo({'did': my_did})  without using client.login('my-handle', 'my-password') at all.
So I already tested with a handful of DIDs, and it's been the same error. It seems to be related with what @strideynet describes here.
Most probably it concerns all accounts that have been migrated already.
The official app doesn't have the option to DL (archive) the repo, and all programmatical ways I know of - indigo, dart api, Python SDK - seem to have the same problems.
I fear it can only be fixed by bluesky-social, and they probably have different priorities... :(

Repos have been moved to new PDSs and don't all live on bsky.social anymore. You should be checking a user's DID doc to figure out which PDS is hosting their repo and then downloading it from there using the getRepo endpoint or you can download it from the Relay service at bsky.network which stores a mirror of all repos for a given user. Since migrating users to new PDSs, some users have repos with bad signatures that will be fixed the next time they create a record, so the Relay service may not provide the repo for those users while their PDS  will still work for getRepo. See https://atproto.com/blog/repo-export#on-another-instance


Implement Subheader v2 Component

Spec reference: https://material.google.com/components/subheaders.html

I think with the subheader space it would be best to add subheadings into the components that they are defined for. This has been a quirky thing about the specification for a while with me. I don't understand why this is its own component defining a single piece of 3-4 other specs, when it should just be a section within those specifications. That way the class naming is more streamlined.
.mdl-menu__subheading vs .mdl-subheading--menu, I think the former version is much better for developers given the scoping of the BEM syntax we use.

Superceded by https://github.com/material-components/material-components-web/issues/33


Verification on 1.7.2 fails (Kubectl apply)

When following the instructions for the "Kubectl apply", installation fails verification with the following error:
❯ bash -x ./validate.sh
+ kubectl apply -f test-resources.yaml
namespace/cert-manager-test unchanged
Error from server (InternalError): error when creating "test-resources.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-managercert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": service "cert-managercert-manager-webhook" not found
Error from server (InternalError): error when creating "test-resources.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-managercert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": service "cert-managercert-manager-webhook" not found

Deployed with kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.2/cert-manager.yaml as outlined in the documentation.
Here are the manifests for good measure:
❯ cat test-resources.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: cert-manager-test
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: test-selfsigned
  namespace: cert-manager-test
spec:
  selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: selfsigned-cert
  namespace: cert-manager-test
spec:
  dnsNames:
    - example.com
  secretName: selfsigned-cert-tls
  issuerRef:
    name: test-selfsigned

Describe the bug:

Expected behaviour:

The expected behavior is that verification passes.
Steps to reproduce the bug:

Just follow the steps outlined here.
Anything else we need to know?:
Environment details::

Kubernetes version: v1.23.3+k3s1
Cloud-provider/provisioner: Rancher K3s
cert-manager version: 1.7.2
Install method: static manifests

/kind bug

/remove-lifecycle stale

i am expiriencing the same problem, it worked a while ago.
apply the issuer results in the mentioned error message

/remove-lifecycle rotten

Got the same issue.
The webhook is trying to post to "https://cert-manager-cert-manager-webhook..."
It looks like an old version of a helm chart has some config stuck somewhere on the cluster. I deleted everything I could find related to this helm chart, but somehow the webhook server seems to have kept the old helm chart config.

I experienced the same issue.
I outlined a solution on Stackoverflow.
TL;DR
I applied and deleted cert-manager a few times also in different namespaces. Just deleting the respective namespace didn't clean up all the resources, but after following the official guide to uninstalling cert-manager and applying / installing cert-manager again, everything worked as expected.
Resources I had still lying around were for example:
kubectl get -A validatingwebhookconfigurations.admissionregistration.k8s.io
kubectl get -n kube-system  rolebindings.rbac.authorization.k8s.io
...

Maybe this helps.

I am still seeing this error when applying the manifests from https://cert-manager.io/docs/installation/kubectl/#steps. None of the suggested steps above have made a difference for me including uninstalling and reinstalling. Seeing this using 1.16.1


Random joke generator in javaScript: A Complete Gude

Article checklist
Formatting and structure checks

[X] Have you used the correct folder and file structure? - see Contribution Guidelines

[X] Is your article properly formatted in Markdown? - see Github Markdown guide

[X] Have you used our preferred heading structure? - H3 (###) and up

[X] Does your article follow any of the suggested structure formats? - see example formats

[X] Is your article over 750 words? - Tool: Wordcounter.net

[X] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[X] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[X] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[X] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[X] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[X] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[X] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[X] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[X] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[X] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #4088

Plagiarism check done.

@BrianaNzivu hello, I have made the requested changes. Thanks

@BrianaNzivu Hello, Apologies for the delayed answer; I'm currently prepping for end-of-semester examinations, but the improvements you proposed have been incorporated. Thanks

Tech review done 👍

Hi @EssyG10
Great Job on the article.
cc: @BrianaNzivu the image links were missing the leading / but that's a minor change


Add units to UnitConv classes.

Ready to merge

Coverage increased (+0.002%) to 99.426% when pulling 317f658f4eb02afbec445b37c7135e54551e1d0a on T-Nicholls:unitConvChanges into 875cb3205fa786995ac701a5e003af2996a03c53 on dls-controls:master.

Should we add a get_units(field) method or are we content with the get_unitconv(field).eng/phys_units syntax?

@willrogers I think this should be good to merge now.


remove xpress uncontrolled stdout

Tis fix aims to remove the stop Xpress from printing log information on the tdout that concern the reading phase of empty problems.
This fix does remove several prints of this type that precede the messages that benderswrites for the user
Reading Problem empty
Problem Statistics
           0 (      0 spare) rows
           0 (      0 spare) structural columns
           0 (      0 spare) non-zero elements
Global Statistics
           0 entities        0 sets        0 set members

This fix does not look for a solution for the solvers logs.
A separate issue should be created

the issue is not fixed


Add Unichain Sepolia Testnet

Adding a New Chain
This PR adds Unichain Sepolia  to the registry.
Checklist

[x] I have declared the chain at the appropriate Superchain Level.
[x] I have run just validate <chain-id> locally to ensure all local validation checks pass.
[x] I have run just codegen to ensure that the chainlist and other generated files are up-to-date and include my chain.

@trianglesphere did you specify sepolia-dev-0 in your environment file?


init CLI Command

What should be done?
Add an init command to the cli that creates the necessary files to run the client (currently the miden-client.toml configuration file).
How should it be done?

It should be added as another clap subcommand
Make sure that whenever we run a CLI command we use either the config file from the current dir, or check parent directories similar to what git does
Check if it's possible to add a message that is displayed after cargo install. If so, add a message suggesting the usage of miden-client init
Decide whether it should be possible to use if there is an existing config file already

When is this task done?
The task is done when you can run miden-client init and run commands on those particular client settings (test it from outside of the miden-client repo)
Additional context
No response

Reference: https://github.com/0xPolygonMiden/miden-base/pull/531#discussion_r1538038839

closing as #242 got merged, idk why this didn't close automatically


Error running npm install npm ERR<EMAIL_ADDRESS>install: prebuild-install || node-gyp rebuild

For deployment issues, please provide us with the following information:

Repro steps.

your project built successfully on your dev machine but failed on Azure?

npm install from inside azure function directory fails with error above

please write down your build tools and their versions (ie Msbuild <IP_ADDRESS>)
node v10.14.1
npm 6.4.1
tedious 5.0.3
async 2.6.2
readable-stream 3.2.0

Project structures.

in order to reproduce your issue at our end we need a simple
github repository
that highlights structure of the project

https://gist.github.com/gpazo/8ad631d3f6097d20b23af79917ab8032
The log/error given by the failure.
D:\home\site\wwwroot\HttpTrigger3>npm i
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>This version is no longer maintained. Please upgrade to the latest version.

><EMAIL_ADDRESS>install D:\home\site\wwwroot\HttpTrigger3\node_modules\keytar
> prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=10.14.1 runtime=node arch=ia32 libc= platform=win32)

D:\home\site\wwwroot\HttpTrigger3\node_modules\keytar>if not defined npm_config_node_gyp (node "D:\Program Files (x86)\npm\6.4.1\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\Program Files (x86)\npm\6.4.1\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  async.cc
  main.cc
d:\local\userprofile\.node-gyp\10.14.1\include\node\v8.h(21): fatal error C1083: Cannot open include file: 'memory': No such file or directory (compiling source file ..\src\main.cc) [D:\home\site\wwwroot\HttpTrigger3\node_modules\keytar\build\keytar.vcxproj]
  keytar_win.cc
d:\local\userprofile\.node-gyp\10.14.1\include\node\v8.h(21): fatal error C1083: Cannot open include file: 'memory': No such file or directory (compiling source file ..\src\async.cc) [D:\home\site\wwwroot\HttpTrigger3\node_modules\keytar\build\keytar.vcxproj]
  win_delay_load_hook.cc
..\src\keytar_win.cc(6): fatal error C1083: Cannot open include file: 'wincred.h': No such file or directory [D:\home\site\wwwroot\HttpTrigger3\node_modules\keytar\build\keytar.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (D:\Program Files (x86)\npm\6.4.1\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      D:\local\AppData\npm-cache\_logs\2019-03-07T23_51_14_831Z-debug.log

Debug your Azure website remotely.

it is recommended that you share your Web App name, directly or indirectly
we can take a look at what's going on.

Mention any other details that might be useful.
I'm pretty stumped on this one, the behavior only started recently and I've been using the same packages and their versions since the major Azure V2 update.

Thanks! We'll be in touch soon.

We don't have a complete support for native node module especially building it.  @ahmelsayed  what is the workaround?  Can user deploy a pre-built node native moduke?

yes they can deploy pre-build native modules as long as they were built on a Windows machine and are running the same node version locally and on Azure

@ahmelsayed I was hoping to continue using the in-portal editing for convenience, is the typical workflow moving forward the aws approach of develop locally zip it up and deploy?

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


[Event Request] Codeunit 5763 Whse.-Post Shipment - OnInitSourceDocumentHeaderOnBeforePurchaseHeaderReopen

Hi Team,
In codeunit 5763 we need possibility to replace and avoid using standard code. Having event in procedure InitSourceDocumentHeader, would be a perfect solution :

[IntegrationEvent(false, false)]
local procedure OnInitSourceDocumentHeaderOnBeforePurchaseHeaderReopen(var WhseShptLine: Record "Warehouse Shipment Line")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Deno upgrade fails on Windows 7

I don't know if Windows 7 is still supported, but I cannot install Deno 1.8.0 on my Windows 7 machine, while it works fine on my Ubuntu 20.04 LTS, ElementaryOS 5.1 Hera and PopOS 20.10 operating systems. For me it is not a big deal, because I don't like using Windows that much, but as a teacher, many of my students still use Windows 7 or even Vista, so knowing if something is supposed to work on their machines is an important part of getting them into the Deno universe.
Obs: Deno 1.7.5 works fine, and I believe it has something to do with the WebGPU API in the new 1.8.0 version, which may be missing some DLL file or something.

Duplicate of denoland/deno#9608

Duplicate of denoland/deno#9608

Actually it is not a duplicate of [denoland/deno#9608], because 1.7.5 works fine here, and 1.8.0 doesn't, while om 9608 he cannot go from 1.7.0 to 1.7.5, and both error codes are different.

The same problem, but running with RUST_BACKTRACE = 'full', in case it helps.
$Env:RUST_BACKTRACE='full'

The fundamental problem is the we don't target and test on Windows 7.  That it works is coincidence versus intent.

The fundamental problem is the we don't target and test on Windows 7. That it works is coincidence versus intent.

So any issue that happens on a Windows 7 machine will be marked as a duplicate of [denoland/deno#9608]?


Improve Responsive Sidebar

Hi, I am a contributor in GSSOC'23.
I want work on Improving the Responsive side bar project.
Please assign me this task under label gssoc23
problem -

letter-spacing in sidebar is not proper.
sidebar icons and title are stacked on top of each other in each card

solution -
I will make icons and title stacked horizontally and Improve the letter-spacing

I want work on Improving the Responsive side bar project. Please assign me.

Hello @pranjay-poddar
I am a contributor in GSSOC'23. I would like to solve this issue. Please assign me this task under label gssoc23.
Problem identified :-
1.	Menu item names and icons are not aligned properly
2.	The sidebar title is not descent
3.	Letter-spacing is not appropriate
4.	The CSS doesn’t look eye-catching
Solution :-
I will make the icons and menu-item names aligned properly and change the menu-title name “sidebar” and Improve the letter-spacing. Moreover , I will make it more descent and eye-catching . I will also work on improving the hamburger-menu icon.

I am a contributor in GSSOC'23. I would like to solve this issue. Please assign me this task under label GSSOC'23.
Problem Solution:
1.Utilize CSS media queries
2.Prioritize important content
3.Implement a toggle button
4.Optimize touch interaction
5.Test across multiple devices

Hello @pranjay-poddar
I am a contributor in GSSOC'23. I would like to solve this issue. Please assign me this task under label gssoc23.
Possible Solutions for the problems

Using Media queries in order to improve the responsiveness of the navbar
Improving the design and the layout keeping user-friendliness at high priority
Testing the code over multiple screen sizes in for better responsiveness

I would like to do this task .
Please assign me the task

Hi @Saurabh-kumar09, I've successfully the Improved the layout issue and sent the pull request but still It's not been assigned.
Kindly please assign this issue and merge the pull request.


Non SemVer jar files are renamed badly when copying into the distribution dir

Expected Behaviour
Jar files are renamed into the distribution directory without their version number.
Actual Behaviour
If you have a dependency that doesn't conform (vaguely) to semantic versioning, then the jar rename that happens when copying jar files into the distribution directory are renamed to be XXX-version-SNAPSHOT.jar.jar which doesn't stop things from working because of the dynamic way in which jars are loaded, but is obviously confusing.
Steps to reproduce
Shows the error.
Use : https://github.com/adaptris-labs/interlok-twilio-sms/tree/develop
Note that the releaseVersion=4-SNAPSHOT (i.e. the custom code is build into a jar called interlok-twilio-sms-4-SNAPSHOT.jar)

gradle assemble
If you check build/libs then the jar is named properly.

$ ls build/libs
interlok-twilio-sms-4-SNAPSHOT.jar

If you check build/distribution/lib then interlok-twilio-sms is called interlok-twilio-sms-4-SNAPSHOT.jar.jar

$ ls build/distribution/lib/interlok-twilio*.jar
build/distribution/lib/interlok-twilio-sms-4-SNAPSHOT.jar.jar

Workaround the error
Use: https://github.com/adaptris-labs/interlok-twilio-sms/tree/build-parent-jar-rename-issue
Note that this sets the custom code version to be pinned against the interlokVersion; i.e. 4.3.0-RELEASE causes the jar file to be named interlok-twilio-sms-4.3.0-SNAPSHOT.jar

gradle assemble
If you check build/libs then the jar is named properly.
If you check build/distribution/lib then interlok-twilio-sms is called interlok-twilio-sms.jar

The logic that was applied for https://github.com/adaptris/interlok-build-parent/pull/48 and https://github.com/adaptris/interlok-build-parent/pull/49 is the cause of this issue.
It's not a critical situation where you are writing custom components inline with interlok config (since you're in control of the version) but becomes more of an issue if your corporate versioning convention doesn't match semantic versioning...

This renaming is a bit of a pain. I'll raise a task in JIRA so we clearly have it in the backlog.


Distinguish between errors and warnings

I've run the power checker manually on some data from the tip of power-dev/r1.0 to establish the "baseline" to when running @nvpohanh's integration.
I see two types of issues reported on my data:

A couple of genuine power analyzer errors - I probably need to rerun those experiments:

[ ] Check errors and warnings from PTD logs
        '03-09-2021 15:26:20.358: ERROR: Bad watts reading nan from WT310' in ptd_log.txt

ERROR: Not all checks passed

Many warnings related to higher than desired measurement uncertainty. There's actually nothing I can do about it: the WT333E can only measure power from 1.2 W up, and I'm measuring at around 10 W.

[ ] Check errors and warnings from PTD logs
        '03-09-2021 21:17:42.684: WARNING: Uncertainty 1.05% above 1.00% limit for the last measurement sample!' in ptd_log.txt.

ERROR: Not all checks passed

I think the summary line should a WARNING in this case, not an ERROR.
Regardless, the run finished with two cheerful messages

All checks passed

All checks passed

I have no way of telling whether these message relate to some successful experiments, or it is an (incorrect) summary of the whole check (because the check contained the above errors).

I have also see Bad watts reading nan error....

After running the integrated script, I see all my good submissions being marked as invalid with a non-user friendly message:
[x] Check client sources checksum

[x] Check server sources checksum

[x] Check PTD commands and replies

[x] Check UUID

[x] Check session name

[x] Check time difference

[x] Check client server messages

[ ] Check results checksum

        list.remove(x): x not in list

[x] Check errors and warnings from PTD logs

[x] Check PTD configuration

[x] Check debug is disabled on server-side

ERROR: Not all checks passed

Good to see that WARNINGs are no longer ERRORs, but they do not get propagated to the submission checker's summary as such.

Many warnings related to higher than desired measurement uncertainty. There's actually nothing I can do about it: the WT333E can only measure power from 1.2 W up, and I'm measuring at around 10 W.

[ ] Check errors and warnings from PTD logs
'03-09-2021 21:17:42.684: WARNING: Uncertainty 1.05% above 1.00% limit for the last measurement sample!' in ptd_log.txt.

Hello,
I am a bit curious where 1.2W number came from, care to elaborate?
Since lowest range of WT333E power meter is 75W (for US wall power) or 150W (for EU wall power) it seems you are using wrong meter for power level. Probably best course of action would be to use WT310E which can go to 5mA range (750mW//1.5W US/EU range)
Uncertainty coming from meter when measuring 10W is 170mW which is 1.7%.
uncertainty calculations:
https://tmi.yokogawa.com/us/library/resources/faqs/power-analyzer-accuracy-and-basic-uncertainty-calculator/

Hi @dmiskovic-NV, sure. Quoting from my email to the Power WG from 4 February 2021:

A follow-up question about the measurement ranges given in the
Yokogawa WT300 series spec [1].

On page 4, the current ranges are depicted as:
WT310E: 50 uA .. 26 A.
WT310EH: 10 mA .. 40 A.
WT332E/WT333E: 5 mA .. 26 A

On page 11, the current ranges are listed as:
WT310E: 5 mA/10 mA/20 mA/50 mA/100 mA/200 mA/0.5 A/1 A/2 A/5 A/ 10 A/20 A
WT310EH: 1 A/2 A/5 A/10 A/20 A/40 A
WT332E/WT333E: 0.5 A/1 A/2 A/5 A/10 A/20 A

The way I read this is as follows.

For WT310E, the narrowest current range is I = (50, 5000) uA = (0.050,
5.000) mA. Therefore, at the UK voltage of 240 V, the narrowest power
range that can be measured is thus P = (12, 1200) mW = (0.012, 1.200)
W. Extending the range to I = (0.050, 50.000) mA would allow me to
measure P = (12, 12000) mW = (0.012, 12.000) W. To measure Raspberry
Pi 4 consuming between 3.4 W to 7.6 W under load [2], I should use the
latter range then.

For WT310EH, the narrowest current range is I = (10, 1000) mA. At 240
V, the narrowest power range is thus P = (2.4, 240) W. While the RPi4
power consumption is in this range, measurements will probably be too
imprecise to be useful. However, this should hopefully be alright for
devices in the 20-70 W range?

This got confirmed then.
Yokogawa WT333 is all I could get for this submission round in time. I'm getting WT310 for the next one.


Simplify progress bar event emitters

Closes #630
I think the code is a lot cleaner, but the UI is still a bit jumpy -- open to suggestions on:

how the toolbar should act when a user taps the circular progress bar, and vice versa -- I'm not sure if progress should be displayed on both or only one at a time
when to emit progress so the progress bar/circle advances smoothly -- right now I'm emitting progress at the start of an upload, after an observation has been created/updated, and when a photo is attached to an observation. we probably need to display progress for a few smaller in-between steps here, like when the photo is created

Ready for re-review. Mostly a lot of upload code cleanup, with some event emitter cleanup / simplification.


Minor documentation fix

Corrects a simple copy-paste error for is_on()

Noticed this simple copy-paste issue when I was looking through the code. Figured I'd submit a pull-request. Thanks for your work on this!


EPUB, MOBI or PDF file format support?

Hi @chenditc,
Thanks for the awesome work and it's really helps me a lot! Just wondering is there any future plan for supporting other Kindle-friendly file formats, e.g. .epub, .mobi or .pdf?
Cheers

I do want to support these file format, it's currently blocked because I can't find a good api to transform mhtml file to pdf or .epub.

As simple as it is, the best way to convert is as follows.
For every MHTML file do,

Open it up in Chrome
Ctrl+P - Save as PDF
Rinse and repeat

I do have some script to turn convert mhtml to html file in https://github.com/chenditc/safari-books-archive
Then if you host the HTML file on a web server, then you can use public service to create mobi and epub file from your site.
I don't think there is an easy way to do that in a chrome extension. So I prefer just leave the plugin as it.

Is there any tool that converts zip containing mhtml to epub/mobi?


How can we help the maintainers and keep Leaflet alive?

We all love Leaflet and appreciate the work of the maintainers (@mourner, @IvanSanchez, @johnd0e, ... ), thank you ❤
The active contributors knows that the maintainers have a lot of work with Leaflet and it's getting less and less attention, which is completely understandable but deadly for the project.
The Problem of less attention
I can only write for me but I would love to make some PRs and fix issues or update some old PRs which would be very useful, but I'm losing interest because I know the chance to get the PR is merged is currently very low and if it is approved it is possible that  it will still not merged because no one clicks the merge button ... I would say that I'm not the only one who think like that.
I think this is a result of available time of the maintainers for Leaflet + less active maintainers + amount of Issues / PRs. But it won't get better if contributors like me, go away from Leaflet because they think it is not worth to help.
I don't want to accuse you of anything, this project is voluntarily and no one of you must do anything. I only want to show the problem.
But how can we help to make it better?
I have not the perfect answer but maybe we find one together!
I will write here some thoughts:
Supporting
1. Organisation over Contributors
Let us (contributors) help to discuss on PRs / Issues and tag it with labels. The idea behind it is, that a PR can be tagged with "approved", "small", "needs maintainer help", "close", ... to make it easier for the maintainers to use their precious time for some useful / valuable things and not for something like #7562 that we contributors can do too. And also make it possibile to force some small PRs to get merged.
A way would be to grant on Github some contributors to add tags or to add Issues / PRs to a Github-Project. But I don't no if there is a way to do this without other permission granting.
Or other platforms. I only know Jira, but maybe there are some better ones out there
2. Voting
Maybe a voting system can be included to show the desires of the community.
Can be done by voting with 👍 like in lodash (but the system are not understandable for newbies) or on a other platform.
3. More maintainers / Junior-Maintainers
In my eyes it is a problem that the available time of the maintainers are not enough for Leaflet so it needs more maintainers. So my suggestions is to take some contributors into a Junior-Maintainer-Membership. They get step by step more permissions and can help you with some easy things but they also know that they get response and help from one of the maintainers.
4. Strategy
There are a few points which needs a decision how to go further with Leaflet.
For example:

#7128
Validation: In several comments was written that we should validate but how is not defined / decided
#7615
#7591
...

3. Slack / Discord?
I know from the OpenMapTiles project that it can sometimes helpful to have a channel where problems and other things can be discussed but I think that Leaflet is to large for this and also maintainers are needed for this.
4. Every X months a meeting?
Maybe it would be a chance to decide some topics and go further with Leaflet. But for this are topics needed and the time of the maintainers. Maybe a Issue can be created "Topics for the Leaflet-Meeting" where topics are collected and if there are enough a meeting can be made.
Updates / Releases
My suggestion would be to make more small releases. There are several bugs fixed in the master and the last Leaflet Release is older then a year (1.7.1 2020-09-04). It is always a huge step to make a big release so why not making multiple small ones in the year? Bugs are fixed earlier and there would be more contributors because their change is coming soon too.
One of the biggest issue since the last release is #7255 (2020-09-05) and the fix is still not released. (it is so much to read that I don't know if it is fixed, if not: ignore the last sentence 😄 )
It would be very nice to have a good discussion with the maintainers and other contributors.
Important! I don't want to criticize the maintainers and I don't want to say that they are doing something wrong! I only want to show what are problems in my eyes.

I am not so optimistic about Leaflet 2.0.
It demands a lot of resources, but we just do not have so much.
Imagine: devs works so hard, but early version is still less stable, and lacks of important features.
And it may not survive API breaking, as there is too little gain for (thousands of) existent projects to adapt their sources to 2.0.
So I'd rather bet for evolutionary development, step by step. Discontinue IE<11 support, modernize/clean up code and css, deprecate polyfills, ...

Yes I see this points problematic too.
A suggestion: We can say with 2.0 we start a new evolution where we make this steps with each new version. We can create a Roadmap what we want to reach in which release. Instead of 1.9 we call it now 2.0 and make it with the major release visible that there will be changes.
Maybe we need first to create a summary what we think would be good to change

Getting rid of global switches (L_NO_TOUCH and L_DISABLE_3D)

Such switches could be still useful for debugging and testing.
Also related: #7335

Considering removal (or extraction into a plugin) of the Canvas renderer if it's not widely used given typical Leaflet use cases (no need for heavy vector rendering, where libraries like GL JS do much better), and performance advancements for SVG in browsers over the last decade.

SVG becomes too slow at (as low as) a thousand of objects. GL JS may be fast, but a way worse integrated into Leaflet than L.Canvas.
So it's too early to retire it.

So I'd rather bet for evolutionary development, step by step. Discontinue IE<11 support, modernize/clean up code and css, deprecate polyfills, ...

That's exactly what I'm suggesting — focusing on things that make it easier to maintain and do evolutionary changes. Calling it Leaflet v2.0 is just a way to do a major breaking change like dropping IE<11.

The canvas renderer is important to me at the moment. Leaflet is already quite slow in our use case and svg would be a dealbreaker.

All right, keeping the canvas renderer! Just throwing ideas here, looking for potential things to drop for simplicity and easier maintenance.

I think having first-part support via .d.ts files would help the community a-lot. You wouldn't need to clutter your js with types, and people who like them can make them for the project.
Additionally, would this version remove the ".extend" syntax that existed before js had proper class support? It really shows the age of the library and i think a rewrite should deal with this issue.

Perhaps we can close this issue in favor of the discussion that has been started in #7729?

Another thing that may be helpful is to utilize GH issue form templates instead of the current markdown issue templates.
The benefits are that information can be required (so maintainers don't have to ask "can you please <provide that thing that the template already told you to provide but you erased/ignored it>"). It also provides standard HTML inputs such as checkboxes and select drop downs (no more broken checkboxes such as - [], - [ x]) in issue reports.
More info: https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/.

Thanks everyone for your input.

Perhaps we can close this issue in favor of the discussion that has been started in https://github.com/Leaflet/Leaflet/discussions/7729?

Just so we don't miss anything important (let me know if I did), here's a brief summary:

[x] Scheduled/periodic meetings are not helpful to already overloaded maintainers!
[x] Potential codebase modernization and other big breaking changes: https://github.com/Leaflet/Leaflet/discussions/7729.
[x] "Automate as much release routine as possible". I believe there's been a lot of work done in this area already.
[x] "More maintainers / Junior-Maintainers": @Falke-Design and I have since joined as collaborators.
[x] Revisit the labeling system: https://github.com/Leaflet/Leaflet/discussions/8018.
[ ] Sponsorship/crowdfunding may help, though it's not clear how that would work in practice.
(New issue/discussion to discuss separately?)
[ ] Stale bot.
(New issue/discussion to discuss details separately?)
[ ] Issue forms with YAML templates can help people create better issues.
(I'll open a separate issue.)
[ ] "Gratis iPhone 15 and iMac" for @IvanSanchez's birthday
(If you want more attention to your favorite bugs, please contact Ivan and make this a reality. 🙏🏼😄)

Again, thanks everyone for participating in this discussion.
I believe my previous comment summarizes this issue well. If you've suggested a feature here that hasn't been posted in https://github.com/Leaflet/Leaflet/discussions/7729, please do so!
As long as there is a demand for Leaflet, it will be kept alive by the maintainers and the community together. You can help by contributing to Leaflet directly, and also by sponsoring this project. ❤


(MAINT) Updates to README_BRANCHING.md related to 2.1 release

This commit contains some updates to the README_BRANCHING.md document
related to our change in strategy to do 2.1 development from the 2.1.x
branch and unfreeze the master branch for periodic mergeups from the
stable and 2.1.x branches.

:see_no_evil:


Wrong tcp packet content ?

Hi,
I've discovered your work when I was looking for a framework to manage TCP transport on my application.
Using TimeService example I've created a small program which send data over tcp
Here the code of the startup:
            var host = IPAddress.Parse("<IP_ADDRESS>");
            var port = 7000;
            var bootstrapper = new ClientBootstrap().SetTransport(TransportType.Tcp).Build();

            client = bootstrapper.NewConnection(Node.Empty(), NodeBuilder.BuildNode().Host(host).WithPort(port));
            client.OnConnection += (address, connection) =>
            {
                Console.WriteLine("Confirmed connection with host.");
                connection.BeginReceive(ReceivedCallback);
            };
            client.OnDisconnection += (address, reason) => Console.WriteLine("Disconnected.");
            LoopConnect();
            Write();

and here concerning the Write method:
            var command = Encoding.ASCII.GetBytes("TEST");
            _client.Send(command, 0, command.Length, new EmptyNode());

My server receive the message. but with invalid characters at the beginning.
I've checked using wireshark the communication and the sent contains invalid chars at the beginning.
Here the Content in hex for my "TEST" message
04:00:00:00:54:45:53:54
How can I fix it ?
Thanks in advance !

Hi Olin!
The invalid characters at the beginning are from the https://github.com/helios-io/helios/blob/dev/src/Helios/Serialization/LengthFieldPrepender.cs - this is how we frame messages in Helios by default.
You can turn this off inside ClientBootstrap via the following:
 var bootstrapper = new ClientBootstrap().SetEncoder(new NoOpEncoder()).SetDecoder(new NoOpDecoder()).SetTransport(TransportType.Tcp).Build();

This will not perform any message framing by default, so you need to ensure that somewhere you are using message framing or your application will fail as soon as messages stop being of a fixed / consistent size.

Thanks a lot for the Help!
I will test or soon


MM 10915

Summary
Add ability to join team and channel through url.
This will address the issue of joining the team after account creation or login if there is a redirect.
TODO:
Add access denied screen for private teams and private channels?
Ticket Link
MM-9479
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[ ] Added or updated unit tests (required for all new features)
[x] Has UI changes
[ ] Includes text changes and localization file (.../i18n/en.json) updates

closing this. Wrong branch name!


Add GPU support to Cook

This adds support for:

GPU resources on agents, which will only be accepted if enabled in the
config file
Scheduling GPU jobs on GPU machines and non-GPU jobs on non-GPU
machines
Uses DRU & preemption with GPUs as well, but they're considered
independently
Adds GPUs to the REST API
If GPUs are enabled and the Mesos version doesn't support them, fails
loudly

This branch is ready for review--I am now testing this code on actual clusters to verify behaviors end-to-end.


Resolve UID

@sneridagh @robgietema I have a working version of the resolveuid feature in Volto now. I also added a Cypress test for this which passes. Problem is that this does not work reliably (both locally and on Travis, in tests and manually).
The REST API part seems to work fine (I added print statements to the code to show this) but Volto sometimes seems to show the old link instead of the new one (when an item has been moved).
I first thought it was a Volto/Redux update problem. Though, a hard reload of the page with the link does not help.
Maybe this is something we can discuss on Monday...

FYI: Guillotina tests are failing. Plone tests pass. Will look into it...


include ui-router?

hey, sorry about the really late response. I will be making some updates soon and will include it in that :+1:


Would be nice if dictionaries didnt default do downloading from PLAY store and instead had the option to download from your site.

Thank you for this fine software.

What steps will reproduce the problem?
1. Open up the hackers-keyboard from F-Droid repository
2. Click on get dictionaries

Could not open PLAY store

What is the expected behavior? What do you see instead?

Wanted the link to the self hosted dictionaries, as i dont have the PLAY store
installed.

Could be the way this is built, i dont know, but maybe include a an extra link
to the external dicts for repos that just pull down the general apk. That
wouldnt cost too much bandwidth, no?

Please provide any additional information below.

V 1.33

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 7 Jun 2013 at 6:58

Chime in @ #655, quick.


Android backstack is weird

Click to open A, press back button, press back button. This doesn't happen when SomeScreen is called directly, only when BeamerMaterialTransitionPage is being used.
The sample requires animations: ^2.0.0 package.
import 'package:animations/animations.dart';
import 'package:beamer/beamer.dart';
import 'package:flutter/material.dart';

class MyApp extends StatelessWidget {
  final routerDelegate = BeamerDelegate(
    locationBuilder: SimpleLocationBuilder(
      routes: {
        '/': (context, state) =>
            BeamPage(key: const ValueKey('home'), child: HomeScreen()),
        '/a': (context, state) => BeamerMaterialTransitionPage(
              key: const ValueKey('a'),
              title: 'a',
              child: const SomeScreen(),
            ),
      },
    ),
  );

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      routeInformationParser: BeamerParser(),
      routerDelegate: routerDelegate,
      backButtonDispatcher:
          BeamerBackButtonDispatcher(delegate: routerDelegate),
    );
  }
}

// SCREENS
class HomeScreen extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Home Screen'),
      ),
      body: Center(
        child: ElevatedButton(
          onPressed: () => context.beamToNamed('/a'),
          child: Text('Beam deep'),
        ),
      ),
    );
  }
}

class SomeScreen extends StatelessWidget {
  const SomeScreen();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('a'),
      ),
      body: Center(
        child: Text('a'),
      ),
    );
  }
}

void main() => runApp(MyApp());

class BeamerMaterialTransitionPage extends BeamPage {
  final Color? fillColor;

  BeamerMaterialTransitionPage({
    LocalKey? key,
    required Widget child,
    String title = 'hello',
    String popToNamed = '/',
    this.fillColor,
  }) : super(
          key: key,
          child: child,
          title: title,
          popToNamed: popToNamed,
          // + all other you might need
        );

  @override
  Route createRoute(BuildContext context) {
    return SharedAxisPageRoute(
      page: child,
      transitionType: SharedAxisTransitionType.horizontal,
      settings: this,
    );
  }
}

class SharedAxisPageRoute extends PageRouteBuilder<Object> {
  SharedAxisPageRoute({
    required Widget page,
    required SharedAxisTransitionType transitionType,
    required RouteSettings? settings,
  }) : super(
          pageBuilder: (context, primaryAnimation, secondaryAnimation) => page,
          settings: settings,
          transitionsBuilder: (
            context,
            primaryAnimation,
            secondaryAnimation,
            child,
          ) {
            return SharedAxisTransition(
              animation: primaryAnimation,
              secondaryAnimation: secondaryAnimation,
              transitionType: transitionType,
              child: child,
            );
          },
        );
}

Hi @bernaferrari
I figured out the problem. Just remove the default popToNamed from yourBeamerMaterialTransitionPage and make it nullable; String? popToNamed,.
What happens here is that every pop (as well as the ones from Android back button) is overriden to do popToNamed / instead, which does beamToNamed and adds the new BeamState to history (that's a bug #335 which I linked here).

Ok, @slovnicki.
The issue now:
When going back, the URL changes from users/123 to users/. Is there an easy fix like popBack 2 things instead of 1?

@bernaferrari I see
#335 should be fixed soon and you'll be able to use popToNamed. But right now you will need to do this manually by specifying onPopPage (in you relevant BeamPage). I believe something like this should work for you:
onPopPage: (context, delegate, page) {
  delegate.beamStateHistory = [];
  delegate.update(
    state: BeamState.fromUriString('/'),
  );
  return true;
}

Nevertheless, this "pop twice" is an interesting idea and could be a nice feature for the future. I will add an issue for it: #336

@bernaferrari I fixed it: https://github.com/slovnicki/beamer/commit/f8ebe6590a997df92fbc6f280e0bfe3d33df4f1e
You can use popToNamed normally if you take beamer from GitHub

Sorry for the delay. Ok, that fixes in a single case. But what if
Home -> ScreenA -> ScreenB -> Home? Then when I press back it goes to ScreenB, but it should actually exit the app.


Removed the extra " in postFilenameTemplate

https://greasyfork.org/en/scripts/406535-instagram-download-button/discussions/134833
Credit goes to xxalexx.

Thanks for catching this.


feat: upgrade to vee-validate v3

What is accomplished by your PR?
This PR upgrates all components, tests and storybook to vee-validate version 3.x
Is there something controversial in your PR?
I needed to add a new dependency flush-promises in order to make the tests working
Link to the Issue

via slack

Checklist
New Feature / Bug Fix

[x] Run unit tests to ensure all existing tests are still passing
[x] Add new passing unit tests to cover the code introduced by your PR
[ ] Change documentation for the code introduced by your PR
[ ] Add Story / Design System Page for a new component introduced by your PR

Memory consumption looks good now!
This change was requested by me in the community Slack:

I’m running into a memory leak with vee-validate. It got fixed in version 2.1 (https://github.com/logaretm/vee-validate/releases/tag/2.1.0-beta.2) so I think we should update. Unfortunately there are breaking changes in 2.1 and without any code changes all form element are initially invalid  for me.
As the “next” branch of vuesion is using vee-validate v3, I was wondering how much effort it would be  to update it on the stable vuesion or if there’s any ideas why what the validation issue with v2.1 could be.

@xMartin fixed, there is still an issue with validating the checkbox but I also have a workaround. I pushed it and you can comment if this would be enough or if we should further investigate


Deed rolls seem to be rolling incorrectly - roll a 1 and a 6 shows in "Deed Roll". Roll a 4 and a 2 shows in "Deed Roll"

Deed roll ends up blank

Deed roll shows wrong number

Fixed by https://github.com/foundryvtt-dcc/dcc/commit/8d5bb5bb79cd7f176e33f56953b47d075059b707