Ah, as it says in the readme kinda indirectly you have to do: sudo chown -R 1001:1001 syncserver/

Same issue here

See https://github.com/mozilla/geckodriver/releases/

Review from any native speaker would be greatly appreciated! :slightly_smiling_face: (Maybe @andrewnicols if you'd be able to find some time for this?)

This extends creating new window added in #799, so that you can specify intended window type (tab or window), as defined in W3C WebDriver spec. It seems more reasonable to have it as part of RemoteTargetLocator (not directly in RemoteWebDriver), similarly as Java bindings does. So lets move the method there and mark the previous one deprecated.

Example:

// before
$driver->newWindow();

// after:
$driver->switchTo()->newWindow();
// with window type specified:
$driver->switchTo()->newWindow(WebDriverTargetLocator::WINDOW_TYPE_WINDOW); // try to open new window
// or 
$driver->switchTo()->newWindow(WebDriverTargetLocator::WINDOW_TYPE_TAB); // try to open new tab

After merge:

• [ ] Update documentation
• [ ] Update changelog

I downloaded WET version 8.x and I get an error with the lightbox plugin when I try to open an image. I got the error with all v8.x versions. <a class="wb-lbx" href="image.jpg" title="Image title">View image</a>

Do you think it is enough? Is it a good css class names?

It would be helpful indeed, though still being limited due to a bigger issue as I indicated here #1072. And names look good.

Also I wonder how you understand the style editor so well. Most people I know have hard times understanding how to style text in Silex. Did you learn with the docs or videos or does it feel obvious to you?

Learning style management: I think my fortunate past experience with Libreoffice Writer is helping me and I was pretty much unaware of these things before that. Learning Silex: I've learnt Silex mostly from the Youtube videos, specially the two elaborate official webinars available as of now, those two webinars were very necessary. It gave me a good kick start and I feel blessed to have learnt even more now after using the software.

I can understand that you "don't think the approach in this PR is the right way forward" and I'm completely open to a better solution to solve the original issue which is the slightly annoying warning in the Chrome DevTools Console (F12). My use case is the following: as a web developer, I spend a lot of time on daily basis looking at my own warnings/errors the Chrome DevTools Console, but each time I need to visually skip the first warning because it's caused by Kee.

Please consider fixing this issue which affects developers, which are the most likely to recommend your browser extension to their non-technical friends & family members.

This seems strange, what does the clear() function do?

The style in the surrounding code seems to be } else if { without that newline.

It is not absolutely necessary to run unit tests under PHP 8. Really all that is needed is to make sure everything runs correctly under PHP 8 and composer support is added. This library is widely used, so making it PHP 8.0 compatible is a high priority.

One possibility is to have separate unit test source for PHP 8. Not ideal, but would work. At some point, support for PHP less than 7.1 should stop. 5.6 can not hold back the whole world because some people refuse to upgrade. Branch the 5.6 code and let it stagnate. I recently ported a huge project from 5.6 to 7.4, and we will be moving to 8 as soon as this library supports it. Lots of good tools to do so now.

I would be happy to help. Let me know of anything you would like done.

Is it just me? I could only see 8.0rc5 updated 3 days ago and not 8.0.0 or even 7.4.13 in docker hub tags

this error show up everytime i start Vega on win10 , please help?

Note i have java 11.0.8

K:\Users\xanarox\sfarteh>java --version 
java 11.0.8 2020-07-14 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.8+10-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.8+10-LTS, mixed mode)                                                                                                                                                                         

the error:

!SESSION 2020-11-28 01:19:23.490 -----------------------------------------------
eclipse.buildId=unknown
java.version=11.0.8
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2020-11-28 01:19:24.409
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.simpleconfigurator_1.0.300.v20110815-1744 [1]" could not be resolved. Reason: Missing Constraint: Bundle-RequiredExecutionEnvironment: CDC-1.1/Foundation-1.1,J2SE-1.4
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1177)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.eclipse.osgi 4 0 2020-11-28 01:19:24.411
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.300.v20110815-1744.jar was not resolved.

!ENTRY org.eclipse.osgi 2 0 2020-11-28 01:19:24.422
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2020-11-28 01:19:24.422
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.300.v20110815-1744.jar was not resolved.
!SUBENTRY 2 org.eclipse.equinox.simpleconfigurator 2 0 2020-11-28 01:19:24.422
!MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.1))(&(osgi.ee=JavaSE)(version=1.4)))".

!ENTRY org.eclipse.osgi 2 0 2020-11-28 01:19:24.422
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2020-11-28 01:19:24.422
!MESSAGE Bundle org.eclipse.equinox.simpleconfigurator_1.0.300.v20110815-1744 [1] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.simpleconfigurator 2 0 2020-11-28 01:19:24.422
!MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.1))(&(osgi.ee=JavaSE)(version=1.4)))".

!ENTRY org.eclipse.osgi 4 0 2020-11-28 01:19:24.422
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

Hi.

I translated the french version of the website, and am owning the domain on which this translation is available right now.

During past two years, I tried to check regularly at which state is Weblate support for PTIO (https://github.com/privacytools/privacytools.io/issues/1106) but nothing seems to move. I don't have a lot of time to give to PTIO, though, and I can't help to move on this subject.

Since PTIO changed a lot, I would probably have to translate again everything from scratch and I would not like to do this work a second time if I know a Weblate support is under construction.

Please, keep me in touch if something move on this subject (either it's getting developed or community decided to not use it in the end).

Thanks for opening this issue.

Is your feature request related to a problem? Please describe.

Have this graph as an example:

See how the legend is confusing and occupies a large space on the screen. Perhaps the legend is redundant in some respects as well.

Describe the solution you'd like

Maybe we could have something like this, in a table, sorted:

As patched in https://github.com/libssh2/libssh2/commit/dedcbd106f8e52d5586b0205bc7677e4c9868f9c, would it be better to create a new release with that patch?

I noticed that interactive agents are not "kept" listed in the device group when they go offline and stop running the agent. This is not like the regular agents.

It doesn't bother me that they are not listed, except that the user consent parameters do not stick. Specifically, I want all agents to have connection toolbar present. Actually, that's more of my problem. How can I make that a universal setting for all agents? Then I would not need them to be listed at all times. thank you.

Thanks everyone