profile
viewpoint
Brian Clozel bclozel VMWare Lyon, France http://spring.io/team/bclozel Spring Framework and Spring Boot committer @spring-projects

bclozel/http2-experiments 36

Companion repo for the "HTTP/2 for the web developer" talk

bclozel/initializr-stats 15

Companion apps for the Spring Boot 2.0 Web Apps talk

bclozel/gulp-bower-src 14

Gulp-src bower components files

bclozel/gulp-cram 7

Gulp plugin - assemble resources using cujoJS cram

bclozel/bootjug 2

Intro to Spring Boot

bclozel/cfp-example 1

Sample app for the "10 ways to get super-productive with Spring Boot" talk

push eventspring-projects/spring-framework

Brian Clozel

commit sha e02d3f32b4a17effd3bf56006feb476405f4c4d5

Requalify tests as LONG_RUNNING Prior to this commit, some tests would belong to the PERFORMANCE `TestGroup`, while they were not testing for performance but rather performing functional tests that involve long running operations or timeouts. This commit moves those tests to the LONG_RUNNING `TestGroup`. See gh-24830

view details

Brian Clozel

commit sha 61d893257ed02ed041ea1bc03e9f1ab3ec163015

Rewrite "performance" test to JMH benchmarks This commit rewrites the remaining "fastEnough" performance tests into proper JMH benchmarks. See gh-24830

view details

Brian Clozel

commit sha e33e7d7681dc73560071bca4e9e62208cb9a1f27

Remove TestGroup.PERFORMANCE Now that there's a new JMH infrastructure for benchmarks and that performance tests have been rewritten to use it, we should remove the `PERFORMANCE` `TestGroup` to avoid introducing such tests in the future. Closes gh-24830

view details

push time in 5 hours

issue closedspring-projects/spring-framework

Revisit "fast enough" performance tests

Overview

The Spring Framework test suite contains numerous tests that are assigned to the PERFORMANCE CI build, and many of these tests have names along the lines of "ensure that XYZ is fast enough".

When these tests were originally written, they were feasible when executed on an average developer's workstation; however, over time these tests have proven to be flaky when executed on the CI server with various load levels for the various CI agents.

We are opening this issue in order to reassess whether such "performance" tests make sense in the current Spring Framework build.

Candidates

  • [ ] org.springframework.aop.framework.IntroductionBenchmarkTests

Deliverables

  • [x] Introduce a JMH benchmark infrastructure in the build
  • [ ] Search for test methods and test classes that are annotated with @EnabledForTestGroups(PERFORMANCE) (or @EnabledForTestGroups(TestGroup.PERFORMANCE)) or that contain "FastEnough" in their titles and determine if the tests should be deleted or modified to make them more robust.
  • [ ] Delete or modify each such test method or test class.

closed time in 5 hours

sbrannen

issue closedspring-projects/spring-boot

Fail to map GET query params in pojo

<!-- !!! For Security Vulnerabilities, please go to https://pivotal.io/security !!! --> Affects: 2.4.0-SNAPSHOT Affects: Spring boot 2.3.4.RELEASE


Same behavior with kotlin version 1.3.72 and 1.4.10 Tested with java 8


I try to map a GET request into a pojo class in kotlin. The method param resolver fail to map properly the query params.

I used to have no problem to do this mapping in Java; I am not sure anymore but I think it was working before for Kotlin with Set/List/etc. Now it does not work anymore.

I don't think I have to implement my own HandlerMethodArgumentResolver for all my custom criterias, I use only basic fields, and java works but not kotlin.

I know about StringToCollectionConverter, DelimitedStringToCollectionConverter and etc but it does not seem to be working with Kotlin Data class (or normal class)


Do a get with: localhost:8080/test/param/test-1?projectIdIn2=1,2,3&projectIdIn3=1,2,4&projectIdIn4=1,2,5&projectIdIn5=1,2,6&projectIdIn6=1,2,7&projectIdIn8=1,2,9&projectIdIn1=1&projectIdIn1=3

Fail with 2020-09-25 15:36:19.865 WARN 10780 --- [nio-8080-exec-2] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.web.method.annotation.ModelAttributeMethodProcessor$1: org.springframework.validation.BeanPropertyBindingResult: 2 errors Field error in object 'simpleCriteria' on field 'projectIdIn3': rejected value [1,2,4]; codes [typeMismatch.simpleCriteria.projectIdIn3,typeMismatch.projectIdIn3,typeMismatch.java.util.Set,typeMismatch]; arguments [org.springframework.context.support.DefaultMessageSourceResolvable: codes [simpleCriteria.projectIdIn3,projectIdIn3]; arguments []; default message [projectIdIn3]]; default message [Failed to convert value of type 'java.lang.String[]' to required type 'java.util.Set'; nested exception is java.lang.NumberFormatException: For input string: "1,2,4"] Field error in object 'simpleCriteria' on field 'projectIdIn5': rejected value [1,2,6]; codes [typeMismatch.simpleCriteria.projectIdIn5,typeMismatch.projectIdIn5,typeMismatch.java.util.List,typeMismatch]; arguments [org.springframework.context.support.DefaultMessageSourceResolvable: codes [simpleCriteria.projectIdIn5,projectIdIn5]; arguments []; default message [projectIdIn5]]; default message [Failed to convert value of type 'java.lang.String[]' to required type 'java.util.List'; nested exception is java.lang.NumberFormatException: For input string: "1,2,6"]]


Same request as above but with java pojo: localhost:8080/test/param/test-java-1?projectIdIn2=1,2,3&projectIdIn3=1,2,4&projectIdIn4=1,2,5&projectIdIn5=1,2,6&projectIdIn6=1,2,7&projectIdIn8=1,2,9&projectIdIn1=1&projectIdIn1=3

It will return a JSON: {"projectIdIn1":[1,3],"projectIdIn2":["1","2","3"],"projectIdIn5":[1,2,6],"projectIdIn6":["1","2","7"]}


Request for: localhost:8080/test/param/test-3?projectIdIn2=1,2,3&projectIdIn3=1,2,4&projectIdIn4=1,2,5&projectIdIn5=1,2,6&projectIdIn6=1,2,7&projectIdIn7=1,2,8&projectIdIn8=1,2,9&enum2=beijing,shanghai&projectIdIn1=5&projectIdIn1=6

Result: {"projectIdIn1":[5,6],"projectIdIn2":["1","2","3"],"projectIdIn3":[1,2,4],"projectIdIn4":["1","2","5"],"projectIdIn5":[1,2,6],"projectIdIn6":["1","2","7"],"projectIdIn7":[1,2,8],"projectIdIn8":["1","2","9"],"enum1":null,"enum2":["beijing","shanghai"],"enum3":null}



@RestController
@RequestMapping("/test/param")
class TestController {

    @GetMapping("/test-java-1")
    fun test1(criteria: JavaCriteria): JavaCriteria {
        return criteria
    }

    @GetMapping("/test-1")
    fun test1(criteria: SimpleCriteria): SimpleCriteria {
        return criteria
    }

    @GetMapping("/test-3")
    fun test3(
            @RequestParam projectIdIn1: Set<Long>? = null,
            @RequestParam projectIdIn2: Set<String>? = null,
            @RequestParam projectIdIn3: Set<ProjectId>? = null,
            @RequestParam projectIdIn4: Set<ProjectIdNew>? = null,
            @RequestParam projectIdIn5: List<Long>? = null,
            @RequestParam projectIdIn6: List<String>? = null,
            @RequestParam projectIdIn7: List<ProjectId>? = null,
            @RequestParam projectIdIn8: List<ProjectIdNew>? = null
    ): SimpleCriteria {
        return SimpleCriteria(
                projectIdIn1,
                projectIdIn2,
                projectIdIn3,
                projectIdIn4,
                projectIdIn5,
                projectIdIn6,
                projectIdIn7,
                projectIdIn8
        )
    }

}

typealias ProjectId = Long
typealias ProjectIdNew = String

data class SimpleCriteria(
        val projectIdIn1: Set<Long>? = null, // fails to convert 1,2
        val projectIdIn2: Set<String>? = null, // Get a list with one element "1,2"
        val projectIdIn3: Set<ProjectId>? = null, // fails to convert 1,2
        val projectIdIn4: Set<ProjectIdNew>? = null, // Get a list with one element "1,2"
        val projectIdIn5: List<Long>? = null, // fails to convert 1,2
        val projectIdIn6: List<String>? = null, // Get a list with one element "1,2"
        val projectIdIn7: List<ProjectId>? = null, // fails to convert 1,2
        val projectIdIn8: List<ProjectIdNew>? = null // Get a list with one element "1,2"
)

public class JavaCriteria {

    private Set<Long> projectIdIn1;
    private Set<String> projectIdIn2;
    private List<Long> projectIdIn5;
    private List<String> projectIdIn6;

    public JavaCriteria() {
    }

    public Set<Long> getProjectIdIn1() {
        return projectIdIn1;
    }

    public void setProjectIdIn1(final Set<Long> projectIdIn1) {
        this.projectIdIn1 = projectIdIn1;
    }

    public Set<String> getProjectIdIn2() {
        return projectIdIn2;
    }

    public void setProjectIdIn2(final Set<String> projectIdIn2) {
        this.projectIdIn2 = projectIdIn2;
    }

    public List<Long> getProjectIdIn5() {
        return projectIdIn5;
    }

    public void setProjectIdIn5(final List<Long> projectIdIn5) {
        this.projectIdIn5 = projectIdIn5;
    }

    public List<String> getProjectIdIn6() {
        return projectIdIn6;
    }

    public void setProjectIdIn6(final List<String> projectIdIn6) {
        this.projectIdIn6 = projectIdIn6;
    }

    @Override
    public boolean equals(final Object o) {
        if (this == o) return true;
        if (o == null || getClass() != o.getClass()) return false;
        final JavaCriteria that = (JavaCriteria) o;
        return Objects.equals(projectIdIn1, that.projectIdIn1) &&
                Objects.equals(projectIdIn2, that.projectIdIn2) &&
                Objects.equals(projectIdIn5, that.projectIdIn5) &&
                Objects.equals(projectIdIn6, that.projectIdIn6);
    }

    @Override
    public int hashCode() {
        return Objects.hash(projectIdIn1, projectIdIn2, projectIdIn5, projectIdIn6);
    }

    @Override
    public String toString() {
        return "JavaCriteria{" +
                "projectIdIn1=" + projectIdIn1 +
                ", projectIdIn2=" + projectIdIn2 +
                ", projectIdIn5=" + projectIdIn5 +
                ", projectIdIn6=" + projectIdIn6 +
                '}';
    }
}

closed time in 9 hours

Blackdread

issue commentspring-projects/spring-boot

Fail to map GET query params in pojo

Duplicates spring-projects/spring-framework#25815 Please don't open multiple instances of the same issue.

Blackdread

comment created time in 9 hours

create barnchbclozel/spring-framework

branch : gh-24830

created branch time in a day

push eventspring-projects/spring-framework

Brian Clozel

commit sha 687c3985d55d6322c388f285f8fade3adb4d603f

Fix merge-forward

view details

push time in a day

push eventspring-projects/spring-framework

Brian Clozel

commit sha e0b6067621f29948950d1856bf4c17bc3d67510f

Fix merge-forward

view details

push time in a day

push eventspring-projects/spring-framework

Sam Brannen

commit sha 2342f5f48a264212d650cc6e22930556395184aa

Remove unnecessary folders and files from PDF reference documentation Prior to this commit, the asciidoctor Gradle task was configured to generate both the HTML5 and PDF backends. Unfortunately, this resulted in resources such as HTML, JavaScript, CSS, and images being published alongside the generated PDF documents. This commit addresses this issue by introducing the use of a dedicated asciidoctorPdf Gradle task. The existing asciidoctor Gradle task has been modified to only generate HTML5 output. Both of these tasks now share common configuration supplied by the updated asciidoctorj Gradle task. In addition, the asciidoctor task now depends on the asciidoctorPdf task. Thus, invoking `./gradlew asciidoctor` will still generate both the HTML5 and PDF outputs; whereas, `./gradlew asciidoctorPdf` will generate only the PDF outputs. We may later decide to rework the tasks to introduce a dedicated asciidoctorHtml task so that we can generate the HTML outputs without having to generate the PDF outputs (which are more time consuming). See gh-25783

view details

Sam Brannen

commit sha a5a4960859d0d15bfe677be86291cd1e59047436

Do not generate reference docs for include-files Prior to this commit, the Asciidoctor Gradle tasks generated top-level HTML and PDF documents for AsciiDoc files that are included in other top-level documents. This causes slower builds and results in each include-file being published twice: 1) inline in the including document (as intended) 2) as a top-level document but missing surrounding context (unintended) The reason these include-files are generated as top-level documents is that the asciidoctor and asciidoctorPdf Gradle tasks are configured to use '*.adoc' as the input source files. This commit addresses this issue by moving the following include-files to new subdirectories. Locating the include-files in the subdirectories causes them to be ignored in the '*.adoc' pattern used to identify input source files. - data-access-appendix.adoc -> data-access/data-access-appendix.adoc - integration-appendix.adoc -> integration/integration-appendix.adoc - testing-webtestclient.adoc -> testing/testing-webtestclient.adoc Closes gh-25783

view details

Brian Clozel

commit sha a532c527dd47fef9e92e1afb8945d05257bfc3f0

Fix missing reference doc from docs archive Prior to this commit, the `docsZip` task would not reference the new output locations for the `asciidoctor` and `asciidoctorPdf` tasks. This results with missing reference docs in the docs zip. This commit updates the input locations of the Zip task to include the produced reference docs. Fixes gh-25783

view details

Brian Clozel

commit sha 6f04c7b60e19fd3f21aaa7dae0cfc596e2fc9ae1

Merge branch '5.2.x'

view details

push time in a day

issue closedspring-projects/spring-framework

Published reference documentation contains unnecessary folders and files

Affects: 5.x

The directory for the PDF documentation contains HTML files and JS and CSS directories that, AFAIK, don't need to be there and can be a bit confusing. For example, if you're not familiar with Asciidoctor you may open docinfo.html expecting some information about the PDF documentation. You get a blank page instead.

closed time in a day

wilkinsona

push eventspring-projects/spring-framework

Brian Clozel

commit sha a532c527dd47fef9e92e1afb8945d05257bfc3f0

Fix missing reference doc from docs archive Prior to this commit, the `docsZip` task would not reference the new output locations for the `asciidoctor` and `asciidoctorPdf` tasks. This results with missing reference docs in the docs zip. This commit updates the input locations of the Zip task to include the produced reference docs. Fixes gh-25783

view details

push time in a day

issue commentspring-projects/spring-framework

Published reference documentation contains unnecessary folders and files

Reopening as the reference docs are now missing from the zip archive.

➜  docs wget https://repo.spring.io/snapshot/org/springframework/spring/5.3.0-SNAPSHOT/spring-5.3.0-20200923.191224-393-docs.zip
--2020-09-24 18:05:15--  https://repo.spring.io/snapshot/org/springframework/spring/5.3.0-SNAPSHOT/spring-5.3.0-20200923.191224-393-docs.zip
Resolving repo.spring.io (repo.spring.io)... 35.241.58.96
Connecting to repo.spring.io (repo.spring.io)|35.241.58.96|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 31233368 (30M) [application/zip]
Saving to: ‘spring-5.3.0-20200923.191224-393-docs.zip’

spring-5.3.0-20200923.191224- 100%[=================================================>]  29,79M  23,7MB/s    in 1,3s

2020-09-24 18:05:16 (23,7 MB/s) - ‘spring-5.3.0-20200923.191224-393-docs.zip’ saved [31233368/31233368]

➜  docs tar -xzf spring-5.3.0-20200923.191224-393-docs.zip
➜  docs ls
javadoc-api                               spring-5.3.0-20200923.191224-393-docs.zip
kdoc-api
wilkinsona

comment created time in a day

IssuesEvent
IssuesEvent

push eventspring-projects/spring-framework

Brian Clozel

commit sha 6e7be762788fe6d87b759e78ff045e76e9db11ac

Upgrade to AsciidoctorJ 3.1.0 Closes gh-24991

view details

push time in 2 days

issue closedspring-projects/spring-framework

Upgrade to Asciidoctor Gradle plugin 3.x

Looking at the reference documentation of the plugin, we might improve our configuration and better include the documentation theme from spring-doc-resources.

closed time in 2 days

bclozel

issue closedspring-projects/spring-boot

I changed field name in Java Class: but JSON response is more different

Hi

I have SpringBootApplication. For customer request, I changed some field names in my Java Class. However, when I executed REST API with Postman, I saw that JSON response is more different to my Java Class fields.

I do not khow how to change these values, and it is stopper for my implementation and adjustments project.

Thanks. Postman_REST_API_createdocument Postman_REST_API_infoevaluacion

closed time in 3 days

cristian9401

issue commentspring-projects/spring-boot

I changed field name in Java Class: but JSON response is more different

Thanks for getting in touch, but it feels like this is a question that would be better suited to StackOverflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.

cristian9401

comment created time in 3 days

issue commentspring-projects/spring-framework

UriComponentsBuilder should not treat a dot followed by a number as illegal

Adding this comment for future reference.

The URI implementation calls this case out with:

// for a fully qualified hostname check that the rightmost
// label starts with an alpha character.
if (l > start && !match(charAt(l), L_ALPHA, H_ALPHA)) {
  fail("Illegal character in hostname", l);
}

The ABNF defined by RFC 2396 looks like alphanum are allowed after the last -, and it seems to be acknowledged by the OpenJDK team in JDK-8188305.

jenniferbain

comment created time in 3 days

issue closedspring-projects/spring-framework

UriComponentsBuilder should not treat a dot followed by a number as illegal

<!-- !!! For Security Vulnerabilities, please go to https://pivotal.io/security !!! --> Affects: 5.2.8.RELEASE


<!-- Thanks for taking the time to create an issue. Please read the following:

  • Questions should be asked on Stack Overflow.
  • For bugs, specify affected versions and explain what you are trying to do.
  • For enhancements, provide context and describe the problem.

Issue or Pull Request? Create only one, not both. GitHub treats them as the same. If unsure, start with an issue, and if you submit a pull request later, the issue will be closed as superseded. --> There is an issue when using UriComponentsBuilder to build a URI for an address that contains a . followed by a number. The address is valid as an internal Kubernetes cluster address but fails the UriComponentsBuilder validation for the "illegal character" of "." This issue can be overcome by wrapping the String output in a URL object and then calling the .toUri method on the result, where no error is thrown.

See following code for example:

    @Test
    public void test() throws URISyntaxException, MalformedURLException {
        
        UriComponentsBuilder uriComponentsBuilder = getUriBuilder();
        String query = String.format("(eq,attribute,%s)", "23426342786242");

        //Without .toUri and Cast to URL does not throw error results in:
        // http://deployment-name.20-14/api/path/to/resource?filter=(eq,attribute,23426342786242)
        String noToUri = uriComponentsBuilder
                .queryParam("filter", query).build().toString();
        URI uri2 = new URL(noToUri).toURI();

        //With .toUri straight from build results in :
        // java.lang.IllegalStateException: Could not create URI object: Illegal character in hostname at index 23: 
        // http://deployment-name.20-14/api/path/to/resource?filter=(eq,attribute,23426342786242)
        URI test =getUriBuilder()
                .queryParam("filter", query).build().toUri();

    }

    private UriComponentsBuilder getUriBuilder(String... pathSegments) {
        return UriComponentsBuilder.fromHttpUrl("http://deployment-name.20-14")
                .path("/api/path/to/resource")
                .pathSegment(pathSegments);
    }

closed time in 3 days

jenniferbain

issue commentspring-projects/spring-framework

UriComponentsBuilder should not treat a dot followed by a number as illegal

This is not strictly related to Spring Framework actually, but a consequence of which method we're using to instantiate a URI.

In the first case, we're implicitly creating the URI with URI uri = new URI(url.toString()); In java.net, this method does not perform additional validations with its parser, namely the URI.Parser.requireServerAuthority.

In the second case, our UriComponentsBuilder has not encoded the resulting URI yet so we can use the alternative constructor new URI(getScheme(), getUserInfo(), getHost(), getPort(), path, getQuery(), getFragment()). This constructor performs the additional URI.Parser.requireServerAuthority validation and fails.

We can reproduce this without involving Spring Framework at all:

➜  jshell
|  Welcome to JShell -- Version 15
|  For an introduction type: /help intro

jshell> new URI("http", "", "deployment-name.20-14", -1, "/path", "", "")
|  Exception java.net.URISyntaxException: Illegal character in hostname at index 24: http://@deployment-name.20-14/path?#
|        at URI$Parser.fail (URI.java:2963)
|        at URI$Parser.parseHostname (URI.java:3506)
|        at URI$Parser.parseServer (URI.java:3347)
|        at URI$Parser.parseAuthority (URI.java:3266)
|        at URI$Parser.parseHierarchical (URI.java:3208)
|        at URI$Parser.parse (URI.java:3164)
|        at URI.<init> (URI.java:708)
|        at (#1:1)

jshell> var uri = URI.create("http://deployment-name.20-14/path")
uri ==> http://deployment-name.20-14/path

You can work around this issue by encoding the UriComponents before calling the toURI() method:

@Test
void gh25784() {
  UriComponentsBuilder uriComponentsBuilder = UriComponentsBuilder.fromHttpUrl("http://deployment-name.20-14")
	.path("/api/path/to/resource");

  String query = String.format("(eq,attribute,%s)", "23426342786242");
  URI uri = uriComponentsBuilder.queryParam("filter", query).build().encode().toUri();

  assertThat(uri.toASCIIString()).isEqualTo("http://deployment-name.20-14/api/path/to/resource?filter=(eq,attribute,23426342786242)");
}

I think we need to consider this as a limitation of the JDK URI; we can't really encode the URI builder before turning it into an URI in all cases, because we should reflect the behavior difference of the JDK (and we have a test for that in org.springframework.web.util.UriComponentsTests#toUriNotEncoded.

In summary, I'm closing this issue, but with a known workaround: you should encode the URI builder with the appropriate charset before turning this into an URI.

Thanks!

jenniferbain

comment created time in 3 days

issue commentspring-projects/spring-framework

Support for HTTP Request Method: SEARCH

We do support already custom methods on Controllers, would that support be enough? Are you expecting something more here?

joao-rebelo

comment created time in 3 days

issue commentspring-projects/spring-framework

Support for HTTP Request Method: SEARCH

There's a new version of this draft published but it's expired. We're not seeing much activity in the Spring ecosystem around that. We might work on this if technologies we support offer this feature.

Do you have links to Java libraries supporting this?

joao-rebelo

comment created time in 3 days

push eventspring-io/sagan

Brian Clozel

commit sha feb8b81bbea8a276ed076ce1a9c32db30c5bafb5

Make version input readonly in releases form To avoid issues with ordering and and version management, the releases form in the admin console now makes the version field readonly. Developers now should add/delete releases as they see fit.

view details

push time in 3 days

issue commentspring-projects/spring-framework

Empty or blank required UUID header validation results in 200 response status

The team discussed this issue. W've come to the conclusion that the StringToUUIDConverter implementation might be odd here (returning null for empty strings).

We don't think that the behavior of the "required" attribute on @RequestHeader is in question here, since the consensus here is that it requires the presence of such header in the request, but not necessarily that it won’t be null.

We first need to review other the existing converter implementations and reconsider this issue after.

maxdewil

comment created time in 3 days

PR closed spring-io/sagan

Jdk8 datetime

we can work togetter

+124 -52

2 comments

15 changed files

duransakalli

pr closed time in 3 days

pull request commentspring-io/sagan

Jdk8 datetime

duplicates #374

duransakalli

comment created time in 3 days

push eventspring-io/sagan

Brian Clozel

commit sha 1980099e2a6e20a8406f1ef329e5a69b8af9836a

Fix guides template Fixes gh-999

view details

push time in 3 days

issue closedspring-io/sagan

Some guides are not rendering

I have no idea of the scope of this problem, nor the cause, nor whether it is a temporary issue or not. Bot some of the guides do not display any content.

For example: https://spring.io/guides/gs/accessing-data-jpa/

I can still find the guide via google or via the https://spring.io/guides/ page (search for jpa). But when I go to the actual guide there's no content there (just the header and footers we see on every page but no tutorial contents). Most of the other guides I tried to go to do work, but there was at least one other guide that didn't. Sorry I do not remember which one it was, I clicked on a few.

closed time in 3 days

kdvolder

startedomrilotan/cloudflare-google-tagmanager

started time in 4 days

delete branch spring-io/sagan

delete branch : projects

delete time in 4 days

push eventspring-io/sagan

Brian Clozel

commit sha 70dd61aa51bb989d89cfd9e8aaaf5066cd4d0faa

Refactor domain model for Projects This commit completely refactors the domain model for Projects and Groups, Releases, Samples, etc. This commit also adds a new Generation concept, which describes the support policy for a given generation of releases. These changes are reflected in a new Flyway migration script as well as the fixtures. Because the latest migration script uses postgresql-specific queries, the standalone H2 configuration now enables the postgresql mode. Fixes gh-903

view details

Brian Clozel

commit sha 65f9d724140af16c2fee15ef2bfe8a4be4fe6607

Update ProjectMetadataService This commit updates the ProjectMetadataService to use the new domain model and repositories. We're also adding a new SupportPolicy processor that calculates the support policy EOL dates on the model before persisting it to the database. See gh-964

view details

Brian Clozel

commit sha 58850eb242fac91750bacfbcf90c745f24d22107

Update and move SVG Badge support to its own package

view details

Brian Clozel

commit sha ae750525f25eced6051946a0c002250b2f45996c

Add ModelMapper library support This commit adds the ModelMapper library to the application for mapping domain model to/from DTOs. This also requires a change in the devtools configuration for reload support.

view details

Brian Clozel

commit sha 8ac8c7f1a161d86e3a927776d5b4a5bb68c78bb6

Update project pages This commit updates the projects pages after the domain model changes and also adds a new tab in the project view to display project generation support dates. Fixes gh-987

view details

Brian Clozel

commit sha 443f449a51bb09aebc8e6f3f5da35c47b597ca48

Rework the project admin pages This commit completely reworks the project admin pages. Prior to this commit, there was a single project admin page binding the full project model to a single form. This made it difficult for users to update project information and hard to maintain this part of the application. This commit uses ModelMapper to map only the relevant parts to the admin UI and split the form into multiple pages.

view details

Brian Clozel

commit sha 97069e2344af331c01482c335de522f399cd9927

Move modules under the sagan.site package

view details

Brian Clozel

commit sha 1815137f227aa288df85b48131a2802aeac51972

Remove Project Metadata API Prior to this commit, this application would expose a Web API under `"/project_metadata/*"`. This was initially used for external project pages hosted on projects.spring.io (previously, GitHub pages). It's also been used by start.spring.io and Initializr instances to fetch the list of available Spring Boot versions at runtime. This is problematic since this Web API is merely serializing the raw domain model as JSON. Any change in the model results in incompatible changes in the API. Now that all project pages haven been moved to this application, we can focus on the remaining use case and ship tailored JSON payloads to Initializr instances until they upgrade to the new API. This commit removes the former implementation and provides a legacy endpoint for Initializr instances only. Closes gh-978

view details

Brian Clozel

commit sha 604c8428af047977df445fc0e55d0f9cb88550a0

Add new REST API for project metadata Now that the previous Web API has been removed, this commit adds a new REST API for various resources managed by this application.

view details

Damien Vitrac

commit sha 485ac1365d3d7b6e12126c3ca5a8f256b8379970

Add project support timeline visualisation This commit adds a JS widget for visualising the support timeline for project generations. Closes gh-964

view details

Damien Vitrac

commit sha abb44a5643c128b544cef8426cc79799d7ba5899

Fix timeline creation

view details

Damien Vitrac

commit sha 3978797042402effd1bc248f5e20c26f34608cf5

Fix dark mode colors

view details

Damien Vitrac

commit sha ce5ea481ec4a6e71de4192d33885783d2798f6b9

Timeline legend

view details

Brian Clozel

commit sha f20ccf4483d800252c02d678633270e057319932

Upgrade Node.js version

view details

Brian Clozel

commit sha e15e47bd14af866be6e5d7af94027e1ee2437470

Update devtools configuration for webpack build This commit ensures that all resources built by webpack during local developement do not trigger a devtools context restart.

view details

Damien Vitrac

commit sha 477eedd7f7ffedd5aa78264e870bcc94d2580d73

Update legend timeline on project page

view details

Brian Clozel

commit sha 64fe8637c4b92905e29c0dd2d619cf742e8938c7

Update suppport timeline legend

view details

Brian Clozel

commit sha 236ed4a42079ba3b0f25f0bf80dd31730a58b628

Add last-modified date on project generations model This commit adds a last-modified date on the project generations domain model, allowing to send HTTP cache response headers to clients on the Web API.

view details

Brian Clozel

commit sha 7d7ce9f07b4719c4c546aac41684a50f46ec051f

Update footer on the EOL support project tab

view details

Damien Vitrac

commit sha e675a1fd0389d71ae933442e837cfa03dc3e0fcf

Update timeline legend

view details

push time in 4 days

issue closedspring-io/sagan

Calendar releases

As a user, I would like to see on the project page a timeline of the releases and their support.

Inspiration: https://www.php.net/supported-versions.php

closed time in 4 days

oodamien

issue closedspring-io/sagan

Retire the /project_metadata API

At first, the "/project_metadata" was meant as an "internal" API supporting former versions of the project pages (hosted on projects.spring.io). Over time, this has been extended and is being used more and more:

  • project teams are using it to automatically update their project information as part of their release pipeline
  • Spring Initializr instances are relying on it to fetch version information for Spring Boot (and many aren't using caching unfortunately
  • other parties might be using this API for other goals

Currently this API is very brittle since it's not thoroughly tested and is not friendly to consumers. We're basically serializing the entities, which makes it hard to customize the payloads and to change the database schema without breaking clients.

We need to create a new API and remove the "project_metadata" one.

closed time in 4 days

bclozel

issue closedspring-io/sagan

Support new Calver naming for display

Currently, it looks a bit wonky image

Should probably be

2020.0.0 [SNAPSHOT]
2020.0.0 M3 [PRE]

closed time in 4 days

spencergibb

issue closedspring-io/sagan

Updating a version causes the current checkbox to change

This bug hits us often when releasing Spring Boot. To reproduce:

  • Got to "manage projects"
  • Edit the existing project
  • Edit the version for the current release by changing the last digit (i.e. as if a patch release has happened)
  • Click update

The expected behavior is the updated version retains the current checkbox. Unfortunately, this sometimes seems to get lost.

closed time in 4 days

philwebb

issue closedspring-io/sagan

Spring Cloud Reference/API Links are Inconsistent

I've noticed a lot of inconsistencies with the Reference and API links for Spring Cloud projects.

Findings

  • Reference links for most of the Spring Cloud projects don't account for the specific release version you're selecting. The links are the same URL for each release version for most Spring Cloud projects.
  • API links for most of the Spring Cloud projects point to their respective GitHub repos instead of their Javadoc like other Spring projects.
  • spring-cloud-bus reference links point to the project page instead of the documentation.
  • spring-cloud-cluster project page link points to the main spring-cloud project page. no reference or api links.
  • spring-cloud-starters, spring-cloud-cli project page links point to their respective GitHub repos.
  • spring-cloud-dataflow, spring-cloud-stream-modules api link for the 1.0.0 M2 release is broken
  • spring-cloud-zookeeper api links point to the same documentation as the reference links.
  • Inconsistent use of docs & cloud sub-domains.

I've compiled a table of the reference and api links for all Spring Cloud projects. The links were gathered from each project page.

image

closed time in 4 days

andersonkyle

issue commentspring-io/sagan

Spring Cloud Reference/API Links are Inconsistent

I think this has been fixed in the meantime by the Spring Cloud team. The documentation has also moved to docs.spring.io now.

andersonkyle

comment created time in 4 days

issue closedspring-io/sagan

show "push-to-pws" button on mobile version

At the moment the "push-to-pws" button shows up on the page of the Spring guides when using a regular browser, but doesn't appear on the mobile version of the page. Would be great if this would show up on the mobile page, too.

closed time in 5 days

martinlippert

issue commentspring-io/sagan

show "push-to-pws" button on mobile version

We're retiring the push to PWS support.

martinlippert

comment created time in 5 days

issue closedspring-io/sagan

why build failed?

F:\ideaprojects\sagan>gradlew.bat build

Configure project :sagan-site Repository https://jcenter.bintray.com/ replaced by http://maven.aliyun.com/nexus/content/groups/public/.

Task :sagan-client:npmSetup F:\ideaprojects\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm -> F:\ideaprojects\sagan\sagan-client.gradle\npm\npm-v6.14.4\node_modules\npm\bin\npm-cli.js F:\ideaprojects\sagan\sagan-client.gradle\npm\npm-v6.14.4\npx -> F:\ideaprojects\sagan\sagan-client.gradle\npm\npm-v6.14.4\node_modules\npm\bin\npx-cli.js

  • npm@6.14.4 added 435 packages from 869 contributors in 58.4s

Task :sagan-client:npmInstall npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated

node-sass@4.14.1 install F:\ideaprojects\sagan\sagan-client\node_modules\node-sass node scripts/install.js

Cached binary found at C:\Users\11477\AppData\Roaming\npm-cache\node-sass\4.14.1\win32-x64-79_binding.node

core-js@2.6.11 postinstall F:\ideaprojects\sagan\sagan-client\node_modules\core-js node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

node-sass@4.14.1 postinstall F:\ideaprojects\sagan\sagan-client\node_modules\node-sass node scripts/build.js

Binary found at F:\ideaprojects\sagan\sagan-client\node_modules\node-sass\vendor\win32-x64-79\binding.node Testing binary Binary is fine npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"13.12.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 885 packages from 553 contributors and audited 887 packages in 146.661s

38 packages are looking for funding run npm fund for details

found 2 vulnerabilities (1 low, 1 high) run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_install npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 887 packages in 5.161s

38 packages are looking for funding run npm fund for details

found 2 vulnerabilities (1 low, 1 high) run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_run_build

sagan@ build F:\ideaprojects\sagan\sagan-client webpack

Hash: 2d2d11fe286afc7a078a Version: webpack 4.44.1 Time: 14476ms Built at: 2020/08/17 涓嬪崍5:58:01 21 assets Entrypoint main = css/main.css js/main.js Entrypoint guide = css/guide.css js/guide.js Entrypoint project = css/project.css js/project.js Entrypoint team = css/team.css js/team.js Entrypoint profile = css/profile.css js/profile.js Entrypoint blog = css/blog.css js/blog.js Entrypoint admin = css/admin.css js/admin.js Entrypoint theme = js/theme.js Entrypoint run_prettify = js/run_prettify.js [16] ./src/app/main.js 10.3 KiB {3} [built] [19] ./src/css/main.css 1.46 KiB {3} [built] [failed] [1 error] [20] ./src/css/dark.scss 39 bytes {3} [built] [21] ./src/app/guide.js 1.17 KiB {2} [built] [34] ./src/css/guide.css 39 bytes {2} [built] [35] ./src/app/project.js 1.81 KiB {5} [built] [36] ./src/css/project.css 39 bytes {5} [built] [37] ./src/app/team.js 3.98 KiB {7} [built] [38] ./src/css/team.css 39 bytes {7} [built] [39] ./src/app/profile.js 3.67 KiB {4} [built] [40] ./src/css/profile.css 39 bytes {4} [built] [41] ./src/app/blog.js 24 bytes {1} [built] [43] ./src/app/admin.js 909 bytes {0} [built] [49] ./src/app/theme.js 305 bytes {8} [built] [50] ./src/app/run_prettify.js 18.1 KiB {6} [built] + 46 hidden modules

WARNING in configuration The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment. You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/

ERROR in ./src/css/main.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (F:\ideaprojects\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at F:\ideaprojects\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at F:\ideaprojects\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 7:0-24

ERROR in ./node_modules/@fortawesome/fontawesome-free/css/all.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at F:\ideaprojects\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (F:\ideaprojects\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (F:\ideaprojects\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at F:\ideaprojects\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at F:\ideaprojects\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 4:0-50 Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/@fancyapps/fancybox/dist/jquery.fancybox.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/@fortawesome/fontawesome-free/css/all.css: 1 asset Entrypoint mini-css-extract-plugin = * 18 modules

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 7:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 12:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 17:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 5:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 6:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 10:36-79

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 11:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 15:37-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 16:37-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.eot 1:0
Module parse failed: Unexpected character '锟?' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 4:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.eot 1:0
Module parse failed: Unexpected character '锟?' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 14:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 9:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 13:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 8:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 18:37-76

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/bulma/css/bulma.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/jquery-datetimepicker/jquery.datetimepicker.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!src/css/dark.scss: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./src/css/dark.scss 9.89 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/admin.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/admin.css 2.83 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/blog.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/blog.css 5.03 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/guide.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/guide.css 3.99 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/main.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/main.css 107 KiB {0} [built] [3] ./src/fonts/metropolis-regular-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [4] ./src/fonts/metropolis-regular-webfont.woff 284 bytes {0} [built] [failed] [1 error] [5] ./src/fonts/metropolis-bold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [6] ./src/fonts/metropolis-bold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [7] ./src/fonts/metropolis-extrabold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [8] ./src/fonts/metropolis-extrabold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [9] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 271 bytes {0} [built] [failed] [1 error] [10] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 284 bytes {0} [built] [failed] [1 error] [11] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 284 bytes {0} [built] [failed] [1 error] [12] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 284 bytes {0} [built] [failed] [1 error] [13] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 424 bytes {0} [built] [failed] [1 error] [14] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 281 bytes {0} [built] [failed] [1 error] [15] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 284 bytes {0} [built] [failed] [1 error] [16] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 284 bytes {0} [built] [failed] [1 error] + 24 hidden modules

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 13:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 18:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 23:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 28:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 33:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 38:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 20:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 30:37-106

ERROR in ./src/fonts/metropolis-regular-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 4:36-88

ERROR in ./src/fonts/metropolis-regular-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 5:36-87

ERROR in ./src/fonts/metropolis-bold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 6:36-85

ERROR in ./src/fonts/metropolis-bold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 7:36-84

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 8:36-90

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 9:36-89

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 11:36-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 12:36-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 16:37-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 17:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 21:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 22:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 26:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 27:37-105

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 31:37-108

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 32:37-107

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 36:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 37:37-103

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.eot 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 35:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 1:0
Module parse failed: Unexpected character '锟?' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 15:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.eot 1:0
Module parse failed: Unexpected character '锟?' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 25:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 10:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 14:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 19:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 24:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 29:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 34:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 39:37-102

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/profile.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/profile.css 4.18 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/project.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/project.css 11.7 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/team.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/team.css 2.06 KiB {0} [built] + 1 hidden module npm ERR! code ELIFECYCLEUTING [4m 9s] npm ERR! errno 216% EXECUTING [4m 10s] npm ERR! sagan@ build: webpackm 10s] npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the sagan@ build 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! C:\Users\11477\AppData\Roaming\npm-cache_logs\2020-08-17T09_58_01_408Z-debug.log

Task :sagan-client:npm_run_build FAILED

FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ':sagan-client:npm_run_build'.

Process 'command 'F:\ideaprojects\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2

  • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 4m 13s 5 actionable tasks: 5 executed

closed time in 5 days

sundayong

issue commentspring-io/sagan

why build failed?

Duplicates #979

sundayong

comment created time in 5 days

issue closedspring-io/sagan

org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://github.com/login/oauth/access_token":

I deployed Sagan web application to Aliyun server, but failed to login with GitHub third party. I use the built-in Tomcat, and the server can ping github.com website. This is my log:

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::       (v1.5.18.RELEASE)

2020-07-08 19:20:48.496  INFO 4857 --- [           main] sagan.SiteApplication                    : Starting SiteApplication on iZbp1exgdlpkfrcg6eu9arZ with PID 4857 (/home/space/sagan-site-1.0.0.BUILD-SNAPSHOT.jar started by root in /home/space)
2020-07-08 19:20:48.504  INFO 4857 --- [           main] sagan.SiteApplication                    : The following profiles are active: standalone
2020-07-08 19:20:57.797  WARN 4857 --- [           main] sagan.support.github.GitHubConfig        : GitHub API access will be rate-limited at 60 req/hour
2020-07-08 19:20:59.177  INFO 4857 --- [           main] b.a.s.AuthenticationManagerConfiguration :

Using default security password: 60f9b679-26f5-40aa-8831-119e581273a2

2020-07-08 19:21:00.328  INFO 4857 --- [           main] sagan.SiteApplication                    : Started SiteApplication in 12.504 seconds (JVM running for 13.123)
2020-07-08 19:25:52.620 ERROR 4857 --- [p-nio-80-exec-3] o.s.s.c.web.ProviderSignInController     : Exception while completing OAuth 2 connection:

org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://github.com/login/oauth/access_token": Connect to github.com:443 [github.com/47.31.167.15] failed: 连接超时; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to github.com:443 [github.com/47.31.167.15] failed: 连接超时
        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:674) ~[spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:621) ~[spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:388) ~[spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.social.oauth2.OAuth2Template.postForAccessGrant(OAuth2Template.java:242) ~[spring-social-core-1.1.6.RELEASE.jar!/:1.1.6.RELEASE]
        at org.springframework.social.oauth2.OAuth2Template.exchangeForAccess(OAuth2Template.java:144) ~[spring-social-core-1.1.6.RELEASE.jar!/:1.1.6.RELEASE]
        at org.springframework.social.connect.web.ConnectSupport.completeConnection(ConnectSupport.java:160) ~[spring-social-web-1.1.6.RELEASE.jar!/:1.1.6.RELEASE]
        at org.springframework.social.connect.web.ProviderSignInController.oauth2Callback(ProviderSignInController.java:228) ~[spring-social-web-1.1.6.RELEASE.jar!/:1.1.6.RELEASE]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_45]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_45]
        at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_45]
        at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) [spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133) [spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:849) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:760) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:635) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) [spring-webmvc-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-embed-websocket-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.springframework.boot.web.filter.ApplicationContextHeaderFilter.doFilterInternal(ApplicationContextHeaderFilter.java:55) [spring-boot-1.5.18.RELEASE.jar!/:1.5.18.RELEASE]
        at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.21.RELEASE.jar!/:4.3.21.RELEASE]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) [urlrewritefilter-4.0.4.jar!/:4.0.4]
        at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) [urlrewritefilter-4.0.4.jar!/:4.0.4]
        at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) [urlrewritefilter-4.0.4.jar!/:4.0.4]
        at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:389) [urlrewritefilter-4.0.4.jar!/:4.0.4]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.35.jar!/:8.5.35]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.35.jar!/:8.5.35]

closed time in 5 days

WeiXiaoxia

issue closedspring-io/sagan

FAILURE: Build failed with an exception.

Microsoft Windows [Version 10.0.18362.1082] (c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\AMOL>cd C:\Open Source\sagan

C:\Open Source\sagan>gradlew :sagan-site:bootRun Starting a Gradle Daemon, 7 busy Daemons could not be reused, use --status for details

Task :sagan-client:npmSetup C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm -> C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\node_modules\npm\bin\npm-cli.js C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\npx -> C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\node_modules\npm\bin\npx-cli.js

  • npm@6.14.4 added 435 packages from 869 contributors in 197.178s

Task :sagan-client:npmInstall npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

node-sass@4.14.1 install C:\Open Source\sagan\sagan-client\node_modules\node-sass node scripts/install.js

Cached binary found at C:\Users\AMOL\AppData\Roaming\npm-cache\node-sass\4.14.1\win32-x64-79_binding.node

core-js@2.6.11 postinstall C:\Open Source\sagan\sagan-client\node_modules\core-js node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

:sagan-client:npmInstall The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: https://opencollective.com/core-js https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

node-sass@4.14.1 postinstall C:\Open Source\sagan\sagan-client\node_modules\node-sass node scripts/build.js

Binary found at C:\Open Source\sagan\sagan-client\node_modules\node-sass\vendor\win32-x64-79\binding.node Testing binary Binary is fine npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"13.12.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 887 packages from 554 contributors and audited 889 packages in 284.378s

41 packages are looking for funding run npm fund for details

found 1 low severity vulnerability run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_install npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 889 packages in 9.727s

41 packages are looking for funding run npm fund for details

found 1 low severity vulnerability run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_run_build

sagan@ build C:\Open Source\sagan\sagan-client webpack

Hash: 1e7c9cfb2254d0bc9651 Version: webpack 4.44.2 Time: 16995ms Built at: 20/09/2020 4:14:16 pm 21 assets Entrypoint main = css/main.css js/main.js Entrypoint guide = css/guide.css js/guide.js Entrypoint project = css/project.css js/project.js Entrypoint team = css/team.css js/team.js Entrypoint profile = css/profile.css js/profile.js Entrypoint blog = css/blog.css js/blog.js Entrypoint admin = css/admin.css js/admin.js Entrypoint theme = js/theme.js Entrypoint run_prettify = js/run_prettify.js [16] ./src/app/main.js 10.3 KiB {3} [built] [19] ./src/css/main.css 1.45 KiB {3} [built] [failed] [1 error] [20] ./src/css/dark.scss 39 bytes {3} [built] [21] ./src/app/guide.js 1.17 KiB {2} [built] [34] ./src/css/guide.css 39 bytes {2} [built] [35] ./src/app/project.js 1.81 KiB {5} [built] [36] ./src/css/project.css 39 bytes {5} [built] [37] ./src/app/team.js 3.98 KiB {7} [built] [38] ./src/css/team.css 39 bytes {7} [built] [39] ./src/app/profile.js 3.67 KiB {4} [built] [40] ./src/css/profile.css 39 bytes {4} [built] [41] ./src/app/blog.js 24 bytes {1} [built] [43] ./src/app/admin.js 909 bytes {0} [built] [49] ./src/app/theme.js 305 bytes {8} [built] [50] ./src/app/run_prettify.js 18.1 KiB {6} [built] + 46 hidden modules

WARNING in configuration The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment. You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/

ERROR in ./src/css/main.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at C:\Open Source\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 7:0-24

ERROR in ./node_modules/@fortawesome/fontawesome-free/css/all.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at C:\Open Source\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 4:0-50 Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules@fancyapps\fancybox\dist\jquery.fancybox.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules@fortawesome\fontawesome-free\css\all.css: 1 asset Entrypoint mini-css-extract-plugin = * 18 modules

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 7:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 12:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 17:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 5:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 6:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 10:36-79

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 11:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 15:37-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 16:37-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 4:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 14:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 9:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 13:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 8:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 18:37-76

Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\bulma\css\bulma.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\jquery-datetimepicker\jquery.datetimepicker.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\sass-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\dark.scss: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./src/css/dark.scss 9.89 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\admin.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/admin.css 2.83 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\blog.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/blog.css 5.03 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\guide.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/guide.css 3.99 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\main.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/main.css 107 KiB {0} [built] [3] ./src/fonts/metropolis-regular-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [4] ./src/fonts/metropolis-regular-webfont.woff 284 bytes {0} [built] [failed] [1 error] [5] ./src/fonts/metropolis-bold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [6] ./src/fonts/metropolis-bold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [7] ./src/fonts/metropolis-extrabold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [8] ./src/fonts/metropolis-extrabold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [9] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 271 bytes {0} [built] [failed] [1 error] [10] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 284 bytes {0} [built] [failed] [1 error] [11] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 284 bytes {0} [built] [failed] [1 error] [12] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 284 bytes {0} [built] [failed] [1 error] [13] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 424 bytes {0} [built] [failed] [1 error] [14] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 281 bytes {0} [built] [failed] [1 error] [15] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 284 bytes {0} [built] [failed] [1 error] [16] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 284 bytes {0} [built] [failed] [1 error] + 24 hidden modules

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 13:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 18:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 23:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 28:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 33:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 38:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 20:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 30:37-106

ERROR in ./src/fonts/metropolis-regular-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 5:36-87

ERROR in ./src/fonts/metropolis-regular-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 4:36-88

ERROR in ./src/fonts/metropolis-bold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 6:36-85

ERROR in ./src/fonts/metropolis-bold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 7:36-84

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 8:36-90

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 9:36-89

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 11:36-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 12:36-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 17:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 16:37-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 21:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 22:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 27:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 26:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 31:37-108

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 32:37-107

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 37:37-103

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 36:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.eot 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 35:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 15:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 25:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 10:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 14:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 19:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 24:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 29:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 34:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 39:37-102

Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\profile.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/profile.css 4.18 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\project.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/project.css 11.7 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\team.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/team.css 2.06 KiB {0} [built] + 1 hidden module npm ERR! code ELIFECYCLE npm ERR! errno 246% EXECUTING [10m 32s] npm ERR! sagan@ build: webpack npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the sagan@ build 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! C:\Users\AMOL\AppData\Roaming\npm-cache_logs\2020-09-20T10_44_17_131Z-debug.log

Task :sagan-client:npm_run_build FAILED

FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ':sagan-client:npm_run_build'.

Process 'command 'C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2

  • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 10m 54s 5 actionable tasks: 5 executed

C:\Open Source\sagan>java -version java version "1.8.0_251" Java(TM) SE Runtime Environment (build 1.8.0_251-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)

C:\Open Source\sagan>node -version node: bad option: -version

C:\Open Source\sagan>node -v v12.13.1

C:\Open Source\sagan>gradlew :sagan-site:bootRun --stacktrace

Task :sagan-client:npmInstall npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 889 packages in 7.037s

41 packages are looking for funding run npm fund for details

found 1 low severity vulnerability run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_install npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 889 packages in 8.053s

41 packages are looking for funding run npm fund for details

found 1 low severity vulnerability run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_run_build

sagan@ build C:\Open Source\sagan\sagan-client webpack

Hash: 1e7c9cfb2254d0bc9651 Version: webpack 4.44.2 Time: 5483ms Built at: 20/09/2020 4:51:04 pm 21 assets Entrypoint main = css/main.css js/main.js Entrypoint guide = css/guide.css js/guide.js Entrypoint project = css/project.css js/project.js Entrypoint team = css/team.css js/team.js Entrypoint profile = css/profile.css js/profile.js Entrypoint blog = css/blog.css js/blog.js Entrypoint admin = css/admin.css js/admin.js Entrypoint theme = js/theme.js Entrypoint run_prettify = js/run_prettify.js [16] ./src/app/main.js 10.3 KiB {3} [built] [19] ./src/css/main.css 1.45 KiB {3} [built] [failed] [1 error] [20] ./src/css/dark.scss 39 bytes {3} [built] [21] ./src/app/guide.js 1.17 KiB {2} [built] [34] ./src/css/guide.css 39 bytes {2} [built] [35] ./src/app/project.js 1.81 KiB {5} [built] [36] ./src/css/project.css 39 bytes {5} [built] [37] ./src/app/team.js 3.98 KiB {7} [built] [38] ./src/css/team.css 39 bytes {7} [built] [39] ./src/app/profile.js 3.67 KiB {4} [built] [40] ./src/css/profile.css 39 bytes {4} [built] [41] ./src/app/blog.js 24 bytes {1} [built] [43] ./src/app/admin.js 909 bytes {0} [built] [49] ./src/app/theme.js 305 bytes {8} [built] [50] ./src/app/run_prettify.js 18.1 KiB {6} [built] + 46 hidden modules

WARNING in configuration The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment. You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/

ERROR in ./src/css/main.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at C:\Open Source\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 7:0-24

ERROR in ./node_modules/@fortawesome/fontawesome-free/css/all.css Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleParseError: Module parse failed: Unexpected character ' ' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) at handleParseError (C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19) at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5 at C:\Open Source\sagan\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12 at C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3 at iterateNormalLoaders (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10) at Array.<anonymous> (C:\Open Source\sagan\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4) at Storage.finished (C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16) at C:\Open Source\sagan\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9 at C:\Open Source\sagan\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) @ ./src/app/main.js 4:0-50 Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules@fancyapps\fancybox\dist\jquery.fancybox.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules@fortawesome\fontawesome-free\css\all.css: 1 asset Entrypoint mini-css-extract-plugin = * 18 modules

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 7:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 12:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 17:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 5:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 10:36-79

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 6:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 11:36-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 15:37-78

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 16:37-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 4:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 14:37-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 9:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-regular-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 13:36-77

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-brands-400.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 8:36-76

ERROR in ./node_modules/@fortawesome/fontawesome-free/webfonts/fa-solid-900.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.14.0 by @fontawesome - https://fontawesome.com
 @ ./node_modules/@fortawesome/fontawesome-free/css/all.css (./node_modules/css-loader/dist/cjs.js!./node_modules/@fortawesome/fontawesome-free/css/all.css) 18:37-76

Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\bulma\css\bulma.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\jquery-datetimepicker\jquery.datetimepicker.css: 1 asset Entrypoint mini-css-extract-plugin = * 2 modules Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\node_modules\sass-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\dark.scss: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./src/css/dark.scss 9.89 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\admin.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/admin.css 2.83 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\blog.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/blog.css 5.03 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\guide.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/guide.css 3.99 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\main.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/main.css 107 KiB {0} [built] [3] ./src/fonts/metropolis-regular-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [4] ./src/fonts/metropolis-regular-webfont.woff 284 bytes {0} [built] [failed] [1 error] [5] ./src/fonts/metropolis-bold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [6] ./src/fonts/metropolis-bold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [7] ./src/fonts/metropolis-extrabold-webfont.woff2 284 bytes {0} [built] [failed] [1 error] [8] ./src/fonts/metropolis-extrabold-webfont.woff 284 bytes {0} [built] [failed] [1 error] [9] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 271 bytes {0} [built] [failed] [1 error] [10] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 284 bytes {0} [built] [failed] [1 error] [11] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 284 bytes {0} [built] [failed] [1 error] [12] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 284 bytes {0} [built] [failed] [1 error] [13] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 424 bytes {0} [built] [failed] [1 error] [14] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 281 bytes {0} [built] [failed] [1 error] [15] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 284 bytes {0} [built] [failed] [1 error] [16] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 284 bytes {0} [built] [failed] [1 error] + 24 hidden modules

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 13:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 18:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 23:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 28:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 33:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 38:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 20:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 30:37-106

ERROR in ./src/fonts/metropolis-regular-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 4:36-88

ERROR in ./src/fonts/metropolis-regular-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 5:36-87

ERROR in ./src/fonts/metropolis-bold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 6:36-85

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 8:36-90

ERROR in ./src/fonts/metropolis-bold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 7:36-84

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 9:36-89

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 11:36-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 12:36-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 16:37-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 17:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 21:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 22:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 26:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 27:37-105

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 31:37-108

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 32:37-107

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 36:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 37:37-103

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.eot 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 35:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 15:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.eot 1:0
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 25:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 10:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 14:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 19:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 24:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 29:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 34:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 39:37-102

Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\profile.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/profile.css 4.18 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\project.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/project.css 11.7 KiB {0} [built] + 1 hidden module Child mini-css-extract-plugin ../../../Open Source\sagan\sagan-client\node_modules\css-loader\dist\cjs.js!../../../Open Source\sagan\sagan-client\src\css\team.css: 1 asset Entrypoint mini-css-extract-plugin = * [0] ./node_modules/css-loader/dist/cjs.js!./src/css/team.css 2.06 KiB {0} [built] + 1 hidden module npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! sagan@ build: webpack npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the sagan@ build 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! C:\Users\AMOL\AppData\Roaming\npm-cache_logs\2020-09-20T11_21_04_817Z-debug.log

Task :sagan-client:npm_run_build FAILED

FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ':sagan-client:npm_run_build'.

Process 'command 'C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2

  • Try: Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':sagan-client:npm_run_build'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:205) at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:263) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:203) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:184) at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:114) at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46) at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36) at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77) at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55) at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52) at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416) at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406) at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158) at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36) at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52) at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41) at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372) at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359) at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352) at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338) at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127) at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191) at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182) at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) Caused by: org.gradle.process.internal.ExecException: Process 'command 'C:\Open Source\sagan\sagan-client.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2 at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:417) at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38) at org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:156) at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1147) at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1142) at org.gradle.api.Project$exec$5.call(Unknown Source) at com.moowork.gradle.node.exec.ExecRunner.run(ExecRunner.groovy:59) at com.moowork.gradle.node.npm.NpmExecRunner.doExecute(NpmExecRunner.groovy:37) at com.moowork.gradle.node.exec.ExecRunner.execute(ExecRunner.groovy:108) at com.moowork.gradle.node.exec.ExecRunner$execute.call(Unknown Source) at com.moowork.gradle.node.npm.NpmTask.exec(NpmTask.groovy:94) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104) at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:49) at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:42) at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:727) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:694) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:568) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394) at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:553) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:536) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$300(ExecuteActionsTaskExecuter.java:109) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:276) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:265) at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:33) at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:33) at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26) at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:67) at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:36) at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:49) at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:34) at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:43) at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73) at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54) at org.gradle.internal.execution.steps.CatchExceptionStep.execute(CatchExceptionStep.java:34) at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:44) at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:54) at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:38) at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:49) at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:159) at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:72) at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:43) at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:44) at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:33) at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38) at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24) at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:92) at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:85) at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55) at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39) at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76) at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37) at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36) at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26) at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:94) at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:49) at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:79) at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:53) at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74) at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:78) at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:78) at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34) at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:39) at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:40) at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:28) at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:192) ... 30 more

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 36s 5 actionable tasks: 3 executed, 2 up-to-date

C:\Open Source\sagan>

C:\Open Source\sagan>

closed time in 5 days

amol1234567

issue commentspring-io/sagan

FAILURE: Build failed with an exception.

Duplicates #995

amol1234567

comment created time in 5 days

issue commentspring-io/sagan

Ubuntu build error with following message

@suvDev yes, see https://github.com/spring-io/sagan/wiki

dotku

comment created time in 6 days

startedgraphql/graphql-over-http

started time in 8 days

issue commentspring-projects/spring-framework

SpringBoot Error w/SecurityManager and AllPermission

Hi @spoofzu

There are several ways to achieve something like this; it really depends on your deployment model and how developers are supposed to use this library with their application.

If they're meant to integrate it at build time, you could ask them to add that dependency to their build file, and even consider building a specific Spring Boot Starter (with configuration properties and more features).

If your product should be used on an already packed archive, you could use the PropertiesLauncher instead of the JarLauncher and add a custom entry for your jar. There are also ways to unpack an existing application and run it with additional dependencies (see this docker + Spring Boot tutorial) - just note that classpath ordering can be lost if you go with a wildcard classpath, as explained in that tutorial.

Finally, if your product is meant to be deployed as an agent (or something close to that), you could take a look at Cloud Native Buildpacks and Paketo. Paketo has buildpacks implementations that do change the classpath or attach an agent to the application, while building the container image. This makes an even better experience if you want this to be included in the CI pipeline automatically.

Thanks!

spoofzu

comment created time in 8 days

push eventspring-projects/spring-framework

Brian Clozel

commit sha 5f587faffae7e18faa49056981a395cc38335642

Update CI to JDK 15 GA

view details

push time in 8 days

push eventspring-projects-experimental/spring-graphql

Brian Clozel

commit sha 39e22eb81ab678a1130daa5580b552588656d7d5

Move auto-configurations to web module This commit adds the relevant dependencies to the web module so as to move all auto-configurations to a single place. Starter modules will only ship dependencies as a result.

view details

Brian Clozel

commit sha 1e61beb0a4d6a464dc1af3013ecccd326bf2a7ea

Remove auto-configurations from starter modules

view details

Brian Clozel

commit sha 54ec20c51027c7b81097098fea1eb294a8b5ed5e

Switch back interceptor to simple interface

view details

Brian Clozel

commit sha 6040dce0c1051849177dd9871f7b042cc2351924

Update request/response GraphQL classes This commit decouples the HTTP layer from the expected request and response messages expected with GraphQL.

view details

Brian Clozel

commit sha 0d46a98f62dccc0490abc3c0e2ca13f1e07cdc70

Create web stack-specific GraphQL handlers Instead of trying to create a single handler for both reactive and non-reactive implementations, this commit splits the implementations.

view details

Brian Clozel

commit sha 9aff167527d86e8877c6291d1c39898e470ddbb4

Add basic support for core GraphQL auto-configuration

view details

Brian Clozel

commit sha 2693742b63bbe0d71c406a85b3f038a0c387a684

Add GraphQL web support This commit removes the controller components and instead moves the web support to specific auto-configurations. This commit also adds tests for both web stacks.

view details

push time in 9 days

issue closedspring-projects/spring-framework

SpringBoot Error w/SecurityManager and AllPermission

Affects: \v5.2.0.RELEASE

Running with Spring Boot v2.2.0.RELEASE, Spring v5.2.0.RELEASE

I have been working on getting webgoat to run with springboot with a securitymanager. To minimize likelihood of user coding problems on my part, I'm using java.lang.SecurityManager as the test. I am running with the following policies,

grant { 
  permission java.security.AllPermission;
  permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};

With SecurityManager enabled and the previous policies, no access control checks should fail. Following is the command line I use to execute springboot with webgoat.

java -classpath ./webgoat-server-8.0.0.M26.jar:./JVMXRay-0.0.1-SNAPSHOT.jar -Djava.security.manager=java.lang.SecurityManager -Djava.security.policy==/Users/milton/zwebgoat/nulljava.policy org.springframework.boot.loader.JarLauncher --server.port=8080 --server.address=localhost

The problem is that org.owasp.webgoat.HSQLDBDatabaseConfig is not found and server exists. However, if remove the SecurityManager and policy file from the command line the server starts as expected. The expected behavior with SecurityManager and the AllPermission policies should be the same as no SecurityManager. I reviewed some of the code near,

org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1465

I noticed that a different classloader may be used depending on whether springboot is initialized with a SecurityManager or not, regardless of policy settings. That's about as far as I got in the code. I checked to see if I could identify a SecurityManager unit test where this code path is exercised but didn't notice anything. I reviewed the next and other bug submissions to the spring project but didn't notice anything similar. I'm hope this information is helpful.

-----FULL STACKTRACE FOLLOWS------

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-02-18 19:36:33.199 ERROR 38449 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanDefinitionStoreException: Failed to read candidate component class: URL [jar:file:/Users/milton/zwebgoat/webgoat-server-8.0.0.M26.jar!/BOOT-INF/classes!/org/owasp/webgoat/StartWebGoat.class]; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.owasp.webgoat.HSQLDBDatabaseConfig] for bean with name 'HSQLDBDatabaseConfig' defined in URL [jar:file:/Users/milton/zwebgoat/webgoat-server-8.0.0.M26.jar!/BOOT-INF/classes!/org/owasp/webgoat/HSQLDBDatabaseConfig.class]; nested exception is java.lang.ClassNotFoundException: org.owasp.webgoat.HSQLDBDatabaseConfig
	at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.scanCandidateComponents(ClassPathScanningCandidateComponentProvider.java:454) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:316) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.boot.context.properties.ConfigurationPropertiesScanRegistrar.scan(ConfigurationPropertiesScanRegistrar.java:83) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.context.properties.ConfigurationPropertiesScanRegistrar.registerBeanDefinitions(ConfigurationPropertiesScanRegistrar.java:60) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.context.annotation.ImportBeanDefinitionRegistrar.registerBeanDefinitions(ImportBeanDefinitionRegistrar.java:86) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.lambda$loadBeanDefinitionsFromRegistrars$1(ConfigurationClassBeanDefinitionReader.java:385) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) ~[na:na]
	at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromRegistrars(ConfigurationClassBeanDefinitionReader.java:384) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:148) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:120) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:337) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:242) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:275) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:95) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:706) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:532) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.owasp.webgoat.StartWebGoat.main(StartWebGoat.java:47) ~[classes!/:8.0.0.M26]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:567) ~[na:na]
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) ~[webgoat-server-8.0.0.M26.jar:8.0.0.M26]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) ~[webgoat-server-8.0.0.M26.jar:8.0.0.M26]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) ~[webgoat-server-8.0.0.M26.jar:8.0.0.M26]
	at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) ~[webgoat-server-8.0.0.M26.jar:8.0.0.M26]
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.owasp.webgoat.HSQLDBDatabaseConfig] for bean with name 'HSQLDBDatabaseConfig' defined in URL [jar:file:/Users/milton/zwebgoat/webgoat-server-8.0.0.M26.jar!/BOOT-INF/classes!/org/owasp/webgoat/HSQLDBDatabaseConfig.class]; nested exception is java.lang.ClassNotFoundException: org.owasp.webgoat.HSQLDBDatabaseConfig
	at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1474) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.determineTargetType(AbstractAutowireCapableBeanFactory.java:682) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:649) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1605) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doGetBeanNamesForType(DefaultListableBeanFactory.java:520) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:491) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:613) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:605) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.boot.context.TypeExcludeFilter.getDelegates(TypeExcludeFilter.java:77) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.boot.context.TypeExcludeFilter.match(TypeExcludeFilter.java:65) ~[spring-boot-2.2.0.RELEASE.jar!/:2.2.0.RELEASE]
	at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.isCandidateComponent(ClassPathScanningCandidateComponentProvider.java:492) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.scanCandidateComponents(ClassPathScanningCandidateComponentProvider.java:431) ~[spring-context-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	... 30 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.owasp.webgoat.HSQLDBDatabaseConfig
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:436) ~[na:na]
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588) ~[na:na]
	at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:92) ~[webgoat-server-8.0.0.M26.jar:8.0.0.M26]
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[na:na]
	at java.base/java.lang.Class.forName0(Native Method) ~[na:na]
	at java.base/java.lang.Class.forName(Class.java:415) ~[na:na]
	at org.springframework.util.ClassUtils.forName(ClassUtils.java:277) ~[spring-core-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:456) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doResolveBeanClass(AbstractBeanFactory.java:1542) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$resolveBeanClass$5(AbstractBeanFactory.java:1466) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:688) ~[na:na]
	at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1465) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
	... 41 common frames omitted

closed time in 9 days

spoofzu

issue commentspring-projects/spring-framework

SpringBoot Error w/SecurityManager and AllPermission

Hi @spoofzu

I believe, it's the other way around - by launching your application like this, you've chosen to deviate from the jar launcher which is using a specific class loader for loading resources from the executable jar.

Allowing this use case was considered but declined in the end, see the conversation on the Spring Boot issue tracker. You can however enable the security manager by calling something like System.setSecurityManager(new SecurityManager()); in the main application method.

If you feel that this is a missing use case from webgoat (using a security manager with their app), you can reach out to them for such an improvement. Just note that supporting that from the command line with the system classloader is not going to work because of the issue I've linked to.

I'm closing this issue since it's not related to Spring Framework. Thanks!

spoofzu

comment created time in 9 days

issue commentspring-projects/spring-boot

high memory usage for spring boot Path variable api

Unlike your previous report, I'm not seeing Tomcat CachedResource entries in the "biggest objects" tab, nor any evidence of memory leak. Could you elaborate on where the leak is in this case?

I ran a local benchmark as well and could not find any leak.

To make sure there's a memory leak, could you run your benchmark, then once it's done force a GC with the profiler and take a memory snapshot. If the heap looks fine and the snapshot doesn't show any problem, this just means that the application is creating short-lived objects and that they'll be collected by the GC. This is not a memory leak but standard JVM behavior given the memory it's been allocated.

rahulsingh336

comment created time in 9 days

issue closedspring-projects/spring-boot

high memory usage for spring boot Path variable api

We have created one microservice with single endpoint. This api consist of single path variable and it is just returning OK response. In real time, it will have different processing mechanism but for testing and POC purpose we have kept it simple. Now, When we generate load with jmeter for this particular api and pass in random path variable values using random variable in jmeter then we have observed that memory is constantly increasing over a period of time and objects are not getting GC.

spring boot version:- 2.3.1 RELEASE dependencies:- spring-boot-starter-web, spring-boot-starter-security, spring-boot-starter-actuator

Sample api:- /app/ping/{id} GET

Jmeter :- path = /app/ping/${random_var} - random_var having value in between 1 - 100000 Number of Threads:- 60 Ramp Up Seconds:- 1 Loop Count:- Forever Spring boot app configuration:- -Xmx150m Heap Dump:- Attached VisvualVM screenshot:- Attached

Leak Suspect: Attached

image

heapdump-1600192132939_Leak_Suspects.zip

heapdump-1600192132939.zip

image

Please let me know If I am missing something.

closed time in 9 days

rahulsingh336

issue commentspring-projects/spring-boot

high memory usage for spring boot Path variable api

Sorry about the spring-boot-starter-parent note, you're right.

Unfortunately 1.5.18.RELEASE is not maintained anymore, so I'm closing this issue - if you can reproduce this on a supported version we'd be happy to take a look. For what it's worth, those objects should not leak as they have a TTL associated with them and they should be collected by the GC.

Thanks!

rahulsingh336

comment created time in 9 days

issue commentspring-projects/spring-boot

high memory usage for spring boot Path variable api

Are you sure this is the right application?

The application you've sent doesn't build because the POM is broken (it's importing spring-boot-starter-parent instead of spring-boot-parent) and it's also using 1.5.18.RELEASE, which is not maintained anymore.

I've fixed the POM and changed the version to 2.3.1 RELEASE (the version noted in your original report) and I can't reproduce the behavior here. I'm running a lot of requests on that endpoint, as explained in your report and yourkit doesn't event show the cached entries in the object explorer.

Could you check again your sample app and make sure that you're running Yourkit against the actual sample and not some other deployed application?

rahulsingh336

comment created time in 10 days

issue commentspring-projects/spring-boot

high memory usage for spring boot Path variable api

Could you share your sample application?

I'm seeing a lot of ConcurrentHashMap$Node instances held by Tomcat CachedResource entries.

image

Requests to Spring endpoints should not create such cache entries - those are usually only linked to static resources served by Tomcat.

rahulsingh336

comment created time in 10 days

issue closedspring-projects/spring-boot

Reactor bom dependency broken for spring boot 2.4.0-SNAPSHOT

<!-- Thanks for raising a Spring Boot issue. Please take the time to review the following categories as some of them do not apply here.

🙅 "Please DO NOT Raise an Issue" Cases

  • Question STOP!! Please ask questions about how to use something, or to understand why something isn't working as you expect it to, on Stack Overflow using the spring-boot tag.
  • Security Vulnerability STOP!! Please don't raise security vulnerabilities here. Head over to https://pivotal.io/security to learn how to disclose them responsibly.
  • Managed Dependency Upgrade You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
  • With an Immediate Pull Request An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details) Please provide details of the problem, including the version of Spring Boot that you are using. If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details) Please start by describing the problem that you are trying to solve. There may already be a solution, or there may be a way to solve it that you hadn't considered.

TIP: You can always edit your issue if it isn't formatted correctly. See https://guides.github.com/features/mastering-markdown --> Reactor bom dependency broken for spring boot 2.4.0-SNAPSHOT (https://repo.spring.io/snapshot/org/springframework/boot/spring-boot-dependencies/2.4.0-SNAPSHOT/spring-boot-dependencies-2.4.0-20200915.133154-449.pom)

<reactor-bom.version>2020.0.0-RC1</reactor-bom.version>

Getting the below error -

Could not resolve: org.springframework.boot:spring-boot-starter-data-jpa Could not resolve: org.springframework.boot:spring-boot-starter-mail Could not resolve: org.springframework.boot:spring-boot-starter-quartz Could not resolve: org.springframework.boot:spring-boot-starter-validation Could not resolve: org.springframework.boot:spring-boot-starter-log4j2 Could not resolve: org.springframework.boot:spring-boot-starter-jetty Could not resolve: org.springframework.boot:spring-boot-starter-web Could not resolve: org.springframework.session:spring-session-core

Attached the build.gradle file

build.gradle.zip

closed time in 10 days

arixion

issue commentspring-projects/spring-boot

Reactor bom dependency broken for spring boot 2.4.0-SNAPSHOT

All SNAPSHOT versions can also depend on MILESTONE versions (here, Reactor or Spring Framework) so this is the expected behavior, at least with the way we're organizing our artifact repositories right now.

In doubt, you can always generate a project on start.spring.io (or just explore it really) and check things out.

Thanks!

arixion

comment created time in 10 days

issue commentspring-projects/spring-boot

Reactor bom dependency broken for spring boot 2.4.0-SNAPSHOT

Maybe a missing repository definition for maven { url 'https://repo.spring.io/milestone' } in your settings.gradle file? Could you look at a freshly generated project on start.spring.io to check for issues in your build?

If this doesn't solve the issue, please provide a sample project that reproduces the problem.

Thanks!

arixion

comment created time in 10 days

issue closedspring-projects/spring-framework

StringHttpMessageConverter may trigger humongous allocations (G1GC)

Affects: 5.2.7.RELEASE


<!-- Thanks for taking the time to create an issue. Please read the following:

  • Questions should be asked on Stack Overflow.
  • For bugs, specify affected versions and explain what you are trying to do.
  • For enhancements, provide context and describe the problem.

Issue or Pull Request? Create only one, not both. GitHub treats them as the same. If unsure, start with an issue, and if you submit a pull request later, the issue will be closed as superseded. -->

I come from spring-projects/spring-boot#21308, where I noticed that Spring related code is triggering humongous allocations (g1GC). Part of these are related to Spring Boot actuators. But others are triggered by WebMVC code. This is causing regular unresponsiveness in the application(s) (pauses up-to ~100ms).

image

image

I can share the flamegraph privately as there are other private flames triggering humongous allocations.

closed time in 10 days

bric3

issue commentspring-projects/spring-framework

StringHttpMessageConverter may trigger humongous allocations (G1GC)

I can't think of anything we could improve here in Spring Framework. We're basically creating a writer with the response output and writing the incoming String to it.

At that point, the allocation is already done (even if further allocation can be done by OutputStreamWriter). I think improving the approach in Spring Boot is the best course of action.

Feel free to reopen this issue if you've got ideas about possible StringHttpMessageConverter improvements.

bric3

comment created time in 10 days

issue commentspring-projects/spring-framework

StringHttpMessageConverter may trigger humongous allocations (G1GC)

@bric3 Your last comment seems to be unrelated to the issue here, besides that the 100ms pauses might be linked to some other parts of your application or GC configuration. Could we circle back on the StringHttpMessageConverter?

Do you have an idea about the size of the String provided to the converter? Is there something we can do here in Spring Framework to improve the situation?

bric3

comment created time in 10 days

push eventbclozel/spring-graphql

Brian Clozel

commit sha b39f12ed4ee067d0e698254f63aee0ba65678fe9

Refactor Gradle build This commit refactors the Gradle build with the following: * use of the dependency management plugin * import the Spring Boot BOM for dependency management * add support for publishing artifacts

view details

Brian Clozel

commit sha a44c836fc0d10854c2a4b74e7226de54e42a4acf

Merge modules This commit merges the common, webmvc and webflux modules into a single web module for supporting GraphQL with all Spring web frameworks. We're working here with optional dependencies to build the support for Spring MVC on one side and Spring WebFlux on the other. Also, this commit updates the starter modules to adopt the official naming convention. For now, starter modules will host both the configuration infrastructure and the transitive dependencies to activate support.

view details

Brian Clozel

commit sha 3e2a601af0fcfd9f99dd764fa8bc5a38b8b9fc94

Move auto-configuration classes to Spring Boot namespace

view details

push time in 10 days

push eventspring-projects-experimental/spring-graphql

Brian Clozel

commit sha b39f12ed4ee067d0e698254f63aee0ba65678fe9

Refactor Gradle build This commit refactors the Gradle build with the following: * use of the dependency management plugin * import the Spring Boot BOM for dependency management * add support for publishing artifacts

view details

Brian Clozel

commit sha a44c836fc0d10854c2a4b74e7226de54e42a4acf

Merge modules This commit merges the common, webmvc and webflux modules into a single web module for supporting GraphQL with all Spring web frameworks. We're working here with optional dependencies to build the support for Spring MVC on one side and Spring WebFlux on the other. Also, this commit updates the starter modules to adopt the official naming convention. For now, starter modules will host both the configuration infrastructure and the transitive dependencies to activate support.

view details

Brian Clozel

commit sha 3e2a601af0fcfd9f99dd764fa8bc5a38b8b9fc94

Move auto-configuration classes to Spring Boot namespace

view details

push time in 10 days

push eventspring-projects-experimental/spring-graphql

Brian Clozel

commit sha e39567e6f73038d83935b76b21eaaf1508c16836

Move auto-configuration classes to Spring Boot namespace

view details

push time in 10 days

push eventspring-projects-experimental/spring-graphql

Brian Clozel

commit sha 06f91d0066d09b5ea7c91cc61b733cc7d90abc0b

Refactor Gradle build This commit refactors the Gradle build with the following: * use of the dependency management plugin * import the Spring Boot BOM for dependency management * add support for publishing artifacts

view details

Brian Clozel

commit sha 60641e20f681cace5d5f951873ff69eeb03429b5

Merge modules This commit merges the common, webmvc and webflux modules into a single web module for supporting GraphQL with all Spring web frameworks. We're working here with optional dependencies to build the support for Spring MVC on one side and Spring WebFlux on the other. Also, this commit updates the starter modules to adopt the official naming convention. For now, starter modules will host both the configuration infrastructure and the transitive dependencies to activate support.

view details

push time in 10 days

PR closed tomekzar/quarkus-vs-spring-boot-performance

Fix blocking thread issue on the Webflux variant

Here's a proposal for fixing the odd result you encountered with the Spring Webflux variant during your benchmark.

Using blocking calls within reactive applications is a real problem and leads to performance issues like this one. The commit message here explains a bit why.

Note that some IDEs (for example, IntelliJ IDEA) now show warning messages whenever developers try do this in their application. The Reactor team also provides tools to automatically detect such problems in your entire application (libraries included!): https://github.com/reactor/BlockHound/tree/master/docs

+16 -19

1 comment

2 changed files

bclozel

pr closed time in 10 days

pull request commenttomekzar/quarkus-vs-spring-boot-performance

Fix blocking thread issue on the Webflux variant

Closing in favor of 1e301f8bb6630a75e7b0ef48094de9fb442c485d

bclozel

comment created time in 10 days

PullRequestReviewEvent

Pull request review commenttomekzar/quarkus-vs-spring-boot-performance

Fix blocking thread issue on the Webflux variant

 package com.cogrammer.service; +import java.time.Duration;+ import com.cogrammer.dto.Cities; import com.cogrammer.dto.City; import com.cogrammer.dto.Message; import com.cogrammer.repository.CityRepository; import lombok.RequiredArgsConstructor;-import org.springframework.stereotype.Service; import reactor.core.publisher.Mono; +import org.springframework.stereotype.Service;+ @Service @RequiredArgsConstructor public class ExampleService { -    private final CityRepository repository;+	private final CityRepository repository; -    public Mono<Message> blockingHello() {-        return Mono.fromSupplier(() -> {-            try {-                Thread.sleep(100);-                return new Message("Hello!");-            } catch (InterruptedException e) {-                throw new RuntimeException(e);-            }-        });-    }+	public Mono<Message> delayedHello() {+		return Mono.just(new Message("Hello!"))

Thanks!

bclozel

comment created time in 10 days

PublicEvent

issue commentspring-projects/spring-boot

Spring boot application.properties "spring.jackson.parser.allow_unquoted_field_names" can not take effect

@fransflippo feel free to point us to an SO question and we can take a look.

xuchang86

comment created time in 10 days

push eventbclozel/asciidoctorj3

Brian Clozel

commit sha e5ca22960741a9fdd338e0a2c5a5919292532f67

Add repro project

view details

push time in 10 days

PR merged spring-projects-experimental/spring-graphql

introduce generic GraphQLHandler

Introduce generic GraphQLHandler in common package which doesn't depend on webflux or webvmc specifics.

+331 -176

0 comment

22 changed files

andimarek

pr closed time in 10 days

push eventspring-projects-experimental/spring-graphql

Andreas Marek

commit sha a37aa740a98ec81096c517e0f647027d64d9160f

introduce common GraphQLHandler which doesn't depend on either webflux or webmvc specifics. Refactor webflux to use the new Handler

view details

Andreas Marek

commit sha f2cf46989b77398ae06ece14d93bc27ebe4ba8cf

Refactor webmvc to use the new Handler

view details

Andreas Marek

commit sha 59214d4c5bc8e0168572b3be9b3ffcf9b01be1e7

add default implementations for Interceptor

view details

Andreas Marek

commit sha 740a3f1f929ed873e965c35c70bf6ae58018ffed

add non nullable package annotations rename GraphQLResponseBody -> GraphQLResponse

view details

Andreas Marek

commit sha 8238353f9a1f8557b1b5b61fb0ef63dab7b686c2

refactor to GraphQLHttpRequest and GraphQLHttpResponse and added params map

view details

Andreas Marek

commit sha a7cf5b6d558a63191c6529bec8cc14f6bd430352

pass params to interceptor

view details

Andreas Marek

commit sha 7bc8cea8ed608ddb19050f2ba2c9af08cb16eea1

add http headers for the response

view details

Andreas Marek

commit sha 5741e3f4bc6e768eb58686ce632bc95c1ca0cb62

refactoring

view details

push time in 10 days

push eventbclozel/spring-graphql

Andreas Marek

commit sha a37aa740a98ec81096c517e0f647027d64d9160f

introduce common GraphQLHandler which doesn't depend on either webflux or webmvc specifics. Refactor webflux to use the new Handler

view details

Andreas Marek

commit sha f2cf46989b77398ae06ece14d93bc27ebe4ba8cf

Refactor webmvc to use the new Handler

view details

Andreas Marek

commit sha 59214d4c5bc8e0168572b3be9b3ffcf9b01be1e7

add default implementations for Interceptor

view details

Andreas Marek

commit sha 740a3f1f929ed873e965c35c70bf6ae58018ffed

add non nullable package annotations rename GraphQLResponseBody -> GraphQLResponse

view details

Andreas Marek

commit sha 8238353f9a1f8557b1b5b61fb0ef63dab7b686c2

refactor to GraphQLHttpRequest and GraphQLHttpResponse and added params map

view details

Andreas Marek

commit sha a7cf5b6d558a63191c6529bec8cc14f6bd430352

pass params to interceptor

view details

Andreas Marek

commit sha 7bc8cea8ed608ddb19050f2ba2c9af08cb16eea1

add http headers for the response

view details

Andreas Marek

commit sha 5741e3f4bc6e768eb58686ce632bc95c1ca0cb62

refactoring

view details

push time in 10 days

issue closedspring-projects/spring-framework

WebClient/MockMVC issue with jquery ajax post

Hello,

i am using htmlunit with spring test in order to test all ihm interface from my web application. It works fine with html form (post and get) and with ajax get but i have a problem with ajax post request.

The controller don't received the request. If i replace post by get the junit test case works fine.

this the html view

<!DOCTYPE html>
<html lang="fr" xmlns="http://www.w3.org/1999/xhtml" 
	xmlns:th="http://www.thymeleaf.org">
	<head>
		<title>Spring Html Unit</title>
        <meta charset="utf-8" />
		<meta name="format-detection" content="telephone=no">
		<meta name="viewport" content="width=device-width, initial-scale=1.0">
		<script src="https://code.jquery.com/jquery-3.5.1.min.js" integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" crossorigin="anonymous"></script>
		<script>
			function postTest() {
				$.ajax({
			        type:"post",
					data: {
						'subject' : 'subject test',
						'message' : 'message test'
					},
			        url:"[[@{/test/post}]]",
			        success: function(data, textStatus, jqXHR){
			        	$("#result").text(data);
			        }
			    });
			}		
		</script>
	</head>
	<body>
		<h4 th:text="'Hello to Thymeleaf '+${myParam}">Hello from Thymeleaf</h4>
		
		<button type="button" onClick="postTest()">Test post</button>
		<div>
			<span>result :</span><span id="result"></span>
		</div>
		
	</body>
</html>

and the controller


@Controller
public class WelcomeController {

	@GetMapping("/")
	public String init(Model model) {
		model.addAttribute("myParam", "Guillaume");
		return "welcome";
	}

	@PostMapping("/test/post")
	public @ResponseBody String post(@RequestParam String subject, @RequestParam String message, Model model) {
		return subject + " " + message;
	}
}

you can also find the complete code on my github https://github.com/guisimon28/spring-test-htmlunit

Can you help me to find if there is some missing configuration or if its a htmlunig bug or pull request ?

Thanks for All

Guillaume

closed time in 11 days

guisimon28

issue commentspring-projects/spring-framework

WebClient/MockMVC issue with jquery ajax post

Thanks for getting in touch, but it feels like this is a question that would be better suited to StackOverflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.

The sample you've provided doesn't use Spring Boot - I'd suggest to use Spring Boot instead to dramatically reduce the amount of boilerplate.

Also there seems to be a confusion around your usage of jQuery. Right now it's sending the form as a POST, but with an urlencoded request body. You should either switch to GET or send the body as "multipart/form-data" and use a JavaScript FormData object.

Even better, you could look into the getting started guides for Spring Boot. See https://spring.io/guides/gs/handling-form-submission/

Thanks!

guisimon28

comment created time in 11 days

create barnchbclozel/spring-graphql

branch : build

created branch time in 11 days

fork bclozel/spring-graphql

Incubator for Spring Boot GraphQL support

fork in 11 days

CommitCommentEvent
CommitCommentEvent
CommitCommentEvent

create barnchbclozel/spring-framework

branch : asciidoctorj3

created branch time in 12 days

push eventspring-projects/spring-framework

Brian Clozel

commit sha b2a0978c129856804e0ae82e676f65616a2ea5ef

Prepare for Sinks API updates in Reactor See reactor/reactor-core#2374 All usages of this API are in tests, which are not checking overflow or concurrent emissions - so a simple replacement with `try***` equivalents is fine.

view details

push time in 14 days

push eventspring-projects/spring-framework

Brian Clozel

commit sha b61d0584a9f3d2fdf63f6d0684867fdf72225da9

Update after RSocket SNAPSHOT changes

view details

Brian Clozel

commit sha 8473f71a42a61811b2830068f1025127d5df0526

Update JDK 15 version in CI image This also switches to the adoptopenjdk-produced binaries for better consistency with other JDK versions in our CI.

view details

push time in 14 days

issue commentspring-projects/spring-boot

Allow RSocket transport customization

Right!

@srinivasvsk

In the meantime, you can declare an RSocketServerCustomizer in your Spring Boot application like this:

@Configuration(proxyBeanMethods = false)
public class RSocketConfig {

  @Bean
  public RSocketServerCustomizer fragmentationCustomizer() {
    return (server) -> server.fragment(16384); // use a non-zero value that tells the server to fragment messages at this size
    // you should use a value that's not too small to avoid overhead, but not larger than the `65536` websocket max frame size
  }

}
srinivasvsk

comment created time in 14 days

issue commentspring-projects/spring-boot

Improve sanitization for list of URI types

Thanks for your first contribution @helloworldless - I took your commit and just simplified it a bit.

I think this first-timer issue was more subtle than expected, but the fix looks right. I ended up removing the more complex parts about matching array-like keys, because I think there was a confusion about that. The Sanitizer is only involved in the Actuator endpoints, when iterating on the parsed PropertySource instances; so the Sanitizer is never looking at the properties/yaml syntax, but rather the parsed representation of keys ("[http://user1:password1@localhost:8080,http://user2:password2@localhost:8082]" being the string representation of a list here).

This is now merged in 2.2.x and merged-forward in later branches.

crmky

comment created time in 14 days

PR closed spring-projects/spring-boot

Sanitize entire value if property is not of URI type; Fixes gh-23037 status: waiting-for-triage

Handles case where a property has a uri/address key but the value is not matched against the value regex. In this case, we now sanitize the value.

+11 -1

1 comment

2 changed files

helloworldless

pr closed time in 14 days

pull request commentspring-projects/spring-boot

Sanitize entire value if property is not of URI type; Fixes gh-23037

Closing in favor of the fix variant committed in gh-23037. Thanks!

helloworldless

comment created time in 14 days

push eventspring-projects/spring-boot

David Good

commit sha 775f0fa8613c5360bac2159f4c45089733049587

Improve sanitization for list of URI types Prior to this commit, Actuator would sanitize properties values when serializing them on the dedicated endpoint. Keys like "password" or "secret" are entirely sanitized, but other keys like "uri" or "address" are considered as URI types and only the password part of the user info is sanitized. This commit fixes the sanitization process where lists of such URI types would not match the first entries of the list since they're starting with `'['`. This commit improves the regexp matching process to sanitize all URIs within a collection. The documentation is also updated to better underline the processing difference between complete sanitization and selective sanitization for URIs. Fixes gh-23037

view details

Brian Clozel

commit sha 62cb87bd9542b3cb9a30fdcf1841393155ba07e8

Merge branch '2.2.x' into 2.3.x Closes gh-23252

view details

Brian Clozel

commit sha 20eb8d0fc22dbd84e392a50a305c6bbbf7efb21d

Merge branch '2.3.x' Closes gh-23253

view details

push time in 14 days

issue closedspring-projects/spring-boot

Improve sanitization for list of URI types

Forward port of issue #23252 to 2.4.x.

closed time in 14 days

bclozel

issue closedspring-projects/spring-boot

Improve sanitization for list of URI types

Forward port of issue #23037 to 2.3.x.

closed time in 14 days

bclozel

push eventspring-projects/spring-boot

David Good

commit sha 775f0fa8613c5360bac2159f4c45089733049587

Improve sanitization for list of URI types Prior to this commit, Actuator would sanitize properties values when serializing them on the dedicated endpoint. Keys like "password" or "secret" are entirely sanitized, but other keys like "uri" or "address" are considered as URI types and only the password part of the user info is sanitized. This commit fixes the sanitization process where lists of such URI types would not match the first entries of the list since they're starting with `'['`. This commit improves the regexp matching process to sanitize all URIs within a collection. The documentation is also updated to better underline the processing difference between complete sanitization and selective sanitization for URIs. Fixes gh-23037

view details

Brian Clozel

commit sha 62cb87bd9542b3cb9a30fdcf1841393155ba07e8

Merge branch '2.2.x' into 2.3.x Closes gh-23252

view details

push time in 14 days

issue closedspring-projects/spring-boot

Improve sanitization for list of URI types

Problem

I'm using Spring Boot 2.2.9. The change introduced by https://github.com/spring-projects/spring-boot/pull/19999 considers any keys contains "uri", "uris", "address" or "addresses" are "comma separated URLs". This is not always the right assumption. It will try to remove password from those URLs, however if it's not a URL format, it will return the original content.

Expected Behavior

If that key is not a URL format, it should return as ******. Or at least allow developers to configure whether they want sanitize URLs or not.

Reproducer

Sanitizer sanitizer = new Sanitizer();
System.out.println(sanitizer.sanitize("uris", "[amqp://foo:bar@host/]"));
System.out.println(sanitizer.sanitize("uris", "amqp://foo:bar@host/"));

The output is:

[amqp://foo:bar@host/]
amqp://foo:******@host/

closed time in 14 days

crmky

issue openedspring-projects/spring-boot

Improve sanitization for list of URI types

Forward port of issue #23252 to 2.4.x.

created time in 14 days

issue openedspring-projects/spring-boot

Improve sanitization for list of URI types

Forward port of issue #23037 to 2.3.x.

created time in 14 days

push eventspring-projects/spring-boot

David Good

commit sha 775f0fa8613c5360bac2159f4c45089733049587

Improve sanitization for list of URI types Prior to this commit, Actuator would sanitize properties values when serializing them on the dedicated endpoint. Keys like "password" or "secret" are entirely sanitized, but other keys like "uri" or "address" are considered as URI types and only the password part of the user info is sanitized. This commit fixes the sanitization process where lists of such URI types would not match the first entries of the list since they're starting with `'['`. This commit improves the regexp matching process to sanitize all URIs within a collection. The documentation is also updated to better underline the processing difference between complete sanitization and selective sanitization for URIs. Fixes gh-23037

view details

push time in 14 days

issue closedspring-projects/spring-boot

Spring Reactive WebSocket does not work when Spring Web is present in the classpath.

<!-- Thanks for raising a Spring Boot issue. Please take the time to review the following categories as some of them do not apply here.

🙅 "Please DO NOT Raise an Issue" Cases

  • Question STOP!! Please ask questions about how to use something, or to understand why something isn't working as you expect it to, on Stack Overflow using the spring-boot tag.
  • Security Vulnerability STOP!! Please don't raise security vulnerabilities here. Head over to https://pivotal.io/security to learn how to disclose them responsibly.
  • Managed Dependency Upgrade You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
  • With an Immediate Pull Request An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details) Please provide details of the problem, including the version of Spring Boot that you are using. If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details) Please start by describing the problem that you are trying to solve. There may already be a solution, or there may be a way to solve it that you hadn't considered.

TIP: You can always edit your issue if it isn't formatted correctly. See https://guides.github.com/features/mastering-markdown --> Spring Reactive WebSocket does not work when Spring Web is present in the classpath. For example, pull this sample application https://github.com/faros/reactive-websockets; this sample works on Netty but when I tried to bring this on Tomcat by including spring-boot-starter-web in the pom.xml, the ws:// url started to return 404.

Steps to reproduce:

  1. Download the code: https://github.com/faros/reactive-websockets
  2. Include spring-boot-starter-web in the pom.xml
  3. mvn spring-boot:run
  4. App comes up on Tomcat
  5. try: http://localhost:8080/ on browser with F12 Dev Window on.
  6. Receive the error in the console: GET ws://localhost:8080/stringConverter [HTTP/1.1 404 82ms] Firefox can’t establish a connection to the server at ws://localhost:8080/stringConverter.

Please note that I tried Tomcat update strategy unsuccessfully.

closed time in 14 days

vlaguduva
more