XSym symbolic links cannot be used in PHP on Docker for Windows












4















When using PHP inside a Docker container on Windows (e.g. using DDEV), symbolic links that are created inside the container (e.g. by composer) do not seem to work correctly with PHP's file streams.



Scenario



Imagine the following PHP code



<?php

mkdir('demo-base-directory');

symlink('demo-base-directory', 'demo-symbolic-link');

var_dump(glob('demo-*', GLOB_ONLYDIR));


If executed inside the container, it outputs only demo-base-directory, however demo-symbolic-link is missing (the very same example works as expected on Linux/Unix systems inside Docker containers)



array(1) {

  [0]=>

  string(19) "demo-base-directory"

}


When viewing the symbolic link in the host system (e.g. using cat demo-symbolic-link in Windows PowerShell) it shows



XSym

0019

0df68e8650ddca993c28277a5cfa3dcd

demo-base-directory


There have been other reports to Docker for Windows about symlink emulation - I could not reproduce this behavior for files using fgets or file_get_contents but for the mentioned glob invocation, see




  • https://github.com/docker/for-win/issues/137

  • https://github.com/drud/ddev/issues/1283


Shared volumes are mounted in a Linux-based Docker container on a Windows host system as Samba/CIFS mount like this:




//10.0.75.1/C on /var/www/html type cifs
(rw,relatime,vers=3.02,sec=ntlmsspi,cache=strict,username=olly,domain=OLIVERHADERB9D8,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.75.1,file_mode=0755,dir_mode=0777,iocharset=utf8,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)




Mount option mfsymlinks refers to Minshall+French symlinks



Workaround



Instead of creating symbolic links inside the container, creating them outside (directly in Windows) solves the problem.



Using plain mklink in cmd.exe



del demo-symbolic-link

mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


Using plain mklink via cmd in PowerShell



del demo-symbolic-link

cmd /c mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


side note: New-Item -ItemType SymbolicLink could not be resolved using glob(..., GLOB_ONLYDIR in PHP - using mklink /d here as well



Using Git-Bash for Windows



I had to execute the following while executing Git-Bash as administrator. Setting the environment variable with export is important here - see Enable native NTFS symbolic links for Cygwin



rm demo-symbolic-link

export MSYS=winsymlinks:nativestrict

ln -s demo-base-directory/ demo-symbolic-link


Helper tools



I've created helper tool examples that search for Samba XSym pointers in a particular directory (TYPO3 related, public/typo3conf/ext/) and "upgrade" the XSym pointers to proper symlinks - probably admin privileges are required when executing those scripts:




  • BAT helper to be used in cmd.exe

  • BASH helper to be used in Git-Bash


Results



Executing the PHP example from above again now outputs both expected items



array(2) {

  [0]=>

  string(19) "demo-base-directory"

  [1]=>

  string(18) "demo-symbolic-link"

}


Question



Working inside a Docker container and having to adjust symbolic links manually on the host system is really just a workaround - not a solution. At which level could this be enhanced and optimized in order to create proper symbolic links using the Docker container only?



It seems this could be resolved at different layers:





  • PHP's glob invocation (especially for flaky GLOB_ONLYDIR flag)


  • glibc's glob implementation (especially for Minshall+French symlinks XSym)

  • Docker not using Samba/CIFS for volume sharing



Updates




  • switched from mklink /j (junction) to mklink /d (symlinked directory) since removing the linked junction removed it's origin as well

  • PowerShell's symlink cmdlet New-Item -ItemType SymbolicLink (instead of previous New-Item -ItemType Junction) then again could not be resolved using glob(..., GLOB_ONLYDIR in PHP - as a result, using cmd /c mklink /d here

  • added Samba/CIFS mount information






php docker windows-10 samba ddev







share|improve this question

























  • Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

    – rfay
    Nov 20 '18 at 17:18
















4















When using PHP inside a Docker container on Windows (e.g. using DDEV), symbolic links that are created inside the container (e.g. by composer) do not seem to work correctly with PHP's file streams.



Scenario



Imagine the following PHP code



<?php

mkdir('demo-base-directory');

symlink('demo-base-directory', 'demo-symbolic-link');

var_dump(glob('demo-*', GLOB_ONLYDIR));


If executed inside the container, it outputs only demo-base-directory, however demo-symbolic-link is missing (the very same example works as expected on Linux/Unix systems inside Docker containers)



array(1) {

  [0]=>

  string(19) "demo-base-directory"

}


When viewing the symbolic link in the host system (e.g. using cat demo-symbolic-link in Windows PowerShell) it shows



XSym

0019

0df68e8650ddca993c28277a5cfa3dcd

demo-base-directory


There have been other reports to Docker for Windows about symlink emulation - I could not reproduce this behavior for files using fgets or file_get_contents but for the mentioned glob invocation, see




  • https://github.com/docker/for-win/issues/137

  • https://github.com/drud/ddev/issues/1283


Shared volumes are mounted in a Linux-based Docker container on a Windows host system as Samba/CIFS mount like this:




//10.0.75.1/C on /var/www/html type cifs
(rw,relatime,vers=3.02,sec=ntlmsspi,cache=strict,username=olly,domain=OLIVERHADERB9D8,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.75.1,file_mode=0755,dir_mode=0777,iocharset=utf8,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)




Mount option mfsymlinks refers to Minshall+French symlinks



Workaround



Instead of creating symbolic links inside the container, creating them outside (directly in Windows) solves the problem.



Using plain mklink in cmd.exe



del demo-symbolic-link

mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


Using plain mklink via cmd in PowerShell



del demo-symbolic-link

cmd /c mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


side note: New-Item -ItemType SymbolicLink could not be resolved using glob(..., GLOB_ONLYDIR in PHP - using mklink /d here as well



Using Git-Bash for Windows



I had to execute the following while executing Git-Bash as administrator. Setting the environment variable with export is important here - see Enable native NTFS symbolic links for Cygwin



rm demo-symbolic-link

export MSYS=winsymlinks:nativestrict

ln -s demo-base-directory/ demo-symbolic-link


Helper tools



I've created helper tool examples that search for Samba XSym pointers in a particular directory (TYPO3 related, public/typo3conf/ext/) and "upgrade" the XSym pointers to proper symlinks - probably admin privileges are required when executing those scripts:




  • BAT helper to be used in cmd.exe

  • BASH helper to be used in Git-Bash


Results



Executing the PHP example from above again now outputs both expected items



array(2) {

  [0]=>

  string(19) "demo-base-directory"

  [1]=>

  string(18) "demo-symbolic-link"

}


Question



Working inside a Docker container and having to adjust symbolic links manually on the host system is really just a workaround - not a solution. At which level could this be enhanced and optimized in order to create proper symbolic links using the Docker container only?



It seems this could be resolved at different layers:





  • PHP's glob invocation (especially for flaky GLOB_ONLYDIR flag)


  • glibc's glob implementation (especially for Minshall+French symlinks XSym)

  • Docker not using Samba/CIFS for volume sharing



Updates




  • switched from mklink /j (junction) to mklink /d (symlinked directory) since removing the linked junction removed it's origin as well

  • PowerShell's symlink cmdlet New-Item -ItemType SymbolicLink (instead of previous New-Item -ItemType Junction) then again could not be resolved using glob(..., GLOB_ONLYDIR in PHP - as a result, using cmd /c mklink /d here

  • added Samba/CIFS mount information






php docker windows-10 samba ddev







share|improve this question

























  • Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

    – rfay
    Nov 20 '18 at 17:18














4












4








4








When using PHP inside a Docker container on Windows (e.g. using DDEV), symbolic links that are created inside the container (e.g. by composer) do not seem to work correctly with PHP's file streams.



Scenario



Imagine the following PHP code



<?php

mkdir('demo-base-directory');

symlink('demo-base-directory', 'demo-symbolic-link');

var_dump(glob('demo-*', GLOB_ONLYDIR));


If executed inside the container, it outputs only demo-base-directory, however demo-symbolic-link is missing (the very same example works as expected on Linux/Unix systems inside Docker containers)



array(1) {

  [0]=>

  string(19) "demo-base-directory"

}


When viewing the symbolic link in the host system (e.g. using cat demo-symbolic-link in Windows PowerShell) it shows



XSym

0019

0df68e8650ddca993c28277a5cfa3dcd

demo-base-directory


There have been other reports to Docker for Windows about symlink emulation - I could not reproduce this behavior for files using fgets or file_get_contents but for the mentioned glob invocation, see




  • https://github.com/docker/for-win/issues/137

  • https://github.com/drud/ddev/issues/1283


Shared volumes are mounted in a Linux-based Docker container on a Windows host system as Samba/CIFS mount like this:




//10.0.75.1/C on /var/www/html type cifs
(rw,relatime,vers=3.02,sec=ntlmsspi,cache=strict,username=olly,domain=OLIVERHADERB9D8,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.75.1,file_mode=0755,dir_mode=0777,iocharset=utf8,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)




Mount option mfsymlinks refers to Minshall+French symlinks



Workaround



Instead of creating symbolic links inside the container, creating them outside (directly in Windows) solves the problem.



Using plain mklink in cmd.exe



del demo-symbolic-link

mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


Using plain mklink via cmd in PowerShell



del demo-symbolic-link

cmd /c mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


side note: New-Item -ItemType SymbolicLink could not be resolved using glob(..., GLOB_ONLYDIR in PHP - using mklink /d here as well



Using Git-Bash for Windows



I had to execute the following while executing Git-Bash as administrator. Setting the environment variable with export is important here - see Enable native NTFS symbolic links for Cygwin



rm demo-symbolic-link

export MSYS=winsymlinks:nativestrict

ln -s demo-base-directory/ demo-symbolic-link


Helper tools



I've created helper tool examples that search for Samba XSym pointers in a particular directory (TYPO3 related, public/typo3conf/ext/) and "upgrade" the XSym pointers to proper symlinks - probably admin privileges are required when executing those scripts:




  • BAT helper to be used in cmd.exe

  • BASH helper to be used in Git-Bash


Results



Executing the PHP example from above again now outputs both expected items



array(2) {

  [0]=>

  string(19) "demo-base-directory"

  [1]=>

  string(18) "demo-symbolic-link"

}


Question



Working inside a Docker container and having to adjust symbolic links manually on the host system is really just a workaround - not a solution. At which level could this be enhanced and optimized in order to create proper symbolic links using the Docker container only?



It seems this could be resolved at different layers:





  • PHP's glob invocation (especially for flaky GLOB_ONLYDIR flag)


  • glibc's glob implementation (especially for Minshall+French symlinks XSym)

  • Docker not using Samba/CIFS for volume sharing



Updates




  • switched from mklink /j (junction) to mklink /d (symlinked directory) since removing the linked junction removed it's origin as well

  • PowerShell's symlink cmdlet New-Item -ItemType SymbolicLink (instead of previous New-Item -ItemType Junction) then again could not be resolved using glob(..., GLOB_ONLYDIR in PHP - as a result, using cmd /c mklink /d here

  • added Samba/CIFS mount information






php docker windows-10 samba ddev







share|improve this question
















When using PHP inside a Docker container on Windows (e.g. using DDEV), symbolic links that are created inside the container (e.g. by composer) do not seem to work correctly with PHP's file streams.



Scenario



Imagine the following PHP code



<?php

mkdir('demo-base-directory');

symlink('demo-base-directory', 'demo-symbolic-link');

var_dump(glob('demo-*', GLOB_ONLYDIR));


If executed inside the container, it outputs only demo-base-directory, however demo-symbolic-link is missing (the very same example works as expected on Linux/Unix systems inside Docker containers)



array(1) {

  [0]=>

  string(19) "demo-base-directory"

}


When viewing the symbolic link in the host system (e.g. using cat demo-symbolic-link in Windows PowerShell) it shows



XSym

0019

0df68e8650ddca993c28277a5cfa3dcd

demo-base-directory


There have been other reports to Docker for Windows about symlink emulation - I could not reproduce this behavior for files using fgets or file_get_contents but for the mentioned glob invocation, see




  • https://github.com/docker/for-win/issues/137

  • https://github.com/drud/ddev/issues/1283


Shared volumes are mounted in a Linux-based Docker container on a Windows host system as Samba/CIFS mount like this:




//10.0.75.1/C on /var/www/html type cifs
(rw,relatime,vers=3.02,sec=ntlmsspi,cache=strict,username=olly,domain=OLIVERHADERB9D8,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.75.1,file_mode=0755,dir_mode=0777,iocharset=utf8,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)




Mount option mfsymlinks refers to Minshall+French symlinks



Workaround



Instead of creating symbolic links inside the container, creating them outside (directly in Windows) solves the problem.



Using plain mklink in cmd.exe



del demo-symbolic-link

mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


Using plain mklink via cmd in PowerShell



del demo-symbolic-link

cmd /c mklink /d demo-symbolic-link demo-base-directory


output



symbolic link created for demo-symbolic-link <<===>> demo-base-directory


side note: New-Item -ItemType SymbolicLink could not be resolved using glob(..., GLOB_ONLYDIR in PHP - using mklink /d here as well



Using Git-Bash for Windows



I had to execute the following while executing Git-Bash as administrator. Setting the environment variable with export is important here - see Enable native NTFS symbolic links for Cygwin



rm demo-symbolic-link

export MSYS=winsymlinks:nativestrict

ln -s demo-base-directory/ demo-symbolic-link


Helper tools



I've created helper tool examples that search for Samba XSym pointers in a particular directory (TYPO3 related, public/typo3conf/ext/) and "upgrade" the XSym pointers to proper symlinks - probably admin privileges are required when executing those scripts:




  • BAT helper to be used in cmd.exe

  • BASH helper to be used in Git-Bash


Results



Executing the PHP example from above again now outputs both expected items



array(2) {

  [0]=>

  string(19) "demo-base-directory"

  [1]=>

  string(18) "demo-symbolic-link"

}


Question



Working inside a Docker container and having to adjust symbolic links manually on the host system is really just a workaround - not a solution. At which level could this be enhanced and optimized in order to create proper symbolic links using the Docker container only?



It seems this could be resolved at different layers:





  • PHP's glob invocation (especially for flaky GLOB_ONLYDIR flag)


  • glibc's glob implementation (especially for Minshall+French symlinks XSym)

  • Docker not using Samba/CIFS for volume sharing



Updates




  • switched from mklink /j (junction) to mklink /d (symlinked directory) since removing the linked junction removed it's origin as well

  • PowerShell's symlink cmdlet New-Item -ItemType SymbolicLink (instead of previous New-Item -ItemType Junction) then again could not be resolved using glob(..., GLOB_ONLYDIR in PHP - as a result, using cmd /c mklink /d here

  • added Samba/CIFS mount information






php docker windows-10 samba ddev




php docker windows-10 samba ddev






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 15:32







Oliver Hader

















asked Nov 20 '18 at 15:41









Oliver HaderOliver Hader

1,815829




1,815829













  • Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

    – rfay
    Nov 20 '18 at 17:18



















  • Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

    – rfay
    Nov 20 '18 at 17:18

















Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

– rfay
Nov 20 '18 at 17:18





Thanks for the great work on this here and on github.com/drud/ddev/issues/1283 - I'm confident we're going to get this sorted out and get predictable behavior for Windows people.

– rfay
Nov 20 '18 at 17:18












1 Answer
1






active

oldest

votes


















1














Starting with ddev v1.5.0, the ddev composer command on Windows attempts to convert XSym symlinks to legitimate Windows symlinks. This feature only works if you have enabled "Developer mode" on Windows. See Windows OS and ddev composer in docs.






share|improve this answer
























  • Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

    – Oliver Hader
    Jan 9 at 18:06













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53396559%2fxsym-symbolic-links-cannot-be-used-in-php-on-docker-for-windows%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Starting with ddev v1.5.0, the ddev composer command on Windows attempts to convert XSym symlinks to legitimate Windows symlinks. This feature only works if you have enabled "Developer mode" on Windows. See Windows OS and ddev composer in docs.






share|improve this answer
























  • Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

    – Oliver Hader
    Jan 9 at 18:06


















1














Starting with ddev v1.5.0, the ddev composer command on Windows attempts to convert XSym symlinks to legitimate Windows symlinks. This feature only works if you have enabled "Developer mode" on Windows. See Windows OS and ddev composer in docs.






share|improve this answer
























  • Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

    – Oliver Hader
    Jan 9 at 18:06
















1












1








1







Starting with ddev v1.5.0, the ddev composer command on Windows attempts to convert XSym symlinks to legitimate Windows symlinks. This feature only works if you have enabled "Developer mode" on Windows. See Windows OS and ddev composer in docs.






share|improve this answer













Starting with ddev v1.5.0, the ddev composer command on Windows attempts to convert XSym symlinks to legitimate Windows symlinks. This feature only works if you have enabled "Developer mode" on Windows. See Windows OS and ddev composer in docs.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 8 at 16:27









rfayrfay

1,4251015




1,4251015













  • Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

    – Oliver Hader
    Jan 9 at 18:06





















  • Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

    – Oliver Hader
    Jan 9 at 18:06



















Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

– Oliver Hader
Jan 9 at 18:06







Thanks for integrating this solution into DDEV! Basically the problem is located in PHP and some inconsistencies there (e.g. using glob('*', GLOB_ONLYDIR)). Great you provided a solution for that! :+1:

– Oliver Hader
Jan 9 at 18:06




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53396559%2fxsym-symbolic-links-cannot-be-used-in-php-on-docker-for-windows%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I have successfully enabled authorization on MongoDB and I have created an account on the admin database and then I created an account for my database called test. The following connection string to connect to my test database works successfully: mongo --host 192.168.17.52 --port 27017 -u user1 -p password --authenticationDatabase test Only problem I have now is, I cannot execute commands such as: show dbs. I get the following error when I try to do so: "errmsg" : "not authorized on admin to execute command { listDatabases: 1.0, lsid: { id: UUID("a1d5bc0d-bc58-485e-b232-270758a89455") }, $db: "admin...
Read more

Npm cannot find a required file even through it is in the searched directory

Image
up vote 0 down vote favorite I got that error: users-Air:pdfuploader user$ npm run start client@0.1.0 start /Users/user/Documents/pdfuploader react-scripts start Could not find a required file. Name: index.html Searched in: /Users/user/Documents/pdfuploader/public npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! client@0.1.0 start: `react-scripts start` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the client@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/user/.npm/_logs/2018-11-19T10_19_14_555Z-debug.log users-Air:pdfuploader user$ And the file is in /Users/user/Documents/pdfuploader/public as you can see in my github repository: https://github.c...
Read more

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

Image
1 I tried to upgrade a yummy sandwich made of two test slices (@JsonTest and @JdbcTest in my case, crunchy test code in between) adding spring boot 2.1 flavour to it. But it seems it was not much of a success. I cannot annotate my tests with many @...Test since they are now each bringing their own XxxTestContextBootstrapper. It used to work when they all used same SpringBootTestContextBootstrapper. @RunWith(SpringRunner.class) @JdbcTest @JsonTest public class Test { @Test public void test() { System.out.printn("Hello, World !"); } } The error I get from BootstrapUtils is illegalStateException : Configuration error: found multiple declarations of @BootstrapWith for test class I understand I might be doing something wrong here but is there an easy way I could load both Json and Jdbc contex...
Read more