text:
Flaky test: DockerSuite.TestExecInteractiveStdinClose

Found in:
#17202
----------------------------------------------------------------------
FAIL: docker_cli_exec_unix_test.go:18: DockerSuite.TestExecInteractiveStdinClose

docker_cli_exec_unix_test.go:37:
    c.Assert(strings.TrimSpace(output), checker.Equals, "hello")
... obtained string = ""
... expected string = "hello"

----------------------------------------------------------------------

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

tracked here #17473

authors: GordonTheTurtle calavera runcom

repo: docker/docker


text:
Docker pull CPU usage limit

Extraction part of Docker pull process produces CPU load that can be significant on hosts with a few CPU cores. Is there a way to limit it using cgroups? There should be a way to do a tradeoff between pull speed and CPU load.

Sure, you can put docker in a cgroup.
If you are using systemd, see https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html for available options.

Is it safe to put entire daemon in CPU limited cgroup? Could that impact some other daemon functionality? I guess it is safe since nothing else that daemon does is CPU intensive.

Let me close this ticket for now, as it looks like it went stale.

source: gharchive/issue

authors: alenca cpuguy83 thaJeztah

license_type: permissive

license_source: github-api


text:
Docker app for MacOS not starting up all the way/hangs

Steps to reproduce the issue:

Start docker application (Spotlight, type "Doc", select Docker icon).
Docker icon in upper right shows "Starting"
Never finishes starting.

Describe the results you expected:
Expect that eventually Docker will have finished starting and I will be able to docker build, docker run, etc.
Additional information you deem important (e.g. issue happens only occasionally):
Tried rebooting, still hangs.
Output of docker version:
BAM-034083-JB:~ brereton$ docker version
Client:
 Version:      1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   78d1802
 Built:        Wed Jan 11 00:23:16 2017
 OS/Arch:      darwin/amd64
Error response from daemon: Bad response from Docker engine

Output of docker info:
Error response from daemon: Bad response from Docker engine

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker for Mac,
Version of OS/X is 10.10.5

Mac specific issues need to be opened in https://github.com/docker/for-mac/issues and should include a diagnostic code. I am closing this here as this is for engine specific issues.

authors: joannbrereton justincormack


text:
docker run -t causes stderr messages to be sent to stdout.

Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1121689
Description of problem:
The handling of stdout/stderr stream is not correct in tty mode (works fine in non-tty mode). You can see it on the example bellow. (ls non_existing_file prints into stderr stream)
Version-Release number of selected component (if applicable):
docker-1.1.1-1.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
TTY:
[root@localhost ~]# docker run -t -a stderr fedora ls non_existing_file
[root@localhost ~]# docker run -t -a stdout fedora ls non_existing_file
ls: cannot access non_existing_file: No such file or directory
NON-TTY:
[root@localhost ~]# docker run -a stderr fedora ls non_existing_file
ls: cannot access non_existing_file: No such file or directory
[root@localhost ~]# docker run -a stdout fedora ls non_existing_file
Actual results:
In tty mode the output is visible only when STDOUT is attached, in non-tty mode it's visible in STDERR
Expected results:
In booth modes the output should be in STDERR stream.
Additional info:
When I use ls / it prints the info correctly into STDOUT in booth modes.

Today i ran into this case, in my usecase, docker 1.4.1,  we directly use  below command:
docker run  fedora ls non_existing_file, then it will bind to stdout and stderr.

since this by design because of blockers w pty I think this can be fixed when someone updates docs and possibly adds warning

#dibs

Hi @devopsko,
Please remember to add the keyword tags closes or fixes once you PR to help make tracking the fixes easier. Thanks!

authors: devopsko jfrazelle nhsiehgit rhatdan xiaods


text:
closes 11646 to fix volume path validations in server side

Closes https://github.com/docker/docker/issues/11646
We added volume validation in server side when creating a container in order to keep consistent to users' expectation when sending request to server remotely.
ZJU community pair: resouer & zhouyuzhe88

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "11646-fix-volume-path-validations" git@github.com:ZJU-SEL/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

I  can confirm both two authors have signed off.@GordonTheTurtle

@resouer Indeed.
Also would be really good if we can move these validations a bit higher int he stack, before a container is ever created.

@cpuguy83  Code squashed and CI fixed. Please review.
ZJU community pair: yuzhe zhou & resouer

@cpuguy83 This is your kingdom :-) Are you +1 on design, should we move to code review?

Oh yes, sorry, didn't realize this wasn't in code review.

@cpuguy83  Code updated, please review :smile:

Can you add a call to the validation in daemon/start.go just after runconfig.ContainerHostConfigFromJob(job) is called?

@cpuguy83 Code updated, please review
cc:@resouer

Still need to make sure this gets run for both create and start and squash to 1 commit.
Let me know if you need any help! Thanks!

@cpuguy83 Code updated, please review
cc:@resouer

Also still need to squash these commits down: git rebase -i head ~4, and then change pick to squash for the bottom 3 commits, can use just one commit message since we're only really adding one thing.

@cpuguy83  Sorry, I am a little confused here... could you please give a code sample about what you mean?

@cpuguy83 Code updated, please review
ping @resouer

LGTM

@cpuguy83  CI fails again because auto-merge failed, I think we need re-base?

Hmm, looks like there the build escapes test needs to be updated since it is trying to create a volume at a non-absolute path.

@cpuguy83 We have fixed the tests, please ship it!

LGTM again

@resouer @zhouyuzhe88  looks like this needs a rebase

@thaJeztah Rebase done! :smile:

needs rebase so sorry :(

@jfrazelle rebase done ... please ship it ...

@jfrazelle rebase done ... please ship it ...

@crosbymichael does #13025 address this issue?

@calavera it's probably missing a few cases for some of the checks

so, what's the next step? @calavera @crosbymichael

ping @jfrazelle @cpuguy83

@resouer sorry, looks like this needs a rebase (again) :'(
If you can rebase, I'll pester some maintainers, I think this is taking too long.
Thanks for being patient!

There is an ongoing effort that's changing most of the volumes behavior as they know them now. I'm afraid this code will be obsolete as soon as it lands in master and merging it will only complicate things.
I really appreciate that you spent some time on this, but I think we should close this PR for now.

fine then

fine then, @calavera will this fix still needed in up coming volume code? so at least we can keep a eye open on that.

I'm not completely sure, I need to double check. There are too many changes around this code rn, sorry. :pensive:

@calavera I think I just read that the new volume features will be put behind an "experimental" flag, also, it's not "in" yet. Given its a small amount of changes (mostly added tests), it looks simple to "rip" this out again when the volume-changes are merged.
Would the tests still be useful when the new volumes-code is implemented?

Would the tests still be useful when the new volumes-code is implemented?

The validations are different, for instance data:/data is valid with the new volumes in certain cases.

Given its a small amount of changes (mostly added tests), it looks simple to "rip" this out again when the volume-changes are merged.

The new code needs to be ready this week, afaik. So, this will be rewritten in 3 days tops. I'd rather not rewrite any code that's not completely necessary in master rn.

@resouer the volumes refactor is already in master. I think this still can be relevant if you want to finish it. The only validation change would be that data:/data is now valid, since the first part can be the name of a volume.

@calavera Thanks for your remind, I'll moving on.

@resouer Thanks for the patch and for your patience! Can you please rebase?

@resouer sorry could you please rebase? :(

Closing this PR until it moves forward. Please, feel free to reopen it when there is any update in the code.

@calavera  @runcom @icecrime  sorry for a late response as I did not notice the comments here, I'll open a new RP to solve this

@resouer if possible, you can update this PR, be sure to "ping" a maintainer to reopen this PR before pushing, otherwise GitHub will not update the PR

ping @resouer just checking; are you working on this (or a replacement PR)?

@thaJeztah  sorry, im hanging up on other stuff ... so not progress yet

@resouer alright, just checking :+1:

source: gharchive/pull-request

authors: GordonTheTurtle calavera cpuguy83 crosbymichael icecrime jfrazelle resouer runcom thaJeztah zhouyuzhe88


text:
Move Vishnu to alumni

/cc @vishh - thanks!

<3 LGTM

:clap: :heartbeat: LGTM

LGTM :) Docker engine gets a bit more love than it used to, thanks to all the current maintainers :+1:

authors: calavera icecrime thaJeztah vishh


text:
Refactor JSON decoding, reduce defers

There's no need to check for error-nilness if we're going to return a "nil" on success.
Also, removed defer statements because they were no longer needed, and have some overhead; http://lk4d4.darth.io/posts/defer/

ping @vdemeester @calavera for review :frog:

Seems fair :stuck_out_tongue_closed_eyes:
LGTM 🐯

LGTM

LGTM

authors: calavera duglin thaJeztah vdemeester

repo: docker/engine-api

license_source: bigquery


text:
Second up rewrites entry point

The second time you fig up, fig rewrites the entry point on a container. To reproduce this issue, start with the following fig file:
whomovedmyentrypoint:
    image: scratch
    entrypoint: fail

Then, run fig up twice, inspecting the entry point each time:
$ fig up; docker inspect --format='{{.Config.Entrypoint}}' $(docker ps -ql); fig up; docker inspect --format='{{.Config.Entrypoint}}' $(docker ps -ql)
Creating foo_whomovedmyentrypoint_1...
Cannot start container 5206410efc5dce757cc0146d5dd3b28ac3cf37e23100015ea8565adf832edeb1: exec: "/fail": stat /fail: no such file or directory
[/fail]
Recreating foo_whomovedmyentrypoint_1...
Cannot start container 3fc0d214031cf7a0f955501f43e546381139610bd30ee8df98b9d938579707b9: exec: "echo": executable file not found in $PATH
[echo]

The use case for not changing the entry point is that the minimal container just for housing volumes (documented by Docker as Data Volume Containers) is little more than scratch with directories and a single, no-op executable like true-asm.

Tracking this in #613, the workaround for now is to use busybox or a container that has /bin/echo

authors: dnephin kojiromike

repo: docker/fig


text:
Kitematic Beta doesn't allow login

Expected behavior
Kitematic beta lets you login
Actual behavior
Kitematic beta doesn't let you login
Information about the Issue
Steps to reproduce the behavior

Enter username
Enter password
Try logging in
gets stuck at password should be lower case letters and numbers

Also, why do we have a peculiar requirement for password only in Kitematic Beta? dockerhub doesn't have this restriction!
Kitematic beta version : 0.10.2 (Mac)

did you try it with v0.10.3 too? https://github.com/docker/kitematic/releases

Yep. Just did. Same behaviour

make sure that you're using your hub username in lowercase

FrenchBen, this worked thanks.
However, dockerhub lets users login with either email id or username.

Was expecting kitematic to behave the same here. (Kitematic should allow login via email id as well)
Please feel free to close this issue as the original issue in the title is non-existent

@xgt001 It's a feature request we've logged, unfortunately we are more focused on fixing a few bugs atm.
Feel free to create a PR to fix this :D

authors: FrenchBen pmario xgt001

repo: docker/kitematic


text:
[macOS] identity of developer cannot be confirmed

I'm getting that message when opening Kitematic on a Mac. I guess that's because the app is not signed correctly.

Installing Kitematic from Docker for Mac is hard:

select "Kitematic" in the menu
a popup invites you to download it and place it in /Applications directory
if you retry you see that error message, without the "open" button
you need to right click on Kitematic in  /Applications to see it
after doing this, it will finally  work from Docker for Mac menu

I don't think we had that issue when we released Docker for Mac... Has anything been changed in Kitematic's release process since then?

I think that shows up no matter what, if the app isn't downloaded from the app store. If you know of a better way to do this, I'm all ears.

@FrenchBen, I don't think that is true. As long as you've got a Developer ID cert you should be able to sign the app and distribute as is without seeing this warning. Whether or not there is currently a Developer ID to use is another story.
See  Apple Developer ID and  Distribution guide

@WilsonGiese I was thinking of the different pop-up - The application was repackaged to prevent the above screenshot from happening.

this is permission when you install app not have authentic. you could use teminal with comand line as below for fix
sudo spctl --master-disable

That works, MarusaThem. Thank you!

this is permission when you install app not have authentic. you could use teminal with comand line as below for fix
sudo spctl --master-disable

Works perfectly! Thank you!

authors: FrenchBen KadirMYilmaz MarusaThem WilsonGiese aduermael


text:
Docker.Core.DockerException Failed executing &Kitematic

Expected behavior
Start Kitematic through right click on docker icon in taskbar and then kitematic.
Actual behavior
When clicking on kitematic I get an .Net Framework Error
Information about the Issue
Im using windows 10 Enterprise 64-bit. Build 17134
Detailed error message:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
Exception Text
Docker.Core.DockerException: Failed executing &Kitematic: The operation was canceled by the user
at Docker.Systray.Systray.<>c__DisplayClass18_0.b__0(Object , EventArgs ) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Systray\Systray.cs:line 186
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies:
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
Docker for Windows
Assembly Version: 2.0.0.30215
Win32 Version: 2.0.0.30215
CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker%20for%20Windows.exe
Docker.Core
Assembly Version: 2.0.0.30215
Win32 Version: 2.0.0.30215
CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker.Core.DLL
Docker.WPF
Assembly Version: 2.0.0.30215
Win32 Version: 2.0.0.30215
CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker.WPF.DLL
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
NLog
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files/Docker/Docker/NLog.DLL
Newtonsoft.Json
Assembly Version: 11.0.0.0
Win32 Version: 11.0.2.21924
CodeBase: file:///C:/Program%20Files/Docker/Docker/Newtonsoft.Json.DLL
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.ServiceModel
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
Microsoft.Toolkit.Uwp.Notifications
Assembly Version: 1.5.1.0
Win32 Version: 1.5.1.0
CodeBase: file:///C:/Program%20Files/Docker/Docker/Microsoft.Toolkit.Uwp.Notifications.DLL
Windows.UI
Assembly Version: 255.255.255.255
Win32 Version: 10.0.10011.16384
CodeBase: file:///C:/WINDOWS/system32/WinMetadata/Windows.UI.winmd
Windows.Data
Assembly Version: 255.255.255.255
Win32 Version: 10.0.10011.16384
CodeBase: file:///C:/WINDOWS/system32/WinMetadata/Windows.Data.winmd
System.Runtime.InteropServices.WindowsRuntime
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.InteropServices.WindowsRuntime/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.InteropServices.WindowsRuntime.dll
System.ValueTuple
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ValueTuple/v4.0_4.0.0.0__cc7b13ffcd2ddd51/System.ValueTuple.dll
Docker.Win32Helpers
Assembly Version: 1.0.6953.20825
Win32 Version:
CodeBase: file:///C:/Program%20Files/Docker/Docker/Docker.Win32Helpers.DLL
PresentationFramework.Aero2
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero2.dll
System.Net.Http
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
WindowsFormsIntegration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_4.0.0.0__31bf3856ad364e35/WindowsFormsIntegration.dll
Windows.Foundation
Assembly Version: 255.255.255.255
Win32 Version: 10.0.10011.16384
CodeBase: file:///C:/WINDOWS/system32/WinMetadata/Windows.Foundation.winmd
System.Net.Http.Formatting
Assembly Version: 5.2.3.0
Win32 Version: 5.2.30128.0
CodeBase: file:///C:/Program%20Files/Docker/Docker/System.Net.Http.Formatting.DLL
SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
Steps to reproduce the behavior

Start docker
Try to start kitematic
Error appears

Facing the same issue

@Jimsson  were you able to find any workaround ? or any fault in setting up the kitematic in the folder structure ?

I haven't, still living with the issue and have to use CMD-prompt to be able to use docker atm (not that it's a problem but I liked Kitematic)

Installing the entire toolbox instead of just Kitematic helped fix this for me.

authors: AdityaRawat23 Jimsson krishnakb


text:
Protocol 0.2.0

Update to the protocol as a result of libchan meeting with Matteo Collina.
Bump the version to 0.2.0 and name the set the previous version as 0.1.0.
Protocol changes:

Define stream provider to support multiple multiplexing protocols
Support CBOR in addition to Msgpack for channel message encoding
Add extended type codes definition
Require byte-streams to send "libchan-parent-ref"
Allow byte-streams as duplex or half-duplex
Add channel synchronization through ack definition
Add channel errors
Update description of relationship to Go channels

Other changes:

Add Derek and Matteo to authors
Reformatted to 80 character lines
Much cleanup and rewording

Ping @mcollina for review of initial draft
Matteo, I am still uncertain about the method for doing acks, you were as well. Think of possibly keeping acks much simpler, a simple integer message, 0 for non-error ack, and > 0 for error ack. When an error is received a string message can follow, then a remote close. If no string message is given then the close should still happen resulting in an EOF. The simple integer type will work well with msgpack and cbor as most messages will only end up being a single byte.

Sorry for not reading this through sooner, I was stuck in the consulting businness :(. I think we should add a header for the message encoding. This is necessary to ensure things works with different encodings.
I propose to add a mime type of application/libchan+msgpack5 or application/libchan+cbor.
Should I send a PR against this PR with my updates?
Thanks for adding me as an author :dancers:.

Excellent point, any newly created stream which will send data should have a content-type.
Types

application/vnd.libchan.send+msgpack5 - Encoded messages in msgpack5
application/vnd.libchan.recv+msgpack5 - Encoded responses in msgpack5
application/vnd.libchan.send+cbor - Encoded messages in cbor
application/vnd.libchan.recv+cbor - Encoded responses in cbor
application/octet-stream - Byte stream

Updated based on original feedback, still need to update for content types

:+1: for the types.
Just one question: what happens if the other party does not support that encoding?

I think the ":status" as used currently in spdy and defined in HTTP is missing here. I will add ":status" as the response header which should contain an HTTP status code. In the case of unsupported content-type, a 415 would be used.

Hmm looking more at the streams interface, I am thinking streams will need to have a function to handle the reply unless it would be expected the stream provider would be configured to know how to accept content-types and expose that to the stream user.  My goal would be after a new stream is accepted, it is always good and would never need to explicitly failed by the stream user because of invalid content-type.

Finally pushed the update. Going to revive this and get this work completed.

Updated with last comments and content types
Pushed an update to the streams library in support of this change https://github.com/dmcgowan/streams/commit/f02a9e7b00caabc2b0bc3d166a329354ea57ce4d. This will enable proper content type handling by libchan.

authors: dmcgowan mcollina

repo: docker/libchan


text:
Add advertise-addr support

With this change, all the auto-detection of the addresses are removed
from libnetwork and the caller takes the responsibilty to have a proper
advertise-addr in various scenarios (including externally facing public
advertise-addr with an internal facing private listen-addr)
Signed-off-by: Madhu Venugopal madhu@docker.com

ping @aboch @aaronlehmann

This replaces the need for local-address as well for https://github.com/docker/docker/pull/24237.

Just realized that the tunnel encryption requires the localAddress.
changing this PR as WIP.

LGTM (not a maintainer)

ping @mrjana @aboch. Can you PTAL

I do not see any code which validates the bind and adv addresses.
At least before if a valid bind addr was  missing, libnetwork was trying to retrieve one via best effort.
Now, I think we should at least fail if we do not get a valid bind addr (and a valid adv addr if in agent mode)

@aboch for your comment above https://github.com/docker/libnetwork/pull/1337#issuecomment-234135308, libnetwork is designed to handle the scenario of remote-addr, local-addr and advertise-addr to be valid across different calls to agentInit. Hence erroring out isnt appropriate and infact that is exactly designed not to error out on such scenarios.
But for ease of debugging, I added an Infof (which is useful even for the user to know which ip-addresses are chosen/configured for local-addr, advertise-addr and remote-addr.

@aboch addressed your comments. PTAL

LGTM

authors: aaronlehmann aboch mavenugo

repo: docker/libnetwork


text:
sandbox_externalkey.go: split for cross compilation

runc/libcontainer split the State struct into platform specific structs
in
opencontainers/runc@fe1cce6.
As a result, NamespacePaths isn't anymore in a global struct and
libnetwork is not cross-compiling in Docker (specifically on Windows) because
sandbox_externalkey.go is using NamespacePaths.
This patch splits sandbox_externalkey.go into platform specific
files and moves common things to a generic sandbox_externalkey.go.
related to docker/docker#18106
Signed-off-by: Antonio Murdaca runcom@redhat.com

ping @mavenugo @mrjana @aboch (sorry for the noise)

LGTM

@runcom this fix seems to have made the externalkey support specific to linux.
Are we sure this doesn't have a negative impact on FreeBSD/ARM, etc ?
Can you please confirm ?

@jfrazelle updated as per your comment

\o/ all up to @mavenugo

Sorry about the delay.
With the changes to !windows shouldn't we just add a _windows.go file and not do unsupported? Even if we do _unsupported.go, isn't it appropriate to include just the Windows target ?

make sense, most docker code is the way you said @mavenugo (i.e. https://github.com/docker/docker/blob/master/daemon/container_windows.go and https://github.com/docker/docker/blob/master/daemon/container_unix.go)
I'll update the PR

green again :)

Thanks. LGTM

LGTM

Thanks all!

authors: aboch jfrazelle mavenugo mrjana runcom


text:
Win7 Enterprise SP1 - docker-machine scp  error: exit status 1 -> when using cmd shell [docker toolbox 1.9.1]

The "docker-machine scp" command is not working in Windows "cmd" shell but is working fine in MIGW64 shell.
Using MIGW64 :
$ docker-machine scp ./boot2docker-setup.sh default:/home/docker
boot2docker-setup.sh                                                                           100% 1301     1.3KB/s   00:00
boot2docker-setup.sh                                                                           100% 1301     1.3KB/s   00:00

In Windows "cmd":
C:\Development\dev-tools\devops\docker-toolbox>docker-machine scp ./boot2docker-setup.sh default:/home/docker
exit status 1

Machine details:
$ docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL                         SWARM
default   -        virtualbox   Running   tcp://192.168.99.108:2376

Docker Toolbox:
$ docker-machine env default
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.108:2376"
export DOCKER_CERT_PATH="C:\Users\zoltar\.docker\machine\machines\default"
export DOCKER_MACHINE_NAME="default"

$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      windows/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

There's no scp available in your path most likely.

Hi @flado any news on this issue? Did you make it work?

Yes, it worked after computer restart. It's possible that scp was not in the PATH.

authors: dgageot flado nathanleclaire

repo: docker/machine


text:
adding additional 'make static' command

Just creates static builds of server and signer for reliable use with alpine container for official images.
I'm by no means good at Makefiles so let me know if there's a better way to do this.
Signed-off-by: David Lawrence david.lawrence@docker.com (github: endophage)

Non-blocking - you can't seem to compile the binary statically in OS X - I'm wondering if it'd be worth it to wrap those in a
ifeq ($(UNAME_S),Darwin)
        ...
endif

Alternately we can just document in a comment that they don't work in OS X.  :)
LGTM otherwise!  The server compiles just fine.  Signer not so much because of CGO.

@cyli because the SoftHSM stuff has been taken out, the signer shouldn't have any CGo dependencies. Will need to look at that.

I second @cyli's comment about notary-signer on OS X (just tried it myself).  Otherwise LGTM!

Good to know. I'm considering this blocked until we work out why signer still has CGo dependencies.

I'm wondering if the +pkcs11 build directive has something to do with it (i'll check when I get home)

Nope.  :(   that wasn't it, sorry.  Server seems to be failing for me now too?

Looks like maybe you just can't pass the -static flag in OS X?  (https://stackoverflow.com/questions/3801011/ld-library-not-found-for-lcrt0-o-on-osx-10-6-with-gcc-clang-static-flag)
I'm getting that error above:
+ /Users/cyli/Go/src/github.com/docker/notary/bin/static/notary-server
# github.com/docker/notary/cmd/notary-server
/usr/local/Cellar/go/1.5.2/libexec/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

godep: go exit status 2
make: *** [/Users/cyli/Go/src/github.com/docker/notary/bin/static/notary-server] Error 1

@cyli well that's a bit rubbish :-(
I'll wrap it with a conditional as you suggested. Technically we only need to statically build for linux as this is just for building official binaries to be run in linux containers.

@cyli can you check that it now outputs the notifications on mac?

Just tried on my mac, I didn't get the warnings:
~ notary $ make static
pkcs11 import was not found anywhere without a build tag, yay

+ /Users/c1mqm40sg944/go/src/github.com/docker/notary/bin/static/notary-server
# github.com/docker/notary/cmd/notary-server
/usr/local/go/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

godep: go exit status 2
make: *** [/Users/c1mqm40sg944/go/src/github.com/docker/notary/bin/static/notary-server] Error 1

LGTM!

authors: cyli endophage riyazdf

repo: docker/notary


text:
events after engine connection inexistent

If an agent is disconnected from a cluster, that shows up in the list of events of swarm master
2015-09-16T05:34:37.000000000+01:00 (from swarm node:node1) engine_disconnect

However, the same doesn't occur if node1 is connected again.

Hi @aanm, hmm strange we do have an emitted engine_connect event on ConnectWithClient.. does this only happen when the engine disconnects and reconnects?

@abronan I had a master and an agent on that node (node-1). I was listen for events on the master node (node-0). I did docker rm -f swarm-agent on node-1, waited more or less minute an half until I saw 2015-09-16T05:34:37.000000000+01:00 (from swarm node:node1) engine_disconnect on node-0. After a while I did docker run swarm-agent (with the specific arguments for using consul). I wait a minute and I could see node-0 with docker -H node-1:2375 info but I didn't see the message.

@aanm Ok. In the meantime do you see the first engine_connect when an engine first connects to a cluster? Trying to narrow down and see if this only happens on disconnect/reconnect.

@abronan Weird...

Started master on node-0
DOCKER_HOST=localhost:2373 docker event on node-0
Start swarm master and swarm agent on node-1 (replication mode is active)
Stop swarm agent on node-1
Output of node-0:

$ DOCKER_HOST=localhost:2373 docker events
2015-09-16T17:44:51.000000000Z 7747ce705ea96fce1ff04751e73e33a5103eee97827411fcc590d4e632fc92ba: (from swarm:0.4.0 node:node2) create
2015-09-16T17:44:51.000000000Z 7747ce705ea96fce1ff04751e73e33a5103eee97827411fcc590d4e632fc92ba: (from swarm:0.4.0 node:node2) start
2015-09-16T17:46:28.000000000Z 199ba61323a10f43563ac864e86c18b21333b82a494d836d1ff6d5e14559e39f: (from swarm:0.4.0 node:node2) kill
2015-09-16T17:46:28.000000000Z 199ba61323a10f43563ac864e86c18b21333b82a494d836d1ff6d5e14559e39f: (from swarm:0.4.0 node:node2) die
2015-09-16T17:46:28.000000000Z 199ba61323a10f43563ac864e86c18b21333b82a494d836d1ff6d5e14559e39f: (from swarm:0.4.0 node:node2) stop
2015-09-16T17:47:08.000000000Z (from swarm node:node2) engine_disconnect

Ok I see, somehow the engine_connect is not emitted even on first connect. Annoying if you rely on events to register connection/disconnection from an external program. I'll try to have a look at it.
@vieux any idea?

@abronan Maybe I have found what's wrong. I'll try to fix. :)

Close via https://github.com/docker/swarm/pull/1219

authors: aanm abronan jimmyxian

repo: docker/swarm


text:
Swarm framework abort when Mesos master leaves.

According to my understanding, Swarm should detect the Mesos master automatically at runtime, and re-register to it when Mesos master recovery, but I found I am wrong after I tested this behaviour based on the latest code in community.
My test steps as below:
Step1: Prepare the Swarm + Mesos environment based on the latest code in community.
Step2: Run a task in Swarm cluster, and it started successfully.
$ docker -H gradyhost1.eng.platformlab.ibm.com:2375 run -d --cpu-shares 1 ubuntu:14.04 sleep 120
b8013e636cdc8d387b73d4ca252df7088e0f7d365db8ca609db34616e54df842
Step3: Then kill the Mesos master service, and I find some swarm error logs:
......
......
time="2016-02-02T07:29:46Z" level=debug msg="Removing offer" name=mesos offerID="&OfferID{Value:*9132caa4-a4a9-43ef-808a-ffe635f77db1-O4,XXX_unrecognized:[],}"
time="2016-02-02T07:29:46Z" level=debug msg="Offer \"9132caa4-a4a9-43ef-808a-ffe635f77db1-O4\" declined successfully" name=mesos
ERROR: logging before flag.Parse: I0202 07:29:46.726012       1 http_transporter.go:218] Failed to POST: Post http://9.111.255.10:5050/master/mesos.internal.LaunchTasksMessage: dial tcp 9.111.255.10:5050: getsockopt: connection refused
ERROR: logging before flag.Parse: I0202 07:29:46.726103       1 scheduler.go:1081] Aborting framework [&FrameworkID{Value:*9132caa4-a4a9-43ef-808a-ffe635f77db1-0000,XXX_unrecognized:[],}]
ERROR: logging before flag.Parse: I0202 07:29:46.726141       1 scheduler.go:1012] Stopping the scheduler driver
ERROR: logging before flag.Parse: I0202 07:29:46.726147       1 scheduler.go:1062] stopping messenger
ERROR: logging before flag.Parse: I0202 07:29:46.726154       1 messenger.go:269] stopping messenger..
ERROR: logging before flag.Parse: I0202 07:29:46.726160       1 http_transporter.go:476] stopping HTTP transport
ERROR: logging before flag.Parse: I0202 07:29:46.726167       1 scheduler.go:1065] Stop() complete with status DRIVER_STOPPED error <nil>
time="2016-02-02T07:29:46Z" level=error msg="Failed to send message mesos.internal.LaunchTasksMessage: Post http://9.111.255.10:5050/master/mesos.internal.LaunchTasksMessage: dial tcp 9.111.255.10:5050: getsockopt: connection refused" name=mesos
time="2016-02-02T07:29:46Z" level=error msg="Failed to send message mesos.internal.LaunchTasksMessage: Post http://9.111.255.10:5050/master/mesos.internal.LaunchTasksMessage: dial tcp 9.111.255.10:5050: getsockopt: connection refused" name=mesos
2016/02/02 07:29:46 Recv loop terminated: err=EOF
2016/02/02 07:29:46 Send loop terminated: err=<nil>
time="2016-02-02T07:29:46Z" level=debug msg="Mesos driver stopped unexpectedly, status/err DRIVER_ABORTED: <nil>"
time="2016-02-02T07:29:50Z" level=debug msg="Engine update succeeded" id="RJNG:KRN6:OUXI:Z6ND:MRN6:VC4A:3JRQ:F5XZ:4YIX:GEDZ:K5IF:PVHM" name=gradyhost3.eng.platformlab.ibm.com
time="2016-02-02T07:29:55Z" level=debug msg="Removing offer" name=mesos offerID="&OfferID{Value:*9132caa4-a4a9-43ef-808a-ffe635f77db1-O5,XXX_unrecognized:[],}"
time="2016-02-02T07:29:55Z" level=error msg="Error while declining offer \"9132caa4-a4a9-43ef-808a-ffe635f77db1-O5\": Unable to LaunchTasks, expected driver status DRIVER_RUNNING, but got DRIVER_ABORTED" name=mesos
time="2016-02-02T07:30:11Z" level=debug msg="Removing offer" name=mesos offerID="&OfferID{Value:*9132caa4-a4a9-43ef-808a-ffe635f77db1-O6,XXX_unrecognized:[],}"
time="2016-02-02T07:30:11Z" level=error msg="Error while declining offer \"9132caa4-a4a9-43ef-808a-ffe635f77db1-O6\": Unable to LaunchTasks, expected driver status DRIVER_RUNNING, but got DRIVER_ABORTED" name=mesos
time="2016-02-02T07:30:25Z" level=debug msg="Engine update succeeded" id="B6X2:KCUU:RYQC:ZR7T:6TKQ:TVFG:Z7HY:ASEM:CZC5:RKHM:AWS7:JPHP" name=gradyhost2.eng.platformlab.ibm.com
......
......

Step4: Restart the Mesos master service, Swarm framework does not re-register.
I am not sure whether it is a bug, because it does not always appear in my environment.

Interesting. Is that consistent for you (Swarm never re-Register)?

@doronp Yes, today I have tried with some times again, and Swarm never re-register when Mesos master recovery.
My steps as below:

Start Mesos master with command:

# (./mesos-master.sh --ip=9.111.255.10 --work_dir=/tmp/mesos-master >> /tmp/mesos-master.log 2>&1 &)

Start Swarm Manager with command:

# ./swarm --debug manage \
  -c mesos-experimental \
  --cluster-opt mesos.address=9.111.255.10 \
  --cluster-opt mesos.tasktimeout=10s \
  --cluster-opt mesos.user=root \
  --cluster-opt mesos.offertimeout=10m \
  --cluster-opt mesos.port=3375 \
  --cluster-opt mesos.enablerevocable=true \
  --host=0.0.0.0:4375 9.111.255.10:5050

Kill the Mesos master

# ps -ef | grep mesos
root      2277     1  0 17:24 pts/0    00:00:00 /opt/mesos/build/src/.libs/lt-mesos-master --ip=9.111.255.10 --work_dir=/tmp/mesos-master
root      5299  7635  0 17:27 pts/0    00:00:00 ./swarm --debug manage -c mesos-experimental --cluster-opt mesos.address=9.111.255.10 --cluster-opt mesos.tasktimeout=10s --cluster-opt mesos.user=root --cluster-opt mesos.offertimeout=10m --cluster-opt mesos.port=3375 --cluster-opt mesos.enablerevocable=true --host=0.0.0.0:4375 9.111.255.10:5050
root      5677  2840  0 17:27 pts/4    00:00:00 grep --color=auto mesos
# kill -9 2277

Restart the Mesos master:

# (./mesos-master.sh --ip=9.111.255.10 --work_dir=/tmp/mesos-master >> /tmp/mesos-master.log 2>&1 &)

After checking Mesos portal and logs, swarm never re-register.

Swarm logs:
DEBU[0000] Registering HTTP route                        method=DELETE route=/networks/{networkid:.*}
DEBU[0000] Registering HTTP route                        method=DELETE route=/volumes/{name:.*}
INFO[0000] Listening for HTTP                            addr=0.0.0.0:4375 proto=tcp
ERROR: logging before flag.Parse: E0315 17:27:45.170644    5299 standalone.go:180] Get http://9.111.255.10:5050/state.json: dial tcp 9.111.255.10:5050: getsockopt: connection refused
ERROR: logging before flag.Parse: E0315 17:28:15.170754    5299 standalone.go:180] Get http://9.111.255.10:5050/state.json: dial tcp 9.111.255.10:5050: getsockopt: connection refused

It seems the problem is not necessarily in Swarm:
https://github.com/mesosphere/kubernetes-mesos/issues/344
Problem in mesos go which was not attended to.

Thanks @doronp, do we have the plan to fix this issue?

@gradywang
I've opened https://github.com/mesos/mesos-go/issues/231
Let see if we can get it looked at, otherwise I will try to.

Closing due to https://github.com/docker/swarm/pull/2853

authors: doronp gradywang nishanttotla


text:
Allow specifying default resource constraints when running swarm manager

Allow specifying default resource constraints with cluster options. This is very useful when using other tools interacting with swarm cannot create containers because they do not expose options for --cpu-shares or --memory.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "default-resources" git@github.com:clinta/swarm.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Closing due to https://github.com/docker/swarm/pull/2853

authors: GordonTheTurtle clinta nishanttotla


text:
Add option to disable double-click creating a floating window.

A computer-challenged customer is having difficulties accidentally double-clicking the dockpanel tabs which causes them to undock and turn into a floating window. This can be a problem when not expecting it. Setting the DockAreas property is not sufficient as the ability to undock is still desired - just not when double-clicked.
Option added in DockPanel.cs:
        private bool m_floatOnDoubleClick;
        [LocalizedCategory("Category_Docking")]
        [LocalizedDescription("DockPanel_FloatOnDoubleClick_Description")]
        [DefaultValue(true)]
        public bool AllowFloatOnDoubleClick
        {
            get
            {
                return m_floatOnDoubleClick;
            }
            set
            {
                m_floatOnDoubleClick = value;
            }
        }

Option checked in DockPaneStripBase.cs:
        [SecurityPermission(SecurityAction.LinkDemand, Flags = SecurityPermissionFlag.UnmanagedCode)]
        protected override void WndProc(ref Message m)
        {
            if (m.Msg == (int)Win32.Msgs.WM_LBUTTONDBLCLK)
            {
                base.WndProc(ref m);

                int index = HitTest();
                if (DockPane.DockPanel.AllowEndUserDocking && DockPane.DockPanel.AllowFloatOnDoubleClick && index != -1)
                {
                    IDockContent content = Tabs[index].Content;
                    if (content.DockHandler.CheckDockState(!content.DockHandler.IsFloat) != DockState.Unknown)
                        content.DockHandler.IsFloat = !content.DockHandler.IsFloat;
                }

                return;
            }

            base.WndProc(ref m);
            return;
        }

Help text added in Strings.resx: DockPanel_FloatOnDoubleClick_Description	Allow document to float (undock) when tab is double-clicked.

You should be able create your own themes and then override WndProc in the strip class to disable the behavior like you indicated above. I don't think a change in DockPanel Suite itself is needed and it brings no real value to most users, who should expect DPS to behave like VS.

Thanks for the tip. The intent was to create a theme-independent option for
those who want it. I agree that it's a very narrow use case, but I figured
it could be useful to someone who doesn't want to go to the trouble of
creating a custom theme.
On Mon, Mar 19, 2018 at 2:28 PM, Lex Li notifications@github.com wrote:

You should be able create your own themes and then override WndProc in
the strip class to disable the behavior like you indicated above. I don't
think a change in DockPanel Suite itself is needed and it brings no real
value to most users, who should expect DPS to behave like VS.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dockpanelsuite/dockpanelsuite/issues/546#issuecomment-374384957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJIeYW0wugHsAZW2rFVtVkyX9y0WYHKyks5tgCLlgaJpZM4Sw55E
.

The current bar to include some feature in DockPanel Suite is higher than ever, as maintainers do have quite limited time to review the changes. Many pull requests are pending due to the same reason.
If something can be easily implemented in a custom theme, then you are not bind to DPS itself and can do whatever changes you like.

Totally understand, that's why I made the three-line addition and submitted
it instead of just suggesting the feature.
This option would also provide the inverse option that the FloatWindow
class already has:
private bool m_doubleClickTitleBarToDock = true;
public bool DoubleClickTitleBarToDock
{
get { return m_doubleClickTitleBarToDock; }
set { m_doubleClickTitleBarToDock = value; }
}
Anyway, I do like DockPanelSuite and how feature-rich it is. Keep up the
good work.
On Tue, Mar 20, 2018 at 8:09 PM, Lex Li notifications@github.com wrote:

The current bar to include some feature in DockPanel Suite is higher than
ever, as maintainers do have quite limited time to review the changes. Many
pull requests are pending due to the same reason.
If something can be easily implemented in a custom theme, then you are not
bind to DPS itself and can do whatever changes you like.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dockpanelsuite/dockpanelsuite/issues/546#issuecomment-374822767,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJIeYQS5-qEo8dBjWVwjI7OhaJ2GnDowks5tgcROgaJpZM4Sw55E
.

I think this issue should be considered for inclusion for the following reasons:

Double-clicking a tab in Visual Studio 2017 does not float the window. This suggests that this should at least be an option.
This issue has a duplicate at #156, which seems to suggest that this feature is actually desired by the DockPanelSuite community.
Some users have reported a bug involving double clicking that I have opened as issue #584. For this reason I would like to disable the feature that double-clicking a tab makes it float to prevent this bug being a problem for our users.
(Mentioned by @jakehedlund): There is an equivalent property on FloatWindow. If double-clicking a FloatWindow does not "un-float" the window, but double-clicking a tab floats it, that seems inconsistent.

Instead of making it "an option", I think it should be made a separate theme. Related to #506 and #577.
#584 will be investigated separating.
FloatWindow is far from feature complete (also related to #506), so "double clicing a FloatWindow does not unfloat the window" should be handled as a separate issue too.

Why don't we take a vote? You can drag the panel to float it anyway, why do
you need to double-click it too? Seems redundant enough to at least make it
optional.
On Fri, Dec 21, 2018 at 2:29 PM Lex Li notifications@github.com wrote:

FloatWindow.DoubleClickTitleBarToDock was added in 2013 as #91
https://github.com/dockpanelsuite/dockpanelsuite/pull/91, where we
tended to add certain new features. However, recently it is less likely to
introduce new properties, unless the addition can benefit most users, other
than only a few themes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dockpanelsuite/dockpanelsuite/issues/546#issuecomment-449514162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJIeYUetXsr9huKopA6btRV6xL9rrHSRks5u7WDmgaJpZM4Sw55E
.

@jakehedlund that's a behavior defined by Microsoft for certain VS releases, and the goal of this library is to emulate the same.
For a project with very limited resource (volunteer hours from me mainly in the past few years), it is not fair to "take a vote". Adding a switch/flag might seem to be a "simple" thing in your eye, but once added it is part of a contract to be maintained. That's why I said above it would be preferred to be isolated to a VS2017/2019 theme, as that minimizes the impact to only whoever uses that theme(s) and I don't need to spend time asking inquiries like this one.
Of course, if we get more resources to work on this project, things can change.

I've just tried the double-clicking behaviour in VS 2015, and it doesn't undock a document. Perhaps this suggests that the VS2015 themes should be changed, so that double-clicking a tab does not undock the document?

authors: DanCarterGMSL jakehedlund lextm

repo: dockpanelsuite/dockpanelsuite

license: mit


text:
The owner can now view their own unpublished hosted files

For #3801
The owner can now view their own unpublished hosted files
Frontend uses https://dev.dockstore.net/api/static/swagger-ui/index.html#/workflows/getTestParameterFiles_1 to get test paramter files for pretty much types of workflows in my-workflows -> versions -> actions -> edit
It works for everything except unpublished hosted workflows. This PR should fix that.
The alternative is to use https://dev.dockstore.net/api/static/swagger-ui/index.html#/workflows/getWorkflowVersionsSourcefiles but that has several hurdles.

That's an OpenAPI endpoint that returns OpenAPI SourceFile[] which would clash with the rest of the mostly swagger site
The immediate frontend component doesn't know the descriptorType of the current workflow or the test parameter fileTypes of the descriptorType so that endpoint makes it more difficult.

Interesting, looks good in principle.
Worth being extra paranoid with permissions for hosted files. Please add a test that a owner can now view their own unpublished hosted files. And double-check the tests and/or expand the tests that ensure that they can't be viewed before publishing.

Added 2 assertions to check that the owner can view their own unpublished hosted files. The original assertions above it checks that other users can't see it

repo: dockstore/dockstore


text:
Not working inside VM on Proxmox

Hi there,
i have a Proxmox Host with different VMs.
One for my Docker containers. For this VM i enabled "nested virtualisation"
To this VM i pass through my host CPU ( Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz)
When i try to run your container it works up until the point of extracting image, or whatever the last one is before the reboot.
After that the VNC window in the browser only says "failed to connect to server"
And then it does nothing. Just sits there.
docker compose logs:
❯ Starting Windows for Docker v2.07...
❯ For support visit https://github.com/dockur/windows

❯ Downloading Windows 11...
[i] Downloading Windows media from official Microsoft servers...
[i] Downloading Windows 11...
[!] Microsoft blocked the automated download request based on your IP address. Please check the FAQ on how to boot from a local file and manually download this ISO in a web browser here: https://www.microsoft.com/en-us/software-download/windows11

[!] 1 attempted download(s) failed! Please re-run Mido with these arguments to try downloading again (any partial downloads will be resumed): win11x64
[+] Finished! Please see the above errors with information
❯ Failed to download Windows 11 using Mido, will try a different method now...
❯ Downloading product information from Microsoft...
❯ Downloading Windows 11...
/storage/tmp/win11x64.esd          100%[===============================================================>]   4.54G  86.1MB/s    in 56s
❯ Extracting Windows 11 bootdisk...
❯ Extracting Windows 11 environment...
❯ Extracting Windows 11 setup...
❯ Extracting Windows 11 image...
❯ Adding XML file for automatic installation...
❯ Building Windows 11 image...
❯ Creating a 64G growable disk image in raw format...
❯ Booting Windows using QEMU emulator version 8.2.1 ...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8]
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
BdsDxe: loading Boot0003 "Windows Boot Manager" from HD(1,GPT,07522914-0A09-4EBD-B3BE-2623BFBAD596,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi

Maybe someone has an idea of why this is happening?
Does this needs to be run on bare metal?

I tried win11 and win10, both with and without BOOT_MODE : "windows_plain"
Here's my compose file:
#version: "3"
services:
  windows:
    image: dockurr/windows
    container_name: windows
    devices:
      - /dev/kvm
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 3389:3389/tcp
      - 3389:3389/udp
    volumes:
      - /storage/media/windows-disk:/storage
    stop_grace_period: 2m
    environment:
      #BOOT_MODE for win11 - disables Secure Boot + TPM + Hyper-V
      BOOT_MODE: "windows_plain"
      VERSION: "win10"
      RAM_SIZE: "4G"
      CPU_CORES: "4"
      DISK_SIZE: "64G"
    restart: on-failure

repo: dockur/windows

license: MIT


text:
这个站和cn.vuejs.org有什么区别？

这个站和cn.vuejs.org有什么区别？
是否重复了？

https://vue.docschina.org/about/index.html

authors: bi-kai dear-lizhihua


text:
Update output-management.md

describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

已修复

authors: dear-lizhihua hechenxi


text:
fixes undefined index in ClassMetadataInfo

Fix undefined index 0 in ClassMetadataInfo when entity doesn't have ...

When does this even happen? This check is too expensive just for the small window where no identifier is yet defined.
if ( ! $this->isIdentifierComposite && $this->identifier) {

Would be much better.

Also you could add a test.

I'm going through the list of all Entities and am gathering all data necessary for a data generation script.

How is it possible that you have an entity without identifier at that point?

It seems that the list also contains the entities defined as mapped-superclass. At leas I'm finding the User entity for FOSUB in there. Also I'm using the same code for listing as found in InfoDoctrineCommand of DoctrineBundle

Too expensive to check, isIdentifier is used in frequent states. Just check for isMappedSuperclass before.

authors: beberlei mvrhov


text:
Support for versions of Doctrine that work on PHP5.x and PHP7.0

I was reading http://www.doctrine-project.org/2017/07/25/php-7.1-requirement-and-composer.html with interest and I was wondering what is the Doctrine policy for supporting doctrine-common and doctrine-annotations on these older versions of PHP? Will 2.7.x and 1.4.x get bug fixes, or just security fixes or no fixes at all?
The reason I'm asking is that Symfony 3.4 will be supported until 2021 and it'll not drop PHP5.x support till then. I work a lot on the Drupal project and we're trying to decide what to do with PHP5.x support and one of our concerns is security support on older versions of Doctrine. Like many PHP developers I'm always excited to be using the latest version but that excitement is not shared by every user and not every user has the ability to get new OS versions in production (Ubuntu will be support PHP5.x till 2019 probably - EOL of 14.04 LTS).

one of our concerns is security support on older versions of Doctrine.

We fix security issues as far back as we can, so that's not a problem.
We don't do bug LTS support.

Thanks!

authors: Ocramius alexpott


text:
Order not working

At this moment, options.order is not working. I have seen that sort function is using options.toc instead.
https://github.com/documentationjs/documentation/blob/6cbf4bd1d8945e7007ba925a2831ea6234123234/lib/sort.js#L15
Is there a different way to handle it? I can create a PR.

I think I can remove this option. If I do read this right -> https://github.com/documentationjs/documentation/blob/master/docs/CONFIG.md than all you have to do, is to put a documentation.yml in the source folder. Is that true?

Ok, better idea is to change it to the toc option. It's more flexible. Can you send a PR?

Pull request sent. #10

authors: SunboX davehg

repo: documentationjs/grunt-documentation


text:
Issue with generate_access_token

Is this supposed to be a deprecated method? This method doesn't seem to be returning the access token and is set to exit before then.
https://github.com/docusign/docusign-ruby-client/blob/master/lib/docusign_esign/client/api_client.rb#L573

Hi, Yes, we plan to deprecate method GenerateAccessToken in the future since it is better to use an OAuth client library such as OmniAuth.
At the same time, the method should work! I have submitted internal report DCM-4066

authors: LarryKlugerDS nadbm

repo: docusign/docusign-ruby-client


text:
WebpackError: ReferenceError: window is not defined

Bug Report
Describe the bug
Not able to generate build. Trying to deploy documentaiton live
A clear and concise description of what the bug is.
To Reproduce

docz build

FOR BUGS: Insert debug trace
 ERROR #95312

"window" is not available during server side rendering.

See our docs page for more info on this error: https://gatsby.dev/debug-html

  21 |  // to operate correctly into non-standard environments
  22 |  // @see https://github.com/webpack-contrib/style-loader/issues/177
> 23 |  return window && document && document.all && !window.atob;
     | ^
  24 | });
  25 |
  26 | var getTarget = function (target, parent) {

  WebpackError: ReferenceError: window is not defined

  - addStyles.js:23
    node_modules/style-loader/lib/addStyles.js:23:1

  - addStyles.js:12
    node_modules/style-loader/lib/addStyles.js:12:1

  - addStyles.js:80 ./node_modules/style-loader/lib/addStyles.js.module.exports
    node_modules/style-loader/lib/addStyles.js:80:1

  - buttons.scss?d045:16 Object.../src/components/Button/buttons.scss
    src/components/Button/buttons.scss?d045:16:82

  - index.js:1 Module.../src/components/Button/index.js
    src/components/Button/index.js:1:1

⠋ Building static HTML for pages
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

In order to allow us to quickly reproduce you issue please include a link to a reproduction repository.
Expected behavior
sucessful build
A clear and concise description of what you expected to happen..
Environment

OS: [e.g. OSX 10.13.4]
Node/npm version: [e.g. Node v10.15.3/npm 6.4.1]

This looks like one of your dependencies is expecting window to be there. However Gatsby renders your app using node to generate the markup and you can't expect window to be defined at all times.
More info here.

@BTARPAR Can you supply us with some more information about your project? Do you have a link to your project?
Looks like you are using sass, are you using some custom webpack config for it or are you running create-react-app?

@jesperorb  Yes I am using sass and for sass, I am using webpack loaders
{
test: /.(scss|css)$/,
use: [
'style-loader',
{
loader: 'css-loader',
options: {
modules: {
mode: 'local',
localIdentName: 'my-app__[local]'
}
}
},
'sass-loader'
]
}

I'm running into a similar problem. Here's a barebones repo with instructions on how to reproduce the error. Adding style-loader (in order to compile .scss files) seems to be the problem.
https://github.com/deammer/docz-test

Thank you @deammer 🙂
Try installing isomorphic-style-loader
yarn add isomorphic-style-loader --dev

And exchanging style-loader to isomorphic-style-loader in gastby-node.js:
exports.onCreateWebpackConfig = ({ actions }) => {
  const extraConfig = {
    module: {
      rules: [
        {
          test: /\.(scss)$/,
          use: ['isomorphic-style-loader', "css-loader", "sass-loader"]
        }
      ]
    }
  };

  actions.setWebpackConfig(extraConfig);
};

Not ideal but seems to work.

I replaced all my style-loader in webpack , and gatsby-node.js but still giving me the same error

Did you try removing .docz-folder after you installed the new package and replaces your webpack config?
That package worked in @deammer repo so I thought it would work for you. You can try if this works (i haven't tried it):
Install gatsby-plugin-sass
yarn add node-sass gatsby-plugin-sass

Create a gatsby-config.js in your root with the following:
module.exports = {
 plugins: [`gatsby-plugin-sass`]
}

And remove your your rules for scss in your webpack config.

@jesperorb  I've tried the way you mentioned in the previous comment. But I am getting GRAPHQL ERROR

Same error on the when I do docz dev

@BTARPAR Check this issue and see if any solutions in the issue helps: https://github.com/doczjs/docz/issues/1007

@jesperorb thank you for your help! I didn't like the isomorphic-style-loader because it required extra code to work properly. Using gatsby-plugin-sass worked best.

@jesperorb  I've tried to follow that issue but still, no luck  getting the same error with the 404 page

Is this success build?

I was able to do docz dev  "docz": "^2.0.0-rc.42" but when I upgrade it to "docz": "^2.0.0-rc.53", I am not able to docz dev and also got GRAPHQL ERROR

Hey @BTARPAR
Does "docz": "^2.0.0-rc.52" work ?
Also can you copy the output of the command below
rm -rf node_modules yarn.lock .docz && yarn add docz@next && yarn docz dev

I've checked 42,44 to 53 with below command non of them worked. (I'll try one more time with your command)
rm -rf node_modules yarn.lock .docz &&  yarn docz dev

@rakannimer I've tried your command with "docz": "^2.0.0-rc.52" but did not work have the same error GRAPHQL (https://github.com/doczjs/docz/issues/1118#issuecomment-539160355)

can you copy the output here of the command below

rm -rf node_modules yarn.lock .docz && yarn add docz@next && yarn docz dev

I think we need more information to be able to properly help instead of guessing.
Could you provide a repository with a minimal reproduction of your problem and we can continue working from there ?

@rakannimer sure, I'll do that this weekend and let you know

@rakannimer @jesperorb here is a repo, where u was able to reproduce the error
https://github.com/BTARPAR/DOCZ

@BTARPAR can you please check https://github.com/BTARPAR/DOCZ/pull/1
It fixes the GraphQL error you referenced. After that the build fails because of some directories you did not include in the demo like config.

@rakannimer updated the repo you can find the missing file now

Your repo is working correctly on my side after removing gatsby-theme-docz 1.2.0
What's the error you're getting ?

Ii am getting the error mentioned on the top

Did you try the PR I referenced : BTARPAR/DOCZ#1 ?

docz dev this worked for me as well try to do docz build

I tried @jesperorb's solution of replacing style-loader with isomorphic-style-loader and building using it works.

Merge https://github.com/BTARPAR/DOCZ/pull/2
pull from master
rm -rf .docz && yarn docz build

Yes, it worked for me as well let me see how it goes on my main project. Since this project works with docz I'll try to move my old stuff here and see how it goes. Wish me luck @rakannimer

Hey @BTARPAR
Did you get the chance to confirm docz works with your codebase ?

Good News latest version worked guys. It still has the issue but that definitely looks like on my side but build worked and dev also worked. I am closing this issue for now. If anything come up I'll let you know guys.
Thank You @rakannimer @jesperorb  for this

Same error, I have components using window, I cannot import them because of the SSR done by gatsby, I've tried their workaround in the documentation, nothing has worked so far.

I'm also in a situation like this, I want to use cytoscape-dagre and having an import error:
   8 | 	else
   9 | 		root["cytoscapeDagre"] = factory(root["dagre"]);
> 10 | })(window, function(__WEBPACK_EXTERNAL_MODULE__4__) {
     |  ^
  11 | return /******/ (function(modules) { // webpackBootstrap
  12 | /******/ 	// The module cache
  13 | /******/ 	var installedModules = {};

  WebpackError: ReferenceError: window is not defined

  - cytoscape-dagre.js:10
    node_modules/cytoscape-dagre/cytoscape-dagre.js:10:2

I'm also in a situation like this, I want to use cytoscape-dagre and having an import error:
   8 | 	else
   9 | 		root["cytoscapeDagre"] = factory(root["dagre"]);
> 10 | })(window, function(__WEBPACK_EXTERNAL_MODULE__4__) {
     |  ^
  11 | return /******/ (function(modules) { // webpackBootstrap
  12 | /******/ 	// The module cache
  13 | /******/ 	var installedModules = {};

  WebpackError: ReferenceError: window is not defined

  - cytoscape-dagre.js:10
    node_modules/cytoscape-dagre/cytoscape-dagre.js:10:2

in my case: https://www.gatsbyjs.com/docs/debugging-html-builds/#fixing-third-party-modules works.

Working Solution after spending 3 hours
"dependencies": {
"docz": "^2.3.1",
"gatsby-plugin-sass": "^3.2.0",
........
},
// gatsby-config.js
module.exports = {
// To fix the SCSS Errors
plugins: [gatsby-plugin-sass],
// This has impressed me a lot
flags:{
DEV_SSR:false
}
}

authors: BTARPAR deammer jesperorb nitin- rakannimer tquiroga wilkerlucio yes1am

repo: doczjs/docz


text:
[!!Leaked~video*]~ Pragya-Nagra.Viral.Video.Original

37 seconds ago.....
►✅ 🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 ❤❤⬇⬇
►✅ 𝘾𝙇𝙄𝘾𝙆 𝙃𝙀𝙍𝙀 ==►► DOWNLOAD HERE ❤❤⬇⬇
WATCH NOW

L𝚎aked Video Pragya Nagra video Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
Pragya Nagravideo Original Video video took the internet by storm and amazed viewers on various social media platforms.Pragya Nagravideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoPragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter
Pragya Nagravideo Original Video video oficial twitter
L𝚎aked Video Pragya Nagra video Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
Pragya Nagra video-video
.
.
.
.
.
.
37 seconds ago.....
►✅ 🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 ❤❤⬇⬇
►✅ 𝘾𝙇𝙄𝘾𝙆 𝙃𝙀𝙍𝙀 ==►► DOWNLOAD HERE ❤❤⬇⬇
WATCH NOW

L𝚎aked Video Pragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
Pragya Nagravideo Original Video video took the internet by storm and amazed viewers on various social media platforms.Pragya Nagravideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoPragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter
Pragya Nagravideo Original Video video oficial twitter
L𝚎aked VideoPragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.37 seconds ago.....
►✅ 🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 ❤❤⬇⬇
►✅ 𝘾𝙇𝙄𝘾𝙆 𝙃𝙀𝙍𝙀 ==►► DOWNLOAD HERE ❤❤⬇⬇
WATCH NOW

L𝚎aked Video Pragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Pragya Nagravideo Video Original Video LinkPragya Nagravideo Video Viral On Social Media X Trending Now
Pragya Nagravideo Original Video video took the internet by storm and amazed viewers on various social media platforms.Pragya Nagravideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoPragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter
Pragya Nagravideo Original Video video oficial twitter
L𝚎aked VideoPragya Nagravideo Original Video Viral Video L𝚎aked on X Twitter..
.
.

.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.

authors: havanaohnaa sgravejuli


text:
+![𝟐𝟎𝟐𝟒-𝐯𝐢𝐫𝐚𝐥!𝘃𝗶𝗱𝗲𝗼𝘀]* Sean Diddy Video Original Video Link Sean Diddy Video Viral On Social Media X Trending Now

#![XXX FULL Video]— A Video Original Video Link  Sean Diddy Video Viral On Social Media X Trending Now
21 seconds ago
L𝚎aked Video  Sean Diddy Original Video Viral Video L𝚎aked on X Twitter Telegram
..
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full  Sean Diddy Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 ( Sean Diddy Viral Video Link)
..
[-wATCH-]—  Sean Diddy Video Original Video Link  Sean Diddy Video Viral On Social Media X Trending Now
[-wATCH-]—  Sean Diddy ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—  Sean Diddy ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—  Sean Diddy Video Original Video Link  Sean Diddy Video Viral On Social Media X Trending Now
Sean Diddy Original Video video took the internet by storm and amazed viewers on various social media platforms.  Sean Diddy, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video  Sean Diddy Original Video Viral Video L𝚎aked on X Twittera
Sean Diddy Original Video video oficial twitter
L𝚎aked Video  Sean Diddy Original Video Viral Video L𝚎aked on X Twitter..yjhgrdafassf
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full  Sean Diddy Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 ( Sean Diddy Viral Video Link)
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
..
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full  Sean Diddy Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 ( Sean Diddy Viral Video Link)
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link

 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 Viral Video Link
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 Viral Video Link

 🟢 WATCH NOW 🌐 ➤ ➤ ➤ CLICK HERE 𝖳𝗈 𝗅𝗂𝗇𝗄
 🔴 WATCH NOW 👉👉 ➤► ➤► Viral Video Link
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.


text:
[feat] Development Guideline & Documentation and Development Environment in VM

Feature Request
Describe the Feature Request
There are many good C/C++ programmers out there but setting up the development environment is always the tedious stage. There is need to provide good documentation and environment VM to speed up the adaptation to let developers jump into development in a quicker way.
Describe Preferred Solution
-Provide step-by-step: how to start the dev,  how to setup the development environment
-Use good documentation website such as https://readthedocs.org/
-Provide a development VM that pre-setup and configured for Dogecoin development use.
-Use of docker, etc.

Writing a Dockerfile for a bare-bones Linux image wouldn't be too bad and could provide some value. That might leave Windows and Mac developers out, but it's a start.

https://github.com/vertiond/DockerDOGE

It would be helpful to have the blockchain/bdb files as a mountable directory from your local filesystem, or have a sidecar image that isolates state from the main wallet container. This would greatly benefit people who want a simple way to run their doge node and update it without having to re-download the chain / backup their keys etc..

https://github.com/vertiond/DockerDOGE

Thanks for the info. Glad to know there is such there.

Writing a Dockerfile for a bare-bones Linux image wouldn't be too bad and could provide some value. That might leave Windows and Mac developers out, but it's a start.

Totally!

It would be helpful to have the blockchain/bdb files as a mountable directory from your local filesystem, or have a sidecar image that isolates state from the main wallet container. This would greatly benefit people who want a simple way to run their doge node and update it without having to re-download the chain / backup their keys etc..

This is an issue with these traditional blockchain design. The files got bigger every time. Need a more efficient way to handle this to be more sustainable.

repo: dogecoin/dogecoin


text:
Fix some python RPC tests

This includes bitcoin/bitcoin@49d86c7477ba1dbbbd08f452d0e7d710b22bad92. smartfee.py is still broken though and I can't really get what it's supposed to test anyway. I also hate python :)

Travis cancelled for obvious reasons.


text:
Dogecoin is a fork of Bellscoin

Please update the following statement:
‘ Dogecoin was originally a fork of a cryptocurrency called Luckycoin - itself a fork of Litecoin.’
Found here:
https://dogecoin.com/dogepedia/faq/dogecoin-has-no-developers/
Billy Markus specifically mentions Bellscoin which is a fork of Luckycoin as the direct fork of Dogecoin.
References:

https://x.com/billym2k/status/1732424915528417602?s=46
https://x.com/billym2k/status/1643063317781680131?s=46
https://www.youtube.com/watch?v=lWxXwZ6abhA&t=419s
https://x.com/billym2k/status/1735062601548398794?s=46

https://github.com/LuckycoinFoundation/Luckycoin/blob/master/src/main.cpp#L846
vs
https://github.com/Nintondo/bellscoinV3/blob/main/src/validation.cpp#L1771
vs
https://github.com/dogecoin/dogecoin/blob/master/src/dogecoin.cpp#L133
Sorry, Dogecoin is a fork of Luckycoin, and not Bells.
This is because in Bells, the prevhash didn't influence the random reward unlike Luckycoin AND Dogecoin, and thus it cannot have been forked from that ❤

So Billy is lying?
I also this on Reddit:
https://www.reddit.com/r/dogecoin/comments/js2o07/comment/gbwud5u/
Also, why are you referencing a file on Dogecoin where the oldest commit was in 2018.
Lastly, why did you referenced Bellsv3 instead of the OG one:
https://github.com/bellscoin/bellscoin/tree/master

https://github.com/LuckycoinFoundation/Luckycoin/blob/master/src/main.cpp#L846
vs
https://github.com/Nintondo/bellscoinV3/blob/main/src/validation.cpp#L1771
vs
https://github.com/dogecoin/dogecoin/blob/master/src/dogecoin.cpp#L133
Sorry, Dogecoin is a fork of Luckycoin, and not Bells.
This is because in Bells, the prevhash didn't influence the random reward unlike Luckycoin AND Dogecoin, and thus it cannot have been forked from that ❤

So Billy is lying? I also saw this on Reddit: https://www.reddit.com/r/dogecoin/comments/js2o07/comment/gbwud5u/ Via this tweet by a Dogecoin Foundation Dev: https://x.com/inevitable360/status/1677596792588828672?s=46
Also, why are you referencing a file on Dogecoin where the oldest commit was in 2018. Lastly, why did you referenced Bellsv3 instead of the OG one: https://github.com/bellscoin/bellscoin/tree/master

Hello, sorry but @patricklodder is right, my Post on X.com is not entirely correct.

So there are 2 Dogecoin devs that are saying:
“Billy Markus is lying, that Dogecoin was a fork of Bells.”
Got it.

If you guys think that is the only reason I am requesting a correction on the main site, “to pump my bags” then you don’t really know who I am.
I am merely trying to spread awareness and making sure the right information is being shared. Unlike what this revival of Luckycoin is doing.
Isn’t that what this statement is on the site mean?:
“ Let’s fight against the disinformation surrounding Dogecoin! Much wow!”
In any case, I will go ahead and close this. Apologies if I had offended anyone.

Here is the summary of my research on Bellscoin being forked to create Dogecoin:

The Genesis Block message is the same: https://x.com/ZachZwei/status/1862512487868112906
The Bellscoin logo on the Dogecoin Client: https://x.com/ZachZwei/status/1862897218107453770
AI comparing repos of Luckycoin, Bellscoin and Dogecoin to explain lineage: https://x.com/ZachZwei/status/1863226678740492632

Sources:
main.cpp file for all coins mentioned (oldest versions available):
https://github.com/maxpwr/Luckycoin/blob/master/src/main.cpp
https://github.com/bellscoin/bellscoin/blob/master/src/main.cpp
https://github.com/dogecoin/dogecoin/blob/8b09dc5d711bc0bedefc29c199a79ce39f691558/src/main.cpp
Bellscoin Logo on Dogecoin client (v1.0) video:
https://x.com/ZachZwei/status/1863270288974344270
bitcoin.icns file link:
https://github.com/dogecoin/dogecoin/blob/8b09dc5d711bc0bedefc29c199a79ce39f691558/src/qt/res/icons/bitcoin.icns

authors: qlpqlp zachzwei


text:
Thrown error

Just wanted you to inform you about an error being thrown:

Error
73050.ed28c446e39c70b0c6c0.js:1 [BetterDiscord] [Patcher] Could not fire after callback of renderAttachments for ECBlocks TypeError: res.props.attachments is not iterable
    at Object.eval [as callback] (EnhanceCodeBlocks.plugin.js:976:47)
    at eK.<anonymous> (renderer.js:5:23163)
    at eK.render (8ffaad5d94980deea02d.js:1:306846)
    at o_ (44076.b5f9426088ebaff2b53a.js:12:914886)
    at og (44076.b5f9426088ebaff2b53a.js:12:914684)
    at u (44076.b5f9426088ebaff2b53a.js:12:956156)
    at sB (44076.b5f9426088ebaff2b53a.js:12:938190)
    at 44076.b5f9426088ebaff2b53a.js:12:938056
    at sF (44076.b5f9426088ebaff2b53a.js:12:938064)
    at sT (44076.b5f9426088ebaff2b53a.js:12:933101)
    at x (44076.b5f9426088ebaff2b53a.js:12:1125228)
    at A (44076.b5f9426088ebaff2b53a.js:12:1125758)
    at D.<computed> (44076.b5f9426088ebaff2b53a.js:1:500866)
    at M (44076.b5f9426088ebaff2b53a.js:1:500631)
    at MessagePort.k (44076.b5f9426088ebaff2b53a.js:1:500690)
t.<computed> @ 73050.ed28c446e39c70b0c6c0.js:1
(anonymous) @ VM10476 43455.8c79ce3e1753b38de4a4.js:23
_log @ renderer.js:5
err @ renderer.js:5
(anonymous) @ renderer.js:5
render @ 8ffaad5d94980deea02d.js:1
o_ @ 44076.b5f9426088ebaff2b53a.js:12
og @ 44076.b5f9426088ebaff2b53a.js:12
u @ 44076.b5f9426088ebaff2b53a.js:12
sB @ 44076.b5f9426088ebaff2b53a.js:12
(anonymous) @ 44076.b5f9426088ebaff2b53a.js:12
sF @ 44076.b5f9426088ebaff2b53a.js:12
sT @ 44076.b5f9426088ebaff2b53a.js:12
x @ 44076.b5f9426088ebaff2b53a.js:12
A @ 44076.b5f9426088ebaff2b53a.js:12
D.<computed> @ 44076.b5f9426088ebaff2b53a.js:1
M @ 44076.b5f9426088ebaff2b53a.js:1
k @ 44076.b5f9426088ebaff2b53a.js:1

I pushed a fix couple days ago, you just need to download it from github

Awesome!
Sorry for wasting your time then xd

authors: TheBlackEntity doggybootsy

repo: doggybootsy/enhancecodeblocks


text:
Squad freezes Nvidia driver: "NVRM: Xid 31 (...) ACCESS_TYPE_VIRT_WRITE"

Squad causes random but frequent freezes where the Nvidia kernel driver spews one specific error message, and Squad's (i.e., UE4's) GPU thread becomes unresponsive until the game's own watchdog kills the process 2-3 minutes later. During this time the WM is practically unusable, suffering from a lag of 1+ minutes per keystroke.
The driver error is exactly the same line every time, except of course for the pid:

NVRM: Xid (PCI:0000:2d:00): 31, pid=970, Ch 00000023, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_RAST faulted @ 0x0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_WRITE

If I set the game's internal frame limit slider to 60-ish to match my monitor's refresh rate the freezes become rare enough that I may be able to play a few hours without one. But if I set the limit to the max (which is 240 i.e. practically unlimited in my case) it's guaranteed to freeze within 10 minutes or so.
I've found at least two situations where the freeze is significantly more likely to occur than otherwise. One is when the game is changing maps, seems to be the loading of a new map that often causes it. The other situation is more interesting because it's brought on by user action: simply clicking on the role loadout tab in the deployment menu is practically guaranteed to freeze the game then and there.
The freeze will occasionally happen with no obvious trigger, too.
I'll try to upload logs here as soon as I have a moment.
Software information

Squad a-15.4.5.19500-4.21.2-SHIPPING.
Steam Proton. Tested with all recent upstream releases as well as own builds with updated Wine versions.
Debian unstable + i3, no compositor in use.
Linux 5.2.9-ck1 with fsync patches.

System information

GPU: Nvidia RTX 2080
Driver: 418.52.20. Tested several recent Vulkan beta drivers in the 418.52.x series.
Wine version: Tested with Protonified builds of 4.2, 4.11, 4.12.1, and 4.13.
DXVK version: Everything from at least v1.3 up to master exhibit the behavior. Older versions not tested.

Apitrace file(s)

N/A

Log files

Will upload these fairly soon.

I don't have the game, so I'll need an apitrace to debug this.
Does disabling "Allow Flipping" in nvidia-settings fix your issue?

I don't have the game

What's your Steam ID?

so I'll need an apitrace to debug this.

I'll see what I can do.

Does disabling "Allow Flipping" in nvidia-settings fix your issue?

No, I have all the known tricks such as flipping settings applied and tested through countless times at this point.

To be clear, unless it's obvious that DXVK does something invalid, I cannot really debug GPU hangs on Nvidia drivers at all, so there's probably not much I could do even if I had the game.
Can you run the game with VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation and post the full console output? This requires you to have a recent version of the Vulkan SDK/validation layers installed.

To be clear, unless it's obvious that DXVK does something invalid, I cannot really debug GPU hangs on Nvidia drivers at all, so there's probably not much I could do even if I had the game.

Understood.

Can you run the game with VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation and post the full console output? This requires you to have a recent version of the Vulkan SDK/validation layers installed.

Alright, I'll do this probably tomorrow, I hope.

@imaami Assuming that you have an IOMMU, does it work if you disable your IOMMU?

@imaami
I bought this game a couple of days ago, but have not been able to get this to crash. I have not played for "hours on end", but mostly various practice fields and a few maps online.
I did however notice that DXVK had allocated just > 8GB at times, but mostly hovers around 7-7.2GB when everything setting is "Epic +". Not sure if the game could have some sort of memory leak or whatnot, cos it tends to start off around 5GB and grow. I did not crash tho.
Any particular setting you use when this happens? My RTX2070 card is not able to push more than around 50-55fps at those settings (and 8GB allocated/6-7GB used).

I think it depends a lot on the map? Huge maps at high settings = vram spending like crazy. I was watching DXVK hud when i crashed, and it had 9.6GB allocated, and 8.8GB vram used. nvidia-smi said the game used just above 7GB (total 7902/7949).
I think it would be somewhat expected to crash in a situation like that? (It happened just as i the game switched map)
Caused no XID error, so i guess it was just a vram allocation crash (and rightfully so).

@SveSop, video memory being full is not an abnormal situation. This shouldn't be producing crashes.
imaami captured an Apitrace which with I have managed to reproduced at least one bug consistently. This is not the bug being reported, but I have reason to believe they are related.

imaami captured an Apitrace which with I have managed to reproduced at least one bug consistently. This is not the bug being reported, but I have reason to believe they are related.

Proof that I've in fact not as lazy at it seems. ;) Just bad at updating tickets.

Try disabling IOMMU support in your kernel (or BIOS in case it has such a setting)... It may be on by default. When it's causing problems, it's likely during concurrent IO across a variety of devices in your system. @ryao already suggested to try disabling it.

I do not seem to be using IOMMU. (Intel vt-d disabled in the bios)
dmesg|grep -i iommu
[    4.987552] vboxpci: IOMMU not found (not registered)

sudo find /sys |grep dmar does not find anything either.

Try disabling IOMMU support in your kernel (or BIOS in case it has such a setting)... It may be on by default. When it's causing problems, it's likely during concurrent IO across a variety of devices in your system. @ryao already suggested to try disabling it.

I did try disabling IOMMU, no effect.

There is a bug in our Vulkan driver where, when video memory is full, certain internal allocations can fail in video memory without a fallback in system memory, which at least triggers one kind of error and could conceivably be the cause of the error seen by @imaami. Fix is in progress, I will update this bug when a release carrying the fix is available.

@ahuillet Would that be fixed by 435.19.03?
    Fixes:
        Fixed a bug which caused corruption in the following DXVK titles:
            Saints Row IV
            Saints Row: The Third
        Fall back to system memory when video memory is full for some driver-internal allocations.
            This can help fix Xid 13 and Xid 31 cases when video memory is full.

https://developer.nvidia.com/vulkan-driver

@pchome @imaami @foresto @buscher @MinIsMin You might want to try out the new driver to see if it improves things for you.

Yes, that driver release should fix this issue.

I see the fix was noticed before I could announce it here. Please test this new driver release to confirm it fixes the problem.

Unfortunately the system I used doesn't work anymore due to a hardware error, so I can't test it. Sorry.

I just had the most awesome Squad match in a long time. Ended 1-0. No freezes or crashes during these past 2-3 hours with the new driver.
This isn't confirmation yet because the bug has been probabilistic from the beginning. I'd say if I don't get freezes in the next 3 days from now it's likely that it's fixed.

I tested too using the tutorial. There were no discernible issues.

Can you guys test the new NVIDIA vulkan beta driver released today? (Linux 435.19.03)
https://developer.nvidia.com/vulkan-driver
it fixed my problems with alt-tab on GTA V (because i was running out of VRAM)
Fixes:
Fixed a bug which caused corruption in the following DXVK titles:
Saints Row IV
Saints Row: The Third
Fall back to system memory when video memory is full for some driver-internal allocations.
This can help fix Xid 13 and Xid 31 cases when video memory is full.

I spent 3 hours testing Squad with the new driver. I cannot reproduce the issue with it on my GTX 1070. This seems to be fixed. :)

Thanks for testing, I'll consider this resolved then.

Thank you imaami for providing the apitrace that let us diagnose the problem!

I have this issue with 455.28 version in Borderlands 3. Before nvidia driver update i haven't this hangs so perhaps it's went back? Can someone confirm?

(Sorry for posting to a closed issue that's most likely unrelated to DXVK but :shrug:)

I have this issue with 455.28 version in Borderlands 3. Before nvidia driver update i haven't this hangs so perhaps it's went back? Can someone confirm?

Two other people have recently reported crashes with a Xid 31 error in Squad (https://github.com/ValveSoftware/Proton/issues/938#issuecomment-703769378, https://github.com/ValveSoftware/Proton/issues/938#issuecomment-706672103). That would make yours the third one.
@ahuillet might want to keep an eye out for a regression in 455.y memory management code. Very similar symptoms, it seems.

Confirming on 455.28 with multiple games (both dx9 and dx11).
This may be somehow related to gnome-shell - unchecking "Allow the WM to control the windows" in winecfg seems to remove the hang / Xid 31 for me.

It turn out that my problem go away with new proton-experimental and i guess it's was something window management related. And i am experienced it only on gnome-shell/muter, other WM's without compositing was fine.

authors: MinIsMin SveSop ahuillet doitsujin gasinvein imaami kakra kassindornelles ryao sven337 tim77

repo: doitsujin/dxvk

license: Zlib


text:
[d3d9] The First Templar has lighting issues, not present with wined3d

Software information
The First Templar, GOG copy, all settings set to maximum possible
System information

GPU: 7900 XTX
Driver: Mesa 24.2.3
Wine version: Proton Experimental
DXVK version: Whatever Experimental has as of now

Apitrace file(s)
wined3d trace:
https://drive.google.com/file/d/1Et4a9dbP9nOk7I3Nfkv8muZcozK26lhh/view?usp=sharing
dxvk trace:
https://drive.google.com/file/d/1PSOT1wePe9PWaDDG6_iLywewEsvOpWmp/view?usp=sharing
Log files
Proton log:
steam-heroic-The First Templar.log
Shows a bunch of:
err:   DxvkContext: copyImageFb: Unsupported operation:
err:     srcFormat = VK_FORMAT_D32_SFLOAT_S8_UINT (aspect 6)
err:     dstFormat = VK_FORMAT_D32_SFLOAT (aspect 2)

Screenshots that shows the issue

90 @0 IDirect3DDevice9::CreateDepthStencilSurface(this = 0xd4240f0, Width = 2560, Height = 1440, Format = D3DFMT_D24S8, MultiSample = D3DMULTISAMPLE_NONE, MultisampleQuality = 0, Discard = TRUE, ppSurface = [0xd4c6430], pSharedHandle = NULL) = D3D_OK
89 @0 IDirect3DDevice9::CreateTexture(this = 0xd4240f0, Width = 2560, Height = 1440, Levels = 1, Usage = D3DUSAGE_DEPTHSTENCIL, Format = D3DFMT_DF24, Pool = D3DPOOL_DEFAULT, ppTexture = [0xd4c92e8], pSharedHandle = NULL) = D3D_OK

10533570 @0 IDirect3DDevice9::SetDepthStencilSurface(this = 0xd4240f0, pNewZStencil = 0xd4c6430) = D3D_OK
10561899 @0 IDirect3DDevice9::SetTexture(this = 0xd4240f0, Stage = 0, pTexture = 0xd4c92e8) = D3D_OK // RESZ

Referenced PR fixes the issue. Thanks for the quick fix.


text:
[d3d9] Ignore modes with refresh rates under 60 Hz

Also fixes #4288. Still not the shadows, they're fine.
An alternative to #4414, and IMHO a better way to address the problem the game has, while keeping with ascending ordering, which seems to have been respected on Windows XP at least, is to simply ignore modes with refresh rates under 60 Hz.
I've taken the liberty of adding a config option to revert to the old behavior, for purists, but the filtering gets enabled by default.

50 Hz is the default refresh rate in most of Europe and many other countries. Are you sure disabling that by default is a wise choice?

Here are some sample outputs on Windows XP, using olden GPUs:
d3d8-triangle_WinXP_ATI_HD4650_8.65.txt
d3d8-triangle_WinXP_Nvidia_GF4_45.23.txt
d3d8-triangle_WinXP_Nvidia_FX5500_93.71.txt
Are you connecting your modern GPU to an analogue CRT for that authentic retro experience? That's nice, but also not typical for the average dxvk use-case. Still there's a config option you can use in case you want to have access to absolutely all the modes exposed by your monitor.

Not sure if this is such a great idea to begin with, but if we do go for it, this absolutely needs a safeguard to report the mode with the highest refresh rate for each resolution, even if said mode is < 60.

After some debate, it was agreed #4414 is less invasive, so we should go with that and hope nothing regresses. Though if WineD3D is sorting modes descending by refresh rate anyway, I guess it should be fine.

authors: PatrickvL WinterSnowfall doitsujin


text:
Unable to Join Guild

Summary
Unable to join guild
Reproduction Steps
My selfbot is unable to join a guild, I get the error "Bad Request"
Code
No response
Expected Results
Should Join a server via the invite
Actual Results
Saying "400 Bad Request"
System Information

Python v3.8.12-final
discord.py-self v1.9.2-final
aiohttp v3.7.4.post0
system info: Linux 5.15.0-1016-gcp #21~20.04.1-Ubuntu SMP Fri Aug 5 12:53:07 UTC 2022

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
No response

Maybe this is related to a captcha issue

Yes it is. Install the alpha, and use a captcha handler.

authors: Dart2004 dolfies tcrms