primordic/IssueDupesLite huggingface dataset:
Repository: ericgio/react-bootstrap-typeahead

Issue #198: Passing new value(s) to `selected` doesn't correctly filter the menu
Created: 2017-06-13T13:02:01Z
Version
1.4.0
Steps to reproduce

have two autocomplete entries linked with each other such that selecting an option in one updates the other to match. For example adding/selecting name+email pairs.
select value from one entry
click open both of the dropdowns
select a different value from second entry
click open both of the dropdowns

Expected Behavior
Both dropdowns / entries show similar options, shouldn't matter whether the value was selected through clicking on the entry itself or updated programmatically.
Actual Behavior
After selecting one on the first entry (step 1&2):

After selecting two from the second entry (3&4):

Code
<Typeahead
    onInputChange={(selected) => this.setState({ selected })}
    options={['one', 'two', 'three']}
    selected={[this.state.selected]}
/>
<Typeahead
    onInputChange={(selected) => this.setState({ selected })}
    options={['one', 'two', 'three']}
    selected={[this.state.selected]}
/>

Duplicate issue #212: Component doesn't update options when using 'selected' prop
Created: 2017-07-23T11:21:09Z
Version
1.4.2
Steps to reproduce
<Typeahead className="typeahead" ref={i === 0 ? 'typeahead' : ('typeahead' + i)} onChange={this.onChange.bind(null, i)} options={values.options || []} selected={values.selected || []} placeholder={add values} multiple={true} disabled={!isAttributeSelected} />
Expected Behavior
I implemented a next button feature: when clicking on the button - I update 'selected' prop to contain the next attribute in 'options' array. After selected is updated - the form shows the actual selected attribute (that's happening and it is ok) and when clicking again on the form, I want to see the new options (after filtered with the updated selected prop).
Actual Behavior
when clicking on the form, after selected had changed, it still shows the first selected attribute.

Closing comment (2017-07-23T20:32:17Z): Hi, thanks for the report. This is a duplicate of #198 and should be fixed in v2.0.0-alpha.1
Repository: ericgio/react-bootstrap-typeahead

Issue #776: Long option causes menu to open in wrong position
Created: 2023-03-16T13:19:47Z
Version
6.0.2
Steps to reproduce

Go to https://codesandbox.io/s/react-typeahead-bug-with-long-labels-ix81kd
open typeahead menu
notice that menu is shifted to the left edge of the view
start scrolling options and notice that menu position fixes itself

Expected Behavior
Menu is aligned with input when opened.
Actual Behavior
Menu is shifted to the left edge of the view once opened. Menu position gets fixed once you start scrolling.
I can reproduce it with Chrome and FF.

Duplicate issue #857: found an UI glitch
Created: 2024-07-18T19:18:46Z
When the text inside options are too long, the first render will make the dropdown box on wrong position

direct cause:
when first render. the container calculates the "translate" based on width of the option box. In my case its:
transform: translate(-263px, 38px);
however its based on oversized text box (the class ".dropdown-item") which causes the issue.
once you scroll it, then it will be auto adjusted.
my current workaround is to hardcode width of ".dropdown-item"

Closing comment (2024-07-18T21:33:56Z): Thanks @xmluozp! I believe this is a duplicate of #776.
Repository: ericgio/react-bootstrap-typeahead

Issue #628: Tests data-testid is being ignored / not being passed down
Created: 2021-03-22T14:17:32Z
Version 5.1.4
Steps to reproduce
// App.tsx
export default () => (
  <Typeahead
    data-testid='search-bar-input'
    placeholder="Test"
    filterBy={() => true}
    autoFocus={true}
    options={[]}
  />
)

Then import that file into a test using react-testing-library
// App.test.tsx
import { render } from '@testing-library/react';
import App from './App';

it('should be focused', async () => {
  const { getByTestId, container } = render(<App />);
  // console.log(container.innerHTML)
  const input = getByTestId('search-bar-input')
  expect(input).toHaveFocus()
});

Expected Behavior
It should pass the test
Actual Behavior
It cannot find search-bar-input
If we do a console.log(container.innerHTML)the result has no 'search-bar-input' at all

Duplicate issue #629: ID attribute is ignored
Created: 2021-03-23T14:02:35Z
Required attribute id, do not propagate to HTML element - attribute id is ignored. This means is not possible to anchor label with input.
Version
react-bootstrap-typeahead@5.1.4
Steps to reproduce
<AsyncTypeahead id="test" />
Expected Behavior
Rendered input HTML should contain id="test":
<input ... id="test">
Actual Behavior
Input doesn't contain attribute id.
Workaround
<AsyncTypeahead inputProps={{id: "test"}} />

Closing comment (2021-03-23T15:49:20Z): Duplicate of #628 and others
Repository: ericgio/react-bootstrap-typeahead

Issue #217: Deletion of token disables menu expanding by mouse
Created: 2017-08-21T15:51:41Z
Go to the "Basic Example", check on "Multi-Select", so typeahead control is in multiple mode.
Select at item, and then delete it by clicking on a token x.
Selected item is removed, but when you click inside the control to open a menu with options again, nothing happens.
This occurs when mouse clicks on the placeholder ("Choose a state..." in this particular example).
When the control looses focus, or mouse clicks inside the control but outside of the placeholder, everything works fine.

Duplicate issue #232: After deleting a token and emptying the Typeahead form, clicking on the placeholder text does not show the dropdown list
Created: 2017-09-20T14:03:04Z
Version
^1.4.2
Steps to reproduce
Visit the demo: http://ericgio.github.io/react-bootstrap-typeahead/#behaviors

Using the Typeahead box under the Behaviors title, click on "Choose a state..."
Add a state
Delete the state
Click on "Choose a state..." and choose another state
Note: It doesn't work, to re-select a state, you have to either first click outside the Typeahead box, and then click back in -- or by clicking somewhere to the right of the "Choose a state..." hint text.

Expected Behavior

You should be able to delete a value and, by clicking on the placeholder text ("Choose a state..."), be presented the dropdown again.

Actual Behavior

It doesn't work, to re-select a state, you have to either click outside the Typeahead box, and then click back in.  Or click somewhere to the right of the "Choose a state..." hint text.

Closing comment (2017-09-20T16:40:26Z): Dupe of #217
Repository: ericniebler/range-v3

Issue #125: Reconsider constexpr
Created: 2015-03-29T17:42:22Z
E.g.
constexpr auto rng = view::iota(0, 10);
constexpr auto rng2 = view::iota(0) | view::take(10);
constexpr auto rng3 = rng | view::transform(square) | view::remove_if(odd);
should probably work, but that means C++14 will be a requirement. FWIW if the purpose is to prepare a C++17 library, C++14 should be a requirement anyways even tho right now that means clang > 3.6 and gcc 5.0 for the "bug-free" experience.

Duplicate issue #339: Compiled-time views?
Created: 2016-04-27T10:55:59Z
I was wondering whether compiled-time view were/are/will considered for range-v3 library?
Currently, it doesn't work, unless there is a specific syntax/magic to enable it?
  assert(ranges::equal({0, 1}, ranges::view::ints | ranges::view::take(2)));
  static_assert(ranges::equal({0, 1}, ranges::view::ints | ranges::view::take(2)));
Such approach is possible with Boost.Hana, however, Hana purpose is different, so it doesn't have all goodies ranges have.
Motivation...
Simple board (known size) and col / row view could be calculated at compile time (which elements should be taken, not values) and verified during run-time with given values.

Closing comment (2016-05-04T21:55:52Z): Dupe of #125
Repository: ericniebler/range-v3

Issue #1220: Extra call to filter function
Created: 2019-06-19T19:32:21Z
It appears that filtering function is called two times for the last element when converting a filter_view of at least two elements to a vector. Consider the following code:
#include <range/v3/all.hpp>
#include <iostream>
#include <vector>

int main()
{
    std::vector<int> a = {1, 2};
    int i = 0;
    std::vector<int> rng =
      ranges::view::filter(a, [&](int v) {
        std::cout << "i++: " << i++ << ", " << "v: " << v << std::endl;
        return true;
    });
}
Output:
i++: 0, v: 1
i++: 1, v: 2
i++: 2, v: 2

However, if the underlying container contains only a single element, this does not happen:
    ...
    std::vector<int> a = {1};
    ...
Output:
i++: 0, v: 1

Is this the expected behavior?
I have encountered this when migrating HiPipe to v1.0-beta and I was getting a strange double free (not yet sure if it is related, probably not since v0.5.0 does the same thing).
Thank you and have a great day!

Duplicate issue #1254: unexpected call sequence generated when combining view::filter with other views
Created: 2019-08-12T13:17:51Z
I am not sure whether the following is a bug. At least it is unexpected behaviour and quite confusing. Applying view::filter generates an unexpected number of function calls depending on how it is combined with other views. The example uses view::transform with an identity op and filters that always return true to demonstrate the effect.
Code: main.txt
Output: output.txt
Is this a bug?

Closing comment (2019-08-19T07:41:36Z): Maybe related to #1220 .
Repository: ericniebler/range-v3

Issue #819: generate(foo) | take(n) calls foo n+1 times
Created: 2018-04-20T16:13:48Z
I noticed that generate_n(foo, n) calls foo n times while generate(foo) | take(n) calls it n+1 times. Is this by design? If so, what is the rationale?
In some situations I would like to guarantee that foo is called exactly n times, but it seems that I can't always use generate_n. For example, say that I want to do something like this:
for_each(generate(foo), [](auto x) { return yield_if(bar(x), x); }) | take(n);
In this case, foo might be called more than n times depending on how often bar(x) returns false, but I would like to ensure that it is called exactly as many times as it takes to generate n elements and no more. I don't see how I could do it with generate_n. I guess I would need something like for_each_n, which (as far as I can see) only exists as an algorithm and not as a view.

Duplicate issue #807: Unexpected behavior in generate with return by reference
Created: 2018-03-10T10:20:41Z
The following code gives a weird output:
#include <iostream>
#include <range/v3/all.hpp>
#include <vector>

const std::vector<int> p4{0, 1, 2, 3};

auto perms() {
    return ranges::view::generate([t = p4]() -> const std::vector<int> & {
        std::cout << "Returning vector of size " << t.size() << '\n';
        return t;
    });
}

int main(int /*argc*/, char ** /*argv*/) {
    auto ps = perms();
    for (const auto & p : ps | ranges::view::take(2)) std::cout << " -> Obtained vector of size " << p.size() << '\n';
    std::cout << "==========\n";
    for (const auto & p : perms() | ranges::view::take(2)) std::cout << " -> Obtained vector of size " << p.size() << '\n';
}
On both clang (OSX, trunk) and gcc (linux, 7.4) the output I obtain is this:
Returning vector of size 4
 -> Obtained vector of size 4
Returning vector of size 4
 -> Obtained vector of size 4
Returning vector of size 4
==========
Returning vector of size 4
 -> Obtained vector of size 0
Returning vector of size 4
 -> Obtained vector of size 4
Returning vector of size 4

Notice the 0 as the size of the first returned vector for the second version. I would not expect a difference between the two options here, is there something I am missing?
Related question, I would have expected the lambda passed to generate to be called 2 rather than 3 times with that code, are 3 calls the expected behavior?

Closing comment (2018-04-20T20:59:28Z): Wait, the initial bug I reported was about the undefined behavior, not about the number of times the function was called (that was incidental). As far as I am aware the main issue remains, and is not a duplicate of #819 - though it might well be fixed at the same time
Repository: ericniebler/range-v3

Issue #221: Interleaved Range
Created: 2015-10-03T01:15:43Z
In C# you could do something along the lines of this.
IEnumerable<T> Interleave<T> (ICollection<IEnumerable<T>> xs )
{
  if( ( xs == null ) || ( xs.Count == 0 ) ) return;
  using (var nx = new CircularLinkedList<T>() )
  { 
    // Generate a circular linked list of containing the enumerated enumerators.
    using( var en0 = xs.GetEnumerator() )
    {
      while ( en.MoveNext() )
      {
        nx.AddLast( en.Current.GetEnumerator() ) ; // Add this enumerator to circular linked list.
      };

    } // Dispose of the enumerator, used to get the enumerators.

    while( nx.Any() )           // Are there a nodes to process?
    {
      var en = nx.Head;
      if( en.Value.MoveNext() ) // is there a next value?
      {
        yield en.Value.Current; // yield the current value, of the current enumerator ( en )
        nx.RotateLeft();        // eg Move Head to Head.Next
      }
      else
      {
        en.Value.Dipose();     // dispose of the enumerator (Note T needs to be constrained T:IDisposable )
        en.Remove();           // remove this node
      }
    }
  } // dispose of the circular linked list.
}

Duplicate issue #425: introduce variant_view
Created: 2016-07-05T11:20:29Z
It would be nice to have a variant_view, like any_view but limited to a closed set of ranges.
I think this could be useful for flattening trees, possibly not as bad as any_view.

Closing comment (2016-07-07T12:39:26Z): I think this is a duplicate of #221 .
Repository: errata-ai/vale

Issue #414: Incorrect error placing in AsciiDoc when comments with the same error are present.
Created: 2022-03-03T08:05:37Z
Vale version: 2.15.2
Vale correctly skips errors in comments.
But, when the same error appears in a comment, and then in the content after the comment, then Vale incorrectly reports the error in the comment instead of the error in the content.
The following GIF explains the issue better than words:

Duplicate issue #420: Regex negative lookbehind misbehaviour
Created: 2022-03-26T11:08:05Z
Vale version: latest.
Rule
extends: existence
message: "Change"
level: warning
tokens:
  - '(?<!automatic\s+)entr[a-z]*'

Text
This is a automatic entry example file which
just has to trigger on entry word when there's
no 'automatic' before it.

Vale output
{
  "testfile.adoc": [
    {
      "Action": {
        "Name": "",
        "Params": null
      },
      "Check": "testsuite.testWord",
      "Description": "",
      "Line": 1,
      "Link": "",
      "Message": "Change this",
      "Severity": "warning",
      "Span": [
        21,
        25
      ],
      "Match": "entry"
    }
  ]
}

Expected behaviour
It should mark entry word in line 2, because it is not preceded with automatic , but it marks the entry in the first line and never goes further.
Maybe I'm doing something wrong here?

Closing comment (2022-03-30T02:14:29Z): Thanks for the report.
This is actually similar to #414 and it should be fixed in the next release.
Repository: errata-ai/vale

Issue #271: Quad backticks in markdown shifts the result numbers
Created: 2020-11-16T06:52:13Z
Very minor issue, but if you are using quad backticks in a markdown file (so that you can have triple backticks render in a code block), it shifts the results off by one character (sometimes one word) for each quad backtick pair.
So, for example, with a rule looking for the word "easy", each quad backtick shifts the results left (it's the same in CLI):

From:
This is how to write a CI YAML code block:

````markdown
```yaml
job:
  script:
    - echo "Wow"
```
````

Another easy example:

````markdown
```yaml
job:
  script:
    - echo "Wow"
```
````

Was that easy?

It's written that way, so that the triple backticks render properly, for example:
This is how to write a CI YAML code block:
```yaml
job:
  script:
    - echo "Wow"
```
Another easy example:
```yaml
job:
  script:
    - echo "Wow"
```
Was that easy?
cc @jdkato

Duplicate issue #278: Square brackets in URLs cause vale to lint within the URL (markdown)
Created: 2020-12-02T02:45:38Z
@jdkato A minor bug we just ran into. If the URL has square brackets (either [ or ] seem to trigger the bug), Vale will lint within the "code" when it shouldn't:

Closing comment (2020-12-07T01:25:00Z): @jdkato Yes, and I also have some more details. On Friday a co-worker was able to clear these false positives by excluding all "quad backtick" codeblocks from linting: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/49154/diffs#5bce789523695fa2be00cc10575b9cf889c61fa4_1929_1942
I'm not sure if this is related to #271 or not, though.
I dug into that file, and deleted as much as I could to see what was the culprit. I got it down to the following, which still causes false positives with multiple rules (both scope:raw and regular):
Currently a blacklist [link](https://gitlab.com/name[]).

````markdown
```ruby
external_url "https://gitlab.example.com"
```

```yaml
gitlab:
  host: "gitlab.example.com"
```
````


It turns out the false positive I'm highlighting in the screenshot above is actually from the codeblock, but the square brackets are causing it to be reported in the URL (I think?). If I delete the square brackets, the warning moves down to the codeblock:

Aha, if you delete the nested triple backtick codeblocks, all false positives disappear:
Currently a blacklist [link](https://gitlab.com/name[]).

````markdown
external_url "https://gitlab.example.com"

gitlab:
  host: "gitlab.example.com"
````


If you delete the quad backtick code blocks, they disappear too:
Currently a blacklist [link](https://gitlab.com/name).

```ruby
external_url "https://gitlab.example.com"
```

```yaml
gitlab:
  host: "gitlab.example.com"
```


Finally, if you put another layer of single backticks, the text seems to be ignored again:
Currently a blacklist [link](https://gitlab.com/name).

````markdown
```ruby
external_url "https://gitlab.example.com"
```
````

````markdown
```ruby
`external_url "https://gitlab.example.com"`
```
````
Repository: errata-ai/vale

Issue #346: Is it possible to add words with dashes to the whitelist?
Created: 2021-04-30T02:46:15Z
Is it possible to add words with dashes to the accept.txt?
I added "matter-of-factly", but still get a spellcheck error:
# echo "matter-of-factly" | ./vale

 stdin.txt
 1:11  error  Did you really mean 'factly'?  Vale.Spelling

✖ 1 error, 0 warnings and 0 suggestions in stdin.

Thanks!

Duplicate issue #345: Compound words (phrases) in spell-check
Created: 2021-04-17T16:10:39Z
It  appears (confirmed in #200) phrases in vocab.txt don't work for spelling checks. This makes compound words and names difficult. For I only want vu to flag as a misspelling if it's not part of déjà vu, I only want La to flag as a misspelling if it's not part of La Scala, etc..
I assume (confirmed in #200) this is due to the spell-check parsing word-by-word and matching against the vocab lines for exclusions, so it would only see vu and not déjà vu, etc.
Based on your response to #200 this is by design so I'll abort trying to add it.

Closing comment (2021-07-14T22:04:16Z): Related to #346.
Repository: errata-ai/vale

Issue #414: Incorrect error placing in AsciiDoc when comments with the same error are present.
Created: 2022-03-03T08:05:37Z
Vale version: 2.15.2
Vale correctly skips errors in comments.
But, when the same error appears in a comment, and then in the content after the comment, then Vale incorrectly reports the error in the comment instead of the error in the content.
The following GIF explains the issue better than words:

Duplicate issue #785: Use tree-sitter libraries for parsing
Created: 2024-03-05T11:07:41Z
Check for existing issues

 Completed

Describe the feature
Using tree-sitter parsers will allow scoping without losing line numbering (obviously, if you want to edit, you need original line numbers, not after processing). Markdown flavours and reStructured text are available.
Sadly, asciidoc tree-sitter parser is still not available though.

Closing comment (2024-03-05T19:39:00Z): This is a bug related to #414 and multi-byte (non-English) characters. It should be fixed in the next release.
Repository: errata-ai/vale

Issue #136: Does consistency style support regex
Created: 2019-07-08T13:34:13Z
I am attempting to create a style that searches for inconsistent use of quote marks, i.e. mixing smart and non-smart in one document etc. Before I get to lost in regex, does the style (https://errata-ai.github.io/vale/styles/#consistency) even support regex pairs in the declaration?

Duplicate issue #206: Apostrophe in  substitution key not having effect
Created: 2020-05-22T17:08:24Z
Perhaps I'm doing something wrong here, I'd like to simply check for contractions and Vale doesn't seem to be picking it up. Using Antora to generate adocs to HTML via it's built-in generator. Vale is working on outputted HTML.

Run as docker
Vale version 2.2.0

extends: substitution
message: Use '%s' instead of '%s'
level: error
ignorecase: true
nonword: true
swap:
  aren't: are not

# This goes in a file named either `.vale.ini` or `_vale.ini`.

StylesPath = build/vale/styles
MinAlertLevel = warning

# Only HTML files; change to whatever you're using.
[*.{html}]

# List of styles to load.
# BasedOnStyles = proselint, write-good, Joblint, Default
BasedOnStyles = Default

Generated HTML seems to be the culprit, how would I solve this?
<div class="paragraph">
<p>This sentence has aren&#8217;t in it.</p>
</div>

Closing comment (2020-06-04T15:25:32Z): You're right -- the problem here is the Asciidoctor converts the apostrophe into a "smart" character under the hood, which means your rule (which uses a regular character) won't match. If you use a smart character in your rule, then Vale won't be able to find the word in the source document because it was written with a regular character.
The only way for this to work at the moment is to use a smart character in the document and the rule.
I'm not sure exactly how Vale should handle this (it'd nice if we could disable the behavior, but that doesn't seem to be possible?)
Also related to #136, #148, #226.
Repository: errata-ai/vale

Issue #870: vale sync hits  dial tcp 185.199.108.133:443: i/o timeout
Created: 2024-07-10T22:10:40Z
Check for existing issues

 Completed

Environment

OS: Windows 10
Installation: direct download
Vale 3.6.0

Describe the bug / provide steps to reproduce it
When attempting to perform a vale sync with a custom package defined, vale still tries to load the https://raw.githubusercontent.com/errata-ai/styles/master/library.json file, but for some reason hits a timeout.
$ ./vale.exe sync
Syncing mine [1/1] ███████████████████████████████████████████████████ 100% | 0s
Get "https://raw.githubusercontent.com/errata-ai/styles/master/library.json": dial tcp 185.199.108.133:443: i/o timeout
Doing a reverse lookup on that IP address shows it's a CDN for GitHub
cdn-185-199-108-133.github.com
Packages = http://mydomain.com/vale/mine.zip

If the value of Packages contains only custom URLs, it shouldn't try to get that file.

Duplicate issue #932: Vale sync fails when githubusercontent.com is not available
Created: 2024-12-12T00:51:42Z
Check for existing issues

 Completed

Environment

OS: Linux
Install method: Direct download
Version: 3.9.1

Describe the bug / provide steps to reproduce it
I am working in an environment that does not have access to the open web. We have created our own Vale package that is hosted on a local GitLab instance; however, when I try to install it using vale sync I get this error:
Get "https://raw.githubusercontent.com/errata-ai/styles/master/library.json": dial tcp: lookup raw.githubusercontent.com on <IP-address>: no such host
Looking at the source code it seems like this is probably an error when it looks at the Vale package hub. Since I do not need access to the hub, it would be nice if the sync command could still work for my locally hosted package.

Closing comment (2024-12-13T08:52:28Z): This will be fixed in the next release.
(Related to #870.)
Repository: errata-ai/vale

Issue #343: publish latest released docker image in hub.docker
Created: 2021-04-06T12:37:14Z
Hello,
It looks like the latest tag doesn't have the corresponding version tag in https://hub.docker.com/r/jdkato/vale/tags?page=1&ordering=last_updated
Would it be possible to publish the latest released with the tags named v2.10.1 ? the last named version tag is v2.9.1.

Duplicate issue #342: Publish latest versions in the dockerhub
Created: 2021-04-06T12:36:41Z
The latest tag in the https://hub.docker.com/r/jdkato/vale/tags is v2.9.1. Two latest versions are missing in the dockerhub.

Closing comment (2021-04-06T12:38:39Z): duplicates #343
Repository: errata-ai/vale

Issue #117: Creating a style that checks YAML tags in a markdown file.
Created: 2019-04-02T13:57:33Z
Hi there!
I am quite new at using Vale, so this may be a stupid question. My issue is that I have several markdown files that contain YAML at the top, something like this:
---
yamltag: true
---
# Heading here

I noticed though when I wrote a new style it would ignore the data wrapped inside '---'.
I found this issue: #24 and it sounds like it should be able to parse the lines?
My style .yml file looks like this:
extends: existence
message: "No yamltag has been set"
level: error
tokens:
  - yamltag

Duplicate issue #504: Enable checking for specific frontmatter
Created: 2022-10-28T16:01:39Z
We have a Hugo based documentation site with a lot of 'lists' that are defined mostly in the front matter. For example, a glossary entry might look like:
---
title: RACI
acronym: Responsible, Accountable, Consulted, Informed
description: The RACI model describes participation by various roles in completing tasks or deliverables for a project or business process
more_info: https://en.wikipedia.org/wiki/Responsibility_assignment_matrix
---
Note that all of the content is in the front matter and the markdown is actually blank. It is rendered by Hugo templates. This gives us a lot of flexibility, for example we can read these files and export other formats.
Even if we weren't doing that, having the ability to check titles, which appear to the user in menu and bread-crumb lists, would be of value.
We have used Vale successfully in other contexts and like what it can do for us. Unfortunately Vale currently has a hardcoded regex to ignore the front matter. Worse, the code that implements the BlockIgnores configuration option is in the same function with the hardcoded removal of the front-matter. If we turn off the 'code' scope, BlockIgnores no longer work and we can no longer customize the linting.
Vale 2.20.2 installed by downloading package from GitHub into a GitHub codespace.

Closing comment (2022-10-28T16:41:52Z): Yes, this is intended behavior.
Front matter isn't Markdown and so features (such as BlockIgnores) that involve processing/understanding Markdown syntax won't work.
If you have a rule that you want to apply to front matter generally, you can use scope: raw. A better approach, though, might be to use a script to parse the front matter and only pass the desired keys (such as title) to Vale.
(Related to #117.)
Repository: errata-ai/vale

Issue #81: Configuration not loaded on Ubuntu 18.04
Created: 2018-09-22T10:28:14Z
Hi, this tool looks great!
Just trying to get it to run, but not getting anywhere: no matter how I configure vale, I always get the same output:
✔ 0 errors, 0 warnings and 0 suggestions in 1 file.

Installed on Ubuntu 18.04 via snap as per the getting started instructions.
One should be able to use the styles 'vale', 'proselint', and 'write-good' without specifying a StylePath nor downloading/installing anything else, correct?
I've simplified the .vale file as much as possible, and put it inside the same directory as my markdown file:
# Global settings (applied to every syntax)
[*]

# List of styles to load
BasedOnStyles = vale

the output of running vale myfile.md is always:
✔ 0 errors, 0 warnings and 0 suggestions in 1 file.

The file contains a lot of text content, and I even introduced grammar errors, spelling errors, etc. I've tried with various markdown files, tried using proselint, and so on... whatever I do, I always get the same output.
Is there any way to debug what is going on? It feels like whatever I put in the .vale file is always ignored...
Thanks.

Duplicate issue #134: Doesn't seem to work on Ubuntu
Created: 2019-07-03T16:55:37Z
OS: Ubuntu 18.04
Install method: snap
Version: "master"
 vadi   development  ~  Programs  Mudlet  mudlet  vale test.md
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
✔ 0 errors, 0 warnings and 0 suggestions in 1 file.
 vadi   development  ~  Programs  Mudlet  mudlet  cat test.md 
## Getting Started

Rule 1: Don't start sentences with "so":

> So, this is an example sentence.

Rule 2: Don't start a sentence with "there is" or "there are":

> There are many ways to start a sentence.
 vadi   development  ~  Programs  Mudlet  mudlet  cat .vale.ini 
# This goes in a file named either `.vale.ini` or `_vale.ini`.
#
# Alerts are assigned a level of suggestion, warning, or error.
MinAlertLevel = warning

# We only want to lint Markdown files.
[*.md]
# Vale comes with three built-in styles: write-good, proselint, and Joblint.
#
# Here, we specify that we want to enable all rules in the "write-good" style.
BasedOnStyles = write-good
 vadi   development  ~  Programs  Mudlet  mudlet  vale --version
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
vale version master
 vadi   development  ~  Programs  Mudlet  mudlet  

Closing comment (2019-07-03T17:38:52Z): I don't maintain the snap anymore, but this is probably related to #81.
Repository: eth-brownie/brownie

Issue #956: borwnie recompiles every time multiversion project
Created: 2021-02-12T10:00:46Z
Environment information

brownie Version: v1.13.0
ganache-cli Version: v6.12.2
solc Version: multiple
Python Version: 3.*
OS: linux

What was wrong?
running brownie console re-compiles every time the whole project.
How can it be fixed?
Probably use multiple build cache folders for different versions

Duplicate issue #1194: Brownie compiles contracts even when not need - Option to disable
Created: 2021-08-11T11:56:56Z
Environment information

brownie Version: 1.14.6
ganache-cli Version: 6.12.2
solc Version: 0.8.6
Python Version: 3.9.0
OS: linux (inside docker image)

What was wrong?
When I run any pytest command (even pytest --help), it always compiles the contracts, even when not needed and even when the files didn't changed
pytest --help
Compiling contracts...
  Solc version: 0.8.6
  Optimizer: Enabled  Runs: 200
  EVM Version: Istanbul
Generating build data...
 - BaseAssetManager
 - DataTypes
...

How can it be fixed?
At least it should detect nothing changed and don't run the compilation. But also should be possible to tell with some environment variable or config setting to completely avoid compilation tasks. This can be useful to speed up when testing pure python code.

Closing comment (2021-08-14T20:18:33Z): Might be a duplicate of #956.
Repository: eth-brownie/brownie

Issue #398: Add params to brownie run
Created: 2020-04-08T20:31:05Z
Overview
Now we can put args  and kwargs into brownie run, when we are using brownie console mode (here in code), but we can't do it through calling of brownie run from shell. Possible it's very useful feature in CI/CD, scripts etc

I want to deploy my token in CI/CD with dynamic params (for example address of other contracts, which have deployed earlier in CI/CD). Now I deploy their manually through brownie console.
I want to run my brownie scripts without interactive mode in docker files.

Specification
For example we can add args and kwargs so:
brownie run <filename> [<function>] [<args1>] … [<argsN>] [options] [kwargs], where
* [<args1>] … [<argsN>] - is tuple of args
*[kwars] - is kwargs, but without reserves keys like --network
Dependencies
I could not search.
If we can do these changes, than I can implement it at the next week.

Duplicate issue #968: Scripts should allow args from cmd line
Created: 2021-02-18T15:31:17Z
Overview
Brownie should support args for running scripts.

What you are trying to do
I am running scripts and I would like to pass arguments to the functions.

Specification
@iamdefinitelyahuman happy to use whatever you prefer.
The most naive implementation I can think of is:
--args arg1,arg2,arg3

Dependencies
None

Closing comment (2021-02-18T23:52:29Z): Duplicate of #398, some work toward this has been done in #816 and #930
Repository: eth-brownie/brownie

Issue #619: Challenges working with proxy contracts
Created: 2020-06-07T15:29:10Z
Overview
When dealing with proxy contracts, it's sometimes required to have two different ProjectContract objects pointing at the same address.  Currently this fails because "contract already exists".
Specification
TBD - there must be an elegant solution to this though.

Duplicate issue #867: deploy proxy
Created: 2020-11-25T04:01:50Z
Overview
would be useful to have a function which can deploy proxy as in the OZ cli.
myContract.deployProxy()
Specification
port this code?
https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/master/packages/plugin-truffle/src/deploy-proxy.ts
Dependencies

Closing comment (2020-11-25T12:19:07Z): Related to #619
Repository: eth-brownie/brownie

Issue #480: Add support for `console.log`
Created: 2020-05-03T09:54:10Z
Overview
Brownie should support console.log as implemented by Buidler
Specification

Access to the functionality comes from an import: import "@nomiclabs/buidler/console.sol";
The imported contract is available at: nomiclabs/buidler/packages/buidler-core/console.sol
console is a library. log sends a call to an empty account with a particular signature depending on the param type(s) given. It will be possible to extract these from the debug_traceTransaction output.

Considerations

How to handle importing console.sol without reliance on NPM? The solution will likely require expanding the brownie package manager.
The implementation must produce consistent results with buidler. Should examine their test cases around this and write similar ones for Brownie.

Duplicate issue #792: Create a way to print console.log in smart contracts
Created: 2020-10-05T07:46:57Z
Overview
Smart contracts are hard to debug. This feature would allow printing console.log messages. Currently the only way to debug transactions is thru tx.call_trace() and tx.subcalls
Specification
inlucde EVM that does allow printing console.log.
https://buidler.dev/buidler-evm/
pragma solidity >=0.4.25 <0.7.0;

 import "./ConvertLib.sol";
+import "@nomiclabs/buidler/console.sol";

...

    function sendCoin(address receiver, uint amount) public returns(bool sufficient) {
+       console.log(msg.sender, receiver, amount);
        if (balances[msg.sender] < amount) return false;

Dependencies
@nomiclabs

Closing comment (2020-10-06T18:35:59Z): Closing as a duplicate of #480
I'm definitely into this idea, it's just a big job and haven't found the bandwidth for it yet.
Repository: eth-brownie/brownie

Issue #1603: ValueError: Multiple networks using ID 'fork-mainnet'
Created: 2022-08-30T03:00:12Z
I installed brownie with all possible ways : using repository | npx install | pip install
Always having this error :

Duplicate issue #1614: Error : Multiple networks using ID 'fork-mainnet'
Created: 2022-09-23T14:49:59Z
Environment information
I installed brownie with : pip install eth-brownie

Python 3.10.6
OS: 12.0.1

What was wrong?

I ran brownie init  / brownie / brownie networks list

Error :

Closing comment (2022-11-14T11:29:41Z): duplicate of #1603
Repository: eth-brownie/brownie

Issue #1076: verfication failed
Created: 2021-05-04T02:43:21Z
Environment information

brownie Version: 1.14.6
solc Version: 0.8.4
Python Version: 3.9.4
OS: linux

What was wrong?
Given a contract
// contracts/hodl.sol
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

import "OpenZeppelin/openzeppelin-contracts@4.0.0/contracts/utils/Context.sol";
import "OpenZeppelin/openzeppelin-contracts@4.0.0/contracts/token/ERC777/ERC777.sol";

contract TestToken is ERC777 {
    constructor() ERC777("Test Token", "TEST", new address[](0)) {
        _mint(msg.sender, 1e25, "", "");
    }
}

brownie compile runs perfect. But in brownie console, verification always fails using either deploy() or publish_source().
How can it be fixed?
I don't know how to fix this.

Duplicate issue #1122: Publish code - Unable to verify
Created: 2021-06-23T21:55:45Z
Environment information

brownie Version: v1.14.6
solc Version: 0.8.6
Python Version: 3.8.8
OS: linux
Network: kovan

What was wrong?
>>> tc = TestCurrency.at("0x9b4926E597CcC1867BbE7BB3b43cE66268ffD768")
>>> TestCurrency.publish_source(tc)
Verification submitted successfully. Waiting for result...
Verification pending...
Verification complete. Result: Fail - Unable to verify
False
TestCurrency.sol:
//SPDX-License-Identifier: Unlicense
pragma solidity ^0.8.0;

import "@openzeppelin/contracts/token/ERC20/ERC20.sol";

contract TestCurrency is ERC20 {
  address private _owner;

  constructor(string memory name_, string memory symbol_, uint256 initialSupply) ERC20(name_, symbol_) {
    _owner = msg.sender;
    _mint(msg.sender, initialSupply);
  }

  function mint(address recipient, uint amount) public {
    // require(msg.sender == _owner, "Only owner can mint");
    return _mint(recipient, amount);
  }

  function burn(address recipient, uint amount) public {
    // require(msg.sender == _owner, "Only owner can burn");
    return _burn(recipient, amount);
  }

}
Also I tried verifying manually the .json in build folder and doesn't works either.

Closing comment (2021-06-23T23:13:36Z): Duplicate of #1076
Repository: eth-brownie/brownie

Issue #52: Simplify retrieving data from events
Created: 2019-03-28T04:12:44Z
Instead of:
id_ = tx.events[2]['data'][0]['value']
it would be much simpler to type:
id_ = tx.events['NewAuthority']['id']
Need to give this some thought. Multiple firings of the same event in the same tx will complicate it, but there must be a way..

Duplicate issue #86: How to obtain event via an mapping key?
Created: 2019-04-30T14:08:51Z
Related to TransactionReceipt.events, which returns list instead of a dictionary.
I was not able to obtain the event with its mapping key, is it possible in different approach?
The way I am able to obtain the event value only by the index of the list =>
tx.events[0]['data'][<index>]['value']

for i in range(0, len(tx.events[0]['data'])):
      print(tx.events[0]['data'][i])

output:
{'name': 'clusterAddress', 'type': 'address', 'value': '0xe0cb57839ad45c3497fafb9b148ff9b11a21f33c', 'decoded': True}
{'name': 'jobKey', 'type': 'string', 'value': 'QmWmyoMoctfbAaiEs2G46gpeUmhqFRDW6KWo64y5r581Vd', 'decoded': True}
{'name': 'index', 'type': 'uint256', 'value': 0, 'decoded': True}

Closing comment (2019-04-30T16:47:43Z): Related to #52 - I thought about this but I haven't dealt with it yet.  I will mark it as a priority.  Closing this issue for now as a duplicate.
Repository: eth-brownie/brownie

Issue #520: Add `--interactive` flag to `brownie run`
Created: 2020-05-14T12:25:16Z
Overview
In the same way that --interactive may be used to enter a console on a failed test, it should be used to enter a console after executing a script via brownie run.
Specification
Add a flag:
brownie run --interactive
The functionality should be similar to brownie test, where the script's local and global namespace are available as well as all standard console objects.
The namespace is available via inspect.stack()[0].frame. See pytest_exception_interact in brownie/test/managers/runner.py for an example.
Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.

Duplicate issue #538: Support interactive debugging of `brownie run`
Created: 2020-05-22T21:19:19Z
Overview
I'm writing some run scripts and they have some bugs. It would be really handy to be able to do brownie run -I ... just like I can do brownie test -I

Closing comment (2020-05-23T07:03:35Z): Duplicate of #520
Repository: eth-brownie/brownie

Issue #180: Incorrect return type in api-brownie.rst for format_input
Created: 2019-09-10T19:27:08Z
The docs currently state that format_input returns "Returns a list of values formatted for use by ContractTx or ContractCall."
However, it seems it actually returns an instance of brownie.convert.ReturnValue which inherits from tuple.
I have updated the docs in my PR #170 but was hoping to get a second set of eyes on this to make sure I'm not missing something.
For references, here's the output in my terminal.
>>> from brownie.convert import format_input
>>> abi = {'constant': False, 'inputs': [{'name': '_to', 'type': 'address'}, {'name': '_value', 'type': 'uint256'}], 'name': 'transfer', 'outputs': [{'name': '', 'type': 'bool'}], 'payable': False, 'stateMutability': 'nonpayable', 'type': 'function'}
>>> format_input(abi, ["0xB8c77482e45F1F44dE1745F52C74426C631bDD52","1 ether"])
('0xB8c77482e45F1F44dE1745F52C74426C631bDD52', 0)
>>> type(format_input(abi, ["0xB8c77482e45F1F44dE1745F52C74426C631bDD52","1 ether"]))
<class 'brownie.convert.ReturnValue'>

This all also applies to the format_output method.

Duplicate issue #200: Explicitely define public/private API
Created: 2019-09-13T08:12:39Z
The Issue
There are many areas of the Brownie API where the docs mention "this should not be called directly", but that are not explicitly marked as private.
How to Fix
Naming

Any package, module, class or function that is only intended to be called internally MUST be prefixed with a single underscore.
If a module is marked as internal, each method and class within it MUST also be marked to increase readability of from ... style imports.
Class methods MUST be prefixed if they are only called by other methods within the same class, regardless of if the class itself is marked as private.

Documentation

The API documentation MUST include complete information about all packages and methods that are not flagged as internal.
Internal packages and methods SHOULD be included in the documentation, always after the public API, always within a sub-section marked "[package] Internal Methods"

Docstrings and Comments

All public API methods MUST include detailed docstrings.
All internal API methods MUST NOT include docstrings, but MIGHT include comments.

Progress

 brownie.cli - private
 brownie.gui - only the Root class to instantiate the GUI should be public
 brownie.network - a mix of public and private
 brownie.project - mostly private, except the methods accessible from __init__.py
 brownie.test - private

Closing comment (2019-09-13T08:13:53Z): Related to #180, #185
Repository: ethereum-mining/ethminer

Issue #152: --opencl-devices parameter not working
Created: 2017-07-14T02:56:11Z
I've tried calling ethminer.exe --list-devices, and then using those device numbers with the --opencl-devices param to skip my integrated graphics, but it doesn't seem to be working. It still seems to select my integrated graphics card and then it tells me that my graphics card doesn't have enough memory to upload the dag file.

Duplicate issue #959: 0.15.0.dev0 Linux, -X option loops on start with 'No work. Pause for 3 s.', ignores BREAK.
Created: 2018-03-31T14:26:39Z
Linux 4.15, Nvidia 390.47, AMDGPU-PRO 17.50, CUDA 9.1
Updating ethminer-buildinfo:
Project Version:  0.15.0.dev0
System Name:      linux
System Processor: x86_64
Compiler ID:      gnu
Compiler Version: 5.4.0
Build Type:       release
Git Commit Hash:  44848c9
Timestamp:        2018-03-31T10:00:51
Ethminer works well with either -G or -U options, but not with -X
Consider the command line
ethminer --work-timeout 180 --opencl-platform 1 --farm-recheck 2000 -X -P stratum+tcp://${WALLET}.${RIG}@eu1.ethermine.org:4444

With -X

With -G

With -U

At times, simply changing the wallet or pool information, will allow a mixed rig to run without issues.  I hate reporting seeming randomness, but with the latest merged master, the No work. loop seems pretty consistent.  If it should start, after sometime, a GPU will fail out and report 0.  Always AMD GPUs that fail out.  Mining with only AMD or NVIDIA give no issues over time.
Output of ethminer --list-devices

Closing comment (2018-04-28T13:54:14Z): Related to #152
Repository: ethereum-mining/ethminer

Issue #902:  Fatal GPU error: CUDA error in func dev::eth::CUDAMiner::search at line 503
Created: 2018-03-17T18:28:21Z
ethminer-0.14.0.dev4-Windows
windows 10 pro, version 1709, OS build 16299.248
cuda 9.1
nvidia 390.65
rig with 6gpu (4 gtx 1070, 2 gtx 1060)
after 10-15hour on ubiqpool.maxhash.org on screeen is this error:
Fatal GPU error: CUDA error in func dev::eth::CUDAMiner::search at line 503
it does happend on ethminer-0.14.0.dev3-Windows too, but after 3-6 hours.
with ethminer-0.13.0-Windows everithing works just fine.

Duplicate issue #1130: Fatal GPU error: CUDA error in func dev::eth::CUDAMiner::search at line 461 unspecified launch failure Terminating
Created: 2018-05-21T06:37:58Z
Build:
0.15.0 dev 10.
Error:
"Fatal GPU error: CUDA error in func dev::eth::CUDAMiner::search at line 461 unspecified launch failure Terminating."
Description of a problem:
On two farms of a mistake appear with a different frequency. On one thicket (10-15 times a day), on another is more rare (4-5 times a day).
On farms on 4 video cards, and the message at the same time appears on each video card.
After that the mayner finishes the work.
At the Windows 10 updating to the version 1803 the problem began to be shown after 8-10 share (1-2 minutes after start).
Forcedly downgrade windows 10 back to version 1709 was necessary.
Configuration:
CPU: AMD Phenom II X3 - X4.
RAM: 8Gb.
OS: Windows 10 (1709), build 16299.431.
Driver NVIDIA: 391.35
Question:
In what can be a problem? What is occurs in this release in line 461?

Closing comment (2018-05-21T09:28:41Z): Same as
#902
#793
#239
Repository: ethereum-mining/ethminer

Issue #414: low hashrate
Created: 2017-12-02T16:29:16Z
Hi,
I have used ethminer with my gtx 1070 cards, and they work fine.  However I am not using rx 580 cards, and the hashrate is very slow.
With my six rx580 cards, I get over 180mh/s using claymore (174 with the nofee option).  However with ethminer I am only getting 130-135mh/s.  I am sure I have something wrong to be this low.  Both are using the same overclock (using msi afterburner), and the same modded bios.
Here is my start file.
ethminer --farm-recheck 200 -G --opencl-platform 1 -S us1.ethermine.org:4444 -O ee8866a0f1e6fae19cb5ddfbcdfc6ca076c1d73b.rig1
Also I am running windows 10.

Duplicate issue #415: Low hash rate
Created: 2017-12-02T17:04:37Z
Hi,
I opened this earlier and it was closed saying I sould use -U for cuda.  But if you read, I am using rx 580 cards, which are AMD.  etherminer worsk fine with my nvida cards using cuda, but I am having problems getting it to work with AMD cards.
With my six rx580 cards, I get over 180mh/s using claymore (174 with the nofee option). However with ethminer I am only getting 130-135mh/s. I am sure I have something wrong to be this low. Both are using the same overclock (using msi afterburner), and the same modded bios.
Here is my start file.
ethminer --farm-recheck 200 -G --opencl-platform 1 -S us1.ethermine.org:4444 -O ee8866a0f1e6fae19cb5ddfbcdfc6ca076c1d73b.rig1
Also I am running windows 10.

Closing comment (2017-12-02T17:05:54Z): dupe of #414