vim-beancount: fix broken

Signed-off-by: Sirio Balmelli<EMAIL_ADDRESS>Motivation for this change
vim-beancount package would fail to invoke autocompletion at runtime with: ModuleNotFoundError: No module named 'beancount'
Things done
Add python3 dependency to vim-beancount override.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been open since 13 May.
Would be great to be able to get it merged and stop tracking and periodically rebasing a separate branch in my repo.
I've gone through CONTIBUTING.md a couple times and if there's something I should be doing to improve this pull request I don't see it.
Any feedback is much appreciated.

diff LGTM, dosrry i didn't get around to it sooner

diff LGTM, sorry i didn't get around to it sooner

No worries - and I notice you handle a lot of the package review for Nix!
That's certainly much appreciated.


Hits but 0 matches

We are using ElastAlert to track the health of our Hadoop tables, like the count of records for each hour.
Here is how my filter looks like:
filter:
- query:
    query_string:
      query: "_type: my_type"
- range:
    count:
      from: 0
      to: 300000

After testing this rule, it will give me 4 hits (which is the correct amount of hours that have 0 ~ 300000 records) but 0 matches. So I am wondering what "hits" and "matches" really tell us. And if my need email alerting, will alerts be sent based on hits or matches? Thanks!
Sorry if this is not the right place to ask questions. If I'm at the wrong place, can anyone drop me a link to where I should post my questions?

Problem solved. 0 match is because of impropriate timeframe.


[request] Move Visit and VisitMut default implementations to another method

The Visit and VisitMut traits are great but there's 1 giant usability issue, and that is that each method defines its own implementation.
Now why is this a problem? Well, if I implement my own visitor and override a method, I lost the default implementation, and there's no easy way (besides dynamic dispatch below) to reuse the implementation, so I end up copying and pasting a bunch of code. For example, say I have my own visitor that needs to do something with Program, I would do this:
pub struct Example<'a>;

impl<'a> Visit<'a> for Example<'a> {
    fn visit_program(&mut self, program: &Program<'a>) {
        for stmt in &program.body {
            // Do something here
        }
    }
}

But I still want the visitor to work correctly, so then I have to copy the default code like so:
pub struct Example<'a>;

impl<'a> Visit<'a> for Example<'a> {
    fn visit_program(&mut self, program: &Program<'a>) {
        for stmt in &program.body {
            // Do something here
        }

        // Default
        let kind = AstKind::Program(self.alloc(program));
        self.enter_scope({
            let mut flags = ScopeFlags::Top;
            if program.is_strict() {
                flags |= ScopeFlags::StrictMode;
            }
            flags
        });
        self.enter_node(kind);
        for directive in &program.directives {
            self.visit_directive(directive);
        }
        self.visit_statements(&program.body);
        self.leave_node(kind);
        self.leave_scope();
    }
}

You can sort of work around this be using dynamic dispatch, like the following.
pub struct Example<'a>;

impl<'a> Visit<'a> for Example<'a> {
    fn visit_program(&mut self, program: &Program<'a>) {
        for stmt in &program.body {
            // Do something here
        }

        // Default
        Visit::visit_program(self, program);
    }
}

This works for some methods, but causes warnings for others. A warning I see often is "function cannot return without recursing". I'm not sure if this actually causes problems though.
Regardless, I have a suggestion here. Instead of defining a default implementation for methods, why not define another method like do_visit_program that has the implementation, and then update visit_program to call do_visit_program. That way, when the method is overridden, we can still call it normally.
For example:
// Before
pub trait Visit<'a>: Sized {
    fn visit_program(&mut self, program: &Program<'a>) {
        let kind = AstKind::Program(self.alloc(program));
        self.enter_scope({
            let mut flags = ScopeFlags::Top;
            if program.is_strict() {
                flags |= ScopeFlags::StrictMode;
            }
            flags
        });
        self.enter_node(kind);
        for directive in &program.directives {
            self.visit_directive(directive);
        }
        self.visit_statements(&program.body);
        self.leave_node(kind);
        self.leave_scope();
    }
}

// After
pub trait Visit<'a>: Sized {
    fn do_visit_program(&mut self, program: &Program<'a>) {
        let kind = AstKind::Program(self.alloc(program));
        self.enter_scope({
            let mut flags = ScopeFlags::Top;
            if program.is_strict() {
                flags |= ScopeFlags::StrictMode;
            }
            flags
        });
        self.enter_node(kind);
        for directive in &program.directives {
            self.visit_directive(directive);
        }
        self.visit_statements(&program.body);
        self.leave_node(kind);
        self.leave_scope();
    }

    fn visit_program(&mut self, program: &Program<'a>) {
        self.do_visit_program(program);
    }
}

I had a similar idea before, I need an enter_program and a leave_program method in the transformer
The implementation looks like this
pub trait VisitMut<'a>: Sized {
    fn enter_program(&mut self, program: &mut Program<'a>) {
        // do something
    }
    fn leave_program(&mut self, program: &mut Program<'a>) {
       // after program.body visited, we may need to modify the program.body
    }

    fn visit_program(&mut self, program: &mut Program<'a>) {
        let kind = AstKind::Program(self.alloc(program));
        self.enter_scope({
            let mut flags = ScopeFlags::Top;
            if program.is_strict() {
                flags |= ScopeFlags::StrictMode;
            }
            flags
        });

        // enter here
        self.enter_program(program);

        self.enter_node(kind);
        for directive in &program.directives {
            self.visit_directive(directive);
        }
        self.visit_statements(&mut program.body);

        // leave here
        self.leave_program(program);

        self.leave_node(kind);
        self.leave_scope();
    }
}

This is similar to { visitor: { program() {}, "program:exit"() {} } in babel

Been tinkering around with this more, and the dynamic dispatch approach seems to always trigger a stack overflow.

Try:

use the ModuleRecord data https://github.com/oxc-project/oxc/blob/main/crates/oxc_semantic/src/module_record/builder.rs
use the enter / leave callbacks https://github.com/oxc-project/oxc/blob/8ab667c90ec8e036dc821b48947ca7a097cdd218/crates/oxc_ast/src/visit.rs#L15-L16

This requires a lot of manual work, and given we have some workarounds, I'm going to close this as not planned for now.


Unable to build master

Describe the bug
branch: master
device: macOs, latest rust tools & compiler version
after cloning , when running cargo buildat project root:
error: failed to select a version for the requirement parquet = "^16.0.0"
candidate versions found which didn't match: 15.0.0, 14.0.0, 13.0.0, ...
location searched: crates.io index
required by package datafusion v9.0.0 (https://github.com/apache/arrow-datafusion?rev=0289bfe6a98bdae371eee29d3f257b173ddb4437#0289bfe6)
... which satisfies git dependency datafusion of package ballista-benchmarks v5.0.0 (/Users/ybouraoui/arrow-ballista/benchmarks)

done


Angular 5 peer dependency?

Could  || ^5.0.0 be added to the @angular/core and @angular/http peer dependencies?

Yes!

Added the ng5 peer dependencies in v4.2.6. I'll switch from Http to HttpClient in v5.0.0 in a few days. Thanks.

Awesome :)

v5.0.0 is out with HttpClient.


Add typecheck script

CI now fails if you have a type issue:

Getting lint-staged to do this nicely in pre-commit is evading me, so leaving that out for now.

👨🍳 Pefect.


NFS doesn't work on macs

Because of the way we find ip address info:
https://github.com/jonludlam/vagrant-xenserver/blob/master/lib/vagrant-xenserver/action/prepare_nfs_settings.rb#L45

Fixed, I think


Windows binary release can't find libwinpthread-1.dll

Hello,
I am trying to run the Windows binary of Preview 4.6-dev.
The following error dialog appears:

It seems that MinGW is needed to run the pre-compiled program, not just for compiling. This is a bit odd in my opinion.
The README file could state that Mingw is required for compiling and running rayjs or more ideally, the dependency could be statically compiled into the program if this is possible.

The binary on the releases page is unfortunately not up to date. Did you check this issue https://github.com/mode777/rayjs/issues/2

Sorry, I did not check. I suppose a new release could be made (in the releases tab) so the correct version is easier to find and more people don't report this already fixed issue. :)


Makefile contains targets which can only be built in full source tree

Describe the bug
I tried to build the source tree as is to create a Debian package but failed due to several references to code parts that are not contained in kent-core.  I've written a patch to fix several issues but its not complete yet.
To Reproduce
Steps to reproduce the behavior:

Try make clean to get a first impression what's going on.
Try make to see what's happening.

Expected behavior
Building should be possible without parts of ucscGenomeBrowser/kent that are not (yet) part of kent-core.  The patch I've created should perfectly work inside the full source tree since its always checking whether a directory exists or not (sometimes with make wildcard sometimes with shell if - no idea what you might prefer in the long run thus filling this issue to discuss about next steps.
I stopped here when I was running into:
make[2]: *** No rule to make target '../lib/x86_64/jkOwnLib.a', needed by 'webBlat'.  Stop.
make[2]: Leaving directory '/builds/med-team/kent-core/debian/output/source_dir/src/webBlat'

since I'm wondering whether you might like to consider providing jkOwnLib.a source code with MIT license to be able to build webBlat which is not possible yet.
Desktop (please complete the following information):

OS: Debian

Kind regards, Andreas.

Sorry for the long delay, the problem was that I accidentally had removed the top-level "makefile" which was supposed to solve this. I've added it back now. This new, additional top-level makefile (which doesn't exist in the full kent source tree) runs only "make utils" so non-functional BLAT targets should not be an issue now. I think that's a smaller change than what your patch suggests.
Let me know if you run into another problem, I will get back to you quicker next time.

Well, I confirm that the build goes more smoothly now - but its not true that its just because of the missing makefile.  The clean target remains broken if you test
cd src && make clean

it ends up with
cd lib && make clean
/bin/sh: 1: cd: can't cd to lib

I did not changed the tarball (yet) since it has no tagged release and I can override the build process in debian/rules easily.  However, even in this case the build process fails with
cd blat && make test
/bin/sh: 1: cd: can't cd to blat

I need to admit that our most wanted target is actually blat - may be its license has changed as well but is missing in this archive?
Kind regards, Andreas.

I did not changed the tarball (yet) since it has no tagged release

Sorry can you explain what you mean with "the tarball", and what you mean
with "it"

and I can override the build process in debian/rules easily
https://salsa.debian.org/med-team/kent-core/-/blob/master/debian/rules#L14-L15.

Sorry, I don't know what this sentence means. Does this mean that you don't
need a makefile?

However, even in this case the build process fails
https://salsa.debian.org/med-team/kent-core/-/jobs/4130819 with

Sorry, can you explain what you mean with "in this case" - which case?

Message ID: @.***>

I need to admit that our most wanted target is actually blat

BLAT was written by Jim Kent outside of his UCSC job and he holds the
copyright. BLAT is not under an MIT license, so it is not contained in this
repo. I think you have tried before to convince Jim to give BLAT away for
free, and he rejected it. As far as I know, his opinion has not changed.
On Wed, Apr 12, 2023 at 10:27 PM Maximilian Haeussler @.***>
wrote:

I did not changed the tarball (yet) since it has no tagged release

Sorry can you explain what you mean with "the tarball", and what you mean
with "it"

and I can override the build process in debian/rules easily
https://salsa.debian.org/med-team/kent-core/-/blob/master/debian/rules#L14-L15.

Sorry, I don't know what this sentence means. Does this mean that you
don't need a makefile?

However, even in this case the build process fails
https://salsa.debian.org/med-team/kent-core/-/jobs/4130819 with

Sorry, can you explain what you mean with "in this case" - which case?

Message ID: @.***>

Am Wed, Apr 12, 2023 at 01:28:29PM -0700 schrieb Maximilian Haeussler:

I did not changed the tarball (yet) since it has no tagged release

Sorry can you explain what you mean with "the tarball", and what you mean
with "it"

For the Debian package I fetch a tarball that is created by Github from
a tag.  If there is a new tag, I fetch a new tarball with the version
determined by the tag.

and I can override the build process in debian/rules easily
https://salsa.debian.org/med-team/kent-core/-/blob/master/debian/rules#L14-L15.

Sorry, I don't know what this sentence means. Does this mean that you don't
need a makefile?

A makefile is perfectly welcome since it expresses the explicit way
upstream intends to build the source and gives upstream control over the
build process (which might change from release to release).  In this
specific case where I would have to change a tagged release tarball
which is either by doing not clean or add another patch to the Debian
package which reproduces your commited makefile I decided for the cleaner
approach and added the one liner to the debian/rules file (which is a
makefile as well).
I will remove that one liner from debian/rules once the makefile will
show up inside a tagged release.

However, even in this case the build process fails
https://salsa.debian.org/med-team/kent-core/-/jobs/4130819 with

Sorry, can you explain what you mean with "in this case" - which case?

The "case" when I try to build with the very same statement as in your
makefile.  Did you tried make inside the kent-core repository?  You
should be able to reproduce the result in the linked build log.
Kind regards, Andreas.

Am Wed, Apr 12, 2023 at 01:31:05PM -0700 schrieb Maximilian Haeussler:

I need to admit that our most wanted target is actually blat

BLAT was written by Jim Kent outside of his UCSC job and he holds the
copyright. BLAT is not under an MIT license, so it is not contained in this
repo. I think you have tried before to convince Jim to give BLAT away for
free, and he rejected it. As far as I know, his opinion has not changed.

What is the most straightforward way to ask Kent again?  (Which e-mail
address, issue tracker, whatever is he reading these days?)
Kind regards, Andreas.

You can find his email address on his home page:
https://users.soe.ucsc.edu/~kent/
On Thu, Apr 13, 2023 at 7:44 AM Andreas Tille @.***>
wrote:

Am Wed, Apr 12, 2023 at 01:31:05PM -0700 schrieb Maximilian Haeussler:

I need to admit that our most wanted target is actually blat

BLAT was written by Jim Kent outside of his UCSC job and he holds the
copyright. BLAT is not under an MIT license, so it is not contained in
this
repo. I think you have tried before to convince Jim to give BLAT away for
free, and he rejected it. As far as I know, his opinion has not changed.

What is the most straightforward way to ask Kent again? (Which e-mail
address, issue tracker, whatever is he reading these days?)
Kind regards, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1506378266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TL7QMMWN52FQ3UMTWDXA6HDFANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I did not test "make clean", not sure why that is important when building
on throw-away VMs, but fixed this now. Also added a ton of tools, many
thanks for this comment, it make me realized that the entire src/hg/*
branch was missing. Added now. And tagged as "v447-test". Can you try the
build again?
On Thu, Apr 13, 2023 at 7:44 AM Andreas Tille @.***>
wrote:

Am Wed, Apr 12, 2023 at 01:31:05PM -0700 schrieb Maximilian Haeussler:

I need to admit that our most wanted target is actually blat

BLAT was written by Jim Kent outside of his UCSC job and he holds the
copyright. BLAT is not under an MIT license, so it is not contained in
this
repo. I think you have tried before to convince Jim to give BLAT away for
free, and he rejected it. As far as I know, his opinion has not changed.

What is the most straightforward way to ask Kent again? (Which e-mail
address, issue tracker, whatever is he reading these days?)
Kind regards, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1506378266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TL7QMMWN52FQ3UMTWDXA6HDFANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I did not test "make clean", not sure why that is important when building on throw-away VMs, but fixed this now.

Thanks for fixing this.  To let you understand why make clean is important at least for the Debian packaging:  Its simply part of the build process to start in a clean build directory and packagers should make sure that a package builds from scratch twice in a row which presupposes that make clean works and leaves the build directory in an identical state as unpacking the source tarball.

Also added a ton of tools, many thanks for this comment, it make me realized that the entire src/hg/* branch was missing. Added now. And tagged as "v447-test". Can you try the build again?

I did a test build (without any Debian specific patches).  The build went smoothly until
make[3]: Leaving directory '/build/kent-core-447-test/src/hg/lib'
cd hg/cgilib && /usr/bin/make
/bin/sh: 1: cd: can't cd to hg/cgilib
make[2]: *** [makefile:33: hgLib] Error 2

Feel free to check the full build log in our packaging CI.
Thanks a lot for your cooperation, Andreas.

Oops, sorry, I pushed this change to the wrong repo first. Should be fixed
now. Tag is v447-test2
On Thu, Apr 13, 2023 at 2:47 PM Andreas Tille @.***>
wrote:

I did not test "make clean", not sure why that is important when building
on throw-away VMs, but fixed this now.
Thanks for fixing this. To let you understand why make clean is important
at least for the Debian packaging: Its simply part of the build process to
start in a clean build directory and packagers should make sure that a
package builds from scratch twice in a row which presupposes that make
clean works and leaves the build directory in an identical state as
unpacking the source tarball.
Also added a ton of tools, many thanks for this comment, it make me
realized that the entire src/hg/* branch was missing. Added now. And tagged
as "v447-test". Can you try the build again?
I did a test build (without any Debian specific patches). The build went
smoothly until
make[3]: Leaving directory '/build/kent-core-447-test/src/hg/lib'
cd hg/cgilib && /usr/bin/make
/bin/sh: 1: cd: can't cd to hg/cgilib
make[2]: *** [makefile:33: hgLib] Error 2
Feel free to check the full build log
https://salsa.debian.org/med-team/kent-core/-/jobs/4133336 in our
packaging CI.
Thanks a lot for your cooperation, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1506907332,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TKKSEEALG5NIVCFFPLXA7YXRANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Thanks again for the quick fix.  Feel free to blame me some pretty different patch in my initial Makefile patch.  I had to fix the libssl linking in another patch to enable building in a clean Debian chroot.  I consider your way of linking statically with explicit PATH options for different architectures unusual.  Do you have some specific reason to do so instead of simply using -lssl?
The build now ends (again) in
make[4]: Leaving directory '/build/kent-core-447-test2/src/utils/bedGeneParts'
make[3]: Leaving directory '/build/kent-core-447-test2/src/utils'
cd blat && make test
/bin/sh: 1: cd: can't cd to blat
make[2]: *** [makefile:131: blat.test] Error 2

and you can inspect the full build log here.
Thanks again for your quick response, Andreas.

Am Thu, Apr 13, 2023 at 06:55:41AM -0700 schrieb Maximilian Haeussler:

I can run "make clean" fine in my copy of kent-core.

It works now since your test release.

In your build log,
https://salsa.debian.org/med-team/kent-core/-/jobs/4133458/raw I cannot
find the message "can't cd to blat", did you see this exact message?

About 20 lines before the end of the log.  In the non-raw link line
2686.  I'd be astonished if you run make yourself if you would not get
that error yourself.
Kind regards, Andreas.

Wait a moment.  After I removed the line from debian/rules fully trusting
your makefile the build went further.  I need to check ...

Continuing with new build issues:  First I think that the makefiles seem to implement a mix between building and installing software.  There is the common habit to do some make install separately from make.  Remembering that you was wondering about the need of make clean when talking about some throw-away VMs it might not relevant for you to split into these steps.  I can surely work around this - just mentioning it for your kind consideration.
I realised this mix of building and installing when I stumbled upon the fact that
mv cartReset /build/kent-core-447-test2/debian/kent-core-web/usr/lib/cgi-bin/kent-core/cartReset

failed since the target directory did not existed.  While it was simple enough to solve for me it might make sense to verify that the target directory exists inside the makefile.
The more honest blocker is now that it seems that not all libraries are build as you can see in the latest build log:
cc -O -g -g -O2 -ffile-prefix-map=/builds/med-team/kent-core/debian/output/source_dir=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -Wall -Wformat -Wimplicit -Wreturn-type -Wuninitialized -std=c99 -Wall -Wall das.o ../../lib/x86_64/jkhgap.a ../../lib/x86_64/jkhgapcgi.a ../../lib/x86_64/jkweb.a  -lpthread -lssl -lcrypto ../../htslib/libhts.a -lpng16 -lm -lz  -lm /usr/lib/x86_64-linux-gnu/libmysqlclient.a -ldl -lstdc++ -lrt
/usr/bin/ld: cannot find ../../lib/x86_64/jkhgapcgi.a: No such file or directory
collect2: error: ld returned 1 exit status
make[4]: *** [makefile:17: compile] Error 1

I checked which static libraries were actually built:
/build/kent-core-447-test2 # find . -name "*.a"
./src/parasol/lib/x86_64/paralib.a
./src/lib/x86_64/jkweb.a
./src/lib/x86_64/optimalLeaf.a
./src/lib/x86_64/jkhgap.a
./src/htslib/libhts.a

Do you have any idea why jkhgapcgi.a was not build?
Kind regards, Andreas.

Hi Andreas,
I don't know what your build system is doing, it should only run the
top-level "make", without any options, no cd into "src", just the top-level
makefile. I just did that and it's not trying to build "das".
The top-level makefile has this line:
all: bindir
cd src && ${MAKE} utils USE_HAL=0 USE_FREETYPE=0 USE_HIC=0
BINDIR=$(CURDIR)/bin
bindir:
mkdir -p bin
It's only building the "utils". Your error occured in the "das" directory,
"das" is a CGI web program, it will not be useful for Debian users. I can
remove the directory from the repo, but thought that I didn't want to get
into stripping things too much, I just removed the parts with a non-MIT
licence for now and a few directories that are not useful and relatively
big.
I don't know what you mean with the "install" comment, it's not installing,
not if you use my top-level makefile, as you can see, it will mv the
binaries into CURDIR/bin so will not write outside the build tree.
On Fri, Apr 14, 2023 at 10:24 AM Andreas Tille @.***>
wrote:

Continuing with new build issues: First I think that the makefiles seem to
implement a mix between building and installing software. There is the
common habit to do some make install separately from make. Remembering
that you was wondering about the need of make clean when talking about
some throw-away VMs it might not relevant for you to split into these
steps. I can surely work around this - just mentioning it for your kind
consideration.
I realised this mix of building and installing when I stumbled upon the
fact that
mv cartReset /build/kent-core-447-test2/debian/kent-core-web/usr/lib/cgi-bin/kent-core/cartReset
failed since the target directory did not existed. While it was simple
enough to solve
https://salsa.debian.org/med-team/kent-core/-/blob/master/debian/rules#L16
for me it might make sense to verify that the target directory exists
inside the makefile.
The more honest blocker is now that it seems that not all libraries are
build as you can see in the latest build log
https://salsa.debian.org/med-team/kent-core/-/jobs/4134995:
cc -O -g -g -O2 -ffile-prefix-map=/builds/med-team/kent-core/debian/output/source_dir=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -Wall -Wformat -Wimplicit -Wreturn-type -Wuninitialized -std=c99 -Wall -Wall das.o ../../lib/x86_64/jkhgap.a ../../lib/x86_64/jkhgapcgi.a ../../lib/x86_64/jkweb.a  -lpthread -lssl -lcrypto ../../htslib/libhts.a -lpng16 -lm -lz  -lm /usr/lib/x86_64-linux-gnu/libmysqlclient.a -ldl -lstdc++ -lrt
/usr/bin/ld: cannot find ../../lib/x86_64/jkhgapcgi.a: No such file or directory
collect2: error: ld returned 1 exit status
make[4]: *** [makefile:17: compile] Error 1
I checked which static libraries were actually built:
/build/kent-core-447-test2 # find . -name "*.a"
./src/parasol/lib/x86_64/paralib.a
./src/lib/x86_64/jkweb.a
./src/lib/x86_64/optimalLeaf.a
./src/lib/x86_64/jkhgap.a
./src/htslib/libhts.a
Do you have any idea why jkhgapcgi.a was not build?
Kind regards, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1508127147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TJPJVNTIGRC3Y6HT7TXBECSTANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi Andreas, I don't know what your build system is doing, it should only run the top-level "make", without any options, no cd into "src", just the top-level makefile.

Argh, I just had some remaining --sourcedirectory=src which was used before the top-level makefile existed.  Sorry for the noise!

Your error occured in the "das" directory, "das" is a CGI web program, it will not be useful for Debian users. I can remove the directory from the repo, but thought that I didn't want to get into stripping things too much, I just removed the parts with a non-MIT licence for now and a few directories that are not useful and relatively big. I don't know what you mean with the "install" comment, it's not installing, not if you use my top-level makefile, as you can see, it will mv the binaries into CURDIR/bin so will not write outside the build tree.

Thanks for the hint.  It makes perfectly sense to keep all free code in that repository and simply not build the code if it is not interesting.
Thanks again for your cooperation and sorry for the noise I've created with the remaining option.
Kind regards, Andreas.

Thanks for all your work on this! Do you know what the package will be
called? Are you planning to have the package include all the binaries?
On Fri, Apr 14, 2023 at 11:04 AM Andreas Tille @.***>
wrote:

Hi Andreas, I don't know what your build system is doing, it should only
run the top-level "make", without any options, no cd into "src", just the
top-level makefile.
Argh, I just had some remaining --sourcedirectory=src which was used
before the top-level makefile existed. Sorry for the noise!
Your error occured in the "das" directory, "das" is a CGI web program, it
will not be useful for Debian users. I can remove the directory from the
repo, but thought that I didn't want to get into stripping things too much,
I just removed the parts with a non-MIT licence for now and a few
directories that are not useful and relatively big. I don't know what you
mean with the "install" comment, it's not installing, not if you use my
top-level makefile, as you can see, it will mv the binaries into CURDIR/bin
so will not write outside the build tree.
Thanks for the hint. It makes perfectly sense to keep all free code in
that repository and simply not build the code if it is not interesting.
Thanks again for your cooperation and sorry for the noise I've created
with the remaining option.
Kind regards, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1508187423,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TIP6SBFKY3XD42J44TXBEHJ7ANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Another remark:  The repository contains the ELF 32-bit LSB executable src/hg/fishClones/bander.i386.  Since the Debian source should not contain such binaries I have to exclude this file from upstream source (which is simple enough).  I'm just wondering whether this is intended or can be generally removed.

The file src/webBlat/webBlat.c contains
/* Copyright 2004 Jim Kent.  All rights reserved. */

and thus should not belong to this repository of MIT licensed source code.

Thanks! That was my mistake. Removed.
On Mon, Apr 17, 2023 at 1:57 PM Andreas Tille @.***>
wrote:

The file src/webBlat/webBlat.c contains
/* Copyright 2004 Jim Kent.  All rights reserved. */
and thus should not belong to this repository of MIT licensed source code.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1511202417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TKZQR6NJ4RQIZKRWUTXBUVZDANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Thanks again for the quick response.

kent-tools ?
genome-browser-tools ?
browser-tools ?
On Mon, Apr 17, 2023 at 2:37 PM Andreas Tille @.***>
wrote:

I'd be seriously interested in suggestions and will follow your advise.
Do you have suggestions for the name of the binary package(s)?
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1511259307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TKQHMSXPWFJSLAJDCDXBU2QRANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi Andreas,
do you know if there is any project that ports Debian packages over to
Redhat? If I get a user on e.g. Centos, is there something I can tell them
how to use this package?
On Mon, Apr 17, 2023 at 6:58 PM Andreas Tille @.***>
wrote:

Am Mon, Apr 17, 2023 at 05:39:49AM -0700 schrieb Maximilian Haeussler:

kent-tools ?
genome-browser-tools ?
browser-tools ?

Out of these suggestions I'd prefer genome-browser-tools and will start
with this. Thanks for your suggestions, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1511745854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TLW5WYJP2WV2MR52O3XBVZERANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Am Tue, Apr 18, 2023 at 04:59:41AM -0700 schrieb Maximilian Haeussler:

do you know if there is any project that ports Debian packages over to
Redhat? If I get a user on e.g. Centos, is there something I can tell them
how to use this package?

I admit I have no idea about any RPM based distro.  I know there are some deb2rpm converters out there but I have no idea about their quality and what is recommendable.  The only thing I know is that rpm2deb does not lead to any satisfying result and if I needed a deb from some rpm I usually inspected the srpm (source package) for some metadata and did the packaging manually using hints from there.
Hope this helps, Andreas.

OK, that's what I had expected. Thanks!

Message ID: @.***>

I have another question: Once building with your makefile I get lots of binaries inside the bin/ directory:
aNotB                       faOneRecord             raToLines
addCols                     faPolyASizes            raToTab
aladdin                     faRandomize             randomLines
ameme                       faRc                    rmFaDups
ave                         faRenameRecords         rowsToCols
aveCols                     faSimplify              scrambleFa
bamToPsl                    faSize                  sizeof
barChartMaxLimit            faSomeRecords           spacedToTab
bedClip                     faSplit                 splitFile
bedCommonRegions            faToFastq               splitFileByColumn
bedGeneParts                faToNib                 stToXao
bedGraphPack                faToTab                 strexCalc
bedGraphToBigWig            faToTwoBit              stringify
bedJoinTabOffset            faTrans                 subChar
bedJoinTabOffset.py         faTrimPolyA             subColumn
bedPileUps                  faTrimRead              subs
bedRemoveOverlap            fastqStatsAndSubsample  tabInfo
bedRestrictToPositions      fastqToFa               tabQuery
bedToBigBed                 findMotif               tabRepeatedFieldsToArrayField
bigBedInfo                  fixCr                   tabToHtml
bigBedNamedItems            gapSplit                tabToTabDir
bigBedSummary               gffPeek                 tableSum
bigBedToBed                 git-reports             tagStormArrayToCsv
bigGuessDb                  gmtime                  tagStormCheck
bigHeat                     headRest                tagStormDeleteTags
bigWigAverageOverBed        hitreport               tagStormFromTab
bigWigCat                   htmlCheck               tagStormHoist
bigWigCluster               htmlPics                tagStormInfo
bigWigCorrelate             indexfa                 tagStormJoinTab
bigWigInfo                  indexgl                 tagStormReformat
bigWigMerge                 ixIxx                   tagStormRenameTags
bigWigSummary               ixali                   tagStormRenameVals
bigWigToBedGraph            ixword1                 tagStormToCsv
bigWigToWig                 ixword3                 tagStormToHtml
bottleneck                  jkUniq                  tagStormToJson
bptForTwoBit                jsonToTagStorm          tagStormToSql
bptLookupStringToBits64     lineCount               tagStormToTab
bptMakeStringToBits64       linesToRa               tailLines
calc                        localtime               tdbRename
catDir                      makepgo                 tdbSort
catUncomment                matrixClusterColumns    textHist2
ccCp                        matrixMarketToTsv       textHistogram
chopFaLines                 matrixNormalize         tickToDate
chromToUcsc                 matrixToBarChartBed     toLower
clusterMatrixToBarChartBed  metaFlatten             toUpper
colTransform                metaHoist               trackDbIndexBb
convolve                    metaReformat            trixContextIndex
countChars                  mktime                  trixMultiSearch
counter                     newProg                 trixSearch
cpg_lh                      newPythonProg           twoBitDup
detab                       nibFrag                 twoBitInfo
dnadust                     nibSize                 twoBitToFa
dnsInfo                     nt4Frag                 ucscApiClient
endsInLf                    paraFetch               udcCleanup
expMatrixToBarchartBed      paraSync                udcFuse
faAlign                     primeMate               undupFa
faCmp                       protDust                upper
faCount                     pslMap                  vcfFilter
faFilter                    pslMapPostChain         venn
faFilterN                   pslPosTarget            verticalSplitSqlTable
faFlyBaseToUcsc             pslRc                   webSync
faFrag                      pslRemoveFrameShifts    weedLines
faGapLocs                   pslScore                wigCorrelate
faGapSizes                  pslSwap                 wigToBigWig
faNcbiToUcsc                pslToPslx               wordLine
faNoise                     pslToXa

I wonder which binaries are really user oriented executable and which ones are some kind of internal helpers.  Could you give any hint whether they might fall into different categories or might it even make sense to put some in a different binary package?  (Please note: I'm personally not a user of these binaries not even a bioinformatician thus I really need your help to make some sensible packaging.)
Kind regards, Andreas.

Another issue is about testing:  src/makefile contains a test target but the root makefile not.  Would you mind providing some sensible test target to enable testing for those targets that will be built by the makefile?
Kind regards, Andreas.

I wonder which binaries are really user oriented executable and which ones are some kind of internal helpers. Could you
give any hint whether they might fall into different categories or might it even make sense to put some in a different
binary package? (Please note: I'm personally not a user of these binaries not even a bioinformatician thus I really need
your help to make some sensible packaging.) Note: binary names like for instance calc are pretty generic and I can not > ship this in /usr/bin/ since it conflicts with another executable from the calc package. Kind regards, Andreas.

I agree. Sorry, forgot about the generic tools, you're right. The following tools are probably too generic and can be replaced by somwhat experienced linux users with bash commands (e.g. xargs)
wordLine fixCr calc endsInLf ccCp lineCount newProg dnsInfo gmtime localtime upper toUpper toLower tickToDate subChar sizeof
I'm unsure about "randomLines",  I'd leave it, I think there is a bash construct to replace it, but the tool here is much faster and easier to use.
I'd not split up the tools over multiple packages, that seems more work that it's useful, you could split by filetype (e.g. psl-tools, bed-tools, etc), but several tools can be used with several filetypes, so that would be hard to decide then.
Testing: I don't think you need to implement testing here. Testing of genomics tools it not as easy as you may think. The tests download big input files from our servers. I don't think it's up to the package maintainers to test the tools, we do that before our release and in our nightly builds.

I agree. Sorry, forgot about the generic tools, you're right. The following tools are probably too generic and can be replaced by somwhat experienced linux users with bash commands (e.g. xargs)
wordLine fixCr calc endsInLf ccCp lineCount newProg dnsInfo gmtime localtime upper toUpper toLower tickToDate subChar sizeof
I'm unsure about "randomLines", I'd leave it, I think there is a bash construct to replace it, but the tool here is much faster and easier to use.
I'd not split up the tools over multiple packages, that seems more work that it's useful, you could split by filetype (e.g. psl-tools, bed-tools, etc), but several tools can be used with several filetypes, so that would be hard to decide then.

There is an option to move all tools to /usr/lib/genome-browser-tools/bin and place symlinks from /usr/bin to those applications that are relevant to be called by users.

Testing: I don't think you need to implement testing here. Testing of genomics tools it not as easy as you may think. The tests download big input files from our servers. I don't think it's up to the package maintainers to test the tools, we do that before our release and in our nightly builds.

I tend to disagree here.  Testing a package is more than testing your tools upstream.  It might uncover issues in the packaging on the Debian system.  Assume a new gcc version might cause issues, some other tool has a conflicting name, some architecture we support in Debian might create issues.  Packages that are containing tests are somehow "privileged" citizens in the Debian package pool since they migrate faster than others etc.  The  Debian Med team is keen on providing tests for every package for theses reasons.  In the case of kent-core I also want to use the Debian packaged htslib - thus I would be happy to test whether it works as expected.
Kind regards, Andreas.

I can add a testing target... hopefully it'll just work... but I doubt
that, because it'll want to to test all other non-MIT code.
You cannot use the package Debian htslib. We modified htslib to use our
caching layer.
On Wed, Apr 19, 2023 at 12:02 PM Andreas Tille @.***>
wrote:

I agree. Sorry, forgot about the generic tools, you're right. The
following tools are probably too generic and can be replaced by somwhat
experienced linux users with bash commands (e.g. xargs)
wordLine fixCr calc endsInLf ccCp lineCount newProg dnsInfo gmtime
localtime upper toUpper toLower tickToDate subChar sizeof
I'm unsure about "randomLines", I'd leave it, I think there is a bash
construct to replace it, but the tool here is much faster and easier to use.
I'd not split up the tools over multiple packages, that seems more work
that it's useful, you could split by filetype (e.g. psl-tools, bed-tools,
etc), but several tools can be used with several filetypes, so that would
be hard to decide then.
There is an option to move all tools to /usr/lib/genome-browser-tools/bin
and place symlinks from /usr/bin to those applications that are relevant
to be called by users.
Testing: I don't think you need to implement testing here. Testing of
genomics tools it not as easy as you may think. The tests download big
input files from our servers. I don't think it's up to the package
maintainers to test the tools, we do that before our release and in our
nightly builds.
I tend to disagree here. Testing a package is more than testing your tools
upstream. It might uncover issues in the packaging on the Debian system.
Assume a new gcc version might cause issues, some other tool has a
conflicting name, some architecture we support in Debian might create
issues. Packages that are containing tests are somehow "privileged"
citizens in the Debian package pool since they migrate faster than others
etc. The Debian Med team is keen on providing tests for every package for
theses reasons. In the case of kent-core I also want to use the Debian
packaged htslib - thus I would be happy to test whether it works as
expected.
Kind regards, Andreas.
—
Reply to this email directly, view it on GitHub
https://github.com/ucscGenomeBrowser/kent-core/issues/2#issuecomment-1514465493,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL4TM4ZADP6S4TM5FQH3LXB6Z4VANCNFSM6AAAAAAWRFOEMA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I can add a testing target... hopefully it'll just work... but I doubt that, because it'll want to to test all other non-MIT code.

Some defined subset for testing is better than nothing.  There are some packages doing superfluous tests like
foo --help

which despite its triviality has uncovered issues.  Something that is better than this would be great.

You cannot use the package Debian htslib. We modified htslib to use our caching layer.

I was afraid you would say so.  I remember the discussion on our mailing list which somehow should be revived.  In Debian its strongly recommended to avoid code duplication due to security issues and other obstacles.  Thus I'd really recommend to talk do htslib authors how it might be possible to use their official code and whether it is possible to include some enhancements you might depend from.  I'd happily like to initiate some discussion about this if you confirm that this is a sensible goal for your code.
Kind regards, Andreas.

I am not sure how to implement the tests now. They're testing some of the
non-MIT tools. I'll have to add a lot of exclusions again.
htslib: for this version, you'll have to do with our patched htslib.
Getting the original htslib to add the hooks we need may take some time.


Vanillajs template missing vite config

Describe the bug
I've just discovered vite, not very familiar yet, but when I compare the vanilla js sample with all other samples (incl. Vanilla ts), it seems to be missing vite configs.
Is this intended or a "bug" (i.e. vite really not enabled in the vanilla js template)?
Used Scaffolding
create-electron
Used Package Manager
npm
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Support now


Java: Support custom/any service in Java Semantic Kernel

Similar to the intent of #161 but this time for Java.

Anyone can already extend an AI service, but there may be more nuanced intent here.


Upgrade to dotnet 8

[ ] upgrade all projects to dotnet 8 and C# 12 via the https://github.com/tye-v2/tye2/blob/main/Directory.Build.props file
[ ] update all nuget references that do not introduce breaking / code changes
[ ] clean up this hack from the initial fork : https://github.com/tye-v2/tye2/pull/8#discussion_r1494489936

@drakon660 do you want to take care of this one while i move forward with the packaging pipeline / push to nuget ?

I can do that, two things

delete Microsoft namespace.
"clean up this hack from the initial fork" ? You mean this not working tests in the pipeline? I so how?

delete Microsoft namespace.

i'll do the renames as part of the push to nuget issues - i need to rename the projects there anyway to get the new exe names

"clean up this hack from the initial fork" ? You mean this not working tests in the pipeline? If so how?
I meant the part about the --roll-forward from here. I think with tye itself on 8, the roll forward will not be needed.

Ok, I got it. Will do

merged


Update transforms.py cv2.wrapAffine dsize should be (xshape,yshape))

Thanks for your PR.
Can you please share the portion of dataset config you are using?

Thanks for your PR. Can you please share the portion of dataset config you are using?
"dataset_params": {
"train_dataset_params": "{'data_dir': '/home/groot/Aromal/yolonas-train-infer/nn/yolonas_train/', 'images_dir': 'train/', 'labels_dir': 'train/', 'classes': ['Signboard_Caution_Board', 'Signboard_Chevron_Board_Left', 'Signboard_Gantry_Board', 'Signboard_Gantry_Board_2', 'Signboard_Hazard_Board', 'Signboard_Information_Board_B', 'Signboard_Information_Board_G', 'Signboard_Information_Board_N', 'Signboard_Mandatory_Board', 'VMS_Gantry', 'Delineator', 'Bus_Shelter', 'ECB_(SOS)', 'Encroachment', 'Hectometer_stone', 'Kilometer_Stone', 'Solar_Blinker', 'Double_Arm_Street_Light', 'Street_Light_Slanding', 'Pot_Holes', 'Signboard_Mandatory_Board_Stop', 'Single_Arm_Light_Slanting', 'High_Mast_Light', 'Expansion_Joint', 'Hoardings', 'Flex_Banner', 'Shop_Board', 'Water_Stagnation', 'Excess_Mud', 'ATCC', 'CCTV', 'DB_box', 'Wall_poster', 'Vegetation_Growth', 'Cattle_movement', 'Car', 'Motorbike', 'Bus', 'Truck', 'Signboard_Mandatory_Board_White'], 'input_dim': [352, 640], 'cache_dir': None, 'cache': False, 'cache_annotations': True, 'ignore_empty_annotations': True, 'transforms': [{'DetectionMosaic': {'input_dim': [352, 640], 'prob': 0.5, 'enable_mosaic': False, 'border_value': 114}}, {'DetectionRandomAffine': {'degrees': 6, 'translate': 0.05, 'scales': [0.7, 1.2], 'shear': 0.5, 'target_size': [352, 640], 'filter_box_candidates': True, 'wh_thr': 2, 'area_thr': 0.1, 'ar_thr': 20}}, {'DetectionHSV': {'prob': 0.3, 'hgain': 5, 'sgain': 6, 'vgain': 6}}, {'DetectionPaddedRescale': {'input_dim': [352, 640], 'pad_value': 114}}, {'DetectionTargetsFormatTransform': {'input_dim': [352, 640], 'output_format': 'LABEL_CXCYWH'}}], 'class_inclusion_list': None, 'max_num_samples': None}",

these are the dataset parameters i used and the aspect ratio is changing during affine transformation.

This the output after affine transform after this modification

After carefully reviewing the existing transformations and existing dataset configs it seems the problem is deeper than it looked at the first glance. Seems our transformations are not using consistent convention whether image size defined as (H,W) or (W,H).
Some transformations assumes (H,W) while other - (W,H) and this is the first place we should fix in the first place.
Merging your PR as is considered a breaking change. Since there could be other projects that expect current behavior (Eventually what you need to do is flip values for target_size argument when creating DetectionRandomAffine in your local config) and that would cause existing configs to work incorrectly.
The right way to solve this would be:

We decide how we approach error-proof way of defining output size of images in our transformations
Implement it, making existing properties deprecated.
Document thoroughly the convention
Make a new release

Clearly this is one a one-day effort, so as a temporary solution I suggest you to fix it locally as follows:
DetectionRandomAffine:

target_size: [640, 352] # Instead of [352, 640]

Again, thanks for bringing this issue up!

Again, thanks for bringing this issue up!
it is my pleasure


[Related Content] Create "right rail" component (UI only)

Description
We need to create a component that will eventually house the related content. This component should be displayed to the right of the page content. At the time of writing, the design treatment for this is still in flux, but the current thinking is that this will sit to the right of the content but,a s the page scrolls up, the right rail will get locked to the top of the page (sticky).
NOTE: this ticket is only for the markup / styles.
Helpful Links
N/A
Screenshots
Work-in-Progress Wireframes

Another wireframe:

NOTE: merge this work in once the buttons have been moved here.

For now, we are going to only add the edit/issue page buttons for this ticket so that we can release this PR on its own.


Three question marks (???) are showing up at the street number in the address.

Thanks for reporting! Copying from email, your suggestion to indicate that OpenStreetMap doesn't have the street number:

Either put a text that says "Unknown Street Number" in place of "???" or put an asterisk and display text above the field that says "Street Number is unavailable."

Thanks for reporting! Copying from email, your suggestion to indicate that OpenStreetMap doesn't have the street number:

Either put a text that says "Unknown Street Number" in place of "???" or put an asterisk and display text above the field that says "Street Number is unavailable."


Preview unavailable (sorry, we couldn't find this file in the repository)

I'm trying to add support for code scanning alerts to https://github.com/ludeeus/action-shellcheck (here is my fork: https://github.com/Arkq/action-shellcheck). I've integrated shellcheck-sarif (many thanks for this project) with the action runner, so right now I've got scanning alerts. However, it seems that the file path in the SARIF file is incorrect. When exploring alerts, there is no file preview. See screenshot below:

On my other projects I'm using CodeQL checks, and I've noticed that the file path does not begin with "./" there. Maybe that's the issue?

@Arkq basically shellcheck-sarif will output the file path in the same way the file path is input into the tool.
so if you run shellcheck -f json shell.sh | shellcheck-sarif, the output sarif file will contain path references to shell.sh
if you run shellcheck -f json ./shell.sh | shellcheck-sarif, the output sarif file will contain path references to ./shell.sh
I think if possible, the best solution would be to see if you can adjust the way you invoke shellcheck to pass the file in without the ./. If that's not possible, we'd need to discuss a way of rewriting paths and a common interface to that.

basically shellcheck-sarif will output the file path in the same way the file path is input into the tool.

OK, it seems reasonable. I've modified shellcheck run, so the leading ./ is removed. Not it works perfectly :)

I'm having the same issue with clippy and even though I specify the --manifest-path from another dir it doesn't work. What should I do?

I think I should do a different issue, this talks about shellcheck :laughing:


Support ETag for static files

Render the ETag header when serving static files. We are already performing .stat() on the open file handle, so we should have the required data in order to build an ETag. We could use the same algorithm as the popular Nginx web server.
When serving, also check the If-None-Match header, and render HTTP 304 Not Modified if appropriate.

Hi! I'd be interested in helping with this enhancement. Any tips on where I should look in the project? I did some basic searching yesterday, but wasn't able to find a file/module this feature could be integrated into.

Hi @dominik-air!
And thanks for your interest in contributing to the project!
Serving static files is implemented in falcon/routing/static.py.


Build is failing!

Build is failing!
npm run build is failing. Attaching the terminal log:
npm run build

><EMAIL_ADDRESS>build /Users/samar/Projects/learn-webpack/webpack-css-example
> webpack

Hash: 191467eb0d73dca00856
Version: webpack 1.12.2
Time: 11230ms
 Asset    Size  Chunks             Chunk Names
app.js  609 kB       0  [emitted]  app
   [0] multi app 28 bytes {0} [built]
    + 162 hidden modules

ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
 @ ./src/stylesheets/base.sass 4:14-504

ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
 @ ./src/stylesheets/modules/container.sass 4:14-517

ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
 @ ./src/stylesheets/modules/header.sass 4:14-514

ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
 @ ./src/stylesheets/utilities/clearfix.sass 4:14-518

ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
 @ ./src/stylesheets/modules/footer.sass 4:14-514

ERROR in ./src/stylesheets/base.sass
Module build failed: Error: Didn't get a result from child compiler
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:90:22)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:214:10)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:77:5)
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:576:13)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:571:10)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:566:9)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:562:8)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:524:7)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:397:15)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:444:10)
    at Compilation.errorAndCallback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:343:3)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:399:12)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (native)
    at callback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:137:11)
    at DependenciesBlock.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/NormalModule.js:85:18)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206:13)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:186:21)

ERROR in ./src/stylesheets/modules/header.sass
Module build failed: Error: Didn't get a result from child compiler
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:90:22)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:214:10)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:77:5)
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:576:13)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:571:10)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:566:9)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:562:8)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:524:7)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:397:15)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:444:10)
    at Compilation.errorAndCallback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:343:3)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:399:12)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (native)
    at callback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:137:11)
    at DependenciesBlock.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/NormalModule.js:85:18)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206:13)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:186:21)

ERROR in ./src/stylesheets/utilities/clearfix.sass
Module build failed: Error: Didn't get a result from child compiler
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:90:22)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:214:10)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:77:5)
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:576:13)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:571:10)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:566:9)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:562:8)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:524:7)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:397:15)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:444:10)
    at Compilation.errorAndCallback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:343:3)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:399:12)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (native)
    at callback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:137:11)
    at DependenciesBlock.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/NormalModule.js:85:18)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206:13)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:186:21)

ERROR in ./src/stylesheets/modules/footer.sass
Module build failed: Error: Didn't get a result from child compiler
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:90:22)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:214:10)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:77:5)
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:576:13)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:571:10)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:566:9)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:562:8)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:524:7)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:397:15)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:444:10)
    at Compilation.errorAndCallback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:343:3)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:399:12)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (native)
    at callback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:137:11)
    at DependenciesBlock.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/NormalModule.js:85:18)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206:13)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:186:21)

ERROR in ./src/stylesheets/modules/container.sass
Module build failed: Error: Didn't get a result from child compiler
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:90:22)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:214:10)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at Object.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/extract-text-webpack-plugin/loader.js:77:5)
    at Compiler.next (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:576:13)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:571:10)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:566:9)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:562:8)
    at Compilation.applyPluginsAsync (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:524:7)
    at Compiler.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compiler.js:397:15)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:444:10)
    at Compilation.errorAndCallback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:343:3)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:399:12)
    at /Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (native)
    at callback (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/Compilation.js:137:11)
    at DependenciesBlock.<anonymous> (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/lib/NormalModule.js:85:18)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206:13)
    at DependenciesBlock.loadPitch (/Users/samar/Projects/learn-webpack/webpack-css-example/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:186:21)
Child extract-text-webpack-plugin:
        + 1 hidden modules

    ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
Child extract-text-webpack-plugin:
        + 1 hidden modules

    ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
Child extract-text-webpack-plugin:
        + 1 hidden modules

    ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
Child extract-text-webpack-plugin:
        + 1 hidden modules

    ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?
Child extract-text-webpack-plugin:
        + 1 hidden modules

    ERROR in `libsass` bindings not found. Try reinstalling `node-sass`?

I bumped the version number for sass-loader from 0.4.1 to 3.1.1 in package.json. Now it seems working. Will add a PR for this.

@samarpanda hmm, the current version works fine for me. Looks like something went wrong when Sass installed for you. Can you delete node_modules, run npm install again & see if it all installs correctly? Also which version of node & npm are you using?

I tried npm install removing node_modules completely. No luck there. I am using:
[samar@sp webpack-css-example [±] master 5b34def ✓]$ node -v
v4.0.0
[samar@sp webpack-css-example [±] master 5b34def ✓]$ npm -v
2.14.2

Ah, I believe older versions of node-sass have some trouble with Node 4. Leave it with me, I'll upgrade a bunch of things at once :smile:

Cool :satisfied:

"sass-loader": "^3.1.1", fixed it for me

Updated all the things & released a new version: https://github.com/bensmithett/webpack-css-example/releases/tag/v2.0.0
Thanks for letting me know @samarpanda! Shout out if you have any more issues.

Cool @bensmithett. Thanks for the quick release. :+1:


My issue with this project

My issue with this project is the fact that i didn't thanked you enough.
Good job! 👍
Thank you! 💯

Thank you @sarbull. This is a lovely first issue. Much appreciated! :heart::smile:


navigation_depth has no effect

Details

Project URL: https://github.com/mabuchilab/QNET
Doc URL:  http://qnet.readthedocs.io/en/latest/
Build URL: http://readthedocs.org/projects/qnet/builds/

Description
It appears the navigation_depth setting has no effect on the RTD website. In
conf.py, I have
html_theme_options = {
    'collapse_navigation': True,
    'display_version': True,
    'navigation_depth': 4,
}

This works correctly when generating the documentation locally (make doc in a
checkout of the project), using sphinx_rtd_theme. However, on the online
version of the docs, the navigation depth remains at 2, which is insufficient.
How do I get a deeper navigation in the sidebar?

@goerz what version of sphinx_rtd_theme are you using locally?
In RTD it seems you are using 0.1.7 which I think doesn't support navigation_depth. Consider upgrading it in your requirements and let me know if that is the reason.

A good place to take a look is the RTD documentation itself, that seems to have at least 3. Maybe you can steal some configurations from there -> https://docs.readthedocs.io/en/latest/team.html#members

I'm using version 0.2.4 locally. Is it supposed to work by upgrading whatever older version of the theme  RTD is using through environment.yml? I've added the following to environment.yml
- ...
- pip:
    - ...
    - sphinx_rtd_theme==0.2.4

In the RTD build logs, it says "requirement already fulfilled". It still
complains about "unsupported theme options"
And why is RTD not using the most current version of their own theme on their
server? I really wish they'd just let me create a clean conda environment and
issue the same make doc I'm using locally, and then just host the resulting
HTML file.

Oh, I think I get why it's not working: After installing the latest version of the theme from environment.yml, it then downgrades it again in the next step of the build process. So how do I get around that? Do I have to fork the theme under a different name just so I can put that name in conf.py?
Sorry I'm annoyed...

Closing in favor of https://github.com/rtfd/readthedocs.org/issues/3829


Set up GitHub Pages

Set up GitHub Pages (from the main branch), update repository description with the proper website link

Configuration is done. Link - dmitryzh100.github.io


make optimisticLocking a store feature?

These tests override isLockingOptimistic:
https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-cassandra/src/test/java/com/thinkaurelius/titan/graphdb/CassandraGraphTest.java#L28
https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-berkeleyje/src/test/java/com/thinkaurelius/titan/graphdb/berkeleyje/BerkeleyGraphTest.java#L62
https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-test/src/test/java/com/thinkaurelius/titan/graphdb/inmemory/InMemoryGraphTest.java#L71
https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-hbase-parent/titan-hbase-core/src/test/java/com/thinkaurelius/titan/graphdb/hbase/HBaseGraphTest.java#L32
https://github.com/thinkaurelius/titan/blob/47e9b35efaa4d1eb8722c1db0b1e599336a2c049/titan-cassandra/src/test/java/com/thinkaurelius/titan/graphdb/thrift/ThriftGraphCacheTest.java#L25
This value varies from one storage backend to another. Those differences are summarized here, and I think it makes sense to pull this out of tests into StoreFeatures. If you agree I could make a pull request...
Thanks
Alex

created pull request https://github.com/amcp/titan/commit/0638987c7b5907a790e880e1eec305b49ac6494c

isLockingOptimistic was a hack in the test code before the PR, but if we're pulling it into src/main like this, then perhaps we should refine the concept a bit.  Thinking out loud here...
It might be misleadingly named, since "pessimistic" behavior on BDB only really applies to its read locks; write lock acquisition is still deferred until the titan transaction commits.
This behavior is also not strictly a store feature; I suppose it's determined by the (locker, store) pair.   On the other hand, with the only non-default alternative locker deleted and likely to remain that way (#1131), we could probably get away with treating optimism as a strictly store-only property, even though it isn't theoretically true.  This could be a problem for someone writing a custom locker.
I see that optimisticLocking is listed as a table row in the linked documentation, but I don't understand exactly what contract this implies to the user.  Is it the same property we use in the test code -- telling us in what order conflicting transactions are expected to fail?

I agree the name is probably not right. It is the same property used in test code, determining the order in which conflicting transactions are expected to fail. If you can suggest a better name for this feature, I can update it in the pull request and in the linked documentation
I will fix the imports in another pull request.

There may not be much wrong with the suggested name, as long as the documentation of the feature in StoreFeatures says that it works in conjunction with the Locker in place.

I haven't thought about this carefully yet, but perhaps moving isLockingOptimistic (or whatever we call it) to GraphDatabaseConfiguration would obviate the hypothetical problem about considering the locker.  Its implementation could still just call and return some boolean-returning method on StoreFeatures right now, functionally equivalent to the PR.  However, exposing this publicly through GDC instead of StoreFeatures would let us account for locker behavior if we need to without affecting user code that just wants information about conflicting transaction failure order.  What do you think?

I think that exposing isLockingOptimistic in GraphDatabaseConfiguration would allow us to consider the locker. Let me revise the PR.

https://github.com/thinkaurelius/titan/pull/1140


build error: Could not resolve all dependencies

Took latest git version 13 March 2016. Tried to exactly follow build instructions found in Readme.md
./gradlew assembleDebug
...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not find com.android.support:appcompat-v7:23.2.0.
     Searched in the following locations:
         https://jcenter.bintray.com/com/android/support/appcompat-v7/23.2.0/appcompat-v7-23.2.0.pom
         https://jcenter.bintray.com/com/android/support/appcompat-v7/23.2.0/appcompat-v7-23.2.0.jar
         https://jitpack.io/com/android/support/appcompat-v7/23.2.0/appcompat-v7-23.2.0.pom
         https://jitpack.io/com/android/support/appcompat-v7/23.2.0/appcompat-v7-23.2.0.jar
     Required by:
         android-vts-master:app:unspecified
         android-vts-master:app:unspecified > com.github.paolorotolo:appintro:3.3.0
   > Could not find com.android.support:cardview-v7:23.1.1.
...
(more messages likes that, total 11 'Could not find com.android...')

I am under Gentoo/Amd64 if it matters.
How do I build the project?

You need to download the Android Support Library package by following the instructions here:
http://developer.android.com/tools/support-library/setup.html
At the time of writing, the latest version is 23.2:
http://android-developers.blogspot.co.uk/2016/02/android-support-library-232.html
You then need to update the version number in your app\build.gradle file on lines 47-50:
    compile 'com.android.support:appcompat-v7:23.2.1'
    compile 'com.android.support:cardview-v7:23.2.1'
    compile 'com.android.support:design:23.2.1'

This issue can now be closed?

Created pull request #143 Update external dependencies.


OpenTracing library is deprecated

OpenTracing is deprecated. Currently the documentation instructs developers to use OpenTracing to add manual instrumentation. Perhaps the tracer in opentelemetry-dotnet should be used
Using the API built-in to .NET could also be a solution here. (#434).
Additional context
From the About section on the project's github -- https://github.com/opentracing/opentracing-csharp:

_OpenTracing API for C# (.NET). 🛑 This library is DEPRECATED! https://github.com/opentracing/specification/issues/163_

Documentation about the built-in .NET Activity class in the  opentelemetry-dotnet project

We are aware of it.
We are actively involved in the development of https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation.


change iDeep to Chainer Backend for Intel Architecture …

…in docs/source/tips.rst
Thank you for creating a pull request!
Please double-check the following.

Read our contribution guide.

Does your code conform to our coding guidelines?
Did you write sufficient test code?
Did you write sufficient documentation?

Also, take a look at our compatibility policy.

Could you fix the ReST syntax errors (lengths of underlines of section headers)?
https://travis-ci.org/chainer/chainer/jobs/414367789#L2048
http://docutils.sourceforge.net/docs/user/rst/quickstart.html#sections

@toslunar would you please help merge the change to master? Thanks.

Sorry for being late.
Jenkins, test this please.

Jenkins CI test (for commit f0698f7c3527da8c1d059240326c3dbafad97a05, target branch master) succeeded!


darker image for "unknowns" rotation

darker image for "unknowns" rotation
Kim mentioned yesterday that darker images will probably look better (or at least more of a mixture). At presnet most of our backgrounds are "light"

The cytokinesis video has a dark background.
I remade the "unknowns rotation image with a dark grey background. (in drop box)

I think it might be too dark, with the dark cytokinesis we are going a bit goth (do you remember  the phase when all web pages had a black background? )
Anyway I have done some called unknown_medium. I think these might work OK....

Do you think we should use the  image I made with a darker background?
Can close this if you think the existing one is better.
v

I'm not sure.  Here's what it looks like.  It should be visible if you visit the URL for my desktop: http://pombase2-kmr.bioinformatics.nz/
I'll try the medium background one you made next.

I think the dark one is too dark with the contrasrt with the pie. I should have deleted that one. The medium one might work....

I've swapped it in the dev version on my desktop so you can see it in context: http://pombase2-kmr.bioinformatics.nz/
Let me know if you think we should go with it.

but it looks OK now we have a dark one and a few others

Yep, and the infographic rather than the curation graph in the middle panel improves things.


multi node ci

What does this PR do?

Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In in short, see following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

Hello @tchaton! Thanks for opening this PR.

In the file test_multi_nodes/test_multi_nodes_gpu.py:

Line 20:1: E402 module level import not at top of file
Line 22:1: E402 module level import not at top of file
Line 23:1: E402 module level import not at top of file
Line 24:1: E402 module level import not at top of file
Line 26:1: E402 module level import not at top of file
Line 27:1: E402 module level import not at top of file
Line 28:1: E402 module level import not at top of file
Line 47:1: E305 expected 2 blank lines after class or function definition, found 1

Do see the Hitchhiker's guide to code style


GET requests automatically redirected in staging env

Sails version: 1.0.2
Node version: 8.10.0
NPM version: 6.1.0
DB adapter name: sails-postgresql
DB adapter version: 1.0.1
Operating system: Heroku servers

Hi, Im facing an issue while trying to handle a GET request on staging environement. (_It works fine in dev mode and also when I dockerize the apps on my dev server_). I've been hard searching for a solution since a Week but did not find anything.
Context
I'm implementing two apps on Heroku exchanging by HTTPs requests.

Backend : Sails obviously
Frontend : Stand-alone Vue Js app

Problem
Trying to request the datas associated to a logged in user. I use a GET request sended by 'axios' to a controller I've define in my routes config :
GET /api/v1/account/user-controller':                  { action: 'account/user-controller'},
The request is made with an axios instance named HTTP (it comports the authorization header and the aimed base url) :
HTTP({
      method: GET,
      url: '/api/v1/account/user-controller'
    })
      .then(resp => {
        console.log('Request for user successful, respond with the user ' + resp.data.user.id)
        // State change
        commit(USER_SUCCESS, resp)
        console.log('Commit state change : USER - succes')
      })
      .catch(err => {
        console.log('Request for user failed, respond with the err ' + err)
        // State Change
        commit(USER_ERROR, err)
        console.log('Commit state change : USER - error')
        // if resp is unauthorized, logout too
        dispatch(AUTH_LOGOUT)
      })

And the aimed controller (actions 2) in sails 👍
module.exports = {

  friendlyName: 'Get account information',

  exits: {
    success: {
      description: `Success`,
      extendedDescription:`User informations send in JSON format.`
    },
    unfound: {
      description: `Unfound`,
      responseType: 'unauthorized'
    }
  },

  fn: async function (inputs, exits) {

    var userRecord = await User.findOne({ id: this.req.token.id });
    sails.log.info('USER (cont.) - User founded', userRecord.id);

    // If there was no matching user, respond thru the "unfound" exit.
    if(!userRecord) {
      throw 'unfound';
    }

    return exits.success({user: userRecord});
  }
};

Each time the GET request is sent from my frontend, my sails instance logs this info : info: Redirecting GET request from 'undefined.' subdomain… & it "pings" the request to my frontend app.
Also if replace the method from GET to POST, it works.
Finally just for info, the relevant part of my env.files that I think is ok with all CORS settings 👍
  //--------------------------------------------------------------------------
  //     Blueprint API Configuration
  //--------------------------------------------------------------------------

  blueprints: Object.assign({}, PRODUCTION_CONFIG.blueprints, {
    actions: false,
    rest: false,
    shortcuts: false
  }),

  //--------------------------------------------------------------------------
  //      Security Settings Configuraiton
  //--------------------------------------------------------------------------

    cors: {
      allRoutes: true,
      allowOrigins: ['https://frontend-app-url.herokuapp.com'],
      allowRequestHeaders: 'Host, Origin, Referer, Content-Type, Authorization, Accept',
      allowRequestMethods: 'GET,PUT,POST,OPTIONS,HEAD'
    },
    csrf: false

  //--------------------------------------------------------------------------
  //      WebSocket Server Settings Configuration
  //--------------------------------------------------------------------------

    onlyAllowOrigins: ['https://frontend-app-url.herokuapp.com']

ok, fixed!

ok, fixed!

@qvdp At a glance, looks like this is happening because of the custom hook (see https://github.com/balderdashy/sails-generate/blob/3ac16f60b4fd9cd71f481f10aad8d3dddb222239/lib/core-generators/new/templates/api/hooks/custom/index.js.template#L139-L154)

@mikermcneil Your answer is spot on ! I just disabled this part of the custom hook and it works like a charm.
You solved my problem thank you.

Yes @mikermcneil - thanks for pointing that out!
May I suggest, that that redirection part with subdomains gets a small paragraph in the deployment section? I was absolutely going crazy about this for a couple of days, putting my whole infrastructure in doubt. Really tricky to find and impossible to actually find it without this issue post.


Improving chess openings database #2 (OpeningDB)

Sac -> Sacrifice (grammar)
UNNAMED -> Unnamed (grammar)
Queen -> Queen's (http://bit.ly/1RZT0j5)
King -> King's (http://bit.ly/1R7orb2)

King Pawn and Queen Pawn are alternate names for the Open and Closed games respectively.

Yes, but there is always apostrophe. (who - Queen, what - Pawn = Queen's Pawn)

Unfortunately, your attempt at logistics loses to the fact that the king pawn is a noun in itself: https://en.wikipedia.org/wiki/Pawn_(chess)
Both King Pawn Opening and King's Pawn Opening are used, with the former being more common.

Agree. But more often is used name King's Pawn Opening.

so... merge or what?

An Internet search yields that King's Pawn Game is the more common spelling.  +1 to merge.


test-branch/execute-job/quoted-authorization/a4db0e32-c725-4d3f-8855-0f931b452c1d

PR for testing d8649d9eb4f6b384197406bbf672408587db8e32

/canonical/self-hosted-runners/run-workflows d8649d9eb4f6b384197406bbf672408587db8e32


UDP:  When is this protocol invoked?

This requirement:
Maintain session persistence | Make sure your firewall doesn't change the mapped Network Address Translation (NAT) addresses or ports for UDP.
--Arent' all sessions encapsulated over tcp/443?

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

ID: 1d996cf7-9f48-2b30-7759-afaf3fe82caa
Version Independent ID: 24dd6cdf-d35f-53b2-06c2-0a27891825d4
Content: Prepare your organization's network for Teams - Microsoft Teams
Content Source: Teams/prepare-network.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Use go-version instead of semver to accept various versions.

Signed-off-by: morimoto-cybozu<EMAIL_ADDRESS>Fixes: https://github.com/VictoriaMetrics/operator/issues/178

thanks for contribution!


Should return errors when deploy the services with invalid annotation formats.

As per the new implementation, the annotation of the services are different.(@http:BasePath, @http:POST)  but it will not give any error or warning when we put those annotations even as the previous way. (@POST, @BasePath)

Fixed in v0.86


⚠ Bofrost.com has degraded performance

In d04b6a5, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 2568 ms

Resolved: Bofrost.com performance has improved in 7f3fe1f after 6 minutes.


Add APIs for safely interacting with some trickier WebView APIs

Task/Issue URL: https://app.asana.com/0/72649045549333/1208402254099284/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5070  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CDRussell and the rest of your teammates on  Graphite

Thanks for looking already @joshliebe, tagging you as the assigned reviewer 😄