ToDo: diffs FF76-FF77

FF77 is scheduled for release June 2nd
FF77 release notes [when ready]
FF77 for developers
FF77 compatibility
FF77 security advisories

other in v77

[ ] update wiki re CSP
[ ] 2701: dFPI option

109 diffs ( 58 new, 33 gone, 18 different )
new in v77.0:

[x] pref("dom.security.https_only_mode.upgrade_local", false); - https://github.com/ghacksuserjs/ghacks-user.js/commit/f69d92e6ddc4c855686601caa391fda5a953ebaa

removed, renamed or hidden in  v77.0:
ALL DONE - https://github.com/ghacksuserjs/ghacks-user.js/commit/f6e6de844430fa64440ae230061720839e8282be

[x] 0850e pref("browser.urlbar.oneOffSearches", true); - 1628926
[x] 2605 pref("browser.tabs.remote.allowLinkedWebInFileUriProcess", false); - 1603007

changed in  v77.0:

[ ] pref("dom.quotaManager.useDOSDevicePathSyntax", true); // prev: false
[ ] re: link history timing attacks

pref("layout.css.always-repaint-on-unvisited", true); // prev: false
pref("layout.css.notify-of-unvisited", true); // prev: false

ignore
click me for details
==NEW

pref("accessibility.ARIAReflection.enabled", false);
pref("apz.windows.force_disable_direct_manipulation", true);
pref("browser.find.anonymous_content.enabled", true);
pref("browser.newtabpage.activity-stream.asrouter.providers.messaging-experiments", "{\"id\":\"messaging-experiments\",\"enabled\":true,\"type\":\"remote-experiments\",\"messageGroups\":[\"cfr\",\"whats-new-panel\",\"moments-page\",\"snippets\",\"cfr-fxa\"],\"updateCycleInMs\":3600000}");
pref("browser.tabs.documentchannel.parent-initiated", true);
pref("browser.tabs.documentchannel.ppdc", true);
pref("browser.urlbar.restyleSearches", false);
pref("devtools.contenttoolbox.webconsole.input.context", false);
pref("devtools.debugger.features.frame-step", true);
pref("devtools.experiment.f12.shortcut_disabled", false);
pref("devtools.inspector.compatibility.target-browsers", "");
pref("dom.security.https_only_mode.upgrade_onion", false);
pref("dom.security.https_only_mode_ever_enabled", false);
pref("dom.window.content.untrusted.enabled", true);
pref("editor.truncate_user_pastes", false);
pref("extensions.blocklist.addonItemURL", "https://addons.mozilla.org/%LOCALE%/%APP%/blocked-addon/%addonID%/%addonVersion%/");
pref("extensions.blocklist.useMLBF", false);
pref("extensions.blocklist.useMLBF.stashes", false);
pref("gfx.vsync.force-disable-waitforvblank", false);
pref("gfx.webrender.gl-debug-message-critical-note", false);
pref("gfx.webrender.gl-debug-message-print", false);
pref("gfx.webrender.use-optimized-shaders", true);
pref("identity.sync.useOAuthForSyncToken", false);
pref("image.avif.enabled", false);
pref("image.honor_orientation_metadata.natural_size", true);
pref("image.honor-orientation-metadata", true);
pref("javascript.options.mem.gc_high_frequency_large_heap_growth", 150);
pref("javascript.options.mem.gc_high_frequency_small_heap_growth", 300);
pref("javascript.options.mem.gc_large_heap_incremental_limit", 110);
pref("javascript.options.mem.gc_large_heap_size_min_mb", 500);
pref("javascript.options.mem.gc_small_heap_incremental_limit", 140);
pref("javascript.options.mem.gc_small_heap_size_max_mb", 100);
pref("javascript.options.wasm_reftypes", true);
pref("layout.css.grid-template-masonry-value.enabled", false);
pref("layout.css.is-where-selectors.enabled", false);
pref("media.getdisplaymedia.enabled", true);
pref("media.testing-only-events", false);
pref("network.data.max-uri-length-mobile", 2097152);
pref("pdfjs.enablePermissions", false);
pref("privacy.restrict3rdpartystorage.expiration_visited", 2592000);
pref("privacy.restrict3rdpartystorage.heuristic.recently_visited", true);
pref("privacy.restrict3rdpartystorage.heuristic.recently_visited_time", 600);
pref("privacy.trackingprotection.testing.report_blocked_node", false);
pref("privacy.webrtc.allowSilencingNotifications", false);
pref("privacy.webrtc.legacyGlobalIndicator", true);
pref("privacy.webrtc.sharedTabWarning", false);
pref("prompts.defaultModalType", 3);
pref("prompts.modalType.confirmAuth", 2);
pref("prompts.modalType.insecureFormSubmit", 2);
pref("services.blocklist.addons-mlbf.checked", 0);
pref("services.blocklist.addons-mlbf.collection", "addons-bloomfilters");
pref("services.blocklist.addons-mlbf.signer", "remote-settings.content-signature.mozilla.org");
pref("services.sync.prefs.sync.intl.regional_prefs.use_os_locales", true);
pref("signon.showAutoCompleteImport", "");
pref("toolkit.asyncshutdown.report_writes_after", 20000);
pref("toolkit.osKeyStore.loglevel", "Warn");
pref("webgl.prototype.ipc-pcq", 0);

==REMOVED or HIDDEN
pref("apz.frame_delay.enabled", true);
pref("browser.aboutwelcome.log", "warn");
pref("browser.fixup.dns_first_for_single_words", false);
pref("browser.fixup.typo.scheme", true);
pref("browser.osKeyStore.loglevel", "Warn");
pref("browser.stopReloadAnimation.enabled", true);
pref("browser.tabs.multiselect", true);
pref("browser.tabs.showAudioPlayingIcon", true);
pref("browser.ui.scroll-toolbar-threshold", 10);
pref("browser.urlbar.update1", true);
pref("browser.urlbar.update1.view.stripHttps", true);
pref("browser.xul.error_pages.enabled", true);
pref("devtools.debugger.source-maps-enabled", true);
pref("devtools.inspector.use-new-box-model-highlighter", false);
pref("dom.mozBrowserFramesEnabled", true);
pref("dom.registerProtocolHandler.insecure.enabled", false);
pref("extensions.webservice.discoverURL", "https://discovery.addons.mozilla.org/%LOCALE%/firefox/discovery/pane/%VERSION%/%OS%/%COMPATIBILITY_MODE%");
pref("gfx.vsync.use-waitforvblank", false);
pref("javascript.options.mem.gc_avoid_interrupt_factor", 100);
pref("javascript.options.mem.gc_dynamic_heap_growth", true);
pref("javascript.options.mem.gc_dynamic_mark_slice", true);
pref("javascript.options.mem.gc_high_frequency_heap_growth_max", 300);
pref("javascript.options.mem.gc_high_frequency_heap_growth_min", 150);
pref("javascript.options.mem.gc_high_frequency_high_limit_mb", 500);
pref("javascript.options.mem.gc_high_frequency_low_limit_mb", 100);
pref("javascript.options.mem.gc_non_incremental_factor", 112);
pref("layout.css.contain.enabled", true);
pref("network.disable.ipc.security", true);
pref("privacy.purge_trackers.logging.enabled", false);
pref("security.identityblock.show_extended_validation", false);
pref("signon.management.overrideURI", "about:logins?filter=%DOMAIN%");

==CHANGED
pref("browser.contentblocking.report.monitor.how_it_works.url", "https://monitor.firefox.com/about"); // prev: "https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/monitor-faq"
pref("browser.newtabpage.activity-stream.asrouter.providers.message-groups", "{\"id\":\"message-groups\",\"enabled\":false,\"type\":\"remote-settings\",\"bucket\":\"message-groups\",\"updateCycleInMs\":3600000}"); // prev: "{\"id\":\"message-groups\",\"enabled\":true,\"type\":\"remote-settings\",\"bucket\":\"message-groups\",\"updateCycleInMs\":3600000}"
pref("browser.safebrowsing.provider.google.reportURL", "https://safebrowsing.google.com/safebrowsing/diagnostic?site="); // prev: "https://safebrowsing.google.com/safebrowsing/diagnostic?client=%NAME%&site="
pref("browser.safebrowsing.provider.google4.reportURL", "https://safebrowsing.google.com/safebrowsing/diagnostic?site="); // prev: "https://safebrowsing.google.com/safebrowsing/diagnostic?client=%NAME%&site="
pref("browser.tabs.remote.separatePrivilegedContentProcess", true); // prev: false
pref("browser.urlbar.maxCharsForSearchSuggestions", 100); // prev: 20
pref("devtools.netmonitor.columnsData", "[{\"name\":\"status\",\"minWidth\":30,\"width\":5}, {\"name\":\"method\",\"minWidth\":30,\"width\":5}, {\"name\":\"domain\",\"minWidth\":30,\"width\":10}, {\"name\":\"file\",\"minWidth\":30,\"width\":25}, {\"name\":\"url\",\"minWidth\":30,\"width\":25},{\"name\":\"initiator\",\"minWidth\":30,\"width\":10},{\"name\":\"type\",\"minWidth\":30,\"width\":5},{\"name\":\"transferred\",\"minWidth\":30,\"width\":10},{\"name\":\"contentSize\",\"minWidth\":30,\"width\":5},{\"name\":\"waterfall\",\"minWidth\":150,\"width\":15}]"); // prev: "[{\"name\":\"status\",\"minWidth\":30,\"width\":5}, {\"name\":\"method\",\"minWidth\":30,\"width\":5}, {\"name\":\"domain\",\"minWidth\":30,\"width\":10}, {\"name\":\"file\",\"minWidth\":30,\"width\":25}, {\"name\":\"url\",\"minWidth\":30,\"width\":25}, {\"name\":\"cause\",\"minWidth\":30,\"width\":10},{\"name\":\"initiator\",\"minWidth\":30,\"width\":10},{\"name\":\"type\",\"minWidth\":30,\"width\":5},{\"name\":\"transferred\",\"minWidth\":30,\"width\":10},{\"name\":\"contentSize\",\"minWidth\":30,\"width\":5},{\"name\":\"waterfall\",\"minWidth\":150,\"width\":15}]"
pref("devtools.netmonitor.visibleColumns", "[\"status\",\"method\",\"domain\",\"file\",\"initiator\",\"type\",\"transferred\",\"contentSize\",\"waterfall\"]"); // prev: "[\"status\",\"method\",\"domain\",\"file\",\"cause\",\"type\",\"transferred\",\"contentSize\",\"waterfall\"]"
pref("gfx.omta.background-color", true); // prev: false
pref("gfx.webrender.enable-item-cache", true); // prev: false
pref("layout.css.image-orientation.initial-from-image", true); // prev: false
pref("network.auth.confirmAuth.enabled", true); // prev: false
pref("network.http.http3.default-qpack-table-size", 0); // prev: 65536
pref("privacy.purge_trackers.logging.level", "Error"); // prev: "Warn"
pref("signon.management.page.os-auth.enabled", false); // prev: true

some bugzilla tickets

accessibility.ARIAReflection.enabled
Bug 1628418 - ARIA reflection: implement AccessibilityRole interface

apz.frame_delay.enabled
Bug 1630781 - Eliminate the frame_delay pref, assume it true everywhere.

apz.windows.force_disable_direct_manipulation
Bug 1635243. Only use WS_EX_LAYERED | WS_EX_TRANSPARENT on the compositor window on nightly for now.
Bug 1632357. Add a pref to disable adding the WS_EX_LAYERED style to the compositor window.

browser.aboutwelcome.log
Bug 1631668 - Consolidate messaging-system and about:welcome logging, add additional logs
Bug 1617783 - Add JSWindowActors to about:welcome

browser.contentblocking.report.monitor.how_it_works.url
Bug 1602096 - update 'How it works' link on Firefox Monitor Card.

browser.find.anonymous_content.enabled
Bug 1627643 - Allow to find and display selection native anonymous content.

browser.fixup.dns_first_for_single_words
Bug 1496578 - convert nsDefaultURIFixup to URIFixup.jsm.

browser.fixup.typo.scheme
Bug 1496578 - convert nsDefaultURIFixup to URIFixup.jsm.

browser.newtabpage.activity-stream.asrouter.providers.message-groups
Bug 1633009 - Disable the Remote Settings message-group provider because it is not used
Bug 1578754 - Implement groups configuration for Messaging System content

browser.newtabpage.activity-stream.asrouter.providers.messaging-experiments
Bug 1631456 - Create a CFR message loader for ExperimentAPI

browser.osKeyStore.loglevel
Bug 1631879 - Update the name of the osKeyStore log preference now that it has moved to toolkit.
Bug 1194529 - Update OSKeyStore pref names now that the module is moved.

browser.safebrowsing.provider.google.reportURL
Bug 1408779 - link to report why page has been classified as malicious/deceptive/... should have variables %NAME% and %LOCALE% replaced
Bug 1408779 - link to report why page has been classified as malicious/deceptive/... should have variables %NAME% and %LOCALE% replaced

browser.safebrowsing.provider.google4.reportURL
Bug 1408779 - link to report why page has been classified as malicious/deceptive/... should have variables %NAME% and %LOCALE% replaced
Bug 1408779 - link to report why page has been classified as malicious/deceptive/... should have variables %NAME% and %LOCALE% replaced

browser.stopReloadAnimation.enabled
Bug 1629953 - Use prefers-reduced-motion media query for the stop/reload button animation.

browser.tabs.documentchannel.parent-initiated
Bug 1632098 - P3. Enable the ParentProcessDocumentChannel.
Bug 1602318 - Enable parent initiated loads pref.
Bug 1602318 - Initiate document loads in the parent process in parallel with setting up the content process side.
Bug 1602318 - Start loads directly from CanonicalBrowsingContext when possible.

browser.tabs.documentchannel.ppdc
Bug 1632098 - P3. Enable the ParentProcessDocumentChannel.
Bug 1607984 - P17. Put ParentProcessDocumentChannel behind a pref.

browser.tabs.multiselect
Bug 1634013 - Remove the browser.tabs.multiselect pref

browser.tabs.remote.allowLinkedWebInFileUriProcess
Bug 1603007 - Remove allowLinkedWebInFileUriProcess
Bug 1626583 - Always disable allowLinkedWebInFileUriProcess
Bug 1603006 - Ignore allowLinkedWebInFile when documentChannel is enabled

browser.tabs.remote.separatePrivilegedContentProcess
Bug 1621269 - Disable the privileged about content process on Linux64 ccov builds.
Bug 1617983 - Re-enable separate privileged about content process for about:home, about:newtab, about:welcome on Nightly.

browser.tabs.showAudioPlayingIcon
Bug 1634012 - Remove the browser.tabs.showAudioPlayingIcon pref.r=dao

browser.ui.scroll-toolbar-threshold
Bug 1627716 - Remove APZ/composition code related to DynamicToolbarAnimator.

browser.urlbar.maxCharsForSearchSuggestions
Bug 1618769 - Increase max chars for search suggestions, and don't fetch suggestions at all when max is reached due to paste.

browser.urlbar.oneOffSearches
Bug 1628926 - Remove the browser.urlbar.oneOffSearches pref.

browser.urlbar.restyleSearches
Bug 1626946 - Remove search suggestions that dupe a search history result.

browser.urlbar.update1
Bug 1627988 - Remove the browser.urlbar.update1.view.stripHttps pref.
Bug 1627969 - Remove the megabar pref.
Bug 1617029 - Enable urlbar.update1.* prefs (quantumbar update 1) on Release.
Bug 1616880 - Allow tabbing through urlbar results when there's a search string.
Bug 1613869 - Enable urlbar.update1.* prefs on early Beta.
Bug 1613699 - Rename browser.urlbar.update1.expandTextOnFocus pref to ...update2...
Bug 1613608 - Enable Interventions in Nightly but not in xpcshell tests.
Bug 1613608 - Enable Interventions in Nightly.
Bug 1608766 - Disable tabbing through results after focusing the Urlbar with the keyboard, behind a pref.
Bug 1606917 - Port the Interventions experiment into a new provider.
Bug 1609699 - Rename browser.urlbar.searchTips pref to browser.urlbar.update1.searchTips.
Bug 1603780 - Set browser.urlbar.update1.expandTextOnFocus default value in Nightly.
Bug 1601339 - Disable expandTextOnFocus.

browser.urlbar.update1.view.stripHttps
Bug 1627988 - Remove the browser.urlbar.update1.view.stripHttps pref.
Bug 1617029 - Enable urlbar.update1.* prefs (quantumbar update 1) on Release.

browser.xul.error_pages.enabled
Bug 1592780 - Empty alerts when browser.xul.error_pages.enabled=false,

devtools.contenttoolbox.webconsole.input.context
Bug 1628346 - Add a dedicated context selector pref for content toolbox.

devtools.experiment.f12.shortcut_disabled
Bug 1630228 - Basic implementation to disable F12 until toolbox opens

devtools.inspector.compatibility.target-browsers
Bug 1590981: Make target browsers persistent.

devtools.inspector.use-new-box-model-highlighter
Bug 1607755 - Remove box model highlighter implementation with setupInParent()

dom.mozBrowserFramesEnabled
Bug 1630691: Part 2 - Get rid of the "dom.mozBrowserFramesEnabled" pref.

dom.quotaManager.useDOSDevicePathSyntax
Bug 1632133 - Enable DOS device path syntax for quota storage by default;
Bug 1626846 - Disable useDOSDevicePathSyntax for QuotaStorage on Windows;

dom.registerProtocolHandler.insecure.enabled
Bug 1597267 - Remove dom.registerProtocolHandler.insecure.enabled

dom.security.https_only_mode.upgrade_local
Bug 1631384 - Added upgrade exceptions for HTTPS Only Mode.

dom.security.https_only_mode.upgrade_onion
Bug 1631384 - Added upgrade exceptions for HTTPS Only Mode.

dom.security.https_only_mode_ever_enabled
Bug 1620244 - Retention telemetry for HTTPS Only Mode.

dom.window.content.untrusted.enabled
Bug 1632143 - Disable window.content in early betas
Bug 1632116 - Introduce dom.window.content.untrusted.enabled

editor.truncate_user_pastes
Bug 1320229 - allow user pastes longer than input maxlength

extensions.blocklist.addonItemURL
Bug 1620621 - Add bloomfilter-based blocklist for addons

extensions.blocklist.useMLBF
Bug 1620621 - Implement blocklist stashing behind pref
Bug 1620621 - Add bloomfilter-based blocklist for addons

extensions.blocklist.useMLBF.stashes
Bug 1620621 - Implement blocklist stashing behind pref

extensions.webservice.discoverURL
Bug 1620438 - Remove references to extensions.webservice.discoverURL.

gfx.color_management.mode
Bug 455077 - Enable color management for all CSS/images, not just tagged images.

gfx.omta.background-color
Bug 1535532 - Enable background color animations on the compositor by default on all channels.

gfx.vsync.force-disable-waitforvblank
Bug 1630389 - Enable WaitForVBlank by default on Windows 10

gfx.vsync.use-waitforvblank
Bug 1630389 - Enable WaitForVBlank by default on Windows 10
Bug 1628137 - Switch to using WaitForVBlank for vsync on Windows
Bug 1628137 - Switch to using WaitForVBlank for vsync on Windows.

gfx.webrender.enable-item-cache
Bug 1633842 - Enable WR item cache
Bug 1616412 - Enable WebRender display item caching

gfx.webrender.gl-debug-message-critical-note
Bug 1632096 - Forward WebRender gl(ANGLE) error message to gfx critical note

gfx.webrender.gl-debug-message-print
Bug 1632096 - Forward WebRender gl(ANGLE) error message to gfx critical note

gfx.webrender.use-optimized-shaders
Bug 1604615 - Use optimized shader source in webrender.

identity.sync.useOAuthForSyncToken
Bug 1631830 - Fetch Sync tokens with OAuth behind a pref

image.avif.enabled
Bug 1625363 - AVIF (AV1 Image File Format): experimental support.

image.honor_orientation_metadata.natural_size
Bug 1630165 - Remove nightly-only gate from naturalWidth/naturalHeight honoring orientation metadata.
Bug 1566316 - Make naturalWidth/naturalHeight on images honor orientation metadata.

image.honor-orientation-metadata
Bug 1616411 - Part 3: Make RasterImage deal with and apply image orientation.

javascript.options.mem.gc_avoid_interrupt_factor
Bug 1630961 - Remove unused heurisitic to delaying GCs that may cause resets

javascript.options.mem.gc_dynamic_heap_growth
Bug 1633405 - Remove dynamic GC options that are enabled everywhere

javascript.options.mem.gc_dynamic_mark_slice
Bug 1633405 - Remove dynamic GC options that are enabled everywhere

javascript.options.mem.gc_high_frequency_heap_growth_max
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_high_frequency_heap_growth_min
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_high_frequency_high_limit_mb
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_high_frequency_large_heap_growth
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_high_frequency_low_limit_mb
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_high_frequency_small_heap_growth
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_large_heap_incremental_limit
Bug 1633752 - Calculate non-incremental threshold based on heap size and increase it for smaller heaps

javascript.options.mem.gc_large_heap_size_min_mb
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.mem.gc_non_incremental_factor
Bug 1633752 - Calculate non-incremental threshold based on heap size and increase it for smaller heaps

javascript.options.mem.gc_small_heap_incremental_limit
Bug 1633752 - Calculate non-incremental threshold based on heap size and increase it for smaller heaps

javascript.options.mem.gc_small_heap_size_max_mb
Bug 1633457 - Rename some GC parameters for clarity

javascript.options.wasm_reftypes
Bug 1618595: Disable Cranelift on aarch64 when reftypes are enabled;

layout.css.always-repaint-on-unvisited
Bug 1632765 - Turn on some more :visited privacy mitigations.

layout.css.contain.enabled
Bug 1626458 part 1: Remove pref for CSS Containment (layout.css.contain.enabled)
Bug 1623819 - Part 1: Fix a few initial values in Rust property definitions.

layout.css.grid-template-masonry-value.enabled
Bug 1607954 part 1 - [css-grid][css-align] Implement style system support for Masonry layout.

layout.css.image-orientation.initial-from-image
Bug 1616411 - Part 2: Don't bother passing in the size to OrientedImage::OrientSurface.
Bug 1623820 - Part 2: Make image-orientation initial value change be Nightly only.

layout.css.is-where-selectors.enabled
Bug 1509418 - Enable the feature in Nightly.
Bug 1629735 - Implement parsing / selector-matching for :is() and :where().

layout.css.notify-of-unvisited
Bug 1632765 - Turn on some more :visited privacy mitigations.

media.getdisplaymedia.enabled
Bug 1624181 - Omit getDisplayMedia() function on android to aid feature detection.

media.testing-only-events
Bug 1625615 - part5 : add test-only attribute and event for media element.

network.data.max-uri-length-mobile
Bug 1626687 - Do not handle data URIs larger than 2M on mobile

network.disable.ipc.security
Bug 1322254 - Remove network.disable.ipc.security pref

network.http.http3.default-qpack-table-size
Bug 1628460 - Turn off qpack dynamic table.

privacy.purge_trackers.logging.enabled
Bug 1628743 -  Enable cookie purging by default in Nightly, clean up logging prefs.
Bug 1599262 - Purge site data after identifying tracking site via cookies.

privacy.purge_trackers.logging.level
Bug 1628743 -  Enable cookie purging by default in Nightly, clean up logging prefs.
Bug 1624863 - Rewrite PurgeTrackerService.jsm logging to use console.createInstance

privacy.restrict3rdpartystorage.expiration_visited
Bug 1616585 - add heuristic for visited redirection;

privacy.restrict3rdpartystorage.heuristic.recently_visited
Bug 1616585 - add heuristic for visited redirection;

privacy.restrict3rdpartystorage.heuristic.recently_visited_time
Bug 1616585 - add heuristic for visited redirection;

privacy.trackingprotection.testing.report_blocked_node
Bug 1608516 - Part 3: Add a pref to prevent sending unnecessary IPC if we are not in testing.

privacy.webrtc.allowSilencingNotifications
Bug 1637336 - Add a preference that uses an alternative WebRTC screen sharing permission panel configuration.

privacy.webrtc.legacyGlobalIndicator
Bug 1636207 - Fork the WebRTC global indicator for a refresh.

privacy.webrtc.sharedTabWarning
Bug 1634796 - Add a panel that warns users before switching tabs when sharing the window over WebRTC.

prompts.defaultModalType
Bug 1615588 - Extended nsIPromptService to support tab modal prompts.

prompts.modalType.confirmAuth
Bug 1629808 - Updated ConfirmAuth dialogs to be tab modal and re-enabled them.

prompts.modalType.insecureFormSubmit
Bug 616849 - Made insecure form submission prompt tab modal.

security.identityblock.show_extended_validation
Bug 1599729 - Remove security.identityblock.show_extended_validation pref and related UI code.

services.blocklist.addons-mlbf.checked
Bug 1620621 - Add bloomfilter-based blocklist for addons

services.blocklist.addons-mlbf.collection
Bug 1620621 - Add bloomfilter-based blocklist for addons

services.blocklist.addons-mlbf.signer
Bug 1620621 - Add bloomfilter-based blocklist for addons

services.sync.prefs.sync.intl.regional_prefs.use_os_locales
Bug 1379910 - Add Preference option to change the locale strategy for regional preferences

signon.management.overrideURI
Bug 1569253 - remove old password manager UI.

signon.management.page.os-auth.enabled
Bug 1636511 - Disable the OS auth feature in about:logins on Release and Beta.
Bug 1626138 - Add a temporary pref to disable the OS auth prompt.

signon.showAutoCompleteImport
Bug 1618311 - Contextually suggest importing passwords as an autocomplete entry

toolkit.asyncshutdown.report_writes_after
Bug 1610134: Part 1: add timeout pref that turns on late write checking to see if it's possible to crash browser earlier.

toolkit.osKeyStore.loglevel
Bug 1631879 - Update the name of the osKeyStore log preference now that it has moved to toolkit.

webgl.prototype.ipc-pcq
Bug 1621762: Part 7 - Add IpdlQueue actor traits to WebGLParent/WebGLChild

I think we can remove 0850c, 0850d, 0850e (b is already gone and e is deprecated this release: that the oneOffSearches). The urlbar is now switched to the new awesomebar (and urlbar1 prefs removed) and those prefs (c + d), AFAIK, relate to the old one, but we should check. It also wouldn't surprise me if everything we know about the location bar is up for re-checking: e.g. if all suggestion types are disabled, are search engine keywords still disabled, etc. I mean, they rebuilt all the logic around their UX studies
Anyway: maxRichResults (c) and autofill (d) have nothing to do with privacy and oneOffSearches (e) doesn't either, but at least that's deprecated now. I get the shoulder surfer aspect of it, but that's on the end user: even Tor Browser doesn't cover this. You can't code OpSec.
TBH: if you're like me and don't like the urlbar doing anything except being static (no suggestions, not UI changes, no movements, no color changes), then I've simply been using chrome css

^^ I am using 0850c and 0850d. And both are still valid in FF 76.
Don't know about 77 yet.
OT: did I loose collaborator title?

dom.security.https_only_mode.upgrade_local:

If true and HTTPS-only mode is enabled, requests
to local IP addresses are also upgraded

dom.security.https_only_mode.upgrade_onion:

If true and HTTPS-only mode is enabled, requests
to .onion hosts are also upgraded

dom.security.https_only_mode_ever_enabled:

WARNING: Don't ever update that pref manually! It is only used
for telemetry purposes and allows to reason about retention of
the pref dom.security.https_only_mode from above.

Telemetry is disabled and reseting this in the user.js would be useless.

https://github.com/ghacksuserjs/ghacks-user.js/issues/923 is an issue again in FF77 !! (but it only affects Windows)
The good news is that the problem is apparently already fixed in FF78+ (1634267).
So we can either temporarily set 0709 to false or add dom.quotaManager.useDOSDevicePathSyntax=false for the 77 release.
useDOSDevicePathSyntax=true is supposed to fix issues when file paths exceed the path limit on Windows so I think the better option is to just set 0709 to false.
(We should set it to false instead of making it inactive, for people who don't run the prefsCleaner after every update)
Linux and Mac users can add 0709 to their user-overrides if they deem it necessary but it's a pretty edge-case protection anyways and losing it for 1 release isn't too bad either, IMO.

speaking of breakage - did you get that email I sent about changes to the origin attributes and thus to the naming conventions? I don't have the email anymore so I can't find the ticket quickly. I hope we don't end up with a migration mess like when they applied OA to extensions

this is the link you sent me: https://bugzilla.mozilla.org/show_bug.cgi?id=1558932#c16

updated OP for the final release.
Only 1 difference since RC1: the change to gfx.color_management.mode didn't land

Sorry if I missed this somewhere, but Firefox release on Windows just updated to v77. With ghacksuserjs, extensions seemed to be messed up. For example, trying to view the uBlock Origin settings page only shows the header bar but no content. This issue seems to affect other extensions as well. Without ghacksuserjs, there is no issue. Suggestions on a setting I should adjust?  There's a lot of dFPI stuff going on, and then baku is busy adding isolate* prefs (some sort of partitioning ), and then there's a bunch of over-arching tickets about principals and OA's

OT: anyone know the css for userChrome to modify the awesomebar and searchbar blue outlines when they have focus (as show in the top part of the pic)

@collinbarrett , @crssi  https://github.com/ghacksuserjs/ghacks-user.js/commit/05580f5e99ccbe02646c9062acd137e51b55a8d2
Added to the master so no-one needs an override: I'll remove it some time well after 78 lands and it's known to be fixed

If anyone has a reddit account ... this totally looks like the UNC / DOS Path problem - just point them to #923 - TIA

https://old.reddit.com/r/firefox/comments/gvc7zd/none_of_my_extensions_work_now_with_firefox_77/

anyone know the css for userChrome to modify the awesomebar and searchbar blue outlines when they have focus

Maybe https://www.reddit.com/r/FirefoxCSS/comments/fxez4e/remove_new_megabar_grow_shrink_effect/fmvadbr/

OT: anyone know the css for userChrome to modify the awesomebar and searchbar blue outlines when they have focus (as show in the top part of the pic)

I use this.
#urlbar[focused] > #urlbar-background{
  border-color:hsla(240,5%,5%,.35) !important;
  /*box-shadow: none !important;*/
  box-shadow: 0 1px 6px rgba(0,0,0,.1) !important;
}

^^ thanks (I'll check it out), and @gwarser that helped with the css property name
this works for urlbar: cannot for the life of me get the selectors right for searchbar (the one on the right)
#urlbar, .searchbar-textbox {
	--toolbar-field-focus-border-color: #202124 !important;
}

my bad, didn't realize you needed both, this should work.
#urlbar[focused="true"] > #urlbar-background,
#searchbar:focus-within{

this should work

Excellent .. have a socially distanced hug 🤗

I think they fully broke 1633. Now its user_pref("ui.prefersReducedMotion", 1);. Can somebody confirm or its my imagination?
Classic urlbar CSS for Firefox 77
#urlbar[breakout][breakout-extend] {
top: 5px !important;
left: 0px !important;
width: 100% !important;
padding: 0px !important;
}
#urlbar[breakout][breakout-extend] > #urlbar-input-container {
height: var(--urlbar-height) !important;
padding: 0 !important;
}
#urlbar[breakout][breakout-extend] > #urlbar-background {
animation: none !important;;
}
#urlbar[breakout][breakout-extend] > #urlbar-background {
box-shadow: none !important;
}
#urlbar-results {
padding-top: 0 !important;
padding-bottom: 0 !important;
}
.urlbarView-body-inner {
border-top: 0px !important;
}

I can't see any 1633 or that pref in the user.js - you'll have to more clear on STR and what it is that is changing
Is RFP on? Are you using toolkit.cosmeticAnimations.enabled? What happens if you set RFP to false in the user.js and restart (don't forget to turn change it back to true)
Note: I do not consider this an issue for this repo (outside the larger issue below about RFP exemptions - which can only be done upstream)

RFP returns  no-preference with prefers-reduced-motion (FF63+), and whatever the pref is for animations (e.g. toolkit.cosmeticAnimations.enabled ) is being removed and tied to prefers-reduced-motion - but AFAIK that's all in 78 AFAIK .. I'm not really following it - maybe there's something in 77 to do with whatever it is you say is still being animated

1417079 - Make tab hover animation obey PRM
1520641 - Make zoom level percentage bubble animation obey PRM
1635095 - Obey PRM in CustomizeMode.jsm
1635419 - Make saved-to-library animations obey PRM
1636057 - Make arrow panel opening animation obey PRM
1635475 - Make notification bars obey PRM
1636112 - Make post-prompt animation obey PRM
1634861 - Set ui.prefersReducedMotion instead of toolkit.cosmeticAnimations.enabled for tabpaint

See that last one - we do have toolkit.cosmeticAnimations.enabled in the user.js under personal and off by default.

What needs to happen is for RFP to allow exceptions where not web content/accessible. A bit like this one for prefers-color-scheme which just landed
There are bigger overriding tickets (and lots of little ones about exemptions) about how to classify principals (like about pages, chrome://, resource://, web extension pages, vs web content) and what web accessible content is in or can be read in those - and allowing exceptions for all RFP patches where exempted - including based on origin attributes (so you can have RFP off in normal windows, and on in PB mode)
this ticket is kinda what I'm talking about

Yes. Im talking about toolkit.cosmeticAnimations.enabled in personal section. Look on refresh page button with ui.prefersReducedMotion;1 and without it.

Here's the meta bug - there are at least 5 bugs in all of the ones for FF77 (I queried all 77 bugs) where the title indicates a change to UI animations to use PRM
The pref in the personal section will eventually be deprecated. Just use your custom chrome css. But long term the idea is that RFP exempts the UI (chrome) etc.
Yes, javascript can query what your prefers motion and prefers color etc are - so RFP locks that down to the default, otherwise it's just another bit of data that can be used overall in your fingerprint

pref("privacy.dynamic_firstparty.use_site", true);
pref("privacy.firstparty.isolate.use_site", false);

Quoting FF Devs:
"We can keep FPI/dFPI have the same behavior here, and (if necessary, ) use another pref to control whether we should use site or not. The pref may keep some backward-compatibility for special cases, e.g. Tor Browser, and we can turn this pref on to use "site"."
src https://bugzilla.mozilla.org/show_bug.cgi?id=1637516#c9

"The first pieces of dynamic first-party isolation (DFPI) landed in Nightly. DFPI is an experimental approach to isolating all third party cookies and storage, similar to FPI (which is enabled by default in the Tor Browser and is also supported by Firefox). The most important difference between DFPI and FPI is that DFPI will adhere to exceptions granted through the storage access API and thus ensure better web compatibility. "
https://wiki.mozilla.org/Firefox_Security_Newsletter/FSN-2020-Q1

Thanks. I'm aware of all that and for the user.js I'm tracking it in #930

Welcome, @Thorin-Oakenpants  is there any benefit at this point enabling privacy.firstparty.isolate.use_site?


python3Packages.pymunk: 6.5.2-> 6.9.0, convert to pyproject, fix cross

https://github.com/viblo/pymunk/blob/master/CHANGELOG.rst
Before this change the build process fails for nix build .#pkgsCross.aarch64-multiplatform.python3Packages.pymunk, but adding cffi to nativeBuildInputs fixes it.
I've tested this change at runtime as well by cross-compiling a Python env with this package, copying the closure to a Raspberry Pi 4, and importing the module on the Raspberry Pi. The build machine is x86_64 and binfmt is disabled (checked by trying to run the cross-compiled environment, and I correctly got "cannot execute binary file: Exec format error"). nix path-info -r ./result | grep -v aarch returns no results so it looks clean to me.
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
[ ] 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

[ ] Fits CONTRIBUTING.md.

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

@emilytrau Any thoughts as maintainer?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/5022

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354101

x86_64-darwin

:fast_forward: 6 packages marked as broken and skipped:

python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.pettingzoo
python312Packages.pettingzoo.dist
python312Packages.shimmy
python312Packages.shimmy.dist

:x: 2 packages failed to build:

python311Packages.pettingzoo
python311Packages.pettingzoo.dist

:white_check_mark: 4 packages built:

python311Packages.pymunk
python311Packages.pymunk.dist
python312Packages.pymunk
python312Packages.pymunk.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354101

aarch64-darwin

:fast_forward: 6 packages marked as broken and skipped:

python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.pettingzoo
python312Packages.pettingzoo.dist
python312Packages.shimmy
python312Packages.shimmy.dist

:white_check_mark: 6 packages built:

python311Packages.pettingzoo
python311Packages.pettingzoo.dist
python311Packages.pymunk
python311Packages.pymunk.dist
python312Packages.pymunk
python312Packages.pymunk.dist


Reuse docker image #929

@sonichi
Related issue number
Closes  #929
Checks

[x] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[x] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[x] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3a768c3) 26.63% compared to head (a06f024) 26.44%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #956      +/-   ##
==========================================
- Coverage   26.63%   26.44%   -0.19%
==========================================
  Files          28       28
  Lines        3777     3777
  Branches      858      858
==========================================
- Hits         1006      999       -7
- Misses       2700     2706       +6
- Partials       71       72       +1

Flag
Coverage Δ

unittests
26.44% <ø> (-0.14%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feat: add Download app page

Describe the feature
To create a download app page
Add ScreenShots

it will redirect to download page
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @arghadipmanna101 PTAL


Add pyproject.toml

Use Poetry, MyPy, Ruff, and Black

Hey @uripeled2 can you please open a PR for this?

Yup merged in https://github.com/assafelovic/gpt-researcher/pull/319


video_player black screen on iOS

I'm unable to play videos, that were recorded on Android using MediaRecorder
Sound is working
Video is valid and is playing via system Photos apps, as well as on Android, Chrome etc.
I've uploaded sample here: https://camy.cam/video.mp4
FFPlay output:
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 0
    compatible_brands: isom3gp4
    creation_time   : 2019-04-12T06:50:45.000000Z
  Duration: 00:00:09.71, start: 0.000000, bitrate: 16554 kb/s
    Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 16679 kb/s, 29.99 fps, 30 tbr, 90k tbn, 180k tbc (default)
    Metadata:
      rotate          : 180
      creation_time   : 2019-04-12T06:50:45.000000Z
      handler_name    : VideoHandle
    Side data:
      displaymatrix: rotation of -180.00 degrees
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 118 kb/s (default)
    Metadata:
      creation_time   : 2019-04-12T06:50:45.000000Z
      handler_name    : SoundHandle

Just in case hosting is down uploading sample here:
video.mp4.zip
Tried latest video_player from pub and master branch
Flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.3.8, on Mac OS X 10.14.3 18D109, locale en-BY)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.2)
[✓] Android Studio (version 3.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.1)
[!] VS Code (version 1.32.3)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Hi @rostopira
Could you try the following commit and check if your videos are rendered properly (i.e. no more black screen)?
dependencies:
  video_player:
    git:
      url: https://github.com/recastrodiaz/plugins.git
      path: packages/video_player
      ref: fa7ee080bb7429c6e46dbb0fc9b04be5782265e8
    version: ^0.10.1+4

For more info about the changes please check: https://github.com/flutter/plugins/pull/1307/

Closing as outdated


Fine-grained script detection.

I frequently write messages with mixed language content, in English, Japanese, and Chinese. Japanese and Chinese fonts differ regionally, and while in general it is acceptable to use the default han character font on the platform to render characters, even if the font is not appropriate for the specific language, there are cases where this can look really hideous. Particularly if say, you are in Taiwan and are reading a piece of Japanese text (mixed kana and kanji) on a computer configured to prefer Taiwanese fonts: you will see a mix of Taiwanese fonts on some of the kanji, Japanese fonts on some of the variant kanji that are only used in Japan (e.g. 說 vs 説), and kana rendered in a proper japanese font, or possibly from a Chinese font other than the one displaying the rest of the common unified han characters, which happens to have kana (e.g. MS KaiTi).
Furthermore, screen readers often struggle with multilingual text, or even just text that doesn't have a plausible language tag; you may be lucky and be in a situation where the defaults make sense, but you can also end up with a situation where the screen reader will read Japanese kanji as pronunciations of the most common Mainland Chinese pinyin for the given character, in an American English accent with no tones.
I have a relatively lightweight library that I've used to solve this segmentation problem before, it is general and consults the browser environment (via navigator.language and navigator.languages) to resolve ambiguous situations (e.g. a word on its own that is common between all or most CJK languages and regional scripts; or a word that is common among many latin script languages). If I were to make a clean PR for tagging likely regional script boundaries on the web frontend, and rendering them into spans with lang attributes, and the additional size and runtime were considered negligible, how likely is it that this would be merged?
P.S. If there is a similar source of locale preferences available to the mobile apps, it should be applicable there as well; and provided the language information can be provided through the platform accessibility APIs, the accessibility issues should be resolved through that on mobile as well, or at least on iOS (I think RN doesn't use accessibilityLanguage properly on Android, and doesn't have upstream support for LocaleSpan [the Android approach to spans with language tag information]).

This sounds awesome! Can you start a topic in #frontend on chat.zulip.org about this idea?
I don't personally have much background in this specific problem, so you may want to start with a bit more education for the Zulip community with examples; we'd of course love a PR for this but it's probably best to get buy-in on the technical design. (I'm not sure what the tradeoffs are between an explicit Markdown feature, for example, or relying on auto-detection).


Add option for multiple ingresses objects

Hi, I have a use-case where I need to deploy 2 ingresses for the same service, with different annotations per each ingress.
In particular I'm trying the set nginx.ingress.kubernetes.io/auth-url for one ingress and don't set it for the other.
Can you please add support for multiple ingresses objects?

Hi, so is this what you suggest to be supported in the values file?
current:
ingress: 	enabled: true 	annotations: 		nginx.ingress.kubernetes.io/auth-url: /foo
new:
ingress: 	- annotations: 		nginx.ingress.kubernetes.io/auth-url: /foo 	- annotations: 		nginx.ingress.kubernetes.io/auth-url: /bar

Hey, yes something like that.
I suggest to accept a list of ingresses and create an Ingress object for each of them.
I my case the 2nd ingress doesn't need the auth-url annotation.
e.g:
current:
ingress:
  enabled: true
  path: /foo
  hostname: "a.example.com"
  ingressClassName: "nginx"
  annotations:
    nginx.ingress.kubernetes.io/auth-url: http://test.com/foo

new:
ingress:
  - enabled: true
    path: /foo
    hostname: "a.example.com"
    ingressClassName: "nginx"
    annotations:
      nginx.ingress.kubernetes.io/auth-url: http://test.com/foo
  - enabled: true
    path: /bar
    hostname: "a.example.com"
    ingressClassName: "nginx"

@atkrad What do you think about this? I really need this since I currently have an ingress applied manually outside of the chart because of different annotations.
Maybe adding extraIngresses option will solve this? I can work on a PR

I also need this, @atkrad What do you think ?


Fixed : VERIFY-DEPLOYMENT-PROVISION-SRIOV

Execution is verified.
08/07/2018 09:05:03 : [INFO ] ~~~~~~~~~~~~~~~TEST END : VERIFY-DEPLOYMENT-PROVISION-SRIOV~~~~~~~~~~
08/07/2018 09:05:03 : [INFO ] CURRENT - PASS    - 1
08/07/2018 09:05:03 : [INFO ] CURRENT - FAIL    - 0
08/07/2018 09:05:03 : [INFO ] CURRENT - ABORTED - 0
08/07/2018 09:05:03 : [INFO ] Checking background cleanup jobs..
08/07/2018 09:05:03 : [INFO ] Removed 0 context files.
08/07/2018 09:05:03 : [INFO ] Cycle Finished.. TC-79380
08/07/2018 09:05:04 : [INFO ]
Test Results Summary
ICA test run on 08/07/2018 08:58:24
ARM Image under test RedHat : RHEL : 7.4 : latest
Total Executed TestCases        1 (       1 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:0:6
XML file: TestConfiguration
VERIFY-DEPLOYMENT-PROVISION-SRIOV Execution Time: 6.61 minutes
	VERIFY-DEPLOYMENT-PROVISION-SRIOV : PASS
		  FirstBoot : PASS
		  FirstBoot : Call Trace Verification : PASS
		  Reboot : PASS
		  Reboot : Call Trace Verification : PASS
Logs can be found at .\TestResults\2018-07-08-08-58-17-8139
08/07/2018 09:05:04 : [INFO ] Creating 'Azure-79380-buildlogs.zip' from '.\TestResults\2018-07-08-08-58-17-8139'
08/07/2018 09:05:04 : [INFO ] C:\LISAv2\VMTZ79380\Azure-79380-buildlogs.zip created successfully.
08/07/2018 09:05:04 : [INFO ] Copied : .\report\report_TC-79380.xml --> .\report\report_TC-79380-junit.xml
08/07/2018 09:05:04 : [INFO ] Analysing results..
08/07/2018 09:05:04 : [INFO ] PASS  : 1
08/07/2018 09:05:04 : [INFO ] FAIL  : 0
08/07/2018 09:05:04 : [INFO ] ABORT : 0
Copying all files back to original working directory: C:\Jenkins-Slaves\azure-slave-2-executor-9\workspace\job-azuretest\job-cloudtest-auto@2.
Cleaning up C:\LISAv2\VMTZ79380
Setting workspace back to original location: C:\Jenkins-Slaves\azure-slave-2-executor-9\workspace\job-azuretest\job-cloudtest-auto@2
08/07/2018 09:05:05 : [INFO ] LISAv2 exits with code: 0

I've also noticed that there some other tests cases due to same cause.
Will fix them in separate PRs. It needs proper execution verification.


feat: enable preview of Fedora 40 main builds

This PR enables F40 *-main images builds with minor caveats:

The F40 builds are nokmods images only, which is the norm since F39.
No mate images are built since our upstream isn't yet building F40.

Important note:
The naming conventions for F40 images (other than silverblue/kinoite) are confusing because of the Fedora naming change to "Atomic Desktop". I may want to discuss this before we start publishing images with wrong names.
Currently we have:

sericea
onyx
lazurite
mate
vauxite

Fedora upstream is renaming sericea to sway-atomic and onyx to budgie-atomic (or something like that). So I think we should find out what their image names will really be and use that, but I'm open to suggestions.
Also, https://quay.io/organization/fedora-ostree-desktops is publishing Lazurite and Vauxite, so I guess we can keep going with those, but would we move them to the new naming convention we use with the official Sway and Budgie images?
And finally, we don't have a maintainer for Mate,, so I'm not sure what we want to do with it. I think we may drop it.

Blocked by: https://github.com/ublue-os/akmods/pull/143

IMO let's name them what upstream Fedora names them, and then for things that timothee adds to the repo we follow we should just mirror as a community service.
Things that we don't have maintainer for like mate (and other repos in the org) we should just retire when F38 retires, if people want to maintain them we should encourage them to either work with fedora officially or have them do it at the compose step in timothee's gitlab namespace. What do we think about that?

IMO let's name them what upstream Fedora names them, and then for things that timothee adds to the repo we follow we should just mirror as a community service.

This is what I expected, and I agree.
The only nuance here is really the naming. I'm not 100% sure what Fedora will name their images. Right now their "official" name for the silverblue image is fedora-silverblue and we're going to keep silverblue so... already we've departed a bit.
So what I'm really asking is are we going to name ours sway-atomic-main and budgie-atomic-main or just sway-main and budgie-main.
And... similarly, if we are going to do that for those, are we going to stick with lazurite and vauxite or are going to proactively switch to lxqt-main and xfce-main?

Things that we don't have maintainer for like mate (and other repos in the org) we should just retire when F38 retires, if people want to maintain them we should encourage them to either work with fedora officially or have them do it at the compose step in timothee's gitlab namespace. What do we think about that?

I agree with this point. We'll be retiring some things in our org which don't really get maintained.

I'm seeing timothee at kubecon I'll ask about the image names and get a list

I think this looks good to go in to get us some initial  F40 images

Stick with the names being used by upstream in my opinion. If they change, we can do a rename at that time. @castrojo if you can get something confirmed by Timothee, we would appreciate it!

Stick with the names being used by upstream in my opinion. If they change, we can do a rename at that time.

I agree, this is certainly the simplest approach and doesn't require guesswork.
Even with upstream branding name changes, so far the image names haven't actually changed, so maybe they won't.
It's probably worth having this now on current names, and renaming images if needed later.

@travier  -  I was told you can provide information on the upcoming naming of Atomic Desktop images?

@travier - I was told you can provide information on the upcoming naming of Atomic Desktop images?

Why don't we merge in with the current names so it is consistent and then also double-tag the layers with the new names if the image names change?

Ok, l'm willing convert to this to an open PR now, with the caveat that we VERY LIKELY will be renaming Fedora 40 images as we see changes from upstream in the next few weeks.
@ublue-os/approver

Ok, l'm willing convert to this to an open PR now, with the caveat that we VERY LIKELY will be renaming Fedora 40 images as we see changes from upstream in the next few weeks.
@ublue-os/approver

Would it not make sense to have the same release under two different names, the old ones and the new ones? That way it would be the least confusing to users.

How would two sets of names be less confusing? This feels like one of those cases where we're stuck with fedora's chosen name schemes?

How would two sets of names be less confusing? This feels like one of those cases where we're stuck with fedora's chosen name schemes?

People already using the current name would see a new version with valid updates on it and not have to rebase.

Yeah not sure what we can do about that, waiting for the fedora names/images was one of the conditions of us leaving beta, and we're not going to bring the old tech debt with us for release.
This is one of the reasons why we don't recommend direct usage of these images. Downstreams who aren't paying attention will notice when their builds stop updating and update, and we special cased the one offs last cycle.
And the people who rebased know how to do it already so it's probably not too much of an ask for them to do it again considering that's really the only way to end up on these images anyway. Though we'll make sure we document it in the release notes.

Yeah not sure what we can do about that, waiting for the fedora names/images was one of the conditions of us leaving beta, and we're not going to bring the old tech debt with us for release.
This is one of the reasons why we don't recommend direct usage of these images. Downstreams who aren't paying attention will notice when their builds stop updating and update, and we special cased the one offs last cycle.
And the people who rebased know how to do it already so it's probably not too much of an ask for them to do it again considering that's really the only way to end up on these images anyway. Though we'll make sure we document it in the release notes.

I'm just thinking having two image names w/ the same layers wouldn't be too hard. It's the equivalent of having :40 and :latest IMO.

But where would we draw the line?  Do we removed them in 41? 42?
I'd say sticking with upstream's choices and timelines is the best option for us IMO.

But where would we draw the line? Do we remove them in 41? 42? I'd say sticking with upstream's choices and timelines is the best option for us IMO.

Do we have to ever remove them? Adding an alias is basically free, just do a copy/push to both names in GHCR after the build.

Odd that 40 is failing now. It worked on commit https://github.com/ublue-os/main/pull/521/commits/77631cacd4b2548439be22d80cc3fb6ffc144400

So, the idea for F40 was to avoid doing painful renames and only change visible names, so we'll likely keep the Sericea and Onyx names for F40. For future releases or new artifacts (the container images built from fedora infra for example), we can make the change so we are probably going to move to sway-atomic and budgie-atomic.
I'll ping you when we make the change or decide on the new names.

so we'll likely keep the Sericea and Onyx names for F40. For future releases or new artifacts (the container images built from Fedora infra for example), we can make the change so we are probably going to move to sway-atomic and budgie-atomic.

This seems reasonable to me.

I'll ping you when we make the change or decide on the new names.

Thank you!


Add Flex Superpowers to the Tweet Embed | Your .follow-btn should have a display property set to flex.

Describe your problem and how to reproduce it:
Add Flex Superpowers to the Tweet Embed
Your .follow-btn should have a display property set to flex.
write source code but not accepted by test
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/responsive-web-design/css-flexbox/add-flex-superpowers-to-the-tweet-embed
Tell us about your browser and operating system:

Browser Name:  Microsoft Edge (Chromium)
Operating System: Windows 10

Screenshot:

Describe your problem and how to reproduce it:
Add Flex Superpowers to the Tweet Embed
Your .follow-btn should have a display property set to flex.
Same as above, "write source code but not accepted by test"
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/responsive-web-design/css-flexbox/add-flex-superpowers-to-the-tweet-embed
Tell us about your browser and operating system:

Browser Name: Firefox 78.4.0esr (64-bit)
Operating System: Debian 10 Buster (stable)

Screenshot:

Heya folks~!
Please be sure that you've disabled any extensions, such as ad blockers, as these interfere with the tests. Ad blockers especially, which commonly block a twitter follow button from rendering.
Additionally, for help with code you have written it is best to use the forum. Feel free to make a post there - if the community determines that there is a bug in the challenge, then make a GitHub issue. 🙂

I didn't even think of that! Disabling uBlock Origin on freecodecamp.org fixed the issue, as did only disabling cosmetic filtering.
Thank you for a quick response!


Allow gswin64c in restricted mode

gswin64c fails in restricted mode:
https://github.com/ho-tex/pdfcrop/blob/2ad5497487c78802f3dea0e86ff287deba414a22/pdfcrop.pl#L635-L639

@bersbersbers  agreed there seems no reason to allow gs and gswin32c but not gswin64c, I'll update

With the advent of 64-bit Windows in TL23 ... please apply/release this. Not that I care personally :).

@kberry added in v1.41 although (r)pdfcrop isn't by default in
shell_escape_commands

From my comment in texmf.cnf (from years ago, when we first added
repstopdf and the whole automatic eps->pdf conversion):
% rpdfcrop - maybe ok, but let's get experience with repstopdf first.
it seems it's never been there, and no one has asked for it.
So I'm not inclined to add it, although I don't see any obvious problem
with it.  Unlike epstopdf, it looks like arbitrary gs options aren't
allowed to be specified, so that eliminates one big pain that epstopdf
has to deal with.
At any rate, thanks for the new release. --thanks, karl.


⚠ ClamAV has degraded performance

In 15538cf, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 49 ms

Resolved: ClamAV performance has improved in 9b3d6ba.


There are many slices with negative duration

Hello Perfetto team
Thank you so much for making a very useful tool.
I used perfetto for finding cause of android drawing performance problem.
But there are some cases slices doesn't have duration value.
negative_dur.zip
(Attached file was recorded with ring buffer with small in-memory-buffer size for getting this problem easily.)
There are many negative duration slices in SystemUI main thread track so it is really inconvenient and I can't sure what slices's ts is correct or not.

This is a known issue which happens in cases where the central ring-buffer wraps in a bad way.  I'm closing this one as this is tracked by internal bug b/192586066.
Here is the detail from the internal bug:
Imagine the following sequence of ftrace bundles which completely fills the central ringbuffer:
bundle {
cpu: 0
end_slice { ts: 11, tid: 1 }
}
bundle {
cpu: 1
begin_slice { ts:10, name: foo, tid: 1 }
}
bundle {
cpu: 0
begin_slice { ts:13, name: bar, tid: 1 }
}
bundle {
cpu: 1
end_slice { ts:14, tid: 1 }
}
The output we would see in the UI would be:
Tid 1:           [ foo ]. [ bar]
Now suppose that we get another bundle which pushes out the first bundle only. This leaves the ring buffer in the following state:
bundle {
cpu: 1
begin_slice { ts:10, name: foo, tid: 1 }
}
bundle {
cpu: 0
begin_slice { ts:13, name: bar, tid: 1 }
}
bundle {
cpu: 1
end_slice { ts:14, tid: 1 }
}
bundle {
cpu: 0
begin_slice { ts: 15, name: baz, tid: 1 }
}
As we've lost the end event for foo, this leads to the following UI result:
Tid 1:           [ foo                                     } (unfinished)
[ bar] [ baz                             }
which is clearly wrong.
One proposal to fix this would be to reject all atrace slices before we see at least one event for every CPU. This would ensure any slices in the first bucket which have a begin but their end was dropped would be dropped as well.
This proposal has two problems:

We need to know the number of CPUs on the device. This can be done using either hardcoding (like the power profile info) or we can poll some node in /proc
Dropping information like this is always risky as we could drop more than we intended.
Other proposals are welcome.


Add Confluent's free ebook: Designing Event Driven Systems by Ben Stopford

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
Add a link to Confluent's free ebook on building Kafka steaming services.
For resources
Description
A book on builing event-driven streaming services build on top of Apache Kafka from Confluent - a company which builds its expertise on the Kafka platform.
Why is this valuable (or not)?
Event-driven systems are a an immense topic, this books provides a look into it through Kafka perspective.
How do we know it's really free?
The ebook can be downloaded free of charge from the Confluent page here: https://www.confluent.io/designing-event-driven-systems/ after providing some personal data. The link in the PR leads directly to confluent assets page.
For book lists, is it a book? For course lists, is it a course? etc.
It's a PDF e-book.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

nice
Thanks, and welcome to free-programming-books!

Hi! Thanks for the merge and warm welcome ❤


Use xcrun simctl json output. Drop Xcode 6 support

In CocoaPods/CocoaPods#5956, we spent some time debugging an issue that came down to regex breaking. Given that we're on our second Xcode release where xcrun simctl list has json output, it seems like as good a time as any to use that output, since it provides consistent structure.
In doing this, I updated the fixtures and specs to use json output with iOS 9 and iOS 10 simulators from Xcode 8.

@segiddins there's no CHANGELOG for this repo 😭. Should I just include it in the README (something about previous to this version)? I could start a CHANGELOG? There are only 36 commits in this repo, so it shouldn't be too bad to rebuild one. I wonder if someone has scripted this before…

Ah yeah I found a tool to help. Gonna try to put one together

I ended up just making it up myself. @neonichu I paraphrased the 1 or 2 release, but the rest just came from your commit messages. Feel free to comment if you see typos or you feel the descriptions aren't accurate. I got the release dates from rubygems.org.
@segiddins fixed!

Known: I still have a travis thing left to work out

On travis xcrun simctl list -j shows iOS 8.1 devices first, and then it goes in descending order starting with iOS 10. Guess it's time to implement simulator sort 😩

Need to add more specs, but this should hopefully pass Travis now.

Alright this is ready to go now

Travis build passing with this fourflusher and CocoaPods master: https://travis-ci.org/benasher44/CocoaPods/builds/164176490 (build is red because I don't have Danger setup in my fork, but the specs are passing)


profile file cannot be null

Describe the bug
I am trying to use SNS to send a message, however, it gives me ERROR.
Resolved [com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: [com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@3d572a77: Unable to load credentials from service endpoint, com.amazonaws.auth.profile.ProfileCredentialsProvider@779e33d4: profile file cannot be null]]

Even if I have already given the credentials details in my application.yml file.
cloud:
  aws:
    credentials:
      access-key: AKIXXXXXXXXXXXXXX
      secret-key: TmKrqVXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I solved this problem by adding an extra Bean, But I have no idea why my configuration doesn't work? Is there anything I left?
    @Bean
    @Primary
    public AWSCredentialsProvider getCredentialsProvider() {
        return new ClasspathPropertiesFileCredentialsProvider();
    }

spring-boot version is 2.2.4
spring-cloud version is Hoxton.SR3
Sample
Nothing

https://github.com/spring-cloud/spring-cloud-aws/blob/328b1307f41f8b011a964d7491318e9df6345b17/spring-cloud-aws-autoconfigure/src/main/java/org/springframework/cloud/aws/autoconfigure/context/ContextCredentialsAutoConfiguration.java#L88-L91
Try to rename key properties:
cloud:
  aws:
    stack:
      auto: false
    credentials:
      accessKey: "yourAccessKey"
      secretKey: "yourSecretKey"

I second @dmile. At the current stage the right way to set access key and secret key is through camel case version (despite IDE autocompletion suggesting the other way).
Closing as a duplicate of https://github.com/spring-cloud/spring-cloud-aws/issues/535 but this will be fixed for sure.


[5.5] Use Arr::wrap when calling seeders

Hey, didn't this change the logic? The previous logic allowed anything to be cast into an array, now that anything will be an element in the array.

@sisve The Arr::wrap() method has the same logic that was simplified here. 👍

@paulofreitas No, it does not. The previous logic casted the value to an array, while Arr::wrap creates an array with the value in it. Here's an example on the difference in a scenario where I load the list of seeders from a json file. https://3v4l.org/rar1K

@sisve Indeed, but it should be noted that this behavior was an unexpected side-effect, the method's docstring says it should expect an array or a string. 😃


add blacklist_flags field to schema description and update schema page

While the blacklist_flags field was added to our tables, when showing table descriptions via the command line tools (ie: bq show ) the field is not displayed along with the other fields in the schema.
Investigate why, fix and update documentation on the schema page.

@critzo didn't you do this?

@georgiamoon Yes. I'm reviewing all the old site issues. This one is resolved. Closing.


B4 Submission

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

confirmed:B4
address:3EZTdPfQM1MWMHt2aJ58Phm1FhtUf3X2bHrntB3dG71D6N4EUn
baker:387

confirmed:B4
address:3EZTdPfQM1MWMHt2aJ58Phm1FhtUf3X2bHrntB3dG71D6N4EUn
baker:387

form submitted-27/04/2022 (UTC +3) 02:38


Ghost version 0.20.0 hosted on NPM repository

Bug description:
A project I got to work on had the following issue https://github.com/angular-ui/ui-select/issues/1849. As stated the fix is to update to >0.19.6.
Ours was listed as 0.20.0 in package.json so I assumed something else was the source of the bug.
Later when I noticed that our version was 0.20.0 and the latest release only goes up to 0.19.8 I found out that somehow there is a 0.20.0 version hosted on npm:
https://registry.npmjs.org/ui-select/-/ui-select-0.20.0.tgz
The date mentioned to the version number are from the release version 0.19.5 hence why we were still having this bug.
Still trying to figure out how we got to version 0.20.0 and why this is hosted on NPM and why it seems to be a duplicate of 0.19.5.
Link to minimally-working plunker that reproduces the issue:
N/A
Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
Angular:
1.6.9
UI-Select:
0.20.0

paste of that versions package.json: https://gist.github.com/KevinRamharak/c5f88ffad4bffa9fe7ee596ce6284e8d


get DISTINCT values for an int (BSI) field

Description
A question was posed by @brucenan here: https://github.com/travisturner/bit-slice-index/issues/1 about getting the set of distinct values for a BSI field.
We can currently get the value for a single column, but I don't believe we have anything that scans the BSI fragment data and collects multiple values.
I wonder if a solution might have multiple row scanners (one for each BSI row), which synchronously scan across the columns to determine each column's value. That value can then be added to a set, which would be the fragment's return value for the distinct query. The aggregator would have to merge the sets from all fragments. Each fragment would have to scan up to 2^20 columns (at standard shardWidth).
Success criteria (What criteria will consider this ticket closeable?)
Once can get the set of distinct values from an int field.

this is probably a subtask of #1752

in addition to some solution that perhaps scans the roaring fragment file to compile a list of distinct values, it may also be worth considering/benchmarking a data structure which keeps a columnID-to-value mapping as part of the field data. in that case, getting distinct would be a matter of performing the normal BSI query, and then passing the results of that query to a lookup step which gets the values from the columnID-to-value map.

From pilosa side, it means map all values from one Fragment to one Slice. The Slice's each available column equals to original Fragment's each value.
Loop is a easy way, but it's not efficient. Maybe divide it into several sub-part and use recursion or multi-thread is a better way.

This is my sample codes by Java:
for(int i = start;i<end;i++) {
  int s = 0;
  for (int j = 0,len = mrbs.length; j < len; j++) {
  if (mrbs[j].contains(i))
     s = s | (1 << j);
  }
  s1.setBit(s);
}

But performance is too low. For 10,000,000 times loop, it spends nearly 7000ms, most of times spends on RoaringBitmap's contains() function. It is unacceptable. Is there any better solution to improve the performance?

@brucenan we don't currently have plans to merge this PR. The code in #2052 is a first pass at an implementation in case you want to reference that.


bug: Collapse with icon, Arrow is jumping but plus/minus icon seems ok

What version of daisyUI are you using?
v4.5.0
Which browsers are you seeing the problem on?
Chrome
Reproduction URL
https://play.tailwindcss.com/EqKz1x2vVS
Describe your issue
Collapse with checkbox and icon with more content has Arrow Icon what is jumping but plus/minus icon seems ok.
In the Arrow Icon: .collapse-arrow > .collapse-title:after { top: 50% } that's why animations is weird, but it properly centered.
In the .collapse-plus > .collapse-title:after { top: 0.9rem; } that's why it looks ok.
Maybe something like this: https://play.tailwindcss.com/i2LKgeYQ1o?file=css
.collapse-title {
    min-height: 2.5rem;
}

.collapse:not(.collapse-close):has(> input[type=checkbox]:checked), .collapse:not(.collapse-close):has(> input[type=radio]:checked) {
    grid-template-rows: 2.5rem 1fr;
}

.collapse {
    grid-template-rows: 2.5rem 0fr;
}

Hello @OlegSuncrown  😄
I'm taking a look at it right now. I think to stay as adaptive as possible, without changing everything that has been done for the collapse, is to change top position of the arrow icon. This is consistent with the collapse "arrow plus/minus icon".
I'm open to other proposals until the PR is reviewed 😉

This fix caused the arrow being not centered when the title bar is not the default height.

Thanks for your feedback, I'll take a look and suggest another solution.

After trying different approaches, I can't seem to solve the problem. I've noticed that my first idea solved the problem, but it's no longer centered. However, when the top is defined as a percentage, the problem persists. Looking for another solution, I found that by placing the svg in the dom, we could probably align the text and arrow without the problem of displacement when rotating. This involves changing the architecture of the component.
Moreover, the component with the plus/minus icon isn't centered either when the title is longer.
If anyone can find a simpler solution, I'd be very interested. 😄


Shouldn't you have two sequences of variables for the accelerated version?

For instance this line only has variables w
https://github.com/benchopt/benchOpt/blob/01acb156bd76708b01a30c3de8918609f1cde3ff/benchmarks/lasso/solvers/python_pgd.py#L31
but I think you need two sequences. Something like this (note the additional variables in x)
   L = np.linalg.norm(self.X, ord=2) ** 2
   n_features = self.X.shape[1]
   w = np.zeros(n_features)
   x = np.zeros(n_features)
   t_new = 1

    for _ in range(n_iter):
        if self.use_acceleration:
            t_old = t_new
            t_new = (1 + np.sqrt(1 + 4 * t_old ** 2)) / 2
        grad = self.X.T.dot(self.X.dot(w) - self.y)
        x_old = x.copy()
        x -= grad / L
        x = self.st(x, self.lmbd / L)  # Not sure what this step does
        if self.use_acceleration:
            w = x+ (t_old - 1.) / t_new * (x -x_old)
    self.w = w

Thanks @gowerrobert !
self.st is the soft thresholding step
with the code you included, if use_accel is False, w is always 0 and so grad = self.X.T.dot(self.X.dot(w) - self.y) should not be correct, right ?
Also one subtlety is that you need to return x, not w  (w is most likely dense because it never forgets initial xs in its update formula w = x+ (t_old - 1.) / t_new * (x -x_old)
I'll give it a more detailed look in the afternoon

OK so I thought there was a way to do it with a single sequence, but it's not so obvious any more.
Adopting this notation (z accelerated, w point to return):

I propose this implementation:
for _ in range(n_iter):
    if self.use_acceleration:
        t_old = t_new
        t_new = (1 + np.sqrt(1 + 4 * t_old ** 2)) / 2
        w_old = w.copy()
    else:
        z = w
    w -= self.X.T @ (self.X @ z - self.y) / L
    w = self.st(w, self.lmbd / L)

    if self.use_acceleration:
        z = w + (t_old - 1.) / t_new * (w - w_old)
self.w = w

do you agree ?

Yes, that looks good to me!
On Fri, 11 Sep 2020, 12:35 pm mathurinm<EMAIL_ADDRESS>wrote:

OK so I thought there was a way to do it with a single sequence, but it's
not so obvious any more.
Adopting this notation (z accelerated, w point to return):
[image: image]
https://user-images.githubusercontent.com/8993218/92912355-02bd8500-f42a-11ea-8406-9ffb379b2475.png
I propose this implementation:
for _ in range(n_iter):
if self.use_acceleration:
t_old = t_new
t_new = (1 + np.sqrt(1 + 4 * t_old ** 2)) / 2
w_old = w.copy()
else:
z = w
w -= self.X.T @ (self.X @ z - self.y) / L
w = self.st(w, self.lmbd / L)
if self.use_acceleration:
    z = w + (t_old - 1.) / t_new * (w - w_old)

self.w = w
do you agree ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/benchopt/benchOpt/issues/60#issuecomment-691018069,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKLP7D5IWBCBQ62N6NU6GTSFH4OXANCNFSM4RFMSQFQ
.


:memo: Add missing httpreferer option doc.

The PR #801 forgot to update the doc.
\cc @frankhale

can you also doc the userAgent option .

:+1: Thanks @hokein

@deepak1556
Done :+1:

Can you rename the option names to httpReferer and userAgent? It has not been documented yet so a rename should be OK.

Done.

The calls in webview also needs to be changed.

@zcbenz Done.

:+1:


A powertoy that allows users to revert specific OS elements that are broken by windows feature updates

Description of the new feature / enhancement
Like most windows feature updates, 22H2 broke many things. Among these are:

Not being able to rearrange taskbar icons
Multi-row tray icons is broken
The gap between tray icons is incredibly wide
Mandatory Recommended section in Windows Search
Ability to restore the old Windows Explorer until the bugs are fixed

Scenario when this would be used?
When people want to be able to update their computer and still be able to use it afterward
Supporting information
No response

/feedbackhub


installation OS

Hello,
congratulations for the work done, you can tell me which linux version I can install Openvas on

any version of linux. you only need to install docker first.


Should put "log" and "ckpt_LEARNER_DATE_TIME" into same folder?

Now the checkpoints and log data are stored in two separate folders. Should we introduce a higher level folder, name EXPERIMENT_NAME or so to store all data of single experiment in it?
By the way, the name format of the checkpoint look quite weird to me, why there are two "_" between the date? I suggest to make it as "checkpoints_MODELNAME" and this is enough! It is not reasonable to write the "created time" in the folder name, since the folder contains lots of checkpoints that are created at different time.

How about the following output file structure:

users need to indicate the field experiment_name in user config, just like:main_config = dict(
    experiment_name='test_exp_name',
    policy=dict(
        ...,
    ),
    env=dict(
        ...,
    ),
)

and if this field is not indicated, engine will set this value in the following default format——'exp_createtime'
In a high level experiment folder, the specific output contents can be like this:

Well, this problem is actually the relation between run log and checkpoint data.
You can analysis like this:

If you need to keep the every-time running log, and it is usually can related one by one with a checkpoint, then you should just put them together.
If every-time running log is not necessary (or too big to keep, too complex so that not able to manage it, any reasons like these), just keep the current structure.

So just think about the user need, the answer is there.

this issue has been figured out in PR #10


Object's member access is O(n)

Object member access, i.e. Value::FindMember(), is in O(n) by linear searching.

Design a faster approach for member access.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 30 Nov 2011 at 5:31

I don't think it is possible to use a faster algorithm without ordering the
keys.

Ordering the keys and putting them in a map also has a overhead so it is does
not make sense to implement it.

Users should access a value once, then store it and re-use the value without
calling Document::operator []. That will be faster than anything.

Original comment by<EMAIL_ADDRESS>on 23 Jul 2013 at 9:28

With C++11 it is possible to use std::unordered_map see e.g.
http://en.cppreference.com/w/cpp/container/unordered_map

Original comment by<EMAIL_ADDRESS>on 5 Nov 2013 at 10:00

Just my opinion…

AFAIK, hash-map overhead is known to be a lot heavier than sorted B-trees if
key count is small. And JSON object usually expected to have a few of keys -
less than 10 keys for example - because large number of keys means there's
something wrong with data structure design.

So I doubt on using hash-map for performance. If your object has dozens of
keys, it would make sense, but I never seen such JSON object.

IMO, binary search is the best approach for a JSON object, and C++11 std::map
is usually intended to be a b-tree.

Original comment by<EMAIL_ADDRESS>on 21 Dec 2013 at 4:57

[deleted comment]

Original comment by<EMAIL_ADDRESS>on 20 Jun 2014 at 8:28

Changed state: WontFix

Added an analysis on this issue.
https://github.com/miloyip/rapidjson/issues/102

Original comment by<EMAIL_ADDRESS>on 11 Aug 2014 at 5:32


con is an invalid folder name (all Windows, but possibly other OSes)

Yes, this is an old issue regarding OSes that remain compatible to code going back to the 70's/80's.
con is a reserved name that can not be used as a folder name in several OSes. You used it in the voice files paths.
Therefore I have problems checking out the repository on Windows 10.
Same is for extraction of the release zip file.
I used Nana Zip to automatically rename the invalid folder to _con.
Probably needs some code changes.

duplicate #126

The docker should work as a bandaid solution for you in the mean time 👍

Thank you, I used WSL, worked also.


Feature: Dark Theme

Needs some work as avalonia acrylic design doesn't seem to work and but dark theme works for now

Does not look modern yet, but a lot better


Proposal: Add support for OpenDev git repos

Support for OpenStack was added in Ia64bdb1dafea33b1c3770803230d30ec1059df22,
and there are still projects working on implementing portions of their functionality in go.
Since that was added though, the infrastructure services for the OpenStack community
have rebranded to be OpenDev, with an expanded scope to support other open source
projects in addition to just the OpenStack project. This is expected to bring in a more
diverse mix of projects and technology choices.
As part of that rebranding, the git services were updated from being at git.openstack.org
to being hosted at opendev.org. The existing support for git.openstack.org should be
kept for some time to make sure there is backwards compatibility. The opendev team
have committed to providing redirects from the old URLs to the new, and there may be
various places where things are hard coded to git.openstack.org. That support can likely
be removed in the future, but for now opendev.org should be added in addition to the
legacy URL support.

This is kind of why we resist adding these special cases in the first place. Even if we update this, it will only start working in Go 1.13 at the earliest, which is probably not what you want.
The best solution here is for the service to serve proper meta tags. Then you'll have full control over the mapping, as well as the redirects, and it will work right away. https://golang.org/cmd/go/#hdr-Remote_import_paths
Any reason that's not possible here?

@FiloSottile - please take a look at the paste.openstack.org link in the patch comments. I think this might already be the case, but I'm not sure of all the internal details and corner cases, so really looking for some advice on what the proper approach should be here.
Based on the output in that example, it looks like it might actually be the case that this can be dropped and the existing entry for git.openstack.org can probably just be removed.

Yep, it looks like opendev.org is already set up.
https://opendev.org/x/golang-client/openstack?go-get=1
Now, the question is what you want to do with the old paths. If you do nothing they are going to be separate packages, which might cause issues with internal imports.
/cc @ianthehat @jayconrod who have more experience with naming and renaming issues than me.

Now, the question is what you want to do with the old paths.

Is it possible to continue to serve the old paths, possibly through redirects?
We really don't have a good story for renaming existing packages at this point.

That is the plan for the time being. It would be nice to be able to get away from that sooner rather than later, but at least as of right now there is no declared end date for when those redirects will stop working.
The only gotcha that I've seen with the rebranding is that some repos moved from, for example, git.openstack.org/openstack-dev/devstack to opendev.org/openstack/devstack (the namespace changed if it's not obvious), but I don't think there should be anything relevant to Go that would have been impacted by this.
So if the consensus is that nothing needs to change and the old entry in there for git.openstack.org is fine to leave, I think I can just abandon that change and close this issue. I'll just wait for any further comments before I do.

I think the best course of action w.r.t. the Go command is not to make any change. It looks like opendev.org is serving the correct meta tags, so there's no need for a new special case. We should keep the git.openstack.org case in place to maintain consistency across Go versions.
About renaming and redirects: as Bryan said, we don't yet have a good story for renaming modules. It's best if the old URLs continue to serve the old repositories. Renaming causes a lot of confusion as users upgrade across versions. #30831 is a prominent example of this. We hope to have a better solution for Go 1.14.


Update naive_bayes.py

the function drop_final_s is not needed (not used anywhere else in the code)
def drop_final_s(word):
return re.sub("s$", "", word)

I take back my comment.
The code appears later in the chapter (p.183), on how to improve the model.
Apologies


Something is wrong when using a transformation in hull.objects.ingress..tls..hosts

Hello again,
It seems that I've found another interesting phenomenon.
Let's assume we have the following values.yaml:
hull:
  objects:
    ingress:
      test:
        rules:
          default:
            host: example.org
            http:
              paths:
                root:
                  path: /
                  pathType: Prefix
                  backend:
                    service:
                      name: test
                      port:
                        name: http
        tls:
          default:
            hosts:
              - example.org
            secretName: tls-certificate

Everything seems to be fine in this case, we get the following Ingress object:
kind: Ingress
metadata:
  annotations: {}
  labels:
    app.kubernetes.io/component: test
    app.kubernetes.io/instance: test
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: hull-test-3
    app.kubernetes.io/part-of: undefined
    app.kubernetes.io/version: 0.0.0
    helm.sh/chart: hull-test-3-0.0.0
  name: test-hull-test-3-test
  namespace: default
spec:
  rules:
  - host: example.org
    http:
      paths:
      - backend:
          service:
            name: test-hull-test-3-test
            port:
              name: http
        path: /
        pathType: Prefix
  tls:
  - hosts:
    - example.org
    secretName: test-hull-test-3-tls-certificate

The spec.tls part is valid.
But when we try to use a transformation in hull.objects.ingress.*.tls.*.hosts, we have something different.
Here's values.yaml:
hull:
  objects:
    ingress:
      test:
        rules:
          default:
            host: example.org
            http:
              paths:
                root:
                  path: /
                  pathType: Prefix
                  backend:
                    service:
                      name: test
                      port:
                        name: http
        tls:
          default:
            hosts:
              - _HT/util.domainNames.getIngressHostname
            secretName: tls-certificate

The templates/_domain_names.tpl module is simple and straightforward:
{{- define "util.domainNames.getIngressHostname" -}}
example.org
{{- end -}}

In this case we have the following result:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations: {}
  labels:
    app.kubernetes.io/component: test
    app.kubernetes.io/instance: test
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: hull-test-3
    app.kubernetes.io/part-of: undefined
    app.kubernetes.io/version: 0.0.0
    helm.sh/chart: hull-test-3-0.0.0
  name: test-hull-test-3-test
  namespace: default
spec:
  rules:
  - host: example.org
    http:
      paths:
      - backend:
          service:
            name: test-hull-test-3-test
            port:
              name: http
        path: /
        pathType: Prefix
  tls:
  - hosts: example.org
    secretName: test-hull-test-3-tls-certificate

The spec.tls structure is wrong: the hosts parameter has become a string instead of being an array.
What do you think, why does it happen?
Thank you!

I changed _HT/util.domainNames.getIngressHostname to _HT/hosts/util.domainNames.getIngressHostname in values.yaml:
hull:
  objects:
    ingress:
      test:
        rules:
          default:
            host: example.org
            http:
              paths:
                root:
                  path: /
                  pathType: Prefix
                  backend:
                    service:
                      name: test
                      port:
                        name: http
        tls:
          default:
            hosts: _HT/hosts/util.domainNames.getIngressHostname
            secretName: tls-certificate

templates/_domain_names.tpl:
{{- define "util.domainNames.getIngressHostname" -}}
hosts:
- example.org
{{- end -}}

The result:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations: {}
  labels:
    app.kubernetes.io/component: test
    app.kubernetes.io/instance: test
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: hull-test-3
    app.kubernetes.io/part-of: undefined
    app.kubernetes.io/version: 0.0.0
    helm.sh/chart: hull-test-3-0.0.0
  name: test-hull-test-3-test
  namespace: kloudster-control-plane
spec:
  rules:
  - host: example.org
    http:
      paths:
      - backend:
          service:
            name: test-hull-test-3-test
            port:
              name: http
        path: /
        pathType: Prefix
  tls:
  - hosts:
    - example.org
    secretName: test-hull-test-3-tls-certificate

But why does it work this way (when I use a transformation for the whole spec.tls.hosts) and doesn't work that way (when I use a transformation for one element of spec.tls.hosts only)?

Thank you very much for the detailed explanation (and, again, for the great tool you've made)!
If I had been more careful, I would have found #237 without bothering you. If I had been smarter, I would have found the answer in the source code.


Bump nokogiri to 1.14.3

Test pass locally. I'm not sure why all but RuboCop has stopped running on GitHub, with the move from the old publichealthengland/data_management_system repo to ukhsa-collaboration/data_management_system


"is_regular_file" for file trait + integration test

This MR adds the "is_regular_file" and "is_regular_directory"-methods for the File-trait which is especially useful if you work with the generic FileHandle abstraction.
Furthermore, it splits up the existing integration test a little for a clearer separation of concerns. The simple file system protocol test now tests creating a file in the root volume. On this file, I test my newly created additions.
Additionally, FileHandle::into_type now returns a direct value instead of a Result. If we have a failure there, it is a hard-bug in the uefi-rs lib and not something the user should take care of.

Quick notice: I'm currently on vacation and probably won't work on the PRs until the last week of August

This is ready for the next review round.

Ready for another review round @nicholasbishop


Ziggy Script in Comment

Expected Behavior
Load ziggy script first.
Current Behavior
I have some issues with the ziggy script in the server, works fine on local. the script commented and fires and error current is undefined. Is there an option to load the routes first before my app.js?
For bug reports only please provide
Currently installed Laravel version:
5.8.35
Currently installed Ziggy version
0.8.0

Hahaha!


Dump failure with error code:3

after installing Dumberdore_S60_5_X_v_1_0_0.sis in my N86 phone, i can't find "RnD tools" in main meun, also can't run Dumberdore.exe under C:/sys/bin/, it complain "can't open"
I also tried open Dumberdore app, and click "Dump RPKG", it show "Calculate dump size" firstly, then show "Dump failure with error code:3" error message.
How can i dump RPKG successfully?

Yes, sorry for the trouble. I'm resolving it and will give you result as soon as possible!

Thank you very much, no rush! will try your fixing after done!

Hi, I have investigated and it looks like you need to enable the Patch
Open4All in RomPatcherPlus for the dumper to work. Please help me by try
enabling it! If you got success with it then I will add a note in the dump.
Thank you very much!
Vào Th 3, 6 thg 10, 2020 vào lúc 16:32 EinPakistein <
<EMAIL_ADDRESS>đã viết:

Thank you very much, no rush! will try your fixing after done!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EKA2L1/Dumber/issues/5#issuecomment-704149609, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGEGSOVIOEPWXLAWCKCW4Y3SJLPZTANCNFSM4R4ZRSJA
.

Hi, I reinstalled the latest Dumberdore sis/sisx, and enabled "Open4All" in RompatcherPlus.
it shown "Calculate dump size" firstly, then shown "Dump failure with error code:3 (category KERN-EXEC)!" after several seconds.

Yes, it seems Open4All is not all the root cause. I will continue
investigating, but it's very hard to know why without a debugger, so it
might take sometimes. Thank you.
Vào Th 5, 8 thg 10, 2020 vào lúc 16:47 EinPakistein <
<EMAIL_ADDRESS>đã viết:

Hi, I reinstalled the latest Dumberdore sis/sisx, and enabled "Open4All"
in RompatcherPlus.
it shown "Calculate dump size" firstly, then shown "Dump failure with
error code:3 (category KERN-EXEC)!" after several seconds.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EKA2L1/Dumber/issues/5#issuecomment-705458867, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGEGSOUMKCLKBVIQ7DX5UZ3SJWDBZANCNFSM4R4ZRSJA
.

Thank you very much!
I have another question: For now, every user need to dump rom and RPKG on phone by themselves, this look abit complex. Can we share the usable roms and RPKGs on website? or integrate them into EKA2L1 software directly?

That's not something I can answer, since it's questionable about legality.
Sorry.
Vào Th 7, 10 thg 10, 2020 vào lúc 16:52 EinPakistein <
<EMAIL_ADDRESS>đã viết:

Thank you very much!
I have another question: For now, every user need to dump rom and RPKG on
phone by themselves, this look abit complex. Can we share the usable roms
and RPKGs on website? or integrate them into EKA2L1 software directly?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EKA2L1/Dumber/issues/5#issuecomment-706522399, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGEGSOUH67IGEEVDN54TZF3SKAVFBANCNFSM4R4ZRSJA
.

I pushed a new release, integrated from @artem78 . Please check out. If you have the same issue as before, I hope you can help us by setting up a debugger. I will guide you about that when it is needed. Sorry for the inconvenience.

Thank you very much! i'd like to try the latest version and set up debugger if need.
But i can't install the new sis/sisx, i tried to install it, but it required network... for now i have no SIM card for this N86 phone. So i can't install it now.

Can you try copying the SISX from PC to your phone? The SIS dont require any network, so it's weird it requests so. Screenshot me if you can!

Dumber issue snapshots.zip
Hi I uploaded a video for this strange issue, we can see that after i click open botton, the network selection widwon pop up...
I also updated 2 picture about old version issue.

Do you really try to open file with sis extension? Looks weird.

Try to install it using Nokia PC Suite.
------- Первоначальное сообщение -------

От: EinPakistein<EMAIL_ADDRESS>Кому<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Отправлено: 16.10.'20,  20:24
Dumber issue snapshots.zip
Hi I uploaded a video for this strange issue, we can see that after i click open botton, the network selection widwon pop up...
I also updated 2 picture about old version issue.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

can someone tell me how to create a blank site and when you open it wait 5 seconds and then open google ?PLS IM LITTERALY 13 YO

can someone tell me how to create a blank site and when you open it wait 5 seconds and then open google ?PLS IM LITTERALY 13 YO


Update Android.gitignore

Exclude .idea/ dir and *.iml files from Android Studio.
Several sources indicating this is the right thing:

https://code.google.com/p/android/issues/detail?id=156708#c6
https://stackoverflow.com/questions/18415541/android-studio-import-project-with-gradle-changes-iml-files
https://github.com/owncloud/android/blob/master/.gitignore

The link to googlecode is an answer from a Google employee on Android:

For Gradle-based Android projects, Studio uses build.gradle files as its source of truth and generates the iml files based on the project structure defined in build.gradle files. How they get regenerated is in IDEA's functionality.
It is strongly recommended to not include iml in source control.

Thanks, but see Global/JetBrains.gitignore for this

Ah sorry didn't see that!


Raspberry Pi 3: init

Description of changes
Upstream my config for Raspberry PI 3
It's just some config that make it works for me
It's heavily inspired by the file that create sd-image for Aarch64
I don't understand everything of it
Things done

[x] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and importing it via <nixos-hardware> or Flake input

Seems good for me !

@mergify queue


fix: update api & fix comment - tuto create nft

The PrivateKey.generate() API is deprecated, the idea is to
used to update one and this commit fix a wrong comment
Signed-off-by: bwnyasse<EMAIL_ADDRESS>

Thank you @bwnyasse


Unable to load styled component styles at the end of the  tag

Hi
I was using RMWC library with styled components. When I import few component from rmwc, the css files are loading after my styled components styles. How can I load my styled component styles at the end of the head tag?

You can't really, it's determined by load order (judging by a quick scan both SC and RMWC append). Is this causing issues in your project, and if so, can you describe them?

This might help: https://github.com/styled-components/styled-components/pull/2463

You can't really, it's determined by load order (judging by a quick scan both SC and RMWC append). Is this causing issues in your project, and if so, can you describe them?

I have two repositories, One repository which has all the common components and the other repository uses these common components by importing them
I have used npm link to import common code to to current project(The screenshot above refers). The style tags which you see above and below styled component tag are coming from my common repository
Following is my webpack file
webpack.config.js.zip

This might help: #2463

I believe PR is not merged yet.

I believe PR is not merged yet.

Correct. If you can't wait you can use a git commit reference in your package.json.

I believe PR is not merged yet.

Correct. If you can't wait you can use a git commit reference in your package.json.

When will this PR get merged?

It's not high priority so probably will be a 5.1 candidate PR

I have the same problem. It's work correct with my own Webpack config. I find this problem after I migrate to create-react-app.

I have the same problem. It's work correct with my own Webpack config. I find this problem after I migrate to create-react-app.

@GFwer can you share your webpack file

It's not high priority so probably will be a 5.1 candidate PR

Any update on this? Is it available in 5.1?

Don't think that this is still actuall, but for me this solution fixed the problem. At the point of initialization ThemeProvider and Styles Provider here is injectFirst flag:
<StylesProvider injectFirst>
which is move all default styles of mui to top of the head. Found solution here: https://gist.github.com/Danilo-Araujo-Silva/2ce11fd0540dcc7eb3ad3e67fd75d02a#gistcomment-2935337

Still having the problem in Sep. 2021