bring sysconfig template for RHEL7 and Fedora up-to-date for DNS

The template for RHEL7/CentOS7/Fedora was not setting DNS servers and search path in /etc/sysconfig/docker. This template is very similar to the one used on other platforms and the two could/should probably be consolidated.
Sorry, but I'm in a crunch so I just "modernized" the CentOS7/etc version as I didn't have time to dive into the spec and acceptance testing and make the proper prep for merging the two templates and testing the conditional logic. FWIW, I have tested this branch on a live VM I've been using for testing of Jenkins + Docker work and things look fine.

@nrvale0 no problem, and thanks for addressing. Will look at killing some of the duplication in the future.


update hackathon info and simon's picture

update hackathon info and simon's picture

You're consistently submitting good work @simonguozirui , good job! 👍


Worse performance on windows than Ubuntu

I'm getting around 20fps on windows but 60fps on Ubuntu when I used the mobilenet pretrained weights.
Both windows and Ubuntu use:

CUDA 10.1
pytorch 1.4

PC specs:

intel i7
8 gb ram
gtx 970m

Not sure why this is happening.

Windows is always slower when using the 'WDDM' driver because Windows takes control of the GPU.
To get optimal performance on Windows, you must use the 'TCC' driver and bypass Windows UI. This requires a Titan, Quadro or Tesla card.


Install error

Overview
Hi @roll ,
first of all: this is great idea, a great product, thank you very much 🙏🙏🙏.
When I install it, I have this error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
mkdocs-rss-plugin 0.17.0 requires Jinja2<3,>=2, but you have jinja2 3.0.2 which is incompatible.
jinja-markdown 1.200630 requires Jinja2~=2.11, but you have jinja2 3.0.2 which is incompatible.
datapackage-pipelines 2.2.6 requires python-dateutil<2.8.1, but you have python-dateutil 2.8.1 which is incompatible.

Does the only solution is to use virtualenv?
Thank you
Please preserve this line to notify @roll (lead of this repository)

I have solved using pipx  that for me is the way I prefer to install "problematic" python modules.
livemark is really a great idea

Thanks @aborruso !


Feat: Introduce bootstrap function to inject into DOM

Example usage:
import { bootstrap } from 'faster-dom';
import { createMyComponent } from './MyComponent';
import { MyComponentProps, MyComponentOtherProp } from './types';

bootstrap<[
  MyComponentProps,
  MyComponentOtherProp
]>('#root', createMyComponent, { myProp: 'foo' }, 'someOtherProp');

Internally, this will do:

Select the HTMLElement to append to with document.querySelector
Call createMyComponent({ myProp: 'foo' }, 'someOtherProp')
Append the FastDomNode to the HTMLElement

Reference: #12

I defined the type as
function bootstrap<F extends any[]>(
  selector: string,
  factoryFn: (args?: F) => FastDomNode,
  ...factoryArgs: F
): void

In cases where the factory takes multiple arguments, I was having some issues creating the type definition for this. I opt'd for having the user pass a generic type to bootstrap which would be an array containing each individual type definition for the arguments.
For example, with the definition above:

function createMyComponent(foo: string, bar: number, xyz: SomeInterface) => FastDomNode

bootstrap<[string, number, SomeInterface]>('#root', createMyComponent, 'foo', 123, { my: 'interface' });

@PxyUp  If you have any suggestions on how to define this better, I'm all up for it.

@baruchvlz I like it!

Merge it @baruchvlz


Call to a member function count() on array after update from 3.1.54 to 3.2.3

I have just update my crud package from 3.1.54 to 3.2.3, before update everything works perfectly but now i am getting "Call to a member function count() on array" error in admin listing.
when i check on the framework file the issue in create in below code:
    <?php if($crud->filters->count()): ?>
      <?php echo $__env->make('crud::inc.filters_navbar', array_except(get_defined_vars(), array('__data', '__path')))->render(); ?>
    <?php endif; ?>

any help how to resolve this

Had teh exact same problem, and still don't know how I fixed it. Try php artisan clear to clean compiled templates, or delete your vendor folder and composer update again, something along those lines fixed it for me

Hi guys,
No matter how much I tried, I wasn't able to get the same error updating. If you guys figure out what command helps to clear everything, please let me know - I'd love to put it in the upgrade guide for others. Ideas:
php artisan cache:clear
php artisan dump-autoload
php artisan clear-compiled
Thanks, cheers!

you may try to change from  filters->count()): ?> to
filters)): ?>

Yes this happened to me too. Ended migrate to Laravel 5.4 ... haha

the same thing.
@AurelDragut fix helped me.

Hello guys,
Check if you have the following file:
/resources/views/vendor/backpack/crud/list.blade.php
Otherwise try running:
php artisan view:clear

and also, I got this
ErrorException in LogController.php line 8: Declaration of Backpack\LogManager\app\Http\Controllers\LogController::index() should be compatible with App\Http\Controllers\Controller::index(Illuminate\Http\Request $request)
after update.

Hey,
I got this issue and also issue related to getUri()...
You should remove resources/views/vendor/backpack/curd and base also (for getUri issue)
then re-run:
php artisan vendor:publish --provider="Backpack\CRUD\CrudServiceProvider" --tag="views"
php artisan vendor:publish --provider="Backpack\Base\BaseServiceProvider" --tag="views"
hope it will help!

For me, I had a list.blade.php in resources\views\vendor\backpack\crud, despite not having changed this manually, so I removed this and re-ran:
php artisan vendor:publish --provider="Backpack\CRUD\CrudServiceProvider" --tag="views"
to recreate it, and all was well.


Issue with LS100 and clone pro micro

Describe the bug
Using a clone Pro Micro (5v), when uploading the LS100 example sketch, the lighting channels don't work or light up (sometimes will work with rainbow swirl effect but cannot be changed in iCue). The Pro Micro is detected in iCue as an LS100 device.
When uploading any other sketch (Node Pro, Node Core, Commander Pro), everything works as expected and lighting channels can be controlled in iCue.
When uploading a Node Pro sketch but choosing "Smart Lighting Controller" as the device, the lighting channels can be controlled and the Pro Micro is detected as a LS100 device but the gamma correction from release 0.9.0 isn't applied.
I'm using a clone pro micro and reflashed the bootloader so I don't have to short the RST pins to upload any sketches.
Doesn't matter which pins were used, although I've had the sketch work once with the exact same configuration but with release 0.8.0 and board library 0.1.1. Suddenly stopped working again
edit: Planning on upload the STL for an LS100 style enclosure when everything is working
To Reproduce
Steps to reproduce the behavior:

Choose "CLP SparkFun Pro Micro 5V, 16MHz"
Choose "Smart Lighting Controller"
Upload example "LS100" sketch

Images

Current wiring and setup. Shouldn't be an issue as using the Node Pro sketch is working as expected
System (please complete the following information):

OS: Windows 10 x64 1909 & Windows 10x64 1903
Board: Clone Pro Micro 5V, 16MHz
IDE: Arduino IDE 1.8.10
Version: 0.8.0 & 0.9.0, Board Library 0.1.1 & 0.1.2
Sketch: LS100

Code changes
Tested sketch with default pins but same issue. Preferred pins are 9 & 10 for the lighting channels and pin 14 for the LS100 button.

Did you try to disable the on/off button feature?

Yup, I've tried version 0.8 before the on/off button and version 0.9 with the on/off button. I've removed the on/off code from 0.9 but it didn't make a difference.
The on/off button is working as expected because when channels do light up, the button can turn it on/off (but I can't control the lights in iCue as mentioned)
As soon as I upload the node core sketch, everything works. If I add the on/off button code to the node core sketch, everything still works.
Looking at the code, I think there's a difference between corsairLightingNodeCOREFirmware() and corsairLS100Firmware() that's causing it but I haven't been able to find it yet. I'm still studying how the protocol works.

The different firmware names are only aliases. So there is no difference in semantics.

Did you apply the gamma correction in your sketch?

Nope, I haven't touched anything else in the sketches. I'm still learning how it all works. I was just planning on seeing the differences between the node pro sketch and ls100 sketch to figure out why the ls100 one doesn't work.
Worst case is that I just use the node core sketch instead and apply the gamma correction to that

I can confirm that I have the exact same issue. Tested on both 8Mhz 3v3 Pro Micro, and a custom 16Mhz 5V 32u4 board, both of which work using the Lighting Node Pro sketch. Using the Arduino IDE 1.8.10, and also tested 0.8.0 & 0.9.0, and Board Library 0.1.1 & 0.1.2. I did not make any changes to the code, still using the default pins.
The Lighting channels don't work, and I do seem to get sometimes the rainbow swirl effect that is not controlled by iCue. The button seems to sometimes turn the leds off when there is a rainbow swirl, but not always.

Ok seems like the LS100 sketch uses too much memory. The total size of both led channels must be reduced when using an ATmega32U4. This can also be seen in the real LS100 there you can't have two channels with 135 leds, you can only have one channel with 135 and the second only with 54 leds. I will update the LS100 sketch and add a hint.

Hi
this is 3D sketch for print?

@bryan065 can you share the STL of the LS100 enclosure?

In lieu of OP's design, I am developing a snap-closed enclosure.  Once I figure out how I want to route power in, I will post the STLs here.

Heavily inspired by OP, with a few tweaks and a cover.

Grabcad Link:
https://grabcad.com/library/ls100-pro-micro-omron-3-5mm-1
Model is built around using JST XH connectors, Omron 6x6mm microswitch, and Wurth Electronik
694102303002 which is a 3.5mm power input.  3.5mm jack size allows selection of 12V (WS2815) or 5V (WS2813/2812B) LED strips.  The board and connector assembly slides in from the 'top' and then the cover locks the board in place.  Recommended superglue or liberal amounts of hot glue to secure the power input.  LS100 button is programmed as pin 18, and leg closest to USB is bent out and connected to GND.  Other two legs are meant to be clipped.  Tolerances are tight, so some post-processing may be required depending on your printer.


Update DG for lessons

closes #203

Codecov Report

Merging #282 (b59cb67) into master (ab83af8) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #282      +/-   ##
============================================
+ Coverage     69.02%   69.06%   +0.03%
- Complexity      954      956       +2
============================================
  Files           128      128
  Lines          3245     3245
  Branches        413      413
============================================
+ Hits           2240     2241       +1
  Misses          842      842
+ Partials        163      162       -1

Impacted Files
Coverage Δ

.../seedu/address/model/lesson/CalendarEntryList.java
90.27% <0.00%> (+0.69%)
:arrow_up:

Continue to review full report at Codecov.

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


Disable Pcap logging for 4GB pcap test

Motivation:
Pcap 4GB log test produces a huge amount of log which is not required and makes debugging other CI failures impossible because the browser just gives up rendering such log files.
Modification:
Disable logging by overriding the logTCP and making it NO-OP.
Result:
No more enormous logs

@normanmaurer Can you pull this on priority? Analysing CI logs is impossible now :V

Let's just do https://github.com/netty/netty/pull/14596.


More benchmarks and longer benchmarks

More benchmarks are needed (3D cases that are homogeneous in 2 of the dimensions might be easiest to setup).
Longer benchmarks are needed (more time steps, e.g.) for GPU cases, which run quickly and are thus vulnerable to small runtime differences. This can be passed into the case.py benchmark case via an argument that contains the device type, like examples/weak_scaling.

This is on my ToDo list.


feat: Handle TCU41_x04 as gateway

@xSauron back then in https://github.com/home-assistant/core/issues/122056 we ignore your gateway directly in HA. I now would like to handle that in the library correctly. For that I would need to know the roles that are applied to your gateway. Could you provide that by doing an API call via curl?

Hey, sorry for late response - sending the body from https://api.viessmann.com/iot/v1/equipment/installations regarding gateways.
"gateways": [
{
	"serial": "7633107055930236",
	"version": "504.2244.48.0",
	"firmwareUpdateFailureCounter": 0,
	"autoUpdate": false,
	"createdAt": "2023-05-23T14:33:22.586Z",
	"producedAt": "2023-05-23T14:33:22.345Z",
	"lastStatusChangedAt": "2024-10-03T03:39:16.256Z",
	"aggregatedStatus": "WorksProperly",
	"targetRealm": "DC",
	"gatewayType": "WiFi_SA0041",
	"installationId": 2459939,
	"registeredAt": "2023-12-22T16:53:44.264Z",
	"description": null,
	"otaOngoing": false,
	"devices": [
		{
			"gatewaySerial": "7633107055930236",
			"id": "TCU",
			"boilerSerial": null,
			"boilerSerialEditor": null,
			"bmuSerial": null,
			"bmuSerialEditor": null,
			"createdAt": "2023-12-22T16:48:25.363Z",
			"editedAt": "2024-10-03T03:38:42.434Z",
			"modelId": "E3_TCU41_x04",
			"status": "Online",
			"deviceType": "tcu",
			"roles": [
				"capability:zigbeeCoordinator",
				"type:E3",
				"type:gateway;TCU100"
			],
			"isBoilerSerialEditable": false
		},
		{
			"gatewaySerial": "7633107055930236",
			"id": "0",
			"boilerSerial": "7970019305582103",
			"boilerSerialEditor": "DeviceCommunication",
			"bmuSerial": null,
			"bmuSerialEditor": null,
			"createdAt": "2023-12-22T16:48:25.363Z",
			"editedAt": "2024-10-03T03:38:42.434Z",
			"modelId": "E3_Vitodens_100_BHC_0421",
			"status": "Online",
			"deviceType": "heating",
			"roles": [
				"capability:backup;0037_HBMU_VD",
				"capability:consumptionReport;electric",
				"capability:consumptionReport;thermal",
				"capability:monetization;AdvancedReport",
				"capability:productionReport;electric",
				"capability:productionReport;thermal",
				"type:E3",
				"type:boiler",
				"type:dhw;integrated",
				"type:heating;integrated",
				"type:product;Vitodens_100"
			],
			"isBoilerSerialEditable": false
		}
	]
}
]


Vivaldi does not tile (when ran as a xwayland app (default)) [Bug]:

Before you make the issue, confirm that

[X] You are running the master build from GitHub actions
[X] You have read the FAQ and the usage instructions
[X] You have searched pull requests and issues and have found none similar to your issue
[X] This problem comes from a failure in the tiling system and not a missing feature

Describe the bug
Vivaldi does not tile alongside other tiled windows. Opens Maximised on top of other tiled windows.
To reproduce

Launch a termnial or any window
Launch vivaldi
notice vivaldi does not get tiledNotice Vivaldi

Expected behavior
Vivaldi gets tiled alongside other windows
Relevant log output
journalctl --user --no-pager -e | grep -i "polonium"
Apr 03 16:31:46 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:31:46 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:31:46 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:31:46 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:31:47 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:31:47 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window steam hooked into script
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window steam added
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Adding window steam to desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"}
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Fullscreen on client steam set to true
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Untiling window steam on desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"}
Apr 03 16:31:49 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"}
Apr 03 16:31:54 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window TeamViewer hooked into script
Apr 03 16:31:54 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window TeamViewer added
Apr 03 16:31:54 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Adding window TeamViewer to desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"}
Apr 03 16:31:54 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:32:11 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:11 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:13 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:32:13 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window vivaldi-stable hooked into script
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window vivaldi-stable added
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Adding window vivaldi-stable to desktops
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window vivaldi-stable hooked into script
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window vivaldi-stable added
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Adding window vivaldi-stable to desktops
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:14 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:15 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:32:15 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:32:15 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:15 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:16 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:16 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:16 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:32:16 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:32:17 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell hooked into script
Apr 03 16:32:17 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Not tiling window org.kde.plasmashell
Apr 03 16:32:18 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:18 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:19 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window TeamViewer removed
Apr 03 16:32:19 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window TeamViewer from desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"}
Apr 03 16:32:19 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:32:20 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:20 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops
Apr 03 16:32:21 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window python3 removed
Apr 03 16:32:21 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window python3 from desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"}
Apr 03 16:32:21 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-1"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"DP-2"},{"desktop":"8d5382aa-d8b0-416b-8148-ec30b5b4dfc5","activity":"f577afb5-1dac-4cd8-932c-770f8518f05f","output":"HDMI-A-2"}
Apr 03 16:32:21 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Window org.kde.plasmashell removed
Apr 03 16:32:21 Garuda-Linux kwin_wayland[8630]: qml: Polonium DBG: Removing window org.kde.plasmashell from desktops

Screenshots and videos
No response
Additional context
No response

It appears that vivaldi sets itself to be a maximized window if it was previously maximized and then closed. The issue is that, unlike most windows that do this (discord, firefox, dolphin etc.) Vivaldi does this after it is opened and not during the opening process. This causes the maximization to be picked up as a user action and leads to Vivaldi becoming untiled.
There are a few solutions -

Disable "maximize when single window" and tile/float Vivaldi, then close it. Vivaldi shouldn't remember being maximized and should stay manipulatable by the engine.
Tile Vivaldi if it starts maximized, this can be done in a variety of ways. The untile/retile shortcut is most likely the best way, but the maximize/unmaximize shortcut can be used as well (just swap desktops quickly to rebuild the layout)
Disable remembering window state for Vivaldi, I wouldn't know how to do this but I assume it's possible somehow.

Try one of these solutions and see how it works for you. There will never be a fix to the root cause of this issue unless Vivaldi chooses to not start maximized.

Hmm no luck vivaldi just seems to ignore the untile/retile shortcut (other apps work fine with it)
I tried setting some window rules to disable initial placement of the vivaldi window but all that does is open vivaldi floating un maximised

appernetly enabling wayland support fixes the issue. you can do that by setting vivaldi://flags/#ozone-platform-hint to auto or wayland. Vivaldi now tiles with the rest of my windows

To be fair, if the app runs fine on Wayland and X11 is not officially supported, this issue might as well be resolved.

one caveat is this doesn't solve the problem 100% it still fails to tile I have manually occasionally grabbed it and tiled it by moving it to the the screen edge sometimes to kick in ill try to get a log of this

@zeroxoneafour tiling seems to have broken on Vivaldi again my previous fix of manually tiling with the mouse no longer works polonium tiles windows behind Vivaldi its as if Vivaldi does not exist for Polonium
tried to get a log but polonium for some reason is no longer outputting to the journal
journalctl --user --no-pager -e | grep -i "polonium"
doesn't show anything I have left logging enabled in the polonium settings


Decline to provide custom configurations for all but the currently active target

Bug type: Language Service
Describe the bug

Windows 10:
Latest: 1.56
C/C++ Extension Version: 1.4.0
Other extensions you installed: CMake Tools (1.7.2)

A single C codebase that has 2 CMake targets/proejcts defined for it: One using CUDA and another not using it (plain C).
The same codebase is compiled to either of these depending on which target is current/active.
CUDA-related portions are within #ifdef __CUDACC__ blocks.
Compilation succeeds on both targets, producing working executables.
But the editing experience is not adjusting properly.
Switchin back and forth between targets doesn't inform the syntax highlighting and code anlysis of a CUDA target being enabled/disabled. It always just debahves as if the projects aren't using CUDA.
There is a .cu file who's #include is under an #ifdef __CUDACC__ block, and when opening it even while the CUDA target is active, none of the CUDA-specific syntax is considered properly, so is full of errors being reported visually - even though it compiles and runs just fine.
Steps to reproduce

Start a new CUDA CMake project'
Create a code.h file with a #ifdef __CUDACC__ block declaring a __constant__ variable.
Create a cuda_code.cu file and include it into code.h under that #ifdef __CUDACC__, and add some CUDA-specific code in it.
Include code.h in main.cu (Add #include code.h).
Duplicate main.cu and rename it's file extension to just .c
Duplicate the project definition in the CMakeLists.txt file, renaming it to something else and making it a non-CUDA target/project (remove the CUDA term in the project() directive, as well as any target properties such as CUDA_SEPARABLE_COMPILATION), then change it's target executable to be main.c insteaf of main.cu.
After CMake reconfigures, select the CUDA-enabled target as the active one, and open cuda_code.cu - see how the syntax highlighting isn't working. Also open code.h and see how the #ifdef __CUDACC__ block is greyed out.

Expected behavior
The code analysis and syntax highlighting should get enabled and disabled appropriately when switchin between the CUDA vs. the non-CUDA targets.
Note: See attached animated-gif
Code sample and logs
#ifdef __CUDACC__
    #ifndef NDEBUG
        #define gpuErrchk(ans) { gpuAssert((ans), __FILE__, __LINE__); }
        inline void gpuAssert(cudaError_t code, const char *file, int line, bool abort=true) {
            if (code != cudaSuccess) {
                fprintf(stderr,"GPUassert: %s %s %d\n", cudaGetErrorString(code), file, line);
                if (abort) exit(code);
            }
        }
    #else
        #define gpuErrchk(ans) ans
    #endif
#endif

Configurations in c_cpp_properties.json
None (default)

Logs from running C/C++: Log Diagnostics from the VS Code command palette
Nothing special:

-------- Diagnostics - 5/12/2021, 7:11:28 PM
Version: 1.4.0-insiders
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "${workspaceFolder}/**"
    ],
    "defines": [
        "_DEBUG",
        "UNICODE",
        "_UNICODE"
    ],
    "windowsSdkVersion": "10.0.19041.0",
    "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe",
    "cStandard": "c17",
    "cppStandard": "c++17",
    "intelliSenseMode": "windows-msvc-x64",
    "configurationProvider": "ms-vscode.cmake-tools",
    "compilerArgs": [],
    "intelliSenseModeIsExplicit": true,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "compilerPathIsExplicit": true,
    "browse": {
        "path": [
            "${workspaceFolder}/**"
        ],
        "limitSymbolsToIncludedHeaders": true
    }
}
Custom browse configuration:
{
    "browsePath": [
        "d:/code/c/raytracerxpu"
    ],
    "standard": "c++14",
    "compilerPath": "c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang-cl.exe",
    "compilerArgs": [
        "-D_WINDOWS",
        "-Xcompiler=\" /GR /EHsc\"",
        "-Xcompiler=\"-O2 -Ob2\"",
        "-DNDEBUG",
        "--generate-code=arch=compute_52,code=[compute_52,sm_52]",
        "-Xcompiler=-MD",
        "-std=c++14"
    ]
}
Custom configurations:
[ D:\Code\C\RayTracerXPU\main.c ]
{
    "defines": [
        "WIN32",
        "_WINDOWS",
        "NDEBUG"
    ],
    "includePath": [],
    "compilerPath": "c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang-cl.exe",
    "compilerArgs": [
        "/DWIN32",
        "/D_WINDOWS",
        "/O2",
        "/Ob2",
        "/DNDEBUG",
        "-MD"
    ]
}
Translation Unit Mappings:
[ D:\Code\C\RayTracerXPU\main.c ]:
    D:\CODE\C\RAYTRACERXPU\LIB\RENDER\RAYTRACER.H
    D:\CODE\C\RAYTRACERXPU\LIB\CORE\TYPES.H
Translation Unit Configurations:
[ D:\Code\C\RayTracerXPU\main.c ]:
    Process ID: 4504
    Memory Usage: 64 MB
    Compiler Path: c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang-cl.exe
    Includes:
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\LLVM\X64\LIB\CLANG\11.0.0\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.28.29910\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.28.29910\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UCRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\WINRT
    Defines:
        WIN32
        _WINDOWS
        NDEBUG
        WIN32
        _WINDOWS
        NDEBUG
    Standard Version: c17
    IntelliSense Mode: windows-clang-x64
    Other Flags:
        --ms_compatibility
        --microsoft_version=1929
        --ms_extensions
        --clang
        --clang_version=110000
Total Memory Usage: 64 MB

------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 4161

Screenshots

Additional context
I've also tried different settings (without success) such as:
    "C_Cpp.intelliSenseEngine": "Tag Parser",
    "C_Cpp.default.intelliSenseMode": "windows-clang-x64",
    "C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools",

Setting to "Tag Parser" has the opposite effect: CUDA syntax seems to always be on, even when the non-CUDA project is active.

@andreeis Summary is: decline to provide custom configurations for all but the currently active target.

I'd actually like to use this issue to track a change to the configuration provider API to a) provide all configurations up-front (this is needed for Unification, ultimately), and b) indicate which source files are in the currently active project - so they can be preferred when searching for a header for a source file.  I do not believe that declining to provide configurations for inactive targets would be a good idea.

I do not believe that declining to provide configurations for inactive targets would be a good idea.
@Colengms I was about to say the same thing - there should probably be a way to just choose the active one out of the given set. But that's a detail of the coordination, so I removed my saying that (a 'not my problem' kind of a thing).

@Colengms Should the title be changed?


is_polygon function, initial simulation robot positioning error fixed

I added a function to check if a given field has a valid polygon as boundary.
Also, there was an issue with the initial use of the robot position when using the simulation, occurred on a new system. The changes now set initial values for the robot position in the simulation to prevent the system from crashing.

additionally i added a first re-style of the dev page. More to follow.


put CD integrations in a partial

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

put CD integrations in a partial

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


bug: Fix image proportions

Looks like adding an image via Ghost editor renders with incorrect proportions.

Closed via https://github.com/nchepanov/the-ghost-plain/pull/9


[0.10.3] RaisedButton requires double click

Since the 0.10.3 release RaisedButton now only fires onClick when you click on it a second time. Reverting to 0.10.2 fixes this.
The code is:
<RaisedButton label="Submit" primary={true} onClick={this.submit} />

this.submit is only called on the second click.

Thanks @jagregory - It looks like there was a problem with how the children were rendered. Sorry I didn't catch this - onTouchTap seemed to be working fine...not sure why onClick was affected.


Describe what do you mean Off-peak hours

Hi team,
please can you describe in more details how is determined off-peak hours for Automatic VM parch management ?
How is it evaluated on Windows and Linux OS ? You are refering VM timezone, but where is defined ?

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

ID: 61687573-f03b-85dc-54cf-e95d95efb235
Version Independent ID: 7bfd1c0f-0ecd-44da-9724-6118b950f4ff
Content: Automatic VM Guest Patching for Azure VMs - Azure Virtual Machines
Content Source: articles/virtual-machines/automatic-vm-guest-patching.md
Service: virtual-machines
Sub-service: maintenance
GitHub Login: @maulikshah23
Microsoft Alias: maulikshah

@jjindrich
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly

@maulikshah23
Can you please check and add your comments on this doc update request as applicable.

Please is there any update ?

@kjohn-msft , can you please assist in answering the questions above?

@jjindrich apologies for the delayed response. The off-peak hours are subject to a region's timezone. The hours generally rang from 10 PM to 6 AM, however these are subject to change, especially during emergency rollout.

@jjindrich , please close this comment if my above response answered your question.


acr: updating existing version to fix swagger quality issue in s360

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360 (https://msazure.visualstudio.com/Swagger KPIs/_workitems/edit/8187827)
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[x] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Can any reviewer please tell me what specific prettier check errors. I have followed the instructions and saw nothing:
C:\sdk\specs>npm run prettier -- --write C:\sdk\specs\specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json

><EMAIL_ADDRESS>prettier C:\sdk\specs
> prettier "--write" "C:\sdk\specs\specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json"

specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json 187ms

Can any reviewer please tell me what specific prettier check errors. I have followed the instructions and saw nothing:
C:\sdk\specs>npm run prettier -- --write C:\sdk\specs\specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json

><EMAIL_ADDRESS>prettier C:\sdk\specs
> prettier "--write" "C:\sdk\specs\specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json"

specification\containerregistry\resource-manager\Microsoft.ContainerRegistry\preview\2019-12-01-preview\containerregistry.json 187ms

@yugangw-msft The issue is with 2017-10-01/containerregistry.json and 2019-05-01/containerregistry.json: No new line at end of file.


Improving samples for build2022

Description
These samples have been modified for a better understanding of the XAML/WinUI concepts.

Improving TitleBar sample,
Improving and adding a new sample for Creating Multiple WIndow,
Improving ItemsRepeater sample with the DataModel code and adding Layout and DataTemplete as Resource of the ScrollViewer
Improving AnimationsInterop sample - There was an error when copy&paste the code in WinUI3, there is no App.Current in desktop, and the Compositor comes from the Window object.
Improving ContentDialog sample, the sample code for getting the XamlRoot was very fragile
Fixing bug in Mica CS code sample. There was a ; after a class definition.

Motivation and Context
I have modified several samples to help users understand the WinUI/XAML concepts better and avoid users going back and forward from docs to the WinUI Gallery.
How Has This Been Tested?
Smoke tests in the WinUI3 project.
Screenshots (if appropriate):
Types of changes

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

@gregwoo-microsoft Should we merge this or close this as stale?

The branch badly needs to be rebased and there are pretty significant merge conflicts. I don't have a strong opinion but I'm leaning towards closing as stale.

I agree. Let me check in with Gabby as she worked on this branch with Miguel.

Got confirmation from Gabby that we can close this as stale.


add supported laravel version to top of README.md

please add the supported laravel version to the readme.
tried installing on laravel 5.6.3 but composer install failed directly due to version issue.

It's in there, right above the "Installation Steps" heading
okay okay, fine... you caught me.. I cheated... I just updated it from "and newer" to "and 5.5".

thanks man ;)


chore(mlx-lm): fix print_trainable_parameters for quant models

address https://huggingface.co/mlx-community/Mixtral-8x7B-Instruct-v0.1-hf-4bit-mlx/discussions/1

@awni, I have updated the PR based on your suggestion. It is now ready for review again. Please let me know if there is anything else that needs to be updated.


Reduce tickets size as much as possible

Follow-up of: https://github.com/apereo/cas/pull/5850

This pull request breaks many of the existing unit tests, due to either NPEs with the services object being null, or invalid property references. There are still areas that reference cas.logout.remove-descendant-tickets=true. Please review.

You can see some of the test failures here: https://github.com/mmoayyed/cas/actions/runs/6942518937
Some of this I have fixed, I think. (It's always worthwhile to run the tests on your own fork, for example as I do in the link. Goes much faster and you can control what gets built or tested very easily)

I will check on the master branch.

I see some OAuth tests failing on master. I will fix them via: https://github.com/apereo/cas/pull/5861


Chore/okp4 migration

:nail_care: make this project follow okp4 guidelines

Great job. I have a few general comments that can be discussed:
* I don't see the point of putting the `node_modules` directory in git. Also, I would be inclined to delete it. @fredericvilcot

* Ideally, the programming language of the project should be `typescript` and not `javascript` to comply with OKP4's choices in this matter, and this, I know what you're going to tell me, even if there are only a few lines of code. wink @fredericvilcot

* If the distribution in the `dist` folder is done by you and not by the CI, it would be appropriate to have a CI workflow that makes sure that the distribution in conf actually matches what we expect it to be. @amimart

* I see you used the `wearerequired/lint-action` action to manage the listing of js code. Sounds interesting. For questions of homogeneity of our CI, it would be advisable to look in more detail at its adoption (and if ok, update the project [okp4/actions](https://github.com/okp4/actions) accordingly).  @amimart

Hi,

Ok about typescript : yes I should have more self respect. I'll check this out.
About committing node_modules : https://docs.github.com/en/actions/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action-to-github
I'll add some build actions to update dist and node_module folder and also synchronize the package.json version like discussed above.

Great job. I have a few general comments that can be discussed:

I don't see the point of putting the node_modules directory in git. Also, I would be inclined to delete it. @fredericvilcot
Ideally, the programming language of the project should be typescript and not javascript to comply with OKP4's choices in this matter, and this, I know what you're going to tell me, even if there are only a few lines of code. 😉 @fredericvilcot
If the distribution in the dist folder is done by you and not by the CI, it would be appropriate to have a CI workflow that makes sure that the distribution in conf actually matches what we expect it to be. @amimart
I see you used the wearerequired/lint-action action to manage the listing of js code. Sounds interesting. For questions of homogeneity of our CI, it would be advisable to look in more detail at its adoption (and if ok, update the project okp4/actions accordingly).  @amimart

@ccamel From what I see, - node_modules must be part of the package itself as there is no dependencies fetching phase when action runs. - Yes, 100% agree for the use of TS over JS, even if there a really few code (this allows above all to reference the project in TS in github)

@fredericvilcot So strange. 🤔 In my sense, when the action runs, only the code in the dist directory is needed (it's statically self sufficient). No?
By the way, how the following action runs if it has no node_modules https://github.com/actions/checkout ? 🧐

:wave:  I reviewed the PR and updated the description.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat(pivot): add support for multiple pivot types when using the same accessor

Summary
Currently, when you have multiple belongsToMany relations with a custom pivot, the accessor will have a single type. This PR ensures that multiple types are allowed. Also the $pivot property should be nullable as it is not always set during runtime.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

[x] Existing tests have been adapted and/or new tests have been added
[x] Add a CHANGELOG.md entry
[ ] Update the README.md
[x] Code style has been fixed via composer fix-style

There's a small issue with the docblocks this PR generates. If the type is already present, it is duplicated. Here is a sample from my codebase running the latest 3.2.1 of ide-helper
- * @property-read \Modules\Contacts\Infrastructure\Models\Phonable|\Modules\Contacts\Infrastructure\Models\Emailable|\Modules\Contacts\Infrastructure\Models\Mailable|null $pivot
+ * @property-read \Modules\Contacts\Infrastructure\Models\Phonable|\Modules\Contacts\Infrastructure\Models\Phonable|\Modules\Contacts\Infrastructure\Models\Emailable|\Modules\Contacts\Infrastructure\Models\Emailable|\Modules\Contacts\Infrastructure\Models\Mailable|\Modules\Contacts\Infrastructure\Models\Mailable|null $pivot


Replace the underscore since Java 11 says it may not be used as an identifier

Description
Fix to build the sources using Java 11 (as the target JVM). Otherwise the following errors show up:
$ sbt kernelApi/Compile/doc
...
[error] /Users/jacek/dev/oss/delta/kernel/kernel-api/src/main/java/io/delta/kernel/internal/deletionvectors/RoaringBitmapArray.java:214:1: as of release 9, '_' is a keyword, and may not be used as an identifier
[error] /Users/jacek/dev/oss/delta/kernel/kernel-api/src/main/java/io/delta/kernel/internal/deletionvectors/RoaringBitmapArray.java:214:1: as of release 9, '_' is a keyword, and may not be used as an identifier
[error] /Users/jacek/dev/oss/delta/kernel/kernel-api/src/main/java/io/delta/kernel/internal/deletionvectors/RoaringBitmapArray.java:214:1: as of release 9, '_' is a keyword, and may not be used as an identifier

It is only "visible" when you change build.sbt to use the following line (which I'm going to submit in a separate PR):
Compile / compile / javacOptions ++= Seq("-target", "11"),

How was this patch tested?
A local build with Scala 2.13 (val default_scala_version = scala213) and Java 11 (val targetJvm = "11" not "1.8") with the dependencies loaded from local-ivy-repo (not central)
$ sbt clean publishLocal
$ ./bin/spark-shell --packages io.delta:delta-spark_2.13:3.0.0rc1 \
--conf spark.sql.extensions=io.delta.sql.DeltaSparkSessionExtension \
--conf spark.sql.catalog.spark_catalog=org.apache.spark.sql.delta.catalog.DeltaCatalog
...
	found io.delta#delta-spark_2.13;3.0.0rc1 in local-ivy-cache
	found io.delta#delta-storage;3.0.0rc1 in local-ivy-cache

Does this PR introduce any user-facing changes?
No

Can I ask for your review @allisonport-db @vkorukanti @scottsand-db? 🙏

Just FYI that I fixed (git commit --amend) the author after @scottsand-db's approval since it was Anonymous (for no obvious reason).


Unable to stream from RtmpFromFile.

Hi @pedroSG94  first of all thankyou for great library,
I'm not able to stream prerecorded video on facebook rtmp url, its woking fine on different devices I've tested but the issue occur on Samsung SM-G970F Android 10 onVideoDecoderFinished() this method is called when I start the stream. Here is the details of video

Any help will be appreciated.

Unable to reproduce. If you can provide more info or share the video to test you can reopen it
Closing as inactive.


updated console icon and new html5 console icon

#2272
https://bugzilla.redhat.com/show_bug.cgi?id=1201132

@martinpovolny please review

Thx. Ok, with me. Now we just need to update the toolbar definition to use the icon.

@martinpovolny pls review


Move Compiler.indexDependencyClasspath to separate utility

The indexDependencyClasspath should be moved out of Compiler.scala since it doesn't do anything related to the compiler. See https://github.com/scalameta/language-server/pull/45/files#r152680485

Has this been closed by #71?

Yes :)


Uncaught Error: Cannot find module 'crossfilter'

I installed the package inside a create-react-app and copied the demo code.

I solved it by adding crossfilter manually in my dependencies.

use npm install command to install dependencies.


Clone, not fetch the ce repo when building

Until you switch over to using a submodule, use clone/checkout to get the CE source code so that the set-version script in the build works correctly.

I don't think we should be having different version numbers.


fix(windows): don't attempt to initialize COM security levels twice

We use global functions to initialize COM. If the client executes
multiple scan operations at the same time on the same process, then COM
will be initialized twice, eventually resulting in an error.
The error is RPC_E_TOO_LATE, which according to the Windows
documentation, means that COM was already initialized. This commit
workarounds the initialization error by catching this HRESULT and
assuming everything is fine, but the correct solution is to get rid of
COM altogether.
Change-Type: patch
Changelog-Entry: Fix "Couldn't initialize the scanner: An unknown error occurred" error.
Fixes: https://github.com/resin-io-modules/drivelist/issues/198
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

@hedss Can we make VB rebase before creating the bump commit?


PSREDEV-1171: updated publish-to-dev to publish-to-demo.yaml

Proposed changes
PSREDEV-1171: updated publish-to-dev to publish-to-demo.yaml
What changed
Replaced test in the file name and file with demo to reflect the environment.
Why did it change
To ensure naming consistency.
Related links

Checklists

Environment variables or secrets

[x] No environment variables or secrets were added or changed

Permissions

[ ] This PR adds or changes permissions

Testing

How to review

Updated the secrets to use DEMO instead of TEST and created and added the Demo-test environment.


fixes shadow hydration escaping

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

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

fixes #3773
there are many better ways to solve this, if anyone has a suggestion.
Tests

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

Changesets

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

I also tried using devalue package but it's the same, html becomes malformed. This way is vulnerable to XSS probably so not the best way, but just a suggestion.

Actually I found out that Next.js is using the same(similar) strategy with regex like this PR:
https://github.com/vercel/next.js/blob/694407450638b037673c6d714bfe4126aeded740/packages/next/server/htmlescape.ts
I'll improve this a little but this isn't that bad.

we have a utility for that https://github.com/sveltejs/kit/blob/59badb515755a9294365e8084f9beefa10a90773/packages/kit/src/utils/escape.js#L19

and it would be great to have a test in https://github.com/sveltejs/kit/tree/master/packages/kit/test/apps/basics/src/routes/xss  so that we can catch regressions.

Thanks, I actually adopted the code from Next.js in the latest commit, but I'll implement that code now you suggested because DRY.

@PH4NTOMiki  i pushed a fix for the invalid double-qoute escape and added a test. hope you don't mind. this is kind of urgent :grimacing:

@PH4NTOMiki i pushed a fix for the invalid double-qoute escape and added a test. hope you don't mind. this is kind of urgent grimacing

Yeah, of course, thank you

Looks like you'll need to run pnpm format

these docs describe where the escaped result can be safely used, not how the return value looks like.
see https://github.com/sveltejs/kit/blob/647131e00149cb5299042eedeb880efcd855a2df/packages/kit/src/runtime/server/page/load_node.js#L260
it's actually a string prop on a larger json thats added to a script block elsewhere later. Not fond of this complexity but it is what it is.
I'd like to merge this first and we can improve the docs in a followup PR.

Something in this PR seems to have broken https://kit.svelte.dev/docs

@dominikg what do you think?
@benmccann could you roll over back to https://github.com/sveltejs/kit/pull/3793/commits/886ad462f5881694c2856d93f78b64d92029632b
I think that should work?

Or should I try to PR that again?

@benmccann also, is there any change that that Vite update could be causing anything? maybe together with this, or alone?

I think it's the " fix that @dominikg pushed, https://github.com/sveltejs/kit/pull/3793/commits/8c8e4e68b166a0afd323eb52c7d87c37c93d59a0 this commit, I think is the cause

It works if I revert this line:
body += `<script type="application/json" data-type="svelte-props">${escape_json_in_html(s(shadow_props))}</script>`;

Isn't that the current/latest line?

Yes, and it's broken


FCM Integration Android

Hello,
Can someone tell me how to integrate this libary with FCM, there is no word about it in Docs.
I followed: https://firebase.google.com/docs/cloud-messaging/android/client  because GCM is getting depracated.
and: https://github.com/wix/react-native-notifications/blob/master/README.md
But got stuck on Step #2: Add Sender ID to Manifest File is there something equivalent for FCM to this:
<meta-data android:name="com.wix.reactnativenotifications.gcmSenderId" android:value="1234567890\0"/>
Right now im getting:
java.lang.IllegalStateException: Sender ID not found in manifest. Did you forget to add it as the value of a 'com.wix.reactnativenotifications.gcmSenderId' meta-data field?
Thanks in advance

@AugustoAleGon did you?

@BenWildeman I do have completed successfully the integration. I still have to work on the article. What do you need?


Update README.md

This README needs a lot of work, but for the short-term I made a small fix (removed "we") so the project (which is useful to Zalandos) doesn't alienate non-Zalandos.

Coverage remained the same at 68.837% when pulling aff247b308fc9127cbce3aa8c6b54803f88b9163 on LappleApple:patch-1 into 2c1c5d945e3ac1880f0d2edd280abd66652bd840 on zalando-stups:master.

 Updated on successful CI builds.

:+1:

:+1:


Update description to reflect Sodium's FRAPI changes

Since Sodium now supports the FRAPI, it may be a good idea to update the READMEs to mention that Sodium now integrates it natively on 0.6 and above

Done!


feat: added fetch and event bus solutions

nano-event-bus and extended-fetch

Stars as usual....race for hype.

What I'm trying to do is list libraries that have been used, or at least reviewed, by some people already. This tends to uncover unexpected bugs and inconsistencies, and build some community.
Stars are not the best way to measure it, but it's better than nothing. Alternatively, we could use 50+ weekly npm installs, it's up for discussion.
If this list gains some traction itself, we could have a monthly promoted package to help new tools gain exposure and pass the regular criteria.
Hugs 🤗


[Issue] Login not possible after upgrade to 0.5.0

[X] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here:
azd version 0.5.0-beta.1 (commit 57cba771d598398f30acfef18a272d1906a8e4f1)
Output from az version
Run az version and copy and paste the output here (minimum required version is 2.38.0):
{
"azure-cli": "2.39.0",
"azure-cli-core": "2.39.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {}
}
Describe the bug
After the upgrade to 0.5.0-beta.1 I use the new login flow via azd login. The login option "Interactive authentication with a browser" is started opening a browser window.
Authentication via username (=email) states that:
This username may be incorrect. Make sure you typed it correctly. Otherwise, contact your admin.

A login with this username via az login or via Azure Portal is working.
To work around this issue, I did:

azd config set auth.useAzCliAuth true
Proceeded with azd login

And login worked as normal.
To Reproduce

Install/upgrade to latest version of Azure Developer CLI
Start the command azd login to kick off the "Interactive authentication with a browse"
Enter your username and press "next"

Expected behavior
The interactive login via browser and username should be possible
Environment
Windows 11
PowerShell 7.3.1
Additional context

Screenshot of error message:

The fallback via azd config set auth.useAzCliAuth true works

@ellismg Could this be fixed by the work on tenant IDs? It looks like our auth flow isn't handling personal accounts (outlook address for example).

To workaround the issue,

azd config set auth.useAzCliAuth true
Proceed with azd login

Thanks for the super-quick fix of this issue. Highly appreciated!


Update for search service overview

#sign-off
@timheuer @CamSoper @HeidiSteen

:x: Validation status: errors

File
Status
Preview URL
Details

api/overview/azure/index.yml
:x:Error

Details

:x:Error

Details

api/overview/azure/index.yml

[Error] Error transforming model "W:\uik2-o-unknown\raw-\pdpg2pav.mcm\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

[Error] Error transforming model "W:\uik2-o-unknown\raw-\pdpg2pav.mcm\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Description of localSystem is not helpful

Issue description
The description of localSystem is not helpful. Please rewrite this in a way where it is easy to see that if you want to do a deployment of a NixOps managed Linux machine on a Mac that you should set this.
In fact, the concept of defaulting to the platform on which one is running is flawed, because it is not functional anymore.
Functional means that "equal inputs should have equal outputs", but now we have that on a Mac there will be a different output.
Please explain why this defaulting mechanism was committed in the first place.
Additionally, until this is resolved, seeing a simpler change in which a warning is displayed if you are deploying something which does not specify this variable would be great.
    localSystem = mkOption {
      type = types.attrs; # TODO utilize lib.systems.parsedPlatform
      default = { inherit (cfg) system; };
      example = { system = "aarch64-linux"; config = "aarch64-unknown-linux-gnu"; };
      # Make sure that the final value has all fields for sake of other modules
      # referring to this. TODO make `lib.systems` itself use the module system.
      apply = lib.systems.elaborate;
      defaultText = literalExample
        ''(import "''${nixos}/../lib").lib.systems.examples.aarch64-multiplatform'';
      description = ''
        Specifies the platform on which NixOS should be built. When
        nixpkgs.crossSystem is unset, it also specifies
        the platform <emphasis>for</emphasis> which NixOS should be
        built.  If this option is unset, it defaults to the platform
        type of the machine where evaluation happens. Specifying this
        option is useful when doing distributed multi-platform
        deployment, or when building virtual machines. See its
        description in the Nixpkgs manual for more details.
        Ignored when nixpkgs.pkgs is set.
      '';
    };

I'm open to suggestions for improvements here but TBH I think that's a pretty good description of what localSystem does. As for defaulting to something else, what would you suggest? On macOS we could default to localSystem = { system = "x86_64-linux"; } but that seems just as arbitrary to me. We support many architectures so the user has to be specific on what they want.

It should be an error to not specify it given the above logic. That error could show some common use cases.
I still don't know what the option actually means.
Specifies the platform on which NixOS should be built.
I have read similar descriptions in GNU tools and those target system, etc., could be understood with some effort. This is not something you can give to someone and expect them to understand it.
It's not clear to me what the set of valid values is for example (I already looked at the source to get some sort of idea), but if I want to deploy nix to a Linux machine from a Mac system, I don't see what I should specify (nor do I see why I should specify something, because I already specified localSystem), but perhaps I missed in in one place (which brings us to the issue of defaults).
In fact, I would suggest to just link to GNU documentation or alternatively write something so clear that nobody can ask a question about it.
I might not even export the symbol in the first place, because determining the arch can be done at deploy time too given an AMI, as in my case.

I think this thread should only concern documentation efforts for specifically just this one option. Discussion of the design of the cross-compilation infrastructure should likely go elsewhere.
My current belief is that the cross-compilation infrastructure was likely designed by experienced professionals and as such their decisions are likely sound (albeit not understood by everyone).

It seems to me that NixOS would be better off with a 'host' and 'target' option. Conceptually:

host: where it's built
target: the system type that the NixOS instance will be compiled for

You're going to need a 3rd one for Nixpkgs no matter what. Consider building a C compiler where you have one machine that it is built /on/, one machine where it will be /run/, and another machine that it emits code for. NixOS modules should only have to worry about pkgs.buildPlatform and pkgs.hostPlatform. I agree that the naming is bad but I think this new scheme would lead to more confusion.
@shlevy has a rename that seems like an improvement in #36217. Basically we rename them to build, run, and emit to eliminate confusion from host and target.

This should probably have been represented as

nixpkgs.system: target
nixpkgs.hostSystem: host

They should both default to the current system.
Is it too late for this?

Again, not convinced this is better. I would name them "targetSystem" and "buildSystem" to clarify the confusion from "host". "host" in Nixpkgs means where you run stuff on, not where you are building it.

I would also point out that the example given in the documentation of this option does not actually work.

Any updates on this?

Any updates on this?


Is there a way to use chromedp on server without x11?

Is there a way to use chromedp on linux-server without x11?
To use chromedp I need to install chromium-browser before.
But it depends on x11..
I wouldn't like to install x11..

See https://github.com/chromedp/docker-headless-shell.


Train calculator

improved template module
added train calculator
added SNCF train data

How do we proceed on these, this and others are open now since several days. Should I merge as soon one approval is there? Or what is the procedure we want to use?


Add GitHub issue and PR templates

Would make it easier for people to raise the appropriate kind of issues and PRs. Shouldn't be too structured, but have enough comments to prompt detailed enough issues.
A few types of issues:

Bug (Something is broken)
Science Request (Add a new diagnostic)
Feature Request (Change something about the CSET software)

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests


Monorepo Deployment Build

[ ] The site and design system must build from a Docker image that can be used to deploy to Fly.io
[ ] The Fly.io Deployment must be able to connect to a Postgres and Redis instance
[ ] Prisma migrations and migration deployment must work from Fly build.
[x] Ensure all modules in server build (including deps) are ESM compatible.

This was time-consuming because the process was basically: Run the project, see what modules cause ESM import errors, and add those modules to the remix.config.json serverDependenciesToBundle. The current list is comprehensive,
If ESM errors are encountered during the server build, this is the solution.

[ ] Update NPM deps to remove 'outdated' warnings.
[ ] Ensure we're not making multiple connections to the Redis cache

Currently trying to find a workaround for this: https://github.com/npm/cli/issues/3847

Looks like this is a problem with npm: https://github.com/npm/cli/issues/3847
Will take some time to switch the project to Yarn.


macOS support

These changes add support for macOS. The I/O code for writing tunnel traffic adheres to the platform independent interfaces that already exist and are implemented for Linux, but the uapi code is shared in full between Linux and macOS. There is one slight inefficiency in the tunnel trait that forces a copy that could be eluded with a slight change to the trait. I've tested this implementation a bit and it seems to be on par with the linux implementation, sans the firewall mark.
This implementation does rely on 3 extra dependencies, some of which are there purely for ergonomics (nix) and could be substituted with more calls to libc and in-line struct definitions.

Hi @pinkisemils thanks a lot for contributing to wireguard-rs!
Letting you know that I am reviewing your code at this moment, but will need access to a macos machine to test the patch.
Until then can I get you to Sign off on the commits?


File Input

File input

[x] File upload
[x] Helper text
[x] Multiple files
[x] Sizes

Completed.


Settings.json is not saved

With the latest commits (HEAD @ https://github.com/whyboris/Video-Hub-App/commit/26fb13b6a9387ef271b39b800d10c38b62c0c1c1), if I use the X button to close the window, everything works fine. But if I Alt+F4 the window, settings.json will be reset to 0 byte.
Maybe it has something to do with https://github.com/whyboris/Video-Hub-App/commit/268294b2ca28cbe6359184b35ad6489f2fe4413e?

Thank you for keeping track of this 🙇 -- I removed remote because it's deprecated by Electron - with the commit you point to: https://github.com/whyboris/Video-Hub-App/commit/268294b2ca28cbe6359184b35ad6489f2fe4413e#diff-856b4a4969a5de4eb6bf7ac1f8f156c7063fc7bdf68209192b7b8769e059b788L493
I thought I solved the problem by making the app save everything before it finally quit, but seems like there are some loose ends 😓
I'll keep this Issue open until I get to it to fix it. PR for a fix is also welcome 👍

If I comment out the settings.json write at https://github.com/whyboris/Video-Hub-App/commit/268294b2ca28cbe6359184b35ad6489f2fe4413e#diff-0b4a13d876020b09b600e6a8fb04f755f6d531ecb9c9a7335510da545bbe9d7bR367, no reset happens. If I change the write mode to something non-destructible like r+, Alt+F4 wouldn't reset to empty but sometimes reset to all default values.
So it seems this function behaves differently depending on how "close window" is invoked. Maybe Alt+F4 doesn't leave enough time for the function to execute, and it was OK before because remote was synchronous?
If that's the case, I wonder maybe the ultimate solution is write settings whenever a setting is changed, instead of doing one lump sum write at closing time. Same for the vha2 file I guess?

There's bound to be a way to preventDefaul() somewhere 👌 or just properly use an Electron hook somewhere like -beforeunload 🤔
I would rather not write the settings every time the users plays with the buttons, and especially not write a possibly large (5+ MB) .vha2 file 😅 every time the hub gets updated (a video plays, tag is added, etc).
I'll try to find some time this weekend to replicate the bug and then fix it 🤞 though I'm also happy if anyone prefers to fix it instead of me 🤝 🙇 😁

I spent some time on this issue. It seems if I add event.preventDefault() before the getAngularToShutDown(); in win.on('close'), the problem is solved. So I think the logic you intended was

When the main window is about to close, intercept it, prevent it (which is currently missing), send event to try to save files.
When file is confirmed written, try to close the window again, with the readyToQuit = true set.
Now the event handler would actually close.

I guess because the event was not prevented, the closure still happened. So there was a race condition between the app quitting and file being saved. Since file change can't commit before quit, we got 0 byte settings.json.

Thank you so much! I'll try all this out on my end.
If you happen to have the code already, please consider opening up a PR 🙇
And if it's not 100%, I could clean it up too - please don't feel like you have to do everything 🤝

PR: https://github.com/whyboris/Video-Hub-App/pull/694

I had this issue and it broke the app in weird ways for me.  Settings changes would never save anymore after some point, regardless of the exit method.  I was stuck with the settings I had a month ago.  I reinstalled and it worked.  After that, settings save if I exit with the X button, but they don't save if I exist with alt-f4, which is what my mouse gesture uses.  However, I don't get a zero length settings.json file.  It just doesn't update.
Could you also add a "save settings" button if the bug persists?  Then making changes but forgetting to hit X would be less of an issue.

Closed with #694 🙇  thank you @CrendKing for the fix!


Hide empty returnTo

Changed

Changed redirect only have returnTo if not empty

Have you tested it? It looks like the automated tests are failing. Could be just a problem with the test itself.

@Schparky I got it working again. I'd still like to add when-avail later, but for now it's ready.


Application should not exit if passwords do not match during file encryption

Resolve #1 by adding a new method that will recursively prompt users for their passwords if they enter non matching passwords during file encryption. A limit could be added to the recursion to avoid stack overflow, but it is hard for me to see a user messing up the password that many times. That's your call though, I can add it if you want.

Merged. Thank you.


Request: better /usr/sbin/rebuild-iptables error messages on failure

Cookbook version
4.3.4
Chef-client version
13.8.5-1
Platform Details
debian-8, debian-9
Scenario:
If the iptables rules specified in the cookbook/recipe are invalid, the error message from a chef-client client run should identify the text of the rule that failed to apply.
Steps to Reproduce:
chef generate cookbook iptables-demo
cd iptables-demo
echo "depends 'iptables', '~> 4.3.4'" >> metadata.rb
echo "include_recipe 'iptables::default'" >> recipes/default.rb
echo "iptables_rule 'sample' do" >> recipes/default.rb
echo "  lines '-A DROP'" >> recipes/default.rb
echo "end" >> recipes/default.rb
## configure test kitchen for debian-8
kitchen converge

Expected Result:
chef-client should report the standard output of /usr/sbin/rebuild-iptables, and this output should include the specific iptables rule that failed to apply (in this case -A DROP, because it has no chain name).
Actual Result:
iptables-apply indeed generates the message,
Applying new iptables rules from '/etc/iptables/general'... iptables-restore: line 5 failed

where line 5 of this file is,
-A DROP

But rebuild-iptables doesn't output this last piece of information:
Expected process to exit with [0], but received '1'
---- Begin output of /usr/sbin/rebuild-iptables ----
STDOUT:
STDERR: iptables-restore: line 5 failed
/usr/sbin/rebuild-iptables:137:in `': /usr/sbin/rebuild-iptables: failed to install iptables rules (RuntimeError)
---- End output of /usr/sbin/rebuild-iptables ----
Ran /usr/sbin/rebuild-iptables returned 1

doing #67 and removing the extra shell_out layer would probably help this a lot

Hi,
I am closing this as it relates to an old version of the cookbook which has since been fundamentally changed. If you still have the issue with the latest version please could you open a new issue,
Thanks


Parent nodes buggy

Given a default group which has the permission "essentials.spawn" and a group user which has default as parent, sometimes the user group is not permitted to execute /spawn due to insufficient permissions.
Server version: git-Spigot-56f8471-43183ea
LuckPerms version: 5.0.23
Essentials version: <IP_ADDRESS>

So you set essentials.spawn to the group default?
Did you make sure you're using EssentialsX (Not Essentials. The X is important!) with EssentialsXSpawn?
Also, what is the actual MC version itself? The git version of spigot doesn't give a real clue about that.

Yeah, default group has permission essentials.spawn.
Yeah, I am using EssentialsX with EssentialsXSpawn.
Server is on version 1.14.4R01.

Could you try using the verbose command to debug this a little further.
https://github.com/lucko/LuckPerms/wiki/Verbose
It should make it clear what's going on here.

I think I may be running into the same issue. If not, let me know and I'll open a new one.
I have 3 groups:
default
member (parent: default)
mod (parent: member)
default has essentials.*: false
member has essentials.(sethome|home|me|msg): true
I am currently set as "mod", but when I try and run /home, I get "You do not have access to that command."
Running /lp verbose gives me the following output: (copied from web, sorry for the formatting)
t3rminus | essentials.home | false
Context: world=world
Origin: PLATFORM_PERMISSION_CHECK
Processor: me.lucko.luckperms.common.calculator.processor.WildcardProcessor
Cause: match: essentials

@t3rminus I suspect 88c432496b388c692a7139ae884fc7c40436845f will fix your issue.

@t3rminus I suspect 88c4324 will fix your issue.

Is there a new or replacement syntax that I should be using instead? I’m fine to upgrade from legacy syntax if necessary.

@lucko But I am not using shorthand syntax and it isn't working either..

@t3rminus I suspect 88c4324 will fix your issue.

Is there a new or replacement syntax that I should be using instead? I’m fine to upgrade from legacy syntax if necessary.

No need :)


Fetch response.json() seems slower than response.text()

Just wanted to document this performance issue (incase it really exists).
fetch_from_network = function() {
  fetch(url, {
      headers: {
        'Cache-Control': 'no-cache'
      }
    })
    .then(function(res){
      // If we do res.json, for unknown reason it is slowing the render of our very complex view. res.text() does not seem to have this issue
      return res.text();
    })
    .then(function(json){
      // setstate is called in this.process
      this.process( JSON.parse(json) );
    }.bind(this));
}.bind(this);

@mchev2 Can you do some profiling and post the results?

I did some independent tests and did not see any difference between res.text and res.json. I had to add in caching so res.text will work for my use case.
I'm not sure where the issue could be. Perhaps the json is too heavily nested and so there is a bottleneck. I will close this for now and let you know if I find anything else.
Thank you

@mchev2 just bringing this guy's issue to your attention, could be similar.
https://stackoverflow.com/questions/36499603/taking-too-much-time-to-call-promises-then-function/36501330#36501330

I have encountered the same issue, the responseText comes back straight away in milliseconds, but when it convert to json using .json(), it takes a few seconds, the interesting thing is if I click the screen during the .json() parsing period, it get the json data back straight away

Make sure you are:

profiling on device, not with Chrome debugger
profiling in production
measuring just the response.json() time and not anything else like setState.


[1.15.2] Potion charms color

I'm using the version 3.3.7, for 1.15.2. When I was using 3.2.4, charms used to be colored according to the potion they were crafted with, but with the latest version, they're all gray, and undistinguishable except by hovering them.

After bisecting a bit versions from 3.2.4 to 3.3.7, it seems the charms lost their colors starting from 3.3.0 (the backporting version ?), if that may help.


Add support for creating pre-production environments after a pull request in Azure DevOps?

When will this be added? Are there even plans to do so?

@archubbuck
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

Sorry about that @RamanathanChinnappan-MSFT
https://learn.microsoft.com/en-us/azure/static-web-apps/review-publish-pull-requests

Pull requests and pre-production environments are only supported in GitHub Actions deployments.


remove thomson Reuters from text of page and signatures of employees

Thomson Reuters is requesting the removal of mention of Thomson Reuters from the text of the overlay fact sheet and the signatures of some current an former employees (list below) as these employees are not authorized to speak on behalf of  Thomson Reuters. Any statements of this type would need to be vetted and approved through other mechanisms. (their names can remain if they wish, with the company designation removed.)
Ian Kersey
Caryn Pagel
Geetha Somasundaram
Nate Weber
Thank you,
Peter Bossley
Sr. Manager, Accessibility

I have attempted to create a branch but cannot push to this project as I don't appear to have access.
git push --set-upstream origin tr
remote: Permission to karlgroves/overlayfactsheet.git denied to pbossley.
fatal: unable to access 'https://github.com/karlgroves/overlayfactsheet/': The requested URL returned error: 403

Was able to fork and make pull request for this requested update.
#969
Thank you.


Add a detailed tutorial creating a non-trivial application

Walking people through implementing a real-world project using Rust would likely help jumpstart many people's progress. One suggestion was a camera web server, or we could do a Wi-Fi lightbulb project or something similar.

[ ] std
[ ] no_std

I'm working on something similar that is not on github yet, and which I informally call the "mega-demo".
My idea for the mega-demo is to just be a WiFi Routing/Repeater, as that does not require any additional hardware, so any board would work:

Basically, the WiFi will work simultaneously in WiFi AccessPoint mode, as well as in WiFi STA mode and would serve as a wireless extender of sorts, but on layer 3 instead of layer 2, due to restrictions in the WiFi ESP-IDF implementation. More or less a Rust-ified copy of https://github.com/martin-ger/esp32_nat_router
Might extend it with optional Ethernet support as well, now that all Ethernet drivers are also supported by esp-idf-svc

Now, the concrete use case of the demo is not that important, as I want to demo the other details. The stuff that basically transforms a "proof of concept" into an actual, working firmware that can be upgraded and integrated with smart home software:

It should have a WiFi ssid/password provisioning mechanism. The initial one should be based on the WIP captive portal, we might extend later with other provisioning capabilities
It should have over-the-air update mechanism, based on the WIP OTA Rust wrappers as well as the WIP GitHub-based OTA server implementation
Needless to say, it would need the (new) HTTP server Rust wrappers, the Wifi wrappers, the Eth wrappers and the NVS storage wrappers
The provisioning and management UI is planned to be based on Bulma and Yew and will be part of the firmware itself. If Yew turns out to be too heavy of a dependency I might switch to plain JavaScript. All of this to happen in the edge-frame project
The communication of the UI with the server should be based on these WIP APIs
Undecided yet: It might have an MQTT and/or mDNS+COAP story for sending statistics and controlling the router (to some extend) via smart home software like Home Assistant or OpenHAB

Once we have this, it should be easy to tailor this project into whatever specific hardware the user wants to support with it. I have the feeling, the hardware-specific stuff would be the minority of the code, the rest could just be re-used from this project. :)
But as you can imagine, lots of work, and lots of moving parts. Can easily take a few months.
Help greatly appreciated!

Hey there!
I'd be an eager consumer of such a tutorial. Especially I'd like to learn how to use Rust with OTA on my ESP32, preferably in a way that I can build+deploy using a button in VS-Code.

Hey there!
I'd be an eager consumer of such a tutorial. Especially I'd like to learn how to use Rust with OTA on my ESP32, preferably in a way that I can build+deploy using a button in VS-Code.

One year later, we still don't have a detailed tutorial for a non-trivial application, but at least we do have the foundations of the application that should be the basis of the tutorial.
Given how much the design of the mega-demo has deviated from the original plan from above, I think it needs its own book though - which can be referred from here of course.

Hey there, I thought I'd share my success with esp-rs + OTA here, maybe somebody else stumbling over this ticket might appreciate the relatively simple sample (~340 loc at the moment) including documentation how to use the OTA implementation:
https://gitlab.com/thomas351/esp32-rust-playground


Login Error: AccountLogonDeniedNeedTwoFactorCode

I built the bot, wrote the Settings.json File.
Created the authfiles Folder, extracted the zip from the SDA in there.
Than i set up my Account with it.
now when i start the Bot i get the following Error down belllow:
botmgr > botmgr > [TestBot 2016-04-05 11:21:30] ERROR: Login Error: AccountLogonDeniedNeedTwoFactorCode
[TestBot 2016-04-05 11:21:30] ERROR: Failed to generate 2FA code. Make sure you have linked the authenticator via SteamBot.
Can anyone help me Please :(

#427 #527

This Is not really helping me much :/

Run the exec [bot index] linkauth.  We should probably include that in the error string.

@BlueRaja where i can find this exec ? my Folders look like this

@BlueRaja where i can find this exec ? my Folders look like this

It would be a command entered while running the bot.
Please continue with any further questions on the SteamBot reddit, as mentioned above.

@BlueRaja New commands should be added here: https://github.com/Jessecar96/SteamBot/wiki/Usage-Guide


Capistrano deployment failing with 'rbenv: /home/alexander/.rvm/bin/rvm: command not found'

I won't show the whole log but here's the error message:
    (Backtrace restricted to imported tasks)
    cap aborted!
    SSHKit::Runner::ExecuteError: Exception while executing as<EMAIL_ADDRESS>bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

    SSHKit::Command::Failed: bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

    Tasks: TOP => deploy:updated => bundler:install
    (See full trace by running task with --trace)
    The deploy has failed with an error: Exception while executing as<EMAIL_ADDRESS>bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

I have no idea what this means. Ideas?

Error message indicates a problem with rvm missing. Please try at stack overflow for an answer on installing it. Try https://github.com/capistrano/rvm/ or http://capistranorb.com/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/

rvm definitely isn't missing. It's installed on the machine and I've verified that through SSH.

Please read the whole answer you were given.

The command still fails through SSH, too.

The command still fails through SSH, too.

Seems like a server problem rather than a Capistrano one, if it even doesn't work with Capistrano out of the equation. Try and read the links you were given, and open an issue with your hosting provider, or with the RVM/Capistrano teams.


CLIMATE-700 - Complete examples to reproduce a RCMES-based paper

Ten yaml files have been added in examples/NARCCAP_paper to reproduce the plots in Kim et al.(2013) paper on evaluating NARCCAP RCMs

Merged build triggered. Test Failed.

Merged build started. Test Failed.

Merged build finished. Test Failed.


python3Packages.nox: Remove optional dependencies from testing

Things done
This reduces closure size and none of the optional dependencies seem to be critical for testing.
My main motivation is to remove uv from the dependencies so updates can hopefully go to master instead of staging.

Built on platform(s)

[x] 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/)
25.05 Release Notes (or backporting 24.11 and 25.05 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.

@ofborg build python312Packages.nox python312Packages.nox.passthru.tests

Seems this may have caused a test failure? But I'm not sure how something like that would only appear now...

That doesn't look related to this change at all, and was not something I saw building this change against master..

and was not something I saw building this change against master

Yeah I'm not able to reproduce this on master either. I'm guessing it's a staging issue
Could you try rebasing onto master? I think the rebuild count here would be fine

@ofborg build python312Packages.nox

This reduces closure size and none of the optional dependencies seem to be critical for testing.

First of all, since we are talking about nativeCheckInputs, this is an incorrect statement, as these are not added to the closure, but are only build time dependencies. Please fix that in the commit message.

My main motivation is to remove uv from the dependencies so updates can hopefully go to master instead of staging.

It is correct though that due to nox's dependency on uv, changing uv causes a change to nox. Could you explain a bit better what is your motivation? You want to be able to change which package and not go through staging? It seems you have managed to not go through staging in this PR..
Note @getchoo that now that the target branch is master, CI is green, so you should be able to unblock the PR.

It is correct though that due to nox's dependency on uv, changing uv causes a change to nox. Could you explain a bit better what is your motivation? You want to be able to change which package and not go through staging? It seems you have managed to not go through staging in this PR..

Uv has an artificially inflated rebuild count because it's added where it's not even needed/used.
I want uv updates to be as fast/smooth as possible.


Update ConfigureNric1384.cs

Add missing [Category(ConfigurationCategory)] attributes to calibration file path properties

Use this PR to address #363 as well.


bring back lost commits

Changes Unknown when pulling 26335c03e63aa170abbce5dbd35f90f39fbaa1ad on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 26335c03e63aa170abbce5dbd35f90f39fbaa1ad on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 120ec566e864694b64bd5be0ff15e0d5c772c2ee on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 542696a5e44eee3ed1ecb44f20306f928b430634 on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 542696a5e44eee3ed1ecb44f20306f928b430634 on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 381e8b191b137c35b96e3fec50de663467d7b443 on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 381e8b191b137c35b96e3fec50de663467d7b443 on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 381e8b191b137c35b96e3fec50de663467d7b443 on master into ** on vincent/lost-branch**.

Changes Unknown when pulling 86133bb198a24a15f9850c2833f7e13942964956 on master into ** on vincent/lost-branch**.


Any good ways to get access to the output shape of certain previous layer?

Need this information to either pad or crop the feature map to train the fully convolutional neural network.

Yes! Build your model, access the layers with model.layers, then check out the attributes of your layer of interest. .input_shape and .output_shape are what you're looking for.

Thx, But I need that information to be included in the computation graph. Namely, the running computation needs to adjust the computation based on that.

Indeed, model.layers is only accessible once you have instantiated your model.
Using the ._keras_shape attribute of the output of any instantiated Layer, you should be able to get the output_shape of your tensor and run your computations accordingly. For instance:
x = keras.layers.Input(x_train.shape[1:])
conv1 = keras.layers.Conv1D(16, 8, padding='same')(x)
print(conv1._keras_shape)
I think if you want to be "cleaner" you should create a custom layer (https://keras.io/layers/writing-your-own-keras-layers/) and use the input_shapeargument in the build function to get the relevant information that you need. This is for the previous layer.
If you want information from all the previous layers shapes, you can use get_input_shape_at(node_index), which is an inherited function from the Layer class.

Simply call the output or output.shape
model.layers[5].output
or
model.layers[5].output.shape


feat: add dart implementation

Summary
Init Dart Package.
Add Features:

Conversion: Ascii to Gurmukhi
Gurmukhi Utils: Remove vishraams, First Letters, Split, Normalization

Test
PASS

I have refactored the tests to get data from the Json files.
I have 2 assertions failing (for functions unicode3, and unisant2):
"iBÎo": "ਭਿ੍ਯੋ"
"kIÎo": "ਕੀ੍ਯੋ"

What I understand is you want to sort diacritics with virama for ਹ, ਰ, ਵ, ਟ, ਤ, ਨ, and ਚ but with the exception of ਯ?
The expected strings ਭਿ੍ਯੋ and ਕੀ੍ਯੋ are themselves invalid Unicode sequence.
It's better if 1st is converted into ਭ੍ਯਿੋ, for the 2nd I don't know.
As Unicode Standard doesn't have ਯ variants as of now, I think we should not try to work around in these cases. We should handle them with Sant-Lipi modifiers.

I would love to show as accurately as possible. This would require some testing on different platforms / font rendering engines. Very curious what this shows:
ਭ੍ਯਿੋ
As for the other example (where the preceding consonant has a right-side vowel/modifier) of ਕੀ੍ਯੋ, I don't think that will work in any platform/font rendering engine. I'd be very impressed if it did work. We had to create Sant Lipi almost purely for this real issue.
Related https://github.com/shabados/mobile/issues/194

੍ਯ is not present in SGGS, and SDG has variants of ਯ. So, if the user wants to handle ਯ variants, he has to use Sant-Lipi.
I strongly believe that unicode, santlipi, and unisant test functions should not be expected to give same output in the case of ਯ. It will also let the user to choose the conversion type he wants.
For example:

ascii
unicode
santlipi
unisant

iBÎo
ਭ੍ਯਿੋ
ਭਿ꠳ਯੋ
ਭਿ੍ਯੋ

kIÎo
ਕ੍ਯੋੀ
ਕੀ꠳ਯੋ
ਕੀ੍ਯੋ

 likes fine on my devices (Windows, Android).

Sorry for the delay. Some thoughts on next actions / clarity:

Unicode and unisant functions should return exactly the same output. The whole point of unisant function is to confirm sant lipi markup can be properly converted to unicode
We have to decide on what our unicode standard is basically. This depends on how well all platforms/engines can render the words. For example ਭ੍ਯਿੋ seems to be working, and we can create a rule that says if there is only left-hand vowels on the preceding consonant and none on the half-yayya following then to render it properly in unicode. This is up to us as a team, our parameter is simply to ensure it can be displayed accurately (or with good information) to the end user.

Some actions for you please:

Please create an issue (task) to implement a linter/checker and add some of the info from this PR into there for tracking purposes (or at the least reference this PR link to add reference)
Same thing for normalization / ਡ + ਼ = ੜ and such

This will help us simplify the scope of this PR

I also think ੍ਯ should be considered as exception for sorting diacritics in case of Virama.
I have also added ਿ as a further exception in this case as it looks better.
You can see my change for reference.
So, all the tests are passing finally!
Except ਭਿ੍ਯੋ, my result is ਭ੍ਯਿੋ.
Please update ਭ੍ਯਿੋ in the tests.

Awesome! We are pretty close to finishing up this PR (I still have to do a final review)
Please do the following:

Update global test for ਭ੍ਯਿੋ
Update global readme with Dart support (there is a progress chart under ## WIP)

I will open an issue to investigate ੍ਯ patterns.

Thank you very much for that! Would you agree that this PR is ready for a final review? Is there anything else you'd like to do?

Thanks! I would add more features in later PRs.
This PR is more than enough for now.