text:
DBeaver crashes on startup (macOS Mojave)

System information:

macOS version 10.14.3 (18D42)
DBeaver version 5.3.5
Java version "1.8.0_121"

Problem
Cannot open DBeaver
Steps to reproduce, if exist:

Open DBeaver from GUI DBeaver.app
Open /Applications/DBeaver.app/Contents/MacOS/dbeaver

logs when open from CLI
Contents/MacOS » ./dbeaver
2019-02-18 19:54:52.289 - Create display
2019-02-18 19:54:52.636 - > Start org.jkiss.dbeaver.core [5.3.5.201902180650]
2019-02-18 19:54:52.640 - DBeaver 5.3.5.201902180650 is starting
2019-02-18 19:54:52.641 - OS: Mac OS X 10.14.3 (x86_64)
2019-02-18 19:54:52.642 - Java version: 1.8.0_121 by Oracle Corporation (64bit)
2019-02-18 19:54:52.643 - Install path: '/Applications/DBeaver.app/Contents/Eclipse'
2019-02-18 19:54:52.644 - Instance path: 'file:/Users/achaipreecha/.dbeaver4/'
2019-02-18 19:54:52.645 - Memory available 77Mb/910Mb
2019-02-18 19:54:52.660 - Starting RMI server at 51440
2019-02-18 19:54:52.736 - Run workbench
2019-02-18 19:54:52.786 - > Start org.eclipse.e4.ui.workbench.swt [0.14.300.v20180906-1121]
2019-02-18 19:54:52.789 - > Start org.eclipse.e4.core.services [2.1.200.v20180817-1215]
2019-02-18 19:54:52.791 - > Start org.eclipse.e4.core.contexts [1.7.100.v20180817-1215]
2019-02-18 19:54:52.798 - > Start org.eclipse.e4.ui.services [1.3.200.v20180906-1121]
2019-02-18 19:54:52.826 - > Start org.eclipse.e4.ui.di [1.2.300.v20180906-1121]
2019-02-18 19:54:52.859 - > Start org.eclipse.emf.common [2.15.0.v20180723-1316]
2019-02-18 19:54:52.875 - > Start org.eclipse.emf.ecore [2.15.0.v20180722-1159]
2019-02-18 19:54:52.925 - > Start org.eclipse.emf.ecore.xmi [2.15.0.v20180706-1146]
2019-02-18 19:54:53.055 - > Start org.eclipse.core.filesystem [1.7.200.v20180828-0158]
2019-02-18 19:54:53.089 - > Start org.eclipse.core.resources [3.13.100.v20180828-0158]
2019-02-18 19:54:53.220 - > Start org.eclipse.e4.ui.workbench.addons.swt [1.3.200.v20180828-0227]
2019-02-18 19:54:53.229 - > Start org.eclipse.core.expressions [3.6.200.v20180817-1401]
2019-02-18 19:54:53.241 - > Start org.eclipse.e4.ui.workbench.renderers.swt [0.14.300.v20180828-0227]
2019-02-18 19:54:53.347 - > Start org.eclipse.e4.ui.bindings [0.12.200.v20180828-0227]
2019-02-18 19:54:53.388 - > Start org.eclipse.e4.core.di.extensions [0.15.200.v20180817-1215]
2019-02-18 19:54:53.400 - > Start org.eclipse.ui.ide [3.14.100.v20180828-1350]
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:141)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:106)
	at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.<init>(BasicSplashHandler.java:53)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
	at org.eclipse.ui.splash.BasicSplashHandler.getContent(BasicSplashHandler.java:240)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.initVisualization(DBeaverSplashHandler.java:112)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.init(DBeaverSplashHandler.java:69)
	at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:833)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:849)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:600)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:161)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-18 19:54:53.534 - Internal error in workbench lifecycle
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:141)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:106)
	at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.<init>(BasicSplashHandler.java:53)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:608)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:161)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:141)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:106)
	at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.<init>(BasicSplashHandler.java:53)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:179)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-18 19:54:53.584 - DBeaver is stopping
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:141)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:106)
	at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.<init>(BasicSplashHandler.java:53)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.shutdown(DBeaverApplication.java:312)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:182)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-18 19:54:53.608 - Stop RMI server
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:141)
	at org.eclipse.jface.wizard.ProgressMonitorPart.<init>(ProgressMonitorPart.java:106)
	at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.<init>(BasicSplashHandler.java:53)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.rpc.DBeaverInstanceServer.stopInstanceServer(DBeaverInstanceServer.java:185)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.shutdown(DBeaverApplication.java:321)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:182)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-18 19:54:53.662 - < Stop org.jkiss.dbeaver.ext.mssql.ui [1.0.2.201902180650]
java.lang.IllegalArgumentException: Argument not valid
	at org.eclipse.swt.SWT.error(SWT.java:4576)
	at org.eclipse.swt.SWT.error(SWT.java:4510)
	at org.eclipse.swt.SWT.error(SWT.java:4481)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:810)
	at org.eclipse.swt.widgets.Widget.checkParent(Widget.java:534)
	at org.eclipse.swt.widgets.Widget.<init>(Widget.java:142)
	at org.eclipse.swt.widgets.Control.<init>(Control.java:121)
	at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:76)
	at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:138)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.DBeaverApplication$BundleLoadListener.bundleChanged(DBeaverApplication.java:417)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:911)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
2019-02-18 19:54:53.663 - < Stop org.jkiss.dbeaver.ext.mssql [1.0.97.201902180650]
java.lang.IllegalArgumentException: Argument not valid
	at org.eclipse.swt.SWT.error(SWT.java:4576)
	at org.eclipse.swt.SWT.error(SWT.java:4510)
	at org.eclipse.swt.SWT.error(SWT.java:4481)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:810)
	at org.eclipse.swt.widgets.Widget.checkParent(Widget.java:534)
	at org.eclipse.swt.widgets.Widget.<init>(Widget.java:142)
	at org.eclipse.swt.widgets.Control.<init>(Control.java:121)
	at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:76)
	at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:138)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.DBeaverApplication$BundleLoadListener.bundleChanged(DBeaverApplication.java:417)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:911)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
2019-02-18 19:54:53.663 - < Stop org.jkiss.dbeaver.ext.oracle [2.1.88.201902180650]
java.lang.IllegalArgumentException: Argument not valid
	at org.eclipse.swt.SWT.error(SWT.java:4576)
	at org.eclipse.swt.SWT.error(SWT.java:4510)
	at org.eclipse.swt.SWT.error(SWT.java:4481)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:810)
	at org.eclipse.swt.widgets.Widget.checkParent(Widget.java:534)
	at org.eclipse.swt.widgets.Widget.<init>(Widget.java:142)
	at org.eclipse.swt.widgets.Control.<init>(Control.java:121)
	at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:76)
	at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:138)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.DBeaverApplication$BundleLoadListener.bundleChanged(DBeaverApplication.java:417)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:911)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
2019-02-18 19:54:53.664 - < Stop org.jkiss.dbeaver.ext.ui.tipoftheday [1.0.9.201902180650]
java.lang.IllegalArgumentException: Argument not valid
	at org.eclipse.swt.SWT.error(SWT.java:4576)
	at org.eclipse.swt.SWT.error(SWT.java:4510)
	at org.eclipse.swt.SWT.error(SWT.java:4481)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:810)
	at org.eclipse.swt.widgets.Widget.checkParent(Widget.java:534)
	at org.eclipse.swt.widgets.Widget.<init>(Widget.java:142)
	at org.eclipse.swt.widgets.Control.<init>(Control.java:121)
	at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:76)
	at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)
	at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:138)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.getActiveMonitor(DBeaverSplashHandler.java:48)
	at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.showMessage(DBeaverSplashHandler.java:153)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.lambda$0(DBeaverApplication.java:130)
	at org.jkiss.dbeaver.Log.debugMessage(Log.java:155)
	at org.jkiss.dbeaver.Log.debug(Log.java:143)
	at org.jkiss.dbeaver.Log.debug(Log.java:137)
	at org.jkiss.dbeaver.core.application.DBeaverApplication$BundleLoadListener.bundleChanged(DBeaverApplication.java:417)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:911)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)

I tried downgrade to previous versions, still does not work.
Tried to install with (pkg installer + JRE), does not work as well.
This workaround also does not work.
Any suggestion?

Seems similar to #4872
Could you try to start with -nosplash command line parameter?

It opens with these message on the logs
Contents/MacOS » ./dbeaver -nosplash
2019-02-20 09:57:50.969 - Create display
2019-02-20 09:57:51.420 - > Start org.jkiss.dbeaver.core [5.3.5.201902180650]
2019-02-20 09:57:51.426 - DBeaver 5.3.5.201902180650 is starting
2019-02-20 09:57:51.427 - OS: Mac OS X 10.14.3 (x86_64)
2019-02-20 09:57:51.428 - Java version: 1.8.0_152 by Oracle Corporation (64bit)
2019-02-20 09:57:51.429 - Install path: '/Applications/DBeaver.app/Contents/Eclipse'
2019-02-20 09:57:51.430 - Instance path: 'file:/Users/achaipreecha/.dbeaver4/'
2019-02-20 09:57:51.431 - Memory available 117Mb/910Mb
2019-02-20 09:57:51.449 - Starting RMI server at 59166
2019-02-20 09:57:51.587 - Run workbench
2019-02-20 09:57:51.605 - > Start org.eclipse.e4.ui.workbench.swt [0.14.300.v20180906-1121]
2019-02-20 09:57:51.607 - > Start org.eclipse.e4.core.contexts [1.7.100.v20180817-1215]
2019-02-20 09:57:51.609 - > Start org.eclipse.e4.core.services [2.1.200.v20180817-1215]
2019-02-20 09:57:51.620 - > Start org.eclipse.e4.ui.services [1.3.200.v20180906-1121]
2019-02-20 09:57:51.669 - > Start org.eclipse.e4.ui.di [1.2.300.v20180906-1121]
2019-02-20 09:57:51.716 - > Start org.eclipse.emf.common [2.15.0.v20180723-1316]
2019-02-20 09:57:51.737 - > Start org.eclipse.emf.ecore [2.15.0.v20180722-1159]
2019-02-20 09:57:51.802 - > Start org.eclipse.emf.ecore.xmi [2.15.0.v20180706-1146]
2019-02-20 09:57:51.971 - > Start org.eclipse.core.filesystem [1.7.200.v20180828-0158]
2019-02-20 09:57:52.010 - > Start org.eclipse.core.resources [3.13.100.v20180828-0158]
2019-02-20 09:57:52.137 - > Start org.eclipse.e4.ui.workbench.addons.swt [1.3.200.v20180828-0227]
2019-02-20 09:57:52.149 - > Start org.eclipse.core.expressions [3.6.200.v20180817-1401]
2019-02-20 09:57:52.162 - > Start org.eclipse.e4.ui.workbench.renderers.swt [0.14.300.v20180828-0227]
2019-02-20 09:57:52.297 - > Start org.eclipse.e4.ui.bindings [0.12.200.v20180828-0227]
2019-02-20 09:57:52.347 - > Start org.eclipse.e4.core.di.extensions [0.15.200.v20180817-1215]
2019-02-20 09:57:52.361 - > Start org.eclipse.ui.ide [3.14.100.v20180828-1350]
2019-02-20 09:57:52.613 - > Start org.eclipse.e4.ui.css.swt [0.13.200.v20180828-0227]
2019-02-20 09:57:53.200 - > Start org.eclipse.e4.ui.css.swt.theme [0.12.100.v20180828-0227]
2019-02-20 09:57:53.585 - Initializing DBeaver 5.3.5
2019-02-20 09:57:53.586 - Host plugin: org.jkiss.dbeaver.core.application 5.3.5.201902180650
2019-02-20 09:57:53.587 - Initialize Core...
2019-02-20 09:57:53.605 - Can't find BC security provider. Use default JCE.
2019-02-20 09:57:53.606 - BouncyCastle not registered, using the default JCE provider
2019-02-20 09:57:53.725 - > Start org.eclipse.team.core [3.8.300.v20180827-1041]
2019-02-20 09:57:53.747 - > Start org.jkiss.dbeaver.ui.navigator [1.0.3.201902180650]
2019-02-20 09:57:53.835 - Total database drivers: 72 (69)
2019-02-20 09:57:53.867 - > Start org.eclipse.equinox.security [1.2.500.v20180827-1235]
2019-02-20 09:57:53.882 - > Start org.eclipse.ui.net [1.3.300.v20180827-1041]
2019-02-20 09:57:53.883 - Proxy service 'org.eclipse.core.net.proxy.IProxyService' loaded
2019-02-20 09:57:53.884 - > Start org.eclipse.core.net [1.3.300.v20180827-1041]
2019-02-20 09:57:53.886 - Core initialized (299ms)
2019-02-20 09:57:54.016 - Configure workbench window
2019-02-20 09:57:54.026 - > Start org.eclipse.help [3.8.200.v20180821-0700]
2019-02-20 09:57:54.372 - Create actions
2019-02-20 09:57:54.374 - Disable Eclipse action set 'org.eclipse.ui.edit.text.actionSet.annotationNavigation'
2019-02-20 09:57:54.398 - Disable Eclipse action set 'org.eclipse.ui.WorkingSetActionSet'
2019-02-20 09:57:54.440 - > Start org.eclipse.ui.editors [3.11.200.v20180822-1511]
2019-02-20 09:57:54.441 - > Start org.eclipse.core.filebuffers [3.6.300.v20180822-1339]
2019-02-20 09:57:54.671 - > Start org.eclipse.search [3.11.300.v20180822-1339]
2019-02-20 09:57:54.698 - > Start org.eclipse.ui.workbench.texteditor [3.11.100.v20180824-1030]
2019-02-20 09:57:54.710 - Initialize workbench window
2019-02-20 09:57:54.717 - Finish initialization
2019-02-20 09:57:54.781 - > Start org.eclipse.equinox.p2.core [2.5.100.v20180822-1532]
2019-02-20 09:57:54.784 - > Start org.eclipse.equinox.p2.operations [2.5.100.v20180822-1302]
2019-02-20 09:57:54.788 - > Start org.eclipse.equinox.p2.engine [2.6.100.v20180822-1302]
2019-02-20 09:57:54.795 - > Start org.eclipse.equinox.p2.metadata [2.4.100.v20180822-1302]
2019-02-20 09:57:54.809 - > Start org.eclipse.equinox.p2.ui.sdk.scheduler [1.4.100.v20180827-1122]
2019-02-20 09:57:54.812 - > Start org.eclipse.equinox.p2.updatechecker [1.2.100.v20180827-1122]
2019-02-20 09:57:54.816 - > Start org.eclipse.equinox.p2.metadata.repository [1.3.100.v20180822-1302]
2019-02-20 09:57:54.818 - > Start org.eclipse.equinox.p2.repository [2.4.100.v20180822-1354]
2019-02-20 09:57:55.139 - > Start org.jkiss.dbeaver.ext.sample.database [1.0.40.201902180650]
2019-02-20 09:57:55.143 - > Start org.jkiss.dbeaver.ext.ui.tipoftheday [1.0.9.201902180650]
2019-02-20 09:57:55.171 - Event loop exception
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.jface.dialogs.Dialog.initializeDialogUnits(Dialog.java:937)
	at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:769)
	at org.jkiss.dbeaver.ext.ui.tipoftheday.ShowTipOfTheDayDialog.createContents(ShowTipOfTheDayDialog.java:76)
	at org.eclipse.jface.window.Window.create(Window.java:429)
	at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1099)
	at org.jkiss.dbeaver.ui.dialogs.BaseDialog.create(BaseDialog.java:72)
	at org.eclipse.jface.window.Window.open(Window.java:786)
	at org.jkiss.dbeaver.ext.ui.tipoftheday.ShowTipOfTheDayHandler.showTipOfTheDayDialog(ShowTipOfTheDayHandler.java:66)
	at org.jkiss.dbeaver.ext.ui.tipoftheday.ShowTipOfTheDayHandler.showTipOfTheDay(ShowTipOfTheDayHandler.java:51)
	at org.jkiss.dbeaver.ext.ui.tipoftheday.TipOfTheDayInitializer.initializeWorkbenchWindow(TipOfTheDayInitializer.java:16)
	at org.jkiss.dbeaver.core.application.ApplicationWorkbenchWindowAdvisor.lambda$1(ApplicationWorkbenchWindowAdvisor.java:242)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4068)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3735)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:161)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-20 09:57:55.229 - > Start org.eclipse.equinox.p2.ui [2.5.200.v20180822-1357]
2019-02-20 09:57:57.779 - Open [https://dbeaver.io/product/version.xml]
2019-02-20 09:58:29.872 - Event loop exception
java.lang.NullPointerException
	at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:177)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:138)
	at org.eclipse.swt.widgets.TableColumn.pack(TableColumn.java:545)
	at org.eclipse.e4.ui.bindings.internal.KeyAssistDialog.createTableDialogArea(KeyAssistDialog.java:347)
	at org.eclipse.e4.ui.bindings.internal.KeyAssistDialog.createDialogArea(KeyAssistDialog.java:287)
	at org.eclipse.jface.dialogs.PopupDialog.createContents(PopupDialog.java:682)
	at org.eclipse.jface.window.Window.create(Window.java:429)
	at org.eclipse.e4.ui.bindings.internal.KeyAssistDialog.open(KeyAssistDialog.java:502)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.openKeyAssistShell(KeyBindingDispatcher.java:508)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.lambda$0(KeyBindingDispatcher.java:490)
	at org.eclipse.swt.widgets.Display.runTimers(Display.java:4266)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3724)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
	at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:161)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
2019-02-20 09:58:57.598 - DBeaver is stopping
2019-02-20 09:58:57.600 - Stop RMI server
2019-02-20 09:58:57.621 - < Stop org.jkiss.dbeaver.ext.mssql.ui [1.0.2.201902180650]
2019-02-20 09:58:57.621 - < Stop org.jkiss.dbeaver.ext.mssql [1.0.97.201902180650]
2019-02-20 09:58:57.622 - < Stop org.jkiss.dbeaver.ext.oracle [2.1.88.201902180650]
2019-02-20 09:58:57.622 - < Stop org.jkiss.dbeaver.ext.ui.tipoftheday [1.0.9.201902180650]
2019-02-20 09:58:57.647 - Shutdown Core...
2019-02-20 09:58:57.854 - Shutdown completed in 207ms

But the application is unusable, cannot create a new connection, etc.

This is a bug in Eclipse platform (https://bugs.eclipse.org/bugs/show_bug.cgi?id=540357)
It is somehow related to light/dark themes switch. It happens only on some Macs (e.g. it works fine on our mac air with Dark theme and on macbook with light theme).
This should be fixed in the next platform version (this spring). Unfortunately I can't say what exactly causes this issue. And I don't know any workaround  :(

This is a bug in Eclipse platform (bugs.eclipse.org/bugs/show_bug.cgi?id=540357)
It is somehow related to light/dark themes switch. It happens only on some Macs (e.g. it works fine on our mac air with Dark theme and on macbook with light theme).
This should be fixed in the next platform version (this spring). Unfortunately I can't say what exactly causes this issue. And I don't know any workaround :(

Very weird issue, does not work with either light nor dark for me :/

Updated OSX from 10.14.4 to 10.14.5 yesterday. DBeaver Community version 6.0.4 crashes on start up with UI. It was fine before the OSX update.
If start with terminal ,
$ /Applications/DBeaver.app/Contents/MacOS/dbeaver
Segmentation fault: 11

Not sure it is the same issue or not.

For me, the root cause of this issue is that I was using macOS Mojave with Light Theme with Dark Menu Bar and Dock.
Then I reverted the change, i.e., defaults write -g NSRequiresAquaSystemAppearance -bool No
DBeaver starts crashing since I reverted.
I have to enable it back to solve the problem.
Now it works fine with new updates also.
Hope this help 🙂

Ok, I don't have NSRequiresAquaSystemAppearance set at all.
$ defaults read -g | grep NSRequiresAquaSystemAppearance
$

After set it to No and Yes, it still have the same issue.
$ defaults write -g NSRequiresAquaSystemAppearance -bool yes
$ defaults read -g | grep NSRequiresAquaSystemAppearance
    NSRequiresAquaSystemAppearance = 1;

Guess my issue is different from yours.

Ok, I had the same NullPointerException as the thread creator. After executing the following it started normally:
defaults write -g NSRequiresAquaSystemAppearance -bool Yes
Mavbe this helps someone.

Ok, I had the same NullPointerException as the thread creator. After executing the following it started normally:
defaults write -g NSRequiresAquaSystemAppearance -bool Yes
Mavbe this helps someone.

alhamdulillah, solved for me..

Meanwhile I've found out that this parameter is not set in a freshly installed MacOS. So you have to remove it with
defaults remove -g NSRequiresAquaSystemAppearance
After this reboot. It helped me on other issue with VMware Fusion and Apache Directory Studio too!

Updated OSX from 10.14.4 to 10.14.5 yesterday. DBeaver Community version 6.0.4 crashes on start up with UI. It was fine before the OSX update.
If start with terminal ,
$ /Applications/DBeaver.app/Contents/MacOS/dbeaver
Segmentation fault: 11

Not sure it is the same issue or not.

I had the same issue and trying to change the defaults of system appearance did not solve the crash on startup at all.

Updated OSX from 10.14.4 to 10.14.5 yesterday. DBeaver Community version 6.0.4 crashes on start up with UI. It was fine before the OSX update.
If start with terminal ,
$ /Applications/DBeaver.app/Contents/MacOS/dbeaver
Segmentation fault: 11

Not sure it is the same issue or not.

I had the same issue and trying to change the defaults of system appearance did not solve the crash on startup at all.

First time seeing that issue, Mine seems to be fixed now after the Catalina update I have no more issues.

authors: Kiza RickS-C137 alminisl attomos brdacost cecepabufatih serge-rider


text:
[CT-2862] [Bug] Vars are passed by reference in models, which causes issues with compile+run steps

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I'm not sure if this is by design, but I couldn't find any other issues relating to it and no docs on the topic, so it may just be this needs calling out somewhere to save people the trouble of discovering themselves.
Basically, it seems like dbt variables are passed to the environment by reference, rather than by value. For the vast majority of use cases this is probably fine and makes no difference, however in a case where the variable is a list and a model or macro alters this list, this is done both in the compile and the run steps of dbt run, which means the action is (incorrectly) taken twice.
Using the .copy() method avoids this issue, however I couldn't find it documented obviously anywhere.
Expected Behavior
This variable would be passed by value, so that alterations done in the compile step are not impacting the run step.
Steps To Reproduce

Start with a new project, create a model called test.sql with the following content:{% set x = var('test_list', []) %}
{{ log('x: ' ~ x, info=True) }}
{% do x.append(1) %}
{% do x.append(2) %}

{{ log('x: ' ~ x, info=True) }}

{% set y = var('test_list2', []) %}

{{ log('y: ' ~ y, info=True) }}
{{ test_macro(y) }}
{{ test_macro(y) }}

{{ log('y: ' ~ y, info=True) }}

{% set z = var('test_list3', []).copy() %}
{{ log('z: ' ~ z, info=True) }}
{% do z.append(1) %}
{% do z.append(2) %}

{{ log('z: ' ~ z, info=True) }}

select 1 as a

Create a macro called test_macro with the following content:{% macro test_macro(my_list) %}
  {% do my_list.append('y') %}
{% endmacro %}

Add the following to dbt_project.yml:vars:
  test_list: []
  test_list2: []
  test_list3: []

Do dbt run, see the first two variables are updated twice.

Relevant log output
09:35:18  Running with dbt=1.5.1
09:35:18  Unable to do partial parsing because a project config has changed
09:35:19  x: []
09:35:19  x: [1, 2]
09:35:19  y: []
09:35:19  y: ['y', 'y']
09:35:19  z: []
09:35:19  z: [1, 2]
09:35:19  Found 1 model, 0 tests, 0 snapshots, 0 analyses, 308 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
09:35:19
09:35:19  Concurrency: 1 threads (target='postgres')
09:35:19
09:35:19  1 of 1 START sql view model dbt_ryan.test ...................................... [RUN]
09:35:19  x: [1, 2]
09:35:19  x: [1, 2, 1, 2]
09:35:19  y: ['y', 'y']
09:35:19  y: ['y', 'y', 'y', 'y']
09:35:19  z: []
09:35:19  z: [1, 2]
09:35:19  1 of 1 OK created sql view model dbt_ryan.test ................................. [CREATE VIEW in 0.07s]
09:35:19
09:35:19  Finished running 1 view model in 0 hours 0 minutes and 0.18 seconds (0.18s).
09:35:19
09:35:19  Completed successfully
09:35:19
09:35:19  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Environment
- OS: MacOS
- Python: 3.9.13
- dbt: 1.5.1

Which database adapter are you using with dbt?
No response
Additional Context
It may be this just would benefit from being documented with the copy() workaround, but I'm not sure if this is the intended behaviour or not. Another alternative workaround is to use the {% if execute %} block, but it wasn't clear you should do this for list variables.

This is a fun one! Two things going on here:

dbt renders complex Jinja twice, once at parse time and again at "execute" time (hence why if execute works)
dbt returns the actual Python object for the variable to the Jinja context, rather than a copy of its value

https://github.com/dbt-labs/dbt-core/blob/6130a6e1d0d29b257fbcd1b17fcd730383d73ce0/core/dbt/context/base.py#L163-L173
If I update that to:
    def get_rendered_var(self, var_name):
        from copy import copy
        raw = copy(self._merged[var_name])

It seems to resolve this issue:
$ dbt --no-partial-parse run
10:35:22  Running with dbt=1.7.0-a1
10:35:23  Registered adapter: postgres=1.7.0-a1
10:35:23  x: []
10:35:23  x: [1, 2]
10:35:23  y: []
10:35:23  y: ['y', 'y']
10:35:23  z: []
10:35:23  z: [1, 2]
10:35:23  Found 1 model, 1 seed, 0 sources, 0 exposures, 0 metrics, 353 macros, 0 groups, 0 semantic models
10:35:23
10:35:23  Concurrency: 5 threads (target='dev')
10:35:23
10:35:23  1 of 1 START sql view model dbt_jcohen.test .................................... [RUN]
10:35:23  x: []
10:35:23  x: [1, 2]
10:35:23  y: []
10:35:23  y: ['y', 'y']
10:35:23  z: []
10:35:23  z: [1, 2]
10:35:23  1 of 1 OK created sql view model dbt_jcohen.test ............................... [CREATE VIEW in 0.10s]
10:35:23
10:35:23  Finished running 1 view model in 0 hours 0 minutes and 0.23 seconds (0.23s).
10:35:23
10:35:23  Completed successfully
10:35:23
10:35:23  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

As a general practice, we should try to avoid having the special values that we add to the Jinja context be things that users can mutate with custom code.
@gshank feels like you might have a thought about this one :)

@gshank Did you get a chance to take a look at this please?

I think the correct workaround is to use the {% if execute %} block, so I'm going to close this out.
We can certainly add better docs here, where do you think would be the best spot? Some ideas:

https://docs.getdbt.com/reference/dbt-jinja-functions/execute
https://docs.getdbt.com/docs/build/jinja-macros

If you have a specific spot in mind, feel free to open up an issue over in the docs site repo - https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose

source: gharchive/issue

repo: dbt-labs/dbt-core

license_type: permissive

license_source: github-api


text:
[CT-2997] Ability to test incremental models

Description
We should allow folks to add unit tests to incremental models
Acceptance criteria

Ability to test incremental models in both full refresh and incremental mode
Ability to specify the current status of an incremental model to test the incremental behavior
Ability to test the incremental behavior of models using incremental strategy that requires partitioning (e.g. insert overwrite in BigQuery)

A "current_actual" could define the current state of the model we're incrementing on, testing whether the incrementing works as expected.

@gshank please pull Ability to test the incremental behavior of models using incremental strategy that requires partitioning (e.g. insert overwrite in BigQuery) out into a separate ticket

2x2 = 4 acceptance tests for us to write as part of implementation:

{{ is_incremental() }} : True + False
{{ this }} fixture: provided or not

Here's how i'm imagining the spec for this:
unit-tests:
 - model: my_model
   tests:
    - name: test_name
      given:
      - input: this
         rows: ...

authors: MichelleArk gshank jtcohen6 martynydbt


text:
[CT-3554] Define SourceDefinition contract in dbt/artifacts

Housekeeping

[X] I am a maintainer of dbt-core

Short description
As part of an effort to move any ArtifactMixin subclasses upstream of other core modules into the top -level dbt/artifacts directory, we need to move Metric, which WritableManifest depends on.
Acceptance criteria
SourceDefinition (and its necessary dependencies) are moved to a new dbt/artifacts directory. dbt/artifacts should have no additional dependencies on dbt.core except for from contracts.nodes which are actively being refactored.
SourceDefinition should be split into data & functional interfaces, defined in dbt/artifacts in dbt/core respectively. Additionally, any inheritance hierarchy between concrete node classes should be flattened as part of this spike.
Should follow initial pattern set in https://github.com/dbt-labs/dbt-core/issues/9379
Impact to Other Teams
N/A - should be a refactor.
Will backports be required?
nope
Context
No response

Also blocked on #9505

authors: MichelleArk QMalcolm


text:
Unit test GraphQueue class

Housekeeping

[X] I am a maintainer of dbt-core

Short description
As part of our Robust Testing Initiative we want to create generalized fixtures for our unit tests to make writing unit tests easier. To that end we want to add or update unit some unit tests to utilize the new fixture. Currently the GraphQueue class is not unit tested at all. We could unit test by reusing the DiGraph fixture created in https://github.com/dbt-labs/dbt-core/issues/9871.
Acceptance criteria

There are unit tests for the GraphQueue class

Suggested Tests
The work is the tests
Impact to Other Teams
None
Will backports be required?
Narp
Context

This include testing the public interfaces.

The work @MichelleArk(Thanks!) did in #10129 accomplished this ticket.

authors: ChenyuLInx QMalcolm


text:
TEMP (for comparing changes!)

nothing to see here!

Assuming this was related to this slack thread, so going to close this as resolved!

source: gharchive/pull-request


text:
Fixes Jinja example in fromyaml docs page

Description & motivation
Adds missing % to Jinja example in the docs.
https://docs.getdbt.com/reference/dbt-jinja-functions/fromyaml#usage

Duplicated by: https://github.com/dbt-labs/docs.getdbt.com/pull/1230


text:
User develops override

What are you changing in this pull request and why?
New option in dbt Cloud to override the dbt version used for projects.

Add new Override dbt version section to Upgrade Core version in Cloud page
Create release note

Checklist

[x] Review the Content style guide so my content adheres to these guidelines.
[x] For docs versioning, review how to version a whole page and version a block of content.
[x] Needs review from product eng

Adding or removing pages (delete if not applicable):

[ ] Add/remove page in website/sidebars.js N/A autogenerated for release notes
[x] Provide a unique filename for new pages

thanks for reviewing, @ericbaumann !  i added another step to delete the override env var -- good flag!


text:
1.1.42 release notes

Description & motivation
To-do before merge
Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

FYI @schottj @runleonarun

FYI @schottj @runleonarun
I ran into trouble with the original SHA I was using so I had to do the release with a newer SHA and I updated the draft changelog text to reflect that. Wanted to give you a heads up in case you had already started reviewing the text before now.


text:
AVI mime type

I understand that you define AVI with following mime type:
public static final String VIDEO_AVI = BASE_TYPE_VIDEO + "/x-msvideo";

I also see this mime type in various lists (related to Android) but when I actually work with AVI files on Android, I usually have to use video/avi to:

Filter items in MediaStore as indexed AVI files are stored with this mime type
Filter files in native SAF file chooser as it also recognizes only video/avi
1st party apps like Files by Google also use video/avi

I don't know the history of these mime types so these are just my observations.

Yeah, I think that's wrong.  It does appear that the official mime type for avi is "video/x-msvideo", but a lot of times I'll see the extension in mime types.  I would use both.  :)
I think the way I have MP42 mapped is wrong, but I'm not sure what to map it to.  I did just see that my Note S20 has a video/mp43, so I'm going to change it to video/mp42.  I don't think it will work either way.  :)  I did get MP42 to play (poorly) when I mapped it to "video/mp43", but I don't think it's right.
Part of the issues is that container and the codec are both of type "video/", which confuses the matter.

So, I found this in AOSP.
https://android.googlesource.com/platform/external/mime-support/+/refs/heads/master/mime.types
I would assume that means that "video/x-msvideo" is the official type for AVI on Android.

authors: dburckh moneytoo

repo: dburckh/ExoPlayer


text:
Error in Android app build (c++ version)

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch react-native-pkce-challenge@5.3.0 for the project I'm working on.
I have an error when building my android app with react-native@0.73.* and react-native-pkce-challenge@5.3.0, I think this is because react-native no longer supports c++ 11, using c++ 20 in CMakeLists solves my problem.
Error:
error Failed to install the app. Command failed with exit code 1: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
Execution failed for task ':react-native-pkce-challenge:buildCMakeDebug[arm64-v8a]'.
mobile/android/../node_modules/react-native/ReactCommon/jsi/jsi/jsi.h:1107:23 error: no template named 'enable_if_t' in namespace 'std'; did you mean 'enable_if'? typename = std::enable_if_t< ~~~~~^~~~~~~~~~~ enable_if

Here is the diff that solved my problem:
diff --git a/node_modules/react-native-pkce-challenge/android/CMakeLists.txt b/node_modules/react-native-pkce-challenge/android/CMakeLists.txt
index b6ea016..44f20fa 100644
--- a/node_modules/react-native-pkce-challenge/android/CMakeLists.txt
+++ b/node_modules/react-native-pkce-challenge/android/CMakeLists.txt
@@ -2,7 +2,7 @@ cmake_minimum_required(VERSION 3.4.1)
 project(PkceChallenge)

 set (CMAKE_VERBOSE_MAKEFILE ON)
-set (CMAKE_CXX_STANDARD 11)
+set (CMAKE_CXX_STANDARD 20)

 add_library(cpp
             SHARED

Do you have the same problem?
All works in iOS.
This issue body was partially generated by patch-package.

v5.3.1 release should include the fix for this issue.

authors: cavanierc dcangulo

repo: dcangulo/react-native-pkce-challenge

license: MIT


text:
ldc not auto detected

I happened to install only ldc2 on my machine and cmake wouldn't auto detect it. I changed the auto-detect logic to search for it as well and it just works. Is there a reason why ldc2 wasn't added to the auto-detect?

No reason that I know of, a PR is welcome.

I created a pull request for the change, a trivial one at that.

Thanks!

authors: baruch dcarp

repo: dcarp/cmake-d

license: mit

license_source: bigquery


text:
TypeError: '>' not supported between instances of 'NoneType' and 'int'

Hi,
After configuring multiple users I got this error after using the weight:
Logger: homeassistant.helpers.event
Source: custom_components/bodymiscale/body_metrics.py:20
Integration: Bodymiscale (documentation)
First occurred: 17:47:18 (1 occurrences)
Last logged: 17:47:18
Error while processing state change for sensor.weight_karol
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 272, in _async_state_change_dispatcher
hass.async_run_hass_job(job, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 432, in async_run_hass_job
hassjob.target(*args)
File "/config/custom_components/bodymiscale/init.py", line 168, in _state_changed_event
self.state_changed(event.data.get("entity_id"), event.data.get("new_state"))
File "/config/custom_components/bodymiscale/init.py", line 191, in state_changed
self._update_state()
File "/config/custom_components/bodymiscale/init.py", line 218, in _update_state
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 368, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 404, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/config/custom_components/bodymiscale/init.py", line 301, in state_attributes
lib = body_metrics.bodyMetrics(weight, height, age, gender, impedance)
File "/config/custom_components/bodymiscale/body_metrics.py", line 20, in init
elif impedance > 3000:
TypeError: '>' not supported between instances of 'NoneType' and 'int'
Regards,
Charles

Hello, can you copy your bodymiscale.yaml?

Hello, can you copy your bodymiscale.yaml?

sure, https://pastebin.com/2GA6VJU5

It seems correct to me. Delete the test user. All your users' sensors must exist in Home assistant

It seems correct to me. Delete the test user. All your users' sensors must exist in Home assistant

It is strange because this error is only on my user, my wife's user works fine...

your sensors weight is between 10 and 220 and impedance between 0 and 3000?

your sensors weight is between 10 and 220 and impedance between 0 and 3000?

Oh shit, I found the error... I had a wrong name of inpedance sensor in esphome... I am really sorry for disturbing you :( Now all works fine


text:
Add alternateNames to manifests

Sometimes an app/driver had a different name a while back. This will allow a match up to work by specifying alternate names that the app/driver used to be called

Requires a change to hpm.exe too

repo: dcmeglio/hubitat-packagemanager


text:
Update repositories.json

I'm a novice GitHub user, so I hope I've done this correctly.

Sorry about that. I've fixed the missing comma and published the change.

Sorry about that. I've fixed the missing comma and published the change.

repo: dcmeglio/hubitat-packagerepositories

license: Unlicense


text:
dcos cluster setup fails for clusters without authentication

What version of DC/OS + DC/OS CLI are you using (dcos --version)?
dcoscli.version=20f80a50d62367f12bb6542eefa10eb5ef51da04
dcos.version=1.12.0-beta1
dcos.commit=a55cf6cd18bea6961e2cc3c957ac8d0ee47583d5
dcos.bootstrap-id=f6e3cce0ac2024518b3dfac5879423ef75db79ac

What operating system and version are you using?
Debian 8.6 (jessie)
What did you do?
dcos cluster setup http://10.0.91.11 to configure the CLI for a 1.12.0-beta1 test cluster.
What did you expect to see?
Successful CLI configuration for the given cluster.
What did you see instead?
CLI configuration failed with Error: expected status code 401, got 200
When run with -v:
$ dcos -v cluster setup http://10.0.91.11
Setting up the cluster...
Falling back to the WWW-Authenticate challenge.
Error: expected status code 401, got 200

I think the problem is in this code: https://github.com/dcos/dcos-cli/blob/20f80a50d62367f12bb6542eefa10eb5ef51da04/pkg/setup/setup.go#L110-L119
If there is no ACS token, the CLI tries to login to get one. Because the cluster has no authentication configured, it doesn't return the 401 auth challenge response that the CLI expects.
As a workaround, I provided an arbitrary ACS token to skip the login and was able to configure my cluster:
$ DCOS_CLUSTER_SETUP_ACS_TOKEN=blah dcos cluster setup http://10.0.91.11
$ dcos cluster list
        NAME                      ID                    STATUS      VERSION            URL
  *  seed-stack  24d8583c-38ba-4091-adb7-fe11a3b4d3db  AVAILABLE  1.12.0-beta1  http://10.0.91.11

Thank you for the report!

Because the cluster has no authentication configured

Did you use the oauth_enabled configuration parameter for this?

Thanks for the quick reply. Sorry for the inconvenience!

(We don't really want to juggle oauth stuff for test clusters that we rebuild regularly and that aren't accessible from the public internet anyway.)

Makes sense.
I have created a JIRA ticket which tracks patching the CLI to address the issue you have observed.
By the way: good stuff that praekelt.org is doing there with DC/OS :)

authors: jerith jgehrcke

repo: dcos/dcos-cli


text:
tox.ini: Use --cov-report=term-missing

so we can see line numbers of uncovered lines

Can one of the admins verify this patch?

I'm not convinced of the value of adding this to the CI report. It is buried in an already log build/test log and there is no action based on the outcome of the report. I would also argue that its the responsibility of the reviewer to make sure changes have tests. What do you think?

Yeah I don't think people will look at it in the CI logs. I just found it useful myself while developing locally and trying to increase coverage -- e.g.: #902
The ideal thing to have I think is to have the CI measure the coverage and fail the build if the new or changed code is uncovered - see http://www.couverture.io/ (disclaimer: I am friends with the founder, @aconrad).

Yes, something like that would be great. It would need to also detect code tested by integration tests, which is what the majority of our tests are.

If you are looking for a code coverage service, I'm currently looking for testers at www.couverture.io and I'll be more than happy to provide direct support. Here's a sample PR on how to do it (with Travis):
https://github.com/benoitc/gunicorn/pull/1456/files
But it seems that you are using TeamCity, in which case you'd want to simply go through the documentation of www.couverture.io and see how to hook up your repository to it.

@tamarrow I saw you were attempting to upload a coverage report to Couverture.io (thanks!) but you were getting a 404 when uploading to this URL:
https://app.couverture.io/coverage/github/tamarrow/dcos/dcos-cli/d41fd05225c84154b1f7215c1ef3c1a8b125bdc2/

It's indeed invalid because you are missing the job name at the end of the path which can be anything that describes the task that generated the coverage report. You could set it to simply python but since you are using tox, a common practice with to use the $TOXENV environment variable as the job name which will result in the following URL in your scenario:
https://app.couverture.io/coverage/github/tamarrow/dcos/dcos-cli/d41fd05225c84154b1f7215c1ef3c1a8b125bdc2/py35-unit

Checkout the docs which provide a sample curl upload command:
http://www.couverture.io/#docs

@tamarrow I realize the link I provided you with doesn't work, there's your username in it AND the org's name, dcos. It's one or the other. This would be more like it:
https://app.couverture.io/coverage/github/dcos/dcos-cli/d41fd05225c84154b1f7215c1ef3c1a8b125bdc2/py35-unit

Thanks. We're not going to add anything now, but I'll check back when we have some time to look into different test coverage reports.

Sounds good. Remember the link above is meant to be used to upload the coverage report using a POST request. Just ping me if I can be of any help, otherwise the docs on the website should have you covered.

authors: aconrad mesosphere-ci msabramo tamarrow


text:
tunnel: Add examples and other cleanup

What are your changes?
What type of changes does your doc introduce?

[x] Bug fix
[ ] New feature

What is the urgency level of this change?

[ ] Blocker
[ ] High
[x] Medium

I have completed these items:

[x] I have tested all commands and code snippets.
[x] I have built locally and tested for broken links and formatting.
[x] I have made this change for all affected versions (e.g. 1.7, 1.8, and 1.9).
[x] My doc follows the style guide: https://github.com/dcos/dcos-docs#contributing.

Ping @emanic @sascala @joel-hamill for reviewing pull request changes.
Also @joerg84
If you included a comment with your commit, it appears here:

Ready for review @sascala and @joerg84

I made an update to address the comments.

Ok, I've made some changes.

@nlsun Okay, one last change and I think it's good to go.

Ok, removed the lonely 1.

I'll rebuild the live site by EOD. In the meantime you can view your changes internally at https://dev.dcos.io/docs/1.8/administration/access-node/tunnel/ within 10 minutes.

authors: joel-hamill nlsun

repo: dcos/dcos-docs


text:
[1.12] gen: Make X-Frame-Options configurable for DC/OS UI

This is a backport of https://github.com/dcos/dcos/pull/4888 with changed default value from DENY to SAMEORIGIN.
High-level description
Provides a new configuration adminrouter_x_frame_options that allows configuring X-Frame-Options value for DC/OS UI responses.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-49594 Allow X-Frame-Options to be set in cluster configuration

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot label Ready For Review

@jongiddy i'll create 1.13 follow up PR with default changelog entry

repo: dcos/dcos


text:
Updated a configuration name to 'mesos_docker_volume_chown'.

High-level description
What features does this change enable? What bugs does this change fix?
Updated a configuration name to 'mesos_docker_volume_chown'.
Corresponding DC/OS tickets (required)

DCOS_OSS-5381 Add a configuration option to change docker volume ownership to the task user.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot label Ready For Review


text:
🛑 Danbs is down

In 4d743ab, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 139 ms

Resolved: Danbs is back up in c1945c1 after 6 minutes.

repo: ddanbs/upptime


text:
🛑 Danbs is down

In be59931, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3148 ms

Resolved: Danbs is back up in 2492412 after 6 minutes.


text:
🛑 Danbs is down

In 70f51d4, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 155 ms

Resolved: Danbs is back up in 98a5a71.


text:
🛑 Danbs is down

In 341bd5a, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3476 ms

Resolved: Danbs is back up in 6f33c18 after 27 minutes.


text:
🛑 Danbs is down

In cf66f2a, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 173 ms

Resolved: Danbs is back up in 9aca239.


text:
🛑 Danbs is down

In 8881aec, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 126 ms

Resolved: Danbs is back up in a16eb2b.


text:
Consider removing ghostscript or making it optional

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Ghostscript support was added over at https://github.com/ddev/ddev/issues/920 to support typo3. While other systems can use it, it's not that common to do directly on a web node because PDF rendering can be memory intensive. Since that PR, some distributions including Ubuntu have actually disabled ImageMagick / GhostScript integration due to security issues: https://stackoverflow.com/a/60145352
As well, typo3 doesn't list ghostscript as a requirement. The only mention I can find for it in the docs is at https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/10.3/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.html#description.
Given that Ghostscript adds ~50MB to the web image. Let's not impose that cost on every DDEV user.
On master:
ddev/ddev-webserver-prod                             v1.23.4-47-gfec8d695f-dirty     c57d5ba5346a   7 minutes ago   1.39GB
ddev/ddev-webserver                                  v1.23.4-47-gfec8d695f-dirty     d21725fbef6f   7 minutes ago   1.62GB

Locally, removing ghostscript:
ddev/ddev-webserver-prod                             v1.23.4-47-gfec8d695f-dirty     f78c597f9b2c   About a minute ago   1.34GB
ddev/ddev-webserver                                  v1.23.4-47-gfec8d695f-dirty     f1bc54da514f   2 minutes ago        1.57GB

Describe your solution
Either:

Remove ghostscript entirely.
Add a config option so the typo3 recipe can install ghostscript automatically.

Describe alternatives
No response
Additional context
No response

@nickchomey are you using typo3 or something else?

I use it every day 🥹

Ideally for TYPO3 it would be cool to have some kind of recipe that dynamically adds it to the image if "typo3" project type is selected? My reasoning would be to make it easy for people who try to contribute to TYPO3 (or have a dev instance) who might not be familar with ddev configs. And it would be a breaking change for them otherwise.
One of the reasons for DDEV getting a high adoption for us was always, that the default web container is ready-to-go and can be used without much further very specific configuration.

I get the point to remove this, however I highly suggest to phase this out slighty. That means, the "ddev" command may eventually add some "warning/info" in ddev starts or similar.
Background for that is, that I know that in my current agency we have nearly every project which relies on the one or other way on that (TYPO3, Magento, Plain PHP Projects, Wordpress), and in my old company even more.
Taken into account that on a update and silently stripping that package would for sure waste a lot of time in many agencies and for freelancer investigating why their local setups with ddev no longer works or get errors.
Moving that to an extra package/install also means that no longer all may have the same setup depending on the time each developer has started/build their images or updated which can also leads to different setups.
So at least, please phase it out "slightly" over one or more versions and not dropping it simply so "agencies" may have time to add that extra package to their project repositories/branches to be prepared when it gets dropped.
If I'm not fully wrong, imagic/ghostscript combination is also used to generate pdf thumbnails which I guess more then the "fixed" apptypes may use.
Would consider removing this "carefully".

While the initiative of lightening the ddev-webserver is awesome, it sound like this is not the one we want to work on, too intrusive to existing workflows.
I'm going to close this one, but would love the same folks to take a look at

https://github.com/ddev/ddev/pull/6570

and say your opinions about that one.

Thanks folks for all the feedback. It's good to know that this tool is more broadly than I expected!

authors: deviantintegral garvinhicking rfay sbuerk

repo: ddev/ddev


text:
DBZ-574 Panel with 7 latest blogposts

https://issues.jboss.org/browse/DBZ-574

@gunnarmorling Anyfurther comments on this? Are the margins still too big?

@jpechane Yeah, looks much better now. Could we only have the same amount of padding on the right side of the text as on the left side of the menu? I think then it'd be perfect. And it'd also need a rebase to current HEAD. Thanks!

To clarify that's what I meant. The padding on the left side is great, would be nice to have the same on the right side, too.

@gunnarmorling Rebased and made padding on both sides

Looks great! Thanks, @jpechane!

authors: gunnarmorling jpechane


text:
DBZ-2587 Warning on BOOLEAN type on Db2

A warning on BOOLEAN types until the issue is resolved with IBM support.

Thanks @lga-zurich !

authors: Naros lga-zurich

repo: debezium/debezium


text:
DBZ-7463: SQL Server queries with special characters fail after applying DBZ-7273

Enclose column names in square brackets to account for spaces and special characters.

There was a fix added to main to address the test failures @ramanenka.
I'm going to rebase your PR against main and let CI run once more.

Checked locally the test failure is un-related.  Thanks @ramanenka !

authors: Naros ramanenka


text:
DBZ-1169 Outbox support

Context
DBZ-1169
This PR
This is a Draft PR which will try to reflect upon the decisions in the design of the outbox support by Debezium
Let's leave this PR for technical reviews, about the behavior let's centralize in Jira.
Todo

[ ] Configuration definition

[x] Configuration for Event Timestamp
[x] Configuration for extra fields translated to headers or message body

My idea here is to create a mapping where you can set the field and its destination: event_id:header,my_extra_field:value

[ ] Validate configuration

[x] Deal with unexpected operations

[x] Is IllegalStateException fine? We cannot throw ConnectException within apply

[x] Ignore deletions and tombstones
[x] Create Event Record with its values
[ ] Deal with Schema and Schemaless?
[x] Route by field support

[x] Set record Key based on EventKey or fallback to AggregateId

[x] Support Event Timestamp or fallback to ts_ms
[x] Extra fields support (As header, payload or ignore)
[ ] Integration tests

@renatomefi, just was reminded of the discussion with @jgao54 regarding a field for the schema version. It seems we wouldn't have to "bake this in", as it can be added by the user via that notion of "extra fields". WDYT?

@renatomefi, just was reminded of the discussion with @jgao54 regarding a field for the schema version. It seems we wouldn't have to "bake this in", as it can be added by the user via that notion of "extra fields". WDYT?

It's a bit more complicated, I didn't forget about it but I was leaving it to the end because the version is part of the metadata and has to be set in the SchemaBuilder rather than a normal value, check this.
So what I want to do is to create a Map of version and schema, since while capturing you might have multiple versions of the schema among your records, specially if your KC service is running for a while!
Is that approach valid?
Also, if you check the latest commit DBZ-1169 Schema should inherit from original type, what do you think about the approach to reuse the original schema? There's one caveat which is the field used for routing, this one should always be string since it becomes a topic, to ensure this behavior I'm using getString and the user will get an exception otherwise

Hey @renatomefi, I saw you pushed some more things to this PR. Do you have more planned or do you consider it done from your POV? Any specific things you feel we should discuss apart from a general review (planned for tomorrow, so barring any severe findings it could go into the next release)?

Hey @gunnarmorling, I think I'm done, I still want to increase tests for edge cases and misconfiguration but I can do that later, also I'll work on the docs during the week, so I'd say it's ready to go if you approve it =)

Superseded with https://github.com/debezium/debezium/pull/820

Merged via #820

authors: gunnarmorling jpechane renatomefi


text:
Page Animation

Create a simple website and add some animation

I want to contribute

Closed


text:
Rw/profile and membership

Mobile navbar implementation,
fixed scroll bar to be on right side of window on large screens,
fixed phone input width,
Union Hub page: updated "New Member Guide" link

@robu9 - you've got a failing circle CI check on this one.

repo: debtcollective/membership


text:
Markdown new line "  " (double space) converts to ""

Markdown new line "  " (double space) converts to a backslash  in the markdown editor....

Current editor,...

The slate editor from #254 is about to be merged. I can't seem to reproduce this in Slate, so that's good. If you want to have a try, look at https://deploy-preview-254--cms-demo.netlify.com/. I might just not be understanding the error you're mentioning..

@tortilaman
In markdown, two spaces are used after a certain sentence to start the next sentence on a new line.
In the current editor, this only works if the text is displayed as markdown code, in wysiwyg mode double spaces are replaced by a backslash and the text is not on a new line...
In the new slate editor, the double spaces do not work at all (not in the content preview as well).

@tortilaman
In markdown, two spaces are used after a certain sentence to start the next sentence on a new line.
In the current editor, this only works if the text is displayed as markdown code, in wysiwyg mode double spaces are replaced by a backslash and the text is not on a new line...
In the new slate editor, the double spaces do not work at all (not in the content preview as well).

@bert-bruggeman Alright, I would assume it's preferable to not have the slash, so that's probably good. I'm curious if it's the markdown library itself that doesn't support the double space syntax.

It looks like the reason this is broken in the new Slate editor is because of these lines in #254:
/**
 * Turn off soft breaks until we can properly support them across both
 * editors.
 */
pull(this.Parser.prototype.inlineMethods, 'break');

https://github.com/KyleAMathews/netlify-cms/blob/6ad4207431d0a3517257432259ab09cd49926d93/src/components/Widgets/Markdown/serializers/index.js#L119

@tech4him1 good eye :)
The issue is that soft breaks are entities in the Markdown AST, and there's no obvious way to express that entity in the Slate AST. Just need to dig in more and find the right approach. As always, contributions are welcome!

@bert-bruggeman a break can be accomplished in markdown via double space or backslash. The AST we use for markdown doesn't carry specifics, just abstract meaning - to wit, the AST doesn't know what how the break was made. When we stringify that AST, therefore, we normalize output. Breaks will be output as backslashes.
The good new is, both styles are now supported in the new editor, which is on master and soon to be released.

Sorry for bothering you with this issue a year later, but the Netlify CMS Markdown editor is still outputting line breaks as a backslash for me ()
The result in Jekyll (which uses Kramdown) is a \ in the middle of the text, instead of a  :(
You wrote The good new is, both styles are now supported in the new editor, which is on master and soon to be released.
Is this the case? Is there any way I can add support for a double space, instead of a backslash?
Sorry in advance if I am missing the obvious solution, but I couldn't find a way to force Kramdown to grudgingly accept the backslash line break notation.
For reference, I'm using Netlify CMS version 2.0.0 (https://unpkg.com/netlify-cms@^2.0.0/dist/netlify-cms.js)
Thank you!

We output commonmark compatible markdown, but Kramdown doesn't really adhere to the commonmark spec. There should be ways to configure our markdown widget's output, though, definitely worth discussing.

Hmm looks like turning off the commonmark flag might fix it: https://github.com/remarkjs/remark/blob/master/packages/remark-stringify/lib/visitors/break.js

@ouarez have you found a solution when using kramdown with netlify-cms?

Bump for this.
Jigsaw utilises Parsedown which does not appear to work with backslash newlines.
they backslash characters are rendered into content instead of newlines.
Having to train editors into using a double space is no mean feat when they just expect to type and everything "works"

I think the config options include a
 tag as well, as double spaces can be easily deleted by mistake.

This is still our single biggest issue our editors experience.
Saving in rich text mode converts all double spaces to backslash which then display in articles. Not great

Please someone address this issue.

Hey guys is there a solution for this? It's quite frustrating to not be able to add a line break without getting that weird slash.. I did switch from react-markdown to react-commonmark to try and address this but that didn't fix the issue

I've been struggling with this one also.  I've implemented some simple regex to get around it:
//Generate Content
let converter = new showdown.Converter({ simpleLineBreaks: true });
let html = converter.makeHtml(frontMatter.body);

//Hack to remove random backslash with single line breaks. See: https://github.com/netlify/netlify-cms/issues/512
html = html.toString().replace(/\\
/g, "
");
frontMatter.htmlBody = html;

This just takes any html that is \
 and replaces it with a
.
Seems to work ok in my case, maybe this is helpful for others viewing this ticket.

I've been struggling with this one also. I've implemented some simple regex to get around it:
//Generate Content
let converter = new showdown.Converter({ simpleLineBreaks: true });
let html = converter.makeHtml(frontMatter.body);

//Hack to remove random backslash with single line breaks. See: https://github.com/netlify/netlify-cms/issues/512
html = html.toString().replace(/\\
/g, "
");
frontMatter.htmlBody = html;

This just takes any html that is \
 and replaces it with a
.
Seems to work ok in my case, maybe this is helpful for others viewing this ticket.

Works like a charm. Thanks!

I've been struggling with this one also. I've implemented some simple regex to get around it:
//Generate Content
let converter = new showdown.Converter({ simpleLineBreaks: true });
let html = converter.makeHtml(frontMatter.body);

//Hack to remove random backslash with single line breaks. See: https://github.com/netlify/netlify-cms/issues/512
html = html.toString().replace(/\\
/g, "
");
frontMatter.htmlBody = html;

This just takes any html that is \
 and replaces it with a
.
Seems to work ok in my case, maybe this is helpful for others viewing this ticket.

Works like a charm. Thanks!

hi all
where i add this ?

repo: decaporg/decap-cms


text:
When using Chrome/Firefox to edit the "Body" text editing box on the Android phone, it is almost impossible to enter any text.

Describe the bug
When using Chrome/Firefox to edit the "Body" text editing box on the Android phone, it is almost impossible to enter any text.
To Reproduce

You need to have an Android phone.
Open the Netlify CMS
Click the "Body" textfield and try to input any characters.
See error.

Expected behavior
Input any characters normally.
Applicable Versions:

Netlify CMS version: 2.0.10
Git provider: GitHub
OS: MIUI 13 (Android 12)
Browser version: Chrome Dev 100 and Firefox Beta 98

CMS configuration
backend:
  name: git-gateway # https://github.com/netlify/netlify-cms
  branch: main # 要更新的分支(可选；默认为主分支)

# This line should *not* be indented
publish_mode: editorial_workflow

# This line should *not* be indented
media_folder: "themes/fluid/source/img" # 媒体文件将存储在图片/上载下的Repo中。
public_folder: "/img" # 上传的媒体的src属性将以/images/uploads开头。

site_url:  # 网站网址
display_url:  # 显示网址
logo_url:

locale: "zh_Hans" # 语言环境 https://github.com/netlify/netlify-cms/tree/master/packages/netlify-cms-locales/src

auto_generator:
  post:
    # 如果你有多个Post文件夹，在这里定义多个，见https://github.com/jiangtj/blog/blob/master/netlify-cms.yaml
    all_posts:
      # 设置为false，关闭默认的Post
      enabled: false
      label: "Post"
      folder: "source/_posts"
      create: true
      editor:
        preview: true
  # Page生成配置
  page:
    enabled: false
    config:
      label: "Page"
      # 默认禁止删除Page文件
      delete: false
      editor:
        preview: true

collections:      # https://www.netlifycms.org/docs/configuration-options/#collections
  - name: "posts" # 在路由中使用，例如：/admin/collections/blog。
    label: "文章" # 在用户界面中使用

    folder: "source/_posts" # 存储文件的文件夹的路径。
    create: true # 允许用户在这个集合中创建新的文件。
    fields: # 每份文件的字段，通常是前面的内容。
      - {label: "标题", name: "title", widget: "string"}
      - {label: "作者", name: "author", widget: "string", required: false}
      - {label: "摘要", name: "excerpt", widget: "list", required: false}
      - {label: "文章页顶部大图", name: "banner_img", widget: "image", required: false}
      - {label: "文章在首页的封面图", name: "index_img", widget: "image", required: false}
      - {label: "发布日期", name: "date", widget: "datetime", format: "YYYY-MM-DD HH:mm:ss", dateFormat: "YYYY-MM-DD", timeFormat: "HH:mm:ss", required: false}
      # - {label: "更新日期", name: "updated", widget: "datetime", format: "YYYY-MM-DD HH:mm:ss", dateFormat: "YYYY-MM-DD", timeFormat: "HH:mm:ss", required: false}
      - {label: "永久链接", name: "permalink", widget: "string", required: false}
      - {label: "内容", name: "body", widget: "markdown", required: false}
      - {label: "标签", name: "tags", widget: "list", required: false}
      #- {label: "分类", name: "categories", widget: "list", required: false}
      - {label: "文章排序权重", name: "sticky", widget: "number", required: false}
      - {label: "在首页中隐藏此文章", name: "hide", widget: "boolean", default: false, required: false}
      #  comment: 'This is a multiline\ncomment'
      # - {label: "评论区", name: "comments", widget: "boolean", default: true, required: false}
      # - {label: "关键词", name: "keywords", widget: "list", required: false}
    editor:
      preview: true

I’ve the same problem on my ipad.
OS: ipados 15.5
Browser: Safari

FYI, this is also reproducible on the Netlify demo page.
To add a little color:

Text cannot be added with the rich text editor until one of the buttons on the editor is clicked. This action causes the Android keyboard to open.
Once text is entered, it doesn't seem to be fed into the app. The text is not shown in the preview on the right
Switching chrome to desktop mode does not help. Im fact, it somehow causes text entered to be prepended (typing "hello" will actually add "olleh" to the text box)
Text entered is also apparently not accessible when posting the article. The UI gives an error about missing body content

I suspect the issue ties to the WYSIWYG editor since other fields that are plain old text (Title, for example) work fine and accept the textual input.

I'm having a similar issue. In the editor, when I try to type text into the middle of an existing line, the cursor automatically moves to the end of that line after each keystroke.
This happens on both the markdown and rich text view in Chrome (but not in Safari).

The issue is still there in Decap CMS.

We are actively working on updating Slate, which is the root of all editor problems. In the meantime, you can try this fix: https://github.com/decaporg/decap-cms/issues/5092#issuecomment-1256321540

It works on my side. Thanks @martinjagodic

We are actively working on updating Slate, which is the root of all editor problems. In the meantime, you can try this fix: https://github.com/decaporg/decap-cms/issues/5092#issuecomment-1256321540

One year ago😂😂😂
I just realized that this project has been renamed😭😭

We are actively working on updating Slate, which is the root of all editor problems. In the meantime, you can try this fix: #5092 (comment)

This fixed my cursor jumping on chrome on macos but I still can't edit rich text on chrome/firefox on my android phone.

@Songyon, @zoran-cuckovic, @jeebb, @timpaul is this issue solved for you in Decap 3.0?

@Songyon, @zoran-cuckovic, @jeebb, @timpaul is this issue solved for you in Decap 3.0?

Thank you. After my attempt, I confirmed that the problem has been fixed.

Great! Closing as fixed.

authors: 0x3st DRuggeri Songyon jeebb martinjagodic maxwedwards timpaul


text:
Demo site doesn't keep changes made

"Try the interactive demo" goes to https://demo.decapcms.org.
Confirm please - editing seems possible of various nodes, but the changes are discarded right?
For example: can't add one more "post" even though filling all the pertinent fields is possible and [save] can be pressed

No changes are saved on the demo playground.

authors: martinjagodic paul-hammant


text:
make polygon specific provider / signer calls dynamic to the network

Description
I took what was done in https://github.com/decent-dao/fractal-interface/pull/999 and put those calls into a method that delineates the calls depending on which network you're on.
This way we can bring back polygon, but not rely on the provider for other networks.

@decent-dao/fractal I think this logic is still good for supporting Polygon post Eth denver, but given that we're rewriting the contracts and invalidate existing DAOs, I'm going to still remove Polygon from the supported networks

repo: decent-dao/fractal-interface


text:
Use range scan after a certain parcel threshold

Range queries for parcels are working faster than using OR for each one. Set a threshold to take advantage of range when fetching many parcels. This implementation keeps the same interface of the API.

Works great! two minor things to see what you think:

As a mini perf-boost, instead of doing 3 maps, what do you think of just pushing the coords to the x/yCoord arrays? Something like this:

  const xCoords = []
  const yCoords = []

  coordinates
    .forEach(coord => {
      const [x, y] = coordinatesUtils.toArray(coord)
      xCoords.push(parseInt(x, 10))
      yCoords.push(parseInt(y, 10))
    })

it looses the functional feel it has so I don't know if it's really necessary given that the perf bust is minimal.

I can't really tell if the tradeoff is going to be positive, but we could filter the requested coordinates out of the final range, to send less data thought the wire:

  const parcels = await ParcelState.inRange(mincoords, maxcoords)
 return parcels.filter(parcel => /* check that it belongs to `coordinates` */)

What do you think? it's better to just return everything and avoid another loop? my gut tells me that the filter should be faster than TCP :P

authors: NicoSantangelo abarmat

repo: decentraland/auction


text:
For many users the initial default fullscreen resolution is super small

We should check this PR to at least try to force the issue to solve it
https://github.com/decentraland/explorer-desktop/pull/74

A user reported:
Display resolution setting: 3840x2160 / scaling 100% / HDR on

I have tried the following :
Right click program desktop shortcut
select properties
select compatibility tab
select change high dpi settings
select checkbox program DPI
click OK
result
Window is still not scale able, I can not see bottom of the game (chatbox can not be clicked).

inside game
Graphics setting is set to ultra
changed program setting (P) to window mode : windowed
cannot change settings on the right
changed program setting (P) to window mode : full screen
terribele everything becomes distorted
changed program setting (P) to window mode : fullscreen borderless
same as windowed
Graphics setting is set to ultra

computer setup
I5-6600 /16GB/ GTX1080 / win 10home version 19044.1526 / chrome OS 99.0.4844.51 64 bit / display Philips 436M6

Apparently this happened again

repo: decentraland/explorer-desktop


text:
Adding revealed messages to challenge hash

Closes #74
Adding the revealed messages as well as the signature domain value to the challenge hash in ProofGen and ProofVerify.

Couple of updates,

Per @tplooker suggestion the R value (number of revealed messages) is added to the challenge hash.
Removed the PK from the challenge hash since it is already part of the domain value.

Will be addressed after merging of #138

Replaced by #188. Closing.

authors: BasileiosKal tplooker

repo: decentralized-identity/bbs-signature


text:
Clarification on signer methods and return types

signer params are very confusing at the moment.
ES256K signers are expected to produce ECDSASignature objects while Ed25519 signers are expected to produce strings.
The developer is notified of this by an error.
See SignerAlgorithm.ts#L28 and SignerAlgorithm.ts#L41
This should be improved.
Signers should only produce strings since that way, signing can be externalized and there would no longer be a need to understand all algorithms locally, thus allowing support for many more crypto suites.

Any thoughts on using a more generic underlying library such as jose? Would extend the number of supported algorithms :)
Don't know how difficult it would be to migrate, but would be nice with wider support!

Yes, this relates directly to that approach.
If this lib makes assumptions about the structure of signatures then it essentially prohibits the use of libs like jose

Is that because of the use of ES256K-R? Basically because of ethereum addresses being valid signature keys in this library?

Yes, so there would still be special handling of non-standard algorithms; at least for a while.
The point of this issue is to relax the need of this library to know signature formats and expect signers to always produce strings.
Regarding ES256K-R, in the long run it should not even be a thing since, even for ethereumAddress as keys, it can be verified almost the same as ES256K.
In parallel, I made a proposal to ethr-did-resolver to use public keys as identifiers instead of ethereum addresses. That would alleviate the need to have special handling here.

That sounds great :) FYI, we are likely to start using the jose library to do IPLD object signatures and encryption in Ceramic. But afaik, it should still be possible to verify signatures generated from that with the did-jwt library!

authors: mirceanis oed

repo: decentralized-identity/did-jwt


text:
Node skeleton project

This PR introduces a simple node project structure to start from.

koa framework/ koa router
yarn for npm frontend
prettier/husky/lint-staged for opinionated pre-commit code formatting
jest testing framework
axios for http client

This PR is now using Typescript and the npm CLI instead of yarn.

authors: bezreyhan thedoctor

repo: decentralized-identity/hubs


text:
The schema should contain a signature attribute

In order to enable easy validation of the trust-establishment JSON, it would be helpful to add a signature by the author.
Proposal
This issues refers to examples in the examples published on the identity.foundation site
The signature attribute is created by signing the hash of the attributes:

id
version
last_updated
schemas
participants
roles

hashing process
To make the hashing process repeatable the steps are

the attributes of all the objects are sorted alphabetically
the JSON is stringified without line breaks and spaces
the resulting string is used to create a SHA-256 hash

validity
In order to be deemed valid, the signature must be created by the DID in participants.author

sorry, this issue was opened without reading through the whole spec


text:
Cannot edit metadata from info overview, only from 3 dots menu

https://user-images.githubusercontent.com/50382414/152254789-f3975214-492b-4b3d-b5bb-92e67e22e322.mp4

You actually cannot in both cases. In the first case, trying to edit metadata will let you know which formats are unsupported (if any) so the user can choose to proceed or not with the items that are supported.

Oh, my bad.

authors: Donkey-Doug deckerst

repo: deckerst/aves


text:
infinite gitpod-remigrate

How to reproduce
Just run npm run gitpod-remigrate while deep is running
Problem
gitpod /workspace/dev (main) $ npm run gitpod-remigrate

> @deep-foundation/dev@0.0.21 gitpod-remigrate
> npm run gitpod-unmigrate && npm run gitpod-migrate

> @deep-foundation/dev@0.0.21 gitpod-unmigrate
> export NEXT_PUBLIC_ENGINES=0; export NEXT_PUBLIC_HIDEPATH=1; export npm_config_yes=true; export JWT_SECRET="{\"type\":\"HS256\",\"key\":\"3EK6FD+o0+c7tzBNVfjpMkNDi2yARAAKzQlk8O2IKoxQu4nF7EdAh8s3TwpHwrdWT6R\"}" export MIGRATIONS_ID_TYPE_SQL=bigint; export MIGRATIONS_ID_TYPE_GQL=bigint; export MIGRATIONS_HASURA_PATH=$(echo $(gp url 8080) | awk -F[/:] '{print $4}'); export MIGRATIONS_HASURA_SSL=1; export MIGRATIONS_HASURA_SECRET=myadminsecretkey; export DEEPLINKS_HASURA_SECRET=myadminsecretkey;  export NEXT_PUBLIC_DEEPLINKS_SERVER=https://$(echo $(gp url 3007) | awk -F[/:] '{print $4}'); export NEXT_PUBLIC_GQL_PATH=$(echo $(gp url 3007) | awk -F[/:] '{print $4}')/api/gql; export NEXT_PUBLIC_GQL_SSL=1 DEEPLINKS_HASURA_PATH=localhost:8080; export DEEPLINKS_HASURA_SSL=0; export MIGRATIONS_DEEPLINKS_APP_URL=$(gp url 3007); export MIGRATIONS_DEEPLINKS_URL=$(gp url 3006); export DEEPLINKS_PUBLIC_URL=$(gp url 3006); export DOCKER_DEEPLINKS_URL=http://host.docker.internal:3006; cd packages/deeplinks && npm run unmigrate

> @deep-foundation/deeplinks@0.0.331 unmigrate
> npm run package:build && npx migrate@latest down --matches '*.js'

> @deep-foundation/deeplinks@0.0.331 package:build
> tsc --project tsconfig.json

(node:5564) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `node --trace-warnings ...` to show where the warning was created)
ok
ok
(node:5564) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
  down : 1694386912180-sync-handlers-update-new.js
  down : 1693460330175-sync-handlers-update.js
  down : 1690737739096-deepcase-opened.js
  down : 1689630159473-healthz.js
  down : 1687790060025-finder.js
  down : 1682327540225-mathjs-schema-packages.js
  down : 1680017137379-npm-packager-ui.js
  down : 1678940577209-deepcase.js
  down : 1677340638677-npm-packager.js
  down : 1664940577209-deepcase.js
  down : 1664940577200-tsx.js
  down : 1661392616544-core-symbols.js
  down : 1658909585601-hasura-storage.js
  down : 1658622099992-unvalue.js
  down : 1657720948151-handlers.js
  down : 1657486935281-authorization.js
  down : 1655979260869-sync-handlers.js
  down : 1642827746040-demo.js
  down : 1637975150590-promises.js
  down : 1637975150573-packager.js
  down : 1623023831753-jwt.js
  down : 1622421760260-permissions.js
  down : 1622421760259-can.js
  down : 1622421760258-selectors.js
  down : 1622421760256-types.js

I have waited 60+ minutes and deep is still remigrating. While I have been waiting I have created a new deep instance in gitpod and waited until finish of installation (it was much faster to create a new gitpod instance with deep than remigrating, I guess it is infinite cause of a bug)

If you use gitpod remigrate to delete all the links without deleting essential links you can create a link that will be a marker to delete all the links created after it (having bigger id)

repo: deep-foundation/dev


text:
Can't edit items

I can't click on a person and edit their details.

@ianblair44 . Hey Ian we have fixed this issue, but this was working earlier as we have showed you in demo also. After taking pull some of the functionality got disturbed for some reasons. May be the UI team is working on HTML. This might lead to re-iteration of these kind of issues.

Alright, well let's get it fixed without breaking the HTML. Also make sure to add an expression to the ng-hide on the no items found div so that it hides when there are items.

repo: deepakshrma/peoplePlugin


text:
Create Most Used Language component

This should be like the 'Most Used Language' component on this page.
For this component the language the user most often uses is determined, then a logo matching that language is displayed.
There's no need to focus too much on styling at this point. The important thing is that it's working and the displaying the intended data. The component should be displayed on the home page.
The code for the component is located in src/components/top-lang. You should add any other files related to your component in there (e.g. css or tests). If you want to interact with the github api you should use src/services/api.js.

Thanks @pynnl, if you run into anything/have any questions feel free to say so through here or DM me in slack (the one for the class would likely be best).
Note that you're going to want to update master and the branch you're working on, I just merged in some code that changed the location of the components.


text:
add unstaking operation and unstaking judge

add unstaking operation and unstaking judge

Codecov Report

Merging #238 (2b48ed2) into master (14587af) will decrease coverage by 0.13%.
The diff coverage is 56.63%.

@@            Coverage Diff             @@
##           master     #238      +/-   ##
==========================================
- Coverage   70.51%   70.37%   -0.14%
==========================================
  Files          53       53
  Lines       15265    15349      +84
==========================================
+ Hits        10764    10802      +38
- Misses       4501     4547      +46

Impacted Files
Coverage Δ

pallets/operation/src/tests.rs
89.79% <ø> (ø)

runtime/src/lib.rs
11.60% <ø> (ø)

pallets/operation/src/lib.rs
45.11% <12.50%> (-4.21%)
:arrow_down:

pallets/credit/src/lib.rs
72.09% <44.00%> (-2.47%)
:arrow_down:

pallets/credit/src/tests.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 14587af...2b48ed2. Read the comment docs.

authors: codecov-commenter jerry-yu

repo: deeper-chain/deeper-chain