LogLevel seems to be ignored

From<EMAIL_ADDRESS>on November 04, 2010 14:19:06
What steps will reproduce the problem? 1. Apache LogLevel set to alert
2. ErrorLog fills with info and warning messages What is the expected output? What do you see instead? I would expect the module logging to respect the LogLevel definition; instead if seems to log anything. On what operating system? Debian 2.6.26-2-amd64 Which version of Apache? Server version: Apache/2.2.9 (Debian)
Server built:   Nov 14 2009 21:07:23 Which MPM? prefork Please provide any additional information below, especially a URL or an HTML file that exhibits the problem.
Original issue: http://code.google.com/p/modpagespeed/issues/detail?id=18

From<EMAIL_ADDRESS>on November 04, 2010 11:22:49
Adding a few of these log entries:
[Thu Nov 04 19:21:26 2010] [warn] [1104/192126:WARNING:net/instaweb/util/google_message_handler.cc(32)] http://s2.bmedien.eu/4/images/buttons/collapse_40b.png : Invalid url relative to ' http://www.html.de/' [Thu Nov 04 19:21:26 2010] [notice] [1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] http://www.html.de/vbseo.php:1 : 47622us: HtmlParse::ApplyFilter:HtmlAttributeQuoteRemoval
[Thu Nov 04 19:21:26 2010] [notice] [1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] http://www.html.de/vbseo.php:1 : 47809us: HtmlParse::ApplyFilter:HtmlWriter
[Thu Nov 04 19:21:26 2010] [notice] [1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] http://www.html.de/vbseo.php:1 : 50323us: HtmlParse::FinishParse
[Thu Nov 04 19:21:26 2010] [warn] [1104/192126:WARNING:net/instaweb/util/google_message_handler.cc(32)] Fetching resource http://www.html.de/customavatars/ce.d522f0f7185919e7e893e3f6f30f5c37.avatar8427_2,g.gif.. .
[Thu Nov 04 19:21:26 2010] [notice] [1104/192126:INFO:net/instaweb/util/google_message_handler.cc(29)] Fetch succeeded for http://www.html.de/customavatars/ce.d522f0f7185919e7e893e3f6f30f5c37.avatar8427_2,g.gif , status=200
The logfile grew to 60Mb in 10minutes; I am going to disable the module for now but I can re-enable it for debugging any time.

From<EMAIL_ADDRESS>on November 04, 2010 12:33:16
I'm seeing the same behavior. Similar config. LogLevel set to "Error" and getting Warn and Notices filling up log files very rapidly. Had to disable most modules to prevent server from overloading on I/O.

From<EMAIL_ADDRESS>on November 04, 2010 12:45:45
I had the same issue,
CentOS release 5.5; x86_64
Server version: Apache/2.2.8 (Unix)
MPM: prefork

From<EMAIL_ADDRESS>on November 05, 2010 02:47:49
same here, confirmed. Loglevel is at "warn" but logs are spammed with INFO messages.
Apache/2.2.14 (Ubuntu)
X-Mod-Pagespeed	<IP_ADDRESS>-128
mpm/prefork

From<EMAIL_ADDRESS>on November 05, 2010 05:53:04
Same here. More than 400 MB of error log file in less than 2 minutes. Server usage goes to 95 in top (never seen that without the box dying).
CentOS release 5.5; x86_64
Server version: Apache/2.2.16
PHP/5.2.14
prefork

From<EMAIL_ADDRESS>on November 05, 2010 08:22:58
We're looking into this, thanks for you patience, guys.
Owner<EMAIL_ADDRESS>Labels: -Priority-Medium Priority-Critical

From<EMAIL_ADDRESS>on November 05, 2010 11:16:41
Owner<EMAIL_ADDRESS>

From<EMAIL_ADDRESS>on November 05, 2010 15:50:06
https://code.google.com/p/modpagespeed/source/detail?r=146 Note: this fix has not been made available in binary form yet.  We will release new binary distributions incorporating these changes on Monday Nov 8.
Those building using the open-source instructions on https://code.google.com/p/modpagespeed/wiki/HowToBuild can try out these improvements immediately.
Status: Fixed

From<EMAIL_ADDRESS>on November 08, 2010 11:49:57
Did this go out today ?  Not sure how to tell if there was a new release posted.

From<EMAIL_ADDRESS>on November 08, 2010 11:52:30
This hasn't been released yet.  The wheels are turning.  Will post when the release is out.

From<EMAIL_ADDRESS>on November 09, 2010 00:44:54
Fixed & verified with the new release. Thank you guys.

From<EMAIL_ADDRESS>on November 09, 2010 07:41:45
Your welcome, glad to make us respect user settings.

From<EMAIL_ADDRESS>on November 19, 2010 05:41:23
mod-pagespeed-beta <IP_ADDRESS>- r215 VineLinux x64 5.1
Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8k DAV/2 PHP/5.3.3
confirm the same problem.

From<EMAIL_ADDRESS>on November 19, 2010 05:56:49
Teama -- you are still seeing messages in your error_log that should not be there, based on the log level?   Can you paste one of them into this bug?

From<EMAIL_ADDRESS>on November 20, 2010 00:13:39
Sorry for lack of information.
LogLevel was "warn", but "notice" was written into the "error_log"
<httpd.conf>
LogLevel warn
<Error_log>
3774 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7307us: HtmlParse::ApplyFilter:Javascript
3775 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** Found script with src https://***
3776 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** Found script with src .js
3777 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/apache/serf_url_async_fetcher.cc(632)] Initiating async fetch for http://  /****.js
3778 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(29)] http://** Couldn't fetch resource getdata.js to rewrite.
3779 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7776us: HtmlParse::SanityCheck
3780 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7918us: HtmlParse::CoalesceAdjacentCharactersNodes
3781 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7975us: HtmlParse::ApplyFilter:InlineCss

From<EMAIL_ADDRESS>on November 20, 2010 05:41:06
Teams.Ken: please update to the latest release; binary or source

From<EMAIL_ADDRESS>on November 21, 2010 01:42:47
Thank you for your advise.
I apologise for mistake.
The cause is thing that I used an old rpm unpack modules.
I re-unpack latest release rpm and store it on folders, and confirmed this issue was resolved.

From<EMAIL_ADDRESS>on December 04, 2010 06:11:36
bug in Apache 2.2.x Win32 (in 2.2.17 too)
pls reopen bug

From<EMAIL_ADDRESS>on December 04, 2010 10:11:40
Win32 version has been moved to bug 132 . Please let us know if this is an issue for other platforms as well.

From<EMAIL_ADDRESS>on December 04, 2011 17:52:14
Hi All,
Is this already fixed? In what version of Apache?
COz I am also having problems with this. Loglevel is set to warn but
[notices] and all are still showing in error.log
Regards,
Cerebro911

From<EMAIL_ADDRESS>on December 04, 2011 17:59:05
Can you paste a fragment from your error log?  This was fixed quite some time ago, probably in mod_pagespeed 0.9.11.*.
I'm not I understand the comment about the apache version; apache is versioned separately from mod_pagespeed and this bug is mod_pagespeed-specific.

From<EMAIL_ADDRESS>on December 04, 2011 18:38:54
Hi,
Sorry newbie here.
Oh I thought it is an apache bug.
My issue is something like this:
Sorry for lack of information.
LogLevel was "warn", but "notice" was written into the "error_log"
<httpd.conf>
LogLevel warn
<Error_log>
3774 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7307us: HtmlParse::ApplyFilter:Javascript
3775 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** Found script with src https://***
3776 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** Found script with src .js
3777 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/apache/serf_url_async_fetcher.cc(632)] Initiating async fetch for http://  /****.js
3778 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(29)] http://** Couldn't fetch resource getdata.js to rewrite.
3779 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7776us: HtmlParse::SanityCheck
3780 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7918us: HtmlParse::CoalesceAdjacentCharactersNodes
3781 [Fri Nov 19 21:59:18 2010] [notice] [1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 7975us: HtmlParse::ApplyFilter:InlineCss
I got this from comment 15.This is exactly my issue. I set loglevel to warn but then [notices] and other log messages are showing in error.log. SO what do I need to do? Install mod_pagespeed?
Regards.

From<EMAIL_ADDRESS>on December 04, 2011 18:40:00
hi
and this is running in Windows 7 environment.
Thanks

From<EMAIL_ADDRESS>on December 04, 2011 19:24:01
This is pretty interesting.  We have heard hints on the discussion forum of people running mod_pagespeed in Windows.  But we have never attempted to compile it on Windows ourselves.
But based on your message, someone did indeed once get this working, and evidently a copy of it is still floating around.  However, I can tell by the error log fragments that the version is very old & out of date.  It's quite possible that the version you are using pre-dates our bug fix for this issue, which occurred over a year ago.
Can you tell use the origin of your mod_pagespeed installation?


Typo in Daisy Pinout graphic shows I2C3_SCL on Pin1

The pin is correct, and the csv file is accurate, but the pin is not capable of doing I2C3_SCL.

this has been resolved with the new version of the pinout :)


Add specific variables for PWM control, rather than sharing SpeedData…

… - must be matched in main.c!!!

another push coming; hold this a moment.

ok, both done.  flash write (or read) does not work :(.

when was the last time it was working? Can you manipulate flash through ASCII protocol?


Can't push RTMP to instance using this container

First, I realize this isn't wowza support and I don't expect that, but I'm gonig to ask anyway in case this has to do with setup and assumptions that might have been made one way or another.
For testing live, I use ffmpeg to push RTMP using copy where the source is a an h.264, baseline with aac audio (all very typical). In the past, I've had no issues using this (see below) to push a stream to wowza, but with the instance I created using this container, I'm getting strange errors that I've not seen and I'm wondering if there might be dependencies on the server that aren't setup, which were with the official EC2 Wowza AMI.
To make matters worse, it seems like the stream will run for as much as 10 seconds some times and error out instantly at others. I have ~35Mbps uplink and the video is only 3.5Mbps so I don't think that's relevant (though I've never seen such behavior when I was pushing too much anyway.)
Any thoughts?
My command: "c:\Program Files\ffmpeg\bin\ffmpeg.exe" -stream_loop -1 -i teaser.mp4 -vcodec copy -acodec copy -f flv rtmp://my.streaming.server:1935/liveorigin/teaser
The errors (tail of output):
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
WriteN, RTMP send error 10054 (129 bytes)
WriteN, RTMP send error 10054 (41 bytes)
WriteN, RTMP send error 10038 (42 bytes)
av_interleaved_write_frame(): Operation not permitted
[flv @<PHONE_NUMBER>7fa020] Failed to update header with correct duration.
[flv @<PHONE_NUMBER>7fa020] Failed to update header with correct filesize.
Error writing trailer of rtmp://my.streaming.server:1935/liveorigin/teaser: Operation not permittedframe=   24 fps=0.0 q=-1.0 Lsize=     294kB time=00:00:00.95 bitrate=2514.0kbits/s speed=3.75x
video:461kB audio:23kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Conversion failed!

Can you try using the demo version of Wirecast (if you don't own it) or Adobe Flash Encoder to rule out the possibility of ffmpeg options being your problem?  My experiences using ffmpeg have been far from consistently successful and I've never has any issues using this container.

That did the trick so it's clearly not wowza (or this image). Thank you.

thanks for helping out @jshimko. much appreciated :+1:


Consider adding support for Open Document Format files

Please consider implementing reading and writing of Open Document Format files (with the .ods extension in this case).
This is an open, standardized format not under the control of a single commercial entity and can in fact be read and written by Microsoft Excel.
Support will facilitate the broadest reach of information exchange without relying on proprietary formats with associated network effects and vendor lock-in.
https://www.libreoffice.org/discover/what-is-opendocument/

Note that xlsx is an open specification:
https://ecma-international.org/publications-and-standards/standards/ecma-376/
I've looked into ods and it is a substantial amount of work to import/export from ods

Hi,
Thanks for your response.
The OOXML standard is apparently described in a much larger document than ODF that received much less scrutiny compared to ODF during the standardization progress, it's unclear how much Microsoft adheres to its own specification in its software because it is much larger, OOXML standardization came in response to the ODF ISO standardization and the standardization process was unusual and contentious, per
https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML. My read of the situation is that ODF is easier to implement correctly and fully compared to OOXML.
The question really is, why didn't Microsoft simply adopt ODF instead of its own standard, and work within the standards bodies to improve it if it believed it to be necessary?
This seems to be a case of using a standards organization to give legitimacy to a competing format while refusing to adopt and improve an existing standard because it would mean loss of control for the company. Then the question becomes, who really owns and manages this "standard"?
I realize this is partly a political argument, but to avoid long-term document interoperability issues it is important for software to properly adhere to standards and not be effectively controlled by a single business entity with its own agenda of using the network effects of its proprietary document formats to capture markets and a history of Embrace, Extend, Extinguish.
At any rate, this is just a suggestion for your consideration, and as a Rust fan I appreciate the work you are doing! 👍 Thank you.

Hi Jos,
This is huge topic, and in a large way, as you say political. One of the most important topics objectives of IronCalc is reach as many people as possible so open standards is a priority for us.
We will try to implement ODF import export once we reach a stable version :)

Hi Nicolás,
That makes a lot of sense. Thank you so much for considering this! 🙏


UX Design FAM single users and multiple users for roles assignment

Describe the task
Develop UI design for multiple users to multiple roles and multiple forest client #
Acceptance Criteria

[ ] Visual representation of the ability to add multiple users to roles and client #
[ ] Design should support both single and multiple users
[ ] third

Additional context

The design will work towards scenario 1 in this mural board of assigning the same multiple users to the same multiple roles and the same multiple forest client ids: https://app.mural.co/t/climatechange4363/m/climatechange4363/1681866407421/10f7dc05b9fe00dc1c9895ee513593b1cc93455a?sender=u84301558fa490f89e6792901

Moved out of sprint


Unable to set colours over the LAN protocol.

As the issue states, this plugin is unable to change the LIFX lights colours via the LAN protocol.

I'm seeing this issue too. Library works fine without lan mode enabled, but with the original (kickstarter) lifx bulbs, lan protocol works fine for turning the lights on and off, but does not work for setting any of the colour attributes. the homebridge console log displays the brightness, saturation, and hue changes accurately - just the bulbs never update these characteristics over lan.
i'm looking in to it now.

👍


OCPBUGS-37740: Should not panic when invalid log-level flag is used

Description
This fix avoid oc-mirror v2 going into panic, when an invalid log-level flag is used.
NB The loglevel flag has been changed to log-level to comply with other tools such a Podman etc
Fixes # OCPBUGS-37740
Type of change

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

How Has This Been Tested?
Locally , executing binary
Expected Outcome
bin/oc-mirror --config simple.yaml file://test-lmz --v2 --log-level -v

2024/09/04 12:36:30  [WARN]   : ⚠  --v2 flag identified, flow redirected to the oc-mirror v2 version. This is Tech Preview, it is still under development and it is not production ready.
2024/09/04 12:36:30  [INFO]   : 👋 Hello, welcome to oc-mirror
2024/09/04 12:36:30  [INFO]   : ⚙  setting up the environment for you...
2024/09/04 12:36:30  [ERROR]  : log-level has an invalid value -v , it should be one of (info,debug,trace)

/lgtm


The PrivacyInfo.xcprivacy has Invalid API category declaration "User Defaults"

This may be an Xcode error, causing the source code of the plist file to be stored incorrectly
...
<key>NSPrivacyAccessedAPIType</key>
    <string>User Defaults</string> // wrong value
    <string>NSPrivacyAccessedAPICategoryUserDefaults</string> // correct value
...

ITMS-91054: Invalid API category declaration - The PrivacyInfo.xcprivacy for the “GoogleMapsResources.bundle/GoogleMaps.bundle/GMSCoreResources.bundle/GMSShaders.metallib” file contains “User Defaults” as the value for a NSPrivacyAccessedAPIType key, which is invalid. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPIType keys in your app’s privacy manifest must be valid API categories. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.
ITMS-91054: Invalid API category declaration - The PrivacyInfo.xcprivacy for the “GoogleMapsResources.bundle/GoogleMaps.bundle/GMSCoreResources.bundle/GMSShadersSim.metallib” file contains “User Defaults” as the value for a NSPrivacyAccessedAPIType key, which is invalid. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPIType keys in your app’s privacy manifest must be valid API categories. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@LuYu001 Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

Hi @LuYu001, did you use the bundle provided at https://developers.google.com/maps/documentation/ios-sdk/config#add-apple-privacy-manifest-file? We expect that that bundle contains the correct value for NSPrivacyAccessedAPICategoryUserDefaults in NSPrivacyAccessedAPIType.

From the documentation:

Download the Privacy Manifest bundle for the Maps SDK for iOS: GoogleMapsPrivacy.
Extract the file to access GoogleMapsPrivacy.bundle.
Copy GoogleMapsPrivacy.bundle into your Xcode project's top level directory.

How does this actually work? How does the app know that the privacy manifest is associated with the Google Maps SDK? Inside the manifest itself, there's no indication of which SDK it belongs to.
This is also what Apple's documentation says:

For each executable or dynamic library in an app that uses a required reason API, the bundle that includes the executable or dynamic library needs to include a privacy manifest file that reports the API. For the expected location of frameworks and dynamic libraries, see Placing content in a bundle.

Shouldn't the privacy manifest be embedded into the SDK?

@wangela
Privacy manifest should be included into the SDK itself, we should not copy it manually into our app's bundle
Example how Facebook did it:
https://github.com/facebook/facebook-ios-sdk/commit/f1c6efffa33aa6eeee0d474986d0a448b4853d68#diff-38739d8f80b7049551eb5763290275ae4820767db457ac03cc3f182e6968db10


Calculate elbo and derivatives only for relevant sources

Currently the bvn and brightness gets calculated for every source in 1:mp.S, which is wasteful.

Closed in https://github.com/jeff-regier/Celeste.jl/pull/199


Assorted fixes for the documentation

I spotted a couple of typos/errors in the examples of the Mapping and the Faceting sections of the documentation.
I haven't reformatted the XML documents so the pull request is more readable, feel free to do it.

Thanks a lot! Merged, and created https://hibernate.onjira.com/browse/HSEARCH-1021 for this.


parsers: whois.cira.ca: Add new version support for 2019 whois output

Most recent whois output from CIRA, with year 2019, has a very different
output than what was expected in the past. This adds support for it
while keeping support for previous versions of the whois output.
This requires the changes introduced in PR https://github.com/weppos/whois-parser/pull/130 to work properly (as issue with the missing new line otherwise).
Fixes #126

Looking good! Fixes #126.

I'm finding that this fix is needed for the .ca domains.
If we're not comfortable with the fix in #130, Is it possible to move the fix for the unterminated (with newline lines into the parser (lib/whois/parsers/whois.cira.ca.rb) with something like:
      def content_for_scanner
        super
        @content_for_scanner << "\n" unless @content_for_scanner.end_with?("\n")
        @content_for_scanner
      end

How can we move this PR forward?

I just answered to @joallard on #130 to have this move forward.
Who has merge rights on this repository though ?

Thanks for this @XaF, for the record I ended up starting my fork in which I merged some of the pending PRs and provided more fixes. I didn't cherry-pick your PR here because it was keeping a lot of legacy code and adding on top, instead I refactored the parser to use the standard ICANN Compliant parser and updated all tests in ed7068c39a9821b084eb59416e49d3f0a7567d83. There's no reason to keep supporting the outdated version (unless you see one?), whois.cira.ca server is not going to return older versions any more. This version is working well for the couple hundreds of .ca domains I have. So people who need this can use my fork in the meantime:
gem 'whois-parser', github: 'jarthod/whois-parser' # Unofficial but more up-to-date fork, check status at https://github.com/jarthod/whois-parser


Improve the serialization performance of pickled lists and tuples

Describe your changes and why you are making these changes
For collections that are pickled, we can go one layer down and serialize each individual object before pickling. This is not recursive.
Created a new serialization_type called BSON_PICKLE to convey the info that any tables in the potential connection will have to be serialized/deserialized with BSON_TABLE.
Testing:
Are there performance metrics you'd like me to collect?
Related issue number (if any)
ENG-2478
Loom demo (if any)
Checklist before requesting a review

[ ] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[ ] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[ ] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@likawind added the new test as discussed!


monitoring-plugins: 2.3.5 -> 2.4.0

Description of changes

https://github.com/monitoring-plugins/monitoring-plugins/releases/tag/v2.4.0

All patches are now included in this release and could been removed.
As upstream removed the translations, the Makefile does not need to be patched anymore^0.
The license was fixed, as it is GPL-3.0-or-later, take a look at the "or (at your option) any later version" part in each license header^1.
Things done

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

@anthonyroussel: As you just merged #298757, addressing similar topics, would you please take a look? Thanks :)

Thanks for taking the time and merging it, @anthonyroussel.


Variance normalization

I'm trying to understand the variance normalization that happens here https://github.com/royerlab/cytoself/blob/9f482391a8e7101fde007184f321471cb983d94e/cytoself/trainer/cytoselffull_trainer.py#L144
I can't seem to find a similar variance normalization discussed in the hierarchical VQ-VAE paper or other older papers, and it's not clear to me why normalization by a single scalar is needed here.
It's also not clear to me why you only normalize reconstruction1_loss, but reconstruction2_loss calculated here is left the same https://github.com/royerlab/cytoself/blob/9f482391a8e7101fde007184f321471cb983d94e/cytoself/trainer/autoencoder/cytoselffull.py#L198 Wouldn't it make sense to normalize both of them, given that they get summed into the same loss?
Also do you think it's really important to calculate the variance for train/ val/ test separately? Could one just use the variance across train for all? The difference doesn't seem to be large, and it makes things a little easier.
Any help here would be appreciated - thanks!!

Also the variance value I have is ~285, which seems quite high relative to the other loss numbers and means that the reconstruction1_loss seems to be having very little effect.

Opps, my bad, my variance is actually 0.01677 which makes what you have in your example and won't cause the reconstruction loss to be ignored, my bad. Still my questions above remain.

I can't seem to find a similar variance normalization discussed in the hierarchical VQ-VAE paper or other older papers, and it's not clear to me why normalization by a single scalar is needed here.

I couldn't find a good explanation online either, although I think I did read something in the early time of this project.
I might have not thought too much about why and simply followed the original implementation.
Now looking back to the original VQ-VAE paper (particularly Fig. 1), I feel the purpose of variance normalization is to facilitate the optimization of the red vector in Fig. 1. I guess it might have been difficult to balance reconstruction loss among other losses without variance normalization (although it's not impossible to just let the model figure out the best way). If that's the case, the value of the variance shouldn't matter as long as the optimization can go on smoothly.

Wouldn't it make sense to normalize both of them, given that they get summed into the same loss?

If the purpose of variance normalization is to facilitate optimization, then yes, reconstruction2_loss should be normalized in one way or another. I didn't normalize it I guess because I didn't know what should I use for the normalization (whether the variance of the original input data or the latent vector).

Also do you think it's really important to calculate the variance for train/ val/ test separately? Could one just use the variance across train for all? The difference doesn't seem to be large, and it makes things a little easier.

If my guess above was correct, then yes we don't need to worry about the accurate value of any variance. I guess in practice we just need to estimate an approximate number that falls in the same order of magnitude of the real training variance (this may vary up to the dataset). And we don't need to calculate variance for val and test.

feel the purpose of variance normalization is to facilitate the optimization of the red vector in Fig. 1. I guess it might have been difficult to balance reconstruction loss among other losses without variance normalization (although it's not impossible to just let the model figure out the best way). If that's the case, the value of the variance shouldn't matter as long as the optimization can go on smoothly.

Ok yeah - this makes sense, it's just a nice way to get some rough scale invariance, e.g. mse / variance.

then yes, reconstruction2_loss should be normalized in one way or another. I didn't normalize it I guess because I didn't know what should I use for the normalization (whether the variance of the original input data or the latent vector).

hmm ok yeah, it might make sense to still use variance of the original data. i might give that i try. I can let you know if i see any performance differences. I suspect they will be minor.

I guess in practice we just need to estimate an approximate number that falls in the same order of magnitude of the real training variance (this may vary up to the dataset). And we don't need to calculate variance for val and test.

Yeah, I think I will just use one precomputed rough number as it makes things a lot faster and easier.
Thanks for all the input here, I'll let you know if I see anything important as I try things out!!


Implement remove_by_id on EntityWorldMut

What problem does this solve or what need does it fill?
We are able to insert type erased components via insert_by_id - I was expecting a similar api to be able to remove them.
What solution would you like?
What alternative(s) have you considered?
Additional context

Implemented here: https://github.com/bevyengine/bevy/issues/9261


Auto-scroll main menu to second item only on round screens

Previously, the main menu would auto-scroll to the second item on both round and square screens, causing the first item to be hidden on square screens.

This fixes the problem by only scrolling on round screens.

Hey, thanks for mentioning this, I only own round watches, so I couldn't find this bug. Sorry for this late reply, there was a lot to do, but I merged your commit now and will release this as soon as possible. :)


Deployment-modal warn users about swarm compatibility with docker node where he deploys #996

Missing translation

and changelog 😅


[Snyk] Security upgrade org.springframework.data:spring-data-jpa from 2.5.3 to 3.2.0

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

master/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

SQL Injection SNYK-JAVA-COMQUERYDSL-8400288
  177
org.springframework.data:spring-data-jpa:  2.5.3 -> 3.2.0 Major version upgrade Proof of Concept

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 SQL Injection

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: code/snyk check is complete. No issues have been found. (View Details)


Docs: Permalinks do not work

The platform which you're using to display documentation does not support permalinking. This is decently inconvenient.
Also, the documentation navigation sidebar is not properly responsive.

As mentioned elsewhere we are shifting to jsdoc documentation which does appear to allow permalinking.  You can view this documentation here.
Feel free to comment on issues you may have on that format.


More convenient skill buying

When you reach a step in the guide, where you need to buy gems ("highlight: hold omni key"). It highlights all the needed gems in the build and you should scroll to get all the needed gems.
It would be more convenient, that it would highlight gems, which are just needed for this step.
For example (I deleted part in leveling tracker.ahk, so it doesnt show highlight: hold omni key", but it shows what gems to buy on this step):

If it would work how I am showing in this example, it needs to highlight only Frost Bomb, Flame Wall, Orb of Storms and Steelskin.

The vendor highlights from within the guide do indeed work the way you're suggesting. I think you're somehow triggering the "Hideout Lilly" search-string. That's the one that includes every gem from the build.
I tried it with a build that only has many gems for Siosa, so feel free to send me your PoB code so that I can double-check that specific build as well.


docs: improve section on including other YAML files

I've cleaned up the docs a bit in the section on including other YAML files:

Some typo and spelling fixes
Use a code block title instead of inline YAML comment about the file path
Minor cosmetic/consistency improvements

Follow-up of #846 (specifically, 5d1e9c6c0a07ce86ccbe1e55d13e59f56199c947 respectively 12bd54239cff91140040b8ef592d66aabdc17386).

Codecov Report

Merging #853 (14be9e7) into master (12bd542) will decrease coverage by 0.80%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #853      +/-   ##
==========================================
- Coverage   96.58%   95.78%   -0.81%
==========================================
  Files          41       41
  Lines        2990     2990
==========================================
- Hits         2888     2864      -24
- Misses        102      126      +24

Flag
Coverage Δ

unittests
95.78% <ø> (-0.81%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

tests/test_tools.py
56.00% <0.00%> (-36.00%)
:arrow_down:

copier/tools.py
85.71% <0.00%> (-7.15%)
:arrow_down:

tests/test_vcs.py
94.91% <0.00%> (-5.09%)
:arrow_down:

tests/conftest.py
90.90% <0.00%> (-4.55%)
:arrow_down:

copier/subproject.py
95.12% <0.00%> (-2.44%)
:arrow_down:

copier/types.py
83.33% <0.00%> (-2.09%)
:arrow_down:

copier/template.py
95.79% <0.00%> (-0.47%)
:arrow_down:

copier/user_data.py
94.06% <0.00%> (-0.46%)
:arrow_down:

copier/main.py
94.03% <0.00%> (-0.29%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


1.21 support

Consider supporting 1.21, as it was officially launched a few days ago https://www.minecraft.net/en-us/article/minecraft-java-edition-1-21
Thanks for the mod!

yeah i should support 1.21. but ive been busy and will busy in next 5 days.

now supporting


Avoid markers that look like region tags

We use "region tags" to extract code samples for cloud.google.com, a region starts with [START $tag] and finishes with [END $tag] where $tag is the region tag name.  We use similar markers in other places:
https://github.com/googleapis/google-cloud-cpp/blob/0e3303aad95877f24b25a9523ba10e51d8f6075b/ci/generate-markdown/extract-install.sh#L21-L22
We should not. They work, but they confuse some of the tooling, such as the region tag bot.

How will this affect https://github.com/googleapis/google-cloud-cpp/issues/2356?

Separate issues I think.  #2356 is asking us to use the bigtable region tags for a README or some other document describing how to install the Bigtable client.  This bug is saying we should not use things that look like region tags for other purposes (e.g. extract from Docker files to .md files).

Fixed by https://github.com/googleapis/google-cloud-cpp/pull/5476


[feature]add xtrabackup manger

Is your feature request related to a problem? Please describe.

we need xtrabackup to cloud for the cluster
Describe the solution you'd like
None

Describe alternatives you've considered

Additional context

reference:
https://github.com/presslabs/mysql-operator/blob/master/docs/backups.md
issue:
https://github.com/presslabs/mysql-operator/issues?q=backup


Load FutureStates after Auth

I'm loading states based on the user who is logged in. I retrieve the relevant states from the backend and add them during config. However if the user is not logged in, I need to retry. The lifecycle of futureStates is not clear to me.
Is there a promise I can hook into if auth fails?
Or re-resolve states after an  "is-authed-event" fires.

Future states works by cancelling a state transition to a Future State, capturing that cancelled state transition, and retrying it later (after the future state factory has resolved the promise it returns).

A StateFactory is an injected factory function (using the runtime $injector). When invoked, the function is injected with a FutureState (using the camelCase variable name futureState). The function should process the FutureState and convert it into a full UI-Router state, or state tree. The function should return a promise which is resolved when the full UI-Router state is loaded.

I think that's the promise you want to hook into.


Fix post-merge conflicts

Addresses https://github.com/jazzband/pip-tools/pull/824#issuecomment-594512120.

@camilonova thanks!

@atugushev Thanks to you pal 🍺


smart_irrigation.reset_bucket doesn't reset zone id:0

What happened?
I wanted to reset the bucket of my zones one by one. Two of three zones were reseted, but not the one with id:0
service: smart_irrigation.reset_bucket
data: {}
target:
  entity_id:
    - sensor.bewasserung_wohnzimmer

What works is:
service: smart_irrigation.reset_all_buckets
data: {}

How to reproduce
Call the service: smart_irrigation.reset_bucket for zone id:0
Relevant log output
None

Which version are you running?
v2023.8.0-beta16
Diagnostics file

[X] I have attached a diagnostics file

Additional information
config_entry-smart_irrigation-6f22650b100cefed9d7411c48a4ba2b7.json.txt

fixed in beta 17

Yes, this bucket now also gets reset. :-)


Update sbt to 1.8.2

Updates org.scala-sbt:sbt from 1.8.0 to 1.8.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.8.0).
You might want to review and update them manually.
yarn.lock

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Codecov Report

Merging #703 (08936fc) into main (7007c0e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              main      #703    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           66        56    -10
  Lines         2861      1970   -891
  Branches       475       322   -153
==========================================
- Hits          2861      1970   -891

Impacted Files
Coverage Δ

packages/recheck/src/browser.ts

packages/recheck/src/lib/native.ts

packages/recheck/src/lib/env.ts

packages/recheck/src/lib/java.ts

packages/recheck/src/lib/exe.ts

packages/recheck/src/lib/pure.ts

packages/recheck/src/lib/agent.ts

packages/recheck/src/main.ts

...ges/eslint-plugin-redos/src/rules/no-vulnerable.ts

packages/recheck/src/lib/worker-pool.ts

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Unable to Set ArrayBuffer Value for Descriptor

Attempting to set the following descriptors fails on the second descriptor. This approach works flawlessly on Linux, assuming something is getting lost in translation for the second descriptors arraybuffer
descriptors: [
                new Descriptor({
                    uuid: '2901',
                    value: Buffer.from('Volume', 'utf8')
                }),
                new Descriptor({
                    uuid: '2904', // https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.descriptor.gatt.characteristic_presentation_format.xml
                    value: new Buffer([
                        0x04, // Uint8 0-255 value is allowed (numeric keypad)
                        0x00, // no exponent (value === value)
                        0x27, 0x25, // https://www.bluetooth.com/specifications/assigned-numbers/units joules (energy)
                        0x01, // Bluetooth SIG Assigned Numbers
                        0x00, // No description
                        0x00])
                })
            ]

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Expecting NSData value type for Format descriptor'

@notjosh might this be related to xpc-connection? it looks like https://github.com/jongear/xpc-connect is more up to date.


The performances when using ReCoSa

Hi, Thank you for publishing this great repository.
I opened this issue because I want to ask a question to you.
I'm currently trying to implement a multi-turn dialogue generation task using ReCoSa structure.
I coded the entire structure by referring the paper and I combined 4 datasets, DailyDialog, PersonaChat, EmpatheticDialogue and BlendedSkillTalk.
But after training, I have not been able to get satisfactory results since it makes the outputs with no meaning or severely repetitive words in the inference step.
I've been trying to improve it by changing the hyperparameter setting several times and training again and gain, but I still can't get good results.
I want to know why mine is not working...maybe due to wrong hyperparameter settings, problems with implementation itself, or lack of data...
The most likely problem to me at this moment is the sequence length since I've set it very long at 300, so I think there will be difficulties in encoding an utterance but I'm not sure.
So I wonder if you got decent qualities with ReCoSa model, not the automatic scores but the actual engaging conversations. (even if your structure seems slightly different from the original version in the paper...)
As I look at your codes, my model has bigger dimensions and complexity, but I don't think this is the cause since even the overfitting is not happening.
Please tell me what your results looked like. That will be really grateful.
Thank you.

Hi, thank you for your attention on my work. I think you can find two repos on the GitHub which contains the ReCoSa model. The first is the author's, which is written by the tensorflow, the other is mine. Before I re-implement my version of the ReCoSa, I try to run the original version, but it occur the same issue as yours. After carefully analyzing the structure of the ReCoSa, I think it's about the Transformer decode. After I replace the transformer masked decoder with the standard RNN (GRU) decoder, the performance seems fine. I recommand that you can try to change the structure of the ReCoSa on the fly.
If you have any issues, feel free to contact with me.
| |
GMFTBY
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 10/28/2020 14:18，Jaewoo<EMAIL_ADDRESS>wrote：
Hi, Thank you for publishing this great repository.
I opened this issue because I want to ask a question to you.
I'm currently trying to implement a multi-turn dialogue generation task using ReCoSa structure.
I coded the entire structure by referring the paper and I combined 4 datasets, DailyDialog, PersonaChat, EmpatheticDialogue and BlendedSkillTalk.
But after training, I have not been able to get satisfactory results since it makes the outputs with no meaning or severely repetitive words in the inference step.
I've been trying to improve it by changing the hyperparameter setting several times and training again and gain, but I still can't get good results.
I want to know why mine is not working...maybe due to wrong hyperparameter settings, problems with implementation itself, or lack of data...
The most likely problem to me at this moment is the sequence length since I've set it very long at 300, so I think there will be difficulties in encoding an utterance but I'm not sure.
So I wonder if you got decent qualities with ReCoSa model, not the automatic scores but the actual engaging conversations. (even if your structure seems slightly different from the original version in the paper...)
As I look at your codes, my model has bigger dimensions and complexity, but I don't think this is the cause since even the overfitting is not happening.
Please tell me what your results looked like. That will be really grateful.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Oh, that is not what I have thought about.
I will look into that!
Thank you very much.


Generate extension list automatically from the JSON grammar file.

Closing in favour of #583 which is already assigned.


Intellisense support in 'this' keyword inside an object.

Hi, maybe this is a bug but is not showing any intellisense regarding with the current object.
TypeScript Version:  1.8.0
Code
interface Person {
    name : string;
    lastName : string;
    age: number;

    greet() : string;
}

var People : Person[] = [{
    name : "Santi",
    lastName : "Aguilar",
    age : 21,
    greet : function(){
        return this.name;
    }
}]

Expected behavior:
Offer intellisense for the current object (this)
Actual behavior:

We experimented with inferring the type of this by the surrounding object, but because it broke a lot of existing code (see #8191).
You can add an explicit this type in each method in TypeScript 2.0 (check our nightlies with npm install -g typescript@next):
var People : Person[] = [{
    name : "Santi",
    lastName : "Aguilar",
    age : 21,
    // Notice 'this: Person'
    greet : function(this: person) {
        return this.name;
    }
}]

Alternatively, you can add this: this to each method on the Person interface and implicitly have it work:
interface Person {
    name : string;
    lastName : string;
    age: number;

    greet(this: this) : string;
}

var People : Person[] = [{
    name : "Santi",
    lastName : "Aguilar",
    age : 21,
    greet : function() {
        return this.name;
    }
}]

If you ever want to avoid this being typed as any, we've also provided the --noImplicitThis flag, which gives an error when you used this and the type is not inferrable.

Thank you for your answer @DanielRosenwasser :smile:

See #14141.


July Blog Post

added blog post and images

@jancborchardt @m1guelpf @evalica  can you please approve my changes :)

@jancborchardt @m1guelpf @evalica please approve my image fixes, thank you!

Your blog posts are always great @dmichl! :tada:


vscode-eslint fails to load eslint-plugin with entry point other than /index.js and not dot-prefixed

I just tried to load this plugin: https://github.com/SebastienGllmt/eslint-plugin-no-floating-promise
with eslint and vscode-eslint.
The package specifies it's entry point with "main": "lib/index.js"
Command line eslint works. vscode-eslint fails
Changing the entry point to "main": "./lib/index.js" fixes the problem. So, it appears that vscode-eslint fails without a ./
Seems to be a fairly common practice, so it would seem that vscode-eslint should accept it.
(node:15988) UnhandledPromiseRejectionWarning: Error: Failed to load plugin 'eslint-plugin-promise' declared in '.eslintrc.json': Cannot find module 'eslint-plugin-promise'
Require stack:
- AppLocation\.eslintrc.json
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:934:15)
    at Function.resolve (internal/modules/cjs/helpers.js:94:19)
    at Object.resolve (AppLocation\node_modules\@eslint\eslintrc\lib\shared\relative-module-resolver.js:28:50)
    at Object.ModuleResolver.resolve (AppLocation\node_modules\@rushstack\eslint-patch\lib\modern-module-resolution.js:148:44)
    at ConfigArrayFactory._loadPlugin (AppLocation\node_modules\@eslint\eslintrc\lib\config-array-factory.js:1017:39)
    at ConfigArrayFactory._loadPlugin (AppLocation\node_modules\@rushstack\eslint-patch\lib\modern-module-resolution.js:150:43)
    at AppLocation\node_modules\@eslint\eslintrc\lib\config-array-factory.js:908:33
    at Array.reduce (<anonymous>)
    at ConfigArrayFactory._loadPlugins (AppLocation\node_modules\@eslint\eslintrc\lib\config-array-factory.js:904:22)
    at ConfigArrayFactory._normalizeObjectConfigDataBody (AppLocation\node_modules\@eslint\eslintrc\lib\config-array-factory.js:725:44)
(node:15988) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 591)

It started working later on. I don't know what the issue was...
I made a variant with './lib/index.js' and that seems to work but with errors. Then the original started working. Mystery

I suspect this had something to do with the caching, which I wasn't aware of at the time.


🦸 RHEL 8.3: Switch to production CDN URL

Use the production CDN URL now that RHEL 8.3 beta content is available.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

☝🏻 REMINDER: Remove the RHN registration steps from cloud-init for the RHEL 8.3 instances (in Jenkins managed files configuration) when this has merged!.


Allow a nonce to be set on single fetch stream transfer inline scripts

Closes: #9359

[x] Docs
[ ] Tests - not sure of the best approach to add tests for this. I looked at adding one to packages/remix-react/__tests__/components-test.tsx but it requires setting a context.serverHandoffStream which seems non-trivial? Is there a better approach?

Testing Strategy:
I patched @remix-run/react in our application with these changes and saw that it fixed our CSP violations.

Thanks!
Yeah this stuff is best tested through our E2E tests - want to try something like this in integration/single-fetch-test.ts?
You can run it with pnpm test:integration single-fetch --project chromium
  test("supports nonce on streaming script tags", async ({ page }) => {
    let fixture = await createFixture({
      config: {
        future: {
          unstable_singleFetch: true,
        },
      },
      files: {
        ...files,
        "app/entry.server.tsx": js`
          import { PassThrough } from "node:stream";

          import type { EntryContext } from "@remix-run/node";
          import { createReadableStreamFromReadable } from "@remix-run/node";
          import { RemixServer } from "@remix-run/react";
          import { renderToPipeableStream } from "react-dom/server";

          export default function handleRequest(
            request: Request,
            responseStatusCode: number,
            responseHeaders: Headers,
            remixContext: EntryContext
          ) {
            return new Promise((resolve, reject) => {
              const { pipe } = renderToPipeableStream(
                <RemixServer context={remixContext} url={request.url} nonce="the-nonce" />,
                {
                  onShellReady() {
                    const body = new PassThrough();
                    const stream = createReadableStreamFromReadable(body);
                    responseHeaders.set("Content-Type", "text/html");
                    resolve(
                      new Response(stream, {
                        headers: responseHeaders,
                        status: responseStatusCode,
                      })
                    );
                    pipe(body);
                  },
                  onShellError(error: unknown) {
                    reject(error);
                  },
                  onError(error: unknown) {
                    responseStatusCode = 500;
                  },
                }
              );
            });
          }
        `,
      },
    });
    let appFixture = await createAppFixture(fixture);
    let app = new PlaywrightFixture(appFixture, page);
    await app.goto("/data", true);
    let scripts = await page.$$("script");
    expect(scripts.length).toBe(6);
    for (let s of scripts) {
      // Do nonce expect() calls here for the scripts that should have it - which I think might just be
      // any with `window.__remixContext.streamController` in the innterHTML?
      console.log(await s.getAttribute("nonce"), await s.innerHTML());
    }
  });


Ample-Zen

Describe your request
Hi,
I use Ample-Zen since ages in vanilla Emacs and I loved it.
I recently switched to DoomEmacs (because I'm tired of managing my 2000+ lines of config.org and getting half-backed results).
I've consult'ed all the Doom themes. Unfortunately, I couldn't find one that suits my needs (org, and many languages : R/Python/Java/Dart/Rust/...):

I can't use a "light" themes anymore as they burn my eyes
Most of the Dark themes make org's #+TITLE (and other stuff like comments) almost the same color as the background, thus unreadable
The other ones have nice backgrounds, but too colorful keywords... Thus reading any code in them also burn my eyes.

I'm very bad at lisp/design/colors/etc. Would it be difficult to convert a vanilla Emacs theme like AmpleZen to Doom?
NOTE: I'm publish here as last change in https://github.com/mjwall/ample-zen/issues/4 dates back 9 years :{
Resources
https://github.com/mjwall/ample-zen

You should be able to use that theme in doom, your not limited to just the doom themes, you would install it like any other package and then just the Doom theme variable to that theme. That being said if you can get the colours out of the theme then it should be relatively trivial to convert

I can't use a "light" themes anymore as they burn my eyes

Amen, brother.

Most of the Dark themes make org's #+TITLE (and other stuff like comments) almost the same color as the background, thus unreadable

Most of doom's themes have a doom-NAME-brighter-comments variable. Like doom-one has doom-one-brighter-comments. With (setq doom-one-brighter-comments), the comment colors will have more contrast.

The other ones have nice backgrounds, but too colorful keywords... Thus reading any code in them also burn my eyes.

Emacs themes are easily customizable. Start with any theme as a baseline, then use the custom-set-faces macro to tweak whatever you want about them.
If you're using Doom Emacs, use the custom-set-faces! macro instead:
(custom-set-faces! `(font-lock-comment-face :foreground "red"))

More examples of its use with C-h f custom-set-faces\! (or M-x helpful-function RET custom-set-faces\!).
You can look up faces with C-h F (M-x describe-face).

Would it be difficult to convert a vanilla Emacs theme like AmpleZen to Doom?

It'd be a simple matter of copying one of our other themes (I'd recommend doom-one, as it's the most fleshed out), and substituting the colors at the top with AmpleZen.

Anyhow, in the future, please redirect questions like these to our Discourse, as our issue tracker is for bug reports and feature requests.


Rename?

I've never seen the nixify prefix used to describe Nix packaging repo names.
Maybe ollama-nix
If this project ends up doing more than packaging ollama, we might even give it an unique name, like https://github.com/tweag/jupyenv

I am okay with ollama-nix for now

perhaps even ollama-flake


Enable webview tests on remote as well

Testing these tests in CI. These tests pass locally for me but were previously unreliably in CI

Merging this since it passed in CI. Will make sure it passes the full build as well


Closing the last editor should move focus back to explorer view

Issue Type: Bug
Open a  file.
Close it using ctrl+F4.
The focus doesn't come again to the closed file.
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.91GB (2.92GB free)

Process Argv
--crash-reporter-id 3673b813-712f-4de4-aae0-a658c8663e0e

Screen Reader
yes

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.10

java
red
0.68.0

sonarlint-vscode
Son
1.17.0

vscodeintellicode
Vis
1.2.10

vscode-java-debug
vsc
0.28.0

vscode-java-dependency
vsc
0.13.0

vscode-java-pack
vsc
0.10.0

vscode-java-test
vsc
0.24.2

vscode-maven
vsc
0.24.2

I don't understand the issue here, when you close a file why should it focus it again?

Hi @bpasero
Thanks for commenting.
There might be other files as well in the file explorer tree.
Now, If I want to access them, I always have to close the file, navigate to the entire tree using keyboard, and then open it.
As I am a keyboard+screen reader user, If my focus gets to the closed file, then I can navigate around the siblings/childrens/parent files in the file explorer tree.

E.G.
I have a tree/directory  structure like this:
Project(folder)
Project folder contains a folder "sub Project".
The "sub project" folder has 2 files.
"HelloWorld" and "HelloGithub".
If I Open "HelloWorld", and close it again, my focus should go to "HelloWorld".
The same doesn't happen now.
I all the way have to navigate this entire tree/directory to access "HelloGithub".

@gauravahir28 thanks for providing feedback and sorry for the slow response I was on vacation.
So if you open both "HelloWorld" and "HelloGithub" then closing either one of them will focus the other one.
However if you open only one, we do not automatically open another file. That would be unexpeceted for most users.
If you wanted to open both, but did not maybe try changing this setting
"workbench.editor.enablePreview": false

Hay @isidorn I guess I couldn't able to explain my issue.
Let me try again.
As you said in your comment, I don't want to open file explicitly.
My focus should be set to that file so that, I can press enter to open that file.
e.g.
If I open "Hello World", An if I close it again, my focus should be set to the title of that file in the file explorer tree  so that, I can navigate using down/up arrow in the file explorer tree and open the file using enter.
For now, If I close the file, my focus gets lost from the file explorer tree.

I understand. So the gist you:
You want focus to move from editor area back to explorer when the last editor is closed.
This is a fair request, however we would not add it right now since it would break how users are used to focus in vscode. We rarely magically move focus around, since that would be unexpected for most users. Though I do understand your scenario.

I really wish you would consider implementing this. I find it really annoying when I close the last editor and I am just stuck in an empty group. I have to move my focus back to the Explorer. I am also a blind screen reader user. VS Code has some powerful settings, why not add a setting for this?
Thanks.


adjust warnings for 2DAR

Concisely describe what has been changed/addressed in the pull request.

Find that the rho feature of 2DAR was incompletely implemented and a full fix is not feasible at this time.  Provide new warnings and guidance to users.

Resolves issue #615

What tests have been done?
Numerous runs with various permutations of estimating or fixing age-specific sigmasel values using hake 2DAR example.
Where are the relevant files?

What tests/review still need to be done?
none
Is there an input change for users to Stock Synthesis?

Additional information (optional).

@e-perl-NOAA   Please reflect these revised warnings into the manual.


Plugins: [react()] in defineConfig cause error Type 'PluginOption[]' is not assignable to type 'PluginOption'.

Describe the bug
i have vite.config.ts initially includes plugin: [react()]
but when i change it to use defineConfig from vitest/config
it shows squiggle error:
Type 'PluginOption[]' is not assignable to type 'PluginOption'.

Reproduction
create vite app with react + SWC
install vitest,
change the import from  "vite" to "vitest/config"
/// <reference types="vitest" />
import react from "@vitejs/plugin-react-swc";
import { configDefaults, defineConfig } from "vitest/config";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  server: {
    port: 3000,
  },
  base: "/order",
  build: {
    outDir: "./build",
  },
  resolve: {
    alias: {
      "@src": "/src",
    },
  },
});

System Info
"@vitejs/plugin-react-swc": "^3.3.2",
    "vite": "^4.4.5",
    "vitest": "^0.34.1",

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Your package manager resolved your global Vite and Vitest Vite to different versions. Check your lockfile and resolve it.

ok thanks, ill look into it
but i wonder why its happened in the first place? its a fresh create vite app and vitest setup

hi @sheremet-va , i haven't look into resolving the version
but instead i split the config into vite.config.ts and vitest.config.ts
with this i wont type error (because defineConfig are different for test and vite config)
is this approach alright?

// vite.config.ts
import react from "@vitejs/plugin-react-swc";
import { defineConfig } from "vite";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  server: {
    port: 3000,
  },
  ....
});

// vitest.config.ts
/// <reference types="vitest" />
import { configDefaults, defineConfig } from "vitest/config";

// https://vitejs.dev/config/
export default defineConfig({
  test: {
    //... some test config...
  },
});

is this approach alright?

Vitest config doesn't inherit Vite config, so you will need to merge it yourself.

Just ran into this myself. In my case it was due to having vitest installed at the root of our monorepo and trying to install @vitejs/plugin-react inside one of the packages. Hoisting @vitejs/plugin-react to the root as well fixed the issue.

I get the same error on:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
The error disappear if i downgrade to:

<EMAIL_ADDRESS>
I do not have vite in package.json. I'm on a Next Js app.
Thanks!

I avoided the warning this way.
/// <reference types="vitest" />

import react from "@vitejs/plugin-react";
import { UserConfig, defineConfig } from "vitest/config";

export default defineConfig({
  plugins: [react()] as UserConfig["plugins"],
  ...
});

This issue is always cause by the package manager installing different versions of Vite package. Make sure there are no multiple versions installed by running dedupe command for example (in pnpm it is pnpm dedupe). On Vitest side we cannot do anything unfortunately.


Add SSL context support to UrlConnectionHttpClient

Add the following capability to UrlConnectionHttpClient,

An ability to insert SSLSocket (needed for DRS requests)
UrlConnectionHttpClient now supports Higher TLS by default, regardless of Android API version. (Please see the added test case).

Also remove the adapter classes, since we're going for a breaking change in the next release.
This, of course, introduces a breaking change, I'll send PR for those later.

TLS1 and TLS1.1 test are failing because... the pipeline doesn't support such connection
it's either the JVM itself, or there are something else that blocks it - still have no clue.
javax.net.ssl.SSLHandshakeException: The server selected protocol version TLS11 is not accepted by client preferences [TLS13, TLS12, SSL20Hello]

rebased dev.


Add lftp box part #261

I didn't realize I could make my own box part until this morning. Here's a pull request for the feature I requested.

Thank you.


Validation fixes

Category

[x ] Content fix

Docs Build status updates of commit b32917b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/scenario-guidance/Development-models.md
:warning:Warning
View
Details

docs/schema/_authsubmissionpath-element-formsauthcredentials-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_cookies-element-cookieauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_namevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_namevaluepairs-element-ssoauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_securablenamevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_ssoappid-element-ssoauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/scenario-guidance/Development-models.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_authsubmissionpath-element-formsauthcredentials-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_cookies-element-cookieauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Outlines information, a definition, and elements and attributes for the _ErrorPageUrl element in Sharepoint.' is duplicated in 'schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md(3,14)', 'schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md(3,14)'.

docs/schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Outlines information, a definition, and elements and attributes for the _ErrorPageUrl element in Sharepoint.' is duplicated in 'schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md(3,14)', 'schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md(3,14)'.

docs/schema/_namevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_namevaluepairs-element-ssoauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_securablenamevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_ssoappid-element-ssoauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1edee51:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/scenario-guidance/Development-models.md
:warning:Warning
View
Details

docs/schema/_authsubmissionpath-element-formsauthcredentials-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_cookies-element-cookieauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_namevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_namevaluepairs-element-ssoauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_securablenamevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/_ssoappid-element-ssoauthdata-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/scenario-guidance/Development-models.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_authsubmissionpath-element-formsauthcredentials-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_cookies-element-cookieauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_errorpageurl-element-cookieauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_errorpageurl-element-formsauthcredentials-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_namevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_namevaluepairs-element-ssoauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_securablenamevaluepairs-element-securableauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/_ssoappid-element-ssoauthdata-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
@VesaJuvonen
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


podman stats is incompatible with Docker

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman stats requires containers to be specified while docker stats shows all running containers by default.
Also, the man page describes the behavior of Docker, not the current behavior of Podman.
https://github.com/containers/libpod/blob/7e238b9e0c650b20f1a325dad14ef94a3e7d1aab/docs/podman-stats.1.md
Steps to reproduce the issue:
podman stats
Describe the results you received:
Error: you must provide at least one name or id
https://github.com/containers/libpod/blob/5f72e6ef2ef7b6941cefc3c655903aeacb53e115/cmd/podman/stats.go#L48
https://github.com/containers/libpod/blob/fd389d28ce2223550c82d809cbafa12a54e733e6/cmd/podman/common.go#L43-L63
Describe the results you expected:
Should show all running containers as in docker stats
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version: 1.6.1
...

Thanks for opening the issue, @AkihiroSuda. I opened https://github.com/containers/libpod/pull/4275 to fix it.


[Extension] Build tooling for different browsers

We need something similar to what https://github.com/webextension-toolbox/webextension-toolbox is offering, minus the webpack stuff.

:tada: This issue has been resolved in version 3.31.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Issue 56 deployment env config

Issue: https://github.com/My-DIGI-ID/aries-cloudagent-loadgenerator/issues/56

Locally tested network in different setup


[html][emmet] Emmet Backspace Issue

VSCode Version:1.16
OS Version: OSX 10.12.6

Steps to Reproduce:

Open and save an html file
Write "select[name=foo]>option[value=bar$]*2"
TAB it to autocomplete with emmet
Undo with STRG+Z
Delete the last 2 characters "*2"
TAB again
Nothing happens
Delete the last "]" then replace it with a freshly typed "]"
TAB again and it works again

It would be great if emmet is still recognized after deleting the code after an undo. Sometimes you have to adjust the emmet snippets and the issue described above is slightly annoying. Thanks!

Reproduces without extensions: Yes/No

Pressing tab accepts the first suggestion in the suggestion list if the suggestion list is present.
Suggestion list appears when you type or when you manually invoke it using Ctrl+Space
This is the general behavior of suggestions/auto-complete in VS Code
This is what is happening in your Step 3 and 9
In Step 6, when you press tab there is no suggestion list
Your options

Hit Ctrl+Space to trigger suggestions -> you will see emmet in the suggestions -> press tab to accept the suggestion
Or you can set emmet.triggerExpansionOnTab to true. This will trigger Emmet on tab when suggestion list is absent.


Deprecate :commandline: plugin

Right now the extensions commandline_highlight.py and customwriter.py are semi-broken. We might as well remove all instances where we use it until we get the code to a working condition. So far we've affected sysadmin.rst and openldap.rst

Specifically commits https://github.com/remyabel/angels-of-clockwork/commit/ba1b676811cbd38808c1201a85924445f1976145 and https://github.com/remyabel/angels-of-clockwork/commit/eb09bd2f855e521190c737dd578bbd852ff4e63c


Hydra's webkit-gtk is a cache-miss for anyone with nixpkgs.config.pulseaudio enabled...

Describe the bug
Synopsis:
I'm having to constantly rebuild webkit gtk, I asked in Matrix and Sushi Dude informed me:
From IRC
Sushi Dude
nixpkgs.config.pulseaudio = true; requires building libopenmpt from source which gst_all_1.gst-plugins-bad depends on which webkitgtk depends on. https://github.com/NixOS/nixpkgs/pull/136735

colemickens 🏳🌈
I guess I do see that, but what has changed exactly? that just looks like a rename?
And yes, you hit the nail on the head, I've been seeing libopenmpt building too and wondering what that was all about

Sushi Dude
libopenmpt is dependent on that config option and that pull request added libopenmpt as a dependency to gst_all_1.gst-plugins-bad.

colemickens 🏳🌈
oh oh oh okay, I see.
yeesh, do we have an issue for this? even just as an fyi?
(not trying to sign you up necessarily, and I really appreciate you chiming in!)

Sushi Dude
The package variants that nixpkgs.config options produce should be cached, but they are not.

colemickens 🏳🌈
So, I guess this is the first time anyone's noticed that a browser output depends on a nixpkgs.config ?
But that doesn't seem right, wouldn't one of the other browser packages have fallen into this trap before and caused complaints from users?

Steps To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
We should be building and caching builds of webkit that users are likely encountering.
My question is --

how have we never hit this before?
Why do we not cache packages built with this config that desktop users are likely to employ (similarly, why bother building browsers and caching them that don't have pulseaudio enabled)?

This feels like it maps to a more generic issue:
Many things are built with: pulseSupport = config.pulseaudio or true but also many things are built with pulseSupport = config.pulseaudio or false.
The point being, if a user has set nixpkgs.config.pulseaudio they override the default (and thus cached) result for some number of packages.
When https://github.com/NixOS/nixpkgs/pull/136735 was merged, it included this as a new input for libopenmpt:
, usePulseAudio ? config.pulseaudio or false
Thus, any user that had config.pulseaudio = true set, will start having to build libopenmpt and its dependents (including webkit-gtk) from source.
Quick thoughts:

We should have a policy for what this defaults to.
We could consider just removing this option (because what, are we going to add another global option for pipewire, etc?) (though I realize this will be a tough sell, some folks are probably happy to be able to disable this)

Since this is the first time I'm noticing this, I'm making assuming that every other dependency of the browsers I've ever used must have been built with pulseSupport = config.pulseaudio or (something that evals to true). Otherwise I would've been experiencing rebuilds for a long time.
Thus, I think we should change libopenmpt to act similarly so that Hydra is building more in line with other pkgs in nixpkgs that seem to err on the side of supporting pulseaudio (when targetting linux).

I'm very much in favor of completely removing this option. I don't see any reason for why you'd set it to false.