Can't deploy external resources to outside wwwroot

Plugin name and version

OS: Mac
Plugin: Azure-webapp-maven-plugin:1.13.0-SNAPSHOT

Plugin configuration in your pom.xml
<plugin>
 <groupId>com.microsoft.azure</groupId>
 <artifactId>azure-webapp-maven-plugin</artifactId>
 <version>1.13.0-SNAPSHOT</version>
 <configuration>
 <schemaVersion>v2</schemaVersion>
 <resourceGroup>testrg</resourceGroup>
 <appName>webapp128www</appName>
 <pricingTier>P1v2</pricingTier>
 <region>westeurope</region>
 <deployment>
 <resources>
 <resource>
 <directory>${project.basedir}</directory>
 <targetPath>../relativeAdditional/test</targetPath>
 <includes>
 <include>*.xml</include>
 </includes>
 </resource>
 </resources>
 </deployment>
 <runtime>
 <os>Windows</os>
 <javaVersion>Java 8</javaVersion>
 <webContainer>Tomcat 8.5</webContainer>
 </runtime>
 </configuration>
 </plugin>

Actual behavior
[INFO] Successfully created Web App webapp128www.
[INFO] Trying to deploy artifact to webapp128www...
[ERROR] Status code 500, "{"Message":"An error has occurred.","ExceptionMessage":"End of Central Directory record could not be found.","ExceptionType":"System.IO.InvalidDataException","StackTrace":"   at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()\r\n   at System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)\r\n   at System.IO.Compression.ZipArchive..ctor(Stream stream, ZipArchiveMode mode, Boolean leaveOpen, Encoding entryNameEncoding)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<>c__DisplayClass21_0.b__1() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 720\r\n   at System.Threading.Tasks.Task.InnerInvoke()\r\n   at System.Threading.Tasks.Task.Execute()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.d__21.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 726\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.d__17.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 542\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 235\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass8_0.<b__0>d.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 115\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Contracts.Infrastructure.LockExtensions.d__51.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Contracts\\Infrastructure\\LockExtensions.cs:line 100\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.<FetchDeploy>d__8.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Core\\Deployment\\FetchDeploymentManager.cs:line 108\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<PushDeployAsync>d__15.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 444\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<OneDeploy>d__11.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 336\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__31.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()"}"
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:46 min
[INFO] Finished at: 2021-01-28T15:51:38+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.13.0-SNAPSHOT:deploy (default-cli) on project webapp1: Status code 500, "{"Message":"An error has occurred.","ExceptionMessage":"End of Central Directory record could not be found.","ExceptionType":"System.IO.InvalidDataException","StackTrace":"   at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()\r\n   at System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)\r\n   at System.IO.Compression.ZipArchive..ctor(Stream stream, ZipArchiveMode mode, Boolean leaveOpen, Encoding entryNameEncoding)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<>c__DisplayClass21_0.b__1() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 720\r\n   at System.Threading.Tasks.Task.InnerInvoke()\r\n   at System.Threading.Tasks.Task.Execute()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.d__21.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 726\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.d__17.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Services\Deployment\PushDeploymentController.cs:line 542\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 235\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass8_0.<b__0>d.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 115\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Contracts.Infrastructure.LockExtensions.d__51.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Contracts\\Infrastructure\\LockExtensions.cs:line 100\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Core.Deployment.FetchDeploymentManager.<FetchDeploy>d__8.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Core\\Deployment\\FetchDeploymentManager.cs:line 108\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<PushDeployAsync>d__15.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 444\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<OneDeploy>d__11.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 336\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__31.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()"}" -> [Help 1]

Test pass.


Performing an image build with RUN adduser -u<PHONE_NUMBER> will result in no space left on host

Description
Doing an adduser -u<PHONE_NUMBER> in a RUN will cause the filesystem on the host to fill up and report a No space on device left.
Steps to reproduce the issue:

Create a Dockerfile with RUN adduser user -u<PHONE_NUMBER> -g 0 -r -m -d /home/user/ -c "Default Application User"
Perform docker build -t test .
Wait until no space left on device is shown

Describe the results you received:
Step 3 : RUN adduser user -u<PHONE_NUMBER> -g 0 -r -m -d /home/user/ -c "Default Application User"
 ---> Running in e8472dbea9bf
ApplyLayer exit status 1 stdout:  stderr: write /var/log/lastlog: no space left on device
ERROR: Build failed: exit code 1

Describe the results you expected:
Succeeding build
Additional information you deem important (e.g. issue happens only occasionally):
Reproduced on GItlab CI runner as https://gitlab.com/gbraad/issue-docker/builds/6767776 (Source Dockerfile can be found in the repo: https://gitlab.com/gbraad/issue-docker)
Output of docker version:
Client:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-46.el7.centos.10.x86_64
 Go version:      go1.6.3
 Git commit:      d381c64-unsupported
 Built:           Thu Aug  4 13:21:17 2016
 OS/Arch:         linux/amd64

Server:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-46.el7.centos.10.x86_64
 Go version:      go1.6.3
 Git commit:      d381c64-unsupported
 Built:           Thu Aug  4 13:21:17 2016
 OS/Arch:         linux/amd64

Output of docker info:
Containers: 38
 Running: 0
 Paused: 0
 Stopped: 38
Images: 71
Server Version: 1.10.3
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: journald
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.10.0-327.22.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 1
Total Memory: 489.1 MiB
Name: vps13.novalocal
ID: ATDQ:VMVE:SNUV:P67X:KPBK:DHHF:JFII:O23Q:VPVU:HV6I:6BZO:FE36
Username: gbraad
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Registries: docker.io (secure)

Additional environment details (AWS, VirtualBox, physical, etc.):

Confirmed that this is still an issue in master 1ef10c8.
reproduction: curl https://gitlab.com/gbraad/issue-docker/raw/master/Dockerfile | docker build -
docker info:
Containers: 2
 Running: 0
 Paused: 0
 Stopped: 2
Images: 332
Server Version: 1.14.0-dev
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: 2k42xdn0j840958vyndm2jm8i
 Is Manager: true
 ClusterID: yk5quoro08hfi7sa31orgc2ph
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e
runc version: 51371867a01c467f08af739783b8beafc154c4d7
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-47-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 14.69 GiB
Name: ws01
ID: SN3T:CNK6:JKQD:54CY:XKF2:BRX3:CIRU:DQBT:6DVZ:VWQ2:Q5ET:F23L
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 28
 Goroutines: 127
 System Time: 2016-11-29T07:10:46.152785794Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

When I hit the issue, /var/lib/docker/overlay2/876025c2a053c0f8ccc8ceaeb8d4a508e31493277513c287672444c24e19a1dd/diff/var/log/lastlog grews up extremely large (filled with zero bytes).
Probably the issue is a bug of the implematation of adduser used in Fedora, rather than a bug of Docker itself?

Closing as a dupe of https://github.com/docker/docker/issues/5419#issuecomment-41786665

The underlying issue is that a large sparse file is created (approximately 32 GB), but it's not exactly a Docker bug.

As mentioned in https://github.com/docker/docker/issues/5419#issuecomment-41478290, adduser -l should work

@AkihiroSuda I am not sure how severe this is... although adduser -l will fix this, but as an automated build on Docker Hub this will result in the same error: https://hub.docker.com/r/gbraad/issue-dockerfile/builds/bsdmngknf8dhfreh8sgfmyu/

Just doing some hacking with info I found on the internet.  Built a script that checks for sparse files.
cat /usr/bin/sparse
#!/bin/sh
sparse() {
	file=$1
	if [ "$((`stat -c '%b*%B-%s' -- "$file"`))" -lt 0 ]; then
	    echo "$file" is sparse
	fi
}
while IFS='' read -r file || [[ -n "$file" ]]; do
      sparse "$file"
done

# find /var/log -type f ! -size 0 | sparse
/var/log/lastlog is sparse

Could we change docker commit to not save sparse files and just zero them out?

We would need to wait for https://github.com/golang/go/issues/13548 to implement that.
(Or we can fork the tar pkg)

Last action on that was 9 Months ago.  :^(

@rhatdan seems like someone commented on that pr to get a fix in by go 1.9 (more likely 1.10)

Let's hope so, as this can cause issues with automated build processes.


begin implementation of POVButton

If we're using the Logitech 3D stick, then get the POVButton library at least set up in oi.py. We may have use of it.

Implementation complete.


Test-Runner Changes Project Settings file

Bug description
Test Runner changes
ProjectSettings/ProjectSettings.asset
specifically it edits this setting
runInBackground: 0
to
runInBackground: 1
this change is not reversed after the testing step is done, and so the branch is flagged "dirty" and this prevents the Building step from being executed.
And this error is showed
Warning: Changes were made to the following files and folders:

Warning:  M ProjectSettings/ProjectSettings.asset

Error: Branch is dirty. Refusing to base semantic version on uncommitted changes

How to reproduce
run the Test Runner step with any configuration on a unity project in a github repository through git hub action as follows:
name: Actions 😎

on: [push, pull_request]

jobs:
  build:
    name: Build my project ✨
    runs-on: ubuntu-latest
    steps:
      # Checkout
      - name: Checkout repository
        uses: actions/checkout@v2
        with:
          lfs: true

      # Cache
      - uses: actions/cache@v2
        with:
          path: Library
          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
          restore-keys: |
            Library-
     # Test
      - name: Run tests
        uses: game-ci/unity-test-runner@v2
        env:
          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
        with:
          githubToken: ${{ secrets.GITHUB_TOKEN }}

      # Build
      - name: Build project
        uses: game-ci/unity-builder@v2
        env:
          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
        with:
          targetPlatform: StandaloneWindows64

      # Output
      - uses: actions/upload-artifact@v2
        with:
          name: Build
          path: build

Expected behavior

if the testing step runs successfully,the build should also run successfully and produce the built project as an artifact
Additional details
The project is built successfully if the same script is used but with out the test runner step, so the test runner is probably creating the problem
This is the project : https://github.com/Hussein-Attie/BugFixing3.git

Looking at your project, I don't see any test cases.
The unity-test-runner action is only intended to be used with test cases that use the Unity Test Framework: https://docs.unity3d.com/Manual/com.unity.test-framework.html
My recommendation is to either:
a) add some test cases
OR
b) remove the test step

oh thanks so much, I am really sorry for the late reply but that's because of the power outage , I will be removing the test step as we do not need testing now.
Thanks so much again


Fix #11: be more defensive about malformed input data.

Closes #11.

Thanks for the PR, @dblock. We've gone ahead and put in a fix.

I looked at https://github.com/actions-on-google/actions-on-google-nodejs/commit/cbfa71ac7385821058c77c893cee05672f3b0885, you took the code change, but not the test. Can you add the test too please so that this doesn't break in the future?


Security problem in /config/admin.js

I can see the ADMIN_JWT_SECRET into a raw string instead of an environment variable

That's provided as a default - if you set ADMIN_JWT_SECRET environment variable yourself that that default wouldn't be used.


feat: functionality to reorder schedules

Users should be able to reorder their schedules through the schedule dropdown via a drag and drop reorder functionality
Current:

Expected behavior:

We can't do this because of the RDS migration. I just realized this, and I wanted to tell you before you spend too much time on it.
Ideally, this would be a feature, but I don't know how to support it in the DB just yet.

That makes sense. We can discuss this more once RDS migration is fully completed, if not already.

I have figured it out. You can move forward with it. Sorry for the confusion


[optimization] Disk/Bandwith usage optimizations for IPLD NMT and Samples

Right now, we store/exhange on the network redudandant data:

1 byte for NMT IPLD node type

It is possible to get NMT Node type indirectly, without serializing the type itself. WE can look at the amount of links.

Additional node per each leaf node

This was also a quick solution for a problem that can b solved without introducing one more ipld node.

8 bytes additional Namespace for each share via NMT wrapper

Can be avoided if we enable once https://github.com/celestiaorg/nmt/issues/55 is resolved

For each inner non-leaf node, we prepend an additional byte.

It is possible to get Namespace for each share encoded in inner non-leaf nodes of the NMT tree.

I think I get it, but I'm not 100% sure. Mind elaborating on this a bit more? What if some non-leaf nodes, along with their respective leaf nodes, can't be found?

Referencing this here as it is highly related: https://github.com/celestiaorg/celestia-node/pull/244#discussion_r761576295

@liamsi, I made a separate issue out of this. Even though they are related, your comments deserve a separate issue.

https://github.com/celestiaorg/celestia-node/pull/464 relies on the fact that our NMT tree looks like:
---X
-X---X
X-X-X-X
X-X-X-X

While one of the points of this issue is to make the tree look like this:
---X
-X---X
X-X-X-X

So once we fix this issue, we should also fix https://github.com/celestiaorg/celestia-node/pull/464

8 bytes additional Namespace for each share via NMT wrapper
Can be avoided if we enable once

Why can't it be avoided today? Storage format is an implementation detail. So long as you can losslessly convert between formats, it doesn't matter what it's stored as.

@adlerjohn you are right. It can be avoided today. See https://github.com/celestiaorg/nmt/issues/55#issuecomment-1118931841

@johnadler, it can be avoided. My understanding was that we have to store everything we commit to via nmt.Push, but I missed that we can avoid storing some pieces of shares on the fly via Visitor in nmt and add them on the fly as well. However, as pointed out in the linked nmt issue, this is somewhat hacky, and, actually, a leaky abstraction that should be avoided ideally.

Grooming 12/07/2022:

if we are fine with the current stack, we need to have this implemented before Incentivized Testnet

We need this before incentivized testnet.

The description is now up to date


Text with length <= 2 become invisible

All works perfectly, if text length is 3 or more, but with 2 or less text length TextView's width become 0

@Syjgin i've tested on text with size 1 and 2 chars. Library works fine. Can you provide test code to reproduce this bug?


use BTreeMap instead of HashMap to always serialize the same

It happened to me the psbt added in the test case was sometimes serialized in a different byte array.
That is due to the fact this psbt has 2 partial sigs in the map and rust HashMap is randomized.
This PR propose to use BTreeMap which is visited in order.

Codecov Report

Merging #310 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #310      +/-   ##
==========================================
+ Coverage   81.72%   81.78%   +0.05%
==========================================
  Files          38       38
  Lines        6808     6813       +5
==========================================
+ Hits         5564     5572       +8
+ Misses       1244     1241       -3

Impacted Files
Coverage Δ

src/util/psbt/map/global.rs
61.79% <100%> (ø)
:arrow_up:

src/util/psbt/raw.rs
80.85% <100%> (ø)
:arrow_up:

src/util/psbt/mod.rs
86.06% <100%> (+0.24%)
:arrow_up:

src/util/psbt/map/input.rs
66.66% <100%> (ø)
:arrow_up:

src/util/psbt/map/output.rs
62.16% <100%> (ø)
:arrow_up:

src/util/psbt/serialize.rs
84.61% <0%> (+5.76%)
:arrow_up:

Continue to review full report at Codecov.

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

concept ACK. Curious what others think. There will be a perf/memory hit here. But on the other hand PSBTs can never get that large in practice..

@RCasatta Can you add a PSBT fuzztest (or if there is one, make it properly roundtrip instead of counting fields or whatever hack currently exists)?
I remember testing the PSBT PR I had a lot of trouble because of this.

added PSBT fuzztest, since fuzz data could be deserialized even if fields are out of order, the comparison is done in the following way:
if the fuzzed data is successfully parsed into a PSBT, then the test serialize/deserialize/serialize to compare to our own serialization.
(The fuzzer found a match on wrong code 0a30a48, impressive)

Nice! I think that's the best we can do.


All merge pr commiter is Gogs

After i merge a pr, this action's author is Gogs not me.
I think i should become the author of the merge action.

Work on it now.
cc @hickscorp I now understand what you were trying to report.

Pushed fix to master!

I click the button which displayed "Merge Pull Request", Then display error page "500". I think you can find the log in the server of try.gogs.io

Which PR you were trying to merge?

@Unknwon https://try.gogs.io/Meister/Test_Project/pulls/1

Fixed :wink:

@Unknwon Thank u!


fix: fixed the webpack build

Problem
The webpack build was failing for portal, trade-finance-manager-ui, and gef-ui.
Solution

The failure was because the webpack version had been updated, which required a more recent version of ajv.
I ran npm i webpack in each of the services to pick up the latest dependencies needed.

This generated the changes in the package-lock files
For trade-finance-manager-ui this was quite fiddly because there is a broken dependency between apollo and graphql. Which means you have to append --legacy-peer-deps to be able to run npm i. We seem to need --legacy-peer-deps in a few places. Is it worth raising a tech debt ticket to try and fix the dependencies, or one for this particular dependency? (Edit: Discussed on Slack, there are changes planned in TFM that will hopefully remove the need for using this flag, so there is no action needed for this PR)

I then ran npm run build to verify that the webpack builds all compile.

This generated the changes in the public folders

Further work

There are some warnings that come up in the webpack builds, which I will investigate as part of this PR

Seems to be missing package.json files with latest version for webpack and webpack-cli deps?

The webpack version in package.json was already updated on main in this commit: 78f0d7bd00.
I've not done anything to the webpack-cli version. Would you like me to update that as well?

Seems to be missing package.json files with latest version for webpack and webpack-cli deps?

The webpack version in package.json was already updated on main in this commit: 78f0d7b. I've not done anything to the webpack-cli version. Would you like me to update that as well?

Okay cool, I can see main already have all three UI latest version. Thanks

Few failing tests to address please.

There are some linting errors when I run npm run lint:all. But they also appear to happen on main so I don't think are introduced in these changes.
I can only see the errors when I run that command locally, does the linter get run in the pipeline at all? I might be missing it in this PR.
The linter is also run in the pre-commit hook. It's very slow to run for me, which might just be a VM issue, so I generally turn it off when developing and manually run npm run lint:all. Do other people find the same problem? If no-one's really using it we could potentially remove it.
Also, since it's broken on main at the moment, it feels like the checks it runs might be inconsistent with the checks run in the pipeline. So we could either remove the lint check from the pre-commit hook, or change it to match whatever check happens in the pipeline. What do you think?

@JennyHumphries don't worry about those lint:all failures, will fix in a new PR (I also spotted them during my last PR). I've done similar but I think it's a VM thing rather than an issue with the command itself - tempted to leave it for now and see how it performs when we get laptops and come back to it if it's an issue. Given it's tempting and easy to just turn off the pre-commit hook I agree might be worth duplicating the hook in the pipeline so we get to see it there too! (Don't think there is a linting step in the pipeline right now)

Looks like some old copy is in the E2E tests, or new copy is in there and it's not updated properly somewhere else.
Abhi was the fix just upgrading govuk dependency and have they got anywhere in their readme/changelog that 4.5.0 isn't compatible with the current version of webpack? Seems like an annoying place to lose some time on!


Renamed all "anObject" parameters

Fixes #211

Pull Request Test Coverage Report for Build 726

28 of 30 (93.33%)  changed or added relevant lines in 29 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.667%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/IMAPClient-Core.package/ICStreamWrapper.class/instance/host..st
0
1
0.0%

packages/IMAPClient-Core.package/ICStreamWrapper.class/instance/port..st
0
1
0.0%

Totals

Change from base Build 720:
0.0%

Covered Lines:
1232

Relevant Lines:
1650

💛  - Coveralls


Debentures

Mutual fund ra ipo ko difference pani apply garda dekhaunaparyo

Thanks for opening the issue! I have just released v0.3.5 with the suggested improvement.


Add full node snapshotting with enableFullNodeSnapshots flag

Summary:

Add full node snapshotting with enableFullNodeSnapshots flag (fromSnapshotObject(), toSnapshotObject())
Add prefix to both state label ('#state:') and radix label ('#radix:') in state proof

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/649

Comments addressed, PTAL! @liayoo

Thanks for the review! Now merging..


[vm/ffi] @Constant for compile-time null terminated strings

Would be nice to have to avoid managing allocations for C strings, and in AOT it could be part of the .rodata section of the executable.
Would support UTF-8 (Uint8) and UTF-16 (Uint16). Could be extended for value and struct constants behind a pointer as well.
@Constant('Hello, World!\n')
external Pointer<Uint8> get greeting;

puts(greeting);

// Or maybe...?
const greeting = Constant<Pointer<Uint8>>('Hello, World!\n');

puts(greeting.ptr);

cc @dcharkes

That's an interesting idea.
When addressing https://github.com/dart-lang/sdk/issues/47718, we should get the right infrastructure to do this.
Though, how do we provide an API for JIT in this case? Do we in JIT allocate at runtime and leak?
And maybe we can try to align the syntax with https://github.com/dart-lang/sdk/issues/50551.
// Global var in native asset, similar to `@Native external` function.
@NativeSymbol(/* optional symbol and asset */); // No type argument, as the Pointer already has it.
external Pointer<Uint8> get greeting;

// Global var in Dart.
@Constant('Hello, World!\n')
external Pointer<Uint8> get greeting;

Maybe if we address https://github.com/dart-lang/sdk/issues/50565 and https://github.com/dart-lang/sdk/issues/50551, we can just put them in a src/constants.c instead. Is there a strong preference for having them in Dart?

My preference for having them in Dart is mostly reducing the need to alloc & copy strings to the heap. It's a pain to manage temporary allocations for string-heavy APIs. A good example is Vulkan, where you have to look up all your functions using an instance-provided lookup function.
For JIT, the strings could live as long as the VM. Might require interning with a string cache of some kind.


Bump dependencies

See individual commits for details

Codecov Report

Merging #3186 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3186   +/-   ##
======================================
  Coverage    45.2%   45.2%
======================================
  Files         111     111
  Lines       11982   11982
======================================
  Hits         5416    5416
  Misses       5732    5732
  Partials      834     834

Flag
Coverage Δ

#linux
49.23% <ø> (ø)
:arrow_up:

#windows
40.58% <ø> (-0.03%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #3186 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3186   +/-   ##
======================================
  Coverage    45.2%   45.2%
======================================
  Files         111     111
  Lines       11982   11982
======================================
  Hits         5416    5416
  Misses       5732    5732
  Partials      834     834

Flag
Coverage Δ

#linux
49.23% <ø> (ø)
:arrow_up:

#windows
40.58% <ø> (-0.03%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM

this good to go? 🙏


Fix order of loading session settings

Currently the session simply overwrites default settings and if they
were not persisted before, they will be just null. Load session before
loading default config to fill empty places.
Signed-off-by: Tomas Slusny<EMAIL_ADDRESS>

I can reproduce this consistently one my PC where I did not reset settings, because of new Enum option in Prayer plugin, this bug basically stopped loading of the config panel, so the prayer panel was empty (well did not opened, and it was empty after going to another tab and back). It was because parsing of Enum failed, because Name was null (as the default config got overwritten). After this patch, Prayer panel is loading fine.

@Adam- So can this be added to next release? I saw that you said its ok to merge yesterday but I am not sure if it was related to this one.

This is now a regression from https://github.com/runelite/runelite/commit/cda98fc50e2490f3c124a0b3cbff109ae01b60ee where before having the plugin manager registers on the eventbus prior to plugins starting allowed it to load default plugin config when plugins were loaded, which prevented this.

Removed the clientSessionManager move around


Update SUPPORT.md

Update default support.md to reflect support policy provided by readme.md

This is wonderful, thank you for the contribution to clarify our support structure. I've added a couple of edits and am merging.


remove-vmpool-task-from-managepy

:+1:

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/298/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/299/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/300/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/301/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/302/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/303/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/304/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/305/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/306/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/307/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/308/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/309/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/310/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/311/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/312/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/313/
Test FAILed.

!test

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/314/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/315/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/316/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/317/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/318/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/319/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/320/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/321/
Test PASSed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/322/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/323/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/324/
Test FAILed.

!test

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/325/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.staging.regression/326/
Test PASSed.


Which D3 version is the official website code

How do I know the compatibility between D3 version and vue version

As far as I know there is no compatibility issue between D3 and vue. You can see the versions currently in use in https://github.com/d3/d3/blob/main/package.json


No active span with onError and onComplete

Hello!
Is there any reason to not wrap TracedSubscriber.onError() and TracedSubscriber.onComplete() within the active span?
I would like to access the span in both cases in order to have a clean log correlation.
Happy to contribute if needed!
Thanks.

Hey @NHebrard yeah, I don't see a reason why we can't wrap those as well. If you can make that PR and some coverage I can merge it in.

Hello @jam01
Thank you for the quick feedback, I will take care of it during the upcoming week.

@NHebrard Good catch for these 2 👍
Here are 2 test cases which can reproduce the bugs:
	@Test
	public void activeSpanShouldBeAccessibleInOnCompleteCallback() {
		MockSpan initSpan = tracer.buildSpan("foo").start();

		try (Scope ws = tracer.scopeManager().activate(initSpan)) {
			Flux.range(1, 5)
				.flatMap(i -> Mono.fromCallable(() -> i * 2).subscribeOn(elastic()))
				.doOnComplete(() -> assertNotNull(tracer.activeSpan()))
				.then()
				.block();
		} finally {
			initSpan.finish();
		}
	}

	@Test
	public void activeSpanShouldBeAccessibleInOnErrorCallback() {
		MockSpan initSpan = tracer.buildSpan("foo").start();

		try (Scope ws = tracer.scopeManager().activate(initSpan)) {
			Mono.error(RuntimeException::new)
				.subscribeOn(elastic())
				.doOnError(e -> assertNotNull(tracer.activeSpan()))
				.onErrorResume(RuntimeException.class, e -> Mono.just("fallback"))
				.block();
		} finally {
			initSpan.finish();
		}
	}

Thanks @NHebrard @chengchen ! The changes should be public under v0.2.0. Let me know if they are not.


Changed Security Structure

From previously of having a separate SecurityBox and SecurityManager handling the commands, I've changed so that logic now parses the commands, and checks whether user is authenticated to execute certain command.
One big problem though is that, how AddressBookParser works is that it first displays the invalid message command before it actually parse the arguments, but I would want to check authentication first before the invalid message occurs. Look at picture below. This is before the user is actually logged in.

As you can see even if the command is not fully typed, it should display this error message as seen below

Check whether the format is corrent/Try to match command word
1a. If wrong format/command doesn't exist (Parse exception), print invalid command message
Check authentication
2a. If not authorised (Authorize exception), print unauthorised message
Try to parse individual command
3a. If cannot parse (Parse exception), print usage message
Try to execute
4a. If cannot execute (Command exception), print usage message

Feels like the key is in splitting up point 1 and point 3 to insert point 2 in between. Now parseCommand() in AddressBookParser does point 1 and 3 in the same method, that's why it's causing this problem. Maybe consider splitting parseCommand() into, say identifyCommandWord(), which returns the correct command class (e.g. AddTimeCommand.class) and parseCommandArgs(), which returns the corresponding command if successfully parsed.

Maybe parseCommand() can return a Class object (https://docs.oracle.com/javase/8/docs/api/java/lang/Class.html) so security knows what command it is. Then check for authentication. Then try to parse it by calling the correct parser (somehow link the Class object to the corresponding parser)

Pulled upstream before comitting, fixed insane number of merge conflicts. Please do merge if passes all tests

Follow-up question: Even if we ignore the SRP-related "problems", why does checking for security need to happen twice (once during parsing and once during executing)? Seems to be double work

Follow-up question: Even if we ignore the SRP-related "problems", why does checking for security need to happen twice (once during parsing and once during executing)? Seems to be double work

It doesn't happen during executing, only parsing

One big question:
Why do the parsers throw security exceptions? Seems to be a big violation of SRP

Good question. Lets take it on slack to explain

Pretty sure the issues will drop by 5 once this cleared

To @nianfei97 questions above, perhaps the reply on slack will be hidden, ill copy paste here.

You are right it doesn't need, my new commits removes it.

Yep we need logic for keeping track of history, which is declared in logic


Have permissions be filtered (DelegatedWork or DelegatedPersonal) based on account type

Note: This is from an intern, but I forgot to add interns to my branch name.
Overview
I noticed when using Graph Explorer as a personal account (MSA) I still get shown DelegatedWork permissions. When I try to accept them I can't.

Demo
For instance,

a personal account should only see "User.Read".
What this bug fix shows:

What is currently shown (only DelegatedWork):

Notes
May want to change the "Not supported" thing that pops up.

Also I apologize for the PR I opened and then closed when I realized there were files I didn't want to merge.
Testing Instructions
No new tests were added because the function getProfileInfo is already being tested and it calls the new function I added. Currently all existing tests pass.

I've removed console.log(), the try catch and changed the code so that the profile contents in state does not get overwritten. I added a new function isBetaURLResponse that returns true or false and put the profileTypeSuccess in the existing if statement so the profile contents is not overwritten.

Thanks for your feedback and review @thewahome! Since I don't have permissions to merge the PR, would you be able to do that if the PR is ready? Thanks 😊!


Data page occasionally shows completely off ETH price

We've seen it in multiple occasions -

What number did you see when it was off?

ETH was around $414 when that screenshot was taken

Price is determined the same way the rest of the tokens are, which is slippageless cost of USD value of BNT.
If we consider Binance to be "market price" then a discrepancy here should illustrate an arbitrage opportunity.

Discussion with Yudi, utilise CryptoCompare to sus out USD price of BNT and ETH.

[ ] Sus out key requirement.

Now API sourced


Move React Native version dependency over to boilerplates

Related to #957, we should move the version dependency to our boilerplates.
• Issue a warning if opts.version is not set here
• Update ir-next and default to properly call out which RN version they want

This is the best route as it has been one issue I've been struggling with.


Cleanup core C# Adapters (BF Adapter and related)

Via @johnataylor:

we want to rewrite/refactor/cleanup the js and C# bf adapters

The initial plan here is to make a stepwise improvement to our unit test coverage in this area before we do any refactoring.

We are working on units tests in R10. Any refactoring is R11.

Closing because this is being handled in other CloudAdapter work.


i can not solve this ,help me please

git@github.com:orientechnologies/spring-data-orientdb.git
is empty? can you help me ? thanks

It's there alright https://github.com/orientechnologies/spring-data-orientdb.


Opening IndexdDB exception

Hi,
What is reason of  opening DB  exception "UnknownError: Internal error opening backing store for indexedDB"?
As I checked, When a transaction is running, any try to open DB raise this exception.
I run transaction with mode r!,rw!.
also when my transaction is ongoing , isOpen method return false value .

That exception happens when your browser's database is corrupt. Can happen for various reasons depending on browser. I've seen this error very rarely. What OS / browser are you on?

Hi,
My OS is Windows 10 and browser Google Chrome.

Google Chrome has a stable implementation except that it fails silently on quota exceeded. Make sure your DB has not reached the quota limit for your site. Other than that, I could only think of a corrupt hard disk or broken Google Chrome installation.

Hi @dfahlander, I need to bring this topic up again because the UnknownError with message "Internal error opening backing store for indexedDB.open." occurred again.
The MacBook of a colleague restarted unexpectedly while he used a web application with Dexie (IndexedDB). After the restart he reopened the web application and got the error. So it looks like the unexpected MacBook restarted ruined the database (which can now no longer be used).
Does IndexedDB support database journaling at all or is there any other activity that can be done to prevent such data loss? Can the IndexedDB get repaired?

There is nothing about disaster recovery in the indexedDB standard what I know of.

@dfahlander I am also facing this error when performing the delete operation. is the above issue resolved in newer versions or still exist ? we are using version 3.2.2
db.devicelogs
    .where(schema.deviceLogs)
    .between(startRange, endRange, true, true)
    .delete()
    .catch((e) => {
      if (e && e.name !== 'OpenFailedError') {
        console.log("Error: ", e)
      }
    });

I am able to replicate this error consistently in 118.0.5993.70 using a very specific set of steps:

On this page, Click + to add a couple items to the database.
Clear all Cookie & Site Data. (Click the Lock icon to the left of the URL bar and go to Cookies & Site Data -> Manage.  Then click the Trash button.)
Without reloading the page click the + button again. The count should go to 1 and, except for a warning in the console, all will appear normal.  Clicking + multiple times will continue to increment the count.
At this point, reloading the page will  lead to an UnknownError Internal error opening backing store for indexedDB.open.
Reloading the page again will work -- although edits made after the previous deletion are lost.

The problem does not occur when:

The page is reloaded after clearing Site data without pressing the button (creating another Dexie transaction).
Manually deleting the database via Dev Tools - only occurs when using the Clear Cookie & Site Data.

The code pen editor page is here: https://codepen.io/walexander/pen/oNmBWPy

It sounds marvelous that you found a way to reproduce this. Hopefully this repro could help chromium devs to fix the issue, but I'll start by verifying this and that it's not a Dexie issue before filling it further to the chromium bug tracker.

I tested the repro and it fails with UnknownError every time I repeat that procedure. I also use Chrome 118.0.5993.70 (on Arm64 (mac)).
I can confirm this is not a bug in dexie but a Chromium bug that need to be reported in Chromium bug tracker.
The good news is that the issue could be worked around by catching "UnknownError" and retry opening the database. I implemented the workaround in dexie and repeated the repro 10-15 times and the repro never failed to reopen the database the 2nd time so the workaround seems to solve this - at least when reproduced as described in the repro.
Immediately after clearing the site data, another chrome-issue is also being hit (#613) - that the call to db.transaction() fails with "InvalidState". This issue has already a workaround - so that dexie is able to reopen the database and retry the call to db.transaction(). Thanks to that workaround, the database succeeds to reopen the database when clicking the plus icon after clearing site data. After refreshing page we get the "UnknownError" instead, but by catching "UnknownError" from db.open() and doing a similar workaround there (retry db.open()) it seems to be successful to workaround both issues.
A new version of dexie@3 and dexie@4 will be out soon with the workaround.
It would be great if someone could report this issue to chromium bug tracker. Please post here a link to reported bug and refer to the repro we have in this bug. There's already a similar issue since 2020 in chromium bug tracker.

A workaround for this issue was released in<EMAIL_ADDRESS>The workaround is not release for<EMAIL_ADDRESS>(stable) yet.

It's amazing to see that Dexie continues to receive updates even after so many years. Keep up the good work, @dfahlander! 💪
Dexie is still an integral part of Wire's messenger. ⭐

I, too, get this error in Google Chrome with Dexie 3.2.4 when I use the browser function to delete all website data and reload the page.

I get this error too with Dexie 3.2.4, macOS, Chrome 124.0.6367.93 (arm64). I encounter it after using the browser function to delete all website data. Will the workaround still be released to Dexie 3?

I get this error too with Dexie 3.2.4, macOS, Chrome 124.0.6367.93 (arm64). I encounter it after using the browser function to delete all website data and reloading the page. Will the workaround still be released to Dexie 3?

It was released in 3.2.5. Latest 3.x is now 3.2.7.

Oh that's great, thank you, I will update!


[Bug] unused-argument when the argument is used in the default of another argument

What happened?
Given the following code:
Amazing Keyword
    [Arguments]    ${name}    ${message}=hello ${name}, how are you?
    Log  ${message}

Robocop will consider ${name} to be an unused argument:
//obfuscated/path/to/file.resource:0:0 [W] 0919 Keyword argument '${name}' is not used (unused-argument)

What command/code did you try to run?
robocop //obfuscated/path/to/file.resource

What is the full error message?
//obfuscated/path/to/file.resource:0:0 [W] 0919 Keyword argument '${name}' is not used (unused-argument)

What did you expect to happen instead?
I expect one of two things:

RoboCop should not flag this since ${name} is used in the default value of another argument.
The documentation of the rule should explain why RoboCops behavior is correct.

Operating System
Windows
Robocop version
5.0.0

I have tested it with your code but it does not shown as unused-argument for some reason.. are you using most recent Robocop version?

Ok I see you wrote in bug report that you used 5.0.0. I've just checked and I can reproduce this issue for 5.0.0 but not for 5.0.3 (recent). Please verify on your end

You're correct. I can't reproduce with 5.0.3. I did check the changelog and found nothing related to 0919 🤷♂
I'll close the issue

Yeah, I have also checked - I probably fixed it by foxing something else :) But I have added tests thanks to your issue so it will stay i our regression tests


clp-package: Add Python future.annotations import to allow running with Python 3.8.

Description

#416 used syntax that isn't supported by Python 3.8 without the __future__.annotations import. The effect of this is that the search scheduler can't run with Python 3.8 (and all searches will seemingly freeze).
This PR adds the import.
Validation performed

Built and started the package in an Ubuntu Focal container
Compressed some data
Used sbin/search.sh to run a query and ensured that it didn't freeze.

The PR title is fine to be used as the squashed commit message.

I agree with the new PR title to be used as the commit message.


Doesn't work with MSBuild 16.3

.nuget\packages\dasmulli.simplegitversion\1.0.0-rc1-0007\build\DasMulli.SimpleGitVersion.targets(100,5): error : This NuGet package is only supported for use with .NET SDK based projects.


docs(router): Added migration guide from ngrx/router to angular/router

@MikeRyan52 @fxck @robwormald

Thanks for doing this. I am planning to be porting in a few days.


Not able to fetch data from some URL's

I am using this library and doing something like this .
try {
showProgress(context);
var data = await extract("https://www.nst.com.my/news/nation/2020/05/595467/man-who-rescued-monitor-lizard-becomes-internet-hero");
} catch (e) {
hideProgress(context);
}
I am getting an exception.
I checked inside the library and the code showing exception at
JsonLdSchema(document) .
The issue is coming when i am extracting image from class JsonLdParser . I have attached an snapshot of the exception.

Thanks for bringing this up. I have to investigate this further.
The JsonLdParser needs more work as of now. I recommend trying OpenGraph or https://github.com/jg-l/metadata_fetch#get-html-metadata as it is much more stable.
`
import 'package:metadata_fetch/metadata_fetch.dart';
import 'package:http/http.dart' as http;
void main () async {
// Makes a call
var response = await http.get("https://www.nst.com.my/news/nation/2020/05/595467/man-who-rescued-monitor-lizard-becomes-internet-hero");
// Covert Response to a Document. The utility function responseToDocument is provided or you can use own decoder/parser.
var document = responseToDocument(response);
// get metadata
var data = MetadataParser.OpenGraph(document);
print(data);
}
`

The fix is merged.
https://github.com/jg-l/metadata_fetch/pull/6
Could you publish a new version, please.

The fix is merged.
#6
Could you publish a new version, please.

Done. 3.0.2 is published.


ERROR Cannot establish one or more browser connections. (docker 1.18.3)

What is your Scenario?
We run our tests on gitlabci using the official docker image testcafe/testcafe:1.16.0 and all is fine.
Tests are executed behind the proxy.
We tried to switch to a more fresh version 1.18.3 (changed only docker tag) but this resulted in the pipeline failure, tests are not executed and we see the next error:
ERROR Cannot establish one or more browser connections.
1 of 1 browser connections have not been established:
- chromium --start-maximized --incognito
Hints:
- Increase the value of the "browserInitTimeout" option if it is too low (currently: 2 minutes for local browsers and 6 minutes for remote browsers). This option determines how long TestCafe waits for browsers to be ready.
- The error can also be caused by network issues or remote device failure. Make sure that your network connection is stable and you can reach the remote device.```

- >
  /opt/testcafe/docker/testcafe-docker.sh "chromium --start-maximized --incognito"
  -c 1
  e2e/tests/*.test.ts
  --skip-js-errors --color
  --reporter spec,xunit:e2e/tests/reports/index.xml,html:e2e/tests/reports/index.html
  --video e2e/tests/reports/video
  --video-options singleFile=false,failedOnly=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.mp4
  -s takeOnFails=true,path=e2e/tests/reports/screenshots,fullPage=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.png
  --page-load-timeout 90000
  --assertion-timeout 60000
  --proxy $CODE_PROXY_HOST:$CODE_PROXY_PORT
  --page-request-timeout 60000
  -q attemptLimit=2,successThreshold=1

### What is the Current behavior?

Tests did not run

### What is the Expected behavior?

 Run any test in docker v1.18.3

### TestCafe version

1.18.3

### Node.js version

-

### Command-line arguments

    - >       /opt/testcafe/docker/testcafe-docker.sh "chromium --start-maximized --incognito"       -c 1       e2e/tests/*.test.ts       --skip-js-errors --color       --reporter spec,xunit:e2e/tests/reports/index.xml,html:e2e/tests/reports/index.html       --video e2e/tests/reports/video       --video-options singleFile=false,failedOnly=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.mp4       -s takeOnFails=true,path=e2e/tests/reports/screenshots,fullPage=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.png       --page-load-timeout 90000       --assertion-timeout 60000       --proxy $CODE_PROXY_HOST:$CODE_PROXY_PORT       --page-request-timeout 60000       -q attemptLimit=2,successThreshold=1

### Browser name(s) and version(s)

chromium

### Platform(s) and version(s)

-

### Other

-

Hi @dositec
I can not share my project but it is quite standard I would say.
gitlab.ci is similar to the documentation https://testcafe.io/documentation/402816/guides/continuous-integration/gitlab
e2e_tests:
  image:
    name: testcafe/testcafe:1.18.3
    entrypoint: ["/bin/sh", "-c"]
  script:
    - >
        /opt/testcafe/docker/testcafe-docker.sh "chromium --start-maximized --incognito"
        -c 1
        e2e/tests/*.test.ts
        --skip-js-errors --color
        --reporter spec,xunit:e2e/tests/reports/index.xml,html:e2e/tests/reports/index.html
        --video e2e/tests/reports/video
        --video-options singleFile=false,failedOnly=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.mp4
        -s takeOnFails=true,path=e2e/tests/reports/screenshots,fullPage=true,pathPattern='${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}'.png
        --page-load-timeout 90000
        --assertion-timeout 60000
        --proxy $CODE_PROXY_HOST:$CODE_PROXY_PORT
        --page-request-timeout 60000
        -q attemptLimit=2,successThreshold=1

and these tests run thru proxy.

I could not reproduce the problem with the settings on my side. You can try to find its cause on your own. Add the disablehttp2 argument to the Jobs section of your .yml GitLab CI configuration file. Then, try to reproduce the problem and share your results with us.

nothing has changed with that flag

Seems it is chromium related issue. I've tried to run tests in firefox with the same settings and it works fine.

I'm happy to hear that you've solved the problem. Could you please create a simple public project on GitLab where the problem is reproduced and share a project link so that we can research the problem and fix it?

Here it is: https://gitlab.com/AM1988/testacfe-ci-setup/-/tree/docker_testcafe_1.18.3 (branch -> docker_testcafe_1.18.3)
Example of failed pipeline: https://gitlab.com/AM1988/testacfe-ci-setup/-/jobs/2093946120
$ /opt/testcafe/docker/testcafe-docker.sh "chromium --start-maximized --incognito" -c 1 e2e/tests/*.test.ts --skip-js-errors --color --page-load-timeout 90000 --assertion-timeout 60000 --page-request-timeout 60000 -q attemptLimit=2,successThreshold=1
ERROR Cannot establish one or more browser connections.
1 of 1 browser connections have not been established:
- chromium --start-maximized --incognito
Hints:
- Increase the value of the "browserInitTimeout" option if it is too low (currently: 2 minutes for local browsers and 6 minutes for remote browsers). This option determines how long TestCafe waits for browsers to be ready.
- The error can also be caused by network issues or remote device failure. Make sure that your network connection is stable and you can reach the remote device.

We have also observed this issue quite often on latest testcafe docker image for chromium:headless For us the issue is seen intermittently i.e. not reproducible for every run, but a bunch of jobs fail over a period of time.

This solved the issue for us: https://testcafe.io/documentation/402838/guides/advanced-guides/use-testcafe-docker-image#troubleshooting

I've tried with "chromium --no-sandbox --disable-dev-shm-usage" but that does not help, still getting the same error.

I have this problem too, but unfortunately I can't share it，   --no-sandbox --disable-dev-shm-usage do not help，  forfox is ok，but not stabilization

Hello @AM1988, thank for the provided links:

Here it is: https://gitlab.com/AM1988/testacfe-ci-setup/-/tree/docker_testcafe_1.18.3 (branch -> docker_testcafe_1.18.3)
Example of failed pipeline: https://gitlab.com/AM1988/testacfe-ci-setup/-/jobs/2093946120

Unfortunately, I can't open the links. I think this is related to the permission level of the project. I am currently getting a "404 Page Not Found" page. Could you please give public permissions to the project?

@dositec my fault, fixed. Could you please check once again?

@AM1988
Thank you for the answer. Currently, I have access to your project, but I don't have access to your CI/CD; we need it to reproduce the problem (I have access to the pipelines but I don't have access to the "Run" button). Could you please give us access to your CI/CD? You can send the credentials to our email -<EMAIL_ADDRESS>We will keep this information private and will remove the credential when we resolve this problem.

@dositec
I've given you a 'Developer' role in that project. So you should be able to run the pipeline now.
I believe you can also simply fork the project and try it within your own account.
I will not share my creds )

@AM1988 Thank you for the clarification and help. We reproduced the behavior, but we don't think that it's a bug. Could you please to try using "chromium:headless" instead of "chromium" in your .yaml file to avoid the error message? We will correct our documentation to point out that the correct way is to use "chromium:headless" in the pipeline file.

yup,  chromium:headless does the job as I said in the https://github.com/DevExpress/testcafe/issues/6865#issuecomment-1038933460

The documentation has been updated. It may take a while for the website to reflect these changes.


Examples Fail to Build Outside of the Vulkano Project

Version of vulkano: 0.34.1
OS: Win10
GPU: 3080
GPU Driver: 551.52

Issue
Taking any example from 0.34.1 Vulcano into an isolated project will not compile because of missing dependencies. Specifically with RecordingCommandBuffer and CommandBufferBeginInfo. I tested triangle and basic-compute-shader, but I assume any example that uses these dependencies will fail.
Building and running the examples within the Vulkano project works correctly. The issue only happens when you try to use the same structs in another project using Vulkano as a dependency. Also, going back to version 0.33.0 of Vulkano the example code has no issues building and running.

RecordingCommandBuffer and CommandBufferBeginInfo are not part of Vulkano 0.34.1. They are only in the unstable version that has not been released yet. You need to use the examples from the last release.

Ah, ok thanks for the quick response! I will stick with the last release version.


List pages.  There is no quick way to reset the filter – can there be a button to reset the filter, so all list items show.

Reloading the page will reset the filters.  But there should be some sort of button as well.  This button would need javascript attached that populates all the fields in the form to their default value and (if the current on change doesn't pick this up already) trigger an on change event for one of the fields - this on change event should trigger the ajax call to get the new data.


Remove tests for scripts that do not exist anymore

There are a number of tests in testing/ that point to scripts that no longer exist:

test_sct_convert_binary_to_trilinear.py (should this be test_isct_convert_binary_to_trilinear?)
test_sct_documentation.py
test_sct_orientation.py
test_sct_register_graymatter.py

I presume these are no longer needed and can be removed (at least the last three, anyway)?

Hi, I would like to work in this one. Could you assign me this?

Hi @GSantos23 👋   Thank you for your willingness to help. Yes, you are more than welcome to work on this one.

Hi guys, before doing the pull request I want to confirm if the file test_sct_convert_binary_to_linear.py have to be removed.

@GSantos23 Yes, it can be removed. Also, there is a line in sct_testing that should be removed as well:
https://github.com/neuropoly/spinalcordtoolbox/blob/d94f602fe0b9466e656122f1bc554860002918ef/scripts/sct_testing.py#L410
Out of curiosity, are you participating in Hacktoberfest? If so, thank you for stopping by! :)

Hi @joshuacwnewton,, yes I am participating on Hacktoberfest.
I will do those changes as well.
Sorry for the late reply.

Sorry for the late reply.

No worries! We are all working asynchronously, so delays like that are normal. :)


masterPage.js is inside /src (should be in /src/pages)

Currently this extension works fine but it places masterPage.js inside of src folder but it should be inside pages folder instead of src.

Hello, @l0eix !
I have checked the code. I see the file has a path in the pages folder
https://github.com/shoonia/velo-filesystem/blob/886181da7f34f28b81010b9e9f93ee0a719ccdac/src/module/textModel.ts#L45-L47
but it saves in the src
https://github.com/shoonia/velo-filesystem/blob/886181da7f34f28b81010b9e9f93ee0a719ccdac/src/module/downloadFiles.ts#L45
You're right, It should be in the pages folder. I'll fix it.

Fixed in new v0.8.0


Add Levels/Rounds for CodeTrek Applicants

Parent Issue:- https://github.com/ColoredCow/portal/issues/2704
Related Issue
https://github.com/ColoredCow/portal/issues/2734
https://github.com/ColoredCow/portal/issues/2736
https://github.com/ColoredCow/portal/issues/2743
https://github.com/ColoredCow/portal/issues/2794
https://github.com/ColoredCow/portal/issues/2807
Is your feature request related to a problem? Please describe.
In ColoredCow, CodeTrek is a journey that most of the interns do. In it, they learn the basics of software development and hone their skills. Now, we want to track and capture this journey of all the interns in Portal. This will help us monitor each individual's progress and see where we can or they can do better.
For this, we have introduced Codetrek Module and added functionality to add, edit, and delete applicants' details in previous tasks.
Now we need to add the Levels/Rounds of the applicants and provide the functionality to streamline Evaluation Process.

Expected behavior

Action Items

[x] Read about Laravel Migration. Create a column Round  in the code_trek_applicants  table in the employee portal database.
[x] Add view and Evaluate button as shown in the image below.

[x] On clicking the view button it should be redirected to the applicant-edit page where all the data of the applicant will be shown.
[x] On clicking the Evaluate button it should be redirected to the applicant-evaluation page where data of the applicant will be shown in the image below.

[x] Read about accordion in Bootstrap.
[ ] Inside the applicant-evaluation page make functionality so that on click of Take action  applicants can be evaluated and their Rounds should be updated.

should i have to store feedback in code_trek_applicant details table or another table

There should be another table with the name codetrek_applicant_round_details
There you will add applicant_id, round_name, and other details corresponding to that round
for very new round of applicant a new entry will be created in this table. So it will have one-to-many realtionship


Way to filter GitHub Actions tests by result state

Description
It would be nice to be able to filter the GH Actions workflow results by the state. We have many tests in our workflows, so when GitHub says "144 successful, 2 skipped, 9 queued, and 1 failing checks" it takes quite a bit of scrolling to get to the failing test:

It could be nice to have a way to filter down the tests by their state, only showing the "failed" ones for example.
Screenshot
No response
Example URL
https://github.com/prisma/ecosystem-tests/pull/2695#partial-pull-merging

Related:

https://github.com/refined-github/refined-github/issues/3136
https://github.com/refined-github/refined-github/issues/4958

Sorting by state (failed first, then succeeded) might actually also be an interesting way that does not need interaction. (#3136 mentions sorting by workflow, which the checks are not for some reason 🤷 )

Duplicate of https://github.com/refined-github/refined-github/issues/5062


DungeonGenerator parametrization improvements

Hello
The current DungeonGenerator is a bit too random, would be cool to be able to choose:

If a dead end should be a room instead of just a dead end
Type of the first Room (for spawn)
Type of the last Room (for boss)
Default room ( for basic monster room)
Type of the room at the x position (for special room such as Secret/Treasure/Merchant etc)

If a dead end should be a room instead of just a dead end

You can choose to generate no dead ends. Actually, this is the default setting. If you leave deadEndRemovalIterations setting at maximum, all corridors will end with a room, effectively leaving no dead ends (if you don't spawn any 1-tile rooms in the first place). If you want some dead ends on the map, I'm afraid you'd have adjust the removal iteration setting or manually iterate over tiles, find dead ends and decide what to do.

Type of the first Room (for spawn)
Type of the last Room (for boss)
Default room ( for basic monster room)
Type of the room at the x position (for special room such as Secret/Treasure/Merchant etc)

There is no concept of "first" or "last" room in the generator. Room placement is pretty much random. Even if you lower the random connector chance and effectively generate a labyrinth, I'm afraid you'd have to select the initial and last room yourself.
Sounds like you want to carve room shapes yourself. Try implementing RoomType interface and set it with dungeonGenerator.addRoomType(new MyRoomCarver()) method. Pseudo-code carving implementation:
@Override
 public void carve(final Room room, final Grid grid, final float value) {
      if (isFirst(room)) {
            DefaultRoomType.ROUNDED.carve(room, grid, value);
      } else if (isSpecial(room)) {
            DefaultRoomType.CASTLE.carve(room, grid, value);
      } else {
            DefaultRoomType.SQUARE.carve(room, grid, value);
      }
}

Anyway, looking through the Noise4J code inspired me to give it some love and refactor some ugly stuff. Thanks.

Thanks for your info, i'll try that :)
I once tried to make something similar by myself but i don't have the source anymore to share the ideas i had, but it was something like that:

abstract class Room
{
    abstract int width;
    abstract int height;

    abstract void fill(TileMap map, int start_x, int start_y);
}

class StartRoom extends Room
{
    override int width = 52;
    override int height = 52;

    override void fill(TileMap map, int start_x, int start_y)
    {
        // some layout
    }
}

gen.placeRoom(startRoom)
times(15)
    gen.placeRoom(randomSizedRoom)

if(rng.change(0.1))
    gen.placeRoom(treasureRoom)

times(15)
    gen.placeRoom(randomSizedRoom)

gen.placeRoom(bossRoom)

But it was really bad because i had no idea how to generate walls / path etc..

RoomType mechanism works similarly to your abstract room hierarchy, although avoiding inheritance. The generator basically gives you a Room instance at some point - which is no more than a rectangle somewhere on the grid - and you choose to fill it the way you want. By checking the room's bounds and position, you can completely take control of the carving process and make it somewhat predictable. Corridors are generated later, so there will be no huge empty areas around the rooms if you carve something smaller than a simple square.


Method publishNewCrl in CRLRevocationDataProvider should have a throws declaration

There are a lot of thing that may go wrong. Let's not be silent about it.

Being fixed


[IBEX] Code Review: IBEX integration with galoy backend using USD wallet to receive lightning via LN Invoice - Bounty #3

This task is to do a comprehensive code review for the changes made to the flash backend that replace the galoy USD (stablesats) wallet with the IBEX custodial USD wallet when generating a lightning invoice using the LnUsdInvoiceCreate mutation, and suggest a solution for updating the flash backend with the updated IBEX wallet balance once the invoice has been paid and the IBEX API returns the webhook.
The branch with these changes can be found here
Submitted PR can be found here
For testing the frontend you can connect the staging environment to http://api-development.flashapp.me:4002/graphql
For testing the IBEX API you can connect to http://api-development.flashapp.me:8760/api/v1/
BOUNTY available ⚡⚡⚡

Bounty posted!


wallet immediately close after walletpassphrase via console Win 8.1

I dwld the newest qt wallet <IP_ADDRESS> and try to find out my private key via console with dumpprivkey
wallet is encrypted and currently locked on my win 8.1

walletpassphrase  60
then the wallet immediately close

FYI the balance is 0, and before I withdrawl my coins from cryptopia I wish to have this informations

Test:

walletpassphrase 1234 60
dumpprivkey tCG84kzKsWNh4tJFpSvVFtn67FZbWAiATy
Works with 2.0.5 and balance > 0 and balance == 0.

@igilepic Please retest with 2.0.5.

@shbli walletpassphrase works when in debugger, seems like a NDEBUG related problem you had before. Can you check this?
Maybe related to #27

@teknex Looking into this

@teknex @igilepic test out the code I just committed on develop branch and let me know!
I'm closing the issue now but open it again if the issue arise again.
Not related to #27

Sorry, but Im not a programmer, so what exactly should I do to test it?

The rpc server is needed to lock the wallet after the specified time
With the current fix, when you don't have server active and you return the error message, the wallet is already unlocked

@igilepic The function does work already. dumpprivkey needs the wallet to be unlocked. You can do this by

Unlock the wallet via UI. Wallet Encryption > (Un)lock Wallet  (take care to uncheck the 'for staking only' box
Start the wallet with the -server option to activate the RPC server. (RPC server is internally needed to lock the wallet after the specified time)


Running single tests with Gradle command line does not work

Running just a single test does not work when running from the command line. To reproduce, use kotlintest's own current master (65cd9d03b52e9936904a2d55d5087a0bcc4c86fd) and run:
./gradlew test --tests io.kotlintest.extensions.system.SystemExitTest

It will run all tests instead of just io.kotlintest.extensions.system.SystemExitTest.

Gradle 4.7 ?

No, you are using Gradle 4.6 in kotlintest 😉 See https://github.com/kotlintest/kotlintest/blob/65cd9d03b52e9936904a2d55d5087a0bcc4c86fd/gradle/wrapper/gradle-wrapper.properties.

lol I thought I had upgraded it.

It looks like --tests is not passed through to the JUnit 5 test runner, but only used by Gradle's junit 4 scanner.

I've opened an issue at gradle.
https://github.com/gradle/gradle/issues/5678

I've made some progress with the workaround I talked about in the gradle ticket. On master now, we can do --tests com.test.Class but it will fail if there is no match. It will also fail the build if there's a multi modules, as it will match in one module and not in another.
I think for the latter, we could either, if no classes match the pattern then we test all classes. This will fix the multi module issue, but will mean if you do a typo then you'll run everything. Thoughts @sschuberth

On master now, we can do --tests com.test.Class but it will fail if there is no match.

I like that it fails it that case. While vanilla Gradle's runs all tests in that case, I do consider that to be a bug.

It will also fail the build if there's a multi modules, as it will match in one module and not in another.

But what if there's only one unique match throughout all modules? Would it still fail?

Yes it would because it treats each module in isolation. That's the
annoying part.
On Mon, 11 Jun 2018, 09:34 Sebastian Schuberth<EMAIL_ADDRESS>wrote:

On master now, we can do --tests com.test.Class but it will fail if there
is no match.
I like that it fails it that case. While vanilla Gradle's runs all tests
in that case, I do consider that to be a bug
https://github.com/gradle/gradle/issues/5688.
It will also fail the build if there's a multi modules, as it will match
in one module and not in another.
But what if there's only one unique match throughout all modules? Would it
still fail?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/356#issuecomment-396165089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGvn2n7qOUlk_e1fCmeyyTa9cdSAkks5t7iuMgaJpZM4UdQcC
.

You can of course use the :project-name:test syntax to narrow down to the
submodule. Then it will work.
On Mon, 11 Jun 2018, 09:41 Stephen Samuel (Sam<EMAIL_ADDRESS>wrote:

Yes it would because it treats each module in isolation. That's the
annoying part.
On Mon, 11 Jun 2018, 09:34 Sebastian Schuberth<EMAIL_ADDRESS>wrote:

On master now, we can do --tests com.test.Class but it will fail if there
is no match.
I like that it fails it that case. While vanilla Gradle's runs all tests
in that case, I do consider that to be a bug
https://github.com/gradle/gradle/issues/5688.
It will also fail the build if there's a multi modules, as it will match
in one module and not in another.
But what if there's only one unique match throughout all modules? Would
it still fail?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/356#issuecomment-396165089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGvn2n7qOUlk_e1fCmeyyTa9cdSAkks5t7iuMgaJpZM4UdQcC
.

You can of course use the :project-name:test syntax to narrow down to the submodule.

Ah, right. I'd say that's good enough then.

You can try in 3.1.7 and hopefully tell me it's ok :)

Confirmed to be working, thanks!


Service Manager client

Description
Add Service Manager client built from available credentials stored in SAP BTP service operator secrets. Client is required for operations on Service Offerings, Service Instances and Service Bindings.
Related issue(s)

See #442

/hold

/unhold

/test pull-btp-manager-build


Not compiled in latest version(1.1.8) of MaLiang

Hi, dear.
I tried to build the Example in MaLiang downloads with pod install with cocoa pods.
Here is the Podfile where I did new line, pod 'MaLiang' for Maliang.
use_frameworks!
target 'MaLiang_Example' do
pod 'Comet'
pod 'MaLiang'
end
But, many erros arise when build.
For example,
MaLiang-1.1.8/Example/Pods/Comet/Comet/Extensions/UIAlertController+Comet.swift:13:64: 'Style' is not a member type of 'UIAlertAction'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Extensions/UIBarButtonItem+Closure.swift:17:69: 'Style' is not a member type of 'UIBarButtonItem'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:92:91: Type 'UIResponder' has no member 'keyboardWillShowNotification'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:94:90: Type 'UIResponder' has no member 'keyboardDidShowNotification'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:95:98: Type 'UIResponder' has no member 'keyboardWillChangeFrameNotification'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:149:42: Type 'UIResponder' has no member 'keyboardAnimationDurationUserInfoKey'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Extensions/UIVIew+Comet.swift:65:98: 'OptionsKey' is not a member type of 'UINib'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:150:26: Type 'UIView' has no member 'AnimationOptions'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:167:34: Type 'UIResponder' has no member 'keyboardFrameEndUserInfoKey'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Classes/KeyboardManager.swift:180:22: Type 'UIView' has no member 'AnimationOptions'
MaLiang-1.1.8/Example/Pods/Comet/Comet/Extensions/UINavigationBar+Comet.swift:27:59: Type 'NSAttributedString' has no member 'Key'
...
MaLiang-fgkbrzhxgpualzdixhtqfoxfrjaj/Build/Products/Debug-iphoneos/Comet/Comet.framework/Modules/module.modulemap:9:12: Header 'Comet-Swift.h' not found
MaLiang-1.1.8/Example/MaLiang/ViewController.swift:10:8: Could not build Objective-C module 'Comet'
Command Ditto failed with a nonzero exit code
Would you help me, please ?
Thanks.

Please update the swift version of your project to swift 4.2

Fixed as your guidance.
Thank you.
Sent from Outlookhttp://aka.ms/weboutlook

From: Harley<EMAIL_ADDRESS>Sent: Tuesday, October 30, 2018 7:10 AM
To: Harley-xk/MaLiang
Cc: superITdev; Author
Subject: Re: [Harley-xk/MaLiang] Not compiled in latest version(1.1.8) of MaLiang (#17)
Please update the swift version of your project to swift 4.2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Harley-xk/MaLiang/issues/17#issuecomment-434126004, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AmaS9whC6QUt4zEnw_d5nCxYyuguYgv8ks5up5jngaJpZM4X_dkZ.


Fix sign of the rotation angle

Actually no this doesn't work...

The original sign was right, what do you see?
@TheoLaudatQM

Yeah I redid all the calculations and it appears that it is actually the way the integration weights are rotated in the config that is wrong. This is why I closed this PR, I opened it too quickly....


Redirect URL

Hello FloFlal,
First of all thank you for bringing this project.
I can't figure out what to do with the redirect url field.
If I do understand right, I should have a server listening to some port to redirect the token there.
But I cannot figure out how to bring this server to life !
Maybe I'm completely wrong there...
Could you please help and advise ?
Thank you

forget my message I have found how to do it.
I used http://localnoderedaddress:localport/ewelink-auth/auth/callback
It worked :)

Hello !
Thank you for your interest for my nodes.
In the 1st release of it, I forgot to put the basic documentation I prepared.
It is now the case and as you already figgured out, the library is providing the listening redirect URL.
Good if it worked for you.


Strange warnings: Cannot find source file

Hey, thanks for cool lib. It implements nice separation of concerns approach!
I'm using proppy + proppy-preact. and I received strange warnings when I'm trying to import proppy's utils into my project. Everything works fine, but these warnings trash my console and I want to remove them.
Here is an example:
(Emitted value instead of an instance of Error) Cannot find source file '../src/compose.ts': Error: Can't resolve '../src/compose.ts' in '/Users/user/project/node_modules/proppy/lib'
 @ ./node_modules/proppy/lib/index.js 3:16-36
 @ ./src/components/pages/calculator/Calculator.js
 @ ./src/components/pages/index.js
 @ ./src/components/app.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./index.js```

Thanks for the positive feedback, @Vargentum! 💖
Could you kindly share rest of your code too? Like how you are importing it. That would really help me understand.
An example on CodeSandbox would be helpful too.
For example, the playground with proppy + proppy-react is here: https://codesandbox.io/s/github/fahad19/proppy/tree/master/examples/react-playground

I am assuming you are using TypeScript.
And it could be because of this line in .npmignore, where we do not push the src directory to npm: https://github.com/fahad19/proppy/blob/master/packages/proppy/.npmignore#L3
If you want to send a PR that removes the src line from .npmignore of all packages, that may solve it.

Sure. Here are the imports:
import { attach } from 'proppy-preact'```

I'm not using TypeScript.
I also run build to exclude issues with webpack-dev-server. Warnings still remain, so it's not a source.
Could it be related with webpack resolving modules setup? I have following config:
```...
resolve: {
         extensions: ['.jsx', '.js', '.json', '.styl'],
	modules: [
		path.resolve(__dirname, "src/lib"),
		path.resolve(__dirname, "node_modules"),
		'node_modules'
	],
	alias: {
		components: path.resolve(__dirname, "src/components"),    // used for tests
		style: path.resolve(__dirname, "src/style"),
		'react': 'preact-compat',
		'react-dom': 'preact-compat'
	}
},
...```

I have just published v1.2.2 which has the src directory published to npm too. Could you please try again? It should solve your warnings issue.

Yes it helps.
Thanks.


Add support to use an existing Redis client connection

I'm connecting to a remote Redis server on another machine (e.g. not using the default localhost IP/port) and using the connect-redis plugin as-is causes things to fail since it can't connect.  This change adds the ability to supply an existing client connection.

oh, i just saw your pull request. Maybe this one solves your problem: https://github.com/visionmedia/connect-redis/pull/14


Jest is broken

Version
29
Steps to reproduce
Jest is giving me:
 FAIL  src/handlers/restapi/__tests__/redirect.test.ts
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/alper/Code/backend/move-token-registry/spaces/erp/node_modules/.pnpm/axios@1.7.2/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (../../node_modules/.pnpm/jest-runtime@27.5.1/node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (../../node_modules/.pnpm/intuit-oauth@4.1.2/node_modules/intuit-oauth/src/OAuthClient.js:30:15)

Expected behavior
I expect it to run.
Actual behavior
It fails.
Additional context
No response
Environment
System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M2 Pro
  Binaries:
    Node: 18.6.0 - ~/.nvm/versions/node/v18.6.0/bin/node
    Yarn: 1.22.21 - ~/Library/pnpm/yarn
    npm: 8.13.2 - ~/.nvm/versions/node/v18.6.0/bin/npm
    pnpm: 8.8.0 - ~/Library/pnpm/pnpm
    bun: 1.1.18 - /opt/homebrew/bin/bun

Did you try any of the suggestions in the error message? Regardless, this is without a reproduction

We worked our way around it in some way but maybe it would be better if typescript support was just not a part of Jest? It obviously does not really work.