[MP Product Plan]  2021 MicroProfile Program Plan Slide Deck -  Spanish Version

Make available: 2021 MicroProfile Program Plan Slide Deck:
https://docs.google.com/presentation/d/1-mu4dIsfAzLlE81splWBKwsGeRLJhzEWrXgsQ_i0JZQ/edit#slide=id.gb4cf2bb036_0_0
WIP here:
https://docs.google.com/presentation/d/15VlF895lpclxdvv1HlRD3hNxi0R2YexQ3MguqB4arH0/edit#slide=id.p

A First Draft:
https://docs.google.com/presentation/d/1-OrSEgEeU39OIxmlXZd1suMQEKJRmjbUzqIO2OyZC2g/edit?usp=sharing

@emecas,
Just beautiful.
Emerson, can you please add in the notes of page 2, first thing, Translated by Emerson?
It is view only so I cannot help with review nor adding such suggestions.

@aeiras, I thought it was accessible, I've update permissions and moved it to the Community folder, so you can review / edit. thx

It works Emerson.
I added you and will provide extra eyes after the program has been approved. :)
So fun!

Hola @emecas,
We ought to finalize the Spanish translation so that it can be added to the MPWG page in the website.
How much time do you think MicroProfilers need to collaborate on the review?  2 weeks from next Monday?
Whats your preference?

@aeiras, I have a question, is this the final version of the document?
I'm asking because my impression based on the last 2 meetings has been that it could get some changes, but it is also true that the strategic goals are described in a high level to keep them intact,  anyways, I will give another round to the first translation  draft before our next meeting. And Yes, I think  2 weeks after that are more than enough for reviewing it

Dias Emerson,
Yes, that is the voted and approved final version that we need to use to also finalized your wonderful document.

Dias Emerson,
Yes, that is the voted and approved final version that we need to use to also finalize your wonderful document.

Done @aeiras , I finished final adjustments for the Spanish translation for the 2021 MicroProfile Program Plan Slide Deck, How do you think we should handle/invite to the review?

Hola Emerson,
If I were you, I would send a new thread to the MP general forum with 1 to max 2 sentences that include the link of this ticket and the slides' link. It includes the March 29th welcome feedback deadline and makes it a call to action to all Spanish-speaking MicroProfilers in the forum. I would write that short message and the title of the email in Spanish, not 1 word in English.
However, you can and ought to always do whatever you feel/think you can own (your contributor signature is yours to bear) to help close the amazing contribution you are making possible.
You are likely to inspire other MicroProfilers to translate the slides as well. Let's see.

Oh and I will help you with the review. You have 1 helper already :) But I won't re-start until you choose how to push the close up.

Oh and I will help you with the review. You have 1 helper already :) But I won't re-start until you choose how to push the close up.

Thank you @aeiras for the suggestion, here is the new thread: https://groups.google.com/g/microprofile/c/hCBSh-CdDnI

So wonderful. I have scheduled to work on it this week, Emerson. Thanks for making it possible.

Hi @emecas
I did the first review of the current status of the slides and applied a couple of updates.
I left a couple of comments too.

Hi @emecas
I did the first review of the current status of the slides and applied a couple of updates.
I left a couple of comments too.

Thank you @cesarhernandezgt , I just noticed the document you where you added  comments is not the latest one, be sure using this one: https://docs.google.com/presentation/d/1-OrSEgEeU39OIxmlXZd1suMQEKJRmjbUzqIO2OyZC2g/edit#slide=id.gbe60ace8dc_0_69

Thanks for the new references @emecas, I just move my feedback to the new document. Since Google slides don't have "suggestion" mode like Docs has, the only way to see my changes is by selecting the history of the slides.

@emecas,
I have fun re-reading the slides. Like @cesarhernandezgt stated, there is no way to "suggest edit" on google slides, so I modify a few words. The current draft has greatly improved. You are just wow!
With this task, you have helped us improved the original slides in a few sections like Duke's logo, bookmarks with trademark, tracking on approval of the original document, etc.
Thank you for being so fun on lowering the bar so that the Latin Armada can join and contribute to MP. :)

I am getting "You need access" message now, is this intentional, @emecas?

I am getting "You need access" message now, is this intentional, @emecas?

@mehmandarov  No intentional at all, Thank you for letting me know,  it seems it is a problem with the permissions, meanwhile may you try this link: https://docs.google.com/presentation/d/e/2PACX-1vQA322Lkoxs10BUCWfNFituhpSUoMCb2adBw-fk1cz13_dFqDLvw49_RvYpDVtvLq_4qQqWDyxj01Jl/pub?start=false&loop=false&delayms=3000

Thank you! These links work!

Final folder: https://drive.google.com/drive/folders/1hj-o5s2-LXBpuw0h_xKkJVQ-iz265K6C
PDF: https://drive.google.com/file/d/1ENJIhBRnrJMQuBiSY1mNw-iX1EY_9PNj/view?usp=sharing


Default to the same extensions as GHC

The following function is part of a module.
type Trio = (Maybe Integer, String, String)

parse :: String -> Trio
parse text = (n, op, s)
  where
    pattern = "[-]?[[:digit:]]+"
    (prefix, num, suffix) = text =~ pattern :: (String, String, String)
    trim = T.unpack . T.strip . T.pack
    n = R.readMaybe $ trim num
    op = trim prefix
    s = trim suffix

This compiles and works for the given test cases, but hlint emits an error.
Error: Parse error: on input `='
Found:
    parse text = (n, op, s)
      where
  >     pattern = "[-]?[[:digit:]]+"
        (prefix, num, suffix) = text =~ pattern :: (String, String, String)
        trim = T.unpack . T.strip . T.pack

I've gone through most of the tickets that reported similar errors, and the suggestion is to disable TemplateHaskell using the pragma {-# LANGUAGE NoTemplateHaskell #-}. However, that doesn't help in this case.

I can confirm that using the pragma {-# LANGUAGE NoPatternSynonyms #-} fixes the error. Can hlint not turn on language extensions magically?

@asarkar HLint could do anything it wanted. But it's a balance - do we break more users by turning on PatternSynonyms, or fix more users? I think the view is that it fixes more users than it breaks, so on by default is the right default. If you pass -XHaskell2020 or similar I think it restricts you to a specific language standard, so you can opt in to following a standard rather than the default behaviour.

What I don’t understand, perhaps from my lack of experience working with Haskell, is that why hlint can’t use the user-provided configuration, if any, instead of imposing its own opinion about what’s good for the user?

hlint will use the user provided configuration if it is given one. as @ndmitchell  recommend pass -XGhc2021 (or -XHaskell2010 or -XHaskell98`) to hlint. doing this you have precisely specified what base set of extensions are enabled.

GHC2021 is used by GHC if neither Haskell98 nor Haskell2010 is turned on explicitly.

It seems to be the default without me having to specify explicitly. That’s the way I’d like to keep it, so that the code is always compatible with the latest language specification.

GHC2021 is used by GHC if neither Haskell98 nor Haskell2010 is turned on explicitly.

It seems to be the default without me having to specify explicitly. That’s the way I’d like to keep it, so that the code is always compatible with the latest language specification. Notably, PatternSynonyms is not enabled by GHC2021.

if no language specifier is provide hlint constructs its own set of extensions to default enable. that set enables more extensions than GHC would default enable if not invoked with an explicit language specifier.

the default behavior is chosen for hlint is to parse as many files as possible (i.e. default behavior = not give a language specifier).

if no language specifier is provided hlint constructs its own set of extensions

... which is different from what GHC chooses, hence the problem. Why not choose the default the same as GHC?

hlint to parse as many files as possible

Is there any substantiated data that shows the difference between hlint chosen extensions and GHC chosen extensions? In other words, can it be shown that the if hlint chose the same default extensions as GHC, it'd fail to parse x% of files?

if no language specifier is provided hlint constructs its own set of extensions

... which is different from what GHC chooses, hence the problem. Why not choose the default the same as GHC?

i agree this a reasonable proposition.

hlint to parse as many files as possible

Is there any substantiated data that shows the difference between hlint chosen extensions and GHC chosen extensions? In other words, can it be shown that the if hlint chose the same default extensions as GHC, it'd fail to parse x% of files?

i don't know about that.

Now that we have established this ticket has a valid point, I’ve updated the title to better suit the problem.

turn on most

There’s a definitive list of the extensions enabled by default by GHC. What this ticket is asking is for hlint to use that list instead of making up its own. Is that what you referred to as hard, almost impossible?

No, the list of extensions enabled by GHC in your project is based on those defined in Cabal, Stack, command line flags and elsewhere. We can get the list of extensions enabled if you type ghc, but since that doesn't work in most projects, it's not that helpful. What we want is to approximate the extensions enabled in your project.

I'm not sure what you mean. Consider the case that Steve has a project. In his .cabal file he has the extension PatternSynonyms enabled. Currently HLint works. If I follow the same default as GHC, it would not. Audrey has a project, he uses a custom build system like Bazel, and in herproject he has TemplateHaskell turned on in the .bazelconfig that applies to every project in her megarepo. Currently HLint works, but with the same default as GHC, it doesn't. My understanding based on talking to users is that if HLint defaulted to what GHC does (which you can do with a .hlint.yaml file if you want), then fewer projects would work out of the box.

In his .cabal file he has the extension PatternSynonyms enabled. Currently HLint works. If I follow the same default as GHC, it would not

If user has enabled any extensions, then hlint won't fallback to defaults. All I'm saying is that when the user hasn't enabled any extensions, GHC defaults and hlint defaults aren't the same.

I don't follow. In the .cabal file the user has enabled PatternSynonyms. What should HLint do?

If user has enabled any extensions, then hlint won't fallback to defaults

How do we detect if a user has enabled any extensions in their .cabal/stack/bazel projects?


ToDo: diffs FF61-FF62b6

FF62 is scheduled for release 5th Sept
misc

[x] :exclamation: change cookie behavior & deletion prefs - see #479 #439 - https://github.com/ghacksuserjs/ghacks-user.js/commit/572d16d5a5863c08da5ed3b96f96d1effba3eeb8
[x] remove [SETTING-ESR52] lines - https://github.com/ghacksuserjs/ghacks-user.js/commit/ab404680dfc07f192dd8ead1660657689f3788e0
[x] disable IPv6 - https://github.com/ghacksuserjs/ghacks-user.js/commit/5b6ed92da4a9eb31160b96acb1ebc1541d78da7d
[x] enforce IDB=true - https://github.com/ghacksuserjs/ghacks-user.js/commit/9e67f982abd3759d93ec6c2b9a694c5c8848b5e9
[ ] do something with 1700s (containers)
FF63: 1409664 media.mediacapabilities.enabled - don't want to lose track of this, so dumping here (make sure it carries over to 63 diffs)

123 diffs ( 47 new, 44 gone, 32 different )
new in v62.0b6:

pref("extensions.systemAddon.update.enabled", true); 0505

pref("browser.history_swipe_animation.disabled", false);
pref("browser.newtabpage.activity-stream.asrouterOnboardingCohort", 0);
pref("browser.security.newcerterrorpage.enabled", false);
pref("browser.sessionstore.resuming_after_os_restart", false);
pref("browser.tabs.multiselect", false);
pref("browser.tabs.remote.tabCacheSize", 0);
pref("devtools.debugger.pause-on-caught-exceptions", true);
pref("devtools.inspector.fonthighlighter.enabled", false);
pref("devtools.inspector.three-pane-first-run", true);
pref("devtools.webconsole.jsterm.codeMirror", false);
pref("dom.clearSiteData.enabled", false);
pref("dom.mutation-events.cssom.disabled", true);
pref("dom.serviceWorkers.parent_intercept", false);
pref("dom.webcomponents.shadowdom.report_usage", false);
pref("extensions.webextensions.ExtensionStorageIDB.enabled", false);
pref("gfx.webrender.program-binary-disk", true);
pref("image.animated.resume-from-last-displayed", true);
pref("io.activity.intervalMilliseconds", 0);
pref("layout.accessiblecaret.script_change_update_mode", 0);
pref("layout.css.scrollbar-colors.enabled", false);
pref("layout.css.webkit-appearance.enabled", false);
pref("layout.css.xul-display-values.content.enabled", false);
pref("network.cookie.maxNumber", 3000);
pref("network.cookie.maxPerHost", 180);
pref("network.sts.poll_busy_wait_period", 50);
pref("network.sts.poll_busy_wait_period_timeout", 7);
pref("network.sts.pollable_event_timeout", 6);
pref("pdfjs.scrollModeOnLoad", 0);
pref("pdfjs.spreadModeOnLoad", 0);
pref("print.font-variations-as-paths", true);
pref("privacy.trackingprotection.storagerestriction.enabled", false);
pref("services.sync.engine.bookmarks.validation.enabled", true);
pref("services.sync.engine.passwords.validation.enabled", true);
pref("toolkit.winRegisterApplicationRestart", false);

removed, renamed or hidden in v62.0b6:

[x] pref("browser.urlbar.autoFill.typed", true); - 1239708 - https://github.com/ghacksuserjs/ghacks-user.js/commit/776e32c27f286d6260348cf9a00b607c0493637d

note: we REMOVED this from our user.js as it's already covered by browser.urlbar.autoFill

[ ] pref("plugin.state.java", 1);

changed in v62.0b6:

pref("browser.cache.offline.insecure.enable", false); // prev: true 2730b
pref("geo.wifi.uri", "https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%"); // prev: "https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY%" 0210
pref("startup.homepage_welcome_url", "about:welcome"); // prev: "https://www.mozilla.org/%LOCALE%/firefox/%VERSION%/firstrun/" 5000

pref("apz.android.chrome_fling_physics.enabled", true); // prev: false
pref("browser.newtabpage.activity-stream.telemetry.ut.events", true); // prev: false
pref("devtools.debugger.ignore-caught-exceptions", true); // prev: false
pref("devtools.new-animationinspector.enabled", true); // prev: false
pref("dom.ipc.plugins.sandbox-level.flash", 3); // prev: 2
pref("dom.keyboardevent.dispatch_during_composition", true); // prev: false
pref("dom.registerContentHandler.enabled", false); // prev: true
pref("dom.registerProtocolHandler.insecure.enabled", false); // prev: true
pref("extensions.geckoProfiler.getSymbolRules", "localBreakpad,dump_syms.exe"); // prev: "localBreakpad,remoteBreakpad,dump_syms.exe"
pref("gfx.webrender.async-scene-build", true); // prev: 2
pref("image.animated.decode-on-demand.threshold-kb", 20480); // prev: 4194303
pref("layers.enable-tiles-if-skia-pomtp", true); // prev: false
pref("layout.css.moz-document.url-prefix-hack.enabled", false); // prev: true
pref("layout.css.shape-outside.enabled", true); // prev: false
pref("layout.display-list.retain", true); // prev: false
pref("network.tcp.tcp_fastopen_enable", true); // prev: false
pref("security.pki.name_matching_mode", 3); // prev: 1

ignore
click me for details
==NEW
pref("browser.newtabpage.activity-stream.section.highlights.rows", 2);
pref("browser.newtabpage.activity-stream.section.topstories.rows", 1);
pref("browser.safebrowsing.provider.mozilla.lists.base", "moz-std");
pref("browser.safebrowsing.provider.mozilla.lists.content", "moz-full");
pref("gfx.webrender.debug.echo-driver-messages", false);
pref("gfx.webrender.debug.new-frame-indicator", false);
pref("gfx.webrender.debug.new-scene-indicator", false);
pref("services.blocklist.addons.signer", "remote-settings.content-signature.mozilla.org");
pref("services.blocklist.gfx.signer", "remote-settings.content-signature.mozilla.org");
pref("services.blocklist.onecrl.signer", "onecrl.content-signature.mozilla.org");
pref("services.blocklist.pinning.signer", "pinning-preload.content-signature.mozilla.org");
pref("services.blocklist.plugins.signer", "remote-settings.content-signature.mozilla.org");

==REMOVED or HIDDEN
pref("browser.EULA.version", 3);
pref("browser.rights.3.shown", false);
pref("browser.rights.version", 3);
pref("browser.safebrowsing.provider.mozilla.lists.base.description", "mozstdDesc");
pref("browser.safebrowsing.provider.mozilla.lists.base.name", "mozstdName");
pref("browser.safebrowsing.provider.mozilla.lists.content.description", "mozfullDesc2");
pref("browser.safebrowsing.provider.mozilla.lists.content.name", "mozfullName");
pref("browser.search.defaultenginename", "chrome://browser-region/locale/region.properties");
pref("browser.search.defaultenginename.US", "data:text/plain,browser.search.defaultenginename.US=Google");
pref("browser.search.order.1", "chrome://browser-region/locale/region.properties");
pref("browser.search.order.2", "chrome://browser-region/locale/region.properties");
pref("browser.search.order.3", "chrome://browser-region/locale/region.properties");
pref("browser.search.order.US.1", "data:text/plain,browser.search.order.US.1=Google");
pref("browser.search.order.US.2", "data:text/plain,browser.search.order.US.2=Bing");
pref("browser.snapshots.limit", 0);
pref("devtools.devedition.promo.enabled", false);
pref("devtools.devedition.promo.shown", false);
pref("devtools.devedition.promo.url", "https://www.mozilla.org/firefox/developer/?utm_source=firefox-dev-tools&utm_medium=firefox-browser&utm_content=betadoorhanger");
pref("devtools.inspector.three-pane-toggle", false);
pref("devtools.telemetry.tools.opened.version", "{}");
pref("devtools.toolbar.enabled", true);
pref("devtools.toolbar.visible", false);
pref("devtools.webconsole.autoMultiline", true);
pref("extensions.geckoProfiler.symbols.url", "http://symbols.mozilla.org/");
pref("extensions.minCompatibleAppVersion", "4.0");
pref("extensions.minCompatiblePlatformVersion", "2.0");
pref("geo.provider.ms-windows-location", false);
pref("gfx.webrender.all", false);
pref("gfx.webrender.enabled", false);
pref("gfx.webrender.hit-test", true);
pref("hangmonitor.timeout", 0);
pref("image.mem.max_decoded_image_kb", 256000);
pref("javascript.options.array_prototype_values", true);
pref("layout.accessiblecaret.allow_script_change_updates", false);
pref("layout.css.getPropertyCSSValue.enabled", false);
pref("layout.css.text-combine-upright-digits.enabled", false);
pref("layout.event-regions.enabled", false);
pref("network.activity.intervalMilliseconds", 0);
pref("network.dir.format", 2);
pref("plugin.java.mime", "application/x-java-vm");
pref("security.allow_chrome_frames_inside_content", false);
pref("security.OCSP.GET.enabled", false);

==CHANGED
pref("app.update.channel", "beta"); // prev: "release"
pref("app.update.url.details", "https://www.mozilla.org/%LOCALE%/firefox/beta/notes"); // prev: "https://www.mozilla.org/%LOCALE%/firefox/notes"
pref("app.update.url.manual", "https://www.mozilla.org/firefox/beta"); // prev: "https://www.mozilla.org/firefox/"
pref("browser.cache.disk.max_chunks_memory_usage", 40960); // prev: 10240
pref("browser.cache.disk.max_priority_chunks_memory_usage", 40960); // prev: 10240
pref("device.sensors.ambientLight.enabled", false); // prev: true
pref("device.sensors.proximity.enabled", false); // prev: true
pref("devtools.inspector.show-three-pane-tooltip", true); // prev: false
pref("devtools.inspector.three-pane-enabled", true); // prev: false
pref("devtools.toolbox.previousHost", "right"); // prev: "side"
pref("network.trr.blacklist-duration", 60); // prev: 1200
pref("toolkit.telemetry.enabled", true); // prev: false

bugzilla tickets for some of the remaining prefs

apz.android.chrome_fling_physics.enabled
Bug 1460206 - Let the new Android fling physics ride the trains.
Bug 1459293 - Enable new Android fling physics on the Nightly channel.
Bug 1448439 - Add a pref to get APZ to use the Chrome fling physics on Android.

browser.cache.disk.max_chunks_memory_usage
Bug 1457084 - Increase max chunk memory usage limit,

browser.cache.disk.max_priority_chunks_memory_usage
Bug 1457084 - Increase max chunk memory usage limit,

browser.cache.offline.insecure.enable
Bug 1460478 - Remove support for AppCache in stable.

browser.EULA.version
Bug 1409054 - Remove code from the old about:home.

browser.history_swipe_animation.disabled
Bug 860493: Add pref to disable history swipe animations.

browser.rights.3.shown
Bug 1409054 - Remove code from the old about:home.

browser.rights.version
Bug 1409054 - Remove code from the old about:home.

browser.safebrowsing.provider.mozilla.lists.base
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.safebrowsing.provider.mozilla.lists.base.description
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.safebrowsing.provider.mozilla.lists.base.name
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.safebrowsing.provider.mozilla.lists.content
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.safebrowsing.provider.mozilla.lists.content.description
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.safebrowsing.provider.mozilla.lists.content.name
Bug 1457021 - Migrate the JS of Preferences::Blocklists to Fluent.

browser.search.defaultenginename
Bug 1352539 - Move default search engine to list.json.
Bug 1417678 - New search defaults for browser and mobile.

browser.search.defaultenginename.US
Bug 1352539 - Move default search engine to list.json.
Bug 1417678 - New search defaults for browser and mobile.

browser.search.order.1
Bug 1461345 - Move browser.search.order to list.json.

browser.search.order.2
Bug 1461345 - Move browser.search.order to list.json.

browser.search.order.3
Bug 1461345 - Move browser.search.order to list.json.

browser.search.order.US.1
Bug 1461345 - Move browser.search.order to list.json.
Bug 1417678 - New search defaults for browser and mobile.

browser.search.order.US.2
Bug 1461345 - Move browser.search.order to list.json.
Bug 1442738 - Update default search config.
Bug 1417678 - New search defaults for browser and mobile.

browser.security.newcerterrorpage.enabled
Bug 1463748 - Fork and pref-off the new error pages

browser.sessionstore.resuming_after_os_restart
Bug 603903 - Part 2: restore session when restarted by Windows

browser.snapshots.limit
Bug 860493: Add pref to disable history swipe animations.

browser.tabs.multiselect
Bug 1458010 - Add ability to select multiple tabs using Ctrl/Cmd.

browser.tabs.remote.tabCacheSize
Bug 1465106 - Disable tab layer cache
Bug 1176019 - Cache layers of background tabs

browser.urlbar.autoFill.typed
Bug 1239708: Improve awesomebar autofill. Part 3: Front-end changes.

device.sensors.ambientLight.enabled
Bug 1462308 - Disable all Device Sensor events except orientation by default for stable.

device.sensors.proximity.enabled
Bug 1462308 - Disable all Device Sensor events except orientation by default for stable.

devtools.devedition.promo.enabled
Bug 1463924 - Remove Dev. Edition promo doorhanger.

devtools.devedition.promo.shown
Bug 1463924 - Remove Dev. Edition promo doorhanger.

devtools.devedition.promo.url
Bug 1463924 - Remove Dev. Edition promo doorhanger.

devtools.inspector.fonthighlighter.enabled
Bug 1440855 - New font text-run highlighter used from the font inspector;r=gl

devtools.inspector.show-three-pane-tooltip
Bug 1467564 - Only show the 3 pane tooltip in release or beta.
Bug 1464233 - Allow 3 pane inspector to ride the trains.
Bug 1433718 - Enable 3 pane inspector in nightly and make unit tests pass.
Bug 1433718 - Make unit tests pass with the 3 pane inspector on in nightly.
Bug 1446944 - Provide onboarding tooltip for the 3 pane inspector feature.

devtools.inspector.three-pane-enabled
Bug 1464233 - Allow 3 pane inspector to ride the trains.
Bug 1433718 - Enable 3 pane inspector in nightly and make unit tests pass.
Bug 1433718 - Make unit tests pass with the 3 pane inspector on in nightly.

devtools.inspector.three-pane-first-run
Bug 1468495 - Reset the inspector widths for the first run of 3 pane inspector.

devtools.inspector.three-pane-toggle
Bug 1462451 - Remove checks for the 3 pane toggle button.

devtools.new-animationinspector.enabled
Bug 1470807: Enable new animation inspector on Beta and Release channel.

devtools.telemetry.tools.opened.version
Bug 1296723 - Remove logOncePerBrowserVersion telemetry functions and probes

devtools.toolbar.enabled
Bug 1461970 - Removing DeveloperToolbar, its menu, its pref and everything using gDevToolsBrowser.getDeveloperToolbar.

devtools.toolbox.previousHost
Bug 1192642 - Add a left host type for the toolbox.

devtools.webconsole.autoMultiline
Bug 1464476 - Remove devtools.webconsole.autoMultiline preference;

devtools.webconsole.jsterm.codeMirror
Bug 1463409 - Add a preference to enable CodeMirror-powered jsterm;

dom.clearSiteData.enabled
Bug 1268889 - Implement Clear-Site-Data header - part 2 - pref,

dom.ipc.plugins.sandbox-level.flash
Bug 1366256 - Part 1: Promote Windows plugin process sandbox to level 3.
Bug 1433577 - [Mac] Enable sandboxing for the Flash NPAPI plugin process on Nightly;
Bug 1366256: Part 1 - Promote Windows plugin process sandbox to level 3
Bug 1444291 - Part 3 - Add read access to the Mac Flash sandbox, support sandbox levels

dom.keyboardevent.dispatch_during_composition
Bug 1446401 - Start to dispatch "keydown" event and "keyup" event even during in composition in Nightly and early Beta

dom.mutation-events.cssom.disabled
Bug 1460295 - Don't dispatch mutation event for style attribute change from CSSOM.

dom.registerContentHandler.enabled
Bug 1460481 - Disable registerContentHandler from stable releases.

dom.registerProtocolHandler.insecure.enabled
Bug 1460506 - Restrict registerProtocolHandler over insecure connections in stable releases.

dom.serviceWorkers.parent_intercept
Bug 1469024 Define service worker parent intercept pref in StaticPrefList and read it once at startup.

dom.webcomponents.shadowdom.report_usage
Bug 1461278 - Print a note to the web console when a web site is using shadow DOM (v1), preffed off by default,

extensions.geckoProfiler.getSymbolRules
Bug 1461056 - Remove the "remoteBreakpad" symbol rule, because it's no longer needed.
Bug 1441051 - Automatically invoke dump_syms.exe on Windows when the profiler asks for symbol tables.

extensions.geckoProfiler.symbols.url
Bug 1461056 - Remove unneeded function urlForSymFile.

extensions.minCompatibleAppVersion
Bug 1461216: Remove minCompatible*Version preferences.

extensions.minCompatiblePlatformVersion
Bug 1461216: Remove minCompatible*Version preferences.

extensions.systemAddon.update.enabled
Bug 1428459 - Divorce system add-ons from app.update prefs

extensions.webextensions.ExtensionStorageIDB.enabled
Bug 1406181 - Add ExtensionStorageIDB JSM module.

gfx.webrender.async-scene-build
Bug 1452845 - Turn on async scene building by default.
Bug 1391318 - Automatically enable async scene building with webrender.all.
Bug 1451469 - Complete hooking up of the sampler thread.

gfx.webrender.debug.echo-driver-messages
Bug 1469041 - Expose WebRender's frame/scene debug indicators.

gfx.webrender.debug.new-frame-indicator
Bug 1469041 - Expose WebRender's frame/scene debug indicators.

gfx.webrender.debug.new-scene-indicator
Bug 1469041 - Expose WebRender's frame/scene debug indicators.

gfx.webrender.hit-test
Bug 1436409 - Remove gecko/APZ hit-test codepath from WebRenderCommandBuilder.

gfx.webrender.program-binary-disk
Bug 1418202 - Serialize ProgramBinary to/from blob/disk

hangmonitor.timeout
Bug 1448040 - Remove HangMonitor/ChromeHangs

image.animated.decode-on-demand.threshold-kb
Bug 1460258 - Re-enable discarding of animated image frames.
Bug 1454824 - Disable discarding of animated image frames due to high CPU consumption.

image.animated.resume-from-last-displayed
Bug 1454149 - Do not advance animated images which are not displayed.

image.mem.max_decoded_image_kb
Bug 1335148 - Part 4: Remove unused max_decoded_image_kb pref.

io.activity.intervalMilliseconds
Bug 1447931 - NetworkActivity becomes IOActivity -

javascript.options.array_prototype_values
Bug 1469540 - Remove option to disable Array.prototype.values.

layers.enable-tiles-if-skia-pomtp
Bug 1454978 - Enable tiled parallel OMTP when we are using skia on windows on nightly.
Bug 1454978 - Cleanup tiling prefs in all.js.
Bug 1438551 - Add a pref for enabling tiles when we are using skia with parallel painting.

layout.accessiblecaret.allow_script_change_updates
Bug 1463576 - 1. Add layout.accessiblecaret.script_change_update_mode pref;

layout.accessiblecaret.script_change_update_mode
Bug 1463576 - 1. Add layout.accessiblecaret.script_change_update_mode pref;

layout.css.getPropertyCSSValue.enabled
Bug 1408301: Remove getPropertyCSSValue.
Bug 1461092 - Unship GetPropertyCSSValue in Firefox 61.
Bug 1448415: Hide getPropertyCSSValue on nightly.

layout.css.moz-document.url-prefix-hack.enabled
Bug 1448225 - Convert StylePrefs to StaticPrefs.
Bug 1446470: Add another pref to control the url-prefix hack.

layout.css.scrollbar-colors.enabled
Bug 1460456 part 3 - Add scrollbar-{face,track}-color properties.

layout.css.shape-outside.enabled
Bug 1457297: Turn pref layout.css.shape-outside.enabled on by default for all channels.
Bug 1353631 Part 1: Set preference default to true in Nightly for layout.css.shape-outside.enabled.
Bug 1353631: Set preference default to true in Nightly for layout.css.shape-outside.enabled.

layout.css.text-combine-upright-digits.enabled
Bug 1457373 - Remove text-combine-upright digits option -

layout.css.webkit-appearance.enabled
Bug 1429713 part 1 - Add a -webkit-appearance alias for -moz-appearance (behind a pref).

layout.css.xul-display-values.content.enabled
Bug 1288572: Hide -moz- display values from content behind a pref.

layout.display-list.retain
Bug 1467530 - Disable retained display lists by default for Firefox 61.

layout.event-regions.enabled
Bug 1436409 - Remove the layout.event-regions.enabled pref and bake it in as false everywhere.

network.activity.intervalMilliseconds
Bug 1447931 - NetworkActivity becomes IOActivity -

network.cookie.maxNumber
Bug 1460251 - Up cookie limit to 180 per host and expose prefs.

network.cookie.maxPerHost
Bug 1460251 - Up cookie limit to 180 per host and expose prefs.

network.dir.format
Bug 833098: Part 1 - Remove dead code in xpfe directory viewer.

network.sts.poll_busy_wait_period
Bug 1442178 - Do a busy wait of socket poll() shortly after network change detection,

network.sts.poll_busy_wait_period_timeout
Bug 1442178 - Do a busy wait of socket poll() shortly after network change detection,

network.sts.pollable_event_timeout
Bug 1442178 - Repair broken socket polling wakeup mechanism after a network change to prevent long load hangs,

network.trr.blacklist-duration
bug 1470005 - change default TRR blacklist duration to 60 seconds
bug 1451011 - expire TRR blacklist entries after 20 minutes by default

plugin.java.mime
Bug 1461243 - Part 5: Stub out obsolete DOM API navigator.javaEnabled(). r=jimm

plugin.state.java
Bug 1461243 - Part 5: Stub out obsolete DOM API navigator.javaEnabled(). r=jimm

print.font-variations-as-paths
Bug 1464094 - print font variations as paths for PDF/PS output.

privacy.trackingprotection.storagerestriction.enabled
Bug 1461921 - Block storage access for third-parties on the tracking protection list - part 1 - Pref and Blocking check,

security.OCSP.GET.enabled
bug 1456489 - prevent making OCSP requests on the main thread

security.pki.name_matching_mode
Bug 1463936 - Set default security.pki.name_matching_mode to enforce (3) for all builds.
Bug 1461373 - Set BRNameMatchingPolicy to "Enforce" for Nightly

services.blocklist.addons.signer
Bug 1460321 - Change addons/plugins/gfx blocklist content-signature certificate
Bug 1461750 - Backout blocklist signature verification from Firefox 61.
Bug 1450985 - Enable signature verification for addons/gfx/plugins blocklists

services.blocklist.gfx.signer
Bug 1460321 - Change addons/plugins/gfx blocklist content-signature certificate
Bug 1461750 - Backout blocklist signature verification from Firefox 61.
Bug 1450985 - Enable signature verification for addons/gfx/plugins blocklists

services.blocklist.onecrl.signer
Bug 1461750 - Backout blocklist signature verification from Firefox 61.
Bug 1450985 - Enable signature verification for addons/gfx/plugins blocklists

services.blocklist.pinning.signer
Bug 1461750 - Backout blocklist signature verification from Firefox 61.
Bug 1450985 - Enable signature verification for addons/gfx/plugins blocklists

services.blocklist.plugins.signer
Bug 1460321 - Change addons/plugins/gfx blocklist content-signature certificate
Bug 1461750 - Backout blocklist signature verification from Firefox 61.
Bug 1450985 - Enable signature verification for addons/gfx/plugins blocklists

toolkit.winRegisterApplicationRestart
Bug 603903 - Part 1: add RegisterApplicationRestart

yay! another small one

huh .. tying tracking protection to the cookie pref? I mean I get it, kinda (I use cookies to control localStorage & IDB), but I don't follow why they would tie it directly to that setting. Am trying to read that diff.
So users who block all cookies can't use TP (or any of the other TP lists they are going to add)? That's not very nice of them. I get that it currently only applies to cookies, but future lists included non-cookie stuff IIRC

users who block all cookies can't use TP

You can use TP and block all cookies just fine AFAIK. ATM there are 2 kinds of TP, active and passive. Active TP will completely block requests (which could theoretically also try to set a cookie) while passive TP will just prevent the cookie from being set. At least that's how I think it works.
Seems like a nice option for people who don't want to allow everything (0=allow all cookies and site data) but for whom 1st-party-only breaks too many of their favorite sites.
Maybe one day mozilla will make it the new default value instead of 0.

Time will tell, it's all as clear as mud ATM to me. I'm still not sure how they can reconcile TP's state with a defined cookie default. eg

network.cookie.cookieBehavior=0 - you block all cookies
network.cookie.cookieBehavior=1,2,3 - you allow all or some cookies

So if you block all cookies, but allow a site exception, how can TP know whether it's allowed to kick in or not. The reverse don't matter (eg blocking cookies as a site exception). Because that's the only difference I see in the cookie pref - allow-all-some vs block
I think I'm confusing this with privacy.trackingprotection.*.enabled which still remains as the on/off switch, and the new setup is just about domains in TP lists and how to handle those domains's cookies + localStorage etc

[ ] do something with 1700s (containers)

I'd rather NOT do something with containers just yet. Users can enable it if they want but we shouldn't enable it by default for everyone because there are probably reasons why mozilla are still keeping it disabled.

Well, I ain't got to it yet. My first thing to check was what the defaults are in FF62, and ESR60. I thought that they were enabled - in which case I was going to propose maybe removing the section (and shoving 1704 to personal). Anyway... lemme go check the defaults

the only one that is on by default is 1703 which doesn't really matter.

@earthlng what is the default for privacy.usercontext.about_newtab_segregation.enabled in ESR60.x ? If it's true then we could remove this pref?

default is false in 60.1.0ESR. It was changed to true in FF61 and ESR is based on FF60 so it makes sense that it's still false in ESR because they very rarely change prefs in ESR.

oh okay, I just explained it a bit more because 3 hours ago you wrote:

on FF61 (and I'll just assume ESR60 is the same), the only one that is on by default is 1703

^^that's what "assumption" means - hence I asked you (IDK, I just always go to you for ESR stuff). Anyway, screw this .. time for some food and bed

They'll set fallback-limit pref to TLS 1.3 by default for Firefox 62 and IMO we can just remove that pref from the user.js because it's not necessary to enforce the default. plus: "We're on the road to remove that code"

^^ added to changed in OP (cuz it wasn't there yet, just so you're aware)

moved from new to ignore -> new:

all the activity-stream shit since it's still possible to delete the system addon. FF63+ will have it built-in and we'll deal with it then
pref("browser.security.newcerterrorpage.enabled", false); - wait until they enable it by default
pref("browser.tabs.multiselect", false); - not privacy/security related
pref("devtools.inspector.fonthighlighter.enabled", false);
pref("devtools.inspector.three-pane-first-run", true);
pref("dom.webcomponents.shadowdom.report_usage", false);
probably nightly-only. We'll see it in the diffs if they ever change it to true in beta or release
pref("extensions.webextensions.ExtensionStorageIDB.enabled", false); - see my comment
pref("privacy.trackingprotection.storagerestriction.enabled", false); - see my comment

moved from changed to ignore -> changed:

pref("apz.android.chrome_fling_physics.enabled", true); // prev: false - Android only. IDGAF
pref("dom.ipc.plugins.sandbox-level.flash", 3); // prev: 2
Flash. IDGAF. higher sandbox-level is always welcome but we don't need to enforce it or anything
pref("dom.registerContentHandler.enabled", false); // prev: true
navigator.registerContentHandler() has been removed  :+1:
pref("dom.registerProtocolHandler.insecure.enabled", false); // prev: true
navigator.registerProtocolHandler() can no longer be used on insecure sites  :+1:
pref("network.http.throttle.version", 1); // prev: 2
pref("security.pki.name_matching_mode", 3); // prev: 1
more restrictive hostname matching in TLS certificates  :+1:

some of the remaining changed prefs might be beta-only, let's wait until 62-release is out

moved from new to ignore
pref("browser.history_swipe_animation.disabled", false); // not privacy related
pref("browser.tabs.remote.tabCacheSize", 0);
 // ^ temp(?) change due to e10s related issues
pref("devtools.debugger.pause-on-caught-exceptions", true);
pref("devtools.webconsole.jsterm.codeMirror", false);
 // ^ don't need to change these
pref("dom.mutation-events.cssom.disabled", true);
pref("dom.serviceWorkers.parent_intercept", false);
pref("gfx.webrender.program-binary-disk", true);
pref("image.animated.resume-from-last-displayed", true);
pref("io.activity.intervalMilliseconds", 0);
pref("layout.accessiblecaret.script_change_update_mode", 0);
 // ^ https://hg.mozilla.org/mozilla-central/rev/92022a209721
pref("layout.css.property-append-only", false);
pref("layout.css.scrollbar-colors.enabled", false);
pref("layout.css.webkit-appearance.enabled", false);
pref("layout.css.xul-display-values.content.enabled", false);
pref("network.cookie.maxNumber", 3000);
pref("network.cookie.maxPerHost", 180);
pref("network.sts.poll_busy_wait_period", 50);
pref("network.sts.poll_busy_wait_period_timeout", 7);
pref("network.sts.pollable_event_timeout", 6);
pref("services.sync.engine.bookmarks.validation.enabled", true);
pref("services.sync.engine.passwords.validation.enabled", true);
 // ^^ IDGAF about sync

62.0 changes since 62b20
new
pref("browser.newtabpage.activity-stream.improvesearch.topSiteSearchShortcuts", false); // true in 62b20
pref("services.sync.engine.bookmarks.validation.enabled", true);
pref("services.sync.engine.passwords.validation.enabled", true);
removed
pref("geo.provider.ms-windows-location", false);
changed
pref("app.update.channel", "beta"); // prev: "release"
pref("app.update.url.details", "https://www.mozilla.org/%LOCALE%/firefox/beta/notes"); // prev: "https://www.mozilla.org/%LOCALE%/firefox/notes"
pref("app.update.url.manual", "https://www.mozilla.org/firefox/beta"); // prev: "https://www.mozilla.org/firefox/"
pref("browser.newtabpage.activity-stream.telemetry.ut.events", true); // prev: false
pref("dom.keyboardevent.dispatch_during_composition", true); // prev: false
pref("geo.wifi.uri", "https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%"); // prev: "https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY%"
pref("layout.css.moz-document.url-prefix-hack.enabled", false); // prev: true
pref("network.tcp.tcp_fastopen_enable", true); // prev: false
pref("toolkit.telemetry.enabled", true); // prev: false
--- updated 1st post

https://bugzilla.mozilla.org/show_bug.cgi?id=603903#c69

... This feature is currently limited to Windows, though it may be extended to macOS later (in bug  1326181).

Firefox will automatically restore your tabs after Windows OS reboot. To disable this feature, set the "toolkit.winRegisterApplicationRestart" pref to false.

browser.sessionstore.resuming_after_os_restart is used internally and toggled back and forth automatically -> moved to ignore
also Content loads and runs before user has logged in but it might be a Windows 10 problem only

pdfjs: https://github.com/mozilla/pdf.js/pull/9208

dom.registerContentHandler.enabled & dom.registerProtocolHandler.insecure.enabled .. both previously true - shouldn't we add these for ESR60 users? or were they also flipped there?

no they were not flipped in ESR60.
dom.registerContentHandler.enabled isn't listed under "Privacy & Security" in Firefox 62 Site Compatibility so IDK if we need that.
But ESR60 users might also want user_pref("layout.css.moz-document.content.enabled", false); "since it could be used by attackers for CSS injection to steal private data in the URL of third-party sites."

pref("layout.css.moz-document.content.enabled", true); - from our diffs, added in FF59 1035091, flipped to false in 61

added to list, feel free to do a commit

I'd say we don't add stuff just for ESR60 users. They know they won't get non-critical updates.
There was a good reason to stick with ESR52 for the legacy extension support but IDK why anyone would choose ESR60 over release, beta or nightly. And this user.js was always made for Release anyway.
The rest under new and changed can be ignored as well IMO.
Add toolkit.winRegisterApplicationRestart if you want and then we can close this

I agree with the prefs from the looks of them, I just hadn't gotten around to reading about them on bugzilla.
Not sure on the ESR thing - it wouldn't be hard to maintain it (a few extra prefs here and there, or leaving something in when the default becomes what we want). I need to think about it (I'm 50/50). IF we drop ESR I would want to mention it somewhere - eg under the release version

well both the register*Handler APIs are behind prompts anyway, fe see https://mdn.mozillademos.org/files/9683/protocolregister.png and the problem with disabling the moz-document css rule in ESR60 is that the exception which prevents most or all of the breakage landed in 61 and wasn't backported.

I can't be arsed with the restart with windows when forcibly terminated thing. I want to properly disable any local data for crash to be able to read back, and I have the other issue for that

No we don't need to do anything, no warning no cleanup no nothing. ESR users can continue to use the latest master and just activate the ESR60 deprecated part with the one-char switch.
There's probably not a lot of stuff that we'll change in terms of existing prefs anyway, mostly we'll add new prefs that won't exist in ESR or remove old prefs which they can re-enable in 9999

^^

although to be honest I don't think there's much left to be found and added - just new prefs going forward

fair enough, although I might add that release line in if people get confused

Do you want to do a release. I already changed the version and date, so go ahead - it's all yours :) unless there was something else

https://github.com/ghacksuserjs/ghacks-user.js/issues/463#issuecomment-418741061

^^ lets add toolkit.winRegisterApplicationRestart somewhere and set it to false and active. It could be pretty annoying when content loads and runs before user has logged in

sure
Holy F .. WTH did they do to the startup in 62. The chrome paints before its had a chance to resize - so you see blinding white rectangle (at 1600x900 from remembered close state), which then sizes larger off my screen (probably around about my screen size, its just that I have the browser fairly centered on my 2560x1440), and then it finally settles back to 1600x900 as per my prefs - and takes about 1 seconds all up. Highly F annoying.
Wonder if it's that blank paint pref thing? Anyone else getting this?

^^ yes that's the new blankWindow pref. It has that problem when RFP is enabled

browser.startup.blankWindow=false fixes it
Maybe we should add that in under RFP section?>

/* 4504: disable showing about:blank as soon as possible during startup (FF60+)
 * When default true (FF62+) this no longer masks the RFP resizing activity on startup
 * Also blindingly white .. my eyes, my eyes!! ***/
user_pref("browser.startup.blankWindow", false);

^^ I can drop the last comment line if i have to
toolkit.winRegisterApplicationRestart - should we file this under 0001 or under 1000 cache / session stuff

/* 0002: disable automatically restoring your tabs after Windows OS reboot [WINDOWS] (FF62+) ***/
user_pref("toolkit.winRegisterApplicationRestart", false);

should we add the bugzilla? I mean it won't launch FF is FF was closed when windows rebooted, so the description is a bit misleading. Wanna fix it up? I kinda want to do this now, so we can do a release and I get to bed (and you can do a changelog) - otherwise it's gonna be another 12+ hrs. I'll make a coffee and await your writing skills :)

blankWindow: https://bugzilla.mozilla.org/show_bug.cgi?id=1448423
toolkit.winRegisterApplicationRestart: definitely not 0001. /*** 0100: STARTUP ***/ or maybe under MISC, IDK.

"disable automatically restoring your Firefox session after restarts (FF61.0.2+)"
"As of FF62 it's Windows-only but support for MacOS is also planned"

headsup - the RFP window resizing took a hit, I guess something in the toolbar changed. It shifted 1 pixel in height

reading thru that ticket - it definitely launches firefox and restores session (regardless of session prefs) on all windows starts (if FF was open). That's how I read it
https://bugzilla.mozilla.org/show_bug.cgi?id=603903#c9 - used to be just updates or installs, but since Win10 Fall update its every start
but .. sometimes it doesn't - see comment .. screw it .. IDK, people can just read the ticket
/* xxxx: disable automatic Firefox start and session restore after reboot [WINDOWS] (FF62+)
 * [1] https://bugzilla.mozilla.org/show_bug.cgi?id=603903 ***/
user_pref("toolkit.winRegisterApplicationRestart", false);

whats with the 61.0.2+ - did it land in a dot release?

blankWindow: once bug 1448423 gets fixed we can remove the pref again - add the link for easy reference?
winRegisterApplicationRestart:

whats with the 61.0.2+ - did it land in a dot release?

https://www.mozilla.org/en-US/firefox/61.0.2/releasenotes/

Adds support for automatically restoring your Firefox session after Windows restarts. Currently, this feature is not enabled by default for most users, but will be gradually enabled over the coming weeks.

(61.0.2+) or (FF62+) - whatever you prefer is fine

I'm confused : https://github.com/ghacksuserjs/ghacks-user.js/commit/8b5547a9737bbefe93544ba401fdbd2c1a3b3576 <- do we want to add the 1448423 link here?
winRegister look good for 1024
I'll add these and if you want any changes just let me know. If everything is fine, then feel free to close this and even do a release


Finetuned Model Weights

Hi @jerryjliu ,
Many thanks for the great codebase. Is it possible that you can please share the fine-tuned (adapter) model weights on the hugging face model hub or provide another way to download the model weights?
Thanks!

hey @usamayaseen-veeva! hmm good question, that's definitely possible.
Assuming you're wiling to run the script it will cost ~$15 USD. but understand it might be more convenient to just download the weights

I would be interested in the fine tuned model if it can be made available. Thanks


npm install from values.yaml

Thank you for making node-red ⚙ better
Fixes:

#198

Let me know what you think and if you think there's a better way to do it.
Also verify you have:

[x] Read the contributions page.
[x] Read the DCO, if you are a first time contributor.
[x] Read the [code of conduct](Code of Conduct).

Hi @beasteers,
The issue I have with this approach is that you are overloading the specific use case of this "hardcoded" sidecar. This sidecar is only resposible for loading flows from configmaps/secrets via the k8s-sidecar
See https://github.com/SchwarzIT/node-red-chart/tree/main/charts/node-red#sidecar-
And assumes, that the image in the sidecar has nodejs installed. Or you need to change the image of the sidcar too.
I would rather use the existing function of defining a new extraSidcars
https://github.com/SchwarzIT/node-red-chart/blob/93feb40c903f5d0733ce30ca09a00bcf2bd9d342/charts/node-red/templates/deployment.yaml#L48-L50
WDYT?

Oh oops you're right sorry I got lost in the weeds trying to fix the git history and accidentally re-added those lines back to the wrong container. I meant to add it to the main container which I can fix.
Do you think this would be best suited for an initContainer instead? It should happen before settings.js is loaded so that there isn't a race condition.

According to the K8s docs https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#define-a-command-and-arguments-when-you-create-a-pod, when you set the command field it will overwrite the entrypoint of the container image.
Did you tested this? Is node-red still starting?

Yes I made sure to include the original entrypoint (/entrypoint.sh) in the command so node-red does start up.
"{{- if .Values.installPackages }}npm install {{ join " " .Values.installPackages }};{{ end }} ./entrypoint.sh"

My concern with this is in case someone is using a custom image with an entrypoint that's different from the default entrypoint script. I just tried to implement it using an initContainer, but the packages weren't showing up in the nodered instance. I'd have to dig deeper, but I suspect that the packages are being installed inside the initContainer's file system which is being discarded.
Here's the initContainer config I tried (not sure how much of this is needed)
      {{- if or .Values.initContainers }}
      initContainers:
        {{- if .Values.initContainers }}
          {{- toYaml .Values.initContainers | nindent 8 }}
        {{- end }}
        {{- if .Values.installPackages  }}
        - name: {{ .Chart.Name }}-npm-install
          {{- if .Values.securityContext }}
          securityContext:
            {{- toYaml .Values.securityContext | nindent 12 }}
          {{- end }}
          image: "{{ .Values.image.registry }}/{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
          imagePullPolicy: {{ .Values.image.pullPolicy }}
          command:
           - sh
           - -c
           - npm install {{ join " " .Values.installPackages }}
          {{- if .Values.env }}
          env:
          {{- toYaml .Values.env | nindent 10 }}
          {{- end }}
          volumeMounts:
            {{- if and .Values.npmrc.enabled }}
            - name: npmrc-volume
              mountPath: /usr/src/node-red/.npmrc
              subPath: npmrc
            {{- end }}
            {{- with .Values.extraVolumeMounts }}
              {{- toYaml . | nindent 12 }}
            {{- end }}
            - name: data
              mountPath: /data
              {{- if .Values.persistence.subPath }}
              subPath: {{ .Values.persistence.subPath }}
              {{- end }}
          {{- if .Values.resources }}
          resources:
            {{- toYaml .Values.resources | nindent 12 }}
          {{- end }}
        {{- end }}
      {{- end }}

fyi the indentation was still broken in the main container (the fix you implemented only fixed the sidecar). I can take it out and move it to a different PR if you want but it was small and breaking my tests so I just threw it in

@beasteers that would be awesome

I'd have to dig deeper, but I suspect that the packages are being installed inside the initContainer's file system which is being discarded.

@beasteers maybe check the volumeMount. It should share it.

Hi @beasteers,
with https://github.com/SchwarzIT/node-red-chart/pull/216 I fixed the issue with the indentation on the main container!
I will close this issue for now. Feel free to open a new one for the npm enhancements.


ANSI output used with non-ANSI terminals, NO_COLOR

I'm running my Bevy projects via Sublime Text, which doesn't have a real terminal, only a super basic plaintext log.
The problem is that naga_oil uses ANSI colors on non-WASM targets unconditionally, without checking whether the terminal is compatible. In my case TERM is undefined, and I'm running std::env::set_var("NO_COLOR", "1") in main, but I still get ANSI color output that makes WGSL errors completely unreadable:

i don't understand this well enough to fix it but a pr would be welcome.

@robtfm submitted a fix in #103


Fix nil pointer dereference in istiod-remote/templates/services.yaml

The Helm values were flattened in #52036, but the endpoints.yaml and services.yaml templates weren't updated, causing the following error when rendering the istiod-remote chart:
failed to install helm chart istiod-remote: template: istiod-remote/templates/services.yaml:5:16: executing "istiod-remote/templates/services.yaml" at <.Values.pilot.enabled>: nil pointer evaluating interface {}.enabled

Hi @luksa. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test


error when creating Application.kt file for Firebase Messaging 10.0.1

I am trying to use latest FCM using firebase_messaging: ^10.0.1 in my pubspec.yaml
from the documentation in here https://firebase.flutter.dev/docs/messaging/overview#flutter-android-embedding-v1 , I have to create a Application.kt file in the Android project folder. from that documentation, the code is still in Java, so the Android Studio will convert it automatically to Kotlin like this

import io.flutter.app.FlutterApplication
import io.flutter.plugin.common.PluginRegistry.PluginRegistrantCallback
import io.flutter.plugins.GeneratedPluginRegistrant
import io.flutter.plugins.firebase.messaging.FlutterFirebaseMessagingBackgroundService

class Application : FlutterApplication(), PluginRegistrantCallback {
    override fun onCreate() {
        super.onCreate()
        FlutterFirebaseMessagingBackgroundService.setPluginRegistrant(this)
    }

    override fun registerWith(registry: PluginRegistry?) {
        GeneratedPluginRegistrant.registerWith(registry)
    }
}

but I have error like this https://i.stack.imgur.com/fVPMR.png
I have tried to import, but I will have another error like this: https://i.stack.imgur.com/T70Nw.png
it seems that I can't import PluginRegistry and I have error suggestion like this

Add library 'Gradle: org.apache.maven:maven-ant-tasks:2.1.3' to classpath

but.... I don't understand. what should I do ?
what is the code to be added to Application.kt (Kotlin) so I can use the Firebase Messaging?
I have no issue from Flutter Doctor

[✓] Flutter (Channel stable, 2.2.1, on macOS 11.2.1 20D74 darwin-x64, locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] VS Code (version 1.56.2)
[✓] Connected device (4 available)
• No issues found!

Hi @AgungLaksana
Is your project on embedding v1 and if so have you considered upgrading?
Thank you

@markusaksli-nc yup you are right, I don't need to create Application.kt since I use Flutter 2.2.1


[Viewer] Missile switch off means keep the entire tree on screen

This is a preview of the animation with and without missiles enable


test: Adding test for local_hostpath.go

Added testing for local_hostpath issue #121

cc @vharsh

Thanks @giovannitgl for contributing to OpenEBS. 🥳


Use HTML5 validation on indicator setup forms

Bootstrap has a model for validating form fields that we are not following.  Using their model would likely result in cleaner code and less need for JS in the validation process.

@sanjuroj Is this ticket still relevant? If yes, shall we move to Fruit Basket (if needs a spike) or Poblano (if ready to implement)?

@jennyhavah I'm not sure.  HTML 5 can provide validation for some types of fields but not others.  I suspect, for consistency's sake, we may want to do custom validation messages for everything.  @axoplasm, any thoughts?

LOL, consistency.
I think we could apply the :valid and :invalid pseudoclasses as BS wants. We have not done this consistently (at all? ever?) and instead rely on B3-era (or older) utility classes. I've been adding custom classes to parent elements (which doesn't require strict neighbor markup like the BS4 method)
HTML5 validation is really a way to provide a hook to do this. We can't count on browsers implementing (or announcing) validation consistently as the BS docs note.
So... this is really a markup task and it has global-ish implications. it could kind of be a "start on it any time" task but not a "do it in two hours" (or even two days) kind of task.

…I guess I'd spike it in Fruit Basket unless someone is looking for a few days’ work. I’d only ask they check with me before they start.

Would it make sense to document some sort of design/coding pattern so that as we're developing new features we can use that pattern?  Then we can backfill when we have time/volition.

Sure, I guess that would be the spike then? I legit have no idea how big a lift this would be globally

…I also worry about our proliferation of patterns, frontend-wise

@sanjuroj Is this ticket still valid? If yes, let's move to the "backstage" column of Poblano.


[IOTS-400] UI text improvements

Reference: https://wso2.org/jira/browse/IOTS-400

This issue is duplicated in https://github.com/wso2/product-iots/issues/983, https://github.com/wso2/product-iots/issues/984, https://github.com/wso2/product-iots/issues/988 and https://github.com/wso2/product-iots/issues/989 hence closed.


Update README.md

at 2.26+ prometheus versions,  params should be list, not k/v ;
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config

Hey! Thanks for pointing that out. I was somewhat busy with some refactoring, including the docs. I should have merged this beforehand, but missed that, sorry. Would you be up for updating the PR to be against docs/configuration.md instead (which now contains this section)?


Bump version in Cargo.toml as well

The package.json was updated, but not the Cargo.toml

Thanks again!


No IP being generated for any other container besides Nginx

Hi there,
I have been searching for many hours for a solution but have been unable to find anything.
This is the "main" docker-compose file i'm using:
version: "2"

services:
  nginx:
    image: nginx
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/etc/nginx/conf.d"
      - "/etc/nginx/vhost.d"
      - "/usr/share/nginx/html"
      - "../../../volumes/proxy/certs:/etc/nginx/certs:ro"
    networks:
      - proxy-tier
  nginx-gen:
    image: jwilder/docker-gen
    container_name: nginx-gen
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "../../../volumes/proxy/templates/nginx-compose-v2.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro"
    volumes_from:
      - nginx
    entrypoint: /usr/local/bin/docker-gen -notify-sighup nginx -watch -only-exposed -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
  letsencrypt-nginx-proxy-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-nginx-proxy-companion
    volumes_from:
      - nginx
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
      - "../../../volumes/proxy/certs:/etc/nginx/certs:rw"
    environment:
      - NGINX_DOCKER_GEN_CONTAINER=nginx-gen

networks:
  proxy-tier:
    external:
name: nginx-proxy

Then I am attempting to start up additional websites using:
version: "2"

services:
  simple-site:
    image: nginx
    container_name: simple-site
    volumes:
      - "../../../volumes/examples/simple-site/conf.d/:/etc/nginx/conf.d"
    environment:
      - VIRTUAL_HOST=site.example.com
      - VIRTUAL_NETWORK=nginx-proxy
      - VIRTUAL_PORT=80
      - LETSENCRYPT_HOST=site.example.com
      - LETSENCRYPT_TEST=true
      -<EMAIL_ADDRESS>    networks:
      - proxy-tier

networks:
  proxy-tier:
    external:
      name: nginx-proxy

This works fine, I can add multiple sites by adding docker-compose files like the one above. I get this in my generated nginx config:
upstream site.example.com {
   # Container: simple-site@nginx-proxy
   server <IP_ADDRESS>:80;
}

lets encrypt container logs:
2016-09-05 00:39:54,313:INFO:simp_le:1305: site.example.com was successfully self-verified
However, when I change the image to anything other than nginx, I loose the IP address and the SSL certs are unable to be downloaded.
version: "2"

services:
  simple-site2:
    image: tutum/apache-php
    container_name: simple-site2
    environment:
      - VIRTUAL_HOST=site2.example.com
      - VIRTUAL_NETWORK=nginx-proxy
      - VIRTUAL_PORT=80
      - LETSENCRYPT_HOST=site2.example.com
      - LETSENCRYPT_TEST=true
      -<EMAIL_ADDRESS>    networks:
      - proxy-tier

networks:
  proxy-tier:
    external:
      name: nginx-proxy

Generated nginx default.conf lines:
upstream site2.example.com {
           # simple-site2
           server :80;
}

lets encrypt container logs:
2016-09-05 00:48:22,077:WARNING:simp_le:1303: site2.example.com was not successfully self-verified. CA is likely to fail as well!
2016-09-05 00:48:22,098:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
2016-09-05 00:48:22,436:INFO:simp_le:1313: Generating new certificate private key
2016-09-05 00:48:22,871:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
2016-09-05 00:48:23,147:ERROR:simp_le:1271: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Is there a warning log entry about unsuccessful self-verification? Are all your domains accessible from the internet?
Challenge validation has failed, see error log.

Am I doing this the wrong way? Or is this config incorrect?

Even when using default docker-compose this still has the same issue:
version: "2"

services:
  nginx:
    image: nginx
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/etc/nginx/conf.d"
      - "/etc/nginx/vhost.d"
      - "/usr/share/nginx/html"
      - "../../../volumes/proxy/certs:/etc/nginx/certs:ro"
    networks:
      - proxy-tier
  nginx-gen:
    image: jwilder/docker-gen
    container_name: nginx-gen
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "../../../volumes/proxy/templates/nginx-compose-v2.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro"
    volumes_from:
      - nginx
    entrypoint: /usr/local/bin/docker-gen -notify-sighup nginx -watch -only-exposed -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
  letsencrypt-nginx-proxy-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-nginx-proxy-companion
    volumes_from:
      - nginx
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
      - "../../../volumes/proxy/certs:/etc/nginx/certs:rw"
    environment:
      - NGINX_DOCKER_GEN_CONTAINER=nginx-gen

  simple-site:
    image: tutum/apache-php
    container_name: simple-site
    environment:
      - VIRTUAL_HOST=site.example.com
      - VIRTUAL_NETWORK=nginx-proxy
      - VIRTUAL_PORT=80
      - LETSENCRYPT_HOST=site.example.com
      -<EMAIL_ADDRESS>    networks:
      - proxy-tier

networks:
  proxy-tier:
    external:
      name: nginx-proxy

upstream site.example.com {
           # simple-site
           server :80;
}

Figured out the issue, I don't know if this is really a "Fix" though.
removed the first if statement in a section under nginx-v2.tmpl:
    {{ $addrLen := len $value.Addresses }}
    {{/* If only 1 port exposed, use that */}}
    {{ if eq $addrLen 1 }}
        {{ with $address := index $value.Addresses 0 }}
           # {{$value.Name}}
           server {{ $address.IP }}:{{ $address.Port }};
        {{ end }}

    {{/* If a VIRTUAL_NETWORK is specified use use its IP */}}
    {{ else if $value.Env.VIRTUAL_NETWORK }}
        {{ range $i, $network := $value.Networks }}
           {{ if eq $network.Name $value.Env.VIRTUAL_NETWORK }}
   # Container<EMAIL_ADDRESS>   server {{ $network.IP }}:{{ $value.Env.VIRTUAL_PORT }};
           {{ end }}
{{ end }}

to become:
    {{ $addrLen := len $value.Addresses }}
    {{/* If a VIRTUAL_NETWORK is specified use use its IP */}}
    {{ if $value.Env.VIRTUAL_NETWORK }}
        {{ range $i, $network := $value.Networks }}
           {{ if eq $network.Name $value.Env.VIRTUAL_NETWORK }}
   # Container<EMAIL_ADDRESS>   server {{ $network.IP }}:{{ $value.Env.VIRTUAL_PORT }};
           {{ end }}
{{ end }}

This seemed to fix all the issues:
upstream site2.example.com {
   # Container: site2@nginx-proxy
   server <IP_ADDRESS>:80;
}

2016-09-05 05:26:44,481:INFO:simp_le:1305: site2.example.com was successfully self-verified
Could someone shed some light on this?

I see there is a pull request for this already.  "Check for VIRTUAL_NETWORK first"

You're absolutely right, i've been really busy these pasts months, but i'll be checking everything and adding more examples soon.
Thanks for your comments

Great thanks man.
Haha, I can relate to that!

Please see related issues here:
#https://help.nextcloud.com/t/nextcloud-nginx-reverse-proxy-letsencrypt-in-docker-containers/1687/17


docs(#1465): Updating reference docs

Related to issue 1465.

Ok, i will merge this now.
@Amelie-V You can check the result here https://rubrix.readthedocs.io/en/master/reference/webapp/view_dataset_metrics.html once it is merged, maybe you can have a quick look at it, but I think (hope) I made a thorough QA.
@leireropl @Amelie-V I think the View dataset metrics could be structured better, but we can leave this for another iteration. Also, after writing the docs, i think we could improve a bit the structure of the "Metrics" section of the sidebar. I will ping you about this next week.


Offscreen API Refactor

Refactors Offscreen API work with proper serialized types and fixes transaction building.

this is just a merge into the other PR branch? it's still wip so i see no reason to not just do that
otherwise i have time to review around noon/1pm pacific

@turbocrime good point, can you review the base branch?


🐞 The word 'random' is being dropped into most sentences

The sentence generation prompts need tweaking.

Workaround: f1a546054c21b478d1d66edbf1a5e84f60ecf3b9


Fix issue in LinuxPath.Combine where the '.' directory would not combine correctly

@bartsaintgermain ping for review


WIP: TLSProxy using random ports, take 2

For quite a while now, the test recipes that use TLSProxy were stuck with the same hard coded ports, which meant that if you wanted to run several test suites at the same time, you had to be careful so TLSProxy based tests wouldn't overlap (in practice, you simply wouldn't run several test suites at the same time).
No longer. With this change, the ports used by TLSProxy are chosen at random.
This makes a small change to the openssl s_server output, where this line:
ACCEPT

now contains a bit more information:
ACCEPT <IP_ADDRESS>:45633

ACCEPT [::]:45633

This is an alternative to #5805

Would anyone be ok with this backported to 1.1.0 as well?

Hmmmm...  something happens on Windows...  the second time TLSProxy::Proxy::start is run, "it" simply hangs.  Exactly where, I don't know, but I'm guessing it's around this line:
    $self->serverpid(open(STDIN, "$execcmd |"));

@dot-asm, you seem to know this trickery a bit better, do you have any ideas?

Actually, with a little bit of print debugging, I found out that everything grinds to a halt at this line:
    open my $savedin, "<&", \*STDIN;

This works without error on Linux, though...

A bit of experimentation showed that instead of a save'n'restore of STDIN, just reassigning STDIN in the dumping subprocess seems to work just as well, or even better on Windows.

...  unforatunately, it was only half true.  test_sslmessages gets stuck in a manner I cannot grasp for the moment.

@dot-asm, have a look at the middle commit (98454966fa669eb3aa0b7c5f738a4e9239b1479d), I think that translates your original idea from #5805.  Did I do something wrong there?
Regarding Win32::Process::Create, that's a bit troublesome:
: ; corelist Win32::Process

Data for 2017-09-22
Win32::Process was not in CORE (or so I think)
: ; corelist Win32::Process::Create

Data for 2017-09-22
Win32::Process::Create was not in CORE (or so I think)

I had a look at ActiveState perl, and it doesn't seem to include Win32::Process or any sub module

corelist Win32::Process

I believe corelist Win32 tells the story. In worst case I'd say it wouldn't be inappropriate to skip the tests if it (or Win32::API) is not found.

Isn't this becoming quite a bit convoluted just for a piece of information?  #5805 works uniformly on all platforms where we even do this (which includes all aspects of Windows that we care about).
Anyway, the Win32 stuff is over my head at this point.  If you want this PR to come through, I gladly hand it over.

have a look at the middle commit (9845496), I think that translates your original idea from #5805. Did I do something wrong there?

Yes, that should have worked. In more ideal world that is. And it actually works occasionally. Somehow. But not always. Bottom line is that fork is not to be trusted on Windows. I'll proceed tomorrow. If you want me to I can take an own go in this...

Yes, that should have worked. In more ideal world that is. And it actually works occasionally. Somehow.

... yeah, I suspected that.  that's a kind of fragility I decidedly have no desire to see in our test suite.

If you want me to I can take an own go in this...

Please, be my guest


⚠ Bofrost.fr has degraded performance

In ffde70b, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2146 ms

Resolved: Bofrost.fr performance has improved in 6caeae7 after 6 minutes.


Runners getting killed due to runner deployment directory clashes

Steps to reproduce

ftl serve --recreate --log-level=DEBUG --idle-runners 3 (default idle runners also hits the issue)
Wait for idle runners to be loaded, using deployment directories [...]/ftl-runner/runner[0,1,2]/deployments
ftl deploy examples/go/time -n 10
This will cause more runners to be spun up, using deployment directories [...]/ftl-runner/runner[0,1,2...9]/deployments (overlaps with above)
As deployments are reconciled, there'll be errors of error:runner2: Deployment terminated: signal: killed, and the deployment count will increase, sometimes decrease, and eventually make its way to 10

This line should be using the randomly generated config.Key.


Fix typos in 16-open-source-models/README.md and 17-ai-agents/README.md

This PR fixes typos in 16-open-source-models/README.md and 17-ai-agents/README.md.

@microsoft-github-policy-service agree


Implement ORDER BY

Details

Add consumer for substrait::protobuf::SortRel
Add producer and test

Thanks @nseekhao


apply Issue

Filename :lispy.py
replaced 'apply':apply in environment dictionary with 'apply':lambda proc, args: proc(*args)
If I'm wrong then I would be very grateful if you explain

You are correct. In Python 2 there was an apply function; it is gone in 3.


fix two warnings

See separate commits.  These both print warnings when running TS tests.

Please update the branch and then we can merge it.

One of these days I'll remember to merge this after updating the branch


Fix device params

--device must be single params and not a list

Hi Lars, looks good to me, i will take it in.


CSharpier Rider plugin mangles UTF-8 characters when running on save

IDE Version: JetBrains Rider 2023.3.4
Extension Version: 1.6.3
CSharpier Version: 0.27.2+b456544aad8957d0e2026afe1a37544bb74552ba
Operating System: Windows 11
.csharpierrc Settings: printWidth: 120
.editorconfig Settings: N/A

Log Output
Steps to reproduce

Ensure the csharpier plugin is installed in Rider and ensure the "Run on Save" setting is turned on in the plugin's settings.
Open any .cs file
Ensure the file encoding is set to UTF-8 with BOM
Type any non-ascii UTF-8 character, like ë or ä
Save the file.

Expected behavior
The non-ascii UTF-8 character is preserved
Actual behavior
The character is mangled. For example, ë becomes Ã«. Saving this again then mangles the characters again, resulting in ÃƒÂ«.
I've narrowed this down to the CSharpier plugin in Rider, because non-ascii UTF-8 characters are preserved correctly when turning off the 'Run on Save' setting of the plugin. When running csharpier from the terminal using dotnet csharpier . --config-path ./.csharpierrc.yaml, the problem does not arise either.

I haven't been able to reproduce the problem and matched your setup exactly, except for the contents of the file.
Does this still occur with a brand new project + new file?
Can you also try it with "Use CSharpier Server" turned on to see if that makes a difference?
This is the file I used for testing with UTF-8-BOM encoding
namespace PluginIssue;

public class Class1ë
{
    private string Fieldä = "ä";
}

I haven't been able to reproduce the problem and matched your setup exactly, except for the contents of the file.
Does this still occur with a brand new project + new file? Can you also try it with "Use CSharpier Server" turned on to see if that makes a difference?
This is the file I used for testing with UTF-8-BOM encoding
namespace PluginIssue;

public class Class1ë
{
    private string Fieldä = "ä";
}

Hello, I have provided a reproduction here. https://github.com/OwenCross289/CsharpierRepro This issue appears to ONLY be with the Rider plugin. Running CSharpier through the CLI does NOT affect this.
Thanks for the great tool :)
If there is anything I can do to help this get fixed please let me know :)


Updated NoMachine cask

Updated the NoMachine cask to the most recent version on found on the website
which is 5.0.43_3
fzakaria $ brew cask audit nomachine
audit for nomachine: passed
fzakaria $ brew cask audit nomachine --download
==> Downloading http://download.nomachine.com/download/5.0/MacOSX/nomachine_5.0.43_3.dmg
######################################################################## 100.0%
audit for nomachine: passed

Thanks, but in future, please use a commit message which includes the version you are updating the cask to. i.e "NoMachine 5.0.43_3"

Will do.


16MB video within the library source code

We are including the library in WordPress plugin but it is very big. There is video within the library that is literaly 16 MB which is too much for projects limited on size. Can this be moved out of the project somehow?
Thanks.

@gdarko Please fetch the project using composer as described in this doc. All unnecessary files will automatically be excluded.

Thank you @ankitpokhrel , i just noticed it is removed


chore: update license authors

Update Apache2 license to contain copyright authors

Guess this is the PR for https://github.com/cdevents/github-action/issues/5?


Check for excessive power/network usage (Dev)

We know about the memory leak, but we should do a check for this too.

checked, heartbeats use a little, but these were removed.
We're good
10 minutes


fix: Google Analytics (UA) will stop working on July 1st, 2023

Description
package:usage supports UA only, which will be shut down (for users without some "Analytics 360" subscription) on 01.07.2023.
See also:

https://github.com/dart-lang/usage/issues/185
https://github.com/leancodepl/patrol/pull/1131

Thanks for letting us know!


Forecasting: Training failed with error "cross validation is not implemented" or "length doesn't match, 216 != 10".

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>6701 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.5.2)
.Net: 6.0
Describe the bug

On which step of the process did you run into an issue:
Training failed with error "cross validation is not implemented" or "length doesn't match, 216 != 10".

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/forecasting.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select Forecasting scenario.
Go to the Data page, choose the data source.
On the Train page, click "Strat training" button, then you will see the training is failed.

Expected behavior
Training should be successful.
Screenshot

Additional context

The bug has been fixed on the latest main build <IP_ADDRESS>8001


[HUDI-1135] Make timeline server timeout settings configurable.

Tips
What is the purpose of the pull request
Make timeline server timeout settings configurable.
Brief change log
Add timeout config settings for timeline server.
Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.
This pull request is already covered by existing tests.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@n3nash corrected the errors.


Colloquial name property in ArtifactCreated

The need for providing a non-canonical name of artifacts has been put forward. Sometimes GAVs are rather cryptic or non-descriptive, and then a colloquial, non-canonical name is valuable.
I see very little reason in not including it as an optional property, and would suggest data.colloquialName. Thoughts?

I think it should be part of the data.gav data structure, or even better, replace the data.gav structure with a data.artifact structure instead. The GAV is very limited and does not work very well. This is what I propose:

data.artifact.artifactId    (Required)
This should be the product number of an artifact or something that uniquely identifies it.

data.artifact.version    (Required)

data.artifact.artifactName  (Optional)
A human understandable name of the artifact.

data.artifact.type  (Optional)
This could be a list of strings that tells the type of the artifact, e.g. LoadModule, Interphase, Tool, etc

data.artifact.groupId

Could we use a simpler term then colloquial? I like the simplicity of artifactName if used in a gav context. Although I think it should be data.artifact.name if we would go for that approach.

Sure, we can skip colloquial and make that fact implicit. "artifact" as a prefix is redundant, so simply "name" should do just fine.
If we're going to add type, is there any reasonable way we can standardize/enumerate that? Any way we can avoid free text strings? :)
GAV is a widely used and well understand concept, and should be preserved. Adding properties to it isn't helpful. So it's going to be
data.gav
data.name
data.types (?)

If the name and the type isn’t tied to the artifact there is a big risk that no one know what these fields are to be used for! One of the reasons for 2.0 was to avoid being ambiguous!
I do not agree that concept of GAV is widely used; widely used by Maven of course but not beyond that. I do not see anything stopping us from defining our own Artifact data structure. The “GAV” parts are still in there!

The properties would be in ArtifactCreated. Any properties within its data object refer to the artifact. You can mentally append "of the artifact" to every property: "gav of the artifact", "name of the artifact" et cetera.
GAV is supported by all the major repository managers, by Ivy, Gradle, Maven, Buildr, SBT... For identifying distributed dependencies, I'd argue it's the closest thing we have to a standard.

Yes, and the common denominator is Java. For all other non-java artifacts, GAV is unknown. Besides, I do not see why Eiffel have to be so tied to a  Maven vocabulary. We do have a lot of other types of products that is not Java based. It would make a lot more sense to have a wider Artifact identification data structure.
The reason why I think it is better to group it in an Artifact identification object and not to have it separate is because then you can easily handle data that goes together in an easy way, both in terms of implementation and in data structures. Having name and type on the top level would be the same as having “data.fileInformation.extension” as just “data.extension” and still keep the “data.fileInformation” object. The GAV is an artifact identification object, which is lacking name and type and maybe even more things! Let’s create an artifact identification object that is more practical and which can be expanded if needed!

I see your point. But still, whatever one might think of it, GAV is a standard, and so long as we do use it we shouldn't do violence to it by adding custom properties to it. Because then we're not following any standard at all.
Regarding the Java community. Despite having its roots there, the standard is applicable and increasingly used outside of Java, and I still prefer following a (albeit not ubiquitous) standard than following no standard. Allowing for more than one is of course an alternative (see e.g. handling of SCM systems in SourceChangeCreatedEvent) to consider - would you like to propose a competing alternative to GAV?

I would not like to propose a competing alternative to the GAV data structure, it would be ridiculous to have two structures having almost the same content. Instead I think we should treat the “GAV” in the same way as Maven, Nexus, etc. does where the “GAV” is not an object. It is just three data fields which are not grouped together. Eiffel should follow this standard. It is only in Eiffel that the groupId, ArtifactId and Version is put in a separate data structure – the “GAV”. This does not add value. It only makes implementation harder. Let’s get rid of this data structure and the limitations that it enforces will go away.
•  data.groupId
•  data.artifactId
•  data.version
•  data.name
•  data.contentTypes
etc...

I don't have a strong opinion either way, but there are many ways of expressing GAVs. To exemplify, Ivy does
<dependency org="commons-lang" name="commons-lang" rev="2.0"/>
and Gradle does
'org.springframework:spring-core:2.5'
or
[group: 'org.springframework', name: 'spring-core', version: '2.5']
The only common denominator is that the unique identifier consists of three parts. Then they can be expressed at the root of the POM or as a string or in a separate object or an array or whatever.

Then, you have just proven that there is no standard for how a “GAV” should be expressed, so my arguments still stand. Let’s not use a ”GAV” sub structure for reason of simplicity. A substructure does not add any value and it complicates triggering and implementation, for reasons I’m not allowed to explain.

Sorry, but that makes no sense to me. This thread has gone far enough off topic already, so let's end it there: continuing this thread isn't going to lead to a resolution. Feel free to bring it up in front of a whiteboard if this is a serious issue, then we take it from there.
Returning to the original topic, as already raised in PR #77 and then implemented in PR #89, properties for name and type are valid additions to ArtifactCreated. Closing the thread.


feat: Add privilege definition for alias interfaces

Add privilege to the relevant interfaces of Alias, imitating the structure of privilege in Collection.
issue :#237

/lgtm


Support custom admin password for installation

The default Kyma installation will configure dex with an initial generated admin password.
Instead of figuring out the password after installation and potentially changing it, there should be a way to configure the password as part of installation.
Proposal:
Introduce -p/--password flag to install command which configured the password for the installer.
Assure that the password gets printed nowhere, especially not at the summary section at the end of installation.

https://github.com/kyma-incubator/kyma-cli/pull/55 - solves this. Use the -p option to provide the custom password for the installation.


Minimal example throws linting errors

I'm using the exact syntax shown in the Minimal Example however the linter in VSCode for the workflow file is throwing the following errors:

Missing required inputs: komac-token, identifier
Invalid action input 'package-id'

My YAML looks like this:
  publish-winget:
    needs:
      - create-release
    runs-on: ubuntu-latest
    steps:
    - name: Update Packages
      uses: michidk/winget-updater@v1
      with:
        package-id: BC3Tech.FileSorter
        repo: bc3tech/filesorter
        url: https://github.com/bc3tech/filesorter/releases/download/{VERSION}/FileSorter_{VERSION}.zip

Hi,
yeah I need to update the example.
A actually working example can be found here: https://github.com/michidk/winget/blob/main/.github/workflows/update-packages.yml#L27


Cannot read property 'length' of undefined

When I try to test my project I get the following error in the browser
 jasmine.js:796 Uncaught TypeError: Cannot read property 'length' of undefined

I've tried to tweak the preprocessors section of the karma conf
    preprocessors: {
        './di.js': ['coverage', 'browserify'],
        './tests/di.spec.js': ['browserify']
    },

but the end result is always the same
To run the test do:
$> git clone https://github.com/scaljeri/javascript-dependency-injection.git
$> npm install
$> gulp test

Any suggestion what might be the problem ?


Add possibility to customize artifacts building

E.g. user should be able to choose custom name and tag while building release docker image via make  tooling.

Closed by #25


feature: provide server information in the result from /signalk

This should be added to the spec and java server as well.


Exec tachikoma update<PHONE_NUMBER>4608

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage remained the same at ?% when pulling 1b642529da37e60d61b7a56a9362571e3a6009b2 on pazjacket:tachikoma/update-20180828174608 into ddf31327ec9d3097b29bd6c49c1071d946319912 on sanemat:master.


fix(curriculum): use gap instead of deprecated grid-gap

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #37988

The checkbox you did not check is there for a reason.  Please only make changes to challenge files of the same language on a single PR.  It makes the review much easier and faster.
You can revert the changes to the non-English files for this file and then make a separate PR for each of the other languages.
Thank you.
Thank you.

Please only make changes to challenge files of the same language on a single PR. It makes the review much easier and faster.

I'm not sure but I guess that all the file rename changes (e.g. "Add Gaps faster with grid-gap.arabic.md" -> "Add Gaps faster with gap.arabic.md") would need to be in a single change to not break the build process with css-grid/meta.json?
In total that would be 7 PRs (arabic, chinese, english, portuguese, russian, spanish and the file rename changes) to change grid-gap to gap. I think it would be easier to do it all in one go (but also I'm kinda lazy and don't want to do 6 more PR's 😄).
Thoughts?

We recommend individual microscopic PRs.

I think it would be easier to do it all in one go (but also I'm kinda lazy and don't want to do 6 more PR's

We understand, and thank you for your efforts. But please note that most mods on the QA team are volunteers same as you, and it's of utmost important that we can respect everyones time.
Finally its not trivial to go thru 116 files at a go.
Also, I see your formatter is touching a lot of files that it should not be. I am blocking the merge for now to let you sort it out first.

Thanks. I still disagree, but I will update this PR to only change english files.

Thanks could you also update the PR to only make the intended changes and not touch the formatting.

According to MDN:

CSS Grid Layout initially defined the grid-gap property. This prefixed property is being replaced by gap. However, in order to support browsers that implemented grid-gap and not gap for grid, you will need to use the prefixed property as in the interactive example above.

It is not that it is deprecated because users must use the prefixed version to deal support Internet Explorer, some Edge browsers and all Safari browsers.  I think it is a bit premature to suggest this change.

@SimonSiefke When you create an issue, you should typically let others respond to discuss whether or not a change is actually needed.  This will prevent you from spending the time to create a PR in case it is decided a change is not warranted or at least discuss what changes would be acceptable to the community.
I have given my opinion here that we should not be making this change at this time.

users must use the prefixed version to deal support Internet Explorer, some Edge browsers and all Safari browsers.

Source?

Source?

MDN.  Check it out for yourself.

Source?

I would like to point you to your issue thread. The MDN quote, that you quoted yourself literally says this feature is "being replaced" and workarounds like

However, in order to support browsers that implemented grid-gap and not gap for grid, you will need to use the prefixed property as in the interactive example above.

need to be done for some browsers. Meaning you need to implement a API two ways. Its not generic, definitely not universal and hence not deprecated.
All this is from your quote from the official MDN.
We could go on about facts and semantics, but I think let's close this PR for now, wait if there is any interest on the reported issue and comeback with an improvement later.

Hello, @raisedadead, @RandellDawson, @SimonSiefke is this still open to solve it or what?

@Mstava This has been closed.


AWS: some of the IAM resources can not be imported

Summary
Some of the IAM resources can not be imported by the following command:
$ terraformer import aws --profile=XXXX --resources=iam

Version Information
$ terraformer version
Terraformer v0.8.6

Expected Result
$ terraformer import aws --profile=XXX --resources=iam
2020/02/13 00:31:48 aws importing default region
2020/02/13 00:31:48 aws importing... iam

<skip>

2020/02/13 00:30:25 Refreshing state... XXXXXX

<skip>

2020/02/13 00:30:26 aws Connecting....
2020/02/13 00:30:26 aws save iam
2020/02/13 00:30:26 aws save tfstate for iam

$ terraform state list | cut -d'.' -f1 | sort | uniq

aws_iam_group
aws_iam_group_policy # ----------> missing
aws_iam_instance_profile
aws_iam_policy
aws_iam_policy_attachment
aws_iam_role
aws_iam_role_policy
aws_iam_user
aws_iam_user_group_membership # ----------> missing
aws_iam_user_policy

Actual Result
$ terraformer import aws --profile=XXX --resources=iam
2020/02/13 00:31:48 aws importing default region
2020/02/13 00:31:48 aws importing... iam

<skip>

2020/02/13 00:30:25 Refreshing state... XXXXXX

<skip>

2020/02/13 00:30:26 aws Connecting....
2020/02/13 00:30:26 aws save iam
2020/02/13 00:30:26 aws save tfstate for iam

$ terraform state list | cut -d'.' -f1 | sort | uniq

aws_iam_group
aws_iam_instance_profile
aws_iam_policy
aws_iam_policy_attachment
aws_iam_role
aws_iam_role_policy
aws_iam_user
aws_iam_user_policy

I can confirm this!
Version 0.8.5 didn't have this issue. Version 0.8.6 introduce it.
Workaround: Use version 0.8.5 for this AWS group related objects. But f you need IAM Instance Profile import then you need to use the latest.


Typo in the ACE Paper + Possible Reference Issue

provably  should be	probably
This Reference might be wrong for the following text from the Paper.
"Neural memory architectures provide dynamic episodic state tracking [ 53 ]"
Here is the reference   [53] An introduction to variational autoencoders. Foundations and Trends® in Machine Learning
In that PDF (book), I Didn't find these words, phrases
---  memory (except in references), Neural memory, memory architectures, state tracking, tracking
Found book here --> https://zlib-articles.se/book/79113047/78c0f8

Passed it up the chain, thanks


Switch to faster XPath Evaluator.

see https://github.com/modilabs/enketo/issues/239
Project is ongoing at https://github.com/kirang20/wgxp-java-rosa.

deemed not feasible, see enketo/enketo-wicked-good-xpath


scrcpy quits camera application after exactly 2 minutes

Environment

OS: Windows 10
scrcpy version: 1.17
installation method: Windows release
device model: Samsung Galaxy S5 mini
Android version: 6.0.1

Whenever I mirror my phone front camera and use it as a webcam it quits the camera application after exactly 2 minutes and returns to where I launched the camera application from(in my case the menu)
Since I run scrcpy in 90 degrees clockwise the only thing being put out in the command line is the change of resolution.
Info: New texture: 1280x720
I checked the commands but didn't find any to change that.
Does anybody know a way to fix that?

Whenever I mirror my phone front camera and use it as a webcam it quits the camera application after exactly 2 minutes and returns to where I launched the camera application from(in my case the menu)

Scrcpy does not kill Android app, so either your camera app is crashing or has its own timer.
Check adb logcat or try another camera app :)

Samsung smartphones and tablets shut down the Camera App after exactly 2 minutes of non-activity. Has nothing to do with scrcpy. Try running your galaxy on it's own, and you will see the app shut down after 120 seconds. Very annoying. I've searched the internet for a reason and solution for this nonsense, but could not find anything. I found one forum that guessed that Samsung turns off the camera because the "sensor gets too hot", but I have not seen any hard evidence that is the case.
The camera app is not crashing, it's timing out on it's own.


[FEATURE] Support putFragmentMetadata from kvssink

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
Attention: 45 lines in your changes are missing coverage. Please review.

Comparison is base (6af9a7a) 16.38% compared to head (24d8e46) 16.29%.
 Consider uploading reports for the commit c082d34 to get more accurate results

Files
Patch %
Lines

samples/kvssink_gstreamer_sample.cpp
0.00%
29 Missing :warning:

src/gstreamer/gstkvssink.cpp
0.00%
16 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1122      +/-   ##
===========================================
- Coverage    16.38%   16.29%   -0.10%
===========================================
  Files           51       51
  Lines         6849     6875      +26
===========================================
- Hits          1122     1120       -2
- Misses        5727     5755      +28

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


fix: bump stdlib

stdlib 0.61.0 introduced breaking changes.  Changes:

bumped all stdlib references to 0.61.0
changes assertStrictEq to assertStrictEquals

Hi @qu4k,
thx for contributing to cliffy!
Can you also bump the deno version in the main and all package README.md files please? Than i will merge it.

@c4spar you mean the deno version in the README shields?

yes exactly. The version needs to be ^1.2.0.

@c4spar, this should be ready for review


fixed dots in upper pagination

seems that someone forget to style the dots in the upper pagination bar

Thanks @pablobuenaposada !
Seems like a very minor fix we should just merge. But, I'll wait on a JSPUI user/committer to verify before doing so.

Thanks @tdonohue, we were missing closing more than that span tag!

+1 tested on DSpace-Vagrant, JSPUI discovery with multi-page search results
...

This was merged in "master" and cherry-picked to "dspace-5_x" for the 5.3 release


feat: add support for groups with compatibility with fsm handlers

Using some telebot groups with some fsm manager - bad idea. Because managers will rewrites  base group.

This solution will overwrite middleware chain anyway.
I think real worked solution - copy function tele.applyMiddleware, but i don't do this now.


firestore: unclear why CollectionIterator has no Stop method

// Stop stops the iterator, freeing its resources.
// Always call Stop when you are done with an iterator.
// It is not safe to call Stop concurrently with Next.
func (it *DocumentIterator) Stop() {

All the iterators in this package can be stopped, but not CollectionIterator. Is there a reason for this? If this is by design, I think it should be documented. Otherwise, I'm left thinking that I am not freeing its resources as per the godoc above.

It is by design. I tried to clarify the docs in https://code-review.googlesource.com/c/gocloud/+/30830.