primordic/IssueDupesLite huggingface dataset:
Repository: sds/scss-lint

Issue #821: ColorKeyword erroneously finds map-get arguments
Created: 2016-08-04T01:27:06Z
If I have a map like
$my-colors: (
  red: #de2424,
  green: #28d424,
  blue: #2820e0
);
and I use it like
.some-thing {
  border-color: map-get($my-colors, green);
}
then the ColorKeyword checker alerts me that green should be written in hexadecimal form. But it isn't a color keyword here; it's a table key.
Unfortunately, I'm not sure there's a way to distinguish between that and darken(green, 10%), which should be caught by ColorKeyword.

Duplicate issue #911: VariableforProperty shouldn't trigger when using a function or mixin
Created: 2017-08-10T14:08:35Z
It's quite common to use a palette function for colors.
// pallette
// @see https://twitter.com/thecodezombie/status/595977653296996354/photo/1
@function palette($palette, $tone: 'base') {
  @return map-get(map-get($palettes, $palette), $tone);
}

$palettes: (
	grey: (
		border: #E8E8E8,
		text: #565656
	)
);

div {
    border: 1px solid palette(grey, border);
    color: palette(grey, text);
}

These both currently trigger a linter error if you've got either ColorVariable or VariableforProperty enabled.

Closing comment (2017-08-14T04:41:15Z): My mistake. This is actually a duplicate of #821.
Repository: sds/scss-lint

Issue #496: Add require: false to README?
Created: 2015-06-18T13:02:05Z
I ran into the issue described here: mkhairi/materialize-sass#34 and had to add require: false when I switched from scss-lint to the scss_lint gem in order to precompile assets.  Is it worth a mention in the README?

Duplicate issue #503: Illegal Nesting SCSS Error when using scss_lint v0.39.0
Created: 2015-06-26T20:39:00Z
Today I attempted to bump from scss-lint v0.38.0 (with the dash) to scss_lint v0.39.0 (without the dash) to get a patch fix I had requested into my application.
It caused massive failures when running our rspec test suite.
I found some articles around the internet that might help:

mkhairi/materialize-sass#34
rails/sass-rails#307

All of the failures were very similar to this one:
     Failure/Error: Unable to find matching line from backtrace
     ActionView::Template::Error:
       Illegal nesting: Only properties may be nested beneath properties.
     # (sass):10
     ...

Reverting back down to scss-lint v0.38.0 (again, with the dash) resolved the issue for me.

Closing comment (2015-06-26T20:55:18Z): Unfortunately there isn't a simple way for scss-lint to work around this, so you need to augment your Gemfile yourself. See d495bc6 for details.
Related to #496.
Repository: sds/scss-lint

Issue #355: Disable not working in nested includes DeclarationOrder
Created: 2015-01-30T17:11:52Z
An include in an include throws an error even when the linters are disabled:
// file.scss

// scss-lint:disable

@include mixin(blah) {
    .el { @include mixin; }

    @include mixin;
}
file.scss:4 [W] DeclarationOrder: Rule sets should be ordered as follows: @extends, @includes without @content, properties, @includes with @content, nested rule sets

Duplicate issue #369: Disable linters for a @mixin
Created: 2015-02-18T17:20:45Z
Disabling a linter for an ordinary selector works perfect (any example you've given in the Readme). But when it comes to disabling a linter for a mixin, it doesn't seem to work for me. I have this mixin:
@mixin font-size($size, $line: $size * 1.5) {
  font-size: ($size * 10) + px;
  line-height: ($line * 10) + px;
  font-size: $size + rem;
  line-height: $line + rem;
}
In this case I need the fallback px values for IE support and can't remove them. So I'm trying to add the // scss-lint:disable DuplicateProperty comment to avoid the duplicated property warning. Tried both within the mixin on the first line and outside right before it. Both didn't work.
Is there a different way to do this (without excluding the whole file where the mixin is) or not working for a reason?

Closing comment (2015-02-23T03:08:09Z): Duplicate of #355.
Repository: sds/scss-lint

Issue #384: Add option to NestingDepth to ignore parent reference suffixes
Created: 2015-03-06T09:33:20Z
As you may know, since SASS 3.3.0
("The parent selector, &, can be used with an identifier suffix..." http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#smaller_improvements_2)
we can use the ampersand character (&) to build compound selectors.
This is quite usefull if you use BEM principles for writing your classnames selectors.
Take a look at this SASS/SCSS example:
.block {
&--state {
color: blue;
}
}
That will compile to the following CSS:
.block--state {
color: blue;
}
When I run CSS Lint on my SCSS source code, it considers that I'm using nesting while in reality I'm not.
It could look like nesting but in fact, I'm just concatenating several string into a single classname.
Do you consider this as an issue ?

Duplicate issue #477: Option to exclude pseudo-classes from nesting count
Created: 2015-06-02T16:48:41Z
Pseudo-classes appear to be included in the nesting count. I'm sure some users may need this, but I'd like the ability to disable them. In my view, the nesting depth is intended to limit individual elements specified in the selector chain (each one increases specificity). Pseudo-classes and pseudo-elements are typically never used without a qualifying element, so I don't believe they should count as a fully separate level.
.panel {
    > header {
        .btn-clear {
            &:hover { }
        }
    }
}

Closing comment (2015-06-08T02:32:09Z): I'm realizing that this is a duplicate of #384, so closing in favor of that issue.
Repository: sds/scss-lint

Issue #38: Add compatibility for .sass files
Created: 2013-09-04T21:43:16Z
Is sass compatibility planned?  If not, are you guys open to pull requests?  Thanks.

Duplicate issue #530: Sublime Text 3
Created: 2015-07-18T03:33:44Z
nvm =[

Closing comment (2015-07-18T16:50:22Z): Duplicate of #38
Repository: sds/scss-lint

Issue #516: Use the first .scss-lint.yml configuration file found in the current working directory or one of its ancestors
Created: 2015-07-08T14:52:29Z
I understand how the configuration files work at the moment (.scss-lint-files by --config flag >> CWD >> ~), and no merging. I just ran into an 'issue' in a very large project with different teams regarding the configuration of the linter - because everybody wanted to do sth. just a little bit different :/ (tabs vs. spaces etc.)
The solution then was, that every team got their own config-file, with their own customizations. This resulted in a lot of duplicated code in the .scss-lint.yaml-files (and lots of those files as well). Adding or changing rules in the future would thus be quite tedious, because it has to be done in lots of files...
I know that this is more a political issue and should be solved by just sticking to one default standard for all teams, but could you consider sth. like eslint's configuration cascade? http://eslint.org/docs/user-guide/configuring#configuration-cascading-and-hierarchy
The idea here: every file is being checked by using 'the closest' .scss-lint.yaml file - if none in the current dir, move to the parent and so on - and as a last resort ~/.scss-lint.yaml. This way I could configure a 'sane default', and then let the teams just add their custom rules on top.
Would this be possible at all, or do you even think that this would be a bad idea?

Duplicate issue #947: Ignore node_modules in all projects
Created: 2018-03-31T20:51:29Z
Is it possible to ignore folders, like node_modules, from the home dir config file?
I tried the following but it didn't work. In the ~/.scss-lint.yml file, I put the following:
exclude:
  - '*.css'
  - 'node_modules/**'

This didn't work. It only worked if I put it in a project's .scss-lint.yml file. Is this intentional? I know the docs say the paths are relative to the config file. So this means that it's not possible to exclude node_modules for all projects, since it's definitely something that I don't mind being a global exclude?

Closing comment (2018-04-01T02:51:36Z): Duplicate of #516. Feel free to contribute to the discussion there, but at its core we are happy to add this if someone submits a pull request!
Repository: sds/scss-lint

Issue #655: Feature request: More informative output
Created: 2015-12-17T18:15:43Z
Currently the output of running $ scss-lint is just the error lines. No error count. No message if there are no errors. It would be nice to have:

An error count if there are errors
A success message of there are no errors
An error raise if there are errors, to trigger a failed build on CI tools like CircleCI or TravisCI

Duplicate issue #784: Print to stdout total number of errors
Created: 2016-04-26T19:26:29Z
It would be nice to have a total number of errors/warnings after each run:

Closing comment (2016-04-26T19:48:08Z): Dup of #655 which has many comments
Repository: seanmonstar/warp

Issue #532: How to combine multiple request methods with dir filter
Created: 2020-04-13T00:11:38Z
I'm using the latest v0.2 and I would like to combine multiple request methods with the dir filter. For example GET's and  HEAD's. Something like code below:
#![deny(warnings)]

use warp::Filter;

#[tokio::main]
async fn main() {
    pretty_env_logger::init();

    let public_head = warp::head().and(warp::fs::dir("public/"));
    let public_get = warp::get().and(warp::fs::dir("public/"));
    let routes = public_head.or(public_get);

    warp::serve(routes)
        .run(([127, 0, 0, 1], 8787))
        .await;
}
but it doesn't work. I think because of the get check instead of any (like file for example).
Is there any way to make this possible?
Note: I have tested with any filter using a fork locally. It works for both methods (GETs & HEADs), but when I try to request a dummy file, I get a response with status 405 instead of a 404.

Duplicate issue #834: HEAD request support for fs::dir() filter
Created: 2021-04-19T13:00:33Z
Hi,
filters::fs::dir() only reply to GET requests, it should also reply to HEAD requests.

Closing comment (2021-04-26T12:57:58Z): I think this is related to or possibly dup of #532.
Repository: seanmonstar/warp

Issue #3: Returning unit from map or and_then is weird
Created: 2018-08-01T21:57:28Z
While warp usually handles unit () from built-in Filters quite well, if a user tries to map (or and_then) a Filter and return nothing, the unit is no longer dropped.
Example
warp::any()
    // unit was dropped, no arg needed
    .map(|| {
        println!("no returning anything");
    })
    // return of `map` was auto-wrapped in `(T,)`, becoming `((),)`
    .map(|((),))| {
        println!("gross");
    })

Duplicate issue #121: [Beginner question]: How to execute a filter conditionally?
Created: 2018-10-22T10:15:06Z
Sorry for the noob question but I'm trying to find some information in the docs without much success.
What I'm willing to get is some sort of filter that is executed conditionally depending on an external variable.
I have this piece of code, but I would like to only execute spa filter in case the bool is_spa is true.
let files = warp::fs::dir(final_path);
let spa = warp::fs::file(spa_index_path);

let routes = files.or(spa);

let address = ([0, 0, 0, 0], final_port);
warp::serve(routes.map(|x| {
      println!("{:?}", x);
      x
}))
.run(address);
I've tried many combinations of filters without luck so any help would be really appreciated 😉

Closing comment (2018-10-23T17:02:12Z): I think part of the inconvenience is related to #3. You can't really do any validation in an and_then and return "nothing", which is annoying.
let is_spa = warp::any(move || is_spa)
    .and_then(|is_spa| {
        if is_spa {
            Ok(IsSpa)
        } else {
            Err(warp::reject::not_found())
        }
    });

let route = is_spa
    .and(warp::fs::file(spa_index_path))
    // map away the worthless value we had to return from and_then
    .map(|IsSpa, file| {
        file
    })
Repository: seanmonstar/warp

Issue #58: Relation to tower-web
Created: 2018-08-14T21:53:56Z
I just read your blog post that introduces the warp library, so I'm quite intrigued now as to how things will develop now with tower and tower-web quickly entering the stage. I am certainly attracted by the design philosophy of warp, but I do want to know how you see it in relation to tower-web, which you mentioned in passing. From an issue you have open here, it would seem the Filter and Service traits are somehow analogous? I'm presuming neither tower-web nor warp will ever include the other as a dependency, but what will the relation between them be, going forwards? Direct competitors?
Side question: does warp support async workflows like Gotham or such?

Duplicate issue #46: Add compression Filters
Created: 2018-08-09T22:53:40Z
These would likely need to be with filters.
Some hypothetical example:
let route = warp::fs::dir("static")
    .with(warp::compress::gzip());

Closing comment (2020-01-24T15:28:29Z): related to #58
cc @LucioFranco
Repository: seanmonstar/warp

Issue #514: https can not get it's remote address.
Created: 2020-04-01T08:49:49Z
warp version
warp={ version = "0.2.2", features = ["tls"] }

 let routes = warp::any().and(warp::addr::remote()).map(|addr: Option<SocketAddr>|  format!("Hello, World! {:?}",addr) );

    warp::serve(routes)
        //.tls()
        //.cert_path("tls/cert.pem")
        //.key_path("tls/key.rsa")
        .run(([0, 0, 0, 0], 3030))
        .await;
using http it's work ok.
  let routes = warp::any().and(warp::addr::remote()).map(|addr: Option<SocketAddr>|  format!("Hello, World! {:?}",addr) );

    warp::serve(routes)
        .tls()
        .cert_path("tls/cert.pem")
        .key_path("tls/key.rsa")
        .run(([0, 0, 0, 0], 3030))
        .await;
using https can not get it's remote address.

Duplicate issue #559: `addr::remote()` is `None` for TLS connections
Created: 2020-05-02T09:41:13Z
When I start a server using warp::serve(routes).tls() the filter warp::addr::remote() returns None. If I disable TLS, I do get the remote address.
How can I get the IP address of a client when using tls?

Closing comment (2020-06-16T22:18:07Z): Actually: it's a duplicate of #514. Should be fixed in v0.2.3.
Repository: seanmonstar/warp

Issue #175: Question: pipe a request body into a file?
Created: 2019-03-01T18:33:06Z
I am coming from the Node.js world but I'm looking for something with low latency, type-safety etc.
For my use-case I want to pipe a request body into a file (upload). Is this possible in Warp, without having the full contents in memory?

Duplicate issue #354: add proxy-server example
Created: 2019-12-29T04:12:17Z
Our use-case is ci/cd deployment with a non-privileged on ubuntu where the lower port ranges are restricted and can be handled with a proxy server.  There may be others.
I've peeked at the hyper example: https://github.com/hyperium/hyper/blob/master/examples/http_proxy.rs and would be happy to contribute with some suggestions/guidance.
Related issue: #230

Closing comment (2020-01-11T23:51:11Z): Looking at this it looks like this is about a Request/Response combination that results in a usable Socket afterwards?  I must say the documentation isn't exactly verbose.
I'm looking to do Cut-through switching.  That is I want to validate and alter Request Headers and then hand off the Body to another HTTPD without storing the body(could be several GB of file upload).  I likewise want to do the same with the Response, for file downloads.
The whole story.  I recently wanted to share a saved game file but I was unable to locate a file sharing service that I was happy with.  I've obtained a VPS from Google, but it has limited storage.  I plan to use FreeNet as my file storage backend.  What I'm looking to do is pass through filtered access to an instance of FreeNet.
Can Warp do anything like this?
Edit: Similar to #175
Repository: seanmonstar/warp

Issue #454: real ip/X-Forwarded-For support for remote_addr
Created: 2020-02-20T21:46:47Z
Right now I'm using the following for logging. It would be nice if it would handle "real ip" transparently.
let log = warp::log::custom(|info| {
        info!(
            "{:?} {} {} {} {:?}",
            info.remote_addr(),
            info.method(),
            info.path(),
            info.status(),
            info.elapsed(),
        );
    });

Duplicate issue #553: Support X-Forwarded-For in the logs
Created: 2020-04-28T14:41:41Z
The access logs that are automatically generated by warp::filters::log::log() and ::custom() functions have some kind of access to the remote end of the stream, but this doesn't work that well with a reverse proxy in front of it.
Would it be possible to support the X-Forwarded-For header as a source of the client IP address? I think it's currently impossible to do this as a library user since (correct me if I'm wrong) it's not possible to build wrapping filters.

Closing comment (2020-05-05T15:22:47Z): Similar to #454
Repository: seanmonstar/warp

Issue #16: Custom `with` filters
Created: 2018-08-02T19:50:18Z
Under the current api, Filter::with requires that the type be W: Wrap however the Wrap trait is sealed making it difficult to write custom wrapping filters. For instance, I'm trying to write a filter that will forward a header from a request to the response. So far I've come up with the filter to generate the either grab the request id or generate a new one:
let req_id = warp::header::<String>("x-request-id").or_else(|_| Ok(("generated".to_owned(),)))
But I can't figure out using the combinators provided how to store the request-id in the filter and use it on the response.
It also seems that you cannot call map after returning a warp::reply in the combinator chain so I can't even make the above work with boiler plate something like
let my_route = req_id.map(warp::reply).map(|id: String, reply: warp::Reply| {
    reply.set_header("x-request-id", id)
})

Duplicate issue #574: Custom Wrapper for `with`?
Created: 2020-05-11T12:53:14Z
I've been using Warp to great effect so far. But I'm confused about the with method.
Is it possible to pass something else than a warp::log? I want to echo back an ID the client send my service. Now (only 2 endpoints) I just carry that ID around until I assemble the reply but that feels awkward.
I'm new to Rust so I might be missing something incredibly evident.

Closing comment (2020-05-14T07:13:31Z): Closing. Duplicate of #16
Repository: seanmonstar/warp

Issue #808: Route based on path suffix
Created: 2021-02-26T19:56:40Z
Is your feature request related to a problem? Please describe.
Currently, all routing abstractions are limited by:

Prefix patterns
Fixed arity of path segments
Well known path segments

let route = warp::path("x"); // Prefix style + Well known segments
let route = warp::path!("some" / String); // Prefix style + Fixed arity + Well known segments

So, there is no easy way to match a path based on its suffix if the segments structure is not well known.
Describe the solution you'd like
A method to capture a request based on a path suffix for any arbitrary path structure, such that all of a.ext, a/b.ext and b/c.ext reach the same route.

Duplicate issue #940: path! to support concatenation of string
Created: 2022-02-13T10:32:23Z
I'd like to be able to use static strings inside the path! macro like e.g.:
path!("my" / "path" / MyParam ".pdf")
As for the concatenation it could be with a symbol or not:

w/ symbol: path!("my" / "path" / MyParam + ".pdf")
w/out: path!("my" / "path" / MyParam ".pdf")

Is your feature request related to a problem? Please describe.
This is especially useful when you want to have multiple routes that lead to the same route with a given file extension or you just want to match a static string in the route between other path parts. Or you want to have a prefix or suffix.
let html_route = path!("my" / "path" / MyParam ".html").or(path!("my" / "path" / MyParam))
Describe alternatives you've considered
using a NewType struct with Display/FromStr impl to handle the extension:
#[derive(Debug, Display, FromStr, Deserialize, Serialize, Clone)]
#[display("{file_name}.pdf")]
#[serde(try_from = "&str", into = "String")]
pub struct Pdf<T: std::fmt::Display + std::str::FromStr + Clone> {
    pub file_name: T,
}

Closing comment (2022-02-13T11:08:23Z): Duplicate of #808
Repository: seanmonstar/warp

Issue #601: Can I Use Warp With Other Executors?
Created: 2020-06-09T22:11:54Z
Is there a way to use Warp with an executor such as smol and avoid including Tokio? There is an example of how to hook up hyper to use smol; is there any way that I could do something like that to run Warp on top of smol?

Duplicate issue #603: Is warp usable with async-std?
Created: 2020-06-10T19:46:24Z
Is warp usable with async-std?

Closing comment (2020-06-10T19:50:31Z): Duplicate of #601
Repository: selectize/selectize.js

Issue #110: Disable text input on a vanilla select
Created: 2013-09-11T07:19:02Z
Is there any configuration option to explicitly disable text input on the control?
I mean, not to disable the dropdown, but just disable keyboard input (and the caret blinking), something like the readonly attr for the generated text input maybe?

Duplicate issue #382: Hide search input on specific select
Created: 2014-04-17T05:20:07Z
Hello.
Is there a way of hide the search input on specific select?
Some selects in my website are just too short to have a search input, so I want it hidden – like this one in Chosen plugin.
Thank you.

Closing comment (2016-08-26T18:03:37Z): Dupe #110
Repository: selectize/selectize.js

Issue #214: On Android, backspace doesn't delete tag
Created: 2013-12-09T13:41:15Z
Android: 4.3.1, browser: Chrome 31.
Touching backspace does nothing.

Duplicate issue #539: Cannot remove items on Android
Created: 2014-08-15T11:40:11Z
Hey, I tested it on Android and everything works and looks fine, except that I cannot remove any item by pressing backspace. It most probably calls different javascript event on Android than on PC. Can you please fix this?

Closing comment (2014-08-15T12:59:12Z): Duplicate of #214
Repository: selectize/selectize.js

Issue #219: Cannot call method 'mixin' of undefined 
Created: 2013-12-11T17:32:46Z
Hello,
Got this error on the line: MicroPlugin.mixin(Selectize);
Using jQuery 2.0.3. Using selectize 0.8.5.
Calling with:
$('select').selectize();
Regards

Duplicate issue #327: Cannot call method 'mixin' of undefined
Created: 2014-03-13T00:13:20Z
Why am i getting this when trying to run selectize for the first time?

Closing comment (2014-03-13T04:06:36Z): Duplicate of #219.
Repository: selectize/selectize.js

Issue #809: Autogrow buggy with some characters like '@', '.'
Created: 2015-06-03T13:00:52Z
In order to create a new entry (like email), I need periods to be printed (obviously). Everything is fine in chrome but not in firefox unless I add:
|| keyCode === 190

here: https://github.com/brianreavis/selectize.js/blob/master/dist/js/standalone/selectize.js#L1018
I can't reproduce it in a plnkr so I guess a script of mine could interfere but still, it feels wrong: how come the printable is that limited.
I guess its not a bug but does it ring a bell please?

Duplicate issue #979: Typing @ gives jerk in text.
Created: 2016-01-07T15:16:42Z
When we press "@" or "?" key in text field for new entry or searching an entry the text typed in input box gives jerk for one time at left side.
The text moves little onto left and comes back to normal position this happens every time when we press "@" or "?" key.

Closing comment (2016-01-07T16:25:07Z): Duplicate of #809. Thank you
Repository: selectize/selectize.js

Issue #598: Selectize removes options field tags in the dom.
Created: 2014-10-15T16:59:55Z
Calling selectize on a select field removes the 'option' tags from the hidden 'select' tag in the dom.
This becomes an issue for us since our existing test suite interacts with the actual select fields and now break after applying selectize on them.
Is is possible for selectize to work without modifying the existing dom elements? Select2 for example does this.

Duplicate issue #39: Unable to query original select
Created: 2013-06-20T15:20:13Z
When you select an option with selectize it changes the original select component adding an option with the selected value
for (i = 0, n = this.items.length; i < n; i++) {
                options.push('<option value="' + htmlEntities(this.items[i]) + '" selected="selected"></option>');
            }
I think the option component should reflect exactly how the original option was (including the label) so the user can query the select component and get the label and wherever data he wants from it.

Closing comment (2014-11-01T16:33:13Z): +1 for this issue.
dup: #598
@brianreavis We're currently using select2 and attempting to move selectize breaks our integration test since they interact with elements in the dom.
Repository: selectize/selectize.js

Issue #256: Allow text selection when input type="text"
Created: 2014-01-20T08:09:52Z
Currently it is impossible to use arrow keys + left/right, or even CTRL+A to select the item text.
For this request - my interest is in single item selection on a input type="text". So selectize becomes a better 'typeahead' with the nice to have 'add ' prompt. I wonder if this use case can be supported and then the selected item can be inside the hidden input type="text" and thus selectable.

Duplicate issue #486: Can't use Ctrl/Cmd+A to select all text when option is selected
Created: 2014-06-20T09:18:49Z
Using a simple (single item) select, it seems it's not possible to select all the text in the input by pressing Ctrl+A/Cmd+A. It only seems to work when being in "search mode".
Steps to reproduce:

Open select
Type something random
Press Ctrl+A/Cmd+A - observe that all the text is selected
Now, clear the input and select an option from the dropdown
Open the select again, press Ctrl+A/Cmd+A
Observe that it doesn't select the text in the input

I would expect being able to select the text in input regardless of whether it contains an actual selected option or a search string.

Closing comment (2016-07-23T21:50:36Z): Looks similar to #256. Thanks
Repository: selectize/selectize.js

Issue #75: "select": close at double click
Created: 2013-08-14T17:17:09Z
If I click once, the list opens. But if I click again, it will be closed for 0.01 seconds, and again opened.
You can do that when you click again the list closed?
Example: http://brianreavis.github.io/selectize.js/
Any "select", for example "Gist-style Language Selector" - Signle
p.s. sorry for my english

Duplicate issue #126: Issue when closing the dropdown
Created: 2013-09-23T13:57:11Z
If you open the dropdown and then you press the input to close it, you can't. It close and open very quickly.
You can see the effect in the following fiddle:
http://jsfiddle.net/cHxcZ/10/

Closing comment (2013-09-24T03:06:25Z): Duplicate of #75. A fix for this is about 90% done along with some improvements on focus handling.
Repository: selectize/selectize.js

Issue #15: Preload remote data
Created: 2013-06-05T14:44:56Z
Currently Selectize doesn't preload any data, so when you're using a remote source and call addItem before you've manually typed anything, nothing will happen as the data hasn't loaded yet.
Obviously it'd be better to give this its own option, so you can decide if you want to preload anything or nothing.

Duplicate issue #27: Text and value both same in selectize.jquery.js
Created: 2013-06-06T12:40:42Z
Can somebody explain why the jQuery plugin initializes selectize a text and value attribute with the same values? See here.
This is causing issues for us as our tags use one value for the tag label and another for the actual value which we send back to our server.
Surely something else should be occurring here?

Closing comment (2013-06-10T10:00:39Z): In a way, this is related to #15 as we need to preload data that's entered into the input, but which contains data that normally comes from load in an XHR request.
$this.selectize({
    create: false,
    delimiter: ',',
    valueField: 'agent_id',
    labelField: 'agent_name',
    searchField: ['agent_name'],
    sortField: 'agent_name',
    persist: false,
    render: {
        item: function(item) {
            return '<div data-value="' + item.value + '" data-text="'+item.text+'">' + (item.text ? '<span class="name">' + item.text + '</span>' : '<span class="name">' + item.agent_name + '</span>') + '</div>';
        },
        option: function(item) {
            console.log(item);
            return '<div>' +
            '<img src="'+item.picture+'" alt="">' +    
                '<span class="agent_name">' +
                    '<span class="name">' + item.agent_name + '</span>' +
                '</span>' +
            '</div>';
        }
    },              
    load: function(query, callback) {
        if (!query.length) return callback();

        $.ajax({
            url: '/api/users',
            type: 'GET',
            dataType: 'json',
            data: {
                q: query
            },
            error: function() {
                callback();
            },
            success: function(res) {
                callback(res);
            }
        });
    }
});
Repository: selectize/selectize.js

Issue #78: Enter key should submit form
Created: 2013-08-20T20:50:36Z
I'm not sure if I am missing an option, but it would be nice to be able to allow the enter key to submit the form, even when selectize has focus.

Duplicate issue #111: Submit form on ENTER key
Created: 2013-09-12T22:06:31Z
When a selectized control has focus and the dropdown is closed I would expect pressing the ENTER key to submit the form, but this doesn't happen. It would be useful to reflect normal select behavior and permit fast form compilation.

Closing comment (2013-09-12T22:19:57Z): Duplicate of #78.
Repository: selectize/selectize.js

Issue #104: "select": scroll to selected value
Created: 2013-09-05T14:27:18Z
For example if there select with years, from 1940 to 2013 and default value set to 1999, when I open the "select" it open the list from start - from 1940 instead of 1999.
And also if I choose any value, on click the list again start from the start instead of the value that I chose.
You can add scroll to "selected" value ("selected option")?
p.s. Sorry for my english

Duplicate issue #131: Does not set previous selected item on focus
Created: 2013-09-25T05:51:13Z
When the control gains focus, it always select the first item in the list, despite of which option was selected at first.
Even when you select another option, if you go back to correct a mistake, you'll need to start searching all over again.
This could be a disadvantage when you are dealing with long lists.

Closing comment (2013-09-25T18:51:41Z): I see that this is a duplicate of
#104
Repository: sentinl/sentinl

Issue #473: Unable to specify message when creating new actions
Created: 2018-06-22T11:52:22Z
Sentinl and Kibana version
Kibana: 6.2.4
Sentinl: 6.2.4 (master)


Issue description
Unable to specify message when creating new actions in sentinl.


First image: https://github.com/sirensolutions/sentinl/releases/download/tag-6.2.3-3/sentinl-v6.2.4.zip

Second image: https://github.com/sirensolutions/sentinl master branch



Reproducing the issue step-by-step
(master)
In the process of creating a watcher I am unable to specify what message I would like to send.


Expected results vs. actual results
Expected is the first image.
Actual is the last image.


Sample of data


Additional details

Duplicate issue #482: Unable to add body/message in actions
Created: 2018-06-26T13:50:04Z
Sentinl and Kibana version
6.2.3


Issue description
When configuring actions in reporters, the Body or Message field is gone, there is no where to input a message.


Reproducing the issue step-by-step
Create new reporter, try to add any action, body/message field is not there.


Expected results vs. actual results


Sample of data


Additional details

Closing comment (2018-06-26T14:01:52Z): Duplicate of #473. The fix for this will be available today.
Repository: sentinl/sentinl

Issue #613: org.elasticsearch.index.mapper.MapperParsingException: failed to parse
Created: 2018-11-21T01:34:04Z
test

Duplicate issue #614: webhook action: Error: store alarm: [mapper_parsing_exception] failed to parse 
Created: 2018-11-21T07:55:15Z
test

Closing comment (2018-11-22T08:32:41Z): @aabababb seems it is a duplicate of #613
Repository: sentinl/sentinl

Issue #201: Watcher action email_html is not sending action's html text
Created: 2017-08-24T08:43:43Z
Issue Description
When using email_html action I configured different messages for plaint text (email_html action's body property) and HTML email (email_html action's html property). However, I'm only getting emails with plain text.


Reproducing the Issue step-by-step
Configure email_html action, in body property set message1, in html property set message2. When action is triggered and email is sent, email will contain message1 in both text/html and text/plain email message parts.


Expected Results vs. Actual Results
Email message should have HTML body from action's html property, not action's body property (which is valid for text part, not HTML part of message, as per configuration examples from wiki).


Additional Details
It seems there is a typo in https://github.com/sirensolutions/sentinl/blob/master/server/lib/actions.js#L202, instead of using action.email_html.body there should be action.email_html.html at both places in given line, to use configured html text as per given configuration sample at line https://github.com/sirensolutions/sentinl/blob/master/server/lib/actions.js#L194.

Duplicate issue #211: email html action is not working
Created: 2017-09-20T05:03:11Z
in server/lib/action.js:202:
    var html;
    if (_.has(action, 'email_html')) {
      formatterS = action.email_html.subject ? action.email_html.subject : 'SENTINL: ' + key;
      formatterB = action.email_html.body ? action.email_html.body : 'Series Alarm {{ payload._id}}: {{payload.hits.total}}';
      formatterC = action.email_html.body ? action.email_html.body : '<p>Series Alarm {{ payload._id}}: {{payload.hits.total}}</p>';
the formatterC still use action.email_html.body ? action.email_html.body, it should be action.email_html.html ? action.email_html.html

Closing comment (2017-09-20T06:04:23Z): duplicate of #201
Repository: sentinl/sentinl

Issue #577: reports: mail subject and content ignored
Created: 2018-10-10T13:46:12Z
Kibana version:
6.2.4
Elasticsearch version:
6.2.4
Report engine:
puppeteer
Describe the bug:
when sending a report, Subject & Content fields are ignored
Steps to reproduce:

Setup a report using wizard, fill Subject & Content fields
Generate the report

Expected behavior:
Resulting email Subject & Content should match what has been defined.
Actually:
email subject = "SENTINL: " + report "Title"
email content = empty, only the attachment is present

Duplicate issue #585:  Sentinl Report Title and Body not effective.
Created: 2018-10-22T03:54:13Z
1.Mail is acceptable，but Sentinl Report Title and Body not effective.
2.Expect to nest a description in the screenshot
3.for example:
"actions": {
"report_dashboard": {
"report": {
"to": "xxxxxx",
"from": "xxxxx",
"subject": "Report Title",#Not in effect in the email
"priority": "high",
"body": "Series Report",#Not in effect in the email
"snapshot": {
"res": "1280,900",
"url": "http://www.google.com",
"path": "/tmp/",
"params": {
"username": "xxxxx",
"password": "xxxxx",
"delay": 5000,
"crop": false
}

Closing comment (2018-10-23T08:47:23Z): Duplicate of #577
Repository: sentinl/sentinl

Issue #577: reports: mail subject and content ignored
Created: 2018-10-10T13:46:12Z
Kibana version:
6.2.4
Elasticsearch version:
6.2.4
Report engine:
puppeteer
Describe the bug:
when sending a report, Subject & Content fields are ignored
Steps to reproduce:

Setup a report using wizard, fill Subject & Content fields
Generate the report

Expected behavior:
Resulting email Subject & Content should match what has been defined.
Actually:
email subject = "SENTINL: " + report "Title"
email content = empty, only the attachment is present

Duplicate issue #583: Sentinl report subject and body not effective.
Created: 2018-10-22T03:38:01Z
Kibana version:
Elasticsearch version:
Server OS version:
Browser version:
Browser OS version:
Original install method (e.g. release pkg link, gulp, from source, etc.):
Describe the bug:
Steps to reproduce:

Mail is acceptable，but Sentinl Report Title and Body not effective.

Expected behavior:
2.Expect to nest a description in the screenshot
Sample of data you have in Elasticsearch
Full watcher document
Screenshots (if relevant):
{
"actions": {
"report_dashboard": {
"report": {
"to": "xxxxxx",
"from": "xxxxx",
"subject": "Report Title",
"priority": "high",
"body": "Series Report",
"snapshot": {
"res": "1280,900",
"url": "http://www.baidu.com",
"path": "/tmp/",
"params": {
"username": "xxxxx",
"password": "xxxxx",
"delay": 5000,
"crop": false
}
},
"stateless": false
}
}
},
"input": {
"search": {
"request": {
"index": [
"logstash-dmpdatatest630"
],
"body": {
"size": 1000,
"query": {
"bool": {
"must": [
{
"script": {
"script": {
"lang": "painless",
"params": {
"costTimeThrehold": 10000
},
"source": "if(doc['sceneInfo.playerdelay'].value > params.costTimeThrehold){true; } else{false;}"
}
}
},
{
"range": {
"@timestamp": {
"gte": "now-1M",
"lte": "now"
}
}
}
]
}
}
}
}
}
},
"condition": {
"script": {
"script": "payload.hits.total >= 1"
}
},
"trigger": {
"schedule": {
"later": "every 1 minutes"
}
},
"disable": true,
"report": true,
"title": "SinglePlay",
"save_payload": true,
"spy": true,
"impersonate": false
}
Errors in browser console (if relevant):
Provide Kibana logs and/or server output (if relevant):
Any additional context:
Tips:

Try to query Elasticsearch manually first. Do you receive the results you want for your query?
For example, on Linux, you can query Elasticsearch using curl:

curl -X GET "localhost:9200/_search?pretty" -H 'Content-Type: application/json' -d'
{
  "query": { 
    "match_all": {}
  }
}
'

Closing comment (2018-10-23T08:47:17Z): Duplicate of #577
Repository: sentinl/sentinl

Issue #473: Unable to specify message when creating new actions
Created: 2018-06-22T11:52:22Z
Sentinl and Kibana version
Kibana: 6.2.4
Sentinl: 6.2.4 (master)


Issue description
Unable to specify message when creating new actions in sentinl.


First image: https://github.com/sirensolutions/sentinl/releases/download/tag-6.2.3-3/sentinl-v6.2.4.zip

Second image: https://github.com/sirensolutions/sentinl master branch



Reproducing the issue step-by-step
(master)
In the process of creating a watcher I am unable to specify what message I would like to send.


Expected results vs. actual results
Expected is the first image.
Actual is the last image.


Sample of data


Additional details

Duplicate issue #480: Unable to delete watcher/reporter actions
Created: 2018-06-26T13:37:03Z
Sentinl and Kibana version
6.2.3


Issue description
When creating a new watcher or reporter, I'm unable to delete actions like the default "email_admin" or any other action that I add.


Reproducing the issue step-by-step
Create new watcher/reporter, try to delete the default "email_admin" action, no error is shown but action is not removed even after saving.


Expected results vs. actual results


Sample of data


Additional details

Closing comment (2018-06-26T14:04:50Z): This related to #473
The fix will be available today.
Repository: sentinl/sentinl

Issue #577: reports: mail subject and content ignored
Created: 2018-10-10T13:46:12Z
Kibana version:
6.2.4
Elasticsearch version:
6.2.4
Report engine:
puppeteer
Describe the bug:
when sending a report, Subject & Content fields are ignored
Steps to reproduce:

Setup a report using wizard, fill Subject & Content fields
Generate the report

Expected behavior:
Resulting email Subject & Content should match what has been defined.
Actually:
email subject = "SENTINL: " + report "Title"
email content = empty, only the attachment is present

Duplicate issue #584: Sentinl report subject and body not effective. #583
Created: 2018-10-22T03:52:46Z
1.Mail is acceptable，but Sentinl Report Title and Body not effective.
2.Expect to nest a description in the screenshot
3.for example:
"actions": {
"report_dashboard": {
"report": {
"to": "xxxxxx",
"from": "xxxxx",
"subject": "Report Title",#Report Title is not effective in email.
"priority": "high",
"body": "Series Report",#body  is not effective in email.
"snapshot": {
"res": "1280,900",
"url": "http://www.google.com",
"path": "/tmp/",
"params": {
"username": "xxxxx",
"password": "xxxxx",
"delay": 5000,
"crop": false
}

Closing comment (2018-10-23T08:47:36Z): Duplicate of #577
Repository: sequelize/sequelize

Issue #13062: Example code for getters incorrectly uses identifier, should be string
Created: 2021-02-28T03:39:16Z
Issue Description
What was unclear/insufficient/not covered in the documentation
On this page:
https://sequelize.org/master/manual/getters-setters-virtuals.html#getters
getDataValue(username) is not valid.
If possible: Provide some suggestion on how we can enhance the docs
Correct code is getDataValue('username')
Additional context
N/A
Issue Template Checklist

Is this issue dialect-specific?

 No. This issue is relevant to Sequelize as a whole.
 Yes. This issue only applies to the following dialect(s): XXX, YYY, ZZZ
 I don't know.

Would you be willing to resolve this issue by submitting a Pull Request?


 Yes, I have the time and I know how to start.
 Yes, I have the time but I don't know how to start, I would need guidance.
 No, I don't have the time, although I believe I could do it if I had the time...
 No, I don't have the time and I wouldn't even know how to start.

Duplicate issue #13445: Minor snippet issue in "Getters, Setters & Virtuals" section of docs
Created: 2021-08-14T07:37:47Z
Issue Creation Checklist
[x] I have read the contribution guidelines
Issue Description
What was unclear/insufficient/not covered in the documentation
In "Getters" section ,the type of parameter which pass to function getDataValue should be "String",or it would report ReferenceError when copying example-code to run.

If possible: Provide some suggestion on how we can enhance the docs
After adding double quote to username , ReferenceError disappears .

Additional context
Add any other context or screenshots about the issue here.

Closing comment (2021-08-29T09:36:20Z): Duplicate #13062 #12811 #12655
PR that closes this issue.
Repository: sequelize/sequelize

Issue #7961: updatedAt (on update) not working
Created: 2017-07-16T17:20:35Z
What you are doing?
When updating a model the "updated_at" field is not updated automatically.
//price model
const Price = sequelize.define('prices', {
  	amount: Sequelize.INTEGER.UNSIGNED,
  	updated_at: Sequelize.DATE,
},
{
  underscored: true,
  timestamps: true,
  createdAt: false,
});

//updating the model
Price.findOne({
  where: {id: 1}
}).then(price => { 
	price.update({
    	amount: 150,
    })
});
What do you expect to happen?
Automatic updating "updated_at" attribute.
What is actually happening?
No updated of "created_at" occurs after updating the price value.
Dialect: mysql
Database: version:5.7.18
Sequelize: version:4.3.2

Duplicate issue #9803: updatedAt (on update) not working
Created: 2018-08-15T21:18:43Z
When updating a model the "updated_at" field is not updated automatically.
//price model
const Price = sequelize.define('prices', {
amount: Sequelize.INTEGER.UNSIGNED,
updated_at: Sequelize.DATE,
},
{
underscored: true,
timestamps: true,
createdAt: false,
});
//updating the model
Price.findOne({
where: {id: 1}
}).then(price => {
price.update({
amount: 150,
})
});
What do you expect to happen?
Automatic updating "updated_at" attribute.
What is actually happening?
No updated of "created_at" occurs after updating the price value.
Dialect: mysql
Database: version:5.7.18
Sequelize: version:4.3.2

Closing comment (2018-08-15T21:19:04Z): related to: #7961
Repository: sequelize/sequelize

Issue #11800: Multi-tenancy scenario support
Created: 2020-01-07T18:27:04Z
Issue Description
What was unclear/insufficient/not covered in the documentation
Is there a reasonable way to support multi-tenancy with a schema-based tenant?
ex, I have 3 DBS, each DB has the same table structures so it could use the same modules, but it requires 3 Knex connections, how would someone manage to kee the 3 connections and selecting the right one when using a model?
Is this issue dialect-specific?

 No. This issue is relevant to Sequelize as a whole.
 Yes. This issue only applies to the following dialect(s): XXX, YYY, ZZZ
 I don't know.

Would you be willing to resolve this issue by submitting a Pull Request?


 Yes, I have the time and I know how to start.
 Yes, I have the time but I don't know how to start, I would need guidance.
 No, I don't have the time, although I believe I could do it if I had the time...
 No, I don't have the time and I wouldn't even know how to start.

Duplicate issue #11783:  Change schema according to tenant
Created: 2020-01-02T00:24:37Z
I would like to dynamically change the schema according to the request tenant.
I didn't find anything in the documentation about
I'm using Postgres and Express

Closing comment (2020-01-17T15:15:39Z): Duplicate of #11800
Repository: sequelize/sequelize

Issue #11155: Superfluous data passed to create and update statements should be logged
Created: 2019-07-05T20:33:14Z
When you pass additional data columns than supported by the sequelize model, they are ignored. However, that may be because someone forgot to add a  column. It would make sense to log a warning when this happens.
Describe the solution you'd like
An optional warning indicating that a data column is passed that doesn't match the model. Ideally, the data value should be logged. So, in case someone does fuck up, they can at least retrieve the data from the logs.
Why should this be in Sequelize
To avoid undetected bugs

Duplicate issue #11070: How to validate fields in "where"
Created: 2019-06-15T19:53:46Z
If we misspelled field name then it will be ignored. And that may lead to bugs that hard to debug.
Is it possible to make throw error when we use unknown column in where?
// our User model have field wallet_ref
var moneyRecipient = await User.findAll({where: {wallet_id: "xxx"}})
^ this will generate query with WHERE 1=1, and we will send money to wrong user

Closing comment (2019-08-01T01:14:16Z): Similar to #11155
Repository: sequelize/sequelize

Issue #11033: defaultValue support async function
Created: 2019-06-05T01:41:19Z
I hope defaultValue can support async function in model defintiton,for example:
sequelize.define('foo', {
 id: { type: Sequelize.TEXT, allowNull: false, defaultValue: async ()=>{ return await doSome();}}
});

Duplicate issue #11054: Model.init , attributes.column.defaultValue should be supporting Promise
Created: 2019-06-11T14:47:48Z
Is your feature request related to a problem? Please describe.
http://docs.sequelizejs.com/class/lib/model.js~Model.html#static-method-init
I read the docs, making defaultValue function reuturn a Promise,but it didnot resolve the value,it turned out the [object Object], the sql  error message is sqlMessage: "Incorrect integer value: '[object Object]' for column 'id' at row 1",
Describe the solution you'd like
attributes.column.defaultValue should be supporting async function or return  Promise as defaultValue
Why should this be in Sequelize
In some case, the defaultValue is asynchronously generating, one of the best ways is to return a Promise。
Describe alternatives you've considered
In my Case, I did not have a good way to solve Promise value as defaultValue
Usage example
    id: {
      type: BIGINT.UNSIGNED,
      primaryKey: true,
      autoIncrement: false,
      defaultValue() {
        return snowflake();//snowflake() return  `Promise`
      }
    },
Additional context
none

Closing comment (2019-07-25T22:58:08Z): Duplicate of #11033
Repository: servo/webrender

Issue #1432: Support ANGLE with wrench
Created: 2017-06-28T18:27:44Z
This makes us closer to Gecko

Duplicate issue #1550: Get wrench running with ANGLE on windows.
Created: 2017-08-03T23:52:06Z
This would make the benchmarks more representative of what we would intend to ship products with.

Closing comment (2017-08-10T13:52:25Z): It seems similar to #1432

Indeed. Closing as duplicate.