text:
Rename 'Fds' to 'File Descriptors' in docker info

This makes the docker info more readable. Also change a log line
in a test file renaming Fds
Signed-off-by: Ankush Agarwal ankushagarwal11@gmail.com

LGTM

LGTM, thanks!

@tiborvass  is this one really ok to do given people may be parsing it (its a UX change instead of a bug)?

@duglin good point... I'm not sure... @crosbymichael what do you think?

Can we provide a inspect like output for info when an additional option is passed like docker -j info

@ankushagarwal I'm not sure I understand what docker -j info means.
The /info API didn't change, it's only the displaying that changed which could be parsed by shell scripts. I don't know, I sorta think it's okay.

I think a note should be added in the release notes, for those that do parse the output.
On the other hand; is the CLI output considered a stable API? If not, the docs should include a general note that states that CLI output is not a stable API and cannot be relied on for parsing. A section with examples on how to use the remote API in shell-scripts could be nice there (may be a nice Bday Party task as well)

Since Docker doesn't make a clear distinction between machine-readable output and human-readable output, we kind of have to assume any of it can, and will, be machine parsed.  So to me, unless we consider this a bug, I don't think we should be changing the output on people in a dot-release.
@crosbymichael - need your thoughts on this.

@tiborvass : I am sorry if I wasn't clear. I was proposing adding a -j (j for json) option to the info command. The -j option produces a machine readable output which can be parsed, but I guess they can talk to the server at /info to get a machine readable output. Or a general -j (or some other appropriate letter) option across the docker cli commands which just spits out the server's response as is.
@duglin : The motivation for this change was that Fds was very unclear in a human readable output and it was documented nowhere in the code that Fds means File Descriptors.
People shouldn't be relying on docker client's human readable output, they should be talking to the server at /info directly. But, I do agree that this can potentially break things.

People should use the API /info if they want machine readable, and guarantee on output format.

authors: ankushagarwal duglin icecrime thaJeztah tiborvass


text:
Windows: Factoring out unused fields

Signed-off-by: John Howard jhoward@microsoft.com
@swernli
This PR is part of the proposal described in docker/docker issue 10662 to port the docker daemon to Windows. This PR addresses a lot of "TODO Windows" by refactoring many platform specific fields which were still common across all platforms into the right place. This includes
-- daemon\config: CorsHeaders; EnableCors
-- daemon\container: ResolvConfPath; HostnamePath; HostsPath; UpdateDns; MountPoints; Volumes; VolumesRW
-- daemon\inspect ContainerJSONBase
-- reworking of daemon\create due to above
-- reworking of daemon\volume due to above (there is more to do here, but I'm trying to limit the size of the PR)

It looks good at first glance. I don't know if createPlatformSpecific is too abstract.

I was trying to be concise :) But next push will update it to createContainerPlatformSpecificSettings

Rebase from hell completed :)

oh, gosh. I'm very sorry. Changes LGTM.

:( needs rebasse

ping me after :)

Rebased. Waiting for CI to complete.

ok only seems to be failing on stupid urandom, LGTM, merging

source: gharchive/pull-request

authors: calavera jfrazelle jhowardmsft

repo: docker/docker

license_type: permissive

license_source: github-api


text:
Don't set ulimits (nproc, nfile) for all init scripts

There is a not-insignificant performance overhead for all containers (if
containerd is a child of Docker, which is the current setup) if rlimits are
set on the main Docker daemon process (because the limits
propogate to all children).
We recommend using cgroups to do container-local accounting.
This applies the change added in 8db61095a3d0bcb0733580734ba5d54bc27a614d
to other init scripts.
relates to https://github.com/docker/docker/pull/24307
ping @justincormack @tianon @runcom @cyphar PTAL if this looks good to you; I didn't know the best way to verify/test this, but can try if you agree on this

LGTM!

LGTM

unlimited is still a number, just that it's a really high number.

@cpuguy83 is there a way to set no limit? If setting unlimited does still apply a limit, I wonder if https://github.com/docker/docker/pull/24307 (and this PR) has any benefits.
@cyphar did you benchmark the difference before/after applying https://github.com/docker/docker/pull/24307?

@thaJeztah According to the reporter of the bug, their benchmark time almost halved (from ~130 minutes to ~80) after setting the ulimits to be unlimited.

@cpuguy83 The special value RLIM_INFINITY is used by the kernel to mean "no limit". It is not the same as using a different very large number.

@cpuguy83 It looks like for RLIMIT_NOFILE Linux doesn't use RLIM_INFINITY as a special value specifically for the fastpath. So I'm not really sure why there is a performance impact -- it might be some weird quirk of rpm that causes this to happen.

In fact you don't appear to be able to set RLIMIT_NOFILE to unlimited anyway:
ulimit -n unlimited
bash: ulimit: open files: cannot modify limit: Operation not permitted

It is bounded by /proc/sys/fs/file-max. So that line is not doing anything at all. So it can only be the process limit that is having an effect, if anything there will probably be a lower file limit than before as it was not being raised.

@justincormack hm, that's weird I think it tried that, but maybe I messed up and only tried on ulimit -u :blush: I see the man page mentions;

-n     The maximum number of open file descriptors (most systems do not allow this value to be set)

Looks like you can only set a numeric value, that's lower or equal to 1048576, but not a higher one;
ulimit -n 1048576

ulimit -n 1048577
bash: ulimit: open files: cannot modify limit: Operation not permitted

but that limit doesn't match /proc/sys/fs/file-max;
cat /proc/sys/fs/file-max
398153

I'm trying that in a container, so possibly that's related there

So, does setting LimitNOFILE=infinity in systemd work? And why? Or is it silently ignored?

Try it outside a container, docker may already have that limit set...
On 13 Jul 2016 12:51 p.m., "Sebastiaan van Stijn" notifications@github.com
wrote:

@justincormack https://github.com/justincormack hm, that's weird I
think it tried that, but maybe I messed up and only tried on ulimit -u 😊
I see the man page mentions
http://man7.org/linux/man-pages/man1/bash.1.html;
-n The maximum number of open file descriptors (most systems do not allow
this value to be set)
Looks like you can only set a numeric value, that's lower or equal to
1048576, but not a higher one;
ulimit -n 1048576
ulimit -n 1048577
bash: ulimit: open files: cannot modify limit: Operation not permitted
but that limit doesn't match /proc/sys/fs/file-max;
cat /proc/sys/fs/file-max
398153
I'm trying that in a container, so possibly that's related there
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/24555#issuecomment-232332677, or mute
the thread
https://github.com/notifications/unsubscribe/AAdcPMGGjZNiOldl4tMntHJAMjmyyWjyks5qVNE-gaJpZM4JK1Uw
.

nope, looks to be the same;
root@dockr:~# ulimit -n 1048576
root@dockr:~# ulimit -n 1048577
-bash: ulimit: open files: cannot modify limit: Operation not permitted
root@dockr:~# ulimit -n unlimited
-bash: ulimit: open files: cannot modify limit: Operation not permitted

cat /proc/sys/fs/file-max
100809

ok that limit is hardcoded http://stackoverflow.com/questions/1212925/on-linux-set-maximum-open-files-to-unlimited-possible

Updated to only set nproc, and updated the systemd unit file accordingly; @cyphar can you confirm if setting LimitNOFILE=infinity actually worked? The systemd documentation seems to indicate it accepts the same values as ulimit -n; https://www.freedesktop.org/software/systemd/man/systemd.exec.html#id-1.7.2.29.17.3

LGTM

LGTM

@thaJeztah LimitNOFILE=infinity definitely works. I'm currently running a Docker daemon with that limit set.

authors: LK4D4 cpuguy83 cyphar justincormack thaJeztah tianon


text:
Windows: Set correct root path logic

Signed-off-by: John Howard jhoward@microsoft.com
Fixes a correctness issue after discussion with @swernli. Only set the Root.Path in the OCI spec on Windows if the container is NOT a Hyper-V Container.
Also set the Root.Readonly to false explicitly, as a read-only root FS is not supported on Windows.
@swernli PTAL.

LGTM

@thaJeztah @vdemeester

authors: jhowardmsft swernli


text:
Add random-assign to poule.yml

Randomly assign incoming pull requests to one of the (Docker Inc employed) maintainers of the project.
The role of the assignee is not necessarily to review the pull request herself/himself, but to be accountable for moving it forward.
Cc @vieux @thaJeztah.

LGTM 👍

Closing this as we're having a debate with @tonistiigi about giving it a threshold before assigning (e.g., if it's still opened after 1 week).

authors: icecrime vieux


text:
Fix TestAPIDockerAPIVersion on windows

Fixing my own mistake 😅.
PS: this causes all windowsRS1 build to fail (master, PRs) so, should be merged quick 👼 🙏
/cc @thaJeztah @AkihiroSuda @johnstep
🦁
Signed-off-by: Vincent Demeester vincent@sbr.pm

windowsRS1 is green 💚

Janky failed on 09:16:10 FAIL: docker_cli_push_test.go:608: DockerRegistryAuthTokenSuite.TestPushMisconfiguredTokenServiceResponseError, which is identified and being worked on 😉

haha, you fix one, but got bitten by the other one

Let's merge are the failures are being worked on 👼

authors: thaJeztah vdemeester


text:
Can't login to docker hub windows

I can't seem to login with a valid email

@nicolasbrugneaux Can you take a look?

source: gharchive/issue

authors: FrenchBen sfabriece

repo: docker/kitematic

license_source: bigquery


text:
Error - Failing to connect to Docker Engine

"There was a problem connecting to the Docker Engine in the VirtualBox VM. This could be because this Mac is currently connected to a VPN, blocking access to this VM."
No VPN currently connected. Issue persists following restart of network adapter, restart of Kitematic and boot cycle of Mac.

Thanks for the issue!
Does:

Removing the dev VM through VirtualBox
Restarting Kitematic

work?

Hi Jeffrey,
Thanks for your response. I resolved this by:

Connecting and disconnecting my VPN client (Junos Pulse)
Restarting Kitematic and successfully downloading and running CentOS VM

Confirmed resolved following reboot. Not sure why the one instance of
connecting/disconnecting the VPN fixed it, but bugs with Junos Pulse don't
surprise me any more...
Thanks!
Andrew
On 18 March 2015 at 04:19, Jeffrey Morgan notifications@github.com wrote:

Thanks for the issue!
Does:

Removing the dev VM through VirtualBox
Restarting Kitematic

work?
—
Reply to this email directly or view it on GitHub
https://github.com/kitematic/kitematic/issues/302#issuecomment-82733075.

--
Andrew Valentine
P: 07828 045095

I'm having the same issue, though restarting the app and closing Junos Pulse doesn't seem to help

I killed junos entirely, docker-machine removed the dev image and created a new one
search for an image:  select scratch official, start installing, receive the following:

now I can't delete the image,  running docker images yields:
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>              <none>              511136ea3c5a        21 months ago       0 B

everything's frozen until I kill kitematic and the VM

This also persists through reboot

➜  ~  docker-machine create -d virtualbox dev
INFO[0000] Creating SSH key...
INFO[0000] Creating VirtualBox VM...
INFO[0008] Starting VirtualBox VM...
INFO[0008] Waiting for VM to start...
INFO[0040] "dev" has been created and is now the active machine.
INFO[0040] To point your Docker client at it, run this in your shell: $(docker-machine env dev)
➜  ~  $(docker-machine env dev)
➜  ~  docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
➜  ~

@lostinplace There are 2 issues here -

Problem connecting to Docker Engine

If that worked, the base image - CentOS - will not run as Kitematic doesn't support running base images (not given instructions on how to run it). - This part of the issue will be merged with https://github.com/kitematic/kitematic/issues/485

Should be fixed.
These logs might be useful for #1029 as well.. will merge.

This is not fixed, still getting errors.

authors: andrewvalentine jeffdm lostinplace mchiang0610 megamindbrian


text:
Get an error trying to set up Kitematic

Expected behavior
Setup works.
Actual behavior
I get this error :

And here it is in text:
Command failed: /usr/local/bin/docker-machine -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.13.0, build 9ba6da9,Found binary path at /usr/local/bin/docker-machine,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:58443,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(flag-lookup) Calling .GetMachineName,(flag-lookup) Calling .DriverName,(flag-lookup) Calling .GetCreateFlags,Found binary path at /usr/local/bin/docker-machine,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:58447,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,Error generating certificates: Creating machine certificate dir failed: mkdir /Users/nikivi/.docker: file exists,open /Users/nikivi/.docker/machine/machines/default/default/Logs/VBox.log: no such file or directory,notifying bugsnag: [Error generating certificates: Creating machine certificate dir failed: mkdir /Users/nikivi/.docker: file exists],

Information about the Issue
My macOS version is : 10.11.6
Perhaps that's the issue. I installed Kitematic from Docker Toolbox.

This on latest release.


text:
404 when downloading new container

Expected behavior
Pulling a new container - hit the create button, and
Actual behavior
I'm presented with an error (screenshot below)
Information about the Issue
It happens only with the latest tag. If I select a specific version, everything works fine.
Steps to reproduce the behavior

Click the + NEW button
Click the CREATE button on a container

BTW it happen to me again when I was trying to create an elasticsearch container as well.

Looks like those repositories do not have a :latest tag, so you will have to specify a specific tag to use; here's the steps to do so (steps below are for the elasticsearch image, but the steps are similar for the image you're using):

Click on the ... button to view the image's details

Click on the Selected tag: latest to open the "tag selection" window

Click the tag / version of the image you want to run

Click the (X) to close the tag selector window

Click on the Create button to pull the image and start the container
Closing this issue because this is not a bug, but feel free to continue the conversation


text:
docker compose not working with default bridge network

docker compose not able to use default bridge network which created at the time of docker daemon installation.

No response after 3 weeks, I'm closing the issue

repo: docker/labs


text:
Fixes https://github.com/docker/docker/issues/13426

Ported the code over and adjusted to the setup process and the new netlink library
Fixes https://github.com/docker/docker/issues/13426
Signed-off-by: Madhu Venugopal madhu@docker.com

@mrjana @aboch addressed all the relevant comments. PTAL.

LGTM

LGTM

authors: aboch mavenugo mrjana

repo: docker/libnetwork


text:
fix for #14633, use original nexthop ip value instead of obtained via…

Here is detailed description of the issue
https://github.com/docker/docker/issues/14633

LGTM
/cc @mrjana @aboch @mavenugo

LGTM

authors: dave-tucker mrjana pyakpyak


text:
support github enterprise urls for b2d downloads

This commit allows downloading boot2docker releases not only from the official releases url (https://api.github.com/repos/boot2docker/boot2docker/releases) but from arbitrary github repositories that publish releases with a boot2docker.iso artifact. It also supports downloading from github enterprise installations.

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 "b2d_gh_enterprise_urls" git@github.com:databus23/machine.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.

This is pull request is a follow up for #537.

This pull request does only solve the initial booting of a custom boot2docker image from a custom github releases compatible api url.
The boot2docker lib machine provisioner still only uses the official releases url for upgrading which is kind of bad.
I noticed that the url provided during creation is already recorded in the config.json of the machine, but there seems to be no way to access the config via the Driver interface so that the provisioner could use the custom url for upgrades as well.
Any ideas on how to tackle this?

The failing tests seem unrelated to my changes:
github.com/MSOpenTech/azure-sdk-for-go (download)
package github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient
	imports github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient
	imports github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient: cannot find package "github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient" in any of:
	/usr/local/go/src/github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient (from $GOROOT)
	/home/ubuntu/.go_workspace/src/github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient (from $GOPATH)
	/usr/local/go_workspace/src/github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient

go get -t -d -v ./... returned exit code 1

/home/ubuntu/.go_project/src/github.com/MSOpenTech/azure-sdk-for-go/clients/vmClient Action failed: go get

@databus23 can you rebase on master? Build bustage should be fixed.
Thanks.

@dmp42 not really. Rebased against master and circleci still fails to pull some dependencies.

Rebased on top of current master. Circlci is still moody.

@databus23 Thanks.
Follow-up to fix circle over here: #1883

Rebased on current master.

Rebased against current master again.

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 "b2d_gh_enterprise_urls" git@github.com:databus23/machine.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

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

I managed to find a solution for fixing the boo2docker provisioner so that it now uses the boot2docker-url that was specified when the VM was created. That means upgrading from custom boot2docker urls works now as well.

Hi @databus23 sorry for the inconvenience, but can you rebase once again on master please? Things have changed quite a bit ;-)

rebased on current master

LGTM. ping @dmp42

LGTM

repo: docker/machine


text:
FIX #2624 reject duplicate hostonlyifs name/IP

Signed-off-by: David Gageot david@gageot.net

Nice!  Needs a rebase but LGTM.

authors: dgageot nathanleclaire


text:
Simplify appveyor config

Now that go 1.6 is the default, we can simplify the AppVeyor configuration file.
Signed-off-by: David Gageot david@gageot.net

LGTM


text:
Add --amazonec2-block-duration-minutes flag

Add the --amazonec2-block-duration-minutes flag, analogous to
--block-duration-minutes from the AWS CLI.

Wow, looks popular :D

Code looks pretty reasonable, you need to run gofmt on it though

The gofmt error seems to be unrelated to this PR since it doesn't modify ls.go:
commands/ls.go:452:6: expected operand, found 'range'
commands/ls.go:458:2: expected '{', found 'for'
commands/ls.go:463:2: expected ';', found 'return'
commands/ls.go:466:6: expected '(', found 'IDENT' newHostListItemInError
commands/ls.go:475:6: expected '(', found 'IDENT' sortHostListItemsByName

@cifkao Not sure where you're getting that, but in the Travis log, you can see that the issue is with drivers/amazonec2/amazonec2.go:
drivers/amazonec2/amazonec2.go
make: *** [fmt] Error 1
mk/validate.mk:12: recipe for target 'fmt' failed
make: *** [build validate] Error 2

and I can see quite clearly that defaultBlockDurationMinutes equals sign is not aligned with the others, so the file clearly does need gofmt.  Thanks.

Oh, I see. I'm getting the ls.go error when I run make test. I didn't see any specific message for drivers/amazonec2/amazonec2.go so I assumed it was fine.

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 "amazonec2-block-duration-minutes" git@github.com:cifkao/docker-machine.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

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

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 "amazonec2-block-duration-minutes" git@github.com:cifkao/docker-machine.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

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

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 "amazonec2-block-duration-minutes" git@github.com:cifkao/docker-machine.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

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

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 "amazonec2-block-duration-minutes" git@github.com:cifkao/docker-machine.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

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

LGTM... I'm going to squash these to one commit

Can you submit docs change to https://github.com/docker/docker.github.io/tree/master/machine please?  vnext-machine branch

authors: GordonTheTurtle cifkao nathanleclaire


text:
Use correct commit sha for PRs?

Behaviour
Hey folks, similar to https://github.com/docker/metadata-action/issues/191 a bit, when running a workflow on a PR event, the {{ sha }} refers to the temporary merge commit to the target branch, not the commit that was pushed to trigger the event.
I realize this is a pretty common situation with GitHub actions, but it ends up with Docker tags/labels that don't map back to any real commits. It would be really useful if this action automatically used github.event.pull_request.head.sha for PR events. I think it would have to be set for the tags {{ sha }} value and the auto-generated label org.opencontainers.image.revision.
I'm aware we can work around the tags situation by using type=raw and passing a value based on github.event.pull_request.head.sha, but it feels a bit error-prone.
I'm unaware of a workaround for overriding the org.opencontainers.image.revision label, though.
Steps to reproduce this issue
See example workflow and run on a PR
Expected behaviour
Tags with the correct sha in a PR (same with org.opencontainers.image.revision label)
Actual behaviour
Tags are created with the merge commit of the PR to the target branch (same with org.opencontainers.image.revision)
name: AWS

on:
  push:
    branches: ["main"]
    tags: ["v*"]
  pull_request:
    branches: ["*"]

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: Docker meta
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: "my-repo/my-image"
          tags: |
            type=ref,event=branch,suffix=-{{ sha }}
            type=ref,event=pr,suffix=-{{ sha }}

the {{ sha }} refers to the temporary merge commit to the target branch, not the commit that was pushed to trigger the event.

No, {{sha}} refers to the commit SHA that triggered the workflow run. It's the same as GITHUB_SHA or ${{ github.sha }} in github context.
You can check this behavior by adding the following step in your workflow to trace the context:
      - name: Dump context
        if: always()
        uses: crazy-max/ghaction-dump-context@v1

In your case you might want ${{ github.event.pull_request.head.sha }} or ${{ github.event.pull_request.base.sha }}:
jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: Docker meta
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: "my-repo/my-image"
          tags: |
            type=ref,event=branch,suffix=-{{ sha }}
            type=ref,event=pr,suffix=-${{ github.event.pull_request.head.sha }}

when running a workflow on a PR event

Also on PR event your don't have access to secrets so you don't push your image anyway? Maybe it's a private repo and you're using OIDC?

but unaware of anything for labels and it's just a tricky thing to have to account for whenever we want to reference the git sha.

Sorry I missed your case with labels. So yes you can override them with:
jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: Docker meta
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: "my-repo/my-image"
          tags: |
            type=ref,event=branch,suffix=-{{ sha }}
            type=ref,event=pr,suffix=-${{ github.event.pull_request.head.sha }}
          labels:
            org.opencontainers.image.revision=${{ github.event.pull_request.head.sha }}

Oh gotcha thanks for the link. Not sure if this is an issue though? Looks like it adds a tag rather than replacing
Docker labels
  org.opencontainers.image.title=my_repo
  org.opencontainers.image.description=
  org.opencontainers.image.url=https://github.com/my_org/my_repo
  org.opencontainers.image.source=https://github.com/my_org/my_repo
  org.opencontainers.image.version=pr-123
  org.opencontainers.image.created=2022-05-11T19:15:32.381Z
  org.opencontainers.image.revision=b0609399d9ffb14f42dd7097df4a12fc81a1234f
  org.opencontainers.image.licenses=
  org.opencontainers.image.revision=d48678cbb01422b60f8fe3cc2e1c1438ab6789e

https://github.com/docker/metadata-action/issues/125#issuecomment-910761577

Got it, that works thank you!
Any thoughts on being able to set the commit sha for PRs specifically? I think it would be a great quality of life improvement.

what @evandam said, it'd be great if we could fetch the "real" SHA of the PR vs some temporary SHA that doesn't match really to anything 😅

Agree @scalp42, The thing is that, it is not event respecting the checkout commit.
I have used ref: ${{ github.event.pull_request.head.sha }} to checkout the PR head and it works but the meta is still taking future merge commit id.

Should this issue be re-opened since the change was reverted?

@dylanANZ they reverted the default behavior but the feature is available (see https://github.com/docker/metadata-action/pull/239):

revert changes to set associated head sha on pull request event and use commit sha that triggered the workflow by default. User can still set associated head sha on PR by setting the env var DOCKER_METADATA_PR_HEAD_SHA=true.

repo: docker/metadata-action


text:
Notary purge does not properly remove delegation keys

Notary built from latest release/0.4 branch.
Docker Engine version:
❯ notary version
notary
 Version:    0.3
 Git commit: 946674a
❯ docker version
Client:
 Version:      1.12.1-cs1-rc1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6dea08f
 Built:        Wed Sep  7 05:03:49 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:        Wed Jul 13 03:41:15 2016
 OS/Arch:      linux/amd64

~/.docker
❯ notary delegation purge 54.68.209.79:4431/someorg/somerepo --key 785b2152ba2057b883d77162c6bf5e7aaadd94f7b31ab957eb62523e4bd4c294
Removal of the following keys from all delegations in 54.68.209.79:4431/someorg/somerepo staged for next publish:
	- 785b2152ba2057b883d77162c6bf5e7aaadd94f7b31ab957eb62523e4bd4c294
~/.docker
❯ notary status 54.68.209.79:4431/someorg/somerepo
Unpublished changes for 54.68.209.79:4431/someorg/somerepo:

#    ACTION    SCOPE        TYPE          PATH
-    ------    -----        ----          ----
0    update    targets/*    delegation

~/.docker
❯ notary publish 54.68.209.79:4431/someorg/somerepo
Pushing changes to 54.68.209.79:4431/someorg/somerepo
Enter username: someuser
Enter password:

~/.docker 7s
❯ notary delegation list 54.68.209.79:4431/someorg/somerepo

ROLE               PATHS             KEY IDS                                                             THRESHOLD
----               -----             -------                                                             ---------
targets/someorg    "" <all paths>    785b2152ba2057b883d77162c6bf5e7aaadd94f7b31ab957eb62523e4bd4c294    1

fixed on release branch by #954

Hi!
"Removal of the following keys from all delegations in 54.68.209.79:4431/someorg/somerepo ... ". Is it possible to have multiple delegations for a repo?
Thank you!

yes, and it also supports nested delegtions

yes, and it also supports nested delegtions

@HuKeping ... thank you!

authors: HuKeping LenutaToderean hinshun riyazdf

repo: docker/notary


text:
set MemorySwappiness default value

Fix this issue: https://github.com/docker/swarm/issues/1411
Signed-off-by: Xian Chaobo xianchaobo@huawei.com

ping @fsfshijm @AzenYao
Can you try this and see if it works. Thanks

@jimmyxian, Seems it works well!
-sh-4.2$ ps -ef | grep swarm
jmshi     9427     1  0 03:36 ?        00:00:00 swarm join --addr=192.168.0.233:2375 etcd://192.168.0.141:4001
jmshi     9439     1  0 03:36 ?        00:00:00 swarm join --addr=192.168.0.17:2375 etcd://192.168.0.141:4001
jmshi     9450     1  0 03:36 ?        00:00:02 swarm manage -H 0.0.0.0:2380 etcd://192.168.0.141:4001
jmshi    10466  9473  0 04:23 pts/0    00:00:00 grep --color=auto swarm
-sh-4.2$ export | grep DOCKER_HOST
export DOCKER_HOST="tcp://0.0.0.0:2380"
-sh-4.2$ swarm -v
swarm version 1.0.0 (HEAD)
-sh-4.2$ docker-compose up -d
Creating web
Creating mongo
-sh-4.2$ docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                          NAMES
678b77255062        mongo                         "/entrypoint.sh mongo"   3 seconds ago       Up 3 seconds        27017/tcp                      EP003/mongo
88d14f3e4264        bfirsh/compose-mongodb-demo   "/bin/sh -c 'python a"   6 seconds ago       Up 3 seconds        192.168.0.233:1234->5000/tcp   PEKdev233.dev.fwmrm.net/web
-sh-4.2$

Thanks very much!

ping @docker/swarm-maintainers

LGTM

ping @vieux

@jimmyxian shouldn't this be fixed in compose ?

@vieux I think should fix in both compose \ docker \ swarm.
If send create json request without MemorySwappiness to docker / swarm, we should set this -1 in docker / swarm.
In compose, maybe also need to set this -1.

when will this get merged?

@johnjelinek Can you try this and see if it work. Thanks.

@jimmyxian: I don't think I can test this until there's a container for it. I'm not set up to build golang apps yet in my cluster.

I must've done something wrong. I did a $GOPATH/bin/godep go install . to build a new swarm bin (this is after I checked out this branch). Then I stopped all my swarm-agent containers and manually ran swarm in all my cluster servers. When I do docker version, it says swarm is pointing to this commit hash: https://github.com/jimmyxian/swarm/commit/087e245. I still get the same error message about swappiness. Any ideas how I can build just your branch right?

@jimmyxian: I also tried merging your branch into master in my local repo of swarm:master. Same problem. What should I do to ensure that it's tracking an updated commit hash?

@johnjelinek Did you restart your Swarm Manager too with the new Image/binary including the commit? From your comment I read that you tried only with Swarm Agents. You mostly need to restart the Swarm Manager. So restarting it (hopefully) should do the trick :)

Hrmm ... I'll give that a shot. I have the swarm manager running in HA mode with consul. Not sure if that makes a difference.
—
Sent from Mailbox
On Thu, Dec 3, 2015 at 5:25 PM, Alexandre Beslic notifications@github.com
wrote:

@johnjelinek Did you restart your Swarm Manager too with the new Image/binary including the commit? From your comment I read that you tried only with Swarm Agents. You mostly need to restart the Swarm Manager. So restarting it (hopefully) should do the trick :)
Reply to this email directly or view it on GitHub:
https://github.com/docker/swarm/pull/1425#issuecomment-161822203

@abronan: that was it :) all fixed now. :shipit:

@johnjelinek Woop! Thanks a lot for testing and confirming :)
Let's include the fix asap. PTAL @docker/swarm-maintainers

@johnjelinek Thanks for testing. :)

@jimmyxian / @abronan: do you have an ETA on when this might get merged/published? I feel nervous running all these processes outside of docker containers.

LGTM

@johnjelinek Hey, you can run the master swarm image by doing a docker run of dockerswarm/swarm:master instead of swarm.
This will be published in 1.0.1 sometime next week.

@aluzzardi: sweet, thanks!

If I understand correctly, this fixes https://github.com/docker/docker/issues/17879 ?

Yes, that's correct.
On Sun, Dec 6, 2015 at 4:39 AM, Sebastiaan van Stijn <
notifications@github.com> wrote:

If I understand correctly, this fixes docker/docker#17879
https://github.com/docker/docker/issues/17879 ?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/swarm/pull/1425#issuecomment-162299511.

authors: abronan aluzzardi fsfshijm jimmyxian johnjelinek thaJeztah vieux

repo: docker/swarm


text:
Replace BMP resources with PNG

Reduces the size of the compiled library from 418KB to 247KB.

Merged. Thanks for proposing this change.

authors: arhughes lextm

repo: dockpanelsuite/dockpanelsuite

license: mit


text:
SEAB-6164: resizing and alignment fix for the new landing page

Description
During the demo, we discovered some tweaks that would improve the landing page.
Changes made:

Changed card text to left align
The card width was raised to 45% from 40% when aligned into rows to remove the scrollbar on the code block of the Tips and Tricks card
For window sizes less than lg defined here,, the cards are aligned as columns.
Removed the horizontal padding in the cards and increased the card content width to 90%

This is the video demo for the resizing
https://github.com/dockstore/dockstore-ui2/assets/61166764/eac1ac29-25a8-445e-8732-f5266adc5f39
Review Instructions
Play with the resizing on https://qa.dockstore.org/github-landing-page and verify that things look good.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-6164
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

The bottom text was not center aligned so that was fixed

I thought you were going to left-align the top text, not center-align the bottom :)
You can probably find links arguing the other way round, but here's one I found for my position.
If I'm the only who feels this way, I'll concede.

Updated the screen recording and alignment. Thanks Charles!


text:
Fix label losing "for" attribute and deprecation warning

This is for the 1.0 branch (which looks great, by the way).
When the input was re-rendered, the label's for attribute would disappear (since the underlying elements all change). This is solved by switching from didInsertElement (called only once as of Ember 1.13) to didRender (called on re-renders too).
This also fixes a deprecation warning present due to the for attribute being modified during this rendering phase by shifting it to the afterRender callback.
I'm still not sure changing the element's for attribute after rendering is ideal (as the comment already noted), but I'm not entirely sure how else to go about this.
This also includes a couple of other small things I ran into while testing this, but let me know if you'd prefer for any of this to be split out into separate pull requests:

Locking jQuery to 1.11.3, since running ember tests would otherwise hang on a fresh installation due to jQuery 1.12 being installed: https://github.com/ember-cli/ember-cli/issues/5317
Raising exceptions during tests for any Ember deprecations (so I could ensure the afterRender fix would indeed do the trick). I also needed to fix the template used in one other test to get rid of deprecation warnings about the binding syntax in Ember 1.13+.

Thank you @GUI, this is excellent.
@bcardarella this is good to merge, if you want to

@diogomafra you can do so, I'll let you have ownership over the 1.0 branch

:ok_hand:

authors: GUI bcardarella diogomafra

repo: dockyard/ember-easy-form

license: MIT


text:
[support] Why is this preferable over native HTML input?

Hey Dockyard!
Stumbled upon your addon in Ember Weekly.
As I understand, the same result can be achieved without any extra addon/component, with native HTML form elements:
{{one-way-input
  value=currentValue
  update=(action (mut currentValue))
}}

<input
  value={{currentValue}}
  oninput={{action (mut currentValue) value="target.value"}}
>

What's the benefit?

If you edit a text input, the cursor will always go to the end of the input because of the bindings. I can make a jsbin in a bit to show you the issue

Please do!
I've also noticed that your source code exposes some hooks.
It would be awesome if you documented both the native issue and the hooks!

I'll update the readme! Thanks :)

http://jsbin.com/jeheku/1/edit?html,css,js,output
You can't use mut with the native input event, as it returns an object

@danmcclain, wut?

https://ember-twiddle.com/7dc033ebfc86f779e100

Twiddle link isnt working, but broken with mut in this example: http://jsbin.com/qidenisuka/edit?html,css,js,output

@danmcclain Because you dropped value="target.value" that exists in the top post.

@lolmaus Ah, thanks, I missed that. Still shows the janky cursor! http://jsbin.com/juxedi/edit?html,css,js,output

Thank you @poteto. But the hook(s) still not documented!

authors: danmcclain lolmaus poteto

repo: dockyard/ember-one-way-input


text:
Setup py tweaks

Just a few small things:
It's probably easier to maintain the version number when it's just in one place.
The entry points add the specified name to your PATH and execute the function you point this name to.
In this case after pip installing, you can invoke your program in the terminal:
hla

This cuts down on typing and allows you to distribute multiple executables with one package.
Here are some more references on entry points:

https://chriswarrick.com/blog/2014/09/15/python-apps-the-right-way-entry_points-and-scripts/
https://setuptools.readthedocs.io/en/latest/setuptools.html#automatic-script-creation
https://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins

Thank you for the hint with entry points, it is very useful indeed.

yea, feel free to close this PR if you plan to add some other entry point for the app. I thought it would be easier to "show rather than tell" this kind of stuff :)

authors: iliakur pavlodyban


text:
Invalid access of subselect columns in automatically generated subselect

I see a lot of errors of the following pattern:
SELECT
  DISTINCT blog_article_id_0
FROM
  (
    SELECT
      ...
      b0_.date AS date_4,
      ...
      b0_.like_count AS like_count_8,
      ...
    FROM
      blog_articles b0_
  ) dctrn_result
ORDER BY
  date_4 DESC,
  like_count_8 DESC

The error is that the outer query tries to use fields from the inner query, which obviously fails.
These issues first appeared for 2.5 and only appear on certain occassions - but if they appear they are consistent, i.e. they are reproducible.
The current error case is quite big, I try to create a reduced reproducible test case.
Just wanted to create the issue beforehand, because maybe somebody had similar issues and knows of any solution?
Installed versions:
doctrine/annotations                 v1.2.7             Docblock Annotations Parser
doctrine/cache                       v1.6.0             Caching library offering an object-oriented API for many cache backends
doctrine/collections                 v1.3.0             Collections Abstraction library
doctrine/common                      v2.6.1             Common Library for Doctrine projects
doctrine/dbal                        v2.5.4             Database Abstraction Layer
doctrine/doctrine-bundle             1.6.3              Symfony DoctrineBundle
doctrine/doctrine-cache-bundle       1.3.0              Symfony Bundle for Doctrine Cache
doctrine/doctrine-migrations-bundle  1.1.1              Symfony DoctrineMigrationsBundle
doctrine/inflector                   v1.1.0             Common String Manipulations with regard to casing and singular/plural rules.
doctrine/instantiator                1.0.5              A small, lightweight utility to instantiate objects in PHP without invoking their constructors
doctrine/lexer                       v1.0.1             Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers.
doctrine/migrations                  1.4.1              Database Schema migrations using Doctrine DBAL
doctrine/orm                         v2.5.4             Object-Relational-Mapper for PHP

Seems to be a duplicate of #5622, sorry for the noise.


text:
PHP7.2: implemented \Countable to LoginInformation

Code example from README.md is not working with PHP7.2:
if(isset($loginInformation) && count($loginInformation) > 0) { // ...

You cannot count object without \Countable implementation.
Is there a way to make swagger code generation compatible with PHP7.2+?

Thank you for the PR.
I apologize for the extremely slow response. We've changed our processes so this doesn't happen again.
LoginInformation is now obsolete.
Only OAuth authentication is supported for new applications.
And OAuth apps must use /oauth/userinfo instead of the old loginInformation

authors: LarryKlugerDS emelnychenko

repo: docusign/docusign-php-client


text:
*Official~#LIVE™!] Ipswich Town vs Chelsea LIVE STreams ON TV Channel 30,December 2024

Ipswich Town vs Chelsea live stream: English Premier League 2024 prediction, TV channel, how to watch, start time, odds Chelsea vs Ipswich Town : How to watch, schedule, live stream info, game time, TV channel
Chelsea v Ipswich Town live score and video online live stream starts on 30 December 2024 at 24:45 time in English Premier League - Rugby Union. English Premier League 2024 leaders Ipswich Town travel to Ellis Park, Johannesburg on Saturday with manager Mikel Arteta bidding to extend a surprising undefeated run away to Chelsea.
The Gunners won on each of their last two visits to west Melbourne in the top flight without particularly imposing themselves on their opposition, this time it may well be different for a side who have established themselves as a surprising early season contender for major honors.
Event details:
NAME: Ipswich Town - Chelsea
DATE: 30 Dec 2024
TIME: 19:45 UTC
VENUE: Portman Road Stadium, Ipswich, England
Chelsea, meanwhile, have work to do if they are to drag Ipswich Town into the battle for top four, rather than the title. Lose on Saturday and they will trail their rivals by 31 points, a sizeable gap to make up even with two-thirds of the season left to go.
Here is how you can watch the match and what you need to know: Chelsea and Ipswich Town are meeting up for their first leg of the season at 8.45 PM AEDT, 9.45 PM NZT on Saturday at Ellis Park, Johannesburg. The teams split their matchups last year, with Chelsea winning the first 2-0 on the road and Ipswich Town taking the second 4-2. Chelsea are taking on Melbourne rivals Ipswich Town at Ellis Park, Johannesburg as the Blues aim to close the 31-point gap between the two clubs in the English Premier League 2024 Saturday, 30 Dec 2024.
Chelsea had been going along nicely under Graham Potter until a chastening defeat at his former club Ipswich Town last weekend, and now face two tricky matches – against Ipswich Town and Chelsea – before the English Premier League break. The Gunners are looking to reach the English Premier League on top of the table and got back on track last weekend with a 5-0 win over Ipswich Town, having slipped to a 1-1 draw at Ipswich Town in their previous match. Ipswich Town won both of the past two corresponding fixtures away at Chelsea, earing a 4-2 victory last season Saturday, 30 Dec 2024.
Old foes and former colleagues will reunite at Ellis Park, Johannesburg on Saturday lunchtime as Chelsea tackle Ipswich Town in a mouth-watering English Premier League 2024 Melbourne Ipswich Town . Both sides enter the game on the back of continental successes, as the Blues got the better of Dinamo Zagreb 2-1 in the English Premier League 2024, while the Gunners advanced to the last 01 of the English Premier League 2024.

bgf
✅🟢 STREAM PLAY NOW ▶
✅🟢 PLAY NOW ONLINE

.
✅🟢 STREAM PLAY NOW ▶
✅🟢 PLAY NOW ONLINE
xswq

◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
.
.

.
.

.
.

.
.
.
.

.
.

.

.
.
👉⏩🎥🅻🅸🆅🅴🔴▶ ✅🟢 STREAM PLAY NOW ▶
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶ ✅🟢 PLAY NOW ONLINE
xdw

authors: neroevo666 tmakhs umonhasana

repo: doczjs/docz


text:
Extract out the default Genesis configs of different networks

The default genesis.json should be defined in the code, so that user could deploy DogeChain-Lab jury nodes and join in network more easily.
Network is also needed to be defined, and separated from each other instead of confusing our users.
By the way, node upgrade module is heavily depend on the pre-defined network and Genesis block hash.

Reference issues: #140
Reference PRs: #172
Would do more to get closed to this goal.

repo: dogechain-lab/dogechain


text:
[bug] Build fails with Protobuf 24.x

Bug Report
First I would like to mention that after I have worked around the issue mentioned in the bug report, I am very pleased to report that Dogecoin Core QT compiles and runs "out of the box" on FreeBSD without any patches.  Well done!  If the Dogecoin project can commit to making sure that it continues to work on FreeBSD, unaltered, I will submit this to the FreeBSD ports team so they can include it as part of the official ports tree.
Current behavior:
FreeBSD has updated their default version of Protobuf in the ports tree to 24.4,1 (as of this bug report).  Dogecoin fails to build due this new version of Protobuf:
/usr/local/include/google/protobuf/port_def.inc:210:1: error: static_assert failed due to requirement '201103L >= 201402L' "Protobuf only supports C++14 and newer."
static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");
^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Attempting to force a c++14 compiler (with CXXFLAGS="-std=c++14") solves the above, but results in Dogecoin failing to build at another point:
In file included from qt/utilitydialog.cpp:10:
In file included from ./qt/utilitydialog.h:11:
In file included from ./qt/walletmodel.h:8:
In file included from ./qt/paymentrequestplus.h:10:
In file included from ./qt/paymentrequest.pb.h:24:
In file included from /usr/local/include/google/protobuf/io/coded_stream.h:134:
In file included from /usr/local/include/absl/strings/cord.h:78:
In file included from /usr/local/include/absl/container/inlined_vector.h:53:
In file included from /usr/local/include/absl/container/internal/inlined_vector.h:30:
In file included from /usr/local/include/absl/container/internal/compressed_tuple.h:40:
/usr/local/include/absl/utility/utility.h:164:12: error: no member named 'in_place_t' in namespace 'std'
using std::in_place_t;
      ~~~~~^
/usr/local/include/absl/utility/utility.h:165:12: error: no member named 'in_place' in namespace 'std'
using std::in_place;
      ~~~~~^

The 'workaround' is to remove the devel/protobuf port which is at version 24.4.1 and replace it with devel/protobuf3.  Then re-attempt to compile using c++11.
Unfortunately the two ports can not co-exist.  I can see that as a potential problem.
Expected behavior
Dogecoin Core should build with c++14 and with Google's latest version of Protobuf
Steps to reproduce:

Install FreeBSD 13 or 14
Checkout ports tree
Checkout Dogecoin port located at https://github.com/tuaris/FreeBSD-Coin-Ports
Install devel/protobuf
Attempt to build the port: cd /path/to/FreeBSD-Coin-Ports/net-p2p/dogecoin; make build
Observe error
Remove devel/protobuf
Install devel/protobuf3
Port build successfully

Dogecoin Core version
v1.14.7.0-330d9f5
Machine specs

OS: FreeBSD
CPU: Intel
RAM: 32G
Disk size: 100G
Disk Type (HD/SDD): SSD

Extra information
The code to functional port can be viewed at: https://github.com/tuaris/FreeBSD-Coin-Ports/tree/master/net-p2p/dogecoin

/usr/local/include/absl/utility/utility.h:164:12: error: no member named 'in_place_t' in namespace 'std'
using std::in_place_t;
      ~~~~~^
/usr/local/include/absl/utility/utility.h:165:12: error: no member named 'in_place' in namespace 'std'
using std::in_place;
      ~~~~~^

[..]
Dogecoin Core should build with c++14 and with Google's latest version of Protobuf

std::in_place_t is c++17, not 14. I think this is caused by how abseil is compiled with the ports package. There's a similar issue on MacOS where the brew abseil package requires C++17 (brew link). I'm by no means an expert on ports, as I haven't actively used it for a very long time, but looking at it with my limited knowledge I suspect that the ports package also requires c++17.
For Dogecoin Core, I was already planning to add an --enable-c++17 flag for 1.15.0, which we could - depending on impact - backport to a 1.14 patch release.

@tuaris: This should no longer produce the errors on in_place and in_place_t anymore in the 1.15.0-dev branch (at fdf534c13), when you use --enable-c++17 when configuring. Could you please check if that solved your issue?

@patricklodder your changes work (at least on FreeBSD 13.2)  I did have to make one small patch in regards to miniupnp
https://github.com/tuaris/FreeBSD-Coin-Ports/blob/6f49fef3d9cb20616b3d5c35d3674bafbe21b69d/net-p2p/dogecoin/files/patch-src_net.cpp
I did not run into the issue reported in https://github.com/dogecoin/dogecoin/issues/3673, but I'm using an older version of FreeBSD.  I'll run some additional tests on some of my build boxes.
Btw, how is CI handled?  Would it be possible to incorporate FreeBSD testing?  The ports system makes it super easy, and the most time consuming part of getting setup is already done with this: https://github.com/tuaris/FreeBSD-Coin-Ports/tree/master/net-p2p/dogecoin

Perhaps it is more useful to do nightly builds against ports managed dependencies? Get early warning in through that?

Yeah, I think that might be the only option.  The FreeBSD ports get updated a lot more frequently and that's usually what breaks builds.  They do cut quarterly branches, but that too may be too often.
Anyway, I did test the build against 13.3, 14.1, and 14.2.  They all worked using the patch in https://github.com/dogecoin/dogecoin/issues/3673.

authors: patricklodder tuaris

repo: dogecoin/dogecoin


text:
[Bug]: Strings over RPC fail to be parsed

Steps to reproduce
// Note: This file doesn't actually need to exist.
namespace Your.RPC
{
    public static class Class
        /// <summary>
        /// Test method
        /// </summary>
        /// <param name="aString"></param>
        [Preserve]
        public static void AMethodThatAcceptsASingleString(string aString)
        {
            // Will never make it here.
            AssertIsDevBuild();
            Debug.Log("SUCCESS");
        }
    }
}

from gamium import *

service = TcpGamiumService("127.0.0.1", 50061)
gamium = GamiumClient(service)

gamium.connect()

# Send any non-numeric string over RPC
gamium.execute_rpc(
    RpcBy.method(
        "Your.RPC.Class",
        "AMethodThatAcceptsASingleString",
        "c11557d5-ffcc-47fc-9263-2b1717eb070d",
    )
)

Expected result
Client successfully sends the request and prints out SUCCESS in console.
Actual result
Client crashes prior to sending request to server.
$ python test.py
INFO: GamiumClient.connect
INFO: Connecting to 127.0.0.1:50061
INFO: GamiumClient.execute_rpc By: 0, class: Your.RPC.Class, target: AMethodThatAcceptsASingleString
Traceback (most recent call last):
  File "F:\ABI\cvr_unit_tests\test.py", line 7, in <module>
    gamium.execute_rpc(
  File "C:\Users\N3X15\AppData\Local\pypoetry\Cache\virtualenvs\cvr-unit-tests-K3olf5zB-py3.11\Lib\site-packages\gamium\gamium_client.py", line 135, in execute_rpc
    res = self._service.request(create_execute_rpc(locator.by, locator.class_name, locator.target_name, params))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\N3X15\AppData\Local\pypoetry\Cache\virtualenvs\cvr-unit-tests-K3olf5zB-py3.11\Lib\site-packages\gamium\tcp_gamium_service.py", line 104, in request
    raise e
  File "C:\Users\N3X15\AppData\Local\pypoetry\Cache\virtualenvs\cvr-unit-tests-K3olf5zB-py3.11\Lib\site-packages\gamium\tcp_gamium_service.py", line 98, in request
    return self.pop_message(req)
           ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\N3X15\AppData\Local\pypoetry\Cache\virtualenvs\cvr-unit-tests-K3olf5zB-py3.11\Lib\site-packages\gamium\tcp_gamium_service.py", line 126, in pop_message
    raise GamiumError(response.error.code, f"request response error: {reason}")
gamium.errors.gamium_error.GamiumError: (301, "request response error: Unexpected character encountered while parsing value: c. Path '', line 0, position 0.")

Version
2.0.9

Use-case: Our testing process requires that we send GUIDs over RPC for loading worlds, since actually browsing for the world in UI is currently an overly-complicated task for automation.

The problematic code has been modified, but deploy will be delayed due to PyPI account issues.

Fixed in version 2.0.10.

repo: dogu-team/gamium


text:
Release information and tags

Dear Dominic @dohomi
thanks providing this component and your effort on it.
Could you please establish a way to describe changes that were included in new releases and tag them?
Currently on npmjs there is version 3.3.0 but I can't get from what sources you have built that. What it be possible for you to tag the branch on releasing an write some short "changes".
I am pretty sure that would be welcome by others as well.
Again thanks
Tom

Thanks for updating @dohomi and @TimMikeladze

repo: dohomi/react-hook-form-mui


text:
Laggy performance with large data object (1000 items)

Describe the bug
Finding that performance on an Android is very slow for parallax Carousel with 1000 items. Is there some config that needs to be set to handle a large data source, or is this expected? Attaching an example below (mostly modified https://github.com/dohooo/react-native-reanimated-carousel/blob/66b2d23b78d09fc15f300ba43e31ca94a13be689/exampleExpo/src/complex/index.tsx by stripping out stuff). Saw there was a similar issue raised but I'm not sure this provided a solution, as I've tried setting windowSize=3 and still seeing significant lag https://github.com/dohooo/react-native-reanimated-carousel/issues/207
To Reproduce
import * as React from 'react';
import { ScrollView, Text, View, Dimensions } from 'react-native';
import Carousel from 'react-native-reanimated-carousel';
import SButton from '@components/SButton';

const PAGE_WIDTH = Dimensions.get('window').width;

function Index() {
    const r = React.useRef(null);

    return (
        <View
            style={{
                flex: 1,
                backgroundColor: '#f1f1f1',
                paddingTop: 100,
            }}
        >
            <View style={{ width: PAGE_WIDTH, height: 240 }}>
                <Carousel
                    defaultIndex={0}
                    ref={r}
                    width={PAGE_WIDTH}
                    data={[...new Array(1000).keys()]}
                    mode="parallax"
                    windowSize={3}
                    renderItem={({ index }) => (
                        <View
                            key={index}
                            style={{
                                flex: 1,
                                justifyContent: 'center',
                                alignItems: 'center',
                                backgroundColor: '#ff7a45',
                                padding: 16,
                            }}
                        >
                            <Text style={{ color: 'white', fontSize: 30 }}>
                                {`index:${index}`}
                            </Text>
                        </View>
                    )}
                />
            </View>
            <View
                style={{
                    marginTop: 24,
                    flexDirection: 'row',
                    justifyContent: 'space-evenly',
                }}
            >
                <SButton onPress={() => r.current?.prev()}>{'Prev'}</SButton>
                <SButton onPress={() => r.current?.next()}>{'Next'}</SButton>
            </View>
        </View>
    );
}

export default Index;

Expected behavior
Unfortunately all the examples I've seen have a small number of objects in data, but I expected scrolling behavior to be as smooth for 1000 items as 5 items.
Versions (please complete the following information):

"react": "18.0.0"
"react-native": "0.69.5"
"react-native-reanimated": "~2.9.1"
"react-native-reanimated-carousel": "^3.0.4"
"react-native-gesture-handler": "~2.5.0"
"expo": "^46.0.0"

Smartphone (please complete the following information):

Device: Pixel 6
OS: Android
Version 13

@michaelshum did you find a solution here?

@RRaideRR I did not 🙃

The issue is still happening. The merge did not fix the issue.

+1

authors: RRaideRR ertan95 michaelshum shideneyu

repo: dohooo/react-native-reanimated-carousel


text:
Broken sun, shadows and light in Grand Theft Auto V

Seems like some other things is broken too, like shadows and light.
Software information
Grand Theft Auto V
System information

GPU: GTX 950
Driver: 390.48.0
Wine version: wine-staging (wine-gaming-nine) - 3.6-1
DXVK version: v0.42

Log files

d3d11.log:

info:  D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
info:  D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn:  D3D11Device: No matching border color found for (1,0,0,0)
warn:  D3D11RasterizerState: Depth clamp not properly supported
warn:  D3D11RasterizerState: Depth clamp not properly supported
warn:  D3D11RasterizerState: Depth clamp not properly supported
warn:  D3D11RasterizerState: Depth clamp not properly supported
warn:  D3D11RasterizerState: Depth clamp not properly supported
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
err:   D3D11: Invalid blend factor: 1205503520
err:   D3D11: Invalid blend factor: 1213985360
err:   D3D11: Invalid blend op: 1213985208
warn:  Dxvk: GpEmulateInstanceFetchRate not handled yet

dxgi.log:

info:  Enabled instance layers:
info:  Enabled instance extensions:
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce GTX 950:
info:    Driver: 390.48.0
info:    Vulkan: 1.0.65
info:  Enabled instance layers:
info:  Enabled instance extensions:
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce GTX 950:
info:    Driver: 390.48.0
info:    Vulkan: 1.0.65
warn:  Vulkan extension VK_KHR_maintenance2 not supported
info:  Enabled device extensions:
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_sampler_mirror_clamp_to_edge
info:    VK_KHR_maintenance1
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_swapchain
warn:  DXGI: MakeWindowAssociation: Ignoring flags
info:  DxgiVkPresenter: Recreating swap chain:
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
  Buffer size:  1920x1080
info:  Enabled instance layers:
info:  Enabled instance extensions:
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce GTX 950:
info:    Driver: 390.48.0
info:    Vulkan: 1.0.65

Its a driver issue. 396.18 with new compiler fixes sun issue, but these drivers perform badly atm.
Shadows work if you enable nvidia PCSS shadows from game options

Sun issue should be fixed by the current Nvidia beta driver.
I'm aware of the shadow issue but I cannot debug it at the moment as the game does not work with DXVK on RADV.

Can anybody confirm if the new nvidia driver fixes the indoor lighting issues? All light sources aside from the sun don't appear to illuminate the scene on my end.

For me personally indoor lighting seems to render correctly in GTA V now. So at least my addition to to this issue is fixed now. Sun was fixed by Nvidia.

repo: doitsujin/dxvk

license: Zlib


text:
Boolean attribute: no validation in published data

The Boolean attribute

accepts and displays the values "true", true, "false", 1
accepts but does not display values 0, false

but also accept "sim", "qq coisa" ...

Expected result:

Test OK.

repo: dojot/dojot


text:
[GUI] Standardize the color of error messages

Different colors are being used for error messages in password registration.

error messages when setting password less than 8 characters

other error messages:

Test OK.


text:
ci: Change travis scripts to use npm ci instead of npm install (for nodejs based components)

As described here, the npm ci command is preferred for automated tests environments and continuous integration environments, as it is faster and stricter than plain npm install command.

Travis is no longer used in our pipeline. It was replaced by the 'Github Actions'.

authors: giovannicuriel rascaraficci


text:
Locking the entire application on mount

Good afternoon I'm just learning in c#. I am making my disk mount application using wpf. I pasted the mount code from the RegistryFS example, but when I ran the line of code
using (var dokanInstance = dokanBuilder.Build(rfs))
{
mre.WaitOne();
}
the disk is mounted in windows explorer, but the application in wpf is blocked and nothing can be done with it. Wait, please tell me what can be fixed so that there is no blocking of the entire application

Hi @ZolfSchultz ,
mre.WaitOne(); is blocking the Thread to keep alive dokanInstance inside the using. This Thread needs to run for your UI to be available. You should store somewhere the dokanInstance and not use using with WaitOne.

authors: Liryna ZolfSchultz

repo: dokan-dev/dokan-dotnet


text:
Terminal tab background is broken since the latest VSC update (1.82.0)

Describe the bug
After updating to the latest Visual Studio Code update (1.82.0), when you reapply the background, the terminal tab doesn't have the background set, however the rest of the tabs have the background. This issue still appears even when I unset my custom background.
To Reproduce

Ensure you are on the latest version (atleast 1.82.0)
Set the background for your Visual Studio Code

Expected Behavior
All views should have the background set correctly, like before the update
Environment
Version: 1.82.0 (user setup)
Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314
Date: 2023-09-06T22:07:07.438Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.23536
Doki theme version: v88.1.15
Screenshots

Same issue here for a while now. I'm considering downgrading my VSCode just for it.
Enviornment:
Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479fleb312d
Date: 2023-09-14T05:51:20.9812 (3 wks ago)
Electron: 25.8.1
ElectronBuildid: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
ve: 11.4.183.29-electron.0
OS: Linux x64 5.15.0-84-generic

Same problem here, but in 1.18.0 instead.
Version: 1.84.0-insider (user setup)
Commit: 4678919d52909efc7c4ab958a2e5c8f45d50ffc3
Date: 2023-10-13T05:34:13.175Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

authors: RealEthanPlayzDev WingXSaber justalemon

repo: doki-theme/doki-theme-vscode


text:
Don't close the server and reload if already reloading

Hi, I came across an issue with the CLI where if a watched file is edited multiple times while the server is restarting, Cloudworker tries to start multiple servers resulting in an EADDRINUSE error.
Changes to the worker script detected - reloading...
{...access logs}
Changes to the worker script detected - reloading...
{...more access logs}
Successfully reloaded!
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3001
    at Server.setupListenHandle [as _listen2] (net.js:1279:14)
    at listenInCluster (net.js:1327:12)
    at Server.listen (net.js:1414:7)
    at Cloudworker.listen (/Users/ricky/srv/ricky-me-cf-worker/node_modules/@dollarshaveclub/cloudworker/lib/cloudworker.js:57:19)
    at server.close (/Users/ricky/srv/ricky-me-cf-worker/node_modules/@dollarshaveclub/cloudworker/bin/cloudworker.js:72:62)
    at Server.close (net.js:1565:9)
    at Object.onceWrapper (events.js:286:20)
    at Server.emit (events.js:203:15)
    at emitCloseNT (net.js:1618:8)
    at process._tickCallback (internal/process/next_tick.js:63:19)

This PR adds a check whether the process of reloading has already started before closing the server. server.close() should only need to be called once so I don't think this should cause any other issues.
Thanks in advance.

Thanks! I’ll take a look this weekend.

Thank you!

authors: hankjacobs richardkazuomiller

repo: dollarshaveclub/cloudworker


text:
I use gateway Kong Routing is configured

My problem is usering swagger request interface Tips is 404。kong routing is http//xxxx.com/servicename/controllers/aciton. but swagger url is http://xxxx.com/controllers/aciton. How should I set up swagger?

Closing due to inactivity

authors: domaindrivendev miaoyukai


text:
Swashbuckle 5.0 and Password Grant Flow

There is documentation on how to authenticate request with the Implicit Grant Flow but not with the Password Grant Flow. Based on the doc for the implicit grant I've enable swagger like this
Swashbuckle.Application.SwaggerEnabledConfiguration sec = config.EnableSwagger(c =>
      {
        c.SingleApiVersion("v1", "MyApi");

        c.OAuth2("oauth2")
          .Description("OAuth2 Password Grant")
          .Flow("password")
          .Scopes(scopes => { scopes.Add("read", "Read access to protected resources"); })
          .TokenUrl("http://localhost:51398/OAuth/token");
        c.OperationFilter<AssignOAuth2SecurityRequirements>();

        c.IncludeXmlComments(System.String.Format(@"{0}\bin\MyApi.XML", System.AppDomain.CurrentDomain.BaseDirectory));
      });

      sec.EnableSwaggerUi();

I took the "AssignOAuth2SecurityRequirements" extension under SwahsBuckle.Dummy.Core.
Is there any other extensions needed for the Password Flow?

As far as I can tell, the OAuth2 "Password flow" is not currently supported by the swagger-ui
https://github.com/swagger-api/swagger-ui/issues/807
So, you can describe it in the spec (as you appear to be doing above) but you won't get any of the additional UI goodness. But, SB does allow you to a) inject your own JavaScript or b) inject your own version of index.html so if you were willing, you could theoretically build in the UI workflow yourself ...

Hi @domaindrivendev is this still not available yet? I was hoping to be able to support this flow on the UI level too.

@domaindrivendev I second the request by @tjoudeh this will be a much appreciated feature.

I just develop my web api documentation using swashbuckle 5 but I think I will use another previous version because I need this feature.

@domaindrivendev  @tjoudeh Any update on this?

@domaindrivendev It looks like Password Flow support has landed in swagger-ui Master: https://github.com/swagger-api/swagger-ui/pull/2397
Are there any changes that need to be done in Swashbuckle to include this?

@domaindrivendev I'd appreciate a response to my comment above.

This would interest me, too.

I am also interested in the latest version of swagger ui.  I believe the current version is 3.0.9 and seems to add additional support for the OAuth forms.

Does anyone have some documentation on how to implement password flow?

authors: FelschR Shark75 ciscocabe domaindrivendev lookwhatisee pdusen remiplanglois rexthuhking rifaj tjoudeh

repo: domaindrivendev/Swashbuckle


text:
Accessibility fix

Remove the location button's href link (<a href="#">) to remove the empty link accessibility issue. See WebAIM's website for more information about web links and accessibility.
Before

After

Thank you! Merged and released with 0.60.0.

authors: domoritz geospatialem

repo: domoritz/leaflet-locatecontrol


text:
Move block binaries/scripts out of the config directory

As pointed out by a user, the actual block binaries and/or scripts should not reside in the config directory. I don't think this is actually required even now, as long as the scripts are in PATH, succade should be able to run them. Apart from that, can we currently specify the path to the bin/script in the config files? If not, we should have that option. In other words, decouple bin/script and config file, effectively making the blocks just a config file. It is then up to the user where the bin/script actually is. Let's look into this.

A quick glance at the code reveals that we need to slightly change the logic behind initializing and running blocks. Also, we need to add a config option to specify the binary to use, I suggest bin. This should not be too much work.

repo: domsson/succade


text:
Use standard version of graphql java

Could you switch to use the standard version of graphql-java: https://mvnrepository.com/artifact/com.graphql-java/graphql-java/3.0.0

Hi, @TerryTran
Not yet, my implementation using this class: https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/schema/CoercingSerializeException.java (it's available only on snapshot version).
Waiting for release of new graphql-java.

authors: TerryTran donbeave

repo: donbeave/graphql-java-datetime


text:
updating chat guide to use updated supermodel generator

closes https://github.com/donejs/donejs/issues/802.

Coverage remained the same at 96.396% when pulling 33af60bedbaab72797338d3288f8aaccd0ae9327 on chat-guide-models into b9de09adfc883b4cc2b35d421ca441e380659f6e on major.

Coverage remained the same at 96.396% when pulling 33af60bedbaab72797338d3288f8aaccd0ae9327 on chat-guide-models into b9de09adfc883b4cc2b35d421ca441e380659f6e on major.

authors: coveralls phillipskevin

repo: donejs/donejs


text:
Implementation of exchangeability testing

Hi donlnz,
thanks for creating this lib. Did you already plan how to implement the exchangeability testing from:
[2] Fedorova, V., Gammerman, A., Nouretdinov, I., & Vovk, V. (2012). Plug-in martingales for testing exchangeability on-line. In Proceedings of the 29th International Conference on Machine Learning (ICML-12) (pp. 1639-1646).?
I would be willing to contribute as this is related to my area of research.
Best regards
Nicolas Jourdan

@nicolasj92 are you familiar with any other exchangeability testing implementations?

repo: donlnz/nonconformist


text:
No copy-audio option in other_video_transcoding

Hi Don,
I've been using your tool to transcode blu-ray rips, and I really just want to use it to transcode the video but keep the audio track intact. Video transcoding had a flag for --copy-audio, which does not seem present in Other video transcoding.
Is there a way to do full audio passthrough with other video transcoding?
Thank you.

@sweaver2 Thanks for using my tools. Yes, there's a way to copy original audio tracks with other-transcode. But I don't make it obvious because I strongly discourage the practice. It simply goes against the goal of transcoding into a smaller, more portable format.
If you use other-transcode --help full and look in the "Audio options" section you'll see that there's an audio width that can be specified besides surround and stereo. Just use original for the width and the track will be copied. So, to copy instead of transcoding the main audio track you would add this option and argument to your command line:
--main-audio 1=original

If you only want to copy lossy DTS and DTS-ES audio then you would add then you would add this option to your command line:
--pass-dts

Does that answer your question?

Yes I believe it does, thank you for the info and the quick reply!

@sweaver2 No problem and glad to help. I'll close this now then.


text:
AppleID Sign in prompt.

Discussed in https://github.com/dooboolab-community/react-native-iap/discussions/2655

Originally posted by sleep9 December 27, 2023
await initConnection();
This snippet is prompting the user to sign in to apple. However I am already signed in. What gives?

Resolved by adding a sandbox account and signing in with that.

repo: dooboolab-community/react-native-iap


text:
TypeError: Cannot read property 'stopRecorder' of undefined

I can see the audio player when I press play it says it is undefined.
It works just fine on Android.
I have checked everywhere (all the files) to see if that is a linking issue and found that it is not showing up in products in pod folder (Attached screenshot below) but not sure it is happening due to the same or not.
Version of react-native-audio-recorder-player: 2.2.2
Platforms you faced the error (IOS or Android or both?)
IOS
Expected behavior
Start recording

you got some solution?

Nope still looking for solution.

any solution?

Nope switched to the react-native audio toolkit and it is working fine.

Please try 2.2.3 and come back for current issue.

now i don't get the undefined error but still i cann't record anything in ios, recorder will start but i'ts not working as expected, the 'addRecordBackListener's current_position is always 0

Please try 2.3.0.

Hi, @hyochan  I have tried v2.3.0 and the good news is that I am not facing undefined error but recording seems broken as I am also getting current_position as 0 always in 'addRecordBackListener'.

@simformsolutions Which platform are you facing this? Did you also try example project in repo?

authors: aliotadi chandanrai95 hyochan simformsolutions


text:
Add allocating array

Omitted allocating array. This will fix the issue. Sorry.

#255 resolved

authors: JJMoon dooboolab

repo: dooboolab/react-native-iap


text:
Update types for transactionDate to be a number

As received inside purchaseUpdatedListener on a subscription purchase.
So either the types need to change, or the package should parse the transactionDate as a number. I've chosen to just change the types, as that might be more backward compatible.
Might be good to parse it as a number in the future, as it is actually a number.

(black rectangles are redacted, not related to this PR)

Ahh, that's why I had troubles with creating a Date object from it! Well spotted 👏

I'll check it today!

@hyochan , you are correct. On iOS it's a number. I'll change the types to transactionDate: string | number then. Then you'll get correct type warnings.

But even better would be to change this line: https://github.com/dooboolab/react-native-iap/blob/3d0f991db16a013dbac4920936cbc6fc09283cff/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L296
item.putString("transactionDate", String.valueOf(purchase.getPurchaseTime()));

Probably like this?
item.putInt("transactionDate", purchase.getPurchaseTime());

@jvandenaardweg That sounds much better. Would you please update this in current PR?

https://github.com/dooboolab/react-native-iap/pull/681/commits/ae9597d608820820d9608f9a7bc5502969dae584 converts the long to a double, so JS picks it up as a number. As suggested here: https://github.com/facebook/react-native/issues/9685#issuecomment-244530834

@hyochan , you are correct. On iOS it's a number. I'll change the types to transactionDate: string | number then. Then you'll get correct type warnings.

I think it's good to make this a number on Android too. For future updates of the package.

Hi, could you help me to understand, how I can debug IAP without publish .apk to google play. Thank you!

Hi, could you help me to understand, how I can debug IAP without publish .apk to google play?

You can't. You need a release in one of the tracks in Google Play Console, preferably a non-production track, so you can debug.

Hi, could you help me to understand, how I can debug IAP without publish .apk to google play?

You can't. You need a release in one of the tracks in Google Play Console, preferably a non-production track, so you can debug.

But, how you did get info in console? I can't understand how to get this info for fix bugs with transactionReceipt. thank you!

But, how you did get info in console? I can't understand how to get this info for fix bugs with transactionReceipt. thank you!

By just using a console.log and use React Native Debugger or the console in http://localhost:8081/debugger-ui

authors: 404-html hyochan iutin jvandenaardweg


text:
Add receipt validation option

Hey @hyochan !
First I have to thank you for the awesome work on react-native-iap 👍
I'm maintaining a few open source projects myself and I know the commitement and time it takes.
Secondly, thank you for starring react-native-iaphub 🙏
Your module is making IAP easy on the client side and I'm trying on my side with IAPHUB to take care of the pain validating receipts on the server side...
react-native-iaphub is just a simple wrapper of your library directly communicating to IAPHUB.
Was thinking it would be cool to add an option using iaphub in the "Receipt validation" section of the README 🙂
I added the section in this PR if it sounds good to you.
Thank you!

Thanks @hyochan ! Will definitely do when I can

@maxs15 Could you also notify our modules to IAPHUB. That would make us feel friendly :) You can use our [logo[(https://user-images.githubusercontent.com/27461460/75094417-20321b00-55ce-11ea-8de7-a1df42a4b7df.png) if you want!

I added a link to your repo on the top of the README 🙂


text:
[Help] how to avoid row value "null" display when data is null

PlutoColumn(title: "id", field: "id", type: PlutoColumnType.text()),

when data value is ['1', null, '3']

how to replace "null" to empty
I have solution like
  List<PlutoColumn> columns = [
    PlutoColumn(
        title: "id",
        field: "id",
        type: PlutoColumnType.text(),
        formatter: (value) {
          if (value == null) return '';
          return value.toString();
        },
        readOnly: true),
  ];

but is there are simply way?

You have to use the renderer property and return the Text widget with the value by checking the value before if it was null to view anything else.

renderer should give you full control of the cell widget, or you may change null to '' when you build the cells array ( alter the data )

authors: design2023 doonfrs yunchiri


text:
[Snyk] Upgrade next from 14.2.10 to 15.0.2

Snyk has created this PR to upgrade next from 14.2.10 to 15.0.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠ Warning: This PR contains major version upgrade(s), and may be a breaking change.

The recommended version is 318 versions ahead of your current version.

The recommended version was released on a month ago.

[!IMPORTANT]

Warning: This PR contains a major version upgrade, and may be a breaking change.
Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

:no_entry: Snyk checks have failed. 8 issues have been found so far.

Icon
Severity
Issues

Critical
0

High
0

Medium
8

Low
0

:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:no_entry: license/snyk check is complete. 8 issues have been found. (View Details)

repo: doperiddle/web-examples


text:
How to get the GICS code for a given stock

Is there a way to find which industry is a stock in.
like, how to get which industry is APPLE in?

Consumer Electronics.

repo: dorklein/py-gics


text:
[Snyk] Security upgrade ubuntu from 14.04 to trusty-20190515

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

builder/parser/testfiles/kartar-entrypoint-oddities/Dockerfile

We recommend upgrading to ubuntu:trusty-20190515, as this image has only 266 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

536
Improper Check for Dropped Privileges SNYK-UBUNTU1404-BASH-542607
Mature

829
Off-by-one Error SNYK-UBUNTU1404-SUDO-1065770
Mature

686
Improper Privilege Management SNYK-UBUNTU1404-SUDO-3234995
Mature

686
Improper Handling of Exceptional Conditions SNYK-UBUNTU1404-SUDO-473059
Mature

536
Out-of-bounds Write SNYK-UBUNTU1404-SUDO-546522
Mature

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Privilege Management

BS bot


text:
Interface resolvers should have only __resolveType method

Describe the bug
When a Graphql interface is resolved, the resolvers of only the implementing type (returned by __resolveType method of the interface) are called. The resolvers of the interface is never called (expect the __resolveType method). Therefore, the interface resolver should only require the implementation of resolveType field. However, current version require the interface resolver to implement every field of the interface. I tried using useImplementingTypes: true option but that didn't do anything.
"@graphql-codegen/cli": "^1.21.1",
"@graphql-codegen/typescript": "^1.21.0",
"@graphql-codegen/typescript-resolvers": "^1.18.2",

schema: ''
generates:
./src/generated/codegen-server.ts:
    schema:
      - 'src/schema-shared.graphql'
      - 'src/schema.graphql'
    plugins:
      - 'typescript'
      - 'typescript-resolvers'
    config:
      contextType: ../types#Context
      useIndexSignature: true
      avoidOptionals: true
      showUnusedMappers: true
      useImplementingTypes: true
      # optionalResolveType: true
      noSchemaStitching: true
      federation: true
      nonOptionalTypename: true
      mappers:
        Comment: ../types#CommentMapper
        Commentable: ../types#NodeMapper
        Likeable: ../types#NodeMapper
        Node: ../types#NodeMapper
        Bookmarkable: ../types#NodeMapper
        Flaggable: ../types#NodeMapper
        CommentConnection: ../types#CommentConnectionMapper

Hmm makeExecutableSchema from graphql-tools inherits resolvers from interfaces with inheritResolversFromInterfaces flag so this is not 100% true for all cases.
Also I see you're using avoidOptionals which causes every single field should be implemented individually.
@dotansimha Maybe we should add this flag to the resolvers plugin but this would be a breaking change for existing users?

I'm all in with having this as a flag, to avoid breaking changes. PRs are welcome!

@skk2142 I created a PR for this here: https://github.com/dotansimha/graphql-code-generator/pull/5666
Can you please try the alpha version and let me know if it works well for you? It's @graphql-codegen/typescript-resolvers@1.19.0-alpha-c6305bc9.0 .

Yes it works on using onlyResolveTypeForInterfaces: true option. Thank you!

thank you for the quick feedback. Keeping open until we'll release that :)

Available in @graphql-codegen/typescript-resolvers@1.19.0

authors: ardatan dotansimha skk2142

repo: dotansimha/graphql-code-generator


text:
unable to read property list from file: /Users/testuser/Desktop/bluetooth-ble/ios/bluetoothble/Info.plist: The operation couldn’t be completed. (XCBUtil.PropertyListConversionError error 2.)

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
[ ] I'm running the latest version

Question
Hi, I get the following error when debugging on iOS. I researched this error on the internet but could not find a solution. Does anyone have any ideas on this subject?
Error is here:
unable to read property list from file: /Users/testuser/Desktop/bluetooth-ble/ios/bluetoothble/Info.plist: The operation couldn’t be completed. (XCBUtil.PropertyListConversionError error 2.)

This is likely unrelated to the library itself but rather to formatting thst plist file. Can you share it here?

This is likely unrelated to the library itself but rather to formatting this plist file. Can you share it here?

The problem was that in the info plist file, the line where I gave the bluetooth permission affected other lines. I solved this problem, thank you.

Closing as issue seems to be resolved

repo: dotintent/react-native-ble-plx


text:
Fixed issue #2045

What kind of a pull request is this?

QA / Code Review

Code Checklist

[ ] The code follows dotkom code style
[ ] The code passes the defined tests
[ ] I have added tests for the code I added
[ ] I have provided documentation for the code I added
[x] The code is ready to be merged

(Possible) Breaking Changes

[ ] The changes are backwards compatible

[ ] I have updated the build configuration
[ ] These changes requires changes to configuration in production

[ ] I have applied the required changes in production
[ ] I cannot apply the required changes in production before this is deployed.

Description of changes
Css is changed in article.
Screenshot(s) if appropriate

Fix isort then merge.

authors: aslakhol monikahm


text:
Update mark duration from 30 to 20 days

Description of changes

Online wishes to change the duration of a mark from 30 days to 20 days.
Code Checklist

[ ] I have added tests
[ ] I have provided documentation

Visual changes

Before

After

It might be preferable to make the duration configurable instead, and make a db-migration so that it defaults to 30 for existing marks, so that this does not have a retroactive side-effect

The change on the mark duration should affect all marks(not only the new ones). With that in mind is it still preferable to attach the duration to the MarkRuleSet?

status? @Thomhas 😳😳😳😳😳

status? @Thomhas 😳😳😳😳😳

Soon!

authors: Thomhas anderssonw henrikhorluck


text:
Move snippets to project file

Create Rgd3 folder to contain sample here and follow Rdg1

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e9bda968-e2c8-dabb-94bf-aff0381d3bd4
Version Independent ID: e9bda968-e2c8-dabb-94bf-aff0381d3bd4
Content: RDG003: Unable to resolve parameter
Content Source: aspnetcore/fundamentals/aot/request-delegate-generator/diagnostics/rdg003.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @captainsafia
Microsoft Alias: safia

This error may be used in .NET 9


text:
Blazor Working With Images Docs

Fixes: https://github.com/dotnet/aspnetcore/issues/36991
Fixes: https://github.com/dotnet/aspnetcore/issues/37016

@guardrex for your consideration. As always feel free to change / edit as you see fit 😄

I'll be OOF for a few hours this afternoon. If you're ready for me to proceed :ear:, I'll edit and ping you back this evening. I couldn't tell if you were done because of the suggestion up there for Line 187 :point_right:.

I'll be OOF for a few hours this afternoon. If you're ready for me to proceed 👂, I'll edit and ping you back this evening. I couldn't tell if you were done because of the suggestion up there for Line 187 ☝.

Yep all ready, committed the suggestion for 187 😄

Ok, thanks. I'll ping u back later today for the final look and updates.

@TanayParikh ... Let's start with this, but I'll edit it again in the morning.
btw --- You don't say where to call ...
URL.revokeObjectURL(url);

btw --- You don't say/show where to call ...
URL.revokeObjectURL(url);

There isn't really a set location to call URL.revokeObjectURL(url), it depends on when you're done with the image. For example, in a form, after the user "submits" the data, you may wish to revoke the object URL as it will no longer be needed.

@TanayParikh ... I ran into a few more nittish-new-topic things this morning on the edit, and some of this is just an FYI for future reference:

Fully working, cut-'n-paste examples are popular with readers. I go ahead here with the first (basic) example and set it up that way. With our built-in Copy code button in live docs, it's great. I've added this topic (and the download files topic) to my UE pass tracking issue for more work like this later.
I added a line about when to call URL.revokeObjectURL(), but it's still confusing: We don't say "object URL" or have a url var anywhere above this remark, so it's still not clear where/how/on what it should be called. btw ---- and along the lines of a fully-working example ---- do you have a fully working example of this component that you could paste into a comment here? Immediately before the revokeObjectURL remarks, I could add it ... "Here's the complete code for the Razor component:" ... and then show the full component that would show revokeObjectURL being called. Then, we could have it say, "In the preceding component, URL.revokeObjectURL() is called to ..... (proceed with our current text).
I moved the JS for the last two examples into a lead-in under an H2 heading. Again, this will facilitate (eventually) fully working/cut-'n-paste examples.

This looks great, thanks!
Agree copy+paste would help simplify things 😄

Do you have these last two components/JS bits in fully working form such that you could paste them into a comment here (or provide a link to a GH repo where you have them)? If not, no worries ... I'll get them set up later when I get back to this topic for more work. I'll ping u on that PR, which very likely wouldn't be until 22H1.

I had working bits aligned with my initial commit, but there's been some churn in the docs so my code isn't up-to-date anymore. I think this should be fine for now ✅

authors: TanayParikh guardrex


text:
Http logging in dotnet 8 doesn't work without call AddHttpLogging

Based this issue on aspnetcore repository, HTTP logging without call AddHttpLogging method doesn't work and get exception.
I added this line to the doc

Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/http-logging/index.md
HTTP Logging in ASP.NET Core

Thanks for the fix, @naeemaei !

authors: naeemaei tdykstra