nixos/systemd-stage-1: Support resolved

Description of changes
This comes with an additional change to put systemd-resolved.service in sysinit.target instead of multi-user.target, given that this is what the upstream unit file indicates in its [Install] section.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This still needs a NixOS test. Help would be greatly appreciated on this, because I'm not actually all that familiar with how to deal with DNS and have already spent hours trying to write a test that I'm pretty sure is nowhere near correct.

So, I've added a test for systemd-resolved, but I'm not quite satisfied with it in stage 1. I couldn't do the resolvectl query part of the test in stage 1 for some reason. I get this:
example.com: resolve call failed: The name org.freedesktop.resolve1 was not provided by any .service files

And looking back at the logs, I sometimes see something like this,
client # [    1.333575] systemd[1]: systemd-networkd.service: Unexpected error response from GetNameOwner(): Connection terminated
client # [    1.334477] systemd-sysroot-fstab-check[149]: Requesting swap.target/start/replace...
client # [    1.341035] systemd[1]: systemd-resolved.service: Unexpected error response from GetNameOwner(): Connection terminated

Or sometimes something like this,
client # [    1.311828] systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.network1': Transport endpoint is not connected
client # [    1.312865] systemd[1]: systemd-networkd.service: Cannot watch bus name org.freedesktop.network1: Transport endpoint is not connected
client # [    1.316867] systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.resolve1': Transport endpoint is not connected
client # [    1.317882] systemd[1]: systemd-resolved.service: Cannot watch bus name org.freedesktop.resolve1: Transport endpoint is not connected

Or sometimes nothing indicative of any problems. No matter the logs, I get the resolve call failed error from resolvectl.

Sounds like dbus is not running

@arianvp It is though. If I add print(client.succeed("systemctl status dbus.socket dbus.service")), I get this:
client: must succeed: systemctl status dbus.socket dbus.service
(finished: must succeed: systemctl status dbus.socket dbus.service, in 0.01 seconds)
● dbus.socket - D-Bus System Message Bus Socket
     Loaded: loaded (/etc/systemd/system/dbus.socket; linked; preset: enabled)
     Active: active (running) since Tue 2024-05-21 07:26:24 UTC; 5s ago
   Triggers: ● dbus.service
     Listen: /run/dbus/system_bus_socket (Stream)
     CGroup: /system.slice/dbus.socket

May 21 07:26:24 localhost systemd[1]: Listening on D-Bus System Message Bus Socket.

● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/etc/systemd/system/dbus.service; linked; preset: enabled)
     Active: active (running) since Tue 2024-05-21 07:26:24 UTC; 5s ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 99 (dbus-daemon)
      Tasks: 1 (limit: 1131)
     Memory: 388.0K (peak: 652.0K)
        CPU: 7ms
     CGroup: /system.slice/dbus.service
             └─99 /nix/store/pvyfwb5fyh0max87rkhch4ac4d9b90lq-dbus-1.14.10/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

May 21 07:26:24 localhost systemd[1]: Starting D-Bus System Message Bus...
May 21 07:26:24 localhost systemd[1]: Started D-Bus System Message Bus.

Ah, we didn't have the necessary dbus files from systemd included. Fixed, and ready for review!

This is really sweet! Thank you for your continued grind on making systemd in stage1 work, @ElvishJerricco. Appreciate you.


Shap Force Plot does not show all the feature value/names

Hi All,
I am trying to get all the features and values showing on the force plot but i could not achieve it unfortunately. basically the plot just shows few highest contributors to the output value and the others just show without name/value on the plot. what can i do to get all contributing feature name and values shown on graph?

I think you have to use attribute: feature_names='your_dataset_columns_names' in the shap.force_plot function


Generated cert has invalid common name

Also, https://<IP_ADDRESS> doesn't work.

Merged, core/pull-requests/257


NetObserv touchstone config update

Description
updating for metrics added in PR # 308 and aws s3 storage metric.

/cc @paigerube14 @nathan-weinberg

Can one of the admins verify this patch?

/lgtm

@mohit-sheth @rsevilla87 - could you PTAL and help merge? this should not impact anything.


latest seems broken

docker run -it toniher/couchdb-lucene:latest
./bin/run: 16: exec: java: not found

I quickly fixed it by rebuilding  it and adding in run-lucene.sh:
    export PATH=/usr/local/openjdk-11/bin:$PATH
before
runuser -l couchdb -c './bin/run'
so last 2 lines are
export PATH=/usr/local/openjdk-11/bin:$PATH
runuser -l couchdb -c './bin/run'

it is a problem in the bin/run script which is part of the lucene distribution.


Add cairo1 prank cheatcode

Closes #1748
Docs https://github.com/software-mansion/protostar/pull/1811

Docs here https://github.com/software-mansion/protostar/pull/1811

I merged the docs into this PR for easier review.


Add help and about

\about should give basic info about the bot.
\help should give usage info
\help command should give detailed help on command

[x] About command
[x] \help
[x] \help command

All done with 4b4fb91f20c6251835ba3c7f76d8fc619c4633ea and ebcee57


default server.xml

I am working thru converting the unit tests to gradletest for the 3.0 stuff.  i have a recurring problem i can't seem to fix.  If you create a new server, with no config files, common sense tells me liberty should generate a default server.xml.  but it doesn't appear to do that, and i can't find any code that generates a generic default server.xml
where is the code that generates that file?

That file gets generated as part of the create server command that gets called by the ant code. You can execute the command that generates a default server.xml file by going into the wlp/bin folder and executing ./server create.

that ant code seems pretty flaky.  I just ended up implementing my own generator.

Closing this issue due to lack of activity. Please feel free to reopen if you think issue has not been resolved.


Bad Label with Box Layout On RadioButtons

Test case:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                   xmlns:mx="library://ns.apache.org/royale/mx"
                   width="600" height="400" >
		<mx:HBox>
			<mx:RadioButton label="1" value="Radio 1"/>
			<mx:RadioButton label="2" value="Radio 2"/>
		</mx:HBox>
</mx:Application>

Note how "2" label is under the radio button icon
I think the width of the HBox is set to be 60px before the width of the last RadioButton is measured. Because of that the the last radio button's label overflows.

With the example I posted, now both buttons have labels misaligned, and also selecting one doesn't deselect the other.

also selecting one doesn't deselect the other.

I think I made a mistake here. The problem is I'm getting a selection that shouldn't happen, as can be seen here.
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:mx="library://ns.apache.org/royale/mx"
	applicationComplete="init()"
	width="600" height="400">
	<fx:Script>
	<![CDATA[
		import mx.controls.RadioButton;

		private function init():void
		{
			var rb1:RadioButton = new RadioButton();
			rb1.value = "Radio 1";
			rb1.group = myGroup;
			var rb2:RadioButton = new RadioButton();
			rb2.value = "Radio 2";
			rb2.group = myGroup;
			myBox.addElement(rb1);
			myBox.addElement(rb2);
			rb1.label = "1";
			rb2.label = "2";
			myGroup.selectedValue = "Radio 2";
		}

	]]>
	</fx:Script>
	<mx:RadioButtonGroup id="myGroup" selectedValue=""/>
	<mx:HBox id="myBox">
	</mx:HBox>
</mx:Application>

This was not a problem in Flex, probably because adding an element didn't immediately mean a check for selection according to group was made. 4aaaaca should provide a fix.

The layout problem in this example is partly because the label isn't yet populated when the rb is measured.

The layout problem in this example is partly because the label isn't yet populated when the rb is measured.

Workaround (tested) for that is to call parent.dispatchEvent(new Event("layoutNeeded")) after a label change, but that seems wasteful.

Well, you can check if "isWidthSizedToContent()" before sending layoutNeeded, but otherwise, that is the way things work in MXRoyale.  In Flex, the RadioButton would call invalidateSize() on itself when the label changed, and the LayoutManager would eventually get around to calling invalidateSize() on the parent for you.  MXRoyale is currently not using a LayoutManager because of potential issues with deferred updates in browsers.  So yes, in many cases you have to tell the parent to layout again.
In Basic, the "rules" are different.  For PAYG reasons, Basic components should not automatically call layoutNeeded on the parent.  As you said, it would be wasteful in many scenarios.  Instead the app developer is supposed to hook up just the properties they know affect layout to the parent layout via binding, custom code, or LayoutChangeNotifier.


Exporting volume from container running in windows 10 insider preview doesn't work

Description
I am trying the latest windows 10 insider preview build with docker overlay driver support.
I have a image thats build with the below Dockerfile
FROM microsoft/windowsservercore

COPY . C:/temp

SHELL ["powershell", "-Command"]

RUN New-Item c:\Qumram -Type directory; \
    New-Item C:\Qumram\start.ps1 -Type File -Value \
    'Param( \
        [string]$LogFilePath = \"C:\Qumram\config\config.log\" \
    ) \
    Copy-Item C:\temp\*  C:\Qumram\config -Recurse | Out-Null; \
    New-Item -Path $LogFilePath -Itemtype file -Force | Out-Null; \
    Get-Content -Path $LogFilePath -Wait;'

VOLUME C:\\Qumram\\config

SHELL ["powershell", "-File"]

HEALTHCHECK CMD exit 0
ENTRYPOINT C:\Qumram\start.ps1

And i deploy a stack using the below compose.yml file
version: '3.0'

volumes:
    windows-configuration:

services:
    config-windows-volume:
        image: josejiby/qumram:testconfig-windows-dev
        volumes:
            - windows-configuration:\\c\Qumram\config
        deploy:
            mode: replicated
            replicas: 1
            placement:
                constraints:
                    - engine.labels.type == windows
            restart_policy:
                condition: on-failure

I used to use volumes_from in the earlier 2.0 format in windowsservercore to share the volume, however i am using the new v3 format hence the named volume in compose file.
Steps to reproduce the issue:

I run `docker -H linuxhost stack deploy -c compose.yml test
It schedules and starts running the container
The container fails throwing an error starting container failed: container a85162e691c88570cc097eb709862659838d6e68291bf55f6aa1672b887bbc7c encountered an error during Start: failure in a Windows system call: The compute system exited unexpectedly. (0xc0370106)

Describe the results you received:
The container should have started exporting the folder as a named volume
Describe the results you expected:
The container crashes
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.24)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      windows/amd64
 Experimental: false

Output of docker info:
Containers: 5
 Running: 0
 Paused: 0
 Stopped: 5
Images: 57
Server Version: 1.13.1
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: l2bridge l2tunnel nat null overlay transparent
Swarm: active
 NodeID: mzpe8u9g1448u9aw7ph2s8wub
 Is Manager: false
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Default Isolation: hyperv
Kernel Version: 10.0 15031 (15031.0.amd64fre.rs2_release.170204-1546)
Operating System: Windows 10 Enterprise Insider Preview
OSType: windows
Architecture: x86_64
CPUs: 1
Total Memory: 1.983 GiB
Name: windows
ID: 5262:FAUI:VLWB:COL4:Z3HH:5XGE:DBPD:HFBS:VYXB:CNAY:VKV3:CGFT
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Username: josejiby
Registry: https://index.docker.io/v1/
Labels:
 type=windows
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
The windows host is running inside parallels along side an ubuntu vm, which is the master of the swarm.

@friism is this some kind of limitation ?

This may be a duplicate of / related to https://github.com/docker/docker/issues/31224, could you check if that looks the same?

@thaJeztah i believe its the same issue, i will close this one.

thanks!


fix[#51]: Explicitly export types

fix types issues

Noted, will fix up soon

fixed, can you please review


chore: bug: adjust WDS caption text style

Fixes #30896

Summary by CodeRabbit

Refactor

Reordered typography variants for improved consistency in design.

New Features

Enhanced feature flag checks to directly return true for specific flags, improving feature toggling.

Style

Adjusted the order of style options in the widget property pane for better usability.

@vadim Note: In the PR, I have just reverted the order caption and body. The reason is in the code, we don't specifically create sizes for body,caption,footnote etc. We just create some sizes and assign them by index.
return Object.keys(TYPOGRAPHY_VARIANTS).reduce((prev, current, index) => {
    return {
      ...prev,
      [current]: styles[index],
    };
  }, {} as Typography);

@jsartisan this seems to change the effective body size (and as a result all the widgets having text of that size), can we avoid that?

Few solutions i can think of:

Change default value of fontsize to "caption" instead of "body"
Rename "caption" altogether maybe?

@vadim

@jsartisan

Makes our semantic naming meaningless
I don't understand how changing the name would change the value.

@jsartisan this seems to change the effective body size (and as a result all the widgets having text of that size), can we avoid that?

@ichik You're right, but everything seems to be correct here. If we want to change the values, we can tweak the config and make the growth slower or something.

@vadim

I don't understand how changing the name would change the value.
I was just wondering why people are getting confused with caption is because of its name? maybe they expect "caption" to be smaller than "body". so i thought just changing the name would have cleared their confusion. just a random thought.


After enabling web support… iOS simulators disappeared

I have followed below url and enabled web for my flutter application.
https://flutter.dev/docs/get-started/web
flutter channel master
flutter config --enable-web
flutter create .
flutter run -d chrome
flutter build web
Everything went well and I am able to launch my application on Web. However, after enabling web my ios simulators not appearing in devices list.
flutter devices 2 connected devices:
Chrome • chrome • web-javascript • Google Chrome 80.0.3955.4 dev
Web Server • web-server • web-javascript • Flutter Tools
flutter --version
Flutter 1.10.15-pre.424 • channel master •
https://github.com/flutter/flutter.git
Framework • revision 289b4588f4 (21 hours ago) • 2019-11-06 02:51:17 -0500
Engine • revision 9726b4cb99
Tools • Dart 2.7.0
dart --version
Dart VM version: 2.6.0 (Thu Oct 24 17:52:22 2019 +0200) on "macos_x64"

/cc @jonahwilliams

I can't reproduce the issue:
jonahwilliams-macbookpro2:flutter jonahwilliams$ open -a Simulator.app
jonahwilliams-macbookpro2:flutter jonahwilliams$ flutter devices
Building flutter tool...
4 connected devices:

iPhone 11 Pro Max • 647BA2F4-7EA5-4846-B29B-35B6B4D2136D • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-1 (simulator)
macOS             • macOS                                • darwin-x64     • Mac OS X 10.14.6 18G87
Chrome            • chrome                               • web-javascript • Google Chrome 78.0.3904.87
Web Server        • web-server                           • web-javascript • Flutter Tools

@CherukuriSiva, can you please try again on the latest Flutter?

I did flutter upgrade. Still same.
Siva-MacBook-Pro:f_groceries siva$ flutter upgrade
Upgrading Flutter from /Users/siva/Documents/development/flutter...
Updating fbabb264e..e7073f9a1
.../lib/i18n/{stocks_en.arb => stocks_en_US.arb}   |    0
.../lib/i18n/{stocks_es.arb => stocks_es_ES.arb}   |    0
.../projectName.podspec.tmpl                       |    0
347 files changed, 12913 insertions(+), 4228 deletions(-)
Building flutter tool...
Upgrading engine...
Downloading Android Maven dependencies...                           0.8s
Flutter 1.10.16-pre.113 • channel master • https://github.com/flutter/flutter.git
Framework • revision e7073f9a1f (4 hours ago) • 2019-11-09 17:08:53 -0800
Engine • revision 31cd2dfca2
Tools • Dart 2.7.0
Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.10.16-pre.113, on Mac OS X 10.13.6 17G65, locale en-AE)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] Xcode - develop for iOS and macOS (Xcode 9.4.1)
✗ Flutter requires a minimum Xcode version of 10.2.0.
Download the latest version or update via the Mac App Store.
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.3)
[✓] Connected device (2 available)
! Doctor found issues in 1 category.
Sivas-MacBook-Pro:f_groceries siva$ flutter devices
2 connected devices:
Chrome     • chrome     • web-javascript • Google Chrome 80.0.3955.4 dev
Web Server • web-server • web-javascript • Flutter Tools
I am using Channel Master.
Siva-MacBook-Pro:f_groceries siva$ flutter channel
Flutter channels:
beta
dev

master
stable

I think the issue might be this:
[!] Xcode - develop for iOS and macOS (Xcode 9.4.1)
✗ Flutter requires a minimum Xcode version of 10.2.0.
Download the latest version or update via the Mac App Store.

Would you mind upgrading your Xcode and trying again?

Fixed.
I have updated my MacOS to Catalina and updated XCode to 11.2. Now the issue is fixed and I am able to see all devices.


Threat Found : Trojan:Win32/Wacatac.H!ml

My Windows Defender is blocking the build and detecting Trojan.
I am oncommit no 124. It was not the case with yesterday's Code.

Disable WD.
Naturally as processes read from memory via external processes, it will be flagged as something suspicious or straight up harmful.

There are other github Repositorys that only provide binarys. They are 100% Infected Viruses and pure Scam. If there would be Malware in Open Source Project. Github is really fast in removing such Scam Repositorys and Accounts. So if CS2_External would be suspicious, it would already be removed.

Great Thanks.
I am not sure why it just started showing up.
I am using this Exteral ESP since it only had walls and there were no issues from WD.

Great Thanks. I am not sure why it just started showing up. I am using this Exteral ESP since it only had walls and there were no issues from WD.

Because Windows Defender automatically uploads your exe and other files, if they detect some uncommon behavior, they will flag that file. So yesterday it was safe, but today it's unsafe. That's why.
https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/cloud-protection-microsoft-antivirus-sample-submission?view=o365-worldwide#sample-submission-settings


Suggestion to create a pypi package for this

for #11

(.venv) jgu@jgu-pc:~/self_repos/shell-functools (master%=) % pip uninstall ft
Uninstalling ft-1.0.0:
  /home/jgu/self_repos/shell-functools/.venv/bin/filter
  /home/jgu/self_repos/shell-functools/.venv/bin/foldl
  /home/jgu/self_repos/shell-functools/.venv/bin/ft-functions
  /home/jgu/self_repos/shell-functools/.venv/bin/map
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft-1.0.0-py3.6.egg-info
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__init__.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/__init__.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/command.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/error.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/functions.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/internal.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/termcolor.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/test_command.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/__pycache__/types.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/command.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/__init__.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/__pycache__/__init__.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/__pycache__/filter.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/__pycache__/foldl.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/__pycache__/map.cpython-36.pyc
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/filter.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/foldl.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/commands/map.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/error.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/functions.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/internal.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/termcolor.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/test_command.py
  /home/jgu/self_repos/shell-functools/.venv/lib/python3.6/site-packages/ft/types.py
Proceed (y/n)? y
  Successfully uninstalled ft-1.0.0
(.venv) jgu@jgu-pc:~/self_repos/shell-functools (master%=) % pip install .
Processing /home/jgu/self_repos/shell-functools
Installing collected packages: ft
  Running setup.py install for ft ... done
Successfully installed ft-1.0.0

Example of running pip install .

Issues to think about:
how to do versioning? maybe use ft.version as the version in setup.py
what versions of python to support? I suggest this repo should have ci from travis -- I can make a separate PR for this one and verify builds across multiple python versions. I tested python 3.6 and 3.5. Not sure about others
more metadata to be added in setup? I am not sure about this

how to do versioning? maybe use ft.version as the version in setup.py

How do other pip packages handle this? I'm okay with adding a new python file somewhere that includes the __version__ (or include it in an existing file).

what versions of python to support? I suggest this repo should have ci from travis -- I can make a separate PR for this one and verify builds across multiple python versions.

That sounds great.

I tested python 3.6 and 3.5. Not sure about others

I'd be okay with that for now.

more metadata to be added in setup? I am not sure about this

I can take a look once this is merged.

Thanks!

maybe you can create tags now for this repo

https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi
you can take a look at this and upload the package to pypi and publish it!

Thank you for the link.
The package has been uploaded to pypi.


ARROW-3986: [C++] Write prose documentation

@wesm @fsaintjacques

Thanks. I think I've addressed your comments now.

I've pushed a couple additions here. If no objections, I may merge this soon and continue in other PRs.

I will have a look through today if possible and leave any comments to be addressed in follow up PRs


MudNumericField: Clearable with Min

Description

Fixes #3884
MudNumericField could not be cleared if Min property was set (or negative Max).
How Has This Been Tested?

New unit test
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Hi @matyasbach, and thanks for taking the time for this PR.
There has been another PR (https://github.com/MudBlazor/MudBlazor/pull/4973) for MudNumericField. Can you check if #3884 is fixed with it too? And if not, can you merge from the latest dev, so I can start reviewing it?

Closing in favor of #5077 where the bug was fixed too and test included.


Add minimal example for minting NFTs

Curious what the status is on this? I'd really like to give it a spin. Maybe an idea of what is missing so I can try to pick it up?


Node versions question

Hi,
The README doesn't specify how I may target automatically the latest LTS, how may I do that?
Thanks!

Hello @BlueskyFR
Thank you for creating this issue.
Please use below code for fetching the latest LTS version:
       - uses: actions/setup-node@v4
         with:
          node-version: 'lts/*'

Feel Free to reach out to us in case of any issues.

Thanks! Are you sure though? I think I saw another issue in which it was reported that this expression doesn't do that.

Hello @BlueskyFR,
The actions/setup-node action is designed to use the latest LTS Node.js version when 'lts/*' is specified. This is validated by the action's official test suites and source code.
If you have seen a specific issue where this was not working as expected, could you please provide more details or a link to that issue for a more accurate response?

Hello @BlueskyFR 👋 , just following up. Do you have any updates or queries related to the latest LTS Node.js version setup?

Hello @BlueskyFR,
Due to inactivity, I'm going to close this issue for now. If you have any further  questions, please feel free to reopen this issue or create a new one. Thank you :)


Aggregate values?

I am wondering if it is possible to not only see the value of the last iteration, but have numatop aggregate the values of multiple iteration?
Do you have plans of adding such a feature? Any suggestion on how to implement it in numatop?
Numatop seems to very usefull to get an idea on how well applications work on NUMA systems, but from time to time I would like to be able to get results aggregated over al longer period.

Hi,
Currently, numatop samples the performance data (RMA, LMA, CPU%, …) from the performance counters per 5s at default. So for the counting of RMA, LMA, CPU%, …, they are generated in last 5s.
Could you give me an example to let me understand well for the feature of aggregating the values of multiple iteration?
Thanks
Jin Yao
From: Jens Breitbart<EMAIL_ADDRESS>Sent: Monday, October 19, 2015 6:50 PM
To: 01org/numatop
Subject: [numatop] Aggregate values? (#16)
I am wondering if it is possible to not only see the value of the last iteration, but have numatop aggregate the values of multiple iteration?
Do you have plans of adding such a feature? Any suggestion on how to implement it in numatop?
Numatop seems to very usefull to get an idea on how well applications work on NUMA systems, but from time to time I would like to be able to get results aggregated over al longer period.
—
Reply to this email directly or view it on GitHubhttps://github.com/01org/numatop/issues/16.

Thank you for your quick response.
The use case I have in mind would be something like this:

start numatop
press a key to toggle between the current mode and an aggregate mode
in aggregate mode I would sum up all values for all applications returned from the performance counters.

That way I could e.g. get a sum of RMA for a 30 second interval but get updates every 5 seconds.

It’s a good idea! I will add this feature requirement in my development plan.
Thanks
Jin Yao
From: Jens Breitbart<EMAIL_ADDRESS>Sent: Tuesday, October 27, 2015 8:49 PM
To: 01org/numatop
Cc: Jin, Yao
Subject: Re: [numatop] Aggregate values? (#16)
Thank you for your quick response.
The use case I have in mind would be something like this:

start numatop
press a key to toggle between the current mode and an aggregate mode
in aggregate mode I would sum up all values for all applications returned from the performance counters.

That way I could e.g. get a sum of RMA for a 30 second interval but get updates every 5 seconds.
—
Reply to this email directly or view it on GitHubhttps://github.com/01org/numatop/issues/16#issuecomment-151480684.


MQTT and Mysensors Switches won't get switched when you set the state on/off via entities. <>

Hey there,
i don't know if its intentionally but i found out that you can not set the state for mysensors and mqtt switches via entities <> on and off, you have to add both kind of switches to the gui that you can test them manually.
Best regards,
DuckY

Setting a state in the developer tools only changes the internal state in home assistant. To change the real device state you have to use the corresponding service. Does this explain your experience?

I used the corresponding services instead, but its a bit tricky when you are used to trigger internal automation this way. Just wanted to know if its on "purpose" as a lot ppl working with entity states.

I'm closing this since I think it's working as intended.


DRaFT paper

It looks like DRaFT (DIRECTLY FINE-TUNING DIFFUSION MODELS ON DIFFERENTIABLE REWARDS) has a similar idea, and I'm wondering what're the main differences between your approaches. Thanks!

In terms of code the difference is minor.
i) We do randomized truncated backprop however they do just truncated backprop.
ii) They sample many noise samples, however we sample a single noise sample.


local run mode doesn't catch errors

Needs to be fixed for https://github.com/BIDS-Apps/MAGeTbrain/issues/3

Fixed by #151


RSDK-1823 Add new functionality to facilitate user-specific tests in our scene infrastructure

I ended up testing this locally against the latest RDK with the Single Benchmark instructions to verify the tests themselves didn't break.
I do have some terminal output that indicates its using the correct frame for planning purposes:
1.6783252144513001e+09	info	omplbindings	motionplan/motionPlanner.go:191	planning motion for frame end_effector. Goal: reference_frame:"world"  pose:{x:-600  y:-400  z:60.000000000000014  o_x:2.220446049250313e-16  o_y:-1  o_z:2.220446049250313e-16} Starting seed map map[arm:[{0} {0} {0} {0} {0} {0}] end_effector:[{0.5128} {-1.9168} {-2.2394} {-1.8598} {1.141} {-0.9511}]], startPose x:-817.2  y:-322.9  z:62.79999999999998  o_x:1.5700924586837752e-16  o_y:-1  o_z:2.220446049250313e-16  theta:89.99999999999999, worldstate: obstacles:{reference_frame:"world"  geometries:{center:{x:350  z:500  o_z:1}  box:{dims_mm:{x:80  y:1000  z:1000}}  label:"unnamedWorldStateGeometry_1"}  geometries:{center:{x:350  z:-500  o_z:1}  box:{dims_mm:{x:700  y:1000  z:1000}}  label:"unnamedWorldStateGeometry_2"}  geometries:{center:{x:-450  z:-266  o_z:1}  box:{dims_mm:{x:900  y:2000  z:100}}  label:"unnamedWorldStateGeometry_3"}}
Interesting labels for the geometry there; I will probably go through the scenes and fix all those so we are actually labeling the geometries tomorrow.

Going to look at the actual code in a minute but right off the bat its odd to me that your terminal output still references omplbindings since references to that shoud have been scrubbed.  Makes me think something is out of date or we missed a reference?

Going to look at the actual code in a minute but right off the bat its odd to me that your terminal output still references omplbindings since references to that shoud have been scrubbed. Makes me think something is out of date or we missed a reference?

The string being passed to NewLogger wasn't ever changed from omplbindings. I changed that just now and will show up in the next update.


array property doesn't contain initial & value on the property name, but only on each array item

I have initialized my form based on initial data
user: {     subscribed: [ { kk:'aa' }, {kk:'bb'} ] }
I am going to update this property using customized components, so my fields setting was:
fields: {    user.subscribed }
when looking in redux-dev i see the info as:
state: {    ...    form: {       myform: {           user: {               subscribed: [{ kk:'aa' }, {kk:'bb'}]           }       }    }    ... }
i expect to see initial & value under subscribed...
My problem is that when i call the onchange on the subscribed field , it ads a value property ...
What am i missing ?

@erikras , i would love to get your feedback on this? (also i would love to contribute and fix it, but not sure i have all the info yet)

The reason for this not to work is since we are using redux-form 3.1.7 in the ultimate redux template

Thanks for reporting back your discovery. :+1:


Get the total count of system users from the api endpoint /users/stats

Summary
Passes the number of total users to mattermost-webapp.
Ticket Link
https://github.com/mattermost/mattermost-server/issues/6521
Checklist
Test Information

You've got some style issues here that is preventing the PR from being built
><EMAIL_ADDRESS>check /home/ubuntu/jenkins/workspace/mmrdx/mattermost-redux-pr/src/github.com/mattermost/mattermost-redux
> eslint --ignore-path .gitignore --ignore-pattern node_modules --quiet .

/home/ubuntu/jenkins/workspace/mmrdx/mattermost-redux-pr/src/github.com/mattermost/mattermost-redux/src/reducers/entities/users.js
  401:1  error  Trailing spaces not allowed  no-trailing-spaces

/home/ubuntu/jenkins/workspace/mmrdx/mattermost-redux-pr/src/github.com/mattermost/mattermost-redux/src/store/initial_state.js
  337:29  error  Trailing spaces not allowed  no-trailing-spaces

✖ 2 problems (2 errors, 0 warnings)
  2 errors, 0 warnings potentially fixable with the `--fix` option.

hey, @hmhealey! I fixed the style issues, please let me know if there is anything else!

Waiting on https://github.com/mattermost/mattermost-server/pull/8847 to be merged after 5.0 is branched

hello @lisakycho can you please rebase and fix the conflict? thanks!

@lisakycho The server PR for this has been merged, so if you rebase this, we can get it merged as well

is this still a valid PR? if so it needs rebase

@enahum, @hmhealey sorry for the late reply, this has been rebased!


Update docker hub from omni-nightly to latest nightly

Mealie is now stable. Latest docker hub is just nightly

Thanks very much! The switch from images is seamless, the underlying systems are exactly the same?

Previous version was v1.0.0-RC1.1. New version is v1.0.0. I was able to migrate seamlessly using amd64 images.
Does your updater create a new image automatically from docker hub?

Well I'll push it now! Automatic updates ara every Saturdays. What actually triggers the build is the change of version in config.yaml


Custom pattern for email in Bootstrap Form Validator is not working

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
The default behavior of email validation is just checking any number of characters then an @ symbol and any character that's it.
I want to check for a correct validation so I tried to put a pattern tag in email input with following pattern.
pattern="[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$" But the pattern is working (still default behavior) and Browser throwing error as follow:
Pattern attribute value [a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$ is not a valid regular expression: Uncaught SyntaxError: Invalid regular expression: /[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$/v: Invalid character in character class
I tried to remove novalidate from form tag to bypass the Bootstrap's Javascript. But same error.
As soon as I hit the @ key browser throwing same error.
Could anyone check where I am wrong?
Suggestion: Please upgrade https://getbootstrap.com/docs/5.3/forms/validation/ page to provide in depth detail for form validator. I also wanted to use my custom javascript code along with Bootstrap's form validator but It is not working.
Similar Issue here: https://stackoverflow.com/questions/69894643/custom-validation-with-bootstrap-v5
Reduced test cases
Live Demo on Codepen
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.3.0

Pattern attribute value [a-z0-9.%+-]+@[a-z0-9.-]+.[a-z]{2,}$ is not a valid regular expression: Uncaught SyntaxError: Invalid regular expression: /[a-z0-9.%+-]+@[a-z0-9.-]+.[a-z]{2,}$/v: Invalid character in character class

This error doesn't come from Bootstrap.
If you go on Chrome to https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/pattern#try_it, change the pattern to pattern="[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$", you'll see the same error in the console.


Request support for Integra (Onkyo) DRX-5

Kindly requesting added support for Integra (Onkyo) DRX-5 receiver. Homebridge-Onkyo already connects to my receiver with the default receiver type. Adding support would line up options to this requested receiver.
Thanks.
Mike A.

My PR https://github.com/ToddGreenfield/homebridge-onkyo/pull/80 includes an updated eiscp.js that I found that supports the DRX-5. You could test the PR or wait until it's merged.

Since this issue is stale and should/could have been resolved with an update, I'm closing this. If it's still a problem, reopen (or file a issue) and give updated details describing the problem and what version of the plug-in you're currently using.


Ubuntu Chiseled Dotnet

Summary of your issue
I am trying to compile OpenCV and OpenCVSharp like the examples found here https://github.com/shimat/opencvsharp/tree/master/docker and at the very end copy it from builder to https://hub.docker.com/r/ubuntu/dotnet-deps image, so I can run my self-contained application in a non-root mode without any system/tooling unnecessary garbage.
Environment
Image ubuntu/dotnet-deps:7.0_edge with my application compiled as self-contained for a specific architecture (amd64/arm64).
Example code:
No code
Output:
The type initializer for 'OpenCvSharp.Internal.NativeMethods' threw an exception.
System.TypeInitializationException: The type initializer for 'OpenCvSharp.Internal.NativeMethods' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'OpenCvSharpExtern' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
/app/OpenCvSharpExtern.so: cannot open shared object file: No such file or directory
libopencv_stitching.so.407: cannot open shared object file: No such file or directory
libOpenCvSharpExtern.so: cannot open shared object file: No such file or directory
/app/OpenCvSharpExtern: cannot open shared object file: No such file or directory
/app/libOpenCvSharpExtern: cannot open shared object file: No such file or directory

What did you intend to be?
I am now debugging with LD_DEBUG=libs to figure out where to put the files so the self-contained application finds the libs but I was wondering if you didn't already have a dockerfile for this prepared?

cc @shimat

sorted by placing required libs in the right folders


switching to full screen

an ability to show the carousel in the fullscreen
fullScreen option passed to the Carousel component with the following values:

null (default) - no fullscreen
on click - switch to fullscreen on click and switch back on next click
on double click - switch to fullscreen on double-click and switch back on next double-click
always - always full screen, it can be used to control fullscreen with a custom way

IssueHunt Summary

Backers (Total: $11.00)

 piotr-s-brainhub ($11.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

@piotr-s-brainhub I have a question regarding to the behavior of the carousel after going fullscreen.
How should we handle the width and height of the content? Do we keep them at the same size as what they're displaying originally, or should we make them stretch to fix the screen?
Below is the screenshot of the carousel going fullscreen and preserve the content size:

@huytd

The size should be increased to fit the entire screen but keeping the image proportions (we have to resize in both directions with the same scale)
It should work at least for the latest versions of (only desktop):

Mac: Chrome, Firefox, and Safari
Windows: Chrome, Firefox, and Edge

Thank you so much @piotr-s-brainhub

@huytd
you're welcome

@huytd would you like to implement this feature?

Sorry. Lot’s of stuff is going on from my end and I didn’t have time to
follow this yet.
On Mon, Jun 15, 2020 at 4:12 AM piotr-s-brainhub<EMAIL_ADDRESS>wrote:

@huytd https://github.com/huytd would you like to implement this
feature?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brainhubeu/react-carousel/issues/322#issuecomment-644064801,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEV4N3SFJ44C4ZPTZEFPGTRWX62LANCNFSM4LFZBR6Q
.

@huytd
OK, so I hope somebody else will implement this.
Thanks for your contribution (a question thanks to which we have more details).

Hi @piotr-s-brainhub, Can you guide me a bit? So, I can contribute to it.

@Ckbhatia
I don't what guide you'd like to have.
You can read the workflow and the requirements in this issue description.

@piotr-s-brainhub Where is the directory for this? In the documentation, there's getting started guide for documents.
But, I didn't find any guide to get started with react carousel components.

@Ckbhatia
I created https://github.com/brainhubeu/react-carousel/issues/550, I invite you to like (👍) and comment it.

@Ckbhatia
Now we have to drop funding from all the features until we finish refactor so if you want to work on some issues, you can fix some bugs.
here is the list of all the funded issues, please note that some of them are already started.


ionic7-angular-sqlite-app tutorial fails on v5.7.1

Describe the bug
Updating the demo ionic7-angular-sqlite-app to v5.7.1 breaks with webpack errors and  jeep-sqlite element is not present error.
To Reproduce
git clone https://github.com/jepiqueau/blog-tutorials-apps.git
cd blog-tutorials-apps/Part-1/ionic7-angular-sqlite-app
npm install
npm install --save<EMAIL_ADDRESS>ionic serve

[ng] ./node_modules/jeep-sqlite/dist/esm/jeep-sqlite.entry.js:2926:20-37 - Warning: Module not found: Error: Can't resol
ve 'crypto' in 'ionic7-angular-sqlite-app\SQLite\Part-1\ionic7-angular-sqlite-app\node_modules\jeep-sqlite\dist\esm'
[ng]
[ng] BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
[ng] This is no longer the case. Verify if you need this module and configure a polyfill for it.
[ng]
[ng] If you want to include a polyfill, you need to:
[ng]    - add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
[ng]    - install 'crypto-browserify'
[ng] If you don't want to include a polyfill, you can use an empty module like this:
[ng]    resolve.fallback: { "crypto": false }

The app runs but fails with

initializeAppError: Error: The jeep-sqlite element is not present in the DOM! Please check the @capacitor-community/sqlite documentation for instructions regarding the web platform.

Desktop (please complete the following information):

OS: [e.g. iOS] Windows 10

Additional context
With a bit of Googling I ended up with the following changes:
package.json
    "crypto-browserify": "^3.12.0",
    "stream-browserify": "^3.0.0",
    "vm-browserify": "^1.1.2",

tsconfig.json
{
  "compilerOptions": {
    "paths":{
      "crypto":["node_modules/crypto-browserify"],
      "stream":["node_modules/stream-browserify"],
      "vm":["node_modules/vm-browserify"]
    }
  }
}

angular.json
{
  "architect": {
    "build": {
      "options": {
        "allowedCommonJsDependencies": ["crypto"],
      }
    }
  }
}

The above fixes the webpack < 5 breaking change error in compilation but still fails with

initializeAppError: Error: The jeep-sqlite element is not present in the DOM!

So I am a bit stuck.

@ChrisHSandN Thanks for reporting. jeep-sqlite does not use 'crypto' module in fact the latest release of sql.js did, so the build of jeep-sqlite esm/jeep-sqlite-entry.js referred to crypto. To avoid the error message in angular create a webpack.config.js file including
module.exports = {
  resolve: {
    fallback: {
      crypto: false
      // Add more fallbacks if needed
    }
  }
};

@ChrisHSandN Sorry this does not work with Angular13.3.2 so i look at it

@jepiqueau thanks for your reply,
I am using Angular 16.2.12 (as per the tutorial package.json setup).

Digging into this further, I suspect the issue may be with this function:
https://github.com/capacitor-community/sqlite/blob/48e0c217a5ea8cfdafccc068460adc4a324e2e9a/src/web.ts#L47
Although it is async it has an internal then() so will resolve immediately (before anything has actually been set up).
I would propose something like:
async initWebStore(): Promise<void> {
  await customElements.whenDefined('jeep-sqlite');

  this.jeepSqliteElement = document.querySelector('jeep-sqlite');
    // ... etc.

Otherwise await initWebStore() doesn't actually wait for it to be ready and then checkConnectionsConsistency gets called before the element is set up.

@ChrisHSandN You right. Will be fixed in the next release

@ChrisHSandN The tutorial has also been updated. thanks for your contribution


Update for vulnerability fixes please

Hey all,
Node v6.1.0, v5.11.1, v4.4.4, v0.12.14, and v0.10.45 were released four days ago to fix vulnerabilities in OpenSSL. Could you release these versions please?
It might be worth you scheduling some time when the vulnerability announcements are made a few days ahead of the release in anticipation that important fixes will be released, in order to reduce the time it takes for end users to patch their systems. Particularly if a critical bug is fixed affecting Node, it could be very problematic having a week of exposure.
In any case, still really appreciate the work you all do - makes my life a hell of a lot easier. ❤

These are currently building. Unfortunately we can't really make them much faster for a few reasons. Basically, we can't make the distribution packages until the official sources are released, and building those takes some time. Then, after those exist, it takes additional time to make the Docker images. So in a situation like last week when there were basically five simultaneous security releases, things can get backed up. We try to do the current LTS release first, then "current", then the rest so that the highest priority things get to end users the fastest.

Looks like this is done now :)


Fix ajax calls (and other urls) to allow for a custom base URI

Currently there are lots of hard coded absolute URI's throughout the code such as "/explore/..."
It would be nice if those modules included the config/environment.js and made use of the baseURL config option so that the UI can be used in more varied environments.

Jira ticket # REX-83

There's two things to consider.
One is the baseURL variable in config/environment.js. This controls where Ember expects static files to live (the CSS and .js files).
The other one is the prefix for the API (for the /explore, /control and /riak endpoints). Is it safe to assume that we can just use the same setting for both of them?

Yes, the baseURL should be the root for all static assets, and also the starting path for any of the other API routes (/explore, /control, /riak, etc).

Ok, fixed in the most recent commits. The Explorer service (in services/explorer.js), the Store adapter (in adapters/explorer-resource.js) and the handful of hardcoded URLs (which will be cleaned up in due course) all use the baseURL variable from config/environment.js


Can we decrease the size of start?

I need smaller size of start, is it possible to do that?

Sorry, I got the answer.
:star-size="20"


Swift 3 compatibility

Hey, I'd love to see this lib available in Swift 3 so I can implement it in my project.
Thanks 😄

Please use 2.0 version.


add pcm solvent models

added PCM family solvent models including C-PCM, COSMO, IEF-PCM, SS(V)PE
added their analytical gradients

@sunqm can you confirm this is a bug? We are supposed to return self, right?
https://github.com/pyscf/pyscf/blob/master/pyscf/soscf/newton_ah.py#L708

@sunqm can you confirm this is a bug? We are supposed to return self, right? https://github.com/pyscf/pyscf/blob/master/pyscf/soscf/newton_ah.py#L708

Yes. Your change fixes the bug.


Feature Request: Support Download Autogenerated YouTube Subtitles, thanks

version: yt-dlp-gui 2023.03.21
When downloading a youtube video with no subtitles except the autogenerated subtitle.
The GUI Subtitle Control was hided and I cannot download the autogenerated YouTube subtitle.
for example: https://www.youtube.com/watch?v=gk1GK_hWuGE
Although I can download the autogenerated YouTube subtitle using config.txt in yt-dlp-gui.
--write-subs --write-auto-subs -o "%(title)s.%(ext)s" -o "subtitle:%(title)s.%(ext)s"
I still wish you could add an option in the Subtitle Control to download the autogenerated YouTube subtitle.
thanks a lot.

Thank you for using my GUI.
In fact, my GUI has never included automatic subtitles. In the information obtained from yt-dlp, automatic subtitles and normal subtitles are in different sections, so even if the control panel is not hidden, automatic subtitles cannot be downloaded. This is mainly because my GUI has never fetched this data.
With the current version, I think it is more convenient to set up several commonly used configuration files for switching.
Regarding automatic subtitles, it was also mentioned in #72, and I provided a more detailed explanation there. Currently, there are only preliminary ideas for implementing this feature, and I am not sure when it can be implemented. Thank you for your understanding.


Cannot read properties of undefined (reading 'element')

TypeError: Cannot read properties of undefined (reading 'element')
at b.element in src/vs/base/browser/ui/list/listView.ts:780:28
at <anonymous> in src/vs/base/browser/ui/list/listWidget.ts:244:98
at Array.map (<anonymous>)
at b.splice in src/vs/base/browser/ui/list/listWidget.ts:244:50
at <anonymous> in src/vs/base/browser/ui/list/splice.ts:17:35
at Array.forEach (<anonymous>)
at t.splice in src/vs/base/browser/ui/list/splice.ts:17:20
at <anonymous> in src/vs/base/browser/ui/list/listWidget.ts:1550:57
at fn in src/vs/base/common/event.ts:1576:13
at X.splice in src/vs/base/browser/ui/list/listWidget.ts:1550:22
at X.splice in src/vs/base/browser/ui/tree/abstractTree.ts:1901:9
at g.s in src/vs/base/browser/ui/tree/indexTreeModel.ts:306:14
at g.splice in src/vs/base/browser/ui/tree/indexTreeModel.ts:157:9
at D.l in src/vs/base/browser/ui/tree/objectTreeModel.ts:122:14
at D.setChildren in src/vs/base/browser/ui/tree/objectTreeModel.ts:71:8
at w.setChildren in src/vs/base/browser/ui/tree/objectTree.ts:56:14
at re.I in src/vs/base/browser/ui/tree/asyncDataTree.ts:1024:13
at re.B in src/vs/base/browser/ui/tree/asyncDataTree.ts:789:8
at async re.z in src/vs/base/browser/ui/tree/asyncDataTree.ts:549:3
at async re.setInput in src/vs/base/browser/ui/tree/asyncDataTree.ts:522:3
at async W.a in src/vs/workbench/contrib/debug/browser/variablesView.ts:91:5

Go to Errors Site

Duplicate


Propietary license: Is the downloadable linux (.deb) version corresponding with this code?

Hi,
Thanks for this amazing project.
I'm confused with the license used here. I've downloaded the last .deb file (ferdi_5.5.0_amd64.deb), and when I try to install it, the Ubuntu GUI installer says "License: Proprietary".
I would like to avoid building the full repo, but I don't get why the license of the compiled file is proprietary.   Could you clarify this please?
Thanks

Ferdi is Open Source, if you download and unpack the .deb file, you can see that it is licensed as Apache-2.0.
I have the problem that Ubuntu does not recognise the licences with other software as well. Seems to be a bug: https://bugs.launchpad.net/snap-store-desktop/+bug/1878924
So no need to build the full repo.

Closing since seems to be bug of snap store. License is specified as Apache-2.0 in package.json


Do not deprecate wrangler's proxy feature, e.g. wrangler pages dev -- vite or keep at least the injection part with a new api such as wrangler inject -- vite

Edit: I edited the issue title since this thread has been evolved about how to inject CF env vars into a hot reloading dev server, the actual issue is further down: https://github.com/cloudflare/workers-sdk/issues/5315#issuecomment-2012389845
Which Cloudflare product(s) does this pertain to?
Pages
What version(s) of the tool(s) are you using?
3.35.0
What version of Node are you using?
v20.11.1
What operating system and version are you using?
Ubuntu 22.04.2 LTS
Describe the Bug
Observed behavior
When the app redirects wrangler pages dev does the redirect but the URL in the browser's URL bar doesn't change (or redirect's header lacks the redirect status and new URL and the response header lacks a location header.
This is a big problem because it breaks relative links on redirected pages and doesn't reflect  production.
Expected behavior
A proper redirect with URL change and proper headers
Steps to reproduce
git clone https://github.com/newsve/wrangler-no-redirect.git
npm i
npm run dev

In your browser go first to localhost:5713 which is the og SvelteKit/Vite server without wrangler, you see a redirect happng to localhost:5713/some-random-page.  Now try the same with localhost:8788 which is via wrangler, still redirects but the URL in the URL bar does not change.
Also check and compare the headers (left: 5713, right 8788), note that the 8788 one lacks a response location header:

Please provide a link to a minimal reproduction
git clone https://github.com/newsve/wrangler-no-redirect.git
Please provide any relevant error logs
No response

Thanks for the report. This can be fixed by building assets to a directory and pointing Wrangler at that (wrangler pages dev <directory>), rather than using the proxy feature (wrangler pages dev -- <command>). This proxy feature will be deprecated shortly because of incompatibilities like you flag in this issue: #5317.

Thanks for your prompt answer.
When I develop I usually don't have a build yet which wrangler pages dev could consume. And, I assumed wrangler pages dev is for  developing, so running dev envs with HMR and live reload, etc., it is not meant for testing static production builds without hot realod/HMR. Please correct me if I am wrong.
Most modern web frameworks are based on Vite and when I look into, e.g. SvelteKit's output folder .svelte-kit I don't see any cloudflare/ folder when in developing mode (vite dev' or just 'vite'). Only when I do a build with 'vite build, then I see that folder. But actually I never do latter because CF does this automatically when pushing to GH. So, not sure how the dev workflow would be then.
So, maybe I do miss something and you can hint me with an example wrangler command targeting a Vite framework such as SvelteKit how this should work when developing not. Thanks!

But will wrangler pages dev still inject Cloudflare binds, e.g. to services like KV, or the props on request.cf, so the framework can consume those? This is somewhat the key USP of wrangler.

Yes, it will.

Just an idea:
Right now, I use only the output of vite's dev server on 5173 despite wrangler started and proxied latter. And it is great because it has already all injected binds without the need to use wrangler's proxied version on 8788.
A dev doesn't need more. So if there is way to get just the binds injected into vite dev without actually wrangler proxying vite would be already a huge step (because something like vite build --watch isn't as nice as vite dev for development).

hi @newsve, if you use the latest cloudflare adapter for sveltekit it will allow you to access all the bindings from within sveltekit's dev server. you can scaffold a new project using create-cloudflare to test it out and check out https://developers.cloudflare.com/pages/framework-guides/deploy-a-svelte-site/#sveltekit-cloudflare-configuration - the docs don't mention it yet (WIP) but you can configure the bindings via wrangler.toml. Again, check out a clean create-cloudflare project where all of this is preconfigured already.

Thanks, just skimmed through a create-cloudflare installation, and wow,l super impressive! All the supported framework in one place, amazing!
One question though: I can't use the locally emulated Cloudflare services anymore like with wrangler in dev mode (wrangler doesn't run with npm run dev, just with build and preview), so I would need to bind my local dev server with an actual Cloudflare service in the cloud and have there always min. two of each kind (one for dev and one for production).
Did I get it right?

Did I get it right?

not quite, with the create-cloudflare integration we start a wrangler/miniflare process behind the scenes and integrate it into vite. So you can access a local D1 database, or KV store from your app while it's running via vite dev

Incredible! Is vite then somehow patched? Because in package.json, I only find "dev": "vite dev", and in vite.config.js I find no invocation of wrangler/miniflare either:
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vitest/config';

export default defineConfig({
        plugins: [sveltekit()],
        test: {
                include: ['src/**/*.{test,spec}.{js,ts}']
        }
});

tl;dr:

Deprecating Wrangler's proxy functionality risks degrading developer experience by losing key development features like live reload and HMR, repro steps for Svelte below but this issue is with every framework, Svelte acts as an example her
This change may push developers towards other platforms due to reduced testing convenience; this is critical because the workers-sdk acts as the gateway and catalyst for utilizing all other Cloudflare services
Suggestion: Allow Cloudflare feature injection in npm run dev without full proxy use, to retain essential development tools.

Hey Cloudflare Team,
Wanted to flag again a potential issue with deprecating Wrangler's Pages Dev Proxy functionality. Please follow these steps setting up a Svelte project with your new create-cloudflare CLI (which is again highly impressive!):
npm create cloudflare@latest // Chose Create aoo/Website o. app/Svelte/Typescript

Now. add src/routes/+page.server.ts:
import type { PageServerLoad } from './$types'

export const load: PageServerLoad = async ({ request }) => {
  console.log(request.cf)
}

Try npm run dev and check the server logs, access the new app in your browser, console.log prints nothing.
Try npm run preview and chack the server logs, and yes, request.cf is set! but you don't get:

Must-have: Rebuild on file changed (somehow doesn't work)
Must-have: Live-reload in the browser (this wouldn't work if even 1 did work)
Nice-to-have: HMR in the browser (this wouldn't work if even 1 did work)

2 and 3 rely on Vite's unmatched dev server which is key to Vite's success and which you can't use with npm run preview
The current developer experience (DX) with Cloudflare services takes a hit due to the necessity of restarting the server or refreshing the browser on every file change. This becomes especially problematic for those relying on Cloudflare-specific features, such as request.cf, to dynamically adjust behavior based on the node's location. The cumbersome workaround of using npm run preview isn't a viable solution for a smooth and efficient development workflow.
I'm concerned this move might push developers towards alternative solutions or other providers, particularly when the ease of integration and testing of CF services is compromised. The deprecation of wrangler pages dev -- could lead to missed opportunities in leveraging Cloudflare to its full potential.
Would it be possible to explore a solution that allows injecting Cloudflare's features into the development environment, specifically through npm run dev, without fully acting as a proxy? Currently, I bypass the proxy's verbosity on 8788 and limitations by directly using Vite's output on 5173. So, we would need just the injecting part of wrangler pages dev ++ vite.

Strongly agree with @newsve's points above... I was shocked to learn that wrangler is deprecating the proxy feature without a viable replacement (vite build --watch will not meet our needs).
To be clear: hot-reload support is not a "nice-to-have" for us, it is essential to our workflow: we literally cannot develop without it. Our application has a lot of intricate client state (we're building games) and forcing hard-reloads fundamentally breaks our team's workflow. cc: @admah

fwiw, I changed issue title/subject since the actual issue evolved to env var injection to hot reloading dev servers such as vite dev (instead of starting a new thread), hope that's ok and look forward to CF's thoughts and ideas on how to tackle this issue

And even if you don't need HMR, the live-reload feature does not work, see #5351.

Try to upgrade to the latest of wrangler and then need to downgrade because of this, at least provide a way to make it work with current tooling, AFAIK it's impossible to do it with Vite to support HMR, bundleless, etc. Or you guys want me to move to rollup and rollup --watch

As user perpective, I think honox API is the BOAT here, they provide a vite plugin and I don't need to do anything
Below is my command, is pretty long but runable
pnpm dlx kill-port-process 8788 && wrangler pages dev --compatibility-date=2024-04-01 --compatibility-flag nodejs_compat --proxy 5173 --log-level log -- vite --host <IP_ADDRESS> -l silent

// ps: yes I need to kill-port-process 8788 because wrangler randomly not teardown process if it's crash or something
honox is pretty good at DX, however they generate a _worker.js as output, which is I understand will cost 1 request for each static file.

After chasing this problem for 2 days. I realised there is a way to integrate miniflare without using wrangles pages dev at all.
the wrangler package provides a function called getPlatformProxy that will give you access to everything.
The svelte adapter handles it in the following manner.
https://github.com/sveltejs/kit/blob/bbab296f6fcc05af6b999182798bcdedabbaa4c9/packages/adapter-cloudflare/index.js#L130

+1
I'm trying to find a solution to be able to run a dev server for my Astro + Pages Function GPT Chat application without -- <command>. Like mentioned by others here, it's important to be able to use live reloading when making changes in a dev environment without have to rebuild and restart the dev server every time.
I wrote a discussion post on this with more details about my workflow and project: How do I start an Astro + Pages Function dev server if --  is being deprecated?

@jonaswre Could you elaborate on this? I'm a new programmer and am struggling to understand how to implement this solution for my Astro project.

After chasing this problem for 2 days. I realised there is a way to integrate miniflare without using wrangles pages dev at all.
the wrangler package provides a function called getPlatformProxy that will give you access to everything.
The svelte adapter handles it in the following manner.
https://github.com/sveltejs/kit/blob/bbab296f6fcc05af6b999182798bcdedabbaa4c9/packages/adapter-cloudflare/index.js#L130

@AVGVSTVS96 seems like astro has the same concept like sveltekit. But from the doc it seems like its not enabled by default.
https://docs.astro.build/en/guides/integrations-guide/cloudflare/#platformproxy
This should help

@jonaswre Thanks for looking into it!

I realised there is a way to integrate miniflare without using wrangles pages dev at all.
the wrangler package provides a function called getPlatformProxy that will give you access to everything
The svelte adapter handles it in the following manner.

Please check again my mini example which indeed uses the cloudflare-adapter in  https://github.com/cloudflare/workers-sdk/issues/5315#issuecomment-2012389845
But while using the cloudflare-adpater it still doesn't exposes anything in dev mode.

"preview": "npm run build && wrangler pages dev .svelte-kit/cloudflare",

This is a way to have a look at something that closely resembles how its running in prod.

npm run preview is amazing but devs need dev mode for a close feedback loop with all the thing which preview lacks: rebuild on file change, live reload and/or HMR in the browser after rebuild and all in few ms. preview doesn't give us any of that.
How do you want to develop against all the services such as D1, KV, DO, etc.? Using native binds doesn't work in dev mode and preview is way too clunky to do anything more than a hello world or do you want to manually rebuiild, wait and refresh your browser on any little change? So you go back to use REST calls with API tokens in env vars just like before. But then why do we need wrangler in the first place (except for managing the cloud resources in a dashboard manner once or twice a week) ?

Thats the Point.
With the Platform Proxy you should just be able to use the normal dev server from your framework. No need for wrangler dev.
In sveltekit I can just use "vite dev" as usual the platform proxy injects everything it should.
Have you enabled the platform proxy as seen in the like I provided?
If you need further help please provide your Astro config where you configure the adapter.
One more thing to notice. You need to use .dev.vars instead/in combination with your .env file. Miniflare will use envs from .dev.vars instead of .enc.

I am having the same problem.  I understand the reasoning behind wanting to switch away from this, but if a viable alternative is not available then removal is not an option.
Reading the blog and other issues, it looks like CF is working with the full stack frameworks to make it integrate nicely with them, but for plain Vite or any other unsupported tools, there is no way to do this anymore.
I think this should be added back with a disclaimer about the potential issues, but still allow its use for projects that rely on it.

@KyGuy2002
There is.
The wrangler npm package exposes a getPlatformProxy function.
You can use it in the same way that the svelte or astro adapter use it.
If you look at the source code of those adapters, you will see they don't use any specific tools for the integration that you won't be able to use in "plain" vite.
Basic concept is:
let DB = env.db
If(env == Dev) {
platform = getPlatformProxy()
DB = platform.env.db
}
DB.query(...)
The frameworm adapters inject this, in the way they think platform specifics should be handled.
For svelte in all functions that could interact with the platform you have access to a event object. That event object has a platform property which always contain the bindings from wrangler. In Prod/Preview they contain the real deal. In dev they referenced the local services.
I think the development workflow is meant to be the following:

Dev your features using your hmr development server ( access cloudflare using the getPlatformProxy)
Build
Verify your result using a better representation of the cloudflare infrastructure using "wrangler dev <build_path>"
Deploy to Preview
Deploy to Production

@jonaswre
Thanks for responding.
I'm not sure im understanding what you mean.  I am using the vanilla pages functions in the functions directory, and then my react site from src.  Don't I need vite dev to serve the react app, and wrangler proxy those requests and handle the functions ones?
Thanks.

@jonaswre If I understand correctly, I should be able to enable platformProxy for cloudflare adapter in astro config file and cloudflare should inject bindings into my dev server? Does bindings include ability to access my cloudflare function, or is this just for database stuff?
I tried this and have not been successful, no access to function in dev mode.
Do I also have to setup something else to access the cloudflare runtime? Or should this just work?
Here's a link to the branch in my repo where I tried this: https://github.com/AVGVSTVS96/astroSite/tree/cloudflareProxy

Dev your features using your hmr development server ( access cloudflare using the getPlatformProxy)

@jonaswre would you mind to make a small poc repo? Even C3 (npm create cloudflare@latest) with SvelteKit as app doesn't expose anything nor does it run wrangler dev along vite. Or just take @AVGVSTVS96 repo and add the missing parts.
Without being able to access the native, og CF bindings in a hot-reloading dev environment, how should we develop against killer products such as CF KV?

https://github.com/jonaswre/super-math-5233
If created a small example that does something useless with KV.
Steps do reproduce:

npm create cloudflare@latest
chose svelte
wrangler kv:namespace create wrangler_demo
add config to wrangler.toml
Add types to app.d.ts
Use KV in hooks
npm run dev

But I guess the "magic" is how to access the KV. Don't use process.env but event.platform.env.
src/hooks.server.ts
import type { Handle } from "@sveltejs/kit";

export const handle: Handle = async ({ event, resolve }) => {
	if(event.platform !== undefined) {
		const key = "SET_ME";
		const last_value =  await event.platform.env.wrangler_demo.get(key);
		const new_value = (last_value ?? '')+1;
		await event.platform.env.wrangler_demo.put(key, new_value);
		event.locals.current = new_value;

	}
	return await resolve(event);
}

src/app.d.ts
// See https://kit.svelte.dev/docs/types#app
// for information about these interfaces
declare global {
	namespace App {
        interface Locals {
            current: string | null;
        }
        interface Platform {
            env: {
				wrangler_demo: KVNamespace;
			};
            cf: CfProperties
            ctx: ExecutionContext
        }
    }
}

export {};

@jonaswre Is this not possible in my static Astro project?

@jonaswre If I understand correctly, I should be able to enable platformProxy for cloudflare adapter in astro config file and cloudflare should inject bindings into my dev server? Does bindings include ability to access my cloudflare function, or is this just for database stuff?
I tried this and have not been successful, no access to function in dev mode.
Do I also have to setup something else to access the cloudflare runtime? Or should this just work?
Here's a link to the branch in my repo where I tried this: https://github.com/AVGVSTVS96/astroSite/tree/cloudflareProxy

I have no experience with astro but from the documentation you should be able to.
https://docs.astro.build/en/guides/integrations-guide/cloudflare/#cloudflare-runtime
const { env } = Astro.locals.runtime;

It seems like the folloing line injects the platformProxy the same way its handled in svelte.
https://github.com/withastro/adapters/blob/38c32c9db490dbe58d813c7eed1113d4f7f8683d/packages/cloudflare/src/index.ts#L194

You can use it in the same way that the svelte or astro adapter use it.
If you look at the source code of those adapters, you will see they don't use any specific tools for the integration that you won't be able to use in "plain" vite.

If this is going to be the recommended path forward, the community really needs a spec implementation rather than piecing together what some frameworks have thrown together (not to mention that has no guarantee of being correct).

If this is going to be the recommended path forward, the community really needs a spec implementation rather than piecing together what some frameworks have thrown together (not to mention that has no guarantee of being correct).

I think it would be best for the deprecation warning to guide people to the following page: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy and then add a section that lets people know that if they use a framework they should check the adapters documentations.
If you have some very custom setup you need to put some thought into your dev mode anyway.
I think the information is all there they should just point people to the new solution. Just telling people it will no longer work creates threads like this.
And if there are a lot of people, just using vite without any other framework, they could come together an implement a vite plugin that handles it for vite.
As I said not much magic going on in the adapters.
Astro
const platformProxy = await getPlatformProxy({
		configPath: args.platformProxy.configPath ?? 'wrangler.toml',
		experimentalJsonConfig: args.platformProxy.experimentalJsonConfig ?? false,
		persist: args.platformProxy.persist ?? true,
	});

	const clientLocalsSymbol = Symbol.for('astro.locals');

	server.middlewares.use(async function middleware(req, res, next) {
		Reflect.set(req, clientLocalsSymbol, {
			runtime: {
				env: platformProxy.env,
				cf: platformProxy.cf,
				caches: platformProxy.caches,
				ctx: {
					waitUntil: (promise: Promise<any>) => platformProxy.ctx.waitUntil(promise),
					passThroughOnException: () => platformProxy.ctx.passThroughOnException(),
				},
			},
		});
		next();
	});

call platform proxy
inject in the way they handle platform specifics.

Sveltekit
const proxy = await getPlatformProxy(options.platformProxy);
	const platform = /** @type {App.Platform} */ ({
		env: proxy.env,
		context: proxy.ctx,
		caches: proxy.caches,
		cf: proxy.cf
	});

	/** @type {Record<string, any>} */
	const env = {};
	const prerender_platform = /** @type {App.Platform} */ (/** @type {unknown} */ ({ env }));

	for (const key in proxy.env) {
		Object.defineProperty(env, key, {
			get: () => {
				throw new Error(`Cannot access platform.env.${key} in a prerenderable route`);
			}
		});
	}

	return {
		platform: ({ prerender }) => {
			return prerender ? prerender_platform : platform;
		}
	};

call platform proxy
inject in the way they handle platform specifics.

Remix
 let { getPlatformProxy } = await importWrangler();
      // Do not include `dispose` in Cloudflare context
      let { dispose, ...cloudflare } = await getPlatformProxy<Env, Cf>(options);
      let context = { cloudflare };
      return () => {
        if (!viteDevServer.config.server.middlewareMode) {
          viteDevServer.middlewares.use(async (nodeReq, nodeRes, next) => {
            try {
              let build = (await viteDevServer.ssrLoadModule(
                serverBuildId
              )) as ServerBuild;

              let handler = createRequestHandler(build, "development");
              let req = fromNodeRequest(nodeReq);
              let loadContext = getLoadContext
                ? await getLoadContext({ request: req, context })
                : context;
              let res = await handler(req, loadContext);
              await toNodeRequest(res, nodeRes);
            } catch (error) {
              next(error);
            }
          });
        }
      };

call platform proxy
inject in the way they handle platform specifics.

While looking through the implementation it would probably be very easy to change the remix adapter to a standalone vite adapter.
https://github.com/remix-run/remix/blob/b3f75da44749d6d69dd613668fd346b0e6802d9c/packages/remix-dev/vite/cloudflare-proxy-plugin.ts#L34

if they use a framework they should check the adapters documentations. If you have some very custom setup you need to put some thought into your dev mode anyway.

There's a huge gap between not using a framework and "very custom setup" -- a plain Vite/Webpack/Parcel app is not a "very custom setup".
Pointing at what frameworks have cobbled together, again, is not sufficient. A spec (frameworkless, vanilla) implementation is the bare minimum needed to have a healthy migration, else, people will stick to old versions.

You are write having to look for the solution is annoying. That's why I suggested to add a reference to the docs.
But they already did a pretty nice job of hiding the details.
export let kv = process.env.kv1;
If (process.env.DEV == true) {
   const {platform} = getPlatformProxy();
   kv = platform.env.kv1
}

This is pretty great to emulate the whole cloudflare infrastructure.
You haven't seen bad dx if you didn't try to develop web services in azure.
In open source land there is always the option to develop a vite/webpack/parcel plugin.
The reason why I think plain JavaScript is custom because most people who develop web apps usually pick framework or separate server and client code. And in the regular client spa you can't access cloudflare services directly anyways.

You are right having to look for the solution is annoying. That's why I suggested to add a reference to the docs.

I, and I'd imagine all others, have read the docs. While the getPlatformProxy API is indeed loosely documented, emulating the full CloudFlare suite is an exercise entirely left up to the reader. This is not good.

This is pretty great to emulate the whole cloudflare infrastructure.
...
In open source land there is always the option to develop a vite/webpack/parcel plugin.

Neat, where's the docs showing off integrations with the full suite? How to manage the dichotomy of a dev mode that is entirely built off of custom, third-party middlewares while in prod we have rigid file system-based routing requirements and a marginally different API?

And in the regular client spa you can't access cloudflare services directly anyways.

I think you're missing the forest for the trees here. You can access these services via a worker/page function/etc., which in dev the proxy is a rather good option for, hence why we're here.

I was a bit disappointed to learn the proxy flag was being deprecated. It made building a SPA + CF Functions integrated together in 1 repo so easy.
I understand you could get something similar working with running vite build --watch and simultaneously wrangler pages dev <directory>. however, this comes with some cons:

Using vite build --watch makes it harder to debug your app code as its compiled with build settings (minified code/split into chunks)
You miss out on HMR, you need to manually refresh pages whenever you want to see updates (not having HMR after using it for years is a painful developer experience)
You can't easily use tools like React Dev Tools / Vue Dev Tools, these work best when your app is built in dev mode. (there are some custom extensions you can force these to work but the experience is not great)

I'm also familiar with various frameworks adding getPlatformProxy support. I'd prefer not to use svelte, astro, or remix, when I'm building simple app (TODO) and just stick with a SPA app + CF Functions (part of the nicety of CF Pages is simplicity).
For developers like me, I think it would be nice if Cloudflare added some examples of how to integrate
getPlatformProxy support in a basic react app with vite (no remix, astro, next.js, etc).  Even better if CF provided a npm package for this but maybe that's asking too much.
Alternatively, I also understand that @IgorMinar has been working with the Vite team on the new Environments API that looks like it may solve some of these concerns I, and other developers, have around trying to build simple SPAs on CF Pages with HMR support while running wrangler pages dev.
Similar to getPlatformProxy, I think once Vite 6 is release and the Environment API is stable, it would be great for Cloudflare to document some basic examples of how to use these to integrate CF bindings during local development + enable HMR.

💡  TIL: vite dev handles local CF/miniflare/KV for you automagically if you're using SvelteKit (and other adapters)
https://blog.cloudflare.com/blazing-fast-development-with-full-stack-frameworks-and-cloudflare/
I used the -- proxy option a 2 years ago and thought I needed it for SvelteKit now. But I don't.
I assumed npm run dev (aka vite dev) couldn't possibly be running the Wrangler KV in the background, but it is. And HMR works too.
Thought I would just comment here in case anyone else is in a similar confused state trying to run a non-SPA app locally with CF KV etc.

11ty user here, moving across from netlify dev, which allows you to define a build command in the .toml.
The cludgy workaround for now is:
@11ty/eleventy --watch && npx wrangler pages dev _site --live-reload

Then nudging wrangler.toml when the build finishes:
  eleventyConfig.on('eleventy.after', async () => {
    const now = new Date();
    fs.utimes('./wrangler.toml', now, now);
  });

It works, but I don't love it!
Was surprised that wrangler.toml didn't seem to support the build command (unless I've missed something?), especially seeing as it can be set via the UI.

I don't know why Cloudflare team decided to deprecate the -- command or proxy feature.
For whatever reasons they have done this it just put developers into very much confusion about how to run the Vite Server with Cloudflare Pages ie Wrangler.
Problems:

Now what to do when it got deprecated and difficult to understand further solutions given by others.
How to run both vite and cloudflare pages workers functions simultaneously?
We can't use vite build --watch (Not Good Solution)

My Analysis and Solution:

We want to run Vite Sever
We want to run Wrangler Dev
We need HMR

How to do it?
So as of now I am using Wrangler Version 3.99. This version of Wrangler supports --proxy.  And with Concurrently package we can run the commands simultaneously. So Lets run vite and wrangler simultaneously and use the proxy feature of wrangler.
So earlier it was:
Wrangler Version Less than < 3
"scripts": {
    "dev": "wrangler pages dev --port 8789 -- npx vite -- proxy 5174",
}

And now it is:
Wrangler Version Greater than > 3
"scripts":{
	"dev": "concurrently --kill-others-on-fail \"pnpm run dev:vite\" \"pnpm run dev:wrangler\"",
	"dev:vite": "vite",
	"dev:wrangler": "wrangler pages dev --proxy 5174 --port 8789",
}

This is just running two servers simultaneously and making things easier to understand. In earlier version of wrangler they had support for command as well as proxy as an arguments. Now they only support proxy as an argument. So using concurrently I am able to run both properly without much of difficulty to understand.
This comment is just to help others so that things can stay simple and also it is working now and I don't know if in future they remove --proxy argument. Then things will fail.


[Bug] markpoint textBorderColor not working when set label color

Version
5.4.0
Link to Minimal Reproduction
https://jsfiddle.net/stanzah/1yzfteba/13/
Steps to Reproduce
markPoint: {
      	label: {
        	color: '#fff',
                textBorderColor: '#000',
        },
},

Current Behavior
textBorderColor not working
Expected Behavior
textBorderColor working
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

Please also set the textBorderWidth to be a value greater than 0.


electron-main/main.ts: Improve structure in the massive main method.

There are probably loads of other fixes that could be made; this should be seen as a starting point and definitely something we can improve upon as we move along.
(Caveat: this is my first PR to the project. It's also one of my first TypeScript commits ever, so keep that in mind. I happened to see the TODO note the other day while skimming through the code, so I thought I'd give it a try since I'm very interested in seeing what TypeScript has to offer. Really, I don't think I'd ever have dared doing these kind of changes in an untyped language; the type checking really, really, really makes it much easier.)

Hi @perlun, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@perlun, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

I'm glad you took this opportunity to get to know TypeScript. I will reject this PR though for a couple of reasons:

main.ts is still a quite heavy construction site, we are adding things left and right over there and the structure will likely change soon
The PR doesn't really fix anything besides code reorg.

I suggest you take a peek at the help wanted issue list, they are all great opportunities for you to contribute something with impact in the product.

@joaomoreno - that's fine, I can understand it's not so normal for people to come right out of the blue and start refactoring things. 😉 One of the beauties of open source.
As far as your second point is concerned:

The PR doesn't really fix anything besides code reorg.

...I think that these kind of massive reoganizings are better kept isolated from other changes. (i.e. don't mix this kind of change with a lot of functional changes, because you're basically making it impossible for anyone to grasp the diff when looking at the PR).
Anyway, thanks for the suggestions - I might check in some time again if I'm out of other fun things to entice myself with. 😇

@joaomoreno - I checked in now again to see what the main.ts file looks like and it still is a bit messy and has this comment in it, which started all of this:

// TODO@Joao wow this is huge, clean up!

I'd gladly help with this, but I don't feel like spending time on it only to get rejected again. 😛 We should either remove that comment or start doing something about it.
Would you be willing to accept a PR that does a much smaller subset of the cleanup than the PR I sent? If not, I definitely think we should go for the first route and remove that TODO comment. It's not good to have comments in the code that inspires people to make changes that will never make it into the source. It's much better that we file a GitHub issue about the cleanup then instead, and assign it to you (if that's the plan and only you have the insight to do it).
But as stated above, I am willing to give this another try if I can get a suggested starting direction.


docs(plugins) SCP idHint and removal of name and automaticNamePrefix

Fixes #2705 partially, the rest is for migration guide

remove name: true and automaticNamePrefix from splitChunks
add idHint option to splitChunks to provide a hint for the named ids

Thanks!


Get Children  of a selector  OR Get Elements  with a syntax to access all the children of an element.

Is your feature request related to a problem? Please describe.
Currently we are missing dynamic dom tree traversal method.
Describe the solution you'd like
Add Get Children that will return selectors for handlers of all the child elements of a specific selector.
Describe alternatives you've considered
Some selector syntax to directly access children with Get Elements. This could still be the way to go.

xpath //node() might help.

xpath ok


pypandoc-citeproc has been deprecated

pypandoc-citeproc has been deprecated by upstream in favor of the pandoc --citeproc option. We should switch to that for the test suite and the filters argument will probably also need to be redone or at least its documentation changed.

Builds seem to be failing not finding pandoc-citeproc https://travis-ci.org/github/bebraw/pypandoc/jobs/768316665#L432

Hi there.
This issue should be fixed now, and will be in the next release of PyPandoc (version 1.6)


spam website

1000fapvids.online
ddbca.localmeets.link
localmeets.link
Why should these domain(s) be blocked?
https://trafficlight.bitdefender.com/info/?url=http://ddbca.localmeets.link
https://www.fortiguard.com/webfilter

Thank you for this Aritra @olumolu.
I'm taking two of those domains in commit f3069eb63.
1000fapvids.online
ddbca.localmeets.link

I can't see a justification for the root localmeets.link domain here.
Closing!

This domins do dns rebinding attack and open random pop up websites you can check your self. This are phishing websites.

Here is hagazi
https://github.com/iam-py-test/my_filters_001/commit/1621f86ea71cad7c765fd9884e8bb915c0356a33
I have submitted because of the nature of the website.
Before closing request you could have asked me.

Here is hagazi
https://github.com/iam-py-test/my_filters_001/commit/1621f86ea71cad7c765fd9884e8bb915c0356a33
The root domain is used for this sketchy purposes so blocking this root does not make a issue as i have yet to find a legitimate searvice or stuff over this root domain.


Not working.

Im using paste bin, along with port 26093, im using it on my own laptop connected to different internet than pc but it is not working.

Are you using a local or remote IP? If your trying to connect to clients outside your own network you will need to port forward them, if it's on the local network however (e g. LAN) Try using a local IP, such as <IP_ADDRESS> (your own device) to make sure its a problem with your settings and not the client / server

its port forwarded, via VPN but when its set to <IP_ADDRESS> i can connect to my own pc

ive confirmed its port forwarded on canyouseeme.org

@MrD3D3 Please confirm with your VPN service that they support Port Forwarding, if your issue isn't with the program, you may want to close the issue

The reverse proxy is important please add it in your next update thanks love your hard work

Yes, the vpn says forwarded port 26093 when I connect

I feel dumb, I fixed it.


SCRUM-1520 upload_file_to_s3 default uploads to storage class STANDAR…

…D, but xml files should use GLACIER_IR

I don't know why the functional test took 14 minutes while the previous one took 3.5 minutes.  This only changes the s3 upload, and that shouldn't be part of the functional tests.

Looks good @azurebrd

Thanks @sweng66 !


PlatformView sometime not working

Steps to Reproduce
Prepare a device with Harmony OS 2.0.0, maybe some version of android have this problem too.

Using a PlatformView such as WebView.
Execute flutter run on this device
Now it is fine
Close the app then relaunch it by just click the icon on the desktop
The PlatformView would not show up.

Expected results: The PlatformView show up.
Actual results: The PlatformView would not show up.

Logs
[✓] Flutter (Channel unknown, 2.8.1, on macOS 11.6 20G165 darwin-x64, locale zh-Hans)
    • Flutter version 2.8.1 at /Users/xxxx/Workspace/flutter
    • Upstream repository unknown
    • Framework revision 77d935af4d (11 hours ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

What I found
  I have two PlatformView used in our project. One is WebView and another is implemented by ourself. It works as I want on Android and iOS. I have a test device with Harmony OS 2.0.0. Found that if the application is launched by flutter run, the platform view works fine. If not, the platform view would not work. I have
class ViewA implements PlatformView {

  private ViewB viewB;

  @Override
  public void onFlutterViewDetached() {}

  @Override
  public View getView() { return viewB; }

}

class ViewB extends FrameLayout {

  @Override
  protected void onDetachedFromWindow() {
  }

}

I found when it does not work, the ViewB::onDetachedFromWindow has been invoked but ViewA::onFlutterViewDetached has not been invoked. I did nothing so that the view should not be disposed or removed. I didn't figure out why this would behave differently between launched by flutter run or not. Specially the os is HarmonyOS but I guess some version android would have the same issue too.
Call stack of ViewB::onDetachedFromWindow attached

@haoguo
Please check this issue comment regarding Flutter's support for Harmony OS, that will give you an idea that if it's specific to Harmony OS, then the behavior is expected since Flutter doesn't support that OS.
Also, regarding your comment on some Android device may show the same behavior, in order to properly verify that, please provide a complete reproducible code sample that we can use to verify and confirm.

@darshankawar
Thanks for your help, finally solved this issue without big change.
Found that on HarmonyOS, VirtualDisplay platform view have some problems. Similar with #89146.
Change to hybrid composition can works.


Import testify/mock replaced with gomock

Closes #26
Hi, I have replaced testify/mock with gomock. EthClient is autogenerated with mockgen.
Please let me know if the tests are rewritten correctly.

Hi @vavrajosef, just wanna say thank you greatly for taking the time to open this PR. @anupsv-cb will validate the test implementations, in the meantime I've dropped some feedback and have formally assigned the issue to you :)

@epociask Merge conflicts should be resolved.

Looks like it's failing lint: https://github.com/base-org/pessimism/actions/runs/4751519710/jobs/8453021423?pr=27
You can verify lint compliance locally by running:
make lint

Apologies for not having instructions for this yet, we've only been rolling for a few weeks now!

Looks like it's failing lint: https://github.com/base-org/pessimism/actions/runs/4751519710/jobs/8453021423?pr=27
You can verify lint compliance locally by running:
make lint

Apologies for not having instructions for this yet, we've only been rolling for a few weeks now!

+1
Rest looks good

I am using windows, so I had some issues with golint. I think I fixed everything that was reported, but when someone runs it here, we will know for sure.

Review Error for anupsv-cb @ 2023-04-21 21:16:29 UTC
User failed mfa authentication, see go/mfa-help