usb_modeswitch: fixes

Motivation for this change
usb_modeswitch currently isn't working #60878
This is unfortunately quite an extensive change, mostly redoing the packaging of usb-modeswitch itself. Because of the size of the change, I'd like a review from the nixpkgs packaging experts before attempting to upstream this. I have successfully tested this with an "LG L-02C LTE".
This has the following goals:

Make DESTDIR and PREFIX work as per usual. Currently PREFIX isn't supported due to many hardcoded paths.

Remove hardcoded paths to dependencies and rely on the PATH variable instead.

Allow configuration of which init systems to use, instead of checking the state of the build machine.

Still TODO:

[ ] Fix kernel module probing

[ ] New default PREFIX changes the result of make install. Either change the readme, or restore the existing behavior.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

What do you mean by "Fix kernel module probing" ?

As I'm also suffering from broken usb-modeswitch and I have hardware to test this pull-request, I'm offering this review (per https://nixos.org/nixpkgs/manual/#reviewing-contributions-package-updates and https://nixos.org/nixpkgs/manual/#reviewing-contributions-module-updates). Note that this is a partial review as I can't follow all the changes that the patch file of brings.
Reviewed points (package update)

[x] package name fits guidelines (no change)
[x] package version fits guidelines (no change)
[x] package build on x86_64-linux
[x] executables tested on x86_64-linux
[ ] all depending packages build

Reviewed points (module update)

[x] changes are backward compatible
[x] removed options are declared with mkRemovedOptionModule (not applicable)
[x] changes that are not backward compatible are documented in release notes (not applicable)
[ ] module tests succeed on ARCHITECTURE
[x] options types are appropriate (no change)
[x] options description is set (no change)
[x] options example is provided (no change)
[ ] documentation affected by the changes is updated

Comments

I tested this module with a Huawei K3765: It works as expected (but didn't before applying this pull request)

A few seconds after plugging in the device, the system log told me that the usb modeswitching service is started.
Devices /dev/ttyUSB{0,1,2} appeared.
I used picocom and some AT-commands to query my provider's balance.

Tested after rebasing onto current nixos-unstable channel (bc94dcf500286495e3c478a9f9322debc94c4304).
For what it's worth: I expected ModemManager to pick up the device, but ModemManager didn't auto-start -- I had to start it manually with systemctl start ModemManager. This is possibly due to 3f9ac24d531090a6b49afd212b5cf2b78c825b94 .
Notifying usb-modeswitch co-maintainer: @marcweber

Tested successfully with the Logitech G920 racing wheel

Is this still WIP ?

What should be done before it can be merged ? I am using it for a few months now without issues

The patch is not applying anymore on master

I updated the patch in this commit : https://github.com/nyanloutre/nixpkgs/commit/b092c4618aedbb34837f37abc387e499cf98700e

Thank you all for your patience.

Hydra build is failing because my updated patch didn't get merged.
I made a PR: #77695

Works for me, too!


Automatic reload function, bracket removal and CSS clock documentation?

Hey together,
I am not sure but I can't find anything related to automaticly reload the time which I get using moment in a NodeJS/Express+PUG environment.
Also the final object is written within "< >" brackets which should never be happen!
Means that I ask you to implement or document, how to reload the "clock" in your documentation every 1 secound and that you please remove the "< >" omitting brackets, thanks.
My second point is, that you have a nice clock on your main page but how can this clock be displayed and reloaded automaticly, without reloading the hole page? There is also no documentation about this for the use with NodeJS/Express App + Pug ... sadly :(
Would be nice to either get help here or to see implementations for it, thanks :)

Thanks for opening this request.
Moment.js is used in a variety of environments. If you have a question about a particular environment, perhaps check Stack Overflow, or contribute to our documentation at https://github.com/moment/momentjs.com .
I'm not sure what you mean by "bracket removal". It helps me if you open each concern in a new GitHub issue.
You can see how we do the clock here.


Scroll on Salesforce1/Ipad

Hello,
I'm using it on a lightning component but isn't working when scrolling from an Ipad in Salesforce1, do you know if we have do to something more?

Hi @maximorojr,
Glad your finding use out of my lighting component!
Regarding the scrolling behavior, I'm not certain about iPad use and how mobile Safari detects scrolling behavior.
My guess is it may be something to do with either:
(a) How the renderer.js listens for scroll event, or
(b) How the renderer.js detects window and scroll position, or
(c) It may be something with how Salesforce1 mobile app does or doesn't do scrolling events like in a standard browser.
I don't readily have an iPad available to me. I only tried this out in Chrome on Windows 10. Maybe someone else can chime in with testing this out?


Virtual network issue solved by disabling Bastion

When I create the Virtual Network there is an issue and it was solved by disabling Bastion
Do I need to enable it?
And is it a must to connect with Bastion?
Best regards,
Omar Moustafa

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

ID: 0f0990fc-9834-bde3-5e06-071c75fa89a5
Version Independent ID: 96f5df37-aa95-443d-2500-37665179ce89
Content: Quickstart: Create a virtual network - Azure portal - Azure Virtual Network
Content Source: articles/virtual-network/quick-create-portal.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

I use Sandbox for educational purposes I don't have Azure btw.
BTW = By the way

Hello @KidsCanProgram, Doesnt sound like you need the Bastion service for your scenario so makes sense to disable it. the Bastion service is not a requirement but it does provide a secure & seamless way to manage remote desktop session for windows or SSH for Linux through a Secure Socket.  You can find more information on Bastion service here.
Hope this helps but dont hesitate to ping if you have any followup quesitons.
Cheers.

Yeah, I want to use Bastion but it doesn't work when I enable the Bastion in the virtual network and gives an error but, if I disabled it, there is no error.
I will send you the error.


Regenerate files to fix Android

Problem
Generated files from #7439 are out of sync. Specifically, they are missing a change where ContentLaunchCluster was renamed ContentLauncherCluster.
As I understand, the CI should have blocked #7439 if this is the case. Not sure why it didn't.
Change overview
Run zap_regen_all.py.
Testing
Regeneration only.

Problem
Generated files from #7439 are out of sync. Specifically, they are missing a change where ContentLaunchCluster was renamed ContentLauncherCluster.
As I understand, the CI should have blocked #7439 if this is the case. Not sure why it didn't.

Probably a "mid-air collision" aka tests ran against an older baseline.

Change overview
Run zap_regen_all.py.
Testing
Regeneration only.


Bug in tasks/swift_key_distribute.yml

Do NOT include any confidential information, this issue will be created on a public repo
This section is completed by the issue reporter
On which version(s) do you encounter this issue?
r12.2.8
Please provide the output to 'git describe --all' for  all deployments where you have confirmed it occurs.
12.2.8
What type of issue is this? Please tick the appropriate box.

[x] bug - existing functionality that does not work for you as documented
[ ] feature - new functionality that you would like to see added

What is the expected behavior?
Swift playbook completes.
What is actually happening?
An error occurs similar to the following nova issue:
https://bugs.launchpad.net/openstack-ansible/+bug/1531783
What were you attempting to do when you encountered this error (give as much detail as possible)?
Upgrade to 12.2.8
How can we reproduce this issue?
Run the swift playbook.
How can we verify your issue is addressed?
Playbook runs successfully.
If you are using or know of a workaround please describe the necessary steps?
I was able to add the following to tasks/swift_key_distribute.yml:
with_items: groups['swift_all'] + groups['swift_remote_all']
when: hostvars[item]['swift_pubkey'] is defined
tags:
What is your evaluation on the importance of this issue, and why?
It's important because the swift playbook will currently fail to run without the patch.
This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[ ] master
[ ] mitaka-13.1
[ ] liberty-12.2
[ ] kilo

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[ ] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[ ] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[ ] This change includes additional testing
[ ] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[ ] This change does not require a release note.

Doc Impact
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

Thanks @rpawlik!
Given that there is a workaround and this doesn't prevent deployment of a default environment, I am marking this as a prio-3. Please let me know if you feel like this should take a higher priority.


Install web-ext (used in scripts)

It looks like we forgot to add this to our devDependencies when adding the launch:firefox script.

Yeah. I forgot to push that change earlier. I added it here in #290. but it should have been a separate PR.