primordic/IssueDupesLite huggingface dataset:
Repository: halide/Halide

Issue #416: Fail compilation and execution. 
Created: 2014-08-09T20:35:17Z
Hello, I am trying to run the first example in Ubuntu 14.4, but the following errors occur:
g++ lesson_01_.cpp -g -I ../include -L ../bin -lHalide  -lpthread -ldl -o lesson_01
../bin/libHalide.so: referência indefinida para `std::_throw_out_of_range_fmt(char const, ...)@GLIBCXX_3.4.20'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Then I tried this:
g++ lesson_01*.cpp -g -I ../include -L ../bin -lHalide  -lpthread -ldl -o lesson_01 -shared -fPIC
Compiled normally, but when trying to run the generated file displays the following error:
Segmentation fault (core image recorded)
What will be the problem? is missing some library?
Thank you very much.
Sorry for bad english.

Duplicate issue #486: Link error attempting to compile tutorial/lesson_01 on ubuntu 14.04 x86_64, g++ 4.8.2
Created: 2014-10-01T01:50:28Z
Obtained from :
halide_Linux_64_trunk_58ba5da3b99de2654d2554cae32ea3a712ae4857_2014_07_16.tgz
Build command as specified:
g++ lesson_01*.cpp -g -I ../include -L ../bin -lHalide -lpthread -ldl -o lesson_01
The error is
../bin/libHalide.so: undefined reference to `std::__throw_out_of_range_fmt(char const*, ...)@GLIBCXX_3.4.20'
collect2: error: ld returned 1 exit status
A quick google shows that this type of issue has been reported on many projects and seems to be caused by building a lib against one version of libstdc++ and then linking to an application built with another.
It's not specific to this system - earlier today I tried the same thing on an older ubuntu machine and got the same error. I don't recall the version but it was running gcc 4.6.3.
In any case, this appears to be an issue that could be fixed by specifying which version(s) of libstdc++ the supplied binaries can be expected to work with.
I will try building from source using clang 3.4
UPDATE: no problem building using clang 3.4 from the instructions in README.

Closing comment (2014-10-02T01:35:24Z): Duplicate of #416. (I'm surprised that searching for '__throw_out_of_range_fmt' doesn't find either issue).
Repository: halide/Halide

Issue #4599: Adjoints from Generators with Scalar Parameters
Created: 2020-02-09T18:12:02Z
Hello Halide-Team,
(thanks for putting your efforts in such a neat to tool for more application oriented programmers and scientists!)
I have started to play around with the rather recent feature of auto-diff and the -d 1 option to generators. Although maybe not the primary concern for prototypical DL applications, generators with scalar input parameters Input<scalar_type> seem currently not supported and running the generator fails:
$ bin/host/lens_blur.generator -g lens_blur -e static_library,h,registration,stmt,assembly -o bin/host -f lens_blur target=host auto_schedule=true -d 1
Internal Error at /home/cl/workspace/halide/Halide/src/Generator.cpp:1490 triggered by user code at :
Condition failed: input->parameters_.size() == input->funcs_.size():
>>CORE DUMP<<

I wondered if there is a fundamental obstacle for supporting scalar inputs, if this feature has just been postponed, or if a bug made it into the implementation. Alas, I did not have the chance for a deep dive to see what's going on under the hood yet. As a work-around, one might pass a scalar Func which is likely not the stylistically preferred alternative in the long run.
Best,
Christian
ps. One little thing. Knowing about the recent make doc target, the online documentation currently seems not to reflect the latest API changes, e.g. Func::set_estimates().

Duplicate issue #5406: Internal compiler error when differentiating generators with scalar parameters.
Created: 2020-10-26T18:25:55Z
Make a generator with a scalar input (the example generator in test/generators works) and try to take the derivative
abadams@anadams-work:~/projects/Halide_autodiff_generator_scalar_bug
$ make bin/example.generator
make: 'bin/example.generator' is up to date.

abadams@anadams-work:~/projects/Halide_autodiff_generator_scalar_bug
$ bin/example.generator -g example -o . target=host -d 1
Internal Error at /home/abadams/projects/Halide_autodiff_generator_scalar_bug/src/Generator.cpp:1544
Condition failed: input->parameters_.size() == input->funcs_.size():
Aborted (core dumped)

I imagine the issue is that in the reverse pipeline that scalar input needs to turn into a scalar output, which could be done as a zero-dim buffer but isn't. We at least need an error message here, but ideally we'd turn them into zero-dim buffer outputs.
Not sure who did the autodiff support for generators. Maybe @BachiLi ?

Closing comment (2020-10-28T07:24:26Z): Same as #4599.
Repository: halide/Halide

Issue #2784: Parameters can leak if self-referential Exprs are used
Created: 2018-02-28T19:31:47Z
Consider a snippet like so:
int main() {
  Var x("x");
  Func f("f");
  f(x) = 0;

  auto d0 = f.output_buffer().dim(0);
  d0.set_bounds(0, d0.extent());

  return 0;
}

If you run this under a good leak detector (e.g. Clang ASAN), you'll find that the Parameter attached to f.output_buffer() has leaked.
Interestingly, I can only make this fail as of recent Halide builds; a Halide snapshot of 5125fa3 (~Feb 12) doesn't appear to leak for me, but 1d27985 (~Feb 26) does not. That said, it's not clear to me how we were avoiding cyclical refs before, or what might have changed in this timeframe.

Duplicate issue #4527: ImageParams can be held by Exprs and also hold Exprs, so they can participate in reference cycles and cause leaks
Created: 2020-01-14T17:42:47Z
E.g:
Halide::ImageParam result(Halide::type_of<float>(), 2); 
result.dim(1).set_stride(result.dim(0).extent());

We need to be able to detect cycles among Parameter objects. I don't think such a cycle can legally include a Function, (the Exprs in a Parameter can't call Functions), but this is probably unchecked, so some members of the cycle could be Function objects too.
It seems that everything that can be referred to by an Expr and also can hold Exprs needs to be cycle-aware.

Closing comment (2020-01-14T21:35:41Z): Might be related to #2784?
Repository: halide/Halide

Issue #7606: ASAN reports out-of-bounds read error in `anderson2021_test_apps_autoscheduler`
Created: 2023-06-01T23:32:15Z
ASAN is reporting an out-of-bounds read error in SearchSpace.cpp:125; examination reveals that we are reading past the end of a std::vector (in this case, c->size.size() is 1, but l.pure_dim is 1)... so this is a real bug.
Unfortunately I have no idea where to even begin debugging this... assigning to @abadams for now to see if he can route it to the right person.
(ASAN isn't necessary to repro this bug, just add something like internal_assert(l.pure_dim < c->size.size()); in the code)
(But if you want to run with asan, just add --preset linux-x64-asan to the cmake and ctest commands)

Duplicate issue #7539: Anderson2021 autoscheduler should ignore multitarget
Created: 2023-04-29T00:24:05Z
If you are building with multitarget and specify the Anderson2021 autoscheduler, the schedule file produced will contain multiple identical copies of the same schedule; this is a waste of time (since we compute the same schedule multiple times) and confusion (since the schedule is the same). We should improve this, but it requires some additional plumbing to do it cleanly.

Closing comment (2023-07-20T16:19:36Z): This might be a duplicate of #7606 -- can you offer a repro case of what you are seeing?

Sure. I will submit a draft PR featuring the repro case. Moving the discussion to #7606 .
Repository: halide/Halide

Issue #5374: Some apps are missing CMake builds
Created: 2020-10-19T17:53:25Z
The following apps do not have CMake builds and so are not properly tested on CI

 HelloAndroid (not built by Makefile either)
 HelloAndroidCamera2 (not built by Makefile either)
 HelloAndroidGL (not built by Makefile either)
 HelloMatlab
 HelloPyTorch (not built by Makefile either)
 HelloiOS (not built by Makefile either)
 HelloWasm (has CMake build, not built by Makefile)
 auto_viz (not built by Makefile either)
 fft
 hexagon_benchmarks (not built by Makefile either)
 hexagon_dma (not built by Makefile either)
 linear_blur (not built by Makefile either)
 nn_ops (not built by Makefile either)
 onnx
 opengl_demo (not built by Makefile either)
 openglcompute (not built by Makefile either)
 resnet_50
 simd_op_check (not built by Makefile either)

There might be good reasons for some of these, eg. I think linear_blur uses generator stubs, which aren't available from CMake (yet/ever). But even then, we should document that somewhere.

Duplicate issue #5399: We are missing a CMake example for Android target
Created: 2020-10-23T14:55:38Z
The section
https://github.com/halide/Halide/blob/master/README_cmake.md#use-externalproject-directly
gives some idea of what is needed to use Halide in a project that targets Android and uses CMake.
But it's a big hurdle to actually do this. Can you provide a HelloWorld example in the apps folder for this scenario?
I'm a library developer and I'm not interested and not able to read Gradle files, only CMake/make. I think that this is quite a common case because a lot of people using Halide are going to be library developers as opposed to app developers.

Closing comment (2020-10-27T17:02:43Z): This is a duplicate of #5374

I was not clear. I meant that I want an example with an Android library (static or shared), as opposed to a full app. I think this is an important distinction that deserves a separate example. To my knowledge it doesn't exist.
Repository: haml/haml

Issue #231: Comment output brocken for compact style
Created: 2010-08-12T11:30:25Z
/*
 * LICENCE INFO
 */

Results in (for compact style):
/* LICENCE INFO /

For default style it works well. It also works well if you remove the leading space before the closing comment.

Duplicate issue #232: Comment output brocken for compact style
Created: 2010-08-12T11:30:25Z
/*
 * LICENCE INFO
 */

Results in (for compact style):
/* LICENCE INFO /

For default style it works well. It also works well if you remove the leading space before the closing comment.

Closing comment (2010-08-12T17:49:58Z): Duplicate of #231 and #226.
Repository: haml/haml

Issue #648: Interpolation and whitespace
Created: 2013-03-10T00:11:46Z
%pre
  Hello #{}
  interpolated
produces
<pre>Hellointerpolated</pre>
or
<pre>Hello interpolated</pre>
in ugly mode.

Duplicate issue #748: Newlines are added to scripts with blocks in non-ugly, not in ugly
Created: 2014-02-21T21:49:03Z
If the result of a ruby method that is passed a block is included with = then the behaviour is different in ugly and non-ugly modes.
An example with Rails’ link_to helper:
= link_to 'http://example.com/1' do
  %span Example 1

= link_to 'http://example.com/2' do
  %span Example 2
produces this in development (i.e with ugly set to false):
<a href="http://example.com/1"><span>Example 1</span>
</a>
<a href="http://example.com/2"><span>Example 2</span>
</a>
but in production (ugly true) produces:
<a href="http://example.com/1"><span>Example 1</span>
</a><a href="http://example.com/2"><span>Example 2</span>
</a>
This may not seem much, but depending on your styling can be significant.
A simpler, somewhat contrived, non-Rails example that more clearly shows the difference in results:
-def foo
  - "Hello"

=foo do
  .ignored
=foo
produces
Hello
Hello
in normal mode and
HelloHello
in ugly mode.
When compiling the push_script method adds a trailing newline in normal mode, but not in ugly mode if a block is given. If no block is given a newline is added even in ugly mode
In normal mode the script is handled by the format_script method, which strips trailing whitespace. With the newline provided by push_script the result is always a single newline. In ugly mode format_script (usually) doesn’t handle it, so the result is whatever number newlines are returned from the method, which could be zero.
I think we should always add a newline after the script in ugly mode, to reduce the difference between the two modes. Making that change only causes a couple of tests to fail, where they are expecting a single trailing newline but get two.
(This issue was prompted by this SO question: http://stackoverflow.com/questions/21741015/haml-render-different-html-in-two-different-stages)

Closing comment (2017-03-06T19:07:09Z): @k0kubun the original intent of #751 was to make ugly and non-ugly modes behave (almost) the same. Now that there is only one mode it’s not needed from that point of view. I hadn’t really considered the issue of scripts with blocks behaving differently from those without.
This appears to be (loosely) related to #648 (which is in turn related to #465 which you recently commented on) as they all deal with when a script should have a newline added afterwards.
My thoughts are that we should aim for consistency if possible (i.e. always adding a newline after a script), but I don’t know if people are relying on the current behaviour. If we do make changes, now—in a major version bump—would be the best time.
Repository: haml/haml

Issue #97: Feature Request: Import Folder
Created: 2010-03-05T00:02:51Z
It would be very useful to be able to import all the files inside a folder by only providing:
@import folder_name
Right now, my system has a lot of churn due to the fact that I need to have an extra sass file that imports all the files in a folder.  I'm sure I can't be the only one...
Thanks!

Duplicate issue #237: Add directory glob include/watch support to SASS
Created: 2010-08-16T19:29:29Z
I would like to build an .scss file out of all .scss files within a directory, including subdirectories:
css/foo.scss:
@import "foo/**/*.scss"

css/foo/_bar.scss:
.bar { font-size: 2em; }

css/foo/qux/_quux.scss:
.qux .quux { color: green; }

See also this thread.

Closing comment (2010-08-16T20:17:02Z): Duplicate of #97 and #207. The answer is still no.
Repository: haml/haml

Issue #241: FYI: haml-rails's issue #1
Created: 2010-08-25T02:42:26Z
This is haml-rails's issue but adding :: in all Rails in haml/util.rb will fix this.
http://github.com/indirect/haml-rails/issues/#issue/1

Duplicate issue #244: RAILS_ROOT and RAILS_ENV
Created: 2010-08-27T21:01:45Z
Can you please fix deprecation warnings in some files?
DEPRECATION WARNING: RAILS_ROOT is deprecated. Please use ::Rails.root.to_s. (called from rails_root at lib/haml/util.rb:276)
DEPRECATION WARNING: RAILS_ENV is deprecated. Please use ::Rails.env. (called from rails_env at lib/haml/util.rb:287)

Closing comment (2010-08-27T21:15:56Z): haml-rails defines a Haml::Rails class, which interferes when Haml tries to refer to Rails.
Closing as a duplicate of #241
Repository: haml/haml

Issue #248: form_tag outputs directly to the Haml template
Created: 2010-08-30T00:50:35Z
I just updated a Rails 3 RC 2 application to Rails 3 Final and Im getting the following error now:
form_tag outputs directly to the Haml template.
Disregard its return value and use the - operator,
or use capture_haml to get the value as a String.
(ActionView::Template::Error)
/Users/dcrec1/.bundle/ruby/1.9.1/bundler/gems/haml-3511ef9/lib/haml/buffer.rb:133:in format_script_false_false_false_true_false_false_true' ./app/views/layouts/application.html.haml:17:in_app_views_layouts_application_html_haml___1720253655888528308_2181331840__1377659222366036362'
The code looks like this:
= form_tag search_path do
= text_field_tag 'q'
= submit_tag t(:search)
I tried with Haml 3.0.17 and edge

Duplicate issue #249: Rails 3.0.0 release and 3-0-stable...
Created: 2010-08-30T04:16:14Z
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5493-form_for-silently-failing-with-rails-300#ticket-5493-7
It appears that the introduction of the haml gem causes 3.0.0 and 3-0-stable to fail silently.

Closing comment (2010-08-30T04:23:57Z): Dup of #248.
Repository: haml/haml

Issue #233: "sass -watch ." broken with 3.0.16
Created: 2010-08-12T16:26:29Z
The following command to watch the current directory for changes produces an error since 3.0.16
sass --watch .
NoMethodError: private method `split' called for nil:NilClass
Use --trace for backtrace.
I have a gut feeling that "Use better heuristics for figuring out when someone might be using the wrong syntax with sass --watch" is making things worse.

Duplicate issue #235: (3.0.16) sass --watch requires colon else fails with undefined method split
Created: 2010-08-13T18:01:41Z
sass --watch  used to work (i.e. without colon-separated paths), implicitly
treating the watched directory as the destination directory.  in 3.0.16 they
must both be specified.
[davidjh@nyx]
$ sass --version
Haml/Sass 3.0.16 (Classy Cassidy)

Steps to reproduce
[davidjh@nyx]
$ sass --trace --watch public/stylesheets/
/home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:445:in `split_colon_path': undefined method `split' for nil:NilClass (NoMethodError)
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:441:in `colon_path?'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:459:in `probably_dest_dir?'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:391:in `watch_or_update'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:349:in `process_result'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:41:in `parse'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/lib/haml/exec.rb:21:in `parse!'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/gems/haml-3.0.16/bin/sass:8:in `<top (required)>'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/bin/sass:19:in `load'
    from /home/davidjh/.rvm/gems/ruby-1.9.2-rc1/bin/sass:19:in `<main>'

Workaround
[davidjh@nyx]
$ sass --trace --watch public/stylesheets/:public/stylesheets/
>>> Sass is watching for changes. Press Ctrl-C to stop.

Closing comment (2010-08-13T18:04:01Z): Duplicate of #233.
Repository: haml/haml

Issue #97: Feature Request: Import Folder
Created: 2010-03-05T00:02:51Z
It would be very useful to be able to import all the files inside a folder by only providing:
@import folder_name
Right now, my system has a lot of churn due to the fact that I need to have an extra sass file that imports all the files in a folder.  I'm sure I can't be the only one...
Thanks!

Duplicate issue #207: Import wildcard
Created: 2010-07-02T23:19:29Z
I like to split up my stylesheets into a large number of files (dozens) in several subdirectories. It would save me a lot of typing if I could write
import 'dir1/*'
import 'dir2/*'

instead of a long series of import 'dir1/whatever's. Currently, the * is interpreted literally.

Closing comment (2010-07-02T23:46:46Z): Duplicate of #97
Repository: haml/haml

Issue #20: Sass: Syntax error when nesting functions as arguments to mixins
Created: 2009-07-17T17:15:00Z
=foo(!var)
  color= !var

.foo
  +foo(rgb(1,255,127))

raises a parse error:
Syntax error on line 5: Expected rparen token, was end of text.

Duplicate issue #23: calling sass functions within mixin arguments
Created: 2009-08-03T18:42:37Z
If you try to call a sass function as a mixin argument you get a syntax error.
Example:
=foo(!a)
  div
    :background-color = !a

+foo(rgb(255,255,0))

Closing comment (2009-08-04T04:56:39Z): Isn't this a duplicate of #20?
Repository: haml/haml

Issue #90: haml >= 2.2.18 with rails xss breaks helper
Created: 2010-02-12T14:51:48Z
I have the following form helper:
def form_tag_remote(url_for_options = {}, options = {}, *parameters_for_url, &block)
concat('<iframe id="blackhole" name="blackhole"></iframe>')
options = { :multipart => true, :target => "blackhole", :onsubmit => "show_spinner(); return true;" }.merge(options)
form_tag(url_for_options, options, *parameters_for_url, &block)
end
It works fine when using haml <= 2.2.17, but outputs the raw html when using haml >= 2.2.18.
It even doesn't work correctly when changed like this:
def form_tag_remote(url_for_options = {}, options = {}, *parameters_for_url, &block)
concat('<iframe id="blackhole" name="blackhole"></iframe>'.html_safe!)
options = { :multipart => true, :target => "blackhole", :onsubmit => "show_spinner(); return true;" }.merge(options)
form_tag(url_for_options, options, *parameters_for_url, &block).html_safe!
end

Duplicate issue #91: Escaped form_for in 2.2.19
Created: 2010-02-12T22:53:45Z
With the new release, the form_for gets escaped, and displayed as text.
Forcing 2.2.17 makes it work well.

Closing comment (2010-02-13T00:08:33Z): This is a duplicate of #90 and #86. It's fixed, it'll be released in 2.2.20 this weekend.
Repository: hammerjs/hammer.js

Issue #796: Enable Sourcegraph
Created: 2015-05-21T07:51:10Z
I want to use Sourcegraph for hammer.js code search, browsing, and usage examples. Can an admin enable Sourcegraph for this repository? Just go to https://sourcegraph.com/github.com/hammerjs/hammer.js. (It should only take 30 seconds.)
Thank you!

Duplicate issue #799: Enable Sourcegraph
Created: 2015-05-31T14:00:17Z
I want to use Sourcegraph for hammer.js code search, browsing, and usage examples. Can an admin enable Sourcegraph for this repository? Just go to https://sourcegraph.com/github.com/hammerjs/hammer.js. (It should only take 30 seconds.)
Thank you!

Closing comment (2015-06-07T19:04:23Z): Closing this as a duplicate of #796
Repository: hammerjs/hammer.js

Issue #602: Support for mousewheel? 
Created: 2014-07-16T12:09:37Z
Is there support for mousewheel in hammer.js v2?
Or can it be easily done with a custom recognizer? I'm unsure how to go about this; the docs seems lacking on this.

Duplicate issue #658: Support pinch and zoom for Chrome 36+/IE on desktop with multi-touchpads.
Created: 2014-09-04T16:40:22Z
If you open Google Maps on a desktop Chrome browser with a Macbook you will recognize that you can pinch and zoom the map with the touchpad.
This functionality is integrated since Chrome 36+ (desktop only).
It would be great if hammer.js would also allow desktop pinch and zoom for Chrome 36+ additionally.
Chrome issue regarding this feature: https://code.google.com/p/chromium/issues/detail?id=289887
Sample code for this feature: http://jsbin.com/qiyaseza/4/edit
It should also work with IE and a touchpad... but I cannot test this.

Closing comment (2014-09-04T16:51:33Z): this feature is related to #602
Repository: hammerjs/hammer.js

Issue #1050: Pan event doesn't work correctly with touch-action pan-y in Chrome 55
Created: 2016-11-28T03:46:11Z
Before upgrade to Chrome 55.0.2883.59 beta (64-bit), it works fine
but now, when I pulldown in chrome emulator , the panmove event just triggered once or twice, and the event data is not correct

this is the right event data when i set touchAction none, but if touchAction is none , the page will not scroll

coarse demo
http://jsbin.com/tevitozuku/edit?output

Duplicate issue #1110: Pan/Swipe issues on mobile Chrome w/ `overflow: auto` children
Created: 2017-05-16T17:10:24Z
Versions
Hammer.js 2.0.8, Chrome 58, Windows 7
Reproducer
https://codepen.io/kirschre/full/bWjoaJ
Steps
Open this page on Chrome mobile and attach a debugger - alternatively, open in Chrome, load developer tools (ctrl + shift + i), open device emulation mode (ctrl + shift + m). The reproducer just prints the names of swipe/pan events as they are generated. Click and drag (or swipe/pan) starting from the green area and observe the console output. Then, do the same actions, starting from the red area, and observe the console output.
Expected Behaviour
Swipe/pan events should behave the same way in each area, regardless of whether a child element has overflow: auto or not.
Observed Behaviour
Pan/Swipe events work as expected through the green area. In the regular desktop view, they work as expected in the red area as well. However, on mobile Chrome, and in desktop Chrome's mobile device view, events coming from the area with overflow property behave strangely. Swipe events don't seem to be fired ever, and pan events fire sporadically. Occasionally panend/pancancel will not fire after pan events. Hopefully I'm just missing something simple, but I haven't been able to find anything related in documentation/issues/SO.

Closing comment (2017-05-19T15:35:21Z): Discovered I was missing touch-action on the child with overflow. Other problems still remain, but closing this as a duplicate of #1050 and #1056.
Repository: hammerjs/hammer.js

Issue #595: Feature request: Rotation velocity
Created: 2014-07-12T21:15:47Z
In order to support kinetic rotation i.e. a case where the user rotates something, and the object would continue rotation after they release their touch, adding the information of rotation velocity is needed.

Duplicate issue #752: pinch/rotate velocity
Created: 2015-01-23T07:16:08Z
Hey,
Thanks for this great library. However, is there a way to get rotate and pinch velocity or is this limited to drag velocity? In case of the last, is there a particular reason why this is hard to add and if not can you direct me to the right place in the code to add this? Thanks!

Closing comment (2015-04-07T06:20:23Z): Duplicate of #595
Repository: hammerjs/hammer.js

Issue #1183: iOS 11.4 Safari does not trigger pan when scroll without a break
Created: 2018-06-18T08:14:49Z
before iOS 11
Each scroll without a break triggered pan events.
iOS 11
When scrolling without a break,
2nd and follow scrolls don't trigger pan events.

Duplicate issue #1192: iOS horizontal scroll issue while using press event on the child element
Created: 2018-08-27T13:47:32Z
i am developing a application using angular framework. I have used a hammerjs package for press event on the child elements, were there are number of child elements that creates an horizontal scroll. However after i applied this press event on the child elements, it restricts scroll while touching on the child element, where press event is applied, on iOS safari.
The same issue i had solved on android chrome browser by using [style.touch-action]="'pan-x'" .
however i am not finding solution for iOS safari.
i hope someone knows the solution here.
this is the tag where press event is applied:
<li [ngClass]="{'active':selectedCustomerIndex == i}" *ngFor="let item of customers;let i=index;" (press)="onLongPress(item)" [style.touch-action]="'pan-x' (click)="updateUserBasedProducts(item,i,$event);"> 
  </li>

Closing comment (2018-09-28T23:07:15Z): Same as
#1183
and mentioned here as well:
https://stackoverflow.com/questions/51815182/hammerjs-in-safari-scroll-issue
Repository: hammerjs/hammer.js

Issue #597: Customizing window and document
Created: 2014-07-14T07:59:27Z
Currently the library adds event handlers using global variables.
Would you be open to modifying or accepting a pull request to allow customizing the window by passing it in as an argument?

Duplicate issue #849: Remove global dependency to window and document
Created: 2015-09-02T21:39:41Z
Currently, Hammejs is required to have a DOM available. This makes non-browser tests breaks with the error
})(window, document, 'Hammer');
   ^
ReferenceError: window is not defined

Here, this test would fail:
// test.js
require('hammerjs');

mocha test.js
This makes testing components that require Hammer to fail.
Is there a way to differ the window binding ?
#178 may have the same issue.

Closing comment (2015-11-11T15:20:12Z): Curious, what non-browser test environment are you using?  If it's Phantom, you should have window available to you.
Closing in favor of more discussion here: #598
And as a duplicate of #597
Repository: hammerjs/hammer.js

Issue #292: Doubletap firing on single tap
Created: 2013-06-06T14:56:22Z
Testing the Hammer.js demo at http://eightmedia.github.io/hammer.js/ on a 1080p touchscreen triggers the 'doubletap' message on a single tap most of the time, only sometimes triggering just the 'tap' message.
The only way I have been able to get around this is to ignore any taps which occur shortly after previous tap.
In jquery.hammer.js I have replaced from line 1114 (check if double tap) section with the following code:
if(prev && prev.name == 'tap' &&
    (ev.timeStamp - prev.lastEvent.timeStamp) < 140 &&              // less than 140ms ago
    (prev.lastEvent.target.offsetLeft - ev.target.offsetLeft)==0 && // same h target
    (prev.lastEvent.target.offsetTop - ev.target.offsetTop)==0) {   // same v target
    console.log('no tap');
} else {
    console.log('tap');
    Hammer.detection.current.name = 'tap';
    inst.trigger(Hammer.detection.current.name, ev);
}
This now catches any secondary taps which occur (and of course won't trigger any doubletaps) but feels very hacky. Does anyone know anything about this issue?

Duplicate issue #447: Double event issue with hybrid mouse/touch system
Created: 2014-01-20T10:48:07Z
Dear all,
I'm writing software for a multitouch board. I have an issue with double events.
The demo below is tested on Chrome 32, Firefox 26 and Safari 7.0.1 on OS X.
I have the following log line in my main file.
Hammer(document).on('tap doubletap', function(e) {
  console.log('Hammer ' + e.type);
});
I put the following log (in hammer.js) right before checking all the gestures.
console.log('check all gestures for ' + eventData.srcEvent.type + '/' + eventData.eventType);
Hammer.utils.each(this.gestures, function(gesture) {
  // …
});
This is my console output on a single tap.
check all gestures for touchstart/start (hammer.js:833)
check all gestures for touchend/end (hammer.js:833)
Hammer tap
check all gestures for mousedown/start (hammer.js:833)
check all gestures for mouseup/end (hammer.js:833)
Hammer doubletap
Hammer tap

As you can obviously see my system triggers mouse events (for the first touch), as well as touch events for all touches.
Has anyone had this problem, and is there a known solution for this? As for now I'll continue debugging and trying out solutions.
Sidenote: I can't disable mouse events. The board I develop for is connected to a desktop computer. Thus the application should be usable via mouse on desktop, as well as via touch on the board.
Thanks for reading.

Closing comment (2015-06-08T05:16:03Z): Closing this a duplicate of #292
Repository: hammerjs/hammer.js

Issue #806: [META] Momentum and currentDelta support for gestures
Created: 2015-06-11T18:16:13Z
deltaX and deltaY currently represent the distance from the origin event.  This is great for simple CSS transforms and the like, but more event context is needed to build gestures with physics.
Example issue/PR #748
I propose hammer should expose something akin to originDeltas and currentDeltas.
I think that any actual momentum calculation is better left to a plugin or individual implementation, but that's up for debate.

Duplicate issue #414: Is there a deltaX / deltaY of last event fire?
Created: 2013-12-18T02:21:13Z
I noticed that when using the drag event, the deltaX and deltaY properties are the total distance you have dragged so far. Is there a delta of the number of pixels moved since the last event fire? How do I get this?

Closing comment (2015-06-11T19:48:13Z): Closing this as being tracked in #806
Repository: hammerjs/hammer.js

Issue #1053: HammerJS versioning is confusing
Created: 2016-12-07T14:33:43Z
Hi,
Checking this page:
https://www.npmjs.com/package/hammerjs
It says:
Hammer.js 2.0.6
However:
2.0.8 is the latest of 26 releases
Now:
npm install hammerjs and inside hammer.js:
/*! Hammer.JS - v2.0.7 - 2016-04-22

http://hammerjs.github.io/

WTF?

Duplicate issue #1043: Versions mismatched
Created: 2016-11-14T15:13:45Z
Just happened to notice, your Readme says 2.0.6, but the latest NPM version is 2.0.8

Closing comment (2016-12-07T17:10:56Z): same as #1053
cc:- @arschmitz @runspired please close.
Repository: haraka/Haraka

Issue #1323: Migrate to Streams3
Created: 2016-02-01T14:51:26Z
Currently Haraka implements SMTP by reading data from an incoming socket using the old stream 'data' event and parsing it line-by-line and dispatching the commands as they are read, then when the DATA command is sent, a secondary stream is created (message_stream) to buffer the headers and message data that plugins can then read from.
For 3.0 - we should migrate this to a Streams3 stream EventEmitter and run the plugins from the emitted events.
Due to the plugin architecture - I've been thinking that it might be best to create 'spool' files similar to how qpsmtpd works e.g. when we go into DATA mode, we write message to a transport file.   The transport file could be placed on tmpfs for speed.  When a plugin pipes the stream, we would output the current headers from memory, followed by the message body from transport file.   We would use transform streams for plugins like clamav which require special formatting.

Duplicate issue #1715: Rewrite attachment parsing code
Created: 2016-11-14T12:59:36Z
Attachment parsing/handling code is crap.
The code/flow is impossible to understand and documentation is lacking, transaction.attachment_hooks is a shame, it doesn't follow standard haraka hook style when you have to call next() cb in order to proceed further. More than that, it doesn't reflect it's name, the hook itself is called when whole attachment is parsed, and recommended usage ( using 4th argument, AttachmentStream to do the work ) defeats its purpose. The stream is emitted when whole attachment is already there, not when haraka started parsing it and stream emits stuff when that stuff is received/(parsed live) by haraka core.
Making next available would allow get rid of crazy hacks I/we have to implement in order to pause processing before the dot response.

Closing comment (2017-07-29T00:01:49Z): Closing as duplicate of #1323.
Repository: haraka/Haraka

Issue #2225: Haraka throws exception when local hostname includes underscores
Created: 2017-10-19T06:29:56Z
Haraka generates queue filenames based on hostname and joins separate parts with underscores. If the local hostname is configured to include underscore as well (eg "example_host" – not sure if it is even valid but it happens) then this underscore also gets included in the filename which results in a failed filename check which in turn is causes an exception to be thrown. Easy fix would be to replace underscore with a codepoint as is done with "/" and ":" but maybe something more thorough should be considered? Like replacing all non-alphanumeric chars with codepoints?

Duplicate issue #2342: Haraka throws exception because of machine name
Created: 2018-02-16T10:50:52Z
system info
Please report your OS, Node version, and Haraka version by running this shell script on your Haraka server and replacing this section with the output.
Haraka 2.8.15
Node v6.12.3
OS Linux 4.13.0-32-generic - 16.04.1-Ubuntu - _64 x86_64 x86_64 GNU/Linux
openssl | OpenSSL 1.0.2g
Expected behavior
Haraka to not error because of machine name
Observed behavior
My machine name had an underscore in it. When qfile.parts checks the transaction file name, which has the machine name appended to it, it throws a bad filename exception
Steps to reproduce
Rename your machine to include an underscore

Closing comment (2018-02-16T16:24:26Z): Duplicate of #2225 and and fixed in #2324.
Repository: haraka/Haraka

Issue #1873: Disable outbound delivery
Created: 2017-03-31T07:31:18Z
Hi I'm trying to implement an email journaling system,
where I would like to queue up incoming mails to a rabbitMQ queue
and process the mails with another system, but I don't want any outbound
capabilities.
The communication between the other SMTP server (which sends the journals)
and Haraka is encrypted via TLS. I use GMail's SMTP server for sending the journals
for all the company emails.
My question is, how do I go by implementing this, is it already possible with Haraka core
or with existing plugins, or will I have to write my own plugin(s) for this, and if that's the case, where should I "hook" in?
Thanks in advance.

Duplicate issue #1909: Authentication required when using TLS
Created: 2017-05-08T06:14:58Z
Currently in connection.js, there exists the following block of code:
    // Require authentication on connections to port 587 & 465
    if (!this.relaying && [587,465].indexOf(this.local.port) !== -1) {
        this.errors++;
        return this.respond(550, 'Authentication required');
    }

This block is run during the MAIL command (before the plugin hook).
Is this necessary?
I have a plugin that authorises users based on their IP address and MAIL FROM that doesn't work on TLS, but is fine when used in plaintext.

Closing comment (2017-05-08T21:54:11Z): Duplicate of #1873
Repository: haraka/Haraka

Issue #2374: Fix calls to `new Buffer()`
Created: 2018-03-22T15:36:41Z
Node has deprecated new Buffer() - as of node 10 it throws a warning.
We'll need to fix the approx 30 or so places we use this.

Duplicate issue #2548: Problem non-latin symbols
Created: 2018-11-28T14:47:42Z
system info



Haraka
Haraka.js — Version: 2.8.21




Node
v7.10.1


OS
Linux hostname 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


openssl
OpenSSL 1.0.2g  1 Mar 2016



Expected behavior
Content Transfer Encoding 8bit lose non-ASCII symbols
Observed behavior
Emails from many of our clients containing Content-Type: utf-8 and Content-Transfer-Encoding 8bit removes non-ASCII characters. For example, German ß turns into �.
Steps to reproduce
Create a plugin from this code
var plugin;

exports.register = function () {
    plugin = this;
};

exports.hook_rcpt_ok = function (next, connection, params) {
    connection.transaction.parse_body = true;
    return next();
};

exports.hook_data_post = function (next, connection, params) {
    connection.logwarn(connection.transaction.body);
    return next();
};
and send this email
Subject: Test
To: to@example.com
From: from@example.com
Date: Wed, 27 Nov 2018 18:09:23 +0100
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary=------------D0A00162984CC178E2583417
Content-language: en-US

This is a multi-part message in MIME format.
--------------D0A00162984CC178E2583417
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Grüße,

Buß

--------------D0A00162984CC178E2583417
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Grüße,

Buß<br>
  </body>
</html>

--------------D0A00162984CC178E2583417--

via swaks with command
swaks --to to@example.com --from from@example.com -d test.eml
As a result we see the following problem
       bodytext: 'Gr��e,\n\n Bu�\n\n',
       body_text_encoded: 'Grüße,\n\nBuß\n\n',
       body_encoding: 'utf-8',

It is not a problem with console. This will be displayed in DB and other places.
We were trying to find out what the problem was and found

367 to 369 in master

new Buffer(line, 'binary'); will lose all non ascii symbols, when 'binary' is removed everything is ok.

Closing comment (2018-12-01T23:16:37Z): This is tangentially related to #2374
Repository: haraka/Haraka

Issue #2511: Dynamically rewrite mail_from in plugin
Created: 2018-09-28T08:52:28Z
I have been poking around with hook_mail and tried to overwrite the mail_from like this.
exports.hook_mail = function (next, connection, params) {
  connection.transaction.mail_from = new Address('<new@domain.com>');
  next()
}

However the emails I receive are still sent by the old address.

Duplicate issue #2880: rewriting mail_from in a plugin , causes issue in smtp_forward plugin
Created: 2020-12-18T00:25:36Z
i am using haraka now as a MSA the server that sends the email has port25 installed on it
i am using smtp_forward plugin to do that but i having hard time figuring out how to change mail from always takes the original domain

Closing comment (2020-12-18T00:37:01Z): duplicate of #2511
Repository: harvester/harvester

Issue #1244: [BUG] Node driver and cloud provider enhancement of RKE2 cluster with external Harvester cluster
Created: 2021-09-17T12:48:11Z
To Reproduce
Steps to reproduce the behavior:

Create a Harvester cloud credential choosing "External Harvester" and providing valid Kubeconfig
Navigate to the form to create Harvester RKE2 cluster
Pick the credential created above
Fields are not populated with available options
Harvester cloud provider is not working as expected as described on rancher/rancher#34969

Expected behavior

Fields are populated with available options from Harvester (namespaces, networks, etc)
Cloud provider integration should also works with external Harvester cluster

** Actual behavior**
Fields are not populated with available options

Duplicate issue #1297: [BUG] external harvester clusters don't populate entries in RKE1/RKE2 node-driver
Created: 2021-09-27T22:35:01Z
Describe the bug

If you create cloud credentials for Harvester with an external Harvester (Using the KUBECONFIG), then the dropdowns don't populate for the
To Reproduce
Steps to reproduce the behavior:

Create cloud credentials using the KUBECONFIG for a harvester cluster
Verify that the KUBECONFIG should work
Create a new harvester cluster using those credentials
Check in the creation screen for dropdowns next to things like image, namespace, network etc

Expected behavior

You should have the dropdowns. If you import the harvester cluster into virtualization management and use those cloud credentials it will populate the dropdowns
Support bundle

Environment:

Harvester ISO version: master-b7b757e9-head
Rancher version: v2.6-head
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): DL160

Additional context
This is an issue because you would have to know the resolution for the namespace and the name of the backing image to get this working without the dropdowns. I also validated that the KUBECONFIG worked with kubectl from my Rancher box.
![Greenshot 2021-09-27 15 26 40](https://user-images.githubusercontent.com/8378795

2/134994238-984b56d0-82ac-421b-86dc-0039e7c36901.png)

Closing comment (2021-09-28T07:30:50Z): close as duplicate of #1244
Repository: harvester/harvester

Issue #1400: [BUG] Add  insufficient disk scheduling message
Created: 2021-10-09T03:37:37Z
Describe the bug
we need to make an enhancement from the back-end side to report the volume info correct via pod instead leave it for the UI to grasp the events info and identify it manually, this should be a general k8s enhancement issue.
VM view:

pod view:

events:

To Reproduce
Steps to reproduce the behavior:

create VM with insufficient disk size e.g 100000Gi

Duplicate issue #777: [BUG] Harvester VM stuck at starting
Created: 2021-04-27T01:02:07Z
Describe the bug
Harvester reaches a limit while creating VM's and does not give any error. Just goes in perpetual loop until an active machine is stopped.
To Reproduce
Steps to reproduce the behavior:

Created 10 vm's
Shows last VM Worker 1 stuck in starting status.

The CPU and memory utilization is low


Shows disk for Worker 1 successfully created even though machine does not start

Stopped Worker 2.

This kicked off Worker 1 creation which had been stuck for 8 hrs.

Tried to restart Worker 2 which has now been stuck as starting for hours

Summary of Infrastructure
Host 1


Host 2


Host 3


Summary of Harvester usage



 
CPU
Memory




intel-nuc
4
32


dell-black
8x2
32


lrn-ml
8x2
32


Physical
20
94


 
 
 


Pihole
2
4


Nginx
4
16


Unimatrix
4
8


Trimatrix 1
4
8


Trimatrix 2
4
8


Trimatrix 3
4
8


Worker 1
4
8


Worker 2
4
8


Worker 3
4
8


Worker 4
4
8


Total
38
84


 
 
 


Active oversubscribe
1.7
0.8


Total oversubscribe
1.9
0.9



[update] - changing all 4 worker VM's to 2 CPU and 4 gig RAM mitigates the issue and starts all VM's

Expected behavior
Harvester should either let the user know why a process is stuck.
If there is a setting for over subscribe that is limiting it will be nice to be notified.
It will be nice to have a quick way to get log file.
Log
Environment:

Harvester ISO version:
Installation Mode: ISO
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 3 bare metal nodes.

Additional context
Add any other context about the problem here.

Closing comment (2021-10-12T03:42:01Z): duplicate of #1400
Repository: harvester/harvester

Issue #594: [BUG] Constantly switching the physical NIC of the node will cause an error to set the physical NIC of the node
Created: 2021-03-26T05:30:12Z
Describe the bug
Occasional, with a higher chance of occurrence
To Reproduce
Steps to reproduce the behavior:

Enable vlan setting, default physical NIC fill in eth0
Go to the network settings of the host node
Set eth1 as the physical NIC
Reset eth0 as the physical NIC
Repeat steps 3 and 4




Environment:

Harvester ISO version: master-c5a265d5-head
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Duplicate issue #309: Saving the network-setting failed
Created: 2020-12-08T08:28:29Z
Steps to reproduce:

On the settings page, edit the network-setting, remove the Physical NIC, then save
Edit it again, fill in the Physical NIC again, then save

Result:
Save failed, along with an error message
Operation cannot be fulfilled on settings.harvester.cattle.io "network-setting": the object has been modified; please apply your changes to the latest version and try again

Closing comment (2021-04-02T08:16:09Z): duplicate of #594
Repository: harvester/harvester

Issue #4905: [ENHANCEMENT] Harvester should display and honor the "virtual size" of uploaded qcow2 images
Created: 2023-12-22T10:50:15Z
Is your enhancement related to a problem? Please describe.
In case we upload the SLE Micro 5.5 image (SLE-Micro.x86_64-5.5.0-Default-qcow-GM.qcow2) and create a new VM based on this image with default settings - the VM crashes during bootup.
Reason for this is that the default OS disk size in Harvester is 10 GB but the OS in this case requires 13 GB at least.
Because Harvester in this case "shrinks" below the minimum required - it causes the OS not to work.
 qemu-img info SLE-Micro.x86_64-5.5.0-Default-qcow-GM.qcow2
image: SLE-Micro.x86_64-5.5.0-Default-qcow-GM.qcow2
file format: qcow2
virtual size: 20 GiB (21474836480 bytes)
disk size: 955 MiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false


Describe the solution you'd like
Within a qcow2 image we can see the "virtual size" of an image - this should be taken as default for the OS image size at least. In case the admin selects something smaller - a warning should show up that there is a risk for problems if the OS disk is created smaller.
Describe alternatives you've considered
Manual adjustment of OS disk size during VM creation - this works but is not very user-friendly as Harvester does not give any idication of "more space required for the OS".
Additional context
Also the image overview in Harvester should show the "virtual size" in additon to the current "disk size" to help administrators.

Duplicate issue #6560: [ENHANCEMENT] Show QCOW virtual size in the UI 
Created: 2024-09-13T11:53:02Z
Is your enhancement related to a problem? Please describe.
When creating a VM from a QCOW file, you can choose the root file system's size. If you choose less than the virtual size of the QCOW image you will be stuck in an initramfs rescue shell like this:

Describe the solution you'd like
It would be nice if the UI could show the virtual size of the QCOW image.
Additional context
There is a note in the documentation which is great, but it would be nice if the UI could warn about this kind of situation.

Closing comment (2024-09-13T15:52:38Z): Thank you for reporting this issue, @dfaltum. It appears to be a duplicate of #4905, which has already been resolved in the v1.4 branch.