Collection: A variety of options/non-word syntax-needles for exclusion

Since I have already modded this plugin for a variety of syntaxes I want to be able to exclude, I figured I can just as well make it a list to work down. I unfortunately have no experience with forking and building code. Hence, I am making an issue to collect the various needles & mods, in case anyone wants to take them in themselves, or the author wants to implement them.

* May be heavily modded due to my own need, as I exclusively use themes/plugins which allow the following syntax to be used:
![[Path/To/Image|A title, with any kind of [special characters] you could imagine!|300]]

In this case, the needle would be either built to remove the entire image embed, e.g. something like \!\[\[.*\]\], but probably more robust, or to non-match the title portion and match-and-strip-away the rest. I have not yet decided what I am gonna do.
Functions modded:
function getWordCount(text,settings) {
    const spaceDelimitedChars = /'’A-Za-z\u00AA\u00B5\u00BA\u00C0-\u00D6\u00D8-\u00F6\u00F8-\u02C1\u02C6-\u02D1\u02E0-\u02E4\u02EC\u02EE\u0370-\u0374\u0376\u0377\u037A-\u037D\u037F\u0386\u0388-\u038A\u038C\u038E-\u03A1\u03A3-\u03F5\u03F7-\u0481\u048A-\u052F\u0531-\u0556\u0559\u0561-\u0587\u05D0-\u05EA\u05F0-\u05F2\u0620-\u064A\u066E\u066F\u0671-\u06D3\u06D5\u06E5\u06E6\u06EE\u06EF\u06FA-\u06FC\u06FF\u0710\u0712-\u072F\u074D-\u07A5\u07B1\u07CA-\u07EA\u07F4\u07F5\u07FA\u0800-\u0815\u081A\u0824\u0828\u0840-\u0858\u08A0-\u08B4\u0904-\u0939\u093D\u0950\u0958-\u0961\u0971-\u0980\u0985-\u098C\u098F\u0990\u0993-\u09A8\u09AA-\u09B0\u09B2\u09B6-\u09B9\u09BD\u09CE\u09DC\u09DD\u09DF-\u09E1\u09F0\u09F1\u0A05-\u0A0A\u0A0F\u0A10\u0A13-\u0A28\u0A2A-\u0A30\u0A32\u0A33\u0A35\u0A36\u0A38\u0A39\u0A59-\u0A5C\u0A5E\u0A72-\u0A74\u0A85-\u0A8D\u0A8F-\u0A91\u0A93-\u0AA8\u0AAA-\u0AB0\u0AB2\u0AB3\u0AB5-\u0AB9\u0ABD\u0AD0\u0AE0\u0AE1\u0AF9\u0B05-\u0B0C\u0B0F\u0B10\u0B13-\u0B28\u0B2A-\u0B30\u0B32\u0B33\u0B35-\u0B39\u0B3D\u0B5C\u0B5D\u0B5F-\u0B61\u0B71\u0B83\u0B85-\u0B8A\u0B8E-\u0B90\u0B92-\u0B95\u0B99\u0B9A\u0B9C\u0B9E\u0B9F\u0BA3\u0BA4\u0BA8-\u0BAA\u0BAE-\u0BB9\u0BD0\u0C05-\u0C0C\u0C0E-\u0C10\u0C12-\u0C28\u0C2A-\u0C39\u0C3D\u0C58-\u0C5A\u0C60\u0C61\u0C85-\u0C8C\u0C8E-\u0C90\u0C92-\u0CA8\u0CAA-\u0CB3\u0CB5-\u0CB9\u0CBD\u0CDE\u0CE0\u0CE1\u0CF1\u0CF2\u0D05-\u0D0C\u0D0E-\u0D10\u0D12-\u0D3A\u0D3D\u0D4E\u0D5F-\u0D61\u0D7A-\u0D7F\u0D85-\u0D96\u0D9A-\u0DB1\u0DB3-\u0DBB\u0DBD\u0DC0-\u0DC6\u0E01-\u0E30\u0E32\u0E33\u0E40-\u0E46\u0E81\u0E82\u0E84\u0E87\u0E88\u0E8A\u0E8D\u0E94-\u0E97\u0E99-\u0E9F\u0EA1-\u0EA3\u0EA5\u0EA7\u0EAA\u0EAB\u0EAD-\u0EB0\u0EB2\u0EB3\u0EBD\u0EC0-\u0EC4\u0EC6\u0EDC-\u0EDF\u0F00\u0F40-\u0F47\u0F49-\u0F6C\u0F88-\u0F8C\u1000-\u102A\u103F\u1050-\u1055\u105A-\u105D\u1061\u1065\u1066\u106E-\u1070\u1075-\u1081\u108E\u10A0-\u10C5\u10C7\u10CD\u10D0-\u10FA\u10FC-\u1248\u124A-\u124D\u1250-\u1256\u1258\u125A-\u125D\u1260-\u1288\u128A-\u128D\u1290-\u12B0\u12B2-\u12B5\u12B8-\u12BE\u12C0\u12C2-\u12C5\u12C8-\u12D6\u12D8-\u1310\u1312-\u1315\u1318-\u135A\u1380-\u138F\u13A0-\u13F5\u13F8-\u13FD\u1401-\u166C\u166F-\u167F\u1681-\u169A\u16A0-\u16EA\u16F1-\u16F8\u1700-\u170C\u170E-\u1711\u1720-\u1731\u1740-\u1751\u1760-\u176C\u176E-\u1770\u1780-\u17B3\u17D7\u17DC\u1820-\u1877\u1880-\u18A8\u18AA\u18B0-\u18F5\u1900-\u191E\u1950-\u196D\u1970-\u1974\u1980-\u19AB\u19B0-\u19C9\u1A00-\u1A16\u1A20-\u1A54\u1AA7\u1B05-\u1B33\u1B45-\u1B4B\u1B83-\u1BA0\u1BAE\u1BAF\u1BBA-\u1BE5\u1C00-\u1C23\u1C4D-\u1C4F\u1C5A-\u1C7D\u1CE9-\u1CEC\u1CEE-\u1CF1\u1CF5\u1CF6\u1D00-\u1DBF\u1E00-\u1F15\u1F18-\u1F1D\u1F20-\u1F45\u1F48-\u1F4D\u1F50-\u1F57\u1F59\u1F5B\u1F5D\u1F5F-\u1F7D\u1F80-\u1FB4\u1FB6-\u1FBC\u1FBE\u1FC2-\u1FC4\u1FC6-\u1FCC\u1FD0-\u1FD3\u1FD6-\u1FDB\u1FE0-\u1FEC\u1FF2-\u1FF4\u1FF6-\u1FFC\u2071\u207F\u2090-\u209C\u2102\u2107\u210A-\u2113\u2115\u2119-\u211D\u2124\u2126\u2128\u212A-\u212D\u212F-\u2139\u213C-\u213F\u2145-\u2149\u214E\u2183\u2184\u2C00-\u2C2E\u2C30-\u2C5E\u2C60-\u2CE4\u2CEB-\u2CEE\u2CF2\u2CF3\u2D00-\u2D25\u2D27\u2D2D\u2D30-\u2D67\u2D6F\u2D80-\u2D96\u2DA0-\u2DA6\u2DA8-\u2DAE\u2DB0-\u2DB6\u2DB8-\u2DBE\u2DC0-\u2DC6\u2DC8-\u2DCE\u2DD0-\u2DD6\u2DD8-\u2DDE\u2E2F\u3005\u3006\u3031-\u3035\u303B\u303C\u3105-\u312D\u3131-\u318E\u31A0-\u31BA\u31F0-\u31FF\u3400-\u4DB5\uA000-\uA48C\uA4D0-\uA4FD\uA500-\uA60C\uA610-\uA61F\uA62A\uA62B\uA640-\uA66E\uA67F-\uA69D\uA6A0-\uA6E5\uA717-\uA71F\uA722-\uA788\uA78B-\uA7AD\uA7B0-\uA7B7\uA7F7-\uA801\uA803-\uA805\uA807-\uA80A\uA80C-\uA822\uA840-\uA873\uA882-\uA8B3\uA8F2-\uA8F7\uA8FB\uA8FD\uA90A-\uA925\uA930-\uA946\uA960-\uA97C\uA984-\uA9B2\uA9CF\uA9E0-\uA9E4\uA9E6-\uA9EF\uA9FA-\uA9FE\uAA00-\uAA28\uAA40-\uAA42\uAA44-\uAA4B\uAA60-\uAA76\uAA7A\uAA7E-\uAAAF\uAAB1\uAAB5\uAAB6\uAAB9-\uAABD\uAAC0\uAAC2\uAADB-\uAADD\uAAE0-\uAAEA\uAAF2-\uAAF4\uAB01-\uAB06\uAB09-\uAB0E\uAB11-\uAB16\uAB20-\uAB26\uAB28-\uAB2E\uAB30-\uAB5A\uAB5C-\uAB65\uAB70-\uABE2\uAC00-\uD7A3\uD7B0-\uD7C6\uD7CB-\uD7FB\uF900-\uFA6D\uFA70-\uFAD9\uFB00-\uFB06\uFB13-\uFB17\uFB1D\uFB1F-\uFB28\uFB2A-\uFB36\uFB38-\uFB3C\uFB3E\uFB40\uFB41\uFB43\uFB44\uFB46-\uFBB1\uFBD3-\uFD3D\uFD50-\uFD8F\uFD92-\uFDC7\uFDF0-\uFDFB\uFE70-\uFE74\uFE76-\uFEFC\uFF21-\uFF3A\uFF41-\uFF5A\uFF66-\uFFBE\uFFC2-\uFFC7\uFFCA-\uFFCF\uFFD2-\uFFD7\uFFDA-\uFFDC/
        .source;
    const nonSpaceDelimitedWords = /\u3041-\u3096\u309D-\u309F\u30A1-\u30FA\u30FC-\u30FF\u4E00-\u9FD5/.source;
    const nonSpaceDelimitedWordsOther = /[\u3041-\u3096\u309D-\u309F\u30A1-\u30FA\u30FC-\u30FF\u4E00-\u9FD5]{1}/
        .source;
    const pattern = new RegExp([
        `(?:[0-9]+(?:(?:,|\\.)[0-9]+)*|[\\-${spaceDelimitedChars}])+`,
        nonSpaceDelimitedWords,
        nonSpaceDelimitedWordsOther,
    ].join("|"), "g");
    if (typeof settings==="object") {
        var dontcountWhitespace = settings.dontcountWhitespace
        var dontcountHTMLComments = settings.dontcountHTMLComments
        var dontcountFrontmatter = settings.dontcountFrontmatter
    }
    else {
        var dontcountWhitespace = false
        var dontcountHTMLComments = false
        var dontcountFrontmatter = false
    }

    if (dontcountHTMLComments) {
        if (text.match(/(?=<!--)([\s\S]*?)-->/g)){
            text = text.replace(/(?=<!--)([\s\S]*?)-->/g, '') // ~Gw:  replace HTML comments
        }
    }

    if (dontcountFrontmatter) {
        if (text.match(/^---(.|\n)*?\---/s)){
            text = text.replace(/^---(.|\n)*?\---/s, '') // ~Gw:  replace frontmatter
        }
    }
    return (text.match(pattern) || []).length;
}
function getCharacterCount(text,settings) {
    // ~Gw: modifications to this function and its calls to allow for easy exclusion via regex. - 27.01.2023 - updated on 09.02.2023 for better expandability.
    var textcleaned = ""
    var initiallength = 0
    var cleanedlength = 0
    initiallength = text.length // used for testing comparison purposes only.
    textcleaned = text
    if (typeof settings==="object") {
        var dontcountWhitespace = settings.dontcountWhitespace
        var dontcountHTMLComments = settings.dontcountHTMLComments
        var dontcountFrontmatter = settings.dontcountFrontmatter
    }
    else {
        var dontcountWhitespace = false
        var dontcountHTMLComments = false
        var dontcountFrontmatter = false
    }

    if (dontcountWhitespace) {
        if (textcleaned.match(/\s+/g)){
            textcleaned = textcleaned.replace(/\s+/g, '') // ~Gw:  replace whitespace
        }
    }

    if (dontcountHTMLComments) {
        if (textcleaned.match(/(?=<!--)([\s\S]*?)-->/g)){
            textcleaned = textcleaned.replace(/(?=<!--)([\s\S]*?)-->/g, '') // ~Gw:  replace HTML comments
        }
    }

    if (dontcountFrontmatter) {
        if (textcleaned.match(/^---(.|\n)*?\---/s)){
            textcleaned = textcleaned.replace(/^---(.|\n)*?\---/s, '') // ~Gw:  replace frontmatter
        }
    }

    cleanedlength = textcleaned.length
    return cleanedlength
}

The calls to these functions in class StatsManager{} → async change(text) & class StatusBar → async updateStatusBar(text) are changed to
const currentWords = getWordCount(text,this.plugin.settings);
const currentCharacters = getCharacterCount(text,this.plugin.settings);

display = display + getWordCount(text,this.plugin.settings);
display = display + getCharacterCount(text,this.plugin.settings);

respectively.
The calls to these functions in class StatsManager{} → async calcTotalWords() & class StatsManager{} → async calcTotalCharacters are changed to
words += getWordCount(await this.vault.cachedRead(file),false);
characters += getCharacterCount(await this.vault.cachedRead(file),false);

simply because I don't use that functionality, and currently do not plan on using it. In theory it should be similar, but as I cannot test it I left it to fail silently for now.

To whomever wants to use it, feel free to take it. I just can't build it and don't have the time to set that up on my end, so I'm doing this as an issue instead. All needles are verified to work on my end, and in daily use so-far.

I'll add to this if I find other sets of characters I don't want to consider myself.

Wow thank you for this!

I would love it if it was possible to exclude all/certain code blocks.
I use dataview at the top of a lot of my notes and I would like this block not to be included in the word count displayed in the status bar.
thank you!


Condition.extension:endocrinologicalDisorder doesn't seem needed

endocrinologicalDisorder
This seems really specific to one concept case and I'm not sure it belongs in a specification. I don't see why it would need to be it's own extension.
Google turns up one specific diagnosis code that corresponds to endocrinological Disorder:

Something I'm missing here? Just looks like an example of something you could represent with Condition.

Finnish icd-10 version (specified by THL) has this specific case for codes that end with '&', these are cancer diagnosis that may be supplemented with additional code starting with 'E'  from ICD-10. Here I took the approach of embedding this additional e-code to the condition. Using a completely separate condition instance would be difficult, because we have no condition-to-condition linking in FHIR.
I'm not quite sure if this is Finnish only.
Some kind of condition-to-condition linking or "sub-condition":ing could potentially remove need for some other extensions defined in this profile too.

Maybe it's needed to stay it's own thing, but I'm also not sure how extending the single IDC-10 codeset couldn't accomplish this. Or including multiple related conditions.
Can you include an example of how one of these would be specified with the current specifications?

Still looking for an example - it might make sense as you say but I'd like to see what it looks like.

I'll ad an example.

@mikajylha @jpriebe-epic can you please confirm whether this issue is resolved and can be closed?

Not a huge deal for us if this is left as-is. Would be interested in seeing an example though

Not a huge deal for us if this is left as-is. Would still be interested in seeing an example, though


Historical tool tips cut off be modal size

Describe the bug
Historical tool tips cut off be modal size
To Reproduce
Steps to reproduce the behavior:

Go to 'details page'
Click on 'historical data'
Show first day tool tip

Expected behavior
Tool tip data should be readable
Screenshots

Desktop (please complete the following information):

OS: Fedora
Browser Firefox
Version 65

Additional context
Testing against CI insightsbeta

The modal also cuts off the bottom 'day of month' text when resized

The tooltip is provided by Victory, the underlying library for the charts. We could make the margin much larger, but that may be undesirable.
@dchorvat1 When resizing the window, the modal should be scrollable.


Logs show up as JSON and are not parsed by Stackdriver Logging

Hi, I am using the latest code from master from K8S pod, with the following config:
config :logger_json, :backend,
       metadata: :all,
       formatter: LoggerJSON.Formatters.GoogleCloudLogger

config :logger,
       backends: [LoggerJSON],
       level: :info

The logs do show up in Stackdriver Logging, but they are not parsed, i.e. it doesn't know they are structured (JSON) and is treating them like plaintext. For example this is how it looks like visually:
2018-10-22 09:57:13.907 CEST
{"application":{"version":"0.5.17","name":"tzdata"},"log":"Tzdata has updated the release from 2018e to 2018f"}

Instead it should be parsed, and only show JSON once you click on it, AFAIK.

Thanks for the help!

I think if you provide a message and serviceContext (see https://cloud.google.com/error-reporting/docs/formatting-error-messages) it will display only message when the log is collapsed which might be a easier to parse.

@malcolmstill the problem is that doc is only true when you use API to submit your logs. When they are collected as binaries by stackdriver agent or fluentd in GKE rules are different and there is a very limited number of things you can do.
See https://cloud.google.com/logging/docs/agent/configuration#special-fields.

I've got an example that might be helpful here. We are also running on GKE and experienced the same issue as described here and in #13.
Here's an example log from one of our apps back in stackdriver.

As you can see the initial entry just looks like a line of JSON and everything does work, it just doesn't look pretty in stackdriver.
What my colleague @malcolmstill is suggesting, is that if instead of using the log key, you set the message key, then what happens is the same thing. Except that initial entry is actually parsed from the jsonPayload.message field and printed just like a normal non json log. Picture shows this better:

We've had a play around and this seems consistent from running apps in GKE.
Client Version: v1.14.7
Server Version: v1.14.7-gke.23

Here's a minimal reproduction case using gcloud cli for ease (apologies for my horrendous typos):
gcloud logging write my-test-log '{ "message": "Show me this text", "id": "1234", "log": "This is my log engtry"}' --payload-type=json --severity=DEBUG

gcloud logging write my-test-log '{"id": "1234", "log": "This is my log engtry"}' --payload-type=json --severity=DEBUG

I have tried to read through the documentation on stackdriver as to why this is parsed differently, but still can't understand exactly why.
But it would be super handy as you get all the benefits of json (and exporting to big query) but also the messages in stackdriver look more familiar and easily parsable as only the message field is initially displayed.
I think message field has more tie in to stackdriver debugging too as it may help container multiline errors in logs to a single entry rather than multiple lines.

Oh, I got it @hawksight and I agree that if message would be used by Stackdriver by default we should use it instead of log. For me it's weird that they are behaving differently :). Please send a PR or I'll do it myself in the next weeks.


Incorrect configuration in documentation example

As of the most recent versions of SvelteKit, any VIte plugins must be passed to a vite object in the Svelte config, e.g.
kit: {
  ...
  vite: {
    plugins: [svg()]
  }
}

This is not currently reflected on the plugin documentation - you may want to update it.
Thanks for the super-useful plugin 😃

Thanks for the feedback 😊. I'm on vacation, hence the late response, but an update will come soon.


Notify meta on value

Fixes a minor bug with setValue. We now update meta when the root value is updated.
Additional commits are noted. But one add is jest-dom which includes some convenience matchers to expect

Good call @jdeal! Thanks for that 👍


some  component tests fixes

Description
This PR is a continuation of work in #5082. aiming to have a full set of component tests running on all hypervisors. see #6391 for an inventory of all work to be done.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

included:

[x] test_host_ha.py
[x] test_rootvolume_resize.py
[x] test_vpc_vm_life_cycle.py

Screenshots (if appropriate):
How Has This Been Tested?

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1244

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1494

@nvazquez a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3544


Add charge value to weapons in worn item inventory

Add a counter that shows how many charges until your weapon degrades (I.E. Trident, Archlight, Tentacle, Ibans Staff, Etc) similar to how the slayer helmet overlay looks (example:  )

basically duplicate of #953

I don't think that's the request--as I understand it, this is simply a request to show the charges for any equipment we track charges for when on the equipment tab in addition to on the inventory tab.

Both are requests to show charges for items with charges, so closing as duplicate of #953


Need to propagate exceptions in sync mode

For unit tests it's useful to configure Q with sync=True to avoid the need to run a worker cluster. In this case we expect to get AssertionError exceptions from mocks, and we want those to be caught by the unit test framework so we can see why a test failed.
At the moment exceptions are logged by Q but not propagated to the code that invokes the (synchronous) task, so tests fail for other reasons and you have to look through logging to see what happened.
So we need a configuration option to propagate exceptions when executing tasks synchronously. Or just propagate AssertionError exceptions by default when sync=True.

task.result is the formatted traceback string instead of traceback objects. This is not great for clarity in unit tests (exceptions are logged, but tests don't fail). It's a small change to re-raise the exceptions in the worker when task["sync"] == True.
I have created a simple PR here: #417


module loader error on ubuntu artful 0.1.0~b7-1

Can't 'az login'  from Ubuntu Artful
az login output
root@a1:~# az login
Error loading command module 'storage'
init() got multiple values for keyword argument 'default_completer'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/azure/cli/main.py", line 35, in main
cmd_result = APPLICATION.execute(args)
File "/usr/lib/python3/dist-packages/azure/cli/core/application.py", line 84, in execute
self.parser.load_command_table(command_table)
File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 91, in load_command_table
enable_autocomplete(self)
File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 34, in enable_autocomplete
argcomplete.autocomplete(parser, validator=lambda c, p: c.lower().startswith(p.lower()))
File "/usr/lib/python3/dist-packages/argcomplete/init.py", line 166, in call
default_completer=default_completer)
File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 30, in init
**kwargs)
TypeError: init() got multiple values for keyword argument 'default_completer'
Environment summary
root@a1:~# az --version
Python (Linux) 3.6.3 (default, Oct  3 2017, 21:45:48)
[GCC 7.2.0]
Install method: ubuntu:    apt-get install azure-cli
Distribution: Ubuntu artful
root@a1:~# apt policy azure-cli
azure-cli:
Installed: 0.1.0~b7-1
Candidate: 0.1.0~b7-1
Version table:
*** 0.1.0~b7-1 500
500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status
root@a1:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Artful Aardvark (development branch)"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful

Pertinent piece:
Error loading command module 'storage'
init() got multiple values for keyword argument 'default_completer'

If 0.1.0b7 is the version number of the CLI, this is an incredibly old version.
Did you install with the instructions here?
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest#install-on-debianubuntu-with-apt-get

the default ubuntu image comes with a hint to install the azure cli which installs the outdated version

the default ubuntu image comes with a hint to install the azure cli which installs the outdated version

@rafmathijs Can you provide more details for our own information?
I'm not aware of the above.

I believe this is only relevant for users running on Ubuntu Artful (17.10).
As a user, when you run az in the terminal, you are met with the following error:
><> az
The program 'az' is currently not installed. You can install it by typing:
sudo apt install azure-cli

Running the instructions as followed gives you v0.1.0.
><> sudo apt install azure-cli
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.13.0-16 linux-headers-4.13.0-16-generic linux-image-4.13.0-16-generic linux-image-extra-4.13.0-16-generic
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  azure-cli
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 170 kB of archives.
After this operation, 2,108 kB of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu artful/universe amd64 azure-cli amd64 0.1.0~b7-1 [170 kB]
Fetched 170 kB in 1s (147 kB/s)
Selecting previously unselected package azure-cli.
(Reading database ... 222252 files and directories currently installed.)
Preparing to unpack .../azure-cli_0.1.0~b7-1_amd64.deb ...
Unpacking azure-cli (0.1.0~b7-1) ...
Setting up azure-cli (0.1.0~b7-1) ...

We should probably get this apt repository removed if we are maintaining a separate apt repository for azure-cli builds.
For reference, this is a completely vanilla install of Artful:
><> apt list | grep azure-cli

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

azure-cli/artful,now 0.1.0~b7-1 amd64 [installed]

Output of all sources:
><> cat /etc/apt/sources.list | grep -v "^$" | grep -v "^#"
deb http://ca.archive.ubuntu.com/ubuntu/ artful main restricted
deb http://ca.archive.ubuntu.com/ubuntu/ artful-updates main restricted
deb http://ca.archive.ubuntu.com/ubuntu/ artful universe
deb http://ca.archive.ubuntu.com/ubuntu/ artful-updates universe
deb http://ca.archive.ubuntu.com/ubuntu/ artful multiverse
deb http://ca.archive.ubuntu.com/ubuntu/ artful-updates multiverse
deb http://ca.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu artful-security main restricted
deb http://security.ubuntu.com/ubuntu artful-security universe
deb http://security.ubuntu.com/ubuntu artful-security multiverse
deb [arch=amd64] https://download.docker.com/linux/ubuntu artful edge

And as @derekbekoe pointed out, following the instructions from https://docs.microsoft.com to add the Ubuntu Wheezy repository and install azure-cli worked like a charm. For others, that'd be
echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ wheezy main" | sudo tee /etc/apt/sources.list.d/azure-cli.list
sudo apt-key adv --keyserver packages.microsoft.com --recv-keys 52E16F86FEE04B979B07E28DB02C46DF417A0893
sudo apt-get install apt-transport-https
sudo apt-get update && sudo apt-get install azure-cli

Thanks Derek! :)

Opened https://bugs.launchpad.net/ubuntu/+source/azure-cli/+bug/1745467 to track this.

Still have the issue on Ubuntu.

@yami12376 while we're still waiting on Ubuntu's end to remove the package from Ubuntu's apt repositories, you can follow the steps I provided above (https://github.com/Azure/azure-cli/issues/4692#issuecomment-353206432) to add the wheezy repository to your list to install the Azure CLI.

@bacongobbler  I manage to install newer version with:
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?view=azure-cli-latest


Missing Mixer for Fixed-Wing HIL Simulation

I tried to run the HIL simulation using the XPlane10 simulator. The airplane model is the HILStar downloaded from the Pixhawk webpage. The Pixhawk is flashed with the latest release (v1.6.5) and using the HILStar(XPlane) airframe. The stable release v3.2 of QGC is used.
When running the simulation according to this Guideline the data from the XPlane simulator is received on the Pixhawk. However, it is not possible to fly the airplane with a remote control. The reason is that the AERT mixer is missing, it was deleted in commit  previous to the latest firmware release. By just adding the latest version of the mixer to the firmware the HIL simulation works as expected.
Was the AERT mixer deleted accidentally or is there a way to run the HIL simulation without adding the mixer manually to the firmware?

I've been meaning to fix this. https://github.com/PX4/Firmware/pull/7620
I'll find time later today to go through it with the latest PX4 + QGC and make sure everything is working again.

Fixed by #7794


[Event Request] page 9209 "Invt. Analys by Dim. Matrix" - OnBeforeAnalysisViewSelection

We would like to add a new event OnBeforeAnalysisViewSelection in the following trigger:
trigger OnOpenPage()
var
    IsHandled: Boolean;
begin
    CurrentAnalysisArea := CurrentAnalysisArea::Inventory;

    GLSetup.Get();
    //A200F0010.Event.ns
    OnBeforeAnalysisViewSelection(
        CurrentAnalysisArea, CurrentItemAnalysisViewCode, ItemAnalysisView, ItemStatisticsBuffer, Dim1Filter, Dim2Filter, Dim3Filter, IsHandled);
    if IsHandled then
        exit;
    //A200F0010.Event.ne
    ItemAnalysisMgt.AnalysisViewSelection(
      CurrentAnalysisArea.AsInteger(), CurrentItemAnalysisViewCode, ItemAnalysisView, ItemStatisticsBuffer,
      Dim1Filter, Dim2Filter, Dim3Filter);
end;

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnBeforeAnalysisViewSelection(CurrentAnalysisArea: Option; var CurrentItemAnalysisViewCode: Code[10]; var ItemAnalysisView: Record "Item Analysis View"; var ItemStatisticsBuffer: Record "Item Statistics Buffer"; var Dim1Filter: Code[250]; var Dim2Filter: Code[250]; var Dim3Filter: Code[250]; var IsHandled: Boolean)
begin
    //A200F0010.Event
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


accurics.gcp.NS.112 suggest basic auth is enabled when is not

terrascan version: v0.1.10
Operating System: MacOS 10.15.7

Description
As per Hardening your cluster doc, we should disable basic-auth.
As per Terraform docs the way to accomplish so is by providing an empty username and password.
However, terrascan is suggesting that I have basic-auth enabled which I'm not.
Please note that not specifying these fields at all won't enable basic-auth and doesn't fire the rule.
What I Did
cat <<EOF > cluster.tf
resource "google_container_cluster" "cluster" {
  master_auth {
    username = ""
    password = ""
  }
}
EOF
terrascan scan -t gcp -f cluster.tf
results:
  violations:
  - rule_name: gkeBasicAuthDisabled
    description: Ensure GKE basic auth is disabled.
    rule_id: accurics.gcp.IAM.110
    severity: HIGH
    category: Identity & Access Management
    resource_name: cluster
    resource_type: google_container_cluster
    file: cluster.tf
    line: 1
  count:
    low: 0
    medium: 0
    high: 1
    total: 1

What I Expect
cat <<EOF > cluster.tf
resource "google_container_cluster" "cluster" {
  master_auth {
    username = ""
    password = ""
  }
}
EOF
terrascan scan -t gcp -f cluster.tf
results:
  violations: []
  count:
    low: 0
    medium: 0
    high: 0
    total: 0

Thanks for catching this and providing a reproducer, @lucas-giaco!

Thanks to you for the quick fix :)


A lot of generated java files contain 'OpenHashMap.drv' / 'OpenHashSet.drv' string only

for example
Byte2LongLinkedOpenHashMap.java contains string OpenHashMap.drv only
ByteOpenCustomHashSet.java - OpenHashSet.drv

this is because these files contain only mentioned strings

not sure if I remember correctly but these are symlinks which windows (screenshot looks like windows) doesn't handle in the same way (NTFS has symlinks I think but they are hardly used)

Please replicate under a sensible OS (Linux, Mac OS X).

ok. got it
What about replacing in the makefile strings:
LinkedOpenCustomHashMap.drv -> OpenHashMap.drv
LinkedOpenCustomHashSet.drv -> OpenHashSet.drv
LinkedOpenHashMap.drv -> OpenHashMap.drv
LinkedOpenHashSet.drv -> OpenHashSet.drv
OpenCustomHashMap.drv -> OpenHashMap.drv
OpenCustomHashSet.drv -> OpenHashSet.drv
I have done it, it works.


PubSub : add the concept of message abandonment

PusubMessage / AckReplyConsumer needs the concept of "abandoning" a message.
Abandoning a message would mean that the message ack deadline would no longer be auto-extended.
public void receiveMessage(final PubsubMessage message, final AckReplyConsumer consumer) {
	try {

		// message processing

		consumer.ack();
	} catch (Throwable t) {
		// In an effort to prevent a tight message delivery / processing loop,
		// we want to abandon the message (stop extending the ack deadline and
		// let the message expire "naturally")

		consumer.abandon();
	}
}

I would second this request. I need to be able to abort processing without what is essentially instantaneous redelivery. If I'm writing messages to a DB and the DB is down, for example, and will be down for an an extended period, there is no need or desire to instantaneous reprocess that would fail thousands and and thousands of times. But I dont want to throw it away, as service will eventually be restored.
 It will result in potentially millions of unnecessary instant failed retry attempts, all logged and eating at my bill.
The "abandoned" concept would allow the service to simply redeliver based on the subscription ack timeout which at least is better than immediately before any type of downstream service recovery has occurred.
Or I could even ework with a .nack(redelivery_delay) call and manage the redelivery timing myself, per message.
Native, innate. Support for built in exponential backoffs for nacked messages, configured at the subscription level would be ideal, but I'll take anything at this point.

nhartner@, if you simply stop extending the ack deadline, the Cloud Pub/Sub service will likely resend the exact same message back to you instantaneously once the most recent period expires.  This means it will be sent back to you in 30 seconds (or whatever your configured ack extensions period is) instead of .5 seconds when you nack it.  If you want to implement a per-message exponential backoff on another service (a database for example) you should consider implementing that in your own code, since Cloud Pub/Sub has no way of knowing what backoff pattern you would find acceptable.
You can implement this in your message handler by performing x requests with y delay between them on failure, acking on any success and nacking on final failure.  Google's api-client-library provides a useful utility for generating backoff times here.  But simply not extending the deadline is not a useful answer, as it gives the user no control over when they want to retry.
As an aside, if the answer to 'when to retry' is 'never', I would suggest using a dead letter queue pattern, where you publish unprocessable messages to a separate topic, nack them once publish is guaranteed, and handle them separately.

@dpcollins-google I used the term abandon() but in reality it's an async delayed nack().  I understand that this can be implemented by a developer ... but it seems like such a common pattern that it should be in the API proper.
For example ... given a Subscriber with a max ack extension period of 1 hour ...
public void receiveMessage(final PubsubMessage message, final AckReplyConsumer consumer) {
	try {
		// message processing

		consumer.ack();
	} catch (Throwable t) {
		// In an effort to prevent a tight message delivery / processing loop
                // perform a delayed nack() ... asynchronous nack after 600000 milliseconds
                consumer.nack(600000);
	}
}

@dhoard Whether this is a common pattern is kind of orthogonal to the question of whether this is something that should be handled by pubsub.  If you want to retry after 10 minutes, every 10 minutes, thats fine if that is the correct backoff strategy for whatever service that might fail that you're interacting with.  I'd argue that that backoff strategy should be part of the client library for the service you're communicating with, not the Cloud Pub/Sub library.  If you're making requests to an external service that might fail that does not implement a backoff strategy, the correct thing to do (in my opinion) would be to implement a backoff strategy appropriate for that service in that client library.

@dpcollins-google your points are valid.
@sduskis given the discussion above, I have no problem with closing this issue.

For any possibly subscribers on the issue, something like the code below (not tested) could be used in your application to perform a simple delayed nack()
import com.google.cloud.pubsub.v1.AckReplyConsumer;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.util.concurrent.Executors;
import java.util.concurrent.ScheduledExecutorService;
import java.util.concurrent.TimeUnit;

/**
 * Class to perform assynchronous nack of AckReplyConsumer
 */
public class AckReplyConsumerUtils {

    private static final Logger logger = LoggerFactory.getLogger(AckReplyConsumerUtils.class);

    private static AckReplyConsumerUtils instance = new AckReplyConsumerUtils();

    private ScheduledExecutorService scheduledExecutorService;

    private AckReplyConsumerUtils() {
        this.scheduledExecutorService = Executors.newScheduledThreadPool(100);
    }

    /**
     * Method to get instance
     *
     * @return AckReplyConsumerUtils
     */
    public static AckReplyConsumerUtils getInstance() {
        return instance;
    }

    /**
     * Method to asynchronously nack an AckReplayConsumer after a delay
     *
     * @param ackReplyConsumer
     * @param delay
     * @param timeUnit
     */
    public void nack(AckReplyConsumer ackReplyConsumer, long delay, TimeUnit timeUnit) {
        this.scheduledExecutorService.schedule(
                new Runnable() {
                    @Override
                    public void run() {
                        try {
                            ackReplyConsumer.nack();;
                        } catch (Throwable t) {
                            logger.warn("Exception nacking message");
                        }
                    }
                },
                delay,
                timeUnit);
    }
}

AckReplyConsumerUtils usage example ...
public void receiveMessage(final PubsubMessage message, final AckReplyConsumer consumer) {
	try {
		// message processing

		consumer.ack();
	} catch (Throwable t) {
		AckReplyConsumerUtils.getInstance().nack(consumer, 10, TimeUnit.MINUTES);
	}
}

Please note that @kolea2's response is still correct. We do agree this is a useful feature, but would want to ensure the service supports it natively rather than just using modify ack deadline for it. Delaying the nack on a message may have unintended consequences if flow control limits are set. These messages will count toward the outstanding messages and so more messages will not be delivered if enough message responses are delayed. We will provide updates when we have more to share on the possibility of supporting delayed redelivery for messages.

@dhoard thanks for the suggested workaround. I'll be interested to play around with this. I suspect 100 threads is overkill since tasks are internally put in a queue by ScheduledThreadPoolExecutor and don't tie up a thread until they are ready to processed.


"No Data" in "Cell Count (Estimated)" column inconsistent with "Unspecified"

In conversations with @NoopDog about the Known diseases field when there is no information in the metadata, we decided that entering "Unspecified" was a solution as this term is used elsewhere to convey that the information is not known (GH issue).
On the main Browser landing page (defaults to Project view), missing Cell Count (Estimated) data is shown as "No Data", which is not consistent with the rest of the site. I suggest keeping this consistent and displaying "Unspecified" if cell counts are missing from the metadata.

Hi @malloryfreeberg these updates have been promoted to staging. Would love to have your feedback.
https://staging.data.humancellatlas.org/explore/projects
Thanks,
D


Abort on panic

Currently tests hang if a thread panics, meaning that if a lot of tests panic CI can hang for a long time. For testing purposes we just want to abort on panic to ensure we get quick test output in those cases.

I added it to the debug profile as well.


add observation common name

current code pulls common name from genus - many orgs only have common names for species but entire genera. so use the common name attached to the specific observations as well

added in 13cac9f


ability to render(), error message from server in exception

@catherio please review this changes.
1. I've changed _post_request() to return json. This works as optimization (many json() removed), but more importantly it parses error message from server. Now code like this:
    env_id = 'CartPole-v1337'
    instance_id = client.env_create(env_id)

Prints on client side:
ValueError: Attempted to look up malformed environment ID 'CartPole-v1337'

2. I've changed get_required_param() on server side so it works directly on json. This works as optimization when more than one parameter needed.
3. step() now has render parameter (boolean). If true, it renders current state in a window. There was no way to render before. It is bundled with step() because possibly we don't want another roundtrip for render() call.
After (3) it's obvious that we also have environment leak, environments don't close. But I stop here because it's already a lot of changes and you may have done something similar already.

...and I also pushed C++ binding to master, it appeared here.
Dependencies: jsoncpp, libcurl.
Random agent even works, but sure there are bugs.


CSS Styling the Class

Description
In css, Brackets does not recognize my classes. So when want to use css for a class, it totally ignores the class.
Expected behavior: [The css to recognize my class. ]
Actual behavior: [Brackets did not recognize the class.]
Versions
On brackets 1.9,

Hi @Loganpi,
could you share some code where this occurs?

Here you go, you can see that the css styling is not recognizing the class

@Loganpi From the screen shot it seems both the language mode CSS and HTML is rendered using consistent code coloring.  What's the theme you are using?  Looks like the theme has been written to color selectors as red. To avoid any confusion, if you are using a custom theme, switch back to Brackets default theme. If that's not the case, please share the whole CSS file.

What is a theme?

In the live preview it didn't style as it was supposed to.

Please share the whole CSS file.  Looks like it has a broken syntax...

OK. I will do it this afternoon.

https://drive.google.com/drive/folders/0B7mODDgNFqgFajY4YnJDRU9CeGM
Go to this link, I cant upload the files directly to github.

I am doing a slideshow.

The files linked in the comment above seems to have changed.
I think you had a syntax error in your css.
Closing.


mock: split code into modules

This also fixes the tests, it seems they have been broken and could not be executed.

Looks good, thanks! I think this code need a comprehensive refactor / redesign and this is a good first step in that direction.

Agreed! I will try to keep that in mind as I add the mocking code.


Revert "Configure cloud provider"

Reverts Agazoth/github-actions-continuous-delivery-azure#2

Adding label


API requires password?

I got the API to run with this code:
//import { client } from "@gradio/client";

// This did not help:
// const client = require('@gradio/client');

(async () => {

    // This did not work, because the client is not a function.
    //const client = await import('@gradio/client');

    const dynamic = new Function('modulePath', 'return import(modulePath)');

    const { client } = await dynamic('@gradio/client');

    const app = await client("http://osprey:osprey@<IP_ADDRESS>:8000/");
    const result = await app.predict(0, []);

    // @ts-ignore
    console.log(result.data);

})();

but I get this error:
Error: Could not get config:
    at resolve_config (file:///home/arthur/dev/ai/manga/node_modules/@gradio/client/dist/index.js:1390:11)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///home/arthur/dev/ai/manga/node_modules/@gradio/client/dist/index.js:457:18

which I think is due to the page requiring the osprey/osprey password...
could that password be removed so API access can work?
Thanks.

Hi, @arthurwolf
I recommend deploying our model locally in your machine instead of relying on the online API for several reasons.
Firstly, the online API is currently serviced as a demo and hosted on a single machine with limited trial support, making it unsuitable for large-scale access. Users may experience delays as they need to queue up after multiple visits. Secondly, the online API only caters to two question types: simple description and detailed description, which may not align with your specific requirements.

Thanks for the answer.
I don't mean to use the demo for large scale use, I mean to use it exactly for what it's meant: a demo...
Deploying the model locally is going to mean a lot of work and a lot of money to spend, I need to know if the model does what I want before I do that. I thought the demo would enable me to do that, and that was the reason why the demo API was exposed...


Request for contributing invitation.

Hey, Myself Andri Wahyudi (1st Hackerone Inc Leaderboard)

[ ]  Python Programming Enthusiast
[ ]  Penentration Testing / Vulnerability Analysis
[ ]  Focus on Contributing more throughout the year

Welcome mate !!


qbittorrent icon for queued torrents is a broken image

Describe the bug
after ap[plying the default theme the icon for torrents that are waiting in the seed queue are a broken image
Theme Install Method (Don't skip)
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=${TIMEZONE}
      - WEBUI_PORT=8532
      - DOCKER_MODS=ghcr.io/gilbn/theme.park:qbittorrent
    volumes:
      - ./config_qbt:/config
      - /shares/nfs/torrents:/downloads
      - /shares/nfs/torrents/_incomplete:/incomplete
      - /shares/nfs/media_vault/:/media_vault
    ports:
      - 8532:8532
    restart: always
    stop_grace_period: 60s
    labels:
      containermon.enable: true

qbittorrent  | [mod-init] **** Installing all mod packages ****
qbittorrent  | fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
qbittorrent  | fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
qbittorrent  | (1/8) Installing libuuid (2.38.1-r0)
qbittorrent  | (2/8) Installing apr (1.7.0-r2)
qbittorrent  | (3/8) Installing apr-util (1.6.1-r13)
qbittorrent  | (4/8) Installing lz4-libs (1.9.4-r1)
qbittorrent  | (5/8) Installing libsasl (2.1.28-r3)
qbittorrent  | (6/8) Installing serf (1.3.9-r10)
qbittorrent  | (7/8) Installing subversion-libs (1.14.2-r4)
qbittorrent  | (8/8) Installing subversion (1.14.2-r4)
qbittorrent  | Executing subversion-1.14.2-r4.pre-install
qbittorrent  | Executing busybox-1.35.0-r27.trigger
qbittorrent  | OK: 127 MiB in 72 packages
qbittorrent  | ------------------------------
qbittorrent  | | qBittorrent theme.park Mod |
qbittorrent  | ------------------------------
qbittorrent  | Variables set:
qbittorrent  | 'APP_FILEPATH'=/config/qBittorrent/qBittorrent.conf
qbittorrent  | 'TP_DISABLE_THEME'=
qbittorrent  | 'TP_HOTIO'=
qbittorrent  | 'TP_DOMAIN'=
qbittorrent  | 'TP_COMMUNITY_THEME'=
qbittorrent  | 'TP_SCHEME'=
qbittorrent  | 'TP_THEME'=
qbittorrent  |
qbittorrent  | No domain set, defaulting to theme-park.dev
qbittorrent  | No scheme set, defaulting to https
qbittorrent  | No theme set, defaulting to organizr
qbittorrent  | ---------------------------------------
qbittorrent  | | Downloading WebUI files from github |
qbittorrent  | ---------------------------------------
qbittorrent  |
qbittorrent  | Downloading qBittorrent webui to "/themepark"..please wait
qbittorrent  |
qbittorrent  | Download finished
qbittorrent  |
qbittorrent  |
qbittorrent  | Downloading qBittorrent webui icons to "/themepark/xxx"..please wait
qbittorrent  |
qbittorrent  | Download finished
qbittorrent  |
qbittorrent  | ---------------------------------------
qbittorrent  | | Adding the stylesheet to html files |
qbittorrent  | ---------------------------------------
qbittorrent  | Stylesheet set to organizr on /themepark/public/index.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/upload.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/confirmruleclear.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/newtag.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/rename_feed.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/rename.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/confirmdeletion.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/newfolder.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/confirmruledeletion.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/shareratio.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/newcategory.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/addpeers.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/index.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/download.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/newrule.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/properties.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/filters.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/preferencesToolbar.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/search.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/propertiesToolbar.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/rss.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/searchplugins.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/installsearchplugin.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/statistics.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/aboutToolbar.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/rssDownloader.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/about.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/preferences.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/views/transferlist.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/newfeed.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/addtrackers.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/uploadlimit.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/setlocation.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/rename_file.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/rename_rule.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/downloadlimit.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/confirmfeeddeletion.html
qbittorrent  |
qbittorrent  | Stylesheet set to organizr on /themepark/private/edittracker.html

Application Info (Don't skip)

Version - n/a
Branch - n/a
Container - n/a
Logs - see above

To Reproduce
Steps to reproduce the behavior:

add the DOCKER_MODS=ghcr.io/gilbn/theme.park:qbittorrent to docker-compose.yml
rebuild stack
open qbittorrent ui
See error

Expected behavior
the image should be there
Screenshots

Desktop (If applicable) (please complete the following information):

OS: Win11
Browser: vivaldi (chrome based)
Version: always latest stable

Additional context
I tried with different theme (nord) but it's the same

Errors in the browser console?

I searched for the file inside the container and found it at
/themepark/public/icons/queued.svg
/themepark/private/icons/queued.svg

They are identical. If I copy what's inside it to notepad and save it as a .svg and drag it to either Vivaldi or Edge or IrfanView it opens the picture correctly.
I also tried to run the svg thru SVG Sanitizer (https://svg.enshrined.co.uk), which changed it a bit. I replaced the contents of both queued.svg inside the container with the sanitized .svg code, restarted the container, but it's the same.

Found the issue:
line 982 of dynamicTable.js calls for
img_path = "images/queued.svg";, but there is no such file ls: cannot access '../images/queued.svg': No such file or directory, however there is ../icons/queued.svg.
I copied the file like so @5ec3179abb1a:/themepark/private/scripts$ cp ../icons/queued.svg ../images/ and reloaded the page without restarting the container and "it just works".
I wanted to make a PR for that, but I gotta come clean I'm too stupid to figure out GitHub (I couldn't even find the .js file lol)

The files are downloaded from here https://github.com/GilbN/theme.park/blob/master/docker-mods/qbittorrent/root/etc/s6-overlay/s6-rc.d/init-mod-themepark/run#L69

https://github.com/qbittorrent/qBittorrent/issues/18073

Fixed upstream


Autobahn without crossbar.io

I have just started adapting my current architecture for a Django + pusher.com website to a more realtime-friendly application. I am wondering it Autobahn over asyncio can be run on its own without the need of any additional external routers/servers like crossbar.io (option suggested at the Autobahn's website).

You can use AutobahnPython as a pure WebSocket library. When using WAMP, a router is always required. Btw: we have a mailing list;)


Roll engine e91e4db7e03d..fbb7893a0820 (3 commits)

https://github.com/flutter/engine/compare/e91e4db7e03d...fbb7893a0820
git log e91e4db7e03d..fbb7893a0820 --no-merges --oneline
fbb7893a0 Report asset names in loading trace events. (flutter/engine#6713)
d06ace699 Roll src/third_party/skia 3bdaa46bff71..f1eda00bf6b0 (11 commits) (flutter/engine#6724)
60d4d582f Roll src/third_party/skia 763fc966993d..3bdaa46bff71 (2 commits) (flutter/engine#6723)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5299922083512320

Commit queue failed; closing this roll.


Multi-Line Replacement in tokens

Hello,
First off thank you for this great tool! Its awesome! :)
I am trying to do an import using the following methodology:
#%%AD_SERVER_LIST%%=<List>\
#<String>[server1.domain.com](http://server1.domain.com/)</String>\
#<String>[server2.domain.com](http://server2.domain.com/)</String>\
#<String>[server3.domain.com](http://server3.domain.com/)</String>\
#</List>

the import is ignoring the \ and terminating on the first line (so none of the strings or the closing list make it in the import) and I end up with the following:
              <entry key="servers">
                <value>
                    <List>\
                </value>
              </entry>

Error thrown:
2022-04-14T23:15:01,870 TRACE http-nio-8080-exec-4 sailpoint.WorkflowTrace:216 - Starting step Import
2022-04-14T23:15:01,925 ERROR http-nio-8080-exec-4 sailpoint.IIQDevAcceleratorWF:-2 - Importer failed with exception: java.lang.RuntimeException: Line: 103 Column:19: The element type "List" must be terminated by the matching end-tag "</List>".
2022-04-14T23:15:01,950 TRACE http-nio-8080-exec-4 sailpoint.WorkflowTrace:216 - Step result variable: payload
2022-04-14T23:15:01,951 TRACE http-nio-8080-exec-4 sailpoint.WorkflowTrace:216 - <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE String PUBLIC "sailpoint.dtd" "sailpoint.dtd">
<String>java.lang.RuntimeException: Line: 103 Column:19: The element type "List" must be terminated by the matching end-tag "</List>".</String>

thanks, Robert!
At this point the multiline properties are not supported by the extension, sorry :(
I know it's supported by the sailpoint ssb, but in the extension I use an external library to read property files which only supports one liners.
At this point your best bet is just to convert it to one line (a little harder to read but well supported)
Let me know if it's a show stopper for you.

My team would consider this a show stopper.
We use the multi-line tokens for our email templates. Specifically to include stylesheet, header, and footer information. Makes the email templates consistent. We had to switch to utilizing tokens when SailPoint removed the ability (for security reasons) for email templates to reference/import other email templates.
Could we convert it all to one line... yes, but it does make maintenance a pain.
One final note... The Extension is AWESOME. I much prefer working from Visual Studio Code.
Keep up the good work!!!


MAINT: remove old todos

This is a toughy, @jairideout can you review?

There's too much cognitive overhead for me to possibly review this.


Issue templates are too complicated

BUG DESCRIPTION
Problem
The issue templates are too complicated.
Steps to reproduce

Submit a bug report or feature request about any bug/feature
Assign the issue to yourself
Fill out the issue owner section for the planned work

Current behavior
The issue templates are frequently not completely filled out or are filled out incorrectly.  Frequently, the issue owner section is not filled out.  Sometimes, other users have gone in and fleshed out or edited some issues after the initial report.  Work typically begins without having filled out the issue owner section.
Another observation I have had is that whenever there has been decent effort invested into filling out the issue owner section, the review of designs, limitations, assumptions, etc often goes off the rails (causing a delay while trying to reach agreement) - particularly when compared to when the design happens concurrently with coding and the first time reviewers see the work is after it's done.  Even though the work that is done was so contentious when presented as a design, there is usually no or very few issues when the end result (i.e. the code) is reviewed.
Expected behavior
A submitter completely and correctly fills out the bug/feature section.  The issue owner fills out the issue owner section.  Ideally, at this point, the issue owner section (if our process dictates a review is necessary - usually based on self-gauged level of effort) would be reviewed before work begins, but we have not developed a mechanism to govern this process.  Then coding would begin.
Suggested Change
I don't think anything needs to be changed WRT the feature or bug report sections.  I think accuracy WRT entries in these sections have been improving and usually it's only the comment section that is empty.  We could remove the examples to make it look cleaner, but I think it's not really hurting anything and could still aid infrequent and/or new submitters (e.g. lab members).
WRT the issue owner section, there are 2 possibilities.  In either case I don't think there's any benefit in eliminating the issue owner section.

Ideally we would develop a process for design review that would specify when the issue owner section needed to be filled out and develop processes for when/if it should be reviewed, by how many people, and how frequently that should occur.  The method by which we submit a design could probably be benefitted by standardizing a design style so that we all know how to read each others' designs.
It may benefit from some tweaks/discussion to address any clarity issues.

Comment
This issue was captured during a Zoom meeting.
I actually am not sure what the issue precisely is.  The above is my interpretation.  In the context of submitting a bug/feature (in which the issue was brought up), I don't understand what is complicated.  These sections seem straightforward:

Problem
Steps to reproduce
Current behavior
Expected behavior
Suggested Change
Comment

In fact, I think breaking up the bug report into these sections has improved our bug reporting dramatically. Before I started using a template like this, I would read my own reported issues and often be bewildered about what the real problem was that I myself had reported, let alone anyone else's.
So I would guess that the "too complicated" feedback refers to the "issue owner section". I would argue that each item/section is straightforward, and I think would also have a positive impact on our overall development if we actually used it properly, which we haven't been doing. And by that, I mean: filling it out when we take an issue and have a design review before work begins. I know that we implicitly/tacitly decided to not do that because of a perception that it slows things down (i.e. increases costs in terms of time). I would argue that it would have the opposite effect. The earlier a bug is caught, the cheaper it is (i.e. less time it takes) to fix. Performing these processes doesn't have to take long at all, and the extra time spent fixing issues after work is done adds up to much longer. It really wouldn't take that long to do if we simply made the time (i.e. developed the processes) to handle it.
Besides, by and large, the bulk of expensive projects' cost, when initial development time is minimized (by cutting out such rigor), is in the maintenance phase - debugging and refactor work. There's a significant inverse relationship between development duration and long term costs (when normalized by project size).
Anyway, I'm not proposing we change how we're currently operating. I just think that if there are elements of the templates that can be disambiguated and if fixed, would be more utilized, I think we should fix it.

ISSUE OWNER SECTION
Assumptions

List of assumptions made WRT the code
E.g. We will assume input is correct (explaining why there is no validation)

Requirements

List of conditions to be met for the feature
E.g. Every column/row must display a value, i.e. cannot be empty

Limitations

A list of things this work will not fix
E.g. Getting edge case X to work requires too much effort and will not be
fixed in this effort.

Affected/Changed Components

Files
Environment variables
External executables
Database tables
Cron job settings
Etc.

DESIGN
GUI Change description
Describe changes the user will see.
Code Change Description (Pseudocode optional)
Describe code changes planned for the fix.
Tests
A test should be planned for each requirement (above), where possible.

I don't have a problem with the bug reports as they are, though I'm happy to discuss proposed changes if people have suggestions. I think they have improved the reporting of bugs quite a bit.
I do think, however, that we need a process for lab members to quickly submit issues / suggestions that we, as developers, will then triage and respond to. If we determine that an issue (bug report or enhancement request) should be created in response, we can point the lab member to the issue so they can comment further, follow progress if they like, etc.
I'm going to write up a process in a GitHub issue so we can get a link created and we all know where to look for feedback.

Even in the context of researcher feedback, while I mentioned I could create a separate streamlined template specifically for researcher feedback, I don't think that the current templates are too complicated in the same way that I don't think a DMV form isn't too complicated.  The complexity is under a heading (e.g. "DMV official use only") that I think clearly is understandable to researchers in the same way that the "issue owner section" does not have to be filled out by them. Thus, given that plus our own disuse of that section, it's easy to have inferred that the "too complicated" criticism was more broad in scope than researcher use.
That said, there's still an issue WRT the bug/feature mechanism separate from the researcher feedback feature which is a different issue.  Whether it's "too complicated" or not, the template is underutilized and either it needs to change or processes surrounding it should be developed.
WRT that separate researcher feedback issue, I also agree that we shouldn't force researchers to register for a github account.  A quick google reveals a couple ways to allow the creation of github issues without requiring a github account:

gitreports
[using a google form[(https://ez34.net/2016/12/publish-anonymous-issues-on-github.html)

Regarding this issue, my feeling about how the underutilization of the issue owner section should be addressed has been discussed before (e.g. via the development of an SCMP), so I don't think it's worth rehashing.  But, one thing that I think would move us forward is to adopt a set of design and/or pseudocode conventions/standards.  That, plus, the rocket idea (which I think was only agreed upon informally) has not panned out because

it didn't have the procedures to back it up
our design (issue owner section) review process has not proven to illicit productive feedback
If the main purpose of the section is (as I would describe) to catch bugs earlier in our process and lessen our overall time-costs, I think that a design review should:
Be triggered/conditionally-required based on a self-estimated "level of effort"
Be treated like a code-review
But for right now, all I'm interested in is better characterizing the problem that is causing underutilization of the "issue owner section", as you guys would characterize it. If that problem is related to for example, a belief that it costs more than it benefits us, then the next step would be to assess whether that's true to establish buy-in. I think there is enough data in the issues to perform an audit/cost-benefit analysis.


Traing Time

Hello,
How long does the model need to train?

@AmingWu It depends on what device you use to train the network. It takes around half a day on a single 1080ti for each stage if I remember correctly.


types: add OP and STATUS Codes

Please describe the changes this PR makes and why it should be merged:
Would appreciate if codes would be checked before merging.
Status

[ ] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

opcodes_status_codes.ts

Is in snake case now.


fix for default max gas on payable functions

What ❔
Removed the gasLimit override for payable functions.
Why ❔
The explorer sets the gas limit to 10000000 by default for payable functions, preventing connected wallets like MetaMask from setting their own correct gas estimates.

Thanks for the PR, the same changes were already done in this PR.


sysbench: 1.0.6 -> 1.0.13

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin/sysbench --help got 0 exit code
ran /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin/sysbench --version and found version 1.0.13
found 1.0.13 with grep in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
found 1.0.13 in filename of file in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘sysbench-1.0.13’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/development/tools/misc/sysbench/default.nix:18 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
make[1]: Leaving directory '/tmp/nix-build-sysbench-1.0.13.drv-0/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
shrinking /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin/sysbench
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin
patching script interpreter paths in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
/nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/share/sysbench/tests/test_run.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash"
checking for references to /tmp/nix-build-sysbench-1.0.13.drv-0 in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13...

Success on aarch64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13
shrinking /nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13/bin/sysbench
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13/bin
patching script interpreter paths in /nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13
/nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13/share/sysbench/tests/test_run.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/bash"
checking for references to /build in /nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13...
/nix/store/17ynr3bvslpnzw7rmhgph8mqpsv6qrx6-sysbench-1.0.13


continueLabelText and skipButtonText properties added

Added continueLabelText and skipButtonText properties for customize text of continue label and skip button.

Can you please merge this PR, we also need this and it's really handy :)

@ctews done.  Updated repo and pod spec.
@mugabe: thanks for your help. I did a little change to avoid some warnings

Thx @mugabe !


Simple dump speedup

Reduce workload perfomed by sync client & server
Add support for velocypack (but leave it deactivated for now)

Lets see whether this works, can't compile right now on devel http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr-linux/421/


Can I search for all of my @mentions?

Or can I search for @mentions of a certain user?

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

ID: 34ae521f-6ae4-4d7f-2cce-f844e5811b66
Version Independent ID: 18098490-1f34-e966-3135-cb90197bfa6f
Content: Use @mentions in work items and pull requests - Azure DevOps Services & TFS
Content Source: docs/notifications/at-mentions.md
Product: devops
GitHub Login: @chcomley
Microsoft Alias: chcomley

Without a way to search mentions as part of a query. The emails gets lost and no way for us to respond.

This is a feature request disguised as a question.  while one can use 'history' field and search for your specific mention name string.  however, it would be much easier if there was an @me parameter within history so any user can see THEIR mentions in a shared query.

Hi @rselvarajbsd and @herkyjerky,
We address content feedback on this avenue, however here's a link if you'd like to submit a feature request, idea, or get support: https://developercommunity.visualstudio.com/content/idea/post.html?space=21. Thanks.


added bin support + port from env variable

A minimal changes to make the package to run and configured as a global.
npm i -g https://github.com/noygal/linux-dash.git#feature/bin
export PORT=8080
linux-dash

Thank you, @noygal. This is a very useful addition.


libc/test/common

Codecov Report

Merging #45 (37a1730) into musl-go (f7774f6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           musl-go      #45   +/-   ##
========================================
  Coverage    12.52%   12.52%
========================================
  Files          497      497
  Lines        19405    19405
========================================
  Hits          2430     2430
  Misses       16812    16812
  Partials       163      163

Continue to review full report at Codecov.

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


Update docstring usage of code-block

In a lot of places we use .. code-block: yaml, however the correct format is .. code-block:: yaml.  Cleaning this up will show our sample policies in the resource documentation.

merged


Add "strlen" extractionFn.

Just a nice simple function that helps with #3682.
Also added clarifications to how we count characters in strings.

👍

👍


use poetry to manage dependencies

Changes

Comments

#156
#155
#154  👈
master

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

Join @chrisaddy and the rest of your teammates on  Graphite

Merge activity

May 14, 9:13 PM EDT: @chrisaddy started a stack merge that includes this pull request via Graphite.


Tweek verifying step header

@Expensify/pullerbear
Quick copy change as per the comment in the issue

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/7322
Tests / QA Steps
Just test on Web is fine

Follow https://stackoverflow.com/c/expensify/questions/342 to add a PENDING bank account

When you get the PENDING state, verify that the title says "Test Transactions"

Add another VBA that needs to be verified and is in the VERIFYING state

When you get to the validationStep, verify that the title says "Validate Bank Account"

Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @ctkochan22 in version: 1.1.33-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @sketchydroide in version: 1.1.34-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Persist Accepted but Reversible Blocks

When a node shuts down the most recent 240 blocks (or more) are lost. This normally isn't a problem because the node will sync those blocks from other peers when it reboots; however, there exists one kind of crash where all nodes deterministically crash at the same time due to a bug in block production. This may or may not take down all speculative validators as well.
In this event the producers would be unable to restart the chain without generating "byzantine proofs".
To resolve this, a new shared memory file (chainbase) will be created that will store all applied but reversible blocks.
Shutdown Modes:

Graceful - fork database is logged to disk and restored on load
Ungraceful - fork database is not logged to disk leaving the forkdb and shared-memory state inconsistent and forcing a "replay".  In theory all undo history could be popped until things are consistent.

Startup Modes

Replay - fork database is destroyed and block must resync the most recent 240 blocks from network
Resync - fork db & shared memory are gone and everything is downloaded fresh
Inconsistent - fork db is inconsistent with shared memory file

Getting around bugs
Sometimes a "bad block" introduces a bug and a node would like to startup without that block. This block could exist in either the fork database or the pending block cache. In some extreme cases (with byzantine faults) the block might exist in irreversible block log.
On startup nodes should be able to indicate "which block" they want to start on.

I just updated to the latest and got this:
3490925ms thread-0   controller.cpp:261            ~controller_impl     ] db.revision(): 1 head->block_num: 3 blog.read_head()->block_num(): 2
3490928ms thread-0   main.cpp:113                  main                 ] 10 assert_exception: Assert Exception
end && end->block_num() == head->block_num: fork database exists but reversible block database does not, replay blockchain
{"blog_head":2,"head":3}
thread-0  controller.cpp:239 init
{}
thread-0  chain_plugin.cpp:417 plugin_startup

@trigx300
Have you fixed it? I got the same error by upgrading and run the first three command of EOS wiki:
sudo ./eosio_build.sh
sudo make install
./nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin

And the message is:
1729673ms thread-0   chain_plugin.cpp:202          plugin_initialize    ] initializing chain plugin
1729695ms thread-0   block_log.cpp:123             open                 ] Log is nonempty
1729696ms thread-0   block_log.cpp:136             open                 ] my->head->block_num(): 1
1729696ms thread-0   block_log.cpp:142             open                 ] Index is nonempty
1729720ms thread-0   http_plugin.cpp:285           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
1729720ms thread-0   net_plugin.cpp:2827           plugin_initialize    ] Initialize net plugin
1729720ms thread-0   net_plugin.cpp:2848           plugin_initialize    ] host: <IP_ADDRESS> port: 9876
1729720ms thread-0   net_plugin.cpp:2920           plugin_initialize    ] my node_id is 8035193e4a3548ddfa10e6435896809db2c76e204fd1708678998c59cb185767
1729720ms thread-0   main.cpp:104                  main                 ] nodeos version 379cb1a9
1729720ms thread-0   main.cpp:105                  main                 ] eosio root is /home/forfrt/.local/share
1729721ms thread-0   fork_database.cpp:93          close                ] num_blocks_in_fork_db: 1
1729721ms thread-0   controller.cpp:261            ~controller_impl     ] db.revision(): 0 head->block_num: 1 blog.read_head()->block_num(): 1
1729724ms thread-0   main.cpp:113                  main                 ] 10 assert_exception: Assert Exception
db.revision() >= head->block_num: fork database is inconsistent with shared memory
    {"db":0,"head":1}
    thread-0  controller.cpp:243 init

    {}
    thread-0  chain_plugin.cpp:428 plugin_startup

I also tried to boot without eosio::chain_api_plugin and it gives this:
./nodeos -e -p eosio --plugin eosio::history_api_plugin

1747693ms thread-0   chain_plugin.cpp:202          plugin_initialize    ] initializing chain plugin
1747718ms thread-0   block_log.cpp:123             open                 ] Log is nonempty
1747718ms thread-0   block_log.cpp:136             open                 ] my->head->block_num(): 1
1747718ms thread-0   block_log.cpp:142             open                 ] Index is nonempty
1747742ms thread-0   http_plugin.cpp:285           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
1747742ms thread-0   net_plugin.cpp:2827           plugin_initialize    ] Initialize net plugin
1747742ms thread-0   net_plugin.cpp:2848           plugin_initialize    ] host: <IP_ADDRESS> port: 9876
1747742ms thread-0   net_plugin.cpp:2920           plugin_initialize    ] my node_id is 1a21bccfa7d98f52deb91279243c4a899a1ae944bcef8a7069c5954bb56dc82d
1747744ms thread-0   main.cpp:104                  main                 ] nodeos version 379cb1a9
1747744ms thread-0   main.cpp:105                  main                 ] eosio root is /home/forfrt/.local/share
1747746ms thread-0   fork_database.cpp:93          close                ] num_blocks_in_fork_db: 1
1747746ms thread-0   controller.cpp:261            ~controller_impl     ] db.revision(): 0 head->block_num: 1 blog.read_head()->block_num(): 1
1747752ms thread-0   main.cpp:113                  main                 ] 10 assert_exception: Assert Exception
db.revision() >= head->block_num: fork database is inconsistent with shared memory
    {"db":0,"head":1}
    thread-0  controller.cpp:243 init

    {}
    thread-0  chain_plugin.cpp:428 plugin_startup

I have excluded all environmental problem by reinstalling the image.
Any advices?

@forfrt
try nodeos --replay-blockchain

hi! 2018-10-11T09:22:45.332 thread-0   main.cpp:125                  main                 ] 3020000 fork_database_exception: Fork database exception
reversible block database is inconsistent with fork database, replay blockchain
{"head":574302,"unconfimed":358546}
thread-0  controller.cpp:303 init
{}
thread-0  chain_plugin.cpp:655 plugin_startup

{}
thread-0  chain_plugin.cpp:655 plugin_startup

any ideas

okey!!!! ./nodeos -e -p eosio --hard-replay-blockchain --delete-all-blocks --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin

lol))


KiJai, do you notice LTX Video?

it a 2b video model, I tested it, its i2v is about 10 times faster than cogvideo 5b with faster cache enabled, and the quality is better than cogvideo fun 2b, even better than cogvideo fun 5b.
on my 4060ti 16G, create a 576x1024, 25 frame, 30 steps, the time of whole process  is about 28 seconds, cogvideo 1.5 5b + faster cache needs more than 200 seconds.

I'm in the test group yes, it is fast and promising, can't agree with the quality being on par with 5b though, it's fine on some stuff but being smaller model it can't do everything as well (yet). What ultimately matters most is how it will be to further rain, LoRAs and control methods especially as they are the most interesting things we have available for CogVideoX.

Tried it too but found not so good. For i2v it probably produces static videos no matter what the prompt is, I think the cogvideox 2b i2v (not the fun version) dose better in i2v staff.

Just tried it. I can't get as much direction as I can with 1.5, but that doesn't mean necessary that the LTX is bad. It is new and it could probably be me not knowing how to prompt it.
What is important for me, (I'm talking about myself specifically and ONLY) is the models to be trained in low res footage, and get good results. I do max 213 frames in one run with a clean 4090 at 624x624, taking 17:50 minutes (no off-load) in 1.5. That's what can fit in a 4090. I up-scale with Topaz to whatever res I want. Below 624px 1.5 it just doesn't work.
Well, LTX beats that by FAR.
So, what remains is the quality, for which, I repeat, LTX is still new.
I'm a fan of whatever can do uncensored content open-source locally.

Tried it too but found not so good. For i2v it probably produces static videos no matter what the prompt is, I think the cogvideox 2b i2v (not the fun version) dose better in i2v task.

It has a relatively good effect on standing postures and sitting postures.

Just tried it. I can't get as much direction as I can with 1.5, but that doesn't mean necessary that the LTX is bad. It is new

CogVideo 1.5 is much better than LTX Video at present. but I feel  LTX is much better than cogvideo 2b fun, it is useful when I try to animate photo just for fun because it is so fast, happy to see that i2v could be so fast,This has made me have great hopes for AI videos.

Just tried it. I can't get as much direction as I can with 1.5, but that doesn't mean necessary that the LTX is bad. It is new

This has made me have great hopes for AI videos.

This, TOTALLY this is my feeling as well.
As a Msc. on multimedia holder I have one clean 4090 running cog 1.5 24/7 almost 3 weeks for my true wish for my life (participation on Short Film Festivals), and one clean 4090 for cg boring job (such as porn industry, and marketing companies in a country that has NO single idea on what AI can do -no antagonism) that is funding my wish expenses. Kijai and others I follow (I don't know if I can mention them here) are very important people for me.
And now comes LTX. I hope both uncensored models to be developed even further. And they will. And more new models will come.


integration_test iOS white screen

iOS integration_test white screen
I am following guide for integration_test ios device testing. But when I try to run the test on my iPhone with this command:
xcodebuild test-without-building -xctestrun "build/ios_integ/Build/Products/Runner_iphoneos15.4-arm64.xctestrun" -destination id=<YOUR_DEVICE_ID>

I see only the white screen and nothing happens.
But if in this step I remove build-for-testing, then it works.
pushd ios
xcodebuild -workspace Runner.xcworkspace -scheme Runner -config Flutter/Release.xcconfig -derivedDataPath $output -sdk iphoneos build-for-testing
popd

Is this some problem with build-for-testing or something wrong in project configurations?
Flutter doctor
[✓] Flutter (Channel stable, 2.8.1, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 2.8.1 at /Users/okryzhan/fvm/versions/2.8.1
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (5 months ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/okryzhan/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] VS Code (version 1.67.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.41.20220516

[✓] Connected device (5 available)
    ...

• No issues found!

Hi @SashaKryzh, Thanks for filing the issue. Does the test run when you run it via xcode

Run Product > Test to run the integration tests on your selected device.

Also, Could you please try running with the latest stable version of flutter?


Disabled months

When fromDate and toDate are within a year, months that aren't in rango are disabled from the selector
In the example, from is July 1st, 2016, and to is Feb 10, 2017

Also, added a demo site to test plugin

unable to merge.


Use a list of Hypothesis groups instead of just one

A single Hypothesis group is used to pull annotations. Maybe a user would want multiple for different subjects. These can then be used in the annotation template and in the hierarchy configuration.

Yes! +1 for this. Kagi'd it specifically and found this. Right now I will be hacking some CLI workarounds to do this -- each group in a different top-level folder, for example. Anyway this would be a most welcome feature. Also -- not just a list but an 'all' option -- that would be ideal.

Added in PR #101 - should already work with gooseberry config group as expected, but needs some testing and README updates

Incredible. So fast. Thank you!! I managed to clone, checkout, and build that version and ran it and the behaviour is exactly as expected, especially with the hierarchical ordering of group_name/title etc. Just brilliant. This saved me from a nutty workaround I had all planned: hit the API to get a list of groups, filter out 'Public', create a gooseberry config.toml for each... etc. etc. Thanks so much. Massively increases usability.


multi: fix typos

Fixes multiple typos across the codebase.

If anyone wants to take over and do the extra work, please, by all means.
If not, feel free to close the PR.
No hard feelings.


⚠ Bofrost.si has degraded performance

In 474742b, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 3360 ms

Resolved: Bofrost.si performance has improved in ac4d9b0 after 6 minutes.


Add Code of Conduct

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.
Please follow these instructions on how to add a Code of Conduct.
Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

Please assign me this taks. I would like to create this code of conduct file for this repository.

Hey@Vanshika-73, Sure, you can proceed with it.!
Ctrate a new branch, push the changes in that branch!
And feel free to give this Repository a STAR⭐ and follow back 😊.

@bishalde sure, then please officially assign this issue to me.

@bishalde sure, then please officially assign this issue to me.

Sure!


GLOP: NO OpenMP and Solver Output

What version of OR-tools and what language are you using?
Version: master
Language: C++
Which solver are you using (GLOP)
What operating system (Windows 10)
On implementation, multitreading does not seem to work in the binary version because OPENMP was not active when compiling the library for release.
Furthermore SolverOutput does not work either. Nothing comes back.

do you mean this lines ?
https://github.com/google/or-tools/blob/a0a56698ba8fd07b7f84aee4fc45d891a8cd9828/ortools/glop/reduced_costs.cc#L366-L408

We never compile with open mp.
We should just remove the code.

I renamed the issue.
What do you mean no solver output ? Can you send us a code ?

I think the problem was, that verbose flag was not seted propertly. Now I get get some output.


README.md: Only support two latest yocto releases

Signed-off-by: Therese Nordqvist<EMAIL_ADDRESS>

Pyro will instead be updated with this change by merging master into the branch.


Add Hacktoberfest Tag

hello there,
As I contributed in your repository and I got to know that this repository is not participating in Hacktoberfest.
So, can you please add hacktoberfest tag in your repo here ⬇

Hi @kishanrajput23, will be adding the hacktoberfest-accepted label to your PR.
Thank you


Update 'samples' link to 'samples' folder

The original samples link pointed to the (now) out of date examples for version 0.8 of this gem. I lost a few hours wondering why things were not working.
Hoping to save someone else the time I lost (and reap the karmic bounty thereof).

I signed it!

Fixes #362


Edit request 15315

Copy edit complete - needs review

Made changes in the public repo--moved changes to the private repo and closed this request

Made changes in the public repo--moved changes to the private repo and closed this request


IOS respond SMS permission denied

IOS respond SMS permission denied. Is this library working with Iphone ?

Now It's only support android


Fixes 5058: separate set cancel from set cancel_attempted

Summary
The "template not found" error is still showing up because of an edge case where a task is failed before it is canceled
I missed this case in the discussion here. Bryttanie had it right. :)
Testing steps
I could not reproduce this locally, but the unit test is able to test this scenario
To reproduce this locally, you could try running the following as a script, while also modifying that update-template-content task to fail. But this did not work for me.
UUID=$(curl -s -X POST --location "http://localhost:8000/api/content-sources/v1.0/templates/"     -H "x-rh-identity: eyJpZGVudGl0eSI6eyJvcmdfaWQiOiIxNzc5MTU2MCIsICJ0eXBlIjoiVXNlciIsInVzZXIiOnsidXNlcm5hbWUiOiJzbmFwVXNlciJ9LCJhY2NvdW50X251bWJlciI6IjE3NzkxNTYwIiwiaW50ZXJuYWwiOnsib3JnX2lkIjoiMTc3OTE1NjAifX19Cg=="     -H "Content-Type: application/json"     -d "{
          \"name\":\"test-$RANDOM\",
          \"arch\": \"x86_64\",
          \"version\": \"8\",
          \"repository_uuids\": [\"917abddc-0745-4752-a100-ec147c7ee34b\"],
          \"date\": \"2024-08-09T14:04:05Z\"
        }"  | jq -r .uuid)

curl -s -X DELETE --location "http://localhost:8000/api/content-sources/v1.0/templates/$UUID"     -H "x-rh-identity: eyJpZGVudGl0eSI6eyJvcmdfaWQiOiIxNzc5MTU2MCIsICJ0eXBlIjoiVXNlciIsInVzZXIiOnsidXNlcm5hbWUiOiJzbmFwVXNlciJ9LCJhY2NvdW50X251bWJlciI6IjE3NzkxNTYwIiwiaW50ZXJuYWwiOnsib3JnX2lkIjoiMTc3OTE1NjAifX19Cg=="

https://issues.redhat.com/browse/HMS-5058


Missing manage relations form

Latest wordpress and latest WooCommerce-Salesforce-integration plugin.
The application is connected to Salesforce, but the relationship management form does not appear.

@code2prog do you have any entry in the error log?

@matejbasic I do not see any errors in the php logs and the JS console in the browser

@matejbasic  I'm seeing a similar situation; signed up for Salesforce, have latest WP, have WC 3.3.x; after setting up the latest version of the WC-Salesforce-integration plugin, activating it, setting up the Salesforce app (and waiting), and then doing the initial connection, I get redirected back to the settings page with no relationships showing.  No error message that I saw either.  What's a good way to debug this please?  This plugin looks great, hoping to actually enjoy it soon, thanks!

Update: tried everything again, making a new Salesforce App, entering the new Consumer key and secret, granting approval again; initially I saw the same behavior: redirected back to the Settings screen, didn't see any relations.  Without changing anything I tried clicking "Save changes" and after that, the relationships showed up.  However, that brought another set of problems, so I'll open a new issue about those...

After one hour of debugging...
I figured out the problem, when encrypting the token the final token returned by the Encryption method is empty and then the option is not saved in the database or saved but empty.
So when you make the calls to display the relationships the token is not there and the form will not be displayed.
File: WooCommerce-Salesforce-integration-master / includes / controllers / core-class-nwsi-salesforce-token-manager.php
Functions: load_access_token (), save_access_token (), load_refresh_token (), save_refresh_token ()

Was anyone able to get this working?
Many thanks

Hi,
I'd like to know if this plugin is still in dev.
I get the same problem: manage relations form and no error even after a fresh installation of the plugin.
Thanks


A "do it now or do it later" macro

Thinking about the format macro.
We already have a ticket #183 to improve the macro using the (emerging) built-in macro system. But I just thought of another thing.
Looking at how the macro is used at the end of the file:
say( format("{0}{1}{0}", ["abra", "cad"]) );        # abracadabra
say( format("foo{0}bar", ["{1}"]) );                # foo{1}bar ({} things can occur in the arguments)

Those are all constant strings and arrays of strings going into the macro. If it could only detect that somehow, and run the quasi code at macro invocation time, it could return (a Qtree of) the constant result.
What would the code doing that computation look like? Why, it'd be the quasi, but without the quasi:
return replaceAll(fmt, sub transform(arg) {
    return args[+arg];
});

(Here assuming fmt contains the format string (not its Qtree) and args contains the array of format arguments.)
That code is much easier to read, too. No unquotes.
Because we don't like writing duplicated code, the above "direct" code ought to be able to run either directly at macro time, when possible, or "inject itself" as the current quasi implementation does and run at runtime, when necessary.
I'm not firing at 100% right now, but I think this macro streamline could do that:
return streamline(quasi {
    replaceAll({{{fmt}}}, sub transform(arg) {
        return {{{args}}}[+arg];
    });
});

All it'd need to do was to recognize that the unquotes it just filled in were constant/literal values, and so it has enough to run the results of the quasi now, right here in the macro; it runs them, gets a string back, and turns that back into a Qtree. Maybe?
Streamline would need to intercept the normal quasi/unquote templating process in order to check all the unquotes. So it's definitely a macro. But can it do that? We just said that a quasi is not a Qtree fragment, it's a function, which indicates it's to some extent opaque. But... I don't think it's unreasonable to still expose (Qtree fragments for) the code in the unquotes. Those evaluate in the context of the macro, not the quasi, after all. They're more like arguments to the quasi than an actual part of it.
So, I think it all works out. In fact, I'm glad I thought of this use case, because it shows a bit more what we expect of Q::Term::Quasi also; in this case we expect to be able to iterate over the unquotes so that we can get at their contents and evaluate them.
Here's to more macros for macro authors! 🍺

Even better: since the format string is known, you can optimize it even if not all other arguments are known :).

Huh! Yes — fmt is in some sense more "stable" or long-lived than args. Maybe there's some way to formulate this pattern so that we can separately streamline them, getting either of the following three situations:

fmt and args both dynamic
fmt constant, args dynamic
fmt and args both constant

Wondering whether annotations might not capture this better, either on the macro parameters or on the macro itself. Fuzzy on the details.

Suddenly I'm thinking that this might be much better handled by the compiler itself. Maybe we're needlessly adding hints to the compiler here, like register in C?

...Yep.
Going to close this one, as I suspect it'll get stuck between a "we have more interesting low-hanging fruit to pick" rock and an "a sufficiently savvy compiler should be able to already do this without a hint" hard place.
Still an interesting/worthwhile idea, though, AFAICS.


Delete pods and lease using etcd container

As of now when user consume the bundle to provision the cluster, old data around pods and lease is consumed and timestamp for those pods are also around same time when we first provisioned this cluster. This PR try to use etcd image to run etcd server using same db which created by the cluster  and uses etcdctl command to delete the pods and lease details. It will help to make sure every pods comes up in clean state.

/retest

/retest

/cherry-pick release-4.17

/cherry-pick release-4.16