Add Meilisearch example using a CLI

@prrao87 I decided to also introduce CLIs here also because I have used them a lot with Meilisearch like this and have seen others doing the same so it seemed appropriate.

You did mention that CLIs are among the cases where Rust shows the biggest speedups over Python, so is there any way we could work that in here?

The biggest difference is in startup time and I have noticed that in these examples (unmeasured). There is a chance the Python example is faster on indexing. My perception while watching things run is it makes better use of async for this, but I haven't timed it yet or looked closely at the Rust SDK  code to verify. I'll see if I can come up with a good way to bench mark that includes the startup time, since I think that is the biggest win for the Rust CLI.

On a quick test using time meilisearch-cli create-index seems to illustrate this well:
Rust: ./meilisearch-cli create-index  0.01s user 0.01s system 10% cpu 0.140 total
Python: meilisearch-cli create-index  0.59s user 0.05s system 82% cpu 0.777 total

Awesome, I think it would be great to document the following in the readme:

Startup time (informal timing or just describing that Python is noticeably slower would work)
Indexing time (as you just noted)
Query time for 10 random queries

I think that should illustrate the goal of this piece really well!

I added a performance section. For the searches instead of doing truly random I did the same 10 searches in both Rust and Python so things would be even. If you have a better ideal let me know, you tend to be better at coming up with good ideas for this kind of thing than I am.

The timing numbers are very interesting! I'm not sure I understand what causes the Python CLI to be that much slower for just 10 queries. This isn't like a running web server, so every query that gets sent to the CLI is like a cold start on a web server or database, right?
I suppose the scenario of us sending 10 queries in sequence is a bit contrived, as this isn't typically how people interact with a CLI. But based on your understanding of how users have used your CLIs in the past, the startup time for the Python interpreter is actually noticeable, I presume? Which makes sense that Rust is the go-to language for CLIs these days.

For the searches instead of doing truly random I did the same 10 searches (each unique) in both Rust and Python so things would be even. If you have a better ideal let me know, you tend to be better at coming up with good ideas for this kind of thing than I am.

I think the 10 unique searches is more than enough to illustrate the point here. Your example is better than any I'd have come up with in this case!

The timing numbers are very interesting! I'm not sure I understand what causes the Python CLI to be that much slower for just 10 queries. This isn't like a running web server, so every query that gets sent to the CLI is like a cold start on a web server or database, right?

Exactly. With each run Python interpreter has to startup first and load the program which takes some time. If the multiple searches were done with one CLI command I expect the numbers would be much closer. I expected to see a difference with this, but honestly I didn't think it would be this big. It tested a single search to try to confirm this big difference and the rust program ran in 0.010s while the Python took 0.737s. So you pay a big penalty for the startup and that adds up over runs.

I suppose the scenario of us sending 10 queries in sequence is a bit contrived, as this isn't typically how people interact with a CLI. But based on your understanding of how users have used your CLIs in the past, the startup time for the Python interpreter is actually noticeable, I presume? Which makes sense that Rust is the go-to language for CLIs these days.

I initially was thinking it was contrived also and considered doing a different test. But the more I think about, it could add some value. It is true that you wouldn't do several rapid runs like this, but if you are taking the time to write a CLI it means you will most likely be running the program many times over the days/months/years. So over time the speed difference adds up. I'll add something to the description mentioning this.


make it work in cohortSymmetry

cdm <-
omock::emptyCdmReference("mock") |> omock::mockCdmFromTable(cohortTable = list(cohort2 =
markerCohort,
cohort1 = indexCohort)) |>
CDMConnector::copy_cdm_to(con = con,
schema = "main",
overwrite = T)
Error:
! write_schema must be provided in the cdm object to use this function
Run `rlang::last_trace()` to see where the error occurred.
Called from: signal_abort(cnd, .file)

make it run locally first.
create duckdb first , cdmref and copy the omock cdm into cdm created.


Makefile should create "bin" directory if not exists

The compilation will fail if there isn't a bin directory when you launch the build, so the Makefile should be able to check this and create a proper directory before continue.

Oh yeah, I faced this issue while working on issue #13.
I have fixed this in the makefile, can I submit a PR regarding this, before continuing with issue #13?

Actually there is a PR fixing this now, but go ahead!


fix position errors cocos2d-x #20725

see also https://github.com/cocos2d/cocos2d-x/pull/20744/files
THIS PROJECT IS IN DEVELOPMENT MODE. Any pull requests should merge to branch dev, otherwise will be rejected immediately.
Describe your changes
Issue ticket number and link
Checklist before requesting a review

[x] I have performed a self-review of my code

After some checks:
Zwoptex is really seldom used.
I closed it


Keyword arguments for chunks?

I always felt that type should be a keyword argument, mostly because I generally prefer keyword arguments over optional positional arguments. And in light of https://github.com/m3g/ChunkSplitters.jl/issues/18 it might make sense to even make nchunks a keyword argument, such that one can write:
chunks(array; n=8)
chunks(array; size=8)
chunks(array; n=8, type=:scatter)

Note that this would be similar to range where one can specify either length and/or step and/or start and/or stop.
Only downside is that chunks(array; n=8) is more verbose than chunks(array, 8) but only slightly and also more explicit.

And since I mentioned type, I'm not a fan of it to begin with. Maybe distribution/dist?
chunks(array; n=8, dist=:scatter)

(I'm bringing these things up now because #17 is anyways breaking 😀)

Should we default n to Threads.nthreads()? What you think?
(I'm not completely happy by dist or distribution - neither by type).

Done in the #17 PR. We use n= and distribution= for the keywords.

(I'm not completely happy by dist or distribution - neither by type).

More suggestions: scheme or split
E.g.
chunks(arr; n=8, scheme=:scatter)

Should we default n to Threads.nthreads()?

I don't think we should. First of all, chunking and multithreading are different things. Second of all, it might be strange to call chunks(arr) and get no chunking at all (i.e. 1 chunk) by default (i.e. when running single-threaded).

BTW, similar to range(1,4) (which means range(start=1, stop=4)) we could still have chunks(arr, 8) mean chunks(arr, n=8) if we wanted to.

I'm fine with the keyword only interface. I actually like it better.
I went for split for now, as the split is in the package name.


Crash when choosing Show Layout by XML in Demo

X11 Error encountered:
  Error: BadMatch (invalid parameter attributes)
  Request:     12 (0)
  Resource ID: 0x2600015
  Serial:      485
  Hwnd:        Hwnd, Mapped:True ClientWindow:0x2600016, WholeWindow:0x2600015, Zombie=False, Parent:[<null>]
  Control:     WeifenLuo.WinFormsUI.Docking.DockPanel, BorderStyle: None   at System.Environment.get_StackTrace() in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/corlib/System/Environment.cs:line 261
   at System.Windows.Forms.XplatUIX11.HandleError(IntPtr display, XErrorEvent ByRef error_event) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 2115
   at System.Windows.Forms.XplatUIX11.XTranslateCoordinates(IntPtr , IntPtr , IntPtr , Int32 , Int32 , Int32 ByRef , Int32 ByRef , IntPtr ByRef )
   at System.Windows.Forms.XplatUIX11.ClientToScreen(IntPtr handle, Int32 ByRef x, Int32 ByRef y) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 2695
   at System.Windows.Forms.XplatUI.ClientToScreen(IntPtr handle, Int32 ByRef x, Int32 ByRef y) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUI.cs:line 525
   at System.Windows.Forms.Control.PointToScreen(Point p) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3844
   at System.Windows.Forms.Control.RectangleToScreen(Rectangle r) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3928
   at WeifenLuo.WinFormsUI.Docking.DockPanel.GetAutoHideWindowBounds(Rectangle rectAutoHideWindow) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.AutoHideWindow.cs:line 602
   at WeifenLuo.WinFormsUI.Docking.DockPanel.OnLayout(System.Windows.Forms.LayoutEventArgs levent) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.cs:line 682
   at System.Windows.Forms.Control.PerformLayout(System.Windows.Forms.Control affectedControl, System.String affectedProperty) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3822
   at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 576
   at WeifenLuo.WinFormsUI.Docking.DockPanel.OnVisibleChanged(System.EventArgs e) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.cs:line 874
   at System.Windows.Forms.Control.OnParentVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 6166
   at System.Windows.Forms.Control.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 6293
   at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 578
   at System.Windows.Forms.Form.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:line 2152
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4789
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:line 2373
   at System.Windows.Forms.Control.set_Visible(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3200
   at System.Windows.Forms.Application.RunLoop(Boolean Modal, System.Windows.Forms.ApplicationContext context) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 823
   at System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext context) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 724
   at System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 707
   at DockSample.Program.Main() in /home/matthias/Projekte/dockpanelsuite-master/DockSample/Program.cs:line 17

X11 Error encountered:
  Error: BadMatch (invalid parameter attributes)
  Request:     12 (0)
  Resource ID: 0x26003EE
  Serial:      6097
  Hwnd:        Hwnd, Mapped:True ClientWindow:0x26003EF, WholeWindow:0x26003EE, Zombie=False, Parent:[<null>]
  Control:     WeifenLuo.WinFormsUI.Docking.DockPanel, BorderStyle: None   at System.Environment.get_StackTrace() in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/corlib/System/Environment.cs:line 261
   at System.Windows.Forms.XplatUIX11.HandleError(IntPtr display, XErrorEvent ByRef error_event) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 2115
   at System.Windows.Forms.XplatUIX11.XTranslateCoordinates(IntPtr , IntPtr , IntPtr , Int32 , Int32 , Int32 ByRef , Int32 ByRef , IntPtr ByRef )
   at System.Windows.Forms.XplatUIX11.ClientToScreen(IntPtr handle, Int32 ByRef x, Int32 ByRef y) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 2695
   at System.Windows.Forms.XplatUI.ClientToScreen(IntPtr handle, Int32 ByRef x, Int32 ByRef y) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUI.cs:line 525
   at System.Windows.Forms.Control.PointToScreen(Point p) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3844
   at System.Windows.Forms.Control.RectangleToScreen(Rectangle r) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3928
   at WeifenLuo.WinFormsUI.Docking.DockPanel.GetAutoHideWindowBounds(Rectangle rectAutoHideWindow) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.AutoHideWindow.cs:line 602
   at WeifenLuo.WinFormsUI.Docking.DockPanel.OnLayout(System.Windows.Forms.LayoutEventArgs levent) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.cs:line 682
   at System.Windows.Forms.Control.PerformLayout(System.Windows.Forms.Control affectedControl, System.String affectedProperty) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3822
   at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 576
   at WeifenLuo.WinFormsUI.Docking.DockPanel.OnVisibleChanged(System.EventArgs e) in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockPanel.cs:line 874
   at System.Windows.Forms.Control.OnParentVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 6166
   at System.Windows.Forms.Control.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 6293
   at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 578
   at System.Windows.Forms.Form.OnVisibleChanged(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:line 2152
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4789
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:line 2373
   at System.Windows.Forms.Control.set_Visible(Boolean value) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3200
   at System.Windows.Forms.Control.Show() in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4153
   at DockSample.MainForm.menuItemNewWindow_Click(System.Object sender, System.EventArgs e) in /home/matthias/Projekte/dockpanelsuite-master/DockSample/MainForm.cs:line 408
   at System.Windows.Forms.ToolStripItem.OnClick(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripItem.cs:line 1001
   at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripMenuItem.cs:line 266
   at System.Windows.Forms.ToolStripMenuItem.HandleClick(Int32 mouse_clicks, System.EventArgs e) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripMenuItem.cs:line 538
   at System.Windows.Forms.ToolStripItem.FireEvent(System.EventArgs e, ToolStripItemEventType met) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripItem.cs:line 1778
   at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs mea) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStrip.cs:line 970
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs mea) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripDropDown.cs:line 635
   at System.Windows.Forms.Control.WmLButtonUp(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 5279
   at System.Windows.Forms.Control.WndProc(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 5020
   at System.Windows.Forms.ScrollableControl.WndProc(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 651
   at System.Windows.Forms.ToolStrip.WndProc(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStrip.cs:line 1226
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ToolStripDropDown.cs:line 727
   at System.Windows.Forms.Control+ControlWindowTarget.OnMessage(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 228
   at System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message ByRef m) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 209
   at System.Windows.Forms.NativeWindow.WndProc(IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/NativeWindow.cs:line 240
   at System.Windows.Forms.XplatUIX11.DispatchMessage(MSG ByRef msg) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 3576
   at System.Windows.Forms.XplatUI.DispatchMessage(MSG ByRef msg) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUI.cs:line 605
   at System.Windows.Forms.Application.RunLoop(Boolean Modal, System.Windows.Forms.ApplicationContext context) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 941
   at System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext context) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 724
   at System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm) in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Application.cs:line 707
   at DockSample.Program.Main() in /home/matthias/Projekte/dockpanelsuite-master/DockSample/Program.cs:line 17

System.NullReferenceException: Object reference not set to an instance of an object
  at System.Windows.Forms.MdiWindowManager.FormClosed (System.Object sender, System.EventArgs e) [0x0001c] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/MdiWindowManager.cs:401
  at System.Windows.Forms.Form.OnClosed (System.EventArgs e) [0x0001c] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2003
  at System.Windows.Forms.Form.FireClosedEvents (CloseReason reason) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:159
  at System.Windows.Forms.Form.RaiseCloseEvents (Boolean last_check, Boolean cancel) [0x00092] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2554
  at System.Windows.Forms.Form.WmClose (System.Windows.Forms.Message& m) [0x000b8] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2597
  at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message& m) [0x000c0] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2438
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:228
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0000c] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:209
  at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x0008e] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/NativeWindow.cs:240
System.NullReferenceException: Object reference not set to an instance of an object
  at System.Windows.Forms.MdiWindowManager.FormSizeChangedHandler (System.Object sender, System.EventArgs e) [0x00048] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/MdiWindowManager.cs:167
  at (wrapper delegate-invoke) <Module>:invoke_void__this___object_EventArgs (object,System.EventArgs)
  at System.Windows.Forms.Control.OnSizeChanged (System.EventArgs e) [0x00029] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:6229
  at WeifenLuo.WinFormsUI.Docking.DockContent.OnSizeChanged (System.EventArgs e) [0x00056] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContent.cs:331
  at System.Windows.Forms.Control.UpdateBounds (Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight) [0x000f2] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4881
  at System.Windows.Forms.Control.UpdateBounds (Int32 x, Int32 y, Int32 width, Int32 height) [0x00023] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4842
  at System.Windows.Forms.Control.SetBoundsCoreInternal (Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) [0x0012c] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4716
  at System.Windows.Forms.Control.SetBoundsCore (Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4662
  at System.Windows.Forms.Form.SetBoundsCore (Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) [0x00096] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2323
  at System.Windows.Forms.Control.SetBoundsInternal (Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) [0x000a8] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4138
  at System.Windows.Forms.Control.SetBounds (Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) [0x00044] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4123
  at System.Windows.Forms.Control.set_Size (Size value) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:3048
  at System.Windows.Forms.Form.set_Size (Size value) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:1195
  at System.Windows.Forms.Form.set_FormBorderStyle (FormBorderStyle value) [0x00084] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:710
  at System.Windows.Forms.Form.set_MdiParent (System.Windows.Forms.Form value) [0x000d5] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:920
  at (wrapper remoting-invoke-with-check) System.Windows.Forms.Form:set_MdiParent (System.Windows.Forms.Form)
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.SetPane (WeifenLuo.WinFormsUI.Docking.DockPane pane) [0x0009f] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:696
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.RemoveFromPane (WeifenLuo.WinFormsUI.Docking.DockPane pane) [0x0000d] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:410
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.set_PanelPane (WeifenLuo.WinFormsUI.Docking.DockPane value) [0x00053] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:395
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.set_Pane (WeifenLuo.WinFormsUI.Docking.DockPane value) [0x00054] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:289
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.set_DockPanel (WeifenLuo.WinFormsUI.Docking.DockPanel value) [0x00012] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:232
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.Dispose (Boolean disposing) [0x00008] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:40
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.Dispose () [0x00001] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:32
  at WeifenLuo.WinFormsUI.Docking.DockContentHandler.Form_Disposed (System.Object sender, System.EventArgs e) [0x00001] in /home/matthias/Projekte/dockpanelsuite-master/WinFormsUI/Docking/DockContentHandler.cs:916
  at System.ComponentModel.Component.Dispose (Boolean release_all) [0x0004f] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/System/System.ComponentModel/Component.cs:134
  at System.Windows.Forms.Control.Dispose (Boolean disposing) [0x000b9] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:984
  at System.Windows.Forms.ContainerControl.Dispose (Boolean disposing) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ContainerControl.cs:544
  at System.Windows.Forms.Form.Dispose (Boolean disposing) [0x00045] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:1986
  at DockSample.DummyDoc.Dispose (Boolean disposing) [0x0001f] in /home/matthias/Projekte/dockpanelsuite-master/DockSample/DummyDoc.Designer.cs:20
  at System.ComponentModel.Component.Dispose () [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/System/System.ComponentModel/Component.cs:111
  at (wrapper remoting-invoke-with-check) System.ComponentModel.Component:Dispose ()
  at System.Windows.Forms.Control.Dispose (Boolean disposing) [0x0009d] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:980
  at System.ComponentModel.Component.Dispose () [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/System/System.ComponentModel/Component.cs:111
  at (wrapper remoting-invoke-with-check) System.ComponentModel.Component:Dispose ()
  at System.Windows.Forms.Control.Dispose (Boolean disposing) [0x0009d] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:980
  at System.Windows.Forms.ContainerControl.Dispose (Boolean disposing) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ContainerControl.cs:544
  at System.Windows.Forms.Form.Dispose (Boolean disposing) [0x00045] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:1986
  at DockSample.MainForm.Dispose (Boolean disposing) [0x0001f] in /home/matthias/Projekte/dockpanelsuite-master/DockSample/MainForm.Designer.cs:20
  at System.ComponentModel.Component.Dispose () [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/System/System.ComponentModel/Component.cs:111
  at (wrapper remoting-invoke-with-check) System.ComponentModel.Component:Dispose ()
  at System.Windows.Forms.Form.WmClose (System.Windows.Forms.Message& m) [0x000f0] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2602
  at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message& m) [0x000c0] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2438
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:228
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0000c] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:209
  at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x0008e] in /home/abuild/rpmbuild/BUILD/mono-3.0.6/mcs/class/Managed.Windows.Forms/System.Windows.Forms/NativeWindow.cs:240

I got this error in a few other places, all of them related to invalid coordinates (negative values) and/or zeroed widths and heights. Mono seems to set the layout in a crazy order, so when some of these functions are called when the window is about to be shown, the actual dimensions of the window aren't set yet, that's why X11 blames about invalid parameters, probably negative coordinates/dimensions being passed to it.
The solution is to include a check to see if the window/button/rectangle coordinates and dimensions are higher than zero before calling these functions.
I'll try to come up with a structured fix ASAP.

I got this error in a few other places, all of them related to invalid coordinates (negative values) and/or zeroed widths and heights. Mono seems to set the layout in a crazy order, so when some of these functions are called when the window is about to be shown, the actual dimensions of the window aren't set yet, that's why X11 blames about invalid parameters, probably negative coordinates/dimensions being passed to it.
The solution is to include a check to see if the window/button/rectangle coordinates and dimensions are higher than zero before calling these functions.
I'll try to come up with a structured fix ASAP.

Can you update how to fix this error?
Thanks

See https://github.com/DanWBR/dwsim3/commits/master/DockPanelSuite/WinFormsUI/Docking


Feature request: cask aliases

Description of feature/enhancement
Is it possible to have cask aliases, similar to those in homebrew/homebrew-core?
I tried adding the Aliases directory locally, but didn't seem to have any effect.
Justification
It's helpful when the "default" formula/cask can still be installed provided it's respective version.
Also helpful to have common, alternative names to a cask.
Example use case
java8 aliases to java.
Existing example: node@8 aliased to node in homebrew/homebrew-core.

I personally think that this falls under Homebrew-Cask is not a discoverability service.

our users are expected to have reasonable knowledge about the apps they’re installing through us before doing so

What you ask is already covered by name. It provided all the disambiguation needed while searching, and is clearer than having a bunch of token aliases.
Only problem is search doesn’t yet take advantage of it. PRs welcome.


feat: in-app ramps for "invite user to an application" and "custom roles"

This PR adds in-product ramps for invite user to specific apps and custom roles
GAC details are available at this Notion doc https://www.notion.so/appsmith/GAC-668b5ded22ce45a29d8bdfcf76c4df50
PR fixes following issue(s)
Fixes # (issue number)
https://github.com/appsmithorg/cloud-services/issues/813
https://github.com/appsmithorg/cloud-services/issues/812
Media
https://www.loom.com/share/1649d35e42c64dfa81fdbdfa9958ca34
Type of change

Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[x] Jest
[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/build-deploy-preview recreate=true

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/build-deploy-preview recreate=true

/ok-to-test

/build-deploy-preview recreate=true

/ok-to-test


Abstract activation of extension code for unittesting

Add unit tests to ensure extension gets activated.
We need to test the activation event of the extension.

@brettcannon @d3r3kk
I've been working on some tests to measure and compare the activation times of the extension for:

Dev version
Release version
Dev version with Jedi disabled (i.e. using analysis engines)

Output:

Give us an indication of the load times
Will also confirm the fact that the extension loads and gets activated

Discuss:

How do we run these tests? I wouldn't want to run these every time, on every PR.
This test is kind of a smoke test, mixed with some performance metrics
Should these tests be invoked as a separate task as part of the release plan?

Load times are definitely a good thing to track.
We can run it every time, on every PR, but only if the startup time is fairly quick (I imagine it is) and we can operate this set of tests in parallel to other tests.
However, if it still proves too costly time-wise, then the next best thing is to send it along the pipeline to our release process.
I opened #1807 to discuss  the actual release process.

What @d3r3kk said. If it's fast enough then it can be per PR, otherwise it can be per merge. IOW anything that is a critical gate and would break the majority of users using a development build should gate on the PR, otherwise we can run stuff like this which won't break the extension and we can assume most of the time will be fine against master after each merge.


Integrating flow [work in progress]

Based on https://github.com/chrmod/spanan/pull/19

currently it throws:
Built with error:
index.js: index.js: Unexpected token (23:16)
        in /tmp/broccoli-3794UD1rvOe6ELSR/out-07-broccoli_merge_trees
        at broccoli-persistent-filter:Babel

dropping the topic for now


@-sign in object literal compiles into invalid Javascript

I was bit surprised to find out today that this compiles:
foo = @bar: 1

The output is
var foo;
foo = {
  this.bar: 1
};

Which is invalid Javascript.
I think that CoffeeScript compiler should throw an error when trying to compile this.

→ #1055


Recruitment invitation: tokens must be persisted with the API supported tokens

API supports: {{firstname}} and {{fullname}}
Recruitment form supports: {name}, {accept_url} and {decline_url}.
I suggest to rename the recruitment token to be: {{fullname}}, {{accept_url}} and {{decline_url}} in order to be consistent with the API and the users don't get confused.
When replacing {{fullname}} with the invitee name, I also suggest to ignore the replacement if the invitee has a profile. Let's delegate the replacement to the API so it can get the preferred name of the user.
Thoughts @carlosmondra ?

Nope, I don't have any. I think for now this is fine. I guess later it would be nice if all the replacements are done in the same place.

What do you mean make two separate functions?
I see that you already changed the journal code what is great.


invalid Exclude parameter

Hi,
trying to add more filter to the Exclude option but soon as I am trying to add a second one, separated by comma as indicated in the doc, I got this error:
dotnet test /p:CollectCoverage=true /p:CoverletOutput=Coverage\  --no-build /p:Exclude="[xunit.*]*,[*]DAL.ModelsV2.*"
MSBUILD : error MSB1006: Property is not valid.
Switch: [*]DAL.ModelsV2.*

For switch syntax, type "MSBuild /help"

corverlet version: 2.6.3

ok...msbuild doesn't handle well ,, we are in 2019 :).
If you encode it %2c, it's working well:
dotnet test /p:CollectCoverage=true /p:CoverletOutput=Coverage\  --no-build /p:Exclude="[xunit.*]*%2c[*]DAL.ModelsV2.*"

Thanks!

Actually it's not so clear on guide, it's under Note for Powershell / VSTS users maybe we should make it clearer.

Cannot confirm right now but I think I try and got the same error on CMD too, so not only Powershell but "Windows"


Add git tag for 3.15 release

Currently there is no release/3.15.0 tag. On https://microsoft.github.io/language-server-protocol/specification#version_3_15_0 it shows a release date of 09/19/2019 so at that time the latest commit on master appears to have been: https://github.com/microsoft/language-server-protocol/commit/68775c83e00e02d9e2972858b74cfe5d3c779c82

The tag is: 05b3224 - Publish 3.15 specification
The problem is the wrong date in the markdown document. Will fix that.
OK to close.

Thanks for the info! Can you create the tag and push it up to GitHub as well? You can see that there is no 3.15 in https://github.com/microsoft/language-server-protocol/releases (which is driven by git tags).

Done. Sorry for missing it.

Great, thanks!


created code analysis config

Description
Adds automated github code scanning
Motivation
Need for security scanning

Solid addition to cover all our bases, thank you Alex!


CONTRIBUTING.md still mentions license to be BSD

This library's license was changed from BSD + patent grants to MIT in March 2018. However, the CONTRIBUTING.md file still states the license to be BSD.

This was addressed by https://github.com/graphql/libgraphqlparser/pull/88.


Question: Live server sudo mode for port 80

I'm submitting a...
Question

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ X] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior
I tried to set to port 80 in settings.json, however, it will auto changed to port 81. Port 80 is empty and available, i would say the culprit live server doesn't have the permission (sudo) to use Port 80. How can I enable Sudo mode and use port80?
I am trying to connect to other software and they are sending HTTP request only.

Environment
Computer: MacBook Pro (M1, 2020)
OS: IOS 11.1
Live Server Version: v5.7.9 (version number after reinstalled) (no info for version number before reinstalled)
VSCode Version: 1.56.2 (Universal)
Browser:

- [ x] Chrome (desktop) version 89.0.4389.114
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

Make sure nothing is running on port 80.
https://superuser.com/questions/597398/no-idea-what-is-listening-on-port-80-in-os-x

Make sure nothing is running on port 80.
https://superuser.com/questions/597398/no-idea-what-is-listening-on-port-80-in-os-x

As stated in the question, PORT 80 IS CONFIRMED EMPTY AND NO SERVICE IS OCCUPIED.


added lcov report gen for web and pdf (squashed into 1!)

All lcov uploads to same as php one
Tweaks to use node for jest test instead of puppeteer
Use node-browser docker image
Added arch key for uniqueness in caching
Additional steps for calling webhook on coveralls
Added docker images for php-cli-node for the upload
this is subject to the result of issue request:
https://github.com/lemurheavy/coveralls-public/issues/1390#issuecomment-594410482
reverted to use codecov. this has issues with reporting when a coverage report is done, still reports this in the browser. may improve once the build process splits into build and path to live.

Purpose
Briefly describe the purpose of the change, and/or link to the JIRA ticket for context
Fixes UML-####
Approach
Explain how your code addresses the purpose of the change
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the Refunds service
Checklist

[x ] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Coverage increased (+0.03%) to 75.622% when pulling 2cb8b9b74f6bdd81374de6253cc5e45509761889 on UML-431-Add-coveralls-to-web into 1cddaea7282b93917ea00030b088d9d9863c3fa2 on master.

Wait, codecov is working?
🕺

Wait, codecov is working?
🕺

Yup! only. Thing is now it needs to add a PR comment when done. currently not possible as CodeCov is waiting for the build to complete, as it has an approval state. Once the build split is done in UML-540, this should theoretically work as i'd expect.

Closing for now - will reinstate at a later date.

codecov coverage working now.


400 on trying to download local-universe.tar.gz

https://github.com/mesosphere/universe/blob/version-3.x/docker/local-universe/README.md
The URL's to mesosphere domain in this link are outdated. example: https://downloads.mesosphere.com/universe/public/local-universe.tar.gz 404

file is present. likely a permission issue. 🤔
@fatz?

No i guess the file is to big. We had such issues already. The max cloudfront filesize is 20G this file is about 28G
I just checked the docs we don't seem to have local universe somewhere in our docs anymore!? There is a way which we provide to EE customers. So I'd like to ask contacting our support you will get a working universe address from them.
@pierrebeitz we should take this into the next DC/OS meeting. The here mentioned README is outdated and we must decide how to rephrase this and provide a different solution


modifyUrl setting not useful

show my code
<scrollactive
      :modify-url="false"
      :always-track="true"
      :duration="800"
      bezier-easing-value=".5,0,.35,1"
>
      <h-navbar
              :slider="{
                width: 50,
                height: 4,
                color: '#FF4A83',
              }"
              :tabs="tabs"
      >
              <a :slot="`tab${index}`" :href="`#floor${index + 1}`" v-for="(item, index) in tabs" :key="index">{{item}}</a>
      </h-navbar>
</scrollactive>

as i set props modifyUrl to false
but i find noting happend
the url is also be modifyed,
like: http://localhost:8080/#/course/courseList?courseId=COURSEID to http://localhost:8080/#/floor1
i do something error?

ou,
i see it,
if i set class='scrollactive-item' ,
modifyUrl is useful,
but there is also question,
i cant scroll to dom

Hello, do you still have the described problem? I couldn't reproduce it in my environment, but might be because you're using router with hash mode instead of history mode.
I would be glad if you or someone could reproduce this and tell if it's a bug or just something else.

Great to know then :) Cheers


AssertionError: The render_mode must be 'rgb_array', not None

HI, when I execute python3 reach/ppo.py, I received an error says

can I do anything to solve this?

Hi @ziyao-hhs,
in the newest release, stable-baselines has changed over to gymnasium in favor of gym.
I will change the required version of stable-baselines in setup.py to version v1.8.0, until I also migrate sofa_env and sofa_zoo to gymnasium.
Let me know, if that solves your issue.
Cheers,
Paul

getting this issue after trying with main branch, gynamisum is installed

Hi @saketh2002,
sadly I currently do not have a system on which to test this.
Could you please open a new issue?
I will try to give it a look in September.
Best,
Paul

Yeah, will actually mention the issue elaborately over there


[Bug] Incompatibility with "Charm"

Versions

Charm version - charm-fabric-1.16.4-2.2.0` (latest release offed in issue 442)
ATBYW version - atbyw-1.16.4-1.3.4
Minecraft version - 1.16.4`

Description
Bootup crash when loading with All The Blocks You Want With Charm
(crash before Mojang loading screen)
latest.log
Also Uploaded on other mods issue tracker HERE

This has been reported day 1 when I released the mod, I still don't really know how I could fix it without breaking my mod...

it seems Charm's EnchantingTableBlockMixin and ATBYW's EnchantingTableBlockMixin are trying to mixin into the same part of the same class.
Which causes the game to crash on startup.

My bad, I checked the charm page first and didn't see a report there and created this post after already creating the charm post.
would an option in the config file to completely remove the enchanting table related content resolve the issue?

For the time being, I came up with the best workaround my coder illiterate brain could muster, expanding off of your suggestion from Issue #2
Charm and ATBYW Both add nearly the variant bookshelves. however, you took it a step further with the Redstone bookshelves, Charm also has a config to disable every aspect of the mod so for now...

Remove "EnchantingTableBlockMixin" From charms mod file
Set "VariantBookshelves Enabled" = false in the charm config

For the time being, I came up with the best workaround my coder illiterate brain could muster, expanding off of your suggestion from Issue #2
Charm and ATBYW Both add nearly the variant bookshelves. however, you took it a step further with the Redstone bookshelves, Charm also has a config to disable every aspect of the mod so for now...

Remove "EnchantingTableBlockMixin" From charms mod file
Set "VariantBookshelves Enabled" = false in the charm config
Set "VariantLadders Enabled" = false being that both mods add them (ATBYW also adds bamboo)

Yeah the best workaround to avoid crash on startup so far is to disable either of the two mods EnchantingTableBlockMixin. The ladders might also cause some recipe interferences but I didn't get to test that, thanks for mentioning it.

Charm resolved this issue with their latest update, it also resolves an issue with charm and better end having the same problem so the 3 mods should work fine together now
https://github.com/svenhjol/Charm/issues/448

Alright, I saw it when they added it to the source, I was just waiting for it to be released fully


Mismatch of DB (table: data, column: localdata_value) between flyway migration script and building db via hibernate

If flyway is used to create the DB scheme, data-table's localdata_value column has oid type see
https://github.com/International-Data-Spaces-Association/DataspaceConnector/blob/1957363bab5f3d98f1e849a8a76895fd5274480f/src/main/resources/db/migration/V5.0.0__Baseline.sql#L114
Export of table after creation:
create table if not exists data
(
    dtype           varchar(31) not null,
    id              bigint not null primary key,
    deleted         boolean default false,
    localdata_value oid,
    access_url      varchar(2048)
);

If DB is created from scratch without flyway, the column has TEXT type, see:
https://github.com/International-Data-Spaces-Association/DataspaceConnector/blob/1957363bab5f3d98f1e849a8a76895fd5274480f/src/main/java/io/dataspaceconnector/model/artifact/LocalData.java#L53
Export of table after creation:
create table if not exists data
(
    dtype           varchar(31) not null,
    id              bigserial
        primary key,
    deleted         boolean,
    localdata_value text,
    access_url      varchar(2048)
);

Solution

[ ] DB migration fix for v8 shall be created in separate file converting oid to TEXT https://github.com/International-Data-Spaces-Association/DataspaceConnector/tree/main/src/main/resources/db/migration

renaming of value field to localdata_value was a result from trying to support mssql databases, which was reverted due to other problems, occuring afterwards


🐛 BUG: KV local dev broken for Nextjs.

Which Cloudflare product(s) does this pertain to?
KV
What version(s) of the tool(s) are you using?
Wrangler C3 , Nextjs 14.2.3
What version of Node are you using?
3.69.1
What operating system and version are you using?
Mac OS Monterey 12.7.6
Describe the Bug
Following documented methods as described on cloudflared docs.
KV bindings work when deployed.
Values displayed as null when running locally using wrangler cli or next dev (next dev as documented being the preferred method)
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
Return is null and no error logs

Could you please share your code so that I can help you troubleshoot it?


Location reading interval

Stream location now manages also the notifications that keeps to send the locations even if the app is killed.
It is possibile to set the notification interval and it must be >=60 seconds.
It is possible to set the accuracy and to customise the notification message content.
The UserNotificationDelegate.swift and LocationUtility.swift files are no longer needed.

@matteoKuama
This is an example on how you should write the comments:
/**
 This method sum two double numbers and returns.

 Here is the discussion. This methods adds two double and return the optional Double.

 - parameter number1: First Double Number.
 - parameter number2: Second Double Number.
 - returns: The sum of two double numbers.

 # Notes: #
 1. Parameters must be **double** type
 2. Handle return type because it is optional.

 # Example #
\`\`\`
 if let sum = self.add(number1: 23, number2: 34) {
  print(sum)
 }
 \`\`\`
*/

Also please create constants with reasonable names for the magic numbers  inside LocationUtility and evaluate the possibility to transform those static methods into extensions

Added comments for StreamLocation.swift.
UserNotificationDelegate.swift and LocationUtility.swift files are no longer needed, so they can be deleted.


Tailwind styles not showing on generated site, after running nuxt generate

Version
"@nuxtjs/tailwindcss": "^4.2.1",
"nuxt": "^2.15.7",
"postcss": "^8.3.5"
Reproduction Link

Repo: https://github.com/revueltai/nuxt-tailwind-poc

Clone the repo
Run yarn dev > The site should load with the correct styles
Run yarn generate + yarn start > The site should generate correctly, but styles look broken when running it.

Live Generated site: https://60e827bc46bf75b117417d77--admiring-feynman-abdd06.netlify.app/
Comparison Screenshot: https://a.storyblok.com/f/47007/4730x2576/0df151cde6/screenshot-tailwind-nuxt.jpg

Steps to reproduce
Tailwind styles seem to not be included to the site, after running yarn generate.
I am attaching an example  repo that shows my problem in a context as close as possible to the real project I have to work on.
I see that if I set purging to false the generated site looks correct, but, as expected, the outputted css is very large.
I followed the installation steps stated here.
I tried many of the related answers on this repo's issues, but none solved the problem :( .
At this stage I cannot figure it out if it is a dumb simple "you forgot to install something" problem, or some whitelisting I am missing, or if there is another issue going on.
Any help solving this will be greatly appreciated!
What is Expected?
The generated version should look the same as the dev one.
What is actually happening?
The generated version doesn't show the styles for most of the elements.

Also: noticed that we had to add grid, for example, to the safelist object of tailwind, so that nuxt build wouldn't erase classes such as: grid-cols-3.

In our case the problem lied on Tailwind purging those classes that were created after concatenating strings (in a computed prop for example).
This would work:
computed () {
    getFontSize () {
         return 'sm:text-xl'
    }
}

And this would fail:
data () {
  return {
     fontSize: 'text-xl'
  }
},
computed () {
    getFontSize () {
         return 'sm:' + this.fontSize
    }
}

Our temp solution, so far, has also been adding all those classes that were being purged into the safelist object.

Having this issue.  Did you figure out a permanent solution?

this fixed itself, for me, most probably through an upgraded version. Too much time has passed, to remember exactly.

I feel like this should be getting addressed further. The deeper problem I feel like is order of operations when it comes to when classes are generated and components are rendered by StoryblokComponent. Sure, I can use the safelist, but the convenience of auto-generated classes is destroyed by having to do this.


Remove ruamel.yaml from requirements

Signed-off-by: Kaiyuan Hu<EMAIL_ADDRESS>

/lgtm
/approve


Accessibility of pages where something is revealed as a result of an interaction but not given focus

We may already have separate issues about individual pages but I'm adding this as a general issue for discussion during the next developer day. We have a number of pages like annotated diagram, hotspot image and others where infor is hidden by default and then revealed after the click of a label, button or hotspot etc. Tab order is usually correct in terms of getting to those links, buttons and hotspots but after choosing one of those a screenreader user isn't taken to the revealed content.

I think I've fixed all of these so closing the issue. Will re-open if there are still pages not yet done.


generateBlobSASQueryParameters(...).toString() returns improperly escaped URL query parameters

Package Name: @azure/storage-blob
Package Version: 12.1.1
Operating system: Ubuntu 18.04.4
[x] nodejs

version: 12.16.1

[x] typescript

version: 3.8.3

Bug description
generateBlobSASQueryParameters(...).toString() sometimes generates improperly escaped URL query parameters. This happens rarely. In all the instances it occurred, the improperly escaped portion of the query parameters was always in the "sig" field and the character "+" was the one that was not properly escaped.
The blobstore returns 403 unauthorized error as the sig field is incorrect.
Replacing the "+" symbol with %2B fixes the issue. I have provided 2 instances of the incorrect query parameters generated by the function:
sv=2019-07-07&st=2020-06-05T13:30:42Z&se=2020-06-05T14:30:42Z&sr=b&sp=r&sig=BoZh+1sadbfxQgMVcpuZwL9QL5Xz1W/zcGpVe2i7lik=
sv=2019-07-07&st=2020-06-05T11:53:45Z&se=2020-06-05T12:53:45Z&sr=b&sp=r&sig=tAJYTYjWGMjjiU+Ai+uvYgXjWbFnPjjF5HRCSdAi3NU=
Steps to reproduce the behavior
The bug is hard to reproduce. I have attempted repeatedly generate SAS URLs for a blob and have failed to get an improper URL over 1000 attempts.
Current workaround
Replace all occurrences of "+" in the URL with %2B. But this can be messy and result in incorrect behavior. Another possibility it to attempt to get a new set of SAS query parameters from the server. It is very likely to not contain the error.

Thanks for report! I'll check what happens, thanks for your efforts with over 1000 attempts.

@ljian3377 Can you help check? Given the CRI assignment.

What do you mean by

Replace all occurrences of "+" in the URL with %2B. But this can be messy and result in incorrect behavior.

Previously, we were running axios.get(URLwithSASParams). It failed on the input examples I had provided. Just as a test we ran axios.get(URLwithSASParams.replace('+', '%2B')). This successfully fetched the Blob.

For

Another possibility it to attempt to get a new set of SAS query parameters from the server. It is very likely to not contain the error.

actually no request is made to the server to generate the SAS. So same input should generate the same result. It's a pity you haven't logged you input that generated the SAS with +.

My bad. I was referring to the "server" in my application which generates the SAS tokens, and not the blob store server.
Regarding the inputs, the inputs to the function are 1) container name, 2) blob name, 3) permissions, and 4) shared key credentials. Apart from these, I notices the function implicitly uses the current timestamp (in seconds) as input. We have the log of the timestamp (+-10 seconds) when the SAS tokens were generated. Will I be able to reproduce the bug with that?

Hi @viveksesha
SAS generation will force encodeURIComponent for each query parameter name and key including sig. Refer to
https://github.com/azure/azure-sdk-for-js/blob/d6308753263c0abe85072b06d02abed1fc908898/sdk/storage/storage-blob/src/SASQueryParameters.ts#L461
encodeURIComponent escapes "+" to "%2B".
Can you help provide your sample for reproduce?

Hi @XiaoningLiu ,
I have been unable to reproduce the error. The two to three errors we noticed were all in a short burst. I think we can safely mark this as closed for now. I will get back here if I notice the error again.
--
Vivek


Added "Define and operate on a type represented as a bitfield" example

I've added the bitflags example but unfortunately there is a linking error due to other book dependencies using different bitflags versions.
clap -> bitflags 0.8.2
png -> bitflags 0.7.0
openssl -> bitflags 0.9.1
This results in standard problem
error[E0465]: multiple rlib candidates for `bitflags` found
 --> /tmp/rust-skeptic.wsSHTSHfCBhF/test.rs:3:1
  |
3 | extern crate bitflags;
  | ^^^^^^^^^^^^^^^^^^^^^^
...

It the moment I have no idea how to work around such problem in general without changes to skeptic or cargo itself
fixes: https://github.com/brson/rust-cookbook/issues/189

blocked on https://github.com/kbknapp/clap-rs/pull/966
blocked on https://github.com/PistonDevelopers/image-png/pull/56
both dependencies updated but we are still blocked until each releases new version to crates.io.
Update: image-png and image have released a new version compatible with bitflags "^0.9". Still waiting for clap-rs

Seems like the root bug in skeptic needs to be fixed https://github.com/brson/rust-skeptic/issues/18. This is a horrible problem.

The https://github.com/brson/rust-skeptic/issues/18 will have to be solved otherwise contribution to and maintenance of cookbook will not be realistic (see this issue history).


fix: obey --ignore-scripts CLI option

Set npm_config_ignore_scripts=true in the env so that it propagates to
when the config spit out by 'npm config ls --json' which is then fed in
to npm-lifecycle.
Fixes #7

Makes sense. This is just the quick'n'dirty fix I used locally to get it working on a project.
@mikesherov should opts be passed through to config()?

Sorry, for the short answer. I was on mobile before. Ideally the runScript function would early return BB.resolve(); for that option.
Let me know if that makes sense. Also, please add a unit test to prove the functionality.
Thanks so much for contributing!

@mikesherov @zkat is this more in line with what you were looking for?

This is great thanks!

Cool. Squashed and cleaned up the commit message so it is no longer a lie, in case it is wanted as-is.


mail function in Actions

Is this a thing yet? Just wondering because it's documented here.
I couldn't find any hint of the mailer being integrated into actions.

WIP at the moment - those docs are evidence of my occasional "docs-driven development" approach. There is no mail() method on actions yet. Certainly open to alternatives as well.

As a service?

That's certainly an option (sending emails was actually one of the original use cases I had in mind for services, among other things).
My only hesitation with sending emails via a service is that it opens it up for userland code to break framework conventions. I.e. what happens if someone adds their own mail service that would override the builtin mail service?
I could see pros and cons here - it's cool to be able to implement framework functionality using already existing features (a kind of dogfooding exercise I suppose). But it also opens up the ability for users to mess with framework conventions (i.e. if I override the mail service with my own incompatible service, I lose out on all the benefits of the framework / convention based approach). Do we want to allow that kind of potential footgun?
@tomdale - I know you're out on vacation this week, but whenever you're back, I'd love to hear your thoughts if you have any on this issue.

My only hesitation with sending emails via a service is that it opens it up for userland code to break framework conventions. I.e. what happens if someone adds their own mail service that would override the builtin mail service?

Sounds like a nice way to override. The only thing I'd do is print a console log if an addon is overwriting an internal service.

It is, but my question is do we want to allow overrides? In other words, if mailers are baked in and conventional in Denali, allowing overrides in the public API loses some of that benefit. If I develop some email related addon for denali, now I can't trust that Action#mail() does what the docs suggest, since the user can override [1].
I'm starting to think that if we allow overrides, then mailers shouldn't even be baked into the core framework. It could be an officially supported userland addon, similar to how Ember Data is the officially supported data lib, but there are other implementations too.
While I'm not convinced there's enough variation in how email sending is handled that it needs to be an overridable userland thing, I'm starting to lean towards an official userland addon as a starting point, which could be absorbed by core later on once we discover the appropriate patterns. Seems easier to go that direction than the reverse (have it start in core, discover enough variation that it gets extracted into userland later).

[1] When I say "can override", I mean the framework allows and even invites overrides. Obviously, this is JavaScript, so a user can override whatever they feel like. I'm more concerned with what the "good citizen" of the Denali ecosystem would be encouraged to do.

Yeah maybe an addon is the best way and we just include it by default.
Would it provide a service or extend Action?

In that scenario, I say provide as a service. Since Denali auto-loads all of app/* into the container, we can keep the app/mailers folder structure.

You'll have to create that repo, I don't think I have the permissions.

I can't push to the new mailer repo.

Whoops - should be good to go now

Still nothing lol

See https://github.com/denali-js/denali-mailer

Closing in favor of #194


Migrations not generated if only annotations change

Generally, when I change something in the schema, a migration can be performed. I'm using SQLite. So, when I change a column to be nullable, the migration will fail (which I expect) because SQLite does not support changing a column from NULL to NOT NULL and vice versa. But I recently changed my schema using an annotation so that an existing foreign key became ON DELETE CASCADE:
It was:
edge.To("jobs", Job.Type)

Then I changed it to:
edge.To("jobs", Job.Type).Annotations(entsql.Annotation{OnDelete: entsql.Cascade}),

I did these things:

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

I made the above change
I re-run the code generator with ent generate --feature sql/upsert ./ent/schema && go build
I start the program, which run the migrations with: client.Schema.Create(context.Background())
The sqlite schema remains exactly the same. The program goes to delete something that refers to a Job, and it fails because of a foreign key constraint.
Suffering ensues, but as the Buddha is often misquoted as saying, life is suffering.

however

If I delete the database and run the program, the cascade is added and works fine. So the ent migrator doesn't add the CASCADE to an existing foreign key.

Expected Behavior 🤔
If the underlying database supports changing the ON DELETE action for a foreign key, then it should do that. If it doesn't, then I should get an error telling me that ent can't apply such a change (sqlite falls into this category of databases whose ALTER TABLE can't do this).
Steps to Reproduce 🕹
See above
Your Environment 🌎

Tech
Version

Go
1.18

Ent
v0.10.1

Database
sqlite

Driver
https://github.com/mattn/go-sqlite3

Thanks for making such an amazing project! It's really improved my life overall.

Closing because the suggestion above should solve the issue, but please feel free to reopen or join our Discord server if you still need help with this 😎


There are no devices connected. Review your USB connection and try again.

I'm getting this error over and over.
08:35:15 Android WiFi ADB: There are no devices connected. Review your USB connection and try again.
08:35:27 Adb connection Error:Se ha forzado la interrupción de una conexión existente por el host remoto
08:35:28 Connection attempts: 1

Using Windows 10, AS 1.4 and One plus One device.

Same issue. Mac OS X 10.11.1 , Nexus 5 , AS 1.4 stable channel.
Android WiFi ADB: There are no devices connected. Review your USB connection and try again.

@MiguelCatalan @johnwatsondev  can you try to execute this commands and paste the output here?
adb tcpip 5555
adb connect <IP_ADDRESS>
Replace <IP_ADDRESS> with the IP assigned to your device.

Thanks!

@pedrovgs

@pedrovgs after running the first command
PS C:\Users\something> adb tcpip 5555
adb server is out of date.  killing...
* daemon started successfully *

And the plugin worked like charm

@johnwatsondev review your ADB installation.  There is something wrong there. I can't change the code of my plugin to get you adb installation working, sorry. I'm closing this issue.

@MiguelCatalan AFAIK you know java and could be awesome if you reproduce the bug again and send me a PR with the fix. It's quite simple. What do you think?

@pedrovgs Sorry about that i didn't read the Usage carefully. I didn't connect my device through cable with AS...  My fault. :sob:

No problem @johnwatsondev


Getting error

I am getting this error when using this tool,
Error parsing key
Error loading credentials
Am i doing something wrong?

When passing keys to `aea`, they need to be prefixed with `base64:`

Thanks it works!


Inference speed

The inference speed mentioned in the paper is 10.2 fps. In the codes,  the depth complement files have been provided. So how do we get the real inference speed.

The latency reported in the paper includes the depth completion network, you can refer to the PENet and TWISE for latency of depth completion network.

The latency reported in the paper includes the depth completion network, you can refer to the PENet and TWISE for latency of depth completion network.

Thank you for your reply.
Does the average processing time per frame of depth estimation network + average time per frame of detection network detection represent the final inference time.

Yes


Makes Spotify Blank

Recently it started simply making the entire Spotify blank, not sure if this is a spicetify issue or an issue with the theme in general

.

It is surely an issue on Spicetify's end, not mine

https://github.com/spicetify/spicetify-cli/issues/1483 @NYRI4

spicetify/spicetify-cli#1483 @NYRI4

that doesn't look like the same issue this person is having (this one is fully blank instead of partially), Nyria has already removed that part of the code 6 days ago

I have the same problem! And it's not only with this theme, any theme that I install comes with the same blank screen

It's a Spicetify issue, just reinstall Spotify.

I had the exact same issue.

It's a Spicetify issue, just reinstall Spotify.

This fixed it for me 👆🏽
$ spicetify restore
(update sptotify and spicetify with your package manager or however you install your programs)
$ spicetify --version
(make sure you are using version 2.9.2)
$ spotify --version
(make sure you are using at least version 1.1.80)
$ spicetify restore backup apply

Not sure about the spotify version number exactly, correct me if I'm wrong

Another Spicetify related issue.


GH-1137 avoid populating version second time during update and insert

Addressing #1137 issue. Jens @schauder, can you, please, review the changes.

Thanks for the PR. Most of it looks really good. There is only one major concern: We can't remove public classes, methods, or constructors without deprecating them first, except for major versions. So we should make those changes that the original signatures stay available but are deprecated.

Yes, you are right, I have forgotten about it :) I will fix this shortly, thank you very much for reviewing PR, appretiate it)

As requested, I have deprecated the api that will not be used anymore if we apply this change :) Jens @schauder, can you, please, take a look?)

Please rebase this on the current main branch and squash it into a single commit.

Over the course of exploring a possible design for GH-537 where AggregateChange represents the change plan via DbAction for multiple entities and JdbcAggregateChangeExecutionContext is capable of being used for multiple roots, I happened to explore a refactor that deals with this same concern but uses a different approach.
I wasn't previously aware of the issue that this PR closes, but since my changes also seem to address the extraneous constructor calls, I figured I would cross reference it here for possible consideration.

I'd like to go forward with the PR by @ctailor2
The result is easier to understand at least for me.
@Mikhail2048  I'm sorry that you put so much work into this before I turn around and go with a different PR. Your work on this, on previous and hopefully future PRs is still very much appreciated.
I leave this open for now until I can actually merge the other PR.

A pity, but OK, at the end of the day the goal is to make framework better :) Thank you fellows @schauder @ctailor2 !)


Programmatically get the manifest output

Would it be possible to use this plugin directly so that you can get the manifest output/object without having to write it to a file?
For example:
const ManifestPlugin = require('webpack-manifest-plugin');

plugins: [
    {
        apply: function(compiler) {
            const manifest = ManifestPlugin.getFromCompiler(compiler);

            // Do something with the manifest, e.g. write it to a service worker sw.js file
        }
    }
]

Our use case is that we want to write the manifest for use in a service worker file.
Maybe the generate option is useful here because if the compilation changes through watch then maybe that would be a better approach? Possibly related to: https://github.com/danethurber/webpack-manifest-plugin/issues/137

I'm interested in this functionality as well for a complex multi-entrypoint/multi-chunk build that can embed different functionality at runtime based on a small embed script. For that script to have access to the compiler output would be a ton of help. I recognize that I could accomplish this through a secondary build for the embed script that runs after the primary build, but I'd much rather avoid that complexity and be able to wrap it up under one.

@gdvsbp you may find this code useful... I've basically wrote our own plugin which generates a manifest file of the chunk information under a new file manifest.json - you can adapt the code to change the format or pick our specific chunks.
This is for Webpack 4, not sure if it needs to be adapted for later version of Webpack:
build/manifest.js
const path = require('path');

function GenerateManifest() {
    GenerateManifest.prototype.apply = function(compiler) {

    compiler.hooks.emit.tapAsync('generate-manifest-plugin', function(compilation, callback) {
        var manifest = {
            // Get output path without leading and trailing slashes
            path: compilation.outputOptions.publicPath.replace(/^\//, '').replace(/\/$/, ''),
            chunks: {},
            assets: {}
        };

        var getFileDetails = function(chunk, file) {
            return {
                path: file,
                ext: path.extname(file).substr(1)
            }
        };

        compilation.chunks.forEach(function(chunk) {
            if (chunk.isOnlyInitial()) {
                manifest.chunks[chunk.name] = chunk.files.map((file) => getFileDetails(chunk, file));
            }
        });

        var source = JSON.stringify(manifest);

        compilation.assets['manifest.json'] = {
            source: function() {
                return source;
            },

            size: function() {
                return source.length;
            }
        };

        callback();
    }.bind(this));
};

module.exports = GenerateManifest;

Output format example of manifest.json:
{
  "path": "dist-admin",
  "chunks": {
    "admin": [
      {
        "path": "admin-8ebaecbefb148a102400.css",
        "ext": "css"
      },
      {
        "path": "js/admin-6413be24c62724ad0bc1.js",
        "ext": "js"
      }
    ],
    "admin-tab": [
      {
        "path": "js/admin-tab-b232dd435ee11580f3c5.js",
        "ext": "js"
      }
    ],
    "vendor": [
      {
        "path": "js/vendor-003306aa5189662769bf.js",
        "ext": "js"
      }
    ]
  },
  "assets": {}
}

Usage:
const GenerateManifest = require('./build/manifest');

// Under plugins array in webpack add:
new GenerateManifest();

.... we personally use this manifest.json file for various things, such as cache invalidation, use in a service worker, etc.

Closing this as there are a few workarounds shared which are reasonable. If none of these workarounds are satisfactory, please open a new Feature issue.


Question: What is the most likely cause of Timeaccount drops?

I've started to get these in the console a while back
"Timeaccount fell below 10%"
And quickly after "Timeaccount zero, no more transmission possible"
And "TX lost, repeat it, buffer full", at which point sending (for example) dimming messages takes anywhere from 10 to 20 seconds to reach the device.
I'm guessing it might have to do with memory on the USB stick, but I know way to little about xcomfort to be confident.   Any suggestions are welcome.

This means that you are sending too many messages. The device can only transmit for a relatively short period in an hour, if you send too many messages your time account will be spent and the device will wait before sending more messages. You may have something that's updating light bulbs or similar too often.


Add enable/disable command for plugins

Add following feature:
patternlab enable --plugins=plugin-name1, plugin-name2
patternlab disable --plugins=plugin-name1, plugin-name2

@bmuenzenmeyer Is this a viable feature and par with any core functionality?

yes,
as long as by enable and disable, you setting the value inside patternlab-config.json per guidance in the example here: https://github.com/pattern-lab/plugin-node-tab#configuration

Cool. I will implement it as per spec. Thanks

Just had a second look at it … isn't it a bit verbose to just expose plugin-related logic on the config?
This way either the plugin itself has to
(a) return its default configuration or
(b) the CLI has to map that somehow or
(c) the user has to manually add it to the PL config
I prefer (a) … as this unties the CLI and user from knowing the exact config. Also if different plugins or plugin versions require diff config this would be the easiest way to make sure having a non-breaking setup.

Actually: The more I think about this the more I feel we should handle it like babel—let the user enable/config plugins. I am closing this for now


Output for IMPROVE_RESULT in wrong format.

Printing dict, should be single float.

Added fix to improve branch. Rebuilding and testing image.

Seems ok, testing with HPO

ok


Feature request. Request resized image

We need an option to get smaller image by specifying height or width.
Image for sure should be cached on server side.

Already done.


How to configure eslint and prettier?

Trying to configure the eslint and prettier, but there are many global variables defined. Can you please guide how to set up the same to support for vscode as a default editor

Hey @hansiemithun! 👋
Please, use the forum or our Discord server for this kind of question.
This is not an issue with Adonis nor in the scope of Adonis.
If you want to use eslint and prettier you must learn those tool and check their documentation first.


port dart2js Utf8Decoder acceleration to DDC

dart2js commit: https://github.com/dart-lang/sdk/commit/3836c70a8150bc33a695788deee346b940b40769
If the following changelog entry is committed, update from 'dart2js' to 'JavaScript': https://dart-review.googlesource.com/c/sdk/+/21526

https://dart-review.googlesource.com/#/c/sdk/+/54529


For application/pdf iterate over pages adding canvas to sequence per page

Two-stage implementations with a temp release.
For pdf resources.

Implement hack against current cantaloupe that passes ?page=99999 and parses error to get page number
Cantaloupe v5.0 custom delegate to add page count to image manifest info.json

Both will require creating and adding canvas to sequence per page.

Will resolve https://github.com/TAMULib/SAGE/issues/302

Hold off on merging until completion of #104


[TW#28036] Core  0 panic'ed in mdns_parse_packet

Environment

Development Kit:      M5Stack
Kit version (for WroverKit/PicoKit/DevKitC): -
Module or chip used:  ESP32
IDF version ESP-IDF v3.3-beta1-4-g23b6d40c5 and versions before!
Build System:         Make
Compiler version Toolchain version: crosstool-ng-1.22.0-80-g6c4433a
Compiler version: 5.2.0
Operating System:    macOS
Power Supply:          USB

Problem Description
I realized a small SmartHome ESP32-controller with connecting to Apple HomeKit. Homekit can read the values from ESP32 but every time the mdns-service crashed after a time.
Expected Behavior
Here is the crash report:
Important: The messages started with mdns_parse_packet are my new message!

mdns_parse_packet 5-X1
mdns_parse_packet 5-K1
mdns_parse_packet 5-K2
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x401b9463  PS      : 0x00060530  A0      : 0x801b9dc9  A1      : 0x3ffedd20
0x401b9463: mdns_parse_packet at /Users/my/esp/esp-idf/components/mdns/mdns.c:4283
A2      : 0x00000000  A3      : 0x00000010  A4      : 0x00000098  A5      : 0x3ffd5898
A6      : 0x3ffd5b8d  A7      : 0x3ffd5c25  A8      : 0x801b9455  A9      : 0x3ffedd00
A10     : 0x0000000a  A11     : 0x3ffd5b8d  A12     : 0x00000098  A13     : 0x00000001
A14     : 0x00060120  A15     : 0x00000010  SAR     : 0x00000010  EXCCAUSE: 0x0000001c  EXCVADDR: 0x00000004  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffa
Backtrace: 0x401b9463:0x3ffedd20 0x401b9dc6:0x3ffedda0 0x401b9e23:0x3ffeddd0 0x400918a1:0x3ffede00
0x401b9463: mdns_parse_packet at /Users/my/esp/esp-idf/components/mdns/mdns.c:4283
0x401b9dc6: _mdns_execute_action at /Users/my/esp/esp-idf/components/mdns/mdns.c:4283
0x401b9e23: _mdns_service_task at /Users/my/esp/esp-idf/components/mdns/mdns.c:4283
0x400918a1: vPortTaskWrapper at /Users/my/esp/esp-idf/components/freertos/port.c:403
CPU halted.

Actual Behavior
Steps to reproduce and Code to reproduce this issue
Every time I started the app it crashed.
Here are the crash part in mdns.c:
void mdns_parse_packet(mdns_rx_packet_t * packet)
{
   static mdns_name_t n;
 ...
   } else if (ours) {
                    if (parsed_packet->questions && !parsed_packet->probe) {
                        _mdns_remove_parsed_question(parsed_packet, type, service);
                        continue;
                    }
                    //detect collision (-1=won, 0=none, 1=lost)
                    int col = 0;
                    if (clas > 1) {
                        col = 1;
                    } else if (!clas) {
                        col = -1;
                    } else {
          printf("HERE mdns_parse_packet HERE!\n");
          printf("clas=%d len=%d\n", clas, data_len);
          printf("HEXDUMP: ");
          for (int j=0; j<data_len; j++)
            printf("%02x ", (uint8_t) *(data_ptr+j) );
          printf("\n\n ASCIIDUMP:>");
          for (int j=0; j<data_len; j++)
            printf("%c", (uint8_t) *(data_ptr+j) );
          printf("<\n\n");
          /  goto clear_rx_packet; //dirty workaround
                        col = _mdns_check_txt_collision(service->service, data_ptr, data_len);
                    }
                    if (col && !_mdns_server->interfaces[packet->tcpip_if].pcbs[packet->ip_protocol].probe_running) {
          printf("mdns_parse_packet NEXT STEP\n");
                        do_not_reply = true;
                        _mdns_init_pcb_probe(packet->tcpip_if, packet->ip_protocol, &service, 1, true);
                    } else if (ttl > 2250 && !col && !parsed_packet->authoritative && !parsed_packet->probe && !parsed_packet->questions && !_mdns_server->interfaces[packet->tcpip_if].pcbs[packet->ip_protocol].probe_running) {
                        _mdns_remove_scheduled_answer(packet->tcpip_if, packet->ip_protocol, type, service);
                    }
                }

Debug Logs
The output before the error occurred is:
mdns_parse_packet START
HERE mdns_parse_packet HERE!
clas=1 len=152
HEXDUMP: 97 4c 6f 78 4c 49 56 45 3a 20 2a 34 44 36 39 36 45 36 39 37 33 36 35
37 32 37 36 36 35 37 32 20 31 39 32 2e 31 36 38 2e 30 2e 36 32 3a 38 30 20 35
30 34 46 39 34 31 30 31 46 33 38 20 31 30 2e 30 2e 39 2e 32 34 20 49 50 76 36
3a 2c 30 33 64 38 30 32 34 31 3a 39 30 30 30 38 32 32 2f 4f 2c 30 34 64 38 30
37 62 33 3a 39 30 30 30 39 31 35 2f 4f 2c 30 36 64 38 30 31 63 32 3a 39 30 30
30 38 32 32 2f 4f 2c 30 31 64 38 31 66 31 31 3a 39 30 30 30 38 32 32 2f 4f

 ASCIIDUMP: ?LoxLIVE: *4D696E69736572766572 <IP_ADDRESS>:80 504F94101F38
<IP_ADDRESS> IPv6:,03d80241:9000822/O,04d807b3:9000915/
O,06d801c2:9000822/O,01d81f11:9000822/O

mdns_parse_packet NEXT STEP

Other items if possible
The message which produced the error is a message from an uninvolved device called "loxone".
My dirty workaround is to stop the processing an goto  "clear_rx_packet".

Hi @GermanSheepDog,
Thanks for reporting this issue. It looks like the "loxone" packet contains either standalone TXT or a TXT entry ahead of PTR/STR records and mdns parser is not resistant to this condition and needs to be fixed.
Just to confirm it is the case can you try to apply this condition
if (service) {
    col = _mdns_check_txt_collision(service->service, data_ptr, data_len);
}

to the original call of _mdns_check_txt_collision?
Also it would be helpful if you can provide entire packet that is causing this issue. Could be as pcap (if you can do wireshark in your network) or an output printf the same way you provided the section above. It is possible to inject the provided section only, but that causing crashes only to releases 3.1 and 3.2, interestingly it works with latest master/3.3 which means we miss something. It'd be highly appreciated if you could prove the entire packet (=udp payload only).
Thanks for your help,
David


Adding object relationships

I have created an annotation called a Relationship which allows for the cascading of saving between on object and another. This is useful for complex schemas where joins are necessary. Currently it only supports Lazy loading which can be observed in the the example with "Book, Author, and Page".  This shows how the object relationships is used.
I have chosen to use a join table for all object relationships. I am aware that this is not standard practice except for ManyToMany relationships however I have decided to do this based on the idea that model relationships to change. If a relationship is defined as a OneToOne and eventually needs to become a ManyToOne or ManyToMany, then this would be a significant issue to try to accomplish in an onUpgrade script.
The main changes to look for are the Relationship.java annotation I added as well as the ReflectionUtils.java changes, SugarObject.save() and SchemaGenerator.java which now Generates the join tables as well.

thanks @mbag102 , i'll review it and get back.

I like it! :+1:

Really hoping this support will be added to manage lib soon.


support for email addresses over 30 characters

trigger build

trigger build

tests also failing on jenkins for master, but they're passing locally so I'm going to continue with the hotfix and fix tests later


App Configuration: publish 2020-07-01-preview specs

The official docs for App Configuration use the 2020-07-01-preview version to define an ARM template with keyValues. Why is this spec not published yet?
Our customers (Pulumi Azure NextGen provider) are eager to use it. Please publish the specs.

Fixed by #10224


affine: init at 0.13.1

Description of changes
Add AFFiNE, an open-source, all-in-one workspace and an operating system for all the building blocks that assemble your knowledge base and much more -- wiki, knowledge management, presentation and digital assets.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Hey thank you for this, this is very nice ! Do you have plans for makign a service, is there anything you need help with ?

Hey thank you for this, this is very nice ! Do you have plans for makign a service, is there anything you need help with ?

Hi, thanks for your kind words! I currently don't have plans to add this, but feel free to submit a PR if you'd like to contribute.