New version: BlenderFoundation.Blender version 4.0.2

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Resolves: https://github.com/microsoft/winget-pkgs/issues/131848

There seems to be a possible issue with the Blender foundation website blocking the winget package manager from grabbing the installer, as I'm getting 403's via https://download.blender.org/release/Blender4.0/blender-4.0.2-windows-x64.msi
I've used https://mirror.clarkson.edu/blender/release/Blender4.0/blender-4.0.2-windows-x64.msi which is an official mirror (albeit US based), will revert to blender.org to see if this passes, though should that fail would the clarkson edu mirror suffice? 🤔

Hi @BiosPlus,
This manifest adds Apps and Features entries that aren't present in previous PR versions. Should these entries be added to the previous versions also?
(Automated response - build 489.)


[BUG] SODStockMarket does not work on existing save on v37.08

Describe the bug
Opening Stockmarket on a cruncher just shows a empty page with "Closed", cannot be exited out of.

Reproduction scenario

Load existing save
Open cruncher

Expected behavior
StockMarket site shows up
Additional context

SODStockMarket v2.0.3
SODCommon v1.1.8
Asset_Bundle_Loader v1.0.4
BepInExPack_IL2CPP v6.0.667

[Message: Preloader] BepInEx 6.0.0-be.667 - Shadows of Doubt
[Message: Preloader] Built from commit 6b500b35727716f8ba182dedae304a628dbbb608
[Info   :   BepInEx] System platform: Windows 10 64-bit
[Info   :   BepInEx] Process bitness: 64-bit (x64)
[Info   :   BepInEx] Running under Unity 2021.3.35f1
[Info   :   BepInEx] Runtime version: 6.0.7
[Info   :   BepInEx] Runtime information: .NET 6.0.7
[Info   : Preloader] 0 patcher plugins loaded
[Info   : Preloader] 0 assemblies discovered
[Message:AssemblyPatcher] Executing 0 patch(es)
[Message:   BepInEx] Chainloader initialized
[Warning:Il2CppInterop] Class::Init signatures have been exhausted, using a substitute!
[Info   :Il2CppInterop] Registered mono type Il2CppInterop.Runtime.DelegateSupport+Il2CppToMonoDelegateReference in il2cpp domain
[Info   :   BepInEx] 10 plugins to load
[Info   :   BepInEx] Loading [AssetBundleLoader 1.0.2]
[Info   :AssetBundleLoader] AssetBundleLoader: Loading bundle 0c0533342366f0d0a47dd50d15e9ee76.bundle with file CAB-37b77ade5e80bd224f8f5edcabd11692
[Info   :Il2CppInterop] Registered mono type UniverseLib.UniversalBehaviour in il2cpp domain
[Info   :Il2CppInterop] Registered mono type UniverseLib.Runtime.Il2Cpp.Il2CppManagedEnumerator in il2cpp domain
[Info   :AssetBundleLoader] Plugin AssetBundleLoader is loaded!
[Info   :   BepInEx] Loading [DDSLoader 1.0.2]
[Info   : DDSLoader] Plugin DDSLoader is loaded!
[Info   : DDSLoader] Plugin DDSLoader is patched!
[Info   :   BepInEx] Loading [SOD.Common 1.1.8]
[Info   :SOD.Common] Setting up configuration bindings.
[Info   :SOD.Common] Plugin is patched.
[Info   :   BepInEx] Loading [HoursOfOperation 0.1.0-BE667]
[Info   :HoursOfOperation] Setting up configuration bindings.
[Info   :HoursOfOperation] Plugin HoursOfOperation is loaded!
[Info   :HoursOfOperation] Plugin HoursOfOperation is patched!
[Info   :   BepInEx] Loading [PrintBugfix 0.1.1-BE667]
[Info   :PrintBugfix] Plugin PrintBugfix is patched!
[Info   :   BepInEx] Loading [RealEstateListingCruncherApp 1.0.5]
[Info   :RealEstateListingCruncherApp] Plugin RealEstateListingCruncherApp is loaded!
[Info   :RealEstateListingCruncherApp] Plugin RealEstateListingCruncherApp is patched!
[Info   :Il2CppInterop] Registered mono type RealEstateListingCruncherApp.RealEstateCruncherAppContent in il2cpp domain
[Info   :Il2CppInterop] Registered mono type RealEstateListingCruncherApp.RealEstateCruncherAppContent+CruncherForSaleContent in il2cpp domain
[Info   :RealEstateListingCruncherApp] Plugin RealEstateListingCruncherApp has added custom types!
[Info   :   BepInEx] Loading [CruncherCorrection 1.0.1]
[Info   :CruncherCorrection] sod.sspj.crunchercorrection v1.0.1: Successfully Loaded
[Info   :   BepInEx] Loading [NoNoticeNonsense 0.1.5]
[Info   :    NoNoNo] sod.sspj.nonoticenonsense v0.1.5: Successfully Loaded
[Info   :   BepInEx] Loading [QoL 1.1.4]
[Info   :       QoL] Setting up configuration bindings.
[Info   :       QoL] Plugin is patched.
[Info   :   BepInEx] Loading [StockMarket 2.0.3]
[Info   :StockMarket] Setting up configuration bindings.
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppMenu get_AppMenu() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppMenu
[Warning:Il2CppInterop] Method Void set_AppMenu(SOD.StockMarket.Implementation.Cruncher.Content.AppMenu) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppMenu value of type SOD.StockMarket.Implementation.Cruncher.Content.AppMenu
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppStocks get_AppStocks() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppStocks
[Warning:Il2CppInterop] Method Void set_AppStocks(SOD.StockMarket.Implementation.Cruncher.Content.AppStocks) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppStocks value of type SOD.StockMarket.Implementation.Cruncher.Content.AppStocks
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppPortfolio get_AppPortfolio() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppPortfolio
[Warning:Il2CppInterop] Method Void set_AppPortfolio(SOD.StockMarket.Implementation.Cruncher.Content.AppPortfolio) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppPortfolio value of type SOD.StockMarket.Implementation.Cruncher.Content.AppPortfolio
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppStock get_AppStock() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppStock
[Warning:Il2CppInterop] Method Void set_AppStock(SOD.StockMarket.Implementation.Cruncher.Content.AppStock) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppStock value of type SOD.StockMarket.Implementation.Cruncher.Content.AppStock
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppFundsInterface get_AppFundsInterface() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppFundsInterface
[Warning:Il2CppInterop] Method Void set_AppFundsInterface(SOD.StockMarket.Implementation.Cruncher.Content.AppFundsInterface) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppFundsInterface value of type SOD.StockMarket.Implementation.Cruncher.Content.AppFundsInterface
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppInstantBuyInterface get_AppInstantBuyInterface() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppInstantBuyInterface
[Warning:Il2CppInterop] Method Void set_AppInstantBuyInterface(SOD.StockMarket.Implementation.Cruncher.Content.AppInstantBuyInterface) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppInstantBuyInterface value of type SOD.StockMarket.Implementation.Cruncher.Content.AppInstantBuyInterface
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppInstantSellInterface get_AppInstantSellInterface() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppInstantSellInterface
[Warning:Il2CppInterop] Method Void set_AppInstantSellInterface(SOD.StockMarket.Implementation.Cruncher.Content.AppInstantSellInterface) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppInstantSellInterface value of type SOD.StockMarket.Implementation.Cruncher.Content.AppInstantSellInterface
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppNews get_AppNews() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppNews
[Warning:Il2CppInterop] Method Void set_AppNews(SOD.StockMarket.Implementation.Cruncher.Content.AppNews) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppNews value of type SOD.StockMarket.Implementation.Cruncher.Content.AppNews
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppTradeHistory get_AppTradeHistory() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppTradeHistory
[Warning:Il2CppInterop] Method Void set_AppTradeHistory(SOD.StockMarket.Implementation.Cruncher.Content.AppTradeHistory) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppTradeHistory value of type SOD.StockMarket.Implementation.Cruncher.Content.AppTradeHistory
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppIntroduction get_AppIntroduction() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppIntroduction
[Warning:Il2CppInterop] Method Void set_AppIntroduction(SOD.StockMarket.Implementation.Cruncher.Content.AppIntroduction) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppIntroduction value of type SOD.StockMarket.Implementation.Cruncher.Content.AppIntroduction
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppBuyLimitInterface get_AppBuyLimitInterface() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppBuyLimitInterface
[Warning:Il2CppInterop] Method Void set_AppBuyLimitInterface(SOD.StockMarket.Implementation.Cruncher.Content.AppBuyLimitInterface) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppBuyLimitInterface value of type SOD.StockMarket.Implementation.Cruncher.Content.AppBuyLimitInterface
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppSellLimitInterface get_AppSellLimitInterface() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppSellLimitInterface
[Warning:Il2CppInterop] Method Void set_AppSellLimitInterface(SOD.StockMarket.Implementation.Cruncher.Content.AppSellLimitInterface) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppSellLimitInterface value of type SOD.StockMarket.Implementation.Cruncher.Content.AppSellLimitInterface
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.Content.AppLimitOrdersOverview get_AppLimitOrdersOverview() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.Content.AppLimitOrdersOverview
[Warning:Il2CppInterop] Method Void set_AppLimitOrdersOverview(SOD.StockMarket.Implementation.Cruncher.Content.AppLimitOrdersOverview) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.Content.AppLimitOrdersOverview value of type SOD.StockMarket.Implementation.Cruncher.Content.AppLimitOrdersOverview
[Warning:Il2CppInterop] Method SOD.StockMarket.Implementation.Cruncher.IAppContent get_CurrentContent() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type SOD.StockMarket.Implementation.Cruncher.IAppContent
[Warning:Il2CppInterop] Method Void set_CurrentContent(SOD.StockMarket.Implementation.Cruncher.IAppContent) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.IAppContent value of type SOD.StockMarket.Implementation.Cruncher.IAppContent
[Warning:Il2CppInterop] Method System.Collections.Generic.IReadOnlyList`1[SOD.StockMarket.Implementation.Cruncher.IAppContent] get_PreviousContents() on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported return type System.Collections.Generic.IReadOnlyList`1[SOD.StockMarket.Implementation.Cruncher.IAppContent]
[Warning:Il2CppInterop] Method Void SetTitleDateHeader(System.Object, SOD.Common.Helpers.TimeChangedArgs) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter System.Object sender of type System.Object
[Warning:Il2CppInterop] Method Void AddPreviousContent(SOD.StockMarket.Implementation.Cruncher.IAppContent) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.IAppContent content of type SOD.StockMarket.Implementation.Cruncher.IAppContent
[Warning:Il2CppInterop] Method Void RemovePreviousContent(SOD.StockMarket.Implementation.Cruncher.IAppContent) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.IAppContent content of type SOD.StockMarket.Implementation.Cruncher.IAppContent
[Warning:Il2CppInterop] Method Void SetCurrentContent(SOD.StockMarket.Implementation.Cruncher.IAppContent) on type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent has unsupported parameter SOD.StockMarket.Implementation.Cruncher.IAppContent content of type SOD.StockMarket.Implementation.Cruncher.IAppContent
[Info   :Il2CppInterop] Registered mono type SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent in il2cpp domain
[Info   :StockMarket] Plugin registered custom types into IL2CPP domain.
[Info   :StockMarket] Plugin initialized stock market hooks.
[Info   :StockMarket] Plugin is patched.

[Warning:     Unity] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects.
[Warning:     Unity] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects.
[Warning:     Unity] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects.
[Info   :       QoL] Adjusted energy restore amount for "MugTea" to "0.07".
[Info   :       QoL] Adjusted energy restore amount for "MugCoffee" to "0.11".
[Info   :       QoL] Adjusted energy restore amount for "StarchKola" to "0.1".
[Info   :       QoL] Adjusted energy restore amount for "TakeawayCoffee" to "0.12".
[Warning:     Unity] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects.
[Warning:     Unity] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects.
[Info   :AssetBundleLoader] Using existing bundle: C:\Users\[user]\AppData\Roaming\Thunderstore Mod Manager\DataFolder\ShadowsofDoubt\profiles\Default\BepInEx\plugins\Piepieonline-RealEstateCruncherApp\realestatelistingcruncherappbundle_stable
[Info   :RealEstateListingCruncherApp] Loading custom asset bundle complete
[Info   :AssetBundleLoader] Using existing bundle: C:\Users\[user]\AppData\Roaming\Thunderstore Mod Manager\DataFolder\ShadowsofDoubt\profiles\Default\BepInEx\plugins\Venomaus-SODStockMarket\stockmarketbundle_stable
[Info   : DDSLoader] Loaded DDS Content and Patches For: Piepieonline-RealEstateCruncherApp
[Info   : DDSLoader] Loaded String Content For: Piepieonline-RealEstateCruncherApp
[Info   :StockMarket] Attempting to load a premod install savegame, a new market economy will be generated for this savegame.
[Info   :StockMarket] Stock market initialized.
[Error  :Il2CppInterop] Exception in IL2CPP-to-Managed trampoline, not passing it to il2cpp: System.Exception: Time is not initialized at this state of the game, check for the property "Lib.Time.IsInitialized".
   at SOD.Common.Helpers.Time.get_CurrentDateTime()
   at SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent.GetCurrentDateTimeReadable()
   at SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent.SetTitleDateHeader(Object sender, TimeChangedArgs e)
   at SOD.StockMarket.Implementation.Cruncher.StockMarketAppContent.OnSetup()
   at Trampoline_VoidThisSOD.StockMarket.Implementation.Cruncher.StockMarketAppContentOnSetup(IntPtr , Il2CppMethodInfo* )

Can you provide a savegame where I can reproduce this?

Sure! here is the savefile that I experienced it on (Notice the .txt at the end, sodb wasn't supported by github.)
All I did was install it, open the save and open the cruncher.
This is the full list of mods I have, I don't think there should be any of those that caused the conflict, but here it is:

SODCommon v1.1.8 by Venomaus
HoursOfOperation v0.1.0 by TeamSpyraxi
BepInExPack_IL2CPP v6.0.667 by BepInEx
DDSLoader v1.0.4 by Piepieonline
Asset_Bundle_Loader v1.0.4 by Piepieonline
RealEstateCruncherApp v1.0.7 by Piepieonline
No_Notice_Nonsense v0.1.5 by PixelJunkies
SODQoL v1.1.4 by Venomaus
PrintBugfix v0.1.1 by TeamSpyraxi
Cruncher_Correction v1.0.1 by PixelJunkies

SODStockMarket

Reuben Schulz Brisbane 2024-25-4-22-45-2216.sodb.txt

Likely gonna need the city as well I guess.
Brisbane.2.3707.CityEditor.citb.txt
Brisbane.2.3707.CityEditor.txt

Thank you for the bug report, I fixed a really serious issue in Lib.Time helper of SOD.Common because of it.
Bug is solved in v1.1.9 of SOD.Common release. Should be released sometime soon.


Misbehavior if zoxide history length <= 2

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
kitty
yazi --debug output
Yazi
    Version: 0.3.3 (Arch Linux 2024-09-05)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.3 (Arch Linux 2024-09-05)

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect : Kitty

Adapter
    Adapter.matches: Kitty

Desktop
    XDG_SESSION_TYPE           : Some("x11")
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some(":0.0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL              : Some("/usr/bin/zsh")
    EDITOR             : None
    VISUAL             : None
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None

Text Opener
    default: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block  : Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : tmux 3.5a
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file             : 5.45
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: 2.2.3
    magick           : 7.1.1-39
    fzf              : 0.55.0
    fd               : 10.2.0
    rg               : 14.1.1
    chafa            : 1.14.2
    zoxide           : 0.9.6
    7z               : 17.05
    7zz              : No such file or directory (os error 2)
    jq               : 1.7.1

Did you try the latest nightly build to see if the problem got fixed?
No, and I'll explain why below
Describe the bug
If only one entry is in zoxide history, Yazi shows the message: No directory history in the database, check out the zoxide docs to set it up. Even if are two entries in the history, but one of it is the current working directory, the message appears.
I except that the history is show as soon as there is at least one entry in the history, also if the entry is the current working directory.
Unfortunately I had no possibility to try nightly build.
Minimal reproducer

Clear zoxide history
Add one new entry to the history
Open Yazi and press z

Anything else?
No response

Hmm. On my linux machine zoxide has no problems if only one entry is in the history. It shows it perfectly in interaction with fzf. And if the history contains no entries it outputs just "zoxide: no match found". Is it os-dependent what you mentioned?

Oh, they fixed it in zoxide 0.9.5 (specifically in https://github.com/ajeetdsouza/zoxide/commit/dbe6f185cf62744a03c107bae1f6c546daa72fb2#diff-f1a262a75a15c046693e28608e526e2c3d73fa8266139cf692bd8f7a4aae522fL115, where they removed --select-1)
But I can still reproduce it in zoxide 0.9.4:

Considering some users might still be using an older version of zoxide, let's keep this behavior for now.

If you put the --exclude also here...

you can reduce the length comparision to 1...

Then it only shows the No directory history...-message if HIST_ENTRIES - CWD == 0. And in all other cases the history is shown correctly.
But I couldn't check this to the zoxide-0.9.4 version.

Yes, but that doesn't change the fact that we still need more than 1 (>= 2) history entries, if one of them is cwd itself.
It just shifts the workload Yazi is doing over to zoxide, but it won't help with hacking to fix the interactive behavior of the old zoxide version.

I dug into it and found that zoxide offers a _ZO_FZF_OPTS environment variable, which lets you completely rewrite the fzf parameters to fix the behavior of older zoxide versions, and this env variable has been supported since 0.4.2, will create a PR for it later.

Please try https://github.com/sxyazi/yazi/pull/1822

I tested it with nightly build on Win11. It works if history length > 0.
But if history length == 0, this message in yazi is shown...

and on the command line this message...

But I according to lua file, I think this message should be shown in yazi:
No directory history found, check Zoxide's doc to set it up and restart Yazi
Or did I need something to configure before using it?

I can't reproduce it. Are you sure you renamed/deleted the db.zo history database file?
https://github.com/user-attachments/assets/8d1a1643-54aa-4719-89a4-5f8c5309cd6a
What's your zoxide version? Could you try debugging zoxide.lua a bit as per https://github.com/sxyazi/yazi/issues/1813#issuecomment-2427368115 and see if zoxide query returns the expected result on your system?

I rechecked the new nightly build  and it is working now. Maybe I did something wrong before.


Multiple Instances of CSS properties on inline CSS

Issue description:
Thanks for your great effort. While i was trying to live preview text color of breadcrumbs. Inline CSS was inserted but it was replaced by default style.css. Next i found properties are being repeat for 3 times.
Here is the code i am using
Suffice_Kirki::add_field( 'suffice_config', array(
	'type'			=>	'color',
	'settings'		=>	'suffice_breadcrumbs_font_color',
	'label'			=>	esc_html__( 'Breadcrumbs Font Color', 'suffice' ),
	'description'	=>	esc_html__( 'Controls the text color of breadcrumbs', 'suffice' ),
	'section'		=>	'suffice_section_breadcrumbs',
	'priority'		=>	10,
	'default'		=>	'#cbc9cf',
	'choices'     	=> array(
		'alpha'			=> false,
	),
	'transport'		=>	'postMessage',
	'js_vars'		=>	array(
		array(
			'element'	=>	'.breadcrumbs .breadcrumbs-trail a',
			'function'	=>	'css',
			'property'	=>	'color'
		)
	)
) );

Here is what I found while inspecting

Version: 2.3.7
I am still not sure while default color properties for text is not being overwritten by inline CSS.
Update:
Just found Li was missing before a tag. That solved the live preview issue. But still why there is 3 more inline style?
Thank you

Does this only happen while in the customizer?
Or are you having this issue in the frontend of your site?

Can't replicate using the develop branch, so I'll go ahead and close this one.


BOSH: Uncaught Error on timeout

I'm using stanza with BOSH. The current implementation has a retry mechanism which works mostly just fine.
However, an uncaught error is thrown here when constructing a new Buffer-Object because body is in case of a timeout undefined (See trace below).
On first sight this seems odd, as this happens in a then-block. The problem lies in chaining of the promise then and catch methods: When chaining a then after a catch, it is also executed which in this case is not desired!
The following code tries to illustrate the issue:
Promise.reject('error')
  .then((result) => console.log(`Result is: ${result}`))    // <-- is not called as expected
  .catch((err) => console.log(`Error is: ${err}`))             // <-- is called as expected
 .then((result) => console.log(`Result is: ${result}`))    // <--- Gets executed and result is undefined!

I can fix this issue but I first wanted to discuss on what is the best way to fix it. We can either refactor the retryRequest so that the then on the resulting promise is only called when body is defined and rejected otherwise. In case of a failure, it would be desirable to emit an event so that users can handle this problem. What do you think?
Here the original trace (via Zone.js)
Error: Uncaught (in promise): TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
    at fromObject (index.js:311)
    at from (index.js:137)
    at new Buffer (index.js:113)
    at eval (bosh.js:278)

Thanks :tada:


add slabs workgraph

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 47.05882% with 27 lines in your changes missing coverage. Please review.

Project coverage is 62.56%. Comparing base (3909083) to head (0fb8a93).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

workgraph_collections/ase/common/surface.py
43.33%
17 Missing :warning:

workgraph_collections/ase/espresso/pw.py
16.66%
10 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   68.27%   62.56%   -5.71%
==========================================
  Files          15       19       +4
  Lines         435      537     +102
==========================================
+ Hits          297      336      +39
- Misses        138      201      +63

Flag
Coverage Δ

python-3.11
62.56% <47.05%> (-5.71%)
:arrow_down:

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

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


Rich text sanitization removing img tag incorretly

Description
Rich text sanitization removing img tag incorrectly. The current sanitize-html package is removing img tag used in the CKEditor. I have updated the package to use the dompurify as we're using in the HTMLElement widget.
Extra: Fixed incorrect config name being used for allowed content configuration.
Pull request checklist

[x] All new and existing tests passed
[x] I run lint command locally and it doesn’t give errors
[ ] PR title properly formatted [XX-000]: description
[ ] Added record to packages' CHANGELOG.md
[ ] Bumped package version in package.json and package.xml
[ ] Added a link to related project PRs (atlas, pluggable-widgets-tools, testProject, etc.) (optional)
[ ] Created docs PR to mendix/docs and added a link (optional)

Pull request type

[ ] No code changes (changes to documentation, CI, metadata, etc)
[x] Dependency changes (any modification to dependencies in package.json)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Test related change (New E2E test, test automation, etc.)

What should be covered while testing?
The image tag shouldn't be removed when sanitization is enabled.

Great job! But, we have a pr (#254) that fixes issue with edit mode 😬 . Can we please merge it first and then merge your fix? In mentioned PR there are already version bump, etc.
cc: @leonardomendix

@iobuhov sure, no problem! I still have more 2 PRs to open about the Rich Text, we can merge those after this PR you mentioned. I'll add the bump version and changelog in the last one. 😎


[Embeddingapi] TC add for setTextZoom with CSS3 columns

Impacted tests(approved): new 2, update 0, delete 0
Unit test platform: Crosswalk Project for Android 19.49.514.0
Unit test result summary: pass 2, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/CTS-712

lgtm


write/read:Int

Unless using 32 as the total bits, the number is treated as unsigned.
write:Int(-4, 32)
print(read:Int(-4, 32))

-4
write:Int(-4, 8)
print(read:Int(-4, 8))

252

this is all fixed in my local copy, i will choose to commit it sometime later


Add Laravel 5.8 support

@kaidesu Is there any issue?

@kaidesu Please review the pr, thanks

What is the last situation?

just need some time to test - I'll get around to it, don't worry 👍

@kaidesu So did you test?

Sorry - we got Laravel 5.8 support in v6.0.0!


Move multiplicative_generator from FFTField to Field

Currently multiplicative_generator is a method defined on FFTField. We should instead move this to Field, since all fields have a multiplicative generator, not just FFTField's. (Furthermore, there are contexts where one may not have an FFT-friendly field, but still needs the multiplicative generator for it)
This would be a breaking change, that I think would require a change to every curve in curves.
(Thanks to @mikerah for pointing this out in telegram)

How easy is it to test if an element is a generator? It's not clear that factorizing (p^n - 1) is easy for arbitrary p and n. (p - 1 is a factor of p^n - 1, but there must be other prime factors too.)

See https://trac.sagemath.org/ticket/31686 for factoring pn - 1. Summary: yes it is easy in the cases likely to arise in Arkworks, using the code at https://trac.sagemath.org/ticket/31686#comment:7 .

That’s perfect, thanks!

Ah yeah, I was going to suggest some possibility of factorization by cyclotomic polynomials since $ x^n - 1 = \Prod_{d | n} Φ_d(x) $, but it seems like the link covers this.
I'm assuming this hasn't been implemented into arkworks yet?  If not I will start here.

@pwang00 indeed it hasn't been implemented yet, so you can start there. Please feel free to ask any questions!


RTT value initialization during device discovery

Describe the bug
The discoverymgr runs the deviceDetectionRoutine function to find devices at regular intervals.
During this period, it sets the RTT value to 0 even if the corresponding data is in the networkdb.
Expected behavior
If the networkdb doesn’t have corresponding data, the networkdb should insert or update the network information.
Screenshots

Test environment configuration (please complete the following information):

Firmware version: Ubuntu 16.04
Hardware: x86-64
Edge Orchestration Release: Baobab

@t25kim Thank you for this report! It definitely is a bug and should be fixed. Could you propose the solution for this reported bug? :D


add coreos-teardown-initramfs-network.service

This is a forward port of coreos-teardown-initramfs-network.service
from the spec2x branch [1] (used for RHEL CoreOS). When moving to NM
in the initrd [2] we decided that we also needed a mechanism to take down
the networking between the initramfs and the real root. While we would
like to use NetworkManager's logic to do this operation in the future
it's currently not easily achieved because NetworkManager is not running
persistently in the initramfs [3].
Additionally, we have decided to propagate initramfs networking configuration
in some scenarios [4]. The policy here is:

If a networking configuration was provided before this point
(most likely via Ignition) and exists in the real root then
we do nothing and don't propagate any initramfs networking.
If a user did not provide any networking configuration
then we'll propagate the initramfs networking configuration
into the real root.

[1] https://github.com/coreos/ignition-dracut/pull/78
[2] https://github.com/coreos/fedora-coreos-tracker/issues/394
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1814038
[4] https://github.com/coreos/fedora-coreos-tracker/issues/394#issuecomment-599721173

this is working in initial tests but I need to look at things more comprehensively before we merge this.. setting to draft for now

I think one reason we weren't doing this in FCOS is that we ended up with two DHCP leases or something.  We need to also kill dhclient; maybe it's watching for the interface going down, but that's going to be racy because it may not have a chance to release the lease before being killed by switchroot.

@cgwalters - I haven't seen any issues with that in initial tests with NM in the initrd. I'll watch out for it.

I think the double lease issue was fixed since https://github.com/coreos/fedora-coreos-config/pull/82.

Could we split the tearing down part from the persisting part? Presumably once we can use NM for the latter, that service would just be e.g. ExecStart=nmcli networking off, right?

Could we split the tearing down part from the persisting part? Presumably once we can use NM for the former, that service would just be e.g. ExecStart=nmcli networking off, right?

right.

though one problem with doing that is the question of who is responsible for removing /run/NetworkManager/* files. Is it the teardown or the propagate.

ok I talked with jlebon and we are going to leave this in a single teardown script/service for now.
I did a bunch of testing on this using a script to simulate different scenarios. It seems like things are going well so far. This script is at https://dustymabe.fedorapeople.org/fcos-network-testing.sh . I need to find the right place to put it for now. I've been told that network testing in our CI is going to be somewhat limited for now because of unpriv qemu networking but maybe we can use this script as inspiration for CI tests when that is no longer a blocker.

LGTM, I guess my commends were nits.

FYI: I've been testing this using an ugly script for now (better than hand testing at least 😄). It goes through and makes sure variations of initrd passed networking config and ignition passed networking config works. See https://github.com/coreos/fedora-coreos-config/pull/316


feat: generated command outputs

Closes #731

This change is

@princeibs  is this ready for review or still in progress?

@TAdev0 Still in progress


Version 1.18.3 does not appear as a function

In version 1.18.2, the import of sanitize-html appeared to be a function, but with the release of 1.18.3, it appears to be an empty object, preventing the use of this library.

Nevermind, this is a dupe of  #241


Human readable UUID logs

@pawurb opened a PR for this sometime ago, which unfortunately did not end up getting merged due to the approach taken but the issue / pain is real ;)
Current behavior
Ecto.UUID values are currently logged at binary ids with is completely unreadable and makes working with UUIDs pretty painful.

Expected behavior

For context: https://github.com/elixir-ecto/ecto_sql/pull/292 & https://github.com/elixir-ecto/ecto/pull/3531

As mentioned in the issue, there needs to be some mechanism to annotate the log how to format types. Preferably in a way where don’t end up encoding the data again. We don’t have bandwidth to explore solutions, so unless someone devises an approach, we will likely end up closing this. :) thanks!

I have one idea. In the Ecto.Query.Planner we traverse the query casting parameters. We could both cast parameters and keep the original parameters as is. We would pass the original parameters as an option to the adapter, something like :log_params, which we then use for querying.

Thanks a lot for the proposal @josevalim, I want to say I can take this but the planer is a pretty challenging beast on its own and I am not that familiar with the code base. If nobody else volunteer to do that part, I can try to dig into it but I would need some guidance please. Thanks !

Yes, the planner is actually the most complex part of the codebase but I think you keep most of your changes small. In particular, you are only worried about the plan operation, as that handles in params. This code is responsible for handling params:
https://github.com/elixir-ecto/ecto/blob/b30e581e60662c307bfbc06c1970c3b519c31d48/lib/ecto/query/planner.ex#L736-L749
You can see that it is adding the current param v to the accumulator acc, I would change to something like this:
   case cast_param(kind, query, expr, v, type, adapter) do
      {:in, cast_v_and_v} -> {Enum.reverse(cast_v_and_v, acc), false}
      cast_v -> {[{cast_v, v} | acc], cacheable?}
    end

In other words, the goal is to keep all values and their cast versions. This implies a couple things:

You will have to change whatever returns {:in, _} to keep both v and cast_v

The return of plan_cache (the thing that returns all params that you collect above), is now inaccurate. It returns a list of tuples instead of a list of values. You should change plan_cache to call Enum.unzip, so you get both params and original_params (i.e. cast_v and v), and return a four element tuple instead.

Doing the changes above will require changes in other parts of Ecto, but if you can do the above and make the suite pass (even if you don't use the original_params anywhere, it will be 95% of the job. The rest is easy and we can touch point later.

I had an idea for this and was curious if the general approach is ok before finishing a PR.
The idea is to have the adapter dumpers specify whether they want to keep the cast value for a type. This will wrap the value in a struct %Ecto.Query.Param{cast: cast, dump: dump} and then cast will be sent to the logger and dump to the driver.
The upsides I see:

not having to keep 2 copies of every param
adapter creator has freedom to choose which types are better logged as cast. we don't have to worry about breaking anything by switching all types over to cast

The downsides I see:

some extra work for the adapter creator if they want to take advantage of the improved logging. but i tried to keep it simple/easy
have to loop through the params to extract the dumped value before sending to the driver, in case any of them are wrapped in the new struct

I have an implementation in my own branches to give a better idea of what I was thinking:
ecto_sql: https://github.com/greg-rychlewski/ecto_sql/commit/d666040bcdc51e854e86a4c82dae3a8b38873b81
ecto: https://github.com/greg-rychlewski/ecto/commit/18469aead4b7494823f90ea3c21160f063c9c24f

Could we perhaps use the existing Tagged struct? I think adapters can already return it and they are passed forward.

Thanks a lot @greg-rychlewski for implementing this !

No worries :). I still need to add it for insert_all and assigned myself this ticket incase you'd like to track the progress: https://github.com/elixir-ecto/ecto/issues/3933


Add public API to configure debug logging

Is your feature request related to a problem? Please describe.
For debugging, sometimes we need to enable logging in the SDK.  Currently this can be done by cash.z.ecc.android.sdk.internal.Twig.enabled(true).  This is non-obvious for someone looking at the API and Twig is an internal API.
Describe the solution you'd like
Add a public API that makes it easy to enable logging.
The exact implementation may depend on decisions made for #482.

Closing as still not implemented. Will be replaced with https://github.com/Electric-Coin-Company/zcash-android-wallet-sdk/issues/1435


Pass context to api calls

This PR refactors methods to pass context to api calls to be context aware.

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@k-yomo are you able to add a changelog entry here?

@tobio
I added to changelog!  Also fixed missing parameter error🙏

jenkins test this


Set gain using setTargetAtTime

Proposed changes
Always set gain values using setTargetAtTime, instead of setting gain.value
I added a constant to the audio engine to help with this, because setTargetAtTime needs a time constant. According to the web audio docs, the value reaches 95% of its target value after three times the time constant. I set the constant to one third of one frame at 30fps, so that the value will reach 95% in one frame.
Reason for changes
Resolves https://github.com/LLK/scratch-audio/issues/68

So it'll take 2 frames in 60fps mode?

Thanks for the help @paulkaplan and @mrjacobbloom.  After some discussion and further experiments we decided to rename this to DECAY_TIME as Paul suggested, and reduce the value down to 1 millisecond, which is a short interval that does not cause a clicking sound when e.g. changing the volume 100 to 0, or changing the pan from 100 to -100.

Ha! I guess it's because of the audio distortion, which sounds a bit like a zipper being zipped, that you get when you rapidly update an audio parameter, but it's not smooth, so you get a click or other glitch at each update...


Last Week in Pony - August 30, 2020

The "docker-builder" shared docker container is being deprecated and not being replaced. If you are using for anything, be aware that there will be no further updates. The existing image will continue to work via being pulled from docker hub.

Flynn aims to bring a Pony-like actor-model implementation to Swift. It is powered by a modified version of the Pony Runtime and utilizes a custom linter to enforce actor-model safety at compile time.

Audio from the August, 25 2020 Pony Development sync is available: https://sync-recordings.ponylang.io/r/2020_08_25.m4a

Version 0.3.0 of ponylang/release-notes-bot-action has been released.
See the release notes for more details.

Version 0.3.0 of ponylang/changelog-bot-action has been released.
See the release notes for more details.

Version 0.1.0 of ponylang/action-readme-version-updater has been released.
See the release notes for more details.

We will no longer be announcing Pony compiler releases on Twitter.
You can get information about releases either here in Last Week in Pony or by subscribing to the RSS feed for ponyc releases on GitHub: https://github.com/ponylang/ponyc/releases.atom

Version 0.37.0 of ponylang/ponyc has been released.
See the release notes for more details.

Version 0.6.1 of ponylang/ponyup has been released.
See the release notes for more details.

Version 0.3.2 of ponylang/release-bot-action has been released.
See the release notes for more details.

Version 0.3.1 of ponylang/release-notes-bot-action has been released.
See the release notes for more details.

Version 0.1.1 of ponylang/action-readme-version-updater has been released.
See the release notes for more details.

Version 0.20.0 of ponylang/action-testing has been released.
See the release notes for more details.

Version 0.3.3 of ponylang/release-bot-action has been released.
See the release notes for more details.

Version 0.21.0 of ponylang/action-testing has been released.
See the release notes for more details.


SQL commends not output informational

I fixed this before I created this issue. So gimme a badge for it.
https://www.sqlskills.com/blogs/jonathan/capturing-infomessage-output-print-raiserror-from-sql-server-using-powershell/
$informationalmessagehandler = [System.Data.Odbc.OdbcInfoMessageEventHandler] {param($sender, $event) Write-Host $event.Message };
$Script:DatabaseConnection.add_InfoMessage($informationalmessagehandler) # WARNING: add_InfoMessage will not show up anywere in autocomplete.

The output is limited somewhere to 80,099 bytes. Not sure what that comes from.

I'd close it just to get the bullshit badge, but I do worry about that limit.

I'm closing this. Rather than worry about the max output, I can just break commands to output a reasonable (<90K) amount of text.


Code Housekeeping

A lot of little build housekeeping bundled into one PR.

@gsoltis Any idea why this test might start failing? https://github.com/vercel/turborepo/runs/6830242709?check_suite_focus=true#step:8:89

When I was working in the repository I noticed that turbo.json references a JSON schema file that doesn't exist, as does the documentation. The JSON schema is in schema.d.ts, is this something we should be referencing instead?

@ObliviousHarmony Our base repository is required to be different from everybody else. We generate an up-to-date schema.json for our own repository here:
https://github.com/vercel/turborepo/blob/2419e2fc98a04b698be98e54aae9536498fa15ec/docs/package.json#L11
You can get that generated for you using turbo run schema.

That makes sense, thanks for the clarification @nathanhammond


Segmentation error (core dumped)

I am using Fastapi so whenever i am turning USE_MESA=True
i am getting this error as segmentation error (core dumped) .
can anyone tell why is this error ??

This issue is fixed, please pull the latest code.
See: https://github.com/facebookresearch/AnimatedDrawings/pull/177

yes its working now
Thank You


vitest UI doesn't log html correctly in the "console log" tab.

Describe the bug
When trying to log out HTML text in the console log with vitest UI, vitest UI is cutting up the output a lot, missing entire tags and symbols.
Example of broken output:

This is what the exact same output looks like in my terminal:

vitest UI seems to be removing all lines starting with < so entire lines like <body> are missing in the output.
This makes it extremely hard to debug anything to do with HTML when using vitest UI and I have to revert to using my console every time.
As a React developer who uses @testing-library/react and screen.debug() a lot. I am constantly looking at HTML output in my tests.
Reproduction
Try to console log any HTML in a test with vitest UI.
Or use React testing library's screen.debug method in any component to see the broken output.
System Info
System:
    OS: macOS 12.3.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 3.49 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.0.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.6.0 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 101.0.4951.54
    Firefox: 99.0.1
    Safari: 15.4
  npmPackages:
    @vitejs/plugin-react: 1.3.2 => 1.3.2
    vite: 2.9.8 => 2.9.8
    vitest: ^0.12.1 => 0.12.1

Used Package Manager
pnpm
Validations

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

@MarkLyck
A simple test is working https://stackblitz.com/edit/vitest-dev-vitest-grlue7, what version of vitest are you using?
About the screen.debug we added colored log to the UI (https://github.com/vitest-dev/vitest/pull/1108): it seems that method is also encoding the dom output to be colored and so the editor on the ui shows the formatted html. I have it working using outerHTML on a div (https://stackblitz.com/edit/vitest-dev-vitest-brpxau):
console.log(screen.getByText('Hello').outerHTML);

as expected, the change in the filter makes other use cases not work as they should

ok, the body isn't the problem, the html is sent colored:

there is no solution to this, either it escapes or it doesn't, we can't do both things at the same time, I think it would be convenient to add some warning in the documentation ( using screen.debug and prettyDOM in the UI)

Hello all, I hope this ping isn't an intrusion, but I wound up here from google because I was debugging a very large component and wasn't seeing all the HTML and it felt hopeless for a while for me.  I eventually by chance found out that the env variable DEBUG_PRINT_LIMIT=10000 can help by increasing the amount of test output visible in vitest (and all node tests I guess).
Regards and happy testing!

For anyone who is facing the same Issue and is not concerned with highlighting but wants the formatting thats missing when using just console.log(screen.getByText('Hello').outerHTML); you could use screen.debug(screen.getByText("hello"), 1000, {highlight: false })
That way, your output is formatted just without colors


iOS Implementation for FusionLocalAuth

I don't merge it automatically in case you want to proceed in the same branch. If I should merge every PR, just let me know.

@gr-markin I will take care of the merge. No worries.


Variables not expanding in the providers section of the config toml

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Ethereum providers are not expanded in the config.toml files for the graph-node and the graph-node errors out with the following error:
Jun 28 13:41:40.293 INFO Reading configuration file `/root/graph-node-configs/index_node_0_config.toml` configuration error: the url `${ETHEREUM_RPC_0}` for provider mainnet is not a legal URL: relative URL without a base
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
It's not necessarily a bug, but the steps to reproduce is to pass an env var to the graph-node and then try to read it within the toml file's provider section.
provider = [ { label = "mainnet", url = "${ETHEREUM_RPC_0}", features = ["archive", "traces"] } ]
What is the expected behavior?
The variable should be expanded like in the db connection strings (ie. connection = "postgresql://${postgres_user}:${postgres_pass}@${postgres_host}:5432/${postgres_db}" <--- this works)
This will make our advanced branch of the StakeSquid mainnet repo be more easily managed without having to edit too many filed to get started initially 🙏🏻

Just a note for whoever picks that up: look for shellexpand::env in node/src/config.rs and do something similar for the provider URL's in the config module.


[MINOR] Small Selenium test fixes

What is this PR for?
Remove unused imports;
Replace "Thread.sleep" (unstable solution);
Add "deleteTestNotebook()" method  -> testWidth.
What type of PR is it?
[Refactoring]
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?
Travis-CI
Screenshots (if appropriate)
https://travis-ci.org/apache/zeppelin/builds/190644901 -> https://travis-ci.org/apache/zeppelin/jobs/190644918
Questions:

Does the licenses files need update? (no)
Is there breaking changes for older versions? (no)
Does this needs documentation? (no)

@bitchelov Thanks for making selenium test more stable!
LGTM and merge to master if no more discussions.

Merged it into master and branch-0.7


Fix heading tag

Fixed to fully use

. Previously used to open
 and then close with
.

OMG - embarrassing! Thanks for finding, and fixing!


Spanner emulator for local testing

Our team is using Cloud Spanner throughout our infrastructure. We are currently testing our code using a remote Spanner instance but are interested in an emulator that can be run locally so as to cut down on test time and allow our testing to scale. Is there any plan to support a local Spanner emulator? Thanks!

@sartorimatt
A beta version of an official emulator for Cloud Spanner has now been released. More information can be found here: https://cloud.google.com/spanner/docs/emulator

Excellent! Thank you for the pointer @olavloite


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

9ee663d: Modified and new Side nav tokens
Design Motivation
Category headings changed to Adobe Clean 12 Medium @ gray-600, to differentiate them from multi-level, top navigation items.
Token Diff
Token added (1):

side-navigation-header-to-item

Token value updated (1):

side-navigation-item-to-header: changed from desktop: 16px mobile: 20px to desktop: 24px mobile: 30px

Run report for f12c62c7
Total time: 49.9s | Comparison time: 45.3s | Estimated loss: 4.6s (9.3% slower)

Action
Time
Status
Info

⬛
SetupNodeTool(18.13.0)
1s
Skipped

🟩
InstallNodeDeps(18.13.0)
15.6s
Passed

🟩
SyncNodeProject(tokens)
0.2ms
Passed

🟩
RunTarget(tokens:buildTokens)
31.1s
Passed

🟩
RunTarget(tokens:buildManifest)
408.5ms
Passed

🟩
SyncWorkspace
0ms
Passed

🟩
RunTarget(tokens:build)
15.7ms
Passed

🟩
RunTarget(tokens:generateDiffResult)
2.2s
Passed

Touched files
.changeset/neat-pets-rhyme.md
packages/tokens/CHANGELOG.md
packages/tokens/package.json


Faithfulness Errors

[x] I checked the documentation and related resources and couldn't find an answer to my question.

Your Question
I got the following error.
ERROR:ragas.executor:Exception raised in Job[9]: AttributeError('NoneType' object has no attribute 'generate')
Code Examples
import openai
from ragas.experimental.metrics._faithfulness import FaithfulnessExperimental
from ragas.metrics.base import get_segmenter
from ragas.llms import llm_factory
from datasets import Dataset
from ragas import evaluate
from ragas.metrics import (
    faithfulness,
)

LLM_NAME = "gpt-4o-mini"
ragas_llm = llm_factory(model=LLM_NAME)

# データセットの準備
dataset = Dataset.from_dict(
    {
        "question": questions,
        "answer": answers,
        "contexts": contexts,
        "ground_truth": ground_truths,
    }
)

# Faithfulnessの言語を指定
faithfulness = FaithfulnessExperimental()
faithfulness.sentence_segmenter = get_segmenter(language="japanese", clean=False)
faithfulness.llm = ragas_llm

# Use the adapted faithfulness metric in your evaluation
score = evaluate(
    dataset,
    llm=ragas_llm,
    metrics=[
        faithfulness,
        ],
                 )
print(score)

@dosu @dosubo
I have almost similar code with the same model gpt 4o mini  and i counter the same error and when i checked what is inside llm_factor(model= MODEL_NAME) i found that
LangchainLLMWrapper(run_config=RunConfig(timeout=180, max_retries=10, max_wait=60, max_workers=16, exception_types=<class 'openai.RateLimitError'>, log_tenacity=False, seed=42))


Dice_Game

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #4027

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @shivan2004 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @shivan2004 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


[Aggregate-reports] Link verification check failing in nightly runs

Aggregate-reports nightly test runs are failing with:

Error message:
##[error][404] broken link https://docs.microsoft.com/javascript/api/@azure/ai-language-text
Checking 24 links found on page file:///D:/a/_work/1/s/sdk/cognitivelanguage/ai-language-text/samples/v1-beta/typescript/README.md
##[warning]broken link https://docs.microsoft.com/javascript/api/@azure/ai-language-text
Checking 2 links found on page file:///D:/a/_work/1/s/sdk/cognitivelanguage/ai-language-text/swagger/README.md
Checking 0 links found on page file:///D:/a/_work/1/s/sdk/cognitivelanguage/ai-language-text/CHANGELOG.md
Checking 1 links found on page file:///D:/a/_work/1/s/sdk/cognitivelanguage/ai-language-text/MIGRATION_ai_text_analytics.md
Checking 28 links found on page file:///D:/a/_work/1/s/sdk/cognitivelanguage/ai-language-text/README.md
##[warning]broken link https://docs.microsoft.com/javascript/api/@azure/ai-language-text

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1723665&view=results

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.37663954,Cognitive - Text Analytics:0.25607947,Docs:0.122019455'

This issue reappears.
For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1828805&view=results


Backport xtensa atomic detection to a 0.7.x release

If we backport https://github.com/rust-embedded/heapless/commit/02935035b12bedea380caa245d6d3f6d815ee3b5 to a 0.7.x patch release, we can avoid breakage as crates slowly migrate to 0.8.
Discussion here

done in #423


Ability to view your own archives as if they were someone elses ("incognito mode"?)

For developing applications that use the DatArchive API, I haven't quite found a way to view one's own archives in Read-Only mode (as if they were someone else's). Did I overlook a way to do so that exists already (0.8.8 on macOS), or would this perhaps be a generally useful feature?

I think you'd need to just do this in your application. You're ultimately going to be reacting to the owner flag


Option to change download directory and naming pattern

Would be great to have an option to change the download directory so we can save the files somewhere else, and an option to customize the naming so we can add the album title to the file name that way if there different versions of the same song they don't get replaced by the other (all this in a centralized directory).

Bump

Please add naming patterns


is Franz has possibility to use Chrome extensions?

hi, @adlk is there have any chances to make Franz support Chrome extensions? such include (Grammarly)[https://app.grammarly.com/] as a part of the recipe.
cuz I'm planning to deploy a recipe which let Franz support Google Translation as service. I use that for a long while, from Franz 4.x to 5.x even when I was using Rambox. but Google Translation cannot do some sort of grammar check, which is kinda important for people who are not native English speaker, like me.

@iamcxa not at the moment. I'm looking into options to add this but I can't promise anything right now.

I know i'm late to the party but i have chromium installed on linux and i have lastpass installed on it. And the chrome extension actually autofills my passwords in franz. so if chromium is available on your OS you might get away installing plugins on it

Would be really great - my team and I would like to use the mailbutler plugin with gmail in Franz. Or does someone has a workaround or another solution?

Update. It's possible to day ?

@AnonStar Rambox, but it's a paid feature.


Revert "refactor Reduce prepare overhead (#33421)"

This reverts commit f56ce5a83ab46fc748fb90c5ba91329c3118f5a9.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Missing files in application when loading it up from cmd

Files aren't loaded properly.

Fixed in last merge pull request.


NeedMediaData with smaller numFrames in prerolling state

Summary: NeedMediaData with smaller numFrames in prerolling state
Type: Fix
Owner: Marcin Wojciechowski
Reviewers: Adam Czynszak, Stuart Pett
Coding Standard Applied: Y
Test Plan: None
Dependencies and Impacts: None
Jira: RIALTO-5, RIALTO-25

https://jenkins.code.rdkcentral.com/job/github-triggered/26046/ started

https://jenkins.code.rdkcentral.com/job/build-component/62231/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18348/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30596/ started.

build-brcm-va Console Log uploaded to Gist URL: https://gist.github.com/8731b6dbc8752625630a19a14fd70563

build-aml-refboard Console Log uploaded to Gist URL: https://gist.github.com/6e35070fcfdbfc1fea013948c94c58a4

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134424/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134425/

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18375/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30624/ started.

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134487/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134486/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134488/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134485/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134511/


nixos/armagetronad: Add module with NixOS tests

Description of changes

New module, services.armagetronad, for hosting Armagetron dedicated servers.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Marking this as a draft because it'll require #263675 to be merged in order to correct the crashing (which this PR replicates)

Ready for review since Armagetron updates were merged.

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

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

Thanks for the feedback @SuperSandro2000. #284626 adds meta.mainProgram to squash the warnings during the build.

@SuperSandro2000 I tried using systemd unit templates, but it doesn't look like they work with per-unit ExecStart being different due to potentially different packages per server. So we're stuck with armagetronad- vs<EMAIL_ADDRESS>

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1479


Organize docs with single lefthand sidebar

Can we please add a single lefthand navigation to the docs?  Something like this:
Home
Installation
Usage
  Overview
  Loading a Delta Table
  Examining a Delta Table
  Querying a Delta Table
  Managing a Delta Table
  Writing Delta Tables
API Reference

This can be done but it will also change how the rest of the pages look, e.g top navigation menus. This is all driven by the theme. Currect version is using material which is popular at the moment. We can choose a style and make our own modifications but we need to choose the overall desired design before making changes to sections.

I am moving the installation guide to the Usage section that will fix this issue: https://github.com/delta-io/delta-rs/pull/1875


Conda environments not detected

I've recently changed from miniconda3 and python 3.6 to anaconda3 and python 3.7. As a result, conda environments are not being detected and added as jupyter kernels.
I have nb_conda_kernels 2.1.1 installed in my base environment (python 3.7.0) and ipykernel 5.1.0 in my external environment (also python 3.7.0).
Within my external environment, I can see a kernel.json file in ~\anaconda3\envs\env_name\share\jupyter\kernels\python3 and its content correctly points to the bin\python directory of that environment.
However, jupyter kernelspec list does not show the environment and it's not available in either jupyter notebook or lab.
Update
I noticed that my jupyter_notebook_config.py only had one entry for something else and nothing for nb_conda_kernels. I guessed that means jupyter is using the default KernelSpecManager.
So, I removed that file and restarted jupyter notebook. Kernels all detected and available!!
Even when I put the file back exactly as it was, I can create new environments and they are detected ok.
So - all is now working for me, but is there an issue installing nb_conda_kernels where a jupyter_notebook_config.py file exists?

I'm not sure this is related, but I recently had a look at my jupyter_notebook_config.py in an editor, without changing anything, at least to my knowledge, and since then, my py37 environment wasn't found anymore, while py36 was still there?
I then went on to reinstall the whole conda py37 environment, but to no avail.
I then tried to conda remove the "nb_conda_kernels" package and received this feedback in the terminal:
$ conda remove nb_conda_kernels                                                                   (py37)
Solving environment: done

## Package Plan ##

  environment location: /Users/klay6683/miniconda3/envs/py37

  removed specs:
    - nb_conda_kernels

The following packages will be REMOVED:

    nb_conda_kernels: 2.2.0-py37_1000 conda-forge

Proceed ([y]/n)?

Preparing transaction: done
Verifying transaction: done
Executing transaction: / + /Users/klay6683/miniconda3/envs/py37/bin/python -m nb_conda_kernels.install --disable
Disabling nb_conda_kernels...
ERROR: The global setting does not match the local setting:
    Global: ENABLED
    Local:  DISABLED
This is typically caused by another configuration file in
the path with a conflicting setting.
Use the --verbose flag for more information.

WARNING conda.core.link:run_script(813): pre-unlink script failed for package conda-forge::nb_conda_kernels-2.2.0-py37_1000
consider notifying the package maintainer
done

I'm not user what's going on there, but I can assure you that I would not deactivate nb_conda_kernels, it's my life blood, and currently I'm quite nervous, in trying for an hour to get back to a working py37 environment. :/

@michaelaye a couple of things. First, where exactly is your jupyter_notebook_config.py file located, and what non-trivial content does it have in it? For instance, mine is in ~/.jupyter/; and I can see what's active with this grep command:
grep -v '^\s*\(#.*\)\?$' ~/.jupyter/jupyter_notebook_config.py

where exactly is your jupyter_notebook_config.py located; and what exactly does it have inside it (ignoring the comments)? For instance, I created one in ~/.jupyter,
Second, you could try using the verbose enable/disable commands:
python -m nb_conda_kernels.install -v --enable
python -m nb_conda_kernels.install -v --disable
python -m nb_conda_kernels.install -v --status

This should help us see what's going on.
The error you're seeing above is telling me that, somehow, your jupyter_notebook_config.py file already has some sort of setting in it that is overriding what nb_conda_kernels is trying to achieve locally.

I think my interpretation of "not having my py37 env" in the notebook is merely the renaming how it appears as discussed in other GH issues.
But for the records, I executed the --status  command from above:
$ python -m nb_conda_kernels.install -v --status                                                                                (py36)
Determining the status of nb_conda_kernels...
Entry points:
  - conda = nb_conda_kernels.discovery:CondaKernelProvider
  NOTE: entry points not used in Jupyter 5.2.3
jupyter_notebook_config.json entries:
  - /etc/jupyter: <no file>
  - /usr/local/etc/jupyter: <no file>
  * /Users/klay6683/miniconda3/envs/py36/etc/jupyter: {
      "NotebookApp": {
        "nbserver_extensions": {
          "jupyter_nbextensions_configurator": true
        },
        "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
      }
    }
  - /Users/klay6683/.jupyter: {
      "NotebookApp": {
        "nbserver_extensions": {
          "jupyterlab_github": true,
          "jupyter_nbextensions_configurator": true,
          "jupyterlab_git": true,
          "nbresuse": true
        },
        "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
      }
    }
Status: enabled

Is maybe the settings in .jupyter clashing with the settings in the conda env when asking for an uninstall, creating above error message?
Your grep through the jupyter_notebook_config only brings up settings related to my notebook server configuration, like port, ip, certfile, keyfile, password and my GH client_id and _secret.

My envs aren't being found on Mac, but are on Windows. On mac, the contents of jupyter_notebook_config.json are sparse:
{
  "NotebookApp": {
    "nbserver_extensions": {
      "jupyterlab": true
    }
  }
}

The kernels are found however:
Robins-MacBook:~ robincole$ jupyter kernelspec list
Available kernels:
  bluesky          /Users/robincole/Library/Jupyter/kernels/bluesky
  circuitpython    /Users/robincole/Library/Jupyter/kernels/circuitpython
  gophernotes      /Users/robincole/Library/Jupyter/kernels/gophernotes
  javascript       /Users/robincole/Library/Jupyter/kernels/javascript
  micropython      /Users/robincole/Library/Jupyter/kernels/micropython
  nodemcu          /Users/robincole/Library/Jupyter/kernels/nodemcu
  python2          /Users/robincole/Library/Jupyter/kernels/python2
  sat_img_env      /Users/robincole/Library/Jupyter/kernels/sat_img_env
  ubit             /Users/robincole/Library/Jupyter/kernels/ubit
  python3          /Users/robincole/anaconda3/share/jupyter/kernels/python3

I know this is an old issue but I also don't want to close it in case someone can properly identify a root cause and solution.
Note however that in this comment I am seeing two copies of the nb_conda_kernels configuration. The one in /Users/klay6683/.jupyter should be removed, leaving only the one in sys.prefix where nb_conda_kernels is itself installed.

Hi, I am experiencing a similar issue on Anaconda3, base(root) environment, python=3.7.3, nb_conda_kernels=2.2.1, ipykernel=5.1.0.
I run:
(base) bash-3.2$ jupyter kernelspec list
Available kernels:
  python3    /Users/benjamin/Library/Jupyter/kernels/python3

However, when I open Jupyter, there are 2 kernels to chose from, as can be seen here

I also check another folder:
(base) bash-3.2$ cd anaconda3/share/jupyter/kernels/
(base) bash-3.2$ ls
python3

So I don't understand where is Python [conda:env root]. (I was searching for it to modify the names.)
I also don't have a jupyter_notebook_config.py, but a jupyter_notebook_config.json in /Users/benjamin/anaconda3/etc/jupyter/. And it holds:
{
  "NotebookApp": {
    "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
  }
}

So I was having a similar issue, possibly the same as FBen3, I'm going to try to outline the steps I took to get my kernels showing up the way I want them too:
I wanted to make sure I was starting fresh with kernels so I decided to try this.

Removing /Users/${USER}/Library/Jupyter/kernels fixes the issue.

Well it didn't fix my issues but it seemed to remove the kernels that looked like the ones in FBen3's post.
Next step is to make sure you really follow the steps in this post especially for manually registering a kernel that already exists. I'll try to outline the important ones:

Update your conda, idk if this is essential but I haven't been using mine in a while and I wanted to make sure I was on the most up to date.
Do conda install nb_conda_kernels on the base environment, I believe this is supposed to auto detect new environments in the future but I actually haven't tested it yet.
Do conda activate into the environment you want to add
Here are the crucial parts: Make sure ipykernel is installed with conda install notebook ipykernel. I thought nb_conda_kernels should be picking up the new kernel but it was not so I had to do the next step.
You need install the kernel. If ipython kernel install doesn't work try ipython kernel install --user, I believe the --user flag is for if your kernelspec is located in /Users/... rather than /usr/.... If you want a to add a specific name do ipython kernel install --user --name [kernel_name] --display-name [kernel_name].  I'm not a 100% sure on that but I think that's why they don't show up.
conda deactivate and jupyter kernelspec list. You should hopefully start seeing the env names there.  Google ranked this thread up pretty high, so I'm posting it here for posterity. For anyone trying to do add conda-installed kernels in Docker, here is the process:
FROM jupyter/minimal-notebook:7a0c7325e470
ARG conda_env=py36
COPY environment.yml /home/${NB_USER}/tmp/

RUN cd /home/${NB_USER}/tmp/ && \
    conda env create -p $CONDA_DIR/envs/$conda_env -f environment.yml

# create Python 3.6 environment and link it to jupyter
RUN $CONDA_DIR/envs/${conda_env}/bin/python -m ipykernel install --user --name=${conda_env}
# any additional pip installs:
RUN $CONDA_DIR/envs/${conda_env}/bin/pip install numpy

# prepend to path
ENV PATH $CONDA_DIR/envs/${conda_env}/bin:$PATH
# optional defaulting
ENV CONDA_DEFAULT_ENV ${conda_env}

# some cleanup because we used the docker-stacks images.
RUN fix-permissions $CONDA_DIR && \
    fix-permissions /home/$NB_USER

(--display-name "Other Python" in the ipykernel step if you want a different display name in the Jupyter dropdown, and you can avoid the COPY with conda create changed to conda create --quiet --yes -n $conda_env python=3.6 pip ipython ipykernel )

Maybe this will offer some insight into what was happening above:
The issue I was trying fix was that on my system (MacOS, python==3.7.6, nb_conda_kernels==2.2.2) my conda environments simply weren't appearing.
In running through some of the troubleshooting above, I noticed that
python -m nb_conda_kernels.install -v --disable
was failing to disable the extension.
$ python -m nb_conda_kernels.install -v --disable
Disabling nb_conda_kernels...
Entry points:
  - conda = nb_conda_kernels.discovery:CondaKernelProvider
Removing from local configuration
Writing config in /Users/hackalog/miniconda3/envs/nlp/etc/jupyter...
jupyter_notebook_config.json entries:
  - /etc/jupyter: <no file>
  - /usr/local/etc/jupyter: <no file>
  * /Users/hackalog/miniconda3/envs/nlp/etc/jupyter: {
      "NotebookApp": {
        "nbserver_extensions": {
          "nb_conda": true
        }
      }
    }
  - /Users/hackalog/.jupyter: <no file>
Status: enabled

Notice the status still enabled at the end.
I traced through that code, and in the end, realized the disabled == True (line 145) code path of  https://github.com/Anaconda-Platform/nb_conda_kernels/blob/1b9e821e7cafe388b633ba4fdb8feb3eec815d6c/nb_conda_kernels/install.py#L140-L151
was not getting entered. I can't tell if that's intentional, or just a missed case in the refactored if statement on line 140.
(In my case, status == False, is_enabled_local == False, enable == False, and is_enabled_entry == True, which is why the code was ignored)
When I backed nb_conda_kernels all the way back to 2.1.1 (before that code path was refactored) , I finally succeeded in disabling nb_conda_kernels; i.e. the config file was changed to:
{
  "NotebookApp": {}
}

Upon re-enabling it, I could finally see all my conda environments (yay). The new config file was
{
  "NotebookApp": {
    "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
  }
}

Now, when I attempt to upgrade to nb_conda_kernels 2.2.2, I get the same error as @michaelaye, namely:
Enabling nb_conda_kernels...
ERROR: The global setting does not match the local setting:
    Global: ENABLED
    Local:  DISABLED
This is typically caused by another configuration file in
the path with a conflicting setting.
Use the --verbose flag for more information.

conda install nb_conda_kernels fixed the problem quite easily since it auto-detects and picks up the existing conda envs

@mcg1969 I think this can now be close as there is a way to render environment visible by jupyter tools.

For future reference (And searchability), what is that way?

@mcg1969 https://github.com/mcg1969 I think this can now be close as
there is a way to render environment visible by jupyter tools.

if that were true, i guess the whole project should be archived? I'm also unaware of other jupyter tools that scan all conda envs for available kernels.

As explain in the README, you can optionally install the virtual conda kernel specs in a place searched for by conda:

Create a configuration file for jupyter named jupyter_config.json in the folder returned by jupyter --config-dir.
Add the following configuration to install all kernel spec for the current user:

{
  "CondaKernelSpecManager": {
    "kernelspec_path": "--user"
  }
}

Execute the command (or open the classical Notebook or JupyterLab UI):

python -m nb_conda_kernels list

Check that the conda environment kernels are discovered by jupyter:

jupyter kernelspec list

The kernelspec path needs to be writable by the users as kernelspecs will be dynamically updated by nb_conda_kernels.

@fcollonval I think my jupyter_notebook_config.json is dynamically being created from my jupyter_notebook_config.py in the same folder so I'm not sure one should directly edit it? At least I never created it but still am getting it automatically after setting up new jupyter environments on new machines.

The json format and the py format are both acceptable. And configuration are merged from the two files (with JSON having a higher priority). So I'll be surprised if jupyter_notebook_config.json is generated from the Python script. What is true, is that running command like jupyter serverextension enable/disable are editing the JSON file. But at no point should a tool generates it (i.e. removing value from it).
To take a parallel, it is like git config. It modifies your git config file. But nevertheless you can change the config file manually.

There is only one exception for jupyter: if you use the flag --generate-config. But it will ask a confirmation if a file already exists.


Update Gambit, Gerbil, Glow

Update Gambit, Gerbil and Glow with Glow's first release v0.1.0.
Also include some changes in lib that Gerbil support relies on, notably including the POP object system, which by now is rather stable and proven for the purpose of building coherent locally modified sets of packages.

Motivation for this change
Things done

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

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

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

@7c6f434c

I don't understand the failure in the grahamcofborg-eval job above.

I could move the lib stuff to its own PR, but since it's actually of negative value unless used, that would be a catch-22.
Actually, I initially wanted to put pop inside gerbil... but then I found I couldn't extend gerbil with pop if pop was itself in gerbil (or at least it was trickier and uglier). So I moved it to lib, where it belongs eventually. I even started an RFC (82) about having an "official" way to deal with such "experimental" libraries, but it doesn't look like this will ever happen.

I created a PR just for the POP thing: https://github.com/NixOS/nixpkgs/pull/116275

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114449 run on x86_64-linux 1

5 packages built:

gambit
gambit-unstable
gerbil
gerbil-unstable
glow-lang

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

gambit:

warning: attribute-typo
A likely typo in git-version argument was found, did you mean version?
Near pkgs/development/compilers/gambit/build.nix:25:10:
   |
25 |   inherit src version git-version;
   |          ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md
warning: unclear-gpl
lgpl21 is a deprecated license, check if project uses lgpl21Plus or lgpl21Only and change meta.license accordingly.
Near pkgs/development/compilers/gambit/gambit-support.nix:35:5:
   |
35 |     license     = licenses.lgpl21; # dual, also asl20
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern<EMAIL_ADDRESS>doesn't match anything in file 'config.status'
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md

Can I insert a comment to disable the attribute-typo warning on line 25 of .../gambit/build.nix ? Other warnings were useful, and fixed.

@SuperSandro2000 should git-version be reported as possible typo when version is also there?

Can I insert a comment to disable the attribute-typo warning on line 25 of .../gambit/build.nix ? Other warnings were useful, and fixed.

No, nixpkgs-hammering does not have such a feature right now.

@SuperSandro2000 should git-version be reported as possible typo when version is also there?

probably not.

but then I found I couldn't extend gerbil with pop if pop was itself in gerbil (or at least it was trickier and uglier).

I still don't get it (and we don't have enough shepherd volunteers to reopen global-POP RFC so it makes sense to revisit the least-impact approach).
Let POP live in gerbil directory tree, every version of Gerbil just imports POP and uses it, and then reexports it. If you need POP to extend Gerbil, you just grab it (and it doesn't matter where you grab it from, it is the same import)
I guess you could also have default.nix for Gerbil doing just general composition and defining attributes for various versions, then the top level would just inherit the attributes from it. Then POP can also be taken from gebrilVersions too, if desired.

As in put it in the passthru of some derivation? Would that cause the derivation to be built?
Or just register it under pkgs.gerbil-support.POP or something?

Nix is lazy, so passthru stuff can be used without building the derivation to which it is attached. gerbil-support makes sense, too, of course. I don't have strong opinions here, I just want to avoid global lib changes that are large enough to be controversial.


Tests are not consistent and some are not skipping some tests

I noticed this while going through the rna exercise. It seems that none of the tests are skipped. Should this be changed? I wasn't sure if there may be an additional parser that would made the change before giving it to a user.
https://github.com/exercism/dart/blob/ef475fb4f2a06f1a3193c15d281eb56a4e35c5a0/exercises/rna-transcription/test/rna_transcription_test.dart#L19
My thinking was perhaps they are not set to true in order to run the tests in this project.
Additionally, the test files are organized differently from each other. I think we want consistency in the format and to skip all but the first test by default.

These are great observations @Stargator.

It seems that none of the tests are skipped. Should this be changed?

I think probably yes—if we skip tests in any of the exercises, I think we should skip them in all of them. I've written a little bit about the background for why I originally added skips to tests, and why I think it's probably the right thing to do: test suite anatomy

I wasn't sure if there may be an additional parser that would made the change before giving it to a user.

No, the tests are delivered as-is from the repo.

My thinking was perhaps they are not set to true in order to run the tests in this project.

This is always a bit tricky. We want to provide the best possible experience for the end-user, but we also don't want to have to edit the tests locally every time in order to run the tests. We also don't want to accidentally check in the changes if we do edit them to run the tests while working on the exercises. I wrote a bit about this in the tooling and ci doc for the "launch a track guide", in case that helps here.

Additionally, the test files are organized differently from each other. I think we want consistency in the format and to skip all but the first test by default.

Yeah, I think we should be consistent wherever we don't have a compelling reason to do otherwise.
Often it takes a while in a newer track to figure out all the patterns that we want, so it feels like it's the right time to think about this now.
@SuperPaintman You've got the most context about the history and background of this track. I'd love to hear your perspective on all of this, since you might well have made some decisions deliberately/carefully, and we might not see all the reasons.

There can be a compelling reason to introduce "groups" into the test files. Cause they are a concept used by the framework to organize tests we may want to slowly expose users to them over the course of exercises.

Nice! Yeah, I think we have some exercises where this would be a natural fit.
Does the test suite also allow you to run "focused" tests in any way (by line number or test name or group or whatnot?)

By group name, yes. Not sure about line number.
As for test name, I think tests are automatically run once they are defined. This can be seen by the group functionality.
From the Difference of Squares test:
void squareOfSums() { // Wrap the group with a function and then wherever the function is called the group will be called as well.
    group("#squareOfSums()", () {
      test("square of sum 1", () {
        expect(squares.squareOfSums(1), equals(1));
      });

      test("square of sum 5", () {
        expect(squares.squareOfSums(5), equals(225));
      });

      test("square of sum 100", () {
        expect(squares.squareOfSums(100), equals(25502500));
      });
    });
}

Then there are tags, which can be applied to individual tests, groups, or suites. Then either by running an argument with pub run test or configuring dart_test.yaml, you can specify which tests are run by tags.

Interesting. So another option we have, instead of skipping, would be to use a tag for the active tests to run, and then people would add the tags. Then you could run the whole test suite by just not specifying any tags.

I'm going to suggest we add tags to a later exercise(s) and just use the first 10 exercises to introduce the language, the test framework, the package manager, and analysis tool. especially for beginners that's a lot to take in.

Speaking of which, I noticed none of the current tests seem to be dependent on another. Are we not going to guide users into the language/framework/tools by controlling the first 10 exercises they work on?

I noticed none of the current tests seem to be dependent on another.

Do you mean that none of the tests for any of the exercises depend on tests for any other exercises?

Are we not going to guide users into the language/framework/tools by controlling the first 10 exercises they work on?

We have a whole lot of control.
We can set "core": true on 8 to 20 exercises, which will need to be completed in the order specified in the exercises array in config.json. All of the core exercises must be completed in order to complete the track. In the normal usage of the v2 site, you cannot move on to the next core exercise until the mentor approves your solution.
Each core exercise should unlock about 3 additional (optional) exercises. You don't have to complete any of these in order to complete the track, however we expect people to do so, while they're discussing their core exercises with mentors.
You will typically get feedback from mentors on optional exercises, as well.
So we can do a lot to guide people along the way, in particular we can add this guidance to the core exercises.
We should not have dependencies between exercises, I think. Each exercise should be stand-alone, though the knowledge learned from previous exercises can be relevant to solving the next one.

Do you mean that none of the tests for any of the exercises depend on tests for any other exercises?

I meant to say, none of the exercises block other exercises. @kytrinyx's response to the other comment was helpful.
Then I think we should determine what order we want the current exercises to be in. Then we can determine where to introduce concepts like groups, setup/teardown, etc.

Then I think we should determine what order we want the current exercises to be in.

Agreed.

@kytrinyx Closing this discussion to focus talks about the order of the exercises in another thread.


workload - health checks are lost when creating deployment

rancher:master-3375-head
Steps:

set health checks when creating a deployment for the dashboard

create the deployment

Results:

the deployment is created
but the health checks are lost

health checks are NOT included in the POST request payload

the bug fix is validated on master-3398-head
the steps are the same.
The health checks are set properly in the request. The workload is deployed successfully and the values are elected in the dashboard.


Unable to install

Unable to install
Your system is up to date! Continuing with PiVPN installation...
Can't call method "set" on an undefined value at /usr/share/perl5/Debconf/FrontEnd.pm line 126,  line 5.
Use of uninitialized value $ret in scalar chomp at /usr/share/perl5/Debconf/Client/ConfModule.pm line 132,  line 4.
Use of uninitialized value $ret in split at /usr/share/perl5/Debconf/Client/ConfModule.pm line 133,  line 4.
Use of uninitialized value $ret[0] in string eq at /usr/share/perl5/Debconf/Client/ConfModule.pm line 134,  line 4.
Use of uninitialized value $ret[0] in string eq at /usr/bin/debconf-apt-progress line 350,  line 4.

I get this on Ubuntu:
+ command -v debconf-apt-progress
+ grep -q https /etc/apt/sources.list
+ debconf-apt-progress -- apt-get --yes --no-install-recommends install openvpn git tar wget grep iptables-persistent dnsutils expect whiptail net-tools
Can't call method "set" on an undefined value at /usr/share/perl5/Debconf/FrontEnd.pm line 126, <GEN0> line 5.
Use of uninitialized value $ret in scalar chomp at /usr/share/perl5/Debconf/Client/ConfModule.pm line 132, <STDIN> line 4.
Use of uninitialized value $ret in split at /usr/share/perl5/Debconf/Client/ConfModule.pm line 133, <STDIN> line 4.
Use of uninitialized value $ret[0] in string eq at /usr/share/perl5/Debconf/Client/ConfModule.pm line 134, <STDIN> line 4.
Use of uninitialized value $ret[0] in string eq at /usr/bin/debconf-apt-progress line 350, <STDIN> line 4.

you both did not tell what distro version you are using.
pihole installer seems to have a similar problem:  https://www.reddit.com/r/pihole/comments/6n9e0w/cant_install_pihole_get_these_errors_tried/

you both did not tell what distro version you are using.
pihole installer seems to have a similar problem: https://www.reddit.com/r/pihole/comments/6n9e0w/cant_install_pihole_get_these_errors_tried/

Using  raspbian stretch

I came across the same error when reinstall pivpn. I tried this and it fixed the issue.
apt-get install --reinstall debconf

I got the problem after installing, uninstalling and reinstalling pivpn.
The directory /opt/pivpn does not exist. The pivpn command ist not available.
What can I do to clean the system so that a new installation is possible?
:::
::: You are root.
::: Verifying free disk space...
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
::: Static IP already configured.
::: Using User: pi
:::
::: Checking for existing base files...
:::    Checking /etc/.pivpn is a repo... OK!
:::     Updating repo in /etc/.pivpn... done!
:::
::: Stopping OpenVPN service... done.
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
::: Install Complete...
::: Restarting services...
Synchronizing state of openvpn.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable openvpn
::: done.
:::
::: Installation Complete!
::: Now run 'pivpn add' to create an ovpn profile for each of your devices.
::: Run 'pivpn help' to see what else you can do!
::: It is strongly recommended you reboot after installation.
:::
::: The install log is located at: /etc/pivpn/install.log

Please give it a shot again as a couple of issues have been fixed in the meanwhile.
I'd recommend reinstalling raspbian and running PiVPN again.
then if you still see the same issue please comeback and fill the issue template the best you can please.
Kind Regards.


Adjust bundle notation while referencing templates in services

Hi!
As reported here the new SyliusThemeBundle has removed support for bundle notation while referencing templates. This PR will fix the problem also in the service arguments.

Thanks!