Add setExternalForces method to NonlinearSolid

This PR allows users to specify a vector of external forces (VectorCoefficients) to apply to a NonlinearSolid.
The forces are added to NonlinearSolid.H_ because the H_ operator is used both in the quasistatic and dynamic modes and will be consistent.
Instead of writing yet another nonlinearformintegrator, a mfem::LinearformIntegrator was wrapped as an mfem::NonlinearformIntegrator.

Codecov Report

Merging #326 (d6a3ae5) into develop (e807860) will decrease coverage by 0.25%.
The diff coverage is 44.44%.

@@             Coverage Diff             @@
##           develop     #326      +/-   ##
===========================================
- Coverage    90.77%   90.51%   -0.26%
===========================================
  Files           43       43
  Lines         1658     1666       +8
===========================================
+ Hits          1505     1508       +3
- Misses         153      158       +5

Impacted Files
Coverage Δ

src/serac/physics/nonlinear_solid.hpp
100.00% <ø> (ø)

src/serac/physics/nonlinear_solid.cpp
96.90% <44.44%> (-2.56%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #326 (d6a3ae5) into develop (e807860) will decrease coverage by 0.25%.
The diff coverage is 44.44%.

@@             Coverage Diff             @@
##           develop     #326      +/-   ##
===========================================
- Coverage    90.77%   90.51%   -0.26%
===========================================
  Files           43       43
  Lines         1658     1666       +8
===========================================
+ Hits          1505     1508       +3
- Misses         153      158       +5

Impacted Files
Coverage Δ

src/serac/physics/nonlinear_solid.hpp
100.00% <ø> (ø)

src/serac/physics/nonlinear_solid.cpp
96.90% <44.44%> (-2.56%)
:arrow_down:

Continue to review full report at Codecov.

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

@samuelpmishLLNL could you take a look at this? Thanks!

@samuelpmishLLNL could you take a look at this? Thanks!

As we discussed in last week's meeting, there are some additional load types we may want to support as well but this seems like a reasonable start for for small deformations

As we discussed in last week's meeting, there are some additional load types we may want to support as well but this seems like a reasonable start for for small deformations

LGTM

LGTM


Chaining streams triggers "reached the recursion limit during monomorphization"

Using this branch here: https://github.com/cetra3/apache_log/tree/recursion_limit
Trying to compile renders the following message:
cargo build
   Compiling apache_log v0.2.0 (file:///Users/cetra/Desktop/apache_log)
error: reached the recursion limit during monomorphization (selection ambiguity)

error: Could not compile `apache_log`.

I'm wondering if there is another way to accomplish what I'm trying to do, or whether there is some setting I can set to increase the recursion limit

May be related to https://github.com/alexcrichton/futures-rs/issues/367 or https://github.com/alexcrichton/futures-rs/issues/393 or https://github.com/rust-lang/rust/issues/40003. I'd love to work around these errors but unfortunately I'm not sure how to do so :(


Issue 890 - close Jetty related issues, update docker-compose.yml

Jetty upgrade not needed: the project was migrated to spring boot.
The docker-compose file needed updating to reflect this.
There are also a number of files generated when running docker-compose up and I added those paths to .gitignore
Issues / PR related to Jetty:
closes #890
closes #407
closes #422
closes #804

I signed the ICLA and sent it by email, so I also updated contributing.md here

Thanks for your fixes and welcome to the project! :)


how to set only one codec to ulaw?

Hi, I need to set only one codec to ulaw? How to do that? Please share a simple code snippet. thank you

This is not a bug so I will be closing it. In the future please our Google Group for questions like this.
You can achieve what you want to do with modifiers. You can use the stripRtpPayload modifier to strip all other rtp payloads. Alternatively you can write your own modifier that does the opposite, strip everything besides what is on a whitelist.


only run flake8 if flake8 is present

I have lots of projects on my laptop but I do not have flake8 (nor do I want to have flake8) installed in the virtual environment for every one of my projects. It would be nice if linter-flake8 respected my desire to not install flake8 globally instead of throwing these errors that occur whenever it tries to launch flake8:

Is it possible to conditionally report flake8 violations if and only if flake8 is actually present?
It might be worthwhile to throw a one-time warning (at start-up?) that displays to show that linter-flake8 will not work without flake8 installed.

Hmmm, I'm tempted to simply mark this as wontfix, but I'm open to moving this to a warning on the first time a lint is called on a file (instead of spamming you on every change to the file!).

I set the "Executable path" to $PROJECT/.venv/bin/flake8;/bin/true. true is a standard unix tool that does nothing and exits with a non-zero exit code. Kind of a hack and perhaps not very portable, but works for me.

Nice. That works for me too. I have all of my virtualenvs in my home directory, so I set the executable path to $VIRTUAL_ENV/bin/flake8;/usr/bin/true

Marking this as closed, there's a workaround posted here and nobody has found this important enough to submit a PR for it in the first place 😉.


writeFile & readFile

What do you think about including ByteString variants of those operations from http://hackage.haskell.org/package/pipes-safe-2.2.2/docs/Pipes-Safe-Prelude.html? It will create dependency on pipes-safe here. As for me, it would be worse to put them into pipes-safe as it will get dependency on pipes-bytestring then. I can make a PR, but I'm not sure, where they should go, and whether there are some other reasons why they are not already here.

No need to inflict a dependency on each other. There could be a Pipes.ByteString.SafeIO library that imports both.

Yeah, I would prefer either a separate library or for pipes-safe to depend on pipes-bytestring (but not the other way around).  The pipes-safe library is the one library in the pipes ecosystem that I believe was probably the one I most poorly designed, so I try to avoid dependencies on that library from other pipes libraries.

@Gabriel439 I'm curious (and always eager to learn about proper exception handling techniques) - why do you think it's poorly designed?

@mitchellwrosen The main reason is that I feel that pipes is the wrong abstraction for resource-safety.  I feel that a more restricted abstraction (like Shell from turtle, for example) is necessary to get predictable resource management guarantees and a nice user experience.

I was wondering about this. Is it 'bi-directionality' that causes this problem?  If so would it be possible to restrict the instances so that only regular pipes-directional Proxys come under them?

readFile and writeFile are highly desirable operations, I think, if only from a tutorial perspective.

I was thinking this while looking at an attempt I started to write a version of the conduit tutorial that just went through each example for all familiar streaming libraries at once, rather than just conduit. Frankly the framework dependence of the literature is demoralizing and dumb. The plan of replicating that tutorial isn't quite practical as it stands, but readFile/writeFile would be helpful.

Bidirectionality is not the problem.  Even something as simple as ListT has the same issue.  The root of the problem is that if you expose the ability to request just one element then the burden of freeing things falls on the user.  That's the reason why Shell works and can provide harder resource guarantees because it doesn't provide a next-like function.

Okay I see people are expecting more than I anticipated under this heading. It explains the resistance of conduit to exposing something like next I suppose? This does seem like a very disabling constraint. The absence of next and the like is closely bound up the way I feel when using conduit like I'm a captive of a framework with obscure protocols that must be learned from a master and so on. turtle has this effect too, of course, but has a restricted ambition.

This does suggest that I should scrap the attempt to fit the streaming business with e.g. resourceT since there's no way I can accept giving up on the inspection of the stream. But there's still some understanding I'm missing. Is this much different from the fact that if e.g.  I don't mind this at all frankly.


Made reload current project ask for confirmation with unsaved changes

Fix #52287
I tested that this (and quit) doesn't work when save each scene on quit setting is turned off, idk if issue is reported or not but I left this problem as is because it should be covered in a separate PR.

Thanks!

Cherry-picked for 3.5.

Minor regression in the 3.5 fix.
3.4.4-stable behavior:

hit PROJECT > RELOAD CURRENT PROJECT
pending script changes auto-saved
pending scenetree changes auto-discarded <--- bug
Project reloaded WITH PREVIOUSLY ACTIVE SCENE OPEN AND ACTIVE

3.5-RC6 behavior:

hit PROJECT > RELOAD CURRENT PROJECT
if pending changes (script or scenetree), "Please confirm" dialog asking to save changes <--- bug fixed, awesome!
Project reloaded with no active scene, i.e. PREVIOUSLY ACTIVE SCENE DISCARDED <-- regression

For me, this is a small hit to usability, because it was nice previously to just hit "project reload" (after quickly hitting ctrl-shift-alt-S to force global save, due to the bug) when you need to clear any lingering editor issues and then land right back in the same scene after reload to continue on.  But now we have to go find the scene/script we were working on and reopen it.
No biggie, but just noting the change in behavior (which might be due to the way the fix had to be implemented).

Minor change (not really a regression) in behavior after the 3.5 fix:
3.4.4-stable behavior:

Make a change to the scenetree (don't manually save the change)
hit PROJECT > RELOAD CURRENT PROJECT
pending scenetree changes auto-discarded <--- bug
Project reloads WITH PREVIOUSLY ACTIVE SCENE/TAB OPEN AND ACTIVE

3.5-RC6 behavior:

Make a change to the scenetree (don't manually save the change)
hit PROJECT > RELOAD CURRENT PROJECT
"Please confirm" dialog asking to save changes <--- bug fixed, awesome!
Hit "Save and Reload"
Project reloaded with no active scene, i.e. PREVIOUSLY ACTIVE SCENE NOT REOPENED

For me, this is a small hit to usability, because it was nice previously to just hit "project reload" (after quickly hitting ctrl-shift-alt-S to force global save, due to the bug) when you need to clear any lingering editor issues and then land right back in the same scene after reload to continue on.  But now we have to go find the scene we were working on and reopen it.
Not a big deal, but just noting the change in behavior.  You can observe how the "save and reload" step now closes the active scene, leaving just the "empty" tab before reloading the project, so I guess that new step is why it doesn't reopen the previously active scene on reload.
Note that in both 3.4.4 and 3.5-RC6, if you ONLY make an unsaved change to a script and hit RELOAD CURRENT PROJECT then it autosaves WITHOUT showing the "do you want to save" dialog, and in both cases the project will be reloaded with the previously active script tab open and active again.  This post-fix change (no longer reopens the active scene) only exhibits when there are unsaved changes to the scenetree.

Sounds similar to #33326
Not sure why it would happen only in 3.x though.


bug: using ref variable name when referencing DOM node with useRef leads to error

Describe the bug
Naming variable ref when referencing DOM node with useRef:
const ref = React.useRef(null);

will lead to error:
Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?

Check the render method of `_anonymous$2`.
    at MillionBlock (https://vitejsvitetmqweb-ayit--5173--e809191e.local-credentialless.webcontainer.io/node_modules/.vite/deps/million_react.js?v=b5dfed3d:823:42)
    at _anonymous$2 (https://vitejsvitetmqweb-ayit--5173--e809191e.local-credentialless.webcontainer.io/src/App.jsx?t=1688610481787:7:21)
    at App

Renaming the variable helps avoid the error:
const inputRef = React.useRef(null);

But inputRef will never reference DOM node. It always in it's initial state with null value.
The bug doesn't reproduce if you reference something else other than DOM node.
To Reproduce
Here's an example: https://stackblitz.com/edit/vitejs-vite-tmqweb?file=src%2FApp.jsx
Device (please complete the following information):

OS: Linux 64-bit
Browser: Chrome 114.0.5735.198 (Official Build) (64-bit)
Version: Million 2.4.9, React 18.2.0, Vite 4.3.9

Good job @Semro, thank you very much for this! The team will definitely have a look at this.

Hello @Semro , we're looking at this bug more deeply. thanks for share this use case. 👀

Hello @Semro , we're looking at this bug more deeply. thanks for share this use case. 👀

Thank you Oliver!

Will be fixed in a release soon


templates not showing changes in cloned repo

I cannot make any changes to my Flask app which I cloned from: .https://github.com/cyrilrbt/canadian-nutrient-file
I tried editing template HTML files, the code in the routing in views.py but no changes are reflected.
I edited my views.py here: https://github.com/nyck33/canadian-nutrient-file/blob/master/cnf/views.py
to show index2.html and show2.html rather than the originals index.html and show.html.
But the routing still goes to the originals.
I used command bin/buildout to rebuild the app after making these changes just in case but it still goes to the original templates.
So I also tried editing the original templates as shown here on line 7 to 9 I inserted:

hello

but it's still not reflected.

I actually have no idea where "Food Standards" is coming from either because layout.html only has:
{% block content %} {% endblock %}

and index.html has a heading that does not appear anywhere:

Canadian Nutrient File Food Search

Expected Behavior

The rendered page should change to show edits to the template.
# Paste a minimal example that causes the problem.

my question on stackoverflow on this issue
Actual Behavior

The rendered page stays the same.
Paste the full traceback if there was an exception.

No exception.
Environment

Python version:  3.7
Flask version:1.1.2
Werkzeug version:1.0.1

Basically just trying to update a template which does not happen.

@ThiefMaster I have updated my question with an MVCE and additional info I would like assistance on.  Please re-open the issue.

Actually it is okay.  I made a new issue with full MVCE, links to repos, added a requirements.txt so everything can be recreated.


Bump npm deps

get-stdin wasn't bumped to ^5 because it introduced a breaking
change which would require use to drop support for node 0.10 or
add a promise library just for this module.

Any particular reason gaze didn't get a bump? node-sass:gaze ^0.5.1-->0.5.2(0.6.x available, minor bump to globule):globule 0.1.0(0.2.0 available, results in major bump to lodash):lodash . I tried doing it myself on the version gulp-sass uses-- TravisCI only builds correctly for node v0.10.x . node v0.10.41 and npm@latest is what I used for 'npm test' and the tests pass...
I looked at your TravisCI builds for node-sass which look ::borat;very nice:: and mine... not so much.
It worries me that node-sass only installs correctly for me on node v0.10.x (v0.10.41 was successful specifically). TravisCI only passes for the same v0.10.x for me. Your TravisCI runs pass from top to bottom...
I pull requested my minor bump of gaze for node-sass to the wrong repo/branch this morning.
Any advice for better regression testing on my part? This thing is awesome-- and more complicated than most of the stuff I work on.
I am running kubuntu 14.something (E530) and OS X El Capitan -- both with nvm (currently at 0.10.41 for both system and nvm) and the latest npm.
I've appended the steps and output of testing regarding the bump to a higher gaze dependency.
brad@E530 should prefix all the commands I ran.
I don't know enough about sass, node-sass, or gulp-sass to know if the output to the stderr of:
brad@E530:~/Desktop/node-sass$ npm test > testResults.txt
is inportant or not. But, I wanted to mention it. (The stderr messages are posted between the command and the tail of the document created below.)
<>
brad@E530:~/Desktop$ git clone --recursive git@github.com:bradchesney79/node-sass.git
Cloning into 'node-sass'...
remote: Counting objects: 18478, done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 18478 (delta 5), reused 0 (delta 0), pack-reused 18458
Receiving objects: 100% (18478/18478), 21.01 MiB | 975.00 KiB/s, done.
Resolving deltas: 100% (10684/10684), done.
Checking connectivity... done.
Submodule 'libsass' (git://github.com/sass/libsass.git) registered for path 'src/libsass'
Submodule 'test/sass-spec' (https://github.com/sass/sass-spec.git) registered for path 'test/fixtures/spec'
Cloning into 'src/libsass'...
remote: Counting objects: 13790, done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 13790 (delta 5), reused 0 (delta 0), pack-reused 13769
Receiving objects: 100% (13790/13790), 8.79 MiB | 2.54 MiB/s, done.
Resolving deltas: 100% (8114/8114), done.
Checking connectivity... done.
Submodule path 'src/libsass': checked out 'f47645c2ebb98c9e0c970f59820b239ab417dda3'
Cloning into 'test/fixtures/spec'...
remote: Counting objects: 15802, done.
remote: Compressing objects: 100% (51/51), done.
remote: Total 15802 (delta 27), reused 0 (delta 0), pack-reused 15735
Receiving objects: 100% (15802/15802), 2.03 MiB | 1016.00 KiB/s, done.
Resolving deltas: 100% (4589/4589), done.
Checking connectivity... done.
Submodule path 'test/fixtures/spec': checked out 'b089cff39e623de5c6d3c88ad021220df5c67657'
brad@E530:~/Desktop$ cd node-sass
brad@E530:~/Desktop/node-sass$ git submodule update --init --recursive
brad@E530:~/Desktop/node-sass$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
brad@E530:~/Desktop/node-sass$ git checkout -b forTravisCI
Switched to a new branch 'forTravisCI'
brad@E530:~/Desktop/node-sass$ vi package.json
brad@E530:~/Desktop/node-sass$ git status
On branch forTravisCI
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
    modified:   package.json

no changes added to commit (use "git add" and/or "git commit -a")
brad@E530:~/Desktop/node-sass$ git add .
brad@E530:~/Desktop/node-sass$ git commit -m"Bumped gaze dependency to next minor version"
[forTravisCI aa24d56] Bumped gaze dependency to next minor version
1 file changed, 2 insertions(+), 2 deletions(-)
brad@E530:~/Desktop/node-sass$ git push origin forTravisCI
Counting objects: 22, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 328 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
To git@github.com:bradchesney79/node-sass.git

[new branch]      forTravisCI -> forTravisCI

brad@E530:~/Desktop/node-sass$ git checkout master
Previous HEAD position was aa24d56... Bumped gaze dependency to next minor version
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
brad@E530:~/Desktop/node-sass$ git pull origin forTravisCI
From github.com:bradchesney79/node-sass

branch            forTravisCI -> FETCH_HEAD
Updating 877db52..aa24d56
Fast-forward
package.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
brad@E530:~/Desktop/node-sass$ git push origin master
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:bradchesney79/node-sass.git
877db52..aa24d56  master -> master

(TravisCI fails for all node versions-- except v0.10)
brad@E530:~/Desktop/node-sass$ nvm install v0.10.41
######################################################################## 100.0%
Now using node v0.10.41
brad@E530:~/Desktop/node-sass$ nvm alias default 0.10.41
default -> 0.10.41 (-> v0.10.41)
brad@E530:~/Desktop/node-sass$ git submodule update --init --recursive
brad@E530:~/Desktop/node-sass$ npm install
npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
npm WARN deprecated latest stable version. To upgrade to npm@2, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest-2
npm WARN deprecated
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with sudo, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to npm run-script and
npm WARN deprecated semver behavior.
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.12.0"} (current: {"node":"0.10.41","npm":"1.4.29"})

<EMAIL_ADDRESS>postinstall /home/brad/Desktop/node-sass/node_modules/cross-spawn/node_modules/spawn-sync
node postinstall

Installing native dependencies (this may take up to a minute)

<EMAIL_ADDRESS>install /home/brad/Desktop/node-sass/node_modules/gaze
node-gyp rebuild

make: Entering directory /home/brad/Desktop/node-sass/node_modules/gaze/build'   CXX(target) Release/obj.target/pathwatcher/src/main.o   CXX(target) Release/obj.target/pathwatcher/src/common.o   CXX(target) Release/obj.target/pathwatcher/src/handle_map.o ../src/handle_map.cc: In member function ‘bool HandleMap::Erase(WatcherHandle)’: ../src/handle_map.cc:41:26: warning: ‘void NanDispose(v8::Persistent<S>&) [with T = v8::Value]’ is deprecated (declared at ../node_modules/nan/nan.h:612) [-Wdeprecated-declarations]    NanDispose(iter->second); // Deprecated, use NanDisposePersistent when v0.12 lands                           ^ ../src/handle_map.cc: In member function ‘void HandleMap::Clear()’: ../src/handle_map.cc:48:28: warning: ‘void NanDispose(v8::Persistent<S>&) [with T = v8::Value]’ is deprecated (declared at ../node_modules/nan/nan.h:612) [-Wdeprecated-declarations]      NanDispose(iter->second); // Deprecated, use NanDisposePersistent when v0.12 lands                             ^   CXX(target) Release/obj.target/pathwatcher/src/pathwatcher_linux.o   SOLINK_MODULE(target) Release/obj.target/pathwatcher.node   SOLINK_MODULE(target) Release/obj.target/pathwatcher.node: Finished   COPY Release/pathwatcher.node make: Leaving directory /home/brad/Desktop/node-sass/node_modules/gaze/build'

<EMAIL_ADDRESS>install /home/brad/Desktop/node-sass
node scripts/install.js

Binary downloaded and installed at /home/brad/Desktop/node-sass/vendor/linux-x64-11/binding.node

<EMAIL_ADDRESS>postinstall /home/brad/Desktop/node-sass
node scripts/build.js

/home/brad/Desktop/node-sass/vendor/linux-x64-11/binding.node exists.
testing binary.
Binary is fine; exiting.
<EMAIL_ADDRESS>node_modules/get-stdin
<EMAIL_ADDRESS>node_modules/mocha-lcov-reporter
<EMAIL_ADDRESS>node_modules/async-foreach
<EMAIL_ADDRESS>node_modules/nan
<EMAIL_ADDRESS>node_modules/mkdirp
└──<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/chalk
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/glob
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/npmconf
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/rimraf
└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/sass-graph
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/mocha
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/meow
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/request
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/node-gyp
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/coveralls
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/jshint
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/istanbul
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/cross-spawn
├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/gaze
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>brad@E530:~/Desktop/node-sass$ rm /home/brad/.nvm/v0.10.41/bin/npm
brad@E530:~/Desktop/node-sass$ sudo npm -g install npm@latest
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/lib
└──<EMAIL_ADDRESS>brad@E530:~/Desktop/node-sass$ ln -s /usr/local/bin/npm /home/brad/.nvm/v0.10.41/bin/npm
brad@E530:~/Desktop/node-sass$ npm test > testResults.txt
DEPRECATION WARNING: Passing red, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 8 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/colors/basic/input.scss
DEPRECATION WARNING: Passing 24, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 6 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass/unquote/input.scss
WARNING: Mixin bar takes 3 arguments but 5 were passed.
on line 35 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass/var-args/input.scss
This will be an error in future versions of Sass.
WARNING: Mixin bar takes 3 arguments but 4 were passed.
on line 37 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass/var-args/input.scss
This will be an error in future versions of Sass.
DEPRECATION WARNING: Passing null, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 7 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1106/input.scss
DEPRECATION WARNING: Passing null, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 13 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1106/input.scss
DEPRECATION WARNING: Passing null, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 17 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1124/input.scss
DEPRECATION WARNING: Passing null, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 19 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1124/input.scss
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1240/input.scss:5 DEBUG: 1
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1240/input.scss:6 DEBUG: 2, 3
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1240/input.scss:7 DEBUG: 1 2, 3
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1240/input.scss:8 DEBUG: 1 2, 3
DEPRECATION WARNING: Passing "(-webkit-min-device-pixel-ratio: 2)", "(min-resolution: 192dpi)", a non-string value, to unquote()
will be an error in future versions of Sass.
on line 6 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1258/input.scss
DEPRECATION WARNING: Passing 3, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 2 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1291/input.scss
DEPRECATION WARNING: Passing -3, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 2 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1291/input.scss
DEPRECATION WARNING: Passing 5, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 7 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1291/input.scss
DEPRECATION WARNING: Passing -5, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 7 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1291/input.scss
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1331/input.scss:3 DEBUG: (foo: 1px, null: 2px, false: 3px, true: 4px)
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1331/input.scss:4 DEBUG: 1px
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1331/input.scss:5 DEBUG: 2px
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1331/input.scss:6 DEBUG: 3px
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1331/input.scss:7 DEBUG: 4px
/home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_1336/input.scss:1 DEBUG: null
DEPRECATION WARNING on line 5 of /home/brad/Desktop/node-sass/test/fixtures/spec/spec/libsass-closed-issues/issue_674/input.scss:
Naming a function "url" is disallowed and will be an error in future versions of Sass.
This name conflicts with an existing CSS function with special parse rules.
WARNING: Don't crash the ambulance, whatever you do
on line 2 of fixtures/spec/spec/misc/warn-directive/input.scss
tail -n3000 testResults.txt

<EMAIL_ADDRESS>pretest /home/brad/Desktop/node-sass
jshint bin lib scripts test

<EMAIL_ADDRESS>test /home/brad/Desktop/node-sass
mocha test

api
.render(options, callback)
  ✓ should compile sass to css with file

  ✓ should compile sass to css with outFile set to absolute url

  ✓ should compile sass to css with outFile set to relative url

  ✓ should compile sass to css with outFile and sourceMap set to relative url

  ✓ should compile generate map with sourceMapRoot pass-through option

  ✓ should compile sass to css with data

  ✓ should NOT compile empty data string

  ✓ should NOT compile without parameters

  ✓ should compile sass to css using indented syntax

  ✓ should throw error status 1 for bad input

  ✓ should compile with include paths

  ✓ should render with precision option

  ✓ should contain all included files in stats when data is passed

  ✓ should render with indentWidth and indentType options

  ✓ should render with linefeed option
.render(importer)

/Users/me/sass/lib/a.scss
  ✓ should still call the next importer with the resolved prev path when the previous importer returned both a file and contents property - issue #1219

  ✓ should override imports with "data" as input and fires callback with file and contents

  ✓ should override imports with "file" as input and fires callback with file and contents

  ✓ should override imports with "data" as input and returns file and contents

  ✓ should override imports with "file" as input and returns file and contents

  ✓ should override imports with "data" as input and fires callback with file

  ✓ should override imports with "file" as input and fires callback with file

  ✓ should override imports with "data" as input and returns file

  ✓ should override imports with "file" as input and returns file

  ✓ should fallback to default import behaviour if importer returns sass.NULL

  ✓ should fallback to default import behaviour if importer returns null for backwards compatibility

  ✓ should fallback to default import behaviour if importer returns undefined for backwards compatibility

  ✓ should fallback to default import behaviour if importer returns false for backwards compatibility

  ✓ should override imports with "data" as input and fires callback with contents

  ✓ should override imports with "file" as input and fires callback with contents

  ✓ should override imports with "data" as input and returns contents

  ✓ should override imports with "file" as input and returns contents

  ✓ should accept arrays of importers and return respect the order

  ✓ should be able to see its options in this.options

  ✓ should be able to access a persistent options object

  ✓ should copy all options properties

  ✓ should reflect user-defined error when returned as callback

  ✓ should reflect user-defined error with return

  ✓ should throw exception when importer returns an invalid value
.render(functions)

  ✓ should call custom defined nullary function

  ✓ should call custom function with multiple args

  ✓ should work with custom functions that return data asynchronously (53ms)

  ✓ should let custom functions call setter methods on wrapped sass values (number)

  ✓ should properly convert strings when calling custom functions

  ✓ should let custom functions call setter methods on wrapped sass values (string)

  ✓ should properly convert colors when calling custom functions

  ✓ should properly convert boolean when calling custom functions

  ✓ should let custom functions call setter methods on wrapped sass values (boolean)

  ✓ should properly convert lists when calling custom functions

  ✓ should properly convert maps when calling custom functions

  ✓ should properly convert null when calling custom functions

  ✓ should be possible to carry sass values across different renders

  ✓ should let us register custom functions without signatures

  ✓ should fail when returning anything other than a sass value from a custom function

  ✓ should properly bubble up standard JS errors thrown by custom functions

  ✓ should properly bubble up unknown errors thrown by custom functions

  ✓ should properly bubble up errors from sass value constructors

  ✓ should properly bubble up errors from sass value setters

  ✓ should fail when trying to set a bare number as the List item

  ✓ should fail when trying to set a bare Object as the List item

  ✓ should fail when trying to set a bare Object as the Map key

  ✓ should fail when trying to set a bare Object as the Map value

  ✓ should always map null, true and false to the same (immutable) object
  should properly bubble up errors from sass color constructor

    ✓ four booleans

    ✓ two arguments

    ✓ single string argument
.render({stats: {}})

  ✓ should provide a start timestamp

  ✓ should provide an end timestamp

  ✓ should provide a duration

  ✓ should contain the given entry file

  ✓ should contain an array of all included files

  ✓ should contain array with the entry if there are no import statements

  ✓ should state `data` as entry file

  ✓ should contain an empty array as includedFiles
.renderSync(options)

  ✓ should compile sass to css with file

  ✓ should compile sass to css with outFile set to absolute url

  ✓ should compile sass to css with outFile set to relative url

  ✓ should compile sass to css with outFile and sourceMap set to relative url

  ✓ should compile generate map with sourceMapRoot pass-through option

  ✓ should compile sass to css with data

  ✓ should compile sass to css using indented syntax

  ✓ should NOT compile empty data string

  ✓ should NOT compile without any input

  ✓ should throw error for bad input
.renderSync(importer)

  ✓ should override imports with "data" as input and returns file and contents

  ✓ should override imports with "file" as input and returns file and contents

  ✓ should override imports with "data" as input and returns file

  ✓ should override imports with "file" as input and returns file

  ✓ should override imports with "data" as input and returns contents

  ✓ should override imports with "file" as input and returns contents

  ✓ should fallback to default import behaviour if importer returns sass.NULL

  ✓ should fallback to default import behaviour if importer returns null for backwards compatibility

  ✓ should fallback to default import behaviour if importer returns undefined for backwards compatibility

  ✓ should fallback to default import behaviour if importer returns false for backwards compatibility

  ✓ should accept arrays of importers and return respect the order

  ✓ should be able to see its options in this.options

  ✓ should throw user-defined error

  ✓ should throw exception when importer returns an invalid value
.renderSync(functions)

  ✓ should call custom function in sync mode

  ✓ should return a list of selectors after calling the headings custom function

  ✓ should let custom function invoke sass types constructors without the `new` keyword

  ✓ should let us register custom functions without signatures

  ✓ should fail when returning anything other than a sass value from a custom function

  ✓ should properly bubble up standard JS errors thrown by custom functions

  ✓ should properly bubble up unknown errors thrown by custom functions

  ✓ should properly bubble up errors from sass value getters/setters/constructors
.renderSync({stats: {}})

  ✓ should provide a start timestamp

  ✓ should provide an end timestamp

  ✓ should provide a duration

  ✓ should contain the given entry file

  ✓ should contain an array of all included files

  ✓ should contain array with the entry if there are no import statements

  ✓ should state `data` as entry file

  ✓ should contain an empty array as includedFiles
.info

  ✓ should return a correct version info

cli
node-sass < in.scss
  ✓ should read data from stdin (214ms)

  ✓ should compile sass using the --indented-syntax option (212ms)

  ✓ should compile with the --quiet option (218ms)

  ✓ should compile with the --output-style option (216ms)

  ✓ should compile with the --source-comments option (215ms)

  ✓ should render with indentWidth and indentType options (223ms)

  ✓ should render with linefeed option (220ms)
node-sass in.scss

  ✓ should compile a scss file (221ms)

  ✓ should compile a scss file to custom destination (217ms)

  ✓ should compile with the --include-path option (205ms)

  ✓ should compile silently using the --quiet option (214ms)

  ✓ should still report errors with the --quiet option (224ms)

  ✓ should not exit with the --watch option (106ms)
  - should emit `warn` on file change when using --watch option
  - should emit nothing on file change when using --watch and --quiet options
  - should render all watched files
  - should watch the full scss dep tree for a single file (scss)
  - should watch the full sass dep tree for a single file (sass)
node-sass --output directory
  - should watch whole directory
  - should compile all changed files in watched directory
node-sass in.scss --output out.css

  ✓ should compile a scss file to build.css (255ms)

  ✓ should compile with the --source-map option (316ms)

  ✓ should omit sourceMappingURL if --omit-source-map-url flag is used (223ms)

  ✓ should compile with the --source-root option (232ms)

  ✓ should compile with the --source-map-embed option and no outfile (221ms)
node-sass sass/ --output css/

  ✓ should create the output directory (249ms)

  ✓ should compile all files in the folder (246ms)

  ✓ should compile with --source-map set to directory (241ms)

  ✓ should skip files with an underscore (242ms)

  ✓ should ignore nested files if --recursive false (239ms)

  ✓ should error if no output directory is provided (222ms)

  ✓ should error if output directory is not a directory (222ms)
node-sass in.scss --output path/to/file/out.css

  ✓ should create the output directory (227ms)
node-sass --follow --output output-dir input-dir

  ✓ should compile with the --follow option (234ms)
importer

  ✓ should override imports and fire callback with file and contents (221ms)

  ✓ should override imports and fire callback with file (220ms)

  ✓ should override imports and fire callback with data (222ms)

  ✓ should override imports and return file and contents (221ms)

  ✓ should override imports and return file (221ms)

  ✓ should override imports and return data (217ms)

  ✓ should accept arrays of importers and return respect the order (242ms)

  ✓ should return error for invalid importer file path (216ms)

  ✓ should reflect user-defined Error (211ms)
functions

  ✓ should let custom functions call setter methods on wrapped sass values (number) (230ms)

  ✓ should properly convert strings when calling custom functions (225ms)

lowlevel
✓ fail with options not an object

✓ data context with options.data not provided

✓ data context with both options.data and options.file not provided

✓ file context with both options.data and options.file not provided

✓ file context with options.file not provided, options.data given

✓ fail with options.result not provided

✓ fail with options.result not an object

✓ fail with options.result.stats not provided

✓ fail with options.result.stats not an object

✓ options.indentWidth not provided

✓ empty data string

✓ empty file string

runtime parameters
configuration precedence should be respected
SASS_BINARY_NAME
    ✓ command line argument

    ✓ environment variable

    ✓ npm config variable

    ✓ package.json
  SASS_BINARY_SITE

    ✓ command line argument

    ✓ environment variable

    ✓ npm config variable

    ✓ package.json
  SASS_BINARY_PATH

    ✓ command line argument

    ✓ environment variable

    ✓ npm config variable

    ✓ package.json

library detection
✓ should throw error when libsass binary is missing.

spec
test/sass-spec directory
  ✓ should be a cloned into place
basic

  ✓ 00_empty

  ✓ 01_simple_css

  ✓ 02_simple_nesting

  ✓ 03_simple_variable

  ✓ 04_basic_variables

  ✓ 05_empty_levels

  ✓ 06_nesting_and_comments

  ✓ 07_nested_simple_selector_groups

  ✓ 08_selector_combinators

  ✓ 09_selector_groups_and_combinators

  ✓ 10_classes_and_ids

  ✓ 11_attribute_selectors

  ✓ 13_back_references

  ✓ 14_imports

  ✓ 15_arithmetic_and_lists

  ✓ 16_hex_arithmetic

  ✓ 17_basic_mixins

  ✓ 18_mixin_scope

  ✓ 19_full_mixin_craziness

  ✓ 20_scoped_variables

  ✓ 21_one_builtin_function

  ✓ 22_colors_with_alpha

  ✓ 23_basic_value_interpolation

  ✓ 24_namespace_properties

  ✓ 25_basic_string_interpolation

  ✓ 26_selector_interpolation

  ✓ 27_media_queries

  ✓ 28_url

  ✓ 29_if

  ✓ 30_if_in_function

  ✓ 31_if_in_mixin

  ✓ 32_percentages

  ✓ 33_ambiguous_imports

  ✓ 35_varargs_false

  ✓ 36_extra_commas_in_selectors

  ✓ 37_url_expressions

  ✓ 38_expressions_in_at_directives

  ✓ 39_dash_match_attribute_selector

  ✓ 40_pseudo_class_identifier_starting_with_n

  ✓ 41_slashy_urls

  ✓ 42_css_imports

  ✓ 43_str_length

  ✓ 44_bem_selectors

  ✓ 45_str_insert

  ✓ 46_str_index

  ✓ 48_case_conversion

  ✓ 49_interpolants_in_css_imports

  ✓ 50_wrapped_pseudo_selectors

  ✓ 51_trailing_commas_in_list

  ✓ 52_interchangeable_hyphens_underscores

  ✓ 53_escaped_quotes

  ✓ 54_adjacent_identifiers_with_hyphens

  ✓ 55_variable_exists

  ✓ 56_global_variable_exists

  ✓ 57_function_exists

  ✓ 58_mixin_exists

  ✓ 59_if_expression

  ✓ 60_call
colors

  ✓ adjust-color

  ✓ adjust-hue

  ✓ basic

  ✓ change-color

  ✓ complement

  ✓ desaturate

  ✓ fade-in

  ✓ fade-out

  ✓ saturate

  ✓ saturation

  ✓ scale-color
css

  ✓ bizarrely_formatted_comments

  ✓ blockless_directive_without_semicolon

  ✓ closing_line_comment_end_with_compact_output

  ✓ directive_with_lots_of_whitespace

  ✓ empty_block_directive

  ✓ ms_long_filter_syntax

  ✓ multiple_comments
extend-tests

  ✓ 001_test_basic

  ✓ 002_test_basic

  ✓ 003_test_basic

  ✓ 004_test_basic

  ✓ 005_test_multiple_targets

  ✓ 006_test_multiple_extendees

  ✓ 007_test_multiple_extends_with_single_extender_and_single_target

  ✓ 008_test_multiple_extends_with_single_extender_and_single_target

  ✓ 009_test_multiple_extends_with_multiple_extenders_and_single_target

  ✓ 010_test_multiple_extends_with_multiple_extenders_and_single_target

  ✓ 011_test_chained_extends

  ✓ 012_test_dynamic_extendee

  ✓ 013_test_dynamic_extendee

  ✓ 014_test_nested_target

  ✓ 015_test_target_with_child

  ✓ 016_test_class_unification

  ✓ 017_test_class_unification

  ✓ 018_test_id_unification

  ✓ 019_test_id_unification

  ✓ 020_test_universal_unification_with_simple_target

  ✓ 021_test_universal_unification_with_simple_target

  ✓ 022_test_universal_unification_with_simple_target

  ✓ 023_test_universal_unification_with_simple_target

  ✓ 024_test_universal_unification_with_simple_target

  ✓ 025_test_universal_unification_with_namespaceless_universal_target

  ✓ 026_test_universal_unification_with_namespaceless_universal_target

  ✓ 027_test_universal_unification_with_namespaceless_universal_target

  ✓ 028_test_universal_unification_with_namespaceless_universal_target

  ✓ 029_test_universal_unification_with_namespaceless_universal_target

  ✓ 030_test_universal_unification_with_namespaceless_universal_target

  ✓ 031_test_universal_unification_with_namespaced_universal_target

  ✓ 032_test_universal_unification_with_namespaced_universal_target

  ✓ 033_test_universal_unification_with_namespaced_universal_target

  ✓ 034_test_universal_unification_with_namespaceless_element_target

  ✓ 035_test_universal_unification_with_namespaceless_element_target

  ✓ 036_test_universal_unification_with_namespaceless_element_target

  ✓ 037_test_universal_unification_with_namespaceless_element_target

  ✓ 038_test_universal_unification_with_namespaceless_element_target

  ✓ 039_test_universal_unification_with_namespaceless_element_target

  ✓ 040_test_universal_unification_with_namespaced_element_target

  ✓ 041_test_universal_unification_with_namespaced_element_target

  ✓ 042_test_universal_unification_with_namespaced_element_target

  ✓ 043_test_element_unification_with_simple_target

  ✓ 044_test_element_unification_with_simple_target

  ✓ 045_test_element_unification_with_simple_target

  ✓ 046_test_element_unification_with_simple_target

  ✓ 047_test_element_unification_with_namespaceless_universal_target

  ✓ 048_test_element_unification_with_namespaceless_universal_target

  ✓ 049_test_element_unification_with_namespaceless_universal_target

  ✓ 050_test_element_unification_with_namespaceless_universal_target

  ✓ 051_test_element_unification_with_namespaceless_universal_target

  ✓ 052_test_element_unification_with_namespaceless_universal_target

  ✓ 053_test_element_unification_with_namespaced_universal_target

  ✓ 054_test_element_unification_with_namespaced_universal_target

  ✓ 055_test_element_unification_with_namespaced_universal_target

  ✓ 056_test_element_unification_with_namespaceless_element_target

  ✓ 057_test_element_unification_with_namespaceless_element_target

  ✓ 058_test_element_unification_with_namespaceless_element_target

  ✓ 059_test_element_unification_with_namespaceless_element_target

  ✓ 060_test_element_unification_with_namespaceless_element_target

  ✓ 061_test_element_unification_with_namespaceless_element_target

  ✓ 062_test_element_unification_with_namespaced_element_target

  ✓ 063_test_element_unification_with_namespaced_element_target

  ✓ 064_test_element_unification_with_namespaced_element_target

  ✓ 065_test_attribute_unification

  ✓ 066_test_attribute_unification

  ✓ 067_test_attribute_unification

  ✓ 068_test_attribute_unification

  ✓ 069_test_attribute_unification

  ✓ 070_test_pseudo_unification

  ✓ 071_test_pseudo_unification

  ✓ 072_test_pseudo_unification

  ✓ 073_test_pseudo_unification

  ✓ 074_test_pseudo_unification

  ✓ 075_test_pseudo_unification

  ✓ 076_test_pseudo_unification

  ✓ 077_test_pseudo_unification

  ✓ 078_test_pseudoelement_remains_at_end_of_selector

  ✓ 079_test_pseudoelement_remains_at_end_of_selector

  ✓ 080_test_pseudoclass_remains_at_end_of_selector

  ✓ 081_test_pseudoclass_remains_at_end_of_selector

  ✓ 082_test_not_remains_at_end_of_selector

  ✓ 083_test_pseudoelement_goes_lefter_than_pseudoclass

  ✓ 084_test_pseudoelement_goes_lefter_than_pseudoclass

  ✓ 085_test_pseudoelement_goes_lefter_than_not

  ✓ 086.1_test_pseudoelement_goes_lefter_than_not

  ✓ 086_test_pseudoelement_goes_lefter_than_not

  ✓ 087_test_negation_unification

  ✓ 088_test_negation_unification

  ✓ 089_test_negation_unification

  ✓ 090_test_comma_extendee

  ✓ 091_test_redundant_selector_elimination

  ✓ 092_test_long_extendee

  ✓ 093_test_long_extendee_matches_supersets

  ✓ 094_test_long_extendee_runs_unification

  ✓ 095_test_long_extender

  ✓ 096_test_long_extender_runs_unification

  ✓ 097_test_nested_extender

  ✓ 098_test_nested_extender_runs_unification

  ✓ 099_test_nested_extender_alternates_parents

  ✓ 100_test_nested_extender_unifies_identical_parents

  ✓ 101_test_nested_extender_unifies_common_substring

  ✓ 102_test_nested_extender_unifies_common_subseq

  ✓ 103_test_nested_extender_chooses_first_subseq

  ✓ 105_test_nested_extender_counts_extended_superselectors

  ✓ 106_test_nested_extender_with_child_selector

  ✓ 107_test_nested_extender_finds_common_selectors_around_child_selector

  ✓ 108_test_nested_extender_finds_common_selectors_around_child_selector

  ✓ 109_test_nested_extender_doesnt_find_common_selectors_around_adjacent_sibling_selector

  ✓ 110_test_nested_extender_doesnt_find_common_selectors_around_adjacent_sibling_selector

  ✓ 111_test_nested_extender_doesnt_find_common_selectors_around_adjacent_sibling_selector

  ✓ 112_test_nested_extender_doesnt_find_common_selectors_around_sibling_selector

  ✓ 113_test_nested_extender_doesnt_find_common_selectors_around_sibling_selector

  ✓ 114_test_nested_extender_doesnt_find_common_selectors_around_sibling_selector

  ✓ 115_test_nested_extender_doesnt_find_common_selectors_around_reference_selector

  ✓ 116_test_nested_extender_doesnt_find_common_selectors_around_reference_selector

  ✓ 117_test_nested_extender_doesnt_find_common_selectors_around_reference_selector

  ✓ 118_test_nested_extender_with_early_child_selectors_doesnt_subseq_them

  ✓ 119_test_nested_extender_with_early_child_selectors_doesnt_subseq_them

  ✓ 120_test_nested_extender_with_child_selector_unifies

  ✓ 121_test_nested_extender_with_child_selector_unifies

  ✓ 122_test_nested_extender_with_child_selector_unifies

  ✓ 123_test_nested_extender_with_early_child_selector

  ✓ 124_test_nested_extender_with_early_child_selector

  ✓ 125_test_nested_extender_with_early_child_selector

  ✓ 126_test_nested_extender_with_early_child_selector

  ✓ 127_test_nested_extender_with_early_child_selector

  ✓ 128_test_nested_extender_with_sibling_selector

  ✓ 129_test_nested_extender_with_hacky_selector

  ✓ 130_test_nested_extender_with_hacky_selector

  ✓ 131_test_nested_extender_merges_with_same_selector

  ✓ 132_test_nested_extender_with_child_selector_merges_with_same_selector

  ✓ 133_test_combinator_unification_for_hacky_combinators

  ✓ 134_test_combinator_unification_for_hacky_combinators

  ✓ 135_test_combinator_unification_for_hacky_combinators

  ✓ 136_test_combinator_unification_for_hacky_combinators

  ✓ 137_test_combinator_unification_for_hacky_combinators

  ✓ 138_test_combinator_unification_for_hacky_combinators

  ✓ 139_test_combinator_unification_for_hacky_combinators

  ✓ 140_test_combinator_unification_double_tilde

  ✓ 141_test_combinator_unification_double_tilde

  ✓ 142_test_combinator_unification_double_tilde

  ✓ 143_test_combinator_unification_double_tilde

  ✓ 144_test_combinator_unification_tilde_plus

  ✓ 145_test_combinator_unification_tilde_plus

  ✓ 146_test_combinator_unification_tilde_plus

  ✓ 147_test_combinator_unification_tilde_plus

  ✓ 148_test_combinator_unification_tilde_plus

  ✓ 149_test_combinator_unification_tilde_plus

  ✓ 150_test_combinator_unification_tilde_plus

  ✓ 151_test_combinator_unification_tilde_plus

  ✓ 152_test_combinator_unification_angle_sibling

  ✓ 153_test_combinator_unification_angle_sibling

  ✓ 154_test_combinator_unification_angle_sibling

  ✓ 155_test_combinator_unification_angle_sibling

  ✓ 156_test_combinator_unification_double_angle

  ✓ 157_test_combinator_unification_double_angle

  ✓ 158_test_combinator_unification_double_angle

  ✓ 159_test_combinator_unification_double_angle

  ✓ 160_test_combinator_unification_double_plus

  ✓ 161_test_combinator_unification_double_plus

  ✓ 162_test_combinator_unification_double_plus

  ✓ 163_test_combinator_unification_double_plus

  ✓ 164_test_combinator_unification_angle_space

  ✓ 165_test_combinator_unification_angle_space

  ✓ 166_test_combinator_unification_angle_space

  ✓ 167_test_combinator_unification_angle_space

  ✓ 168_test_combinator_unification_angle_space

  ✓ 169_test_combinator_unification_angle_space

  ✓ 170_test_combinator_unification_plus_space

  ✓ 171_test_combinator_unification_plus_space

  ✓ 172_test_combinator_unification_plus_space

  ✓ 173_test_combinator_unification_plus_space

  ✓ 174_test_combinator_unification_plus_space

  ✓ 175_test_combinator_unification_plus_space

  ✓ 176_test_combinator_unification_nested

  ✓ 177_test_combinator_unification_nested

  ✓ 178_test_combinator_unification_with_newlines

  ✓ 179_test_extend_self_loop

  ✓ 182_test_nested_extend_loop

  ✓ 183_test_multiple_extender_merges_with_superset_selector

  ✓ 184_test_control_flow_if

  ✓ 185_test_control_flow_for

  ✓ 186_test_control_flow_while

  ✓ 187_test_basic_placeholder_selector

  ✓ 188_test_unused_placeholder_selector

  ✓ 189_test_placeholder_descendant_selector

  ✓ 190_test_semi_placeholder_selector

  ✓ 191_test_placeholder_selector_with_multiple_extenders

  ✓ 192_test_placeholder_interpolation

  ✓ 193_test_media_in_placeholder_selector

  ✓ 194_test_extend_within_media

  ✓ 195_test_extend_within_unknown_directive

  ✓ 196_test_extend_within_nested_directives

  ✓ 197_test_extend_within_disparate_media

  ✓ 198_test_extend_within_disparate_unknown_directive

  ✓ 199_test_extend_within_disparate_nested_directives

  ✓ 206_test_extend_succeeds_when_one_extension_fails_but_others_dont

  ✓ 207_test_optional_extend_succeeds_when_extendee_doesnt_exist

  ✓ 208_test_optional_extend_succeeds_when_extension_fails

  ✓ 209_test_pseudo_element_superselector

  ✓ 210_test_pseudo_element_superselector

  ✓ 211_test_pseudo_element_superselector

  ✓ 212_test_pseudo_element_superselector

  ✓ 213_test_pseudo_element_superselector

  ✓ 214_test_pseudo_element_superselector

  ✓ 215_test_multiple_source_redundancy_elimination

  ✓ 216_test_nested_sibling_extend

  ✓ 217_test_parent_and_sibling_extend

  ✓ 218_test_nested_extend_specificity

  ✓ 219_test_nested_double_extend_optimization

  ✓ 220_test_extend_in_double_nested_media_query

  ✓ 221_test_partially_failed_extend

  ✓ 222_test_newline_near_combinator

  ✓ 223_test_duplicated_selector_with_newlines

  ✓ 224_test_nested_selector_with_child_selector_hack_extendee

  ✓ 225_test_nested_selector_with_child_selector_hack_extender

  ✓ 226_test_nested_selector_with_child_selector_hack_extender_and_extendee

  ✓ 227_test_nested_selector_with_child_selector_hack_extender_and_sibling_selector_extendee

  ✓ 228_test_nested_selector_with_child_selector_hack_extender_and_extendee_and_newline

  ✓ 229_test_extended_parent_and_child_redundancy_elimination

  ✓ 230_test_extend_redundancy_elimination_when_it_would_reduce_specificity

  ✓ 231_test_extend_redundancy_elimination_when_it_would_preserve_specificity

  ✓ 232_test_extend_redundancy_elimination_never_eliminates_base_selector

  ✓ 233_test_extend_cross_branch_redundancy_elimination

  ✓ 234_test_extend_cross_branch_redundancy_elimination

  ✓ 235_extend_with_universal_selector

  ✓ does_not_move_page_block_in_media

  ✓ issue_146
libsass

  ✓ arg-eval

  ✓ at-stuff

  ✓ bool

  ✓ bourbon

  ✓ calc

  ✓ charset

  ✓ color-names

  ✓ conversions

  ✓ css-import

  ✓ css_nth_selectors

  ✓ css_unicode

  ✓ div

  ✓ env

  ✓ eq

  ✓ filter-functions

  ✓ http_import

  ✓ image-url

  ✓ import

  ✓ inh

  ✓ inheritance

  ✓ interpolated-function-call

  ✓ interpolated-urls

  ✓ keyframes

  ✓ length

  ✓ list-evaluation

  ✓ lists

  ✓ media

  ✓ media-hoisting

  ✓ mixin

  ✓ mixins-and-media-queries

  ✓ multi-blocks

  ✓ placeholder-mediaquery

  ✓ placeholder-nested

  ✓ rel

  ✓ scale

  ✓ selector_interpolation_in_string

  ✓ selectors

  ✓ test

  ✓ unary-ops

  ✓ unitless

  ✓ units

  ✓ unquote

  ✓ url

  ✓ var-args

  ✓ variables_in_media
libsass-closed-issues

  ✓ 47_str_slice

  ✓ issue_1007

  ✓ issue_1016

  ✓ issue_1025

  ✓ issue_1029

  ✓ issue_1030

  ✓ issue_1036

  ✓ issue_1043

  ✓ issue_1060

  ✓ issue_1061

  ✓ issue_1063

  ✓ issue_1074

  ✓ issue_1075

  ✓ issue_1080

  ✓ issue_1081

  ✓ issue_1082

  ✓ issue_1087

  ✓ issue_1091

  ✓ issue_1092

  ✓ issue_1098

  ✓ issue_1102

  ✓ issue_1103

  ✓ issue_1106

  ✓ issue_1107

  ✓ issue_1115

  ✓ issue_1121

  ✓ issue_1124

  ✓ issue_1127

  ✓ issue_113

  ✓ issue_1130

  ✓ issue_1132

  ✓ issue_1153

  ✓ issue_1162

  ✓ issue_1163

  ✓ issue_1167

  ✓ issue_1168

  ✓ issue_1169

  ✓ issue_1171

  ✓ issue_1178

  ✓ issue_1188

  ✓ issue_1192

  ✓ issue_1206

  ✓ issue_1207

  ✓ issue_1208

  ✓ issue_1214

  ✓ issue_1215

  ✓ issue_1218

  ✓ issue_1224

  ✓ issue_1230

  ✓ issue_1231

  ✓ issue_1240

  ✓ issue_1248

  ✓ issue_1251

  ✓ issue_1253

  ✓ issue_1255

  ✓ issue_1257

  ✓ issue_1258

  ✓ issue_1259

  ✓ issue_1260

  ✓ issue_1263

  ✓ issue_1269

  ✓ issue_1271

  ✓ issue_1273

  ✓ issue_1277

  ✓ issue_1279

  ✓ issue_1281

  ✓ issue_1283

  ✓ issue_1285

  ✓ issue_1291

  ✓ issue_1297

  ✓ issue_1298

  ✓ issue_1301

  ✓ issue_1303

  ✓ issue_1304

  ✓ issue_1305

  ✓ issue_1323

  ✓ issue_1331

  ✓ issue_1332

  ✓ issue_1336

  ✓ issue_1355

  ✓ issue_137

  ✓ issue_1370

  ✓ issue_1376

  ✓ issue_1393

  ✓ issue_1394

  ✓ issue_1396

  ✓ issue_1398

  ✓ issue_1399

  ✓ issue_1404

  ✓ issue_1405

  ✓ issue_1413

  ✓ issue_1422

  ✓ issue_1425

  ✓ issue_143

  ✓ issue_1434

  ✓ issue_1437

  ✓ issue_1438

  ✓ issue_1440

  ✓ issue_1448

  ✓ issue_1459

  ✓ issue_1482

  ✓ issue_1484

  ✓ issue_1486

  ✓ issue_1487

  ✓ issue_1488

  ✓ issue_151

  ✓ issue_152

  ✓ issue_1535

  ✓ issue_1557

  ✓ issue_1566

  ✓ issue_1567

  ✓ issue_1568

  ✓ issue_1569

  ✓ issue_1570

  ✓ issue_1574

  ✓ issue_1577

  ✓ issue_1579

  ✓ issue_1584

  ✓ issue_1601

  ✓ issue_1604

  ✓ issue_1606

  ✓ issue_1610

  ✓ issue_1622

  ✓ issue_1624

  ✓ issue_1629

  ✓ issue_1632

  ✓ issue_1634

  ✓ issue_1640

  ✓ issue_1648

  ✓ issue_1658

  ✓ issue_1667

  ✓ issue_1669

  ✓ issue_1671

  ✓ issue_1672

  ✓ issue_1673

  ✓ issue_1685

  ✓ issue_1715

  ✓ issue_224

  ✓ issue_261

  ✓ issue_279

  ✓ issue_308

  ✓ issue_338

  ✓ issue_344

  ✓ issue_346

  ✓ issue_349

  ✓ issue_361

  ✓ issue_368

  ✓ issue_394

  ✓ issue_439

  ✓ issue_442

  ✓ issue_452

  ✓ issue_453

  ✓ issue_456

  ✓ issue_469

  ✓ issue_472

  ✓ issue_478

  ✓ issue_485

  ✓ issue_487

  ✓ issue_492

  ✓ issue_495

  ✓ issue_502

  ✓ issue_506

  ✓ issue_509

  ✓ issue_510

  ✓ issue_512

  ✓ issue_534

  ✓ issue_535

  ✓ issue_548

  ✓ issue_549

  ✓ issue_552

  ✓ issue_553

  ✓ issue_555

  ✓ issue_556

  ✓ issue_557

  ✓ issue_574

  ✓ issue_575

  ✓ issue_577

  ✓ issue_578

  ✓ issue_579

  ✓ issue_590

  ✓ issue_592

  ✓ issue_593

  ✓ issue_595

  ✓ issue_602

  ✓ issue_610

  ✓ issue_613

  ✓ issue_614

  ✓ issue_615

  ✓ issue_617

  ✓ issue_622

  ✓ issue_623

  ✓ issue_636

  ✓ issue_639

  ✓ issue_641

  ✓ issue_643

  ✓ issue_644

  ✓ issue_646

  ✓ issue_652

  ✓ issue_660

  ✓ issue_672

  ✓ issue_674

  ✓ issue_683

  ✓ issue_688

  ✓ issue_694

  ✓ issue_698

  ✓ issue_699

  ✓ issue_700

  ✓ issue_701

  ✓ issue_702

  ✓ issue_703

  ✓ issue_708

  ✓ issue_712

  ✓ issue_733

  ✓ issue_736

  ✓ issue_738

  ✓ issue_740

  ✓ issue_748

  ✓ issue_759

  ✓ issue_760

  ✓ issue_763

  ✓ issue_783

  ✓ issue_784

  ✓ issue_803

  ✓ issue_813

  ✓ issue_815

  ✓ issue_817

  ✓ issue_820

  ✓ issue_823

  ✓ issue_828

  ✓ issue_829

  ✓ issue_857

  ✓ issue_859

  ✓ issue_864

  ✓ issue_870

  ✓ issue_873

  ✓ issue_877

  ✓ issue_883

  ✓ issue_884

  ✓ issue_890

  ✓ issue_893

  ✓ issue_894

  ✓ issue_930

  ✓ issue_931

  ✓ issue_941

  ✓ issue_942

  ✓ issue_943

  ✓ issue_945

  ✓ issue_947

  ✓ issue_948

  ✓ issue_950

  ✓ issue_976

  ✓ issue_978

  ✓ issue_980

  ✓ issue_988

  ✓ issue_992
libsass-ok-issues

  ✓ issue_1259

  ✓ issue_1295

  ✓ issue_1298

  ✓ issue_1305

  ✓ issue_1328

  ✓ issue_1332

  ✓ issue_1333
maps

  ✓ map-get

  ✓ map-has-key

  ✓ map-keys

  ✓ map-merge

  ✓ map-remove

  ✓ map-values
misc

  ✓ JMA-pseudo-test

  ✓ directive_interpolation

  ✓ empty_content

  ✓ error-directive

  ✓ import_with_interpolation

  ✓ lang-bug

  ✓ media_interpolation

  ✓ mixin_content

  ✓ namespace_properties_with_script_value

  ✓ negative_numbers

  ✓ selector_interpolation_before_element_name

  ✓ selector_only_interpolation

  ✓ trailing_comma_in_selector

  ✓ unicode_variables

  ✓ warn-directive
number-functions

  ✓ abs

  ✓ ceil

  ✓ floor

  ✓ max

  ✓ min

  ✓ percentage

  ✓ random

  ✓ round
sass

  ✓ imported
scope

  ✓ clash

  ✓ each

  ✓ for

  ✓ function

  ✓ if

  ✓ mixin

  ✓ nested

  ✓ root

  ✓ ruleset

  ✓ while
scss

  ✓ almost_ambiguous_nested_rules_and_declarations

  ✓ alpha

  ✓ append

  ✓ arglist

  ✓ backrefs-in-selector-groups

  ✓ backslash

  ✓ basic_function

  ✓ basic_mixins

  ✓ basic_prop_name_interpolation

  ✓ basic_selector_interpolation

  ✓ blimp

  ✓ block_comment_in_script

  ✓ cfunc

  ✓ classes-and-ids

  ✓ color_output

  ✓ comment_after_if_directive

  ✓ comparable

  ✓ composed-args

  ✓ concat

  ✓ cons-up

  ✓ css_basic_scss

  ✓ css_block_directive_with_semicolon

  ✓ css_cdo_and_cdc_ignored_at_toplevel

  ✓ css_crazy_comments

  ✓ css_empty_declarations

  ✓ css_empty_rule

  ✓ css_import_directive

  ✓ css_invisible_comments

  ✓ css_property_comments

  ✓ css_rule_comments

  ✓ css_selector_comments

  ✓ css_selector_hacks

  ✓ css_spaceless_combo_selectors

  ✓ css_unary_ops

  ✓ default-args

  ✓ default-parameters

  ✓ default-vars-in-default-params

  ✓ directives-in-propsets

  ✓ each

  ✓ each_directive

  ✓ each_in_functions

  ✓ for

  ✓ for_directive

  ✓ for_in_functions

  ✓ function-names

  ✓ function_args

  ✓ functions

  ✓ functions-and-mixins

  ✓ guard_assign

  ✓ hey1

  ✓ hey2

  ✓ huge (477ms)

  ✓ hyphen-interpolated

  ✓ ie-backslash

  ✓ ie-functions

  ✓ ie-hex-str

  ✓ if

  ✓ if-in-mixin

  ✓ if-in-propset

  ✓ if_directive

  ✓ imp

  ✓ important

  ✓ important-in-arglist

  ✓ index

  ✓ interpolated-selectors

  ✓ interpolated-strings

  ✓ interpolation

  ✓ interpolation_with_bracket_on_next_line

  ✓ keyword_args_in_functions

  ✓ lang

  ✓ line_comment_in_script

  ✓ long-selector

  ✓ media-with-interpolation

  ✓ media2

  ✓ mix

  ✓ mixin-content

  ✓ mixin-content-selectors

  ✓ mixin-content-with-no-block

  ✓ mixin_with_keyword_args

  ✓ mixins_with_args

  ✓ mixins_with_empty_args

  ✓ multiline-var

  ✓ multiline_var

  ✓ namespace_properties

  ✓ namespace_properties_with_value

  ✓ negation

  ✓ nested-extend

  ✓ nested_namespace_properties

  ✓ nested_rules

  ✓ nested_rules_with_declarations

  ✓ nested_rules_with_fancy_selectors

  ✓ newlines_in_selectors

  ✓ no_namespace_properties_without_space

  ✓ null

  ✓ numbers

  ✓ one_line_comments

  ✓ parent_selectors

  ✓ passing_all_as_keyword_args_in_opposite_order

  ✓ passing_required_args_as_a_keyword_arg

  ✓ percentages

  ✓ placeholder

  ✓ placeholder-with-media

  ✓ precision

  ✓ prop_name_interpolation_after_hyphen

  ✓ prop_name_only_interpolation

  ✓ property_interpolation_at_dashes

  ✓ quotes-in-interpolated-strings

  ✓ retina-image

  ✓ sass_script

  ✓ selector_interpolation_at_attr_beginning

  ✓ selector_interpolation_at_class_begininng

  ✓ selector_interpolation_at_id_begininng

  ✓ selector_interpolation_at_pseudo_begininng

  ✓ selector_interpolation_in_pseudoclass

  ✓ several_namespace_properties

  ✓ simple-inheritance

  ✓ simple-lists

  ✓ star_plus_and_parent

  ✓ strings

  ✓ url_import

  ✓ variables

  ✓ vars

  ✓ weird-selectors

  ✓ weird_added_space

  ✓ while

  ✓ while_directive

  ✓ while_in_functions
scss-tests

  ✓ 001_test_one_line_comments

  ✓ 002_test_one_line_comments

  ✓ 003_test_variables

  ✓ 004_test_variables

  ✓ 005_test_unicode_variables

  ✓ 006_test_guard_assign

  ✓ 007_test_guard_assign

  ✓ 008_test_sass_script

  ✓ 009_test_for_directive

  ✓ 010_test_for_directive

  ✓ 011_test_if_directive

  ✓ 012_test_if_directive

  ✓ 013_test_if_directive

  ✓ 014_test_comment_after_if_directive

  ✓ 015_test_comment_after_if_directive

  ✓ 017_test_each_directive

  ✓ 019_test_css_import_directive

  ✓ 020_test_css_import_directive

  ✓ 021_test_css_import_directive

  ✓ 022_test_css_import_directive

  ✓ 023_test_css_import_directive

  ✓ 024_test_media_import

  ✓ 025_test_dynamic_media_import

  ✓ 027_test_protocol_relative_import

  ✓ 028_test_import_with_interpolation

  ✓ 029_test_url_import

  ✓ 030_test_block_comment_in_script

  ✓ 031_test_line_comment_in_script

  ✓ 032_test_nested_rules

  ✓ 033_test_nested_rules

  ✓ 034_test_nested_rules

  ✓ 035_test_nested_rules_with_declarations

  ✓ 036_test_nested_rules_with_declarations

  ✓ 037_test_nested_rules_with_declarations

  ✓ 038_test_nested_rules_with_fancy_selectors

  ✓ 039_test_almost_ambiguous_nested_rules_and_declarations

  ✓ 040_test_newlines_in_selectors

  ✓ 041_test_newlines_in_selectors

  ✓ 042_test_newlines_in_selectors

  ✓ 043_test_newlines_in_selectors

  ✓ 044_test_trailing_comma_in_selector

  ✓ 045_test_parent_selectors

  ✓ 047_test_unknown_directive_bubbling

  ✓ 048_test_namespace_properties

  ✓ 049_test_several_namespace_properties

  ✓ 050_test_nested_namespace_properties

  ✓ 051_test_namespace_properties_with_value

  ✓ 052_test_namespace_properties_with_script_value

  ✓ 053_test_no_namespace_properties_without_space

  ✓ 054_test_basic_mixins

  ✓ 055_test_basic_mixins

  ✓ 056_test_basic_mixins

  ✓ 057_test_mixins_with_empty_args

  ✓ 058_test_mixins_with_empty_args

  ✓ 059_test_mixins_with_empty_args

  ✓ 060_test_mixins_with_args

  ✓ 061_test_mixins_with_args

  ✓ 062_test_basic_function

  ✓ 063_test_function_args

  ✓ 064_test_mixin_var_args

  ✓ 065_test_mixin_empty_var_args

  ✓ 066_test_mixin_var_args_act_like_list

  ✓ 067_test_mixin_splat_args

  ✓ 068_test_mixin_splat_expression

  ✓ 069_test_mixin_splat_args_with_var_args

  ✓ 070_test_mixin_splat_args_with_var_args_and_normal_args

  ✓ 071_test_mixin_splat_args_with_var_args_preserves_separator

  ✓ 072_test_mixin_var_and_splat_args_pass_through_keywords

  ✓ 078_test_mixin_list_of_pairs_splat_treated_as_list

  ✓ 083_test_function_var_args

  ✓ 084_test_function_empty_var_args

  ✓ 085_test_function_var_args_act_like_list

  ✓ 086_test_function_splat_args

  ✓ 087_test_function_splat_expression

  ✓ 088_test_function_splat_args_with_var_args

  ✓ 089_test_function_splat_args_with_var_args_and_normal_args

  ✓ 090_test_function_splat_args_with_var_args_preserves_separator

  ✓ 091_test_function_var_and_splat_args_pass_through_keywords

  ✓ 098_test_function_list_of_pairs_splat_treated_as_list

  ✓ 103_test_function_var_args_passed_to_native

  ✓ 104_test_basic_selector_interpolation

  ✓ 105_test_basic_selector_interpolation

  ✓ 106_test_basic_selector_interpolation

  ✓ 107_test_selector_only_interpolation

  ✓ 108_test_selector_interpolation_before_element_name

  ✓ 109_test_selector_interpolation_in_string

  ✓ 110_test_selector_interpolation_in_pseudoclass

  ✓ 111_test_selector_interpolation_at_class_begininng

  ✓ 112_test_selector_interpolation_at_id_begininng

  ✓ 113_test_selector_interpolation_at_pseudo_begininng

  ✓ 114_test_selector_interpolation_at_attr_beginning

  ✓ 115_test_selector_interpolation_at_attr_end

  ✓ 116_test_selector_interpolation_at_dashes

  ✓ 117_test_selector_interpolation_in_reference_combinator

  ✓ 119_test_basic_prop_name_interpolation

  ✓ 120_test_basic_prop_name_interpolation

  ✓ 121_test_prop_name_only_interpolation

  ✓ 122_test_directive_interpolation

  ✓ 123_test_media_interpolation

  ✓ 124_test_script_in_media

  ✓ 125_test_script_in_media

  ✓ 126_test_media_interpolation_with_reparse

  ✓ 129_test_supports_bubbling

  ✓ 130_test_random_directive_interpolation

  ✓ 131_test_nested_mixin_def

  ✓ 132_test_nested_mixin_shadow

  ✓ 133_test_nested_function_def

  ✓ 134_test_nested_function_shadow

  ✓ 171_test_loud_comment_in_compressed_mode

  ✓ 172_test_parsing_decimals_followed_by_comments_doesnt_take_forever

  ✓ 173_test_parsing_many_numbers_doesnt_take_forever

  ✓ 174_test_import_comments_in_imports

  ✓ 175_test_reference_combinator_with_parent_ref

  ✓ 176_test_newline_selector_rendered_multiple_times

  ✓ 177_test_prop_name_interpolation_after_hyphen

  ✓ 178_test_star_plus_and_parent

  ✓ 179_test_weird_added_space

  ✓ 180_test_interpolation_with_bracket_on_next_line

  ✓ 181_test_interpolation

  ✓ 182_test_mixin_with_keyword_args

  ✓ 183_test_passing_required_args_as_a_keyword_arg

  ✓ 184_test_passing_all_as_keyword_args_in_opposite_order

  ✓ 185_test_keyword_args_in_functions

  ✓ 186_test_newlines_removed_from_selectors_when_compressed

  ✓ 187_test_multiline_var

  ✓ 188_test_mixin_content

  ✓ 189_test_empty_content

  ✓ 190_test_options_passed_to_script

  ✓ 191_test_color_translation_functions

  ✓ 191_test_extend_in_media_in_rule
selector-functions

  ✓ append

  ✓ extend

  ✓ nest

  ✓ parse

  ✓ replace

1093 passing (12s)
7 pending

"There is not enough information to act on. Please follow the steps in our troubleshooting guide.
Make sure to capture all output into a github gist. Do not post output here."
Noted.
https://gist.github.com/bradchesney79/9c27f7e7de899468e7ea -- E530
Strangely, works just fine on the MacBook for a recent version of node, v5.3.0. (Worries that my LinuxFu is getting weak and/or eclipsed by my MacFu)
On the Mac all the tests pass the same for v5.3.0 as v0.10.41.

Gaze was not bumped because the latest dist-tag according to npm is 0.5.2
$ npm dist-tags ls gaze
latest: 0.5.2

Until this is change by the maintainer we will not bump to 0.6.

Copy, thanks for the succinct and 100% acceptable answer.


Initialize parent before children

Initialize parent node before children.
This should fix the problem mentioned here https://github.com/intercellular/cell/issues/155
Previously $init was being called from the bottom up. So if the tree structure looked like:
A
  - B
  - C
    - D

The $init() execution order was:

B.$init()
D.$init()
C.$init()
A.$init()

because it was depth first search based. (See demo: https://jsfiddle.net/bnLw8htg/1/)
With this update now the order will be

A.$init()
B.$init()
C.$init()
D.$init()

(See demo: https://jsfiddle.net/bnLw8htg/2/)

Coverage remained the same at 84.04% when pulling 8894074f70da7756c8fce59231403ed5d7dc5f91 on senior_before_junior into 9ce2d50e447c2a6a4ead7480b93007bf25ff79b2 on develop.


feat: add enableCopy to JS and react sdk's

Description

add enableCopy to JS and react sdk's
add validateOnChange to react sdk

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.34.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ReadMe Update to use storage class

Readme Update to use custom storage class for NIM's

@JamesMaki Opened a new PR without conflicts, please review and merge


First pass at binary cleanup

any input around OO within the binary side would be greatly appreciated!

Would you mind writing a brief description of the changes you made? I see a lot of whitespace changes, which makes it hard to tell from the diff which changes are consequential.

it is entirely whitespace/formatting changes and a couple revisions where code was actually broken like:
https://github.com/amzn/ion-js/pull/146/files#diff-daa873b6c5c2943abd7f22cd2fd8d45dL236


[SPARK-31886][WEBUI] Fix the wrong coloring of nodes in DAG-viz

What changes were proposed in this pull request?

This PR fixes a wrong coloring issue in the DAG-viz.
In the Job Page and Stage Page, nodes which are associated with "barrier mode" in the DAG-viz will be colored pale green.
But, with some type of jobs, nodes which are not associated with the mode will also colored.
You can reproduce with the following operation.
sc.parallelize(1 to 10).barrier.mapPartitions(identity).repartition(1).collect()

In the screen shot above, repartition in Stage 1 is not associated with barrier mode so the corresponding node should not be colored pale green.
The cause of this issue is the logic which chooses HTML elements to be colored is wrong.
The logic chooses such elements based on whether each element is associated with a style class (clusterId in the code).
But when an operation crosses over shuffle (like repartition above), a clusterId can be duplicated and non-barrier mode node is also associated with the same clusterId.
Why are the changes needed?

This is a bug.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Newly added test case with the following command.
build/sbt -Dtest.default.exclude.tags= -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver "testOnly org.apache.spark.ui.ChromeUISeleniumSuite -- -z SPARK-31886"

Test build #123372 has started for PR 28694 at commit 8f6d2a7.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27991/
Test PASSed.

Merged build finished. Test PASSed.

Test build #123374 has started for PR 28694 at commit e2aec91.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27993/
Test PASSed.

Test build #123372 has finished for PR 28694 at commit 8f6d2a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123372/
Test PASSed.

Test build #123374 has finished for PR 28694 at commit e2aec91.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123374/
Test PASSed.

cc @gengliangwang FYI

Test build #123451 has started for PR 28694 at commit 88edc95.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/28070/
Test PASSed.

Test build #123451 has finished for PR 28694 at commit 88edc95.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ExecutorResourceRequest(
class ExecutorResourceRequests() extends Serializable
class ResourceProfileBuilder()
class TaskResourceRequest(val resourceName: String, val amount: Double)
class TaskResourceRequests() extends Serializable
case class CheckOverflowInSum(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123451/
Test PASSed.

Thanks, merging to master/3.0


Add Visily to Design Applications

Visily is a very easy-to-use mockup design software that enables anyone, regardless of their design skills, to create beautiful app mockups effortlessly.
Website: https://www.visily.ai/

Thank you @buunguyen


Document the overall application structure

Feature
Why is this feature being added?
When working on the application the structure and flow is super important to know. We want to be able to easily read the code and using documentation understand what the major areas are.
What should your feature do?
For this first step, I want to document the various major parts that need to be documented.
EX:

routes.rb
models
db schema
controllers
configs
Anything else

Acceptance criteria:
Include a simple tree diagram of the major parts of the application and include it in the /docs folder.

Assigning myself as placholder, thanks @donquxiote.

Wanted to check in and make sure I'm on the right track for what y'all are looking for. This is a basic diagram of the models I generated with rails-erd. There's a few options to play around with so it can be a lot cleaner. If y'all want I can include that gem in my pr so y'all can generate these easily in the future too.
file_name.pdf
Next I'll work on diagrams for the other parts listed in the issue.

This is really awesome and going to be helpful.
Would you mind going over how you created this to see if we can create a rake task to auto generate (and keep this up to date)?
I think keeping track of the data model is very helpful.
I would also like to incorporate more ruby/ rails specific knowledge into documentation so that someone new to the rails framework would understand things such as:

why we have tests here
how the test folder mirrors real folder.
How models connects to controllers
How the controller folder structure relates to the api url
If someone wants to make a change to a scheduled job what they should do.

I'm not asking you to do all this, but as this repo is intended to be a strong learning experience for vets I have two goals.

Make the structure of application newbie friendly
Document in ways that are not fragile to application changes.

Gonna mark this as closed for now as we got a schema. And trying to prioritize things.


Update README.md

i have updated the readme file according to the template .
Pull Request for DL-Simplified 💡
Issue Title : README enhancement .
fixes issue #474

Info about the related issue (Aim of the project) : Update README file according to the template in an eye-pleasing format
Name: Nandni Aggarwal
GitHub ID: https://github.com/nandni-a
Email ID<EMAIL_ADDRESS>Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant)  Contributor GSSoC'24

Closes: #issue number that will be closed through this PR
Describe the add-ons or changes you've made 📃
I have made some changes with the readme file of blood disease detection model in the form of the template given . I hope that it is what you were expecting .
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist: ☑

[ ] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

I have updated the readme file of blood disease detection model according to template given .  fixes issue #474 .


HA not preserving source IP for failed attempts

For external (tunnel) login attempts
even after setting externalTrafficPolicy in service
https://github.com/lltr/home-cluster/commit/a57e91888bbe7a663ff3040a14778e0f1133707b

Found out that service external ips does not support externalTrafficPolicy
https://github.com/kubernetes/kubernetes/issues/91374


Ability to ignore specific exceptions

Hey, I've found very distracting to receive exceptions about not important events like chef-client restart or git-repo connection failure.
Here's my attempt to skip these kind of things.

Thanks for contribution.
I changed message attribute to be regexp instead of string, which is more flexible.

Thanks!


CLI should have option to not exit on record import failure.

Error and failed record should be printed to console, but execution should continue.

CLI module to be removed


oracle get data change operation type always be READ

Describe the bug(Please use English)
A clear and concise description of what the bug is.
oracle cdc connector get wrong data change operation type in my case , always be READ ,whatever i create ,update or delete row data in table
Environment :

Flink version :  1.13.5
Flink CDC version:  2.2.1
Database and version: oracle 19c

To Reproduce
Steps to reproduce the behavior:

The test data : whatever data

The test code :

The error :
i always get the opration be READ whatever i do what to the data
Additional Description
If applicable, add screenshots to help explain your problem.

i use the same version mysql connector ,the data change operation type is working ok , so i do the same way on oracle,first problem is that i get operation type always be Read ,second is that the data structure is not same with mysql ,i hope cdc project could make ths data structure same to the same type Database ,such as mysql/orcale/sqlserver


How can I change the floating action menu icon?

I have tried to add the fab:fab_icon just like on floating buttons, but it does not seem to work. Is there any way to change the background image on the floating menu also, except the buttons?
<com.getbase.floatingactionbutton.FloatingActionsMenu
        android:id="@+id/left_labels"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_alignParentRight="true"
        android:layout_below="@+id/mapstyle"
        fab:fab_addButtonColorNormal="@color/white"
        fab:fab_addButtonColorPressed="@color/white_pressed"
        fab:fab_addButtonPlusIconColor="@color/half_black"
        fab:fab_expandDirection="down"
        fab:fab_icon="@drawable/map_marker"
        fab:fab_labelStyle="@style/menu_labels_style"
        fab:fab_labelsPosition="left">

        <com.getbase.floatingactionbutton.FloatingActionButton
            android:id="@+id/alle"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            fab:fab_colorNormal="@color/white_transparent"
            fab:fab_colorPressed="@color/white_pressed"
            fab:fab_icon="@drawable/map_marker"
            fab:fab_size="mini"
            fab:fab_title="Alle" />

</com.getbase.floatingactionbutton.FloatingActionsMenu>

Thank you in advance for your time and effort.

For the icon you just need to set android:src="" filled with a drawable

I did also tried that, but it did not work. :( Thanks for your time and effort though... :D

+1 to @thanos1983 ...... did u find the answer?

Hello @rohitkeshwani07,
I do not have a solid solution to my problem but I have created a work around. Because the answer is big to rewrite it I will provide a link in case that someone in the future might have the same problem How to set icon to getbase FloatingActionsMenu. I have also found a solution in order to update the menu icon from the "sub buttons" when they are clicked [Change image Floating Action Button Android]. (https://stackoverflow.com/questions/30455765/change-image-floating-action-button-android/37035075#37035075)
I hope this helps somebody else that had the same problem. If you have any queries or my answer is not complete get back to me and I will try to help you.

Please use:
...
android:src="@android:drawable/ic_menu_share"
...
Don't use "fab:icon...", but instead use "android:src..."
It works for me👍
X5ibnouf

Hello @ibnouf88 ,
I just tried it, and for me is not working. I do not know if it it not working because I have modified the library or it does not work generally. But the solution that I have posted it works just fine for me. :D
Maybe someone else can tested and verify that it works.

i can confirm that "android:src" has no effect.

Trying this library, you can use custom icon for menu button by using:
fab:fab_menuIcon="@drawable/myIcon"
https://github.com/toanvc/FloatingActionMenu-Animation

if you are using the source not gradle lib then use his changes to the sources.

fab:fab_icon="@drawable/your_icon"

I am also not getting menu icon using android:src="@drwable/*" and using com.getbase:floatingactionbutton:1.10.1 included in gradle as of @Ostkontentitan

For the menu icons I ended up doing it in Java:
FloatingActionButton btn = view.findViewById(R.id.buttonID);
btn.setIcon(R.drawable.myimage);

I also downloaded the library to use in my project locally, not sure if that makes a difference.

using this library
com.github.clans.fab.FloatingActionMenu
app:menu_icon="@drawable/ic_share"
above solution worked for me.


Carbide import statement

It would be pretty handy to have an import statement in Carbide. This would mark the first level 2 feature as it relies on Graphene functionality, but not necessarily Carbon functionality.
In Carbide:
@import Carbon.Collections.Dictionary
@import Carbon.Exception as exec
@import (Dictionary, List) from Carbon.Collections
@import * from Carbon.Collections
@import (Dictionary as dict, List as list) from Carbon.Collections

Compiles to Lua:
local Dictionary = Carbon.Collections.Dictionary
local exec = Carbon.Exception
Carbon.Collections:Import("Dictionary", "List")
Carbon.Collections:ImportAll()
Carbon.Collections:ImportAs({Dictionary = "dict", List = "list"})

The provided example should compile instead to
local Dictionary = Carbon.Collections.Dictionary
local exec = Carbon.Exception
local Dictionary, List = Carbon.Collections.Dictionary, Carbon.Collections.List
Carbon.Collections:ImportAll()
local dict, list = Carbon.Collections.Dictionary, Carbon.Collections.List

Imported into https://github.com/lua-carbon/callisto/issues/1


Alfajores:

Describe your issue here.
Environment

Elixir Version: 1.9.0

Erlang Version: 22

BlockScout Version: 6a6e46763375b7dd547fa56f143fb694a3a3f473

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.210 Safari/537.36

Steps to reproduce
Tell us how to reproduce this issue. If possible, push up a branch to your fork with a regression test we can run to reproduce locally.
Expected Behaviour
Tell us what should happen.
Actual Behaviour
Tell us what happens instead.

Duplicate of #


Toptimes don't disappear sometimes (very often)

subj.
How to reproduce? Press F5 and wait. If it isn't disappeared - try again. This happens very often, for me at least.
I tried to look into code but I don't got how to fix it yet.
\resources[race]\race_toptimes\top_c.lua

fixed in 0144449e26b836fe12999a608aaf117b7f91e425


[PE-D] Progress bar in each entry

Similar to the pie chart, I feel like the progress bar feels underutilised. Right now, a person in the app can be either Complete or Incomplete, and if that are complete the progress bar is filled up and if they are not the progress bar is empty. In that case, if the completion of a person is already indicated as a tag, it seems redundant to have a progress bar as well that takes up more space in the UI just for essentially the same purpose.

Labels: severity.Low type.FeatureFlaw
original: TohWeiJie01/ped#12

Not a feature flaw, documentation was not clear that ONGOING is a possible status.

Possibly can have more increments

Resolved by #152


Update time-stamping-authenticode-signatures.md

Would appear PKCS #9 was a typo.

@jwbrothers : Thanks for your contribution! The author(s) have been notified to review your proposed change.