Memory Leaks after updating to 4.2-stable

Today I've updated my engine to v4.2-stable and after closing the engine on verbose mode I get several memory leaks coming from this addon:

`
Unloading: Finished disposing tracked instances.
XR: Clearing primary interface
XR: Removed interface "Native mobile"
XR: Removed interface "OpenXR"
ERROR: 6 RID allocations of type 'N5GLES312LightStorage11ShadowAtlasE' were leaked at exit.
ERROR: 6 RID allocations of type 'N5GLES312RenderTargetE' were leaked at exit.
ERROR: 35 RID allocations of type 'N5GLES37TextureE' were leaked at exit.
ERROR: Texture with GL ID of 18: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 20: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 21: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 26: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 30: leaked 520 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 38: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 40: leaked 760 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 44: leaked 684 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 45: leaked 684 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 46: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 48: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 54: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 66: leaked 340 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 67: leaked 340 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 76: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1015: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1017: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1018: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1019: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1020: leaked 1364 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1059: leaked 699050 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1060: leaked 131072 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: Texture with GL ID of 1066: leaked 174762 bytes.
at: ~Utilities (drivers/gles3/storage/utilities.cpp:79)
ERROR: 85 RID allocations of type 'N18RendererCanvasCull4ItemE' were leaked at exit.
ERROR: 6 RID allocations of type 'N18RendererCanvasCull6CanvasE' were leaked at exit.
ERROR: 6 RID allocations of type 'N16RendererViewport8ViewportE' were leaked at exit.
ERROR: 109 RID allocations of type 'PN18TextServerAdvanced22ShapedTextDataAdvancedE' were leaked at exit.
ERROR: 1 RID allocations of type 'PN18TextServerAdvanced12FontAdvancedE' were leaked at exit.
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: cleanup (core/object/object.cpp:2208)
Leaked instance: ImageTexture:-9222718926947876424 - Resource path:
Leaked instance: ImageTexture:-9222732121087409678 - Resource path:
Leaked instance: GDScriptNativeClass:-9223071320424578568
Leaked instance: GDScriptNativeClass:-9223069121401323012
Leaked instance: ImageTexture:-9222723324994387437 - Resource path:
Leaked instance: ImageTexture:-9222710130854854040 - Resource path:
Leaked instance: StyleBoxFlat:-9222659003564162374 - Resource path:
Leaked instance: ImageTexture:-9222707931831598404 - Resource path:
Leaked instance: ImageTexture:-9222728822552526052 - Resource path:
Leaked instance: ImageTexture:-9222729922064153549 - Resource path:
Leaked instance: FontFile:-9222741466936245180 - Resource path:
Leaked instance: ImageTexture:-9222703533785086904 - Resource path:
Leaked instance: ImageTexture:-9222702434273459127 - Resource path:
Leaked instance: ImageTexture:-9222701334761831350 - Resource path:
Leaked instance: ImageTexture:-9222699135738575796 - Resource path:
Leaked instance: ImageTexture:-9222692538668809134 - Resource path:
Leaked instance: ImageTexture:-9222679344529275810 - Resource path:
Leaked instance: ImageTexture:-9222678245017648033 - Resource path:
Leaked instance: ImageTexture:-9222668349412998040 - Resource path:
Leaked instance: StyleBoxFlat:-9222658453808348047 - Resource path:
Leaked instance: StyleBoxFlat:-9222657904052534158 - Resource path:
Leaked instance: StyleBoxFlat:-9222657354296720269 - Resource path:
Leaked instance: StyleBoxFlat:-9222656804540906380 - Resource path:
Leaked instance: StyleBoxFlat:-9222656254785092491 - Resource path:
Leaked instance: StyleBoxFlat:-9222655705029278602 - Resource path:
Leaked instance: StyleBoxFlat:-9222655155273464713 - Resource path:
Leaked instance: StyleBoxFlat:-9222654605517650824 - Resource path:
Leaked instance: StyleBoxFlat:-9222654055761836935 - Resource path:
Leaked instance: StyleBoxFlat:-9222653506006023046 - Resource path:
Leaked instance: StyleBoxFlat:-9222652956250209157 - Resource path:
Leaked instance: StyleBoxFlat:-9222652406494395268 - Resource path:
Leaked instance: StyleBoxFlat:-9222651856738581379 - Resource path:
Leaked instance: StyleBoxEmpty:-9222649107959511934 - Resource path:
Leaked instance: StyleBoxFlat:-9222648558203698045 - Resource path:
Leaked instance: StyleBoxFlat:-9222648008447884156 - Resource path:
Leaked instance: ImageTexture:-9222645809424628600 - Resource path:
Leaked instance: StyleBoxFlat:-9222645259668814711 - Resource path:
Leaked instance: StyleBoxFlat:-9222644709913000822 - Resource path:
Leaked instance: StyleBoxFlat:-9222644160157186933 - Resource path:
Leaked instance: StyleBoxFlat:-9222643610401373044 - Resource path:
Leaked instance: StyleBoxFlat:-9222643060645559155 - Resource path:
Leaked instance: StyleBoxEmpty:-9222640861622303599 - Resource path:
Leaked instance: StyleBoxFlat:-9222640311866489710 - Resource path:
Leaked instance: StyleBoxFlat:-9222639762110675821 - Resource path:
Leaked instance: StyleBoxFlat:-9222638662599048043 - Resource path:
Leaked instance: StyleBoxLine:-9222637563087420265 - Resource path:
Leaked instance: StyleBoxFlat:-9222636463575792487 - Resource path:
Leaked instance: StyleBoxFlat:-9222635913819978598 - Resource path:
Leaked instance: StyleBoxFlat:-9222635364064164709 - Resource path:
Leaked instance: StyleBoxFlat:-9222634814308350820 - Resource path:
Leaked instance: StyleBoxFlat:-9222634264552536931 - Resource path:
Leaked instance: StyleBoxFlat:-9222633714796723042 - Resource path:
Leaked instance: StyleBoxEmpty:-9222633165040909153 - Resource path:
Leaked instance: StyleBoxFlat:-9222628766994398041 - Resource path:
Leaked instance: StyleBoxFlat:-9222628217238584152 - Resource path:
Leaked instance: StyleBoxFlat:-9222627667482770263 - Resource path:
Leaked instance: StyleBoxFlat:-9222627117726956374 - Resource path:
Leaked instance: StyleBoxFlat:-9222615572854864705 - Resource path:
Leaked instance: TextLine:-9177423995685773248
Leaked instance: TextLine:-9177424545441587135
Leaked instance: TextLine:-9177423445929959358
Leaked instance: TextLine:-9177422896174145469
Leaked instance: CompressedTexture2D:-9176377810371942693 - Resource path: res://addons/dialogue_nodes/icons/Play.svg
Leaked instance: GDScript:-9176371763057989923 - Resource path: res://addons/dialogue_nodes/nodes/startNode.gd
Leaked instance: GDScript:-9176349772825434398 - Resource path: res://addons/dialogue_nodes/nodes/dialogueNode.gd
Leaked instance: PackedScene:-9176344275267295517 - Resource path: res://addons/dialogue_nodes/nodes/DialogueNodeOption.tscn
Leaked instance: SceneState:-9176343725511481628
Leaked instance: GDScript:-9176339327464970520 - Resource path: res://addons/dialogue_nodes/nodes/option.gd
Leaked instance: CompressedTexture2D:-9176299745046370583 - Resource path: res://addons/dialogue_nodes/icons/DistractionFree.svg
Leaked instance: CompressedTexture2D:-9176330531371948310 - Resource path: res://addons/dialogue_nodes/icons/Filter.svg
Leaked instance: CompressedTexture2D:-9176323384546367764 - Resource path: res://addons/dialogue_nodes/icons/Reload.svg
Leaked instance: CodeHighlighter:-9176294247488231699 - Resource path: res://addons/dialogue_nodes/nodes/DialogueNode.tscn::CodeHighlighter_btpy8
Leaked instance: CompressedTexture2D:-9176306891871951122 - Resource path: res://addons/dialogue_nodes/icons/Profile.svg
Leaked instance: GDScript:-9176246968488237329 - Resource path: res://addons/dialogue_nodes/nodes/signalNode.gd
Leaked instance: GDScript:-9176234873860331783 - Resource path: res://addons/dialogue_nodes/nodes/conditionNode.gd
Leaked instance: GDScript:-9176215082651031809 - Resource path: res://addons/dialogue_nodes/nodes/setNode.gd
Leaked instance: GDScript:-9176202988023126269 - Resource path: res://addons/dialogue_nodes/nodes/commentNode.gd
Leaked instance: GraphNode:48021170343177231 - Node name: StartNode
Leaked instance: Object:48021720098991120
Leaked instance: HBoxContainer:48022269854805009 - Node name: @HBoxContainer@17870
Leaked instance: Object:48022819610618898
Leaked instance: Label:48023369366432787 - Node name: @Label@17871
Leaked instance: Object:48023919122246676
Leaked instance: HBoxContainer:48024468878060565 - Node name: HBoxContainer
Leaked instance: Object:48025018633874454
Leaked instance: Button:48025568389688343 - Node name: RunButton
Leaked instance: Object:48026118145502232
Leaked instance: TextParagraph:-9175345368953459687
Leaked instance: Label:48027217657130010 - Node name: IDLabel
Leaked instance: Object:48027767412943899
Leaked instance: LineEdit:48028317168757788 - Node name: ID
Leaked instance: Object:48028866924571677
Leaked instance: GraphNode:48029416680385566 - Node name: DialogueNode
Leaked instance: Object:48029966436199455
Leaked instance: HBoxContainer:48030516192013344 - Node name: @HBoxContainer@17872
Leaked instance: Object:48031065947827233
Leaked instance: Label:48031615703641122 - Node name: @Label@17873
Leaked instance: Object:48032165459455011
Leaked instance: Label:48032715215268900 - Node name: SpeakerLabel
Leaked instance: Object:48033264971082789
Leaked instance: HBoxContainer:48033814726896678 - Node name: HBoxContainer
Leaked instance: Object:48034364482710567
Leaked instance: LineEdit:48034914238524456 - Node name: CustomSpeaker
Leaked instance: Object:48035463994338345
Leaked instance: OptionButton:48036013750152234 - Node name: Speaker
Leaked instance: Object:48036563505966123
Leaked instance: TextParagraph:-9175334923592995796
Leaked instance: PopupMenu:48037663017593901 - Node name: @PopupMenu@17879
Leaked instance: World2D:-9175333824081368018 - Resource path:
Leaked instance: ViewportTexture:-9175333274325554129 - Resource path:
Leaked instance: Object:48039312285035568
Leaked instance: MarginContainer:48039862040849457 - Node name: @MarginContainer@17874
Leaked instance: Object:48040411796663346
Leaked instance: ScrollContainer:48040961552477235 - Node name: @ScrollContainer@17875
Leaked instance: Object:48041511308291124
Leaked instance: HScrollBar:48042061064105013 - Node name: _h_scroll
Leaked instance: Object:48042610819918902
Leaked instance: VScrollBar:48043160575732791 - Node name: _v_scroll
Leaked instance: Object:48043710331546680
Leaked instance: Control:48044260087360569 - Node name: @Control@17876
Leaked instance: Object:48044809843174458
Leaked instance: Timer:48045359598988347 - Node name: @Timer@17877
Leaked instance: Timer:48045909354802236 - Node name: @Timer@17878
Leaked instance: Button:48046459110616125 - Node name: CharacterToggle
Leaked instance: Object:48047008866430014
Leaked instance: TextParagraph:-9175324478232531905
Leaked instance: Label:48048108378057792 - Node name: DialogueLabel
Leaked instance: Object:48048658133871681
Leaked instance: HBoxContainer:48049207889685570 - Node name: HBoxContainer2
Leaked instance: Object:48049757645499459
Leaked instance: TextEdit:48050307401313348 - Node name: Dialogue
Leaked instance: Object:48050857157127237
Leaked instance: TextParagraph:-9175320629941834682
Leaked instance: TextParagraph:-9175320080186020793
Leaked instance: HScrollBar:48053056180382792 - Node name: @HScrollBar@17880
Leaked instance: Object:48053605936196681
Leaked instance: VScrollBar:48054155692010570 - Node name: @VScrollBar@17881
Leaked instance: Object:48054705447824459
Leaked instance: Timer:48055255203638348 - Node name: @Timer@17882
Leaked instance: Timer:48055804959452237 - Node name: @Timer@17883
Leaked instance: Timer:48056354715266126 - Node name: @Timer@17884
Leaked instance: Button:48056904471080015 - Node name: ExpandButton
Leaked instance: Object:48057454226893904
Leaked instance: TextParagraph:-9175314032872068015
Leaked instance: PopupPanel:48058553738521682 - Node name: DialoguePanel
Leaked instance: World2D:-9175312933360440237 - Resource path:
Leaked instance: ViewportTexture:-9175312383604626348 - Resource path:
Leaked instance: Object:48060203005963349
Leaked instance: Panel:48060752761777238 - Node name: @Panel@17885
Leaked instance: Object:48061302517591127
Leaked instance: VBoxContainer:48061852273405016 - Node name: VBoxContainer
Leaked instance: Object:48062402029218905
Leaked instance: TextEdit:48062951785032794 - Node name: DialogueExpanded
Leaked instance: Object:48063501540846683
Leaked instance: TextParagraph:-9175307985558115236
Leaked instance: TextParagraph:-9175307435802301347
Leaked instance: HScrollBar:48065700564102238 - Node name: @HScrollBar@17886
Leaked instance: Object:48066250319916127
Leaked instance: VScrollBar:48066800075730016 - Node name: @VScrollBar@17887
Leaked instance: Object:48067349831543905
Leaked instance: Timer:48067899587357794 - Node name: @Timer@17888
Leaked instance: Timer:48068449343171683 - Node name: @Timer@17889
Leaked instance: Timer:48068999098985572 - Node name: @Timer@17890
Leaked instance: CenterContainer:48069548854799461 - Node name: CenterContainer
Leaked instance: Object:48070098610613350
Leaked instance: Button:48070648366427239 - Node name: CloseButton
Leaked instance: Object:48071198122241128
Leaked instance: TextParagraph:-9175300288976720791
Leaked instance: HBoxContainer:48072297633868906 - Node name: Option1
Leaked instance: Object:48072847389682795
Leaked instance: Button:48073397145496684 - Node name: FilterButton
Leaked instance: Object:48073946901310573
Leaked instance: TextParagraph:-9175297540197651346
Leaked instance: LineEdit:48075046412938351 - Node name: LineEdit
Leaked instance: Object:48075596168752240
Leaked instance: PopupPanel:48076145924566129 - Node name: FilterPanel
Leaked instance: World2D:-9175295341174395790 - Resource path:
Leaked instance: ViewportTexture:-9175294791418581901 - Resource path:
Leaked instance: Object:48077795192007796
Leaked instance: Panel:48078344947821685 - Node name: @Panel@17891
Leaked instance: Object:48078894703635574
Leaked instance: HBoxContainer:48079444459449463 - Node name: HBoxContainer
Leaked instance: Object:48079994215263352
Leaked instance: LineEdit:48080543971077241 - Node name: Value1
Leaked instance: Object:48081093726891130
Leaked instance: OptionButton:48081643482705019 - Node name: Operator
Leaked instance: Object:48082193238518908
Leaked instance: TextParagraph:-9175289293860443011
Leaked instance: PopupMenu:48083292750146686 - Node name: @PopupMenu@17897
Leaked instance: World2D:-9175288194348815233 - Resource path:
Leaked instance: ViewportTexture:-9175287644593001344 - Resource path:
Leaked instance: Object:48084942017588353
Leaked instance: MarginContainer:48085491773402242 - Node name: @MarginContainer@17892
Leaked instance: Object:48086041529216131
Leaked instance: ScrollContainer:48086591285030020 - Node name: @ScrollContainer@17893
Leaked instance: Object:48087141040843909
Leaked instance: HScrollBar:48087690796657798 - Node name: _h_scroll
Leaked instance: Object:48088240552471687
Leaked instance: VScrollBar:48088790308285576 - Node name: _v_scroll
Leaked instance: Object:48089340064099465
Leaked instance: Control:48089889819913354 - Node name: @Control@17894
Leaked instance: Object:48090439575727243
Leaked instance: Timer:48090989331541132 - Node name: @Timer@17895
Leaked instance: Timer:48091539087355021 - Node name: @Timer@17896
Leaked instance: TextLine:-9175279948011606898
Leaked instance: TextLine:-9175279398255793009
Leaked instance: TextLine:-9175278848499979120
Leaked instance: TextLine:-9175278298744165231
Leaked instance: TextLine:-9175277748988351342
Leaked instance: TextLine:-9175277199232537453
Leaked instance: TextLine:-9175276649476723564
Leaked instance: TextLine:-9175276099720909675
Leaked instance: TextLine:-9175275549965095786
Leaked instance: TextLine:-9175275000209281897
Leaked instance: TextLine:-9175274450453468008
Leaked instance: TextLine:-9175273900697654119
Leaked instance: LineEdit:48098685912935578 - Node name: Value2
Leaked instance: Object:48099235668749467
Leaked instance: Button:48099785424563356 - Node name: ResetButton
Leaked instance: Object:48100335180377245
Leaked instance: TextParagraph:-9175271151918584674
Leaked instance: GraphNode:48101434692005023 - Node name: CommentNode
Leaked instance: Object:48101984447818912
Leaked instance: HBoxContainer:48102534203632801 - Node name: @HBoxContainer@17898
Leaked instance: Object:48103083959446690
Leaked instance: Label:48103633715260579 - Node name: @Label@17899
Leaked instance: Object:48104183471074468
Leaked instance: TextEdit:48104733226888357 - Node name: TextEdit
Leaked instance: Object:48105282982702246
Leaked instance: TextParagraph:-9175266204116259673
Leaked instance: TextParagraph:-9175265654360445784
Leaked instance: HScrollBar:48107482005957801 - Node name: @HScrollBar@17900
Leaked instance: Object:48108031761771690
Leaked instance: VScrollBar:48108581517585579 - Node name: @VScrollBar@17901
Leaked instance: Object:48109131273399468
Leaked instance: Timer:48109681029213357 - Node name: @Timer@17902
Leaked instance: Timer:48110230785027246 - Node name: @Timer@17903
Leaked instance: Timer:48110780540841135 - Node name: @Timer@17904
Leaked instance: GraphNode:48111330296655024 - Node name: SignalNode
Leaked instance: Object:48111880052468913
Leaked instance: HBoxContainer:48112429808282802 - Node name: @HBoxContainer@17905
Leaked instance: Object:48112979564096691
Leaked instance: Label:48113529319910580 - Node name: @Label@17906
Leaked instance: Object:48114079075724469
Leaked instance: LineEdit:48114628831538358 - Node name: SignalValue
Leaked instance: Object:48115178587352247
Leaked instance: GraphNode:48115728343166136 - Node name: SetNode
Leaked instance: Object:48116278098980025
Leaked instance: HBoxContainer:48116827854793914 - Node name: @HBoxContainer@17907
Leaked instance: Object:48117377610607803
Leaked instance: Label:48117927366421692 - Node name: @Label@17908
Leaked instance: Object:48118477122235581
Leaked instance: HBoxContainer:48119026878049470 - Node name: HBoxContainer
Leaked instance: Object:48119576633863359
Leaked instance: LineEdit:48120126389677248 - Node name: Variable
Leaked instance: Object:48120676145491137
Leaked instance: OptionButton:48121225901305026 - Node name: Type
Leaked instance: Object:48121775657118915
Leaked instance: TextParagraph:-9175249711441843004
Leaked instance: PopupMenu:48122875168746693 - Node name: @PopupMenu@17914
Leaked instance: World2D:-9175248611930215226 - Resource path:
Leaked instance: ViewportTexture:-9175248062174401337 - Resource path:
Leaked instance: Object:48124524436188360
Leaked instance: MarginContainer:48125074192002249 - Node name: @MarginContainer@17909
Leaked instance: Object:48125623947816138
Leaked instance: ScrollContainer:48126173703630027 - Node name: @ScrollContainer@17910
Leaked instance: Object:48126723459443916
Leaked instance: HScrollBar:48127273215257805 - Node name: _h_scroll
Leaked instance: Object:48127822971071694
Leaked instance: VScrollBar:48128372726885583 - Node name: _v_scroll
Leaked instance: Object:48128922482699472
Leaked instance: Control:48129472238513361 - Node name: @Control@17911
Leaked instance: Object:48130021994327250
Leaked instance: Timer:48130571750141139 - Node name: @Timer@17912
Leaked instance: Timer:48131121505955028 - Node name: @Timer@17913
Leaked instance: TextLine:-9175240365593006891
Leaked instance: TextLine:-9175239815837193002
Leaked instance: TextLine:-9175239266081379113
Leaked instance: TextLine:-9175238716325565224
Leaked instance: TextLine:-9175238166569751335
Leaked instance: TextLine:-9175237616813937446
Leaked instance: TextLine:-9175237067058123557
Leaked instance: TextLine:-9175236517302309668
Leaked instance: TextLine:-9175235967546495779
Leaked instance: TextLine:-9175235417790681890
Leaked instance: LineEdit:48137168819907807 - Node name: Value
Leaked instance: Object:48137718575721696
Leaked instance: GraphNode:48138268331535585 - Node name: ConditionNode
Leaked instance: Object:48138818087349474
Leaked instance: HBoxContainer:48139367843163363 - Node name: @HBoxContainer@17915
Leaked instance: Object:48139917598977252
Leaked instance: Label:48140467354791141 - Node name: @Label@17916
Leaked instance: Object:48141017110605030
Leaked instance: HBoxContainer:48141566866418919 - Node name: HBoxContainer
Leaked instance: Object:48142116622232808
Leaked instance: LineEdit:48142666378046697 - Node name: Value1
Leaked instance: Object:48143216133860586
Leaked instance: OptionButton:48143765889674475 - Node name: Operator
Leaked instance: Object:48144315645488364
Leaked instance: TextParagraph:-9175227171453473555
Leaked instance: PopupMenu:48145415157116142 - Node name: @PopupMenu@17922
Leaked instance: World2D:-9175226071941845777 - Resource path:
Leaked instance: ViewportTexture:-9175225522186031888 - Resource path:
Leaked instance: Object:48147064424557809
Leaked instance: MarginContainer:48147614180371698 - Node name: @MarginContainer@17917
Leaked instance: Object:48148163936185587
Leaked instance: ScrollContainer:48148713691999476 - Node name: @ScrollContainer@17918
Leaked instance: Object:48149263447813365
Leaked instance: HScrollBar:48149813203627254 - Node name: _h_scroll
Leaked instance: Object:48150362959441143
Leaked instance: VScrollBar:48150912715255032 - Node name: _v_scroll
Leaked instance: Object:48151462471068921
Leaked instance: Control:48152012226882810 - Node name: @Control@17919
Leaked instance: Object:48152561982696699
Leaked instance: Timer:48153111738510588 - Node name: @Timer@17920
Leaked instance: Timer:48153661494324477 - Node name: @Timer@17921
Leaked instance: TextLine:-9175217825604637442
Leaked instance: TextLine:-9175217275848823553
Leaked instance: TextLine:-9175216726093009664
Leaked instance: TextLine:-9175216176337195775
Leaked instance: TextLine:-9175215626581381886
Leaked instance: TextLine:-9175215076825567997
Leaked instance: TextLine:-9175214527069754108
Leaked instance: TextLine:-9175213977313940219
Leaked instance: TextLine:-9175213427558126330
Leaked instance: TextLine:-9175212877802312441
Leaked instance: TextLine:-9175212328046498552
Leaked instance: TextLine:-9175211778290684663
Leaked instance: LineEdit:48160808319905034 - Node name: Value2
Leaked instance: Object:48161358075718923
Leaked instance: ItemList:48161907831532812 - Node name: TrueLabel
Leaked instance: Object:48162457587346701
Leaked instance: VScrollBar:48163007343160590 - Node name: @VScrollBar@17923
Leaked instance: Object:48163557098974479
Leaked instance: TextParagraph:-9175207929999987440
Leaked instance: ItemList:48164656610602257 - Node name: FalseLabel
Leaked instance: Object:48165206366416146
Leaked instance: VScrollBar:48165756122230035 - Node name: @VScrollBar@17924
Leaked instance: Object:48166305878043924
Leaked instance: TextParagraph:-9175205181220917995
Leaked instance: ImageTexture:-9166200180989428776 - Resource path:
Leaked instance: ImageTexture:-9166201280501056549 - Resource path:
Leaked instance: ImageTexture:-9166171593687106587 - Resource path:
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with remove_child()) but not freed (with free() or queue_free()).

Are you using the addon from the godot-4.2 branch?

yes, it happens with that version too, just run the engine on verbose mode and close it.

From my testing, here's what I've found:

The memory leak issue is present in all the versions of the plugin for Godot 3.5, 4.1 & 4.2.
The issue doesn't show up in a game project. It only happens due to the dialogue editor scene.
The issue only shows up on closing Godot, never in any other circumstance.
I tried to open, close and reopen a project that uses the plugin multiple times and did not see any increase in memory usage over time.

So, its safe to assume this issue does not affect the memory while running Godot or the game project. With that out of the way, I would really like to test further and resolve this issue as soon as possible. Please expect some updates regarding this soon.

Anyway, I fixed the memory leaks for Godot 4.2 in this commit.
Also, for Godot 4.1 & Godot 3.5 all thanks to you pointing it out!
Please let me know if the issue is still present, I'll reopen this issue. Cheers!

thanks for the support! I've tested your latest commit and the issue seems to be gone!


Added ICEYE product type translation for simplicity

Created translation table, to change from our few distinctive spotlight types into something less convoluted and put the result into ModeID field.

This is a good start, but other changes will likely need to be made to get a SICD with valid metadata.
For example, current conversion of SpotlightExtendedArea SLC files result in a constant /SICD/Grid/TimeCOAPoly and report a ModeType of "SPOTLIGHT".  These should be nonconstant and "DYNAMIC STRIPMAP" respectively.

Overtaken by the merge for version 1.2.45


Unable to skip missing workers

config/initializers/paperclip_optimizer.rb

Paperclip::PaperclipOptimizer.default_options = {
  skip_missing_workers: true,
  advpng: false,
  gifsicle: false,
  jhead: false,
  jpegoptim: false,
  jpegrecompress: false,
  jpegtran: false,
  optipng: false,
  pngcrush: false,
  pngout: false,
  pngquant: false,
  svgo: false
}

Result:
=> Booting Puma
=> Rails 4.2.0 application starting in development on http://<IP_ADDRESS>:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Unknown architecture (openbsd5.7) assuming one processor.
Exiting
/usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim/worker/class_methods.rb:72:in `create_all': Bin resolving errors: (ImageOptim::BinResolver::Error)
pngout worker: `pngout` not found; please provide proper binary or disable this worker (--no-pngout argument or `:pngout => false` through options)
advpng worker: `advpng` not found; please provide proper binary or disable this worker (--no-advpng argument or `:advpng => false` through options)
pngquant worker: `pngquant` not found; please provide proper binary or disable this worker (--no-pngquant argument or `:pngquant => false` through options)
jpegoptim worker: `jpegoptim` not found; please provide proper binary or disable this worker (--no-jpegoptim argument or `:jpegoptim => false` through options)
svgo worker: `svgo` not found; please provide proper binary or disable this worker (--no-svgo argument or `:svgo => false` through options)
        from /usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim/worker/class_methods.rb:44:in `create_all_by_format'
        from /usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim.rb:77:in `initialize'
        from /usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim/railtie.rb:26:in `new'
        from /usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim/railtie.rb:26:in `register_preprocessor'
        from /usr/local/lib/ruby/gems/2.2/gems/image_optim-0.21.0/lib/image_optim/railtie.rb:7:in `block in <class:Railtie>'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/initializable.rb:30:in `instance_exec'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/initializable.rb:30:in `run'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/initializable.rb:55:in `block in run_initializers'
        from /usr/local/lib/ruby/2.2/tsort.rb:226:in `block in tsort_each'
        from /usr/local/lib/ruby/2.2/tsort.rb:348:in `block (2 levels) in each_strongly_connected_component'
        from /usr/local/lib/ruby/2.2/tsort.rb:429:in `each_strongly_connected_component_from'
        from /usr/local/lib/ruby/2.2/tsort.rb:347:in `block in each_strongly_connected_component'
        from /usr/local/lib/ruby/2.2/tsort.rb:345:in `each'
        from /usr/local/lib/ruby/2.2/tsort.rb:345:in `call'
        from /usr/local/lib/ruby/2.2/tsort.rb:345:in `each_strongly_connected_component'
        from /usr/local/lib/ruby/2.2/tsort.rb:224:in `tsort_each'
        from /usr/local/lib/ruby/2.2/tsort.rb:203:in `tsort_each'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/initializable.rb:54:in `run_initializers'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/application.rb:352:in `initialize!'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/railtie.rb:194:in `public_send'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/railtie.rb:194:in `method_missing'
        from /home/dev/myapp/config/environment.rb:5:in `<top (required)>'
        from /usr/local/lib/ruby/gems/2.2/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
        from /usr/local/lib/ruby/gems/2.2/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `block in require'
        from /usr/local/lib/ruby/gems/2.2/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:240:in `load_dependency'
        from /usr/local/lib/ruby/gems/2.2/gems/activesupport-4.2.0/lib/active_support/dependencies.rb:274:in `require'
        from /home/dev/myapp/config.ru:3:in `block in <main>'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
        from /home/dev/myapp/config.ru:in `new'
        from /home/dev/myapp/config.ru:in `<main>'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/builder.rb:49:in `eval'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/builder.rb:49:in `new_from_string'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/builder.rb:40:in `parse_file'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/server.rb:299:in `build_app_and_options_from_config'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/server.rb:208:in `app'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/server.rb:61:in `app'
        from /usr/local/lib/ruby/gems/2.2/gems/rack-1.6.4/lib/rack/server.rb:336:in `wrapped_app'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/server.rb:139:in `log_to_stdout'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/server.rb:78:in `start'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:80:in `block in server'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:75:in `tap'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:75:in `server'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
        from /usr/local/lib/ruby/gems/2.2/gems/railties-4.2.0/lib/rails/commands.rb:17:in `<top (required)>'
        from bin/rails:8:in `require'
        from bin/rails:8:in `<main>'

Wrong repo, sorry.

Though Unknown architecture (openbsd5.7) assuming one processor. should be fixed :)


node counts

is there a way to get the nodecounts for a clasp-run
instead of the seconds needed ?
just how often the  most inner loop was executed
ithat would be more useful for benchmarks, since seconds depend on
external things like
operation system
processor heat
programs running on other threads

I'm not familiar with the term node count and there are no dedicated loop counters in clasp. However, from what I understand, the number of choices (or alternatively conflicts) might come close to what you want. For this, you have to call clasp with option --stats.
Please note though that these numbers are only deterministic with one solving thread. Multi-threaded solving in clasp (option --parallel-mode,-t) is inherently non-deterministic.

yes,thanks, --stats works. I was only searching --help=3 for
keyword "node"
I'll take the maximum value, which is "Choices"
I didn't notice that clasp -t is non-deterministic
I use ./clasp4 file which calls clasp kk -t 4 on multiple
instances in file and just measures the total time needed
for all instances.
This gave strange time increases today vs. yesterday whose reason
I'm trying to figure out.
I'm currently only considering exact-cover problems.
output of clasp 3.3.5  --stat :
c Models         : 1+
c Calls          : 1
c Time           : 0.138s (Solving: 0.14s 1st Model: 0.14s Unsat: 0.00s)
c CPU Time       : 0.138s
c
c Choices        : 20196
c Conflicts      : 18230    (Analyzed: 18230)
c Restarts       : 1        (Average: 18230.00 Last: 2222)
c Model-Level    : 4.0
c Problems       : 1        (Average Length: 0.00 Splits: 0)
c Lemmas         : 18230    (Deleted: 16338)
c   Binary       : 17       (Ratio:   0.09%)
c   Ternary      : 317      (Ratio:   1.74%)
c   Conflict     : 18230    (Average Length:   19.7 Ratio: 100.00%)
c   Loop         : 0        (Average Length:    0.0 Ratio:   0.00%)
c   Other        : 0        (Average Length:    0.0 Ratio:   0.00%)
c Backjumps      : 18230    (Average:  1.11 Max:  29 Sum:  20183)
c   Executed     : 18230    (Average:  1.11 Max:  29 Sum:  20183 Ratio:
100.00%)
c   Bounded      : 0        (Average:  0.00 Max:   0 Sum:      0 Ratio:
0.00%)
c
c Variables      : 300      (Eliminated:    0 Frozen:    0)
c Constraints    : 2216     (Binary:  89.2% Ternary:   0.0% Other:
10.8%)
==========================================================
output of Kissat 3.1.0
c conflicts:                            12434            72682.00 per
second
c decisions:                            46198                3.72 per
conflict
c eliminated:                              19                6 %
variables
c propagations:                       1384073          8090493    per
second
c queue_decisions:                      39140               85 %
decision
c random_decisions:                      2266                5 %
decision
c random_sequences:                        14              888
interval
c reductions:                               7             1776
interval
c rephased:                                 4             3108
interval
c restarts:                              1768                7.03
interval
c score_decisions:                       4792               10 %
decision
c strengthened:                            90                3 %  checks
c subsumed:                                10                0 %  checks
c switched:                                 7             1776
interval
c vivified:                              1400               21 %  checks
c vivify_checks:                         6525             1631    per
vivify
c vivify_units:                             0                0 %
variables
c walk_improved:                            1              100 %  walks
c walks:                                    1            12434
interval
c
c ---- [ resources ]
c
c maximum-resident-set-size:          4915200 bytes          5 MB
c process-time:                                              0.17
seconds
==================================
output of Donald Knuth's "dancing links , dlx1.w" :
1 solution, 198026+1124421278 mems, 41732507 updates, 31952 bytes,
1976196 nodes.
Am 15.07.2024 10:15 schrieb Benjamin Kaufmann:

I'm not familiar with the term node count and there are no dedicated
loop counters in clasp. However, from what I understand, the number of
choices (or alternatively conflicts) might come close to what you
want. For this, you have to call clasp with option --stats.
Please note though that these numbers are only deterministic with one
solving thread. Multi-threaded solving in clasp (option
--parallel-mode,-t) is inherently non-deterministic.
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
@.***>
Links:
[1]
https://github.com/potassco/clasp/issues/102#issuecomment-2227933633
[2]
https://github.com/notifications/unsubscribe-auth/BCAREI7WT43MX76RDZ6NTELZMOAK3AVCNFSM6AAAAABK35AVHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXHEZTGNRTGM


Bump package.json

@theRealPadster Should we bump it before or after creating the release

@theRealPadster Should we bump it before or after creating the release

Before. I botched the release tho 🙈 we need to delete the tag and redo it


Media with this code does not exist

results has no data

InstagramScraper\Exception\InstagramException Object
(
[message:protected] => Media with this code does not exist
[string:Exception:private] =>
[code:protected] => 500
[file:protected] => /Users/max/php/instagram-php-scraper/src/InstagramScraper/Instagram.php
[line:protected] => 823
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /Users/max/php/instagram-php-scraper/examples/getMediaByUrl.php
[line] => 16
[function] => getMediaByUrl
[class] => InstagramScraper\Instagram
[type] => ->
[args] => Array
(
[0] => https://www.instagram.com/p/CX3OQ9gIXLI/
)
            )

    )

[previous:Exception:private] =>

)

Same here. I debugged the script a little bit and found out that the request for example https://www.instagram.com/p/CYnlJraMNzC/?__a=1 returns object with property "items" instead of "graphql", and the script throws exception.
The same in Postman using the header data generated from the script. Instagram returned the same object.
What can we do in this case?

did you solve this problem?

Unfortunately not yet.

Unfortunately not yet.

tell me when you solved :)


RFC: BDV Decrease

RFC: BDV Decrease
Authors
Brean, Ben Weintraub, Brendan Sanderson, Guy, deadmanwalking
Summary
Implement a new Convert type that allows any user to decrease a Deposit’s BDV if the Recorded BDV (the BDV stored on-chain with the Deposit) is greater than the Current BDV (the number of tokens in the Deposit * the current BDV of that token).
Problem:
Currently, the Recorded BDV of a given Deposit is asynchronous with its Current BDV. For example, if a user Deposits BEANETH into the Silo and the USD price of ETH falls significantly (and thus the BDV of BEANETH decreases), the Recorded BDV does not decrease, i.e., the user “locked in” the greater BDV at the time of Deposit. In practice, this may mean Beanstalk is over crediting BDV to Deposits relative to their value to the system.
Beanstalk only supports Convert types that do not decrease the BDV of the Deposit.
Solution
Implement a new Convert type ANTI_LAMBDA_LAMBDA , callable by anyone, that Converts on behalf of a user.
Context
This functionality becomes particularly impactful once Generalized Convert (https://github.com/BeanstalkFarms/Beanstalk/issues/716) is live and a stable pair (for example, BEAN:USDT) is whitelisted in the Silo. For example, if a Depositor “locks in” a high Recorded BDV in a BEANETH Deposit and the USD price of ETH begins dropping, they should be compelled to consider that if they don’t Convert out of BEANETH, their BDV may decrease. This is not something that any Depositor in the system currently has to consider — they’ll be credited with the BDV (and thus, base Stalk) they “locked in”, regardless of how the BDV of the underlying tokens change.
Specification
ConvertFacet.sol

Add an additional parameter account in LibConvert.convert(…).
To conform with previous convertData types, have them return 0, and have a check that uses msg.sender instead of address.
Replace msg.sender in other places with account.

Note: This is additionally developed with the Tractor specification in mind; if this is developed after Tractor, we can replace msg.sender with the input parameter of _convert.

Add to the return parameters a boolean representing whether the Convert type should decrease BDV or not.

Example Implementation
....
address toToken; address fromToken;
uint256 grownStalk; address account;
(toToken, fromToken, toAmount, fromAmount, account, decreaseBDV) = LibConvert.convert(
            convertData
        );
...
if(account == address(0)) account = msg.sender;
LibSilo._mow(account, fromToken);
LibSilo._mow(account, toToken);
...
uint256 newBdv = LibTokenSilo.beanDenominatedValue(toToken, toAmount);
if(decreaseBDV) {
	toBdv = newBdv;
} else {
	toBdv = newBdv > fromBdv ? newBdv : fromBdv;
}

Libraries

Add a new Convert type ANTI_LAMBDA_LAMBDA in LibConvertData.sol.
Add ANTI_LAMBDA_LAMBDA check in LibConvert.sol.
Update return parameters to return account.

For non ANTI_LAMBDA_LAMBDA converts, return 0.
the ANTI_LAMBDA_LAMBDA convert can use the same library/function as LibLamddaConvert.sol.

Add to the return parameter a boolean representing whether the Convert type should decrease BDV or not:

Example Implementation
// LibConvert:
...
} else if (kind == LibConvertData.ConvertKind.UNRIPE_TO_RIPE) {
	(tokenOut, tokenIn, amountOut, amountIn) = LibChopConvert
    .convertUnripeToRipe(convertData);
	// DecreaseBDV = false;
	// account = address(0);
// new code
} else if (kind == LibConvertData.ConvertKind.ANTI_LAMDA_LAMDA) {
	(tokenOut, tokenIn, amountOut, amountIn, account) = LibLambdaConvert
    .convert(convertData);
	DecreaseBDV = true;
} else {
	revert("Convert: Invalid payload");
}

Note: the boolean DecreaseBDV and address account are initialized to 0, and thus previous Convert types do not need to be updated.

https://github.com/BeanstalkFarms/Beanstalk/pull/802 addresses this issue.


Fix "Prefer format() over string interpolation operator" issue

This pull request automatically fixes all occurrences of the following issue:
Issue type: Prefer format() over string interpolation operator
Issue details: https://www.quantifiedcode.com/app/project/gh:SpriteLink:NIPAP?groups=code_patterns/%3A4ACGxFj1
To adjust the commit message or the actual code changes, just rebase or cherry-pick the commits.
For questions or feedback reach out to<EMAIL_ADDRESS>Legal note: We won't claim any copyrights on the code changes.
Cheers,
Cody - Your code quality bot

I mostly wanted to test what happened when I pressed the "fix this" button in QuantifiedCode. I think this PR is too large to merge in one go. All the changes are to log lines which aren't really covered by CI so we can't trust CI result that this is correct. Does QuantifiedCode do all the conversions correctly? I'll close this. Think we should take it in smaller chunks.


[API Management] Fix apim's apply-network-updates command

Description

apply_network_configuration_updates function has been renamed to begin_apply_network_configuration_updates
Testing Guide

Create an APIM instance
az apim apply-network-updates --name {servicename} --resource-group {rg} --subscription {sub} --location {location}
Ensure that it passed successfully

History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

[X] I adhere to the Error Handling Guidelines.

API Management


Non standart Assignment relation looking

Does it possible to make Assignment relation looking closer to Archimate Standart - with black and smaller circle at starting end ?
Archimate PlantUML looking

Archimate Standart looking

It looks like this is caused by using 0-->> as arrow notation, which gives  an open circle.
If it is replaced with @-->>, we get the desired result.
I've opened #35 to resolve this.


document xhr option

Adds a mention of the xhr option to the readme. Otherwise it seems like a private / not-intended-for-public-consumption option.

lgtm.


Export the javascript regexes

Overview
Oops. Need to add javascript.js to index.js.
Deliverables

[x] do it

Work for this issue will begin begin on branch work-liquid-labs/regex-repo/31.


Scroll to history on log panel

It could be a 'nice to see' enhancement. I wish I could scroll on log screen for the past logs.

Oh no, is that not possible?

+1

A quick workaround is to use the blessed.list in place of the log component. Replace thelog with blessed.list. And replace log.log with log.pushItem

Just found a working solution:
(I use the log widget in a grid layout.)
var log = grid.set(16.8, 0, 4.8, 20, contrib.log,
          { fg: "green"
          , selectedFg: "green"
          , height: "70%"
          , label: 'Log'
// following properties of "option" are necessary:
          , mouse: true
//          , keys: true
          , bufferLength: 90
          , scrollbar: {
              ch: ' '
            , inverse: true
          }
        });
// finally, this really enables scrolling of log!!
log.interactive = true;

log.interactive is set to false by default, that's why scrolling is that tricky to enable.
bufferLength is set to 30 by default, so you might want to increase this.
There are seems to be a funktion that provides a way to set a line of the buffer to scroll to (which by default is set to scroll to the end of the log each time a new line is added):
this.scrollTo(this.logLines.length);
...so, I think this issue might be solved/closed, can you please verify?


Increase OCP ClusterNetwork cidr range

For installing OCP clusters with large number of worker nodes, the CIDR range for the cluster network has to be changed from /14 to /13.

LGTM


can't resolve module in webpack 2.6.0

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
my webpack.config.js
var path = require('path');
var webpack = require('webpack');

const srcPath = path.resolve(__dirname, '../src');
const rootPath = path.resolve(__dirname, '../');

module.exports = {
    entry: ['./src/index.js'],
    output: {
        path: path.resolve(__dirname, 'dist'),
        publicPath: '/',
        filename: 'bundle.js'
    },
    module: {
        rules: [{
            enforce: 'pre',
            test: /\.(js|jsx)$/,
            exclude: /node_modules/,
            use: ['babel-loader', 'eslint-loader']
        }, {
            test: /\.css$/,
            use: [
                'style-loader',
                'css-loader'
            ]
        }, {
            test: /\.(js|jsx)$/,
            exclude: /node_modules/,
            use: [
                'babel-loader'
            ],
            include: __dirname + '/src/'
        }, {
            test: /\.(png|jpg)$/,
            exclude: /node_modules/,
            use: 'file'
        }]
    },
    resolve: {
        modules: [`${rootPath}/src`, 'node_modules'],
        mainFields: ['browser', 'module', 'main'],
        extensions: [' ', '.js', '.jsx'],
        alias: {
            boxes: `${srcPath}/boxes'`,
            buss: `${srcPath}/buss'`,
            styles: `${srcPath}/styles'`,
            utils: `${srcPath}/utils'`
        }
    },
    plugins: [
        new webpack.DefinePlugin({
            'process.env.NODE_ENV': JSON.stringify('dev'),
            '__ENV__': JSON.stringify('dev')
        }),
        new webpack.NoEmitOnErrorsPlugin(),
        new webpack.HotModuleReplacementPlugin(), // Enable HMR
        new webpack.LoaderOptionsPlugin({
            minimize: true
        })
    ]
};

my package.json
{
  "name": "react-demo-manual",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node tools/start.js"
  },
  "author": "wupeng",
  "license": "ISC",
  "devDependencies": {
    "babel-cli": "^6.24.1",
    "babel-core": "^6.25.0",
    "babel-eslint": "^7.2.3",
    "babel-loader": "^7.0.0",
    "babel-plugin-transform-object-rest-spread": "^6.23.0",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-preset-env": "^1.5.2",
    "babel-preset-es2015": "^6.24.1",
    "babel-preset-react": "^6.24.1",
    "css-loader": "^0.28.4",
    "eslint": "^4.0.0",
    "eslint-loader": "^1.8.0",
    "eslint-plugin-react": "^7.1.0",
    "file-loader": "^0.11.2",
    "opn": "^5.1.0",
    "style-loader": "^0.18.2",
    "webpack": "2.6.0",
    "webpack-dev-server": "^2.4.5"
  },
  "dependencies": {
    "babel-polyfill": "^6.23.0",
    "babel-runtime": "^6.23.0",
    "lodash": "^4.17.4",
    "react": "^15.6.1",
    "react-dom": "^15.6.1",
    "react-redux": "^5.0.5",
    "react-router": "^4.1.1",
    "react-router-loader": "^0.5.4",
    "redux": "^3.7.0",
    "redux-thunk": "^2.2.0",
    "superagent": "^3.5.2"
  }
}

and I belive my config is correct, I think it's a bug in version 2.6.0
when I require my sub component in router, I got the error Module not found

the config didn't work, because it's in windows. Path notation in windows and mac is different


cuda 10.x support

Is cuda 10.x support feasible or planned?

Unfortunately, no.    cuCIM depends on 11.X features -- @gigony is the best person to explain where those features are used.

Hi @chrisroat,
To support GDS feature in cuCIM, CUDA version >= 11.x is needed (though we currently disabled GDS feature for now and would enable it again in the future) and we currently release conda packages with CUDA 11.x only
However, since cuCIM's IO package (cucim.CuImage/ cucim.clara.xxx) works independently with cuCIM's CuPy-based scikit-image API (cucim.skimage), I think you can install and use only cucim.skimage (previously https://github.com/mritools/cupyimg ) package through the following command using pip:
# Replace cupy-cuda10X with corresponding version name such as `cupy-cuda102` available from https://cupy.dev/
pip install --upgrade scipy scikit-image cupy-cuda10X cucim

Please help let us know your use cases with cuCIM!

Thanks!  The github README.md explicitly indicates cuda 11 is needed.  I have another package stuck on cuda 10 for the near future, so want to stick with 10 for a while.   I did a small test with your cuda 10 suggestion with cucim, and things seem fine.  I will try some larger tests in our full stack before we make the full switch from cupyimg (which we currently use) to cucim.
Our use case is GPU-accelerated skimage rigid registration of neuroscience image processing.   The rest of our cupyimg use is in scipy, which seems to be absorbed into mainline cupy.  We also have some other existing cupy based routines, as well.
I will close this because you've provided a lot of helpful information and I should be good to go.

Hi @chrisroat
I forgot and ignored the fact that cucim/__init__.py would be also imported as well as cucim/skimage/__init__.py when executing import cucim.skimage.
Yes, the current version always import cucim.clara package so it has dependencies to CUDA 11.+.
I am sorry for the confusion.
Let me push a pre-release version of the PyPI package soon that removes the dependency so that you can use it for now.
And, in the next release, I would make sure that it doesn't depend on CUDA 11.x+ when only cucim.skimage package is needed.

Yes, I have run both our unit tests and deployed it on our Docker images.  Both are doing great!
Much appreciated!


Soleil disabled in Regent tests

Soleil has been disabled in Regent tests since 283337ab55e77b1b26a203ea1d1e8db33cb2e5f9. I attempted to turn it back on in 1f85f16506c0aa99b57a232d26a5a189574d5b85, but had to revert it in 933756089a887a38042e460663cdc13ff232413b.
Soleil is failing to build right now so we should really make sure it gets tested.

I turned this back on in c2bac84a6db4400d354a0bf41e78a69bf8c227ea, and it works now.


Add test case for append option without compression

See #3569.

Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
Docs Changes:
Release Note:

As described in #3569 and https://bugs.ruby-lang.org/issues/18388, Ruby 2.7 and 3.0 on macOS have the issue.
Our CI with this test expectedly indicates it.
https://github.com/fluent/fluentd/runs/4602455215?check_suite_focus=true
Failure: test: append without compression(FileOutputTest)
/Users/runner/work/fluentd/fluentd/test/plugin/test_out_file.rb:440:in `check_result'
/Users/runner/work/fluentd/fluentd/test/plugin/test_out_file.rb:415:in `block in check_events_append'
/Users/runner/work/fluentd/fluentd/test/plugin/test_out_file.rb:408:in `upto'
/Users/runner/work/fluentd/fluentd/test/plugin/test_out_file.rb:408:in `check_events_append'
/Users/runner/work/fluentd/fluentd/test/plugin/test_out_file.rb:589:in `block in <class:FileOutputTest>'
     586:   end
     587:
     588:   test 'append without compression' do
  => 589:     check_events_append(false)
     590:   end
     591:
     592:   test 'append when JST' do
<"2011-01-02T13:14:15Z\ttest\t{\"a\":1}\n" +
"2011-01-02T13:14:15Z\ttest\t{\"a\":2}\n" +
"2011-01-02T13:14:15Z\ttest\t{\"a\":1}\n" +
"2011-01-02T13:14:15Z\ttest\t{\"a\":2}\n">(UTF-8) expected but was
<"2011-01-02T13:14:15Z\ttest\t{\"a\":1}\n" +
"2011-01-02T13:14:15Z\ttest\t{\"a\":2}\n">(ASCII-8BIT)

diff:
- 2011-01-02T13:14:15Z	test	{"a":1}
- 2011-01-02T13:14:15Z	test	{"a":2}
  2011-01-02T13:14:15Z	test	{"a":1}
  2011-01-02T13:14:15Z	test	{"a":2}

? Encoding: UTF  -8
?           ASCII  BIT
?           ???  +++

I removed check_events_append method, use data driven test instead to make easy to read.

The test should be merged with #3579, so I close this one.
Thanks for your contribution!


Can't start bot

Please tick all applicable boxes.

[x] I am using Python 3.5 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[x] The latest master version (1.9.8)
[ ] The latest review version

What type of issue are you creating?

[x] Bug
[ ] Feature request
[ ] Question

Description of issue
I use the bot on raspberry pi for a while and it worked ok. But i updated the bot because of some bugs (disconnecting and reconnecting all the time).
So i make it to autorun just running "/home/pi/MusicBot/run.sh" on "/etc/rc.local" and it was fine.
And now v1.9.8_2 it doesn't work because:  (((comando não encontrado = command not found)))

~ $ /home/pi/MusicBot/run.sh
/home/pi/MusicBot/run.sh: linha 7: python3.6: comando não encontrado
/home/pi/MusicBot/run.sh: linha 8: python3.7: comando não encontrado
python3: can't open file '/run.py': [Errno 2] No such file or directory

And when i do:

~ $ cd MusicBot/
~ $ ./run.sh

it works.
I just reinstall it to make sure it was all ok. But i think it is something of the recent update.
Steps to reproduce

/home/pi/MusicBot/run.sh

Log file
Log of the step i said it works.

I tried to change the file "run.sh" like this

.14: pyhon "run.py" to "/home/pi/MusicBot/run.py"

so it returns:

[INFO] launcher: Starting sanity checks
[INFO] launcher: Checking for Python 3.5+
[INFO] launcher: Checking console encoding
[INFO] launcher: Ensuring we're in the right environment
[CRITICAL] launcher: Bot wasn't installed using Git. Reinstall using http://bit.ly/musicbotdocs.
Press enter to continue . . .

I tried to run on terminal:

~ $ python3 /home/pi/MusicBot/run.py

it returns the same:

[INFO] launcher: Starting sanity checks
[INFO] launcher: Checking for Python 3.5+
[INFO] launcher: Checking console encoding
[INFO] launcher: Ensuring we're in the right environment
[CRITICAL] launcher: Bot wasn't installed using Git. Reinstall using http://bit.ly/musicbotdocs.
Press enter to continue . . .

As stated by the output please reinstall using git

@AutumnClove it works when he/she is in the musicbot directory so that's not the case
About the initial issue: My guess is that it's because bash's working directory is wherever you invoke bash, so it can't find the run.py
But according to the guide you're supposed to run it in the musicbot directory (does earlier version really work without requiring you to be in the directory? weird)

Well after a long time looking to a script to add on /etc/init.d and it doesn't work. I just back to run.sh file and add a simple line on it.

cd /home/pi/MusicBot/

The bot back to autorun with no problems. Thanks for trying to help me.
Anyone who have doubts of how autorun it on raspberry is just edit the file run.

PYTHON37_VERSION=python3.7 -c 'import sys; version=sys.version_info[:3]; print({0}".format(version[1]))' || { echo "no py37"; }
cd /home/pi/MusicBot
if [ "${python[0]}" -eq "3" ]; then # Python = 3

And on /etc/rc.local add on the last line the directory of the run.sh file like this:

"/home/pi/MusicBot/run.sh"(in my case).

Thanks.


Bring over nfoWare Toolcraft Job Jar

Salvage the Diary & Job Jar nfoWare tools/t000000.htm for nfoTools/docs/tools/t000000.md
Update status and completions.

One clean-up pass completed.  It is a bit messy with tables in Markdown.  I need to open the web page to see what I want to manipulate.


Shortcut to keep opened tab fixed

Issue Type: Feature Request
Actual behavior
I can search and open a file with shortcuts, but if I keep opened the file tab unfixed - without clicking over it with the mouse -  and open another file with shortcuts too, than first opened file fades away and the last takes its place.
Desire behavior
Keep first opened file and fixed with a shortcut for open next file on another tab. For dont use the mouse.
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:27:31.086Z)
OS version: Linux x64 4.9.0-9-amd64

The command is: workbench.action.keepEditor

I have been imagined opening file editor and keeping it unfixed until I want, but I'm doubt about if it's usual. I'll use this settings for now, I think it can solve my "problem". Thanks @bpasero


add a collection modelIdAttribute

Define an optional modelIdAttribute for collections. If present it is used as the key by which models are uniquely identified in a collection. Useful for when using a model factory.

Or, modelIdAttribute could be defined like:
// Returns the key by which the model is uniquely
// identified in the colleciton.
modelIdAttribute: function(attrs) {
  return this.model.prototype.idAttribute || defaultIdAttribute;
}

and modelId like:
// Returns the value by which the model is uniquely
// identified in the colleciton.
modelId: function(attrs) {
  return attrs[_.result(this, 'modelIdAttribute')];
}

I'm not sure this really gives us anything over providing a #modelId, e.g. https://github.com/jashkenas/backbone/issues/3760 is still a problem.

Correct, its intent was an easier api for collections with polymorhpic models by exposing the key the collection uses to uniquely identify models. As it is now, one must override the function to change a key.

As it is now, one must override the function to change a key.

But your suggested changes use methods, and now we have two where just one will do. I'd love to simplify the uniqueness issues with a collection, but I don't think this is the right way.

Hm, I'm fine with that. I guess I don't see the reason not to offer more hooks than less :P Thanks for your feedback!


SetupExtensionsBuilderExtensions.RegisterLayoutRenderer supports LayoutRenderOptions

Closing and reopening to trigger rebuild.

Close and reopen one more time, because I feel lucky

Close and reopen one more time, because I still feel lucky

Green on Travis :)

Thanks!


ci: Split docs building from linting

This lays the groundwork for automatically uploading documentation when a release is cut.
Signed-off-by: Matt Wozniski<EMAIL_ADDRESS>

This gets us 80% of the way there. On top of this, we should have an action that fires only when releases are published that publishes the github-pages artifact to the gh-pages branch using actions/pages-deploy - but I'm not sure how to test that right now, given that what's on main contains some staged documentation changes for the next release that we're not yet ready to publish.

@godlygeek do you want to merge this PR as it is and work on the automation as a separate one?


Files for 1.15.11 and 1.16.0 are incomplete on dl.gitea.io

Gitea Version
1.15.11, 1.16.0
Git Version
No response
Operating System
Linux-amd64
How are you running Gitea?
linux-amd64 binary with systemd
Database
No response
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Description
1.16.0 is missing more files than 1.15.11, but in both cases the linux-amd64 binary is absent.
First I thought that the upload might not be finished because it had just been released, but that was hours ago, so apparently something went wrong.
Screenshots

Unfortunately we're having some trouble uploading the assets to dl.gitea.io

您好, 请问当前有可用的版本是多少？我是
OS: Linux
Arch: amd64
May I ask what version is currently available?

It is possible to also upload binaries to github releases?
https://github.com/go-gitea/gitea/releases/tag/v1.16.0 contains only source code tarballs.

Meanwhile, linux-amd64 is there, but the signature does not verify:
$ gpgv gitea-1.16.0-linux-amd64.asc gitea-1.16.0-linux-amd64
gpgv: Signature made Sun 30 Jan 2022 19:58:00 CET
gpgv:                using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpgv: BAD signature from "Teabot<EMAIL_ADDRESS>
Is that expected/related?

Meanwhile, linux-amd64 is there, but the signature does not verify:

It's not; only the signatures are there.

Meanwhile, linux-amd64 is there, but the signature does not verify:

It's not; only the signatures are there.

Funny. It's there for me. Uploaded 01/31/2022 02:27:45 AM +00:00, SHA1 a200cb8f6daa3e0a44a28a46d80ac89d56f2cb60.

I see it too. Maybe he meant 1.15.11.

I'm missing:
gitea-1.15.11-linux-amd64

I can confirm that 1.16.0 is there for Linux 64-bit, but the signature verification fails.
Also tried downloading 1.15.11 for Linux 64-bit, but the binary file is not there, so I'm trying 1.15.10 instead.
Downloading seems to take forever: 1.16.0 took about 16.5 minutes, and 1.15.10 took almost 18 minutes.

Where is the public GPG key to verify the signatures with ?

1.16.0 is there fully now. Note, some checksums may have changed due to timestamps on files in bindata, and I'm working on 1.15.11 now, if anyone wants to follow along here: https://drone.gitea.io/go-gitea/gitea/50157

the 1.15.11 files are uploading now. apologies for delay. please direct all the blame at the infrastructure team (spider man meme of @techknowlogick pointing at another @techknowlogick)


Allow list-initialization of registers and address spaces.

@AtomCrafty I'm proposing this to restore the ability to write down constant registers:
const register unsigned<4> BAR[3] = {1,2,3};

Is the approach ok or is there a smarter way in Xtend?


Endpoint registry cosmetic

After https://github.com/raiden-network/raiden-contracts/pull/217 there are some mostly cosmetic changes I would like to do to the EndpointRegistry:

Reword some comments a bit
Remove the [at]dev natspec as it's not needed and it was just a copy of [at]notice
Be consistent in the naming. We were using both socket and endpoint to refer to the same thing. A TCP socket is one type of endpoint, but since it's an endpoint registry I think using that term everywhere is better.

https://github.com/raiden-network/raiden-contracts/blob/f5e106591c7738f70e14e4975b109fd0825d5816/raiden_contracts/utils/events.py#L22-L26 also needs changing

Opsity ops. Will do so right now @loredanacirstea


[Re-merge] Support available((swift_attr("@Sendable")))

Attempting to merge #40170 again with a fix for the Windows build issue after it was reverted by #40262.

This PR implements most of the sendability auditing support for ClangImporter. Specifically:

__attribute__((swift_attr("@Sendable"))) is now allowed on Clang decls, even when it would not be allowed on equivalent Swift decls.
A Clang type declaration is imported with a synthesized @unchecked Sendable conformance if it:

Has @Sendable, but not plain @_nonSendable.
Has the enum_extensibility, flag_enum, swift_newtype, or swift_wrapper Clang attributes, but not plain @_nonSendable.
Has the ns_error_domain Clang attribute, regardless of the presence of plain @_nonSendable. (Error is always Sendable, so error codes must also be Sendable.)

We now force implicit Sendable conformances before printing the contents of a module, and we print the extensions generated by @_nonSendable even if we would normally skip unavailable or implicit extensions.
When ClangImporter is using a clang that supports https://reviews.llvm.org/D112773 (see apple/llvm-project#3547), it will define __SWIFT_ATTR_SUPPORTS_SENDABLE_DECLS to be 1.

It includes a number of related refactorings:

SynthesizedProtocolAttrs can now create @unchecked conformances.
SynthesizedFileUnits can now be attached to any FileUnit, not just SourceFile.
ClangImporter::Implementation::diagnose() has been overloaded so that, if a HeaderLoc (wrapping a clang::SourceLocation and related info) is passed in place of a SourceLoc, it will emit a diagnostic in the header file. This replaces several lines of boilerplate per use site.

Fixes rdar://84431708. It does not implement two things that I will defer to 85569247:

@_nonSendable in parameter position.
Implicit @Sendable (probably @_unsafeSendable in practice) on completion handler parameters.

Some tests will not pass without https://reviews.llvm.org/D112773, which I am in the process of cherry-picking to our clang branches.
This should only cause language behavior changes if you consume headers that include the currently-invalid __attribute__((swift_attr("@Sendable"))), __attribute__((swift_attr("@_nonSendable"))), or  __attribute__((swift_attr("@_nonSendable(_assumed)"))) attributes.

@swift-ci please smoke test Windows platform

@swift-ci smoke test


Navigable path from attendee table to Stripe/Dwolla transaction

Most organizers think in terms of attendees, so it's critical to be able to match attendees with their related financial transactions (even though on the database end we have a couple intermediary models). Here's one real-world use-case (names changed):
Mildred Hopkins accidentally orders two passes when she only means to order one. The Organizer would like to refund one of these passes. Because Dancerfly only supports complete refunds on transactions and this is a partial refund, it will need to be done through Stripe. The Organizer should be able to search the attendee table for Mildred by name and navigate from there to the stripe transaction.
Currently this involves writing down the order code from the attendee table and manually cross-referencing it to the Finances table. Not ideal.

Essentially this would mean linking from the Transactions in the Order detail page to their stripe / dwolla equivalents. That's where I'd want to start with this ticket.


Possibility to add onBundle callback?

Hi! This is just an issue to get your opinion on adding a new onBundle callback as part of the options object, similar to onDereference. I'm willing to contribute this, if you're open to adding this feature. Here's some context on why we need it:
We use json-schema-ref-parser to parse and bundle OpenAPI and AsyncAPI files, heavily relying on overriding the resolvers to fetch external references from GitHub.
One issue with that is: if external $ref contains $schema and $id - the bundle() function keeps them, but the resulting OpenAPI document fails validation, due to unexpected additional properties. Here's a concrete minimal example:
schema.json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "someId",
  "type": "object",
  "properties": {
    "exampleProperty": {
      "description": "Lorem ipsum and so on",
      "type": "boolean"
    }
  }
}

api.yaml
openapi: "3.0.3"
info:
  title: Example API
  version: "1.0"
servers:
  - url: https://localhost:3000/v1
paths:
  /example:
    get:
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: 'schema.json'

script.ts
import fs from 'node:fs/promises';
import $RefParser from '@apidevtools/json-schema-ref-parser';
import swaggerParser from '@apidevtools/swagger-parser';
import yaml from 'yaml';

const body = await fs.readFile('api.yaml', 'utf8');
const content = yaml.parse(body);
const result = await $RefParser.bundle(content, { resolve: { external: true } });
await fs.writeFile('bundledApi.yaml', yaml.stringify(result));
await swaggerParser.validate(result);

bundledApi.yaml
openapi: 3.0.3
info:
  title: Example API
  version: "1.0"
servers:
  - url: https://localhost:3000/v1
paths:
  /example:
    get:
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                $schema: http://json-schema.org/draft-07/schema#
                $id: someId
                type: object
                properties:
                  exampleProperty:
                    description: Lorem ipsum and so on
                    type: boolean

This fails validation with:
SyntaxError: Swagger schema validation failed.
  #/paths/~1example/get/responses/200/content/application~1json/schema must NOT have additional properties
  #/paths/~1example/get/responses/200/content/application~1json/schema must NOT have additional properties
  #/paths/~1example/get/responses/200/content/application~1json/schema must have required property '$ref'
  #/paths/~1example/get/responses/200/content/application~1json/schema must match exactly one schema in oneOf
  #/paths/~1example/get/responses/200 must have required property '$ref'
  #/paths/~1example/get/responses/200 must match exactly one schema in oneOf

Removing $schema and $id would make it pass the validation, however there doesn't seem to be an easy way of doing that. If we were calling dereference() instead of bundle() - the problem would be trivially solved with something like this:
const result = await $RefParser.dereference(content, {
  resolve: { external: true },
  dereference: {
    onDereference: (path: string, value: JSONSchemaObject) => {
      if ('$schema' in value) {
        delete value.$schema;
      }
    },
  },
});

Do you think adding the possibility to pass in an onBundle callback would make sense here? Or can our problem be solved in some other way? Appreciate any feedback.

That sounds reasonable, we'd add the feature if you make a PR


Add a symlink to log file

This change creates a symlink to log file, the symlink is valid while the job is in progress, and will be removed when the job completes.

is this trying to resolve logs sometimes not ending in .log?

Yes, we'll always have a .log file pointing to current log file. So if program crashes (which we ideally dont want to), we still have a log file at the path we display. Kind of similar to syslog

Closing this, as Vikas suggested a better way.


Null domain_id column for EnumerationValues in the breadcrumb_tree table

The breadcrumb_tree table's domain_id column is null for EV data,
the grails 5 migration will fix it but we need to resolve it, or at least work out if this is still a present issue or something historic

not sure what the root cause of this is, ive tested the basic api endpoints and the domain id is being set. This is therefore probably a legacy issue so closing


Observations

Hey Adam! Been looking a bit through the code and I thought to take note of some things that called out to me.
Documentation
EuroPi struct needs better naming or documentation. I'd guess K1 and K2 are the knobs, but it is hard to be sure. Adding a comment or changing them to Knob1 and Knob2 would be pretty good (I'd opt for the second since it would make comments superfluous, which is an especially good thing!). Same goes for NewAI and NewDI functions, their naming seems evil to me hahah :upside_down_face:
API
I feel like you should be making better use of the tinygo drivers package and it's interfaces. A lot of stuff here has wrappers that feel superfluous to me. An example is the Display. Instead of having a *Display in the EuroPi struct could you not use a drivers.Displayer and have the font stored in the EuroPi struct too if needed?
I also feel like the DigitalReader could be a struct instead of an interface. Though this would prevent mocking (never mocked tinygo programs myself though).
After some thinking... Shouldn't all of Europi's fields be non-interface types? What exactly is the advantage of having them as interface types? Seems to me they should be at most structs that embed interfaces which implement the IO functionality.
Heap
yep, I think strconv.Itoa is causing those awful heap alloc. Instead I'd have a static byte array of the size of the display and use the strconv.AppendInt function to avoid heap allocations altogether.
type display struct {
     // ...
     buf [16]byte
}
// ...
n := copy(disp.buf[:],  "my knob is at ")
strconv.AppendInt(a[:n:16], number, 10) // if append exceeds capacity then you have a problem

Thank you so much for all of these thoughtful comments! I'm digging to each up them and slowly making the changes. I'll report back with any findings on the heap allocation performance improvements as I go.

EuroPi struct needs better naming or documentation

Agreed! I have added docstrings to each of the peripheral/component singletons. The terse naming is a carryover from the official repo (which has better documentation). I wanted to keep the naming conventions the same for naming parity, though I am considering changing to your suggesting since this is a completely separate repo and a fresh start.

Instead of having a *Display in the EuroPi struct could you not use a drivers.Displayer

This was an ah-ha moment for me, since tinydraw accepts a device.Displayer, then that would have been the correct interface to use! I did end up removing the EuroPi struct in favor of peripheral/component singletons, so I'm not using that interface at the moment.

Shouldn't all of Europi's fields be non-interface types? What exactly is the advantage of having them as interface types?

Yeah, my original intention was to make it easy to fake out parts of the EuroPi struct for testing. The interfaces aren't really doing anything for me now, so I'll remove them and only add them back if I truly need them.

Seems to me they should be at most structs that embed interfaces which implement the IO functionality.

This is a really good observation. Early on I was exploring using composition like this but I never got around to implementing it.

Seems to me they should be at most structs that embed interfaces which implement the IO functionality.

This is a really good observation. Early on I was exploring using composition like this but I never got around to implementing it.

I ended up implementing this for the DigitalReader and it makes so much more sense! Thanks for the nudge. Unfortunately the hardware implementations for Analog Input and Knob are different enough that they need separate implementations.
I'm applying my changes in my existing Singleton refactor branch: https://github.com/awonak/EuroPiGo/pull/3

Yeah, my original intention was to make it easy to fake out parts of the EuroPi struct for testing. The interfaces aren't really doing anything for me now, so I'll remove them and only add them back if I truly need them.

If you do this remember to keep fields unexported so that if you change them back to a interface they don't break programs!
I'll look at your PR #3 now


forge flatten : Failed to flatten: missing field block

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (b174c3a 2024-02-09T00:16:22.953958126Z)
What command(s) is the bug in?
forge flatten
Operating System
Linux
Describe the bug
UUPS Contract Implementations are not getting flattened, only the proxy contracts and other specified contracts are getting flattened
errors are showing:
Failed to flatten: missing field block at line 1 column 194281
Failed to flatten: missing field block at line 1 column 492135
when it's the implementation's turn to be flattened

tried it on WSL

and on Ubuntu server

forge 0.2.0 (b174c3a 2024-02-09T00:16:22.953958126Z)
ending up with the same result

hey @Metaxona thank you for the report! any chance you could share a repro for this?
If the code being flattened contains do-while blocks than I probably know what might be causing this, but otherwise a repro would be very useful here

hey @Metaxona thank you for the report! any chance you could share a repro for this?
If the code being flattened contains do-while blocks than I probably know what might be causing this, but otherwise a repro would be very useful here

yeah it does indeed contain a do while loop, several of them. though I am currently not able to share the repo since it's a private and not a personal repo
but i did use do while loops in-place of all or most for loop applications


Add streaming API

Fixes #4.

i think this is an improvement api wise, but doesn't fix the problem where an archive is very very big, it still all has to fit into memory

Not super familiar with how the internals of streams works outside of the API, but wouldn't this work:
const extract = decompressTarbz2()(fs.createReadStream('archive.tar.bz2'));

extract.on('entry', (header, stream) => {
	stream.pipe(fs.createWriteStream(header.name));
});

extract.on('end', () => {
	console.log('done');
});

yeah that looks like it would work :)

Good :). I'm going to add that logic to decompress too so you would be able to supply a stream there and it'll do the writing for you (keeping the stats etc too).


Consider rewriting histories of exercises

So that the networks match the lesson material after the current exercise changes are merged. Now they are getting more commits. Perhaps it's a non-issue. But just so I don't forget to think about it.

Yes, it diverged too much - adjusting histories ...

[x] centralized
[ ] forking

The forking one is not a problem if the network does not match exactly. Closing.


Implementing custom templates tags

The branch created for purpose of implementing custom templates tags .

Got this error when starting new project:-
gitpod /workspace $ cookiecutter labzero/
project_name [myapp]:
project_author_name [My Name]:
project_author_email<EMAIL_ADDRESS>
project_version [0.0.0]:
project_description [Some description]:
project_slug [myapp]:
Traceback (most recent call last):
  File "/home/gitpod/.local/bin/cookiecutter", line 8, in <module>
    sys.exit(main())
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/cli.py", line 194, in main
    cookiecutter(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/main.py", line 114, in cookiecutter
    result = generate_files(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/generate.py", line 373, in generate_files
    generate_file(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/generate.py", line 173, in generate_file
    tmpl = env.get_template(infile_fwd_slashes)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 1010, in get_template
    return self._load_template(name, globals)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 969, in _load_template
    template = self.loader.load(self, name, self.make_globals(globals))
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/loaders.py", line 138, in load
    code = environment.compile(source, name, filename)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 768, in compile
    self.handle_exception(source=source_hint)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "src/{{cookiecutter.project_slug}}/templates/index.html", line 1, in template
jinja2.exceptions.TemplateSyntaxError: Encountered unknown tag 'load'.
  File "src/{{cookiecutter.project_slug}}/templates/index.html", line 1
    {% load custom_tags %}

Can you please try again.

Got this error when starting new project:-
gitpod /workspace $ cookiecutter labzero/
project_name [myapp]:
project_author_name [My Name]:
project_author_email<EMAIL_ADDRESS>
project_version [0.0.0]:
project_description [Some description]:
project_slug [myapp]:
Traceback (most recent call last):
  File "/home/gitpod/.local/bin/cookiecutter", line 8, in <module>
    sys.exit(main())
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/cli.py", line 194, in main
    cookiecutter(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/main.py", line 114, in cookiecutter
    result = generate_files(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/generate.py", line 373, in generate_files
    generate_file(
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/cookiecutter/generate.py", line 173, in generate_file
    tmpl = env.get_template(infile_fwd_slashes)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 1010, in get_template
    return self._load_template(name, globals)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 969, in _load_template
    template = self.loader.load(self, name, self.make_globals(globals))
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/loaders.py", line 138, in load
    code = environment.compile(source, name, filename)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 768, in compile
    self.handle_exception(source=source_hint)
  File "/home/gitpod/.local/pipx/venvs/cookiecutter/lib/python3.10/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "src/{{cookiecutter.project_slug}}/templates/index.html", line 1, in template
jinja2.exceptions.TemplateSyntaxError: Encountered unknown tag 'load'.
  File "src/{{cookiecutter.project_slug}}/templates/index.html", line 1
    {% load custom_tags %}

The error fixed.


V4 Cherry build question

Hi, I received the following request from JLCPCB while ordering the v4 version (cherry), but I do not know anything about it, so I am asking a question.

Above image, the indicated pad and trace is connected. Should I need to separate them?

It's no problem.
I think it would be best for you to confirm the data with kicad before ordering to the factory.

I have fixed this just in case. Thanks

Thank you so much @foostan !


Update faq

/cc @ljharb and @jkrems
This doesn't solve for the node use case regarding polyfills, but I think that is something that we can create a mechanism to fix as an embedder.

Since polyfill ~= APM instrumentation, would the following become the standard way to start an application?
// Ensure all global state is in good shape
import 'apm';
import 'polyfills';

// Start loading any app code
await import('./actual-app');

I guess some of this might also be solved via custom loaders but the above seems like it would support both node and the browser (minus efficiency in the browser because it's not as prefetch-friendly without additional meta tags).

There's no need for the third import to be dynamic, as long as the polyfills and apm modules do not themselves use top-level await (i.e. do not explicitly choose to yield to the event loop).

Gotcha. The issue would only occur with, say:
if (!Promise.finally) {
  await import('./polyfills');
}

if (process.env.NODE_ENV === 'production') {
  await import('apm');
}

await import('./actual-app.js');


[ BUG ] Ratelimits

Describe
A clear and concise description of what the bug is.
To Reproduce
download a bunch of maps
418 (blocked ip from catboy.best)

Expected behavior
respect ratelimits
Screenshots

Additional context
Please handle 429 so your users don't get fucked over and end up being blocked off the mirror thank you very much

Uhrm, interesting status code.
I am not sure about the limitations of catboy.best mirror as it's not explicitly specified on their website. The only way is to tweak around the concurrency config to find the sweet spot. However you do reminded me to make a better queue system, as the current system handle request rate by download speed. Anyway, I suppose this is not a bug but rather a suggestion. Thank you for reporting.

For there being nothing on the site is fair, I will address that.
However Mino rate-limit works in 3 stages, we return 200 and obviously the download, then we return a 429, which is the standard for "Too many requests", if you keep requesting beyond that 429 (15req/min burst), we're going to ban that IP, and start returning 418.
If you don't want to handle the 429, we also provide a X-Ratelimit-Remaining header in the download, which you can also utilize for this purpose, this is returned no matter if the user is getting a 200 or a 429.
Our IP ban list from your service at this point is fairly long, (~30 IPs) and we'd not like it to get longer as this issue is transparent and likely not understood by the end users who utilize your application, therefore this ban is unfair on them.

Hi Philenst,
I apologize for the unintended misuse of your service by my program. This was not my intention, and I deeply regret any inconvenience caused.
Initially, I used chimu.moe, one of the largest osu! mirror service provider websites, which did not have strict rate limitations as per what I can remember. Consequently, I focused on overall functionality rather than rate limitation handling. After chimu.moe was discontinued, the original site redirected users to your service. I assumed it was managed by the same development team under a different brand, leading me to use your service similarly.
I understand the unfairness to end users and appreciate your transparency on this issue. Unfortunately, I cannot simply "terminate the service", as it runs locally on users' machines. Additionally, my program lacks an "announcement" or "notice" function to broadcast this issue. For now, the best I can do is update the README and any other available information to prevent new users from encountering this problem.
Regarding the implementation of rate limitation handling, I regret that I cannot address this immediately due to ongoing academic commitments and exams. I will seek a collaborator who can submit a pull request to resolve this issue as a matter of urgency.
Thank you for your understanding, and I sincerely apologize for any inconvenience caused.

Understood. I will try to make the necessary changes to your information after addressing my current academic commitments, likely after the middle of this month. Thanks a lot for your understanding :)

Close as completed, released v2.7.5

Thank you for the swift work on this @roogue, I've cleared out the ban list therefore all previously banned users will be able to utilise Mino once again.

Thank you, @Philenst. I apologize for any inconvenience caused previously. The current program allows up to 50 requests/min and 5 burst requests by default (429 is handled too), which has been tested and runs smoothly within this limit. Thank you once again for your free and API key-less service. If there are any issues or areas of dissatisfaction, please feel free to open a new issue. I am happy to discuss further.


Backport/metadata handling issue fixed in master

Fixes #19  and #22 for the core-api-v1 (aka 1.x logstash-core) series of plugins.

@jsvd can you let me know your thought on this backport?

Code LGTM, but we need to address the concurrent-ruby version problem before merging..
so if logstash-core is <=1.5.5 concurrent-ruby needs to be 0.9.1, but if > 1.5.5 then 0.9.2?

@jsvd as it's right now the gemfile is only helping on development environment. It will be harmless when installing the plugin/gem. what do you think?

but doing bundle install && bundle exec rspec will break as soon as 1.5.6 is released, right?
maybe we can pin down the logstash-core version only in the group?

well I guess as soon as 1.5.6 gets released we don't need this anymore. what do you think?

ahh because 1.5.6 pins a specific version of concurrent-ruby instead of ~0.9.1?
that still means we'll need to come to this plugin and remove the group definition, right?

+1 on removing the concurrent-ruby pinning
otherwise LGTM

ah and please change the logstash-core dependency to < 2.0.0.alpha0 ?

works for me, thanks for your feedback.


Investigate current state of unit testing

Why
We don't have any automated tests right now, and this is a considerable risk, especially when we work on new features.
Acceptance criteria

Identify if Jest is already setup in the project.
Setup Jest for unit test if its not already setup
Create unit tests for one component - the simplest one
Add the running of unit tests to CI

Now we can implement unit-tests (Jest) to our project.
Depend on our version Quasar, our project cant support Jest tests.

We won't address this in this repository
https://github.com/telosnetwork/epics/issues/9


[ZEPPELIN-2342] Improving Test Environment for zeppelin-web (e2e, coverage)

What is this PR for?
Improved testing environment for zeppelin-web

added test:watch command for continuous testing
displaying coverage report in console
e2e testing in zeppelin-web (can be written easily compare to the zeppelin-server integration tests. For example: home.spec.js)

This PR adds a zeppelin-web specific travis profile and it usually takes 8-9 mins to execute unit + e2e tests (zeppelin-web)

https://travis-ci.org/1ambda/zeppelin/jobs/252453901

Details

the headless chrome browser works with chromedriver 2.29+ (https://chromium.googlesource.com/chromium/src/+/c75dbfd25cc376b92a494d340259056a01e1432e)
in the case of ubuntu precise (our travis container), should use /usr/bin/chromium-browser
xvfb is required, please refer https://docs.travis-ci.com/user/gui-and-headless-browsers/#Using-xvfb-to-Run-Tests-That-Require-a-GUI and https://iamakulov.com/notes/install-google-chrome-on-travis/#what-does-the-code-mean
for protractor conf, please check https://github.com/travis-ci/travis-ci/issues/7650#issuecomment-302467188
can't install stable version of chrome, precise (12.04) support was dropped by chrome
chromium-browser (37.0) is shipped by default in precise and chromedriver version 2.11 is compatible with it. (https://support.saucelabs.com/hc/en-us/articles/225095307-Chromedriver-version-for-each-Chrome-browser-version, https://github.com/travis-ci/travis-ci/issues/5899)

What type of PR is it?
[Improvement]
Todos

[x] - test:watch
[x] - displaying coverage reports in console
[x] - e2e testing in zeppelin-web

What is the Jira issue?
ZEPPELIN-2342
How should this be tested?
CI should be green. If you want to test locally,

stop zeppelin which is running on localhost:8080
mvn package -DskipTests -DskipRat -Pweb-ci -B
mvn verify -DskipRat -pl 'zeppelin-web' -Pweb-ci -Pweb-e2e -B

Screenshots (coverage)

Screenshots (e2e)

Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - YES, updated

Oh, it looks great improvement!
Tested and LGTM. It works well and it's cool!
Thanks @1ambda

Thanks for the review. @soralee. It enables us to write integration tests easily. I will add some integration tests into zeppelin-web later based on this.
Merge if no more discussion.


Separate logic for last price saving and history writing

https://github.com/AndreyMashukov/go-crypto-bot/blob/d1773242a95e96bbff41c00cbaffc74fd8c86c09/src/repository/exhange_repository.go#L708
Make two separate methods
first one is for saving current price
Second one is for updating history
Push last price to history during reading history

It will allow us to decrease cpu usage and avoid having duplicated data in redis list


2018.4

The 2018.3 option doesn't work, says the signature is missing.

It's done. Now 2018.4 is supported as separate item of list