Add --no-banner option hiding CLI version output

When using the pre-commit hook and passing multiple files, the output becomes harder to read than necessary when then banner is displayed for each file processed.
Example of existing output
❯ pre-commit run -a
markdownlint-cli2........................................................Failed
- hook id: markdownlint-cli2
- exit code: 1

markdownlint-cli2 v0.12.1 (markdownlint v0.33.0)
markdownlint-cli2 v0.12.1 (markdownlint v0.33.0)
markdownlint-cli2 v0.12.1 (markdownlint v0.33.0)
doc1.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "Not a title"]
doc2.md:127 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
markdownlint-cli2 v0.12.1 (markdownlint v0.33.0)
doc3:35 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

To limit the noise when running the hook we also run with:
{
  "noProgress": true,
  "showFound": false
}

Output with this PR, passing the --no-banner option:
❯ pre-commit run -a
markdownlint-cli2........................................................Failed
- hook id: markdownlint-cli2
- exit code: 1

doc3.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "Not a title"]
doc3.md:127 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc4:35 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

Would it make sense to make this the new default behaviour?

This project has a strong preference for configuration file settings over command line parameters (except where necessary), so were we to move forward with this, I would want to see it as a setting instead.
FYI, you do not need to set showFound (above) when noProgress is true.
But my main question is why your pre-commit hook is invoking this tool multiple times instead of passing it a single list of files. That is the common behavior and results in just a single banner.
FYI, the banner is very useful for troubleshooting because it makes clear what version of CLI2 and markdownlint are being used and people are sometimes unsure or unclear about that.

Thank you for taking the time to review and answers in such detail!

This project has a strong preference for configuration file settings over command line parameters (except where necessary), so were we to move forward with this, I would want to see it as a setting instead.

I started out with adding it as a configuration option, but then I saw that the logging happened before the config parsing was finished. Would you prefer if I changed it to a config option noBanner and moved the banner logging after config parsing is done then?

FYI, you do not need to set showFound (above) when noProgress is true.

Ah! I'll remove that from the test setup

But my main question is why your pre-commit hook is invoking this tool multiple times instead of passing it a single list of files. That is the common behavior and results in just a single banner.

I'm not sure why, though it happens consistently when running with pre-commit run -a at least. I'll double check if I'm using the hook or pre-commit wrong.

FYI, the banner is very useful for troubleshooting because it makes clear what version of CLI2 and markdownlint are being used and people are sometimes unsure or unclear about that.

I see your point about accurate error reporting and I opted to make the option default false to not change existing behaviour. I would argue that it's hurting the UX for regular CLI users though.

I am OK with the idea of adding this as a configuration parameter, but I have some specific thoughts about how to do it. Since I just published a new version of the library, CLI2 is my current project and I can make this change if you don’t want or won’t be able to do so in the next few days.
My thinking is to make the banner string a file-level constant and move the logMessage of it down to the first opportunity after getBaseOptions (as you point out). A new “noBanner“ property should be supported to suppress the banner at that time. I think that will work for most cases, but not when an exception comes out of readOptionsOrConfig or getBaseOptions. To handle that, I think a try/finally will be needed to wrap that small section of the code (lines 940-959) and output the banner in the finally. If the base configuration failed to load, output the banner anyway. I don’t like that this scoping breaks a couple of constant variables, but I don’t see a cleaner way from reading the code on my phone right now. The showHelp method should display the banner unconditionally.
With these changes, all existing test cases should pass unaltered and only the new test cases for this setting should be needed.
Let me know what you think.

Thank you for taking the time <3 The approach you are describing sounds good. I don't have much time to work on this, so if you have a plan, go for it!


Document '.tesselignore' dotfile

Similar to npm, the t2-cli looks for a .tesselignore dotfile to use in blacklisting files being sent over to Tessel 2 when pushing/running code. Reference
This should be documented in the Tessel docs, probably under the Tessel 2 CLI page.

Moved to https://github.com/tessel/t2-docs/issues/32


Let zipTree() and tarTree() be available on injected service

to create read-only archive FileTree instances where the Project isn't available.
See https://github.com/gradle/gradle/issues/13277

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFN

OK, I've already cancelled the old build and triggered a new ReadyForNightly build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


Do we want to set the precedent that every Lab Director will respond to GitHub mentions?

From @jonleung on September 20, 2015 2:23
This means that we need to set the precedent that Lab Directors will check GitHub notifications regularly.
I think that this will make it a lot easier to:

get pull requests merged in (because discussion can happen much more quickly)
allow Lab Directors to have discussions in comments on pull requests for case studies
celebrate when people submit a pull request in the pull request itself

Thoughts @hellyeah @zachlatta @MaxWofford @xeonjake @paked @Bogidon?
Copied from original issue: hackedu/hackedu#231

From @paked on September 20, 2015 13:30
GitHub's notification UI does not make this task very easy IMO. What is the stance on using external software?

From @Bogidon on September 20, 2015 18:36
Recently I've been getting most GitHub notifications over email and they don't even show up at https://github.com/notifications (like the one for this issue). Other than having issues receiving the notifications, I like the GitHub issue/PR system and think it would benefit the Labs program to encourage it more.

From @xeonjake on September 20, 2015 19:2
Github on Android crashes alot for me, and also email doesn't always give me the full conversation. Any suggestions?

From @paked on September 20, 2015 21:28
Pinging @zachlatta because he mentioned he had a good workflow set out when we hung out last.

Yeah, so couple things about GitHub notifications:

If you view a notification in your email, it's removed from the
notification center on GitHub's website
If you view a notification in the web interface before they send you an
email notification (there's a tiny delay), they don't send the email
notification.

I personally manage my GitHub notifications from email and use a slightly
modified version of https://github.com/mastahyeti/OctoGAS to apply relevant
tags to notifications.
On Sun, Sep 20, 2015 at 2:28 PM, Harrison Shoebridge <
<EMAIL_ADDRESS>wrote:

Pinging @zachlatta https://github.com/zachlatta because he mentioned he
had a good workflow set out.
—
Reply to this email directly or view it on GitHub
https://github.com/hackedu/hackedu/issues/231#issuecomment-141835885.

--
Zach Latta
hackEDU |<EMAIL_ADDRESS>

@hackclub/staff thoughts on closing this?

@zachlatta Seconded


issue #10

Create README to report to report changes and improvements made

All the information about the issues we have made and the improvements we have added, we hope you like them


What's your intent?

What would be your reasoning for copying the code, instead of creating a fork?

@BlurryRoots Hi, sorry for the misleading here. I mainly used for learning purpose, and fixed some install problems to met my requirements, I think this is not good for sending a pr to u. Although I would very like to contribute to you if you like.


Constants set from C gets incorrect top bits (in 32bit)

    mrb_define_const(ruby, ruby->kernel_module, "A0", mrb_fixnum_value(-2000000000));
    mrb_define_const(ruby, ruby->kernel_module, "B0", mrb_fixnum_value(0x7fffffff));
    mrb_load_string(ruby, "module Kernel ; A1 = -2000000000 ; B1 = 0x7fffffff ; end");
    mrb_load_string(ruby, "p A0 ; p B0 ; p A1 ; p B1");

outputs
147483648
-1
-2000000000
2147483647

The last two (set from ruby) are correct, the top two (set from C) are incorrect.
Could there be some bitwise operations happening that depends on int (or related types) being 64 bit ? Like shifting outside the 32bit range ?

I think you will get the expected result if you use mrb_int_value instead of mrb_fixnum_value.
These values can be represented as integers, but in the case of 32-bit word-boxing they cannot be represented as fixnums (immediate values), so you must use mrb_int_value.

Actually fixnums and integers are treated the same in mruby
#define SET_INT_VALUE(mrb,r,n) BOXNIX_SET_VALUE(r, MRB_TT_INTEGER, value.i, (n))
#define SET_FIXNUM_VALUE(r,n) BOXNIX_SET_VALUE(r, MRB_TT_INTEGER, value.i, (n))

MRB_INLINE mrb_value mrb_int_value(struct mrb_state *mrb, mrb_int i)
{
  mrb_value v;
  SET_INT_VALUE(mrb, v, i);
  return v;
}

MRB_INLINE mrb_value mrb_fixnum_value(mrb_int i)
{
  mrb_value v;
  SET_FIXNUM_VALUE(v, i);
  return v;
}

The implementation of SET_INT_VALUE and SET_FIXNUM_VALUE is different because wrod boxing is enabled by default unless you specify boxing configuration explicitly.
https://github.com/mruby/mruby/blob/07c847027875a955ba64d3c84f8f456e96155b31/include/mruby/boxing_word.h#L180-L181

Ah, I was looking at the wrong implementation. Thanks!
... but what is difference between fixnum and integer then?

Fixnums are integers boxed in mrb_value (31bit width on Word Boxing). Integers are .. integers. Some integers are inlined fixnums, some are allocated in the GC-managed heaps.


NIFI-10550 Fixing SSH Context Service validation for NifiRegistryFlowRegistryClient

NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

NIFI-10550

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[x] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks @simonbence good catch. Now that the UI has been integrated I can easily verify that this fixes the issue. +1 will merge.


Question: can use vue-concurrency with android app?

I am using capacitor to create an android app. In debug mode everything works, but the release app only gives a white screen.
white screen:
const task = useTask(function* () {
  yield timeout(700)
})

I don't see a reason why this would break. I'd guess capacitor still use a webview right? So it uses android chrome under the hood. It should have support for generators.


feature: state backend telemetry

Related to discussion in https://github.com/meltano/squared/issues/115
We should have an attribute or event that gets fired to Snowplow so we can understand if a particular execution is using a state backend i.e. sqlite/postgres/S3/GCP/etc. Right now we dont have a way of knowing this.

@cjohnhanson - Do we sent any events when the verb of getting, setting, listing states is performed? Should we add a new event for this?  For instance, we could trigger an event when state is set, which presumably would run during meltano state set as well as during meltano elt and other ways that el blocks are executed.
Alternatively, we could keep all of the existing events and add a ELStateContext to existing telemetry events that specifically leverage state.


Simplify signature of Viewport::push_input

This patch simplifies the signature of Viewport::push_input and the function itself.
This got introduced in 8e6960a69e0202cb1e6f3b3dc9f9bb34e1c1d889 to allow sending InputEventAction events with local coords in scene/2d/touch_screen_button.cpp
However these events don't have positions. This means, that handling local coordinates was not a required use case in the first place.

Could be useful having this functionality. Closing this.


756 log error info 3

Q
A

Branch
7.1.x

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed issues
chameleon-system/chameleon-system#756

License
MIT

There are conflicts now. I will happily merge when they are resolved.


nan with numfmt with vdev's

Greetings,
I've been successfully working with the configs from 12eecbfea8288c252c9d5a2c4f5e3cf1b46594f4.
Adding a new host with ZFS. Decided to grab the latest template and config file. I was getting errors in the vdev data so I cranked the logging.
The command on the old host returned a command that looked something like this: /sbin/zpool status | grep "sda" | awk '{ print $3 }'which returned 0.
The command on the new host returned a command that looked something like this:  /sbin/zpool status | grep "sda" | awk '{ print $3 }' | numfmt --from=si which returned 'nan'
It looks like numfmt returns nan anytime I pass it a 0. eg: echo 0 | numfmt --from=si or even echo 0 | numfmt
I think I get the point of converting the numbers when it returns something like 1M, but before I put something that catches nan to return 0 I thought I would ask if anyone else is seeing this issue. For the moment I'm just using the old config file and it seems to work.
Thoughts? Thanks!

Dratz.....
So I can replicate this on every version of RHEL 7.9 with coreutils-8.22-24.el7_9.2.x86_64 (which is the latest and all my boxes are updated).
I can not replicate this on any Ubuntu 20.04 (coreutils 8.30-3ubuntu2), Debian Buster (coreutils 8.30), nor RHEL 8 (coreutils-8.30-8.el8.x86_64). Unfortunately, I don't have access to anything else. It's either RHEL 7.9 or coreutils 8.30. :laughing:
So instead of trying to write weird code to support all of it, my suggestion is to just put a note in the README for those of us still stuck on RHEL7 for a while.

@cstackpole thank you for the bug report, I'm not sure how to handle this yet, maybe an if will do the job there.
The absence of the -p flag on old versions of the zpool command is definitively bothersome :-/

Did a lot of digging on this. Found that I could replicate this in some situations but not all. Finally reached out for help and it was pointed out to me that there was a bug in RHEL glibc that caused the issue. This fix is applied to the 7.9 hosts that work...and it fails on the 7.9 hosts that don't have this fix yet.
So I need to go on a patching spree (glibc is blocked from auto updates until we get to our rolling maintenance windows).
Should anyone else run into this issue, you need glibc-2.17-323.el7_9 or better.
This is not an issue for this project so I'm closing this. Thanks @AceSlash for your work on this Zabbix template. It is much appreciated.

@cstackpole : thank you for your deep analysis, I was having trouble to reproduce it, now I understand why :-)


cmd interface: train command should not fail if data folder contains more than train files

Currently, the command line interface fails to train the nlu or core model, if the data folder contains more than the expected training file.
Example:
Data folder contains stories.md and nlu.md and you execute the command rasa nlu train. The execution will fail with the following error:
ValueError: Unknown data format for file data/stories.md

If you run rasa core train, the execution fails with
TypeError: expected str, bytes or os.PathLike object, not NoneType

Current solution:
The data folder should contain only the training file you need to train your model. E.g. if you want to run rasa train nlu, the data folder should just contain nlu.md.
What needs to be done:
Ignore files in the data folder if they are not in the expected format, so that you don't have to move files before training any model.

@erohmensing Your comment https://github.com/RasaHQ/rasa/issues/3272#issuecomment-486993949 is a duplicate of this issue, I belief. I started looking into this today and it does not seem to be that trivial as you might think.
We already validate the training data when training an nlu model. This can be easily adapted to skip invalid files. However, for core models such a validation does not exist. And looking into the data, I'm also not sure, how you can say a nlu.md file is not a valid stories.md file as the syntax itself is valid. Do you have any ideas on how to recognize a nlu.md file when looking for stories.md files?

The reason it breaks on train core and train nlu but not train is because train always trains core and nlu in temporary directories in which it's only copied over the relevant files. Is there any reason we dont want to do this in core and nlu by default? I think this issue could be fixed in like 2 lines of code actually.

Not that I'm aware of. But how would you detect "relevant" files? As the files are not always named nlu.md and stories.md you need to check the content to see, if this file is a valid training data file or not. But maybe I'm missing something... Please go ahead if you already have a simple solution in mind.

the logic is already there because rasa train does it -- it basically pulls training data files, checks which are nlu, and then puts what's left in stories. check out my branch
https://github.com/RasaHQ/rasa/tree/data-files


Add more coverage

Finally learned what coverage was, ha. Messed around with everything that wouldn't get a merge conflict from one of my other PRs and wasn't too difficult (I believe the fs code was the only one I excluded for that reason).
I want 100% coverage!

Coverage increased (+1.7%) to 97.11% when pulling bd90b25d26506e04cdea2e01534927aa69fce2c2 on Kampfkarren:coverage2 into 4b36aa7ff3ef87157447cc36a4d895ee5762586e on LPGhatguy:master.

@LPGhatguy Fixed that and every other PR I made. I have no idea what Travis is taking so long.

That's what I'm waiting on, I'll check back in a few minutes and restart the builds if they haven't started by then.

An hour goes by and Travis doesn't even look like it has started, very strange...

They're aware of the issue and things should resume normally soon:
https://www.traviscistatus.com/incidents/kfgyk0ygvt65

@LPGhatguy Travis is up now


Mark down - #mention in multiline code block is not consistent in expense preview and thread

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.70-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Send a multiline code block text containing a #mention in the second line

hello
#bye

Note that the #mention is in monospace font
Submit an expense containing the same text in Step 2
Note that in 1:1 DM, the #mention is not in monospace font
Go to transaction thread
Note that #mention is in monospace font but highlighted in the description row

Expected Result:
#mention in multiline code block should be in monospace font and should not be highlighted in expense preview
Actual Result:
In Step 5, #mention in multiline code block is not in monospace font in expense preview in the main chat
In Step 7, #mention in multiline code block is highlighted in description row in transaction thread
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/33995ccd-d04f-430c-a46e-5d857d2af17e
View all open jobs on GitHub

@joekaufmanexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
The room mentioned is rendered as mention inside codeblock in money request description, but not in the chat message.
What is the root cause of that problem?
The regex for room mention currently doesn't prevent to be converted into room mention when inside a code block. When we send a message with a room mention inside a codeblock, you can see it's rendered as a mention. If the room mention doesn't exist, then the BE will return the message without the mention. If the room exists, then the mention stays.
What changes do you think we should make in order to solve the problem?

We should prevent the text to be converted into room mention if it's inside a codeblock. We can follow the regex from other mention that is by adding
(?!((?:(?!<a).)+)?<\\/a>|[^<]*(<\\/pre>|<\\/code>))

to the end of the regex. This will prevent the room mention to be rendered inside a link, code block, and inline code block.

going to review this morning

I can't imagine it's going to be common that many/any customer try and put a multi-line code block as the description for an expense. I'm inclined to say we should do nothing now, and see if any actual customers experience this before deciding to do anything. Closing.

Is the example your citing in a regular message, rather than a description of an expense?

Do we think it'll be common that many/anyone will do that? I agree in an ideal world it'd be consistent, but I'm still not sure it's worth prioritizing this right now.

I'm not sure if it's a common thing to do (putting a "hashtag" inside a code block), but I think it's a common expectation that text inside a code block won't be converted to a markdown.

I actually can't reproduce this with regular messages on my end at all

@joekaufmanexpensify did you send the message in a policy room? Room mention only works in a policy room.
https://github.com/Expensify/App/assets/50919443/06435742-08e3-48a2-b012-48312610cd91

@joekaufmanexpensify have you retested it?

Yes, I did. I do see it in a workspace room. But only if you do a multi-line code block where the room name is second. If It's first, the multi-line code block works correctly. I'm still not really convinced this is worth prioritizing, or that many/anyone will experience this. I feel like it might be good to wait and see if there is any customer impact before deciding to prioritize this.


Deploy v0.9.6 to v0.9.7 to DEV without loosing blockchain contents

Pre-requirements: the tag is created and pushed into master. master points to v0.9.7. blockchain-hf-workspace is running on DEV.
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ docker-compose down --rmi local
WARNING: The SIMPLE variable is not set. Defaulting to a blank string.
WARNING: The DOMAIN variable is not set. Defaulting to a blank string.
WARNING: The PROTOCOL variable is not set. Defaulting to a blank string.
WARNING: The SWAGGER variable is not set. Defaulting to a blank string.
Stopping pha-zuellig       ... done
Stopping pha1              ... done
Stopping pha2              ... done
Stopping whs2              ... done
Stopping whs-takeda        ... done
Stopping whs1              ... done
Stopping mah-pfizer        ... done
Stopping mah-bayer         ... done
Stopping mah-sanofi        ... done
Stopping mah-novo-nordisk  ... done
Stopping mah-takeda        ... done
Stopping mah-msd           ... done
Stopping mah-gsk           ... done
Stopping mah-roche         ... done
Stopping fgt-workspace     ... done
Stopping traefik-logrotate ... done
Stopping traefik           ... done
Removing pha-zuellig       ... done
Removing pha1              ... done
Removing pha2              ... done
Removing whs2              ... done
Removing whs-takeda        ... done
Removing whs1              ... done
Removing mah-pfizer        ... done
Removing mah-bayer         ... done
Removing mah-sanofi        ... done
Removing mah-novo-nordisk  ... done
Removing mah-takeda        ... done
Removing mah-msd           ... done
Removing mah-gsk           ... done
Removing mah-roche         ... done
Removing fgt-workspace     ... done
Removing traefik-logrotate ... done
Removing traefik           ... done
Removing network traceability-net
Removing network api_default
Removing image api_fgt-workspace
Removing image api_mah-roche
Removing image api_mah-bayer
Removing image api_mah-gsk
Removing image api_mah-msd
Removing image api_mah-novo-nordisk
Removing image api_mah-pfizer
Removing image api_mah-takeda
Removing image api_mah-sanofi
Removing image api_whs-1
Removing image api_whs-2
Removing image api_whs-takeda
Removing image api_pha-1
Removing image api_pha-2
Removing image api_pha-zuellig

pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ git pull

pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ ./bootCompose.sh eth-dev

bootCompose is failing in building fgt-workspace:
pharmaledger@fgt-dev-pl:~$ docker logs --timestamps -f fgt-workspace 2>&1 | less

2022-06-23T09:37:13.055343735Z rm: can't remove 'apihub-root/external-volume/config/domains/traceability.json': Permission denied
2022-06-23T09:37:13.055379845Z rm: can't remove 'apihub-root/external-volume/config/domains/predefined.json': Permission denied
2022-06-23T09:37:13.055382685Z rm: can't remove 'apihub-root/external-volume/config/domains/epi.json': Permission denied
2022-06-23T09:37:13.055384765Z rm: can't remove 'apihub-root/external-volume/config/domains/vault.json': Permission denied
2022-06-23T09:37:13.055386805Z rm: can't remove 'apihub-root/external-volume/config/domains/default.json': Permission denied
2022-06-23T09:37:13.055388805Z rm: can't remove 'apihub-root/external-volume/config/apihub.json': Permission denied
2022-06-23T09:37:13.055390755Z rm: can't remove 'apihub-root/external-volume/config/bdns.hosts': Permission denied
2022-06-23T09:37:13.055737408Z cp: can't create directory 'apihub-root/external-volume/config/config': Permission denied
2022-06-23T09:37:13.361406464Z
2022-06-23T09:37:13.361423334Z ><EMAIL_ADDRESS>switch-to-test-chain
2022-06-23T09:37:13.361439934Z > node ./node_modules/octopus/scripts/setEnv --file=../../../env.json "node ./node_modules/octopus/scripts/run switch-
to-test-chain"
2022-06-23T09:37:13.361443054Z
2022-06-23T09:37:13.396593928Z Running in STABLE (FREEZED) mode
2022-06-23T09:37:13.397976999Z Environment updated accordingly to env file passed as argument.
2022-06-23T09:37:13.398071190Z Preparing to execute cmd node ./node_modules/octopus/scripts/run switch-to-test-chain
2022-06-23T09:37:13.432212896Z Looking for configuration file at path /fgt-workspace/octopus-freeze.json
2022-06-23T09:37:13.449083738Z Action buildWebCardinalComponents was registered.
2022-06-23T09:37:13.449646782Z [Octopus] Start checking switch-to-test-chain...
2022-06-23T09:37:13.449654532Z [Octopus] Found 1 switch-to-test-chain...
2022-06-23T09:37:13.449733573Z [Octopus] Running tasks for: [0] Switch apihub configs to a local test blockchain. Apihub needs restart.
2022-06-23T09:37:13.450083036Z Start copying ./blockchain-patch/apply/external-volume to folder ./apihub-root/external-volume
2022-06-23T09:37:13.455920871Z /fgt-workspace/node_modules/octopus/scripts/run.js:22
2022-06-23T09:37:13.455933211Z     throw err;
2022-06-23T09:37:13.455935561Z     ^
2022-06-23T09:37:13.455937481Z
2022-06-23T09:37:13.455939421Z Error: EACCES: permission denied, open '/fgt-workspace/apihub-root/external-volume/config/domains/traceability.json'
2022-06-23T09:37:13.455941811Z     at Object.openSync (node:fs:585:3)
2022-06-23T09:37:13.455943721Z     at Object.writeFileSync (node:fs:2157:35)
2022-06-23T09:37:13.455945601Z     at __copyFile (/fgt-workspace/node_modules/octopus/lib/utils/FSExtension.js:168:16)
2022-06-23T09:37:13.455947611Z     at __copyDir (/fgt-workspace/node_modules/octopus/lib/utils/FSExtension.js:135:17)
2022-06-23T09:37:13.455949531Z     at __copyDir (/fgt-workspace/node_modules/octopus/lib/utils/FSExtension.js:130:17)
2022-06-23T09:37:13.455962051Z     at __copyDir (/fgt-workspace/node_modules/octopus/lib/utils/FSExtension.js:130:17)
2022-06-23T09:37:13.455964141Z     at Object.__copy [as copy] (/fgt-workspace/node_modules/octopus/lib/utils/FSExtension.js:89:17)
2022-06-23T09:37:13.455967611Z     at Object.ActionsRegistry.actions.copy (/fgt-workspace/node_modules/octopus/ActionsRegistry.js:701:19)
2022-06-23T09:37:13.455969611Z     at wrapper (/fgt-workspace/node_modules/octopus/ActionsRegistry.js:909:30)
2022-06-23T09:37:13.455971531Z     at __runAction (/fgt-workspace/node_modules/octopus/Runner.js:259:13) {
2022-06-23T09:37:13.455973401Z   errno: -13,
...

PS: Just a side note: Deployment of v0.9.7 on TST was done with external volume removal.
pharmaledger@fgt-tst-pl:~/fgt-workspace/docker/api$ docker-compose down -v --rmi local
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ ./bootCompose.sh tst

The permissions of the files on the external volume look like:
root@fgt-tst-pl:~# ls -l /var/lib/docker/volumes/api_*_vol/_data
/var/lib/docker/volumes/api_mah-bayer_vol/_data:
total 12
drwxr-xr-x 3 techsupport techsupport 4096 Jun 23 11:03 config
drwxr-xr-x 4 techsupport techsupport 4096 Jun 23 11:03 domains
-rw-r--r-- 1 techsupport root          57 Jun 23 10:50 read.me
...
root@fgt-tst-pl:~# ls -l /var/lib/docker/volumes/api_mah-bayer_vol/_data/domains/vault/anchors/
total 32
-rw-r--r-- 1 techsupport techsupport    85 Jun 23 11:03 7saRdSm81FqYLzhW8xB5TD77WKFiQBZVgs9tEZZJhC17TY6ri7uah4pnnJaHuekp6VMS9L1cDuSJGefugmhfd
...

Note that the read.me is from the root group, and not from the techsupport (gid=1000) group. But all child folders and child folder files have ownership techsupport:techsupport.
This is not the case in DEV due to the chown... But should only be a problem if the read.me needs to be changed by the container. Closing the issue anyway!


neolix canbus

add neolix edu car canbus module

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


not load resource configuration

Receive this error message when at first logon -- We could not load resource configuration. Refresh the page to try again, - no resource display either
sound like we are reaching to the maximum configuration at somewhere, do you know where I can change that configuration?  The error disappear If we filter and drop to just a few aws accounts.

Yes, this is a known issue due to the payload limitations of of the lambda function. We will be looking to implement pagination in an upcoming release to solve this. Unfortunately the only workaround currently is what you are doing by using the account filters to reduce the size of the payload coming from the backlog.
https://github.com/awslabs/aws-perspective/issues/27

Thanks for opening this issue @rsiripan
I intend to use #27 to track this issue and close this one. If we can be of more assistance, feel free to reopen it.

Thaks for the updated & looking forward to the next release..

Ray Siripan
Senior Cloud Solution Architect
Group IT
TUI Group
Wigmore House | Wigmore Lane | Luton | UK
Phone: +44 7786 004 052
Email: Ray.Siripan<EMAIL_ADDRESS>Website: http://www.tuigroup.comhttp://www.tuigroup.com/
LinkedIn: https://www.linkedin.com/company/tuigroup
Twitter: https://www.twitter.com/tuigroup
Chairman of the Supervisory Board: Dr. Dieter Zetsche | Executive Board: Friedrich Joussen (CEO), Birgit Conix, David Burling, Sebastian Ebel, Dr. Elke Eller, Frank Rosenberger | Company seat: Berlin/Hannover | Commercial register: Amtsgericht | Berlin-Charlottenburg HRB 321 | Hannover HRB 6580
[A close up of a sign  Description automatically generated]
[A close up of a sign  Description automatically generated]
[A close up of a sign  Description automatically generated]
[A close up of a sign  Description automatically generated]
[A close up of a sign  Description automatically generated]
[A picture containing drawing  Description automatically generated]
From: Scott Piper<EMAIL_ADDRESS>Reply to: awslabs/aws-perspective<EMAIL_ADDRESS>Date: Wednesday, 4 November 2020 at 17:21
To: awslabs/aws-perspective<EMAIL_ADDRESS>Cc: Ray Siripan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [awslabs/aws-perspective] not load resource configuration (#51)
Thanks for opening this issue @rsiripanhttps://github.com/rsiripan
I intend to use #27https://github.com/awslabs/aws-perspective/issues/27 to track this issue and close this one. If we can be of more assistance, feel free to reopen it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/awslabs/aws-perspective/issues/51#issuecomment-721865106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKQOV4ORXVJKGIEDOKZX7L3SOGEPTANCNFSM4SEOXT6Q.


Apprise version pinning

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
The docker image for v1 pins Apprise to v1.6. Is there a specific reason for pinning it? Could I happily install the latest (like the docker image for v2 does) without causing issues for UK?
📝 Error Message(s) or Log
N/A
🐻 Uptime-Kuma Version
1.23.15
💻 Operating System and Arch
Ubuntu 24.04 / Debian 12
🌐 Browser
Brave
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

Respectfully, this does not answer my question. If am not using Docker, is there any issue with using the latest Apprise with v1?


update changeSlide to preventDefault if target is a child of an a tag

update changeSlide to preventDefault even if target is a child of an <a> tag
bugged jsfiddle:

https://fiddle.jshell.net/localpcguy/vbyg5wxx/1/show/light/
http://jsfiddle.net/localpcguy/vbyg5wxx/1/

working jsfiddle:

https://fiddle.jshell.net/localpcguy/vbyg5wxx/2/show/light/
http://jsfiddle.net/localpcguy/vbyg5wxx/2/

Fixes #1508

I didn't know what minifier you tend to use, or I would have updated the .min.js file as well.
I did do just a tiny amount of cleanup in the same function, moving the if that checks for the 'li' into the switch/case statement since it was only needed for the 'index' case.

Updated Fiddles:
Bugged JSFiddle:
https://fiddle.jshell.net/localpcguy/vbyg5wxx/3/show/light/
original: http://jsfiddle.net/localpcguy/vbyg5wxx/3/
Fixed JSFiddle:
https://fiddle.jshell.net/localpcguy/vbyg5wxx/4/show/light/
original: http://jsfiddle.net/localpcguy/vbyg5wxx/4/


React Lamp

Create a genie lamp that's a react component

Very interested. Building a bitcoin trading platform which has quite a huge amount of UI elements.

If I have time, maybe I'll get to it, but I wouldn't be hopeful for it. A PR would be totally welcome :-) Thanks for expressing interest! Encourages me to work on it.


get_libfply.sh not working

Mirroring360 doesn't contain fply.dylib anymore.

Although (or since) I suspect Mirroring360 (like Reflector, AirServer, etc.) to not have legally acquired the obfuscated binary blob they share in the first place, I feel very uncomfortably publicly sharing my local copy.
Do you have proposals on how to handle this?
For the time being I suppose using fplyServer.py with @espes arm emulation is a way to try it.

The Wayback Machine at Internet Archive is your friend here.  :)


LED indicator

Is it possible to disable these?
Would like to reduce the power consumption when not powered from ac.

The current hardware version (PCB01a,PCB01b) cannot be off.


Another study question: bounds-check here not needed? Or forgotten?  =)

The lines with seemingly (I could be wrong, maybe it's pre-checked by caller that I've overlooked?) unguarded [1] indexing accesses:
https://github.com/cryptocode/bio/blob/15d16a39aa3ad8730926a31bc250ccba74d0cc41/src/intrinsics.zig#L535
https://github.com/cryptocode/bio/blob/15d16a39aa3ad8730926a31bc250ccba74d0cc41/src/intrinsics.zig#L538
https://github.com/cryptocode/bio/blob/15d16a39aa3ad8730926a31bc250ccba74d0cc41/src/intrinsics.zig#L548

Also, separate issue but no separate Issue — missing requireExactArgCount in callable? and opaque? — forgotten or by design?  =)
https://github.com/cryptocode/bio/blob/15d16a39aa3ad8730926a31bc250ccba74d0cc41/src/intrinsics.zig#L455C1-L470C1

Also, separate (maybe)issue but no separate Issue — missing requireExactArgCount

Yep, spot on. I'll fix those, thanks!
The quasiquote expansion is already rewritten in a VM branch so I'll skip those.


Configure libertem-server worker params from command line

Right now we require the user to go through a create/connect page before loading data in libertem-server.
I would argue that in most cases people immediately click 'Connect' without looking at the content. We could offer the ability to pre-configure the cluster from the launch command, e.g.:
libertem-server -c 8 -g 1

which would create an 8 cpu / 1 gpu cluster and put you immediately on the select data file browser page. It might even be worth it to just create a maximum-resource cluster by default, and the current behaviour with the configuration page  becomes an option, too (which is already what we do with a simple call to lt.Context()).
This could also extend to connecting to existing Dask clusters:
libertem-server --dask-scheduler <IP_ADDRESS>:8080

The goal would to reduce the typical time-to-analysis. If implemented in a certain way the cluster could still be loading / preloading at the same time the file browser page is loading in and becomes ready to use.

An additional feature here would be to actually expose the scheduler address when libertem-server creates a cluster, that way you have a one-command solution to set up a LiberTEM-configured cluster on a server somewhere, then connect to it remotely from another machine.

Agreed - defaulting to a max resource cluster is a good idea. We could then have a "reconfigure cluster" command in the status bar, to add/remove workers (which would in reality stand up a new cluster when applying).
With #1353 we should also have better defaults for the number of CUDA workers (and maybe detection of pinning via taskset or constrained docker CPU resources?), meaning one less reason to change the defaults.


Make Netatmo able to discover both Weather station and Health Coach

Description:
Netatmo is now able to discover both Weather Station and Health Coach devices at the same time.
Before it would only discover one of the types. If you had both types not all devices would be found.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Please do not force-push after a review, it makes the reviewer start from scratch.

Please do not force-push after a review, it makes the reviewer start from scratch.

Sorry, I was not aware of that.

Move the import back into a method, having it global will fail if REQUIREMENTS are not already installed.

Moved back again

Looks good 👍. Please also make a PR for the documentation, mentioning the new health_idx module name .

It now indeed discovers my Netatmo Weather station and associated modules, as well as one of my two Home Coaches. However ... only one of the two ...

@erikproper Please file a separate issue.

Will try ;-)
On Thu, 14 Mar 2019 at 09:17, Anders Melchiorsen<EMAIL_ADDRESS>wrote:

@erikproper https://github.com/erikproper Please file a separate issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/20274#issuecomment-472747261,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AELVlamZg06sgQVPj3wx6bCQ5L9uYo5aks5vWgV-gaJpZM4aJzf7
.


Webhook to create ticket in GitHub/ZenHub

Describe the issue
Somewhere in the onboarding process the incoming team fills out a form and data is captured about the team.  A webhook would trigger and generate an issue in the CPF repo.
Additional context

we have a bit of a balancing act around the private contents of the CRM vs the public aspect of the CPF repo issues

Definition of done

When a team is preparing for onboarding and they input their info
In the CRM we can have an approval step

a button that the PO or whoever could click to "approve" and create a ticket

Fields in the ticket

name of the team

a way to find the entry in the CRM (without a direct link or leaking private info)

no longer relevant because we will be using the registry


Not using _imshow_kwargs everywhere in plotting

https://github.com/aknierim/thesis_scripts/blob/244bf4b17aa53350e93ba090a8a9e4e723d75673/thesis_scripts/plotting/skyplots.py#L257
Could you pass the _imshow_kwargs here too? Would make comparison much easier when changing norms etc for I Q U V.

Thanks, I missed that. Will fix that


Use babel-jest instead of ts-jest

Why
ts-jest uses tsc to compile the source code before running the tests. As the project grows, it makes the tests slower and slower.
However, we don't really need to have type errors making the tests fail (in fact, it's even annoying for dev). There is a dedicated step for that in CI (tsc --noEmit) and our editor is generally configured to let us know when there is a type error.
Thus, we can ditch the type checking part and just compile the TS code into JS. This is what babel-jest does. Because it has less work to do, it is MUCH faster.
From my (quite performant) machine:

Before
After

The diff may be even bigger in watch mode. That should also make CI a bit faster 😉

Codecov Report

Merging #75 (6d636d7) into main (e5e4961) will decrease coverage by 1.35%.
The diff coverage is 96.21%.

@@            Coverage Diff             @@
##             main      #75      +/-   ##
==========================================
- Coverage   98.49%   97.13%   -1.36%
==========================================
  Files           8       12       +4
  Lines         332      454     +122
  Branches      102      158      +56
==========================================
+ Hits          327      441     +114
- Misses          5       11       +6
- Partials        0        2       +2

Impacted Files
Coverage Δ

src/core/generateZodSchema.ts
95.00% <92.00%> (-2.21%)
:arrow_down:

src/utils/resolveModules.ts
97.67% <97.67%> (ø)

src/core/generate.ts
100.00% <100.00%> (ø)

src/core/jsDocTags.ts
98.57% <100.00%> (-1.43%)
:arrow_down:

src/core/validateGeneratedTypes.ts
97.05% <100.00%> (-0.31%)
:arrow_down:

src/utils/getSimplifiedJsDocTags.ts
100.00% <100.00%> (ø)

src/utils/isNotNull.ts
100.00% <100.00%> (ø)

src/utils/resolveDefaultProperties.ts
100.00% <100.00%> (ø)

... and 6 more

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 cb1bf35...6d636d7. Read the comment docs.

P.S: IMO, the codecov reports are busted. No way this PR decreases code coverage 😆
I would get rid of codecov integration, it's not working well for TS projects in my experience (confirmed here).


[Suggestion] /ignore command in game.

What you want to be added?
Hi! I have another suggestion (Sorry for all the suggestions!) a command such as /ignore for players to use ingame or /dcdisable to not get relayed messages from the Discord if they wanted to disable it as some players may not like the spam if it is a heavily populated or talkative server such as mine.
I've had quite a few players request this.

Added in next update. Syntax: /discord ignore


feat(spanner): add CMEK samples

@GoogleCloudPlatform/php-admins Could you please review and merge this PR? :)


NuGet package failed to install

Testing Visual Studio 2017 15.7 Preview 3 release.
Getting an error message: "NuGet package failed to install" when trying to enable the "Enable Restore on Build" option (right-click on the libman.json file and click on the "Enable Restore on Build" option).
Any ideas why?

We are looking in this issue now. I will update you once it is fixed. Thanks for reporting!

I guess it wasn't published to NuGet yet at the time.
Looks like it is there now: Microsoft.Web.LibraryManager.Build 1.0.20
It's working now.
Thank you.

On my work PC the error was still happening. I tracked it down to Service Fabric registering a Machine-wide NuGet package source. I have actually uninstalled Service Fabric on this PC, but it kept the NuGet setting in Visual Studio for NuGet package sources. I unchecked the box and it fixed the problem on the work PC as well.
This is more of a Visual Studio or Service Fabrci bug. Needs to be passed along to the right team.

Closing since the LibraryManager package is now published.
@D3MaxT I think the issue in your latest comment is a known NuGet issue, but that would be the place to raise feedback for a change.


Administrative account only auditing small number of files

What sort of permissions does the account running the audit need to have over a folder in order for it to show up? I'm running it on an account that has org-wide managerial access but I'm only pulling maybe 8 out of over 100 folders.

The method used to grab all files from the root Drive folder is DriveApp.getFiles() which uses the default scopes as I was building/testing the script using a standard workspace account. I'm not exactly sure what kind of access permissions org-wide accounts have regarding sub-accounts, but I imagine at a minimum read-only access is available. You may want to try setting explicit scopes for the script in the manifest.json file, which you can do by following these steps:
https://developers.google.com/apps-script/concepts/scopes#setting_explicit_scopes
Here are the scopes you could paste into the array based on those allowed for the getFiles() method:
"https://www.googleapis.com/auth/drive.readonly"
"https://www.googleapis.com/auth/drive"


gazebo_video_monitor_plugins: 0.4.2-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository gazebo_video_monitor_plugins to 0.4.2-1:

upstream repository: https://github.com/nlamprian/gazebo_video_monitor_plugins.git
release repository: https://github.com/nlamprian/gazebo_video_monitor_plugins-release.git
distro file: noetic/distribution.yaml
bloom version: 0.9.8
previous version for package: 0.4.1-2

gazebo_video_monitor_plugins
* Enable C++14

holding for the upcoming Noetic sync


[WIP] Refactor model API for abstract parallelization

Closes #51
Important changes:

Removed RegressionModel subclass
BaseModel is now an abstract class (cannot be directly instantiated)
BaseModel has a create_regression method that behaves equivalently to the previous RegressionModel
Added two subclasses - TableModel and SingleFeatureModel for serial & parallel models respectively
Added a ModelIterator class
Changed behavior of specify_model to save params, coords, etc. as attributes.

Other parameters such as alr_params can be passed and will be saved in the self.specifications dict
This was done so we are not limited to ALR models in TableModel. Will likely need to update/decompose full_fit_to_inference in the future.

Yes, definitely save ilr for later. I think the more important thing for
this PR to try to nail down the naming scheme and avoid implementing road
blocks as highlighted above
On Sat, Jul 3, 2021 at 2:25 PM Gibs @.***> wrote:

@.**** commented on this pull request.
In birdman/model_base.py
https://github.com/gibsramen/BIRDMAn/pull/52#discussion_r663405394:

@@ -280,103 +208,69 @@ def to_inference_object(self) -> az.InferenceData:
args = {
k: self.specifications.get(k)
for k in ["params", "coords", "dims", "posterior_predictive",

                 "log_likelihood"]

                 "log_likelihood", "alr_params"]

Gotcha - yes I can see how this could get hairy fast...
Do you think we could save this for a different PR? There's probably some
clever inheritance stuff we could do (multiple-inheritance maybe?) but I'd
like to get this refactor implemented first.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gibsramen/BIRDMAn/pull/52#discussion_r663405394, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXLULNP7M3UEM2WULE3TV5W2VANCNFSM47VQA3UA
.

Thinking about this some more I'm not sure I fully understand the need to rename/create ALRModel. If we remove alr_params from TableModel.specifications isn't that sufficient? A CLRModel would be able to use the same inference conversion but specifying no fitted parameters are in ALR coordinates. (And ILRModel we can figure out later.)

Yes I think that’ll be the solution for now.
On Sat, Jul 3, 2021 at 3:31 PM Gibs @.***> wrote:

Thinking about this some more I'm not sure I fully understand the need to
rename/create ALRModel. If we remove alr_params from
TableModel.specifications isn't that sufficient? A CLRModel would be able
to use the same inference conversion but specifying no fitted parameters
are in ALR coordinates. (And ILRModel we can figure out later.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gibsramen/BIRDMAn/pull/52#issuecomment-873473104, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXOO6N4E6RJC23TB2M3TV56R5ANCNFSM47VQA3UA
.

Right ... I wonder if we even need the alr_params here right? Can we just
remove it completely? And would we still be able to obtain inference
objects if we do so
On Tue, Jul 6, 2021 at 9:55 AM Gibs @.***> wrote:

@.**** commented on this pull request.
In birdman/model_util.py
https://github.com/gibsramen/BIRDMAn/pull/52#discussion_r664683330:

@@ -9,7 +9,7 @@
from .util import convert_beta_coordinates

-def single_fit_to_inference(
+def full_fit_to_inference(
fit: CmdStanMCMC,
params: Sequence[str],
coords: dict,
Or actually probably cleaner to just assign to an empty list if alr_params
== None
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gibsramen/BIRDMAn/pull/52#discussion_r664683330, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXOUKJVV2KSZ4R5UXDLTWMRO5ANCNFSM47VQA3UA
.

Removing alr_params from full_fit_to_inference would require some rethinking. Couple of options below

Specifying values in coords to be D-1 rather than D for the default (ALR) models and performing ALR -> CLR in e.g. NegativeBinomial.to_inference_object. In this case full_fit_to_inference would essentially be a light wrapper for az.from_cmdstanpy (similar to how it is currently done in the single feature equivalent).
Having full_fit_to_inference take some sort of optional transformation function/callable for post-processing (this could I guess be used to build ILR/cosh/etc. in an included transform.py module).
Leave any transformations up to the user

I think (2) is the best approach but open to other options.

Let's try to flesh out option 2 a bit more.
If I'm understanding this correctly, the whole problem stems from az.from_cmdstanpy where the coords for the features needs to be passed in correctly?
Wouldn't each model have their own coords defined? ALR / CLR / ILR should have their own feature names specified in these models, so I would think that these models should be passed in directly to az.from_cmdstanpy.
Regarding the alr to clr conversion, I recommend creating a separate method that does that -- this could take in an inference object in alr coordinates and return a clr transformed object. This should further simplify the interface.

Ok - that sounds like a plan. We should have full_fit_to_inference do no transformation on its own and handle that in a separate function/module.
I'll address that in a new PR - is there anything else you think should be addressed in this PR before merging?

👍 I think this is ready to merge.


[FOLO] First upload/download request WINS

If a file is downloaded then uploaded, only the download is registered in the log, and vice versa. This is bad, because which one is kept is completely dependent on which one is used first.
I suppose it's not really cool to have a build download something, build the same thing (from a GAV perspective) and try to re-upload it...but still, it seems like at least we need some sort of formal declaration of this design.

Can you point me a ftest or similar one corresponding to this issue? Questions are like, what is FOLO for, what does upload (store?) and download mean in this context? Where is the log and what register is (log4j output?). I need some more background for this issue.

There are ftests for folo in the addons/folo/ftests module...I'm not sure if that's what you're after.
 It exposes a set of REST URLs that basically the same as the ones you would normally use to download or upload content, with the difference that they allow you to specify a tracking id. When you download or upload content via one of these URLs (instead of the main ones), folo will add entries to the tracking record corresponding to that tracking id. It also exposes a few REST resources for sealing (closing) the tracking record, and downloading / deleting the record.
Where you'd normally use the following to download content from the public group:
http://localhost:8080/api/group/public/org/commonjava/commonjava/11/commonjava-11.pom
To track it, you might use:
http://localhost:8080/api/folo/track/my-session/group/public/org/commonjava/commonjava/11/commonjava-11.pom
Then, to retrieve the tracking report, you'd use:
http://localhost:8080/api/folo/admin/my-session/record
You could also choose to download the content you accessed as a zip containing a repository-formatted directory structure:
http://localhost:8080/api/folo/admin/my-session/repo/zip
You'll see logs for the ftests in embedders/savant/target/failsafe-tests, just like with any other ftest.
A test like this one might be modified to have an upload and a download of the same file, then the rest of the test would show what's in the tracking record:
https://github.com/Commonjava/indy/blob/master/addons/folo/ftests/src/main/java/org/commonjava/indy/folo/ftest/report/StoreFileAndVerifyInTrackingReportTest.java

Thanks for the details! I've added a ftest to reproduce the issue.
As you mentioned we need a "defined rule for which one gets kept, and which discarded". The code shows If (path, storeKey, accessChannel) equals, the later entry will override the original entry, i.e., FoloRecordCache.recordArtifact { ... inProgressRecordCache.put( entry, entry ); ...}. So what is the rule? Do we keep both download and upload entry of the same file/path? What if there are multiple downloads or uploads, do we record them all?
BTW, it seems the entry is written via FoloTrackingListener. Where and how does this listener get registered? I did not find any usage via IDEA "find usage" for this listener.

I think it might serve the most use cases if we log both download and upload for a given file. That would require adding the event type (upload/download) to the key used to lookup the path for de-duplication, I guess, but I don't think that really hurts anything.
The FoloTrackingListener uses the JEE @Observes annotation to listen for Event, which is triggered by implementations of FileEventManager (from galley). I think Indy may have its own implementation of that, but I'm not sure. It's a bit of a pain to trace, since IDEA can't really follow it normally through the call stack (or through "find usage" as you said).

Thanks for help. I fix it by updating TrackedContentEntry.equals(), adding event type as another key field; so that when putting new entry to map, the previous entry is not overridden. I've updated the ftests and it works fine. BTW, I add Thread.sleep(2000) before seal to let event being handled. Otherwise event handler may report "xxx already sealed" error. There should have similar issue in other ftests. That explains why sometimes I run a test failed within IDEA but succeeded via command line mvn test, e.g., StoreFileAndVerifyInTrackingReportTest. Not sure if that is a problem in prod environment.
----- Original Message -----

From: "John Casey"<EMAIL_ADDRESS>To: "Commonjava/indy"<EMAIL_ADDRESS>Cc: "Rui Han"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Sent: Tuesday, September 27, 2016 12:01:58 AM
Subject: Re: [Commonjava/indy] [FOLO] First upload/download request WINS (#371)
I think it might serve the most use cases if we log both download and upload
for a given file. That would require adding the event type (upload/download)
to the key used to lookup the path for de-duplication, I guess, but I don't
think that really hurts anything.
The FoloTrackingListener uses the JEE @Observes annotation to listen for
Event, which is triggered by implementations of
FileEventManager (from galley). I think Indy may have its own
implementation of that, but I'm not sure. It's a bit of a pain to trace,
since IDEA can't really follow it normally through the call stack (or
through "find usage" as you said).
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Commonjava/indy/issues/371#issuecomment-249614432


Move widget-specific scss out of default.scss

Currently all styles are defined in default.scss. This poses problems for sharing widgets, and makes it harder to find styles for the widget you're working on.
Instead, widget styles should be moved to an appropriately-named file in the widgets folder.
e.g. Styles for the number widget would go in widgets/number_widget.scss alongside widgets/number_widget.jsx

Fixed in #14


Crashing app

Description
Second time. It seems to happen when I am cutting and pasting files. between two tabs.
Steps To Reproduce
select files in one tab
ctrl x
select other tab
ctrl c
crash report
Requirements

eg. Fix crash that occurs when...cutting and pasting files.
eg. Correct action happens when clicking...

Files Version
2.4.67
Windows Version
Edition	Windows 10 Pro Version	22H2 Installed on	11/7/2022 OS build	19045.2846 Experience	Windows Feature Experience Pack 120.2212.4190.0
Log file
debug.log

Thanks for the report. I am unable to reproduce this, Can you give the following information.

Where are you pasting to and from?

@pakmanj


[📑 Docs]: improve studio validation tutorial

What Dev Docs changes are you proposing?
I was following this tutorial link (https://www.asyncapi.com/docs/tutorials/studio-document-validation) to complete the Studio beta Invalid Document tutorial. The link seems outdated because the vast majority of errors in the document are not even mentioned in the tutorial. That's not actually very helpful for a tutorial, because there are 5 remaining unaddressed errors that I don't know how to solve and can't find the info for. A tutorial should be easy to follow and educational. I feel that by not addressing a majority of the errors (5) that it isn't as educational as it should be.

Also, within the Studio Invalid Document there is a link to a tutorial. (https://www.asyncapi.com/docs/tutorials/validate-documents) It results in an error 404, so is not working. It needs to be updated to the correct link.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey @KD117, thanks for raising this issue. Please update the Issue title to have better visibility for everyone.
Pinging @alequetzalli here to inform her about this issue.

Echoing what @akshatnema said, thank you for voicing your experience and feedback!
I agree we can improve this tutorial and address the remaining errors. Would you like to contribute your time to work on this issue? @KD117

fyi @starlightknown, thoughts? 😄

fyi @starlightknown, thoughts? 😄

yes, this could use some improvement, I can find out more errors and try to document them. Last time we did, I think it was only for the major ones

do you feel open to picking it up, @starlightknown? (assuming we don't hear back from @KD117)   😄

Yep I'll pick it if they don't reply

Hello all! @starlightknown @alequetzalli My apologies, I am very new to this! We work mostly within GitLab at work, and I'm not as familiar with GitHub. How can I help? I could use some direction please. Thanks.

Hey @alequetzalli :wave:
An update on this issue.
After following the tutorial, I'm getting the following message from the diagnostics box

Also, within the Studio Invalid Document there is a link to a tutorial. (https://www.asyncapi.com/docs/tutorials/validate-documents) It results in an error 404, so is not working. It needs to be updated to the correct link.

I think this has also been fixed :arrow_up:

Also, within the Studio Invalid Document there is a link to a tutorial. (https://www.asyncapi.com/docs/tutorials/validate-documents) It results in an error 404, so is not working. It needs to be updated to the correct link.

I've opened an issue and following PR to address this in the Studio repo.


Add type-safe model selection and support for Swift Concurrency

What it Does
This Commit:

replaces the optional completion closure parameters ((OpenAI?, OpenAIError?) -> Void) in OpenAISwift.sendCompletion(with:model:completionHandler:) with the Result type ((Result<OpenAI, OpenAIError>) -> Void)
adds an async wrapper around OpenAISwift.sendCompletion(with:model:completionHandler:) using a CheckedThrowingContinuation so that it can be called in an asynchronous context using Swift Concurrency (async/await)
adds an OpenAIModelType enum which replaces the old string-based model naming with strongly typed enum cases. It supports all the GPT and Codex models listed in the documentation.

Note: I haven't included the Content filter models as the documentation suggests the use of their moderation endpoint instead of the current completion endpoint

This is such a nice improvement, thank you 😍


CHAP configuration for iscsi targets

Is there documentation on how/where to configure CHAP settings when creating the iscsi targets/luns? Is there a way to store that in a secret and point to it from the storageclass parameter key?
I have the CSI driver setup and working, and it creates the targets and luns as expected, but I don't see where to provide CHAP credentials. If I create the PVC in my k8s cluster, it will create the target and luns, but will fail to connect because my nodes are passing CHAP credentials to the Synology NAS. If I edit the target in DSM, then the lun mounts as expected.
This is a new install, so I am not sure what will happen with scaling up and down yet, but mobility between nodes should be fine.
For references, my cluster is using Ubuntu 22.04LTS on Raspberry Pi 4B Nodes, which are PXE Booting to an iSCSI root off the Synology. So the iscsi configuration on the nodes and the synology are configured and working correctly. And as stated, after the PVCs are deployed and the PVs are created, I can see the LUNs and Targets in the DSM. If I add the CHAP configuration at that point, then the volumes mount and run as expected.

+1 it would be great to have support for auth in this driver

There seems to be some stub code but no real implementation: https://github.com/SynologyOpenSource/synology-csi/blob/a4270a3a9c793694f58f9284eb117b44f3f51e64/pkg/driver/initiator.go#L32

I found a solution by adding chap setting in iscsi config file "iscsid.conf" on each nodes.


Type Mismatch: Signed to Unsigned

Hello -

I'm using PromiseKit 6 (major version)
I'm using PromiseKit via CocoaPods

A minor security vulnerability showed up in a Fortify scan for my app. It deals with a signed to unsigned type mismatch. It doesn't appear I'm able to submit this in the GitHub security tab so I'm reporting it here. Please move this to security area and close this issue, if able to.
Fortify describes the vulnerability as...

Type Mismatch: Signed to Unsigned
It is dangerous to rely on implicit casts between signed and unsigned numbers because the result can take on an unexpected value and violate weak assumptions made elsewhere in the program.
Conversion between signed and unsigned values can lead to a variety of errors, but from a security standpoint is most commonly associated with integer overflow and buffer overflow vulnerabilities.

Fortify references this code in PromiseKit...

The function ^{}() in PMKCallVariadicBlock.m is declared to return an unsigned value, but on line 91 it returns a signed value.

This appears to be a very minor issue, but I wanted to offer the information and see if it can be resolved. I doubt it is of significant risk, but it would be nice to resolve if possible to achieve a clean scan with Fortify.

https://github.com/mxcl/PromiseKit/blob/f035696eb44587be4fbd7ffaa5c7ed96491d7f3b/Sources/PMKCallVariadicBlock.m#L43
I think Fortify is wrong. The function return type is id and this is some voodoo ObjC / C stuff here. id can basically be any type.

Thanks for the quick response. I will comment in Fortify. Thanks!


go1.4.1 build breaks on ubuntu

I am trying to build go1.4.1 from the latest repo on Ubuntu 14.04.02 x86_64 box
$ git checkout go1.4.1
$ cd src
$ ./all.bash
...
...
..
# Checking API compatibility.
Error running hg clone on go.tools: exit status 255
abort: HTTP Error 404: Not Found
exit status 1

The cause of the failure seems to be that go tools has been moved from code.google.com to a github repo.
~/g/src git:tags/go1.4.1 ❯❯❯ grep -r  "hg clone"                                                                                ◼
cmd/api/run.go:// else it hg clones it.
cmd/api/run.go:	// cloneDir is where we run "hg clone".
cmd/api/run.go:	os.RemoveAll(tmpDir)   // in case of aborted hg clone before
cmd/api/run.go:		log.Fatalf("Error running hg clone on go.tools: %v\n%s", err, out)

Though the above is the last test before the "ALL PASSED" mark, it still results in an unclean build.

You can just run ./make.bash instead. We won't be doing any new releases of Go 1.4, especially for such a minor issue.

Seen with SteamOS building go 1.4.3 branch to build latest 1.7, unblocked go.googlesource.com/go build by running make.bash instead as suggested. The "just works" path may always pause here with the go 1.4 dependency.

@pciet, we don't reuse old bugs. Open a new bug if you have a unique issue to discuss. If it's the same as this one, this one is closed.


Eval submission fixes for 70b / other models

@vwxyzjn i'm trying to make it scale GPUs automatically!


Translation function

Description of the new feature / enhancement
It is hoped that the existing translation function can be built-in to prevent the plug-in from being unable to be installed due to different folder names.
Scenario when this would be used?
It is hoped that the existing translation function can be built-in to prevent the plug-in from being unable to be installed due to different folder names.
Supporting information
No response

Can you elaborate a bit more on the request? Thanks
/needinfo


fix: save terms of service checkbox in draft

Details

This PR fixes the condition which set the value of terms of service checkbox inside the draft state.
Fixed Issues

$ https://github.com/Expensify/App/issues/16885
PROPOSAL: https://github.com/Expensify/App/issues/16885#issuecomment-1520846065
Tests

Go to Settings > Workspace > Connect Bank Account.
Click on "Continue with Setup."(Enter all record if you have not)
Uncheck the Step 1 checkbox and go back.
Click on "Continue with Setup" again.

Verify that the checkbox remains unchecked.

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Go to Settings > Workspace > Connect Bank Account.
Click on "Continue with Setup."(Enter all record if you have not)
Uncheck the Step 1 checkbox and go back.
Click on "Continue with Setup" again.

Verify that the checkbox remains unchecked.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/30054992/236485584-05125f13-6516-4b3a-9f92-4a8d20aa3ec9.mov

Mobile Web - Chrome

https://user-images.githubusercontent.com/30054992/236485695-2150ba7b-60cd-4c74-8e9b-25b7a37c9d2a.mov

Mobile Web - Safari

https://user-images.githubusercontent.com/30054992/236485758-1dcc8309-a4f6-42c1-9560-42356b785431.mov

Desktop

https://user-images.githubusercontent.com/30054992/236485794-2fb6db62-b1c0-40ac-a837-427a3c6fbe22.mov

iOS

https://user-images.githubusercontent.com/30054992/236485858-d7bd1967-7bb3-4ddd-af58-884988aedd89.mov

Android

https://user-images.githubusercontent.com/30054992/236485937-2b1acfcb-57a4-4bd2-bb67-91586fe5f144.mov

: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 https://github.com/pecanoro in version: 1.3.13-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Make playwright tests not flaky

I keep seeing broken playwright tests in PRs
I don't know why it's flaky, but we shouldn't be seeing that so often in PRs
/bounty $5

Yes if its idiomatic

@seveibar the tests are flaky they somtime passed but sometimes they take more time due to UI Delays
Before:

After tracing each of them:

Some failed due to timeouts because some tests are accesing more than 1 UI elements and due to this they are fail to do in required time.

/attempt #346


Stop processing level cap 40 by default

More justifications: pvpoke has started ranking XL Pokemon by default.

@TurtleSocks I think that is an independent concern. Please review this change first and we can figure that out in another PR?


Extreme high prediction time

Describe the bug
I first trained an efficient_ad model with my own dataset. Afterwards I want to make some prediction. But i got the problem, that the time needed to make one prediction in extremely high. One prediction takes between 90s and 120s. How can I improve the time?
GPU: NVIDIA GeForce RTX 2060
Dataset
Other (please specify in the text field below)
Model
Other (please specify in the field below)
Steps to reproduce the behavior

Train model
Run inference

for file in test_images_paths:
    image_name = str(file).split("/")[-1].split(".")[0]
    image_name = image_name + ".png"

    command = 'python tools/inference/lightning_inference.py --config results/efficient_ad_SolderJoints_reduzierte_Anzahl_100_Epochs/efficient_ad/SolderJoint/run/config.yaml --weights results/efficient_ad_SolderJoints_reduzierte_Anzahl_100_Epochs/efficient_ad/SolderJoint/run/weights/lightning/model-v1.ckpt --input datasets/SolderJoints/test_eindeutig_sortiert/' + image_name + ' '
    command = command + '--output run/efficient_ad_solder_joints --visualization_mode "simple"'# --show'
    command = command.replace("\\", "/")
    timeStart = time.time()
    subprocess.run(str(command), shell=True)
    timePred = "Time for prediction: {:5.3f}s".format(time.time() - timeStart)
    print(timePred)

OS information
OS information:

OS: [e.g. Ubuntu 20.04]
Python version: [e.g. 3.8.10]
Anomalib version: [e.g. 0.3.6]
PyTorch version: [e.g. 1.9.0]
CUDA/cuDNN version: [e.g. 11.1]
GPU models and configuration: [e.g. 2x GeForce RTX 3090]
Any other relevant information: [e.g. I'm using a custom dataset]

Expected behavior
Faster inference speed
Screenshots

Pip/GitHub
pip
What version/branch did you use?
anomalib                  1.0.0.dev0
Configuration YAML
dataset:
  name: SolderJoint
  format: folder
  root: ./datasets/images/
  normal_dir: IO
  abnormal_dir: NIO
  task: classification
  mask_dir: null
  normal_test_dir: null
  extensions: null
  split_ratio: 0.2
  seed: 0
  image_size: 256
  train_batch_size: 64
  eval_batch_size: 64
  num_workers: 24
  normalization: none
  test_split_mode: from_dir
  val_split_ratio: 0.5
  transform_config:
    eval: null
    train: null
  val_split_mode: from_test
logging:
  log_graph: False
  logger: []
metrics:
  image:
  - F1Score
  - AUROC
  threshold:
    manual_image: null
    manual_pixel: null
    method: adaptive
model:
  lr: 0.0001
  model_size: small
  name: efficient_ad
  normalization_method: min_max
  pad_maps: True
  padding: False
  teacher_out_channels: 38
  weight_decay: 0.00001
optimization:
  export_mode: null
project:
  path: ./results/efficient_ad
  seed: 42
trainer:
  accelerator: gpu
  accumulate_grad_batches: 1
  auto_lr_find: False
  auto_scale_batch_size: False
  benchmark: False
  check_val_every_n_epoch: 1
  default_root_dir: null
  detect_anomaly: False
  deterministic: False
  devices: 1
  enable_checkpointing: True
  enable_model_summary: True
  enable_progress_bar: True
  fast_dev_run: False
  gradient_clip_algorithm: norm
  gradient_clip_val: 0
  limit_predict_batches: 1.0
  limit_test_batches: 1.0
  limit_train_batches: 1.0
  limit_val_batches: 1.0
  log_every_n_steps: 50
  max_epochs: 50
  max_steps: 70000
  max_time: null
  min_epochs: null
  min_steps: null
  move_metrics_to_cpu: False
  multiple_trainloader_mode: max_size_cycle
  num_nodes: 1
  num_sanity_val_steps: 0
  overfit_batches: 0.0
  plugins: null
  precision: 32
  profiler: null
  reload_dataloaders_every_n_epochs: 0
  replace_sampler_ddp: True
  strategy: null
  sync_batchnorm: False
  track_grad_norm: -1
  val_check_interval: 1.0
visualization:
  image_save_path: null
  log_images: False
  mode: full
  save_images: true
  show_images: False # show images on the screen

### Logs

```shell
NVIDIA GeForce RTX 2060
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\anomalib\config\config.py:280: UserWarning: config.project.unique_dir is set to False. This does not ensure that your results will be written in an empty directory and you may overwrite files.
  warn(
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\torchmetrics\utilities\prints.py:36: UserWarning: Metric `PrecisionRecallCurve` will save all targets and predictions in buffer. For large
datasets this may lead to large memory footprint.
  warnings.warn(*args, **kwargs)
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\anomalib\utils\callbacks\__init__.py:142: UserWarning: Export option: None not found. Defaulting to no model export
  warnings.warn(f"Export option: {config.optimization.export_mode} not found. Defaulting to no model export")
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\pytorch_lightning\trainer\connectors\checkpoint_connector.py:55: LightningDeprecationWarning: Setting `Trainer(resume_from_checkpoint=)` is deprecated in v1.5 and will be removed in v2.0. Please pass `Trainer.fit(ckpt_path=)` directly instead.
  rank_zero_deprecation(
GPU available: True (cuda), used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
`Trainer(limit_train_batches=1.0)` was configured so 100% of the batches per epoch will be used..
`Trainer(limit_val_batches=1.0)` was configured so 100% of the batches will be used..
`Trainer(limit_test_batches=1.0)` was configured so 100% of the batches will be used..
`Trainer(limit_predict_batches=1.0)` was configured so 100% of the batches will be used..
`Trainer(val_check_interval=1.0)` was configured so validation will run at the end of the training epoch..
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\torchmetrics\utilities\prints.py:36: UserWarning: Metric `ROC` will save all targets and predictions in buffer. For large datasets this may lead to large memory footprint.
  warnings.warn(*args, **kwargs)
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
C:\Users\z004uhnp\.conda\envs\anomalib_env\lib\site-packages\pytorch_lightning\trainer\connectors\data_connector.py:224: PossibleUserWarning: The dataloader, predict_dataloader 0, does not have many workers which may be a bottleneck. Consider increasing the value of the `num_workers` argument` (try 24 which is the number of cpus on this machine) in the `DataLoader` init to improve performance.
  rank_zero_warn(
Predicting DataLoader 0: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:31<00:00, 31.36s/it]
Time for prediction: 60.973s

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello.
There might be more reasons for this, but the first thing is that this is not really just inference time. The time you track also includes time needed to create instances of dataloader, trainer, metrics and many other things. In real scenario, you usually don't re-instantiate all those things for prediction, a more realistic approach would be to just time predict step.
https://github.com/openvinotoolkit/anomalib/blob/66532fc1625020ce7ff6f3fc1565663aa540e834/tools/inference/lightning_inference.py#L83
Now this still doesn't explain such a long duration. I believe the issue is having 24 workers for the dataloader, so try using num_workers: 0.
Having more workers is usually better when you are sending multiple data to the model. However this is not the case for small datasets or a single image. I also noticed that on some of my systems, having this number high results in a very long delay until the first step of training. I'm not sure why, but it might be due to the way the dataloader copies are made and orchestrated behind the scenes.
To summarize: try setting num_workers to 0 and keep in mind that the way you benchmark doesn't capture just the inference time.

Hi @LenaMetzen, you could refer to #1183. I'm closing this as this is a duplicate. Feel free to ask questions there if you experience any issues. Good luck!


Vehicle reconnection logic gives up

Describe the bug
If the car is offline or the server cannot be reached, the logic attempts to re-establish the connection. However, if this does not work for a certain period of time, no further connection attempt is made and the car remains "offline". The behavior is apparently logic and not brand-related. See also here. Currently a restart solves the issue until next occurrence.
Steps to reproduce

Connect a car and start evcc. Car is "online"
try to block the connection from the car to the server. Time period unknown. Try for at least 24h.
unblock the connection and reconnect the car to the server
EVCC should stay "offline" although it should be connected
Restart evcc should solve the issue

Configuration details
not provided

Log details
right after evcc start
ERROR 2024/03/18 16:16:38 creating vehicle dacia_1 failed: cannot create vehicle type 'template': cannot create vehicle type 'dacia': Get "https://accounts.eu1.gigya.com/accounts.login?xxxxxx": dial tcp: lookup accounts.eu1.gigya.com on <IP_ADDRESS>:53: server misbehaving

and 10 minutes later:
evcc[1542]: [lp-1  ] INFO 2024/03/18 16:26:54 vehicle updated: unknown -> Dacia Spring 2023 (unavailable)

16 hours later:
evcc[1542]: [lp-1  ] INFO 2024/03/19 08:21:14 vehicle updated: Dacia Spring 2023 (unavailable) -> unknown
evcc[1542]: [lp-1  ] INFO 2024/03/19 12:34:50 vehicle updated: unknown -> Dacia Spring 2023 (unavailable)

and so on ...
vehicle stays offline
What type of operating system are you running?
Linux
Version
0.124.7

Missing log

Let's see if we can incorporate at least a manual retry in https://github.com/evcc-io/evcc/pull/12962

i could not get the reason until now, but i logged with debug level and added it to the log details above... the trace log floods my log files after 18 hours... do i need anyway?


Set Black as the formatter for all Python code in the extension

Black just hit beta, so I think we can rely on it as our official formatter for all Python code in the extension and make it a PR requirement that code be formatted using it.

Doesn't black run only in Python3?
If so, three would be a few challenges, as  we install modules into selected environment (which could be python2).

This is just for our internal Python code in the extension, not for users.

Oops, didn't read the comments carefully enough.

Closing as it's being tracked here: https://github.com/microsoft/vscode-python/issues/2012


import/order 2.20.1

This package works incorrectly on v2.20.1 for import/order rule.
Previously I was working on v2.18.x and the rules worked as I expected in accordance with the documentation.
After package upgrade I got an error:
There should be no empty line within import group  import/order
This error happens where it should not.
If it'd help, v2.20.0 works fine as expected and only the latest patch version produces this behavior.
.eslintrc.json
    "import/order": [
      2,
      {
        "newlines-between": "always",
        "groups": [
          ["builtin", "external"],
          ["parent", "internal", "sibling", "index", "unknown"]
        ]
      }
    ]

component.jsx
import React from 'react';
import ReactDOM from 'react-dom';

import { App } from './App/App';
import { unregister } from './serviceWorker';
import './index.css';

Which line is warned on?

I'm not sure what in v2.20.1 would have caused this; #5625 should only affect alphabetize (cc @wschurman), #1605 would only affect the external module folders setting.
What's your full eslint config?

@ljharb
affected line

config (I removed all rules except import/*)
{
  "parser": "@typescript-eslint/parser",
  "plugins": [
    "@typescript-eslint",
    "prettier",
    "react",
    "import",
    "react-hooks",
    "promise",
    "sonarjs"
  ],
  "extends": [
    "airbnb-typescript",
    "eslint:recommended",
    "react-app",
    "prettier",
    "prettier/react",
    "prettier/@typescript-eslint",
    "plugin:prettier/recommended",
    "plugin:react/recommended",
    "plugin:compat/recommended",
    "plugin:promise/recommended",
    "plugin:sonarjs/recommended",
    "plugin:import/errors",
    "plugin:import/warnings",
    "plugin:import/typescript",
    "plugin:@typescript-eslint/recommended"
  ],
  "settings": {
    "import/resolver": {
      "eslint-import-resolver-lerna": {
        "packages": "packages/"
      },
      "node": {
        "paths": [
          "src"
        ],
        "extensions": [
          ".js",
          ".jsx",
          ".ts",
          ".tsx"
        ]
      }
    },
    "import/parsers": {
      "@typescript-eslint/parser": [
        ".ts",
        ".tsx"
      ]
    },
    "react": {
      "version": "detect"
    }
  },
  "rules": {
    "import/no-unresolved": 2,
    "import/named": 2,
    "import/namespace": 2,
    "import/default": 2,
    "import/export": 2,
    "import/no-cycle": 2,
    "import/imports-first": [
      2,
      "absolute-first"
    ],
    "import/newline-after-import": 2,
    "import/prefer-default-export": 0,
    "import/no-useless-path-segments": 2,
    "import/no-default-export": 2,
    "import/no-mutable-exports": 2,
    "import/no-namespace": 2,
    "import/no-extraneous-dependencies": 0,
    "import/no-duplicates": 2,
    "import/order": [
      2,
      {
        "newlines-between": "always",
        "groups": [
          [
            "builtin",
            "external"
          ],
          [
            "parent",
            "internal",
            "sibling",
            "index",
            "unknown"
          ]
        ]
      }
    ]
  },
  "env": {
    "browser": true,
    "node": true,
    "jest": true
  }
}

What's the full code of component.jsx? Sometimes I get this warning when theres an errant import or require below in the body of the code.

@wschurman
I don't think if this is the same case;
be sure that the error is on the 2nd line
to make it clear I did several times the same thing:

install 2.20.0
run lint + check the component. Everything is fine.
install 2.20.1
run lint (caught errors) + check the component (eslint plugin displayed an error)

full code:
import React from 'react';
import ReactDOM from 'react-dom';

import { App } from './components/App';
import { unregister } from './serviceWorker';
import './index.css';

ReactDOM.render(<App />, document.getElementById('root'));

// If you want your app to work offline and load faster, you can change
// unregister() to register() below. Note this comes with some pitfalls.
// Learn more about service workers: https://bit.ly/CRA-PWA
unregister();

@maktarsis are you on windows?
Either way, can you also try with the latest commit on master for this plugin, and see if your problem is fixed?

@ljharb yeah, I am
Ok, I'll probably try

I'll close this for now, but am happy to reopen if the issue isn't solved on latest master.

@ljharb everything is fine now


How add this project in Angular and .Netcore Web api preview

how to add this project as a template to my Angular and ASP.Net core (preview) Project?
i was tried but some of designs are not working properly so kindly guide me how to do that.
Thanks.

Even I am trying to integrate the same with my project but not able to integrate it properly here is what I am trying
https://github.com/Github743/PrimeNgFlex


Use cmake variables for installation destinations

Location of libraries and development files may be different when building for different platforms. CMake can handle this just fine, however, the current cmake configuration does not use these facilities. This merge request fixes that.

Disclaimer, I am no expert on CMake, so would love if you could explain (or point me to) the difference between say CMAKE_INSTALL_PREFIX}/lib and CMAKE_INSTALL_LIBDIR/. Are you suggesting that the issue is that I "hardcoded" include and lib for the directories?
As it was, you could change CMAKE_INSTALL_PREFIX to point to location that you wanted, so that was not enough?
Again, nothing against the change, just trying to understand better. Thanks!

I'm not an expert on CMake either but we are building the client for a platform that puts libraries in /usr/lib64. The build system is yocto and it has cmake class that takes care of installing bits and pieces into correct locations. But having destinations hardcoded interferes with the intent.

You may want to hold off this patch though. I want to give it to our CMake expert to review. I may have missed something.

Sure, thanks!

that being said, your changes seem fine to me. Using those 2 cmake variables seem to work fine (include defaults to include and lib to lib on my macOS, which is what I was hardcoding with). But probably defaults to other values for other platforms.

I may have missed something, it is still not placing the libraries in /usr/lib64 for me :-(

Have you modified CMAKE_INSTALL_PREFIX? You can do that from make edit_cache.

I'm closing the pull request. It is completely wrong. First of all, CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_INCLUDEDIR variables are defined by GNUInstallDirs module that is not included. And secondly, the part I modified is used to build uninstall target and has nothing to do with the installation. I will create a new pull request once I figure it out.


Picking up of configuration

Shutting down and starting up the VM with Gogs running in Docker, will go to install page in the browser, with logs outputting, "Custom config '/data/gogs/conf/app.ini' not found, ignore this if you're running first time".
It happens on my Mac with CoreOS VM, running Docker 1.10.3. Issue does not occur with docker restart gogs. However, issue resolves after performing docker restart gogs.

I think it is because you did not volume the custom directory... deployment problem please go to https://discuss.gogs.io/...


Is there a way to change the startup directory for the PowerShell process?

It seems the current startup directory is the VSCode app directory ($Env:LocalAppData\Programs\Microsoft VS Code in Windows). Is there a way to set it, for example, to the VSCode workspace folder (${workspaceFolder})?
I know there is $PSScriptRoot to reference the current test file's directory, but there seems to be no straight forward/consistent way to reference the workspace root (directory).

I can look into enabling it to follow wherever you have PSIC defined or a separate setting, but $PSScriptRoot is indeed the recommended way to reference relative paths in tests.

The PSIC cwd is a great idea! That way the behavior would be consistent with the PowerShell extension's run/debug commands.

This was fixed a while ago in c3cb336